Database Users

[Question] how to unroot/restore

Hello,
I recently bought a nexus one from Craigslist. I thought it hadn't been tampered with but it turns out that it is rooted. I read you can tell its rooted when theres an open lock underneath the nexus sign when loading it. I don't know how he rooted but its preventing me from updating to the pinch and zoom capabilities. Always get (status 7) error. So I want to unroot the phone, update it then perhaps later root it. Is there a way I can unroot it with a Mac?
Thanks for the help!
Extra info about my phone (if it makes a difference)
Firmware version
2.1
Baseband version
32.19.00.16U_4.02.02.14
Kernel version
2.6.29-gad36b87
[email protected] #1
Build Number
ERD79

It's rooted without an unlocked bootloader? I doubt that, or maybe you have the only one in existence.
You can always just flash this:
http://www.mediafire.com/file/hy2yj42my3i/gapps-passion-ERE36B-2-signed.zip
in recovery and you'll get the multitouch update.

mortzz said:
It's rooted without an unlocked bootloader? I doubt that, or maybe you have the only one in existence.
You can always just flash this:
http://www.mediafire.com/file/hy2yj42my3i/gapps-passion-ERE36B-2-signed.zip
in recovery and you'll get the multitouch update.
Click to expand...
Click to collapse
Dude did you not read his first post? It has an OPEN lock. There is a way you can get the update. Man

Extra info about my phone (if it makes a difference)
Firmware version
2.1
Baseband version
32.19.00.16U_4.02.02.14
Kernel version
2.6.29-gad36b87
[email protected] #1
Build Number
ERD79

change your thread title. Its seriously misleading....[HOW TO] is for threads TEACHING how and not for questions or requests.

shonanthebarbarianTP2 said:
Dude did you not read his first post? It has an OPEN lock. There is a way you can get the update. Man
Click to expand...
Click to collapse
How do I update it then? I have always gotten (status 7) error. Better yet how do I unroot it? Any ideas?

As of right now, theres no way to unroot a phone. But if I were you, id consider upgrading it to CyanogenMod (search in nexus one development for it) that enables the multi-touch capabilities.

Its not possible
The best you could do is this, http://forum.xda-developers.com/showthread.php?t=614850
But anyway, why unroot, a rooted phone is much better
How about you look around the site and see wah u can actually do with your phone now

Just look for modaco's 1.7 , download it. Put your phone into recovery by powering down then hold volume down, down while holding that down press n hold power button. A white screen should come up. Leave it be until the green lettering disappears. Then press volume down to navigate to "recovery". Once in recovery use trackball to navigate to USB toggle . Click on it via trackball. Now plug ur phone into your comp via micro USB cable. Go to "my computer" on ur comp. Double click removable disk to open ur SD card. Delete everything from ur SD. Go to where u saved modacos 1.7 drag it to your empty SD card. Now click ur track ball to disable USB connection. Unplug your phone. Go to wipe. Click on it with ur track ball. Now click wipe data. Let it do its thing. Then wipe dalvik cache. Let it do its thing. After that push volume down to get back to ur menu. Go to flash update. Click on it and click on the zip you just put on ur Sd card. Let it do its thing and you're done.

1. Download a ROM of your choice, and then load it on to your SD card in the root directory.
2. Shut the phone off.
3. Hold down the volume down button, and hit + hold the power button at the same time.
4. Continue holding until the phone boots up
5. Scroll down to recovery by hitting the volume down button once.
6. Press the power button once.
7. Scroll down with the scrollball to Wipe
8. Wipe device/factory reset
9. Wipe cache
10. Click the volume down again
11. Scroll to Flash update/zip
12. Scroll to the ROM you downloaded and loaded to your zip, and then click
13. Click the trackball again to accept.
Now, you really just have to make sure the ROM you downloaded has the pinch to zoom, which most have. I don't believe you'll lose root, but you should at least gain the features you're looking for.

Your Nexus One is unlocked, not rooted. There is difference.

Thanks everyone for the help! I ended up needing to install the Amon RA recovery image and then installed the MoDaCo ROM. Works good but I read that Cyanogen is better with better features. I think I will now install the Cyanogen ROM. Not sure what he means by updating the radio if needed though. My radio is RADIO-4.02.02.14
If anyone knows if this is ok then I would appreciate it, I will try to research and see if it's ok too.
Thanks again!

Remember to do a nandroid backup in case you either screws something up or you wish to go back to your previous Rom (saves time and headache).

As far as i know updating the radio is optional, you just download it, nandroid backup, update like a rom, and reboot, IMPORTANT ON REBOOT IT WILL GO TO A LOADING SCREEN WHERE IT UPDATES THE RADIO DO NOT TOUCH ANYTHING OR PULL BATTERY OR YOU MAY BRICK YOUR PHONE-FOR REAL. With that said after the radio loads it will take you back to recovery, then nandroid again if you want(never hurts), wipe and flash cyanogens rom then the gapps add on and then reboot and youre good to go.

I just download all the files but I noticed that the radio is a .img file
Not sure how I can install it... any suggestions?

[Q] A few beginner Questions

