Hey,
I'm lost in the process of freeing my HTC Sensation. I bought it used and it's T-Mobile branded (cidnum: T-MOB101) and came with hboot 1.18.0000 and some 2.3 firmware.
After revolutionary did not work, I unlocked the bootloader with htcdev.com/bootloader. The installation of some "ClockworkMod Recovery v5.8.0.9" (with touch enabled) via "fastboot flash recovery" worked flawlessly.
I tried flashing several ICS images, to get one of it booting and saw bootloops and the phone being stuck. The CyanogenMod 9 nightly finally booted, after manually flashing the boot.img from the zip file with "fastboot flash boot". The setup wizard is shown after boot but freezes when tapping to select the language or to continue. After some seconds, the phone reboots and behaves like before (freezes, reboots).
With flashing SuperSU from CWM Recovery I got root.
Since in the thread for the CyanogenMod 9 nightlies it's stated, that the latest firmware (3.32) is required, I will have to update to an unlocked (S-OFF) hboot and current radio image, I presume. But how is this possible? I could not get it to work with
* a PG58IMG.zip (for cidnum: T-MOB101) on sdcard and booting into the bootloader,
* "fastboot flash hboot $path" (or "fastboot flash radio $path"),
* "flash_image hboot $path" (from booted CM9).
Step 4 in this guide did not work, because I get no confirmation to update. The bootloader just unpacks, parses end returns to the menu.
Changing the cidnum with "fastboot oem writecid 11111111" did not work.
Does somebody know, how to navigate out of this labyrinth?
Thanks in advance!
henning
phects said:
Hey,
I'm lost in the process of freeing my HTC Sensation. I bought it used and it's T-Mobile branded (cidnum: T-MOB101) and came with hboot 1.18.0000 and some 2.3 firmware.
After revolutionary did not work, I unlocked the bootloader with htcdev.com/bootloader. The installation of some "ClockworkMod Recovery v5.8.0.9" (with touch enabled) via "fastboot flash recovery" worked flawlessly.
I tried flashing several ICS images, to get one of it booting and saw bootloops and the phone being stuck. The CyanogenMod 9 nightly finally booted, after manually flashing the boot.img from the zip file with "fastboot flash boot". The setup wizard is shown after boot but freezes when tapping to select the language or to continue. After some seconds, the phone reboots and behaves like before (freezes, reboots).
With flashing SuperSU from CWM Recovery I got root.
Since in the thread for the CyanogenMod 9 nightlies it's stated, that the latest firmware (3.32) is required, I will have to update to an unlocked (S-OFF) hboot and current radio image, I presume. But how is this possible? I could not get it to work with
* a PG58IMG.zip (for cidnum: T-MOB101) on sdcard and booting into the bootloader,
* "fastboot flash hboot $path" (or "fastboot flash radio $path"),
* "flash_image hboot $path" (from booted CM9).
Step 4 in this guide did not work, because I get no confirmation to update. The bootloader just unpacks, parses end returns to the menu.
Changing the cidnum with "fastboot oem writecid 11111111" did not work.
Does somebody know, how to navigate out of this labyrinth?
Thanks in advance!
henning
Click to expand...
Click to collapse
You need to S Off first to be able to flash boot.
Go to the tool in my signature. Check your PMs.
kgs1992 said:
You need to S Off first to be able to flash boot.
Go to the tool in my signature. Check your PMs.
Click to expand...
Click to collapse
Looks like this only works on Windows. Sorry, forgot to say, I'm on Linux. I will try to understand what you did there and transfer it to Linux.
Thanks!
Related
Tried to root and unlock HTC Rezound from 2.3.4 and then flash CounterShrike 2.3 following the Unlockr instructions. Seemed to be going well until it bootlooped at the cyanogen mod screen.
When I connect the phone to the PC and start adb, it only sees the phone in fastboot. What's my best course of action?
Try to flash the kernel off an SD card out of hboot?
Wipe the Countershrike ROM and try to flash the stock ICS?
I've followed the instructions from the developers forum to relock via fastboot, but since I can't access the phone with the adb devices command, I'm hesitant to proceed. Any advice?
Thanks.
Forgot to post the info about the phone from the Fastboot screen:
***Relocked***
Vigor PVT SHIP S-ON RL
HBOOT- 2.11.0000
RADIO- 0.95.00.118r/0.95.00.1223r
OpenDSP- v.10.6.0.7611.00.0919
eMMC-boot
Oct 6 2011, 15:43:22
purchased the phone of eBay. It was on 2.3.4, so I did a factory reset and was trying to get it rooted and on ICS before activating it.
STEP 2:
Opened command prompt from my platform tools & tried to flash AmonRa recovery via fastboot ("fastboot boot rezound-recovery.img") but received an error message:
downloading 'boot.img'...
OKAY [ 1.49s]
booting...
FAILED <remote:not allowed>
finished.total time 1.525s
can you post the link to the instructions you followed?
instructions followed
The original set of instructions I followed to root & unlock the phone were @ Unlockr.
I'm currently running through NilsP's protocol:
Latest RUU Leak and Installation Instructions
NOTE: This is only needed if you want the latest ICS Firmware (Good Idea)
Quote:
Download the 4.03.605.2 Global RUU: >> Here. MD5 = bcdd450501e390ce323a46b396cd0a49
Rename the RUU to "PH98IMG.zip". Just remove everything in the name before the PH
Copy the renamed ipdate to the root of your external SD Card.
Re-lock the bootloader. Skip this if S-OFF
Open a DOS prompt and change directory to the folder where you have fastboot.exe
Reboot to bootloader
Type "fastboot oem lock" (No Quotes) while you are in bootloader (fastboot usb).
Reboot to bootloader again via recovery menu.
The bootloader should find the PH98IMG.zip file and scan it.
Scanning will take awhile so be patient. When it prompts you say yes. The update will make the first pass. This will take awhile so just watch the progress bar on the right The phone will reboot and sit on the white HTC screen. This could be awhile so be patient and don't get nervous. When it is done it will reboot back to bootloader to run the second pass of the install. Again, this will take some time so just watch the progress bar and OK's on the list. When it is done it will say "press power to reboot" so do it. Now it will boot into the leaked Update.
Once booted skip everything in setup. If you plan to run it stock then just get it set up to your liking
Install Amon Ra recovery version 3.15 (My Preference) If hboot will show tampered at the top but that is normal
Flash my ROM using the instructions in post 1
It's alive running stock...phwew! since I bought it for my wife to replace her DINC that's acting up.:highfive:
Your issue earlier was that you were on gingerbread firmware trying to run an ICS rom. Updating to the newest RUU updated you to ICS firmware.
Sent from my GT-P1010 using Tapatalk 2
[FIX] & [DOWNGRADE HBOOT] - Stupid Bootloop with HBOOT 1.58 EVO 3D - UPDATED 1-7-13
My friend's phone had the annoying bootloop problem. I'm posting this because after a lot of searching, I found nothing to fix the bootloop, just people asking about it. Here's a simply fix.
BOOTLOOP FIX:
If you already tried unlocking/ and you're still S-On, then set everything back to stock:
Flash the attached stock recovery,
fastboot oem lock to be locked again.
Use the latest RUU to update the phone.
At this point the stock, locked phone should function normally.
I have busted this phone a ton of times trying to get different recoveries and roms to work, and this method has always fixed the bootloop.
At this point you can try whatever tutorial you like to downgrade or customize the phone...and if it breaks, hopefully this method will still work for you. If it doesn't work the first time, try running the RUU a second time. Or third.
CUSTOM RECOVERY:
If you want to unlock and install custom stuff:
Use the HTC Dev unlock method.
Fastboot install CWM Recovery v5.8.0.1 from their website -
The ONLY recovery that I've found to be compatible with HBOOT 1.58 is CWM v5.8.0.1. Everything else leaves the phone in an infinite bootloop. Maybe others have had different experiences.
To fastboot install the CWM recovery, rename the file to recovery.img (for simplicity) and type in a command prompt (same directory as fastboot and recovery.img):
fastboot flash recovery recovery.img
Then, to enter into recovery, either pull the battery and enter recovery through the bootloader menu, or type in:
fastboot boot recovery.img
This should get you into the working CWM recovery. If it doesn't, it's because HTC hates people that buy their phones.
If you feel like giving up and running stock, all you need to do is reflash the stock recovery, and relock the phone using fastboot oem lock - and now it should run the stock rom...and if it doesn't, then rerun the RUU. Tedious.
HBOOT Downgrade & S-Off:
If you have: Stock 2.89 RUU / Locked / S-On
Unlocked with HTC Dev method
Flash CWM 5.8.0.1 from the CWM website:
fastboot flash recovery recovery.img - then
fastboot boot recovery.img (to enter recovery)
Flash the SetMainVersionLOW.zip file attached (thanks ramjet73)
Relock the phone with: fastboot oem lock
Use the Unknownforce/closeone hboot downgrade with live CD using the 2.89 RUU's rom.zip (from windows temp folder) renamed to PG86IMG.zip - go to the Unknownforce/closeone thread for this part: http://forum.xda-developers.com/showthread.php?t=1563342
Then flash the standard 1.13 RUU on your windows system (may also work with the PG86IMG.zip method, have not tested)
Then use revolutionary 0.4pre4 to S-Off
Finally, you need to flash a custom recovery which you can do from revolutionary, or from fastboot as listed above. Once the recovery is installed, you should be able to install a compatible custom rom and kernel.
You bootloader screen should now say REVOLUTIONARY on top instead of UNLOCKED or RELOCKED etc... and show HBOOT 1.40.1100.
Thanks to Unkownforce, closeone, and ramjet73 for making this possible.
PS. Screw up your phone at your own risk.
In case anybody was wondering, the RUU I've been using is the latest one at the time of this post: RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe
If by "reset s-on" you mean to switch s-off to s-on using the "write secureflag 3" command, then there is no need to do that., you can directly run RUU.exe on S-OFF and any recovery (hboot needs to be one of the stock versions I guess, I dont know for sure).
And I dont know if theres any relation with hboot version and recovery but TWRP and 4ext recovery works for every hboot. And if you are s-on, you dont always have to flash boot.img seperately using fastboot if you turn smartflash on.
mnomaanw said:
If by "reset s-on" you mean to switch s-off to s-on using the "write secureflag 3" command, then there is no need to do that., you can directly run RUU.exe on S-OFF and any recovery (hboot needs to one of the stock versions, I dont know for sure).
And I dont know if theres any relation with hboot version and recovery but TWRP and 4ext recovery works for every hboot. And if you are s-on, you dont always have to flash boot.img seperately using fastboot if you turn smartflash on.
Click to expand...
Click to collapse
Yeah, don't ever do the write secure flag command. That's bad news. Running a ruu will not s- on, and you're better staying s-off
Sent from my PG86100 using xda app-developers app
Reset s-on, and
fastboot oem lock to be locked again.
Click to expand...
Click to collapse
As others have mentioned, this is completely unnecessary. Once you're s-off htc's unlock is a non-issue and you can run any RUU you wish to at any time.
I know of no reason whatsoever where someone would need to set S-ON once it's off.
xHausx said:
As others have mentioned, this is completely unnecessary. Once you're s-off htc's unlock is a non-issue and you can run any RUU you wish to at any time.
I know of no reason whatsoever where someone would need to set S-ON once it's off.
Click to expand...
Click to collapse
@xHausX
Totally agree. The only reason to set S-ON once S-OFF is achieved is to return to 100% stock for warranty service or to sell the phone.
Nice to see you in these parts again and Happy New Year!
@joshdv
The CWM recovery version (6.0.1.4) you attached to the OP gives an error about accessing mmcblk0p34 when used with the engineering (ENG) bootloader, which a lot of Evo 3D users have installed to run GB or AOSP based ROM's. The current version of TWRP2 (2.3.3.0) has a similar error about the misc partition and I don't know if those errors will affect anything else or not. Apparently those errors are caused by variations in the emmc partition layouts with different bootloaders.
I prefer to use 4EXT which doesn't show any errors once cache+dalvik are formatted.
ramjet73
I updated the OP. I read somewhere else that it was necessary, this phone was never S-Off, so I wasn't sure.
Thanks
Everytime i run the ruu for my 3d it will finish as it has completed and boot. But whenever i remove my battery to switch it with a secondary, i used to do this before bed every night, i get a bootloop and cant boot untill i boot into bootloader and select the recovery option which wipes the phone and boots untill then next time i remove the battery. Why wont the RUU fix this? ive ran it multiple times. And also whenever im in the stock recovery and i select factory reset or any of the options i get "invalid option" "sucess rebooting by reason oem-00" what does this mean!?! can this be my sd? cause i cant mount cache recovery command or mount anything in recovery for that matter. if i need an sd ill buy one. just dont wanna find out its not my sd. and ive run the RUU about 7 times in total and nothing helps. thanks
ramjet73 said:
@joshdv
The CWM recovery version (6.0.1.4) you attached to the OP gives an error about accessing mmcblk0p34 when used with the engineering (ENG) bootloader, which a lot of Evo 3D users have installed to run GB or AOSP based ROM's. The current version of TWRP2 (2.3.3.0) has a similar error about the misc partition and I don't know if those errors will affect anything else or not. Apparently those errors are caused by variations in the emmc partition layouts with different bootloaders.
I prefer to use 4EXT which doesn't show any errors once cache+dalvik are formatted.
ramjet73
Click to expand...
Click to collapse
Yeah, I put WIP because it still never worked right, it was just the only one that ever actually loaded. I still hate this phone, I wish HTC was as nice as Samsung. It's so easy to work with Samsung, I always get mad trying to work around HTC's crippling B.S. Still better than Motorola though.
bootloop in my Htc Evo 3D hboot 1.53.007
How do you flash the stock recovery?
jcthelight said:
How do you flash the stock recovery?
Click to expand...
Click to collapse
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
joshdv said:
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
Click to expand...
Click to collapse
i have hboot 1.53 with s-on stuck on bootloop and i did as u said i flashed stocked recovery from temp folder from ruu-ics-35-ara.exe still my phone is in boot loop. Even i tried oem lock and run ruu.exe file upto 65% process goes fine then suddenly shows 100% process complete and reboot device(still stuck on bootloop).... plz give me suggestion to get rid of this thing.....
"RUU_SHOOTER_U_ICS_35_S_HTC_ARA_3.28.415.2_Radio_11.77.3504.00U_11.25.3504.06_M_release_264795_signed.exe"
joshdv said:
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
Click to expand...
Click to collapse
I'm a little confused. I've never rooted this phone so it's completely stock. My phone keeps powercycling. When I type in "fastboot flash recovery recovery.img" my cmd prompt tells me FAILED (remote: signature verify fail).
Any suggestions?
Re: [FIX] & [DOWNGRADE HBOOT] - Stupid Bootloop with HBOOT 1.58 EVO 3D - UPDATED 1-7-
Dang it! Why does it seem like developers have quit developing fully functioning roms for this phone? I live in a good 4g area so those roms without it are out of the question for me. And the others are having major issues with cameras, video playing, text messaging that keep it from being a daily....
And after using jellybean these ICS roms feel very incomplete even though they're more functional. I know you developers are busy people but please, can ICS get freshened up. Or just ignore me if y'all think the camera/text thing will be resolved very soon.
Sent from my PG86100 using xda premium
i cleared everything and i have 2 different roms on the sd but when i install one i get htc boot logo i can get into recovery and hboot which is 1.50 by the way so what do i do? i have no backup and im just confused?
Since you are s-on, you need to make sure you're flashing the kernel separately. Most people have good luck using 4ext with its Smart Flash option.
You have likely hosed up the boot partition/kernel preventing 4ext's Smartflash feature from working. If u enter your recovery via fastboot command prompt you should be able to flash normally and get the rom's kernel to load.
The HTC Unlock/hboot 1.5x Guide (my signature) should help.
Sent from my "Up all night, Sleep all day" EVO3D!
mpgrimm2 said:
You have likely hosed up the boot partition/kernel preventing 4ext's Smartflash feature from working. If u enter your recovery via fastboot command prompt you should be able to flash normally and get the rom's kernel to load.
The HTC Unlock/hboot 1.5x Guide (my signature) should help.
Sent from my "Up all night, Sleep all day" EVO3D!
Click to expand...
Click to collapse
what does that mean and how do i do that?
larikeal said:
what does that mean and how do i do that?
Click to expand...
Click to collapse
It means put your phone in "fastboot usb" mode and from the directory on your PC that contains adb and fastboot issue the following command:
fastboot boot recovery.img
The "recovery.img" parameter is the file name of whatever custom recovery you flashed to root.
After the phone boots up in recovery, just make sure SmartFlash (S-ON) is disabled in the tools menu if you are using 4EXT, then flash the ROM the same way you normally would. This method of starting recovery allows you to flash the boot partition (kernel) from recovery even though you are S-ON.
If you need more information than that, look at the links in the mpgrimm2's signature.
ramjet73
ramjet73 said:
It means put your phone in "fastboot usb" mode and from the directory on your PC that contains adb and fastboot issue the following command:
fastboot boot recovery.img
The "recovery.img" parameter is the file name of whatever custom recovery you flashed to root.
After the phone boots up in recovery, just make sure SmartFlash (S-ON) is disabled in the tools menu if you are using 4EXT, then flash the ROM the same way you normally would. This method of starting recovery allows you to flash the boot partition (kernel) from recovery even though you are S-ON.
If you need more information than that, look at the links in the mpgrimm2's signature.
ramjet73
Click to expand...
Click to collapse
guys same problem here hboot 1.53 S-on and im sure this is the rite rom for my model : RUU_SHOOTER_U_ICS_35_S_HTC_ARA_3.28.415.2_Radio_11.77.3504.00U_11.25.3504.06_M_release_264795_signed.exe
but i can complete the process upto 65% flash goes normal then suddenly shows up 100% process complete still stuck on bootloop and i can't able to find the rom anywhere and i donno whether there is problem with rom or phone.
phone status: ***relocked***, s-on, hboot 1.53 RL
any suggestion pls.................
mobileplazza said:
phone status: ***relocked***, s-on, hboot 1.53 RL
any suggestion pls.................
Click to expand...
Click to collapse
You can't flash with a relocked bootloader. Since the phone is S-ON you need to htcdev unlock the bootloader again after flashing the RUU, then install a custom recovery and you should be able to flash successfully or restore a previous nandroid backup.
ramjet73
It's not clear to me, but it almost sounds like MobilePLazza's problem is that he can't flash the full RUU to get back to stock and not sure if he even has the correct RUU.
Same outcome as the OP, but different problem. Perhaps he will clarify.
mpgrimm2 said:
It's not clear to me, but it almost sounds like MobilePLazza's problem is that he can't flash the full RUU to get back to stock and not sure if he even has the correct RUU.
Same outcome as the OP, but different problem. Perhaps he will clarify.
Click to expand...
Click to collapse
ok this is the issure phone is in bootloop now...............i relocked and flashed stock rom (ruu) as i said process 65% goes normal then suddenly shows 100% process complete but still phone in bootloop and im sure nothing is changed in my phone....but i can goto bootloader and even i can unlock phone again.....and i can run fastboot commands ....phone still in s-on.....
@ramjet : even if i flash custom rom after unlocking still my s-on is there to block and its not letting me to process it (no backup is taken b4 im so stupid here)
plz help me to solve this problem i just want this phone to run normally
It looks like you are on a GSM version of the 3d but the process is the same as the Sprint CDMA version we have, just different files (have to trust u on having the right Ruu, recovery, & Rooted Rom files).
Did u put the phone into "fastboot USB" mode, connect to pc and run the Ruu.exe from Windows OS when u did it?
As Ramjet73 was suggesting...
After u unlock the bootloader, are you able to use fastboot commands to flash a recovery.img? ie..
fastboot flash YourRecoveryFileName.img (to install recovery)
Then
fastboot boot YourRecoveryFilename.img (to boot the custom recovery)
Then flash a Rooted Rom from your sdcard with the recovery and reboot.
* keep in mind that you must enter the recovery via the above "fastboot boot.." command prompt every time you want to flash a Rom/kernel with S-on or you will bootloop because the kernel never gets loaded *
Sent from my "Up all night, Sleep all day" EVO3D!
Alright, I might as well post in this semi-fresh topic. I tried to change roms tonight and got stuck in a boot loop. It loads the HTC white screen, starts a little past that and then resets. I've tried wiping my data, and both caches. I've made sure SmartFlash is enabled on 4EXT because I'm S-On. I've tried it with SmartFlash disabled, too. I tried fastboot boot recovery.img to install my rom and my kernel. I can't seem to get out of this loop. Any advice?
Glee, please state your full phone/carrier /specs / recovery/rom if you want help. If you are CDMA/Sprint, I suggest you read through the HTC Unlock/Hboot 1.5x Guide (in my signature), specifically the linked post about flashing Roms/kernels via Fastboot/Recovery. Then you will be better prepared to explain what you've done so far.
Sent from my "Up all night, sleep all day" HP CM9 Touchpad
Hello,
I have a US 3G Flyer that my friend messed up while trying to root and reflash it. He asked me to revive it.
The device was stuck at the HTC logo during boot.
It must have had HC since the HBOOT is 1.11.0011. It was unlocked through HTCDev since it says UNLOCKED in the bootloader. However, it still has S-ON. The device has Revolutionary CWM 4.0.1.4 flashed as a recovery.
I tried to follow the instructions by globatron in http://forum.xda-developers.com/showthread.php?p=18508210 to downgrade to GB in order to run Revolutionary and get S-OFF.
fastboot getvar cid gives HTC__102
However, I do not have permission to read the thread that has the download links to the RRU: http://forum.xda-developers.com/showthread.php?t=1062184
So I went ahead and tried to flash DextersJB18 because it seemed from the thread http://forum.xda-developers.com/showthread.php?t=1795342 that some people flashed it sucessfully with HTCDev unlocked S-ON devices.
I downloaded the ROM zip file and gapps-jb-20121212-signed.zip, put that on the SD card, booted into CWM v4 and flashed this way:
1. Wipe factory data/reset
2. Wipe cache
3. Go into mounts and storage
4. Format /system
5. Format /data
6. Format /cache
7. Enter advanced
8. Wipe dalvik
9. Flash ROM (including wipe all) then flashed gapps
10. Booted to fastboot then "fastboot flash boot boot.img" (taken from DextersJB18.zip)
After I reboot, it never goes past the HTC logo. If I hold the power key, it shutdowns but reboots immediately. I know I go to the bootloader and say power off to prevent draining the battery.
Can someone please provide some insight into how I can get the device up and running again? Thanks. I really appreciate it.
Resolved
Well after another day of trying various things I finally got the device back up and running.
I figured out that for the HTC__102 model device I could use RUU_Flyer_HTC_WWE_2.00.405.3_R_Radio_20.3501.30.089BU_3809.05.04.10_M_release_194964_signed.exe to downgrade to Gingerbread. I googled that and found it on a random site.
After I found the correct RUU, I was able to follow globatron's instructions in http://forum.xda-developers.com/showthread.php?p=18508210 to downgrade to stock Gingerbread. The device booted OK into Gingerbread.
I then got S-OFF with Revolutionary and upgraded to Honeycomb by running ARUWizard.exe in RUU_3G_B09.zip. The device then booted OK into Honeycomb.
I then flashed DextersJB18 and gapps-jb-20120726-signed.zip from CWM recovery. Initially I had weird issues like the keyboard crashing because I used gapps-jb-20121011-signed.zip, which is ONLY for Android Jelly Bean 4.1.2, not 4.1.1. After flashing the correct gapps, things were OK.
The device now boots into Jelly Bean! Yea!
help, cant get boot or recovery
Hi hope you can help.
I have been running my flyer rooted on stock honeycomb with no trouble. I wanted to install Dexters JB18 rom, something went wrong after the install and now i can only access hboot screens, flyer wont boot, and recovery (was cwm with no issues) just brings up htc screen with nothing else.
I have tried flashing several recovery/boot images via fastboot, without any noticable effect. I get the messages saying image is written okay from command prompt but rebooting device or attempting to enter recovery just brings me white htc screen.
I have run getvar cid and got the result htc001, but attempting to reboot using adb gives the result device not found.
this is the info on the hboot screen
****unlocked****
flyer pvt ship s-on
hboot-1.11.0011
microp-0950
radio-3822.10.08.07_m
emmc-boot
A few threads here look promising, but i cant access them to be sure or find the right links, such as finding RUU type etc altho I dont think Im that far along until i can flash and get in to a workable recovery?
---------- Post added at 12:32 PM ---------- Previous post was at 12:14 PM ----------
Hi hope you can help.
I have been running my flyer rooted on stock honeycomb with no trouble. I wanted to install Dexters JB18 rom, something went wrong after the install and now i can only access hboot screens, flyer wont boot, and recovery (was cwm with no issues) just brings up htc screen with nothing else.
I have tried flashing several recovery/boot images via fastboot, without any noticable effect. I get the messages saying image is written okay from command prompt but rebooting device or attempting to enter recovery just brings me white htc screen.
I have run getvar cid and got the result htc001, but attempting to reboot using adb gives the result device not found.
this is the info on the hboot screen
****unlocked****
flyer pvt ship s-on
hboot-1.11.0011
microp-0950
radio-3822.10.08.07_m
emmc-boot
A few threads here look promising, but i cant access them to be sure or find the right links, such as finding RUU type etc altho I dont think Im that far along until i can flash and get in to a workable recovery?
adb driver?
ok, i think my issue is with adb.
with flyer in hboot so options are
fastboot
recovery
factory reset
clear storage
simlock
image crc
when i check device manager, it is listed as ADB interface, expand that and you get 'bootloader interface'
put flyer in fastboot mode, i see
bootloader
reboot reboot bootloader
power down
and the device is gone from device manager completely.
in either mode, when in adb running command 'adb devices' i get nothing, although running commands such as 'fastboot flash boot boot.img/recovery.img i get a success message after writing. 'fastboot reboot' will successfully reboot the device but it still does not boot up or enter recovery when attempted.
am i missing an adb driver or something?
Jelly Bean 1.8 No Wifi
I did the Same like you.
The device now boots into Jelly Bean! But i dont have wirless connection. It searches for wifi but dont find nothing.What should i do?
Where to download DextersJB18?
Hi, right now it's impossible to download DextersJB18 from dev-host, do you know any mirror link? Or kindly upload your saved ROM to other cloud storage? Thanks!
Better late than never...
I have been looking for dexterjb for a while now, thought I would search for it tonight and voila! There it is at
hmm, can't post external links. I could have sworn I was able to before...
?fid=746163614322263502 after androidfilehost.com/
I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.
I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
doctajay said:
I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.
I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
Click to expand...
Click to collapse
You need to unlock again in order to flash back a custom recovery. You also need to have the stock splash screen before you ruu. Had the exact same issue you had. Stock h-boot, stock splash screen and relock and all should be good.
That is my main problem. All of the unlock methods require me to load load an apk to change the CID. I can't do that in fastboot. Is there another unlock method I'm missing that allows you to do it from the fast boot mode?
Sent from my LG-D800 using Tapatalk
if u have your original unlock code from htc dev I think u can fastboot flash that code to unlock again. its in the forum somewhere just not sure where it is.
try this thread, good luck
http://forum.xda-developers.com/showthread.php?t=2160677
You don't have to run a apk to change the cid just Google change cid commands, you do it through adb change it to 22222222 then redo the HTC dev to get your unlock.bin again if u don't have it.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
doctajay said:
I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.
I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
Click to expand...
Click to collapse
You device most likely can't downgrade due to having a locked device. Have you tried flashing the 2.07 ruu
Thank you for all of the replies. Actually the change of the CID command might have worked but I didn't see that reply before I had tried another method found in this thread: http://forum.xda-developers.com/showthread.php?t=2570548.
I was truly stuck in fastboot and couldn't flash a custom recovery at all. Well I used the advice from a previous thread and edited the firmware .zip posted in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=2314771. I had initially tried to flash the .zip posted but when I tried to boot into the recovery it wouldn't work. So I opened the .zip file without extracting it and removed the recovery.img from the .zip, I then took the TWRP custom recovery and inserted it into the .zip (if you extract the zip this will not work; you need to use software that can edit a zip without extracting it. On the Mac, which I was using, I used Spring). I renamed the TWRP recovery to "recovery.img" to match what I had previously deleted.
Then I flashed this edited firmware.zip by using the following command in usb fastboot mode (here's the link for my edited file):
fastboot oem rebootRUU
fastboot flash zip YOUREDITEDFILE.zip
fastboot reboot
This then allowed me to boot into recovery. I thought I had figured it out and could now sideload a ROM using the "adb sideload" command and flash some type of ROM that would boot. This failed miserably; it would allow me to push the file, but the install would always fail before it completed.
So then I found this thread here: http://forum.xda-developers.com/showthread.php?t=2570548. I first flashed the two .zip files that were posted in post #44. then I flashed the full RUU posted in post #1. This gave me a bootable stock ROM. Praise God!!!
Finally I went back to this thread: http://forum.xda-developers.com/showthread.php?t=2293919, and flashed the following code.
Code:
adb devices (your device should be listed)
adb reboot bootloader
fastboot devices (your device should be listed)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
Not sure why I had such a terrible time, but I'm glad its over and the DNA is finally sold. Thank you for all your help!
trying to restore my dna back to stock
I got my dna locked again and now I am running the ruu file and i am stuck at 6%. Can someone help please!! Tried it by double clicking the ruu file and running it like that, and i also ran it in administration and both ways i am stuck at 6%