I have not been able to update to TWRP 2.8.5.0 from 2.8.0.3, every time I end up hanging in entering recovering in the white boot screen. I have tried fastboot and the RUU method, I always end up reinstalling the 2.8.0.3 TWRP to get recovery back. I checked the firmware everything is up to date but hboot currently on 16 latest is 19. Question could my hboot being out of date cause the update problem and can I just flash the hboot alone?
Affichage des articles dont le libellé est hboot. Afficher tous les articles
Affichage des articles dont le libellé est hboot. Afficher tous les articles
vendredi 27 février 2015
jeudi 26 février 2015
[Q] [5.0] Which partition is hboot? topic
Since Lollipop, I can no longer access hboot via /dev/block/mmcblk0p11, and when I do # mount | grep blk, it shows:
/dev/block/mmcblk0p45 /system ext4 ro,seclabel,noatime,data=ordered 0 0
/dev/block/mmcblk0p46 /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p39 /devlog ext4 rw,seclabel,nosuid,nodev,relatime,errors=continue, data=ordered 0 0
/dev/block/mmcblk0p27 /fataldevlog ext4 rw,seclabel,nosuid,nodev,relatime,errors=continue, data=ordered 0 0
/dev/block/mmcblk0p37 /carrier ext4 rw,seclabel,nosuid,nodev,noatime,grpid,data=ordere d 0 0
/dev/block/mmcblk0p22 /custdata ext4 ro,seclabel,nosuid,nodev,relatime,data=ordered 0 0
During 4.4.x, I was able to access hboot via mmcblk0p22 but it was gone since 5.0.x. I wanna take away those annoying red text, can anyone point me to the right direction?
/dev/block/mmcblk0p45 /system ext4 ro,seclabel,noatime,data=ordered 0 0
/dev/block/mmcblk0p46 /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p39 /devlog ext4 rw,seclabel,nosuid,nodev,relatime,errors=continue, data=ordered 0 0
/dev/block/mmcblk0p27 /fataldevlog ext4 rw,seclabel,nosuid,nodev,relatime,errors=continue, data=ordered 0 0
/dev/block/mmcblk0p37 /carrier ext4 rw,seclabel,nosuid,nodev,noatime,grpid,data=ordere d 0 0
/dev/block/mmcblk0p22 /custdata ext4 ro,seclabel,nosuid,nodev,relatime,data=ordered 0 0
During 4.4.x, I was able to access hboot via mmcblk0p22 but it was gone since 5.0.x. I wanna take away those annoying red text, can anyone point me to the right direction?
dimanche 22 février 2015
[Q] Cdma s-off for hboot 1.58? 3d help!! topic
Good morning all. Hopefully I can keep this short and sweet, and hopefully you all have the information that I don't want dig for. Well, I KNOW you have the information need, thanks in advance to everyone who's helped us beginners and intermediates with your question answers, helpful tutorials, and tips and tricks.
I have an HTC Evo 3D, Rooted, S-On, and I'd like to finally downgrade the hboot and get the S-Off. I have the Smooth Criminal rom installed with a Butteredtoast chaser and 4ext RC2 Recovery. Android 4.0.3, hboot 1.58, radio 1.09.00.0108, software 2.89.651.710RD. I'd just like help with the best procedure for downgrading and S-Offing for 2015.
Screenshots of specs are attached, I welcome and thank all input. Speaking of actually, my endgame was a 4.4.4 rom to fix force closes, and a full featured kernel with OTG, fastcharge and Linux swap support, any input on that would Re also be awesome. THANKS=)
I have an HTC Evo 3D, Rooted, S-On, and I'd like to finally downgrade the hboot and get the S-Off. I have the Smooth Criminal rom installed with a Butteredtoast chaser and 4ext RC2 Recovery. Android 4.0.3, hboot 1.58, radio 1.09.00.0108, software 2.89.651.710RD. I'd just like help with the best procedure for downgrading and S-Offing for 2015.
Screenshots of specs are attached, I welcome and thank all input. Speaking of actually, my endgame was a 4.4.4 rom to fix force closes, and a full featured kernel with OTG, fastcharge and Linux swap support, any input on that would Re also be awesome. THANKS=)
samedi 21 février 2015
[GUIDE] Return to Stock with hboot 1.56+ (M7) - Telstra Australia (no ruu avail) topic
Due to the massive inconvenience/time this has caused me, having little experience initially with android devices and coupled with the fact Telstra Australia will not release an RUU to make things easy, I thought I would document my method for those currently on hboot 1.5x+ who are wanting to roll their device back to complete stock. This process is specifically for people who want a Telstra branded rom for warranty and does require sunshine if you have hboot 1.57. This is for the HTC one M7 although I suspect the process is the same on the M8..
This method was performed in Windows 7 as Windows 8 seems to have issue with fastboot commands. If you have a different carrier, are performing this on Mac or plan to use a Nandroid please see nkk71s superguide for more details. Unfortunately the only 2 Telstra Nandroids I could find both failed for me.
*Please make sure fastboot is unchecked and usb debugging is turned on in developer options
I have packaged all of the tools needed including the RUU.zip I used in the link below. The Guru files are hosted separately.
http://1drv.ms/1AVZvMF
The Guru files are hosted here, you will need both of these.
Stock Rom Guru Reset
http://www.htc1guru.com/dld/guru_res...-24-841-1-zip/ - download
http://www.htc1guru.com/downloads/stock-rom-downloads/ - info
Bootloader to remove tamper/lock bootloader
http://www.htc1guru.com/dld/guru_boo...reset_1-0-zip/ - download
http://forum.xda-developers.com/show....php?t=2527194 - info
1. S-off must be achieved. If you have it already you are in luck, proceed. This table shows what you can or cannot achieve with S-off for reference. Cannot remember exactly where I found this. Please message me with username so I can provide props if known.

