Database Users

[HOWTO]: Rooting the Huawei S7 Android 2.2.2 stock

Well this was a bit of a mess!
Firstly updating:
http://forum.xda-developers.com/showthread.php?t=1043349
http://phonedock.net/huawei-ideos-s7-froyo-2-2-2-update.html I followed this nice writeup. Be sure to delete the log file in dload for the second round of the upgrade as your device might, like mine, just blink on and off for a while trying to flash what it thinks it finds is already flashed but what just gives an error!
http://www.androidtablets.net/forum...uawei-ideos-s7-official-firmware-2-2-2-a.html Links to 2.2.2 Brazil which is the best for the 101 apparently, some tests done in that post on which rom work best for which model.
Now,
REMOVE YOUR SDCARD IF ANY! AND REBOOT THE DEVICE ! THIS HACK RELIES HEAVILY ON HIGH STRANGENESS AND SPOOKY ACTION AT A DISTANCE!
Originally i though modifying an ol doroot.sh script to using the psneuter exploit from SuperOneClick i would manage to root the device. Not without some fuzz, no. Firstly i discovered "cp" and many basic fileutils im used to in the world of *nix was missing from the 2.2.2 image kindly provided by Huawei ( The Norwegian Telenor image i might add that the camera on a model 101 will not work with!) so i found an easier way! push push push!
Here's what i did, for convenience ill try making it a script, but be prepared to copy these commands manually instead! For windows simply remove the ./ and add .exe .
Now, to make this work, simply get SuperOneClick from http://shortfuse.org/?page_id=2 and unzip, i used the adb from the google android sdk, but i guess the adb binary that comes with SOC is a simpler route if your just in for a quick root fix. Simply rename the appropriate adb for your system and use this method.
The simplest thing to do i guess is to copy Exploits/psneuter or gingerbreak to the ADB folder (in SuperOneClick's folder) and go on from there, also copy su-v3 (rename it to su) and Superuser.apk from "Root/" to the folder (ADB), or if you choose to, rewrite this "script" with the appropriate paths. Im unsure if the following script will work in every case, so you might want to do it manually, but most should get the drift, if you are not comfortable with this procedure you probably have no business or reason rooting the device in the first place. Disclaimer; if this bricks your device don't blame me, this is a fact of "it worked for me", your results may differ.
Be sure to set your USB mode to "Developer" mode
AND BE ROOT ON YOUR MACHINE!
Code:
#/bin/bash
echo "The BackAsswardsRootScript!\n\n"
echo "Lets start the adb server.\n\n"
./adb kill-server
./adb start-server
echo "Pushing the exploit psneuter onto the device.\n\n"
./adb push psneuter /data/local/tmp/psneuter
./adb shell "chmod 0755 /data/local/tmp/psneuter"
./adb push busybox /data/local/tmp/busybox
./adb shell "chmod 4755 /data/local/tmp/busybox"
echo "Now we run the root exploit.\n\n"
./adb shell "./data/local/tmp/psneuter"
echo "We should be root now, making sure.\n\n"
./adb root
echo "Remointing the FS as RW!\n\n"
./adb shell " /data/local/tmp/busybox mount -o rw,remount /system"
echo "Pushing the system files in place\n"
./adb shell "/data/local/tmp/busybox cp /data/local/tmp/busybox /system/bin/busybox"
./adb push su /system/bin/su
./adb push Superuser.apk /system/app/Superuser.apk
echo "Correct permissions might be nice.\n"
./adb shell "chmod 4755 /system/bin/busybox"
./adb shell "chmod 4755 /system/bin/su"
./adb shell "chmod 755 /system/app/Superuser.apk"
# Lets go back to read only, just for kicks!
echo "Remounting the filesystem as Read-Only\n\n"
./adb shell "busybox mount -o ro,remount -t /system"
echo "You should now be rooted my friend.\n Enjoy!\n"
Please help feed my Linux addiction! Go to http://threader.zapto.org and click Donate!

Rooting S7 using Gingerbreak
Just too inform you. I've just succesfully rooted the Indonesian 2.2.2 running on a
S7-105 using Chainfire's Gingerbreak v1.2.

Cool, theres a gingerbreak exploit in the superoneclick package also, i tried that after i though psneuter didnt work, just a matter of replacing psneuter with gingerbreak. Did you use this method though or did you find some other way?

I didn't change or replace anything. My terminal skills are not on a level to have the guts anyway.
I simply updated from S7V100R001C43B010 to S7v100R001C98B021.
Then ran the Gingerbreak 1.2 exploit.

Interesting, yeah the gingerbreak exploit will work, when i wrote the fist post i used the gingerbreak exploit instead of the psneuter one thinking psneuter didnt work, turns out it did though and i went back to that one as its designed for 2.2.2, didnt know of this wrapper though, thanks!

Just granted su superuser permissions on the Australian s7
Great work. Just noticed a missing final quotation mark:
threader said:
./adb shell "chmod 0755 /data/local/tmp/psneuter
Click to expand...
Click to collapse
Probably works because of the end of line but should be:
./adb shell "chmod 0755 /data/local/tmp/psneuter"

threader said:
Well this was a bit of a mess!
Firstly updating:
http://forum.xda-developers.com/showthread.php?t=1043349
http://phonedock.net/huawei-ideos-s7-froyo-2-2-2-update.html I followed this nice writeup. Be sure to delete the log file in dload for the second round of the upgrade as your device might like mine just blink on and off for a while trying to flash what it finds is already flashed but what just gives an error. !
http://www.androidtablets.net/forum...uawei-ideos-s7-official-firmware-2-2-2-a.html Links to 2.2.2 Brazil which is the best for the 101 apparently, some tests there on which roms work best for which models also.
Now,
REMOVE YOUR SDCARD IF ANY! AND REBOOT THE DEVICE ! THIS HACK RELIES HEAVILY ON HIGH STRANGENESS AND SPOOKY ACTION AT A DISTANCE!
Originally i though modifying an ol doroot.sh script to using the psneuter exploit from SuperOneClick i would manage to root the device. Not without some fuzz, no. Firstly i discovered "cp" and many basic fileutils was missing from the 2.2.2 image kindly provided by Huawei (Norwegian Telenor image, that i might add, the camera on a model 101 will not work with!) soo i found an easier way! push push push!
Heres what i did, for convenience ill try making it a script, but im making it as i type this post so this is untested as a script(!) Be prepared to copy these commands instead!
Now, to make this work, simply get SuperOneClick from http://shortfuse.org/?page_id=2 and unzip, i used the adb from the google android sdk, but i guess the adblinux binary that comes with SOC will work just as well, simply rename it to adb and use this method. The simplest thing to do i guess is copy Exploits/psneuter to the ADB folder (in SuperOneClick's folder) and go from there, also copy su-v3 (and rename it to su) and Superuser.apk from Root to the folder (ADB), or rewrite this "script"/collection of commands i used" with the appropriate paths. Im unsure if the following script will work as is as i said, so you might want to do it manually, but most should get the drift, if not you probably have no business or reason rooting the device in the first place. Disclaimer; if this bricks your device don't blame me, this is a fact of "it worked for me", your results may differ.
Be sure to set your usb mode to Developer mode
BE ROOT!
#/bin/bash
echo "The backasswardsrootscript!\n\n"
echo "Lets start the adb\n\n"
./adb kill-server
./adb start-server
./adb push psneuter /data/local/tmp/psneuter
./adb shell "chmod 0755 /data/local/tmp/psneuter
echo "Now we run the root exploit.\n\n"
./adb shell "./data/local/tmp/psneuter"
echo "Should say we are already root now.\n\n"
./adb root
echo "Remointing the FS as RW!\n\n"
# This really should be /dev/block/mmcblk0p1, i have no idea why this works.
./adb shell "mount -o rw,remount -t ext3 /dev/block/mmcblk1p1 /system"
# Now instead of copying using cp or moving with mv, considering "cp" was missing
# and mv just didnt work for some reason...! I found just pushing the files straight to the
# system after remounting worked just fine
echo "Pushing the system files in place\n"
./adb push su /system/bin/su
./adb push Superuser.apk /system/app/Superuser.apk
./adb push busybox /system/bin/busybox
echo "Correct permissions might be nice.\n"
./adb shell "chmod 4755 /system/bin/busybox
./adb shell "chmod 4755 /system/bin/su"
./adb shell "chmod 755 /system/app/Superuser.apk"
# Lets go back to read only just for kicks!
echo "Remounting the filesystem as Read-Only\n"
./adb shell "mount -o ro,remount -t ext3 /dev/block/mmcblk1p1 /system"
echo "You should be rooted my friend\n Enjoy!\n BE SURE TO DONATE TO SUPERONECLICK!!!"
# One of the main strangenesses i found was the block device was logically enough placed on
# partioton 1, of block1 which really should have been block 0 part 1, but that doesnt work.
# So it boils down to that this shouldnt work but does for no apparent reason(!).
# even /etc/mtab says that mmcblk0p1 is mounted to a non existent /mnt/dcard
# as an EXT4 partition which isnt supposed to be supported until 2.3.x
Click to expand...
Click to collapse
Dear S7 users,I am using the ideos s7 by Teltra supllier and i did unlock sim by norwegian rom.I read a lot of document but i didnt find out an easy way to run clockwork that i can run cook rom,can u help me how to run it in easy way.Thanks and appreciate that.
http://www.androidtablets.net/forum...wegian-2-2-2-s7v100r001c57b111.html#post82863

PuZZleDucK said:
Just granted su superuser permissions on the Australian s7
Great work. Just noticed a missing final quotation mark:
Probably works because of the end of line but should be:
./adb shell "chmod 0755 /data/local/tmp/psneuter"
Click to expand...
Click to collapse
Great! Thanks! Ops, yeah missed that, fixed now, thank you for pointing that out. I haven't spent much more time on this. the pad has pretty much been untouched since i moved house. I would like to make this easier for less technical inclined here but its just a matter of replacing ./adb with adb.exe if your on windows. Besides, i don't want to be at fault for bricking someone. And maybe i could write some simple application for installing Gnu/Linux as well, ( http://forum.xda-developers.com/showthread.php?t=1109730 ) but that will have to wait until someone bribes me or hits me over the head i guess.

tell me how you did it. i have a s7 - 105 too. please tell me the full tutorial, beginning to the end. cause i'm new to this android stuff. please..
---------- Post added at 08:53 PM ---------- Previous post was at 08:51 PM ----------
Maniacnl said:
Just too inform you. I've just succesfully rooted the Indonesian 2.2.2 running on a
S7-105 using Chainfire's Gingerbreak v1.2.
Click to expand...
Click to collapse
tell me how you did it. i have a s7 - 105 too. please tell me the full tutorial, beginning to the end. cause i'm new to this android stuff. please..

[Solved] [Stock .27] ADB only work in recovery mode

Hello, i have a problem with my TF101 (B70 if i'm right), ADB only work when i'm in recovery mode.
I lost root i don't know how and tried to regain it, but every rooting tools failled, i then discovered that commands wasn't working (even ls), but they do work in recovery mode (from /sbin).
When i try to flash a .zip from CWM , it seems that changes suposed to be applied to /system/bin aren't applied (SuperUser/SuperSU never find /system/bin/SU) but /system/bin/app correctly get updated.
I'd prefer to not wipe the device's data and repair it from it's current state if possible.
TF101's current state : Stock .27 guevor kernel 717, CWM non touch recovery
From recovery
ls -l /sbin
http://pastebin.com/tmyZagUk
ls -l /system/bin
http://pastebin.com/6tsPaPF0
ls -l /system/xbin
http://pastebin.com/D3jW5Sy3
If you need more info please tell
Bounty : I'll send Russian chocolat and candies to the one that will find how to fix this !

Magissia said:
Hello, i have a problem with my TF101 (B70 if i'm right), ADB only work when i'm in recovery mode.
I lost root i don't know how and tried to regain it, but every rooting tools failled, i then discovered that commands wasn't working (even ls), but they do work in recovery mode (from /sbin).
When i try to flash a .zip from CWM , it seems that changes suposed to be applied to /system/bin aren't applied (SuperUser/SuperSU never find /system/bin/SU) but /system/bin/app correctly get updated.
I'd prefer to not wipe the device's data and repair it from it's current state if possible.
TF101's current state : Stock .27 guevor kernel 717, CWM non touch recovery
From recovery
ls -l /sbin
http://pastebin.com/tmyZagUk
ls -l /system/bin
http://pastebin.com/6tsPaPF0
ls -l /system/xbin
http://pastebin.com/D3jW5Sy3
If you need more info please tell
Click to expand...
Click to collapse
Go to the play store, download & install Goomanager, install TWRP. CWM seems to have a few issues with teh TF101's.

Hello, i have a CWM flashable TWRP recovery, i even tested it, but wasn't able to work with it, it was very slow and didn't found files i was looking for, i will regive it a try.
Edit : I have the exact same problem when flashing SuperSU from TeamWin recovery, everything act as i don't have SU, i can grant rights to anything i want it will still act as i don't have root, and SuperSU is unable to update it own binary at startup

Magissia said:
Hello, i have a problem with my TF101 (B70 if i'm right), ADB only work when i'm in recovery mode.
I lost root i don't know how and tried to regain it, but every rooting tools failled, i then discovered that commands wasn't working (even ls), but they do work in recovery mode (from /sbin).
When i try to flash a .zip from CWM , it seems that changes suposed to be applied to /system/bin aren't applied (SuperUser/SuperSU never find /system/bin/SU) but /system/bin/app correctly get updated.
I'd prefer to not wipe the device's data and repair it from it's current state if possible.
TF101's current state : Stock .27 guevor kernel 717, CWM non touch recovery
From recovery
ls -l /sbin
http://pastebin.com/tmyZagUk
ls -l /system/bin
http://pastebin.com/6tsPaPF0
ls -l /system/xbin
http://pastebin.com/D3jW5Sy3
If you need more info please tell
Bounty : I'll send Russian chocolat and candies to the one that will find how to fix this !
Click to expand...
Click to collapse
Hi, your busybox installation seems corrupt (ie busybox binary is missing). You can reinstall busybox to /system/bin (do make sure that /system is mounted) from inside CWM and everything shall be fine. Your root su also seems to exist and should be fine.
If you can't do it in CWM then you can try and connect to the tablet in normal use mode and then run /system/bin/su and you should be root. Then you can install busybox manually ( you'll need to upload the busybox binary to /data/local/tmp or something) and run:
/system/bin/toolbox chmod 755 /data/local/tmp/busybox ( or if you're in CWM make sure /data is also mounted and then run: /sbin/chmod 755 /data/local/tmp/busybox )
/data/local/tmp/busybox --install /system/bin ( Please verify syntax ).
Good luck!
Sent from my Transformer TF101G using xda app-developers app

idcrisis said:
Hi, your busybox installation seems corrupt (ie busybox binary is missing). You can reinstall busybox to /system/bin (do make sure that /system is mounted) from inside CWM and everything shall be fine. Your root su also seems to exist and should be fine.
If you can't do it in CWM then you can try and connect to the tablet in normal use mode and then run /system/bin/su and you should be root. Then you can install busybox manually ( you'll need to upload the busybox binary to /data/local/tmp or something) and run:
/system/bin/toolbox chmod 755 /data/local/tmp/busybox ( or if you're in CWM make sure /data is also mounted and then run: /sbin/chmod 755 /data/local/tmp/busybox )
/data/local/tmp/busybox --install /system/bin ( Please verify syntax ).
Good luck!
Sent from my Transformer TF101G using xda app-developers app
Click to expand...
Click to collapse
Hello, i cannot do anything if not under CWM (even ls gives a "not found" if not in CWM)
I tried /system/xbin/su and got a
"sh: /system/etc/mkshrc[8]: id: not found"
Rebooted in CWM and tried to install Busybox
i mounted /system /data and /sdcard
i created the folder /data/local/temp
cp /sdcard/busybox /data/local/temp
applied /sbin/chmod 755 to /data/local/temp/busybox
ran /data/local/temp/busybox --install /system/bin and got a "Invalid cross-device link" error on every commands busybox tried to install
http://pastebin.com/g3DMHbJz
Tried to install it on /system/xbin too, but same error
Note : When i use /system/xbin/su in CWM, it change name to [email protected] from ~# while it doesn't in normal mode
Edit : Titanium backup rework :
In CWM, i copied busybox to /system/bin, and i installed it to /system/bin from /system/bin
cp /data/local/temp/busybox /system/bin
/system/bin/busybox --install /system/bin
I'm now checking if only Titanium backup works or if everything else too
Thanks for your help, i don't know if it's done yet, but i made a progress using your information !
Edit 2 : Seems everything works, please send me a private message to talk about candies and chocolat

Magissia said:
Edit 2 : Seems everything works, please send me a private message to talk about candies and chocolat
Click to expand...
Click to collapse
Good to see everything works. Give the candy to some children in the neighborhood mate, I'm watching the calories
Cheers!
Sent from my Transformer TF101G using xda app-developers app

[Guide] [L5 II] Root LG Optimus L5 II E450

I had found a way to root L5 II, the method comes from a chinese tool:
1. (The address is in attached file)
Press the blue and white down arrow to download the tool
2. Enable Android debug mode
3. Execute the program, wait for the phone reboot.
4. Rooted!
It works on my e450!

tfe104270 said:
I had found a way to root L5 II, the method comes from a chinese tool:
1. (The address is in attached file)
Press the blue and white down arrow to download the tool
2. Enable Android debug mode
3. Execute the program, wait for the phone reboot.
4. Rooted!
It works on my e450!
Click to expand...
Click to collapse
This works perfectly on my LG E450 too ! But I want to change the Chinese SuperUser to SuperSU, did you try to do that already?
---------- Post added at 09:34 PM ---------- Previous post was at 08:58 PM ----------
Okay, I got SuperSu English version working on my LG E450. These are the steps I have taken.
1) Download SuperSU from the android market
2) Grant Permission for SuperSU to work ( Press the left button on the chinese dialogue )
3) When prompted to update the SU binary, tap on Update
4) Once Update is over, swipe to the Settings tab and select, "Install SuperSU in /system" , option.
5) After Phone restarts, you will find the Chinese SuperUser is not present, but the SuperSU is present.
6) now execute the following command in your terminal or command prompt
---------- For Windows Users ---------------
adb.exe shell "su -c 'mount -o remount,rw /system'"
adb.exe shell "su -c 'rm /system/bin/su'"
adb.exe shell "su -c 'rm /system/xbin/su'"
------------- For Mac/Linux Users ------------
adb shell "su -c 'mount -o remount,rw /system'"
adb shell "su -c 'rm /system/bin/su'"
adb shell "su -c 'rm /system/xbin/su'"
7) Now Open SuperSU and once again update SU Binary.
If you hve any question, please do reply me in this thread.

