Related
Hey I was hoping that someone here would be able to help.
Ive been trying for get s-off on my device, I have tried everything but it dosent wnat to work. I am probably missing something basic.
I have a GPE HTC one that I until recently used with RevolutionHD 30 (Sense version).
Now that 4.4 is out I want to flash that, but every rom seems to require s-off.
Being that my Hboot version is 1.54, i understand that my only option to s-off is using rumrunner.
I have tried to rumrunner a number of times:
Using a windows machine
Using a Linux machine
I have tried both wirh the following roms: CM 10.2, CM 11, ADR 30
But I cant seem to have any luck. On both machines I alwasy get stuck at the same place:
HTML:
Please wait....
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (17/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[************************************************************]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: Download updated package at www.rumrunner.us
I dont know if it helps but "fastboot getvar mainver" alwasy rettuns blank.
I tried to log onto the rumrunner irc, but it looks to be empty.
Is their anything that I can do?
Please tell me your cid and your model id and I 'll guide you
Sent from my HTC One using Tapatalk
Thanks,
Cid num: GOOGL001
Model id: PN0712000
Just in case fastboot getvar all output:
HTML:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36JW913072
(bootloader) imei: *******************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4313mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s
AmirH said:
Hey I was hoping that someone here would be able to help.
Ive been trying for get s-off on my device, I have tried everything but it dosent wnat to work. I am probably missing something basic.
I have a GPE HTC one that I until recently used with RevolutionHD 30 (Sense version).
Now that 4.4 is out I want to flash that, but every rom seems to require s-off.
Being that my Hboot version is 1.54, i understand that my only option to s-off is using rumrunner.
I have tried to rumrunner a number of times:
Using a windows machine
Using a Linux machine
I have tried both wirh the following roms: CM 10.2, CM 11, ADR 30
But I cant seem to have any luck. On both machines I alwasy get stuck at the same place:
HTML:
Please wait....
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (17/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[************************************************************]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: Download updated package at www.rumrunner.us
I dont know if it helps but "fastboot getvar mainver" alwasy rettuns blank.
I tried to log onto the rumrunner irc, but it looks to be empty.
Is their anything that I can do?
Click to expand...
Click to collapse
Since your hboot is 1.54 use Guru Reset: 2.24.xxx.x, such as: http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/ (if this doesnt work try a different 2.24 version)
in installer, select ROOT, and unselect "stock recovery", then give rumrunner a chance
nkk71 said:
Since your hboot is 1.54 use Guru Reset: 2.24.xxx.x, such as: http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/ (if this doesnt work try a different 2.24 version)
in installer, select ROOT, and unselect "stock recovery", then give rumrunner a chance
Click to expand...
Click to collapse
Although not mentiond I also tried with "Guru Reset M7 3.63.707.4" maybe the version number that I tried wasnt good.
The download is on the way and I will try it then.
This wont cause any problems with the touch issues correct? I dont not have a OTG cable.
Or follow this guide http://forum.xda-developers.com/showthread.php?t=2358781 to flash the 4.4 Google edition RUU and be completely stock. Then your main version won't be blank, and can try to get s-off
Sent from my HTC One using Tapatalk
Ivanovic said:
Or follow this guide http://forum.xda-developers.com/showthread.php?t=2358781 to flash the 4.4 Google edition RUU and be completely stock. Then your main version won't be blank, and can try to get s-off
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
That was one of the posts that I was looking at but then i saw this
HTML:
Prerequisites
S-Off,
ADB knowledge
Fastboot knowledge
Should I not be worried about that?
I thought about that but you already have the correct CID and MID. I believe it will flash just fine
Sent from my HTC One using Tapatalk
Sounds reasonable ... I will update once finished.
AmirH said:
Sounds reasonable ... I will update once finished.
Click to expand...
Click to collapse
why not try s-off with 2.24 rom, and if that doesnt work you can always try the second method. once you upgrade you can no longer downgrade with S-On.
nkk71 said:
why not try s-off with 2.24 rom, and if that doesnt work you can always try the second method. once you upgrade you can no longer downgrade with S-On.
Click to expand...
Click to collapse
Thats what I plan to do.. Im downloading both roms at the same time.
Once they are finished and I have gotten a chance to play around with them, I will update.
I do hope that one of the methods work.
OK so both methods failed, maybe I'm doing something wrong...
First:
The real reason that I wanted s-off was because I wanted to install 4.4 so i decided to try with the RUU.
I tried with a locked and unlocked boot loader. the errors i got were;
1. FAILED (remote: 12 signature verify fail)
2. FAILED (remote: 99 unknown fail)
Then I went with the GURU method...
I installed the Rom, flashed stock recovery, and added root (Bootloader still unlocked).
1. Setup my HTC
2. Allowed USB debugging
3. turned fast boot off
4. Tried to run the rumrunner again (Am I missing a step here?!?)
Still get the rumrunner error.
Im not sure if its relevent, but I get this when trying to lock and unlock the bootloader:
HTML:
fastboot oem lock
...
(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.189s
And
HTML:
fastboot oem unlock
...
(bootloader) Erasing userdata...
(bootloader) eMMC Manufacturer ID: 15
(bootloader) Start Verify: 3
(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: 10.802s
Does this tell you guys anything?
Check your drivers.. ? or install HTC Naked drivers.
SaHiLzZ said:
Check your drivers.. ? or install HTC Naked drivers.
Click to expand...
Click to collapse
Based on what part are you saying that?
Should I update the drivers and try to install RUU
or install and try to lock/unlock the bootloader.
ADB and fastboot do work just fine.
As for the rumrunner it was ran on a Unix machine. So the drivers shouldn't be an issue.
As an added suggestion, perhaps the drivers are not interacting properly to give those messages. Haven't seen those before. http://forum.xda-developers.com/showthread.php?t=2139767
(bootloader) Erasing userdata...
(bootloader) eMMC Manufacturer ID: 15
(bootloader) Start Verify: 3
(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.
AmirH said:
OK so both methods failed, maybe I'm doing something wrong...
First:
The real reason that I wanted s-off was because I wanted to install 4.4 so i decided to try with the RUU.
I tried with a locked and unlocked boot loader. the errors i got were;
1. FAILED (remote: 12 signature verify fail)
2. FAILED (remote: 99 unknown fail)
Then I went with the GURU method...
I installed the Rom, flashed stock recovery, and added root (Bootloader still unlocked).
1. Setup my HTC
2. Allowed USB debugging
3. turned fast boot off
4. Tried to run the rumrunner again (Am I missing a step here?!?)
Still get the rumrunner error.
Im not sure if its relevent, but I get this when trying to lock and unlock the bootloader:
HTML:
fastboot oem lock
...
(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.189s
And
HTML:
fastboot oem unlock
...
(bootloader) Erasing userdata...
(bootloader) eMMC Manufacturer ID: 15
(bootloader) Start Verify: 3
(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: 10.802s
Does this tell you guys anything?
Click to expand...
Click to collapse
I didnt know that "fastboot oem unlock" works with the M7, but maybe it does with the GPe
have you checked the rumrunner thread? recommend you head over there and see if you get some help. i'm not familiar enough with GPe to be able to guide you properly. sorry
I cant believe I cant get this too work... after a little investigation, I'm starting to think that it might have something to do with the fact that
"fastboot getvar mainver" returns "mainver: "
I cant even flash a stock RUU
Edit:
Updated my mainver using this tool:
http://forum.xda-developers.com/showthread.php?t=2344671
still no help
I upgraded the firmware on the HTC One (AT&T Branded). In order to do that, I had to relock the bootloader and flash firmware.zip using fastboot. I did have a proper Nandroid backup from TWRP before doing this.. Now the phone is bricked, and TWRP does not start for some reason...
I can't flash TWRP again because the bootloaded is relocked.. And when I request the bootloader unlock key from htcdev.com, I get an error
Error Code: 173.
Error Reason: Check Rule Fail with exception.
Is there any way I can get around this?
Quick update - @HTCDev came back and told me that their unlock service was down. They fixed it now and I was able to download the unlock code file.
HOWEVER, when I go to fastboot and try to flash it, nothing happens on the device (the status still shows relocked) even though fastboot says that the command succeeded..
C:\Users\walletless\Desktop\One_All-In-One_Kit_v\Data>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.167s
I also tried "fastboot reboot-bootloader" after this and it still shows status as relocked. I am on hboot 1.56 and supercid if it matters.
Anyone has suggestions?
fastboot getvar all shows:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: (delete)
(bootloader) imei: (delete)
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4259mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.095s
Also tried fastboot erase cache.. Command completed successfully but still cannot boot into recovery
Next try would be ruu... any idea which RUU I should try?
I cant use guru reset since booting into recovery does not work (I get a screen with a red triangle and exclamation when I attempt to boot to recovery)
Finally, found a solution. Phew!
Just flashed an older firmware (http://arhd.onedroid.net/db_mirror/Firmware/HTC/HTC_One/401/3.62.401.1.zip) and I am able to boot into android now...
You shouldn't need to lock the bootloader to flash firmware. Anyway, you erased your custom recovery when you flashed that firmware. Re-flash TWRP again. Make sure you have the same version as you did before so you can restore your nandroid. Did you get your bootloader unlocked?
BTW, I'd advise that you delete the Serial and imei numbers from your getvar readout in your post.
Edit: Too slow to post again, glad your device working. Still should delete those numbers.
farang4u said:
You shouldn't need to lock the bootloader to flash firmware. Anyway, you erased your custom recovery when you flashed that firmware. Re-flash TWRP again. Make sure you have the same version as you did before so you can restore your nandroid. Did you get your bootloader unlocked?
BTW, I'd advise that you delete the Serial and imei numbers from your getvar readout in your post.
Edit: Too slow to post again, glad your device working. Still should delete those numbers.
Click to expand...
Click to collapse
I cant reflash anything for some reason.. the bootloader remains in "relocked" state even after I flash unlockcode..
Immediately after flashing unlockcode, my command window shows:
Code:
> fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.165s
And the phone freezes on the fastboot screen - does not respond to any button presses, etc..
Finally got everything!!
Managed to unlock bootloader again using revone (./revone -u) and also removed the tamper flag using the -t switch.. flashed twrp and all is good again!!
Thanks....!
walletless said:
Finally got everything!!
Managed to unlock bootloader again using revone (./revone -u) and also removed the tamper flag using the -t switch.. flashed twrp and all is good again!!
Thanks....!
Click to expand...
Click to collapse
for future the best way to reclock and unlock boot loader if you are stuck is to flash any gpe firmware and simply run this command fastboot oem unlock voila it will be unlocked.
gunswordx said:
for future the best way to reclock and unlock boot loader if you are stuck is to flash any gpe firmware and simply run this command fastboot oem unlock voila it will be unlocked.
Click to expand...
Click to collapse
Thanks. I had tried that but it error'd out as well
btw, sorry I am not very good with acronyms.. what does "gpe firmware" mean?
Sent from my SGH-I337 using xda app-developers app
walletless said:
Thanks. I had tried that but it error'd out as well
btw, sorry I am not very good with acronyms.. what does "gpe firmware" mean?
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
gpe is the google edition firmware not having sense
gunswordx said:
gpe is the google edition firmware not having sense
Click to expand...
Click to collapse
Ah ok, that I did not try. Thanks for the tip!
Anyway, phone is up and running well now.. Rocking Android RevolutionHD 40.2
Hello everybody,
I'm a victim of the infamous purple tint camera bug so I'm planning get my phone fixed and thus need to get back on stock. I'm currently S-OFF and relocked bootloader. My phone's original CID is O2___102 (German O2 HTC One) but right now its on super CID (11111111). My hboot is 1.44 and my radio 4a.13.3231.27. As of right now there is a 4.2.2 custom rom running on the phone. I tried to go back to stock using this RUU ruu_m7_u_jb_50_htc_europe_1-29-401-2_r_radio_4a-14-3250-13_10-33-1150-01_release_311663_signed_2_4-exe but it always gives me that annoying 155 image error. Does anybody know a way for me to return to stock? All answers are kindly appreciated! :fingers-crossed:
fearless! said:
Hello everybody,
I'm a victim of the infamous purple tint camera bug so I'm planning get my phone fixed and thus need to get back on stock. I'm currently S-OFF and relocked bootloader. My phone's original CID is O2___102 (German O2 HTC One) but right now its on super CID (11111111). My hboot is 1.44 and my radio 4a.13.3231.27. As of right now there is a 4.2.2 custom rom running on the phone. I tried to go back to stock using this RUU ruu_m7_u_jb_50_htc_europe_1-29-401-2_r_radio_4a-14-3250-13_10-33-1150-01_release_311663_signed_2_4-exe but it always gives me that annoying 155 image error. Does anybody know a way for me to return to stock? All answers are kindly appreciated! :fingers-crossed:
Click to expand...
Click to collapse
You can follow the link in my signature on returning to stock. The reason you were not able to run that RUU is your MID or CID needs to change to match the RUU. Take a look at this crushalot's site for the .401 RUU.
Thanks a lot for the reply. My CID is on 11111111, shouldnt I be able to flash every RUU? So basically I should change my CID to HTC__102 and then flash RUU M7 UL K44 SENSE55 MR HTC Europe 4.19.401.9 R Radio 4A.23.3263.28 10.38r.1157.04L Release 353069 Signed 2-1 ?
fearless! said:
Thanks a lot for the reply. My CID is on 11111111, shouldnt I be able to flash every RUU? So basically I should change my CID to HTC__102 and then flash RUU M7 UL K44 SENSE55 MR HTC Europe 4.19.401.9 R Radio 4A.23.3263.28 10.38r.1157.04L Release 353069 Signed 2-1 ?
Click to expand...
Click to collapse
Try this RUU it is stock for your phone. You can try it with superCID, if it fails just change CID to O2___102.
I've tried to flash the RUU with both super CID and O2___102 but it did not work. It failed with a 158 error.
fearless! said:
I've tried to flash the RUU with both super CID and O2___102 but it did not work. It failed with a 158 error.
Click to expand...
Click to collapse
if you're comfortable following my guide, you'll need to use CWM method. Here are all the files you'd need: http://forum.xda-developers.com/showpost.php?p=54857652&postcount=1068
Many thanks for your tips. Im trying to do the CWM nAndroid method but when Im trying to flash the RUU.zip, I get the following error:
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Restart the same procedure with "hboot-preupdate" response for (XXXXXXXXX)...
Is something wrong with my bootloader?
PS: If it's of any interest, here is my getvar all output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXX
(bootloader) imei: XXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4261mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status malformed (0 bytes))
fearless! said:
Many thanks for your tips. Im trying to do the CWM nAndroid method but when Im trying to flash the RUU.zip, I get the following error:
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Restart the same procedure with "hboot-preupdate" response for (XXXXXXXXX)...
Is something wrong with my bootloader?
Click to expand...
Click to collapse
You need to follow instructions. When you run a RUU, you have to run the same command twice. Here are the instructions out of nkk71's guide.
In bootloader/FASTBOOT USB, flash it:
Code:
[B][I]fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip[/I][/B] <- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
[B][I]fastboot reboot-bootloader[/I][/B]
majmoz said:
You need to follow instructions. When you run a RUU, you have to run the same command twice. Here are the instructions out of nkk71's guide.
In bootloader/FASTBOOT USB, flash it:
Code:
[B][I]fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip[/I][/B] <- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
[B][I]fastboot reboot-bootloader[/I][/B]
Click to expand...
Click to collapse
Im not able to put in the command twice. After the first time it just gets stuck.
For the record, here is what my cmd looks like:
finished sending zip
OKAY
writing 'zip'... (bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Restart the same procedure with "hboot-preupdate" response for (XXX)...
< waiting for device >
starts sending zip again...
gets stuck
I think the problem is that fastboot shouldnt "restart the same procedure" on its own, so I can type in the command again right?
fearless! said:
Im not able to put in the command twice. After the first time it just gets stuck.
For the record, here is what my cmd looks like:
finished sending zip
OKAY
writing 'zip'... (bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Restart the same procedure with "hboot-preupdate" response for (XXX)...
< waiting for device >
starts sending zip again...
gets stuck
I think the problem is that fastboot shouldnt "restart the same procedure" on its own, so I can type in the command again right?
Click to expand...
Click to collapse
You are correct, it should not start its self. Let me do some quick checking and I will get back to you.
majmoz said:
You are correct, it should not start its self. Let me do some quick checking and I will get back to you.
Click to expand...
Click to collapse
Thank you a lot, Sir!
fearless! said:
Thank you a lot, Sir!
Click to expand...
Click to collapse
This is the only thing I could find. Let's reboot the phone and try the steps again.
Code:
fastboot reboot-bootloader
Code:
fastboot devices
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip ruu.zip
Code:
[B][I]fastboot flash zip ruu.zip[/I][/B] <- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
Code:
fastboot reboot-bootloader
Arrrgh tried it again and same results..I don't know what's wrong with my phone..
fearless! said:
Arrrgh tried it again and same results..I don't know what's wrong with my phone..
Click to expand...
Click to collapse
It may not be your phone, are you running Win 8 or 8.1? If so, they don't recognize hboot 1.44, so you will need to use Win 7 or Ubuntu on USB FAQ Q#5.
I was running windows 7 but your advice was aiming at the right direction. I changed PCs to another Windows 7 PC and now the flashing seems to be working! Thanks for your help so far and Im gonna keep you updated if everything else went well
Next problem: after flashing the ruu and changing the CID back the adb pushing doesnt seem to work for me. It tells me that all the files have been copied but cwm wont find any files to restore. So Im guessing that the copying didnt work. Tried it in normal storage mode too but Im getting an error kessage while trying to copy the bigger files (900 and 400mb) . Any advice on how to solve this?
fearless! said:
Next problem: after flashing the ruu and changing the CID back the adb pushing doesnt seem to work for me. It tells me that all the files have been copied but cwm wont find any files to restore. So Im guessing that the copying didnt work. Tried it in normal storage mode too but Im getting an error kessage while trying to copy the bigger files (900 and 400mb) . Any advice on how to solve this?
Click to expand...
Click to collapse
are you pushing to the right location? can you copy/paste your command prompt output
if you look at post #8 in my guide, you'll have a visual walkthrough of what kind of output to expect.
nkk71 said:
are you pushing to the right location? can you copy/paste your command prompt output
if you look at post #8 in my guide, you'll have a visual walkthrough of what kind of output to expect.
Click to expand...
Click to collapse
I did manage to get the files on my phone (over simple USB and put it in sdcard/clockworkmod/backup). But now CWM does not recognize the backup (another test backup that i put into the same folder is being recognized). When I tried to push the files before my cmd output looked just like the output in your guide. Ill try to push the files again and post the output here.
Here is my output:
c:\mini-sdk>adb push 2013-03-11.17.58.27 /data/media/clockworkmod/backup/2013-03
-11.17.58.27
push: 2013-03-11.17.58.27/system.ext4.tar.b -> /data/media/clockworkmod/backup/2
013-03-11.17.58.27/system.ext4.tar.b
push: 2013-03-11.17.58.27/system.ext4.tar.a -> /data/media/clockworkmod/backup/2
013-03-11.17.58.27/system.ext4.tar.a
push: 2013-03-11.17.58.27/system.ext4.tar -> /data/media/clockworkmod/backup/201
3-03-11.17.58.27/system.ext4.tar
push: 2013-03-11.17.58.27/recovery.img -> /data/media/clockworkmod/backup/2013-0
3-11.17.58.27/recovery.img
push: 2013-03-11.17.58.27/nandroid.md5 -> /data/media/clockworkmod/backup/2013-0
3-11.17.58.27/nandroid.md5
push: 2013-03-11.17.58.27/data.ext4.tar.a -> /data/media/clockworkmod/backup/201
3-03-11.17.58.27/data.ext4.tar.a
push: 2013-03-11.17.58.27/data.ext4.tar -> /data/media/clockworkmod/backup/2013-
03-11.17.58.27/data.ext4.tar
push: 2013-03-11.17.58.27/cache.ext4.tar.a -> /data/media/clockworkmod/backup/20
13-03-11.17.58.27/cache.ext4.tar.a
push: 2013-03-11.17.58.27/cache.ext4.tar -> /data/media/clockworkmod/backup/2013
-03-11.17.58.27/cache.ext4.tar
push: 2013-03-11.17.58.27/boot.img -> /data/media/clockworkmod/backup/2013-03-11
.17.58.27/boot.img
10 files pushed. 0 files skipped.
2670 KB/s (1532716986 bytes in 560.567s)
CWM says: No file found
Hello all,
I am having trouble trying to restore my AT&T HTC One M7 back to being functional again. The phone was soft-bricked "somehow" by my ex-wife and have been trying to restore it for the past few months. I have done alot of searching and tried many options but nothing is working so far.
The phone had never been rooted and has no custom roms on it. After it was soft-bricked, I was able to get it unlocked at one point, but stupidly enough I followed some wrong advice on how to proceed from there and relocked the phone. Now I cannot unlock it again in order to try to put TWRP or recovery on the phone to get it working again.
So far I have tried the following approaches to this issue:
1)I tried going through the HTC dev site steps to get a unlock code, but nothing happens on the phone screen even after getting a successful notice in CMD screen. (I tried both the original code and getting a new code)
2)Every time I try to flash it on there also I get signature failures in CMD and nothing happens on the phone.
3)I also tried running a stock RUU app, but after the process beings the final update, I get a usb cable error saying it is unplugged when it is not.
Thanks in advance for any suggestions.
To me that sounds like it might be a corrupt boot loader. You could also try to gain s-off and flash a recovery that way. Rumrunner works well: http://rumrunner.us
If you can s-off it then you can flash an hboot image which should fix the issue. Just go to the hboot section on the rumrunner website. Then install TWRP etc....
Your bootloader needs to be locked in order to run the RUU. Boot to bootloader screen and make sure you are in Fastboot. If on Windows, ensure you have adb installed correctly. Open command prompt on Windows with phone connected and type 'Fastboot relock oem'. This should relock the bootloader. From there, you need to make sure you have the correct RUU for your firmware, boot the phone to the main bootloader screen and run the RUU. Let me know if you need more details.
MarkBell said:
Your bootloader needs to be locked in order to run the RUU. Boot to bootloader screen and make sure you are in Fastboot. If on Windows, ensure you have adb installed correctly. Open command prompt on Windows with phone connected and type 'Fastboot relock oem'. This should relock the bootloader. From there, you need to make sure you have the correct RUU for your firmware, boot the phone to the main bootloader screen and run the RUU. Let me know if you need more details.
Click to expand...
Click to collapse
Thanks for sticking around and helping others
The correct command to lock the bootloader is fastboot oem lock. but he says he can't unlock his bootloader so I doubt that's the problem.
@Squirrelsquisher what is the software version on the phone
3.xx.502.x / 4.xx.502.x / 5.xx.502.x ?
you can use a fastboot command to get the info
fastboot getvar all
you can post the result here or just give me your version number as you have AT&T I already know you MID and CID
I love Xda, and plan to become more involved. My thinking is he is likely flashing the wrong RUU. If there is a mistake to be made, I've made it.
---------- Post added at 07:47 PM ---------- Previous post was at 07:37 PM ----------
And sorry about screwing up that Fastboot command. Lol. Posting too early in the day I guess. Lol. It is indeed Fastboot oem lock. I skimmed over the fact he can't unlock the bootloader. Sorry.
clsA said:
Thanks for sticking around and helping others
The correct command to lock the bootloader is fastboot oem lock. but he says he can't unlock his bootloader so I doubt that's the problem.
@Squirrelsquisher what is the software version on the phone
3.xx.502.x / 4.xx.502.x / 5.xx.502.x ?
you can use a fastboot command to get the info
fastboot getvar all
you can post the result here or just give me your version number as you have AT&T I already know you MID and CID
Click to expand...
Click to collapse
The software version on the phone is 4.18.502.7 and I made sure to get the same version RUU because I read I cannot use a lesser version than the phone. Also, my phone is also not unlocked, it is relocked currently. When I ran the RUU, it was processing just fine and didnt get a wrong version error. The only error I got was the crazy usb cable error because it was connected just fine.
Squirrelsquisher said:
The software version on the phone is 4.18.502.7 and I made sure to get the same version RUU because I read I cannot use a lesser version than the phone. Also, my phone is also not unlocked, it is relocked currently. When I ran the RUU, it was processing just fine and didnt get a wrong version error. The only error I got was the crazy usb cable error because it was connected just fine.
Click to expand...
Click to collapse
Try using a different USB cable. Make sure it's not one of those cheap ones from ebay. I've had issues with those before. Use your stock usb cord if you can. Let me know if you try that and it still doesn't work. Also try a different USB port on your computer. For some reason, port 2 tends to work best for most people is what I've read.
Squirrelsquisher said:
The software version on the phone is 4.18.502.7 and I made sure to get the same version RUU because I read I cannot use a lesser version than the phone. Also, my phone is also not unlocked, it is relocked currently. When I ran the RUU, it was processing just fine and didnt get a wrong version error. The only error I got was the crazy usb cable error because it was connected just fine.
Click to expand...
Click to collapse
You can flash just the firmware zip
It's on my android file host
I'll post the link when I get to my PC
MarkBell said:
Try using a different USB cable. Make sure it's not one of those cheap ones from ebay. I've had issues with those before. Use your stock usb cord if you can. Let me know if you try that and it still doesn't work. Also try a different USB port on your computer. For some reason, port 2 tends to work best for most people is what I've read.
Click to expand...
Click to collapse
I tried again using different USB ports and different cables with the same error result. Both cables that I used are stock HTC One cables that came with this problem phone and my newer M8 version.
The RUU I have been trying is:
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2
Did you have sense 5.5 or had you upgraded to Sense 6 before? If you upgraded look for the RUU made for your software version with Sense 6. You may also try a newer RUU version. Just don't try an older one.
MarkBell said:
Did you have sense 5.5 or had you upgraded to Sense 6 before? If you upgraded look for the RUU made for your software version with Sense 6. You may also try a newer RUU version. Just don't try an older one.
Click to expand...
Click to collapse
I didn't get any version errors during the update and I have not seen any RUU out there with sense 6 that doesn't require S-off.
Have you tried the first one on this list? http://forum.xda-developers.com/showthread.php?t=2428276
---------- Post added at 03:19 AM ---------- Previous post was at 03:15 AM ----------
Also. Make sure you check the MD5 of everything you download. I've heard of people downloading corrupted RUUs using Google Chrome. Try another browser. Any other one besides the one you have been using and check the MD5.
Squirrelsquisher said:
I didn't get any version errors during the update and I have not seen any RUU out there with sense 6 that doesn't require S-off.
Click to expand...
Click to collapse
MarkBell said:
Have you tried the first one on this list? http://forum.xda-developers.com/showthread.php?t=2428276
---------- Post added at 03:19 AM ---------- Previous post was at 03:15 AM ----------
Also. Make sure you check the MD5 of everything you download. I've heard of people downloading corrupted RUUs using Google Chrome. Try another browser. Any other one besides the one you have been using and check the MD5.
Click to expand...
Click to collapse
He said in both post #6 and #9 that that is the RUU he's trying
Here's the firmware from the OTA try flashing it then the RUU
http://www.androidfilehost.com/?fid=23329332407580581
I meant that download specifically thinking along the lines of a bad file/download. clsA is very good and I recommend following any advice he gives.
clsA said:
He said in both post #6 and #9 that that is the RUU he's trying
Here's the firmware from the OTA try flashing it then the RUU
Could you be a little more specific on the steps involved in that? Because I tried straight flashing that file and it said it could not load.
Click to expand...
Click to collapse
Squirrelsquisher said:
Could you be a little more specific on the steps involved in that? Because I tried straight flashing that file and it said it could not load.
Click to expand...
Click to collapse
In these situations, it's usually best to always post a "fastboot getvar all" excluding IMEI, possibly a screenshot of bootloader, and a copy/paste of your command prompt output.
the way to flash firmware is:
fastboot oem rebootRUU
fastboot flash zip ATT_OTA.4.18.502.7.firmware.zip
fastboot flash zip ATT_OTA.4.18.502.7.firmware.zip <- yes twice!!, first will say failed flush again, second one should report success
fastboot reboot-bootloader
nkk71 said:
In these situations, it's usually best to always post a "fastboot getvar all" excluding IMEI, possibly a screenshot of bootloader, and a copy/paste of your command prompt output.
the way to flash firmware is:
fastboot oem rebootRUU
fastboot flash zip ATT_OTA.4.18.502.7.firmware.zip
fastboot flash zip ATT_OTA.4.18.502.7.firmware.zip <- yes twice!!, first will say failed flush again, second one should report success
fastboot reboot-bootloader
Click to expand...
Click to collapse
I attached a screenshot of the getvar results before attempting those steps you posted.
I attached the results of the steps you posted that I should use. Since the results says it failed, I did not run the RUU afterwards.
Squirrelsquisher said:
I attached the results of the steps you posted that I should use. Since the results says it failed, I did not run the RUU afterwards.
Click to expand...
Click to collapse
getvar looks ok (well, more or less), what says "it failed"?
example of a copy/paste of a command prompt output:
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot oem rebootRUU[/COLOR][/B]
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.047s
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot flash zip <myfirmwarezip>.zip[/COLOR][/B]
sending 'zip' (1033216 KB)...
OKAY [ 41.559s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
[B][COLOR="Red"]FAILED (remote: 90 hboot pre-update! please flush image again immediately)[/COLOR][/B]
finished. total time: 43.118s
^^ as expected "flush again"
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot flash zip <myfirmwarezip>.zip[/COLOR][/B]
< waiting for device >
sending 'zip' (1033216 KB)...
OKAY [ 41.912s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) [RUU]WP,sbl3,0
(bootloader) [RUU]WP,sbl3,100
(bootloader) ...... Successful
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) start image[pg2fs_spcustom] unzipping & flushing...
(bootloader) [RUU]UZ,pg2fs_spcustom,0
(bootloader) [RUU]UZ,pg2fs_spcustom,38
(bootloader) [RUU]UZ,pg2fs_spcustom,99
(bootloader) [RUU]UZ,pg2fs_spcustom,100
(bootloader) ...... Successful
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,100
(bootloader) [RUU]WP,tz,0
(bootloader) [RUU]WP,tz,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
......
......
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]WP,rcdata,0
[B](bootloader) ...... Successful
OKAY [200.187s]
finished. total time: 242.101s[/B]
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.037s]
finished. total time: 0.037s
---------- Post added at 06:28 PM ---------- Previous post was at 06:24 PM ----------
Squirrelsquisher said:
I attached the results of the steps you posted that I should use. Since the results says it failed, I did not run the RUU afterwards.
Click to expand...
Click to collapse
oh crap, just saw your screenshot
are you using a USB3 port?
nkk71 said:
getvar looks ok (well, more or less), what says "it failed"?
example of a copy/paste of a command prompt output:
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot oem rebootRUU[/COLOR][/B]
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.047s
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot flash zip <myfirmwarezip>.zip[/COLOR][/B]
sending 'zip' (1033216 KB)...
OKAY [ 41.559s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
[B][COLOR="Red"]FAILED (remote: 90 hboot pre-update! please flush image again immediately)[/COLOR][/B]
finished. total time: 43.118s
^^ as expected "flush again"
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot flash zip <myfirmwarezip>.zip[/COLOR][/B]
< waiting for device >
sending 'zip' (1033216 KB)...
OKAY [ 41.912s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) [RUU]WP,sbl3,0
(bootloader) [RUU]WP,sbl3,100
(bootloader) ...... Successful
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) start image[pg2fs_spcustom] unzipping & flushing...
(bootloader) [RUU]UZ,pg2fs_spcustom,0
(bootloader) [RUU]UZ,pg2fs_spcustom,38
(bootloader) [RUU]UZ,pg2fs_spcustom,99
(bootloader) [RUU]UZ,pg2fs_spcustom,100
(bootloader) ...... Successful
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,100
(bootloader) [RUU]WP,tz,0
(bootloader) [RUU]WP,tz,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
......
......
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]WP,rcdata,0
[B](bootloader) ...... Successful
OKAY [200.187s]
finished. total time: 242.101s[/B]
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.037s]
finished. total time: 0.037s
---------- Post added at 06:28 PM ---------- Previous post was at 06:24 PM ----------
oh crap, just saw your screenshot
are you using a USB3 port?
Click to expand...
Click to collapse
My PC does not have USB3 ports, only USB2. I don't see how the speed of the transfer would affect the process though?
Today my cell phone got stuck on the android one logo.
I was using the cell phone when it suddenly fired, so I forced a restart with the power button and from that moment on it never turned on again.
I have the bootloader unlocked and I was running the Paranoid Quartz 4 rom about 3 months ago without any problem.
The first thing I did was try to enter recovery mode (twrp) and it was not possible. The only thing I can do with the cell phone is enter fastboot mode. So I decided to flash the stock rom using MiFlash (I tried with android 9 and android 10), but the error is always the same: "remote: Error flashing partition: Write Protected".
I have been trying to find a solution for several hours, I watched a lot of videos, I read a lot of threads, but there is no case: no solution has worked so far.
In the MiA2 forums the only thread I found is the following:
https://forum.xda-developers.com/mi-a2/help/help-xiaomi-mi-a2-write-protected-t4153629
I followed all the steps you left in the comments but nothing worked.
I wanted to know if this is happening to anyone else, and if anyone can try to help me fix it.
Thank you very much, I appreciate any kind of help.
try running :
fastboot flashing unlock_critical
*if that doesn't work then try to run
fastboot getvar all
***post the output here so we can see what's going on
have you checked the basics ? are you CERTAIN you didn't lock bootloader ..
when you went back to stock from the custom rom did you remember to go into dev settings afterwards & to check that oem unlock and adb debug were toggled to on position
lastly if trying to restore stock using miflash try it in edl mode :
fastboot oem edl
then flash latest stock in miflash
the write protect error sounds strange to me .. what happens while trying to enter twrp ? what error do you get ? did you hold power and volume up until entering recovery ..are you sure you don't have ARB triggered ?
KevMetal said:
try running :
fastboot flashing unlock_critical
*if that doesn't work then try to run
fastboot getvar all
***post the output here so we can see what's going on
have you checked the basics ? are you CERTAIN you didn't lock bootloader ..
when you went back to stock from the custom rom did you remember to go into dev settings afterwards & to check that oem unlock and adb debug were toggled to on position
lastly if trying to restore stock using miflash try it in edl mode :
fastboot oem edl
then flash latest stock in miflash
the write protect error sounds strange to me .. what happens while trying to enter twrp ? what error do you get ? did you hold power and volume up until entering recovery ..are you sure you don't have ARB triggered ?
Click to expand...
Click to collapse
Thanks for the reply.
This is the output when i put "fastboot getvar all"
(bootloader) crc:1
(bootloader) anti:1
(bootloader) token:/+VhxhMzqIjkRrCKNtCRXkCZccE=
(bootloader) parallel-download-flash:yes
(bootloader) hw-revision:10000
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4346
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) erase-block-size: 0x200
(bootloader) logical-block-size: 0x200
(bootloader) variant:SDM EMMC
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xBB77F7E00
(bootloader) partition-type:vendor_b:raw
(bootloader) partition-size:vendor_b: 0x80000000
(bootloader) partition-type:vendor_a:raw
(bootloader) partition-size:vendor_a: 0x80000000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0xC0000000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xC0000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x4000000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x4000000
(bootloader) partition-type:minidump:raw
(bootloader) partition-size:minidump: 0x8000000
(bootloader) partition-type:rawdump:raw
(bootloader) partition-size:rawdump: 0x8000000
(bootloader) partition-type:modem_b:raw
(bootloader) partition-size:modem_b: 0xC000000
(bootloader) partition-type:modem_a:raw
(bootloader) partition-size:modem_a: 0xC000000
(bootloader) partition-type:logdump:raw
(bootloader) partition-size:logdump: 0x4000000
(bootloader) partition-typeersistbak:raw
(bootloader) partition-sizeersistbak: 0x2000000
(bootloader) partition-typeersist:raw
(bootloader) partition-sizeersist: 0x2000000
(bootloader) partition-type:splash:raw
(bootloader) partition-size:splash: 0x4000000
(bootloader) partition-type:mdtp_b:raw
(bootloader) partition-size:mdtp_b: 0x2000000
(bootloader) partition-type:mdtp_a:raw
(bootloader) partition-size:mdtp_a: 0x2000000
(bootloader) partition-type:bk1:raw
(bootloader) partition-size:bk1: 0x700000
(bootloader) partition-type:bluetooth_b:raw
(bootloader) partition-size:bluetooth_b: 0x100000
(bootloader) partition-type:dsp_b:raw
(bootloader) partition-size:dsp_b: 0x1000000
(bootloader) partition-type:dsp_a:raw
(bootloader) partition-size:dsp_a: 0x1000000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2: 0x800000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1: 0x800000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg: 0x800000
(bootloader) partition-type:logfs:raw
(bootloader) partition-size:logfs: 0x800000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x800000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc: 0x400000
(bootloader) partition-type:xbl_b:raw
(bootloader) partition-size:xbl_b: 0x380000
(bootloader) partition-type:xbl_a:raw
(bootloader) partition-size:xbl_a: 0x380000
(bootloader) partition-type:sti:raw
(bootloader) partition-size:sti: 0x200000
(bootloader) partition-type:bluetooth_a:raw
(bootloader) partition-size:bluetooth_a: 0x100000
(bootloader) partition-type:keymaster_b:raw
(bootloader) partition-size:keymaster_b: 0x100000
(bootloader) partition-type:keymaster_a:raw
(bootloader) partition-size:keymaster_a: 0x100000
(bootloader) partition-type:mdtpsecapp_b:raw
(bootloader) partition-size:mdtpsecapp_b: 0x400000
(bootloader) partition-type:mdtpsecapp_a:raw
(bootloader) partition-size:mdtpsecapp_a: 0x400000
(bootloader) partition-type:tz_b:raw
(bootloader) partition-size:tz_b: 0x400000
(bootloader) partition-type:tz_a:raw
(bootloader) partition-size:tz_a: 0x400000
(bootloader) partition-type:devcfg_b:raw
(bootloader) partition-size:devcfg_b: 0x100000
(bootloader) partition-type:devcfg_a:raw
(bootloader) partition-size:devcfg_a: 0x100000
(bootloader) partition-type:toolsfv:raw
(bootloader) partition-size:toolsfv: 0x100000
(bootloader) partition-type:ddr:raw
(bootloader) partition-size:ddr: 0x100000
(bootloader) partition-type:dip:raw
(bootloader) partition-size:dip: 0x100000
(bootloader) partition-type:abl_b:raw
(bootloader) partition-size:abl_b: 0x100000
(bootloader) partition-type:abl_a:raw
(bootloader) partition-size:abl_a: 0x100000
(bootloader) partition-type:cmnlib64_b:raw
(bootloader) partition-size:cmnlib64_b: 0x100000
(bootloader) partition-type:cmnlib_b:raw
(bootloader) partition-size:cmnlib_b: 0x100000
(bootloader) partition-type:cmnlib64_a:raw
(bootloader) partition-size:cmnlib64_a: 0x100000
(bootloader) partition-type:cmnlib_a:raw
(bootloader) partition-size:cmnlib_a: 0x100000
(bootloader) partition-typemic_b:raw
(bootloader) partition-sizemic_b: 0x80000
(bootloader) partition-typemic_a:raw
(bootloader) partition-sizemic_a: 0x80000
(bootloader) partition-type:hyp_b:raw
(bootloader) partition-size:hyp_b: 0x80000
(bootloader) partition-type:hyp_a:raw
(bootloader) partition-size:hyp_a: 0x80000
(bootloader) partition-type:rpm_b:raw
(bootloader) partition-size:rpm_b: 0x80000
(bootloader) partition-type:rpm_a:raw
(bootloader) partition-size:rpm_a: 0x80000
(bootloader) partition-type:frp:raw
(bootloader) partition-size:frp: 0x80000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:msadp:raw
(bootloader) partition-size:msadp: 0x40000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-typeraw
(bootloader) partition-size 0x20000
(bootloader) partition-type:storsec:raw
(bootloader) partition-size:storsec: 0x20000
(bootloader) partition-type:vbmeta_b:raw
(bootloader) partition-size:vbmeta_b: 0x10000
(bootloader) partition-type:vbmeta_a:raw
(bootloader) partition-size:vbmeta_a: 0x10000
(bootloader) partition-type:sec:raw
(bootloader) partition-size:sec: 0x5000
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd: 0x8000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits: 0x8000
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc: 0x2000
(bootloader) partition-type:dpo:raw
(bootloader) partition-size:dpo: 0x2000
(bootloader) partition-type:switch:raw
(bootloader) partition-size:switch: 0x2000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno:ca5094d9
(bootloader) product:jasmine
(bootloader) max-download-size:805306368
(bootloader) kernel:uefi
all:
finished. total time: 0.570s
Click to expand...
Click to collapse
And when I put fastboot flashing unlock_critical
FAILED (remote: Device already : unlocked!)
finished. total time: 0.004s
The problem is that I never thought to go back to the stock rom, I am trying to do it because my cell is dead. But the usb debugging was activated (I remember, whenever I connected the cell phone to the car, the notification would appear).
I already tried flashing the stock rom in EDL. I tried different versions but they all end in the same error. At this moment I am again downloading the last stable that they uploaded (V11.0.14.0.QDIMIXM) to try, but without hope hahaha
Finally, it doesn't let me enter TWRP, the only way is with a boot from fastboot (because flashing does not allow me, just like the roms). When I boot the twrp it starts up but gets stuck at the boot logo, it never enters recovery. And I don't know what you mean by "ARB triggered"
This MiA2 literally looks like a stone, I don't know what else to do. In a forum they told me that I have to have an "authorized EDL account" or contact one in order to unbrick the terminal.
Thanks again for the reply, I appreciate it.
ivan.lxc.10 said:
Thanks for the reply.
This is the output when i put "fastboot getvar all"
And when I put fastboot flashing unlock_critical
FAILED (remote: Device already : unlocked!)
finished. total time: 0.004s
The problem is that I never thought to go back to the stock rom, I am trying to do it because my cell is dead. But the usb debugging was activated (I remember, whenever I connected the cell phone to the car, the notification would appear).
I already tried flashing the stock rom in EDL. I tried different versions but they all end in the same error. At this moment I am again downloading the last stable that they uploaded (V11.0.14.0.QDIMIXM) to try, but without hope hahaha
Finally, it doesn't let me enter TWRP, the only way is with a boot from fastboot (because flashing does not allow me, just like the roms). When I boot the twrp it starts up but gets stuck at the boot logo, it never enters recovery. And I don't know what you mean by "ARB triggered"
This MiA2 literally looks like a stone, I don't know what else to do. In a forum they told me that I have to have an "authorized EDL account" or contact one in order to unbrick the terminal.
Thanks again for the reply, I appreciate it.
Click to expand...
Click to collapse
it will work by flashing the stock rom in edl
1. install Qualcomm 9008 drivers
2. run : fastboot oem edl
3.open miflash and refresh and flash rom
make sure you are using THE LATEST miflash ( use it to install drivers)
you can also try just changing to your other slot ...stock android 1 might still be there :
fastboot set_active b
or if you are b just put :
fastboot set_active a
KevMetal said:
it will work by flashing the stock rom in edl
1. install Qualcomm 9008 drivers
2. run : fastboot oem edl
3.open miflash and refresh and flash rom
make sure you are using THE LATEST miflash ( use it to install drivers)
you can also try just changing to your other slot ...stock android 1 might still be there :
fastboot set_active b
or if you are b just put :
fastboot set_active a
Click to expand...
Click to collapse
it didn't work. I'll leave you the log so you can see if you see something that I don't
"ACK count don't match!"
http://www.mediafire.com/file/z746700jxil5d6e/COM8%4020201019114123.txt/file (1st)
http://www.mediafire.com/file/5ba9u2yb0rnzqg9/COM8%402020101911540.txt/file (2nd)
ivan.lxc.10 said:
it didn't work. I'll leave you the log so you can see if you see something that I don't
"ACK count don't match!"
http://www.mediafire.com/file/z746700jxil5d6e/COM8%4020201019114123.txt/file (1st)
http://www.mediafire.com/file/5ba9u2yb0rnzqg9/COM8%402020101911540.txt/file (2nd)
Click to expand...
Click to collapse
I will take a look when i can
were you able to enter EDL correctly ?
did you try changing slots using the commands specified ?
KevMetal said:
I will take a look when i can
were you able to enter EDL correctly ?
did you try changing slots using the commands specified ?
Click to expand...
Click to collapse
Yes, every time I try to flash (so far without success) I try in fastboot mode and in EDL mode. Each mode has a different error: in fastboot mode the error is "remote: Error flashing partition: Write Protected". In EDL mode the error is: "ACK count don't match!".
ivan.lxc.10 said:
Yes, every time I try to flash (so far without success) I try in fastboot mode and in EDL mode. Each mode has a different error: in fastboot mode the error is "remote: Error flashing partition: Write Protected". In EDL mode the error is: "ACK count don't match!".
Click to expand...
Click to collapse
ACK count doesn't match error is because you didn't listen to me ..USE THE LATEST BETA MI FLASH ... uninstall old ones first ... send a photo to show you are using latest
---------- Post added at 11:47 PM ---------- Previous post was at 11:33 PM ----------
I looked at the logs.. you also seem to be using patched programmer files ..STOP ..use only the stock rom ..without copying or replacing files ...
send me a summary of exactly which version of miflash you are using ..which stock rom and explain what you are trying to do correctly
KevMetal said:
ACK count doesn't match error is because you didn't listen to me ..USE THE LATEST BETA MI FLASH ... uninstall old ones first ... send a photo to show you are using latest
---------- Post added at 11:47 PM ---------- Previous post was at 11:33 PM ----------
I looked at the logs.. you also seem to be using patched programmer files ..STOP ..use only the stock rom ..without copying or replacing files ...
send me a summary of exactly which version of miflash you are using ..which stock rom and explain what you are trying to do correctly
Click to expand...
Click to collapse
Sorry but you said to use the latest version of my flash .. not the BETA of my flash.
Anyway I just downloaded the beta version of miflash and it didn't work either, I'm starting to go crazy lol
What do you mean by "patched programmer files"? I am using the latest fastboot rom from 09/28/2020, I did not touch or replace anything (neither now nor in the previous times I tried to flash)
Now the step by step is as follows:
I am using the beta version of my flash that I downloaded from here https://drive.google.com/file/d/12Gy2RP1eWBBKS6R2S2G9qzt-UQRIxpAM/view
and the fastboot rom I downloaded it from here https://xiaomifirmwareupdater.com/archive/miui/jasmine/
(from the xiaomi page the links for the roms do not work)
So what I do is:
- Open cmd and MiFlash
- I put in MiFlash the option "clean all"
- I select the path where the rom is located (I have it in c: \ rom)
- fastboot oem edl
- refresh and flash in MiFlash
ivan.lxc.10 said:
Sorry but you said to use the latest version of my flash .. not the BETA of my flash.
Anyway I just downloaded the beta version of miflash and it didn't work either, I'm starting to go crazy lol
What do you mean by "patched programmer files"? I am using the latest fastboot rom from 09/28/2020, I did not touch or replace anything (neither now nor in the previous times I tried to flash)
Now the step by step is as follows:
I am using the beta version of my flash that I downloaded from here https://drive.google.com/file/d/12Gy2RP1eWBBKS6R2S2G9qzt-UQRIxpAM/view
and the fastboot rom I downloaded it from here https://xiaomifirmwareupdater.com/archive/miui/jasmine/
(from the xiaomi page the links for the roms do not work)
So what I do is:
- Open cmd and MiFlash
- I put in MiFlash the option "clean all"
- I select the path where the rom is located (I have it in c: \ rom)
- fastboot oem edl
- refresh and flash in MiFlash
Click to expand...
Click to collapse
well if that the case you need to consider a hardware failure...
please try the command to change slots and send me a photo of what is says in fastboot
also when you try to edl flash did you check that your phone appears as qualcomm 9008 device in device manager * just to make sure your 9008 drivers were installed correctly.
anyway try another thing .... download the fastboot version aosip-derp from their official page ...then flash all the image files one by one from fastboot ..but before starting first do :
fastboot -w
send me photo of what happens
KevMetal said:
well if that the case you need to consider a hardware failure...
please try the command to change slots and send me a photo of what is says in fastboot
also when you try to edl flash did you check that your phone appears as qualcomm 9008 device in device manager * just to make sure your 9008 drivers were installed correctly.
anyway try another thing .... download the fastboot version aosip-derp from their official page ...then flash all the image files one by one from fastboot ..but before starting first do :
fastboot -w
send me photo of what happens
Click to expand...
Click to collapse
I spoke with a person from the xiaomi forum and checking the log he told me that apparently the device has memory damaged, so it could not be solved with the firmware flashing. After that, he consulted another person and gave him the same diagnosis: the memory is damaged so it does not allow me to write in various sectors. So effectively, my problem is hardware.
I will send it to the technical service and then I will make an update on this thread to tell my experience.
Thank you very much for the answer, I appreciate it.
ivan.lxc.10 said:
I spoke with a person from the xiaomi forum and checking the log he told me that apparently the device has memory damaged, so it could not be solved with the firmware flashing. After that, he consulted another person and gave him the same diagnosis: the memory is damaged so it does not allow me to write in various sectors. So effectively, my problem is hardware.
I will send it to the technical service and then I will make an update on this thread to tell my experience.
Thank you very much for the answer, I appreciate it.
Click to expand...
Click to collapse
yeah hardware failure makes sense
KevMetal said:
yeah hardware failure makes sense
Click to expand...
Click to collapse
Hi there
having a similar issue with regards to flashing a rom over to an Asus Zenfone 5 ZC600KL X017DA has a Qualcomm Chipset 630
the issue i have is the phone is stuck on Asus logo and all i can get from the device using the power and volume Keys is CSC fastboot mode no recovery or anything
downloaded a couple firmwares details are
Asus_Zenfone_5_Lite_ZC600KL_630_14.0400_1808.057_20180903_CMD
And
[firmware27]CSC__ZC600KL(630)_14.0400.1801.006_20191023_Phone_PtoN
both firmwares in fastboot mode will fail and one thing to note is write protected keeps appearing and the interesting thing is the first firmware i listed seems to not do very much it will show several lines and then fail but the second firmware had more activity it seemed to be pushing something but then several points it kept saying write protected
i am to assume the device bootloader is locked
i keep seeing everywhere to try unlock bootloader i need to be able to disable the OEM within the phone settings ( obviously i cannot due to it not booting ) as well as debugging mode being enabled again i cant enable
i have a third firmware that is meant to be used with QPTS / Qfil and that throws up a couple of errors also
really could use some help with this it would be super appreciated and would owe an virtual beer haha
any solutions
nighthawk658 said:
Hi there
having a similar issue with regards to flashing a rom over to an Asus Zenfone 5 ZC600KL X017DA has a Qualcomm Chipset 630
the issue i have is the phone is stuck on Asus logo and all i can get from the device using the power and volume Keys is CSC fastboot mode no recovery or anything
downloaded a couple firmwares details are
Asus_Zenfone_5_Lite_ZC600KL_630_14.0400_1808.057_20180903_CMD
And
[firmware27]CSC__ZC600KL(630)_14.0400.1801.006_20191023_Phone_PtoN
both firmwares in fastboot mode will fail and one thing to note is write protected keeps appearing and the interesting thing is the first firmware i listed seems to not do very much it will show several lines and then fail but the second firmware had more activity it seemed to be pushing something but then several points it kept saying write protected
i am to assume the device bootloader is locked
i keep seeing everywhere to try unlock bootloader i need to be able to disable the OEM within the phone settings ( obviously i cannot due to it not booting ) as well as debugging mode being enabled again i cant enable
i have a third firmware that is meant to be used with QPTS / Qfil and that throws up a couple of errors also
really could use some help with this it would be super appreciated and would owe an virtual beer haha
any solutions
Click to expand...
Click to collapse
Good day, I would like to ask did you resolve the problem we have exactly same problem.
KevMetal said:
try running :
fastboot flashing unlock_critical
*if that doesn't work then try to run
fastboot getvar all
***post the output here so we can see what's going on
have you checked the basics ? are you CERTAIN you didn't lock bootloader ..
when you went back to stock from the custom rom did you remember to go into dev settings afterwards & to check that oem unlock and adb debug were toggled to on position
lastly if trying to restore stock using miflash try it in edl mode :
fastboot oem edl
then flash latest stock in miflash
the write protect error sounds strange to me .. what happens while trying to enter twrp ? what error do you get ? did you hold power and volume up until entering recovery ..are you sure you don't have ARB triggered ?
Click to expand...
Click to collapse
Bro i have the same problem with my redmi note 5 pro .one day it running smoothly but suddenly it stuck.when i restarted the device it stuck on logo. Recovery also got stucked.fastboot logo not showing only black screen but computer detected fastboot.i tried many things .but it says that the device is write protected