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!
Related
I'm the next one in line with the same question, but no other answers helped me yet. What I did wrong was adb sideloading the OTA file using CWM recovery. That part I understand, so completely my own fault.
However, the update is still on the SD card and I tried to load stock recovery via fastboot so that I can install OTA from the SD card. What I get is something I find a lot of others have as well; the recovery fails to mount sd card 5 times. When I try to "Apply from SD card" I get an error "Check cid failed! --invalid operation--" and the phone reboots. The same error happens to users in many places, an example here: androidcentral . com/how-manually-update-your-google-play-edition-htc-one-android-44-kitkat
I think I can recover the phone with instructions (I can't post URLs yet) that will install a different recovery and uses adb sideload. But it also erases the sdcard which I try to avoid.
So, Is there anyone who can advice me what to do? If it cannot be avoided that my sdcard will be wiped; so be it. But I will manage doing that, I'm looking for an alternative at the moment. I suspect that if I find the correct recovery version that it will "mount" the "sdcard" (which I think is an emulation because the HTC One has no sdcard??) will also allow me to recover my phone with sdcard intact. But I find it difficult to find the correct recovery.img. I've tried two versions *can't find numbers back right now, will post if needed*.
HTC One, converted into GPe (so tampered and unlocked)
HBOOT 1.44
ruud.walraven said:
I'm the next one in line with the same question, but no other answers helped me yet. What I did wrong was adb sideloading the OTA file using CWM recovery. That part I understand, so completely my own fault.
However, the update is still on the SD card and I tried to load stock recovery via fastboot so that I can install OTA from the SD card. What I get is something I find a lot of others have as well; the recovery fails to mount sd card 5 times. When I try to "Apply from SD card" I get an error "Check cid failed! --invalid operation--" and the phone reboots. The same error happens to users in many places, an example here: androidcentral . com/how-manually-update-your-google-play-edition-htc-one-android-44-kitkat
...
HTC One, converted into GPe (so tampered and unlocked)
HBOOT 1.44
Click to expand...
Click to collapse
Ruud, I don't know if I completely understand your story, but you are able to get into stock recovery right? If so, do not choose 'Apply from SD card', but 'Apply from phone'. I got the same error messages (fails to mount SD card...), but if the OTA file is on your phone, you have to choose phone storage.
mbroeders said:
Ruud, I don't know if I completely understand your story, but you are able to get into stock recovery right? If so, do not choose 'Apply from SD card', but 'Apply from phone'. I got the same error messages (fails to mount SD card...), but if the OTA file is on your phone, you have to choose phone storage.
Click to expand...
Click to collapse
I should have mentioned that the other options (apply from phone and apply from cache) don't work either. One thing I am unsure about is if this is indeed the stock recovery.img I put back on. Is there a single recovery.img for HTC One, or a list where I can find which one came standard so I can put it back. My suspicion is that that recovery will work, although the guy I bought the phone from may have installed recovery/images that may have reformatted everything in a way that stock won't work any longer...
I noticed most people need to post fastboot getvars all. Makes sense to figure out what software I need so here it is:
(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.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 1234567890AB
(bootloader) imei: 123456789000000
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
ruud.walraven said:
I noticed most people need to post fastboot getvars all. Makes sense to figure out what software I need so here it is:
(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.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 1234567890AB
(bootloader) imei: 123456789000000
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
Are you sure this is the GPe version? I get a feeling that you have the Sense version and then it won't work of course. (sorry if I'm wrong)
Sent from my HTC One using XDA Premium 4 mobile app
I've tried a whole range of things that didn't help. Don't want to preserve the sd card any longer.
Flashed recovery versions: 1.29.401.12, 2.24.401.8, 3.07.1700.1 and 3.58.1700.5.
Neither version was able to reinstall from sdcard. But I found out later that I may have done *something* to the sdcard (see CWM below)
Next I flashed CWM to try flashing a nandroid. However during the process I couldn't browse my sdcard anymore. Before flashing above recoveries I had CWM and then I could see all files. May have done something wrong.
After trying the mentioned nandroid a few times I realized that I am S-ON.
I have been trying to get S-OFF for the last few hours because I found a file I want to use on my phone (See htc1guru . com/2013/11/android-4-4-kit-kat-google-edition-3-58-1700-5-ruu-ota-files/). I've looked at Moonshine, but my phone is not in the list of supported rom versions (1.29.401.12). I tried Revone, but get error = 1.
So now I'm not sure what to do next!!
mbroeders said:
Are you sure this is the GPe version? I get a feeling that you have the Sense version and then it won't work of course. (sorry if I'm wrong)
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am absolutely sure I have a Sense version originally. I bought it from someone who unlocked the bootloader and replaced the sense firmware with GPe. OTA was working because I OTA-ed to 4.3. I've contacted him this morning, but he says to have no idea what files he used.
you bought it from an idiot.
you can't properly convert to GPE with s-on. That's why your hboot, mainver and cid are all wrong for a GPE conversion.
I assume you're boot-loader unlocked? flash cwm or TWRP. Then restore this nandroid: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-htc__102-1-29-401-12-2013-05-16-zip/
after restoring that nandroid try to s-off with revone and or rumrunner.
Revone: http://forum.xda-developers.com/showthread.php?t=2314582
Rumrunner: http://forum.xda-developers.com/showthread.php?t=2488772
once your s-off you can properly convert your phone to GPE. The problem wasn't just that you flashed it with a custom recovery but that the phone was never in a proper state to receive OTA for GPE!
use the RUU from here once your s-off to convert to GPE 4.4 : http://forum.xda-developers.com/showthread.php?t=2358781
you'll also want to go supercid with fastboot oem writecid 11111111
ruud.walraven said:
I am absolutely sure I have a Sense version originally. I bought it from someone who unlocked the bootloader and replaced the sense firmware with GPe. OTA was working because I OTA-ed to 4.3. I've contacted him this morning, but he says to have no idea what files he used.
Click to expand...
Click to collapse
I'm downloading all required files right now. In the meantime looking into everything to make sure to not further brick it once S-OFF. Tricky business!
ipfreelytech said:
you'll also want to go supercid with fastboot oem writecid 11111111
Click to expand...
Click to collapse
There's one question I found: according to this thread SuperCid 11111111 doesn't get OTA and the best bet for me would be HTC__001. Is that correct, or can I also choose from HTC_001 or GOOGL001? (the latter I remember reading is supposed to be good too). In any case ... I suppose I can best follow your instructions and I can change the cid to whatever needed afterwards anyway.
edit: It took 1.5 hours to download the nandroid, but something must have gone wrong because the file cannot be opened by winzip nor 7z. After the failed opening of the file I've md5-ed the entire zip file and it doesn't match the checksum on the download link. So started download again...
I have a problem; the download stops at different points, never completing. Must be a problem in the connection or at htc1guru. Is there an alternative file/download/mirror I can use as well? Have searched google for the same file with no results.
I was finally able to download the file through FF. Every time the download failed I started again, but paused and replaced the .part file with the failed download. When you resume FF detects the last bit and resumes from there. Best part was that I got my Chrome 900+MB download and used that as .part file. So I could resume nearly finished. Ran the checksum to be sure nothing funny had happened because of my tinkering. To quote Borat: great success.
However, after restoring the nandroid through CWM I tried both Revone and Rumrunner. Revone fails error = 1 and Rumrunner assumes I start from my homescreen (which I can't). A bit unwise, but I tried anyway from both fastboot and CWM but in neither case will Rumrunner continue. It claims there is no ADB connection (even though the phone shows up in adb devices).
So I am stuck for now. Still looking at as many posts about S-OFF as I can to see if I find some vital piece of inof I missed or something I can still try. But for now I'd like some idea's how to achieve S-OFF..
What is the date in your hboot version? If after June, then revone won't work. Have you tried moonshine?
SaHiLzZ said:
What is the date in your hboot version? If after June, then revone won't work. Have you tried moonshine?
Click to expand...
Click to collapse
hboot has a date? Hboot is 1.44 and bootloader start screen says apr 12 2013, is that what you mean?
My version (1.29.401.12) is not supported by moonshine for as far as I can tell.
I also notice now that fastboot getvars bootmode says: fastboot. Shouldn't this be disabled for revone and/or rumrunner?
ruud.walraven said:
...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 1234567890AB
(bootloader) imei: 123456789000000
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
...
Click to expand...
Click to collapse
Just a question: In a sense I can't have messed anything up that bad because I'm S-ON. So if I would install the 4.3 release that was on the device before I sideloaded the 4.4 OTA through CWM, wouldn't it just work because all things point to the correct places? Since I broke it with adb sideloading, I could restore the device probably just as well, right?
In any case; I still would want to S-OFF my device to go through ipfreelytech's steps and get a functioning 4.4 GPe. But So far I found that Moonshine doesn't support my device and for both rumrunner and revone I need to start from a booted up android homescreen. So all three options don't seem to work. Did I really brick my phone, or is there still hope??
I had same problem on my device. I decided to install CWM instead of TWRM, downloaded RUU 4.2.2 and flashed it. Next I get update to 4.3 and 4,4 later and now everytning works perfect.
ziolooo said:
I had same problem on my device. I decided to install CWM instead of TWRM, downloaded RUU 4.2.2 and flashed it. Next I get update to 4.3 and 4,4 later and now everytning works perfect.
Click to expand...
Click to collapse
Willing to try, but I don't see the RUU file needed on http://forum.xda-developers.com/showthread.php?t=2428276 nor on htc1guru.com. This should be done through fastboot oem rebootRUU, right? If everything works I'm don. if OTA or some functions don't wrok I maybe able to S-OFF and follow previous instructions till the end. And if it doesn't work I'm back to where I am now anyway.
ruud.walraven said:
Willing to try, but I don't see the RUU file needed on http://forum.xda-developers.com/showthread.php?t=2428276 nor on htc1guru.com. This should be done through fastboot oem rebootRUU, right? If everything works I'm don. if OTA or some functions don't wrok I maybe able to S-OFF and follow previous instructions till the end. And if it doesn't work I'm back to where I am now anyway.
Click to expand...
Click to collapse
Here you have good tutorial how to install RUU:
http://htc-one.wonderhowto.com/how-...with-bootloader-recovery-ota-updates-0148068/
Download and flash RUU from this site.
ziolooo said:
Here you have good tutorial how to install RUU:
http://htc-one.wonderhowto.com/how-...with-bootloader-recovery-ota-updates-0148068/
Download and flash RUU from this site.
Click to expand...
Click to collapse
Thanks for the link. That won't work though because I'm still trying to achieve S-OFF which is a prerequisite to follow that guide.
ruud.walraven said:
Thanks for the link. That won't work though because I'm still trying to achieve S-OFF which is a prerequisite to follow that guide.
Click to expand...
Click to collapse
http://htc-one.wonderhowto.com/how-to/set-your-htc-one-s-off-using-moonshine-windows-0147992/
ziolooo said:
http://htc-one.wonderhowto.com/how-to/set-your-htc-one-s-off-using-moonshine-windows-0147992/
Click to expand...
Click to collapse
I already tried that.
ruud.walraven said:
...
In any case; I still would want to S-OFF my device to go through ipfreelytech's steps and get a functioning 4.4 GPe. But So far I found that Moonshine doesn't support my device and for both rumrunner and revone I need to start from a booted up android homescreen. So all three options don't seem to work. Did I really brick my phone, or is there still hope??
Click to expand...
Click to collapse
Hello there everyone, sorry to add another 'bricked' thread to the first page but it seems the more I try to fix my phone on my own, the deeper the hole I'm digging becomes.
About a week ago I installed Cyanogenmod via their installer. It was nice and straightforward but I soon began to miss Sense 5.5 so I set out to return my phone to stock. This was a few days ago and since then I have learned about flashing, rooting, fastboot etc., but I am now stuck where I cannot make it past the Cyanogenmod logo and I have absolutely no idea where to start fixing things. I can't make any progress as I do not have USB debugging mode enabled (nor can I enable it now) and I have no backup other than the automatic backup to Dropbox.
Below is my getvar output. Phone is 'TAMPERED' and 'UNLOCKED'. Oh, the phone is not rooted and was bought in Hong Kong but I use o2 in England. Please let me know If there is any more information I need to include.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.708.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Oops
(bootloader) imei: nothing to see here
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__622
(bootloader) battery-status: good
(bootloader) battery-voltage: 4300mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-14eb688c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Thanks for taking the time to read this, any pointers would be very much appreciated
I'm no expert, but maybe this can help.
Here's what I did with mine when I thought I bricked it. Keep in mind that I had a micro-USB to USB OTG cable. (costs less than $5)
Mine was bootloader unlocked, s-on but with hboot 1.55 or 1.54.
1. install TWRP recovery (openrecovery-twrp-2.6.3.3-m7.img) using fastboot.
2. Boot into TWRP recovery, then using OTG cable, mount a USB flash drive that has a installable zip image of the whole thing. I just used one from here:
http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
I got the "Download stock odexed 4.19.401.8" since I wanted to return it to stock like so I can return it.
I flashed it with that, and it would reboot into stock-like Android. I still had a bootloader from GoogleExperience version, and I accidentally did S-on before fixing these so I was screwed.
Anyways, that's how I got mine back to working state. After that, I couldn't get S-off (hboot 1.54) no matter what even using Rumrunner. Trying to get S-off again, I had to reflash the kernel with some other custom kernel, and then was able to do rumrunner to get s-off again. From that point, everything was easy, and I was able to reinstall real AT&T stock android using their RUU exe file. After that it installs OTA updates too.
kelvov said:
Hello there everyone, sorry to add another 'bricked' thread to the first page but it seems the more I try to fix my phone on my own, the deeper the hole I'm digging becomes.
About a week ago I installed Cyanogenmod via their installer. It was nice and straightforward but I soon began to miss Sense 5.5 so I set out to return my phone to stock. This was a few days ago and since then I have learned about flashing, rooting, fastboot etc., but I am now stuck where I cannot make it past the Cyanogenmod logo and I have absolutely no idea where to start fixing things. I can't make any progress as I do not have USB debugging mode enabled (nor can I enable it now) and I have no backup other than the automatic backup to Dropbox.
Below is my getvar output. Phone is 'TAMPERED' and 'UNLOCKED'. Oh, the phone is not rooted and was bought in Hong Kong but I use o2 in England. Please let me know If there is any more information I need to include.
Thanks for taking the time to read this, any pointers would be very much appreciated
Click to expand...
Click to collapse
Do you have a nandroid backup of your phone? Remove IMEI and S/N from your last post!!
hp79 said:
I'm no expert, but maybe this can help.
Here's what I did with mine when I thought I bricked it. Keep in mind that I had a micro-USB to USB OTG cable. (costs less than $5)
Mine was bootloader unlocked, s-on but with hboot 1.55 or 1.54.
1. install TWRP recovery (openrecovery-twrp-2.6.3.3-m7.img) using fastboot.
2. Boot into TWRP recovery, then using OTG cable, mount a USB flash drive that has a installable zip image of the whole thing. I just used one from here:...
I got the "Download stock odexed 4.19.401.8" since I wanted to return it to stock like so I can return it.
I flashed it with that, and it would reboot into stock-like Android. I still had a bootloader from GoogleExperience version, and I accidentally did S-on before fixing these so I was screwed.
Anyways, that's how I got mine back to working state. After that, I couldn't get S-off (hboot 1.54) no matter what even using Rumrunner. Trying to get S-off again, I had to reflash the kernel with some other custom kernel, and then was able to do rumrunner to get s-off again. From that point, everything was easy, and I was able to reinstall real AT&T stock android using their RUU exe file. After that it installs OTA updates too.
Click to expand...
Click to collapse
Thanks for the info, will have to try it tomorrow after buying a cable
alray said:
Do you have a nandroid backup of your phone? Remove IMEI and S/N from your last post!!
Click to expand...
Click to collapse
Unfortunately no, I wrongly assumed a simple backup would have sufficed in the event anything went wrong. Never again. Oops, that for the heads up on that
You should be able to push ARHD 31.6 and be ok
sent from my mobile device
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?
Last night I got a notification for a System Update to version 6.12.161.5.
Has anyone tried this yet? And any problems found?
With the last two updates over the last 3-4 months I have had major problems:
1. When VodaFone forced the Rich Communication Suite / Service upon us; abysmal battery performance and terrible instability problem with phone frequently crashing on incoming calls and texts - which I 'solved' by Disabling RCS.
2. When VodaFone pushed the next update that greyed out the box to Disable RCS (they appeared to fix the instability and battery drain problem, but now I don't even have the option to disable RCS).
After lots of self-help and web searching I now have a stable phone with decent battery life again, and given those past painful experiences I am somewhat reluctant to blindly update.
Has anyone tried this Update yet, and can you comment after a few days of usage, particuarly on stability and battery usage?
Thanks
David
I had the 6.12.161.5 update a few days ago. Ive just had the 6.12.161.8 download now. Whats the difference?
Pilch2k said:
I had the 6.12.161.5 update a few days ago. Ive just had the 6.12.161.8 download now. Whats the difference?
Click to expand...
Click to collapse
Yeah, I also just had the 6.12.161.8 update. I've still not installed the previous one. I'm planning to wait this one out, after problems in the past. Will wait until some other folks try it first
daveingram said:
Yeah, I also just had the 6.12.161.8 update. I've still not installed the previous one. I'm planning to wait this one out, after problems in the past. Will wait until some other folks try it first
Click to expand...
Click to collapse
To be honest i've not noticed any issues yet, or any changes!
needed Ota file 6.12.161.8
Hi!
Would someone be so nice to post a link to his copy of this OTA? I need it desperately to revive my bricked One m7...
I've tryed anything but to flash this one on my s-on device..
Please help to save an Htc's life!! :cyclops:
Seymour2002 said:
Hi!
Would someone be so nice to post a link to his copy of this OTA? I need it desperately to revive my bricked One m7...
I've tryed anything but to flash this one on my s-on device..
Please help to save an Htc's life!! :cyclops:
Click to expand...
Click to collapse
you can not flash OTA to unbrick a phone. You need to flash the complete rom. And btw, OTA can not be flashed manually with S-ON, it must be initiated from the OS .
Flash firmware from OTA...
alray said:
you can not flash OTA to unbrick a phone. You need to flash the complete rom. And btw, OTA can not be flashed manually with S-ON, it must be initiated from the OS .
Click to expand...
Click to collapse
Well reading this sound like different from what you say... http://forum.xda-developers.com/showthread.php?t=2182823; but probably I'm wrong...
The actual thing is there's no Ruu nor OTA nor Zip for CID VODAP405 around... Or does?
Seymour2002 said:
Well reading this sound like different from what you say... http://forum.xda-developers.com/showthread.php?t=2182823;
Click to expand...
Click to collapse
Dont know what you are referring to.
The actual thing is there's no Ruu nor OTA nor Zip for CID VODAP405 around... Or does?
Click to expand...
Click to collapse
Unfortunately, there is not much files for that CID.
I don't understand what you want to attempt with an OTA file. Firmware included in OTA are not complete, it only contain files to be updated in an incremental way. If you manually flash a firmware from an OTA updates and you do it over the wrong version (currently installed on your phone) this could end with a bricked phone (hardbrick)
Flashing the entire OTA zip file will not help either. OTA files are patches that must be installed over a working rom and proper rom version. It also must be flashed using the "software update" option within the OS (unless the phone is s-off)
what you should do imo, is to start over fresh, flash twrp recovery 2.6.3.3 and flash a "close to stock" rom
Flash firmware from OTA...
First I want to thank for your help...
Then just to explain things, here's my awkward situation:
- I have a working rom but with battery that always stays at 1% no matter what, I get an ota update but I can't update since it says there's not enought battery...
the ota It gets is a 4.19.1540.9 which doesn't match with the follwing:
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.12.161.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH37WW904203
(bootloader) imei: 357864057367987
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP405
(bootloader) battery-status: good
(bootloader) battery-voltage: 4261mV
(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
To finish the cake: recovery doesn't work and bootloader is relocked and doesn't unlock anymore....
Any suggestion?
Seymour2002 said:
First I want to thank for your help...
Then just to explain things, here's my awkward situation:
- I have a working rom but with battery that always stays at 1% no matter what, I get an ota update but I can't update since it says there's not enought battery...
the ota It gets is a 4.19.1540.9 which doesn't match with the follwing:
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.12.161.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***************
(bootloader) imei: *********************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP405
(bootloader) battery-status: good
(bootloader) battery-voltage: 4261mV
(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
To finish the cake: recovery doesn't work and bootloader is relocked and doesn't unlock anymore....
Any suggestion?
Click to expand...
Click to collapse
how did you manage s-on + locked bootloader + no recovery ?
was this phone converted to DE or GPE at one time ?
Flash firmware from OTA...
I actually didn't do anything extraordinary except maybe to have flashed a rom with a different cid which got an update and brought me almost a this situation.
Then I wanted to bring the device to stock, so I flashed the original recovery and relocked the booloader. Nothing else.
I don't know why at the moment there's no way to enter recovery and if I try to unlock the bootloader again I reach the screen where I must agree on the device's screen to unlock, but then It just stuck on htc logo whilw trying to enter recovery..
Seymour2002 said:
I actually didn't do anything extraordinary except maybe to have flashed a rom with a different cid which got an update and brought me almost a this situation.
Then I wanted to bring the device to stock, so I flashed the original recovery and relocked the booloader. Nothing else.
I don't know why at the moment there's no way to enter recovery and if I try to unlock the bootloader again I reach the screen where I must agree on the device's screen to unlock, but then It just stuck on htc logo whilw trying to enter recovery..
Click to expand...
Click to collapse
are you sure your not just going to stock recovery ?
have you done the fastboot erase cache ?
followed by fastboot reboot-bootloader ?
what was the last custom recovery you had on their and what happened to make it gone ? RUU ?
Flash firmware from OTA...
clsA said:
are you sure your not just going to stock recovery ?
have you done the fastboot erase cache ? Yes, several times...
followed by fastboot reboot-bootloader ? Yes....
what was the last custom recovery you had on their and what happened to make it gone ? RUU ?
Click to expand...
Click to collapse
I was usimg twrp recovery, then I'm pretty sure I flashed the stock recovery, I don't know what happened to make it disappear, It just happened! I haven't been able to use any Ruu well since I never found the right one matching my CID., so I always got an error..
Seymour2002 said:
I was usimg twrp recovery, then I'm pretty sure I flashed the stock recovery, I don't know what happened to make it disappear, It just happened! I haven't been able to use any Ruu well since I never found the right one matching my CID., so I always got an error..
Click to expand...
Click to collapse
if you flashed the stock recovery correctly you go to the bootloader choose recovery hit power button
the screen will go black push volume up and tap power again to see the recovery menu, choose format data . factory reset
after it finishes reboot the phone and try again to unlock the bootloader
Flash firmware from OTA...
clsA said:
if you flashed the stock recovery correctly you go to the bootloader choose recovery hit power button
the screen will go black push volume up and tap power again to see the recovery menu, choose format data . factory reset
after it finishes reboot the phone and try again to unlock the bootloader
Click to expand...
Click to collapse
Once I select recovery from the bootloader menu and I press power button the phone reboots the bootloader...
SOLVED! Unbrikked THC ONE M/!!!!!
So thanks to MIke 1986 and his great page link:http://forum.xda-developers.com/showthread.php?t=2182823, I managed to recover my very very hrad brikked phone!!!!!!!!!
Here's what I did:
1- checked all phone's details with fastboot getavar all---> took note of CID - MID - versione OS installed etc.
2- took the OTA update corresponding to the firmware installed and extracted the firmware.zip
3- flashed the firmware.zip via fastboot (fastboot oem rebootRUU - fastboot flash zip firmware.zip [thanks to mike 1986]) ; #Alray: since a phone is S-On there's no risk to flash a wrong firmware and as I did anyone can do it via normal fastboot command with no issue!:angel:
4-In this way I recovered stock recovery and the possibility to unlock the bootloader again!!
5-moved a CWM nand backup to phone sd using sideload push command ( sideload push nandbackupname.zip /sd/cwm/backup/dateof backup - just make a nand backup yourself first to get exact loaction)
6-recovered from nandbackup using proper tool of cwm.
7-enjoyED MY revived device!!!!!! NOT THANKS TO ALRAY....http://cdn4.xda-developers.com/images/icons/icon8.gif
Seymour2002 said:
So thanks to MIke 1986 and his great page link:http://forum.xda-developers.com/showthread.php?t=2182823, I managed to recover my very very hrad brikked phone!!!!!!!!!
Here's what I did:
1- checked all phone's details with fastboot getavar all---> took note of CID - MID - versione OS installed etc.
2- took the OTA update corresponding to the firmware installed and extracted the firmware.zip
3- flashed the firmware.zip via fastboot (fastboot oem rebootRUU - fastboot flash zip firmware.zip [thanks to mike 1986]) ; #Alray: since a phone is S-On there's no risk to flash a wrong firmware and as I did anyone can do it via normal fastboot command with no issue!:angel:
4-In this way I recovered stock recovery and the possibility to unlock the bootloader again!!
5-moved a CWM nand backup to phone sd using sideload push command ( sideload push nandbackupname.zip /sd/cwm/backup/dateof backup - just make a nand backup yourself first to get exact loaction)
6-recovered from nandbackup using proper tool of cwm.
7-enjoyED MY revived device!!!!!! NOT THANKS TO ALRAY....http://cdn4.xda-developers.com/images/icons/icon8.gif
Click to expand...
Click to collapse
Glad you got your phone revived :good:
since a phone is S-On there's no risk to flash a wrong firmware
Click to expand...
Click to collapse
The risk is there, if you flash a firmware patch (ota firmware) over the wrong version (i.e 5.xx.xxx.x over 3.xx.xxx.x), this could brick. Happened many times that's why its mentioned in some threads. There is no risk flashing the same version like you did
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?