Database Users

Unroot the vibrant

I want to root but want to be reassured I can unroot for warranty purposes.

In theory couldn't you just restore to factory settings?
Sent from my SGH-T959 using Tapatalk

JWhipple said:
In theory couldn't you just restore to factory settings?
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Restoring factory settings does not remove root.

Just open terminal on your computer and type
Code:
adb shell
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
That'll remove the components that rooting installs.
*obviously to use adb shell you'll need the SDK installed

mmm easy
Ahh, easiest root/unroot makes me happy

Xyber3364 said:
Ahh, easiest root/unroot makes me happy
Click to expand...
Click to collapse
Yeah, the Vibrant is ridiculously simple so far.

bahnburner said:
Just open terminal on your computer and type
Code:
adb shell
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
That'll remove the components that rooting installs.
*obviously to use adb shell you'll need the SDK installed
Click to expand...
Click to collapse
could you just use the terminal on the phone ?

Yeah, I just don't like BetterTerminal. For some reason it always gives me hell, and it's the only terminal emulator that allows for an on screen keyboard.
To do this in terminal on the phone:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su

bahnburner said:
Yeah, I just don't like BetterTerminal. For some reason it always gives me hell, and it's the only terminal emulator that allows for an on screen keyboard.
To do this in terminal on the phone:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
Click to expand...
Click to collapse
actually you can use any terminal and just hold the menu button to pull up the keyboard... it worked for anything i needed on the mt3g seems to still work on the vibrant but havent tested in terminal so whoever tries it out let us know

bahnburner said:
Yeah, I just don't like BetterTerminal. For some reason it always gives me hell, and it's the only terminal emulator that allows for an on screen keyboard.
To do this in terminal on the phone:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
Click to expand...
Click to collapse
skater4690 said:
actually you can use any terminal and just hold the menu button to pull up the keyboard... it worked for anything i needed on the mt3g seems to still work on the vibrant but havent tested in terminal so whoever tries it out let us know
Click to expand...
Click to collapse
Sweet, thanks guys. Im gonna root now. Even if the terminal on the Phone dont work, atleast I can install the drivers and go the adb route.. AWESOME..

skater4690 said:
actually you can use any terminal and just hold the menu button to pull up the keyboard... it worked for anything i needed on the mt3g seems to still work on the vibrant but havent tested in terminal so whoever tries it out let us know
Click to expand...
Click to collapse
Wouldn't hard resetting put those back even after deleting?

ok my phone is having hardware issues home key and search buttons are not working so i have to return my phone problem is that im rooted. i just downloaded terminal emulator and am trying to put that code in but its not working any advice

mx4life921 said:
ok my phone is having hardware issues home key and search buttons are not working so i have to return my phone problem is that im rooted. i just downloaded terminal emulator and am trying to put that code in but its not working any advice
Click to expand...
Click to collapse
Try hard resetting to make sure?
only thing I suggest is install the drivers on your pc and the sdk and do it that way.. I'd link ya to the instructions but I'm still trying to find this instructions myself....
Anyone got a link?

where can I find the terminal On my pc?

temperbad said:
where can I find the terminal On my pc?
Click to expand...
Click to collapse
press "Control+r"
type "cmd"
press enter

bahnburner said:
Yeah, I just don't like BetterTerminal. For some reason it always gives me hell, and it's the only terminal emulator that allows for an on screen keyboard.
To do this in terminal on the phone:
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
Click to expand...
Click to collapse
Good 'ol "Terminal Emulator" has a soft keyboard toggle as well, works just fine.
My only gripe is the Swype backspace doesn't work right in any of the terminal applications including connectbot so you have to change your input method first if you have any desire to use the backspace key... Original android one works ok.

bahnburner said:
press "Control+r"
type "cmd"
press enter
Click to expand...
Click to collapse
Ok so after opening that it and when I press SU it errors, says superuser error. Do I got to get it to recognize my device first somehow? I got the drivers installed and in cmd it recognizes my device... What does the line you enter the command got to say when I enter in the commands?

Quick question. I am rooted and going to exchange under warranty. Can I do a factory data reset without causing any problems? I thought I read where someone tried when they were rooted and it wouldnt boot after. Thanks

