hey guys, yesterdy I got a notification for android 6.0 upgrade and it was a ~100mb file for preparation so i downloaded it and charged my battery and tapped to install it, it reboots and wants to start installing but then goes to recovery menu and gives an error
the phone is all stock, no root or bl unlock or anything
I attached the error msg below:
it's m8sd not e8sd, mistyped in topic
Might be due to bad zip file! Download the update again and try!
Kianush said:
hey guys, yesterdy I got a notification for android 6.0 upgrade and it was a ~100mb file for preparation so i downloaded it and charged my battery and tapped to install it, it reboots and wants to start installing but then goes to recovery menu and gives an error
the phone is all stock, no root or bl unlock or anything
I attached the error msg below:
it's m8sd not e8sd, mistyped in topic
Click to expand...
Click to collapse
I had a similar error as yours doing exactly the same thing but mine was a e8sw running LP5 Sense6 rooted stock with xposed.
Even when I uninstalled xposed and disabled supersu, I still could not install the upgrade.
Finally managed to get the upgrade by going all the way back to stock and allow the OTA updates all the way up the MM6 update. Took me nearly 2 days to do that.
I have taken clean twrp backups of all the stock updates and will try and post them here soon.
generalugh28 said:
I had a similar error as yours doing exactly the same thing but mine was a e8sw running LP5 Sense6 rooted stock with xposed.
Even when I uninstalled xposed and disabled supersu, I still could not install the upgrade.
Finally managed to get the upgrade by going all the way back to stock and allow the OTA updates all the way up the MM6 update. Took me nearly 2 days to do that.
I have taken clean twrp backups of all the stock updates and will try and post them here soon.
Click to expand...
Click to collapse
thank you for the information, but as I mentioned in op my phone is already all stock, I havent ever moded or rooted or anything, it's stock locked bootloader
Have the exact same issue. My device is compelitely stock. Tried flashing the recovery from the downloaded OTA but still got the sama error. Hopefully someone will be able to resolve the issue.
if you have problems in installing OTA updates, follow these steps
1. check if your CID and MID are matching each other. they should be both for same region. mine are for vietnam. mec_dugl / HTC__057
2.Flash an stock RUU from http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210
3.Skip all registeration process and directly go to update menu.
4.this is a 3 stage update process: a small update for some applications/another 100 MB update for making device ready for main update!! / at last 1 GB main update . each one should be downloaded and installed separately.
5. after downloading 100MB update, DO NOT restart. coneect your phone to PC and go to download folder on phone internal memory, there should be a zip file containing updates(sadly I forgot file name), copy it on your PC and extract recovery.img from it.
6. boot your phone into bootloader and flash stock recovery you've extracted using fastboot.
7. now you have complete stock ROM. go to setting/update again and follow update process.
8.after updating you may flash twrp and supersu.
9. I don't know why, but there is a good chance that after messing with system files in MM you get stuck in several kinds of bootloops and soft-breaks. Don't worry; all you should do is going to recovery and wiping caches. sometimes you need a factory reset too. also have in mind that a complete boot after changing system files may take up to 15 minutes even without wipes.
@sam5154 well thank you for the info, Im gonna try these steps except, I will try to download again and flash recovery and try it before flashing a RUU and lose everything
but I hope it works anyway, btw mine is also vietnam region.
sam5154 said:
if you have problems in installing OTA updates, follow these steps
1. check if your CID and MID are matching each other. they should be both for same region. mine are for vietnam. mec_dugl / HTC__057
2.Flash an stock RUU from http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210
3.Skip all registeration process and directly go to update menu.
4.this is a 3 stage update process: a small update for some applications/another 100 MB update for making device ready for main update!! / at last 1 GB main update . each one should be downloaded and installed separately.
5. after downloading 100MB update, DO NOT restart. coneect your phone to PC and go to download folder on phone internal memory, there should be a zip file containing updates(sadly I forgot file name), copy it on your PC and extract recovery.img from it.
6. boot your phone into bootloader and flash stock recovery you've extracted using fastboot.
7. now you have complete stock ROM. go to setting/update again and follow update process.
8.after updating you may flash twrp and supersu.
9. I don't know why, but there is a good chance that after messing with system files in MM you get stuck in several kinds of bootloops and soft-breaks. Don't worry; all you should do is going to recovery and wiping caches. sometimes you need a factory reset too. also have in mind that a complete boot after changing system files may take up to 15 minutes even without wipes.
Click to expand...
Click to collapse
Hi, thanks for this. I will try this once i got home.
But i have one questions, mine is Vietnam MEC_DUGL with stock lollipop 5.0.2. The RUU only available for stock lollipop 5.0.1. Can I use this RUU or should I look for specific RUU for lollipop 5.02?
Thanks!
Kianush said:
@sam5154 well thank you for the info, Im gonna try these steps except, I will try to download again and flash recovery and try it before flashing a RUU and lose everything
but I hope it works anyway, btw mine is also vietnam region.
Click to expand...
Click to collapse
If you gonaa try that, then remeber to unroot and uninstall xposed, and you can use titanium backup for restoring your apps and data of course.
sam5154 said:
If you gonaa try that, then remeber to unroot and uninstall xposed, and you can use titanium backup for restoring your apps and data of course.
Click to expand...
Click to collapse
in op I already told that I dont have root or anything and the phone is all stock and it was like this from the begining, that means no xposed or anything else
Kianush said:
in op I already told that I dont have root or anything and the phone is all stock and it was like this from the begining, that means no xposed or anything else
Click to expand...
Click to collapse
Have you tried the suggestion above? Let me know the result! Thanks man
sam5154 said:
If you gonaa try that, then remeber to unroot and uninstall xposed, and you can use titanium backup for restoring your apps and data of course.
Click to expand...
Click to collapse
and how to check for this mec_dugl / HTC__057?
the first part is ok it shows that in booloader menu, but how to check for HTC__057??
Kianush said:
in op I already told that I dont have root or anything and the phone is all stock and it was like this from the begining, that means no xposed or anything else
Click to expand...
Click to collapse
Kianush said:
and how to check for this mec_dugl / HTC__057?
the first part is ok it shows that in booloader menu, but how to check for HTC__057??
Click to expand...
Click to collapse
Here you go :
If you want more information, use ADB (if you don't how to get it going, use the search on the forum or Google about it).
While you phone is connected to your PC, type adb reboot bootloader and wait for your phone to reboot into bootloader mode. Once there, you can perform fastboot commands like getvar. Type fastboot getvar all and you will see all the information about the phone, including the product variable which lists the model you have.
Source : http://forums.androidcentral.com/htc-one-m7/320871-how-check-htc-one-variant-model.html
bataskhayal said:
Here you go :
If you want more information, use ADB (if you don't how to get it going, use the search on the forum or Google about it).
While you phone is connected to your PC, type adb reboot bootloader and wait for your phone to reboot into bootloader mode. Once there, you can perform fastboot commands like getvar. Type fastboot getvar all and you will see all the information about the phone, including the product variable which lists the model you have.
Source : http://forums.androidcentral.com/htc-one-m7/320871-how-check-htc-one-variant-model.html
Click to expand...
Click to collapse
Thank you for the info
btw I did go through the steps of downloading the 110mb update and flashing its recovery before pressing install and that didnt work and still gives OP error
so I guess I have to use RUU but not gonna do that for a while and also Im not so sure it'll work because the phone is already factory stock!
Kianush said:
Thank you for the info
btw I did go through the steps of downloading the 110mb update and flashing its recovery before pressing install and that didnt work and still gives OP error
so I guess I have to use RUU but not gonna do that for a while and also Im not so sure it'll work because the phone is already factory stock!
Click to expand...
Click to collapse
Yes bos, i also did the recovery trick but still cant make it work. So the only solution we havent try is to flash RUU which i doubt also will make it work since my phone also factory stock. So i guess will stay in 5.0.2 for a while.
Kianush said:
Thank you for the info
btw I did go through the steps of downloading the 110mb update and flashing its recovery before pressing install and that didnt work and still gives OP error
so I guess I have to use RUU but not gonna do that for a while and also Im not so sure it'll work because the phone is already factory stock!
Click to expand...
Click to collapse
Hi, I have managed to finally update my Vietnam HTC One E8 dual SIM (MEC_DUGL) to Android 6.0. The problem that cause the error is the error recovery file, hence I re-install the RUU to get the correct recovery.img file. Below are the steps :
Note : Try with your own risk
1. My device is currently stock 5.0.2 no root and locked. Before starting the update process please make sure to backup all of your important data. Im using the stock HTC backup software, when you restore your device after you finished your update process, it will re-install your currently installed apps , contacts, settings, etc.
2. Download RUU for your device here : http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210
I downloaded :
[Vietnam][DUAL][M8sd][mec_dugl][CID HTC__059][OPAJ20000] :
[Lollipop 5.0.1][2.35.425.2] : LINK
Seems not match with my current software (5.0.2), but eventually it will do the magic.
3. Flash RUU. NOTE : You will lose all of your data in your internal phone memory. Make sure to backup all of your important files.
Steps:
1) Download RUU.
2) Rename RUU to 0PAJIMG.zip (the first character is a zero, NOT A LETTER O)
3) Put renamed 0PAJIMG.zip on your external_SD
4) Boot into your bootloader and make sure your in hboot and let it update its RUU.
5) No PC, no adb, no fastboot, no terminal is needed, just a root explorer to rename and transfer the renamed RUU file to external_sd
6) After you have updated your RUU, make sure to remove the 0PAJIMG.zip from your external_sd because it will ask to update your RUU everytime your reboot to your bootloader which it is technically supposed to do but its unnecessary after you have done it once (unless you are planning on flashing RUU again).
7) Done!
Source : http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210
4. Reboot your phone, now your phone is back to factory stock, connect it to wifi, no need to set up any account, just go directly to software update from Settings > About > Software Updates. Just install all the available software updates (5.0.2 > 6.0 part 1 > 6.0 part 2).
5. BOOM! Your HTC One E8 now runs Android 6.0.1 Marshmallow.
6. Restore your phone from the stock HTC Backup Software.
7. Done
Related
I'm on Acer_AV043_A700_1.026.00_EMEA_GB.
Still no update available - is any one else having this problem?
chrisgeller said:
I'm on Acer_AV043_A700_1.026.00_EMEA_GB.
Still no update available - is any one else having this problem?
Click to expand...
Click to collapse
It's not a problem. It can take up to 2-3 months for updates to roll out completely to all regions and serial numbers.
Yeah, I dont have it either.
I do know it takes time though
which is why most of the time we force it with a ROM update
chrisgeller said:
I'm on Acer_AV043_A700_1.026.00_EMEA_GB.
Still no update available - is any one else having this problem?
Click to expand...
Click to collapse
I don't know if you did it, but you won't get the update once you unlocked the bootloader and rooted your tab.
....That wouldn't prevent the OTA from being showing as available and downloading, though. It just prevents install. That can be remedied, though...I was rooted and unlocked and just returned to stock to get the last OTA.
Returning to stock...
ExtremeRyno said:
....That wouldn't prevent the OTA from being showing as available and downloading, though. It just prevents install. That can be remedied, though...I was rooted and unlocked and just returned to stock to get the last OTA.
Click to expand...
Click to collapse
Can you please post how you returned the bootloader to stock, or "locked" ? My A700 is rooted and unlocked. I can "hide" the root with OTA Rootkeeper, but I am not sure how to return the unlocked bootloader back to stock.
Any help is much appreciated and thanks in advance!
Even though this worked for me, you should still do this at your own risk....I'm not an expert, I just got lucky.
1. Get Android SDK & the official Acer USB Drivers http://developer.android.com/sdk/index.html & http://support.acer.com/product/default.aspx?modelId=4318
2. Unlock the bootloader: http://forum.xda-developers.com/showthread.php?t=1710755
3. Install Clockwork Recovery: http://forum.xda-developers.com/showthread.php?t=1791165
- I had to install this (6.0.1.4) recovery.img using the BAT file from this post. IMPORTANT! DO NOT INSTALL THE recovery.img FROM THAT (5.5.0.4) LINK! It will brick you. Replace it with the one from the first thread above ( CWM v.6.0.1.4).
4. Download the appropriate FULL ROM for your device. http://forum.xda-developers.com/showthread.php?t=1720157
5. Follow the directions in this link. If you can't get update.zip to run from an external SD (I couldn't) then try it from the root directory of your internal SD. http://forum.xda-developers.com/showthread.php?t=1812635
After you've done it all, be sure to choose "NO" when you reboot the system from CWM, otherwise CWM is still going to be there and you're probably going to be unable to get future updates.
It took me about two hours of trial and error to figure all this out, and in the end my bootloader was relocked, my root was unrooted, and I was on stock 1.0.29 and able to get OTA updates.
Thanks!
ExtremeRyno said:
1. Get Android SDK & the official Acer USB Drivers http://developer.android.com/sdk/index.html & http://support.acer.com/product/default.aspx?modelId=4318
2. Unlock the bootloader: http://forum.xda-developers.com/showthread.php?t=1710755
3. Install Clockwork Recovery: http://forum.xda-developers.com/showthread.php?t=1791165
- I had to install this (6.0.1.4) recovery.img using the BAT file from this post. IMPORTANT! DO NOT INSTALL THE recovery.img FROM THAT (5.5.0.4) LINK! It will brick you. Replace it with the one from the first thread above ( CWM v.6.0.1.4).
4. Download the appropriate FULL ROM for your device. http://forum.xda-developers.com/showthread.php?t=1720157
5. Follow the directions in this link. If you can't get update.zip to run from an external SD (I couldn't) then try it from the root directory of your internal SD. http://forum.xda-developers.com/showthread.php?t=1812635
After you've done it all, be sure to choose "NO" when you reboot the system from CWM, otherwise CWM is still going to be there and you're probably going to be unable to get future updates.
It took me about two hours of trial and error to figure all this out, and in the end my bootloader was relocked, my root was unrooted, and I was on stock 1.0.29 and able to get OTA updates.
Click to expand...
Click to collapse
Thanks! I was able to get the 1.0.29 flashed back and have stock bootloader with no root. I did NOT install CWM because I am going to wait for JB before I do any root or recovery modes. I am looking to try to find the Acer ROM AV043.RV23RC03_PA_CUS1 ROM because it was what I had on the tablet and was an update over 1.0.29. If you know where I can get it, I would appreciate it. I can't find it anywhere!- Thanks again!
My v10 downloaded an OTA , which im assuming is 6.0
1. Im rooted on stock 6.0 and unlocked boot loader. Will the OTA work without messing up anything ? Ill have to root again im sure, just want some info before i pull the trigger.
I don't think the update will even proceed being that you're on a rooted ROM. I have that notification too, and i just don't know how to turn it off.
I to am rooted,unlockboot and stock rom. I don't feel like taking a chance. So I used titanium backup to freeze the software update and in the drop down notification if you press it, it's a notification from Google play services if you block it in apps it will disappear from your drop down. I also deleted the update zip in the cache folder.I used es file explorer ,device/cache/update
popwar said:
My v10 downloaded an OTA , which im assuming is 6.0
1. Im rooted on stock 6.0 and unlocked boot loader. Will the OTA work without messing up anything ? Ill have to root again im sure, just want some info before i pull the trigger.
Click to expand...
Click to collapse
Okay, I'm assuming you are on H90120e (system version). There is a root exploit for the H90120j update. You just do the following:
Make a backup of your apps and settings
Flash your phone to the new update (H90120j)?
Take a look at either one of these threads to root your device again:
http://forum.xda-developers.com/tmobile-lg-v10/general/step-step-guide-rooting-lg-v10-using-t3382631
OR
http://forum.xda-developers.com/tmobile-lg-v10/general/root-android-6-0-h901-t3382819
You can't flash the phone that is already rooted and has TWRP.
I am in this same situation. On stock rom with root and twrp. I want to update to the new update, but do not want to loose all my apps, settings, etc.
Question is, how to do the initial update before having to re-root again?
How do we flash the phone with the new update?
bhagiratha said:
You can't flash the phone that is already rooted and has TWRP.
I am in this same situation. On stock rom with root and twrp. I want to update to the new update, but do not want to loose all my apps, settings, etc.
Question is, how to do the initial update before having to re-root again?
How do we flash the phone with the new update?
Click to expand...
Click to collapse
Why can't you flash the phone that is already rooted and has TWRP?
All you are doing is opening the LGUP tool and flashing the new H90120j .kdz file using the "refurbish" option then flashing the H90120j .tot file that has TWRP using the "update" option which will flash the phone regardless of what is running on your phone. The guides on the first link explain that. I believe your concern is keeping all of your settings and apps. Look up Titanium backup, it works for me.
Thank you. I only flash the LGH901AT-01-V20j-310-260-JUL-12-2016-ARB02+0ROOTTWRP tot file and all is good.
Well except that I lost Dolby audio.
I will look for a fix.
jun19inf said:
Okay, I'm assuming you are on H90120e (system version). There is a root exploit for the H90120j update. You just do the following:
Make a backup of your apps and settings
Flash your phone to the new update (H90120j)?
Take a look at either one of these threads to root your device again:
http://forum.xda-developers.com/tmobile-lg-v10/general/step-step-guide-rooting-lg-v10-using-t3382631
OR
http://forum.xda-developers.com/tmobile-lg-v10/general/root-android-6-0-h901-t3382819
Click to expand...
Click to collapse
Hi,
Do I have to use LGUP to install the update or can I click install on the dropdown of my phone?
I'm on stock MM 6.0 (H90120e) Rooted and I will not have access to my main PC for another week as I'm traveling.
Thanks,
-NJ
Anyone?
bhagiratha said:
You can't flash the phone that is already rooted and has TWRP.
I am in this same situation. On stock rom with root and twrp. I want to update to the new update, but do not want to loose all my apps, settings, etc.
Question is, how to do the initial update before having to re-root again?
How do we flash the phone with the new update?
Click to expand...
Click to collapse
There's a guide in general that tells how to do all this. In fact jun19inf WROTE it.
In a nutshell, do a twrp backup.
Upgrade to 20j by flashing the stock 20j kbz.
Enable usb debugging and oem unlock
flash tot that has twrp in it.
Now you can go into twrp and 1) root via supersu 2) restore ONLY data from your twrp backup taken previously to get your apps etc back. Alternatively Titanium Backup will also do just fine.
njdevils28 said:
Hi,
Do I have to use LGUP to install the update or can I click install on the dropdown of my phone?
I'm on stock MM 6.0 (H90120e) Rooted and I will not have access to my main PC for another week as I'm traveling.
Thanks,
-NJ
Click to expand...
Click to collapse
If all is you have is root, you should be able to unroot in the SuperSU settings, and then let the update install. But if you have TWRP, then I can't see any way to do the update without using a PC to flash your phone back to stock ROM and recovery. Although you may check the dev. section to see if Eliminator has a flashable ROM to bring you up to date.
Sent from my LG-H901 using XDA-Developers mobile app
YrrchSebor said:
If all is you have is root, you should be able to unroot in the SuperSU settings, and then let the update install. But if you have TWRP, then I can't see any way to do the update without using a PC to flash your phone back to stock ROM and recovery. Although you may check the dev. section to see if Eliminator has a flashable ROM to bring you up to date.
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
Ah. Thank you very much!
-NJ
Hi all. I just got my factory warranty back and I attempted to root it. Everything went as it should, until just after the install finished. Instead of rebooting normally, it now will only reboot into TWRP. Once there, when I try to flash a custom ROM (in this case, Bliss, but I don't think it matters, I get an error message that says the zip file is corrupt. Then, while still in recovery, when I tried to wipe everything except the sd card, it says mkfs.fat process ended with error. I then powered down and attempted the factory reset. I scrolled down on both screens and it did not say anything about any errors, so I assumed it took. However, it reboots right back into TWRP recovery. It also boots right to TWRP recovery when I try to boot normally. Of course, adb does not recognize the phone in any mode that I can get into (fastboot/recovery/download), so, I can't use LG Bridge to reflash the original firmware. Does anybody have any ideas for a fix? I know that this replacement phone had 6.0 on it. I thought I did everything to a t? TIA...
OK, not sure how I got there, but when I attempt to reboot from TWRP it says No OS Installed! Are you sure you want to reboot? That at least says what the problem is. Does anybody know how to fix this?
Where can I download the update file?
wbexpress said:
Hi all. I just got my factory warranty back and I attempted to root it. Everything went as it should, until just after the install finished. Instead of rebooting normally, it now will only reboot into TWRP. Once there, when I try to flash a custom ROM (in this case, Bliss, but I don't think it matters, I get an error message that says the zip file is corrupt. Then, while still in recovery, when I tried to wipe everything except the sd card, it says mkfs.fat process ended with error. I then powered down and attempted the factory reset. I scrolled down on both screens and it did not say anything about any errors, so I assumed it took. However, it reboots right back into TWRP recovery. It also boots right to TWRP recovery when I try to boot normally. Of course, adb does not recognize the phone in any mode that I can get into (fastboot/recovery/download), so, I can't use LG Bridge to reflash the original firmware. Does anybody have any ideas for a fix? I know that this replacement phone had 6.0 on it. I thought I did everything to a t? TIA...
OK, not sure how I got there, but when I attempt to reboot from TWRP it says No OS Installed! Are you sure you want to reboot? That at least says what the problem is. Does anybody know how to fix this?
Click to expand...
Click to collapse
Did you select refurbish or upgrade?
I believe you need to select upgrade when flashing or you get stuck in TWRP
Sent from my LG-H901 using XDA-Developers mobile app
How to root V10 T-mobile M.M ver V20L
How to root V10 T-mobile M.M ver V20L
Can some one guide me on the following:
1. Can I flash back and downgrade to Software version V20J from V20L.
2. Is there any root method for V10 t-mobile MM ver V20L.
1. It is well explained in this forum, you CANNOT go back without facing a software brick.
2. You can root your phone through Dirty_Cow method or by flash Eliminater74 ROM (Part1 & Part2).
Again, search for that in this section and in development one...
jonsat said:
1. It is well explained in this forum, you CANNOT go back without facing a software brick.
2. You can root your phone through Dirty_Cow method or by flash Eliminater74 ROM (Part1 & Part2).
Again, search for that in this section and in development one...
Click to expand...
Click to collapse
Thanks so much for your reply, I was about to flash it to downgrade my V10 from V20L to V20J i even downloaded the files for it Phew....
Okay, I have searched most of the rootings are V20J i have not found a method for rooting and twrp for V20L software update.
Please if u can share the link, that would be helpful...
thanks regards,
I wonder how people perform searches... by the way, few lines under this very thread, there is:
https://forum.xda-developers.com/tmobile-lg-v10/general/root-20l-dirty-cow-t3498722
jonsat said:
I wonder how people perform searches... by the way, few lines under this very thread, there is:
https://forum.xda-developers.com/tmobile-lg-v10/general/root-20l-dirty-cow-t3498722
Click to expand...
Click to collapse
Awwhh GOD!!! big thanks for your help, u r truly an awesome person. Peace and blessing upon u.
regards,
After Failing over and over, I finally was able to flash the latest NOUGAT Update provided in the other thread:
http://forum.xda-developers.com/moto-z/how-to/android-7-international-rollout-t3510790
Download the update.zip file "Blur_Version.24.21.46.griffin.retail.en.US.zip" from one of the posts
Main issue for me was i was on the wrong firmware, simple flash the "XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml" firmware by grabbing it from
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
Notice you need the MPL24.246-45 FIRMWARE , the number 45 plays a major role as it will be verified later. I was running the buildnumber MPL24.246-20 instead of 40
once you get that out of the way and are done flashing the MPL24.246-40 firmware, simply adb sideload the Blur_Version.24.21.46.griffin.retail.en.US.zip from your computer, reboot in stock recovery and then hold power and then press volume up and choose the option adb sideload
My sideload failed at 95%, however when i rebooted, it was running nougat
let me know how it goes for you guys
My bootloader is unlocked, and i did not relock it
This is really sad. They said it was going to be this week and a global roll out.
Nothing!
I can't wait until Samsung release the S8E.. Giving this phone to my 8 years old niece to have!
can u make some order here ?
what is your model ?
if u flashed 24.246-45 then u said it needs to be 40
then did u flash the 40 over 45 ?
thanks
hassanman1997 said:
Download the update.zip file "Blur_Version.24.21.46.griffin.retail.en.US.zip" from one of the posts
Main issue for me was i was on the wrong firmware, simple flash the "XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml" firmware by grabbing it from
Notice you need the MPL24.246-45 FIRMWARE , the number 45 plays a major role as it will be verified later. I was running the buildnumber MPL24.246-20 instead of 40
once you get that out of the way and are done flashing the MPL24.246-40 firmware,
Click to expand...
Click to collapse
This is really helpful. I hit the same snag when I tried to upgrade from -17 firmware.
Any chance you could upload the Canadian Rogers firmware (-45) to Mega? It's so painful waiting for 9 hours for it to fail a few minutes from the end.
Yeah I can try, but I won't be home until night, the only pain was waiting 9 hours, and the firmware is -45, I accidently wrote -40 , I don't think there is any firmware with-40
I tried all the above. Still fails for me.
---------- Post added at 05:14 PM ---------- Previous post was at 05:10 PM ----------
I think because the file has been replaced with a v2 so it's failing verification
I'm uploading the Rogers .45 firmware to mega right now. I'll update this post once its done uploading.
Link: https://mega.nz/#!nssGEDiT!hhLkcTM106hmqbH_fiWfAytEV-fgdlYOhUwpcd_sGJY
Downloaded straight from FileFactory and uploaded directly to Mega
Here is: XT1650-03_GRIFFIN_ROGERS_MPL24.246-45
https://drive.google.com/file/d/0Bw3YYHFxKQxVNTBLeWxadUFZOU0/view?usp=sharing
...Now, can someone help me figure out how to flash it? That would be awesome
svetius said:
Here is: XT1650-03_GRIFFIN_ROGERS_MPL24.246-45
https://drive.google.com/file/d/0Bw3YYHFxKQxVNTBLeWxadUFZOU0/view?usp=sharing
...Now, can someone help me figure out how to flash it? That would be awesome
Click to expand...
Click to collapse
Whats the status of your device right now? Are you purely stock? Rooted? Unlocked? TWRP or stock recovery?
Prfndhatrdofman said:
Whats the status of your device right now? Are you purely stock? Rooted? Unlocked? TWRP or stock recovery?
Click to expand...
Click to collapse
I flashed XT1650-03_GRIFFIN_ROGERS_MPL24.246-45 via this method:
http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
And while the flash was successful, strangely booting into the OS I'm still on -20.
So then I tried to sideload nougat, and it went up to 87% and failed, causing a bootloop. The bootloop can be fixed by manually flashing -45 again (which is so weird because it actually loads -20).
I am unrooted, bootloader locked.
svetius said:
I flashed XT1650-03_GRIFFIN_ROGERS_MPL24.246-45 via this method:
http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
And while the flash was successful, strangely booting into the OS I'm still on -20.
So then I tried to sideload nougat, and it went up to 87% and failed, causing a bootloop. The bootloop can be fixed by manually flashing -45 again (which is so weird because it actually loads -20).
I am unrooted, bootloader locked.
Click to expand...
Click to collapse
You got further than me. ADB Sideload wouldnt even look at the Nougat OTA zip. tried multiple ADB versions too
svetius said:
I flashed XT1650-03_GRIFFIN_ROGERS_MPL24.246-45 via this method:
http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
And while the flash was successful, strangely booting into the OS I'm still on -20.
So then I tried to sideload nougat, and it went up to 87% and failed, causing a bootloop. The bootloop can be fixed by manually flashing -45 again (which is so weird because it actually loads -20).
I am unrooted, bootloader locked.
Click to expand...
Click to collapse
Sideload was successful for me, but still completely in a bootloop as well..
for me it worked fine with ADB sideload.
my bootloader is unlocked, i tried locking it back to get official OTA but failed to lock it again.
I tried every method that was mentioned but failed over and over
so here is what I did:
1) removed all the personal files from phone (pictures, videos, texts etc) so i don't lose em
2) flashed the rogers [XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml] firmware by using mfastboot, make sure you grab the mfastbootv2, you can google and download it, use mfastboot and flash the firmware by command lines
3)after flashing, rebooted, set up the device and skipping a few steps to get into homescreen, and then powered off the phone.
4)downloaded Blur_Version.24.21.46.griffin.retail.en.US.zip and placed it in the adb folder, make sure you download the latest adb tools, you can google and find them easily too
5) extract the adb folder and place the Blur_Version.24.21.46.griffin.retail.en.US.zip in side that folder
6) reboot the phone and press volume to navigate to recovery, you should boot into stock recovery as you flashed stock firmware
7) hold power button and press volume up and youll see the menu, select update by ota and connect to the phone
8) open command line in the adb tools and use command to flash ota via adb
9) mine failed at 95% because of system image error, so instead of rebooting it, i used the command again and flashed the ota via adb, it failed again, however when i rebooted i was presented by the new red moto boot animation, there i knew it was updated to android N
*Delete*
hassanman1997 said:
After Failing over and over, I finally was able to flash the latest NOUGAT Update provided in the other thread:
http://forum.xda-developers.com/moto-z/how-to/android-7-international-rollout-t3510790
Download the update.zip file "Blur_Version.24.21.46.griffin.retail.en.US.zip" from one of the posts
Main issue for me was i was on the wrong firmware, simple flash the "XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml" firmware by grabbing it from
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
Notice you need the MPL24.246-45 FIRMWARE , the number 45 plays a major role as it will be verified later. I was running the buildnumber MPL24.246-20 instead of 40
once you get that out of the way and are done flashing the MPL24.246-40 firmware, simply adb sideload the Blur_Version.24.21.46.griffin.retail.en.US.zip from your computer, reboot in stock recovery and then hold power and then press volume up and choose the option adb sideload
My sideload failed at 95%, however when i rebooted, it was running nougat
let me know how it goes for you guys
My bootloader is unlocked, and i did not relock it
Click to expand...
Click to collapse
OK, so i got it working. But there were some difficulties.
I was on 24.246-45 already, but i installed TWRP and a custom kernel. I reflashed the recovery and boot from the BELL 24.246.45 firmware, and proceeded sideloading the update. It errored out, saying system was mounted r/w once (after I installed TWRP, but I never altered it beyond that).
So i flashed the system chunks from the firmware ( "mfastboot flash system system.img_sparsechunk.0" , "mfastboot flash system system.img_sparsechunk.1" etc.), then i retried the sideload, and it worked. The system information still says the build number is MPL24.246-45, but the android version is 7.0, everything seems to be working, including split screen, the new easter egg, quicklaunch ribbon, and new notifications.
gomisensei said:
... The system information still says the build number is MPL24.246-45, but the android version is 7.0, everything seems to be working, including split screen, the new easter egg, quicklaunch ribbon, and new notifications.
Click to expand...
Click to collapse
This should be only a "cosmetic" issue... probably you can fix it by editing build.prop...
enetec said:
This should be only a "cosmetic" issue... probably you can fix it by editing build.prop...
Click to expand...
Click to collapse
meh, i'm not really worried about it, at least not enough to guess what the version SHOULD be...
gomisensei said:
meh, i'm not really worried about it, at least not enough to guess what the version SHOULD be...
Click to expand...
Click to collapse
:laugh:
Does that actually work for other software channels as well?
I'm from india, my software chanel is retin (retail India) can I still flash the one that came for retus?
Sent from my Moto Z using XDA Labs
Hi guys,
My phone now is on LeeDroid custom ROM (Build 1.03.401.6.9_g CL923215)
What are the steps to return the htc u11 to stock please?
The original software number of my phone is: 1.11.400.4
EDIT: I went to: https://forum.xda-developers.com/showpost.php?p=72425224&postcount=5
& downloaded stock recovery & nandroid TWRP backup (for 1.11.400.4).
However, I couldnt flash that nandroid TWRP from TWRP recovery.
Long story short, I just got the phone today, I made a big mistake by not inserting the simcard in & testing to see if the phone working or not.
So, I went straight through the process of unlocking bootloader, installing TWRP, Rooting, Installing custom ROM without making a nandroid backup.
For all that, the phone did not recognize the sim cards (tried both my sim & my gf's sim. not working)
The store will take back the phone as long as I return it to stock.
Thanks for your help!!!
dsymbol said:
Hi guys,
What's the process of returning the htc u11 to stock please?
Googling doesn't give me much result.
Long story short but I just got the phone today, I made a big mistake by not inserting the simcard in & testing to see if the phone working or not.
So, I went straight through the process of unlocking bootloader, installing TWRP, Rooting, Installing custom ROM without making a nandroid backup.
For all that, the phone did not recognize the sim cards (tried both my sim & my gf's sim. not working)
The store will take back the phone as long as I return it to stock.
Thanks for your help!!!
Click to expand...
Click to collapse
You'll need to download the stock rom for your verison (ruu). Hopefully one is available. Check the guide section here.
purple patch said:
You'll need to download the stock rom for your verison (ruu). Hopefully one is available. Check the guide section here.
Click to expand...
Click to collapse
I've downloaded stock recovery & nandroid TWRP backup of my stock ROM now.
What are the steps to revert the phone to stock please?
Thanks
dsymbol said:
I've downloaded stock recovery & nandroid TWRP backup of my stock ROM now.
What are the steps to revert the phone to stock please?
Thanks
Click to expand...
Click to collapse
Restore the TWRP backup, check everything is working, then flash stock recovery if you need to. The stock Nandroid should include recovery asfaik. I'm more of a trial and error guy lol. Read guide pages to know for certain, check HTC 10 guides, same steps.
purple patch said:
Restore the TWRP backup, check everything is working, then flash stock recovery if you need to. The stock Nandroid should include recovery asfaik.
Click to expand...
Click to collapse
ok so I downloaded TWRP_Backup_Untouched_System_Image_+_Boot_1.11.400.4_OCEAN_DUGL_with_recovery.
1. Transfering the TWRP backup to the phone's storage
2. Flashing that backup just like flashing the custom ROM (it says Invalid zip file format. Error ect...) Please help
3. Flashing the recovery just like flashing the TWRP using adb commands
4. Lock the bootloader? I don't know how to do this.
Please advice
Thanks purple patch
dsymbol said:
ok so I downloaded TWRP_Backup_Untouched_System_Image_+_Boot_1.11.400.4_OCEAN_DUGL_with_recovery.
1. Transfering the TWRP backup to the phone's storage
2. Flashing that backup just like flashing the custom ROM (it says Invalid zip file format. Error ect...) Please help
3. Flashing the recovery just like flashing the TWRP using adb commands
4. Lock the bootloader? I don't know how to do this.
Please advice
Thanks purple patch
Click to expand...
Click to collapse
Get the one from here and follow instructions. That's what the thread is for. https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048. Sorry i don't have time to do the leg work for you (i'm out atm), but it's all there.
download this Official RRU firmware and install it https://forum.xda-developers.com/u11/how-to/unlocked-htc-u11-software-update-6-19-t3624814
Use the ruu, you might need the HTC drivers but in the future never not make a backup, 15 mins could save u a major headache
AllGamer said:
download this Official RRU firmware and install it https://forum.xda-developers.com/u11/how-to/unlocked-htc-u11-software-update-6-19-t3624814
Click to expand...
Click to collapse
I'm downloading it now & will report back very soon.
Thanks for the tip AllGamer!!!
AllGamer said:
download this Official RRU firmware and install it https://forum.xda-developers.com/u11/how-to/unlocked-htc-u11-software-update-6-19-t3624814
Click to expand...
Click to collapse
Finished downloading & now I got an ERROR installation, something like a wrong ROM, probably because I'm currently on LeeDroid custom ROM (Build 1.03.401.6.9_g CL923215)
Please advice
Thank you
dsymbol said:
Finished downloading & now I got an ERROR installation, something like a wrong ROM, probably because I'm currently on LeeDroid custom ROM (Build 1.03.401.6.9_g CL923215)
Please advice
Thank you
Click to expand...
Click to collapse
Your going to need a full signed RUU zip matching your original firmware and CID buddy.
Based on your original build number its an Indian dual SIM device so here is the ruu:
https://www.androidfilehost.com/?fid=817550096634780026
1. Rename it to 2PZCIMG.zip
2. Lock your bootloader
3. Drop the zip on your external SD card.
3. Boot to download mode, at that point you will be prompted to flash... Accept... Profit.
If you don't have an external SD.
1. Lock your bootloader.
2. Boot to download mode.
3. Open a cmd window and run the below commands.
fastboot orm rebootRUU (hit enter)
fastboot flash zip (drag the zip into the cmd window then hit enter)
dsymbol said:
Finished downloading & now I got an ERROR installation, something like a wrong ROM, probably because I'm currently on LeeDroid custom ROM (Build 1.03.401.6.9_g CL923215)
Please advice
Thank you
Click to expand...
Click to collapse
On the PC side, what was the exact error message?
you can ignore the warning from the phone side.
I had a similar issue the other day, but then I was able to run the RUU upgrade to rest my phone back to stock as I had to ship it back for a refund, to get the new Red ones
When I ran the RUU thing it wouldn't detect the phone, did a few things, and then it was finally able to detect the phone.
and when it started updating the Boot image it hung for a long while, I had to restart the phone back into download mode, then run the RUU again, and it was able to continue from there.
AllGamer said:
On the PC side, what was the exact error message?
you can ignore the warning from the phone side.
I had a similar issue the other day, but then I was able to run the RUU upgrade to rest my phone back to stock as I had to ship it back for a refund, to get the new Red ones
When I ran the RUU thing it wouldn't detect the phone, did a few things, and then it was finally able to detect the phone.
and when it started updating the Boot image it hung for a long while, I had to restart the phone back into download mode, then run the RUU again, and it was able to continue from there.
Click to expand...
Click to collapse
It says: ERROR [130]: MODEL ID ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
The previous screen says:
Verifying that you want to update
Image version 1.03.401.6
to
Image version 1.11.617.4
LeeDroid said:
Your going to need a full signed RUU zip matching your original firmware and CID buddy.
Based on your original build number its an Indian dual SIM device so here is the ruu:
https://www.androidfilehost.com/?fid=817550096634780026
1. Rename it to 2PZCIMG.zip
2. Lock your bootloader
3. Drop the zip on your external SD card.
3. Boot to download mode, at that point you will be prompted to flash... Accept... Profit.
Click to expand...
Click to collapse
I'm on it now & will report back!
Thank you Sir for joining the party. I have hope now
dsymbol said:
I'm on it now & will report back!
Thank you Sir for joining the party. I have hope now
Click to expand...
Click to collapse
Added an extra step incase you don't have an external sd
dsymbol said:
It says: ERROR [130]: MODEL ID ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
The previous screen says:
Verifying that you want to update
Image version 1.03.401.6
to
Image version 1.11.617.4
Click to expand...
Click to collapse
The 1.03.401.6 may be European software. You will need the RUU for your exact phone model from: http://www.htc.com/us/support/updates.aspx
or https://forum.xda-developers.com/u1...u-firmware-t3612048/post72425227#post72425227
michaelbsheldon said:
The 1.03.401.6 may be European software. You will need the RUU for your exact phone model from: http://www.htc.com/us/support/updates.aspx
or https://forum.xda-developers.com/u1...u-firmware-t3612048/post72425227#post72425227
Click to expand...
Click to collapse
I have linked the correct ruu in my post above as per the original firmware mentioned in the op
The correct build is 1.11.400.4
LeeDroid said:
I have linked the correct ruu in my post above as per the original firmware mentioned in the op
The correct build is 1.11.400.4
Click to expand...
Click to collapse
I have the ext. sdcard ready.
I have a question about locking the bootloader please
To lock the bootloader, I have to do this? (found instruction from google)
adb reboot bootloader
& type in 1 of these commands & stop there if it works?
fastboot oem lock
fastboot flashing lock
fastboot oem relock
Please advice
dsymbol said:
I have the ext. sdcard ready.
I have a question about locking the bootloader please
To lock the bootloader, I have to do this? (found instruction from google)
adb reboot bootloader
& type in 1 of these commands & stop there if it works?
fastboot oem lock
fastboot flashing lock
fastboot oem relock
Please advice
Click to expand...
Click to collapse
adb reboot download
fastboot oem lock
LeeDroid said:
adb reboot download
fastboot oem lock
Click to expand...
Click to collapse
Confirmation number: 5G354245BV234401U
Dear members
I want to update my rooted E6633 running 32.2.A.0.376 to 32.4.A.0.160 through the OTA, of course, because my device is already rooted the downloaded update couldn't be installed, the reason behind seeking for this update that I'm not able to make phone call and the phone is not able to detect the SIM cards and showing pop up error message android.phone.com has stopped repeatedly whenever I press ok and phone app crashes.
what I have done so far is through superus app I chose full unroot and the phone rebooted successfully and I have checked it with the root checker showing that the root is not installed properly
I launched the flashtool and booted the device on flashmood and selected the bootloader relock option
flashtool said that bootloader finished relocking the device, but the device is not able to boot to the normal mood whenever I push the power on button the device only vibrate or boots to flashmood when the cable is connected but when unlocking the bootloader, the device boots normally.
How to update my device without losing my current data and to fix phone application and SIMs recognition?
Do I have to fastboot the original Sony kernel and where can I find it? because I didn't make any backup
I don't mind losing root I just want to make the OTA update installed without flashing my phone and starting from the beginning.
Thank you
Notes: when the device is rooted again and when opening luckyputcher the error messages disappear and SIMs cards work fine and phone app opens normally
I will assume the reason you are not going for this is because of limited bandwidth or something along those lines.
You can either wait for someone to post a stock kernel of it but if you have a the .376 ftf you can extract the kernel using this guide (at step 3 you can flash the kernel using adb/fastboot)
Dna10 said:
I will assume the reason you are not going for this is because of limited bandwidth or something along those lines.
You can either wait for someone to post a stock kernel of it but if you have a the .376 ftf you can extract the kernel using this guide (at step 3 you can flash the kernel using adb/fastboot)
Click to expand...
Click to collapse
Thanks for your reply, not limited bandwidth but slow connection that one of the reasons, if I could extract the kernel from the firmware and flashing it without losing the data and allowing ota to be installed this will be great. Hopefully this way fixes the system errors and keeping the data and settings as it is.
Thanks again I will start following these guidelines if something went wrong surely I will sue you :laugh:
Ok I downloaded the ftf file, extracted kernel.sin
opened flashtool
I coudn't found the Dump Data option but I clicked on extract data inisted
I renamed the extracted kernel from elf to boot.img
I flashed the kernel using this command
fastboot boot boot.img
I got this error message : FAILED (remote: dtb not found)
so I relocked the bootloader and I got diffrent message : FAILED (status read failed (Too many links))
I went to flashtool and flasehd the kernel with no errors but the mobile did'nt boot, it's stuck on sony logo
what is the problem !?
kingskull said:
Ok I downloaded the ftf file, extracted kernel.sin
opened flashtool
I coudn't found the Dump Data option but I clicked on extract data inisted
I renamed the extracted kernel from elf to boot.img
I flashed the kernel using this command
fastboot boot boot.img
I got this error message : FAILED (remote: dtb not found)
so I relocked the bootloader and I got diffrent message : FAILED (status read failed (Too many links))
I went to flashtool and flasehd the kernel with no errors but the mobile did'nt boot, it's stuck on sony logo
what is the problem !?
Click to expand...
Click to collapse
Ok First Things First you should have used the command :
fastboot flash boot boot.img
Secondly to remedy to the problem flash the ftf BUT don't select anything in the wipe section, keep them all unchecked. Then you will have a stock and unrooted ROM without having lost your data.
Edit: If you were able to download that big of a file why didn't you go directly with the .106 fw? You would have had the same initial result you wanted! ::facepalm::
Dna10 said:
Ok First Things First you should have used the command :
fastboot flash boot boot.img
Secondly to remedy to the problem flash the ftf BUT don't select anything in the wipe section, keep them all unchecked. Then you will have a stock and unrooted ROM without having lost your data.
Edit: If you were able to download that big of a file why didn't you go directly with the .106 fw? You would have had the same initial result you wanted! ::facepalm::
Click to expand...
Click to collapse
I was not sure about flashing the whole ftf, I was worried if I flashed the the new 160 would cause the system to break down, so I decided to unroot and to keep my self on the safe side by unrooting, relocking bootloader and installing the stock kernel so that I will be able to update to the .160 fw through OTA
I will follow your instruction about flashing the .367 fw. I was thinking about it but I wasn't sure which options that should I select without losing the data. Should I select the whole options except the wipe section?
Thanks for your help
Don't select anything! It should look like in the screenshot I uploaded
Dna10 said:
Don't select anything! It should look like in the screenshot I uploaded
Click to expand...
Click to collapse
Hmmm yesterday before posting my last reply I flashed the firmware I only selected the kernel and nothing happened, no changes happened to the firmware except the ota size was reduced from 485mb to 187mb !?
Oh dear according to the screenshot you uploaded the ftf I downloaded is for middle east and I'm from Saudi Arabia never thought there is custom firmware for Saudi Arabia do you think that the reasone behind this boot failure is because of the difference between the installed firmware and the downloaded one?
It shouldn't pose any problems at all. Any problem arising might be of your doing. What you could do is make a Titanium Backup of your user apps and go for clean install if your problems persist.
Dna10 said:
Don't select anything! It should look like in the screenshot I uploaded
Click to expand...
Click to collapse
Ok that's great, after flashing the ftf the device boot normally but the bloody ass error still persist I can't make or receive phone calls the phone app is crashing, of course, since the root is not available luckypatcher will not solve the problem and to be honest I don't know what is the relation between this error and luckypatcher.
The funny thing after the process succeed the phone showing that the software is up to date man !!
more than that when checking software update settings app crashes
I really want to thank you for helping me, I really appreciate it :good:
my last option is downloading 160 fw and flashing it
Have you tried a different dialier app?
First Lock Bootloader Then Flash FTF File.