***unlocked***
shooter xc ship s-on RL
hboot 1.50.0000
radio -0.97.10.000
emmc-boot
aug 7 2011
I have a hand me down Sprint evo 3d that I believe has the HTC dev unlock. I attempted to install the following OTA update.
- OTA_Shooter_S_Sprint_WWE_2.08.651.3-2.08.651.2_release_2201598na37g8l1af4e904
The phone restarted during the update and went to the exclamation screen with the blue android guy. I can get into hboot but when I try to get into recovery the phone boot loops again.
I have been reading for hours and have found several suggestions but do not know where to go from here. From what I can tell I need to re-flash a rom and/or flash a recovery image but but I am not sure exactly what versions of either is needed, where I would get it or if any prior steps are required due to the phones current configuration. I am also not sure how to complete this as from what I can tell, I may have trouble due to the 1.5 boot loader. As much as I would like to try a few things on my own, I don not want to cause more damage or more work for myself.
A few notes.
- I am using a MAC
- I have the android SDK installed but am not familiar with any commands.
- I do not know what version of android I had installed prior to the attempted updated other then I am sure it was a stock HTC load.
- I have not done anything other then try to load recovery since the boot loop
- I can not locate a back up on the SD card.
- I have access to a external SD card reader
- I have access to a external battery charger.
Any help would be much appreciated.
flash stock recovery, lock your bootloader then run the ota exe. But why on earth are you flashing the old gingerbread ruu when ICS is available?
mnomaanw said:
flash stock recovery, lock your bootloader then run the ota exe. But why on earth are you flashing the old gingerbread ruu when ICS is available?
Click to expand...
Click to collapse
I attempted to flash the recover using recovery image you posted in another thread.
mnomaanw said:
Not all recoveries work on hboot 1.50 . I got only two working
First boot in bootloader by pressing volume down+power button, then select fastboot and flash this recovery http://www.mediafire.com/?n72emuv5a1c00sd
after flashing recovery , flash a boot.img from the ROM you want to use from fastboot (sorry dont know mac commands)
And then just follow the steps from step no 6 from the link given below.
You should flash the same ROM(MIUI is used in post below) from which you have flashed the boot.img above.
http://forum.xda-developers.com/showpost.php?p=19967637&postcount=16
necessary file are attached in the post and you should put them on SD card
If the above recovery wont boot ....try the recovery from this post
http://forum.xda-developers.com/showpost.php?p=19944274&postcount=9
Click to expand...
Click to collapse
The phone rebooted back into the boot loop. I can still access hboot but am not able to access recovery. I may be using the wrong method or commands.
Input:
./fastboot-mac boot ./recovery.img
Output:
downloading 'boot.img'... OKAY
booting... OKAY
Here is what I get in the fast boot help menu...
usage: fastboot [ <option> ] <command>
commands:
update <filename>.................................reflash device from update.zip
flashall..................................................flash boot + recovery + system
flash <partition> [ <filename> ]...............write a file to a flash partition
erase <partition>...................................erase a flash partition
getvar <variable>..................................display a bootloader variable
boot <kernel> [ <ramdisk> ]...................download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ].....create bootimage and flash it
devices.................................................list all connected devices
reboot....................................................reboot device normally
reboot-bootloader....................................reboot device into bootloader
options:
-w...............................................erase userdata and cache
-s <serial number>.......................specify device serial number
-p <product>................................specify product name
-c <cmdline>...............................override kernel commandline
-i <vendor id>...............................specify a custom USB vendor id
Do you know if I am attempting to flash the recover correctly? It appears as if it is looking for a boot.img from a rom.
To answer your question, the original goal was to update to ICS. I was not aware that the the phone was dev unlocked and never considered that the OTA would cause a problem. I thought it was odd that the available OTA it offered was GB but wrote it off as potentially requiring a series of sequential updates to arrive at the latest version.
After reading this thread I tried flashing again....
http://forum.xda-developers.com/showthread.php?t=1592922
Input:
/fastboot-mac flash recovery recovery.img
Output:
sending 'recovery' (5068 KB)... OKAY
writing 'recovery'... OKAY
The phone went back into a boot loop. I am essentially back to were I started.
I would assume the above procedure is correct. Other then trying other recovery images, I am not sure where to go from here.
I flashed the CWM image from this link as well with no luck.
http://forum.xda-developers.com/showpost.php?p=19944274&postcount=9
Still no luck here. Does anyone think the problem flashing the recovery has anything to do with s-on? I found this link related to the legend and think it may apply.
http://forum.xda-developers.com/showthread.php?t=1290841
I obviously have not tried it because the linked CWM appears to not apply to my phone and I found nothing on CWM's site that would apply.
I am not specifically looking to go stock. I just would like to get the phone working again. Do I need to get recovery working to flash this? Should I just be looking for rom and using hboot with PG86IMG.zip on the SD card? Any input on this would be very much appreciate.
you should not boot the stock recovery , it will never work.
you should flash it to your device. then take the ota .
if it does not work, lock your bootloader after flashing stock recovery , then take OTA.
I'm having the same problem, boot loop after trying to flash the new OTA zip from the development section now no matter what ROM I flash nothing works. Do I have to try and relock the boot loader then run the stock RUU?
Sent from my cm_tenderloin using xda premium
mnomaanw said:
you should not boot the stock recovery , it will never work.
you should flash it to your device. then take the ota .
if it does not work, lock your bootloader after flashing stock recovery , then take OTA.
Click to expand...
Click to collapse
Thank you, I was not aware of that. However, I should be able to flash custom recoveries while unlocked s-on correct? I have tried flashing quite a few custom recoveries and am still unable to boot into recovery using hboot or ./fastboot-mac boot (recovery).img.
I plan on working on it more tonight and if I can get it working I'll be sure to post the resolution for other experiencing the same issue. Thanks again for your help.
I just relocked my bootloader and went back to stock Ill mess with it later but at least it works now.
That is great, thanks for the update. I'll give it a shot after work and report back. I got hung up on not being able to get a stock or custom recovery loaded. I was worried about not using recovery to "clean up" before moving on.
Out of curiosity, what method did you flash your rom?
I used the touch recovery then it went to bootloop so I re locked the bootloader and ran the stock RUU, then updated to the OTA 4.0.
Sent from my PG86100 using xda premium
malicenfz said:
I'm having the same problem, boot loop after trying to flash the new OTA zip from the development section now no matter what ROM I flash nothing works. Do I have to try and relock the boot loader then run the stock RUU?
Sent from my cm_tenderloin using xda premium
Click to expand...
Click to collapse
Did you actually flash the OTA successfully and no roms would boot afterward?
You can't take the ota if you are unlocked. Flash twrp 2.2.0 (directions are on their site), then flash a custom rooted ROM. Since you are s-on, you will have to flash the kernel properly (using fastboot or flash image GUI). I recommend you get s-off.
I would give you links, but I'm on my phone. Google is your friend.
Save the Drama for your Mama with Tapatalk 2
Wow Thanks Guy. I used this method to stop boot-loops with 4.0 Rom and it worked like a charm.
Related
hi all,
I just soft bricked my evo 3d, who will kindly help me?
My new htc evo 3d just go in trouble: when I rebooted yesterday it just boot loop, then I googled and tried my methods to make it boot, all failed!
My evo 3d is hboot 1.5, and I followed htc method to unlocked it, and tried ruu from goo-inside.me/shooter/ruu ( md5sum checked), but failed to boot up.
Then, I tried:
fastboot erase boot
give thus result:
erasing 'boot'...
FAILED<remote:not allowed>
But It seemed that the command "fastboot flash boot boot.img" successful:
sending 'boot' < 3604 KB>...
OKAY [1.016s]
writing 'boot' ...
OKAY [ 8.468s]
finished..
But, I unlocked with htc method, and I can see ***UNLOCKED*** when get into fastboot, why I can not erase boot and any other partitions? So I guess flash boot successful just a fake?
Am I right? What should I do next?
Thanks in advance!
I'm sorry for my English!
I mean, my evo 3d has HBOOT 1.5, and now go in trouble of boot loop.I have followed htcdev.com to unlocked the bootloader, and have tried:
* after unlocked the bootloader,tried twrp-1.0.3, cwm-4.1.0.4 recovery, but all failed to boot into, just stop @ splash screen.
* then I relock with 'fastboot oem lock', and flash with ruu 2.08.651.2, but still failed to escape from boot loop.
* then I unlock it again, and tried 'fastboot erase boot' and want to reinstall boot partition, but failed when running 'fastboot erase boot', please refer to #1 post.
So I think HTC unlock method maybe a suck? if I can not erase the old boot partion, how can i write to boot partion? Am I right?
Thank for any help!
EDIT: I found that after boot loop some times(maybe 10 times), the phone will become very hot, especially around the camera, I don't know why.
Go y htcevohacks.com and follow the really easy steps there to do unlock, get recovery, and super user to all work well. I used these steps and had no problem. I running clean ROM and a custom kernel.
---------- Post added at 03:05 PM ---------- Previous post was at 02:59 PM ----------
There are only 2 recoveries working for the HTC way they have been modified to work with the hboot 1.5 the htcevohacks.com way has a zip file that has everything you need to do the recovery and superuser. Just read the threads and you can find more detailed instructions....
jamesjeter1 said:
Go y htcevohacks.com and follow the really easy steps there to do unlock, get recovery, and super user to all work well. I used these steps and had no problem. I running clean ROM and a custom kernel.
---------- Post added at 03:05 PM ---------- Previous post was at 02:59 PM ----------
There are only 2 recoveries working for the HTC way they have been modified to work with the hboot 1.5 the htcevohacks.com way has a zip file that has everything you need to do the recovery and superuser. Just read the threads and you can find more detailed instructions....
Click to expand...
Click to collapse
Thanks jamesjeter!
I have followed htcevohacks' method, but can not enter into recovery, everytime when I select recovery from fastboot, it just boot into normal mode and stuck at the splash screen with HTC logo and then boot loop.
I have tried fastboot boot cwm-4.0.1.4-shooter.img or fastboot flash recovery cwm-4.0.1.4-shooter.img, all failed.
I just can not enter into recovery.
I don't know it is a software brick or a hardware brick? and anyway I can break the boot loop?
Thanks in advance!
do you ever get everything working. Im still stuck trying to get into recovery
MWaV said:
do you ever get everything working. Im still stuck trying to get into recovery
Click to expand...
Click to collapse
You also posted this question in my Flash Image GUI thread. I'll provide you the same answer here:
Steps 1 - 3 will work having used AlphaRevX's revolutionary method. Steps 1 & 3 will work having used HTC's unlock method. The two methods unlock the internal memory write protection differently, hence the difference in steps for flash a custom recovery on the EVO 3D.
1) Flash from normal android mode: My application works well for this, Flash Image GUI, as well as flashing kernels, especially when being away from or not having a computer available.
2) Flash through the bootloader by putting a PG86IMG.zip file on the root of your sdcard. This file with the recovery.img loaded inside is available at the TWRP site.
3) Flash through fastboot by using the following command: fastboot flash recovery c:\downloads\twrp-recovery.img
Hope that helps!
thanks bro, sorry about the double post
subaochen said:
Thanks jamesjeter!
I have followed htcevohacks' method, but can not enter into recovery, everytime when I select recovery from fastboot, it just boot into normal mode and stuck at the splash screen with HTC logo and then boot loop.
I have tried fastboot boot cwm-4.0.1.4-shooter.img or fastboot flash recovery cwm-4.0.1.4-shooter.img, all failed.
I just can not enter into recovery.
I don't know it is a software brick or a hardware brick? and anyway I can break the boot loop?
Thanks in advance!
Click to expand...
Click to collapse
i used the TWRP recovery for Hboot 1.50 http://www.mediafire.com/?n72emuv5a1c00sd Put the recovery.img on the root of sd card.
type:fastboot boot recovery.img
Hope that helps
I think I got your answer. Relock phone with HTC method and then reflash ruu complety and reroot with HTC method.
Sent from my Nocturnal 3D using xda premium
hi all
Forgot to charge my EVO 3D (CDMA) and battery completely drained. Even after using another fully charged battery my phone goes to bootloop - just shows the HTC logo and reboots again and again. Here is what I have:
hboot : 1.5 (S-ON)
radio : 1.06.00.1216
ota : 2_17.651_5
(I am using this phone in India activated on Reliance)
As the phone doesn't boot I can't access it thru adb to give command 'adb reboot bootloader'
I can get bootloader by pressing vol_down+power
When I run the 2_17.651_5 RUU (exe) from my computer while phone is on fastboot, it completes successfully without errors. But still on reboot it just stays at the htc screen and reboots (guess it's becoz stock kernel not getting flashed as the phone is s-on)
kindly help to get back my phone boot again
thanks and regards
ananth
R.I.P
Sent from my HTC.EVO.3D.Xda Premium
Don't listen to the previous guy. Try using fastboot OEM lock and then ruuing. Or, try getting freezas stock kernel and extracting the boot.IMG and flashing it thru fastboot. Or, you could use fastboot flash recover recovery.IMG to get twrp or clockworkmod and do a superwipe and try flashing a new Rom. There are tons of options if you still have fastboot.
Sent from my HTC popout book.
jdeoxys said:
Don't listen to the previous guy. Try using fastboot OEM lock and then ruuing. Or, try getting freezas stock kernel and extracting the boot.IMG and flashing it thru fastboot. Or, you could use fastboot flash recover recovery.IMG to get twrp or clockworkmod and do a superwipe and try flashing a new Rom. There are tons of options if you still have fastboot.
Sent from my HTC popout book.
Click to expand...
Click to collapse
Thanx for responding. As I mentioned earlier,I have already relocked and RUU'd the exe file,but though it runs without errors doesn't solve problem. Again as it is s-on doesn't permit to flash boot.img. Though I am able to flash twrp recovery, not able to get into recovery from fastboot. Thanks again, really appreciate your help.
ananth001 said:
Thanx for responding. As I mentioned earlier,I have already relocked and RUU'd the exe file,but though it runs without errors doesn't solve problem. Again as it is s-on doesn't permit to flash boot.img. Though I am able to flash twrp recovery, not able to get into recovery from fastboot. Thanks again, really appreciate your help.
Click to expand...
Click to collapse
You don't need to relock once you unlock the HTC way. Just unlock the phone then flash via fastboot the boot.img and then ruu if you want.
Sent from my PG86100 using Tapatalk
megabiteg said:
You don't need to relock once you unlock the HTC way. Just unlock the phone then flash via fastboot the boot.img and then ruu if you want.
Click to expand...
Click to collapse
thanks. extracted boot.img from freeza's kernel and flashed from fastboot after unlocking. But still doesnt solve problem. Can you give me a link for boot.img
Pleassssssse HELP !!!!!!
I have the exactly the same problem, a full reboot result in boot loop, and can not fix it by now.
I guest the phone is rooted before OTA, so OTA can not flash kernel successfully because the wrong signature, and the phone will not boot because the wrong kernel.
I have tried ruu, fastboot boot recovery.img and etc, all failed.
The key point is that, the phone is rooted and you tried OTA. HTC OTA must have a stupid bug, it can not recovery from a partial update, or automatically roll back becasuse of the partial update, dem!
Please have a look at the guide/flashing notes in my signature. If u r unlocked u are likely not entering recovery correctly.
If u are trying to flash the Ruu u have to be locked or relocked. If u cant boot to android, run the xhausx's full Ruu zip from bootloader.
Sent from my PG86100 using Tapatalk
mpgrimm2 said:
Please have a look at the guide/flashing notes in my signature. If u r unlocked u are likely not entering recovery correctly.
If u are trying to flash the Ruu u have to be locked or relocked. If u cant boot to android, run the xhausx's full Ruu zip from bootloader.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
1) flashed RUU (exe) after relocking - flash completed without errors
2) ran xhausx's full RUU zip (PG86IMG_2.17.651.5.zip) from bootloader (could get into bootloader by pressing volum_up + power button. adb cannot connect to phone (as phone does not boot), to run 'adb rebooot bootloader')
But still doesn't solve problem and phone keeps rebooting, apparently kernel has not flashed properly.
Please help !!!1
ananth001 said:
1) flashed RUU (exe) after relocking - flash completed without errors
2) ran xhausx's full RUU zip (PG86IMG_2.17.651.5.zip) from bootloader (could get into bootloader by pressing volum_up + power button. adb cannot connect to phone (as phone does not boot), to run 'adb rebooot bootloader')
But still doesn't solve problem and phone keeps rebooting, apparently kernel has not flashed properly.
Please help !!!1
Click to expand...
Click to collapse
You need to use the RUU 2.17 exe after you relock your phone... Then flash a copy of CWM or TWRP on it..
Then adb
fastboot boot recovery.img
Wipe and flash whatever you want
Just noticed u said India & carrier is reliance. Why would u be using a Sprint USA CDMA Ruu? Shouldn't u be using a GSM RUU version?
Sent from my PG86100 using Tapatalk
mpgrimm2 said:
Just noticed u said India & carrier is reliance. Why would u be using a Sprint USA CDMA Ruu? Shouldn't u be using a GSM RUU version?
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
I wonder the same thing all I saw was 1.5
Sent from my PG86100 using xda premium
mpgrimm2 said:
Just noticed u said India & carrier is reliance. Why would u be using a Sprint USA CDMA Ruu? Shouldn't u be using a GSM RUU version?
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Reliance has both CDMA as well as GSM service in India. Mine is a Reliance CDMA MDN.
thanks and regards
reaper24 said:
You need to use the RUU 2.17 exe after you relock your phone... Then flash a copy of CWM or TWRP on it..
Then adb
fastboot boot recovery.img
Wipe and flash whatever you want
Click to expand...
Click to collapse
Yeah , as I mentioned earlier, I also tried using the RUU 2.17 exe after relocking (RUU completed successfully without errors) , and flashed twrp recovery from fastboot . But still it's a no go.
(Again would like to repeat that I can't boot into bootloader from adb - adb cannot connect as phone doesn't android boot. I get into fastboot by pressing vol_down + power)
thanks all for your responses and help, hope you all will continue guiding me till I get this done.
ananth001 said:
Yeah , as I mentioned earlier, I also tried using the RUU 2.17 exe after relocking (RUU completed successfully without errors) , and flashed twrp recovery from fastboot . But still it's a no go.
(Again would like to repeat that I can't boot into bootloader from adb - adb cannot connect as phone doesn't android boot. I get into fastboot by pressing vol_down + power)
thanks all for your responses and help, hope you all will continue guiding me till I get this done.
Click to expand...
Click to collapse
Have you tried to just run the RUU like you said boot turn debug on .... Then go to hboot flash your recovery...
Then fastboot boot recovery.img.
This should work I have unrooted my phone 3 times already in the past month Trial and Error on my part adb always found my phone...
I am tryin to figure out what is going wrong on the last part with TWRP...
Since you said after you do that it was a no go? What happend ? Adb should still be working since you just flashed the recovery...
Anyways I hope you get it solved man I am tryin to figure this problem out.
Do you have a rom already ready to be flashed on your SD card?
Problem is, since i’m not able to android boot I can't reboot bootloader from adb, as I can't connect adb without the phone normal booting. When I boot it just stays at the HTC white screen.
I have flashed twrp recovery from fastboot, but when I give command 'fastboot boot <twrpxxxxx>.img it just boots back to the HTC splash screen
You can go back to complete stock if you rename the RUU file PG86IMG.zip and load onto the root of sd card. Get into bootloader with [power+volume down] and it will automatically detect and load the zip file. This can only be done if you are relocked. I did this in order to get the latest update. After you get back to stock you can unlock and root again.
Android Cowboy said:
You can go back to complete stock if you rename the RUU file PG86IMG.zip and load onto the root of sd card. Get into bootloader with [power+volume down] and it will automatically detect and load the zip file. This can only be done if you are relocked. I did this in order to get the latest update. After you get back to stock you can unlock and root again.
Click to expand...
Click to collapse
As I mentioned in earlier post, have tried flashing PG86IMG.zip from bootloader, but still phone doesn't boot properly and is in a bootloop.
You've used the following file and done these exact steps and allowed the phone to boot to full stock OS? (assuming 2.17.651.5 is correct version)
OPTION 2 - RUU.zip info:
I prefer the .exe version but xHausx’s “FULL” PG86IMG_2.17.651.5.zip may work for you (must be renamed PG86IMG.zip). Make sure you have plenty of battery/charge left!
- (XDA) Xhausx full PG86IMG.zip RUU images (651.5 zips)
PG86IMG_2.17.651.5.zip http://forum.xda-developers.com/showpost.php?p=21593454&postcount=564
MD5: 8F82C2D8F98C077AF775266064BACB5D
From Scrosler's zip Directions : http://forums.androidcentral.com/htc-evo-3d-rooting-roms-hacks/107641-how-return-100-stock-all-versions.html
Scrosler; said:
USE ONLY FOR EMERGENCY PURPOSES. THIS OVERWRITES EVERYTHING!!!!
**THIS WILL RETURN YOU TO FRESH OUT OF THE BOX**
You will not need any special drivers loaded, etc...
1.Download the stock ROM ZIP image from here: and rename it "PG86IMG.zip"
2.Copy it to SD Card
3.Reboot phone into hboot mode by holding volume down and then press power.
Keep volume down held until you boot into hboot mode.
4.In hboot mode the phone will scan the SD card with the image. Once it finds it will ask you if you want to update. Press "Power" to update.
5.Wait.... For a while. When it gets to "system" it will loop a few times. Its quite nerve wracking actually but after about 5 or 6 times it will complete.
6.Once the entire flash is complete it will prompt you to "press power to reboot." Press power and your phone will reboot to 100% stock ROM.
Click to expand...
Click to collapse
Hi,
I've been searching through posts for help. But I might have run into a combination of bad luck and noobness, and I can't perform any suggested recovery procedure that I've found smoothly. If you think my problem can be solve by another answered post please link.
My phone was rooted (from the HTCDev tool) and sim unlocked. This morning I started the Update pushed from HTC (that should be the ICS update???). The update last more than 40 minutes (I wasn't watching) and stuck on the HTC boot screen. I thought it's problem hanged, unplugged the battery (maybe I noobed out here? shouldn've waited 4 hours? or do a hard reset instead?).
Anyway, from that point onward it's hang on boot.
I boot it up the the hboot menu. Go to recovery, tried wiping the cache, tried the factory reset. No luck.
Here is what I have on HBOOT
*** UNLOCKED ***
SHOOTER_U PVT SHIP S-ON RL
HBOOT_1.49.0008
eMMC-boot
Jul 15 2011, 14:39:25
When I tried to run the "update from SD card" in the recovery mode I always get the
E:can't open /cache/recovery/command
no matter what I've put in the SD card
When I try to use 4EXTRecovery, it always says error: device not found
I also tried to use revolutionary to turn S-OFF but it always stuck on waiting for device
the fastboot command line from HTC Dev however, can talk to the phone slightly...
fastboot devices
HT17WV302432 fastboot
fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.007s]
finished. total time: 0.150s
But the phone doesn't turn to the unlock agreement page, phone remains S-ON.
I don't have CWM installed on my phone yet. And I don't know how to get it onto my phone with market place. Putting update.zip in SD card doesn't seem to trigger the phone in any way.
At this point, I think I should?
S-OFF my phone?
See if I can use fastboot to flash any workable ROM / boot / Recovery onto the phone?
Any help would be great.
Thanks a lot.
Gil
If I remember correctly to update to the official OTA you need to put the stock recovery back on your phone and re-lock it.
I don't really care whether it is official OTA or not. I just want to get my phone back to work. Do you have any link to where I can get the OTA and how to do it?
Does it require turning S-OFF? I'm under the impression it is blocking me to do anything. And because my phone is already in a bad state a lot of the tools is not communicating with the phone right now...
No luck with the OTA. I was able to get CWM onto recovery through fastboot, and also tried flashing King Cobra. But the phone still won't be with King Cobra, I'm still on S-ON. Revolutionary still won't connect.
u dont need s-off with 4ext recovery
I had an unlocked EVO3D (htcdev method) and the problem you had happened to me too. The phone stuck at the initial splashscreen and iI had to pull the battery off.
To have my phone back it was enough to use 4ext to restore a saved backup I had
done previously.
If you dont have backups then installing KingCobra (1.5, I have issues with 1.6) should be enough to solve. Copy the rom to the sdcard and then install it via 4EXT.
If you want to go S-OFF i recommend to use the wire-trick method
unlimited.io/juopunutbear-public-beta-0-1/instructions
It's tricky indeed but works very well.
kernBeros said:
I had an unlocked EVO3D (htcdev method) and the problem you had happened to me too. The phone stuck at the initial splashscreen and iI had to pull the battery off.
To have my phone back it was enough to use 4ext to restore a saved backup I had
done previously.
If you dont have backups then installing KingCobra (1.5, I have issues with 1.6) should be enough to solve. Copy the rom to the sdcard and then install it via 4EXT.
If you want to go S-OFF i recommend to use the wire-trick method
unlimited.io/juopunutbear-public-beta-0-1/instructions
It's tricky indeed but works very well.
Click to expand...
Click to collapse
How do you get 4EXT onto the phone? Is there anyway to flash it to recovery? Or do you already have it flashed before? I was trying to find a 4EXT recovery flash but no luck.
I tried using CWM flashed to the recovery and installed King Cobra, it installed but still doesn't boot up. I also tried flashing boot.img onto boot (by using fastboot) but the phone still doesn't boot up. The firmware (PG86IMG.zip) wouldn't flash tho, so maybe I need either S-OFF or 4EXT to do that.
Thanks.
gyt2wong said:
How do you get 4EXT onto the phone? Is there anyway to flash it to recovery? Or do you already have it flashed before? I was trying to find a 4EXT recovery flash but no luck.
I tried using CWM flashed to the recovery and installed King Cobra, it installed but still doesn't boot up. I also tried flashing boot.img onto boot (by using fastboot) but the phone still doesn't boot up. The fireware (PG86IMG.zip) would flash tho, so maybe I need either S-OFF or 4EXT to do that.
Thanks.
Click to expand...
Click to collapse
=================================================================================
DISCLAIMER: I AM NOT RESPONSIBLE IF YOU BRICK / RUIN YOUR PHONE IN ANY WAY.
=================================================================================
4Ext was already flashed. However what you did should be ok. Are you sure that the boot.img that you flashed is the correct one for the ROM that you installed?
The boot.img on the KingCobra main page belongs to the 1.6 version.
You can extract the correct one for the 1.5 version from the ROM zip file.
The path in the zip file is Custom/Kernels/Stock/boot.img
I used the 1.5 version with the original radio without problems.
Fixed this by:
1) Getting the official RUU on ICS.
2) Connect USB in HBOOT
3) Use fastboot to relock the bootloader
4) Run RUU on Windows and successfully flashed everything
So seems like S-ON pluse unlocked bootloader means no no to both official rom and custom rom.
Helloo xda developer forums!
I have a problem with my GSM HTC evo 3d when flashing new roms :crying:
I unlocked it the htc way, installed 4ext touch recovery and
rooted my stock rom using the superuser app.
But whenever i try to flash boot.img from a custom rom,
nothing changes. i tried rebooting several times but i
still have the same rom!!!
Whenever i type fastboot flash boot boot.img this happens:
sending 'boot' (4852 KB)...
OKAY [ 0.931s]
writing 'boot'...
OKAY [ 4.506s]
finished. total time: 5.439s
I am a true noob at android stuff so if i made any stupid mistakes please help me or direct me to the right thread so i wont make stupid mistake anymore
Thank you for your help in advance!!
More info would be helpfully, firstly what is your hboot? Are you s-on or s-off? What Rom did you flash? You are have issues with bootloops after you flash a rom?
(My evil evo is snake bitten by venom sense 4.1 rom and also infected with THE kernel,don't ask me for help, as I couldn't care less if you phone explodes)
Jaklo said:
Helloo xda developer forums!
I have a problem with my GSM HTC evo 3d when flashing new roms :crying:
I unlocked it the htc way, installed 4ext touch recovery and
rooted my stock rom using the superuser app.
But whenever i try to flash boot.img from a custom rom,
nothing changes. i tried rebooting several times but i
still have the same rom!!!
Whenever i type fastboot flash boot boot.img this happens:
sending 'boot' (4852 KB)...
OKAY [ 0.931s]
writing 'boot'...
OKAY [ 4.506s]
finished. total time: 5.439s
I am a true noob at android stuff so if i made any stupid mistakes please help me or direct me to the right thread so i wont make stupid mistake anymore
Thank you for your help in advance!!
Click to expand...
Click to collapse
re-read the steps on flashing a ROM...youll find out you need more than just the boot.img file to do it... only time you should have to flash the boot.img is when a new rom is installed but wont boot up...if your phone still boots then youre not installing the ROM properly
You need to supply the information that flashallthetime requested, but you should also be aware that flashing boot.img from fastboot does not flash the ROM and doesn't even flash all the files associated with the kernel. The attached screenshot of the warning that comes up in 4EXT when selecting the "flash boot.img" option expains it better than I can.
If you are S-ON, the proper way to flash a ROM is to "fastboot boot recovery.img" then flash the entire ROM .zip file from recovery, or use 4EXT with the S-ON (SmartFlash) option enabled. You can tell that SmartFlash is working by watching to see if your phone boots twice after your exit recovery. The first boot is used to flash the boot partition and the second boot loads the new kernel and ROM.
Don't confuse the complete kernel with boot.img, which is only one of the files required.
ramjet73
thank you for your replies!!
flashallthetime my hboot version is 1.53.0007 and i am s-on.
I tried to flash the Cool-ICS and the cerom.
ramjet73 i tried flashing several diffrent roms(inclucing both of the above) with the 4ext smartflash enabled, but i only got to the animation an then
the whole process froze. And thank you for the explenation with fastboot i was only flashing the boot.img
i guess this is a total noob question but when i type fastboot boot recovery.img it says thatit cannot load recovery.img Where do i get this file from?
Or can you please link me to the thread with more noob friendly info on flashing roms with s-on?
Jaklo said:
thank you for your replies!!
ramjet73 i tried flashing several diffrent roms(inclucing both of the above) with the 4ext smartflash enabled, but i only got to the animation an then
the whole process froze. And thank you for the explenation with fastboot i was only flashing the boot.img
i guess this is a total noob question but when i type fastboot boot recovery.img it says thatit cannot load recovery.img Where do i get this file from?
Or can you please link me to the thread with more noob friendly info on flashing roms with s-on?
Click to expand...
Click to collapse
I'm not familiar with the S-ON flashing guides for GSM which will be a little different than those for CDMA, so someone else will have to help with that, but you can get the recovery.img file for 4EXT that you need from the OP of the XDA thread. It's right above the other download links on that page. Look for the following sentence that has the download link embedded:
If you somehow lost those files, there's a direct download for a version you can flash via fastboot.
Click to expand...
Click to collapse
ramjet73
the "fastboot boot recovery.img" is just a command to get into recovery. You could also use the command "adb reboot recovery" (unless you are in bootloader mode)
I think the problem is your hboot. loads of people have problems with the newer roms because of the 1.53.xxxx hboot
EM|NEM said:
the "fastboot boot recovery.img" is just a command to get into recovery. You could also use the command "adb reboot recovery" (unless you are in bootloader mode)
I think the problem is your hboot. loads of people have problems with the newer roms because of the 1.53.xxxx hboot
Click to expand...
Click to collapse
Thanks again for the quick replies!!!
Ok i got it, but if i am in fastboot and execute fastboot boot recovery.img i get an error , but if i execcute the adb command i get into the recovery normaly.
Have you got any idea on how to fix the hboot problems?
If not is there any easy way of downgrading the hboot except the wire trick becose it looks very dangerous and i realy dont wanna brick my phone.
Jaklo said:
Ok i got it, but if i am in fastboot and execute fastboot boot recovery.img i get an error , but if i execcute the adb command i get into the recovery normaly.
Have you got any idea on how to fix those problems?
If not is there any easy way of downgrading the hboot except the wire trick becose it looks very dangerous and i realy dont wanna brick my phone.
Click to expand...
Click to collapse
What error do you get when you try the "fastboot boot recovery.img" command? You have to be in the "fastboot USB" mode in the bootloader to run fastboot commands and if you were the ADB commands wouldn't work which require being booted into Android with "debug" on in the developer settings.
ramjet73
ramjet73 said:
What error do you get when you try the "fastboot boot recovery.img" command? You have to be in the "fastboot USB" mode in the bootloader to run fastboot commands and if you were the ADB commands wouldn't work which require being booted into Android with "debug" on in the developer settings.
ramjet73
Click to expand...
Click to collapse
i know that i have to be in fastboot usb mode
it gives me cannot load recovery.img error.
Buuuuut i finaly managed to install yoda´ s ICS custom ROM and EVERYTHING workssss
THX guys
Theres no way to downgrade your hboot without the wire trick my friend. you need s-off to downgrade your hboot. any older hboot could have easily been downgraded and then s-offed
I would suggest you try some other rom. This ones a pretty good rom (sense 4.1 but no 3d) and i'm sure it works with s-on/1.53
http://beta.androidfilehost.com/?fid=9390113915771289764
as always wipe then flash rom in recovery
then flash boot.img from fastboot and reboot
---------- Post added at 03:50 AM ---------- Previous post was at 03:46 AM ----------
oh good you already did another rom. good for you
EM|NEM said:
as always wipe then flash rom in recovery
then flash boot.img from fastboot and reboot
Click to expand...
Click to collapse
ok sorry for a noob question but does wipe mean factory data reset?
that is what i meant. do factory data reset and wipe dalvik cache as well
ramjet73 said:
What error do you get when you try the "fastboot boot recovery.img" command? You have to be in the "fastboot USB" mode in the bootloader to run fastboot commands and if you were the ADB commands wouldn't work which require being booted into Android with "debug" on in the developer settings.
ramjet73
Click to expand...
Click to collapse
The OP cant load his recovery because he might not have a file named "recovery.img" in his fastboot/adb folder.
Flashing a boot.img is just the part of flashing ROM, especialy on S-On state. It still has not flashing your ROM, until you "update from *.zip file" from recovery.
SOLVED
Hey, I have htc evo 3d gsm (shooteru). I unlocked the bootloader using htcdev.com and installed clockworkmod recovery. Then I changed cid to HTC__001 and tried to flash a gingerbread ROM in preparation for using the flashmaniac tool to downgrade my hboot (1.53.0007 -> 1.49.0007).
But when I tried to flash the gb rom the recovery said that installation finished but the phone did nothing after reboot. So I took out the battery and went into bootloader and everything looked the same as before the flash attempt. So I tried once again with same result. Then I powered off the phone and now when I turned it on again it only shows the HTC logo for a few seconds and then nothing (the buttons at the bottom have their lights turned on though).
Any ideas?
Yes, hboot version not compatible with gb rom, and or boot partition didn't get flashed. Unlocked but s-on doesn't let boot partition have write if booted into recovery in a normal way.
So yoy can get boot.img from install zip and flash with fastboot
fastboot flash boot boot.img
Or you can reinstall from recovery if booted from fastboot command.
fastboot boot recovery.img
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
Yes, hboot version not compatible with gb rom, and or boot partition didn't get flashed. Unlocked but s-on doesn't let boot partition have write if booted into recovery in a normal way.
So yoy can get boot.img from install zip and flash with fastboot
fastboot flash boot boot.img
Or you can reinstall from recovery if booted from fastboot command.
fastboot boot recovery.img
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Click to expand...
Click to collapse
Somehow got it at least to bootloader, no idea how, just tried taking out battery a few times and charging it a bit and it worked.
Thanks for the advice, didn't realize there was a difference between these flashing methods.
randomguyhtc said:
Somehow got it at least to bootloader, no idea how, just tried taking out battery a few times and charging it a bit and it worked.
Thanks for the advice, didn't realize there was a difference between these flashing methods.
Click to expand...
Click to collapse
Power + volume down when turning on will get you into bootloader
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
Power + volume down when turning on will get you into bootloader
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Click to expand...
Click to collapse
I know , it just didn't work for some reason before.
So I flashed the boot.img and now it's stuck in a boot loop. Tried going to cwm recovery and wiping various caches etc and flashing again, and flashing boot.img again but it still goes into boot loop.
I would just use the flashmaniac's tool anyway because I don't care about any data on the phone or anything, but it seems that it requires the phone to be booted before it can start the downgrade.
What should I do? Try to flash other roms maybe? The one that I have now is EU_Shooter_U-1.20.401.8_ROOTED.
So I extracted a rom.zip from a RUU but it won't flash from cwm "Can't open /sdcard/rom.zip (bad)", should I try to flash it with adb/fastboot? I'm worried that the zip may be broken (even though archive manager integrity check says its fine).
Would this work with shooteru/GSM?
[TOOL] Ultimate Recovery Tool 3.1 (Unbrick, Downgrade, VM Radio Fix/Reset)
I'm thinking it might be a way to sidestep the boot loop problem that I have now, just relock the bootloader and follow the instructions until I get HBoot 1.40.something like the guy in the video?
Do I need some special drivers when using the RUU executables on Windows?
So I've got it to work. The problem was what jcfunk said (both of the things he mentioned, actually), I was trying to flash a GB rom when I should have tried an ICS rom instead (lol). After going to ICS RUU, I did the wire trick (unlimited.io) and now everything works nicely and I can get the latest roms.
Glad to hear.