Use my new RegawMOD Hero Rooter HERE
If you do not see the Superuser Permissions app in the app tray after running the exploit, on your phone, go to
Settings > About Phone > Software information
If it says 2.27.651.6 under "Build Number" (notice the bolded, underlined, italic 6), you need to run the RUU in the second post of this thread to revert to .5 first. Doing this WILL erase all of your data on your phone, so be sure to back up anything if you need to first.
It's been a long search for root, but it has finally been achieved!
The Hero 2.1 exploit is based on the EVO rooting method.
The EVO rooting could not have been possible without the combined efforts of:
Matt Mastracci
ozzeh
Joshua Wise
They are all AMAZING and should be thanked for all they have done.
Thank you to Amon_RA for the recovery.img (1.5.2) and Jus10o for packing up a boot.img for me last night when I needed it quick.
Over the past week, Matt and I worked hard applying this exploit to gain permanent root on the Hero.
I now have permanent root access on 2.1 down to a few simple steps that are detailed in this guide.
Also, I'd like to thank everyone that worked really hard on trying to find root here in the Hero community, and specifically all of those who contacted me and worked together with me trying to gain root:
abcdfv
imleon
thatguythatdid
navalynt
nfinitefx45
lifetrip718
rejectedkid
nebenezer (for being cool)
These guys worked incredibly hard with me and had extremely innovative ideas. They deserve a ton of credit for sticking with it as well trying to find . They were all in this for all the Hero users.
If I forgot your name, please let me know via pm so I can add you to the list.
As of right now, this guide is for windows only. Soon to come, OSX & Linux.
HOW TO ROOT SPRINT'S 2.27.651.5 RELEASE FOR THE CDMA HERO (Stock Android 2.1)
Make sure your phone is unplugged from your computer until I tell you to plug it in!
If you already have the Android SDK and HTC Sync set up on your computer, skip to Step 4 now
Step 1: Download the Android SDK here
Step 2: Extract the Android SDK zip. Move the contents of the extracted zip to C:\
Your Android tools folder path should now be C:\android-sdk-windows\tools
Step 3: Download HTC Sync 2.0.33 here
Run the installer, and reboot your computer when it is finished. Move on to step 4 once rebooted.
Step 4: Download the hero-root.zip. This zip contains everything you need to root your Hero.
(md5: c6e5058ed14f71c68fb099e10be142fb)
Step 5: Extract the 3 files inside hero-root.zip to the C:\android-sdk-windows\tools folder on your computer.
Step 6: Make sure USB Debugging is ON (checked) on your Hero. Go to Settings > Applications > Development > and make sure it is checked.
Step 7: Plug your phone into the computer via USB, Make sure that the connection type in the Notification Pull-Down Bar is "Charge Only", not "Disk Drive" or else this won't work.
If your computer asks you to restart after the new drivers were installed, do that now.
Step 8: Open a Command Prompt window by clicking the Start button and typing cmd into the search box and pressing enter.
It is also found under Start Menu > All Programs > Accessories > Command Prompt
Step 9: You will now enter the commands that I have put in code boxes followed by pressing ENTER, one code at a time.
You may also copy/paste these commands in to the Command Prompt, pressing ENTER after each, one at a time.
Comments will be outside of the code boxes (do NOT type these into the Command Prompt as they just are to help describe the root process)1:
Code:
cd C:\android-sdk-windows\tools
You should now see C:\android-sdk-windows\tools>
Now type2:
Code:
adb devices
If you've been following this guide you will see your phone's serial number. If you get "device not found" error, you either need to make sure you the drivers were properly installed or make sure you enable USB debugging on your phone. Continue on once you get the proper phone serial output.
You will now push the files needed to gain root to your sdcard in your phone with these following commands:3:
Code:
adb push unrevoked /sdcard
4:
Code:
adb push recovery.img /sdcard
5:
Code:
adb push boot-patched.zip /sdcard
Now we run the exploit. Be patient, this may take up to 40 seconds.6.
Code:
adb shell
(You should now see $)​7.
Code:
sh /sdcard/unrevoked
You should now see output that says this:
Code:
$ sh /sdcard/unrevoked
sh /sdcard/unrevoked
Unpacking, please wait...
88 88 88b 88 88""Yb 888888 88 dP dP"Yb 88 dP 888888 8888b.
88 88 88Yb88 88__dP 88__ 88dP dP Yb 88odP 88__ 8I Yb
Y8 8P 88 Y88 88"Yb 88"" 8dP Yb dP 88"Yb 88"" 8I dY
`YbodP' 88 Y8 88 Yb 888888 YP YbodP 88 Yb 888888 8888Y
==================================================================
unrEVOked: root for HTC evo and hero (http://unrevoked.com)
#
-----------------
Now, on your phone, go to your app tray, and you will see that the Superuser Permissions app is in it.
Open the Superuser Permissions app. You will see a blank screen.
If you do not see the Superuser Permissions app in the app tray, go to
Settings > About Phone > Software information
If it says 2.27.651.6 under "Build Number" (notice the bolded, underlined, italic 6), you need to run the RUU in the second post of this thread to revert to .5 first and run this guide again. Doing this WILL erase all of your data on your phone, so be sure to back up anything if you need to first.
-----------------
In the Command Prompt on your computer, type:8.
Code:
su
A prompt will appear on your Hero asking you to give /system/bin/sh privileges. Click Allow.
Go back to your command prompt, and you should see
Code:
$ su
su
#
Now type:9.
Code:
flash_image recovery /sdcard/recovery.img
Flashing the recovery may take many seconds to complete. Wait until the # symbol returns to proceed.
You should now see
# flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
#
This means it was a successful flash.
Now type10.
Code:
reboot recovery
Your phone will now boot to the custom recovery image you just flashed.
If that doesn't work, (ie you get errors or it stays at the white/green HTC screen) try using this recovery image, put it on your sdcard, and try code #9 again.
In the Recovery Menu on your phone, choose the option:
Code:
Flash zip from sdcard
Then select
Code:
boot-patched.zip
and press the Home button to apply.
Once Recovery says "Install from sdcard complete", you need to make a nandroid backup!
In the main menu or the Recovery Screen, you will see an option that says
Code:
Backup/Restore
Choose that option, and then choose the option
Code:
Nand backup
This can take up to 5 minutes, so be patient while you see the
Code:
............
Once done, a nandroid backup of your phone will be created and saved to your sdcard in the folder directory:
Code:
/sdcard/nandroid/(your serial number)/
When it is complete, hit the back button to return to the Main menu, and hit "Reboot system now" from the menu to reboot normally!
DISABLE OTA UPDATES!!!!
To disable OTA updates that will patch this exploit, (after rooting and booted after creating a nandroid backup) run the following commands from Command Prompt.
Code:
cd C:\android-sdk-windows\tools
Code:
adb remount
Code:
adb shell
Code:
mv /system/etc/security/otacerts.zip /system/etc/security/otacerts.zip.bak
After doing this, the OTA updates WILL still download, BUT they will not pass signature checks to flash because of the code you just entered.
You now have full root access on 2.1!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The RUU that was updated on HTC and Sprint's Websites was in fact the patch to this exploit. I am posting a few VERIFIED copies of the 2.27.651.5 RUU's that are from the original release date, and have not been patched. Use these to revert back to .5 before rooting.
My Personal One I used for testing
nfinitefx45
More mirrors to come after verification from me.
HAHAHA
I knew if anyone could do it it would be Regaw
Way to go bro
regaw_leinad said:
Coming at 9pm PST
Click to expand...
Click to collapse
regaw_leinad said:
reserveddd
Click to expand...
Click to collapse
congrats dood.
regaw_leinad said:
Coming at 9pm PST
Click to expand...
Click to collapse
Nice thank you
Good job guys.
Coming at 9pm PST
Click to expand...
Click to collapse
Very good job....
-------------------------------------
Sent via the XDA Tapatalk App
great man, regaw!
awesome.....as a coder, this puts you right up there with Toast. obviously that's saying a lot. congrats!
You like to me?
Not cool bro.
Great job to all involved. Hope to keep some of ya around after the EVO.
regaw_leinad said:
Coming at 9pm PST
Click to expand...
Click to collapse
Thank you for your hard work.......
Congratulations. Damn we've got a talent pool here in the Sprint Hero section!
you are the man
Good job bro! I was wondering if it was even possible for a second there. Nice to see your back rooted too.
I'm impressed. Great job man , I was smart enough not to upgrade though (lol jk!). I should of tried to root 2.1, but I was way too busy; I guess I'll try when 2.2 comes around.
JsChiSurf said:
Congratulations. Damn we've got a talent pool here in the Sprint Hero section!
Click to expand...
Click to collapse
Yes we do! I'm just hoping not all of this talent is jumping ship to the Evo in the next 10 or so hours.
Congratulations to Daniel and all the others who helped him root the cursed official 2.1! Thanks for all your hard work.
I really hope htc will release the new 2.1 kernel source code soon after regaw release the root method, haha. Great job regaw!
Ausgezeichnet!!!
regaw_leinad said:
Coming at 9pm PST
Click to expand...
Click to collapse
Half an hour left!!!!
Imma finish watching the laker game..
I had faith in you Regaw.
i caught you asking question in the General section of Xda not the CDMA Hero Section
and i was like ohhh hes dedicated lmao.
Related
Why should you root your Dream/G1?
You can install a full Linux distribution, like Debian.
You can run applications that require root, like Screenshot and Auto Rotate your Browser and or any other application.
You can install the latest Android build directly from the Android source tree.
Customize your boot image.
Create full backups of the state of your phone.
Create custom ROMs.
Install Applications to your SD Card to save space.
Use your phone as a tether to connect your computer/laptop to the internet.
Turn your phone into a wireless router that provides internet access.
Well, hopefully one of those reasons convinced you to get root access on your phone!
Preparing to Get Root on your Phone
Getting root on your phone involves exploiting a security hole that existed in an early version of Android. The versions with the security holes are known as RC19, RC28, and RC29 (or RC7 or lower for UK phones). As of RC30 (RC8 on UK), Google patched the security hole so that your phone can not be rooted (don't worry, we can still root it!).
To check your version, go to the Home Screen, click your menu button, choose "Settings", and then click "About phone". You will then see the following screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you have US-RC30/UK-RC8 or higher, you will first need to downgrade your phone to a previous version. (Skip these steps otherwise)
Format your phone's SD card to FAT32 mode:
Hook your phone up to your computer using a USB cable and then wait for the notification to show up in your title bar of your phone.
Click the notification, and then click "Mount".
A new removable disk should show up on your computer. Right click it and select Format, and select FAT32 as the file system type.
Download and unzip the RC29 or RC7 image file. Copy the DREAIMG.nbh file to the SD card. (RC29 for US, RC7 is for UK)
Turn the device power off.
Hold Camera button, and press Power button to entry boot loader mode. You should see a gray/white screen with instructions to flash your phone with the update on your SD card. If you don't see that, make sure you followed the instructions properly.
As per the on-screen instructions, press the Power button to start upgrade procedure. DO NOT DO ANYTHING TO INTERRUPT THIS PROCESS.
After it is finished, perform the restart your phone.
Rooting your RC29 or lower phone:
On RC29 phones and lower, anything you type into your keyboard is also being run in a hidden console with root permissions. More information regarding that at the bottom of this post. But, to get root access, do the following:
Instructions:
Download recovery.img or the new version by Amon recovery-RA-dream-v1.5.2.img and copy it to your SD card (see the previous instructions on how to copy from your computer to your Phone's SD card).
Download the Hard SPL and copy the zip file to the SD card.
All files must be on the root of your SD card.
Restart your phone. Wait for your phone to start up fully and show the home screen.
After your phone starts up, hit the enter key twice, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
Download an Android "Telnet" application from the Market and connect to localhost.
If you connect successfully, you will have a root prompt "#".
Type the following into Telnet (these commands will give you root access easier in the future):
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img
Now you have root!
What To Do Now That You Have Root
Now that you have root, you will want to apply "Hard SPL" to your phone. HardSPL is what will allow you to apply flash images from other regions (like UK on US phones, and vice versa), create full backups of your phone, install the latest build from the Android source, and usually resurrect your phone if it is "bricked". You have already downloaded the file to your SD card, so now you can apply it.
Power off your phone.
Start up in recovery mode by holding home and pressing power.
You will now enter recovery mode. You should see an exclamation.
If you do not see a menu on screen, press Alt-L to show the menu.
Press Alt-S to apply the update from the SD card.
After the update is complete, hold Home and press Back to restart.
And now, the last step! You are still running an old version of Android, but you want to upgrade to the latest and greatest update! You can do this, and not lose root by downloading modified versions of the updates.
First, choose a modified image from the list below:
ADP1.1: (md5: bacc58302e0b239d66c7bcc8db6c434b)
http://jf.odiness.com/v1.41/JFv1.41_ADP1.1_BuildEnvironment.tar.gz
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://andblogs.net/2009/01/jesusfrekes-14-images-are-out/
RC33: (md5: f24b6c237775147cb4bc42efc2393973)
http://jf.odiness.com/v1.41/JFv1.41_RC33_BuildEnvironment.tar.gz
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://andblogs.net/2009/02/new-rc33-based-images-from-jesusfreke/
RC8: (md5: de2d0d34adbb4015ee3aa5e4e7ca3c07)
http://jf.odiness.com/v1.41/JFv1.41_RC8_BuildEnvironment.tar.gz
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://andblogs.net/2009/01/jesusfrekes-14-images-are-out/
Download the image.
Rename it to update.zip.
Copy it to your phone's SD card.
Turn your phone off.
Start up in recovery mode by holding Home and pressing Power.
Press alt-W to wipe your device. (You need to do this, or the device may hang at the flashing Android screen)
Press alt-S to apply the update.
And that's it! Remember to check the links up top to learn how to use root to do the advanced things I mentioned.
Rooting, Hacking, and Flashing your G1/Dream
Reserved for future posting
Wow this is great news keep the community updated. thanks man
EDIT:i just tested it my self!! your right this seems like root to me
Koush said:
I verified this by remounting the /system partition as read write and changing files around.
Click to expand...
Click to collapse
How did you do that?
Wow, good job!
I classify this as a major "oops" on Google's part...
humble said:
How did you do that?
Click to expand...
Click to collapse
mount -oremount,rw /dev/block/mtdblock3 /system
You can't remount that directory that unless you have root.
Use the dd command to copy stuff around (the cp command is not available). I should mention I'm a Windows guy, and am pretty clueless with Linux: my coworker figured the rest of this out once I got to a root prompt.
Incidentally, in the /system/bin directory there is a flash_image executable that changes the recovery.img used when you hard reset the device. I've noticed that I can run this without root access from a standard adb shell. Maybe we never needed to root the device after all... I think we can flash it without root access... I'm too scared to mess with that at all though.
i just rebooted from telnet!!! i must say this is cool
thanks dude I'm going to give it a run(not flashing) I'm scared too 428 and some change down the draine nooo
Yes!!! Now we dont even have to worry about the update.zip file!
Well, it still will be usefull for package updates.
I'm goin for the bootloader and pretty soon we'll be able to port Android to other HTC devices aswell.
Maybe this can be usefull its kind of old buthttp://benno.id.au/blog/2007/11/13/android-under-the-hood
well
i don't konw how safe it is but you can just chmod 777 files and access them through the glance file manager. can't open but you can copy and past them on the sd card and open from there. i wish i could figure out how to see them
i keep getting "Error running telnet: permission denied" in LogCat. any ideas ? i have rc29
hrm
i'm now getting Unable to chmod *******: Read-only file system across the board /////////////////nm i'm retarded
Koush said:
mount -oremount,rw /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
If you want to edit anything, you have to remount it as read/write.
yeah i forgot i rebooted my phone, lol just trying to see if i can figure out how to change the view when you mount the sd card to show all files.
anyone with RC29 getting root access ?
yeah i am
not that i know what to do with it
can u describe the steps ? i keep getting Permission denied
anyone know where the boot code is so I can tell it to mount all folders as read write at boot?
quedijo said:
Yes!!! Now we dont even have to worry about the update.zip file!
Well, it still will be usefull for package updates.
I'm goin for the bootloader and pretty soon we'll be able to port Android to other HTC devices aswell.
Click to expand...
Click to collapse
Good news!
Hope someone can develop something for Universal!
Cheers to all,
neerhaj said:
can u describe the steps ? i keep getting Permission denied
Click to expand...
Click to collapse
http://android-dls.com/forum/index.php?f=15&t=151&rb_v=viewtopic
All the steps are laid out there. pterminal downloadable and all.
WOW AFTER AGES>>>>>>> FINALLY!!!! YAY!!!
First i would like to thank every one who made this possible , im sorry i dont know ur names..
This is what i did i dont know if itll work for every one but fingers crossed....
1. its like the normal rooting procedure except with the boot.img that i have!!! U need the sdk for this to work!!
2. Download superhero rom v2: http://www.megaupload.com/?d=3Y02RZAT
3. rename as update.zip and place on sdcard.
4. Shutdown phone.
5. Download: http://rapidshare.com/files/248983573/recovery-RAv1.0H.img
6. place this img in the tools folder of the sdk.
7. Start phone in fastboot mode (power+voulme)
8. from the fastboot menu in cmd restart phone with the boot image provided above. (c:\sdk\tools fastboot boot recovery-RAv1.0H.img).
UPDATE:: DO A NANDROID BACKUP THEN USE THE BOOT.IMG THAT WAS BACKED UP BY NANDROID (ON YOUR SD CARD) FOR STEP NUMBER 12/13/14..
9. wipe data and update .
10. reset phone but remove battery when the rogers sign comes on.
11. go to flashboot mode again.
12. .......... use backed up boot.img
13. place this in the tools directory of the sdk
14. in cmd again flash the boot image (c:\sdk\tools fastboot flash boot boot.img)
15. Now reboot and thats it ur done!!!!
NO WIFI!!!! NO BLUETOOTH IN THE SUPER HERO ROM AM TRYING OTHER ROMS... I THINK THIS METHORD SHOULD WORK AN ALL ROMS NOW... maybe not....
after trying for a while only superhero works not the hero by haykuro... dunno why it keeps restarting at the htc splash screen....
waiting nice
Thanks for using my recovery! lol
reply: like i said in the begenning thnx to all tht helped....
ps the daldroid should work as well
good job man, very interested in this but gotta wait till wifi works.
i think wifi dosent work becase superhero was for dream not magic... but the ui is sweet!
can someone help to enable wifi and bluetooth??
Oh wow, thanks. I will shortly follow your instructions.
lol to fix wifi find out whos boot.img you stole rolleyes and take the wlan.ko from /system/lib/modules and throw it over the one in the build.
sign, package, fly.
EDIT:
also, in default.prop (within the boot.img) change it ro.secure to 0 if you want rooted adb shell
Code:
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
heh.. this is why sometimes you should wait before just throwing an incomplete build out
haykuro said:
lol to fix wifi find out whos boot.img you stole rolleyes and take the wlan.ko from /system/lib/modules and throw it over the one in the build.
sign, package, fly.
EDIT:
also, in default.prop (within the boot.img) change it ro.secure to 0 if you want rooted adb shell
Code:
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
heh.. this is why sometimes you should wait before just throwing an incomplete build out
Click to expand...
Click to collapse
That is exactly why I am waiting for a proper release to come out.......hint
LOL
it was the boot image i backed up myself... so what do i do exactly??? I kinda got the first part, used adb pull and push to copy over the file, but the edit just flew way oover my head.....
ps haykuro can you use this to make a biuld?? alsoo can u pls show me how to sign a package searched everywhere couldnt find out how...
re: TRIED THE wlan.ko file transfer still it says failed to start wlan!!!
Killadude said:
reply: like i said in the begenning thnx to all tht helped....
ps the daldroid should work as well
Click to expand...
Click to collapse
Yes, it works. Since June 8th ;-)
But daldroid-recovery is really a quick-mod of haykuro's one, so thank him (and others, I only mentioned him and a few others in a readme file in the ramdisk image)
I'm happy to see that someone else started releasing roms for pvt 32A board, because I was really busy and used all of my sparetime to try to rebuild a working kernel (Hero is running on my phone since 3 weeks, untested-bluetooth-fix, wlan fix, but still no working kernel, no iptables, so no release).
Going abroad for a few days, I'm sure I'll come back and be able to download your (or Haykuro's) new rom with a new built-from-sources-working-kernel for pvt32A ;-)
Greetings
Daldroid
Killadude said:
it was the boot image i backed up myself... so what do i do exactly??? I kinda got the first part but the edit just flew way oover my head.....
ps haykuro can you use this to make a biuld??
Click to expand...
Click to collapse
Im pretty sure he has
http://www.getyourdroidon.com/root/hero-sapphire-signed.zip
or did you mean a rogers specific one?
- Wifi and BT cannot start in this rom
yup one specific for rogers cuz our is the only goddam magic that couldnt until today be rooted!!
I just followed your instructions for the superherov2 rom and I ran into some problems.
I cannot upload the boot.img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now my phone is stuck with the Rogers logo. Any ideas on how about I can go on fixing this problem.
First u could try in fastboot mode re booting to the recovery img boot..... once in there wait for a minute, connect usb to computer and in cmd go to tools folder and type
adb devices, if u see a serial underneath then type
adb push boot.img /data/local/boot.img
with the image you downloaded if this fails then, ill redriect u to a link Thanks to daldroid itll help you run the origanal magic rom, without the rogers crap installed on it. Just not you have to set the api settings in the menu to:
name: rogers
address: internet.com
to acess the rogers edge/3g internet.
http://www.arbitraryuser.com/blog/2...-south-africa-to-get-android-market-and-more/
just skip to instruction number 8 in the step by step instructions
PS IF U DID DO A NANDROID BACKUP JUST PLACE THE BOOT.IMG & SYSTEM.IMG THAT WERE BACKED UP INTO THE TOOLS FOLDER AND TYPE IN CMD
FASTBOOT FLASH BOOT BOOT.IMG
FASTBOOT FLASH SYSTEM SYSTEM.IMG
I had to do that many a times because most of the roms failed to install...
tell me if any of that helps...
PS thanks for the test i have now changed the instructions on the main page..
Killadude said:
First u could try in fastboot mode re booting to the recovery img boot..... once in there wait for a minute, connect usb to computer and in cmd go to tools folder and type
adb devices, if u see a serial underneath then type
adb push boot.img /data/local/boot.img
with the image you downloaded if this fails then, ill redriect u to a link Thanks to daldroid itll help you run the origanal magic rom, without the rogers crap installed on it. Just not you have to set the api settings in the menu to:
name: rogers
address: internet.com
to acess the rogers edge/3g internet.
http://www.arbitraryuser.com/blog/2...-south-africa-to-get-android-market-and-more/
just skip to instruction number 8 in the step by step instructions
PS IF U DID DO A NANDROID BACKUP JUST PLACE THE BOOT.IMG & SYSTEM.IMG THAT WERE BACKED UP INTO THE TOOLS FOLDER AND TYPE IN CMD
FASTBOOT FLASH BOOT BOOT.IMG
FASTBOOT FLASH SYSTEM SYSTEM.IMG
I had to do that many a times because most of the roms failed to install...
tell me if any of that helps...
PS thanks for the test i have now changed the instructions on the main page..
Click to expand...
Click to collapse
OK, if I try to use adb, it gives me an error stating that the device cannot be found.
I tried using my own boot.img, but I got the same error. Any ideas?
hotweiss said:
OK, if I try to use adb, it gives me an error stating that the device cannot be found.
I tried using my own boot.img, but I got the same error. Any ideas?
Click to expand...
Click to collapse
When you are in fastboot mode, "adb devices" won't show it. I THINK he meant "fastboot devices". It should show your devices in fastboot mode
OK, I used Ubuntu to fastboot my boot.img and that has now worked. I have one question now, how do you enter your Rogers data information. The ROM doesn't make a data connection with Rogers.
hotweiss said:
OK, I used Ubuntu to fastboot my boot.img and that has now worked. I have one question now, how do you enter your Rogers data information. The ROM doesn't make a data connection with Rogers.
Click to expand...
Click to collapse
Settings -> Wireless Controls -> Mobile networks -> Access Point Names
EDIT: read the NEXT post for the correct settings to put into the fields
All the info and links needed, none of the fluff. If you have questions, simply ask.
This guide aims to be platform independent. However, some cheats may require user contribution. Thanks in advance!
UPDATED 5-4-2010: New, Faster Factory Reset. Thanks rt1oo and johnsongrantr
Root CDMA Hero, Load Custom Recovery & ROM
Forum Post: Step By Step Way to root Using Flashrec(Updated 4/5)
Thanks goku14238
1) Download: flashrec-1.1.3-20091107.apk
1.1) Download: recovery-RA-heroc-v1.6.2.img
1.2) Download ROM ZIP of Choice: XDA Wiki - ROMs
1.3) Market Download: Any File Manager. RootExplorer, ES File Manager, Astro, etc.
2) Rename "recovery-RA-heroc-v1.6.2.img" to "recovery_backup.img"
3) Copy downloads to SD card root (/sdcard/)
4) Fill in check box for: Settings>Applications>Unknown sources
5) Install "flashrec-1.1.3-20091107.apk" via Any File Manager (RootExplorer, ES File Manager, Astro, etc.) or ADB
*Unmount SD Card if mounted through USB*
6) Open "Recovery Flasher" App and select "Restore Backup Image"
7) Power OFF
8) Power ON to Recovery: Press and hold the "Home" button, Continue holding "Home" while pressing and releasing the "Power" button
9) Flash zip from sdcard>select ROM ZIP
10) Reboot
Reset Phone With Loaded ROM (1.5 "Cupcake" ROMs)
Code:
Menu > Settings > Security > Factory data reset > Reset phone > Erase everything
Reset Phone With Loaded ROM (2.1 ROMs)
Code:
Menu > Settings > Privacy > Factory data reset > Reset phone > Erase everything
Factory Reset
Thanks rt1oo: Forum Post
This will return the phone to its out-of-box, factory condition (including radio!).
Search "RUU" if you want it the official Windows way.
NOTE: If you used the 2.1 RUU, this will not work. HBoot version must be 1.41. Read Forum Post for another method.
1) Download: HERCIMG.ZIP
2) Copy to root of SD card (/sdcard/)
3) Turn phone OFF
3) Hold Volume Down while pressing the power button (turn back on)
4) Press trackball when prompted
5) Reboot
Boot to Recovery from Power OFF
Press and hold the "Home" button, Continue holding "Home" while pressing and releasing the "Power" button
Nandroid Backup
-Reboot into recovery mode>Backup/Restore>Nand backup
TIP: If you choose "Nand backup + ext" it will backup your apps2sd apps along with your imaged system.
*CAUTION: you must restore this kind of backup to an SD Card that is similarly formatted (i.e. SWAP/EXT/FAT backup)
COPY THE CONTENTS OF THE "nandroid" FOLDER TO OTHER MEDIA ON REGULAR BASIS IN CASE OF SD CARD FAILURE!
Nandroid Restore
-Reboot into recovery mode>Backup/Restore>Nand restore>Select desired backup
*TIP* If no backups are found, you need to copy the "nandroid" folder back onto your SD Card from your Computer backup (You did make a copy of nandroid to your Computer didn't you!?)
Partition SDCard for apps2sd (A2SD)
-WARNING: This will erase EVERYTHING from the SDCard. Nandroid does NOT backup SD Card data, except for apps2sd apps, and ONLY if you selected "Nand backup + ext"
1) Reboot into recovery mode>Partition sdcard>Follow on-screen instructions (Default values suggested are OK)
Load Custom ROMs
Download ROM ZIP of Choice: XDA Wiki - ROMs
1) Copy ROM ZIP to SDCard Root (/sdcard/)
2) Reboot into recovery mode>Flash zip from sdcard>select ROM ZIP
Load Android SDK [Mac]
1) Download Latest Android SDK: http://developer.android.com/sdk/index.html
2) Unpack and rename the extracted folder to "AndroidSDK", Move it to "Applications"
3) Copy and Paste into TextEdit:
Code:
export PATH=${PATH}:/Applications/AndroidSDK/tools
4) Save as: "~/.bash_profile"
5) Fill check box on Phone: Settings>Applications>Development>USB debugging
How to modify system files from Recovery
Code:
adb shell
mount <MOUNT_POINT>
Replace <MOUNT_POINT> with area you want to modify (ex: /system /data)
Install Apps through ADB
Code:
adb install <PATH_TO_APK>
Replace <PATH_TO_APK> with the location of your apk (ex: ~/Installers/Android/apk/wireless_tether_1_60_htc.apk)
How to tell if apps2sd (A2SD) is working
1) Connect Phone via USB
Code:
adb remount
adb shell
ls /system/sd/app/
If you get a list of applications, or no errors, then apps2sd is *should be* working properly.
Remove Extra Useless Preloaded Apps
Link: Root Explorer
Yes, you CAN do this through adb, but this is MUCH easier. Simply open, hit "mount r/w" button, delete anything in /system/app and /data/app you don't want! I'm well aware of the cost of the app. If you don't want to pay and help the developer, then search the forums and figure it out yourself !
Good stuff. Thanks for the contribution. Would you mind if I put it on GeekFor.Me / would you like to put it on there?
http://geekfor.me/news/wanted-writers-for-faq-tutorial-help/
Let me know.
Please do! Thanks for the read! Also, thank you very much for all of your hard work, the ROMs you make are crucial to all of this stuff advancing forward!
Thanks for putting this together - great post!
Thanks a lot for this Gallias. Definitely helped me out. I wish I had found this a couple weeks ago heh.
When I tried to enable compcache with your instructions I was getting a read-only error. Doing 'adb remount' first seems to have solved it.
AH yes thank you my apologies. Updated.
Hey, I swear i've tried for two hours to get Modacos custom ROM installed. I successfully installed the recovery-RA-heroc-v1.5.2.img and when I power off and reboot into recovery mode, I only get one option -- to CLEARSTORAGE "Delete all user data? <action>yes <send> no, I select YES and it reboots the phone and it looks like the same interface. I've tried flash_image recovery /sdcard/update.zip by renaming the ZIP file modaco 2.2 to (update) and moving it to the SDCARD home directory. I then use Lindas file manager to load the custom recovery image and select SDCARD/update.zip This doesn't work (I'm probably doing something wrong) But I don't understand why I can't boot into recovery mode. I am using the CDMA (sprint) version.
Any tips? I need a bit of some help here.
When you reboot into recovery mode you should see this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you don't see that, then you haven't actually pushed the new recovery image into the phone. The screen you describe is the default recovery loader that comes with the phone.
Try my "Load Custom Recovery" step over again, or if on a different platform, follow the root guide for your specific platform:
CDMA Hero Guides
I got up to the point of
adb push asroot2 /data/local
it says 836 KB/s <74512 bytes in 0.087s>
C:\hero\tools> aadb shell
$chmod 0755 /data/local/asroot2
chmod 0755 /data/local/asroot2
$ /data/ocal/asroot2 /system/bin/sh
/data/local/asroot2 /system/bin/sh
now get this.... this is what it gives back to me
[+] Using newer pipe_inode_info layout
Opening: /proc/758/fd/3
YES it says 758 NOT 857.
It then says
SUCCESS: Enjoy the shell
Is that right or is it supposed to be 857? I saw the guide and it told me that it should say 857 so it's not giving me the right message I assume.
I'll try again and see if this is right, i'll post an edit later to let you know if I get it workin, if not I guess 758 is incorect
Well, based on the C:\ I'm going to say your using Windows. I don't think that number will be critical, but you do need to perform this after you get the "SUCCESS: Enjoy the shell"
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4775 su
exit
exit
THEN, you also need to push the recovery image. If you are following the link I placed at the top of this guide on how to root with Windows, it should have you go through everything I'm explaining. Don't get worried or hung up on steps that don't exactly match up with what other people are seeing; at the end of the day you may see some differences, but if you are getting "SUCCESS" from asroot2 it means that the technical "rooting" part is working, you just need to finish up and follow through on the rest of the steps. Keep working at it you are really close, don't let inconsistent numbers discourage you!
Just letting you know, you've got a typo in the rooting area. It should be asroot2 not asroot 2
ffolkes said:
Just letting you know, you've got a typo in the rooting area. It should be asroot2 not asroot 2
Click to expand...
Click to collapse
Ah yes very true thanks! Fixed.
I followed the instructions for rooting with a MAC, I did the boot into recovery mode, there is no option for "NANDROID" backup. It just says "Clear User Data" <ACTION> Yes <SEND> No. Wound up clearing everything off my phone.
rlundeen said:
I followed the instructions for rooting with a MAC, I did the boot into recovery mode, there is no option for "NANDROID" backup. It just says "Clear User Data" <ACTION> Yes <SEND> No. Wound up clearing everything off my phone.
Click to expand...
Click to collapse
Ouch! Sorry man, it means something went wrong during "Load Custom Recovery [MAC]". Try that step over again.
theraginasian said:
Ouch! Sorry man, it means something went wrong during "Load Custom Recovery [MAC]". Try that step over again.
Click to expand...
Click to collapse
Did it 3 times, get the same thing over and over. Actually, if you hold the Volume Down key and then power the phone on, I can do the nandroid backup, flash rom, etc.
theraginasian said:
Remove Extra Useless Preloaded Apps
Forum Post 1: How to remove Stocks, Nascar, and other useless apps...
Forum Post 2: APPS that are SAFE to remove
Thanks chuckhriczko and VoXHTC!
Beyond what most custom ROMs remove, I remove:
-Sprint Navigation (Sprint_Navigator.apk/odex)
-Sprint Visual Voicemail (Sprint_Core.apk/odex)
-Device Self-Service (SDSA.apk/odex)
Code:
adb remount
adb shell
cd /system/app
rm <NAME_OF_APP>.apk
rm <NAME_OF_APP>.odex
Replace <NAME_OF_APP> with the name of the app you want removed.
Make sure to check /system/sd/app for duplicate/other unwanted applications if you have apps2sd running.
Click to expand...
Click to collapse
Thanks the cheat sheet. Is this list of apps that can be safely removed still valid for 2.1 ROMs? I am running DC v2.07.2 ROM.
prateekandroid said:
Thanks the cheat sheet. Is this list of apps that can be safely removed still valid for 2.1 ROMs? I am running DC v2.07.2 ROM.
Click to expand...
Click to collapse
Make a NANDROID before removing any of them, so if you remove something you want back or that messes your phone up. You can go back to original.
They arent usually the main choices. But you can if you want to.
Heres some you can remove.
Type this
adb remount
adb shell
cd /system/app
ls
* "ls" this will show you all the apps on your phone.*
These are commonly removed-
Sprint_Navigation.apk
Sprint_TV.apk
Sprint_TVWidget.apk
Sprint_Nscar.apk
Sprint_NFL.apk
Stock.apk
com.htc.StockWidget.apk
HtcRingtoneTrimmer.apk
Youtube.apk
Facebook.apk
There are more, but these are usually the common ones. Pick and choose what you want and what you dont want.
Jus10o said:
Make a NANDROID before removing any of them, so if you remove something you want back or that messes your phone up. You can go back to original.
They arent usually the main choices. But you can if you want to.
Heres some you can remove.
Type this
adb remount
adb shell
cd /system/app
ls
* "ls" this will show you all the apps on your phone.*
These are commonly removed-
Sprint_Navigation.apk
Sprint_TV.apk
Sprint_TVWidget.apk
Sprint_Nscar.apk
Sprint_NFL.apk
Stock.apk
com.htc.StockWidget.apk
HtcRingtoneTrimmer.apk
Youtube.apk
Facebook.apk
There are more, but these are usually the common ones. Pick and choose what you want and what you dont want.
Click to expand...
Click to collapse
Thanks for a prompt response.
Just curious, wat do people prefer instead of Youtube.apk to watch Youtube? Because as far as I know there is no Adobe Flash support yet. So Youtube videos will not work on its website. I use Dolphin browser.
i personally believe the flashrec method is much more practical. i was able to root and flash a custom rom without ever plugging my phone into my computer, i did it all from my phone.
is there a downside to flashrec im not aware of?
This all started out as an experiment to get my nandroid system.img file running in the adb emulator. Well sadly I haven't been able to do that (yet) but I have found something useful. I've Seen several people all over asking how to get a working marketplace app in 2.2 on the adb emulator. After a lot of researching (and trial and error) I've managed to get one. Here are the steps I've taken. (Steps 5 and 6 optional, you can just use the included build.prop if you prefer)
1) Create an avd running 2.2 (froyo,plenty of places explain how to do this so I won't)
2) Download the file (attached below, root files included)
3) Unzip to a location that's easy to remember and find.
4) Load your emulated phone (allow it to load fully)
5) enter this command in a command prompt/terminal window (make sure you "cd" to the directory where you extracted the files)
Code:
adb pull /system/build.prop
6) Remove or comment "ro.config.nocheckin=yes" (no quotes, might be able to just change it to "no" but I haven't tried it that way)
7) enter these commands
Winblows (I mean windows)
Code:
adb remount
adb push build.prop /system/build.prop
adb install GoogleServicesFramework.apk
adb install Vending.apk
adb install Gmail.apk (optional but sometimes signing in here lets the market sign in)
adb shell rm /system/app/SdkSetup.apk
Linux
Code:
adb remount
adb push ./build.prop /system/build.prop
adb install ./GoogleServicesFramework.apk
adb install ./Vending.apk
adb install ./Gmail.apk
adb shell rm /system/app/SdkSetup.apk
8) Sign in. If it works you're done if not reboot and try again, sometimes it takes 3 or 4 reboots to set. If your emulated phone has a data signal from your computer (you'll see a 3G and network icon in the notification area) just wait for it to sign in. The cancel button should grey out within a minute. If it says it can't connect restart the emulator and try again, be patient.
There is a known bug that not all apps show up in the marketplace. I'm not sure why so if someone here knows how to fix that by all means leave a post and let me know. If I see it I'll add it to the first post (provided it works of course )
Edit: Working on getting root on the emulator (just for the hell of it). So far I have su in the xbin directory and superuser.apk installed. Not 100% sure what else I need to do to get the su requests to go through though, I'll probably PM a more experienced member and post back when I have more. Got root? I do (got it working.) Here are the steps you need to take.
Rooting the standard android image on the emulator
1) Open a command prompt (cd to the directoy where you extracted the files)
2) enter these commands
Code:
adb shell mount -o rw,remount -t yaffs2 /dev/block/mtdblock03 /system
adb push su /system/xbin/su
adb shell chmod 06755 /system
adb shell chmod 06755 /system/xbin/su
adb install superuser.apk
That's it! You now have a rooted, market-enabled android emulator.
New! N00b-friendly method
1) create your avd
2) download the emulator files archive attached to this post
3) extract somewhere easy to find
4) open command prompt/terminal and cd to the extracted location
5) start your avd
6) Run your script (windows.bat or linux.sh)
7) sign into market and enjoy root!
Note:
You may have to chmod su again upon restarting the emulator.
To get root back simply run the re-root script for your OS (bat for windows,sh for linux)
To install busybox simply run the re-root script, it will automatically install if you're using the script to install on a new avd.
Post 2
[reserved for updates, explanations, pictures, present/future tweaks in progress, etc]
Pictures:
Superuser list,Marketplace (I like solitaire><), Terminal with su permissions, and re-rooted Terminal​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tweaks:
1: root (done!)
2: busybox (done!)
Wow nice....
Thank you the root resets after reboot, working on making it stick but its not hard to do it again, just start with the "-wipe-data" command and redo the root, market works after reboot though. Still working on getting a dumped system.img to boot, ill post that in its own thread when i get it. Glad you like this.
Sent from my ROOTED T-Mobile myTouch 3G Slide using XDA App
Edit: see first post on how to get root back,no data-wipe!
so cool!! Good job man!
Thanks ^_^ let me know if you find any problems that I haven't already mentioned and I'll see if I can fix them or if they're just an emulator quirk.
Sorry for the double post but I wanted to let you all know busybox is now included! Installation can be performed through scripts (included in the "Emulator Files.rar" archive) or manually. If you wish to do it manually simply open the script in a text editor to see what's going on and enter the commands in a command prompt/terminal window.
I'm not able to make this work, not with a toolkit downloaded yesterday anyway.
Pulling of build.prop works, but pushing fails with a directory related error.
"adb shell" followed by "cd /system" and "ls -l" gives a list of files that does not include build.prop, neither as a file nor as a directory.
"ls -l build.prop" works though, and lists a file with 0644 permissions.
Install of all apks different from Gmail fails, with an error that says that those apks are already installed. Uninstalling them through adb doesn't work, netting instead a simple generic error.
Does anyone know whether I'm doing something wrong or Google has modified the emulator images so to render the Market workaround unusable? If so, where could I download an earlier version of the 2.2 system image?
Many thanks
Rocco
I actually had this issue as well. Try re-making the avd, worked for me. You could also try running the scripts to install, might work. If it doesnt post back and ill post the system.img from my sdk.
Sent from my ROOTED T-Mobile myTouch 3G Slide using XDA App
I have the same problem as ropi. Remade the avd several times with different properties, still no go.
I would really appreciate it if someone could upload a fully set-up avd somewhere.
I'll try again late this afternoon (I'm on CEST). Hope it works. If not, I'd be happy too if some kind soul would upload a link to a working avd
Thanks for the kind help
Rocco
I have no idea why people are having so many problems :/. I had the problem and once I remade the avd it went away. Try starting with the -partition-size 96 option and see if that helps. If not here are the files, just extract to your avd directory, it has the ini and img files you need and it's already setup. Just run re-root to get root back and sign into market and you're good to go.
http://hotfile.com/dl/79959332/3efbade/froyo-avd.rar.html
Edit: I just downloaded the latest revision and everything seems to be working fine :/ As I've said before try starting with -partition-size 96 and also try using the scripts I've provided. That should fix the issues, but if it doesn't there's always the hotfile link I've provided (or if you're just lazy lol)
Edit 2: also,just thought of this, make sure before you push the build.prop you adb remount. Pulling will work fine without doing that but pushing won't. No one said if they had done this and still received the errors so I'm trying to cover all bases. If remount fails try the adb shell mount command posted on the first page.
Thanks dbzfanatic, that avd worked great.
Glad it worked for ya. Let us know how everything works.
Sent from my ROOTED T-Mobile myTouch 3G Slide using XDA App
A lot of apps can not be found in the Market ... I cannot find Lookout....
Yeah, I've mentioned that,firs post. It's a known bug. Nothing I can do to fix it at the moment. You could download the apk on your phone then pull it then install it in the emulator. Bit of a roundabout way of doing things but it's all we can do on the emulator for the time being, at least from what I know.
Ok after a bit of poking around (sorry it took so long) I found out a bit about the market. It seems it's not just your region that it uses to show apps but things like your carrier, presence/absence of a SIM card, Android version, etc. It uses the filters to choose which apps to show and which to exclude (not showing an American user Japanese apps, not showing someone on Verizon T-Mobile apps, etc) so this explains part of the problem. I also found out that the SIM card and IMEI numbers were(are?) hard-coded into the emulator binary, changing these may allow us to see a few more apps. I looked through the binary file a bit and didn't find anything but I'll look more closely in a bit (new job, yay <- read as "groan"). I don't know how to emulate or spoof a carrier so that will still cut us back on some of the apps being seen. If anyone knows how to do this please post here and let us know! It would also be beneficial if a user who has already modified their IMEI and SIM numbers in the emulator to compare the apps list to the one you see in the standard, non-modded emulator binary and let us know if there is a difference or not. The more apps we can see in the marketplace the better!
Just wanted to confirm that I've tried Market Enabler a few days ago and it doesn't seem to work.
Alright thanks for the feedback. Ill keep working on it.
Sent from my ROOTED T-Mobile myTouch 3G Slide using XDA App
Despite several tries, I've so far been unsuccessful in using this method to install the marketplace on a 2.2 avd. Many thanks for having provided ready-made avds, then!
I've been able to install marketplace on the Galaxy Tab images provided by Samsung, though!
Keep up the good work
Will type up better guide later on gonna include my ota i pulled as well maybe help someone
btw do at ur own risk im not responsable if u mess the phone up
added batch script hope it works to automate the process and guide u. before u can use this guide or batch script make sure to enable developer settings and adb
you can download it this https://forum.xda-developers.com/attachment.php?attachmentid=4181698&stc=1&d=1497456929 extract it go into the folder find root.bat double click file.
or follow the guide below
1.need to get temp root with king root first grab that here https://kingroot.net/ grab file for android not windows version
grab this file https://forum.xda-developers.com/attachment.php?attachmentid=4180414&stc=1&d=1497364232
2.once extracted go inside folder. hold down shift key and right click inside the folder. click open command window here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
unhide for root guide
3. type this "su"
then continue guide
4. type this "getprop ro.product.name"
should show output "ZTE_BEAM"
5. type this "setprop persist.sys.k ZTE_BEAM"
6. type this "getprop persist.sys.k"
output "ZTE_BEAM"
7. type this "cd /dev/block/platform/soc.0/7824900.sdhci/by-name/"
Lets backup recovery
8. type this "dd if=recovery of=/sdcard/recovery.img"
Lets write boot to recovery!
9. type this "dd if=boot of=recovery"
10. type this inside of adb shell "reboot recovery"
if u get black screen just hold power down to reboot
once booted up
make sure your still inside adb command prompt
11. type this "adb shell"
12. type this "su"
13. type this "id"
should show this output
"uid=0(root) gid=0(root) context=u:r:shell:s0"
then to set permissive
14. type this "setenforce 0"
15. type this "getenforce"
output "Permissive"
16. to test if mount system rw while still root type "mount -o remount,rw /system"
if it mounts no errors then system is writeable
reboot
if for some reason u cant write to system u can try
run this command in adb shell or terminal
reboot disemmcwp
to re-enable write protection issue this command
reboot emmcwpenab
working on replacing king with supersu til then perm root with kingroot
enjoy
and u wanna donate for my hard work click here http://paypal.me/riley60
to restore recovery back to stock u can do once u have perm root do this to restore recovery
type this inside of adb shell dd of=recovery if=/sdcard/recovery.img
hit the thanks button if my post was helpful
original guide here
thanks jcase for his guide for me to base on
https://plus.google.com/+JustinCaseA...ts/KzgyHLgVhwo
also dont forget to hit the thank you button if this post was helpful
ota file attached may help some that are bricked
to remove annoying lock screen with ads
open king root then touch the 3 dots goto settings
then touch accelerate charging turn switch it off
then that annoying part is gone if purify is installed remove it and everything should be good.
Awesome, do you know if this will work on the ZTE Warp Elite?
everyone get their phone rooted ok
Well 2 things...
1: can you lost a guide on how you did those steps?
2: if I already did a software update for my phone, would that affect my chances of getting my phone permanently rooted?
those steps are the guide if you dont know what adb is or how to use it or king root then u could look both those up for guides on the 2. after u know how to use both its pretty much gain temp root have adb open then paste commands make sure they say the same as the guide for outputs follow all steps and should be good. unless they released an update that make it android n im sure it will work. once i send in these 2 dead phones to get repaired ill make a video guide of the steps in guide. as i dont know if it will break root to try redo all the steps to show everything i did.i will see if i can automate the process with batch script. aka filename.bat
updated the guide lil for if anyone who is lil new to adb etc
I've used adb when dealing with moto phones. But this has me confused as to what to actually put in cmd prompt. Either way you're a God among us. I'm going to attempt and see if I can get it working. Thank you for your work sir. Hope to see a batch script some day.
added batch script
No errors so far. Just a little sluggish.
Stevenbew said:
No errors so far. Just a little sluggish.
Click to expand...
Click to collapse
um no errors from what and whats sluggish and for anyone who asks i used the lastest kingroot version
Just errors in general. Nothing is giving me any problems. My phone was a little sluggish after first rebooting. Almost acted like a temp root until I ran the reboot disemmcwp cmd. Then no problems.
Stevenbew said:
Just errors in general. Nothing is giving me any problems. My phone was a little sluggish after first rebooting. Almost acted like a temp root until I ran the reboot disemmcwp cmd. Then no problems.
Click to expand...
Click to collapse
did u use script or manual
madvane20 said:
did u use script or manual
Click to expand...
Click to collapse
I did it manually. Knowing exactly what to type after you edited made everything alot easier to understand.
Stevenbew said:
I did it manually. Knowing exactly what to type after you edited made everything alot easier to understand.
Click to expand...
Click to collapse
ok i only asked cause im already rooted so i couldnt really test the script but it should work and at the end it tells what commands to type in to test. looks like i may need to edit the guide lil bit later and edit my script
I read the guide over and over. While I think I may understand, I'm still afraid to attempt this since it is my only phone and I cannot replace it currently if something were to go wrong. Your typing style makes it somewhat difficult to understand but nonetheless, thank you. I'll attempt when I'm able to replace the phone if something goes wrong.
Heartseed said:
I read the guide over and over. While I think I may understand, I'm still afraid to attempt this since it is my only phone and I cannot replace it currently if something were to go wrong. Your typing style makes it somewhat difficult to understand but nonetheless, thank you. I'll attempt when I'm able to replace the phone if something goes wrong.
Click to expand...
Click to collapse
use to batch script after u get temp root it will do most of the work for you and guide u through the rest
I need help, I can not do temporary root, so neither method allows me to enter the ADB get the SU command, should the phone have any condition before trying to apply them? My phone has software version 0B09 and the options are unlocked OEM and USB debugging, which I am doing wrong, any commentary? thank you!
Pirela said:
I need help, I can not do temporary root, so neither method allows me to enter the ADB get the SU command, should the phone have any condition before trying to apply them? My phone has software version 0B09 and the options are unlocked OEM and USB debugging, which I am doing wrong, any commentary? thank you!
Click to expand...
Click to collapse
grab the newest king root then if it fails keep trying it til it goes through. if it fails uninstall king root reboot reinstall try again. also try adding this commands first if it works without root "reboot disemmcwp" without quotes then try install king root and root see if u get temp root. then if it makes it easier i have a batch script made in the minimal adb and fastboot package
madvane20 said:
grab the newest king root then if it fails keep trying it til it goes through. if it fails uninstall king root reboot reinstall try again. also try adding this commands first if it works without root "reboot disemmcwp" without quotes then try install king root and root see if u get temp root. then if it makes it easier i have a batch script made in the minimal adb and fastboot package
Click to expand...
Click to collapse
Mandvane20 Thanks for your answer and interest
It was not possible to have some temp root, I tried with king root apk and pc, also with kingo root, I went to recovery and deleted the cache, I have force stop the application, I uninstalled and reinstalled, use reboot Disemmcwp, I have made multiple attempts and none has worked, I keep reading, searching and learning, I hope to get some way
Pirela said:
Mandvane20 Thanks for your answer and interest
It was not possible to have some temp root, I tried with king root apk and pc, also with kingo root, I went to recovery and deleted the cache, I have force stop the application, I uninstalled and reinstalled, use reboot Disemmcwp, I have made multiple attempts and none has worked, I keep reading, searching and learning, I hope to get some way
Click to expand...
Click to collapse
connect to pc open adb shell run king root while its trying to root keep typing su in adb shell tell it says root. or til it doesnt give u the error saying no su then proceed with guide see if that works