Jump to content


Photo

[SOLVED]SafeStrap not going into recovery no os on phone

xt807 safestrap no os motorola droid razr m help

Best Answer tucstwo , 24 April 2013 - 07:02 PM

OK, OFFICIALLY SOLVED! This member needed the 4.1.2 Razr M FXZ files that were pre-released this evening. (I'm sure a public release in imminent). When he flashed the (edited...to confirm previous version..in his case) he was able to get his phone fully restored and booting. Case CLOSED.

 

To those reading. The Razr M 4.1.2 FXZ files HAVE leaked and I'm sure will be on SBF developers within hours. Cheers!

Go to the full post


  • Please log in to reply
107 replies to this topic

#41 lowvolt

lowvolt

    Droid Master

  • Members
  • PipPipPip
  • 478 posts

Posted 24 April 2013 - 06:47 AM

OK, just ordered my adapter - don't need it now, but who wants to wait until you do? :)
 
@lowvolt - if I uninstall Safestrap, I'd lose my custom recovery, so what would I do for backing up my ROM, etc? Ummm. dumb question, I suppose. There's probably a way to install a recovery without Safestrap, I'd guess. Or it's something you can do once you are unlocked. Never been unlocked before in the same way.


After you unlock you can install a real custom recovery like TWRP which is just like s's or cwm which is kinda like stock recovery

Sent from my XT907 using Tapatalk 2


Exactly! IMHO it is more fail proof then ss

Sent from my XT907 using Tapatalk 2

#42 aiur1

aiur1

    Member

  • Members
  • PipPip
  • 54 posts
  • LocationCalifornia
  • Current Device(s):Note 3 (SM-N900V)

Posted 24 April 2013 - 07:02 AM

I charged my phone via the wall charger, and ran matts utility. It stopped throwing out the battery messages. What's wrong now?

 

 


[*] Simple Razr Restore
[*] Windows Version
[*] Created by mattlgroff
[*]
[*] Before continuing, ensure your Razr is in the
[*] "AP Fastboot" mode and connected via USB.
[*]--- Also press the keys after the screen flashes back on when asked---
[*] If your battery is low do NOT run this program Charge Charge Charge!
Press any key to continue . . .
sending 'sbl1' (100 KB)...
OKAY [  0.016s]
writing 'sbl1'...
OKAY [  0.480s]
finished. total time: 0.497s
sending 'sbl2' (126 KB)...
OKAY [  0.022s]
writing 'sbl2'...
OKAY [  1.033s]
finished. total time: 1.055s
sending 'sbl3' (512 KB)...
OKAY [  0.051s]
writing 'sbl3'...
OKAY [  1.227s]
finished. total time: 1.280s
sending 'rpm' (140 KB)...
OKAY [  0.023s]
writing 'rpm'...
OKAY [  0.503s]
finished. total time: 0.527s
sending 'tz' (192 KB)...
OKAY [  0.030s]
writing 'tz'...
OKAY [  0.504s]
finished. total time: 0.535s
sending 'aboot' (256 KB)...
OKAY [  0.037s]
writing 'aboot'...
OKAY [  1.005s]
finished. total time: 1.042s
rebooting into bootloader...
OKAY [  0.008s]
finished. total time: 0.008s
 Waiting for a moment...
sending 'partition' (32 KB)...
OKAY [  0.016s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.292s
sending 'sbl1' (100 KB)...
OKAY [  0.022s]
writing 'sbl1'...
OKAY [  0.709s]
finished. total time: 0.731s
sending 'sbl2' (126 KB)...
OKAY [  0.024s]
writing 'sbl2'...
OKAY [  1.292s]
finished. total time: 1.316s
sending 'sbl3' (512 KB)...
OKAY [  0.054s]
writing 'sbl3'...
OKAY [  1.240s]
finished. total time: 1.295s
sending 'rpm' (140 KB)...
OKAY [  0.026s]
writing 'rpm'...
OKAY [  0.519s]
finished. total time: 0.546s
sending 'tz' (192 KB)...
OKAY [  0.028s]
writing 'tz'...
OKAY [  0.765s]
finished. total time: 0.794s
sending 'aboot' (256 KB)...
OKAY [  0.040s]
writing 'aboot'...
OKAY [  0.753s]
finished. total time: 0.795s
sending 'boot' (10240 KB)...
OKAY [  0.807s]
writing 'boot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 1.098s
sending 'system' (30720 KB)...
OKAY [  2.384s]
writing 'system'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 2.709s
sending 'recovery' (10240 KB)...
OKAY [  0.835s]
writing 'recovery'...
OKAY [  2.750s]
finished. total time: 3.585s
sending 'modem' (30720 KB)...
OKAY [  2.385s]
writing 'modem'...
OKAY [  0.985s]
sending 'modem' (17576 KB)...
OKAY [  3.013s]
writing 'modem'...
OKAY [  0.949s]
finished. total time: 7.334s
sending 'devtree' (512 KB)...
OKAY [  0.055s]
writing 'devtree'...
OKAY [  0.552s]
finished. total time: 0.607s
erasing 'modemst1'...
OKAY [  0.598s]
finished. total time: 0.599s
erasing 'modemst2'...
OKAY [  1.078s]
finished. total time: 1.079s
sending 'fsg' (2794 KB)...
OKAY [  0.231s]
writing 'fsg'...
OKAY [  1.364s]
finished. total time: 1.596s
erasing 'cache'...
OKAY [  1.216s]
finished. total time: 1.216s
erasing 'tombstones'...
OKAY [  0.836s]
finished. total time: 0.836s
 It is recommened to wipe data, especially if you were on a custom rom.
 If you don't you will probably bootloop and have to wipe anyway...
 Press any key to Wipe the phone's data (might wipe internal SD card!)
 or exit the utility.
Press any key to continue . . .
erasing 'userdata'...
OKAY [  2.532s]
finished. total time: 2.533s
sending 'modem' (30720 KB)...
OKAY [  2.386s]
writing 'modem'...
OKAY [  1.446s]
sending 'modem' (17576 KB)...
OKAY [  3.004s]
writing 'modem'...
OKAY [  0.948s]
finished. total time: 7.785s
erasing 'modemst1'...
OKAY [  0.605s]
finished. total time: 0.605s
erasing 'modemst2'...
OKAY [  1.101s]
finished. total time: 1.101s
rebooting...
 
finished. total time: 0.005s
 You are now on stock JB 4.1.1.
 Your device will now reboot and install radio files, then fully boot normally.
 
Please make a selection or hit ENTER to return:

 



#43 coleam

coleam

    n00b

  • Members
  • Pip
  • 21 posts
  • Current Device(s):Moto XT907

Posted 24 April 2013 - 07:36 AM

Does your phone boot into an OS?  Because the final message you got is the successful flash message.



#44 aiur1

aiur1

    Member

  • Members
  • PipPip
  • 54 posts
  • LocationCalifornia
  • Current Device(s):Note 3 (SM-N900V)

Posted 24 April 2013 - 07:43 AM

It doesn't. It just sits at the blank screen after the unresponsive safestrap screen



#45 aiur1

aiur1

    Member

  • Members
  • PipPip
  • 54 posts
  • LocationCalifornia
  • Current Device(s):Note 3 (SM-N900V)

Posted 24 April 2013 - 07:46 AM

Maybe I need to flash a new recovery? I need an admin in here :( Tucs need to get on



#46 Aixelsyd

Aixelsyd

    Freak on a Leash

  • Administrator
  • 640 posts
  • LocationWindy City
  • Current Device(s):x13 Dev Ed & x14 Pure Ed & Droid Turbo

Posted 24 April 2013 - 07:51 AM

Maybe I need to flash a new recovery? I need an admin in here :( Tucs need to get on

If the device is charged up and you can manually boot into bootlaoder mode I'd force it into AP mode and reflash the device with the full 4.1.1 XML file using RSD Lite. Then you are back to square one and it will boot like it should. Reason i say that is if you look in your post Boot & System failed when flashing using Matt's Utility. 



#47 tucstwo

tucstwo

    www.drdevs.com

  • Administrator
  • 14,435 posts
  • Twitter:tucstwo
  • Google+:tucstwo@gmail.com
  • LocationNJ
  • Current Device(s):LG G3 VS985, Nexus 7 (flo)

Posted 24 April 2013 - 08:04 AM



Maybe I need to flash a new recovery? I need an admin in here :( Tucs need to get on


If the device is charged up and you can manually boot into bootlaoder mode I'd force it into AP mode and reflash the device with the full 4.1.1 XML file using RSD Lite. Then you are back to square one and it will boot like it should. Reason i say that is if you look in your post Boot & System failed when flashing using Matt's Utility. 


This ^

It seems like the utility is attempting to flash the wrong system version. I would grab RSD lite and the file from the link I sent you one the first page and restore it that way.

Sent from my HTC6435LVW using Tapatalk 2
  • shane1 and aiur1 like this

Visit DRDevs.com hosting site for all official Droidrzr.com ROMs, Apps, GApps and other mods/files!!
Please PM me if you need help!
I will be hosting AOSP-Based ROM GApps packages!
Download the most Up-to-Date GApps Packages for AOSP ROMs from me here!


#48 aiur1

aiur1

    Member

  • Members
  • PipPip
  • 54 posts
  • LocationCalifornia
  • Current Device(s):Note 3 (SM-N900V)

Posted 24 April 2013 - 09:01 AM

I'm flashing

 

C:\Users\Aiur\Downloads\VZW_XT907_4.1.1-9.8.1Q-27-2-4_1FF.xml\VZW_XT907_4.1.1-9.8.1Q-27-2-4_1FF.xml\VZW_XT907_4.1.1-9.8.1Q-27-2-4_1FF.xml

 

With RSD lite and it comes back with this:  

 
 

Failed flashing process: 1/19 flash partition "gpt_main0.bin" > Phone returned FAIL



#49 aiur1

aiur1

    Member

  • Members
  • PipPip
  • 54 posts
  • LocationCalifornia
  • Current Device(s):Note 3 (SM-N900V)

Posted 24 April 2013 - 09:07 AM

On the physical device when I try flashing the above image it says:

 

usb connected

downgraded security version

update gpt_main version failed

preflash validation failed for GPT

downgraded security version

update gpt main version failed



#50 Aixelsyd

Aixelsyd

    Freak on a Leash

  • Administrator
  • 640 posts
  • LocationWindy City
  • Current Device(s):x13 Dev Ed & x14 Pure Ed & Droid Turbo

Posted 24 April 2013 - 09:21 AM

I'm flashing

 

C:\Users\Aiur\Downloads\VZW_XT907_4.1.1-9.8.1Q-27-2-4_1FF.xml\VZW_XT907_4.1.1-9.8.1Q-27-2-4_1FF.xml\VZW_XT907_4.1.1-9.8.1Q-27-2-4_1FF.xml

 

With RSD lite and it comes back with this:  

 
 

Failed flashing process: 1/19 flash partition "gpt_main0.bin" > Phone returned FAIL

 

 

Using 7-zip open the *.XML as an archive ( ie Ie right nouse click on it), then click the folder you see. After that highlight and drag the small *.xml you see to your desktop. Leave the archive open and downsize to your taskbar. Then right mouse click on the XML and select Edit. When it opens look for any lines that have " getvar" in them. Any line with " Getvar " in it delete the line. Once those are deleted save the file. Now drag your saved/edit file back into the archive you have open still. Once you move the edited XML back into the archive close the archive and try flashing again using RSD Lite and oyu should be fine

 

 

 

Edit: here made life easier on you I have the edited file done. Just downlaod it to your desktop. Then open the XML as archive, click folder to open it and drag this edited file into the folder. you should get a popup when oyu drag it asking if you want to overwrite the current file. Hit YES and let it do its thing. Now just close archive and try flashing

Please Login or Register to see this Hidden Content


  • neckchop likes this

#51 aiur1

aiur1

    Member

  • Members
  • PipPip
  • 54 posts
  • LocationCalifornia
  • Current Device(s):Note 3 (SM-N900V)

Posted 24 April 2013 - 09:25 AM

I didn't see anything with those keywords. Here's what's in the XML file if you can overlook it

 

 

 

 

<?xml version="1.0"?>
<flashing>
  <header>
    <phone_model model="SM_JB_VZW_1FF" />
    <software_version version="smq_vzw-user 4.1.1 9.8.1Q_27-2 4 release-keysSM_BP_1139.000.32.62P" />
    <interfaces>
      <interface name="AP" />
    </interfaces>
  </header>
  <steps interface="AP">
    <step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="1471592C5BF1F0FD177F38FD49832E57" />
    <step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="29C7BBE0C1CE38534FBDBE690AAF070F" />
    <step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="ADF26930AE152628B139A679295D75ED" />
    <step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="086A85B235882300B2760A447FBA26C5" />
    <step operation="flash" partition="rpm" filename="rpm.mbn" MD5="919D0B340CFDD5FC7C541803DB65C2D6" />
    <step operation="flash" partition="tz" filename="tz.mbn" MD5="ED1C505E36E769CCF0BB3C10E46DD62B" />
    <step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="0AB29C2AC836305CC197703C1F651324" />
    <step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="5554941C30D2D489E56465DB30F42FC3" />
    <step operation="flash" partition="fsg" filename="fsg.mbn" MD5="4233256789D5F11C35B22591ED448C73" />
    <step operation="erase" partition="modemst1" />
    <step operation="erase" partition="modemst2" />
    <step operation="flash" partition="logo" filename="logo.bin" MD5="506F42184C465D9CD8BB2BD27DB77F1A" />
    <step operation="flash" partition="devtree" filename="device_tree.bin" MD5="66AD59B88203992915EAF476C9E17E58" />
    <step operation="flash" partition="boot" filename="boot.img" MD5="8BE117DF3E339FD49C457353492414BC" />
    <step operation="flash" partition="recovery" filename="recovery.img" MD5="C0274E6128C610552B351A7645E17D99" />
    <step operation="flash" partition="cdrom" filename="cdrom" MD5="8C578BC3308036F86BF30BA802E488DF" />
    <step operation="flash" partition="system" filename="system.img" MD5="4EEAB1D756FC77F357806935E5E0D60C" />
    <step operation="erase" partition="tombstones" />
    <step operation="erase" partition="cache" />
  </steps>
</flashing>


#52 Aixelsyd

Aixelsyd

    Freak on a Leash

  • Administrator
  • 640 posts
  • LocationWindy City
  • Current Device(s):x13 Dev Ed & x14 Pure Ed & Droid Turbo

Posted 24 April 2013 - 09:31 AM

your using RSD Lite 6.1.4?

Have most current Moto drivers installeed?

Putting device in AP mode before hooking up to your comp with RSD Lite open first?

I'd also suggest putting the XML file in the install location folder of RSD Lite. Sometimes RSD Lite can be picky. 



#53 aiur1

aiur1

    Member

  • Members
  • PipPip
  • 54 posts
  • LocationCalifornia
  • Current Device(s):Note 3 (SM-N900V)

Posted 24 April 2013 - 09:36 AM

I did just that, and it still came out with the same result and I do have RSD v 6.1.4



#54 aiur1

aiur1

    Member

  • Members
  • PipPip
  • 54 posts
  • LocationCalifornia
  • Current Device(s):Note 3 (SM-N900V)

Posted 24 April 2013 - 09:43 AM

Is this a good idea? "From what I understand, you can edit the XML file inside the zip file and remove the line with got_main0.bin. Save it and it should install. No guarantees, that's just what I read."

 

 

 

source: 

Please Login or Register to see this Hidden Content



#55 Aixelsyd

Aixelsyd

    Freak on a Leash

  • Administrator
  • 640 posts
  • LocationWindy City
  • Current Device(s):x13 Dev Ed & x14 Pure Ed & Droid Turbo

Posted 24 April 2013 - 09:44 AM

What does it say on the screen of the device when you manually boot it into AP mode? 



#56 aiur1

aiur1

    Member

  • Members
  • PipPip
  • 54 posts
  • LocationCalifornia
  • Current Device(s):Note 3 (SM-N900V)

Posted 24 April 2013 - 09:47 AM

AP Fastboot Flash mode (S)

10.9B(*) (sha-le9f557, 2012-10-21 17:10:35)

eMMC Info: Size 8GB

 

Device is LOCKED, Status Code:0

 

Battery OK

 

Transfer Mode:

USB Connected

 

 

 

 

 

 

 

Fastboot Reason: Flash Failure

usb connected



#57 aiur1

aiur1

    Member

  • Members
  • PipPip
  • 54 posts
  • LocationCalifornia
  • Current Device(s):Note 3 (SM-N900V)

Posted 24 April 2013 - 09:48 AM

RSD Lite also doesn't correctly recognize this information:
 
ESN: N/A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: N / A
DRM Version: N / A
 

 

 

I don't know if that matters or not



#58 Aixelsyd

Aixelsyd

    Freak on a Leash

  • Administrator
  • 640 posts
  • LocationWindy City
  • Current Device(s):x13 Dev Ed & x14 Pure Ed & Droid Turbo

Posted 24 April 2013 - 09:54 AM

Is this a good idea? "From what I understand, you can edit the XML file inside the zip file and remove the line with got_main0.bin. Save it and it should install. No guarantees, that's just what I read."

 

 

 

source: 

Please Login or Register to see this Hidden Content

 

 

No clue to be honest.  

 

Have you just tried manually fastbooting /system , /recovery, /boot and see what it does. Wont take but a few mins really as you have the files needed seeing as you have the full XML file on hand already. 



#59 Aixelsyd

Aixelsyd

    Freak on a Leash

  • Administrator
  • 640 posts
  • LocationWindy City
  • Current Device(s):x13 Dev Ed & x14 Pure Ed & Droid Turbo

Posted 24 April 2013 - 09:57 AM

 

RSD Lite also doesn't correctly recognize this information:
 
ESN: N/A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: N / A
DRM Version: N / A
 

 

 

I don't know if that matters or not

 

that is all normal so dont worry about that stuff. 



#60 aiur1

aiur1

    Member

  • Members
  • PipPip
  • 54 posts
  • LocationCalifornia
  • Current Device(s):Note 3 (SM-N900V)

Posted 24 April 2013 - 10:05 AM

How do I manually send the commands through RSD ?







Also tagged with one or more of these keywords: xt807, safestrap, no os, motorola droid razr m, help

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users