Hello, so i posted a thread yesterday and got no help at all on this subject, but i have an Sprint HTC EVO 3D rooted with hboot1.5, i also have TWRP v2.2 installed as my recovery partition. Unfortunately i lost all back ups and my OS on the phone due to me being stupid and accepting an OTA update when not using stock recovery. So now i am left with a phone that just boots to the HTC screen, and i can boot into the recovery partition with no OS on the phone at all. Is there any way i can get the phone back on and functional or am i just screwd out of luck?I am a noop at android so please if you can help please provide an extensive explanation as possible, or give as much guidance if possible. I really need my phone back. I have a windows computer so i can not fastboot through linux, if you suggest that. Please and thank you if you can help!
Download a few sense ROMs to the sd card- I recommend one gingerbread and one ICS ROM (mean ROM or zr3d if you want my opinion). Go into twrp and wipe everything except sd card (I'm not sure exactly the command since I use 4ext). Then flash one of the ROMs and reboot. I suggest sense based since those seem to have the least issues. Try the ICS one first and if that still bootloops then try the GB one.
Save the Drama for your Mama with Tapatalk 2
yea just flash another ics rom. but if you flash the new sprint ota roms you need to update the hboot to the new 1.58 hboot. just make sure you check if your s-on or s-off unless you dont care about being s-off
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!
Ok, so my friend didn't go home when he was drunk. So he flashed a Sprint ROM on his AT&T HTC One.
The phone has Hboot 1.44 (Thank God)
I received the phone in these conditions:
Re-locked (Don't know why)
Only enters bootloader
Cannot enter recovery
Cannot boot the phone
Internal SD card was somehow corrupt
What I was able to do:
Unlock it with fastboot commands
Flash TWRP with HTC One Toolkit [M7] • 2.0!
Entered TWRP, wiped everything due to not being able to access the Sd card or boot.
What I'm TRYING to do:
Root the phone- Cannot push SU or even get the PC to recognize the mounted sd card in TWRP
Gain s-off to run the RUU and revert to full stock.
Any help will be appreciated!
HolloWX said:
Ok, so my friend didn't go home when he was drunk. So he flashed a Sprint ROM on his AT&T HTC One.
The phone has Hboot 1.44 (Thank God)
I received the phone in these conditions:
Re-locked (Don't know why)
Only enters bootloader
Cannot enter recovery
Cannot boot the phone
Internal SD card was somehow corrupt
What I was able to do:
Unlock it with fastboot commands
Flash TWRP with HTC One Toolkit [M7] • 2.0!
Entered TWRP, wiped everything due to not being able to access the Sd card or boot.
What I'm TRYING to do:
Root the phone- Cannot push SU or even get the PC to recognize the mounted sd card in TWRP
Gain s-off to run the RUU and revert to full stock.
Any help will be appreciated!
Click to expand...
Click to collapse
sprint uses different partitions your only course of action is to flash a ruu sinse you have 1.44 hboot this one should work
http://www.htc.com/us/support/news.aspx?p_id=628&p_name=htc-one-att
ok, will try. ty so much
Sent from the cold abyss...
jerrycoffman45 said:
sprint uses different partitions your only course of action is to flash a ruu sinse you have 1.44 hboot this one should work
http://www.htc.com/us/support/news.aspx?p_id=628&p_name=htc-one-att
Click to expand...
Click to collapse
Can I run that latest RUU and still keep the same bootloader version for S-OFF purposes?
HolloWX said:
Can I run that latest RUU and still keep the same bootloader version for S-OFF purposes?
Click to expand...
Click to collapse
flashing a ruu will not change s-off.you will get whatever hboot is in the ruu but since you are s-off you can downgrade if you want
http://forum.xda-developers.com/showthread.php?t=2316726
here's the link to get Revone s-off ->>http://forum.xda-developers.com/showthread.php?t=2314582
and here is the newest AT&T RUU ->> http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
istalled viper 2.0now my phone stickes on the htc screenim unlocked
hboot 1.73
ine got access still to custom recovery twrp its an att htc one x + and it was on 4.2 sense 5 before running viper any help would be appreciated
i just want to go back to 4.2 instead of esing with anything else this is way out of my range
denial4242 said:
istalled viper 2.0now my phone stickes on the htc screenim unlocked
hboot 1.73
ine got access still to custom recovery twrp its an att htc one x + and it was on 4.2 sense 5 before running viper any help would be appreciated
i just want to go back to 4.2 instead of esing with anything else this is way out of my range
Click to expand...
Click to collapse
Have you flashed the boot.img?
boot img
yes i did but then i tried to go back to stock just using the nandroid i made and when it stated to boot it got stock so then i tried to reinstall viper and boot loop again so i finally got viper back working by selckting to flash the boot img again in the viper software
i like the viper the viper rom but the only bad thing is its 4.1 and seense 4 other than that great rom hopefully there will be a 4.2 rom coming for the att htc one x+
Hi,
I'm in a bit of a pickle with my HTC Flyer 32gb 3g.
I unlocked the bootloader using the HTC DEV website and installed recovery. I did not make the device S-OFF nor does it have superuser on it.
The mistake I made was that I installed a custom ROM without S-OFF and superuser (it had honeycomb on it, I wanted to put jellybean on it). Of course the custom ROM did not want to boot (also tried flashing boot.img). I had made a backup of the original ROM in recovery but for some reason this backup can no longer be found on the SD card.
I am stuck with a device which won't boot past the green HTC logo and even though I am able to install custom ROMs they won't boot.
I can access bootloader and recovery and connect to my PC just fine.
Last known Android: 3.2
Hboot: 1.11.0011
Any help on getting back a functioning Android?