No luck on the E460
tfe104270 said:
I had found a way to root L5 II, the method comes from a chinese tool:
1. (The address is in attached file)
Press the blue and white down arrow to download the tool
2. Enable Android debug mode
3. Execute the program, wait for the phone reboot.
4. Rooted!
It works on my e450!
Click to expand...
Click to collapse
Not sure if I am doing something wrong but it seemed to do it however still no root access, thanks anyway

subho007 said:
This works perfectly on my LG E450 too ! But I want to change the Chinese SuperUser to SuperSU, did you try to do that already?
---------- Post added at 09:34 PM ---------- Previous post was at 08:58 PM ----------
---------- For Windows Users ---------------
adb.exe shell "su -c 'mount -o remount,rw /system'"
adb.exe shell "su -c 'rm /system/bin/su'"
adb.exe shell "su -c 'rm /system/xbin/su'"
.
Click to expand...
Click to collapse
edit: my phone has been Rooted now.. by other method will post my tutorial after a few days..
btw thanks for your help..

looking forward to tutorial
alley23 said:
edit: my phone has been Rooted now.. by other method will post my tutorial after a few days..
btw thanks for your help..
Click to expand...
Click to collapse
Looking forward to the tutorial, especially if it will work on the E460, pm me if you can and I will try it on the E460

