Database Develop

[Q] m7 weird brick need help

Hi guys .last month weird thing happen
My m7 lose signal then i restarted the phOne suddenly bricked ..
the problem
Stuck on bootloop
Lost my access to recovery
RUU not stocking but not showing any error (RUU.exe)
I think its because the kernel i have instaled (elementarX 14)
I think sumting wrong with emmc or mid (pn071****)
My rom arhd62
Cid-11111111
Hboot-1.44.0000
Baseband-4a.14.3250.13
eMMC-boot
M7_ul s-off
Modelid n071
I searched all over the place ..need help ppl

Can u try reflashing recovery through fastboot? Sometines the kernel if flashed improperly can wipe recovery partition and it needs to be reflashed....reflash recovery through fastboot and reflash with fastboot flash recovery yourrecoveryname.img
Sent from my HTCONE using Tapatalk

knockratos said:
Hi guys .last month weird thing happen
My m7 lose signal then i restarted the phOne suddenly bricked ..
the problem
Stuck on bootloop
Lost my access to recovery
RUU not stocking but not showing any error (RUU.exe)
I think its because the kernel i have instaled (elementarX 14)
My rom arhd62
Cid-11111111
Hboot-1.44.0000
Baseband-4a.14.3250.13
eMMC-boot
M7_ul s-off
Modelid n071
I searched all over the place ..need help ppl
Click to expand...
Click to collapse
Post the output of fastboot getvar all except IMEI and S/N.
have you tried to flash your recovery + erase cache?

alray said:
Post the output of fastboot getvar all except IMEI and S/N.
have you tried to flash your recovery + erase cache?
Click to expand...
Click to collapse
I alredy did that ..
i try reflash the twrp then the rom.zip the zip say error not enough space
i try to erase system and stuff failed too

knockratos said:
I alredy did that ..
i try reflash the twrp then the rom.zip the zip say error not enough space
i try to erase system and stuff failed too
Click to expand...
Click to collapse
fastboot getvar all

alray said:
fastboot getvar all
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4241mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.092s

knockratos said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4241mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.092s
Click to expand...
Click to collapse
What ruu are you trying to use? With s-off it should be quite easy to restore your phone...
did you modified your MID?

alray said:
What ruu are you trying to use? With s-off it should be quite easy to restore your phone...
did you modified your MID?
Click to expand...
Click to collapse
RUU m7 u jb 50 htc europe 1.29.401.2.r.radio 4a1432501310331150release311663signed24..
First time i bricked and it works ..after that i allways use nandroid ..but now doesnt work and i dont have acces to recovery

knockratos said:
RUU m7 u jb 50 htc europe 1.29.401.2.r.radio 4a1432501310331150release311663signed24..
First time i bricked and it works ..after that i allways use nandroid ..but now doesnt work and i dont have acces to recovery
Click to expand...
Click to collapse
So you are using a ruu.exe. What version of windows do you have? 7, 8 or 8.1?

alray said:
What ruu are you trying to use? With s-off it should be quite easy to restore your phone...
did you modified your MID?
Click to expand...
Click to collapse
knockratos said:
RUU m7 u jb 50 htc europe 1.29.401.2.r.radio 4a1432501310331150release311663signed24..
First time i bricked and it works ..after that i allways use nandroid ..but now doesnt work and i dont have acces to recovery
Click to expand...
Click to collapse
1- JTAG repair ? (thanks @scotty1223 )
2- you have a UL model it seems not a U
@alray link him the MID change tool (not the ENG method ) change mid to PN0710000 then he can go on with an m7_ul ruu... or whatever need to be done, good luck

mid change tool:
http://forum.xda-developers.com/showthread.php?t=2535365

nkk71 said:
1- JTAG repair ? (thanks @scotty1223 )
2- you have a UL model it seems not a U
@alray link him the MID change tool (not the ENG method ) change mid to PN0710000 then he can go on with an m7_ul ruu... or whatever need to be done, good luck
Click to expand...
Click to collapse
Windows 7
What is jtag repair
long time agO the RUU was working fine (the brick was only freeze on bootloop but whit recovery)
But now it REBOOTLOOP over and over and i lost access to recovery ..
The RUU do its job sucessfuly but not stocking (doing nothing)
I guess i didnt chage any mid
I have to change ? How ? And than what ?
Is it possibly that is kernel issue ?
Dont know what to do

knockratos said:
Windows 7
Dont know what to do
Click to expand...
Click to collapse
alray is helping you plenty, so return in kind by at least pressing his thanks button

nkk71 said:
alray is helping you plenty, so return in kind by at least pressing his thanks button
Click to expand...
Click to collapse
Done but im new in here ..

alray said:
mid change tool:
http://forum.xda-developers.com/showthread.php?t=2535365
Click to expand...
Click to collapse
How i can install the mid change if i dont have access to recovery?

alray said:
mid change tool:
http://forum.xda-developers.com/showthread.php?t=2535365
Click to expand...
Click to collapse
Hi tried using fastboot flash zip ..it says failed remote not allowed

