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.

[Q] CM10 m2 Encryption Issue

Ok. I foolishly enabled encryption on my i711 and after putting in the password, the volumes unlock and the system starts. The problem is that if the screen goes off for any reason, the phone reboots. Tried all sorts of things to correct and decided I no longer wanted the phone encrypted. There is no way back. Ok, so I thought I could do a factory reset... No dice. The phone reboots and all is still encrypted and there.
Next I tried clockworkmod but couldn't do ANYTHING there because the encrypted volumes aren't mountable. I couldn't factory reset, install a new rom, etc.
Next I went to ODIN and tried to repartition. No luck there either. I flashed clockworkmod again for good measure and even tried Nand Erase All.
After this I booted into the phone and tried to repartition... Now I have a phone that displays the lovely CM10 boot screen but never gets passed that. I can still get into recovery.
Any thoughts on how to undo the encryption and reflash a rom?

fza99 said:
Ok. I foolishly enabled encryption on my i711 and after putting in the password, the volumes unlock and the system starts. The problem is that if the screen goes off for any reason, the phone reboots. Tried all sorts of things to correct and decided I no longer wanted the phone encrypted. There is no way back. Ok, so I thought I could do a factory reset... No dice. The phone reboots and all is still encrypted and there.
Next I tried clockworkmod but couldn't do ANYTHING there because the encrypted volumes aren't mountable. I couldn't factory reset, install a new rom, etc.
Next I went to ODIN and tried to repartition. No luck there either. I flashed clockworkmod again for good measure and even tried Nand Erase All.
After this I booted into the phone and tried to repartition... Now I have a phone that displays the lovely CM10 boot screen but never gets passed that. I can still get into recovery.
Any thoughts on how to undo the encryption and reflash a rom?
Click to expand...
Click to collapse
I have some very bad news for you.... Encryption is a one way street. Once encrypted the only way back is to flash stock via fastboot.
I can't even start to explain how to use fastboot as I have never been in a situation where I have needed it.
recoveries lose all access on encrypted devices so this is the only way.
Here is some links to get you started... Please do research before you begin the process and make sure you've obtained the appropriate files. I will take no responsibility for bricking your device.
Flashing via Fastboot:
http://forum.xda-developers.com/wik...id#Android_Flashing_Guide_.28with_fastboot.29
Installing Fastboot on Windows:
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Sent from my SGH-I747 using xda app-developers app

[Q] Friend did a bad file flash, Hard bricked phone

Okay my friends wife had an unlucky bad file flash and ended up hard bricking somehow.
And keep this in mind that she never flashed a Int. version.
She flashed the SlimRom 3.1.0-D2SPR then she flashed the custom kernel unlocker file
to use the K747 kernel for slimrom, but the thing was ( She has TWRP ) when she slid the bar to flash
the file, the screen went back to the TWRP home page she waited 5-10 minutes then she tried reflashing the file again
and it said failed. Rebooted and the phone's hard bricked after installing the kernel. ( No LED when USB plugged in for recharge,
No power or haptic feedback. )
Her husband used the same method to install slim rom and his phone is fine
but the screen never went to the TWRP home page, it went straight into installing it.
The thing that boggles my mind is that she flashed everything in order and it hard bricked.
Rom first, rebooted recovery, kernel unlock, cache and dalvik cleared. rebooted recovery
When she tried flashing the K747 AOSP Kernel, she said it never went to the page screen that would show
it install, it just went straight to the home page, retry flashing but failed. ( here's the weird part I've never experienced. )
Is her devices bootloader corrupted? Because all I'm thinking is she's the one in a million of people that has a defective
device itself and a bad flash ( This is what I think ) hard brick her device.
But my suggested solution if correct would be force odin mode via USB Jig or send it in for jtag repairs if possible.
If there is no chance for the both of these solutions then a full blown replacement repair will be the last thing she'll do
because she doesn't have TEP or a warranty on the device.

