kingroot infected? - Fire HD 8 and HD 10 Q&A, Help & Troubleshooting

Hello all,
I recently started to get lots of popads on my device, so I ran my usual scan with Malwarebytes and it came up with KingRoot being heavily infected with malware. I cant uninstall, since its what i used to root and its also a system app. Any help?

loganwaffle8 said:
Hello all,
I recently started to get lots of popads on my device, so I ran my usual scan with Malwarebytes and it came up with KingRoot being heavily infected with malware. I cant uninstall, since its what i used to root and its also a system app. Any help?
Click to expand...
Click to collapse
see rootjunky's supersume video
https://www.youtube.com/watch?v=3O3DcpeS_Ic
or manually install supersu with a terminal emulator
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html

Ill try the rootjunky method in a few hours, I tried the terminal emulator installed and it just forceclosed all apps and rebooted.
Sent from my KFTBWI using XDA Labs

So I got a bit impatient, and decided to retry the w0lfdroid method. The same thing happened from last time (apps wouldnt open) and so I decided to reboot.
As the device began to shutdown, SuperSU appeared for a few seconds, then my device switched off. I believe I have bricked my device as it has been stuck on the 'fire' logo for the past 10 minutes. Congrats to me ._.

I tried to install adb and its drivers, however drivers wouldnt install saying 'windows couldnt find any driver software for you device' when i point it to the drivers. Any idea why?

loganwaffle8 said:
I tried to install adb and its drivers, however drivers wouldnt install saying 'windows couldnt find any driver software for you device' when i point it to the drivers. Any idea why?
Click to expand...
Click to collapse
Download kindle_fire_usb_driver.zip from Amazon site
Connecting Your Fire Tablet for Testing or XDA
extract files
run KindleDrivers.exe
Then manually select drivers
Open device manager Settings>Devices>Device Manager
Connect Kindle Fire
Enable USB debugging
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface for Stock rom or recovery/adb sideload
Select Android ADB interface for Fastboot mode
or Android Composite ADB interface
next
you may have to reboot pc
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my KFFOWI using XDA Labs

Thanks
Have I done it right? I hope I've done everything. Also when I open ADB a load of text flashes down the cmd box for about a second then it closes. Ran as administrator and everything. Hoping I can get this fixed by the weekend...

Ok, I think I got it.
Doing adb devices gives me G000HH0454340LB9, I beleive this is the correct device?
Anyways, plan is:
Boot into recovery on device and select apply update from adb
Get the 5.1.1 update (firmware it originally had) and place it in the folder adb installed in.
Do adb sideload (file name)
Wait (maybe grab a cup of coffee?)
Hopefully success, back to stock firmware!
Afterwards ill root with kingroot and then remove using rootjunky supertool.

Ok, this is getting kinda annoying.
Placed the update-kindle-32.5.4.1_user_541112720 .bin file in the same folder I have adb installed.
Booted devices into recovery mode, selected apply update from adb
Open adb, do adb sideload update-kindle-32.5.4.1_user_541112720
Get error message 'cannot read update-kindle-32.5.4.1_user_541112720'
Have ALL correct drivers and stuff installed @sd_shadow

Can anyone help? I really need this fixing...

loganwaffle8 said:
Can anyone help? I really need this fixing...
Click to expand...
Click to collapse
try downloading the firmware again, or try a different version like 5.1.2
which version is on it now?
Sent from my KFFOWI using XDA Labs

The version on my device before it was bricked is 5.1.1. I'm staying on that version since its the easiest to root.

Related

[Q] trouble installing adb USB drivers on windows

