Related
Hello everybody
The new ICS update for the ROGERS EVO 3D just came out yesterday, so I restored my phone to the original firmware (via restoring the backup I did in the recovery) and then proceeded to download the OTA update. After it finished, the phone rebooted into the recovery (i have 4-ext touch recovery) and started installing. After it finished, the phone rebooted and then got stuck on the white HTC screen. I managed to enter the recovery again and restore the original firmware again. What is that I'm doing wrong here? Here is some helpful info:
Rogers EVO 3D, GSM version
Unlocked bootloader (HTCDEV method), S-ON
carrier unlocked
HBOOT 1.49.0008
OS is rooted
I'm in the same boat but I'm not able to do a recovery. I went through the update process and when the phone rebooted it got stuck on the white htc screen. I can get it into the bootloader menu but when i choose recovery it starts but then i get an error with a pic of the device and the red yield sign. If i choose factory reset it just gets stuck at the white htc. I read some other posts and I saw that having an unlocked bootloader may cause issues with updates so that may be your issue as for me, I'm not sure what I can do. I may just need the actual update file to redo the update but I'm not sure where to find it.
Same here, but I don't get half way through the ota update before I see the red triangle and exclamation mark. Phone will boot into stock recovery (which I would assume you need instead of modded recovery) and the update starts, but doesn't complete. I pull the battery and the phone boots up normally. Just can't seem to get through the update. Could be something to do with being s-off I would guess.
EJ
madmajd said:
Hello everybody
The new ICS update for the ROGERS EVO 3D just came out yesterday, so I restored my phone to the original firmware (via restoring the backup I did in the recovery) and then proceeded to download the OTA update. After it finished, the phone rebooted into the recovery (i have 4-ext touch recovery) and started installing. After it finished, the phone rebooted and then got stuck on the white HTC screen. I managed to enter the recovery again and restore the original firmware again. What is that I'm doing wrong here? Here is some helpful info:
Rogers EVO 3D, GSM version
Unlocked bootloader (HTCDEV method), S-ON
carrier unlocked
HBOOT 1.49.0008
OS is rooted
Click to expand...
Click to collapse
Same problem but whit s-off
I have been predicting that this would happen... ICS failures with non-standard HBOOTs. Good luck.
Probably will have to wait for an RUU or custom.
I'd recommend using the GB ruu to get you back to full stock. Always found Rogers ota updates (possibly all carriers?) won't install if you're rooted or using a custom recovery.
I had to install the ruu via renaming the rom.zip to PG86IMG.zip and copying it to the sd card so that the bootloader would auto flash it. Running the ruu exe tossed up all kinds of errors.
It will put everything back to Rogers stock. After that just setup wifi and do the 2 Rogers OTA updates.
Once in ICS, it's easy peasy to get recovery and root back.
Also, for what it's worth, Go Backup is awesome for going rom to rom and not needing a full backup. Use it on rooted rom, then use it to restore after rooting new rom. Will do all your apk's and everything.
1st post here after years of lurking. Yay.
wikkid said:
I'd recommend using the GB ruu to get you back to full stock. Always found Rogers ota updates (possibly all carriers?) won't install if you're rooted or using a custom recovery.
I had to install the ruu via renaming the rom.zip to PG86IMG.zip and copying it to the sd card so that the bootloader would auto flash it. Running the ruu exe tossed up all kinds of errors.
It will put everything back to Rogers stock. After that just setup wifi and do the 2 Rogers OTA updates.
Once in ICS, it's easy peasy to get recovery and root back.
Also, for what it's worth, Go Backup is awesome for going rom to rom and not needing a full backup. Use it on rooted rom, then use it to restore after rooting new rom. Will do all your apk's and everything.
1st post here after years of lurking. Yay.
Click to expand...
Click to collapse
Alright thanks a lot
Just an update on what I did. I was able to reload the stock gb rom for rogers using the exe file, then I went through the 2 updates that came up when checking and ics is now up and running on my phone. However in my attempts of trying to fix the original problem, I managed to re-lock my bootloader before flashing to stock rom and I had s-on the whole time. hope this help.
i switched to stock like.. a week back?
jus got ota on 4th
i WAS rooted and using juopunutbear's hboot *u can jus get the hboot from their website*
so i jus flashed back stock recovery.. and updated.. and success.. lost root though.. and i was back to stock bootloader..
used the PG86IMG with juopunutbear's bootloader and 4ext recovery.. and flashed cwm supersu.. v0.91 i think.. i dunno.. latest one.. and bam.. im on stock.. rooted.. and works perfectly..
Possible sollution
Maybe try flashing one of the customized ROMs that are based on the latest OTA update. I'm sure Anryl's newest rom is blazing-fast and stable. You can find it in the gsm android development forum and flash it via recovery. Make sure you have the latest 4ext recovery installed, though.
where can a i find that stock rogers rom i modified mine and that might be the reason i get a security failure in hboot. s is on. when i run the ruu file in windows to downgrade i get error 155. when i run the the update from about phone. it locks up with blue android guy and yellow exclamation mark. i remove the battery and she boots fine with no changes.
I am trying to do same. Get stuck on HTC screen. I have S-ON. Was on cobra 2.4 prior.
If anyone can give details on how to fix it, it would be great! Please no saying "install exe". I need to know which exe etc.
just wanted to tell everyone that in order for the ota update to work properly, you need to be running stock unrooted firmware with a locked bootloader. Just relock your bootloader, reinstall the stock firmware, upgrade to ics via ota, then re-unlock and re-root.
Hi
I have a HTC EVO 3D from Rogers that was got messed up during changing networks... rooted the phone for no apparent reason... to now get a update for it for ics from the provider and it bricked the phone.
It's stuck at HTC boot screen, can get fastboot USB from bootloader. recovery gets a ! in a triangle and factory reset doesn't work, freezes at splash screen after restarting the phone. Was stupid not making a backup or searching for programs to back it up before I went ahead and clicked update
It has HTC boot-loader 1.49 s-on but is rooted.
I am looking for clear(fix my evo for dummies) step by step instructions with correct installation for my model of phone, HTC EVO 3D Rogers GSM, or anything that could replace the os to get my phone to be useful again I'm currently using my backup phone a HTC G1 HTC ftw
Try kingcobra's rom, ota from rogers will not boot due to the fact that your phone is rooted, kingcobra's rom is based on rogers ota, flash it and leave it.
Sent from my HTC EVO 3D X515m using xda premium
Davideichler7 said:
Hi
I have a HTC EVO 3D from Rogers that was got messed up during changing networks... rooted the phone for no apparent reason... to now get a update for it for ics from the provider and it bricked the phone.
It's stuck at HTC boot screen, can get fastboot USB from bootloader. recovery gets a ! in a triangle and factory reset doesn't work, freezes at splash screen after restarting the phone. Was stupid not making a backup or searching for programs to back it up before I went ahead and clicked update
It has HTC boot-loader 1.49 s-on but is rooted.
I am looking for clear(fix my evo for dummies) step by step instructions with correct installation for my model of phone, HTC EVO 3D Rogers GSM, or anything that could replace the os to get my phone to be useful again I'm currently using my backup phone a HTC G1 HTC ftw
Click to expand...
Click to collapse
Go to the gsm development forum and download the RUU for the phone, and restore it to stock unrooted OS. Before you do that though, make sure that your phone's BOOTLOADER IS LOCKED. Look up how to re-lock your bootloader. After you relock your bootloader, you can proceed with restoring the phone.
Soooo.... basically, what I'm getting from this is, if you like having a locked bootloader, CWM and root, don't bother trying to install this OTA update because it's a headache. Agree?
The phone's not mine, it's my wife's, and she doesn't want anything special or like the idea of me messing around in her phone.
I was about to install this late last night, just about to hit that button, then I thought, "what about the bootloader? what about root? what about the fact that it's now unlocked and being used on a carrier other than Rogers?"
im used to flashing ROMs on my galaxy SII. so my girl wanted me to upgrade her EVO to android 4.0. i forgot that i needed to use adb and fastboot to install ROMs on her device. I booted into TWRP via the power menu and proceeded to flash a ROM. i am now stuck in a bootloop. i can get into the bootloader menu, but nothing i do seems to fix the problem. ive been searching for a while and found some info im still reading about on how to get S-off and whatnot. anyone got any advice for me?
since you were able to get into TWRP, Imma assume that you went to HTCDev,
since you can get to the bootloader, i assume you can also set it to fastboot?
my suggestion would be to downgrade your h-boot (procedures are different for GSM and CDMA if I'm not mistaken) and get S-off, as some roms can have problems with higher hboot versions regardless of S-off.
From there you have pretty much free reign to do whatever you like to the phone.
My guess would be that since the phone is not S-off it's not playing nice with the ROM/Kernel you installed.
Links to Downgrading threads:
GSM:
http://forum.xda-developers.com/showthread.php?t=1471246
CDMA:
http://forum.xda-developers.com/showthread.php?t=1563342
Got it sorted. From fastboot I was able to relock the bootloader with advt. Then run the latest RUU and go back to stock. Now to unlock the bootloader again.
Question, if I downgrade the hboot and get s-off, can I just flash from recovery instead of booting recovery through fastboot and adb then flashing?
Sent from my SPH-D710 using xda app-developers app
yep, when you downgrade hboot and get S-off, you can flash all manner of roms and kernels without hooking the phone up to a pc at all
Hi guys, I've searched the forums for days now and tried many recovery methods, all which end in failure.
Basically my Evo which is on cyanogenmod is stuck on the wrong kernel, and I now have zero reception.
I even tried going into sprint, but their tech told me the first step towards recovery is going to be installing the right kernel.before I can do anything or get service again. He even let me take a picture of the Kernel info on an EVO LTE in the store.
The method of HOW to install the right kernel is where I am completely at a loss and would appreciate help.
I believe I'm looking for Odin
Stock Kernel
Stock Rom
and the steps it takes to do it
I am rooted.
I have TWRP v.2.2.2.0
Here is what my Hboot looks like.
***TAMPERED ***
***UNLOCKED***
JEWEL PVT SHIP S-0N RL
HBOOT 1.12.0000
RADIO. 1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMMC-boot apr 26 2012, 19:54:01
I have tried multiple RUU's which end in Failure and errors.
I've tried placing a stock recovery image and flashing it through Hboot.
UPDATE: someone told me I need to re-lock before I can flash a RUU.
so I re locked. and then ran an RUU and it finally completed successfully...
and now my phone has nothing but H boot.
no more TWRP
no more Rom
still have adb and electricity so if there is any way of saving my phone I'd appreciate any pointers.
UPDATE 2: after being stuck in fastboot only for the last 7 hours and trying all the recommended RUU's, I decided I'd try anything, so I re-did htc dev unlock.
I was then taken to my boot animation of cyanogen mod and nothing else.
I just rebooted into recovery and ::huzzah:: TWRP is still intact with 2 old backups of cyanogen mod.
I am going to be very careful of where I step next because all I've managed to do is dig myself deeper.
this is the one step forward in an otherwise downhill **** eating of grand magnitude.
I just read a google voicemail transcript for a video gig that I just lost because I never got the call.
I am thinking of installing the most stock rom I can, taking it into sprint, and claiming ignorance in hopes that they will just swap it out.
I'm now going to check if flashing the RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.15.651.16
got my reception back...
Here's to hoping!
Which ruu did you run? If an old ruu and you still have hboot 1.12, any time you flash a ROM the correct kernel will also be flashed in the process.
I've never used ruu before, but it seems weird to me that after RUU, there is no ROM on your phone.
Do you have an SD card and card reader and PC?
Also, your twrp version is very outdated.
Using fastboot, you should be able to fastboot flash recovery to update TWRP. If you're unsure how, om4 has a great guide in either the general or general sticky section.
Sent from my EVO using xda premium
t3chn0v1k1ng said:
Hi guys, I've searched the forums for days now and tried many recovery methods, all which end in failure.
Basically my Evo which is on cyanogenmod is stuck on the wrong kernel, and I now have zero reception.
I even tried going into sprint, but their tech told me the first step towards recovery is going to be installing the right kernel.before I can do anything or get service again. He even let me take a picture of the Kernel info on an EVO LTE in the store.
The method of HOW to install the right kernel is where I am completely at a loss and would appreciate help.
I believe I'm looking for Odin
Stock Kernel
Stock Rom
and the steps it takes to do it
I am rooted.
I have TWRP v.2.2.2.0
Here is what my Hboot looks like.
***TAMPERED ***
***UNLOCKED***
JEWEL PVT SHIP S-0N RL
HBOOT 1.12.0000
RADIO. 1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMMC-boot apr 26 2012, 19:54:01
I have tried multiple RUU's which end in Failure and errors.
I've tried placing a stock recovery image and flashing it through Hboot.
UPDATE: someone told me I need to re-lock before I can flash a RUU.
so I re locked. and then ran an RUU and it finally completed successfully...
and now my phone has nothing but H boot.
no more TWRP
no more Rom
still have adb and electricity so if there is any way of saving my phone I'd appreciate any pointers.
Click to expand...
Click to collapse
Odin is the upgrade utility for Samsung, our equivalent is basically the HTC RUU packages. I would suggest re-running the ruu or running either 1.15 or 1.19 to restore the phone. If you want to continue using custom roms you should go to unlimited.io and follow the directions for soff
scottspa74 said:
Which ruu did you run? If an old ruu and you still have hboot 1.12, any time you flash a ROM the correct kernel will also be flashed in the process.
I've never used ruu before, but it seems weird to me that after RUU, there is no ROM on your phone.
Do you have an SD card and card reader and PC?
Also, your twrp version is very outdated.
Using fastboot, you should be able to fastboot flash recovery to update TWRP. If you're unsure how, om4 has a great guide in either the general or general sticky section.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
the RUU I flashed was "RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed.exe"
Also I just noticed I am upgraded to Hboot 2.09.0000
t3chn0v1k1ng said:
the RUU I flashed was "RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed.exe"
Also I just noticed I am upgraded to Hboot 2.09.0000
Click to expand...
Click to collapse
:what: Well... you can disregard that post about gaining s-off, that is a thing of the past now that you fully updated to the new baseband and hboot. If I might as (you don't have to answer as it doesn't really matter now) Why were you still s-on with hboot 1.12 in the first place??
mrrogers1 said:
:what: Well... you can disregard that post about gaining s-off, that is a thing of the past now that you fully updated to the new baseband and hboot. If I might as (you don't have to answer as it doesn't really matter now) Why were you still s-on with hboot 1.12 in the first place??
Click to expand...
Click to collapse
Honestly I have no idea.
I rooted my phone like the 2nd day I had it.
I also had on OG evo that I had rooted the entire time I owned it.
I never learned about s-off. I just wanted CM10, tethering, and adfree.
This is the reason for all of this to begin with:
on CM10, I had working 3G, but also 4G here and there.
my connection would drop out all the time to zero, or 1x.
Still had bars though, just no mobile data.
oh yea I have an air rave, does that make this story more fun?
anyway.
After getting a different answer, literally every time I went into sprint and asked about 4G.
It's on! it's coming next month! we have a repeater just in this area! it's coming on next month!
I decided it was my phones fault and that I need it back to factory.
I even have backups named "dec 2012 LTE works" and "DONT **** THIS UP"
And now I am here. twrp and fastboot are the only things I can access now.
I'm thinking of taking it into sprint with a stock image flashed
and letting it bootloop no matter what they try.
It'll still say "relocked" "tampered though"
I guess unrooting is my best next option?
I'm so clueless it's probably pretty funny to some of you.
the latest RUU I flashed is RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed (1).exe
does this mean my kernel and radio are updated now?
Yes should be. But now you may have more problems now with the new hboot then you had to begin with. Hboot 2.09 has more security features.
Hello all,
I am brand new to the android community, and have come accross a problem that I can't seem to get fixed. I previously rooted/rom'd my EVO lte with mean rom a while back. I started to have wireless issues so I decided to spend some time learning/fixing the problems that I'm sure my noobness created.
I relocked my phone and unrooted it back to factory 2.13.651.1. After doing that I updated my phone via Sprints OTA updater. I recieved an update that took me to 3.16.561.3. After that was completed I preceeded to unlock my bootloader again and installed TWRP 2.4.1.0. When I try to install any ROM it appears to go well in TWRP, but it reboots right after it says "updating kernel, this may take a while". When it reboots it sits at the HTC white startup screen, it doesnt even flash the red developer letters under the HTC logo like it normally does when continuing to boot into recovery or the old ROM.
I did some search and have found that others had issues with TWRP 2.4.1.0 (http://forum.xda-developers.com/showthread.php?t=2048229&page=573). They rolled back to 2.4.0.0. The problem is that with the OTA update the touch sence in TWRP is broken unless you run 2.4.1.0.
Anyone else run across ths issue?
The solution is probably staring me in the face but my noob aura is blocking it. :silly:
TWRP 2.4.1.0 broke something with flashing so you might have to relock and ruu to get back to normal. The problem is there is no ruu out for 3.16 and running the ruu for 3.15 may mess up your phone. I would try to flash the kernel separately by flashing with fastboot or flashgui and see if that allows it to boot into the rom. You may be able to run dirty racun and gain s-off since the hboot didn't change with the latest update.
Waterheeter said:
Hello all,
I am brand new to the android community, and have come accross a problem that I can't seem to get fixed. I previously rooted/rom'd my EVO lte with mean rom a while back. I started to have wireless issues so I decided to spend some time learning/fixing the problems that I'm sure my noobness created.
I relocked my phone and unrooted it back to factory 2.13.651.1. After doing that I updated my phone via Sprints OTA updater. I recieved an update that took me to 3.16.561.3. After that was completed I preceeded to unlock my bootloader again and installed TWRP 2.4.1.0. When I try to install any ROM it appears to go well in TWRP, but it reboots right after it says "updating kernel, this may take a while". When it reboots it sits at the HTC white startup screen, it doesnt even flash the red developer letters under the HTC logo like it normally does when continuing to boot into recovery or the old ROM.
I did some search and have found that others had issues with TWRP 2.4.1.0 (http://forum.xda-developers.com/showthread.php?t=2048229&page=573). They rolled back to 2.4.0.0. The problem is that with the OTA update the touch sence in TWRP is broken unless you run 2.4.1.0.
Anyone else run across ths issue?
The solution is probably staring me in the face but my noob aura is blocking it. :silly:
Click to expand...
Click to collapse
So u was on 3.16 and unlocked it? Did u use dirty racun? Did it work? Sorry I accepted ota and want s-off rooted if possible.
Sent from my EVO using xda app-developers app
polar2792 said:
So u was on 3.16 and unlocked it? Did u use dirty racun? Did it work? Sorry I accepted ota and want s-off rooted if possible.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I didnt use dirty racun to unlock, I used the fastboot method. I'm not developed enough in my knowledge to be s-off atm.
cruise350 said:
TWRP 2.4.1.0 broke something with flashing so you might have to relock and ruu to get back to normal. The problem is there is no ruu out for 3.16 and running the ruu for 3.15 may mess up your phone. I would try to flash the kernel separately by flashing with fastboot or flashgui and see if that allows it to boot into the rom. You may be able to run dirty racun and gain s-off since the hboot didn't change with the latest update.
Click to expand...
Click to collapse
On your notes I did some searching to learn what you were saying. First I tried to use the fastboot update 'meanbean-rom.zip' file but it produced errors:
archive does not contain 'android-info.txt
archive does not contain 'android-product.txt
error: update package has no android-info.txt or android-product.txt
I tried fastboot flash boot boot.img after extracting the boot.img from the .zip. After rebooting the phone stays on the white HTC logo screen but now populates the red dev notice. Looks like I'm going in the right direction
Thanks for your help so far.
I believe I have it figured out. I searched for an unofficial version of CWM recovery (all the XDA links for the evo lte have been removed for now due to bugs). I'll deal with those bugs as I was stuck without a phone until I got it figured out
Installed CWM 5.8.3.5 and flashed Meanbean Rom. Problem fixed
I'll put TWRP back on when they release a patch.
*Edit* spoke too soon. The touch interface doesnt work with meanbean due to the driver update (I'm guessing). Atlease I can see any missed calls now. lol
*Edit* Thanks to the D3rps I was able to get my phone up and going again. They had posted the stock 3.16 rom here: http://forum.xda-developers.com/showthread.php?t=2127947, with *Removed* recovery I was able to flash that rom. Now I just have to keep an eye out for the Meanbean update that will make it work with 3.16 touch.
**Edit** I removed the reference to the recovery I was using due to problems my noob self was not aware of. Thanks to Bigdaddy619 for his guidance, I now realize why no one is using it on the evo lte.
Hey guys, I seem to have ran into a few problems while trying to flash a custom rom on my evo 4g lte. Being that I was unable to flash two different roms i decided to go back to stock via the ruu.exe.To root, I unlocked bootloader with htcdev.com and proceeded to root with twrp. While trying to undo I then relocked the boot loader but when the ruu gets to around 93% it fails and gives me an error code. I currently dont have a rom to flash to nor have a recovery to flash anything. When at the bootloader screen i have ''Tampered'', ''Relocked'', and ''Security Warning''. Also I have S-On.
Any help or information is greatly appreciated. I need my phone back lol. I used to flash all the time with my old evo and never got stuck like this before.
Some more information might be useful. List your Hboot version and radio (baseband) version. Really, you should be able to unlock your bootloader again and push a recovery to your phone, at which time you should be able to flash a ROM.
If that doesn't work, hit the top link in my sig and go to the last post in the thread. Hit the link and follow the instructions on how to manually install from the bootloader.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Hit the top link in my sig, and go to the last post in the thread. Hit the link for the 3.17 RUU and follow the instructions on how to manually install it from the bootloader. What happens when you try to enter recovery from the bootloader?
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
I am downloading now. I wasnt able to find this version but it is newer than the one I had. When i go to recovery it just goes right back to the bootloader. The error code I was receiving was 140. Btw, I really do appreciate you helping me out!!
FinZ28 said:
Some more information might be useful. List your Hboot version and radio (baseband) version. Really, you should be able to unlock your bootloader again and push a recovery to your phone, at which time you should be able to flash a ROM.
If that doesn't work, hit the top link in my sig and go to the last post in the thread. Hit the link and follow the instructions on how to manually install from the bootloader.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
hboot version=2.09
Radio=1.13.11.0830
Im going to try to unlock the bootloader again and flash a stock rom. Is there only certain types of roms i can use with twrp?
kaintcme187 said:
hboot version=2.09
Radio=1.13.11.0830
Im going to try to unlock the bootloader again and flash a stock rom. Is there only certain types of roms i can use with twrp?
Click to expand...
Click to collapse
You can flash any ROM with TWRP so long as it's for the EVO LTE. Having said that, since you're S-on you'll have to install the ROM kernel separately from the ROM itself. Read the guide in the top link in my sig for more info. There are a few ROM's that are easy to flash while S-on (MeanBean being one of them).
Sent from my HTC EVO 4G LTE
I never had to flash the kernel separately. Just did the normal wipe then flash and after it booted up it would go into a bootloop and I would reboot into bootloader then flash the rom again with it wiping
Took the red pill. HTC evo 4G LTE evilution red pill.
gstanke said:
I never had to flash the kernel separately. Just did the normal wipe then flash and after it booted up it would go into a bootloop and I would reboot into bootloader then flash the rom again with it wiping
Took the red pill. HTC evo 4G LTE evilution red pill.
Click to expand...
Click to collapse
That only works with Sense roms that are equipped with the S-On Kernel installer. If you are coming from the OG Evo, you should know that flashing on this device is not the same at all. You certainly need to read before you act, otherwise you might brick your device. I've been stuck in recovery before from the same problem.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel