Database Info

[Q] Phone Stuck in Boot Loop Why?

Hey All,
I just got my One XL and I was so excited by the root on 2.20 that I decided to try and flash the custom rom of AOKP on onto it.
After rooting the phone, I did the following:
Flashed TWRP 2.3.1.0 - success
Then I went and saw the thread about the AOKP rom and followed instructions. On that thread, it states that you must flash the boot.img before doing this through fastboot if you are coming forom 2.20 firmware, so I did that. Then I saw that it said on the thread "do not complain about bootlooping if you flashed a custom KERNEL or did not manually flash the stock KERNEL via fastboot" As this was the first custom rom I had attemped with this phone I assumed that I had the stock KERNEL already installed, so I did not flash any kind of kernel.
As soon as I flashed the boot.img from AOKP, I saw that there was red writing on the bootloader about this being for development use only and I noticed that the phone would get past the bootloader to a black screen and then would reboot (boot loop).
I thought that the issue here was that I did not flash the kernel so I went and downloaded the rohan.kernel and flashed that. HOWEVER, I did not realize that I was meant to use recovery to do that and I pushed the boot.img from within the kernel via fastboot instead of using recovery to flash the new kernel (not sure if that matters all that much, but I think that from now on all rom work will be done in the day time after sleeping a little more).
After doing that I see no change in the performance of the phone (it is still boot looping). I am unsure of what to do now. I managed to push the KERNEL zip file and the ROM zip file to the phone via adb but when I try and install them via TWRP I am getting an error because the phone reports that it is unable to mount /sdcard/.
Can one of the far more knowlegable gurus here point me in the right direction? I have wiped the cache and davlik cache numerous times but that has not helped. Should I use TWRP to wipe the system? How can I get the phone back to a place where I can install the new rom?
Thanks!!

ackerchez said:
Hey All,
I just got my One XL and I was so excited by the root on 2.20 that I decided to try and flash the custom rom of AOKP on onto it.
After rooting the phone, I did the following:
Flashed TWRP 2.3.1.0 - success
Then I went and saw the thread about the AOKP rom and followed instructions. On that thread, it states that you must flash the boot.img before doing this through fastboot if you are coming forom 2.20 firmware, so I did that. Then I saw that it said on the thread "do not complain about bootlooping if you flashed a custom KERNEL or did not manually flash the stock KERNEL via fastboot" As this was the first custom rom I had attemped with this phone I assumed that I had the stock KERNEL already installed, so I did not flash any kind of kernel.
As soon as I flashed the boot.img from AOKP, I saw that there was red writing on the bootloader about this being for development use only and I noticed that the phone would get past the bootloader to a black screen and then would reboot (boot loop).
I thought that the issue here was that I did not flash the kernel so I went and downloaded the rohan.kernel and flashed that. HOWEVER, I did not realize that I was meant to use recovery to do that and I pushed the boot.img from within the kernel via fastboot instead of using recovery to flash the new kernel (not sure if that matters all that much, but I think that from now on all rom work will be done in the day time after sleeping a little more).
After doing that I see no change in the performance of the phone (it is still boot looping). I am unsure of what to do now. I managed to push the KERNEL zip file and the ROM zip file to the phone via adb but when I try and install them via TWRP I am getting an error because the phone reports that it is unable to mount /sdcard/.
Can one of the far more knowlegable gurus here point me in the right direction? I have wiped the cache and davlik cache numerous times but that has not helped. Should I use TWRP to wipe the system? How can I get the phone back to a place where I can install the new rom?
Thanks!!
Click to expand...
Click to collapse
First of all I think if you're on 2.2 fw I don't think you can flash kernels through TWRP - I think it has to be through fastboot, I don't know first hand as I'm still on an earlier fw version.
Secondly if you can get into recovery you can flash another rom.
Go to Mount > Mount USB Storage with your phone connected via USB, it should mount as a drive otherwise windows asks you to format format the drive if this happens chances are may have wiped it in bootloader with factory reset or clear storage in either case just format the drive.
You can then drag and drop another rom onto the phone and flash that - remember to extract the boot.img from the rom and flash via fastboot so it will boot.
Goodluck