I am attempting to root my HTC Panache (MyTouch 4G) with this guide.
The problem is with the first step which is installing adb and the USB driver. The guide referred to the cyanogenmod wiki on installing the android SDK. I believe that I followed all the instructions correctly but it does not show that my drivers are installed properly in windows device manager and CMD.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So here is the entire process that I took:
installed java sdk exe
downloaded Android SDK zip file and extracted to root C:\
opened SDK Manager
installed "Android SDK Platform-tools, revision 6" (revision 4 not available) and "Google USB Driver package, revision 4" packages in SDK manager
went into control panel > system > advanced settings > environment variables > double clicked "Path" > added ";C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools"
downloaded and replaced the default "android_winusb.inf" file with the modified file from the cyanogenmod wiki
enabled "USB debugging" and ensured USB was in "charge only" mode in phone
opened CMD and typed in "adb devices", didn't show anything
opened windows device manager and found an "Android Phone" device with the yellow exclamation mark instead of "Unknown Device" with ADB listed under it as mentioned in the cyanogenmod wiki
right clicked and update driver software, clicked browse and located the "C:\android-sdk-windows\extras\google\usb_driver" folder with the modified .inf file
"Windows was unable to install your Android Phone"
I've been trying many things for hours so any help would be appreciated! Thanks in advance.
Try these drivers...
http://www.multiupload.com/HBVGRC92IP
Ace42 said:
Try these drivers...
Click to expand...
Click to collapse
Success!
All I needed to do was install the .exe you gave me, restart the computer, device manager > right-click the unknown android phone device and "scan for changes", then the driver automatically installed! confirmed with cmd > adb devices.
Thank you!
qayum said:
Success!
All I needed to do was install the .exe you gave me, restart the computer, device manager > right-click the unknown android phone device and "scan for changes", then the driver automatically installed! confirmed with cmd > adb devices.
Thank you!
Click to expand...
Click to collapse
Np, the generic drivers normally don't install anyway, have to use the htc ones instead.
Ace42 said:
Np, the generic drivers normally don't install anyway, have to use the htc ones instead.
Click to expand...
Click to collapse
Off-topic but, another problem.
I've successfully generated the CID with SimpleGoldCard but it seems that the gold card IMG generator website psas.revskills.de/?q=goldcard is down.
Will it be online again? Is there any other way to get the IMG file?
qayum said:
Off-topic but, another problem.
I've successfully generated the CID with SimpleGoldCard but it seems that the gold card IMG generator website psas.revskills.de/?q=goldcard is down.
Will it be online again? Is there any other way to get the IMG file?
Click to expand...
Click to collapse
I have no clue what the gold card is really, I last heard about it when people were rooting the magic. Since you mentioned CID, are you trying to unlock the phone fir other carriers ?
Ace42 said:
I have no clue what the gold card is really, I last heard about it when people were rooting the magic. Since you mentioned CID, are you trying to unlock the phone fir other carriers ?
Click to expand...
Click to collapse
No, I do not need to unlock it. The phone is from my carrier Mobilicity, but people referred me to use the Videotron HTC Panache guide (link to thread in OP) because it has a newer ROM version and making a gold card allows to "flash RUU files with a different CID to your own device - in other words, it allows you to flash files that were not made for your phone."
Basically, there was a back-to-school sale on the HTC Panache from Mobilicity and people who wanted to root (and unlock) it followed the guide above.
Please give me any suggestions, thanks!
Odin is not recognize by my phone since CM 10.1 been installen on my phone
Good day!
Since Cyanogenmod 10.1 nightly been installed on my phone, Odin does not see the phone anymore even is the USB debugging is active on the phone. I am able to see the phone using the command ADB devices -l. I need Odin back because I want to put back the stock firmware on my phone which is Jelly Bean 4.1.2. from Virgin Mobile.
Can someone tell me why ADB can see my phone and not Odin?
Thank you!

Installing TWRP. Stuck at "waiting for device"

