Hey guys
I've got a few questions here:
I want to ask if it is possible to convert my device into a Developer edition.
I want to set my device back to Stock so I have to use a RUU...Right?
I've already tried it but something had gone wrong.
I used this tutorial....but afterward I wasn't able to install the Ota-Update (4.4.2) (from 4.4 to 4.4.2)
My device is running on ARHD 52.0
Hboot 1.56
SuperCid
S-Off
Thanks in advance for your answers
Boachti said:
Hey guys
I've got a few questions here:
I want to ask if it is possible to convert my device into a Developer edition.
I want to set my device back to Stock so I have to use a RUU...Right?
I've already tried it but something had gone wrong.
I used this tutorial....but afterward I wasn't able to install the Ota-Update (4.4.2) (from 4.4 to 4.4.2)
My device is running on ARHD 52.0
Hboot 1.56
SuperCid
S-Off
Thanks in advance for your answers
Click to expand...
Click to collapse
can you please post you fastboot getvar all minus IMEI/Sn. I converted my phone several time so I can assist you with this.
Boachti said:
Hey guys
I've got a few questions here:
I want to ask if it is possible to convert my device into a Developer edition.
I want to set my device back to Stock so I have to use a RUU...Right?
I've already tried it but something had gone wrong.
I used this tutorial....but afterward I wasn't able to install the Ota-Update (4.4.2) (from 4.4 to 4.4.2)
My device is running on ARHD 52.0
Hboot 1.56
SuperCid
S-Off
Thanks in advance for your answers
Click to expand...
Click to collapse
Look, if your intention is to convert ur HTC One to a Dev. Edition, then you simply have to follow this guide:
http://forum.xda-developers.com/showthread.php?t=2541082
The RUU which you need to flash is:
http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-16-exe/
S-OFF is required, which you have already. However, you will keep a few things in mind:
1) Windows 7 must only be used. 8.1 is NOT supported
2) Depending on your phone, you may have to alter model and carrier id. Post your getvar all, for more assistance
3) Your HBOOT version will need a downgrade to 1.44. The method is mentioned in the guide
4) You cannot OTA update with a custom recovery. The guru reset rom and stock recovery are required for OTAs
raghav kapur said:
The guru reset rom and stock recovery are required for OTAs
Click to expand...
Click to collapse
What? That doesn't make any sense, if he flash a ruu his phone will be stock, no needs to flash a guru reset rom after....
+ he doesn't need to downgrade hboot to 1.44 if he use a ruu.zip instead of a ruu.exe like this one
so he will only need to change CID and MID (if required) before flashing the ruu.zip... simple as that.
To change CID:
Code:
fastboot oem writecid BS_US001
fastboot reboot-bootloader
TO change MID to PN0712000 use this tool with custom recovery:http://forum.xda-developers.com/showthread.php?t=2535365
then flash the ruu
Code:
fastboot oem rebootRUU
fastboot flash zip <name_of_ruu>.zip
fastboot flash zip <name_of_ruu>.zip
fastboot reboot
alray said:
What? That doesn't make any sense, if he flash a ruu his phone will be stock, no needs to flash a guru reset rom after....
+ he doesn't need to downgrade hboot to 1.44 if he use a ruu.zip instead of a ruu.exe like this one then windows 8.1 is supported (for the zip method) as said in the guide you linked
so he will only need to change CID and MID (if required) before flashing the ruu.zip... simple as that.
To change CID:
Code:
fastboot oem writecid BS_US001
fastboot reboot-bootloader
TO change MID to PN0712000 use this tool with custom recovery:http://forum.xda-developers.com/showthread.php?t=2535365
then flash the ruu
Code:
fastboot oem rebootRUU
fastboot flash zip <name_of_ruu>.zip
fastboot flash zip <name_of_ruu>.zip
fastboot reboot
Click to expand...
Click to collapse
What I meant was that the OTA cannot be installed on ARHD
And, ok, I wasn't aware that the HBOOT doesn't need to be downgraded through zip method
raghav kapur said:
What I meant was that the OTA cannot be installed on ARHD
Click to expand...
Click to collapse
ok
raghav kapur said:
And, ok, I wasn't aware that the HBOOT doesn't need to be downgraded through zip method
Click to expand...
Click to collapse
I wasn't aware of this too, nkk71 told me last week.
from nkk71's guide, look at the s-off column:
{
"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"
}
2) RUU.ZIP (Windows7, Mac, Linux): http://www.htc1guru.com/downloads/ruu-zip-downloads/ <- this is now the preferred method instead of RUU.EXE
Click to expand...
Click to collapse
no hboot downgrade require for the zip method as per his guide:
http://forum.xda-developers.com/showpost.php?p=47794203&postcount=3
Thank you very much
I will post getvar ass soon as I'm back home
Thanks
alray said:
can you please post you fastboot getvar all minus IMEI/Sn. I converted my phone several time so I can assist you with this.
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4A.22.3263.14
version-cpld: None
version-microp: None
version-main: 4.06.1540.3
version-misc: PVT SHIP S-OFF
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: 11111111
battery-status: good
battery-voltage: 3823mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bee46337
hbootpreupdate: 11
gencheckpt: 0
Boachti said:
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4A.22.3263.14
version-cpld: None
version-microp: None
version-main: 4.06.1540.3
version-misc: PVT SHIP S-OFF
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: 11111111
battery-status: good
battery-voltage: 3823mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bee46337
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
Change your CID to BS_US001:
boot your phone in bootloader, select fastboot and connect usb cable to computer. From your adb/fastboot folder, open a cmd prompt.
Code:
fastboot oem writecid BS_US001
fastboot reboot-bootloader
confirm your cid is now BS_US001:
Code:
fastboot oem readcid
the output should be BS_US001
Install latest TWRP recovery (you can skip this if your version is 2.6.3.0 and above)
download and save latest twrp to your adb/fastboot folder
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
boot phone in twrp recovery (main menu)
download this MID change tool and save it to you adb/fastboot folder push it to your sdcard
Code:
adb push MID_Change_1.01.zip /sdcard/
then in twrp menu select ''install'' and chose the MID_Change_1.01.zip
Follow graphical interface instruction and change MID to PN0712000
reboot phone in bootloader/fastboot usb mode
download this ruu.zip and save it to your adb/fasboot folder
flash the ruu
Code:
fastboot oem rebootRUU
fastboot flash zip <name_of_ruu_file>.zip
fastboot flash zip <name_of_ruu_file>.zip <------ do it again
fastboot reboot
boot phone normally, download and install ota.
Related
Hello,
i'm reading here for some weeks and this forum helped me much so far. Now I made a bad mistake while flashing the latest firmware on my One and it seems that I have bricked it.
What have I done?
I used ARHD 5.1 GE on my One with an older firmware. Before that I was using ARHD 4.1. Data of my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4260mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I changed to SuperCID, before that I had VODAP102. Bootloader is relocked.
After flashing latest firmware, my sdcard got wiped. So I have no backups or any other data on my phone. The phone stops booting after the white screen with the "HTC" logo and shows a turquoise color with little stripes and nothing happens.
I tried to flash another firmware, as you can see in the phone's details. That worked, but changed nothing. I can't install a rom, because adb doesn't find my device, but fastboot does. I tried several HTC-drivers and cables and USB-slots. Nothing.
I read several How-To's but I got stuck with this. Even tried to install the 1.28.401.7 RUU, but that stops with Error 155. After first time that error occured I relocked my bootloader, but that didn't help. I can't push files to the phone, because adb doesn't work.
Now only one thing left: Asking you for help. I'm somewhat frustrated.
Peko
pekomane said:
Hello,
i'm reading here for some weeks and this forum helped me much so far. Now I made a bad mistake while flashing the latest firmware on my One and it seems that I have bricked it.
What have I done?
I used ARHD 5.1 GE on my One with an older firmware. Before that I was using ARHD 4.1. Data of my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
I changed to SuperCID, before that I had VODAP102. Bootloader is relocked.
After flashing latest firmware, my sdcard got wiped. So I have no backups or any other data on my phone. The phone stops booting after the white screen with the "HTC" logo and shows a turquoise color with little stripes and nothing happens.
I tried to flash another firmware, as you can see in the phone's details. That worked, but changed nothing. I can't install a rom, because adb doesn't find my device, but fastboot does. I tried several HTC-drivers and cables and USB-slots. Nothing.
I read several How-To's but I got stuck with this. Even tried to install the 1.28.401.7 RUU, but that stops with Error 155. After first time that error occured I relocked my bootloader, but that didn't help. I can't push files to the phone, because adb doesn't work.
Now only one thing left: Asking you for help. I'm somewhat frustrated.
Peko
Click to expand...
Click to collapse
1- remove IMEI and s/n
2- install latest TWRP 2.6.3.3 (needed for 4.4 roms)
You need TWRP 2.6.3.3 (or later) for 4.4 roms, also if you are using a GPE rom, then you need to be s-off.
Download from here: http://techerrata.com/browse/twrp2/m7 don't use a download manager, it will fail; download normally and check MD5 to make sure file is not corrupt,
go to bootloader/FASTBOOT USB, and flash it:
fastboot flash openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
3- confirm adb working in TWRP now, and unlock using: http://forum.xda-developers.com/showthread.php?t=2475914 or "revone -u"
(you don't need to relock if you're s-off)
4- push, sideload, or OTG a ROM and install
5- error 155 occurs due to hboot 1.55+, you'll need to downgrade to 1.44 to run RUU
nkk71 said:
1- remove IMEI and s/n
2- install latest TWRP 2.6.3.3 (needed for 4.4 roms)
You need TWRP 2.6.3.3 (or later) for 4.4 roms, also if you are using a GPE rom, then you need to be s-off.
Download from here: http://techerrata.com/browse/twrp2/m7 don't use a download manager, it will fail; download normally and check MD5 to make sure file is not corrupt,
go to bootloader/FASTBOOT USB, and flash it:
fastboot flash openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
3- confirm adb working in TWRP now, and unlock using: http://forum.xda-developers.com/showthread.php?t=2475914 or "revone -u"
(you don't need to relock if you're s-off)
4- push, sideload, or OTG a ROM and install
5- error 155 occurs due to hboot 1.55+, you'll need to downgrade to 1.44 to run RUU
Click to expand...
Click to collapse
Step 1 already edited, right after posting...
Thanks for now, I have to try that when I am at home. I will post here, if it worked or not.
pekomane said:
Step 1 already edited, right after posting...
Thanks for now, I have to try that when I am at home. I will post here, if it worked or not.
Click to expand...
Click to collapse
no problem, IF you're gonna end up using RUU, you need to downgrade to this hboot: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
then go to bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip <- just in case the first one says "failed flush again"
fastboot reboot-bootloader
and run the RUU, should work fine.
nkk71 said:
no problem, IF you're gonna end up using RUU, you need to downgrade to this hboot: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
then go to bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip <- just in case the first one says "failed flush again"
fastboot reboot-bootloader
and run the RUU, should work fine.
Click to expand...
Click to collapse
Thanks for that, but using RUU was only one way I thought of to get my phone working again, because adb push and sideload don't work. If the way you mentioned in your first post works, then I will be absolutely fine without using RUU. Otherwise I will try the RUU option.
It worked! Thanks for your help! :good:
pekomane said:
It worked! Thanks for your help! :good:
Click to expand...
Click to collapse
Cool, if everything OK now, could you edit main thread title to include [SOLVED], Danke
Done.
By the way, it was the first option you posted that did the trick.
pekomane said:
Done.
By the way, it was the first option you posted that did the trick.
Click to expand...
Click to collapse
Sent from my HTC One using Tapatalk
Hello nkk7
S-OFF by rumrunners
bootloader 1.55
Version main 3.62.401.1
Cid HTC001
Mid pn0710000
I have tu use ruu to go back to stock can u please give me step by step guide in sequence pls
Pls
And there is no ruu for 3.62.401.1
Thus I will have downgrade that's why I am confused
Pls give me step by step info
shurahbil said:
Hello nkk7
S-OFF by rumrunners
bootloader 1.55
Version main 3.62.401.1
Cid HTC001
Mid pn0710000
I have tu use ruu to go back to stock can u please give me step by step guide in sequence pls
Pls
And there is no ruu for 3.62.401.1
Thus I will have downgrade that's why I am confused
Pls give me step by step info
Click to expand...
Click to collapse
follow my guide in my signature, there is a RUU.EXE available for CID: HTC__001 and MID: PN0710000 (so you can follow the RUU.EXE procedure)
in my opinion do NOT GO S-ON!!
nkk71 said:
follow my guide in my signature, there is a RUU.EXE available for CID: HTC__001 and MID: PN0710000 (so you can follow the RUU.EXE procedure)
in my opinion do NOT GO S-ON!!
Click to expand...
Click to collapse
Done ok ty
Why do not go s-on
Because you will close an avenue of troubleshooting if you are S-ON..
hi
i have htc one with :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.16
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
this steps i have follow:
for update from 1.44.0000 to 4.19.401.9
1.Type: fastboot oem lock (if your device is not relocked yet)
2.Type: fastboot oem rebootRUU and wait for device to reboot
3.Type: fastboot flash zip firmware.zip and wait for process to complete
4.Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
5.Type: fastboot flash zip firmware.zip and wait for process to complete
6.Type: fastboot reboot
troubles after the update :/
1/ i get msg from the battery that he is 4% and that is not right.
i be sure that he is 89% is full
2/ now he is bootlocked and cant get twrp2.6.3.3 on it
3/adb is not working only fastboot
question:
1/have i take the wrong firmware?
so yes where can i find the right firmware for 1.29.401.16
2/ how can i get back bootloader unlock in 4.19.401.9
3/ revone is that working under 4.19.401.9?
i have noidea what i need to do now
aater updation phone stuck
MRX_X said:
hi
i have htc one with :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.16
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
this steps i have follow:
for update from 1.44.0000 to 4.19.401.9
1.Type: fastboot oem lock (if your device is not relocked yet)
2.Type: fastboot oem rebootRUU and wait for device to reboot
3.Type: fastboot flash zip firmware.zip and wait for process to complete
4.Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
5.Type: fastboot flash zip firmware.zip and wait for process to complete
6.Type: fastboot reboot
troubles after the update :/
1/ i get msg from the battery that he is 4% and that is not right.
i be sure that he is 89% is full
2/ now he is bootlocked and cant get twrp2.6.3.3 on it
3/adb is not working only fastboot
question:
1/have i take the wrong firmware?
so yes where can i find the right firmware for 1.29.401.16
2/ how can i get back bootloader unlock in 4.19.401.9
3/ revone is that working under 4.19.401.9?
i have noidea what i need to do now
Click to expand...
Click to collapse
i am having the same problem with a twist. My HTC One duel sim was running on 4.2.2. It is not rooted and is on stock firmware. After updation, the phone is not booting and is stuck on HTC logo. I tried the Power+volume down method(which i read in some other thread) which reveals the bootloader is locked.How and why i dont know. Kindly guide me what to do. Please note that a noob altogather. Regards
MRX_X said:
hi
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
1.Type: fastboot oem lock (if your device is not relocked yet)
i have noidea what i need to do now
Click to expand...
Click to collapse
you don't need to lock bootloader to flash firmware when you are S-Off, those instructions are for S-On!!
Here download this:
fw_TWRP_2.6.3.3_1.26.401.3.zip 8.9 MB
https://mega.co.nz/#!6VcSlICK!lWPl1wgrah43yxom7mLkpPHi71kAXoSk-BdNpaTcxNc
MD5: BF37A63802EB37B37689DE08D133484F
fastboot oem rebootRUU
fastboot flash zip fw_TWRP_2.6.3.3_1.26.401.3.zip
fastboot reboot-bootloader
fastboot erase cache
-> enter recovery
use the following adb commands to unlock your bootloader: http://forum.xda-developers.com/showthread.php?t=2475914
PS: note that the above will change your version-main to 1.26.401.3 (referring to TWRP 2.6.3.3), only the displayed value not the actual firmware, once you flash another firmware, the "displayed" number will change again.
---------- Post added at 12:36 PM ---------- Previous post was at 12:31 PM ----------
asadkhattak said:
i am having the same problem with a twist. My HTC One duel sim was running on 4.2.2. It is not rooted and is on stock firmware. After updation, the phone is not booting and is stuck on HTC logo. I tried the Power+volume down method(which i read in some other thread) which reveals the bootloader is locked.How and why i dont know. Kindly guide me what to do. Please note that a noob altogather. Regards
Click to expand...
Click to collapse
Dual SIM is different that m7_u / ul models, please check Dual SIM threads.
nkk71 said:
you don't need to lock bootloader to flash firmware when you are S-Off, those instructions are for S-On!!
Here download this:
fw_TWRP_2.6.3.3_1.26.401.3.zip 8.9 MB
https://mega.co.nz/#!6VcSlICK!lWPl1wgrah43yxom7mLkpPHi71kAXoSk-BdNpaTcxNc
MD5: BF37A63802EB37B37689DE08D133484F
fastboot oem rebootRUU
fastboot flash zip fw_TWRP_2.6.3.3_1.26.401.3.zip
fastboot reboot-bootloader
fastboot erase cache
-> enter recovery
use the following adb commands to unlock your bootloader: http://forum.xda-developers.com/showthread.php?t=2475914
PS: note that the above will change your version-main to 1.26.401.3 (referring to TWRP 2.6.3.3), only the displayed value not the actual firmware, once you flash another firmware, the "displayed" number will change again.
---------- Post added at 12:36 PM ---------- Previous post was at 12:31 PM ----------
Dual SIM is different that m7_u / ul models, please check Dual SIM threads.
Click to expand...
Click to collapse
i have get the bootloader back in unlock via the link that you have give me.
than i have install TWRP than install the custom rom AR_HDone_52.0
and so far work everything good
thanks for fast respond
MRX_X said:
i have get the bootloader back in unlock via the link that you have give me.
than i have install TWRP than install the custom rom AR_HDone_52.0
and so far work everything good
thanks for fast respond
Click to expand...
Click to collapse
It's just my home-brew of TWRP 2.6.3.3 repackaged in a firmware zip to be able to flash in RUU mode :silly:
you may wanna reconsider reflashing your firmware though, just so your "fastboot getvar all" doesnt show version-main: 1.26.401.3 (a made up version number), the actual firmware is still whatever you flashed, but doesn't show up in the getvar.
the "version-main" is always, the last thing you flashed in ruu mode.
anyway, remember, you don't need to lock with s-off: http://forum.xda-developers.com/showpost.php?p=49832723&postcount=388
nkk71 said:
It's just my home-brew of TWRP 2.6.3.3 repackaged in a firmware zip to be able to flash in RUU mode :silly:
you may wanna reconsider reflashing your firmware though, just so your "fastboot getvar all" doesnt show version-main: 1.26.401.3 (a made up version number), the actual firmware is still whatever you flashed, but doesn't show up in the getvar.
the "version-main" is always, the last thing you flashed in ruu mode.
anyway, remember, you don't need to lock with s-off: http://forum.xda-developers.com/showpost.php?p=49832723&postcount=388
Click to expand...
Click to collapse
I have put your flash ruu in me collection ( have the time is right when i be troubles than i can use it )
MRX_X said:
I have put your flash ruu in me collection ( have the time is right when i be troubles than i can use it )
Click to expand...
Click to collapse
it's very easy to create yourself too, just get whatever recovery you want, rename to recovery.img + an "android-info.txt" with proper MID and CID, and you can even make your "version-main" 6.78.401.9 (as in 6789 but WWE) :silly: in the android-info.txt file (remember it's unix format not dos/windows).
obviously you need to be S-Off to flash it since it's completely unsigned.
only reason you would need it if you locked/relocked bootloader while S-Off, which is completely redundant... no need to lock/relock with s-off
hi
i restored my phone to flash a stock rom (RUU), i relocked my phone and now the RUU file wont flash . i`ve tested everything on the internet . but device is stuck on bootloader .
hboot 1.57
os version 6.09.4116466
m7 U
sorry for my bad english
volta22 said:
hi
i restored my phone to flash a stock rom (RUU), i relocked my phone and now the RUU file wont flash . i`ve tested everything on the internet . but device is stuck on bootloader .
hboot 1.57
os version 6.09.4116466
m7 U
sorry for my bad english
Click to expand...
Click to collapse
correct ruu ? Same or higher ?
see attached picture
yatindroid said:
correct ruu ? Same or higher ?
see attached picture
Click to expand...
Click to collapse
i couldn`t find same ruu.exe for this version . there is a higher one but its only for m7 UL .
there is a backup for my version, how can i flash that ? (does that even work ? )
------------------
link for same version back up
yadi.sk/d/rQzZ9i0CdmstQ
volta22 said:
i couldn`t find same ruu.exe for this version . there is a higher one but its only for m7 UL .
there is a backup for my version, how can i flash that ? (does that even work ? )
------------------
link for same version back up
yadi.sk/d/rQzZ9i0CdmstQ
Click to expand...
Click to collapse
there is no higher ruu for your phone till maybe you found dev edition Rom which won't flash to your phone
You should flash this backup and update it
yatindroid said:
there is no higher ruu for your phone till maybe you found dev edition Rom which won't flash to your phone
You should flash this backup and update it
Click to expand...
Click to collapse
how am i suppose to flash the backup with no recovery on the phone ?
command with cmd ( or adb ) ? please walk me trough im rookie
volta22 said:
how am i suppose to flash the backup with no recovery on the phone ?
command with cmd ( or adb ) ? please walk me trough im rookie
Click to expand...
Click to collapse
unlock the bootloader, flash twrp recovery, push the backup to your phone and restore it using twrp. Your phone is stuck in bootloader mode because you have re-locked it while it was still running custom software.
alray said:
unlock the bootloader, flash twrp recovery, push the backup to your phone and restore it using twrp. Your phone is stuck in bootloader mode because you have re-locked it while it was still running custom software.
Click to expand...
Click to collapse
i cant unlock the bootloader when i flash unlock.bin device reboots and it stuck in htc logo top of the screen entering recovery mode .
volta22 said:
when i flash unlock.bin device reboots and it stuck in htc logo top of the screen entering recovery mode .
Click to expand...
Click to collapse
Its because you have relocked the bootloader with a custom recovery installed. When unlocking the bootloader, the phone must perform a factory reset and its done from the stock recovery. Because the stock recovery isn't there, it doesn't work.
so you need to reflash the stock firmware first. What is the output of "fastboot getvar all" ? (dont post imei and serialno)
alray said:
Its because you have relocked the bootloader with a custom recovery installed. When unlocking the bootloader, the phone must perform a factory reset and its done from the stock recovery. Because the stock recovery isn't there, it doesn't work.
so you need to reflash the stock firmware first. What is the output of "fastboot getvar all" ? (dont post imei and serialno)
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.28.3218.04
version-cpld: None
version-microp: None
version-main: 6.09.401.111
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__J15
battery-status: good
battery-voltage: 3937mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0
volta22 said:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.28.3218.04
version-cpld: None
version-microp: None
version-main: 6.09.401.111
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__J15
battery-status: good
battery-voltage: 3937mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
download this firmware: https://yadi.sk/d/n7BAQ8vpdqPSS
save it in the same folder were you have adb and fastboot
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
then try to unlock the bootloader again, you might need to redo the whole htcdev procedure (getting e new unlock code)
alray said:
download this firmware: https://yadi.sk/d/n7BAQ8vpdqPSS
save it in the same folder were you have adb and fastboot
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
then try to unlock the bootloader again, you might need to redo the whole htcdev procedure (getting e new unlock code)
Click to expand...
Click to collapse
thank u sooooooooooooooooooo much . it worked . *_*
i unlocked the phone and installed TWRP recovery . device went back to same version i had totally ok .
now i can update to 5 by ota ?
I have tried to flash the ROM on my M7 with no luck. Just getting a boot. I have used a mates computer and didn't noticed his copy of Hasoons was for the M8 when I changed from TWRP to ClockWorkMod and now I can't get into recovery mode. That's a new problem. The old one is not being able to successfully flash the ROM.
***TAMPERED***
***UNLOCKED***
M7 UL PVT SHIP S-ON RH
HBOOT-1.61.000
OS-7.19.771.21
eMMC-boot 2048MB
adb devises doesn't show up anything anymore but the unit is recognized by Windows.
Thanks in advance. Any help or ideas would be much appreciated.
Out of Boot Loop
OK, I'm out of the boot loop now and just struggling to image the ROM, if nothing I install will not work and I manage to re-install the RUU, is that going to be all I can install?
humback said:
OK, I'm out of the boot loop now and just struggling to image the ROM, if nothing I install will not work and I manage to re-install the RUU, is that going to be all I can install?
Click to expand...
Click to collapse
What rom (name + version) are you trying to flash?
What recovery (name + version) are you using?
What is you "fastboot getvar all" ? (don't post imei / serialno)
alray said:
What rom (name + version) are you trying to flash?
What recovery (name + version) are you using?
What is you "fastboot getvar all" ? (don't post imei / serialno)
Click to expand...
Click to collapse
Hi thanks for your reply:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.771.21
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4158mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
humback said:
Hi thanks for your reply:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.771.21
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4158mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Since you only answered 1 of the 3 questions asked, the only thing I can suggest you is to relock your bootloader and flash the 7.19.771.21 RUU http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
alray said:
Since you only answered 1 of the 3 questions asked, the only thing I can suggest you is to relock your bootloader and flash the 7.19.771.21 RUU http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Click to expand...
Click to collapse
Sorry I didn't relise you asked the other questions, I have been using Hasoon2000 v3.1 and tried both CWM and TWRP. Also multiple ROMS including the reccomended stock one for the preivious carrier for HTCdev and a couple of the latest versions of kitkat and lollipop from this site.
Thanks.
humback said:
Sorry I didn't relise you asked the other questions, I have been using Hasoon2000 v3.1 and tried both CWM and TWRP. Also multiple ROMS including the reccomended stock one for the preivious carrier for HTCdev and a couple of the latest versions of kitkat and lollipop from this site.
Thanks.
Click to expand...
Click to collapse
I would suggest you to avoid using toolkits and instead work directly from a command window using the latest android sdk tools (fastboot and adb). Files that comes with these toolkits, like Hasoon 2000, are outdated.
E.g:
Hasoon 2000 v 3.1
Outdated SU binaries (1.45). Latest is 2.46 and is mandatory for lollipop roms.
Outdated TWRP recovery (2.6.0.1) - Latest twrp recovery for the M7 is 2.8.7.0, all roms requires at least 2.6.3.3, some other like Cyanogenmod requires at lest 2.7.1.1
Outdated CWM recovery (6.0.3.4) - latest cwm for M7 is 6.0.4.8
So setup your android sdk tool folder, download your custom recovery directly from TWRP or CWM website (twrp is preferred for the M7), flash the recovery using fastboot, copy the om to your phone and flash it in recovery.
humback said:
I bought this HTC last Saturday and it was on the 3 network with their software. I am on EE, my intention was to re-image the device with a non branded version O/S and get it unlocked to any network.
Click to expand...
Click to collapse
You need to be on the stock rom to sim unlock the phone so better to relock the bootloader, flash the ruu, unlock the sim using a sim unlock code, unlock the bootloader again and flash the rom you want to use.
alray said:
I would suggest you to avoid using toolkits and instead work directly from a command window using the latest android sdk tools (fastboot and adb). Files that comes with these toolkits, like Hasoon 2000, are outdated.
E.g:
Hasoon 2000 v 3.1
Outdated SU binaries (1.45). Latest is 2.46 and is mandatory for lollipop roms.
Outdated TWRP recovery (2.6.0.1) - Latest twrp recovery for the M7 is 2.8.7.0, all roms requires at least 2.6.3.3, some other like Cyanogenmod requires at lest 2.7.1.1
Outdated CWM recovery (6.0.3.4) - latest cwm for M7 is 6.0.4.8
So setup your android sdk tool folder, download your custom recovery directly from TWRP or CWM website (twrp is preferred for the M7), flash the recovery using fastboot, copy the om to your phone and flash it in recovery.
You need to be on the stock rom to sim unlock the phone so better to relock the bootloader, flash the ruu, unlock the sim using a sim unlock code, unlock the bootloader again and flash the rom you want to use.
Click to expand...
Click to collapse
So I need to use the stock, unlock the sim and then go back and use whatever ROM. That sounds good. Do you know where I could find the command I'm going to need and any examples. So far I only know how to use the all in one tools to move files.
humback said:
So I need to use the stock, unlock the sim and then go back and use whatever ROM. That sounds good. Do you know where I could find the command I'm going to need and any examples. So far I only know how to use the all in one tools to move files.
Click to expand...
Click to collapse
You can find the instructions how to flash the ruu in the link above but here it hus tin case:
lock the bootloader:
Code:
fastboot oem lock
flash the ruu:
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_H3G_UK_7.19.771.21_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430335_signed.zip
htc_fastboot reboot
Then boot the phone and inter your sim unlock code when prompted to after that the sim unlock will be permanent whatever rom you flash.
unlock the bootloader again (instructions at htcdev.com/bootloader):
Code:
fastboot oem get_identifier_token
fastboot flash unlocktoken Unlock_code.bin
then flash the custom recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
Then copy your rom to your phone storage and install it with your recovery.
Don't forget all files you want to flash (RUU, Recovery, Unlock_code) must be saved in the same folder you have adb, fastboot and htc_fastboot installed on your computer.
alray said:
You can find the instructions how to flash the ruu in the link above but here it hus tin case:
lock the bootloader:
Code:
fastboot oem lock
flash the ruu:
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_H3G_UK_7.19.771.21_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430335_signed.zip
htc_fastboot reboot
Then boot the phone and inter your sim unlock code when prompted to after that the sim unlock will be permanent whatever rom you flash.
unlock the bootloader again (instructions at htcdev.com/bootloader):
Code:
fastboot oem get_identifier_token
fastboot flash unlocktoken Unlock_code.bin
then flash the custom recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
Then copy your rom to your phone storage and install it with your recovery.
Don't forget all files you want to flash (RUU, Recovery, Unlock_code) must be saved in the same folder you have adb, fastboot and htc_fastboot installed on your computer.
Click to expand...
Click to collapse
I'm up to the flash zip and getting a error FAILED (remote 02 data lenth is to large) I took this file from the link above 1.6GB
humback said:
I'm up to the flash zip and getting a error FAILED (remote 02 data lenth is to large) I took this file from the link above 1.6GB
Click to expand...
Click to collapse
Are you using the fastboot version linked in the same thread from where you have downloaded the ruu? You must use that version of fastboot, the normal one that comes with the sdk tools can't handle big file like this ruu.
alray said:
Are you using the fastboot version linked in the same thread from where you have downloaded the ruu? You must use that version of fastboot, the normal one that comes with the sdk tools can't handle big file like this ruu.
Click to expand...
Click to collapse
No, I'll re download it when I get home, do I just replace that version in my folder with the other files as an exe?
humback said:
No, I'll re download it when I get home, do I just replace that version in my folder with the other files as an exe?
Click to expand...
Click to collapse
keep both fastboot version, save that one in the same folder as the original fastboot but name it htc_fastboot.exe so you have both fastboot version. When needed, type "htc_fastboot your_command" instead of "fastboot your_command" like when flashing the ruu:
Code:
fastboot oem rebootRUU
htc_fastboot flash zip ruu_file_name.zip
fastboot reboot
alray said:
keep both fastboot version, save that one in the same folder as the original fastboot but name it htc_fastboot.exe so you have both fastboot version. When needed, type "htc_fastboot your_command" instead of "fastboot your_command" like when flashing the ruu:
Code:
fastboot oem rebootRUU
htc_fastboot flash zip ruu_file_name.zip
fastboot reboot
Click to expand...
Click to collapse
Thanks alray, I'm back on stock. Just going to unlock the sim and reload a custom rom.
alray said:
keep both fastboot version, save that one in the same folder as the original fastboot but name it htc_fastboot.exe so you have both fastboot version. When needed, type "htc_fastboot your_command" instead of "fastboot your_command" like when flashing the ruu:
Code:
fastboot oem rebootRUU
htc_fastboot flash zip ruu_file_name.zip
fastboot reboot
Click to expand...
Click to collapse
All done, I got the phone unlocked for a couple of pounds on Ebay, and managed to install the RUU you suggested. Managed to update to a custom ROM today and everything is good. I did try to re-lock the bootloader and ran into another loop, so left it open for now with tampered and security warning for now. Apart from that it's all working fine. Thanks again for your help Alray.
hey,i received yesterday a htc one m7 from my cousin he sent it to me to take it to a specialist,the problem here he turned off his phone one night the next day he turned on his phone it got stuck in a bootloop he has twrp and bootloader unlocked,i tried flashing custom roms such as lineage os and RR based on cm 13 and android revolution the phone doesn't run any rom,but i can access twrp and hboot 1.55 anytime please help me with this and thank you.
This was "SOLVED" (special thank to alray),read below if you have the same issue goodluck.
Khalid47 said:
hey,i received yesterday a htc one m7 from my cousin he sent it to me to take it to a specialist,the problem here he turned off his phone one night the next day he turned on his phone it got stuck in a bootloop he has twrp and bootloader unlocked,i tried flashing custom roms such as lineage os and RR based on cm 13 and android revolution the phone doesn't run any rom,but i can access twrp and hboot 1.44 anytime please help me with this and thank you.
Click to expand...
Click to collapse
Please post the output of "fastboot getvar all" (do not post the imei number)
If the phone is still on hboot 1.44, the firmware might be to old to run newer roms. Also what version of twrp is installed on the phone?
okay
alray said:
Please post the output of "fastboot getvar all" (do not post the imei number)
If the phone is still on hboot 1.44, the firmware might be to old to run newer roms. Also what version of twrp is installed on the phone?
Click to expand...
Click to collapse
first thank you for replying,i just saw your comment in a htc one m7 topic i wished you would answer hah,okay btw correction the hboot is 1.55 sorry i wrote it wrong
fastboot getvar all gave me this :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.16.3250.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4241mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ea0bccbd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
twrp version: twrp-3.1.0-0-m7univ
alray said:
Please post the output of "fastboot getvar all" (do not post the imei number)
If the phone is still on hboot 1.44, the firmware might be to old to run newer roms. Also what version of twrp is installed on the phone?
Click to expand...
Click to collapse
please help with this problem today i flashed cm11 and it's the only rom that can boot but it saw "type password to decrypt storage" at least i can see the keyboard i saw some people in the forums saying format user data i tried but no success what should i do and can you tell me which firmware was this phone on so i can upgrade or whatever i'm on hboot 1.55 does that mean i can't flash 7.19 stock? and what is the difference between firmware that always has like 30 mbs or close and ruu zip
Khalid47 said:
please help with this problem today i flashed cm11 and it's the only rom that can boot but it saw "type password to decrypt storage" at least i can see the keyboard i saw some people in the forums saying format user data i tried but no success what should i do and can you tell me which firmware was this phone on so i can upgrade or whatever i'm on hboot 1.55 does that mean i can't flash 7.19 stock? and what is the difference between firmware that always has like 30 mbs or close and ruu zip
Click to expand...
Click to collapse
VODAP304 is firmware base x.xx.161.x. There is a recent ruu for this version (7.18.161.51). In order to flash this ruu, you'll probably have to update the firmware first (7.18.161.2 firmware).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
fastboot oem rebootRUU
htc_fastboot_flash zip PN07IMG_M7_UL_L50_SENSE60_MR_Vodafone_UK_7.18.161.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_459048_signed.zip
fastboot reboot
If your bootloader is unlocked you will need to relock it before doing the above commands. You can find htc_fastboot.exe here https://www.androidfilehost.com/?fid=24341993505161791
alray said:
VODAP304 is firmware base x.xx.161.x. There is a recent ruu for this version (7.18.161.51). In order to flash this ruu, you'll probably have to update the firmware first (7.18.161.2 firmware).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
fastboot oem rebootRUU
htc_fastboot_flash zip PN07IMG_M7_UL_L50_SENSE60_MR_Vodafone_UK_7.18.161.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_459048_signed.zip
fastboot reboot
If your bootloader is unlocked you will need to relock it before doing the above commands. You can find htc_fastboot.exe here https://www.androidfilehost.com/?fid=24341993505161791
Click to expand...
Click to collapse
i managed to get in cm11 now i can use cm11 but i want stock,the problem is i can't see main-version it's blank anyways
oem lock then flash firmware first then ruu zip? same method?
alray said:
VODAP304 is firmware base x.xx.161.x. There is a recent ruu for this version (7.18.161.51). In order to flash this ruu, you'll probably have to update the firmware first (7.18.161.2 firmware).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
fastboot oem rebootRUU
htc_fastboot_flash zip PN07IMG_M7_UL_L50_SENSE60_MR_Vodafone_UK_7.18.161.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_459048_signed.zip
fastboot reboot
If your bootloader is unlocked you will need to relock it before doing the above commands. You can find htc_fastboot.exe here https://www.androidfilehost.com/?fid=24341993505161791
Click to expand...
Click to collapse
Thank you so much, i managed to flash it after,i just realized i was flashing without firmware before and it was failing,you saved my cousins device thank you