Database Info

[Q] How do I unbrick my phone?

So tonight I began the process of unlocking my phone and installing a custom ROM. I unlocked my phone successfully with the toolkit and was able to get into recovery and begin flashing my first ROM (Cyangogen 10 most recent nightly along with the Gapps). However on my first reboot after flashing the room, I started to realize something was awry when after 20-30 minutes it was still on a boot screen. I proceeded to try and reflash the ROM 2 more times with no real change in outcome. Whenever I tried booting out of recovery I would get a warning stopping me saying that no OS was installed, despite having clearly flashed a new ROM. Okay, so as a last ditch effort I went into the bootloader mode and enabled fastboot so that I could try the RUU - which of course failed despite 2-3 attempts at using the utility. After the RUU failures I also noticed that my SD card would no longer mount unless I manually formatted it - which I finally gave in to and was able to load another custom rom (Jellybam this time) which also would get stuck on the boot screen despite successfully flashing. So now I'm basically stuck in a limbo land where no custom ROM will boot into the OS and the RUU to take me back to stock has failed. Any suggestions on how to get out of this? (I've read in other places that you can use fastboot to flash files in the bootloader but my attempts at doings this have also been unsuccessful - if this is the route to go can anyone give me some specific instructions on how to do it?)
Thanks in advance guys.
Phone Specifics - AT&T HTC One X, 16gb running the 2.2 firmware on Android 4.04 before I got into all this nonsense.

Dissentire77 said:
So tonight I began the process of unlocking my phone and installing a custom ROM. I unlocked my phone successfully with the toolkit and was able to get into recovery and begin flashing my first ROM (Cyangogen 10 most recent nightly along with the Gapps). However on my first reboot after flashing the room, I started to realize something was awry when after 20-30 minutes it was still on a boot screen. I proceeded to try and reflash the ROM 2 more times with no real change in outcome. Whenever I tried booting out of recovery I would get a warning stopping me saying that no OS was installed, despite having clearly flashed a new ROM. Okay, so as a last ditch effort I went into the bootloader mode and enabled fastboot so that I could try the RUU - which of course failed despite 2-3 attempts at using the utility. After the RUU failures I also noticed that my SD card would no longer mount unless I manually formatted it - which I finally gave in to and was able to load another custom rom (Jellybam this time) which also would get stuck on the boot screen despite successfully flashing. So now I'm basically stuck in a limbo land where no custom ROM will boot into the OS and the RUU to take me back to stock has failed. Any suggestions on how to get out of this? (I've read in other places that you can use fastboot to flash files in the bootloader but my attempts at doings this have also been unsuccessful - if this is the route to go can anyone give me some specific instructions on how to do it?)
Thanks in advance guys.
Phone Specifics - AT&T HTC One X, 16gb running the 2.2 firmware on Android 4.04 before I got into all this nonsense.
Click to expand...
Click to collapse
You know you also have to relock the bootloader before you RUU Right?
and if your on hboot 1.14 you have to flash the boot img separately from the zip(in the folder you put fastboot,adb,etc.)

WhatTheAndroid? said:
You know you also have to relock the bootloader before you RUU Right?
and if your on hboot 1.14 you have to flash the boot img separately from the zip(in the folder you put fastboot,adb,etc.)
Click to expand...
Click to collapse
I was forgetting to relock the bootloader, thanks man. Was able to go back to stock, restart the process and am now rocking CM10. This is why I love XDA.

Dissentire77 said:
I was forgetting to relock the bootloader, thanks man. Was able to go back to stock, restart the process and am now rocking CM10. This is why I love XDA.
Click to expand...
Click to collapse
Sounds like a thanks button click is on order for WhatTheAndroids post to you
ViperXL 2.4.0 w/ElementalX 3.1 kernel

[Q] xt926 CM10.2 Stuck on Boot Logo After 1st Reboot