Hello everyone,
my Name is Fabi and I'm fairly new to Android. My previous Phone had Symbian...
My current phone is of course the HTC Legend...
... it has 2.1 stock on it
... Baseband Version 47.26.35.04U_7.05.35.26L
... Kernel Version 2.6.29-e3993620 [\n] [email protected] #1
... Build Number 1.31.405.5 CL154058 release-keys
... Software Number 1.31.405.5
... Browser Version WebKit 3.1
... it is NOT rooted.
I read a lot in the last few weeks here and know a lot more about Android "Development".
But there are still a few open Questions
If i root a device, it's loosing its warranty. But if i unroot it (like in the new available Guide) again, can they still notice that it has been rooted before?
Do i have to reset/wipe all my Phones data if i unroot my device?
Is there something like BarryAllen so I can switch between roms (I think there is something like that called Rom Manager - but i'm not sure)
Can i receive FOTA's again after i went to the stock Image again (to use the stock FroYo as soon as it is out)
Does the FM Radio work again after i went back to the stock Image again?
Can i create a RomDump of my phone, so i can flash it back whenever i want?
Where can I find a description of Clockwork Mod (what does it do, and how and how to use it,...)
Thank you for reading (and answering) those stupid n00b questions.
I hope you understood my English
Fabi
Edit: I figured out that RUU means Rom Upgrade Utility, but what does WWE mean?

fabi280 said:
If i root a device, it's loosing its warranty. But if i unroot it (like in the new available Guide) again, can they still notice that it has been rooted before?
Click to expand...
Click to collapse
No
fabi280 said:
Do i have to reset/wipe all my Phones data if i unroot my device?
Click to expand...
Click to collapse
Yes
fabi280 said:
Is there something like BarryAllen so I can switch between roms (I think there is something like that called Rom Manager - but i'm not sure)
Click to expand...
Click to collapse
Be sure, you'll be right more often than you think. ROM Manager is indeed the app for managing ROMs.
fabi280 said:
Can i receive FOTA's again after i went to the stock Image again (to use the stock FroYo as soon as it is out)
Click to expand...
Click to collapse
In theory, yes. Some people seem to have difficulty with this though. Not sure why
fabi280 said:
Does the FM Radio work again after i went back to the stock Image again?
Click to expand...
Click to collapse
Yes
fabi280 said:
Can i create a RomDump of my phone, so i can flash it back whenever i want?
Click to expand...
Click to collapse
Yes, it's called a nandroid backup. You need to be rooted to make and restore from them
fabi280 said:
Where can I find a description of Clockwork Mod (what does it do, and how and how to use it,...)
Click to expand...
Click to collapse
Right here:
It's an alternative recovery image, and gives you lots of options: creating/restoring backups, flashing new ROMs (it works with ROM manager to make this easy), wiping anything you like and, of course, flashing all the other MODs you're gonna want to mess around with.
How to use it:
Well, if your phone boots properly you can just tap "Reboot into recovery" from ROM manager (also use ROM manager to install clockworkMOD). If your phone doesn't start properly (boot loop) you can still get to it. To quote myself:
Press and hold the volume down button while you press the power button. You'll get to a white screen with little Android dudes at the bottom. Ain't they sweet, riding their little skateboards. Anyhoo, what you see now is the bootloader, the pesky little thing that made rooting so hard. Within this area of your phone you need to use the volume buttons to move up and down in the menu, and the power button to select. So, wait for the list of files to appear and disappear again, click on the "RECOVERY" menu, and wait until you get to the infamous "red-exclamation-mark-in-a-red-warning-triangle-on-top-of-a-picture-of-a-phone-that-looks-nothing-like-the-one-you're-holding-and-just-screams-danger-at-you" screen. When you see this, ignore your instict and don't run for the hills. Just press and hold the volume up key while you press the power button. Ignore the error, and wait until you see a blue menu. Using the volume and power buttons navigate to, and click, "apply sdcard:update.zip"
Wait for it...
Wait for it...
BOOM! ClockworkMOD recovery. We're back in business! In these menus you need to use the optical trackball that HTC so kindly provided us, and click on "nandroid".
What's that? Your screen went black? Didn't I just tell you to use the optical trackpad? Use that for clicking too. Kicking youself now, aren't you?
Click to expand...
Click to collapse
I think that covers it. Have fun!

Thank You very much.
Cyanogen Mod is great

fabi280 said:
...Edit: I figured out that RUU means Rom Upgrade Utility, but what does WWE mean?
Click to expand...
Click to collapse
World War Three (replace the E with an 3)...joking. World Wide English is the meaning and it's just saying that the ROM in question is "universal" having English as default language (I hope I've explained correct). You should always want to use a WWE ROM, if you don't want to end up having a localized ROM installed on your phone (Chinese sounds good? )

[joke]
You just said World War 3 because I'm a German - thats unfair... It was the fault of Austrians, in both cases.
[/joke]
Okay, thank you for all your answers.

[GUIDE 25/02/2012]UK ONLY /Orange/ T-mobile – ROOTING, UNLOCKING BOOTLOADER

I have updated this guide as I have a new replacement from t-mobile. This guide was based on my previous atrix which was running froyo (2.2.2) This time I have applied OTA 45.21.2.Mb860.T-mobile.en.gb and everything works perfect so if you have updated your phone to 2.3.4 then you can use this guide as well
I have decided to create this thread as I have seen many people confused about the difference between At&t phones and their UK ones. This thread will help you make the decision whether you want to hack your phone or not. I own T-mobile UK Atrix and whatever I have done worked perfectly for me. I’m not responsible for any bricks. You doing this on your own risk – good news is that no one (UK) had their mobile bricked. ALL CREDITS GOES TO DEVELOPERS AND OTHERS THAT CREATED SIMILAR THREATS – THANKS
ROOTING – If you running froyo (2.2.2) I have used gingerbreak method which is very easy:
Code:
1. Download Gingerbreak.exe from here: [url]http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1046626&v=1&libid=1311795059566&out=http%3A%2F%2Fbandbinnovations.com%2Fxda%2FGingerBreak.exe&ref=http%3A%2F%2Fforum.xda-developers.com%2Fforumdisplay.php%3Ff%3D997%26order%3Ddesc%26page%3D4&title=%5BHOWTO%5D%20Easy%20Root%201.5.7%20%26%201.83%20using%20GingerBreak%20-%20xda-developers&txt=http%3A%2F%2Fbandbinnovations.com%2Fxda%2FGingerBreak.exe[/url]
2. Make sure you have got debugging mode ON(settingsApplications Development) and you have installed drivers for your atrix
3. Run Gingerbreak.exe on your pc
4. In your phone you will find new app called gingerbreak – run it and select root. Mobile will reboot itself once is done.
5. Congratulation you are rooted.
NOTICE: You need to have External SD Card and also be aware that rooting this way will format your internal storage.
ROOTING – If you running gingerbread (2.3.4) use superoneclick (http://forum.xda-developers.com/showthread.php?t=803682) and fallow the instructions on the original thread. Very easy way.
If you want to try ANY Custom ROM you need to Unlock your Bootloader:
Code:
1. You need to download and install RDS lite on your PC: [url]http://forum.xda-developers.com/attachment.php?attachmentid=634879&d=1308872277[/url]
2. Download and extract IHOP_Bell.rar: [url]http://diamantephoto.com/IHOP_Bell.rar[/url]
3. Download and extract Fastboot tools [url]http://gititbit.ch/FAST[/url]
4. Power down your Motorola Atrix
5. Take out your microSD card and SIM card for the flashing process
6. While turning the phone on, hold the Volume Up button until it acknowledges RSD
7. Your device will say “Starting RSD protocol support”
8. Run “RSD Lite” on your computer
9. Press the “. . .” button next to the box labeled “Filename”
10. Load up the SBF file – IHOP_Bell.sbf
11. Plug your device into your computer
12. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…”
13. Press the “Start” button
14. Be patient while the phone reboots. It will take a long time.
15. Open and extract the Fastboot package from above
16. Open a command prompt window
a. On Windows, press Start and type “cmd” then press the enter button
17. Type the following command. Your directory will be the folder where you extracted the Fastboot package.
(Example: cd C:\Users\Kenneth\Desktop\fastboot-package)
a. cd your directory here
18. Power down your Atrix device
19. Hold the power button and the downward volume button until you see “Fastboot”
20. Let go of the buttons and press the upward volume button once
21. You will now see “Starting Fastboot protocol support”
22. Plug your device into a USB port in the back slot of your computer
a. Front slots sometimes do not have enough power to stay connected to the device.
23. Type the following command:
a. fastboot oem unlock
24. You will now receive a warning along with a unique device ID
25. Type the following commands using your unique device ID in place of the ####:
a. fastboot oem unlock ####
b. fastboot reboot
26. Wait for your device to reboot. Congratulations! You now have an unlocked bootloader!
I recommend to install romracer's Recovery : http://forum.xda-developers.com/showthread.php?t=1204500.
Instalation:
Code:
$ fastboot devices
TA20700KXH fastboot
$ fastboot erase recovery
erasing 'recovery'... OKAY [ 0.741s]
$ fastboot flash recovery recovery.img
sending 'recovery' (4780 KB)... OKAY [ 0.490s]
writing 'recovery'... OKAY [ 0.544s]
The reason I recommend this recovery is because the official clockwork recovery doesn't support external sdcard (bug?). If this doesn't bother you then you can download Rom manager from market and install official recovery.
Most of the roms have unified kernel which means you don't need to apply anything after installation. This includes roms like aura, the dark side, cyanogen mod.
However if you do have issues with memory then download kernel from this thread: http://forum.xda-developers.com/showthread.php?t=1156040

Thanks for this - thats my night sorted

Very useful and thorough guide. Thanks a lot Mr Foka. I left you a "thanks" btw.

thank you so much! just going to unlock my orange atrix
Sent from my MB860 using XDA Premium App

Jibraldor said:
Very useful and thorough guide. Thanks a lot Mr Foka. I left you a "thanks" btw.
Click to expand...
Click to collapse
That's very kind. Thanks

Hi there,
sorry, a quick question regards to the custom ROMS, you mentioned if I am going to apply the AT&T ROMs, I need to apply custom kernels,
Foka002 said:
You can now install ANY Custom ROM. However if you want to install ROM That is designed for AT&T you will have to apply FIXED Kernel for international (faux’s or eveal kernels working excellent for our devices - http://forum.xda-developers.com/showthread.php?t=1169409 or http://forum.xda-developers.com/showthread.php?t=1156040)
Click to expand...
Click to collapse
but in eval-'s thread, he mentioned:
I suspect these boot.img will 'fix' RAM for unlocked internationals on any Gingerbread 2.3.x build (only), but this as faux123 helpfully points out, your modules must match (important for wifi, vpn) ! So for now, these boot.img with quick & dirty RAM fix are only for this Orange FR 2.3.4 system.img!! (Unless you want to copy around dhd.ko and parts of /system/lib/hw between /systems...)
Click to expand...
Click to collapse
So can I just apply his kernel on the AT&T firmware?
Cheers,

Well I tried eval kernel few times and long time ago. For every rom I had it I used faux kernel so it's safer to use it with recent roms.
Sent from Motorola Atrix

Hi thanks for the time and effort but I was hoping someone could help me.Trying to follow the guide but having trouble with two parts.Firstly when running pudding through rsd how long exactly do you leave it?It says to leave it at android lockscreen but rsd dhows as not finished like 38% rebooting at this time/Also when to connect or disconnect is confusing as I read a guide previously to yours am not sure if phone gets disconnected after rsd?Lastly and I think my most serious problem is that I cant get the fastboot command to work.It will either say unable to find the path specified or no command on internal or external etc.Any ideas?Thanks

Great guide! Thanks for putting this together.

So correct me if im wrong but I can follow this guide, and put on gingerbread on my orange ATRIX and it will work fine?!?!?!?
Also once the official update hits UK can I just install that?
Great work btw
Sent from my MB860 using XDA App

Just to ask / add
There is going to be an official Orange OTA update isnt there? I could do it this way but for a change want to try it the offical way

scotty7910 said:
Hi thanks for the time and effort but I was hoping someone could help me.Trying to follow the guide but having trouble with two parts.Firstly when running pudding through rsd how long exactly do you leave it?It says to leave it at android lockscreen but rsd dhows as not finished like 38% rebooting at this time/Also when to connect or disconnect is confusing as I read a guide previously to yours am not sure if phone gets disconnected after rsd?Lastly and I think my most serious problem is that I cant get the fastboot command to work.It will either say unable to find the path specified or no command on internal or external etc.Any ideas?Thanks
Click to expand...
Click to collapse
In order to use fastboot you need to have motorola drivers installed. Im not sure about eds but if your device is recognised then it is fine. Im not sure about waiting time in rsd but if you did fallow this guide step by step you shouldn't have any problems.
Roberts56
Yes you will be able to flash gingerbread but you won't be able to use official OTA unless you downgrade to 2.2.2 using fruitcake method. The thing is if you want to play with custom roms then there is no point in waiting for official release because its not going to be any better than any rom we've got now. Just keep in mind once you unlock your bootloader you will lose warranty.
Uk OTA is coming for sure but I have no idea when. Rumours says in sep/oct

Boot screen
Hi
After flashing IHOP_BELL, everytime I reboot I get a menu instead of Motorola Logo at beginning. Is that normal?? When I leave it there it will boot Android and will show the Motorola Logo.
It looks like this:
http://2.bp.blogspot.com/-dPOywn12xbg/Th6albF5xPI/AAAAAAAAAGw/BStIYOa7B_A/s1600/11.JPG
Thanks for your help

R3wt3d said:
Hi
After flashing IHOP_BELL, everytime I reboot I get a menu instead of Motorola Logo at beginning. Is that normal?? When I leave it there it will boot Android and will show the Motorola Logo.
It looks like this:
http://2.bp.blogspot.com/-dPOywn12xbg/Th6albF5xPI/AAAAAAAAAGw/BStIYOa7B_A/s1600/11.JPG
Thanks for your help
Click to expand...
Click to collapse
Strange...I've never seen this before. Can anyone tell why is that ?

hmm it's not normal then?
Any idea if I could overwrite with IHOP_BELL again downloaded freshly from xda?
I downloaded it from here.
http://diamantephoto.com/IHOP_Bell.rar
thanks

R3wt3d said:
hmm it's not normal then?
Any idea if I could overwrite with IHOP_BELL again downloaded freshly from xda?
I downloaded it from here.
http://diamantephoto.com/IHOP_Bell.rar
thanks
Click to expand...
Click to collapse
Notice of on your photo it says that your phone is unlocked! Is that right?
Did you flash a recovery? Romracer's I hear is good at the moment.
Then did you flash a rom? As says no OS DETECTED!
Can recommend http://forum.xda-developers.com/showthread.php?t=1169409
But you can use fruitcake s
Swyped from "Mount" Olympus

nitrox1 said:
Notice of on your photo it says that your phone is unlocked! Is that right?
Did you flash a recovery? Romracer's I hear is good at the moment.
Then did you flash a rom? As says no OS DETECTED!
Can recommend http://forum.xda-developers.com/showthread.php?t=1169409
But you can use fruitcake s
Swyped from "Mount" Olympus
Click to expand...
Click to collapse
yeah it's unlocked. and after that menu I flashed ORFR boot system webtop
U guys never seen that menu? I got it right after flashing sbf...well during sbf flashing.

R3wt3d said:
yeah it's unlocked. and after that menu I flashed ORFR boot system webtop
U guys never seen that menu? I got it right after flashing sbf...well during sbf flashing.
Click to expand...
Click to collapse
Did you flash the rom with it too, as webtop is a separate part?
Never seen that menu, but never tried to boot just after ihop either though, as has no rom as party of it, check out size of the file, and size of a normal sbf.
Swyped from "Mount" Olympus

I think this is soft brick...Is this UK atrix ??

Noob questions
Do I need to root before I flash this ROM? Because I don't have an SD card I'm a bit confused if I can do this or not. Once flashed to Orange France 2.3.4, if the OTA comes through what should I do? Accept? Decline? I'm very doubtful that Motocrap will update us to ICS, so can we update to ICS manually if I flash right now? Finally, if I do Brick, what can I do? I don't have insurance. Can I backup to a PC? I want something that no matter what happens I can restore to. Thanks for the answers ( if I get any )
Kartik

Iconia A500 SOD fix (at least for me)

I've been dealing with SOD (Sleep Of Death) problem since official OTA ICS update. On HC everything (except calendar) was fine, but after official ICS update I was having SOD almost every sleep longer then few minutes.
Tried WiFi/sync tricks etc.
What helped ? Well..
1. hardware reset (Vol+ / Pwr / RotateLock)
2. factory reset (from Settings Menu)
3. full update via sd card (Vol- / Pwr)
OFFICIAL ROM: 7.014.16 - 041.213.01 - COM_GEN1 (ICS)
(Acer_A500_7.014.16_041.213.01_COM_GEN1_1336732099520_45282ff4.zip)
and once again:
4. hardware reset (Vol+ / Pwr / RotateLock)
5. factory reset (from Settings Menu)
...I know that hardware & facory reset are pretty much the same, but...It helped...

mayekk said:
I've been dealing with SOD (Sleep Of Death) problem since official OTA ICS update. On HC everything (except calendar) was fine, but after official ICS update I was having SOD almost every sleep longer then few minutes.
Tried WiFi/sync tricks etc.
What helped ? Well..
1. hardware reset (Vol+ / Pwr / RotateLock)
2. factory reset (from Settings Menu)
3. full update via sd card (Vol- / Pwr)
OFFICIAL ROM: 7.014.16 - 041.213.01 - COM_GEN1 (ICS)
(Acer_A500_7.014.16_041.213.01_COM_GEN1_1336732099520_45282ff4.zip)
and once again:
4. hardware reset (Vol+ / Pwr / RotateLock)
5. factory reset (from Settings Menu)
...I know that hardware & facory reset are pretty much the same, but...It helped...
Click to expand...
Click to collapse
Does t means I have to re-install all applications?

cscs3 said:
Does t means I have to re-install all applications?
Click to expand...
Click to collapse
yes, but you can use titanium backup or similar app to do it for you...

I have a A501 and want to get rid of this sod problem. so i took the last "Ice Cream Sandwich 4.0.3 (LEAK)" Rom from http://forum.xda-developers.com/showthread.php?t=1816560 and tried to install the update.zip file from the sd card. When i get to the recovery it starts but crashes after a few seconds. Do i habe to install a different recovery or unlock my bootloader? I'm a little bit confused...can somebody give me a short hint? Thx.

captainn said:
I have a A501 and want to get rid of this sod problem. so i took the last "Ice Cream Sandwich 4.0.3 (LEAK)" Rom from http://forum.xda-developers.com/showthread.php?t=1816560 and tried to install the update.zip file from the sd card. When i get to the recovery it starts but crashes after a few seconds. Do i habe to install a different recovery or unlock my bootloader? I'm a little bit confused...can somebody give me a short hint? Thx.
Click to expand...
Click to collapse
This is probably because of a couple of reasons.
1. You didn't do the incremental update. The available update files are incremental patch files, which means you have to have the others installed before you install the latest. Or at least part 1 and 2 of the original leak.
2. You didn't decrypt the file and remove the "update.zip". Generally, you can't just rename these update files to "update.zip". So the latest OTA you took, you should decrypt it "if it needs it", open in 7zip or Winzip and pull the update.zip file and copy that to your EXT SD card.
The final Official release build, was build .021. So if you still get SOD on .021, then chances are you have one of the later revision tablets, and may have to wait a long time until Acer releases another update, as the later revisions only account for a very small percentage.
Or, you can install the unlocked bootloader, and try one of the newer kernels we have.
MD

Moscow Desire said:
This is probably because of a couple of reasons.
1. You didn't do the incremental update. The available update files are incremental patch files, which means you have to have the others installed before you install the latest. Or at least part 1 and 2 of the original leak.
2. You didn't decrypt the file and remove the "update.zip". Generally, you can't just rename these update files to "update.zip". So the latest OTA you took, you should decrypt it "if it needs it", open in 7zip or Winzip and pull the update.zip file and copy that to your EXT SD card.
The final Official release build, was build .021. So if you still get SOD on .021, then chances are you have one of the later revision tablets, and may have to wait a long time until Acer releases another update, as the later revisions only account for a very small percentage.
Or, you can install the unlocked bootloader, and try one of the newer kernels we have.
MD
Click to expand...
Click to collapse
Thanks for your replay. So what i did was to install all available OTA updates. Then i downloaded the full package Ice Cream Sandwich 4.0.3 (LEAK) from the site above, extracted the update.zip from this archive and put it on the external sd card. i think that is all i have to do. And my current build number is Acer_AV041_A501_1.021.00_EMEA_DE...so don't know exactly if "[LEAK]Acer A501 ICS (COM_GEN1). Build number 041.126.01" is the same version.
And i tried to unlock my bootloader but the next funny thing is that i tried that Afterota-Tool, but it stucks at 3/4 "Flashing recovery...".
I don't want to loose my 3G-Feature and i saw that nearly all roms are only for A500. Which kernel and rom would you recommend for me?
Looking forward for your replay. Thx a lot!

captainn said:
Thanks for your replay. So what i did was to install all available OTA updates. Then i downloaded the full package Ice Cream Sandwich 4.0.3 (LEAK) from the site above, extracted the update.zip from this archive and put it on the external sd card. i think that is all i have to do. And my current build number is Acer_AV041_A501_1.021.00_EMEA_DE...so don't know exactly if "[LEAK]Acer A501 ICS (COM_GEN1). Build number 041.126.01" is the same version.
And i tried to unlock my bootloader but the next funny thing is that i tried that Afterota-Tool, but it stucks at 3/4 "Flashing recovery...".
I don't want to loose my 3G-Feature and i saw that nearly all roms are only for A500. Which kernel and rom would you recommend for me?
Looking forward for your replay. Thx a lot!
Click to expand...
Click to collapse
You current build is cooked my friend. Unless you want Acer repair.
Most of all OTA ICS Updates are Com Gen 1 now. Not sure what acer had in mind. But I believe it has duetch or danish language.
You have to use a 501 update if you want to use 3g and GPS.
My question, were you successful in booting to your system after installing the updates correctly? That is my primary question. If so, make sure you have USB debugging turned on.
But I need to know exactly what your tablet is in now before going further. Does it boot into the OS after running the updates?
MD

Moscow Desire said:
You current build is cooked my friend. Unless you want Acer repair.
Most of all OTA ICS Updates are Com Gen 1 now. Not sure what acer had in mind. But I believe it has duetch or danish language.
You have to use a 501 update if you want to use 3g and GPS.
My question, were you successful in booting to your system after installing the updates correctly? That is my primary question. If so, make sure you have USB debugging turned on.
But I need to know exactly what your tablet is in now before going further. Does it boot into the OS after running the updates?
MD
Click to expand...
Click to collapse
I don't know exactly which updates you are talking about. I installed all the available ota updates and the tablet booted correctly after this. If you mean any other update via sd-card i can only tell you that i was not able to install one of them. what do you mean with "cooked"? sorry for stupid questions
My USB debugging ist turned on, firewall and uac off.
Thx.

captainn said:
I don't know exactly which updates you are talking about. I installed all the available ota updates and the tablet booted correctly after this. If you mean any other update via sd-card i can only tell you that i was not able to install one of them. what do you mean with "cooked"? sorry for stupid questions
My USB debugging ist turned on, firewall and uac off.
Thx.
Click to expand...
Click to collapse
The only stupid question, is the one that doesn't get asked
What is the current version you are on? (settings/about tablet) The current build should be .021
MD

Moscow Desire said:
The only stupid question, is the one that doesn't get asked
What is the current version you are on? (settings/about tablet) The current build should be .021
MD
Click to expand...
Click to collapse
Android 4.0.3
Kernel 2.6.39.4+
Image Acer_AV041_A501_RV20RC05_EMEA
Build Acer_AV041_A501_1.021.00_EMEA_DE
P/N FM.S14A0.02A
Is it all you need?

captainn said:
Android 4.0.3
Kernel 2.6.39.4+
Image Acer_AV041_A501_RV20RC05_EMEA
Build Acer_AV041_A501_1.021.00_EMEA_DE
P/N FM.S14A0.02A
Is it all you need?
Click to expand...
Click to collapse
Yes, you have build .021 But I am surprised it's not WW_Com_Gen_1
This is the latest Acer build. So stay with it.
Ok, info for you, I am currently working with kernel dev's to maybe get something better as far as kernels, that may help with your SOD if you still have it.
For right now, let us work on things. This may take a few days.
As with Unlocked Bootloader and CWM recovery.
Here is what you should do.
GET YOUR UID NUMBER and write it down.
1. Make sure your Acer drivers are installed.
2. Using After OTA, only install the Patched Bootloader.
3. If you already have the patched bootloader installed (you see Skirlax_CZ bootloader text when you boot),
Did it install the patched bootloader?
MD

Moscow Desire said:
Yes, you have build .021 But I am surprised it's not WW_Com_Gen_1
This is the latest Acer build. So stay with it.
Ok, info for you, I am currently working with kernel dev's to maybe get something better as far as kernels, that may help with your SOD if you still have it.
For right now, let us work on things. This may take a few days.
As with Unlocked Bootloader and CWM recovery.
Here is what you should do.
GET YOUR UID NUMBER and write it down.
1. Make sure your Acer drivers are installed.
2. Using After OTA, only install the Patched Bootloader.
3. If you already have the patched bootloader installed (you see Skirlax_CZ bootloader text when you boot),
Did it install the patched bootloader?
MD
Click to expand...
Click to collapse
So in Afterota i open the tab advanced and there i can choose "browse for custom bootloader" and i can choose between different binary files. I think "bl_ics_ac_v8.bin" or "bl_ics_pb_v8.bin" should be right. What's the difference, what's the right one?

captainn said:
So in Afterota i open the tab advanced and there i can choose "browse for custom bootloader" and i can choose between different binary files. I think "bl_ics_ac_v8.bin" or "bl_ics_pb_v8.bin" should be right. What's the difference, what's the right one?
Click to expand...
Click to collapse
Well, I did things the old fashioned way.
If I am to guess. the first one is CWM recovery included, and the second is Public Recovery included. I never used this tool
I would choose door number 1
BTW, there are other methods to install these things. But let's see what happens. Personally, I don't use these all in 1 tools. Got too many of them in the forums. But, let's see what happens.
If not successful, we'll use My method. And you will learn something in the process.
MD

Moscow Desire said:
Well, I did things the old fashioned way.
If I am to guess. the first one is CWM recovery included, and the second is Public Recovery included. I never used this tool
I would choose door number 1
BTW, there are other methods to install these things. But let's see what happens. Personally, I don't use these all in 1 tools. Got too many of them in the forums. But, let's see what happens.
If not successful, we'll use My method. And you will learn something in the process.
MD
Click to expand...
Click to collapse
*LOL* Tool doesn't work at all...so i will do it by using another method...can you recommend one that really works= :fingers-crossed:

captainn said:
*LOL* Tool doesn't work at all...so i will do it by using another method...can you recommend one that really works= :fingers-crossed:
Click to expand...
Click to collapse
Ehhhh,,, we're gonna do it my way now.
Ok, keep in mind, it's late in Moscow, and I have a baby that will need bath (long process) and other family duties.
Let's get your computer prepared the way it should always be when dealing with the dark side of android.
Your tab is running now, and that's good. You have a .021 build. Ok. But let;s see if we can make it better.
First thing, and I hope you have Windows XP or Windows 7.
Download and install the Android SDK.
http://developer.android.com/sdk/index.html
Now, next, is the Oracle Java Platform (JDK)
http://www.oracle.com/technetwork/java/javase/downloads/index.html
After you do these 2 things, well, we can move over to the dark side.
Now, after everything is installed, I want you to do something.
Connect your tab with USB debugging on. (Never turn this off)
Open Windows explorer, go to C:\program file (x86)\Android\Android-sdk\platform tools . Open a command window here (SHIFT & Right mouse click)
Then type adb devices in the CMD window. Should show device connected and some numbers.
This tells me the drivers are installed.
If not, You have to install Acer USB drivers from the website.
Then try again.
And that, is as far as I go tonight, too late.
Tomorrow, I will give you a lesson in NVFlash and fastboot.
Rule number 1. Drivers, Drivers, Drivers. This was just to prepare your system.
To save some time, for tomorrow, shut down your tab.
Using a paper clip, or needle or something. Press and hold the pin hole button near the USB port. Hold it. Then, press and hold PWR button. Wait 4 seconds, release PWR only. 1 second later, release the pin hole.
Tab should be black. PWR button white. You may get vibrate.
This is what we call APX mode.
When you connect your tab to your PC, after a few seconds, the PC should recognize this as (Recovery Mode, APX Mode, or Download Mode)
Will need to know what it says. If it says nothing, but gives you an error in Windows device manager, then Houston, we have a problem. And the problem is the drivers. And you need to fix it. You may have to manually select from a list or tell it where the drivers are.
And that is all for tonight Mate. Baby needs bath.
MD

Thank you very much. I installed the bootloader, the recovery and the tegraowner ics rom for the A501. It looks great and it seems that SOD is now part of the history 3G is also working. Great success :laugh:
Thanks for your help and to all developers!

captainn said:
Thank you very much. I installed the bootloader, the recovery and the tegraowner ics rom for the A501. It looks great and it seems that SOD is now part of the history 3G is also working. Great success :laugh:
Thanks for your help and to all developers!
Click to expand...
Click to collapse
Great! Was waiting to hear!
Not that I demand it, but, it's customary to hit the "thanks" button for those that help
Always remember, you have a "fastboot" bootloader, so if something happens, you can boot to the Fastboot, and do things like install boot.img's (kernels), Custom Recoveries, and some other things. That's why you installed Android SDK. Also, you have ADB capability as well.
Rock On!
MD

Moscow Desire said:
Great! Was waiting to hear!
Not that I demand it, but, it's customary to hit the "thanks" button for those that help
Always remember, you have a "fastboot" bootloader, so if something happens, you can boot to the Fastboot, and do things like install boot.img's (kernels), Custom Recoveries, and some other things. That's why you installed Android SDK. Also, you have ADB capability as well.
Rock On!
MD
Click to expand...
Click to collapse
In addition: Now i am using "ICS Evil Alex Unleashed Ver 2". I switched because gps is not working when using tegraowners rom. Now it seems, that all important features are working! Thanks a lot for your rom!

I have the official A500 ICS, didn't do anything other than the OTA upgrade, and it worked fine until I installed some additional apps, it started to do the SOD. Then I uninstalled the latest apps I added, more likely instagram, and the SOD went away, till now at least. So, if you can't get it to work, maybe a factory reset to clear out all the apps might help, then, add apps slowly to see find out which one actually act bad.

Moscow Desire said:
Ehhhh,,, we're gonna do it my way now.
Ok, keep in mind, it's late in Moscow, and I have a baby that will need bath (long process) and other family duties.
Let's get your computer prepared the way it should always be when dealing with the dark side of android.
Your tab is running now, and that's good. You have a .021 build. Ok. But let;s see if we can make it better.
First thing, and I hope you have Windows XP or Windows 7.
Download and install the Android SDK.
http://developer.android.com/sdk/index.html
Now, next, is the Oracle Java Platform (JDK)
http://www.oracle.com/technetwork/java/javase/downloads/index.html
After you do these 2 things, well, we can move over to the dark side.
Now, after everything is installed, I want you to do something.
Connect your tab with USB debugging on. (Never turn this off)
Open Windows explorer, go to C:\program file (x86)\Android\Android-sdk\platform tools . Open a command window here (SHIFT & Right mouse click)
Then type adb devices in the CMD window. Should show device connected and some numbers.
This tells me the drivers are installed.
If not, You have to install Acer USB drivers from the website.
Then try again.
And that, is as far as I go tonight, too late.
Tomorrow, I will give you a lesson in NVFlash and fastboot.
Rule number 1. Drivers, Drivers, Drivers. This was just to prepare your system.
To save some time, for tomorrow, shut down your tab.
Using a paper clip, or needle or something. Press and hold the pin hole button near the USB port. Hold it. Then, press and hold PWR button. Wait 4 seconds, release PWR only. 1 second later, release the pin hole.
Tab should be black. PWR button white. You may get vibrate.
This is what we call APX mode.
When you connect your tab to your PC, after a few seconds, the PC should recognize this as (Recovery Mode, APX Mode, or Download Mode)
Will need to know what it says. If it says nothing, but gives you an error in Windows device manager, then Houston, we have a problem. And the problem is the drivers. And you need to fix it. You may have to manually select from a list or tell it where the drivers are.
And that is all for tonight Mate. Baby needs bath.
MD
Click to expand...
Click to collapse
Great tutorial!
I have a500 with ota ICS. Rooted. Locked bootloader. And working fine, but I think it could be better..
I am used to flashing rom and kernel on my android phone, but it looks like it is a bit more difficult on this device..
If I want to try another rom, should I follow your tutorial first? Or what do I do?
Oh, and what rom do you recommend? - I need fast, reliable and everything working.. Nothing fancy is required
Sent from my A500 using xda app-developers app

[Guide][CDMA R800x] FXP CM7 to CM9 upgrade. (As of FXP 125)

Hi everybody! I'm Dr...
Nah nm. Anyways well the past 2 days I have been working on switching from FXP CM7 to CM9. Needless to say, the process was abit confusing and did run across some snags along the way. So now that I figured it out with some help. I am returning the favor to the community and putting up this guide. (Also this guide is for users who already have an unlocked bootloader and so. So if you are a new R800x user who JUST unlocked their bootloader using testpoint or so, you too can use this guide)
Keep in mind this guide is based on the changes and tweaks from FXP 125!
So for those who are using a R800x CDMA Xperia play, this is for you.
-= The Prep =-
1: You will need the Flashtool to flash the latest ftf from Verizon. agraceful was nice enough to put it on his cloud storage here. http://www.mediafire.com/?yas7dola6dgd8 (You may wanna disable your AV for this as Kaspersky for me, didnt like the file since it uses exploits to do the stuff to your phone) if the cloud storage is down, this is the thread for the flashtool. http://forum.xda-developers.com/showthread.php?t=1351299
2: The latest Verizon ftf file here. http://forum.xda-developers.com/showthread.php?t=1696233
3: The latest FXP CM9 (remember its zeusc that you are downloading for!) AND the gapps for ICS! (Very important you use the right gapps here), http://forum.xda-developers.com/showthread.php?t=1447542
*OPTIONAL* 4: Mjolnir Kernel (boot.img) - http://forum.xda-developers.com/showthread.php?t=1708459 (Rename that img file to boot.img) (This is a diff kernel which may have some different features and abilities compared to fxp 125, so take a look and choose, atm it has zRam support (compcache) )
*OPTIONAL* 5: Cdma Carrier Name Fix - https://dl.dropbox.com/u/21955004/Carrier Fix.zip (This can either let you use a custom carrier name or least fix it from saying T-Cdma 64)
6: Of course, fastboot, drivers, and drivers for the flashtool which come with flashtool for flash drivers. (Not covered in this guide, cause if you already have CM7 on CDMA.. I am assuming you already have an unlocked bootloader, drivers etc already installed)
Now once you have everything. Time to do some EXTRA note prep work:
1: Make note of your MDN/MSID numbers. (The phone number and 2nd set of number incase you need to manually program your phone if OTA programming doesnt work)
2: Titanium Backup of your apps/data
3: Put the CM9 zip, cdma mega fix, and gapps ics into the memory card root folder. You will need this here to flash in a bit.
4: Kiss your phone bye bye and tell it you love it and that it will be back online soon if you dont mess it up!
Now you are ready to get started!
-= The Upgrade Install Process! =-
1: Turn your phone off, hold the back button and plug in the usb, You should be in the flash mode. Load up flashtool. (Your PC will install the drivers now if it needs to or the flashtool will error and tell you where the drivers are located to install and run its exe file to install)
2: With drivers ready, phone ready, you can drag the verizon ftf file to the main screen of flashtool. It should start up, give you some notes, tell you what you need to do if needed and just start flashing. Wait till its done fully, then you can close out of it, reboot your phone, if it boots up to Verizon screen setup, you have done the job correctly! Grats!
3: Unplug USB, Turn off phone, hold the search button, then plug in the usb again. You will see a blue light on the power button to tell you that you are fastboot mode.
4: Make sure the boot.img (Either the boot.img from FXP 125 zip file or the downloaded one) is in the same folder as your fastboot command! From cmd prompt, be in the directory of your fastboot and type fastboot -i 0xfce flash boot boot.img this should be a quick process and will put the new kernel you need with its cwm recovery built in needed for CM9. After thats done, type fastboot -i 0xfce reboot
5: During the reboot phase, LOOK at the power button. The MOMENT you see it light up "blue" hold the back button. This will load you into CWM where you can get started!
6: Now you SHOULD have your files on your SD card ready to be flashed! If you dont and you forgot. Just go to "mount" and mount the usb storage and then put your files on the sd card. (Silly person forgetting! Remember, its the cm9 zip, cdma fix, and the gapps ics)
7: Now flash the fxp 125 cm9 zip. Will take a min or 2. Once that is done. Do the 4x wipe. Wipe/Factory reset, Wipe Cache, Then goto Advanced, Wipe Devlik, Wipe Battery Stats.
8: Now flash gapps ics
9: (Optional) Flash the Cdma Carrier name fix.
10: Reboot into your phone.
If you see the cool transwarp sliders style android logo. Go WOOT!
-= The Inital Setup =-
Now that you are staring at the new android setup wizard here are my "personal" tips
1: From the setup wizard. I just did the basic, and SKIPPED the sign in part. Get your wifi running once inside if you want. Then load up "Play Market" and sign into google from there.
Why did I do this? Well.. I did it the other way 1st time signed in during the setup process.. and well.. I left the option "Restore phone from google" enabled.. yea.. not smart, next I know its installing EVERY app I had from Google. (Which I guess it was basing it on the google history or using my G1s installed stuff to restore from) By doing it the way above, it doesnt try to start restoring everything. Which is good.
2: Now to program your phone number and so again. Now I did this using pageplus, which is still verizon. For me, the OTA to get my number back in was *228 send. Wait wait wait, and it should program and be done with. Alt numbers are *22890 and *22891 which some update the roaming towers or just an alt form of OTA. Now if none of that works, then do the manual programming.
3: In the market, get titanium backup (and your pro key) and install.
4: The rest you should be able to do yourself as far as restoring goes using titanium backup.
Congrats you are now running ICS CM9 FXP!
Hope this guide helps people who maybe confused and would like a lil thread with something to look over to help them get it going. =)

Reserved..For..Stuff..

-=Tweaks=-
V6 Supercharger - http://forum.xda-developers.com/showthread.php?t=991276 (This is being used to help increase performance of CM9 on our xperia as well as some games that started sluggishing up after the change to ICS)
Volume+ - https://play.google.com/store/apps/details?id=com.TEST.android.lvh&hl=en Well worth the money.. otherwise my emulators sounded too quiet lol. Not to mention Youtube. Now at work, I use Speaker setting 8.

Hey,
You can make the update, as of FXP125 you don't need a separate kernel to get CWM. It's baked in again. Volume keys get you into it.

Mogul345 said:
Hey,
You can make the update, as of FXP125 you don't need a separate kernel to get CWM. It's baked in again. Volume keys get you into it.
Click to expand...
Click to collapse
Done. I left it optional for now. =) Also the only thing I need to confirm on is if we need that cdma mega fix file still... I forgot my XP at home.. (Go figure) so I wont be able to test the update out till tm. Heh.

Mysticales said:
Done. I left it optional for now. =) Also the only thing I need to confirm on is if we need that cdma mega fix file still... I forgot my XP at home.. (Go figure) so I wont be able to test the update out till tm. Heh.
Click to expand...
Click to collapse
I did not have to flash the megafix. All I did was the following (w/ FXP125):
1)Use flashtool to flash new baseband from 2.3.4 FTF (when selecting what to flash, I excluded everything but baseband).
2)Use fastboot to flash the FXP125 kernel.
3)Booted into CWM, wiped data/cache/dalvik cache/battery stats, then flashed FXP125 and the 4/29 Gapps.
Only thing I think needs flashed is the carrier name fix. My phone says T-CDMA 64 again.

