xt926 soft-brick unrooted, locked bootloader - RAZR HD Q&A, Help & Troubleshooting

I know this situation has come up in the past, but most of the essential links are broken in all threads I could find.
background: this my wife's Verizon xt926. It has never been rooted and the bootloader is locked. She applied all system updates to it, so I can only assume it is using the most recent version (which is important as the locked bootloader prevents downgrading). Several days ago it crashed, and despite multiple attempts at factory default wipes from the default recovery software, it continues to be non-functional. It boots to the Motorola M logo, but no further. Recovery options are available, but do not fix the issue.
What I have tried so far:
factory reset via recovery
fastboot restore using out of date stock rom
adb sideload using out of date stock rom (didn't even begin to work)
From what I've read, fastboot should be able to fix the issue, but I need an up to date stock rom and a working copy of RDS lite on my machine. Is that correct? Does anyone have a stock rom they can share? I've already scoured the internet and have found many helpful articles explaining the process, but none with actively working links. Most of them link to sbf.droid-developers.org, but that site gives 403-forbidden on all pages.
Thanks,
jwilson8767

jwilson8767 said:
I know this situation has come up in the past, but most of the essential links are broken in all threads I could find.
background: this my wife's Verizon xt926. It has never been rooted and the bootloader is locked. She applied all system updates to it, so I can only assume it is using the most recent version (which is important as the locked bootloader prevents downgrading). Several days ago it crashed, and despite multiple attempts at factory default wipes from the default recovery software, it continues to be non-functional. It boots to the Motorola M logo, but no further. Recovery options are available, but do not fix the issue.
What I have tried so far:
factory reset via recovery
fastboot restore using out of date stock rom
adb sideload using out of date stock rom (didn't even begin to work)
From what I've read, fastboot should be able to fix the issue, but I need an up to date stock rom and a working copy of RDS lite on my machine. Is that correct? Does anyone have a stock rom they can share? I've already scoured the internet and have found many helpful articles explaining the process, but none with actively working links. Most of them link to sbf.droid-developers.org, but that site gives 403-forbidden on all pages.
Thanks,
jwilson8767
Click to expand...
Click to collapse
I can't believe no one responded to this... Here you go man this should be everything you need http://www.droidrzr.com/index.php/topic/54379-fxz-442-1834615/

Related

[Q] Brick question

I've been doing research on this for a while, and I decided to sign up and ask about this question. Majority of the topics here dealing with bricking either have solved it because of access to fastboot, or some users have given up and either retired their devices or sent them in to ASUS.
Long story short, I installed Clockwork Recovery Mod and Cyanogen mod with no issues. After a couple of weeks, I decided I wanted to go back to stock. I did some research and found a topic which said I needed TWRP in order to flash back the stock ROM. I installed TWRP, but some things seemed to have gone awry with that install and I no longer have access to the fastboot menu and the tablet keeps booting straight into recovery.
I can load new roms by pushing them with adb, but when I try to reload the stock mod it just reboots and nothing gets installed. I tried to sideload a rom, but my version of TWRP doesn't have that feature (I have 2.2). So far, I think I can get it back on track if I could somehow install a new recovery, or start my device from scratch somehow.
Also whenever I transfer to device memory, if I reboot the tablet, everything gets erased and the log is littered with errors about not being able to find and mount /data. From what I've read, it should be solved with a simple format of the file system. However, all of my attempts to use the recovery's built in wiping/formatting tools have ended with no success. If I put in a microSD, that gets wiped as well so in order to load a ROM, I have to push it using adb.
I thought I had fully bricked it, but it seems that since it's accessible through adb, it's still somewhat fixable. I know about backing up everything with nvflash, now, I guess I just didn't do enough research before getting into this. Any ideas, feedback, is appreciated, so far I'm learning a lot about android devices from this experience.
lino4 said:
I can load new roms by pushing them with adb, but when I try to reload the stock mod it just reboots and nothing gets installed. I tried to sideload a rom, but my version of TWRP doesn't have that feature (I have 2.2).
Click to expand...
Click to collapse
Where did you dig out this ancient TWRP version? It is not compatible with the current bootloaders and cannot access the internal storage at all - that's why all your installation attempts are failing.
Read this thread, it deals with a similar problem: http://forum.xda-developers.com/showthread.php?t=2291974
_that said:
Where did you dig out this ancient TWRP version? It is not compatible with the current bootloaders and cannot access the internal storage at all - that's why all your installation attempts are failing.
Read this thread, it deals with a similar problem: http://forum.xda-developers.com/showthread.php?t=2291974
Click to expand...
Click to collapse
Yeah I found that thread not too long ago, I pushed the bootloader and was able to load the stock rom and get everything going.

In a right mess trying to return to stock

Please could someone help ! I'm trying to unlock my XT1032. I have the correct Sim-Unlock (network unlock) code from my old telco, but... it won't work because the phone is rooted, bootloader unlocked (S-ON) running CM13.
I figured that returning it to a stock build would allow me to unlock the phone, then I could re-root and return to CM13 on my new network.
However..... there are about a dozen guides on returning a Moto G to stock and the first one I tried left the phone stuck on the 'Warning: Bootloader is unlocked' message. Since then, I've tried several other guides and have got nowhere fast. I've been on this for four hours now and the only thing I seem to be able achieve is to get TWRP or CWM recovery on there by flashing from fastboot. Every other image I try either gives 'preflash validation failed' messages, sticks on the Bootloader Unlocked screen or gets it stuck in a bootloop!
I just want to switch networks... Why is this so bloody difficult ?
What Firmware did your XT1032 originally come with? or which Carrier?
Kitkat I think, and it's Tesco (UK).
I subsequently did the OTA update to Lollipop and then.... WHOAAAAA.... hold on... it's booting !!!
I don't know how, or what I've done to get this far, but the only thing I can think of that's changed is that the battery is now at 100% charge. It appears as though it's successfully flashed the 5.1 untouched ROM from http://forum.xda-developers.com/devdb/project/?id=7981#downloads
But, I've tried flashing that loads of times this evening and it's failed everytime.
Having said that it's booting, it's sitting here on the Motorola logo - and it hasn't got that far in the last five hours.... I'll be back shortly !
Update: It worked ! It completed the boot, I put the new SIM in, it asked for the unlock code and this time it worked OK. Now I'm tackling putting CM13 back on it. I think I'll stick with TWRP rather than CWM recovery, as long as TWRP can handle the automatic updating for the CM nightlies.
I have no idea what went wrong there - maybe it was just that the battery had to be at 100% ?? Who knows... Thankfully I doubt I'll be tackling that again !
I don't know if things have changed, but I would be careful with OTA Updates in CM. People have hard-bricked (phone is effectively destroyed) applying updates in this way. I also suggest you avoid official Motorola updates, rather use the factory firmware images available here: (which already include the content of OTA Updates)
[INDEX] Moto G [Falcon][Peregrine] Factory Firmware Images​
Thanks for replying anyway mate. In the end, it's all good now. Unlocked and back on CM13 and on my new network !
Ahhh... not so good after all. The phone reboots every time you try to uninstall an app. I've tried flashing back to CM12.1, the latest stable release, and it does the same, so I've obviously screwed something up along the way.
Could someone help me flatten this thing completely and get it working normally please?
I've tried reflashing loads of times, even tried Cyanogen Recovery instead of TWRP but nothing I do gets rid of this reboot problem.
Can anyone assist please?
OK, so I've followed the procedure detailed here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 and flashed the Untouched 5.0.2. EU Stock ROM successfully, but it still reboots when you try to uninstall any app.
Whatever it is that's causing this is not getting overwritten by the flashing procedures I'm using is it ?
HELP !!!!!
@aneng64 - You have not done what I told you to do. Read my post again.
Yes I did... and I still had the same problem. It was only once I stopped trying to flash zips from TWRP and used mfastboot to flash the whole set individually (non-hlos, motoboot etc) that I got it to behave. The issue, incidentally, seemed to be the same one mentioned elsewhere here that also causes settings to crash when you try to go into settings, security.
Once it was stable with a stock ROM, I was able to flash CM13 again and it's now sorted. Thanks for your help anyway.

[Completed] HTC One M9 Major Issue

I have an HTC One M9 (Sprint) software version 2.11.651.19 (OPJA2) with Android v5.1
Within the last couple months I unlocked the devices bootloader, and rooted it. Last night I left the phone under my laptop and I'm thinking it got way way way too hot, somehow the thing is still alive, however when I went to turn it on in the morning, I had no wifi or cellular capabilities. At first I assumed this was a hardware issue, however I then unrooted the device on a whim, and this fixed it (Until I turned it off again, to my dismay).
I'm thinking somehow my phone overheated (Which explains why my battery life won't go over 47%) and somehow my flash memory must have been corrupted because I can no longer boot into recovery mode, which is my serious catch 22. Since I figure this is some issue related to my firmware, which I would LIKE to reflash (This is my goal here). To my dismay, in order to flash a stock RUU or firmware to the device, you must have your bootloader relocked. However in order to relock your bootloader you must have root, and like an idiot I unrooted it. I can't reinstall SuperSU through my TWRP recovery because my phone refuses to boot into recovery mode. I attempted to re-flash TWRP to the device through download mode, the flashing is completed successfully, however I still cannot boot into my recovery. To break it down simply:
-Want to reflash stock firmware
-Must have root to reflash stock firmware/RUU
-Don't have root because I uninstalled it
-Can't re-root because my recovery is corrupted
-Can't re-flash TWRP (Already tried and it's not working)
-Can't re-root because I can't flash TWRP
-Can't reflash stock firmware because I can't disable it with root
Regardless of this I attempted to use adb and echo to relock the bootloader however instead of getting # I get $, so I'm not really able to do this either. Is there ANY way I can repair my recovery, has anyone ever run into an issue like this before? Or am I just completely screwed, hahaha.
Do you think I might be able to reflash Android V5.1 to try and fix the corruption and then maybe that would allow me to get into recovery mode so I can flash Super SU so I can at least factory reset my device with TWRP, or possible reload stock firmware and factory reset from there?
Thanks guys for any help you can provide.
*EDIT
If anyone wants to provide any advice great, but for now I'm going to try using HTC Sync Manager to load Marshmallow (v6.0) onto the HTC and see if this may allow me to actually get into recovery mode. Downloading the file from here: *nevermind can't post links yet, under 10 posts, you can find it on HTC's website* (This is for the HTC One M9, Sprint) in case anyone else EVER has to run into this awful issue, lol.
Moderators please feel free to update the thread to SOLVED status, I was able to update my phone to marshmallow to resolve the issue. This time around I WILL be backing up my phone, probably not going to root it this time around either, I have like 3 other phones so I'll just root them instead, lol. If you would like the download link I am happy to provide it VIA PM so you can update my OP with the link for the full fix. My phone is able to get wifi and texts now without an issue, unfortunately all my data is wiped but honestly I don't really care!!
Thanks everyone!
Good job on solving your issue.
If you have further questions or want to help out others, you can do so here
http://forum.xda-developers.com/sprint-one-m9/help
http://forum.xda-developers.com/sprint-one-m9
Thread closed

How to downgrade HTC U11+ from Android Pie?

Already created thread in the wrong place https://forum.xda-developers.com/showthread.php?t=3952280
I have HTC U11+ TW version. Ever since I got the Pie update, my phone is freezing a lot. I need to force restart it 10+ times a day. I tried factory reset, clear cache, etc. Nothing works. I did not have any experience with flashing, but I have been reading a lot. I have my bootloader unlocked with S-ON.
My current build number is 2.15.709.1, since I wanted to downgrade, I tried flashing stock image HTC_U11+_TW_1.24.709.999_Images_OTA using fastboot (no TWRP). My phone went into a bootloop when I did that. I think this is because I can only flash an image with the same build number? Anyway, I flashed a HTC_U11+_TW_2.15.709.1_Images_OTA image and my phone is back to where it was, Android Pie (no bootloop), but still freezing a lot.
I found the HTC_DevInfo_Tool.zip tool on this thread https://forum.xda-developers.com/u11/how-to/guide-downgrade-htc-u11-oreo-to-nougat-t3754481, but I am not sure if it will work on my phone.
Can someone advise what should I do to downgrade? Also did anyone face a similar problem after the update?
I found someone tried what I wanted to do here
https://forum.xda-developers.com/htc-u11/help/error132-signature-error-downgrade-htc-t3948079
Looks like it wont work?

