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. ;(
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
Alright everyone,for those of you having issues to revolution on your Evo 3d and flooding the irc I figured id start this to compile everything.
Things I have noticed.
1. yes after the install your device to attempt a hands free activation,don't freak when is say checking for firmware update,it wont find anything!
2. You may have to do a battery pull after the initial flash/install. On Mine,the recovery did not install! Problem will be worked out im sure,this is a beta AND teamwin has their own recovery going on as well.
[ I have found the reason why the recovery is not installed is simply because clockwork is not support on the shooter yet.Do install a recovery use team wins recovery image and directions which can be found here: http://forum.xda-developers.com/showthread.php?t=1192077
Here is a simplistic break down on how to do this,I am not responsible for your actions!
Download the .img file found in the thread,make sure you also download the fastboot.exe and place it in the same folder as ADB for easy access. Once that is done,reboot while holding down your power + volume down button!
Fastboot menu will come up,the command you need it
fastboot flash recovery (location of file).img
For me it was fastboot flash recovery C:\Downloads\durka.img yes I renamed it durka because I dont like long names]
3. If you are having issues getting your serial number,connect it to ADB and do adb get-serialno
4. If you cannot get root,you will have to download busybox by stericson on the market. I had to manually sign into my gmail accounts so remember your passes!
[This is wrong,if you do not have root you need to have the teamwin recovery installed and you need to flash the superuser.zip file found on the forums. If you are having issues installing,make sure signature verification is unchecked,then once reboot install busybox]
All apps that I have that require root are working for me, just waiting on a deodexed rom. Even SetCPU is working,but I dont have the custom kernel installed,which could actually be easily doable now!
And I leave the thread to y'all
Well, I can probably help troubleshoot. Rooted and installed teamwin recovery first try. Doing a nandroid backup now.
I can also help people troubleshoot, I am also rooted and have teamwin recovery going!
N e 1 kno how to do this with a mac?
D3VO
Rooted and recoveried on first try. Doing my compressed NAND backup now. (I like the fact that it can be compressed...but it's slow as hell lol)
Yeah, I was a tad concerned at first about the hands-free activation notice, but everything was smooth like buttah... Thank god I remembered my passwords!
My issues:
First try: I got all the way to the part where the phone is taken to hboot and fastboot usb is selected. I was getting a red X for the driver not being installed bc I didn't have HTC Sync installed, so I cancelled revolutionary, rebooted my phone, installed htc sync on my pc, and tried again...
Now, after rebooting both my phone and the pc, I can't get past the initial "Acquiring Root" step.
help...
rtbluver said:
I can also help people troubleshoot, I am also rooted and have teamwin recovery going!
Click to expand...
Click to collapse
Successfully gained S-OFF but when I select recovery from HBOOT it sends me to htc screen. Power button then reboots phone.
tia
A few of us are stuck on --- Acquirig root ( method 3) -- Any ideas???
only issue I've found is that Titanium Backup refuses to work on my phone.
yes, I flashed the SU package found here, and also tried the Busybox installer from the market.
besides that, everything's working great, already nandroided my stock setup and my WiMax partition while waiting for the ROMs to drop!
hey guys.....im trying to fastboot thye recovery img but cant quite to get it goiung.....do the recovery img and fastboot.exe have to be placed int he same folder?....or where exactly do i put them?.....thanks fellas
tek818 said:
My issues:
First try: I got all the way to the part where the phone is taken to hboot and fastboot usb is selected. I was getting a red X for the driver not being installed bc I didn't have HTC Sync installed, so I cancelled revolutionary, rebooted my phone, installed htc sync on my pc, and tried again...
Now, after rebooting both my phone and the pc, I can't get past the initial "Acquiring Root" step.
help...
Click to expand...
Click to collapse
HTC Sync should not be installed. Install the HTC Fastboot drivers from the revolutionary wiki
reverepats said:
hey guys.....im trying to fastboot thye recovery img but cant quite to get it goiung.....do the recovery img and fastboot.exe have to be placed int he same folder?....or where exactly do i put them?.....thanks fellas
Click to expand...
Click to collapse
Yes, Fastboot, recovery and AdbWinUsbApi.dll must all be in the same folder
miguelfp1 said:
only issue I've found is that Titanium Backup refuses to work on my phone.
yes, I flashed the SU package found here, and also tried the Busybox installer from the market.
besides that, everything's working great, already nandroided my stock setup and my WiMax partition while waiting for the ROMs to drop!
Click to expand...
Click to collapse
TB works great for me. Are you sure that the su installed? is it in your app drawer? If not download it from the market and try installing that.
housry23 said:
TB works great for me. Are you sure that the su installed? is it in your app drawer? If not download it from the market and try installing that.
Click to expand...
Click to collapse
yeah, flashed it twice. other root programs work (including the Busybox installer), which stumps me... TB even worked flawlessly with the temp-root before
Did you try uninstalling then reinstalling TB?
housry23 said:
Yes, Fastboot, recovery and AdbWinUsbApi.dll must all be in the same folder
Click to expand...
Click to collapse
mines set like that but i get
Code:
C:\sdk\tools>fastboot flash_image recovery C:\Users\Tesso\Desktop\recovery-twrp-
shooter-1.img
usage: fastboot [ <option> ] <command>
CheesyNutz said:
mines set like that but i get
Code:
C:\sdk\tools>fastboot flash_image recovery C:\Users\Tesso\Desktop\recovery-twrp-
shooter-1.img
usage: fastboot [ <option> ] <command>
Click to expand...
Click to collapse
In the new sdk adb is in platform-tools folder, so here's what I did. I moved fastboot and twrp recovery to platform-tools folder, renamed the recovery image to recovery.img and pressed shift while right clicking on the platform-tools folder and choose open command prompt(or window) here. Then just type flasboot flash recovery recovery.img and press enter. Worked for me.
I see what you did...you have to type "fastboot flash recovery nameofrecoveryhere.img" and it will work. Make sure the recovery image is in the same folder as fastboot.
housry23 said:
Did you try uninstalling then reinstalling TB?
Click to expand...
Click to collapse
no go either , I'll keep trying
thanks for your help!
miguelfp1 said:
no go either , I'll keep trying
thanks for your help!
Click to expand...
Click to collapse
Did you unroot the temp root before installing Revolutionary? This might be the cause because attn1 from AlphaRev told me to unroot and factory reset to get rid of all the temp root stuff before running Revolutionary.
irock1985 said:
A few of us are stuck on --- Acquirig root ( method 3) -- Any ideas???
Click to expand...
Click to collapse
I'm stuck here also..
Ok First Of all This Rom Is The Fastest I have Ever used.
But ok HEre is my Huge problem. so i was rooted bl unlocked everything fine, with my stock rom with 1.3 ghz kernel until i installed the home base ext 4 mega. ok my problem is simple, when i installed it, it basically unrooted my device is was supposed to be a rooted rom, but anyway i decided to root my atrix again right? and thats when i found that when im on adb writing cp /preinstall/su /system/bin sumthing like that it says cp write error: No space left on device. and i cant root my device !!!! PLEASE HELP!!!!!!!!!!!!!!!!!!!! If I can't root my device it is paperweight basically
This is the set of instructions I have always used and have always worked and now they give me this annoying error of no space left on device. After cp /preinstall/su /system/bin
Put phone in fastboot mode, then:
Code: fastboot flash preinstall preinstall.img fastboot reboot
(older versions maybe need "fastboot -i 0x22b8")
after fastboot & reboot, type in adb ("adb shell") or terminal emulator, exactly:
Code: /preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
chmod 6755 /system/bin/su
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
Really should move the thread before ppl start *****in
Ps. Try doin a clean reinstall again.
Sent from my CM7 Motorola Atrix 4G
Should be in Q&A!
SUPER DEV THREAD GOOOOOOOOooooooooo
Ilkinansr92 said:
Really should move the thread before ppl start *****in
Ps. Try doin a clean reinstall again.
Sent from my CM7 Motorola Atrix 4G
Click to expand...
Click to collapse
Sir but how can i do a clean install again? if i cannot root my phone i need a recovery and it need's rooting the phone what can i do.
i'm running on a darkside prefinal rom for about a month.
suddenly the soft stopped responding(don't work at all), and the screen sometimes think i'm touching it when the phone lays on the table far from me.
i think i should mention that before the darkside i had a gingerbread at&t stock rom and after that a cm7 nightly rom.
i read on the internet and even in this forum that i need to run a pds fix.
i tried that it fixed the phone for about day or two and then everything went wrong again.
i returned to the store where i bought the phone. they burned me a at&t original stock rom. that fixed the problem for two hours at most.
i wanted to know if someone knows how to fix it or did anyone encounter this problem.
thanks
Nir
I have soft keys issue too.
i got a similar problem..
just wrote this.. unfortunately in the wrong q&a.. anyway.
did you find any solution?
didn't find an answer.
i'm starting to think this is a hardware problem.
There is a thread called FIX PDS, download it, install it through CWM and the problem is gone
i tried a pds fix it didn't fix the problem
i think that's because i didn't preform it well
can you explain how to do it?
can you quote the post of the pds fix?
here is the original post. you have to download the img file from there.
Choose your version: FroYo(*_v4) or Gingerbread (*_v8)
METHOD 1 (Locked Bootloader)
Extract the .img file.
Here is the code:
Code:
adb push pdsfix.img /data/local/tmp
adb shell
su chmod 777 /data/local/tmp/pdsfix.img
dd if=/data/local/tmp/pdsfix.img of=/dev/block/mmcblk0p3
exit
exit
adb reboot
Click to expand...
Click to collapse
METHOD 2 (Unlocked Bootloader)
You can use these commands in Fastboot mode :
(Obviously remember to place the pds.img in the same folder where you have the moto-fastboot executable)
Here is the code:
Code:
moto-fastboot flash pds pdsfix.img
moto-fastboot reboot
Click to expand...
Click to collapse
PS: IN SOME CASES YOU NEED TO WIPE CACHE.
If wiping thru CWM Recovery does not help try, the following commands to deeply erase thru Fastboot.
Here is the code:
Code:
Fastboot getvar boot-mode
Fastboot erase cache
Fastboot reboot
Click to expand...
Click to collapse
Enjoy
Click to expand...
Click to collapse
hope this helps you out. it did for me!
i tried it too but it didn't work for me
i have some questions if you don't mind
first how did you run all this code lines? (i tired throw a terminal application)
second how to i know which one of them to use? (i tried both)
which method should i choose? (i tried the first one)
how to i get permissions to move the img file into the /data/local/tmp directory.(i tried
running it throw the terminal application from /sdcard directory)
also i didn't have permission to run the "dd if=/data/local/tmp/pdsfix.img of=/dev/block/mmcblk0p3" command
can you help me understand specifically how to run the pdsfix.img file
i'm kind of a new in this thing
Thank
Nir
if yall need help with the pds fix i have an easyer fix than that its 100% works if thats the issue or if its a digitizer issue
Pm me we can sort this out on skype
ill walk ya right through the whole process
OK, here's the deal. My i777 was running SlimROM, updated, and now my power button is inop. Flashed back to stock ICS, but I forgot to do one critical step - a complete wipe before installing. Now my phone gets stuck at the "Rethink Possible" screen, and I can't do anything else.
I've booted into 3e recovery and tried recovery --wipe_data through adb, but it still hangs. (as suggested here). I've got a jig, forced it into download mode, and tried flashing another ROM, but I still get stuck on the Rethink Possible screen.
Is there a way that I can basically nuke all the contents of the phone so I can use it again? I've read through most of the documentation for adb, but I don't see an option.
steelforce said:
OK, here's the deal. My i777 was running SlimROM, updated, and now my power button is inop. Flashed back to stock ICS, but I forgot to do one critical step - a complete wipe before installing. Now my phone gets stuck at the "Rethink Possible" screen, and I can't do anything else.
I've booted into 3e recovery and tried recovery --wipe_data through adb, but it still hangs. (as suggested here). I've got a jig, forced it into download mode, and tried flashing another ROM, but I still get stuck on the Rethink Possible screen.
Is there a way that I can basically nuke all the contents of the phone so I can use it again? I've read through most of the documentation for adb, but I don't see an option.
Click to expand...
Click to collapse
Id wait until a dev chimes in, but my understanding is that as you can still get into DL mode, ODIN would be your best bet. Id flash one of the all in one ODIN ICS packages that also contain boot loaders (LL6 would be most recent). As a last resort you can also flash the stock .pit file and repartition the whole phone, BUT BE SURE TO BACKUP YOUR EFS FOLDER if possible. I say this as I did not do this and now have a generic IMEI on my phone, hindering some aps from working.
ADB is able to reformat and flash ROM packages as far as i know, though it should be unnecessary as long as you can still use ODIN. The only reason i used ADB was to resurrect a S2 i bought of someone that flashed a ROM from a i9100.
steelforce said:
OK, here's the deal. My i777 was running SlimROM, updated, and now my power button is inop. Flashed back to stock ICS, but I forgot to do one critical step - a complete wipe before installing. Now my phone gets stuck at the "Rethink Possible" screen, and I can't do anything else.
I've booted into 3e recovery and tried recovery --wipe_data through adb, but it still hangs. (as suggested here). I've got a jig, forced it into download mode, and tried flashing another ROM, but I still get stuck on the Rethink Possible screen.
Is there a way that I can basically nuke all the contents of the phone so I can use it again? I've read through most of the documentation for adb, but I don't see an option.
Click to expand...
Click to collapse
You need root access to format the data partition. I don't use adb a lot, but I think you can boot into recovery, then "adb shell", then "format data." You might have to type "su." If that doesn't get you out of the Rethink Possible screen, the I would format data, format system, and format cache. Then turn the phone off, by pulling the battery if necessary, and enter download mode and flash the full stock distribution. As the previous poster suggested, UCLL6 would be a good choice. You can get it from the download repository. See the link in my signature.
creepyncrawly said:
You need root access to format the data partition. I don't use adb a lot, but I think you can boot into recovery, then "adb shell", then "format data." You might have to type "su." If that doesn't get you out of the Rethink Possible screen, the I would format data, format system, and format cache. Then turn the phone off, by pulling the battery if necessary, and enter download mode and flash the full stock distribution. As the previous poster suggested, UCLL6 would be a good choice. You can get it from the download repository. See the link in my signature.
Click to expand...
Click to collapse
Thanks. I forgot to grab the phone before I left for the office this morning, so I'll try it when I get home later tonight.
steelforce said:
Thanks. I forgot to grab the phone before I left for the office this morning, so I'll try it when I get home later tonight.
Click to expand...
Click to collapse
So, home with my phone. When I get into the shell, format isn't a valid command:
Code:
[email protected]:/ $ format
format
/system/bin/sh: format: not found
Trying to su ends up segfaulting, so I don't think it's a permissions issue. Other sources suggest using fastboot, but as I understand it, the i777 doesn't support it.
I'm looking at the mounts - is there documentation on which of the /dev/block/mmcblk0pX partitions map to the mount points? I'm familiar with Linux (at least enough to get me in trouble), but I'm lost on where to go next.
You have to have root access to do the format command. Requires the # prompt, like this:
Code:
adb shell
$ su
# format data
# exit
$ exit
Probably, cache is mounted but system and data are not mounted. It shouldn't make any difference though, if I remember right.
If you can't get the su command to give you the # prompt, then maybe adb is not connected to the daemon correctly?
Edit:
I have never used adb in recovery before, so for my own interest, I decided to do a little experimentation. First of all, to get a hash prompt in shell try
Code:
adb root
followed by
Code:
adb shell
From reading, it seems some people say both wipe and format commands should work in shell in recovery, but I couldn't get them to work. I would get "/sbin/sh: format: not found" error. So the work around is this:
Code:
adb shell
~ # mount /data
~ # rm -rf /data/*
~ # reboot
This will recursively force the removal of the contents of the data directory. I did not test this, but I did test "rm -rf /cache/*" and successfully removed the contents of the cache directory, so I know it should work.
If your system still doesn't boot, you could wipe cache and system as well as data and then reboot into download mode and flash the full stock tar
Code:
adb shell
~ # mount /data
~ # mount /system
~ # rm -rf /cache/*
~ # rm -rf /data/*
~ # rm -rf /system/*
~ # reboot download
creepyncrawly said:
Edit:
I have never used adb in recovery before, so for my own interest, I decided to do a little experimentation. First of all, to get a hash prompt in shell try
Code:
adb root
followed by
Code:
adb shell
Click to expand...
Click to collapse
Ugh - adb root fails with the following error:
Code:
D:\adt-bundle-windows-x86_64-20130219\sdk\platform-tools>adb root
adbd cannot run as root in production builds
Looks like it's because the build that I have flashed doesn't have root. Wicked catch-22, since I can't root the phone until I wipe the cache to actually boot.
steelforce said:
Ugh - adb root fails with the following error:
Code:
D:\adt-bundle-windows-x86_64-20130219\sdk\platform-tools>adb root
adbd cannot run as root in production builds
Looks like it's because the build that I have flashed doesn't have root. Wicked catch-22, since I can't root the phone until I wipe the cache to actually boot.
Click to expand...
Click to collapse
Well, yes, you need root. You could flash one of the stock plus root packages, probably Entropy512's original uckh7 plus root since it has busybox, with odin, see links in my sig. I didn't see anything in your original posts that indicate the flash would fail.
creepyncrawly said:
Well, yes, you need root. You could flash one of the stock plus root packages, probably Entropy512's original uckh7 plus root since it has busybox, with odin, see links in my sig. I didn't see anything in your original posts that indicate the flash would fail.
Click to expand...
Click to collapse
The flash doesn't fail, but it's never able to boot past the AT&T "Rethink Possible" splash screen. I've tried flashing a couple of different packages, but i'll try some more tonight.
steelforce said:
The flash doesn't fail, but it's never able to boot past the AT&T "Rethink Possible" splash screen. I've tried flashing a couple of different packages, but i'll try some more tonight.
Click to expand...
Click to collapse
Flash the rooted package and you will then have root. Whether the phone boots or not, the system will then contain the superuser.apk and the su binary. I suggested Entropy512's package because I'm not sure but I think you need busybox to use the unix commands in adb in recovery. My stock plus root packages don't have busybox, and if you can't boot, you can install it from the play store. Once you have root in the system, then adb root should succeed.
creepyncrawly said:
Flash the rooted package and you will then have root. Whether the phone boots or not, the system will then contain the superuser.apk and the su binary. I suggested Entropy512's package because I'm not sure but I think you need busybox to use the unix commands in adb in recovery. My stock plus root packages don't have busybox, and if you can't boot, you can install it from the play store. Once you have root in the system, then adb root should succeed.
Click to expand...
Click to collapse
I tried both of Entropy512's packages from here. Flashed them and tried to boot, both hung at the Rethink Possible screen. Rebooted into recovery, was able to connect to it via adb - but adb root failed on both.
I'm getting closer and closer to punting and picking up a Nexus 4 after this....
With lineage recovery I do a full wipe like:
Code:
mkfs.ext4 -qFF /dev/block/by-name/userdata
mkfs.ext4 -qFF /dev/block/by-name/cache
mkfs.ext4 -qFF /dev/block/by-name/system