thejosh86 said:
First of all I think if you're on 2.2 fw I don't think you can flash kernels through TWRP - I think it has to be through fastboot, I don't know first hand as I'm still on an earlier fw version.
Secondly if you can get into recovery you can flash another rom.
Go to Mount > Mount USB Storage with your phone connected via USB, it should mount as a drive otherwise windows asks you to format format the drive if this happens chances are may have wiped it in bootloader with factory reset or clear storage in either case just format the drive.
You can then drag and drop another rom onto the phone and flash that - remember to extract the boot.img from the rom and flash via fastboot so it will boot.
Goodluck
Click to expand...
Click to collapse
Hey!
Thanks a ton for your reply! I managed to get the phone to install a new ROM (AOKP V5) and it seems to boot up. Now when I get into that rom, I see all kinds of things crashing on me. The "Settings" app crashes, the keyboard crashes..any idea?

Did you wipe system, factory reset, davlik and cache from within TWRP before flashing?
Try that otherwise if you're still running into issues post in the thread.

You flashed the 11/10 JB gapps?
Sent from my Nexus 7 using xda premium

ok, i got the phone back up now and have been able to flash stuff properly.
I am working on an issue where after flashing a new rom (AOKP v4) and then a new kernel right after (rohan.kernel V2) the rom seems to hang on the loading splash screen. Has anyone else had this happen? Know how to solve it?

ackerchez said:
ok, i got the phone back up now and have been able to flash stuff properly.
I am working on an issue where after flashing a new rom (AOKP v4) and then a new kernel right after (rohan.kernel V2) the rom seems to hang on the loading splash screen. Has anyone else had this happen? Know how to solve it?
Click to expand...
Click to collapse
Did u wipe everything? (davlik, cache)
Sent from my HTC One XL using xda premium

[Q] Custom Rom don't work

Unlocked and rooted ATT HTC One X and flashed pa_evita-2.54-09NOV2012-210217 ROM.
Boot up as far as an Android character with the lettering Paranoid Android 2.+ and then freezes there.
Any suggestions?? If nothing else, how do I get back to stock ROM?
Noob rldieb

rldieb said:
Unlocked and rooted ATT HTC One X and flashed pa_evita-2.54-09NOV2012-210217 ROM.
Boot up as far as an Android character with the lettering Paranoid Android 2.+ and then freezes there.
Any suggestions?? If nothing else, how do I get back to stock ROM?
Noob rldieb
Click to expand...
Click to collapse
1. What recovery are you using?
2. Did you wipe cache/dalvik-cache, factory reset?
In order to get back to a stock ROM, you will need to boot into recovery, then mount your usb storage. Put the rom on your sd card and then unmount. To be safe, wipe the cache and dalvic cache, then flash the stock rom.

What hboot are you on?
You may have flash boot.img first if you are on hboot 1.14

I think he just didn't full wipe

That's just wrong!
Sent from my Nexus 7 using Tapatalk 2

I'm having the same issue. I'm trying to flash this same rom on a device rooted on 2.20. I think my issue has something to do with flashing the boot.img. I have tried to flash using hasoon's toolkit, which doesnt seem to work, i have extracted the zip and placed the boot.img in the kernel folder, and when the command prompt tries to flash it, it says error. I have also tried flashing the kernel from the phone directly using the flash flash image gui app, and it says flash is successful, but when it prompts to boot into recovery, the command doesnt work from my phone so i have to boot into recovery manually.
can anyone give a solid link or tutorial on how to successfully flash the boot img onto my device, every link I have read uses windows cmd prompt, which when i try to replicate, it never works.. So, for now I flashed back to viper rom, since it has its own installer. It would be so nice if all these other roms were able to install like that.
thanks in advance for the help

