kfu is failed install twrp...how to bootloader uninstall or unlock in cmd?i want root......
icolt said:
kfu is failed install twrp...how to bootloader uninstall or unlock in cmd?i want root......
Click to expand...
Click to collapse
I can help you. Please follow below step.
install TWRP:
1.Package You need：
a.Kindle Fire 6.2.2 image file
b.TWRP package
2.after install driver，you can input below command under CMD:
fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img
3.Root Step:
If you want to root your KF,You must use the 6.2.2 firmware.
root command:
adb push root/su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb remount
adb install root/Superuser.apk
adb reboot
attachment is the root file you need.
2012androidfans said:
I can help you. Please follow below step.
install TWRP:
1.Package You need：
a.Kindle Fire 6.2.2 image file
b.TWRP package
2.after install driver，you can input below command under CMD:
fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img
3.Root Step:
If you want to root your KF,You must use the 6.2.2 firmware.
root command:
adb push root/su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb remount
adb install root/Superuser.apk
adb reboot
attachment is the root file you need.
Click to expand...
Click to collapse
in 6.3version?????
icolt said:
in 6.3version?????
Click to expand...
Click to collapse
NO, ONLY FOR 6.2.2 or 6.2.1.
Hey y'all,
I am rooting / rom-ing my third KF.
I could not get TWRP to install so I installed CWM that comes with the KFU
I installed Jandycane and the most current gapps
From then on, the Kindle gets stuck at the boot animation
I have tried other options in KFU, but everything involving fastboot does not work. The kindle shows up as a composite device in the device manager, and is able to be adb-ed into.
In KFU, I see the bootmode being 4000. When I tried the idme command to change it to recovery, it told me that it could not accept the idme command.
I've tried going using the adb shell to push fiels and create directories, but have failed. Su does not work, mkdir does not work, and chmod does not work.
Additionally I have tried the KF Unbrick 1.1 and none of the options seem to do anything.
I am running out of options here. I have tried these procedures on two PCs without avail.
Before I installed the current rom, I have made a backup of the stock rom. Is there any way I could adb into the device and restore it? Would this be a valid way to fix this up?
Can anyone suggest anything else that I have not tried?
Anyone?
When I try to push fbmode from here: http://forum.xda-developers.com/showthread.php?t=1414832
Code:
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>adb push fbmode /data/local/tmp
failed to copy 'fbmode' to '/data/local/tmp': No such file or directory
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>
Now lets see if I can escalate my privileges
Code:
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>adb shell
[email protected]:/ $ su
su
Segmentation fault
[email protected]:/ #
Now lets see if I can push fbmode regardless
Code:
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>adb shell
[email protected]:/ $ cd /data/local/tmp
cd /data/local/tmp
/system/bin/sh: cd: /data/local/tmp: No such file or directory
2|[email protected]:/ $ cd /data/local/
cd /data/local/
/system/bin/sh: cd: /data/local: No such file or directory
2|[email protected]:/ $ cd /data/
cd /data/
[email protected]:/data $ ls
ls
opendir failed, Permission denied
255|[email protected]:/data $
So much for adb ... how about that fastboot
Every time I do anything with fastboot it says waiting for device:
Code:
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>fastboot -i 0x1949 flash recovery twrp.img
< waiting for device >
Are there any devices showing?
Code:
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>fastboot devices
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>adb devices
List of devices attached
0123456789ABCDEF device
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>
fastboot does not see any devices whereas adb does...
I have tried sending the fastboot command while the device is off and then turning it on. The kindle just hangs at the kindle fire screen.
EDIT: I switched computers, and it got back into previous state at being stuck at the animation screen
This is what happens when I try to install TWRP in KFU:
Code:
Installing TWRP...
If we get stuck here for awhile, power the kindle on and off a few times.
You should also check device manager for "kindle" If so, rerun the driver
installer that came packaged with KFU.
***********************************************
* Activating Fastboot (4002) *
***********************************************
failed to copy 'files\fbmode' to '/data/local/fbmode': No such file or directory
Unable to chmod /data/local/fbmode: No such file or directory
/system/bin/sh: /data/local/fbmode: not found
The kindle has been told to reboot in Fastboot Mode.
< waiting for device >
Can you actually put your device into fastboot mode? You can only use fastboot commands when the bootloader has put the device into fastboot mode. If you can get output from any adb commands, you are not in fastboot mode. Look at this guide and see if you can put the KF into fastboot mode...
http://forum.xda-developers.com/showthread.php?t=1668159
What bootloader do you have installed on the device? (Describe the first bootlogo you see. Refer to the above guide.)
What error do you get when you attempt to set the bootmode with idme?
Where are you running your adb commands? When you are stuck on the boot animation or in recovery?
Can you even get to your recovery?
My guess is you've somehow corrupted the system software on your ROM installation. If you can get to recovery, you'll probably need to reflash your ROM. If you can get the device into fastboot mode, you can get to recovery. If can't do either of those, you'll need a factory cable or be willing to open up the case.
kinfauns said:
Can you actually put your device into fastboot mode? You can only use fastboot commands when the bootloader has put the device into fastboot mode. If you can get output from any adb commands, you are not in fastboot mode. Look at this guide and see if you can put the KF into fastboot mode...
http://forum.xda-developers.com/showthread.php?t=1668159
What bootloader do you have installed on the device? (Describe the first bootlogo you see. Refer to the above guide.)
What error do you get when you attempt to set the bootmode with idme?
Where are you running your adb commands? When you are stuck on the boot animation or in recovery?
Can you even get to your recovery?
My guess is you've somehow corrupted the system software on your ROM installation. If you can get to recovery, you'll probably need to reflash your ROM. If you can get the device into fastboot mode, you can get to recovery. If can't do either of those, you'll need a factory cable or be willing to open up the case.
Click to expand...
Click to collapse
That would make sense. I cannot change the bootmode from 4000, so that's why fastboot does not work. I feel dumb for not thinking this through.
It has CWM installed as I could not load TWRP initially due to a poor connection.
This is what I get when I try to change the bootmode:
Code:
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>adb shell su -c 'idme bootmode 4002'
Segmentation fault
<idme> write 4002 to offset 0x1000
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>adb shell idme bootmode 4002
<idme> Invalid permission
I cannot get into recovery as I cannot get the tablet to boot into anything but the ROM istelf (or try to, as it never boots into anything but just loops the boot animation)
Tell me about this factory cable. I'm sure I have it somewhere among all of my micro USB cables...
The boot pattern is as follows: kindle fire (white orange/stock) -> jandycane boot animation that runs forever
There is no triangle or any press the power button to boot into recovery.
http://forum.xda-developers.com/showpost.php?p=30376760
soupmagnet said:
http://forum.xda-developers.com/showpost.php?p=30376760
Click to expand...
Click to collapse
I cannot get the kindle to boot into a ROM, so I cannot use the terminal app.
Can I get an adb shell and push these files?
Also, per my post above, it seems that something sketch is going on with my superuser settings...
Yes, if you have a working adb, you can absolutely push those files. The path will be slightly different though. Instead of ~/local/tmp, you will push the files to /data/local/tmp then execute:
Code:
adb shell chmod 755 /data/local/tmp/rcmode
adb shell /data/local/tmp/rcmode
Looking through your other posts I see you are trying to invoke the shell and enter the commands seperately. Try again, but only this time add "adb shell" to the command itself, as above, and see if that makes a difference.
Also, I've seen both /data/local and /data/local/tmp used but I've always used /data/local/tmp
[Edit:] if you still get a "No such file or directory" error, see if you can create it:
Code:
adb shell mkdir /data/local/tmp
Zlatty said:
I cannot get the kindle to boot into a ROM, so I cannot use the terminal app.
Can I get an adb shell and push these files?
Also, per my post above, it seems that something sketch is going on with my superuser settings...
Click to expand...
Click to collapse
KFU's included version of CWM recovery does not flash ICS (and very likely JB) ROMS correctly. This is a bug known to corrupt the flash.
It not likely you'll be able to do anything meaningful with the system currently installed on your Kindle Fire. Unfortunately for you, that probably includes using idme or pushing anything that might help you change bootmodes. Of course, I may be wrong and you might find another way out of the mess, but the easiest way for you to fix this is to use a factory cable, put the KF into fastboot mode, flash TWRP, boot into recovery so you can flash a new bootloader and ROM.
factory cable...
http://forum.xda-developers.com/showthread.php?t=1550999
fastboot mode...
http://forum.xda-developers.com/showthread.php?t=1668159
beginner's guide...
http://forum.xda-developers.com/showthread.php?t=1552547
supplement for rooting... installing a ROM... etc...
http://forum.xda-developers.com/showthread.php?t=1638452
EDIT: You can try what soupmagnet suggested while I was typing out my post, but you've already shown that you cannot access the /data partition. I think it's going to be something more than simply just an unmounted partition.
I hadn't really thought about mounting the data partition...it's worth a shot either way.
soupmagnet said:
I hadn't really thought about mounting the data partition...it's worth a shot either way.
Click to expand...
Click to collapse
Well my adventure just keeps getting worse and worse. I charged the kindle last night to ensure enough battery life for today. It is suck at the kindle fire logo now. I have the drivers loaded correctly and my computer sees the kindle. However I cannot adb or fastboot the device. It also went from composite device to adb device in the device manager.
EDIT:
Was able to install FFF and got to boot into recovery. CWM 5.2.0.7.
In adb I tried to get super user permissions
C:\android-sdk-windows\platform-tools>adb shell
~ # su
su
/sbin/sh: su: not found
~ #
Click to expand...
Click to collapse
What are my options at this point. KFU cannot download and install TWRP. I cannot manually push it since I dont have su. KFU's install super user function does not work as it tries to install TWRP.
Zlatty said:
Well my adventure just keeps getting worse and worse. I charged the kindle last night to ensure enough battery life for today. It is suck at the kindle fire logo now. I have the drivers loaded correctly and my computer sees the kindle. However I cannot adb or fastboot the device. It also went from composite device to adb device in the device manager.
EDIT:
Was able to install FFF and got to boot into recovery. CWM 5.2.0.7.
In adb I tried to get super user permissions
What are my options at this point. KFU cannot download and install TWRP. I cannot manually push it since I dont have su. KFU's install super user function does not work as it tries to install TWRP.
Click to expand...
Click to collapse
Ok, so while I was in CWM, I mounted the SD card, downloaded and transfered a flashable TWRP found here http://forum.xda-developers.com/showpost.php?p=28664718&postcount=127
I flashed the zip and now I have TWRP working.
Zlatty said:
Ok, so while I was in CWM, I mounted the SD card, downloaded and transfered a flashable TWRP found here http://forum.xda-developers.com/showpost.php?p=28664718&postcount=127
I flashed the zip and now I have TWRP working.
Click to expand...
Click to collapse
I could not get twrp to boot into normal. So I used KFU to change to 4000 mode.
Code:
***********************************************
* Activating Normal (4000) *
***********************************************
< waiting for device >
... OKAY [ 0.081s]
finished. total time: 0.082s
rebooting...
finished. total time: 0.001s
The kindle has been told to reboot in Normal Mode.
Press any key to continue . . .
Everything went better than expected.... w00t!
So I am trying to manually root my S3 without flashing a rom. I am able to get through most of the steps in these instructions up to the point where it requires you to put phone into download mode. I get phone into download mode, but when I connect to the PC, it doesn't see the phone.
This step worked:
To confirm your device is properly detected, in the command prompt, run
Code:
adb devices
Now copy busybox, su, superuser.apk to /data/local/tmp/ using adb.
Code:
adb push busybox /data/local/tmp adb push su /data/local/tmp adb push Superuser.apk /data/local/tmp
These steps worked:
Now run adb shell
Code:
adb shell
Note that you see a "$" sign in the command prompt. That means you are not rooted.
Next run the following commands in the shell to change permissions and get some limited privileges for the Superuser files:
Code:
chmod 6755 /data/local/tmp/su chmod 755 /data/local/tmp/busybox chmod 644 /data/local/tmp/Superuser.apk
Note that the names of the files are case sensitive.
Files are there and are verified when I ls /data/local/tmp. All three files are there.
This is where I have a stumbling block:
Once in download mode, connect the Android device using the microusb cable to the computer.
Now using the open Nautilus window, navigate to /UserData/local/tmp/ folder and verify that you have the files you sent to the device viz. su, busybox and Superuser.apk
So if I am able to push files to the phone, why won't it recognize it when in download mode?
Using Fedora Linux and have the full Android SDK installed.
Hello!
I bought already DZ and everything is fine, but the system of keyboard is pissed off So, I was thinking if is any way to change that when Im opening a phone automatically screen is turned on. I would like to change that, because sometimes when im taking him the phone is trying to open, because of best opening system Screen should turn on only if I will press the power button. Any idea how to resolve that? I'd really appreciate that.
root DZ
IM NOT RESPONSIBLE TO BRICKED DEVICE(S), APOCALYPSE, GLOBAL WARMING AND NUCLEAR WAR
IT WORKED 4ME BUT MAY NOT WORK 4YOU
Download: Attachments (unzip Root.zip to C:/htc/ directory, then copy PC10IMG.zip and .apk files to C:/htc/) PC10IMG.zip link has been dended to your XDA mailbox
Then:
unpack attachment to C:/htc (example)
copy System32.zip files to C:/Windows/System32/
TempRoot:
Run cmd and type:
Code:
adb push C:\htc\fre3vo /data/local/tmp
adb shell
chmod 777 /data/local/tmp/fre3vo/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
This will kick you srom the device shell , but dont worry and DO NOT reboot your device
Change Misc Version:
Code:
adb push C:\htc\misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
/data/local/tmp/misc_version -s 1.33.405.5
To get:
Code:
--set_version set. VERSION will be changed to: 1.33.405.5
Patching and backing up partition 17...
Then type:
Code:
sync
Now you must type this GOOD (fail=brick) (still in shell!!!):
Code:
dd if=/dev/block/mmcblk0p17 bs=1 skip=160 count=10
Then type:
Code:
exit
Then copy PC10IMG.zip package:
Code:
adb push C:/htc/PC10IMG.zip /sdcard/PC10IMG.zip
CMDline wont response for 6-10 minutes, its fine, its good
When finish type:
Code:
adb reboot bootloader
Wait until bootloader parse package and press VOL-UP
DO NOT POWER-OFF YOUR DEVICE (PLUG IT TO CHARGER)
When it finish, press POWER button to reboot
You dont must set up android
Switch on usb-debugging (settings/apps/develop)
then plug it to pc and type in cmd:
Code:
adb install C:\htc\AndroidTerm.apk
adb install C:\htc\TotalCommander.apk
adb push C:\htc\busybox /data/local/tmp/
adb push C:\htc\gfree /data/local/tmp/
adb push C:\htc\rage /data/local/tmp
adb push C:\htc\root /data/local/tmp/
adb shell chmod 0755 /data/local/tmp/*
adb push C:\htc\su /sdcard/
adb push C:\htc\Superuser.apk /sdcard/
Then launch Terminal emulator and type:
Code:
/data/local/tmp/rage
to get
"forked xxxxxx childs"
Tap "menu" and select "reset term"
It will kill the terminal
Launch Terminal emulator again, but you will get error wit "force close" (force close it)
Launch Terminal Emulator again and type:
Code:
/data/local/tmp/gfree -f
/data/local/tmp/root
sync
close terminal emulator and launch Total Commander
Go to "system directory" and try to open /data
If succeed (Superuser request): TOU DID (S-OFF, Super-CID (no simlock), root)
You can use RootKeeper.apk to "survive" su binary when installing OTA update (you can root android 2.2 but no android 2.3.3)
Disable root keeper when making nandroid
When you have root you can modify it with flashing another rom
Please hit thanks button
I read that few times to be sure what ive got to do, so tommorow im gonna do the operation Man, you are awsome. In one time I will get root (im doing that from time, when i wrote that thread) and resolve of my unlocking problem Hope, that i will not get lost on that. Cant wait for tommorow..
unlocking DZ
I forgot about one thing: after /data/local/tmp/root you can get error, but it's fine too
If you dont want to check root with Tcmd type "su" in terminal
Hello,
I was browsing many topics for over 5 hours until I decided to ask this question so I hope it will not be obvious.
I'm having an Marvell PXA1920 CPU based Android 4.3 phone - Lenovo A788t.
It was rooted using some one-click application, so I did have access to superuser, SuperSU installed etc.
After some modifications done in /etc/permissions and rebooting, phone's entering an infinite loop.
All I need to do now is undo those changes, deleting those files and copying files from backup in another folder. However, for that I need access to /etc with /system remounted in rw mode.
I can access my phone using adb in "Product mode" (phone turned on with lower-volume button pressed), however it seems that from there I don't have root access, so:
I've tried following commands:
1. adb root
result: adbd cannot run as root in production builds
2. adb remount
result: remount failed: Operation not permitted
3. adb shell mount -o rw,remount /system
result: mount: Operation not permitted (in general, no matter what I'm trying to mount/remount)
4. adb shell su
result: the same as echo "su" - prints "su", but does not cause entering su
5. adb shell su -c 'mount -o rw,remount /system'
result: prints command, but does not execute proper action
6. adb shell busybox ...
result: causes the same as all above (operation not permitted)
It seems that phone doesn't support fastboot (adb reboot bootloader doesn't work)
I know that I can do hard reset, but I don't really want to lose all my data and configuration.
Is there anything else what I can do?
Thanks for help in advance