knockratos said:
Hi tried using fastboot flash zip ..it says failed remote not allowed
Click to expand...
Click to collapse
download twrp 2.6.3.3 from here and save it to your adb/fastboot folder
check MD5 before flashing: 72067aefb69541d40e8420d7aa46408d
boot phone in bootloader mode and flash the recovery:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootlader
then boot in recovery mode (TWRP main menu)
Download the MID change tool from here and save it to your adb/fastboot folder
check md5 value: ae54b6e28a925270661994dbe16eb742
push the tool:
Code:
adb push MID_Change_1.01.zip /sdcard/
in twrp, select ''install'' browse sdcard and select ''MID_Change_1.01.zip'' then ''swipe to confirm flash''.
The aroma installer will start:
select ''next'' at the ''welcome screen''
Thick the check box ''I agree with these Terms of Use'', then select ''next''
select ''next'' at the ''Credit and Support'' screen
at the CID Options screen, select ''PN0710000'' then select ''next''
at the ''ready to install'' screen, select ''install now''
wait for the mid tool to do its magic (few seconds) and select ''next''
at the ''Actions were successful'' screen, select ''Finish''
Now you are back in TWRP recovery
select ''back'' twice and then ''reboot'' and choose ''bootloader''
You are now back in bootloader mode
change your cid to match the RUU:
Code:
fastboot oem writecid HTC__001
fastboot reboot-bootloader
download the ruu from here
check md5: 9ad4111ce86981e3dffcce6d9ee80551
launch the ruu and follow instructions.
stay s-off and bootloader unlocked.

alray said:
download twrp 2.6.3.3 from here and save it to your adb/fastboot folder
check MD5 before flashing: 72067aefb69541d40e8420d7aa46408d
boot phone in bootloader mode and flash the recovery:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootlader
Not working cant enter to recovery mode and it keeps reboot loop
I think if the recovery start work i will use my nandroid backup ..and the RUU wont be necessary i guess
How to check the md5 value ?? @alray I realy apreciate what u doing to help me .thnks ..
Click to expand...
Click to collapse

knockratos said:
Not working cant enter to recovery mode and it keeps reboot loop
Click to expand...
Click to collapse
You mean the phone bootloop when you are trying to enter recovery or it bootloop as soon you enter bootloader?
Try holding power + vol down until the phone boot in bootloader and stop looping
How to check the md5 value ??
Click to expand...
Click to collapse
check ''not so FAQ #1'' at the end of this post (from nkk71's guide)
or
http://lmgtfy.com/?q=how+do+i+check+md5+windows

alray said:
You mean the phone bootloop when you are trying to enter recovery or it bootloop as soon you enter bootloader?
Try holding power + vol down until the phone boot in bootloader and stop looping
check ''not so FAQ #1'' at the end of this post (from nkk71's guide)
or
http://lmgtfy.com/?q=how+do+i+check+md5+windows
Click to expand...
Click to collapse
It means that boot loop when i enter recovery mode or factory reset mode or turn on the phone( of course)
Keep boot over and over ..
But the bootloader is fine .

Need help with htc one!

hello,
so i recently accidentally removed my android OS from my htc one (m7) and the backup i took , and now im stuck with a bricked phone.
it is still unlocked , S-on however and i have the Twrp custom recovery.
I have the stock RUU for my phone but i can't use ADB push command to forward it to my phone.
It might be because my usb debugging is off ( probably not ) but i cant open my phone , it keeps stuck at the bootscreen.
i also couldnt flash it with fasboot flash zip command.
If anyone could help me out with this, i would be so happy.
Thanks in advance

angizwa said:
hello,
so i recently accidentally removed my android OS from my htc one (m7) and the backup i took , and now im stuck with a bricked phone.
it is still unlocked , S-on however and i have the Twrp custom recovery.
I have the stock RUU for my phone but i can't use ADB push command to forward it to my phone.
It might be because my usb debugging is off ( probably not ) but i cant open my phone , it keeps stuck at the bootscreen.
i also couldnt flash it with fasboot flash zip command.
If anyone could help me out with this, i would be so happy.
Thanks in advance
Click to expand...
Click to collapse
What RUU are you trying to flash? Here is alray's procedure for your situation. You might want to check the prerequisites on installed drivers. Also, is there a RUU.exe file to use instead of a zip file?
If these procedures don't work, then post a fastboot getvar all except for the imei and serialno.

@majmoz
The ruu im using is a zip ( i used it before and it works, ) its the guru reset M7 3.62.401.1, my drivers work too , it recognizes my phone when plugged into my pc
here is my getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4070mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.165s

angizwa said:
@majmoz
The ruu im using is a zip ( i used it before and it works, ) its the guru reset M7 3.62.401.1, my drivers work too , it recognizes my phone when plugged into my pc
here is my getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4070mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.165s
Click to expand...
Click to collapse
angizwa said:
hello,
so i recently accidentally removed my android OS from my htc one (m7) and the backup i took , and now im stuck with a bricked phone.
it is still unlocked , S-on however and i have the Twrp custom recovery.
I have the stock RUU for my phone but i can't use ADB push command to forward it to my phone.
It might be because my usb debugging is off ( probably not ) but i cant open my phone , it keeps stuck at the bootscreen.
i also couldnt flash it with fasboot flash zip command.
If anyone could help me out with this, i would be so happy.
Thanks in advance
Click to expand...
Click to collapse
guru reset M7 3.62.401.1 is not a RUU, its a ROM (stock rom) and must be installed using a custom recovery, not using "fastboot flash zip" command which is only used to flash RUU.zip or Firmware.zip
However, 3.62.401.1 is no longer the version you need (your hboot is 1.57) so you probably need the 5.11.401.10 or 6.09.401.5 rom.
Also usb debugging have nothing to do with using adb from custom recovery, its only to enable adb when booted in the OS.
make sure to use twrp 2.6.3.3 with latest adb 1.0.31 and latest htc drivers installed and push the correct stock rom to your phone using adb push or sideload.

