Guide for flashing - Motorola Atrix 2

Guys I've been seeing a lot of people having problems flashing new ROMS and having problems with using RSD and flashing the FXZ. This thread is here to guide you on a fix that will keep you up and running no matter what problems you ever encounter. This is also for the beginners who have never flashed a ROM before and are scared they may not be happy with it, this will be a way for you to get back to exactly where you were before the flash.
Lets start with the items we will need. Everythimg I'm listing I personally use everyday so they have been tried and tested by myself and many more people on here so before anyone comes on here saying this didnt work for me, let me stop you there because they all work.
YOU WILL HAVE TO BE ROOTED BEFORE ANY OF THIS WILL WORK FOR YOU. THIS IS ALL COVERED IN THE BEGINNERS GUIDE FOR BOTH 2.3.5 AND 2.3.6 SO I'M NOT GOING TO COVER IT AGAIN
ATRIX2 BOOTSTRAP
get it HERE
INSTRUCTION ON HOW TO USE
Steps to use bootstrap:
1. Install the Atrix2Bootstrap.apk
2. Select "Bootstrap Recovery"
3. Superuser will prompt for permissions
4. Select "Reboot Recovery"
When the phone reboots it will boot up into Clockworkmod Recovery.
J.Y.Daddy's BOOT INTO CWM RECOVERY ON BOOT
get it HERE
installation instructions:
1. First, CWM Recovery install.(Atrix2 Bootstrap)
2. Attachment file(RAZR-CWMOnBoot-Global-J.Y.Daddy.zip) download and copy to SDcard.
3. Boot into CWM using Atrix2 Bootstrap
4. in recovery menu: "install zip from sdcard" -> "choose zip from sdcard" -> select file.
5. After completed update, reboot.
6. After reboot, OPEN Superuser and set permissionons on Atrix2 Bootstrap to deny. (Very important)
7. reboot. (is all finished)
* After all is completed. On every reboot, you will boot into recovery. No big deal just select reboot and you will boot up normally now.
NOW GO AND GET THE REBOOT FROM THE POWER BUTTON MENU
Get it HERE
1. Boot into CWM
2. Wipe Cache
3. Wipe Dalvik Cache (under advanced)
4. Install the reboot.zip
Now that you have all of this installed corretly and have checked to make sure it is all working properly make a CWM backup NOW! It doesnt matter if you are on 2.3.5 or 2.3.6 if what you are running is working very good and you are pleased with it make a backup of it. This way if something goes wrong you always have a backup and now have access to it upon boot so you will no longer have to ever use RSD unless you totally fry your phone.
THIS WILL SPEED UP THE NANDROID PROCESS DRAMASTICALLY!! YOU DON'T HAVE TO USE THIS BUT IT SAVES A LOT OF TIME AND I LOVE IT
Go into sdcard/clockworkmod and create a file named ".hidenandroidprogress" without the parenthesis. The easiest way I have found to do this is using ES File Explorer and go into your sdcard/clockworkmod and hit the menu button and select new, then file and call it ".hidenandroidprogress " . This file wont show up until you look at your phone on your computer but its there. Im sure you can use the same process using Root explorer.
How to perform a backup
1. boot into CWM
2. select backup and restore
3. select backup and let CWM do it thing, be patient this will take a while
4. select reboot system now
That's it your done! Make a mental note of the date and what system you were on in case you have multiple backups on file.
A helpful tip, I have a folder just for all of my backups on my computer that way I dont have 5 or so backups to confuse me on my phone. Each backup has its own folder with system name and what ROM I was using.
Now that you have all of this installed and a backup go out and try some of the great ROMS we have with the confidence that if soemthing goes bad you now have a way to get back to exactly where you were before the problem started.
WHAT HAPPENS IT I HAVE A BOOTLOOP?
No big deal just pull your battery and let it boot into CWM and then perform a restore and you will be back and running in a matter of minutes!
Guys this is truly the fastest and easiest means by far that I have found. Hopefully it will help you too!!!!

I rebooted my phone and have a backup with CWM but when i use Room Tool Box Pro to install the battery icon I get alot of FC's. Then I have to use bootstrap to CWM an older backup and how do I change mt battery in RomTool Box Pro without the FC's???

thanks for the guide JRW!
One drawback of the CWM on boot is that it doesn't like it when you power off the phone then try to charge it... you'll end up in an endless reboot of CWM -> reboot -> Big M -> CWM -> reboot etc. It's not a big drawback because the A2 still charges rapidly while fully powered on.

mkrunk12 said:
I rebooted my phone and have a backup with CWM but when i use Room Tool Box Pro to install the battery icon I get alot of FC's. Then I have to use bootstrap to CWM an older backup and how do I change mt battery in RomTool Box Pro without the FC's???
Click to expand...
Click to collapse
I never use rom tool box as I found too many problems with it.

cogeary said:
thanks for the guide JRW!
One drawback of the CWM on boot is that it doesn't like it when you power off the phone then try to charge it... you'll end up in an endless reboot of CWM -> reboot -> Big M -> CWM -> reboot etc. It's not a big drawback because the A2 still charges rapidly while fully powered on.
Click to expand...
Click to collapse
My phone never gets powered off, so I've never experienced this. Phone gets drained then put kn charge till I get it off

Thank You, I'm new to this and this really helps to have it in one place!

I went through all the steps, when I flashed the REBOOT MOD and then reloaded, it is stuck in a booting loop
Please help me

