[Q] How to update from 4.3 to 4.4? - One (M7) Q&A, Help & Troubleshooting

Hello all,
I am new on this forum and i am total noob so I need Your help.
I have HTC One (m7). My phone was locked, and I send it to service to unlocked it to another network carrier. They unlocked it for me but recovery is now CWM 6.0.4.8. I want to update to 4.4 but OTA wont work. How to update to stock recovery and than update OTA? Or how to update with CWM? I found some tutorial on youtube how to change from cwm to twrp (because most of custom roms flash with twrp), but cmd saying some error. I only want 4.4 rom, stock or custom, it doesn't even matter to me. I read some threads but is just to complicated to me and I wont brick my phone. Thank You .
This is cmd error:
C:\Users\Intel\Desktop\recovery\platform-tools>fastboot devices
FA35LW909339 fastboot
C:\Users\Intel\Desktop\recovery\platform-tools>fastboot flash recovery openrecov
ery-twrp-2.7.0.0-m7.img
sending 'recovery' (9948 KB)...
OKAY [ 1.250s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.285s
C:\Users\Intel\Desktop\recovery\platform-tools>

What is your HBOOT version?
fastboot flash recovery openrecovvery works only on older HBOOTs (1.44 I think). You can flash a recovery by using the fastboot flash recovery recoveryname.img
Please refer to threads here: http://forum.xda-developers.com/showthread.php?t=2265618
or
http://forum.xda-developers.com/showthread.php?t=2173870
or
http://forum.xda-developers.com/showthread.php?t=2358738
BTW, if they unlocked the device for a different carrier, going back to stock will revert you the the original carrier before.

davebugyi said:
What is your HBOOT version?
fastboot flash recovery openrecovvery works only on older HBOOTs (1.44 I think). You can flash a recovery by using the fastboot flash recovery recoveryname.img
Please refer to threads here: http://forum.xda-developers.com/showthread.php?t=2265618
or
http://forum.xda-developers.com/showthread.php?t=2173870
or
http://forum.xda-developers.com/showthread.php?t=2358738
BTW, if they unlocked the device for a different carrier, going back to stock will revert you the the original carrier before.
Click to expand...
Click to collapse
'''''TAMPERED''''
'''''RELOCKED''''
M7_UL PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.44.0000
RADIO-4A.21.3263.04
OpenDSP-v.32.120.274.0909
eMMC-boot
May 3 2013, 17:22:59:1357
So if I want that phone stay unlocked I must flash custom rom?

Mpongr33 said:
'''''TAMPERED''''
'''''RELOCKED''''
M7_UL PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.44.0000
RADIO-4A.21.3263.04
OpenDSP-v.32.120.274.0909
eMMC-boot
May 3 2013, 17:22:59:1357
So if I want that phone stay locked I must flash custom rom?
Click to expand...
Click to collapse
Just follow [GUIDE] How to Return to 100% Stock, it has a link to RUU's. Going the RUU route will return you back to stock so you can run the OTA without trouble.

majmoz said:
Just follow [GUIDE] How to Return to 100% Stock, it has a link to RUU's. Going the RUU route will return you back to stock so you can run the OTA without trouble.
Click to expand...
Click to collapse
But if I flash stock, phone will bi locked to original carrier? I want to flash over this thread http://forum.xda-developers.com/showthread.php?t=2265618 but in section "Flashing custom recovery" saying Your bootloader needs to be "UNLOCKED". "LOCKED" or "RELOCKED" bootloaders can't flash custom recovery and mine phone saying RELOCKED...

Mpongr33 said:
But if I flash stock, phone will bi locked to original carrier? I want to flash over this thread http://forum.xda-developers.com/showthread.php?t=2265618 but in section "Flashing custom recovery" saying Your bootloader needs to be "UNLOCKED". "LOCKED" or "RELOCKED" bootloaders can't flash custom recovery and mine phone saying RELOCKED...
Click to expand...
Click to collapse
If you are set on your new carrier then you need to make sure that your MID is the same as the new carrier. You have SuperCID so you can flash any RUU. If you find your new carrier's RUU when you run it the end results will be stock in your new carrier. There is a tool that you can run to change your bootloader locked or unlock status to what you need it to be. Take a look at this guide (nkk71's SuperGUIDE to returning 100% back to stock) it will provide you with both background information and links. Once you get to stock in the carrier of your choice, update OTA then decide if you want to root, custom recovery and custom roms.

Mpongr33 said:
but in section "Flashing custom recovery" saying Your bootloader needs to be "UNLOCKED". "LOCKED" or "RELOCKED" bootloaders can't flash custom recovery and mine phone saying RELOCKED...
Click to expand...
Click to collapse
Recovery:
You need an unlocked bootloader if you want to flash recovery using the ''fastboot flash recovery name_of_recovery.img'' command
like @majmoz said, you can unlock/lock/relock bootloarder using the htc guru bootloader reset tool from custom recovery or via HTCdev.com
now for the RUU part:
because your phone is S-OFF you can flash any ruu (intended for your phone model only: M7_UL). You must make sure both your MID and CID match the ruu you want to use. CID can easily be changed using this command from bootloader:
Code:
fastboot oem writecid YOUR_CID [COLOR="Red"]<----- 8 characters exactly, in most cases, 2 underscores i.e HTC__001[/COLOR]
then you can change your MID (if required) using this tool from custom recovery.

Related

[Q] Stuck between Roms

