[Q] Older Xoom, root problems, read this ! (SOLVED) - Xoom Q&A, Help & Troubleshooting

As some of you may know I've not been able to unlock ro root my Xoom, much less update the android version. I'm still running 4.1.2, that was last updated by Google. (I have two Xooms)
I have tried everything I've found on this site, and over at the Xoom forums, to no avail. I did, finally get one of them unlocked by switch from a Linux PC to an old XP box.
But, nothing else has come even close to working.
Yesterday I found this,
http://www.droid-life.com/2011/02/25/how-to-root-the-motorola-xoom/
It seems (to this relative newbie) that Droid Life offers a bit more information about rooting and such??? An example below:
---------------------------------------------
5. Type: adb reboot bootloader
6. Type: fastboot flash boot rootboot.img
7. Type: fastboot reboot
8. Wait for your device to reboot all the way.
9. Type: adb remount
10. Type: adb push su /system/bin
11. Type: adb shell ln –s /system/bin/su /system/xbin/su
12. Type: adb shell chmod 4755 /system/bin/su
13. And now this next step you have a couple of options.
Option A: Push Superuser.apk in adb. Type: adb push Superuser.apk /system/app
Option B: Exit adb and download Superuser app from the market.
--------------------------------------------------------
Why couldn't I find this info here, or at the Xoom forums? update: I found it on the Xoom forums
NOTE I still haven't tried it to see if it will work, but the "placement info" seems pretty relevant.

Duh, I get it now.
OK, I get it now. $$ is king.

Related

[Huawei IDEOS U8150] How to gain root access

