Prior to being rooted on 1.57 I had to sbf 1.26 then I ran retainroot version2, following the original instructions. This morning I was on 1.57 when I got the notification of the update to 1.83. I immediately downloaded the update and installed without any issues. After the installation of 1.83 was completed, I confirmed that I had lost root by opening root explorer and sql lite.
I downloaded the latest version of Gladroot and extracted the contents to the C drive or root drive of my windows 7 machine. Make sure that your device is already setup for usb debug mode. I connected my atrix and then selected the usb to None.
Next, I start the command prompt, I ran command prompt as administrator.
Make sure you are in the directory where you extracted Gladroot. Again I put mine under c:\.
From the command prompt I confirmed that the atrix was connected using the following command.
[adb device]
After I confirmed the atrix was connected I ran the following command.
[afterupdate.bat]
Read the message on the command prompt window and wait for your device to reboot.
I confirmed I had root by running root explorer and confirming I could write and by opening sql lite which did not give me the error message regarding not being rooted.
I have not had any problems since rooting or updating to 1.83.
Hope this helps other by simplifying the process. This worked for me the first time and I did nothing else.
aglowlight said:
Prior to being rooted on 1.57 I had to sbf 1.26 then I ran retainroot version2, following the original instructions. This morning I was on 1.57 when I got the notification of the update to 1.83. I immediately downloaded the update and installed without any issues. After the installation of 1.83 was completed, I confirmed that I had lost root by opening root explorer and sql lite.
I downloaded the latest version of Gladroot and extracted the contents to the C drive or root drive of my windows 7 machine. Make sure that your device is already setup for usb debug mode. I connected my atrix and then selected the usb to None.
Next, I start the command prompt, I ran command prompt as administrator.
Make sure you are in the directory where you extracted Gladroot. Again I put mine under c:\.
From the command prompt I confirmed that the atrix was connected using the following command.
[adb device]
After I confirmed the atrix was connected I ran the following command.
[afterupdate.bat]
Read the message on the command prompt window and wait for your device to reboot.
I confirmed I had root by running root explorer and confirming I could write and by opening sql lite which did not give me the error message regarding not being rooted.
I have not had any problems since rooting or updating to 1.83.
Hope this helps other by simplifying the process. This worked for me the first time and I did nothing else.
Click to expand...
Click to collapse
Should have just posted a link to the thread that originally covered this, now give credit to the people who gave us this.
Is this a "How to" on following a "How to"?
A really easy way to Root when you get to 1.8.3 is to use Gingerbreak.
The full guide is here, make sure you follow the directions 100%.
Does anyone still has the script that we can run in the console to hide the files to attain root?
Yeah, there was a bunch of stuff to read and yeah I read through a lot of it. I was simply pointing out that it's pretty easy and didn't involve much of the steps that are listed in the other how to guides. I downloaded 1 file and ran a couple command prompts and then verified.
Not trying to take credit for any work accomplished by anyone else. I didn't create Gladroot or retainroot, I simply used those tools following directions I had previously read. I wanted to make it easy for the person that had simply rooted 1.57 and wanted to retain that root on 1.83 without all the hassle of Gingerbreak or any other solution.
The method worked for me and I wanted to pass that along.
Have a nice day.
or you can just install gingerbreak...worked for me after flashing 1.8.3 sbf
neotekz said:
or you can just install gingerbreak...worked for me after flashing 1.8.3 sbf
Click to expand...
Click to collapse
Yup - worked for me as well.
btw you can mix and match Gladroot with Gingerbreak. What I did:
1. rooted on 1.57 with Gladroot and Gladenable
2. ran Gladroot unroot, which has a minor typo in unroot.bat and does not remove su or sqlite, but does execute the uninstall and remove root access
3. ran gingebreak root
4. ran gingerbreak unroot, which removes only su, not sqlite (which is ok)
5. apply 1.83 update
6. ran gingerbreak root
To be safe, I just wanted my phone to be completely unmodded and not rooted (no su) prior to the update. From reading various posts it seems applying 1.83 on a rooted 1.57 is ok though.
gnahc79 said:
btw you can mix and match Gladroot with Gingerbreak. What I did:
1. rooted on 1.57 with Gladroot and Gladenable
2. ran Gladroot unroot, which has a minor typo in unroot.bat and does not remove su or sqlite, but does execute the uninstall and remove root access
3. ran gingebreak root
4. ran gingerbreak unroot, which removes only su, not sqlite (which is ok)
5. apply 1.83 update
6. ran gingerbreak root
To be safe, I just wanted my phone to be completely unmodded and not rooted (no su) prior to the update. From reading various posts it seems applying 1.83 on a rooted 1.57 is ok though.
Click to expand...
Click to collapse
I am right now rooted with gladroot, still on 1.57 but getting a notification to updated to 1.83. does this mean I have to unroot the gladroot and then re-root with gingebreak before i update to retain root?
If someone could post detailed instructions and maybe links files I need to download I would be greatly appreciated. (its my first droid device, coming from win-mo, love it so far
hlywine said:
I am right now rooted with gladroot, still on 1.57 but getting a notification to updated to 1.83. does this mean I have to unroot the gladroot and then re-root with gingebreak before i update to retain root?
If someone could post detailed instructions and maybe links files I need to download I would be greatly appreciated. (its my first droid device, coming from win-mo, love it so far
Click to expand...
Click to collapse
You should be fine with 1.57 w/ root (no webtop or other mods installed) and then update to 1.83.
1) Make sure sideloading is enabled. If you can install gingerbreak on 1.57 then you're fine.
2) update to 1.83
3) back up your internal SD and external SD contents to your PC
4) root w/ gingerbreak
5) copy back over your internal and ext SD contents if they are wiped out on your phone
{
"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"
}
omg its moving great
Sent from my MB860 using XDA Premium App
norm688 said:
Does anyone still has the script that we can run in the console to hide the files to attain root?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=12506713&postcount=88
Thank you! this is super nice that I don't have to flash back to 1.26!!!! Woo Hoooo!
Related
Team,
This One-Click Root process will copy over the rooted-update.zip or unroot-update.zip file then reboot your phone. Follow the instructions in the CMD prompt that launches.
Credits:
LeshaK at Samdroid: for the original rooted-update.zip.
gunnarhafdal : for creating the Mac GUI for my app.
This has been tested on stock Android 2.1 Eclair only. If you rooted using another process you can use this process to unroot as long as you didnt load a rom that created links to busybox.
For the following models:
GT-I9000
Captivate SHG-I897
Vibrant SGH-959
GT-I9000M
Epic SPH-D700 (Untested but should work like other phones. Post with your results. This is harmless it will either work or it wont. It copies over 3 files to your existing build.)
Rooting adds the following to your system and unrooting removes them:
/system/xbin/busybox (version 1.17.1)
/system/xbin/su
/system/app/Superuser.apk (version 2.3.1)
and links /system/bin/su to /system/xbin/su
More will follow as they are released. PM me to add your Galaxy S Model.
Warning: I am not responsible for bricked phones, rooting can void your warranty....
PC Instructions:
{
"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"
}
Download the app: here, mirror.
Watch the video for the full procedure on The Unlockr.
Video/Procedure Link Click Here
Requirements: Install Link: Dot Net Framework version 4
Rooting Instructions:
1. Make sure your phone is on USB Debug mode: (MENU > Settings > Applications > Developement > USB debugging = Checked )
2. For Windows x86 and x64 systems make sure that the Samsung Drivers are installed. You can get them here.
3. Extract the contents of GalaxyS_Vibrant_One-Click_Root.rar to a folder.
4. Connect your phone to your PC via the USB cable and launch the file "T-Mobile Vibrant One-Click Root.exe" file.
5. Click the "One-Click Root" button. This will launch a command shell follow the instructions in the CMD window.
Mac Instructions:
Download the app: here, mirror.
It requires Mac OS X 10.5 or higher.
Rooting Instructions:
1. Make sure your phone is on USB Debug mode: (MENU > Settings > Applications > Developement > USB debugging = Checked )
2. Connect the phone to your computer.
3. Click one of the buttons depending on what you want to do.
4. After the phone has rebooted into recovery select "apply sdcard:update.zip" for I9000 and I9000M and choose "Reinstall Packages" for the US models using the volume keys and then press the home button for I9000 and I9000M and the power button on the right top side for US models to start the process.
=====================================================================
Done! You are rooted.
=====================================================================
Un-Rooting Instructions:
To Un-Root follow the same instructions except click on the Un-root button. If you rooted using another process you can use this process to un-root as long as you didnt load a rom that created links to busybox. I would suggest to restore you phone back to stock ROM before even needing to unroot and if you are on stock un-root all you want otherwise what is the point of un-rooting.
=====================================================================
Getting Started with Android After Rooting:
Flash Clockwork Custom Recovery On your phone:
Follow this URL to find fill information on ROM Manager:
http://forum.xda-developers.com/showthread.php?t=734164
Install ROM Manager from Market.
Launch ROM Manager and click on Backup ROM and save you android O/S stock rooted making getting back to stock un-rooted much easier..
Great app! I am on a Mac and rooted already so I don't need it but this should help about 90% of all new users.
Thank you.
+1 for the program. I rooted it last Sunday, and am too on a Mac, but this should def make the process alot easier for people.
This should go up as a sticky.
man it does not get easier for the new android users lol
Man I wish this app came out sooner...Fkn awesome!
Sent from my SAMSUNG-SGH-I897 using XDA App
One question since this seems to be a major topic as well, any way you could have it load a generic settings.db file or one click exit to the existing one for non-market apps?
That seems to be giving some people a bit of a headache.
decepticon said:
One question since this seems to be a major topic as well, any way you could have it load a generic settings.db file or one click exit to the existing one for non-market apps?
That seems to be giving some people a bit of a headache.
Click to expand...
Click to collapse
I will see what I can do. I don't have a Captivate. I have a Vibrant. But I have sent a request to kirbo20 to send me his file. If I get it I will add it to the app.
TGA_Gunnman said:
I will see what I can do. I don't have a Captivate. I have a Vibrant. But I have sent a request to kirbo20 to send me his file. If I get it I will add it to the app.
Click to expand...
Click to collapse
I will pull mine and post it here in a few
is your file the original?
Sent from my SGH-T959 using XDA App
It's edited to enable non-market apps
This is awesome, I have been waiting for this!
I am having a problem though, I have gotten to the "press the One Root Button" step. The green shell screen says it can't load the update onto my sd card, so when I re-install packages, it can't find the zip file. It does reboot the phone though and it is set on debug, is there a step I missed? I do have another 8g speed6 sd card I put in the empty slot, could that be messing it up?
Well sounds like your drivers maybe not set up right. go to start then run and open up prompt by typing cmd and see if "adb devices" runs and sees your device.
Sent from my SGH-T959 using XDA App
Ah, I just did it manually. Easy. Thanks for the motivation though.
Awesome work. I'll probably wait for the updated version with the "Unroot" option, but very cool nonetheless!
Here is my settings.db file. Some have speculated that it varies some from phone to phone so may need some testing.
It has been edited to enable non-market apps.
reminder to anyone using someone elses settings.db:
Make note of the android_id in your settings.db before swapping. You'll need it!
I think I am going to leave deploying settings.DB alone.
Sent from my SGH-T959 using XDA App
I created a duplicate batch for vibrant when it comes to rooting.
Ill paste the code in a sec.
Side loading
Script I had for SL'ing didn't work cause once adb shell is launched batch imput no longer works.
Temp rooted with visionary. Then I downloaded the root.rar files hboot and wpx I plugged my phone in moved them to the sd unplugged phone opened astro and I saw both files on my sd but the folder looked different they were white or something. I pressed on wpx and the hboot and they say "file type ko not found" terminal pretty much said something to that effect when I was entering the second command can someone please help me here I'm desperate.! And one more thing do I have to have adb installed for me to root?
1. Download the root.rar file and unzip it to /sdcard on your device.
2. Run VISIONary to gain temp root.
3a. Start terminal emulator up on your device.(I prefer this method b/c you can see the output.)
a. type "su" + enter to gain root privileges.
b. Type "cd /sdcard/root" + enter.
c. Type "sh root.sh" + enter.
d. Follow the on screen prompts.
---
c. Now wait about 18 to 20 seconds and restart your device
5. Run visionary again with permroot (if its what you want) and reboot again. This will make root stick.
Look here!! http://forum.xda-developers.com/showthread.php?t=895117
Two things i see that may be your problem. First, you have to be on 2.2.1 Second, After downloading the root.rar you are suppose to extracted it on your pc. It will extract a folder called root. that folder is to be put on the root of your sd card. Then follow the instructions above and all should be peachy.
Also debugging has to be on, fastboot off and check mark set system r/w after root on visionary. Hope it helped.
I'm going to try it now. There is a root folder with three files in it
Yes. dont touch it, just put the whole folder in your root sd. Then follow instructions.
Ugh all it says on terminal is root not found
When I open astro shows the root folder is in the sd so that means its in the root o of the sd correct ? Thank u in advance
When I open astro shows the root folder is in the sd so that means its in the root o of the sd correct ? Thank u in advance
Well you can try DL'ing a fresh copy of the root.rar and try it again..?
Here look at this. http://www.youtube.com/watch?v=eHrtVzlsA_s
Jmayes1786 said:
When I open astro shows the root folder is in the sd so that means its in the root o of the sd correct ? Thank u in advance
Click to expand...
Click to collapse
When you open that root folder, does it have another root folder inside it? Like 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"
}
Yes that's exactly what it looks like root.sh wpx hboot that's the one I'm putting in my sd
But for some reason it says nbo file not found sh file not found and ko file not found
Jmayes1786 said:
Yes that's exactly what it looks like root.sh wpx hboot that's the one I'm putting in my sd
Click to expand...
Click to collapse
I think you might've missed my question. Notice the red box in my screen shot? See how it has two root folders? i.e. \root\root
I want to pause and not go any further until we have clarification of if you have a "nested" root folder - i.e. a root folder within a root folder.
Keep me posted!
My advice is since it's obvious you don't really know what you're doing; DON'T ROOT.
You have demonstrated here today by not even knowing what folder to put on your SD card and where to put it, that you have no understanding yet about this process.
You seem to be rushing to root. You're just going to end up bricking it and then asking us for help.
If you don't know how to perform a Nandroid backup, or restore a previous ROM backup, flash updates, install custom ROM's, boot into Safe mode, Mount R/W, run shell commands or Terminal Emulator etc, then you should NOT root. You should browse the forums here, read, read and re-read everything until you know it well. Google search related topics. Exhaust all available avenues, then ask questions. After you've executed all of these options you might consider rooting and starting to tinker with your device.
This is not here to offend anyone's sensitivity or hurt your feelings. Many have argued that bricking and recovery is the way they learn. That's fine [for them]. I highly doubt those same people started running before walking, or walking before crawling. But the majority of people need to learn first. Preventing someone from ruining their device is MY best advice.
CBConsultation said:
My advice is since it's obvious you don't really know what you're doing; DON'T ROOT.
You have demonstrated here today by not even knowing what folder to put on your SD card and where to put it, that you have no understanding yet about this process.
You seem to be rushing to root. You're just going to end up bricking it and then asking us for help.
If you don't know how to perform a Nandroid backup, or restore a previous ROM backup, flash updates, install custom ROM's, boot into Safe mode, Mount R/W, run shell commands or Terminal Emulator etc, then you should NOT root. You should browse the forums here, read, read and re-read everything until you know it well. Google search related topics. Exhaust all available avenues, then ask questions. After you've executed all of these options you might consider rooting and starting to tinker with your device.
This is not here to offend anyone's sensitivity or hurt your feelings. Many have argued that bricking and recovery is the way they learn. That's fine [for them]. I highly doubt those same people started running before walking, or walking before crawling. But the majority of people need to learn first. Preventing someone from ruining their device is MY best advice.
Click to expand...
Click to collapse
Agreed 110%. Could not of worded it any better. When i bought my MyTouch3G a while ago i bought it used rooted because i didn't want to brick anything in the process. But since i've learned alot, and still am asking ALOT about various things.
Alot of people think Rooting a phone puts you in the "cool crowd" it doesn't all it does is prove that you know how to read and follow directions.
With that being said like the person said above me, read, read, read, read some more, then take a nap, when you wake up read, read, and read some more.
It took me about 6 months to to finally get up the nerves to even to unroot my phone /the Magic/, then about another 3 to re-root it. just so i would have the experience.
If you are just wanting to Tether, or run SetCPU i would highly advise just temprooting and being happy there.
I just don't get it man I think I'm just doing to listen to the dude above and read some more because for some reason I'm I'm doing something wrong with this root file. This sucks I wanted to get read of all the bloatware and start flashing roms. Thank u so much though for all ur help and everyone else thank u I'm going to read and give out another shot
First I need to pay credit to Stuke00 http://forum.xda-developers.com/showthread.php?t=1185243 for the commands needed for the Temp Root. Now this is a Temp Root not a Perm Root which means if your phone gets shutdown your root will be lost. A Perm Root has been made by Evil_DevNull here http://forum.xda-developers.com/showthread.php?t=1276583 Use this Temp Root if you dont want your phone to always be rooted or if you are trying to downgrade your HBoot.
The process is 4 easy steps.
1. Install SDK Manager to the root of your C:\ drive.
Follow this guide by BrandoKC here http://forum.xda-developers.com/showthread.php?t=932749 for installing SDK Manager properly.
2. Download these 3 files and place them in your C:\AndroidSDK\platform-tools.
http://downloads.androidsu.com/super...ser3-beta1.apk
http://downloads.androidsu.com/super.../su-3.0-alpha7
http://tinyw.in/1lI
3. Connect phone to computer and make sure you select Charge Only when asked by Connect to PC menu
4. Now download my Temp Root.rar and unpack. Run my Temp Root.bat file and your phone will be Rooted.
Follow step 3 and run my Temp Root Re-Root.bat file for re-rooting your phone if Temp Root is lost.
duckster18 said:
First I need to pay credit to Stuke00 http://forum.xda-developers.com/showthread.php?t=1185243 for the commands needed for the Temp Root. Now this is a Temp Root not a Perm Root which means if your phone gets shutdown your root will be lost. A Perm Root has been made by Evil_DevNull here http://forum.xda-developers.com/showthread.php?t=1276583 Use this Temp Root if you dont want your phone to always be rooted or if you are trying to downgrade your HBoot.
The process is 4 easy steps.
1. Install SDK Manager to the root of your C:\ drive.
Follow this guide by BrandoKC here http://forum.xda-developers.com/showthread.php?t=932749 for installing SDK Manager properly.
2. Download these 3 files and place them in your C:\AndroidSDK\platform-tools.
http://downloads.androidsu.com/super...ser3-beta1.apk
http://downloads.androidsu.com/super.../su-3.0-alpha7
http://tinyw.in/1lI
3. Connect phone to computer and make sure you select Charge Only when asked by Connect to PC menu
4. Now download my Temp Root.rar and unpack. Run my Temp Root.bat file and your phone will be Rooted.
Follow step 3 and run my Temp Root Re-Root.bat file for re-rooting your phone if Temp Root is lost.
Click to expand...
Click to collapse
Excuse me but i did not give you any permission to post a remake of my batch file. nor does a batch need android sdk installed to use
Evil_DevNull said:
Excuse me but i did not give you any permission to post a remake of my batch file. nor does a batch need android sdk installed to use
Click to expand...
Click to collapse
oh boy, here we go again . . .
I'm not using your batch file at all. If you read my post the batch file I have attached is a batch file I wrote myself based off the post for temp rooting based off the ADB commands posted by Stuke00. I just put a link to your post about the perm root that you posted to give you credit for a perm root. Lots of respect for you, I've been following your post for a while now.
duckster18 said:
I'm not using your batch file at all. If you read my post the batch file I have attached is a batch file I wrote myself based off the post for temp rooting based off the ADB commands posted by Stuke00. I just put a link to your post about the perm root that you posted to give you credit for a perm root. Lots of respect for you, I've been following your post for a while now.
Click to expand...
Click to collapse
What do you think android bullet is?
never mind... the script is fine......
This script wont work. I looked at it and it looks ****ed up.
Sent by breaking the sound barrier
Indirect said:
This script wont work. I looked at it and it looks ****ed up.
Sent by breaking the sound barrier
Click to expand...
Click to collapse
+7 ^^^^^^^^^^^
The way it calls the commands crashes adb...
Sent by breaking the sound barrier
Indirect said:
This script wont work. I looked at it and it looks ****ed up.
Sent by breaking the sound barrier
Click to expand...
Click to collapse
gee, tell us how you really feel. lol
Dude, im not trying to be a **** or ruin credit but 1) there is already 2 scripts for this (1 more advanced) and im saying how this guy can better his script. I tild him whats wrong in the second post i made.
Sent by breaking the sound barrier
Tests confirm, adb isn't fast enought to handle .002sec commands, which is why I put annoying pauses into it. Which is also why Inditect give adb time to catch up as well with his Yes/No request commands. Batch files are from the DOS age, but reliable in its simplest form. However old DOS with current ADB crashes. Which is why you can't call ADB its self.
This script is in all honesty, a fast way to soft brick ANY device.
the OG commands, I.e copy n paste gave adb time to follow thru with the commands and report errors as they come.
My script and batch had to be slowed down (pauses) to provide debugging information.
Indirects script added yes/no pauses to allow again, for adb to keep up.
Batch files are raw, fast and as dumb as it sounds, furious. It's unrelenting to say the least.
By this batch being as raw as it is, and uncontrollable as it is, seems irresponsible for any dev to release.
Please don't take this as an insult but why let others take it 2 steps forward, just to release something that takes 5 steps back.
Just my 15 years of exp worth of 2 cents.
{
"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"
}
Evil_DevNull said:
Tests confirm, adb isn't fast enought to handle .002sec commands, which is why I put annoying pauses into it. Which is also why Inditect give adb time to catch up as well with his Yes/No request commands. Batch files are from the DOS age, but reliable in its simplest form. However old DOS with current ADB crashes. Which is why you can't call ADB its self.
This script is in all honesty, a fast way to soft brick ANY device.
the OG commands, I.e copy n paste gave adb time to follow thru with the commands and report errors as they come.
My script and batch had to be slowed down (pauses) to provide debugging information.
Indirects script added yes/no pauses to allow again, for adb to keep up.
Batch files are raw, fast and as dumb as it sounds, furious. It's unrelenting to say the least.
By this batch being as raw as it is, and uncontrollable as it is, seems irresponsible for any dev to release.
Please don't take this as an insult but why let others take it 2 steps forward, just to release something that takes 5 steps back.
Just my 15 years of exp worth of 2 cents.
Click to expand...
Click to collapse
You can't just say "don't take this as an insult" and then post a deliberately insulting picture. Leave dude alone. I think all of your dresses look pretty, okay?
lol... so quick to jump all over someone when the shoes on the other foot... funny thing is it was ok when we had a temp root method, plus a 3 step rollback method, but yet we needed more.... now we have enough though?? what a place this has become
The script wont work right. Thats what its about.
Sent from my PC36100 using xda premium
First:
Warning! This is only for A70B/A70IT2 Honeycomb model, It won't work on Froyo model!
Here is a package that enables unofficially SDE menu in recovery and install a rooted stock firmware with busybox and SuperUser.Apk
Pre-Requisite:
- Adb must be enabled on tablet and PC driver+adb command must be working. You can test on pc with "adb shell", it should give you a '$' prompt. If you don't have this, first make it work. There are multiple links around to help if needed.
Instructions:
- Unzip files on your pc in adb.exe directory.
- Launch enable_sde.bat on your pc. It's better to do it in a cmd.exe window, you'll be able to copy-paste log here if anything goes wrong.
- Follow instructions in the cmd window. Basically, script reboots tablet multiple times, you have to press enter when tablet is completely booted each time.
- Congratulation, your device is sde enabled and has a rooted sde firmware. Please read below for more information.
Upgrades:
If you already installed a first version and enabled sde already, here is how to install new rooted firmware:
- Optional: flash updated stock firmware. I always recommend to match stock firmware, it avoids dalvik-cache rebuilds and bootloaders may have been updated in new firmwares.
- Boot rooted firmware. You should be running rooted firmware if you want upgrade script to work. To be sure of that, you should see SuperUser app in your apps menu.
- Unzip files on your pc in adb.exe directory
- Launch upgrade.bat (or upgrade.sh for linux)
- Tablet reboots at the end to rooted firmware and should be upgraded to new version.
SDE information:
1) What is SDE?
SDE (Special Developer Edition) is basically a dual boot mechanism. It allows us to dual boot Archos stock firmware and our custom ones.
2) How does it work ?
I won't give much details on how to use it, I should do a separate topic about this one someday. Until then, here is some basic information:
- At the end of this script, you are booted with sde firmware, superuser should be in your start menu and you should be root with adb or any root app.
- If you reboot or boot, press volume up while booting, it will display the dual boot menu. Select "Developer Edition", it will start the rooted build (check here point 9 to see how it looks).
- If you missed volume key or don't do anything during reboot, you will go back to unrooted stock firmware. You have to press the volume up key during boot to get the boot menu.
- Warning: booting stock firmware is harmless except that you will loose your SuperUser.apk preferences. As it's not part of stock firmware, Android clears it.
- You can boot straight to rooted firmware by deleting the stock firmware kernel in recovery. Check here, do point 4,5, and on screen 6, select "Remove Android Kernel". Make sure that you have properly working SDE firmware before doing that. If you want to re-enable back stock firmware, just flash it from recovery again.
Downloads:
3.2.80 can be downloaded here: Mirror 1 (Mediafire), Mirror 2 (Sendspace).
3.2.81 can be downloaded here: Mirror 1 (SendSpace) (bat fixed)
Sorry, Mediafire no longer let me upload without signup, if you know one good upload location without registration and allowing more than 200 MB, let me know.
*reserved*
Registered just to say thank you!
Worked like a charm, and no problems using the shell script (I run Arch Linux)
Keep up the good work!
Thanks
I mean real thanks
Sent from my ARCHOS 70it2 using xda premium
EDIT:
Beautiful man, beautiful. Works splendidly
Thanks again
LeTama
Have a beer or two on me, 84G89322WT2139701.
Thanks again for your Rom.
Hi mrew42,
Thanks a lot! Much appreciated!
Tomorrow, my 70b return at home
I testing that !
but my 70bit2 is with 3.2.81
Letama, can you may be make the same for 3.2.81?
Yes, it will come soon...
3.2.81 is up and instructions on first post updated if you upgrade.
Great
http://www.jbmm.fr/?p=27601
{
"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"
}
cajl said:
Great
Click to expand...
Click to collapse
Nice job! Thanks for the article on jbmm!
Thanks, will try it out soon.
Thanks letama, this is just what I wanted. Awsome work!
I think there is an error in upgrade.bat and enable_sde.bat for 3.2.81.
The line that reads:
adb push android_32.ext4.update /media/
should read:
adb push android_32.ext4.update /data/media/
Also, upgrade.bat is missing the line that says:
adb shell rm /data/local.prop
Keep up the good work and thanks again.
ColinTaylor said:
I think there is an error in upgrade.bat and enable_sde.bat for 3.2.81.
The line that reads:
adb push android_32.ext4.update /media/
should read:
adb push android_32.ext4.update /data/media/
Click to expand...
Click to collapse
Ah! Right! Thanks for pointing it, I'll fix that and re-upload when I find time to do it.
Also, upgrade.bat is missing the line that says:
adb shell rm /data/local.prop
Click to expand...
Click to collapse
Yes, this is normal, this one is only needed when enabling sde first time. local.prop is coming from temp root and won't be there anymore.
I finally had time to try it out tonight, all seemed to be installed fine, but I don't see the Superuser in the apps list... I can boot into developers fw menu though. Did I miss something or should I just try to reinstall the SDE again by running that bat file again?
No, as ColinTaylor said, there is a typo in script, you just need to push the ext4.update at root of storage.
Just type this command in the directory you unzipped the files:
Code:
adb push android_32.ext4.update /data/media/
then boot sde.
Hello
As i have read your post about how to root 3.2.81, the instructions seems to confuse me, but what do you mean by adb? im sorry im kinda new at this ,please let me know thanks!
hello, first of all thanks for your work.
I am having some problems with the upgrade file.
it says that it cannot stat 'zImage':no such file or directory
and secondly it cannot open the kernel file (no such file or directory) mkf lashimage failed.
could you please provide some help with this?
thanks!
lozano.markp said:
Hello
As i have read your post about how to root 3.2.81, the instructions seems to confuse me, but what do you mean by adb? im sorry im kinda new at this ,please let me know thanks!
Click to expand...
Click to collapse
adb is a developer tool from android sdk that let you execute commands on your tablet from your PC. You have to install android sdk to get it, you need to enable it on the tablet and have a proper driver.
Just about tried everything to root this and found this.
I tried this method on 9.30.1 and it worked for me
This root method was made for the Samsung Galaxy S4, But the OP says may work on others too
Has been confirmed to work on the Razr HD, Razr HD Maxx and the Razr M here and over at my post @ droidrzr.com
You do not need to install the samsung drivers.
Just the Moto drivers and make sure adb is working.
http://forum.xda-developers.com/showthread.php?t=2565758
Enjoy
All 3 msm8960 phones [xt907, xt925/6 & mb866] have always used the same low level exploits & this SHOULD be no different. Works on one, works on all.
BTW I never knew how to interpret the BL codes:
Device is LOCKED. Status Code: 0
Device is UNLOCKED. Status Code: 1
Device is LOCKED. Status Code: 2
Device is UNLOCKED. Status Code: 3
Root pics
{
"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"
}
KC, if this works, you'll be the man .....
I am FXZ'ing my M tester to give it a whirl as well. Will keep you posted.
Delete
aviwdoowks said:
Status 0 means no root!
I think the root check app is in error.
Have you created a folder in the root of the phone? Or used a root browser in /cache?
Click to expand...
Click to collapse
yes I have also loaded blurry rom on safestrap
So you did the process just as posted for the galaxy s4?
aviwdoowks said:
So you did the process just as posted for the galaxy s4?
Click to expand...
Click to collapse
yes
Confirmed to work on the M version 98.30.1 as well. Added a test folder to system to confirm as well.
livinginkaos said:
Confirmed to work on the M version 98.30.1 as well. Added a test folder to system to confirm as well.
Click to expand...
Click to collapse
Awesome
http://forum.xda-developers.com/showthread.php?p=49257686#post49257686
Are any timid?
http://forum.xda-developers.com/showthread.php?t=2602657
Rooted 98.18.94 XT907
kc6wke said:
Just about tried everything to root this and found this.
I tried this method on 9.30.1 and it worked for me
Try at your own risk
http://forum.xda-developers.com/showthread.php?t=2565758
Click to expand...
Click to collapse
I have been trying to root my phone since September 2013. I had given up and was reading some info on the possibility of using an AT&T sim in my Verizon phone on Droidrazr.com when I came across a post from yesterday that said "and just like that". Root is confirmed 100%. Thanks very much for the help. These two sites are invaluable.
P.S. I did not have to install the Samsung Drivers.
kc6wke said:
Just about tried everything to root this and found this.
I tried this method on 9.30.1 and it worked for me
Try at your own risk
http://forum.xda-developers.com/showthread.php?t=2565758
Click to expand...
Click to collapse
The referenced thread seems to be talking about Samsung devices. Are you saying this root method for Samsung works on a Motorola RAZR HD (xt926)?
I have a razr hd with unlocked bootloader and recently flashed the 9.30.1 update and lost root. I read somewhere that you can somehow copy the su binary back to the phone in one of the directories in the path using fastboot but I have no idea how to do that. I do have an unlocked bootloader if that helps. I also have a copy of the su and Superuser.apk files on my PC in my original motochopper folder.
chuckh1958 said:
The referenced thread seems to be talking about Samsung devices. Are you saying this root method for Samsung works on a Motorola RAZR HD (xt926)?
I have a razr hd with unlocked bootloader and recently flashed the 9.30.1 update and lost root. I read somewhere that you can somehow copy the su binary back to the phone in one of the directories in the path using fastboot but I have no idea how to do that. I do have an unlocked bootloader if that helps. I also have a copy of the su and Superuser.apk files on my PC in my original motochopper folder.
Click to expand...
Click to collapse
The op will update soon but it works as is on xt926 & 907.
http://forum.xda-developers.com/showpost.php?p=49288923&postcount=22
Ok. So after verifying adb works, I just unzip the saferoot.zip file, cd to the directory where I extracted it, and run install.bat? That simple?
Should I remove the old Superuser app (that no longer works) before running this?
chuckh1958 said:
Ok. So after verifying adb works, I just unzip the saferoot.zip file, cd to the directory where I extracted it, and run install.bat? That simple?
Should I remove the old Superuser app (that no longer works) before running this?
Click to expand...
Click to collapse
Shoot I missed u unlocked!
No need for this exploit. Flash su & you are done.
But now that you did it, yea delete the old su.
See my stickys for the su/root zip-flash from cwmr via matt's util.
I just tried this on a Razr HD XT926 running 9.18.94, android 4.1.2
Confirmed WORKING, at least for me. Got my root back yay!
Thanks for this OP
Worked
Amazing worked on Razr HD 9.30.1
Thought I'd never be able to get this phone rooter.
You have made my day!