I was flashing custom ROMs and accidentally soft-bricked my phone after attempting to go from an alpha Ice Cream Sandwich build to flashing the RUU of the official Sense 3.0 OTA (I know, stupid rookie mistake. I was tired). I tried fixing it, but so far have come up empty handed. The bootloader has just been unlocked through htcdev.com after multiple failed attempts and previously was S-OFF through AlphaRev's Revolutionary (S-ON => Revolutionary S-OFF => S-ON => HTCDEV unlock).
Bootloader reads:
VIVO PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-3822.10.08.28_M
eMMC-boot
Nov 1 2011,20:33:03
When I attempt to boot, it stays on the htc logo screen, then turns off and back on and into recovery.
Does anyone else have this problem or know how to solve it?
I'd like to flash the new RUU.
So far I've tried:
Flashing htc recovery so I can try flashing the RUUs again. No luck
I even modified the android-info.txt inside the RUUs.
I've tried the WWE RUU, the Asia HK RUU and the Asia WWE RUU (the guy from pakistan who posted in the general thread)
Should I be downgrading using a goldcard?
A goldcard is not for downgrading as such, its for flashing another carriers rom. So by all means, try flashing stock RUU with goldcard if you can't locate RUU from your carrier.
You mentioned trying to flash stock recovery but having no luck. With recovery or RUU after that?
Since you are in Canada, you probably have a IncS S710A/PG3212000 model. All of the 3.0x RUUs are for the PG3213000 model, so your only hope is that the unlocked bootloader is going to allow you to flash a modified PG32IMG.zip that has the android-info.txt file changed for modeled PG3212000.
I was able to do this with the 3.08.405.3 WWE RUU, but in my case I have permanent S-OFF via the XTC clip, so the real question is whether the 2.00.0000 unlocked HBOOT will allow you to flash a modified RUU ROM.zip or not. Good luck. You may just have to settle for custom ROMs.
Nonverbose said:
You mentioned trying to flash stock recovery but having no luck. With recovery or RUU after that?
Click to expand...
Click to collapse
I can flash the stock recovery all right by extracting recovery.img from the RUU.zip through fastboot. Sorry, I was unclear. I meant that flashing the RUUs through the bootloader still didn't work even after flashing the recovery. It's mentioned somewhere that you need the htc recovery to flash the RUU, and that it won't work with CWM.
tpbklake said:
Since you are in Canada, you probably have a IncS S710A/PG3212000 model. All of the 3.0x RUUs are for the PG3213000 model, so your only hope is that the unlocked bootloader is going to allow you to flash a modified PG32IMG.zip that has the android-info.txt file changed for modeled PG3212000.
Click to expand...
Click to collapse
Actually, I own a S710e/PG32130 model. I bought it from Taiwan, unlocked.
tpbklake said:
I was able to do this with the 3.08.405.3 WWE RUU, but in my case I have permanent S-OFF via the XTC clip, so the real question is whether the 2.00.0000 unlocked HBOOT will allow you to flash a modified RUU ROM.zip or not. Good luck. You may just have to settle for custom ROMs.
Click to expand...
Click to collapse
I tried the HK one first, because I thought it might be the one that Taiwan receives (Apparently the WWE was for European countries?). Anyways, that worked (sort of, that's how I got this updated Hboot and radio). Then I couldn't boot so I tried the other Asia WWE and the Euro WWE and neither will flash.
If the device is unlocked you can just extract the update zip file and flash it manually. Probably just needs boot.img
fastboot flash boot boot.img
(Although this depends on what exactly is unlocked and with what method,something your posts do not state)
Nonverbose said:
(Although this depends on what exactly is unlocked and with what method,something your posts do not state)
Click to expand...
Click to collapse
I mean I bought it off contract, for the full price of 500 dollars. There are no carrier markings on it either. I bought it from an independent shop, not from a carrier store.
Nonverbose said:
If the device is unlocked you can just extract the update zip file and flash it manually. Probably just needs boot.img
Click to expand...
Click to collapse
Do you mean extract the rom.zip from the RUU.exe, flash the rom.zip as PG32IMG.zip in the bootloader and then fastboot flash boot.img (extracted from PG32IMG.zip)? I've tried that, I'll try it again.
Thanks for the help by the way, and happy new year!
exaltedbladder said:
I mean I bought it off contract, for the full price of 500 dollars. There are no carrier markings on it either. I bought it from an independent shop, not from a carrier store.
Do you mean extract the rom.zip from the RUU.exe, flash the rom.zip as PG32IMG.zip in the bootloader and then fastboot flash boot.img (extracted from PG32IMG.zip)? I've tried that, I'll try it again.
Thanks for the help by the way, and happy new year!
Click to expand...
Click to collapse
Actually just meant the boot.img as there seems to be a common trend of it failing on this phone with symptoms of stopping at splash screen.
On that note when flashing img file in fastboot you need to specify the partition you wish to flash, which is missing in your post, it should read:
fastboot flash(command) boot(partition) boot.img(file)
Minus the brackets of course.
Happy new year to you also
Flashing the boot.img still isn't working. I've tried all three boot.imgs.
EDIT: I've been doing
"fastboot flash boot boot.img"
Flash a custom recovery and boot into it. Wipe cache, dalvik cache and do factory reset. Restart phone and give it 5-10 mins boot time in case its trying to rebuild dalvik cache
@tpbklake can you see what filesystem stock rom is using please
Nonverbose said:
Flash a custom recovery and boot into it. Wipe cache, dalvik cache and do factory reset. Restart phone and give it 5-10 mins boot time in case its trying to rebuild dalvik cache
@tpbklake can you see what filesystem stock rom is using please
Click to expand...
Click to collapse
The stock ROM uses EXT3 for the filesystem.
Nonverbose said:
Flash a custom recovery and boot into it. Wipe cache, dalvik cache and do factory reset. Restart phone and give it 5-10 mins boot time in case its trying to rebuild dalvik cache
Click to expand...
Click to collapse
I used CWM, and it's just like before. It shows the htc screen for around 10 seconds then reboots into recovery.
exaltedbladder said:
I used CWM, and it's just like before. It shows the htc screen for around 10 seconds then reboots into recovery.
Click to expand...
Click to collapse
Flash 4ext recovery so you can confirm that your partitions are formatted to the correct filesystem (ext3) I'm not 100% but I think ics may use ext4
Nonverbose said:
Flash 4ext recovery so you can confirm that your partitions are formatted to the correct filesystem (ext3) I'm not 100% but I think ics may use ext4
Click to expand...
Click to collapse
Yeah, great idea. I had a feeling it was to do with ICS. I'll get right on that.
Whelp, looks like they're all ext3 unfortunately.
exaltedbladder said:
Whelp, looks like they're all ext3 unfortunately.
Click to expand...
Click to collapse
OK, here is a thought after rereading your original post. You currently have HBOOT 2.00.0000 and it has been unlocked via HTCDEV.com, right?
In order to flash a RUU with HBOOT 2.00.0000 in place, it must be in a LOCKED/RELOCKED state. So one suggestion you could try is go into FASTBOOT mode and enter
fastboot oem lock
to relock and then try and run the Sense 3.0 RUU that you attempted in the first post.
tpbklake said:
OK, here is a thought after rereading your original post. You currently have HBOOT 2.00.0000 and it has been unlocked via HTCDEV.com, right?
In order to flash a RUU with HBOOT 2.00.0000 in place, it must be in a LOCKED/RELOCKED state. So one suggestion you could try is go into FASTBOOT mode and enter
fastboot oem lock
to relock and then try and run the Sense 3.0 RUU that you attempted in the first post.
Click to expand...
Click to collapse
Okay, it wasn't locked before. After issuing the command, the bootloader now says
*** RELOCKED ***
*** Security Warning ***
at the top. I tried flashing the PG32IMG.zip, but now it's giving me a CID error. I did getvar all to find out out my cidnum is HTC__621 while in the android-info.txt for the RUU it is HTC__622. Is it enough to edit the android-info.txts or do I need a goldcard or something else to flash the RUU? I'm going to try the other RUUs as well.
EDIT: I just checked all my RUUs. None of them are HTC__621. The closest is HTC__622. Yikes.
exaltedbladder said:
Okay, it wasn't locked before. After issuing the command, the bootloader now says
*** RELOCKED ***
*** Security Warning ***
at the top. I tried flashing the PG32IMG.zip, but now it's giving me a CID error. I did getvar all to find out out my cidnum is HTC__621 while in the android-info.txt for the RUU it is HTC__622. Is it enough to edit the android-info.txts or do I need a goldcard or something else to flash the RUU? I'm going to try the other RUUs as well.
EDIT: I just checked all my RUUs. None of them are HTC__621. The closest is HTC__622. Yikes.
Click to expand...
Click to collapse
Then you will need a goldcard to try and flash.
tpbklake said:
Then you will need a goldcard to try and flash.
Click to expand...
Click to collapse
All the guides I've found require me to install GoldCardHelper from the Android Market or to use adb. My phone doesn't work. Is there any other way to create a goldcard?
exaltedbladder said:
All the guides I've found require me to install GoldCardHelper from the Android Market or to use adb. My phone doesn't work. Is there any other way to create a goldcard?
Click to expand...
Click to collapse
Do you have another phone that you could use?
---------- Post added at 03:46 PM ---------- Previous post was at 03:31 PM ----------
tpbklake said:
Do you have another phone that you could use?
Click to expand...
Click to collapse
OK, so once again reading through this thread, here is what the current status of your phone is:
HBOOT 2.00.0000 RELOCKED
You can boot into HBOOT USB and FASTBOOT USB mode, right? There is currently no RUU for your CID, so a goldcard is needed.
When you were attempting to flash the boot.img files in FASTBOOT mode, the phone was in a LOCKED state, not the UNLOCKED state, right?
Since you can't boot the phone so you can use adb.exe plus the fact that zergRush cannot temp root HBOOT 2.00.0000 anyway, you could try going to HTCDEV.com and follow the unlock bootloader procedure to change HBOOT to UNLOCKED. Then you could retry flashing a boot_signed.img from the PG32IMG.zip file in FASTBOOT mode.

[Q] return to stock after rum runner

I am TMOB101 (the german t-mobile) i have successfully s-offed using rum runner.
There is no RUU for my phone as far as i know..
Is there a way to s-on again?
does rum runner backup my original hboot, so i can restore it to go back s-on?
Nomader0 said:
I am TMOB101 (the german t-mobile) i have successfully s-offed using rum runner.
There is no RUU for my phone as far as i know..
Is there a way to s-on again?
does rum runner backup my original hboot, so i can restore it to go back s-on?
Click to expand...
Click to collapse
You can flash the GuruReset ROM for your version: http://www.htc1guru.com/dld/guru_reset_m7_2-24-111-3-zip/
Make sure you choose to flash stock recovery and boot etc.
When all back to fully stock you are then safe to s-on again by issuing the following command: fastboot oem writesecureflag 3
Hope that comes in useful
Nomader0 said:
I am TMOB101 (the german t-mobile) i have successfully s-offed using rum runner.
There is no RUU for my phone as far as i know..
Is there a way to s-on again?
does rum runner backup my original hboot, so i can restore it to go back s-on?
Click to expand...
Click to collapse
Why do you need to s-on? And with s-off you can flash any RUU that you want. To s-on again, the command is "fastboot oem writesecureflag 3", but you need to be COMPLETELY stock before you do this, or you'll have a hard brick.
Sent from my iPod touch using Tapatalk
thank you for your answers.. I want to s-on to send back for warranty issues (purple tint).
I just want to understand how it works..
Rum runner installed an unsecured hboot. correct?
in order to s-off i need to go back to stock hboot first? people install RUU so they can install 1)stock rom, 2)stock radio, 3) stock recovery 4)stock hboot correct?
the Guru Reset rom just installs rom, recovery and radio (no hboot?)
can i just install any RUU and s-on? i thought i needed the one matching my phone
ok i found this http://www.htc1guru.com/guides/return-stock-guide/ and answered most of my questions.. except one:
As i said there is no RUU for me.. i will use a nandroid to restore most of the stuff. BUT there will be a mismatch between my stock Rom installed and the firmware (what is written in bootloader screen OS:XXXXXXX) How can i fix that?
can i just install the TMOB101 firmware from here http://android-revolution-hd.blogspot.gr/p/android-revolution-hd-mirror-site-var.html and fix the mismatch?
Nomader0 said:
ok i found this http://www.htc1guru.com/guides/return-stock-guide/ and answered most of my questions.. except one:
As i said there is no RUU for me.. i will use a nandroid to restore most of the stuff. BUT there will be a mismatch between my stock Rom installed and the firmware (what is written in bootloader screen OS:XXXXXXX) How can i fix that?
can i just install the TMOB101 firmware from here http://android-revolution-hd.blogspot.gr/p/android-revolution-hd-mirror-site-var.html and fix the mismatch?
Click to expand...
Click to collapse
Once you flash the guru reset, and then perform the OTA, you'll be on the same firmware after install.
Yeah but that will be different than the one my cid is supposed to have.. won't HTC service notice?