subho007 said:
This works perfectly on my LG E450 too ! But I want to change the Chinese SuperUser to SuperSU, did you try to do that already?
---------- Post added at 09:34 PM ---------- Previous post was at 08:58 PM ----------
Okay, I got SuperSu English version working on my LG E450. These are the steps I have taken.
1) Download SuperSU from the android market
2) Grant Permission for SuperSU to work ( Press the left button on the chinese dialogue )
3) When prompted to update the SU binary, tap on Update
4) Once Update is over, swipe to the Settings tab and select, "Install SuperSU in /system" , option.
5) After Phone restarts, you will find the Chinese SuperUser is not present, but the SuperSU is present.
6) now execute the following command in your terminal or command prompt
---------- For Windows Users ---------------
adb.exe shell "su -c 'mount -o remount,rw /system'"
adb.exe shell "su -c 'rm /system/bin/su'"
adb.exe shell "su -c 'rm /system/xbin/su'"
------------- For Mac/Linux Users ------------
adb shell "su -c 'mount -o remount,rw /system'"
adb shell "su -c 'rm /system/bin/su'"
adb shell "su -c 'rm /system/xbin/su'"
7) Now Open SuperSU and once again update SU Binary.
If you hve any question, please do reply me in this thread.
Click to expand...
Click to collapse
How do you type :
- adb.exe shell "su -c 'mount -o remount,rw /system'"
- adb.exe shell "su -c 'rm /system/bin/su'"
- adb.exe shell "su -c 'rm /system/xbin/su'"
in my Command Prompt, thats not working,,,,,,
Please Help Me changing supersu to english!!!!!!!!!!!!!!