I hold no responsibility to how you use or not use this info and if you brick phone - you do this at your own risk
There is a couple away you can go about gaining root access with this phone I have tested all 3 ways but only had success with 2 of them.
a) You can download 'z4root' from the Android Market (If is still available) or search XDA forums for it.
b) Search the XDA forums for 'SuperOneClick' which requires mono to work on Linux. I have read people that have had success with 'SuperOneClick' but that was not the case for me.
c) My preferred method:
Prerequisite:
knowledge of Linux and Terminal
knowledge of ADB (guide available in forums)
I did all this using Debian (testing) 64bit, Android SDK.
Creating correct permissions to access the phone via USB:
i) create
Code:
/etc/udev/rules.d/51-android.rules
ii) in the file put
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
iii) then
Code:
chmod a+r /etc/udev/rules.d/51-android.rules
iv) restart udev or reboot
Downloading and/or Installing required software:
1) Downloading and installing the android-sdk from: developer.android.com/sdk/index.html
2) Downloading and extracting 'SuperOneClick' (you will only need these 5 files: rageagainstthecage, sqlite3, su, busybox and superuser.apk)
3) Copy rageagainstthecage, sqlite3, su, busybox and superuser.apk into the platform-tools directory of android-sdk. Put phone in debug mode.
4) From a terminal (command line) change to the android/platform-tools directory and carefully do these steps.
Check to see if adb can see your phone properly:
Code:
./adb devices
You should see the serial number of you device, if you see bunch of '?' you have done something wrong.
Now for the fun part rooting the phone: <= no phun intended hehe
Code:
./adb push rageagainstthecage /data/local/tmp/rageagainstthecage
Code:
./adb shell
Code:
cd /data/local/tmp
Code:
chmod 0755 rageagainstthecage
Code:
./rageagainstthecage
5) Now wait until you get kicked out from adb before you do the following:
Code:
./adb shell
If everything worked now you should see a "#" instead of the "$" you saw previously in the adb shell which means you shouldn't get "permission denied" in the following steps:
Code:
mount -o rw,remount /dev/block/mdtblock4 /system
Code:
exit
Code:
./adb push su /system/bin/su
Code:
./adb push busybox /system/bin/busybox
Code:
./adb push sqlite3 /system/bin/sqlite3
Code:
./adb push Superuser.apk /system/app/Superuser.apk
Code:
./adb shell
Code:
cd /system/bin
Code:
chmod 4755 su
Code:
chmod 4755 busybox
Code:
chmod 4755 sqlite3
Code:
./adb reboot
Now you should be able to use apps like 'Cache Cleaner NG', 'Root Explorer', 'SetCPU' etc that require root access to work correctly.
Enjoy
Guide reflash FW for those who did some damage:
* Download from here that you want to install the FW
* Copy the folder in the microSD DLOAD (with the file inside UPADATE.APP)
* From phone off, Volume + Hold down RED BUTTON UP and power button.
* start the firmware upgrade, take a few minutes and then restart the phone . is a bit slow, do not be afraid, let him work and then back on (like the first time)
Help to get into recovery mode:
* down the 'volume up 'and 'green button'and then switch the device
Guide to bootloader mode:
* switch off, press and hold power button + volume down + red key
Overclock
Can this fone be oveclocked
SethIsHere said:
Can this fone be oveclocked
Click to expand...
Click to collapse
yes it can be OCed, I recommend using setCPU from the market
SethIsHere said:
Can this fone be oveclocked
Click to expand...
Click to collapse
Yes it can, to a Maximum of 600mhz (0.6 ghz) on the stock kernel
setCPU is no longer available on the market for free afaik.
Also can someone better translate the instructions to get into recovery mode? i can barely make sense of the above instructions ^^^
.produkt-R said:
Also can someone better translate the instructions to get into recovery mode? i can barely make sense of the above instructions ^^^
Click to expand...
Click to collapse
does this help:
http://forum.xda-developers.com/showpost.php?p=10371747&postcount=5
quail said:
does this help:
http://forum.xda-developers.com/showpost.php?p=10371747&postcount=5
Click to expand...
Click to collapse
Helped, Thanks.
Although after reading the entire page, i wonder if i should have a Recovery ROM installed. But i wonder if the phone will be left in it's current working state after installing it ?
i used z4root, worked fine for me
quail said:
Code:
chmod 4755 su
Code:
chmod 4755 busybox
Code:
chmod 4755 sqlite3
Click to expand...
Click to collapse
I think only "su" should be 4755 (setuid root), busybox and sqlite3 should just be 0755? Thanks for the instructions.
pb05life said:
i used z4root, worked fine for me
Click to expand...
Click to collapse
Ok I figured it ill shut up you have to use crappy dos command prompt and type everything in manually install proggies lol Google must die!
quail said:
Creating correct permissions to access the phone via USB:
i) create
Code:
/etc/udev/rules.d/51-android.rules
ii) in the file put
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
iii) then
Code:
chmod a+r /etc/udev/rules.d/51-android.rules
iv) restart udev or reboot
Click to expand...
Click to collapse
Anyone know this part for windows XP?Not linux?
I got to rageagainstthecage and it says permission denied.
fvckyougooglescammer said:
So would you tell us, exactly how you did it?
Without using the market place?
Because I have tried 100 things downloaded all that junk wasted 5 hours.
And I do not know how to run the z4root on my phone.
I do not want to install another ROM.
I do not know why you can not run z4root and a file manager from the SD card I have tried methods with the SDK they are total rubbish.
Once again *without* using the market place.
Thanks
Click to expand...
Click to collapse
Download it mediafire.com/u8150
Sent from my Ideos using XDA App
could you explain why you prefer this way instead using z4root?
nitro-ale said:
could you explain why you prefer this way instead using z4root?
Click to expand...
Click to collapse
I have Z4root on the phone and its supposedly rooted.
Yet, I can install apps from PC onto phone, but can not uninstall them.
Adb always gives me failure.
And if I try from shell it always says permission denied.
tilal6991 said:
Download it
Sent from my Ideos using XDA App
Click to expand...
Click to collapse
Hi thanks downloaded it fine its on the phone but this doesn't tell me how to remove apps.
I have been able to install but not remove adb always says failure.
Thanks man,
Just worked perfectly on my IDEOS brought from 2degrees in NZ.
The copy of SuperOneClick that I downloaded contained a file called su-v2 instead of su. In order to get the hack to work I had to rename su-v2 to su before running ./rageagainstthecage . Pretty obvious, but it might help someone out.
Thanks
fvckyougooglescammer said:
I have Z4root on the phone and its supposedly rooted.
Yet, I can install apps from PC onto phone, but can not uninstall them.
Adb always gives me failure.
And if I try from shell it always says permission denied.
Click to expand...
Click to collapse
I followed your instructions and installed SetCPU to test my phone was rooted. It worked great! Thanks.
I still have a problem. When I try adb root it still says "adbd cannot run as root in production builds". I'm trying this to be able to control my phone with pc mouse/keyboard with androidscreencast.
Any suggestions will be much appreciated.
Answering to myself: I updated my phone with FUSIONideos 1.5 and now adb runs as root without problems.
Z4root
http://forum.xda-developers.com/showthread.php?t=833953
Worked for me
Does it removes simlock I have Huawei U8150 IDEOS Android phone with career lock ( Simlock ), so will this remove it
can there be a batch file / command / app for all this, too techy out there
also how to setup the environment to run these commands, i m windows user can i do it ?

