Active cmdline overflow! - One (M7) Q&A, Help & Troubleshooting

Hi, my dad just got a HTC One and tried to install a ROM but failed terribly by wiping everything that he possibly could, don't ask me how, and then he had me fix it because he couldn't. I sideloaded Android Revolution HD but got error 7 (old recovery) so I updated the recovery and that's where the problems started, I got the error 'Active cmdline overflow!' which I couldn't find a solution to, I installed an older recovery and it worked fine so it turns out that I can't install any recoveries capable of KitKat ROMs without getting that problem that prevents me from booting or getting to recovery. I restored using an RUU which didn't fix much; I can't update the stock ROM without getting a boot loop and if I try to change the kernel so I can S-OFF I get 'Active cmdline overflow!' again!! Now I'm stuck in bootloader because I can't flash any kernels Can anyone help me please?
Getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3B2W900221
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-09ff2ded
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks in advance Sorry if I got anything wrong this is my first post in a very, very long time

Please provide specific versions of recovery that works and the version that results in active cmdline overflow.

cschmitt said:
Please provide specific versions of recovery that works and the version that results in active cmdline overflow.
Click to expand...
Click to collapse
CWM - 6.0.4.5+ causes the error I think
TWRP - 2.6.3.3+ causes the error
All others seem to be fine

Jak3Mac said:
CWM - 6.0.4.5+ causes the error I thing
TWRP - 2.6.3.3+ causes the error
All others seem to be fine
Click to expand...
Click to collapse
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2708134

cschmitt said:
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2708134
Click to expand...
Click to collapse
No, it's the LTE version of the phone so that recovery won't work

Jak3Mac said:
No, it's the LTE version of the phone so that recovery won't work
Click to expand...
Click to collapse
??? It's for m7_ul, which is your phone.

cschmitt said:
??? It's for m7_ul, which is your phone.
Click to expand...
Click to collapse
I'm sorry, I don't know what's wrong with me :laugh: I'll give it a try when I get up, it's 3:30 am so I'm ready to sleep but I'll need to find and flash the stock kernel first because the current kernel is causing the issue at the moment and this prevents me from getting to recovery

cschmitt said:
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2708134
Click to expand...
Click to collapse
I tried this, it doesn't work. Same issue: "Active cmdline overflow! (1025 Bytes)"

Jak3Mac said:
I tried this, it doesn't work. Same issue: "Active cmdline overflow! (1025 Bytes)"
Click to expand...
Click to collapse
Thanks for giving it a try. So as soon as you return to a pre-2.6.3.3 TWRP the error no longer appears in hboot screen?
We seen this error in various cases and trying to nail down the exact cause.
FYI, Some have had luck with downgrading to a pre-1.54.000 hboot.

cschmitt said:
Thanks for giving it a try. So as soon as you return to a pre-2.6.3.3 TWRP the error no longer appears in hboot screen?
We seen this error in various cases and trying to nail down the exact cause.
FYI, Some have had luck with downgrading to a pre-1.54.000 hboot.
Click to expand...
Click to collapse
Yes that's right, it's very odd. I'm going to try and flash the Viper ROM using 4.2.2 and see if I can S-OFF, then I'll write super CID and downgrade hboot.
***Update***
I flashed the venom ROM but when using Rum Runner I'm getting a lot of pours so I don't think it's going to work

Jak3Mac said:
Yes that's right, it's very odd. I'm going to try and flash the Viper ROM using 4.2.2 and see if I can S-OFF, then I'll write super CID and downgrade hboot.
Click to expand...
Click to collapse
Here's hboot 1.54.0000 Aug 19, 2013 from GPE 3.07.1700.1. There are several 1.54.0000 hboots with different production dates, but the Aug 19 version is the last one to not include the 'Active cmdline overflow' code, so it should work for you once you are s-off.
firmware_3.07.1700.1.zip

cschmitt said:
Here's hboot 1.54.0000 Aug 19, 2013 from GPE 3.07.1700.1. There are several 1.54.0000 hboots with different production dates, but the Aug 19 version is the last one to not include the 'Active cmdline overflow' code, so it should work for you once you are s-off.
firmware_3.07.1700.1.zip
Click to expand...
Click to collapse
Thanks for all your help, could you help me out with S-OFF? I'm getting infinite pours but there's not much I can do about it, I can't flash kernels or flash the current rom. Would stock recovery help?

Jak3Mac said:
Thanks for all your help, could you help me out with S-OFF? I'm getting infinite pours but there's not much I can do about it, I can't flash kernels or flash the current rom. Would stock recovery help?
Click to expand...
Click to collapse
You're trying to get a specific rom and kernel installed to s-off?
Assuming bootloader is unlocked, just pull the boot.img out of the kernel zip you want and 'fastboot flash boot boot.img'
For the rom, maybe find a nandroid backup of the \system partition for the rom you want and just restore it using the older twrp or cwm recovery. Might work.
Ask in the rom thread your trying to install, maybe someone will post a backup for you. Or search for the 'guru reset' thread, I think there are some nandroid backups there.

