Database Info

[Q] Flashed stock, still boot loop

I was running Cyanogenmod9 on my SGH-I727R when I got into a bootloop. I reflashed stock Rogers Rom and still stuck in a boot loop. Any help please?

Scarecrow Legion said:
I was running Cyanogenmod9 on my SGH-I727R when I got into a bootloop. I reflashed stock Rogers Rom and still stuck in a boot loop. Any help please?
Click to expand...
Click to collapse
Can you please be more specific?
What screen are you exactly getting, the boot logo then a reboot? are you getting a recovery screen or do you bootloop not into the system but into ClockworkMod recovery?

The boot boot logo then restart. same thing with the stock rom it would boot into the Rogers logo then restart

Have you tried formatting through recovery? formatting can be found in mounts and storage.

yup, when I get back home I'll see if I can darkside wipe. see if that will help

That should help a lot. It should definitely work, make sure you install a Custom ROM and not a Stock ROM.
Make sure in future situations you don't install a stock ROM if your current ROM is a custom ROM, this can cause problems and will not fix problems. If you want to revert back to Stock ROMs after installing a Custom ROM I highly recommend you use Fastboot to flash the image. However there are tutorials and instructions on how to use Fastboot efficiently and properly so you don't mess anything up.
Cheers

Thanks again, darkside wipe worked. I have no clue what bricked it in the first place though
Scarecrow Legion

No problem Wiping everything would've worked too lol!

Cannot flash any ROM, then stuck at HTC logo

Not sure what happened but I can't flash any custom ROM. This is what I did so I can start flash. I "fastboot OEM lock" then run RUU (RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02_10.1..._262073_signed.exe). Everything went good. After that I did a factory reset and erase phone thought Setting. This should be fresh.
Now I unlock bootloader. I did not request a new Unlock_code.bin. I just use the old one i had. Unlock when good. Now I flash "fastboot flash recovery recovery-clockwork-5.8.3.1-ville.img", success. I reboot and when into recovery then flash "SuperSU v0.96", success and i do see SuperSU on the phone. Finally I install Goomanager. GooManager installed "openrecovery-twrp-2.3.0.0-ville.img", success.
Now I install custom ROM. I open the custom ROM and drag "boot.img" so i can flash it first before flashing the ROM.
did a "fastboot flash boot boot.img" success. Then when into TWRP v2.3.0.0, and did a wipe cache, wipe devlik, and factory reset, finally flash the ROM. It flash only like less than 5% and then the phone just reboot, Now I'm stuck at HTC Logo w/red letter below..
Could the ROM not compatible w/TWRP v2.3.0.0. This are the ROM i tried, Unofficial AOKP JellyBean Build 4.1 [10/8/12] and Venom ROM, all said ROM flash success and stop at about 5% of flashing, then it reboot and stuck at HTC Logo
Please help.
PS. if I lock BL and run RUU it's working but after unlock BL, root and all success, i cannot flash any rom as stated above.
My BHoot 1.09

cat2115 said:
Not sure what happened but I can't flash any custom ROM. This is what I did so I can start flash. I "fastboot OEM lock" then run RUU (RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02_10.1..._262073_signed.exe). Everything went good. After that I did a factory reset and erase phone thought Setting. This should be fresh.
Now I unlock bootloader. I did not request a new Unlock_code.bin. I just use the old one i had. Unlock when good. Now I flash "fastboot flash recovery recovery-clockwork-5.8.3.1-ville.img", success. I reboot and when into recovery then flash "SuperSU v0.96", success and i do see SuperSU on the phone. Finally I install Goomanager. GooManager installed "openrecovery-twrp-2.3.0.0-ville.img", success.
Now I install custom ROM. I open the custom ROM and drag "boot.img" so i can flash it first before flashing the ROM.
did a "fastboot flash boot boot.img" success. Then when into TWRP v2.3.0.0, and did a wipe cache, wipe devlik, and factory reset, finally flash the ROM. It flash only like less than 5% and then the phone just reboot, Now I'm stuck at HTC Logo w/red letter below..
Could the ROM not compatible w/TWRP v2.3.0.0. This are the ROM i tried, Unofficial AOKP JellyBean Build 4.1 [10/8/12] and Venom ROM, all said ROM flash success and stop at about 5% of flashing, then it reboot and stuck at HTC Logo
Please help.
PS. if I lock BL and run RUU it's working but after unlock BL, root and all success, i cannot flash any rom as stated above.
My BHoot 1.09
Click to expand...
Click to collapse
Everything looked like you did it right. I never new TWRP had a 2.3 version so I looked it up and found this.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may not longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated.
Click to expand...
Click to collapse
It might not be related but since you seem to be doing it write I would go back to TWRP 2.2.2.0 and try to flash a rom there. I'll test it out myself this morning.

Yes the Roms you are using are not compatible with twrp that you are using.I went through this sane exact thing last night.in the thread here they say there is aNew updater binary needed in roms to be ABLE to flash.they provide one but when I put it in my roms they still didn't flash. Boot into bootloader and adb flash cwmr or the previous version of twrp.