Huawei Ideos Super FAQ

This is an FAQ for the Huawei Ideos as there have been many questions on how to do the same things. Hopefully this should help. There are other FAQs but this one tries to compile as many as it can into one FAQ.
Feel free to reply to this if there are any questions or if you want me to make any additions. The FAQ won't be complete to begin with but I will add as I get time.
One thing I will say is that I WON'T TAKE RESPONSIBITY IF YOU DAMAGE YOUR PHONE. I AM PROVIDING THE INFORMATION AND WILL TRY TO HELP YOU IF SOMETHING BAD HAPPENS BUT I CAN'T TAKE ANY RESPONSIBILITY
1. How to root the IDEOS
This can be done quite simply by adapting what quail wrote:
There is a couple away you can go about gaining root access with this phone I have tested all 3 ways but only had success with 2 of them.
a) You can download 'z4root' from here (WORKS)
b) Search the XDA forums for 'SuperOneClick' which requires mono to work on Linux. I have read people that have had success with 'SuperOneClick' but that was not the case for me. (HAVEN'T CHECKED)
c) My preferred method: (HAVEN'T CHECKED)
Prerequisite:
knowledge of Linux and Terminal
knowledge of ADB (guide available in forums)
I did all this using Debian (testing) 64bit, Android SDK.
Creating correct permissions to access the phone via USB:
i) create
Code:
/etc/udev/rules.d/51-android.rules
ii) in the file put
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
iii) then
Code:
chmod a+r /etc/udev/rules.d/51-android.rules
iv) restart udev or reboot
Downloading and/or Installing required software:
1) Downloading and installing the android-sdk from: developer.android.com/sdk/index.html
2) Downloading and extracting 'SuperOneClick' (you will only need these 5 files: rageagainstthecage, sqlite3, su, busybox and superuser.apk)
3) Copy rageagainstthecage, sqlite3, su, busybox and superuser.apk into the platform-tools directory of android-sdk. Put phone in debug mode.
4) From a terminal (command line) change to the android/platform-tools directory and carefully do these steps.
Check to see if adb can see your phone properly:
Code:
./adb devices
You should see the serial number of you device, if you see bunch of '?' you have done something wrong.
Now for the fun part rooting the phone: <= no phun intended hehe
Code:
./adb push rageagainstthecage /data/local/tmp/rageagainstthecage
Code:
./adb shell
Code:
cd /data/local/tmp
Code:
chmod 0755 rageagainstthecage
Code:
./rageagainstthecage
5) Now wait until you get kicked out from adb before you do the following:
Code:
./adb shell
If everything worked now you should see a "#" instead of the "$" you saw previously in the adb shell which means you shouldn't get "permission denied" in the following steps:
Code:
mount -o rw,remount /dev/block/mdtblock4 /system
Code:
exit
Code:
./adb push su /system/bin/su
Code:
./adb push busybox /system/bin/busybox
Code:
./adb push sqlite3 /system/bin/sqlite3
Code:
./adb push Superuser.apk /system/app/Superuser.apk
Code:
./adb shell
Code:
cd /system/bin
Code:
chmod 4755 su
Code:
chmod 4755 busybox
Code:
chmod 4755 sqlite3
Code:
./adb reboot
Now you should be able to use apps like 'Cache Cleaner NG', 'Root Explorer', 'SetCPU' etc that require root access to work correctly.
Enjoy​
2. How to flash the Ultrakiller Recovery Image
Now this has been covered many times but there have been a lot of problems with the BSOD on the IDEOS. A few days ago Ultrakiller came up with a solution that works regardless of the LCD type. Now this was distributed as an IMG file so many people were confused so here is a link to one with everything you need included. All I did was remove the amon'ra image and copied the Ultrakiller recovery IMG to the folder and edited the scripts to point to the new file.
After you download the file:
* Put your device in bootloader mode - turn it off, then press the power button while holding the 'Volume Down' and 'End (Red)' keys (Yes, bootloader is just the IDEOS logo) WHILE YOUR DEVICE IS PLUGGED IN
* WINDOWS - double click 'install-recovery-windows.bat'
* MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-recovery-mac.sh' followed by './install-recovery-mac.sh'
* LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-recovery-linux.sh' followed by './install-recovery-linux.sh'​
See Q3 if you have Windows and the prompt hangs on "Waiting for Device"
3. How to solve problems with drivers on Windows in bootloader mode?
1. Unplug your phone
2. Download and install PDANet from here - at the end of the setup it will tell you to plug in your phone - do that
3. Put the phone into bootloader (See Q2 above)
4. Go to device manager and right click on "Android 1.0" and click "Update drivers"
5. Click "No, not this time" and Next
6. When it asks you where to look for drivers point it to PDANet's install location
7. Hopefully it should find the driver and prompt you to install it - it will take some time
8. You can now access your device in bootloader!​
Thanks to the following people:
Quail for the base of the guide and the ROM I'm using - it's amazing BTW
Ultrakiller for the recovery image
Changelog:
21/01/2010: Initial writeup
22/01/2010: Added Q3 and made some minor changes​
i unfortunately deleted a system app and upon restarting my phone it wont boot.....it keeps hanging at the startup and reboots.. help me how to system restore...
Hi - the Ultrakiller recovery IMG in the ZIP from the Link above is "Ultrakiller.img.img". Dunno if it didnt work cause of this - sry didnt test, just downloaded new Ultrakillers "UltraJack-Recovery_v4.6.2.img", saved into that folder and changed the .bat to "fastboot-windows.exe flash recovery UltraJack-Recovery_v4.6.2.img" and it worked for me Even superuser.apk didnt work for usb-root but z4root does it perfect and DroidExplorer showing files now .
Thanks so far to all investing their time here
P.S.: the HUAWEI background of Ultrakillers recovery is very delicious
General guide to Flash ROM
Can you please provide a detailed guide for flashing Huawei Ideos. Because it is super guide. So it must contain this topic also.
I want to flash official ROM on following link:
http://forum.xda-developers.com/wiki/index.php?title=Huawei_U8150_IDEOS
Waiting for your response
yrnehukuht said:
i unfortunately deleted a system app and upon restarting my phone it wont boot.....it keeps hanging at the startup and reboots.. help me how to system restore...
Click to expand...
Click to collapse
Dear have u find out the solution of this problem?? COZ im also suffering from this if u find it then plz tell me [email protected]
I have downloaded a rom from xda-developers wiki from this link
http://forum.xda-developers.com/wiki/index.php?title=Huawei_U8150_IDEOS
then updated my device software by going in to update mode(press vol up + end key + power button) .
This step returned me my original recovery.
But I am not going to recommend it bcoz i am facing problems like my cd drive which is automatically displayed has become inaccessible.
I am having problem to copy files to sd card.
My upgrade mode is not working now.
all these things were working immediately after the above mentioned process but I am now stuck with these things.
I think it is because i have flashed lower version number of rom on phone.
If you want to recover recovery mode only then I have successfully flashed UltraJack-Recovery 5.2.1 from this link
http://forum.xda-developers.com/showthread.php?t=860189&page=24
Inform about your progress
Thanx. Very useful
Hi guys. I am in a lot of trouble with my ideos.
Tried installing a custom ROm using ROM manager and it failed, although the original ROM is still there and its booting up and working perfectly.
However, when i try to boot into recovery, only the lit blackscreen shows.
I have tried everything from running ULTRAjack recovery on windows(which only shows 'waiting for device' on cmd, with the pdanet drivers installed) to ubuntu(which shows 'waiting for device' on Amon-ra recovery and permission denied on ULTRAjack).
Could it be i didnt root the device properly since i used z4 root?
Any more ideas?
900/2100 or 850/1700/1900/2100
Hello, How do I tell which sub-model my U8150 is please? Either HSDPA 900 / 2100 / AWS or HSDPA 850 / 1900 / 2100 / 1700. baseband = 22201003; build no.= U8150V100R001C183B825; IMEC = 355093040562676; IMEC-SV = 39.
Check out your fcc id suffix. I have heard there is a b version and a d version.
hi do flashing many roms affects my ideos mobile?
netskink said:
Check out your fcc id suffix. I have heard there is a b version and a d version.
Click to expand...
Click to collapse
All I got is a U8510-1, no letter... any thoughts?
Unlock u8150
Hello.
i have a T-Mobile Ideos u8150, also known as Comet.
it is locked to T-Mobile and requests a pin code when using another sim card.
is there a way to unlock the phone?
please help me...
thank you.
Enable USB Debugging & One Click Root with Unlock Root Tool

