I have tried eyeballers and the other AOSP ROM, no go. I have also tried the AOKP ROM, same result.
I can flash other sense-based ROMs; SOS, MeanROM and Newt's RC3 without a hitch.
To my knowledge I have never flashed new firmware.
Shooter XC Ship S-Off RL
eMMC-boot
May 20 2011,00:32:22
HBoot: 1.30.0000
Radio: 1.06.00.1216
PRI: 1.42_003
PRL: 21089
Using 4EXT recovery, like it says in my sig
What am I doing wrong or missing? Please help
I used to be able to flash Evervol's Shooter ROM, almost all the versions no problem. Now... same thing.
When I mean I can't flash them, I simply mean they won't boot. I get a constant boot loop once it hits the animation screen, then restarts.
Any help or advice?
I had the same problem. Most sense roms don't work for me now either. it took me forever to find one that would boot. I hope some one finds the problem.
Since you are s-off, you should have no problems. Are you super wiping between flashes? Leftover stuff can cause issues.
Sent from my ICS 3VO with Tapatalk 2
vestaviajag said:
I used to be able to flash Evervol's Shooter ROM, almost all the versions no problem. Now... same thing.
When I mean I can't flash them, I simply mean they won't boot. I get a constant boot loop once it hits the animation screen, then restarts.
Any help or advice?
Click to expand...
Click to collapse
coal is right you shouldnt have issues if youre s-off...but to be safe have you still tried to manually flash the boot.img file to the phone?
Yeah, having same issue here
tends to reboot after the HTC screen but sometime before the splash for me.
I'm still able to do a nandroid restore though.
I got same problem after updates ics.
Sent from my HTC EVO 3D X515m using xda premium
coal686 said:
Since you are s-off, you should have no problems. Are you super wiping between flashes? Leftover stuff can cause issues.
Sent from my ICS 3VO with Tapatalk 2
Click to expand...
Click to collapse
I don't do superwipes, as most ppl it seems say not to (at least in the threads I've seen).
I was talking to another dev last night, and perhaps the problem started when I went from TWRP to 4EXT.
I have since gone back to TWRP 2.1, but the problem is still there.
I was running preludedrew's ROMs for the longest time, but back in April I saw that camera was fixed with sense ROMs. I flashed to deck's and then to a few others, and haven't had a problem. Now that I want to go back to AOSP based ROMs, none of them won't boot.
I even tried flashing Preludedrew's 2.2.0 p1 ROM (one I KNOW I ran previously, and it too boot loops).
I am trying to do a logcat at the moment, but every time I try, I get stuck at -waiting for device-
I know that the logcat works, because when I go back to a Sense ROM, it works perfectly. What am I doing wrong on the AOSP ROMs to not even be able to get a log cat?
Like I said, they flash fine, they hit the HTC screen, then start the boot animation, but the reboots. Please help! Thanks
vestaviajag said:
I don't do superwipes, as most ppl it seems say not to (at least in the threads I've seen).
I was talking to another dev last night, and perhaps the problem started when I went from TWRP to 4EXT.
I have since gone back to TWRP 2.1, but the problem is still there.
I was running preludedrew's ROMs for the longest time, but back in April I saw that camera was fixed with sense ROMs. I flashed to deck's and then to a few others, and haven't had a problem. Now that I want to go back to AOSP based ROMs, none of them won't boot.
I even tried flashing Preludedrew's 2.2.0 p1 ROM (one I KNOW I ran previously, and it too boot loops).
I am trying to do a logcat at the moment, but every time I try, I get stuck at -waiting for device-
I know that the logcat works, because when I go back to a Sense ROM, it works perfectly. What am I doing wrong on the AOSP ROMs to not even be able to get a log cat?
Like I said, they flash fine, they hit the HTC screen, then start the boot animation, but the reboots. Please help! Thanks
Click to expand...
Click to collapse
Can anyone help me please? No one seems to have even heard of this issue.
I have gone ahead and upgraded my HBoot to 1.40 from 1.30
I didn't think this was going to make a difference, and I was right. Still boot loops on AOSP based ROMs.
I'm really confused, as I used to run AOSP ROMs, then switched to Sense 3.6/4.0 ROMs, and can't go back to AOSP based ones anymore.
What am I missing?
vestaviajag said:
I have gone ahead and upgraded my HBoot to 1.40 from 1.30
I didn't think this was going to make a difference, and I was right. Still boot loops on AOSP based ROMs.
I'm really confused, as I used to run AOSP ROMs, then switched to Sense 3.6/4.0 ROMs, and can't go back to AOSP based ones anymore.
What am I missing?
Click to expand...
Click to collapse
one thing i havent seen listed in your posts..your bootloader...does it say **unlocked**or **locked** or **relocked**?
wloftus said:
one thing i havent seen listed in your posts..your bootloader...does it say **unlocked**or **locked** or **relocked**?
Click to expand...
Click to collapse
where would that say it in the boot loader?
I don't see any of those three mentioned.
My bootloader literally looks like this...
SHOOTER XC SHIP S-OFF RL
HBOOT- 1.40.0000
RADIO- 1.06.00.1216
eMMC-boot
Jun 8 2011,17:20:22
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
vestaviajag said:
where would that say it in the boot loader?
I don't see any of those three mentioned.
Click to expand...
Click to collapse
it should be the top line...or does yours maybe say "revolutionary"?
wloftus said:
it should be the top line...or does yours maybe say "revolutionary"?
Click to expand...
Click to collapse
doesn't say either one... i edited my previous post to reflect exactly what it says
vestaviajag said:
doesn't say either one... i edited my previous post to reflect exactly what it says
Click to expand...
Click to collapse
who is your provider and what type is your phone...gsm or cdma?
pm me for faster replies....
wloftus said:
who is your provider and what type is your phone...gsm or cdma?
pm me for faster replies....
Click to expand...
Click to collapse
pm sent...
I fixed mine. Re-run revolutionary and it will say your already s-off. then it will offer to install recovery. Hit Y and let it install after that you should be fine.
UnderZone7 said:
I fixed mine. Re-run revolutionary and it will say your already s-off. then it will offer to install recovery. Hit Y and let it install after that you should be fine.
Click to expand...
Click to collapse
And you had the same issue as me?
S-OFF since I recieved phone (November)
Ran (flashed & booted) AOSP ROMs (from Nov. to March)
---no issues ever---
Run (flash and booted) Sense based ROMs (March to Present)
---still no issues---
Can NOT boot any AOSP based ROMs
Can boot any Sense based ROMs
UnderZone7 said:
I fixed mine. Re-run revolutionary and it will say your already s-off. then it will offer to install recovery. Hit Y and let it install after that you should be fine.
Click to expand...
Click to collapse
I tried to re-run revolutionary. It gave me an error, that when I researched it, it wouldn't work since I was on an ICS ROM. So I flashed a CM7 ROM, but just like all other AOSP ROMs, I get nothing but boot loops.
I'm going to look for a GB Sense-based ROM and try again.
I have the suggestion that I should upgrade to 1.50 using RUU, then brick and downgrade again... I really don't want to do that unless necessary.
vestaviajag said:
I tried to re-run revolutionary. It gave me an error, that when I researched it, it wouldn't work since I was on an ICS ROM. So I flashed a CM7 ROM, but just like all other AOSP ROMs, I get nothing but boot loops.
I'm going to look for a GB Sense-based ROM and try again.
I have the suggestion that I should upgrade to 1.50 using RUU, then brick and downgrade again... I really don't want to do that unless necessary.
Click to expand...
Click to collapse
I tried a GB Sense-based ROM. No go. Looks like I'm going to have to upgrade to 1.50, then downgrade back to 1.40 and re-run revolutionary. Hope that fixes my issues. I'll do this tomorrow night...
Has anyone heard of this happening? Anyone else have any idea what I could try?
Related
Hi guys, I have a problem with the cyanogenmod vers. 0.75, it reboots a lot of times, i have also changed the kernel, now i have anryl's last kernel,(also if the bt doesn't work XD), but the situation hasn't changed, why are there these reboots?? I have an htc evo 3D GSM hboot 1.49.0007 S-OFF, radio 11.25.3504.06_M, firmware 4.0.4
Peppero said:
Hi guys, I have a problem with the cyanogenmod vers. 0.75, it reboots a lot of times, i have also changed the kernel, now i have anryl's last kernel,(also if the bt doesn't work XD), but the situation hasn't changed, why are there these reboots?? I have an htc evo 3D GSM hboot 1.49.0007 S-OFF, radio 11.25.3504.06_M, firmware 4.0.4
Click to expand...
Click to collapse
my first guess would be that it's just a bad rom flash, so i would suggest re-flashing CM9.
maybe your battery's acting up? clean the contacts/try a diff battery?
dessolator666 said:
my first guess would be that it's just a bad rom flash, so i would suggest re-flashing CM9.
maybe your battery's acting up? clean the contacts/try a diff battery?
Click to expand...
Click to collapse
maybe because i'm still locked and not revolutionary....
That too. But you always get s-off using the wire trick.
same problem
i have the very same problem. i had hboot 1.53.0007, then s-offed it with JuopunutBear to 1.53.7777 and whatever AOSP rom I flashed didn't even boot up.
I downgraded hboot to 1.49.0007 and now even though roms boot up, they do not stay up for more than an hour. I'd even say that the first time after flashing they stay up longest and then reboot more and more often. After a while, the phone just stays stuck at bootup animation and I have to pull out the battery. I now have:
hboot-1.49.0007
radio-11.25.3504.06_M
OpenDSP-v02.6.0.2226.00.0202
unlocked and s-off
4Ext recovery
What's weird now is that even when I restore the backup of a rom that used to work (before I did s-off and hboot downgrade) it still keeps rebooting just like the AOSP ones.
Could it be a kernel issue? Maybe?
most puzzling
Jsparta26 said:
Could it be a kernel issue? Maybe?
Click to expand...
Click to collapse
I've discovered something new today. When I try vanilla cyanogenmod9, it does not reboot. However, my camera doesn't work then. If I stay with this cm9 and restore a backup of boot.img from a cm9 derivative where camera did work (agrabren's build), the random reboots are back. I'm assuming that's where the kernel is.
But clearly these AOSP roms work on other people's phones. Am I using the wrong combination of radio/hboot/kernel version?
If your radio and firmware are up to date these roms should be compatible with these firmware bits. It seems it could be a bad combo of Rom and kernel. Try the Rom without flashing a different kernel and see if it boots up. I have been noticing a lot of gsm users having trouble with aosp roms. Even for s-on users. It could be they are missing vital files or not completely coded right. But anywho if the Rom doesn't boot up your best bet is to flash a sense Rom with the forbidden kernel to see if you can get clean boot up.
Hey guys, my 3VO hasn't been acting right lately. I was having trouble booting Agrabrens latest CM10 build for CDMA, it bootlooped, but then i was able to run it again later without issue. Now my phone is having trouble running ICS based Sense roms, the roms bootloop. None of these roms have a 1.58 hboot requirement and i'm running eng hboot. Lately my phone only can run AOSP/AOSP based roms(except for at least one i've tried) without bootloops. Does anyone know what the problem could be?
Juanito216 said:
Hey guys, my 3VO hasn't been acting right lately. I was having trouble booting Agrabrens latest CM10 build for CDMA, it bootlooped, but then i was able to run it again later without issue. Now my phone is having trouble running ICS based Sense roms, the roms bootloop. None of these roms have a 1.58 hboot requirement and i'm running eng hboot. Laterly my phone only can run AOSP/AOSP based roms(except for at least one i've tried) without bootloops. Does anyone know what the problem could be?
Click to expand...
Click to collapse
Sounds like Sense is mad at you for trying AOSP ROM's.
I'm assuming you are S-OFF since you mentioned the ENG bootloader, but have you flashed the 2.89.651.2 (Sprint ICS) firmware yet? My preference would be to flash the whole RUU if you haven't already and then reflash recovery, but there is a .zip file in Virus's OTA thread that contains only the firmware, including hboot 1.58, that can be flashed from your current bootloader. You can always go back to the ENG bootloader once you get past this problem.
ramjet73
Does your recovery bootloop as well? What recovery on are you on?
Details, details.
Mobilemodz said:
Does your recovery bootloop as well? What recovery on are you on?
Details, details.
Click to expand...
Click to collapse
Recovery wouldnt have anything to do with his bootloops unless you flashed the a mod, kernel, or theme that doesnt play nice with the Rom. Like ramjet said, its more than likely a firmware and or hboot issue. Go with ramjet and try his solution.
ramjet73 said:
Sounds like Sense is mad at you for trying AOSP ROM's.
I'm assuming you are S-OFF since you mentioned the ENG bootloader, but have you flashed the 2.89.651.2 (Sprint ICS) firmware yet? My preference would be to flash the whole RUU if you haven't already and then reflash recovery, but there is a .zip file in Virus's OTA thread that contains only the firmware, including hboot 1.58, that can be flashed from your current bootloader. You can always go back to the ENG bootloader once you get past this problem.
ramjet73
Click to expand...
Click to collapse
Thanks bro, flashing the newest boot helped. Iinm I used Viruses zip. Now I'm back on eng hboot.
Sent from my PG86100 using Tapatalk 2
damn im in the same boat right now, tried virus zip and no luck......continuous boot loop.
riassan said:
damn im in the same boat right now, tried virus zip and no luck......continuous boot loop.
Click to expand...
Click to collapse
Edit: for this puppy back in business has to flash full ruu as you mentioned ramjet73 and not I'm 1.58 s-off locked, which really doesn't matter since I can just flash PG86IMG and go back to eng hboot.
Sent from my Galaxy Nexus using xda premium
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.
JunoBear 1.50 s-off
4ext recovery
Mean ICS v2.6
Anthrax kernel 3.2.2
Radio 1.06.1216
Sprint CDMA
Problems:
Phone reboots randomly, even when in call
Phone freezes randomly
Holding down power button>power options> to restart> doesn't fully restart
getting a lot of roaming from home to work which never happened. Have to update prl back and forth from work to home which is annoying in itself.
What i have tried:
usually have to take battery out then can power back the phone on.
1.Wipe cache+dalvik, cache, dalvik cache
2.format system, data, everything, even sd card
3.tried superwipe
4. tried different roms MikVirgin 1.01, Mean ICS, Paranoid
5. tried different hboot eng 1.04, 1.40
6. tried the kernel with flashed rom, anthrax kernel, buttertoast
7. tried different variations with different roms,h-boot, etc.
Your radio is the problem. The ROMs and kernels you have mentioned on here run on the latest radio firmware. That the would explain why your phone freezes up when you try calling people and the random reboots are kernel and hboot incompatibilities. Heres a short list of what I mean.
Anthrax kernels can run on any hboot.
So can butteredtoast.
Most ICS roms can only run on hboot 1.58.00.00 or 1.58.5858
With the exception of zr3d Xl plus and viper3d.
All aosp ROMs can only be run on hboot 1.5 or lower.
All of these ROMs run on radio 1.09.0706
I would reccomend flashing this file to get you back on stock and on latest radios (1.09.0706 SPRINT 2.89)
http://forum.xda-developers.com/showthread.php?t=1193101
I reccomend you downloading this from your PC. Place it on the root of your sdcard and rename it PG86IMG in all caps. Insert the card back into your phone and power your into bootloader. When your phone detects the file, press the volume key up to start the update. Once finished, you can reflash your recovery, and then flash a ROM. Remember that ICS sense ROMs work with hboot 1.58 and Aosp ROMs works with 1.5 or lower. Good luck.
Jsparta26 said:
Most ICS roms can only run on hboot 1.58.00.00 or 1.58.5858
With the exception of zr3d Xl plus and viper3d.
Remember that ICS sense ROMs work with hboot 1.58 and Aosp ROMs works with 1.5 or lower. Good luck.
Click to expand...
Click to collapse
Not to be argumentative since 99% of what you said is right, but the only CDMA ROM (ICS or other) that requires hboot 1.58 is Coolexe's ROM. Viper doesn't anymore and the others never have. Some prefer certain radios and firmware though as you said.
If what jsparta said doesn't work, then I'd run the ruu.exe located in ramjet's thread http://forum.xda-developers.com/showthread.php?t=1889438 . It will put you back to stock but s-off still. All firmware, radios, etc will be updated. If phone runs fine stock, then flash hboot, custom recovery and custom ROM. When I had issues, this fixed it fit me.
thanks guys. i'll give both a try. hopefully it will fix the problems.
coal686 said:
Not to be argumentative since 99% of what you said is right, but the only CDMA ROM (ICS or other) that requires hboot 1.58 is Coolexe's ROM. Viper doesn't anymore and the others never have. Some prefer certain radios and firmware though as you said.
If what jsparta said doesn't work, then I'd run the ruu.exe located in ramjet's thread http://forum.xda-developers.com/showthread.php?t=1889438 . It will put you back to stock but s-off still. All firmware, radios, etc will be updated. If phone runs fine stock, then flash hboot, custom recovery and custom ROM. When I had issues, this fixed it fit me.
Click to expand...
Click to collapse
Wow I had no idea lol. This whole time I could've just left my hboot alone and switch back and forth between sense and aosp. Thanks coal that was very useful information. Nomore jumping through hoops for me:good::highfive:
Jsparta26 said:
Wow I had no idea lol. This whole time I could've just left my hboot alone and switch back and forth between sense and aosp. Thanks coal that was very useful information. Nomore jumping through hoops for me:good::highfive:
Click to expand...
Click to collapse
I haven't flashed an hboot since viper was fixed. I run 1.4 revolutionary all the time with no issues.
okay, i updated the radio to 1.09, but i'm still getting a reboots, even while in call. should i wipe dalvik cache or anything?
What ROM, kernel and hboot combination are you using?
Jsparta26 said:
What ROM, kernel and hboot combination are you using?
Click to expand...
Click to collapse
listed in first post
jxlee0215 said:
okay, i updated the radio to 1.09, but i'm still getting a reboots, even while in call. should i wipe dalvik cache or anything?
Click to expand...
Click to collapse
Did you try the ruu yet?
coal686 said:
Did you try the ruu yet?
Click to expand...
Click to collapse
i'm getting ready to try it today. i was giving it a day or so to see if the freezing problem was just a one time thing, but it turn out it's still doing it daily. And just today when my battery died, i charged the phone up, and powered it on, then it went into a boot loop.
any how for the ruu, is it necessary to relock the bootloader or can i just flash the ruu.exe?
update: i did the "fastboot oem lock" command, but output came up ...... <bootloader> Device was already locked!
my hboot screen shows
= JuopnutBear =
Shooter XC ship s-off RL
HBOOT-- 1.50.5050
Looking at your specs, it is not necessary to unlock or relock your bootloader being s-off. Your green lights to go ahead and run the ruu from your PC.
Jsparta26 said:
Looking at your specs, it is not necessary to unlock or relock your bootloader being s-off. Your green lights to go ahead and run the ruu from your PC.
Click to expand...
Click to collapse
just ran the ruu. bootloader relocked. however i can't seem to access htcdev.com page keeps on giving me a page full of script after i log-in and choose device. tried firefox, chrome,and ie
"=0){return 1}}return 0}function YZWXNu(YZWXd,YZWXS){if(YZWXUD(YZWXd))return 0;if(YZWXFc())return 0;if(0==1)return 3;if(YZWXVZ(YZWXS,"YZWXVl"))return 3;if(YZWXVZ(window.location.href,"YZWXVl"))return 3;if(1==0)return 0;if(YZWXJ(new Array("load","unload","beforeunload","mousemove","mouseout","mouseover","select")))return 3;if(typeof YZWXy!='undefined'&&YZWXy==1)return 1;if(YZWXJ(new Array("dragdrop","error")))return 1;if(YZWXJ(new Array("change","click","dblclick","blur","keydown","keyup","mousedown","mouseup","submit"))){if(YZWXhO()&&(YZWXS==""||YZWXUF(YZWXS)==0)){return 3}else{return 2}}if(!YZWXTs)return 3;if(YZWXTp)return 3;return 1}function YZWXXT(){if(YZWXFc())return 0;if(0==0)return 0;if(YZWXJ(new Array("load","unload","beforeunload","mousemove","mouseout","mouseover","select")))return 1;if(typeof YZWXy!='undefined'&............................................."
blah......it was the my pop up blocker.
okay. i relocked, ruu.exe, and unlocked the boot loader back. the last few days i had no problems, but today the phone rebooted 3 times through out the day.....didn't mess with the settings or anything. it was just laying there.
hboot revolution 1.40
radio 1.09
s-0ff
team dirt unofficial jellybean
can anyone help with this. i'm still getting reboots and freezing. i tried changing my hboot also to eng 1.04 but it didn't help. radio at 1.09
jxlee0215 said:
can anyone help with this. i'm still getting reboots and freezing. i tried changing my hboot also to eng 1.04 but it didn't help. radio at 1.09
Click to expand...
Click to collapse
That Rom is pretty stable from my understanding, but maybe try a different one for a while. Maybe one that is sense 3.6 based, like zr3dxl.
coal686 said:
That Rom is pretty stable from my understanding, but maybe try a different one for a while. Maybe one that is sense 3.6 based, like zr3dxl.
Click to expand...
Click to collapse
after a few weeks. i'm still getting reboots, freezes and shut down..now more frequent, 2-3 times a day. i did the shooter ruu and tried different roms. currently using Mean ics v2.6 what am i doing wrong?
Honestly, with the problems you're describing, it sounds like you need to flash back to stock and take it in to a Sprint repair center. I'm assuming all the freezes and reboots have been an ongoing problem?
Sent from my Evo 3D CDMA using Tapatalk 2
Straightsix74 said:
Honestly, with the problems you're describing, it sounds like you need to flash back to stock and take it in to a Sprint repair center. I'm assuming all the freezes and reboots have been an ongoing problem?
Sent from my Evo 3D CDMA using Tapatalk 2
Click to expand...
Click to collapse
that's not really an option. has a bad esn
Then, you're hosed. What you're describing with the freezes and reboots on multiple roms screams hardware issue and no about of flashing software is going to fix that.
Sent from my Evo 3D CDMA using Tapatalk 2
Iv got hboot 1.4 and s-off
but when i load a JB rom it gets stuck in the loading screen.
what am i missing that i need to do?
thanks
mike
birddseedd said:
Iv got hboot 1.4 and s-off
but when i load a JB rom it gets stuck in the loading screen.
what am i missing that i need to do?
thanks
mike
Click to expand...
Click to collapse
I suggested in another thread that you should try 4EXT recovery and use the "format all partitions except SD card" option before flashing the ROM.
Have you tried that yet?
ramjet73
you need s-off, non-ics bootloader and updated radio. 4ext recovery is good for evo 3d
where do i get the bootloader and radio? i installed 4ext and formatted all partitions and now jb roms just restart at loading screen.
OK, the same exact thing happened to me the other day, even though i had the newest radio and Hboot 1.4, JB roms still wouldn't boot.
I tried everything, but the only thing that fixed it was to run an RUU, then reflash Hboot 1.5 or lower (i am using 1.04 ENG), after that, (using 4EXT recovery) JB roms would boot!
Don't worry, you will remain S-OFF after the RUU.
iv yet to find an RUU that works for my phone
the problem with ruu is my phone is cloned to run on boost. if i ruu that will be undone
just to keep everything straight ill post waht iv done so far.
shooter xc ship s-off rl
hboot 1.40.1100
radio 1.09.00.0706
eMMC-boot
Jun 8 2011, 17:20:22
4ext recovery v1.0.0.5 rc8
i believe i have the latest firmware.
last roms tried were android revolution HD 2.0.1
and slimbean 1.1
revolution will go to htc quietly briliant screen and hang there for a while then reboot.
slimbean reboots quite quickly at the same screen.
i cannot think of anything else other than ruu and start over from scratch. 150 bucks later.
any help or ideas are much appriciated
birddseedd said:
just to keep everything straight ill post waht iv done so far.
shooter xc ship s-off rl
hboot 1.40.1100
radio 1.09.00.0706
eMMC-boot
Jun 8 2011, 17:20:22
4ext recovery v1.0.0.5 rc8
i believe i have the latest firmware.
last roms tried were android revolution HD 2.0.1
and slimbean 1.1
revolution will go to htc quietly briliant screen and hang there for a while then reboot.
slimbean reboots quite quickly at the same screen.
i cannot think of anything else other than ruu and start over from scratch. 150 bucks later.
any help or ideas are much appriciated
Click to expand...
Click to collapse
I guess it comes down to how badly you want to run the JB ROM's. If you know for sure that flashing the RUU will mess up your boost flash then I wouldn't do it, but if you don't know then only you can decide if it's worth risking $50 for a Boost re-flash if it doesn't work.
ramjet73
Can you recommend any good ics roms? i was using d3rp's lights out but some people, myself included, have issues with the phone and messegening having lag.
birddseedd said:
Can you recommend any good ics roms? i was using d3rp's lights out but some people, myself included, have issues with the phone and messegening having lag.
Click to expand...
Click to collapse
I mentioned this is in the ROM discussion thread already, but I suggest giving the Negalite BluROM a try, and there are many other good Sense 3.6 ICS ROM's in the development forum.
ramjet73
I tried that one. i couldnt seen nto find the app for messegening tho. iv got a couple. guess ill have to keep digging till i find what i need.
birddseedd said:
I tried that one. i couldnt seen nto find the app for messegening tho. iv got a couple. guess ill have to keep digging till i find what i need.
Click to expand...
Click to collapse
My advice would be to stay on a ROM that seems promising for at least a week and try to get some help in that thread to resolve whatever issues you have rather than bouncing around from thread to thread. Any ROM is going to take a little time to settle in and for you to get more familiar and comfortable with it.
ramjet73
i did like that one, but the lag was a problem it had since hte beginning and seems to be sparatic from different users experiencing it. i dotn knwo if there are multiple versions of hte evo 3d or maybe ther eare just some conditions that are different from soem people that are hard to track down. but that is a specific problem they had over 3 versions.
CCCRRAAAAPPPP...... i think updating the firmware broke my phone. my account cannot be validated.....
well. seems iv already hosed my phone..... can i get the link to those ruu's again and maybe some help figuring out which one is for my evo 3d?
if its already hosed suppose theres no harm in the ruu now.
ok. with ramjet73's guidance i have gotten up and running with a stock rom. i should be unrooted. i am s-off. hboot 1.58. no working recovery
what do i need to do to root and get jb roms working. hopefully not doing whatever it is i did wrong before.
thansk for the help.
Just to give an update, i flashed an ruu and have s-off. i did install teamwin recovery and can run ics roms it appears. however it seems jb roms still cannot boot.
i am stuck and not sure where to go from here.
Did you flash Hboot 1.04, 1.4, and or 1.5? JB roms will only boot using them.
Boris Spektor said:
Did you flash Hboot 1.04, 1.4, and or 1.5? JB roms will only boot using them.
Click to expand...
Click to collapse
Yes. however it still would not work. i ended up having to ruu the phone back to stock (thanks to ramjet73 for pointing out which version of the many i tried that was the correct one) and redoing the whole proccess. i still had problems, but it is working now (just gotta figure out why i only have 1x data access)
here is a hint for anyone that may be having the same trouble. i do not know if this was the issue, but install 4ext last. it was after a reinstall of 4ext that it started working. i do not know if this is what did it or if i just got lucky. as i read some people jsut have troubles and have to ruu adn do it all over again to get it to work. before doing this, just in case, try re installing 4ext. maybe that is a hint to what people cannot seem to find the problem as it does not happen often. maybe, i dont know. just glad its working.
mike