Works on e460?
CAn anyone tell me if this works on LG Optimus L5 II (LG e460)???

undon3 said:
CAn anyone tell me if this works on LG Optimus L5 II (LG e460)???
Click to expand...
Click to collapse
I bump this, I would very like to know too!

undon3 said:
CAn anyone tell me if this works on LG Optimus L5 II (LG e460)???
Click to expand...
Click to collapse
Yes this works for LG e460 too. You need to plug into the computer, start the program, wait for it to detect your phone, then click on root.

Rafito123 said:
How do you type :
- adb.exe shell "su -c 'mount -o remount,rw /system'"
- adb.exe shell "su -c 'rm /system/bin/su'"
- adb.exe shell "su -c 'rm /system/xbin/su'"
in my Command Prompt, thats not working,,,,,,
Please Help Me changing supersu to english!!!!!!!!!!!!!!
Click to expand...
Click to collapse
You need to have Android SDK installed for the above command to run. Or else you can download it from the attachments,

subho007 said:
Yes this works for LG e460 too. You need to plug into the computer, start the program, wait for it to detect your phone, then click on root.
Click to expand...
Click to collapse
Thank you very much! I'm assuming you actually tried it, if you didn't may I have the source of that information? You see I really wouldn't like to brick my new phone XD What if it somehow bricks anyway? How do you factory reset the E460?

Divergence-of-B said:
Thank you very much! I'm assuming you actually tried it, if you didn't may I have the source of that information? You see I really wouldn't like to brick my new phone XD What if it somehow bricks anyway? How do you factory reset the E460?
Click to expand...
Click to collapse
Factory reset is something along the lines of VOL-UP+POWER. I've reset a few times accidentally If it doesn't work, it should simply fail though. I can't see how it would brick anything.

