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
Related
i've been wondering if anyone else has been having any issues with mean rom ics, i've flashed it twice, and even done a full wipe and everything. but it seems every time i restart (or the phone powers down) i go through about 6 - 10 crashes before it can run stable enough for me to use it at all. has anyone else had this issue or have this issue and can shed any light on what could be causing it?
Strange. Are you s-on or s-off?
Read, Search, Read again, ... Then Ask with Tapatalk 2
Im s-off via Juopunutbear. My phone came with bootloader 1.50 but I updated for ics using what was posted Here, so I could retain s-off
I was having some odd things happen when I first moved to MeanROM 2.6 as well so I flashed the 2.89 RUU when it became available to make sure that the software and firmware were completely in sync. That's pretty easy to do if you are S-OFF since all you have to do is connect your phone to a Windows PC and run the RUU.exe, then flash a custom recovery and optionally a different bootloader.
Things seem to be a little smoother for me after flashing the 2.89 RUU as a base.
ramjet73
ramjet73 said:
I was having some odd things happen when I first moved to MeanROM 2.6 as well so I flashed the 2.89 RUU when it became available to make sure that the software and firmware were completely in sync. That's pretty easy to do if you are S-OFF since all you have to do is connect your phone to a Windows PC and run the RUU.exe, then flash a custom recovery and optionally a different bootloader.
Things seem to be a little smoother for me after flashing the 2.89 RUU as a base.
ramjet73
Click to expand...
Click to collapse
but isn't flashing via bootloader the firmware bits doing (the long-ish way) the same thing as what the RUU would do? I'm still on the stock HTC bootloader for 1.58 because i was updated to it from the firmware bits, but if the RUU does something extra then maybe i would benefit from flashing with it. but i mean i also have MIUI 2.8.17 and i installed it (after i was able to use my phone) through boot manager a few weeks after installing MeanROM and booting to it yields me no issues of crashing or anything. do note its based off (supposedly) the GSM port for the E3D as well as files from the sprint/htc ICS release
AlexxSeven said:
but isn't flashing via bootloader the firmware bits doing (the long-ish way) the same thing as what the RUU would do? I'm still on the stock HTC bootloader for 1.58 because i was updated to it from the firmware bits, but if the RUU does something extra then maybe i would benefit from flashing with it. but i mean i also have MIUI 2.8.17 and i installed it (after i was able to use my phone) through boot manager a few weeks after installing MeanROM and booting to it yields me no issues of crashing or anything. do note its based off (supposedly) the GSM port for the E3D as well as files from the sprint/htc ICS release
Click to expand...
Click to collapse
There's no guaranty that flashing the RUU will fix anything but it did seem to help on my phone. The RUU flashes both the stock ROM and all the firmware, including the bootloader, so it makes your phone 100% stock except for the S-ON/S-OFF radio security and bootloader locked/unlocked status. It won't change either of those, but you must have your bootloader locked (or relocked) to run the RUU if S-ON.
After running the RUU.exe you can flash a custom recovery and bootloader if you want. It should be the same as returning to stock and taking the OTA update, but flashing the RUU.exe is faster and easier.
ramjet73
Hboot 1.5 s-on and I'm running meanrom ICS 2.6 .
I did the HTC unlock. Then installed Su zip from this site. Then I installed 4ext and rebooted into recovery...flashed the meanrom zip (it flashed the kernel that comes w the Rom ) and that was it. Now I'm on sw 2.89 build w the 3.0.16 kernel and like I said still s off and hboot 1.5
If anyone knows any where to get a kernel to overclock please let me know
Sent from my PG86100 using xda app-developers app
ramjet73 said:
There's no guaranty that flashing the RUU will fix anything but it did seem to help on my phone. The RUU flashes both the stock ROM and all the firmware, including the bootloader, so it makes your phone 100% stock except for the S-ON/S-OFF radio security and bootloader locked/unlocked status. It won't change either of those, but you must have your bootloader locked (or relocked) to run the RUU if S-ON.
After running the RUU.exe you can flash a custom recovery and bootloader if you want. It should be the same as returning to stock and taking the OTA update, but flashing the RUU.exe is faster and easier.
ramjet73
Click to expand...
Click to collapse
i actually decided to give it a try after making a nand backup ofc, and still had the same issues :s after re-flashing from my backup though it seems to boot fairly stable now. even between switching roms im not sure exactly why but could it have been an issue with anything that is permanent between any rom?
Here is where I am with my phone.
Shooter XC Ship S-OFF RL
HBOOT-1.40.1100
RADIO-0.97.10.0530
Rooted
clockworkmod
Cool Sense v11
-----------------------------------------
I am hoping that I am not the only one that has NO idea what to do with the HBOOT and what HBOOT I need or should be running.
So here are a few questions I hope other have. I guess things have changed a bit since I was on my EVO 4G?
Seeing that for now I am on a ICS rom, will it hurt to upgrade my HBOOT?
Will I lose anything by upgrading my HBOOT?
Can I run ICS and JB ROMS on the new HBOOT?
What is the HBOOT really? (help me understand it a little)
Can I run ANY recovery with any HBOOT?
HBOOT anf KERNEL's, do they play nice?
---------------------------------------------------------
Here is the deal, I want to jump to a JB rom as soon as one is fully working, and want to try out the new Cool Sense v11 but I think being on the old HBOOT is giving me boot loops, but even if not I want to understand them a little more and know if I should upgrade it.
Thanks for filling me in a bit!
Its not the hboot that gives bootloop. its the firmware. You are S-off so hboot doesnt really matter.
http://d-h.st/Mf1
put in sdcard. reboot to bootloader and accept update.
will wipe data so make a backup.
As for the recovery try 4EXT. best out there for evo 3d
and as for JB try agrabrens Disarmed Toaster. still a few bugs but really smooth
EM|NEM said:
Its not the hboot that gives bootloop. its the firmware. You are S-off so hboot doesnt really matter.
http://d-h.st/Mf1
put in sdcard. reboot to bootloader and accept update.
will wipe data so make a backup.
As for the recovery try 4EXT. best out there for evo 3d
and as for JB try agrabrens Disarmed Toaster. still a few bugs but really smooth
Click to expand...
Click to collapse
Whoa!
That PG86IMG.zip file looks like a complete set of firmware for a GSM phone and the OP clearly has a CDMA phone.
And much testing on the Evo 3D CDMA model has proven that the version of the bootloader installed, not just the rest of the firmware, can cause booting problems. The bootloader is actually part of the firmware and works in conjunction with the other firmware to write and erase partitions, in addition to the other functions it performs.
ramjet73
Sorry, should of said I am cdma (Sprint)
Sent from my PG86100 using xda premium
OP, I was in the same situation as you until yesterday. Now I'm latest hboot and unlocked (still s-off)
I took the advice in Tribulattifather's rom on the last page. Jbear's cdma ics hboot and latest 1.58 yesterday and I'm G2G. No issues whatsoever. Also if you're s-off you can change hboot anytime you likely. PM me if you need more info but its simple even for me who has half a brain
Edit
Here's more
http://forum.xda-developers.com/showthread.php?t=1885108
oops.. sorry my bad :S
should have realized that *facepalm*
I'm sure the hboot does matter but i was just saying that its not really a requirement to have the latest hboot to run JB,kernels or recoveries. I have the revolutionary hboot and havn't had any problems with the latest roms/kernels.
EM|NEM said:
oops.. sorry my bad :S
should have realized that *facepalm*
I'm sure the hboot does matter but i was just saying that its not really a requirement to have the latest hboot to run JB,kernels or recoveries. I have the revolutionary hboot and havn't had any problems with the latest roms/kernels.
Click to expand...
Click to collapse
I guess the GSM and CDMA models are a little different in that respect, since the most recent Sprint ICS 1.58 bootloader has problems booting GB and AOSP ROM's on the CDMA model. The older hboots do run those ROM's.
ramjet73
So I should. . .
Use this HBOOT
http://forum.xda-developers.com/showpost.php?p=30014044&postcount=7
PG86IMG_1.58-hboot.zip
This Recovery
http://forum.xda-developers.com/showthread.php?t=1561999
and I will be ok to run most, ICS or JB ROM?
Anymore I am only half sure what is going on, lol in the old days you could just flash away.
And thanks everyone!!!
Really, I am not sure if I have to do it in order or if it matters?
Also, I see 4ext will not let you update firmware or the radio. . . How do I know if I have the ones I should have. . ?
If coolexe's rom is using the new kernel, then the 1.4 hboot is causing the issue. You would need the 1.58 hboot.
1.58 hboot: needed to flash anything with the latest kernel. Can flash any sense based ics rom. Cannot flash AOSP, CM, or GB roms.
1.4 hboot: Can flash any custom rom except ones that use the new kernel.
No recovery can flash hboots or firmware , but since you are s-off, you can flash either hboot at will in the bootloader. You can also update to the latest firmware using freeza's 2.89 zip available in the development thread.
I think that answers all your questions, but if not, please reply.
Read, Search, Read again, ... Then Ask with Tapatalk 2
coal686 said:
If coolexe's rom is using the new kernel, then the 1.4 hboot is causing the issue. You would need the 1.58 hboot.
1.58 hboot: needed to flash anything with the latest kernel. Can flash any sense based ics rom. Cannot flash AOSP, CM, or GB roms.
1.4 hboot: Can flash any custom rom except ones that use the new kernel.
No recovery can flash hboots or firmware , but since you are s-off, you can flash either hboot at will in the bootloader. You can also update to the latest firmware using freeza's 2.89 zip available in the development thread.
I think that answers all your questions, but if not, please reply.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Click to expand...
Click to collapse
That about does it, just one more thing that I am not to clear on. How is the firmware different than a ROM?
chaos67731 said:
That about does it, just one more thing that I am not to clear on. How is the firmware different than a ROM?
Click to expand...
Click to collapse
Technically it could all be considered firmware since it is all flashed to the NAND memory of the phone, and an RUU.exe flashes all of it, but generally people think of the boot, system and data partitions as the "ROM" and more as software than firmware. The system and data partitions are also modified during normal operation which is generally not true of the firmware partitions. The "firmware" consists mostly of the bootloader, radios and low level functions similar to BIOS on a PC, and it gets flashed to different partitions.
ramjet73
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
I could not load what i believe is newer (ICS) roms. My phone would restart after the loading screen. so i did the s-off thing and i could now run ics roms.
now. i need to access the # codes. only one of them works. If i try older roms, including the backup from when i first rooted the phone, it gets to sense, then resets after a second or two.
is this because of S-OFF?
how can i undo the S-OFF so i can put my stock rom back on and access the # codes.
thanks for the help
No its not because of s-off.
What is your current hboot version?
What rom are you using now?
And your backup was ICS or Gingerbread?
If you want to boot a Gingerbread ROM you need to be on older hboot.
What is the code that you want to try?
I guess almost all Gingerbread dialer codes should work on sense based ICS rom.
mnomaanw said:
No its not because of s-off.
What is your current hboot version?
What rom are you using now?
And your backup was ICS or Gingerbread?
If you want to boot a Gingerbread ROM you need to be on older hboot.
What is the code that you want to try?
I guess almost all Gingerbread dialer codes should work on sense based ICS rom.
Click to expand...
Click to collapse
hboot is 1.58
iv tried several roms including my original backup.
i believe backup was gingerbread. what the phone came with 2 years ago.
only one of hte codes worked. i dont know which ones specificialy i need
for soem reason they jsut dont work on ics roms
i assumed it was s-off because s-on was what kept me from running ics
What are you trying to do?
birddseedd said:
hboot is 1.58
iv tried several roms including my original backup.
i believe backup was gingerbread. what the phone came with 2 years ago.
only one of hte codes worked. i dont know which ones specificialy i need
for soem reason they jsut dont work on ics roms
i assumed it was s-off because s-on was what kept me from running ics
Click to expand...
Click to collapse
You have hboot 1.58, so you have a Sprint evo 3d.. so you need hboot 1.4 or 1.5 or eng hboot or revolutionary hboot or jb 1.50.5050 to boot you gingerbread backup. Just download and try few of these by renaming them to PG86IMG.zip and installing through bootloader. If the backup is almost 2 year old try revolutionary or 1.40 hboot.
And what recovery are you using now? Back then there was no touch recoveries. Only non touch cwm. So the backup is most likely made from that recovery. I don't know whether your current recovery restores it correctly or not.
And what exactly are you trying to do? Most codes work on Sense based ICS roms.
mnomaanw said:
You have hboot 1.58, so you have a Sprint evo 3d.. so you need hboot 1.4 or 1.5 or eng hboot or revolutionary hboot or jb 1.50.5050 to boot you gingerbread backup. Just download and try few of these by renaming them to PG86IMG.zip and installing through bootloader. If the backup is almost 2 year old try revolutionary or 1.40 hboot.
And what recovery are you using now? Back then there was no touch recoveries. Only non touch cwm. So the backup is most likely made from that recovery. I don't know whether your current recovery restores it correctly or not.
And what exactly are you trying to do? Most codes work on Sense based ICS roms.
Click to expand...
Click to collapse
I dont know exactly which codes. but i know that only one of them worked.
basically i want to downgrade hboot and turn S-ON. i THINK this is what i need to do to run a gingerbread rom and have access to the # codes i need that wouldnt work on multiple ics roms
If you turn back to s-on you won't be able to downgrade.
But with s-off you can upgeade/downgrade anytime.
Your gingerbread rom will boot on s-off. There are many cases of bricked devices while turning s-off to s-on which can be fixed but there's no reason for you to turn it s-on, is there?
i dont know. s-off is what i had to do when i coudl boot gignerbread and not ics, so im under the assumption that to run gingerbread and not ics i need s-on. if this is not the case then all i need to do is go back to hboot 1.4? can you point me in the direction of downgrading please?
birddseedd said:
i dont know. s-off is what i had to do when i coudl boot gignerbread and not ics, so im under the assumption that to run gingerbread and not ics i need s-on. if this is not the case then all i need to do is go back to hboot 1.4? can you point me in the direction of downgrading please?
Click to expand...
Click to collapse
There's a difference between assumption and fact...
When you first did s-off you had a Gingerbread ROM and not ics and it was able to boot.
Currently I am dual booting with one ICS rom and one gingerbread rom and I'm s-off and they both boot perfectly. ON S-OFF GINGERBREAD BOOTS WITHOUT ISSUES.
Download the hboot 1.40.zip from somewhere (cannot attach using phone right now and I'm too lazy to search ramjet73 post ) and rename it to PG86IMG.zip and put it on root of sdcard then reboot into bootloader, let it scan and it will ask to update.. Hit volume up key then power key and it will reboot but before it boots, remove battery as your current ROM is not going to boot on that hboot unless it uses vm kernel. Now remove memory card and delete/rename/move that file from your sdcard using a card reader. Then boot into recovery and restore your backup. Make sure you use the same recovery that you used to make the backup. Only use the HBOOT 1.40 if you have evo 3d from sprint.
.
.
.
If you dont want to do all these download RUU. Exe file made for your phone from shipped-roms.com and run it and follow the instructions, it will get you to stock rom and will unroot your phone. Your phone will be like new with stock recovery but still s-off. You can still flash custom recoveries and ROMs and hboots later.
that site seems to not have an ruu for me
mnomaanw said:
There's a difference between assumption and fact...
When you first did s-off you had a Gingerbread ROM and not ics and it was able to boot.
Currently I am dual booting with one ICS rom and one gingerbread rom and I'm s-off and they both boot perfectly. ON S-OFF GINGERBREAD BOOTS WITHOUT ISSUES.
Download the hboot 1.40.zip from somewhere (cannot attach using phone right now and I'm too lazy to search ramjet73 post ) and rename it to PG86IMG.zip and put it on root of sdcard then reboot into bootloader, let it scan and it will ask to update.. Hit volume up key then power key and it will reboot but before it boots, remove battery as your current ROM is not going to boot on that hboot unless it uses vm kernel. Now remove memory card and delete/rename/move that file from your sdcard using a card reader. Then boot into recovery and restore your backup. Make sure you use the same recovery that you used to make the backup. Only use the HBOOT 1.40 if you have evo 3d from sprint.
.
.
.
If you dont want to do all these download RUU. Exe file made for your phone from shipped-roms.com and run it and follow the instructions, it will get you to stock rom and will unroot your phone. Your phone will be like new with stock recovery but still s-off. You can still flash custom recoveries and ROMs and hboots later.
Click to expand...
Click to collapse
i cannot seem to find an attached zip
birddseedd said:
that site seems to not have an ruu for me
Click to expand...
Click to collapse
Are you sure that you have HTC SHOOTER AKA EVO 3D?
These are RUUs from sprint from 1st to last
1. Gingerbread http://shipped-roms.com/download.ph...0.0518_NV_SPCS_1.15_release_193503_signed.exe
2. Gingerbread http://shipped-roms.com/download.ph...530_NV_NV_SPCS_1.16_release_198109_signed.exe
3. Gingerbread http://shipped-roms.com/download.ph...08_NV_SPCS_1.31_003_release_208230_signed.exe
4. Gingerbread http://shipped-roms.com/download.ph...08_NV_SPCS_1.31_003_release_219445_signed.exe
5. Gingerbread http://shipped-roms.com/download.ph...216_NV_NV_spcs_1.42_release_233304_signed.exe
6. ICS http://shipped-roms.com/download.ph...06__NV_NV_SPCS_1.43_release_271101_signed.exe
These are for sprint evo 3d......And not gsm or virgin.
EDIT : I see you edited it yourself.
yep. that is my phone
ok im confused. i thought that sense and apex were just ui options? i chose sense with a ics rom and now ##3424#. im confsued.
birddseedd said:
ok im confused. i thought that sense and apex were just ui options? i chose sense with a ics rom and now ##3424#. im confsued.
Click to expand...
Click to collapse
yes
raptoro07 said:
yes
Click to expand...
Click to collapse
grr. that doesnt help. lol. so sense vs apex is more than the ui? it is actualy involved in the core of the os? or do each simply have different dialers?