Develop Bugs

HELP PLEASE - EVO 3D Stuck in Bootloop!

Hello All,
I recently rooted my EVO3D using the HTCDEV method because the bootloader was version 1.5.
Here are the steps I followed to root (sorry for the copy and past but I want to be as detailed as possible)
Files Used
su 2.3.6.3
TWRP Recovery
Steps Taken:
1)Take both the su.zip and recovery.img files and put them in your sdk tools folder.
2)Now do the following in ur command prompt, hitting enter after each command.
3)Code:adb push recovery.img /sdcard/And,
4)Code:adb push su-2.3.6.3.zip /sdcard/Then,
5)Code:adb reboot bootloaderUr phone will go to fastboot and should look like the after picture above. Now you can flash the twrp recovery, so do,
6)Code:fastboot flash recovery recovery.imgIt will ouput something like this,
7)Code:sending 'recovery' <5068 KB>... OKAY////writing 'recovery'... OKAY///finished. total time: 11.355sNow you have twrp recovery, so you can navigate to it. On ur phone, use the power button to pick bootloader, then scroll down to recovery and pick that. You will then be booted into recovery.
8)Here you can pick "install zip" and then pick the "su-2.3.6.3.zip"
It will flash, the you can pick "back to main menu", then "reboot system now"
9)You will boot back up and have working Superuser. I have had no trouble with Titanium Backup, Root Explorer, Quick Boot or any other app that requires root. Before you do too much, it would be good to go back to recovery and do a Nandroid backup. Always best to get one ready before you start modding anything.
All of this worked fine, and the phone was "unlocked."
Then, I flashed the most recent version of CleanRom (2.7)
Again, the phone worked fine, battery life was a little crappy.
I decided to flash Ziggy's kernel.I flashed the kernel simply by putting on the SD card, and then rebooting into recovery. This worked fine as well, but I noticed some of the buttons for example the menu popups displayed volume where it should have said more, or bluetooth options where it should have said preferences. so this is where the trouble started, I downloaded kernel manager, and flashed silverneedle through that program. Now, I am stuck at the White HTC Splash screen bootloop. The phone turns on and after 15 seconds reboots, and reboots, and reboots.
What Ive attempted:
I have done countless wipes and clears of the dalvik cache and cache
ive formatted the system and the date sections (advanced menu in twrp)
ive reflashed the rom after wiping countless times
ive tried flashing different kernels in recovery to no avail
factory reset and wipe havent helped
im not concerned losing the contents of the SD card
I need help because I already had two phone claims in the past 11 months, and if I claim another lost phone I will lose insurance for life with Asurion (sprint)
anytips or help would be greatly appreciated
i can provide any additional info

Similar situation, Not sure if you've already solved the problem but I'm going to copy paste my solution from another thread...
Hi, I'm not sure if this is the right place to ask but this is a preety derp question. I've gone across the internet and tried a lot of reflashing to repair my sort of "bricked" evo. What happened, was that I had a evo 3d s-on htc bootloader unlocked, with custom recovery -clockwork..anyways I had flashed the leedroid 3d 4.0 rom and It worked the only problem was my wifi, so i attempted to flash another kernel onto it, but I had accidently flashed "Rcmix" kernel which I later found out was cdma =.=. so now my phone keeps rebooting at the htc screen, it would just load up with the green htc letters, then after 10 seconds or so it'd reboot, and then begin the process again. I can boot into bootloader and recovery but whatever I flash doesn't seem to work including restoring my backups...and then the battery died so i couldn't even charge it or go in. But i managed to work out I could load into bootloader from the CMD and the furthest i've gotten to is to have the bootloader show FASTBOOT USB. SO I must be getting somewhere...? I did read that i had to load from the cmd and not just from power+vol down..but I'd appreciate any help towards restoring my phone to the way it is or at least before i flashed the rcmix.
Just a note tho I've tried factory resetting but all i get is that it loads into recovery at the bootloader options i dont get "clear storage" as an option and "restore to factory settings" and what not just boots me into recovery agian.
EDIT:
I Managed to fix the phoneeee!!!..just for future preferences and anyone else who has this problem...
I followed bits and piece of IL DUCE's advice to izzy spun, the important part was booting the recovery from cmd. I wasn't able to "erase recovery" But I tried just booting it,
First I would remove the battery,
Put it back in,
Plug the usb cable in
1. Type command, from your Adb/fasboot folder, "adb reboot-bootloader"
2. After that I made sure my bootloader said "Fastboot USB", and then I issued the command, "fastboot boot cwm-4.0.1.4-shooteru.img" or with whatever recovery you had..
3. From there I restored from my backups my original rom. Rebooting, and fixed.
--- and It worked. At the time I was on clock work recovery, i only had the Revolutionary recovery img. Cwm-4.0.14.-shooteru.img to be exact,
after going in there I just cleared the cache and davlik and then, proceeded to restore my backups (I'm not sure if it would've worked if I had re-flashed the leedroid or a custom rom)
and then I simply rebooted the phone, and it got back into my phones original state before leedroid (as I had Only backedup before then)....
Apologies for the lengthly post, but I guess reading does help, but I've been going nuts before I managed to fix this. Just thought I'd leave this post incase someone were to need this.

