Database Develop

[Q] Rom Manager on Nexus s claims device is not rooted

Hi
When I start the Rom Manager I get the message "You must root your phone for ROM Manager to function. Superuser was not found as "/system/bin/su" or/system/xbin/su".
I have followed the instructions here on how to root my Nexus s and I am able to enter recovery mode and am able to go into bootloader. I also see that is says "Unlock" there.
So the way I understand it, the phone is rooted. Unless I miss something here.
I also see the Superuser icon in my launcher.
What am I doing wrong?

Think this is the wrong area to ask but when you flashed the su file did you mount system in the mount and storage before flashing the su file?

I dont think it was mentioned in the guide.
how do I do that?
Can I reapply the su zip file again?

jerrycycle said:
Think this is the wrong area to ask but when you flashed the su file did you mount system in the mount and storage before flashing the su file?
Click to expand...
Click to collapse
OK. That is what I was missing.
Now its done.
Thanks

dbenyakar said:
OK. That is what I was missing.
Now its done.
Thanks
Click to expand...
Click to collapse
What method did you use to root?

Nexus S & Galaxy Nexus one click root toolkit ! Unlock bootloader+CWM+Su(or)SuperSu

Nexus S & Galaxy Nexus one click root toolkit ! Unlock bootloader+CWM+Su(or)SuperSu
This tool will root you nexus s/Galaxy Nexus install su or super su and ClockWorkMod recovery!!
For Nexus S:4G,I9020T,I9023,I9020A.
Galaxy Nexus:GSM/Verizon/Sprint
Disclaimer!
Your warranty is now void.
I am not responsible for bricked or damaged devices
YOU are choosing to make these modifications.
Click to expand...
Click to collapse
DOWNLOAD
Click to expand...
Click to collapse
Current Version (Nexus S + Galaxy Nexus) 3.5: http://d-h.st/qaL
MIRROR:http://www.mediafire.com/download.php?1if2rvgpcte2rcs
Old versions:
3.0: http://d-h.st/mhO
2.0: http://dev-host.org/gcZ (nexus s only)
1.0: http://dev-host.org/bEE (nexus s only)
HOW-TO
Click to expand...
Click to collapse
just unzip the content and run the tool ! drivers are included in case you need them.
incase you had any problems try rerunning the tool,and if you got superuser/supersu app but you are unable to use root apps,update superuser/supersu from the play store then update the binary from inside the app.
CHANGELOG
Click to expand...
Click to collapse
V3.5
-added support for jelly bean
-few script optimization
-updated superuser and supersu
V3.0
-added support to galaxy nexus and all it's variants.
-added support to install super su.
-moved from *.bat to *.exe
-new icon
-su/super su, will now automatically flash no need to touch "install zip"
-skip bootloader unlock if you are already unlocked.
-update drivers
V2.0
-Removed "sticky.bat"
-modified su flashing script.
-the recovery now will stick automatically no need to flash any file after rooting or running any script.
V1.0
-initial release
ALL DATA WILL BE WIPED FROM DEVICE(only if bootloader is locked)
credits
-Chainfire for super su
-ChainsDD for superuser
-Pdanet for drivers
-Clockworkmod team for recovery
-my friend for the icon​

am i going to loose everithing on USB storage ? or jjust sistem data ? i have to have a full rom right ?

raducux said:
am i going to loose everithing on USB storage ? or jjust sistem data ? i have to have a full rom right ?
Click to expand...
Click to collapse
if your bootloader is locked then yes you will loose everything on USB storage,if the bootloader is already unlocked you will not loose any data,you don't need to flash a rom after rooting the device as it will not wipe the system.

Hi, I installed the drivers on my computer and am currently running the run.bat file. It's saying my device is not found. I have USB Debugging on, and USB storage is on. Any ideas?

Sticky please
Can i replace CWR with newest img version?
PLEASE STICKY THIS THREAD ON TOP.

Romaniac said:
Hi, I installed the drivers on my computer and am currently running the run.bat file. It's saying my device is not found. I have USB Debugging on, and USB storage is on. Any ideas?
Click to expand...
Click to collapse
Turn off the usb storage,you just need usb debugging enabled if you turned on usb storage it will not work
stewie-droid said:
Can i replace CWR with newest img version?
PLEASE STICKY THIS THREAD ON TOP.
Click to expand...
Click to collapse
The tool includes the latest cwm img,but if you want to replace it with another one you can do,just make sure you rename it to same name of the img in the root tool folder,but make sure that the recovery you will use is compatible with the nexus s

After I execute run.bat the phone is rooted. I reboot using ClockWorkMod Recovery. Then, when I run sticky.bat and follow the instructions I get the following:
[email protected]:/ $ su
su
[email protected]:/ # rm /etc/installrecovery.sh
rm /etc/installrecovery.sh
rm failed for /etc/installrecovery.sh, No such file or directory
What should I be doing? Please help.

