Related
My Razr maxx hd (xt926) had been rooted and bootloader unlocked sitting on version 9.16.9 for a while. With KitKat available I downloaded the 9.18.49 rom file and reset the phone flashing it with the Blur_Version.9.30.1.XT926.Verizon.en.US rom and getting everything back to stock. At this point it shows build 9.8.1Q I loaded the KK rom on the SD card and tried to flash from stock recovery.
During verification it aborts, with an error
expects build fingerprint of xt926_verizon/vanquish:4.1.2/9.8.1q-94/56:user release-keys
this device has xt926_verizon/vanquish:4.1.2/9.8.1q-94-1/57:user/r
Any thoughts on how to deal with this?
try this posted by @zachariahpope http://crackflasher.com/blur_version-9-18-94-xt926-verizon-en-us-zip-motorola-droid-razr-hd-cdma-livinginkaos/
billycar11 said:
try this posted by @zachariahpope http://crackflasher.com/blur_versio...zip-motorola-droid-razr-hd-cdma-livinginkaos/
Click to expand...
Click to collapse
That's the file I was trying to flash
Sent from my DROID RAZR HD using Tapatalk
samabuelsamid said:
That's the file I was trying to flash
Sent from my DROID RAZR HD using Tapatalk
Click to expand...
Click to collapse
okay then sorry i was confused try this one.
https://drive.google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/edit
posted by @Sabissimo
billycar11 said:
okay then sorry i was confused try this one.
https://drive.google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/edit
posted by @Sabissimo
Click to expand...
Click to collapse
Bad news. I flashed that one from recovery and it put my phone into a boot loop
Time to start over from scratch
samabuelsamid said:
Bad news. I flashed that one from recovery and it put my phone into a boot loop
Time to start over from scratch
Click to expand...
Click to collapse
I was reading that it rewrites your recovery. Go back into your recovery (should be a new version) and try to I stall again.
Yeah you need to install 2 times.
Did it install the recovery?
billycar11 said:
Yeah you need to install 2 times.
Did it install the recovery?
Click to expand...
Click to collapse
I'll let you know later tonight. I had to reflash back to where I was so I'd have a working phone for my workday.
samabuelsamid said:
I'll let you know later tonight. I had to reflash back to where I was so I'd have a working phone for my workday.
Click to expand...
Click to collapse
Definitely, the reboot during the install back into recovery is what confused a lot of us who were part of the soak test and tried to apply it manually ourselves.
When you first go into recovery and install the OTA, it will reboot. At that point, it will boot back to the recovery screen. There, you must press volume up + power. That is different from the old vol up+ vol down.
Anyways, once you are back in the "hard to read" recovery (why did they reduce the brightness on the new recovery?), you need to go back and install the OTA again. This time it will continue on where it left off and apply the KK update to your system.
Profit!
You might want to go to my post here (
http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1) and read some of the gotchas. Read them BEFORE you take the update so you don't bork your phone:
billycar11 said:
Yeah you need to install 2 times.
Did it install the recovery?
Click to expand...
Click to collapse
iBolski said:
Definitely, the reboot during the install back into recovery is what confused a lot of us who were part of the soak test and tried to apply it manually ourselves.
When you first go into recovery and install the OTA, it will reboot. At that point, it will boot back to the recovery screen. There, you must press volume up + power. That is different from the old vol up+ vol down.
Anyways, once you are back in the "hard to read" recovery (why did they reduce the brightness on the new recovery?), you need to go back and install the OTA again. This time it will continue on where it left off and apply the KK update to your system.
Profit!
You might want to go to my post here (
http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1) and read some of the gotchas. Read them BEFORE you take the update so you don't bork your phone:
Click to expand...
Click to collapse
Thanks, I'll provide an update of how this works!
iBolski said:
Definitely, the reboot during the install back into recovery is what confused a lot of us who were part of the soak test and tried to apply it manually ourselves.
When you first go into recovery and install the OTA, it will reboot. At that point, it will boot back to the recovery screen. There, you must press volume up + power. That is different from the old vol up+ vol down.
Anyways, once you are back in the "hard to read" recovery (why did they reduce the brightness on the new recovery?), you need to go back and install the OTA again. This time it will continue on where it left off and apply the KK update to your system.
Profit!
You might want to go to my post here (
http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1) and read some of the gotchas. Read them BEFORE you take the update so you don't bork your phone:
Click to expand...
Click to collapse
This all worked perfectly and I'm now rocking KitKat
iBolski said:
Definitely, the reboot during the install back into recovery is what confused a lot of us who were part of the soak test and tried to apply it manually ourselves.
When you first go into recovery and install the OTA, it will reboot. At that point, it will boot back to the recovery screen. There, you must press volume up + power. That is different from the old vol up+ vol down.
Anyways, once you are back in the "hard to read" recovery (why did they reduce the brightness on the new recovery?), you need to go back and install the OTA again. This time it will continue on where it left off and apply the KK update to your system.
Profit!
You might want to go to my post here (
http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1) and read some of the gotchas. Read them BEFORE you take the update so you don't bork your phone:
Click to expand...
Click to collapse
One other question: My bootloader is unlocked, I'm trying to find the directions to root again under kitkat by manually sideloading. Anyone have a link?
samabuelsamid said:
One other question: My bootloader is unlocked, I'm trying to find the directions to root again under kitkat by manually sideloading. Anyone have a link?
Click to expand...
Click to collapse
All you need to do is flash CWM and then find a sideloadable SU package to sideload under CWM. That's it.
iBolski said:
All you need to do is flash CWM and then find a sideloadable SU package to sideload under CWM. That's it.
Click to expand...
Click to collapse
Thanks. Just a couple more questions before I do this to make sure I don't send my phone back into oblivion and have to start all over again. Is the CWM recovery specific to any particular version of Android, current one available for XT926 on clockworkmod.com download page is 6.0.4.4. Similarly, does SU need to be specific to this phone/KitKat rom?
I've rooted numerous phones before, always using a script like Razr Hd utility. This is my first attempt at manual root so I appreciate your patience
samabuelsamid said:
Thanks. Just a couple more questions before I do this to make sure I don't send my phone back into oblivion and have to start all over again. Is the CWM recovery specific to any particular version of Android, current one available for XT926 on clockworkmod.com download page is 6.0.4.4. Similarly, does SU need to be specific to this phone/KitKat rom?
I've rooted numerous phones before, always using a script like Razr Hd utility. This is my first attempt at manual root so I appreciate your patience
Click to expand...
Click to collapse
You need to download the new CWM for KK. xt926-KK-CWM-6048.img is the name. You can get it from here: http://forum.xda-developers.com/showpost.php?p=52564336&postcount=1
iBolski said:
You need to download the new CWM for KK. xt926-KK-CWM-6048.img is the name. You can get it from here: http://forum.xda-developers.com/showpost.php?p=52564336&postcount=1
Click to expand...
Click to collapse
good thing I asked first
Update: not rooted on KitKat!
samabuelsamid said:
My Razr maxx hd (xt926) had been rooted and bootloader unlocked sitting on version 9.16.9 for a while. With KitKat available I downloaded the 9.18.49 rom file and reset the phone flashing it with the Blur_Version.9.30.1.XT926.Verizon.en.US rom and getting everything back to stock. At this point it shows build 9.8.1Q I loaded the KK rom on the SD card and tried to flash from stock recovery.
During verification it aborts, with an error
expects build fingerprint of xt926_verizon/vanquish:4.1.2/9.8.1q-94/56:user release-keys
this device has xt926_verizon/vanquish:4.1.2/9.8.1q-94-1/57:user/r
Any thoughts on how to deal with this?
Click to expand...
Click to collapse
I have the same problem, but I'm getting the error message that expects your device. What was the image that you used? I have the vanquish:4.1.2/9.8
1Q-94/56:user.
samabuelsamid said:
good thing I asked first
Update: not rooted on KitKat!
Click to expand...
Click to collapse
Then you cannot use CWM and there is no safe strap for KK.
Also, root is now lost, but SamuriHL is working on a theory that might work. Unfortunately, it requires locked phones that have NOT taken the soak or OTA yet and we have to wait for the official KK FXZ image file before he can continue. If the phone has had the OTA or soak applied to it, then it can't be part of the test.
iBolski said:
Then you cannot use CWM and there is no safe strap for KK.
Also, root is now lost, but SamuriHL is working on a theory that might work. Unfortunately, it requires locked phones that have NOT taken the soak or OTA yet and we have to wait for the official KK FXZ image file before he can continue. If the phone has had the OTA or soak applied to it, then it can't be part of the test.
Click to expand...
Click to collapse
Sorry, that should have read NOW rooted. CWM worked fine as did Koush's superuser
samabuelsamid said:
Sorry, that should have read NOW rooted. CWM worked fine as did Koush's superuser
Click to expand...
Click to collapse
you know what, color me stupid.
I've been helping so many people that when I read "no root", I interpreted it as "locked bootloader".
My bad.
I have rooted my OnePlus One a few days back. There was an update to 11.0-XNPH30O. When I hit the install button, it redirects me to the Team Win recovery mode. Then when I hit reboot, system. It still says "An update is available for your system" Do I have to flash a newer ROM? I'm sorry, I am really new to this as this is my first android phone, what are the precautions and pre-requisites I have to do? Will this wipe my phone? Do I have to manually wipe it? I'm sorry for these questions..
Thank you in advance.
skyhonor said:
I have rooted my OnePlus One a few days back. There was an update to 11.0-XNPH30O. When I hit the install button, it redirects me to the Team Win recovery mode. Then when I hit reboot, system. It still says "An update is available for your system" Do I have to flash a newer ROM? I'm sorry, I am really new to this as this is my first android phone, what are the precautions and pre-requisites I have to do? Will this wipe my phone? Do I have to manually wipe it? I'm sorry for these questions..
Thank you in advance.
Click to expand...
Click to collapse
Did you check the current build on the phone, because there are two OTA's (one major and one minor). if you see 30O build on your about settings and yet you see an update available it is the small update. if you are still on 25R go to developer options and uncheck "update CM recovery" and try to do the OTA update again.
vamshi88 said:
Did you check the current build on the phone, because there are two OTA's (one major and one minor). if you see 30O build on your about settings and yet you see an update available it is the small update. if you are still on 25R go to developer options and uncheck "update CM recovery" and try to do the OTA update again.
Click to expand...
Click to collapse
I am still on 25R, the update CM Recovery option was unchecked and when I went to install update, it says XNPH30O Incremental. I press install update and it boots me to the TeamWin recovery
skyhonor said:
I am still on 25R, the update CM Recovery option was unchecked and when I went to install update, it says XNPH30O Incremental. I press install update and it boots me to the TeamWin recovery
Click to expand...
Click to collapse
why not just sideload the incremental. you can find the zip here.
http://forum.xda-developers.com/oneplus-one/general/cm-11s-30o-ota-slowly-rolling-t2844689
vamshi88 said:
why not just sideload the incremental. you can find the zip here.
http://forum.xda-developers.com/oneplus-one/general/cm-11s-30o-ota-slowly-rolling-t2844689
Click to expand...
Click to collapse
Will I have to wipe my phone first? I don't want to wipe it though.
skyhonor said:
Will I have to wipe my phone first? I don't want to wipe it though.
Click to expand...
Click to collapse
No you dont have to wipe anything(if you are on stock 25R), all apps and settings will be intact. Also did you make any changes like to mixer xml or lockscreen or anything else? you have to revert back to old ones or else the installation will fail.
vamshi88 said:
No you dont have to wipe anything(if you are on stock 25R), all apps and settings will be intact. Also did you make any changes like to mixer xml or lockscreen or anything else? you have to revert back to old ones or else the installation will fail.
Click to expand...
Click to collapse
I don't think so, but I did install nova theme and widgets, franco.kernel, smoothscrolling mod, and the 1+Volume Increase, will this affect anything? What is the difference between stock 25R and twrp? (I used twrp to root my phone) Also, what do you mean by "or else the installation will fail?" does that equal bricking phone or there will be a message that says "the installation has failed."
Thanks.
skyhonor said:
I don't think so, but I did install nova theme and widgets, franco.kernel, smoothscrolling mod, and the 1+Volume Increase, will this affect anything? What is the difference between stock 25R and twrp? (I used twrp to root my phone) Also, what do you mean by "or else the installation will fail?" does that equal bricking phone or there will be a message that says "the installation has failed."
Thanks.
Click to expand...
Click to collapse
the "franco.kernel, smoothscrolling mod, and the 1+Volume Increase" are mods so you will have to revert back to stock. if you dont want to/know how to revert back to stock then this thread can help you.
http://forum.xda-developers.com/oneplus-one/general/ota-8-17-cm11sfixed-zip-ota-to-stock-t2845075
Before you do anything read step 6 in this post just to understand what you are doing.
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
after reading the thread if you need any help let me know.
vamshi88 said:
the "franco.kernel, smoothscrolling mod, and the 1+Volume Increase" are mods so you will have to revert back to stock. if you dont want to/know how to revert back to stock then this thread can help you.
http://forum.xda-developers.com/oneplus-one/general/ota-8-17-cm11sfixed-zip-ota-to-stock-t2845075
Before you do anything read step 6 in this post just to understand what you are doing.
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
after reading the thread if you need any help let me know.
Click to expand...
Click to collapse
I have read it but it kind of confuses me a bit.
I have already flashed the META-INF.zip, so I'm guessing all the mods I put should be gone now.
Now I'm wondering, can I just transfer the cm-bacon-d22b777afa-to-0428073396-signed.zip (113mb file) to the phone and install it using TeamWin? After I reboot and power off/and power back on. then transfer the cm-bacon-0428073396-to-4f280f505a-signed.zip (8.12mb file) to the phone and install it using TeamWin.
Will this work too? Thank you for helping, really means a lot.
skyhonor said:
I have read it but it kind of confuses me a bit.
I have already flashed the META-INF.zip, so I'm guessing all the mods I put should be gone now.
Now I'm wondering, can I just transfer the cm-bacon-d22b777afa-to-0428073396-signed.zip (113mb file) to the phone and install it using TeamWin? After I reboot and power off/and power back on. then transfer the cm-bacon-0428073396-to-4f280f505a-signed.zip (8.12mb file) to the phone and install it using TeamWin.
Will this work too? Thank you for helping, really means a lot.
Click to expand...
Click to collapse
Before you do anything Take a Nandroid back up, so that if anything goes bad you can just restore.
OK. Just download this zip and flash it using TWRP(since the post says you can do it without sideload).
https://docs.google.com/file/d/0BzgUrWZ7XZ0rcDA2YVZLZUY0YkU/edit
after this is flashed just reboot the device and go to developer options uncheck "update CM recovery" then go to "about" and look for update and it will be installed with no problems.
****NOTE****
If you run into a bootloop. Wipe both caches and try flashing again. If you get any FC then try setting permissions with another cache wipe.
vamshi88 said:
Before you do anything Take a Nandroid back up, so that if anything goes bad you can just restore.
OK. Just download this zip and flash it using TWRP(since the post says you can do it without sideload).
https://docs.google.com/file/d/0BzgUrWZ7XZ0rcDA2YVZLZUY0YkU/edit
after this is flashed just reboot the device and go to developer options uncheck "update CM recovery" then go to "about" and look for update and it will be installed with no problems.
****NOTE****
If you run into a bootloop. Wipe both caches and try flashing again. If you get any FC then try setting permissions with another cache wipe.
Click to expand...
Click to collapse
It said sideloading 100% in the command prompt (PC. But It says sideload failed on the phone, I will try flashing it using TWRP, a bit later. Thank you for helping.
vamshi88 said:
Before you do anything Take a Nandroid back up, so that if anything goes bad you can just restore.
OK. Just download this zip and flash it using TWRP(since the post says you can do it without sideload).
https://docs.google.com/file/d/0BzgUrWZ7XZ0rcDA2YVZLZUY0YkU/edit
after this is flashed just reboot the device and go to developer options uncheck "update CM recovery" then go to "about" and look for update and it will be installed with no problems.
****NOTE****
If you run into a bootloop. Wipe both caches and try flashing again. If you get any FC then try setting permissions with another cache wipe.
Click to expand...
Click to collapse
I ran into a bootloop like you predicted, how do I wipe both caches?
skyhonor said:
I ran into a bootloop like you predicted, how do I wipe both caches?
Click to expand...
Click to collapse
In TWRP go to WIPE>Advanced Wipe, in there check cache and Dalvik cache and swipe to wipe and reboot.
vamshi88 said:
In TWRP go to WIPE>Advanced Wipe, in there check cache and Dalvik cache and swipe to wipe and reboot.
Click to expand...
Click to collapse
It's not a bootloop the CM gear icon just keeps on spinning. How long do I have to wait? It's been spinning for a while now.
skyhonor said:
It's not a bootloop the CM gear icon just keeps on spinning. How long do I have to wait? It's been spinning for a while now.
Click to expand...
Click to collapse
TeamWin is still accessible though. I guess I'll have to Factory reset.
skyhonor said:
It's not a bootloop the CM gear icon just keeps on spinning. How long do I have to wait? It's been spinning for a while now.
Click to expand...
Click to collapse
it shouldn't take long, leave it for 10mins. if it is still stuck hold the power button for 10 sec or untill the screen goes off then hold power + volume down button untill 1+ logo appears then clear the caches as said above.
vamshi88 said:
it shouldn't take long, leave it for 10mins. if it is still stuck hold the power button for 10 sec or untill the screen goes off then hold power + volume down button untill 1+ logo appears then clear the caches as said above.
Click to expand...
Click to collapse
Okay I will come back in 10 minutes.
skyhonor said:
Okay I will come back in 10 minutes.
Click to expand...
Click to collapse
It has been over 15 minutes... I think I'm experiencing what is called a soft brick? What can I do. I'm somewhat in panic mode.:crying:
skyhonor said:
It has been over 15 minutes... I think I'm experiencing what is called a soft brick? What can I do. I'm somewhat in panic mode.:crying:
Click to expand...
Click to collapse
did you power it off as i said.
vamshi88 said:
did you power it off as i said.
Click to expand...
Click to collapse
yes device is powered off now. I didn't do a Nandroid backup because I have titanium backup.
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
Hey there fellow U11 Users,
I just received the update concerning 60fps HD-Video etc. I use TWRP so the update can't be installed by itself. So I have two questions:
A
Where do I find the update file. I looked around a lot but couldn't locate it.
B
Once found, can I just flash it with TWRP?
Thanks in advance!
Dito13 said:
Hey there fellow U11 Users,
I just received the update concerning 60fps HD-Video etc. I use TWRP so the update can't be installed by itself. So I have two questions:
A
Where do I find the update file. I looked around a lot but couldn't locate it.
B
Once found, can I just flash it with TWRP?
Thanks in advance!
Click to expand...
Click to collapse
See here: https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048/page63
Alright, thanks! :good: That only leaves the first question unanswered.
Dito13 said:
Alright, thanks! :good: That only leaves the first question unanswered.
Click to expand...
Click to collapse
/data/data/com.htc.updater/files
btw...twrp can install the update but you need to flash the firmware.zip inside the ota manually
Thank you kindly!
OMJ said:
/data/data/com.htc.updater/files
btw...twrp can install the update but you need to flash the firmware.zip inside the ota manually
Click to expand...
Click to collapse
Just to be clear: I only flash the firmware.zip manually via TWRP or do I need to flash the whole ota?
Sorry for the question. I mostly handled Nexus devices...
Dito13 said:
Just to be clear: I only flash the firmware.zip manually via TWRP or do I need to flash the whole ota?
Sorry for the question. I mostly handled Nexus devices...
Click to expand...
Click to collapse
twrp will install the ota zip but it wont install the firmware.zip inside, you have to extract & manually install from download mode
grrr.... I tried following your suggestions, but recieved error 7 in TWRP. Can you help me in the right direction?
Dito13 said:
grrr.... I tried following your suggestions, but recieved error 7 in TWRP. Can you help me in the right direction?
Click to expand...
Click to collapse
list your steps your using to install the ota via twrp....personally, I let the system initiate the install (booted into OS) as if I was 100% stock, once twrp loads, it automatically installs except for the firmware.zip
more details here...
OK, I am a Noob to the HTC world. I am used to easy flashing/rooting/etc. on Nexus devices.
TWRP doesn't do anything after accepting the ota. When I try to install the OTA via TWRP I receive Error 7. I worked my way through a lot of guides here on XDA concerning manual OTA installing. One thing I tried was flashing back to stock recovery which I found in the firmware.zip of the OTA in bootloader mode. That failed also ("FAILED (remote: not allowed on PRODUCTION device).
Edit: The device has obviously an unlocked bootloader, s-on, rooted via magisk and is a DGLU device, software number 1.16.400.5
Are you on an Untouched System Image? Completely stock ROM? While it is great we can flash the OTA in TWRP, the system stills needs to be stock, and of course will still have to fastboot firmware.
schmeggy929 said:
Are you on an Untouched System Image? Completely stock ROM? While it is great we can flash the OTA in TWRP, the system stills needs to be stock, and of course will still have to fastboot firmware.
Click to expand...
Click to collapse
Yes, everything is stock.
I managed to flash the stock recovery now. I didn't remember to use the download mode /sorry. Then Then I checked for the ota again, downloaded it and tried to apply but I landed in the stock recovery with the red exclamation mark and then nothing happened.
Dito13 said:
Yes, everything is stock.
I managed to flash the stock recovery now. I didn't remember to use the download mode /sorry. Then Then I checked for the ota again, downloaded it and tried to apply but I landed in the stock recovery with the red exclamation mark and then nothing happened.
Click to expand...
Click to collapse
re-flash twrp and try it again.
schmeggy929 said:
re-flash twrp and try it again.
Click to expand...
Click to collapse
Same result unfortunately. TWRP hands out Error 7 and "system partition has unexpected contents" or something like that although I didn't do any tinkering with the stock rom. I flashed Magisk and did a backup before and that was all.
Dito13 said:
Same result unfortunately. TWRP hands out Error 7 and "system partition has unexpected contents" or something like that although I didn't do any tinkering with the stock rom. I flashed Magisk and did a backup before and that was all.
Click to expand...
Click to collapse
Only thing I would say is start fresh. Backup all the data for your apps first. Flash the RUU, Take the OTA and reinstall all your apps.
schmeggy929 said:
Only thing I would say is start fresh. Backup all the data for your apps first. Flash the RUU, Take the OTA and reinstall all your apps.
Click to expand...
Click to collapse
Thanks again - seems to have worked. It will be interesting to see which problems occur with the Android Oreo update which was announced till the end of the year by HTC
Hi everyone!
Issue is pretty simple to explain - after upgrading via OTA from the latest open beta Pie (29) to open beta Android 10 (30), I can't boot into recovery.
System works normally, the only thing I'm having trouble with are the generic issues discussed on the OP community forum (autorotate and other sensors, Gboard gap...). It is recommended repeatedly that one should reboot to recovery and wipe the cache partition.
The problem is that I can only get into fastboot mode - tried the advanced boot menu, adb/fastboot and selecting recovery mode while in the fastboot mode but it always goes into fastboot.
TWRP doesn't support android 10 yet as far as I know and I've found no other reference of this issue anywhere else. Only thing that comes to mind is to wait for the next open beta and hope it will be resolved after another OTA.
Thanks for your help!
seems the open beta install was more bad for you than mine. Upgraded from op29 to op30 like you, but i had everything stock. No unlocked bootloader, no big customizations, etc. I just tried entering recovery mode via fastboot and it worked like normal for me, had to enter my pin to decrypt my data, and the rest like normal. I'd suggest to downgrade back to pie and reflash the open beta software to see if the issue is gone or not, but that's your call to do so.
HighOnLinux said:
seems the open beta install was more bad for you than mine. Upgraded from op29 to op30 like you, but i had everything stock. No unlocked bootloader, no big customizations, etc. I just tried entering recovery mode via fastboot and it worked like normal for me, had to enter my pin to decrypt my data, and the rest like normal. I'd suggest to downgrade back to pie and reflash the open beta software to see if the issue is gone or not, but that's your call to do so.
Click to expand...
Click to collapse
I think you stumbled across the answer everyone has been searching for. How did you upgrade? Did you download the whole zip and flash through updated?
This kinda makes sense. Do you remember how big the update file was? It could have been an incremental rather than a full if you weren't unlocked and thus (maybe) didn't change fastboot.
verbatim7 said:
Hi everyone!
Issue is pretty simple to explain - after upgrading via OTA from the latest open beta Pie (29) to open beta Android 10 (30), I can't boot into recovery.
System works normally, the only thing I'm having trouble with are the generic issues discussed on the OP community forum (autorotate and other sensors, Gboard gap...). It is recommended repeatedly that one should reboot to recovery and wipe the cache partition.
The problem is that I can only get into fastboot mode - tried the advanced boot menu, adb/fastboot and selecting recovery mode while in the fastboot mode but it always goes into fastboot.
TWRP doesn't support android 10 yet as far as I know and I've found no other reference of this issue anywhere else. Only thing that comes to mind is to wait for the next open beta and hope it will be resolved after another OTA.
Thanks for your help!
Click to expand...
Click to collapse
Had read somewhere that flashing stock boot.img will help restore stock recovery.. Have you tried doing that
brashmadcap said:
I think you stumbled across the answer everyone has been searching for. How did you upgrade? Did you download the whole zip and flash through updated?
This kinda makes sense. Do you remember how big the update file was? It could have been an incremental rather than a full if you weren't unlocked and thus (maybe) didn't change fastboot.
Click to expand...
Click to collapse
i grabbed the update file from this news article from xda itself: https://www.xda-developers.com/oneplus-android-10-oxygenos-beta-oneplus-6-6t/
the update zip was the full update and not incremental. i updated my device using the local device upgrader found under the system update settings to do the job for me.
Edit: this part down was meant for OP, sorry for confusion
so far when i updated last night, the auto rotate was tripping, until you mentioned that wiping the cache should do the trick (and it did do the trick thanks for that).
But back to your problem, you should try flashing the file under the link i put into this reply and if it doesn't work, just back up your data, downgrade back to pie, and flash the full update file that is present within that article and you should be back to normal
HighOnLinux said:
i grabbed the update file from this news article from xda itself: https://www.xda-developers.com/oneplus-android-10-oxygenos-beta-oneplus-6-6t/
the update zip was the full update and not incremental. i updated my device using the local device upgrader found under the system update settings to do the job for me. so far when i updated last night, the auto rotate was tripping, until you mentioned that wiping the cache should do the trick (and it did do the trick thanks for that).
But back to your problem, you should try flashing the file under the link i put into this reply and if it doesn't work, just back up your data, downgrade back to pie, and flash the full update file that is present within that article and you should be back to normal
Click to expand...
Click to collapse
Thanks for the idea. Unfortunately, it seems that having root and having recovery isn't possible for me at this point.
I've installed the OTA, got the recovery back and managed to wipe cache and everything worked - except I didn't have root. Then I've installed the magisk boot image to get back root, but then the same issues started happening and I was unable to access recovery.
Now I have to decide what's more important :crying:
Use an older version of magisk and you won't lose twrp
verbatim7 said:
Thanks for the idea. Unfortunately, it seems that having root and having recovery isn't possible for me at this point.
I've installed the OTA, got the recovery back and managed to wipe cache and everything worked - except I didn't have root. Then I've installed the magisk boot image to get back root, but then the same issues started happening and I was unable to access recovery.
Now I have to decide what's more important :crying:
Click to expand...
Click to collapse
how did u get back the recovery?
LazerH said:
how did u get back the recovery?
Click to expand...
Click to collapse
As stated above - just downloaded the OTA Android 10 update file for the right device, installed it and didn't install magisk to inactive slot and I had it back. If I tried to install magisk to keep root I didn't have the recovery mode. My guest guess is that magisk still isn't fully compatible with the new Android 10 boot changes.
verbatim7 said:
Thanks for the idea. Unfortunately, it seems that having root and having recovery isn't possible for me at this point.
I've installed the OTA, got the recovery back and managed to wipe cache and everything worked - except I didn't have root. Then I've installed the magisk boot image to get back root, but then the same issues started happening and I was unable to access recovery.
Now I have to decide what's more important :crying:
Click to expand...
Click to collapse
To me having a stable phone is much more important than a heavily modified device that's unstable at any given time. I'd say use the msm tool, flash back to a fresh build of pie, download the full open beta 30 zip, after its done flashing, reboot twice to iron out any present issues, then unlock the bootloader, and then you should be good to go. If you want root, just fastboot boot into twrp and flash the latest magisk zip and you're good to go. At the end you should have root, an unlocked bootloader, all while on the open beta android 10 build, with access to the stock recovery
Can u guys help me please, i just flashed by mistake with " fastboot flash boot" a TWRP enchilada file and now i'm stuck in fastboot and i cant boot ...i dont know how to factory reset or flash firmware from fastboot (
terrorblade23 said:
Can u guys help me please, i just flashed by mistake with " fastboot flash boot" a TWRP enchilada file and now i'm stuck in fastboot and i cant boot ...i dont know how to factory reset or flash firmware from fastboot (
Click to expand...
Click to collapse
Had the same problem. Flash this one: https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
OOS 10 Open Beta 1 Stock Boot
Schnullifax said:
Had the same problem. Flash this one: https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
OOS 10 Open Beta 1 Stock Boot
Click to expand...
Click to collapse
thanks..this is what i was looking for ...the problem is that now i'm in a boot loop , the dots keep spinning 4ever...and i did factory reset it from recovery
up1: i managed to install on slot a (i guess) Twrp.. but the whole memory is empty and i cant place anything (firmware) with pc on phone
formated data from twrp (to some format ntfc4 or smth like that ) and installed back android q and is working .