Ok thanks. Yea, according to lightningdude the only things in the cdma mega fix was just the gamepad fix (dont know what that is yet) and the cdma carrier name. Gonna try to see about those. While its minor, still good info to have.
Also its being said that we should use V6 Supercharger on the CM9 to improve some games again for XP users.

Ok thanks to lightningdude, I put the cdma carrier name fix in the guide. =)

Mysticales said:
Ok thanks. Yea, according to lightningdude the only things in the cdma mega fix was just the gamepad fix (dont know what that is yet) and the cdma carrier name. Gonna try to see about those. While its minor, still good info to have.
Click to expand...
Click to collapse
Ahh OK. That gamepad fix is the patch to the .idc file changing the button map so circle isn't back in some games.
Sounds like the megafix is just all the preferred patches that were applied to paxChristos' CDMA builds.

Yea, just made life easier. Also I excluded the gamepad fix as thats a personal pref.. cause BUTTON_B vs BACK_ALT mapping can break some apps which devs code for one or the other. Normally everyone is using BACK_ALT. Then emulators which can remap it all anyways works fine with it.
Edit: Ok just updated to 125 myself without the CDMA carrier name thing. My Pageplus comes up as Verizon Wireless, so not sure if the patch was needed, but still its in guide as optional, case you want a custom name or you do get that t-cdma 64 issue.

