[Q] HTC One Restore on Reboot Android Revolution 12 - One (M7) Q&A, Help & Troubleshooting

I have HTC One International version and flashed device with Android Revolution HD 12, and later some time tried to install CM using rom manager but didn't succeed(this part done by my friend and i dont know what exactly happened) currently boot loader is unlocked and device is rooted and have Android Revolution HD 12 the problem is if device restart or shutdown the system has restored to previous date(date is unsuccessful CM install date) and other thing is if i try to sync anything email,sms...etc the device rebooted and restored to previous date, i tried to install Android Revolution HD again using usb flash drive and OTG cable install successful but when boot the phone phone restored to that previous date and i tried to factory reset and same result,means phone restored to previous date, and i tried to copy /system/xbin/busybox to /system/bin according to some forum the result was same i hope any guy have any idea to get back to work this HTC one is relay helpful. Thanks

jdchathuranga said:
I have HTC One International version and flashed device with Android Revolution HD 12, and later some time tried to install CM using rom manager but didn't succeed(this part done by my friend and i dont know what exactly happened) currently boot loader is unlocked and device is rooted and have Android Revolution HD 12 the problem is if device restart or shutdown the system has restored to previous date(date is unsuccessful CM install date) and other thing is if i try to sync anything email,sms...etc the device rebooted and restored to previous date, i tried to install Android Revolution HD again using usb flash drive and OTG cable install successful but when boot the phone phone restored to that previous date and i tried to factory reset and same result,means phone restored to previous date, and i tried to copy /system/xbin/busybox to /system/bin according to some forum the result was same i hope any guy have any idea to get back to work this HTC one is relay helpful. Thanks
Click to expand...
Click to collapse
Have you tried doing a full wipe in recovery, including system, then formatting so that it wipes the OS aswell ... Then try doing a clean install using your OTG and see if you still have any issues. Are you using TWRP or CWM btw? I often do what I mentioned to do a clean install but I use TWRP, I assume you can do the same in CWM though.
I don't understand what you mean with the frequent mentions of "date". You could always try running the RUU if it's available for your region/carrier and see if that resolves it.

AllAboutTheCore said:
Have you tried doing a full wipe in recovery, including system, then formatting so that it wipes the OS aswell ... Then try doing a clean install using your OTG and see if you still have any issues. Are you using TWRP or CWM btw? I often do what I mentioned to do a clean install but I use TWRP, I assume you can do the same in CWM though.
I don't understand what you mean with the frequent mentions of "date". You could always try running the RUU if it's available for your region/carrier and see if that resolves it.
Click to expand...
Click to collapse
Thanks for reply i'll try this, and im using TWRP, date is unsuccessful rom flash date.

jdchathuranga said:
Thanks for reply i'll try this, and im using TWRP, date is unsuccessful rom flash date.
Click to expand...
Click to collapse
try and twrp 6.0.1 and ordroid 8.2.5 to see how it goes! just an advice

AllAboutTheCore said:
Have you tried doing a full wipe in recovery, including system, then formatting so that it wipes the OS aswell ... Then try doing a clean install using your OTG and see if you still have any issues. Are you using TWRP or CWM btw? I often do what I mentioned to do a clean install but I use TWRP, I assume you can do the same in CWM though.
I don't understand what you mean with the frequent mentions of "date". You could always try running the RUU if it's available for your region/carrier and see if that resolves it.
Click to expand...
Click to collapse
First sorry for late reply
I tried to re-lock bootloader (fastboot oem lock) it says successfull but when rebooted to bootloader it says UNLOCKED so i can't try RUU, i tried many solution out there but no luck, as my idea if i re lock bootloader may be posible to try RUU and go back to stock rom and problem will solve but the problem is how to relock boot loaded i tried fastboot oem lock (on both winodws and mac), it says success but when rebooted still UNLOCKED any idea how to relock bootloader ?
Thanks

Related

Updating and restoring to stock issues

