Database Develop

[Q] Stuck In TWRP. Please help.

Hello,
I unlocked my bootloader through HTC, placed TWRP in the same folder such as adb and then booted into it. However, when I try to run any of the options such as install, it prompts me to swipe to unlock but I'm unable to swipe to unlock.
I've found that if I press the hard home key, I can then swipe to unlock, but it acts as if I never selected an option. Has anyone had this happen?

rpinney said:
Hello,
I unlocked my bootloader through HTC, placed TWRP in the same folder such as adb and then booted into it. However, when I try to run any of the options such as install, it prompts me to swipe to unlock but I'm unable to swipe to unlock.
I've found that if I press the hard home key, I can then swipe to unlock, but it acts as if I never selected an option. Has anyone had this happen?
Click to expand...
Click to collapse
Make sure you have the right firmware/TWRP combination. 4.2.2 firmwares work with TWRP 2.6.0.1 (TWRP was updated to support the touch drivers in the 2.17 and 2.24 version firmwares. 4.1.2 firmwares work with an M7 specific version of TWRP 2.5.0.0.

dgtiii said:
Make sure you have the right firmware/TWRP combination. 4.2.2 firmwares work with TWRP 2.6.0.1 (TWRP was updated to support the touch drivers in the 2.17 and 2.24 version firmwares. 4.1.2 firmwares work with an M7 specific version of TWRP 2.5.0.0.
Click to expand...
Click to collapse
Crap. I'm using 2.6.0.0, but it was the one that was listed to use if you have a Sprint One. It didn't give an option to use .01.

rpinney said:
Crap. I'm using 2.6.0.0, but it was the one that was listed to use if you have a Sprint One. It didn't give an option to use .01.
Click to expand...
Click to collapse
Sprint is different, I am not sure of the version for your device if its Sprint. Did you check on the Sprint HTC One forum?

dgtiii said:
Sprint is different, I am not sure of the version for your device if its Sprint. Did you check on the Sprint HTC One forum?
Click to expand...
Click to collapse
I looked through and did a search, but I didn't see anything relevant. Should I repost in there?

rpinney said:
I looked through and did a search, but I didn't see anything relevant. Should I repost in there?
Click to expand...
Click to collapse
Yeah, I would repost there too!

dgtiii said:
Yeah, I would repost there too!
Click to expand...
Click to collapse
I actually ended up figuring out how to fix:
Version 2.6.0.0 from TWRP is bad. What you'll have to do is download 2.5.0.0. and put the recovery file into your android\sdk\platform-tools folder and use this command to push it to your phone: fastboot flash recovery openrecovery-twrp-2.5.0.0-m7wls.img.

Yep, that's how you flash a recovery. Good job, I'm glad you figured it out! Sorry I couldn't help more.

Stuck on twrp can't swipe
I really need help on this one. I been searching for the night till today morning and nver find a soulution to problem.
I have HTC One Lte. International since i bought it one of the mall in Qatar. Yesterday, i Decide to Unlock bootload and Root it. I use AIO 3.1.
Now its tampered and unlocked and select perm root.
I booted on system and find the SU is not intalled. So what i do is fastboot again and select perm. boot again. then i reboot after. Then After entering to twrp 2.5 recovery. I can swipe the screen. then i search and find 2.6.1.download it, but when i try connect it to AIO. Can find the my phone. So i decide to do it manually by going to cmd and push twrp 2.6.1.
Now when i booted, twrp is working well. i was able to back up. but after rebooting to system. twrp 2.5.0 open up. Now my phone running both twrp 2.5 and 2.6.1!
Thsi the detail of my phone.
(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.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4095mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Hope someone can help.
---------- Post added at 10:01 AM ---------- Previous post was at 09:57 AM ----------
By the way. Hope someone can tell me step by step on resolving this issue. i can only fast on cmd but not on AIO. I hope i didnt brick my phone.
Manay thanks for those will reply to my SOS!

blackknightrealms said:
I really need help on this one. I been searching for the night till today morning and nver find a soulution to problem.
I have HTC One Lte. International since i bought it one of the mall in Qatar. Yesterday, i Decide to Unlock bootload and Root it. I use AIO 3.1.
Now its tampered and unlocked and select perm root.
I booted on system and find the SU is not intalled. So what i do is fastboot again and select perm. boot again. then i reboot after. Then After entering to twrp 2.5 recovery. I can swipe the screen. then i search and find 2.6.1.download it, but when i try connect it to AIO. Can find the my phone. So i decide to do it manually by going to cmd and push twrp 2.6.1.
Now when i booted, twrp is working well. i was able to back up. but after rebooting to system. twrp 2.5.0 open up. Now my phone running both twrp 2.5 and 2.6.1!
Thsi the detail of my phone.
(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.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4095mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Hope someone can help.
---------- Post added at 10:01 AM ---------- Previous post was at 09:57 AM ----------
By the way. Hope someone can tell me step by step on resolving this issue. i can only fast on cmd but not on AIO. I hope i didnt brick my phone.
Manay thanks for those will reply to my SOS!
Click to expand...
Click to collapse
So what version works? 2.6.0.1?
Which version does your phone boot into when you select 'recovery' in bootloader?
Can you still access your working phone/ROM?

blackknightrealms said:
I really need help on this one. I been searching for the night till today morning and nver find a soulution to problem.
I have HTC One Lte. International since i bought it one of the mall in Qatar. Yesterday, i Decide to Unlock bootload and Root it. I use AIO 3.1.
Now its tampered and unlocked and select perm root.
I booted on system and find the SU is not intalled. So what i do is fastboot again and select perm. boot again. then i reboot after. Then After entering to twrp 2.5 recovery. I can swipe the screen. then i search and find 2.6.1.download it, but when i try connect it to AIO. Can find the my phone. So i decide to do it manually by going to cmd and push twrp 2.6.1.
Now when i booted, twrp is working well. i was able to back up. but after rebooting to system. twrp 2.5.0 open up. Now my phone running both twrp 2.5 and 2.6.1!
---------- Post added at 10:01 AM ---------- Previous post was at 09:57 AM ----------
[/COLOR]By the way. Hope someone can tell me step by step on resolving this issue. i can only fast on cmd but not on AIO. I hope i didnt brick my phone.
Manay thanks for those will reply to my SOS!
Click to expand...
Click to collapse
I am not sure what you mean when you said you cannot connect to AIO, I assume you mean ADB. You may have to update your SDK files to get ADB to work.
Next issue. What do you mean when "So i decide to do it manually by going to cmd and push twrp 2.6.1". Fastboot flash recovery recovery.img is the command you need to upgrade your TWRP version (for example, fastboot flash recovery TWRP_2.6.0.1.img, or whatever the name of your TWRP file is). I think you still have TWRP version 2.5 installed, use the command I listed to install 2.6.01. Make sure the 2.6.0.1 file is in the same folder as your fastboot SDK files.

Thsi what happen. I use all in onw toolkit 3.1. done everything there.tampered and unlock.. I rebooted my One. then i see there is no supersu. so i fastboot again and push perm root on ALL in One toolkit. the reboot. then TWRP shown which i can't swipe. i fastboot again. then try connecting it again to AIO 3.1 but device not detected. So i decided by using adb by pushing TWRP 2.6.1 which i find. It load. go to recovery. backup.install SU. the reboot to to system. After it reboot to HTC logo. Then TWRP 2.5.0 showned next. then i can't swt to unlock or even the butoon are not running.
Apology. i kind noob in this way and trying to find answer for the pas 25 hrs. kinda paranoid. thanks for reply too. hope this can be solved
---------- Post added at 11:44 AM ---------- Previous post was at 11:37 AM ----------
redbull123 said:
So what version works? 2.6.0.1?
Which version does your phone boot into when you select 'recovery' in bootloader?
Can you still access your working phone/ROM?
Click to expand...
Click to collapse
2.6.01. is working. but when i boot to system. it rebooted back to 2.5.0
By using All in One tool kit. Not possible. but by using CMD line. I was able to access detail of my phone. how can i remove twrp 2.5??/
so 2.6.1 will be remain. Still now i can able to pass 2.5 to reboot on my phone..
---------- Post added at 11:50 AM ---------- Previous post was at 11:44 AM ----------
dgtiii said:
I am not sure what you mean when you said you cannot connect to AIO, I assume you mean ADB. You may have to update your SDK files to get ADB to work.
Next issue. What do you mean when "So i decide to do it manually by going to cmd and push twrp 2.6.1". Fastboot flash recovery recovery.img is the command you need to upgrade your TWRP version (for example, fastboot flash recovery TWRP_2.6.0.1.img, or whatever the name of your TWRP file is). I think you still have TWRP version 2.5 installed, use the command I listed to install 2.6.01. Make sure the 2.6.0.1 file is in the same folder as your fastboot SDK files.
Click to expand...
Click to collapse
i place 2.6.1 along side of c: android. Inside this folder are adb exe,adbwinapi.dll, fastboot and twrp 2.6.1. I already push this version and it work. but i thought it will over write twrp 2.5.
Should i put back the files inside the folder of skd??
Where is the command to install this 2.6.1 and over write or remove 2.5.?

blackknightrealms said:
Thsi what happen. I use all in onw toolkit 3.1. done everything there.tampered and unlock.. I rebooted my One. then i see there is no supersu. so i fastboot again and push perm root on ALL in One toolkit. the reboot. then TWRP shown which i can't swipe. i fastboot again. then try connecting it again to AIO 3.1 but device not detected. So i decided by using adb by pushing TWRP 2.6.1 which i find. It load. go to recovery. backup.install SU. the reboot to to system. After it reboot to HTC logo. Then TWRP 2.5.0 showned next. then i can't swt to unlock or even the butoon are not running.
Apology. i kind noob in this way and trying to find answer for the pas 25 hrs. kinda paranoid. thanks for reply too. hope this can be solved
---------- Post added at 11:44 AM ---------- Previous post was at 11:37 AM ----------
2.6.01. is working. but when i boot to system. it rebooted back to 2.5.0
By using All in One tool kit. Not possible. but by using CMD line. I was able to access detail of my phone. how can i remove twrp 2.5??/
so 2.6.1 will be remain. Still now i can able to pass 2.5 to reboot on my phone..
Click to expand...
Click to collapse
Ok, first of all - stop using the toolkit.
Go into fastboot in your bootloader so it shows 'FASTBOOT USB' then command
Code:
fastboot devices
If your device shows, command
Code:
fastboot erase cache
Once this is done, make sure your 2.6.0.1.img file is in your fastboot folder and command
Code:
fastboot flash recovery name_of_your_2.6.0.1_recovery.img

redbull123 said:
Ok, first of all - stop using the toolkit.
Go into fastboot in your bootloader so it shows 'FASTBOOT USB' then command
Code:
fastboot devices
If your device shows, command
Code:
fastboot erase cache
Once this is done, make sure your 2.6.0.1.img file is in your fastboot folder and command
Code:
fastboot flash recovery name_of_your_2.6.0.1_recovery.img
Click to expand...
Click to collapse
ok. this what i do as instructed.
C:\Android>fastboot devices
XXXXXXXXX fastboot
C:\Android>fastboot erase cache
erasing 'cache'...
OKAY [ 0.038s]
finished. total time: 0.038s
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.0.1-m7.img
sending 'recovery' (8014 KB)...
OKAY [ 1.241s]
writing 'recovery'...
OKAY [ 0.648s]
finished. total time: 1.890s
then push power to hboot. then to recovery. Recover to twrp 2.6.1. ok.
first and second try. when i rebooted to system. it recover again to 2.5...

blackknightrealms said:
ok. this what i do as instructed.
C:\Android>fastboot devices
SH35XW900196 fastboot
C:\Android>fastboot erase cache
erasing 'cache'...
OKAY [ 0.038s]
finished. total time: 0.038s
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.0.1-m7.img
sending 'recovery' (8014 KB)...
OKAY [ 1.241s]
writing 'recovery'...
OKAY [ 0.648s]
finished. total time: 1.890s
then push power to hboot. then to recovery. Recover to twrp 2.6.1. ok.
first and second try. when i rebooted to system. it recover again to 2.5...
Click to expand...
Click to collapse
Weird.. I've never heard of that.. So what is it you want to do while in 2.6.0.1? If it were me ( I'm not saying this is the correct answer), I would try flashing a stock ROM like this one then root it later:
http://forum.xda-developers.com/showthread.php?t=2224752
Or now might be a good chance for you to try out a close-to-stock custom ROM such as 'ARHD' which comes already rooted.

redbull123 said:
Weird.. I've never heard of that.. So what is it you want to do while in 2.6.0.1? If it were me ( I'm not saying this is the correct answer), I would try flashing a stock ROM like this one then root it later:
http://forum.xda-developers.com/showthread.php?t=2224752
Or now might be a good chance for you to try out a close-to-stock custom ROM such as 'ARHD' which comes already rooted.
Click to expand...
Click to collapse
Lets say your are me. Which is the best option. Anything support my current version? and will not give me head ache in the end but enjoy the phone?
Does this stock rom will do for my psoted version??pleaseeee! I need this phone!:crying:
Thanks in advance! and waiting for your recommendation.
well, using AIO toolkit and asb is not a good partner.
What do you think is common reason why i arrived to this?? I booted to my system before i reboot to 2.5 which i can't use. so thats why i try 2.6.1. And why this 2.5 kept staying on?? Does the procedure in flashing rom in AOI place it in different place so that this 2.6.1 seem can't over write it??

any one suggestion???

TWRP 2.6.1 and 2.5 on my ONE
Guys! any taker??? please share your knowledge on a noob like me. is there anyway i can remove TWRP 2.5 and leave TWRP 2.6.1?
Appreciate for a big help! thanks

blackknightrealms said:
Guys! any taker??? please share your knowledge on a noob like me. is there anyway i can remove TWRP 2.5 and leave TWRP 2.6.1?
Appreciate for a big help! thanks
Click to expand...
Click to collapse
Did you try flashing a rom like I said?
Sent from my HTC One using xda premium

redbull123 said:
Did you try flashing a rom like I said?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Bro. Do you think the present available rom should work on my unit specs?? Thats the only stopping me. i already collected and download needed files. But after i messed up my One. I have to make sure what step should i do. I will not blame it on anyone. Its really hard to read all post. its really quite long. Just only making sure that a same unit already installed with the same rom. But i'm still thinking which are better. but my first choice will ARHD. Since they put so much improvement. And I only making sure thats the last option i will take. If there is no other solution to resolve my present predicament then so be it. If i was able to flash back my stock rom. So please guide me if you don't mind. So what do you think bro?? Thanks again for responding to my SOS. Good day!

[Q] Reboot loop

Question about HTC One m7
Ive got the reboot loop problem...
Yester i wantend to instal a new rom
After installation its said failed en keeps a reboot problem
now i watch movies and it works perfect until iv come to fastboot zip ruu.zip
it fails ...
youtube.com/watch?v=C0G0hKY4P9Y
I can go to my bootloadermode but not in my recoverymode
So i think everything is away from my phone
Please make it à little easy for me ... Its all new for me
Htc One m7
code: [2.24.401.8]
my bootloader is back Locked
Can u help me please ... i need my htc !!!
grtz

No'one ?
Karroowte said:
Question about HTC One m7
Ive got the reboot loop problem...
Yester i wantend to instal a new rom
After installation its said failed en keeps a reboot problem
now i watch movies and it works perfect until iv come to fastboot zip ruu.zip
it fails ...
youtube.com/watch?v=C0G0hKY4P9Y
I can go to my bootloadermode but not in my recoverymode
So i think everything is away from my phone
Please make it à little easy for me ... Its all new for me
Htc One m7
code: [2.24.401.8]
my bootloader is back Locked
Can u help me please ... i need my htc !!!
grtz
Click to expand...
Click to collapse
No one can help me ? i need my phone !

Karroowte said:
No one can help me ? i need my phone !
Click to expand...
Click to collapse
Need more information, can you post output from "fastboot getvar all" , If you already had a custom recovery installed, you need to re unlock your bootloader for it to work, That may be your problem with it not booting. Can you also post bootloader info.

info
mb_guy said:
Need more information, can you post output from "fastboot getvar all" , If you already had a custom recovery installed, you need to re unlock your bootloader for it to work, That may be your problem with it not booting. Can you also post bootloader info.
Click to expand...
Click to collapse
C:\fastboot>fastboot getvar all
(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) serialno: HT332W900154
(bootloader) imei: 354436053062863
(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: 4295mV
(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
all: Done!
finished. total time: 0.045s
So i must try evrything again just with my bootloader unlock, nog its relocked

Karroowte said:
C:\fastboot>fastboot getvar all
(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) serialno: HT332W900154
(bootloader) imei: 354436053062863
(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: 4295mV
(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
all: Done!
finished. total time: 0.045s
So i must try evrything again just with my bootloader unlock, nog its relocked
Click to expand...
Click to collapse
If you have a custom recovery like TWRP or CWM installed the bootloader must remain unlocked!

no
mb_guy said:
If you have a custom recovery like TWRP or CWM installed the bootloader must remain unlocked!
Click to expand...
Click to collapse
i cant go to my recovery, so i think i dont have one ...

Karroowte said:
i cant go to my recovery, so i think i dont have one ...
Click to expand...
Click to collapse
bootloader isn't recovery. Does the device show relocked in the bootloader screen. If so unlock the bootloader again from the htcdev site, I'm assuming you must have done this once.
Exactly what all did you do yesterday, please explain step by step.

step
mb_guy said:
bootloader isn't recovery. Does the device show relocked in the bootloader screen. If so unlock the bootloader again from the htcdev site, I'm assuming you must have done this once.
Exactly what all did you do yesterday, please explain step by step.
Click to expand...
Click to collapse
i explain what im doing now,
my bootloader is unlocked
firt off all i got a map with evrything in, my zip file and fastboot, .....
shift + right click and open a window
i typ in
fastboot oem rebootRUU
then
fastboot flash zip ruu.zip (i namedt the zip file ruu)

Karroowte said:
i explain what im doing now,
my bootloader is unlocked
firt off all i got a map with evrything in, my zip file and fastboot, .....
shift + right click and open a window
i typ in
fastboot oem rebootRUU
then
fastboot flash zip ruu.zip (i namedt the zip file ruu)
Click to expand...
Click to collapse
What ruu are you flashing?

flash
mb_guy said:
What ruu are you flashing?
Click to expand...
Click to collapse
2.24.401.8

Karroowte said:
2.24.401.8
Click to expand...
Click to collapse
The entire file name would help, also the download link. I think the issue is that that is the wrong file.

wrong
mb_guy said:
The entire file name would help, also the download link. I think the issue is that that is the wrong file. flashable ruu's are .exe not zip And you do need a locked bootloader for those.
Click to expand...
Click to collapse
can u pleas pleas pleas send me the correct thing .... now im 2 days lookin how i fix my HTC one m7
and i realy realy realy want it now fix ...
can u send me the correct Ruu or somthing that fix my htc
thnx mate !

Karroowte said:
can u pleas pleas pleas send me the correct thing .... now im 2 days lookin how i fix my HTC one m7
and i realy realy realy want it now fix ...
can u send me the correct Ruu or somthing that fix my htc
thnx mate !
Click to expand...
Click to collapse
So let's backup a bit here.
Yesterday your phone was stock?
No custom recovery?
Locked bootloader?
You wanted to change rom so found the ruu and attempted to flash
Today the phone bootloops.?
Bootloader is unlocked?
Still no custom recovery?

no
mb_guy said:
So let's backup a bit here.
Yesterday your phone was stock?
No custom recovery?
Locked bootloader?
You wanted to change rom so found the ruu and attempted to flash
Today the phone bootloops.?
Bootloader is unlocked?
Still no custom recovery?
Click to expand...
Click to collapse
Yesterday i had a costum rom, Viper One
and i think unlocked bootloader with ***TAMPERED***
uhm yea i want to change te rom, but i think now there is nothing on my device because he reboot loops and wen i choose recovery he reboot loops
the bootloop is since yesterday when the installation failed from the athor rom, after then he loops
nog is my bootloader unlocked

Think
Karroowte said:
Yesterday i had a costum rom, Viper One
and i think unlocked bootloader with ***TAMPERED***
uhm yea i want to change te rom, but i think now there is nothing on my device because he reboot loops and wen i choose recovery he reboot loops
the bootloop is since yesterday when the installation failed from the athor rom, after then he loops
nog is my bootloader unlocked
Click to expand...
Click to collapse
OK so if you had viper one you must have had a custom recovery. I think this will work for you.
Download and flash TWRP 2.6.3.4 be sure to get the m7_ul version, this should get recovery working again.
http://techerrata.com/browse/twrp2/m7ul
Then use this guru reset file to reset your phone. Read the info and watch the video, then download the one for your device cid and partno
http://www.htc1guru.com/downloads/stock-rom-downloads/
should be this one
http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
You will likely have to use adb push to get the zip to your device, you can do this in twrp (lots of threads on how to do this)
---------- Post added at 09:47 AM ---------- Previous post was at 09:30 AM ----------
Karroowte said:
i explain what im doing now,
my bootloader is unlocked
firt off all i got a map with evrything in, my zip file and fastboot, .....
shift + right click and open a window
i typ in
fastboot oem rebootRUU
then
fastboot flash zip ruu.zip (i namedt the zip file ruu)
Click to expand...
Click to collapse
just another thought. If you haven't started on the guru reset path, You could also try this .
Do what you did here using the ruu you found (assuming it is correct) , but issue the last command twice
so
fastboot oem rebootruu
fastboot flash zip ruu.zip
fastboot flash zip ruu.rip
and see what happens, may be that simple

YEAAH
mb_guy said:
Think
OK so if you had viper one you must have had a custom recovery. I think this will work for you.
Download and flash TWRP 2.6.3.4 be sure to get the m7_ul version, this should get recovery working again.
http://techerrata.com/browse/twrp2/m7ul
Then use this guru reset file to reset your phone. Read the info and watch the video, then download the one for your device cid and partno
http://www.htc1guru.com/downloads/stock-rom-downloads/
should be this one
http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
You will likely have to use adb push to get the zip to your device, you can do this in twrp (lots of threads on how to do this)
---------- Post added at 09:47 AM ---------- Previous post was at 09:30 AM ----------
just another thought. If you haven't started on the guru reset path, You could also try this .
Do what you did here using the ruu you found (assuming it is correct) , but issue the last command twice
so
fastboot oem rebootruu
fastboot flash zip ruu.zip
fastboot flash zip ruu.rip
and see what happens, may be that simple
Click to expand...
Click to collapse
ok thnx, but the download are going slow !
i just instal EZToolkit advanced and flash my recovery, and my recovery works
maybe can i use somthing else ?

link
mb_guy said:
Think
OK so if you had viper one you must have had a custom recovery. I think this will work for you.
Download and flash TWRP 2.6.3.4 be sure to get the m7_ul version, this should get recovery working again.
http://techerrata.com/browse/twrp2/m7ul
Then use this guru reset file to reset your phone. Read the info and watch the video, then download the one for your device cid and partno
http://www.htc1guru.com/downloads/stock-rom-downloads/
should be this one
http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
You will likely have to use adb push to get the zip to your device, you can do this in twrp (lots of threads on how to do this)
---------- Post added at 09:47 AM ---------- Previous post was at 09:30 AM ----------
just another thought. If you haven't started on the guru reset path, You could also try this .
Do what you did here using the ruu you found (assuming it is correct) , but issue the last command twice
so
fastboot oem rebootruu
fastboot flash zip ruu.zip
fastboot flash zip ruu.rip
and see what happens, may be that simple
Click to expand...
Click to collapse
the guru files, dont wanne download ...
you have another rom ?
i can go to recovery maybe just (push file to phone) with another rom ?
an so instal ? or not ?
and so yes, can u tell me wich rom of give me a download link ?

Karroowte said:
ok thnx, but the download are going slow !
i just instal EZToolkit advanced and flash my recovery, and my recovery works
maybe can i use somthing else ?
Click to expand...
Click to collapse
Try your original ruu but do the flash zip twice before reboot.
Can always do the guru later if needed

sd
mb_guy said:
Try your original ruu but do the flash zip twice before reboot.
Can always do the guru later if needed
Click to expand...
Click to collapse
hi guys, a friend of my makes some own Roms ... and he helpt me yesterday and today,
iv got TWRP on my phone back, and i can use Adb,
the problem is, my phone doesnt find my SDcard ... crap ...
does somebody knows how you reset or reinstall your SDCard ?
thnks

Stuck trying to install ROM.

Hey guys,
So I was running 4.2 Viper on my H1, and decided to update to the 4.4 Revolution ROM. After getting the .zip onto the phone, I attempted to install using an older version of CWM. Unfortunately I got stuck in a boot loop where it was attempting to reboot to recovery for about 2 secs, and would flash the CWM screen before going into another loop.
My phone beforehand had suffered from a problem where it was only being charged by certain chargers, and only being recognised on my computer by certain cables. Now, however, it isn't charging at all, nor is it being recognised on my computer by any cable in any USB port (4 cables, 4usb ports). This means that I am stuck with the ROMs that are already in the storage, and I can't transfer a new one (RUU etc) by mounting the phone in recovery.
Fastboot USB, however, seems to still be recognised, so I was able to flash both the latest TWRP and CWM recoveries, and reinstall the Revolution ROM. The ROM installs well using both recoveries (obviously doing full wipes beforehand), but still gets stuck in either a bootloop (CWM) or stuck on the HTC splash screen (TWRP).
Is there any way I can get another ROM onto the phone either in fastboot or alternative methods? Or somehow revert the phone to stock?
I have a backup, but it is on my computer, and therefore isn't transferrable via USB
Sent from my SM-N9005 using Tapatalk

Do I need to manually install the 4.4 kernel?
Sent from my SM-N9005 using Tapatalk

No you dont need to flash kernel before, but did you a full wipe before you installed the rom????

Yep full wipe. I just did a "full" full wipe in TWRP and now I don't even have the ROM. Zip in the phone to attempt a reflash.
I can't mount as USB to side load. Is there another way to push a ROM in fastboot?
Sent from my SM-N9005 using Tapatalk

nick_sixx said:
Yep full wipe. I just did a "full" full wipe in TWRP and now I don't even have the ROM. Zip in the phone to attempt a reflash.
I can't mount as USB to side load. Is there another way to push a ROM in fastboot?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Do you have a otg cabel and a usb stick ?

knudsen81 said:
Do you have a otg cabel and a usb stick ?
Click to expand...
Click to collapse
I don't have an OTG cable. is this likely to help?
Sent from my SM-N9005 using Tapatalk

nick_sixx said:
I don't have an OTG cable. is this likely to help?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
it's to connect a usb storage to you device

knudsen81 said:
it's to connect a usb storage to you device
Click to expand...
Click to collapse
Yeah I have seen them...just don't know if it will help seeing as my phone is only recognizing USB cables in fastboot
Sent from my SM-N9005 using Tapatalk

nick_sixx said:
I don't have an OTG cable. is this likely to help?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
nick_sixx said:
Yeah I have seen them...just don't know if it will help seeing as my phone is only recognizing USB cables in fastboot
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
in recovery you cant activate sideload? but you computer cant find you htc then?

knudsen81 said:
in recovery you cant activate sideload? but you computer cant find you htc then?
Click to expand...
Click to collapse
No...my computer won't recognize the phone in recovery, only in fastboot for some reason.
Similarly it only charges when off
Sent from my SM-N9005 using Tapatalk

nick_sixx said:
No...my computer won't recognize the phone in recovery, only in fastboot for some reason.
Similarly it only charges when off
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
you can flash a stock rom from fastboot a ruu.zip if nothing works

knudsen81 said:
you can flash a stock rom from fastboot a ruu.zip if nothing works
Click to expand...
Click to collapse
Perfect! Do you have a link to a guide handy?
Sent from my SM-N9005 using Tapatalk

nick_sixx said:
Perfect! Do you have a link to a guide handy?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
here is the ruu.zip downloads http://www.htc1guru.com/downloads/ruu-zip-downloads/ and here is the guide http://www.htc1guru.com/guides/return-stock-guide/

Thanks so so much. Will try asap
Sent from my SM-N9005 using Tapatalk

nick_sixx said:
Thanks so so much. Will try asap
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
i hope it works where should be a zip that is the same as yours htc

knudsen81 said:
i hope it works where should be a zip that is the same as yours htc
Click to expand...
Click to collapse
I am getting the following:
./fastboot flash zip ruu.zip
sending 'zip' (1029984 KB)...
OKAY [ 35.459s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 35.709s
Don't know where to go from here?

nick_sixx said:
I am getting the following:
./fastboot flash zip ruu.zip
sending 'zip' (1029984 KB)...
OKAY [ 35.459s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 35.709s
Don't know where to go from here?
Click to expand...
Click to collapse
Post the output of ''fastboot getvar all'' minus your IMEI and SERIALNO and post a link to the ruu you have downloaded.
Also how the device is listed in windows device manager when booted in twrp? ''other devices --> One'' or ''android usb devices --> My HTC'' ?

alray said:
Post the output of ''fastboot getvar all'' minus your IMEI and SERIALNO and post a link to the ruu you have downloaded.
Also how the device is listed in windows device manager when booted in twrp? ''other devices --> One'' or ''android usb devices --> My HTC'' ?
Click to expand...
Click to collapse
./fastboot getvar all
(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.980.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: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 3751mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.042s
I think I used this RUU (using a mac so .exe not an option at this stage)
http://www.htc1guru.com/dld/ruu-zip...0-13_10-33-1150-01_release_311678_signed-zip/
I can fire up bootcamp and use an exe if it will make a difference.
I am using an Australian-delivered unlocked phone

nick_sixx said:
decided to update to the 4.4 Revolution ROM. After getting the .zip onto the phone, I attempted to install using an older version of CWM.
Unfortunately I got stuck in a boot loop
Click to expand...
Click to collapse
4.4 rom require at least TWRP 2.6.3.3
nick_sixx said:
Fastboot USB, however, seems to still be recognised
Click to expand...
Click to collapse
So it looks more like a driver issue than a bad usb cable.
nick_sixx said:
Is there any way I can get another ROM onto the phone either in fastboot or alternative methods? Or somehow revert the phone to stock?
Click to expand...
Click to collapse
If you can't make adb working, buy a usb otg cable as suggested before.
---------- Post added at 10:56 AM ---------- Previous post was at 10:48 AM ----------
nick_sixx said:
./fastboot getvar all
(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.980.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: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 3751mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
http://www.htc1guru.com/dld/ruu-zip...0-13_10-33-1150-01_release_311678_signed-zip/
Click to expand...
Click to collapse
That ruu isn't for your phone! You need the ruu that match your version base (.980), your cid (VODAP021) and your MID (PN0714000). With S-ON you also need to use a ruu of the same or higher version (1.29.980.2 or higher). Unfortunately, there is no RUU available for your phone
With s-on, the only choice you have atm is to flash a rom. Sorry.
---------- Post added at 10:58 AM ---------- Previous post was at 10:56 AM ----------
If you really can't make adb works via twrp then buy a usb otg cable from ebay (pretty cheap) and copy your rom to a usb stick.
plug the otg cable with the usb stick and boot in twrp. Then mount the usb drive and install the rom.
Btw be sure to use latest version of twrp. (2.7.0.0)

alray said:
4.4 rom require at least TWRP 2.6.3.3
So it looks more like a driver issue than a bad usb cable.
If you can't make adb working, buy a usb otg cable as suggested before.
---------- Post added at 10:56 AM ---------- Previous post was at 10:48 AM ----------
That ruu isn't for your phone! You need the ruu that match your version base (.980), your cid (VODAP021) and your MID (PN0714000). With S-ON you also need to use a ruu of the same or higher version (1.29.980.2 or higher). Unfortunately, there is no RUU available for your phone
With s-on, the only choice you have atm is to flash a rom. Sorry.
---------- Post added at 10:58 AM ---------- Previous post was at 10:56 AM ----------
If you really can't make adb works via twrp then buy a usb otg cable from ebay (pretty cheap) and copy your rom to a usb stick.
plug the otg cable with the usb stick and boot in twrp. Then mount the usb drive and install the rom.
Btw be sure to use latest version of twrp. (2.7.0.0)
Click to expand...
Click to collapse
Ok so I got the OTG cable, and can finally mount a USB.
Tried installing InsertCoin ROM, and get this message at the final stages of installation
set_metadata_recursive: some changes failed
The next screeen is "Installation Failed" Installer Status: 7
Any ideas on how to progress?

flash recovery issue

I am having a weird issue that I have not been able to fix it. The only custom recovery that works with my device is twrp 2.6.3.3.
I flashed the newer versions of twrp and the latest version of cwm for m7 - it flashes successfully (no error during flashing), but when trying to enter recovery, it gets stuck at "entering recovery" screen (restart recovery-->shows up the "entering recovery" screen-->for one secong the screen goes black --> goes back to htc splash with "entering recovery" message)
also, the factory recovery WORKS.
I tried:
- fastboot erase cache - reflash recovery
- factory reset - fastboot erase cache - flashed recovery
- I even downgraded the software version: wiped all the phone, including internal storage; flashed twrp 2.6.3.3 - adb loaded 4.19.401.11 stock - flashed factory recovery - updated the official OTAs back to 6.09.401.5
nothing helped.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4048mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.113s
If anyone has some idea why this happens or can give me some new ideas to try, please let me know

Not sure why but I'd stick with 2.6.3.3. It is nice and stable. Newer isn't always better

did you try out the latest Unofficial TWRP 2.7.1.2? im using it and havent looked back, works execelent (at least for me)

nateboi81 said:
Not sure why but I'd stick with 2.6.3.3. It is nice and stable. Newer isn't always better
Click to expand...
Click to collapse
true
the thing is that i need ver. 2.7.0.0 or newer in order to flash for ex slimkat or other roms

seqas said:
did you try out the latest Unofficial TWRP 2.7.1.2? im using it and havent looked back, works execelent (at least for me)
Click to expand...
Click to collapse
is it the version from June or something?
if it's newer version, could you please send me a link for it? i can't seem to find it
Thx

floxrin3 said:
is it the version from June or something?
if it's newer version, could you please send me a link for it? i can't seem to find it
Thx
Click to expand...
Click to collapse
its from 12th Jul
yes, here http://mdmower.cmphys.com/twrp-m7/

seqas said:
its from 12th Jul
yes, here http://mdmower.cmphys.com/twrp-m7/
Click to expand...
Click to collapse
yes, I tried that - no luck :/
thanks though

it has to do something with not wiping the cache after flashing the recovery ... I think
after every failed twrp2.7xx or latest cwm flash , I need to flash the 2.6.3.3 version that works flawlessly.
what i notice right away, is that whatever i try to do in there, i m getting E:Unable to mount '/cache'
wipe--advanced--select cache--wipe works though and after that everything is ok in 2.6.3.3
i tried fastboot erase cache, did`t make any difference
i´m pretty much out of ideas...

You will always get unable to mount cache in recovery after you do a fastboot erase cache. Have you been using that command after you flash the recovery? I just noticed you've been doing that before you flash it. You should flash the recovery. Then erase cache

nateboi81 said:
You will always get unable to mount cache in recovery after you do a fastboot erase cache. Have you been using that command after you flash the recovery? I just noticed you've been doing that before you flash it. You should flash the recovery. Then erase cache
Click to expand...
Click to collapse
thanks a lot for the info.
I will give it another go. I tried via flashify as well - same outcome
Sent from my HTC One using Tapatalk

still no success. I even ruu-ed it til the ver. 1.19.xx.xx and gradually used the official ota to update to 6.09.401.5. same issue, it says that flashed successfully, but doesn't enter recovery ; staying stucj at the htc splash page with ^entering recovery ^ text. I'm out of ideas, using sense roms anyway. it's just that it drives me kookoo not knowing why this is happening ??
Sent from my HTC One using Tapatalk

deleted

deleted
Sent from my HTC One using Tapatalk

Have you tried 2.8.0.1?
---------- Post added at 01:49 PM ---------- Previous post was at 01:47 PM ----------
Also: You may have to take everything back to factory. Turn s on if off. Relock bootloader. Run RUU. Enter factory recovery and perform factory reset. Unlock bootloader, Flash TWRP, and root.

ruu

for the life of me, i cannot find the ruu for this htc one m7 ul..
here is my getvar all
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH365W903916
(bootloader) imei: 357864055134611
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-7661b1d7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.099s

Tmobilefan906 said:
for the life of me, i cannot find the ruu for this htc one m7 ul..
here is my getvar all
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH365W903916
(bootloader) imei: 357864055134611
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-7661b1d7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.099s
Click to expand...
Click to collapse
7.18.161.21 RUU posted in the RUU collection thread (sticky thread in the general section). If your phone was running an higher version of that before (e.g 7.18.161.30 or 7.18.161.51), which is impossible to know since your version-main is blank, you'll first need to edit your /misc partition to write the correct version number before flashing (explained at the end of post #2 of that same sticky thread). Make sure to flash a stock 7.18.161.x before relocking the bootloader in case you need to do the /misc trick.
NVM, I found a 7.18.161.51 that should work fine
https://www.androidfilehost.com/?fid=529152257862665225

alray said:
7.18.161.21 RUU posted in the RUU collection thread (sticky thread in the general section). If your phone was running an higher version of that before (e.g 7.18.161.30 or 7.18.161.51), which is impossible to know since your version-main is blank, you'll first need to edit your /misc partition to write the correct version number before flashing (explained at the end of post #2 of that same sticky thread). Make sure to flash a stock 7.18.161.x before relocking the bootloader in case you need to do the /misc trick.
NVM, I found a 7.18.161.51 that should work fine
https://www.androidfilehost.com/?fid=529152257862665225
Click to expand...
Click to collapse
I did the nobc BL to get it unjammed from the active cmdline overflow. Should I do the p9 first? I can't flash any ROM zips with the nobc BL.

alray said:
7.18.161.21 RUU posted in the RUU collection thread (sticky thread in the general section). If your phone was running an higher version of that before (e.g 7.18.161.30 or 7.18.161.51), which is impossible to know since your version-main is blank, you'll first need to edit your /misc partition to write the correct version number before flashing (explained at the end of post #2 of that same sticky thread). Make sure to flash a stock 7.18.161.x before relocking the bootloader in case you need to do the /misc trick.
NVM, I found a 7.18.161.51 that should work fine
https://www.androidfilehost.com/?fid=529152257862665225
Click to expand...
Click to collapse
Yea. I seen that image..but don't I need s off to flash ruu zips?

alray said:
7.18.161.21 RUU posted in the RUU collection thread (sticky thread in the general section). If your phone was running an higher version of that before (e.g 7.18.161.30 or 7.18.161.51), which is impossible to know since your version-main is blank, you'll first need to edit your /misc partition to write the correct version number before flashing (explained at the end of post #2 of that same sticky thread). Make sure to flash a stock 7.18.161.x before relocking the bootloader in case you need to do the /misc trick.
NVM, I found a 7.18.161.51 that should work fine
https://www.androidfilehost.com/?fid=529152257862665225
Click to expand...
Click to collapse
I tried getting adb to see phone while in recovery, but PC doesn't see it. Could it be cuz of the nobc BL recovery?

Tmobilefan906 said:
I did the nobc BL to get it unjammed from the active cmdline overflow. Should I do the p9 first? I can't flash any ROM zips with the nobc BL.
Click to expand...
Click to collapse
You mean p19 (not p9)? You've flashed the no BCB version of twrp and not fixed your p19 partition yet?
---------- Post added at 10:08 AM ---------- Previous post was at 09:41 AM ----------
Your p19 must be fixed, flashing a rom or flashing a RUU will not solve your cmd line overflow problem, the p19 partition is not included in any RUU or ROM. When your phone is booting, the kernel checks at the BCB from p19, if there is invalid data there, like in your case, the phone will not boot and throw that "active cmd line overflow" error code. That's why you're flashing a custom recovery made to ignore the data from p19's BCB (the "no-bcb twrp/cwm recovery), so your phone can boot something and gives you access to your memory and fix the BCB corruption by flashing that generic p19 provided by nkk71 in his thread. Only when p19 will be fixed you'll be able to boot something else than a "no-bcb" recovery.
---------- Post added at 10:16 AM ---------- Previous post was at 10:08 AM ----------
Tmobilefan906 said:
Yea. I seen that image..but don't I need s off to flash ruu zips?
Click to expand...
Click to collapse
No, you only need s-off if downgrading or if flashing a RUU version not made for your CID/MID.
Tmobilefan906 said:
I tried getting adb to see phone while in recovery, but PC doesn't see it. Could it be cuz of the nobc BL recovery?
Click to expand...
Click to collapse
No, the "no-bcb" recovery is made exactly for ppl to be able to use adb to fix the p19 partition. Since you were able to flash the recovery, it's most likely a driver problem since any other problem, lets say defective usb port/cable, would also have prevented fastboot commands to work correctly... Re-install the latest driver version from HTC and make sure nothing else can interfere with the process (e.g another connected device, other drivers, htc sync). Make sure you are using the latest adb version.

alray said:
You mean p19 (not p9)? You've flashed the no BCB version of twrp and not fixed your p19 partition yet?
---------- Post added at 10:08 AM ---------- Previous post was at 09:41 AM ----------
Your p19 must be fixed, flashing a rom or flashing a RUU will not solve your cmd line overflow problem, the p19 partition is not included in any RUU or ROM. When your phone is booting, the kernel checks at the BCB from p19, if there is invalid data there, like in your case, the phone will not boot and throw that "active cmd line overflow" error code. That's why you're flashing a custom recovery made to ignore the data from p19's BCB (the "no-bcb twrp/cwm recovery), so your phone can boot something and gives you access to your memory and fix the BCB corruption by flashing that generic p19 provided by nkk71 in his thread. Only when p19 will be fixed you'll be able to boot something else than a "no-bcb" recovery.
---------- Post added at 10:16 AM ---------- Previous post was at 10:08 AM ----------
No, you only need s-off if downgrading or if flashing a RUU version not made for your CID/MID.
No, the "no-bcb" recovery is made exactly for ppl to be able to use adb to fix the p19 partition. Since you were able to flash the recovery, it's most likely a driver problem since any other problem, lets say defective usb port/cable, would also have prevented fastboot commands to work correctly... Re-install the latest driver version from HTC and make sure nothing else can interfere with the process (e.g another connected device, other drivers, htc sync). Make sure you are using the latest adb version.
Click to expand...
Click to collapse
Omg. Tyvm. I will do on my lunch. Should I pm you or post here in the thread? Thanks.

I was able to get the nobc working by issuing fastboot OEM enableqxdm 0

alray said:
You mean p19 (not p9)? You've flashed the no BCB version of twrp and not fixed your p19 partition yet?
---------- Post added at 10:08 AM ---------- Previous post was at 09:41 AM ----------
Your p19 must be fixed, flashing a rom or flashing a RUU will not solve your cmd line overflow problem, the p19 partition is not included in any RUU or ROM. When your phone is booting, the kernel checks at the BCB from p19, if there is invalid data there, like in your case, the phone will not boot and throw that "active cmd line overflow" error code. That's why you're flashing a custom recovery made to ignore the data from p19's BCB (the "no-bcb twrp/cwm recovery), so your phone can boot something and gives you access to your memory and fix the BCB corruption by flashing that generic p19 provided by nkk71 in his thread. Only when p19 will be fixed you'll be able to boot something else than a "no-bcb" recovery.
---------- Post added at 10:16 AM ---------- Previous post was at 10:08 AM ----------
No, you only need s-off if downgrading or if flashing a RUU version not made for your CID/MID.
No, the "no-bcb" recovery is made exactly for ppl to be able to use adb to fix the p19 partition. Since you were able to flash the recovery, it's most likely a driver problem since any other problem, lets say defective usb port/cable, would also have prevented fastboot commands to work correctly... Re-install the latest driver version from HTC and make sure nothing else can interfere with the process (e.g another connected device, other drivers, htc sync). Make sure you are using the latest adb version.
Click to expand...
Click to collapse
Do u have a link by chance of latest htc drivers?I would surely appreciate it. Thanks.

alray said:
You mean p19 (not p9)? You've flashed the no BCB version of twrp and not fixed your p19 partition yet?
---------- Post added at 10:08 AM ---------- Previous post was at 09:41 AM ----------
Your p19 must be fixed, flashing a rom or flashing a RUU will not solve your cmd line overflow problem, the p19 partition is not included in any RUU or ROM. When your phone is booting, the kernel checks at the BCB from p19, if there is invalid data there, like in your case, the phone will not boot and throw that "active cmd line overflow" error code. That's why you're flashing a custom recovery made to ignore the data from p19's BCB (the "no-bcb twrp/cwm recovery), so your phone can boot something and gives you access to your memory and fix the BCB corruption by flashing that generic p19 provided by nkk71 in his thread. Only when p19 will be fixed you'll be able to boot something else than a "no-bcb" recovery.
---------- Post added at 10:16 AM ---------- Previous post was at 10:08 AM ----------
No, you only need s-off if downgrading or if flashing a RUU version not made for your CID/MID.
No, the "no-bcb" recovery is made exactly for ppl to be able to use adb to fix the p19 partition. Since you were able to flash the recovery, it's most likely a driver problem since any other problem, lets say defective usb port/cable, would also have prevented fastboot commands to work correctly... Re-install the latest driver version from HTC and make sure nothing else can interfere with the process (e.g another connected device, other drivers, htc sync). Make sure you are using the latest adb version.
Click to expand...
Click to collapse
I've tried it and I still can't issue adb while in recovery. Any suggestions? Thanks.

Tmobilefan906 said:
I've tried it and I still can't issue adb while in recovery. Any suggestions? Thanks.
Click to expand...
Click to collapse
Is usb otg working? If yes put the generic p19 on a usb drive and use twrp's terminal instead of adb to write the generic p19 to your p19 partition.

alray said:
Is usb otg working? If yes put the generic p19 on a usb drive and use twrp's terminal instead of adb to write the generic p19 to your p19 partition.
Click to expand...
Click to collapse
How I tell if otg is working?

alray said:
Is usb otg working? If yes put the generic p19 on a usb drive and use twrp's terminal instead of adb to write the generic p19 to your p19 partition.
Click to expand...
Click to collapse
I don't have a USB drive...since this device doesn't have ext SD. Nvm. I see

I forgot to mention that I can boot into an operational ROM. Does that help? Could I upload the file to my phone on es file explorer?

I keep getting this darn screen

Tmobilefan906 said:
I keep getting this darn screen
Click to expand...
Click to collapse
solved. had to update drivers and had to chose samsung adb interface. now im up and running. what rom do you recommend? i flashed RR, but it seems to be in a bootloop

Tmobilefan906 said:
solved. had to update drivers and had to chose samsung adb interface. now im up and running. what rom do you recommend? i flashed RR, but it seems to be in a bootloop
Click to expand...
Click to collapse
Im running RR and its working fine. Is your p19 fixed now? If yes you should flash the ruu so everything is set back to stock and after flash the custom rom you want.

alray said:
Im running RR and its working fine. Is your p19 fixed now? If yes you should flash the ruu so everything is set back to stock and after flash the custom rom you want.
Click to expand...
Click to collapse
Yes. I fixed it
Sent from my SM-N900T using XDA Labs

Tmobilefan906 said:
Yes. I fixed it
Click to expand...
Click to collapse
Idk what one to flash. Its a Vodafone from the u.k
Sent from my SM-N900T using XDA Labs

alray said:
Im running RR and its working fine. Is your p19 fixed now? If yes you should flash the ruu so everything is set back to stock and after flash the custom rom you want.
Click to expand...
Click to collapse
How long was boot up after flash? Mine was over 10 mins, without a successful boot up.
Sent from my SM-N900T using XDA Labs