I Managed to restore using Nandroid Backup to my stock 2.3.6.. Anyways thanks for that simplified procedure

Stuck in bootloop after flashing reboot.zip. And done the noob thing - no nandroid backup. Any help?
Thanks.

Thanks for the speedy nan tip. Makes backups breeze by.

This is one of the best threads on this site. Should be a stickie imo.
The End.

Problem
JRW 28 said:
Guys I've been seeing a lot of people having problems flashing new ROMS and having problems with using RSD and flashing the FXZ. This thread is here to guide you on a fix that will keep you up and running no matter what problems you ever encounter. This is also for the beginners who have never flashed a ROM before and are scared they may not be happy with it, this will be a way for you to get back to exactly where you were before the flash.
Lets start with the items we will need. Everythimg I'm listing I personally use everyday so they have been tried and tested by myself and many more people on here so before anyone comes on here saying this didnt work for me, let me stop you there because they all work.
YOU WILL HAVE TO BE ROOTED BEFORE ANY OF THIS WILL WORK FOR YOU. THIS IS ALL COVERED IN THE BEGINNERS GUIDE FOR BOTH 2.3.5 AND 2.3.6 SO I'M NOT GOING TO COVER IT AGAIN
ATRIX2 BOOTSTRAP
get it HERE
INSTRUCTION ON HOW TO USE
Steps to use bootstrap:
1. Install the Atrix2Bootstrap.apk
2. Select "Bootstrap Recovery"
3. Superuser will prompt for permissions
4. Select "Reboot Recovery"
When the phone reboots it will boot up into Clockworkmod Recovery.
J.Y.Daddy's BOOT INTO CWM RECOVERY ON BOOT
get it HERE
installation instructions:
1. First, CWM Recovery install.(Atrix2 Bootstrap)
2. Attachment file(RAZR-CWMOnBoot-Global-J.Y.Daddy.zip) download and copy to SDcard.
3. Boot into CWM using Atrix2 Bootstrap
4. in recovery menu: "install zip from sdcard" -> "choose zip from sdcard" -> select file.
5. After completed update, reboot.
6. After reboot, OPEN Superuser and set permissionons on Atrix2 Bootstrap to deny. (Very important)
7. reboot. (is all finished)
* After all is completed. On every reboot, you will boot into recovery. No big deal just select reboot and you will boot up normally now.
NOW GO AND GET THE REBOOT FROM THE POWER BUTTON MENU
Get it HERE
1. Boot into CWM
2. Wipe Cache
3. Wipe Dalvik Cache (under advanced)
4. Install the reboot.zip
Now that you have all of this installed corretly and have checked to make sure it is all working properly make a CWM backup NOW! It doesnt matter if you are on 2.3.5 or 2.3.6 if what you are running is working very good and you are pleased with it make a backup of it. This way if something goes wrong you always have a backup and now have access to it upon boot so you will no longer have to ever use RSD unless you totally fry your phone.
THIS WILL SPEED UP THE NANDROID PROCESS DRAMASTICALLY!! YOU DON'T HAVE TO USE THIS BUT IT SAVES A LOT OF TIME AND I LOVE IT
Go into sdcard/clockworkmod and create a file named ".hidenandroidprogress" without the parenthesis. The easiest way I have found to do this is using ES File Explorer and go into your sdcard/clockworkmod and hit the menu button and select new, then file and call it ".hidenandroidprogress " . This file wont show up until you look at your phone on your computer but its there. Im sure you can use the same process using Root explorer.
How to perform a backup
1. boot into CWM
2. select backup and restore
3. select backup and let CWM do it thing, be patient this will take a while
4. select reboot system now
That's it your done! Make a mental note of the date and what system you were on in case you have multiple backups on file.
A helpful tip, I have a folder just for all of my backups on my computer that way I dont have 5 or so backups to confuse me on my phone. Each backup has its own folder with system name and what ROM I was using.
Now that you have all of this installed and a backup go out and try some of the great ROMS we have with the confidence that if soemthing goes bad you now have a way to get back to exactly where you were before the problem started.
WHAT HAPPENS IT I HAVE A BOOTLOOP?
No big deal just pull your battery and let it boot into CWM and then perform a restore and you will be back and running in a matter of minutes!
Guys this is truly the fastest and easiest means by far that I have found. Hopefully it will help you too!!!!
Click to expand...
Click to collapse
Hi,
While doing below:-
NOW GO AND GET THE REBOOT FROM THE POWER BUTTON MENU
Get it HERE
1. Boot into CWM
2. Wipe Cache
3. Wipe Dalvik Cache (under advanced)
4. Install the reboot.zip
I forgotten the step 2 and 3 and my phone now kept restarting at the Motorola Logo there.
Please help!

Pull the battery. Automatically boot into cwm recovery (assuming you installed that prior). Restore your backup (assuming you did that).
The End.

@JRW does the reboot script add anything at all other than the reboot option? Does it affect lockscreen, notification screen, status bar etc. Thanks.
The End.

KEB64 said:
@JRW does the reboot script add anything at all other than the reboot option? Does it affect lockscreen, notification screen, status bar etc. Thanks.
The End.
Click to expand...
Click to collapse
Yes it adds a lot of features since one if the main items is your framework-res hpdi.