Spark91 said:
Is her devices bootloader corrupted? Because all I'm thinking is she's the one in a million of people that has a defective
device itself and a bad flash ( This is what I think ) hard brick her device.
But my suggested solution if correct would be force odin mode via USB Jig or send it in for jtag repairs if possible.
If there is no chance for the both of these solutions then a full blown replacement repair will be the last thing she'll do
because she doesn't have TEP or a warranty on the device.
Click to expand...
Click to collapse
So, I'm just going to rattle through my thought process on this, just to get things clear in my mind:
Her phone cannot turn on at all. Do a battery pull/replace and make sure that there's no going into recovery or download mode. If that's the case, then JTAG might be your only solution.
This happened when trying to flash a kernel. It seems unlikely that a kernel would screw up the bootloader. I was under the impression that only recovery zips touch the bootloader/recovery partition.
If the kernel or Rom zip was for an international GS3, then it would try to write to the bootloader partition. But since you said your buddy's phone flashed the same files just fine, it seems unlikely that they flashed the international zips.
I've had TWRP fail to flash a zip. Each time I tried to flash a zip, it would say it failed. All I had to do was reboot into recovery (even if I hadn't flashed a ROM, so I had no system file), and then I could flash the file. Sometimes TWRP had those issues for me. Her story reminded me exactly of when that happened to me, but if hers won't load into recovery (or download mode), that's a major difference.
After all that, I honestly have no clue how this happened. It sounds to me like the JTAG is the best bet. You can find them online for around $60. Sorry this happened, and I hope you find a good fix for your friend's wife.

Its possible that you can still fix this....
Couple questions. When you try to turn it on, what exactly happens? does it vibrate? what occurs?
There is a possiblity that you can bypass the idea of holding the power button and vol button, try to adb reboot recovery command. ive had this save me about 5 times now when flashing goes bad.
http://droidlessons.com/how-to-install-adb-on-a-windows-7-pc/
make sure adb is installed...
while the phone is trying to boot, keep typing or copy/pasting or in cmd pressing up and enter after you enter the command.
adb devices
if it gives you the UID of your phone you at least know that you might have the ability to fix it.
From here just type
adb reboot recovery and it will reboot into the recovery to allow you to flash a "good" kernel again.
Bit of advice.. I am always paranoid after going through this so many times of a bad flash. As a result i never stack flashes.. for instance.
if i want to flash a rom, kernel, modem, radio..
i wipe dalvik, flash rom, wipe dalvik, wipe system, wipe cache.
Reboot let android do its thing...
reboot into recovery.
wipe dalvik, flash kernel, wipe dalvik, wipe system, wipe cache.
reboot, let android fully boot up.
reboot into recovery
wipe dalvik, flash radio, wipe dalvik, wipe system, wipe cache.
reboot...you get the point.
Just precations i started doing because of issues ive had in the past. If you have a mac, the commands are a bit different so let me know...

This is interesting, Hamspiced.
I didn't know that flashing a kernal can "brick" your phone.
Do you happen to know why or how this happens? You allude to stacking flashes... I normally only stack gapps with the ROM, but I was wondering if it's important to reboot and go through the setup prior to flashing gapps.
Thanks for the info!

topherk said:
This is interesting, Hamspiced.
I didn't know that flashing a kernal can "brick" your phone.
Do you happen to know why or how this happens? You allude to stacking flashes... I normally only stack gapps with the ROM, but I was wondering if it's important to reboot and go through the setup prior to flashing gapps.
Thanks for the info!
Click to expand...
Click to collapse
When i had my evo things flashed slightly different.
There were many issues in kernel flashing where if the kernel didnt download properly or you had a bad dl. it will what we called soft-brick. This would allow the phone to "act" like it was booting up but only display a black screen and never boot. Screen would flicker, phone was active but nothing would display and it will not boot loop. kind of just freeze.
We noticed that if we connect the phone to the computer we could actually use adb to access the phone. from there we noticed that we could push recoveries, and even push kernels and radios to the phone even though it wasnt displaying anything.
I figured the easiest way to get through this issue is to see if you can Reboot Recovery through adb if it allows you, and hopefully then you can restore functionality.