I'm getting this issue with Kindle Fire Utility when trying to install TWRP;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have rebooted my kindle fire while waiting for it, but I haven't been able to find other solutions, please help! I'm fairly sure that I have ADB working... I'm really not sure what to do
georgeos said:
I'm getting this issue with Kindle Fire Utility when trying to install TWRP;
I have rebooted my kindle fire while waiting for it, but I haven't been able to find other solutions, please help! I'm fairly sure that I have ADB working... I'm really not sure what to do
Click to expand...
Click to collapse
If you would have followed my tutorial you wouldnt have this problem here is the fix:
• I have noticed that some people have problems getting stuck around 2:32 into the video where twrp is downloading and getting ready to install. If this happens to you and it is constantly “waiting for device” You may need to hit disconnect on your KF and run burrito root on your Kindle again, click “agree”,then click “You Rock”, Then click “root”. Once you do so you must re-open adb shell by opening a command prompt and typing the following:
cd c:\KindleADB this is to get into adb shell
adb devices this is to make sure your kindle is connected properly
adb root this is to get proper permissions
Just to be very clear on what you should type in your cmd prompt:
cd c:\KindleADB
adb devices
adb root
• Once you have done this re-open the run bat in KFU v0.9.1 and select option 5 again and it will install the twrp with proper root permissions.
here is a link to my tutorial for you to check if you have more problems afterwards:
http://forum.xda-developers.com/showthread.php?t=1417234
[-_-] said:
If you would have followed my tutorial you wouldnt have this problem here is the fix:
• I have noticed that some people have problems getting stuck around 2:32 into the video where twrp is downloading and getting ready to install. If this happens to you and it is constantly “waiting for device” You may need to hit disconnect on your KF and run burrito root on your Kindle again, click “agree”,then click “You Rock”, Then click “root”. Once you do so you must re-open adb shell by opening a command prompt and typing the following:
cd c:\KindleADB this is to get into adb shell
adb devices this is to make sure your kindle is connected properly
adb root this is to get proper permissions
Just to be very clear on what you should type in your cmd prompt:
cd c:\KindleADB
adb devices
adb root
• Once you have done this re-open the run bat in KFU v0.9.1 and select option 5 again and it will install the twrp with proper root permissions.
here is a link to my tutorial for you to check if you have more problems afterwards:
http://forum.xda-developers.com/showthread.php?t=1417234
Click to expand...
Click to collapse
I tried what you said, and have made some progress, the Kindle Fire is rebooting when it comes to say "waiting for device" but then gets stuck at boot, so I have to put it back to normal boot rather than fast boot
georgeos said:
I tried what you said, and have made some progress, the Kindle Fire is rebooting when it comes to say "waiting for device" but then gets stuck at boot, so I have to put it back to normal boot rather than fast boot
Click to expand...
Click to collapse
Once again all of the answers to your problems and the questions you have are in this tutorial. From what it looks like to me from your screen shot you do not have "root Permissions" if this is in fact the problem then what you are probably trying to do is to start at step five from the Kindle Fire Utility and download to install twrp2.0 If this is what you are trying to do then you must see on the command prompt of KFU that you are downloading and then waiting on device. If this is still your situation then the fix is what I stated above and in my link. If you have gotten passed that problem and still have issues with you either being stuck at the yellow triangle( firefirefire ) or a Kindle Fire boot screen that will not go away then the fix is also in my link... If you do not wish to follow the link and see the videos or read through the trouble shooting guide then I am afraid I have no way of helping you...
If I helped please do not forget to hit the thanks button and post back in my guide thread that it worked okay for you as well so that new members can see that this is one of the easiest guides to follow here is a link to take you to that guide a little quicker good luck....
http://forum.xda-developers.com/show....php?t=1417234
If you need further help reply in that thread and I will be more than happy to help you there so others can find the fix to the problem that you come across a little easier
I got stuck in several places when I did it, the issues I had where an old version of adb, and drivers, had to uninstall and reinstall the drivers
Sent from my Kindle Fire using xda premium

I screwed up.