(FIXED) Bootloader Locked but Device Won't Boot

I recently ran into the issue during custom rom work. I reflash the stock android ZIP, it starts booting, then I hard reset it with the power button and try to reach bootloader again. This, as it turns out, is terrible to do if you want a fast setup. The moment it starts and you reboot it, the boot image is corrupted (that's my guess) because escaping the boot screen during a clean flash bricks your phone. If you're reading this, it happened to you as well.
The answer is so flipping obvious and it took me an hour to figure it out - nowhere on the internet is there a "solution" for this problem, no matter how frequent it is. But there are lots of people who deal with this, whether still on their factory images (like the Pixel 3 EDL issue) or like me bouncing from custom to stock. So here's the answer:
ALL YOU HAVE TO DO IS SIDELOAD THE CURRENT SOFTWARE OTA OR A BETA OTA FROM ANOTHER FUTURE VERSION.
It doesn't recognize timestamps before your current software, so you'll need to assume you're on the latest of whatever you're on and do that. Future versions work as well, so if you wanted to reach 12 in one shot, your phone's bootloader would fully accept it as long as the file isn't corrupted. If you need a sideloading or flashing guide, here you go.
For me, I flashed the latest build of Android 11 (August patch) and rebooted during the boot up. What I did was download the OTA of the same exact file to my laptop, and entered adb sideload coral.xxx.x.zip. (The name of the file) It ran all the way through and it started up perfectly normal.
I hope this helps someone!
P.S. I don't have any pictures or tutorials, I only wrote this to help others understand what happened and how to fix it. Probably wouldn't have needed to say it if the forum for it existed.

Categories

Resources