Methods:
a) If youre on hboot 1.44 use revone -
http://forum.xda-developers.com/show....php?t=2314582
http://revolutionary.io/
b) If you are hboot 1.54/1.55 you can attempt rumrunner
http://forum.xda-developers.com/show....php?t=2488772
http://rumrunner.us/
c) If you are in hboot 1.56/1.57 you will need sunshine for usd as I did. As far as I am aware there is currently no way around it. However I am very happy with this application and support. Firewater is discontinued.
http://theroot.ninja/
2. Reboot into bootloader/fastboot usb and perform getvar
fastboot getvar all
Note the following:
version-bootloader: 1.57.0000 hboot version
cidnum: TELST001 - CID
modelid: PN0714000 MID
version-main: 5.11.841.9 firmware
All Telstra devices should have a modelid of PN0714000. If for some reason you do not have this MID see nkk71s superguide for different MID/CID RUUs and download a different version.
BOOT LOOP
The firmware will be reset to a 1.29.x base when you flash the RUU which is fine for OTA updates. If you have previously experienced boot loop it is because the firmware coming out in the OTA updates is lower than the firmware already installed on your device. Firmware can only be upgraded not downgraded by OTAs.
3. Provided your MID is PN0714000 proceed to change your CID to match RUU CID. The CID associated with the RUU provided is HTC__044
fastboot oem writecid HTC__044
fastboot reboot-bootloader
*confirm CID is now HTC__044 see bootloader or getvar
4. Flash the RUU.
fastboot oem rebootRUU (silver htc will appear)
fastboot flash ruu.zip (it will report failed flush, repeat command)
fastboot flash ruu.zip (success)
fastboot reboot-bootloader
*bootloader should now read hboot 1.44
5. Change CID back to stock (TELST001)
fastboot oem writecid TELST001
fastboot reboot-bootloader
6. Mount and Launch TWRP custom recovery
fastboot boot openrecovery-twrp-2.8.4.0-m7
7. Once in TWRP your phone become available as a mass storage device. Run an ADB command to check the phone is being recognized in windows and then push the guru reset rom to the device.
adb devices
adb push Guru_Reset_M7_2.24.841.1.zip /data/media
If your device does not display a serial number executing an adb devices command you will need to install the drivers in device manager, it is likely an unrecognized device post RUU flash. See nk771s FAQ for instructions.
8. In TWRP recovery hit install, navigate to the data/media folder and select the Guru_Reset_M7_2.24.841.1.zip
Run through the installer and select the options as seen in this video
https://www.youtube.com/watch?v=Gqfly8XVw6w
When complete hit do not add root and reboot the device. If it gives option to wipe cache, do so.
9. Boot your phone as normal into the now stock 4.2.2 Rom, set up wireless and install the first two small OTA updates to confirm they are working. If successful uncheck fastboot/enable usb debugging again and reboot phone back into boot loader with adb command.
abd reboot bootloader
10. In fastboot USB mount/launch TWRP recovery then adb push the Guru Boot Loader tool to the device.
fastboot boot openrecovery-twrp-2.8.4.0-m7
adb push Guru_Bootloader_Reset_1.0.zip /data/media
11. Hit Install, Navigate to the folder and launch Guru_Bootloader_Reset_1.0.zip. Run through the wizard and select remove tamper and lock function then wipe cache. Video here for clarification.
https://www.youtube.com/watch?v=yimzmt23E6Q
12. Reboot the phone a few times into bootloader to make sure lock/tamper does not return
fastboot reboot-bootloader
If unlocked/tamper returns or the installer fails you may have to use the manual method, exercise caution. See nk771's FAQ for instructions.
13. Set S-on
fastboot oem writesecureflag 3
fastboot reboot-bootloader
Fastboot into bootloader a few times to make sure everything is fine before proceeding to final OTA updates.
14. Boot phone normally and proceed to do all of the remaining OTA updates to bring your software/firmware up to latest version. Sometimes the phone will boot into stock recovery mode first time after S-on, just reboot it, it will come good.
If you would prefer to use a Nandroid backup (although I am not sure why), start from step 7 and restore it via TWRP or CWM (depending on the backup type) in place of Guru Reset. After this is complete you can proceed with the remaining steps.
This all came about from Telstra being unwilling to repair my purple haze issue (which is clearly a sensor/camera module hardware defect) while having my bootloader unlocked/tampered. The purple haze issue occurred when my device was factory locked. I understand unlocking the boot loader voids warranty but this issue is hardware related which happens on stock software/firmware. I find it a little dishonest that HTC/Telstra want to charge me to have my unit replaced/repaired when it's a known hardware defect unless I am willing to go back through the process of making this device look like it's stock. I hope this can help some of the Telstra customers in the same position as RUU/Nandroids are almost non existent. Thank god for guru! ;)
This method was performed in Windows 7 as Windows 8 seems to have issue with fastboot commands. If you have a different carrier, are performing this on Mac or plan to use a Nandroid please see nkk71s superguide for more details. Unfortunately the only 2 Telstra Nandroids I could find both failed for me.
*Please make sure fastboot is unchecked and usb debugging is turned on in developer options
I have packaged all of the tools needed including the RUU.zip I used in the link below. The Guru files are hosted separately.
http://1drv.ms/1AVZvMF
The Guru files are hosted here, you will need both of these.
Stock Rom Guru Reset
http://www.htc1guru.com/dld/guru_res...-24-841-1-zip/ - download
http://www.htc1guru.com/downloads/stock-rom-downloads/ - info
Bootloader to remove tamper/lock bootloader
http://www.htc1guru.com/dld/guru_boo...reset_1-0-zip/ - download
http://forum.xda-developers.com/show....php?t=2527194 - info
1. S-off must be achieved. If you have it already you are in luck, proceed. This table shows what you can or cannot achieve with S-off for reference. Cannot remember exactly where I found this. Please message me with username so I can provide props if known.