Sensation dead?

Hey guys!
My Sensation recently died on me, or should I say it won't boot ANY ROM available here. It just enters bootloop and cuts off on first glimpse of the boot animation (or sometimes after fresh ext4 format it just hangs on the splash screen - white bg with HTC). I have installed 4EXT recovery because I thought it was due to CWM Recovery. I had ViperS installed andd I got occasional random reboots followed by bootloops. After pulling the battery out the ROM booted fine until today. Now I can't boot any ROM, flashing goes OK, I tried restoring my factory ROM, but that just bootloops and cuts off at the beats logo, too.
What to do? Is there any fix?

5ageman said:
Hey guys!
My Sensation recently died on me, or should I say it won't boot ANY ROM available here. It just enters bootloop and cuts off on first glimpse of the boot animation (or sometimes after fresh ext4 format it just hangs on the splash screen - white bg with HTC). I have installed 4EXT recovery because I thought it was due to CWM Recovery. I had ViperS installed andd I got occasional random reboots followed by bootloops. After pulling the battery out the ROM booted fine until today. Now I can't boot any ROM, flashing goes OK, I tried restoring my factory ROM, but that just bootloops and cuts off at the beats logo, too.
What to do? Is there any fix?
Click to expand...
Click to collapse
S-ON or S-OFF?

rzr86 said:
S-ON or S-OFF?
Click to expand...
Click to collapse
It's all in my sig, I only have 1.27 now. S-OFF, rooted, unlocked. Flashed many ROMs and they worked fine, even now every ROM installs without any error but they all get stuck in bootloop

5ageman said:
It's all in my sig, I only have 1.27 now. S-OFF, rooted, unlocked. Flashed many ROMs and they worked fine, even now every ROM installs without any error but they all get stuck in bootloop
Click to expand...
Click to collapse
i am really blind
ok.i assume you have now 4ext
if yes then:
format all partitons except sdcard
flash the rom
otherwise flash the boot.img of the rom manually
see here how
http://forum.xda-developers.com/showthread.php?t=1631861 (only extra 1 step)

rzr86 said:
i am really blind
ok.i assume you have now 4ext
if yes then:
format all partitons except sdcard
flash the rom
otherwise flash the boot.img of the rom manually
see here how
http://forum.xda-developers.com/showthread.php?t=1631861 (only extra 1 step)
Click to expand...
Click to collapse
It happens
I tried both, 4EXT wipe and flashing the boot.img, but that didn't help
Now, this is weird! I thought after countless tries to try again, just before I give up, and try restoring my CWMR backup of the stock factory ROM I had and after one bootloop the phone started booting and now works normally :silly: even after couple of restarts.
Thanks for trying to help, but now I'm afraid to flash anything else on it. Could it be my hardware is not right?

[Q] HTC J Butterfly Half Bricked

Hi, so i got my phone last week. And yesterday, I decided to try and flash some custom roms on it. My device is pretty funny, I live in Hong Kong and when i bought my device, they have done S-OFF, unlocked bootloader, even custom recovery with twrp AND cwm. Now the default recovery was twrp, I tried flashing some roms, tried different ones, my device doesn't acccept them, after installing the rom, my device boots, shows the red text, stuck there for around 15 seconds and it reboots itself into the same state. So I used my twrp backup and flashed the recovery to cwm to give it a shot, the results are the same. And then at point, i booted up into recovery and it says Entering Recovery, and it gets stuck there forever. I can't boot into the system either. I tried using fastboot clear the cache, reflash the two different recoveries, no luck. I can get into bootloader and nothing else. Tried using HBOOT CL99IMG.zip method, but my phone just doesnt accept the roms. Any ideas?
Thankyou, any help would be greatly appreciated.

Any ideas? Anyone? Because all i need to do is to boot into twrp recovery. However, when i try to boot recovery it just says entering recovery, with the htc screen, and stays there forever. Any Suggestions?

Did you try "fastboot erase cache" command ?
Try to flash the boot.img included in your rom.zip with "fastboot flash boot boot.img"

Kroutnuk said:
Did you try "fastboot erase cache" command ?
Try to flash the boot.img included in your rom.zip with "fastboot flash boot boot.img"
Click to expand...
Click to collapse
Yea I did, apparently i got something. I mixed some files from the HTL21 Taiwan zip thingy, with the signed rom. I am able to boot into the os. However once I unlock it it crashes. Recovery still doesnt work :/
Anyways, thanks for the suggestion Appreciate it.

UPDATE: Now the phone isn't accepting anything from fastboot :/
It all says FAILED <remote:not allowed>
This is getting nuts lol

The fastboot is activated in the settings in your rom ?

Not sure about that, probably no :/ but thats the only rom i can get working
I can see it fastboot devices tho

anyone else? anymore ideas? :/