[GUIDE][US 3G ONLY] How To Root Your Xoom From 3.2 Stock [PC & Mac]

**THIS IS FOR US 3G XOOM ONLY**
**DO NOT USE THIS ON WIFI MODEL**
This guide in no way implies or expresses any warranties.
What you choose to do with your equipment is your sole responsibilty.
__________________________________________________ ______________________________________​
SUMMARY
You must already be running Honeycomb 3.2 on your Xoom
You will be unlocking your Xoom, if you have not already. This will wipe data so make sure to back everything up that you would like to keep.
You will be unlocking your Xoom, if you have not already. This will wipe data so make sure to back everything up that you would like to keep.
You will be performing steps in ADB. If you are not familiar with this, read HERE first.
You will need Xoom USB drivers and Fastboot
You will need the boot (kernel) partition with rooted stock 3.2 kernel (thanks & credit to, solarnz and p3droid) [see Attachment]
You will need Superuser.apk and su binary to enable functioning root [see Attachment]
**Before you get started, make sure the USB Debugging option is enabled in the Settings. Go to Settings --> Applications --> Development -->USB Debugging**
PROCEDURE
Download and unzip files. Place kernel.img, superuser.apk & su binary in the same place you will open your command window.
Open command window:
Type; adb devices - you should see a long serial number on the screen. If no serial number appears, recheck your adb, sdk & moto usb driver files.
Type; adb reboot bootloader
Type; fastboot oem unlock - and follow the steps on your xoom's screen (You have to accept the terms by pressing the volume down key, and then select 'accept' by pressing the volume up key.)
Allow the xoom to boot up completely and go back into settings and enable USB debugging again.
In the command window on your PC type; adb reboot bootloader - (if xoom does not respond, disconnect from pc and reboot manually by holding vol up + power. then reconnect after fully rebooted)
Type; fastboot flash boot kernel.img
Type; fastboot reboot
Allow the xoom to boot completely - your xoom should be in normal operating mode for the remainder of the process.
In the command window on your PC type; adb remount
Type; adb push su /system/bin
Type; adb shell ln –s /system/bin/su /system/xbin/su
Type; adb shell chmod 4755 /system/bin/su
Type; adb push Superuser.apk /system/app
Thats it...your done!! Unplug the xoom and reboot. Your xoom is now stock rooted.
You can now flash ClockworkMod, other kernels and roms. To verify root, download a root user app from the market and run it.
You should be prompted to allow superuser permissions.
Mac Only Procedure
You will need fastboot for mac
Open a terminal (located in the utilities folder)
Navigate to your sdk/platform-tools folder
Type; ./adb devices - (look for the xoom serial number to show its connected.)
Type; ./adb reboot bootloader
Type; chmod 755 fastboot
Type; ./fastboot oem unlock
Type; adb reboot bootloader
Type; ./fastboot flash boot kernel.img
Type; ./fastboot reboot
Type; ./adb remount
Type; ./adb push su /system/bin
Type; ./adb shell ln –s /system/bin/su /system/xbin/su
Type; adb shell chmod 4755 /system/bin/su
Type; ./adb push Superuser.apk /system/app
Disconnect and reboot xoom. Download a root app and test.
If you found this helpfull press the THANKS button.
thanks & credit to, solarnz and p3droid for the kernel & jase33 for the form and style of this TUT!
PS: to the mods --> please move this thread to the Dev part, currently it's not possible for me to post in there...
can't get this to work
I've followed the instructions to the letter a half dozen times now and when I get to
adb shell ln –s /system/bin/su /system/xbin/su
The reply is that the folder can't be found. Any advice? thanks much!
I know a lot of people have been looking for a guide like this.
dslcpm said:
I've followed the instructions to the letter a half dozen times now and when I get to
adb shell ln –s /system/bin/su /system/xbin/su
The reply is that the folder can't be found. Any advice? thanks much!
Click to expand...
Click to collapse
I just went on past that step and it appears to have still taken the root.
Hi!
Have you had the su binary in the same direstory
From which youve executed the following cmd:
Type; adb push su /system/bin
Because then everything should be fine!
Bye
Thanks a lot
Move ---> xoom android development
Hi mods,
please move this article to Xoom Android Development.
Thanks
Worked perfect
Sent from my HTC Sensation Z710e using XDA Premium App