cschmitt said:
You're trying to get a specific rom and kernel installed to s-off?
Assuming bootloader is unlocked, just pull the boot.img out of the kernel zip you want and 'fastboot flash boot boot.img'
For the rom, maybe find a nandroid backup of the \system partition for the rom you want and just restore it using the older twrp or cwm recovery. Might work.
Ask in the rom thread your trying to install, maybe someone will post a backup for you. Or search for the 'guru reset' thread, I think there are some nandroid backups there.
Click to expand...
Click to collapse
Flashing any kernel triggers the active cmdline error
On the guru reset thread I found one from a phone with the CID vodap002 but mine's vodap001, it will still work though won't it? I'm downloading now, will update the post when I've restored it
***Edit***
I think the partitions are messed up :\ I can't mount cache in recovery which is one of the symptoms of this. Would re-flashing the firmware solve this issue? If I could find it, that is
***Edit 2***
CWM isn't picking up the nandroid I might have to give up on this one, I don't know what to do. I'll put a JB ROM on for now, that'll have to do

Related

[Q] Custom Rom/Recovery w/o tampered message?

Hello.
I just got my One, upgraded from the One X
I am very skilled regarding rooting, flashing custom roms, recoveries, etc. I just have a quick question.
Is it possible to install custom rom, custom recovery and turn the phone S-OFF - WITHOUT getting the tampered message?
- If no, tell me that
- If yes, read on
Second case: Does this RRU match my M7?
First of all, what have i done myself:
- Unlocked bootloader
- Installed TWRP
- Made a nandroid backup
- Relocked bootloader because i want to flash [ROM] Android Revolution HD 3.2 Google Edition | High Quality & Performance | Android 4.3 Jelly Bean | 2.14.1700.15
- Flashed latest firmware for my phone - 2.24.401.1 (the thread above states that its not needed but recommended)
- Got the TAMPERED message and wants to get rid of that (and return from HBOOT 1.54 to original HBOOT 1.44)
In order to get rid of that message, this guide state i must use "method 2", and as part of that method 2, i must find the correct RRU.
The following is the output of getvar all before firmware update:
(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.16
(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__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3980mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.043s
Click to expand...
Click to collapse
And this is getvar all after firmware update:
(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: REMOVED
(bootloader) imei: REMOVED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4010mV
(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
all: Done!
finished. total time: 0.043s
Click to expand...
Click to collapse
Will this RRU be for my phone: RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
- I found it here: http://www.androidruu.com/index.php?developer=M7
I chose it as its the RRU for the M7 Europe model that gets closest to my original main version (1.29.401.16 vs 1.28.401.7), also the radio in that RRU is just a tad older than my own original radio.
Also, is it possible to downgrade like that (im quite certain it is, just want to be sure).
Kind Regards
TwinAdk
Wait, you was in 1.44 hboot and now you're on 1.54?
If yes, you can't get the s-off.
The tools for the S-OFF are working only in 1.44 hboot, and, i if read right, now you have the 1.54 and you can do nothing...
****, you are kidding me, right? And RUU downgrade is not an option? That will downgrade my RUU too.
Aside from S-OFF being down the toilet, are there any other downsides to Hboot 1.54?
TwinAdk said:
****, you are kidding me, right? And RUU downgrade is not an option? That will downgrade my RUU too.
Aside from S-OFF being down the toilet, are there any other downsides to Hboot 1.54?
Click to expand...
Click to collapse
You can't downgrade with any ruu if you don't have the S-OFF...
Nope, but now you can't remove the ****Tampered**** line and you can't get the S-OFF...
Guich said:
You can't downgrade with any ruu if you don't have the S-OFF...
Nope, but now you can't remove the ****Tampered**** line and you can't get the S-OFF...
Click to expand...
Click to collapse
God dammit.. Well, are there any downsides regarding custom roms, to having the 1.54 hboot? Also, is it likely S-OFF will ever be avail. with 1.54?
TwinAdk said:
God dammit.. Well, are there any downsides regarding custom roms, to having the 1.54 hboot? Also, is it likely S-OFF will ever be avail. with 1.54?
Click to expand...
Click to collapse
No, you can flash all rom, kernel, mod, theme that you want.
For the S-OFF, no, devs said that they will work on the tool for the S-OFF when the new update form htc will come with the 1.55 hboot
Guich said:
No, you can flash all rom, kernel, mod, theme that you want.
For the S-OFF, no, devs said that they will work on the tool for the S-OFF when the new update form htc will come with the 1.55 hboot
Click to expand...
Click to collapse
So when 1.55 hboot arrives, work will start for S-OFF for that HBOOT? Any ETA on 1.55?
TwinAdk said:
So when 1.55 hboot arrives, work will start for S-OFF for that HBOOT? Any ETA on 1.55?
Click to expand...
Click to collapse
Atm there are some leaks of android 4.3 and new hboot 1.55, but this isn't the update that we will get.
For the question, yes
Guich said:
Atm there are some leaks of android 4.3 and new hboot 1.55, but this isn't the update that we will get.
For the question, yes
Click to expand...
Click to collapse
Okay, thanks
Now that i booted the phone, my storage is not available and wifi does not turn on (it says enabling, but thats all) - great start! Any idea why?
Ill look into it tomorrow my self, im off to bed now... Guess the One X will be in service for a few more days...
EDIT: Im on a firmware thats NOT for the android version i have, i think thats the problem. I guess ill have to sideload the custom rom running 4.3, and get it running that way.
Freaking hell, no S-OFF!
You relocked your bootloader after the flash of the rom?
If yes, you have to unlock this, reflash the rom and the kernel, and do a wipe of cache and dalvik-cache...
Guich said:
You relocked your bootloader after the flash of the rom?
If yes, you have to unlock this, reflash the rom and the kernel, and do a wipe of cache and dalvik-cache...
Click to expand...
Click to collapse
I cannot flash the rom as my SD is unavail... Is it an option to sideload the ROM?
TwinAdk said:
I cannot flash the rom as my SD is unavail... Is it an option to sideload the ROM?
Click to expand...
Click to collapse
Flash the stock recovery and then do a factory reset in bootloader, this will fix your sd.
After flash a custom recovery and try to use the sideload
Guich said:
Flash the stock recovery and then do a factory reset in bootloader, this will fix your sd.
After flash a custom recovery and try to use the sideload
Click to expand...
Click to collapse
Hello.
I flashed the stock recovery, and factory reset the phone. It rebooted during factory reset (of course), and booted normally afterwards. Wifi and storage did however still not work.. From within android im told that the storage is "Unavailable" (ill post screenshots later) - and from TWRP, i am told that i have "Internal storage" of 28xxx mb available (not sure about the excact size, around 28 gb) - but i cannot mount it and make it available from windows.
I can see the phone in windows, as a HTC media unit, and browse the content (storage -> legacy -> more folders -> root of SD card with folders like "downloaded" etc - default folders). But when i get there i cannot create folders or files, i can only view the content.....?
1. I cannot downgrade with RRU, since im S-ON
2. My Wifi and storage SEEMS broke (i suspect its because i flashed the firmware mentioned earlier, and my android version is not happy with that firmware - someone with more insight are welcome to comment on my guessing here)
3. Sideloading the rom i want to use (based on android 4.3) seems to be the only option - but can i sideload when my SD is not available in recovery?
Starting to worry a bit here
And thank you for all your help so far :good: I didnt get to say that last evening.. Appriciate!
Kind Regards
Hello sir,
first of all, let me say you screwed up already when not researching XDA before doing an update. Since i have done so myself numerous times, let me advise you to make it a habit, when buying a new phone to specifically research downsides of updates before accepting any.
Particularly in the HTC world, it has become a common thing to only gain S-OFF while the phone is in early software states and loose this ability towards later releases. Until now, many HTC phones i have had to deal with, had issues with disabling security on later firmwares.
Then, the storage problem you describe could possibly be related to something i have seen a fair few times. What Guich told you to do is usually the ultimate trick to get it back working. But let me ask this first: were you able to access storage from windows normally before the update? Or could you also face a driver issue?
OK. Guich's comment did not help. You flashed the stock recovery from the firmware you run. Then you ran Factory Reset from within Bootloader? Or from within android? If the latter, try the first...
I will be putting up stock recoveries from different RUU's soon on my thread here: http://forum.xda-developers.com/showthread.php?t=2316726 but you also find them on the forum already by searching. Try different stock recoveries and factory reset from Bootloader.
Then, if that doesn't help, try to run the OTA 2.24 (which already runs on your phone!) again by booting into bootloader, then picking "Fastboot" there (use volume down and up to navigate and power to confirm) and then going to your adb/fastboot with a command window. Oh, connect phone to PC of course
Lets say you have adb and fastboot plus the dll files in C:\Android. Open a CMD window and do "CD C:\Android" to go there.
there, run "fastboot oem rebootRUU" (type exactly as i do here, omit the quotes though).
then, copy and paste the OTA file (obtain HERE) to the same folder (C:\Android).
For easier typing in CMD, rename the OTA to something short and simple like test.zip or whatever.
then go back to your CMD Window and type in "fastboot flash zip test.zip"
Since its the same hboot and firmware in the OTA like you have on phone and since this package is official and signed, your phone ---should--- accept the flash. If not (maybe because you got the wrong model ID or wrong CID) i wouldn't really know how to proceed. But you DID accept that OTA before so it MUST be for your phone or else it wouldn't have flashed in the first place.
If it flashes fine, boot your phone up and check if it fixed everything.
If not, run the check for software update in Settings/Info/ and see if there is already an official OTA for your phone available that brings you past the 2.24. If not, download one of the inofficial OTA's and --- hope --- that you can flash it. Like 3.18 or 3.22. The first is for Asia/Taiwan though and will almost certainly NOT flash on your phone and the second is BrightstarUS and for the DEV edition and will also almost certainly not flash. But its worth a try.
beyond that, i have no more valuable tips. Only thing I would try is to flash CWM and do a clear storage, wipe data, wipe everything there. But be sure to have your nandroid ready if you do that. CWM uses a slightly different formatting method so it could possibly correct issues. In the past, i have read about screwed up SDcards related to CWM formatting more often than those that got screwed up by TWRP though. So its not exactly ideal to play with CWM on a phone that has already issues with its partition. But if i was desperate, i would do it anyway.
If that doesnt help or make it worse, do the very same thing on TWRP, pick the "wipe Data" option which prompts you to type "yes" into an input line. This will once again format your SD with a different method. It could possible correct this problem.
DO NOT attempt to screw around with the SD Partition using tools like MiniTool or EASUS if you can access the sd from them at all!
The SD Card is an EXT4 file system and cannot be formatted with FAT or NTFS from windows. If you do that, the phone wont work at all anymore. The exact parameters to format the partition externally are not known to me and i doubt you can address the partition from within windows at all. Maybe it works under linux...
Sorry. Cant be much help here. If that all doesnt work, just flash stock recovery back and restore your stock nandroid and send it in for repair. Them service dudes will have the right RUU and fix it for you.
[EDIT]
Oh and before i forget: if you can fix it with these tips, you owe me one
You have to flash Team Venom's ViperOne then instead of ARHD! :laugh:
Aroma installer is running now!! So excited to see the result! I sideloaded the zip, via adb sideload Nice short article on it here: http://teamw.in/ADBSideload
Will return with outcome :highfive::fingers-crossed::fingers-crossed::fingers-crossed:
EDIT: Its back! Running custom rom with sd card avail and wifi working! Pew, saved by adb sideload, increddible!

[Q] No OS, no nothing

Oke guys,
I probally did one of the most stupid things. Got my One transformed tot a GPE 4.3 version works smooth. Yesterday an OTA update to 4.4 really messed up my day. Try to install everything gone....No i am not able to install any version at al.
Got the last version of TWRP installed. got myself an unlocked bootloader even an 4.3 GPE rom. But TWRP keeps giving me the message "Error flashing zip: 'sdcard/<M7_UL_JB443_STOCK_UI.
can someone help me solve this problem..
For 4.3 Roms you need twrp 2.6.3.0 and not 2.6.3.3.
Flash it and let us know
Sent from my HTC One using Tapatalk
Ivanovic said:
For 4.3 Roms you need twrp 2.6.3.0 and not 2.6.3.3.
Flash it and let us know
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thans for you answer. I now got another one. "Unable to mount /data
unable to mount internal storage
I'm also not able to mount then by the menu.
Why do you need to mount internal storage?
Sent from my HTC One using Tapatalk
After installing the right twrp version. i use ADB to push the image.zip to my phone. Then i use twrp install and browse to my sdcard where the image.zip is transferred to. when i click it it gives that error. By the way he also starts with error flashing zip.
Comlete error is:
Error flashing zip '/sdcard/M7_UL_JB43..
updating partition details
e:unable to mount /data
e: unable to mount internal storage
i fear for my device...
Please anyone who can help me?
what about to boot to Bootloader, connect to some tools like Hasoon2000 Toolkits (cannot post links yet, sorry) and format everything you got, than flash the recovery again and push the rom via adb
make sure you download rom without any downloader
do not worry, i bricked my one the same day i got it and took me two nights to make it work again it needs lot of trying and searching but eventually you fix it
Thanks for your reply, i flashed everything a couple times. I guess is have the right rom. i do worry cause i tried so many things. Thinking about sending in my phone to HTC today..
lenneej said:
Thanks for your reply, i flashed everything a couple times. I guess is have the right rom. i do worry cause i tried so many things. Thinking about sending in my phone to HTC today..
Click to expand...
Click to collapse
what exactly are you trying to flash, link please.
i tried so many things is don't know exaclty the links. I tried different custom recovery. CWM and TWRP. Since i don't have an OS any more i tried to install de M7xxx.zip
Is the error still unable to mount sdcard? If so, follow post # 3 in my Canadian stock link.. You may need to use a recovery closer to your HBOOT version.
lenneej said:
i tried so many things is don't know exaclty the links. I tried different custom recovery. CWM and TWRP. Since i don't have an OS any more i tried to install de M7xxx.zip
Click to expand...
Click to collapse
would you mind sharing what this "M7xxx.zip" is.
I am having the same issue
I am having the exact same issue as OP. I have HBOOT version 1.54 and TWRP 2.6.3.3., my bootloader is unlocked, and I am S-On. Every time i try to flash an image it gives me the unable to mount error. I am trying to use the Stock 4.4 GPE nandroid rom as suggested by @ipfreelytech. Any suggestions? Thanks
nkk71 said:
would you mind sharing what this "M7xxx.zip" is.
Click to expand...
Click to collapse
I think he was trying to flash a RUU.zip or an OTA.Zip through TWRP. which of coarse ain't gona work
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
Silverlateralus said:
I am having the exact same issue as OP. I have HBOOT version 1.54 and TWRP 2.6.3.3., my bootloader is unlocked, and I am S-On. Every time i try to flash an image it gives me the unable to mount error. I am trying to use the Stock 4.4 GPE nandroid rom as suggested by @ipfreelytech. Any suggestions? Thanks
Click to expand...
Click to collapse
it sounds like your also trying to flash a RUU through recovery
go back where you downloaded the file and read the instructions on how to install it
Silverlateralus said:
I am having the exact same issue as OP. I have HBOOT version 1.54 and TWRP 2.6.3.3., my bootloader is unlocked, and I am S-On. Every time i try to flash an image it gives me the unable to mount error. I am trying to use the Stock 4.4 GPE nandroid rom as suggested by @ipfreelytech. Any suggestions? Thanks
Click to expand...
Click to collapse
Does it work on any other TWRP version? Can your phone boot normally?
SaHiLzZ said:
Does it work on any other TWRP version? Can your phone boot normally?
Click to expand...
Click to collapse
I tried TWRP 2.6.3.0 with the same result. I dont know what you mean by "boot normally", but when I turn it on and don't force it to bootloader it just loads a dead android with a ! symbol.
Silverlateralus said:
I tried TWRP 2.6.3.0 with the same result. I dont know what you mean by "boot normally", but when I turn it on and don't force it to bootloader it just loads a dead android with a ! symbol.
Click to expand...
Click to collapse
From fastboot usb and a command prompt run fastboot getvar all
From here you can figure out what RUU you need to get your phone working again
Sent from my HTC One using Tapatalk
I also tried CM 10.2 with TWRP v2.6.3.0 and 2.6.3.3. These are the errors i keep getting no matter what i try:
wwwTAKETHISOUT.imgur.com/FAbiDqd
---------- Post added at 01:04 AM ---------- Previous post was at 12:56 AM ----------
clsA said:
From fastboot usb and a command prompt run fastboot getvar all
From here you can figure out what RUU you need to get your phone working again
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.07.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4286mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
This is the information I got. Not sure what to do with it though.
Silverlateralus said:
I also tried CM 10.2 with TWRP v2.6.3.0 and 2.6.3.3. These are the errors i keep getting no matter what i try:
(bootloader) version-bootloader: 1.54.0000 - your Hboot
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-main: 3.07.1700.1 - your firmware version
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001 - Google Play Edition CID
This is the information I got. Not sure what to do with it though.
Click to expand...
Click to collapse
Using the above info I see you have a google play phone or converted yours into one
To reset your phone your going to need s-off try here http://rumrunner.us/
what is the file your trying to flash in the photo (link to it please)
clsA said:
Using the above info I see you have a google play phone or converted yours into one
To reset your phone your going to need s-off try here
what is the file your trying to flash in the photo (link to it please)
Click to expand...
Click to collapse
I can't use rumrunner, because I don't have usb debugging enabled (which it says it requires).
The two roms i tried installing with TWRP are:
4.4 Nandroid - mega.co.nREMOVETHISz/#!TMlgWLDJ!ZfFlcx...4grwOLi-Ied3Tg
10.2 Cyanogen Mod - download.cyanogenmod.oREMOVETHISrg/get/jenkins/49872/cm-10.2.0-m7ul.zip

Stock Rom 4.2.2 update to 4.3 = brick

I put stock back on my phone "Guru_Reset_M7_2.24.771.3.zip" which I have done before without any problem.
Stock rom flashed fine, boots up fine and start reinstalling apps etc, OTA firmware starts downloading sense 5.5 etc
Install OTA update and then restart then phone just shows white background with htc logo then bootloops.
Tried going into recovery, restarting, power down, factory reset etc, doesn't work so I do fastboot oem relock to see if it helps.
So basically it's boot looping and now I have no idea how to fix it
EDIT: - I Wiped, reinstalled stock rom and tried again, SAME PROBLEM.
Anarchy89 said:
Hey guys I'll try and keep it short and sweet.
So here's what happened.
I installed android revolution HD 71.1 no problems, notice mobile signal is weak 1-2 bars I normally have 4-5 so I searched and someone said maybe firmware is not up to date.
So I wipe the rom and put stock back on there "Guru_Reset_M7_2.24.771.3.zip" which I have done before without any problem.
Stock rom flashed fine, boots up fine and start reinstalling apps etc, OTA firmware starts downloading sense 5.5 etc
Install OTA update and then restart then phone just shows white background with htc logo then bootloops.
Tried going into recovery, restarting, power down, factory reset etc, doesn't work so I do fastboot oem relock to see if it helps.
So basically it's boot looping and now I have no idea how to fix it, please help, it will be so appreciated
Click to expand...
Click to collapse
If you can flash and access custom recovery, adb push or adb sideload a custom rom..
thanks, I'm making progress, I unlocked the bootloader again and am reflashing the stock firmware...
I flashed stock firmware and stock recovery and downloaded and installed the OTA update and it's doing the same thing!! why?
Just bootlooping
Anarchy89 said:
I flashed stock firmware and stock recovery and downloaded and installed the OTA update and it's doing the same thing!! why?
Just bootlooping
Click to expand...
Click to collapse
Links to stock firmware and stock recovery?
Maybe something is wrong with the phone??
Your best start will be to flash a custom recovery and then flash a custom rom. What is the output of your fastboot getvar all ? (remove IMEI)
SaHiLzZ said:
Links to stock firmware and stock recovery?
Maybe something is wrong with the phone??
Your best start will be to flash a custom recovery and then flash a custom rom. What is the output of your fastboot getvar all ? (remove IMEI)
Click to expand...
Click to collapse
He is using this correct ?: http://www.htc1guru.com/dld/guru_reset_m7_2-24-771-3-zip/
He is having exactly the same problem as someone I was trying to help out who is having exactly the same issue and may join in this thread.
The guru reset puts them on 4.2.2 which works fine then they get a small OTA which installs fine, then a big update to 4.3 which installs, but upon restart for some reason gives a boot loop, doesn't get past the HTC quietly brilliant logo, im at a loss.
Seanie280672 said:
He is using this correct ?: http://www.htc1guru.com/dld/guru_reset_m7_2-24-771-3-zip/
He is having exactly the same problem as someone I was trying to help out who is having exactly the same issue and may join in this thread.
The guru reset puts them on 4.2.2 which works fine then they get a small OTA which installs fine, then a big update to 4.3 which installs, but upon restart for some reason gives a boot loop, doesn't get past the HTC quietly brilliant logo, im at a loss.
Click to expand...
Click to collapse
yes that's the exact one I am using
Seanie280672 said:
He is using this correct ?: http://www.htc1guru.com/dld/guru_reset_m7_2-24-771-3-zip/
He is having exactly the same problem as someone I was trying to help out who is having exactly the same issue and may join in this thread.
The guru reset puts them on 4.2.2 which works fine then they get a small OTA which installs fine, then a big update to 4.3 which installs, but upon restart for some reason gives a boot loop, doesn't get past the HTC quietly brilliant logo, im at a loss.
Click to expand...
Click to collapse
Oh ok.. Interesting.
S-OFF, and move to .401 base perhaps?
SaHiLzZ said:
Oh ok.. Interesting.
S-OFF, and move to .401 base perhaps?
Click to expand...
Click to collapse
I did suggest that, but, somehow he never got the sense 6 update but is on hboot 1.57 and cant s-off
SaHiLzZ said:
Oh ok.. Interesting.
S-OFF, and move to .401 base perhaps?
Click to expand...
Click to collapse
Sorry I don't understand.
Also couldn't I circumvent this hassle just by installing this ROM?
http://forum.xda-developers.com/showthread.php?t=2224752
Seanie280672 said:
I did suggest that, but, somehow he never got the sense 6 update but is on hboot 1.57 and cant s-off
Click to expand...
Click to collapse
ODD! 4.2/4.3 should be on 1.55 Hboot..
@OP.. whats your fastboot getvar all ?
C:\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3838mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.049s
couldn't I circumvent this hassle just by installing this ROM?
http://forum.xda-developers.com/showthread.php?t=2224752
Its strange that you too have HBOOT 1.57, did you get the sense 6 update ?
Seanie280672 said:
Its strange that you too have HBOOT 1.57, did you get the sense 6 update ?
Click to expand...
Click to collapse
nope
Anarchy89 said:
couldn't I circumvent this hassle just by installing this ROM?
http://forum.xda-developers.com/showthread.php?t=2224752
Click to expand...
Click to collapse
Yes... You have 1.57 HBOOT.. you should NOT be using 2.x.771.x files. It does NOT gel well.
You have to stick with custom roms, just use adb push or adb sideload..
Anarchy89 said:
nope
Click to expand...
Click to collapse
Well you could try flashing twrp 2.6.3.3 and then flash that ROM your interested in, but it could make things worse, you have a very strange problem, I would love to know why custom rom's work and the guru-reset file, but the OTA's pretty much kill your phone.
SaHiLzZ said:
Yes... You have 1.57 HBOOT.. you should NOT be using 2.x.771.x files. It does NOT gel well.
You have to stick with custom roms, just use adb push or adb sideload..
Click to expand...
Click to collapse
Okay, well I don't know a lot about all this stuff, for example I don't know what HBOOT is, S-OFF/ON etc, I just look for ROMs I'm interested in, optimizing my phone, I just read guides and 99% of the time I don't have a problem.
Do you think my problem would go away if I had HBOOT 1.55? Is it even possible to downgrade?
I'll just flash the ROM I mentioned...but doesn't that mean I won't be able to get OTA updates? (because of the nonstock recovery)
IDFK
Don't know why your HBOOT is 1:57 while your device is not OTA to Sense 6.0. Certainly you can't downgrage HBOOT to 1:55 without S-OFF. You should flash TWRP 2.6.3.3, then adb sileload a custom rom to install
I just wiped and put android revolution hd 71.1 on there and it seems fine now, the other stock rom I mentioned earlier I flashed and I kept getting errors "unfortunately updater has stopped working" every 3 minutes.
I had a go at S-OFF with rumrunner but it didn't work on two ROMs, someone said to try it on linux as it's more reliable, any suggestions for how I can easily S-OFF? thanks :good:

[Q] Unable to go STOCK or flash other ROMs, adb shows device as offline

Hello xda members.
I'm having some trouble with my device, I did search around this past week but still didnt success in fixing it, hope someone can point me in the right direction.
So I was S-ON with 4.3 - 4.4 on ViperOne for a long time, most of the things worked fine but my 3G was a bit slow/disconnected from time to time.
I though giving a shot to a Lollipop version Sky Dragon. I downloaded and installed Sky Dragon and used it fine for some months, but then when I wanted to use Android Studio for a project my device was not recognized. I manually run adb devices and it would not show my device (debuggin on), tried some search on google but without success.
I though moving back to ViperOne / ARHD (I really missed SENSE) would solve my problem, so downloaded the rom and tried to install but it would always stuck in "formatting partition" process.
I manually put my device in fastboot and run getvar all which resulted in BLANK version-main, very strange.
I did some search but had only few similar cases, I tried to go to STOCK by re-lockocking bootloader, flashing stock firmware but the RUU.exe would always stop at 5% and show "fastboot_htc.exe has stopped working", again did some research but could not find a solution.
When I try to flash custom firmware through fastboot flash zip I will always get "(bootloader) Read zipped android_info fail FAILED (remote: 99 unknown fail)".
I then found a tool to write a version-main into the emmc and after flashing it in TWRP I got a 1.00.000.0 version-main. Tried all of above again with the same results. My device will be recognised as "offline" in adb devices.
Luckily I have some backups (viperone 4.3 and skydragon) that work fine except that I cant update and cant connect via adb.
I have outputted my getvar all, let me know if you need further info for my case.
(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: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3976mV
(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
What can you suggest me?
Thanks a lot guys, and sorry for the long story!
mindxpert said:
Hello xda members.
I'm having some trouble with my device, I did search around this past week but still didnt success in fixing it, hope someone can point me in the right direction.
So I was S-ON with 4.3 - 4.4 on ViperOne for a long time, most of the things worked fine but my 3G was a bit slow/disconnected from time to time.
I though giving a shot to a Lollipop version Sky Dragon. I downloaded and installed Sky Dragon and used it fine for some months, but then when I wanted to use Android Studio for a project my device was not recognized. I manually run adb devices and it would not show my device (debuggin on), tried some search on google but without success.
Click to expand...
Click to collapse
Update your driver to latest HTC drivers
Update you android SDK to latest version
I though moving back to ViperOne / ARHD (I really missed SENSE) would solve my problem, so downloaded the rom and tried to install but it would always stuck in "formatting partition" process.
Click to expand...
Click to collapse
What recovery version is installed on the phone?
I manually put my device in fastboot and run getvar all which resulted in BLANK version-main, very strange.
Click to expand...
Click to collapse
Not really, its a normal issue everyone get when using some twrp versions.
I did some search but had only few similar cases, I tried to go to STOCK by re-lockocking bootloader, flashing stock firmware but the RUU.exe would always stop at 5% and show "fastboot_htc.exe has stopped working", again did some research but could not find a solution.
Click to expand...
Click to collapse
Make sure to uninstall HTC Sync from your computer. Keep the drivers installed but uninstall HTC Sync. You are not giving any info about what ruu you are trying to flash but afaik, there is none you can use for this phone with s-on.
When I try to flash custom firmware through fastboot flash zip I will always get "(bootloader) Read zipped android_info fail FAILED (remote: 99 unknown fail)".
Click to expand...
Click to collapse
You can not flash custom firmware when S-ON...
I then found a tool to write a version-main into the emmc and after flashing it in TWRP I got a 1.00.000.0 version-main. Tried all of above again with the same results. My device will be recognised as "offline" in adb devices.
Click to expand...
Click to collapse
Having the version-main blank is not an issue preventing your phone to work properly, its only an aesthetic issue. The version-main can be restored by flashed the stock firmware back.
alray said:
Update your driver to latest HTC drivers
Update you android SDK to latest version
Click to expand...
Click to collapse
Already have the latest SDK version.
alray said:
What recovery version is installed on the phone?
Click to expand...
Click to collapse
I'm using TWRP 2.8.5.0
alray said:
Make sure to uninstall HTC Sync from your computer. Keep the drivers installed but uninstall HTC Sync. You are not giving any info about what ruu you are trying to flash but afaik, there is none you can use for this phone with s-on.
Click to expand...
Click to collapse
I found from my CID that this might be compatible RUU_M7_UL_K44_SENSE55_MR_Rogers_WWE_4.19.631.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_351317_signed_2.exe
alray said:
You can not flash custom firmware when S-ON...
Click to expand...
Click to collapse
So should I go S-OFF before? I'm not sure if I can downgrade and S-OFF in the current condition.
alray said:
Having the version-main blank is not an issue preventing your phone to work properly, its only an aesthetic issue. The version-main can be restored by flashed the stock firmware back.
Click to expand...
Click to collapse
Thank you for the clarification
mindxpert said:
Already have the latest SDK version.
Click to expand...
Click to collapse
And latest HTC drivers? Your phone should be visible from "my computer" when booted in twrp 2.8.5.0 cause twrp now have mtp support.
Code:
I found from my CID that this might be compatible RUU_M7_UL_K44_SENSE55_MR_Rogers_WWE_4.19.631.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_351317_signed_2.exe
Not with s-on. 4.19.631.9 is a downgrade, you need s-off to downgrade.
So should I go S-OFF before? I'm not sure if I can downgrade and S-OFF in the current condition.
Click to expand...
Click to collapse
You can go s-off using sunshine s-off but it cost 25$ or you can flash other roms by fixing your adb issues.
alray said:
And latest HTC drivers? Your phone should be visible from "my computer" when booted in twrp 2.8.5.0 cause twrp now have mtp support.
Click to expand...
Click to collapse
Yes my device is visible when in recovery.
alray said:
I found from my CID that this might be compatible RUU_M7_UL_K44_SENSE55_MR_Rogers_WWE_4.19.631.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_351317_signed_2.exe
Not with s-on. 4.19.631.9 is a downgrade, you need s-off to downgrade.
You can go s-off using sunshine s-off but it cost 25$ or you can flash other roms by fixing your adb issues.
Click to expand...
Click to collapse
I used sunshine to s-off my device. Currently downloading files from your signature post which had a case with my CID and MID to return stock then update firmware/rom,
Thanks, will report back tomorrow.

[Q] htc one m7_u stock recovery?

Hello
I've been trying to install ota bugfixes on my HTC one m7_U (running android lollipop 5.0.2 official) but because I'm on cwm recovery it's not working. Does anyone have the lollipop stock recovery for the HTC one m7 _U?
Thanks!
So frustrating, I've tried more than 10 recoveries but it's not working, the update stops midprocess and the device reboots.
monrokhoury said:
Hello
I've been trying to install ota bugfixes on my HTC one m7_U (running android lollipop 5.0.2 official) but because I'm on cwm recovery it's not working. Does anyone have the lollipop stock recovery for the HTC one m7 _U?
Thanks!
Click to expand...
Click to collapse
Post the output of "fastboot getvar all" so we can tell which recovery you need exactly.
monrokhoury said:
So frustrating, I've tried more than 10 recoveries but it's not working, the update stops midprocess and the device reboots.
Click to expand...
Click to collapse
hold volume up and hit power to see the error message and post it here.
@alray thanks for helping! i actually found the stock recovery here: http://forum.xda-developers.com/showpost.php?p=61267713&postcount=439
i flashed it then updated which worked but the phone is stuck at the htc logo screen and refuses to boot up. what do i need to do?
really frustrating, i've lost faith in htc and will be switching to a galaxy s5/s6 soon if there's anyone who can help me revive this phone that's you guys
monrokhoury said:
@alray thanks for helping! i actually found the stock recovery here: http://forum.xda-developers.com/showpost.php?p=61267713&postcount=439
i flashed it then updated which worked but the phone is stuck at the htc logo screen and refuses to boot up. what do i need to do?
really frustrating, i've lost faith in htc and will be switching to a galaxy s5/s6 soon if there's anyone who can help me revive this phone that's you guys
Click to expand...
Click to collapse
post the output of "fastboot getvar all"
---------- Post added at 10:26 AM ---------- Previous post was at 10:00 AM ----------
monrokhoury said:
@alray thanks for helping! i actually found the stock recovery here: http://forum.xda-developers.com/showpost.php?p=61267713&postcount=439
i flashed it then updated which worked but the phone is stuck at the htc logo screen and refuses to boot up. what do i need to do?
really frustrating, i've lost faith in htc and will be switching to a galaxy s5/s6 soon if there's anyone who can help me revive this phone that's you guys
(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: 7.19.401.121
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4161mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s
Click to expand...
Click to collapse
So you were on 7.19.401.102 and updated to 7.19.401.121 and the phone is stuck at htc logo. How log did you waited for the phone to boot? First boot can take up to 10-15 minutes on lollipop.
@alray more than half an hour
monrokhoury said:
@alray more than half an hour
Click to expand...
Click to collapse
Did you unlocked the bootloader via htcdev.com when the phone was on 7.19.401.102? If so did you restored everything back to stock before updating like /data/preload? No modification to /system? Any custom kernel installed before the update?
For now try a factory reset and check if it will boot (wait at least 10-15 min on the htc white screen)
@alray everything was stock 100% but the bootloader was unlocked. prelode data present and all
did a factory reset waited for more than 30 minutes nothing happened
monrokhoury said:
@alray everything was stock 100% but the bootloader was unlocked. prelode data present and all
did a factory reset waited for more than 30 minutes nothing happened
Click to expand...
Click to collapse
So I guess you will have to re-flash a custom recovery and flash a nandroid backup of 7.19.401.121 or a custom rom maybe?
Edit: can't find any backup of 7.19.401.121, I think flashing a custom rom like MaximusHD, ARHD or something similar is your best bet for now, maybe someone will upload a backup of 7.19.401.121 later but at least you'll be able to use your phone right now.
@alray don't know much about custom roms but i can try.. do you recommend maximus HD or nusenseven?
do i need s-off to flash a custom rom??
@alray also do i need s-off to use a nanodroid backup? i found one that i created using cwm can i flash it using twrp? where should i place it?
sooooo sorry for toooo many questions
monrokhoury said:
@alray
do i need s-off to flash a custom rom??
Click to expand...
Click to collapse
You don't need s-off
monrokhoury said:
@alray also do i need s-off to use a nanodroid backup?
Click to expand...
Click to collapse
No
i found one that i created using cwm can i flash it using twrp?
Click to expand...
Click to collapse
No, if it was made with CWM it must be restore with CWM.
@alray Thanks! Phone working on 7.19.401.121! Had to flash a cwm recovery and restore my nandroid backup, wipe data/factory reset upgrade to lollipop another reset then upgrade to 7.19.401.121.. took me a while but it worked.
I think I'll make a thread on how to fix these problems..

Categories

Resources