Related
Hi guys..
"just check again in fastboot, ENG HBOOT version has changed to 6.98.2000 iirc. After running the RUU it should be 0.98.0000 again as ENG HBOOT can be overwritten in contrast to the AlphaRevX HBOOT. If you only want ENG HBOOT don't flash the RUU obviously"
This is what I read over at the thread on how to restore to default Rom and s-on...
But I don't get it...
I am currently on hboot 6.xxxxx and have the latest virtuous unity Rom installed.
I want to return to stock Europe Rom and the update to the latest sense 3 its from HTC. I don't want custom ROM anymore Which hboot do I need to flash? Can I flash the enghboot over my curent alpharevx hboot? Is there a risk of bricking? thanks
Just flash the coresponding RUU it will bring everything to stock, including hboot.
If the 6.xx.xxxx hboot really cannot be overwritten then flash this HBOOT
reboot to fastboot with debbuging ON
connect to PC
extract the hboot from the archive
rename it to hboot.img
open cmd
go to the folder where you have fastboot executable (android-sdk\...)
put the hboot there
type
Code:
fastboot devices
if the device is listed type
Code:
fastboot flash hboot hboot.img
fastboot reboot-bootloader
check the new version it has to be 0.98.2000
start your RUU on the PC
Wow thanks! +1
amidabuddha said:
Just flash the coresponding RUU it will bring everything to stock, including hboot.
If the 6.xx.xxxx hboot really cannot be overwritten then flash this HBOOT
reboot to fastboot with debbuging ON
connect to PC
extract the hboot from the archive
rename it to hboot.img
open cmd
go to the folder where you have fastboot executable (android-sdk\...)
put the hboot there
type
Code:
fastboot devices
if the device is listed type
Code:
fastboot flash hboot hboot.img
fastboot reboot-bootloader
check the new version it has to be 0.98.2000
start your RUU on the PC
Click to expand...
Click to collapse
tried this and got :
sending 'hboot' (1024 KB)...
OKAY [ 0.210s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.016s]
finished. total time: 0.226s
and my phone says : can not roll back hboot
my hboot version is 6.98.1002
i tried your guide through fastboot usb mode.
what am i doing wrong ? sorry for being noob or talking bad english :/
oLf06 said:
tried this and got :
sending 'hboot' (1024 KB)...
OKAY [ 0.210s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.016s]
finished. total time: 0.226s
and my phone says : can not roll back hboot
my hboot version is 6.98.1002
i tried your guide through fastboot usb mode.
what am i doing wrong ? sorry for being noob or talking bad english :/
Click to expand...
Click to collapse
It seems that your bootloader cannot be downgraded to the old version. So try to flash this one. Flash only the hboot.img, not the kernel and lib images that are in the same zip in this thread. I flashed a RUU on it without a problem. Let me know is it working
so i dont need to do the nandroid backup, just flash the hboot.img as described above?
oLf06 said:
so i dont need to do the nandroid backup, just flash the hboot.img as described above?
Click to expand...
Click to collapse
yes make a backup of course it will not harm You have to do backup before every eventually dangerous alteration of your system
okay... didnt made a backup ( because im not able to / different error, dont mind ) but i flashed the hboot.img from the thread using the above method. same output on my phone and in cmd. "(bootloader) image update is bypassed! " etc....
oLf06 said:
okay... didnt made a backup ( because im not able to / different error, dont mind ) but i flashed the hboot.img from the thread using the above method. same output on my phone and in cmd. "(bootloader) image update is bypassed! " etc....
Click to expand...
Click to collapse
Hey what errors?
Can you please explain, because the thread opener was asking for a guidance to return to stock. He has no errors and my method is for him.
If you have different situation please explain in details before doing anything on you device...
My problem is that i have the eMMc error :
E:cant mount cache etc....
i made the test and got no errors so the chip is not broken.
now i tried your method :
mke2fs /dev/block/mmcblk0p27
reboot recovery
. that runs without erros but clockwork still says "e:cant mount ..."
now i wanted to flash the hboot to 0.98 so i can use RUU ( with my hboot version it gets stuck at " restarting bootloader" or something like that.
But i am still not able to do that.
I spend the last 2 hours trying to flash the 4extrecovery without any success :/ can't flash with OneClick, installing the zip through recovery runs without errors but dont take effect. and the last 10 minutes i am watching the cmd window because i tried to flash the recovery using fastboot flash all i get is " writing 'recovery' "
edit: i am able to install a new rom ( virtous unity ) but my phone still stucks at the white HTC screen
do you have output on adb command? Try to flash the 2.00.2002 bootloader like in the linked thread I gave you above
EDIT: when you run the RUU there is a temp folder created on your C: drive. Open the Windows Explorer and search for the file rom.zip. Copy the file to another location. Extract it and try to flash the hboot included there
tried to flash the hboot from RUU ... still getting :
sending 'hboot' (1024 KB)...
OKAY [ 0.199s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.029s]
finished. total time: 0.287s
oLf06 said:
tried to flash the hboot from RUU ... still getting :
sending 'hboot' (1024 KB)...
OKAY [ 0.199s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.029s]
finished. total time: 0.287s
Click to expand...
Click to collapse
have you tried the adb command shell from recovery???
a) copy STOCK hboot.img from RUU to sdcard
b)reboot into recovery
b1)In cmd run the following commands (after each command press enter):
adb devices
adb shell
su
c)backup your hboot dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
d) flash new hboot dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
reboot to hboot and check your hboot version
tried this method and getting:
~ # dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
2048+0 records in
2048+0 records out
1048576 bytes (1.0MB) copied, 0.034664 seconds, 28.8MB/s
~ # dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
2048+0 records in
2048+0 records out
1048576 bytes (1.0MB) copied, 10.633719 seconds, 96.3KB/s
got this hboot.img from "RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed.exe"
hboot version still : 6.98.1002
edit : i cannot flash the 2.00.2002 bootloader like in the link you gave me because according to the instructions i have to make a nandroid backup. this is not possible for me because of the error " cant mount/data" . I cannot find this error at google.
sorry for my bad english by the way.....
oLf06 said:
hboot version still : 6.98.1002
edit : i cannot flash the 2.00.2002 bootloader like in the link you gave me because according to the instructions i have to make a nandroid backup. this is not possible for me because of the error " cant mount/data" . I cannot find this error at google.
sorry for my bad english by the way.....
Click to expand...
Click to collapse
It seems that your partition table is messed up and the system cannot find the necessary partitions. A bit dangerous suggestion but maybe you can try skipping the backup. And the RUU that you are using is quite old, try the 1.47.401.4 - it worked for me
format ALL your partitions in recovery.
Then go here http://forum.xda-developers.com/showthread.php?t=1113820
download the PG88IMG file from the 1st post.
open it on your pc and extract the hboot.img file to your desktop, then copy it to the root of your sd card.
connect phone vie adb again and enter the following commands, after each line press enter!
adb shell su
adb shell dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
adb shell dd if=/data/local/tmp/hboot.img of=/dev/block/mmcblk0p18
adb reboot bootloader
Then you are on OLD ENG HBOOT!
Eclipse_Droid said:
format ALL your partitions in recovery.
Click to expand...
Click to collapse
sorry about this noob question but what do you mean with ALL my partitions ?
wipe data/factory reset ?
wipe cache partition ?
format /cache ?
format /data ?
format /sdcard ?
format /system ?
should i do everything i mentioned above or am i missing something ?
oLf06 said:
sorry about this noob question but what do you mean with ALL my partitions ?
wipe data/factory reset ?
wipe cache partition ?
format /cache ?
format /data ?
format /sdcard ?
format /system ?
should i do everything i mentioned above or am i missing something ?
Click to expand...
Click to collapse
format in this order,
system
data
cache
then select wipe data factory reset.
then follow the rest of my guide
on some point this starts to be personal...
error formatting /system
error formatting /data
error formatting/cache
now i am making the factory reset,
trying to flash the hboot tomorrow.... but dont have much hope :/ Thank you guys for now for your great help ... maybe you have some more hints for me ..
general question here.. i am typing the commands when i am in recovery ( clockwork ) because this is how i can see my device when i type " adb devices " .. is this right or am i doing something generally wrong ?
EDIT:
adb shell dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
adb shell dd if=/data/local/tmp/hboot.img of=/dev/block/mmcblk0p18
Click to expand...
Click to collapse
am i right that this doenst make sense ? because "/data/local/tmp/hboot.img" doenst exist?
however ... it is not working again
EDIT 2 : okay.. i searched a bit on google and found out that there is a hboot driver i didnt install .. but my device still cant get listed... dont know why... maybe because usb debugging is not enabled ? how do i enable it in bootloadeR?
hi all new to this ..so my problem is i did the S off with the wire trick it worked but before it could completely reboot and do its thing em i lost my adb drivers so i had delete em and reinstall so unplugged phone before whole process and now im having worst time flashing recovery been at this for 6 hours now and no luck my fast-boot is working but cant flash Ive tried super utility, flashing thru fast-boot and installing zip on SD card with card reader nothing works help please i hope i made sense in this thread
yambo62274 said:
hi all new to this ..so my problem is i did the S off with the wire trick it worked but before it could completely reboot and do its thing em i lost my adb drivers so i had delete em and reinstall so unplugged phone before whole process and now im having worst time flashing recovery been at this for 6 hours now and no luck my fast-boot is working but cant flash Ive tried super utility, flashing thru fast-boot and installing zip on SD card with card reader nothing works help please i hope i made sense in this thread
Click to expand...
Click to collapse
okay try to download 4ext app the link is here:
http://www.4ext.net/get.php?apk
this will give you a recovery without flashing through adb
---------- Post added at 12:34 AM ---------- Previous post was at 12:32 AM ----------
or maybe you have not enabled usb debugging its under developer on the settings
As the post above says you can get 4EXT Recovery on your device , but first you will need an eng Hboot cause I think that is the cause of your problem. Got to the Unlimited.io website and click on downloads and down load the Hboot version for the pyramid and the version or Android you are using. Then use the following fastboot commands.
Code:
fastboot erase cache
fasboot rebootRUU
fastboot flash zip jb_hboot.zip
This should fix any fasboot issues or other ADB issues because all commands are usable with the eng Hboot.
well im stuck in the bootloader how would i use an .apk sorry if im a rookie and cant get to debug cuz i have nothing to boot off dam im not explaining it well i think lol
thx
T-Macgnolia said:
As the post above says you can get 4EXT Recovery on your device , but first you will need an eng Hboot cause I think that is the cause of your problem. Got to the Unlimited.io website and click on downloads and down load the Hboot version for the pyramid and the version or Android you are using. Then use the following fastboot commands.
Code:
fastboot erase cache
fasboot rebootRUU
fastboot flash zip jb_hboot.zip
This should fix any fasboot issues or other ADB issues because all commands are usable with the eng Hboot.
Click to expand...
Click to collapse
thx you i will try that .... having bad day cant even type or even get buy the image verification lol
almost
T-Macgnolia said:
As the post above says you can get 4EXT Recovery on your device , but first you will need an eng Hboot cause I think that is the cause of your problem. Got to the Unlimited.io website and click on downloads and down load the Hboot version for the pyramid and the version or Android you are using. Then use the following fastboot commands.
Code:
fastboot erase cache
fasboot rebootRUU
fastboot flash zip jb_hboot.zip
This should fix any fasboot issues or other ADB issues because all commands are usable with the eng Hboot.
Click to expand...
Click to collapse
well did what you said when i get to last step it gives me an error cannot load jb zip should i be placing the zip in my fastboot tools folder or something
yambo62274 said:
well did what you said when i get to last step it gives me an error cannot load jb zip should i be placing the zip in my fastboot tools folder or something
Click to expand...
Click to collapse
yes!!!
hboot
T-Macgnolia said:
As the post above says you can get 4EXT Recovery on your device , but first you will need an eng Hboot cause I think that is the cause of your problem. Got to the Unlimited.io website and click on downloads and down load the Hboot version for the pyramid and the version or Android you are using. Then use the following fastboot commands.
Code:
fastboot erase cache
fasboot rebootRUU
fastboot flash zip jb_hboot.zip
This should fix any fasboot issues or other ADB issues because all commands are usable with the eng Hboot.
Click to expand...
Click to collapse
not sure if matters my hboot is 1.27 S-OFF- LOCKED
asad510 said:
yes!!!
Click to expand...
Click to collapse
put the zip in folder now i get this error
C:\Program Files\Android\android-sdk\tools>fastboot flash zip jb_hboot.zip
sending 'zip' (353 KB)...
OKAY [ 0.274s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 0.614s
yambo62274 said:
not sure if matters my hboot is 1.27 S-OFF- LOCKED
Click to expand...
Click to collapse
Yes this means it does not allow all ADB and fastboot commands, this is why I mentioned the eng Hboot. It will say JuonutBear where it says LOCKED when you flash the eng Hboot.
---------- Post added at 07:45 PM ---------- Previous post was at 07:42 PM ----------
yambo62274 said:
put the zip in folder now i get this error
C:\Program Files\Android\android-sdk\tools>fastboot flash zip jb_hboot.zip
sending 'zip' (353 KB)...
OKAY [ 0.274s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 0.614s
Click to expand...
Click to collapse
Are you doing all three commands in the order I put them? Please don't take me being rude by asking just covering the bases.
T-Macgnolia said:
Yes this means it does not allow all ADB and fastboot commands, this is why I mentioned the eng Hboot. It will say JuonutBear where it says LOCKED when you flash the eng Hboot.
---------- Post added at 07:45 PM ---------- Previous post was at 07:42 PM ----------
Are you doing all three commands in the order I put them? Please don't take me being rude by asking just covering the bases.
Click to expand...
Click to collapse
so sorry misread your post i will try that thx you for your help sure youll hear from me again lol need a smoke been on this all day no lie UGHHHHH
T-Macgnolia said:
Yes this means it does not allow all ADB and fastboot commands, this is why I mentioned the eng Hboot. It will say JuonutBear where it says LOCKED when you flash the eng Hboot.
---------- Post added at 07:45 PM ---------- Previous post was at 07:42 PM ----------
Are you doing all three commands in the order I put them? Please don't take me being rude by asking just covering the bases.
Click to expand...
Click to collapse
yes i am and i know your not being rude i appreciate it very much you helping me but your telling me there is something else i have to download other than the jb hboot which is the eng hboot sorry for my inexperience lack of knowledge
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
format <partition> format 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
help show this help message
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. should i be using any of those commands ???
No you just need to download the Ub_hboot.zip, then place it in the tools folder or what ever folder your fasboot is in. Then boot uourdevice to bootloader and select fastboot and connect your device via USB to your computer. Then use the fastboot commands I posted.
T-Macgnolia said:
No you just need to download the Ub_hboot.zip, then place it in the tools folder or what ever folder your fasboot is in. Then boot uourdevice to bootloader and select fastboot and connect your device via USB to your computer. Then use the fastboot commands I posted.
Click to expand...
Click to collapse
k so once i see juopuntbear at top i can flash 4ext img fastboot methdood ?
yambo62274 said:
k so once i see juopuntbear at top i can flash 4ext img fastboot methdood ?
Click to expand...
Click to collapse
Yes that meansyou have the eng(engineered) Hboot which means it is UNLOCKED. You have to have a unlocked Hboot to use all the ADB and fastboot commands. But you have to be S-Off to flash the hboot, you are S-Off right? I ask cause some how you have missed installing it if you S-Offed with JuopunutBear S-Off.
T-Macgnolia said:
Yes that meansyou have the eng(engineered) Hboot which means it is UNLOCKED. You have to have a unlocked Hboot to use all the ADB and fastboot commands. But you have to be S-Off to flash the hboot, you are S-Off right? I ask cause some how you have missed installing it if you S-Offed with JuopunutBear S-Off.
Click to expand...
Click to collapse
nice finally did it thank you so much for your help i will buy you a beer tomorrow when my funds are deposited you have my word thank you so much i am S off and juopunutbear at top now just to flash the image fastboot i suppose
yambo62274 said:
nice finally did it thank you so much for your help i will buy you a beer tomorrow when my funds are deposited you have my word thank you so much i am S off and juopunutbear at top now just to flash the image fastboot i suppose
Click to expand...
Click to collapse
Yep just flash your recovery and you are good to go. Glad you got it worked out.
loving it
T-Macgnolia said:
Yep just flash your recovery and you are good to go. Glad you got it worked out.
Click to expand...
Click to collapse
thanks again buddy im loving this rom im running ***pegasus*** from Team Elegancia shout out to them for there great rom .....ill hit you up to buy you a beer soon
Welcome
I have a problem with downgrade HBOOT. While I entered:
Code:
adb push zergRush /data/local/tmp
it shows:mode.
Code:
C:\a3>adb push zergRush /data/local/tmp
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
I can't turn on phone in normal mode. Could sb help me?
I assume you've installed correct drivers for your version of windows,
if so, first let ADB find your device, ....then undertake next steps...
What wersion of android is currently iinstalled on your phone?
If ics, then you should seek to gain root access different way
I've heard ICS has been patched against zerg rush exploit ( still double check it )
Edit: i know the question may appear foolish but:
Is your device - by any chance - already rooted?
I was trying to install Android 4.2.2 downloaded from: http://forum.xda-developers.com/showthread.php?t=2171105
I have install from sd: Rom and Gaps and after rebot it show black screen.
Code:
*** UNLOCKED ***
SAGA PUT SHIP S-ON RL
HBOOT-2.02.0002
RADIO-3831.19.00.110
roman_kaczynski said:
I was trying to install Android 4.2.2 downloaded from: http://forum.xda-developers.com/showthread.php?t=2171105
I have install from sd: Rom and Gaps and after rebot it show black screen.
Click to expand...
Click to collapse
If you're htc dev unlocked then you have to flash boot.img (from the rom zip you've just flashed)
1. adb devices
2.adb reboot bootloader
3.fastboot devices
4. Fastboot flash boot boot.img
1. adb devices
Code:
C:\a3>adb devices
List of devices attached
C:\a3>
2.adb reboot bootloader
Code:
C:\a3>adb reboot bootloader
error: device not found
C:\a3>
3.fastboot devices
Code:
C:\a3>fastboot devices
HT13JTJ30235 fastboot
C:\a3>
4. Fastboot flash boot boot.img
Code:
C:\a3>fastboot flash boot boot.img
sending 'boot' (3354 KB)...
OKAY [ 0.563s]
writing 'boot'...
OKAY [ 0.663s]
finished. total time: 1.231s
C:\a3>
What I shoud to do now?
roman_kaczynski said:
1. adb devices
Code:
C:\a3>adb devices
List of devices attached
C:\a3>
2.adb reboot bootloader
Code:
C:\a3>adb reboot bootloader
error: device not found
C:\a3>
3.fastboot devices
Code:
C:\a3>fastboot devices
HT13JTJ30235 fastboot
C:\a3>
4. Fastboot flash boot boot.img
Code:
C:\a3>fastboot flash boot boot.img
sending 'boot' (3354 KB)...
OKAY [ 0.563s]
writing 'boot'...
OKAY [ 0.663s]
finished. total time: 1.231s
C:\a3>
What I shoud to do now?
Click to expand...
Click to collapse
Reboot and enjoy
this marvelous rom
Edit: by the way, are you sure you've installed
proper adb drivers?
In this mode your phone doesn'seem to be visible...
Fastboot is showing your device though
Yes, it's working, but I can't google play and I have problems with bluetooth: "Unfortunately, Bluetooth Share has stopped".
roman_kaczynski said:
Yes, it's working, but I can't google play and I have problems with bluetooth: "Unfortunately, Bluetooth Share has stopped".
Click to expand...
Click to collapse
If you're comming from a different base (sense rom for example)
it is always better to perform full wipe (all except sd card)
before flashing new rom (and kernel-boot.img)
If that would not resolve your issues,
you should ask in jelly fire bean rom thread for further support
Ok, thanks. I have another question. If I would like to install older version of Android (4.1.*) what I should to do now?
roman_kaczynski said:
Ok, thanks. I have another question. If I would like to install older version of Android (4.1.*) what I should to do now?
Click to expand...
Click to collapse
You can flash- at will- everything you want(- except RUU)
as long as you flash boot. img along with the rom of your choice
(boot.img belonging to that rom naturally, or compatible with)
Do not forget about full wipe,...it often saves us from headache...
Ok, but if I'm turning on Bootloader Mode, I can't get to RECOVERY. It turning on to normal mode. I would like to try install Android 4.2.1 or 4.1.*, because screen dims while I'm moving to settings, etc. Second problem is that I haven't got keyboard on 4.2.2 :cyclops:
EDIT: Now all working fine. If I would like to install Android 4.1.* I should download ROM and Gaps and follow instructions? And at the end: Fastboot flash boot boot.img?
In principle, yes...
In every rom thread you'll find
detailed instructions- how to flash it ...
You must read more
Thank you very much for help.
Regards
Could I install RUU ROM from this: http://forum.xda-developers.com/showthread.php?t=695667 now?
roman_kaczynski said:
Could I install RUU ROM from this: http://forum.xda-developers.com/showthread.php?t=695667 now?
Click to expand...
Click to collapse
No, because those are for a different device.
If I find RUU official for HTC Desire with Android 4.0.4? It will be ok?
roman_kaczynski said:
If I find RUU official for HTC Desire with Android 4.0.4? It will be ok?
Click to expand...
Click to collapse
No, you need desire s (saga) ruu's. You run a huge risk in bricking your device if you try anything else
Sent from my Desire S using Tapatalk 2
I have installed ROM from this: http://forum.xda-developers.com/showthread.php?t=2006392 and I have flash boot.img after install.
After reboot I have black screen.
roman_kaczynski said:
I have installed ROM from this: http://forum.xda-developers.com/showthread.php?t=2006392 and I have flash boot.img after install.
After reboot I have black screen.
Click to expand...
Click to collapse
I've not flashed it so i could be wrong here but i think it's an odexed rom and needs a bit more than just flashing the ROM and kernel. Could you try ice cream saga whilst i have a read, won't be for an hour or two though
Sent from my Desire S using xda premium
so that ROM will not work on my phone? http://forum.xda-developers.com/showthread.php?t=2006392
Sure I'm not mike1986. or a Dev, but it's not my first guide for this type of process. (N7 3G & TF300), and I've wrote this guide for help everyone who wants to unlock, rooting, flashing, restore back Stock his HTC One and use Fastboot easily.
Because If you have some problems for install or use the ADB Line commands, the simple way is to use Fastboot, that's why i've inserted this guide with all commands
You will find:
Post 1 => [TUTORIAL]Unlock - Flash Recovery - Rooting - S-OFF and Gets SUPERCID your HTC One
Post 2 => [GUIDE] Download HTC One M7 RUU - Restore back STOCK
Post 3 => HELP FOR FLASH MORE FASTER WHEN YOU USE FASTBOOT LINE COMMAND
Note: To access the Bootloader, Flash etc. mode on HTC One press your Power Button + Volume key
Click to expand...
Click to collapse
Requirements:
Click to expand...
Click to collapse
- AIO Toolkit for the One => from @hasoon2000
- SDK Platform
Or
- Fastboot files or Platform Tools
And
- recoverystock.img
Don't forget that you should need Android SDK Installed on your machine or you can download Fastboot Files or Platform Tools and install it on the root of your PC in one folder named "fastboot" or "platform tools".
Once your folder created and named "fastboot" or “platform tools”, extract the files into this folder.
{
"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"
}
1st Step:
Using the AIO from Hasoon2000 for the install of the drivers for your One
HOW TO UNLOCK YOUR ONE:
Click to expand...
Click to collapse
DON'T FORGET, USING HTCDEV UNLOCK WILL VOID YOUR WARRANTY!
The process by HTCDev for unlock your One
Go to HTCDev.com website
Register yourself
Click on Unlock Bootloader option
Select “All other supported Models” - not others
Follow the on-screen instructions and at the end your One will be unlocked
You will see [highlight]“UNLOCKED”[/highlight]
Click to expand...
Click to collapse
HOW TO FLASH THE RECOVERY FOR YOUR ONE
Click to expand...
Click to collapse
For the moment, we have some problems with different recoveries. The best way is to use this process:
Use the AIO for flashing the stock recovery from HTC (select your own recovery)
Once your stock recovery flashed, make a backup of your recovery.
Then it’s done, you can flash the recovery that you want (for my part it’s TWRP 2.5.0.0), don't forget to reboot to bootloader and don't wipe your phone
Code:
[B]C:\platform-tools>fastboot flash recovery recoverystock.img[/B]
Once your recovery flashed you will see in the bootloader above
[highlight]“UNLOCKED”[/highlight], [highlight]“TAMPERED”[/highlight]
Click to expand...
Click to collapse
HOW TO ROOT YOUR ONE
Click to expand...
Click to collapse
Just select "Perm root" to AIO Tool.
It’s really simple.
Reboot and try your root with an app as Titanium Backup.
You will may to update the binaries of SU.
HOW TO S-OFF YOUR ONE
Click to expand...
Click to collapse
If you want to S-OFF your One, it's useless to write again another guides because you will find here the both ways for S-OFF your One.
Note: if you're on Hboot 1.54 then s-off can't be achieved at the moment.
Click to expand...
Click to collapse
1 - [S-OFF] revone - DEVELOPER EARLY ACCESS PREVIEW EDITION by ieftm - and REVOLUTIONARY Team
2 - [S-OFF] Moonshine S-OFF - UPDATED -- WINDOWS SUPPORT ADDED by Fuses
HOW YOUR ONE GETS SUPERCID
Click to expand...
Click to collapse
1 - Open terminal/command prompt and type (copy paste command below or make sure that you have EIGHT 1's):
Code:
fastboot oem writecid 11111111
2 - Reboot your phone into bootloader mode (by typing: adb reboot bootloader) and verify CID#. It should look similar to this screenshot:
And now you can play with your subsonic phone:victory:
[GUIDE] Download HTC One M7 RUU - Restore back STOCK
[GUIDE] Download HTC One M7 RUU - Restore back STOCK
Find your HTC One M7 Rom Update Utility (RUU) is very useful if you need to restore back your device to Stock after any modification you’ve made. If you have rooted your One, unlocked its bootloader, installed custom recovery and roms and finally you want decided to getting back to official firmware and then to get or accept future OTA updates again. It’s the best way to restore back your device to Stock.
Coming back to stock is also useful if you have some bugs (for fixing it), Bootloop, stuck in boot screen logo and freeeeezzziiiinnnngggg, etc....
But before to going back to stock, you need to know :
Your bootloader will never be “LOCKED” again !!! You can’t restore it, just RELOCK it.
The “TAMPERED” text in your bootloader will only disappear after the flash of your RUU.
1 - Where I can can find the right RUU for my HTC One-M7 ?
First, you need to download the RUU that matches your device according to what carrier you have, hboot version, and baseband. The RUU will not run if it doesn’t match your device.
If you don’t know your One M7 variants, go to see the end of the post,
and this tread - HTC One variants [U/UL/WL]
But first download and install the necessary files prior to execute this properly. If you have already installed those files, just check theirs.
HTC Sync(Windows only)
Java Runtime Environment.
Android SDK | Android Developers.
Platform tools
Fastboot files
2 - Checking HTC One hboot and overall firmware version
If you already have this installed on your computer then proceed to checking your device info.
To find the correct firmware info of your device (modeid and cidnum), just simply run your device using the below fastboot command.
Hold the power button down until the phone power off.
Press Volume Down and Power to start the device into Bootloader mode.
Use the Volume buttons to select up or down. Highlight Fastboot and press the Power button.
Connect the device to the computer via a usb cable.
Run command prompt. ( Start > Run > type CMD).
Code:
C:\fastboot>fastboot devices
Code:
C:\fastboot>fastboot getvar all
You can read the whole logcat and get your device correct hboot and baseband version.
Download the right RUU for your HTC One from this thread :[COLLECTION] HTC M7 RUU, OTA, and Stock Nandroid Downloads
3 - Running HTC One M7 RUU
First make sure that your battery is fully charge 100%
If you are ready, you need to re-locked the bootloader before to going back to the RUU
Set the phone in fastboot mode (select fastboot from hboot menu), then plug-in USB cable.
Run the command prompt window, go to your fastboot directory
Enter the following commands:
Code:
fastboot devices
Code:
fastboot oem lock
It will then prompts you into a security warning and then relock your bootloader.
Now, you can boot your device into fastboot mode again,
Run the RUU.exe once your device is in fastboot USB mode.
Simply follow the RUU prompts, just wait and don’t unplug the phone until completely finishes.
The phone will reboots once completes and finally your phone should be on stock again.
RUU VARIANTS:
x.xx.61.x - Orange UK (United Kingdom)
x.xx.65.x - Orange CH (Switzerland)
x.xx.69.x - Orange PL (Poland)
x.xx.73.x - Orange FR (France)
x.xx.75.x - Orange ES (Spain)
x.xx.110.x - T-Mobile UK (United Kingdom)
x.xx.111.x - T-Mobile DE (Germany)
x.xx.112.x - T-Mobile AT (Austria)
x.xx.113.x - T-Mobile CZ (Czech Republic)
x.xx.118.x - T-Mobile PL (Poland)
x.xx.161.x - Vodafone UK (United Kingdom)
x.xx.163.x - Vodafone FR (France)
x.xx.165.x - Vodafone IT (Italy)
x.xx.166.x - Vodafone CH-DE (Switzerland - Germany)
x.xx.168.x - Vodafone GR (Greece)
x.xx.169.x - Vodafone AT (Austria)
x.xx.206.x - O2 UK (United Kingdom)
x.xx.207.x - O2 DE (Germany)
x.xx.401.x - World Wide English
x.xx.415.x - Arabic (UAE/Middle East)
x.xx.468.x - Turkey
x.xx.497.x - Morocco
x.xx.498.x - WWE Brightpoint US (United States)
x.xx.531.x - T-Mobile US (United Kingdom)
x.xx.666.x - Bell Canada
x.xx.707.x - Asia WWE (World Wide English)
x.xx.708.x - Asia HK (Hong Kong)
x.xx.709.x - Asia TW (Taiwan)
x.xx.720.x - Asia (India)
x.xx.728.x - Virgin AU (Australia)
x.xx.751.x - Chunghwa Telecom (Taiwan)
x.xx.771.x - Hutchison 3G UK (United Kingdom)
x.xx.841.x - Telsra WWE (World Wide English)
x.xx.862.x - Voda-Hutch AU (Australia)
x.xx.901.x - TIM IT (Italy)
x.xx.911.x - SK Telecom (South Korea)
x.xx.980.x - Optus AU (Australia)
x.xx.1400.x - HTC China
x.xx.1403.x - HTC China CMCC (China Mobile Communications Corporation)
x.xx.1540.x - HTC One U.S. Developer Edition
Thanks to mike1986 for this list
Fastboot & Platform Tool Guide
HELP FOR FLASH MORE FASTER WHEN YOU USE FASTBOOT LINE COMMAND
If you have got a problem with your adb or fastboot or recovery....it's very simply and faster
use this:
Download this zip file "Fastboot_files.zip" or this tool : platform-tools.zip - md5: 15e771613370afe3c70e0be1454d2ef1 - size: 346.8KB
Install this file somewhere in one folder which is named "fastboot" on your PC
=> disk C: root
Unzipped this file on the folder "fastboot" and you will find 3 files:
- adb.exe
- AdbWinApi.dll
- fastboot.exe
Click to expand...
Click to collapse
OR
Unzipped this file on the folder "platform-tools" and you will find 11 files:
- aapt
- adb
- AdbWinApi.dll
- AdbWinUsbApi.dll
- aidl
- dexdump
- llvm-rs-cc
- fastboot
- dx
- NOTICE
- source.properties
Click to expand...
Click to collapse
and when you need to push something by the bootloader, you can use it.
Don't forget to push on this folder the file that you need. For exemple: boot.img or a recovery.img, etc...
CD to where your fastboot or platform tools were installed
The line command is :
Code:
[B]C:\Users\R2D2>cd c:\platform-tools[/B]
Code:
[B]C:\platform-tools>fastboot flash recovery recovery.img[/B]
OR
Code:
[B]C:\Users\R2D2>cd c:\fastboot[/B]
Code:
[B]C:\fastboot>[/B]
Enter
Code:
[B]C:\fastboot>fastboot flash recovery recovery.img[/B]
Enter
If you want to flash the "recovery.img" file
******************************************************************
******************************************************************
If you want to know all lines of command
Code:
c:\fastboot>fastboot
Code:
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
help show this help message
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
OP and post 3 updated with some screenshots for a better help
I do that the same, but after flash Recovery i don't see “TAMPERED” so it's problem to root phone. Help me!
C:\platform-tools>fastboot.exe flash recovery recoverystock.img
sending 'recovery' (9562 KB)...
OKAY [ 1.208s]
writing 'recovery'...
OKAY [ 0.707s]
finished. total time: 1.919s
Flash successfull
phunghoang24 said:
I do that the same, but after flash Recovery i don't see “TAMPERED” so it's problem to root phone. Help me!
C:\platform-tools>fastboot.exe flash recovery recoverystock.img
sending 'recovery' (9562 KB)...
OKAY [ 1.208s]
writing 'recovery'...
OKAY [ 0.707s]
finished. total time: 1.919s
Flash successfull
Click to expand...
Click to collapse
It's not "C:\platform-tools>fastboot.exe flash recovery recoverystock.img
but it's : "C:\platform-tools>fastboot flash recovery recovery.img"
don't write the .exe for fastboot
try this and tell me
It's all working.
phunghoang24 said:
I do that the same, but after flash Recovery i don't see “TAMPERED” so it's problem to root phone. Help me!
Click to expand...
Click to collapse
Have you tried my previous post and is it okay for you now ?
I would like to know if users (apparently many- seen downloads) have encountered problems when using this tutorial.
Or do you think that it is good simply
philos64 said:
I would like to know if users (apparently many- seen downloads) have encountered problems when using this tutorial.
Or do you think that it is good simply
Click to expand...
Click to collapse
I have the same issue, it show:
after imput C:\platform-tools>fastboot flash recovery recoverystock.img
< waiting for device >
sending 'recovery' (9562 KB).
OKAY [ 1.203s]
writing 'recovery'...
OKAY [ 0.717s]
finished. total time: 1.921s
but I don't see “TAMPERED”:crying:
la_muerte said:
I have the same issue, it show:
after imput C:\platform-tools>fastboot flash recovery recoverystock.img
< waiting for device >
sending 'recovery' (9562 KB).
OKAY [ 1.203s]
writing 'recovery'...
OKAY [ 0.717s]
finished. total time: 1.921s
but I don't see “TAMPERED”:crying:
Click to expand...
Click to collapse
Reboot bootloader until u see tampered
Sent from my HTC One using xda premium
burton813 said:
Reboot bootloader until u see tampered
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
tried, no use
also flashed recovery couple times (tried: stock, CWM and TWRP), non of them work after reboot HBOOT, still cannot get into RECOVERY.
no TEMPERED on the screen:crying:
burton813 said:
Reboot bootloader until u see tampered
Click to expand...
Click to collapse
I will added asap for more clarify
[Edit] Added
Sent from my N7 3G with DroiDevs premium between sky and earth.
la_muerte said:
tried, no use
also flashed recovery couple times (tried: stock, CWM and TWRP), non of them work after reboot HBOOT, still cannot get into RECOVERY.
no TEMPERED on the screen:crying:
Click to expand...
Click to collapse
No, this process works because a lot of users have used it.
Are you unlocked ? You can see unlocked when you are bootloder.
Where are your recoverystock file .img ? normally in the platform tools or fastboot folder (look pics)
Can you explain what have you make ?
philos64 said:
No, this process works because a lot of users have used it.
Are you unlocked ? You can see unlocked when you are bootloder.
Where are your recoverystock file .img ? normally in the platform tools or fastboot folder (look pics)
Can you explain what have you make ?
Click to expand...
Click to collapse
Thanks for the help!
But I think I know why the RECOVERY won't work.
Because I have BRANDED htc one.
cid: H3G__106
H3G (3 Austria)
Code:
fastboot getvar version-main
version-main: 1.28.771.6
finished. total time: -0.000s
so I need to find the right version of STOCK RECOVERY IMAGE
1.28.771.6 - Hutchison 3G UK (United Kingdom)
and flash it first!
Just like the steps to unlock AT&T branded htc one.
la_muerte said:
Thanks for the help!
But I think I know why the RECOVERY won't work.
Because I have BRANDED htc one.
cid: H3G__106
H3G (3 Austria)
Code:
fastboot getvar version-main
version-main: 1.28.771.6
finished. total time: -0.000s
so I need to find the right version of STOCK RECOVERY IMAGE
1.28.771.6 - Hutchison 3G UK (United Kingdom)
and flash it first!
Just like the steps to unlock AT&T branded htc one.
Click to expand...
Click to collapse
Lol.. If it's branded by your carrier, I cannot do nothing for this part.
But you're Unlocked without problem ?
philos64 said:
...Are you unlocked ? You can see unlocked when you are bootloder.
...
Click to expand...
Click to collapse
Yes! I can see *** UNLOCKED *** on my bootloader screen, but just cannot get into Recovery Mode.
la_muerte said:
Yes! I can see *** UNLOCKED *** on my bootloader screen, but just cannot get into Recovery Mode.
Click to expand...
Click to collapse
If I find something about this problem with One Branded, I tell you
la_muerte said:
Yes! I can see *** UNLOCKED *** on my bootloader screen, but just cannot get into Recovery Mode.
Click to expand...
Click to collapse
follow this guide and install supeboot zip
http://www.ibtimes.co.uk/articles/4...-install-clockworkmod-recovery-android422.htm
then with hanson all in one flash CWR , done
la_muerte said:
Yes! I can see *** UNLOCKED *** on my bootloader screen, but just cannot get into Recovery Mode.
Click to expand...
Click to collapse
About the install of the recovery, you're UNLOCKED so you can flash a recovery even if you're branded by your carrier.
When you write your command lines which name write you for your recovery ?
Don't forget to write the same name as your recovery name in your your folder: Look screens of the OP
stesa said:
follow this guide and install supeboot zip
http://www.ibtimes.co.uk/articles/4...-install-clockworkmod-recovery-android422.htm
then with hanson all in one flash CWR , done
Click to expand...
Click to collapse
Why giving the link for a another guide to a another website, your post is completly useless.
Please respect all OP who writes guides for helping xda members !!!!!
Thanks
please help. I cannot get Super CID 11111111. I have done this before, but when I sent my phone to HTC my CID is now T-MOB010. I have done this before I sent my One S to HTC, but when I am trying again, it does not work. I do the steps EXACTLY as told. I did it multiple times too. I have my bootloader unlocked with TWRP 2.3.3. and my mmcblk0p4MOD already has 11111111 and same size as mmcblk0p4. what is going wrong?
aloy1455 said:
please help. I cannot get Super CID 11111111. I have done this before, but when I sent my phone to HTC my CID is now T-MOB010. I have done this before I sent my One S to HTC, but when I am trying again, it does not work. I do the steps EXACTLY as told. I did it multiple times too. I have my bootloader unlocked with TWRP 2.3.3. and my mmcblk0p4MOD already has 11111111 and same size as mmcblk0p4. what is going wrong?
Click to expand...
Click to collapse
Why do you want to S-Off?
Sent from my Nexus 7 using Tapatalk HD
HTC has probably set that partition to read only, so your only way to scid is to use moonshine s-off. And when you are s-off, you can use the command fastboot OEM writecid 11111111 to get scid.
First check that you are on the correct firmware to use moonshine.
Sent from my One S using Tapatalk 4
El_Svanto said:
HTC has probably set that partition to read only, so your only way to scid is to use moonshine s-off. And when you are s-off, you can use the command fastboot OEM writecid 11111111 to get scid.
First check that you are on the correct firmware to use moonshine.
Sent from my One S using Tapatalk 4
Click to expand...
Click to collapse
thank you
El_Svanto said:
HTC has probably set that partition to read only, so your only way to scid is to use moonshine s-off. And when you are s-off, you can use the command fastboot OEM writecid 11111111 to get scid.
First check that you are on the correct firmware to use moonshine.
Sent from my One S using Tapatalk 4
Click to expand...
Click to collapse
do I have to use moonshine, or do can I use facepalm
You can not use facepalm, because it needs scid first.
Sent from my One S using Tapatalk 4
El_Svanto said:
You can not use facepalm, because it needs scid first.
Sent from my One S using Tapatalk 4
Click to expand...
Click to collapse
okay, so I successfully moonshined my One S. it is now S-Off, but I want to super CID. can you direct me to how to properly Super CID while on moonshine? is there any backfires doing this?
Sure. Boot to fastboot. Make Sure it says Fastboot USB. Open command prompt in your fastboot folder. Write command: fastboot OEM writecid 11111111. Done.
The only thing to think of is not to do an OTA update of a stock ROM when you are scid. It could hard brick your phone.
Sent from my One S using Tapatalk 4
El_Svanto said:
Sure. Boot to fastboot. Make Sure it says Fastboot USB. Open command prompt in your fastboot folder. Write command: fastboot OEM writecid 11111111. Done.
The only thing to think of is not to do an OTA update of a stock ROM when you are scid. It could hard brick your phone.
Sent from my One S using Tapatalk 4
Click to expand...
Click to collapse
thank you very much
El_Svanto said:
Sure. Boot to fastboot. Make Sure it says Fastboot USB. Open command prompt in your fastboot folder. Write command: fastboot OEM writecid 11111111. Done.
The only thing to think of is not to do an OTA update of a stock ROM when you are scid. It could hard brick your phone.
Sent from my One S using Tapatalk 4
Click to expand...
Click to collapse
I just tried, and that command did not do anything.
C:\Users\Aloy\Desktop\One_S_All-In-One_Kit_v3.5\Data>fastboot OEM writecid 11111
111
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
format <partition> format 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
help show this help message
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
NP. Hit the thanks button
I also would like to add that now when you are s-off, be careful what you flash. Don't mess with hboots and stuff. If you lose your hboot, you are f...ed!
Sent from my One S using Tapatalk 4
---------- Post added at 10:03 PM ---------- Previous post was at 09:36 PM ----------
aloy1455 said:
I just tried, and that command did not do anything.
C:\Users\Aloy\Desktop\One_S_All-In-One_Kit_v3.5\Data>fastboot OEM writecid 11111
111
usage: fastboot [ <option> ] <command>
Click to expand...
Click to collapse
Strange. I have done it on mine. Try typing oem in letters instead of caps.
Sent from my One S using Tapatalk 4
Wrong place