Related
So... I flashed scrosler's Stock Rooted RUU 3.14, and once that was cleanly on and working I got into amonra and cleared data, flashed Venasaur 3.1, and then in Hboot ran the 3.14 kernel again.
How did I go wrong and what's the simple fix that will get me with the pokemon? ~thanks <3
(I'm getting bootlooped that is)
You flashed an incompatible kernel. Are you s-on or s-off? If s-off just flash the Rom again in amon ra and reboot phone. No need to install a kernel it will do it for you. If s-on you need the kernel for venasaur Rom which may need to be flashed in fastboot unless someone has made it into a flammable zip. If s-on might as well take the plunge and s-off. It's a very easy process.
sent from my Clean Rezound
I am S-on, as soon as I find something condutable and more reliable than a paperclip i'll probably do S-off haha
I don't think anyway has, I just time getting the image boot file off of the rom and running it in H-boot, I still get a bootloop (I'm genuinely surprised that it didn't work), that's a pretty sticky situation, i'm stuck without a phone until that's solved =(
I repeal that statement, taking the boot.img out and flashing it in hboot worked, wonderful! thanks =)
Question for you?..
Now that that you have your Venusaur 3.1 running..are you having any issues with Wifi?
I did the re-lock, android police ruu, unlock, install recovery, clean wipe x10, install venusaur 3.1, and then installed sense4 boot image for the venusaur rom. However I keep getting Wi-fi Errors, I'm guessing my wifi modules are wrong but I'm just trying to figure out where I may have messed up. I tried flashing the wifi modules provided by http://forum.xda-developers.com/showthread.php?t=1642217 but no go...any ideas?
well i'm fairly curious how you were able to get the sense4 boot image, it gave me a mainver error, I took the boot image out of the rom and ran that.
Which got me in, and wifi isn't giving me a problem surprisingly, but I'm now curious to how your supposed to go 3g with the new setting setup.
My Sd card also can't mount I'm not sure if that's related to 3.14 and pokemon rom or just my terrible flashing
Watercycle, are you still having problems? If you flashed Scott's Rom that is not an ruu. I believe you are still o n the old firmware. You will need to go to nilsp business Rom in the development section and download the old firmware patch (i think it's in the 4th post) then flash in amon ra. You should be set after that.
sent from my Clean Rezound
actually I flashed scott's 3.14 deodex and old firmware patch + boot img before flashing the pokemon and pokemon boot img
I'm currently only struggling with the issue of sd card mount now
Watercycle said:
actually I flashed scott's 3.14 deodex and old firmware patch + boot img before flashing the pokemon and pokemon boot img
I'm currently only struggling with the issue of sd card mount now
Click to expand...
Click to collapse
The patch may still be on your sd card from Scott then and if not go to the thread I suggested. Just boot to recovery and flash the patch again. You will need that patch for any ics Rom you run because you are still on gb firmware. Don't panic your almost there.
sent from my Clean Rezound
how can you tell if your on old gb firmware? =( since it still boots up and works
darnit I thought i was on ics after that full ruu =o
so after having flashed the pokemon in Hboot i flash the old firmware again? (i'm scared it will bootloop me because i finally got it working haha)
ZombieCodeMonkey said:
Question for you?..
Now that that you have your Venusaur 3.1 running..are you having any issues with Wifi?
I did the re-lock, android police ruu, unlock, install recovery, clean wipe x10, install venusaur 3.1, and then installed sense4 boot image for the venusaur rom. However I keep getting Wi-fi Errors, I'm guessing my wifi modules are wrong but I'm just trying to figure out where I may have messed up. I tried flashing the wifi modules provided by http://forum.xda-developers.com/showthread.php?t=1642217 but no go...any ideas?
Click to expand...
Click to collapse
I briefly searched the venasaur thread (which you can do to) and found most people having WiFi issues either had the wrong kernel or just reset their router and bam, WiFi works. I can't help you anymore then that so you may want to ask in that thread.
Edit: did you unzip the Rom and get the boot.IMG there or did you download seperate? If you didn't unzip and take it out of the Rom then try that. You should be good.
sent from my Clean Rezound
What ruu did you use?
sent from my Clean Rezound
Give me like 20 minutes to get back to you...heading home....motorcycle can't multitask at night more obvious to others haha
Sent from my ADR6425LVW using Tapatalk 2
snow, since I sucsessfully was on
This
will flashing the old gingerbread fix my sd mounting or break everything?
sorry I have to be more direct, gotta get some sleep now =)
Watercycle said:
snow, since I sucsessfully was on
This
will flashing the old gingerbread fix my sd mounting or break everything?
sorry I have to be more direct, gotta get some sleep now =)
Click to expand...
Click to collapse
I think so
Watercycle said:
snow, since I sucsessfully was on
This
will flashing the old gingerbread fix my sd mounting or break everything?
sorry I have to be more direct, gotta get some sleep now =)
Click to expand...
Click to collapse
It will fix your sd card. You never ran the ruu if all you flashed was Scott's rooted, deodexd Rom. If you get with me tomorrow I can walk you through the ruu but I think at that point you might as well s-off. Time to find that wire
sent from my Clean Rezound
If you could see your sd card on Scott's Rom it was because of the patch. Make sure you report back. I need some sleep.
sent from my Clean Rezound
Okay...
I re-locked my bootloader using the usual, fastboot oem lock.
then I download the full leaked RUU from Android Police, androidpolice.com/2012/05/07/exclusive-download-htc-rezound-ice-cream-sandwich-build-3-14-605-5-brings-a-handful-of-fixes-and-newer-radios/"
Booted to Hboot with that file on the SD card in the proper name, completely flashed the phone with the Leaked RUU
Once OS loaded, rebooted back to fastboot and used hTcdev.com to unlocked my bootloader again. (I do not have S-Off yet).
Then I downloaded and flashed through fastboot commands the TWRP 2.1.1. Touchscreen recovery.
Once this was done, I downloaded and installed Venusaur 3.1.0 through recovery after performing scot's superwipe x10,
Then fastboot flashed the boot.img for the sense 4.0 roms.
Wi-Fi does not turn on at all...It will state Turning on...but not to long after will give error.
So after all of that I tried grabbing the wifi module.zip from one of the stock rom de-odexed rooted 3.14.605.5 roms, and tried flashing that through recovery and manually adding the file through root explorer..nothing.
Hope that helps clarify.
Also i would through an inquiry to there thread but I don't have enought posts yet to post in development.
ZombieCodeMonkey said:
Okay...
I re-locked my bootloader using the usual, fastboot oem lock.
then I download the full leaked RUU from Android Police, androidpolice.com/2012/05/07/exclusive-download-htc-rezound-ice-cream-sandwich-build-3-14-605-5-brings-a-handful-of-fixes-and-newer-radios/"
Booted to Hboot with that file on the SD card in the proper name, completely flashed the phone with the Leaked RUU
Once OS loaded, rebooted back to fastboot and used hTcdev.com to unlocked my bootloader again. (I do not have S-Off yet).
Then I downloaded and flashed through fastboot commands the TWRP 2.1.1. Touchscreen recovery.
Once this was done, I downloaded and installed Venusaur 3.1.0 through recovery after performing scot's superwipe x10,
Then fastboot flashed the boot.img for the sense 4.0 roms.
Wi-Fi does not turn on at all...It will state Turning on...but not to long after will give error.
So after all of that I tried grabbing the wifi module.zip from one of the stock rom de-odexed rooted 3.14.605.5 roms, and tried flashing that through recovery and manually adding the file through root explorer..nothing.
Hope that helps clarify.
Also i would through an inquiry to there thread but I don't have enought posts yet to post in development.
Click to expand...
Click to collapse
Why are you not s-off? Makes life much easier. What I have concluded is that you need to start over. You have the wrong kernel. Wipe everything then flash the Rom in recovery. You will have had to unzip the Rom on your pc then take the boot.IMG out and flash this in fastboot to the phone. I don't think there is a ph.zip file for this. There are very good directions if you search that thread.
sent from my Clean Rezound
Sorry guys but it's bed time. If you both follow those directions you should be fine. If not get with me in the morning.
sent from my Clean Rezound
Evo 3D HBOOT 1.5 lastest Spring Firmware never flashed VM firmware
Coming from MeanROM 4.3 GB Base, going to MeanROM ICS 1.9. I wiped data/cache/dalvik, ran modified superwipe, flashed ext4 recovery w/ smartflash on, then flashed the rom. Did everything I do on my other evo 3d but it kept rebooting right after boot when the home screen starts up just to have it reboot. I've tried wiping everything. Flashing rom + kernel through fastboot as well. I thought it was the ROM but it keeps doing it regardless or the ROM I flash. Including the one I was coming from.
Appreciate the help, thanks.
SlevinK said:
Evo 3D HBOOT 1.5 lastest Spring Firmware never flashed VM firmware
Coming from MeanROM 4.3 GB Base, going to MeanROM ICS 1.9. I wiped data/cache/dalvik, ran modified superwipe, flashed ext4 recovery w/ smartflash on, then flashed the rom. Did everything I do on my other evo 3d but it kept rebooting right after boot when the home screen starts up just to have it reboot. I've tried wiping everything. Flashing rom + kernel through fastboot as well. I thought it was the ROM but it keeps doing it regardless or the ROM I flash. Including the one I was coming from.
Appreciate the help, thanks.
Click to expand...
Click to collapse
So I assume your S-ON. I had the same problem the other day flashing an ICS rom. I'm S-ON and GSM.
Just kept on rebooting no matter what.
I think it has to do with not flashing the new radio/firmware, but not sure.
I just went back to the GB rom and its fine.
You should be able to go back to your old rom. If you can't then maybe your old rom .zip file got corrupted.
Yeah, I re-downloaded the first ROM I was using. I still don't see why it worked fine on one my evo and not on my other. both are cdma.
Edit:
Well it's working now, it doesn't seem to work with any ICS roms, anyone know what could be wrong? My other evo works just fine with ICS roms.
SlevinK said:
Evo 3D HBOOT 1.5 lastest Spring Firmware never flashed VM firmware
Coming from MeanROM 4.3 GB Base, going to MeanROM ICS 1.9. I wiped data/cache/dalvik, ran modified superwipe, flashed ext4 recovery w/ smartflash on, then flashed the rom. Did everything I do on my other evo 3d but it kept rebooting right after boot when the home screen starts up just to have it reboot. I've tried wiping everything. Flashing rom + kernel through fastboot as well. I thought it was the ROM but it keeps doing it regardless or the ROM I flash. Including the one I was coming from.
Appreciate the help, thanks.
Click to expand...
Click to collapse
You don't say whether you are S-Off or S-on. Hboot 1.5 S-on does not play well with ICS and usually bootloops.
Hboot 1.5 s-on
coal686 said:
You don't say whether you are S-Off or S-on. Hboot 1.5 S-on does not play well with ICS and usually bootloops.
Click to expand...
Click to collapse
Sorry, I thought people would understand it was S-ON due to it being 1.5. Is there a method to getting S-ON in 1.5? Both of my Evo's are HBOOT 1.5 S-ON. One of them worked fine without a problem, doesn't matter the ICS ROM. The other, the one I"m having a hard time with, does.
SlevinK said:
Sorry, I thought people would understand it was S-ON due to it being 1.5. Is there a method to getting S-ON in 1.5? Both of my Evo's are HBOOT 1.5 S-ON. One of them worked fine without a problem, doesn't matter the ICS ROM. The other, the one I"m having a hard time with, does.
Click to expand...
Click to collapse
You can get s-off on 1.5 if you follow this link.
http://forum.xda-developers.com/showthread.php?t=1585846
I still recommend trying to get 1.4 s-off as that seems to be the one that has the least amount of problems. You can find how to do that in the CDMA Development forum stickies.
Sent from my PG86100 using Tapatalk 2
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.
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: