Installed Cyanongen 11, Revert to stock and im stuck! AT&T HTC One M7 (Please Help!)
Greetings,
I am in a predicament. I installed and used the cyanogenmod 11 beta installer because it looked very easy (and it was), all went well. But, I needed to revert back to stock to unlock my sim with a newly purchased sim unlock code, and I botched my phone in the process and I am stuck running in circles.
What I can do: Lock and Relock bootloader (with tampered and unlocked flags), flash a recovery.
What I can't do: everything else... ruu's fail, flashing fails, and it's a never ending circle.
I can't get S-OFF due to being stuck in the bootloader and while in recovery, I am unable to mount /cache, /system, etc. Nothing seems writeable and nothing seems to be able to flash or install. I have tried, fastboot oem rebootRUU, etc. I have tried sideloading... and everything else that I have read around the net.
Getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***
(bootloader) imei: ***
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4214mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
When locking bootloader to attempt to RUU I get 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.110s
When launching RUU exe I get: ERROR [155]: UNKNOWN ERROR ( I Have tried several different RUU's)
Please help! I am without a phone and I am like a chicken with its head cut off right now...
Any help would be highly appreciated...
OCTechs said:
Greetings,
I am in a predicament. I installed and used the cyanogenmod 11 beta installer because it looked very easy (and it was), all went well. But, I needed to revert back to stock to unlock my sim with a newly purchased sim unlock code, and I botched my phone in the process and I am stuck running in circles.
What I can do: Lock and Relock bootloader (with tampered and unlocked flags), flash a recovery.
What I can't do: everything else... ruu's fail, flashing fails, and it's a never ending circle.
I can't get S-OFF due to being stuck in the bootloader and while in recovery, I am unable to mount /cache, /system, etc. Nothing seems writeable and nothing seems to be able to flash or install. I have tried, fastboot oem rebootRUU, etc. I have tried sideloading... and everything else that I have read around the net.
Getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***
(bootloader) imei: ***
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4214mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
When locking bootloader to attempt to RUU I get 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.110s
When launching RUU exe I get: ERROR [155]: UNKNOWN ERROR ( I Have tried several different RUU's)
Please help! I am without a phone and I am like a chicken with its head cut off right now...
Any help would be highly appreciated...
Click to expand...
Click to collapse
Did you use this thread to downgrade your version main?
http://forum.xda-developers.com/showthread.php?t=2398717
I don't have experience with this but I wonder what recovery you should have before trying to relock bootloader. do you have custom recovery installed?
mb_guy said:
Did you use this thread to downgrade your version main?
http://forum.xda-developers.com/showthread.php?t=2398717
I don't have experience with this but I wonder what recovery you should have before trying to relock bootloader. do you have custom recovery installed?
Click to expand...
Click to collapse
Yes, I have tried. I will try again and post the results...
Results:
Code:
C:\Android\One_All-In-One_Kit_v3.1\One_All-In-One_Kit_v\Data>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT3********* recovery
C:\Android\One_All-In-One_Kit_v3.1\One_All-In-One_Kit_v\Data>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.115s
C:\Android\One_All-In-One_Kit_v3.1\One_All-In-One_Kit_v\Data>fastboot oem reboot
RUU
...
(bootloader) Start Verify: 3
OKAY [ 0.051s]
finished. total time: 0.052s
C:\Android\One_All-In-One_Kit_v3.1\One_All-In-One_Kit_v\Data>fastboot flash rom.
zip
unknown partition 'rom.zip'
error: cannot determine image filename for 'rom.zip'
C:\Android\One_All-In-One_Kit_v3.1\One_All-In-One_Kit_v\Data>fastboot flash zip
rom.zip
sending 'zip' (1029872 KB)...
OKAY [ 45.155s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 146.955s
C:\Android\One_All-In-One_Kit_v3.1\One_All-In-One_Kit_v\Data>fastboot flash zip
rom.zip
sending 'zip' (1029872 KB)...
At this point.. I let it sit for 15 minutes and nothing happened.
I managed to flash a firmware provided by Android Revolution 4.06.1540.2.zip, renamed it to "firmware.zip" and was able to pull that off successfully (I think "see code below") but even after that, I tried to manually flash the rom.zip and install it via the exe and still no profit. :/
Code:
< waiting for device >
sending 'zip' (43288 KB)...
OKAY [ 2.976s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,11
(bootloader) [RUU]UZ,boot,24
(bootloader) [RUU]UZ,boot,35
(bootloader) [RUU]UZ,boot,47
(bootloader) [RUU]UZ,boot,59
(bootloader) [RUU]UZ,boot,72
(bootloader) [RUU]UZ,boot,82
(bootloader) [RUU]UZ,boot,93
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,99
(bootloader) [RUU]WP,boot,100
(bootloader) ...... Successful
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,6
(bootloader) [RUU]UZ,recovery,12
(bootloader) [RUU]UZ,recovery,21
(bootloader) [RUU]UZ,recovery,29
(bootloader) [RUU]UZ,recovery,38
(bootloader) [RUU]UZ,recovery,45
(bootloader) [RUU]UZ,recovery,50
(bootloader) [RUU]UZ,recovery,67
(bootloader) [RUU]UZ,recovery,75
(bootloader) [RUU]UZ,recovery,83
(bootloader) [RUU]UZ,recovery,88
(bootloader) [RUU]UZ,recovery,97
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,99
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(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[sbl1-3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-3,0
(bootloader) [RUU]UZ,sbl1-3,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[sbl2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl2,0
(bootloader) [RUU]UZ,sbl2,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[tp] unzipping & flushing...
(bootloader) [RUU]UZ,tp,0
(bootloader) [RUU]UZ,tp,100
(bootloader) ..... Bypassed
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,6
(bootloader) [RUU]UZ,radio,12
(bootloader) [RUU]UZ,radio,18
(bootloader) [RUU]UZ,radio,24
(bootloader) [RUU]UZ,radio,30
(bootloader) [RUU]UZ,radio,37
(bootloader) [RUU]UZ,radio,43
(bootloader) [RUU]UZ,radio,49
(bootloader) [RUU]UZ,radio,55
(bootloader) [RUU]UZ,radio,62
(bootloader) [RUU]UZ,radio,68
(bootloader) [RUU]UZ,radio,74
(bootloader) [RUU]UZ,radio,81
(bootloader) [RUU]UZ,radio,87
(bootloader) [RUU]UZ,radio,93
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,24
(bootloader) [RUU]WP,radio,49
(bootloader) [RUU]WP,radio,74
(bootloader) [RUU]WP,radio,99
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,42949671
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,42949671
(bootloader) ...... Successful
OKAY [ 27.115s]
finished. total time: 30.095s
It did however change my GetVar slightly (below):
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-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4276mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(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.055s
OCTechs said:
I managed to flash a firmware provided by Android Revolution 4.06.1540.2.zip, renamed it to "firmware.zip" and was able to pull that off successfully (I think "see code below") but even after that, I tried to manually flash the rom.zip and install it via the exe and still no profit. :/
Code:
< waiting for device >
sending 'zip' (43288 KB)...
OKAY [ 2.976s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,11
(bootloader) [RUU]UZ,boot,24
(bootloader) [RUU]UZ,boot,35
(bootloader) [RUU]UZ,boot,47
(bootloader) [RUU]UZ,boot,59
(bootloader) [RUU]UZ,boot,72
(bootloader) [RUU]UZ,boot,82
(bootloader) [RUU]UZ,boot,93
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,99
(bootloader) [RUU]WP,boot,100
(bootloader) ...... Successful
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,6
(bootloader) [RUU]UZ,recovery,12
(bootloader) [RUU]UZ,recovery,21
(bootloader) [RUU]UZ,recovery,29
(bootloader) [RUU]UZ,recovery,38
(bootloader) [RUU]UZ,recovery,45
(bootloader) [RUU]UZ,recovery,50
(bootloader) [RUU]UZ,recovery,67
(bootloader) [RUU]UZ,recovery,75
(bootloader) [RUU]UZ,recovery,83
(bootloader) [RUU]UZ,recovery,88
(bootloader) [RUU]UZ,recovery,97
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,99
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(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[sbl1-3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-3,0
(bootloader) [RUU]UZ,sbl1-3,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[sbl2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl2,0
(bootloader) [RUU]UZ,sbl2,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[tp] unzipping & flushing...
(bootloader) [RUU]UZ,tp,0
(bootloader) [RUU]UZ,tp,100
(bootloader) ..... Bypassed
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,6
(bootloader) [RUU]UZ,radio,12
(bootloader) [RUU]UZ,radio,18
(bootloader) [RUU]UZ,radio,24
(bootloader) [RUU]UZ,radio,30
(bootloader) [RUU]UZ,radio,37
(bootloader) [RUU]UZ,radio,43
(bootloader) [RUU]UZ,radio,49
(bootloader) [RUU]UZ,radio,55
(bootloader) [RUU]UZ,radio,62
(bootloader) [RUU]UZ,radio,68
(bootloader) [RUU]UZ,radio,74
(bootloader) [RUU]UZ,radio,81
(bootloader) [RUU]UZ,radio,87
(bootloader) [RUU]UZ,radio,93
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,24
(bootloader) [RUU]WP,radio,49
(bootloader) [RUU]WP,radio,74
(bootloader) [RUU]WP,radio,99
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,42949671
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,42949671
(bootloader) ...... Successful
OKAY [ 27.115s]
finished. total time: 30.095s
It did however change my GetVar slightly (below):
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-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4276mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(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.055s
Click to expand...
Click to collapse
I'd suggest you post here and see if @clsA thinks his rom will help you
http://forum.xda-developers.com/showthread.php?t=2674222
not sure now that you changed your firmware version and hboot is 1.56
mb_guy said:
I'd suggest you post here and see if @clsA thinks his rom will help you
http://forum.xda-developers.com/showthread.php?t=2674222
not sure now that you changed your firmware version and hboot is 1.56
Click to expand...
Click to collapse
Yea, I'll look into it but as far as having S-ON and 1.56, life seems really bleak.
(last time i'm using cyanogenrom) I can say that much.
clsA's custom rom says it needs to be installed in recovery, which isn't much of an option for me as it would have to be sideloaded,
which thus far has gotten me no-where.
I'm at a loss...
OCTechs said:
Yea, I'll look into it but as far as having S-ON and 1.56, life seems really bleak.
(last time i'm using cyanogenrom) I can say that much.
clsA's custom rom says it needs to be installed in recovery, which isn't much of an option for me as it would have to be sideloaded,
which thus far has gotten me no-where.
I'm at a loss...
Click to expand...
Click to collapse
What is your current recovery?
Is Your device a developer edition or stock at&t us
mb_guy said:
What is your current recovery?
Click to expand...
Click to collapse
I have tried:
openrecovery-twrp-2.6.3.3-m7.img
openrecovery-twrp-2.6.3.4-m7.img
recovery-clockwork-6.0.4.3-m7att.img
recovery-clockwork-touch-6.0.4.6-m7.img
and a few stock recoveries. The last flashed recovery was twrp 2.6.3.3. I can get into recovery, but nothing seems to work... such as mounting /cache, /system, etc. I can get sideload to work (sometimes) and have tried sideloading ruu's and stock roms and tried to install for zip, but no luck, everything fails.
I went from stock to Cyanogenrom 11 beta installer and it worked fine... but it never red flagged as "developer edition" S was never turned off (which was stupid on my part for not doing that first) before trying to RUU, which got me in this mess in the first place. As for it being stock or developer edition, I am not sure... I can unlock the bootloaded with the HTCDEV provided Unlock_code.bin, just fine. When executing "fastboot oem lock" it flags as a *tampered, relocked, and security warning".
OCTechs said:
I have tried:
openrecovery-twrp-2.6.3.3-m7.img
openrecovery-twrp-2.6.3.4-m7.img
recovery-clockwork-6.0.4.3-m7att.img
recovery-clockwork-touch-6.0.4.6-m7.img
and a few stock recoveries. The last flashed recovery was twrp 2.6.3.3. I can get into recovery, but nothing seems to work... such as mounting /cache, /system, etc. I can get sideload to work (sometimes) and have tried sideloading ruu's and stock roms and tried to install for zip, but no luck, everything fails.
I went from stock to Cyanogenrom 11 beta installer and it worked fine... but it never red flagged as "developer edition" S was never turned off (which was stupid on my part for not doing that first) before trying to RUU, which got me in this mess in the first place. As for it being stock or developer edition, I am not sure... I can unlock the bootloaded with the HTCDEV provided Unlock_code.bin, just fine. When executing "fastboot oem lock" it flags as a *tampered, relocked, and security warning".
Click to expand...
Click to collapse
That is normal behavior for bootloader flags. Is your bootloader now unlocked? I noticed a couple of posts back it was relocked. twrp and other custom recoveries need it unlocked to work.
The firmware you flashed is developer edition.
mb_guy said:
That is normal behavior for bootloader flags. Is your bootloader now unlocked? I noticed a couple of posts back it was relocked. twrp and other custom recoveries need it unlocked to work.
Click to expand...
Click to collapse
Yes, I can unlock and relock the bootloader by executing commands:
#fastboot oem lock
and
#fastboot flash unlocktoken Unlock_code.bin
I can install the recoveries once it's unlocked ofcourse, but I relock it in-order to try to RUU or install any sort of stock rom.
OCTechs said:
Yes, I can unlock and relock the bootloader by executing commands:
#fastboot oem lock
and
#fastboot flash unlocktoken Unlock_code.bin
I can install the recoveries once it's unlocked ofcourse, but I relock it in-order to try to RUU or install any sort of stock rom.
Click to expand...
Click to collapse
Why not reinstall twrp and try and sideload @clsA's rom. Or otg cable if you have.
OCTechs said:
Yes, I can unlock and relock the bootloader by executing commands:
#fastboot oem lock
and
#fastboot flash unlocktoken Unlock_code.bin
I can install the recoveries once it's unlocked ofcourse, but I relock it in-order to try to RUU or install any sort of stock rom.
Click to expand...
Click to collapse
Your really in panic mode it seems and your heading for disaster if you don't stop and listen.
First you don't relock to flash anything but a RUU
if you getting error on RUU your using the wrong one
you cid and MID are both stock AT&T ... simply flash the stock AT&T RUU
From your Second post
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 146.955s
Click to expand...
Click to collapse
This just means you used the wrong rom.zip .. if it's a decrypted RUU/ Rom.zip you need S-off to flash it.
Why have you kept flashing different recovery's ?
are you doing all the steps to flash recovery ?
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
then you simple sideload the rom of your choice ...
Are you MD5 checking all your downloads ?
here's the last AT&T RUU it should flash on your current setup (lock the bootloader first) >> http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
---------- Post added at 07:20 PM ---------- Previous post was at 07:17 PM ----------
mb_guy said:
Why not reinstall twrp and try and sideload @clsA's rom. Or otg cable if you have.
Click to expand...
Click to collapse
this would seem the simple choice .. but if he has never cleared the cache from fastboot everything will fail. He also mention trying to mount things in recovery ??? I have never once mounted anything in recovery except my usb-otg device.
clsA said:
Your really in panic mode it seems and your heading for disaster if you don't stop and listen.
First you don't relock to flash anything but a RUU
if you getting error on RUU your using the wrong one
you cid and MID are both stock AT&T ... simply flash the stock AT&T RUU
From your Second post
This just means you used the wrong rom.zip .. if it's a decrypted RUU/ Rom.zip you need S-off to flash it.
Why have you kept flashing different recovery's ?
are you doing all the steps to flash recovery ?
then you simple sideload the rom of your choice ...
Are you MD5 checking all your downloads ?
here's the last AT&T RUU it should flash on your current setup (lock the bootloader first) >> http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
---------- Post added at 07:20 PM ---------- Previous post was at 07:17 PM ----------
this would seem the simple choice .. but if he has never cleared the cache from fastboot everything will fail. He also mention trying to mount things in recovery ??? I have never once mounted anything in recovery except my usb-otg device.
Click to expand...
Click to collapse
Yes, you are 100% right and can sense my tension via chat, lol. I'm freaking out, kinda. Because, I am certain that I screwed up...
Here is where I went wrong (I started fresh on my girlfriends phone which is identical to mine "she has 1.55 though"), I didn't realize Cyanogenrom's > settings > Superuser > settings > "Apps & ADB" (allow access), So when I tried to S-OFF with Rumrunner, it failed because of this... and I was unable to achieve S-OFF. I wasn't thinking and attempted to flash a RUU and everything botched. Now it seems like my phone is stuck in bootloader and a halfway working recovery menu due to the permissions and being unable to mount anything. I have been trying to use the (above RUU) file and it fails and errors out while running the exe. I have taken the "rom.zip" out of the file and attempted to flash that but since it's S-ON it fails.
You have given me hope though, on the fact that "i didn't md5 verify" the downloads and it could possibly be fixed. So that's good news, and I honestly thank you for being here for me man.
OCTechs said:
Yes, you are 100% right and can sense my tension via chat, lol. I'm freaking out, kinda. Because, I am certain that I screwed up...
Here is where I went wrong (I started fresh on my girlfriends phone which is identical to mine "she has 1.55 though"), I didn't realize Cyanogenrom's > settings > Superuser > settings > "Apps & ADB" (allow access), So when I tried to S-OFF with Rumrunner, it failed because of this... and I was unable to achieve S-OFF. I wasn't thinking and attempted to flash a RUU and everything botched. Now it seems like my phone is stuck in bootloader and a halfway working recovery menu due to the permissions and being unable to mount anything. I have been trying to use the (above RUU) file and it fails and errors out while running the exe. I have taken the "rom.zip" out of the file and attempted to flash that but since it's S-ON it fails.
You have given me hope though, on the fact that "i didn't md5 verify" the downloads and it could possibly be fixed. So that's good news, and I honestly thank you for being here for me man.
Click to expand...
Click to collapse
you can flash rom zip .. just not decrypted rom zip
what error did you get with the at&t ruu rom.zip ?
it helps if I can see you command screens for possible errors
the normal procedure to recover from CM 11 is to just flash stock recovery to your phone and do a factory reset with the stock recovery ... then flash TWRP / clear cache / factory reset in twrp and sideload a rom
clsA said:
what error did you get with the at&t ruu rom.zip ?
Click to expand...
Click to collapse
Primarily this error: FAILED (status read failed (Too many links)) when attempting to ruu the rom.zip
clsA said:
you can flash rom zip .. just not decrypted rom zip
the normal procedure to recover from CM 11 is to just flash stock recovery to your phone and do a factory reset with the stock recovery ... then flash TWRP / clear cache / factory reset in twrp and sideload a rom
Click to expand...
Click to collapse
What stock recovery we be best to flash?
And what are the commands in order to sideload the rom from TWRP?
# adb sideload rom.zip ?
Should this automatically begin the installation procedure for the rom?
Or, will I have to attempt to "install from zip" in twrp afterwards?
When I tried to clear cache in twrp, I would get a failed flag "unable to mount /cache" etc.
and it basically did nothing, and it would fail when trying to mount it in twrp.
Update:
When trying to "factory reset" in twrp 2.6.3.3 it Failed.
Code:
E: unable to mount '/cache'
OCTechs said:
What stock recovery we be best to flash?
And what are the commands in order to sideload the rom from TWRP?
# adb sideload rom.zip ?
Should this automatically begin the installation procedure for the rom?
Or, will I have to attempt to "install from zip" in twrp afterwards?
When I tried to clear cache in twrp, I would get a failed flag "unable to mount /cache" etc.
and it basically did nothing, and it would fail when trying to mount it in twrp.
Click to expand...
Click to collapse
the recovery from you current version number is the one you want
you can extract it from a decrypted rom.zip
being your on kitkat this one should work
http://d-h.st/71m
TWRP / Advanced / Sideload
From PC adb /fastboot folder
you use
adb sideload rom.zip
clsA said:
the recovery from you current version number is the one you want
you can extract it from a decrypted rom.zip
being your on kitkat this one should work
http://d-h.st/71m
TWRP / Advanced / Sideload
From PC adb /fastboot folder
you use
adb sideload rom.zip
Click to expand...
Click to collapse
After installing the stock recovery (and trying to access it) it gives me the recycling symbol for a moment, then it bootloops with the HTC logo... So I factory reset within the bootloader, cleared cache, reboot-bootloader, installed twrp 2.6.3.0, cleared cache, reboot-bootloader, and im going to attempt to install the ruu exe from the above post, if that fails, then i'll try to sideload.
Success! Im very happy now... Two days running in circles and 2am ers... I got it to work!
I thank you very much man and I owe you big time bro.
I will post my steps on what I did from start to finish so maybe down the line it will help someone else out.