JRW 28 said:
NOW GO AND GET THE REBOOT FROM THE POWER BUTTON MENU
Get it HERE
1. Boot into CWM
2. Wipe Cache
3. Wipe Dalvik Cache (under advanced)
4. Install the reboot.zip
Click to expand...
Click to collapse
Wait... Why do you need the reboot option in power menu?? It's not necessary for CWM on Boot to run... or is it somehow? I've been using CWM on Boot on my stock odexed (obviously no reboot option) with no problems...

alteredlikeness said:
Wait... Why do you need the reboot option in power menu?? It's not necessary for CWM on Boot to run... or is it somehow? I've been using CWM on Boot on my stock odexed (obviously no reboot option) with no problems...
Click to expand...
Click to collapse
Its not necessary, just having the option to reboot was an option they could choose to have invluded and I felt it was a helpful option

JRW 28 said:
Its not necessary, just having the option to reboot was an option they could choose to have invluded and I felt it was a helpful option
Click to expand...
Click to collapse
It is a very helpful option
Also, don't know if this is worth mentioning, or even necessary, but after flashing back to 2.3.5, I always do the OTA update to 2.3.6 before any rooting or trying to restore a backup through CWM. I have a feeling that restoring a rom based on 2.3.6, doesn't go well over a 2.3.5 build. Also, is there a way to stick that 2.3.6 ota update in your system files, so you don't have to wait for the dang download everytime?
Sent from my mind using XDA

alteredlikeness said:
It is a very helpful option
Also, don't know if this is worth mentioning, or even necessary, but after flashing back to 2.3.5, I always do the OTA update to 2.3.6 before any rooting or trying to restore a backup through CWM. I have a feeling that restoring a rom based on 2.3.6, doesn't go well over a 2.3.5 build. Also, is there a way to stick that 2.3.6 ota update in your system files, so you don't have to wait for the dang download everytime?
Sent from my mind using XDA
Click to expand...
Click to collapse
That is a good question that I don't know the answer to. But I do know that everytime I'va had to flash back to 2.3.5 I've had zero problems just rooting installing A2 bootstrap and restoring my most current backup, which is on 2.3.6
ALWAYS HAVE A GOOD BACKUP ON FILE AT ALL TIMES

JRW 28 said:
That is a good question that I don't know the answer to. But I do know that everytime I'va had to flash back to 2.3.5 I've had zero problems just rooting installing A2 bootstrap and restoring my most current backup, which is on 2.3.6
ALWAYS HAVE A GOOD BACKUP ON FILE AT ALL TIMES
Click to expand...
Click to collapse
Thanks. Good to know that I don't have to go to 2.3.6 everytime before restoring.. so, that kinda nullifies my previous question...
Sent from my mind using XDA

Related

[Q] Stuck in Stock Recovery

