My 16gb HTC Flyer was running the OTA HC load and I decided to upgrade to a Jelly Bean ROM. After loading CWM (Flyer_CWM-Based_Recovery_6.0.1.1_HC.zip) recovery successfully, I loaded the NexusFlyer v1.2 ROM on the SD card and rebooted into CWM and did wipe data/factory partition and wiped the cache. Then I installed the new ROM and it rebooted.... to a never ending black screen. I had to load cwm-4.0.1.4-flyer.img just for the power off option, so I could shut it off.
Here is info on my Flyer:
HBOOT 1.11.0011
Radio 3822.10.00.07-M
Can anyone point me toward my best bet to get my flyer back up and running? Everything I'm finding is asking for specific version of HBOOT like 1.11.0003 for revolutionary load. At this point, I'd be happy just getting Honeycomb back, but ICS/JB would be better obviously.
Any help would be appreciated!
Sounds like you are not s off. Run your hc ruu of flash a hc ROM like virtuous that does not use a custom kernel
Flyer
mcord11758 said:
Sounds like you are not s off. Run your hc ruu of flash a hc ROM like virtuous that does not use a custom kernel
Flyer
Click to expand...
Click to collapse
You are correct, it is still S-ON. I assumed (wrongly...) that I wouldn't need it, as I've burned several ROMs on my Evo 3D with S-ON. Looking as downgrading to GB to get 1.11.0003, so I can use revolutionary to get S-OFF.
Thank you!
Well, so far, i'm failing...
I followed the steps at: Downgrade from HC beta leaks or official HC OTA to Gingerbread. and the RUU install fails saying "Unknown error: 155" I'm back into my boot loader, but otherwise it doesn't look like I can update via the RUU that I chose (RUU_Flyer_BrightstarUS_WWE_1.36.1540.32_R_Radio_20.3501.30.089BU_3809.05.04.10_M_release_191425_signed.exe).
Can I install any rom.zip files with S-ON or can I only update via RUU?
Thanks for any advice!
Other than update via RUU to an older HBOOT (older than 1.11.0011)... can I S-OFF any other ways (other than Revolutionary)?
Got past the part above by relocking HTC bootloader and the RUU loaded just fine. Then I ran revolutionary and it seemed to install fine with S-OFF. Afterwards, I installed CWM 4 and tried to burn nexusflyer v1.2 again only to get stuck at the white HTC screen on boot. I did find some stuff online about pushing boot.img from nexus flyer directly through fastboot, so I went ahead with that. No change...
I reran the RUU and am now back on a stock GB rom and am stuck with a seemingly non-upgradeable tablet.
any ideas why I'd get stuck at the white HTC screen after installing rom via CWM?
You need to be on honey comb to flash this rom
Flyer
mcord11758 said:
You need to be on honey comb to flash this rom
Flyer
Click to expand...
Click to collapse
Any particular HC ROM? Since I have successfully run Revolutionary, i should be able to just burn any HC rom, right?
You need honey comb hboot first
http://forum.xda-developers.com/showthread.php?t=1358758
Then you solo be soff honey comb and can flash freely
Flyer
To flash any HC, ICS or JB custom ROMs, you need to be on the HC hboot.
To flash any GB custom ROM, you need to be on the GB hboot.
Also, if you are S-On, you need to extract boot.img from the ROM file, then flash it via fastboot. But sounds like you are S-Off now.
Ok, I was under the impression that if I used the revolutionary utility to gain S-OFF (while also replacing the OEM HBOOT) that I'd be able to flash any rom.
Here is what I've done so far:
1. started with OEM HC with 1.11.0011 hboot
2. unlocked bootloader using HTCDevs.com
3. Used GB RUU to downgrade to 1.11.0000, to flash revolutionary.
4. Ran revolutionary, which replaced hboot with 6.10.1002 and loaded CWM 4.
So, understanding that I need to be using a HC rom to get to Jelly bean, will this replace my hboot or do I need to be S-ON again? I'm not really sure where to go from here, as I've tried flashing a HC rom and keep going back to a black screen. I thought I needed to be at S-OFF to get it to work, but have I headed down the wrong path?
I will try the post you suggested, mcord11758 and will report back.
I appreciate all the help.
Follow the procedure from the link i last posted
Flyer
Sure, enough. Following the post above worked like a champ. Thank you for all the help!
Related
Hi,
i have some problems with my HCT Flyer (O2 branded german version):
The OTA update to HC failed, so I was only able to get into the fastboot mode any more and the device was relocked (** Security warning ** ** relocked **).
I was able to unlock (via HTC unlock code) and flash the CWM recovery and flash the Leedroid GB ROM onto it, but got a boot-loop (several fails, missing files, and so on seen via ddms). I think the main problem is the radio and HBOOT-version (11.1.0006).
So I tried to flash the Leedroid HC ROM and this one finally boots correctly, but has several Problems (no WLAN, no 3G, no working HW buttons, and so on).
Also I think the radio and hboot versions are still the main problems.
As I'm still S-ON, I'm not able to flash the older radio and hboot files.
The (correct) RUU also don't work properly (Failure 150).
The actual situation:
*** UNLOCKED ***
FLYER PVT SHIP S-ON RL
HBOOT-1.11.0006
MICROP-0950
RADIO-3821.08.00.26_M
eMMC-boot
Aug 29 2011, 13:32:02
So I have a somehow working Leedoid HC on it, I'm able to boot android, connecting via ADB, getting into fastboot and CWM-recovery.
But I'm stuck on getting S-OFF to flash radio/hboot from the RUU.
Any idea how I can do that?
Main aim is getting a working GB, nevertheless if its the stock-rom or a custom rom like Leedroid.
Would be deeply grateful for any assistance in solving that problem.
Kind regards.
In addition I also tryed setting up a goldcard, but had no success with that.
Any other ways known to get it S-OFF?
Oder any other ways to downgrade radio and hboot to the stock-version?
Would be glad if somebody could give me a hint.
Thanks in advance.
to get lee droid hc to boot copy the boot.img from the rom zip. then fastboot flash the boot img and then flash the rom. should work.
to get s off I think you would need to downgrade to gingerbread then use globatrons method to gain hc s off.
mcord11758 said:
to get lee droid hc to boot copy the boot.img from the rom zip. then fastboot flash the boot img and then flash the rom. should work.
Click to expand...
Click to collapse
Leedroid HC does boot without problems, but has several problems (no HW buttons, no WLAN, no 3G, ...). Furthermore I can't switch it off. All the time I shut it down, it rebootes and is running several seconds later. Shutting down is only possibel via the CWM recovery.
to get s off I think you would need to downgrade to gingerbread then use globatrons method to gain hc s off.
Click to expand...
Click to collapse
Downgrading to gingerbread would be nice, but I didn't manage to do so.
I even would prefer staying on gingerbread...
Leedroid GB does not boot (bootloop, several files missing, several fails in DDMS).
And running the RUU leads to Failure 150. I think the newer radio/hboot are the source of all the failures.
But for replacing the hboot/radio by a older one I need to gain s-off ....
Flyer4Flyer said:
Leedroid HC does boot without problems, but has several problems (no HW buttons, no WLAN, no 3G, ...). Furthermore I can't switch it off. All the time I shut it down, it rebootes and is running several seconds later. Shutting down is only possibel via the CWM recovery.
Downgrading to gingerbread would be nice, but I didn't manage to do so.
I even would prefer staying on gingerbread...
Leedroid GB does not boot (bootloop, several files missing, several fails in DDMS).
And running the RUU leads to Failure 150. I think the newer radio/hboot are the source of all the failures.
But for replacing the hboot/radio by a older one I need to gain s-off ....
Click to expand...
Click to collapse
You need to Fastboot flash the boot img for Lees ROM
Sent from my HTC Flyer P510e using xda premium
mcord11758 said:
You need to Fastboot flash the boot img for Lees ROM
Sent from my HTC Flyer P510e using xda premium
Click to expand...
Click to collapse
Ok, I did so, but wasnt able to boot Leedroid anymore after that. Just got the white screen with green "htc" on it.
But how can it be, that the boot.img is required if the lee ROM comes with an own kernel?
Also flashing the kernel that comes with the lee ROM wasnt possible anymore after fastboot flash the boot_signed.img. But via NANDBACKUP I was able to restore it.
So any further idea to get Leedroid GB running?
Or gain S-OFF with my setting?
I may be confused as to you're actual current state. Are you running honeycomb or gingerbread? If honeycomb you can not flash gingerbread roms, and vice versa
Sent from my HTC Flyer P510e using xda premium
mcord11758 said:
I may be confused as to you're actual current state. Are you running honeycomb or gingerbread? If honeycomb you can not flash gingerbread roms, and vice versa
Click to expand...
Click to collapse
That might be the main part of the Problem.
I really cant tell you, I think I'm somewhere in between.
I was running stock gingerbread, s-on and locked - just out of the box.
Then an OTA update to honeycomb was started and failed and left the device (soft-)bricked. Only flashboot was accessible any more. Android didn't boot, turning on automaticly leads to flashboot, starting recovery/factory reset just leads to a reboot into flashboot.
In this state I was able to unlock (via HTC dev utility) and flash CWM recovery to be able to flash zip files. But I was not able to flash hboot, radio, system and so on.
I first tried Leedroid GB wich leads to a bootloop.
Then I flashed Leedroid HC, wich boots, but is not working propperly. (no WLAN, no 3G, no HW-buttons, and so on).
So I think there are incompatible radio and/or hboot on it as the OTA update failed somewhere in the middle.
But as I'm still S-ON, I cant flash all parts of the RUU (GB).
And just running RUU also don't work, as the radio/hboot seem to be newer then the version of the RUU.
And also the HowTo of globatron with "misc_version_universal" (http://forum.xda-developers.com/showthread.php?t=1307759) did not work. (RUU shows the changed version number, but fails nevertheless).
Relock boot loader before attempting ruu
Sent from my HTC Flyer P510e using xda premium
mcord11758 said:
Relock boot loader before attempting ruu
Click to expand...
Click to collapse
THAT was the missing hint!
Thank you so much.
After relocking the bootloader the goldcard worked and installed the stock ROM without any problem. Now ist working again!
Thanks for your great help!
Flyer4Flyer said:
THAT was the missing hint!
Thank you so much.
After relocking the bootloader the goldcard worked and installed the stock ROM without any problem. Now ist working again!
Thanks for your great help!
Click to expand...
Click to collapse
hey, I am a noob, have my flayer exactly like ur status u mentioned b4 HB 1.11.0006
it is stuck on that rom, HC, which have no Phone ability also.
Is it possible that you give me step by step guidance. i am worried if I attempt doing what u said above vaguely I would brick it. actually a friend of mine had the exact situation and got it bricked and had to change the main board.
So I hate sounding noobish but my experience from the incredible is much less complex than what I've done with this phone, anywho...
I currently am on the stock hboot from the most recent GB RUU.
I was wondering... Seeing as how I have been trying to switch to some ICS roms, specifically venusaur, which hboot should I switch to?
I looked at superchilpil's post and didn't really get info that I wanted from it. So should I switch to the leaked ICS hboot or should I use the Jbear hboot?
Also the jbear hboot is the one prepacked in the controlbear files correct?
I am s-off obviously and have rooted stock GB rom.
Use the jbear hboot. You will be able to flash kernels in fastboot if you do.
I know flashing the ICS jbear boot will make my sd mount points screwy. So should I install the GB jbear boot and still be able to install ICS roms?
you will be able to flash ICS roms as long as you flash the GB firmware patch that devs have somewhere in their threads
Now what all would be different about flashing the the newest leak's ph img? Obviously hboot/radios/rom but Is it beneficial to do so?
bukithd said:
I know flashing the ICS jbear boot will make my sd mount points screwy. So should I install the GB jbear boot and still be able to install ICS roms?
Click to expand...
Click to collapse
Flash the latest .4 ics jbear hboot and you'll be fine. I flashed yesterday and everything is fine with my phone
Sent From My Ice Covered ReZound
I tried exactly that yesterday and my sd mounting got screwy as in my sd basically became invisible to my phone.
EDIT: I got what I wanted, I flashed the newest leak zip in hboot and just rerooted stuff.
Like the title its good to upgrade to honeycomb official VIA OTA update idmf my phone condition now is 2.3.4 stock rooted& s- off?
Sent from my HTC Flyer P510e using XDA
no you will soft brick not be able to boot and will have a s off gb hboot with a HC system.
you can either research how to downgrade to a non s off hboot then take the ota or you can upgrade to hc using the easy s off hc thread in development
personally keepig s off will give you an easy route back and forth between hc and gb in case you do not like hc.
mcord11758 said:
no you will soft brick not be able to boot and will have a s off gb hboot with a HC system.
you can either research how to downgrade to a non s off hboot then take the ota or you can upgrade to hc using the easy s off hc thread in development
personally keepig s off will give you an easy route back and forth between hc and gb in case you do not like hc.
Click to expand...
Click to collapse
So i must s-on again to take every OTA official by HTC?..
Soft brick do u mean i still have a hboot or not? And its easy to recoverable or have a chance to hardbrick?..
Now if im in gingerbread i want install honeycomb by leedroid its just install zip from recovery?
Sorry im very newbie in tablet specially for HTC system: )
Thx for the answer
Sent from my HTC Flyer P510e using XDA
I was new to HTC devices with my Flyer and I can say as always there is no substitute to reading
ok. why does an OTA cause a soft brick? When you s off you replace the stock Hboot with a patched one that allows you to flash custom recovery and root. If you are on a s off GB set up and you run a RUU for stock GB if you go into hboot you will see you are still s off. The Hboot will not allow itself to be over written. Now if you OTA you find yourself in the same position. The ota if it runs at all will re write your system and recovery as well as radio but will not be able to over write the s off hboot. This will lead to a system that does not boot and worse yet a system that will not likely charge. If you run out of charge you will be in real trouble as the Flyer will not charge when plugged in. Others have managed to take thier Flyer appart and charge the battery seperated from their Flyer (got to love non removable batteries )
If in this state the simple sollution is to flash a gb ruu which should get you back up an running, provided you have enough charge in your battery
now if your goal is to try Lee Droid's HC rom here is your best approach. Since you are already s off GB you are at a good starting point. Down load the rom from lee's thread but do not flash yet. Look in the development section for globatron's easy s off hc thread. Download the light package which will change your hboot to s off hc. follow instructions to flash this package through fastboot. once this is done get into recovery and flash lee droid. you should be fine.
If you ever want to go back to GB post 3 of the same thread has a downgrade package you can flash in fastboot. This again is just the hboot, recovery, and radio and will not boot on its own. After flash of this you will need to either run a GB RUU or flash a GB Rom.
These 2 light packages are an easy portal back and forth between gb and hc. if you make a nandroid back up of both gb and hc you can restore after you flash to the correct base
Sprint decided to update my Evo 3D, now i'm on
SHOOTER XC SHIP S-OFF RL
HBOOT 1.58.0000
is there anything I can do?
What is your final goal? You are s-off, so you can run any hboot you want. If you want to run GB or AOSP, you can downgrade your hboot to 1.4 using a PG86IMG.zip file. If you want to run an ICS Sense ROM, you can stick with hboot 1.58.
Hey guys, since I received the OTA update I cannot flash my roms on my SD card. I'm somewhat of an amateur so i'm not entirely sure what i've been doing exactly but its always worked, I am S-off Hboot 1.58 LOCKED. I have tried setting up 4ext but I get an error and busy box doesnt seem to think my phone is rooted, I used to load roms by using recovery and i believe revolutionary, Now when I go into recovery i get the HTC style error message with the phone and an exclamation. What can I do to fix this. The ICS rom runs fine but I would like to load in the new ICS mean rom. Any help would be appreciated!
yanmared said:
Hey guys, since I received the OTA update I cannot flash my roms on my SD card. I'm somewhat of an amateur so i'm not entirely sure what i've been doing exactly but its always worked, I am S-off Hboot 1.58 LOCKED. I have tried setting up 4ext but I get an error and busy box doesnt seem to think my phone is rooted, I used to load roms by using recovery and i believe revolutionary, Now when I go into recovery i get the HTC style error message with the phone and an exclamation. What can I do to fix this. The ICS rom runs fine but I would like to load in the new ICS mean rom. Any help would be appreciated!
Click to expand...
Click to collapse
Never take an OTA if you are rooted!!
Now that that is out of the way, it sounds like the OTA removed your custom recovery. Have you tried to flash a new recovery? Download the 4ext img file from this site and use fastboot to push it to recovery on your phone. Then you should be able to flash MeanROM.
coal686 said:
Never take an OTA if you are rooted!!
Now that that is out of the way, it sounds like the OTA removed your custom recovery. Have you tried to flash a new recovery? Download the 4ext img file from this site and use fastboot to push it to recovery on your phone. Then you should be able to flash MeanROM.
Click to expand...
Click to collapse
I have not tried that yet. This update really threw me for a loop. Kind of separating the men from the boys at this point lol. I will go ahead and try to flash that over hopefully I can find a DIY type thread on it
ooooook...this'll either get me killed or contented.
here goes.
the first part of this i basically stole from sullivan's post over at mik's.
there was no answer to his question...
there are too many guides, tutorials and suggested methods that I can't chose the right one to narrow it down...
i'm asking the same manner of question...
<<<<<
EVO 3d
sprint
-Revolutionary-
SHOOTER XC SHIP S-OFF RL
HBOOT 1.40.1100
RADIO-1.06.00.1216
eMMC-boot
Jun 8 2011,17:20:22
hardware 002
running smooth criminal (chose a random sense rom to update pri.prl)
kernel version is 3.0.50-ck1 butteredtoast ics rls 12.2+
Build # is 2.89.651.2 CL409645 release-keys
PRI Version 1.42_003
PRL Version 21090
i used htc unlock and closeone's toolkit.
was using mikvirgin for a while. vm leak without problems. couldn't update pri.prl
changed a few things here and there...then, i started having heat and drain issues. notably from browsing and swype beta.
figured it was time for a clean slate and new rom.
From what I've gathered I need an ics hboot, ie, 1.58 in order to run ics kernels the right way??
What should i do to be current??
start by updating my radio. (where's the latest file?)
should i upgrade hboot? 1.58?
Do I need to relock, ruu, then unlock again? (what method is most recent and where)
i thought i read that i can just change my hboot on its own and then also bootload the latest radio?
ideally, i'd love to be able to run a few aosp jb roms...cm 10...as well as any ics roms without issue.
also, is the deal with ext3 versus ext4 still the same? ext4 can't run sense roms...or, was that only for the evo4g?
>>>>>>>>>>>>>
advice would be considered a thankable and appreciated offense!
many, many thanks, everyone.
i need to head to bed.
clear my brain a bit.
between ramjet's and mpgrimm2's threads...i'm going into overload.
but, thanks. seriously. you guys rock.
--------------------------------------------------------------
what? you think just cause a guy reads comics he can't kick some a$$?
I would relock the bootloader and run the Sprint ICS ruu.exe. This will update you to the latest firmware, radio, hboot, etc, but you'll still be s-off. Then downgrade your hboot to 1.4 or 1.04 and install a custom recovery like 4ext. You should then be ready to install a custom Rom.
coal686 said:
I would relock the bootloader and run the Sprint ICS ruu.exe. This will update you to the latest firmware, radio, hboot, etc, but you'll still be s-off. Then downgrade your hboot to 1.4 or 1.04 and install a custom recovery like 4ext. You should then be ready to install a custom Rom.
Click to expand...
Click to collapse
i'm thinking running the ruu might be the way to go, too.
(if anyone would like to point me in the direction of the latest ruu "how-to" thread...much appreciated)
however, i'm not quite sold on the idea of downgrading hboot back to what i have (or, another 1.4 variation).
as per ramjet's thread on the subject...even the most flexible hboot "eng hboot" has issues with compatibility running 2.89 based kernels.
the ones that run ics and above are the 1.58 hboots and it's variables.
so, anyone have ideas as to what my specs should be to successfully run a cm 10 based rom and kernel successfully?
not to mention that i'd like to continue to swap into a sense based rom every now and again.
that leads me back to the ext3 vs ext4 question.
is ext4 still not a viable ext for sense based roms or was that only for the evo 4g?
thanks again, coal!
cipher77 said:
i'm thinking running the ruu might be the way to go, too.
(if anyone would like to point me in the direction of the latest ruu "how-to" thread...much appreciated)
however, i'm not quite sold on the idea of downgrading hboot back to what i have (or, another 1.4 variation).
as per ramjet's thread on the subject...even the most flexible hboot "eng hboot" has issues with compatibility running 2.89 based kernels.
the ones that run ics and above are the 1.58 hboots and it's variables.
so, anyone have ideas as to what my specs should be to successfully run a cm 10 based rom and kernel successfully?
not to mention that i'd like to continue to swap into a sense based rom every now and again.
that leads me back to the ext3 vs ext4 question.
is ext4 still not a viable ext for sense based roms or was that only for the evo 4g?
thanks again, coal!
Click to expand...
Click to collapse
This post was for a user in a situation similar to yours. It's basically what coal suggested and you can use my guide through Step2, but there is no need to relock the bootloader since you are S-OFF.
If your case, you might want to flash the ENG or JBear 1.50.5050 bootloader after running the RUU.exe since both of those will flash and run GB, ICS and JB ROM's except for a few Sense ROM's that require the stock 1.58 or JBear 1.58.5858 bootloader.
As far as EXT3 versus EXT4 goes, most current Sense and AOSP ROM's support both, but I usually just "format all partitions except SD card" in 4EXT recovery before flashing a ROM and let it default to that (EXT4) or whatever format the dev configured for the ROM. I just checked the nandroids on my SD card and they are all in the EXT4 format.
ramjet73
IMO, you should just update your radio (if you can find the latest PG86IMG.zip) or get the one from virus's thread which contains the latest hboot too. Then to install CM10 ROM downgrade back to eng hboot or 1.4 you should be able to run CM10 ROMs just fine. And if you want sense 3.6 ROM, you can try smoothcriminal ROM after updating your radio. It works with all hboots.
RUU vs OTA vs firmware zip file
mnomaanw said:
IMO, you should just update your radio (if you can find the latest PG86IMG.zip) or get the one from virus's thread which contains the latest hboot too. Then to install CM10 ROM downgrade back to eng hboot or 1.4 you should be able to run CM10 ROMs just fine. And if you want sense 3.6 ROM, you can try smoothcriminal ROM after updating your radio. It works with all hboots.
Click to expand...
Click to collapse
There's some good information about flashing an RUU versus taking an OTA in this thread on the HTC Desire forum, and flashing the firmware zip updates even less than taking the OTA. I've attached screen shots of the contents of virus's firmware zip file versus the RUU rom.zip file from the same build (Sprint ICS 2.89.651.2). As you can see, even discounting the boot, system, and data partitions, there's more that gets updated with the RUU than what's contained in the firmware .zip, which is why I recommend starting with an RUU flash (.exe or .zip) when upgrading to a new build.
ramjet73
ramjet73 said:
There's some good information about flashing an RUU versus taking an OTA in this thread on the HTC Desire forum, and flashing the firmware zip updates even less than taking the OTA. I've attached screen shots of the contents of virus's firmware zip file versus the RUU rom.zip file from the same build (Sprint ICS 2.89.651.2). As you can see, even discounting the boot, system, and data partitions, there's more that gets updated with the RUU than what's contained in the firmware .zip, which is why I recommend starting with an RUU flash (.exe or .zip) when upgrading to a new build.
ramjet73
Click to expand...
Click to collapse
Although mnomaanw makes a great point, I agree with ramjet on this one. My phone recently decided not to let me install ANY CM, GB, or JB based ROMs. The only ones that would successfully boot were Sense 3.6 and 4.0 based ICS ROMs. The rest would show my splash screen and then the phone would bootloop before even the boot ani showed. I tried to flash different radios, hboots, firmware, etc to no avail. Finally, I ran the ruu.exe, downgraded my hboot to 1.4 Revolutionary to try the MIUI ROM everyone is raving about and installed 4ext custom recovery. Everything is running great now.
I can confirm that it does more than just the firmware zip updates as it wiped my custom splash screen I had installed. Going through the hassle of running the ruu is worth it if you want to be sure that everything is completely updated properly.
ramjet73 said:
This post was for a user in a situation similar to yours. It's basically what coal suggested and you can use my guide through Step2, but there is no need to relock the bootloader since you are S-OFF.
If your case, you might want to flash the ENG or JBear 1.50.5050 bootloader after running the RUU.exe since both of those will flash and run GB, ICS and JB ROM's except for a few Sense ROM's that require the stock 1.58 or JBear 1.58.5858 bootloader.
As far as EXT3 versus EXT4 goes, most current Sense and AOSP ROM's support both, but I usually just "format all partitions except SD card" in 4EXT recovery before flashing a ROM and let it default to that (EXT4) or whatever format the dev configured for the ROM. I just checked the nandroids on my SD card and they are all in the EXT4 format.
ramjet73
Click to expand...
Click to collapse
first off...
huge, huge thanks for the responses, guys.
so, yeah...i've actually been using 4ext as my recovery for a while now. i have to say...it's quite good.
however, i always have wondered what the deal was with ext3 vs ext4. clearing that up more definitively than what i've been able to find on my own, as well as my own experiences, is great.
sounds like i'll be running the ruu executable.
just to confirm...already being s-off means that i don't have to relock my bootloader, yeah?
excellent. one less step.
as for the hboot...this seems to be where it gets tricky.
ramjet...you suggested downgrading hboot after the ruu flash to ENG or 1.50.5050.
i'm definitely dumb to NOT take your advice...so, i will. more than likely the 1.50.5050 hboot. seems to be more likely to play well with 2.89 kernels. otherwise, i'd do the ENG hboot.
from your thread, you mention that the only ones that DO run 2.89 based kernels are stock (1.58) and jbear's (1.58.5858).
do you think ENG hboot will be pliable enough at any point to be compatible with them? THAT would be pretty great.
thanks again, gang.
--------------------------------------------------------------
what? you think just cause a guy reads comics he can't kick some a$$?
cipher77 said:
ramjet...you suggested downgrading hboot after the ruu flash to ENG or 1.50.5050.
i'm definitely dumb to NOT take your advice...so, i will. more than likely the 1.50.5050 hboot. seems to be more likely to play well with 2.89 kernels. otherwise, i'd do the ENG hboot.
from your thread, you mention that the only ones that DO run 2.89 based kernels are stock (1.58) and jbear's (1.58.5858).
do you think ENG hboot will be pliable enough at any point to be compatible with them? THAT would be pretty great.
Click to expand...
Click to collapse
Unfortunately, there is no hboot that will run all Evo 3D CDMA ROM's but there are only three ROM's that I know require 1.58 or JBear 1.58.5858 at this time and that's the Sprint ICS stock ROM, Cool ICS and Viper3D. Some ROM developers have incorporated the "VM leak" kernel in place of the stock Sprint ICS 2.89(.651.2) kernel just to avoid that requirement. The reason I'm recommending JBear GB (1.50.5050) or the engineering (ENG-1.04) bootloader at this point is that there are far more ROM's that can be flashed and run with those than the 1.58.x versions, and they both support the fastboot commands that would normally require an unlocked bootloader.
ramjet73
ramjet73 said:
Unfortunately, there is no hboot that will run all Evo 3D CDMA ROM's but there are only three ROM's that I know require 1.58 or JBear 1.58.5858 at this time and that's the Sprint ICS stock ROM, Cool ICS and Viper3D. Some ROM developers have incorporated the "VM leak" kernel in place of the stock Sprint ICS 2.89(.651.2) kernel just to avoid that requirement. The reason I'm recommending JBear GB (1.50.5050) or the engineering (ENG-1.04) bootloader at this point is that there are far more ROM's that can be flashed and run with those than the 1.58.x versions, and they both support the fastboot commands that would normally require an unlocked bootloader.
ramjet73
Click to expand...
Click to collapse
gotcha.
makes sense that devs would swap out the vm leak just to avoid the hassle.
thanks for the info, btw.
about to flash the ruu from your qaderso zip.
not having to relock before doing the flash is nice.
thanks again for all of your help.
i'll report back with success...or, hang ups.
update...
just wanted to check in.
i went ahead and ran the ruu.exe without any issues.
since i was already s-off and unlocked via htc...i didn't bother relocking.
once the ruu did its thing it changed the hboot to stock and the previous REVOLUTIONARY in the bootloader header disappeared and it just read UNLOCKED.
not sure if this was right...but, i didn't have to unlock again.
i stayed s-off AND unlocked after the ruu.
i re-ran the ruu later in the day since staying s-off and unlocked didn't sit well with me after the intial run. but, the result was the same.
so, i'm all good, i suppose.
any takers?
installed SU, reinstalled 4ext (had been using it successfully for a while now. great recovery.) and busybox.
then, something strange happened.
rather, something i didn't expect.
after changing the hboot to 1.50.5050 via bootloader...
as instructed...i powered down.
extracted the zip from the root so i wouldn't be in a bootloop.
but, it still wouldn't load the stock rom.
is that weird? or, expected?
i actually had to reinstall via recovery another sense rom.
otherwise, i think everything's going well.
waiting to get some time to flash a cm10 rom at this point.
unless someone thinks otherwise!
thanks again...
cipher77 said:
then, something strange happened.
rather, something i didn't expect.
after changing the hboot to 1.50.5050 via bootloader...
as instructed...i powered down.
extracted the zip from the root so i wouldn't be in a bootloop.
but, it still wouldn't load the stock rom.
is that weird? or, expected?
i actually had to reinstall via recovery another sense rom.
otherwise, i think everything's going well.
waiting to get some time to flash a cm10 rom at this point.
unless someone thinks otherwise!
thanks again...
Click to expand...
Click to collapse
That's normal. As a reminder, I'll quote from a post I made earlier in this thread:
ramjet73 said:
Unfortunately, there is no hboot that will run all Evo 3D CDMA ROM's but there are only three ROM's that I know require 1.58 or JBear 1.58.5858 at this time and that's the Sprint ICS stock ROM, Cool ICS and Viper3D.
Click to expand...
Click to collapse
The stock 2.89.651.2 ROM is in fact one of the few that currently require the 1.58 bootloader. That's why my guide recommends installing the JBear 1.58.5858 bootloader by default since the RUU installs the stock ICS ROM.
Also, the reason your bootloader shows unlocked is probably because you htcdev unlocked it before doing the hboot 1.4 downgrade for S-OFF. I've never done that method myself, but in discussing it with mpgrimm2, apparently the downgrade method doesn't reset the bootloader status to locked like the JupunutBear (wire trick) method does.
ramjet73
ramjet73 said:
That's normal. As a reminder, I'll quote from a post I made earlier in this thread:
The stock 2.89.651.2 ROM is in fact one of the few that currently require the 1.58 bootloader. That's why my guide recommends installing the JBear 1.58.5858 bootloader by default since the RUU installs the stock ICS ROM.
Also, the reason your bootloader shows unlocked is probably because you htcdev unlocked it before doing the hboot 1.4 downgrade for S-OFF. I've never done that method myself, but in discussing it with mpgrimm2, apparently the downgrade method doesn't reset the bootloader status to locked like the JupunutBear (wire trick) method does.
ramjet73
Click to expand...
Click to collapse
RE: hboot bootloop...doy! consider me FACEPALMED.
maybe, RAM-PALMED!
hell, i probably read over that line twenty times and never really READ it.
so, thanks again.
either way, since not many will stay on stock soft or stock hboot...i suppose it's not really an issue.
change hboot and change rom.
but, it did give me a scare for a minute.
as for the lock versus unlock...your guess is as good as, if not infinitely better, than mine.
everything definitely works, tho.
appreciate you seeing this through and checking in on me, btw.