@alray
oohh okay thanks, ill get that twrp, but do i have to change twrp version ? mine is 2.7-something, i'll download the correct ruu... i feel so stupid right now thanks, i really hope this works

angizwa said:
@alray
oohh okay thanks, ill get that twrp, but do i have to change twrp version ? mine is 2.7-something, i'll download the correct ruu... i feel so stupid right now thanks, i really hope this works
Click to expand...
Click to collapse
There is no RUU you can flash for that version with s-on. Find a stock rom for your version. And better to use twrp 2.6.3.3
Sent from my HTC One using XDA Free mobile app

you can sideload a rom through adb while you're in twrp super easy and fast

@alray
oh okay ill look for a stock rom then

@2B_4G10
i know i tried sideload and push, but for some reason ADB doesnt want to work
i typed adb devices in command and it did show an empty list, no idea why...

hmm i tried flashing the stock rom,
i got this error
http://i.imgur.com/XzOOJYE.jpg
what does this mean ?
oh and after relocking, it gave me a signature check (remote : 12 ) fail... :/

angizwa said:
hmm i tried flashing the stock rom,
i got this error
http://i.imgur.com/XzOOJYE.jpg
what does this mean ?
oh and after relocking, it gave me a signature check (remote : 12 ) fail... :/
Click to expand...
Click to collapse
look back at post #4, already explained why

@alray
oh... so its not a stock rom ? adb doesnt work on my device anymore... adb devices gives me an empty list...
and i cant flash the other TWRP version ... it gives me this problem :
target reported max download size of 1514139648 bytes
sending 'customrecovery' (10854 KB)...
OKAY [ 1.767s]
writing 'customrecovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.709s

angizwa said:
@alray
oh... so its not a stock rom ?
Click to expand...
Click to collapse
Only RUU (Rom Update Utility) can be flashed with fastboot flash zip commands, not ROM even if the rom is a STOCK rom. RUUs and ROMS are 2 differents things. The RUU is a package containing the system(ROM), kernel, radio, bootloader, touch screen drivers and much more. It must be signed with HTC encrypted key to be flashed using "fastboot flash zip"
A ROM is a package including the system (/system) and the kernel (boot.img) and MUST be flashed from custom recovery, even if its a stock rom (like a guru reset rom or a stock odexed rom)
adb doesnt work on my device anymore... adb devices gives me an empty list...
Click to expand...
Click to collapse
Probably because your drivers are not installed correctly. this can be verified from Windows device manager. When the phone is booted in recovery, check that the phone is listed as a "android ADB interface".
and i cant flash the other TWRP version ... it gives me this problem :
target reported max download size of 1514139648 bytes
sending 'customrecovery' (10854 KB)...
OKAY [ 1.767s]
writing 'customrecovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.709s
Click to expand...
Click to collapse
FAILED (remote: signature verify fail) = Locked or Relocked bootloader, you must have an unlocked bootloader to flash recovery.
@angizwa follow procedure linked at post #2

nope, no android ADB in my driver list when in recovery oO , but i can see android usb devices when in fastboot... i guess i have the wrong drivers... ill see if i can find them, i really hope that was the problem oO

angizwa said:
hmm i tried flashing the stock rom,
i got this error
http://i.imgur.com/XzOOJYE.jpg
what does this mean ?
oh and after relocking, it gave me a signature check (remote : 12 ) fail... :/
Click to expand...
Click to collapse
you flash roms with custom recovery (TWRP) not with fastboot. Why did you relock the bootloader ? unlock it reflash TWRP 2.6.3.3 then sideload / Push the rom
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot

@clsA
yes i tried sideload before, but as i said, my adb doesnt work... adb devices does show me an empty list ...

angizwa said:
@clsA
yes i tried sideload before, but as i said, my adb doesnt work... adb devices does show me an empty list ...
Click to expand...
Click to collapse
Then you need to fix your drivers
see post 2 of the superguide
http://forum.xda-developers.com/showthread.php?t=2541082

@clsA
ok thanks, ill try fixing them

[Q] Htc One M7- deleted operating system. Relocked bootloader

Hi guys,
I have a big problem with my HTC One. I wanted to give it to the service, but it costs a lot of money, maybe I will find some help on XDA hopefully.
My bootloader info looks like this:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT- 1.57.0000
RADIO- 4T.27.3218.14
OpenDSP-v32.120.274.0909
OS-5.11.401.10
eMMC-boot 2048MB
May 5 2014,23:16:29.0
I deleted my system partition in twrp recovery. I can get only to bootloader and recovery. I am S-ON all the time, cannot get S-OFF, I get errors all the time using rum runner or firewater. When I type fastboot oem lock, I am stuck in bootloader, cannot enter recovery. Then the bootloader says ***TAMPERED*** ***RELOCKED*** ***SECURITY WARNING***. I really don't know what to do, I'm stuck. Please help :C !!!
Thanks

My fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4332mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.099s

GalaXxXx said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed
(bootloader) imei: removed
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4332mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.099s
Click to expand...
Click to collapse
You should remove your imei and serialno in your previous post. You can use this stock rom zip to go back to stock. It is the same version that you have. Your bootloader must be LOCKED or RELOCKED. Move the file to your adb/fastboot folder and rename it rom.zip. Open a command window on the same folder then type the following:
Code:
[B][I]adb reboot bootloader[/I][/B]
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip rom.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip rom.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse

Thanks a lot @majmoz
I'm downloading zip file now (slow internet 2 hours remaining). I will try your method, and let you know how it went.