Ritwik7 said:
After I execute run.bat the phone is rooted. I reboot using ClockWorkMod Recovery. Then, when I run sticky.bat and follow the instructions I get the following:
[email protected]:/ $ su
su
[email protected]:/ # rm /etc/installrecovery.sh
rm /etc/installrecovery.sh
rm failed for /etc/installrecovery.sh, No such file or directory
What should I be doing? Please help.
Click to expand...
Click to collapse
The phone should booted normally when running the sticky.bat (On the home screen),there is nothing to worry about just Complete the instructions normally one of the two scripts will fail since the name of the file differ in gingerbread and ics,try this rm /etc/install-recovery.sh and continue the instruction it should work and clockworkmod recovery would stick.

Thanks for your reply. I used a FixRecovery.zip file from another thread and flashed it after executing run.bat again. Now I am able to boot into ClockWorkMod.

Ritwik7 said:
Thanks for your reply. I used a FixRecovery.zip file from another thread and flashed it after executing run.bat again. Now I am able to boot into ClockWorkMod.
Click to expand...
Click to collapse
My friend can you guide where i can find this .zip because i m facing the same problem.thank you in advance

Ok I got it to stick by using Root Explorer to mount it as read/write first then ran the sticky.bat. ICS is the rm /etc/install-recovery.sh command.

m.sabra said:
The phone should booted normally when running the sticky.bat (On the home screen),there is nothing to worry about just Complete the instructions normally one of the two scripts will fail since the name of the file differ in gingerbread and ics,try this rm /etc/install-recovery.sh and continue the instruction it should work and clockworkmod recovery would stick.
Click to expand...
Click to collapse
I tried this and when I want to do the sticky.bat, when I type the "rm /etc/install-recovery.sh" it sais rm failed for /etc/.., Read-only file system

I had the same problem with sticky.bat.
Once you 're done with run.bat and it reboots in cwm just flash fix-recovery.zip
http://forum.xda-developers.com/showthread.php?p=20432966&highlight=fix-recovery#post20432966

karx23 said:
I had the same problem with sticky.bat.
Once you 're done with run.bat and it reboots in cwm just flash fix-recovery.zip
http://forum.xda-developers.com/showthread.php?p=20432966&highlight=fix-recovery#post20432966
Click to expand...
Click to collapse
thanks ! added the link to the OP in case anyone had problems like this.

Argh, I seem to have successfully unrooted my Nexus S 9020t and had it rebooted back in, but while it was booting up again I accidentally pressed a button and it told me "error: device not found" twice followed by "<waiting for device>".
Unfortunately my phone has already been rebooted, but it still seems to be waiting for my device. I'm not sure if I can disconnect this device from USB while this is going on, so uh, what do I do?
Edit: Disconnected and reconnected the USB cable on the phone to see what would happen, and it seems to be ok. I'm still stuck on "waiting for device" though. Should I consider restarting the process again?
Edit Edit: Decided to just try to redo the process all over again...seems to have worked!

Updated tool to version 2.0 ! check the changelog in OP, it should solve all sticky recovery related problems,as i removed sticky.bat and now the recovery will stick automatically without the need of running any commands or flashing any fixes.
thanks for reporting problems and feedbacks

thank you for this

Okay, I've tried to run this but it always fails at flashing the recovery.. Any help?