[Q] Can't unlock HTC One GPE that is RELOCKED

I bough a GPE HTC One from the Play store. I used HTC Dev to unlock it, had enjoyed custom roms and recoveries. I wanted to learn how to revert back to stock so before the 4.4 OTA update I relocked the bootloader and restored a stock recovery (not my own original).
I received the 4.4 OTA update yesterday and I attempted to unlock the bootloader once more. I used the original bin file and went through the steps to do it again but am met with the same results. I can at times get a successful unlock command in terminal, but not the screen that is supposed to appear and unlock the device.
I've seen some threads that sort of have the same problem but none that have resolutions that work for me. I've attempted flashing RUU's but am always met with signature verification failures. I've tried fastboot oem unlock but that doesn't work either.
Hoping someone might have an idea.
TAMPERED
RELOCKED
M7_UL PVT SHIP S-ON RH
HBOOT- 1.54.0000
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
OS-3.58.1700.5
eMMC-boot 2048MB
Nov 21 2013, 20:19:24.0
cid: GOOGL001
Misc:
HTC Sync manager installed then uninstalled
latest Android SDK installed for adb
debugging mode on
usb 2.0 on windows 7 x86
Hopefully someone with actual knowledge will come to help you, but why don't you try to S-off? that will give you more solution options.
Arjen_Arg said:
Hopefully someone with actual knowledge will come to help you, but why don't you try to S-off? that will give you more solution options.
Click to expand...
Click to collapse
From what I've been able to determine I'm unable to achieve S-OFF with HBOOT 1.54, or else I definitely would.
There are no RUU for GPE. The conversion RUU is not properly signed and was made from a system dump.
The GPE should be unlockable without a token or using htc dev.
fastboot oem unlock
what do you get?
You can't S-OFF on the GPE rom. you would have to flash a sense rom and then use rumrunner. You can't flash a different rom without unlocking and flashing a custom recovery...
msw141 said:
I bough a GPE HTC One from the Play store. I used HTC Dev to unlock it, had enjoyed custom roms and recoveries. I wanted to learn how to revert back to stock so before the 4.4 OTA update I relocked the bootloader and restored a stock recovery (not my own original).
I received the 4.4 OTA update yesterday and I attempted to unlock the bootloader once more. I used the original bin file and went through the steps to do it again but am met with the same results. I can at times get a successful unlock command in terminal, but not the screen that is supposed to appear and unlock the device.
I've seen some threads that sort of have the same problem but none that have resolutions that work for me. I've attempted flashing RUU's but am always met with signature verification failures. I've tried fastboot oem unlock but that doesn't work either.
Hoping someone might have an idea.
TAMPERED
RELOCKED
M7_UL PVT SHIP S-ON RH
HBOOT- 1.54.0000
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
OS-3.58.1700.5
eMMC-boot 2048MB
Nov 21 2013, 20:19:24.0
cid: GOOGL001
Misc:
HTC Sync manager installed then uninstalled
latest Android SDK installed for adb
debugging mode on
usb 2.0 on windows 7 x86
Click to expand...
Click to collapse
That's old information. There has been an S-Off exploit for 1.54 for over a month. I've done it on a GPE just like yours. Search for Rumrunner S-Off.
---------- Post added at 07:43 PM ---------- Previous post was at 07:35 PM ----------
ipfreelytech said:
You can't S-OFF on the GPE rom. you would have to flash a sense rom and then use rumrunner. You can't flash a different rom without unlocking and flashing a custom recovery...
Click to expand...
Click to collapse
This is wrong. You CAN S-OFF a GPE. Although you need root access or unlocked bootloader.
Do you have root?
Rumrunner S-Off http://rumrunner.us/
edit. answered in post above
ipfreelytech said:
There are no RUU for GPE. The conversion RUU is not properly signed and was made from a system dump.
The GPE should be unlockable without a token or using htc dev.
fastboot oem unlock
what do you get?
You can't S-OFF on the GPE rom. you would have to flash a sense rom and then use rumrunner. You can't flash a different rom without unlocking and flashing a custom recovery...
Click to expand...
Click to collapse
I try unlock but don't succeed. This is the result:
[PG_ERROR] htc_pg_part_traverse(839):
invalid traverse range
[PG_ERROR] htc_pg_part_read(1092):
htc_pg_part_traverse failed
[DISPLAY_ERR] sp_custom partition: unlock_disp_bu:img_buf read error!
[DISPLAY_ERR] Can not load custom splash!
Loading custom splash failed!
OKAY [ 0.537s]
finished. total time: 0.538s
Arjen_Arg said:
Do you have root?
Click to expand...
Click to collapse
No root, sadly. And probably can't get it with locked bootloader and s-on either.
interesting.
Last night just for fun I relocked the bootloader on my GPE converted AT&T one. I then attempted to unlock using fastboot oem unlock and got the exact same results. I suspected it had to do with my phone being converted instead of legit GPE and also having a custom splash screen.
I'm s-off so I just unlocked using a a few quick commands while booted.
Try re-flashing the firmware.zip from the 4.4 ota for good measure. that will re-write your hboot and recovery and other firmwares.
you can download here: https://mega.co.nz/#!DV0UEbBY!Vv6H4Ebf8WRCXrKwe5TGDUQqnvNk-9FiSjOvhjXAQvE
fastboot oem rebootRUU
fastboot flash zip 4.4 firmware.zip
fastboot flash zip 4.4 fimrware.zip
fastboot reboot-bootloader
then attempt unlock again.
msw141 said:
I try unlock but don't succeed. This is the result:
[PG_ERROR] htc_pg_part_traverse(839):
invalid traverse range
[PG_ERROR] htc_pg_part_read(1092):
htc_pg_part_traverse failed
[DISPLAY_ERR] sp_custom partition: unlock_disp_bu:img_buf read error!
[DISPLAY_ERR] Can not load custom splash!
Loading custom splash failed!
OKAY [ 0.537s]
finished. total time: 0.538s
Click to expand...
Click to collapse
ipfreelytech said:
Try re-flashing the firmware.zip from the 4.4 ota for good measure. that will re-write your hboot and recovery and other firmwares.
fastboot oem rebootRUU
fastboot flash zip 4.4 firmware.zip
fastboot flash zip 4.4 fimrware.zip
fastboot reboot-bootloader
then attempt unlock again.
Click to expand...
Click to collapse
Well the firmware flash worked just fine. But then I tried flashboot oem unlock and I got the same error as documented earlier. I even tried the HTCdev method again, got a successful result but no unlock screen.
So I'm still stuck on relocked. But I'm encouraged that your file was able to flash with no error. Do you think there might be more files I could attempt to flash in that manner that could help?
ipfreelytech said:
interesting.
Last night just for fun I relocked the bootloader on my GPE converted AT&T one. I then attempted to unlock using fastboot oem unlock and got the exact same results. I suspected it had to do with my phone being converted instead of legit GPE and also having a custom splash screen.
I'm s-off so I just unlocked using a a few quick commands while booted.
Try re-flashing the firmware.zip from the 4.4 ota for good measure. that will re-write your hboot and recovery and other firmwares.
you can download here: https://mega.co.nz/#!DV0UEbBY!Vv6H4Ebf8WRCXrKwe5TGDUQqnvNk-9FiSjOvhjXAQvE
fastboot oem rebootRUU
fastboot flash zip 4.4 firmware.zip
fastboot flash zip 4.4 fimrware.zip
fastboot reboot-bootloader
then attempt unlock again.
Click to expand...
Click to collapse
Hi @ipfreelytech
If fastboot oem unlock didn't work for you, how did you unlock the bootloader?
SaHiLzZ said:
Hi,
If fastboot oem unlock didn't work for you, how did you unlock the bootloader?
Click to expand...
Click to collapse
When I first got my phone I unlocked via that HTCdev method by betting the unlock_code.bin file and flashing it. I wasn't aware until today that there was a different method for GPE that didn't require that. The problem now is that the oem unlock doesn't work, and HTCdev method says it works but doesn't complete.
Yeah this a new issue that we are seeing being reported more and more after 4.4 GPE update.. Unfortuantely no fix yet.
SaHiLzZ said:
Yeah this a new issue that we are seeing being reported more and more after 4.4 GPE update.. Unfortuantely no fix yet.
Click to expand...
Click to collapse
OK, understood. What do you suggest I keep an eye out for on the forums?
A new S-OFF method for 1.54 with a locked bootloader...a new firmware update where it might work again...or updated drivers for the hardware/adb? Appreciate your input.
adb shell
su
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
more info here: http://forum.xda-developers.com/showthread.php?t=2470340
this only works if you're s off and have root
SaHiLzZ said:
Hi @ipfreelytech
If fastboot oem unlock didn't work for you, how did you unlock the bootloader?
Click to expand...
Click to collapse
Ah Ok, that is what Guru's bootloader zip is based on. Thanks!
ipfreelytech said:
adb shell
su
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
more info here: http://forum.xda-developers.com/showthread.php?t=2470340
this only works if your s off and have root
Click to expand...
Click to collapse
This method that you used to unlock and "relocked" phone, is there any way to do it with S-On? I had previously rooted, and am now stuck, as the others (I have been posting on other threads).
I'm wondering, hoping that there is line code like this one that would allow for us to recover our phones....
doubtful. s-off is required because your modifying a "black box" partition. The solutions used to gain s-off in the first place require using an exploit to write to that partition. What i posted is just directly modifying it using dd.
elisaw99 said:
This method that you used to unlock and "relocked" phone, is there any way to do it with S-On? I had previously rooted, and am now stuck, as the others (I have been posting on other threads).
I'm wondering, hoping that there is line code like this one that would allow for us to recover our phones....
Click to expand...
Click to collapse
SaHiLzZ said:
Yeah this a new issue that we are seeing being reported more and more after 4.4 GPE update.. Unfortuantely no fix yet.
Click to expand...
Click to collapse
Hi I'm replying to you on this original thread instead of starting a new one. I received the 4.4.2 OTA update this morning and I still cannot unlock bootloader, getting the same error messages as documented earlier in this thread.
I am checking to see if you've heard of any success stories for people on a stock GPE HTC One (s-on, relocked, no root) getting their bootloader to unlock after 4.4 or 4.4.2. I've checked the forums regularly but most other people seem to have root, s-off, or customer recovery which I have neither of.
msw141 said:
Hi I'm replying to you on this original thread instead of starting a new one. I received the 4.4.2 OTA update this morning and I still cannot unlock bootloader, getting the same error messages as documented earlier in this thread.
I am checking to see if you've heard of any success stories for people on a stock GPE HTC One (s-on, relocked, no root) getting their bootloader to unlock after 4.4 or 4.4.2. I've checked the forums regularly but most other people seem to have root, s-off, or customer recovery which I have neither of.
Click to expand...
Click to collapse
Im getting this same issue after updating to 4.4.2 after i got my phone back from repair. It is completely stock now and when i try to unlock the phone it wont show the screen that asks me if im sure i want to unlock my phone, which is the last step on the htcdev site.
Im thinking its a kitkat issue.

i'm a total htc noob (came from xperia to htc)

Hi guys! I just got my brand new htc one (m7) with this stock software:
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.63.708.3
eMMC-boot 2048MB
Oct 29 2013,17:34:05.0
HBOOT
Xperia's are easily rooted, deodexed, unlocked, re-locked, downgraded, etc. and if I want to revert to stock, i'll just flash stock FTF and return to warranty unlike HTC phones there's this hboot, s-off, etc. I read a lot of tutorials, noob guides, etc. but got confused on where to start. I just want root without unlocking bootloader or s-off and revert to stock when needed. Any tips guys? and how do you compare xperia development from htc's. Thanks guys.
cyrom said:
Hi guys! I just got my brand new htc one (m7) with this stock software:
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.63.708.3
eMMC-boot 2048MB
Oct 29 2013,17:34:05.0
HBOOT
Xperia's are easily rooted, deodexed, unlocked, re-locked, downgraded, etc. and if I want to revert to stock, i'll just flash stock FTF and return to warranty unlike HTC phones there's this hboot, s-off, etc. I read a lot of tutorials, noob guides, etc. but got confused on where to start. I just want root without unlocking bootloader or s-off and revert to stock when needed. Any tips guys? and how do you compare xperia development from htc's. Thanks guys.
Click to expand...
Click to collapse
you can only get temproot without unlocking the bootloader
the steps for your phone are
unlock bootloader @ htcdev.com
flash custom recovery (TWRP 2.6.3.3 preferred)
Make a Nandroid Backup
Flash SuperSU
reboot and enjoy
clsA said:
you can only get temproot without unlocking the bootloader
the steps for your phone are
unlock bootloader @ htcdev.com
flash custom recovery (TWRP 2.6.3.3 preferred)
Make a Nandroid Backup
Flash SuperSU
reboot and enjoy
Click to expand...
Click to collapse
so meaning to say, unlocking bootloader is a must, right?
cyrom said:
so meaning to say, unlocking bootloader is a must, right?
Click to expand...
Click to collapse
Yes if you want perm root
hello
cyrom said:
so meaning to say, unlocking bootloader is a must, right?
Click to expand...
Click to collapse
Yes,unlocking bootloader is must if you want to get permanent root.Further, if you want to return to complete stock in future,you should think about getting S-Off too.I have had a lot of problem because i can't get S-Off .But you should study before you do anything. Unlocking bootloader will result in loss of data/preload* apps which is a serious problem if you want to get future official OTA updates.If you unlock bootloader,u have to flash data/preload apps again if an official OTA update comes in near future. The most serious part is that the OTA updates check md5 of the apps intalled,so each app of data/preload must have the same md5 as before.But, if you are planning to use custom roms and you don't want official updates, that is not going to be a problem.There are several things that should be carefully studied before you do anything.I can give you a head start on what items to study.
1.check your CID ,mid,firmware version and note it.
2.Search OTA which matches your CID,mid and firmware version, it contains the stock recovery,data/preload apps which you may need in future.
3.Try to learn about S-ON/S-OFF, their uses and implications.
4.Do study about how OTA affects your chances to get S-OFF which you may need in future during serious problems.
5. try to read more and more through the forum, this is must.
Lastly,if you need comprehensive details on unlocking bootloader,flashing recovery,rooting and more, go through the video tutorials by "Sakitech" on youtube.I found them the most useful ones.And. last but not the least, this is all my opinion.Good luck!:good:
clsA said:
Yes if you want perm root
Click to expand...
Click to collapse
oh i see. btw i'm on 4.4.3 (6.13.708.1) and i can simply unlock my BL and get permroot but if i needed to revert to stock i can just flash 4.3 (3.63.708.3) via cmd and get 100% stock?
cyrom said:
oh i see. btw i'm on 4.4.3 (6.13.708.1) and i can simply unlock my BL and get permroot but if i needed to revert to stock i can just flash 4.3 (3.63.708.3) via cmd and get 100% stock?
Click to expand...
Click to collapse
only if you get s-off ... you can not flash a RUU lower than your current software version with s-on
The post above by @sudhirtripathee explains alot
thanks for posting that
@sudhirtripathee thanks mate! i found one stock ota zip for my firmware but it's 4.3 (out-of-the-box) not sure if it's safe to downgrade since im on 4.4.3 with S-ON. So yeah, I'll keep reading before a modify my m7.
cyrom said:
@sudhirtripathee thanks mate! i found one stock ota zip for my firmware but it's 4.3 (out-of-the-box) not sure if it's safe to downgrade since im on 4.4.3 with S-ON. So yeah, I'll keep reading before a modify my m7.
Click to expand...
Click to collapse
he mentions the OTA contains files you may need in the future ... it's of no use to you now your already above that version. When you unlock the bootloader your phone gets wiped and you loose (everything) a folder called data/preload
that's needed later to take a new OTA update. That folder can sometimes be retrieved from an old OTA package.
I know it seems confusing now but it will all be simple once you start doing it.
clsA said:
he mentions the OTA contains files you may need in the future ... it's of no use to you now your already above that version. When you unlock the bootloader your phone gets wiped and you loose (everything) a folder called data/preload
that's needed later to take a new OTA update. That folder can sometimes be retrieved from an old OTA package.
I know it seems confusing now but it will all be simple once you start doing it.
Click to expand...
Click to collapse
sudhirtripathee said:
Yes,unlocking bootloader is must if you want to get permanent root.Further, if you want to return to complete stock in future,you should think about getting S-Off too.I have had a lot of problem because i can't get S-Off .But you should study before you do anything. Unlocking bootloader will result in loss of data/preload* apps which is a serious problem if you want to get future official OTA updates.If you unlock bootloader,u have to flash data/preload apps again if an official OTA update comes in near future. The most serious part is that the OTA updates check md5 of the apps intalled,so each app of data/preload must have the same md5 as before.But, if you are planning to use custom roms and you don't want official updates, that is not going to be a problem.There are several things that should be carefully studied before you do anything.I can give you a head start on what items to study.
1.check your CID ,mid,firmware version and note it.
2.Search OTA which matches your CID,mid and firmware version, it contains the stock recovery,data/preload apps which you may need in future.
3.Try to learn about S-ON/S-OFF, their uses and implications.
4.Do study about how OTA affects your chances to get S-OFF which you may need in future during serious problems.
5. try to read more and more through the forum, this is must.
Lastly,if you need comprehensive details on unlocking bootloader,flashing recovery,rooting and more, go through the video tutorials by "Sakitech" on youtube.I found them the most useful ones.And. last but not the least, this is all my opinion.Good luck!:good:
Click to expand...
Click to collapse
So can you guys elaborate the safest steps on modding htc and return to a 100% stock. Thank you guys!
Sent from my HTC One using XDA Free mobile app
cyrom said:
So can you guys elaborate the safest steps on modding htc and return to a 100% stock. Thank you guys!
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
cyrom said:
So can you guys elaborate the safest steps on modding htc and return to a 100% stock. Thank you guys!
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
In my opinion, unlock your bootloader,intall custom recovery, and root. After you do all these steps, your device's bootloader menu will show tampered and unlocked flag.So, if you want to remove those flags in future, you will strictly need S-OFF. So, you could see how important is it to get S-OFF. Getting S-OFF gets harder as the hboot version of your phone increases and hboot version normally increases after official software update. In some cases, you will need to use premium apps like Moonshine to get S-OFF.So i advice you to unlock bootloader, intall custom recovery,root and then get S-OFF. Having all of them gives you entire freedom in modding. But, after having S-OFF, you will also need to be more responsible when you flash things. That's why, i told you to read as much as possible. If you want to do what i told you, follow these steps.
1.unlock bootloader, install custom recovery, and root.Link:http://www.youtube.com/watch?v=kJYAS2KN17Y
2.to get S-OFF, try: http://firewater-soff.com/instructions/
3. During the end of second step, if you get "Whelp it sucks,no amount of re-flashing custom roms and kernel will do", you will need moonshine to S-OFF. Since it is a premium app,AFAIK, you will need to pay 25$. But, before you pay, they will make sure whether or not will it work on you device.Link: http://forum.xda-developers.com/showthread.php?t=2291087, http://moonshine.io/
4.and to return back to 100% stock in future, this tutorial might help: http://forum.xda-developers.com/showthread.php?t=2358738
sudhirtripathee said:
In my opinion, unlock your bootloader,intall custom recovery, and root. After you do all these steps, your device's bootloader menu will show tampered and unlocked flag.So, if you want to remove those flags in future, you will strictly need S-OFF. So, you could see how important is it to get S-OFF. Getting S-OFF gets harder as the hboot version of your phone increases and hboot version normally increases after official software update. In some cases, you will need to use premium apps like Moonshine to get S-OFF.So i advice you to unlock bootloader, intall custom recovery,root and then get S-OFF. Having all of them gives you entire freedom in modding. But, after having S-OFF, you will also need to be more responsible when you flash things. That's why, i told you to read as much as possible. If you want to do what i told you, follow these steps.
1.unlock bootloader, install custom recovery, and root.Link:http://www.youtube.com/watch?v=kJYAS2KN17Y
2.to get S-OFF, try: http://firewater-soff.com/instructions/
3. During the end of second step, if you get "Whelp it sucks,no amount of re-flashing custom roms and kernel will do", you will need moonshine to S-OFF. Since it is a premium app,AFAIK, you will need to pay 25$. But, before you pay, they will make sure whether or not will it work on you device.Link: http://forum.xda-developers.com/showthread.php?t=2291087, http://moonshine.io/
4.and to return back to 100% stock in future, this tutorial might help: http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
thank you sir!
sorry for bumping this thread..
I think i've done enough reading so correct me if i'm wrong, just making sure before I touch my phone.
my current stock status:
**LOCKED**
M7-UL PVT SHIP S-ON RH
HBOOT - 1.57.0000
RADIO - 4T.28.3218.04
Open DSP - v32.120.274.0909
OS - 6.13.708.1
eMMc - boot 2048MB
Jul 22 2014, 20:59:16.0
Click to expand...
Click to collapse
To gain permanent root access:
I'm gonna need to unlock bootloader first;
Make a stock nandroid (with stock recovery intact via cmd fastboot boot recovery.img);
Install custom recovery and install SuperSU.zip
To revert to 100% stock:
I'm gonna be needing S-OFF. (i'm on 1.57 so I'm gonna search for it.)
flash my stock nandroid
flash stock recovery (if fastboot boot recovery.img didnt work)
lock recovery
fix tampered/relock flag
done.
Thanks!
cyrom said:
I think i've done enough reading so correct me if i'm wrong, just making sure before I touch my phone.
my current stock status:
To gain permanent root access:
1)I'm gonna need to unlock bootloader first; + 2)flash a custom recovery like TWRP
3)Make a stock nandroid (with stock recovery intact via cmd fastboot boot recovery.img); ---> fastboot boot recovery.img command only work on hboot 1.44 so you'll need to make a nandroid backup with the recovery installed on your phone which will overwrite your stock recovery.
Install custom recovery and 3)install SuperSU.zip
To revert to 100% stock:
I'm gonna be needing S-OFF. (i'm on 1.57 so I'm gonna search for it.) --> Firewater or Sunshine if firewater doesnt work.
flash my stock nandroid + flash back /data/preload folder (wiped when unlocking bootloader)
flash stock recovery (if fastboot boot recovery.img didnt work) If you can find your stock recovery somewhere (overwritten by the custom recovery)
lock recovery
fix tampered/relock flag ---> might come back if removed on hboot 1.55 and above
Click to expand...
Click to collapse
see above quote in blue
or
to revert to stock
flash the 2.24.708.4 RUU.zip which will also flash the stock recovery
remove flags etc etc
you might want to take a look at nkk71's guide to returning 100% stock (linked in my sig)
alray said:
see above quote in blue
or
to revert to stock
flash the 2.24.708.4 RUU.zip which will also flash the stock recovery
remove flags etc etc
Click to expand...
Click to collapse
Thanks! but is is ok to downgrade? my out of the box version was 3.63.708.3 i'll download it anyway.
cyrom said:
Thanks! but is is ok to downgrade? my out of the box version was 3.63.708.3 i'll download it anyway.
Click to expand...
Click to collapse
yes but downgrade only if needed (like to return to stock) You must have s-off to downgrade and use this RUU. Once downgraded you can take ota to re-update your phone.
alray said:
yes but downgrade only if needed (like to return to stock) You must have s-off to downgrade and use this RUU. Once downgraded you can take ota to re-update your phone.
Click to expand...
Click to collapse
thanks for the heads up. i thought id never find ruu zip for my version.
cyrom said:
thanks for the heads up. i thought id never find ruu zip for my version.
Click to expand...
Click to collapse
just confirm that the ruu match your MID and CID
CID and MID of the ruu can be found in the android-info.txt file of the ruu
alray said:
see above quote in blue
or
to revert to stock
flash the 2.24.708.4 RUU.zip which will also flash the stock recovery
remove flags etc etc
you might want to take a look at nkk71's guide to returning 100% stock (linked in my sig)
Click to expand...
Click to collapse
one more thing, if i flash the RUU.zip for my version, my current hboot (1.57) will also be downgraded to that version's hboot?
and will it be back to s-on (if i succeeded s-off now) ? thanks
cyrom said:
one more thing, if i flash the RUU.zip for my version, my current hboot (1.57) will also be downgraded to that version's hboot?
and will it be back to s-on (if i succeeded s-off now) ? thanks
Click to expand...
Click to collapse
yes hboot will also be downgraded. You will not loose s-off when flashing a ruu. Only turn s-on back if you must send the phone for warranty.

