Related
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!
I have had my HTC ONE for about 5 months now and as soon as i got the phone i rooted it and installed Teamwin's recovery program. Today i got a notification that there is a system update (4.4.2). What steps do i need to take for updating this phone considering that its rooted and has Teamwins recovery program?
BlockABoots said:
I have had my HTC ONE for about 5 months now and as soon as i got the phone i rooted it and installed Teamwin's recovery program. Today i got a notification that there is a system update (4.4.2). What steps do i need to take for updating this phone considering that its rooted and has Teamwins recovery program?
Click to expand...
Click to collapse
if you have made no changes to the OS just install the stock recovery for your os version.
Stock recovery's
if your using custom roms you need to RUU back to stock then take the update
find your RUU here >> http://www.androidruu.com/index.php?developer=M7
use fastboot getvar all to find your phones information
Ok have used adb and this if my phones info......
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3************
(bootloader) imei: 354***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3868mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.060s
What stock recovery image do i need to use? from the link you sent me above, recovery 2.24.401.8.img??
Will i lose all the data on my phone installing the stock recovery??
BlockABoots said:
Ok have used adb and this if my phones info......
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3**********
(bootloader) imei: 354**************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3868mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.060s
What stock recovery image do i need to use? from the link you sent me above, recovery 2.24.401.8.img??
Will i lose all the data on my phone installing the stock recovery??
Click to expand...
Click to collapse
Edit your previous post and remove serial no and IMEI
yes that's the recovery you need and no it won't erase your phone
clsA said:
Edit your previous post and remove serial no and IMEI
yes that's the recovery you need and no it won't erase your phone
Click to expand...
Click to collapse
Thanks for the pointer.
So these are the steps i need to do:
1. Download 'recovery 2.24.401.8.img'
2. Rename 'recovery 2.24.401.8.img' to 'recovery.img'
3. Place 'recovery.img' in my adb/fastboot folder (C:\Adb)
4. Open Command Prompt and navigate to your adb folder
5. Type 'adb reboot bootloader' to get into fastboot on the HTC ONE
6. And then flash the recovery img by typing 'fastboot flash recovery recovery.img'
Is the above all correct?
Yep that's it
Sent from my HTC One using Tapatalk
uarbie
clsA said:
Yep that's it
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
OK thanks, it doesnt matter than i have S-ON then?
After i type, 'fastboot flash recovery recovery.img'
its says, 'waiting for device' and just sits there, any ideas why this happens?
probably drivers.
check device manager and make sure you have a proper driver loaded
fastboot devices should show your device.
If your on windows 8/8.1 it has trouble with fastboot on older hboot versions. ADB works fine but fastboot doesn't work. I think newer hboot's resolve this so it will work after the update.
Might need to just use a win7 pc or VM to flash stock recovery.
BlockABoots said:
OK thanks, it doesnt matter than i have S-ON then?
After i type, 'fastboot flash recovery recovery.img'
its says, 'waiting for device' and just sits there, any ideas why this happens?
Click to expand...
Click to collapse
ipfreelytech said:
probably drivers.
check device manager and make sure you have a proper driver loaded
fastboot devices should show your device.
If your on windows 8/8.1 it has trouble with fastboot on older hboot versions. ADB works fine but fastboot doesn't work. I think newer hboot's resolve this so it will work after the update.
Might need to just use a win7 pc or VM to flash stock recovery.
Click to expand...
Click to collapse
Ah yeah i am on Windows 8.1. I'll have to use my laptop then. What drivers do i need to be downloading?
Also can 4.4.2 be rooted yet?
I use the universal naked driver pack and usually just choose google nexus bootloader interface for the driver.
Sure, you root it the same as anything else: unlock bootloader, flash cwm/twrp recovery, flash SuperSU.zip
BlockABoots said:
Ah yeah i am on Windows 8.1. I'll have to use my laptop then. What drivers do i need to be downloading?
Also can 4.4.2 be rooted yet?
Click to expand...
Click to collapse
ipfreelytech said:
probably drivers.
check device manager and make sure you have a proper driver loaded
fastboot devices should show your device.
If your on windows 8/8.1 it has trouble with fastboot on older hboot versions. ADB works fine but fastboot doesn't work. I think newer hboot's resolve this so it will work after the update.
Might need to just use a win7 pc or VM to flash stock recovery.
Click to expand...
Click to collapse
ipfreelytech said:
I use the universal naked driver pack and usually just choose google nexus bootloader interface for the driver.
Sure, you root it the same as anything else: unlock bootloader, flash cwm/twrp recovery, flash SuperSU.zip
Click to expand...
Click to collapse
Ok have managed to flash the stock recovery back to the phone, and have update to 4.4.2. But when i turned the phone back on i had to go through all the setup process and now all my contact and text messages and apps have gone!!. I though i wasnt going to lose all my data?
Your bootloader was already unlocked? or was it locked and you just unlocked it? When you perform a bootloader unlock it does wipe the data as a "safety measure".
BlockABoots said:
Ok have managed to flash the stock recovery back to the phone, and have update to 4.4.2. But when i turned the phone back on i had to go through all the setup process and now all my contact and text messages and apps have gone!!. I though i wasnt going to lose all my data?
Click to expand...
Click to collapse
ipfreelytech said:
Your bootloader was already unlocked? or was it locked and you just unlocked it? When you perform a bootloader unlock it does wipe the data as a "safety measure".
Click to expand...
Click to collapse
It should of already been unlocked, as it was rooted and had TWRP install previously
So theres no way for me to get this stuff back then, pictures, messages, contacts etc?
Um, there's some missing information here.
Short answer, if you in fact "unlocked" the phone recently, you wiped all personal data and there is absolutely no way to go back.
There are other ways data can get erased however.
As you pointed out, the phone was likely unlocked previously. Not sure how it would have become relocked forcing you to unlock again, which you don't seem to remember doing anyway.
Also you didn't originally say you lost your pictures. Did you or didn't you? Losing texts and contacts is normal when flashing a ROM. There are backup apps for texts and most people keep their contacts in the cloud do you normally just resync and you're done.
But pictures is something else. Sounds like someone did a factory reset and/or formatted the entire /data partition in recovery.
Normally most recoveries know that when you "format" data, you are really just selectively erasing everything in /data *except* /data/media. You don't usually do an actual format. The stock recovery does not make this distinction, and even custom recoveries often have an advanced features that lets you truly format all of /data. So you might have nuked your pictures in recovery somehow, no unlocking necessary.
You need to go into more detail.
But if you are saying your pictures are gone, they're probably totally gone.
One last possibility, the version-main you posted suggests you may have been using android 4.2 originally.
But I suppose it's possible the original ROM you were using was actually 4.1. Maybe your stuff was at the top level of /data/media and never got moved to /data/media/0
This surprised quite a few people during the transition from Android 4.1 to 4.2
So *if* you didn't unlock *and* didn't totally format everything *and* your old ROM was 4.1, well.. get a file browser and have a look around. Maybe you got lucky.
Sent from my HTC One using xda app-developers app
Well before i flashed the recovery image bootloader had 'Tampered' and 'unlocked' listed at the top of the sceeen, just like it does now so im not really sure what happened. But as soon as i flashed the 'recovery 2.24.401.8.img' back onto my phone and then downloaded the 4.4.2 system update and installed it, when the phone restarted again it was like it was back to factory default in that i had to go through the whole setup screens!, so not sure whats happened.
But on closer inspection even though i have downloaded and installed system update 4.4.2, if i go in settings>about>Software information> it says im on Android version 4.3 and software number 3.62.401.1, isnt this wrong as ive updated to 4.4.2???
You have two separate issues here. You lost your data and you're not running 4.4.2
Apparently you're not worried about your data.
To get 4.4.2 you either need to a) get to a place that is so "stock" that OTA's will take you the rest of the way or b) manually flash a 4.4.2 ROM. The b) option usually requires S-OFF and a suitably recent recovery compatible with KitKat.
If you are already S-OFF of course b) is way simpler. But you're not. In fact you have HBOOT 1.56 which can make S-OFF less certain. If you can get S-OFF that's the way I would go. I personally never screw around chasing OTA's.
You may be in an awkward place right now.
Time for someone with more patience than me to get involved I guess.
Sent from my HTC One using xda app-developers app
No please don't get me wrong I am certainly worried about my lost data, especially the pictures, but from what you said I there's no real way to recover them, is that correct or is there a way at all?
Probably gone, but I would still use adb shell or a file explorer app to look in
/data/media
Your most recent personal data (the stuff you made in the last day or two, not the lost files you are looking for) will be in
/data/media/0
You're checking to see if there is useful stuff *outside* the " 0 " folder.
Don't delete anything unfamiliar (for instance if you see clockworkmod, leave that alone -it's nandroid backups). Just look for orphaned folders full of personal stuff like "DCIM" or " Music" or whatever.
Sent from my HTC One using xda app-developers app
NxNW said:
Probably gone, but I would still use adb shell or a file explorer app to look in
/data/media
Your most recent personal data (the stuff you made in the last day or two, not the lost files you are looking for) will be in
/data/media/0
You're checking to see if there is useful stuff *outside* the " 0 " folder.
Don't delete anything unfamiliar (for instance if you see clockworkmod, leave that alone -it's nandroid backups). Just look for orphaned folders full of personal stuff like "DCIM" or " Music" or whatever.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Sadly there is nothing in /data/media there are 3 folder, 0, legacy. obb and a file .htc_layout_version none hold any of my old photos . I have even tried the program, Wondershare Dr.Fone and that doesnt find any of my old photos either...so i guess there lost for ever, bugger.
I guess i need to get this phone back to stock and then try the update and see if it takes this time?, so ill need to remove the root, TWRP recovery and SuperSU?
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.
Hey there, I flashed a ROM and apparently it messed up my M7 Sprint I can't call or receive SMS, also I can't install apps even from OTG cable, I think this ROM is broken. Not sure if this is a hardware or software issue, I hope it's the latter. I can use the camera, WI-FI and play media files.
I have HBOOT 1.44 and my bootloader says TAMPERED and UNLOCKED.
How can I get back to stock from this stage? I'm super noob every bit of help will be appreciated
Dani84 said:
Hey there, I flashed a ROM and apparently it messed up my M7 Sprint I can't call or receive SMS, also I can't install apps even from OTG cable, I think this ROM is broken. Not sure if this is a hardware or software issue, I hope it's the latter. I can use the camera, WI-FI and play media files.
I have HBOOT 1.44 and my bootloader says TAMPERED and UNLOCKED.
How can I get back to stock from this stage? I'm super noob every bit of help will be appreciated
Click to expand...
Click to collapse
Ok so sounds like your having a rough time. I will try my best for you .
First of all some more information please. Boot you phone into the bootloader and connect fastbootusb. Then in your Fastboot command line type.
Code:
fastboot getvar all
And post the output here. Please edit out your serial no. And imei no.
what Rom did you flash and which recovery are you using? Did you clean flash i.e perform a full wipe before flashing, or Dirty flash i.e flash the Rom without wiping anything?
If the phones booting it can't of done anything to serious so let's hope this is an easy fix
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
uhm nothing, seems adb/fastboot is not working.
Im using Ubuntu 14.04... 64 bit.
p.s. in Windows 8.1 i connected it through this (Nocturnal ADB tool):
http://forum.xda-developers.com/showthread.php?t=2646453
I open the CMD and type adb devices and there it is HT35xxxxxxx. But when I type fastboot getvar all, it says waiting for device and is stuck there for 5+ minutes and nothing.
Dani84 said:
uhm nothing, seems adb/fastboot is not working.
Im using Ubuntu 14.04... 64 bit.
p.s. in Windows 8.1 i connected it through this (Nocturnal ADB tool):
http://forum.xda-developers.com/showthread.php?t=2646453
I open the CMD and type adb devices and there it is HT35xxxxxxx. But when I type fastboot getvar all, it says waiting for device and is stuck there for 5+ minutes and nothing.
Click to expand...
Click to collapse
Ah hA a Linux user nice to use Fastboot in linux all command must start sudo. So
sudo fastboot devices
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
Danny201281 said:
Ah hA a Linux user nice to use Fastboot in linux all command must start sudo. So
sudo fastboot devices
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
Click to expand...
Click to collapse
Oh true!!! :victory:
[email protected]:~$ sudo fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3xxxxxx
(bootloader) imei: 35xxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4278mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 5.042s
Dani84 said:
Oh true!!! :victory:
[email protected]:~$ sudo fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3xxxxxx
(bootloader) imei: 35xxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4278mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 5.042s
Click to expand...
Click to collapse
Your phone does not appear to be a Sprint m7. As they have product I'd m7wls
Yours has m7_ul so it is international version. If you flashed a Sprint Rom that would certainly explain your problem. Luckily your s-on so shouldn't have done to much damage.
What Rom did you flash and which recovery are you using?
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
my recovery is TWRP 2.7.1.1
and the ROM is LiquidSmooth but it is horrible LOL and I can't flash new ROMs apparently.
how do I know if my ONE is sprint or at&t? I always assumed it was sprint as Im from Spain.
Dani84 said:
my recovery is TWRP 2.7.1.1
and the ROM is LiquidSmooth but it is horrible LOL and I can't flash new ROMs apparently.
how do I know if my ONE is sprint or at&t? I always assumed it was sprint as Im from Spain.
Click to expand...
Click to collapse
your phone is not Sprint or AT&T
you have
product: m7_ul <- this is a GSM with LTE
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP304 <- this says it's from Vodafone
So your looking for a RUU with VODAP in the CID ... all I see are some OTA files seems theirs no RUU
Dani84 said:
my recovery is TWRP 2.7.1.1
and the ROM is LiquidSmooth but it is horrible LOL and I can't flash new ROMs apparently.
how do I know if my ONE is sprint or at&t? I always assumed it was sprint as Im from Spain.
Click to expand...
Click to collapse
Your firmware also appears to be very old there is a reset zip i think will do the trick.
http://www.htc1guru.com/dld/guru_reset_m7_2-24-161-1-zip/
This reset zip should return you to stock so you take ota updates, then you can update to official kitkat Rom and firmware.
Reroot the phone and install a international based Rom. Stay away from TWRP 2.7.1.1 though you'll notice in your getvar version main is blank. That's caused by TWRP 2.7.1.1. Stick with TWRP 2.6.3.3 to avoid this happening again.
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
Danny201281 said:
Your firmware also appears to be very old there is a reset zip i think will do the trick.
Link to follow
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
Click to expand...
Click to collapse
k thanks so what to do? what link?
Dani84 said:
k thanks so what to do? what link?
Click to expand...
Click to collapse
See my edited post above
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
Danny201281 said:
See my edited post above
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
Click to expand...
Click to collapse
downloading time = 2hours LOL, no problem I have time.
so I can flash that even when bootloader says TAMPERED and UNLOCKED? i want to be sure im not bricking my phone haha.
Dani84 said:
downloading time = 2hours LOL, no problem I have time.
so I can flash that even when bootloader says TAMPERED and UNLOCKED? i want to be sure im not bricking my phone haha.
Click to expand...
Click to collapse
Yes just flashes like a normal Rom from TWRP recovery, it will replace your custom recovery with stock and your Rom.
I think your firmware is probably still older than this reset.zip though. I'm not sure if that will cause a problem.
So you could also download this OTA extract the firmware from it and flash it manually to bring your firmware in line with the reset.zip
http://www.htc1guru.com/dld/ota_m7_..._p_release_325133_signedlqk8p6c09r7kmir2-zip/
That will require relocking the bootloader though but you can always unlock again after.
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
Dani84 said:
downloading time = 2hours LOL, no problem I have time.
so I can flash that even when bootloader says TAMPERED and UNLOCKED? i want to be sure im not bricking my phone haha.
Click to expand...
Click to collapse
yeah the Guru_Reset requires unlocked bootloader and TWRP 2.6.3.3 custom recovery.
To take the over the air updates it's Important that you choose to install
stock recovery and say no to root in the guru reset Aroma installer.
Good luck !!
Thanks guys, both of you have been very kind and helpful I will try this and tell you tomorrow (its night in Spain).
@clsA do you know about the firmware will he need to update it to match the reset or will it still update ok as is ?
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
Danny201281 said:
@clsA do you know about the firmware will he need to update it to match the reset or will it still update ok as is ?
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
Click to expand...
Click to collapse
The firmware may indeed need updated but I'm not positive
Dani84 said:
Thanks guys, both of you have been very kind and helpful I will try this and tell you tomorrow (its night in Spain).
Click to expand...
Click to collapse
clsA said:
The firmware may indeed need updated but I'm not positive
Click to expand...
Click to collapse
Probably best to do it then in that case, better safe than sorry thanks.
Ok so hopefully this will tell you everything you need.
Download the ota file as well. Then open it on your pc and extract the firmware.zip from it and place it in your Fastboot folder. Then follow this small guide I put together.
Ok so the plan is to upgrade your software to complete Stock 2.24.161.1, Rom, recovery and firmware will all be on the same os version and unmolested stock condition. After which you will be able to update you phone with official ota updates.
Prepare the files, your pc and phone for the procedure. Rename the 2.24.161.1.zip to firmware.zip and place it in your Fastboot folder on your pc. Connect your phone to mass storage with usb and copy the reset.zip to your internal storage/sdcard.
Ok let's get started. Reboot your phone into recovery. And flash the reset.zip just like installing a custom Rom. Select install and choose the reset.zip. Once it's done your Rom, recovery and radio will be back to stock. (if you choose to install the radio, it's optional at this stage as it will be done with the firmware anyway.
Now we need to upgrade the firmware since the OTA update will expect to find version 2.24.161.1 but your firmware is older than that so the OTA may fail to install.
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
Code:
fastboot oem lock
Code:
fastboot reboot-bootloader
Code:
fastboot oem rebootRUU
<--- case sensitive.
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and this time it 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 completed its output the flash is done.
Code:
fastboot reboot-bootloader
You should now see your new firmware version 2.24.161.1 in the bootloader. And that's it
Reboot the phone and complete the Rom setup. You should start getting notifications for OTA updates almost immediately. If not just go to settings>about and check for updates to force it. Take all the OTA's up to the latest and you're done
Completely stock software. If you decide to reroot make a nandroid of the Stock Rom before you root it. And copy it to your pc. This way you can return to stock easily for future OTA updates
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
It worked!!!!!!
Now im running my stock HTC One again. Such a lame Vodafone ROM with tons of bloatware but at least the phone is alive and Im happy with that.
tbh Im now scared of flashing a new ROM, i would like the android revolution or one of those flashy roms but I think im gonna wait some days before making a decission lol. Thanks everyone
Dani84 said:
It worked!!!!!!
Now im running my stock HTC One again. Such a lame Vodafone ROM with tons of bloatware but at least the phone is alive and Im happy with that.
tbh Im now scared of flashing a new ROM, i would like the android revolution or one of those flashy roms but I think im gonna wait some days before making a decission lol. Thanks everyone
Click to expand...
Click to collapse
Well done m8, glad you got it sorted. You shouldn't be scared of flashing a new Rom though. The only thing that went wrong last time was you flashed a Rom for a different version of the M7.
As long as you stick with m7_ul roms you'll be fine but it's understandable you would want to take some time to process what happened. It's never fun thinking you bricked an expensive device such as the HTC one.
If you ever decide you want to try a Rom feel free to pm me for some guidance. For now relax and enjoy your working phone :highfive:
---------- Post added at 05:22 PM ---------- Previous post was at 05:01 PM ----------
@Dani84 Hi m8 just seen your PM. Yeah ARHD is a good place to start, it's quite close to stock but with xposed support and sense 6 toolbox.
Very smooth reliable Rom with no major bugs that I know of. I've been using ARHD since version 43 and I just love it. Version 80.0 is on the Horizon (Android 4.4.3).
I think I warned you already about twrp but just incase make sure to flash twrp 2.6.3.3 to preserve your os information.
Download the Rom and drop it on your sd card. Reboot to recovery and flash the Rom from the install menu in twrp. Make sure to do a full data wipe in the aroma installer as your changing from stock to custom Rom.
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
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?