threetwentyfizzle said:
I'm having the same issue. I'm trying to flash this same rom on a device rooted on 2.20. I think my issue has something to do with flashing the boot.img. I have tried to flash using hasoon's toolkit, which doesnt seem to work, i have extracted the zip and placed the boot.img in the kernel folder, and when the command prompt tries to flash it, it says error. I have also tried flashing the kernel from the phone directly using the flash flash image gui app, and it says flash is successful, but when it prompts to boot into recovery, the command doesnt work from my phone so i have to boot into recovery manually.
can anyone give a solid link or tutorial on how to successfully flash the boot img onto my device, every link I have read uses windows cmd prompt, which when i try to replicate, it never works.. So, for now I flashed back to viper rom, since it has its own installer. It would be so nice if all these other roms were able to install like that.
thanks in advance for the help
Click to expand...
Click to collapse
I do have a solution! Download Flash Image GUI from the market (it's $1.99) and it will do the process for you, no commands needed! The app is also available via XDA for free, do a search and download it.

Tablet Bricked with no System OS or recovery. Just fastboot

OK so I was having problems with my tablet's recovery and I was following this guide that told me to basically wipe all my .img s (boot.IMG, system.IMG , ect.) via fast boot. Then it said to flash the update zip. Well I tried downloading the firmware from Asus website and whenever I tried flashing that with fastboot it gave me an error saying it didn't have a android-info file. Then I tried installing not twrp and cwm and they installed but whenever I tried to go to recovery it just went straight to the fast boot screen. So basically now I just have a tablet that can only do fast boot. What should I do? Is there a different update.zip I should flash or am I basically screwed
Sent from my Nexus 4 using xda app-developers app

charger04 said:
OK so I was having problems with my tablet's recovery and I was following this guide that told me to basically wipe all my .img s (boot.IMG, system.IMG , ect.) via fast boot. Then it said to flash the update zip. Well I tried downloading the firmware from Asus website and whenever I tried flashing that with fastboot it gave me an error saying it didn't have a android-info file. Then I tried installing not twrp and cwm and they installed but whenever I tried to go to recovery it just went straight to the fast boot screen. So basically now I just have a tablet that can only do fast boot. What should I do? Is there a different update.zip I should flash or am I basically screwed
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Your write-up isn't very clear. What is your current firmware version (Settings>About Tablet>Build Number) on stock ROM or reboot into bootloader and read it from the upper left text block. Did you install TWRP or CWM recovery? What recovery version? What update.zip? What guide were you following (provide link)?

[Q] Stuck in recovery restart limbo

Hello all,
Last night I was trying to install the latest Gummy release on my Verizon Galaxy S3. This was the first time I have tried to flash a rom on this phone. It failed, and I rebooted my phone, and now it will only boot into the clockwork recovery.
I thought it may have been damaged as i was transferring the file to the device. I had an SD card in my droid X, So I put it in my Galaxy and formatted it with clockwork. Then I transferred the gummy release (that I also re-downloaded) from my computer to the SD card via a memory card reader. I put it in my Galaxy and tried to install the release, and it gave me a different error
Code:
E: Can't Open /external_sd/Gummy-2.1-01-09-14-NIGHTLY-d2vzw.zip
(bad)
Installation aborted.
Edit: Tried a few other roms and they had the same issue, but Cyanogen Mod 10.2 worked. Anybody have any guesses why?
Edit2: Further developments, Trying to do the latest nightly fir the CM yields the same issue that Gummy's release gave me initially. It reports as follows:
Code:
E: Error in /external_sd/cm-11-20140110NIGHTLY-d2vzw.zip
(Status 7)
Installation aborted
Is there possibly a firmware issue at play?

Did u unlocked ur recovery. And if ur trying to flash a KITKAT rom u need the latest clockwork recovery

I'm having this exact issue except I currently have TWRP 2.6.3. I wiped data, cache and internal and it actually booted the below ROM (the first boot) but once I got everything setup and rebooted the device it will not boot beyond recovery. It hangs on the Samsung boot logo. I've tried to restore to a 4.1.2 ROM as well as install 4.3 and 4.1.2 again multiple times but they will not boot. Any direction would be appreciated.
http://forum.xda-developers.com/showthread.php?t=2601536

twistedillutions said:
Did u unlocked ur recovery. And if ur trying to flash a KITKAT rom u need the latest clockwork recovery
Click to expand...
Click to collapse
Sorry, forgot to mention, I did unlock with EZunlock. Would the clockwork on the play store be the latest one, or is there another place with more up to date versions?
Cappurnikus said:
I'm having this exact issue except I currently have TWRP 2.6.3. I wiped data, cache and internal and it actually booted the below ROM (the first boot) but once I got everything setup and rebooted the device it will not boot beyond recovery. It hangs on the Samsung boot logo. I've tried to restore to a 4.1.2 ROM as well as install 4.3 and 4.1.2 again multiple times but they will not boot. Any direction would be appreciated.
http://forum.xda-developers.com/showthread.php?t=2601536
Click to expand...
Click to collapse
Do you get the same error on install that I'm getting, ro are the installs finishing, but not booting?

Try goo manager or ez-recovery to install the latest recovery
right now i can think of
factory reset format data. Make sure u backup ur internal
Wen changing from rom to rom is a good thing to do a clean install
get the right gapps.
The 1st boot always takes time at least on me.
Sorry i cant think of more helpful things.. Been drinking

Looks like my recovery just needed an update. Thanks everyone.
Sent from my Nexus 7 using Tapatalk

Confirmed also an old recovery for me as well. Thank you very much!

Soft bricked MHA-L29C432; please help!!!!

Hi guys i was trying to install a custom rom on my mate 9 (MHA-L29C432-156)so i followed the instructions ; unlocked the bootloader; then installed twrp 3.1.0-0; on twrp formated data; then full wiped and try to install AurRom from SD; but get a message that zip file is corrupted; so I tried with S.H.I.E.L.D ROM and it flashed , but then when boot goes to eRecovery, and give me 3 options download latest version and recovery; reboot and shutdown. So now I cant boot the phone, when I restarted, followed same steps , format data, full wipe and trying to installing again but getting a message about all zip files of the roms are corrupted; then i try to restore backup; and same again get the huawei logo, then the android logo , phone restarts and eRecovery again.
Please someone HELP, I use this phone for my work...........!!!!!!!!!

How did you full wipe?
Also try with Twrp 3.0.2-2
Here:www.androidfilehost.com/?fid=745425885120697579

dannytgt said:
on twrp formated data
Click to expand...
Click to collapse
Something went wrong here. You can run 'adb logcat' to see the crash details while starting.

If you have a backup on twrp then restore to get phone working. You may need to flash the public and hw-data zips afterwards though.
If you don't have a backup then you could try flashing the C636 off line firmware and then use firmware finder to go back to your original firmware
Sent from my MHA-L09 using XDA-Developers Legacy app

you may just flash the modified recovery ( See Guide subforum ) ) to bypass the update certification and authorization and reflash an original firmware. your stored files will be lost anyway in most cases.
I would bet superuser ( shield ) and SuperSU ( Aurom) messed your boot image. Both are incompatible to each other and, afaik both are incompatible to twrp 3.1.
Flash TWRP 3.0.2.2, reboot to recovery again to change version, flash the rom ( f.e. shield rom), boot once up, reboot to recovery and THEN you may flash twrp 3.1

Thanks all of you guys, I've solved the problem, it seems that's something related to the sd card, I've formated the sd and transfer the files trough another phone and then put the sd on the mate 9, I follow the steps as followed before and works successfully, now I'm on AurRom and 182 firmware.