Hi guys!
My HTC one M9 was rooted, running Android 5.0.2 and i had Twrp recovery set up.
Since i was S-On and i'm a total noob/asshat i never tried to load any rom or mods onto my system =)
Now i wanted to try and get back to stock, so i could receive OTA updates, and after getting Nougat (even if i had to wait a long time for it), then i'd just root again and enjoy the lack of bloatware.
In this order i:
-Unrooted through the SuperSu
-Checked to see if it was unrooted using rootchecker
-Found my stock recovery mode here: http://forum.xda-developers.com/one...collection-t3132698/post61286815#post61286815
-Went to ADB, opened the command prompt
-Went to download mode
-entered fastboot flash recovery HIMA_UHL_Stock_Recovery_1.32.401.15.img
From there, i took my phone and on the phone itself tried to go to recovery mode to check..
The screen went black, it went to (the stock!!!) recovery mode, but now the system can't reboot.
I've seen the same question asked, but not for S-On phone or done in about the same way i did..
My info:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 1.32.401.15
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__031
There are recovery logs on my phone but they are very long and i honestly don't know how or if i can retrieve them through ADB, if any of you should think it necessary and can tell me what command to put in, i'll bring them up right away!
thanks alot for your time, i'm very sorry to bother you with this
Edit: after encountering the issue, i tried wiping the cache partition and factory reset options but to no avail.
flashed twrp recovery back in, no change.
So, you found the correct stock recovery in my thread and didn't read the warning above the download links? Since I'm currently revamping the thread, it would be nice if you could tell me why you didn't read it. Was it to small? Was the colour unreadable? (This is a serious question. I'm not making fun of you. I really need to know that for being able to improve the thread.)
Flash a 401 RUU. Instructions and download links can be found in the same thread.
Sent from my HTC One M9 using XDA Labs
*made mistake, please ignore*
Flippy498 said:
So, you found the correct stock recovery in my thread and didn't read the warning above the download links? Since I'm currently revamping the thread, it would be nice if you could tell me why you didn't read it. Was it to small? Was the colour unreadable? (This is a serious question. I'm not making fun of you. I really need to know that for being able to improve the thread.)
Flash a 401 RUU. Instructions and download links can be found in the same thread.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Sorry man.
You can see from the time it was between 3 and 4 AM =D
I read all your info, i just read it all again, but for some reason i didn't pay attention to
"Read the Backup or the RUU tab of my google sheet if you want to be able to receive and install OTAs, again.
Simply unrooting your device and reflashing the Stock Recovery is not enough due to the block-based OTAs."
I honestly have no *cursing* idea why that didn't register in my brain.
My apologies in any case. Your thread is fine, it's the most helpful i've come across for my phone in days.
I never flashed anything before, and i knew absolutely **** (not that i know alot right now =D but at least i'm learning). Without your thread, i'd probably still be looking.
i flashed the stock recovery (HIMA_UHL_Stock_Recovery_1.32.401.15) back on, got 1.32.401.15 Ruu from your thread
unfortunatly i don't have an SD card.
I tried flashing from platform tools the 0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_426891_signed.zip file
but got this message:
C:\Users\pc\Desktop\platform-tools>fastboot flash zip 0PJAIMG_HIMA_UHL_L50_SENSE
70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_4268
91_signed.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2189252987 is not a multiple of
the block size 4096
sending sparse 'zip' (0 KB)...
error: write_sparse_skip_chunk: don't care size 2189252987 is not a multiple of
the block size 4096
error: write_sparse_skip_chunk: don't care size 2189252987 is not a multiple of
the block size 4096
OKAY [ 1.053s]
writing 'zip'...
(bootloader) HOSD CL#506785
FAILED (remote: 9: SD_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 2.076s
i think the guy here http://forum.xda-developers.com/one-m9/help/urgent-help-bricked-htc-one-m9-t3138987
had the same issue so i'm trying to solve from here, and if not i'll go out and buy an SD card, though i don't know if that'll work, my computer doesn't see my phone at the moment
As written in my thread you can't flash M9 RUUs with fastboot. You need HTC_fastboot.
Sent from my HTC One S using XDA Labs
Flippy498 said:
As written in my thread you can't flash M9 RUUs with fastboot. You need HTC_fastboot.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
So i tried, i changed adb fastboot to the htc_fastboot.exe and now i get this:
C:\Users\pc\Desktop\platform-tools>htc_fastboot flash zip 0PJAIMG_HIMA_UHL_L50_S
ENSE70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_
426891_signed.zip
sending 'zip'... (101066 KB) OKAY
sending time = 7.986 secs
writing 'zip'... (bootloader) HOSD CL#506785
FAIL9: SD_SECURITY_FAIL zip from usb command in download mode
FAILED (remote: 9: SD_SECURITY_FAIL zip from usb command in download mode)
Execution time is 9(s)
Okay! edit: i'm an idiot. i put things back in order, downloaded htc_fastboot from here: http://d-h.st/6LC (thanks brandon gunderson) and tried again.
Unfortunatly now i get this:
C:\Users\pc\Desktop\htc_fastboot>htc_fastboot flash zip 0PJAIMG_HIMA_UHL_L50_SEN
SE70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_42
6891_signed.zip
htc_fastboot wordt niet herkend als een interne
of externe opdracht, programma of batchbestand.
(it means: htc_fastboot is not recognized as an internal or external command, program or batch file)
still an idiot. No idea what's wrong
you said in the thread:
Important Notes:
I won't support flashing RUU.exe files or flashing RUU.zip files via HTC_fastboot in this thread. There have been too many reports of people having problems with these methods. Trying to find the reason for the problems can be quite frustrating and time-consuming. The SD card method on the other hand is much easier and less time-consuming than searching for user errors if the other methods fail.
If you only have a RUU.exe at hand you can extract the *.zip file using these instructions. Although they're a bit older they can still be used with M9 RUUs.
so i went to that other thread to find out how i could do it
Yeah, I wrote that part because of all the problems that arise most of the times if people try to flash RUUs via fastboot and all the risks that are connected with this method. As you can see your try isn't an exception.
The bootloader needs to be locked or re-locked if you use the HTC_fastboot method. However, I don't recommend doing so if you aren't 100% sure that you can flash the RUU without any issues afterwards. If your phone isn't completely stock your phone won't boot anymore after it got (re-)locked. That is a security feature that prevents the phone from getting bricked if anything is modified. You can't even enter TWRP, anymore, in that situation if it's installed. In addition it's impossible to re-unlock the bootloader if your phone is S-ON and the option "OEM Unlock" isn't activated in the developer options. (Sidenote: The option got introduced with firmware 2.x. So in your current situation re-locking is safe. However, as soon as you updated your phone to a higher firmware version you shouldn't do it unless you know that you have a working RUU at hand and you know that you are able to flash it.)
Flippy498 said:
Yeah, I wrote that part because of all the problems that arise most of the times if people try to flash RUUs via fastboot and all the risks that are connected with this method. As you can see your try isn't an exception.
The bootloader needs to be locked or re-locked if you use the HTC_fastboot method. However, I don't recommend doing so if you aren't 100% sure that you can flash the RUU without any issues afterwards. If your phone isn't completely stock your phone won't boot anymore after it got (re-)locked. That is a security feature that prevents the phone from getting bricked if anything is modified. You can't even enter TWRP, anymore, in that situation if it's installed. In addition it's impossible to re-unlock the bootloader if your phone is S-ON and the option "OEM Unlock" isn't activated in the developer options. (Sidenote: The option got introduced with firmware 2.x. So in your current situation re-locking is safe. However, as soon as you updated your phone to a higher firmware version you shouldn't do it unless you know that you have a working RUU at hand and you know that you are able to flash it.)
Click to expand...
Click to collapse
thank you very much man.
i know questions like this must annoy you, and i'm very sorry for bothering you. I'm learning though =)
At this point, after the failed attempts to flash, is it still possible for me to use an SD card? If so i'm going to get one right away.
My worry is, though, that since my phone doesn't register on my computer, how i'll get the file on the SD card... I'm thinking i'll pass by a friend, put it in his phone, load the file on the SD card, put the card in my phone again, change recovery back to twrp and try to flash from there?
Please read the instructions for the SD card method. Chances are high that it's not possible to copy the RUU onto the SD card while it's put into the phone. You probably need a SD card reader.
The SD card method is completely independent of the fastboot method. And as long as the fastboot method fails completely (as in your situation) chances are high that you can still recover your phone with the other method.
Sent from my HTC One S using XDA Labs
Flippy498 said:
Please read the instructions for the SD card method. Chances are high that it's not possible to copy the RUU onto the SD card while it's put into the phone. You probably need a SD card reader.
The SD card method is completely independent of the fastboot method. And as long as the fastboot method fails completely (as in your situation) chances are high that you can still recover your phone with the other method.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
things aren't going well for me today.
I have an SD adapter for micro SD that i can plug into my laptop. I renamed the Ruu zipfile "0PJAIMG.zip", that is the name (in the name i included .zip, that's supposed to be like that, no?)
I put off my phone, put the card in, rebooted to download mode.... Nothing.
tried to boot, it failed (of course), then i got the following menu:
Reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
apply from phone storage
apply from sd card
i tried the "apply from sd card" option but it says:
fail to open file: /sys/devices/platform/android_usb/host mode
Wrtie host_mode error
handle_cota_install: Can't mount /sdcard, 1 times
handle_cota_install: Can't mount /sdcard, 2 times
handle_cota_install: Can't mount /sdcard, 3 times
handle_cota_install: Can't mount /sdcard, 4 times
handle_cota_install: Can't mount /sdcard, 5 times
E: Find no match PARTITION for package path /sdcard/ptt.zip
E: unknown volume for path
E: Can't mount
E: failed to open last_install: No such file or directory
Finding update package....
Opening update package...
E: failed to map file
i tried flasing from the twrp recovery (install, from SD card-. Received the following:
Updating partition details....
.... done
Full SELinux support is present.
Installing '/external_sd/0PJAIMG.zip.zip"...
Checking for MD5 file....
Skipping MD5 check: no MD5 file found
Verifying zip signature...
E: Zip signature verification failed: 1
Error flashing zip '/external_sd/0PJAIMG.zip.zip'
Updating partition details...
... done
FAILED
the SD card is a 32GB Samsung SD card (MB-MC32D model), and it's FAT32
any idea what went wrong? (also, i seem to have hit my max "thank you!" 's i can give out today, i'll be sure to thank any replies that are left tomorrow!)
Fatimiyye said:
things aren't going well for me today.
I have an SD adapter for micro SD that i can plug into my laptop. I renamed the Ruu zipfile "0PJAIMG.zip", that is the name (in the name i included .zip, that's supposed to be like that, no?)
I put off my phone, put the card in, rebooted to download mode.... Nothing.
tried to boot, it failed (of course), then i got the following menu:
Reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
apply from phone storage
apply from sd card
i tried the "apply from sd card" option but it says:
fail to open file: /sys/devices/platform/android_usb/host mode
Wrtie host_mode error
handle_cota_install: Can't mount /sdcard, 1 times
handle_cota_install: Can't mount /sdcard, 2 times
handle_cota_install: Can't mount /sdcard, 3 times
handle_cota_install: Can't mount /sdcard, 4 times
handle_cota_install: Can't mount /sdcard, 5 times
E: Find no match PARTITION for package path /sdcard/ptt.zip
E: unknown volume for path
E: Can't mount
E: failed to open last_install: No such file or directory
Finding update package....
Opening update package...
E: failed to map file
i tried flasing from the twrp recovery (install, from SD card-. Received the following:
Updating partition details....
.... done
Full SELinux support is present.
Installing '/external_sd/0PJAIMG.zip.zip"...
Checking for MD5 file....
Skipping MD5 check: no MD5 file found
Verifying zip signature...
E: Zip signature verification failed: 1
Error flashing zip '/external_sd/0PJAIMG.zip.zip'
Updating partition details...
... done
FAILED
the SD card is a 32GB Samsung SD card (MB-MC32D model), and it's FAT32
any idea what went wrong? (also, i seem to have hit my max "thank you!" 's i can give out today, i'll be sure to thank any replies that are left tomorrow!)
Click to expand...
Click to collapse
so yeah. I'm an idiot. thought i wasn't, but i am.
named it 0PJAIMG without the '.zip' at the back and worked fine. Hope i can install OTA's now
Fatimiyye said:
so yeah. I'm an idiot. thought i wasn't, but i am.
named it 0PJAIMG without the '.zip' at the back and worked fine. Hope i can install OTA's now
Click to expand...
Click to collapse
Yes, OTAs shouldn't be a problem now.
Well, we all make mistakes. You live and learn.
Flippy498 said:
Yes, OTAs shouldn't be a problem now.
Well, we all make mistakes. You live and learn.
Click to expand...
Click to collapse
Thank you very much for your help man =)
The whole thing is stock now, took hours to update it all but i'm on the latest update available here for marshmallow, so i'm quite pleased.
from what i've gathered it's not possible for me to flash Nougat without S-OFF so i'll very likely keep notes on how i did this, and either wait for nougat before re-rooting, or get S-OFF and hurt my (and maybe your) head again trying to get my phone the way i want it xD
cheers man! <3
Related
I've read around on the forums here and other places but some of it doesn't make any sense to me and I watched a YouTube video about unlocking the bootloader then rooting the phone unfortunately i didn't do a nandroid back up before rooting (using supersu) and i am wondering if it is possible to flash to a stock rom so that in the future i can ota update in the future.
here is what i have at the moment
international phone (im on o2 in the uk anyway)
android version: 5.0.2
Software number: 1.32.401.15
unlocked bootloader
rooted
s-off
SuperCID
Also if someone can guide me through this i would be extremely thankful.
Thanks for your help guys.
You would need to either get a nandroid of your particular carriers ROM, or download the correct RUU from HTC.
BillTheCat said:
You would need to either get a nandroid of your particular carriers ROM, or download the correct RUU from HTC.
Click to expand...
Click to collapse
as far as i know there are these 2 RUUs which are the same version as mine
androidruu.com/getdownload.php?file=M9/0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_426891_signed.zip
androidfilehost.com/?fid=96039337900114679
are these fine to flash to my device?
linton85 said:
as far as i know there are these 2 RUUs which are the same version as mine
androidruu.com/getdownload.php?file=M9/0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_426891_signed.zip
androidfilehost.com/?fid=96039337900114679
are these fine to flash to my device?
Click to expand...
Click to collapse
I have no idea, since you haven't told us what version your phone is. I think you ought to wait for feedback from someone else who can advise you better.
linton85 said:
as far as i know there are these 2 RUUs which are the same version as mine
androidruu.com/getdownload.php?file=M9/0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_426891_signed.zip
androidfilehost.com/?fid=96039337900114679
are these fine to flash to my device?
Click to expand...
Click to collapse
Yes your s-off you can use those RUU
hmm i cant seem to use them, i go to flash it then i get this;
Code:
C:\Users\Jack\Desktop\HTC ROOT + UNLOCK\platform-tools>fastboot oem rebootRUU
...
OKAY [ 0.020s]
finished. total time: 0.021s
C:\Users\Jack\Desktop\HTC ROOT + UNLOCK\platform-tools>fastboot flash zip 0PJAIM
G.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (88044 KB)...
OKAY [ 6.331s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22: fail to flash via downloadzip)
finished. total time: 8.430s
any idea?
linton85 said:
hmm i cant seem to use them, i go to flash it then i get this;
Code:
C:\Users\Jack\Desktop\HTC ROOT + UNLOCK\platform-tools>fastboot oem rebootRUU
...
OKAY [ 0.020s]
finished. total time: 0.021s
C:\Users\Jack\Desktop\HTC ROOT + UNLOCK\platform-tools>fastboot flash zip 0PJAIM
G.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (88044 KB)...
OKAY [ 6.331s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22: fail to flash via downloadzip)
finished. total time: 8.430s
any idea?
Click to expand...
Click to collapse
your using the wrong fastboot
you need htc_fastboot >> https://www.androidfilehost.com/?fid=96039337900114016
it's also easy to rename the RUU.zip to 0PJAIMG.ZIP, place it on a ext sd card formatted in FAT32 (a 16 or 32gig one should work), reboot into DOWNLOAD_MODE, agree and it should flash.
it's also easy to rename the RUU.zip to 0PJAIMG.ZIP, place it on a ext sd card formatted in FAT32 (a 16 or 32gig one should work), reboot into DOWNLOAD_MODE, agree and it should flash.
Click to expand...
Click to collapse
ok managed to flash it back successfully couple of things though:
i couldnt copy the file when it was named 0JAIMPG.ZIP to the sd card (was in the phone not sure if i had to take it out and put it on)
it still says "software status modified" "unlocked" "s-off" afaik you can't get software status back to normal, to get unlocked back to locked would mean me relocking the bootloader and s-off shouldnt matter with ota update?
if i was to now re-install twrp but before rooting i took a nandroid backup would this allow me to get ota updates if i then restore to that after rooting or would one of the things above prevent me?
if not is there anyway i can get ota updates again?
linton85 said:
ok managed to flash it back successfully couple of things though:
i couldnt copy the file when it was named 0JAIMPG.ZIP to the sd card (was in the phone not sure if i had to take it out and put it on)
it still says "software status modified" "unlocked" "s-off" afaik you can't get software status back to normal, to get unlocked back to locked would mean me relocking the bootloader and s-off shouldnt matter with ota update?
if i was to now re-install twrp but before rooting i took a nandroid backup would this allow me to get ota updates if i then restore to that after rooting or would one of the things above prevent me?
if not is there anyway i can get ota updates again?
Click to expand...
Click to collapse
If you used the htc_fastboot to flash it will not reset the modified tag
you have to do it yourself >> http://forum.xda-developers.com/one-m9/general/how-to-restore-software-status-original-t3092882
To set unlocked to locked you have to do this >> http://forum.xda-developers.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036
and yes, you can get OTA update with unlocked and s-off
Thank you so much for taking the time to help me out and providing links I am very grateful
clsA said:
your using the wrong fastboot
you need htc_fastboot >> https://www.androidfilehost.com/?fid=96039337900114016
it's also easy to rename the RUU.zip to 0PJAIMG.ZIP, place it on a ext sd card formatted in FAT32 (a 16 or 32gig one should work), reboot into DOWNLOAD_MODE, agree and it should flash.
Click to expand...
Click to collapse
Do I rename this file to fastboot.exe and delete the original fastboot?
I seem to always get the 90 pre-update FAIL when I flash different firmware.
bigp951 said:
Do I rename this file to fastboot.exe and delete the original fastboot?
I seem to always get the 90 pre-update FAIL when I flash different firmware.
Click to expand...
Click to collapse
Just leave it as htc_fastboot. They can coexist.
Dude, what's it tell you after you get the error 90? Flash again immediately, right? EVERYONE gets error 90 when flashing firmware. It's a pre-check before actually doing anything. If you're phone reboots to OS after getting 90, then just leave your command/terminal window open and put your phone back in download mode and re-run the exact same command to start the flash again.
jollywhitefoot said:
Just leave it as htc_fastboot. They can coexist.
Dude, what's it tell you after you get the error 90? Flash again immediately, right? EVERYONE gets error 90 when flashing firmware. It's a pre-check before actually doing anything. If you're phone reboots to OS after getting 90, then just leave your command/terminal window open and put your phone back in download mode and re-run the exact same command to start the flash again.
Click to expand...
Click to collapse
That's what I have been doing.... Did not know EVERYONE gets that error. Thanks for the info though. From what I read elsewhere is that the htc_fastboot will reboot back into download mode instead of os. That's why I mentioned it.
bigp951 said:
That's what I have been doing.... Did not know EVERYONE gets that error. Thanks for the info though. From what I read elsewhere is that the htc_fastboot will reboot back into download mode instead of os. That's why I mentioned it.
Click to expand...
Click to collapse
No problem bro. I think I've gotten reboots to is using HTC_fastboot, too.
clsA said:
your using the wrong fastboot
you need htc_fastboot >> https://www.androidfilehost.com/?fid=96039337900114016
it's also easy to rename the RUU.zip to 0PJAIMG.ZIP, place it on a ext sd card formatted in FAT32 (a 16 or 32gig one should work), reboot into DOWNLOAD_MODE, agree and it should flash.
Click to expand...
Click to collapse
Sir After installing 5.1 update my phone got stuck at boot screen.
Now I am unable to boot into recovery. Also locked My bootloader accidentally. While trying to flash a zip through fastboot I am getting below error. Could you please help me out.
OTA_HIMA_UHL_L50_SENSE70_hTC_Asia_HK_1.40.708.9-1.32.708.15_R1_release_436199
amit_coolcampus said:
Sir After installing 5.1 update my phone got stuck at boot screen.
Now I am unable to boot into recovery. Also locked My bootloader accidentally. While trying to flash a zip through fastboot I am getting below error. Could you please help me out.
OTA_HIMA_UHL_L50_SENSE70_hTC_Asia_HK_1.40.708.9-1.32.708.15_R1_release_436199
Click to expand...
Click to collapse
I'm sorry to tell you but if you updated to 5.1 and did not go into developer options and check to allow bootloader unlock, and then locked your bootloader theirs is nothing you can do but flash a RUU. Are you s-off ? If no your most likely stuck.
I have no idea what the file name you posted above is for... Edit: This may be the help you need >> https://www.androidfilehost.com/?fid=24052804347810886
Sir I am S-On. I am trying to flash a RUU but getting error everytime. Tried from SD card. tried via fastboot.
Also my M9 is HTC Asia (Hongkong). So I have tried flashing below one. Can I try flashing TW version given by you??
https://www.androidfilehost.com/?fid=24269982087001508
clsA said:
I'm sorry to tell you but if you updated to 5.1 and did not go into developer options and check to allow bootloader unlock, and then locked your bootloader theirs is nothing you can do but flash a RUU. Are you s-off ? If no your most likely stuck.
I have no idea what the file name you posted above is for... Edit: This may be the help you need >> https://www.androidfilehost.com/?fid=24052804347810886
Click to expand...
Click to collapse
amit_coolcampus said:
Sir I am S-On. I am trying to flash a RUU but getting error everytime. Tried from SD card. tried via fastboot.
Also my M9 is HTC Asia (Hongkong). So I have tried flashing below one. Can I try flashing TW version given by you??
https://www.androidfilehost.com/?fid=24269982087001508
Click to expand...
Click to collapse
With S-ON it's not possible to downgrade or to flash RUUs that were made for other SKUs (Taiwan is 709 and Hongkong is 708). Since you can't use the RUU in my AFH folder because it's older than your actual firmware and there is no other RUU for the SKU 708 (or at least none I know) than that one you linked your only hope might be the RUU service on llabtoofer's website.
Edit @clsA: That file amit_coolcampus mentioned earlier is one of the OTAs for the Hongkong version of the M9.
Flippy498 said:
With S-ON it's not possible to downgrade or to flash RUUs that were made for other SKUs (Taiwan is 709 and Hongkong is 708). Since you can't use the RUU in my AFH folder because it's older than your actual firmware and there is no other RUU for the SKU 708 (or at least none I know) than that one you linked your only hope might be the RUU service on llabtoofer's website.
Edit @clsA: That file amit_coolcampus mentioned earlier is one of the OTAs for the Hongkong version of the M9.
Click to expand...
Click to collapse
Thanks Sir. Can I get this repaired if i visit HTC service center? Will they be having 2.11.708.30 RUU?
amit_coolcampus said:
Thanks Sir. Can I get this repaired if i visit HTC service center? Will they be having 2.11.708.30 RUU?
Click to expand...
Click to collapse
Honestly, I don't know. I've always been able to recover my phones without the help of the HTC service center or the RUU service. My guess is that the RUU service might be cheaper but that's only a guess. Maybe someone else here had to use one or both of these services and can share his/her experience...
Hi I need some help returning to stock with a RUU.
My phone is currently S-off, rooted, twrp and supercid. I am trying to return to stock (keeping s-off and supercid). From reading posts it seemed like a simple task but I cant get it to work. I have tried two different RUU's. I have tried putting a RUU on my extsd and renamed it to 0PJAIMG.zip but nothing happens in download and it actually says SD NOT MOUNTED down the bottom left.
The other method I have tried is through ADB using these commands.
fastboot oem rebootRUU
fastboot flash zip 0PJAIMG.ZIP
fastboot oem rebootRUU puts it into a screen with the htc logo
fastboot flash zip 0PJAIMG.ZIP gives me the following message
C:\platform-toolsM9>fastboot flash zip 0PJAIMG.ZIP
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (96760 KB)...
OKAY [ 7.557s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22: fail to flash via downloadzip)
finished. total time: 9.673s
Does anyone have any ideas?
Ok I used htc_fastboot and that has worked.
Stock RUU
Hi, I recently unlocked the bootloader and installed TWRP. Since then I have done a backup and installed Android Revolution rom. No my phone continuously turns off and restarts.
I really want to return to stock but can only find limited information. I have a TWRP backup of the stock ROM but when I try to flash it in recovery I get "cannot restore system--mounted read only" Apparently the backup has to be flashed with fastboot however the instructions are a bit dodgy at the android soul
I have the backup copied onto C drive yet it's not in "system.emmc.win format" its " 2015-06-09--04-46-13_LRX22G_release-keys". This folder of course has a few files in it, such as
boot.emmc.win
boot.emmc.win.md5
data.ext4.win000
system.ext4.win000
system.ext4.winooo.md5
I tried looking for the right RUU but couldn't find any for Australia let alone Vodafone Australia. Can I use the UK one?
If anyone has any ideas or advice I'd be most grateful.
I'm really disappointed in how difficult this phone is to root/unlock and restore. I hate it. I hate HTC.
There's one for vodafone australia on Androidruu it's 1.32.710.16. It's actually really easy to return to stock once you know how. Have a look in other threads and use the sd card method. Just make sure its formatted the correct way.
Soopajoosee said:
Hi, I recently unlocked the bootloader and installed TWRP. Since then I have done a backup and installed Android Revolution rom. No my phone continuously turns off and restarts.
If anyone has any ideas or advice I'd be most grateful.
I'm really disappointed in how difficult this phone is to root/unlock and restore. I hate it. I hate HTC.
Click to expand...
Click to collapse
Please don't blame HTC for your failure to read. You're describing a well-known conflict that results from running a 1.40 Rom on top of 1.32 firmware. There is a simple solution: Flash a 1.32 kernel or update your firmware.
And I don't understand your complaints about this being a difficult phone to mod. Compared to anything but a Nexus, it's a piece of cake.
iElvis said:
Please don't blame HTC for your failure to read. You're describing a well-known conflict that results from running a 1.40 Rom on top of 1.32 firmware. There is a simple solution: Flash a 1.32 kernel or update your firmware.
And I don't understand your complaints about this being a difficult phone to mod. Compared to anything but a Nexus, it's a piece of cake.
Click to expand...
Click to collapse
Thanks for your help not....I don't understand why you're a condescending prick. Don't worry, I flashed another rom and all is good. Personally I found the galaxy S2 and S4 a lot easier than this. I thought this was a forum for help....if this is your idea of help, don't bother in future.
Soopajoosee said:
Thanks for your help not....I don't understand why you're a condescending prick. Don't worry, I flashed another rom and all is good. Personally I found the galaxy S2 and S4 a lot easier than this. I thought this was a forum for help....if this is your idea of help, don't bother in future.
Click to expand...
Click to collapse
There's no need for the name calling. He was trying to help even though it could of been more eloquently put.
Sent from my 0PJA10 using Tapatalk
matust said:
There's no need for the name calling. He was trying to help even though it could of been more eloquently put.
Click to expand...
Click to collapse
Well, I was a condescending prick, but this is also a common problem. If you try to run the latest ARHD over 1.32 firmware, you will get random reboots because there is a conflict between the old firmware and 1.40 kernels.
iElvis said:
Well, I was a condescending prick, but this is also a common problem. If you try to run the latest ARHD over 1.32 firmware, you will get random reboots because there is a conflict between the old firmware and 1.40 kernels.
Click to expand...
Click to collapse
I just don't see a reason for name calling. I didn't read what you wrote as rude. What you were saying is correct even though it could of been put better. XDA isn't a place for name calling.
Sent from my 0PJA10 using Tapatalk
I have exactly the same problem. I can't return stock by putting file 0PJAIMG in the microsd and start in download mode and also I can't flash in fastboot. The messages are the same that report Matust. He said solved using HTC_fast boot but I don't how to use it
Cid and model id are correctly and I tried different ruu
jacopo.kaldewey said:
I have exactly the same problem. I can't return stock by putting file 0PJAIMG in the microsd and start in download mode and also I can't flash in fastboot. The messages are the same that report Matust. He said solved using HTC_fast boot but I don't how to use it
Cid and model id are correctly and I tried different ruu
Click to expand...
Click to collapse
If you use sd card method the card needs to formatted to fat32 and make sure the file name has .zip at the end. If your using the adb method download https://www.androidfilehost.com/?fid=96042739161891970 and put it in your adb folder. Use htc_fastboot as the command instead of fastboot to flash the file.
Sent from my HTC One M9 using Tapatalk
jacopo.kaldewey said:
I have exactly the same problem. I can't return stock by putting file 0PJAIMG in the microsd and start in download mode and also I can't flash in fastboot. The messages are the same that report Matust. He said solved using HTC_fast boot but I don't how to use it
Cid and model id are correctly and I tried different ruu
Click to expand...
Click to collapse
here is a link with a link to the htc_fastboot file. Just download it and place it in the same folder as your regular fastboot file.
http://forum.xda-developers.com/showpost.php?p=60346126&postcount=14
jollywhitefoot said:
here is a link with a link to the htc_fastboot file. Just download it and place it in the same folder as your regular fastboot file.
http://forum.xda-developers.com/showpost.php?p=60346126&postcount=14
Click to expand...
Click to collapse
thank you very much for Your help. I solved this problem and flash the RUU with htc_fastboot, but Sorry now I have a new problem. I made some mistake becouse my M9 now became e developer edition and I dont'know how to come back... also my english is bad and I've difficult to understand the thread that i search. Somebody can Help me to come back from developer edition to Europe edition?
my m9 randomly rebooted, and now its stuck in a bootloop, i'm able to get out of it and into download, and from there into twrp and the bootloader, but whenever i try to flash any of the Europe RUU's i get multiple errors
I am -
unlocked, but cant relock for some reason
s-on
have the latest 1.40.401.8 software
have twrp, but cant wipe data or do anything in it, just says failed to mount for data, cache etc
trying to reflash 1.40.401.8
i tried -
htc_fastboot flash zip (zip name).zip but results in the fail90 with please flush immediately text, it just repeats this oer an over with no other result even if i leave it for a while
fastboot oem lock just says failed, too many links and reboots
fastboot flash recovery recovery.img, stock recovery, says its succeeded but it still boots twrp
fastboot boot reocvery .img says booting but does nothing
tried to flash a different ruu but just says zip read error, cant open the zip
-
thanks in advance for you help, much appreciated
eggyfish said:
my m9 randomly rebooted, and now its stuck in a bootloop, i'm able to get out of it and into download, and from there into twrp and the bootloader, but whenever i try to flash any of the Europe RUU's i get multiple errors
I am -
unlocked, but cant relock for some reason
s-on
have the latest 1.40.401.8 software
have twrp, but cant wipe data or do anything in it, just says failed to mount for data, cache etc
trying to reflash 1.40.401.8
i tried -
htc_fastboot flash zip (zip name).zip but results in the fail90 with please flush immediately text, it just repeats this oer an over with no other result even if i leave it for a while
fastboot oem lock just says failed, too many links and reboots
fastboot flash recovery recovery.img, stock recovery, says its succeeded but it still boots twrp
fastboot boot reocvery .img says booting but does nothing
tried to flash a different ruu but just says zip read error, cant open the zip
-
thanks in advance for you help, much appreciated
Click to expand...
Click to collapse
Did you try the sd-card method? Rename the RUU to 0PJAIMG.zip, copy it into the root directory of a sd-card that is formatted to fat32 and not bigger than 32gb, put the card into your phone, boot into download mode and follow the instructions on the phone's screen. (Where did you actually get the 1.40.401.8 RUU? The sources I know provide the OTA update and not the RUU. So maybe you know a source I haven't heard of before.)
The output during relocking my old One S and/or my fathers One SV always stated the "too many links" error, too. Nevertheless the bootloader was always relocked after the reboot. (I've never relocked my M9 because there was no need to do so since I bought it.)
Fastboot boot recovery doesn't work on the M9. That's the reason why we need to grab the stock recovery from RUUs or OTAs instead of backing it up before we start flashing.
What TWRP version are you running? I think that error only existed in one of the older versions and is fixed in the newest one.
To replace TWRP with the stock recovery you can try this: Make a backup with only "recovery" checked. Rename the stock recovery to recovery.emmc.win. Replace the recovery.emmc.win in your TWRP backup with the renamed stock recovery and restore the backup. If you now reboot your phone TWRP will be replaced.
Flippy498 said:
Did you try the sd-card method? Rename the RUU to 0PJAIMG.zip, copy it into the root directory of a sd-card that is formatted to fat32 and not bigger than 32gb, put the card into your phone, boot into download mode and follow the instructions on the phone's screen. (Where did you actually get the 1.40.401.8 RUU? The sources I know provide the OTA update and not the RUU. So maybe you know a source I haven't heard of before.)
The output during relocking my old One S and/or my fathers One SV always stated the "too many links" error, too. Nevertheless the bootloader was always relocked after the reboot. (I've never relocked my M9 because there was no need to do so since I bought it.)
Fastboot boot recovery doesn't work on the M9. That's the reason why we need to grab the stock recovery from RUUs or OTAs instead of backing it up before we start flashing.
What TWRP version are you running? I think that error only existed in one of the older versions and is fixed in the newest one.
To replace TWRP with the stock recovery you can try this: Make a backup with only "recovery" checked. Rename the stock recovery to recovery.emmc.win. Replace the recovery.emmc.win in your TWRP backup with the renamed stock recovery and restore the backup. If you now reboot your phone TWRP will be replaced.
Click to expand...
Click to collapse
i'm running 2.8.7.0 twrp and neither the sd card method nor backup method worked for me, and bootloader is still unlocked with that output, twrp just says failed when i try and do a backup, and reboots when i try to flash a rom, do you think the phones memory is corrupted or something?, i just cant seem to do anything
eggyfish said:
i'm running 2.8.7.0 twrp and neither the sd card method nor backup method worked for me, and bootloader is still unlocked with that output, twrp just says failed when i try and do a backup, and reboots when i try to flash a rom, do you think the phones memory is corrupted or something?, i just cant seem to do anything
Click to expand...
Click to collapse
There is a newer version (2.8.7.1-CPTB-B1) which can be found in the beta version section here. Furthermore there is a stock backup provided in this thread that corresponds to your firmware version. Try to update TWRP and then to restore the backup.
Edit (Just to answer my own question from my previous post): The second Link provides a 1.40.401.8 RUU, too.
Flippy498 said:
Did you try the sd-card method? Rename the RUU to 0PJAIMG.zip, copy it into the root directory of a sd-card that is formatted to fat32 and not bigger than 32gb, put the card into your phone, boot into download mode and follow the instructions on the phone's screen. (Where did you actually get the 1.40.401.8 RUU? The sources I know provide the OTA update and not the RUU. So maybe you know a source I haven't heard of before.)
The output during relocking my old One S and/or my fathers One SV always stated the "too many links" error, too. Nevertheless the bootloader was always relocked after the reboot. (I've never relocked my M9 because there was no need to do so since I bought it.)
Fastboot boot recovery doesn't work on the M9. That's the reason why we need to grab the stock recovery from RUUs or OTAs instead of backing it up before we start flashing.
What TWRP version are you running? I think that error only existed in one of the older versions and is fixed in the newest one.
To replace TWRP with the stock recovery you can try this: Make a backup with only "recovery" checked. Rename the stock recovery to recovery.emmc.win. Replace the recovery.emmc.win in your TWRP backup with the renamed stock recovery and restore the backup. If you now reboot your phone TWRP will be replaced.
Click to expand...
Click to collapse
oh and my internal storage is reading as zero, i cant reformat it either, every action i preform in twrp just fails
and i still cant flash twrp
i get this -
writing 'recovery'...
(bootloader) HOSD CL#549783
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.078s]
finished. total time: 5.047s
eggyfish said:
oh and my internal storage is reading as zero, i cant reformat it either, every action i preform in twrp just fails
Click to expand...
Click to collapse
Well, that definitely sounds like your phone's memory is corrupted. I don't know whether there is another method to help you than sending it to HTC's repair service. Are you sure your storage isn't just full (since the flashing output seems to be ok [see below])?
Edit:
eggyfish said:
i get this -
writing 'recovery'...
(bootloader) HOSD CL#549783
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.078s]
finished. total time: 5.047s
Click to expand...
Click to collapse
I actually don't see any error in that output. Everthing is the way it should be.
Flippy498 said:
Well, that definitely sounds like your phone's memory is corrupted. I don't know whether there is another method to help you than sending it to HTC's repair service. Are you sure your storage isn't just full (since the flashing output seems to be ok [see below])?
Edit:
I actually don't see any error in that output. Everthing is the way it should be.
Click to expand...
Click to collapse
hmm, thats strange as it didnt update, i get the same readout when i flash stock, but it stsys on twrp. sureley it cant be full as a ruu flash wipes your data, i think i'll try get a repair from htc, thanks for your help
hi
my GF phone suddenly displayed message and asked me to enter password to decrypt your data , and so i did. It then told me that my password was right, but the data was corrupt, and presented me a button to reset my phone. The button redirected me to recovery and automatically attempted to wipe /data and then re-mount it, but the wipe failed. I rebooted again with the same issue, same failed attempt to wipe. I went to install the zip again, and this time do a full wipe, but it was unable to mount my phone's storage nor my SD card. I am not able to mount either at all now.
the phone is s-on and locked , and i dont have any chance to unlock bootloader because oem unlock is turned off
is there anyway to repair partition and install a new rom without using any custom recovery ???
I assume a RUU could help you. Try this link.
Edit: Here you can find even more RUUs
Go to download mode and check your CID, that should help you know what RUU is correct for your device
rzarectha said:
I assume a RUU could help you. Try this link.
Edit: Here you can find even more RUUs
Go to download mode and check your CID, that should help you know what RUU is correct for your device
Click to expand...
Click to collapse
The first thread you linked is outdated and the links are broken. Best solution would be looking at the sticky threads here in the general section.
Sent from my HTC One M9 using XDA Labs
if ruu doesnt work, go to download mode and try fastboot format <partition> . I think i had something similar and that was how I solved it.
Flippy498 said:
The first thread you linked is outdated and the links are broken. Best solution would be looking at the sticky threads here in the general section.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
i try to flash ruu through fastboot and get this error :
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
after that i run Ruu.exe procedure , the phone stuck in rebooting to bootloader and pc does not recogonize it , somehow i manually reboot phone to bootloader but i got the error phone is at low 30% battery .
what should i do now ??
Adromir said:
if ruu doesnt work, go to download mode and try fastboot format <partition> . I think i had something similar and that was how I solved it.
Click to expand...
Click to collapse
the phone didnt allow me to do it because the bootloader is locked !!! and i dont have chance to unlock it ,since the oem unlocking is turned off
mikakachi said:
i try to flash ruu through fastboot and get this error :
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
after that i run Ruu.exe procedure , the phone stuck in rebooting to bootloader and pc does not recogonize it , somehow i manually reboot phone to bootloader but i got the error phone is at low 30% battery .
what should i do now ??
Click to expand...
Click to collapse
For starters, charge your phone. I can't remember what the minimum threshold is, but there's a safety measure that requires a minimum battery level to avoid the phone turning off in the middle of delicate software operations.
You mention flashing the ruu via flashboot. Have you looked into applying the ruu via the SD card method? That may serve you better.
computerslayer said:
For starters, charge your phone. I can't remember what the minimum threshold is, but there's a safety measure that requires a minimum battery level to avoid the phone turning off in the middle of delicate software operations.
You mention flashing the ruu via flashboot. Have you looked into applying the ruu via the SD card method? That may serve you better.
Click to expand...
Click to collapse
no i did not tried it ! how can i do that ?
mikakachi said:
no i did not tried it ! how can i do that ?
Click to expand...
Click to collapse
Read the instructions in the thread I've mentioned in my last post.
the phone stuck in reboot to bootloader mode and failed to flash from sd card ! i try to install rom from stock recovery and i got this error :
E:failed to setup expected mounts for install; aborting Installation aborted.
E:failed to mount /devlog (invalid argument).. try emmc mount
E:can't find device node for mount point /devlog
.
.
.
.
E:mount /cache fail, format it and mount again
E:failed to mount /cache (invalid argument).. try emmc mount
Hello everyone,
I have a factory HTC 10, Verizon phone. I'm running on Straight Talk so I don't get OTA updates, but I've updated with my laptop and Sync Manager before, so I know I can. So, I finally got the notification on Sync Manager that I could update my phone, from 6.0.1 Software # 1.85.605.9 to 7.0 S# 2.41.605.20. I go to update it add it stops at 19% and says that I have to low battery, I then charge it 100% and try again, but the same thing happens, the update stops at 19% and says my batteries to low.
Now, in my phone under About, the software # is 1.85.605.9, however when I boot to Download Mode my software # reads 2.41.605.20. And I confirmed this with Sync Manager, when my phone is normal booted and plugged in Sync Manager says my software # is 1.85.605.9. But when in Download Mode and plugged in Sync Manager reads 2.41.605.20.
I backed up my phone and did a Factory Data Reset, hoping that would help, but I still have the same problem. Can anyone help?
Thank you.
https://forum.xda-developers.com/verizon-htc-10/how-to/verizon-official-ruu-1-19-605-9-t3377586 here is the link to the latest official RUU for vzw.
Thank you.
I wanted to flash Nougat the first time that the upgrade failed but I couldn't find the RUU online at the time.
However, I still cant get the update to work. Following the directions from the link, I still cant get my phone to update.
this is what I get on the CMD Prompt,
- PS C:\Unlock> htc_fastboot oem rebootRUU
...
OKAY [ 0.085s]
finished. total time: 0.100s
- PS C:\Unlock> htc_fastboot flash zip android7.zip
target reported max download size of 1579200000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2512129245 is not a multiple of the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2512129245 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2512129245 is not a multiple of the block size 4096
OKAY [ 1.012s]
writing 'zip' 1/1...
(bootloader) HOSD CL#857212
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_9
(bootloader) j4njZ
(bootloader) ERR preload central directory info failed (EOCD).
FAILED (remote: 99 RU_UNKNOWN_FAIL terrible mishap with original ret: 0)
finished. total time: 2.099s
Is my phone really screwed up?
Check the MD5 of your download vs the AFH download link. Make sure they match
I don't think you read the first post of the topic which holds the RUU! It's all explained there how to flash it. I would take the SDCard method. You can't "just" flash it.
Read the first post from the given link and it will be clear.
So take the RUU zip rename it and put it on the SD then boot into download mode and follow procedure
82dodge331 said:
Thank you.
I wanted to flash Nougat the first time that the upgrade failed but I couldn't find the RUU online at the time.
However, I still cant get the update to work. Following the directions from the link, I still cant get my phone to update.
this is what I get on the CMD Prompt,
- PS C:\Unlock> htc_fastboot oem rebootRUU
...
OKAY [ 0.085s]
finished. total time: 0.100s
- PS C:\Unlock> htc_fastboot flash zip android7.zip
target reported max download size of 1579200000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2512129245 is not a multiple of the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2512129245 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2512129245 is not a multiple of the block size 4096
OKAY [ 1.012s]
writing 'zip' 1/1...
(bootloader) HOSD CL#857212
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_9
(bootloader) j4njZ
(bootloader) ERR preload central directory info failed (EOCD).
FAILED (remote: 99 RU_UNKNOWN_FAIL terrible mishap with original ret: 0)
finished. total time: 2.099s
Is my phone really screwed up?
Click to expand...
Click to collapse
You ever have any luck?
aer0zer0 said:
You ever have any luck?
Click to expand...
Click to collapse
He didn't post back, so I would imagine he followed the instructions in the OP this time. :laugh:
xunholyx said:
He didn't post back, so I would imagine he followed the instructions in the OP this time. :laugh:
Click to expand...
Click to collapse
I always try to ask, just to make sure they aren't stuck or frustrated. It's hard being new, and having people flame respond all the time (as I'm sure you saw some of the previous comments)
Thanks everyone for assuming I'm an idiot that doesn't know how to read. I did try to load the RUU via the SD card, that didn't work either. Yes it was formatted to FAT32. The phone recognized the card but didn't detect the RUU. zip file.
Anyway, I haven't bothered since I've been busy and the phone is working.
Is there a reason why my phone says its running Nougat in Download mode, but is running Marshmallow when booted up?
82dodge331 said:
Thanks everyone for assuming I'm an idiot that doesn't know how to read. I did try to load the RUU via the SD card, that didn't work either. Yes it was formatted to FAT32. The phone recognized the card but didn't detect the RUU. zip file.
Anyway, I haven't bothered since I've been busy and the phone is working.
Is there a reason why my phone says its running Nougat in Download mode, but is running Marshmallow when booted up?
Click to expand...
Click to collapse
sounds like firmware from nougat mixed with marshmallow OS. was the RUU.zip renamed to 2PS6IMG.zip?
If Nougat and Marshmallow did mix, could that have happened when my upgrade failed the first time? I tried renaming it a few things, I think I renamed it to 2PS6IMG.zip, but cant remember. Also, I tried to use my 128GB SD card, formatted it to FAT32, but I had to download a format software, as I could get Windows to format it natively, in File Explorer or Command line. Could the SD card be to large? I wanna try again, but I'm gonna get a smaller SD card to try.
82dodge331 said:
If Nougat and Marshmallow did mix, could that have happened when my upgrade failed the first time? I tried renaming it a few things, I think I renamed it to 2PS6IMG.zip, but cant remember. Also, I tried to use my 128GB SD card, formatted it to FAT32, but I had to download a format software, as I could get Windows to format it natively, in File Explorer of Command line. Could the SD card be to large? I wanna try again, but I'm gonna get a smaller SD card to try.
Click to expand...
Click to collapse
What it says in download mode is your firmware version, what it says in settings > about is your ROM base (what the ROM you are running is based on)
Also, with the 10 you don't need to have your card formatted to FAT32. exFAT will work just fine. I would suggest you re-format to that and try again (128gb cards aren't made for FAT32). And make sure you haven't accidentally renamed it to 2PS6IMG.zip.zip (I've seen that mistake several times before).
Well, like I said I formatted to FAT32 because that's what aer0's tutorial said to do. I didn't think it would work with my 128GB, and I was worried I was going to corrupt it, but it didn't.
anyway, I'm going to get an 8GB SD card and try again, I'll format to FAT32 first just to try, then if it doesn't work I'll reformat to exFAT and go again.
I'll report back tonight.
well it worked, I'm running Nougat. I got a 16GB SD card, couldn't find an 8 at Walmart, was already formatted to FAT32, I loaded the .zip file on there from my computer and renamed it 2PS6IMG.zip. Flashed perfectly.
after I plugged it into Sync Manager just to see if it would recognize my phone, as I've trouble with that before. And turns out there's a new update. So, I tried to upgrade, to the new latest and it failed @ 19% again, with a battery to low warning. I had 90% battery. I just cant update my phone through Sync Manager I guess.
Thanks aer0 for the help. I think my problem was I wasn't renaming the zip file right or at all. I tried so many times I forgot exactly what I tried. anyway, I might be even more helpful to add to your tutorial to rename what ever zip a person downloads, they need to rename it to 2PS6IMG.zip. Because, I understood it as, download whichever 2PS6IMG_something.zip, drop it on the SD and go. Just might be more helpful.
82dodge331 said:
well it worked, I'm running Nougat. I got a 16GB SD card, couldn't find an 8 at Walmart, was already formatted to FAT32, I loaded the .zip file on there from my computer and renamed it 2PS6IMG.zip. Flashed perfectly.
after I plugged it into Sync Manager just to see if it would recognize my phone, as I've trouble with that before. And turns out there's a new update. So, I tried to upgrade, to the new latest and it failed @ 19% again, with a battery to low warning. I had 90% battery. I just cant update my phone through Sync Manager I guess.
Thanks aer0 for the help. I think my problem was I wasn't renaming the zip file right or at all. I tried so many times I forgot exactly what I tried. anyway, I might be even more helpful to add to your tutorial to rename what ever zip a person downloads, they need to rename it to 2PS6IMG.zip. Because, I understood it as, download whichever 2PS6IMG_something.zip, drop it on the SD and go. Just might be more helpful.
Click to expand...
Click to collapse
I unfortunately don't have the hosting rights to those files. That's @Kisakuku and others. Have I thought about it, sure have... The only problem with renaming them all to what it should be is you lose tracking of the versions, with so many it's easy to do. What I have done is on my PC, I created a sub directory of all the RUU's, then renamed them appropriately within, so I can drag and drop to the SD. Also, with OCD, I have multiple 4gb SDs labelled with versions. Which RUU did you flash? .23 is the newest, shouldn't be a new release just yet.
I didn't mean for you to rename all the files, as you said no one could keep track of which version is which. I meant you should add a note in the instructions for the downloader to rename the file after they download the zip.
I flashed to .20, because I didn't know .23 was available until I connected to Sync Manager. So I tried to update though Sync Manager to .23 from .20, and it failed @ 19%
82dodge331 said:
I didn't mean for you to rename all the files, as you said no one could keep track of which version is which. I meant you should add a note in the instructions for the downloader to rename the file after they download the zip.
I flashed to .20, because I didn't know .23 was available until I connected to Sync Manager. So I tried to update though Sync Manager to .23 from .20, and it failed @ 19%
Click to expand...
Click to collapse
I updated the OP in the verizon RUU thread per your request sir
It was just a suggestion, but hopefully it helps others just as it did for me.
Again, I appreciate the help.