I decided to change my dpi on my tablet to see if I could install an app that I needed from the market. Well I screwed up. I bumped it to 240 dpi and now I can't unlock my tablet when I cut the screen on because the unlock button that you slide to is off the screen. I can cut the camera on, but I have no home or back button because they are off the screen as well. I can't do anything. I need some help here. I have the build.prop file, but when I try to push it, it doesn't find my device. I have usb debugging on. Please help me before my wife kills me lol.
Wipe your tablet ,thing its fastest way.but you loose your apps and other stuff.
Wysyłane z mojego ASUS Transformer Pad TF300T za pomocą Tapatalk 2
I didn't think wiping would restore the build.prop file.
If the restore doesn't work, then you may have to flash the stock firmware to your tablet. Have you tried accessing it with adb?
I reset and it is still the same. Everytime I try to access through adb, it doesn't find my device. All the drivers are installed. If I could get adb to recognize my device, then I could push the build.prop file and everything would be fine. I'm really stuck here.
Best solution would be getting adb working correctly and pushing the stock build.prop
Do you have any idea why the adb might not be recognizing my device? I wouldn't need to have the bootloader unlocked for adb would I?
I ensure I have right drivers in a folder and not to always use installers, attach device then (on windows) use system/hardware manager and remove the device it is showing as, close device manager, detach device, re-attach the device when asked to install drivers select manually this will then install ALL the drivers required (I found genuine installer didn't install correctly or was fixed so not for users use only programs use) it should pick up your device on at least i'd guess x2 USB ports.
No bootloader etc needs adb to work to unlock it via USB
Rooted Xakep E320/C6 EUU Hacked Update
Try forcefully restarting the tablet. Hold the top power switch and the volume-down until it shuts off. Restarting often helps me with any problems I'm having. It may help your computer recognize the tablet if you keep it attached. And maybe restart your computer, windows is notorious for stuff like that.
Thanks all for the replies. Here's what's going on. I've reinstalled the drivers and the computer recognizes the device now. You can see from the attached image. Am I doing something wrong in my push command that is keeping the pc from pushing the file?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How about trying https://play.google.com/store/apps/details?id=lv.n3o.lcddensity&feature=search_result or any other similar app from the Play Store?
superuser has quit responding anytime that I try to run one of these apps. I can't allow permission so the app won't work. This really sucks. I wish I could just figure out why I can't push the file through adb.
UPDATE:
I fooled around and managed to navigate to the play store without unlocking the screen. Upon doing this, I got into superuser and then allowed the lcd changer app to run. Then I ran the app and it rebooted my tablet and it's back to normal. Thanks for all the tips guys. I am no longer in the dog house.
jbrowning37 said:
UPDATE:
I fooled around and managed to navigate to the play store without unlocking the screen.
Click to expand...
Click to collapse
Just out of curiosity: How did you manage to do that? Is it possible to control the device like that from ADB?
No, even with the screen locked I could pull down the notification bar. When it said "installing adobe flash player" I clicked it and the market opened. I would have been screwed had I not been able to do that.
You shouldn't run the "adb shell" command and then "adb push ....", you should push the file without you go into shell.
Not sure if that was really causing your issue or not, but it could be.

[Q] Windows 7 Driver Problems

Hi guys,
I have literally tried everything I could find here. I have tried the Universal drivers, the PDAnet drivers, and the Google drivers, and I have used an installer as well as manually installed the drivers. For the universal and Google drivers, I can get the phone to be recognized by Windows 7 as a Nexus 4, and Windows says the drivers are configured properly. However, the phone doesn't mount and ADB/fastboot still don't connect (and yes, the phone is in USB debugging mode).
After every failed driver I uninstalled the device, removed the Google drivers from USBdeview, and reinstalled the next set of drivers, to no avail. The computer has been restarted many times, no luck. I have tried all three USB ports on my laptop, and I have tried multiple cords, one of which I know for sure works.
Any suggestions would be appreciated. Thank you.
EDIT: If you want, I can add a screenshot of my USBDeview entries to see if there are any conflicting drivers/interfaces. My old phone was a Samsung Galaxy S, but I removed as many of those drivers as I could find.
Silly question, but when attempting fastboot, you did reboot into the bootloader? If you use twrp, they have an adb push setting in the advanced tab(?), see if that's recognized at all?
Sent from my Nexus 4 using Tapatalk 4 Beta
I couldn't use adb or fastboot at all. No adb when the phone is on, no fastboot in the boot loader. I don't have a custom recovery because I can't flash one without fastboot.
Sent from my Nexus 4 using xda app-developers app
I'm also on 64-bit Windows 7, I forgot to mention that. Just tried the Universal Naked Drivers, to no avail.
Did you update adb to the latest version (v1.0.31)? If not, adb won't see the phone
EddyOS said:
Did you update adb to the latest version (v1.0.31)? If not, adb won't see the phone
Click to expand...
Click to collapse
Thanks for the reply. I've been trying to use Minimal ADB and Fastboot so far, since I really don't want to download the SDK. However, I've also tried to use the newest versions of Wug's Nexus Root Toolkit and mskip's toolkit, both of which do not work.
My Windows 7 Pro x64 work PC can see it as can my personal Windows 8 Pro x64 laptop at home - both using the stock Google drivers from the SDK
Remember, also, that when you run 'adb devices' the phone will ask you to allow the PC to connect. If you don't click OK on the phone it will say it's offline
EddyOS said:
My Windows 7 Pro x64 work PC can see it as can my personal Windows 8 Pro x64 laptop at home - both using the stock Google drivers from the SDK
Remember, also, that when you run 'adb devices' the phone will ask you to allow the PC to connect. If you don't click OK on the phone it will say it's offline
Click to expand...
Click to collapse
The window never pops up on the phone. ADB list of devices comes up blank. I'll try the SDK later.
Using the SDK and the newest ADB did not help, still the same problem. I'm out of ideas.
EDIT: Attached are two screenshots of the USBDeview program after I've uninstalled all the Google and Android drivers. Is there anything there that looks like it needs to be uninstalled?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Need Help Manual Fastboot Driver Installation

Hello
Sorry if this was a very noob topic
I done lots of flashing new ROM or back in stock process but i almost gave up this time
My phone status are
No OS
TWRP installed
Can boot to recovery
PC can't recognize the phone
Typing ADB devices shows empty list
Typing Fastboot devices also shows empty lines
30% battery left
I recently try to install the Lollipop version for my phone but it turns out that the zip are behaving like OTA (yep the title of the zips are OTA)
What i mean is it returned my recovery to stock
Without thinking much further i did 'fastboot flash recovery TWRP2810.img' thing (Yes i rename recovery image that way so it will be more convenience for me) and wipe all partition in the phone through the TWRP without problems
One thing i forgot is to "refresh" all ADB and Fastboot driver for my phone on the PC
Now my phone states are "No OS" and "PC doesn't recognize my phone" wether in ADB (obvious cause i can't boot with no OS so no USB debugging for me) and Fastboot (Enter Bootloader is OK, enter TWRP is OK too)
I already try the WUG step for installing the needed driver but no success since my PC can't recognize my phone
Try on 4 PC at my office and all of them are ignoring my phone
What should i do now, please, any help will be appreciated since its already the time i ussualy already at home
Thank You Very VERY MUCH for any help I can get.
unsungkhan said:
Okay, here's what you do.
Download the ADB drivers first, from here [URL="link"]http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
unsungkhan said:
Extract the zip.
Once you're done extracting, boot your phone into bootloader mode, plug in USB, should show up as an unrecognized device.
Device manager from control panel, select device, properties, driver, update device driver, browse my computer, let me pick, all devices, have disk, navigate to where you extracted zip, select inf file, adb interface.
Should work.
Click to expand...
Click to collapse
[/URL]
Thank you Sir
I managed to fresh install my XP and continue with your instructions
I don't know why but it gave me this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I already try other driver but still a no go?
Do you happen to know other way around for tricking this Sir?
Please lock this unuseful thread
Before locking the thread, can you repeat all the steps and try with ADB Composite Device instead of ADB Interface?
Also, did you try changing USB ports, sometimes these things get a little troublesome because of faulty USB ports.
Last but not the least, you could also try a change of cables.
unsungkhan said:
Before locking the thread, can you repeat all the steps and try with ADB Composite Device instead of ADB Interface?
Also, did you try changing USB ports, sometimes these things get a little troublesome because of faulty USB ports.
Last but not the least, you could also try a change of cables.
Click to expand...
Click to collapse
#late_post
i've been able to resurrect my phone finally
after those steps i found Universal Naked Driver and it works
Thank You very MUCH Sir :laugh:

Categories

Resources