Related
i have had problems with Rom manager not flashing recovery correct leaving me with no recovery. so i had to manually flash recovery following these steps exact. I have personally bricked 2 ERIS phones lucky me.The first i thoought it was just something i did, lucky i had another to replace it...(the second BRICK eris).
So here is a solution to keep from having a BRICK
USE Amon RA's Recovery PERIOD.
credit to northmendo @droidforums
1. download flash_image Here Updated Link 3/17/10
2. Open the terminal and copy and paste the following commands.
adb shell [hit enter]
su [hit enter]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system [hit enter]
3. In a new terminal window (don't close the original one).
adb push flash_image /system/bin [hit enter]
exit [hit enter]
4. Now in the original terminal window
chmod 755 /system/bin/flash_image [hit enter]
5. Now exit all termainl windows and reboot your phone.
6. Download
Amon_RA's recovery Here.
7. Mount your phones sd card and drop recovery-RA-eris-v1.6.2.img on to it and eject
your phone.
8. Open the Terminal and copy and paste the following commands with the phone connected
to your computer.
8. adb shell [hit enter]
9. su [hit enter]
10. flash_image recovery /sdcard/recovery-RA-eris-v1.6.2.img
11. To get into recovery turn off you phone and hold the Volume Up + Power until it boots into recovery.
That's it.
ROM Manager and Clockwork recovery does not work for the Eris.
ROM Manager and Clockwork recovery does not work for the Eris (as far as I know).
Edit: Oops, sorry for the double post.
I currently have the clockwork recovery installed on my eris, can I just download amon's recovery image and install it to switch to it? Or do I have to uninstall clockwork recovery and then install amon's?
trishuhh said:
I currently have the clockwork recovery installed on my eris, can I just download amon's recovery image and install it to switch to it? Or do I have to uninstall clockwork recovery and then install amon's?
Click to expand...
Click to collapse
try to flash it from rom manager,(under other recoveries) if Rom manager has worked for you with no problems. if it doesnt work follow instructions as listed in 1st post
I wouldn't use clockwork recovery, it messed up my installation to the point i couldn't flash any rom or restore any nand. When i would try to flash anything it would fail, It failed when i tried to use the root rom....After I tried flashing root rom i had a nice looking brick on my desk....(I even changed back to RA but Clockwork had messed up my phone so bad that RA didn't even work either....
YOU HAVE BEEN WARNED!!!!!
Yeah, use Amon's. It does every job you need, and is 100% stable and reliable.
t2noob said:
I wouldn't use clockwork recovery, it messed up my installation to the point i couldn't flash any rom or restore any nand. When i would try to flash anything it would fail, It failed when i tried to use the root rom....After I tried flashing root rom i had a nice looking brick on my desk....(I even changed back to RA but Clockwork had messed up my phone so bad that RA didn't even work either....
YOU HAVE BEEN WARNED!!!!!
Click to expand...
Click to collapse
yea you beat me too it, , i only used it because i had it for my DROID and thought maybe devs would try to add it to the list on rom manager.
ok, obviously a bit of an amateur here, how do you know which recovery image you have, i installed amon's, but i'm not sure if clockwork made it to my phone somehow, thinking about unrooting soon, that's why i ask, thanks.
jrhoades858 said:
ok, obviously a bit of an amateur here, how do you know which recovery image you have, i installed amon's, but i'm not sure if clockwork made it to my phone somehow, thinking about unrooting soon, that's why i ask, thanks.
Click to expand...
Click to collapse
reboot into recovery and read the bottom
Ok Please help a newbie out here im losing my mind. I downloaded flash, plugged phone into mac and set phone to debugging and mounted. Opened terminal from utilities on Mac. When I enter adb shell it says "command not found" if I try using ./ before adb as suggested on another forum for macs when i enter su it asks for password? Any how please help a brother out. Thanks
I flashed amons ras recovery from my phone it was easier for me I didn't use rom manger or terminal emulater
Sent from my FroyoEris using XDA App
Can someone help me get rid of clockwork recovery it showed up after I flashed a rom. How do you flash Amons recovery?
tkryan said:
Can someone help me get rid of clockwork recovery it showed up after I flashed a rom. How do you flash Amons recovery?
Click to expand...
Click to collapse
You do exactly what the first post says
Sent from my Eris
ufccowboyfan said:
Ok Please help a newbie out here im losing my mind. I downloaded flash, plugged phone into mac and set phone to debugging and mounted. Opened terminal from utilities on Mac. When I enter adb shell it says "command not found" if I try using ./ before adb as suggested on another forum for macs when i enter su it asks for password? Any how please help a brother out. Thanks
Click to expand...
Click to collapse
When you are doing this, are you in the correct directory? For example, my SDK is installed in /android , so first I would:
cd /android/tools
then
./adb shell
could someone help me with this. i really need to get the stock recovery image on my eris and im alittle noobie at this stuff. if any one could help id be sooooo happy
I'm not sure how to flash amons on a mac. I know for windows you put the recovery.img in the sdk tools folder, boot into fastboot and type
Fastboot flash recovery recovery.img
To get stock recovery (I assume you want your phone back to stock) then flash the official ruu. Will return your phone to 100% stock. You can find it on a sticky in the Eris general forums I believe.
Sent from my Eris using XDA App
I'm not sure on a mac, but on Windows you put the img in the tools folder of your sdk, boot into fastboot and type in adb:
Fastboot flash recovery recovery.img
To get stock recovery back, simply flash the official ruu found on a sticky in the Eris general forums I believe. Flashing the ruu will unroot your phone.
Sent from my Eris using XDA App
I installed Amon Ra as part of the root for leakers instructions some time ago. -- Is there a new version out? (Search was surprisingly not helpful) And what is the best way to update recovery?
Slugdoc said:
I installed Amon Ra as part of the root for leakers instructions some time ago. -- Is there a new version out? (Search was surprisingly not helpful) And what is the best way to update recovery?
Click to expand...
Click to collapse
There is no new version out; the first version (v1.6.2) is the only one that Amon_RA published.
IF there was a new version, you could flash it by using adb with the existing Amon_RA. You don't even need to push a version of "flash_image" to the phone, because it is already in /sbin in Amon_RA recovery. Just get the recovery image to your SD card, start an interactive shell (adb shell), and then
flash_image recovery /sdcard/<wherever-you-put-it>/recovery-RA-eris-v1.6.2.img
Yes, you can "flash a recovery partition by using the recovery" - because when you are interacting with it (the recovery boot), it lives entirely in a ramdisk.
The second easiest way is to have the engineering bootloader (1.49.2000 S-OFF) installed on your phone, and flash it with fastboot from the PC, as in
fastboot flash recovery recovery-RA-eris-v1.6.2.img
Note that neither of these two methods perform any integrity checks on the recovery image file that the normal "Flash .zip from sdcard" ROM installation method does. Therefore, it is imperative that someone using these methods is extremely diligent in cross-checking image MD5 signatures after it has been transferred to the SD card. Amon_RA also has the "md5sum" utility built into it's shell, BTW.
I mention this last point as a warning to newbs - they seem to routinely corrupt files when they transfer them to the SD card. (I suppose they are not using the "safely remove hardware" controls correctly, or they are getting truncated downloads).
bftb0
I rooted my thunderbolt. After flashing clockwork mod, I downloaded the rom of my choosing. Then when booting to recovery to flash the rom, I get kicked to the bootloader. Help!??!?
Ps: It seems its that clockwork mod wont take even though rom manager says flashed sucessfuly
EDIT: I did some more investigation and after redoing this
"Step 5
Next, enter the following commands:
adb shell
/data/local/psneuter
To unlock eMMC:
adb shell
/data/local/wpthis
exit
Step 6
Please pay attention – this is very important. This step involves a small chance of bricking if you mess up.
To push the eng bootloader:
adb push hbooteng.nb0 /data/local/
adb shell
/data/local/busybox md5sum /data/local/hbooteng.nb0
If the output does not match "6991368ee2deaf182048a3ed9d3c0fcb" exactly, stop, delete it, and re-download it. Otherwise, continue.
Now we will write the new bootloader.
dd if=/data/local/hbooteng.nb0 of=/dev/block/mmcblk0p18
Confirm proper write:
/data/local/busybox md5sum /dev/block/mmcblk0p18
If the output does not match "6991368ee2deaf182048a3ed9d3c0fcb," try again; if it still doesn’t work, seek help from chat.andirc.net in channel #thunderbolt. DO NOT REBOOT.
Now, reboot your phone and put the custom RUU (PG05IMG.zip) on your SD card. Then flash it. This will upgrade you to release firmware with an S-OFF bootloader.
Next, run this command:
adb reboot bootloader
After it flashes, you will be running release firmware with S-OFF."
I have working recovery with S-Off. Just thought I would update incase this happens to anyone else
I'm having the same issue after rooting but I used the one click process. Guess at this point I should just try to go.throughit again? Or should I go.through adb and follow your steps?
Thanks you!
Nevermind
Sent from my ADR6400L using XDA App
hi,my htc got stuck logo.i format my desire z with no backups.i unlocked bootloader with htcdev.com........temp root.....S-on..........nothing flashing any Rom...neither custom roms..Nor default roms.....plzzzz help....only fastboot is working....no adb.....plzzzzzzzzzz heellppppppp
klassikkamii said:
hi,my htc got stuck logo... ....only fastboot is working....no adb.....plzzzzzzzzzz heellppppppp
Click to expand...
Click to collapse
Hello,
I am not sure If someone can help in this case.
Please provide more information.
* Do you confirm, that you cannot boot in recovery from HBOOT?
* What is your exact HBOOT version? Do you have an "Engineering HBOOT"?
When only fastboot is working then I only see a little chance for your phone when you have an engineering HBOOT.
Best regards,
Catherall
P.S: Seems like you really tortured you helpless Desire Z
thxx for reply......i try to provide in detail.
* Do you confirm, that you cannot boot in recovery from HBOOT?
yes , i can boot in recovery-clockwork-3.0.2.4-vision.
* What is your exact HBOOT version? Do you have an "Engineering HBOOT"?
No i think i am on stock hboot but i dont know indeed.
More Detail are,
My Hboot Screen shoes it.
****Unlocked****
Vision pvt ship S-on
HBoot-0.85.0015
Microp-0425
Radio-26.10.04.03_M
emmc-boot
Dec 20,2011,16:21:13
Also,should know.i installed Clockwork Recovery.which is working perfectly.when i flash rom it all goes success.but when i reboot with hope ,stuck in logo.i flashed Villision1.0 ,Android_Revolution_HD-4G_7.0.3,C7 succesfully but never start normally just stuck in logo.i use also fastboot flash boot boot.img as well but nothing happened.same stucking.when i use adb commands or adb shell ,getting error device not found.plzz give me back earlier position as company setting it was gingerbread 2.3.3.
i am sorry abount my low english language capabality.
Get your phone back on track with proper unlocking (S-OFF)
klassikkamii said:
thxx for reply......i try to provide in detail.
* Do you confirm, that you cannot boot in recovery from HBOOT?
yes , i can boot in recovery-clockwork-3.0.2.4-vision.
* What is your exact HBOOT version? Do you have an "Engineering HBOOT"?
No i think i am on stock hboot but i dont know indeed.
My Hboot Screen shoes it.
****Unlocked****
Vision pvt ship S-on
HBoot-0.85.0015
Microp-0425
Radio-26.10.04.03_M
Also,should know.i installed Clockwork Recovery.which is working perfectly.when i flash rom it all goes success.but when i reboot with hope ,stuck in logo.
Click to expand...
Click to collapse
Two things are not clear to me:
1) How did you "unlock" you phone, did you use http://htcdev.com/bootloader/ method to get "****Unlocked****" in HBOOT? This is important to know for me.
When you indeed unlocked using http://htcdev.com/bootloader/ method, then you have to install an suitable "boot.img" every time you flash a new ROM.
Otherwise the old boot.img tries to boot the old ROM that was overwritten with the new one you flashed.
2) When you can boot ClockworkMod Recovery then you can connect using adb. Just use adb while booted into your custom recovery.
I really recommend to proper unlock your HTC Desire Z as described in
http://goo.gl/aXNr
The advantage of this method is, that you can flash any custom ROM without the need to flash the kernel of the ROM (boot.img) separately!
ATTENTION: Before doing anything like "fastboot oem lock"
you have to use "misc_version 0.1" and "flashgc". Do not continue without that!
When you do not know how to use that then ask (here or in freenode IRC channel #G2ROOT)!
Then you can go on to downgrade your phone:
[GUIDE] Downgrade G2 (2.3.X) & DZ (2.3.X) & mT4g (2.3.4) & DHD w/ S-ON to Stock Froyo
http://forum.xda-developers.com/showthread.php?t=1178912
Please make sure that you follow the steps described under the topic ***If you have used the "official" htcdev.com unlock option***
Then you can gain S-OFF (real unlock) using gfree
If you have questions then come to the awesome freenode IRC channel #G2ROOT.
Best regards,
Catherall
yes i unlocked with htcdev.com,so i will lock it again with "fastboot oem bootlock" command and will try to unlock as your advice.
i am so happy after seeing your advices.and i didn't know that i can use adb shell in recovery.you mean boot in recovery than use adb terminal from pc.ok i check it and try to apply it.and thankyou very much again for your help.
I will tell you results.
Attention
Before using fastboot oem lock make sure that downgrade would work.
Run the commands "misc_version 0.1" and "flashgc" successfully before doing anything like
fastboot oem lock!
Visit freenode IRC channel #G2ROOT
I am not 100% sure what happens on your semi-bricked phone with fastboot oem lock!
Best regards,
Catherall
one more plzz
ok i will make sure but plzzz tell me can i restore officialy stock rom with adb support ( may be with golcard support ) sothat i dont wanna take any risk.no downgrade,no s-off just my previous position.
I went to #G2Root but i didnt understand how talk anybody.i am not familiar on that.again thxx for your attention for me.
P.E : ok i tried adb commands while booted in recovery. adb devices command works and show serial number, but when i command ' adb shell ' got " # " instead " $ " so stuck again need more advice plzzzzzzzzzzzz.how can get " $ "
PLssss Help
i am getting " ~ # " Error in adb shell please helppp....
Options for S-OFF/root or reverting to Stock
Hello klassikkamii,
most custom Recoveries provide root access when you use "adb shell" to connect to them.
So adb shell returns "#" to indicate root access. When you get the prompt "$" then you have access as a user.
I would do the following steps. They allow you to get full S-OFF, Engineering HBOOT and a ROOTed ROM, or if you prefer return to stock ROM.
Returning the latest stock is much easier and safer when you do the following steps to change the internal software version number of the phone an make your SD card a goldcard.
Download misc_version 0.1:
http://forum.xda-developers.com/attachment.php?attachmentid=661216&d=1311237785
Download flashgc:
http://forum.xda-developers.com/attachment.php?attachmentid=819704&d=1324116910
And then use the following procedure to change version number and make a goldcard (as provided by Setherio in his guide [GUIDE] Downgrade G2 (2.3.X) & DZ (2.3.X) & mT4g (2.3.4) & DHD w/ S-ON to Stock Froyo:
1) Unzip misc_version_01.zip and flashgc.zip in the platform-tools directory.
2) Run the following commands from you platform-tools directory:
Code:
adb shell mount /data
adb push misc_version /data/local/tmp/misc_version
adb push flashgc /data/local/tmp/flashgc
adb shell chmod 777 /data/local/tmp/*
adb shell
Now you are in the phone shell with root access (indicated by the prompt "#").
Continue with the commands:
Code:
cd /data/local/tmp
./misc_version -s 1.00.000.0
This should return:
--set_version set. VERSION will be changed to: 1.00.000.0
Patching and backing up partition 17...
Continue to make you SD card a goldcard:
Code:
./flashgc
Note: If you get the following error, please make sure your sdcard is inserted in your phone: Error opening backup file.
Continue with the command
Code:
sync
Double check that you phone's software version number is set to 1.00.000.0 with the command:
Code:
dd if=/dev/block/mmcblk0p17 bs=1 skip=160 count=10
The first line of the command output must be:
1.00.000.010+0 records in
Exit the phone's shell with
Code:
exit
From here you can get an Engineering HBOOT and a custom, rooted ROM, or revert to a stock ROM. Both ways are about the same effort.
Please post how this worked out for you.
Best regards,
Catherall
still stuck
adb push misc_version /data/local/tmp/misc_version
Getting Error
failed to copy 'misc_version' to /data/loca/tmp/misc_version :Not a directory
As i am already with "~ #" i try direct command :cd /data/local/tmp
Got Error This :/sbin/sh: cd:can't cd to /data/local/tmp
if i use command for sd card,
adb push misc_version /Sdcard/misc_version
it show size of file or push succed but not in local/tmp.
i think if i would get "$" instead " ~#" May be i can do all u advice me.
Better do it interactive
Hello,
there might be several reasons why the command did not work.
Not having "$" is none of them.
Please come to freenode IRC and login to channel #G2ROOT. Ask for Catherall, I should be there for the next hours. When I am not there then check back later.
Best regards,
Catherall
ok i solved all Puzzle.solution was only use " GoldCard Method".i use command mmc2 instead mmc1 and voilaaaaaa i got my CID then everything was eassy.....in the End i really thanks to Catherall,You help me well...your information was helpfulln from your instructions i got my way thanksssss...
Alright well i'm using the zedomax tutorial from htcevohacks. and i'm stuck at step Step 8:
Next, open up a command prompt and type:
cd \hbootdowngrade217
adb push misc_version /data/local/
adb shell /data/local/misc_version -s 1.10.651.2<<<<<now after i type that in i get Denied permissions.... WHY PLEASE HELP
adb reboot bootloader
fastboot getvar mainver
If you get back mainver: 1.10.651.2, you are good to go, go to the next step.
could anyone please help me with this
Spazzpyro said:
Alright well i'm using the zedomax tutorial from htcevohacks. and i'm stuck at step Step 8:
Next, open up a command prompt and type:
cd \hbootdowngrade217
adb push misc_version /data/local/
adb shell /data/local/misc_version -s 1.10.651.2<<<<<now after i type that in i get Denied permissions.... WHY PLEASE HELP
adb reboot bootloader
fastboot getvar mainver
If you get back mainver: 1.10.651.2, you are good to go, go to the next step.
could anyone please help me with this
Click to expand...
Click to collapse
Are you sure you are rooted?
well i'm using the directions for temp root... and when i go through that it says i am.. i'm relcocked hboot 1.5 s-on i re rooted it and then unrooted it again and tried this method again and i'm still getting the same thing
When u do adb shell, do u have $ or #?
cd \hbootdowngrade217
adb push misc_version /data/local/
adb shell /data/local/misc_version -s 1.10.651.2
adb reboot bootloader
fastboot getvar mainver
those are the codes i'm using if thats what u mean
Spazzpyro said:
cd \hbootdowngrade217
adb push misc_version /data/local/
adb shell /data/local/misc_version -s 1.10.651.2
adb reboot bootloader
fastboot getvar mainver
those are the codes i'm using if thats what u mean
Click to expand...
Click to collapse
No, I meant type adb shell and see if their is a # (meaning root) or a $ (meaning no root)
The downgrade thread here at xda made by unknownforce doesnt have that step anymore, its now in the last step. check it out its here
i got a # so i'm rooted i been looking on that thread
Are you giving that command while in android or recovey?
android
Is usb degugging on?
yeah
ok now i've got farther!!!! i think i was copy and pasting it thats why but now instead of it saying no permission or w.e its saying file not found... so whats the code i put in or file name? i got the hbootdowngrade217 file... in my root directory with the fastboot and adb...
ok nvm i'm back to square one same thing with no permission :-/
Did you go through steps again just to make sure you didn't miss a step
Try to restore with an official ruu. Download it and put it in your sd card. Let it boot and turn usb debugging on, then follow the instructions to temporarily root your phone and try again from there.
I have yet to root my Atrix 4G and have been scouring the web to try and find a working method for (at the time .141) which now has been updated. Has anyone tried to root a stock Atrix after this update? Are there any root methods out there that'll give me root access but not completely wipe the phone/new ROM?
The traditional preinstall method should still work. No wiping happens with that. I used it back when I first rooted my phone, everything stayed exactly as it was (all stock) except I had root too.
ravilov said:
The traditional preinstall method should still work. No wiping happens with that. I used it back when I first rooted my phone, everything stayed exactly as it was (all stock) except I had root too.
Click to expand...
Click to collapse
I bought Atrix 4g recently, it came with Android 2.3.4 & Build 4.5.91, I have tried to install CM10 but it looks like the phone is locked. I tried /preinstall fastboot to root, but I am getting "waiting for device", not sure what the problem is. Can some one help me pointing to the right direction? Thanks.
Is the phone in fastboot mode?
ravilov said:
Is the phone in fastboot mode?
Click to expand...
Click to collapse
Yes, the phone is in USB debugging & fast boot mode. Thanks.
USB debugging is irrelevant. It just needs to be in fastboot mode.
Do you have all the proper Moto drivers? What OS?
Look here for info that may help.
Questions go in Q&A, not Development.
ravilov said:
USB debugging is irrelevant. It just needs to be in fastboot mode.
Do you have all the proper Moto drivers? What OS?
Click to expand...
Click to collapse
Yes, have all the moto drivers. Running on Windows 7.
I didn't create this thread, I used the one that is already existing. If it is in the wrong folder, can mod please move this thread to the right folder.
After reinstalling the Motorola driver, it was connecting. But I am struck at the mount point now. Can some one please help what I am doing wrong?. Thanks.
C:\moto-fastboot>adb shell
$ /preinstall/dosu
/preinstall/dosu
bash: groups: command not found
[email protected]:/# whoami
whoami
root
[email protected]:/# /bin/mount-0 remount,rw /system
/bin/mount-0 remount,rw /system
bash: /bin/mount-0: No such file or directory
[email protected]:/# /preinstall/su
/preinstall/su
# /bin/mount-0 remount,rw /system
/bin/mount-0 remount,rw /system
/bin/mount-0: not found
# cp /preinstall/su /system/bin/
cp /preinstall/su /system/bin/
cp: cannot create '/system/bin/su': Read-only file system
#
#
vasudel said:
[email protected]:/# /bin/mount-0 remount,rw /system
/bin/mount-0 remount,rw /system
bash: /bin/mount-0: No such file or directory
Click to expand...
Click to collapse
Very wrong. No wonder nothing else works after that. It is absolutely crucial to follow the instructions to the letter, literally.
For example, instead of the zero you are supposed to have the lowercase "O", and you're missing some spaces too.
ravilov said:
Very wrong. No wonder nothing else works after that. It is absolutely crucial to follow the instructions to the letter, literally.
For example, instead of the zero you are supposed to have the lowercase "O", and you're missing some spaces too.
Click to expand...
Click to collapse
Thanks ravilov, I copy & paste from the website. So it looks like it has been installed. I assume it has been rooted & bootloader unlocked. But after restarting when I put it in Recovery mode to flash the CM10 zip files. It shows the yellow triangle & Android logo, nothing happens after that. I have to take out the battery to restart. Does it show UNLOCKED when we put it in the Recovery mode on the top?
C:\moto-fastboot>moto-fastboot.exe flash preinstall preinstall.img
sending 'preinstall' (30720 KB)... OKAY [ 3.396s]
writing 'preinstall'... OKAY [ 2.858s]
C:\moto-fastboot>moto-fastboot.exe reboot
rebooting...
C:\moto-fastboot>adb shell
$ /preinstall/dosu
/preinstall/dosu
bash: groups: command not found
[email protected]:/# /bin/mount -o remount,rw /system
/bin/mount -o remount,rw /system
[email protected]:/# cp /preinstall/su /system/bin
cp /preinstall/su /system/bin
[email protected]:/# chmod 6755 /system/bin/su
chmod 6755 /system/bin/su
[email protected]:/# PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
pkg: /preinstall/Superuser.apk
vasudel said:
Thanks ravilov, I copy & paste from the website. So it looks like it has been installed. I assume it has been rooted & bootloader unlocked. But after restarting when I put it in Recovery mode to flash the CM10 zip files. It shows the yellow triangle & Android logo, nothing happens after that. I have to take out the battery to restart. Does it show UNLOCKED when we put it in the Recovery mode on the top?
Click to expand...
Click to collapse
OK well, what do you expect? You can't boot into recovery before you install it...
Yes, it looks like rooting went well. To confirm, you can download Root Checker from Play Store. Only problem is, if you really only wanted to install a custom ROM, rooting is completely irrelevant...
Anyway, look in other threads, there are two major recoveries to choose from: RomRacer's CWM or TWRP.
There is no "recovery mode", there is just "booting into recovery". The "UNLOCKED" text is only shown during initial boot screen.
ravilov said:
OK well, what do you expect? You can't boot into recovery before you install it...
Yes, it looks like rooting went well. To confirm, you can download Root Checker from Play Store. Only problem is, if you really only wanted to install a custom ROM, rooting is completely irrelevant...
Anyway, look in other threads, there are two major recoveries to choose from: RomRacer's CWM or TWRP.
There is no "recovery mode", there is just "booting into recovery". The "UNLOCKED" text is only shown during initial boot screen.
Click to expand...
Click to collapse
I did install Root checker & verified that it is rooted now.
I am little confused, because the website mentioned it needs to rooted before I install the CM10 (Jelly bean) ROM. What do I really need to install CM10 (Jelly bean)?. When I looked at Custom CWM-based Recovery 5.0.2.7-atrix5 as you suggested, it says "This recovery is only for UNLOCKED devices", I am not sure what it means?. Does it mean unlock bootloader or SIM network unlock?. Thanks.
C:\moto-fastboot>moto-fastboot devices
TA2070HEQI fastboot
C:\moto-fastboot>moto-fastboot erase recovery
erasing 'recovery'... FAILED (remote: (00180001))
C:\moto-fastboot>moto-fastboot flash recovery recovery-atrix5.img
sending 'recovery' (4708 KB)... OKAY [ 0.514s]
writing 'recovery'... FAILED (remote: (00180002))
Also I just installed GOOManager & tried to flash CM10, it shows "Failed to boot 2" . Luckily I can still pull the battery & works fine with the Stock ROM.
/ruh roh!
Hi guys,
I made the mistake of allowing this update to install, and despite using OTA Rootkeeper, I still lost full root.
I figured I'd give the preinstall method a try and see what happens.... not good.
I can get all the way through the step until the "cp /preinstall/su /system/bin/", then it chokes:
cp: write error: No space left on device
For some reason, Root Explorer was able to still rw on the /system, so for giggles, I backed up and deleted a few usekess apk's to get some needed space. No good, the reported volume free space did not change, and still couldnt copy to bin.
I'm stumped at this this point.... I'm ok on Linux in general, but that only helps so much on android, lol
Any ideas or suggestions?
vasudel said:
I am little confused, because the website mentioned it needs to rooted before I install the CM10 (Jelly bean) ROM. What do I really need to install CM10 (Jelly bean)?.
Click to expand...
Click to collapse
To install any custom ROM, you need unlocked bootloader and custom recovery. That is all.
vasudel said:
When I looked at Custom CWM-based Recovery 5.0.2.7-atrix5 as you suggested, it says "This recovery is only for UNLOCKED devices", I am not sure what it means?. Does it mean unlock bootloader or SIM network unlock?. Thanks.
Click to expand...
Click to collapse
It means bootloader unlock. No ROM, recovery, or anything else ever cares about SIM/network lock. Only carriers and SIM cards care about that.
vasudel said:
C:\moto-fastboot>moto-fastboot devices
TA2070HEQI fastboot
C:\moto-fastboot>moto-fastboot erase recovery
erasing 'recovery'... FAILED (remote: (00180001))
C:\moto-fastboot>moto-fastboot flash recovery recovery-atrix5.img
sending 'recovery' (4708 KB)... OKAY [ 0.514s]
writing 'recovery'... FAILED (remote: (00180002))
Click to expand...
Click to collapse
No idea why it's reporting these errors. I assume the recovery is indeed called recovery-atrix5.img and is in the same folder as moto-fastboot? Maybe a stupid question but I have nothing else right now.
Ditto
I am having the same problem. "no space left on device".
I would like to get this thing rooted so the battery fix will work on it. Any help would be most appreciated.
Rodney
KetoSoi said:
Hi guys,
I made the mistake of allowing this update to install, and despite using OTA Rootkeeper, I still lost full root.
I figured I'd give the preinstall method a try and see what happens.... not good.
I can get all the way through the step until the "cp /preinstall/su /system/bin/", then it chokes:
cp: write error: No space left on device
For some reason, Root Explorer was able to still rw on the /system, so for giggles, I backed up and deleted a few usekess apk's to get some needed space. No good, the reported volume free space did not change, and still couldnt copy to bin.
I'm stumped at this this point.... I'm ok on Linux in general, but that only helps so much on android, lol
Any ideas or suggestions?
Click to expand...
Click to collapse
I did some more testing, I posted over in this topic as the info seemed relevant:
http://forum.xda-developers.com/showthread.php?t=1182871&page=111
ravilov said:
To install any custom ROM, you need unlocked bootloader and custom recovery. That is all.
It means bootloader unlock. No ROM, recovery, or anything else ever cares about SIM/network lock. Only carriers and SIM cards care about that.
No idea why it's reporting these errors. I assume the recovery is indeed called recovery-atrix5.img and is in the same folder as moto-fastboot? Maybe a stupid question but I have nothing else right now.
Click to expand...
Click to collapse
Yes the recovery-atrix5.img is in the same folder as fastboot. But I am getting "Failed to boot 2" now, it looks like I need to unlock Bootloader. But there is a thread "Automatic bootloader UNLOCK/ROOT for AT&T 1.26/1.57/1.83/4.5.91", but there is one other thread which warns about SBF Hard bricked. Not sure which one to start with confidently.
By far this is the one that took me 2 days & still struggling, I have done cracking CM10 on HP touchpad, IPhone & other flashing, it was all just piece of cake.
I will use this thread for my question cause it's similar and to avoid spam. Apologize to the OP.
So my questions are:
Can someone tell me what method should I use to unlock my Atrix? It's European one with Android 2.3.4 and Build 4.5.2. I've searched the forum but there are methods only for the AT&T US Version and for Atrix 4G and I'm not completely sure that they will work.
My second question is if I should avoid all SBF or only some "special" SBFs that can hardbrick my phone. I mean if I only root my phone and I use CWM and never EVER use RSD there is no possible way for me to hardbrick my phone, right?
Thanks in advance!
Edit:
I just managed to unlock my device thanks to this good guy right here http://forum.xda-developers.com/showthread.php?t=1302423 Cheers for him!!! But I still need an answer for my second question cause it concerns me more. Hard bricking my phone will break my hearth. ;(