spunkylm said:
Factory reset is something along the lines of VOL-UP+POWER. I've reset a few times accidentally If it doesn't work, it should simply fail though. I can't see how it would brick anything.
Click to expand...
Click to collapse
That's what I thought, I had just hacked my old P500 before but since that was a very common phone I was more confident with it, there is a bunch of stuff for the P500 around and pretty much nothing yet for the E460...

spunkylm said:
Factory reset is something along the lines of VOL-UP+POWER. I've reset a few times accidentally If it doesn't work, it should simply fail though. I can't see how it would brick anything.
Click to expand...
Click to collapse
actually it's VOL-DOWN+QUICK MEMO BUTTON+POWER for the E460

Also I'm afraid there are things you can do with root that hard reset can't undo.

mircea89fzr said:
actually it's VOL-DOWN+QUICK MEMO BUTTON+POWER for the E460
Click to expand...
Click to collapse
I knew I was going to be wrong if I posted it. I could do with a list of them for the e460. I usually reboot to recovery through adb. Still want to find a way of enabling fastboot though

spunkylm said:
I knew I was going to be wrong if I posted it. I could do with a list of them for the e460. I usually reboot to recovery through adb. Still want to find a way of enabling fastboot though
Click to expand...
Click to collapse
Do you have recovery on e460? how do you boot to recovery? I would do root if I could backup the entire system partition because if I root maybe I won't be able to install updates from LG.

mircea89fzr said:
Do you have recovery on e460? how do you boot to recovery? I would do root if I could backup the entire system partition because if I root maybe I won't be able to install updates from LG.
Click to expand...
Click to collapse
It's not like a CWM recovery where you can do things like that. It just allows the LG software to flash a kdz as far as I'm aware. You still can't access /system without remounting with root. To boot to it use "adb reboot recovery"

spunkylm said:
It's not like a CWM recovery where you can do things like that. It just allows the LG software to flash a kdz as far as I'm aware. You still can't access /system without remounting with root. To boot to it use "adb reboot recovery"
Click to expand...
Click to collapse
Do you have the kdz for E460? I would need it if something goes wrong.

mircea89fzr said:
Do you have the kdz for E460? I would need it if something goes wrong.
Click to expand...
Click to collapse
I downloaded V10H_00.kdz (02 UK) from here: http://luivit.altervista.org/lg-phone-firmware/index.php?id_mod=23.
See if they have one for your version, but make sure to get the 460 version as their are a few other models jumbled in.

Full Root for Nook Glowlight

