i am now in 6.2.1 rooted by Jcase's method.
i can enter the adb correctly but when i type "adb remount"
it resulted back "operation not permitted"
the more important part is that:
when i type in "idme bootmode 0x4002" in the adb shell
it said "<idme>invalid permission"
i have put superuser.apk and su in the correct places.
is there any solution for my situation?
i want to get into fastboot mode becoz i want to try the oc kernel
I have the same problem. is there a solution?
Edit: i found a solution: type su after adb shell, then continue with idme bootmode 4002
after that i was able to install TWRP
Yea you need to su in to be able to do whatever you want.
Sent from my Kindle Fire using Tapatalk
Kindle looks and acts rooted but i can't install TWRP with KFU.
When it ask the kindle to reboot in fastboot the kindle stays idel in usb mode.
EDIt got it rooted by installing android phone drivers then i rolled them back now it reads as a usb composite device or something, doesn't say kindle with the flag like it did at first.
What commands did you use?
what commands??? i used 5 on KFU it did its thing so far then it said waiting for device after it told the kindle to reboot in fastboot.
I just got this today with stock 6.2.2 and got it rooted finally but i want recovery and other roms >.> THe kindle just doesn't reboot when its told by KFU during TWRP installation.
I think KFU isn't working for 6.2.2 at the moment.
Are you comfortable with running commands from the command prompt? If yes, do you have ADB running properly?
if i have a set of instructions I can use the command line. but not intuitivelly, i got this thing rooted even after installing the drivers gfailed so i did pretty good so far
,
Disregard this post. See my next post.
I has to be root first right, cause i was mistaken and it didn't take. when i run the command line to enable root it gets this message
adbd cannot run as root is in production build.
i even tried the instruction on this link by they are very vague for 6.2.2 and it doesn't tell you were to place files which i assume got to C;\kindleADBhttp://rootzwiki.com/topic/13027-universal-all-firmware-one-click-root-including-262/
Disregard my last post. Do the following.
Download BurritoRoot2.bin from this thread and TWRP from here. Place BurritoRoot2.bin and the TWRP image in the same folder as adb.exe and fastboot.exe (you can use the ones from KFU).
Now run the following...
Code:
adb push BurritoRoot2.bin /data/local/tmp/
adb shell chmod 777 /data/local/tmp/BurritoRoot2.bin
adb shell /data/local/tmp/BurritoRoot2.bin
adb root
adb shell idme bootmode 4002
adb reboot
You were given root access for the adb shell with BurritoRoot2 and that allowed you to change the bootmode. The last command will rebooted the KF into fastboot mode.
When you see a solid "Kindle Fire" logo, you can continue with the following commands...
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
The device will reboot and install FFF and TWRP.
I.will be attempting this a lil bit later today have Tiber optics installed and they are due any min.
Thankyou for your help.
Do you guys know why when I command Adb root it tells me its in.production build? This confused me.last night and I am expecting to ru. Into it mater when I attempt to do this root and twrp fix
It's because it isn't rooted. I don't think KFU has implemented BurritoRoot2 yet.
I tried downloading the 6.2.2 update and manually update but when it reboots TWRP 2 says Can't mount /mnt/sdcard/kindleupdates/update-kindle-6.2.2_D01E_3205220.bin
then TWRP gets stuck in a loop only loading into TWRP until I do "idme bootmode 4000"
Anyway, since it seems pretty safe at this point to update to 6.2.2 I want to get it over with now, but am having trouble, is the problem TWRP 2.0?
if you use the original amazon update you will loose fff, twrp and root
take a look at this update method:
http://forum.xda-developers.com/showthread.php?t=1452082
works like a charme
Has Samsung removed the ability to "adb shell" in recovery mode?
In recovery the only way the device is recognized is by sideload, and I can't access shell through that.
I could enter shell through recovery just fine with my SIII.
BTW...both stock 3e recoveries.
I will preface this with stating that this is not my phone. A friend had rooted his LG G2 and installed CWM. After he accepted the OTA, the phone was essentially rendered useless. After this process, the phone will be reverted back to 100% STOCK. It took a while to compile all of this information, and I give all credit to respective owners, but this process I pieced together from multiple threads and was able to make this work.
Symptoms-
Not booting (Hanging at LG screen)
Able to access CWM recovery
Unable to Mount USB
Unable to access Download Mode
#####1#####
Uninstall all previous LG Drivers installed (Add/Remove Programs)
#####2#####
Install PDAnet to get the drivers required installed.
#####3#####
Once PDAnet is installed, ADB should recognize the device when it is in 'Recovery' mode.
(ADB Devices should give the result of: ###DEVICEID### Recovery)
#####4#####
Download aboot.img from: http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware/10b_EUR_16G_partitions
(The file will need to be renamed to aboot.img)
#####5#####
Download: http://www.androidfilehost.com/?fid=23252070760973106
#####6#####
Extract the files we need:
g2_security
loki_patch
loki_flash
recovery.img
#####7#####
Get into a command prompt and run the following:
adb push g2_security /sdcard/
adb root
adb push loki_patch /data/local/tmp
adb push loki_flash /data/local/tmp
adb push recovery.img /data/local/tmp
adb shell "dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img"
adb shell "chmod 644 /data/local/tmp/aboot.img"
adb shell "chmod 755 /data/local/tmp/loki_patch"
adb shell "chmod 755 /data/local/tmp/loki_flash"
adb shell "/data/local/tmp/loki_patch recovery /data/local/tmp/aboot.img /data/local/tmp/recovery.img /data/local/tmp/recovery.lok"
adb shell "/data/local/tmp/loki_flash recovery /data/local/tmp/recovery.lok"
adb shell "rm /sdcard/g2_security"
adb shell "dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img"
adb shell "dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota"
adb shell sync
adb reboot recovery
Once the above is done, the phone should boot into TWRP. I shut the phone off at this point and held "Volume Up" + "Power" and Download mode now worked!
#####8#####
Uninstalled PDAnet and then followed the instructions on the following page (including installing the drivers)
#####9#####--At this point the following thread finished reverting the phone to stock.
http://forum.xda-developers.com/showthread.php?t=2448960
My only suggestion is that you RUN THE MD5 HASH to ensure the large file downloads correctly. After this was done, the phone was successfully reverted back to stock.
If you found this help, please donate and buy me a beer!
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=ZBZ8G6ZPUEN4C
Hi, your last step, a Verizon link for restoring back to stock.. I have international D802.. can I use some other rom(omni rom) instead of your last step...
Guys, this exactly worked for me.. i used D802... however, i used all verizon files only to flash and finally went to download mode and flashed stock ROM... awesome help guys.. i was about to change the PCB by spending half of mobile cost..... i am definitely getting you a case next week...
still nothing
Still stuck in fast boot mode cannot do anything in cwm
---------- Post added at 09:39 PM ---------- Previous post was at 09:35 PM ----------
Still stuck in fast boot mode cannot do anything in cwm. Please can someone help me ??????
:good:
Me too on D802 and it worked. followed exactly as instructed.
thanks bro!
Thanks so much for the guide, one problem for me.... Im on a mac... I have pdanet, and android sdk set up but i cant get the commands to work. any idea on what to use for the commands?
P.S It does find the phone just fine with ./adb devices
dtuma1980 said:
I will preface this with stating that this is not my phone. A friend had rooted his LG G2 and installed CWM. After he accepted the OTA, the phone was essentially rendered useless. After this process, the phone will be reverted back to 100% STOCK. It took a while to compile all of this information, and I give all credit to respective owners, but this process I pieced together from multiple threads and was able to make this work.
Symptoms-
Not booting (Hanging at LG screen)
Able to access CWM recovery
Unable to Mount USB
Unable to access Download Mode
#####1#####
Uninstall all previous LG Drivers installed (Add/Remove Programs)
#####2#####
Install PDAnet to get the drivers required installed.
#####3#####
Once PDAnet is installed, ADB should recognize the device when it is in 'Recovery' mode.
(ADB Devices should give the result of: ###DEVICEID### Recovery)
#####4#####
Download aboot.img from: http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware/10b_EUR_16G_partitions
(The file will need to be renamed to aboot.img)
#####5#####
Download: http://www.androidfilehost.com/?fid=23252070760973106
#####6#####
Extract the files we need:
g2_security
loki_patch
loki_flash
recovery.img
#####7#####
Get into a command prompt and run the following:
adb push g2_security /sdcard/
adb root
adb push loki_patch /data/local/tmp
adb push loki_flash /data/local/tmp
adb push recovery.img /data/local/tmp
adb shell "dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img"
adb shell "chmod 644 /data/local/tmp/aboot.img"
adb shell "chmod 755 /data/local/tmp/loki_patch"
adb shell "chmod 755 /data/local/tmp/loki_flash"
adb shell "/data/local/tmp/loki_patch recovery /data/local/tmp/aboot.img /data/local/tmp/recovery.img /data/local/tmp/recovery.lok"
adb shell "/data/local/tmp/loki_flash recovery /data/local/tmp/recovery.lok"
adb shell "rm /sdcard/g2_security"
adb shell "dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img"
adb shell "dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota"
adb shell sync
adb reboot recovery
Once the above is done, the phone should boot into TWRP. I shut the phone off at this point and held "Volume Up" + "Power" and Download mode now worked!
#####8#####
Uninstalled PDAnet and then followed the instructions on the following page (including installing the drivers)
#####9#####--At this point the following thread finished reverting the phone to stock.
http://forum.xda-developers.com/showthread.php?t=2448960
My only suggestion is that you RUN THE MD5 HASH to ensure the large file downloads correctly. After this was done, the phone was successfully reverted back to stock.
If you found this help, please donate and buy me a beer!
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=ZBZ8G6ZPUEN4C
Click to expand...
Click to collapse
My ADB keeps saying that my phone is unauthorized ;( I can only access .zip. Anyone else have this issue? Have tried multiple drivers, Sideload is the only thing that works.
Joppykid said:
My ADB keeps saying that my phone is unauthorized ;( I can only access .zip. Anyone else have this issue? Have tried multiple drivers, Sideload is the only thing that works.
Click to expand...
Click to collapse
Are you connected via PDAnet?
dtuma1980 said:
Are you connected via PDAnet?
Click to expand...
Click to collapse
I can't because I cannot turn on USB Debugging, I am stuck in the Recovery. Details of my situation are in this thread I posted. http://forum.xda-developers.com/showthread.php?t=2726985
Joppykid said:
I can't because I cannot turn on USB Debugging, I am stuck in the Recovery. Details of my situation are in this thread I posted. http://forum.xda-developers.com/showthread.php?t=2726985
Click to expand...
Click to collapse
Oh boy i got the same issue before. I just go to a local technician to have it fixed.
Joppykid said:
I can't because I cannot turn on USB Debugging, I am stuck in the Recovery. Details of my situation are in this thread I posted. http://forum.xda-developers.com/showthread.php?t=2726985
Click to expand...
Click to collapse
Same issue here. In the command prompt, anything I do returns the unauthorized device error.
EDIT- I'm going to try and sideload a custom ROM, and then flash the stock ROM after setting USB debugging to see if that helps at all. I'll let you know
Joppykid said:
I can't because I cannot turn on USB Debugging, I am stuck in the Recovery. Details of my situation are in this thread I posted. http://forum.xda-developers.com/showthread.php?t=2726985
Click to expand...
Click to collapse
Please refer to the initial post. This will only work if you can access the recovery. If you cannot access recovery, this method isn't going to work. Sorry!
dtuma1980 said:
Please refer to the initial post. This will only work if you can access the recovery. If you cannot access recovery, this method isn't going to work. Sorry!
Click to expand...
Click to collapse
Did you not see what I wrote? Recovery was the only thing I could access. This method didn't work because the RSA Token wasn't authenticated on my computer any longer. My phone was bricked. I now have a new one. Lesson learned. Make sure you have USB debugging on with an RSA token on your computer at all times.
Did you end up wiping the internal SD with the process? I am in a similar situation except I don't have a friend like you to help me out haha.
Joppykid said:
My ADB keeps saying that my phone is unauthorized ;( I can only access .zip. Anyone else have this issue? Have tried multiple drivers, Sideload is the only thing that works.
Click to expand...
Click to collapse
I factory wiped/reset my phone is CWM which got my phone to be recognized as in recovery.
I can't get past the adb shell commands to work. it keeps saying 'dd: can't open '/data/local/tmp/aboot.img' : Not a directory
I tried with the double quotations and without to see if the command would work thinking I was messing up the syntax.
perfect just saved my a$$. ota took for the 24a update. found this and i am back where i was.awesomes
Hi all.
I have this S4, screen broken, no digitizer, USB debug not enabled and can't mount with MTP for unknown reasons. The owner asked me to retrieve some saved stuff.
Ok, I installed CWM recovery via Heimdall and plugged in the usb, but can't connect to it with adb:
Code:
$ adb devices
List of devices attached
(none)
I believe CWM is running just fine, 'cause if I push vol- and then power it goes in sideload mode, and then ADB can see it:
Code:
$ adb devices
List of devices attached
1c1a1234 sideload
...but obviously, with the device in sideload mode, i can't adb pull from it.
Any suggestions?
Try Philz recovery for adb. I think I had issues in the past with cmw and twrp when using adb.
Lennyz1988 said:
Try Philz recovery for adb. I think I had issues in the past with cmw and twrp when using adb.
Click to expand...
Click to collapse
.....aaaand this one made the trick!
Misson accomplished and reputation honored! Thanks!