Methods:
a) If youre on hboot 1.44 use revone -
http://forum.xda-developers.com/show....php?t=2314582
http://revolutionary.io/
b) If you are hboot 1.54/1.55 you can attempt rumrunner
http://forum.xda-developers.com/show....php?t=2488772
http://rumrunner.us/
c) If you are in hboot 1.56/1.57 you will need sunshine for usd as I did. As far as I am aware there is currently no way around it. However I am very happy with this application and support. Firewater is discontinued.
http://theroot.ninja/
2. Reboot into bootloader/fastboot usb and perform getvar
fastboot getvar all
Note the following:
version-bootloader: 1.57.0000 hboot version
cidnum: TELST001 - CID
modelid: PN0714000 MID
version-main: 5.11.841.9 firmware
All Telstra devices should have a modelid of PN0714000. If for some reason you do not have this MID see nkk71s superguide for different MID/CID RUUs and download a different version.
BOOT LOOP
The firmware will be reset to a 1.29.x base when you flash the RUU which is fine for OTA updates. If you have previously experienced boot loop it is because the firmware coming out in the OTA updates is lower than the firmware already installed on your device. Firmware can only be upgraded not downgraded by OTAs.
3. Provided your MID is PN0714000 proceed to change your CID to match RUU CID. The CID associated with the RUU provided is HTC__044
fastboot oem writecid HTC__044
fastboot reboot-bootloader
*confirm CID is now HTC__044 see bootloader or getvar
4. Flash the RUU.
fastboot oem rebootRUU (silver htc will appear)
fastboot flash ruu.zip (it will report failed flush, repeat command)
fastboot flash ruu.zip (success)
fastboot reboot-bootloader
*bootloader should now read hboot 1.44
5. Change CID back to stock (TELST001)
fastboot oem writecid TELST001
fastboot reboot-bootloader
6. Mount and Launch TWRP custom recovery
fastboot boot openrecovery-twrp-2.8.4.0-m7
7. Once in TWRP your phone become available as a mass storage device. Run an ADB command to check the phone is being recognized in windows and then push the guru reset rom to the device.
adb devices
adb push Guru_Reset_M7_2.24.841.1.zip /data/media
If your device does not display a serial number executing an adb devices command you will need to install the drivers in device manager, it is likely an unrecognized device post RUU flash. See nk771s FAQ for instructions.
8. In TWRP recovery hit install, navigate to the data/media folder and select the Guru_Reset_M7_2.24.841.1.zip
Run through the installer and select the options as seen in this video
https://www.youtube.com/watch?v=Gqfly8XVw6w
When complete hit do not add root and reboot the device. If it gives option to wipe cache, do so.
9. Boot your phone as normal into the now stock 4.2.2 Rom, set up wireless and install the first two small OTA updates to confirm they are working. If successful uncheck fastboot/enable usb debugging again and reboot phone back into boot loader with adb command.
abd reboot bootloader
10. In fastboot USB mount/launch TWRP recovery then adb push the Guru Boot Loader tool to the device.
fastboot boot openrecovery-twrp-2.8.4.0-m7
adb push Guru_Bootloader_Reset_1.0.zip /data/media
11. Hit Install, Navigate to the folder and launch Guru_Bootloader_Reset_1.0.zip. Run through the wizard and select remove tamper and lock function then wipe cache. Video here for clarification.
https://www.youtube.com/watch?v=yimzmt23E6Q
12. Reboot the phone a few times into bootloader to make sure lock/tamper does not return
fastboot reboot-bootloader
If unlocked/tamper returns or the installer fails you may have to use the manual method, exercise caution. See nk771's FAQ for instructions.
13. Set S-on
fastboot oem writesecureflag 3
fastboot reboot-bootloader
Fastboot into bootloader a few times to make sure everything is fine before proceeding to final OTA updates.
14. Boot phone normally and proceed to do all of the remaining OTA updates to bring your software/firmware up to latest version. Sometimes the phone will boot into stock recovery mode first time after S-on, just reboot it, it will come good.
If you would prefer to use a Nandroid backup (although I am not sure why), start from step 7 and restore it via TWRP or CWM (depending on the backup type) in place of Guru Reset. After this is complete you can proceed with the remaining steps.
This all came about from Telstra being unwilling to repair my purple haze issue (which is clearly a sensor/camera module hardware defect) while having my bootloader unlocked/tampered. The purple haze issue occurred when my device was factory locked. I understand unlocking the boot loader voids warranty but this issue is hardware related which happens on stock software/firmware. I find it a little dishonest that HTC/Telstra want to charge me to have my unit replaced/repaired when it's a known hardware defect unless I am willing to go back through the process of making this device look like it's stock. I hope this can help some of the Telstra customers in the same position as RUU/Nandroids are almost non existent. Thank god for guru! ;)
[Q&A] [ROM][5.0.2][13 JAN] AICP Lollipop Unofficial[2.15/2.16 HBOOT] topic
Q&A for [ROM][5.0.2][13 JAN] AICP Lollipop Unofficial[2.15/2.16 HBOOT]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.0.2][13 JAN] AICP Lollipop Unofficial[2.15/2.16 HBOOT]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy! :)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.0.2][13 JAN] AICP Lollipop Unofficial[2.15/2.16 HBOOT]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy! :)
jeudi 12 février 2015
[Q] [HELP] Can't upgrade HBOOT to 3.19 topic
Hello, I'm trying to get the newest TWRP and CM 12 but I need HBOOT 3.19. Right now, I'm on 3.16.
I have S-Off
I've tried the firmware update from here: http://forum.xda-developers.com/htc-...401-6-t2899900 but I get FAILED (remote 41 model id check fail)
Am I applying it wrong? Is there a different one I should install?
I have TWRP. I don't want to put a stock rom on and update there, I just want to flash something.
Help would be greatly appreciated. Thanks!
I have S-Off
I've tried the firmware update from here: http://forum.xda-developers.com/htc-...401-6-t2899900 but I get FAILED (remote 41 model id check fail)
Am I applying it wrong? Is there a different one I should install?
I have TWRP. I don't want to put a stock rom on and update there, I just want to flash something.
Help would be greatly appreciated. Thanks!
Hboot 1.60 S-Off? topic
Is it possible to get S-Off on the new lollipop hboot or do you have to downgrade to get it, then flash lollipop without hboot?
mercredi 11 février 2015
[Q] relock/unroot HTC One M7, hboot 1.57 topic
Hi guys, hope you can help me out...
I just rooted my HTC One (unlock bootloader and install TWRP recovery), WITHOUT installing any custom ROM (i just kept the factory OS, because i couldn't S-Off the phone in order to install the google play edition). The OS i had (and still have) is stock Android 4.4.3 with Sense 6.
The problem is that i need to lock the phone back (in order to benefit from the warranty - technical touchscreen problem).
I tried using Revone to lock the phone back, but i get an error: "Failed to open framebuffer device". I understand that revone doesn't work with hboot 1.57.
Could you please help me with the relocking/unrooting the phone (at least give me a link to a guide that is working for my phone configuration - hboot 1.57) ? And also could you tell me if i need a RUU, or i can just wipe/reinstall the current OS (which i never changed in the first place) ? And if i need a RUU, how can i find the one that was initially installed on the phone ?
Oh, and one more thing: at first, when my phone started, i had a Vodafone screen showing up, and some crappy apps preinstalled. After i rooted an installed twrp recovery, i don't get that vodafone screen anymore, an the crappy apps weren't preinstalled anymore.
Cheers and thanks in advance !
I just rooted my HTC One (unlock bootloader and install TWRP recovery), WITHOUT installing any custom ROM (i just kept the factory OS, because i couldn't S-Off the phone in order to install the google play edition). The OS i had (and still have) is stock Android 4.4.3 with Sense 6.
The problem is that i need to lock the phone back (in order to benefit from the warranty - technical touchscreen problem).
I tried using Revone to lock the phone back, but i get an error: "Failed to open framebuffer device". I understand that revone doesn't work with hboot 1.57.
Could you please help me with the relocking/unrooting the phone (at least give me a link to a guide that is working for my phone configuration - hboot 1.57) ? And also could you tell me if i need a RUU, or i can just wipe/reinstall the current OS (which i never changed in the first place) ? And if i need a RUU, how can i find the one that was initially installed on the phone ?
Oh, and one more thing: at first, when my phone started, i had a Vodafone screen showing up, and some crappy apps preinstalled. After i rooted an installed twrp recovery, i don't get that vodafone screen anymore, an the crappy apps weren't preinstalled anymore.
Cheers and thanks in advance !
Inscription à :
Articles (Atom)