temperbad said:
Ok so after opening that it and when I press SU it errors, says superuser error. Do I got to get it to recognize my device first somehow? I got the drivers installed and in cmd it recognizes my device... What does the line you enter the command got to say when I enter in the commands?
Click to expand...
Click to collapse
In Windows it should look like this:
Code:
C:\Users\Bahnburner.MacbookPro>adb shell
$su
#
it may also include this, but don't worry about it if it doesn't:
Code:
* daemon not running. starting it now *
* daemon started successfully *
dashed said:
Quick question. I am rooted and going to exchange under warranty. Can I do a factory data reset without causing any problems? I thought I read where someone tried when they were rooted and it wouldnt boot after. Thanks
Click to expand...
Click to collapse
I have done a factory reset to solve a browser issue and had absolutely no problems, however, the phone will remain rooted. You will still have to manually delete Superuser.apk, su and busybox.

hopefully this will help when people want to unroot if the update won't work without unroot

[Q] s-on/s-off

hey all. anyone know if we can turn s-off on wildfire yet? kninda frustraiting... its root but not really root

bassmonkey said:
hey all. anyone know if we can turn s-off on wildfire yet? kninda frustraiting... its root but not really root
Click to expand...
Click to collapse
To me this is a 100% genuine "WTF?" statement... I don't get what you mean mate, please explain..

bassmonkey said:
hey all. anyone know if we can turn s-off on wildfire yet? kninda frustraiting... its root but not really root
Click to expand...
Click to collapse
Not yet till Alpharev v2 realesed
Sent from my HTC Legend

gyroing said:
Not yet till Alpharev v2 realesed
Sent from my HTC Legend
Click to expand...
Click to collapse
Thanks dude, I've just came from having a totally customized hero
N despite the screen rez I'm loving this phone but no access to system folder is pants
Sent from my HTC Wildfire using XDA App

