Cannot root KFHD 7 - 7" Kindle Fire HD Q&A, Help & Troubleshooting

Cannot root KFHD 7 - 7" Kindle Fire HD Q&A, Help & Troubleshooting

Hi everybody,
I've done all the steps from this topic http://forum.xda-developers.com/showthread.php?t=1891939. And it looks like no problems appeared during installation (ADB Interface appeared in Device Manager tree, Device can be found by adb in cmd, no any exepions or errors during cmd installation).
The only problem at the end - device is not rooted. In ES FileManager root access doesn't work. Superuser app doesn't appears in the list (but when I tried to install it for the secon time in cmd, it says that Superuser.apk is already installed).
So I've tried twice, but have't succeed. Could you please assist with the possible reason for the failture?

Related

Rooting G1 - Telnet prompt showing question marks in diamonds? Help!

I have rooted my phone once before like a year ago, and it worked like a charm - but when the official 1.6 came out it apparently unrooted me (I assume thats what happened?) All I know is now when I try to run root required apps it tells me I'm not rooted.
So I figured to just start over from the beginning. I downgraded to RC29 no problem, but when I get to the telnet step it shows a pattern of question marks in diamonds, with boxes separating them. Like this:
<?><?>[]<?><?>[]<?><?> <?><?>[]<?><?> #
I run the commands anyway, (with the Recovery Image and HardSPL on the root of my SD card) - with each command returning two hash marks # #. But the commands don't seem to do anything, because even when I finish ROM Manager tells me I'm not rooted.
Back in Telnet, I can 'ls' to see my directories, including a root folder - but I'm not sure that means anything.
Not sure where to go from here - any help would be greatly appreciated...
-TQ

........................................

The following Observation was made :
Wrong Section. Belongs in Q/A
K so when u go in adb and type adb shell do you see # or $
Please let us know.

Apologies for posting in the wrong forum. And thanks for moving it.
I can't connect to my phone via ADB - I just get 'device not found' even though I have the USB drivers downloaded. If I do 'adb devices' it shows a blank list.
I've looked into how to resolve this, but with no luck. The phone shows up in device manager under the 'Disk Drives' category as "HTC Android Phone USB Device" when everywhere I read says it should show up under the ADB interface section as "HTC Dream Composite ADB Interface".
I've tried USBDeview to reinstall it properly - no dice. And I tried manually updating the driver with ones I downloaded, but windows says I already have the best driver installed.
I don't know what to do now...

[Q] No usb connect?

Had to factory reset kfhd7 and when I did, it booted up like an android phone. ... Now there's no browser and I can't get play to work. Usb debug is enabled but when I connect to the computer to try and push a browser, my computer doesn't recognize it. I have all the newest drivers installed and just about every program that I can think of (adb, sdk, jdk) What I don't have is a fastboot cable. Any ideas?
Missing my kindle
Edit* So I do have chrome installed but when I open it, I get an error message saying "critical functionality required to run chrome is missing; either your chrome installation is incomplete, or not compatible with this version of android"
Terminal emulator installed too but when I try to open it I get a "terminal emulator has stopped" error.
Super SU installed, works.
No es file explorer
edit#2
Ok, so I decided to open cmd just to see if I can recognize my device.... and it did! So how can I fix my kindle if adb is connecting?
Edit#3 adb devices shoes device but when running a command, it says "device offline"....
Edit#4 plugged usb into another port and reloaded drivers = adb connects, device is online. I have tested by pushing an app to the sdcard. My goal now is to be able to push es file explorer to /system/app/ .... or ..... /data/app/ ...... or where ever it will become active for use. (you know what I mean?) I don't know how to change the permissions via adb and push to system folder. I believe I have successfully pushed es file explorer to the /sdcard/ but I have no idea where to go next.
Now what..... ?

