Related
Hi all,
As the title suggests I would like to flash my UK wifi xoom with the stock US rom to avoid this ridiculous situation of long delays getting what should be routine upgrades from Google, such as a 3.1!
I've read what seems to be most threads on here but wondered if some one could tell me whether it will definately work and point me in the direct of some quick and fairly idiot proof instructions. I'm not looking to root or have non google supported sd card operation, but I would like to receive major firmware upgrades within a week of their US release. So in this instance would just love to have completely stock HC3.1 running.
I'm sure there are loads of uk Xoom users who are in the same situation and would be equally as keen for some definative guidance,
Thanks if you can help!
I think you probably will have to root (or at least unlock your bootloader) in order to remove the software in the first place.
It's pretty easy though, did it myself at the weekend. Used the one click root method in the development section
http://forum.xda-developers.com/showthread.php?t=1011196
Ignore the warnings, but make sure you do choose wifi from within the program. (I'm also on a UK wifi and it worked fine)
From there you can either install 3.1 from this thread
Http://forum.xda-developers.com/showthread.php?t=1074609
Or you can grab the stock system image from the moto website and install that. Personally I think it would be easier to go the first route and keep root, but it's up to you. I can't help with the system image method, never done it before.
I have been tempted by this too, but for my uses at the moment, I wont really gain much, but Ill keep this in mind in case I change my mind
Sent from my MZ604 using XDA Premium App
Also seriously considering this. I'm going on holiday at the weekend though and will need my Xoom in working order so I'll hold off til I'm back. Who knows, we might even have the update by the time I'm back. If not this is definitely my plan.
I'd also really like the UK stock images or to know how to get them off myself just in case.
Sent from my Xoom using XDA Premium App
I don't think there is a uk image yet... although I might have seen a non-us on moto website? Or did I imagine that?
Sent from my MZ604 using XDA Premium App
I have done all of BRD's mods , and its all good chaps
once a uk/euro rom is available I will probs flash that , but for now 3.1 is worth being a yank
nexan21 said:
I have done all of BRD's mods , and its all good chaps
once a uk/euro rom is available I will probs flash that , but for now 3.1 is worth being a yank
Click to expand...
Click to collapse
Can you flash back to stock using a nandroid backup or do the image files go deeper than that?
Sent from my Xoom using XDA Premium App
Wifi models (Ie MZ604) are fine to flash US Boot images (non-3g i might add ) but 3G models are no go and are bricking if trying to install 3.1.
My advice is although it works, i would suggest waiting for the 3.1 UK / Euro updates as there "maybe" compatibility issues (i say maybe because people will go "Oh Wait, there are none")
at the moment i have a working xoom 3G but cant go in the internet using a SIM card... why? why you might ask?
Some strange reason my telephonyprovider.APk has mucked up xd
But anyway, take it easy before you flash, its your problem if you brick.
burden010 said:
Can you flash back to stock using a nandroid backup or do the image files go deeper than that?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
well i cant go back to stock cos the uk/euro version is not available yet , but will be at some point .
so far i have'nt had any issues , touch wood ! (-;
Just updated my UK version to 3.1 by flashing the US wifi image, then re-locked the boot loader. All seems well.
Update too my UK version to 3.1 with the US wifi image, root and install tiamat kernel
then install language package cause I'm French.
All seems well too.
Just a little thing, the web market detects a new device "Xoom Verizon" instead the previous MZ604 device.
elrazerx said:
Update too my UK version to 3.1 with the US wifi image, root and install tiamat kernel
then install language package cause I'm French.
All seems well too.
Just a little thing, the web market detects a new device "Xoom Verizon" instead the previous MZ604 device.
Click to expand...
Click to collapse
yeah , mine is detected as "Xoom Verizon" also
no adverse effects apart from most apps in the market are priced in $'s not £'s , so i'm waiting for uk/euro image to hit !
Mine still says £'s, even when I was accessing the US market via VPN.
Just do it!
The instructions are somewhat hard to find, but...
1. Install the Android-SDK,
2. Make a path to the fastboot command via right clicking Computer selecting properties select advanced system, environment variables, click on PATH and in the variable value input paste:
C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools
3. Make sure you de-zip the stock us Wifi firmware into the C:\Program Files (x86)\Android\android-sdk\platform-tools directory. Download these from the MotoDev web-site.
4. Place your xoom in fastboot by turning off then repowering holding the volume down button to enter fastboot mode.
Open the command prompt if not already open...
Unlock your Xoom by typing:
fastboot oem unlock
at the command prompt.
then enter the following:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Once complete your Xoom should reboot thinking it is a stock US device, so re-configure and you should be prompted with the Update for 3.1.
Job done, no more waiting around like a second class citizen for Motorola to bother passing on the released Google updates to your device. And 3.1 is definately worth the effort...
And yes there is absolutely no reason why European customers paying a premium price point should have to do this to obtain a routine update in a realistic time-frame. Hopefully once flashed to a Stock US device we should receive updates within the same operational window as those who purchased within the US.
Hope this helps, it certainly helped me! (PS this will of course blank your device back to default, once done this should be the last time as updates should now arrive in line with their release!)
pirsiger said:
.... instructions ...
Click to expand...
Click to collapse
Nice - that's the second post of instructions I saw (others are herE: http://forum.xda-developers.com/showthread.php?p=13942581#post13942581)
and as I said then - I think people will still be a little hesitant due to no return to UK image silly Moto
Is there a reason that you would want to go back to a UK image? What is the diff between the UK and US? The only thing I can think of is the UK image Google services connects to servers in UK/Euro.
PsyMonkey said:
Is there a reason that you would want to go back to a UK image? What is the diff between the UK and US? The only thing I can think of is the UK image Google services connects to servers in UK/Euro.
Click to expand...
Click to collapse
If you ever wanted to return it due to a fault (screen, wifi etc) they would take one look at the US software and claim you have invalidated your warranty.
Short it out with 12V DC through inappropriate parts of the internals? Did that with a phone Orange replaced because the replacement was falling apart and the one I sent in was mint externally.
But tbh, I don't think anyone who works in these stores would know much about software versions.
VaKo said:
Just updated my UK version to 3.1 by flashing the US wifi image, then re-locked the boot loader. All seems well.
Click to expand...
Click to collapse
Same here, running sweeeeet
Is there any way to do this without losing data?
Sent from my Xoom using XDA Premium App
Okay guys. I've searched and searched and found nothing, almost found something but wasn't definitive enough, and wasn't going to risk bricking my device.
Acer Iconia A500 Wifi Version
Current OS Version: HC 3.0.1
FLEX Version: 04_COM_GEN1
Kernel Version: 2.6.36.3
Build Number: ACER_A500_1.145.04_COM_GEN1
Now, notice I only bought this end of December-ish 2011 but this device has been out for quite some time. I don't know what is going on with Acer right now but this thing will not update through the system update no matter how many times I click on it. (tap on it you know what I mean)
Now, I wanted to do it manually, since I was able to do so on my Nexus S with ICS. But there are so many version out there and most of those forums say that if you don't use the correct region you'll brick your device.
Also, I searched my build number and only 1 person on 1 forum here on XDA Devs had the same build number and even then was only saying it to share. I cannot find anything regarding this build number, or what build to use to upgrade to 3.2.1, or all the way up to even if it takes multiple updates.
I know that Acer A500s are supposed to be getting ICS 4.0 sometime this month in Jan, but I'd like to be able to be updated to 3.2 at least while I'm here.
NOTE: I DO NOT WANT TO ROOT ANYTHING (That is not what she said)
Can someone take a look at my build number and current versions and what not, and please point me in a direction to get this thing upgrade to 3.2?
Thanks. A lot. In advanced. And stuff.
-B00mer
I'm actually facing the same problem too. Same build number, and no updates found. I checked Acer's website and say a document for updating to 3.2. The document mentions certain build numbers from different countries that are eligible for an update, and ours is not in the list. I wonder what Acer is up to?
Does it download the update?
mrtoken said:
Does it download the update?
Click to expand...
Click to collapse
It won't even see any of the updates. It just keeps saying "No Update: Your device is up to date."
Did a bit of googling for you
Someone had the same problem until they used the acer registration widget and waited a couple of days.
will keep looking
mrtoken said:
Did a bit of googling for you
Someone had the same problem until they used the acer registration widget and waited a couple of days.
will keep looking
Click to expand...
Click to collapse
Hey mate,
Thanks for doing that. However I've used that widget and registered when I got it and its been 2 weeks now. I guess I wasn't able to find that on google mostly because I've been looking under the assumption that because this is an android OS there would be a more technical way of updating the device. Lol.
Not giving up though.
b00mtastik said:
Hey mate,
Thanks for doing that. However I've used that widget and registered when I got it and its been 2 weeks now. I guess I wasn't able to find that on google mostly because I've been looking under the assumption that because this is an android OS there would be a more technical way of updating the device. Lol.
Not giving up though.
Click to expand...
Click to collapse
Some people are reporting that updates come in waves, I know the latest update is doing the rounds now so you might have to wait till that has finished and then you might get a catch up one.
I would just give acer nz a call and ask them
Try and get a date for ICS as well
mrtoken said:
Some people are reporting that updates come in waves, I know the latest update is doing the rounds now so you might have to wait till that has finished and then you might get a catch up one.
I would just give acer nz a call and ask them
Try and get a date for ICS as well
Click to expand...
Click to collapse
Would the update mean much to me since I am still on 3.0.1? I cant even get any of the other ones to even get to the latest update.
If I get a date for ICS, ill be sure to post it.
Just root it, then update. After that you can install a none rooted updated 3.2.1 stock rom
Hi b00mtastik,
I had the same problem with an iconia a couple of days ago. I tried different things and managed to fix it.
I'll try to give you step by step how to fix it (not sure if it will work for you).
I thought that the people from the shop i got the tablet played with it and put some custom rom and so i tried to get it to stock.
I used stuff from this thread.
1. You have to root your tablet - Click here
2. You have to install Clockwork Recovery.
- install from market "Acer Recovery"
- run it and give it root permission
- choose ClockworkMod Recovery rev1.3.4 by thor2002ro
- click Install Recovery Image
3. Download this. It is a backup made with clockworkmod. It will give you an android with version 1.139.02. In the zip is also a update.zip which will update your 1.139.02 to 1.139.05.
4. unzip it and put it on your external sd card (if you do not have one, find one, you need ~ 500 mb free)
5. put the files directly on sd card (e.g. update.zip goes to root, clockworkmod folder goes to root)
6. After that you have to boot in recovery.
- power device off
- keep VOL- button pressed and press and hold power button. Keep holding both button until you get to the menu.
7. Navigate using volume keys and enter a menu using the power button.
8. Navigate to backup/restore and then full backup and full restore (might be a little different). You choose full restore and navigate to restore a backup made on 25.06.
9. Wait until it is done.
10. Reboot and wait for the tablet to boot.
11. Open Acer Recovery and choose to install Stock USA recovery image. install.
12. Again you have to boot in recovery.
- power device off
- keep VOL- button pressed and press and hold power button. Keep holding both button until you see the update installing (An android robot).
13. After the update installs and the tablet boots check for updates.
This has worked for me. I did try other stuff but with no success.
I hope it was helpful for you and you can fix your device.
What you are most likely running into is ACER has not released an OTA for your region. What people are telling you might not be what you want. For example, if someone in the USA is telling you to flash or update, they are often referring to experiences that relate to the USA. NZ might have a different configuration, digital rights, contracts, language, etc etc that ACER just hasn't upgraded yet. Or might not ever upgrade.
If you are totally stock and have never rooted, then CALL ACER TECH SUPPORT and get the correct answer for you make and model for your country. If not, then following directions here might void your warranty. So, just give them a call and see what they tell you first. Then let us know what your find out.
TD
Of course you should first make sure there IS a higher version in your region. And rooting will void warranty.
Although as I spoke with Acer Support about the tablet mentioned in my post, they told me that 3.0.1 is the newest version, which is not true since I have two other a500 tablets both up to 3.2.
Just shared what did it for me.
Hope you can fix your problem the easy way.
Current for NZ is
3.2.1
Kernel version 2.6.36.3+
Build Acer_A500_7.014.15_Com_gen1
Is your current firmware stable? Is everything working OK?
New Zealand and Australia are typically the first countries to get the updates. But they are rolled out by google due to some number to do with your tablet. I'm in the south island and have had 3.2 for quite a while. When I brought my father an A500, it took about a week before the update was available for it. basically if you have any problems just go to the acer ANZ facebook fanpage, one of their acer people are always very good there with question. firmware is stable, and android 4 is meant to be released to NZ/Aussie shortly.
i forgot to mention before you get the big android updates there is a smaller update, i can't remember the size of it, but your tablet has to take that update before it will take the 3.1 or 3.2 update, cannot remember if you need 3.1 before 3.2
I know for a fact that NZ/AUS are supposed to be at 3.2 atleast, as I've seen some of the store A500's with 3.2 running. Also, Acer states NZ/AUS are supposed to be getting ICS 4.0 by the end of Jan.
I'm hoping this will be very soon. I'm thinking that they might have removed the updates from their servers for 3.1 and 3.2 and 3.2.1 and my tablet will just get a OTA for 4.0.
I'm hoping not to have to root anything, but I suppose that'll depend on my patience by the end of this month. Lol.
I should be able to update manually to 3.2 I know this much, but I can't seem to write to my SD Card which is why the manual updating via boot is not working, because it won't let me write to external_sd.
If someone can at least give me ideas on external_sd and write permissions for it WITHOUT rooting. Would be helpful.
Mean while I shall try and get a hold of support and see what they say.
-b00mer
b00mtastik said:
I know for a fact that NZ/AUS are supposed to be at 3.2 atleast, as I've seen some of the store A500's with 3.2 running. Also, Acer states NZ/AUS are supposed to be getting ICS 4.0 by the end of Jan.
I'm hoping this will be very soon. I'm thinking that they might have removed the updates from their servers for 3.1 and 3.2 and 3.2.1 and my tablet will just get a OTA for 4.0.
I'm hoping not to have to root anything, but I suppose that'll depend on my patience by the end of this month. Lol.
I should be able to update manually to 3.2 I know this much, but I can't seem to write to my SD Card which is why the manual updating via boot is not working, because it won't let me write to external_sd.
If someone can at least give me ideas on external_sd and write permissions for it WITHOUT rooting. Would be helpful.
Mean while I shall try and get a hold of support and see what they say.
-b00mer
Click to expand...
Click to collapse
Download the 3.2.x you want on your PC and put the sdcard in your PC, copy the file to the sdcard on your PC. Now take the sdcard out of the PC and put it into your tablet. Works every time.
Lastly, if you're still under warranty, why not just call ACER for help?
timmyDean said:
Download the 3.2.x you want on your PC and put the sdcard in your PC, copy the file to the sdcard on your PC. Now take the sdcard out of the PC and put it into your tablet. Works every time.
Lastly, if you're still under warranty, why not just call ACER for help?
Click to expand...
Click to collapse
The last thing I want to do is give it back to them and wait for about 2 weeks for the retail store to get their asses into gear and send it off, then wait another week for Acer to do fix things, which should just not have happened in the first place.
I've tried the idea you gave me mate. I took out the SD Card, and used an old phone that allowed me to access it as a Mass Storage Device because I didn't have a card reader, and formatted it both to FAT first then FAT32 and still no go. The tablet just cannot seem to be recognizing that it even has an External SD Card in it.
Its looking more and more like I'm going to HAVE to go in and get it sorted somehow. Thanks everyone for your input and help. I've also contacted Acer Support. Lets see what they have to say, which I will post here. I'll also fiercely be practicing my Google-Fu to see what else I can find.
-b00mer
I would suggest that you wait for the ICS to start coming out, I can let you know when I get it.
They may have removed the 3.1 and 3.2 from the OTA update sever to get ready for ICS.
If you don't have ICS in a week after it rolls then I would be taking it back to the retailer and telling them that it does not update, they will send it away to get it loaded etc.
mrtoken said:
I would suggest that you wait for the ICS to start coming out, I can let you know when I get it.
They may have removed the 3.1 and 3.2 from the OTA update sever to get ready for ICS.
If you don't have ICS in a week after it rolls then I would be taking it back to the retailer and telling them that it does not update, they will send it away to get it loaded etc.
Click to expand...
Click to collapse
Its kind of the only choice I have while I'm unable to do anything else.
Thanks mate, that'll be good to know. And yeah, I was thinking they removed it from their servers to get it ready, but I'm hoping they don't cut it out and stop it either like they did with Nexus S. I had to manually update that as well, but that worked seemlessly, while I was JUST getting drunk, during a party. You know something is good when you can do that.
I'm dreading letting it go away, but if they can load it up, I technically should be able to getting it loaded somehow as well?
-b00mer
It seems that I was fiddling with my OTA and I lost my original build Kind of bummed out, and also the fact that I don't even know how to do a full backup. I did a nandroid backup which doesn't even work. I update to the new ICS firmware and messed up everything...Now I'm left in a gutter feeling utterly upset and don't know what to do. If there's anybody who pity's me, please help. It would be sincerely appreciated. I just want to start off fresh.
Mkami said:
It seems that I was fiddling with my OTA and I lost my original build Kind of bummed out, and also the fact that I don't even know how to do a full backup. I did a nandroid backup which doesn't even work. I update to the new ICS firmware and messed up everything...Now I'm left in a gutter feeling utterly upset and don't know what to do. If there's anybody who pity's me, please help. It would be sincerely appreciated. I just want to start off fresh.
Click to expand...
Click to collapse
So where are you at right now. What rom and what exactly have you done to your tab.
Mkami said:
It seems that I was fiddling with my OTA and I lost my original build Kind of bummed out, and also the fact that I don't even know how to do a full backup. I did a nandroid backup which doesn't even work. I update to the new ICS firmware and messed up everything...Now I'm left in a gutter feeling utterly upset and don't know what to do. If there's anybody who pity's me, please help. It would be sincerely appreciated. I just want to start off fresh.
Click to expand...
Click to collapse
Yeah, I share the pity with you Mate. You shouldn't have to look at that busted tab. Just put that shameful thing in a box and mail it to me, to help ease your pain. Heck, I'll toss in shipping so you won't suffer further insult and pain...
Seriously, though, there are plenty of tools and procedures here to bring it back to life.
First off, before you muck things up further, I would look in your nandroid backup, and get the UID number. Hopefully you wrote this down somewhere before you originally messed with things?
For starters, I would goto this link, and see if it works for you...
http://forum.xda-developers.com/showthread.php?t=1699277
The english steps are not the best in the world, but you will get the general idea.
MD
shaun298 said:
So where are you at right now. What rom and what exactly have you done to your tab.
Click to expand...
Click to collapse
At this moment right now, my a500 tab has that orange light on the bottom and it stays there, and when I turn on the tab it starts up normally like it would, and when it does it turns off. The strange thing is that orange charging light where the power button is, stays on even though I'm not even charging it.
I've tried changing the OTA, but after when it starts in the corner it says something like. " Not official blob" I'm not even sure I know what that even means....I have everything including nandroid backed up all the files into the SD card I had in my tab, I notice is there somewhere due to the amount of space it consumed on my SD.
So please! IF you know of any way to fix this I would be in great appreciation, also it's been a month since I've had this tab, as well I have a 2 year warranty.
Moscow Desire said:
Yeah, I share the pity with you Mate. You shouldn't have to look at that busted tab. Just put that shameful thing in a box and mail it to me, to help ease your pain. Heck, I'll toss in shipping so you won't suffer further insult and pain...
Seriously, though, there are plenty of tools and procedures here to bring it back to life.
First off, before you muck things up further, I would look in your nandroid backup, and get the UID number. Hopefully you wrote this down somewhere before you originally messed with things?
For starters, I would goto this link, and see if it works for you...
http://forum.xda-developers.com/showthread.php?t=1699277
The english steps are not the best in the world, but you will get the general idea.
MD
Click to expand...
Click to collapse
Hahaha funny guy! If you haven't seen my post its here and the reasons. Also I do have the UID saved on a text format on my pc...will that work??
So here is the issue are the current moment friend.
my a500 tab has that orange light on the bottom and it stays there, and when I turn on the tab it starts up normally like it would, and when it does it turns off. The strange thing is that orange charging light where the power button is, stays on even though I'm not even charging it.
I've tried changing the OTA, but after when it starts in the corner it says something like. " Not official blob" I'm not even sure I know what that even means....I have everything including nandroid backed up all the files into the SD card I had in my tab, I notice is there somewhere due to the amount of space it consumed on my SD.
So please! IF you know of any way to fix this I would be in great appreciation, also it's been a month since I've had this tab, as well I have a 2 year warranty.
Have you tried putting a stock update.zip on the root of your external sdcard and booting the tablet by holding the volume down button (left volume rocker) down while pressing the power button until the tablet finds the file and installs it. This should bring you back to unrooted stock ICS with locked bootloader and you can start over. Remember, this must be an update.zip file that is extracted from a stock RUU. You can't just rename a RUU file to update.zip.
Mkami said:
Hahaha funny guy! If you haven't seen my post its here and the reasons. Also I do have the UID saved on a text format on my pc...will that work??
So here is the issue are the current moment friend.
my a500 tab has that orange light on the bottom and it stays there, and when I turn on the tab it starts up normally like it would, and when it does it turns off. The strange thing is that orange charging light where the power button is, stays on even though I'm not even charging it.
I've tried changing the OTA, but after when it starts in the corner it says something like. " Not official blob" I'm not even sure I know what that even means....I have everything including nandroid backed up all the files into the SD card I had in my tab, I notice is there somewhere due to the amount of space it consumed on my SD.
So please! IF you know of any way to fix this I would be in great appreciation, also it's been a month since I've had this tab, as well I have a 2 year warranty.
Click to expand...
Click to collapse
Well, you get the orange light because your EC Pwr management is probably fubarred. That should be fixed when you install a stock rom as suggested in both mine and the other poster.
Considering you have your UID, you should be ok.
Of course I don't know if this is a 3.2 or an ICS UID. Best to have both. The sbk is the same, but the uid numbers differ.
If it's a 3.2., check the Q&A thread for a post I did for a guy earlier today.
But you should be able to follow the steps for the update I posted earlier.
Blob means Bootloader. And looks like you had an unlocked bootloader?
Try to roll back to 3.2. That's where I would start.
MD
cruise350 said:
Have you tried putting a stock update.zip on the root of your external sdcard and booting the tablet by holding the volume down button (left volume rocker) down while pressing the power button until the tablet finds the file and installs it. This should bring you back to unrooted stock ICS with locked bootloader and you can start over. Remember, this must be an update.zip file that is extracted from a stock RUU. You can't just rename a RUU file to update.zip.
Click to expand...
Click to collapse
What do you mean by RUU? Also I've tried a couple of the OTA updates, when I first got the tab it was on 3.1 HC didn't even update it or anything, just had a custom ICS ROM on it. Do you think you can post the steps or anything on how to do this properly and go fresh? It would be sincerely appreciate buddy.
Moscow Desire said:
Well, you get the orange light because your EC Pwr management is probably fubarred. That should be fixed when you install a stock rom as suggested in both mine and the other poster.
Considering you have your UID, you should be ok.
Of course I don't know if this is a 3.2 or an ICS UID. Best to have both. The sbk is the same, but the uid numbers differ.
If it's a 3.2., check the Q&A thread for a post I did for a guy earlier today.
But you should be able to follow the steps for the update I posted earlier.
Blob means Bootloader. And looks like you had an unlocked bootloader?
Try to roll back to 3.2. That's where I would start.
MD
Click to expand...
Click to collapse
Hmmm....I'm not even sure what I am doing wrong but whatever it is, it seems to be not working. I looked for you post for the earlier person that you did, but don't know what it is under. By the way when I first bought the tab it was under 3.1 HC and after getting flexreaper it became to ICS 4.0.3...
So like everytime I turn on the tab it shuts down instantly, as well every time I try to boot an update.zip file onto the SD card it shows this animation of the android with this circular sphere in it's stomach after that it falls over with a red caution sign.
Mkami said:
So like everytime I turn on the tab it shuts down instantly, as well every time I try to boot an update.zip file onto the SD card it shows this animation of the android with this circular sphere in it's stomach after that it falls over with a red caution sign.
Click to expand...
Click to collapse
In my experience the common cause for ending up with a caution sign is a corrupted update.zip (incomplete download, bad SD card, etc.). As for the tablet shutting down, my guess is that's related to the power management functions being broken.
im not THEE most savvy here but i do know a few methods and find it easy to discover lesser known ones, i feel bad for you . if you want you can skype video me and ill try talking it over and maybe a few methods? :highfive:
edit: ok from what i can tell your update was bad and your bootloader is causing problems, the power problems are probably arising from the bad power management as moscow desire told.
the tabs obviously rooted n all right? ok so how about flashing the v7 ics bootloader then trying a custom rom?......<-also recommended by moscow desire
lcd047 said:
In my experience the common cause for ending up with a caution sign is a corrupted update.zip (incomplete download, bad SD card, etc.). As for the tablet shutting down, my guess is that's related to the power management functions being broken.
Click to expand...
Click to collapse
You're right! I was able to fix it and boot up to the usual! Thanks mate!
chismay said:
im not THEE most savvy here but i do know a few methods and find it easy to discover lesser known ones, i feel bad for you . if you want you can skype video me and ill try talking it over and maybe a few methods? :highfive:
edit: ok from what i can tell your update was bad and your bootloader is causing problems, the power problems are probably arising from the bad power management as moscow desire told.
the tabs obviously rooted n all right? ok so how about flashing the v7 ics bootloader then trying a custom rom?......<-also recommended by moscow desire
Click to expand...
Click to collapse
Hi Chismay, well I thought I fixed the issue and the problem. Guess again I did not This I can't believed I used a leaked ICS OTA, kinda ruined most of the things in my tab. Lol just had it for a month and already messed it up by fooling around with it. But your help is greatly appreciated buddy! Would like to get a one on one instructions on what I should do.
Cheers!
Correct me if I'm wrong on this...
1. You originally had Honeycomb on your tablet.
2. You flashed FlexReaper on your tablet
3. You probably got a recent version of FlexReaper.
4. You never upgraded your bootloader.
5. You can still get access to recovery.
If all of these are correct, then I think I know what the problem is. It appears you flashed a rom that requires the ICS bootloader and not the Honeycomb bootloader.
This, I think, is an easy fix...
1. Download the following file: http://www.darktremor.info/files/FLEXREAPER-R12.5-ICS-1.031.00.zip (this is an older version I have on my Acer A500).
2. Put the file on your SD card.
3. Boot up into recovery (if you can't get there, stop here).
4. Once you are in recovery, flash the FlexReaper file you just put on your SD card.
5. Now try to boot and see if it works.
Let me know how it works either here, in a PM, or e-mail me at [email protected]. If you need further assistance, don't hesitate to contact me.
Mkami said:
Hi Chismay, well I thought I fixed the issue and the problem. Guess again I did not This I can't believed I used a leaked ICS OTA, kinda ruined most of the things in my tab. Lol just had it for a month and already messed it up by fooling around with it. But your help is greatly appreciated buddy! Would like to get a one on one instructions on what I should do.
Cheers!
Click to expand...
Click to collapse
tkirton said:
Correct me if I'm wrong on this...
1. You originally had Honeycomb on your tablet.
2. You flashed FlexReaper on your tablet
3. You probably got a recent version of FlexReaper.
4. You never upgraded your bootloader.
5. You can still get access to recovery.
If all of these are correct, then I think I know what the problem is. It appears you flashed a rom that requires the ICS bootloader and not the Honeycomb bootloader.
This, I think, is an easy fix...
1. Download the following file: http://www.darktremor.info/files/FLEXREAPER-R12.5-ICS-1.031.00.zip (this is an older version I have on my Acer A500).
2. Put the file on your SD card.
3. Boot up into recovery (if you can't get there, stop here).
4. Once you are in recovery, flash the FlexReaper file you just put on your SD card.
5. Now try to boot and see if it works.
Let me know how it works either here, in a PM, or e-mail me at [email protected]. If you need further assistance, don't hesitate to contact me.
Click to expand...
Click to collapse
Hahaha! Good job on guessing all that! I just followed your order from step to step and I was about to boot up normally! Everything might be erased and stuff, but hey at least I have my tablet working again :good: Case solved!
Good day to all. I know this question has been asked many times and I might frustrate some or many of you. Please accept my apology first and foremost.
Do allow me to tell you my side of the story. I bought a A2017 from AliExpress. I specifically told the seller to leave it stock as I want OTA and future support. By saying this, I am not condemning the Root Community or implying the mod ROM is any way inferior to stock. I believe and trust that the modded ROM is definitely a level or many level better than stock ROM.
Back to my plight, I knew changing imei is taboo here in this wonderful community. I agree and standby to the rules. But the joker seller not only flash my A2017 with A2017G ROM (to which I do not mind having) but that means I am losing the updates either over OTA or SD card upgrade (because his is not stock ROM); and more importantly I am definitely losing the security patches presently available or coming in future.
Now I have a wonderful A2017 which I like a lot, with an non-OTA A2017G ROM and a messed up IMEI. The IMEI as it is programmed is not invalid, but the 2 IMEI IDs found within my phone are identical. More excitingly, the protective sticker that came with the phone have 2 seperate IMEI for each SIM slot, and the box that they shipped to me contains another 2 separate IMEI. So in total I have 5 IMEI numbers!
To all the masters and gurus her, i really appreciate if you can kindly help me out. I would like to know the following:-
First, is it possible for me to fix my IMEI (to repair them exactly to what's with reference to the protective sticker that came on the back of the phone)?
Second, I do not know the term used within the community, but I would like to install the latest stock A2017G ROM into the phone on its base. Meaning if by chance I need to hard reset the phone in future, the one that comes up as base will be the latest ROM I were to install them today.
Third, and yes, among the all the works involved for first and second queries, I would like to know if there's a chance for me to lock everything done and to make the phone as if it is stock? Unroot back to normal if rooting is mandatory for above reworks.
Last but not least, I know the works involve may be tedious and very long winded and maybe highly likely offending one to type out all the procedures. I really thank you for your attention.
If the procedures is really long for you to type out, perhaps you can let me know in point forms and follow up with link. That's will definitely help me to understand step by step in fixing my phone. Also if there's any particular software to be used, perhaps the workable and stable name and version stated will be much appreciated.
Thank you all once again for your time.
P/S: The information on the web is so overwhelming that I lost in the sea of information. I honestly do not know and how to start but to come into the safe zone, the XDA family to seek guidance from.
Again changing IMEI is taboo here, but I am force to correct the issues one created on me, and not that I am doing it to get away with laws or anything. I just want a normal working phone that will behave normally.
Thank you again.
Best regards,
BoyA2017
Edit:
Or can any gurus here advise me the point below in steps. I will try to figure it out from here after.
1. Root (heard using Axon7ToolKit will be relatively user friendly).
2. Fix IMEI (I'll try to find my way around for this).
3. Place the G Nougat bootstack (This has something to do with TWRP?).
4. Backup (not sure if this will backup my IMEI).
5. Unroot (I would assume Axon7Toolkit should able to do this).
Is the above steps will work for my case or I should reshuffle the steps a little?
Please advise.
Cheers.
BoyA2017 said:
Good day to all. I know this question has been asked many times and I might frustrate some or many of you. Please accept my apology first and foremost.
Do allow me to tell you my side of the story. I bought a A2017 from AliExpress. I specifically told the seller to leave it stock as I want OTA and future support. By saying this, I am not condemning the Root Community or implying the mod ROM is any way inferior to stock. I believe and trust that the modded ROM is definitely a level or many level better than stock ROM.
Back to my plight, I knew changing imei is taboo here in this wonderful community. I agree and standby to the rules. But the joker seller not only flash my A2017 with A2017G ROM (to which I do not mind having) but that means I am losing the updates either over OTA or SD card upgrade (because his is not stock ROM); and more importantly I am definitely losing the security patches presently available or coming in future.
Now I have a wonderful A2017 which I like a lot, with an non-OTA A2017G ROM and a messed up IMEI. The IMEI as it is programmed is not invalid, but the 2 IMEI IDs found within my phone are identical. More excitingly, the protective sticker that came with the phone have 2 seperate IMEI for each SIM slot, and the box that they shipped to me contains another 2 separate IMEI. So in total I have 5 IMEI numbers!
To all the masters and gurus her, i really appreciate if you can kindly help me out. I would like to know the following:-
First, is it possible for me to fix my IMEI (to repair them exactly to what's with reference to the protective sticker that came on the back of the phone)?
Second, I do not know the term used within the community, but I would like to install the latest stock A2017G ROM into the phone on its base. Meaning if by chance I need to hard reset the phone in future, the one that comes up as base will be the latest ROM I were to install them today.
Third, and yes, among the all the works involved for first and second queries, I would like to know if there's a chance for me to lock everything done and to make the phone as if it is stock? Unroot back to normal if rooting is mandatory for above reworks.
Last but not least, I know the works involve may be tedious and very long winded and maybe highly likely offending one to type out all the procedures. I really thank you for your attention.
If the procedures is really long for you to type out, perhaps you can let me know in point forms and follow up with link. That's will definitely help me to understand step by step in fixing my phone. Also if there's any particular software to be used, perhaps the workable and stable name and version stated will be much appreciated.
Thank you all once again for your time.
P/S: The information on the web is so overwhelming that I lost in the sea of information. I honestly do not know and how to start but to come into the safe zone, the XDA family to seek guidance from.
Again changing IMEI is taboo here, but I am force to correct the issues one created on me, and not that I am doing it to get away with laws or anything. I just want a normal working phone that will behave normally.
Thank you again.
Best regards,
BoyA2017
Click to expand...
Click to collapse
Hey I'm in the same situation as you , I bought an Axon A2017 from a chinese seller who flashes a A2017g ROM in order to get Google services and play store to work properly but I think he ruined the device as it will not OTA update anymore and that's kinda of frustrating as you will remain stuck with that android 6.0.1 version , therefore no daydream compatibility and that's the main reason I bought this phone. Wish that an A2017 user show us a simple way to get that OTA to work and get the latest firmware and security patches applied.
Youssefmans said:
Hey I'm in the same situation as you , I bought an Axon A2017 from a chinese seller who flashes a A2017g ROM in order to get Google services and play store to work properly but I think he ruined the device as it will not OTA update anymore and that's kinda of frustrating as you will remain stuck with that android 6.0.1 version , therefore no daydream compatibility and that's the main reason I bought this phone. Wish that an A2017 user show us a simple way to get that OTA to work and get the latest firmware and security patches applied.
Click to expand...
Click to collapse
There are plenty of guides for what you want to do, just search on the Q&A thread. As of him, not that easy... I guess going back to stock A2017 is the first thing to do anyways.
In short: Download an official stock A2017 7.1.1 zip, verify that the zip you downloaded doesn't have another zip inside called update.zip (in that case you have to extract the update.zip) (if you open the zip you downloaded and find a bunch of files then you can use it directly), put it in the root of the internal storage, go to Settings then Updates and install it. If you don't have the Updates option you'll need an SD card: put the file there, turn the phone off, hold Power + volume UP, you'll boot to recovery, select Apply update from SD card (or, if your recovery is in Chinese, the option that says sd), select the zip file, press power to confirm, confirm installation
Youssefmans said:
Hey I'm in the same situation as you , I bought an Axon A2017 from a chinese seller who flashes a A2017g ROM in order to get Google services and play store to work properly but I think he ruined the device as it will not OTA update anymore and that's kinda of frustrating as you will remain stuck with that android 6.0.1 version , therefore no daydream compatibility and that's the main reason I bought this phone. Wish that an A2017 user show us a simple way to get that OTA to work and get the latest firmware and security patches applied.
Click to expand...
Click to collapse
Choose an username... guides will fit you perfectly. You may find it a little hassle on the recovery mode. What I found out is, you have to hold (volume up + power) button until you come to a colorful MiFavor screen with lots of Chinese wording. At this point of time, you can release the volume up button, BUT keep power button pressed. Once you let go of power button, it will reboot itself. While pressing the power button, you can toggle the up down with volume buttons. Until you come to something with 'SD' then u release the power button. Your phone should update itself. After update complete, please remove the SD card or to delete the update.zip from the SD card. Else if will continuously detecting the file within your SD as an update.
For the reboot after releasing the power button in recovery mode may only applicable to my A7, not sure if this is across the board. Many A7 here are experiencing their own issues but majority of them works as mentioned. Maybe mine is just a little abnormal.
Hope you can fix your phone right and enjoy your A7.
Cheers.
A while ago I bought a Mediapad M3. Once I realized the 5GHz band was disabled on the US version, I was hellbent on getting it working. I eventually got it working through a bastardized hybrid of the Chinese (BTV-W09C233) and the US (BTV-W09C128) versions. There were a lot of problems with it (e.g. I couldn't install Gboard, I couldn't do a factory reset without losing latin keyboard, etc). I decided to go back to the stock US version and figuring out the minimum change needed to get the 5GHz band working. The tablet just didn't wanna go back to the US version and I wasn't gonna quit. At some point I ****ed up and I'm pretty sure I've hard bricked it dead. Then again many times I've been sure I've totally bricked a device only to stumble across some obscure way to breathe enough life into it to get fastboot or recovery working. I'm hoping this is one of those cases.
The symptoms:
Device is off. Holding the power button for no amount of time has changed that
I've tried a variety of button combos, none seem to do anything
Is there a special download mode like Qualcomm devices where some basic funcionality exists?
Does it respond in fastboot? If so, you might be able to use DC Unlocker(search please.) I haven't been able to try this on my device yet, and probably not for another month.
fargonaz said:
Does it respond in fastboot? If so, you might be able to use DC Unlocker(search please.) I haven't been able to try this on my device yet, and probably not for another month.
Click to expand...
Click to collapse
There would be something on the screen for fastboot, no?
Looking in my dmesg, I don't see any new devices being registered by Linux so I didn't bother with fastboot.
With mine there is no screen activity. If it's not showing up... You could read the DC Unlocker web site, I think there was a hardware method (shorting of test points) to stir the device.
Good Luck!
copolii said:
A while ago I bought a Mediapad M3. Once I realized the 5GHz band was disabled on the US version, I was hellbent on getting it working. I eventually got it working through a bastardized hybrid of the Chinese (BTV-W09C233) and the US (BTV-W09C128) versions. There were a lot of problems with it (e.g. I couldn't install Gboard, I couldn't do a factory reset without losing latin keyboard, etc). I decided to go back to the stock US version and figuring out the minimum change needed to get the 5GHz band working. The tablet just didn't wanna go back to the US version and I wasn't gonna quit. At some point I ****ed up and I'm pretty sure I've hard bricked it dead. Then again many times I've been sure I've totally bricked a device only to stumble across some obscure way to breathe enough life into it to get fastboot or recovery working. I'm hoping this is one of those cases.
The symptoms:
Device is off. Holding the power button for no amount of time has changed that
I've tried a variety of button combos, none seem to do anything
Is there a special download mode like Qualcomm devices where some basic funcionality exists?
Click to expand...
Click to collapse
I am in the same boat.
https://forum.xda-developers.com/mediapad-m3/help/m3-apsabnormal-bricked-t3779100
Will follow this thread will great interest.
Good luck!
I'm on vacation right now and I hate using the laptop for this sort of thing. I'm flying back in the morning and once I'm over the jetlag, I'll see what I can do with the damn thing.
In the meantime, I'd like to punch someone in Huawei for 1- disabling the 5GHz in the NA model and 2- Putting **** software on such great hardware.
Any progress?
Thanks!
Well, hey @copolii. Took a while to find test point as it hasn't been posted or published anywhere. From there it was still a bit tricky. Had to use BTV-DL09 board software to get fastboot only area in ram through factory mode (edl mode). Then fastboot flash the UPDATE.APP to boot to upgrade mode. Then flashed UPDATE.APP with localization files from upgrade mode. After that had to repair serial number and imei in order to get bootloader code. After all that let it update to nougat & emui 5 and it has 5GHz wifi which surprized me a bit. TWRP needs a little tuning and Magisk is working as it should. All of that was accomplished using SigmaKey dongle. Like I said, a bit tricky and don't believe it could have been fixed any other way. Oh, yeah same device, I bought it.
Thanks @tek3195.
I sold the tablet a month ago. Maybe share the info regarding the test pins so that the next person who stumbles upon this here can give it a shot.
copolii said:
Thanks @tek3195.
I sold the tablet a month ago. Maybe share the info regarding the test pins so that the next person who stumbles upon this here can give it a shot.
Click to expand...
Click to collapse
Sorry, I forgot to post this before. So if anyone needs it and I'm sure they will.
Test point for BTV-W09 I would think BTV-DL09 would be the same, both have identical FCCID photos. content://media/external/images/media/28314 . To use test point you must disconnect battery. I would also recommend a little heat at top and bottom of display to remove.
I apologize for no link being posted . I didn't come back and check it , now attached an image hope it works. Don't know where the link went. In the pic there is only one test point as that is all that is used with Kirin devices apparently. The point at end of lime-green line is test point to be grounded with ground pin or any of the heat shields will work. A sharp pair of tweezers works well to make the short and make sure to disconnect battery.
tek3195 said:
Well, hey @copolii. Took a while to find test point as it hasn't been posted or published anywhere. From there it was still a bit tricky. Had to use BTV-DL09 board software to get fastboot only area in ram through factory mode (edl mode). Then fastboot flash the UPDATE.APP to boot to upgrade mode. Then flashed UPDATE.APP with localization files from upgrade mode. After that had to repair serial number and imei in order to get bootloader code. After all that let it update to nougat & emui 5 and it has 5GHz wifi which surprized me a bit. TWRP needs a little tuning and Magisk is working as it should. All of that was accomplished using SigmaKey dongle. Like I said, a bit tricky and don't believe it could have been fixed any other way. Oh, yeah same device, I bought it.
Click to expand...
Click to collapse
Hi @tek3195
I have the same problem.
do you have board software for mediapad m3 BTV DL09 (.xml version)
can you share with me
One more thing, does the process always cause loss of IMEI and serial number.
if so, can we repair it (imei and serial number) without a dongle (maybe via fastboot or twrp)?
I would really appreciate your help
0m M0m0d said:
Hi @tek3195
I have the same problem.
do you have board software for mediapad m3 BTV DL09 (.xml version)
can you share with me
One more thing, does the process always cause loss of IMEI and serial number.
if so, can we repair it (imei and serial number) without a dongle (maybe via fastboot or twrp)?
I would really appreciate your help
Click to expand...
Click to collapse
All I have is .skf format which is for SigmaKey. I have access to paid firmware, I can get .xml format and upload it for you. The only way I know of for xml is IDT which should be packaged with the firmware. What country do you need it for?
Here you should find 2 board software packages with tools and instructions. I've not used IDT before so don't have any insight on it. If you need anything else let me know.
BTV files
tek3195 said:
All I have is .skf format which is for SigmaKey. I have access to paid firmware, I can get .xml format and upload it for you. The only way I know of for xml is IDT which should be packaged with the firmware. What country do you need it for?
Here you should find 2 board software packages with tools and instructions. I've not used IDT before so don't have any insight on it. If you need anything else let me know.
http://www.mediafire.com/folder/43cwcl8hih2u2/BTV-DL09
Click to expand...
Click to collapse
Thank you for replying quickly.
Yes, my plan will be to use idt ver 2.0, because I don't have any dongel :crying:
idt ver 2.0 has a simpler configuration than version 1.0
Actually my devises are btv l0j (mediapa m3 docomo version)
so if you can get the btv l0j version then that would be great.
but if not, then the file that you shared earlier also I think will be enough.
tek3195 said:
... After that had to repair serial number and imei in order to get bootloader code. ..
Click to expand...
Click to collapse
As I have asked before, will this process always cause the loss of IMEI and SN?
if so, can we repair it without a dongle? (via fastboot or twrp maybe)
and once again thank you very much for all your help.
0m M0m0d said:
Thank you for replying quickly.
Yes, my plan will be to use idt ver 2.0, because I don't have any dongel :crying:
idt ver 2.0 has a simpler configuration than version 1.0
Actually my devises are btv l0j (mediapa m3 docomo version)
so if you can get the btv l0j version then that would be great.
but if not, then the file that you shared earlier also I think will be enough.
As I have asked before, will this process always cause the loss of IMEI and SN?
if so, can we repair it without a dongle? (via fastboot or twrp maybe)
and once again thank you very much for all your help.
Click to expand...
Click to collapse
I don't really know as I used sigma's firmware with there software. I have no idea how or what the process are with IDT and the packages I uploaded. Those are straight from easy-firmware, I will look and see if available for l0j.
Added BTV-L0J(2) to MediaFire folder, one 6.0 one 7.0.
tek3195 said:
I don't really know as I used sigma's firmware with there software. I have no idea how or what the process are with IDT and the packages I uploaded. Those are straight from easy-firmware, I will look and see if available for l0j.
Click to expand...
Click to collapse
here is from easy-firmware
https://easy-firmware.com/index.php?a=downloads&b=folder&id=33682
0m M0m0d said:
here is from easy-firmware
https://easy-firmware.com/index.php?a=downloads&b=folder&id=33682
Click to expand...
Click to collapse
Do you have easy-firmware account ?
tek3195 said:
Do you have easy-firmware account ?
Click to expand...
Click to collapse
No, I do not have.
I don't have enough extra money to buy premium easy-firmware. :crying: :crying: :crying:
I am very grateful to you for sharing the board software that I need.
as soon as possible I will try all the files and I will report the results here immediately.
tek3195 said:
I don't really know as I used sigma's firmware with there software. I have no idea how or what the process are with IDT and the packages I uploaded. Those are straight from easy-firmware, I will look and see if available for l0j.
Added BTV-L0J(2) to MediaFire folder, one 6.0 one 7.0.
Click to expand...
Click to collapse
I want to say thank you very much.
I confirm that the file that you shared is working very well.:good::good::good:
I have managed to revive my tab from dead, no power, no recovery, no fast boot, to be normal again. with
slightly modify to the .xml config, skip to the nvme section to avoid missing imei and sn.
The result is i managed to flash board software without losing IMEI and SN.:victory::victory::victory:
once again I really appreciate and thank you for your help.:angel::angel::angel:
tek3195 said:
Sorry, I forgot to post this before. So if anyone needs it and I'm sure they will.
Test point for BTV-W09 I would think BTV-DL09 would be the same, both have identical FCCID photos. content://media/external/images/media/28314 . To use test point you must disconnect battery. I would also recommend a little heat at top and bottom of display to remove.
I apologize for no link being posted . I didn't come back and check it , now attached an image hope it works. Don't know where the link went. In the pic there is only one test point as that is all that is used with Kirin devices apparently. The point at end of lime-green line is test point to be grounded with ground pin or any of the heat shields will work. A sharp pair of tweezers works well to make the short and make sure to disconnect battery.
Click to expand...
Click to collapse
hello i am also having a hard bricked d-01j, is it fixable? please give me detailed instructions, I thank you very much
---------- Post added at 08:04 AM ---------- Previous post was at 07:24 AM ----------
0m M0m0d said:
I want to say thank you very much.
I confirm that the file that you shared is working very well.:good::good::good:
I have managed to revive my tab from dead, no power, no recovery, no fast boot, to be normal again. with
slightly modify to the .xml config, skip to the nvme section to avoid missing imei and sn.
The result is i managed to flash board software without losing IMEI and SN.:victory::victory::victory:
once again I really appreciate and thank you for your help.:angel::angel::angel:
Click to expand...
Click to collapse
Hi, I got hard bricked just like you, have you fixed it? Could you please guide me to fix this error? Thank you very much !!!
0m M0m0d said:
Hi @tek3195
I have the same problem.
do you have board software for mediapad m3 BTV DL09 (.xml version)
can you share with me
One more thing, does the process always cause loss of IMEI and serial number.
if so, can we repair it (imei and serial number) without a dongle (maybe via fastboot or twrp)?
I would really appreciate your help
Click to expand...
Click to collapse
I have the same problem.
do you have board software for mediapad m3 BTV DL09 (.xml version)
can you share with me thank you very much