niksakl said:
To me this is a 100% genuine "WTF?" statement... I don't get what you mean mate, please explain..
Click to expand...
Click to collapse
As far as I can tell its a new security thing HTC have added to the hboot, basically makes the system folder read only even with root (think that's correct??)
Sent from my HTC Wildfire using XDA App

bassmonkey said:
Thanks dude, I've just came from having a totally customized hero
N despite the screen rez I'm loving this phone but no access to system folder is pants
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
Well , it's not totally locked down. You can access it (Read and write) if you boot into recovery. Not the smoothest solution but it works. Also there is AUFS but i don't think i have gotten that to work at all. Maybe it needs to be enabled, haven't really checked but i boot into recovery when i need to change something.

You can change the /system permission with a terminal emulator as Better Terminal Pro on the phone or by the phone connected to your pc via
Code:
> adb shell
doing in both cases:
Code:
# chmod -R 777 /system
when you restart the phone, /system will be reset to the original 755 permissions.

thanks for the response guys
71baker said:
Well , it's not totally locked down. You can access it (Read and write) if you boot into recovery. Not the smoothest solution but it works. Also there is AUFS but i don't think i have gotten that to work at all. Maybe it needs to be enabled, haven't really checked but i boot into recovery when i need to change something.
Click to expand...
Click to collapse
how do you do it through recovery? im guessing thatd be with adb?
Tetractys said:
You can change the /system permission with a terminal emulator as Better Terminal Pro on the phone or by the phone connected to your pc via
Code:
> adb shell
doing in both cases:
Code:
# chmod -R 777 /system
when you restart the phone, /system will be reset to the original 755 permissions.
Click to expand...
Click to collapse
in terminal i entered su
chmod -R777/system
which then gave me; usage: chmod <mode> <file>
i then entered; /system and got permission denied??

bassmonkey said:
thanks for the response guys
how do you do it through recovery? im guessing thatd be with adb?
in terminal i entered su
chmod -R777/system
which then gave me; usage: chmod <mode> <file>
i then entered; /system and got permission denied??
Click to expand...
Click to collapse
If you have written the command exactly as you report is obvious that the os return an error. try to write as i did... (with blanks in between)
of course your phone had to be passed the Unrevoked 3.21 procedure!
http://forum.xda-developers.com/forumdisplay.php?f=701
Anyway if you are not very much concerned in linux shell commands, i would suggest you to wait another more automatic method.

Tetractys said:
If you have written the command exactly as you report is obvious that the os return an error. try to write as i did... (with blanks in between)
of course your phone had to be passed the Unrevoked 3.21 procedure!
http://forum.xda-developers.com/forumdisplay.php?f=701
Anyway if you are not very much concerned in linux shell commands, i would suggest you to wait another more automatic method.
Click to expand...
Click to collapse
lol.'not concerned' very diplomatic yeah, kind of a windoze boy n therefore not really up on linux.
i did root with 3.21 and i tried the chmod command with all the spaces and terminal just gave me 'bad mode' (it also gave me bad mode when i tried adb) so i tried as i posted. bummer but nevermind, come on alpharev 2

71baker said:
Also there is AUFS but i don't think i have gotten that to work at all. Maybe it needs to be enabled, haven't really checked but i boot into recovery when i need to change something.
Click to expand...
Click to collapse
You can enable AUFS in Jacob's latest kernel by typing "aufs --enable" in a terminal emulator app in android, and then reboot the phone.

Cant reboot via terminal.

Hey gius Im trying to reboot via terminal but I cant seem to get it to work. Keep getting "Nor premited!" error.
I tried with both commands and am using a rooted G2 with stock rom.
su reboot - same error
su reboot now- same error.
any ideas? I know there are apps to do it but why is it not working via terminal?

Any reason why you can't just hold the button in and press reboot?

$ su -
# shutdown -r now
it shoulda outta do it then
for just turning off:
# shutdown -h now

ohgood said:
$ su -
# shutdown -r now
it shoulda outta do it then
for just turning off:
# shutdown -h now
Click to expand...
Click to collapse
Hmm Tried that right now and it says shutdown: not found.

I'm getting the same error! I only tried terminal when Gscript Lite gave me a "not permited". Don't know if it's related, but terminal always starts with $ rather than #. The weirdest part is that it DID work through ADB.
I'm S-OFF, root verified. Has anyone else seen this? I've been searching the forums for a while now...

Try
$ su
# busybox killall system_server
Sent from my HTC Vision using Tapatalk

I get busybox: not found, but since I initially thought it was a busybox issue, I have already updated busybox. Per Titanium Backup, I have version 1.18.4-Titanium. Could it be the titanium busybox?
PanCubano said:
Try
$ su
# busybox killall system_server
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse

Having a similar problem with rebooting from terminal "not permitted", I am using Virtuous Unity,and my phone is rooted etc,anybody having any joy getting reboot from terminal working?double checked busybox permissions and are RWX so whats going on???????????????????

Ok restored my nandroid backup of CM7 and reboot from terminal works so for the problem is connected to Virtuous Unity.

got it ! command is:
$su
#reboot -f
hay presto!!!!!!!
EDIT BUT when using a gscripts reboot doesnt work???????????
I have to use the command busybox killall system_server in the script????
I dont get it,what is the problem !!!!!!!!!!!!!!!!

xsteven77x said:
Any reason why you can't just hold the button in and press reboot?
Click to expand...
Click to collapse
This.
Sent from Space using Tapatalk Pro

I know I could, just trying to understand the android system,how it works and why the reboot command works on CM 7 but not on Virtuous Unity, the search for a solution continues...........................

bombadier said:
I know I could, just trying to understand the android system,how it works and why the reboot command works on CM 7 but not on Virtuous Unity, the search for a solution continues...........................
Click to expand...
Click to collapse
I had the same problem on rooted stock, and it has since gone away since I put on CM7. The reason is that it is not just reboot that didn't work. Almost no scripts would run either, and those can be quite helpful. I believe it's a symptom of something larger, but I can't quite place my finger on what.

mjasmin said:
I had the same problem on rooted stock, and it has since gone away since I put on CM7. The reason is that it is not just reboot that didn't work. Almost no scripts would run either, and those can be quite helpful. I believe it's a symptom of something larger, but I can't quite place my finger on what.
Click to expand...
Click to collapse
I can get reboot -f which works but I have to use busybox killall_server to get it work from a script,have tried a few things but literature on the subject is pretty sparse,its not so important but would still like to understand the whole process, but I seem to be in the minority trying to solve this.......
Why I have to use reboot -f on Unity where reboot will do on CM is a mystery,have found a file that seems to define functions on Unity(virtuous-functions.sh), have tried adding REBOOT="$BUSYBOX reboot" to this but doesn't help.
reboot -f it is then!

[Q] EVGA Tegra Note 7 root?

EDIT:
Go here to root your Tegra Note 7: https://github.com/linux-shield/shield-root/blob/master/README.md (thanks to CampGareth for finding the link).
I have tested this, it works with no bloatware, only installs SuperSu.
---------
Hey guys, I got my new Tegra Note 7 last night and I've been trying to get it rooted, but I keep running into trouble.
First of all, I DO NOT want to use some shady Chinese software that installs a bunch of bloat on both my tablet and PC just to get SuperSu going, I've tried that method and had to reset the tablet to get rid of all the crap it installs (and it didn't even seem to root anyway).
Now I'm trying the manual method from here: http://pan.baidu.com/wap/link?uk=3073396937&shareid=3129426036&third=0
Which, again, is Chinese but at least I can see what it's doing since I'm issuing ADB commands, and supposedly it has worked for others on this forum.
Now, I get to step 3 on the included PDF which says to boot an insecure bootloader image with "fastboot boot tegranote_insecure_boot.img", I do this and the tablet screen flashes a few times and reboots to android.
I get to the next step which says to open an adb shell, and do "/sbin/rootsh +p" to get a temp root shell, and this is where I get stuck. Instead of getting a root shell I get the message "/system/bin/sh: /sbin/rootsh: not found". Does anyone have suggestions?
By the way we really need a Tegra Note 7 subforum here at XDA, if the mods could add it that would be great.