After successfully flashing ClockWork RecoveryMod, I placed SU on the root of my SNS, powered it off, went into fastboot, but when I went into Recovery, it just went to Stock Recovery, the Exclamation Mark inside the Triangle with the Android next to it appeared, but no text or anything else is on the screen. I've let it sit for about 15 minutes, and nothing. I also can't do anything by clicking the volume buttons, or the power buttons. I've also unplugged the Phone, held the power button to try to reboot it, held volume-up and power to try to go back into fastboot, but nothing. Should I pull the battery? Why didn't it go into ClockWork RecoveryMod? Command Prompt gave me the whole " sending 'recovery' (3980 KB)... OKAY [ 0.621s]
writing 'recovery'... OKAY [ 0.511s]
finished. total time: 1.132s" thing...
What do I do? I can't just leave it sitting like this forever.
Edit: I unplugged and replugged it a few times, and it rebooted. But I've tried going back to fastboot and going into Recovery, and I get the same screen, over and over. I've even tried flashing CWRM again, and nothing. I'm using 3.0.2.4. Should I just use 3.0.0.5?
When you are in the stock recovery mode and you see the exclamation mark inside the triangle: Just hold the power button and hit volume up and you will get into stock recovery where you can perform a reboot etc.
Just try 3.0.0.5. There is something wrong with clokwork mod it you just went into stock recovery. You should be fine if you follow one of the guides on this forum.
If you still are using the stock rom. This only applies of on stock root rom because the custom rom have the edited already. You must do this. If you don't then you will have to flash clockwork ever time you reboot.
Reboot your Nexus S
Download and install Root Explorer app from Android Market
Open Root Explorer and navigate to etc directory
Tap on the gray box that says Mount R/W
Tap and hold on the file install-recovery.sh and rename this file to install-recovery.sh.old
Once renamed, download and install the app called ROM Manager from Android Market
Once installed, open ROM Manager app and choose Flash ClockworkMod Recovery option.
Hawky_ said:
When you are in the stock recovery mode and you see the exclamation mark inside the triangle: Just hold the power button and hit volume up and you will get into stock recovery where you can perform a reboot etc.
Just try 3.0.0.5. There is something wrong with clokwork mod it you just went into stock recovery. You should be fine if you follow one of the guides on this forum.
Click to expand...
Click to collapse
I tried it again with 3.0.2.5 from http://forum.xda-developers.com/showthread.php?t=988686. Did not work. Went again into Stock Recovery.
jerrycycle said:
If you still are using the stock rom. This only applies of on stock root rom because the custom rom have the edited already. You must do this. If you don't then you will have to flash clockwork ever time you reboot.
Reboot your Nexus S
Download and install Root Explorer app from Android Market
Open Root Explorer and navigate to etc directory
Tap on the gray box that says Mount R/W
Tap and hold on the file install-recovery.sh and rename this file to install-recovery.sh.old
Once renamed, download and install the app called ROM Manager from Android Market
Once installed, open ROM Manager app and choose Flash ClockworkMod Recovery option.
Click to expand...
Click to collapse
I'm a bit confused with your post.
I am still using the Stock Rom, but I don't have root access.
I've tried, after unlocking the Bootloader, going into Rom Manager and Flashing ClockWork, but it tells me first:
"You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin.su". (...)"
Then, when I still attempt to flash ClockworkMod, it tells me:
"An error occurred while attempting to run priviliged commands!"
I should have told the full story first.
I was once rooted, but it was through ROM Manager and flashing Clockwork from there. But then I had a few issues with my Wifi, and I decided to flash back Stock Rom. I still had an unlocked Bootloader though, so I thought that just redownloading Rom Manager and flashing CWRM and having Superuser installed would work. It didn't. So I attempted to root all over again, this time, manually.
But, I always go back to square one, it seems, when I try to get into Recovery.
What up with that?
After you flash CWM recovery, go straight into recovery from the fastboot menu. Do not reboot. Do not power off. Flash CWM and when it finishes immediately press volume down to select recovery and then press power to go in.
The Nexus S will overwrite CWM with stock recovery every time the phone boots by default. This could be what is giving you trouble.
Sent from my Nexus S using XDA App
matt2053 said:
After you flash CWM recovery, go straight into recovery from the fastboot menu. Do not reboot. Do not power off. Flash CWM and when it finishes immediately press volume down to select recovery and then press power to go in.
The Nexus S will overwrite CWM with stock recovery every time the phone boots by default. This could be what is giving you trouble.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Thank you so much!
That was it!
After I did that, I went straight into Recovery, flash SU, rebooted, went into ROM Manager, Flashed CWRM from there, and boom.
I don't understand why AllGamer's guide didn't already say that could happen. I'll post a comment there.
Thanks again!
EonHawk said:
Thank you so much!
That was it!
After I did that, I went straight into Recovery, flash SU, rebooted, went into ROM Manager, Flashed CWRM from there, and boom.
I don't understand why AllGamer's guide didn't already say that could happen. I'll post a comment there.
Thanks again!
Click to expand...
Click to collapse
No problem.
There is a script located in the /etc folder called install-recovery.sh. it runs every time you boot and installs stock recovery. You have two choices: always use rom manager to flash CWM every time you need to access recovery, or use root explorer to rename install-recovery.sh to install-recovery.sh.bak so that it will not run and will leave CWM installed.
Glad you got it figured out!
Sent from my Nexus S using XDA App
Or a third choice of course would be to install a custom ROM because they tend to not include that script
Sent from my Nexus S using XDA App
EonHawk said:
Thank you so much!
That was it!
After I did that, I went straight into Recovery, flash SU, rebooted, went into ROM Manager, Flashed CWRM from there, and boom.
I don't understand why AllGamer's guide didn't already say that could happen. I'll post a comment there.
Thanks again!
Click to expand...
Click to collapse
If you are talking about this guide then it does warn about this problem. I used the guide to root my nexus s and I followed all his steps, including renaming the necessary file - http://forum.xda-developers.com/showthread.php?t=895545
This is from his 2nd post - called notes:
NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
buachaille said:
If you are talking about this guide then it does warn about this problem. I used the guide to root my nexus s and I followed all his steps, including renaming the necessary file - http://forum.xda-developers.com/showthread.php?t=895545
This is from his 2nd post - called notes:
NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
Click to expand...
Click to collapse
Actually I think that guide does have two unnecessary steps that cause confusion. After flashing CWM, the guide instructs the user to power off, power on, and then to access recovery. The user should just access recovery immediately after flashing.
EDIT: I guess the problem is just that the bolded part should be added:
Then back on the SNS select Power Off (Reboot also works)
Power ON the SNS while holding volume up
buachaille said:
If you are talking about this guide then it does warn about this problem. I used the guide to root my nexus s and I followed all his steps, including renaming the necessary file - http://forum.xda-developers.com/showthread.php?t=895545
This is from his 2nd post - called notes:
NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
Click to expand...
Click to collapse
That's partly my fault, I never went down to the 2nd Post and saw those Notes, but what's the point of not including that already in the steps in the main Post? He could have just told to go straight from Recovery after flashing CWRM, but decided not to.
matt2053 said:
Actually I think that guide does have two unnecessary steps that cause confusion. After flashing CWM, the guide instructs the user to power off, power on, and then to access recovery. The user should just access recovery immediately after flashing.
EDIT: I guess the problem is just that the bolded part should be added:
Then back on the SNS select Power Off (Reboot also works)
Power ON the SNS while holding volume up
Click to expand...
Click to collapse
I think he should just have instructed to place the SU zip on the root of the SD card before flashing CWRM. That way, there wouldn't be a need to reboot to mount the SD to place SU, that way potentially losing the CWRM.

OTA EE4 Root Access Help...Please!

