New Droid Razr MAXX.
OTA Updated to ICS. Rooted with Droid RAZR Utilities 1.40. Installed Bootstrap and recovery, made a backup. Was looking to install a ROM, saw one saying I needed Safestap. Uninstalled Bootstrap, installed Safestrap using Utilities 1.40. Ran Safestrap, Installed recovery, rebooted, enabled Safe-system. Rebooted. I have a black screen, nothing happens when I push and hold any buttons. I have a brick as far as I can tell. Any suggestions? What did I do wrong?
Ok. Holding key combos got it to reboot with vol-down and power. If I let it go past the safeboot splash without hitting anything it goes black.
Went back into recovery, disabled safe-system, reboot and and it works ok.
How can I get into safe-system and flash a this rom? Did I do something wrong in the process?
Use 1.81 utility to flash stock 211 and start over. Install superuser/root and busybox then install safe strap and install recovery. From there make a backup and then enable safe mode. Use rom that you put on external SD card and install. Wipe data before booting new rom.
SHVR MAXX
Related
I am currently trying to flash my vibrant back to stock 2.2. My latest attempt was done using the AIO tools. Every method I have tried has lead to the Vibrant boot screen appearing for a few seconds, and then rebooting. Any suggestions?
Have you tried Odin?
Sent from my SGH-T959 using XDA
whatever5 said:
Have you tried Odin?
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
Yes, I have tried Odin with and without AIO tools. In all of the threads I have looked at, the answer seems to be flash back to 2.2 stock, but that is what I am trying to do. Thanks.
Try to boot into recovery and factory reset and see if that breaks the bootloop. If not, see below.
*********
Do you have a nandroid backup of the 2.2 you were on an using? If so, I suggest Odin-ing to stock (2.1), then pull the CWR from my signature put it on your internal card and label it Update.zip. Boot into recovery and hit Reinstall Packages. It will cycle through and you'll have to hit it again. It will cycle through again and your stock (blue) recovery will go to CWR (green). From there you can restore your nandroid backup of the 2.2 you last made (or should have).
You can go to 2.1 using the toolbox, as it has the correct pit/tar files to do so.
Woodrube said:
Try to boot into recovery and factory reset and see if that breaks the bootloop. If not, see below.
*********
Do you have a nandroid backup of the 2.2 you were on an using? If so, I suggest Odin-ing to stock (2.1), then pull the CWR from my signature put it on your internal card and label it Update.zip. Boot into recovery and hit Reinstall Packages. It will cycle through and you'll have to hit it again. It will cycle through again and your stock (blue) recovery will go to CWR (green). From there you can restore your nandroid backup of the 2.2 you last made (or should have).
You can go to 2.1 using the toolbox, as it has the correct pit/tar files to do so.
Click to expand...
Click to collapse
I currently can not get into recovery mode. I am holding the power, vol+, and vol- buttons, inserting the battery and then releasing them when the vibrant screen appears. But it just continues to boot cycle.
I flashed the pit and tar that came with AIO tools. No go. Still just boot cycles. Sorry for being a pain.
I do have a backup, but I am not sure what I can do with right now.
Try turning the phone off, plug in USB hold just volume up and power on the phone..... that should put it into download where you can run Odin and flash back to stock
Sent from my touchpad using XDA
related problem (sort of)
Solved: problem solved. I reflashed CM7 over the bootlooping mess, and it took. Then I was unable to get AIO Vibrant Toolbox to recognize that debugging mode was on, even though it was. So I just copied the files over and went through a massive round of forcing the zip files on again and again. I now have Slim 3.5 on my phone, so I can start playing with it.
*****************************************
I'm an extreme noobie, trying to upgrade my T959 to ICS. I've picked Slim 3.5 (latest release version as of this week) as my first attempt (but really any simple but well-functioning ROM will do for me).
I've rolled back to Eclair (from the official Tmo Froyo upgrade way back when), rooted, and numerous times followed various directions to install the zip for Slim -- sometimes trying CM7 as an intermediate step. The CM7 install failed in the same way as the ICS, as described below.
I've done it with and without AIO Vibrant Toolbox. I've used ClockworkMod Recovery 2.5.1.2 to wipe the data, clear both cache partition and Dalvik cache, and format system. I've popped the zip file in various folders and at toplevel, both external and internal SD.
In all cases, it gets off to a good start, and then I'm left with endless bootlooping: Vibrant logo, Mod logo, a textblock of about 15 lines, repeat. I've always been successful after that in using Odin3 v1.81 to get back to Eclair.
I got sucked into a tech vortex until 4:30 am last night trying again and again, and I'm way way too old for that!
Any thoughts?
Just to be clear for this somewhat newbie... I'm on Eclipse ROM which is based on .173. When (if?) the ICS is released and I want to go back to stock+root so I can get the OTA this is what I do:
0) Make a backup of Apps+Data with Titanium Backup
1) Download Matt's Razr Utility 1.6 (fastboot .181 included)
2) Turn off my phone.
3) Turn on my phone with Power+Vol Dn+Vol Up all buttons pressed at once. When menu appears scroll down with "vol dn" to "AP Fastboot" and then select by pressing "Vol Up".
4) Plug phone into computer with USB.
5) Run Matt's Util and select option #1 to fastboot to .181 (can I do this even tho I am on a .173 based ROM?)
5a) Will this wipe out Bootstrapper? Will there be a need for bootstrapper or should I wait until after I OTA to ICS?
6) Root with utility
7) Run Voodoo OTA rootkeeper and protect root.
8) OTA
9) Restore Root (with fingers crossed?)
10) restore apps+data with Titanium Backup.
10 steps to a new me?
If you are running a custom rom on GB-Kernel you don't have to restore using that tool. Just flash any GB 2.3.6 stock rom via RSD.
Well, if thats easier, I was just looking for ease of returning to stock. I'm not sure how to flash a stock rom with rsd. I flashed the Eclipse with bootstrapper and cwm recovery.
Looking at the "stock ROMs" thread here I see only a .748 as the latest stock rom under "fastboot". Would I flash this one?
Yes, the utility will wipe out bootstrap. As well as your internal storage, so make a backup.
After fastbooting, some people have had to wipe data/cache to have a stable boot, but you can do this from within the utility.
Instead of reinstalling bootstrap / safestrap, wait until you've upgraded via OTA. The hijack will cause the update to fail.
Everything else seems correct and sufficiently thorough to ensure a clean upgrade to ICS since we won't have the luxury of fastboot if the patches are dirty bc of system mods.
Best to fastboot while on GB to be sure you're starting with a perfectly stock base.
[ ...paths? ... where we're going we don't need... paths. ]
Followed my own instructions to the letter and am on 181 rooted awaiting ICS with baited breath.
Thought i would ask tho, when restoring my TitaniumBackup I accidentally told it to restore the bootstrapper app. does this mean I gotta do this all over again?
Shinare said:
Followed my own instructions to the letter and am on 181 rooted awaiting ICS with baited breath.
Thought i would ask tho, when restoring my TitaniumBackup I accidentally told it to restore the bootstrapper app. does this mean I gotta do this all over again?
Click to expand...
Click to collapse
Nah - just uninstall the bootstrap app. The app just being installed doesn't do anything. You have to "install bootstrap recovery", grant su permissions, THEN it'll modify your system. But the app just being installed does nothing. Shouldn't mess with your upgrade to ICS,
[ ...paths? ... where we're going we don't need... paths. ]
Thank you!
Ok, so I am running android version 2.3.4 and I wanted to flash cyanogen 10 mod. so I rooted my phone, checked with root checker to make sure it was rooted, then I tried to install with the stock recovery. To find out I couldn't because of the stock recovery not allowing me to. So I got the DX2 bootstrapper, allowed super user permissions, then I tapped the recovery mode button. The phone just boots normally with no recovery screen. help?
Noobly said:
Ok, so I am running android version 2.3.4 and I wanted to flash cyanogen 10 mod. so I rooted my phone, checked with root checker to make sure it was rooted, then I tried to install with the stock recovery. To find out I couldn't because of the stock recovery not allowing me to. So I got the DX2 bootstrapper, allowed super user permissions, then I tapped the recovery mode button. The phone just boots normally with no recovery screen. help?
Click to expand...
Click to collapse
When you say DX2 bootstrapper, are you talking about CWM Recovery? That's the app I've seen used the most for flashing/backups/etc. I'd highly recommend using that one if you're not already.
You can find download links here: http://forum.xda-developers.com/showthread.php?t=1169677
After installing the app, run it from your app drawer and follow the onscreen instructions:
Press "Install Recovery"
Wait for the "Success" popup
Plug your phone into a wall charger (very important)
Press "Recovery Mode"
Wait for phone to boot into recovery, then proceed as normal.
If you've already tried this, and it's still not working, I'd look into how you rooted. I know using the zergrush method doesn't work as well as Pete's (or at least that's been my experience).
it's not really cwm recovery, it's dx2 system recovery, works almost the same
cwm doesn't work on dx2
Sent from my XT862 using xda premium
I assume he means the Bootstrap Recovery for the Droid X2. Thats the correct file. I'm surprised no one has mentioned this, but when you reboot, make sure your phone is plugged into the wall. You HAVE to have it plugged it for it to work.
EDIT: Never mind, someone did say that. But I would think that would be your problem.
Alright have a razr maxx I'm running 98.72.16.xt912.verizon.en.US jelleybean build 9.8.20-72_VZW-16. I rooted using razr blade and then installed
Cwm touch black edition. Now everytime I reboot I get stuck in a encryption unsuccessful error screen. I have tried using Matt's utility
And that gets the phone back to a usable state as long as I don't reboot or the battery doesn't die if that happens it will boot back into the encryption error. Cwm recovery put some files on the internal SD and I think that's what is causing the problem but I can't seem to delete them they are in a folder named bmm. Does anyone know what I can do to get this fix I've tried everything that I could think of but nothing is working.
I decided to flash a factory image since the GPS was not working anymore with whatever ROM I tried, plus random problems. The phone was previously set up with CM10.1 and BMM.
Installed RSD Lite, Moto drivers, downloaded several stock ROMs.
From the factory recovery mode I cannot flash any of those zip files so I proceed with RSD lite. I flashed "9.8.2O-124_SPUEM-14_S7_USASPDRICS01O2UKE1007.0R_USASPDRJBO2GB_P013_A012_p2b_S1FF_fb.xml.zip" which is a retail UK JB image. The phone shows the very first boot screen (red logo) and then the screen goes blank. The computer still sees an MTP device, though only in device manager.
I've tried installing other images but they are an older type (ICS I guess, 01.6.7.2-180&01.6.5.1-167) and RSD shows an error while trying to flash the first file from the archive.
Oh, I still have the "Customer error: contact dealer" on the first boot screen, I think this was from a ICS to JB upgrade with CID deletion(?).
I've already flashed twice using RSD, deleted cache+data, rebooted and left the phone to start up for ten of minutes, don't know what to do. RSD lite reports that flashing was ok.
been there
brainwash123 said:
I decided to flash a factory image since the GPS was not working anymore with whatever ROM I tried, plus random problems. The phone was previously set up with CM10.1 and BMM.
Installed RSD Lite, Moto drivers, downloaded several stock ROMs.
From the factory recovery mode I cannot flash any of those zip files so I proceed with RSD lite. I flashed "9.8.2O-124_SPUEM-14_S7_USASPDRICS01O2UKE1007.0R_USASPDRJBO2GB_P013_A012_p2b_S1FF_fb.xml.zip" which is a retail UK JB image. The phone shows the very first boot screen (red logo) and then the screen goes blank. The computer still sees an MTP device, though only in device manager.
I've tried installing other images but they are an older type (ICS I guess, 01.6.7.2-180&01.6.5.1-167) and RSD shows an error while trying to flash the first file from the archive.
Oh, I still have the "Customer error: contact dealer" on the first boot screen, I think this was from a ICS to JB upgrade with CID deletion(?).
I've already flashed twice using RSD, deleted cache+data, rebooted and left the phone to start up for ten of minutes, don't know what to do. RSD lite reports that flashing was ok.
Click to expand...
Click to collapse
Did you erase CID?
if you did yo need to boot in a different way
U did a factory reset in stock recovery? U cannot flash a ics image after flashing jb via rsd. Try again jb EU image than go to stock recovery and perform the wipes
Tapped from my RazR
Got it "fixed", finally. I had to go back into the stock boot/recovery menu and choose "BP Tools", last option from the menu and then it booted normally.
I still have to do this after each reboot because it boots to the black screen: hold the three buttons together until it flashes (which means a hard reboot), let go of the power button, press power button again while the other two are still pressed.
On the plus side the GPS started working again after factory reflash which it was kind of expected since the same chip is providing also WiFi and bluetooth which were running fine.
I have a root question: the device was rooted with the virtual machine procedure but after a factory reset the root was lost. I had saved it using Voodoo RootKeeper and the app shows: superuser installed, device rooted, /system supports root protection, protected su available. The "root permission granted" checkbox is disabled though and no application is able to retrieve the root. The su binary is in both /bin and /xbin so I don't understand how it can not function.
Edit: ok, got it, the su binary has -rwsr-sr-x and the owner is root so random users cannot execute it. I also cannot change the permissions so I probably have to root again and figure out a way to keep the root after a factory reset. It makes sense to install BMM since it can take care of permissions.