Same problem
Hi there. I just recently joined so excuse my noobness but i have a similar problem. I recently just rooted my evo 3d sprint with the the boot 1.5 and everything went well. I decided i wanted to overclock my phone so i followed zeemaxs way. Before going into the overclock procedure i decided to do the the RCMIX Evo 3d kernel v. 2.2.3 first so i would have better results when done with the overclock procedure.I bootup the kernel through the recovery mode on the phone butit failed to load so i just reeboted. After that my wifi and 4g stopped working. So i downloaded an app on the market called "flash image GUI" which lets me flash the kernels through the app. I flashed the RCMIX kernel and rebooted and now im stuck ima boot loop. I COULD just go back and back up to my old rom and settings etc...........but the problem is i dintmake any kind of back up or recovery i think. I know i know im stupid and an idiot but i just sort of panicked n ended up with this. If anyone can help please tell me.I do not want to pay for a new phone at full price. PLEASE HELP THIS POOR NOOB!!!!! X(

awsomepanda20 said:
Hi there. I just recently joined so excuse my noobness but i have a similar problem. I recently just rooted my evo 3d sprint with the the boot 1.5 and everything went well. I decided i wanted to overclock my phone so i followed zeemaxs way. Before going into the overclock procedure i decided to do the the RCMIX Evo 3d kernel v. 2.2.3 first so i would have better results when done with the overclock procedure.I bootup the kernel through the recovery mode on the phone butit failed to load so i just reeboted. After that my wifi and 4g stopped working. So i downloaded an app on the market called "flash image GUI" which lets me flash the kernels through the app. I flashed the RCMIX kernel and rebooted and now im stuck ima boot loop. I COULD just go back and back up to my old rom and settings etc...........but the problem is i dintmake any kind of back up or recovery i think. I know i know im stupid and an idiot but i just sort of panicked n ended up with this. If anyone can help please tell me.I do not want to pay for a new phone at full price. PLEASE HELP THIS POOR NOOB!!!!! X(
Click to expand...
Click to collapse
What your going to have to do is flash the original kernel you started with. thats why your in a bootloop

Similar problem
Hi everyone!
I have a kind of similar problem, so I won't post it in a new thread.
Yesterday I rooted my phone following this guide: androidforums.com/evo-3d-all-things-root/494212-complete-newbies-guide-rooting-flashing-evo-3d-roms-kernels-using-fastboot . html (i am not allowed to post links to prevent spam).
I unlocked it with htcdev and installed a custom ROM without getting any errors. After restarting the phone, it got into a boot loop; it showed the starting animations of htc and the ROM and then shut down again.
Here some more information:
-Evo 3d Europe gsm
-hboot 1.5
-s-on
-image version 3.28.401
-installed ROMs using clockworkrecoverymod (as proposed in guide)
I have tried these ROMs (all leading to boot loop):
ICS NonSense
Cyanogen Mod 10 – DisarmedToaster (v. 1.4 and 1.5)
Jelly Bean 3d (by Ubuntuz)
SAD 2.1 DEsenseX
I installed the ROMs by doing:
Connect device via usb > flash boot.img via fastboot (from pc) > clear Cashe/UserData/DalvikVM > install rom.zip from sdcard > reboot
I really don't know what to try
Any ideas how I could install a running Android OS are highly appreciated.
Thx for any help

Problem solved!
Ok, I solved the problem by simply relocking the phone and installing the stock ROM with the RUU.exe

RUU.exe
I'm glad someone else mentioned Relocking before running the RUU. I've read several posts be others that have actually stated that Relocking wasn't necessary but in order for the RUU to take you have to Relock. IF you get a chance check out CoolICS Rom and MeanRom both are pretty good.

Thanks all for the help, had to revisit this issue today.

[HELP] My Zenfone 2 (ZE551ML 4GB) dilemma

My Zenfone 2 (ZE551ML 4GB) dilemma:
*•*I unlocked the bootloader with the official bootloader app
*•*I flashed the latest TWRP via adb. In the recovery screen, I saw an android showing error. That's when the panic started.
*•*I Then I rooted my phone with the one click Zenfone root application (available in XDA)
*•*I installed the official TWRP manager from the playstore and flashed with it. That also didn't solve my problem. Actually, a new problem set in. The phone started bootlooping IN RECOVERY.
*•*I rebooted the phone and then flashed an old version of TWRP for my phone. That solved the problem.
*•*Now, I wanted to flash Lineage OS in my phone. According to a YouTube tutorial, I copied my required files (the custom ROM and OpenGAPPS) to my Micro SD and then from twrp's advanced wipe, deleted everything except for Micro SD. I know that was an extremely stupid move but please bear with me.
*•*Deleting everything made things hundred times worse. It seemed impossible to get the phone into recovery mode again. But after a long time, I did.
*•*Now onto flashing the new ROM. I did a factory reset with twrp and then flashed the ROM and immediately got Error 7. By googling a bit, I found that the only way to solve this problem was by deleting the assert lines from the updater-script in meta/com/google/android inside the ROM.
*•* When I reflashed it, the process completed but it showed an error: (E:unknown command [log])
*•* Then I overlooked it again as a quick google said it didn't matter. Then I successfully flashed OpenGAPPS. I rebooted my phone and it kept bootlooping until it was back in the recovery screen. Weird right?
*•*I didn't seem to find any workaround so I decided to restore stock ROM. I downloaded it and flashed it. It succeeded. I rebooted my phone. And. .
*•*My phone now vibrates when I power on the phone and then it shows a black screen. It reboots automatically. I know it does as the phone vibrated periodically after the reboot
*•* I also can't go into the bootloader menu. My phone seems dead but I really need to revive it. I can't afford a new phone. Could you guys help me out please?

LethalHoe said:
My Zenfone 2 (ZE551ML 4GB) dilemma:
*•*I unlocked the bootloader with the official bootloader app
*•*I flashed the latest TWRP via adb. In the recovery screen, I saw an android showing error. That's when the panic started.
*•*I Then I rooted my phone with the one click Zenfone root application (available in XDA)
*•*I installed the official TWRP manager from the playstore and flashed with it. That also didn't solve my problem. Actually, a new problem set in. The phone started bootlooping IN RECOVERY.
*•*I rebooted the phone and then flashed an old version of TWRP for my phone. That solved the problem.
*•*Now, I wanted to flash Lineage OS in my phone. According to a YouTube tutorial, I copied my required files (the custom ROM and OpenGAPPS) to my Micro SD and then from twrp's advanced wipe, deleted everything except for Micro SD. I know that was an extremely stupid move but please bear with me.
*•*Deleting everything made things hundred times worse. It seemed impossible to get the phone into recovery mode again. But after a long time, I did.
*•*Now onto flashing the new ROM. I did a factory reset with twrp and then flashed the ROM and immediately got Error 7. By googling a bit, I found that the only way to solve this problem was by deleting the assert lines from the updater-script in meta/com/google/android inside the ROM.
*•* When I reflashed it, the process completed but it showed an error: (E:unknown command [log])
*•* Then I overlooked it again as a quick google said it didn't matter. Then I successfully flashed OpenGAPPS. I rebooted my phone and it kept bootlooping until it was back in the recovery screen. Weird right?
*•*I didn't seem to find any workaround so I decided to restore stock ROM. I downloaded it and flashed it. It succeeded. I rebooted my phone. And. .
*•*My phone now vibrates when I power on the phone and then it shows a black screen. It reboots automatically. I know it does as the phone vibrated periodically after the reboot
*•* I also can't go into the bootloader menu. My phone seems dead but I really need to revive it. I can't afford a new phone. Could you guys help me out please?
Click to expand...
Click to collapse
Did you flash the MM bootloader compatible TWRP mentioned in the OP for LineageOS? That solves error 7.

Ragarianok said:
Did you flash the MM bootloader compatible TWRP mentioned in the OP for LineageOS? That solves error 7.
Click to expand...
Click to collapse
I did not do that. I remembered all the steps but forgot that. That is the primary cause of my problem. Anyway to solve it?

LethalHoe said:
My Zenfone 2 (ZE551ML 4GB) dilemma:
*•*I unlocked the bootloader with the official bootloader app
*•*I flashed the latest TWRP via adb. In the recovery screen, I saw an android showing error. That's when the panic started.
*•*I Then I rooted my phone with the one click Zenfone root application (available in XDA)
*•*I installed the official TWRP manager from the playstore and flashed with it. That also didn't solve my problem. Actually, a new problem set in. The phone started bootlooping IN RECOVERY.
*•*I rebooted the phone and then flashed an old version of TWRP for my phone. That solved the problem.
*•*Now, I wanted to flash Lineage OS in my phone. According to a YouTube tutorial, I copied my required files (the custom ROM and OpenGAPPS) to my Micro SD and then from twrp's advanced wipe, deleted everything except for Micro SD. I know that was an extremely stupid move but please bear with me.
*•*Deleting everything made things hundred times worse. It seemed impossible to get the phone into recovery mode again. But after a long time, I did.
*•*Now onto flashing the new ROM. I did a factory reset with twrp and then flashed the ROM and immediately got Error 7. By googling a bit, I found that the only way to solve this problem was by deleting the assert lines from the updater-script in meta/com/google/android inside the ROM.
*•* When I reflashed it, the process completed but it showed an error: (E:unknown command [log])
*•* Then I overlooked it again as a quick google said it didn't matter. Then I successfully flashed OpenGAPPS. I rebooted my phone and it kept bootlooping until it was back in the recovery screen. Weird right?
*•*I didn't seem to find any workaround so I decided to restore stock ROM. I downloaded it and flashed it. It succeeded. I rebooted my phone. And. .
*•*My phone now vibrates when I power on the phone and then it shows a black screen. It reboots automatically. I know it does as the phone vibrated periodically after the reboot
*•* I also can't go into the bootloader menu. My phone seems dead but I really need to revive it. I can't afford a new phone. Could you guys help me out please?
Click to expand...
Click to collapse
xfstk is the only way. go to following thread and do as suggested. one advice when you get into bootloader. flash raw without AFT. that is best.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785

M9 in bootloop, TWRP stopped working

Hello all, my M9 has been crazy since some days. I have a lot of different problems and haven't been able to see what the common issue is, so I will list everything I know:
1. European M9 unlocked, baseband 01.01_U11440792_97.00.51203G_F, OS-3.35.401.32
2. Had official Android 6.0 and couldn't update OTA to Nougat (update crashing after 25%) so I tried rooting and flashing a custom ROM (RR-N-v5.8.0-20170106-himaul-Unofficial). Worked without problems for 3 months and 2 days ago my phone restarted and didn't boot to the rom anymore (I see the HTC logo with white background and red letters, after 10 seconds or so I see the logo of my rom but it freezes and restarts again, over and over again).
3. Tried flashing the same version stock rom with RUU method (renaming it to 0PJAIMG.zip and place it in sd card) and this failed because of a problem with the zip signature.
4. Tried another custom rom (ViperOneM9_6.1.0) and the same situation (I see the rom logo but freezes and restarts again)
5. After flashing the 2nd rom, my TWRP stopped working (I see the logo of TWRP and freezes, restart)
6. I tried using fastboot commands to boot to recovery and nothing happens, tried flashing different TWRP versions and still freezes.
So at the moment the working modes are only download and bootloader.
Any ideas of where the problem is?
I'm pretty used to flashing custom roms but never had such problems before, so my knowledge doesn't go that far. Also if you need logs, please give me some instructions on how to get them. Thanks

Android A1(AQ4501) Dead :(

I own a canvas A1 4GB variant, I had rooted my phone and flashed custom recovery(everything was finee), After a while my phone's battery started giving me problems(lasted only few hours), I considered flashing Stock ROM or any other trusted ROM, I had flashed RR M[07/07] based on android MM, The battery was still giving problem, A week later, My mom's phone broke and she had to use this(A1) temporarily, I formatted everything and thought of flashing stock ROM and handing over the phone to her, I tried flashing the official zip via TWRP, It gave me some error regarding unable to mount system, System partions or something(I don't remember). And after that, I could't flash any ROM, I tweaked some settings in TWRP and now my phone is totally dead, It does not boot up at all, No recovery mode turns on, Nothing except a black dead screen, I tried flashing stock firmware via SP flash tool, It completes and says successful but still nothing happens, Just wanna know if something can happen to this one? I really loved that device and would be great to have it back working.

Flash correct stock firmware in sptools

arunassain said:
Flash correct stock firmware in sptools
Click to expand...
Click to collapse
doesn't work. I have tried various STOCK Roms on mine but didnt work. Please post a link if possible which u think works.

Unable to boot phone once TWRP installed?

Hey guys,
So I've been trying for days to get a custom Ron installed on N975F.
Right now I'm on completely reflashed stock Rom. With stock recovery et al. No root.
I am able to flash Magisk with Odin. No trouble. And my phone continues as usual without issue.
However, once I install TWRP, no matter where or how I install it, once I restart my phone it will boot past the warnings without issue, then go to the screen that just says "SAMSUNG" and the phone will never actually boot up.
I can still boot into TWRP recovery without issue, but system itself will never boot, it will just sit on the "SAMSUNG" screen forever.
In fact, it seems like as long as TWRP is installed to recovery, my system will never boot with any Rom. It can be fixed by reinstalling stock recovery, or by reflashing stock in it's entirety (which I have now done before I try again).
Has anyone got any ideas why this might be occurring or how I can address it? I saw some threads about 'rollback protection' but it seems like that is for people who are not even able to boot into TWRP, or get stuck on the first "Samsung Note 10+", screen rather than the system booting "SAMSUNG" screen.

KiwiNote+ said:
Hey guys,
So I've been trying for days to get a custom Ron installed on N975F.
Right now I'm on completely reflashed stock Rom. With stock recovery et al. No root.
I am able to flash Magisk with Odin. No trouble. And my phone continues as usual without issue.
However, once I install TWRP, no matter where or how I install it, once I restart my phone it will boot past the warnings without issue, then go to the screen that just says "SAMSUNG" and the phone will never actually boot up.
I can still boot into TWRP recovery without issue, but system itself will never boot, it will just sit on the "SAMSUNG" screen forever.
In fact, it seems like as long as TWRP is installed to recovery, my system will never boot with any Rom. It can be fixed by reinstalling stock recovery, or by reflashing stock in it's entirety (which I have now done before I try again).
Has anyone got any ideas why this might be occurring or how I can address it? I saw some threads about 'rollback protection' but it seems like that is for people who are not even able to boot into TWRP, or get stuck on the first "Samsung Note 10+", screen rather than the system booting "SAMSUNG" screen.
Click to expand...
Click to collapse
i am guessing try ADB commands see this link! https://www.koskila.net/how-to-use-twrp-to-flash-an-android-device-that-refuses-to-boot-to-twrp/

Many N975 users have reported this issue and I have forwarded concerned to ian as well. What I believe is formatting on latest (last few) twrp causing issue.
If you have N975/N976 then, visit xda My rom thread - Download area - you will find a folder "for stock rom & bootlooped device" download instructions and follow it, I have wrote guide with or without flashing my rom
Edit :
here is direct link, you will find all required file
https://www.mediafire.com/#0urfw8g1gx630
This guide is stop solution to root/root with twrp/fix Samsung roll back bootloop everything. And yes you don't needs to patch anything yourself, all files available are ready to use

Hi Dr Ketan,
Thanks for the response.
I actually solved the issue simply by using the version of TWRP and following the install instructions on your basic "How to Root and Install TWRP" for Note 10+ guide.
So I think this is a problem relating to Ian's latest TWRP. TWRP linked from your thread
is working fine (but leads to issue with Camera in GSI/Lineage OS ROMs).
I will have a look at your special guide relating to Samsung logo/rollback stuff and see if it will allow me to install latest TWRP from Ian and bypass these issues! Thank you.

KiwiNote+ said:
Hi Dr Ketan,
Thanks for the response.
I actually solved the issue simply by using the version of TWRP and following the install instructions on your basic "How to Root and Install TWRP" for Note 10+ guide.
So I think this is a problem relating to Ian's latest TWRP. TWRP linked from your thread
is working fine (but leads to issue with Camera in GSI/Lineage OS ROMs).
I will have a look at your special guide relating to Samsung logo/rollback stuff and see if it will allow me to install latest TWRP from Ian and bypass these issues! Thank you.
Click to expand...
Click to collapse
Yes, As I said issue is related to newer TWRP only. If you use old TWRP, camera will not work. My above link guide is for latest base and you can get latest TWRP only (Included package are having latest available TWRP & Kernel)