I am going to activate a new device today. Planning on letting OTA EE4 do its thing. Afterwards, what process should I follow to achive root?
Just do a little reading first before asking.
It's in one of the threads. I'll post which one if I come across it.
The step by step is there too.
Done PLENTY of reading before tackling this. Just lots of threads with lots of confusing steps. Just trying to consolidate this process into somewhat simple steps for the beginners. I will attempt to write out the procedure I follow tonight and post it for the beginners. Any help to get this started would be appreciated.
Yes. I have been reading too and did not see clearly how to root after OTA update
Sent from my SCH-I510 using Tapatalk
Can't Find "How to Root from Latest EE4 Update"
I have been reading and searching for the exact same thing - if it is anywhere to be found, it must be buried pretty deep.
There are two ways to root your device. Depending on what you want the end result to be, one way may be quicker than the other.
1. If you want Voodoo and Root, but don't care about custom roms or uv/oc kernels. You can simply use ODIN to flash jt1134's kernel and reboot. It should convert to voodoo on the first boot and you are done.
2. If you want CWM Recovery and the ability to flash custom roms/ kernels in .zip format w/ CWM, You can flash CWM in ODIN and then boot direct to recovery by using the Vol up + Home+ Power button combo, releasing power when samsung logo appers.
Once in CWM flash the rom and kernel of your choice(already on your SDcard) and then reboot.
3. If you want both jt1134's kernel and CWM you just use odin to flash both rebooting in between. First the kernel then CWM.
Once updated
1. Reboot into recovery
2. Wait till you're at the recovery loader
3. Take out battery, disconnect any USB
4. Boot up in loading mode (vol down, plug in USB)
5. When loading screen comes on, you can put the battery back in
6. Use Odin to load the latest CWM (http://forum.xda-developers.com/showthread.php?t=1112804)
7. It'll auto reboot and should put you back into recovery mode. You'll know you're in the right recovery if it's yellow and has the option to install zip from sdcard. If it doesn't take repeat steps 4-6 again (On my wife's phone I had to do it twice)
8. Use CWM to load PBJ's rooted kernel (http://forum.xda-developers.com/showthread.php?t=1104634)
9. reboot
Enjoy!
I too am trying to get guidance on this. I am at what I assume is stock ee4 after taking ota from rooted ed1 flash and I DID lose root.
I flashed the imnuts cwm onto phone a bit ago. It is current file updated yesterday I believe. The problem is that when I go into recovery mode via vol/home/pwr I get into what looks to be still the stock samsung recovery screen with no added options. Then lettering on screen is now blue though where I think it was different prior to flash? Leery of proceeding without some help !!
Thanx In Advance for Any Guidance !!
It has been suggested that you flash the Voodoo kernel after the ROM is installed via CWM it has worked better for many that way.
I tried flashing new cwm using method listed above in reply #7 .... after the flash completed the phone did reboot but to full reboot, it did not boot back to recovery. I shut phone down and go into recovery and it looks to be stock samsung recovery still but lettering is blue:
Android system recovery <3e>
Samsung Recovery Utils for BML
(selections list)
apply sdcard:update.zip
wipe data/Factory reset
wipe cache partition
format internal sd-card
no other options and lettering above is blue
down in screen I have yellow # Manual Mode #
looks to me like cwm flash did not take ?
Edit: Okay I got it !! I flashed again leaving battery out during whole process and now have voodoo cwm ....
On to next step *cringe*
Chopstix9 said:
I tried flashing new cwm using method listed above in reply #7 .... after the flash completed the phone did reboot but to full reboot, it did not boot back to recovery. I shut phone down and go into recovery and it looks to be stock samsung recovery still but lettering is blue:
Android system recovery <3e>
Samsung Recovery Utils for BML
(selections list)
apply sdcard:update.zip
wipe data/Factory reset
wipe cache partition
format internal sd-card
no other options and lettering above is blue
down in screen I have yellow # Manual Mode #
looks to me like cwm flash did not take ?
Click to expand...
Click to collapse
You have to force the phone to recovery mode after flash, by pressing vol up+home+power, releasing power after samsung logo appears. If the phone boots up w/ the stock kernel, cwm is overwritten by stock recovery.
hoppermi said:
You have to force the phone to recovery mode after flash, by pressing vol up+home+power, releasing power after samsung logo appears. If the phone boots up w/ the stock kernel, cwm is overwritten by stock recovery.
Click to expand...
Click to collapse
I flashed again and I am at the CWM Voodoo Lagfix Recovery v 4.0.0.1
I have transfered the imnuts debloated ee4 to the sdcard
I use menu up/down to navigate to selections. After going down to the apply update from sdcard I press the home key to select. It just jumps back up to reboot system now. This happens no matter what selection I attempt to activate using the home key ...
I know I am close, what am I missing here ?
Thanks Tons For The Help
hoppermi said:
There are two ways to root your device. Depending on what you want the end result to be, one way may be quicker than the other.
1. If you want Voodoo and Root, but don't care about custom roms or uv/oc kernels. You can simply use ODIN to flash jt1134's kernel and reboot. It should convert to voodoo on the first boot and you are done.
2. If you want CWM Recovery and the ability to flash custom roms/ kernels in .zip format w/ CWM, You can flash CWM in ODIN and then boot direct to recovery by using the Vol up + Home+ Power button combo, releasing power when samsung logo appers.
Once in CWM flash the rom and kernel of your choice(already on your SDcard) and then reboot.
3. If you want both jt1134's kernel and CWM you just use odin to flash both rebooting in between. First the kernel then CWM.
Click to expand...
Click to collapse
Thanks, I am in same boat, so many threads it is mind boggling.
I see that jt1134's kernel include the voodoo lag fix? What if I just want root. Really all I want it root so I can do some mild de-bloating, but want the phone in a position that if another OTA comes out I can just accept it without worrying.
Thanks!
Chopstix9 said:
I flashed again and I am at the CWM Voodoo Lagfix Recovery v 4.0.0.1
I have transfered the imnuts debloated ee4 to the sdcard
I use menu up/down to navigate to selections. After going down to the apply update from sdcard I press the home key to select. It just jumps back up to reboot system now. This happens no matter what selection I attempt to activate using the home key ...
I know I am close, what am I missing here ?
Thanks Tons For The Help
Click to expand...
Click to collapse
Choose the install zip from sdcard option, then navigate to where debloated rom is and select
Sent from my SCH-I510 using Tapatalk
addictedtocars said:
Thanks, I am in same boat, so many threads it is mind boggling.
I see that jt1134's kernel include the voodoo lag fix? What if I just want root. Really all I want it root so I can do some mild de-bloating, but want the phone in a position that if another OTA comes out I can just accept it without worrying.
Thanks!
Click to expand...
Click to collapse
Sounds like you just want a stock rooted kernel you can flash w / odin. Put in a request in and maybe one of the devs can accommodate you.
For now, I only know of jt's kernel for odin.
Sent from my SCH-I510 using Tapatalk
I'm curious if we will ever see a one click root app for this phone like gingerbreak? What will it take to make it that easy? I have gingerbreak for my tablet(honeycomb 3.0) and it's a snap to switch back and forth.
I only want root to be able to edit some files (starup sounds) and for titanium backup. AND I want to be able to get the OTA updates without having to remeber all the hoops I have to jump through.
I'd gladly pay for a simple root solution for this phone.
I got mine rooted and after many screwups I stumbled onto a 3 step process that was easy as pie. Read my post in this forum 'How I Got to EE4 Root' ....