dark42 said:
Hey guys, I got my new Tegra Note 7 last night and I've been trying to get it rooted, but I keep running into trouble.
First of all, I DO NOT want to use some shady Chinese software that installs a bunch of bloat on both my tablet and PC just to get SuperSu going, I've tried that method and had to reset the tablet to get rid of all the crap it installs (and it didn't even seem to root anyway).
Now I'm trying the manual method from here: http://pan.baidu.com/wap/link?uk=3073396937&shareid=3129426036&third=0
Which, again, is Chinese but at least I can see what it's doing since I'm issuing ADB commands, and supposedly it has worked for others on this forum.
Now, I get to step 3 on the included PDF which says to boot an insecure bootloader image with "fastboot boot tegranote_insecure_boot.img", I do this and the tablet screen flashes a few times and reboots to android.
I get to the next step which says to open an adb shell, and do "/sbin/rootsh +p" to get a temp root shell, and this is where I get stuck. Instead of getting a root shell I get the message "/system/bin/sh: /sbin/rootsh: not found". Does anyone have suggestions?
By the way we really need a Tegra Note 7 subforum here at XDA, if the mods could add it that would be great.
Click to expand...
Click to collapse
I would recommend the following procedure:
1. Download the root_tool_v2.zip attached to this post
2. Unzip the contents the root_tool_v2.zip to a directory
3. Run the following commands from your ADB and Fastboot directory:
Code:
adb reboot bootloader
fastboot boot tegranote_insecure_v2.img
4. Once your device finishes booting the insecure boot.img (Your device's screen will blink several times and then boot into Android) run the following commands:
Code:
adb shell
mount -o remount,rw /dev/block/mmcblk0p5 /system
exit
adb push su /system/xbin/su
adb push Superuser.apk /system/app/Superuser.apk
adb shell
chmod 6755 /system/xbin/su
chmod 644 /system/app/Superuser.apk
mount -o remount,ro /dev/block/mmcblk0p5 /system
exit
adb reboot
5. You should now have Superuser installed and have root access.
What I did was I modified the boot.img provided to be insecure and use an insecure adbd binary to allow a root shell when booted from which can then be used to setup Superuser and su binary access. Let me know how this goes for you and if you have any questions .

Wow, thanks for the help! Unfortunately your attachment seems to be corrupt, I can't decompress the archive. I'm using 7-zip btw. The forum says your attachment is 7.19MB but when downloaded it's only 160KB.
If you can re-upload it I will give it a go.

a reup of the file would be much appreciated! :good:
PS
i have a batch file to expedite the process.

dark42 said:
Wow, thanks for the help! Unfortunately your attachment seems to be corrupt, I can't decompress the archive. I'm using 7-zip btw. The forum says your attachment is 7.19MB but when downloaded it's only 160KB.
If you can re-upload it I will give it a go.
Click to expand...
Click to collapse
dergezero said:
a reup of the file would be much appreciated! :good:
PS
i have a batch file to expedite the process.
Click to expand...
Click to collapse
Re-uploaded the file for you guys let me know how it goes for you .

Awesome your new package downloaded fine.
However I'm still not getting root, I got to step 4 and when I open an adb shell I don't have permissions to do the next command.
The exact error message:
[email protected]:/ mount -o remount,rw /dev/block/mmcblk0p5 /system
mount -o remount,rw /dev/block/mmcblk0p5 /system
mount: Operation not permitted
So I guess the insecure boot image didn't work right. I should mention that I am using the latest Tegra Note firmware, I don't know if that makes a difference though. Any ideas?
Thanks for your help so far.

do you guys have a copy of the drivers for the tablet? mine only seems to work for storage.
update: got drivers working.

dergezero said:
do you guys have a copy of the drivers for the tablet? mine only seems to work for storage.
update: got drivers working.
Click to expand...
Click to collapse
I used Universal Naked Driver 0.73, I just manually installed the driver for the Nvidia Shield, thinking it would work, and it does!
Does shimp208's root image work for you, dergezero?

dark42 said:
I used Universal Naked Driver 0.73, I just manually installed the driver for the Nvidia Shield, thinking it would work, and it does!
Does shimp208's root image work for you, dergezero?
Click to expand...
Click to collapse
no, it just reboots. neither is working. im going to see if any one can give us a dump of their img that already works to be rooted. i tried that Chinese method and its really annoying and i dont get root on any computer i try it on.

Hey guys I am in the process of creating a new boot image that uses a different method for gaining root access and will upload that once I finish it.

shimp208 said:
Hey guys I am in the process of creating a new boot image that uses a different method for gaining root access and will upload that once I finish it.
Click to expand...
Click to collapse
:good: Awesome man, good luck! Eager to try it when you post it! :fingers-crossed:

dark42 said:
:good: Awesome man, good luck! Eager to try it when you post it! :fingers-crossed:
Click to expand...
Click to collapse
I agree, with the amount of malware that is in the chinese root tools, it makes me nervous to use the one the OP posted.
Brew

I wonder if someone would be able to port Clockworkmod Recovery to the TN7 eventually. The bootloader on this device is factory unlocked so it should be simple enough. Unfortunately I'm not a good enough programmer to get this done.
If we had Clockworkmod then rooting would be as easy as flashing the SuperSU .zip from the SD.

I have updated my original post with the rooting instructions to include a new insecure boot method follow the same instructions as before just use the new boot.img I uploaded to that post. Credit to teknoraver for the insecure adbd binary.

shimp208 said:
I have updated my original post with the rooting instructions to include a new insecure boot method follow the same instructions as before just use the new boot.img I uploaded to that post. Credit to teknoraver for the insecure adbd binary.
Click to expand...
Click to collapse
I tried your V2 image, still getting permission errors when doing "mount -o remount,rw /dev/block/mmcblk0p5 /system", what am I doing wrong?

dark42 said:
I tried your V2 image, still getting permission errors when doing "mount -o remount,rw /dev/block/mmcblk0p5 /system", what am I doing wrong?
Click to expand...
Click to collapse
When you boot the image and then type ADB shell do you get a root shell ([email protected]:/ #) or just a regular shell ([email protected]:/ $)?

Amazing
Nice to see you working on a different method of root... I am sorry to those who feel that the method I posted is getting negative reviews just wanted to throw something out there for people... however, I do feel much better with Shrimp208 working on a better root method I really wish we could get a forum going..

I used the Chinese root tool and all seems fine on my Tegra note
Sent from my TegraNote-P1640 using Tapatalk

shimp208 said:
When you boot the image and then type ADB shell do you get a root shell ([email protected]:/ #) or just a regular shell ([email protected]:/ $)?
Click to expand...
Click to collapse
Just a regular shell with $. Doesn't look like I get temp root permissions after running the tegranote_insecure_v2.img.
If it matters, I'm on the latest Stock ROM (4.2.2/JDQ39.13155_268.1942) and I'm using Universal Naked Driver 0.73 for the Shield, which works with this device. Maybe I need to use a different driver?

Toyeboy said:
I used the Chinese root tool and all seems fine on my Tegra note
Sent from my TegraNote-P1640 using Tapatalk
Click to expand...
Click to collapse
yeah it works but you dont really know what was installed on ur phone or on your pc. 3 apps are installed on your phone and a few reg changes on ur pc can be detrimental. and its all bloatware

Unbrick kfsowi

Alpha Release of Gran PC's Restore Tool
https://peniscorp.com/KindleRoot_dist_windows_0.1.zip

*reserverd*

kyleberry.graphics said:
I have sucessfully unbricked a bootlooped (no adb) kindle KFSOWI. Guide to follow tomorrow
Click to expand...
Click to collapse
lvl 1 - kill the kindle - completed
loading....
lvl 2 - kernel firewall - started
great news

mint-an said:
lvl 1 - kill the kindle - completed
loading....
lvl 2 - kernel firewall - started
great news
Click to expand...
Click to collapse
For the discerning reader, the reason i havent posted a solution yet is that while i managed to get the device to boot, the image resized the partition to the size of the image so the /system cannot hold ANY additional...ANYTHING.
fastboot will not write a sparse image so im trying to figure out how to push the stock 11.3.2.1 .bin and reroot

kyleberry.graphics said:
For the discerning reader, the reason i havent posted a solution yet is that while i managed to get the device to boot, the image resized the partition to the size of the image so the /system cannot hold ANY additional...ANYTHING.
fastboot will not write a sparse image so im trying to figure out how to push the stock 11.3.2.1 .bin and reroot
Click to expand...
Click to collapse
yeah i saw your g+ post about it, posted my thought to but I don't thing they are going to help you

kyleberry.graphics said:
a better guide will follow, but for now, download and unzip this image:
Click to expand...
Click to collapse
I cannot download the tar.gz file from google. It brings up a network error.

j.jacobsen said:
I cannot download the tar.gz file from google. It brings up a network error.
Click to expand...
Click to collapse
Works here.
Thanks to all the devs here for making this possible...

micro17 said:
Works here.
Thanks to all the devs here for making this possible...
Click to expand...
Click to collapse
Working on an automated script now =)

kyleberry.graphics said:
Working on an automated script now =)
Click to expand...
Click to collapse
Restore tool uploading now. see first post..

kyleberry.graphics said:
Restore tool uploading now. see first post..
Click to expand...
Click to collapse
gonna try this now man... fingers crossed
---------- Post added at 10:04 AM ---------- Previous post was at 09:42 AM ----------
PHP:
kyleberry.graphics said:
Restore tool uploading now. see first post..
Click to expand...
Click to collapse
i ran your runme.bat. everything went fine but when i booted it up, it got stuck at the boot logo again but instead of the one with the orange logo i got the grey dull one... please help

davethebrave14 said:
gonna try this now man... fingers crossed
---------- Post added at 10:04 AM ---------- Previous post was at 09:42 AM ----------
PHP:
i ran your runme.bat. everything went fine but when i booted it up, it got stuck at the boot logo again but instead of the one with the orange logo i got the grey dull one... please help
Click to expand...
Click to collapse
The problem is the new.img it worked for me because I dint wipe any data so I kept su. Im trying to get a rooted system.img today
Sent from my SCH-R970 using xda app-developers app

hope you'll get the rooted system.img soon!
So i could try to get my messed up kfsowi back to stock... then root it again.

ikarugaski said:
hope you'll get the rooted system.img soon!
So i could try to get my messed up kfsowi back to stock... then root it again.
Click to expand...
Click to collapse
A new all-in-one program with a user interface is being designed as we speak (but not by myself) =)
Sent from my KFSOWI using xda app-developers app

