HTC Inspire 4G - AT&T
Android - Stock GB 2.3.5 + HTC Sense 3.0
Build - 3.20.502.52
PC OS - Windows XP Pro SP3
Method - Easy Ace Root Tool
Noob - Yes
Problem - Bootloader unlock successfully achieved, but installation of BusyBox, Clockworkmod, and SuperUser interrupted during process.
Text from Post-Unlock on shown below. Trouble Areas Colored Red
Summary of Problem according to Tool - "Parameter Format not correct," "Read-Only file system," and "No such file or directory"
USB Debugging and Unknown Sources enabled when errors occur
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
< waiting for device >
sending 'recovery' (3554 KB)... OKAY [ 0.641s]
writing 'recovery'... OKAY [ 0.953s]
finished. total time: 1.594s
rebooting...
finished. total time: 0.297s
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Make sure that USB debugging is enabled and charge only is set as default
Achieving Temp Root
cannot stat '/tools/tmp/fre3vo': No such file or directory
Unable to chmod /data/local/tmp/fre3vo: No such file or directory
/data/local/tmp/fre3vo: not found
Pushing Busybox, SU and Superuser
1 KB/s (536 bytes in 0.312s)
1829 KB/s (380532 bytes in 0.203s)
1906 KB/s (1372660 bytes in 0.703s)
Trying to gain Perm Root
mount: permission denied (are you root?)
/system/xbin/busybox: cannot open for write: Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
failed to copy 'tools\su\su' to '/system/bin/su': Read-only file system
failed to copy 'tools\su\Superuser.apk' to '/system/app/Superuser.apk': Read-onl
y file system
Unable to chmod /system/bin/su: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
FIND: Parameter format not correct
rm failed for EasyAceRoot.cmd, No such file or directory
Perm Root achieved...
I too am looking for the answer. I'll edit this post if I find something
If CWM would install, that wouldn't be a problem
Scozzar said:
I too am having this issue at the moment. The bootloader is unlocked, but I will not get perm root, even though it says it was achieved...
EDIT: Turning off Fastboot yields different results. But still no SuperSU.
EDIT2: I GOT IT! Basically, I downloaded the latest SuperSU .zip off XDA, put it on the phone, then flashed it in CWM. SuperSU now appears as an app!
Click to expand...
Click to collapse
I'll try turning off fastboot, but I can't get CWM to install at the moment either. SuperSU and Busybox also can't install.
Again, I'll try turning fastboot off and see how it behaves.
Prestige0813 said:
I'll try turning off fastboot, but I can't get CWM to install at the moment either. SuperSU and Busybox also can't install.
Again, I'll try turning fastboot off and see how it behaves.
Click to expand...
Click to collapse
What have you done? Also, you can't turn off fastboot; it's a mode selected from the bootloader. Do you mean ADB? Turning that off won't do anything either, other than making your phone's system inaccessible from the computer.
Scozzar said:
Fastboot, as in the check box in the stock ROM. You can't get into bootloader with it on. Also, if I was able to flash a new ROM, does that mean busybox is installed?
Click to expand...
Click to collapse
Depends on the ROM.
Scozzar said:
V2 Oxygen JB is what I'm using.
Click to expand...
Click to collapse
Er, I don't know for every ROM. If it's a custom ROM, probably. If you're rooted (and again, if you're using a custom ROM, you probably are), you can always install it from the play store.
Update:
First off, I've already downloaded the SuperSU App from Google Play, and it's failed to obtain root abilities, so a perm root is not being acheived.
Also, I've downloaded the latest SuperSU via PC, and it's ready to go once I manage to successfully install CWM (however, if the Ace Root Kit succeeds, then using CWM to install root isn't a needed method)
I've tried continuing the process with the Fastboot setting disabled, and I didn't see any difference in the end result. It seems that recovery is successfully written, but it doesn't succeed in installing SuperSU, CWM, or busybox.
On another note, I've downloaded the busybox installer app from Google Play, and it states the phone is rooted; but runs into errors when I attempt to install (regardless of the version I select). I've run two root checking apps, and both say that the phone is not rooted.
In short, All I've been able to achieve is getting the Boot Loader unlocked.
Can you flash recovery manually from fastboot?
New Update
I just found that CWM is in fact installed. I did not realize until just now that from the HTC bootloader I had to select recovery to access it.
I placed the SuperSU.zip on the phone and installed it via CWM, as scozzar had suggested, and the phone is now rooted (verified by two root checking apps)!
From there I installed busybox via Google Play with no hiccups.
I apologize for not trying this sooner I hope that others find success. The Inspire's a great phone, and now I've made mine even better!
Yess
bananagranola said:
Can you flash recovery manually from fastboot?
Click to expand...
Click to collapse
Yes! here is the tutorial
1- Download Android.zip and unzip it
2- make a folder called "Android" in C:/ like that: C:/Android.
3- put inside of the folder Android the files: adb.exe, fasttboot.exe, AdbWinApi.dll and the recovery.img
4- go to cmd and write:
cd \Android
fastboot flash recovery recovery.img
READY! now you have a CWM Recovery
Sorry for my bad english
Related
okay so I have tried installing clockwork too many times to count and it flat out will not install. i have gotten a series of errors, but have just today been able to keep a consistent error. I downloaded one click clockworkmod 2.5.1.0. plugged in my device, extracted to my desktop and ran both bat files. This is a copy of the cmd prompt window:
remove stock recovery patcher
mount: operation not permitted
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system-recovery-from-boot.p, Read-only file system
copy kernel and flasher
2043 KB/s <313888 bytes in 0.150s>
failed to copy 'zImage' to '/sdcard/zImage': Permission denied
flashing kernel
RedBend Update Agent 6,1,14,1
and then it goes on through there... bottom line, it looks like i don't have permissions for the install. and i have already tried remounting rw through adb shell, it comes back and say remounting and then thats it. and ideas? i can give the reset of the scripting in cmd prompt if needed. Thanks in advance.
4nic8
dude theres like 10 other threads on this page about the same exact thing... and this doesn't go in this forum!
Download rom manager from the market and. ...that would do it for u automatically....... and yes pls next time try to search all the forums before posting
Sent from my SPH-D700 using XDA App
Hello all.
I looked and can't find but is there a rooted 1.55.531.3 rom for the device anywhere.
Rooted the phone tried the ICS from sensation and kinda want to go back but not unroot.
I could send you my recovery if you have the ability to flash
rooted 1.55.531.3 with clockwork recovery and SU
M9x3mos said:
Hello all.
I looked and can't find but is there a rooted 1.55.531.3 rom for the device anywhere.
Rooted the phone tried the ICS from sensation and kinda want to go back but not unroot.
Click to expand...
Click to collapse
yeah, what you are looking for doesn't exist at the moment. i too thought about making a nandroid of the the new ROM for people to flash, but since the new setup comes with a new radio, new kernel, new HBOOT, etc., i'm not sure how it would fly if someone just flashed the nandroid?
Hboot n radio would be the only thing missing... Kernels sits in recovery....
rooted 1.55.531.3 with clockwork recovery and SU
I know I made a flashable package out of the Google Talk apk file, and either did or meant to make some out of the other apps in it - I'm not sure which thread it's in.
I can check later and link it. Not sure what else anyone did with it, if wifi calling wasn't pulled forward from it I'll have a package for that sometime soon anyway.
I also never did get a chance to check what the gps changes were I remember being in it.
Edit:
Link to Gtalk flashable zip package from that update.
Sent from my Bulletproof_Doubleshot using xda premium
nlarge said:
I could send you my recovery if you have the ability to flash
rooted 1.55.531.3 with clockwork recovery and SU
Click to expand...
Click to collapse
Do you have the stock rom for 1.55.531.3 that I can flash on my mt4gs? I would really appreciate it
http://forum.xda-developers.com/showthread.php?t=1484679
http://forum.xda-developers.com/showthread.php?t=1433805
It would be flashed as if restoring a nandroid. I would flash the above link. If you really want it I can send it
rooted 1.55.531.3 with clockwork recovery and SU
Thanks. Okay, this is where I am:
Unlocked bootloader with htcdev
s-on
hboot 1.45.0013
software 1.55.531.3
Would like to achieve root so that I can flash custom roms/use titanium backup. From what I can tell, nlarge was able to accomplish this. (http://forum.xda-developers.com/showthread.php?t=1474933&page=6). However, couldn't post on that thread because I have less than 10 posts....sorry.
Cannot use temproot (FR3VO) method because says needs s-off and/or adb mount issue:
An error occurred while running the exploit (-1) (errno: 22)
c:\Android>adb wait-for-device
c:\Android>adb remount
remount failed: Operation not permitted
c:\Android>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
c:\Android>adb shell mount -oremount,suid /dev/block/mmcblk0p23 /data
mount: Operation not permitted
c:\Android>adb shell mkdir /vendor/bin
mkdir failed for /vendor/bin, Read-only file system
c:\Android>adb shell chown root.shell /vendor/bin
Unable to chmod /vendor/bin: No such file or directory
c:\Android>adb shell chmod 755 /vendor/bin
Unable to chmod /vendor/bin: No such file or directory
c:\Android>adb push ./sqlite3 /vendor/bin
cannot stat './sqlite3': No such file or directory
c:\Android>adb push ./su /vendor/bin
cannot stat './su': No such file or directory
c:\Android>adb push ./busybox /vendor/bin
cannot stat './busybox': No such file or directory
c:\Android>adb shell chown root.shell /vendor/bin/su
Unable to chmod /vendor/bin/su: No such file or directory
c:\Android>adb shell chown root.shell /vendor/bin/busybox
Unable to chmod /vendor/bin/busybox: No such file or directory
c:\Android>adb shell chown root.shell /vendor/bin/sqlite3
Unable to chmod /vendor/bin/sqlite3: No such file or directory
c:\Android>adb shell chmod 6555 /vendor/bin/su
Unable to chmod /vendor/bin/su: No such file or directory
c:\Android>adb shell chmod 4555 /vendor/bin/busybox
Unable to chmod /vendor/bin/busybox: No such file or directory
c:\Android>adb shell chmod 755 /vendor/bin/sqlite3
Unable to chmod /vendor/bin/sqlite3: No such file or directory
c:\Android>adb shell busybox --install -s /vendor/bin
busybox: permission denied
c:\Android>adb shell sync
c:\Android>adb shell chmod 6555 /vendor/bin
Unable to chmod /vendor/bin: No such file or directory
c:\Android>adb install ./Superuser.apk
can't find './Superuser.apk' to install
c:\Android>pause
Press any key to continue . . .
So, I understand, permission denied/operation not permitted, I assume because I don't have root.
When I look at superuser, it says "su binary voutdated" and when I tap to check for updates, automatic update fails and error message "su was not updated. A zip file (su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary.
Can't boot into recovery mode, phone just sits on mytouch 4g slide screen. Again, I assume because no root. Same thing happens if I try to factory reset, just stays on the mytouch 4g slide screen.
Anyone have any suggestions? I am going crazy trying to get this phone to work. I would really appreciate the help!
Flash clock work recovery... I think I linked it somewhere... Or Google will help
rooted 1.55.531.3 with clockwork recovery and SU
Now find yourself a nice recovery image (CWM), boot phone into fastboot mode, "fastboot flash recovery recovery.img".
When this is done you will have a free and open recovery image, and can use that to write/install the su binary and apk (either with flashable zip or through adb shell, either will work).
rooted 1.55.531.3 with clockwork recovery and SU
nlarge said:
Now find yourself a nice recovery image (CWM), boot phone into fastboot mode, "fastboot flash recovery recovery.img".
When this is done you will have a free and open recovery image, and can use that to write/install the su binary and apk (either with flashable zip or through adb shell, either will work).
rooted 1.55.531.3 with clockwork recovery and SU
Click to expand...
Click to collapse
Have tried flashing new and old versions of cwr and the earlier links from blue with no luck. Trying to do it manually through the computer with fastboot, results in 'waiting for device' message. All drivers installed, usb debug, have tried charge only/mount as disk drive options. Neither work. Have tried flashing manually by converting .img to .zip without compression and flashing through phone. No error message but nothing changes.
Cannot use cwm to flash because not error message says not rooted. Not sure what else to do. BTW, you guys are awesome for helping me out Thanks!
Put your phone in fastboot. Pull battery, hold down and power then try again
rooted 1.55.531.3 with clockwork recovery and SU
How to fastboot flash recovery
Return to Contents Page - doubleshot Developers Reference
Boltinghouse said:
Have tried flashing new and old versions of cwr and the earlier links from blue with no luck. Trying to do it manually through the computer with fastboot, results in 'waiting for device' message. All drivers installed, usb debug, have tried charge only/mount as disk drive options. Neither work. Have tried flashing manually by converting .img to .zip without compression and flashing through phone. No error message but nothing changes.
Cannot use cwm to flash because not error message says not rooted. Not sure what else to do. BTW, you guys are awesome for helping me out Thanks!
Click to expand...
Click to collapse
(hah, thanked but meant to hit quote)
What you need to do is go here: http://clockworkmod.com/rommanager
Scroll down the list and find the recovery for our device (5.0.2.7 for the myTouch 4G Slide) - download this.
Put it in the same folder as 'fastboot.exe' on your computer. Rename it to recovery.img
On your phone, turn off 'fastboot' in power options.
Power off the phone.
Now, give it a minute to power off - then hold the volume down button and press power.
Now it will boot up to the hboot menu. The list presented will have you highlighted on the word 'fastboot' - press power to choose this.
Now you are presented with the fastboot menu. It should say fastboot with a red highlight around it near the top.
At this time you should plug the USB cord from your computer into the phone. It will update to say fastboot USB in red highlight now.
-okay-
We have the phone booted up in fastboot, attached to the computer, and ready to work with.
Open up your command prompt, and navigate to the folder where you have the fastboot command. This is the same folder that you have the new clockworkmod recovery.img in from before.
In your terminal now type:
Code:
fastboot devices
This will come back with your device, serial number, and show you it is connected and ready to go. (if it is not something is wrong)
Now type:
Code:
fastboot flash recovery recovery.img
Let's break this down:
fastboot = activates the fastboot.exe command, and says that what's typed next uses the definitions in that fastboot.exe file.
flash = command that says write to
recovery = destination (name of partition) being written to
recovery.img = file written to previously defined location.
----
Since you have the new clockworkmod recovery file in the same folder as fastboot.exe, and you renamed it to recovery.img, then the previously shown command will overwrite your stock recovery with the new image you are providing it.
At this point you should have clockworkmod recovery in place of your stock recovery when you boot the device to hboot menu and select recovery.
Let us know if you have any other problems.
Good explanation blue.... It sounded like he knew what he was doing, hence my quick correction...
Hate typing a lot out from phone!
rooted 1.55.531.3 with clockwork recovery and SU
OMG! Thats awesome. FINALLY ROOTED!!!!! yay! So happy. Thank you guys so much. nlarge and blue, you two are the best!
Thanks again
~Brandi~
Oops... Sorry I called you a he...LOL... Most of us nerds are guys
We help where we can
Boltinghouse said:
OMG! Thats awesome. FINALLY ROOTED!!!!! yay! So happy. Thank you guys so much. nlarge and blue, you two are the best!
Thanks again
~Brandi~
Click to expand...
Click to collapse
rooted 1.55.531.3 with clockwork recovery and SU
nlarge said:
Oops... Sorry I called you a he...LOL... Most of us nerds are guys
We help where we can
rooted 1.55.531.3 with clockwork recovery and SU
Click to expand...
Click to collapse
It's all good, I know being a chick I'm in the minority here. Either way, thank you so much.
So it looks like both nlarge and boltinghouse rooted s-on phones. Is there any reason not to go ahead and root that way? Is there any reason you need/want s-off?
it depends on what you want to do with your phone...
If you just want to be able to make recovery and flash ROMS than you dont need s-off
If you want to play with other stuff(radios and mounts) then you need s-off.
I personally like doing things to my phone so I would like to get to s-off. I am ok with it for now, but S-off will give me the full control I want.
qwerty3656 said:
So it looks like both nlarge and boltinghouse rooted s-on phones. Is there any reason not to go ahead and root that way? Is there any reason you need/want s-off?
Click to expand...
Click to collapse
Hey guys this is my first time trying to root so i really need some help doing it. When ever i use oneclickroot i go through all the steps that it says to do. When its in the processing of rooting this comes up
*server not running*
*daemon not running. starting it now*
*daemon started successfully*
Getting temp root
[1] Segmentation fault app_process /dev...
cannot create /data/local.prop: permission denied
deleting all yo stuff
mount: Operation not permitted
46 KB/s (4292 bytes in 0.090s)
Coping files onto phones...
failed to copy 'su' to ' /system/xbin/su': Read-only file system
failed to copy 'superuser.apk' to '/system/app/Superuser.apk': Read-only file system
failed to copy 'busybox' to '/system/xbin/busybox':Read-only file system
failed to copy 'remount' to '/system/xbin/remount': Read-only file system
Setting permissions..
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/remount: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
link failed Read-only file system
Installing busybox...
/system/xbin/busybox: not found
Cleaning up files...
rm failed for /data/local/zergRush, No such file directory
"You should have root!"
Press any key to continue...
When i check my phone i dont see any superuser or anything saying that have been rooted. Am I missing something that I need for this to work? I am using the Samsung Galaxy Prevail.
Help please.
you have all the proper drivers installed? it mentions to try it a few times without your SD card and in airplane mode.
I installed the Samsung drivers for the phone thats all. What else do I need. I tried it without th SD card but not in airplane mode yet.
If you installed the samsung drivers you should be good, make sure the phone is in USB debugging mode and let it install any drivers that come up.
I just tried to root it with usb debugging on, airplane mode on and the SD card out. The thing that i saw was different was it showed Error: Device not found 4 times. This rooting thing is really fustrating me lol just saying . And do I need to install anything else to do this?
you sure you have the proper drivers installed? oneclick isnt recognizing your phone being connected to your computer, hence device not found. I'd reinstall the proper drivers again, maybe install Samsung Kies, and let the device install some drivers will on usb debugging mode and try again.
follow the link below...
http://androidforums.com/galaxy-pre...oot-samsung-prevail-replenish-shabbyfied.html
Ok i will reinstall the samsung drivers. What does Operation not permitted mean and Permission Denied? And its not coping the files to my phone.
Rooting Samsung Galaxy Prevail Gingerbread 2.3.6
.na
check it out. Now, for the rooting procedure on the Galaxy Prevail running Android 2.3.6, read on!
I. Before You Begin
1. This procedure roots your device by flashing a prerooted ROM, which means you will most definitely lose all your data; so back up what’s important before you proceed.
2. Make sure you have the necessary drivers installed before you proceed; if you aren’t sure, download the package in the next section and run SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe from it before you proceed.
II. Necessary Downloads
III. Rooting the Galaxy Prevail
1. Put your device into Download mode. To do this, with your device powered down, press and hold the Camera, Volume Down and Power buttons until you “Downloading” on your device’s display.
2. Connect your device to your Windows PC.
3. Extract the FF19_ROOTED.zip you downloaded above to a folder on your desktop.
4. From the extracted folder, double-click on odin Multi_Downloader_v4.43to run it.
5. Load files from the extracted folder on to Odin by clicking on the relevant buttons as you see in the screenshot below.
6.Click start let it go by itself trust me it works i did mines
7.Now you rooted and have cwm pick up a rom for it
8.when everything is done you like it
Roms for this phone only
I'm trying to root my SE WT19i, but it's being impossible. I´ll tell you all what I've tried so anyone can see any solution:
I followed this thread for downgrading from andoid 4.0 to 2.3. First, flashed the phone with the 4.0.2.A.0.62 version.
Then, for installing adb drivers, tried installing PC Companion, but it wasn't able to install any driver. So, I searched and installed the drivers this way (installing the “Google USB Driver” package).
Then, following the first thread, downloaded the DooMLoRD's Easy Rooting Toolkit [v4.0] , and followed the instructions (USB debugging, unknown sources, even the 10 minutes screen timeout). Don't worked.
So, I flashed again the phone, with the 4.0.2.A.0.42, and tried one more time (and changed the options again according to the script's instructions). Don't worked.
Same for 4.0.2.A.0.58, that is the version that runs my phone now.
Then, I tried this method, by using the Super One Click. That program prompted me to install drivers, so I installed all I was prompted, but don't worked any exploit method of it (yeah, I know the other method "maybe won't work in Android 2.3 and higher", but I had to try).
As there were new drivers installed, I thought the DoomLord's script now, finally, will be able to work, so I tried again. Well, the console output is this (and it is generated in a few seconds...)
---------------------------------------------------------------
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
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- pushing zergRush
cannot open 'files\zergRush': No such file or directory
--- correcting permissions
--- executing zergRush
--- 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
2262 KB/s (1075144 bytes in 0.464s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
53 KB/s (439 bytes in 0.008s)
--- Free space on /system : 172928 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- 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
--- rebooting
ALL DONE!!!
Press any key to continue . . .
Click to expand...
Click to collapse
Well... the "files\zergRush" actually exists. I haven't modified anything in the files more than unzipping them. I don't know why don't recognise it, but because of that, I downloaded directly the zergRush script and replace it, but didn't worked either even when the DoomLord's script found it. I've also tried to unzipping it directly in C:\, but the results are the same.
I'm using Windows 7, but have tried to run in compatibility mode with xp sp3, and with admin permissions without results.
I don't know what more to do, I think I've tried all. Can anyone help?
PS: I was going to post this in the thread of DoomLord's script (that is the correct place for this, I think), but I'm not allowed yet, sorry.
Accordingly to the rules, bumping thread so it can be seen by anyone who could know about it.
I'm currently trying to contact someone in the IRC, but it'is a bit dead... :-/
install stock rom again and try again
That's already done. Several times. Now, I think the problem is more of the computer for not founding the zergRush script than of the phone. I need a way for getting the script working, but don't know how to...
--------------------------------------------------------------------------------------
Edit: I give up. I can't have my phone useless for more time (because is stupid reconfigure it each time you flash it...). I'm interested no more in rooting the phone. Thanks to all who have read this thread.
Hello everyone.
I have a problem with my Z3 dual device"D6633"
I downgraded to 23.0.F.1.74 and rooted using "giefroot_v3" then installed dual recovery. At this point everything looks fine but rooting seems not complete , I had to uninstall and reinstall busybox to make it work completely and it was successful.
The problem is 23.0.F.1.74 is slow and when I updated to 23.0.1.F.0.96 using flashable zip with root and recovery… I found that rooting is incomplete "some apps don't work even after gaining access to root through supersu"….. I couldn't fix this as I did with older rom or older device "Z2"
I created a very good customized flashable rom with following modifications:
• 23.0.1.F.0.96 deodexed and debloated
• Fm radio working without headset
• Added call recording
• Removed notification for disabled mobile data
• Removed notification for usb debugging
• Added some notifications and ringtones after correcting permissions
• Replaced calculator with CM calculator
• Avoided the need for "adaway" by directly modifying hosts file
• Avoided the need for "SD Fix" by correcting card permissions in "platform.xml"
• Replaced original emoji by iphone emoji
After flashing the rom using dual recovery and flashing system parts through flashtool, everything works great and the rom is ok except the rooting problem. Some apps work with root and some don't…
Working apps:
• Titanium Backup
• Call Master
• Aptoide
• File managers
Non-working apps "even after gaining permission in supersu"
• Adaway
• Xposed installer [big shame]
• Sd card fix
• exDialer plugins
I tried all solutions I know. I uninstalled and reinstalled busybox. I reinstalled supersu through recovery. But nothing works.
The question is …. Is there a way for better rooting to solve this problem???!!!
u might having system r/w mounting problem.
try solution here
monx® said:
u might having system r/w mounting problem.
try solution here
Click to expand...
Click to collapse
Thank you for your reply.
Yes , i am having problem with system r/w
I tried your recovery installer. It successfully installed the recovery , but nothing changed
still the same as before
i forgot u r on ur own customized rom. try reflashing stock supersu.zip frm chainfire's site. then reinstall the modded recovery package again. theres might be smth wrong with ur rom installer script.
can u check output frm terminal or shell if u trigger mount command?
mount -o remount, rw /system
Sent from my D6633
This is logging for installation of the modded recovery .. it may help understand the problem
==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= Maintained by [NUT] =
= =
= For Many Sony Xperia Devices! =
= =
==============================================
1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on unrooted ROM using the TowelRoot method
4. Install ADB drivers to windows
5. Exit
Please choose install action.
[1,2,3,4,5]?1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
=============================================
Getting ro.build.product
=============================================
Device model is D6633
Firmware is 23.0.1.F.0.96
=============================================
Step2 : Sending the recovery files.
=============================================
0 KB/s (30 bytes in 1.000s)
983 KB/s (15757 bytes in 0.015s)
0 KB/s (501 bytes in 1.000s)
11 KB/s (11842 bytes in 1.000s)
4122 KB/s (65965 bytes in 0.015s)
192 KB/s (3082 bytes in 0.015s)
0 KB/s (385 bytes in 1.000s)
3736 KB/s (657704 bytes in 0.171s)
4011 KB/s (3016755 bytes in 0.734s)
4026 KB/s (2319570 bytes in 0.562s)
4188 KB/s (1876508 bytes in 0.437s)
8 KB/s (8987 bytes in 1.000s)
=============================================
Step3 : Setup of dual recovery.
=============================================
Look at your device and grant supersu access!
Press any key to continue AFTER granting root access.
-rwxr-xr-x 1 shell shell 657704 Feb 15 04:34 /data/local/tmp/recover
y/busybox
Press any key to continue . . .
##########################################################
#
# Installing XZDR version 2.8.2 RELEASE
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to al
low installation.
mount: permission denied (are you root?)
mount: permission denied (are you root?)
Copy recovery files to system.
cp: can't create '/system/bin/recovery.twrp.cpio.lzma': File exists
cp: can't create '/system/bin/recovery.cwm.cpio.lzma': File exists
cp: can't create '/system/bin/recovery.philz.cpio.lzma': File exists
chmod: /system/bin/recovery.twrp.cpio.lzma: Read-only file system
chmod: /system/bin/recovery.cwm.cpio.lzma: Read-only file system
chmod: /system/bin/recovery.philz.cpio.lzma: Read-only file system
Copy chargemon script to system.
cp: can't create '/system/bin/chargemon': File exists
chmod: /system/bin/chargemon: Read-only file system
Copy dualrecovery.sh to system.
cp: can't create '/system/bin/dualrecovery.sh': File exists
chmod: /system/bin/dualrecovery.sh: Read-only file system
Copy rickiller.sh to system.
cp: can't create '/system/bin/rickiller.sh': File exists
chmod: /system/bin/rickiller.sh: Read-only file system
Installing NDRUtils to system.
cp: can't create '/system/app/NDRUtils.apk': Read-only file system
chmod: /system/app/NDRUtils.apk: No such file or directory
Copy disableric to system.
cp: can't create '/system/xbin/disableric': Read-only file system
chmod: /system/xbin/disableric: No such file or directory
rm: can't remove '/system/etc/.xzdrbusybox': Read-only file system
Copy busybox to system.
cp: can't create '/system/xbin/busybox': File exists
cp: can't create '/system/.XZDualRecovery/busybox': File exists
chmod: /system/xbin/busybox: Read-only file system
chmod: /system/.XZDualRecovery/busybox: Read-only file system
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event3!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================
WARNING: linker: libspeexresampler.so has text relocations. This is wasting memo
ry and is a security risk. Please fix.
WARNING: linker: libspeexresampler.so has text relocations. This is wasting memo
ry and is a security risk. Please fix.
=============================================
Your installation has already cleaned up after
itself if you see the install.bat/install.sh exit.
=============================================
=============================================
Installation finished. Enjoy the recoveries!
=============================================
Press any key to continue . . .
i can see clearly system mount problem. can u pls try mount command using terminal?
Sent from my D6633
"Operation not permitted"
in terminal and adb
I have read that it might be the kernel blocking this !!!
May be i need a modified kernel
no need as im using stock kernel with same device & fw with u. im uploading another package. hope u can test it.
---------- Post added at 05:44 PM ---------- Previous post was at 05:29 PM ----------
How bout THIS
Wow it worked....
Thank you very much
You are the best
akabawy said:
Hello everyone.
I have a problem with my Z3 dual device"D6633"
I downgraded to 23.0.F.1.74 and rooted using "giefroot_v3" then installed dual recovery. At this point everything looks fine but rooting seems not complete , I had to uninstall and reinstall busybox to make it work completely and it was successful.
The problem is 23.0.F.1.74 is slow and when I updated to 23.0.1.F.0.96 using flashable zip with root and recovery… I found that rooting is incomplete "some apps don't work even after gaining access to root through supersu"….. I couldn't fix this as I did with older rom or older device "Z2"
I created a very good customized flashable rom with following modifications:
•23.0.1.F.0.96 deodexed and debloated
•Fm radio working without headset
•Added call recording
•Removed notification for disabled mobile data
•Removed notification for usb debugging
•Added some notifications and ringtones after correcting permissions
•Replaced calculator with CM calculator
•Avoided the need for "adaway" by directly modifying hosts file
•Avoided the need for "SD Fix" by correcting card permissions in "platform.xml"
•Replaced original emoji by iphone emoji
After flashing the rom using dual recovery and flashing system parts through flashtool, everything works great and the rom is ok except the rooting problem. Some apps work with root and some don't…
Working apps:
•Titanium Backup
•Call Master
•Aptoide
•File managers
Non-working apps "even after gaining permission in supersu"
•Adaway
•Xposed installer [big shame]
•Sd card fix
•exDialer plugins
I tried all solutions I know. I uninstalled and reinstalled busybox. I reinstalled supersu through recovery. But nothing works.
The question is …. Is there a way for better rooting to solve this problem???!!!
Click to expand...
Click to collapse
Any chance you can share your rom? Thank you
---------- Post added at 06:13 PM ---------- Previous post was at 05:57 PM ----------
monx® said:
no need as im using stock kernel with same device & fw with u. im uploading another package. hope u can test it.
---------- Post added at 05:44 PM ---------- Previous post was at 05:29 PM ----------
How bout THIS
Click to expand...
Click to collapse
I tried flashing this in TWRP but get an error that no md5 is found and that the zip is corrupt. Should it be flashed in a different way?
slonn said:
I tried flashing this in TWRP but get an error that no md5 is found and that the zip is corrupt. Should it be flashed in a different way?
Click to expand...
Click to collapse
Re-download it or disable the md5 check in recovery
gregbradley said:
Re-download it or disable the md5 check in recovery
Click to expand...
Click to collapse
Re-download got the same error. There doesn't seem to be an option to disable md5 check in TWRP settings.
slonn said:
Re-download got the same error. There doesn't seem to be an option to disable md5 check in TWRP settings.
Click to expand...
Click to collapse
Untick the zip file signature verification once you have selected the zip file to flash
gregbradley said:
Untick the zip file signature verification once you have selected the zip file to flash
Click to expand...
Click to collapse
That was already unticked...
slonn said:
That was already unticked...
Click to expand...
Click to collapse
Did you use the Dev-host download manager to download the file? What is the name of the file you downloaded? Including the extension....
gregbradley said:
Did you use the Dev-host download manager to download the file? What is the name of the file you downloaded? Including the extension....
Click to expand...
Click to collapse
Thanks for your quick replies! I don't know what a Dev-Host manager is. I clicked on the link provided and chose 'download now'. The file name is Z3-lockeddualrecovery2.8.2-MOD.installer+driverV2.zip
slonn said:
Thanks for your quick replies! I don't know what a Dev-Host manager is. I clicked on the link provided and chose 'download now'. The file name is Z3-lockeddualrecovery2.8.2-MOD.installer+driverV2.zip
Click to expand...
Click to collapse
Download it again but make sure the little tick box that says download with dev-host download manager is not ticked
EDIT
are you sure it says ".zip" at the end? Have you hidden file extensions for known file types? I have a feeling you have downloaded the download manager which ends in ".exe"
gregbradley said:
Download it again but make sure the little tick box that says download with dev-host download manager is not ticked
EDIT
are you sure it says ".zip" at the end? Have you hidden file extensions for known file types? I have a feeling you have downloaded the download manager which ends in ".exe"
Click to expand...
Click to collapse
Yes, fairly sure: https://copy.com/DHPGvwPduMaKwurh
Which tick box are you referring to? I don't see one on the download page.
slonn said:
Yes, fairly sure: https://copy.com/DHPGvwPduMaKwurh
Click to expand...
Click to collapse
Hmmm, that's a strange one.
Did you download it on your phone or on your PC?
Try it on your PC please if you did not do it that way
gregbradley said:
Hmmm, that's a strange one.
Did you download it on your phone or on your PC?
Try it on your PC please if you did not do it that way
Click to expand...
Click to collapse
Same error MD5. Pls check this file.