Mogul345 said:
Hey,
You can make the update, as of FXP125 you don't need a separate kernel to get CWM. It's baked in again. Volume keys get you into it.
Click to expand...
Click to collapse
are you saying that steps 3-5 of the install process is not required since its baked in? Sorry, just getting into the more advanced rooting/customization with the r800x. I'm going to unlock the bootloader (put this off for way to long but with the latest "No ICS from Sony/Verizon" i'm just going to move ahead with my own upgrades, then ftf the verizon 2.3.4, and then hopefully be getting ICS.

blkwhk said:
are you saying that steps 3-5 of the install process is not required since its baked in? Sorry, just getting into the more advanced rooting/customization with the r800x. I'm going to unlock the bootloader (put this off for way to long but with the latest "No ICS from Sony/Verizon" i'm just going to move ahead with my own upgrades, then ftf the verizon 2.3.4, and then hopefully be getting ICS.
Click to expand...
Click to collapse
Looks like the original instructions have been updated. You should follow the instructions as directed in the OP. Steps 3-5 currently are where you flash the boot.img (kernel) you wish to use. It's either FXP's (which would be extracted from the ROM .zip), or Moljnir's or the other one listed. All three have working Clockworkmod recoveries now. At the time these instructions were originally written the recovery in FXP's kernel was busted, the next FXP build fixed it, and that's when I wrote the post you're referring to.