That sounds gorgeous! So show it to me please. :highfive:

ikarugaski said:
That sounds gorgeous! So show it to me please. :highfive:
Click to expand...
Click to collapse
https://plus.google.com/communities/115612726860884592519

Hello,
by mistake, i flashed the files for KFHD 2012 (Tate).
During my insuccessful operation, i also wiped the cache of the kindle.
I think that's the reason, why the script does not work.
Are there any news about your Factory Restore Tool and a rooted system.img?
Thank you.

Thanks kyleberry for the link! Then i'll have to wait for Gran PC's tool. Hope for a release soon.

kyleberry.graphics said:
https://plus.google.com/communities/115612726860884592519
Click to expand...
Click to collapse
Thanks a bunch for this.
the tool didnt do it, the timing of getting adb to work seems to me very difficult if you are booting with a fastboot cable , and then want to boot to the mini system img.
BUT....
if you let the tool install the minisystem.img
and then can get adb access , the following post on the google group got me back to stock
How to reinstall FireOS
Botched your /system partition beyond recognition? Everything is broken? Dropped your #Kindle in a sea of piss and need to RMA it? Fear not! You can just reinstall FireOS and get it looking just as if we had never touched it!
First of all, you'll have to root your tablet. I'm assuming you know how to do this!
Once that's done, put this file -- https://s3.amazonaws.com/kindle-fire-updates/update-kindle-11.3.1.0_user_310084920.bin -- in /sdcard/ (you can use adb push).
Then run these commands:
adb shell
su
[email protected]:/# cp /sdcard/update-kindle-11.3.1.0_user_310084920.bin /cache/update.zip
[email protected]:/# echo --update_package=/cache/update.zip > /cache/recovery/command
[email protected]:/# exit
[email protected]:/$ exit
adb reboot recovery
If everything went well, you should see the 'installing update' screen -- and once you're booted, we're back to stock! We did it!!!!!!
I did it slightly differently, I just renamed the bin on my pc first, and adb pushed it to /cache
I had to mount rootfs for r/w to do the adb push into /cache
adb shell
su
mount -o rw,remount rootfs /
chmod 777 /cache