xt926 with unlocked bootloader and can run 10.1 nightly from get.cm with no problem. However, when I install a 10.2 nightly - whether from get.cm, epinter, dhacker or skrilaz - even though the initial boot comes up clean, rebooting after the initial boot gets stuck on the boot logo.
I have tried different recovery images - cwm, twrp, oudhs - and different versions of each.
I have tried clean installs, full formats and dirty upgrades from 10.1.
I have tried multiple force boots from this state (power+vol up).
I have tried with and without the updated gapps and UPDATE-SuperSU-v1.51.zip.
Restoring from backup does not get past this hang. The only way out is to revert to stock (I use mattlegroff's DROID_RAZR_HD_Utility_1.21).
Does anyone have any idea how I might get past this or even get a log?

Only thing that fixed this for me was to flash back to stock 4.1.2, flash newest CWM touch recovery, then flash newest nightly, Gapps, and SU. Then, a popup comes up saying something about the ROM wants to flash your boot image, and asks if you'd like to fix this. I answered YES (fix) and been working since.

Any chance you could link where you got your recovery and SU?
Much appreciated.

Same issue here...
I've also tried everything listed above. I've done everything i can possibly think of to get cm 10.2 on my xt926. For some reason my phone just isn't making it after the first reboot. I've searched and found similar issues but none of the troubleshooting has been working for me. I hope to find a way around this. I need that 10.2!

Same issue here. Not just CM, every 4.3 based ROM I've tried has either failed to boot or failed to boot more than once (more often than not, they won't boot at all).
I've been at this for hours, but I've had no success so far. I'll let you know if I come up with anything.
EDIT:
Here's my setup:
After every try, I flash back to stock 4.1.2 with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml. I've edited it so it doesn't flash the stock recovery and so it flashes a modified logo that doesn't show the bootloader warning. Partway through, I booted up and updated to the latest OTA, so I had to comment out the tz.mdm files as well. I was using TWRP 2.2.2.1, but I updated to 2.6.0.0 earlier.

GeorgeHahn said:
Same issue here. Not just CM, every 4.3 based ROM I've tried has either failed to boot or failed to boot more than once (more often than not, they won't boot at all).
I've been at this for hours, but I've had no success so far. I'll let you know if I come up with anything.
EDIT:
Here's my setup:
After every try, I flash back to stock 4.1.2 with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml. I've edited it so it doesn't flash the stock recovery and so it flashes a modified logo that doesn't show the bootloader warning. Partway through, I booted up and updated to the latest OTA, so I had to comment out the tz.mdm files as well. I was using TWRP 2.2.2.1, but I updated to 2.6.0.0 earlier.
Click to expand...
Click to collapse
one of 2 things should fix this problem,
use cwm 6.0.3.5 from here or
go to recovery/mounts and storage and format the data-media line (i know it says sd card but its internal, do not format the external ed card line or you will loose data on it)
also i updated matts utiliity to the latest ota, so you dont have to take the ota just to get the baseband. its in the dev forum. i will be updating it to a newer version if you wait until later, with the newest recoveries.
edit, btw 2.6.0.0 is not the latest twrp although i recommend using cwm as some have had issues with twrp including me.

First off, the latest TWRP seems to have fixed the problems (for me, anyway). Second, you'll need to use the most up-to-date GAPPs when you flash. Also, a lot of people have noted that mounting sytem prior to doing their wipes has solved the reboot issues.

Thanks a ton for the help. Flashed latest CWM and bumped up to 4.4 and everything's working fine. I appreciate the help!

problem flashing roms on moto g xt1032

Hi, I'm new to flashing roms and after installing CWM 6.0.4.7 on my xt1032 and rooting whenever i try to flash a rom it gets stuck in the boot animation. I have tried CM 11 Carbon rom and paranoid android. I don't know if I'm using the wrong GAPPS or what. Please help.

Gapps are not the problem:the same thing was happening to me. The real problem is the bootloader: if you are on kitkat, you have to revert to stock jelly bean (4.3), install custom recovery (for JB), root and flash the custom rom you desire. That's the only way that worked for me.
Sent from my falcon using xda app-developers app

skorpionvenom said:
Gapps are not the problem:the same thing was happening to me. The real problem is the bootloader: if you are on kitkat, you have to revert to stock jelly bean (4.3), install custom recovery (for JB), root and flash the custom rom you desire. That's the only way that worked for me.
Sent from my falcon using xda app-developers app
Click to expand...
Click to collapse
Ok thanks, I will try that when i have some free time. And how do you revert back to 4.3
never mind i found a post on how to testing now

Brick?
skorpionvenom said:
Gapps are not the problem:the same thing was happening to me. The real problem is the bootloader: if you are on kitkat, you have to revert to stock jelly bean (4.3), install custom recovery (for JB), root and flash the custom rom you desire. That's the only way that worked for me.
Sent from my falcon using xda app-developers app
Click to expand...
Click to collapse
I tried o revert to 4.3 but when flashing boot.img it said hab check failed for boot and now when i try to boot up it goes to the unlock booloader warning turns off and repeats. I can get back to fastboot but when i try to enter recovery it shows a broken android lying sideways. I think i bricked my phone. I really need help