It took some doing, but after following the instructions in this link:
http://forum.xda-developers.com/showthread.php?t=2559915
I was finally able to root my Nook Glowlight. The instructions are kind of sprawled out and extremely unclear so I will sum up.
As always, you will need the ADB. In order to install the ADB, you need the Java Development Kit and the Android Studio (formerly known as the Android SDK)
http://www.oracle.com/technetwork/java/javase/downloads/index.html
http://developer.android.com/sdk/installing/studio.html
How to obtain root via ADB: The ONLY way you can root is using Windows. I was successful on Windows 7 32 bit, but it may be possible on other versions.
step 1) install bootloader driver.
You need to grab the drivers from here (bnusbdrivers.zip):
http://forum.xda-developers.com/showpost.php?p=49665945&postcount=279&nocache=1&z=184593200683593
then, open the Device Manager (on Windows). Be ready to right click on the new device 'omap3660' that shows.
With the nook turned completely off, plug in a USB cable. you will have less than 3 seconds to right click the new omap3660 device that shows up in the system profiler.
If you were successful and you right clicked on it in time, manually install the Barnes & Noble USB driver (there are entries added to the generic Google drivers for both the TI Omap 3660 bootloader and the ADB device after you modify the uRamdisk later on)
***NOTE***
If you WEREN'T successful on your first try (took me THREE times to get to it in time), you aren't going to get another chance to install the drivers. At least not easily anyway, because after Windows tries to automatically install the drivers for the bootloader and fails, it will disregard the device any time it shows up after that. So, you are going to need to delete the registry entries that it created, which in my experience was easier said than done. Even admin access was not sufficient to make the necessary changes to the registry.
You will need to launch regedit.exe using another tool called psexec which is available here:
http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
after you download the pstools package, copy those .exe files to C:\Windows\System32\ (in order to add them to $PATH in cmd.exe)
Then, once you've installed the pstools commands to C:\Windows\System32\, run cmd.exe as admin (right click it and select 'run as administrator') and then open regedit.exe with the following command
Code:
psexec -s -i -d regedit.exe
Then, once regedit is open you need to find the keys created by the Nook bootloader and delete them. The Nook bootloader's device ID is 0451:d00e
You are going to be looking in HKEY_LOCAL_MACHINE\Current Control Set\enum\usb\ for the keys with the bootloader's device IDs. There may also be keys generated in control set 001 and 002 as well. Delete all of those keys and then reboot your computer. Then with the nook power off completely, repeat the process from the first step. eventually you will be successful installing the bootloader driver.
Step 2) temporarily boot with uRamdisk-noogie
you need to download omaplink.exe from here:
http://www.temblast.com/android.htm
and you also need to download the four files which allow you to temporarily mount the boot partition; omap3_aboot.bin, u-boot-ng2-exp-v03.bin, uImage-ng2-130-stk and uRamdisk-noogie.
They are available here:
http://forum.xda-developers.com/showpost.php?p=49779966&postcount=285
download usbboot-ng2-images-noogie-v1.zip
The next part is easy.
Extract the .zip file and then fire up cmd.exe. cd into the directory of the newly extracted .zip
in the new working directory, enter the command
Code:
omaplink omap3_aboot.bin u-boot-ng2-exp-v03.bin uImage-ng2-130-stk uRamdisk-noogie
Then, with the Nook powered all the way off and omaplink running, plug it in and a few seconds later, after the device boots up all the way, you will be looking at the contents of the boot partition instead of the internal storage like normal.
Step 3) Edit uRamdisk
you will need to download bootutil.exe from here
http://www.temblast.com/android.htm
copy bootutil.exe to C:\Windows\System32
with the boot partition mounted, copy uRamdisk to your computer and extract the files init.rc and default.prop, eg;
Code:
bootutil /x /v uRamdisk init.rc default.prop
then using notepad++ (available here: http://notepad-plus-plus.org/) edit the files as follows
default.prop
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
and
init.rc
comment out lines 375 and 392-399
(do this by adding a # to the beginning of the line)
uncomment line 215
(do this by deleting the # at the beginning of the line)
save both files and then repack them into uRamdisk
Code:
bootutil /r /v uRamdisk init.rc default.prop
copy uRamdisk back onto the Nook, eject the disk and power off the device. Reboot and you should be able to connect to ADB via WiFi
eg;
Code:
adb connect 192.168.0.10
replacing '10' with whatever IP your Nook is grabbing from your router.
Step 4) Full Root
at this point, you have root access via ADB only. You will not have root access in any apps like Root Explorer, Terminal, TiBackup, etc.
In order to finish PROPERLY rooting your Nook, you need to install 'su' to /system/bin/ and install the superuser.apk
Code:
adb connect 192.168.0.10
adb shell mount -o remount, rw /system
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
adb install superuser.apk
reboot your device one more time and then you will be fully rooted.
*** Note ***
this devices firmware seems to be a strange hybrid between donut and eclair, although it purports itself to be Android 2.1. The Superuser.apk and su binary came from an old Cyanogenmod 4.6 build in case anyone was wondering (Android Donut). The ones from Cyanogenmod 5 (Android Eclair) do not work. you will get the 'install failed older sdk' error.

installing busybox
I tired installing busybox by using the stericson busybox pro.apk. It would always freeze at 6.47%.
I figured out that if I grabbed an older version of the busybox binary and pushed it to /system/xbin manually and then chmodded it to the proper permissions, auto updates and proper symlinking work using the busybox app
Code:
adb shell mount -o remount, rw /system
adb shell mkdir -p /system/xbin
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
Then reboot, and run the busybox app to update and create symlinks.
enjoy!

installing nano and bash
Code:
adb connect 192.168.0.10
adb shell
mount -o remount, rw /system
adb push nano /system/xbin/
chmod 6755 /system/xbin/nano
adb push bash /system/xbin/
chmod 6755 /system/xbin/bash
bash
mv /system/bin/sh /system/bin/sh.bak
ln -s /system/xbin/bash /system/bin/sh
chmod 6755 /system/bin/sh
adb push profile /system/etc/
adb push terminfo /system/etc/
and then in terminal emulator under 'Preferences' change the initial command to
Code:
export TERMINFO=/system/etc/terminfo;export TERM=linux;export HOME=/sdcard;
and finally
Code:
adb push bashrc /sdcard
adb shell
mv /sdcard/bashrc /sdcard/.bashrc
exit
nano works just fine via ADB, but because of lack of 'ctrl' key (and physical buttons to assign it to) you won't be able to write files (ctrl+o) using the terminal on your nook. But between having full proper root access, busybox, a proper bash terminal emulator and nano for editing config files, this should REALLY extend the usefulness of your Nook Glowlight. It should work just fine on other versions of Nook too.

Hi N00b-un-2,
Many thanks for your summary!
There is one important edit that I think you missed,
in init.rc you also need to:
Line #375, comment out "disabled" with a # at the start of the line.
(see http://forum.xda-developers.com/showthread.php?p=49070213#post49070213)
without this I couldn't get adb to connect.
And since you already made it very noob friendly, might I suggested you clarify:
Line #215 remove # to enable adb over wifi
(rather than search for 5555)
Also, I'm not expert, but I believe the commands to get superuser on the device are (at least it worked for me):
adb connect 192.168.x.x
adb shell mount -o remount, rw /system
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
adb install superuser.apk
Finally, I'm not sure if this is important, but maybe remount system as read only again:
adb shell mount -o remount, ro /system
Thanks again, nice work!
---------- Post added at 01:48 PM ---------- Previous post was at 01:10 PM ----------
Hi again,
had similar issues with installing busybox, here's what worked for me (note needed to run su to create dir):
adb shell mount -o remount, rw /system
adb shell /system/bin/su
adb shell mkdir -p /system/xbin
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
cheers.

As far as remounting /system as ro, I would HIGHLY recommend just rebooting at this point, otherwise your nook might be stuck in a weird pseudo-rooted state. Probably won't cause any problems, but why risk it?
Thanks for clarifying the line number. I will make the appropriate edits to my instructions. I was working off the top of my head and couldn't remember what exact line the ADB over TCP config was, as I just used ctrl+w '5555' to find it myself.
There are several pre-edited uRamdisk images floating around the forum with various features enabled which would be easier for noobs than extracting the config files and manually editing and then repacking them. In the future I'll probably throw those on here as well.
darz said:
Hi N00b-un-2,
Many thanks for your summary!
There is one important edit that I think you missed,
in init.rc you also need to:
Line #375, comment out "disabled" with a # at the start of the line.
(see http://forum.xda-developers.com/showthread.php?p=49070213#post49070213)
without this I couldn't get adb to connect.
And since you already made it very noob friendly, might I suggested you clarify:
Line #215 remove # to enable adb over wifi
(rather than search for 5555)
Also, I'm not expert, but I believe the commands to get superuser on the device are (at least it worked for me):
adb connect 192.168.x.x
adb shell mount -o remount, rw /system
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
adb install superuser.apk
Finally, I'm not sure if this is important, but maybe remount system as read only again:
adb shell mount -o remount, ro /system
Thanks again, nice work!
---------- Post added at 01:48 PM ---------- Previous post was at 01:10 PM ----------
Hi again,
had similar issues with installing busybox, here's what worked for me (note needed to run su to create dir):
adb shell mount -o remount, rw /system
adb shell /system/bin/su
adb shell mkdir -p /system/xbin
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
cheers.
Click to expand...
Click to collapse

N00b-un-2 said:
There are several pre-edited uRamdisk images floating around the forum with various features enabled which would be easier for noobs than extracting the config files and manually editing and then repacking them. In the future I'll probably throw those on here as well.
Click to expand...
Click to collapse
Would have been good if I could have easily found a pre-edited image, but your instructions were a great alternative, thanks again

darz said:
Would have been good if I could have easily found a pre-edited image, but your instructions were a great alternative, thanks again
Click to expand...
Click to collapse
Sorry for the really noob question, I have rooted, wifi adb running and installed apps as per your instructions, but I can't seem to access any of it on the nook. How can I get access to the launcher I installed?
You mentioned pre-edited images, do any of those come with the apps I need to get access to a custom launcher?
Cheers,
Dariusz
==============
Updated: All sorted
==============
For some reason had some issues with ADW launcher, Launcher pro worked fine.
ps I think I made a mistake with the su step I suggested, if you run a one line shell command I don't think it keeps su privileges, so I believe you need to run commands within the shell as per below:
adb shell
mount -o remount, rw /system
/system/bin/su
mkdir -p /system/xbin
exit
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk

Noob
Hey guys any instructions noob friendly or a video in youtube,i stick up at dab connect 192.168.0.10.I dos't have a Windows PC and using Mac whit Parallels Desktop.Is it possible instructions for Mac?

The above instructions from N00b-un-2 should work fine running a vm with parallels on your Mac.
OB
Sent from my SPH-D710VMUB using Tapatalk 2

valentin1985 said:
Hey guys any instructions noob friendly or a video in youtube,i stick up at dab connect 192.168.0.10.I dos't have a Windows PC and using Mac whit Parallels Desktop.Is it possible instructions for Mac?
Click to expand...
Click to collapse
Before you perform the adb connect step you need to find out what your IP address is:
On your nook, click on the settings icon in the top right corner and then select "Change"
Under Wireless Networks, select the wifi name that you are already connected to (where it says "Connected to the internet")
This will display your connection details, remember that IP address
Now go back to your pc and type:
adb connect [IP address]

darz said:
Before you perform the adb connect step you need to find out what your IP address is:
On your nook, click on the settings icon in the top right corner and then select "Change"
Under Wireless Networks, select the wifi name that you are already connected to (where it says "Connected to the internet")
This will display your connection details, remember that IP address
Now go back to your pc and type:
adb connect [IP address]
Click to expand...
Click to collapse
BIG HINT! If you're using Powershell ISE, you have to type .\adb.exe connect [IP address] or else it won't recognize "adb" as an executable!
Don't ask why, because I don't know. :?

thenookieforlife3 said:
BIG HINT! If you're using Powershell ISE, you have to type .\adb.exe connect [IP address] or else it won't recognize "adb" as an executable!
Don't ask why, because I don't know. :?
Click to expand...
Click to collapse
So far so good,but now what?

valentin1985 said:
So far so good,but now what?
Click to expand...
Click to collapse
I just gave a little tip on Powershell ISE. I do not know much about the Nook GlowLight rooting process, as I have a NSTG, not a NG. Ask someone else.

thenookieforlife3 said:
I just gave a little tip on Powershell ISE. I do not know much about the Nook GlowLight rooting process, as I have a NSTG, not a NG. Ask someone else.
Click to expand...
Click to collapse
Yes,i try whit dis command .\adb.exe connect 192.168.0.9 but result is the same.

valentin1985 said:
Yes,i try whit dis command .\adb.exe connect 192.168.0.9 but result is the same.
Click to expand...
Click to collapse
But that's okay! What I said was, if you are using the command program Powershell ISE, do it that way instead. But you are just using cmd.exe, not Powershell ISE!
In cmd.exe, which is what you are using, it is not neccessary to type .\adb.exe. Just type adb.
From there, ask someone else in this thread.

thenookieforlife3 said:
But that's okay! What I said was, if you are using the command program Powershell ISE, do it that way instead. But you are just using cmd.exe, not Powershell ISE!
In cmd.exe, which is what you are using, it is not neccessary to type .\adb.exe. Just type adb.
From there, ask someone else in this thread.
Click to expand...
Click to collapse
I prefer to use ConEmu or Console2 when I am forced to use Windows. Not a big fan of CMD.EXE or Powershell/PowershellISE. there are plenty of other CLI alternatives out there

N00b-un-2 said:
I prefer to use ConEmu or Console2 when I am forced to use Windows. Not a big fan of CMD.EXE or Powershell/PowershellISE. there are plenty of other CLI alternatives out there
Click to expand...
Click to collapse
Well, as I ONLY use Windows and Powershell ISE has a nice-enough layout for my purposes, I use it. That's why I gave a tip on it.

Actually on a lot of installs just typing adb in the command console won't work either unless it's got the path variable set up correctly, I find it easiest to just right click and choose run as administrator, no need for the path to be setup.
OB
Sent from my SPH-D710VMUB using Tapatalk 2

FW 1.2.1
Hi guys,
thanks for creating this thread. I was wondering if this rooting procedure was tested with the firmware 1.2.1 ?

real-6 said:
Hi guys,
thanks for creating this thread. I was wondering if this rooting procedure was tested with the firmware 1.2.1 ?
Click to expand...
Click to collapse
This rooting procedure is for the new Nook GlowLight with firmware 1.3.1. Your device is a Nook Simple Touch with GlowLight, which can be rooted very easily using the rooting package here.

root for 306SH

So I'll update randomly...
boot.img and recovery.img -> https://drive.google.com/file/d/0B5QYBzdG6RuyZy1TSHc2VDVhY2M/view?usp=sharing
temp root:
Code:
adb push root /data/local/tmp
adb push wpoff /data/local/tmp
adb push fbunlock /data/local/tmp
adb push recovery.img /data/local/tmp
adb push boot.img /data/local/tmp
adb shell
$ [COLOR="Red"]chmod 755 /data/local/tmp/root[/COLOR]
$ [COLOR="Red"]chmod 755 /data/local/tmp/wpoff[/COLOR]
$ [COLOR="Red"]chmod 755 /data/local/tmp/fbunlock[/COLOR]
$ /data/local/tmp/root
...
#
defeat WP:
Code:
# /data/local/tmp/wpoff --unprotect-all
check WP status(optional):
Code:
# /data/local/tmp/wpoff --dump
If you see it's all zeroes there it means good, or if there are many 5555 it means NG.
unlock bootloader:
Code:
# /data/local/tmp/fbunlock
install TWRP and patched boot:
Code:
# dd if=/data/local/tmp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
# dd if=/data/local/tmp/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
install SuperSU:
Code:
FLASH SUPERSU LIKE OLD DAYS
Why patch boot?
Cos MIYABI stops ptrace, some apps depends on it won't work properly.
Chinese here:
禁止转载到国内论坛，禁止用于商业用途。日版不会有的。
Note:
a. Remember to rename recovery.00X.zip to recovery.zip.00X before unzipping!
b. If you don't flash boot.img before install SuperSU, you will end up in boot loop. To restore, delete /system/xbin/daemonsu.
Attachments will be uploaded soon.

Hi tewilove, many thanks for publishing this. Amazing work! And a big time saver

tewilove tnx allot !!
hey some one know how can i put su inside in system and then to use SuperSU ?

thank you a lot

thanks but i can not use root app and super su can not install bin su
thank you for your help

tewilove said:
Tested with a 306SH with SW version S4081.
How to:
https://youtu.be/UJs7ruckGgc
This is v1, since the shell code has to be improved yet(WIP).
It only obtains temp root with kernel context. The left things are changing to init context, disable mmc_protect_part, disable miyabi LSM.
There might be v2, which solves all above, if I have time.
And it also works with many other devices.
For example, 305SH, MI4C, SH-01G.
If it keeps crashing, it should be my hard coded offsets.
PS: Please don't reshare this thread.
PS: Chinese: 请不要转载到贴吧，论坛，谢谢。
Click to expand...
Click to collapse
thank you for your help 谢谢某因幡分享

Please I'd like to know how you did that.could you be more clear, a step by step maybe?
Sent from my D6616 using XDA Free mobile app

salmanaman said:
Please I'd like to know how you did that.could you be more clear, a step by step maybe?
Sent from my D6616 using XDA Free mobile app
Click to expand...
Click to collapse
you can watch the video that tewilove make for us .. but we need to wait when some one unlock protect bcs after you restart phone root will disappear..

tewilove said:
Tested with a 306SH with SW version S4081.
Click to expand...
Click to collapse
How can I know that I got the temporary root? Is this step in the input ID?

all step working on my 305sh like youtube video but supersu not working and root checker say me no rooted

soudara said:
all step working on my 305sh like youtube video but supersu not working and root checker say me no rooted
Click to expand...
Click to collapse
yes we know about this .. i try to remount system ( with this command : busybox mount -o remount,rw /system) to get permission but my device is restart when i try .. maybe its from this write protection that @tewilove tell us .. if he can tell us how we can install su in system if its possible for now .. ?

ok so for the moment is useless ?

soudara said:
all step working on my 305sh like youtube video but supersu not working and root checker say me no rooted
Click to expand...
Click to collapse
me too?maybe just kernel root??
---------- Post added at 12:48 PM ---------- Previous post was at 12:31 PM ----------
loonbg said:
yes we know about this .. i try to remount system ( with this command : busybox mount -o remount,rw /system) to get permission but my device is restart when i try .. maybe its from this write protection that tewilove tell us .. if he can tell us how we can install su in system if its possible for now .. ?
Click to expand...
Click to collapse
yea?rootxplore and xposed said no root?

I don't think that folks are understanding what "temp" root means. This solution allows you to achieve root for the current shell session. This does not install the additional binaries to allow other applications to use root access.
With that being said, I am wondering if we can use this temporary elevated access to correct the vulnerability outlined in CVE-2015-1474 affecting /system/lib/libui.so that Sharp has neglected to address in previous OTA updates. The only "corrected" libui.so that I have been able to locate was compiled for v5.0.1 so I am afraid that file would not be compatible with this earlier version of Android on the 306SH. I am not really savvy with in depth programming to be able to fully investigate this and develop a viable solution... anyone who would be able to point me in the right direction would receive many thanks. :banghead:
My apologies if this should have been posted in a separate thread.

awesom! it worked in my 306sh with root permission acquired in shell.

can you use root app and install super su ?

Write protection is keeping us from remounting /system as rw. This prevents us from doing anything that would have any type of impact on the current situation. I want to experiment with attempting to mount partitions with the device powered off... but my device is encrypted so I am unable to access the shell with device off until I perform a factory reset. I am planning on doing that tonight so hopefully I will be able to report back with more information soon.
Sent from my 306SH

soudara said:
can you use root app and install super su ?
Click to expand...
Click to collapse
No. We are working on it though.
On another note, I can't get this temp root to work.
Video of what happens is linked. (too large to attach)
https://mega.co.nz/#!blNTjbhS!p2ljioY_43xlWkpu3EWpj8LvfMVP5eushZT23KLPASk

TechInMD said:
Write protection is keeping us from remounting /system as rw.
Click to expand...
Click to collapse
So I assume, from the quoted text, you have tried mounting /system as rw while in the temp root shell session?

Yes. I tried using the mount command both directly from the root shell prompt plus I tried using busybox to mount also. There seem to be slight variations between them. Also, not sure if it is relevant but I attempted it both through adb and in terminal on the device. I can get to the root prompt but not further.
Sent from my 306SH