Hello,
New to xda-developer forum, but was hoping I could get some help.
I have a Droid Razr M, that has had the boot loader unlocked, but not rooted anymore, after getting an update prior to kitkat. If I remember correctly I was able to get previous updates with no issues with the boot loader unlocked. Today I heard that kitkat was out for my device, so I went into settings to check for a system update and I was offered to update to 4.4.2 (Kitkat). So I went ahead and did it.
However, the problems lies now that It is stick in a boot loop, with the "WARNING BOOTLOADER UNLOCKED" message that I always got after unlocking it. I noticed after the update the boot was taking a really like time, but then I noticed it would **** off and god right back to that same message. Knew something wasn't right, Itll shut down and reboot the that screen multiple times. I first tried clearing the cache partition. Nothing. Tried resetting/wiping, that also didnt fix it.
Some help would be greatly appreciated here.
If you need more information I can try my best.
Thank you!
Related
After countless hours of research, I decided to unlock my bootloader and to root my Motorola Atrix 4G. With success, I was happy to have everything working and installed the Darkside Custom Rom. I let a friend borrow my phone, and they saw the AT&T system update and they decided to install it. They bring back the phone and the system update has finished and was installing. The phone powers off and starts to install the update. 10% into the install, it stops, and I got the little green droid man with the /!\ behind him. I take out my battery, place it back in after 30seconds. It powers on, boots up, powers off and tries to load the update again. I restart it, but this time quickly going into RomManager and starting it up in Recovery Mode. I go to restore the phone using the file I backed up from the TitaniumBackUp app, everything backs up except the system. I plug my phone into my laptop, and everything is in the folder. I performed a system/factory reset, downloaded the last Gingerbread update, but nothing helps. Anything I try to load it says "Installation aborted". No matter if it's the original update or a ROM I download. Looking up other forums, I notice others that have downloaded the Darkside ROM have had the same; if not similar issues. I apologize for the length of this message, but I wanted to put in as much detail as I could so you know exactly what the issue is. I look forward to hearing from someone, and thank you in advance!!!
You probably need to sbf it back to a stock ROM and start over. I had a similar problem when I first got my Atrix and the AT&T update first came out. I had already rooted it and didn't unlock the bootloader yet. It tried to update and bricked the phone. Got AT&T to give me another though as I had just got the thing.
nickdeal said:
You probably need to sbf it back to a stock ROM and start over. I had a similar problem when I first got my Atrix and the AT&T update first came out. I had already rooted it and didn't unlock the bootloader yet. It tried to update and bricked the phone. Got AT&T to give me another though as I had just got the thing.
Click to expand...
Click to collapse
Thanks a ton! How would I go about doing that?
You need to download motorola RSD app to you computer. Search XDA for stock firmwares and download one. You will then need to use the button combo to get in to RSD. Connect the phone to your computer and make sure it recognizes. I had an issue where one of my laptops would not recognize the phone for anything. I had to use a different laptop. Once it's done you should be back to stock. The bootloader should be unlocked still. Just root and flash your ROM of choice.
Sent from my MB860 using XDA App
Hi,
I'm a bit new here and running a good old-fashioned stock Inc 4G LTE, never rooted or flashed to new ROM. It DOES have the latest OTA update from Verizon a couple months ago.
This morning my phone suddenly went off after working OK. Then when trying to restart, I get an infinite boot loop and it won't get past the red Droid screen. I've searched various threads and tried what I think are the most obvious things, and nothing seems to help. But I want to make sure there are no other options before I throw it in the trash.
Here's what I tried:
- Tried entering Safe Mode by holding down volume key after HTC screen comes on. Makes no difference, does not enter Safe Mode.
- Get to HBOOT OK. Says 'LOCKED' and I am running HBOOT v.1.15.0000.
- - In HBOOT, I've tried running Recovery a couple times. Seems to go OK, but just starts looping when restarting.
- - In HBOOT, tried running Recovery > Wipe Cache Partition. Says cache is cleared.
- - In HBOOT, tried running Recovery > Wipe data/factory reset. Seem to go through OK.
- - In HBOOT, tried running Factory Reset.
- - In HBOOT, tried running Clear Storage.
- Pulled battery and tried spare.
- Removed SD card.
Some history - this phone has always been very sluggish. A few months ago started shutting down when doing camera intensive things (would jump to battery at critical level). So I did a factory reset a couple weeks ago and was slowly adding some of the essential apps back in. It crashed trying to upload photos to Facebook. Last night I had just moved some apps to the Phone storage and set my Sound Profile app to change profiles in the morning. This is about the time the phone crashed.
Anything else I should try before giving up?
Can I try to root and install a custom ROM to fix when in this state? Is this now possible with latest OTA update?
If custom ROM is last chance, is there a really solid one running 4.3 and Sense?
THANKS! May be time to get a HTC One or iPhoney, as I'm just not into huge phones that are coming out...
iRunNaked said:
If your on bootloader 1.15.0000 and now 1.16.0000, try using the stock Ruu and restoring the phone. If not, try rebooting in bootloader and factory reset.
If that doesn't work, gain root (if you haven't) and get s-off/unlock bootloader/CID set to 111111, and try a custom rom. If all else fails, take it back to stock and unroot/s-on/CID back to VZW/Relocked.
Call Verizon and tell them you need a replacement. The phone randomly gets real hot and reboots. They should send you a new one no problem.
I girlfriend had the random reboots, ending up getting it replaced. Now shes on her 4th or 5th incredible lte. (data Issues & random reboots)
Click to expand...
Click to collapse
I tried running a stock 2.17.. RUU, but got a "Failed" message because the software was too old. I'm guessing that is because I'm on the newer 2.19.. OTA update?!? Anyone know where to get a RUU file for the latest 2.19 version? I've been searching with no luck.
I'll have to research how to root/unlock the phone when it won't boot. Any specific threads that have fairly detailed instructions would be appreciated.
Thanks!
jethrodesign said:
I tried running a stock 2.17.. RUU, but got a "Failed" message because the software was too old. I'm guessing that is because I'm on the newer 2.19.. OTA update?!? Anyone know where to get a RUU file for the latest 2.19 version? I've been searching with no luck.
I'll have to research how to root/unlock the phone when it won't boot. Any specific threads that have fairly detailed instructions would be appreciated.
Thanks!
Click to expand...
Click to collapse
I looked at the thread about how to successfully root & flash the phone when it has the Verizon OTA update (2.19.xx) found here: http://forum.xda-developers.com/showthread.php?t=2664460.
But it appears at first glance that to do it the phone needs to be booted up and connected to the computer via USB. I can only get my phone to the HBOOT screen, nothing else.
- Can anyone confirm that to unlock and/or flash a new ROM on this phone that it has to be able to boot up? No way to do it on my phone with the 2.19 software and constant rebooting?
Thanks. It's cosmetically perfect, so I feel bad about throwing it away. If I can get it back up somehow I could at least sell it or give it to someone in need.
jethrodesign said:
I looked at the thread about how to successfully root & flash the phone when it has the Verizon OTA update (2.19.xx) found here: http://forum.xda-developers.com/showthread.php?t=2664460.
But it appears at first glance that to do it the phone needs to be booted up and connected to the computer via USB. I can only get my phone to the HBOOT screen, nothing else.
- Can anyone confirm that to unlock and/or flash a new ROM on this phone that it has to be able to boot up? No way to do it on my phone with the 2.19 software and constant rebooting?
Thanks. It's cosmetically perfect, so I feel bad about throwing it away. If I can get it back up somehow I could at least sell it or give it to someone in need.
Click to expand...
Click to collapse
If you want to use mdmower's "temp-root" trick, then you'll need to be able to access the device through Android Debug Bridge. Can you see the device if you type
Code:
adb devices
after booting up past the bootloader?
stringedonbass said:
If you want to use mdmower's "temp-root" trick, then you'll need to be able to access the device through Android Debug Bridge. Can you see the device if you type
Code:
adb devices
after booting up past the bootloader?
Click to expand...
Click to collapse
Hi. I've never tried running ADB. Not very familiar with it at all. But my phone will not boot past the HBOOT option. No matter what I've tried, it will just go into a rebooting loop. I'm assuming it needs to be fully booted up to work with ADB?!?
- Is there an RUU for the latest software update (2.19.xx) somewhere that I can try running to see if it will help it fully boot?
- Any other options?
Thanks!
jethrodesign said:
Hi. I've never tried running ADB. Not very familiar with it at all. But my phone will not boot past the HBOOT option. No matter what I've tried, it will just go into a rebooting loop. I'm assuming it needs to be fully booted up to work with ADB?!?
- Is there an RUU for the latest software update (2.19.xx) somewhere that I can try running to see if it will help it fully boot?
- Any other options?
Thanks!
Click to expand...
Click to collapse
Yes, my understanding is that to use adb, you need to be able to boot into the OS with usb debugging turned on. Hopefully someone will come along with a worthwhile response!
Is anyone aware of more current RUU's than are menteioned here?
http://forum.xda-developers.com/showthread.php?t=1770978
---------- Post added at 05:19 PM ---------- Previous post was at 05:07 PM ----------
If the phone failed as a completely stocked phone, why not try returning as opposed to figuring out how to root a broken phone?
So, to start off, I messed up big time...
I'll give you the short version, but try to provide as much info as possible. I switched roms a few times in the last few days, going from Trents 8, to the newest Dirty Unicorns, to Trents 10 (where I started having issues) back to DU. I was trying to figure out where the issues came from, and came across someone saying that going from a touchwiz based rom, off of it, and back on, can cause problems. I then read that one of the best ways to fix this was to flash stock firmware and reflash new roms. I tried doing this...
Little did I know, it was a HUGE mistake for me to flash the 4.3 firmware through odin, and when the phone restarted, the "Galaxy Note II" page just kept flashing on and off for a few minutes. I think tried flashing older firmwares, with pit file, but I kept getting errors when I restarted saying that I didn't have Verizon Authorized Software.
Sooo this is where I'm stuck right now. I can't boot the phone at all, and when I try to flash the root66 firmware (the one that's supposed to fix everything?) I still get this verizon unauthorized page. It seems from what I've read that the bootloader relocked because of my 4.3 flash, and I can't find any info on how to unlock that. Anyone have suggestions? I'd really appreciate it!
Update: I retried the 4.3 firmware, and right now "Android is upgrading..." so I'm assuming this means my bootloader is locked, I've lost root, and all that jazz right? From what I've read so far there isn't any way to unlock the bootloader again, am I right? If so, can you point me in the right direction? Much appreciated!
xanderharris86 said:
So, to start off, I messed up big time...
I'll give you the short version, but try to provide as much info as possible. I switched roms a few times in the last few days, going from Trents 8, to the newest Dirty Unicorns, to Trents 10 (where I started having issues) back to DU. I was trying to figure out where the issues came from, and came across someone saying that going from a touchwiz based rom, off of it, and back on, can cause problems. I then read that one of the best ways to fix this was to flash stock firmware and reflash new roms. I tried doing this...
Little did I know, it was a HUGE mistake for me to flash the 4.3 firmware through odin, and when the phone restarted, the "Galaxy Note II" page just kept flashing on and off for a few minutes. I think tried flashing older firmwares, with pit file, but I kept getting errors when I restarted saying that I didn't have Verizon Authorized Software.
Sooo this is where I'm stuck right now. I can't boot the phone at all, and when I try to flash the root66 firmware (the one that's supposed to fix everything?) I still get this verizon unauthorized page. It seems from what I've read that the bootloader relocked because of my 4.3 flash, and I can't find any info on how to unlock that. Anyone have suggestions? I'd really appreciate it!
Update: I retried the 4.3 firmware, and right now "Android is upgrading..." so I'm assuming this means my bootloader is locked, I've lost root, and all that jazz right? From what I've read so far there isn't any way to unlock the bootloader again, am I right? If so, can you point me in the right direction? Much appreciated!
Click to expand...
Click to collapse
No, the bootloader can't be unlocked. You can at least get root with saferoot on 4.3.
Or downgrade with mobile tech videos
I bought my Moto X Pure used, and the "bootloader unlocked" message pops up everytime I boot up. However, a new security update came out this morning. But, when the update tries to re-boot, I get the TWRP main screen. The update never takes hold and keeps trying to re-boot. Which brings up the TWRP screen over and over. I've never rooted or worked with custom ROMs, so I'm in the dark here. Any ideas how I get out of TWRP Hell? Thanks.
rsdin559 said:
I bought my Moto X Pure used, and the "bootloader unlocked" message pops up everytime I boot up. However, a new security update came out this morning. But, when the update tries to re-boot, I get the TWRP main screen. The update never takes hold and keeps trying to re-boot. Which brings up the TWRP screen over and over. I've never rooted or worked with custom ROMs, so I'm in the dark here. Any ideas how I get out of TWRP Hell? Thanks.
Click to expand...
Click to collapse
Hi,
Your device is on Twrp Recovery, so official stock OTA's won't get installed via custom recovery like TWRP.
They requires stock recovery. Due to scripts / modifications etc..
Meanwhile, ive found this for you, follow that and fix your device.
Good luck!!
So it has been a VERY, VERY, long time since I attempted to root a device. I admit, that I completely forgot most of what I knew from back in the day rooting like the Motorola OG Droid. Here's the deal. I tried rooting a USC XT1526 and I had no idea what I was doing. I followed the steps through and managed to install TWRP and SU. So I assume I got full root. Well The issue started after I got an UPDATE AVAILABLE message and tried to go through with the OTA Update. When it got to the point of installing the OTA Update, my device turned off like normal but instead of updating, it booted into TWRP recovery. It didn't update at all and when I booted my phone normally, it kept trying to update so my phone turn off (loop) every time it tried to install the update. I did a factory reset and it stopped rebooting. I later tried to flash back to fully stock but I believe I might have downloaded the wrong file because I now have a device with no WiFi. Can someone please help me.