Go back to Stock and start from Scratch.
As long as you can enter fastboot you should be fine.

I too have suffered with this problem, today i have done as above said, reflashed 4,3 but when i onstalled the cwm 4.3 version i still suffered the same problem, so i tried the cwm4.4 and hey presto, i now have cm11 on my phone, yee haaa

A Wild Willis said:
I tried o revert to 4.3 but when flashing boot.img it said hab check failed for boot and now when i try to boot up it goes to the unlock booloader warning turns off and repeats. I can get back to fastboot but when i try to enter recovery it shows a broken android lying sideways. I think i bricked my phone. I really need help
Click to expand...
Click to collapse
Try this,when you get to the broken android follow the instructions in the link below for "external reset" this will reset your phone.
https://motorola-global-portal.cust..._detail/a_id/97329/p/30,6720,9050/action/auth
if that fails just flash a stock 4.4 image with fastboot using one of the guides.

Worked
quizmaniac said:
Try this,when you get to the broken android follow the instructions in the link below for "external reset" this will reset your phone.
https://motorola-global-portal.cust..._detail/a_id/97329/p/30,6720,9050/action/auth
if that fails just flash a stock 4.4 image with fastboot using one of the guides.
Click to expand...
Click to collapse
Yes thank you so much I'm back on 4.4.2 You guys are great

hello everyone
I have a question about PaulOBrien superboot root method (look in modaco forum the moto g root method 1).
I have a 16GB Moto G and updated to Kitkat via OTA.
yesterday I used the method 1 (superboot) on windows 7, to root my phone, and run it for the first time and ended on a black screen with green bars (supposedly normal). I power off the phone and turned on and load kitkat normally and noted that the phone was not rooted.
y tried the method for a second time and have the same results (ended on a black screen with green bars), but when kirkat launched, on the initial screen i saw a message "System UIDs Inconsistent. UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable." and the system didn't respond.
I performed a factory reset via stock recobey and kitkat showed the same message but let me in the "i´m feeling lucky button" worked this time. there I noticed that my device was now rooted but non app was able to access the internal memory due to some r/w permissions as I think, because when I try to copy files to the phone via USB cable, I get have the same denial, even whit ADB push i get the same message of permissions denial.
I need a way to solve this because in this actual stage the phone works but the apps have like no access to the memory making them unusable,
for example i cannot take a picture, or download a file, for some reason all google apps not work or force close every time.
I need a way to upload a .img file to the phone in order to perform a recobery or to make a fresh install via fastboot, donn't know how to make the phone let me wrhite files on it. :crying:
(note: sorry for my bad English)

A Wild Willis said:
I tried o revert to 4.3 but when flashing boot.img it said hab check failed for boot and now when i try to boot up it goes to the unlock booloader warning turns off and repeats. I can get back to fastboot but when i try to enter recovery it shows a broken android lying sideways. I think i bricked my phone. I really need help
Click to expand...
Click to collapse
As long as you can enter the bootloader you haven't bricked anything!!! so don't you worry!
I have two questions: when did you download the stock rom, did you check the MD5 ??? Are you sure that it wasn't a bad download ?
Additionally: are you sure that you have downloaded the appropriate ROM? Did you try to flash any other ROM?

will8578 said:
I too have suffered with this problem, today i have done as above said, reflashed 4,3 but when i onstalled the cwm 4.3 version i still suffered the same problem, so i tried the cwm4.4 and hey presto, i now have cm11 on my phone, yee haaa
Click to expand...
Click to collapse
i'm having troubles too...
tried to install custom roms (c-rom and liquid rom), coming from 4.4 (unlocked and rooted) stock but it stays at the bootanimation.
flashed a stock 4.3, rooted installed, tried 2 recoveries (cwm and twrp), tried c-rom once more...
same problem :crying:
i've run out of options, so have to flash a stock 4.4 again, unless someone gives me thé idea what i can do to make it work.
xt1032

