Related
I believe I habe the kfsowi model. it is 11.3.1.0 it is rooted and I am wanting to factory reset it but I dont have a factory cable. just a normal usb cable that I've been using adb to transfer and even instlal some files because through tweaking it, it lead to a missing status bar in which i change the qmenu = to 0 and 1 or whatever in build.prop but no matter what it doesnt keep the status bar active at all times like it should be. it is non existent until i click on an app in apex, adw or any launcher ive tried then it flashes and disappears. during this flash it is not usable no matter how fast i click it.
also a small issue it has is ever reboot, it says kindle is upgrading but it is not upgrading at all because i have tried to click check now in settings to check for updates but every time it says update failed. next after that message it says starting applications for about 20 seconds. long bootup. i have probably messed with tweak i shouldnt have with pimp my rom and also android tweaker 2 and pro before it became 2. so the status bar is non existent. sucks cause cant even get facebook notifications lol.
i did factory reset it by the menu and also by using andromizer app to click recovery mode and do it that way.
(without status bar i been using all in one gestures but now recently i switched to using LMT.
this kindle has a few issues since i made it kinda as minimal as i could and probably uninstalled a couple things i shouldnt of lol like it only installs apps with adb install and adb install -r sometimes as well as through 1mobile market which is awesome. it will not sideload anything now because through uninstalling an extra deal or two i should of, it wont allow me to enable unknown sources installation through menus. if anyone knows a way to do this through terminal of linux that would be great
thanks to any help
or would there be any way to use the water beta without the cable and only using adb or any other steps. which to my understanding is the only rom so far. thanks
If you are rooted You should I think be able to run these commands from a terminal in Linux, if you meant a terminal on your kindle then take off the and shell in the commands I list to run.
Code:
adb shell
su
reboot bootloader
I think if you are rooted it will kick it into fastboot and you can restore without a cable.
Sent from my LG-P769 using Tapatalk
thanks for the quick reply. yeah i am speaking of terminal from debian/ubuntu. I enter those commands you give me and it is recognizing the device. With adb I can even push files to install since it is screwed up and I can't access the menu part for installing from unknown sources. that is the worst part of the few issues I have with it.
after I enter those commands it only reboots normally. it doesn't go into the bootloader. I can get it to go into recovery mode where I am able to just do a normal wipe of the device but that is about it.
just to make sure I understand this. with a fastboot cable and all it is a different method from just a normal "wipe and reset" isn't it? it is using an untouched .img or something to put back to actual FACTORY as if bought from store? cause the normal wipe and factory reset doesn't put back the items I uninstalled of course from system and what not.
also is this safe to do without a factory cable. I just haven't ever needed one before and even if there is an extra step or two I don't mind instead of waiting a week for a cable.
Actually you might not even need the fastboot cable, if I remember correctly the restore method for that device would normally flash a system image that is smaller and incomplete because the system IMG is to big for fastboots 's buffer, then when it was just bootable enough to have adb push a file, it would push a amazon update file and run a command that forces the system partition to update back to stock from the update zip. So you should be able to simply push the update file for your amazon os version or older/newer and force update it. I don't have instructions handy right now for doing this and its late so maybe I post them tomorrow.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
Actually you might not even need the fastboot cable, if I remember correctly the restore method for that device would normally flash a system image that is smaller and incomplete because the system IMG is to big for fastboots 's buffer, then when it was just bootable enough to have adb push a file, it would push a amazon update file and run a command that forces the system partition to update back to stock from the update zip. So you should be able to simply push the update file for your amazon os version or older/newer and force update it. I don't have instructions handy right now for doing this and its late so maybe I post them tomorrow.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
if you could do that that'd be awesome. thanks. I just read up about a locked bootloader but I've seen it's made some progress. I just need to be sure to not turn it into a drink coaster lol.
I finally found a way to do factory reset thanks to gran pc
How to reinstall FireOS
Botched your /system partition beyond recognition? Everything is broken? Dropped your #Kindle in a sea of piss and need to RMA it? Fear not! You can just reinstall FireOS and get it looking just as if we had never touched it!
First of all, you'll have to root your tablet. I'm assuming you know how to do this!
Once that's done, put this file -- https://s3.amazonaws.com/kindle-fire-updates/update-kindle-11.3.1.0_user_310084920.bin -- in /sdcard/ (you can use adb push).
Then run these commands:
jesunoiMac:multidownload granpc$ adb shell
[email protected]:/$ su -
[email protected]:/# cp /sdcard/update-kindle-11.3.1.0_user_310084920.bin /cache/update.zip
[email protected]:/# echo --update_package=/cache/update.zip > /cache/recovery/command
[email protected]:/# exit
[email protected]:/$ exit
jesunoiMac:multidownload granpc$ adb reboot recovery
If everything went well, you should see the 'installing update' screen -- and once you're booted, we're back to stock! We did it!!!!!!
s3.amazonaws.com/kindle-fire-updates/update-kindle-11.3.1.0_user_310084920.bin
funny thing is I rerooted after the clean update and forgot all about OTA's being automatic of course. The damn thing upgraded to 11.3.2.2 which I searched has NO root exploit right now. I am wondering if I can do the same above steps to go back to 11.3.1 but that is a downgrade and I am worried about a brick although amazon new update is like an iphone you can't tell any difference haha
also is the above way how you install ICE or hellfire?
slixz85 said:
I finally found a way to do factory reset thanks to gran pc
How to reinstall FireOS
Botched your /system partition beyond recognition? Everything is broken? Dropped your #Kindle in a sea of piss and need to RMA it? Fear not! You can just reinstall FireOS and get it looking just as if we had never touched it!
First of all, you'll have to root your tablet. I'm assuming you know how to do this!
Once that's done, put this file -- https://s3.amazonaws.com/kindle-fire-updates/update-kindle-11.3.1.0_user_310084920.bin -- in /sdcard/ (you can use adb push).
Then run these commands:
jesunoiMac:multidownload granpc$ adb shell
[email protected]:/$ su -
[email protected]:/# cp /sdcard/update-kindle-11.3.1.0_user_310084920.bin /cache/update.zip
[email protected]:/# echo --update_package=/cache/update.zip > /cache/recovery/command
[email protected]:/# exit
[email protected]:/$ exit
jesunoiMac:multidownload granpc$ adb reboot recovery
If everything went well, you should see the 'installing update' screen -- and once you're booted, we're back to stock! We did it!!!!!!
s3.amazonaws.com/kindle-fire-updates/update-kindle-11.3.1.0_user_310084920.bin
funny thing is I rerooted after the clean update and forgot all about OTA's being automatic of course. The damn thing upgraded to 11.3.2.2 which I searched has NO root exploit right now. I am wondering if I can do the same above steps to go back to 11.3.1 but that is a downgrade and I am worried about a brick although amazon new update is like an iphone you can't tell any difference haha
also is the above way how you install ICE or hellfire?
Click to expand...
Click to collapse
ah good you found it before i could look it up. It will downgrade just fine, but you will probably need a fastboot cable to do it. If ICE or hellfire are roms then no, the 2013 isn't flashable with the exception of kindlewater. Since the bootloader is locked we are limited to using amazon's bootimg(kernel+intram fs).
stunts513 said:
ah good you found it before i could look it up. It will downgrade just fine, but you will probably need a fastboot cable to do it. If ICE or hellfire are roms then no, the 2013 isn't flashable with the exception of kindlewater. Since the bootloader is locked we are limited to using amazon's bootimg(kernel+intram fs).
Click to expand...
Click to collapse
ok sounds like I need to find out if putting water on this without a fastboot cable is possible then
Last night I sideloaded the 5.1.1 update to my Droid Turbo. While playing around with it this morning, I accidentally clicked the 'Force RTL' option under accessories. Immediately after, my phone crashed, and on boot would display 'system ui has stopped working' indefinitely. The wallpaper would load, and the alert modal would appear, but clearing it just kicked up another 'system ui has stopped working' modal a few seconds later.
I cleared the cache, and now when I reboot the device, it comes up with the Recovery Andy image with 'no command' below. I don't mind doing a factory reset, but I have a LOT of data I'd lose in the process. All of my pictures are backed up to Dropbox/G+, but I have a lot of other files and backups that I neglected to save externally prior to the update ... because I'm a genius.
When I try to reapply the update, I get a message indicating "/system/app/3c_main.apk" has unexpected contents. I've tried to push from SD and from ADB, both with no luck. At this point I'm happy to just reset the device, but I want my data off first. All ADB commands with the exception of SIDELOAD return 'error: closed', so I can't even backup my files.
Ideas? Help?! ANYTHING?!
spikejnz said:
Last night I sideloaded the 5.1.1 update to my Droid Turbo. While playing around with it this morning, I accidentally clicked the 'Force RTL' option under accessories. Immediately after, my phone crashed, and on boot would display 'system ui has stopped working' indefinitely. The wallpaper would load, and the alert modal would appear, but clearing it just kicked up another 'system ui has stopped working' modal a few seconds later.
I cleared the cache, and now when I reboot the device, it comes up with the Recovery Andy image with 'no command' below. I don't mind doing a factory reset, but I have a LOT of data I'd lose in the process. All of my pictures are backed up to Dropbox/G+, but I have a lot of other files and backups that I neglected to save externally prior to the update ... because I'm a genius.
When I try to reapply the update, I get a message indicating "/system/app/3c_main.apk" has unexpected contents. I've tried to push from SD and from ADB, both with no luck. At this point I'm happy to just reset the device, but I want my data off first. All ADB commands with the exception of SIDELOAD return 'error: closed', so I can't even backup my files.
Ideas? Help?! ANYTHING?!
Click to expand...
Click to collapse
Did you use the zip from Rootjunky?
Sent from my Droid Turbo using Tapatalk
zefir738 said:
Did you use the zip from Rootjunky?
Sent from my Droid Turbo using Tapatalk
Click to expand...
Click to collapse
Yes
spikejnz said:
Yes
Click to expand...
Click to collapse
You might have to wait until the OTA is available for manual download and then flash it via RSD Lite. The way the zip works is it'll only install if you have version 21.44.12.en.us installed. You have 23.11.38 so it won't install now.
Sent from my Droid Turbo using Tapatalk
zefir738 said:
You might have to wait until the OTA is available for manual download and then flash it via RSD Lite. The way the zip works is it'll only install if you have version 21.44.12.en.us installed. You have 23.11.38 so it won't install now.
Sent from my Droid Turbo using Tapatalk
Click to expand...
Click to collapse
Yikes. OTA is supposed to drop today, so hopefully that becomes available soon thereafter. Not sure how long I can survive without my phone.
spikejnz said:
Last night I sideloaded the 5.1.1 update to my Droid Turbo. !
Click to expand...
Click to collapse
I assume you mean the 5.1 update? or did you try to use a 5.1.1 update for some other phone by mistake? if so there may be no easy solution.
I don't accept defeat. Everyone said my data was a lost cause, and that Factory Reset was my only hope. Yeah, well who's copying data off his device right now?
THIS GUY.
I downloaded the firmware, removed the "erase userdata" line from the batch file, and ran it to restore the images and partitions.
I then cleared the cache (again) and rebooted my device.
Back to the 'System UI has stopped' loop
Tried unsuccessfully to send ADB commands to the device
Opened and ADB Shell in Cerberus Dashboard, but kept getting disconnected
Sent an Unlock command in Cerberus Dashboard to my device ... voilla!
UI is still crashing, but Windows is now attempting to install drivers
After trying to manually install drivers for an extended period of time, decided to attempt it on my Mac
BOOM, FS mounts and Android File Transfer is now accessing all the files, even if my display is all jacked!
Next comes the factory reset. I knew there was a reason I installed Cerberus on my non-rooted device.
Fix RTL via ADB
I had this problem on my turbo after reading about a possible fix for snapchat image problems.
After a bit of googling, I came up with this simple fix.
This will only work if ADB Debugging is enabled and your PC is already authorized.
No need for root.
Code:
adb devices
adb shell
settings put global debug.force_rtl 0
reboot
And I suppose if you do NOT already have ADB enabled et al, you're SOL?
AnoraxAudio said:
And I suppose if you do NOT already have ADB enabled et al, you're SOL?
Click to expand...
Click to collapse
If your phone has a secure lock screen, it will not recognize a usb port for file transfer or ADB mode until the password/pin/pattern/etc. has been entered. The Cerberus method described above worked because it was able to meet this requirement. With this in mind, you have the following options depending on your lock screen situation:
1. Insecure lock screen, ADB previously enabled: use the ADB method described above.
2. Insecure lock screen, ADB disabled: Plug in the USB, transfer over your important files, reboot the phone in bootloader mode, select recovery mode, perform a factory reset.
3. Secure lock screen (all cases, assuming you can't unlock it with Cerberus or something similar): Wipe cache through recovery to see if that helps anything. If it doesn't, you can try reflashing the system image via mofo or fastboot to see if that helps anything. If not, bite the bullet and perform a factory reset. You will lose your data.
Now if you have mofo, you might be able to flash a rooted rom that can perform the adb method using a su.d script, but I'm not entirely sure about that.
Background
Okay so the glass on my 2013 Moto X broke on September 27th I ordered a new one and while changing it I accidentally broke the digitizer so I disconnected the digitizer and the phone turned on while my digitizer with disconnected then i had no way of turning it off while my digitizer was disconnected the phone started to vibrate every 3 seconds until the battery died... so I was forced to switch over to my Nexus 6 because at the time that was my backup phone because I love the performance of my Moto X.. now a few months later yesterday to be exact my new digitizer arrived and I brought my Moto X back to life powers on and performs just fine
Problem
My wrist twitch to activate camera doesn't work
My dual chop to activate led doesn't work
Whenever I make a phone call or receive a phone call my screen turns off automatically but the phone call works just fine once the phone call has ended my screen does not turn back on I have to reboot the phone to turn on the display again
Phone info
2013 moto x on 5.1.1 stock rom locked bootloader rooted using crashes method with ultra slim root
any help or tip is greatly appreciated
Maybe, but it really depends what's actually wrong. The Moto has a TI MSP430 chip that handles all that 'motion, wave-to-wake, chop-chop' stuff and it's loaded from a /firmware folder or partition (have forgotten at this point). @masterifla figured out which files it was on 4.4.4 & 5.1 that got uploaded to the 430 and wrote a .zip file to change from 4.4.4's "wave to wake" to 5.1 "chop chop" or vice versa. I fixed some little bug in it, and stuck the working .zips up in this post although they may be elsewhere as well: (so :: these zips contain the firmware that actually does the wave-to-wake stuff and can be 'recovery-flashed')
http://forum.xda-developers.com/showpost.php?p=63616790&postcount=17
At least if that works, you'll know that it was the firmware for that chip, and if not, it might actually be the 430 chip(which you can see in the teardown). The post by me and anything by masterifla should be pretty well explained.
Cheers.
but have a locked bootloader I can't flash anything...but you gave hope maybe if I use rsd lite to flash stock I can fix this
BADDINOROX99 said:
but have a locked bootloader I can't flash anything...but you gave hope maybe if I use rsd lite to flash stock I can fix this
Click to expand...
Click to collapse
There still might be a way. I keep trying to have people get this to work, but I'm not sure of the outcome yet, so give it try if you like: Here's some steps:
1) Locked bootloader / no root means mostly that you can't write system, but I'm pretty sure you should be able to temporarily boot into a PC-based copy of twrp. Once in twrp (for one time say) you are root, and you have access to anything on your gizmo. In theory, you should be able to mount system read-write and change something in the file system.
2) Get the correct copy of twrp and adb (from dev forum for this box) and put it on a PC with fastboot in the same folder. To make this easy, called twrp "twrp.img" and call "fastboot" or "mfastboot" fastboot.exe (I am for some reason assuming you've got a PC, not a mac or linux, but the ideas are similar.
3) quick explain of the files in the .zip from above ^^ : 8 files prefixed by MSP that are located when on the moto in /system/etc/firmware. Unzip them and stick them in that same folder.
4) Tricky part : (I think) : reboot into the twrp.img on your PC by getting your device into fastboot / bootloader mode: (so .. volume-up&down&power keys all held down for ~10 seconds perhaps, then if you've gotten it right (it's touchy), you'll be in the bootloader where it has a small tiny text list of stuff like "continue, recovery, etc).
5) you're good with the phone if you've made it here: now on the PC from that folder, type in "fastboot boot twrp.img" and good luck. If it works, your phone will be in TWRP with root access. If not, I don't know another option at the moment.
6) Probably the rest is most easily done from the PC command (or shell) window where the files are. Since your device is in the bootloader and awaiting further instruction, you should be able to use adb to talk to recovery now. so carry on:
7) (get the files from your PC (the MSP prefixed ones) onto the device, so first remount system r/w):
Code:
a) "adb remount" // supposedly should remount system toggling the read attribute to write
b) "adb push msp* /system/etc/firmware/" // copies files to device unless I've got syntax wrong, try one at a time if doesn't work.
c) "adb shell ls -al /system/etc/firmware/" // list all files, and post them back here to see if it even worked.
d) "adb remount" // system partition back to normal ro state.
d) "adb reboot" // moment of truth, a reboot.
8) after things settle post-reboot, check out "wave-to-wake" , camera twist, etc. This works on 4.4.4 or 5.1 (if this other stuff above works).
Note: I could be way off on my idea that rebooting into recovery will give you enough functionality to do this, but I'm not sure what other choices you've got without being able to root. I guess another thing I'm wondering about is why you wouldn't be able to root the phone from recovery regardless of how you booted into it. You still can't unlock bootloader, but I'm not clear on what difference it makes at the moment.
Good luck. It's a "hail mary" pass.
thanks I got my stuff working again ? I screwed up in the file install part freaked out and reflashed stock and rerooted so everything is good now once again thanks
My wife was using her moto x4 to take pictures yesterday and apparently used up almost all her storage space. she got a message saying such and that some apps won't work properly until storage is freed up. She was able to take a couple more pictures but when she tried to text them to someone she couldn't open up hangouts. She rebooted her phone and now its stuck in a bootloop. Won't go past the Android One logo, and restarts after a few seconds. I've been able to get to recovery mode where I thought there used to be a delete cache option, but the only thing I saw was data/factory reset and I wanted that to be the last option since my wife doesn't want to lose her pictures of our kids. They weren't backed up to photos yet because we weren't on wifi. I have used ABD in the past and found a command to delete cache "fastboot erase cache" but that didn't help. I did also tried Mount /system and after doing that the first try it blipped a Motorola logo after the Android One but then went immediately back to bootloop and not getting past Android One.
Is it possible to pull the pictures off her device without being able to boot?
Any ideas to make it boot without doing a factory reset? I assume this is a storage issue but maybe just big coincidence?
I have the Motorola USB utility on my computer, and the device is stock Android 8.1, stock recovery and not rooted or anything.
Thanks,
Richard
boot back into recovery and adb pull the pictures.
so, you boot into recovery..then do adb shell.
then cd /sdcard/DCIM
do ls
you should see another folder or the pictures and videos.
then do exit to come out of adb shell and follow this to pull the folder
https://stackoverflow.com/questions...pull-all-files-of-a-folder-present-in-sd-card
munchy_cool said:
boot back into recovery and adb pull the pictures.
so, you boot into recovery..then do adb shell.
then cd /sdcard/DCIM
do ls
you should see another folder or the pictures and videos.
then do exit to come out of adb shell and follow this to pull the folder
Thanks for the quick reply. I get an error: no devices/emulators found. I don't think my wife has USB debugging enabled. Any other options?
Thanks,
Richard
Click to expand...
Click to collapse
when did you get the error?
Sorry, it occurs at the first step, the adb shell command.
Granted, my experience with using adb is limited but my understanding was that you can't use it unless USB debugging is enabled. Playing around a bit more, my computer doesn't seem to recognize the usb connection unless I chose apply update from ADB but I think that only allows sideloading. The adb shell didn't work and adb devices empty there as well.
Thanks,
Richard
rjschwar said:
My wife was using her moto x4 to take pictures yesterday and apparently used up almost all her storage space. she got a message saying such and that some apps won't work properly until storage is freed up. She was able to take a couple more pictures but when she tried to text them to someone she couldn't open up hangouts. She rebooted her phone and now its stuck in a bootloop. Won't go past the Android One logo, and restarts after a few seconds. I've been able to get to recovery mode where I thought there used to be a delete cache option, but the only thing I saw was data/factory reset and I wanted that to be the last option since my wife doesn't want to lose her pictures of our kids. They weren't backed up to photos yet because we weren't on wifi. I have used ABD in the past and found a command to delete cache "fastboot erase cache" but that didn't help. I did also tried Mount /system and after doing that the first try it blipped a Motorola logo after the Android One but then went immediately back to bootloop and not getting past Android One.
Is it possible to pull the pictures off her device without being able to boot?
Any ideas to make it boot without doing a factory reset? I assume this is a storage issue but maybe just big coincidence?
I have the Motorola USB utility on my computer, and the device is stock Android 8.1, stock recovery and not rooted or anything.
Thanks,
Richard
Click to expand...
Click to collapse
I feel horrible for you. The one pro of iOS is that bootloops are less often but can happen (happened on iPad 6 but reinstalled iOS without data loss). I will always root my phone and install TWRP out of these horror stories. Do you still have the issue?
Hi,
I am in a bit of trouble I have a Motorola Edge 20 (2022) and I was playing with De-Bloater under Magisk. It worked really fine until I pushed the limit of how many Motorola apps i can remove. The last one was the wrong one, I think it was Motorola settings storage (provider) or so. Now the phone won't boot anymore and I was stupid enough not to back up the photos I made in the last three days.
I don't have TWRP on the phone (it's not available yet), so the Android recovery has to do. I saw that I can mount /system, but I don't know how to modify or even read it after mounting it. The internet is full of instructions of how to mount it and always mentions that you can then modify anything on it, but nowhere does it explain exactly HOW to do that
adb shell/push/pull just says "unable to... : closed"
The second option seems to adb sideload some zip. But what zip would I have to flash to disable the De-Bloater without factory resetting everything?
thanks
whoohoo! I jst discovered Safe Mode. Immediate problem thereby solved However, I am still interested in the first part of my question: how to use the mounted /system in Recovery Mode?
michael-brade said:
whoohoo! I jst discovered Safe Mode. Immediate problem thereby solved However, I am still interested in the first part of my question: how to use the mounted /system in Recovery Mode?
Click to expand...
Click to collapse
with stock recovery, youre unlikely to win as /data is decrypted (usually) and /system is largely unmountable and writeable (at least easily)
the usual prescription if you cant get into safe mode is:
Code:
adb wait-for-device shell magisk --remove-modules
from the bible (read on for TWRP ways which are 100% easier):
Magisk - Installation and troubleshooting:Magisk and MagiskHide Installation and Troubleshooting guide
didgeridoohan.com
which obviously removes all modules, even us experienced folks fond ourselves using the magical key combo to get into safe mode on occasion because we flew too close to the sun doping something in magisk
ironically debloating wasnt one of those times for me, i gave a log of what i debloated to the author of one debloater modules recently when he released a new version of his module and he was like "and it still boots?"...the list of debloated packages was at 135, and i could remove even more...
Thanks, good to know. But even adb wasn't able to connect anymore, Android got stuck even earlier.
However, I don't really mind if /system is read-only, I am more interested in how to (even theoretically) use the stock recovery. There is no manual and nobody said anything so far. So once you clicked "mount /system", what to do?
Lenovo (owner of Moto) has a online 'rescue' site that u can go to with your phone connected to the PC and it'll flash your Moto back to stock...prolly won't retain ur data, but it saved my a$$ a few times with my old twrp-less A/B slotted Moto G7. Can't recall the exact url but am sure u can dig it up with google.
Zaxx32 said:
Lenovo (owner of Moto) has a online 'rescue' site that u can go to with your phone connected to the PC and it'll flash your Moto back to stock...prolly won't retain ur data, but it saved my a$$ a few times with my old twrp-less A/B slotted Moto G7. Can't recall the exact url but am sure u can dig it up with google.
Click to expand...
Click to collapse
Hmm... but I can already do that without their help using fastboot. No need for the Android recovery.
Isn't it strange that there is a function we don't know how to use or how it works?