I have an HTC One by T-Mobile, Our update was released Monday. I tried to update but when it rebooted it went to install and failed to install, I looked up some information that say usually the cause of the failed install for software system updates is because of an unlocked bootloader and custom recovery. So I've tried to restore to factory OEM settings but every time it fails to up restore to the factory update as well. I'm at a loss here and no Idea what to do. I can flash any custom roms I want and those seem to work and flash just fine but If I try anything else like reverting to OEM stock it doesn't work. Anyone have any Ideas?
Before anyone asks, I've tried doing a RRU restore from desktop and .Zip on my phone and neither work. Both fail.
TaintedCross said:
I have an HTC One by T-Mobile, Our update was released Monday. I tried to update but when it rebooted it went to install and failed to install, I looked up some information that say usually the cause of the failed install for software system updates is because of an unlocked bootloader and custom recovery. So I've tried to restore to factory OEM settings but every time it fails to up restore to the factory update as well. I'm at a loss here and no Idea what to do. I can flash any custom roms I want and those seem to work and flash just fine but If I try anything else like reverting to OEM stock it doesn't work. Anyone have any Ideas?
Before anyone asks, I've tried doing a RRU restore from desktop and .Zip on my phone and neither work. Both fail.
Click to expand...
Click to collapse
Get s-off and restore any RUU.. After restore, better get s-off before you update, you won't be able to get it after the update.
Sent from my iPod touch using Tapatalk
TaintedCross said:
I have an HTC One by T-Mobile, Our update was released Monday. I tried to update but when it rebooted it went to install and failed to install, I looked up some information that say usually the cause of the failed install for software system updates is because of an unlocked bootloader and custom recovery. So I've tried to restore to factory OEM settings but every time it fails to up restore to the factory update as well. I'm at a loss here and no Idea what to do. I can flash any custom roms I want and those seem to work and flash just fine but If I try anything else like reverting to OEM stock it doesn't work. Anyone have any Ideas?
Before anyone asks, I've tried doing a RRU restore from desktop and .Zip on my phone and neither work. Both fail.
Click to expand...
Click to collapse
you need to flash the stock recovery and lock your bootloader to be able to do the update.
[email protected] said:
you need to flash the stock recovery and lock your bootloader to be able to do the update.
Click to expand...
Click to collapse
I'm pretty sure you don't need to relock the bootloader for OTAs, you do however need 100% stock ROM and (a very close) stock recovery for that ROM.
nkk71 said:
I'm pretty sure you don't need to relock the bootloader for OTAs, you do however need 100% stock ROM and (a very close) stock recovery for that ROM.
Click to expand...
Click to collapse
i stand corrected.
a stock recovery will do
[email protected] said:
i stand corrected.
a stock recovery will do
Click to expand...
Click to collapse
Only for OTAs, to run a full RUU exe, I do think the bootloader has to be locked/relocked
nkk71 said:
Only for OTAs, to run a full RUU exe, I do think the bootloader has to be locked/relocked
Click to expand...
Click to collapse
Not going to matter anyway, I accidently wiped my whole OS. I've tried using adb Sideload but it wont detect my device.
TaintedCross said:
Not going to matter anyway, I accidently wiped my whole OS. I've tried using adb Sideload but it wont detect my device.
Click to expand...
Click to collapse
Restart your computer, also update to latest HTC drivers and adb sdk.
Alternate method, use an OTG cable with a USB stick with a ROM.ZIP on it, and mount "external sdcard" (or whatever it's called) in custom recovery.
nkk71 said:
Restart your computer, also update to latest HTC drivers and adb sdk.
Alternate method, use an OTG cable with a USB stick with a ROM.ZIP on it, and mount "external sdcard" (or whatever it's called) in custom recovery.
Click to expand...
Click to collapse
I have restarted like 20 times, still doesn't detect it. And I don't have an OTG cable
TaintedCross said:
I have restarted like 20 times, still doesn't detect it. And I don't have an OTG cable
Click to expand...
Click to collapse
Does fastboot work?
Sent from my HTC One using Tapatalk
nkk71 said:
Does fastboot work?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I can boot into fastboot on my phone but I've no idea what to do from there.
Edit: HELLS YEAH! I got it! lol had to relock bootloader using fastboot and then go back into fastboot on my phone and run the RUU.exe and it worked this time! SOOO freaking stoked and happy! I've been up for 7 hours straight trying to fix this!
Nice. Please update the thread and put SOLVED
Sent from my HTC One using xda app-developers app

[Q] Trying to downgrade

Firstly, thanks to SafinWasi and Red_81 who both helped me on other threads, this question follows on from those threads.
I'm trying to downgrade from 7.4.9 user 4952320. Eventually, I will probably install CM11 (I tried once and bricked my device), but for now I just want to downgrade the OS and be able to change the wallpaper, I'm sick of the black paper. (I've tried Stunts wallpaper fix and it didn't work)
When the device upgraded to 7.4.9 I made backups of the whole 12 img files (inc boot0block).
I've read that you need a 7.2.3 boot image to be able to install TWRP as part of the CM11. I obtained a rooted 7.2.3 boot image from Red_81s google drive. I then flashed that boot image and tried rebooting the device. No joy. I got the red triangle. I flashed my 7.4.9 boot image and rebooted. The device rebooted and worked as normal.
I then flashed the 7.2.3 rooted system image and rebooted. Again I got the red triangle. I then flashed the 7.2.3 boot image, (so the device had 7.2.3 system and boot images) but again I got the red triangle.
So, how do you downgrade? Should I have flashed all 3 of the 7.2.3 images? (I don't have the checksums of the images so I recognise if one of the images was corrupted the exercise was doomed to failure.)
By flashing my 7.4.9 system and boot images, my device was restored to functionality, and I learned a bit, but not enough to achieve the goal. I'm hoping someone can show me how to downgrade.
Thought I'd add that I did try Kindle Fire First Aide but got lots of errors about dropbox not being available.
Did you flash the system and recovery? Both are needed to successfully downgrade. I always wipe data too.
Sent from my Nexus 7 using XDA Premium 4 mobile app
cecr said:
.
Click to expand...
Click to collapse
You need to flash a custom recovery on a second bootloader as well. You can't just flash the system. You also need to flash the 7.2.3 boot.img and stack override. Any tutorial dealing with this mod will include all the steps. It important to pay attention to details and not skip any steps. http://forum.xda-developers.com/showthread.php?t=2128848
Sent from my Nexus 7 Flo running Paranoid Android 4.4.3 using XDA premium 4 mobile app
Red_81 said:
Did you flash the system and recovery? Both are needed to successfully downgrade. I always wipe data too.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I didn't flash recovery, at my first attempt, just boot, then I tried boot & system. Both tries gave the red triangle.
I've tried again, with all 3 rooted images from your gdrive - recovery, boot & system, and again got the red triangle. I tried again with the 3 images from another source (my own unrooted 7.2.3 backup when I first got the HD7) and again, got the red triangle.
I haven't wiped the data because I would prefer to keep it so I can use the device (and think it should be possible to downgrade without wiping). I haven't been able to find a command to wipe just the cache...
So I'm more than a bit puzzled. The fastboot commands (eg fastboot -i 0x1949 flash boot boot.img) all return with "sending" then "OKAY", then "writing", then "OKAY" so I don't think there's any problem there.
I must be doing something wrong or missing something.
LinearEquation said:
You need to flash a custom recovery on a second bootloader as well. You can't just flash the system. You also need to flash the 7.2.3 boot.img and stack override. Any tutorial dealing with this mod will include all the steps. It important to pay attention to details and not skip any steps. http://forum.xda-developers.com/showthread.php?t=2128848
Sent from my Nexus 7 Flo running Paranoid Android 4.4.3 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Thanks for your response, but at this stage I don't want to flash a new custom ROM, that may (probably will) come later, but at this stage I want to just downgrade. I've been warned that installing TWRP etc may leave the stock system in a bootloop, so a working stock backup won't be possible.
As I have to downgrade the stock boot image anyway in order to install a custom ROM, I thought I'd downgrade the whole OS in order to have a functioning stock system, then I can make a backup of it in TWRP, then install a custom ROM.
If I'm having problems with a simple downgrade, I might have more severe problems flashing a new ROM and be left with a dead device like I was previously, hence my caution and not wanting to move on until I know I can recover to the previous step if things go wrong.
Did you try downloading the original 7.2.3 from the thread and try flashing them ?
Red_81 said:
Did you try downloading the original 7.2.3 from the thread and try flashing them ?
Click to expand...
Click to collapse
Yes, I did. Tried them twice, in a different order (didn't think it would make a difference but you never know....). Anyway, tried again, this time, wiped data and cache (took 45 mins) and it worked! I now have 7.2.3 and access to Gplay (was already there).
I haven't registered it to my Amazon account yet, so email and contacts don't work, and am wondering if I should go straight to installing a custom ROM. I'm thinking if it isn't registered to Amazon, then they can't update it via OTA...... or can they?
It's been a bit of a task getting this far, but at least I'm more confident about getting into ADB and Fastboot!
cecr said:
I'm thinking if it isn't registered to Amazon, then they can't update it via OTA...... or can they?
Click to expand...
Click to collapse
well, I know the answer, yes, even though it hasn't logged into an Amazon account (I realise they pre-register them to your account before dispatch), it updated back to 7.4.9 just as I finished the above post and whilst I was thinking I should disable OTA updates using KFFA!
flip. This is turning into hard work. lol, still I know how to do it now.
I was having many issues after the last OTA and got mine to cm-11-20140609-SNAPSHOT-M7 last night. Mine was at 7.4.9 also. I followed rootjunky youtube videos to get mine re-rooted, flashed and working. After getting it rooted, he uses Fire Flash app to put twrp on the Kindle. I deviated a little and put the twrp 2.7.0.0 version other than that, I followed to a T. Once I got all that done, I went on the internet to Hashcode's repository and downloaded the newest cm-11 UNOFFICIAL he had listed directly to the device. I downloaded the latest Gapps from cyanogenmod and then booted into recovery(twrp) and installed. Everything is working beautifully now. Everything seems faster and smoother so far. I did go ahead and do an update from the about area in the settings to cm-11-20140609-SNAPSHOT-M7. I was also able to get all my books that I had purchased through kindle in the kindle reader.
greg2074 said:
I was having many issues after the last OTA and got mine to cm-11-20140609-SNAPSHOT-M7 last night. Mine was at 7.4.9 also. I followed rootjunky youtube videos to get mine re-rooted, flashed and working. After getting it rooted, he uses Fire Flash app to put twrp on the Kindle. I deviated a little and put the twrp 2.7.0.0 version other than that, I followed to a T. Once I got all that done, I went on the internet to Hashcode's repository and downloaded the newest cm-11 UNOFFICIAL he had listed directly to the device. I downloaded the latest Gapps from cyanogenmod and then booted into recovery(twrp) and installed. Everything is working beautifully now. Everything seems faster and smoother so far. I did go ahead and do an update from the about area in the settings to cm-11-20140609-SNAPSHOT-M7. I was also able to get all my books that I had purchased through kindle in the kindle reader.
Click to expand...
Click to collapse
Nice to know. Think I'll be doing something very similar, now I've made backups of 7.4.9 "just in case". Just have to go through all the above again!

[Q] Chronic phone problems. Want to nuke the whole thing and start again.

I have had inklings that something was a little off with my installation for a little bit. It has always been like pulling teeth to get a rom installed on my htc one, and for the most part I had to sideload everything I wanted to install.
I ran a snapshot of cyanogen for a while, but my phone refused to update to new versions. I got frustrated and installed the nocturnal GPE rom which worked fine for a few months, but recently would not connect to the networks. I attempted to run the factory reset command from TWRP, but the phone hung for an hour trying to erase the cache. Then when I restarted the phone, instead of seeing the boot screen for the GPE rom I had most recently installed, I saw the cyanogen boot screen.
I have had little luck reinstalling roms since then and also have some problems with the recoveries. I have to install CWM or whatever recovery I dont have installed to even get sideloading to work. I've installed the nocturnal GPE rom again, but when it gets to the screen to select English it just restarts without warning.
Right now I just want to know if it is possible to nuke everything but the bootloader and just start fresh from factory settings. I want the nightmare to be over!
I have done everything in this thread:
http://forum.xda-developers.com/htc-one/help/lost-signal-cache-boot-recovery-t2851707/post54949931
gothmog1114 said:
I have had inklings that something was a little off with my installation for a little bit. It has always been like pulling teeth to get a rom installed on my htc one, and for the most part I had to sideload everything I wanted to install.
I ran a snapshot of cyanogen for a while, but my phone refused to update to new versions. I got frustrated and installed the nocturnal GPE rom which worked fine for a few months, but recently would not connect to the networks. I attempted to run the factory reset command from TWRP, but the phone hung for an hour trying to erase the cache. Then when I restarted the phone, instead of seeing the boot screen for the GPE rom I had most recently installed, I saw the cyanogen boot screen.
I have had little luck reinstalling roms since then and also have some problems with the recoveries. I have to install CWM or whatever recovery I dont have installed to even get sideloading to work. I've installed the nocturnal GPE rom again, but when it gets to the screen to select English it just restarts without warning.
Right now I just want to know if it is possible to nuke everything but the bootloader and just start fresh from factory settings. I want the nightmare to be over!
I have done everything in this thread:
http://forum.xda-developers.com/htc-one/help/lost-signal-cache-boot-recovery-t2851707/post54949931
Click to expand...
Click to collapse
Follow this guide.
StormyNight said:
Follow this guide.
Click to expand...
Click to collapse
I tried that. When flashing the firmware, I get (bootloader) read zipped android_info fail. FAILED (remote: 99 unknown fail)
gothmog1114 said:
I tried that. When flashing the firmware, I get (bootloader) read zipped android_info fail. FAILED (remote: 99 unknown fail)
Click to expand...
Click to collapse
Could you screenshot the bootloader for me?
Maybe you've got a whacked recovery. Reflash from fastboot from an md5 verified .img (make sure its m7wls version of TWRP). You should have no problems wiping any partition from within.
StormyNight said:
Could you screenshot the bootloader for me?
Click to expand...
Click to collapse
http://imgur.com/GwCBmpe
gothmog1114 said:
http://imgur.com/GwCBmpe
Click to expand...
Click to collapse
Are you using a Windows 8 computer? If so, try it with Windows 7. If you're using Windows 7, try a different port (preferably a USB 2.0 port).

[Q] Another I completely screwed my phone thread

I have been trying to flash a custom ROM and achieve S Off for a couple of days now and through lots of searching and trial and error made good progress on a system much more complicated than my previous phones/tablets that I have rooted. I was feeling good yesterday and had figured out the whole HTC DEV thing, how to use Fastboot and ADB. Unlocked, flashed recovery, used rumrunner(said I needed to swap ROMs first), and then tried to use the CM installer. This is where things went sideways. The installer found my phone and said everything was cool, then said complete. At this point my was stuck on the Android with its front cover open screen. After waiting a while, I was forced to reboot. Now I am stuck in a bootloop. I have access to Fastboot and Recovery (TWRP 2.8.1.0) but can't mount anything and sideload refuses to work. I have tried 4 different roms with that. I failed to make a backup in recovery once I got it installed but I am not sure that would do a damn at the moment anyway. I have seen a number of threads with similar problems but can't get anything suggested in them to work in my case. Thanks in advance.
singleslammer said:
I have been trying to flash a custom ROM and achieve S Off for a couple of days now and through lots of searching and trial and error made good progress on a system much more complicated than my previous phones/tablets that I have rooted. I was feeling good yesterday and had figured out the whole HTC DEV thing, how to use Fastboot and ADB. Unlocked, flashed recovery, used rumrunner(said I needed to swap ROMs first), and then tried to use the CM installer. This is where things went sideways. The installer found my phone and said everything was cool, then said complete. At this point my was stuck on the Android with its front cover open screen. After waiting a while, I was forced to reboot. Now I am stuck in a bootloop. I have access to Fastboot and Recovery (TWRP 2.8.1.0) but can't mount anything and sideload refuses to work. I have tried 4 different roms with that. I failed to make a backup in recovery once I got it installed but I am not sure that would do a damn at the moment anyway. I have seen a number of threads with similar problems but can't get anything suggested in them to work in my case. Thanks in advance.
Click to expand...
Click to collapse
go back to twrp 2.6.3.3 version and sideload or push arhd
alray said:
go back to twrp 2.6.3.3 version and sideload or push arhd
Click to expand...
Click to collapse
I got that to work, installed ARHD Google version (regular kept failing). Rebooted and then went into a boot loop that would get to the "Welcome" screen and then loop again. Suggestions?
singleslammer said:
I got that to work, installed ARHD Google version (regular kept failing). Rebooted and then went into a boot loop that would get to the "Welcome" screen and then loop again. Suggestions?
Click to expand...
Click to collapse
I'll suggest you read the OP before flashing anything to your phone, especially when you'll have s-off. ARHD GPE (google version) require S-OFF to be used (and clearly mentioned in the OP of ARHD GPE) If you keep flashing things without reading when you'll have s-off, you'll probably end with an hard-bricked device
From arhd GPE OP:
Android Revolution HD 6.1
Google Edition
You need S-OFF, otherwise you'll experience boot-loop!
You can't use ART with deodexed custom ROM
You need TRWP 2.6.3.3 custom recovery!
--- MD5 Checksum: 2A9CD96A42C79D64A7933ECE76AD84E6 ---
Click to expand...
Click to collapse
So go ahead and flash a Sense based version of ARHD.
http://forum.xda-developers.com/showthread.php?t=2183023
Thanks, I originally saw that and in my frustration missed it. I feel like an idiot. Appreciate the help.

M7 Totally Messed up

I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Try re download the zip (or try an other rom)maybe you just got an false download. i also had some trouble with my m7 back in the day.
But in your case now you are stuck with no os or bootloop, i give you as advice to follow an soft unbrick method it worked for me, or if you have an usb otg cable and usb or and usb otg thumbstick, put the rom on that usb and connect it to your phone and then try to flash it (if your using twrp you have an option to choose from wich storage you want to use)
Also a piece of advice, when flashing roms, kernels etc please have your phone charged above 50% (just in case).
Sent from my HUAWEI P7-L10 using XDA Free mobile app
---------- Post added at 09:28 PM ---------- Previous post was at 09:27 PM ----------
its the peanut said:
Try re download the zip (or try an other rom)maybe you just got an false download. i also had some trouble with my m7 back in the day.
But in your case now you are stuck with no os or bootloop, i give you as advice to follow an soft unbrick method it worked for me, or if you have an usb otg cable and usb or and usb otg thumbstick, put the rom on that usb and connect it to your phone and then try to flash it (if your using twrp you have an option to choose from wich storage you want to use)
Also a piece of advice, when flashing roms, kernels etc please have your phone charged above 50% (just in case).
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Click to expand...
Click to collapse
Also make sure you downloaded the rom made for your phone model!
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Can you please post the output of
Code:
fastboot getvar all
please remove your imei and serial number.
Depending on which variant of the M7 you have you probably just need a different version of recovery to install a CM rom. I think they prefer TWRP 2.7.x.x. Post the getvar and we can see what you have. then I can give you a better informed instruction. :good:
P.s also check the md5 of the rom zip you downloaded. Use this tool www.winmd5.com the correct md5 should be listed with the link you downloaded the rom from
failed to mount /dev/block/blah blah blah = needs "block:by-name" support which twrp 2.6.3.3 doesn't have
everything explained here
So update your recovery
and do what danny said above so he can confirm you have the right rom/recovery for your device.
Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Your getvar looks fine this rom should work fine with your device. Download this version of TWRP https://www.androidfilehost.com/?fid=23501681358561860 (2.7.1.2). dropthe file in your fastboot folder and flash it with fastboot.
Code:
fastboot flash recovery "name-of-recovery".img
fastboot erase cache
fastboot reboot-bootloader
Once thats done reflash the rom with the new version of TWRP. It should flash just fine :good:
iv managed to flash cm12.1 now, thanks guys, is there anyway i could get the HTC software back on.
Burky1996 said:
iv managed to flash cm12.1 now, thanks guys, is there anyway i could get the HTC software back on.
Click to expand...
Click to collapse
There are a number of ways to return to stock software. You can simply flash a stock rom through twrp or use a stock nandroid. look for rom that match your version main. 7.19.401.22
I think there is even an lollipop 7.19.401.22 RUU for your device but I'm not sure if it will work with s-on though because it's a zip but it certainly wouldnt hurt to try it though. You will need to relock your bootloader and flash it with fastboot.
I'll edit this post with links when I find them unless some one beats me to it
Hey Dan do you think we could skype and you could talk me through it, it would be much easier?
Burky1996 said:
Hey Dan do you think we could skype and you could talk me through it, it would be much easier?
Click to expand...
Click to collapse
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.
Danny201281 said:
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.
Click to expand...
Click to collapse
i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.
i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.
Burky1996 said:
i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.
Click to expand...
Click to collapse
Okay try this. Download the OTA but select the option "Install Later" connect your m7 to your pc and browse your storage. In the download folder on your phone you should find the OTA in zip format. Copy it to your pc.
Now open the OTA zip on your pc. Inside you'll find another zip called "firmware.zip" extract it then open it. Inside you'll find a recovery.img. extract the recovery file and flash it with fastboot. Now reboot to android and continue to install the OTA. :fingers-crossed:
Sent from my SM-T230 using Tapatalk
im going to have to unlock the boot loader again and then do it
Burky1996 said:
im going to have to unlock the boot loader again and then do it
Click to expand...
Click to collapse
Yes you will need to unlock the bootloader to flash the recovery, Dont forget to fastboot erase cache after flashing the recovery that is cruicial. You don't need to be relocked to install the OTA though.
When you select install now, the device should reboot to the Stock Recovery. At first the screen will just be black for a short while. Then you'll see an image of a phone with a Green ring and download arrow. If you hold Volume up and press the power button you will see the Stock Recovery and its progress in installing the OTA.
I'm not sure why your device was hanging on boot after installing the OTA. Maybe a bad recovery.img. that's why I say to get the recovery from the OTA file.
its still not working so i mite just install twrp and restore to cm12.1
Burky1996 said:
im going to have to unlock the boot loader again and then do it
Click to expand...
Click to collapse
Yes you will need to unlock the bootloader to flash the recovery, Dont forget to fastboot erase cache after flashing the recovery that is cruicial. You don't need to be relocked to install the OTA though.
When you select install now, the device should reboot to the Stock Recovery. At first the screen will just be black for a short while. Then you'll see an image of a phone with a Green ring and download arrow. If you hold Volume up and press the power button you will see the Stock Recovery and its progress in installing the OTA.
I'm not sure why your device was hanging on boot after installing the OTA. Maybe a bad recovery.img. that's why I say to get the recovery from the OTA file.
Danny201281 said:
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.
Click to expand...
Click to collapse
could it be not working coz my hboot has changed to 1.51.
Burky1996 said:
could it be not working coz my hboot has changed to 1.51.
Click to expand...
Click to collapse
Your still stuck with this? Try starting the process over, but do not relock your bootloader at any point.
Wipe system data and cache partitions with TWRP Advanced wipe
Flash the Rom with twrp as a clean install.
Reboot and download the OTA. Choose install later, then copy the OTA to your pc. Extract the Stock Recovery and flash it with fastboot. Reboot and install the OTA.
But do not relock your boot loader. Because when you unlock the bootloader, it wipes the device including the data/preload folder. If the preload folder is not intact the OTA will fail
Sent from my M7 Running ARHD 92.x

Categories

Resources