Related
I tried flashing a new rom for my DS
on this forum:
update-saga-runnymede-s-v5.zip
unluckily
my phone just can turn on once, then it lagged for a long time.
i took out the battery and insert again. turn on again.
badly it lagged again. i repeated
then the third time it stucked at HTC white screen for about an hour
then i tried many times but failed
i try to updated the recovery
'updating recovery' <- this screen has been showing for mayb few hours ( i fell asleep while waiting, when i woke up it's out of battery. then i reboot again but in bootloader NO 'RECOVERY' option!
now my phone has this option but when i choose it it disappears!
so i couldn't flash new recovery through phone
HELP HELP I AM REALLY GETTING CRAZY OF THIS!
can anyone help?
Ok. It seems that your recovery is gone by some reason.
Since you are using adb, I suppose that you have fastboot command also.
Download this file, rename it to recovery.img. Reboot your phone to bootloader (vol down + power), connect it to PC. It should be "FASTBOOT USB" written on the screen. Then open command prompt and type:
Code:
fastboot flash recovery {path to the file}\recovery.img
It should take less than a second to flash it (if longer than you may have troubles with the eMMC chip). If ok reboot to recovery and flash a custom ROM.
If not OK, connect to PC again as described above and type:
Code:
fastboot getvar all
and post the output here.
firstly i haven't tried
Code:
fastboot getvar all
yet since i am still waiting for <waiting for device>
so mayb it has failed.
what should i do to end this and try another method?
close adb directly ?
here is the details when i try fastboot getover all
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\Users\Chris>fastboot getover all
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\Chris>
not getover, but getvar
copy the command from my post and paste it to your command prompt to avoid mistakes
EDIT: have you managed to flash the recovery?? the text in the brackets {} has to be replaced with the path to your file - e.g. C:\android
then the command will look like this:
fastboot flash recovery C:\android\recovery.img
sorry for that i missed the word
C:\Users\Chris>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6.98.1002
(bootloader) version-baseband: 3805.06.02.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.832.1
(bootloader) serialno: SH14MTJ01449
(bootloader) imei: 355067046266979
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__622
(bootloader) battery-status: good
(bootloader) battery-voltage: 3805mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
here's the result
is it possible that the chip fried while "all done"?
all seems ok. Have you managed to flash the recovery image. My previous post is updated, check it
sorry what do you mean your previous post? which is it?
cckwan said:
sorry what do you mean your previous post? which is it?
Click to expand...
Click to collapse
amidabuddha said:
EDIT: have you managed to flash the recovery??
Click to expand...
Click to collapse
the text in the brackets {} has to be replaced with the path to your file - e.g. C:\android
then the command will look like this:
fastboot flash recovery C:\android\recovery.img
oh now when i type
Code:
fastboot flash recovery C:\Users\Chris\Downloads\recovery.img
it shows:
Code:
sending 'recovery' <6000 kb>
OKAY [0.995s]
writing recovery...
then no continue action
staying here
what should i do the next?
Your next step is to go to the [GUIDE] Read this before going for eMMC replacement in my signature and follow point 4.1
Use this RUU
You will lose S-OFF and root, but eventually your phone will work again
how about my flash recovery still not yet complete...?
btw i am still trying to understand that post step 4.1
but i wanna know is it ok that recovery not yet finished?
4.1 If you have a 6.98.xxxx hboot
You probably already have the adb properly configured on your PC
Change your hboot with this one There are 3 ways:
i should download "this one" right? there are <Eng S-Off.rar> and <PG88IMG.zip> inside.
1) use the one click - it will flash it for you
what means by the 'one click"?
2) put PG88IMG.zip on your SDcard and rebot to bootloader. It will flash automatically. After flashing delete PG88IMG.zip from the SDcard
i can't see my sd card on PC, should i pull out the sd card to another phone and put in the files required then insert back to my phone ?
3) extract the image from PG88IMG.zip, rename it to hboot.img, connect the device to PC, reboot it to bootloader (it should be written "FASTBOOT USB" on the phone, open a command prompt on the PC and type:
sorry...
when i am installing ruu
error occurs: usb connection may lost
so wht can i do><
totally lost now
sorry... now i found i haven't flash hboot.img completely
as it showed: image update is bypassed!
so what should i do?
***updates***
i tried 'fastboot flash hboot G:\a1\hboot.img'
(tried:
http://forum.xda-developers.com/showthread.php?t=1236890
&
http://forum.xda-developers.com/showthread.php?t=1113820
then it showed
Code:
C:\Users\Chris>fastboot flash hboot G:\a1\hboot.img
sending 'hboot' (1024 KB)...
OKAY [ 0.201s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.029s]
finished. total time: 0.231s
---------------------------------------------------
cannot flash hboot to 0.98.2000 or what
----------------------------------------------------
i can see my serial no. on PC cmd by using 'fastboot devices'
but adb devices shows nothing
---------------------------------------------------
-Revolutionary-
SAGA PUT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO- 3805.06.02.03_M
eMMC-boot
Mar 10 2011, 14:58:38
---------------------------------------------------
WHEN I choose 'recovery' option on fastboot it blacked for 0.1s then fastboot screen again without 'recovery' option
---------------------------------------------------
sleep time now 2:15am here
thank you very much amidabuddha reli so much!
you have done a lot i know but i just need some more help getting my DS turn on again...or there will be a murder news here which parents killed their son sosad
thank you. hope you can reply me ASAP when you are convenient!
--------------------------------------------------
i tried tpbklake'sadvice to flash a cwm recovery but the cmd stayed at writing recovery...
cckwan said:
***updates***
i tried 'fastboot flash hboot G:\a1\hboot.img'
(tried:
http://forum.xda-developers.com/showthread.php?t=1236890
&
http://forum.xda-developers.com/showthread.php?t=1113820
then it showed
Code:
C:\Users\Chris>fastboot flash hboot G:\a1\hboot.img
sending 'hboot' (1024 KB)...
OKAY [ 0.201s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.029s]
finished. total time: 0.231s
---------------------------------------------------
cannot flash hboot to 0.98.2000 or what
----------------------------------------------------
i can see my serial no. on PC cmd by using 'fastboot devices'
but adb devices shows nothing
---------------------------------------------------
-Revolutionary-
SAGA PUT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO- 3805.06.02.03_M
eMMC-boot
Mar 10 2011, 14:58:38
---------------------------------------------------
WHEN I choose 'recovery' option on fastboot it blacked for 0.1s then fastboot screen again without 'recovery' option
---------------------------------------------------
sleep time now 2:15am here
thank you very much amidabuddha reli so much!
you have done a lot i know but i just need some more help getting my DS turn on again...or there will be a murder news here which parents killed their son sosad
thank you. hope you can reply me ASAP when you are convenient!
Click to expand...
Click to collapse
The Revolutionary HBOOT 6.98.1002 will not allow you to overwrite it. You can only overwrite it using a special version from Revolutionary/AlphaRevX for removing S-OFF and returning to S-ON. Search for Revolutionary return to S-ON.
sorry i am quite new in android
can u tell me how to find revolutionary?
i even dunno what type of file i should search
or can you give me the download link? please
tpbklake said:
The Revolutionary HBOOT 6.98.1002 will not allow you to overwrite it. You can only overwrite it using a special version from Revolutionary/AlphaRevX for removing S-OFF and returning to S-ON. Search for Revolutionary return to S-ON.
Click to expand...
Click to collapse
cckwan said:
sorry i am quite new in android
can u tell me how to find revolutionary?
i even dunno what type of file i should search
or can you give me the download link? please
Click to expand...
Click to collapse
Use the search function of this forum using the key word 'revolutionary s-on'
It should turn up a few threads that address the topic.
Welcome to VomerGuides: [M7 Edition]
Have an M8? There's a guide for that!
Hey folks!
Many of you will find this post similar to the ARHD posts I have made.
Based on several suggestions and PM's - I decided to make a separate thread in the hope that this will stop some repeated questions asked in multiple threads.
Following this guide will allow you to (in this sequence):
- Achieve S-OFF using revone
- Change your CID to SuperCID (allowing you to bypass regional ROM restrictions)
- Upgrade to the latest firmware (UL edition) without loosing any data on your SD card
- Install the latest TWRP recovery
Donations:
I do not believe that I should be charging for information sharing. However, having the physical hardware helps me improve this content and support you better as I do require hardware to test/work on for all my content and it's not always possible for me to find someone to borrow devices from.
If you would like to support my work donate to me via:
Thank you
Disclaimer & Copyrights:
I test everything before I share these guides - thus I know they work as intended. However, please proceed at your own risk as I do not take any liability for your devices.
Please do not copy contents of this guide without explicit permission from me. I like to maintain a set standard and quality of the information I share.
Please refrain from posting mirrors as I like to track downloads - I primarily use AndroidFileHost and they mirror files on multiple servers automatically.
I like to track downloads - so please use the official links provided in this guide.
Here is a mirror for all the files in case main links down:
- Firmwares
- Everything Else
Other useful files:
These files can be used to replace/add features in the latest firmware zips posted in this thread.
- Hboot v1.44: http://d-h.st/1zJ
- Touch panel Driver from firmware 2.24.401.1: http://d-h.st/lL4
- Flash-able Radio Collection: http://forum.xda-developers.com/showthread.php?t=2419699
- Going back to stock ROM: http://forum.xda-developers.com/showthread.php?t=2265618
Click to expand...
Click to collapse
Windows Users: It's a good idea to install the HTC drivers on your pc: http://d-h.st/4LL or use this toolkit to install the drivers.
READING & FOLLOWING EACH STEP IS KEY TO SUCCESS.
SECTION 0: SYSTEM PREPARATION:
First we need to get you ADB and fastboot
Windows Users, download this file and extract the folder called "adb" to your C: drive. Your path should look like this:
Code:
C:\adb\
Also, you will need to open a command prompt window using this method:
Code:
Go to the C:\adb\ folder - hold down SHIFT key and RIGHT-CLICK and select "Open command window here".
Mac/Linux users install ADB & fastboot using: Download
1. Extract the downloaded zip to your desktop
2. Open Terminal and type in:
Code:
su
cd Desktop/Android/ (note: Android is the directory extracted from zip file)
3. Now type
Code:
./ADB-Install-Mac.sh
Note: By using the method above, your adb and fastboot files are stored at this location on your Mac: /usr/bin/
SECTION 1: S-OFF & SUPERCID
Downloads Required:
- revone (hboot 1.44)
- rumrunner (hboot 1.5x)
Note: If you are running a 4.4 based ROM and do not want to downgrade to a lower version to use revone or rumrunner - try this tool to S-OFF
Note: revone (used for s-off) has been reported to work best with 4.2.2 roms. Please install a 4.2.2 ROM before attempting S-OFF.
Note: If you are using rumrunner - please follow the instructions to s-off provided on the rumrunner link above. Steps below are for revone only.
Note: Read these useful tips before attempting S-OFF
Mac/Linux users: Save this file to your Desktop
Windows users: Save this file to the C:/adb/ folder
Also, before continuing - make sure you have USB Debugging enabled on your phone (Settings -> Developer Options -> USB Debugging)
If you do not see "Developer Options", Go to Settings > About phone > Software > More > click on build number 10 times. This should enable that section.
Part 1
1. Push revone to your device:
Code:
Mac/Linux: adb push /Users/vomer/Desktop/revone /data/local/tmp/
Windows: adb push C:/adb/revone /data/local/tmp/
2. Open adb shell by writing:
Code:
adb shell
su
3. Write in the shell:
Code:
cd /data/local/tmp
4. Then write this:
Code:
chmod 755 revone
5. Next, write the following command:
Code:
./revone -P
6. Revone reported that I needed to reboot and try again. So I wrote :
Code:
reboot
[COLOR=Red][B]Note:[/B][/COLOR]
[B]Stuck with error: -1?[/B]
When initiating a reboot after "./revone -P" please press and hold the power button for 15 seconds.
To start the entire process from scratch please power off the device and wait 30 seconds, turn it on and continue to ."/revone -P".
7. Close your Command Prompt/Terminal window. Open it again and type:
Code:
adb shell
su
8. Write (to change directory in the phone):
Code:
cd /data/local/tmp
8a. Write the following command:
Code:
./revone -P (it will now say success and ask to reboot phone - do it by typing: reboot)
8b. Once rebooted - repeat steps 7 & 8
9. To get S-OFF & unlock, write the following command:
Code:
./revone -s 0 -u
10. revone will report success. Exit the shell:
Code:
exit (or just close terminal and open a new one)
11. Reboot into bootloader:
Code:
adb reboot bootloader
12. Check if the bootloader screen show's you as S-OFF (it should be in the in the first line under the "pink" highlighted text)
13. Reboot the phone
14. Start the adb shell, again:
Code:
adb shell
15. Change to the folder where revone is stored by typing:
Code:
cd /data/local/tmp
16. Request revone to reset tampered flag by typing:
Code:
./revone -t
17. Exit the adb shell by writing: exit (or just close terminal and open a new one)
18. Reboot to the bootloader by writing:
Code:
adb reboot bootloader
19. Phone should now be S-OFF and tampered flag should be gone
Now stay at this bootloader screen with your phone plugged in to the PC - and follow the steps in Part 2 below.
Part 2
Now lets get you SuperCID:
1. Open terminal/command prompt and type (copy paste command below or make sure there a eight 1's):
Code:
fastboot oem writecid 11111111
2. Reboot phone into bootloader mode (by typing: adb reboot bootloader) and verify CID#. It should look similar to this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SECTION 2: FIRMWARE UPGRADE
FIRMWARE FAQ:
Q: Do I need S-OFF for firmware flashing?
A: YES!
Q: Do I NEED to update my firmware?
A: NO! But doing so ensures optimal phone performance.
Q: Does it matter when I flash the firmware (before or after new ROM install)
A: NO!
Q: Will updating the firmware erase my SD card or Apps?
A: NO! The firmware files provided in this guide take care of this for you so none of those get erased.
Q: If I only flash the ROM, will I get updated to the latest firmware?
A: NO!
Q: Can I install a U edition firmware on a UL edition phone?
A: YES, but you might loose the ability to connect to LTE or have some other incompatibilities.
FIRMWARE FLASHING:
Firmware Downloads (SD card will not be wiped using these files):
4.2.2 Base Firmwares:
- 2.17.401.1: http://d-h.st/PJv (Rename to firmware.zip after downloading)
- 2.24.401.1: http://d-h.st/WO9 (Rename to firmware.zip after downloading)
- 2.24.401.8: http://d-h.st/qPT (Rename to firmware.zip after downloading) *LATEST*
4.3 Base Firmwares:
- 3.06.1700.10: http://d-h.st/maA (Rename to firmware.zip after downloading)
- 3.09.401.1: http://d-h.st/PSE (Rename to firmware.zip after downloading)
- 3.17.401.2: http://d-h.st/bgE (Rename to firmware.zip after downloading)
- 3.22.1540.1: http://d-h.st/LLO (Rename to firmware.zip after downloading)
- 3.57.401.500 : http://d-h.st/z6g (Rename to firmware.zip after downloading)
- 3.62.401.1 : http://d-h.st/in6 (Rename to firmware.zip after downloading) *LATEST*
4.4 Base
- 4.06.1540.2 (Rename to firmware.zip after downloading)
- 4.06.1540.3 (Rename to firmware.zip after downloading)
- 4.19.401.8 (Rename to firmware.zip after downloading)
- 4.19.401.9 (Rename to firmware.zip after downloading)
- 4.19.401.11 (Rename to firmware.zip after downloading)
- 5.11.1540.9 (Rename to firmware.zip after downloading)
- 5.11.401.10 (Rename to firmware.zip after downloading)
- 6.06.401.1 (Rename to firmware.zip after downloading)
- 6.09.401.5 (Rename to firmware.zip after downloading)
- 6.09.401.10 (Rename to firmware.zip after downloading) *LATEST*
-----
Windows users, you need to do these steps first:
- move the file you downloaded and renamed (firmware.zip) to the C:\adb\ folder.
- next, in the C:\adb\ folder hold down SHIFT key and RIGHT-CLICK and select "Open command window here".
-----
First, plug in phone to PC and type this in terminal/command prompt:
Code:
adb reboot bootloader
-----
Let's start by checking current system details. Type:
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000 [COLOR=Red][B]< This is your bootloader version[/B][/COLOR]
(bootloader) version-baseband: 4A.16.3250.24 [COLOR=Red][B]< This is your radio version[/B][/COLOR]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.666.17 [COLOR=Red][B]< This is your firmware version[/B][/COLOR]
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: <you don't need to know my serial#>
(bootloader) imei: <you don't need to know my IMEI>
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111 [COLOR=Red][B]< This is your CID[/B][/COLOR]
(bootloader) battery-status: good
(bootloader) battery-voltage: 4077mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Now type:
Code:
fastboot reboot-bootloader
After that, type:
Code:
fastboot oem rebootRUU
Note: You should see a silver HTC logo come up on your phone after executing this command.
Note: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
fastboot flash zip /Users/vomer/Desktop/firmware.zip
Windows users: your command will look something like this: fastboot flash zip C:\adb\firmware.zip
Got this:
Code:
sending 'zip' (71868 KB)...
OKAY [ 4.936s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 6.410s
Repeated same command:
Code:
fastboot flash zip /Users/vomer/Desktop/firmware.zip
Got this:
Code:
sending 'zip' (71868 KB)...
OKAY [ 4.884s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[adsp] unzipping & flushing...
(bootloader) [RUU]WP,adsp,0
(bootloader) [RUU]WP,adsp,100
(bootloader) ...... Successful
(bootloader) start image[cir] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-3] unzipping & flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1-3,0
(bootloader) [RUU]WP,sbl1-3,100
(bootloader) ...... Successful
(bootloader) start image[sbl2] unzipping & flushing...
(bootloader) [RUU]WP,sbl2,0
(bootloader) [RUU]WP,sbl2,100
(bootloader) ...... Successful
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]WP,sbl3,0
(bootloader) [RUU]WP,sbl3,100
(bootloader) ...... Successful
(bootloader) start image[tp] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]WP,tz,0
(bootloader) [RUU]WP,tz,100
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,26
(bootloader) [RUU]WP,radio,53
(bootloader) [RUU]WP,radio,79
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
OKAY [ 39.601s]
finished. total time: 44.485s
Note: On my phone's screen the green bar did not go to 100% of the bar ... but everything seemed ok so I moved on.
Last Step:
Code:
fastboot reboot
Then I went back to the bootloader mode (after the phone reboots successfully):
Code:
adb reboot bootloader
Checked if the update worked:
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000 [COLOR=Red][B]< Looks New![/B][/COLOR]
(bootloader) version-baseband: 4A.17.3250.14 [COLOR=Red][B]< Looks New![/B][/COLOR]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1 [COLOR=Red][B]< Looks New![/B][/COLOR]
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: you don't need to know my serial#
(bootloader) imei: you don't need to know my IMEI#
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111 [COLOR=Red][B]< Oh Look! I'm Superman :) [/B][/COLOR]
(bootloader) battery-status: good
(bootloader) battery-voltage: 4331mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
SECTION 3: RECOVERY
Note: I personally prefer TWRP - so my guide below points to using TWRP.
If you like CWM, you can follow the same steps but with the latest CWM file.
----
Get latest TWRP: http://techerrata.com/browse/twrp2/m7ul
With your phone plugged into your PC, type in:
Code:
adb reboot bootloader
Once in bootloader mode, type:
Code:
Mac/Linux: fastboot flash recovery /Users/vomer/Desktop/openrecovery-twrp-2.6.1.0-m7.img
Windows: fastboot flash recovery C:\adb\openrecovery-twrp-2.6.1.0-m7.img
Then:
Code:
fastboot reboot
You are now the the latest version of TWRP.
----
That's it! Enjoy your new found freedom
finally you made own thread
descenpet said:
finally you made own thread
Click to expand...
Click to collapse
haha yes sir! got so many PM's to do it but I didn't want to half-ass it. Had some time today so decided to get it done the proper way!
It is necessary to have bootloader unlocked?
Sent from my HTC One using xda premium
Omg thank you so much I hope this will fix my sleep of death on cm roms issue.
Amazing and easy to follow. Thanks OP
vengadorhq said:
It is necessary to have bootloader unlocked?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Yes, bootloader must be unlocked if your looking to do any customization!
STICKY THIS THREAD!!!
Great guide!
Wait... I need to re-lock my bootloader and remove root and go back to stock to get S-OFF? o.o?
aulterra said:
Wait... I need to re-lock my bootloader and remove root and go back to stock to get S-OFF? o.o?
Click to expand...
Click to collapse
What?
Sent from my HTC One using xda premium
Wonderful thread. It's of no use to me, but I tossed you a Thanks because when it concerns S-OFF, the simplest and most easy-to-follow guides make all the difference for frightened users.
Thanks!
descenpet said:
What?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Well i'm rooted and have my bootloader unlocked from htcdev but i'm S-ON so do I need to relock to use revone to get S-OFF? Or not? Or relock and un root? Or?
aulterra said:
Well i'm rooted and have my bootloader unlocked from htcdev but i'm S-ON so do I need to relock to use revone to get S-OFF? Or not? Or relock and un root? Or?
Click to expand...
Click to collapse
No relock needed
Sent from my HTC One using xda premium
Devaster said:
No relock needed
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
So I can Go ahead now and get S-OFF right now using revone even with an already unlocked bootloader?
aulterra said:
So I can Go ahead now and get S-OFF right now using revone even with an already unlocked bootloader?
Click to expand...
Click to collapse
Yes
Sent from my Nexus 7
vomer said:
Yes
Sent from my Nexus 7
Click to expand...
Click to collapse
Ok sounds great. Do you think that once I have S-OFF and Super CID that the Firmware update will fix my Sleep of Death issues on CM roms? codeworkx said the issue is from what he said a KGSL derp or something. The firmware update would update the gpu driver or update stuff that would effect the gpu driver?
Just wondering, thanks for the amazing guide btw, easiest i've seen so far to follow. Will be doing it tonight after work. Wanted to do it now but I decided not to since I need my phone charged as much as possible before I go to work today (have to get into work early and I didn't know until before so My phone was nearly flat xD)
aulterra said:
Ok sounds great. Do you think that once I have S-OFF and Super CID that the Firmware update will fix my Sleep of Death issues on CM roms? codeworkx said the issue is from what he said a KGSL derp or something. The firmware update would update the gpu driver or update stuff that would effect the gpu driver?
Just wondering, thanks for the amazing guide btw, easiest i've seen so far to follow. Will be doing it tonight after work. Wanted to do it now but I decided not to since I need my phone charged as much as possible before I go to work today (have to get into work early and I didn't know until before so My phone was nearly flat xD)
Click to expand...
Click to collapse
I am not sure on gpu drivers, but this should solve the issue if it is firmware related.
Sent from my Nexus 7
Superb guide! Thanks a lot bro!
Do you no how to get rid of the red writing in boot up splash screen. One thread I read is very confusing. Do I just flash the modified hboot zip?
Sent from my HTC One
Excellent guide, should definitely be stickied. Thanks Vomer :beer: :beer: :beer:
Sent from my HTC One using Tapatalk 2
[Solved] HTC Butterfly S-Off, Unlock, Bootloader & TWRP Recovery "Stuck in bootloop."
PLEASE try to HELP or acknowlede!
Please forgive me for contacting you as such but I'm desparate right now.
Dear All,
I'm wound up in a bootloop. Please help at the earliest.
This is my current status and a little history.
1. I was flashed InsertCoin 3.0.6 on my x920d (originally HTC_038) a couple of days ago (and did a TWRP Backup after That),
2. Had unlocked my previous, old custom rom (thru HTCDev), S-Off (thru rumrunner) and
3. rooted by flashing 'UPDATE-SuperSU-v2.02' from recovery after flashing the ROM a couple of days earlier.
4. I had also flashed Kairi's firmware-kk (which is for HTC_061) as I had Super CID 11111111 by "fastboot oem writecid..." method, now I'm not able to do it anymore).
Anyway, there was some problem (wrongly presumed by me) with the htc backup/restore function, so I reflashed the IC3.0.6 rom a couple of times thru recovery(TWRP 2.7 by Kairi). And the device booted perfectly.
Stupidly, I happened to flash '[ROM] FireKatN4 Deodex V5 TW 4.4.4' through Kairi's recovery. Link of the ROM - http://forum.xda-developers.com/note...emely-t2916463.
Thish rom was for Samsung T Mobile Galaxy Note 4 N910T and it did not flashed properly; so I re-flashed IC3.0.6 thru recovery (if required I can perform this again) and it showed successful at the end.
Now since then whenever I reboot it get stuck in bootloop.
Since yesterday I have been trying various steps (repeated several times and not inchronological order):
- Unlocked the bootloader thru HTCDev once again.
- Flashing the firmware-kk thru oemRUU after changing the CID to 11111111 in the 'adroid-info file" of this firmware's zip. (it gave Remote90 error and after repeating fastboot flash zip firmware-kk.zip it flashed.
Although in between it said "signature checking, verified fail - Bypassing" and then continued on its own after that, successful at the end. However on my device the green bar moved only to 90% and remained there.)
- Rebooted into bootloader, tried flashing the same firmware with Error :
"C:\Fastboot>fastboot flash zip firmware-kk.zip
target reported max download size of 1514139648 bytes
sending 'zip' (19401 KB)...
OKAY [ 1.975s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.011s"
Now my status is:
Although I'm able to flash recovery img thru fastboot. I can do it from oem rebootRUU.
My Getvar all read as :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 3A.32.306.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.04.709.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxx
(bootloader) imei: xxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: deluxe_ub1
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL9911000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4196mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11 - (As per Kairi's original Firmware-kk android-info file it is : 3, the CID is HTC_061)
(bootloader) gencheckpt: 0
all: Done!
Now
1. I,m S-Off, Relocked/Unlocked Bootloader (able to do this thru fastboot).
2. Can boot into bootloader & TWRP Recovery - Kairi's, but cannot boot the phone.
3. After flashed IC3.0.6 thru recover once again. when rebooting, get stuck in bootloop again.
Please try to help me out.
P.S. I have somescreenshots available of several steps, if required.
Hi Capt Vikram.
Try extracting the boot img and flash that. It has got me out of a few bootloops
Clarkie_955i said:
Try extracting the boot img and flash that. It has got me out of a few bootloops
Click to expand...
Click to collapse
Hi Clarkie,
Your help is appreciated.
I flashed the IC3.0.6 rom thru recovery successfull.
rebooted to bootloop.
Then I flashed the boot img from InsertCoin 3.0.6 from fastboot.
No luck Again stuck in bootloop.
Capt Vikram Sandhu said:
Hi Clarkie,
Your help is appreciated.
I flashed the IC3.0.6 rom thru recovery successfull.
rebooted to bootloop.
Then I flashed the boot img from InsertCoin 3.0.6 from fastboot.
No luck Again stuck in bootloop.
Click to expand...
Click to collapse
Did you flash the kk firmware twice? It will fail on the first go so flash again.
Clarkie_955i said:
Did you flash the kk firmware twice? It will fail on the first go so flash again.
Click to expand...
Click to collapse
Yes Clarkie,
I had flashed firmware-kk thru 'fastboot oem rebootRUU', then 'fastboot flash zip fimware-kk.zip'
It gave me th 90 error and I repeated the command and it went successful.
I'll do that again and update you with each step chronologically.
Thanks for your help in my desparate situation.
Here's what I repeated. Step - by -step
1. First of all got the getvar all details:
C:\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 3A.32.306.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.04.709.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ------------------
(bootloader) imei: -----------------------
(bootloader) meid: 00000000000000
(bootloader) product: deluxe_ub1
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL9911000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4195mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
QUERY : Should I be concerned regarding
i. (bootloader) platform: HBOOT-8064
ii. (bootloader) hbootpreupdate: 11, because in Kairi's firmware zip the android-info reads
1) CID H_061 (I changed it to 11111111)
2) hbootpreupdate:3 (This I did not change)
2. Relocked the boot loader (after checking if I could unlock it again through the previous code.bin. I did this successfully but without Selecting 'Yes' option at the end of the process on my device)
C:\Fastboot>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
(bootloader) [HTC]PS_HOLD resets device!
FAILED (status read failed (Too many links))
finished. total time: 1.246s
C:\Fastboot>fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
target reported max download size of 1514139648 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.136s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.009s]
finished. total time: 0.148s
NOTE: Both the times device booted into bootloop.
3. Flashing Kairi's firmware-kk.zip through RUU
a. Rebooted in RUU
C:\Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.053s]
finished. total time: 0.055s
b. Flashed firmware-kk (remember the file CID changed to 11111111
C:\Fastboot>fastboot flash zip firmware-kk.zip
target reported max download size of 1514139648 bytes
sending 'zip' (19401 KB)...
OKAY [ 2.007s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 3.490s
C:\Fastboot>
C:\Fastboot>fastboot flash zip firmware-kk.zip
target reported max download size of 1514139648 bytes
sending 'zip' (19401 KB)...
OKAY [ 2.016s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1-2,0
(bootloader) [RUU]WP,sbl1-2,100
(bootloader) ...... Successful
(bootloader) start image[sbl2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl2,0
(bootloader) [RUU]UZ,sbl2,100
(bootloader) [RUU]WP,sbl2,0
(bootloader) [RUU]WP,sbl2,100
(bootloader) ...... Successful
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) [RUU]WP,sbl3,0
(bootloader) [RUU]WP,sbl3,100
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,8
(bootloader) [RUU]UZ,radio,13
(bootloader) [RUU]UZ,radio,22
(bootloader) [RUU]UZ,radio,31
(bootloader) [RUU]UZ,radio,40
(bootloader) [RUU]UZ,radio,49
(bootloader) [RUU]UZ,radio,58
(bootloader) [RUU]UZ,radio,67
(bootloader) [RUU]UZ,radio,75
(bootloader) [RUU]UZ,radio,80
(bootloader) [RUU]UZ,radio,89
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,35
(bootloader) [RUU]WP,radio,71
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,42949671
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,42949671
(bootloader) ...... Successful
OKAY [ 10.628s]
finished. total time: 12.650s
Note: In the device the green bar did not reach the end. And did not reboot.
c. 'fastboot reboot bootloader' - command not recognized
d. 'fastboot reboot' - rebooted into bootloop
e. Manually booted the device into bootloader.
4. Getvar all - Same as previous.
5. Unlocked the bootloader.
C:\Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1514139648 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.136s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.010s]
finished. total time: 0.149s
Note: The device automatically rebooted into bootloop yet again. Manually rebooted to bootloader it shows *** UNLOCKED ***
6. Re flashed Kairi's TWRP
C:\Fastboot>fastboot flash recovery TWRP-2-7-Kairi.img
target reported max download size of 1514139648 bytes
sending 'recovery' (10572 KB)...
OKAY [ 1.564s]
writing 'recovery'...
OKAY [ 0.977s]
finished. total time: 2.546s
7. Entered Recovery from the device. (To install Kairi's reset kernel) Did not wipe cache/dalvik after installation
Note: - 'adb reboot bootloader' did not work at recovery, thou
C:\Fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FA34HPN00627 recovery
C:\Fastboot>adb reboot bootloader
8. Entered bootloader thru TWRP options on the device.
9. Flashed boot.img (extracted from InsertCoin 3.0.6 Zip). Did not erase cache after this.
C:\Fastboot>fastboot flash boot boot.img
target reported max download size of 1514139648 bytes
sending 'boot' (6500 KB)...
OKAY [ 0.926s]
writing 'boot'...
OKAY [ 0.747s]
finished. total time: 1.677s
10. Entered recovery to install InsertCoin Rom.
a. Selected - Perform a full wipe in the installer.
b. Deselected all the checkmarks (for HTC + Google)
c. Selected - 'Enable Cache - All times' in the end
d. Install. (Please refer the attached screen shots)
e. Reboot your Device now from the installer. (HOPE TO boot into android. Fingers crossed).
f. Again Bootloop.
g. Rebooted into bootloader
h. Fastboot the boot image once again erased cache after that.
C:\Fastboot>fastboot flash boot boot.img
target reported max download size of 1514139648 bytes
sending 'boot' (6500 KB)...
OKAY [ 0.926s]
writing 'boot'...
OKAY [ 0.745s]
finished. total time: 1.675s
C:\Fastboot>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.068s]
finished. total time: 0.070s
I. Still in bootloop.
Please help/advice.
Hi Vikram.
This could be the blind leading the blind. But I will help out as much as I can.
I had the same problem with IC boot looping and especially with my nandroid backups. See if you can download a different rom and get that on your sd card and flash that. You can try BOA Butterfly v8.0 that always booted up for me when IC wouldn't. I also found a stock nandroid x920d backup that worked. At least I had my device working until I had the time to sort out IC on my device.
Now a couple of your queries.
My cid 11111111
HBOOT 1.57
The green progress bar never reaches the end it always stays at about 90% and reboot bootloader command should be like this
"adb reboot-bootloader" without the quotes
Sorry Vikram all over the place tonight I just finished work. Hope this helps. Plus the best information I can give you as well is search this site. everything you need is on here with a little searching. Only been doing this since July and I also tried to flash every rom out there only to discover that they all don't work. Got myself out of a few bootloops.
Try what I mentioned above and see how you go with that.
Clarkie_955i said:
Hi Vikram.
This could be the blind leading the blind. But I will help out as much as I can.
I had the same problem with IC boot looping and especially with my nandroid backups. See if you can download a different rom and get that on your sd card and flash that. You can try BOA Butterfly v8.0 that always booted up for me when IC wouldn't. I also found a stock nandroid x920d backup that worked. At least I had my device working until I had the time to sort out IC on my device.
Now a couple of your queries.
My cid 11111111
HBOOT 1.57
The green progress bar never reaches the end it always stays at about 90% and reboot bootloader command should be like this
"adb reboot-bootloader" without the quotes
Sorry Vikram all over the place tonight I just finished work. Hope this helps. Plus the best information I can give you as well is search this site. everything you need is on here with a little searching. Only been doing this since July and I also tried to flash every rom out there only to discover that they all don't work. Got myself out of a few bootloops.
Try what I mentioned above and see how you go with that.
Click to expand...
Click to collapse
Thanks A TON Clarkie,
Your reply is very much appreciated. It seems like a ray of hope in a dark tunnel. Really grateful to you.
Now coming back to the matter at hand -
I had earlier tried to
1. Tried to flash 'NOS_m7_v3.0.0_dlxbu1' thru Recovery, was successful but when tried to boot, got stuck again in bootloop. Then again installed InserCoin.
Note - Maybe I did not perfom a wipe cache & definately did not flash the boot image thru fastboot after flashing the above rom.
Secondly I'm neither able to reboot from bootloader mode into recovery nor vice verca.
Thirdly, I cannot flash any zip from bootloader (but able to flash image files thru bootloader & install zip thru recovery); & no "fastboot reboot recovery" from bootloader mode and no "adb reboot bootloader"
from recovery (same with RUU "fastboot reboot bootloader", though in recovery & fastboot mode "adb/fastboot devices" show my device).
Fourthly, whenever I reboot into system/android I get Two bootscreens - 1. HTC Quietly Brilliant & the device gets disconnected and connected again and the second boot screen is HTC One.
Finally it stays at the HTC One screen for some time and suddenly there is some very slight variation in the brightness of the bootscreen, then the capacitive buttons (Back, Home & Recent app) lightens and it
reboots.
2. Tried to restore from TWRP Backup (when I was successfully running InserCoin for the first time) but again the bootloop. I also have one of NOS_m7_v3.0.0 (When I was S-On), that I've not tried yet as I'm afraid to get
back to S-On and bootloop at the same time..
3. Meanwhile, today a couple of hours ago, I came across this thread - http://forum.xda-developers.com/showthread.php?t=2208833, and
performed an advanced wipe thru recovery (wiping everythingh except external sd card). Wiped Dalvik Cache. TWRP Backup. Rebooted. (For a lovely change) Got stuck at boot screen -HTC Quitely Briliant.
(maybe no OS installed).
4. Manually went into bootloader and then recovery. Installed InsertCoin again. At the end it said no SuperSU. Swiped to install it. Reboot. Got stuck at Bootloop.
Please try to Suggest:
A. When to flash boot.img - before or after installing the rom.
B. Does restoring S-On state backup will effect my S-Off condition.
Thanx In Advance.
1 + 1 = 11
Will Definately try BOA's Rom meanwhile.
HI Clarkie,
Tried the download links at BOA's ROM thread in the forum. Doesen't work.
Can you provide me a link.
Ok Vikram.
From what I have done and read I have always done a factory reset thru recovery before flashing any rom. Also try re flashing TWRP same version. I also got stuck on HTC ONE screen and turned the device of at power button and back on and it booted up fine. I would keep your device at s.off and i flashed the boot img after the rom because the device would not boot. Sorry for the short replies I am not that quick on the keyboard.
Here is the link for boa
http://forum.xda-developers.com/showthread.php?t=2656094
Spare link 4 is still up.
Just keep going on it. It is a process of thinking what worked before and why it not working now.
Keep me posted
Clarkie_955i said:
Ok Vikram.
From what I have done and read I have always done a factory reset thru recovery before flashing any rom. Also try re flashing TWRP same version. I also got stuck on HTC ONE screen and turned the device of at power button and back on and it booted up fine. I would keep your device at s.off and i flashed the boot img after the rom because the device would not boot. Sorry for the short replies I am not that quick on the keyboard.
Here is the link for boa
http://forum.xda-developers.com/showthread.php?t=2656094
Spare link 4 is still up.
Just keep going on it. It is a process of thinking what worked before and why it not working now.
Keep me posted
Click to expand...
Click to collapse
Thanks Clarkie,
I'll give it a shot.
And let you know.
Capt Vikram Sandhu said:
Thanks Clarkie,
I'll give it a shot.
And let you know.
Click to expand...
Click to collapse
Check your commands you need one of these ---- between adb reboot-bootloader. That is what I was trying to say last night. Not sure if you got it.
Cheers
Clarkie_955i said:
Check your commands you need one of these ---- between adb reboot-bootloader. That is what I was trying to say last night. Not sure if you got it.
Cheers
Click to expand...
Click to collapse
Got it Sir,
Thanx.
P.S. Downloading the BOA Rom from the link. Will let you know what happens.
Capt Vikram Sandhu said:
Got it Sir,
Thanx.
P.S. Downloading the BOA Rom from the link. Will let you know what happens.
Click to expand...
Click to collapse
No worries.
Remember if it gets stuck on htc screen power off with power button and restart. See how you go.
Good Luck
Clarkie_955i said:
No worries.
Remember if it gets stuck on htc screen power off with power button and restart. See how you go.
Good Luck
Click to expand...
Click to collapse
Hi Clarkie,
Tried the following:
Installed TWRP 2.6.3
Factory reset from recovery.
Installed BOA V8.0 thru recovery (Couldn't understand the language of aroma installer, but went ahead both the times).
Device Rebooted into bootloop again.
Powered off with only the power button, but then it again restarted into bootloop.
Flashed the boot.img thru fastboot. Reboot. Again bootloop.
Went to Recovery. Wiped everythingh except Micro SDcard
Installed the rom thru recovery install zip
Aroma Installer Finished Screen -> from recovery reboot options went into fastboot. Flashed the boot.img.
Rebooted to System - Back to square 1 in bootloop.
Also during the bootloop pressing down the power button does not power off & restarts the device. But the screen goes off for a few seconds and automatically boots intp the bootloop.
FYI -
I'm using a partitioned sd card. with 1. FAT32, 2. ext4 & 3. Linux SWAP. And thru recovery file manager it showed sd-ext & superuser folders in the root. I'll give it a try on an unpartitioned card.
had successfully, flashed recovery-clockwork-touch-6.0.3.1-dlxub1 before flashing TWRP 2.6.3. But the CWMod recovery shows the following:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I tried adb reboot-bootloader but nothing happens.
Please try to suggest from here.
How can I check (from Bootloader/recovery) if my device is rooted/unrooted.
I mean when the splash screens stays on for more than a few minutes and not in boot loop hit the power button to off then back on. That has worked for me. I am not sure about your partitioned sd card. I just store things on mine.
Have a look at this. http://forum.xda-developers.com/showthread.php?t=2283896
I had the same similar errors a while ago but I cant remember how I fixed it. Well I do. I fixed one error at a time and lots of searching.
Clarkie_955i said:
I mean when the splash screens stays on for more than a few minutes and not in boot loop hit the power button to off then back on. That has worked for me. I am not sure about your partitioned sd card. I just store things on mine.
Have a look at this. http://forum.xda-developers.com/showthread.php?t=2283896
I had the same similar errors a while ago but I cant remember how I fixed it. Well I do. I fixed one error at a time and lots of searching.
Click to expand...
Click to collapse
I have done again the following steps as you said:
1. Started the Device.
2. First Splash screen came up - HTC quietly Briliant.
3. Second Splash Screen came up - HTC One.
4. Waited for one/two seconds and pressed continuosly on the power button.
5. Screen went totally black/maybe powered off.
6. Removed my finger from the Power button in order to press it back to power the device.
7. Before I can press it is back on the first splash screen pops up and the bootloop starts.
8. Even If I do not release the power button after the 5th step it automatically reboots & bootloop starts.
I did try this from the first bootscreen and also after complete power down from bootloader/recovery mode.
Meanwhile I'll search the link you gave.
I think that maybe I'm unrooted now because when i try thru recovery - advance - file manager, I cannot see any file in /system/bin/ (where there should have been a su file there.)
Thanks for your reply . will keep you posted.
Your replies mean a lot to me.
Hi Clarkie,
Re-read all of your posts and guidance.
Motivated by this and the links provided espaicially by you and reply from abhinav.tella I think I'm able to lock on the problem (perhaps).
Right now compiling it and will post with further details.
Kindly try to walk me thru it with your suggestions and guidance.
Thanx in advance.
Bits and Pieces
Hi Clarlie,
Thanks for your time & energy till date. You are kind enough to help out somebody very selflessly on your part. I'm motivated and have inculcated the same.
Anyway, I tried to understand the whole thing piece by piece. Also I have assimilated a few screenshots (I have many others if required.)
The following is only what I did & now think could be the cause.
First of all; I had successfully installed and was running InsertCoin a few days ago. See Step by Sep as per the numbered images attached with this and several within the next few following posts.
1
1. 1. Unlocked, rooted & running InserCoin, (but a Kernel & firmware based on 4.2 custom rom) --- 28-11-14 17-23hrs
1. 2. Achieved S-Off with XUNUS's (http://forum.xda-developers.com/htc-butterfly/help/qa-insertcoin-3-0-6-dlxub1-android-4-4-t2950052)help & updated to TWRP 2.7 Kairi's along with reste-kernel-ub1 again Kairi's, 29-11-14 19-32.
1. 3. bootloader after s-off before revone, 29-11-14 23-09.
1. 4. bootloader after removing TAMPERED thru revone, 30-11-14 00-02
Cont to next to post...
Capt Vikram Sandhu said:
Hi Clarlie,
Thanks for your time & energy till date. You are kind enough to help out somebody very selflessly on your part. I'm motivated and have inculcated the same.
Anyway, I tried to understand the whole thing piece by piece. Also I have assimilated a few screenshots (I have many others if required.)
The following is only what I did & now think could be the cause.
First of all; I had successfully installed and was running InsertCoin a few days ago. See Step by Sep as per the numbered images attached with this and several within the next few following posts.
1
1. 1. Unlocked, rooted & running InserCoin, (but a Kernel & firmware based on 4.2 custom rom) --- 28-11-14 17-23hrs
1. 2. Achieved S-Off with XUNUS's (http://forum.xda-developers.com/htc-butterfly/help/qa-insertcoin-3-0-6-dlxub1-android-4-4-t2950052)help & updated to TWRP 2.7 Kairi's along with reste-kernel-ub1 again Kairi's, 29-11-14 19-32.
1. 3. bootloader after s-off before revone, 29-11-14 23-09.
1. 4. bootloader after removing TAMPERED thru revone, 30-11-14 00-02
Cont to next to post...
Click to expand...
Click to collapse
Ok Vikram.
I found this for you. It is a very good write up with great detail. http://forum.xda-developers.com/showthread.php?t=2630214
Hope this gets you going.
---------- Post added at 07:37 AM ---------- Previous post was at 07:29 AM ----------
Clarkie_955i said:
Ok Vikram.
I found this for you. It is a very good write up with great detail. http://forum.xda-developers.com/showthread.php?t=2630214
Hope this gets you going.
Click to expand...
Click to collapse
You might want to change your cid. Thought you was supercid 11111111
So you want to use the latest custom ROM but you're on 2.1x firmware. That's not an big issue as long as you're S-OFF. If you're not S-OFF download, install and run Sunshine-3.5.8 (or higher when available). Follow instructions and pay the $25,= You'll be S-OFF within 5 minutes and it's really worth the money considering the functionality you get in return.
Now that you're S-OFF it's time to downgrade the firmware. In order to do so you need the right RUU which can be found in this threat. Download the RUU (zip) to your computer.
Within this RUU you'll find the firmware we need but it's encrypted. Now download the RUU_Decryption_Tool.zip and extract it to any folder of your likings. Let's call it c:\RDT\ e.g. The executable in this folder is a command, not a GUI. Copy the RUU to the same folder RDT and rename it to RUU.zip.
Open up a commandprompt (windows-key - cmd.exe) and head to the folder RDT. Now enter RUU_Decryption_Tool RUU.zip You'll be asked what to do in a menu. All you need is to extract the firmware, nothing else! The tool will decrypt the firmware and copy it to a subfolder. Move to the new folder "firmware" and compress all the files within this folder to a ZIP-file called firmware.zip It does not have to be signed since we're S-OFF.
We've got two important files now. The firmware.zip and the RUU file. To be able to use the RUU rename it to 2PQ9IMG.zip and copy it to the root of your SD-card. While we're copying anyway you might want to copy your custom ROM, GAPPS etc. to the SD-card as well!
Copy the firmware.zip to your adb fastboot folder
Boot your device into download mode. It will ask you if you want to install the RUU (2PQ9IMG.zip). Press volume down to pass. Open up a commandprompt and enter the following fastboot command: htc_fastboot flash zip firmware.zip First time will fail but no panic. Your device will reboot and repeat the command by itself. The firmware will be installed, this doesn't take long.
Once finished, reboot your device again into download mode and install the RUU (volume up). When it's done reboot your device and android will show up. Wait until setup screen so that all partitions will work and reboot again to download mode. Now flash the latest TWRP. Open a commandprompt and enter: htc_fastboot flash recovery twrp-3.1.1-0-hiae.img Reboot into recovery mode and do a data wipe. TWRP will ask you to comfirm this by typing "yes". Once done select advanced wipe and wipe the dalvik/cache and system partitions. After this it's business as usual. Flash your custom ROM, SuperSU, GApps etc. and reboot.
done. :good:
I hope this will help out some people. I've done this several times and it's pretty safe. Nevertheless, don't blame be for wrecking your device if something goes wrong!
As I can remember Qc 3.0 support came with an update. If I downgrade to 6.0 will I continue to use Qc 3.0 ?
I tried this like 15 times. S-off. 2.18.617.30. Unlocked. Rooted.
c:\Sam>htc_fastboot flash zip firmware.zip
sending 'zip'... (133925 KB) OKAY
sending time = 6.731 secs
writing 'zip'... (bootloader) HOSD CL#861328
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAIL22 RU_HEADER_ERROR
FAILED (remote: 22 RU_HEADER_ERROR )
Execution time is 9(s)
Trying from this
https://forum.xda-developers.com/showpost.php?p=73489502&postcount=825
thank you succesfully downgraded ...
Nuroxy said:
I tried this like 15 times. S-off. 2.18.617.30. Unlocked. Rooted.
c:\Sam>htc_fastboot flash zip firmware.zip
sending 'zip'... (133925 KB) OKAY
sending time = 6.731 secs
writing 'zip'... (bootloader) HOSD CL#861328
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAIL22 RU_HEADER_ERROR
FAILED (remote: 22 RU_HEADER_ERROR )
Execution time is 9(s)
Click to expand...
Click to collapse
pls zip files into firmware.zip.not firmware folder to zip.:good::good:
hmm may i , just a short question .. why do i need S-OFF ?
solved said:
hmm may i , just a short question .. why do i need S-OFF ?
Click to expand...
Click to collapse
You need s-off to disable signature verification on all partitions since your home-made firmware.zip will not be signed with HTC's key.
Any htc one a9 device supported
Any htc one a9 device supported
Please emergency ans the question
alray said:
You need s-off to disable signature verification on all partitions since your home-made firmware.zip will not be signed with HTC's key.
Click to expand...
Click to collapse
It's there a way to extract those HTC Keys and Sign the zip with them ? I mean to get the ''certificate.Perm and Key.pk8''.?
HckruxRD said:
It's there a way to extract those HTC Keys and Sign the zip with them ? I mean to get the ''certificate.Perm and Key.pk8''.?
Click to expand...
Click to collapse
The only key that can be extracted from a signed RUU or a signed firmware is the public key present on every phone. The private key used by htc to sign their files is, afaik, impossible to know. I'm pretty sure devs wouldn't waste time on S-OFF if signing your own file was possible...
please help, I kept getting this error about sensor_hub.img
it never flashed successfully
Hi everyone, could you please help me i have a htc A9 and i face a bootloop . the phone hasn't the usb debugging on and it is S-on, i tried with fastboot to change the ruu but impossible always have failed in cmd prompt
Code:
(bootloader) kernel: lk
(bootloader) product: htc_hiaeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 751200000
(bootloader) serialno: HT5ARBE06603
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 352636071084888
(bootloader) version-main: 2.16.163.4
(bootloader) boot-mode: RUU
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PQ910000
(bootloader) cid: VODAP203
if someone has an idea i would appreciate coz i'm stuck
I tried to flash a rom using fastboot and i get this error message
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip 2PQ9IMG.zip
target reported max download size of 751200000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1029804250 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 278606042 is not a multiple of the block size 4096
sending sparse 'zip' (733590 KB)...
error: write_sparse_skip_chunk: don't care size 1029804250 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1029804250 is not a multiple of the block size 4096
OKAY [ 32.033s]
writing 'zip'...
(bootloader) HOSD CL#853511
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_h
(bootloader) RvMuM
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22 RU_HEADER_ERROR )
finished. total time: 57.319s
thanks for your help
kabelou said:
Hi everyone, could you please help me i have a htc A9 and i face a bootloop . the phone hasn't the usb debugging on and it is S-on, i tried with fastboot to change the ruu but impossible always have failed in cmd prompt
Code:
(bootloader) kernel: lk
(bootloader) product: htc_hiaeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 751200000
(bootloader) serialno: HT5ARBE06603
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 352636071084888
(bootloader) version-main: 2.16.163.4
(bootloader) boot-mode: RUU
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PQ910000
(bootloader) cid: VODAP203
if someone has an idea i would appreciate coz i'm stuck
I tried to flash a rom using fastboot and i get this error message
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip 2PQ9IMG.zip
target reported max download size of 751200000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1029804250 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 278606042 is not a multiple of the block size 4096
sending sparse 'zip' (733590 KB)...
error: write_sparse_skip_chunk: don't care size 1029804250 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1029804250 is not a multiple of the block size 4096
OKAY [ 32.033s]
writing 'zip'...
(bootloader) HOSD CL#853511
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_h
(bootloader) RvMuM
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22 RU_HEADER_ERROR )
finished. total time: 57.319s
thanks for your help
Click to expand...
Click to collapse
What ruu version are you trying to flash?
Are you using htc_fastboot.exe or fastboot.exe?
alray said:
What ruu version are you trying to flash?
Are you using htc_fastboot.exe or fastboot.exe?
Click to expand...
Click to collapse
i tried a lot of ruu, an european ruu, vodaphone uk, etc
the htc_fastboot command doesn't work coz it's an old version, i tried to find the newest one but i didn't.
And the fastboot.exe it's the last version in android sdk manager and it's the only thing working...i cannot found ruu with cid vodap203....the phone is from france so if you can help me thanks
kabelou said:
i tried a lot of ruu, an european ruu, vodaphone uk, etc
the htc_fastboot command doesn't work coz it's an old version, i tried to find the newest one but i didn't.
And the fastboot.exe it's the last version in android sdk manager and it's the only thing working...i cannot found ruu with cid vodap203....the phone is from france so if you can help me thanks
Click to expand...
Click to collapse
You must use htc_fastboot.exe to flash RUU not fastboot.exe . The only ruu version that will work on your phone is 2.16.163.4 check on easy-firmware.com it's there
alray said:
You must use htc_fastboot.exe to flash RUU not fastboot.exe . The only ruu version that will work on your phone is 2.16.163.4 check on easy-firmware.com it's there
Click to expand...
Click to collapse
Hello Alray,
i tried to download the RUU you said but its not possible becaus i have to pay for it? do you have any access or are you able to download it ? if not no worries and thanks for help!!!.
Flahable zip
Would you like a flashable zip of the htc one a9 boostmobile/sprint stock rom with root?
anonymouseli said:
Would you like a flashable zip of the htc one a9 boostmobile/sprint stock rom with root?
Click to expand...
Click to collapse
Am glad that you asked this, I know that this is a different thread but I have been looking for a nougat flashable zip, am using HTC One A9 sprint version 1.10.651.1 hiaewhl S-OFF and boot loader unlocked, it's rooted with twrp 2.8.7.0 installed..I just want to grab this opportunity. I need to update my phone to nougat and return to stock.. I saw RUU.exe but I realized that you will flash firmware first before RUU.exe ,I didn't see RUU.zip for hiaewhl and I have not use RUU before..help me out.. I need any rom I can flash through custom recovery.. Is it safe for me to flash custom rom for hiaeul on my hiaewhl being S-OFF and bootloader unlocked? Pls your reply..
Sent from my 2PQ93 using XDA-Developers Legacy app
CAMERON1988 said:
Am glad that you asked this, I know that this is a different thread but I have been looking for a nougat flashable zip, am using HTC One A9 sprint version 1.10.651.1 hiaewhl S-OFF and boot loader unlocked, it's rooted with twrp 2.8.7.0 installed..I just want to grab this opportunity. I need to update my phone to nougat and return to stock.. I saw RUU.exe but I realized that you will flash firmware first before RUU.exe ,I didn't see RUU.zip for hiaewhl and I have not use RUU before..help me out.. I need any rom I can flash through custom recovery.. Is it safe for me to flash custom rom for hiaeul on my hiaewhl being S-OFF and bootloader unlocked? Pls your reply..
Sent from my 2PQ93 using XDA-Developers Legacy app
Click to expand...
Click to collapse
You should be alright ill upload it tomorrow
anonymouseli said:
You should be alright ill upload it tomorrow
Click to expand...
Click to collapse
I will be grateful
Sent from my 2PQ93 using XDA-Developers Legacy app
Stock Rom Rooted
CAMERON1988 said:
I will be grateful
Sent from my 2PQ93 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Okay here is a link to download the rom becuase , i just finish uploading it and its around 4gbs or so.
https://anonfile.com/E1P1E7mdbb/TWRP_zip
Steps to recover
1) First thing you should do is extract the rom, DO NOT FLASH THE ZIP FILE !!! .
2)Delete any old twrp folders in your sd card or phone storage, dont worry it will not affect the recovery itself.
3))Put the twrp folder in your device or sd card, however you can transfer it, its better if its on an sd card(make sure the folder says twrp).
4)Turn off the device and reboot into recovery.
5)Afterwards format the entire phone (Dont use factorey reset, use format data)just make sure you dont delete anything from the sd card.
6) Next go into restore or backup whatever its called and restore the rom from your sdcard, it should automatically detect the folder and if it doesnt try choosing the folder manually.
7) reboot the phone and give it sometime and if doesn't boot up after 20 minutes delete the cache or factory reset.
8) let me know if you got any questions email: [email protected]
---------- Post added at 06:32 PM ---------- Previous post was at 06:30 PM ----------
anonymouseli said:
Okay here is a link to download the rom becuase , i just finish uploading it and its around 4gbs or so.
https://anonfile.com/E1P1E7mdbb/TWRP_zip
Steps to recover
1) First thing you should do is extract the rom, DO NOT FLASH THE ZIP FILE !!! .
2)Delete any old twrp folders in your sd card or phone storage, dont worry it will not affect the recovery itself.
3))Put the twrp folder in your device or sd card, however you can transfer it, its better if its on an sd card(make sure the folder says twrp).
4)Turn off the device and reboot into recovery.
5)Afterwards format the entire phone (Dont use factorey reset, use format data)just make sure you dont delete anything from the sd card.
6) Next go into restore or backup whatever its called and restore the rom from your sdcard, it should automatically detect the folder and if it doesnt try choosing the folder manually.
7) reboot the phone and give it sometime and if doesn't boot up after 20 minutes delete the cache or factory reset.
8) let me know if you got any questions email: [email protected]
Click to expand...
Click to collapse
w.
---------- Post added at 06:32 PM ---------- Previous post was at 06:32 PM ----------
anonymouseli said:
Okay here is a link to download the rom becuase , i just finish uploading it and its around 4gbs or so.
https://anonfile.com/E1P1E7mdbb/TWRP_zip
Steps to recover
1) First thing you should do is extract the rom, DO NOT FLASH THE ZIP FILE !!! .
2)Delete any old twrp folders in your sd card or phone storage, dont worry it will not affect the recovery itself.
3))Put the twrp folder in your device or sd card, however you can transfer it, its better if its on an sd card(make sure the folder says twrp).
4)Turn off the device and reboot into recovery.
5)Afterwards format the entire phone (Dont use factorey reset, use format data)just make sure you dont delete anything from the sd card.
6) Next go into restore or backup whatever its called and restore the rom from your sdcard, it should automatically detect the folder and if it doesnt try choosing the folder manually.
7) reboot the phone and give it sometime and if doesn't boot up after 20 minutes delete the cache or factory reset.
8) let me know if you got any questions email: [email protected]
Click to expand...
Click to collapse
w.
OK thanks a lot, I will download it when I subscribe to a data plan because there's no Wi-Fi here
Sent from my 2PQ93 using XDA-Developers Legacy app
I couldn't download the file as it is failing whenever it gets to 1.97Gb I have tried several times but still the same I have spent almost 7gb but couldn't still get it downloaded..I don't know whether the fault is from the link or not
Sent from my 2PQ93 using XDA-Developers Legacy app