doesn't work ;/
@majmoz , it doesn't work .
I did everything you said and when flashing it says "FAILED (remote: 12 signature verify fail)". Did this command 2 times as you instructed.
The second thing is that the "adb reboot bootloader" command didn't work, cmd said that device not found.
What should I do ?

GalaXxXx said:
@majmoz , it doesn't work .
I did everything you said and when flashing it says "FAILED (remote: 12 signature verify fail)". Did this command 2 times as you instructed.
The second thing is that the "adb reboot bootloader" command didn't work, cmd said that device not found.
What should I do ?
Click to expand...
Click to collapse
Does you bootloader still say "Relocked"? Let try to run the stock firmware 5.11.401.10 using the same method, just rename the download to firmware.zip change the rom.zip in the procedure to firmware.zip.
For adb not working take a look at FAQ Q#2.

My bootloader says TAMPERED RELOCKED SECURITY WARNING
I don't think adb works in bootloader, right ?
The firmware.zip worked, (there was the green bar etc.), but the phone is still not rebooting into system.
hmm... there is no custom recovery anymore, just a phone with red sign. And in bootloader it says only tampered and relocked. Without security warning. @majmoz

GalaXxXx said:
My bootloader says TAMPERED RELOCKED SECURITY WARNING
I don't think adb works in bootloader, right ?
The firmware.zip worked, (there was the green bar etc.), but the phone is still not rebooting into system.
hmm... there is no custom recovery anymore, just a phone with red sign. And in bootloader it says only tampered and relocked. Without security warning. @majmoz
Click to expand...
Click to collapse
You are correct adb does not work in bootloader. When the firmware completed it installed the stock recovery. Since you erased the system partition there is no OS installed. You can try to run the RUU again and it will probably pass now since you have the correct firmware. If this is successful, you will have stock rom and stock firmware on your phone.
What did you mean by give to service?

majmoz said:
You are correct adb does not work in bootloader. When the firmware completed it installed the stock recovery. Since you erased the system partition there is no OS installed. You can try to run the RUU again and it will probably pass now since you have the correct firmware. If this is successful, you will have stock rom and stock firmware on your phone.
What did you mean by give to service?
Click to expand...
Click to collapse
There is an unbrick service here in the forum
I would imagine that's what he's referring to

You are correct adb does not work in bootloader. When the firmware completed it INSTALLED the stock recovery. Since you erased the system partition there is no OS installed. You can try to run the RUU again and it will probably pass now since you have the correct firmware. If this is successful, you will have stock rom and stock firmware on your phone.
What did you mean by give to service?
Click to expand...
Click to collapse
There is an unbrick service here in the forum
I would imagine that's what he's referring to
Click to expand...
Click to collapse
No no, I have a service nearby here in my town. They said they can restore the phone for $30.
I will try the RUU file now, hope it works. I'll be informing what is the status of my "operation" @majmoz @ajbiz11
P.S. How to quote ? You know (Originally Posted by etc.)

GalaXxXx said:
I did everything you said and when flashing it says "FAILED (remote: 12 signature verify fail)".
Click to expand...
Click to collapse
@majmoz I don't think this zip can be flashed using "fastboot flash zip rom.zip", with s-on he can only flash signed ruu from HTC and afaik, htc never released any 5.11.401.10 signed ruu
There is a flashable aroma zip (guru reset) for his version here: https://www.androidfilehost.com/?fid=23501681358543706
to be flashed with a custom recovery (require to unlock the bootloader again)

Yeah @alray , I need to have a 5.11.401.10 signed RUU, but there is no such file avaible to download.
Now, I will unlock my bootloader again, flash custom recovery (TWRP) , and try flash guru reset in this recovery.
Well, I don't really remember, but I think I tried this (maybe with not the same version of guru reset), but I was stuck on "Installation procces" It was 0 % all the time. Let's see how it works out this time with this version of guru.

@alray
I unlocked my bootloader, flashed TWRP, I used adb to push the .zip to sdcard, but the problem now is that the phone says that unable to mount '/data' and unable to mount internal storage. When I click mount in recovery the "data" box doesn't wanna tick .
What should I do ? I'm tired of this ...

Ok, what happened next... I finally did what @alray told me to do. I managed to fix the corrupted data partition, but as I said earlier, when I flash the guru reset in recovery, and start the installation process, it is stuck on 0.00%.
I unlocked the bootloader in order to do this.
No more ideas ? @majmoz ?

GalaXxXx said:
Ok, what happened next... I finally did what @alray told me to do. I managed to fix the corrupted data partition, but as I said earlier, when I flash the guru reset in recovery, and start the installation process, it is stuck on 0.00%.
I unlocked the bootloader in order to do this.
No more ideas ? @majmoz ?
Click to expand...
Click to collapse
What version of TWRP are you using? 2.6.3.3 or 2.8.0.1? I'm pretty sure you checked the MD5 of the files you downloaded.

I'm using TWRP v2.8.0.2. What do you mean by saying you're pretty sure I checked the MD5? I didn't .. @majmoz

GalaXxXx said:
I'm using TWRP v2.8.0.2. What do you mean by saying you're pretty sure I checked the MD5? I didn't .. @majmoz
Click to expand...
Click to collapse
You should always check the MD5 of downloaded files to ensure they did not get corrupted during the downloading process. The MD5 is generally noted on the download site. Here is a how to check the MD5.

I also recommend to use 2.6.3.3 instead of 2.8+