[Q] Trying to go back to stock ROM, I now do not have a recovery

All I get now is the android with the yellow explanation. I know the step I missed..
I am trying the one in this thread
http://forum.xda-developers.com/showthread.php?t=1154947
1. Download repacked stock rom, stock recovery and stock firmware 3.1 update:
Repacked stock rom:http://dl.project-voodoo.org/transformer-roms/3.0.x/
Stock recovery:http://forum.xda-developers.com/atta...2&d=1306284085
http://usa.asus.com/Eee/Eee_Pad/Eee_...F101/#download
2. Copy the files onto your micro sd. Unzip stock update and place the Asus folder on root of sd card.
3. Boot into recovery. install repacked stock rom. Wipe all data, cache partition and dalvik cache. Reboot the tablet let it boot up then shut it down.
4. Boot into recovery and install stock recovery. Wipe all data, cache partition and dalvik cache. And then reboot and shut down.
5.
a.Boot into OS, there should be a notification for an update. select it and follow instuctions. Or
b.Boot into recovery(it should be stock recovery) then press up volume button within five seconds and the official update should install.
6. It should reboot automatically. When it does check about tablet info and check your apps to make sure the Super User icon is gone.
I forgot to install the stock recovery and immediately went to the next step. So my TF will boot now but I have no recovery to go too..
How do I get the recovery back?
acdcking12345 said:
All I get now is the android with the yellow explanation. I know the step I missed..
I am trying the one in this thread
http://forum.xda-developers.com/showthread.php?t=1154947
1. Download repacked stock rom, stock recovery and stock firmware 3.1 update:
Repacked stock rom:http://dl.project-voodoo.org/transformer-roms/3.0.x/
Stock recovery:http://forum.xda-developers.com/atta...2&d=1306284085
http://usa.asus.com/Eee/Eee_Pad/Eee_...F101/#download
2. Copy the files onto your micro sd. Unzip stock update and place the Asus folder on root of sd card.
3. Boot into recovery. install repacked stock rom. Wipe all data, cache partition and dalvik cache. Reboot the tablet let it boot up then shut it down.
4. Boot into recovery and install stock recovery. Wipe all data, cache partition and dalvik cache. And then reboot and shut down.
5.
a.Boot into OS, there should be a notification for an update. select it and follow instuctions. Or
b.Boot into recovery(it should be stock recovery) then press up volume button within five seconds and the official update should install.
6. It should reboot automatically. When it does check about tablet info and check your apps to make sure the Super User icon is gone.
I forgot to install the stock recovery and immediately went to the next step. So my TF will boot now but I have no recovery to go too..
How do I get the recovery back?
Click to expand...
Click to collapse
Get yourself the nvflash tool (You just have too look for it in Transformer Q&A Section) unzip it, install the drivers, if You haven't yet, get a nvflashable version of a rom (PRIME Rom has got an nvflash version) unzip the nvflash Rom to the nvflash tool, so recovery.img system.img and so on are in the same folder as download.bat and so on.
finally enter in APX mode on your transformer, and run download.bat.
when it's done, your tablet should restart.
Sent from my Asus tf101 running official Ice Cream Sandwich.
The android with yellow exclamation point is your stock recovery.
Try taking the "update" file out of the Asus folder and put it directly on the root of your sd card.
If that still don't work do the two file method.
well, I did the download.bat. But I turned it off when it just showed two lines.
Now it wont turn on at all..I am really screwing this up.
It just wont turn on at all..But it has a full charge. I knew I should have left it alone
acdcking12345 said:
well, I did the download.bat. But I turned it off when it just showed two lines.
Now it wont turn on at all..I am really screwing this up.
It just wont turn on at all..But it has a full charge. I knew I should have left it alone
Click to expand...
Click to collapse
What's the serial # of your TF?
baseballfanz said:
What's the serial # of your TF?
Click to expand...
Click to collapse
It starts with a B60
It now says entering NVS Flash recovery mode. Nothing else
acdcking12345 said:
It starts with a B60
Click to expand...
Click to collapse
Use NVFlash unbricking method
http://www.tabletroms.com/forums/tr...stock-3-2-recovery-roms-unbricking-tools.html
acdcking12345 said:
well, I did the download.bat. But I turned it off when it just showed two lines.
Now it wont turn on at all..I am really screwing this up.
It just wont turn on at all..But it has a full charge. I knew I should have left it alone
Click to expand...
Click to collapse
You should not have turned it off. When the installation process was done, your tablet should start up by itself.
Try it again, but this time wait for the tablet to start up.
I redid it and followed it exactly as outlined.
It is now installing the stock update. I think I am ok now.
I appreciate all the help..

