I just got my EVO LTE today. It has hboot 1.12, and is dev unlocked. I've tried flashing the newest nightly of CM10 with both CWM (5.8.3.5) and TWRP (2.2.2.0), and everything seems to go well until I boot into CM10, and it just sits at the CM loading animation forever. Yes, I've done the normal wiping of caches. Any ideas out there? Thanks in advance!
bilbo524 said:
Yes, I've done the normal wiping of caches.
Click to expand...
Click to collapse
Wiping caches isnt the proper wipe.
Thats your issue,.
Do a factory reset, wipe system, data, cache, and dalvik cache
Rxpert said:
Wiping caches isnt the proper wipe.
Thats your issue,.
Do a factory reset, wipe system, data, cache, and dalvik cache
Click to expand...
Click to collapse
Ah. I'll try this right now.
I only ever did cache partition and dalvik when flashing CM7 on my EVO Shift and it worked fine first try, just assumed that's all I needed here.
Thanks already given
bilbo524 said:
Ah. I'll try this right now.
I only ever did cache partition and dalvik when flashing CM7 on my EVO Shift and it worked fine first try, just assumed that's all I needed here.
Thanks already given
Click to expand...
Click to collapse
No problem, I'll stick around for more options if that doesnt fix it.
Also, in an unrelated note, I would highly suggest looking into getting S-OFF
Worked like a charm! :highfive:
I was reading up on lazy panda, but I guess I don't see the benefits of s-off if all I'm doing is CM10 official builds. Care to enlighten me?
bilbo524 said:
Worked like a charm! :highfive:
I was reading up on lazy panda, but I guess I don't see the benefits of s-off if all I'm doing is CM10 official builds. Care to enlighten me?
Click to expand...
Click to collapse
S-OFF = bootloader securities off. You can flash things through the bootloader that are not signed by HTC.
With H-boot 1.12 you can still flash all the usual things that you would normally flash in the bootloader through the recovery, but S-OFF provides an extra bit of safety net in the fact that its future proof. Once you are S-OFF you are S-OFF until you flash the S-ON tool.
With HTC unlock, if somehow the phone gets updated (friends, family, ect not knowing to decline OTA's when using your phone) you lose all ability to flash new radios and other firmware bits. You would also have to fastboot flash kernels each time you flash a ROM. Its a pretty big pain.
Now, being on CM means you wont get HTC updates, so you shouldnt have to worry about it, but S-OFF is still regarded as being better for that added ability to flash through bootloader if things go wrong.
Its suggested that you have access to linux on your computer if you decide to S-OFF, because theres a chance you could temp brick the phone, and the unbrick tool only works in linux.
We have a great guide for this over on AF. Don't be discouraged by the size of it. Lazypanda only takes a few minutes if it doesnt brick.
http://androidforums.com/evo-4g-lte-all-things-root/605567-s-off-lazypanda-root-dummies-guide.html
I'll have to look into that. As an IT Engineer with a Linux background, it should be cake
Thanks again for all of your help!
Rxpert said:
but S-OFF provides an extra bit of safety net in the fact that its future proof. Once you are S-OFF you are S-OFF until you flash the S-ON tool.
Click to expand...
Click to collapse
Does this mean you can upgrade your hboot to 1.15 or 1.19 while still keeping S-OFF? I've been reluctant to touch my hboot out of fear of losing the S-OFF.
edit: whoops, found my answer in another thread. I guess it won't lose the S-OFF but I'm still going to leave it alone.
Sent from my EVO using xda app-developers app
Yes, but theres literally no need to update your h-boot
I had the same issue - didn't do factory wipe, just cache etc.. I cannot even boot into recovery - in a boot loop at that point too. Any suggestions on how to boot into recovery at that point?
if your boot looping. do a hard shut down of your phone. hold the power button down for like 20 seconds. your phone's capacitative buttons should flash. once its off. hold down the Volume down button and push power on the phone. it'll vibrate and should load into the bootloader menu. from there just select recovery and you should get in.
Is the "hard shutdown" an equivalent to a battery pull? ie. a function of the hardware, not software?
Sent from my EVO using xda premium
Yes, holding power for 10+ seconds is the same as a battery pull
I highly advise using lazy panda from a booted Linux pc. I used ubuntu 12.0.4. No bricking problems. As an IT guy you should have no problems with setting up a bootable drive or cd
Took your advice and did the following:
1. Obtained S-OFF via lazy panda.
2. Full backup via TWRP.
3. Flashed stock ROM and followed Regaw's S-ON guide to put phone back to stock (S-ON, no dev unlock, etc). (http://forum.xda-developers.com/showthread.php?t=1744700)
4. Re-rooted, used lazy panda again.
5. Booted into stock ROM and downloaded newest PRL.
6. Flashed newest Radio, PRI with ZIP from http://forum.xda-developers.com/showthread.php?t=1704612
7. Restored TWRP backup and am now running CM10 Nightly with newest Radio, PRI, and PRL, with S-OFF and no stupid dev-unlock.
Thanks for all of the help, guys! Everything went perfect.
Related
Hey guys and girls and maybe other mutant human-like things i may not know about on xda,
I have a HUUUGE problem. Whenever I flash a ROM that is Sense 3.6 or some versions of Sense 4.0, my phone WILL (somewhat) successfully boot the rom to the home screen only displaying a background and notification bar. No icons or dock. Just a background and the notification bar for 2 seconds, then freezes, then it reboots. It then reboots with the same fate. Blank home screen, freeze, reboot. Here's the ROM I want to flash:
http://forum.xda-developers.com/showthread.php?t=1634807
Information about my phone:
HTC EVO 3D CDMA
HBOOT 1.50
What recovery are you using? I've been using 4ext and when I wipe I use the format options. No superwipe. I have yet to see a Rom not boot. I'm 1.50 S- on as well.
Sent from my PG86100 using XDA
UPDATE
I HAVE tried pulling the battery, same thing. But when I pulled the battery and rebooted one time I got to the lock screen.
I am using 4-ext recovery.
I AM S-ON
When I format I just tap Factory Reset. Also I tried to flash the ROM while using another custom ROM, but I Factory Reset first.
Format system as well along with the caches.
Sent from my PG86100 using XDA
Okay thx for quick replies but should I:
1. Wipe Dalvik cache and cache with rom installed already?
OR
2. Wipe System, Data, Boot, caches, and re-flash?
Go with option 2.
Sent from my PG86100 using XDA
I will do so and reply with information.
I just went into the recovery to see what I normally do. I select the option to format all partitions (except SD) and that takes care of it.
Did a superwipe to be sure and I am now flashing the rom so it will be like 15 to 20 minutes.
DAAAAAAAAAANNNNGGGIITTTTTTT!!!!!
Didn't work. Same result. Only this time I'm even more peeved off.
Try the option to format all except SD near the bottom of the wipe list. Don't run the superwipe. I stopped using it because I had issues with boot loops a while back so I do all formatting manually. Anyway, just use that option and try it. Also, what rom are you trying to flash. I can try it here as well.
cburk01 said:
Hey guys and girls and maybe other mutant human-like things i may not know about on xda,
I have a HUUUGE problem. Whenever I flash a ROM that is Sense 3.6 or some versions of Sense 4.0, my phone WILL (somewhat) successfully boot the rom to the home screen only displaying a background and notification bar. No icons or dock. Just a background and the notification bar for 2 seconds, then freezes, then it reboots. It then reboots with the same fate. Blank home screen, freeze, reboot. Here's the ROM I want to flash:
http://forum.xda-developers.com/showthread.php?t=1634807
Information about my phone:
HTC EVO 3D CDMA
HBOOT 1.50
Click to expand...
Click to collapse
This is a very easy to fix problem. You just need the firmware - Any true 3.0 linux kernel (which is included in Android 4.0) cannot boot or run well without the adsp.img.
Download this: https://www.dropbox.com/s/lpx3nn7kjj2s3kq/PG86IMG.zip
Remove everything from it but adsp.img. Place it on the root of your sd card and go into bootloader. Confirm the flash.
Now you'll be on the new firmware without any of the nasty side effects that everyone is having with VM firmware.
Quick question, will this remove all data from phone and remove my unlock from the boot loader?
That's normal, u need the anthrax firmware test kernel or s-off. I had the same problem. I achieved s-off using the wire method on unlimited.io and can load any ics Rom and kernel and still have h-boot 1.5
Sent from my PG86100 using xda premium
...what?
cburk01 said:
Quick question, will this remove all data from phone and remove my unlock from the boot loader?
Click to expand...
Click to collapse
Ignore the other replies. The way I suggested is probably the best way to go about it. (Couldn't really think of a way to say this without coming off as a jerk)
You can't flash this without being S-Off. You shouldn't be S-On though since we have S-Off for HBOOT 1.5.
(S-Off gives your phone more freedom, like being able to flash kernels in recovery and flash unnofficial firmwares like this one)
To get Hboot 1.50 S-off: http://forum.xda-developers.com/showthread.php?t=1585846
After you are S-Off, flash the firmware with everything but adsp.img like I said before. No data will be lost from your phone, but keep in mind that you should've wiped data before flashing a Sense 3.6/4.0 ROM anyway.
After flashing firmware, go into recovery and flash your desired Sense 3.6/4.0 ROM. When you boot up and the dust clears, you should hopefully be running it without issues.
P.S. Send me a PM if you have more issues or questions. I rarely follow threads I post in.
That's what I said! Lol just not in depth
Sent from my PG86100 using xda premium
yousefak said:
Ignore the other replies. The way I suggested is probably the best way to go about it. (Couldn't really think of a way to say this without coming off as a jerk)
You can't flash this without being S-Off. You shouldn't be S-On though since we have S-Off for HBOOT 1.5.
(S-Off gives your phone more freedom, like being able to flash kernels in recovery and flash unnofficial firmwares like this one)
To get Hboot 1.50 S-off: http://forum.xda-developers.com/showthread.php?t=1585846
After you are S-Off, flash the firmware with everything but adsp.img like I said before. No data will be lost from your phone, but keep in mind that you should've wiped data before flashing a Sense 3.6/4.0 ROM anyway.
After flashing firmware, go into recovery and flash your desired Sense 3.6/4.0 ROM. When you boot up and the dust clears, you should hopefully be running it without ssues.
P.S. Send me a PM if you have more issues or questions. I rarely follow threads I post in.
Click to expand...
Click to collapse
The only exception is flashing Chad Goodman's anthrax kernel for ICS, but then you lose 3D and USB. Just bite the bullet and either downgrade to 1.4 so you can s-off or follow the new method for 1.5. Trust me, I kept doing all these workarounds for the longest time to get around my 1.5 s-on, and life got so much easier once I downgraded.
I recently got S-off and decided to update my Hboot and Radio since I was on GB firmware and wanted to be on ICS firmware. I was on Neo's Rage 1.5 Rom when I flashed the new hboot in fastboot and still had a Locked bootloader at this point.
My steps:
* I updated the Hboot to 2.27.0000 and the Radio to 2.22.10.0801r/2.22.10.0803rm from this page I used the 8-12 ICS zip
*After this I formatted the SD card
*then flashed this RUU stock ICS rom.
*I then unlocked the bootloader and then reflashed AmonRa 3.15.
Also, when I would boot into my previous bootloader there was no haptic feedback while holding down vol down + power. Now after the new hboot there is a short haptic vibration before it boots while holding down vol down + power. This normal?
I have tried a couple Sense roms and AOSP rom and each one now has random reboots. Not too often, but usually when I am in the middle of doing something important. Any ideas? Should I switch to a previous Hboot or Radio? It's not that bad of a problem, just wondering if anyone has encountered this. Thanks!
When you did the the RUU flash, did you also do a factory reset after? This COULD cause an issue if not, although I doubt. Extract the stock recovery out of your RUU, fastboot flash it, factory reset then reflash amonra along with rom after a good clean wipe.
Snuzzo said:
When you did the the RUU flash, did you also do a factory reset after? This COULD cause an issue if not, although I doubt. Extract the stock recovery out of your RUU, fastboot flash it, factory reset then reflash amonra along with rom after a good clean wipe.
Click to expand...
Click to collapse
I did do a factory reset after the RUU. I will try the method you mentioned. Is that the boot.img from the RUU? Thanks man!
If all else fails, try flashing to the full .12 RUU...at least get everything back to full stock to eliminate any variables.
http://androidrevolutions.com/neo/files/RUU_Vigor_VERIZON_WWE_3.14.605.12_PH98IMG.zip
shrike1978 said:
If all else fails, try flashing to the full .12 RUU...at least get everything back to full stock to eliminate any variables.
http://androidrevolutions.com/neo/files/RUU_Vigor_VERIZON_WWE_3.14.605.12_PH98IMG.zip
Click to expand...
Click to collapse
To flash the full .12 RUU would I need to relock the bootloader prior to flashing? Thanks for your response!
boyj600 said:
To flash the full .12 RUU would I need to relock the bootloader prior to flashing? Thanks for your response!
Click to expand...
Click to collapse
Just a quick mention; why did you unlock the bootloader when you could have just flashed an unlocked hboot like vinylfreaks? Patched the same way JB hboots are.
Snuzzo said:
Just a quick mention; why did you unlock the bootloader when you could have just flashed an unlocked hboot like vinylfreaks? Patched the same way JB hboots are.
Click to expand...
Click to collapse
I was unaware of vinylfreaks unlocked hboot. ~Hand in face~ I will have to search for that
boyj600 said:
I was unaware of vinylfreaks unlocked hboot. ~Hand in face~ I will have to search for that
Click to expand...
Click to collapse
Don't worry about ti. we all forgot things sometimes. Like earlier today, I forgot to add in the GPU oc option into funky kernel. So you guys get 2 sets of updates instead of just one.
Anyways pertaining to the issue at hand. Yeah a factory reset before you reflash the rom helps. You could potentially be having residual connectivity issues left over from the flash to the new radios. Which causes a kernel panic, then BOOM reboot.
shrike1978 said:
If all else fails, try flashing to the full .12 RUU...at least get everything back to full stock to eliminate any variables.
http://androidrevolutions.com/neo/files/RUU_Vigor_VERIZON_WWE_3.14.605.12_PH98IMG.zip
Click to expand...
Click to collapse
I flashed this RUU and have had no reboots for an hour or so. Looks like that may have done the trick. Thank you guys for the quick responses!
Sent from my Rezound using xda premium
Hello, I have been trying to flash different 4.1.X roms and i have been ending up with a bootloop every time. I use 4EXT
recovery and wipe data, wiped all but sd, wipe cashe,then install and i end up with bootloops every time.
I rooted my phone after taking the 2.89 OTA. htcdev unlock method, wire trick to s off. Thanks in advance for anything that my help ou with getting this to work.
i have tryed to flash
ParanoidAndroid 2.54
MiuiAndroid 2.11.16
CyanogenMod 10 - GANGNAM STYLE
[Team D.I.R.T][JB 4.1.2] KING KANG
ParanoidKangdroid
im not sure if this makes a difference but i am currently using SOS M 2.6.1 w/butter toast kernel(wipeing data and what not before install.)
EVO 3D CDMA
hboot 1.4
radio 1.09.00.0706
s off
not being an ass but a bit of searching or even reading the roms thread would of answered your question.
The issue is you most likely have hboot 1.58
You need to downgrade ti 1.50 or lower.
iTzLOLtrain said:
not being an ass but a bit of searching or even reading the roms thread would of answered your question.
The issue is you most likely have hboot 1.58
You need to downgrade ti 1.50 or lower.
Click to expand...
Click to collapse
not being an ass BUT i did say
EVO 3D CDMA
hboot 1.4
radio 1.09.00.0706
s off
and i have been searching for a couple of weeks i read and read but never posted before.
i just want to try and get this working since i like how these roms look.
Mokokomis said:
not being an ass BUT i did say
EVO 3D CDMA
hboot 1.4
radio 1.09.00.0706
s off
and i have been searching for a couple of weeks i read and read but never posted before.
i just want to try and get this working since i like how these roms look.
Click to expand...
Click to collapse
nice but it seems to me you just edited. but either way ill try to help..
Have you tried flashing hboot 1.50.5050?
Also do your reboots happen right after flashing a rom or do they take awhile to start?
iTzLOLtrain said:
nice but it seems to me you just edited. but either way ill try to help..
Have you tried flashing hboot 1.50.5050?
Also do your reboots happen right after flashing a rom or do they take awhile to start?
Click to expand...
Click to collapse
I have not tried that hboot yet. and they start right away. i get to see the boot animations for less than 5 seconds. ill try to find that hboot and give a try.
Mokokomis said:
I have not tried that hboot yet. and they start right away. i get to see the boot animations for less than 5 seconds. ill try to find that hboot and give a try.
Click to expand...
Click to collapse
alright, mhmm. after flashing the rom you want you should go back into recovery & wipe cache & dalvik then reboot. that might work.
also what recovery are you using?
iTzLOLtrain said:
alright, mhmm. after flashing the rom you want you should go back into recovery & wipe cache & dalvik then reboot. that might work.
also what recovery are you using?
Click to expand...
Click to collapse
ok, so i got the 1.50.5050 hboot
wiped data/ factory reset
wiped all except sd
installed rom
wiped cache and dalvik
and same thing. bootloops let me try another of the roms and see if i get the same thing.
ok just tryed a 2nd rom and im getting the same result.
Thats strange. im wondering if flashing a different kernel might help..
But at this point i might not be much help. If nothing else works you should try returning to full stuck & root your device again.. & no you will not lose s-off if you flash a RUU
iTzLOLtrain said:
Thats strange. im wondering if flashing a different kernel might help..
But at this point i might not be much help. If nothing else works you should try returning to full stuck & your device again.. & no you will not lose s-off if you flash a RUU
Click to expand...
Click to collapse
yeah i am a wear of not losing s off. i will give that a try and see how it goes. hopefully it works. thanks for the help either way.
thanks so much for your advice. flashing the ruu then the rom worked.
Mokokomis said:
thanks so much for your advice. flashing the ruu then the rom worked.
Click to expand...
Click to collapse
Glad i could help.
Ok here's what you do to fix boot loops.
Backup sd card
Format all except sd using 4xt
Format sd card using 4xt
Toggle usb in 4xt
Delete the 4xt folder on the sd card from your pc
Copy back over your sd contents(including Rom you want to flash)
Flash Rom and reboot
This method worked for me
Unlocked
Hboot 1.5
S-off
Sent from my GT-P3113 using xda app-developers app
I have an Evo V 4G (obviously) it's S-OFF (wire trick) and running the buttered toast kernel, I was on Paranoid Android 2.99 and I kept getting fc's, so I decided to try a few new ROMs, so I tried ViperROM for Sense 4.1, that froze in the boot animation, so I went into 4ext and wiped/flashed a new ROM, but in 4ext, when I hit "info" it still says ViperROM no matter how many times I've wiped it.
I've tried going back and forth retracing my steps and trying different ROMs, aroma installer set ups, and I have no clue.
Any ideas would be very much appreciated.
iZandeR said:
I have an Evo V 4G (obviously) it's S-OFF (wire trick) and running the buttered toast kernel, I was on Paranoid Android 2.99 and I kept getting fc's, so I decided to try a few new ROMs, so I tried ViperROM for Sense 4.1, that froze in the boot animation, so I went into 4ext and wiped/flashed a new ROM, but in 4ext, when I hit "info" it still says ViperROM no matter how many times I've wiped it.
I've tried going back and forth retracing my steps and trying different ROMs, aroma installer set ups, and I have no clue.
Any ideas would be very much appreciated.
Click to expand...
Click to collapse
First suggestion would be to post in the right forum, which for this thread would be Q&A. I've reported it to the mods so they will move it for you.
If you are using 4EXT you should do a "format all partitions except sd card" in the wipe/format menu before flashing a ROM. Then make sure the the S-ON/Smartflash option is disabled in the tools menu, although that won't prevent your ROM from flashing correctly.
Try doing that and giving it plenty of time to boot after you flash it (10 minutes should be enough).
ramjet73
This needs to be in Q&A so get ready for some flames, but I'll attempt to answer.
Go into bootloader and use the wipe all utility there. Then go back to 4-ext and make sure to enable smartflash under settings. Wipe everything except your SD card, and then try to flash something like a sense 3.6 ROM that you know will be stable. Finally, let your device reboot or reboot it when the flash is complete, and let it sit for at least ten minutes. If by then, it still hasn't booted, post back.
Best of luck.
---------- Post added at 04:38 PM ---------- Previous post was at 04:37 PM ----------
ramjet73 said:
First suggestion would be to post in the right forum, which for this thread would be Q&A. I've reported it to the mods so they will move it for you.
If you are using 4EXT you should do a "format all partitions except sd card" in the wipe/format menu before flashing a ROM. Then make sure the the S-ON/Smartflash option is disabled in the tools menu, although that won't prevent your ROM from flashing correctly.
Try doing that and giving it plenty of time to boot after you flash it (10 minutes should be enough).
ramjet73
Click to expand...
Click to collapse
lol beat me to it
nickelghandi said:
lol beat me to it
Click to expand...
Click to collapse
At least we're consistent.
ramjet73
sorry about that guys, I'm not new to forums, I just use AndroidForums more often, I'll give it a try, although I've tried formatting already.
A possibility might be that ViperROM was supposed to be flashed with an RUU fastboot? I'm not really familiar with that method
My guess is Viper needs 1.58 hboot since it a sense rom.
And yeah, wrong forum.
well we've gotten past that, I get it, wrong forum, won't happen again.
That might be true, I'm on Eng 1.04, but I've tried installing Paranoid Android again which worked for me on 1.04, so is there any way I could possibly fix this and get it to boot
Yeah, you definitely need HBOOT 1.57 (Juop HBOOT, the one for Virgin Mobile) if you want this to run. Optionally you can also use 1.58 (Evo 3D ICS Bootloader), but you'll need to modify the SPC in info.txt to make it "02" or "2" I forget which one.
You can of course always fuse the build with the Virgin Mobile Leak kernel, and while you'll lose some stability, it will make it compatible with the ENG Bootloader. Sense 4.1 ROMs are not natively compatible with the ENG bootloader (1.04), because they use a modified version of the 2.89 (RUU) kernel.
thebeastglasser said:
Yeah, you definitely need HBOOT 1.57 (Juop HBOOT, the one for Virgin Mobile) if you want this to run. Optionally you can also use 1.58 (Evo 3D ICS Bootloader), but you'll need to modify the SPC in info.txt to make it "02" or "2" I forget which one.
You can of course always fuse the build with the Virgin Mobile Leak kernel, and while you'll lose some stability, it will make it compatible with the ENG Bootloader. Sense 4.1 ROMs are not natively compatible with the ENG bootloader (1.04), because they use a modified version of the 2.89 (RUU) kernel.
Click to expand...
Click to collapse
thank you, is there any way I can get my phone to boot? I've tried every ROM on my sdcard, whether its JB, MIUI, Sense, Sensless, and it seems to be stuck at this HTC logo, it won't play any boot animation or bootloop, its just stuck
Wipe all partitions, get the original HBOOT 1.57 on it, wipe all partitions again, and then flash Harmonia. Harmonia always boots for me 100% of the time. It's really the only surefire way of doing in my opinion.
If you don't have the Juop HBOOT, here's a download from my personal repository https://www.box.com/s/s64uphj0a37yj7mf3jx1
You probably already know, but rename it PG86IMG.zip, put it on your SD card, and go into bootloader. Once it's there, do the update. Take out your SD and get another one (because you won't be able to get to the recovery anymore) and put Harmonia on it. Your phone should boot, this method has saved me more than once.
iZandeR said:
thank you, is there any way I can get my phone to boot? I've tried every ROM on my sdcard, whether its JB, MIUI, Sense, Sensless, and it seems to be stuck at this HTC logo, it won't play any boot animation or bootloop, its just stuck
Click to expand...
Click to collapse
Some people with this problem have needed to flash the RUU.exe to get it resolved. The Virgin Mobile version is here.
Since you are S-OFF you can just flash that from Windows after putting the phone into "fastboot usb" mode, then flash a custom bootloader and recovery and you will be back in business. You can also boot into the stock ROM and download and install the VM OTA update before flashing the custom recovery. Should take no more than a half hour.
I have a link to the bootloaders and instructions for flashing them available in this post and they all work with both the Evo 3D and Evo V.
ramjet73
thebeastglasser said:
Wipe all partitions, get the original HBOOT 1.57 on it, wipe all partitions again, and then flash Harmonia. Harmonia always boots for me 100% of the time. It's really the only surefire way of doing in my opinion.
If you don't have the Juop HBOOT, here's a download from my personal repository https://www.box.com/s/s64uphj0a37yj7mf3jx1
You probably already know, but rename it PG86IMG.zip, put it on your SD card, and go into bootloader. Once it's there, do the update. Take out your SD and get another one (because you won't be able to get to the recovery anymore) and put Harmonia on it. Your phone should boot, this method has saved me more than once.
Click to expand...
Click to collapse
I updated the HBOOT, but when I plug in my other SD card, it's trying to update the Radio, so I hit no and it automatically reboots (and stays frozen)
on the second SD card, all I need is the harmonia zip?
iZandeR said:
I updated the HBOOT, but when I plug in my other SD card, it's trying to update the Radio, so I hit no and it automatically reboots (and stays frozen)
on the second SD card, all I need is the harmonia zip?
Click to expand...
Click to collapse
You need to delete the PG86IMG.zip file on your SD card. See my previous post if you can't get it working with your current direction.
ramjet73
Yeah, delete it, or snag a second SD. All you're going to need is the harmonia.zip. Flash it, and you should be good to go.
EDIT: And if you really can't get it to boot, the RUU is definitely the way to go. Ramjet is totally right there.
ZWYATT said:
My guess is Viper needs 1.58 hboot since it a sense rom.
And yeah, wrong forum.
Click to expand...
Click to collapse
Not anymore, Virus was nice enough to make his ViperROM compatible with any Hboot I hear.
aoaleman said:
Not anymore, Virus was nice enough to make his ViperROM compatible with any Hboot I hear.
Click to expand...
Click to collapse
That's true. I have r304 booting successfully with the ENG 1.04 hboot.
ramjet73
thebeastglasser said:
Yeah, delete it, or snag a second SD. All you're going to need is the harmonia.zip. Flash it, and you should be good to go.
EDIT: And if you really can't get it to boot, the RUU is definitely the way to go. Ramjet is totally right there.
Click to expand...
Click to collapse
Thanks for the advice, I'll give it a try!
aoaleman said:
Not anymore, Virus was nice enough to make his ViperROM compatible with any Hboot I hear.
Click to expand...
Click to collapse
Yeah, that's what I thought too.
I don't want to be giving my friend the wrong information. When his sprint 3d was boot 1.5 I took it and soff it for him downgrading to 1.4. Now recently he upgraded to hboot 1.58 and it says relocked at the top. Of course he still has recovery and still is rooted.
My question is since his phone is soff can't he just still flash whatever with no issues? Does he have to do dev unlock again?
I own a rezound and have had many HTC devices and soff has always been the key to everything for me. Any help would be appreciated
With s-off there's no need to unlock his boot loader again. (For example) If he wants to flash an aosp rom, all he's gotta do is downgrade his hboot via boot loader.
Perfect. Already installed JP bear latest hboot and went to twrp. Making a backup now. That's what I was thinking but I wanted some confirmation. Its been a while since I messed with an Evo 3d
Hmmm. It won't flash paranoid android. Even tried the 1.04 eng hboot. Any ideas? Using twrp recovery. Latest radios and 1.04 eng hboot.
stkiswr said:
Hmmm. It won't flash paranoid android. Even tried the 1.04 eng hboot. Any ideas? Using twrp recovery. Latest radios and 1.04 eng hboot.
Click to expand...
Click to collapse
A lot of people have had better luck with 4EXT on the Evo 3D. You can download the Recovery Updater for free from the www.4ext.net website and install the current version of 4EXT Recovery from that app. Then "format all partitions except SD card" in the wipe/format menu of the recovery, and try flashing PA again.
ramjet73
ramjet73 said:
A lot of people have had better luck with 4EXT on the Evo 3D. You can download the Recovery Updater for free from the www.4ext.net website and install the current version of 4EXT Recovery from that app. Then "format all partitions except SD card" in the wipe/format menu of the recovery, and try flashing PA again.
ramjet73
Click to expand...
Click to collapse
K. I'm working on that now. I let you know soon its backing up now. Thank you for the heads up. Do you think I should go back yo the latest jbear hboot? Or just leave the 1.04 eng hboot? He wants to be able to run these jellybean builds that are out
stkiswr said:
K. I'm working on that now. I let you know soon its backing up now. Thank you for the heads up. Do you think I should go back yo the latest jbear hboot? Or just leave the 1.04 eng hboot? He wants to be able to run these jellybean builds that are out
Click to expand...
Click to collapse
Stay with the ENG 1.04 hboot for now. The GB and AOSP based ROM's won't boot with the latest JBear (1.58.5858) so if you want to use a JBear version 1.50.5050 is better.
ramjet73
ramjet73 said:
Stay with the ENG 1.04 hboot for now. The GB and AOSP based ROM's won't boot with the latest JBear (1.58.5858) so if you want to use a JBear version 1.50.5050 is better.
ramjet73
Click to expand...
Click to collapse
Wow thank you for all the help. I just did everything and unfortunately it is just stuck in a never ending splash loop. Doesn't seem like the kernel/boot is being flashed. Made a backup so I should be good. Just sucks doing all the steps and being stuck.
What kernel are you flashing with pa?
Jsparta26 said:
What kernel are you flashing with pa?
Click to expand...
Click to collapse
It doesn't come with a kernel?
stkiswr said:
Wow thank you for all the help. I just did everything and unfortunately it is just stuck in a never ending splash loop. Doesn't seem like the kernel/boot is being flashed. Made a backup so I should be good. Just sucks doing all the steps and being stuck.
Click to expand...
Click to collapse
Are you doing the "format all partitions except SD card" in 4EXT right before flashing the ROM? Make sure to give it plenty of time to boot since sometimes the first boot can take up to 10 minutes.
ramjet73
stkiswr said:
It doesn't come with a kernel?
Click to expand...
Click to collapse
Well go with ramjets suggestion and try format all partitions minus sdcard along with full factory data wipe and cache/dalvik wipe and see if it boots up all the way.( it couldn't hurt to do all the wipes two or three times before you flash the rom). Just to make sure everything was wiped all the way.
Oh yeah. Step by step . It just never gets past splash. I looked into the ROM downloaded and saw a boot IMG but it really seems like a boot issue. Doesn't make a lot of sense to me. Soff, everything in right place, correct recovery and no boot. Not complaining, he still has his backup he is running and it restores backup correctly.
His phone was soff and he upgraded firmware to the 1.58 so it said locked in hboot. I just flashed 3 dif bootloader with no issues. Its def soff.
Ok, try flashing a different kernel. Try the Mac kernel that's located in Mazda's aokp jb thread. I believe buttered toast came with pa that your trying to flash. It could also be a bad download as well. You could always redownload the rom as well to see if that works. You never know about these things sometimes.
stkiswr said:
Oh yeah. Step by step . It just never gets past splash. I looked into the ROM downloaded and saw a boot IMG but it really seems like a boot issue. Doesn't make a lot of sense to me. Soff, everything in right place, correct recovery and no boot. Not complaining, he still has his backup he is running and it restores backup correctly.
His phone was soff and he upgraded firmware to the 1.58 so it said locked in hboot. I just flashed 3 dif bootloader with no issues. Its def soff.
Click to expand...
Click to collapse
You've tried all the standard stuff to get AOSP ROM's to boot on the Evo 3D. At this point I can only suggest that you flash the 2.89.651.2 SPrint ICS RUU from here, then reflash a custom bootloader and recovery. That will make sure everything is in sync and has cleared up this problem for other users.
You don't need to relock the bootloader (although I think you said it is already relocked) when flashing the RUU if the phone is S-OFF.
ramjet73
Yes, I will try to download ROM again and also grab that kernel.
I soff this phone for him when it was hboot 1.50. Then I reverted to 1.40 via brick method to get it soff. He has ran some form of an hboot/radios update because he was told to do that. Now we are working together and I am trying to fix all his stuff and get him setup correctly. I have an soff rezound and am sure his phone isn't seeing the boot.IMG.
Now today his phone said locked or relocked am not sure. I went ahead an changed his hboot to a recommended 1.04eng hboot. Installed 4ext recovery via the app that was linked. I am downloading gangam style cm10 to test just to see if something will boot. It successfully flashed a sense based ROM and booted fine thru an aroma installer that came with the ROM. In the installer I stated it was soff and had no issues. I will try the ROM and it doesn't boot I will jump back to recovery and flash a kernel and see. Thanks very much for all the help
Well, I have done it all. Not much more I can do. He may try to run the ICS ruu later but I just can't get any cm10 jb based ROM to boot. Y'all have been more than helpful catching me back up to speed on the 3d and while I agree this should be flashing alas it is not booting. I am positive its just not accepting the boot img for what ever reason because it never makes it far enough after reboot from recovery. Just endless quick splash screen reboots.
No problem. I just wanted to add that a lot of users are having weird issues with paranoid android. ( I'm subscribed to the thread) so it could be that your phone doesn't like pa for some reason. ( Not a diss on Lens Flare at All) but he's been having some issues with the rom and is more than likely trying to work on it. Hopefully you can get gangnam style up and running or even aokp jb. If none of these work, I would go with ramjets suggestion and run a ruu and then back to Asop.
Edit: guess you already tried them. Hopefully you get some better luck after you try the ruu method. Good luck.