My original problem is that I ran the OTA upgrade of Froyo like an idiot the day I bought my Desire here in India. Now, I am trying to downgrade the HBOOT so that I can root my device.
Now the issue is that I am not able to follow the procedure to downgrade the HBOOT as I am unable to push the flash_image and the mtd0.img into the data folder as I get an error "remount failed: Operation not permitted" when I try to remount.
I have tried to access shell and do a 'su' which again comes up with the 'access denied' message.
Can anyone help me get rid of the access issue so that I can downgrade the HBOOT and root my device?
Hello all,
So, I recently rooted my Epic 4G using the following thread as a guide: http://forum.xda-developers.com/showthread.php?t=770388
The root worked great, but ClockwordMod isn't quite working as planned.
If I boot the phone holding Power+VolDown+Camera it boots into ClockwordMod, but if I use ROM Manager to try and reboot into ClockworkMod and backup my current ROM, it just takes me to the stock Android recovery screen.
Any ideas as to why this is happening?
Help would be greatly appreciated!
Also, when I download ClockworkMod through ROM Manager, it creates an update.zip on the root of my SD Card, but when I try flashing it, it won't go through.
Also tried manually entering Clockwork and flashing it there, and it went through, but ROM Manager still doesn't work.
You need the recovery redirector. The easiest way to get it is to run the one-click root and recovery or install a rom with the redirector in it.
The other way is to download the one-click zip and unzip it on your sdcard. Copy the files below from the one-click to the same place on your phone.
/system/bin/recovery
/system/bin/recoveryfiles/
/system/bin/recoveryres/
Then type the following commands into a terminal program.
busybox chmod -R 0755 /system/bin/recoveryfiles/*
busybox chmod -R 0755 /system/bin/recoveryres/*
chmod 0755 /system/bin/recovery
sync
DiGi760 said:
You need the recovery redirector. The easiest way to get it is to run the one-click root and recovery or install a rom with the redirector in it.
The other way is to download the one-click zip and unzip it on your sdcard. Copy the files below from the one-click to the same place on your phone.
/system/bin/recovery
/system/bin/recoveryfiles/
/system/bin/recoveryres/
Then type the following commands into a terminal program.
busybox chmod -R 0755 /system/bin/recoveryfiles/*
busybox chmod -R 0755 /system/bin/recoveryres/*
chmod 0755 /system/bin/recovery
sync
Click to expand...
Click to collapse
Followed the second part of what you suggested (manually copying the files, since the one-click script didn't work when I first rooted), and it still boots into the Android recovery.
After rebooting I verified the files were still in /system/bin and they were.
Although, looking at that script, it first checks that the OS version is Froyo.
Is the fact that I'm still on stock (rooted) Eclair the problem?
which one click root program yall talking about ... im stuck here to
Hi everyone! I got the Nitro yesterday and I have tried EVERY possible method under the sun to get root onto my 2.3.5 V10J stock firmware. I am generally good at stuff, but the unbricking tutorial really confuses me. Is there any other way to just get CWM onto the phone and then install a pre-rooted ROM? Or an easier way to root? I tried superoneclick a 100 times, and it just behaves read only. does not allow the software to access root. This is the error I get with all rooting scripts!
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
adb server is out of date. killing...
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
failed to copy 'files\zergRush' to '/data/local/tmp/./zergRush': Permission deni
ed
--- correcting permissions
Unable to chmod /data/local/tmp/zergRush: No such file or directory
--- executing zergRush
./data/local/tmp/zergRush: not found
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
failed to copy 'files\busybox' to '/data/local/tmp/./busybox': Permission denied
--- correcting permissions
Unable to chmod /data/local/tmp/busybox: No such file or directory
--- remounting /system
/data/local/tmp/busybox: not found
--- checking free space on /system
failed to copy 'files\makespace' to '/data/local/tmp/./makespace': Permission de
nied
Unable to chmod /data/local/tmp/makespace: No such file or directory
./data/local/tmp/makespace: not found
--- copying busybox to /system/xbin/
/data/local/tmp/busybox: cannot open for read: No such file or directory
--- correcting ownership
Unable to chmod /system/xbin/busybox: Read-only file system
--- correcting permissions
Unable to chmod /system/xbin/busybox: Read-only file system
--- installing busybox
--install: applet not found
rm failed for /data/local/tmp/busybox, No such file or directory
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
rm failed for *, No such file or directory
--- rebooting
Apparently there is atm no way to get cwm or cwm recovery on your phone w/out going through oh no!'s rom which as a prerequisite you must follow the unbricking method.
If you want go to my profile and check out my recent posts in the nitro general subforum and youll see my little journey....which others were annoyed with ...lmao.
I am currently rooted, running stock ics and love it. I have no issues phone runs near perfect.
I did not "unbrick" my phone and just flashed an older rom (v18) and rooted.
Sparky's root method is the only method that will root this phone via ics.
I made a thread explaining in detail some steps that were not mentioned.
Dont bother with doomlord, oneclick.
Since the tapatalk search function sucks balls use the xda search function from the actual browser.
Hope that helps. Maybe someone else will chime in.
Dont fear the unbrick.
Take your time
Read slow and also read through other peoples posts and what they did wrong, how they remedied it blah blah...
Dont take any short cuts unless for sure, you know exactly what you are doing.
Make sure you have everything ready and have read through prior to doing it.
Nothing to fear flashing is pretty straight forward.
Just take your time.
:beer:
Sent from my LG-P930 using Tapatalk 2
I went from Stock ATT 2.5.6 V10J to ATT STOCK V10F .Using [GUIDE] Unbrick, Root, And Install CWM by mattman86 . Its long but doable its not even that long really .O tip uninstall all the drivers you might have installed and use the one that come with the unbricking pack ,its the key to the whole thing. Im in CM10 Nightly now .Good luck and dont get frustrated its rootable its just not a one click root.
Just keep trying to run the root. I used super one click and it took me at least 20-30 attempts to successfully root. If it asks you if your version is 2 or higher or fails to push any files to the phone, the root will not take. Just reboot the phone and keep trying.
Try using viperMOD PrimeTime v4.6, that's a lot easier and faster, despite what everyone else says, you can root 10j.
Good Luck
I am trying to install CWM on my bootloader locked Xperia S.
It's all went smoothly; downgraded to gingerbread, run the rooting process, currently on a confirmed rooted ICS. Ran RecoverX and for all intentions it installs correctly with no errors. I restart my phone and tap the Sony logo numerous times... and I've tried a countless amount of times now but it just continues on loading stock ICS. It's really starting to get on my nerves now. Does anyone have any idea why it's happening? or is there any adb commands to check if CWM is installed?
RecoverX says accept any SuperUser prompts on the screen, but none appear.
RecoverX log:
Starting adb...
Wait for the device...
Check if the device is correctly rooted...
Check if busybox is installed...
Push files...
Unzip files...
Chmod files to 755...
Run installation script...
Clear temp folder...
Installation complete
Click to expand...
Click to collapse
I've also tried the older adb method via the install.bat but that says this:
Step1 : Waiting for Device.
=============================================
OK
=============================================
Step2 : Sending some files.
=============================================
mkdir failed for /data/local/tmp/cwm, Not a directory
failed to copy 'chargemon' to '/data/local/tmp/cwm': Not a directory
failed to copy 'charger' to '/data/local/tmp/cwm': Not a directory
failed to copy 'recovery.tar' to '/data/local/tmp/cwm': Not a directory
failed to copy 'sh' to '/data/local/tmp/cwm': Not a directory
failed to copy 'step3.sh' to '/data/local/tmp/cwm': Not a directory
=============================================
Step3 : Setting up files system partition.
=============================================
Unable to chmod /data/local/tmp/cwm/sh: Not a directory
Unable to chmod /data/local/tmp/cwm/step3.sh: Not a directory
sh: /data/local/tmp/cwm/step3.sh: not found
rm failed for /data/local/tmp/cwm, Not a directory
Finished!
Click to expand...
Click to collapse
Even though I clearly have access to my phone via adb. Because it's been rooted... Grr!
Nobody have any idea? Spent around 12 hours trying to sort it out yesterday so I'm completely out of things to try
For search purposes I ended up fixing it by updating the flashtool drivers for the phone (ticked every Xperia S checkbox). Well, it was either that or perhaps updating BusyBox, which is highly unlikely as I tried pretty much every version of it yesterday.
I am not responsible for whatever may happen to you or your device when using this, Run this at your own risk!!
Requires unlocked bootloader!
Based on SuperSU - v4.46 (the binary updates from within the app later on)
I put together root installer script that comes with SU-binary/App with a insecure boot.img, everything is done over adb shell since we don't have a recovery right now but i will be working on it and already booted CWM
For current firmware:
LMY47D - root-boot
For past firmware:
LRX21V - root-boot
For past firmware:
LRX21M - root-boot
crappy video but simple demonstration :good:How to install:
Download the zip depending on your Nexus Player's firmware than extract & run root-boot.bat (Other operating system support coming soon for the installer script) Made on windows 7
Follow and read the on screen instruction carefully
Click to expand...
Click to collapse
SU app and binarys gets installed to /system/* directory's, The insecure boot.img gets installed to be able to access root adb shell and install those binarys
The root-boot boot.img is temporarily booted once during this process on the first boot of installation, it does not flash the boot.img
The previous boot.img before the installation is restored after SU is installed
Click to expand...
Click to collapse
Thanks @Chainfire for Superuser
My Donation Box
Troubleshooting:
Check to make sure your device gets picked up in adb before running the script - - - ADB Drivers
This tool uses an unlocked bootloader and i have not unlocked mine yet, does unlocking the bootloader wipe the device? - - - Yes unlocking the bootloader will wipe the device
After fastboot flashed the boot.img than rebooted to the home screen i continued the the script like the installation steps said but it returned "device not found" - - - As long as it shows transferring files a few seconds after than its fine, adb restarts at that moment which will than return "device not found" than it reconnects and transfers. if fastboot flashed than rebooted fine than adb shouldn't have an issue
Help! Something went wrong and im bootlooping but i dont want to loose all my saved data - - - Everything is fine, Download the factory zip from here for your android version than extract the zip and retrieve the system.img and copy it into a folder that contains adb/fastboot and boot your device into fastboot mode and do "fastboot flash system system.img" doing it this way wont wipe your "/data" partition leaving everything intact but will restore the system back to its defaults
(If you were to run the factory zip as an update than it would format everything)
I installed SU with this method but cant use adb commands on my device - - - Go into "Settings>About" and click on "Build" 7 times very fast and it will enable "Developer options" in the settings menu, Go back to the settings menu and open developer options (You may need to reboot if it doesnt show up immediately) and enable the "USB debugging" option
Ill be updating this as new version of lollipop get released
support for both firmwares are up, any issues let me know i tested them both though and everything looked okay
Reuploading, had a minor issue
Edit: LRX21M link back up, let me know if there's any issues
Whoa...
Let the games begin....
ftarules said:
Whoa...
Let the games begin....
Click to expand...
Click to collapse
yeup, after recovery i have a few system modification ideas for the settings apk i was considering
i do have other devices to worry about though so it may take some time
bunchies said:
I put together root installer script that comes with SU-binary/App with a insecure boot.img, everything is done over adb shell since we don't have a recovery right now but i will be working on it and already booted CWM
For current firmware:
LRX21V - root-boot
Click to expand...
Click to collapse
Working well, Thank you, after semi-manually adapting for working from Linux Mint.
I don't have permission to do "adb logcat" or "adb shell logcat" anymore though, unless I restart adbd as root.
mikereidis said:
Working well, Thank you, after semi-manually adapting for working from Linux Mint.
I don't have permission to do "adb logcat" or "adb shell logcat" anymore though, unless I restart adbd as root.
Click to expand...
Click to collapse
Use adb shell
than type su to use root adb shell
Since running the script everything seems all good except for using voice search. Anybody else having issues where voice search just closes?
Update: Erased and manually flashed the V firmware as I was on M and now it appears to be working correctly, not sure if this is going to be a problem with people stuck on M for now but you may want to think of upgrading your fimware.
Getting ADB device not found.. Anywhere I can download drivers from? I have the latest android-sdk
xReaper7x said:
Getting ADB device not found.. Anywhere I can download drivers from? I have the latest android-sdk
Click to expand...
Click to collapse
http://developer.android.com/sdk/win-usb.html
at what point, adb will restart about half way through and it shows it cant connect to device but it really is
but if your in fastboot and it cant connect to the device than thats an issue
i should note this in the OP
Subscribed for later. Awaiting someone else to port a recovery for this, I am lazy.
Snuzzo said:
Subscribed for later. Awaiting someone else to port a recovery for this, I am lazy.
Click to expand...
Click to collapse
lol Snuzzo :good: recovery coming soon
Links are down. Does anyone have a mirror of 21V?
prsterero said:
Links are down. Does anyone have a mirror of 21V?
Click to expand...
Click to collapse
Links are up, hosted on android file host
Can mirror in a bit if needed
bunchies said:
Links are up, hosted on android file host
Can mirror in a bit if needed
Click to expand...
Click to collapse
Looks like it's working now. Before I was getting that the file couldn't be found. Thanks I appreciate you releasing this I just got it unlocked so time to root and have some fun expanding the storage to 128gb
Alright so I just got around to running the script, and none of the commands work after booting back up. There's a failure for every rmdir and mkdir command that's used, so the device doesn't get rooted. I tried doing a adb remount, but the device isn't allowing that.
________________________________________________________
root-boot: By Bunchies @xda
________________________________________________________
________________________________________________________
Power off/unplug the device, hold the power button while
plugging in the device until you see the google logo and
than let go to enter fastboot mode
________________________________________________________
________________________________________________________
Plugin the device to a PC using a usb cable
________________________________________________________
Press any key to continue . . .
waiting for ADB
target reported max download size of 536870912 bytes
sending 'boot' (5424 KB)...
OKAY [ 1.357s]
writing 'boot'...
OKAY [ 1.515s]
finished. total time: 2.876s
rebooting...
finished. total time: 0.602s
When boot completes
and you see the launcher
Press any key to continue . . .
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
rm: /system/bin/install-recovery.sh: Read-only file system
mkdir failed for /system/app/SuperSU, Read-only file system
mkdir failed for /system/bin/.ext, Read-only file system
failed to copy 'SuperSU/SuperSU.apk' to '/system/app/SuperSU/': Is a directory
failed to copy 'x86/su' to '/system/xbin/su': Read-only file system
failed to copy 'x86/supolicy' to '/system/xbin/supolicy': Read-only file system
failed to copy 'x86/libsupol.so' to '/system/lib/libsupol.so': Read-only file sy
stem
failed to copy 'x86/99SuperSUDaemon' to '/system/etc/init.d/99SuperSUDaemon': Re
ad-only file system
failed to copy 'x86/install-recovery.sh' to '/system/etc/install-recovery.sh': R
ead-only file system
cp: system/xbin/su: No such file or directory
cp: system/xbin/su: No such file or directory
cp: system/xbin/su: No such file or directory
cp: /system/xbin/sugote-mksh: Read-only file system
ln: /system/bin/su: Read-only file system
ln: /system/bin/install-recovery.sh: File exists
rm: /system/bin/app_process: Read-only file system
ln: /system/bin/app_process: File exists
mv: rename /system/bin/app_process32 to /system/bin/app_process32_original: Read
-only file system
ln: /system/bin/app_process32: File exists
cp: /system/bin/app_process32_original: No such file or directory
Unable to chmod /system/app/SuperSU: No such file or directory
Unable to chmod /system/app/SuperSU/SuperSU.apk: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/lib/libsupol.so: No such file or directory
Unable to chmod /system/bin/.ext: No such file or directory
Unable to chmod /system/bin/.ext/.su: No such file or directory
Unable to chmod /system/etc/init.d/99SuperSUDaemon: No such file or directory
Unable to chmod /system/xbin/daemonsu: No such file or directory
Unable to chmod /system/xbin/sugote: No such file or directory
Unable to chmod /system/xbin/sugote-mksh: No such file or directory
Unable to chmod /system/etc/install-recovery.sh: No such file or directory
Unable to chmod /system/xbin/supolicy: No such file or directory
Unable to chmod /system/bin/app_process32_original: No such file or directory
Unable to chmod /system/bin/app_process_init: No such file or directory
chcon: Could not label /system/xbin/su with ubject_r:system_file:s0: No such
file or directory
chcon: Could not label /system/bin/.ext/.su with ubject_r:system_file:s0: No
such file or directory
chcon: Could not label /system/lib/libsupol.so with ubject_r:system_file:s0:
No such file or directory
chcon: Could not label /system/etc/init.d/99SuperSUDaemon with ubject_r:syste
m_file:s0: No such file or directory
chcon: Could not label /system/bin/sh with ubject_r:system_file:s0: Read-onl
y file system
chcon: Could not label /system/xbin/sugote with ubject_r:zygote_exec:s0: No
such file or directory
chcon: Could not label /system/xbin/supolicy with ubject_r:system_file:s0: N
o such file or directory
chcon: Could not label /system/xbin/sugote-mksh with ubject_r:system_file:s0:
No such file or directory
chcon: Could not label /system/bin/app_process32_original with ubject_r:zygot
e_exec:s0: No such file or directory
chcon: Could not label /system/bin/app_process_init with ubject_r:system_file
:s0: No such file or directory
Finished, you can now exit the installer
Press any key to continue . . .
Edit: Fixed it! I had to manually do "adb root" then "adb remount" and remount succeeded that time and I was able to run the rest of the script and saw all the file transfers.
prsterero said:
Alright so I just got around to running the script, and none of the commands work after booting back up. There's a failure for every rmdir and mkdir command that's used, so the device doesn't get rooted. I tried doing a adb remount, but the device isn't allowing that.
Edit: Fixed it! I had to manually do "adb root" then "adb remount" and remount succeeded that time and I was able to run the rest of the script and saw all the file transfers.
Click to expand...
Click to collapse
Glad to hear that!
bunchies said:
Glad to hear that!
Click to expand...
Click to collapse
The first time around I got into the bootloop so I had to start over. Second time and it worked now it seems that I can't get apps to install through the adb install command. I'm mainly trying to get es file explorer and stick mount so I can use an external flash drive. Is it possible that the root method somehow nuked this functionality? I've already restarted the adb server numerous times, rebooted the player, turned debugging off and back on, etc. Even after all that it just sits after displaying the transfer rate and never finishes.
Edit: Nevermind. Looks like this issue also goes back to having to do adb root and adb remount. Gotta do it for everything apparently
prsterero said:
The first time around I got into the bootloop so I had to start over. Second time and it worked now it seems that I can't get apps to install through the adb install command. I'm mainly trying to get es file explorer and stick mount so I can use an external flash drive. Is it possible that the root method somehow nuked this functionality? I've already restarted the adb server numerous times, rebooted the player, turned debugging off and back on, etc. Even after all that it just sits after displaying the transfer rate and never finishes.
Edit: Nevermind. Looks like this issue also goes back to having to do adb root and adb remount. Gotta do it for everything apparently
Click to expand...
Click to collapse
Weird, windows 8?