Fire crashes when Mounting USB [Stock Rom Rooted] - Kindle Fire General

I installed OTA root keeper and since then when I mount the USB it freeze up and crashes. It resets on it own some times and sometimes I have to reset by holding down the power button. I uninstalled OTA and its still happening. It may just be a coincidence due to bad timing,

Root keeper screwed with the usb settings probably. Since it messed with mounting, you might have to restore via kindle fire utility if your computer can detect it

Couple Questions.
Will restore wipe my data?
Is this normal for root keeper? is it safe to try again once I restore?

Yes this will wipe ALL data. I have never heard about root keeper screwing with mounting. It only screws with ota updating. I don't think you should try again though.

OK all figured out. It was an error with my pc and the kindle ws just bad timing. I totally forgot my ipod wasnt being recognized earlier today. I finally put two and two together.

Related

[Q] Upgraded without Unrooting

I may have missed this in another thread, so please feel free to redirect me if so...
Without thinking, I updated my Droid with the OTA push and my previously rooted Droid 2 is now not rooted.
I did try to run the oneclick and 1-2-3 root processes. Both end with "your device is now rooted", but of course it's really not. I do have the Superuser APK, but my rooted programs are not communicating with it. And I'm not able to uninstall the Superuser program (thought I'd try to reinstall it). No go.
I had Titanium Backup, ad am wondering if I can wipe my phone and restore it, then upgrade, and root after. I'm a newbie with limited knowledge, so wondering if I've backed myself into a corner on this one.
All feedback appreciated!
Yesterday, I did the same thing you tried and I was successful in rerooting my phone after the OTA update. When you used the 1-click process did you choose option 1 or 2. I tried 2 and it didn't work. I had to chose option 1 (reload everything) to be successful. BTW, remember to make a new recovery backup of the system.
unrooted
xberry said:
I may have missed this in another thread, so please feel free to redirect me if so...
Without thinking, I updated my Droid with the OTA push and my previously rooted Droid 2 is now not rooted.
I did try to run the oneclick and 1-2-3 root processes. Both end with "your device is now rooted", but of course it's really not. I do have the Superuser APK, but my rooted programs are not communicating with it. And I'm not able to uninstall the Superuser program (thought I'd try to reinstall it). No go.
I had Titanium Backup, ad am wondering if I can wipe my phone and restore it, then upgrade, and root after. I'm a newbie with limited knowledge, so wondering if I've backed myself into a corner on this one.
All feedback appreciated!
Click to expand...
Click to collapse
Same issue here - how I fixed
I had already made titanium backups of important stuff - you have to go into applications (that use root) and force stop and clear data. Once this is complete open titanium backup for instance, and you should be asked for super user and then be good to go. Same goes for rest of apps that need root
OTA update Loop?
i have my d2 rooted after the ota 2.2 update. i just received a notification to accept the most recent OTA update ... whatever it is... and assumed it was one of my apps as i didnt read it thru completely b4 tapping 'ok'. now it is stuck in a download, reboot, update, "update unsuccessfully installed", redownload, reboot...........
is there a way to cancel the update? i dont really care if i have it or not
or some way to stop this process aside from the airplane mode i had to set it to so it would stop this madness
So you can do the OTA update without having to unroot and reroot?
Great advice from all - thanks! I'm not sure exactly what fixed it, but I ran DOROOT several times, did the unplug/plug when it hung for a minute, force closed/cleared data from previously rooted items, and also put phone into 'charge only' mode when USB Debugger would not run.
Finally - success! My advice to users with this same issue - try and try again.
Thanks all!

[Q] Can't get root to restore

I have Voodoo OTA Rootkeeper installed & had done a temp unroot, so I could access Amazon prime content, but now I can't get it to restore the root. Any ideas what I'm doing wrong? And it does say "root su restored" after I push the "restore root" button, but even after 2 device restarts, I'm still unrooted. NEED to get on the regular market!
Could it be because it update the os to 6.2? I don't recall what it was before & it never ASKED me to update it, but idk
LoriH7 said:
Could it be because it updated the OS to 6.2? I don't recall what it was before & it never ASKED me to update it, but I don't know.
Click to expand...
Click to collapse
I doubt it, it's working fine for me and many others on 6.2.
If you used it to unroot before 6.2, then when 6.2 silently upgraded, it would have undone the rooting and killed your OTA rooting.
6.2 didn't ask anyone. if you had wifi connected, it would download without messages. and at some point it would have rebooted, like for me. Or others said once they turned it off it went ahead and did it.
super one click will reroot it in less than a minute and you should be good until next time they do this.
Thelgow said:
If you used it to unroot before 6.2, then when 6.2 silently upgraded, it would have undone the rooting and killed your OTA rooting.
6.2 didn't ask anyone. if you had wifi connected, it would download without messages. and at some point it would have rebooted, like for me. Or others said once they turned it off it went ahead and did it.
super one click will reroot it in less than a minute and you should be good until next time they do this.
Click to expand...
Click to collapse
Thanks! I'd bet that's what happened. It's almost always connected to wifi & I've had it rooted for a couple of weeks. Thanks. Back to super one click....
Ok, so I rerooted, but all of my google services are broken still. Reinstalled the apks, but it refuses to install the googleframework.apk. It's on there, asks me about permissions & then says it won't install. I'm clearly missing a step or something.
wierd issue
When I try to reroot my KF after the 6.2 update it roots the device then attempts to reboot into root... and that is when it fails... it just sits on the kindle fire screen flashing like it is rebooting I let it sit for a few minutes and never fineness, however if I hold down the power it will shutdown and I can start it back up but only half way rooted ... and never finished installing superuser or busybody... any ideas?
Not sure about those issues. Different people reported different problems.
Seems not everyone used the same methods. for me googleframework and market worked perfectly fine afterwards, i didnt need to do anything else.
Once my KF updated to 6.2, I could not restore root through OTA Rootkeeper either. Connected it to my computer, ran SuperOneClick, root was restored and backed up my root once again. I think I needed to reset once to ensure that all of my sideloaded apks still worked.
Well I got it figured out I just did a factory reset and reapplied root and now it is working thanks guys
Sent from my Kindle Fire using xda premium

[Q] Can't install latest OTA update after unroot

Hey guys,
So I've googled around for this issue but I still have a question that no other thread I've found seems to answer.
A few weeks ago I rooted my Razr M. I froze a couple of the verizon apps (like the google chrome bookmarks) and backed up and deleted the amazon apps, IMDB, and Audible apps with titanium. When the new OTA was released this week I restored and thawed all of those apps, but the OTA wouldn't install. It reached about 1/4 through the bar of Andy and then he would be on his side with the caution sign. The phone would reboot and say that the installation failed. I decided to unroot, thinking that may have been the cause, but I still got the same error. From there I did a factory reset, and I'm still getting the same error.
Here's my question: I saw on a couple threads that a factory reset doesn't restore everything in /system, which is where I'm worried there's a discrepancy that isn't allowing the update. Is there a way to do a harder reset that will completely bring the phone back to stock?
I'm currently on System version 98.12.4.XT907.Verizon.en.US if that helps. Android 4.1.1. Baseband version is SM_BP_1139.000.32.62P.
JadedRescue said:
Hey guys,
So I've googled around for this issue but I still have a question that no other thread I've found seems to answer.
A few weeks ago I rooted my Razr M. I froze a couple of the verizon apps (like the google chrome bookmarks) and backed up and deleted the amazon apps, IMDB, and Audible apps with titanium. When the new OTA was released this week I restored and thawed all of those apps, but the OTA wouldn't install. It reached about 1/4 through the bar of Andy and then he would be on his side with the caution sign. The phone would reboot and say that the installation failed. I decided to unroot, thinking that may have been the cause, but I still got the same error. From there I did a factory reset, and I'm still getting the same error.
Here's my question: I saw on a couple threads that a factory reset doesn't restore everything in /system, which is where I'm worried there's a discrepancy that isn't allowing the update. Is there a way to do a harder reset that will completely bring the phone back to stock?
I'm currently on System version 98.12.4.XT907.Verizon.en.US if that helps. Android 4.1.1. Baseband version is SM_BP_1139.000.32.62P.
Click to expand...
Click to collapse
Sounds like you did not defrost those system apps using titanium backup before you factory reset. I would restore from your stock backup and unfreeze those apps with titanium and try the ota again. The OTA checks for certain bloatware apps before it will allow it to install the update.
slogar25 said:
Sounds like you did not defrost those system apps using titanium backup before you factory reset. I would restore from your stock backup and unfreeze those apps with titanium and try the ota again. The OTA checks for certain bloatware apps before it will allow it to install the update.
Click to expand...
Click to collapse
I definitely did defrost those apps.
I'm having the same issue. Stops at about 1/4 of the way and then restarts. I'm gonna try it again without my Rogers(non-verizon) sim card and see if it works. Maybe it checks which sim card is being used.
EDIT: Didn't work, sim card irrelevant.
If you really want the ota then why don't you try mattlgroff's utility here:
http://forum.xda-developers.com/showthread.php?p=39576818
It will return you back to completely stock with one click and then you should be able to take the ota and reroot unlock if desired
Sent from my XT907 using Xparent BlueTapatalk 2
RSD
vLegend said:
I'm having the same issue. Stops at about 1/4 of the way and then restarts. I'm gonna try it again without my Rogers(non-verizon) sim card and see if it works. Maybe it checks which sim card is being used.
EDIT: Didn't work, sim card irrelevant.
Click to expand...
Click to collapse
I tried using Mattlgroff's method (which i'm sure is fine for most) but seems to be geared towards linux users mostly, and I ran into some issues. I have always used RSD to get back to stock and never had an issue. Check it out How To Restore Stock Firmware on Razr M. This will hard restore your phone to the factory image, as well as unroot it, no need to unfreeze or reinstall bloat. It will also obviously erase the internal SD card contents so make sure you back those up.
Yeah looks like slogar25 and cliMAKtic are right. I tried a few more things and its not working. I'll do an rsd in the next couple days and try the ota again.
I'm going to try rsd sometime tonight, I'll let everyone know how it goes. Thanks for all the help!!
I like rsd too. The point is to return too stock.
Sent from my XT907 using Xparent BlueTapatalk 2
Same issue, stops 1/4 of the way through.
Flashing back to stock with the RAZR M utility 1.10 once my phone hits 100% battery (at 93% now). Will let you know if I can take the update after.
Keep in mind
RSD is great to get back to clean stock, but keep in mind that it will remove your root. After taking the OTA update, you will be running firmware v4.1.2. If you used MotoFail2Go exploit to root your phone originally you should note that the exploit apparently does not work for the updated firmware. Instead you should use motochopper, an updated exploit that works on 4.1.2 to root your phone, developed by Drjbliss over at Droidrzr.
I honestly don't care too much about being unrooted at this point anyway, having root wasn't doing too much for me. I managed to get back to the original stock ICS using RSD and everything worked out! Downloaded one update to 4.1.1, then the second update to 4.1.2, and everything went swimmingly.
Thank you so much for all your help everyone!

[Q] Encrypting a Galaxy Note 3

I have a new Galaxy Note 3 (having bricked one trying to understand why it wouldn't encrypt) and now with a full stock rom I still find that the phone is impossible to encrypt.
I have an encrypted SD card in it. (only thing I can think of that might be causing problems)..
Settings > General > Security > Encrypt Device keeps stopping after a single shutdown,
How the heck do I encrypt this thing?? - Am I missing the blindingly obvious..
Thanks
tahnoonp said:
I have a new Galaxy Note 3 (having bricked one trying to understand why it wouldn't encrypt) and now with a full stock rom I still find that the phone is impossible to encrypt.
I have an encrypted SD card in it. (only thing I can think of that might be causing problems)..
Settings > General > Security > Encrypt Device keeps stopping after a single shutdown,
How the heck do I encrypt this thing?? - Am I missing the blindingly obvious..
Thanks
Click to expand...
Click to collapse
I'm having the exact same issue. Encryption is requited to get my work email and I can't get it to go.
Finally got mine to encrypt
Took me a bunch of tries.. and finally once i opened a chat with samsung support it finally worked.. i was at 100% charge, plugged into the wall and if finally worked. not sure if thats a bug in its detection if your over the stated 80% or not... good luck.. i finally got it working though.. only did a fast encryption as it didn't work on previous tries either way... so i just chose one and tried it again.
tahnoonp said:
I have a new Galaxy Note 3 (having bricked one trying to understand why it wouldn't encrypt) and now with a full stock rom I still find that the phone is impossible to encrypt.
I have an encrypted SD card in it. (only thing I can think of that might be causing problems)..
Settings > General > Security > Encrypt Device keeps stopping after a single shutdown,
How the heck do I encrypt this thing?? - Am I missing the blindingly obvious..
Thanks
Click to expand...
Click to collapse
I have the Google Policy Manager and Encryption is required for me too. I started at 81% and the first time I did it, it just rebooted. The second time I did it it worked like it was suppose to. Try it again right after it reboots and see if it works.
Make sure the phone is charged and keep trying over and over.
It will work eventually.
I gave up. I'm using touchdown now for work email which will allow me to skip full device encryption
Sent from my SM-N900V using Tapatalk
Same problem here, it will not encrypt
....help please
This is the answer I found doing a couple of root and unroot
1.If you encrypt the device and then root it you will net get past the passcode in the phone (black screen)
2. If you root the phone first and ten try to encrypt you will get the problems mentioned in this thread
..any tips how to get the phone rooted and then encrypted?
greffel said:
This is the answer I found doing a couple of root and unroot
1.If you encrypt the device and then root it you will net get past the passcode in the phone (black screen)
2. If you root the phone first and ten try to encrypt you will get the problems mentioned in this thread
..any tips how to get the phone rooted and then encrypted?
Click to expand...
Click to collapse
Bump. I'm looking for this answer too.
digittante said:
Bump. I'm looking for this answer too.
Click to expand...
Click to collapse
anyone at all? im stuck. Bump!
was having a similar problem on nexus 4 but safe mode helped there.
dind't help on my new n3. shouldn't have rooted before encrypting.
tried pressing encrypt about 10 times.
tried boot into recovery + wipe . also tried safe mode. also tried unroot + factory reset (pretty sure recovery + wipe /data is the same as reset user data from settings).
waiting for the firmware image to download - decided to try a firmware reflash
and then before flashing it I tried rebooting to recovery and powering off and encrypting and it worked. or maybe it was that random 12th time it worked because of an unrelated reason.
and after trying to root it again it just booted to a black screen after cf-root and enter encryption password screen.
*sigh*
My Work-Around
svyr said:
and then before flashing it I tried rebooting to recovery and powering off and encrypting and it worked. or maybe it was that random 12th time it worked because of an unrelated reason.
and after trying to root it again it just booted to a black screen after cf-root and enter encryption password screen.
*sigh*
Click to expand...
Click to collapse
I'm an AT&T customer, but I bought a T Mobile Note 3 off of Craigslist, unlocked it, rooted using Chainfire's ODIN thread, and then used the RegionFree Lock Away app. I was unable to encrypt just like you guys until I did the following. Flashed TWRP tar file from the TWRP site using ODIN. Rebooted into recovery and made an image, backup up everything, just in case. Rebooted and went in the SU Superuser application that Chainfire originally installed and uninstalled through the settings in the program. Once I rebooted I was able to encrypt the device (without fast method), I already had my SD Card encrypted. Once I encrypted the device I downloaded Kingo Root at the advice of DesignGears and used the one click root application from the Kingo Root site (google it.) After I did that, I now have full root access back, encryption, and never had to uninstall the region lock, so I didn't lose phone connectivity, applications, or anything else during the process. I recommend using TitaniumBackup and syncing via Google Drive or Dropbox before you start the process so you can restore your apps and data, once again, just in case.
encrypted ATT Note 3 not able to root
I was able to unroot my ATT Note 3 and then encrypted it. But Kingo Root failed to root the device. (I used it to root the phone once previously)
Now I stuck in a status with encrypted phone not able to root anymore.
Any suggestions please?
GHolbrook4 said:
I'm an AT&T customer, but I bought a T Mobile Note 3 off of Craigslist, unlocked it, rooted using Chainfire's ODIN thread, and then used the RegionFree Lock Away app. I was unable to encrypt just like you guys until I did the following. Flashed TWRP tar file from the TWRP site using ODIN. Rebooted into recovery and made an image, backup up everything, just in case. Rebooted and went in the SU Superuser application that Chainfire originally installed and uninstalled through the settings in the program. Once I rebooted I was able to encrypt the device (without fast method), I already had my SD Card encrypted. Once I encrypted the device I downloaded Kingo Root at the advice of DesignGears and used the one click root application from the Kingo Root site (google it.) After I did that, I now have full root access back, encryption, and never had to uninstall the region lock, so I didn't lose phone connectivity, applications, or anything else during the process. I recommend using TitaniumBackup and syncing via Google Drive or Dropbox before you start the process so you can restore your apps and data, once again, just in case.
Click to expand...
Click to collapse
I was able to get mine to encrypt after killing the bloat apps. All Google sync, amazon, and Verizon services. I can't say which one was killing it since it stopped pretty much every app or service that wasn't critical to the device.
Can anyone confirm that Encryption will never work once we root our phone ?
nlatifolia said:
Can anyone confirm that Encryption will never work once we root our phone ?
Click to expand...
Click to collapse
Same question here... Anyone was able to encrypt after being rooted???
Same question, rooted can't encrypt.
Just got a note 3 and this is an old thread. So wanted to update this question.
To encrypt device after root all that is needed to do is run the following command from terminal or adb shell as root. You must have the latest busybox installed.
pkill -KILL daemonsu
After running this command you should be back at the "$" prompt and out of root. Do not run su again.
Then encrypt your device. Encryption should work fine. Once rebooted you will have root again.
I had to repeat the above steps because I ran su again. Running su restarts daemonsu.
Good luck
Hi,
I was able to root and encrypt my sm-n900 note3 using the steps mentioned on this post:
http://forum.xda-developers.com/showthread.php?t=2791587
Just make sure that you have your backups ready case something goes wrong
I've installed the bloatwares after rooting and encrypt.

Rooting my Metro PCS S3 (SGH-T999N)

Is there any way too root this phone?
Sent from my SGH-T999N using xda app-developers app
More info
Sent from my SGH-T999N using xda app-developers app
Root SGH-T999N (metro PCS) to SGHT999NUVUBMK7 after 4.3 update
RawesomeMike said:
More info
Sent from my SGH-T999N using xda app-developers app
Click to expand...
Click to collapse
Yes, there seems to be a root method for the SGH-T999N that I may have discovered. I synced/backed up on Google sync, when I was running on 4.1.2.
I Unintentionally updated to 4.3 not realizing root would be more difficult. I DID NOT use odin, just cause of the bricking hype. I did do some stuff with sideload, I think.
When flashing I used a 16gig micro SD card & also copied some extracted zip rom files via windows, straight to the phone.
Kept getting the error (in red) when checking for signature or something.(Ex. e: whole-file signature failed <se3>).
In the phone OS, I manually cleared cache, data, notifications, turned off & forced stop on several of the "update" & other potentially restricting security apps on the phone.
Booted into recovery via power + home + volume ? keys.
Wiped cache
Wiped all data
"Upgraded ish" from external SD card.
Reset my phone & still got a signature fail.
Did the wipe & factory default again (after another reboot)
Flashed the same file again (I think) was CWM, Cyanogen or something. d2tmo, d2mtr seem to work.
Did a Factory reset & phone went to metro logo. Did a 2nd recovery reset before 1st one could finish & the phone seemed to go to an out-of-box state/first time setup. That's where I was able to enable superuser root, the box thing & backup?
Sorry I don't remember more detail at the moment. The Google Chrome backup seemed to help a lot for reinstalling rooted apps after 4.3 update w/ factory reset.
polkcontracting said:
Yes, there seems to be a root method for the SGH-T999N that I may have discovered. I synced/backed up on Google sync, when I was running on 4.1.2.
I Unintentionally updated to 4.3 not realizing root would be more difficult. I DID NOT use odin, just cause of the bricking hype. I did do some stuff with sideload, I think.
When flashing I used a 16gig micro SD card & also copied some extracted zip rom files via windows, straight to the phone.
Kept getting the error (in red) when checking for signature or something.(Ex. e: whole-file signature failed <se3>).
In the phone OS, I manually cleared cache, data, notifications, turned off & forced stop on several of the "update" & other potentially restricting security apps on the phone.
Booted into recovery via power + home + volume ? keys.
Wiped cache
Wiped all data
"Upgraded ish" from external SD card.
Reset my phone & still got a signature fail.
Did the wipe & factory default again (after another reboot)
Flashed the same file again (I think) was CWM, Cyanogen or something. d2tmo, d2mtr seem to work.
Did a Factory reset & phone went to metro logo. Did a 2nd recovery reset before 1st one could finish & the phone seemed to go to an out-of-box state/first time setup. That's where I was able to enable superuser root, the box thing & backup?
Sorry I don't remember more detail at the moment. The Google Chrome backup seemed to help a lot for reinstalling rooted apps after 4.3 update w/ factory reset.
Click to expand...
Click to collapse
You say you think.....doesn't sound reassuring can you elaborate a bit more? I don't seem to understand what you are getting at if it works or not? I don't know if I should root my phone now or wait for 4.4.......
Have you heard of/tried the Morobo + Shuame method? Worked a treat for my HTC Wildfire, Motorola Defy, and my HP Slate 7.
Seriously worth a shot if you ask me. A link to the XDA thread:
http://forum.xda-developers.com/showthread.php?t=2092349
Know this is old, but if you're still looking for a method, I successfully rooted my T999N yesterday using ChainFire's autoroot for the t-mobile variant (the T999). I'm new so I can't post a link here, but if you google "chainfire autoroot", it'll direct you to his page where you can download the package from the list of supported devices. The package conveniently contains a version of Odin3 that you will use to flash his stuff to your phone.
Remember, the phone must be in samsung's "download mode" to receive the flash. You get this model into the mode by powering it off, then holding the HOME button, the POWER button, and the VOLUME DOWN button all at once. When the warning message comes up, you push VOLUME UP to continue, then the phone will be in download mode. You can then connect the phone to your computer and if you have the drivers installed correctly, Odin will recognize the phone and be able to send the flash. You will then need to go about disabling Samsung's security software, KNOX, before the phone will be fully rooted. There are plenty of guides on how to do that so no worries there.

Categories

Resources