Hi, i installed Rbox's custom recovery earlier. When running the initial coomand from the adb shell i had to run it as su or i received a permission error. After running the reboot recovery command, the device rebooted, displayed the white Amazon logo, and then went to the Amazon update failed screen... after a minute or two it started up fine. Am i doing something wrong. Thanks!
It seems when you did the dd commands it didn't write the recovery. So you either typed the command wrong, or don't have root access which is needed for permission to write to the partition. Did your cursor change from an $ to # after running su?
Luxferro said:
It seems when you did the dd commands it didn't write the recovery. So you either typed the command wrong, or don't have root access which is needed for permission to write to the partition. Did your cursor change from an $ to # after running su?
Click to expand...
Click to collapse
i didn't notice to be honest, but i did get a message on the FireTV saying su access had been granted, and then the text in the shell (after i copied and pasted the command from the thread in) looked as if it worked... no errors. And yes, i had named my file the same as the example and had put it in the same location. Once i ran the reboot recovery command was where i got the Amazon updated unsuccessful screen. i had thought it would just reboot into the recovery menu. Thanks.
tavery said:
i didn't notice to be honest, but i did get a message on the FireTV saying su access had been granted, and then the text in the shell (after i copied and pasted the command from the thread in) looked as if it worked... no errors. And yes, i had named my file the same as the example and had put it in the same location. Once i ran the reboot recovery command was where i got the Amazon updated unsuccessful screen. i had thought it would just reboot into the recovery menu. Thanks.
Click to expand...
Click to collapse
What you saw was the stock FireTV recovery. I'd give it another try and make sure it switches to root access (#).
I started over as suggested and it worked as it was supposed to this time. I obviously must have missed something or had a typo the last time. Thanks for your help!
Related
I have rooted and flashed to the latest recovery image. i can not get into adb recovery. every time i try i get the following prompt ~# followed by my command and then file not found. Anybody had this problem that knows how to fix. thanks
shadow635 said:
I have rooted and flashed to the latest recovery image. i can not get into adb recovery. every time i try i get the following prompt ~# followed by my command and then file not found. Anybody had this problem that knows how to fix. thanks
Click to expand...
Click to collapse
sounds like you are getting adb. What happens if you just run "adb shell"? What is the exact command you are trying to run?
cd/system/app is the command entered. i am following the post for removing apps. i have entered clockwork, gone to partitions and then went to unmount. connected to pc and type adb remount. get remount succeeded. type adb shell and the following prompts
~#cd/system/app (command)hit enter
cd/sytem/app
/sbin/sh: cd/sytem/app: not found
did u mount the system and SD partitions?
Yes tried both mount and unmount and get the same messages
Sent from my ADR6300 using Tapatalk
shadow635 said:
~#cd/system/app (command)hit enter
cd/sytem/app
/sbin/sh: cd/sytem/app: not found
Click to expand...
Click to collapse
Need a space between "cd" and "/".
If you're not a unix person and are entering these commands without knowing what they do, it's important to enter them exactly as described. Better yet, cut & paste rather than type them.
thanks will try that i did cut and paste will try adding space to command
So I'm trying to get into su to run gfree_verify to make sure my permaroot S-off/SIM card unlock/SuperCID was successful, but I'm getting a permission denied error.
What happens is, I type adb shell, then I type su, there's a really long delay, then it tells me Permission Denied. However, when I run the Terminal Emulator from my phone and type in the su command, I get root access just fine.
I used the "official" method that is on the HTC Vision Wiki that is located here. The only thing, however, is that my Android SDK install wasn't installed using any type of installer. I just extracted a zip file and shoved it in a random folder. I did make sure to run the Command Prompt as Administrator before issuing the adb shell command, but I'm still unable to get superuser access through the PC. Trying to use the adb root command gives me an "adbd cannot run as root in production builds" error.
Did I do something incorrectly?
adb kill-server
adb start-server
See if that works. If not, try rebooting your computer.
Sent from a Western Union telegram.
Does the Superuser app seem to be installed correctly on your phone ?
Do you have the output from gfree ? I wonder if it didn't work correctly with your kernel, it doesn't work with all kernels. What ROM/kernel do you have ?
Which procedure did you use, the one in the Wiki, or one involving dd'ing the eng hboot ?
steviewevie said:
Does the Superuser app seem to be installed correctly on your phone ?
Do you have the output from gfree ? I wonder if it didn't work correctly with your kernel, it doesn't work with all kernels. What ROM/kernel do you have ?
Which procedure did you use, the one in the Wiki, or one involving dd'ing the eng hboot ?
Click to expand...
Click to collapse
I rebooted the daemeon, computer, and also the phone. No dice.
The Superuser app is correctly installed. When I ran Adfree and attempted to go into SU in Terminal, I got the usual Allow Superuser access dialog. Both worked without any problems; like I said, I can get root access from the on-the-phone terminal, it's when I attempted to get root access from the adb shell command on my computer where I have problems.
No special ROMs, completely stock post-November OTA update. The only thing I flashed after permarooting was the Clockwork Recovery mod, but adb shell SU wasn't working before this. I initially used some outdated instructions (involving the use of the dd command, and the wpathis.ko or something). I read some more and learned these were out of dated, so I unrooted. I then used the instructions that are on the wiki using gfree to permroot.
gfree_verify works without any problems if I run it from the Terminal Emulator on my phone. Returns the proper values to indicate I'm SIM Unlocked, SuperCID, and S-off. I'm glad it works, but I still don't like the fact I can't use the adb shell. Typing characters on the G2 is a pain in the ass.
I still want to know why I can't enter superuser from the PC adb shell. Am I doing something incorrectly?
Thanks a lot for your help!
Try clearing data for the SuperUser app?
go in your recovery screen from boot, select your mount options, and mount everything lol. Not sure if it'll fix it but everytime I have adb permission issues that seems to fix it and I don't think it could hurt.
dietotherhythm said:
go in your recovery screen from boot, select your mount options, and mount everything lol. Not sure if it'll fix it but everytime I have adb permission issues that seems to fix it and I don't think it could hurt.
Click to expand...
Click to collapse
This worked perfectly! When I entered su from the command prompt, the SuperUser app popped up on the phone's side and I hit allow. It then let me through.
What exactly was broken though? Why did mounting everything from the Clockwork Recovery menu fix this?
OK here is the story
FireTV 51.1.0.2_user_510058520 2 days old
Rooted and installed busybox everything was fine. So I figured I wanted the latest Rootable version.
Followed this guide (http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/ )
Problems started here: at the end trying to push update.zip to cache got error "cannot stat ‘update.zip’: no such file or directory"
update.zip was in same directory as adb
So I went and Installed Clockworkmod Recovery and pushed it using "adbfire" since it can push files to /sdcard (used this other guide http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/)
Went and rebooted into clockworkmod and that's when I saw the Previous command running trying to install update.zip wich was not there cuz I was never able to push it in the first place.
Well I could not get out of there by any means since I don't have a USB keyboard with me anymore
well I pushed the update.zip to /sdcard (again using adbfire) and used the mv command to transfer the file to /cache aaaaaaand reboot
Now I have my android logo updating the firmware and rebooting the FireTV when reaching the middle of the process just to start again and again
note: I can still connect to my firetv via adb while the screen is on and lose connection when reboots.
Any help would be greatly appreciated
Thanks in advance
LastDeuS said:
OK here is the story
FireTV 51.1.0.2_user_510058520 2 days old
Rooted and installed busybox everything was fine. So I figured I wanted the latest Rootable version.
Followed this guide (http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/ )
Problems started here: at the end trying to push update.zip to cache got error "cannot stat ‘update.zip’: no such file or directory"
update.zip was in same directory as adb
So I went and Installed Clockworkmod Recovery and pushed it using "adbfire" since it can push files to /sdcard (used this other guide http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/)
Went and rebooted into clockworkmod and that's when I saw the Previous command running trying to install update.zip wich was not there cuz I was never able to push it in the first place.
Well I could not get out of there by any means since I don't have a USB keyboard with me anymore
well I pushed the update.zip to /sdcard (again using adbfire) and used the mv command to transfer the file to /cache aaaaaaand reboot
Now I have my android logo updating the firmware and rebooting the FireTV when reaching the middle of the process just to start again and again
note: I can still connect to my firetv via adb while the screen is on and lose connection when reboots.
Any help would be greatly appreciated
Thanks in advance
Click to expand...
Click to collapse
Well you can do
Code:
adb reboot recovery
to get to recovery, Then in one window run
Code:
adb shell
and in then run
Code:
/sbin/recovery-input
and then in another window run adb shell again and this time run killall recovery. Then you can use recovery-input to control recovery. I would recommend pushing one of the prerooted updates, flashing it, doing a factory reset, then reboot and it should be fine. Another option is to use adb sideload.
rbox said:
Well you can do
Code:
adb reboot recovery
to get to recovery, Then in one window run
Code:
adb shell
and in then run
Code:
/sbin/recovery-input
and then in another window run adb shell again and this time run killall recovery. Then you can use recovery-input to control recovery. I would recommend pushing one of the prerooted updates, flashing it, doing a factory reset, then reboot and it should be fine. Another option is to use adb sideload.
Click to expand...
Click to collapse
First thanks for your quick reply
the thing is my current state is Recovery looping while the firetv tries to install the new software so what I see is
Amazon logo
Android logo updating but just the blue bar filling
then shuts down
then android logo again and again
the commands you recommended were adb reboot recovery ----> /sbin/sh: not found
adb shell ---->/sbin/sh: not found
/sbin/recovery-input ----> Welcome to recovery input (this one works but I'm not quite where I need to be to control anything)
killall recovery ----> This command just reboots again into the same state
You also mentioned adb sideload but that's after I regain control of recovery right???
Please let me know other options to get out of this loop
Thanks again
LastDeuS said:
First thanks for your quick reply
the thing is my current state is Recovery looping while the firetv tries to install the new software so what I see is
Amazon logo
Android logo updating but just the blue bar filling
then shuts down
then android logo again and again
the commands you recommended were adb reboot recovery ----> /sbin/sh: not found
adb shell ---->/sbin/sh: not found
/sbin/recovery-input ----> Welcome to recovery input (this one works but I'm not quite where I need to be to control anything)
killall recovery ----> This command just reboots again into the same state
You also mentioned adb sideload but that's after I regain control of recovery right???
Please let me know other options to get out of this loop
Thanks again
Click to expand...
Click to collapse
If recovery is still in some kind of a loop, doing rm /cache/recovery/* while in adb shell should clear that up.
rbox said:
If recovery is still in some kind of a loop, doing rm /cache/recovery/* while in adb shell should clear that up.
Click to expand...
Click to collapse
I tried rm /cache/recovery/* and I think it erases that folder cuz when trying to run same command again it states as no such file or directory but then I wait and reboots again into same loop
again ran killall recovery and nothing reboot again looping T_T
LastDeuS said:
I tried rm /cache/recovery/* and I think it erases that folder cuz when trying to run same command again it states as no such file or directory but then I wait and reboots again into same loop
again ran killall recovery and nothing reboot again looping T_T
Click to expand...
Click to collapse
I dunno. Recovery shouldn't be doing any looping... With an empty /cache/recovery it should just sit there and do nothing. And it makes it more difficult without a usb keyboard.
rbox said:
I dunno. Recovery shouldn't be doing any looping... With an empty /cache/recovery it should just sit there and do nothing. And it makes it more difficult without a usb keyboard.
Click to expand...
Click to collapse
I can bring a keyboard from work tomorrow if that would help us troubleshoot cuz right now my keyboard is wireless
I know I've been asking a lot this last hour but can you please point me in the right direction so tomorrow I can Try something else using an usb keyboard?
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset Cache
Reboot
or
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset to factory defaults
Reboot
roligov said:
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset Cache
Reboot
or
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset to factory defaults
Reboot
Click to expand...
Click to collapse
Well yesterday I couldn't bring the keyboard but now I have it in front of me but I haven't been able to reproduce the recovery mode with the keyboard combination.
I know it works because the firetv reboots but sometimes goes to the initial amazon logo and sometimes just the same updating android logo
So any suggestions now that we have the keyboard here???
OK I finally figured it out.
All started when I ran the command "echo --update_package=/cache/update.zip > command" to update to a stock ROM but was never able to PUSH the actual file... kept getting error "cannot stat ‘update.zip’: no such file or directory"
THEN
I successfully installed Clockworkmod Recovery (luckily) and when rebooted to recovery I was presented with Clockwmod Recovery asking if sure to install the NON PRESENT "rom.zip"
BUT i didn't have a keyboard with me at that moment and didn't know the "control recovery" command either... SO I thought to find a different way to PUSH the file....
So I used push file function in adbfire to get the file into /sdcard/ and the the mv command to get it to /cache
SO I got my problem right there wich I was able to reproduce today: When you connect to adb during recovery or booting the FireTV you will get this error for most commands including su ----> "/sbin/sh: not found"
NOW if you try to push a file it will say it got pushed but only half of it or some shortcut of it I'm not sure
The thing is with that half pushed file the system now obeys "echo --update_package=/cache/update.zip > command" and starts updating and shuts down reboots and update again, whatever you do it keeps on booting again to the same state(trust me nothing works)
What I did basically with the few seconds I got between reboots I ran "rm -f /cache/*.bin" and rm -f /cache/*.zip to erase all cache folder and then I was again asked to install the file (not there again) and disabled recovery flash
Anyways thanks for all the replys I got really appreciated all your help and keep up the good work ppl I hope this helps someone out there besides me.
I'm now running the latest prerooted rom from rbox thanks again for that
have a good one
question: Is there an actual gui windows app to transfer files to FireTV???
2: Do I need to block updates for this custom rom also or that's already implemented?
The pre-rooted ROM blocks updates. You can check using TiBU. I think three files are frozen.
Glad you pulled out of your crash.
schneid said:
The pre-rooted ROM blocks updates. You can check using TiBU. I think three files are frozen.
Glad you pulled out of your crash.
Click to expand...
Click to collapse
It doesn't. But if you had dcp blocked before installing it, it'll remain blocked. You should always have dcp blocked.
rbox said:
It doesn't. But if you had dcp blocked before installing it, it'll remain blocked. You should always have dcp blocked.
Click to expand...
Click to collapse
TiBU shows mine "frozen". Did I do that previously with something else?
schneid said:
TiBU shows mine "frozen". Did I do that previously with something else?
Click to expand...
Click to collapse
Either you froze it with titanium previously or you did the pm disable command.
rbox said:
Either you froze it with titanium previously or you did the pm disable command.
Click to expand...
Click to collapse
I did do the PM disable thing but thought your rooted ROM would undo it. Guess not. Anyway, I'm happy. Thanks.
Think I bricked mine
Just got my firetv and did the usual ie. rooted, su added , then I Installed Clockworkmod Recovery and tried to upgrade to the latest rootable firmware, using update.zip to /cache and then it just keeps rebooting.
No amazon screen, goes to Andriod loads 1/3 of the way andf reboots, over and over.
picture attached
Cant adb to it , when doing the alt+print screen+i with my keyboard just reboots it faster
Think i'm offically bricked and its a bummer , be careful when changing firmware with CWR and sending your update.zip .
I dont know where it went wrong but it did
Note3usr said:
Just got my firetv and did the usual ie. rooted, su added , then I Installed Clockworkmod Recovery and tried to upgrade to the latest rootable firmware, using update.zip to /cache and then it just keeps rebooting.
No amazon screen, goes to Andriod loads 1/3 of the way andf reboots, over and over.
picture attached
Cant adb to it , when doing the alt+print screen+i with my keyboard just reboots it faster
Think i'm offically bricked and its a bummer , be careful when changing firmware with CWR and sending your update.zip .
I dont know where it went wrong but it did
Click to expand...
Click to collapse
Don't use update.zip and don't put it in /cache. Since so many people seem to be screwing up by doing that, I'm going to disable the automatic flashing in the next version. As for not being able to adb to it, it's probably using a different ip than what you are expecting. In every instance of people doing this, adb has always worked. Then just rm whatever you put in /cache. Next time use sideload or put it in /sdcard.
rbox said:
Don't use update.zip and don't put it in /cache. Since so many people seem to be screwing up by doing that, I'm going to disable the automatic flashing in the next version. As for not being able to adb to it, it's probably using a different ip than what you are expecting. In every instance of people doing this, adb has always worked. Then just rm whatever you put in /cache. Next time use sideload or put it in /sdcard.
Click to expand...
Click to collapse
I send the update.zip to the ftv with Amazon FireTV Utility App and it looked like it went all the way through , by default isnt that where it send it to ? /cache
Ive been trying to ping the ip , or shell to it but how much times could I have when it just keeps cycling. I dont think its possible to adb to it at this point as I get the attached screen for like 10 seconds or something it will just hold at the all white amazon logo if i'm screwing around with the keyboard combantions , i'm just stuck at this point and dont wanna keep burning hours if i cant go further.
I'm assuming its trying to load whatever is in the /cache folder which is either nothing or ave an update.zip file no idea
thanks for the reply as i will try some more to adb in
I am in a similar boat. I tried to install "rom.zip" per the instructions here http://www.aftvnews.com/how-to-install-a-custom-rom-image-on-the-amazon-fire-tv/
but it would not install it from CWM. It would abort the installation instantly. I read another thread where someone wasn't able to do something through ADB Shell because of SU permissions. I tried to uninstalled it and sideloaded SuperSU again. When I accessed it instead of clicking on "Normal" I chose the other option. Well, it's not stuck in the same loop as mentioned here.
I see the Amazon logo briefly, then it shows the android logo and reboots. It disconnects for a few seconds with the TV saying there is no HDMI connection and then shows the amazon logo shortly after again. I can no longer ADB into it.
Please help.
Note3usr said:
I send the update.zip to the ftv with Amazon FireTV Utility App and it looked like it went all the way through , by default isnt that where it send it to ? /cache
Ive been trying to ping the ip , or shell to it but how much times could I have when it just keeps cycling. I dont think its possible to adb to it at this point as I get the attached screen for like 10 seconds or something it will just hold at the all white amazon logo if i'm screwing around with the keyboard combantions , i'm just stuck at this point and dont wanna keep burning hours if i cant go further.
I'm assuming its trying to load whatever is in the /cache folder which is either nothing or ave an update.zip file no idea
thanks for the reply as i will try some more to adb in
Click to expand...
Click to collapse
Hey your problem is really similar to mine and what I did was connect to adb in between the loops and erase all cache
try searching on your router or do a scan on your network and find the correct ip address for the firetv
also don't worry about not being able to SU just erase cache using "rm -f /cache/*.bin" and "rm -f /cache/*.zip"
then it will ask for the actual file and just choose "not to install" then "disable recovery flash"
pd: Don't try to enter recovery by keyboard combinations it's useless trust me I tried A LOT
Hello All,
Purchased an Amazon Fire TV from Amazon, it shipped in one day and I have been toying with it for the last few hours. Rooting was easy, as was installing SU, Busybox, Stickmount etc.. However, I am not to the point to where I want to install a custom recovery so I can update to the latest firmware without loosing root. The instructions say I need to downgrade to an earlier firmware in order to do this. My problem is that every time I reboot into recovery it says "Update was not successful" and It boots back to the same version that I started with.
The version I have now is 5.1.1.1.0 fully rooted w/ Busybox. I don't know exactly what I am doing wrong. I have both pushed the update.zip to the AFTV, and I have also put it on a thumb drive. I have tried earlier versions then the one recommended in the guide that I was following. All of this to no avail.
Please help.
Thank you.
Anybody? I was up till little after 3 AM trying to figure this out. Factory reset, re-rooted, nothing seems to work. Has anyone else had this issue?
I had the exact same problem. Try a different firmware download option. I used the "mirror' on AFTVnews.com the first time and had the same fail at the end that you did. I also re installed busybox before I performed the downgrade, so I'm not sure which of the two fixed the problem, but I suspect it was a bad download from the mirror.
roaoro said:
I had the exact same problem. Try a different firmware download option. I used the "mirror' on AFTVnews.com the first time and had the same fail at the end that you did. I also re installed busybox before I performed the downgrade, so I'm not sure which of the two fixed the problem, but I suspect it was a bad download from the mirror.
Click to expand...
Click to collapse
Just tried the mirror. That ended in the same result. I am going to try re-installing Busybox again to see if that has any change.
roaoro said:
I had the exact same problem. Try a different firmware download option. I used the "mirror' on AFTVnews.com the first time and had the same fail at the end that you did. I also re installed busybox before I performed the downgrade, so I'm not sure which of the two fixed the problem, but I suspect it was a bad download from the mirror.
Click to expand...
Click to collapse
Tried re installing busybox that didn't crack it either.
The exact error is "The System Update was not successful." Your AFTV will restart in a few minutes and should resume normal operation.
Any other ideas I can try?
brotherandyslb said:
Tried re installing busybox that didn't crack it either.
The exact error is "The System Update was not successful." Your AFTV will restart in a few minutes and should resume normal operation.
Any other ideas I can try?
Click to expand...
Click to collapse
You need to list exactly what you are doing so we can tell you what you are doing wrong.
I had to do it a couple of times because it didn't work right at first either.
nyder said:
You need to list exactly what you are doing so we can tell you what you are doing wrong.
I had to do it a couple of times because it didn't work right at first either.
Click to expand...
Click to collapse
Ok,
Lets start from the top:
Factory Reset
Watch Video
Sign into Amazon Prime
So no to parental controls
Go to developer options and turn it to on so I can use ADB
Connect with ADB
adb install towelroot
go into towelroot and root
adb install supersu
go into supersu and let it update
adb install busybox
go into busybox and install it and let it symlink
adb the command to turn off updates
Then I follow the guide over at aftvnews.com to downgrade
Download the firmware version you wish to install from the software page
Rename the downloaded file to update.zip
Connect to your Fire TV using ADB
(If you don’t know how, follow up to Step 4 Part 2 in our Windows or Mac guide)
Run the command: adb shell
Run the command: su
(If this is the first time you’ve ever run su, a pop-up will appear on the Fire TV, select Grant)
Run the command: chmod 777 /cache
Run the command: chmod 777 /cache/recovery
Note: If
you see a message saying “No such file or directory”, then run the following two commands:
mkdir /cache/recovery
chmod 777 /cache/recovery
Run the command: cd /cache/recovery
Run the command: echo --update_package=/cache/update.zip > command
Run the command: exit
Run the command (yes, again): exit
Run the command: adb push update.zip /cache
(This assumes the update.zip file you renamed in step 2 is in the same directory as adb, otherwise enter the full path to the file like adb push C:\full\path\to\update.zip /cache)
Once the update.zip file has finished transferring to the Fire TV, run the command: adb reboot recovery
At this point your fire TV should restart and begin installing whichever firmware version you selected.
Click to expand...
Click to collapse
At this point the AFTV restarts and proceeds to install the new firmware about 1/4 way thru it gives the error message and then restarts.
OK, I had my kindle running cyanogenmod 11. I was having problems with some apps running on it, root was acting weird. Root checkers said it was rooted, but some apps that required root weren't installing right.
Fast forward, I thought perhaps I needed to flash the new version. I got into recovery to run it and flash it and this is the error I have.
So all the forums said, just wipe it then it will work. Of course now I have no OS on the thing. TWRP is fine, but I can't use the tablet.
So some other forums suggested it's either a mounting to E:\ problem or a rooting problems. I can get in to ADB, I've pushed many different roms over and they all have similar errors.
All of the Root tools I can find require you to come in the front door. TWRP fails when it goes to 'fix permission' and every time I reboot says , 'root is gone, swipe to fix' but it's not seeming to stick.
Any ideas on how to make sure I can mount the new rom and get this back up and running.
As I said, I've tried many roms, directly downloaded from CM website: Download:
cm-12.1-20160129-NIGHTLY-d2tmo.zip (284.96 MB)
sha1: e461a1dc263d927de3b6748d3b877310e7b1fd39
Download: cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2tmo.zip (286.1 MB)
sha1: bfb989917775ff190b8b795d93c1e439ccf8a514
I'm running TWRP 2.6.0.0 and have a binary ADB driver of 1.0.31. I can ping 4.2.2.2 so I'm pretty sure since the issue is coming from the device itself, and the way it's erroring reminds me of other permission problems I've seen in other devices that it's a root issue.
Is there a simple command line ADB tool or something that I can use to validate/set root?
Thanks!
kyleyarbrough said:
OK, I had my kindle running cyanogenmod 11. I was having problems with some apps running on it, root was acting weird. Root checkers said it was rooted, but some apps that required root weren't installing right.
Fast forward, I thought perhaps I needed to flash the new version. I got into recovery to run it and flash it and this is the error I have.
So all the forums said, just wipe it then it will work. Of course now I have no OS on the thing. TWRP is fine, but I can't use the tablet.
So some other forums suggested it's either a mounting to E:\ problem or a rooting problems. I can get in to ADB, I've pushed many different roms over and they all have similar errors.
All of the Root tools I can find require you to come in the front door. TWRP fails when it goes to 'fix permission' and every time I reboot says , 'root is gone, swipe to fix' but it's not seeming to stick.
Any ideas on how to make sure I can mount the new rom and get this back up and running.
As I said, I've tried many roms, directly downloaded from CM website: Download:
cm-12.1-20160129-NIGHTLY-d2tmo.zip (284.96 MB)
sha1: e461a1dc263d927de3b6748d3b877310e7b1fd39
Download: cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2tmo.zip (286.1 MB)
sha1: bfb989917775ff190b8b795d93c1e439ccf8a514
I'm running TWRP 2.6.0.0 and have a binary ADB driver of 1.0.31. I can ping 4.2.2.2 so I'm pretty sure since the issue is coming from the device itself, and the way it's erroring reminds me of other permission problems I've seen in other devices that it's a root issue.
Is there a simple command line ADB tool or something that I can use to validate/set root?
Thanks!
Click to expand...
Click to collapse
Your TWRP version is out of date. Flash the 2.8.7.0 image from this thread, reboot into TWRP and make sure your TWRP version is now 2.8.7.0, and try flashing CM12.1 after that.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Your TWRP version is out of date. Flash the 2.8.7.0 image from this thread, reboot into TWRP and make sure your TWRP version is now 2.8.7.0, and try flashing CM12.1 after that.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
HI! thanks for that advice. I wish I could. I've tried several methods, and although I can get into ADB shell, I can't access su:
besides kindle fire first aide and other batch files, I found some manual instructions:
http://forum.xda-developers.com/showthread.php?t=2277105
Here's what it tells me to do (among many other things): I realize this is just backing up stuff that doesn't exist etc, but it's indicative of the problems without having su.
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
mkdir C:\KFHD8Backup
adb pull /sdcard/stock-boot.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-recovery.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-system.img/ [C:\KFHD8Backup]
but if I go into adb shell and type any commands, like just simple su:
I get /sbin/sh: su: not found
when I do whoami: I get root
but I get a funky prompt:
~#^[[61;5R
instead of a normal # root prompt.
So I'm kind of stuck because I can't really do anything without the su, and it says I'm root. So can I adb push over the files and mount the right drives or whatever to get it to recognize su. At that point I can install twrp, but i'm sure at that point my existing twrp will work too!
I can't seem to get it into fastboot mode either. When I adb devices it says I'm in recovery, not device and in TWRP it says no OS installed. So my only functioning loader is TWRP. (or however you put that more accurately).
I feel like with adb push working, I should be able to do something to get this back, but all the tools expect you to just push a button, not do it the hard way.
So long story short, if you can point me to a thread that tells me how to update TWRP or how to push SU over with ADB or anything that would be awesome. I"m not a complete turd at this, but I think I broke it using something like kingoroot instead of just using the bin4ry while I still had the cyanogenmod working somewhat. So I'm thinking that's why i got the funky prompt, and that's why my su is gone from where it should be.