Ok, here's the rundown. I tried to install a custom rom on my phone. Used the all in one tool thing to root and unlock bootloader. I've tried three different ROMs and so far, they keep getting stuck at their respective boot logo screens (Cyanomods circle thing, AOKP Unicorn picture, ETC). I don't know what I am doing wrong. I found an error thread that mentioned something about me needing to flash the boot image in the CMD prompt but when I do this (used the "fastboot flash boot boot.img" command), it shows me no improvement. As I am not knowledgeable enough to even figure out how to restore my phone to factory, I am freaking the hell out! Is there one of you gurus would could save me from my madness. I saw all these cool ROMs, wanted to try them and now my phone is little more than a moving graphic. Please help!!!!
Your extracting the boot IMG from the ROM zip?
Then fastboot flash boot.img
Sent from my HOX w/CM10.1
subarudroid said:
Your extracting the boot IMG from the ROM zip?
Then fastboot flash boot.img
Sent from my HOX w/CM10.1
Click to expand...
Click to collapse
Thanks for responding. Yes, I took the boot.img from the ROM and have tried repeatedly to do the fastboot thing. For some reason, whenevr I enter the command, I get a rush of gibberish (I pasted what I get below). Then I reboot and all and nothing changes, it'll sit at the bootloop forever.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Eric>adb>fastboot flash boot boot.img
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this ocmmand with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\Users\Eric>
OK let try and make this easy.
Download a stock ROM ie Scotts ROM then flash that in recovery and it should boot up just fine.
Then us the apk in this thread to flash the boot.IMG. http://forum.xda-developers.com/showthread.php?p=33463262
for any ROM you want. If you get some time read up on downgrading the Hboot with jet. But that should get you going. Let me know if you need anymore help
Sent from my HOX w/CM10.1
subarudroid said:
OK let try and make this easy.
Download a stock ROM ie Scotts ROM then flash that in recovery and it should boot up just fine.
Then us the apk in this thread to flash the boot.IMG. http://forum.xda-developers.com/showthread.php?p=33463262
for any ROM you want. If you get some time read up on downgrading the Hboot with jet. But that should get you going. Let me know if you need anymore help
Sent from my HOX w/CM10.1
Click to expand...
Click to collapse
Ok, where do I find Scotts ROM? It will somehow circumvent the issue? I will use the apk you gave me when I get this up and running. Thanks so much man, I'm still super new to this.
http://forum.xda-developers.com/showthread.php?p=37672182
There you go. Because your on a stock kernel or stuck with that till you can flash a boot.img this should boot up after you flash it.
Sent from my HOX w/CM10.1
---------- Post added at 05:50 PM ---------- Previous post was at 05:49 PM ----------
One more thing for some light reading to help you out.
http://forum.xda-developers.com/showthread.php?p=33303798
Sent from my HOX w/CM10.1
subarudroid said:
http://forum.xda-developers.com/showthread.php?p=37672182
There you go. Because your on a stock kernel or stuck with that till you can flash a boot.img this should boot up after you flash it.
Sent from my HOX w/CM10.1
---------- Post added at 05:50 PM ---------- Previous post was at 05:49 PM ----------
One more thing for some light reading to help you out.
http://forum.xda-developers.com/showthread.php?p=33303798
Sent from my HOX w/CM10.1
Click to expand...
Click to collapse
Thanks so much for all the help guys, but I am still hitting the same error. In the TWRP window, the one that pops up once I swipe to confirm that I wish to flash, i am still seeing "E:Unable to mount '/data', and then when I reboot , I get stuck. Do I need to start looking for a new phone here? Starting to worry me now
Forget what twrp says, when you plug into PC check for the drive you may have to format. You are very far from needing a new phone!
Sent from my HOX w/CM10.1
subarudroid said:
Forget what twrp says, when you plug into PC check for the drive you may have to format. You are very far from needing a new phone!
Sent from my HOX w/CM10.1
Click to expand...
Click to collapse
Glad to hear that lol Not showing up on my computer, though I can reset into recovery, mount the drive and find it that way. Should I reformat, place them on there and try again? Right now it flashes some white squares every 2 mins or so and then powers down and then on again.
http://forums.team-nocturnal.com/showthread.php/1050
Check out this link
3.0 USB can be a problem. Make sure you HTC drivers are installed.
Sent from my HOX w/CM10.1
---------- Post added at 07:18 PM ---------- Previous post was at 07:10 PM ----------
gulley81283 said:
Thanks so much for all the help guys, but I am still hitting the same error. In the TWRP window, the one that pops up once I swipe to confirm that I wish to flash, i am still seeing "E:Unable to mount '/data', and then when I reboot , I get stuck. Do I need to start looking for a new phone here? Starting to worry me now
Click to expand...
Click to collapse
Are you able to transfer the ROM zip? If so unchecked md5 before you flash.
Sent from my HOX w/CM10.1
I also am suddenly unable to boot any rom...
Lets learn how to hit the thanks button for a guy thats totally saving your ass huh..?
Sent from my HTC One XL using xda premium
These guys can't figure out how to do anything right. They can't be expected to figure out how to thank anyone
Sent from my HTC One XL
954wrecker said:
These guys can't figure out how to do anything right. They can't be expected to figure out how to thank anyone
Sent from my HTC One XL
Click to expand...
Click to collapse
Or we're just decently new the site and thus don't know all of the protocols and customs. Don't be a ****, son.
Being a **** would be sending folks on a wild goose chase or perhaps help permabrick your device. We take time away from our family,work,lives to help ungrateful people fix there devices. And all we freakin ask is for them to hit the thanks button.
Sent from my HOX w/CM10.1 4.2.2 s-off
I'm on a meme kick today tgif
Sent from my HOX w/CM10.1 4.2.2 s-off
The first question to all of these threads should be "DO YOU HAVE THE RIGHT FORUM?" I bet at least one of these complaints is someone with a quad-core....
subarudroid said:
I'm on a meme kick today tgif
Sent from my HOX w/CM10.1 4.2.2 s-off
Click to expand...
Click to collapse
Again, I'm ungrateful because I don't know the customs of the site? Once your rude buddy up there brought it up, I went back and actually clicked the "thanks" button. is there anything further needed to justify my thanks or will that suffice? You guys take this stuff a bit too seriously, me thinks.
Hold on..... I never said you were or are ungrateful. it just so happens if sinco or wrecker did not make a "rude" statement you would have not hit the thanks. You just confirmed that's why you did so. I do the same for them when they are helping out in a thread. Its just constructive criticism. There was no need for name calling like penis or vagina. We are here to help. that's the worst hazing you get..... For now
Sent from my HOX w/CM10.1 4.2.2 s-off
gulley81283 said:
Again, I'm ungrateful because I don't know the customs of the site? Once your rude buddy up there brought it up, I went back and actually clicked the "thanks" button. is there anything further needed to justify my thanks or will that suffice? You guys take this stuff a bit too seriously, me thinks.
Click to expand...
Click to collapse
Dude, get some thicker skin or kindly eff off, will you? Jesus. Hissy fit over nothing.
Related
I was wondering how i can change my boot screen to the Nexus Boot, i have the files to do it but dont now how, any help would be appreciated!!
If this is in the wrong section sorry!!
Also i am using the rom MLIGNv.1.1
It depends...
Hi - It depends on the rom you are using. I hope the following helps.
This is how I changed mine (you mentioned that you already have the animation):
(This will only work for Hero ROMs such as CaSense, MyHero, MLIGN. Will not work for CynanogenMod)
The bootscreen is stored in the /system/media/bootscreen folder. I suggest you open up the rom zip file to see the files in this folder. The file boot_animation.xml defines the animation scheme.
You should scan through the file to find something like this:
Code:
<BootConfiguration>
<BootAnimation image="/system/media/bootscreen/hvga_android_006spf.gif"
image2="/system/media/bootscreen/hvga_htc_in_006spf.gif"
loopimage="/system/media/bootscreen/hvga_htc_loop_006spf.gif"
image_bg="/system/media/bootscreen/boot_bg.gif"
audio="/system/media/bootscreen/android_audio.mp3"
screenX="0"
screenY="55"
useAudio="1" />
</BootConfiguration>
"image" is the first animated image displayed (of what I have seen of the different ROMs, this usually has Google's Androids in some form or the other, either with a Hero written or without). "image2" is a static image (in my case, it shows a static HTC logo). "audio" is the sound that is played. "loopimage" is the animation (in my case, it showed the HTC logo with a flare running across"). The "loopimage" is the one that you have to change.
From here on you have two options:
1) More risky, but correct: Modify the boot_animation.xml file based on the above description, change the file to use your file (replace the filenames) and push into the system/media/bootscreen folder
Don't add the words in brackets:
Code:
adb remount (mount the root filesystem in read-write mode)
adb push boot_animation.xml /system/media/bootscreen (this assumes that the boot_animation.xml file is in the same folder as adb)
adb push nexus_animation.gif /system/media/bootscreen (replace nexus_animation.gif with whatever is the filename for the nexus one animation that you have. Also make sure that this is the name of the image in boot_animation.xml)
2) Less risky, but its more of a workaround: In the boot_animation.xml file, check the name of the image under the "loopimage" tag (in the above case it is hvga_htc_loop_006spf.gif). Then make a backup of this image, and then replace this file with the nexus animation.
Don't add the words in brackets:
Code:
adb pull system/media/bootscreen/hvga_htc_loop_006spf.gif (backup)
ren hvga_htc_loop_006spf.gif backup_animation.gif (rename)
ren nexus_animation.gif hvga_htc_loop_006spf.gif (assuming that the nexus_animation.gif is in the same folder)
adb remount (mount the root filesystem in read-write mode)
adb push hvga_htc_loop_006spf.gif system/media/bootscreen/
The advantage with this method is that if something goes wrong, the android bootup will be displayed, instead of the nexus animation, and we have not modified the boot_animation.xml file in anyway. So chances of screw-ups are low.
In either case, restart the phone and you should see the nexus animation.
Obligatory warning: Though I can confirm this has worked, I will not take responsibility for any bricked phones, however remote the possibility for this to happen as you are not making any big changes.
Best of luck!
Slash
Simple
Just update to an Eclair rom both ManUp and Eugene have the Nexus one boot animation.
slash .. that was really interesting idea .. can u provide a vid .. that shows the step works .. splash image>animates boot > home screen > setting > about phone
but i did notice that .. custom ROM eg.CyanMod .. does not have any kind of this folder u said in ur post
/system/media/bootscreen
/system/media/bootanimation
this .zip file only avail in 2.0 custom ROM ..
if i did follow ur step .. then how about our normal boot image setup ?? coz currently i change my boot image to my custom made design that had been told in this thread
http://forum.xda-developers.com/showthread.php?t=527200
is it the custom .png image will disturb/effect our new animation boot image ..
consider we use CyanogenMod
hoping for ur great reply
thx in advance
hey i tried the second one and when i connect my phone to the SDK and then type:
Code:
pull system/media/bootscreen/hvga_htc_loop_006spf.gif
all i get is
Code:
Android Debug Bridge version 1.0.25
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
envivornment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP disconnect <host
>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] <file> - push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB adb
tcpip <port> - restarts the adbd daemon listening on TCP on the spec
ified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
idno wat the problem is?
....
OK. This is getting interesting:
tera89: The instructions I had were for Hero ROMs (I am really sorry for not mentioning that). I see from the link that you gave that the basic version of Android (and Cyanogen's mod for that matter) create animations VERY differently. Hero ROMs just show an animated GIF. I don't think the Nexus One boot screen animation can be used with Cyanogenmod. In case you decide to shift to a Hero Rom just to have the Nexus One animation (I dont see that happening, but anyways), I would suggest CaSense (http://forum.xda-developers.com/showthread.php?t=576445 - very stable, have been using it since the past 1.5 months now).
crisvillani: I suggest exploring the filesystem to check whether the /system/media/bootscreen folder exists and what files are there. One way is to check the zip file you downloaded for flashing the rom and checking the system/media folder inside that (of course, if you are using Cyanogen's mod, it wont be there). The other way is to open up the command prompt in windows: For example here's what my directory structure looks like (make sure you are in the folder where you have the android sdk installed, or you have the path in your system path):
Code:
D:\Downloads\Android\android-sdk-windows-1.6_r1\android-sdk-windows-1.6_r1\tools
>adb shell
* daemon not running. starting it now *
* daemon started successfully *
# cd /system/media/bootscreen
cd /system/media/bootscreen
# ls
ls
←[0;0mBootup_020609.gif←[0m ←[0;0mboot1.gif←[0m
←[0;0mhvga_android_006spf.gif←[0m
←[0;0mandroid_audio.mp3←[0m ←[0;0mboot2.gif←[0m
←[0;0mhvga_htc_in_006spf.gif←[0m
←[0;0mboot.gif←[0m ←[0;0mboot_animation.xml←[0m
←[0;0mhvga_htc_loop_006spf.gif←[0m
←[0;0mboot.mp3←[0m ←[0;0mboot_bg.gif←[0m
# exit
exit
D:\Downloads\Android\android-sdk-windows-1.6_r1\android-sdk-windows-1.6_r1\tools
>
In between the random characters (←[0;0m), you should see the filenames that exist. I suggest starting with the boot_animation.xml. In case the system/media/bootscreen folder does not exist, you will get an error at the second command (cd /system/media/bootscreen)
Let me know if this helps.
Best,
Slash
Mlign
So I downloaded MLIGN's rom from http://forum.xda-developers.com/showthread.php?t=593759 and checked it. The structure is very similar to the CaSense ROM.
Sorry for the wrong commands (am editing my previous post in a moment)
Try:
Code:
adb pull system/media/bootscreen/hvga_htc_loop_006spf.gif c:\
or any other folder instead of c:\ where you want to backup the image.
Another thing, before you will be able to push the new file, you will need to remount the filesystem in a read-write mode using:
Code:
adb remount
I am correcting the original post so that you have all the commands in the right order for method 2.
Best,
Slash
PS> I don't have a webcam handy, so I can't show the phone booting with the Nexus animation. But, it does work
thxs will try the new commands now
Alright did it got the first two commands right but when i do:
Code:
adb push hvga_htc_loop_006spf.gif system/media/bootscreen/
i get this:
Code:
C:\AndroidSDK\tools>adb remount
remount succeeded
C:\AndroidSDK\tools>adb push hvga_htc_loop_006spf.gif system/media/bootscreen/
failed to copy 'hvga_htc_loop_006spf.gif' to 'system/media/bootscreen//hvga_htc_
loop_006spf.gif': No space left on device
C:\AndroidSDK\tools>
what now?
Try flashing this update.zip file (after nandroid backup of course!!!)
http://www.theandroidkitchen.com/CursorSense/CursorSense32A-NexusBootscreen-signed.zip
tried it didnt work!
just to clarify i have an htc magic 32A with MLIGN v.1.1
crisvillani said:
tried it didnt work!
just to clarify i have an htc magic 32A with MLIGN v.1.1
Click to expand...
Click to collapse
What was the error, if any?
Free some space
Looks like you ran out of space on your system partition. I searched through the forums for options. One I got was to restart the device and try again.
The only other thing I can suggest is to delete some safe files from the system folder (such as ringtones/wallpapers that you never have and never will use) to make some space.
Fire up a shell (adb shell) and then check in the system/media/audio/ringtones folder and delete (for example, rm Bubble.mp3) some files. Wallpapers are in system/customize/resource/
Slash
there was no error it flashed with no errors but when i reboot iget the same bootscreen
crisvillani said:
there was no error it flashed with no errors but when i reboot iget the same bootscreen
Click to expand...
Click to collapse
Oh, OK, MLIGN must have his bootscreen in a different folder...
the bootscreen is in system/media/bootscreen
slash12345 said:
Looks like you ran out of space on your system partition. I searched through the forums for options. One I got was to restart the device and try again.
The only other thing I can suggest is to delete some safe files from the system folder (such as ringtones/wallpapers that you never have and never will use) to make some space.
Fire up a shell (adb shell) and then check in the system/media/audio/ringtones folder and delete (for example, rm Bubble.mp3) some files. Wallpapers are in system/customize/resource/
Slash
Click to expand...
Click to collapse
could u plzz tell me exactly what to do not to familiar with adb shell
>adb shell
#adb remount
#cd /system/media/audio/ringtones
#ls
You'll see a list of files. Delete the one's you don't want using the rm command. For example,
#rm Bubble.mp3
(replace Bubble.mp3 with the filename you want to remove)
I think deleting 1-2 files should be enough. Then try pushing in the nexus animation again.
hey removed a couple of ringtones still get no space error!
wat ever it fine ill just stay with wat i got, ill wait until MLIGN adds it to his ROM in a future update
Thank you for the help though it was greatly aprreciated !!
Its the space!
I checked the filesizes of the animations, and now the error makes sense. The normal HTC logo animation is some 207K, while the Nexus One animation is ... wait for it ... 1,348K! The difference is more than 1 MB!
No wonder removing some ringtones did not make a difference. Each ringtone is less than 100K.
It seems that the best bet is to wait it out.
Hopefully, someone will cook a Nexus One ROM for us as a New Year present
This tool is now deprecated. To root your Evo 4G running Gingerbread you will need to use the Revolutionary tool that can be found at http://www.revolutionary.io.
I'm sorry to do it but due to the ridiculous amount of people who are still asking for help rooting gingerbread, I will no longer be supporting this tool what so ever. Any further emails I receive about it will be deleted.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I am proud to present the HTC EVO Auto Root script! It took me awhile but I finally got it fully automated, it probably would have been easier using VB to write it but I wanted it to be readable by everybody. I don't have working scripts for Linux or Mac yet but for older phones you should be able to follow the Alternative Method and use the code included at the end of the post with minimal changes. If you are new to rooting the Evo you should check out the Rooting Information and Common Problems thread to familiarize yourself with some of the screens you will see. At times your phone may shows ominous looking icons that look bad but really aren't, at times like that it is important that you don't panic and do anything that could damage your phone.
This will make a backup of your WiMAX partition and the RSA keys that are stored on it; backing up your RSA keys separate is not necessary. It will save it in the AutoRoot folder so be sure not to delete it.
If you run into any problems please include the following information with your post: Any methods you have previously tried to root with, what it did last plus any error messages it may have given (if you can right click, select all and copy it from the terminal), and if you are in the bootloader we need to know what the top two lines say. Running this will create a log file named: autorootlog.txt. Please post this as well.
Any feedback no matter good or bad is appreciated! Let me know how it works for you.
Randy (randyshear on youtube) has made a great video of the process if you would like to get an idea of what to expect before hand. It is important to note that, depending on your phone, the process may be slightly more involved or require more or less time.
HTC EVO 4G ** ROOT AND NAND UNLOCK ** AUTOROOT V 2.2 ** HOW TO **
This has been confirmed working with:
Software versions 1.32, 1.36, 3.29, 3.30 & 3.70
hBoot Version .76, .93, .97, 2.02 & 2.10
Thanks go to
HTC for making the phone to begin with
Sebastian Khramer for his rageagainstthecage exploit
Toastcfh for his tutorial and all of his work on improving the Evo, a lot of this is borrowed from his previous work
Amon_RA for his recoveries and for his quick work creating a recovery compatible with the new NAND blocks
Calkulin for collecting all of the radios and update images
Whosdaman, Football and Sniper911 for sharing the RUUs with us
The Unrevoked Crew for all of their hard work on the Unrevoked Forever s-off tool
amoamare and Zikronix for all of their hard work on rooting phones with the 2.02 hboot
chris1683 for his Sprint Lovers ROM
Netarchy for all of the great kernels
A huge thanks goes out to Dan0412 who took the time to debug this for version 003 2.02 phones
Schnick1 and tauzins for their help with getting ADB to act right
Props go to RyanZA and anyone else who worked on the z4root app. I wouldn't have got 3.70 rooted as fast as I did if I didn't have their app to learn from.
You Will Need:
A windows machine
HTC Sync that can be found on Sprint's website. HTC Sync 2.0.35.exe
At least 1 GB of free space on your SD card
A full or close to full battery (your phone will not charge during part of this and if it dies you will be SOL, aka Bricked)
ADB debugging enabled (Settings > Applications > Development > ADB Debugging)
Your phone connected to your computer as Charge Only and HTC's Evo drivers / HTC Sync installed.
The AutoRoot.zip File that can be found in this post
[*]I highly recommend you have the appropriate RUU, or PC36IMG, downloaded before you start. It is always good to have and if something does not go as planned it can get your phone back up and running with minimal down time.
Click to expand...
Click to collapse
IF YOU HAVE PREVIOUSLY TRIED ROOTING YOU MUST RESTORE FROM A RUU BEFORE RUNNING THIS. IT WILL NOT ROOT IT UNLESS YOU DO THIS.
Instructions:
This will try to back up your apps but it's not always able to, you will also lose all of your settings. Titanium Backup works well to save your apps however you will need to use z4root to temporarily root before you will be able to use it.
Download HTC Sync from Sprint's website here and install it. You may need to use the 'Repair' option for it to replace any old drivers.
Extract AutoRoot.zip into a folder that is easy to find and then open the folder.
Right click on 'AutoRoot.bat' and run it as Administrator.
Once it finds your phone it will start by checking out what kind of setup it uses and then attempt to get root access. If it fails usually it's from too many active apps or the phone being used, if so you will need to restart it before trying again. If you are using 3.70 it will let you know when it is running by blurring the screen.
When it is ready it will reboot your phone into the boot loader. Then, depending on your phones setup, it will either enter RUU mode and automatically flash the debugging firmware or give you instructions on how to flash it from the hBoot.
If you have to flash it manually just push Power to select "BOOTLOADER" and say Yes when it asks to flash the PC36IMG.zip. It will complain part of the way through about Boot Loader and/or radio errors and then skip them, this is normal. Once it finishes say No when asked to reboot and use the Vol Down button to highlight Recovery. Then press Power to select it.
If you are entering the Recovery your phone will show a Red Triangle with an Exclamation mark inside, at this point the script will take back over and attempt to flash Unrevoked Forever.
After it finishes flashing the engineering bootloader, or Unrevoked Forever, it will reboot into the bootloader and see if your NAND is unlocked. If so it will flash the Sprint Lovers ROM along with the Recovery and updated Radios. Afterward it may boot into the ROM and attempt to restore your Apps before finishing, try not to interrupt it until it tells you it has finished.
Once it's fully rooted and you have your phone set back up it's a good idea to make one more NANDroid with everything up to date. Then make one more backup of your WiMAX partition in case something happens to the first one.
Click to expand...
Click to collapse
If you have an older phone and don't want to flash Unrevoked Forever or Sprint Lovers w/ the radio updates you can have it skip them. It will just flash the engineering bootloader to unlock the NAND and then flash the recovery directly from there. You will need to update everything and flash a custom ROM on your own. This will only work if your phone has a version .9x hBoot.
Instructions for Quick method:
This will completely wipe your phone. If you would like to back up your apps you can use Titanium backup to save them. It also has an option to save the system files but this can result in a buggy ROM afterward.
Extract AutoRoot.zip into a folder that is easy to find.
Open a DOS prompt by running the OpenShell file.
Type 'autoroot quick' and press Enter
It will then flash the engineering bootloader and the recovery through fastboot. Once it is finished you can use the bootloader menu to boot into the recovery and make a NANDroid, flash a ROM, radios, etc.
Click to expand...
Click to collapse
Links:
Downloads
AutoRoot v2.5 - Full Root Zip (MD5: 5E1BF365F3B5479329896BD55C33678E)
AutoRoot v2.5 - Tools Only (MD5: 5DBA70A8CDD052A9908E4F43D6BBC669)
The following are the ROMs pulled out of the RUUs, you can flash them by renaming and putting it on your sd card or from your computer with fastboot using the included FlashZip script.
Sprint Evos (USA):
3.29.651.5_PC36IMG.zip (MD5: 2F5046C0FC6FE61114EBC53D5997B485)
3.30.651.2_PC36IMG.zip (MD5: 4A2CAB264244C79B2E2BE9E3CFE2B503)
3.70.651.1_PC36IMG.zip (MD5: 7056D42812AA5DF03FCC8DDDC2B64E85)
KDDI Evos (Japan):
1.05.970.1_PC36IMG.zip (MD5: 78F9E8BFEE705F34790A46C258268F02)
Sources
How to unlock Nand Protection ~ Part-2
RA-evo-v1.8.0 (a modified version is included)
RUU to restore 3.29.651.5
RUU to restore 3.30.651.2
RUU to restore 3.70.651.1 (Thanks to 911Sniper for the original mirror)
Sprint Lovers ROM (a modified version is included)
Click to expand...
Click to collapse
Changes for v2.5
Script now checks for Admin Priveledges and kills HTC Sync Services for Sync 3.05
Fixed issue recognizing build numbers
It will attempt to back up Apps now
Checks branding in order to recognize KDDI Evos
Unrevoked forever will now be retried if it doesn't get run the first try
Changed it so it will leave the phones in Fastboot mode if it fails
Recognizes ADB issues easier now
Changes for v2.4
Updated the ROM and Recovery
The working directory is now saved correctly when the path has a space in it
Fixed an error checking the firmware version that would cause the script to close
Made it more capable of recovering when the phone is in an unknown state
Fixed the SD card not being recognized with Eclair
Some parts will check for the 'daemon' error messages and will call to fix it
Made it so the MTD data is not saved unless it is recognized
The script will continue if it times out while waiting on Unrevoked Forever
The WiMAX partition is backed up through the ROM at the very beginning instead of through the Recovery
Changes for v2.3:
Updated the ROM, Recovery and Radios
The script will now recognize your phone at any point in the process and will continue where it left off
Fixed the FlashRecovery script and made it so you can choose what to flash, just put your PC36IMG of choice in the folder with it and let it do the work
Fixed the version checker so it doesn't get confused with custom ROMs anymore
Quick mode checks your hboot version from the ROM now so it won't even try if you have a new bootloader
It is much more tenacious going into the recovery, hopefully fixing the issue with ADB dropping out there
Fixed a bug where the MTD block sizes were not always being remembered correctly
Added more checks to make sure the phone is where it's supposed to be throughout the process
Made it try harder to get the recovery log so it doesn't get missed as much
Tweaked the timing some so it moves a little bit quicker and you only have to hit a button twice to exit instead of three times
Fixed the infinite loops so they are now 95% shorter
Changes for v2.2:
Updated the recovery to Amon RA's version 2.2.1
MTD information for each phone is saved in case it is restarted and unable to find out.
Fixed a bug where pre 3.xx ROMs were not being recognized correctly.
Phones are explicitly called by their serial number to prevent confusion if an emulator starts or another phone gets plugged in.
Unresponsive ADB daemons are killed to help prevent them for hanging or randomly restarting.
Changed autoroot.log to autorootlog.txt to make it easier to attach
Minor bug fixes.
Changes for v2.1:
Updated the recovery to Amon RA's version 2.2
Minor bug fixes
Changes for v2.0:
Added an app to give ADB root and keep it active in 3.70
Updated Sprint Lovers and Amon RA
Removed the two separate kernels/recoveries for new and old phones
Added a battery life check before flashing
Checks Firmware versions in both the ROM and hBoot
Checks that the Misc partition was flashed properly
Fixed all of the bugs with Quick root, it no longer flashes Sprint Lovers if you run it with S-OFF
It automatically restarts adbd where it would occasionally reset itself and get hung up
It also kills adbd when it finishes so you can move/delete it
Changed the bat that restarted adbd so it kills it instead
Added a bat to flash AmonRA through Fastboot with non-Eng hBoots
Added a bat to open a Cmd prompt already in the autoroot folder
Rewrote a good portion of the script and cleaned it up a lot
Made it more flexible so it doesn't get lost as easily
Plus more I forgot
Click to expand...
Click to collapse
Contents of v2.5 Include:
adb.exe
adb-linux
adb-mac
adbWinapi.dll
adbWinusbapi.dll
AutoRoot.bat
check.bat
fastboot.exe
fastboot-linux
fastboot-mac
FindPhone.bat
FlashZip.bat
OpenShell.bat
StartRecovery.bat
amon_ra_1.8-mod/
res/
....AutoRoot.apk
....autoroot.ini
....dump_image
....Escalate.vbs
....Escalater.bat
....EscSC.lnk
....exploid.com
....FindPhone.bat
....flash_image
....ini.cmd
....mtd-eng.img
....PC36IMG_UD.zip
....PC36IMG_AmonRA-v2.3-hausmod_revA.zip
....PC36IMG-SprintLovers-AmonRA_2.3-hausmod_revA.zip
....radios.zip
....rageagainstthecage-arm5.bin
....recovery-RA-v2.3-hausmod_revA.img
....URFSOff.zip
....URFSOn.zip
....WatchPhone.bat
Notes:
Recovery is recovery-RA-supersonic-v2.3 with Netarchy's 4.3.2 CFS NoHAVS NoSBC NoUV
radios.zip is EVO_Radio_2.15.00.11.19_WiMAX_27167_R01_PRI_NV_1.90_003
URFSOff.zip is the Unrevoked Forever S-OFF tool
URFSOn.zip is the Unrevoked Forever S-ON tool
Click to expand...
Click to collapse
As always, this will void your warranty and may possibly damage your phone. You and you alone are responsible for anything that you do. Everything contained in this thread is for informational purposes only.
Click to expand...
Click to collapse
IMPORTANT: Everything contained in this post is meant for phones with the older bootloader. If you have hBoot version 2.02 or ROM version 3.30 you must use the above method.
Old Universal Root
(Scroll Down for Alternate Method)
You Will Need:
A windows machine and basic knowledge of DOS or a Linux/Mac box with a little bit of determination
At least 1 GB of free space on your SD card
A full or close to full battery
ADB debugging enabled (Settings > Applications > Development > ADB Debugging)
Your phone connected to your computer as Charge Only
The EVORoot.zip File that can be found in this post
Click to expand...
Click to collapse
Instructions:
Extract EVORoot.zip into a folder that is easy to find and go to that folder. Then copy the 'moveme' folder out of that one and on to your sdcard. Once it finishes copying unmount/eject the SD card through windows and change your phone back to Charge Only.
Double click on 'runexploit' and let it run. When it asks if you want to flash the hBoot push 'y' and then {enter}. If there are any errors follow the instructions given to try and resolve them. It will automatically reboot your phone once it is ready for it. If all you see is the prompt flashing press Ctrl+C or close the window to exit and re-run it as Administrator.
When the bootloader comes up push the Power button and you should see it start searching for updates. When it gets to PC36IMG.zip it will ask if you want to update with it, push Volume Up to say yes.
*DO NOT TURN OFF THE PHONE OR LET THE BATTERY DIE WHILE UPDATING*
When it's finished push the power button to select 'fastboot' and use the volume buttons to select the yellow 'reboot' button. Push power one more time to select it and reboot your phone. It should start up rooted and ready to go, however you will still need a custom Recovery so you can make NANDroid back-ups and flash an up to date ROM.
Once the phone starts back up run 'flashrecovery' through explorer. It will automatically flash and then reboot your phone into Amon_RA's recovery. When it reboots you should see green text on a black background, if you see a triangle with an exclamation mark then you still have the stock recovery and need to reboot and try again.
Use the volume buttons to select Backup/Restore then push Power to select it.
Select Nand backup and push power. This will make an exact copy of your phone as it is. If you get an error that says 'run mobile-nandroid...." make sure you have at least 3 or 400MB free on your memory card. You can use USB-MS toggle to mount your SD card if you need to make room or copy a ROM to your phone. The moveme folder can also be deleted from your SD card at this point and you can make copies or move the backup once it is complete. Just make sure you have one good backup before continuing.
The NANDroids are saved under 'nandroid/??????????/backupfolder-date-time/'. The folders need to be moved whole.
Return to previous menu, select Wipe, then have it Wipe data/factory reset, Wipe cache & Wipe dalvik-cache. If you get stuck in a bootloop try these steps again and try wiping the SD:ext partition as well.
Return, then go in Flash zip from sdcard. Once there flash the Radios. It is again very important not to interrupt or reset the phone while the radios are being flashed, although it will probably want to reboot before flashing can be finalized, just follow the instructions.
Once it is finished Return to the previous menu and select Power Off. Then hold down the vol down button while turning the phone back on.
It will boot back up into the bootloader, select No if it asks to update or reboot. From here select Recovery and it should go back to the black background with green text.
Select Flash zip from sdcard and Flash ROM-Supersonic_3.30....zip. If you have a different ROM you want to use you can flash another one instead.
Once it is finished Return to the main menu and have it Reboot system. Your phone should start up normally and ask to be set up, complete the set up like normal.
When you have it set up and are sure everything is working properly I would make one more NANDroid so you have a copy with the updated radios. At this point you can also flash another recovery and do anything else you would normally do. Just be sure to use unrevoked forever if you plan on using a different hBoot.
Click to expand...
Click to collapse
Links:
Downloads
EVORoot.zip
EVORoot.zip - No bootloader, ROM or Radio updates
eng-PC36IMG.zip mirror 1, mirror 2
The following are the ROMs pulled out of the RUUs and renamed, make sure you use the correct version for your phone but if you aren't able to find out start with the 3.29.
3.29.651.5_PC36IMG.zip
3.30.651.2_PC36IMG.zip
If you are having trouble flashing custom ROMs try using this kernel (Thanks to xxbabiboi228xx)
Stock kernel #17
Sources
How to unlock Nand Protection ~ Part-2
All EVO Radio, WiMAX, PRI & NV versions
RA-evo-v1.8.0
RUU to restore 3.29.651.5
RUU to restore 3.30.651.2
Click to expand...
Click to collapse
Contents Include:
adb.exe
adb-linux
adb-mac
adbWinapi.dll
adbWinusbapi.dll
exploid.com
flashboot.bat
flashrecovery.bat
runexploit.bat
moveme/
.....eng-PC36IMG.zip
.....evo_radios_wimax_pri_nv_3.30.zip
.....flash_image
.....mtd-eng.img
.....rageagainstthecage-arm5.bin
.....recovery-RA-evo-v1.8.0.img
.....SuperSonic_3.30.651.2_Rooted_BB_DeOdexed_Bash_ADP_BattPrcnt.zip
Click to expand...
Click to collapse
Alternate method
If you already have the EVORoot.zip file you can download the scripts below without the boot/ROM/radio.
Instructions:
Extract EVORoot.zip into a folder that is easy to find such as C:\EVORoot. Then copy the 'moveme' folder out of that one and on to your sdcard.
Open up a DOS prompt and go to the EVORoot directory. eg. 'cd C:\EVORoot'.
type: runexploit {enter}
It will scroll a few lines saying that the ADB server will be reset and to run it on the desktop, this is normal. If it says Permission Denied check to make sure your phone is set to charge only and your sd card is not mounted as a hard disk.
type: adb shell {enter}
If you see '$' then type: "./data/local/tmp/rageagainstthecage-arm5.bin", without the quotation marks, and push enter. After a few seconds it should kick you out to the \> prompt.
If you see '#' then type: exit {enter}
type: flashboot {enter}
If you don't see any errors let it continue, if you do see an error push Ctrl+X to stop
Your phone will then reboot, when it comes back up the bootloader option should be highlight. Press the power button to select it. It should then search for a second and ask if you want to install the pc36img.zip, push Volume Up for Yes.
*DO NOT TURN OFF THE PHONE OR LET THE BATTERY DIE WHILE UPDATING*
When it's finished go into fastboot and select the yellow 'reboot' through the menu, it should start up rooted and ready to go however you will still need a custom Recovery so you can make NANDroid back-ups and flash an up to date ROM.
Once the phone starts up do step #4 to check for root (# prompt), if it is a '$' try typing 'su {enter}'. If that does not work use runexploit and then check again. Return to the DOS prompt once finished.
type: flashrecovery {enter}
Let it continue as long as there are no errors, otherwise Ctrl+X will stop it. If you run this more than once you can ignore the file not found errors from when it first starts. When the phone reboots you should see green text on a black background, if you see a triangle with an exclamation mark then you still have the stock recovery.
Use the volume buttons to select Backup/Restore then push Power to select it.
Select Nand backup and push power. This will make an exact copy of your phone as it is. If you get an error that says 'run mobile-nandroid...." make sure you have at least 3 or 400MB free on your memory card. You can use USB-MS toggle to mount your SD card if you need to make room or copy a ROM to your phone. The moveme folder can also be deleted from your SD card at this point and you can make copies or move the backup once it is complete. Just make sure you have one good backup before continuing.
The NANDroids are saved under 'nandroid/??????????/backupfolder-date-time/'. The folders need to be moved whole.
Return to previous menu, select Wipe, then have it Wipe data/factory reset, Wipe cache & Wipe dalvik-cache. If you get stuck in a bootloop try these steps again and try wiping the SD:ext partition as well.
Return, then go in Flash zip from sdcard. Select and Flash ROM-Supersonic_3.30....zip. If you have a different ROM you want to use you can flash that one instead.
Flash the Radios, it is again very important not to interrupt or reset the phone while the radios are being flashed. It will probably want to reboot itself afterward, just follow the instructions.
Once it is finished Return to the main menu and have it Reboot system. Your phone should start up normally and ask to be set up, complete the set up like normal.
Once you have it set up and are sure everything is working properly I would make one more NANDroid so you have a copy with the updated radios. At this point you can also flash another recovery and do anything else you would normally do. Just be sure to use unrevoked forever if you plan on using a different hBoot.
Click to expand...
Click to collapse
Links:
Downloads
EVORoot.zip
EVORoot.zip - No bootloader, ROM or Radio updates
eng-PC36IMG.zip mirror 1, mirror 2
Click to expand...
Click to collapse
Contents Include:
adb.exe
adb-linux
adb-mac
adbWinapi.dll
adbWinusbapi.dll
flashboot.bat
flashrecovery.bat
runexploit.bat
moveme/
.....eng-PC36IMG.zip
.....evo_radios_wimax_pri_nv_3.30.zip
.....flash_image
.....mtd-eng.img
.....rageagainstthecage-arm5.bin
.....recovery-RA-evo-v1.8.0.img
.....SuperSonic_3.30.651.2_Rooted_BB_DeOdexed_Bash_ADP_BattPrcnt.zip
Batch Files
runexploit.bat
Code:
adb shell "cat /sdcard/moveme/rageagainstthecage-arm5.bin > /data/local/tmp/rageagainstthecage-arm5.bin"
adb shell "chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin"
adb shell "./data/local/tmp/rageagainstthecage-arm5.bin"
flashboot.bat
Code:
adb shell "cat /sdcard/moveme/flash_image > /data/flash_image"
adb shell "chmod 755 /data/flash_image"
adb shell "/data/flash_image misc /sdcard/moveme/mtd-eng.img"
adb shell "mv /sdcard/moveme/eng-pc36img.zip /sdcard/pc36img.zip"
adb shell sync
adb reboot bootloader
flashrecovery.bat
Code:
adb shell "mv /sdcard/PC36IMG.zip /sdcard/moveme/eng-PC36IMG.zip"
adb shell "mv /sdcard/moveme/evo_radio_wimax_pri_nv_3.30.zip /sdcard/evo_radio_wimax_pri_nv_3.30.zip"
adb shell "mv /sdcard/moveme/SuperSonic_3.30.651.2_Rooted_BB_DeOdexed_Bash_ADP_BattPrcnt.zip /sdcard/ROM-SuperSonic_3.30.651.2_Rooted_BB_DeOdexed_Bash_ADP_BattPrcnt.zip"
adb shell "cat /sdcard/moveme/flash_image > /data/flash_image"
adb shell "chmod 755 /data/flash_image"
adb shell "/data/flash_image recovery /sdcard/moveme/recovery-RA-evo-v1.8.0.img"
adb shell sync
adb reboot recovery
Click to expand...
Click to collapse
This uses HTC's eng hBoot to unlock NAND protection so it is relatively safe, but, as always, this will void your warranty and may possibly damage your phone. You and you alone are responsible for anything that you do. This is for informational purposes only.
Click to expand...
Click to collapse
Here are linux and mac versions. You just need to get adb from somewhere (I don't think the packaged windows version will work).
If it's in your path, just change all of the "./adb" to "adb", or if you copy the executable to the same directory as these scripts, leave them as is.
Put them in the same directory, as the kit, and they should work.
I haven't tested, but thought I would write them up quickly to help with mutli-os support.
runexploit.sh
Code:
#!/bin/bash
./adb shell "cat /sdcard/moveme/rageagainstthecage-arm5.bin > /data/local/tmp/rageagainstthecage-arm5.bin"
./adb shell "chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin"
./adb shell "./data/local/tmp/rageagainstthecage-arm5.bin"
flashboot.sh
Code:
#/bin/bash
./adb shell "cat /sdcard/moveme/flash_image > /data/flash_image"
./adb shell "chmod 755 /data/flash_image"
./adb shell "/data/flash_image misc /sdcard/moveme/mtd-eng.img"
./adb shell "mv /sdcard/moveme/eng-pc36img.zip /sdcard/pc36img.zip"
./adb shell sync
./adb reboot bootloader
flashrecovery.sh
Code:
#!/bin/bash
./adb shell "mv /sdcard/PC36IMG.zip /sdcard/moveme/eng-PC36IMG.zip"
./adb shell "mv /sdcard/moveme/evo_radio_wimax_pri_nv_3.30.zip /sdcard/evo_radio_wimax_pri_nv_3.30.zip"
./adb shell "mv /sdcard/moveme/SuperSonic_3.30.651.2_Rooted_BB_DeOdexed_Bash_ADP_BattPrcnt.zip /sdcard/ROM-SuperSonic_3.30.651.2_Rooted_BB_DeOdexed_Bash_ADP_BattPrcnt.zip"
./adb shell "cat /sdcard/moveme/flash_image > /data/flash_image"
./adb shell "chmod 755 /data/flash_image"
./adb shell "/data/flash_image recovery /sdcard/moveme/recovery-RA-evo-v1.8.0.img"
./adb shell sync
./adb reboot recovery
I'm getting a permission denied when I try to runexploit
Can you post an alternate mirror for the rootkit?
jacobzamarripa said:
I'm getting a permission denied when I try to runexploit
Click to expand...
Click to collapse
Do you have debugging enabled?
MJStephens said:
Do you have debugging enabled?
Click to expand...
Click to collapse
usb debugging. yes
jacobzamarripa said:
usb debugging. yes
Click to expand...
Click to collapse
Are you running cmd.exe as admin?
Do you guys have a youtube video of step by step for this? Because i cant even get past the third step
BrashL said:
Are you running cmd.exe as admin?
Click to expand...
Click to collapse
im not quite sure how. im on windows xp
jacobzamarripa said:
im not quite sure how. im on windows xp
Click to expand...
Click to collapse
Im pretty sure he just means that your on an user name on windows that has Master rights.
Bravo, bravo. You really outdid yourself on this hauss. What a fabulous tutorial for noobs. In my spare time, I would be happy to make a Mac version of this tutorial for you. I think the Mac part jut confuses people more. Seriously, great work. I will be referring people to this. Replaces the need to do 20 commands with like 4 homemade batch scripts. Pm me or email at [email protected] and I will build a Mac tutorial (giving you full credit of course)...
Confirm?
This looks and sounds awesome. I would LOVE a mac version of this and like to donate to good work
Can I get a confirmation from someone reporting success using this method?
I'd like to use this on a friends phone today but am a bit hesitant because it's so new.
thanks!
i will confirm that all the scripts work on thier own. i have no idea if hauss's batch scripts work. all the exploits are legit though. i will download and proofread. either way, it should work. i know hauss is experianced at rooting and stuff.
wait, huge file. does someone mind sending me everything except the pc36img.zip and eng-pc36img.zip? email is [email protected]
does anyone know if it will work on parallels on mac.
adb connection will be reset. restart adb server on desktop and re-login
I keep getting error message saying "adb connection will be reset. restart adb server on desktop and re-login"
--------------------------------------------
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3316, 3316}
[*] Searching for adb ...
[+] Found adb as PID 1400
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
rukshmani said:
I keep getting error message saying "adb connection will be reset. restart adb server on desktop and re-login"
--------------------------------------------
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3316, 3316}
[*] Searching for adb ...
[+] Found adb as PID 1400
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
Click to expand...
Click to collapse
Actually i kept getting this same message when i was on the adb server and was attempting to get to the recovery screeen on the phone. Do you by any chance have HBoot 2.2 on your evo?
Hi Noobe , yes unfortunately..am i SOL
rukshmani said:
i keep getting error message saying "adb connection will be reset. Restart adb server on desktop and re-login"
--------------------------------------------
[*] cve-2010-easy android local root exploit (c) 2010 by 743c
[*] checking nproc limit ...
[+] rlimit_nproc={3316, 3316}
[*] searching for adb ...
[+] found adb as pid 1400
[*] spawning children. Dont type anything and wait for reset!
[*]
[*] if you like what we are doing you can send us paypal money to
[*] [email protected] so we can compensate time, effort and hw costs.
[*] if you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 usd!
[*]
[*] adb connection will be reset. Restart adb server on desktop and re-login.
Click to expand...
Click to collapse
this is not an error message! This means it is working! Just move on to the next step. If there is nothing that says the word error, there is probably no error!
Definition:
ADB is the android debugging bridge that allows you to control your phone from your PC and is a bridge allowing you transfer stuff from it
Fastboot is usually used in bootloader and used a lot in unlocking your bootloader and commands in it
Setting up ADB:
1.Download the ZIP file from the attachments and extract it in C:\SDK\platform-tools (You will need to create these folders)
2. Go to command prompt by typing this word in menu search
3.Start writing
Code:
cd C:\SDK\platform-tools
adb.exe
You will see
Code:
Android Debug Bridge version 1.0.29
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
Don't freak out everything will be explained
4.Connect device and make sure that USB Debugging is enabled from Settings:Applicationsevelopment(on GB)
Settingseveloper Options(on ICS and HC)
5.Write
Code:
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Device name
6.There are common commands used on ADB:
Code:
adb reboot
adb reboot recovery
adb reboot bootloader
adb push C:\<directory>\file /sdcard/
adb pull /sdcard/file C:\<directory>\
adb install C:\<directory>/file.apk
or /sdcard/<directory>/file.apk
adb remount
Push and Pull means copy form directory to another
ADB Shell for in device commands
Code:
adb shell
#mv /sdcard/file /system/app
#cp /sdcard/file /system/app
#rm /sdcard/file
#mkdir /sdcard/yourfoldernamehere
#ls /sdcard/<directory>
Setting up fastboot: Your phone must be on bootloader
Code:
cd C:\SDK\platform-tools
Commands List:
Code:
fastboot devices – lists which devices in fastboot mode are currently attached to your computer
fastboot boot <filename> – boots a rom stored on your pc specified by the filename
fastboot flash <partition> <filename> – flashes a rom stored on your pc, partition can be one of {boot, recovery, system, userdata}
Example: fastboot flash recovery C:\<directory>\recovery.img
PS: When i wrote <directory> it means like C:\Users\Desktop\Desktop\file
Or you can put the file in the the platform-tools folder you created so
write Ex:
Code:
adb push file.apk /sdcard/
Got stuck with htc logo after the LeeDroid flash on my HTC
Hi All,
Good morning. I am very new with Android, I did the flash rom using Leedroid 4.3.0 I can flash it ok, but it said I use s-off so I need to extract the boot.img from rom.zip and flash it.
I have no idea how to flash it. Can anyone guide me step by step.
I tried the ADB.exe with CMD but no luck, although it say (sending boot <3853 kb> ... okay, writing boot... OKAY, I still cannot get it to work, after reboot, I still got stuck with htc logo.
I am using HTC flyer, HBOOT 6.10.1002
Thank you in advance for your help
you need to flash it when you are in bootloader using fastboot command:
fastboot flash boot boot.img
You are my first teacher......enjoyed it....Thanks a lot...
Incredible s stuck on loading
Hey All,
Here is my story -
Never felt the need of rooting my phone, until one of my relatives, done that for me. If I ever knew, that i will have so many problems, I would have never let him do that.
Moving on, I couldn't find a rom fitting myself, always had bugs, used too much of my battery, or so on. Got tired losing everything, everytime i had to change the rom, after finding a bug i couldn't stand. So, I came back to original rom 2.3.5. Thought i will just update and will have S-off phone with original software.
Somehow it didn't let me update, I stayed with that for few months, then one day i decided i can't stand the old soft, and started working on getting my phone back to s-on and original rom. Used Android flasher to flash this file engHBOOToverARX . The next step was to flash the original rom, via
Android flasher. But i couldn't find it on internet. Therefore i thought it's just gonna be easier and faster that i'll just go and scan for the update.
It found and finally was updating when I was happy i'll get back to normal phone. Unfortunately, It wouldn't load the software anymore, only the white screen with the HTC logo.
Bootloader still says
Revolutionary
Vivo PVT SHIP S-OFF RL
HBOOT - 6.13.1002
RADIO - 3822.10.08.28_M
eMMC - boot
Apr 1 2011, 18:34:39
I tried to follow the steps, on the cmd.
But it looks like it can not find the device.
My phone is connected to the computer via usb cable and on the bootloader menu.
PLEASE HELP ASAP.
I am using my old Nokia 6310i as the backup plan at the moment, and believe me it is not fun at all, uxcept the fact that I make everyone laugh
when I take it from my pocket
Titas
Where to start:
This is not a general help thread
This is not even in the Q&A forum
You have a VIVO which is an incredible s not SAGA (codename for desire s so you're in the wrong forum)
Sywepd form my DsereiS
explanation
"Setting up fastboot: Your phone must be on bootloader "
1st... what do you mean by "Your phone must be on bootloader" & how to do ??
2nd... I accessed this thread from another one concerning nabi II tablet rooting .... but I can't figure out the DIRECT importance to know that ...in regard to rooting the nabi II
.... is it essential ??
3rd.. can u please write the prompt commands in full manner ... as sometimes u use "\" or "/" eg:
"adb install C:\<directory>/file.apk
or /sdcard/<directory>/file.apk "
that's a little bit difficult ..thanks
ayanah said:
"Setting up fastboot: Your phone must be on bootloader "
1st... what do you mean by "Your phone must be on bootloader" & how to do ??
Click to expand...
Click to collapse
If you don't know that then you need to do A LOT of reading before attempting to play around with your device
ayanah said:
2nd... I accessed this thread from another one concerning nabi II tablet rooting .... but I can't figure out the DIRECT importance to know that ...in regard to rooting the nabi II
.... is it essential ??
Click to expand...
Click to collapse
I have no idea how you got here from the Nabi II forum - unless someone there felt that this was a decent guide to also use on the Nabi II
ayanah said:
3rd.. can u please write the prompt commands in full manner ... as sometimes u use "\" or "/" eg:
"adb install C:\<directory>/file.apk
or /sdcard/<directory>/file.apk "
that's a little bit difficult ..thanks
Click to expand...
Click to collapse
The OP is NOT going to rewrite his guide just for you after 6 months. Also, the difference between using '\' and '/' depends on whether you are using Windows or Linux - if you can't work that out then I would also suggest that you leave your device alone before you destroy it.
a reply
SimonTS said:
If you don't know that then you need to do A LOT of reading before attempting to play around with your device
I have no idea how you got here from the Nabi II forum - unless someone there felt that this was a decent guide to also use on the Nabi II
The OP is NOT going to rewrite his guide just for you after 6 months. Also, the difference between using '\' and '/' depends on whether you are using Windows or Linux - if you can't work that out then I would also suggest that you leave your device alone before you destroy it.
Click to expand...
Click to collapse
by the way .. in less than 1 hrs I used his guide to install programs from my PC (& I had no previous knowledge even where to start command prompt) on my old galaxy i5700 (use it for trials) ... I installed the programs using "adb install ....." & every thing is OK ... & I had successfully rooted my galaxy s6102 using another thread (not the one click programs) also every thing is OK ... I'd like to tell you I know about (rooting) less than 2 days ago ... so I think this is a good start for me ..... SO .. it would be appreciated to anyone who could answer me in short just showing little pit details & the pitfalls to avoid ...
also I thought"\" is where I copy from &"/" where I copy to i.e. concerning the direction of the path ... but I wasn't sure so I needed to get that explained
thanks for help but let OP take the decision HIMSELF.
referral thread :http://forum.xda-developers.com/showthread.php?t=1905674
I have been trying to do a factory reset of the Nabi 2, and since I can't seem to access the "Mommy Mode", I thought I could do it from the recovery menu. So far I have yet to find any factor reset option available. Is there such a beast or am I out of luck?
kcallis said:
I have been trying to do a factory reset of the Nabi 2, and since I can't seem to access the "Mommy Mode", I thought I could do it from the recovery menu. So far I have yet to find any factor reset option available. Is there such a beast or am I out of luck?
Click to expand...
Click to collapse
This is not the Nabi 2 forum...
And don't even know what the hell the "Mommy Mode" is, but with the command <adb reboot recovery> should bring you to the recovery.
Sent from my Nexus 7 using xda app-developers app
c.m.b said:
This is not the Nabi 2 forum...
And don't even know what the hell the "Mommy Mode" is, but with the command <adb reboot recovery> should bring you to the recovery.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Actually, was able to get it sorted... I am not sure how I ended up posting on this thread, because I was replying on the Rooting Nabi thread... Weird!
If my USB debugging was off occurred when the soft brick, is there any way to get access via ADB?
My softbrick was caused by a bad file (framework-res.apk).
Is there any way to replace this file?
Nice work mOh19973 :good:
Your guide came in really handy for rooting the Nabi 2 that we got my son for Christmas. He'll be really excited once he sees that the Google play store is now available
Thanks,
Bodie
HELP!!!
mOh19973 said:
Definition:
ADB is the android debugging bridge that allows you to control your phone from your PC and is a bridge allowing you transfer stuff from it
Fastboot is usually used in bootloader and used a lot in unlocking your bootloader and commands in it
Setting up ADB:
1.Download the ZIP file from the attachments and extract it in C:\SDK\platform-tools (You will need to create these folders)
2. Go to command prompt by typing this word in menu search
3.Start writing
Code:
cd C:\SDK\platform-tools
adb.exe
You will see
Code:
Android Debug Bridge version 1.0.29
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
Don't freak out everything will be explained
4.Connect device and make sure that USB Debugging is enabled from Settings:Applicationsevelopment(on GB)
Settingseveloper Options(on ICS and HC)
5.Write
Code:
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Device name
6.There are common commands used on ADB:
Code:
adb reboot
adb reboot recovery
adb reboot bootloader
adb push C:\<directory>\file /sdcard/
adb pull /sdcard/file C:\<directory>\
adb install C:\<directory>/file.apk
or /sdcard/<directory>/file.apk
adb remount
Push and Pull means copy form directory to another
ADB Shell for in device commands
Code:
adb shell
#mv /sdcard/file /system/app
#cp /sdcard/file /system/app
#rm /sdcard/file
#mkdir /sdcard/yourfoldernamehere
#ls /sdcard/<directory>
Setting up fastboot: Your phone must be on bootloader
Code:
cd C:\SDK\platform-tools
Commands List:
Code:
fastboot devices – lists which devices in fastboot mode are currently attached to your computer
fastboot boot <filename> – boots a rom stored on your pc specified by the filename
fastboot flash <partition> <filename> – flashes a rom stored on your pc, partition can be one of {boot, recovery, system, userdata}
Example: fastboot flash recovery C:\<directory>\recovery.img
PS: When i wrote <directory> it means like C:\Users\Desktop\Desktop\file
Or you can put the file in the the platform-tools folder you created so
write Ex:
Code:
adb push file.apk /sdcard/
Click to expand...
Click to collapse
When I go to command and type in adb.exe i get an error. Also when I try to download the file it doesn't let me have the option of saving the file to platform-tools. I have to move it there myself and then I extract the files. I've done this several different times and still keep coming up with same results on the command prompt! Please help!!!! Been working on this for 4 hours!!!
Once in directory you do not type adb.exe. just type
Adb devices
If your Android device is hooked into the USB it should be listed
Flyer
I am having major troubles trying to root my nabi 2 tablet. I tried replying on the actual thread but it wouldnt let me. If anyone can help me out please do. I've tried 2 ways which are pretty much the exact same.
1. download pdanet - install (whilst tablet is plugged in) and chose samsung and it shows up in devices as working fine
2. downloaded platform-tools and made SDK and platform-tools folder. I have the install files as well
3. Run cmd type cd C:\SDK\platform-tools. type adb.exe and it loads in.
4. Run install and chose option 1.
It goes to the option where I choose reboot kernal then it restarts and I get the green android icon with the red triangle with esclamation mark in it.
What am I doing wrong its been doing my head in for 3 days now if anyone can help it would be great. thanks
sweetpea8852 said:
When I go
Click to expand...
Click to collapse
In future, please don't quote the entire OP lie that when there is no need. It makes threads much more difficult to follow.
Klarkus said:
I am having major troubles trying to root my nabi 2 tablet. I tried replying on the actual thread but it wouldnt let me. If anyone can help me out please do. I've tried 2 ways which are pretty much the exact same.
1. download pdanet - install (whilst tablet is plugged in) and chose samsung and it shows up in devices as working fine
2. downloaded platform-tools and made SDK and platform-tools folder. I have the install files as well
3. Run cmd type cd C:\SDK\platform-tools. type adb.exe and it loads in.
4. Run install and chose option 1.
It goes to the option where I choose reboot kernal then it restarts and I get the green android icon with the red triangle with esclamation mark in it.
What am I doing wrong its been doing my head in for 3 days now if anyone can help it would be great. thanks
Click to expand...
Click to collapse
This is the Desire S forum. You may have been directed here, but we don't use Nabi tablets I'm afraid.
Nabi 2
Klarkus said:
I am having major troubles trying to root my nabi 2 tablet. I tried replying on the actual thread but it wouldnt let me. If anyone can help me out please do. I've tried 2 ways which are pretty much the exact same.
1. download pdanet - install (whilst tablet is plugged in) and chose samsung and it shows up in devices as working fine
2. downloaded platform-tools and made SDK and platform-tools folder. I have the install files as well
3. Run cmd type cd C:\SDK\platform-tools. type adb.exe and it loads in.
4. Run install and chose option 1.
It goes to the option where I choose reboot kernal then it restarts and I get the green android icon with the red triangle with esclamation mark in it.
What am I doing wrong its been doing my head in for 3 days now if anyone can help it would be great. thanks
Click to expand...
Click to collapse
Try this link
http://forum.xda-developers.com/showthread.php?t=1905674
i need some help in cammand propt for adb devices please. my problem is when i push enter on putting in adb devices it says emulator-5554 device and then my device underneath, i need to some how turn off the emulator because it will only finish process with one adb device. has anyone asked you about this before? can you help me?
GO HERE AFTER CAREFULLY FOLLOWING THIS PROCEDURE TO INSTALL ROMS, S-OFF, ETC.
delacerda said:
Confirmed! Stock AT&T OneX on 3.18 JB 4.1.1. SuperCID 11111111 , HTC Dev bootloader unlocked, TWRP recovery installed, perm rooted.
Click to expand...
Click to collapse
nhshah7 said:
Got SuperCID and about to unlock after I backup some data.
Thank you so much!
Here is what I did and what worked for me:
Copy oneXchopper, ownage, and busybox files to folder with ADB (this is if you have the android sdk)
Code:
adb push oneXchopper /data/local/tmp/xpwn
adb push busybox /data/local/tmp/busybox
adb push ownage /data/local/tmp/phase1.sh
adb shell chmod 755 /data/local/tmp/xpwn /data/local/tmp/busybox
adb shell
(within ADB shell)
ln -s /data/local/tmp/busybox /data/local/tmp/sed
/data/local/tmp/xpwn
You will see this:
[+] This may take a few minutes.
[+] Success!
2+0 records in
2+0 records out
1024 bytes transferred in 0.001 secs (1024000 bytes/sec)
2+0 records in
2+0 records out
1024 bytes transferred in 0.001 secs (1024000 bytes/sec)
2+0 records in
2+0 records out
1024 bytes transferred in 0.008 secs (128000 bytes/sec)
exit (will exit from shell)
adb reboot bootloader
This will reboot you to the bootloader. If you have the android SDK, you can confirm superCID via the command "fastboot getvar cid".
Next step, hit up HTCdev.com for an unlock code!
Thanks man
Click to expand...
Click to collapse
Root on the ATT 3.18 firmware for HTC One XL and SuperCID. Linux only for now due to laziness.
Here ya go, just extract and run pwn.sh. This automated method is untested, however I have done it manually to my own phone last night.
Just to clarify, this is a temp root which sets your CID to SuperCID allowing a bootloader unlock via HTCDev. It does NOT install Superuser or anything of that sort.
I'm not responsible for bricks, warranty voiding, etc. and please let me know if this works or if I need to tweak some things. It SHOULD handle everything automatically.
Thanks to Dan Rosenberg for Motochopper, which I modified very slightly for use in this script.
Thanks also to the people who paid the bounty. You guys are awesome and probably just bought me something nice. Not sure what yet
One more thanks to Daft Punk for providing some decent music to listen to while I worked on this. I was up all night to get lucky xD
A backup of mmcblk0p4 is made in /sdcard/backup.cid. You can run /data/local/tmp/xpwn manually and restore this backup should things go wrong.
dd if=/sdcard/backup.cid of=/dev/block/mmcblk0p4
This script is sponsored, created, and fueled by absolute hatred of AT&T. Enjoy your HTC Dev unlock!
UPDATE: There is now a Windows auto-pwn script available, thanks to Megadoug13.
You can get it from HERE
I am unable to test or really work with this because I have no Windows box, so contact Megadoug13 if it doesn't work.
The instructions I received with this package are as follows:
Megadoug13 (via email) said:
Just double click "ONLY ONE X" have usb debugging on. and when the phone gets into bootloader it wont tell you that your cid is 11111111. just get your token id and then submit at htcdev. this is only the cid change script. oh make sure to unzip it lol. dont click on anything BUT "ONLY ONE X"
Click to expand...
Click to collapse
myusernam3 said:
Root on the ATT 3.18 firmware for HTC One XL and SuperCID. Linux only for now due to laziness.
Here ya go, just extract and run pwn.sh. This automated method is untested, however I have done it manually to my own phone last night.
I'm not responsible for bricks, warranty voiding, etc. and please let me know if this works or if I need to tweak some things. It SHOULD handle everything automatically.
Thanks to Dan Rosenberg for Motochopper, which I modified very slightly for use in this script.
A backup of mmcblk0p4 is made in /sdcard/backup.cid. You can run /data/local/tmp/pwn manually and restore this backup should things go wrong.
dd if=/sdcard/backup.cid of=/dev/block/mmcblk0p4
This script is sponsored, created, and fueled by absolute hatred of AT&T. Enjoy your HTC Dev unlock!
Click to expand...
Click to collapse
Well well that's sooner than I thought. Good job man. Now to see if other users report success with this.
Sent from Xparent Red using my Venomized Evita
ImagioX1 said:
Well well that's sooner than I thought. Good job man. Now to see if other users report success with this.
Sent from Xparent Red using my Venomized Evita
Click to expand...
Click to collapse
Thank you. As I said, though, I have no clue if the automated method works due to not having a test dummy.
If you need to do it manually, the two scripts "pwn.sh" and "ownage" have everything you need to do in them. Just read them.
myusernam3 said:
Thank you. As I said, though, I have no clue if the automated method works due to not having a test dummy.
If you need to do it manually, the two scripts "pwn.sh" and "ownage" have everything you need to do in them. Just read them.
Click to expand...
Click to collapse
I'll see if I can talk the wife into letting me try it on hers. Awesome job man. Thanks
Sent from my One X using Tapatalk 2
myusernam3 said:
Thank you. As I said, though, I have no clue if the automated method works due to not having a test dummy.
If you need to do it manually, the two scripts "pwn.sh" and "ownage" have everything you need to do in them. Just read them.
Click to expand...
Click to collapse
I'm on hboot 1.09 soff already so no need for me to test. If yall don't mind me making a suggestion I would suggest you pm venomtester and ask him to try your script. He has a riff box and can jtag the phones in case of a brick.
Sent from Xparent Red using my Venomized Evita
ImagioX1 said:
I'm on hboot 1.09 soff already so no need for me to test. If yall don't mind me making a suggestion I would suggest you pm venomtester and ask him to try your script. He has a riff box and can jtag the phones in case of a brick.
Sent from Xparent Red using my Venomized Evita
Click to expand...
Click to collapse
Shot him a PM, we'll see what happens.
Subscribed and will test this once my phone is charged.
Sent from my Transformer Prime TF201 using Tapatalk HD
EDIT: Windows Manual method added from this post
nhshah7 said:
Okay, since people are having issues with the manual methods for Windows, I'm going to recommend installing using the Android SDK. @myusernam3, please remove the code from the OP and the other thread and replace it with a link to this post.
DISCLAIMER: Please read this post 4 times over before you attempt this procedure. It may render your phone unusable (read: a brick) if you don't follow it correctly. I and anyone else associated with this exploit is not responsible for any issues that may arise from this process, such as if you brick your phone. Proceed at your own risk, and with extreme caution. This procedure is not for those who don't want to take the time to read and understand how this works.
Download the android SDK and install it. Once that's done, open the android SDK manager and download platform-tools.
Navigate to C:\Program Files (x86)\Android\android-sdk\platform-tools to make sure adb.exe and fastboot.exe are there.
Download the files in the OP and then copy oneXchopper, ownage, and busybox to the platform-tools folder.
Once the files are moved over, you need to open a command prompt window. In windows explorer open to that folder (platform-tools), hold down the shift button and right click anywhere in the folder (not on a file). Then click Open command prompt window here. You should then see a command prompt window open to the platform tools window.
Plug in your phone and make sure USB debugging is enabled (Settings, developer options - enable this if it asks you, make sure USB debugging is checked). Now back in the command prompt, type "adb devices". It should show you HTCxxxxxxxxxx. That confirms that your phone and adb can see each other. If not, make sure you have the correct drivers installed. You can google around for help with this if you have trouble.
With that, we're ready to start typing in commands!
Type the following commands in one line at a time, minus the stuff in parenthesis. When you get to the first adb shell line, hit enter, then type the following line by line:
chmod 755 /data/local/tmp/xpwn /data/local/tmp/busybox
ln -s /data/local/tmp/busybox /data/local/tmp/sed line
/data/local/tmp/xpwn
You'll see a bunch of lines of code (see below)
Once this is all done, type in "exit", then "adb reboot bootloader" (at the bottom of the code quote)
Code:
adb push oneXchopper /data/local/tmp/xpwn
adb push busybox /data/local/tmp/busybox
adb push ownage /data/local/tmp/phase1.sh
adb shell
(within ADB shell)
chmod 755 /data/local/tmp/xpwn /data/local/tmp/busybox
ln -s /data/local/tmp/busybox /data/local/tmp/sed
/data/local/tmp/xpwn
You will see this:
[+] This may take a few minutes.
[+] Success!
2+0 records in
2+0 records out
1024 bytes transferred in 0.001 secs (1024000 bytes/sec)
2+0 records in
2+0 records out
1024 bytes transferred in 0.001 secs (1024000 bytes/sec)
2+0 records in
2+0 records out
1024 bytes transferred in 0.008 secs (128000 bytes/sec)
exit (will exit from shell)
adb reboot bootloader
You should now be in the bootloader. type in "fastboot getvar cid" and it should show you that your CID is "11111111". If so, it worked! From here, you can follow the instructions here to unlock your bootloader (go to htcdev.com and follow instructions for unlocking a device. in the dropdown device list, select the bottom "other" option).
From there you have to flash TWRP (download link: http://techerrata.com/browse/twrp2/evita - NOTE download 2.3.3.1 because some roms don't flash via TWRP 2.5.0.0). Instructions on how to flash are here (http://techerrata.com/browse/twrp2/evita). you should install via the "Download - Recovery Image Method" - run the fastboot command from the platform-tools folder command prompt above. Your phone should be in bootloader ("adb reboot bootloader" will get you there if you are in android). Copy the downloaded recovery image file to the platform-tools folder, then input the command at the website above (fastboot flash recovery...). Once it flashes successfully, use the up/down volume buttons to select bootloader (on the phone itself), then select recovery via pressing the power button to select. In recovery, make sure you have your rom loaded on your phone first. then go to wipe, and click factory data reset and wipe system. then hit the home button, hit install then install the rom you want. (this is assuming you want to install a rom, not just root.
After unlocking, it will wipe your SD card and you will lose all your sd card data and will have to load a rom to the SD card after unlocking it. it will boot up into the stock rom after you unlock so you can do that here after unlocking and/or flashing TWRP. Alternatively, you can flash SuperSU in recovery to obtain root in the stock rom, then obtain S-Off (see sticky in Developer sub-threads). If you want to use CM or any rom in the Original Android sub-thread, you will have to downgrade your touch-panel firmware. There are stickies in the Original Android Development sub-thread for this.
Good luck!
Click to expand...
Click to collapse
nhshah7 said:
Subscribed and will test this once my phone is charged.
Sent from my Transformer Prime TF201 using Tapatalk HD
Click to expand...
Click to collapse
Best of luck. I'd be happy to take any feedback and if it doesn't work I will resolve it.
If you have TeamViewer or similar we could also walk through doing the whole process manually (5 minutes or so)
I am down to try it here in a few. I'll get my linux machine going tonight and post back.
Sent from my HTC One X using xda app-developers app
Just took a look at the download, do you have a windows script I can use? Or could you provide me with the commands? Thanks!
Sent from my Transformer Prime TF201 using Tapatalk HD
nhshah7 said:
Just took a look at the download, do you have a windows script I can use? Or could you provide me with the commands? Thanks!
Sent from my Transformer Prime TF201 using Tapatalk HD
Click to expand...
Click to collapse
Read the shell script pwn.sh, it has all the commands in it. You can open it in Wordpad (Notepad eats the line endings).
adb push oneXchopper /data/local/tmp/xpwn
adb push busybox /data/local/tmp/busybox
adb push ownage /data/local/tmp/phase1.sh # Yes, it needs to be named this, That's what oneXchopper executes instead of copying su.apk.
adb shell chmod 755 /data/local/tmp/xpwn /data/local/tmp/busybox
adb shell ln -s /data/local/tmp/busybox /data/local/tmp/sed
adb shell "/data/local/tmp/xpwn"
adb reboot bootloader # Your CID should now be 11111111
EDIT: Oh f***, I left out a quotation mark in the script that's run on the phone.
Edit that before you push it! The line starting with "./sed" should be
./sed 's/CWS__001/11111111/' /data/local/tmp/cid > /data/local/tmp/newcid
Good work!
iElvis said:
Good work!
Click to expand...
Click to collapse
Not good work. The .tar.gz that was up a second ago might break stuff. The new one should be fine though.
myusernam3 said:
Not good work. The .tar.gz that was up a second ago might break stuff. The new one should be fine though.
Click to expand...
Click to collapse
I meant finding a way to edit CID.
iElvis said:
I meant finding a way to edit CID.
Click to expand...
Click to collapse
Well, thanks for the compliment. May as well post this cheap, lame way I did it in the thread for people who'd prefer to do it manually.
This is to be run on your HOXL after pushing Busybox and oneXchopper, and obtaining root.
dd if=/dev/block/mmcblk0p4 of=/data/local/tmp/cid
dd if=/dev/block/mmcblk0p4 of=/sdcard/backup.cid
./sed 's/CWS__001/11111111/' /data/local/tmp/cid > /data/local/tmp/newcid
dd if=/data/local/tmp/newcid of=/dev/block/mmcblk0p4
Do I have the balls? Been drinking but hopefully I don't turn the phone into slingshot ammo. Lemme find my laptop.....
-Sugardaddy
Arrow44 said:
Do I have the balls? Been drinking but hopefully I don't turn the phone into slingshot ammo. Lemme find my pc.....
-Sugardaddy
Click to expand...
Click to collapse
I'm not entirely sure what happens if you manage to corrupt mmcblk0p4, but a backup is made during the CID changing process.
If the phone still boots after that, there's still hope.
myusernam3 said:
I'm not entirely sure what happens if you manage to corrupt mmcblk0p4, but a backup is made during the CID changing process.
If the phone still boots after that, there's still hope.
Click to expand...
Click to collapse
If this screws up I am SOL because I just got a refurbished one from AT&T
Arrow44 said:
If this screws up I am SOL because I just got a refurbished one from AT&T
Click to expand...
Click to collapse
If you'd prefer (and if you can trust me with TeamViewer or a similar program) I can try and do it manually, just to make sure nothing goes wrong.
myusernam3 said:
If you'd prefer (and if you can trust me with TeamViewer or a similar program) I can try and do it manually, just to make sure nothing goes wrong.
Click to expand...
Click to collapse
Well Im in Backtrack right now and if what you say is correct all i should do is run the script?
Hello everyone,
I have unlocked my ASUS TF700T and then attempted to TWRP and a custom ROM. Once I did this, I began having issues. It wouldn't boot. I couldn't restore from TWRP backup. I can't seem to write to the system partition for some reason via fastboot but I seem to be able to do this just fine when in CWM or TWRP. Can anyone suggest what I may try from here? I can only get into recovery via VOL DOWN when booting and then selecting the wipe option. Right now I have two major issues. One is that for the life of me, I have never been able to get fastboot to show the actual serial of the device. It has always shown a single question mark. I have gone as far as building a Linux mint box just to get ADP and FASTBOOT drivers to install correctly on a 32-bit machine with USB 2.0. No luck, save result. My second issue is that I am unable to write to the system partition via fastboot. It gives me a remote () error message on fastboot and a could not process the command error in red on my tablet. I will have the exact error message for you shortly but right now I just wanted to get this posted. Any suggestions?
I can't flash the stock blob via fastboot and I can't seem to install a custom ROM via TWRP or CWM. Please advise.
I suspect me not being able to use ADB is my biggest problem. I can't see a serial number when I use fastboot devices. I have tried endlessly to get this resolved and I can't get it to change, AT ALL. I have installed google drivers, 32-bit fresh Linux OS, and plenty of utilities to auto install. No luck. If anyone can help with this, I'd appreciate it.
Here are my issues in a nutshell.
1.) I am unable to boot into recovery directly. I have to go into fastboot and select wipe, it then reboots and starts up in the recovery kernel. TWRP simply executes a command and then restarts and CWM actually boots and allows me to use it.
2.) No matter what I've tried, I have not been able to get the serial number to come up via fastboot. It simply shows a single questionmark. I have tried many solutions for this, but nothing changes.
3.) I am not sure but I believe the bootloader may be the problem. I can currently use fastboot but adb does not recognize the device.
Any assistance would be greatly appreciated. Thank you! I have tried different version of TWRP and clockwork mod but all seem to have the same result. I also attempted to install another custom rom just for good measure and CWM states that
-Tony
Boy oh boy! Mate, your post is one of the most confusing (and confused) posts I have read in a long time. I think you need to go back to the drawing board, forget everything you think you know and start fresh.
Let's clear some of it up:
1) CWM is a recovery (ClockWorkMod), I think you mean your rom is CM (CyanogenMod)
2) When you boot with Volume Down and Power you are booting into the bootloader, you see the bootloader menu and the tablet is in fastboot mode. The bootloader menu consists of 3 icons (if you are on a 4.2 bootloader):
RCK (recovery),
Android (system),
Wipe Data (stay away - it's a small miracle that you are not hard bricked already if you used this)
Are you saying you don't have those three in the BL menu????
RCK should be flashing and pushing Volume Up should boot you into recovery. There is no way to boot directly into it unless your rom has a modified restart menu.
3) adb and fastboot are two different protocols to connect PC and tablet. You use adb when Android is running, you use fastboot when the tablet is in fastboot mode.
Don't know what you tried to get the correct drivers working, but you probably have to go back to square 1 here too. If you use Windows check in Device Manager if your tablet is recognized at all:
Open Device Manager, boot the tablet int the bootloader and connect it via original USB cable to the PC. Do you see any change in Device Manager?
You left out the most important bits:
What bootloader version are you on?
Which version of TWRP?
How did you install TWRP if you don't have fastboot working?
What CM version are you running?
Thanks for the reply. I'll try and be more concise...
Hello,
First of all, I'd like to say thank you. I am all over the place. I will attempt to be more detailed and concise with my wording. Here are my responses below:
berndblb said:
Boy oh boy! Mate, your post is one of the most confusing (and confused) posts I have read in a long time. I think you need to go back to the drawing board, forget everything you think you know and start fresh.
Let's clear some of it up:
1) CWM is a recovery (ClockWorkMod), I think you mean your rom is CM (CyanogenMod)
Click to expand...
Click to collapse
I am familiar with the difference. I have not used nor flashed CyanogenMod. I have indeed installed CWM on recovery and can still do so. I just can't boot into recovery without using the dreded WIPE option on my bootloader. Once I use this, it restarts in CWM and I can use it (still fails to install anything on system though.)
berndblb said:
2) When you boot with Volume Down and Power you are booting into the bootloader, you see the bootloader menu and the tablet is in fastboot mode. The bootloader menu consists of 3 icons (if you are on a 4.2 bootloader):
RCK (recovery),
Android (system),
Wipe Data (stay away - it's a small miracle that you are not hard bricked already if you used this)
Click to expand...
Click to collapse
I have 2 options for my bootloader when I boot into it, fastboot(USB Icon) and wipe (I think we all know this one.) That's it. This is part of the reason why I can't get to recovery mode without using the WIPE option. (I stayed away from the wipe optoin for weeks until I was convince there was nothing else to try. Once I tried this, I was able to boot into recover with CWM or TWRP. TWRP however ONLY runs some sort of script and then reboots again. CWM allows me to use it. Hope this makes sense. Please let me know if I should clarify further.
berndblb said:
Are you saying you don't have those three in the BL menu????
RCK should be flashing and pushing Volume Up should boot you into recovery. There is no way to boot directly into it unless your rom has a modified restart menu.
Click to expand...
Click to collapse
I do not. Since I first installed TWRP, ran a TWRP backup and installed the custom 4.4.2 (I believe) rom I have not seen any other options.
berndblb said:
3) adb and fastboot are two different protocols to connect PC and tablet. You use adb when Android is running, you use fastboot when the tablet is in fastboot mode.
Don't know what you tried to get the correct drivers working, but you probably have to go back to square 1 here too. If you use Windows check in Device Manager if your tablet is recognized at all:
Open Device Manager, boot the tablet int the bootloader and connect it via original USB cable to the PC. Do you see any change in Device Manager?
Click to expand...
Click to collapse
I have gone over multiple times but I am willing to start again. I show ASUS Android Device in Device Manager for Windows 8.1 64-bit. (I have tried flashing many times on Windows 7 32-bit and Linux 32-bit both on USB 2.0. No luck, same issues, same results.
berndblb said:
You left out the most important bits:
What bootloader version are you on?
Which version of TWRP?
How did you install TWRP if you don't have fastboot working?
What CM version are you running?
Click to expand...
Click to collapse
I have no clue how to check the bootloader version without getting into Android. My bootloader doesn't seem to show it on the upper left hand side. Do you know how I can get it?
I have tried TWRP 3.2.1.0, TWRP 2.6.3.2, CWM 6.0.4.7 and Phil's CWM based recovery for the TF700. So far, none have been able to flash a custom ROM again nor the stock rom when I use recovery GUI for them. Please advise.
Also, it seems I am able to write to any partition with fastboot except for system. When I write to the system partition my tablet shows red text on the screen that states "the command flash:system failed 0x170003 or something similar. Fastboot shows a failed: (remote() error after trying to write to the partition. Someone told me my boot loader was the problem, but I have no idea how to change it without using the 'staging' or 'flash system commands.'
I'm not sure if this matters but I thought I'd post it. When I run fastboot -w it fails saying that the file system is not supported. When I run fastboot erase userdata or cache. It seems to work without any issues. Here is a sample of the output I get:
Code:
c:\adb>fastboot erase userdata
erasing 'userdata'...
OKAY [ 10.093s]
finished. total time: 10.093s
c:\adb>erase cache
Could Not Find c:\adb\cache
c:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 1.980s]
finished. total time: 1.980s
c:\adb>fastboot -w
erasing 'userdata'...
OKAY [ 10.031s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.001s]
erasing 'cache'...
OKAY [ 1.972s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.001s]
finished. total time: 12.006s
c:\adb>
When I try to use fastboot to flash the stock firmware using the staging command, I get this on my command prompt:
Code:
c:\adb>fastboot -w flash staging blob
sending 'staging' (800927 KB)...
OKAY [139.757s]
writing 'staging'...
FAILED (remote: ()
finished. total time: 140.900s
c:\adb>
on my tablet it reads in red text failed to process command flash:staging error 0x170003. I have to do a cold boot to get it back up to fastboot mode.
-Tony
qzmicro said:
Hello,
When I try to use fastboot to flash the stock firmware using the staging command, I get this on my command prompt:
Code:
c:\adb>fastboot -w flash staging blob
sending 'staging' (800927 KB)...
OKAY [139.757s]
writing 'staging'...
FAILED (remote: ()
finished. total time: 140.900s
c:\adb>
on my tablet it reads in red text failed to process command flash:staging error 0x170003. I have to do a cold boot to get it back up to fastboot mode.
-Tony
Click to expand...
Click to collapse
Tony try this instead:
Code:
fastboot -i 0x0B05 flash system blob
I have tried it with -i 0x0B05 but it never has different results
sbdags said:
Tony try this instead:
Code:
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
Exact same results:
Code:
c:\adb>fastboot -i 0x0B05 flash system blob
sending 'system' (800927 KB)...
OKAY [141.843s]
writing 'system'...
FAILED (remote: ()
finished. total time: 143.016s
c:\adb>
Thanks for the advise though.
-Tony
qzmicro said:
I have 2 options for my bootloader when I boot into it, fastboot(USB Icon) and wipe (I think we all know this one.) That's it.
I have no clue how to check the bootloader version without getting into Android. My bootloader doesn't seem to show it on the upper left hand side. Do you know how I can get it?
Click to expand...
Click to collapse
What does your bootloader show? Can you post a photo?
qzmicro said:
I have tried TWRP 3.2.1.0, TWRP 2.6.3.2, CWM 6.0.4.7 and Phil's CWM based recovery for the TF700. So far, none have been able to flash a custom ROM again nor the stock rom when I use recovery GUI for them.
Click to expand...
Click to collapse
So you can still flash different recoveries via fastboot and enter them from the bootloader. That means you should also be able to use "adb shell" to connect to your recovery (when it is running). What does the recovery do when you try to flash a ROM?
If adb shell to your recovery works, exit it again and run these commands to assess your situation:
adb shell ls -l /dev/block > devblock.txt
adb shell dmesg > dmesg.txt
adb shell hexdump -C /dev/block/mmcblk0p3 -n 64 > mmcblk0p3.txt
and post the resulting files.
Tony - consider yourself lucky since you caught the attention of two of the best people in this business. Do try to get the info _that was asking for.
I am just trying to clarify things:
Do you remember what stock rom you had before you started this adventure?
It sounds as if you were on pre-JB 4.2 stock rom, then flashed some TWRP version and then a KitKat rom?
If you can flash recoveries, you do have fastboot access to the tablet.
@_that, @sbdags Would it be an option for Tony to flash a CWM recovery that "let him use it" and try to flash sbdags' bootloader/TWRP package?
Tony - don't do anything before you get their advice.
OS
Tony I see that your using a windows PC.. I would highly recommend a Linux Mint OS... There are to many bugs in windows when you are working with low level Android/SoC platforms .... Im not going to say it will fix your issues, but I have seen it do just that for lots of users.... Just let me know if this sound like something for you, when and if your ready, the community with be here to help you out....As always thx lj
I am getting my Linux mint 32-bit OS on my laptop with USB 2.0... again.
Hi guys,
I thank you deeply for your time. I have learned so much trying to un-brick this thing, and yet have had no results. I will be putting together my mint box in just an hour or so and then testing/trying your suggestions. Please check back in an hour or two. Cheers.
-Tony
Here is what my bootloader looks like.
_that said:
What does your bootloader show? Can you post a photo?
Click to expand...
Click to collapse
I have attached the screenshot below.
_that said:
So you can still flash different recoveries via fastboot and enter them from the bootloader. That means you should also be able to use "adb shell" to connect to your recovery (when it is running). What does the recovery do when you try to flash a ROM?
Click to expand...
Click to collapse
It usually fails when it tries to write to the system partition. Please refer to the posts above. It tends to show the FAILED (Remote() error after the write command. My tablet also shows an error saying it could not process the command.
_that said:
If adb shell to your recovery works, exit it again and run these commands to assess your situation:
adb shell ls -l /dev/block > devblock.txt
adb shell dmesg > dmesg.txt
adb shell hexdump -C /dev/block/mmcblk0p3 -n 64 > mmcblk0p3.txt
and post the resulting files.
Click to expand...
Click to collapse
Giving it a try now, I'll let you known what happens.
-Tony
I do not recall. At the time I knew, but not anymore.
berndblb said:
Tony - consider yourself lucky since you caught the attention of two of the best people in this business. Do try to get the info _that was asking for.
I am just trying to clarify things:
Do you remember what stock rom you had before you started this adventure?
It sounds as if you were on pre-JB 4.2 stock rom, then flashed some TWRP version and then a KitKat rom?
If you can flash recoveries, you do have fastboot access to the tablet.
@_that, @sbdags Would it be an option for Tony to flash a CWM recovery that "let him use it" and try to flash sbdags' bootloader/TWRP package?
Tony - don't do anything before you get their advice.
Click to expand...
Click to collapse
I do not recall the stock ROM but I DO KNOW I updated to the latest firmware right after I opened it (Big mistake I know... now.) So, I had no choice but to factory unlcok it with the ASUS TOOL. This was for X-Mas two months ago, so I should be the latest I'd immagine.
I did indeed install a kit kat rom on my first attempt and someone told me I forgot to put the proper bootloader prior and that is why I bricked it. So, I think you are dead on about that but can't confirm.
I do indeed... only problem is that I always get a damn ? for my serial number. I do not believe it has ever shown anything but.... though I didn't check until after I had this problem. I do not recall checking prior to using TWRP to install the kit kat rom zip files.
I will wait. i am very greatful to have help, especially from the top dawgs. xP Cheers!
-Tony
I'm on mint 32-bit OS.
lj50036 said:
Tony I see that your using a windows PC.. I would highly recommend a Linux Mint OS... There are to many bugs in windows when you are working with low level Android/SoC platforms .... Im not going to say it will fix your issues, but I have seen it do just that for lots of users.... Just let me know if this sound like something for you, when and if your ready, the community with be here to help you out....As always thx lj
Click to expand...
Click to collapse
I'm on it. I installed mint on my laptop and am using a USB 2.0 interface. I am willing and able to try whatever you might suggest. Cheers.
-Tony
I get a permissions error when using adb shell in CWM recovery...
_that said:
If adb shell to your recovery works, exit it again and run these commands to assess your situation:
adb shell ls -l /dev/block > devblock.txt
adb shell dmesg > dmesg.txt
adb shell hexdump -C /dev/block/mmcblk0p3 -n 64 > mmcblk0p3.txt
and post the resulting files.
Click to expand...
Click to collapse
After the first command I received:
Code:
Tonys-Mint antonio # adb shell ls -l /dev/block > devblock.txt
error: insufficient permissions for device
This is the error I get when running the first command you asked for _that. Please advise, thank you! Is this something we can fix? Thanks.
Code:
Tonys-Mint antonio # adb shell ls -l /dev/block > devblock.txt
error: insufficient permissions for device
Tonys-Mint antonio # adb shell dmesg > dmesg.txt
error: insufficient permissions for device
Tonys-Mint antonio # adb shell hexdump -C /dev/block/mmcblk0p3 -n 64 > mmcblk0p3.txt
error: insufficient permissions for device
Tonys-Mint antonio #
They all basically told me I have no permissions to my device. Any thoughts? If anyone can/wants to assist outside these forums, please just let me know. I can't offer to pay but I can offer a free pizza at your house no matter where you live! LOL. Cheers fellas!
-Tony
qzmicro said:
I do not recall the stock ROM but I DO KNOW I updated to the latest firmware right after I opened it
Click to expand...
Click to collapse
Your photos show a 9.4.5.x bootloader (and I'm 100% sure about this), which is strange because normally the bootloader is updated together with the stock firmware - so if you updated to the latest firmware, you should also have the latest bootloader (10.6.1.14.x).
qzmicro said:
After the first command I received:
Code:
Tonys-Mint antonio # adb shell ls -l /dev/block > devblock.txt
error: insufficient permissions for device
This is the error I get when running the first command you asked for _that. Please advise, thank you! Is this something we can fix? Thanks.
Click to expand...
Click to collapse
What did the tablet screen show while you ran these commands? The recovery's menu? Which recovery (and version) do you currently have installed?
_that said:
Your photos show a 9.4.5.x bootloader (and I'm 100% sure about this), which is strange because normally the bootloader is updated together with the stock firmware - so if you updated to the latest firmware, you should also have the latest bootloader (10.6.1.14.x).
What did the tablet screen show while you ran these commands? The recovery's menu? Which recovery (and version) do you currently have installed?
Click to expand...
Click to collapse
It just sits there on the main screen as if nothing has happened. Here is a screenie...
-Tony
qzmicro said:
It just sits there on the main screen as if nothing has happened. Here is a screenie...
Click to expand...
Click to collapse
hmm... ok. Try running these commands:
Code:
adb kill-server
adb devices
and post the output.
For the first time EVER, I see the serial number!
_that said:
hmm... ok. Try running these commands:
Code:
adb kill-server
adb devices
and post the output.
Click to expand...
Click to collapse
Here is the output:
Code:
Tonys-Mint antonio # adb kill-server
Tonys-Mint antonio # adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
015d2a50692c0a08 recovery
Tonys-Mint antonio #
Please note that this is the first time the device has EVER shown it's serial number since this all started. Usually it just shows a single question mark. Good sign?! Please advise.
-Tony :fingers-crossed:
qzmicro said:
Here is the output:
Code:
Tonys-Mint antonio # adb kill-server
Tonys-Mint antonio # adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
015d2a50692c0a08 recovery
Tonys-Mint antonio #
Click to expand...
Click to collapse
That looks good so far. Try
Code:
adb shell
and see if you get a shell prompt from the tablet. If you do, type "exit" to get out again, then run the 3 commands I posted earlier.
_that said:
That looks good so far. Try
Code:
adb shell
and see if you get a shell prompt from the tablet. If you do, type "exit" to get out again, then run the 3 commands I posted earlier.
Click to expand...
Click to collapse
Hello, this is what I get...
Code:
Tonys-Mint antonio # adb shell
~ # adb shell ls -l /dev/block > devblock.txt
/sbin/sh: adb: not found
~ # adb shell dmesg > dmesg.txt
/sbin/sh: adb: not found
~ # adb shell hexdump -C /dev/block/mmcblk0p3 -n 64 > mmcblk0p3.txt
/sbin/sh: adb: not found
~ #
I am getting excited, I had not made any leway in over 4 weeks. Those commands seem to have failed though. I kindly await your response. Cheers.
-Tony :cyclops:
qzmicro said:
I am getting excited, I had not made any leway in over 4 weeks. Those commands seem to have failed though. I kindly await your response. Cheers.
Click to expand...
Click to collapse
You forgot to type "exit". But adb shell is working now, that is good. Type "exit" now, then run the 3 commands again, then post the 3 resulting files.