How to Install Packages using adb install
Krsmqn said:
Had to factory reset kfhd7 and when I did, it booted up like an android phone. ... Now there's no browser and I can't get play to work. Usb debug is enabled but when I connect to the computer to try and push a browser, my computer doesn't recognize it. I have all the newest drivers installed and just about every program that I can think of (adb, sdk, jdk) What I don't have is a fastboot cable. Any ideas?
Missing my kindle
Edit* So I do have chrome installed but when I open it, I get an error message saying "critical functionality required to run chrome is missing; either your chrome installation is incomplete, or not compatible with this version of android"
Terminal emulator installed too but when I try to open it I get a "terminal emulator has stopped" error.
Super SU installed, works.
No es file explorer
edit#2
Ok, so I decided to open cmd just to see if I can recognize my device.... and it did! So how can I fix my kindle if adb is connecting?
Edit#3 adb devices shoes device but when running a command, it says "device offline"....
Edit#4 plugged usb into another port and reloaded drivers = adb connects, device is online. I have tested by pushing an app to the sdcard. My goal now is to be able to push es file explorer to /system/app/ .... or ..... /data/app/ ...... or where ever it will become active for use. (you know what I mean?) I don't know how to change the permissions via adb and push to system folder. I believe I have successfully pushed es file explorer to the /sdcard/ but I have no idea where to go next.
Now what..... ?
Click to expand...
Click to collapse
Krsmqn,
Sorry for the delayed response, we have been real busy the last few days. You may use the
following command to install or reinstall software on the Kindle:
Code:
adb kill-server
adb start-server
adb devices
android update adb
If adb is working move on to install software:
Code:
adb install package-whatever.apk
You need to make sure the .apk software package in in the same directory as adb. If
you can not get the Kindle stable you may need a USB Factory Cable, you may order
one from XDA User SkOrPn just send him a PM with the subject Factory Cable Info Please,
include your ship to country and number of cabled needed. He will respond with a PayPal
Invoice. The cable is about $15 USD and is worth every penny since it allows quick
recovery of your Kindle.

prokennexusa,
I want to thank you for all your help. Unfortunately, my issue was kind of a rare issue. I had deleted some amazon apps that were system apps. I tried your solution time and time again to no avail. I was stumped until I remembered a thread I saw in development.
http://forum.xda-developers.com/showthread.php?t=1886189
I was able to download and unzip the 7.2.3 update version and simply install the apks that I was missing. Then, as far as google play went, I just went into System>Applications>Installed Applications>Appstore (Amazon)> Force stop, clear data & cache. Reinstalled Vendor.apk and then updated. Viola!
The USB notification came back, as well as all the other options in settings. Problem solved. Hope this helps future users.

Follow Up - Feedback
Krsmqn said:
prokennexusa,
I want to thank you for all your help. Unfortunately, my issue was kind of a rare issue. I had deleted some amazon apps that were system apps. I tried your solution time and time again to no avail. I was stumped until I remembered a thread I saw in development.
http://forum.xda-developers.com/showthread.php?t=1886189
I was able to download and unzip the 7.2.3 update version and simply install the apks that I was missing. Then, as far as google play went, I just went into System>Applications>Installed Applications>Appstore (Amazon)> Force stop, clear data & cache. Reinstalled Vendor.apk and then updated. Viola!
The USB notification came back, as well as all the other options in settings. Problem solved. Hope this helps future users.
Click to expand...
Click to collapse
Krsmqn,
Great post Krsmqn, I am glad to hear your problems are solved! We offer a fresh copy of the /system/app
folder here: https://dl.dropbox.com/u/54456659/app.zip
Anyone who is experiencing odd issues can download this folder and side load it back to the Kindle through
adb or ES File Explorer. Thank you again, I was getting a bit worried.

[SOLVED] adb error device not found CWM-Recovery

Hi,
Current setup :
Xperia z1 C6903
Three UK
Version 4.4.4
Build 14.4.a.0.108
Rooted
Unlocked Bootloader
adb drivers installed (on xp)
Trying to install Cyanogen Mod.
Flash boot boot .img all worked fine and have CWM recovery screen up.
When I try to use either sideload or adb push I get the same error:
error: device not found
I've googled and searched here and seems to be a driver issue with adb?
I have android SDK (eclipse) and SDK platform tools installed
any thoughts please?

....

...

SOLVED adb driver problem xp device not found
OK, working using universal driver from
http://www.koushikdutta.com/post/universal-adb-driver
Absolutely no idea why XP stopped seeing the phone, and no attempt at driver/sdk updates worked, tried all the ADB drivers I could find including one above, nothing...
then changed usb post after i uninstalled the device from manager (for the 100th time) and ran the adb installer again. and tada there it was :/
hopefully link above might help someone on xp get adb connection working if they are having problems..

Rooted with kingroot and replaced with SuperSu, TWRP and Xposed