mikeataol said:
Thanks a bunch for this.
the tool didnt do it, the timing of getting adb to work seems to me very difficult if you are booting with a fastboot cable , and then want to boot to the mini system img.
BUT....
if you let the tool install the minisystem.img
and then can get adb access , the following post on the google group got me back to stock
How to reinstall FireOS
Botched your /system partition beyond recognition? Everything is broken? Dropped your #Kindle in a sea of piss and need to RMA it? Fear not! You can just reinstall FireOS and get it looking just as if we had never touched it!
First of all, you'll have to root your tablet. I'm assuming you know how to do this!
Once that's done, put this file -- https://s3.amazonaws.com/kindle-fire-updates/update-kindle-11.3.1.0_user_310084920.bin -- in /sdcard/ (you can use adb push).
Then run these commands:
adb shell
su
[email protected]:/# cp /sdcard/update-kindle-11.3.1.0_user_310084920.bin /cache/update.zip
[email protected]:/# echo --update_package=/cache/update.zip > /cache/recovery/command
[email protected]:/# exit
[email protected]:/$ exit
adb reboot recovery
If everything went well, you should see the 'installing update' screen -- and once you're booted, we're back to stock! We did it!!!!!!
I did it slightly differently, I just renamed the bin on my pc first, and adb pushed it to /cache
I had to mount rootfs for r/w to do the adb push into /cache
adb shell
su
mount -o rw,remount rootfs /
chmod 777 /cache
Click to expand...
Click to collapse
Yeah the tool pretty much does just that (the steps on my guide, not your chmod shenanigans.. although that's a nice idea!)
Also, if you're gonna use the tool, please use the latest version (@kyleberry.graphics, update OP please):
https://peniscorp.com/KindleRoot_dist_windows_0.1.1.zip

Gran PC said:
Yeah the tool pretty much does just that (the steps on my guide, not your chmod shenanigans.. although that's a nice idea!)
Also, if you're gonna use the tool, please use the latest version (@kyleberry.graphics, update OP please):
https://peniscorp.com/KindleRoot_dist_windows_0.1.1.zip
Click to expand...
Click to collapse
can you help please I have run the tool everything went fine but when I boot kindle ijust get grey kindle writing still or if I plug fastboot cable in I get fastboot still nothing has chaned kindle still stuck at kindle writing am I ding something wrong what gives can you help me many thanks