htc one m7 stuck at recovery mode with HBOOT: 1.61

M7 stuck in recvery mode in twrp mode, let me know the solution and the info of phone is given below
*** TAMPERED ***
*** UNLOCKED ***
M7_U PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T . 35. 3218. 16
OpenDSP-V35. 120. 274. 0718
OS-7. 21. 707. 105
eMMC-boot 2048MB
Mar 12 2015, 17:04:43.0
please guide me how to flash it or how to recover it, i will be highly oblidge to you
1. set ur botloader to relock
2. change ur cid to original
3. start RUU match with ur CID
deadcore said:
1. set ur botloader to relock
2. change ur cid to original
3. start RUU match with ur CID
Click to expand...
Click to collapse
could be you please explain it with link so that i can download file from link that you will provide and do the same as you says
mandeepsgh1 said:
M7 stuck in recvery mode in twrp mode, let me know the solution and the info of phone is given below
*** TAMPERED ***
*** UNLOCKED ***
M7_U PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T . 35. 3218. 16
OpenDSP-V35. 120. 274. 0718
OS-7. 21. 707. 105
eMMC-boot 2048MB
Mar 12 2015, 17:04:43.0
please guide me how to flash it or how to recover it, i will be highly oblidge to you
Click to expand...
Click to collapse
mandeepsgh1 said:
could be you please explain it with link so that i can download file from link that you will provide and do the same as you says
Click to expand...
Click to collapse
Either 7.21.707.105 or 7.21.707.121 will work. Check the sticky threads in the general section, You'll find a ruu collection thread with files + instructions.
alray said:
Either 7.21.707.105 or 7.21.707.121 will work. Check the sticky threads in the general section, You'll find a ruu collection thread with files + instructions.
Click to expand...
Click to collapse
as i searched on internet , there is a need of S-OFF to flash RUU file.
but there is S-ON on my htc one.
& i dont know how to make it S-OFF.
Please guide me for the same.
my bootloader is unlocked, but when i tried to put rom from "adb sideload abcs.zip" it show cannot read sideload.
and when i tried to select the rom from sdcard(internal storage) then it was at the end as set_metadata_changes_failed
i think this is due to S_ON.
please guide me to make it S-OFF
mandeepsgh1 said:
as i searched on internet , there is a need of S-OFF to flash RUU file.
but there is S-ON on my htc one.
& i dont know how to make it S-OFF.
Please guide me for the same.
Click to expand...
Click to collapse
You don't need s-off to flash a RUU, read the instructions of the RUU collection thread. S-OFF is only needed when you want to use a RUU to downgrade your phone or to convert to another carrier version. If flashing the same or newer version like 7.21.707.105 or 7.21.707.121, you don't need s-off.
my bootloader is unlocked
Click to expand...
Click to collapse
With s-on, you must re-lock the bootloader to flash a ruu, like said in the instructions.
but when i tried to put rom from "adb sideload abcs.zip" it show cannot read sideload.
and when i tried to select the rom from sdcard(internal storage) then it was at the end as set_metadata_changes_failed
i think this is due to S_ON.
please guide me to make it S-OFF
Click to expand...
Click to collapse
Are you taking about the RUU here? Or another rom you did not mentioned before? If you are talking about the RUU, it can't be flashed using a recovery, only using fastboot (read the instructions). If you are talking about a custom rom then it smost likely because you are using an outdated adb version or an outdated recovery version or a combination of both.
alray said:
You don't need s-off to flash a RUU, read the instructions of the RUU collection thread. S-OFF is only needed when you want to use a RUU to downgrade your phone or to convert to another carrier version. If flashing the same or newer version like 7.21.707.105 or 7.21.707.121, you don't need s-off.
With s-on, you must re-lock the bootloader to flash a ruu, like said in the instructions.
Are you taking about the RUU here? Or another rom you did not mentioned before? If you are talking about the RUU, it can't be flashed using a recovery, only using fastboot (read the instructions). If you are talking about a custom rom then it smost likely because you are using an outdated adb version or an outdated recovery version or a combination of both.
Click to expand...
Click to collapse
i tried with RUU version 7.21.707.121 , but when i tried to flash it by fastboot , it gives an error, " cannot allocate ROM.zip"
please guide me for stock or to put any custom ROM so that i can use my phone, it is being 5 days without my htc one.
please help
alray said:
You don't need s-off to flash a RUU, read the instructions of the RUU collection thread. S-OFF is only needed when you want to use a RUU to downgrade your phone or to convert to another carrier version. If flashing the same or newer version like 7.21.707.105 or 7.21.707.121, you don't need s-off.
With s-on, you must re-lock the bootloader to flash a ruu, like said in the instructions.
Are you taking about the RUU here? Or another rom you did not mentioned before? If you are talking about the RUU, it can't be flashed using a recovery, only using fastboot (read the instructions). If you are talking about a custom rom then it smost likely because you are using an outdated adb version or an outdated recovery version or a combination of both.
Click to expand...
Click to collapse
when i try to relock my htc one m7, with , "fastboot oem lock"
it shows me this:
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.239s
here, second last line show failed but on bootloader it shows me RELOCK
Is it going good or there is any issue???
alray said:
You don't need s-off to flash a RUU, read the instructions of the RUU collection thread. S-OFF is only needed when you want to use a RUU to downgrade your phone or to convert to another carrier version. If flashing the same or newer version like 7.21.707.105 or 7.21.707.121, you don't need s-off.
With s-on, you must re-lock the bootloader to flash a ruu, like said in the instructions.
Are you taking about the RUU here? Or another rom you did not mentioned before? If you are talking about the RUU, it can't be flashed using a recovery, only using fastboot (read the instructions). If you are talking about a custom rom then it smost likely because you are using an outdated adb version or an outdated recovery version or a combination of both.
Click to expand...
Click to collapse
thank you so much sir, today i tried with ruu 7.21.707.105, it is being successful believe me xda & you come as an "angel engineer". but thee is only one query from my side, is there any issue with tempered or relocked bootloader??

Categories

Resources