Ohh my god, finally did it !!! Thank you a lot guys !!! I was trying guru reset earlier with unlocked bootloader too, but the twrp version was wrong... ohh, everything because of this new version of twrp.... But thanks, I have my system back . I will be able to do OTA updates now ?
 @majmoz @alray

GalaXxXx said:
Ohh my god, finally did it !!! Thank you a lot guys !!! I was trying guru reset earlier with unlocked bootloader too, but the twrp version was wrong... ohh, everything because of this new version of twrp.... But thanks, I have my system back . I will be able to do OTA updates now ?
@majmoz @alray
Click to expand...
Click to collapse
you should be able to do ota if you have selected to install stock recovery in the aroma installer.

[Q] Help Emergency HTC one issues!!!!

Hello,
Okay so I had an HTC one that was stuck on the boot screen. Well I had a feeling it was rooted but was not sure because clorkworkmod always said boot with "root access" which I ignored. So first off I found something called guru reset 2.24.401.8 which was my version of my phone. So I used adb side load to move to my device then installed it. It worked fine and I was excited however it booted to a black screen with only the battery status, reception meter, and time bar. When I tried using recovery again the phone would show a green sign and then a red exclamation mark sign. I tried for so long going into recovery, but to no avail. I used fast boot to flash recovery and erase cache but did not work. I am terribly stuck and need help.
MIDN0710000
Version:2.24.401.8
Please help a brother in need.
Thank you
Sorry for any mistake wrote this really late.

kobster98 said:
Hello,
Okay so I had an HTC that was stuck on the boot screen. Well I had a feeling it was rooted but was not sure because clorkworkmod always say boot with "root access" which I ignored. So first off I found something called guru reset 2.24.401.8 which was my version of my phone. So I use adb side load to move to my device then install it. It worked fine and I was excited however it booted a black screen with only the battery status reception meter and time. When I tried using recovery again the phone would show a green sign and then a red exclamation mark sign. I tried for so long going in recovery to no avail. I use fast boot to flash recovery and erase cache but did not work. I am terribly stuck and need help.
MIDN0710000
Version:2.24.401.8
Please help a brother in need.
Thank you
Sorry for any mistake wrote this really late.
Click to expand...
Click to collapse
When you flashed the Guru Reset you must have selected "stock recovery" because that is the black screen with green or red triangle. Follow these steps:
Get TWRP 2.6.3.3 from: http://techerrata.com/browse/twrp2/m7
(make sure MD5 is correct, that site does not play nice with download managers)
in bootloader/FASTBOOT USB:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader

Thanks
I have been able to do it and thank you, but i am having issue with adb my fastboot work and is able to find my devices but adb does not.

kobster98 said:
I have been able to do it and thank you, but i am having issue with adb my fastboot work and is able to find my devices but adb does not.
Click to expand...
Click to collapse
ADB works in OS/Android with USB Debugging enabled in Developer Options and in Recovery Mode. It will not work if the phone is in bootloader/FASTBOOT USB.

About to give up
Okay you have been great help, and i need major help i have tried every thing, my phone doesn't boot up properly and just has a black screen, i have tried using guru reset 2.24.401.8 to reset and it doesnt work, i tried with an unlocked bootloader, but with S-On and i read an article saying guru reset should work regardless if it is s-on or s-off. im not sure though. I am not stuck because my phone Hboot is 1.54 and i have tried using rumrunner but doesnt work because my adb only work in recovery. I would like to S-off my phone to be able to install the guru reset. rom. I have tried using RUU's but cant find my radio version. is there any possible way to S-off my phone without an OS to install unto. Or is there any way to re-install my OS i am running out of ideas. Thank you very much!!

kobster98 said:
Okay you have been great help, and i need major help i have tried every thing, my phone doesn't boot up properly and just has a black screen, i have tried using guru reset 2.24.401.8 to reset and it doesnt work, i tried with an unlocked bootloader, but with S-On and i read an article saying guru reset should work regardless if it is s-on or s-off. im not sure though. I am not stuck because my phone Hboot is 1.54 and i have tried using rumrunner but doesnt work because my adb only work in recovery. I would like to S-off my phone to be able to install the guru reset. rom. I have tried using RUU's but cant find my radio version. is there any possible way to S-off my phone without an OS to install unto. Or is there any way to re-install my OS i am running out of ideas. Thank you very much!!
Click to expand...
Click to collapse
There is no way to s-off without a Rom on the phone.
You can push a Rom to the phone using adb in recovery. Which recovery are you using. You should use TWRP 2.6.3.3 to avoid any problems installing the Guru Reset Rom.
Put the Rom in your adb/fastboot folder and rename it to rom.zip. Connect adb in recovery and in the command window type.
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push completes several minutes. When it's done install the Rom with twrp recovery.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

rom install
i tried and installed a guru reset rom,however when i installed it just boots to a plain blackscreen with only the battery status, time, and reception bar showing, yes i am using twrp 2.6.3.3.
thank you for reply