Help possibly?
Can you get it into download mode and just use Odin to flash it?

[HELP] I think I screwed up, factory image/bootloader help

EDIT: SOLVED. After some hours at work I was able to boot back to the bootloader and flash the images individually.
TL;DR at the bottom.
Hi, I've been rooting and ROMming for a while now, and last night I made a mistake that set forth a chain of depressing events. I have a N7 2013 LTE, and was running AOKP up until last night. I wanted to flash the 9001 L preview, despite having no access to data. Simple right? Wrong, you forget to realize I'm a tired idiot last night. I downloaded the zip no problem, rebooted to TWRP and commenced my advanced wipe. Some how, I mistakenly checked off "wipe internal storage" during the process. So I go back to the Install screen, and my heart sinks. F***. At this point I decide to let it lie in recovery until tomorrow (today) and keep it charged.
Fast forward to this morning, I'm at the office. My device is charged and waiting in recovery. I decide I'm just going to flash the factory image to stock 4.4 and start with a clean slate, wiping all (even though it's wiped). Reason for factory image and not just adb push the ROM is that I'm having a seemingly-unsolvable issue of incorrect storage. It tells me my 32gb device only has 11.6 gb total storage. This has persisted through multiple clean-wiped installs of various ROMs, but I don't know if it started out like that when I bought it, since I didn't think to check before unlocking and putting a ROM on it.
So I get the SDK and images on my work PC, and commence flash-all.bat. Working great until it gets to system.img, then it fails. Try again twice, same thing. Open the image zip and extract the files, then try to flash one by one, now it's saying the commands are invalid (fastboot flash system system.img, etc). So I wonder, because sometimes these devices are wonky in ADB, maybe it installed and just said it failed? F*** it, I'll try to boot. Google logo for an hour. Ok, cool, I'll go back to the bootloader. NOPE. The device either won't power on at all, or it will get stuck at the splash screen and hang there. Any idea where to begin to fix this?
TL;DR: No OS on phone, failed flashing system.img in flash-all.bat, now device won't boot to bootloader or (missing) OS. Any ideas?

Stuck on Startup

Having some serious trouble. I rebooted my phone and it asked for my password once it was done as always but this time it said it was wrong. I'm certain I used the correct password but even tried my other alternatives to be sure and still a no go. This isn't the decryption option password you get when booting but my lockscreen password. I booted into recovery and it asks me for an encryption password that I never set but I know this is a common issue with twrp. Tried to go back into android but wouldn't let me because of the "wrong" password so I used the failsafe and went into recoveries file manager and deleted my lockscreen settings to remove my lockscreen passcode (tried and proven method, done it dozen times before). Got past my lockscreen this time but now it was saying starting android forever. Figured it was something with the passcode being deleted so I just decidd to factory reset from the recovery and take that loss. NOW the problem is upon booting the rom in trying to start the setup, I'm stuck on the "just a sec..." screen that comes up after you click start. What do I do from here? I cant access anything in recovery because the encryption passcode issue so I'm kind of stuck. Also I'm a work right now and we cant connect our phones (or any USB for that matter) to the computers and laptops because theyre government property and on a secured line. Any help PLEASE, Ill be home later and can try more then.

Well since you already did a factory reset on the device you mine as well just do a clean install of the OFW then get twrp back and flash your ROM etc back. Would probably be better then to deal with everything going on with the device right now.

loeffler23 said:
Well since you already did a factory reset on the device you mine as well just do a clean install of the OFW then get twrp back and flash your ROM etc back. Would probably be better then to deal with everything going on with the device right now.
Click to expand...
Click to collapse
Hey, I got my phone back working after that and rooted again and flashed same rom. NOW another problem, I rebooted my phone and its not accepting my PIN anymore, nor my fingerprint, and I cant reset through TWRP because of encryption. WTF is the issue, how do I fix this or do I have to flash-all again?