Database Info

Step by Step How-To get Modify RC30

I would like to give thanks to JesusFreke who helped me to understand this process !!!! Please show him some love and make good gestures for his work….. Also to all the other people and sites who made this possible including Koush !!! I take no credit for this just posting it to help people like me, who dont know to much about this.
First…. You need to install a google android usb driver so you can use the adb program. (It lets you push and pull files to/from the phone, and you can open up a shell with it to).
Download the driver file (http://dl.google.com/android/android_usb_windows.zip) and
unzip it to the desktop.
On ur G1… Go menu > Settings > Applications > Development then enable the
USB debugging button.
Then connect your Android device via USB. When the Found New Hardware Wizard
appears, you'll be asked if you'd like Windows Update to search for software,
select No, not this time and click Next. Select Install from a list or specified location
and click Next. Select Search for the best driver in these locations. Browse and
select the unzipped file (android usb windows.zip). Click Finish.
Second…. Setting up the SDK
Go to http://code.google.com/android/download_list.html and download the
SDK
Unzip the file to the desktop and rename the folder to sdk
Open your command prompt (Windows Key and R)
Type “cmd” (Without the quotations)
Then "cd desktop"
Then “cd sdk”
Next “cd tools”
Now type “adb devices
After that it should say some thing like… List of devices attached HT845GZ21370
Device. If u see this abd sees your device.
Third…. Writing JesusFreke’s Recovery image
Download the zip file from this thread... http://forum.xda-developers.com/showthread.php?t=443041)
Unzip the files to the SDK tools folder
Now, in the command window, type
"adb push recovery_testkeys.img /data/local/recovery.img"
(This will copy the recovery image files to the phone)
Fourth…. Get Root working on ur G1
Download the Android Telnet Client from the Market or get it here…
http://www.koushikdutta.com/2008/11/android-telnet-client.html
Turn on your phone's WiFi. This gives your phone an IP you can reach it at.
Restart your phone
Once restarted type telnetd at the home screen and press enter – Yes….. it will
start up a Contact search, do not worry about this, just type “telnetd” and press
enter (the enter button on the keypad).
Now press connect to localhost……. (You now have root!)
Now put in this command….
“mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system”
Then “cd /system”
Then “cat /data/local/recovery.img > recovery.img”
Finally “flash_image recovery recovery.img” (Your Recovery Image is now writen)
*To make sure your Recovery Image was written…. Reboot your phone in Recovery
mode and press Alt+L. At the top it should say "using test keys" If so its written. Go
ahead and Reboot your phone by pressing the Home and Back buttons.*
Fifth…Apply JesusFreke’s modified RC30/RC8/ADP1
Go here http://forum.xda-developers.com/showthread.php?t=475381 and Download the ZIP
Now once the ZIP is downloaded rename it to “UPDATE”
Put it on the storage card
Last but not least Power off your G1 and Power it on by pressing the home key and power key
Press Alt+L (to turn on text)
Press Alt+S (to update)
And Bam you have yourself a modded RC30 G1 !!!!!!!!

ANOTHER Step by Step How-To get Modify RC30
Per user- "brandenk"
I think you need root to make the changes which is why you need to downgrade from RC30 to RC29 to take advantage of the root bug.
To downgrade using this NBH file: http://android-dls.com/wiki/index.php?title=Root_For_RC30
To gain root access: http://android-dls.com/wiki/index.php?title=Rooting_Android
To flash the recovery and install modified rc30: http://android-dls.com/wiki/index.php?title=Keeping_Root
Engineering bootloader for G1: http://forum.xda-developers.com/showthread.php?t=455860
Follow those steps, for #2 you dont need to do the beatbox mod and for step #3 use JKv1.3 instead of 1.2, then I added a step, flashing the Engineering Bootloader. Once you do those steps you will be good to go, I did this for the first time ever last night following those directions and it worked for me, and thats with my changes to the process. It took me reading through the directions like 50 times before I tried it but I went slowly and carefully and it went flawlessly.

Complete instructions for RC30 -> JFv1.3
Per "JesusFreke"
"I saw someone post this over on saurik's G1-hackers mailing list, and thought it would be useful to some of you.
It gives complete step-by-step instructions (all 23 of them ) for going from RC30 to JFv1.3.
http://www.webnetta.com/2009/01/02/t...rc30-to-jfv13/
__________________
"Whether You Think You Can or Can't, You're Right"
--Henry Ford
T-Mobile G1 - modified RC30 with root access !!!

Thanks for the step by step instructions. Been looking for something like this!

would i get brick if i unlock it with a code for ATT?

step three link should be the following:
http://forum.xda-developers.com/showthread.php?t=443041
thanks for the walk through

also the link for the modded RC30 is:
http://rapidshare.com/files/162035634/update-RC30-fullupdate-modified-testkeys-v1.1.zip

I did this last night and upgraded to RC30 but the problem is right before I started the original RC30 was downloaded and it was asking me to update my phone but I declined. So now after everything is done, is there a way I could tell if I have the modded RC30 or the original RC30?

will this work even if your phone has already been updated to the stock rc30?

i dont think so. because they patched it

johnny13oi said:
I did this last night and upgraded to RC30 but the problem is right before I started the original RC30 was downloaded and it was asking me to update my phone but I declined. So now after everything is done, is there a way I could tell if I have the modded RC30 or the original RC30?
Click to expand...
Click to collapse
yup "open a command prompt however you like (telnet, adb, terminal emulator app, etc.) and type "getprop ro.secure". If it says 0, then you're running the modified boot image. Otherwise, if it says 1, you're still running the."-JesusFreke

Still at risk??
A bit of a noob here... but check my thinking:
True/False:
1. Flashing the new recovery image will prevent any further OTA updates from being loaded unless they are signed with the test keys.
2. If 1 is true, then Google/Tmobile can still push a forced update to us if they sign it with test-keys?
If both above are true, maybe we need to look at disabling OTA updates altogether?

anyone want to make a how-to for ubuntu/*nix users?

I just tried all this (havent flashed mod rc30) and rebooted into recovery mode and I see:
Android system recovery utility
"Using Test Keys"
E:Can't open /cache/recovery/command
Is this correct? Is it supposed to say "E:Can't open /cache/recovery/command"? When I do "getprop ro.secure" I get 1. I'm afraid to try the flash like this. Im going to leave my phone off until I can figure this out...dont want a forced rc30 or a brick.
Can anyone help me??

xavier6303 said:
I just tried all this (havent flashed mod rc30) and rebooted into recovery mode and I see:
Android system recovery utility
"Using Test Keys"
E:Can't open /cache/recovery/command
Is this correct? When I do "getprop ro.secure" I get 1. I'm afraid to try the flash like this. Im going to leave my phone off until I can figure this out...dont want a forced rc30 or a brick.
Can anyone help me??
Click to expand...
Click to collapse
yes that looks right. you still get a 1 because you still need to do STEP 5. that is flashing with the modified RC30. Looks like you are set up to go. GL
it will always say that E:Can't open /cache/recovery/command i believe. just ignore it.

mack said:
yes that looks right. you still get a 1 because you still need to do STEP 5. that is flashing with the modified RC30. Looks like you are set up to go. GL
it will always say that E:Can't open /cache/recovery/command i believe. just ignore it.
Click to expand...
Click to collapse
ahh...thank you so much for the reply!
UPDATE: performed the update to rc30 and I now get a 0 for getprop ro.secure

Thanks, I just updated to the mod RC30 with a breeze. Anyways, to make sure, how do I confirm that I'm on the modded RC30?

xavier6303 said:
ahh...thank you so much for the reply!
UPDATE: performed the update to rc30 and I now get a 0 for getprop ro.secure
Click to expand...
Click to collapse
congrats...you now have modded RC30

donutman said:
Thanks, I just updated to the mod RC30 with a breeze. Anyways, to make sure, how do I confirm that I'm on the modded RC30?
Click to expand...
Click to collapse
A quote for a quote
"open a command prompt however you like (telnet, adb, terminal emulator app, etc.) and type "getprop ro.secure". If it says 0, then you're running the modified boot image. Otherwise, if it says 1, you're still running the."-JesusFreke

What are the modified recovery image and modified RC30 update? What it the difference? Why the original onces do not work?

problem

i have a problem, for some reason i cant go to recovery mode. i have JFv 1.42_RC33... what can i do

What exactly do you mean by that? Have you tried booting into recovery straight from the terminal?

Iceucold said:
Have you tried booting into recovery straight from the terminal?
Click to expand...
Click to collapse
That made even less sense.

forgive me if im mistaken, but doesnt it have something to do with the bootloader as well?

kydcleric said:
forgive me if im mistaken, but doesnt it have something to do with the bootloader as well?
Click to expand...
Click to collapse
i dont know im new to this stuff but what happens is that the g1 boot screen pops up when i press home+power then it just restarts and shows the g1 boot screen again then it goes to the normal home screen

Iceucold said:
What exactly do you mean by that? Have you tried booting into recovery straight from the terminal?
Click to expand...
Click to collapse
i dont know what u mean

Sorry about that. I was referring to going into the terminal emulator and typing in the command:
Code:
# reboot recovery

Iceucold said:
Sorry about that. I was referring to going into the terminal emulator and typing in the command:
Code:
# reboot recovery
Click to expand...
Click to collapse
nothing happens i put that in there and it just shows a money sign under it.. and when i just put reboot it says
reboot: operation not permitted

You are holding down home first right? I.e. press home and hold it down and then press power(I continue to hold home down all the way up until I see recovery mode starting)

Can you check if the recovery image (/system/recovery.img) is intact?
if you're using the haykuro builds, it is known that reboot won't work from terminal emulator. but you should be able to reboot recovery through adb shell.
I remember I read somewhere that certain bootloaders have a different key sequence for recovery mode, but i've never seem any of them.

ooooo crap i just checked it and there is no recovery.img in there ok what do i do??

someone plz help me out

probably best to dl the one from the Rooting Hacking & Flashing... post. They have a link to the file there. Just dl it and, as su, copy it to the folder they say.

what post???

Cosine said:
what post???
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=442480

yea but thats only to get to root and i already did that... and i just tried it and it dosent work

Cosine said:
yea but thats only to get to root and i already did that... and i just tried it and it dosent work
Click to expand...
Click to collapse
The suggestion was to try restoring the recovery image as outlined in that thread: (though you shouldn't need to do the "telnetd" part)
Instructions:
1. Download recovery.img and copy it to your SD card (see the previous instructions on how to copy from your computer to your Phone's SD card).
2. Download the Hard SPL and copy the zip file to the SD card.
3. All files must be on the root of your SD card.
4. Restart your phone. Wait for your phone to start up fully and show the home screen.
5. After your phone starts up, hit the enter key twice, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
6. Download an Android "Telnet" application from the Market and connect to localhost.
7. If you connect successfully, you will have a root prompt "#".
8. Type the following into Telnet (these commands will give you root access easier in the future):
* mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
* cd sdcard
* flash_image recovery recovery.img
* cat recovery.img > /system/recovery.img
Now you have root!
Click to expand...
Click to collapse

so should i just try
8. Type the following into Telnet (these commands will give you root access easier in the future):
* mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
* cd sdcard
* flash_image recovery recovery.img
* cat recovery.img > /system/recovery.img
in the terminal emulator

[GUIDE] How To Root The Sprint CDMA Hero (Windows)

I have compiled this guide from the other one posted on this forum, the discussion therein, and my own knowledge. If you have any suggestions on making it better or to correct any mistakes I may have made please let me know.
This guide is intended for Windows and includes detailed instructions. It will cover the steps necessary to root, flash the new recovery image, create a full backup. This will work with software versions 1.29.651.1 and 1.56.651.2 (aka Android 1.5). If you have updated to 2.1 please following this guide here. I am not responsible for any damage done to your phone using this guide. Root at your own risk.
I have put to together a video on YouTube for you to follow along as well. The version numbers of certain files are now outdated in the video so change file names as necessary.
If you own a non-Sprint Hero, you will need to do some extra steps. Follow the guide in the How to Root Non-Sprint CDMA Hero thread.
Step 1: Download the Android SDK from http://developer.android.com/sdk/index.html The Windows file is called android-sdk_r06-windows.zip. Extract the files to your C: drive so that you now have the folder C:\android-sdk-windows
Step 2: Download the asroot2 exploit file from http://forum.xda-developers.com/attachment.php?attachmentid=244212&d=1257621154 Extract asroot2.zip to C:\android-sdk-windows\tools folder.
Step 3: Download the Hero recovery image from http://forum.xda-developers.com/showpost.php?p=4898505&postcount=1g Place this file in C:\android-sdk-windows\tools as well.
Step 4: Make sure USB Debugging is off by going to Settings>Applications>Development. Now connect the phone to your PC via USB cable.
Step 5: Mount your sdcard; Browse to the HTC Sync folder and install HTC Sync on your pc. After it is done installing unmount the sdcard then enable your USB debugging.
Step 6: Open a command prompt by clicking the Start button and typing cmd into the search box and pressing enter or found under All Programs>Accessories.
Step 7: You will now enter a series of commands which I will place inside code boxes to indicate the entire command. You may copy and then paste them into the command prompt window by right clicking. Only enter one command at a time.
1:
Code:
cd C:\android-sdk-windows\tools
2:
Code:
adb devices
If you've been following this guide you will see your phone's serial number. If you get "device not found" error, you either need to make sure you the drivers were properly installed or make sure you enable USB debugging AFTER you connect the USB cable. Continue on once you get the proper phone serial output.
3:
Code:
adb push asroot2 /data/local/
4:
Code:
adb shell
5:
Code:
chmod 0755 /data/local/asroot2
6:
Code:
/data/local/asroot2 /system/bin/sh
You should see an output that says:
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pope_inode_info layout
Opening: /proc/857/fd/3
SUCCESS: Enjoy the shell.
#​Now for a few last commands.
7:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
8:
Code:
cd /system/bin
9:
Code:
cat sh > su
10:
Code:
chmod 4755 su
You are now officially rooted. A few more steps and you will have flashed the recovery image.
11:
Code:
exit
12:
Code:
exit
13:
Code:
adb push recovery-RA-heroc-v1.6.2.img /sdcard
Pushing is equivalent of copy the file to the root of your sdcard. By the time you finished reading this it should be done. You'll know its done because the ouput will say something like transferred X bytes in X secs.
14:
Code:
adb shell reboot
This will cause the phone to restart automatically. Wait till it is fully booted to continue.
15:
Code:
adb shell
16:
Code:
su
17:
Code:
cd /sdcard/
18:
Code:
flash_image recovery recovery-RA-heroc-v1.6.2.img
FLASHING TO THE RECOVERY TAKES SEVERAL SECONDS-- BE PATIENT. ENTER THE NEXT COMMAND ONLY AFTER THE COMMAND PROMPT RETURNS TO THE # (ROOT SYMBOL).
19:
Code:
reboot recovery
Step 8: This is the last command; you may now close the cmd prompt. This will cause your phone to boot into recovery mode; it should take no longer than 30 secs. The third option on the list is "- Backup/Restore"; select it. Now, select the first option "- Nand backup". The phone will prompt you to press HOME to confirm which is want you want to do. The backup will begin. You will see the screen say, "Performing backup : .........." When done, the bottom of the screen will say "Backup complete!" and you will be given the menu options again. Go back to the main menu and select reboot system. Rebooting your phone after installing the new recovery image may take several minutes.
Step 9: Once your phone is fully booted, mount the sdcard. You will see a folder called "nandroid"; I highly recommend you copy this to your pc in case you lose your sdcard data or reformat it. Your phone is rooted, 100% backed up, and ready to install a custom rom if you wish!

wow dude,
instructions worked great on Win7
i was able to download the missing usb_drivers by running SDK Setup in C:\android-sdk-windows, and selecting the usb driver from the available packages. I was unable to download the index for the SDK Setup program until I enabled "force http://" in the settings menu.
had to copy over asroot again after i ran SDK Setup (that program deleted it from the directory)
your instructions worked like a charm. total time spent rooting this thing after finding your post: 18 minutes.
(you might want to add a line there in the "mount and copy over the zip file step" to backup the nandroid folder from your SDCard to your comp just as a backup of your stock phone image)
anyway.. cheers!

izanagi said:
wow dude,
i'm about to follow these instructions. thank's for the precise list!
(btw, about to try it on Win7.. may have to change some folder pathing but we'll see)
okay.. typo on the first command in parentheses, and I'm missing the usb_drivers folder (do you have it / can sent it to me) so am unable to install the device in win7.
Click to expand...
Click to collapse
Heh, thanks for the misspell heads up. I did my rooting from Win7 pc; it automatically installed correct drivers for me. To check go to the Control Panel>View devices and printers. You see one device named "Android Phone". Otherwise as far as Ive heard installing HTC Sync installs proper drivers.​

izanagi said:
*** edit had to copy over asroot again after i ran SDK Setup (that program deleted it from the directory)
**** edit: all done.. your instructions worked like a charm. total time spent rooting this thing after finding your post: 18 minutes.
(you might want to add a line there in the "mount and copy over the zip file step" to backup the nandroid folder from your SDCard to your comp just as a backup of your stock phone image)
anyway.. cheers!
Click to expand...
Click to collapse
Thank you for taking the time help make my guide better. I'm very glad to know there are little to no hiccups.

When I do step 5, instead of:
5. "/data/local/asroot2 /system/bin/sh"
You should see an output that says:
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pope_inode_info layout
Opening: /proc/857/fd/3
SUCCESS: Enjoy the shell.
#
I get:
[1] Killed /data/local/asroot2 /system/bin/sh
Any suggestions? Should I just be quiet until there is an Eris specific way to do this?

When I do step 5, instead of:
5. "/data/local/asroot2 /system/bin/sh"
You should see an output that says:
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pope_inode_info layout
Opening: /proc/857/fd/3
SUCCESS: Enjoy the shell.
#
I get:
[1] Killed /data/local/asroot2 /system/bin/sh
Any suggestions? Should I just be quiet until there is an Eris specific way to do this?

detox702 said:
When I do step 5, instead of:
5. "/data/local/asroot2 /system/bin/sh"
You should see an output that says:
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pope_inode_info layout
Opening: /proc/857/fd/3
SUCCESS: Enjoy the shell.
#
I get:
[1] Killed /data/local/asroot2 /system/bin/sh
Any suggestions? Should I just be quiet until there is an Eris specific way to do this?
Click to expand...
Click to collapse
This guide is for the CDMA Hero not the Eris!

When I go to apply the rom I get an white screen with skateboarding androids on the bottom and the prompt to erase data yes/no. I press the home key and the Hero reboots without asking to "Apply sdcard:choose zip". This is done from the boot menu. Does the rom load automatically? Did I do something wrong? I got root with no problem. A tip; to make it easier and to avoid spelling mistakes copy and paste the rooting commands from the instructions. Made it go faster too. Thanks in advance.
Never mind. I held down Home and Power at
the same time instead of Home THEN power! ARRGH! Loading up now as I type. Sorry.

ELIMINATED said:
When I go to apply the rom I get an white screen with skateboarding androids on the bottom and the prompt to erase data yes/no.
I press the home key and the Hero reboots without asking to "Apply sdcard:choose zip".This is done from the boot menu.
Does the rom load automatically? Did I do something wrong? I got root with no problem.
A tip; to make it easier and to avoid spelling mistakes copy and paste the rooting commands from the instructions. Made it go faster too. Thanks in advance.
Click to expand...
Click to collapse
yuck... break up your sentences, that's alot of crap to throw on someone all at once... and the bold doesn't help it any.
check to see if you have the custom recovery installed....
-turn off phone
-hold vol down + power
-should search for some stuff then give three options
-press "home" to enter recovery image
do you see "!" and a phone.... does it just hang or do you see a green/yellow menu?

At the end of his post he says he figured it out. He wasn't holding down home key

None of this is working for me at all... I'm not sure what I'm doing wrong, but every time I enter ANY of the commands into the prompt all I get is "cannot find the path specified".
For reference, i have done everything in this guide to the letter, everything is downloaded, unzipped to the correct location, USB drivers installed, etc etc. Not sure what's wrong.
EDIT: I figured it out.. user error, awesome. Worked great, thanks for this!

awesomeindeed said:
None of this is working for me at all... I'm not sure what I'm doing wrong, but every time I enter ANY of the commands into the prompt all I get is "cannot find the path specified".
For reference, i have done everything in this guide to the letter, everything is downloaded, unzipped to the correct location, USB drivers installed, etc etc. Not sure what's wrong.
EDIT: I figured it out.. user error, awesome. Worked great, thanks for this!
Click to expand...
Click to collapse
"cd C:\android-sdk-windows\tools" is actually "cd C:\android-sdk_r3-windows\tools"
is that where you are stuck?

thank you TS. I've been lurking xda for a couple years now when i had the mogul and tp. First time on an android device. Thank you for your time in helping me.

someone buy this man a drink!!!
Invaluable piece of work right here, helped me get it done in no time at all....real clear concise and very helpful....REQUEST THIS BE A STICKY!!!!!

fenske09 said:
"cd C:\android-sdk-windows\tools" is actually "cd C:\android-sdk_r3-windows\tools"
is that where you are stuck?
Click to expand...
Click to collapse
That was the name of the zip file not the extracted folder.

Please help, I followed all of your instructions, I received no errors however I can't boot the recovery image. I checked and it is in the sd card, but every time it just hangs at the HTC logo
I downloaded a terminal emulator and typed su and it gave me # so I assuming I am rooted?!

newtodroid said:
Please help, I followed all of your instructions, I received no errors however I can't boot the recovery image. I checked and it is in the sd card, but every time it just hangs at the HTC logo
I downloaded a terminal emulator and typed su and it gave me # so I assuming I am rooted?!
Click to expand...
Click to collapse
Redownload the recovery image and reflash it. The one you're using probably became corrupt during DL or something.

theresthatguy said:
Redownload the recovery image and reflash it. The one you're using probably became corrupt during DL or something.
Click to expand...
Click to collapse
also make sure you have the heroc version there's a hero and heroC, i messed that up once and had similar results

new ROM
So i loaded the custom ROM, and i followed all the istructions as listed on this guide. When i rebooted my phone, a bunch of my apps started Force Closing on startup.
did i miss something, or do something wrong?
if i reinstall them on the new ROM will they work right?
thanks for any insight

kristaps said:
So i loaded the custom ROM, and i followed all the istructions as listed on this guide. When i rebooted my phone, a bunch of my apps started Force Closing on startup.
did i miss something, or do something wrong?
if i reinstall them on the new ROM will they work right?
thanks for any insight
Click to expand...
Click to collapse
you converted your sd card to fat32,ext2,swap and now the apps are looking for the program on your sd card,
turn off your phone
take out sd card
turn on phone
uninstall app
turn off phone
put in sd card
turn on phone
reinstall app
this should fix you

{Howto}Downgrrade form rooted 1.47.651.1

Ok... If your wimax isn't working and you want to downgrade to try to get it working this is how to do it...
1st get all of the files like you want to do Toast's Part-2. link: http://forum.xda-developers.com/showthread.php?t=701835
Then do this part:
STEP 2~FLASHING MTD PARTITION TO ENABLE DOWNGRADE:
- download all files posted above
- unzip the flash_image.zip and the mtd-eng.zip
- put the flash_image and mtd-eng.img on the root of your sdcard
- go into shell on ur pc and do:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img
- this should only take a second or two
- now put the PC36IMG.zip on the root of your sdcard
- power off the phone
STEP 3~FLASHING ENG BUILD:
- hold volume down + power to boot into hboot
- it should now find and verify the PC36IMG.zip on the root of your sdcard. itll show a blue status bar on the top right of the screen.
- after a minute or so it will ask u if u wanna flash SAY YES
- affter it flashes the PC36IMG.zip it will ask if you wanna reboot. SAY YES
After if finally boots you should see HTC quietly brilliant which hangs forever but it should eventually get past it. Once it does you will have the oldest everything. This is a beta build and has a bunch of tools but just do an upgrade to root like you normally would. I would suggest going to .6 then upgrading to the latest 47 from there.
Hope that this helps someone.
P.S. is anyone willing to dump all of the tools that are included in this rom. It might be helpful for the other devs.

Thats the hard way... but yeah it'l work.
Why is everyone so hype on adb everything...?

Tell me the easy way. I would love to do it instead.

kthejoker20 said:
Thats the hard way... but yeah it'l work.
Why is everyone so hype on adb everything...?
Click to expand...
Click to collapse
It's just easier to copy and paste stuff, even typing on a real keyboard. It's a pain in the ass doing it via terminal emulator with the lack of a physical keyboard on our Evo's.

Can anyone confirm if this helps fix the 4g issue?

krosemm said:
Can anyone confirm if this helps fix the 4g issue?
Click to expand...
Click to collapse
If you used the unrevoked, no it wont.
There is no fix for 4g from unrevoked yet.

Neotelos_com said:
If you used the unrevoked, no it wont.
There is no fix for 4g from unrevoked yet.
Click to expand...
Click to collapse
I used the toast method. And if i'm not mistaken I should flash roms w/o the 1.47.651.1 OTA update after downgrading right?

Nope, I try this method and it is not working. Some how the new OTA encrypted a code that any lower version will not over write it.

You don't have root access to even copy/paste or push the files to /data. I tried this and got a permission denied error message.

How do you input adb shell into Vista, I clicked "start", "run" and type "cmd" it bring up C:\users\XXXXX\ cd c:\android hit "enter"
then I type
c:\android>adb remount
Access is denied
Please advise what I did wrong. thanks

It worked for me... you have to make sure that when you enter the su command in adb to look at your phone. There should be a super user permission box that pops up. Accept it and youll be able to adb. It went fine for me after that.

urcboss07 said:
How do you input adb shell into Vista, I clicked "start", "run" and type "cmd" it bring up C:\users\XXXXX\ cd c:\android hit "enter"
then I type
c:\android>adb remount
Access is denied
Please advise what I did wrong. thanks
Click to expand...
Click to collapse
1) Put your phone on USB Debug
2) On your Phone make sure the Ninja(SuperUserPermission) is set to prompt you when you have a request.
3) go to your PC and type in adb shell
4) type in SU
5) Once do you that you will see a prompt from the Ninja asking for a request. Allow for it. And it will remember from that point forward.
6) Look at your cmd prompt screen for a # - if you have it you have full access.
Then so what commands you have been given to do.
It can also be done from the Android Terminal Emulator but some might not like working with a smaller screen I like it myself. Makes me feel geeky

mrmomoman said:
1) Put your phone on USB Debug
2) On your Phone make sure the Ninja(SuperUserPermission) is set to prompt you when you have a request.
3) go to your PC and type in adb shell
4) type in SU
5) Once do you that you will see a prompt from the Ninja asking for a request. Allow for it. And it will remember from that point forward.
6) Look at your cmd prompt screen for a # - if you have it you have full access.
Then so what commands you have been given to do.
It can also be done from the Android Terminal Emulator but some might not like working with a smaller screen I like it myself. Makes me feel geeky
Click to expand...
Click to collapse
This would only work if after the messup your still has root access. Some people have root and the "SU" will work but for the people w/o root will get access denied.

also
From above (I hate quoting) have you tried going to your tools folder inside your android folder and from there try your adb commands?

If you applied the OTA sent from Sprint, you lost root access. There will be no Ninja in the programs folder, because it was a new rom that the was flashed with the OTA. Root access has been closed for those that downloaded the update. If you try and type su, you will get permission denied.
Those of you that still have the root and superuser rights, DON'T DOWNLOAD THE OTA!! You are in a better position then the rest of us. I wanted the good battery life, so that's why I did it.

ASUS Z380KL root achieved with Xposed.

Use only the man who doesn't complain of self-responsibility:laugh:
If your phone was bricked, then it could restore backed up system image by temp-root.
special thanks Mozzie62 @ digi-wo.
new link
download: <dev-host>/8FqR
old link
download: <filedropper>/z380klrootwxposed
-- temp-root environment --
If PC did not recognize bootloader/ADB driver,
then you force update and select ASUS bootloader/ADB driver
from already installed device driver lists.
(1) type "adb reboot bootloader".
(2) type "fastboot boot tmp.img".
(3) it stops by a ASUS logo.
(4) confirm "adb shell" command.
(5) if necessary, save a system image by dd command.
-- root --
Get ready temp-root environment.
(1) type "root.bat".
(2) your phone reboot.
If your phone was not root, please try "unroot" way.
--- install Xposed ---
this batch file will install only v78-sdk21-arm and XposedBridgeApi.
you install xpose*.apk manually
Get ready temp-root environment.
(1) type "xposed.bat" at "xposed" folder.
(2) your phone reboot.
(3) install xposed*.apk
If your phone didn't xposed, please try "remove_xposed" way.
--- uninstall Xposed ---
Get ready temp-root environment.
(1) type "remove_xposed.bat" at "xposed" folder.
(2) your phone reboot.
--- unroot ---
Get ready temp-root environment.
(1) type "unroot.bat"
(2) your phone reboot.
--- etc ---
ASUS updater was failed at root situation.
A way of update and re-root:
(1) uninstall Xposed
(2) unroot
(3) ASUS update (check system update on settings)
(4) root
(5) install Xposed.
This way will keep data and keep Xposed.
If you notice a mistake, I want you to inform me.
Good luck:good:

Hi,
Thanks for your feedback
I have reported this thread being moved to Miscellaneous Android Development so that users having the same device can use this as a guide.
Thank you
-Vatsal

Does this root method work with Z380 (Wi-Fi version)?
download: http://filedropper.com/z380klrootwxposed

mingkee said:
Does this root method work with Z380 (Wi-Fi version)?
Click to expand...
Click to collapse
No, because of a Wi-Fi Version(Z380C) was equipped with a Intel CPU.
This is for only Z380KL with Qualcomm CPUs(410/615).

May be that my phone has recovery-bugs...?
I consider to make other recovery for Z380KL.
Please check your recovery and inform me.
And I recommend that you save your images.
--- enter BOOTLOADER mode --
Step1. Turn off your phone.
Step2. Long press VOL UP + POWER button.
Step3. Release POWER button after short vibration.
Step4. Release VOL UP button after 3 items appeared.
this is BOOTLOADER mode.
--- Please check --
Select "1. Enter SD down mode"
(select:VOL UP/DOWN, choiceower)
You look...
Case A. Recovery menu displayed.
Case B. Became boot loader mode.
My phone was Case B. mmm...
Other type of Zen(Fone/Pad) are normally Case A as recovery mode.
I think this phone has bugs of recovery mode.
If your Z380KL phone was Case A, then please give me recovery image.
After that.
Case A -> select "Reboot" and reboot normally.
Case B -> select "3. Exit update mode." then "Reboot" normally.
thanks.
and ----------
A way of saving/restoring images.
Caution, system.img is too big size, approximately 2.5GB.
--- a way of saving boot/recovery/system images ---
Get ready temp-root environment
(1) type "adb shell" at DOS-prompt.
(2) type "mount /dev/block/bootdevice/by-name/userdata /data"
(3) type "dd if=/dev/block/bootdevice/by-name/system of=/data/system.img bs=4096"
(4) type "dd if=/dev/block/bootdevice/by-name/recovery of=/data/recovery.img bs=4096"
(5) type "dd if=/dev/block/bootdevice/by-name/boot of=/data/boot.img bs=4096"
(6) type "exit" and exit adb-shell.
(7) type "adb pull /data/system.img" at DOS-prompt
(8) type "adb pull /data/recovery.img"
(9) type "adb pull /data/boot.img"
(10) type "adb shell"
(11) type "rm /data/system.img"
(12) type "rm /data/recovery.img"
(13) type "rm /data/boot.img"
(14) type "reboot"
--- a way of restoring system image ---
Get ready temp-root environment
(1) type "adb shell" in DOS-prompt.
(2) type "mount /dev/block/bootdevice/by-name/userdata /data"
(3) type "exit" and exit adb-shell.
(4) type "adb push system.img /data/system.img"
(5) type "adb shell"
(6) type "dd if=/data/system.img of=/dev/block/bootdevice/by-name/system bs=4096"
(7) type "rm /data/system.img"
(8) type "reboot"

backwardastep said:
I consider to make other recovery for Z380KL.
Please check your recovery and inform me.
And I recommend that you save your images.
--- enter BOOTLOADER mode --
Step1. Turn off your phone.
Step2. Long press VOL UP + POWER button.
Step3. Release POWER button after short vibration.
Step4. Release VOL UP button after 3 items appeared.
this is BOOTLOADER mode.
--- Please check --
Select "1. Enter SD down mode"
(select:VOL UP/DOWN, choiceower)
You look...
Case A. Recovery menu displayed.
Case B. Became boot loader mode.
My phone was Case B. mmm...
Other type of Zen(Fone/Pad) are normally Case A as recovery mode.
I think this phone has bugs of recovery mode.
If your Z380KL phone was Case A, then please give me recovery image.
After that.
Case A -> select "Reboot" and reboot normally.
Case B -> select "3. Exit update mode." then "Reboot" normally.
thanks.
and ----------
A way of saving/restoring images.
Caution, system.img is too big size, approximately 2.5GB.
--- a way of saving boot/recovery/system images ---
Get ready temp-root environment
(1) type "adb shell" at DOS-prompt.
(2) type "mount /dev/block/bootdevice/by-name/userdata /data"
(3) type "dd if=/dev/block/bootdevice/by-name/system of=/data/system.img bs=4096"
(4) type "dd if=/dev/block/bootdevice/by-name/recovery of=/data/recovery.img bs=4096"
(5) type "dd if=/dev/block/bootdevice/by-name/boot of=/data/boot.img bs=4096"
(6) type "exit" and exit adb-shell.
(7) type "adb pull /data/system.img" at DOS-prompt
(8) type "adb pull /data/recovery.img"
(9) type "adb pull /data/boot.img"
(10) type "adb shell"
(11) type "rm /data/system.img"
(12) type "rm /data/recovery.img"
(13) type "rm /data/boot.img"
(14) type "reboot"
--- a way of restoring system image ---
Get ready temp-root environment
(1) type "adb shell" in DOS-prompt.
(2) type "mount /dev/block/bootdevice/by-name/userdata /data"
(3) type "exit" and exit adb-shell.
(4) type "adb push system.img /data/system.img"
(5) type "adb shell"
(6) type "dd if=/data/system.img of=/dev/block/bootdevice/by-name/system bs=4096"
(7) type "rm /data/system.img"
(8) type "reboot"
Click to expand...
Click to collapse
Will restore work with if the device is in a bootloop?

Sorry, I don't try to restore it. Do you know a correctly way to restore?
I'll plan to make a new recovery. Now, I'm testing to get adb root at original recovery.
Thanks.

backwardastep said:
Sorry, I don't try to restore it. Do you know a correctly way to restore?
I'll plan to make a new recovery. Now, I'm testing to get adb root at original recovery.
Thanks.
Click to expand...
Click to collapse
I couldn't get to recovery mode too. I think it's because our bootloader is locked.
I tried to follow your steps but I couldn't get ADB to list or identify my device. I did eventually got root and Xposed on my tablet though via a long workaround ☺

mmm..., I don't know a way of boot-loader unlocking for this phone
But, My phone was booted by test recovery on boot-loader mode.
For now, I'll try to port other recovery.
thanks.

backwardastep said:
new link
download: <dev-host>/8FqR
Click to expand...
Click to collapse
I don't see any link ? Where is it ?

geohsu said:
I don't see any link ? Where is it ?
Click to expand...
Click to collapse
I'm sorry. A junior member can't contribute a direct link to XDA.
The link is alive. Please you read <devhost> as "d-h.st".

backwardastep said:
I'm sorry. A junior member can't contribute a direct link to XDA.
The link is alive. Please you read <devhost> as "d-h.st".
Click to expand...
Click to collapse
thanks for your help.
Downloaded it. Trying to root.

geohsu said:
I don't see any link ? Where is it ?
Click to expand...
Click to collapse
http://d-h.st/8FqR#
---------- Post added at 06:16 AM ---------- Previous post was at 06:04 AM ----------
I rooted using KingRoot, is there a way to install Xposed without having to do the temp-root?

xDark_ said:
http://d-h.st/8FqR#
---------- Post added at 06:16 AM ---------- Previous post was at 06:04 AM ----------
I rooted using KingRoot, is there a way to install Xposed without having to do the temp-root?
Click to expand...
Click to collapse
No, without root you can not install anything in system dir...

Renix63 said:
No, without root you can not install anything in system dir...
Click to expand...
Click to collapse
Found a Russian TWRP, flashed Xposed on that. It couldn't mount cache and installing apps didn't work w/ Xposed installed so I tried installing a new version of said TWRP and a thread said I needed to update so I flashed the Japanese update and it bricked my tablet. Working on fixing it right now lol.

xDark_ said:
Found a Russian TWRP, flashed Xposed on that. It couldn't mount cache and installing apps didn't work w/ Xposed installed so I tried installing a new version of said TWRP and a thread said I needed to update so I flashed the Japanese update and it bricked my tablet. Working on fixing it right now lol.
Click to expand...
Click to collapse
You see this link?

Renix63 said:
You see this link?
Click to expand...
Click to collapse
Yes but I used KingRoot to root the tablet. Then used Flashify to flash TWRP. There are a lot of instructions on the Russian site 4pda.ru (much more than XDA) but I can't read Russian and it requires a log in to download things.

Hi guys, i have used KingRoot in order to have root permission, after i have use super_me or something like this in order to change KingUser app with SuperSu app, but after the reboot it has gone in bootloop
I have tried to reset it using standard recovery (by ASUS) but it doesn't works, it is still in bootloop.
Does this method can solve my problem ?

Can you guys upload the stock recivery for Z380KL?
I am now facing a crrisis

eddieleon7pc said:
Can you guys upload the stock recivery for Z380KL?
I am now facing a crrisis
Click to expand...
Click to collapse
Stock recovery ?
Why don't use TWRP ?
I have the stock recovery installed if you can say how i can dump it i can do it
Please, see this before: http://forum.xda-developers.com/android/help/asus-zenpad-8-0-z380kl-bootloop-t3373051/post66714396#post66714396