kobster98 said:
i tried and installed a guru reset rom,however when i installed it just boots to a plain blackscreen with only the battery status, time, and reception bar showing, yes i am using twrp 2.6.3.3.
thank you for reply
Click to expand...
Click to collapse
Did you install the reset Rom with Twrp 2.6.3.3 your first post indicates you used CWM
Can you please post the out put from
Code:
fastboot getvar all
Please remove imei and serial numbers before posting.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Help
Thanks,
Yea i have twrp 2..6.3.3 installed as recovery, i did have clorkworkmod previously but guru reset wiped my data after installation. So i switched to twrp recovery. What Rom or RUU should i install?
Thanks for your time. Info you need is below.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-ON
(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: 4319mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

kobster98 said:
Thanks,
Yea i have twrp 2..6.3.3 installed as recovery, i did have clorkworkmod previously but guru reset wiped my data after installation. So i switched to twrp recovery. What Rom or RUU should i install?
Thanks for your time.
Info you need is below.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-ON
(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: 4319mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Here is the only RUU I could find that is a higher version than yours. There have been people who have bricked their phone by jumping version so I have provide the firmware for the version from 2.24.401.8 to RUU 4.19.401.9.
Firmware 3.62.401.1
Firmware 4.19.401.8
RUU 4.19.401.9
To flash the firmware, place the firmware in your adb/fastboot folder, open a command window in your adb/fastboot folder:
Code:
[B][I]adb reboot bootloader[/I][/B]
After that, type:
Code:
fastboot oem lock
Type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip [COLOR="Purple"]name_of_firmware.zip[/COLOR][/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip [COLOR="Purple"]name_of_firmware.zip[/COLOR][/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot-bootloader[/I][/B]
Click to expand...
Click to collapse
After the last firmware reboots, then run the RUU.

Follow @majmoz instructions, but for the record the RUU should work fine after flashing 3.62.401.1 firmware. As the RUU will contain the full firmware up to 4.19.401.9. So no risk of firmware mismatch.
majmoz said:
Here is the only RUU I could find that is a higher version than yours. There have been people who have bricked their phone by jumping version so I have provide the firmware for the version from 2.24.401.8 to RUU 4.19.401.9.
Firmware 3.62.401.1
Firmware 4.19.401.8
RUU 4.19.401.9
To flash the firmware, place the firmware in your adb/fastboot folder, open a command window in your adb/fastboot folder:
After the last firmware reboots, then run the RUU.
Click to expand...
Click to collapse
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Thanks
So i should use the 4.19.401.9 RUU, but why am i locking the bootloader, doesnt it need to be unlocked. I will try your process. I am very grateful.

kobster98 said:
So i should use the 4.19.401.9 RUU, but why am i locking the bootloader, doesnt it need to be unlocked. I will try your process. I am very grateful.
Click to expand...
Click to collapse
Flash the 3.62.401.1 firmware as per majmoz instructions. Then you can use the RUU to update your phone to kit Kat.
You have to be unlocked to flash Custom software. But the RUU and Firmware are signed Stock files. Because your s-on you must be relocked to flash them
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Thanks
okay so i tried running the steps but my phone did not reboot once, and bootloader say successful, but i get an error.
Here:
C:\Users\Family\Desktop\root\adt-bundle-windows-x86_64-20140702\sdk\platform-too
ls>Fastboot oem rebooutruu
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.002s]
finished. total time: 0.002s
C:\Users\Family\Desktop\root\adt-bundle-windows-x86_64-20140702\sdk\platform-too
ls>fastboot flash zip 3.62.401.1_full_stock_sense_firmware.zip
sending 'zip' (97331 KB)...
OKAY [ 5.001s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 15.428s
C:\Users\Family\Desktop\root\adt-bundle-windows-x86_64-20140702\sdk\platform-too
ls>fastboot flash zip 3.62.401.1_full_stock_sense_firmware.zip
sending 'zip' (97331 KB)...
OKAY [ 5.026s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 15.452s

kobster98 said:
okay so i tried running the steps but my phone did not reboot once, and bootloader say successful, but i get an error.
Here:
C:\Users\Family\Desktop\root\adt-bundle-windows-x86_64-20140702\sdk\platform-too
ls>Fastboot oem rebooutruu
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.002s]
finished. total time: 0.002s
Click to expand...
Click to collapse
Your command to rebootRUU is incorrect it is case sensitive. You also appear to have an extra "u" in there
Code:
fastboot oem rebootRUU
After this command your phone will reboot to a screen with a silver HTC logo. This is RUU mode
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Misunderstanding
Sorry but the problem is that i get Failed (remote:12 signature verify fail) and it does not flash says finished.

kobster98 said:
Sorry but the problem is that i get Failed (remote:12 signature verify fail) and it does not flash says finished.
Click to expand...
Click to collapse
Yes because your phone is not in ruu mode. You cannot flash the firmware in the bootloader.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Misunderstanding
I am in RUU mode, its a black screen with the HTC logo, but when i type the command to flash the firmware it gives me "failed: 12 signature verify"

kobster98 said:
I am in RUU mode, its a black screen with the HTC logo, but when i type the command to flash the firmware it gives me "failed: 12 signature verify"
Click to expand...
Click to collapse
Ok strange, try this firmware zip instead http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/3.62.401.1.zip
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Thank you bro it worked your a life saver

[Q] hboot 1.44.00 and can't move forward nor backwards

Hi everyone
Been on Cyanogenmod 11-20140424-NIGHTLY-M7 for far too long and wanted to either upgrade Cyanogenmod or, better yet, move to Viper. I'm somewhat skilled with Windows and Linux, but I can't seem getting things to work.
What I've got:
HTC One M7 (unbranded, bought in Switzerland)
Unlocked S-ON
hboot: 1.44.0000
M7-UL PVT SHIP S-ON RH
RADIO-4A.14.3250.13
OpenDSP-v26-120-274-0202
CID: HTC_102
It's rooted and got CWM ROM-Manager installed
Notebook with Windows 8.1, USB 3.0 all around
What I've tried so far:
Getting S-OFF
- Did not work. revone throws an ERROR=1 at me when I try to ./revone -P. I've tried like a hundred times, with su and all.
Then I tried to relock and get an RUU on it:
- Relocking did not work. Neither with revone (./revone -l or -r is successful on the CLI, but does nothing, i.e. still says *** UNLOCKED *** in the bootloader), nor with fastboot...
- ... as fastboot does not work, either. Tried different drivers and all, but fastboot always says < waiting for device >. So fastboot oem lock achieved nothing, either.
Then I just tried to install an RUU to get to JB and hboot 1.55 to then continue with rumrunner. This got stuck at some boot-image showing the HTC logo and the .exe cancelled.
Is USB3.0 breaking my neck here or do I have any other options to get to ViperOne?
Thanks in advance...

From what i've read in here many times, hboot 1.44 isn't compatiable with windows 8. 1. You need to use a windows 7 machine.

dorsetqpr said:
From what i've read in here many times, hboot 1.44 isn't compatiable with windows 8. 1. You need to use a windows 7 machine.
Click to expand...
Click to collapse
Correct
Hoelli169 said:
Hi everyone
Been on Cyanogenmod 11-20140424-NIGHTLY-M7 for far too long and wanted to either upgrade Cyanogenmod or, better yet, move to Viper. I'm somewhat skilled with Windows and Linux, but I can't seem getting things to work.
What I've got:
HTC One M7 (unbranded, bought in Switzerland)
Unlocked S-ON
hboot: 1.44.0000
M7-UL PVT SHIP S-ON RH
RADIO-4A.14.3250.13
OpenDSP-v26-120-274-0202
CID: HTC_102
It's rooted and got CWM ROM-Manager installed
Notebook with Windows 8.1, USB 3.0 all around
What I've tried so far:
Getting S-OFF
- Did not work. revone throws an ERROR=1 at me when I try to ./revone -P. I've tried like a hundred times, with su and all.
Then I tried to relock and get an RUU on it:
- Relocking did not work. Neither with revone (./revone -l or -r is successful on the CLI, but does nothing, i.e. still says *** UNLOCKED *** in the bootloader), nor with fastboot...
- ... as fastboot does not work, either. Tried different drivers and all, but fastboot always says < waiting for device >. So fastboot oem lock achieved nothing, either.
Then I just tried to install an RUU to get to JB and hboot 1.55 to then continue with rumrunner. This got stuck at some boot-image showing the HTC logo and the .exe cancelled.
Is USB3.0 breaking my neck here or do I have any other options to get to ViperOne?
Thanks in advance...
Click to expand...
Click to collapse
Windows 8 and hboot 1.44 are not compatible. You should use Windows 7 or better still Linux (preferably ubuntu 32bit)
Sent from my M7 ARHD 84-Kitkat

OK, got my hands on a Linux notebook and managed the relock the bootloader. This led to only being able to boot into Bootloader, Recovery and ROM did always boot into Bootloader.
Then I tried to get a RUU with JB4.3 on the device to be able to run rumrunner on hboot 1.55.
#sudo fastboot flash zip RUU.zip
sending 'zip' (1065710 KB)...
OKAY [ 59.411s}
writing 'zip' ...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 171.238s
Now I unlocked the bootloader again to at least be able to boot into CYM again.
Meh, I'm kinda lost here. I feel confused about RUUs, CIDs, Nandroid Backups and where to go from here.
Any ideas?
Edit:*Here's the fastboot-info
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4128mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Edit2:*OK, I'm stuck in the CYM*launcher. Really kinda lost now D:

Hoelli169 said:
OK, got my hands on a Linux notebook and managed the relock the bootloader. This led to only being able to boot into Bootloader, Recovery and ROM did always boot into Bootloader.
Then I tried to get a RUU with JB4.3 on the device to be able to run rumrunner on hboot 1.55.
#sudo fastboot flash zip RUU.zip
sending 'zip' (1065710 KB)...
OKAY [ 59.411s}
writing 'zip' ...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 171.238s
Now I unlocked the bootloader again to at least be able to boot into CYM again.
Meh, I'm kinda lost here. I feel confused about RUUs, CIDs, Nandroid Backups and where to go from here.
Any ideas?
Edit:*Here's the fastboot-info
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4128mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Edit2:*OK, I'm stuck in the CYM*launcher. Really kinda lost now D:
Click to expand...
Click to collapse
Download this recovery. http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Put the file in your fastboot folder.
Download this Rom. Put the zip in your fastboot folder and rename it rom.zip
http://www.htc1guru.com/dld/guru_reset_m7_1-29-401-13-zip/
Flash the recovery with fastboot
Code:
fastboot erase cache
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot reboot-bootloader
Select recovery from the bootloader menu. While in TWRP recovery. Push the Rom. Type
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push us complete. Do a full wipe and install the Rom. During the install setup choose these options.
Stock recovery = yes
Stock radio = yes
Root = No
You will now have full stock Rom and recovery. Reboot the device and go to settings>about>Software Updates. Download and install the OTA update. Repeat process untill your on JB 3.xx.401.x firmware. Then use rumrunner to gain s-off. :good:
Sent from my M7 ARHD 84-Kitkat

Danny201281 said:
Download this recovery.
Put the file in your fastboot folder.
Download this Rom. Put the zip in your fastboot folder and rename it rom.zip
Flash the recovery with fastboot
Code:
fastboot erase cache
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
Worked!
Select recovery from the bootloader menu. While in TWRP recovery. Push the Rom. Type
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push us complete. Do a full wipe and install the Rom. During the install setup choose these options.
Click to expand...
Click to collapse
This didn't work. While in TWRP, adb was not able to connect. Funnily enough, flashing TWRP*allowed me to boot into CYM again. Activated USB*Debugging and allowed the Host to connect, but still no luck in TWRP.
But since I*had access again I* just copied the Guru image over USB*to the Sdcard, booted back into TWRP*and installed the ROM*manually.
Stock recovery = yes
Stock radio = yes
Root = No
You will now have full stock Rom and recovery. Reboot the device and go to settings>about>Software Updates. Download and install the OTA update. Repeat process untill your on JB 3.xx.401.x firmware.
Click to expand...
Click to collapse
219486214 reboots later... JB*3.62.401.1, hooray!
Then use rumrunner to gain s-off. :good:
Click to expand...
Click to collapse
Another adventure... In the official instructions it says unlocked OR*rooted, so I*did not bother with rooting.
rumrunner then failed and damaged Recovery leading to not being able to boot into TWRP*and thus being unable to install SuperSu zip.
Had to reflash recovery, install SuperSu and run rumrunner again... Which again failed (becuase the screen was off, I did not see that ADB*Shell requested root).
After a couple of tries now it worked ^_^
Thanks a lot for your explanations.
Now I just have to find out how to get to Firmware 5.0.2 to install the latest ViperOne.
Edit:*When I try to run the OTA*update to 4.19.401.11 it just boots into Recovery

Hoelli169 said:
Worked!
This didn't work. While in TWRP, adb was not able to connect. Funnily enough, flashing TWRP*allowed me to boot into CYM again. Activated USB*Debugging and allowed the Host to connect, but still no luck in TWRP.
But since I*had access again I* just copied the Guru image over USB*to the Sdcard, booted back into TWRP*and installed the ROM*manually.
219486214 reboots later... JB*3.62.401.1, hooray!
Another adventure... In the official instructions it says unlocked OR*rooted, so I*did not bother with rooting.
rumrunner then failed and damaged Recovery leading to not being able to boot into TWRP*and thus being unable to install SuperSu zip.
Had to reflash recovery, install SuperSu and run rumrunner again... Which again failed (becuase the screen was off, I did not see that ADB*Shell requested root).
After a couple of tries now it worked ^_^
Thanks a lot for your explanations.
Now I just have to find out how to get to Firmware 5.0.2 to install the latest ViperOne.
Edit:*When I try to run the OTA*update to 4.19.401.11 it just boots into Recovery
Click to expand...
Click to collapse
You need stock rom and recovery to install OTA updates. You can just flash the rom again with stock recovery to take further OTAs.
But as your now s-off you can just flash the firmware manually. You don't need to re lock the bootloader again. That's only for s-on users.
You can download the rest of the firmware updates here https://www.androidfilehost.com/?w=files&flid=32777
You must flash at least one zip for each firmware version. I.e if your on 3.xx.401.x then you have to flash
4.xx.401.x
5.xx.401.x
6.xx.401.x
7.xx.401.x
Then you can flash twrp and install a lollipop rom. You should have the rom on the internal storage before you start as the device won't boot after flashing the firmware as it will replace the stock boot.img. So you will need to flash a rom before it will boot. :good:
Commands for flashing the firmware zip as follows.
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip "name-of-firmware".zip
fastboot flash zip "name-of-firmware".zip
fastboot reboot-bootloader
Flash TWRP, Install Rom, Done :good:
Sent from my SM-T230 using Tapatalk

Danny201281 said:
You need stock tom and recovery to install OTA updates. You can just flash the rom again with stock recovery to take further OTAs.
But as your now s-off you can just flash the firmware manually. You don't need to re lock the bootloader again. That's only for s-on users.
You can download the rest of the firmware updates here
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
I thought I had to adhere to some upgrade path when handling firmwares but if that's not the case I'll be happy to use the latest, thanks!

Hoelli169 said:
I thought I had to adhere to some upgrade path when handling firmwares but if that's not the case I'll be happy to use the latest, thanks!
Click to expand...
Click to collapse
See my edited post above. You can't just flash the latest firmware. It might work but there's a risk of bricking your phone if you skip firmware versions
Sent from my SM-T230 using Tapatalk

Danny201281 said:
See my edited post above. You can't just flash the latest firmware. It might work but there's a risk of bricking your phone if you skip firmware versions
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
Ahh yes. Well, another interesting one going through the firmware updates. Going from 5.xx to 6.xx nearly killed my phone. Screen went black no matter how long I*pressed the power button and connecting through USB*mounted some strange folders on the device.
Luckily found Dexter's thread and his unbricking script solved the problem:
http://forum.xda-developers.com/showthread.php?t=2770684
Now ViperOne is updating, yay ^__^

Hoelli169 said:
Ahh yes. Well, another interesting one going through the firmware updates. Going from 5.xx to 6.xx nearly killed my phone. Screen went black no matter how long I*pressed the power button and connecting through USB*mounted some strange folders on the device.
Luckily found Dexter's thread and his unbricking script solved the problem:
http://forum.xda-developers.com/showthread.php?t=2770684
Now ViperOne is updating, yay ^__^
Click to expand...
Click to collapse
[emoji28] few!! Yeah firmware can be tricky. Glad you got it sorted though. Dexter's thread is a life saver. . Enjoy lollipop :good:
Sent from my SM-T230 using Tapatalk