Skyrocket ICS-leak flash problem

Well, I've been trying to work my way through this one, but I'm unable to find an answer. I tried to flash the UCLD2 firmware ICS leak on my SR and it didn't work, and now the phone goes on an endless boot loop. My phone was rooted with stock ROM (Gingerbread 2.3.6) and I had clockworkmod installed. I did a full back up with Titanium Backup as well. I saw a page in android authority detailing how to flash it using clockwork mod and followed the clockworkmod method:
Flashing via ClockworkMod Recovery
NOTE: You will be needing a rooted Samsung Galaxy S2 Skyrocket with ClockworkMod Recovery (CWM) installed. Check out our guide on how to root your Samsung Galaxy S2 skyrocket. You can also refer to this guide on how to root your phone running Android 4.0.3 UCALC4 firmware. For ClockworkMod Recovery, check this guide on how to flash ClockworkMod Touch Recovery to your phone.
Download the following to your computer:
Download the CWM-flashable UCLD2 package from here (skyrocket-ucld2-ics-leak.zip, md5sum: 5cb721bcacdadf7de2b0b9f041acc114).
Download the root fix file from here (su-bin-3.0.3.2-efghi-signed.zip, 164 kB).
Download the Facebook and Samsung keyboard fix here (UCLD2FontHotfix.zip, 226 kB).
Copy the skyrocket-ucld2-ics-leak.zip, su-bin-3.0.3.2-efghi-signed.zip, and UCLD2FontHotfix.zip to the root of your phone’s SD card.
Switch off your mobile phone.
Reboot your phone into ClockworkMod Recovery. To do that, press the Volume Up key, Volume Down key, and Power button simultaneously until Recovery Mode boots. NOTE: Once in Recovery Mode, use the Volume keys to navigate and Power button to select an option.
Perform a full wipe by doing the following:
Go to Wipe Data/Factory Reset and confirm the action on the next screen.
Select Wipe Cache Partition and confirm the action on the next screen.
From the main menu, select Advanced. From there, select Wipe Dalvik Cache and confirm the action on the next screen.
Go to Mounts and Storage and select Format /system on the next screen. Select Yes on the next screen to begin formatting your system.
Go back to the main menu and select Install ZIP from SD Card. Select Choose ZIP from SD Card and highlight the skyrocket-ucld2-ics-leak.zip. Confirm the action on the next screen to begin flashing the ZIP file to your phone.
Repeat step 6 but this time flash su-bin-3.0.3.2-efghi-signed.zip to your phone. You will meet an error message after flashing this file. Just ignore the error message.
NOTE: Ignore the error after flashing this file. Just go to Superuser and make an update after booting your phone.
Flash the UCLD2FontHotfix.zip file in the same manner as in step 6.
After installing the 3 files, go back to the main menu and select Advanced. From there, select Fix Permissions.
Go back to the main menu and select Reboot system now to restart your mobile phone.
Once your phone has rebooted into Normal Mode, launch the Superuser app and update the su binaries.
Congratulations! You have successfully updated your Samsung Galaxy S2 Skyrocket SGH-I727 to the leaked Android 4.0 Ice Cream Sandwich firmware UCLD2.
I did everything detailed in the clockworkmod method, was very careful and checked everything multiple times. Once I did those steps when I tried to reboot the system it goes on an endless boot loop. Sometimes it gets to the splash screen, sometimes it doesn't. No error messages are displayed, it just keeps booting. I am able to access clockworkmod, but I'm not sure what to do at this point. I've re-downloaded the three files listed in the article and I've redone all the steps, with the same results (obviously...). Not sure what my next step is at this point. Any help would be greatly appreciated.
Use a 1 click release...
Hello.
Your solution:
Put the phone into Download mode, and install the leak from the original 1 click odin release by DesignGears.
How to do it?
1st, search in the forums the location of the firmware, be sure to use the 1 click release, there are 3 leaks, for me the second was the best, probably for you the 3rd will be better, use one of those 2.
Be sure to have all drivers for your phone installed, and be sure Kies wont start when you connect the phone.
Power the phone off, by removing the battery.
Press, Vol up and Down at the same time, while keeping them pressed, connect the USB cable, then, run the 1 click binary.... wait some minutes while it says it is done and enjoy!!!!
Hope it helps, if any problems arise, let us know. I will check the thread later today and tomorrow.
Thank you! Working on it right now. I'll update you on how it goes.
Hope it ends fine for you!
Worked like a charm! Not sure why it didn't work the other way. Regardless, thank you so very much.
Nice!!!
Nice!!!!!!!!!!!!!!!!!!!!