[Q] Rooted xoom wifi error

Hi there! I followed the instructions here:
Code:
Download and unzip files. Place rootboot.img, superuser.apk & su binary in the same place you will open your command window.
Open command window:
Type; adb devices - you should see a long serial number on the screen. If no serial number appears, recheck your adb, sdk & moto usb driver files.
Type; adb reboot bootloader
Type; fastboot oem unlock - and follow the steps on your xoom’s screen (You have to accept the terms by pressing the volume down key, and then select ‘accept’ by pressing the volume up key.)
Allow the xoom to boot up completely and go back into settings and enable USB debugging again.
In the command window on your PC type; adb reboot bootloader - (if xoom does not respond, disconnect from pc and reboot manually by holding vol up + power. then reconnect after fully rebooted)
Type; fastboot flash boot rootboot.img (for WiFi)
OR Type; fastboot flash boot 3Grootboot.img (for 3G Verizon)
Type; fastboot reboot
Allow the xoom to boot completely – your xoom should be in normal operating mode for the remainder of the process.
In the command window on your PC type; adb remount
Type; adb push su /system/bin
Type; adb shell
Type; ln -s /system/bin/su /system/xbin/su (this line starts with lower case “L”, like llama)
Type; chmod 4755 /system/bin/su
Type; exit
Type; adb push Superuser.apk /system/app
to root my xoom. I have an UK xoom 3.2. And everything was going great.
After the first reboot (fastboot flash boot rootboot.img )
When the xoom booted, it was fine, I've logged into my gmail account using my wifi hotspot.
But then ...
after executing this steps and rebooting:
In the command window on your PC type; adb remount
adb push su /system/bin
adb shell
ln -s /system/bin/su /system/xbin/su (this line starts with lower case “L”, like llama)
chmod 4755 /system/bin/su
exit
adb push Superuser.apk /system/app
Now I don't have wifi anymore. The wifi only shows an error.
How can I fix this? I've did a basic search but most related to ppl using version 3.2.1, since I'm using 3.2 I did not believe it would apply to myself.
Any ideas?
Thanks
No idea how to fix that one.
However I can suggest using a one click rooting method in the future - i think i used a tool called xoot the 1st time to root before jumping to ICS.
The above process you mentioned was one of the things that put me off rooting at the start of ownership.
Hopefully someone will be a long soon to help with your problem
What are the specifics of the error you're getting with wifi?
Is the error when you try to turn wifi on?
Did you allow restoring apps/settings when you booted after the rooting process?
Hi lads,
thanks for the support, I've solved by restoring the stock image (3.0) and then using the universal root procedure.
Regards
vinicius.carvalho said:
Hi lads,
thanks for the support, I've solved by restoring the stock image (3.0) and then using the universal root procedure.
Regards
Click to expand...
Click to collapse
where did you get it?

HTC OneX AT&T Manual root process (No Desktop)

I wanted to share my experience with following this thread
http://forum.xda-developers.com/showthread.php?t=1709296
i unfortunatly do not meet the 10 post limit
Following the process i got stuck here
Code:
Now it's time to reboot
adb reboot
After phones reboots
adb remount <-----------------HERE---------------------------
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell rm /data/local.prop
adb reboot
ADB told me that i dod not have the correct permissions to push the SU file to the phone. The phone would boot, but would not load the widgets or bottom menu. Attempting to open settings would prompt Android.Core to crash.
Scary stuff
The problem was with the ADB Reboot command. It normally reboots the phone properly, but when i ran ADB Reboot, the phone cut power (off) instead of rebooting. Something did not go as intended and i needed to power on my phone, and reboot it manually without the USB cable connected (lagged too much).
After that, the ADB Remount was successful and the rest of the process ran smoothly. I am happily rooted
Thank you to all
~Can someone copy this into the actual thread? I want to help spread rootsauce.

Categories

Resources