Related
hey guys....well i downgraded my nexus s 9020T for 4.0.3 to 2.3.6...however but while switching it on the 2.3.6..im getting a lock symbol while switching it on..and when i insert my sim onto the phone ..it is recognising the network but not catching the signal
kindly help me out
The lock symbol at the bottom means your bootloader is unlocked. This means you can replace your recovery partition to CWM or the likes, as well as flash superuser to the OS and flash custom ROMs. You would have achieved this through the "fastboot oem unlock" command.
The signal issue may be related to a bad flash. I would be going into recovery, doing a factory/data reset, formatting /system and /boot, and then flash the 2.3.6 file you have again. Remembering of course to backup anything currently on the phone, and doing a NANDROID backup if you don't have a working one already.
thank so much for the information...after doing this..can my phone still OTA official updates from google once they are released??
roshan567 said:
thank so much for the information...after doing this..can my phone still OTA official updates from google once they are released??
Click to expand...
Click to collapse
As long as you flash a official update
Sent from my ice cream powered Nexus S
a friend of mine is doing the flashing...any idea as to how can i know whether he has flashed an official update or not?
also what is the different between flashable roms n the increamental updates given in this link??
http://forum.xda-developers.com/showthread.php?t=1063664
are both official versions given out by google?
Yes, all of the links in that thread are official Google builds. The full/flashable ROMs are the full operating system in one file. You can install this over any Android version/ROM since the zip will contain all of the files necessary to get the system working.
The incremental updates should only be used if you have a specific (official) Android version and wish to only install the updated files. For example, if you have the official Google release of 2.3.6 and wish to upgrade to 4.0.3, you can use the 2.3.6 -> 4.0.3 incremental update. Otherwise, if don't have one of the supported incremental update versions or if you're using a non-stock ROM then you'll need to download the full ROM.
thank you so much for the information....
i am downgrading my OS to 2.3.6 from 4.0.3..how can i find out whether the 2.3.6 OS ive installed is the original OS???
You can find out BEFORE flashing the rom by comparing checksums, the zip file should have the exact same checksum as indicated in the filename of the files in that thread. Also, that thread just links to files from googles servers used for official updates.
Once it's installed there is no point trying to finding out if it is 100% stock.
Harbb said:
You can find out BEFORE flashing the rom by comparing checksums, the zip file should have the exact same checksum as indicated in the filename of the files in that thread. Also, that thread just links to files from googles servers used for official updates.
Once it's installed there is no point trying to finding out if it is 100% stock.
Click to expand...
Click to collapse
thanks for the information...i didn understand properly how do u do checksums..can you pls explain it??im a noob..
Checksum (or hash) is a way to verify a file. It will create a word/number/pattern/etc according to an algorithm based on all the data in the file. With MD5, SHA1, etc we have a practically guaranteed chance of comparing the two files. Those files there are straight from google and google has provided the checksums in the filename (part of the checksum, at least). If you have any file at all and it has the same code as that, we can be happy that it's the exact same file - thus 100% stock
You can use software such as Checksum or my personal favourite HashTab to find the various comparing techniques.
hey thanks a lot for your information..it really helps....
when i upgraded to ICS my phone stopped receiving reception after 2 days..when i downgraded it after unlocking the bootloader it still wasnt receiving recepetion...why does this happen?
Possibly it's better to split A510 and A511 stock rom firmware list?
Here's the list of A511 ROMs I have found (looks like just one downloadable so far):
Acer_AV041_A511_0.003.00_WW_GEN1
Acer_AV041_A511_0.008.00_WW_GEN1
Acer_AV041_A511_1.011.00_WW_GEN1 (download here) - translation
Acer_AV041_A511_1.028.00_EMEA_DE
Acer_AV041_A511_1.032.00_WW_GEN1 (available through FOTA on my device)
Acer_AV041_A511_1.035.03_WW_GEN1 (mentioned on benchmark website)
Regards,
Nika.
Added new version:
"Acer_AV041_A511_1.032.00_WW_GEN1 (available through FOTA on my device)"
3G version
Is the 3G version out?
Petya19 said:
Is the 3G version out?
Click to expand...
Click to collapse
Sure, that's the A511. Might depend on the region though...
Sent from my S300 using xda premium
Acer_AV041_A511_1.028.00_EMEA_DE
Hey, i have canceld my system. Now i look for this rom or a costum rom for my 511. Its functionally with adb or bootloader. Thanks
http://android.clients.google.com/p...511_AV041.RV35RC04_AV051.RV00RC06_EMEA_DE.zip
It's the direct link for the new JB 4.1.2 update for A511 EMEA_DE devices. :good:
Hi
Anyone know where to download Acer_AV041_A511_1.028.00_EMEA_DE
need it to get my a511 back to stock so that i can install 4.1.2
regards chris
Same over here.
I rooted my A511 and now I can't go back, already tried several things but everytime I install the OTA update I get a bootloader error. (Yes my bootloader is back to stock)
chris1005 said:
Hi
Anyone know where to download Acer_AV041_A511_1.028.00_EMEA_DE
need it to get my a511 back to stock so that i can install 4.1.2
regards chris
Click to expand...
Click to collapse
I'm in a similar boat (bricked my device and somehow need to flash something to have the tablet boot). Can't we just use the firmware linked in the OP? It might not be the german version but I suppose we could still flash it and just change the language or something? Anyway, that's what I'm gonna try as soon as my SD card arrives.
Is it possible, to install the english OS on a "german" tablet?
Or encounter some problems?
English itself, shouldn't be the problem.
I was wondering whether I might get some helpt flashing the "Acer_AV041_A511_1.011.00_WW_GEN1". My Tablet has been bricked for some time because I (stupid as I am) tried to do a factory reset using the recovery provided by nikagl even though he specifically said that we were not to do that (I did read that warning but after a few weeks I just forgot about it :/).
Anyway, I've installed the cmw recovery by nothrills and tried to flash aforementioned firmware. I put it on an external SD card which has been formatted to FAT32. I went to the recovery menu and tried to flash the zip file. However, I got a getprop(product.name) error and the installation was aborted. After browsing the board a bit I found out that I have to delete the line starting with 'assert(getprop("ro.product.name")' which is located in META-INF\com\google\android\. But still, the tablet won't flash the firmware. It simply says "Installation aborted. Status 5 [or 6]".
I've also tried flashing the firmware by going back to stock recovery, renaming the firmware to update.zip and starting the tablet by holding the power and the minus button which is supposed to start the flashing process automatically. However, that just results in a red " ! " and an Android lying on its back.
I'd really appreciate it if someone was able to help me. (I've already sent the tablet to the Acer customer service who said that the installation of cmw recovery has damaged the motherboard. They say they will replace it for ~250€.)
Thank you for trying to help, I really appreciate it .
You have to edit line 1 of the updater-script in META-INF\com\google\android\
Delete this: in assert(getprop("ro.product.name") == "a510_emea_de");
Click to expand...
Click to collapse
That is mostly what I did. Except I used winrar instead of 7zip. The first line of the updater-script was "assert(getprop("ro.product.name") == "a511_ww_gen1");" and I deleted it. When I then try to flash the file it says "E:Error in /external_sd/Acer_AV041_A511_1.011.00_WW_GEN1 - Copy.zip (Status 6)"
I also tried renaming the zip file first but the result was the same.
Edit:
As it turns out, the Status 6 error does only occur when I edit the updater-script file with wordpad. If I open it with the editor it works just fine. I was able to flash the firmware. However, the tablet then wouldn't do anything else then showing "Acer" on the screen for ever and ever and ever and ever :/.
In the case you installed a A510 ROM (without 3G) and can't flash back to the original A511 to be able to upgrade to JB and have a working 3G functionality, cause CWM vomits status 7 or 4 errors while flashing the offered .zip, try this way
Greetz
Pauli
I tried to ask the question before but had no luck getting the answer.
I have rooted tmobile one s, version 1.53 (every one else seems to have 1.78).
I need to update my software.
I downloaded ota update but installation failed.
I have removed couple originals mobile software.
No new rom is installed.
I am sure the question was asked before but I do not seem to find it.
I appreciate if someone post a link or have some guidance on this as to what steps are needed.
dell4320 said:
I tried to ask the question before but had no luck getting the answer.
I have rooted tmobile one s, version 1.53 (every one else seems to have 1.78).
I need to update my software.
I downloaded ota update but installation failed.
I have removed couple originals mobile software.
No new rom is installed.
I am sure the question was asked before but I do not seem to find it.
I appreciate if someone post a link or have some guidance on this as to what steps are needed.
Click to expand...
Click to collapse
Version 1.53 means you are on RomBase 1.53 ??
dell4320 said:
I tried to ask the question before but had no luck getting the answer.
I have rooted tmobile one s, version 1.53 (every one else seems to have 1.78).
I need to update my software.
I downloaded ota update but installation failed.
I have removed couple originals mobile software.
No new rom is installed.
I am sure the question was asked before but I do not seem to find it.
I appreciate if someone post a link or have some guidance on this as to what steps are needed.
Click to expand...
Click to collapse
The OTA update would bring you to version 1.84, the other versions are not for TMOUS. It would seem to help if you gave more details as to how the OTA failed like error messages and such, as well as what "couple originals mobile software" it was you removed, was that some swinging app?
Thank you, here is more info to clarify the question:
Android version 4.0.3
Htc sense version 4.0
Software number 1.53.531.1671 ORD
Htc sdc API level 4.11kernel version 3.0.8-01053-g5dc1dc4
Base version 0.16.31501s.02_10.18
Build number 1.53.531.16CL47441 release keys
The software I removed wifi manager , where is my water, twitter and another one do not remember the name.
The error I am getting when I try to install the downloaded OTA is
[I]Certifying current system....assert failed: apply _patch_check("/system/apphtcTwitterWidget_30.
E:Error in / internal_sdcard/download/OTA_ville_U_TMOUS_1.84.531.16_release2651973.....zip
Status 7
Installation aborted[/I]
I was up for two nights trying to figure how to install the update with no luck. Any assistance is appreciated.
Ok. Easy fix. Download the t mobile nandroid and install the zip in cwm recovery and you'll be on 1.84 . It's in dev section. Make sure you get the t mobile one.
Sent from my HTC VLE_U using xda premium
dell4320 said:
Thank you, here is more info to clarify the question:
Android version 4.0.3
Htc sense version 4.0
Software number 1.53.531.1671 ORD
Htc sdc API level 4.11kernel version 3.0.8-01053-g5dc1dc4
Base version 0.16.31501s.02_10.18
Build number 1.53.531.16CL47441 release keys
The software I removed wifi manager , where is my water, twitter and another one do not remember the name.
The error I am getting when I try to install the downloaded OTA is
[I]Certifying current system....assert failed: apply _patch_check("/system/apphtcTwitterWidget_30.
E:Error in / internal_sdcard/download/OTA_ville_U_TMOUS_1.84.531.16_release2651973.....zip
Status 7
Installation aborted[/I]
I was up for two nights trying to figure how to install the update with no luck. Any assistance is appreciated.
Click to expand...
Click to collapse
Have never had any issues myself but read that OTAs and possibly RUU (?) sometimes require all original apps to be present. You could try to find that TwitterWidget .apk somehow like in /system/app that nandroid Mike talked about, copy it to your SDcard and install it then try the OTA again. Or just install the whole Nandroid in CWM, make sure you backup your stuff first if you mess it up
http://forum.xda-developers.com/showthread.php?t=1698861
Sent from my HTC VLE_U using xda premium
Thank you Mike, can I push my luck and get an answer on how to unzip the update file and how to create cwm step by step link. Thank you again all. It is a rough journey.
dell4320 said:
Thank you Mike, can I push my luck and get an answer on how to unzip the update file and how to create cwm step by step link. Thank you again all. It is a rough journey.
Click to expand...
Click to collapse
you dont unzip any update file, you have a few way to fix this:
1: Restore the apps that the OTA update is complaining about. To do this you download the Nandroid file Mike linked to and use winzip, 7zip or whatever to open it in Windows and find the twitterwidget file in it. Then you copy it to your phones SDCard and click it on your phone. You might have to check the setting to allow apps from other sources than the Play Store in phone settings. Hopefully this works, if not you have to bootloader unlock your phone and root it. There are good guides stickied around here.
2: Unlock your bootloader so you can install CWM recovery, then download the Nandroid file to your SDCard, boot into CWM recovery, and restore the Nandroid. A Nandroid is a complete backup of someones phone software and settings. This might wipe all your data.
3: Easiest way might be to run a RUU for T-Mobile USA with version 1.84. This might wipe all your data. A RUU is a program you run in Windows with your phone connected via USB, it'll factory reset your phone with the version of software in the specific RUU file, you can find a TMOUS one in development section, the thread is called Ville/VilleC2 shipped ROMs.
4: Send it in to TMOUS and they'll probably run a RUU for you.
Thank you frdd:
1: I tried to do number one, but the unzipped files still does not have a breakdown for the specific twitterwidget, somehow it will have to be within a system file that has different name. My phone is unlocked and rooted.
2- eventhough my phone is unlocked, i still can not install cwm, i guess it has something to do with previous postings where others have a problem entering the recovery on htc one s
4- I will do as last resort.
3- I am trying to do now, Do I have to relock the bootloader? is there a step by step guide on how to run RUU.
Thank you again.
Hi, Is there any one suceeded to downgrade from leak Jb 4.1 to ICS 4.0.4??
If yes could some one make video or provide step by step procedure.
There is no thread related to downgrade from leak jb 4.1 to ICS 4.0.4
even though many claimed they suceeded to downgrade.
Thanks
amritn said:
Hi, Is there any one suceeded to downgrade from leak Jb 4.1 to ICS 4.0.4??
If yes could some one make video or provide step by step procedure.
There is no thread related to downgrade from leak jb 4.1 to ICS 4.0.4
even though many claimed they suceeded to downgrade.
Thanks
Click to expand...
Click to collapse
I have. You will have to download the correct file from here . (if your phone is Asia retail like mine , download the 2nd one in the list)
Flashing is the same way you did the JB leak. It's via RSD, put the phone in fastboot and flash via RSD.
--------------------------------------
LIFE!
IT'S WHAT YOU MAKE OUT OF IT!
Lifehacker7 said:
I have. You will have to download the correct file from here . (if your phone is Asia retail like mine , download the 2nd one in the list)
Flashing is the same way you did the JB leak. It's via RSD, put the phone in fastboot and flash via RSD.
--------------------------------------
LIFE!
IT'S WHAT YOU MAKE OUT OF IT!
Click to expand...
Click to collapse
My second and last question is( bear with me it's some how long)
1 I was previously in gingerbread 2.3.6,( the phone was asia retail), I flashed directly from gingerbread to jb leak 4.1.
Everything seemed ok and it passed RSD and the phone booted but stuck in motrolla splash screen ( kinda soft brick),
There was error in my lappy running window 7 64bit , mtp usb drive failed to instal(In device manager when i tried to update mtp usb driver it said
newer version of driver already installed),
Now a second scenerio starts Being in softbrick I tried to downgrade from jb to ICS, every firmware except those written with fastboot p3( I guess only chinese version) can be flashed through RSD , otherwise if fimware like 6.7.2 ------mearet or 6.7.2 ------ searet when flashed failed with error in step 4 in rsd like it shows rebooting in bootloader and shows failed error. So my point is only chines firmware with fastboot p3 can be flashed easily. Now I flashed both chinese and hongkong ICS firmware with title fastboot p3-------, and they both flashed correctly and passed but same things happened as jb leak, stuck in M logo and mtp usb driver failed error in my lappy.
Now my last option to fully boot was to go to gingerbread , so I downloaded couple of stock rom like 5.5.1 edem-27searet, it didnot flashed and got error with rebooting bootloader in step 4 or 5. At last I tried fastboot-p3_edison-edison-user-4.0.4-6.7.2_GC-180-EDS-20-31-release-keys-ChinaRetail-CN_chn.tar and it booted properly.
Now again I tried two times to go to ICS or jb leak and samething happened, stuck in M logo. But gb firmware always booted properly.
Please read above scenario before replying, because I haven't seen such situation in the whole xda thread for atrix 2 and by googling, Everyone flashed the rom and they said booted properly
My questions are
1 I want to flash jb leak rom or otherwise ICS, what will be my step?? I'm desperate to try these roms. Please keep in mind about my above situation as i'm unable to flash like other people do.
2 Why the above situation happening like softbrick while upgrading and why other firmware file are not flashing except titled with fastboot? Is it related to kernel or bootloader. When I was in xperia S when I updated from gb to ics same scenario occured but i tackeled situation by flashing in kernel. When I was in AT&T Infuse 4g, I tacked the above situation by upgrading from froyo to gb by updating from froyo bootloader to gb one.
But situation about atrix 2 just blow my head, I'm trying from 4 days, read every thread of xda related to atrix 2 , atrix 4g, googled for solution, watched video from youtube, tried every firmware but none solved my problem .
So waiting for solution from my senior XDA's
Thanks
1. we have a locked bootloader. ( no custom kernels/edits )
2. You aren't supposed to flash any other firmware files other than the correct one according to your phone region.
3.all the files from the thread i linked to are fastboot files ( correct me if i'm wrong) and are to be flashed via RSD while in fastboot mode ( turn off the phone, press power and volume down simultaneously to get there).
And by mistake of you flashed att firmware, then your phone will be completely screwed up. ( there are hardware and bootloader differences bw att and international versions )
Since you can successfully boot to gb, which firmware version does it state ?
Have you tried taking an OTA ICS? ( idk how well it might go).
I hope Jim comes across this thread
--------------------------------------
LIFE!
IT'S WHAT YOU MAKE OUT OF IT!
Lifehacker7 said:
1. we have a locked bootloader. ( no custom kernels/edits )
2. You aren't supposed to flash any other firmware files other than the correct one according to your phone region.
3.all the files from the thread i linked to are fastboot files ( correct me if i'm wrong) and are to be flashed via RSD while in fastboot mode ( turn off the phone, press power and volume down simultaneously to get there).
And by mistake of you flashed att firmware, then your phone will be completely screwed up. ( there are hardware and bootloader differences bw att and international versions )
Since you can successfully boot to gb, which firmware version does it state ?
Have you tried taking an OTA ICS? ( idk how well it might go).
I hope Jim comes across this thread
--------------------------------------
LIFE!
IT'S WHAT YOU MAKE OUT OF IT!
Click to expand...
Click to collapse
Thanks for ur fastest reply
1 True i know our bootloader is locked
2 If we aren't how we can flash chinese firmware on our set?
3 True
4 True At&T firmware can't be flashed on or model and vice versa
5 As per ur question gb version which i can boot is 2.3.6 and the firmware i Flashed is fastboot-p3_edison_edison-user-2.3.6-5.5.1-1_GC-109-52-release-keys-ChinaRetail-CN_chn.tar.gz
6 Can I take OTA ICS even though my set was not previously in Chinese firmware out of box. By luck or unluck I'm now settled in chinese firmware
7 Now last question is can i go directly to Angeeks jb 4.1 firmware posted in the thread.
Once again thanks :good:
2 I
Lifehacker7 said:
1. we have a locked bootloader. ( no custom kernels/edits )
2. You aren't supposed to flash any other firmware files other than the correct one according to your phone region.
3.all the files from the thread i linked to are fastboot files ( correct me if i'm wrong) and are to be flashed via RSD while in fastboot mode ( turn off the phone, press power and volume down simultaneously to get there).
And by mistake of you flashed att firmware, then your phone will be completely screwed up. ( there are hardware and bootloader differences bw att and international versions )
Since you can successfully boot to gb, which firmware version does it state ?
Have you tried taking an OTA ICS? ( idk how well it might go).
I hope Jim comes across this thread
--------------------------------------
LIFE!
IT'S WHAT YOU MAKE OUT OF IT!
Click to expand...
Click to collapse
A small correction.. If you have a retail phone, you can flash any region firmware as long as it is for this phone. Just don't flash att ones. The radio is different and your phones cdt security number will be increased if you do.
Regarding flashing jb leak, how long did you wait after flashing? First boot usually takes long..
Sent from my MB865 using Tapatalk 2
Ravikirancg said:
A small correction.. If you have a retail phone, you can flash any region firmware as long as it is for this phone. Just don't flash att ones. The radio is different and your phones cdt security number will be increased if you do.
Regarding flashing jb leak, how long did you wait after flashing? First boot usually takes long..
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
About 30 minutes after flashing
More update I Flashed ics hk firmware, and this time it showed android is upgrading 1of 30, then passed 30/30 and then freezed for 25 minutes.
So after waiting for 20 minutes and stuck in android is upgrading I took out the battery and entered into recovery and did factory reset and wipe cached.
Now this time no android is upgrading message came up and stuck in M logo
To try any of the ROMs available ( except the gb ones, official jb leak, and one or 2 ROMs based on that) you should be on an ICS base ( they are built based on the ics kernel).
And to try the angeeks jb ROM, you should be on the JB leak 1st.
ROMs like PA, CM10, 10.1, they all need ics as base.
If nothing is really working out, you should probably give the phone to service station.( tell some lie about how that happened )
--------------------------------------
LIFE!
IT'S WHAT YOU MAKE OUT OF IT!
Ok, so... there is a major issue going on here.
You flashed the HK/TW firmware on an international MEARET or SEARET phone, the HK or TW firmware is very much like the AT&T versions and that they lock the bootloader version so that upgrading or downgrading and changing firmware regions are blocked for the most part. There is a file in all the firmware version that tells RSD and the phone if it can or can not flash things... the one everyone knows is the CDT.bin, and the one that not everyone knows about is the CID, and the CID can get you into BIG trouble if you do not know what it is, or why it is there, so DO NOT mess with it, unless you know what you are doing... The CDT.bin on the other hand is part of EVERY FXZ, it will tell RSD if you can flash something for the most part or not.
Your ONLY chance is to flash your PROPER version of ICS firmware through fastboot commands. I will not give directions again, they are posted in several threads in here, do a search in the general section for the commands.... you MUST flash all the same files that RSD lite would to make this work, and you can no skip any of them. I would look for the order and the files to flash in the .xml file that comes with the firmware so that you know the order and partition names and such.
You MUST have the following and at the latest versions, even if you have the drivers installed, uninstall them and reinstall them again.
1) A2 moto drivers
2) Android SDK
3) moto-fastboot command/utility for your operating system
4) The PROPER ICS FXZ file for your phone and region
5) understanding of the comand line and the commands that are needed to flash with the moto-fastboot utility
After you have done all of that flashing, you should be on the proper ICS for your region. If you want to try and do the JB leak again, then it MIGHT, work, but I am not sure if it will or not.
It is a real bad idea to flash other regions firmwares to your phone, unless they are leaks, and have been tested to work on your regions handset, just for future reference.
jimbridgman said:
Ok, so... there is a major issue going on here.
You flashed the HK/TW firmware on an international MEARET or SEARET phone, the HK or TW firmware is very much like the AT&T versions and that they lock the bootloader version so that upgrading or downgrading and changing firmware regions are blocked for the most part. There is a file in all the firmware version that tells RSD and the phone if it can or can not flash things... the one everyone knows is the CDT.bin, and the one that not everyone knows about is the CID, and the CID can get you into BIG trouble if you do not know what it is, or why it is there, so DO NOT mess with it, unless you know what you are doing... The CDT.bin on the other hand is part of EVERY FXZ, it will tell RSD if you can flash something for the most part or not.
Your ONLY chance is to flash your PROPER version of ICS firmware through fastboot commands. I will not give directions again, they are posted in several threads in here, do a search in the general section for the commands.... you MUST flash all the same files that RSD lite would to make this work, and you can no skip any of them. I would look for the order and the files to flash in the .xml file that comes with the firmware so that you know the order and partition names and such.
You MUST have the following and at the latest versions, even if you have the drivers installed, uninstall them and reinstall them again.
1) A2 moto drivers
2) Android SDK
3) moto-fastboot command/utility for your operating system
4) The PROPER ICS FXZ file for your phone and region
5) understanding of the comand line and the commands that are needed to flash with the moto-fastboot utility
After you have done all of that flashing, you should be on the proper ICS for your region. If you want to try and do the JB leak again, then it MIGHT, work, but I am not sure if it will or not.
It is a real bad idea to flash other regions firmwares to your phone, unless they are leaks, and have been tested to work on your regions handset, just for future reference.
Click to expand...
Click to collapse
Thanks jim for the gr8 info,
Would you recommend me for OTA update to Ics from here? It's saying update available
Do my mobile boot in this scenario?
Any consequences taking OTA.
Thanks again for help
amritn said:
Thanks jim for the gr8 info,
Would you recommend me for OTA update to Ics from here? It's saying update available
Do my mobile boot in this scenario?
Any consequences taking OTA.
Thanks again for help
Click to expand...
Click to collapse
I would not take any OTA, since we have FXZ files that are properly made for the regions our phones are made for, if you know what I mean. The only difference is that an FXZ will wipe your phone clean and you have to resync with google for calandar and e-mail and contacts and apps and such.
With out knowing the EXACT firmware you are on right now, I can not really tell you how safe an OTA or an FXZ will be for you. I am only guessing at this point, that you are still on the HK/TW firmware, and why I suggested you flash the MEARET/SEARET firmware by hand with the moto-fastboot commands, to get you where you should be again, before you try the JB leak, or whatever you are after.
Need to make decision!
Hi guys!
For first, sorry for my bad english. I hope you can understand me. Greeting from Belarus!
I have ME865 with United Arab Emirates warranty.
I flashed my Atrix 2 from 2.3.6 to 4.0.4 6.7.2_EDEM-18-MEARET. It worked fine.
Then I flashed official 4.1.2 leak, rooted it.
Which region firmware I need choose to success downgrade from 4.1.2 to 4.0.4?
Really need your answer! Thanks!
I have some bugs on JB:
1. Can't send and recieve mms.
2. APN dissapear after every reboot. Fix - after reboot turn on/off airplane mode.
3. Bad GPS. Fix - install GpsFix app.
4. Recieve USSD message with sound.
_________________________________________
Just had flash 4.0.4 mearet. All works.
jimbridgman said:
I would not take any OTA, since we have FXZ files that are properly made for the regions our phones are made for, if you know what I mean. The only difference is that an FXZ will wipe your phone clean and you have to resync with google for calandar and e-mail and contacts and apps and such.
With out knowing the EXACT firmware you are on right now, I can not really tell you how safe an OTA or an FXZ will be for you. I am only guessing at this point, that you are still on the HK/TW firmware, and why I suggested you flash the MEARET/SEARET firmware by hand with the moto-fastboot commands, to get you where you should be again, before you try the JB leak, or whatever you are after.
Click to expand...
Click to collapse
As per your question jim I'm currently in android version 2.3.6
system version 55.91.109.ME865.ChinaRetail.en.CN
Model number ME865
build number 5.5.1-1_GC-109
Kernel version 2.6.35.7-g8b6f7f9
[email protected]#1
And I flashed this firmware to get fully boot fastboot-p3_edison_edison-user-2.3.6-5.5.1-1_GC-109-52-release-keys-ChinaRetail-CN_chn.tar.gz
-Also tried different firmware like jb 4.1 leak flashed passed booted but stuck in M logo splash screen.
-Flashed both ICS build from china and hk/tw and stuck in M logo as in jb
-Tried searet and Mearet firmware for both ICS and Gb build but failed after 5/21 rebooting to bootloader and failed
-And at last I tried fastboot-p3_edison_edison-user-2.3.6-5.5.1-1_GC-109-52-release-keys-ChinaRetail-CN_chn.tar passed and booted.
Jim What will be my next move??
Can I try fast boot method as u mentioned or OTA update to ICS
Thanks
amritn said:
As per your question jim I'm currently in android version 2.3.6
system version 55.91.109.ME865.ChinaRetail.en.CN
Model number ME865
build number 5.5.1-1_GC-109
Kernel version 2.6.35.7-g8b6f7f9
[email protected]#1
And I flashed this firmware to get fully boot fastboot-p3_edison_edison-user-2.3.6-5.5.1-1_GC-109-52-release-keys-ChinaRetail-CN_chn.tar.gz
-Also tried different firmware like jb 4.1 leak flashed passed booted but stuck in M logo splash screen.
-Flashed both ICS build from china and hk/tw and stuck in M logo as in jb
-Tried searet and Mearet firmware for both ICS and Gb build but failed after 5/21 rebooting to bootloader and failed
-And at last I tried fastboot-p3_edison_edison-user-2.3.6-5.5.1-1_GC-109-52-release-keys-ChinaRetail-CN_chn.tar passed and booted.
Jim What will be my next move??
Can I try fast boot method as u mentioned or OTA update to ICS
Thanks
Click to expand...
Click to collapse
But you are supposed to be on SEARET/MEARET as your "real" "home" firmware, correct?
If you are supposed to be on SEARET/MEARET, then I would go here, and grab the ICS FXZ file for the SEARET/MEARET firmware, and use the fastboot commands to try and flash it. As always there is no guarantee, and there is always a chance of brick so be careful.
The reason I am really pushing for using the fastboot commands, as I mentioned earlier, that since you are "manually" flashing the parttitions one at a time, from the command line, there will be no checks to see if the proper CDT.bin is on the phone before it does it, and this will save you, in that you should be able to put your "correct" firmware on the phone, I hope.
I have one last question, are you 100% sure that you actually purchased an international MEARET/SEARET phone, and not an HK/TW version of the phone? This is just a thought, since you did say that you were unable to flash any firmware besides the ME865 china HK/TW version... which does bring up that concern.
jimbridgman said:
But you are supposed to be on SEARET/MEARET as your "real" "home" firmware, correct?
If you are supposed to be on SEARET/MEARET, then I would go here, and grab the ICS FXZ file for the SEARET/MEARET firmware, and use the fastboot commands to try and flash it. As always there is no guarantee, and there is always a chance of brick so be careful.
The reason I am really pushing for using the fastboot commands, as I mentioned earlier, that since you are "manually" flashing the parttitions one at a time, from the command line, there will be no checks to see if the proper CDT.bin is on the phone before it does it, and this will save you, in that you should be able to put your "correct" firmware on the phone, I hope.
I have one last question, are you 100% sure that you actually purchased an international MEARET/SEARET phone, and not an HK/TW version of the phone? This is just a thought, since you did say that you were unable to flash any firmware besides the ME865 china HK/TW version... which does bring up that concern.
Click to expand...
Click to collapse
Jim You are genious, Now with fastboot command i'm in the stage where I was 4 days ago pure stock. The firmware which didnot flashed through RSD , flashed with fastboot commands. But with fastboot commands moto-fastboot.exe flash grfs grfs.img, showed error as failed no such partitions. But even without that i'm now booted in stock Sereat gingerbread firmware. Now I will flash ICS firmware through fastboot and will update if anything goes wrong wrong or write
Thank u:good:
Update whatever I do I get stuck in splash screen or M logo after flashing ICS fxz file or Jb file using any method either fastboot
or RSD even though i'm fully stock now 2.3.6 sereat
amritn said:
Update whatever I do I get stuck in splash screen or M logo after flashing ICS fxz file or Jb file using any method either fastboot
or RSD even though i'm fully stock now 2.3.6 sereat
Click to expand...
Click to collapse
Make sure you are getting your FXZ files from a well known good source.
This is the best one:
http://sbf.droid-developers.org/edison/list.php
Try and flash the ICS one, I think it is this one, that you want:
http://sbf.droid-developers.org/edison/6.7.2_EDEM-18-SEARET_cfc.xml.zip
Try it with RSD lite version 6+ ONLY, then if that does not work, try it with the fastboot commands again.
You should not try and flash the p3 files, until you get to ICS first. I think it all has to do with the bootloader versions, and why you can not go from GB to JB. You have to go to ICS then JB, I am pretty sure of that.
jimbridgman said:
Make sure you are getting your FXZ files from a well known good source.
This is the best one:
http://sbf.droid-developers.org/edison/list.php
Try and flash the ICS one, I think it is this one, that you want:
http://sbf.droid-developers.org/edison/6.7.2_EDEM-18-SEARET_cfc.xml.zip
Try it with RSD lite version 6+ ONLY, then if that does not work, try it with the fastboot commands again.
You should not try and flash the p3 files, until you get to ICS first. I think it all has to do with the bootloader versions, and why you can not go from GB to JB. You have to go to ICS then JB, I am pretty sure of that.
Click to expand...
Click to collapse
Jim no matter what I do i cannot upgrade my firmwawre either to ICS or jellybean, Always stuck Im motrolla splash screen at the last stage of boot. But if i return to gingerbread on both chinese and asian retail(using fastboot or RSD) it's working.I've tried everything. It's out of my mind now.
There is something that is causing my mobile not to boot. If u do have any idea, please help me.
Apart from that I want to know do we have ICS stock kernel in zip format which we can flash?
If other ppl had same problem and solved it pls share with me. This seems something new, softbrick in ICS everytime no matter which region firmware i flash apart from AT&T firmware. I'm trying since 5 days.
Pls reply xda senior member or anyone those in similar case.
amritn said:
Jim no matter what I do i cannot upgrade my firmwawre either to ICS or jellybean, Always stuck Im motrolla splash screen at the last stage of boot. But if i return to gingerbread on both chinese and asian retail(using fastboot or RSD) it's working.I've tried everything. It's out of my mind now.
There is something that is causing my mobile not to boot. If u do have any idea, please help me.
Apart from that I want to know do we have ICS stock kernel in zip format which we can flash?
If other ppl had same problem and solved it pls share with me. This seems something new, softbrick in ICS everytime no matter which region firmware i flash apart from AT&T firmware. I'm trying since 5 days.
Click to expand...
Click to collapse
get it done from moto service center
Sent from my ME865 using xda premium
Hello co-A510 users,
I've been lurking for quite a while and I repeatedly see questions about "how to get the JB bootloader?". Followed by the answer "Go back to stock ICS, then get the OTA.". Usually followed by the follow-up question "B-b-but... how?"
This post attempts to answer that follow-up question, for most folks, in the easiest way possible.
The Six Steps to Stock:
Step 1: Download the Stock Acer OS (rom zip)
- Go to http://www.acer.com.au/ac/en/AU/content/drivers
- Select Tablet >> Iconia A >> A510 in the product list
- On the new web portion that will appear, select the "O.S." tab, and download your appropriate build (mine is WW.GEN 1)
Step 2: Flash the OS (rom zip)
- Save the zip in your SD card
- Enter your custom recovery, and flash it
- After the successful flash, reboot your system
- CWM will ask you if you want to keep your custom recovery, say NO. Remember, you want to go back to stock. So let the zip do it's job
Step 3: Check your System Date and Time
- Once booted, make sure that your date and time (time zone included) is correct.
Step 4: Check for System Updates
- Go to Settings >> About Tablet >> System Update >> Check now
Step 5: Wait
- If a pop-up is saying that you're on the latest version, try again at a later time.
- If there's no pop-up saying you're on the latest version, wait. It's a 252MB JB rom downloading in the background.
Step 6: OTA Update
- Once the JB zip is downloaded, a pop-up will say "Install Later, More details, Install Now"
- Select Install Now
- After a few familiar windows, you will now be on the JB recovery, and the JB rom. Ready for the adventure ahead.
This is nice, but a little info regarding why installing JB bootloader would be nice (if I remember correctly one of the things is to reduce the screen flicker, but that's what I THINK), and also how to root and get back in custom ROM road
Oh, and also, is there a way to know what verion of tab we have if we're already on custom ROM?
Lusanagi said:
This is nice, but a little info regarding why installing JB bootloader would be nice (if I remember correctly one of the things is to reduce the screen flicker, but that's what I THINK), and also how to root and get back in custom ROM road
Oh, and also, is there a way to know what verion of tab we have if we're already on custom ROM?
Click to expand...
Click to collapse
The main reason that you would want to have the JB bootloader, is to fix the audio stutter bug of the ICS bootloader.
(If you're on the ICS bootloader, play some music files, then turn your screen off. The CPU throttles down to the point of slowing down your music player.)
About how to root JB, I think it should deserve it's own thread. I simply follow the one here, it's pretty complete already (I rooted my stock JB just an hour ago):
http://forum.xda-developers.com/showthread.php?p=35907925#post35907925
And yes, whatever ROM you are on, you almost always have the settings >> about phone menu.
what I meant was get the appropriate build (either WW.GEN 1 or AAP.AU2); I did enter About Phone, but wasn't able to find any of that data (obviously)
Lusanagi said:
what I meant was get the appropriate build (either WW.GEN 1 or AAP.AU2); I did enter About Phone, but wasn't able to find any of that data (obviously)
Click to expand...
Click to collapse
Ah... good point. What I personally did was to restore my nandroid back-up from my stock image.
As an alternative, I would say flash NoThrills' optimized WW Gen1 rom. However, I do admit that it is something that I never tried as base. And it's a "do it at your own risk" thing.
Firmware version 1.073 A510 ICS
After flashing you will have stock firmware 1.73.00 WW GEN with closed bootloader.
Flash the fastboot mode (with unlock bootloader).
Run the restore.bat in the extracted archive folder.
After flashing tablet upgraded to firmware version AV051_A510_1.034.00_WW_GEN1 by OTA.
First post in 4PDA
Sorry for my english .. :cyclops:
salisbury_steak said:
Hello co-A510 users,
I've been lurking for quite a while and I repeatedly see questions about "how to get the JB bootloader?". Followed by the answer "Go back to stock ICS, then get the OTA.". Usually followed by the follow-up question "B-b-but... how?"
This post attempts to answer that follow-up question, for most folks, in the easiest way possible.
The Six Steps to Stock:
Step 1: Download the Stock Acer OS (rom zip)
- Go to http://www.acer.com.au/ac/en/AU/content/drivers
- Select Tablet >> Iconia A >> A510 in the product list
- On the new web portion that will appear, select the "O.S." tab, and download your appropriate build (mine is WW.GEN 1)
Step 2: Flash the OS (rom zip)
- Save the zip in your SD card
- Enter your custom recovery, and flash it
- After the successful flash, reboot your system
- CWM will ask you if you want to keep your custom recovery, say NO. Remember, you want to go back to stock. So let the zip do it's job
Step 3: Check your System Date and Time
- Once booted, make sure that your date and time (time zone included) is correct.
Step 4: Check for System Updates
- Go to Settings >> About Tablet >> System Update >> Check now
Step 5: Wait
- If a pop-up is saying that you're on the latest version, try again at a later time.
- If there's no pop-up saying you're on the latest version, wait. It's a 252MB JB rom downloading in the background.
Step 6: OTA Update
- Once the JB zip is downloaded, a pop-up will say "Install Later, More details, Install Now"
- Select Install Now
- After a few familiar windows, you will now be on the JB recovery, and the JB rom. Ready for the adventure ahead.
Click to expand...
Click to collapse
Hi,
I'm keen to update my bootloader, and have been trying to get it done for a while now.
However, i got stuck while following your instructions... at the beginning already!
At that url you quoted, there are only UPDATE files. They won't work, tried already. Those need you to have stock rom.
Where can you get a real stock rom zip?
Thanks!
.A.
Sent from my LG-D802 using XDA Free mobile app
Hi.
I am trying to get stock jb Rom on my 511 (sorry, i know 510 is in the threat).
Cwm 6.0.4.5, jb bootloader, cm11 and rooted. Full wiped and formated.
Downloaded 4.0 from Acer, edited update.zip 1. line ond got cwm error 7 device probably encrypred.
Tried same with 4.1 from Acer and got cwm error too.
Dont know what to do now?
Could anyone provide help?
Update.............
Now i am on ics, but ota updates could not be downloaded because of unstable network. Flashing update.zip via sd ends in red android logo (tried editing 1st line) after 1/3 progress?
DAMN...
I must search a little bit under my old account (because I've forgotten sometimes the username
Pls gave a look here
http://forum.xda-developers.com/showthread.php?t=2046832
Any idea how to solve this? http://i83.photobucket.com/albums/j293/socalrailroader/IMG_20120430_012752.jpg
x4x3 said:
Sent from my LG-D802 using XDA Free mobile app
Hi.
I am trying to get stock jb Rom on my 511 (sorry, i know 510 is in the threat).
Cwm 6.0.4.5, jb bootloader, cm11 and rooted. Full wiped and formated.
Downloaded 4.0 from Acer, edited update.zip 1. line ond got cwm error 7 device probably encrypred.
Tried same with 4.1 from Acer and got cwm error too.
Dont know what to do now?
Could anyone provide help?
Update.............
Now i am on ics, but ota updates could not be downloaded because of unstable network. Flashing update.zip via sd ends in red android logo (tried editing 1st line) after 1/3 progress?
DAMN...
Click to expand...
Click to collapse
monacoo said:
Any idea how to solve this? http://i83.photobucket.com/albums/j293/socalrailroader/IMG_20120430_012752.jpg
Click to expand...
Click to collapse
Hi both of you, I know I am terribly late, but I have basically the same problem.
I wanted to go back to the latest stock version because I am selling the tablet.
Before I had all kinds of CM and then NoThrills and wanted to go completely stock.
I managed to get 4.0/ICS with all Stock options, but I couldn't find a way to upgrade to JB with any "official" method.
The standard OTA search says "Unstable network connection" and the SD card update.zip ends with the red triangle robot.
Personally the journey is at an end for me, since I don't care, it will stay on ICS.
Maybe one has to fiddle with the bootloader lock/unlock, but I am tired of it.
Sorry for not being helpful, just saying I have the exact same problem.