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
I believe in this rom has ext4 problems. If you try to modify the file system, it is ruined. At least in my case. Try install the ext3.
Enviado desde mi MB860 usando Tapatalk
Malaquai said:
I believe in this rom has ext4 problems. If you try to modify the file system, it is ruined. At least in my case. Try install the ext3.
Enviado desde mi MB860 usando Tapatalk
Click to expand...
Click to collapse
Ty for answering but i have a question how can i install it if i cannot root my phone :S i need a recovery and it need's rooting the phone. what can i do.
Download the .zip for the rom onto your internal sd card, reboot phone into recovery mode, clear caches etc., install .zip from sd card.
Sent from my MB860 using Tapatalk
EzEddie said:
Download the .zip for the rom onto your internal sd card, reboot phone into recovery mode, clear caches etc., install .zip from sd card.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Ok so I got onto android recovery clear cache's and when I tried to install the zip it says
E: signature verification failed
and it dosnt install it but the file name says it is signed o.o ? Ow man
Related
I have a moto droid, rooted mine the normal way with update.zip and adb but my mom has a eris and wants wifi tether and a faster rom with working youtube app
Can i just download the rooting file update her phone then download rom manager to install recovery image? i dont feel like setting up adb on her computer. i want to flash it to the newest ota rooted rom that is on this site.
bL33d said:
I have a moto droid, rooted mine the normal way with update.zip and adb but my mom has a eris and wants wifi tether and a faster rom with working youtube app
Can i just download the rooting file update her phone then download rom manager to install recovery image? i dont feel like setting up adb on her computer. i want to flash it to the newest ota rooted rom that is on this site.
Click to expand...
Click to collapse
Sure, put your sdcard in your computer, or connect it to your computer with the USB cable and mount the sdcard. Download the PB00IMG.zip with root, flash_image, and recovery.img. Shut the phone down, and then do the VOL DOWN+Power ON to flash PB00IMG to the phone. Once done flashing, go in to the android market and download a terminal emulator. Type these commands:
su
after su, phone should change from sh-3.2$ to sh 3.2#
mount -o rw,remount /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin
chmod 755 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
If you do that, it should allow you to do it without adb on the computer. Just remember to type the 5 commands in the terminal emulator.
I just talked to devs and they told me that It can be done, Just download the rom Manager and install the recovery from there without using adb at all.
You just have to install the root rom first, then you should be able to use the rom manager to install the recovery img, which in my opinion the clockworkmod recovery is a lot better than the RA recovery which is listed in the rom.
thanks guys seemed like it was doable but wanted to double check here first.
I flashed 2.3.4 pudding preroot and looked through all my apps and do not have root and/or root permissions. I installed superuser with apk (of course that wouldnt work) but the rom itself is supposed to come packed with SU. Any ideas? I didnt clean wipe my phone during the flash and I am still running phone with all old apps/unchanged features from before the flash.
Is there anything I missed to get Root permissions onto phone? Ie running code or something else?
Does no one really know... ? I mean wow. :x
eval- said:
Hi guys.. here is a useful little /preinstall for you (attached)
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
The last step is optional (and next-to-last *should* be unnecessary), as you can install Superuser however you like. In fact, if you've installed it, simply typing "/preinstall/su" is another way to root, and you could then mount /system read-write and copy it into /system/bin.
Many thanks to Brandon & The2d for brainstorming this out in a crazy "there's no way it could be possible" rooting session. There were a lot of harder ways... who knew we'd be so lucky! And thanks to Edgan for the great "dosu" =)
You can find fastboot here: http://forum.xda-developers.com/showthread.php?t=1138092
And the preinstall.img file here: http://forum.xda-developers.com/attachment.php?attachmentid=652327&d=1310460219
Click to expand...
Click to collapse
IMO, this is the easiest way to root. If you get an error with the /preinstall/dosu command, just keep going through with the rest like normal and it should work.
If your not bent on having stock gingerbread, then flash Piecrust or alien 3. they are prerooted and optimized.
Alien 3 would be your best bet. Just flash the alien 3 rom and your set. It is stock for the most part and removes some un-necessary bloat which you can get back from the bloat.zip if you want. If you want a new look then flash the alien 3 theme as well. WAAAAY better than stock theme IMO. Not overly flashy and gives the device a up to date look. Motorola needs to work on there GUI a little harder.
Stephen Who said:
I flashed 2.3.4 pudding preroot and looked through all my apps and do not have root and/or root permissions. I installed superuser with apk (of course that wouldnt work) but the rom itself is supposed to come packed with SU. Any ideas? I didnt clean wipe my phone during the flash and I am still running phone with all old apps/unchanged features from before the flash.
Is there anything I missed to get Root permissions onto phone? Ie running code or something else?
Click to expand...
Click to collapse
I had the same issue doing my bros phone, got fed up and put alien on it, then he came back and wanted the alien theme lol. Superuser beta 3 pre-installed into ROM
i love you
Originally Posted by eval- View Post
Hi guys.. here is a useful little /preinstall for you (attached)
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
The last step is optional (and next-to-last *should* be unnecessary), as you can install Superuser however you like. In fact, if you've installed it, simply typing "/preinstall/su" is another way to root, and you could then mount /system read-write and copy it into /system/bin.
Many thanks to Brandon & The2d for brainstorming this out in a crazy "there's no way it could be possible" rooting session. There were a lot of harder ways... who knew we'd be so lucky! And thanks to Edgan for the great "dosu" =)
You can find fastboot here: http://forum.xda-developers.com/show....php?t=1138092
And the preinstall.img file here: http://forum.xda-developers.com/atta...7&d=1310460219
this worked for me i have been looking up 100 different things thanks so much:laugh::laugh::laugh::laugh:
been trying to update to wolfs rom, but lame thing is xrecovery, cant find way to get it to fully working version that allows me to install the rom, instead just wont load up the sdcard
have gotroot access, busybox installed, flashtool works no problem now just this last stage now is getting to the end of my tether
I have got root explorer so can copy over files to system if needs be, but am now stuck, as have already tried the method of copying files over to update xrecovery, also could not see where adb shell is to run the commands that ive seen so am stuck there
any help would be appreciated
What I recomend that you do is flash back to 2.1 using flashtool, then root, install xRecovery, and then follow the instructions in wolfs thread. That's worked for me and many others. Goodluck
Sent from my X10i using XDA Premium App
rm -r /sdcard
mkdir sdcard
chmod 777 sdcard
Click to expand...
Click to collapse
OR
extract APK and copy .
Hello All,
I'm new here. I believe I supposed to write a reply to this thread, but I couldn't. So, sorry to all mods.
Anyway, after applying battery hack files (services.jar & systemUI.apk), my RAZR is now stuck on boot.
However, I can connect my handset to PC and access the shell via ADB. The problem is, silly me, I was so excited that I forgot to backup the services.jar & systemUI.apk in same directory. It's on the sdcard however.
How to mount the sdcard onto the android system, so that I can overwrite the files by original ones from the sdcard?
I'm using XT910, it was AsiaRetail, but I flashed using the latest eu.en.33 & deodexed, which was working fine.
Any helps are appreciated. Thanks.
iman38 said:
Hello All,
I'm new here. I believe I supposed to write a reply to this thread, but I couldn't. So, sorry to all mods.
Anyway, after applying battery hack files (services.jar & systemUI.apk), my RAZR is now stuck on boot.
However, I can connect my handset to PC and access the shell via ADB. The problem is, silly me, I was so excited that I forgot to backup the services.jar & systemUI.apk in same directory. It's on the sdcard however.
How to mount the sdcard onto the android system, so that I can overwrite the files by original ones from the sdcard?
I'm using XT910, it was AsiaRetail, but I flashed using the latest eu.en.33 & deodexed, which was working fine.
Any helps are appreciated. Thanks.
Click to expand...
Click to collapse
when you say stuck on boot, do you mean bootloop?
If you were on deodexed system it should work i don't see why...
Anyway if you have a backup of your file it's fine, if you don't have i'll send it to you in 2hours.
Code:
adb shell
su
cp /sdcard/SystemUI.apk /system/app/
cp /sdcard/services.jar /system/framework/
reboot
No need to mount sdcard it's mounted automatically.
Maybe the change i made, make it unworking on .33. I tried on it before the 1% just with toggle so maybe it's not working.
sevenup30 said:
when you say stuck on boot, do you mean bootloop?
If you were on deodexed system it should work i don't see why...
Anyway if you have a backup of your file it's fine, if you don't have i'll send it to you in 2hours.
Code:
adb shell
su
cp /sdcard/SystemUI.apk /system/app/
cp /sdcard/services.jar /system/framework/
reboot
No need to mount sdcard it's mounted automatically.
Maybe the change i made, make it unworking on .33. I tried on it before the 1% just with toggle so maybe it's not working.
Click to expand...
Click to collapse
Yes, I deodexed using xUltimate 2.4.2 ; Deodexing was successful and my phone was running fine after deodexed.
So my only suspects are the services.jar and systemui.apk
It's not bootloop, it's stuck on the Motorola Animation. Normally, it would vibrate and enter the android, now it's stuck there. But as I said, I can connect using adb and access su.
The sdcard is not mounted (I guess the boot process halted somewhere before it mount the drives automatically).
So, do you know the exact command to mount the sdcard? external sd card in my case.
Btw, if I reflash using the fastboot file, SPDREM_U_01.6.7.2-180_SPU-19-TA-11.2_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_Service1FF_fastboot.xml.zip from droid-developers, will it work? I'm afraid it will make it worse, so I need confirmation before the last resort of re-flashing my phone.
Btw, I was using battery app and tick the 1% hack, it did show 1% decrement, but have it's own notification. If your patch works, then it's great
tia
Try:
Code:
busybox mount -t vfat /dev/block/mmcblk0p1 /sdcard
or
busybox mount -t vfat /dev/block/mmcblk0 /sdcard
or try to fastboot this one:
http://forum.xda-developers.com/showthread.php?t=1747800
might be the same as you mentionned, latest fastboot ICS for EN.EU
sevenup30 said:
Try:
Code:
busybox mount -t vfat /dev/block/mmcblk0p1 /sdcard
or
busybox mount -t vfat /dev/block/mmcblk0 /sdcard
or try to fastboot this one:
http://forum.xda-developers.com/showthread.php?t=1747800
might be the same as you mentionned, latest fastboot ICS for EN.EU
Click to expand...
Click to collapse
Sorry for late replied. I flashed my phone using latest fastboot. At first, it was panicking since it failed in step 6 (system_signed or something) and my phone keep displaying white text of "failed fastboot" even after I powered it down. But with little hope, I tried again and it's succeeded. Thank God the flashing didn't erase anything.
Thanks anyway.
Btw, if I want to do my own mod of those files (1% battery hack), what should I do?
OK, so I have a rooted I9300 and for some reason for the last few weeks I cant update the subinary and titanium wont get root access.
I did many google searches, tried a few thing eg (http://forum.xda-developers.com/showthread.php?t=1900217) , tried rooting again (even though I know Im rooted but nothing works.
So the next thing I want to try is to unroot my phone and root again.
My question is, because I cant access titanium to back everything up,
is there a way to unroot WITHOUT losing all apps and data?
Thanks a lot in advance.
Make nandroid backup and restore apps using titanium when your phone are rooted again.
Use MybackupPro to backup messages/contacts/bookmark/system setting/bookmarks.
Sent from my GT-I9300 using xda app-developers app
Uninstall super su via Google Play and reinstall .
jje
Cant use nandroid. It needs busybox which requests root access.
JJEgan said:
Uninstall super su via Google Play and reinstall .
jje
Click to expand...
Click to collapse
Tried it- it wont uninstall but go back to an earlier version.
Reinstalled the latest version and Im getting the same message.
Root checker app says "This device does not have proper root access".
...just re-root it? Assuming you used CF-Root and will be flashing it again, when CWM runs again and installs the SuperSU ZIP, /system/xbin/su will get overwritten (and get set with the correct permissions).
Else, if whatever reason you don't want to do that, if you have CWM recovery installed, just mount /system, and using ADB delete /system/xbin/su, /system/app/Superuser.apk, /system/bin/.ext and install CWM-SuperSU-v0.96.zip again.
If you don't have CWM, you can use a kernel with an insecure adbd (Perseus kernel has this for Jellybean ROMs, and earlier Siyah and GalaxSih kernels have this for ICS) and delete /system/xbin/su and /system/app/Superuser.apk. You'll have to manually install SuperSU from the ZIP.
qwerty12 said:
...just re-root it? Assuming you used CF-Root and will be flashing it again, when CWM runs again and installs the SuperSU ZIP, /system/xbin/su will get overwritten (and get set with the correct permissions).
Else, if whatever reason you don't want to do that, if you have CWM recovery installed, just mount /system, and using ADB delete /system/xbin/su, /system/app/Superuser.apk, /system/bin/.ext and install CWM-SuperSU-v0.96.zip again.
If you don't have CWM, you can use a kernel with an insecure adbd (Perseus kernel has this for Jellybean ROMs, and earlier Siyah and GalaxSih kernels have this for ICS) and delete /system/xbin/su and /system/app/Superuser.apk. You'll have to manually install SuperSU from the ZIP.
Click to expand...
Click to collapse
I tried rooting again- didn't change anything.
I do have CWM.
Tried using ADB, but it requests root access and fails to get it...
tomerstern said:
I do have CWM.
Click to expand...
Click to collapse
Good, ADB will be running as root in CWM by default. Boot into recovery mode, go to mounts and storage, and select Mount /system.
If you don't already have ADB setup and the correct drivers installed (if you already have Kies installed then you have the drivers installed). do the following. You can check, if you wish, by seeing when you connect your phone in recovery - you should have a SAMSUNG Android ADB Device under SAMSUNG Android Phone or an Android Debugger Bridge device in Device Manager. If not:
Download http://dl.google.com/android/repository/platform-tools_r14-windows.zip and extract the three files adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll to a place of your choosing
install the drivers: http://www.mediafire.com/?2243ouw1701zp8l (Extracted from Kies_2.5.0.12094_27_11.exe)
disconnect and reconnect your phone
Go to the folder where you have adb installed in the Command Prompt, and run "adb shell". Run the following commands:
Code:
rm /system/app/Superuser.apk
chattr -i /system/xbin/su [in case Survival Mode is turned on in SuperSU]
rm /system/xbin/su
rm /system/bin/su [ignore this one if it throws an error]
rm -r /system/bin/.ext
That should unroot your phone.
Go to "Install ZIP from sdcard" and choose to install a zip from the internal sdcard.
Exit out of the root shell (Ctrl+C or, alternatively, "exit" and you'll be sent back to the command prompt) on your computer and download the SuperSU ZIP.
Go back to the command prompt and type this "adb push " (including the space) and drag the CWM-SuperSU-v0.96.zip onto the command prompt window, add a space and type "/data/media". You should have something like "adb push <path to CWM-SuperSU-v0.96.zip> /data/media"
This should put the SuperSU ZIP onto the root of your internal memory card. Choose go back on your phone and select to install a ZIP from the internal memory card again. You should see CWM-SuperSU-v0.96.zip. Install it, reboot, update SuperSU from the Play Store and run SuperSU from the app drawer. You should get a prompt asking you to update the su binary. Do so.
Grab Android Terminal Emulator on the Market, and run "su". If all went well, SuperSU should ask you for permission. Grant it and if the $ turned into a # and the command "id" says uid=0 (root) then you're rooted!
OK, Im really sorry and embarrassed to say that I got confused with my tab 10.1.
I Do not have CWM installed.
Tried installing it now and could not. I stay on odin mode and I dont get the CWM menu...
I guess at this stage when my root is screwed I cant install CWM anymore.
What can I do now?
Thanks again and sorry for the confusion..
tomerstern said:
Tried installing it now and could not. I stay on odin mode and I dont get the CWM menu...
I guess at this stage when my root is screwed I cant install CWM anymore.
Click to expand...
Click to collapse
Flashing CF-Root should always get you CWM as it's done through ODIN, which does not care if your phone is rooted or not. When you're flashing CF-Root, make sure the auto reboot option remains ticked. If your phone doesn't boot into CWM after ODIN reboots it, then take note of the following:
Chainfire said:
- NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
Click to expand...
Click to collapse
qwerty12 said:
Go to the folder where you have adb installed in the Command Prompt, and run "adb shell". Run the following commands:
Code:
rm /system/app/Superuser.apk
chattr -i /system/xbin/su [in case Survival Mode is turned on in SuperSU]
rm /system/xbin/su
rm /system/bin/su [ignore this one if it throws an error]
rm -r /system/bin/.ext
Click to expand...
Click to collapse
OK, Im now in the mounts and storage folder insider CWM.
ADB interface is installed on device manager.
II dont understand what to press and where to run these commands.
tomerstern said:
OK, Im now in the mounts and storage folder insider CWM.
ADB interface is installed on device manager.
II dont understand what to press and where to run these commands.
Click to expand...
Click to collapse
Under the mounts and storage option, select mount /system. It will change to "unmount /system" if selected correctly.
The commands are run from an "adb shell" session, which you can get to by doing this:
Extract those three ADB files from that platform-tools ZIP to a folder somewhere (I chose C:\adb out of randomness). Open that folder and while holding down the shift key, right-click a blank, white area in the folder and select "Open command window here". You can then type "adb shell", which will allow you to run those commands.
qwerty12 said:
Good, ADB will be running as root in CWM by default. Boot into recovery mode, go to mounts and storage, and select Mount /system.
Click to expand...
Click to collapse
There isnt mount system there. I see unmount system.
I see mount data, preload etc.
OK, that's fine, you may move on to running those commands.
Two problems:
1. running "chattr -i /system/xbin/su"
resulted in a "chatter not found" message.
2. Trying to push the su zip resulted in this message: "error: device not found".
tomerstern said:
"chattr -i /system/xbin/su"
Click to expand...
Click to collapse
If rm worked on /system/xbin/su, then ignore it as you don't need it anyway.
2. Trying to push the su zip resulted in this message: "error: device not found".
Click to expand...
Click to collapse
Reconnect the phone and try again?
not working after numerous attempts.
Can I Start the phone and move the zip file manually with a micro sd cable? If not, what else?
tomerstern said:
Can I Start the phone and move the zip file manually with a micro sd cable? If not, what else?
Click to expand...
Click to collapse
That should be fine
moved it to internal memory and after shutdown, power+home+volume up wont take me to cwm anymore but to android system recovery.
Why? How do I get back to cwm? Install it again with Odin?
BY THE WAY, I can still see supersu is installed on my device. Does it mean what we did did not work?
OK, I can confirm this method works
I just installed the zip of the supersu and now Ive got full root privileges.
The reason I couldnt get into cwm was that for some reason I get a short android upgrade each time I boot up. This upgrade deletes cwm. Thats why I found out that I need to install CWM and then immidiately press power-volume up-home, before i let the device power up.
I want to give a big thanks to qwerty12 for the help and much needed patience.