dreezz said:
i'm having troubles too...
tried to install custom roms (c-rom and liquid rom), coming from 4.4 (unlocked and rooted) stock but it stays at the bootanimation.
flashed a stock 4.3, rooted installed, tried 2 recoveries (cwm and twrp), tried c-rom once more...
same problem :crying:
i've run out of options, so have to flash a stock 4.4 again, unless someone gives me thé idea what i can do to make it work.
xt1032
Click to expand...
Click to collapse
I am having the same issue. I got this xt1032 after it was OTA upgraded to Lollipop 5.0.2 and I downgraded it to KitKat 4.4.4 Stock. Now I'm also getting stuck on the boot animations on every Custom ROM I try to flash on it.
Does anyone know if having the bootloader upgraded due to the Lollipop update has anything to do with this? mine is at Ver. 41.18.
EDIT: I was finally able to flash after Formatting Data from Recovery. Keep in mind this will basically delete everything from the internal storage and you need to put everything back there manually. Always make sure you backup your info/apps/music/fotos before Formatting Data.

[Q] Flash to stock 4.4.2 issues

I am currently trying to flash into stock rom 4.4.2. Everything is set up and i run flash-all.bat everything is fine until it finishes flashing the radio. After that it hangs when flashing image-hammerhead-m7864a-etc. for a while. I restart and trying doing it manually with each .img. I succesfully flash recover and boot and userdata.img, but system and cache seem to hang also. The cmd window never reaches the second ok and just sits there. Am i not waiting long enough or is there something wrong. The phone is responsive in the bootloader during the waiting, and there is no downloading, writing, or erasing message at the bottom.

How much time are you giving it? Some of then take a couple of minutes
Sent from my Nexus 5

jd1639 said:
How much time are you giving it? Some of then take a couple of minutes
Sent from my Nexus 5
Click to expand...
Click to collapse
I have waited up to half an hour, with no success.
I tried flashing the 4.4 image instead as my nexus5 is rev 11, supposedly before 4.4.2, but still the same problem. At one point it said out of memory error, so i flashboot formated the userdata and cache, but still hangsafter flashing radio. Some parts of the image-hammerhead zip are getting flashed, as a second cmd window pops up and runs, but as soon as that finishes and closes, the flash-all.bat is still stuck.
Edit: After getting stuck at this point, is it possible to flash an image correctly through stock recovery?
Edit2: fastboot -w update image-hammerhead-krt16m.zip seems to close when trying to flash system.img before it finishes, sometimes leaving the bootloader stuck in downloading.

apocalypserisin said:
I have waited up to half an hour, with no success.
I tried flashing the 4.4 image instead as my nexus5 is rev 11, supposedly before 4.4.2, but still the same problem. At one point it said out of memory error, so i flashboot formated the userdata and cache, but still hangsafter flashing radio. Some parts of the image-hammerhead zip are getting flashed, as a second cmd window pops up and runs, but as soon as that finishes and closes, the flash-all.bat is still stuck.
Edit: After getting stuck at this point, is it possible to flash an image correctly through stock recovery?
Click to expand...
Click to collapse
Yes with unlocked bootloader.
What problems did you have before wanting to flash stock images?

GUGUITOMTG4 said:
Yes with unlocked bootloader.
What problems did you have before wanting to flash stock images?
Click to expand...
Click to collapse
Is there an image of stock 4.4 or 4.4.2 someone could post here, i can only fined .tgzs.
I wanted to reflash to stock because my gps was unable to lock on any satellites, even after trying topntp along with gps status. I read in PA forums that some were having issues with that rom and gps, and that stock worked fine. I pretty much flashed to pa right after i got the phone last week, and never really tried gps under stock. I wanted to reflash to stock to check gps if it works, other wise I was going to RMA and hope for a newer batch (mine is from November, supposedly 312k batch works perfect gps wise).
Edit: found a stock zip: http://forum.xda-developers.com/showthread.php?t=2676691
Downloading and will flash when its ready
Edit: zip did not work (incorrect header/footer?) going to try flashing cwm recovery to see if that works.

apocalypserisin said:
Is there an image of stock 4.4 or 4.4.2 someone could post here, i can only fined .tgzs.
I wanted to reflash to stock because my gps was unable to lock on any satellites, even after trying topntp along with gps status. I read in PA forums that some were having issues with that rom and gps, and that stock worked fine. I pretty much flashed to pa right after i got the phone last week, and never really tried gps under stock. I wanted to reflash to stock to check gps if it works, other wise I was going to RMA and hope for a newer batch (mine is from November, supposedly 312k batch works perfect gps wise).
Edit: found a stock zip: http://forum.xda-developers.com/showthread.php?t=2676691
Downloading and will flash when its ready
Edit: zip did not work (incorrect header/footer?) going to try flashing cwm recovery to see if that works.
Click to expand...
Click to collapse
my previous answer was meant for using flash-all method.
you can't flash anything withing the stock recovery.