ok, so I got my phone kinda working. I used the htc butterfly toolkit, somehow flashing the X920e recoveries can make it work. I then restored from my previous backup with twrp, which contains system, data, boot. but when i boot into the system, it says loading widget, everything works fine for a while, then it suddenly crashes. I have tried restoring the system with only system and boot without data, still no luck. any ideas?? i have attached my log
any help will be greatly appreciated, thanks
http://www.filedropper.com/traces

Can't install Custom Roms.

Alright, so its without wasting time of people here, I'd just state the summary in points.
I flashed stock rom a.17 - I had custom roms before, I got fed up with them changing every 2 months.
Then everything worked fine until I flashed the boot.img from vishal_android_freak to get recovery.
I got the twrp recovery 2.7.0.0.
I flashed AOSP 6.0.1 through it, it was done very well but the rom stuck on boot animation for more then 30 mins.
I pulled the battery out - now I had TWRP 2.8.4.0
I tried flashing the rom again, it gave /data error.
I flashed stock rom, rooted then tried other methods of getting recovery, I failed everytime (Tried from TWRP app, su dd command, Recovery installer app )
Then I found a CWM boot.img to flash through fastboot.
I did and got CWM.
I flashed AOSP again from it, it stuck on boot animation again.
Then again I flashed stock rom and repeated the process.
This time with CWM, I flashed Stryflex LP Ultimate
It also stuck on boot animations.
Any idea why this happens? How to fix this ****?
Summary: Only stock rom works, not any other rom.

Observer000 said:
Alright, so its without wasting time of people here, I'd just state the summary in points.
I flashed stock rom a.17 - I had custom roms before, I got fed up with them changing every 2 months.
Then everything worked fine until I flashed the boot.img from vishal_android_freak to get recovery.
I got the twrp recovery 2.7.0.0.
I flashed AOSP 6.0.1 through it, it was done very well but the rom stuck on boot animation for more then 30 mins.
I pulled the battery out - now I had TWRP 2.8.4.0
I tried flashing the rom again, it gave /data error.
I flashed stock rom, rooted then tried other methods of getting recovery, I failed everytime (Tried from TWRP app, su dd command, Recovery installer app )
Then I found a CWM boot.img to flash through fastboot.
I did and got CWM.
I flashed AOSP again from it, it stuck on boot animation again.
Then again I flashed stock rom and repeated the process.
This time with CWM, I flashed Stryflex LP Ultimate
It also stuck on boot animations.
Any idea why this happens? How to fix this ****?
Summary: Only stock rom works, not any other rom.
Click to expand...
Click to collapse
I think​, that means bootloader is unlocked again! Recheck bootloader state and always use latest TWRP recovery (v3.0.2 for us).
You can download Xperia L recovery from twrp website and then use your current v2.8.4 one to install that. Or just simply use adb & fastboot in your PC and enter this command:
Code:
fastboot flash boot [I]your recovery image name.img[/I]
. And then flash your desired ROM

Kungfu73 said:
I think​, that means bootloader is unlocked again! Recheck bootloader state and always use latest TWRP recovery (v3.0.2 for us).
You can download Xperia L recovery from twrp website and then use your current v2.8.4 one to install that. Or just simply use adb & fastboot in your PC and enter this command:
Code:
fastboot flash boot [I]your recovery image name.img[/I]
. And then flash your desired ROM
Click to expand...
Click to collapse
Alright, I check bootloader state, it says bootloader unlock done means it's unlocked.
I am going to flash twrp 3.0.2 and will update you soon!

Kungfu73 said:
I think​, that means bootloader is unlocked again! Recheck bootloader state and always use latest TWRP recovery (v3.0.2 for us).
You can download Xperia L recovery from twrp website and then use your current v2.8.4 one to install that. Or just simply use adb & fastboot in your PC and enter this command:
Code:
fastboot flash boot [I]your recovery image name.img[/I]
. And then flash your desired ROM
Click to expand...
Click to collapse
Oh Man, you saved my day! nothing worked but the damnit twrp 3.0.2
For anyone else referring here:
I get hell lot of graphical glitches when I flashed twrp 3.0.2, I just made it to factory reset and click install button although my screen was glitched and I cant even look at it.
JUST IGNORE THE GLITCHES! I wiped dalvik cache after flashing AOSP-RRO, now I'm flashing Lineage OS, thanks a lot! Button pressed.

Observer000 said:
Oh Man, you saved my day! nothing worked but the damnit twrp 3.0.2
For anyone else referring here:
I get hell lot of graphical glitches when I flashed twrp 3.0.2, I just made it to factory reset and click install button although my screen was glitched and I cant even look at it.
JUST IGNORE THE GLITCHES! I wiped dalvik cache after flashing AOSP-RRO, now I'm flashing Lineage OS, thanks a lot! Button pressed.
Click to expand...
Click to collapse
Did TWRP 3.0.2 ultimately work with this?
If worked, I am also curious to know how much space is left there for apps in device memory, since the ROM seems to be Marshmallow based.