Hi everyone. My aim here is to present a more clear Tutorial... not sure if i'll succeed, but i want to try. :good: Good Luck. Your results may be different.
A word of Caution: These steps will soft brick the phone and erase all data from your phone. Proceed with caution.
A huge thanks to:
emowing
quyvinh
jemmini
John Hale
kingroot
I refered to these posts when I was rooting:
http://forum.xda-developers.com/vivo-xl/how-to/root-tutorial-t3313120
http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
Download the BLU Vivo XL Backup from https://www.dropbox.com/s/x4lgfv27jtgirkh/Blu_VivoXL_backup-2016-03-05.zip . This is required to unbrick the phone.
WARNING: THE METHOD I FOLLOWED WILL ERASE ALL DATA ON THE PHONE. I really didn't care for the data on the phone so I didn't create a backup. You could google for steps to make a backup before continuing.
I did these on a Windows 7 machine. I didn't take any screenshots. This was totally random effort.
1. Ensure ADB Universal Drivers, adb.exe and fastboot.exe are installed. Use google search. I used this one http://rootjunkysdl.com/?device=Amazon Fire 5th gen. Even though it is for Amazon 5th gen Fire tablet, it worked for BLU Vivo XL
2. Enable 'Developer Options'
3. Enable 'USB Debugging'
4. Connect the phone to the computer.
If you are doing this for the first time then...
The phone will show up as a new 'cd' drive
Open that and you should see the software to install official drivers for the phone
Install the drivers using that software.
If you have previously connected the phone then it will show up like a 'USB flash storage' device with 2 partitions - Phone and SD Card5. Run 'adb.exe' in command prompt ( i assume you know how to do this)
6. Run adb devices and make sure that adb is able to communicate with the phone.
At some point, there will be a pop up on the phone with a key to enable the computer to securely connect to the phone. I don't know what this is called , but it is needed. Make sure you choose to remember this key permanently on the phone.
7. Root the phone with 'Kingroot' (Yes, this is odd, but this is required to get the TWRP recovery to load)
The reason i say this is needed is because without the root when I tried to install the TWRP recovery i got the error saying that there is no root access and therefore TWRP recovery file cannot be copied to the phone
[a] go to kingroot (dot) net and get the latest kingroot apk
try to root with kingroot. the first time i did this it didn't work. kingroot app said there is 'root' method available but it couldn't root.
[c] i uninstalled kingroot
[d] then i installed purify from play store
[e] rebooted the phone
[f] installed kingroot again and tried root again and this time it worked. (go figure...)
[g] so YMMV.
if you rooted successfully with Kingroot, then you can continue, otherwise.... try again till you can root with kingroot

8. reboot the phone
9. Go to developer options and enable the option - 'Enable OEM Unlock'
CAUTION: The next steps will soft brick your phone.
10. Run adb.exe. check connectivity using command 'adb devices'
11. Run command 'adb reboot bootloader' (this will put the phone in fastboot mode)
12. Make sure the TWRP recovery is in the same folder as the adb.exe file. (get the twrp recovery from here http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601)
13. Run command 'fastboot oem unlock'. At this point, there will be a prompt on the phone to confirm the action. Read it carefully, it clearly says that this process will wipe all data.
14. Press 'volume up' on the phone to confirm. It should take a few seconds. Then the phone will become unresponsive. Pressing volume up/down buttons or power button doesn't do anything.
15. Run command 'fastboot reboot-bootloader'
16. Run command 'fastboot flash recovery recovery.img'
17. Run command 'fastboot reboot'. When the phone is rebooting press volume up. If everything went well, This will put the phone in TWRP recovery mode.
18. When the phone enters TWRP recovery mode, it'll ask for 'write permissions'. I swiped to enable the write permissions.
19. At this point, the phone has no OS.
20. On the PC, extract the files downloaded from https://www.dropbox.com/s/x4lgfv27jtgirkh/Blu_VivoXL_backup-2016-03-05.zip
21. With the phone connect to the PC and adb running. Run command adb devices. The phone must be listed as 'xxxxxxxxxxxxxxxxx recovery'
22. You will have to push the back up files to twrp backup using adb
23. The general command is 'adb push <local> <remote>'. This is what i did for each of the files. Be patient, this will take time.
adb push "C:\boot.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/boot.emmc.win
adb push "C:\logo.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/logo.emmc.win
adb push "C:\logo.emmc.win.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/logo.emmc.win.md5
adb push "C:\nvram.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/nvram.emmc.win
adb push "C:\nvram.emmc.win.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/nvram.emmc.win.md5
adb push "C:\secro.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/secro.emmc.win
adb push "C:\secro.emmc.win.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/secro.emmc.win.md5
adb push "C:\system.ext4.win000" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/system.ext4.win000
adb push "C:\system.ext4.win000.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/system.ext4.win000.md5
adb push "C:\system.ext4.win001" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/system.ext4.win001
24. Once all the files are copied to the phone. Go to TWRP Restore option and then do a restore from the backup you just uploaded 2016-03-05.
25. After the restore is successfull and complete, TWRP will automatically ask to install 'SuperSu'.
26. Choose 'yes' and install SuperSu
27. TWRP will recover the phone and root the phone with SuperSu
If all of the above worked then install Xposed as per instructions in http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
GOOD LUCK !!! :good::good::good:

Please help me on rooting my Blu vivo XL I upgraded it to Android 6.0 and now it does not root. Please help.

hamilLewiston said:
Hi everyone. My aim here is to present a more clear Tutorial... not sure if i'll succeed, but i want to try. :good: Good Luck. Your results may be different.
A word of Caution: These steps will soft brick the phone and erase all data from your phone. Proceed with caution.
A huge thanks to:
emowing
quyvinh
jemmini
John Hale
kingroot
I refered to these posts when I was rooting:
http://forum.xda-developers.com/vivo-xl/how-to/root-tutorial-t3313120
http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
Download the BLU Vivo XL Backup from https://www.dropbox.com/s/x4lgfv27jtgirkh/Blu_VivoXL_backup-2016-03-05.zip . This is required to unbrick the phone.
WARNING: THE METHOD I FOLLOWED WILL ERASE ALL DATA ON THE PHONE. I really didn't care for the data on the phone so I didn't create a backup. You could google for steps to make a backup before continuing.
I did these on a Windows 7 machine. I didn't take any screenshots. This was totally random effort.
1. Ensure ADB Universal Drivers, adb.exe and fastboot.exe are installed. Use google search. I used this one http://rootjunkysdl.com/?device=Amazon Fire 5th gen. Even though it is for Amazon 5th gen Fire tablet, it worked for BLU Vivo XL
2. Enable 'Developer Options'
3. Enable 'USB Debugging'
4. Connect the phone to the computer.
If you are doing this for the first time then...
The phone will show up as a new 'cd' drive
Open that and you should see the software to install official drivers for the phone
Install the drivers using that software.
If you have previously connected the phone then it will show up like a 'USB flash storage' device with 2 partitions - Phone and SD Card5. Run 'adb.exe' in command prompt ( i assume you know how to do this)
6. Run adb devices and make sure that adb is able to communicate with the phone.
At some point, there will be a pop up on the phone with a key to enable the computer to securely connect to the phone. I don't know what this is called , but it is needed. Make sure you choose to remember this key permanently on the phone.
7. Root the phone with 'Kingroot' (Yes, this is odd, but this is required to get the TWRP recovery to load)
The reason i say this is needed is because without the root when I tried to install the TWRP recovery i got the error saying that there is no root access and therefore TWRP recovery file cannot be copied to the phone
[a] go to kingroot (dot) net and get the latest kingroot apk
try to root with kingroot. the first time i did this it didn't work. kingroot app said there is 'root' method available but it couldn't root.
[c] i uninstalled kingroot
[d] then i installed purify from play store
[e] rebooted the phone
[f] installed kingroot again and tried root again and this time it worked. (go figure...)
[g] so YMMV.
if you rooted successfully with Kingroot, then you can continue, otherwise.... try again till you can root with kingroot

Yes
Sent from my chronos_ace using XDA Free mobile app

Yes, is it for marshmallow? Or yes, is it for lollipop? Or does it work for both? Please clarify.

Please help ME my phone vivo v 5 plus root How To

Gungho-sd said:
Yes, is it for marshmallow? Or yes, is it for lollipop? Or does it work for both? Please clarify.
Click to expand...
Click to collapse
From what I've read this would only work for Lollipop, as apparently kingroot no longer works on Marshmallow.

Changing /system folder permissions causes bootloop

Alright, maybe I did something stupid, but I don't think so...
I unlocked the bootloader, used the R2 version to remotely launch TWRP (can't get the phone to do it) and then rooted with Magisk. All as recommended.
Ad Away wouldn't work because the permissions weren't set right for system/etc/host directory. So, I used Solid Explorer to change the system directory permissions (rwxrwxrwx -R). Probably overkill, but just wanted to eliminate the issue of permissions.
Shortly after executing the command, I got an error "couldn't remount" and the phone rebooted into a bootloop, which leads to a recovery that won't launch (TWRP won't launch from the phone).
I can stop the bootloop and get into the bootloader, but can't "see" the phone in PC ADB.
Anyone have advice on how to proceed?

In bootloader or recovery it wont be ADB but Fastboot. Try "fastboot devices" and see if the pc sees it.
Also Magisk is a systemless root and they have in option in their main app to allow host file to be written to system/ect/host/.

Database Develop

welcome