Related
Hi guys.
Finally today I receive the OTA upgrade to JB. First an smal upgrade was succesfully downloaded and installed, and then the firmware to upgrade the phone to JB (I had 4.03 custom rom).
After the phone install the JB upgrade the phone stuck on the HTC ONE white screen
I had a backup on the SD that let me recover the phone, I try to install the upgrade again, with the same luck. I read a post that said that erasing the SD will resolve the issue, and I have no better idea than do it!!! (yeah... really!!)
I read several post all day on XDA, I try to flash again the boot and ROM with the upgrade that I save on my PC, and with a Backup via
fastboot. But nothing work (I dont know if I did it right). I cant see the SD on fastboot, already try a factory reset, when I go to the recovery option on fastboot the phone just rebooted with no options.
My CID is BSTAR301
***UNLOCKED***
ENDEAVORU PVT SHIP S-ON RH
HBOOT-1.39.0000
CPLD-None
MICROP-None
RADIO-5.1204.162.29
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Dec 17 2012, 13:59:37
Attached are the backup files that I have in my pc and the OTA upgrade files that my phone download.
Here there are many people who know a lot of this!!
Please help me to recover my phone!
u say you are on a custom rom, But you tried to update OTA?
Restore phone to complete stock ( even recovery) then you can update.
you could use an RUU or maybe a nandroid
{< r o N o $ said:
u say you are on a custom rom, But you tried to update OTA?
Restore phone to complete stock ( even recovery) then you can update.
you could use an RUU or maybe a nandroid
Click to expand...
Click to collapse
Sorry, I mean I had the ORIGINAL ROM (4.03), the only change that I made was root the phone.
My CID is BSTAR301, I only have the backup files that I copy to my pc and the OTA upgrade that the phone download. I attach the images of the files that I have.
Could you please tell me how to restore it to complete stock with the commands? which files should I use?
Thanks for you help.
guillerhcp said:
Sorry, I mean I had the ORIGINAL ROM (4.03), the only change that I made was root the phone.
My CID is BSTAR301, I only have the backup files that I copy to my pc and the OTA upgrade that the phone download. I attach the images of the files that I have.
Could you please tell me how to restore it to complete stock with the commands? which files should I use?
Thanks for you help.
Click to expand...
Click to collapse
I assume that you first installed CWM or TWRP recovery to root your HOX, and if you make backup of your recovery this is CWM or TWRP recovery.img, not stock recovery.img that is came with phone because you reflashed original one with TWRP or CWM and official ROM need official recovery.img. I hope that you make nandroid backup before root with TWRP or CWM because is it "must to do" in every installation guide. If so, when you wanted to update via OTA for official JB you needed to:
1. reverse to stock software (for you, you needed only to unroot or use nandroid backup if you have yours, if not try to find one in xda one x forum matching your current CID and main-version)
2. reverse to stock recovery.img that is matching your CID (exact matching) (you need to find it on xda one x forum section) - i see that you have firmware folder but dont know is it from your backup or from OTA, if it is from OTA than you can use recovery.img from that folder to flash stock recovery.img via fastboot commands (only recovery.img)
3. then you can do official JB update via OTA
And then if you have need to custom ROM you need flash again CWM or TWRP recovery.img
Also you can get full stock with RUU but RUU must fully match your CID and main version, but RUU isn't available for every phone version, and after RUU you can do officall OTA JB update (for RUU you need to lock bootloader)
Information that can help us is yours phone current main version (fastboot getvar version-main)
hpnxfox said:
I assume that you first installed CWM or TWRP recovery to root your HOX, and if you make backup of your recovery this is CWM or TWRP recovery.img, not stock recovery.img that is came with phone because you reflashed original one with TWRP or CWM and official ROM need official recovery.img. I hope that you make nandroid backup before root with TWRP or CWM because is it "must to do" in every installation guide. If so, when you wanted to update via OTA for official JB you needed to:
1. reverse to stock software (for you, you needed only to unroot or use nandroid backup if you have yours, if not try to find one in xda one x forum matching your current CID and main-version)
2. reverse to stock recovery.img that is matching your CID (exact matching) (you need to find it on xda one x forum section) - i see that you have firmware folder but dont know is it from your backup or from OTA, if it is from OTA than you can use recovery.img from that folder to flash stock recovery.img via fastboot commands (only recovery.img)
3. then you can do official JB update via OTA
And then if you have need to custom ROM you need flash again CWM or TWRP recovery.img
Also you can get full stock with RUU but RUU must fully match your CID and main version, but RUU isn't available for every phone version, and after RUU you can do officall OTA JB update (for RUU you need to lock bootloader)
Information that can help us is yours phone current main version (fastboot getvar version-main)
Click to expand...
Click to collapse
Thanks for your help! I got the an RUU, after that I sent my backup to SD and now I have 4.0.4.
Now my phone show me a message to install the OTA to 4.1.1, but when I select install the phone make a reboot and show me CWM recovery with the message:
Finding update package...
E:unknown volume for path [INTERNALSDCARDownload/OTA_ENDEAVOR_U_JB_S_BSTR_ESN_3.14.515.36-2.17.515.1....
E:Can't mount INTERNALSDCARD...
Installation aborted.
Why the phone can't mount the SD?
You need a stock recovery. Do :
Fastboot getvar version-main
And post the outcome !
Edit :
4.0.4 software....you need this recovery and then install the ota again
http://db.tt/U5CK4noo
Mr Hofs said:
You need a stock recovery. Do :
Fastboot getvar version-main
And post the outcome !
Edit :
4.0.4 software....you need this recovery and then install the ota again
This is the result:
C:\CustomRUU>Fastboot getvar version-main
version-main: 3.14.515.36
So... I just need to install the recovery that you send me, reboot and try to install the OTA?
Click to expand...
Click to collapse
Mr Hofs said:
You need a stock recovery. Do :
Fastboot getvar version-main
And post the outcome !
Edit :
4.0.4 software....you need this recovery and then install the ota again
Click to expand...
Click to collapse
THANKS HOFS!!!
After installing the stock recovery 2.17, JB was installed successfully.
You have no idea how much appreciate your help!
Thank you!!!!
Hello All,
So I recently bought a M8 and I just need some help in getting the steps nailed down correctly. Be warned long post with lots of questions...
Code:
fastboot getvar version-main
version-main: 3.32.111.3
fastboot oem readcid
(bootloader) cid: T-MOB101
That is basically my device, now due to it being 4.4.4 from factory I am unable to use Sunshine & Weaksauce. I could wait until the new year but why
bother .
First step:
Get my factory firmware image after reading this thread: http://forum.xda-developers.com/showthread.php?t=2701376 due to it being a T-Mobile and
Germany and 4.4.4 I am unable to run the command listed there to get the stock recovery, so how do I get the stock recovery for my device? @BerndM14
Has provided me with a link to download the latest firmware for my device but it has the TWRP recovery inside it, link is this one: http://www.handy-
faq.de/forum/htc_one_m8_custom_roms/304821-htc_one_m8_firmwaresammlung_ruus_otas_backups.html#post2832636. I should point out that I do have a OTA
waiting to download and install, should I download and install it? The version listed on the screen is 3.32.111.9 and is only 183.73MB. Would it have a
viable stock recovery? Can I downgrade to a older version for the stock recovery?
Second step:
Once the above is done and dusted my next step is getting root & S-OFF & custom recovery. This is relatively simple because all I need to do is visit
HTCDev, unlock and then S-OFF with Sunshine and then a custom recovery. Correct? Sounds and looks simple enough.
Third step:
Download ROM of choice and flash away. So I am going with InsertCoin due to user loyalty from the Desire days . However I see people in the thread
mentioning that they flashed the latest firmware to sort out a couple of issues, I take it they mean the ROM file and not HTC firmware?
Fourth and probably not needed step:
Changing the phone to WWE and SuperCID? Do I really need to do this? Benefit of changing to WWE is changing the HBOOT to a more universal one? The
reason why I am thinking of converting is because I would want to get rid of the red text on the boot screen as listed here: http://forum.xda-
developers.com/showpost.php?p=51744965&postcount=1 however for T-Mobile Dutch the HBOOT CIDS are T-MOB003, if I flash that would it cause a problem?
I would also be looking at running the commands to change the flags showing tampered and unlocked but that looks simple to do. Am I missing anything? For warranty purposes I would use the instructions from this thread: http://forum.xda-developers.com/showthread.php?t=2710735 but download the recovery file for T-MOB Germany instead?
Thank you for reading the long post and I hope that I have made some sort of sense.
Yes it will have the firmware.zip with the recovery.img inside it. Even the small 47MB or so, OTA update for the WWE from 2.22.401.4 - 2.22.401.5 had the firmware.zip inside. So just download the OTA.zip copy to PC extract firmware.zip and grab the recovery.img.
Benefits to converting to WWE or even Developer edition also includes the fact that those devices will receive OTA updates before any carrier version, directly from HTC. It's a bonus if you're into the "latest & greatest" scene.
As for making a backup before flashing custom recovery, have you tried booting the custom recovery? Philz will probably be better if you want to use the booted custom recovery to make a backup of stock recovery. You could also try and boot either TWRP or Philz and see if you can root your device without flashing custom recovery, that way you can at least use the dd command to grab a copy of the recovery block. <My preferred method, though it's a terrible circle. Need to flash custom recovery to root, need root to make backup of stock recovery... So hopefully booting the custom recovery will work. That being said, easiest way still remains to grab it from the OTA.zip.
Perhaps you could even upload a copy of the OTA.zip and share it on here, I don't think the OP has a copy in the second post
ROM/Firmware. You need the latest firmware to run the latest ROM. For most it'll be firmware with 3.x. If you still run on 2.x(which you aren't) you'd have some problems with radio(bluetooth, gps, wifi, data etc)
Thank you for the reply .
To be honest I have not tried booting a custom recovery because I saw this in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=2701376
fastboot boot recovery_filename.img (this does not work on the latest 3.xx firmwares !!! we need to get the stock recoveries from the OTA files)
Click to expand...
Click to collapse
So I am not sure what to try to be honest. This toolkit: http://forum.xda-developers.com/showthread.php?p=51383278&highlight=ota#post51383278 mentions getting root without S-OFF but with a unlocked bootloader. So I am thinking that if I follow those steps, maybe when I get to the reboot phase I can execute a nandroid instead which might get me the files I want?
I won't bother with WWE then. I will rely on the dev's to give me the latest & greatest .
Anakha56 said:
Thank you for the reply .
To be honest I have not tried booting a custom recovery because I saw this in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=2701376
So I am not sure what to try to be honest. This toolkit: http://forum.xda-developers.com/showthread.php?p=51383278&highlight=ota#post51383278 mentions getting root without S-OFF but with a unlocked bootloader. So I am thinking that if I follow those steps, maybe when I get to the reboot phase I can execute a nandroid instead which might get me the files I want?
I won't bother with WWE then. I will rely on the dev's to give me the latest & greatest .
Click to expand...
Click to collapse
Hm, yeah I also had some problems booting a recovery, but I just tested it out again. I can at least boot TWRP version 2.8.3.0 so it still works for me. I'm on 3.28.1540.5 (Developer edition). Haven't tried Philz though, net a bit too slow to bother with even a small download
No problem. I am busy downloading the OTA.zip and once complete I will try the toolkit method and see what happens . Again, thank you for the reply.
I need some help... My phone seems to be stuck in fastboot mode and is not picked up in Device Manager of Windows. I can touch the fastboot screen and it vibrates but it does not nothing. I have held down the power button for 20 seconds with no result. I had just unlocked the bootloader and then tried pushing the Philz recovery image to the device with the command line:
Code:
C:\android\sdk\android\platform-tools>fastboot boot philz_touch_6.57.8-m8.img
downloading 'boot.img'...
OKAY [ 1.541s]
booting...
OKAY [ 0.002s]
finished. total time: 1.547s
*edit*
Holding volume up + power for 10 seconds helped *whew*...
Anakha56 said:
Thank you for the reply .
To be honest I have not tried booting a custom recovery because I saw this in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=2701376
So I am not sure what to try to be honest. This toolkit: http://forum.xda-developers.com/showthread.php?p=51383278&highlight=ota#post51383278 mentions getting root without S-OFF but with a unlocked bootloader. So I am thinking that if I follow those steps, maybe when I get to the reboot phase I can execute a nandroid instead which might get me the files I want?
I won't bother with WWE then. I will rely on the dev's to give me the latest & greatest .
Click to expand...
Click to collapse
You don't need S-Off to root, just the unlocked bootloader, custom recovery, and superuser.
@xunholyx Thanks for the post . I am trying to get an image of my stock recovery file first, so I am trying to avoid flashing the custom recovery right now . BTW Does anyone know if TWRP makes a backup of the stock recovery before overwriting it like Philz does?
Anakha56 said:
@xunholyx Thanks for the post . I am trying to get an image of my stock recovery file first, so I am trying to avoid flashing the custom recovery right now . BTW Does anyone know if TWRP makes a backup of the stock recovery before overwriting it like Philz does?
Click to expand...
Click to collapse
http://www.handy-faq.de/forum/htc_o...resammlung_ruus_otas_backups.html#post2832635
oops sorry.. i see you already been their
your hboot 3.19 will prevent booting to recovery ... and no TWRP doesn't backup stock recovery
you just need to find the OTA.zip for your version it must be out their somewhere
@clsA I have the file
3.32.111.3 - TWRP
Click to expand...
Click to collapse
From that site but its recovery is TWRP. I am trying to grab the stock recovery currently on the device before going forward. When I unzip that file it has 6 items:
boot.emmc.win
boot.emmc.win.md5
system.ext4.win000
system.ext4.win000.md5
system.ext4.win001
system.ext4.win001.md5
Click to expand...
Click to collapse
I have downloaded the OTA that is ready for my phone but I had hit a snag. The file was corrupt, on redownload I have the small OTA but the recovery version number has incremented past mine, I don't know if it will be still useable with the ROM file from the link?
Anakha56 said:
@clsA I have the file
From that site but its recovery is TWRP. I am trying to grab the stock recovery currently on the device before going forward. When I unzip that file it has 6 items:
I have downloaded the OTA that is ready for my phone but I had hit a snag. The file was corrupt, on redownload I have the small OTA but the recovery version number has incremented past mine, I don't know if it will be still useable with the ROM file from the link?
Click to expand...
Click to collapse
it should work, recovery does not have to be exact just close
and the file you have doesn't include TWRP .. it was created with twrp ... big difference
Anakha56 said:
@clsA I have the file
From that site but its recovery is TWRP. I am trying to grab the stock recovery currently on the device before going forward. When I unzip that file it has 6 items:
I have downloaded the OTA that is ready for my phone but I had hit a snag. The file was corrupt, on redownload I have the small OTA but the recovery version number has incremented past mine, I don't know if it will be still useable with the ROM file from the link?
Click to expand...
Click to collapse
You can use any 3.32 based stock recovery for your phone. There are plenty of backups for that on this thread. No need to backup your own.
Thank you guys! That helps me a lot! Off I go to flash a custom recovery .
Hi,
i Restored my phone to the original stock Rom from my nandroid backup then flashed the recovery back and then locked the Bootloader.
once i booted into android i downloaded the OTA for Lollipop but when the phone reboots it starts the install but then goes to recovery and comes up with Installation aborted.
HTC One M8
Orange UK
S-on
I have attached some pictures of what happens and my bootloader.
any ideas on whats happening and how to solve it?
FIX: I downloaded the Update - transferred to PC - unpacked it - opened firmware - copied the Recovery.img to the phone.
I then unlocked the bootloader and flashed the recovery via fastboot . then did the update and all worked.
No need to relock bootloader!
Cheers
That's showing that you're trying to apply the Orange OTA to the unbranded EU model. The message tells you what it expects and what you have in it's place so your backup isn't right
EddyOS said:
That's showing that you're trying to apply the Orange OTA to the unbranded EU model. The message tells you what it expects and what you have in it's place so your backup isn't right
Click to expand...
Click to collapse
The Nandroid i have is the original os that was shiped with the phone after i flashed CWM i did a backup and that is what i restored.
You can't use EU recovery for Orange
After OTA downloaded, select install later.
Copy OTA zip from Internal Storage\Download folder to PC
Open OTA zip with 7-zip, open firmware.zip extract recovery.img
Use this recovery.img
ckpv5 said:
You can't use EU recovery for Orange
After OTA downloaded, select install later.
Copy OTA zip from Internal Storage\Download folder
Open OTA zip with 7-zip, open firmware.zip extract recovery.img
Use this recovery.img
Click to expand...
Click to collapse
Awesome ill try that.
Cheers
The other option is to use the recovery that you should be on from the previous OTA, which you can find here:
https://mega.co.nz/#!tVsiyQKZ!21FvMXKN1nxr83u-4dF7mNcXQ1RCWqkkZLA2q_tvKhg
(You'll have to extract it from the firmware.zip in the OTA file and flash it in fastboot)
EddyOS said:
The other option is to use the recovery that you should be on from the previous OTA, which you can find here:
https://mega.co.nz/#!tVsiyQKZ!21FvMXKN1nxr83u-4dF7mNcXQ1RCWqkkZLA2q_tvKhg
(You'll have to extract it from the firmware.zip in the OTA file and flash it in fastboot)
Click to expand...
Click to collapse
If the Previous comment doesn't work i will give this a try. thanks
Ill let you all know.
Good News flashing the Recovery form the Update file Worked.
I downloaded the Update - transferred to PC - unpacked it - opened firmware - copied the Recovery.img to the phone.
I then unlocked the bootloader and flashed the recovery via fastboot and then re locked the the bootloader. then did the update and all worked.
Thanks for the help
Skynet2Mainframe said:
Good News flashing the Recovery form the Update file Worked.
I downloaded the Update - transferred to PC - unpacked it - opened firmware - copied the Recovery.img to the phone.
I then unlocked the bootloader and flashed the recovery via fastboot and then re locked the the bootloader. then did the update and all worked.
Thanks for the help
Click to expand...
Click to collapse
Great :good::good:
For your info and others that reading this thread ... there is no need to relock bootloader when doing OTA ... leave it unlocked when it is already unlocked.
ckpv5 said:
Great :good::good:
For your info and others that reading this thread ... there is no need to relock bootloader when doing OTA ... leave it unlocked when it is already unlocked.
Click to expand...
Click to collapse
cool updated post.
Hi,
So here's the thing, I wanted to flash the cyanogenmod rom to my HTC One M8 using the TWRP 3.0.2.0. So I wiped the entire phone, including the internal storage and the system. Unfortunately, every time I tried flashing it I received this error:
Updater process ended with ERROR: 7.
Click to expand...
Click to collapse
So I was like ''Ok then I'll just flash a stock ROM'', but I couldn't find any that was matching my firmware since I'm stuck on FW 2.22.401.4 and I am S-ON so I can't flash any other firmware. I've searched literally everywhere and eventually ended up on a german (I think?) forum, and got to download a Nand stock rom (I don't even know the NAND stands for what tbh, but I guess it's the right one?) for my firmware, but now every time I try flashing it I get this error:
Could not find 'META-INF/com/google/android/update-binary' in the zip file.
Error installing zip file 'my file'
Click to expand...
Click to collapse
I've also heard that you could flash stock roms based on lower firmwares and it would work, but I still get the same error. So yeah, I'm kind of stuck with no OS and no way to flash one. I could really need some help right now.
Thank you!
Your low version firmware is the problem ... S-On doesn't stop you to flash firmware.
Post here fastboot getvar all without serial & imei no. then we'll see what you need.
There you go
https://postimg.org/image/7kyadqsif/
RafiKhalil said:
There you go
https://postimg.org/image/7kyadqsif/
Click to expand...
Click to collapse
Your firmware is 2.22.707.3 as shown in the getvar, not x.xx.161.x
You need to update your firmware to the latest in order to install most of the available custom ROMs. Your current firmware is not compatible.
You have 2 options :
1. Read all steps on post #1, restore 2.22.707.4 and 2.22.707.4 stock recovery then do OTA up to the latest 6.14.707.1
Here is the thread : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
2. Install RUU_M8_UL_L50_SENSE60_MR_hTC_Asia_WWE_4.19.707.2_Radio_1.25.21331147A1.06G_20.69.4196.01_F_release_414204_signed.exe then do OTA to the latest 6.14.707.1
To run RUU, you need : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
You also need to relock bootloader with commands
fastboot oem lock
fastboot reboot-bootloader
Note : this RUU procedure will wipe everything in your internal storage, make backup first of important files like musics, photos & etc.
You can get the RUU here : http://androidruu.com/?developer=M8
Hi there,
I had a quick question on my issue.
I found my appropriate file to flash and loaded it in the twrp-backup folder and flashed. Then used the hassoon2000 program to close the bootloader. I was already S-on. Used the program to close the bootloader. Now the bootloader says relocked in red. Rebooted and started up. Everything works great. I'm with Rogers and emmidiately it says an update is available. After I download it asks if I want to flash. It unzips and reboots to the bootloader. What is the next step? I'm also wondering why I'm in the bootloader. Shouldn't it just reboot and finish the upgrade?
I'm convinced there's an issue.
Is there something I should change.
I'm lost. Any help would be appreciated.
Being a tester for Viper as stated in your signature, you shouldn't make this silly mistake.
Don't relock bootloader .. not needed at all and a hassle for you to fix problems.
You need non-rooted backup & stock recovery to update.
Read how-to and files needed in my thread linked in my signature.
You need to unlock bootloader again to fix it.
Its been a year and a half since I tweaked anything on my phone. Viper has been solid but wanted to upgrade to marshmellow then install newer vipper. Anyways, thats just the back ground reasons.
If I open the bootloader ( I'll have to search for this step as I'm sure using the "open bootloader" option in Hassoon's program would require many more steps) the update would take me to recovery. I spent hours searching through folders trying to find the OTA to install with no luck.
Don't use tools...
1. Unlock bootloader with unlock_code bin that you should already have. If no, request again from htcdev
2. Install TWRP
3. Restore non-rooted nandroid backup for your current firmware.
What's your current firmware ?
4. Install current firmware stock recovery
5. Do OTA checking, download & install
You won't find the OTA file after you already tried to install it .. it will be removed by the system after you tried to update (and failed)
ckpv5 said:
Don't use tools...
1. Unlock bootloader with unlock_code bin that you should already have. If no, request again from htcdev
2. Install TWRP
3. Restore non-rooted nandroid backup for your current firmware.
What's your current firmware ?
4. Install current firmware stock recovery
5. Do OTA checking, download & install
You won't find the OTA file after you already tried to install it .. it will be removed by the system after you tried to update (and failed)
Click to expand...
Click to collapse
Again I apprecoate the insight into this. I did some reading and it looks like the tool kit hasn't been updated in a few years. I followed your link/page and went through the unlock with htcdev. It said successful and they were emailing me the code and further instructions. That was originally 12hrs ago. I redid it about 3hrs ago but again still waiting on the email( I did check the spam folder but still nothing.
As for previous firmware, I have:
CID Rogers_001
Version main(OS) 4.20.631.2
HBoot 3.19.0.0000
I was just thinking, maybe its a different token number each attempt. So again I redid the process. Now I wait. I've also looked at my account in the htcdev and it is correct. This is strange.
Sometime it happens the delay.
If I remember correctly, I have RUU for your current version. If there is, while waiting for the unlock_code.bin, you can run RUU for a fresh system and do OTA up to Marshmallow.
Then you can unlock bootloader to install your favorite ROM.
I'm already in bed, I'll check my hdisk tomorrow and upload for you
I assume your device is S-On, if it is S-Off you don't need the unlock code to unlock bootloader.
Am I right about the device is S-On. I hope I am wrong then it's easier to fix it.
ckpv5 said:
Sometime it happens the delay.
If I remember correctly, I have RUU for your current version. If there is, while waiting for the unlock_code.bin, you can run RUU for a fresh system and do OTA up to Marshmallow.
Then you can unlock bootloader to install your favorite ROM.
I'm already in bed, I'll check my hdisk tomorrow and upload for you
I assume your device is S-On, if it is S-Off you don't need the unlock code to unlock bootloader.
Am I right about the device is S-On. I hope I am wrong then it's easier to fix it.
Click to expand...
Click to collapse
You are correct as its still S-On. I had to redo my registration as my old account didn't have all the Capitals, hexadecimal stuff the latest user name/passwords require. but after that the email came through and I'm back to being unlocked. If you stumble on the RUU I'd very very thankful for the copy. In the meantime I'll look up the RUU and the install. chances are this is what your thread is all about.
Splitshot said:
I'm back to being unlocked. If you stumble on the RUU I'd very very thankful for the copy. In the meantime I'll look up the RUU and the install. chances are this is what your thread is all about.
Click to expand...
Click to collapse
No .. my thread is not about RUU but nandroid backup. You don't need the RUU when your target is to have Marshmallow firmware and install custom ROM ..
Now the bootloader is unlocked and you have the unlock_code, the fastest method for you is:
Restore directly Marshmallow nandroid 6.13.631.7 (instead of going for OTA) then relock bootloader and install 6.13.631.7 signed firmware.zip .. reboot.
After all setup done .. you can unlock bootloader, reboot .. after setup is completed, install latest TWRP and install your favorite custom ROM.
The usual method :
Restore 4.20.631.3 backup (yes, not 4.20.631.2 backup), install 4.20.631.3 stock recovery - reboot - setup - check OTA - download and install 6.13.631.7 OTA. Once completed, install latest TWRP and install your favorite custom ROM.
The usual method is better, no hassle of relocking and unlocking bootloader.
followed your procedures but after downloading the marshmallow update it unzips and reboots to the install part after about 1 minute it reboots to factory recovery. is there a step here? because I wiped twrp before restoring the 4.20.631.3 file I have no twrp( That's what I'm familiar with not this factory recovery).
Make sure you install either 4.20.631.3 or 6.13.631.7 stock recovery.
When it stops in recovery, there's an error log on why it stops.
But it never stops in recovery, if there is error, it will boot to bootloader or reboot back to system without installing update.
ckpv5 said:
Make sure you install either 4.20.631.3 or 6.13.631.7 stock recovery.
When it stops in recovery, there's an error log on why it stops.
But it never stops in recovery, if there is error, it will boot to bootloader or reboot back to system without installing update.
Click to expand...
Click to collapse
So if I reDL your 4.20.631.3 and place it back into twrp/backups/phone serial/ and get back into the factory recovery would I be able to restore from here? I don't remember there being a restore option only install.
Or is my only option now to reinstall twrp and go through the paces a 2nd time?
I asked you to 4.20.631.3 or 6.13.631.7 stock recovery, what it got to do with redownload 4.20.631.3 (which I believe you refer to nandroid backup)
Nandroid & stock recovery are two different thing.
There is no need to redo the process of restoring 4.20.631.3 nandroid (if it was done correctly) .. just make sure 4.20.631.3 or 6.13.631.7 stock recovery is installed, not any other version.
Reboot, check OTA, download and select install now. The system will boot to RUU mode to install the update .. it won't go to recovery (that's why I don't understand your above post saying it stop in recovery - no manual installation too)
Read the How-To all the 14 steps and tick what you have done so you'll know that you don't skip any step
ckpv5 said:
I asked you to 4.20.631.3 or 6.13.631.7 stock recovery, what it got to do with redownload 4.20.631.3 (which I believe you refer to nandroid backup)
Nandroid & stock recovery are two different thing.
There is no need to redo the process of restoring 4.20.631.3 nandroid (if it was done correctly) .. just make sure 4.20.631.3 or 6.13.631.7 stock recovery is installed, not any other version.
Reboot, check OTA, download and select install now. The system will boot to RUU mode to install the update .. it won't go to recovery (that's why I don't understand your above post saying it stop in recovery - no manual installation too)
Read the How-To all the 14 steps and tick what you have done so you'll know that you don't skip any step
Click to expand...
Click to collapse
I apologize as if never seen this screen before. My assumption was it's a stock android recovery. But I must admit I do not know.
Attached is the pic of what I'm talking about.
https://drive.google.com/file/d/0B--VfMbsbBNCMEl6X3UyN3NIdGtXS29kRmE1R0tiaWdjVm9n/view?usp=sharing
Yeah ... that's stock recovery with error log ...
It says the system expect stock recovery 4.20.631.3 (463267.3) or 6.13.631.7 (667457.7) is installed for it to proceed the update, but the device has wrong stock recovery image 4.20.631.2 (463267.2) installed so it stops the installation (Status 7)
As I said above, no need to redo the nandroid restore process. Just install recovery image 4.20.631.3 or 6.13.631.7 then redo the OTA checking, download and install.
Note : I believe you followed the instruction written on post #9. There was a typo on recovery version that I edited an hour after posting it yesterday.
That's why you got this error ... sorry for that.
ckpv5 said:
Yeah ... that's stock recovery with error log ...
It says the system expect stock recovery 4.20.631.3 (463267.3) or 6.13.631.7 (667457.7) is installed for it to proceed the update, but the device has wrong stock recovery image 4.20.631.2 (463267.2) installed so it stops the installation (Status 7)
As I said above, no need to redo the nandroid restore process. Just install recovery image 4.20.631.3 or 6.13.631.7 then redo the OTA checking, download and install.
Note : I believe you followed the instruction written on post #9. There was a typo on recovery version that I edited an hour after posting it yesterday.
That's why you got this error ... sorry for that.
Click to expand...
Click to collapse
no worries. I have been feeling like a jerk for not following what your saying. I never wanted to frustrate you like this.
Last quick question before I stress over this. My next steps are:
DL your 6.13.631.7
Install in twrp/backups / 6.13.631.7
reboot
DL the OTA
install.
I'm just not sure about where to put the 6.13.631.7 file?
I think you still confused with nandroid & stock recovery.
There is no need to download 6.13.631.7 nandroid and no need to put it in twrp/backups
You just need to download the stock recovery image. Let's forget about 6.13.631.7 for now ...
1. download stock recovery image 4.20.631.3 - https://mega.nz/#!TdZg1aID!einylYid2QmN8OoxehNcnTrh6iijFqJ2-klrRsb-5MI
2. Put your device on bootloader/fastboot mode and install stock recovery image 4.20.631.3
fastboot flash recovery 4.20.631.3_recovery.img
3. reboot, check OTA, download OTA, select install now and let the system do it stuff.
4. Once completed, it will reboot and greet you with new Marshmallow 6.13.631.7 ROM.
5. Put your device on bootloader/fastboot mode and install latest TWRP
6. install your custom ROM .... done
ckpv5 said:
I think you still confused with nandroid & stock recovery.
There is no need to download 6.13.631.7 nandroid and no need to put it in twrp/backups
You just need to download the stock recovery image. Let's forget about 6.13.631.7 for now ...
1. download stock recovery image 4.20.631.3 - https://mega.nz/#!TdZg1aID!einylYid2QmN8OoxehNcnTrh6iijFqJ2-klrRsb-5MI
2. Put your device on bootloader/fastboot mode and install stock recovery image 4.20.631.3
fastboot flash recovery 4.20.631.3_recovery.img
3. reboot, check OTA, download OTA, select install now and let the system do it stuff.
4. Once completed, it will reboot and greet you with new Marshmallow 6.13.631.7 ROM.
5. Put your device on bootloader/fastboot mode and install latest TWRP
6. install your custom ROM .... done
Click to expand...
Click to collapse
I really don't know whats happened to all my knowledge and abilities. It's like my frustrations have literally taken over.
I was able to push the recovery image to the phone. rebooted and am now DL'ing the update.
for the last little while I've downloaded twrp but have yet to succeed on pushing it to the phone. I've downloaded the latest file, changed the name to twrp.img and used this while in bootloader/fastboot mode.
fastboot flash recovery twrp.img
error cannot load "twrp.img"
At the end of the day today I was able to install your nandroid file, upgrade to marshmallow, install the latest TWRP and about to flash a marshmallow ROM. I cannot thank you enough for all your insight, patience and help with this. You truly have an amazing talent. It is amazing the support you find on XDA and your name should be at the top of that list.
The official step http://www.htcdev.com/bootloader