[Q] Still no update available - Acer Iconia A700 and A510

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!

Related

Cant install Ota Update

Hey friends.
I've got a little Problem.
At first I've some wifi issues of my one s.
Today I got the message, that there is an Ota update. I hoped, that it fixes the wifi issues (disconnect in standby and doesn't reconnect after wake up).
I've the official shipped Rom with opened hboot and root. I rooted it for apps like addblocker.
So after I downloaded my update the phone turned of to install it. Started in recovery where it aborted.
I think it is why I installed Cwm for root.
Is there a way how to install the update? Maybe to reinstall the original recovery?
I don't really want to install a custom rom.
Thanks a lot
sk1786 said:
Hey friends.
I've got a little Problem.
At first I've some wifi issues of my one s.
Today I got the message, that there is an Ota update. I hoped, that it fixes the wifi issues (disconnect in standby and doesn't reconnect after wake up).
I've the official shipped Rom with opened hboot and root. I rooted it for apps like addblocker.
So after I downloaded my update the phone turned of to install it. Started in recovery where it aborted.
I think it is why I installed Cwm for root.
Is there a way how to install the update? Maybe to reinstall the original recovery?
I don't really want to install a custom rom.
Thanks a lot
Click to expand...
Click to collapse
If the bootloader is unlocked, relock it through the HTC One S Toolkit. Also, I might just be able to find a .img file of the stock recovery for you. I will look now.
EDIT: I have attached the stock recovery file. Rename it to "recovery.img" (without the quotes) and flash it in fastboot (replace the obviously fake names with the actual directories):
Code:
cd /sdk/platform-tools (or whatever you keep fastboot and adb in)
adb reboot bootloader (or boot into it manually and skip this)
fastboot devices (just to verify)
fastboot flash recovery recovery.img (it'll say a lot of crap and then tell you when it's copied)
fastboot reboot (or you can go back to the bootloader and get into recovery from there and skip this step)
Also, I have included a picture of a lion. Why? Because I can.
EDIT2: The recovery was to big to upload so I put it on mediafire: http://www.mediafire.com/?unfu1p66545xu7z
sk1786 said:
So after I downloaded my update the phone turned of to install it. Started in recovery where it aborted.
I think it is why I installed Cwm for root.
Is there a way how to install the update? Maybe to reinstall the original recovery?
I don't really want to install a custom rom.
Thanks a lot
Click to expand...
Click to collapse
Yes you need to install stock recovery for OTA update to work.
Use OTA Rootkeeper to save your root file or you will loose root after the update.
Thank you auf lot I'll try it today.
Edit: Didn't had to relock my bootloader. Only did your Fastboot-Instructions and run the Voodoo OTA Rootkeeper. Now everything works fine.

Q A700: Is it possible to lock an unlocked A700?

As I have no succes in installing the OTA update for my A700, and cant get the solution offered somewhere else here to work, i have a question:
Is it possible to lock an unlocked A700 again? After which - i think - it should be able to install the OTA.
Anyone here knows if this is possible?
I was in the same situation, until I flashed an emea_cus1 version. I hope you get this answered, or someone comes up with a flashable pa_cus1 version.
Consider this a bump...
Sent from my A700 using XDA Premium HD app
Can you or anyone tell me what is the difference between emea_cus1 & pa_cus1 versions?
As above, anyone with flashable pa_cus1 version?
i heard that 'unlock' is unrecoverable. Maybe it's work if you can use Flash Tool to flash the whole system by computer.
but there'r no any resources available by now.
I had to do this myself a couple days back so I could return to stock. I made this quick link-list.
1. Get Android SDK & the official Acer USB Drivers http://developer.android.com/sdk/index.html http://support.acer.com/us/en/product/default.aspx?tab=1&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 recovery.img using the BAT file from this post. IMPORTANT! DO NOT INSTALL THE recovery.img FROM THAT LINK! It will brick you. Replace it with the one from the thread above (6.0.1.0).
4. Download the appropriate ROM for your device. You'll want the first CUS1 as it is 1.0.29: http://forum.xda-developers.com/showthread.php?t=1729692
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 (I just noticed the post was updated after I messaged him). http://forum.xda-developers.com/sho...m.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.
ExtremeRyno said:
I had to do this myself a couple days back so I could return to stock. I made this quick link-list.
1. Get Android SDK & the official Acer USB Drivers http://developer.android.com/sdk/index.html http://support.acer.com/us/en/product/default.aspx?tab=1&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 recovery.img using the BAT file from this post. IMPORTANT! DO NOT INSTALL THE recovery.img FROM THAT LINK! It will brick you. Replace it with the one from the thread above (6.0.1.0).
4. Download the appropriate ROM for your device. You'll want the first CUS1 as it is 1.0.29: http://forum.xda-developers.com/showthread.php?t=1729692
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 (I just noticed the post was updated after I messaged him). http://forum.xda-developers.com/sho...m.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 for your answer. Now I just am left with one question. I have image version Acer_AV043_A700_1.026.00_WW_GEN1
The CUS1 you mention can be flashed over that without a problem, after which I should be able to use the OTA from Acer?
CheopsChefren said:
Thanks for your answer. Now I just am left with one question. I have image version Acer_AV043_A700_1.026.00_WW_GEN1
The CUS1 you mention can be flashed over that without a problem, after which I should be able to use the OTA from Acer?
Click to expand...
Click to collapse
Whoops..I originally posted this on another forum where someone asked the same question. They had the US tablet. Get the appropriate file for your country/device. After you flash your country's stock, you will be able to get OTA updates. This relocks and unroots your device back like new.
ExtremeRyno said:
Whoops..I originally posted this on another forum where someone asked the same question. They had the US tablet. Get the appropriate file for your country/device. After you flash your country's stock, you will be able to get OTA updates. This relocks and unroots your device back like new.
Click to expand...
Click to collapse
i need to take my a701 back to acer so i have flashed my a701 back to ICS with Acer_AV043_A701_1.015.00_WW_GEN1 (got from somewhere in this forum i think, i forgot ... sorry). the process went without any trouble.
but my bootloader is still unlock.
when i try the fastboot oem lock .. it showed the lock lock and the door icon on the display ... choose the lock ... and the display show "Please wait.."
wait for more than half an hour .. still "Please wait" and i decided to turnoff the device.
my question is how long does it take to relock (fastboot oem lock) the bootloader? please advice. Thanks

Recommendations on OTA (ATT 4.0.3/4.0/1.73)

Hey all,
I rooted my HOX (1.73, 4.0.3) with the kpenn ne-Click a few days after I got it for the Tether and to de-bloat. Since then I haven't read anything on the One X till I heard Jelly Bean coming along. Anyhoo my question is what the upside of getting the new OTA (4.0.4) would be and how I would go about it if I wanted to (I've never updated before and ATT has stopped asking me to update, also I get nothing when I try to check for an update).
I've been reading around and it seems like most people are on to 1.85 and are flashing 4.1/2.2. My primary uses of my phone are for the media applications/web browsing and I haven't noticed any real drop in performance but I have heard the new updates have sped up the HOX considerably which is something I'm always interested in.
Thanks!
DON'T flash any OTA you will lose your root and will lose your ability to re root because there is no boot loader unlock for the new base. If you want to update and flash a new ROM and want to stick to sense, look at clean rom or xi40. Both are updated on the new base and are heaps and bounds better than the original ATT software :thumbup:
Shaddy-Z. said:
DON'T flash any OTA you will lose your root and will lose your ability to re root because there is no boot loader unlock for the new base. If you want to update and flash a new ROM and want to stick to sense, look at clean rom or xi40. Both are updated on the new base and are heaps and bounds better than the original ATT software :thumbup:
Click to expand...
Click to collapse
i one-clicked unrooted my phone earlier and freaked out (and the new updates didn't work out on my phone anyway). i ended up getting kpenn's one click again and putting SU back into my phone. Do you have any links that can take me on a step by step process of unlocking my phone and flashing those roms on it? I just love being able to control my phone and pushing it to its absolute limits.
Sigh. I followed the tutorial but I made a few mistakes...
1) I unlocked my phone way earlier than I should have so I wiped everything before I could make a back-up..
2) Re-locked accordingly to see if I could keep updating. I did manage to get to 1.85 like the tutorial said but.....
3) Since I didn't have a custom recovery I wasn't sure how to proceed. I couldn't get the root to flash so I tried using the 1-click 1.85 root since my phone was running 1.85.
....This ended up updating to 2.2 so now I have an unlocked HOX 2.2/4.0.4. With all the bloat.
Dumb dumb dumb. Ugh.
Pbdeng said:
Sigh. I followed the tutorial but I made a few mistakes...
1) I unlocked my phone way earlier than I should have so I wiped everything before I could make a back-up..
2) Re-locked accordingly to see if I could keep updating. I did manage to get to 1.85 like the tutorial said but.....
3) Since I didn't have a custom recovery I wasn't sure how to proceed. I couldn't get the root to flash so I tried using the 1-click 1.85 root since my phone was running 1.85.
....This ended up updating to 2.2 so now I have an unlocked HOX 2.2/4.0.4. With all the bloat.
Dumb dumb dumb. Ugh.
Click to expand...
Click to collapse
it's UNLOCKED?
you're lucky then.
just push a recovery like twrp then push root. Then you can debloat.
Yep, it's still unlocked. That was around the 4-7th reset I did (I messed up a lot). Do you have a link that shows me how to do that? I'm actually not as bummed about going to 2.2 since it runs so much faster than 1.73 did.
Pbdeng said:
Yep, it's still unlocked. That was around the 4-7th reset I did (I messed up a lot). Do you have a link that shows me how to do that? I'm actually not as bummed about going to 2.2 since it runs so much faster than 1.73 did.
Click to expand...
Click to collapse
make sure you have your unlock token and then go to http://www.htcdev.com/bootloader/unlock-instructions/page-4/
and follow the directions.
after that look at this thread to install twrp http://forum.xda-developers.com/showthread.php?t=1777773
then this one to re-root
http://forum.xda-developers.com/showthread.php?t=1673935
I notice one of the links is for 1.85. Does that mean that I'll go from 2.2 back to 1.85? I just wanted to make sure since my impression from the forums is that there is no 2.2 root yet unless it was flashed.
Pbdeng said:
I notice one of the links is for 1.85. Does that mean that I'll go from 2.2 back to 1.85? I just wanted to make sure since my impression from the forums is that there is no 2.2 root yet unless it was flashed.
Click to expand...
Click to collapse
no those pages just tell you how to manually install root and recovery.
your bootloader is still unlockable
unlock it
then install a recovery
then install root via that recovery
Ahh, thanks a bunch man.
Sorry if this is repetitive....
So I've checked my phone and currently it states that it is
"Re-locked"
I downloaded a recovery so it's currently on my phone. Furthermore I all ready had a copy of SU sitting in my phone's download folder.
Does this mean that I'm going to...
- Unlock bootloader (that is currently relocked) and have everything erased again.
- Reboot from recovery (of the evita 2.2.img I just downloaded with TWRP)
- Then flash the SU root I all ready have on my phone?
Pbdeng said:
Sorry if this is repetitive....
So I've checked my phone and currently it states that it is
"Re-locked"
I downloaded a recovery so it's currently on my phone. Furthermore I all ready had a copy of SU sitting in my phone's download folder.
Does this mean that I'm going to...
- Unlock bootloader (that is currently relocked) and have everything erased again.
- Reboot from recovery (of the evita 2.2.img I just downloaded with TWRP)
- Then flash the SU root I all ready have on my phone?
Click to expand...
Click to collapse
yeah unlock the boot loader. set up the phone again
then install the recovery then root.
to make your unlock stick, turn off fastboot in power options, then power down phone completely then restart it to the bootloader.
Hmm, so my phone is definitely unlocked now. I installed the recovery and I manually flashedthe new SuperSU in that link you posted for me. As far as I can tell nothing is happening.
Note: It says that it installs the recovery but there is no reboot that occurs. I've done this both with the android app and manually and nothing is happening.
I don't see SuperSU and rootchecker is confirming that my phone isn't rooted yet.
so you reboot to recovery, choose the superSU package to install then what happens?
I know this works I've done it quite a few times myself.
Presently I installed the latest img file with TWRP with the app. There is not reboot that occurs (unless I'm suppose to reboot on my own?). If that's the case then I've been a total idiot.
I've just been installing the openrecovery and then I press "Flash Roms" to flash the supersu. I get a little notification that says "Preparing to Flash" and then nada.
After you install twrp recovery you reboot. Then you boot to recovery and flash the super su zip manually
Wooh! I got it to work! Thank you so much!
Pbdeng said:
Wooh! I got it to work! Thank you so much!
Click to expand...
Click to collapse
No problemmo.
Does this also mean that I can flash any ROMs I want on my phone now?
Yes. But you will have to flash kernels aka boot.img separately using fast boot.

rooting and jb help!!! plsssss

pls i just go my tf700 2 days ago. with building number IML74K.US_epad-9.4.5.26-20120720,. i want to root and need jelly bean on it, but i dont know how to go about it. also i have no memory card yet, pls someone enlighten me on the steps.:crying:
topdee said:
pls i just go my tf700 2 days ago. with building number IML74K.US_epad-9.4.5.26-20120720,. i want to root and need jelly bean on it, but i dont know how to go about it. also i have no memory card yet, pls someone enlighten me on the steps.:crying:
Click to expand...
Click to collapse
First most important, you need to make a NVflash backup of your bootloader, BEFORE PROCEED to upgrade. This is very important, once you upgrade you will not able to do so.
http://forum.xda-developers.com/showthread.php?t=1901479
buhohitr said:
First most important, you need to make a NVflash backup of your bootloader, BEFORE PROCEED to upgrade. This is very important, once you upgrade you will not able to do so.
http://forum.xda-developers.com/showthread.php?t=1901479
Click to expand...
Click to collapse
but how do i upgrade from .26 after the backup? and do i need memory card for the back?
topdee said:
but how do i upgrade from .26 after the backup? and do i need memory card for the back?
Click to expand...
Click to collapse
So did you make a NVflash backup yet? if not you shouldn't proceed. So your device haven't found any OTA update when you check for update in settings -> about tablet-->check for update?
buhohitr said:
So did you make a NVflash backup yet? if not you shouldn't proceed. So your device haven't found any OTA update when you check for update in settings -> about tablet-->check for update?
Click to expand...
Click to collapse
i haven't done anything yet, but my devices sees no update. so assuming i make a NVflash back up, what's the next thing?
topdee said:
i haven't done anything yet, but my devices sees no update. so assuming i make a NVflash back up, what's the next thing?
Click to expand...
Click to collapse
Let do one step at a time. NVflash is very very critical, once you upgrade you will not able to do this. NVflash backup help you to recover from a soft brick situation. After you done with NVflash, here is how to manual upgrade to JB.
1) Download the .30 verion firmware from Asus site (make sure if you in US, you should download the US version of .30)
http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+Infinity+TF700T&p=20&s=16
2) Extract the .zip file somehwere on your desktop (the result will be another .zip file,use it for step 3)
3) Rename the extracted file to EP201_768_SDUPDATE.ZIP and copy it to the ROOT of a MicroSD card or INTERNAL SD card.
4) Use this button combination to get to stock recovery mode
Turn off tablet. Pressing Volume Down and POWER button together until you see white text message appeared on the screen, now release both buttons. Now press Volume UP button (before the 5 seconds expire).At this point the device will go in recovery and should start updating your firmware .
Once done, I will go into how to root.
buhohitr said:
Let do one step at a time. NVflash is very very critical, once you upgrade you will not able to do this. NVflash backup help you to recover from a soft brick situation. After you done with NVflash, here is how to manual upgrade to JB.
1) Download the .30 verion firmware from Asus site (make sure if you in US, you should download the US version of .30)
http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+Infinity+TF700T&p=20&s=16
2) Extract the .zip file somehwere on your desktop (the result will be another .zip file,use it for step 3)
3) Rename the extracted file to EP201_768_SDUPDATE.ZIP and copy it to the ROOT of a MicroSD card or INTERNAL SD card.
4) Use this button combination to get to stock recovery mode
Turn off tablet. Pressing Volume Down and POWER button together until you see white text message appeared on the screen, now release both buttons. Now press Volume UP button (before the 5 seconds expire).At this point the device will go in recovery and should start updating your firmware .
Once done, I will go into how to root.
Click to expand...
Click to collapse
ok, thanx, am downloading the file now. what you are trying to say is that i need to be on .30 before getting to jb?
topdee said:
ok, thanx, am downloading the file now. what you are trying to say is that i need to be on .30 before getting to jb?
Click to expand...
Click to collapse
1. Yes, if you DON'T want to UNLOCK to root your device. Once you're on .30, you root then use OTA root keeper to save root then upgrade to JB.
2. If you went straight to JB, then you need to unlock in order to root. This will be more complicate, since you need to install custom recovery, fastboot and SDK.
buhohitr said:
1. Yes, if you DON'T want to UNLOCK to root your device. Once you're on .30, you root then use OTA root keeper to save root then upgrade to JB.
2. If you went straight to JB, then you need to unlock in order to root. This will be more complicate, since you need to install custom recovery, fastboot and SDK.
Click to expand...
Click to collapse
ok. but is there any benefit or essence UNLOCKING?
topdee said:
ok. but is there any benefit or essence UNLOCKING?
Click to expand...
Click to collapse
Unlocking allows you to run custom rom and making nanodroid backup using custom recovery (2 main reasons for unlocking)
buhohitr said:
Unlocking allows you to run custom rom and making nanodroid backup using custom recovery (2 main reasons for unlocking)
Click to expand...
Click to collapse
I'd love to run custom rom, just that am afraid of bricking my device.
topdee said:
I'd love to run custom rom, just that am afraid of bricking my device.
Click to expand...
Click to collapse
Most of bricking caused by operators' errors, like using the wrong recovery, wrong bootloader/wrong version for the rom etc.., but if you careful, by doing search and ask first then it's pretty safe to flash custom rom.
buhohitr said:
Most of bricking caused by operators' errors, like using the wrong recovery, wrong bootloader/wrong version for the rom etc.., but if you careful, by doing search and ask first then it's pretty safe to flash custom rom.
Click to expand...
Click to collapse
i hope i am not disturbing you. but assuming based on from .26 i want to root, upgrade to jb and also custom ROM, whats the process? is it the same process?
topdee said:
i hope i am not disturbing you. but assuming based on from .26 i want to root, upgrade to jb and also custom ROM, whats the process? is it the same process?
Click to expand...
Click to collapse
None at all. Let assumed you did the nvflash (backup your .26 bootloader). The simple process would be, download full .30 rom from Asus site, place on root of your external micro SD card or internal SDcard, boot into stock recovery and flash it. Next root your device, then download OTA root keeper to save your root. Let OTA upgrade your device, if OTA is not working, then manually upgrade to JB. Once on JB, use OTA root keeper to restore root. That's it.
buhohitr said:
None at all. Let assumed you did the nvflash (backup your .26 bootloader). The simple process would be, download full .30 rom from Asus site, place on root of your external micro SD card or internal SDcard, boot into stock recovery and flash it. Next root your device, then download OTA root keeper to save your root. Let OTA upgrade your device, if OTA is not working, then manually upgrade to JB. Once on JB, use OTA root keeper to restore root. That's it.
Click to expand...
Click to collapse
thanx bro, after upgrade with the above process wih root intact i can run custom ROM write?
topdee said:
thanx bro, after upgrade with the above process wih root intact i can run custom ROM write?
Click to expand...
Click to collapse
Well, if you plan to run custom rom, you need to unlock and custom roms come pre-rooted, so you don't have to worry about losing root.
buhohitr said:
Well, if you plan to run custom rom, you need to unlock and custom roms come pre-rooted, so you don't have to worry about losing root.
Click to expand...
Click to collapse
based on what i read from the link of nvflash, i need to unlock my device before using nvflash
topdee said:
based on what i read from the link of nvflash, i need to unlock my device before using nvflash
Click to expand...
Click to collapse
Correct bro!
buhohitr said:
Correct bro!
Click to expand...
Click to collapse
ok, assuming i have unlock, backup using nvflash, and eventuall follow all process and reached jb with root intact, how do i introduce custom rom?
topdee said:
ok, assuming i have unlock, backup using nvflash, and eventuall follow all process and reached jb with root intact, how do i introduce custom rom?
Click to expand...
Click to collapse
On your PC you need the following:
1. Android SDK (should comes with ADB and fastboot commands).
2. USB driver for your device.
You are going to use fastboot command to install custom recovery, or you could download Goomanager from Googleplay and install TWRP this way. Once you have TWRP/CWR, you boot into custom recovery mode (hold down volume down and power button), then find the custom rom then flash it, pretty straight forward.

[HELP] HTC on e8sd MM update install ERROR

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

Categories

Resources