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.
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.
Guys,
I need help. I tried to work the solution myself and spend days reading different forums and tried different tricks but no luck.
So basically I was asked by my wife to root her Hero as she wanted a higer version of Android to install Viber and some other programmes. I did that using instructions on a Cyanogenmod wiki and everything went fine. However the new rom made the phone a bit slow and clumsy, so I thought I'd look for a different older version that works. I tried numerous roms and they all for some reason were not suitable - either wouldn't boot or were force closing etc...
So at the end of the day I read somewhere that for some ROM you need to install a CWM recovery and I was running a RA 1.7. So I tried to download a newer version of a recovery (to be honest I forgot which one - it was a week ago) and I flashed it and then I realised I have installed a recovery for CDMA and I have a GSM.
So, currently the phone boots and gets stuck at the HERO logo forever. There is no way I can boot into recovery. I have no problem to boot into fastboot, but any attempt to install a different recovery brings a failed signature error. I tried fastboot erase recovery and it did work, but no instalation is possible. When the phone is powered on and while on HERO logo I can run adb and can make it reboot from the command line, but when I try the instructions http://forum.xda-developers.com/showthread.php?t=1630519 I get past the first two lines:
Code:
adb push recovery-clockwork-2.5.0.7-hero.img /data/local/
adb push flash_image /data/local/
and then when I attempt this
Code:
adb shell chmod 777 /data/local/recovery-clockwork-2.5.0.7-hero.img
I get an error message
-exec /system/bin/sh failed no such file or directory
Please help!
PS. A screen shot in fastboot:
http://i3.photobucket.com/albums/y78/tsvet/fastboot.jpg
I managed to fix that with a stock rom and Hboot installation.
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. ;(
Hello!
I want to root my Be United smartphone. Im not found any custom ROMs, recoveries and others for this phone. I try to root this. Framaroot was failed(error 5). I cant flash SU via recovery(3e) due to signature. But... I can unlock bootloader(fasboot oem unlock command works). So, what now? If I try fastboot update i get this:
[[email protected] Bartosz]# fastboot update SU-Busybox-Installer.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
And some more:
[[email protected] Bartosz]# adb remount
remount failed: Operation not permitted
[[email protected] Bartosz]# adb root
adbd cannot run as root in production builds
[[email protected] Bartosz]# fastboot oem unlock
...
OKAY [ 0.001s]
What now? Some method must exist....
Edit:
And i just flashed via recovery package Superuser-3.1.3-arm-signed.zip. But superuser and su are not present in /system(yes, package was verified and flashed successfully).
Anybody?
Still anybody? Please, guys... must be any method...
Please...
Refresh
Refresh
Refresh....
up.. i have the same phone:silly:
succes rooting with srsroot..