[Q] I think I may have unlocked my bootloader twice...

I tried to use the search and google but didn't really find anything helpful. Almost 2 years ago, I unlocked the bootloader back on honeycomb and did custom recovery, root, and custom rom. Then a little while after ICS came out, I did the OTA update.
Today, I reset the xoom back to stock ICS and tried to unlock the bootloader again...thinking nothing of it. The process was taking a few minutes so I decided to get a snack and when I came back it was rebooting.
I assumed that it worked and continued to try and fastboot a recovery image. The recovery image installed and I did another reboot but was greeted with the android welcome screen. Anyways I went through the menus and then tried to enter recovery and it gave me an android laying on its back with and exclamation point above his open chest.
I hard rebooted and can still get into my device, but adb cannot seem to find my xoom anymore. I have tried it on a 64bit desktop and laptop with no luck.
Have I messed up? Or is there a simple fix that I am missing? Thanks in advance for any help!
Can you get into fastboot mode? The second time you unlocked did you have to go through the questions on your xoom again?
dfib1 said:
Can you get into fastboot mode? The second time you unlocked did you have to go through the questions on your xoom again?
Click to expand...
Click to collapse
Yes, I can get into fastboot by holding the volume down key and the power button. That's fastboot, right?
Yes, I had to go through the menus the second time I unlocked.
sounds like the recovery you try to fastboot did not take or the rom was corrupt.. Which recovery was it? Do you want to be rooted and run a custom rom or completely stock? what xoom do you have(wifi, 3g, 4g)
dfib1 said:
sounds like the recovery you try to fastboot did not take or the rom was corrupt.. Which recovery was it? Do you want to be rooted and run a custom rom or completely stock? what xoom do you have(wifi, 3g, 4g)
Click to expand...
Click to collapse
I want to flash this ROM
http://forum.xda-developers.com/showthread.php?t=1997434
With whichever recovery is best. I tried flashing this recovery:
http://forum.xda-developers.com/showthread.php?t=1074979
I am on a 4G xoom on 4.0.4 but I don't use my data plan. I would like to be on a nice stable build of 4.2.
Download your rom choice, gapps and put them on the root of your sd card. If they are already there skip this step
I like TWRP Recovery the best. Easy to use and lots of options.
download this Twrp 2.4 img to the folder you hve fastboot in
open a cmd prompt in that o that folder
type fastboot flash recovery TWRPv2.4.1.0.img
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
You should be in twrp 2.4
select backup/restore and backup your current system
select install and find your rom select asnd then swipe to flash
when done then select home
select install again and find the gapps package and install
when done select wipe dalvick/cache
when done select reboot
select system
you should be good to go.
Well I got through all of the steps, but when I try to boot I get stuck in a loop of the roms boot logo. Is it okay to flash a wingray rom over a stingray device?
dfib1 said:
Download your rom choice, gapps and put them on the root of your sd card. If they are already there skip this step
I like TWRP Recovery the best. Easy to use and lots of options.
download this Twrp 2.4 img to the folder you hve fastboot in
open a cmd prompt in that o that folder
type fastboot flash recovery TWRPv2.4.1.0.img
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
You should be in twrp 2.4
select backup/restore and backup your current system
select install and find your rom select asnd then swipe to flash
when done then select home
select install again and find the gapps package and install
when done select wipe dalvick/cache
when done select reboot
select system
you should be good to go.
Click to expand...
Click to collapse
Well I got through all of the steps, but when I try to boot I get stuck in a loop of the roms boot logo. Is it okay to flash a wingray rom over a stingray device?
I think it is fine just the 3g/4g won't work.
I can get you going again but you are going to be starting with a locked honeycomb device. You will then have to either let it update to ICS or JB or unlock, root, install custom recovery and flash a rom. What xoom do you have 3g or 4g?
dfib1 said:
Download your rom choice, gapps and put them on the root of your sd card. If they are already there skip this step
I like TWRP Recovery the best. Easy to use and lots of options.
download this Twrp 2.4 img to the folder you hve fastboot in
open a cmd prompt in that o that folder
type fastboot flash recovery TWRPv2.4.1.0.img
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
You should be in twrp 2.4
select backup/restore and backup your current system
select install and find your rom select asnd then swipe to flash
when done then select home
select install again and find the gapps package and install
when done select wipe dalvick/cache
when done select reboot
select system
you should be good to go.
Click to expand...
Click to collapse
Okay I restored it again but this time i did a factory reset and wipe dalvick before flashing the rom and gapps. It works! Thank you for your help!
However, could I ask how to root this thing?
since you have a custom recovery on it already and are unlocked.
Download this file Universal xoom root place it on the root of your sd card and flash it. Then reboot and try a root required app such as root checker
dfib1 said:
since you have a custom recovery on it already and are unlocked.
Download this file Universal xoom root place it on the root of your sd card and flash it. Then reboot and try a root required app such as root checker
Click to expand...
Click to collapse
Thanks! Got it!
g;lad to hear it.

Categories

Resources