Related
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.
So I s-offed my wifes evo 3d a little bit ago, Afterwards I put the 1.04 hboot and CM 10.1 on her sd and flash them, Of course wiping in recovery because of the hboot flash, And it bootloops, So i'm like wtf, And I re-wipe, and re-flash. Still a bootloop, So I throw the sd in the pc and realize it corrupted so I format it, And throw back on the 1.04 bootloader and reflashed the rom, Still a bootloop,
So I run the ruu, It goes through, And boots back up so I'm like, Okay, Got it all taken care of.
So I flash the 1.04 bootloader once again and as i'm rebooting for the first time, bootloop. So, This is now seeming like a problem to me, Anyhelp? Ramjet maybe?
This is the same copy same download as the 1.04 bootloader that's running on my phone with CM 10.1 doing just fine.
Can't_Live_Without_My_Evo said:
So I flash the 1.04 bootloader once again and as i'm rebooting for the first time, bootloop. So, This is now seeming like a problem to me, Anyhelp? Ramjet maybe?
This is the same copy same download as the 1.04 bootloader that's running on my phone with CM 10.1 doing just fine.
Click to expand...
Click to collapse
Try the JBear 1.50.5050 hboot.
ramjet73
ramjet73 said:
Try the JBear 1.50.5050 hboot.
ramjet73
Click to expand...
Click to collapse
I'm currently running the RUU again trying to get it to at least boot stabily a time or two.
It's so weird seeing the stock boot animation boot loop lol.
Got it to boot, I feel a little better lol.
Is there a chance somethings seriously wrong? I tried 1.40 and 1.04 and both bootlooped.
ramjet73 said:
Try the JBear 1.50.5050 hboot.
ramjet73
Click to expand...
Click to collapse
Isn't that one GB?
Edit: After a ruu and a run through set up, I unchecked fastboot and checked usb debugging and then flashed the 1.50.5050 and it also bootloops.
What. The. Hell.
The only thing that'll boot up is stock.
Edit 2: So after the RUU I flash the 1.50.5050 you suggested, Bootloop as above stated, So I take out the sd and put the 1.58 stock hboot on it and flash that and it boots back up just fine. Which makes sense, But doesn't... ya know.
Edit 3: So I went to go unlock the bootloader on 1.58 and I'm on the "Unlock Bootloader?" screen, But I can't select yes, I know the dang power button works, I've pressed it 20 times, held it, it wont recognize, I also tried the camera button, don't work
I just tried to select no, and guess what, it'll work for that
Anyone ever seen this?
I unlocked it successfully like, 2 hours ago, with no effort at all. What. The. Hell.
Edit 4: Alright even though it wouldn't go through and reboot when hitting yes, and I even hit no to reboot it, I pulled the battery and went into the bootloader and it's unlocked.
So I wrote a recovery, I'm gonna make a back up of the stock rooted rom and see what we can't figure out here.
Okay, So it'll boot a custom rom on the 1.58 hboot. And I've made a backup of the stock rooted rom, I'm gonna try and flash the 1.04 again, and if it bootloops i'm gonna try and restore the backup of the stock rooted rom from the 1.58 hboot (Will that be a problem)
OKAY! Flashed the 1.04 hboot over Common-Sense (Thanks Turtle) and it finally booted up, Time to flash some jb goodness and hope we've got success.
Can't_Live_Without_My_Evo said:
Isn't that one GB?
Edit: After a ruu and a run through set up, I unchecked fastboot and checked usb debugging and then flashed the 1.50.5050 and it also bootloops.
What. The. Hell.
The only thing that'll boot up is stock.
Edit 2: So after the RUU I flash the 1.50.5050 you suggested, Bootloop as above stated, So I take out the sd and put the 1.58 stock hboot on it and flash that and it boots back up just fine. Which makes sense, But doesn't... ya know.
Click to expand...
Click to collapse
Sorry, I didn't realize that you were still on the stock ROM. As you found out, the only hboots that will boot that is 1.58 and JBear 1.58.5858.
The JBear 1.50.5050 hboot is a customized version of the latest Sprint GB bootloader and should boot everything that the engineering (ENG) 1.04 hboot does. I prefer to use that over the ENG version for day-to-day stuff since it's partition configuration is closer to the stock 1.58 hboot.
ramjet73
ramjet73 said:
Sorry, I didn't realize that you were still on the stock ROM. As you found out, the only hboots that will boot that is 1.58 and JBear 1.58.5858.
The JBear 1.50.5050 hboot is a customized version of the latest Sprint GB bootloader and should boot everything that the engineering (ENG) 1.04 hboot does. I prefer to use that over the ENG version for day-to-day stuff since it's partition configuration is closer to the stock 1.58 hboot.
ramjet73
Click to expand...
Click to collapse
I've got it working now, But I still don't understand the problem.
Everything worked fine except changing hboots.
The first time I flashed the hboot and then the rom without booting into anything and it boot looped, And I know 1.04 and JB work together.
The way I fixed it doesn't make sense to me either, But I'm not complaining about that.
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
I just rooted my EVO 3D via HTC Dev method and then obtained S-OFF with the JuopunutBear "wire trick." I followed this guide by ramjet73 to do this. I then flashed the ENG 1.04 HBoot obtained from here using ramjet's instructions here.
I then proceeded to wipe all partitions (including cache and dalvik) and restore my CM v10.1 "Wild For the Night" backup from 4EXT which I'd made on a previous EVO 3D with the same exact config (had to send in for replacement, working on the new refurb now).
That threw me in a boot loop. So I said, ok fine, wiped everything again and did an advanced restore of just boot, system and data. Same thing. So I once again wiped everything and loaded a fresh install of the ROM from a .zip in my SD. Still loop booting.
Seeing as it is late and I am very tired I gave up and loaded the JBear 1.58 HBoot and restored a stock ICS ROM backup I had also made from my previous phone. This seems to be working fine.
Anyone got any ideas why I can't get Wild For the Night going with the ENG 1.04 HBoot? It worked before....
kriz225 said:
I just rooted my EVO 3D via HTC Dev method and then obtained S-OFF with the JuopunutBear "wire trick." I followed this guide by ramjet73 to do this. I then flashed the ENG 1.04 HBoot obtained from here using ramjet's instructions here.
I then proceeded to wipe all partitions (including cache and dalvik) and restore my CM v10.1 "Wild For the Night" backup from 4EXT which I'd made on a previous EVO 3D with the same exact config (had to send in for replacement, working on the new refurb now).
That threw me in a boot loop. So I said, ok fine, wiped everything again and did an advanced restore of just boot, system and data. Same thing. So I once again wiped everything and loaded a fresh install of the ROM from a .zip in my SD. Still loop booting.
Seeing as it is late and I am very tired I gave up and loaded the JBear 1.58 HBoot and restored a stock ICS ROM backup I had also made from my previous phone. This seems to be working fine.
Anyone got any ideas why I can't get Wild For the Night going with the ENG 1.04 HBoot? It worked before....
Click to expand...
Click to collapse
something similar happened to me sometime ago .. jbear hboot is the reason . downgrade ur hboot to 1.49.0007 u will find many ways to do that on the forum , but since u r soff its very easy less than 1 mega file PG86.. flash via bootloader ..u r done , this hboot has the least compatibility problem with all rom~kernel combo ..
Just to clarify
ahmadalraii said:
something similar happened to me sometime ago .. jbear hboot is the reason . downgrade ur hboot to 1.49.0007 u will find many ways to do that on the forum , but since u r soff its very easy less than 1 mega file PG86.. flash via bootloader ..u r done , this hboot has the least compatibility problem with all rom~kernel combo ..
Click to expand...
Click to collapse
I think you misunderstood my post. I was at the ENG 1.04 Hboot when I was having these issues. I know that the JBear Hboot doesn't work with JB ROMs.
When I had my phone at the ENG 1.04 Hboot and I restored my Wild For the Night backup, or even re-loaded the ROM, my phone got stuck in a loop boot. I had the same exact configuration (same unlock method, S-OFF, same hboot, same recovery) on my previous phone, the one I made the backup from, and it worked just fine.
Also, after running my phone for a bit on the stock ROM with the 1.58 JBear Hboot SU doesn't work, neither does my WiFi or 4G. This was all working before the root and worked fine on the phone I did the stock backup from before.... I'm at a loss here
kriz225 said:
I think you misunderstood my post. I was at the ENG 1.04 Hboot when I was having these issues. I know that the JBear Hboot doesn't work with JB ROMs.
When I had my phone at the ENG 1.04 Hboot and I restored my Wild For the Night backup, or even re-loaded the ROM, my phone got stuck in a loop boot. I had the same exact configuration (same unlock method, S-OFF, same hboot, same recovery) on my previous phone, the one I made the backup from, and it worked just fine.
Also, after running my phone for a bit on the stock ROM with the 1.58 JBear Hboot SU doesn't work, neither does my WiFi or 4G. This was all working before the root and worked fine on the phone I did the stock backup from before.... I'm at a loss here
Click to expand...
Click to collapse
Sounds like kernal issues
Are you sure you're wiping boot before flashing?
Sent from my HTCEVOV4G using xda app-developers app
Yeah, I'm using 4EXT and I've used the "Wipe All Partitions (except for SD)." I've also individually gone and used all the other wipe options (except for SD) including cache and dalvik just to be 200% sure it's wiping everything.
I agree, I've seen that happen before when the kernel isn't wiped properly but I don't see why it wouldn't be... Unless the S-OFF didn't work properly? It says I'm S-OFF though, and I was able to flash the hboots...
you are right i did misunderstand you .. however u have already tried every thing just try this believe me it could work downgrade to hboot 1.49.0007 ..
if u need i will upload you the hboot if u didnt find it nut there are many ways in the forum..
and anyway its always better to be on this particular hboot as i mentioned before..
here is what i used i up;oad it for you
http://www.4shared.com/zip/qQzm0Rji/PG86IMG.html
i guess u know how to deal with it
by the way i just remembered something ... u use to use 4ext before with smart flash on , do u remember they asked u if u r Son and u said yes .. reflash 4ext and verify u r soff.. but still downgrade to hboot 1.49
@op
Don't do this^^^^^^ or you might brick your phone.
I don't know why wild for the night is not working on eng hboot but I guess you messed up your wimax partition by restoring nandroid from previous backup of another 3d. So 4g is not working. Now to fix things just use a ruu without relocking. You will not lose soff. Then start over by flashing custom recovery/hboot.
ahmadalraii said:
by the way i just remembered something ... u use to use 4ext before with smart flash on , do u remember they asked u if u r Son and u said yes .. reflash 4ext and verify u r soff.. but still downgrade to hboot 1.49
Click to expand...
Click to collapse
You know, now that you say that that could be it... I did flash 4EXT when I was S-ON so I might've answered yes to that question. I'll run RUU like the poster above suggested and then reflash 4EXT as S-OFF and see if that helps.
Thanks for the assist guys, this is driving me nuts.
downgrade ur hboot to 1.49.0007
花、不凋落っ said:
downgrade ur hboot to 1.49.0007
Click to expand...
Click to collapse
He clearly has a CDMA phone. That hboot is for gsm
I have wild for the night installed on my phone
Hi,
I know that this hboot using these instructions will work for wild for the night: unlimited. io /jbhboots. htm
also, how did you S-OFF? Did you follow unlimited's website, including running the commands on ubuntu 12.04 or later?
Best of luck!:fingers-crossed: