I've been trying to fix my kindle fire for a while now. My ultimate problem is that my build.prop is not in my /system/ but I have been trying to push a replacement build.prop to that directory to no avail. It looks like I have superuser installed. Superuser.apk is in system/app/ and there are a few SU directories around my file system.
My problem is that even though I have SU in my file system, I am not getting the correct permissions when accessing the KF through adb. Whenever I type in su it says permission denied. Similarly, whenever I try to change the permissions for /system/ I am denied as well. Whenever I type in su, it says "segementation fault".
It seems to me that there are three possibilities:
1. I somehow have the superuser files in place but the SU program itself is not installed.
2. SU is installed but because I can't fully boot up my KF, I can't give ADB Root access through SU because I can't pull up the "allow access" dialog box.
3. Something stupd like I"m trying the wrong commands.
Maybe your kindle auto updated and broke root? But if you've already updated and re-rooted I'm not sure what the issue would be.
Sent from my Nexus S 4G using XDA App
hmmm...I think a main thing I need to know for sure before I continue is if my phone is even rooted for sure. I have the superuser.apk in system/app. I don't have anything in data/local. I have a SU directory in a couple places. Is there any way for ADB to recognize if a phone is rooted (perhaps if the file system is set up a current way?) without having access to root priveledges itself?
Same here, BurritoRoot, I've tried this on both Linux/Mac, but either way, I can never get su to work so my Kindle can be r/w.
Maybe try
adb shell
$su
If $ changes to # you have root.
When installing su check the file permissions on the directory as well.
Sent from my Kindle Fire using Tapatalk
just a try:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
what's the answer ?
if the response is not a failure you should have r/w
b63 said:
just a try:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
what's the answer ?
if the response is not a failure you should have r/w
Click to expand...
Click to collapse
That worked, thank you!
---------- Post added at 02:37 AM ---------- Previous post was at 02:29 AM ----------
But then I lose them after a reboot.
---------- Post added at 02:44 AM ---------- Previous post was at 02:37 AM ----------
$su doesn't give me a # anymore either.
Jessical said:
That worked, thank you!
---------- Post added at 02:37 AM ---------- Previous post was at 02:29 AM ----------
But then I lose them after a reboot.
---------- Post added at 02:44 AM ---------- Previous post was at 02:37 AM ----------
$su doesn't give me a # anymore either.
Click to expand...
Click to collapse
that command only remounts the system partition r/w - not permanent !
but after issuing the comand:
you can copy files, change permission or whatever
you can also run kfu to permantly root with superuser
Fixxxxxxxxxx!
http://forum.xda-developers.com/showthread.php?p=21034648#post21034648
That thread I started has the fix for your issue
taseedorf said:
http://forum.xda-developers.com/showthread.php?p=21034648#post21034648
That thread I started has the fix for your issue
Click to expand...
Click to collapse
It just stalls at:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
downloading 'boot.img'...
Then nothing.
Did you download the image file? You can just renamed the command and use the twrp from fire utility recovery directory
taseedorf said:
Did you download the image file? You can just renamed the command and use the twrp from fire utility recovery directory
Click to expand...
Click to collapse
How would I do that? I downloaded twrp-blaze-2.0.0RC0.img
I have used the terminal in the past, even compiled stuff like Chrome OS, but I don't know anything except the stuff that people put in the instructions...
Where is the boot.img itself coming from?
Related
AndroidPolice has the downloads and instructions for a new method of rooting. Just tested it, it *does* in fact work.
You will need ADB access (which, if you've rooted before, you probably already have).
I can confirm this works.
Is there any reason to do this if we are still rooted and have the secured rooted ROM installed? Should I wait until/if Amazon pushes the updated on top of my rooted 6.2.1?
Noob questions: Assume that the app goes on the KF of course. Where do the Superuser files get placed? Already have Superuser on the KF from previous root so can I skip this step?
Thanks!
cant find the drivers for my kindle??????? need help
i keep getting devce not found.....
movieaddict said:
cant find the drivers for my kindle??????? need help
i keep getting devce not found.....
Click to expand...
Click to collapse
I am not sure if we are talking about the same thing but I think they are included in the Kindle Fire Utility.
Masssy said:
I am not sure if we are talking about the same thing but I think they are included in the Kindle Fire Utility.
Click to expand...
Click to collapse
run install_drivers.bat from Kindle Fire Utility 0.6
Nice. Just regain root for 6.2.1.
did that , nothing
Not working here. Noticed that when I hit Root on the new app on the KF, I get this info which was not in the directions. Anyone else? Should these steps be done and in what sequence combined with the published instructions?
Final Steps
On your computer run the following commands:
adb kill-server
adb root
adb shell
Enjoy.
Hellcat6 said:
Not working here. Noticed that when I hit Root on the new app on the KF, I get this info which was not in the directions. Anyone else? Should these steps be done and in what sequence combined with the published instructions?
Final Steps
On your computer run the following commands:
adb kill-server
adb root
adb shell
Enjoy.
Click to expand...
Click to collapse
only one not in the instructiosn was adb kill-server and its not really needed.
adb root <-- what you likely missed
Root was made (I guess...).
But I still can't install the market. Because I can't mount system to R/W (with root manager or kindle utility).
Is it normal? :/
Cholo981 said:
Root was made (I guess...).
But I still can't install the market. Because I can't mount system to R/W (with root manager or kindle utility).
Is it normal? :/
Click to expand...
Click to collapse
root explorer mounts the system in r/w just fine.
this root works as advertised
ota rootkeeper still works for a temp unroot to watch amazon video.
as far as i can tell everything is the same except we're using superuser app so you have to allow each app permission, it's the only real change i can see
---------- Post added at 07:43 PM ---------- Previous post was at 07:43 PM ----------
jcase said:
only one not in the instructiosn was adb kill-server and its not really needed.
adb root <-- what you likely missed
Click to expand...
Click to collapse
i needed to use the kill-server command to get my computer to pick up the kindle after the update... others may as well so it's good info
screwyluie said:
root explorer mounts the system in r/w just fine.
this root works as advertised
ota rootkeeper still works for a temp unroot to watch amazon video.
as far as i can tell everything is the same except we're using superuser app so you have to allow each app permission, it's the only real change i can see
---------- Post added at 07:43 PM ---------- Previous post was at 07:43 PM ----------
i needed to use the kill-server command to get my computer to pick up the kindle after the update... others may as well so it's good info
Click to expand...
Click to collapse
Thanks for the suggestion re: OTA Rootkeeper! Rooted earlier today, but had trouble unrooting to watch videos, and now that's solved!
I haven't got my fire yet but these instructions don't seem very clear; do I have to keep the tablet connected to the PC at all times? Or do I execute the sudo app on the tablet, and then connect it to the PC so I can run the adb commands?
screwyluie said:
root explorer mounts the system in r/w just fine.
Click to expand...
Click to collapse
I meant root explorer (I wrote root manager indeed).
If I click on the "mount R/W" button, it doesn't do anything. :/
EDIT: Done. I had to push vending.apk by adb... dunno why.
jcase said:
only one not in the instructiosn was adb kill-server and its not really needed.
adb root <-- what you likely missed
Click to expand...
Click to collapse
Working now! Figured out that when installing the script in ADB from the directions, I was not leaving a space before each instance of "/system". Duh. Got Market working again as well. Thanks Developers!
Hellcat6 said:
Not working here. Noticed that when I hit Root on the new app on the KF, I get this info which was not in the directions. Anyone else? Should these steps be done and in what sequence combined with the published instructions?
Final Steps
On your computer run the following commands:
adb kill-server
adb root
adb shell
Enjoy.
Click to expand...
Click to collapse
You need to finish the job with these steps (taken from the androidpolice post):
Code:
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb install com.noshufou.android.su-1.apk
adb reboot
Help! I'm stuck at this step:
adb install com.noshufou.android.su-1.apk
The prompt says it can't find the file. What am I missing?
Thanks!
---------- Post added at 04:47 PM ---------- Previous post was at 04:01 PM ----------
I think I figure it out. The Fire is rooted again. I just need to fiddle with OTA Rootkeeper to be able to watch video streaming again.
Thank you for this thread.
I can run all the steps i just gotta be able to remove the original superuser app that i had before this one. Can someone please tell me how to go about this.
hey guys I removed some systemapps and now I cant install the new row update. can some one please upload a titanium backup
thanks
titanium backup won't work for system apps. you will need a system dump. which apps do you need? i have a dump but i won't upload the whole dump cause its about 1 gb.
ok. thanks for the quick reply. im not sure but it sholud only be the music app. it would be great if you could upload it.
just unpack it and copy both files into the /system/app folder with i.e. rootexplorer etc.
here i uploaded nearly the whole dump:
System Dump
i am the same don't know how to do now.
---------- Post added at 06:11 PM ---------- Previous post was at 06:08 PM ----------
@bananenlarry
I delete some app after root,then I unroot for some reason.
I can't not get root again,and also can not update OTA2 because missing APP.
waht can I do now?
@feskey
how did you unroot? did you delete superuser.apk from /system/app? then download Superuser from market again. because the su file from /system/xbin/ should still be there.
@bananenlarry
Unroot by following command.Su was clean up.
Instructions
1. Follow instructions to set up ADB.
2-Run "adb shell" from a command prompt.
3-In the ADB shell, type the following commands:
su
(this will cause a prompt to come up on the phone asking you to grant root permissions, accept this)
Then, back in ADB shell:
mount -o rw,remount /dev/block/system /system
rm /system/app/Superuser.apk
rm /system/xbin/su
rm /system/bin/su
omg you really unrooted your device thought you just deleted the superuser.apk. i don't know exactly how the root exploit works but as i know it uses a lenovo app to do so. if you also deleted that app, root isn't possible in your case. you will have to wait until there will be another method for rooting.
So was helping someone flash ClockworkMod via ADB in another thread, just thought if I made a topic for it, everyone can see it so if people have any issues they can always use this method instead.
Anyway, here are the instructions:
The 'flash_image' is within the attached zip file! Use the file within the zip file, NOT the zip file itself
The 'recovery.img' is your chosen recovery file, get this off ClockworkMods website or if you have a copy use that. Then when flashing the recovery image where ever it says 'recovery.img' replace that with the name of the recovery file.
Put the recovery image and the flash_image on the root of your C drive.
So,
(make sure you're in the command prompt and have changed directory to where the adb file is)
adb push c:\flash_image /sdcard/
adb push c:\recovery.img /sdcard/
adb shell
su
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img
It has now been flashed successfully
Hope this is of use to some people
Thanks! Very helpful.
varsaljr said:
Thanks! Very helpful.
Click to expand...
Click to collapse
As repeated in many places, press the thanks button instead of posting thanks
Hello, when i enter abd shell, then su.
I get acces denied..
what to do? :O
MrKiller2010 said:
Hello, when i enter abd shell, then su.
I get acces denied..
what to do? :O
Click to expand...
Click to collapse
u rooted and have superuser on your phone??
No i dont some one told me to do this cause my screen freezes when im trying to root it. Chek the How to root your blade.
Sent from my ZTE-BLADE using xda premium
You must be rooted for this, root using z4root or something
Sent from my ZTE-BLADE using Tapatalk 2
MrKiller2010 said:
No i dont some one told me to do this cause my screen freezes when im trying to root it. Chek the How to root your blade.
Sent from my ZTE-BLADE using xda premium
Click to expand...
Click to collapse
Dude i didn't know u weren't rooted yet. U don't need to use adb to root. Just Google z4root modaco and click on the first link. Install z4root and permanent root it. Don't forget to install rom manager and flash cwm from within it
Oh, well z4root doesn't work for me cause i got 2.3.5 i heard that the only way to root my blade is this: http://forum.xda-developers.com/showthread.php?t=1319257
and that doesn't work, it freezes when i enter the command "adb reboot bootloader" it reboots and stay on the ZTE logo and freezes. :S
MrKiller2010 said:
Oh, well z4root doesn't work for me cause i got 2.3.5 i heard that the only way to root my blade is this: http://forum.xda-developers.com/showthread.php?t=1319257
and that doesn't work, it freezes when i enter the command "adb reboot bootloader" it reboots and stay on the ZTE logo and freezes. :S
Click to expand...
Click to collapse
That's what it is supposed to do. That's it in fastboot mode. You need to go on to the next step at that point.
Well when i enter next command nothing happends.
Sent from my ZTE-BLADE using xda premium
matt4321 said:
You must be rooted for this, root using z4root or something
Sent from my ZTE-BLADE using Tapatalk 2
Click to expand...
Click to collapse
So what's the point in doing it?
Just install rom manager & use that instead.
---------- Post added at 04:17 PM ---------- Previous post was at 04:16 PM ----------
MrKiller2010 said:
Well when i enter next command nothing happends.
Sent from my ZTE-BLADE using xda premium
Click to expand...
Click to collapse
You need to install drivers for fastboot if you use Windows. Sometimes you might need to unplug the usb, then plug it back in again & try fastboot again.
It should at least give an error.
wbaw said:
So what's the point in doing it?
Just install rom manager & use that instead.
Click to expand...
Click to collapse
What's the point in using fastboot to flash clockworkmod, it's just another way of doing it, some may prefer other ways (yeah via rom manager is a lot easier i know) but spread the knowledge, may be of use to some people.
matt4321 said:
What's the point in using fastboot to flash clockworkmod, it's just another way of doing it, some may prefer other ways (yeah via rom manager is a lot easier i know) but spread the knowledge, may be of use to some people.
Click to expand...
Click to collapse
You don't need your phone to be rooted to use fastboot, it's a method for new stock roms that have all the common root exploits fixed.
So, what's the point in this method when using Rom Manager is much easier? If you've already rooted your phone then this has to be one of the hardest possible ways to install clockworkmod.
wbaw said:
You don't need your phone to be rooted to use fastboot, it's a method for new stock roms that have all the common root exploits fixed.
So, what's the point in this method when using Rom Manager is much easier? If you've already rooted your phone then this has to be one of the hardest possible ways to install clockworkmod.
Click to expand...
Click to collapse
I was never able to get fastboot working for my blade, always had driver issues, yet adb was fine. So I was able to use this method to flash and try the clockworkmod recovery touch that was released for us (turned out to be useless haha) but that couldn't be done via rom manager (well yeah, but you had to pay and i'm a poor student) so that's an example of when it could be useful.
point aside this is just another way, I just want people to learn as i am here to learn too.
Permission Denied
I need to flash CWM recovery using this adb method since I dont have data on the phone(Videocon Zeus V7500.. a clone of Commtiva Z51).
I have all the files in the right places but when I put the first command I get the following error :
I:\>adb push c:\flash_image /sdcard/
failed to copy 'c:\flash_image' to '/sdcard//flash_image': Permission denied ,
What permissions do I have to grant?
Try adb push c:/flash_image /sdcard/flash_image
Sent from my RACERII using xda app-developers app
Nevermind I figured it out, the problem was that I had mounted sd card to PC and I guess that was causing the problems.
I got it to work and have flashed CWM recovery now
Code:
I:\>adb push c:\flash_image /sdcard/
751 KB/s (26172 bytes in 0.034s)
I:\>adb push c:\recovery-clockwork-2.5.1.3-z71.img /sdcard
2444 KB/s (3831808 bytes in 1.531s)
I:\>adb shell
$ su
su
# su
su
# mount -o remount, rw /system
mount -o remount, rw /system
# cp /sdcard/flash_image /system/bin
cp /sdcard/flash_image /system/bin
# cd /system/bin
cd /system/bin
# chmod 777 flash_image
chmod 777 flash_image
# flash_image recovery /sdcard/recovery-clockwork-2.5.1.3-z71.img
flash_image recovery /sdcard/recovery-clockwork-2.5.1.3-z71.img
Thanks you very much for this thread
how to??
matt4321 said:
So was helping someone flash ClockworkMod via ADB in another thread, just thought if I made a topic for it, everyone can see it so if people have any issues they can always use this method instead.
Anyway, here are the instructions:
The 'flash_image' is within the attached zip file! Use the file within the zip file, NOT the zip file itself
The 'recovery.img' is your chosen recovery file, get this off ClockworkMods website or if you have a copy use that. Then when flashing the recovery image where ever it says 'recovery.img' replace that with the name of the recovery file.
Put the recovery image and the flash_image on the root of your C drive.
So,
(make sure you're in the command prompt and have changed directory to where the adb file is)
adb push c:\flash_image /sdcard/
adb push c:\recovery.img /sdcard/
adb shell
su
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img
It has now been flashed successfully
Hope this is of use to some people
Click to expand...
Click to collapse
friend plss suggest me that how to use this flash_image and where should i put it
in mobile system or in pc drive c
plsss tell me clearly because when i use it in cmd it says su not found whts the mean of this plss tell me clearly one by one step
i am not able to understnd
pls pls pls help me
---------- Post added at 04:09 PM ---------- Previous post was at 03:55 PM ----------
mandloihitesh said:
friend plss suggest me that how to use this flash_image and where should i put it
in mobile system or in pc drive c
plsss tell me clearly because when i use it in cmd it says su not found whts the mean of this plss tell me clearly one by one step
i am not able to understnd
pls pls pls help me
Click to expand...
Click to collapse
heyy plss i m confused in command
i dont know what commnds should i usee
plss help me
plss
---------- Post added at 04:13 PM ---------- Previous post was at 04:09 PM ----------
saaransh9 said:
u rooted and have superuser on your phone??
Click to expand...
Click to collapse
ya i rooted my phone and superuser is also installed on my phone then wht to do
????
clockworkmod is not working in recovery manager also
said unrecognized
thanks for this. Got me out of a jam
This unbricking method requires that you have adb working and have root access.
First, download the latest system update for your device.
For the 7" HDX, they are posted at
http://www.amazon.com/gp/help/customer/display.html?nodeId=201357190.
For the 8.9" HDX, they are posted at
http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=201357220.
Now, please note that I DO NOT have a Kindle Fire HDX, so if this doesn't work, let me know and I will remove it immediately.
Try these commands:
Code:
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /cache/kindleupdate.bin > /cache/recovery/openrecoveryscript
chmod 0777 /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /cache/kindleupdate.bin
adb reboot recovery
The only thing that you have to do is replace "your-downloaded-update.bin" with the path to your downloaded update. (To make it easier and avoid typos, I always just drag and drop the file into the terminal/command prompt window.)
Please also note that IT IS OKAY if the command "mkdir /cache/recovery" fails, as long as the error message says file already exists or something along those lines.
If this helped you repair your beloved HDX, feel free to hit that "Thanks" button.
Sent from my Nexus 7 using Tapatalk
r3pwn said:
This unbricking method requires that you have adb working and have root access.
First, download the latest system update for your device.
For the 7" HDX, they are posted at
http://www.amazon.com/gp/help/customer/display.html?nodeId=201357190.
For the 8.9" HDX, they are posted at
http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=201357220.
Now, please note that I DO NOT have a Kindle Fire HDX, so if this doesn't work, let me know and I will remove it immediately.
Try these commands:
Code:
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /cache/kindleupdate.bin > /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /cache/kindleupdate.bin
adb reboot recovery
The only thing that you have to do is replace "your-downloaded-update.bin" with the path to your downloaded update. (To make it easier and avoid typos, I always just drag and drop the file into the terminal/command prompt window.)
Please also note that IT IS OKAY if the command "mkdir /cache/recovery" fails, as long as the error message says file already exists or something along those lines.
If this helped you repair your beloved HDX, feel free to hit that "Thanks" button.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Nice. Never thought of the simple echo install. Sometimes I think having the device can be a hindrance. You tend to focus on problems, even at the expense of finding solutions. This should be the way EVERYONE with adb access recovers. Really nothing in here that could cause further issue! I like that.
GSLEON3 said:
Nice. Never thought of the simple echo install. Sometimes I think having the device can be a hindrance. You tend to focus on problems, even at the expense of finding solutions. This should be the way EVERYONE with adb access recovers. Really nothing in here that could cause further issue! I like that.
Click to expand...
Click to collapse
Thanks. I thought about adding a wipe system command, but if the download was corrupted, they'd be screwed. So I left it out.
Sent from my Nexus 7 using Tapatalk
I went ahead and added another command to the OP that may/may not help. It couldn't possibly cause any harm, though. Has anyone actually tried and confirmed this to be working?
Sent from my iPod touch using Tapatalk
When I try this, I send adb reboot recovery, the device restarts but says it failed to boot, and gives the options: "reset to factory defaults" or reboot. Is this different than factory reset or is it the same as factory reset. I know we aren't supposed to do a factory reset right?
---------- Post added at 05:17 PM ---------- Previous post was at 04:57 PM ----------
I just realized that it failed to copy the update .bin file. After a long time it said failed to copy file: Permission denied
dcoig1 said:
When I try this, I send adb reboot recovery, the device restarts but says it failed to boot, and gives the options: "reset to factory defaults" or reboot. Is this different than factory reset or is it the same as factory reset. I know we aren't supposed to do a factory reset right?
---------- Post added at 05:17 PM ---------- Previous post was at 04:57 PM ----------
I just realized that it failed to copy the update .bin file. After a long time it said failed to copy file: Permission denied
Click to expand...
Click to collapse
Are you sure you have root?
r3pwn said:
Are you sure you have root?
Click to expand...
Click to collapse
I am sure that the device was rooted before the bootloop condition. I can enter 'adb shell' and then 'su' with no problem from a command prompt. However, I do not think that we are superuser when we use the command 'adb push' from the commandline unless we use 'adb root' first and it won't let me do that. When i enter 'adb root' from the command prompt I get the response: "adbd cannot run as root in production builds"
dcoig1 said:
I am sure that the device was rooted before the bootloop condition. I can enter 'adb shell' and then 'su' with no problem from a command prompt. However, I do not think that we are superuser when we use the command 'adb push' from the commandline unless we use 'adb root' first and it won't let me do that. When i enter 'adb root' from the command prompt I get the response: "adbd cannot run as root in production builds"
Click to expand...
Click to collapse
Hmmmm. Try pushing it to /sdcard and change the path in your echo command to reflect that.
I am guessing that somehow the /cache/kindleupdate.bin is in a secure area that we cannot push to. Is there any area that we can push to? It seems we may have to push somewhere else and then move into the secured area using adb shell with su permission like here:
http://forum.xda-developers.com/showthread.php?t=1687590&page=5
but we don't have an sdcard with our devices.
---------- Post added at 10:35 PM ---------- Previous post was at 10:31 PM ----------
we actually do have an sdcard directory though... i will try to push there
---------- Post added at 10:54 PM ---------- Previous post was at 10:35 PM ----------
so i pushed the update file to the /sdcard/ directory then moved the file to the /cache/ directory, then renamed to kindleupdate.bin . Still does not help the system recovery issue. When I enter 'adb reboot recovery' it brings up a screen which says:
"Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot.
Reseting your device to Factory defaults may
help you to fix this issue.
Volume up/down to move highlight;
power button to select.
------------------------------------
Reboot your Kindle
Reset to Factory Defaults
-------------------------------------
---------- Post added at 11:48 PM ---------- Previous post was at 10:54 PM ----------
If it makes any difference I am not bricked at the grey kindle logo but the white and orange. It just keeps refreshing the animation over and over... nothing seems to ever happen. What should I normally see when I boot to recovery? An extra option to update or something?
No. What I meant was try pushing it to /sdcard then changing the echo command to reflect that.
so then:
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /sdcard/kindleupdate.bin > /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /sdcard/kindleupdate.bin
adb reboot recovery
dcoig1 said:
so then:
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /sdcard/kindleupdate.bin > /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /sdcard/kindleupdate.bin
adb reboot recovery
Click to expand...
Click to collapse
Yes. Try that.
EDIT: Wait. It'll probably say permission denied or some other lame error, so add
mount -o rw,remount /data
After the cache remount then change everything that references "/sdcard/" to "/data/media/0/".
That didn't work either. I keep getting the same result. I don't get errors using the sdcard directory though either, but I also tried with data/media/0. No errors, just doesn't work for me.
so do i.
adb push "bin" to sdcard can work,but after reboot recovery,
only show on screen like this：
Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot.
Reseting your device to Factory defaults may
help you to fix this issue.
Volume up/down to move highlight;
power button to select.
------------------------------------
Reboot your Kindle
Reset to Factory Defaults
-------------------------------------
Do not reset to factory defaults
I wanted to mention fastboot works. Read more...
I tried a different approach.
adb shell
su
adb remount
mkdir "/data/media/0/Updates
exit
exit
adb push C:\update-kindle-13.3.2.4_user_324002120.bin "/data/media/0/Updates/update-kindle-13.3.2.4_user_324002120.bin
Faznx92 said:
I wanted to mention fastboot works. Read more...
Click to expand...
Click to collapse
Not really. Not nearly as useful as the KFHD's. No useful commands work.
ChittyChittyGangBang said:
I tried a different approach.
adb shell
su
adb remount
mkdir "/data/media/0/Updates
exit
exit
adb push C:\update-kindle-13.3.2.4_user_324002120.bin "/data/media/0/Updates/update-kindle-13.3.2.4_user_324002120.bin
Click to expand...
Click to collapse
And did this help you unbrick your device?
Unbrick my Kindle
Sorry to interrupt, but my kindle fire HDX 7" is also bricked, I can not get past the gray "Kindle Fire" screen, I can get into fastboot. My device is not detected in ADB. Is there any hope for my kindle or is it dead?
r3pwn said:
Not really. Not nearly as useful as the KFHD's. No useful commands work.
And did this help you unbrick your device?
Click to expand...
Click to collapse
Nope. Ended up wasting half a weekend on it.
I just sent it back and bought a Samsung Galaxy Tab. Now I have GPS and IR in addition to a device that works like a Droid device should.
Hi guys, I didnt have much luck with the Easy Recowvery method on my G5 (20A)
Sooo, i thought i'd share with you, (what i like to call) Hard Recowvery method.
This is the most effective way i've rooted & installed TWRP my H830 on 7.0 (Nougat)
First lets download the neccessary recowvery files located here (Put them all in a folder): https://build.nethunter.com/android-tools/dirtycow/arm64/
Make sure you have the latest twrp for your phone: https://twrp.me/devices/lgg5h830.html
Latest Verity zip: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Latest SuperSU: https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
---
Shift+Open Command window in Recowvery folder
Note: Use app_process32 on 32-bit targets.
once in cmd window from your recowvery folder follow these steps:
---
adb push dirtycow /data/local/tmp
adb push recowvery-applypatch /data/local/tmp
adb push recowvery-app_process64 /data/local/tmp
adb push recowvery-run-as /data/local/tmp
adb shell
$ cd /data/local/tmp
$ chmod 0777 *
$ ./dirtycow /system/bin/applypatch recowvery-applypatch
"<wait for completion>"
$ ./dirtycow /system/bin/app_process64 recowvery-app_process64
"<wait for completion, your phone will look like it's crashing>"
$ exit
adb logcat -s recowvery
"<wait for it to tell you it was successful>"
"[CTRL+C]"
adb shell reboot recovery
"<wait for phone to boot up again, your recovery will be reflashed to stock>"
adb shell
$ getenforce
"<it should say Permissive, adjust source and build for your device!>"
$ cd /data/local/tmp
$ ./dirtycow /system/bin/run-as recowvery-run-as
$ run-as exec ./recowvery-applypatch boot
"<wait for it to flash your boot image this time>"
$ run-as su
(You need to rename the twrp img to "twrp.img" and put in the root of your internal storage, OR you can use this adb push command. The next two steps wont be neccessary if already done so.)
adb push twrp-3.0.2-x-xxxx.img /sdcard/twrp.img
adb shell
run-as exec dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery
"<wait for it to complete>"
$ reboot recovery
---
You should be in TWRP now,
flash supersu and the verity 4.1 zips. [Format Data] will remove internal storage encryption. so back up everything you need to with nandroid. lg backup, or titanium. (So i saw that they have updated verity zips but i just used 4.1)
I prefer lg backup, its easiest.
After you format data reflash supersu and verity zips for the hell of it. (you dont have to i dont think but i just did anyway)
Now just reboot, & enjoy
This isnt a method i created, i got it from this thread. and made the steps i felt were neccessary.
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Works until "run-as exec dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery" then says:
Current uid: 0
We have root access!
------------
Executing: 'dd' with 2 arguments
dd: /sdcard/twrp.img: No such file or directory
1|h1:/data/local/tmp #
No Twrp recovery any help?
---------- Post added at 08:47 PM ---------- Previous post was at 08:07 PM ----------
Forgot to rename recovery.
---------- Post added at 09:32 PM ---------- Previous post was at 08:47 PM ----------
Problem solved! Forgot to rename img.
Tinbender418 said:
Works until "run-as exec dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery" then says:
Current uid: 0
We have root access!
------------
Executing: 'dd' with 2 arguments
dd: /sdcard/twrp.img: No such file or directory
1|h1:/data/local/tmp #
No Twrp recovery any help?
---------- Post added at 08:47 PM ---------- Previous post was at 08:07 PM ----------
Forgot to rename recovery.
---------- Post added at 09:32 PM ---------- Previous post was at 08:47 PM ----------
Problem solved! Forgot to rename img.
Click to expand...
Click to collapse
The 2 agreement how did u type it BC I had that but I didn't know what to type so I use the toolkit instead
Sent from my LG-H830 using Tapatalk
Rename to twrp.omg move to internal sd card.
Sent from my LG-H830 using Tapatalk
sorry guys i was busy! & yes you need to rename the recovery img to "twrp.img". i will add the step to rename the twrp file!
djevil said:
The 2 agreement how did u type it BC I had that but I didn't know what to type so I use the toolkit instead
Sent from my LG-H830 using Tapatalk
Click to expand...
Click to collapse
Just copy and paste everything as you see it. and if you mean you didnt know how to rename twrp recover just rename to "twrp.img"
so my getenforce keeps saying enforcing?
---------- Post added at 10:39 AM ---------- Previous post was at 10:35 AM ----------
and the command to run-as exec says no exec found?
---------- Post added at 10:50 AM ---------- Previous post was at 10:39 AM ----------
Hmm so after looking it up, apparently my brand new G5 I just got today is on 20c and not 20a. I guess that is the problem?
hello?
jdkzombie said:
hello?
Click to expand...
Click to collapse
Yes that is the problem Read Autoprime's thread on the H83020c update. He explains a way to root device by downgrading to H83020a using LGUP.
Sent from my LG-H830 using Tapatalk
I don't seem to get passed the adb logcat step because I do so and it says that all process was done correctly but my phone won't at all boot up after he T-Mobile logo
Tried and did everything step by step and this is always the problem and can't get passed it
Someone please help
Sent from my iPhone using Tapatalk
Just use the Automagically thread a few below this one. You have to be on 20A for it to work. I used that method and it worked on the first try. Now I'm on 20C and I'm rooted as well. This way is way too complicated.
djerick3 said:
Just use the Automagically thread a few below this one. You have to be on 20A for it to work. I used that method and it worked on the first try. Now I'm on 20C and I'm rooted as well. This way is way too complicated.
Click to expand...
Click to collapse
The easy recovery method that runs the script? I have tried it countless times and also doesn't seem to work
wadamean said:
The easy recovery method that runs the script? I have tried it countless times and also doesn't seem to work
Click to expand...
Click to collapse
First you need to run the script and follow the instructions to the letter. If you read into the thread you'll see that you need to turn off verification before you run it. I forget what option it is but ill check and post it for you. Worked smooth for me first try.
Stuck
I seem to be stuck at adb logcat -s recowvery
"<wait for it to tell you it was successful>"
"[CTRL+C]"
It's been a while. It hasn't moved from there and it won't let me input anything else. I got stuck after beginning of main and beginning of system.
Will this work starting from MM or only once on Nougat? My phone hasn't downloaded the update yet and it won't let me force it. Trying it on MM doesn't seem to complete.
Sent from my LG-H830 using XDA-Developers Legacy app
---------- Post added at 04:17 AM ---------- Previous post was at 03:48 AM ----------
Rican39 said:
Deleted
Sent from my LG-H830 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Sent from my LG-H830 using XDA-Developers Legacy app
Well this is interesting. The script the people above are talking about never worked for me. So I came here and got my hands dirty and did it the manual way. Everything worked great until I formatted data and reflashed verity and su zips. After booting, all I can get the phone to do is boot to twrp. I've successfully flashed the 20A kdz back to stock with unlocked bootloader. Just wondering what I did wrong?
Once I get into TWRP the steps used were:
1 - Flash SuperSU
2- Flash verity zip
3- Format Data
4- Flash SuperSU again (for good measure)
5- Flash verity zip again (for good measure)
All these instructions make sense but at the top of the OP it says to NOT swipe to allow system modifications. I thought after formatting data and flashing the verity zip that we can swipe to allow. If we can't modify the system partition, how do we access it for busybox, etc..
Sorry for the odd questions - just looking for clarity!
UPDATE: Sorry, I resolved my own problem. Just don't ever swipe to modify system in TWRP and you're good. Not sure why this was the case.
eliolicious said:
I seem to be stuck at adb logcat -s recowvery
"<wait for it to tell you it was successful>"
"[CTRL+C]"
It's been a while. It hasn't moved from there and it won't let me input anything else. I got stuck after beginning of main and beginning of system.
Click to expand...
Click to collapse
I have this same problem. Did you figure out the issue?
codahq said:
I have this same problem. Did you figure out the issue?
Click to expand...
Click to collapse
I figured out the issue. There are a bunch of threads floating around here that seem to think that the dirtycow exploit will work on 20A and 20C. That is definitely not the case. 20C it is patched so you have to KDZ back to 20A and then exploit. Then you can TWRP flash 20C if you want to go back to 20C.
I'm was on 20C though and dirtycow definitely doesn't work.
Noob question
I got this phone lg g 5 tmobile variant yesterday. I was on marshmallow rooted with Xposed Framework Flashed 7.0 thinking it was a rom. I lost root and lost custom recovery I'm trying to root on 7.0 via dirty cow but instructions r too complicated. Can anybody tell me what dirty cow files to download and were to put the folder pls