GUGUITOMTG4 said:
my previous answer was meant for using flash-all method.
you can't flash anything withing the stock recovery.
Click to expand...
Click to collapse
Yeah, ending up flashing cwm and the above image and it worked.
Gotta say as a relative noob to all this waiting for your device to boot after messing with adb/fastboot is kinda heartpounding.

Stuck on Samsung logo screen after flashing bootloader!

Hey guys,
I was previously on xtresolite 2.4 lollipop rom and saw that he had a new rom out based on Marshmellow 6.01.
The instructions for the installation the new rom said to flash the new bootloader, modem and recovery before installing the new rom.
I flashed the bootloader with Odin using the BL button as instructed and how it's stuck on the Samsung Screen. I can still boot into download mode, but that's about it. It won't let me boot into recovery. Doing a bit of research it says to boot into download warning screen and cancel. Then quickly do the recovery buttons (volup, home, power), but it still won't go in.
So now I'm stuck! i'm trying to download the new stock Marshmellow firmware to see if I can install that, but aside from that I'm not sure what else I can do.
Any suggestions? Since I'm still able to use Odin, can I try to re-install the correct bootloader or is that too late? I'm not even sure which bootloader to install now. :crying::crying::crying:
Any help is much appreciated!
Thanks,
kc

as long as you can boot into the download mode, everything's alright. try flashing the latest stock rom for your model. then a new recovery, and then the new xtrestolite rom.
if something fails. do it again.... flash the latest stock rom, and so on.

Just make sure you have the correct model software for your phone and there won't be any issues. Did you backup your imei way back when you rooted on lollipop? If you did then everything will be fine if you didn't, Restore stock ROM and root, then backup your imei, hopefully you won't have any issues with your modem

Try pressing on power + vol down untill the phone shuts down then quickly press home+power+vol up before the phone starts . you will be in recovery try a factory reset then wait for the first boot. Voila !

hey all, just wanted to update. I still couldn't get into recovery, but was able to flash the stock rom and it's working as stock right now. Been using it for the past week or so and no major issues noted. I'm a bit scared to mess around again
Now that I'm on stock Marshmallow 6.0.1 rom, do I still need to try and flash the modem and boot loader for it?
Also, now that i'm on stock do I need to unroot again to install the twrp recovery? or can I just go into odin and flash it right away?
Thanks again for the help and suggestions!!!

tnimk said:
hey all, just wanted to update. I still couldn't get into recovery, but was able to flash the stock rom and it's working as stock right now. Been using it for the past week or so and no major issues noted. I'm a bit scared to mess around again
Now that I'm on stock Marshmallow 6.0.1 rom, do I still need to try and flash the modem and boot loader for it?
Also, now that i'm on stock do I need to unroot again to install the twrp recovery? or can I just go into odin and flash it right away?
Thanks again for the help and suggestions!!!
Click to expand...
Click to collapse
Stock rom overrides everything so your root is long gone & you now have the latest bootloader & modem already - don't stress & no need to do anything else! If you want custom recovery simply flash with latest TWRP using Odin in download mode (in tar format using AP button). Don't root with TWRP if asked to - instead download latest recovery flash-able SuperSU (ZIP) onto your device & then flash it using TWRP. This will be the safest option for you (with root if you want).
AFAIK one always uses the "AP" button if you wanna flash <anything> with Odin - not the BL button (I've never used this). The rest are for pro's only (of which I'm not one). I'm simply a regular rom flasher & read/study/compare several guides before attempting anything I've never done before with my device. If the overall feeling is not a good one, rule of thumb is I don't proceed until I feel confident enough about what I'm attempting to do.
Good luck.

On my sm-G920I
I flashed the xtresolite ROM without first flashing the bootloader and modem and it worked fine for me, if you back up everything with an otg cable onto a USB then flash the ROM everything should work fine but you will have to wait around 5 minutes for it to boot. If your still waiting after 10-20 minutes then you did something wrong and you can just wipe your entire phone then recover everything from your backup on your USB ????????