Database Develop

[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!

Accidentally erased operating system on HTC One M7

Hi, i run an HTC One M7 that was originally from AT&T. I unlocked it and use it in my country. Few days ago i wanted to install the stock Android and try it. I did everything as was said - unlocked the bootloader, s-off, recovery etc. after a few hours of the stock Android experience i wanted to change it to ARHD. As i changed it a question popped out asking if i want to root my device. I answered "yes", not knowing what it means. My phone was bricked and stuck on the HTC welcome screen since yesterday. I tried a lot of differend ways of fixing it and still no results. I locked and unlocked the bootloader again, tried to install the official RUU, but it doesn't want to. I get MTP driver error when connecting to my computer.
I have "can't mount SD card" on my phone. I'm pretty desperate, but i want to fix this issue and get back my phone. This will be a lesson for me.

Skyrocker94 said:
Hi, i run an HTC One M7 that was originally from AT&T. I unlocked it and use it in my country. Few days ago i wanted to install the stock Android and try it. I did everything as was said - unlocked the bootloader, s-off, recovery etc. after a few hours of the stock Android experience i wanted to change it to ARHD. As i changed it a question popped out asking if i want to root my device. I answered "yes", not knowing what it means. My phone was bricked and stuck on the HTC welcome screen since yesterday. I tried a lot of differend ways of fixing it and still no results. I locked and unlocked the bootloader again, tried to install the official RUU, but it doesn't want to. I get MTP driver error when connecting to my computer.
I have "can't mount SD card" on my phone. I'm pretty desperate, but i want to fix this issue and get back my phone. This will be a lesson for me.
Click to expand...
Click to collapse
post your fastboot getvar all minus the serial no and IMEI so we can find the files you'll need to restore you phone

clsA said:
post your fastboot getvar all minus the serial no and IMEI so we can find the files you'll need to restore you phone
Click to expand...
Click to collapse
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: --------------------
(bootloader) imei: -------------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.120s
Here we go! thanks a lot!!

Skyrocker94 said:
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: --------------------
(bootloader) imei: -------------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.120s
Here we go! thanks a lot!!
Click to expand...
Click to collapse
download this ruu and run it, its the same version you already have / had on your phone, if you bootloader is unlocked then you will need to re-lock it first.
http://www.htc1guru.com/dld/ruu_m7_...9_10-26-1718-01l_release_356565_signed_2-exe/
with regards to your drivers problem, see FAQ 2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2

Thanks a ton!!! i hope it works!!!

Skyrocker94 said:
Thanks a ton!!! i hope it works!!!
Click to expand...
Click to collapse
fastboot oem lock
relocks the bootloader to run the RUU
if you have problems with the RUU
try this / unlocking the bootloader / flashing TWRP 2.6.3.3 and sideload this Guru Reset >> http://www.androidfilehost.com/?fid=23501681358545274

It worked. Thank you very much!
"Ask and it shall be given to you"

same issue here, no more SO and stuck in HTC log
Hello, help me please, i've search the RUU for restore my HTC but not are sure where's the right.
Here Original "fastboot getvar all" when device was working also w/o SO.
INFOversion: 0.5
INFOversion-bootloader: 1.57.0000
INFOversion-baseband: 4T.27.3218.14
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno:
INFOimei:
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: H3G__402
INFObattery-status: good
INFObattery-voltage: 4102mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-1f512bb6
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Thanks a lot for help, sorry for my English.

vanito said:
Hello, help me please, i've search the RUU for restore my HTC but not are sure where's the right.
Here Original "fastboot getvar all" when device was working also w/o SO.
Thanks a lot for help, sorry for my English.
Click to expand...
Click to collapse
another H3G__402 you need help from @Danny201281
he has the same phone

vanito said:
Hello, help me please, i've search the RUU for restore my HTC but not are sure where's the right.
Here Original "fastboot getvar all" when device was working also w/o SO.
Thanks a lot for help, sorry for my English.
Click to expand...
Click to collapse
Well I'm H3G__001 UK. H3G__402 is Italy right? Not that it makes a difference the software is all the same.
Unfortunately there is no ruu for H3G. What exactly happened with your phone it can hopefully be fixed without the need for an ruu.
Bad flash, wiped your os? Can you access bootloader or recovery?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk

Danny201281 said:
Well I'm H3G__001 UK. H3G__402 is Italy right? Not that it makes a difference the software is all the same.
Unfortunately there is no ruu for H3G. What exactly happened with your phone it can hopefully be fixed without the need for an ruu.
Bad flash, wiped your os? Can you access bootloader or recovery?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
this phone was w/o SO since i've buyed of 2 handle. was installed only a Custom Rom. i want make it S-OFF for installl anythingh for error from TWRP have done advanced wipe and have erase also this Rom whith all partition and BKP.
Phone enter in Recovery, hboot, fastboot and can flash RUU signed, (have tried with an BOX to flash Guru reset but Error becouse No signature), or if you have other Rom or other for fix this issue and after i want make S-OFF for change this Bad cid, if can help me please

vanito said:
this phone was w/o SO since i've buyed of 2 handle. was installed only a Custom Rom. i want make it S-OFF for installl anythingh for error from TWRP have done advanced wipe and have erase also this Rom whith all partition and BKP.
Phone enter in Recovery, hboot, fastboot and can flash RUU signed, (have tried with an BOX to flash Guru reset but Error becouse No signature), or if you have other Rom or other for fix this issue and after i want make S-OFF for change this Bad cid, if can help me please
Click to expand...
Click to collapse
Hi and sorry for the delayed reply, as I say there is no ruu for h3g, but it sounds as if you just need to push a compatible Rom to the phone, what is you current version of TWRP.
I do have some h3g stock nandroids, one for jb 4.3 and one for kk 4.4.2. I'll need to upload them for you and I can't do that until later this evening as I'm in work now. If you want to go s-off the jb 4.3 nandroid has worked for me everytime so would be worth a try. I'll upload it tonight and send you a link as soon as it's available.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk

You're such a nice and friendly forum mate, @Danny201281
tetakpatalked from Nexus 7 flo

Danny201281 said:
Hi and sorry for the delayed reply, as I say there is no ruu for h3g, but it sounds as if you just need to push a compatible Rom to the phone, what is you current version of TWRP.
I do have some h3g stock nandroids, one for jb 4.3 and one for kk 4.4.2. I'll need to upload them for you and I can't do that until later this evening as I'm in work now. If you want to go s-off the jb 4.3 nandroid has worked for me everytime so would be worth a try. I'll upload it tonight and send you a link as soon as it's available.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
Not worry, important i can fix with you help this problem.
My version of TWRP installed now is "twrp-2.7.1.0a-m7" this device first of i Erase all had installed an VENOM Rom, not remember wich ViperOnes version, my Getvar All you have seen, i want listen to you becouse not understand good about these HTC w/o sd card.
If you can send to me this nandroid jb 4.3 and if please write also if i can flash how normal rom/Ruu or how do.... you help is very good for me :good:
wait for you link to download, please if cannot use Mega.co is good becouse here is blocked and impossible open this, Ciao:good:

vanito said:
Not worry, important i can fix with you help this problem.
My version of TWRP installed now is "twrp-2.7.1.0a-m7" this device first of i Erase all had installed an VENOM Rom, not remember wich ViperOnes version, my Getvar All you have seen, i want listen to you becouse not understand good about these HTC w/o sd card.
If you can send to me this nandroid jb 4.3 and if please write also if i can flash how normal rom/Ruu or how do.... you help is very good for me :good:
wait for you link to download, please if cannot use Mega.co is good becouse here is blocked and impossible open this, Ciao:good:
Click to expand...
Click to collapse
Ok sorry I was very busy last night. I am on this for you now, I'll post link as soon as it's ready but my upload seed is very poor
I created this nandroid using TWRP 2.6.3.3 but it should restore fine using other versions of TWRP.
Do you have adb working when in recovery mode? You will need it to push the nandroid to the device.

Danny201281 said:
Ok sorry I was very busy last night. I am on this for you now, I'll post link as soon as it's ready but my upload seed is very poor
I created this nandroid using TWRP 2.6.3.3 but it should restore fine using other versions of TWRP.
Do you have adb working when in recovery mode? You will need it to push the nandroid to the device.
Click to expand...
Click to collapse
Hello, can leave this version of TWRP: "twrp-2.7.1.0a-m7", that i've or you can suggest another version?
System not Mount, i've tryed to push in fastbootRUU but fail anythinghs i want push.
I've tryed putting phone in Recovery mode and i can see from "device manager" that have "adb android" or similar then if open can see "My Htc", if i put in normal mode, (is w/o Boot.img), i can see MTP that install/uninstall and phone how "Cd Unit external", (cannot open).
Not warry where upload it, important not use Mega.co becouse in Italy is Blocked, any other site is ok.
Please can send to me also Command for Push this Nandroid 4.3 in Recovery mode?, (i've also one dongle + sw but for Flash anythinghs requiere fastboot RUU mode), anyway i'm looking forward this Nandroid Bkp and how push in phone hooping that i can fix the phone

@vanito backup done with TWRP 2.6.3.3 is compatible with 2.7.1.0
He is asking you about ADB and using command line of your PC to push the files. Do you know how to do it? Do you have SDK installed on your PC?
tetakpatalked from N7100

vanito said:
Hello, can leave this version of TWRP: "twrp-2.7.1.0a-m7", that i've or you can suggest another version?
System not Mount, i've tryed to push in fastbootRUU but fail anythinghs i want push.
I've tryed putting phone in Recovery mode and i can see from "device manager" that have "adb android" or similar then if open can see "My Htc", if i put in normal mode, (is w/o Boot.img), i can see MTP that install/uninstall and phone how "Cd Unit external", (cannot open).
Not warry where upload it, important not use Mega.co becouse in Italy is Blocked, any other site is ok.
Please can send to me also Command for Push this Nandroid 4.3 in Recovery mode?, (i've also one dongle + sw but for Flash anythinghs requiere fastboot RUU mode), anyway i'm looking forward this Nandroid Bkp and how push in phone hooping that i can fix the phone
Click to expand...
Click to collapse
twrp 2.7.1.0 should work fine :good:
adb will only work in recovery mode. Put phone in recovery and connect usb. Then in the adb/fastboot command line type
Code:
adb devices
You should see an output of your phone's serial no. If you did it's working. You can test adb push with a Rom if you have one. Rename the Rom file to "rom.zip" and put it in your adb/fastboot folder. Then in the command line type
Code:
adb push rom.zip /sdcard
The push will take several minutes the command window will be unresponsive until it's done. When it's finished the push you should be able to Install the Rom using TWRP.
P.S. The stock nandroid is uploading to dropbox. This is ok for use in Italy?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk

@vanito you have got a real little guide for Windows by @Danny201281
In the case that you are a Linux user, it works just slightly different: in such case check my little thread about running fastboot & ADB in Ubuntu. It is posted in the Nexus 7 section but ADB works for Samsung just the same way.
tetakpatalked from Nexus 7 flo

Danny201281 said:
twrp 2.7.1.0 should work fine :good:
adb will only work in recovery mode. Put phone in recovery and connect usb. Then in the adb/fastboot command line type
Code:
adb devices
You should see an output of your phone's serial no. If you did it's working. You can test adb push with a Rom if you have one. Rename the Rom file to "rom.zip" and put it in your adb/fastboot folder. Then in the command line type
Code:
adb push rom.zip /sdcard
The push will take several minutes the command window will be unresponsive until it's done. When it's finished the push you should be able to Install the Rom using TWRP.
P.S. The stock nandroid is uploading to dropbox. This is ok for use in Italy?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
@Danny201281, ok i have this twrp 2.7.1.0 also and can install replace the other one i've installed:good:
Yes i've installed adb&fastboot in C: (principal directory), i use Win7 32 bit and can use also win Xp in the 2 pcs i've adb&fastboot installed.:good:
Yes, i know a little about use of these adb or fastboot, specific command for this case i can copy from this you good guide:good:
I've tested pushing "guru reset..." from fastboot yesterday but have get one Error 24, not have tested pushing via Adb command, but now i see you command above and can test this.
Sorry, i not know which Rom can push and if you can advise me about wich push is big help, (if you can post only link to Rom) for me, if possible any Rom for to make S-Off after that i fix this phone.
Yes, Dropbox i can use here if you give me access for download the Nandroid Bkp 4.3.
Last question, if push of Rom goes all ok, after i open phone in recovery and find this Rom in Sd Card, right?...then from "Install>Sd Card>Rom" swipe and will be installed right?
Ok, after i install this Rom always from recovery can install you nondroid bkp 4.3, ok?, :good:
I'm ready if can send to me link for this Rom and Link of dropbox i want try to ceck anythinghs.

[Q] Applying Backup from one phone to another

Hi Guys,
This might be a little confusing but i will do my best.....About 6 months ago i bought a htc 1 m7, love it and it worked well. Then i decided to root it which was fine but then the OTA update came out so i can make phonecalls again, but i cant install it. Spur of the moment i bought another htc one m7 of ebay because i desperately needed to make and take calls. Turned up a couple of days ago and there seems to be some interesting stuff going on. Firstly i think it is a "test device" I cant remember where but somewhere it does say that its a test device in red writing.Also compared to my old phone the screen is more "brown" as if a filter is being applied. I'm guessing a non-oem screen was fitted that isn't as good quality as the original. I checked and the bootloader is locked and is working but it is still on android 4.4.2 and sense 5.0 and it says its up to date and wont move to sense 6.0.
So currently i'm looking for a way to either "un-test device" the new htc 1 m7 as im guessing that's why its not getting the new updates, or secondly is there anyway to get the ota updates on the rooted htc 1? I'm fairly good tech guy but...being my first android phone i guess you guys would call me a noob.
One other thought i had. If i could get the new phone to update to the latest update and then i rooted it, installed cmw and did a backup could i then load that backup as a recovery on my old phone? I'm not sure if that would work or not.....
Anyway hope you guys can help me out, i dont really care which phone i end up using one has a cracked screen and the other dose not look the best i just want to have the latest updates AND be able to make phonecalls...
Thanks All,
Joel

Happyhog11 said:
Hi Guys,
This might be a little confusing but i will do my best.....About 6 months ago i bought a htc 1 m7, love it and it worked well. Then i decided to root it which was fine but then the OTA update came out so i can make phonecalls again, but i cant install it. Spur of the moment i bought another htc one m7 of ebay because i desperately needed to make and take calls. Turned up a couple of days ago and there seems to be some interesting stuff going on. Firstly i think it is a "test device" I cant remember where but somewhere it does say that its a test device in red writing.Also compared to my old phone the screen is more "brown" as if a filter is being applied. I'm guessing a non-oem screen was fitted that isn't as good quality as the original. I checked and the bootloader is locked and is working but it is still on android 4.4.2 and sense 5.0 and it says its up to date and wont move to sense 6.0.
So currently i'm looking for a way to either "un-test device" the new htc 1 m7 as im guessing that's why its not getting the new updates, or secondly is there anyway to get the ota updates on the rooted htc 1? I'm fairly good tech guy but...being my first android phone i guess you guys would call me a noob.
One other thought i had. If i could get the new phone to update to the latest update and then i rooted it, installed cmw and did a backup could i then load that backup as a recovery on my old phone? I'm not sure if that would work or not.....
Anyway hope you guys can help me out, i dont really care which phone i end up using one has a cracked screen and the other dose not look the best i just want to have the latest updates AND be able to make phonecalls...
Thanks All,
Joel
Click to expand...
Click to collapse
first of all post your fastboot getvar all of the phone that says this is a test device please, remove imei and serial number before posting please, sounds s-off to me, and that's a good thing.

Happyhog11 said:
Hi Guys,
This might be a little confusing but i will do my best.....About 6 months ago i bought a htc 1 m7, love it and it worked well. Then i decided to root it which was fine but then the OTA update came out so i can make phonecalls again, but i cant install it. Spur of the moment i bought another htc one m7 of ebay because i desperately needed to make and take calls. Turned up a couple of days ago and there seems to be some interesting stuff going on. Firstly i think it is a "test device" I cant remember where but somewhere it does say that its a test device in red writing.Also compared to my old phone the screen is more "brown" as if a filter is being applied. I'm guessing a non-oem screen was fitted that isn't as good quality as the original. I checked and the bootloader is locked and is working but it is still on android 4.4.2 and sense 5.0 and it says its up to date and wont move to sense 6.0.
So currently i'm looking for a way to either "un-test device" the new htc 1 m7 as im guessing that's why its not getting the new updates, or secondly is there anyway to get the ota updates on the rooted htc 1? I'm fairly good tech guy but...being my first android phone i guess you guys would call me a noob.
One other thought i had. If i could get the new phone to update to the latest update and then i rooted it, installed cmw and did a backup could i then load that backup as a recovery on my old phone? I'm not sure if that would work or not.....
Anyway hope you guys can help me out, i dont really care which phone i end up using one has a cracked screen and the other dose not look the best i just want to have the latest updates AND be able to make phonecalls...
Thanks All,
Joel
Click to expand...
Click to collapse
Ok there's a few reasons why you may not be receiving OTA updates on the first device.
The second device (test device) Sounds like it's s-off that's not something you want to fix there are many benefits to having the device s-off. As for transferring backups between devices that should be fine as long as their both of the same model id. To be sure of all this can you please post the output of
Code:
fastboot getvar all
For both devices :good:

Hi Guys
So here is the code for the old phone.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.11.980.7
(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: HTC__039
(bootloader) battery-status: good
(bootloader) battery-voltage: 3814mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
As for the new phone, surprisingly out of the blue today it notified me it needed a update to fix the audio so i let it start downloading but my internet is awfully slow so i cant turn it off for another 4 hours. After the update is finished i will post the fastboot stuff asap
Have to look into this s-off thing some more. I have no idea what it means but it sounds interesting
Thanks Again
Joel

Hi Again,
It just finished the update so here is the code for the new phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.11.980.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
(bootloader) battery-status: good
(bootloader) battery-voltage: 3969mV
(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
You guys were right it is s-off but the bootloader is locked which is interesting. And they have the same model id so i can copy backup's between devices which is also cool.
So Danny you said there could be a number of reasons why my old htc is not getting the ota update, care to elaborate? i have the actual update file which is a zip saved on my pc, i just figured because it was rooted and has a different recovery than stock the ota would continue to fail, if there is a way to get it to work that would be awesome, as it would mean i wouldn't loose all my apps compared to restoring a backup from the second phone.
Cheers Guys,
Joel

Happyhog11 said:
Hi Again,
It just finished the update so here is the code for the new phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.11.980.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
(bootloader) battery-status: good
(bootloader) battery-voltage: 3969mV
(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
You guys were right it is s-off but the bootloader is locked which is interesting. And they have the same model id so i can copy backup's between devices which is also cool.
So Danny you said there could be a number of reasons why my old htc is not getting the ota update, care to elaborate? i have the actual update file which is a zip saved on my pc, i just figured because it was rooted and has a different recovery than stock the ota would continue to fail, if there is a way to get it to work that would be awesome, as it would mean i wouldn't loose all my apps compared to restoring a backup from the second phone.
Cheers Guys,
Joel
Click to expand...
Click to collapse
first of all, remove imei and serial numbers from your outputs in your 2 posts, these are 2 numbers you want to keep to yourself, the s-off phone is the better one and easier to work with, leave it s-off, don't ever go s-on, you will regret it, you can follow this very simple step by step guide to get this phone receiving updates again, all the way upto lollipop: http://forum.xda-developers.com/htc-one/general/guide-convert-m7-developer-edition-t2840311 you will need to unlock the bootloader first though to do this.

Happyhog11 said:
Hi Again,
It just finished the update so here is the code for the new phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.11.980.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
(bootloader) battery-status: good
(bootloader) battery-voltage: 3969mV
(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
You guys were right it is s-off but the bootloader is locked which is interesting. And they have the same model id so i can copy backup's between devices which is also cool.
So Danny you said there could be a number of reasons why my old htc is not getting the ota update, care to elaborate? i have the actual update file which is a zip saved on my pc, i just figured because it was rooted and has a different recovery than stock the ota would continue to fail, if there is a way to get it to work that would be awesome, as it would mean i wouldn't loose all my apps compared to restoring a backup from the second phone.
Cheers Guys,
Joel
Click to expand...
Click to collapse
Well I was first thinking maybe it was AT&T and AT&T phones only get OTA's when connected to the AT&T network but that's not the case here.
Are both devices running a the same stock rom. As they are identical you could just make a nandroid of the System and Boot partitions from the s-off device then restore these to the other device without loosing any user data. Could you maybe post a screen shot of the Settings>About>Software information screen from each of the devices?

It's not that it cant "get" the ota updates its more that it wont install.
Also I'm in Aus, as for the first phone it was bought outright through a retailer and i have no idea for the second phone(eBay guy didn't leave any history about the phone.)
I have just put cmw on the new phone so now i can do the guide posted by Seanie280672.
Will post the screenshots in a sec.
Will need your help with making a backup of just the boot and system partitions......don't know how to do that.
Joel

Okay This is the "old phone" screenshot:
https://drive.google.com/file/d/0B5yAH_RjUp-KQmU2bkJfUVlINXc/view?usp=sharing

Okay here is the screenshot for the new phone
https://drive.google.com/file/d/0B5yAH_RjUp-KcmRIUjZIOVN2TU0/view?usp=sharing
Also sorry Google drive was the quickest way to get pictures online from my laptop at the moment.
Only difference is the software number the old phone is x.x.x.7 not x.x.x.12 which im guessing is the update to fix audio.
Not sure if it is relevant but i have the file "OTA_M7_UL_K443_SENSE60_MR_Optus_AU_6.11.980.12-6.11.980.7_release_407474r14kwjhfpdkw8z4t" Thats the update file that the old phone downloaded to fix audio which would make it identical to the new phone, but alas it dose not install.
So i guess the "nandroid of the System and Boot partitions from the s-off device then restore these to the other device without loosing any user data" is still the best solution?
Thanks again i know i say that alot but could not have done this without your help!
Joel

Wait....i was of the belief that cmw was the reason i couldnt install ota's. Is that correct? If so what if i just put the original stock recovery back on the old phone(link http://forum.xda-developers.com/showthread.php?t=2158151) then let the update install and then put cmw back on..... i dont know if it will work but its another method, maybe i have this all back the front lol

Happyhog11 said:
Okay here is the screenshot for the new phone
https://drive.google.com/file/d/0B5yAH_RjUp-KcmRIUjZIOVN2TU0/view?usp=sharing
Also sorry Google drive was the quickest way to get pictures online from my laptop at the moment.
Only difference is the software number the old phone is x.x.x.7 not x.x.x.12 which im guessing is the update to fix audio.
Not sure if it is relevant but i have the file "OTA_M7_UL_K443_SENSE60_MR_Optus_AU_6.11.980.12-6.11.980.7_release_407474r14kwjhfpdkw8z4t" Thats the update file that the old phone downloaded to fix audio which would make it identical to the new phone, but alas it dose not install.
So i guess the "nandroid of the System and Boot partitions from the s-off device then restore these to the other device without loosing any user data" is still the best solution?
Thanks again i know i say that alot but could not have done this without your help!
Joel
Click to expand...
Click to collapse
Ok this may get a little complicated but I'll try to make it as clear as possible
You can use the system and Boot nandroid from the s-off device to update the Rom on the s-on device. Then make a full nandroid backup of the s-on device of System, boot and data. (so now you have a nandroid of the updated Rom with all your apps and settings) now backup the internal storage of the s-on device to your pc.
Now you can extract the firmware.zip from the OTA file and manually flash the firmware to the s-on device to update the firmware. This will require you to relock the bootloader and when you unlock the bootloader the device will be wiped (that's the reason we backup the internal storage to the pc) so you can Unlock the bootloader again restore the internal storage with your pc backup then Flash twrp and restore the nandroid and heypresto the s-on device is fully updated with Rom and Firmware. If you need further instruction on how the flash the firmware from the OTA just let me know
---------- Post added at 04:02 PM ---------- Previous post was at 03:59 PM ----------
Happyhog11 said:
Wait....i was of the belief that cmw was the reason i couldnt install ota's. Is that correct? If so what if i just put the original stock recovery back on the old phone(link http://forum.xda-developers.com/showthread.php?t=2158151) then let the update install and then put cmw back on..... i dont know if it will work but its another method, maybe i have this all back the front lol
Click to expand...
Click to collapse
Yes that's correct if you flash the stock recovery you should be able to install the ota. Although if the stock Rom is modified in some way the OTA may fail to install.

Danny201281 said:
Ok this may get a little complicated but I'll try to make it as clear as possible
You can use the system and Boot nandroid from the s-off device to update the Rom on the s-on device. Then make a full nandroid backup of the s-on device of System, boot and data. (so now you have a nandroid of the updated Rom with all your apps and settings) now backup the internal storage of the s-on device to your pc.
Now you can extract the firmware.zip from the OTA file and manually flash the firmware to the s-on device to update the firmware. This will require you to relock the bootloader and when you unlock the bootloader the device will be wiped (that's the reason we backup the internal storage to the pc) so you can Unlock the bootloader again restore the internal storage with your pc backup then Flash twrp and restore the nandroid and heypresto the s-on device is fully updated with Rom and Firmware. If you need further instruction on how the flash the firmware from the OTA just let me know
---------- Post added at 04:02 PM ---------- Previous post was at 03:59 PM ----------
Yes that's correct if you flash the stock recovery you should be able to install the ota. Although if the stock Rom is modified in some way the OTA may fail to install.
Click to expand...
Click to collapse
Okay your method sounds like a fun experience, as long as your sure my data is safe . Will do a manual backup first anyway. As for the nandroid stuff tho...im allitle confused. with cmw there are not any options to what is included and excluded? or am i missing somehting......Sorry for the noob question.
And yes please i have no clue how to flash firmware, guess you just use fastboot? help would be great

Happyhog11 said:
Okay your method sounds like a fun experience, as long as your sure my data is safe [emoji14]. Will do a manual backup first anyway. As for the nandroid stuff tho...im allitle confused. with cmw there are not any options to what is included and excluded? or am i missing somehting......Sorry for the noob question.
And yes please i have no clue how to flash firmware, guess you just use fastboot? help would be great
Click to expand...
Click to collapse
Yeah my instruction kinda assumes you are using TWRP recovery [emoji14] no one uses CWM on HTC one anymore. TWRP if a far better recovery for best results use TWRP 2.6.3.3 other newer versions all have some bugs of some sort. 2.6.3.3 is bug free and stable :good:

Happyhog11 said:
Okay your method sounds like a fun experience, as long as your sure my data is safe . Will do a manual backup first anyway. As for the nandroid stuff tho...im allitle confused. with cmw there are not any options to what is included and excluded? or am i missing somehting......Sorry for the noob question.
And yes please i have no clue how to flash firmware, guess you just use fastboot? help would be great
Click to expand...
Click to collapse
Edit: this is possible with cmw or do i need to swap to twrp? Also as for the firmware is that just the zip called "firmware.zip" inside the ota zip? what do you do with the images inside? Shame on htc for putting a zip in a zip its just plain bad practice lol

Happyhog11 said:
Edit: this is possible with cmw or do i need to swap to twrp? Also as for the firmware is that just the zip called "firmware.zip" inside the ota zip? what do you do with the images inside? Shame on htc for putting a zip in a zip its just plain bad practice lol
Click to expand...
Click to collapse
Ok this is what I was afraid of when I said it might get complicated.
So first unfortunately I'm really not sure what CWM is and is not capable of these days I have not used it for about 4 years lol, since my galaxy ace days. Either way I would definitely recommend switching to twrp for your HTC one. Although you will need to make new nandroids if you do as TWRP is not compatible with CWM backups as far as I'm aware. TWRP allows you to backup and restore partitions separately.
You are correct about the firmware.zip inside the OTA file just extract the firmware.zip from the OTA and then you can flash the firmware.zip with fastboot. You must be sure you update the Rom before the firmware though or the phone won't boot after flashing the firmware. This is not an unrecoverable situation but will further complicate matters.
To manually update the firmware put the firmware.zip in your fastboot folder.
Boot the phone to the bootloader connected with fastboot usb. In the command window type.
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Your device will reboot to the bootloader and should now be ***RELOCKED***
Code:
fastboot oem rebootRUU
**--- Case sensative ---^^^
Your device should boot to a black screen with a Silver HTC logo. This is RUU mode. We can now flash the firmware. In the command window type
Code:
fastboot flash zip firmware.zip
The first flash will be short, and will appear to fail. Thats normal its just a pre update preparing the hboot for the firmware. The phone screen will go black then return to RUU mode. So now we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal. As long as the command window has finished its output its done. Reboot to the bootloader.
Code:
fastboot reboot-bootloader
Just for the record if the device was s-off like the other one there is never any need to relock the bootloader as s-off allows flashing while unlocked.

Okay super quick question. I'm trying to flash twrp onto one of the phones but how do i use adb/fastboot with multiple devices plugged in? cant figure it out.....the other device is being backed up.

Happyhog11 said:
Okay super quick question. I'm trying to flash twrp onto one of the phones but how do i use adb/fastboot with multiple devices plugged in? cant figure it out.....the other device is being backed up.
Click to expand...
Click to collapse
Fastboot should only see the device that's in the bootloader.
E.g if one device is booted to Android or Recovery (this will be the device your backing up) only adb should see this device.
So you can flash twrp to the other device while in the bootloader with fastboot
Code:
fastboot erase cache
fastboot flash recovery "name-of-recovery".img
fastboot reboot-bootloader

So just so I'm sure we are on the same page I'm going to:
1. System/Boot Nandroid from s-off device
2. System/Boot/Data Nandroid from s-on device
3. Backup files from s-on device to pc
4. Follow your steps flash firmware updates.
5. Copy Files back to phone
6. flash twrp back onto device
7. Restore The nandroid from step 2
8. Heypresto my s-onn phone now has the latest firmware and all my data just as before?
Hope i've got that right makes sense really

Okay so I've flashed twrp onto both phones, backup of the s-off is complete, backup of the s-off is ongoing.
This...i have to say is uber cool. Having two identical phones is going to be super fun when it comes to custom roms and backups and stuff like that, if one phone dies ill just apply the back to the other...super cool stuff

Need to restore stock ROM to sim unlock m7 ATT. Encountering difficulties.

I have an m7 ATT with HBoot 1.44, S-off, and rooted with a CM12 nightly. CID is CWS_001. I'm switching to T-Mobile and as expected when I throw my t-mobile SIM in and punch in the the unlock code it doesn't work. Unless someone knows of a better solution I need to restore the stock rom, but I don't have a nandroid backup of it anymore. I've been doing research for awhile, but there is a lot of information on this topic and I'm a bit lost. What I've come up with seems to suggest that I won't be able to use my touchscreen if I flash a Stock nandroid because they are all so old. I could really use some advice on how to proceed from this point.

Have you looked at this?
http://www.htc1guru.com/guides/return-stock-guide/
Sent from my Nexus 7 using Tapatalk

ZBell said:
Have you looked at this?
http://www.htc1guru.com/guides/return-stock-guide/
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I did come across that in my research. Is that the only solution? Also, it uses an RUU versioned 1.2x. Is that not a problem like it is in nandroids versioned 1.2x? I'm worried about not being able to use the device afterward. Also, if possible I would like to avoid using a method that is so destructive to existing data. I have data backups of course, but it's just another thing that can go wrong later.

Dr3x1 said:
I did come across that in my research. Is that the only solution? Also, it uses an RUU versioned 1.2x. Is that not a problem like it is in nandroids versioned 1.2x? I'm worried about not being able to use the device afterward. Also, if possible I would like to avoid using a method that is so destructive to existing data. I have data backups of course, but it's just another thing that can go wrong later.
Click to expand...
Click to collapse
post your fastboot getvar all please without imei and serial number please.
you are right, your unlock code will only work with stock rom.

Seanie280672 said:
post your fastboot getvar all please without imei and serial number please.
you are right, your unlock code will only work with stock rom.
Click to expand...
Click to collapse
I'm doing an adb backup at the moment, but I'll post that soon. One question I do have though is if I fully restore this device and then unlock the SIM, can I then re S-off+root and restore the adb backup and maintain my sim unlock? I backed up everything (apk shared system, etc).

Dr3x1 said:
I'm doing an adb backup at the moment, but I'll post that soon. One question I do have though is if I fully restore this device and then unlock the SIM, can I then re S-off+root and restore the adb backup and maintain my sim unlock? I backed up everything (apk shared system, etc).
Click to expand...
Click to collapse
are you s-off ? when you restore stock rom, simply unlock your phone with the code you have and then the easiest thing for you to do after that is just convert your phone to a full T_Mo phone using the RUU, you will not loose s-off at all, no need to re-s-off, after that just flash a custom recovery, root and copy all your stuff back.

Seanie280672 said:
are you s-off ? when you restore stock rom, simply unlock your phone and then the easiest thing for you to do after that is just convert your phone to a full T_Mo phone using the RUU, you will not loose s-off at all, no need to re-s-off, after that just flash a custom recovery, root and copy all your stuff back.
Click to expand...
Click to collapse
Yea I'm S-Off. That's good to know. Now my phone isn't getting recognized by windows/adb while in the bootloader though. Yet another problem I have to figure out. I'll get back to you when it's working again. I've had no end to driver issues today. :-/

Dr3x1 said:
Yea I'm S-Off. That's good to know. Now my phone isn't getting recognized by windows/adb while in the bootloader though. Yet another problem I have to figure out. I'll get back to you when it's working again. I've had no end to driver issues today. :-/
Click to expand...
Click to collapse
if you have Windows 8 or 8.1 with HBOOT 1.44 it wont work, you will need to use windows 7, XP or a bootable Linux distro.

... -_- FML. Yea I'm using Windows 8.1. I thought I'd waited long enough to let the OS mature and that I wouldn't have any issues so I just upgraded recently. Will a VM using Oracle Virtualbox work fine?

Dr3x1 said:
... -_- FML. Yea I'm using Windows 8.1. I thought I'd waited long enough to let the OS mature and that I wouldn't have any issues so I just upgraded recently. Will a VM using Oracle Virtualbox work fine?
Click to expand...
Click to collapse
Yeah windows 8 stucks, windows 10 stucks even more, the only 2 good thing about either of those OS's is the boot speeds, yeah Virtualbox should work.

This is frustrating. I've been working on this for hours. I can't get adb on ubuntu to recognize my device either. It's probably more an issue with virtualbox and it sharing the USB device than anything. Can anyone recommend a simple linux distro for this purpose?

Ok so for the time being my phone is a brick, but I don't think it's unrecoverable. I'm now able to communicate with my device properly even on windows 8.1. Although everything I've done so far was on a friend's linux laptop since my VM wasn't working (I didn't want to make a bootable CD and I don't have any USB flash drives lying around). I attempted to flash what I thought was the correct stock RUU zip but I must have done something wrong. Here is the information you requested:
sudo fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: <snip>
(bootloader) imei: <snip>
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3919mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
At the moment I'm sitting on the HTC logo with 4 triangles in the corner. AKA: A brick.
I can still communicate with it via the command line with fastboot. When I unplug the device I get the white bootloader screen, but the only option is: RUU. Also I appear to be on fastboot 1.55 now so I must have flashed the wrong thing.

Dr3x1 said:
Ok so for the time being my phone is a brick, but I don't think it's unrecoverable. I'm now able to communicate with my device properly even on windows 8.1. Although everything I've done so far was on a friend's linux laptop since my VM wasn't working (I didn't want to make a bootable CD and I don't have any USB flash drives lying around). I attempted to flash what I thought was the correct stock RUU zip but I must have done something wrong. Here is the information you requested:
sudo fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: <snip>
(bootloader) imei: <snip>
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3919mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
At the moment I'm sitting on the HTC logo with 4 triangles in the corner. AKA: A brick.
I can still communicate with it via the command line with fastboot. When I unplug the device I get the white bootloader screen, but the only option is: RUU. Also I appear to be on fastboot 1.55 now so I must have flashed the wrong thing.
Click to expand...
Click to collapse
which RUU did you flash ? link please

@Seanie280672 http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/

Dr3x1 said:
@Seanie280672 http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
Click to expand...
Click to collapse
try this one instead, im not so sure the one you flashed contained the firmware, this one will be official stock: http://androidruu.com/getdownload.ph...5_signed_2.exe
I thought you were on HBOOT 1.44? which is why windows 8 couldnt see your phone, what else did you flash to get to 1.55 ?

Seanie280672 said:
try this one instead, im not so sure the one you flashed contained the firmware, this one will be official stock: http://androidruu.com/getdownload.p...13_10.38j.1157.04_release_334235_signed_2.exe
Also, I thought you were on HBOOT 1.44? which is why windows 8 couldnt see your phone, what else did you flash to get to 1.55 ?
Click to expand...
Click to collapse
I was on Hboot 1.44. I could use adb when the phone was on, but I couldn't use fastboot commands when the phone was in the bootloader. As to why I'm on 1.55 now, It must have been included in the zip I flashed. I wasn't on 1.55 before. Now that I am I'm able to use fastboot commands from my windows machine though.
I don't currently have access to a linux machine so will the exe you linked keep me on Hboot 1.55? I don't want to not be able to talk to my phone again on windows if I can avoid it.
Edit: http://www.htc1guru.com/dld/ruu_m7_...13_10-33-1150-01_release_318450_signed_2-exe/
This RUU is the one recommended by the guide I was following (I have the same device as the example device used in the guide). I didn't use it because it's an exe and I was on a linux machine at the time. I could try using that one, but I know it contains HBOOT 1.44.

Dr3x1 said:
I was on Hboot 1.44. I could use adb when the phone was on, but I couldn't use fastboot commands when the phone was in the bootloader. As to why I'm on 1.55 now, It must have been included in the zip I flashed. I wasn't on 1.55 before. Now that I am I'm able to use fastboot commands from my windows machine though.
I don't currently have access to a linux machine so will the exe you linked keep me on Hboot 1.55? I don't want to not be able to talk to my phone again on windows if I can avoid it.
Click to expand...
Click to collapse
yup if that RUU works, then yes you will still beable to use windows 8, that file will come with 1.54 or 1.55, failing that you can flash this firmware first using fastboot: https://www.androidfilehost.com/?fid=23329332407574042
dont forget to flash twice
and then this matching RUU: https://www.androidfilehost.com/?fid=95916177934536694
the 4 red triangles basically mean you have a bad firmware, or wrong firmware, or some sort of conflict going on between rom and firmware at the moment, which makes sense to me as im pretty sure 1.26.502 should come with HBOOT 1.44 not 1.55.
@clsA is the best man for AT&T products, maybe he can confirm the above.
---------- Post added at 11:02 PM ---------- Previous post was at 11:00 PM ----------
Dr3x1 said:
Edit: http://www.htc1guru.com/dld/ruu_m7_...13_10-33-1150-01_release_318450_signed_2-exe/
This RUU is the one recommended by the guide I was following (I have the same device as the example device used in the guide). I didn't use it because it's an exe and I was on a linux machine at the time. I could try using that one, but I know it contains HBOOT 1.44.
Click to expand...
Click to collapse
see the difference there is that one is signed, making it official.

Right, thanks. I'll do that and get back to you.

Great Success!
The phone booted, greeting me with that ugly ATT logo and music I'd hopped to never hear again lol. The sim unlock code took so now I should flash a Tmobile RUU then?
Also I am still on HBoot 1.55 so that's good, I guess.
Edit: It seems I have no cellular network connection with TMobile right now. Yet more things for me to figure out. >_< Maybe if I'm lucky flashing a Tmobile RUU will fix that too. Any recommendations on which one to use?
Edit 2: I just needed to update the APN settings. I knew that of course I'm just tired because I"ve been working on this for too long. I would still like a suggestion on whether or not I should bother flashing another RUU. My end goal is to be rooted using a CM12 nightly like I was doing before. Should I change my CID, flash a stock Tmobile RUU and then Cyanogen mod? I also appear to have lost root, but I expected that.

Update:
http://www.htc1guru.com/dld/ruu_m7_...3_10-38m-1157-04_release_336982_signed_2-exe/
I'm guessing this is the right one. I've updated my CID and MID for Tmobile and re-rooted. Do I really need to flash that RUU now? I can just safely go back to Cyanogen Mod at this point right?

[Q] All folders deleted and I cant access the phone's storage through usb??

So... Sorry if the title is a little misleading, but here goes... Android 5.0.2 and Maximus 50.0.0, no custom kernels or any mods... I gave the phone to a friend and he basically did a factory reset (even tho he really didnt need to...) and it deleted all the apps and stuff, but there was some files under Other in Storage that didnt get deleted, so he had the bright idea to get into recovery (twrp) and do a full wipe (internal, data, system, etc...). So when the phone booted, it gave a SystemUI force close and an Package Access (or something similar) force close too, and there arent any folders at all when you open an app such as androzip or file explorer... Also, when you connect the phone to the pc, it recognizes the phone but theres no "Phone" after I open Computer > HTC One (it used to display a folder with the image of a storage device, like a pendrive, named Phone and under it, it said how much storage space was available... You know, like any other phone, I'm just mentioning it to be as clear and specific as possible). So, being as there is nothing there to open to access all the folders (that also dont exist cause they were deleted), I have no way to copy the rom and flash it again... I tried to sideload it through twrp, nothing... I tried to manually create folders, nothing... I tried the latest RUU and the one that came just before it, nothing on either, they eventually just give an error... So, I'm pretty much stuck with the phone giving systemui and package acces force closes and unable to transfer anything to it... Any thoughts on how to get it back to normal??

Luisit0 said:
So... Sorry if the title is a little misleading, but here goes... Android 5.0.2 and Maximus 50.0.0, no custom kernels or any mods... I gave the phone to a friend and he basically did a factory reset (even tho he really didnt need to...) and it deleted all the apps and stuff, but there was some files under Other in Storage that didnt get deleted, so he had the bright idea to get into recovery (twrp) and do a full wipe (internal, data, system, etc...). So when the phone booted, it gave a SystemUI force close and an Package Access (or something similar) force close too, and there arent any folders at all when you open an app such as androzip or file explorer...
Click to expand...
Click to collapse
It doesn't make sense already.... How can a phone boot in the OS and have a SystemUI force close after wiping the system partition? There is no more system installed on the phone after wiping /system....The phone shouldn't be able to boot at all....Maybe he didn't correctly explained you what he did...
Also, when you connect the phone to the pc, it recognizes the phone but theres no "Phone" after I open Computer > HTC One (it used to display a folder with the image of a storage device, like a pendrive, named Phone and under it, it said how much storage space was available...
Click to expand...
Click to collapse
Only if the phone is correctly(completely) booted in the OS or booted in a custom recovery with MTP support (like newer twrp versions)
I have no way to copy the rom and flash it again... I tried to sideload it through twrp, nothing...
Click to expand...
Click to collapse
Need more precision here:
What happened exactly when trying to sideload?
What rom (name + version)?
What is your adb version (you can find the adb version by typing "adb version" in the command window)?
What is your twrp version?
Also need to know your "fastboot getvar all" (don't post your imei/sn)
I tried the latest RUU and the one that came just before it
Click to expand...
Click to collapse
What versions exactly? Ruu.zip or Ruu.exe?
nothing on either, they eventually just give an error...
Click to expand...
Click to collapse
Need to know what the error was or I can't tell you whats wrong
Any thoughts on how to get it back to normal??
Click to expand...
Click to collapse
Yep, but I need you to answer my questions first :good:

alray said:
It doesn't make sense already.... How can a phone boot in the OS and have a SystemUI force close after wiping the system partition? There is no more system installed on the phone after wiping /system....The phone shouldn't be able to boot at all....Maybe he didn't correctly explained you what he did...
Only if the phone is correctly(completely) booted in the OS or booted in a custom recovery with MTP support (like newer twrp versions)
Need more precision here:
What happened exactly when trying to sideload?
What rom (name + version)?
What is your adb version (you can find the adb version by typing "adb version" in the command window)?
What is your twrp version?
Also need to know your "fastboot getvar all" (don't post your imei/sn)
What versions exactly? Ruu.zip or Ruu.exe?
Need to know what the error was or I can't tell you whats wrong
Yep, but I need you to answer my questions first :good:
Click to expand...
Click to collapse
Sorry he didnt wipe system in recovery, I accidentally included it... He wiped data, caches and internal data. The phone does boot up and everything, but like I said, it gives me a systemui force close as soon as it boots into the home screen, the statusbar is gone aswell as the background, recent apps etc. so systemui is in fact not working, and a few seconds later comes up the package access force close. And as far as sideloading, when i tried to sideload the maximushd 50.0.0 rom it gave me an error saying "error: device not found". I was trying to copy over the same rom it had installed, maximushd 50.0.0 android 5.0.2. My adb version is 1.0.31 and my recovery is twrp 2.7.1.1. The RUU versions I tried where the ones from the RUU thread, the two latest cingular (at&t) ones. The first one was RUU M7 UL K44 SENSE55 MR Cingular US 4.18.502.7 R10 Radio 4T.24.3218.09 10.26.1718.01L Release 356565 Signed 2 (AT&T), but that one stayed at 5% and never continued on. Then I tried the earlier one, RUU M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3 Radio 4A.19.3263.13 10.38j.1157.04 Release 334235 Signed 2, but that one stuck at 3% "Sending" and eventually gave an error saying Error [155] Unknown Error, The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again, and it gave me the option to try and recover but even after recovering it just did the same thing... Finally, here:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-baseband: 4T.33.3218.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-91bb20e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Sorry I didnt give out some of these basic details before, its been a while since I post anything XD so, any thoughts? I appreciate it btw!

Luisit0 said:
Sorry he didnt wipe system in recovery, I accidentally included it... He wiped data, caches and internal data. The phone does boot up and everything, but like I said, it gives me a systemui force close as soon as it boots into the home screen, the statusbar is gone aswell as the background, recent apps etc. so systemui is in fact not working, and a few seconds later comes up the package access force close. And as far as sideloading, when i tried to sideload the maximushd 50.0.0 rom it gave me an error saying "error: device not found". I was trying to copy over the same rom it had installed, maximushd 50.0.0 android 5.0.2. My adb version is 1.0.31 and my recovery is twrp 2.7.1.1. The RUU versions I tried where the ones from the RUU thread, the two latest cingular (at&t) ones. The first one was RUU M7 UL K44 SENSE55 MR Cingular US 4.18.502.7 R10 Radio 4T.24.3218.09 10.26.1718.01L Release 356565 Signed 2 (AT&T), but that one stayed at 5% and never continued on. Then I tried the earlier one, RUU M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3 Radio 4A.19.3263.13 10.38j.1157.04 Release 334235 Signed 2, but that one stuck at 3% "Sending" and eventually gave an error saying Error [155] Unknown Error, The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again, and it gave me the option to try and recover but even after recovering it just did the same thing... Finally, here:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-baseband: 4T.33.3218.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-91bb20e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Sorry I didnt give out some of these basic details before, its been a while since I post anything XD so, any thoughts? I appreciate it btw!
Click to expand...
Click to collapse
Ok, no problem.
Imo what you should do is to flash the latest dev edition ruu not at&t. If you flash the at&t ruu, you'll get the at&t bloatware that comes with it and you'll only be able to install ota update if connected to the a&t network. The dev edition is pretty much the same exact thing except you don't need to be connected to at&t for updates and that it doesn't come with carriers bloatware.
Your phone is on hboot 1.60 which makes me believe it was running the unofficial 7.17.401.1 firmware leaked by LlabToFeR? The ruu you did tried (3.xx.502.x and 4.xx.502.x failed because you need to use a ruu.zip if downgrading (or downgrade the hboot version before using an old ruu.exe).
Since your phone is S-OFF this should be really easy to fix.
Run the 7.17.1540.35 Dev edition RUU posted in this thread :http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
then you should receive one ota update to 7.17.1540.51 which is the update pushed yesterday.

alray said:
Ok, no problem.
Imo what you should do is to flash the latest dev edition ruu not at&t. If you flash the at&t ruu, you'll get the at&t bloatware that comes with it and you'll only be able to install ota update if connected to the a&t network. The dev edition is pretty much the same exact thing except you don't need to be connected to at&t for updates and that it doesn't come with carriers bloatware.
Your phone is on hboot 1.60 which makes me believe it was running the unofficial 7.17.401.1 firmware leaked by LlabToFeR? The ruu you did tried (3.xx.502.x and 4.xx.502.x failed because you need to use a ruu.zip if downgrading (or downgrade the hboot version before using an old ruu.exe).
Since your phone is S-OFF this should be really easy to fix.
Run the 7.17.1540.35 Dev edition RUU posted in this thread :http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
then you should receive one ota update to 7.17.1540.51 which is the update pushed yesterday.
Click to expand...
Click to collapse
I see. I was attempting to use the at&t ruu simply because the phone is an at&t one, but also cause I hadnt seen that thread. Thanks for pointing it out! Also, yes it was the firmware from LlabToFeR the one I flashed, if I do recall correctly. As for the .exe, I had forgot about the difference between it and .zip, its been quite a while since I messed around with the M7. I used to flash the hell out of it before lol. Thanks so much for your time and help, I'm downloading the 7.17.1540.35 ruu now. Hope all goes well! I'll let u know :good:

Luisit0 said:
I see. I was attempting to use the at&t ruu simply because the phone is an at&t one, but also cause I hadnt seen that thread. Thanks for pointing it out! Also, yes it was the firmware from LlabToFeR the one I flashed, if I do recall correctly. As for the .exe, I had forgot about the difference between it and .zip, its been quite a while since I messed around with the M7. I used to flash the hell out of it before lol. Thanks so much for your time and help, I'm downloading the 7.17.1540.35 ruu now. Hope all goes well! I'll let u know :good:
Click to expand...
Click to collapse
Hi I'm having the same problem in my HTC One too. Did the above method solve the problem?