Lelouche said:
Okay, I've tried to run this but it always fails at flashing the recovery.. Any help?
Click to expand...
Click to collapse
Ok first have you unlocked your bootloader when the tool asked you to use volume buttons to chose yes and unlock ? (If you did this you should see an unlocked lock under google logo when booting the phone) if you didn't just run the script again and unlock the bootloader.
Are the drivers installed properly ? When you connect the phone to the pc check device manager to see if the PC recognizes the phone (the drivers are included in the tool in case you need them .
And last check the root tool folder on your pc it should have a file called cwm.img if it doesn't then download the tool again.

SuperUser is not visible after the process
I am on stock ICS, I had previously unlocked the bootloader, then I did the whole process mentioned in this thread. It showed me the CWM menu but when I did the reboot, I couldn't find the superuser app. Then to test whether it is rooted or not, I installed titanium backup but it says the device isnt rooted. What to do now? I tried SuperOneClick but it doesn't seem to work.
Edit: Thanks guys, sorry. It was my mistake, I didnt do the whole process in a right way. It is working as expected.

[Q] Modded kernel on stock rom?

Hi to all.
I have a rooted Incredible S (through HTCDev), stock ics rom and S-ON.
Is there a way to install a modded kernel on stock rom?

jauffre said:
Hi to all.
I have a rooted Incredible S (through HTCDev), stock ics rom and S-ON.
Is there a way to install a modded kernel on stock rom?
Click to expand...
Click to collapse
theres a guide in xics kernel thread

Can you give me the link, please?
I tried XS ICS 2.2, and followed some advices to make it work, but it didn't.

jauffre said:
Can you give me the link, please?
I tried XS ICS 2.2, and followed some advices to make it work, but it didn't.
Click to expand...
Click to collapse
l0st.prophet said:
Changelog
Instructions for S-OFF Users
Simply flash XS-ICSvX.X.zip in your favourite recovery!
Instructions for manual flashing (HTCDev.com unlocked S-ON Users)
Thanks to MrToastbrot for instructions
Step 1: Download the XS-Kernel.zip, then open the Zip on your computer and extract the file mkbootimg.sh in "kernel"
Step 2: Open mkbootimg.sh in a texteditor like notepad++ or notepad, then edit the following in line 3:
Code:
output /tmp/newboot.img
to
Code:
output /sdcard/newboot.img
Step 3: Save your edited file and place it back in your zip, copy your modified zip to your phone-sdcard and install it in the recovery. Then reboot your phone and connect it to pc and take the newboot.img from the root of the sdcard.
Step 4: Now reboot your phone into bootloader and flash it via fastboot flash boot newboot.img
Step 5: Once you phone has booted, mount the system as r/w using something like ES file explorer or Root explorer, then type the following:
Code:
adb push bcm4329.ko /system/lib/modules
Set permissions to rw-r--r--, reboot and enjoy!
Sweep2Wake: Q&A
Q: How do I disable / enable the feature?
A: Two options
Change the value in the file /sys/android_touch/sweep2wake to either 0 for disabled, 1 for enabled and 2 for enabled with backlight. This will be reset upon rebooting.
If your ROM supports init.d scripts, then flash the zip to enable or disable, this will stick over a reboot.
Q: It keeps taking screenshots when I lock the screen!?
A: This is due to an incompatibility with this feature and the native screenshot in Sense. TO stop the screen shots, you need to edit your build.prop and change the property ro.htc.framework.screencapture to false, and then reboot.
Click to expand...
Click to collapse
there

Thanks!
The problem is that although i changed the mkbootimg.sh file, i cannot find the newboot.img.

jauffre said:
Thanks!
The problem is that although i changed the mkbootimg.sh file, i cannot find the newboot.img.
Click to expand...
Click to collapse
Try looking on your sdcard. Assuming you followed the guide correctly...

I followed the guide as it is, i modified the file as the guide says, and there's no newboot.img file on sdcard.

jauffre said:
I followed the guide as it is, i modified the file as the guide says, and there's no newboot.img file on sdcard.
Click to expand...
Click to collapse
Upload your modded zip file.

Nonverbose said:
Upload your modded zip file.
Click to expand...
Click to collapse
here it is

jauffre said:
here it is
Click to expand...
Click to collapse
Your modded zip is working on my phone but It's s-off. I found the newboot.img on sdcard root. Run your flashable zip again then go to tools>copy recovery.log to sdcard. It will be in your 4ext directory. Have a look and see if you can spot any errors. Upload here if you need any help.

Nonverbose said:
Your modded zip is working on my phone but It's s-off. I found the newboot.img on sdcard root. Run your flashable zip again then go to tools>copy recovery.log to sdcard. It will be in your 4ext directory. Have a look and see if you can spot any errors. Upload here if you need any help.
Click to expand...
Click to collapse
This is the log.
I don't understand it very much, but it seems that it copies the boot.img file, and then there are some errors.
could you upload the newboot.img file?

jauffre said:
This is the log.
I don't understand it very much, but it seems that it copies the boot.img file, and then there are some errors.
could you upload the newboot.img file?
Click to expand...
Click to collapse
I'm not on stock Rom, so my newboot.img will not work on your phone because it has a different ramdisk. You might want to try changing your recovery to 4ext touch.

Nonverbose said:
I'm not on stock Rom, so my newboot.img will not work on your phone because it has a different ramdisk. You might want to try changing your recovery to 4ext touch.
Click to expand...
Click to collapse
ok; i changed recovery to 4ext, and here is the log.

jauffre said:
ok; i changed recovery to 4ext, and here is the log.
Click to expand...
Click to collapse
Wow still got that BOARD_KERNEL_CMDLINE error happening. Try flashing tpbklakes unsecured boot.img and then update http://forum.xda-developers.com/attachment.php?attachmentid=1238549&d=1343964381

Nonverbose said:
Wow still got that BOARD_KERNEL_CMDLINE error happening. Try flashing tpbklakes unsecured boot.img and then update http://forum.xda-developers.com/attachment.php?attachmentid=1238549&d=1343964381
Click to expand...
Click to collapse
Thank you Nonverbose!! It worked!!

Error 255

Hi,
I've just received my new Razr i yesterday. I've unlock the bootloader, rooted it and instal CWM 6.0.1.9.
My problem is under the CWM, as soon as I want to install a .zip I've always this message : "E: Error in /external_sd/ ... .zip (Status 255) Installation aborted"
Has anyone the same problem or a solution to solve this problem ?
Thank you

woodyby said:
Hi,
I've just received my new Razr i yesterday. I've unlock the bootloader, rooted it and instal CWM 6.0.1.9.
My problem is under the CWM, as soon as I want to install a .zip I've always this message : "E: Error in /external_sd/ ... .zip (Status 255) Installation aborted"
Has anyone the same problem or a solution to solve this problem ?
Thank you
Click to expand...
Click to collapse
Take the update-binary from any of your working RAZR i flashable zip (or an OTA update.zip) and drag and drop into the zip you are trying to flash.
255 means binary not compatible pretty much.
ARM update-binary won't work on x86 device
This is not development by the way.

mattlgroff said:
Take the update-binary from any of your working RAZR i flashable zip (or an OTA update.zip) and drag and drop into the zip you are trying to flash.
255 means binary not compatible pretty much.
ARM update-binary won't work on x86 device
This is not development by the way.
Click to expand...
Click to collapse
It's working great !!! Thank you

Moved to Q&A

Please provide any such binary
woodyby said:
It's working great !!! Thank you
Click to expand...
Click to collapse
Please provide any such binary that worked for you i replaced with few i know but could not get rid of status 255 error for same device

I tried this and error 255 did not appear again. Though, it did still say 'installation aborted' without saying why.

mattlgroff said:
Take the update-binary from any of your working RAZR i flashable zip (or an OTA update.zip) and drag and drop into the zip you are trying to flash.
255 means binary not compatible pretty much.
ARM update-binary won't work on x86 device
This is not development by the way.
Click to expand...
Click to collapse
I got that error when I tried to install onandroid in cwm (x86) I think it maybe my kernel ...

Huawei GT3 ROM Help [NO OS]

Hi, I saw some threads saying some stuff about the Huawei GT3, but they didnt helped me so Im posting this thread.
I have a huge Problem with my phone.
(Im a Newbie btw)
I wanted to root my phone so I installed TWRP and rebooted (TWRP works btw), now it said "Encryption unsuccessfull"
I looked up on YouTube to look how to fix this and ended up deleting my complete OS
Now I downloaded the Firmware of my Phone and looked how to install it with TWRP and ADB.
When I try to install the "update.zip" File with TWRP it says something like this :
[2017-11-14 08:00:21 623] E:unknown command [errno]
dload_format_userdata,line=527: dload_format_userdata ok!
script aborted: update_huawei_pkg_from_ota_zip: update package from zip failed
update_huawei_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
I:Install took 0 second(s).
Error installing zip file '/data/update.zip'
I also tried to delete the "assert" parts in the updater-script file but it also didnt work.
Now I heard about the "dload" Method but I have some questions about that
1. Where is the dload folder exactly
2. When I try to move the folder cointaining the "update.zip" to as expample root It says not enough space on device (which Is not true) or something like this :
Running command: 'mv "/data/update.zip" "/root"'
mv: write error: No space left on device
mv "/data/update.zip" "/root" process ended with ERROR: 1
Do I maybe have the wrong ROM or something?
Please help me . (or try )

Check the dload guide in my signature. You will know everything. Let me know if any questions or doubts, will help. Dont worry twrp error is normal as these zips shouldn't be flashed with twrp

shashank1320 said:
Check the dload guide in my signature. You will know everything. Let me know if any questions or doubts, will help. Dont worry twrp error is normal as these zips shouldn't be flashed with twrp
Click to expand...
Click to collapse
Hi! Thanks for your reply!
I bought myself a Micro-SD card and extraced the ZIP like in your tutorial, and its working!
Its installing right now!
But I wanted to say something..first thank you very much and second the Russian Website you provided gave me the wrong package, this was the right one :
skyneel.com/huawei-gt3-nougat

niclasdriver said:
Hi! Thanks for your reply!
I bought myself a Micro-SD card and extraced the ZIP like in your tutorial, and its working!
Its installing right now!
But I wanted to say something..first thank you very much and second the Russian Website you provided gave me the wrong package, this was the right one :
skyneel.com/huawei-gt3-nougat
Click to expand...
Click to collapse
There are many ways to get firmware but the best part it worked and successful. Enjoy buddy.