KF stuck in TWRP 2.0 boot loop - Kindle Fire General

Hello all,
I realize that I am a noob. I realize you can see the "posts=1". I realize that you guys have probably seen the above title a million times before. Honestly though, I feel like I'm at end. I've scoured Google & xda-dev for 5+ hours now and I can't find a single answer that works. So here's my "special" problem:
Info: Windows 7 Home Premium 32-bit
Kindle Fire (previously) temp rooted with BurritoRoot. Installed TWRP 2.0, firefirefire, google-framework.apk, and the rest of the lot, then de-rooted.
Yesterday, I realized that the Music tab on my KF was crashing. I was literally unable to look at my music. About half an hour later, I was unable to read books as well. Thinking about it now, I'm pretty sure that it was because I had forgotten to uncheck "update automatically" for the stock kindle apps in the Android Market/Play Store, making it unusable in the stock Kindle OS. Oh well, at least the source of the problems was found.
Of course, being the happy little idiot I am, I thought I should just restore the firmware via stock OS. I could just re-root and reinstall all of my apps, right? Huge mistake. After buzzing around for thirty seconds, Kindle rebooted. Instead of launching into the stock OS for initial config though, it dropped itself into TWRP 2.0 without me even pressing the power button. TWRP, of course, kindly informs me that the entire device is blank.
I fretted for a little bit, then connected my Kindle to my computer. I already have the adb drivers installed, but Windows shows it as Unknown Device.. It also helpfully insists that it has malfunctioned and tells me to buy a new one.
I turned to Vashypoo's KFU. A bunch of threads said it was stuck in fastboot and KFU could could put it back into regular (4000) boot. However, KFU's bootmode menu is unable to find the device, which is in the TWRP menu.
I tried using command prompt to gain access.
Code:
adb shell
then
Code:
fastboot -i 0x1949 idme bootmode 4000
gives me "/sbin/sh: fastboot not found" which is really scaring me.
Back to KFU, I tried reinstalling stock firmware from there. It apparently installed fine (how?). I doubt that it did, but TWRP is showing some signs of an OS in the device (not sure if its the full OS or not). Bootmode 1 now giving me no response (!)
Since all I really need is access to the SD storage to upload the OS, I tried to reinstall the drivers. Windows implores that its "Unknown Device" driver is the correct one. Trying to choose the "Android Phone" driver sens me back to "Unknown Device" for some reason.
I went back to basics. Used the mount function in TWRP to mount USB storage. AS you can probably guess, absolutely no response from PC.
Dearest XDA-devs i reach out to you. I'm at end. I don't know what else to do. If any of you can help me, I'll be grateful. While I'm not a complete noob (know my way around computer root, experienced jailbreaker/rooter, know basic command line) I'm utterly lost at what to do know. At the risk of sounding like a pretentious prude, I'll make a list of accomplishments to help anyone else who happens to have strangely fallen down the same path I have. As always, if you ever need more details, just ask.
nxtfari​
-----------------------------------------------------------------------------
[X] Reason for stock app crashes (Play Store auto-updated stock Kindle apps)
[X] Reason for boot loop (I'm an idiot/Restore via stock OS)

If you can able to get to adb shell, you won't be able to run fastboot commands from there. Fastboot commands can only be issued to the KF when the KF is in fastboot mode... adb commands can only be issued when the KF is in recovery or booted to the OS. Also, the fastboot command is on your computer (probably in the same directory as adb). If you are in adb shell, it's going to run executables stored on your KF, so you are essentially looking in the wrong place for fastboot. That's why it's telling you that the command can't be found.
If you can get into adb shell while booted into TWRP, you should just be able to just run 'idme bootmode 4000' to get the bootmode back to normal and reboot. Hopefully, your system is intact and is able to boot up. Otherwise, you need to get back to TWRP and you can probably just 'adb push' the stock software onto your /sdcard partiton and use TWRP to install it.

Thank you so much
Thank you so much,
i have the same problem, and with this on a cmd:
#adb shell
#idme bootmode 4000
#reboot
now I have again a kindle fire ^_^
Thanks again

nxtfari said:
Hello all,
I realize that I am a noob. I realize you can see the "posts=1". I realize that you guys have probably seen the above title a million times before.
Click to expand...
Click to collapse
I think I speak for most of the people here when I say, your valid attempt at thoroughly explaining your problem, how you arrived at your problem, and the steps you took to resolve your problem is greatly appreciated and goes a LONG way towards getting the help you need in a timely and orderly fashion.
If everyone addressed their problems this way, our forums wouldn't be constantly inundated with threads that require twenty replies to fix a simple problem when it should only take a couple at best.
Wishful thinking
Sent from my Amazon Kindle Fire using xda premium

Related

TWRP Recovery installation through KF Utility bricked my Kindle

Hello, brand new to the Kindle. I rooted my device just fine last night and decided to use Kindle Fire Utility to install TWRP. ADB was recognizing the device perfectly and the script seemed to be running fine until it rebooted the Kindle. At that point the script said "reboot: operation not permitted waiting for device" for an extended period of time. After waiting awhile, at this point I did something I probably shouldn't have, I unplugged the Kindle and rebooted it using the power button. It's been getting stuck at the "kindle fire" boot animation ever since. I haven't gotten a screen with a triangle and fire logo.
I tried following the instructions in the sticky but it seems adb no longer recognizes the device, so I can't push zergRush or anything past that.
Is it permanently bricked or is there a method to fix my problem yet?
Thanks for any help.
_______________________
Update: kindle was fixed by uninstalling drivers, reinstalling as android composite usb device, and switching it out of fastboot. not permanently bricked.
sounds like its in fast boot.
open the utility again, check if its in fast boot, if it is run the install command again. if u can't get it installed, use utility to change boot mode back to 4000.
I had the same problem this method worked for me http://forum.xda-developers.com/showpost.php?p=20509949&postcount=245 http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222
Thanks for the fast replies!
When I try to change the bootmode using the fastboot it just says waiting for device and never progresses. KindleFireUtility shows ADB Online, Boot status at 4002, and fastboot as offline. Device manager doesn't show a Kindle, just an android adb interface with a yellow ! triangle.
I did restart the PC once and the kindle a few times. No luck yet.
I installed the ADB Composite driver again for the device and got this error (attached)
I had the same issue. It turned out that I had forgotten to update my computer with the drivers needed for TWRP install after copying them to the Android and .Android folders. I was able to get to the first reboot.. waiting for device and then checked device manager when it wouldn't progress. I found that the the driver was unrecognized. After updating the drivers in device manager, TWRP completed install successfully and I was able to backup my FW6.2 and then flash CM7.
uninstall the driverand use the driverin the utility thread? someone said leaving ur kindle connected to ur pc and rebooting ur pc will reboot the kindle? if it works su with terminal and change bootmode back to 4000
sent from my kindle fire
Alright everyone, I got it working after uninstalling the driver for the Android device, shutting down, starting up again, and plugging in and reinstalling the driver, then changing the bootmode using the instructions previously posted. Thank you all SO MUCH for helping as much as you could. Now to try this again!
terracode said:
I had the same issue. It turned out that I had forgotten to update my computer with the drivers needed for TWRP install after copying them to the Android and .Android folders. I was able to get to the first reboot.. waiting for device and then checked device manager when it wouldn't progress. I found that the the driver was unrecognized. After updating the drivers in device manager, TWRP completed install successfully and I was able to backup my FW6.2 and then flash CM7.
Click to expand...
Click to collapse
Now I'm wondering what you mean by making sure the drivers are installed for TWRP to install correctly. Obviously I missed a step the first time, what do I do to make sure I don't miss it again? Right now when I try to install TWRP again it says "The system cannot find the filepath specified" several times.
would recomend to use following:
http://forum.xda-developers.com/showthread.php?t=1399889
download the utility and prepare according:
http://forum.xda-developers.com/showthread.php?p=20574755#post20574755
change bootmode, install twrp or whatever with the utility
Got twrp on it last night successfully and flashed CM7.
My question is somewhat related to this thread...
I'm on 6.2 (wifi turned off) and was already rooted and am trying to update to the 6.2.1 secured update with root installed update found on XDA. I'm using Kindle Fire Utility v.6, and to the best of my knowledge using the drivers included with the KF Utility program.
In the utility I show...
ADB Status: Online
Boot Status: 4000
Fastboot Status: Offline
Question is I'm not familiar with fastboot and unclear if I have everything configured in order to (safely) install TWRP. In a command prompt when I type 'fastboot devices' nothing is displayed ("adb devices" shows the device). Combined with the fact I've never seen anything but "Offline" for the Fastboot Status, I'm a little concerned I'm missing a piece of the puzzle and hesitant to install TWRP until I know better.
Any help/advice would be appreciated. Thanks!
look at my post on page 1 of this thread !
@Stevebro: I believe if you are using KF Utility v.6, then you should be good to go. As long as you installed and updated the usb Drivers and then ran zergRush, you should be at the point where you can install TWRP. Just make sure you are using the latest version of KF Utility and it should go pretty smoothly.
... After you install TWRP, I'd recommend going back to your KF OS and do a Titanium Backup of your apps and then doing a TWRP backup. When you flash to CM7 you can restore all your apps easily and painlessly using Titanium backup to restore with the Batch restore option.
Couple nervous moments, reboots and switching out of fastboot mode in the utility... but it all went well. Thanks for the help!!
glad to hear everything is fine ...
Glad to hear everything worked out. I myself sat staring at the "yellow triangle" for a couple of hours. lol, but I just kept working through it and tried not to panic and I got everything working again.
I think OP should edit the first post, or get a mod to edit the title. I keep reading random posts about "lot's of people permanently bricking their Kindle Fires" while I cannot recall a single instance of someone bricking and having to return one and it is getting tiresome.

How I was able to unbrick my Kindle Fire

Hi everyone.
I managed to brick my kindle fire within an hour of purchasing it, but using the suggestions on this forum, I was able to get it back up and running in a few hours.
The method that I had to use involved suggestions grabbed from several threads, so I wanted to provide instructions on exactly how I managed to fix mine in case someone ends up in the same situation as me.
For starters, I had just updated my Kindle Fire to 6.2.1 and I was messing around with trying to get the google app manager installed. I rooted the device, and I was changing permissions in the /system/app directory when the device crashed and became stuck on the boot animation. I did not have TWRP installed at the time.
So if you are like me, or in a similar situation, this may be applicable.
These instructions assume that you have adb on your computer.
First, ensure that you are able to communicate with your device using ADB. Verify this by using the command:
adb devices
Click to expand...
Click to collapse
or by using the kindle fire utility and ensuring that the status is online.
If you are not able to communicate with your device AND have the boot animation (right to left reflection across the "Kindle Fire" logo text), you likely have a driver issue.
Several possible ways to resolve this. First, I recommend going to device manager and unistalling the driver for the android phone adb interface. Unplug the kindle fire and plug it in again. The device should show up without a driver as "kindle". Manually apply the proper driver again and check the adb connection. If this does not work, uninstall the driver again and add 0x18d1 at the end of adb_usb.ini on a line underneath "0x1949" and reapply the driver. Toss in a few shutdowns in between some of these steps if you are still having trouble. Hopefully you now have a connection to your device.
If you are not able to communicate with your device AND do not have the boot animation (right to left reflection across the "Kindle Fire" logo text), your kindle fire is in the wrong bootmode (likely fastboot).
To fix this, download fastboot.exe (if you don't already have it) and run the following command, even if you don't have an adb connection)
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
or if that doesn't work
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
Click to expand...
Click to collapse
Your kindle fire should restart and now be stuck at the logo with animation, and you should have the ability to communicate with your device through adb now.
Now, you should download the kindle fire firmware (6.2.1 as of the time of writing this) from http://www.amazon.com/gp/help/customer/display.html?nodeId=200790620. Rename this to update.zip and drop it in the same directory as adb.exe on your pc. Execute the following command.
adb push update.zip /sdcard/
Click to expand...
Click to collapse
Now, you need to use fbmode to enable the fastboot mode, per pokey9000's instructions at http://forum.xda-developers.com/showthread.php?p=20755810
Assuming that that was able to complete successfully, you need to flash TWRP 2.0 per pyrostic's instructions at http://rootzwiki.com/topic/12363-ho...our-kindle-fire/page__pid__301703#entry301703
You now should be stuck at a screen with a yellow triangle. Pressing the power button several times until it turns orange should bring you into the recovery screen. Do the following:
Wipe cache
Wipe dalvik cache
Factory reset
Go back to the home screen and select install -> update.zip
And when that's done, you can tell it to reboot.
It'll think for a minute or two at the kindle fire boot, and then it will go into the initial setup screen. You're now the proud owner of a working fact0ry default kindle fire!
Quick note: I wrote this from memory quickly to try to help anyone experiencing problems. I'm no android expert, so if there are ways to improve on this or corrections to be made, please let me know so that the community can benefit.
And I don't want to appear to take undue credit for any of these instructions. I did not come up with anything on this guide on my own, everything came from various threads on this forum. These are just the steps that I followed to successfully bring my kindle fire back from death.
Man, My Kindle Fire does not even get detected by my PC
Now, you need to use fbmode to enable the fastboot mode, per pokey9000's instructions at http://forum.xda-developers.com/show...php?p=20755810
Assuming that that was able to complete successfully, you need to flash TWRP 2.0 per pyrostic's instructions at http://rootzwiki.com/topic/12363-how...03#entry301703
You now should be stuck at a screen with a yellow triangle. Pressing the power button several times until it turns orange should bring you into the recovery screen. Do the following:
Wipe cache
Wipe dalvik cache
Factory reset
Go back to the home screen and select install -> update.zip
And when that's done, you can tell it to reboot.
It'll think for a minute or two at the kindle fire boot, and then it will go into the initial setup screen. You're now the proud owner of a working fact0ry default kindle fire!
****When I run the fbmode I am getting stuck on the boot logo screen. Can someone please help me??
that is normal - you are in fastboot mode now - adb commands don't work in this mode - fastboot commands do - resume with the description ...
Thanks for your post.
I also "bricked" my kindle the day I got it but my issue was not having the correct drivers installed when I started the rooting process. My drivers would recognize the Kindle when it was booted normally but when it went into fastboot mode the Kindle would just show as "Unknown Device" in device manager. In windows you can't remove the drivers for unknown device so I had no way of backing out the old drivers.
What I ended up doing was grabbing my other laptop and making sure I had the correct drivers installed, then connected the kindle and was able to back it out of fastboot mode.
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
umarsl said:
Man, My Kindle Fire does not even get detected by my PC
Click to expand...
Click to collapse
Does it show up as "unknown Device" in device manager?
you can uninstall the drivers
win 7:
http://www.petri.co.il/removing-old-drivers-from-vista-and-windows7.htm
xp:
http://www.techrepublic.com/article/removing-unused-device-drivers-from-windows-xp-machines/6017628
Just wanted to say thanx for the post. I ran into the exact same condition that the op did where I inadvertently screwed up the permissions on the /system/app directory which caused the kf to wig out and brick. I wished I had seen your post earlier because I ended up going to many posts and piecing together the information which was a little confusing at times. The op is great and I just wanted to point out two observations that seemed to me the most confusing working through the issue and getting it unbricked and hopefully will bring some clarity for folks.
1. Understanding the different states of the "kindle fire" logo.
- Shimmering animation and appears to loop = normal boot mode and is the state that you should be able to communicate with adb. This is the state where you can push files to the kf like twrp and fbmode which is what is needed to get kf in fastboot mode when bricked like this.
- The logo is static and does not "wink" out or loop = fastboot mode. This is when you use fastboot commands on your PC to change boot modes and also execute files such as twrp to get it installed once you pushed it to the kf with adb.
2. USB Drivers.
- This can be a real killer. After playing with this for hours, the one thing that I found that helped the most was when the driver stopped working I would unplug the kf from the PC and then hard reboot the kf (hold on/off ~20 seconds) then just plug back in, don't use on/off. Keep the device manager open on the PC and watch. You will soon start to see a pattern when you have the right driver and do this a few times.
Once these things are ironed out all eventually works out. BTW, this occurred after my kf was upgraded to 6.2.2. So the instructions and tools and everything else you will find still works. Good luck to anyone working through this issue. Just remember, if you can communicate with it, it's almost certain there is a way to recover it.

[Q] Silly me, bricked my kindle fire after TWRP seemed to fail.

So, as many new KF rooters have, I seem to have bricked my KF. I rooted it just fine, but when installed TWRP through KFU .93 the process seems to have stopped. After waiting over an hour and reading countless "I've been stuck installing TWRP through KFU .93" threads, and seeing many "I switched to .91 and it worked fine" responses, I decided to give that a shot. After unplugging and hard resetting my KF, it is still stuck on the KF logo screen. No yellow box, just the logo screen.
When I plug the KF into my computer, the device is recognized and the proper KF drivers are installed, but I can't get adb to work at all. Every attempt returns a "Device not found" or a "Server didn't ACK." The device does not show up on my list of attached devices, but in Device Manager it is loaded.
I'm unsure of what the next step should be, as I can't get the hardware to respond to anything but resets, and I can't get the software to communicate with the hardware from my PC. I really don't want to admit defeat and contact Amazon.
*edit* Through more research I've made some progress. Opening KFU and selecting the bootmode option, and then when it says "waiting for device" hard resetting the KF and letting KFU change the bootmode to Recovery has done some things. I got a message saying "Failed ..." but it flashed too fast for me to read. Then, upon several restarts, I received a message saying that the KF needed to factory reset, which it is doing now.
As of right now I have a Factory Resetted, working KF. My updated question is now "Where did I go wrong?"
I assume it had to do with TWRP, as it was working until then. Should I redo the whole process using KFU .91 instead of .93? The root went of without a hitch, but the TWRP was what killed me.
Also, do I do Root THEN TWRP, or TWRP THEN Root? I guess I might need Root access to install a Recovery console, but I'm unsure.
use KFU to root, then hit up my gscript install method in the development thread. easy peasy.
but for the record, you were in fastboot, so it won't see adb commands..
fastboot -i 0x1949 oem idme bootmode 4000 maybe woulda saved you. but avoid fast boot entirely, n use my gscript method.
heres how i did it
I was trying to unbridled my kindle fire all last night and about 5hours today.here is how I did it (don't get your hopes up too high,it might not work)
1.Download kindle fire utility
2.Unzip kindle fire utility
3.To install the driver,its easy,just plug in your kindle, when it pops up with the install wizard say pick from the location of: KindleFireUtility>drivers>kindle
4.run kindle fire utility,select 1 then select 1 again
That's it, hope it helps

I know it's the wrong forum, but....please take a look

I really need the help of one or more of this forums intelligent minds. As I'm sure you'll see, I've posted this in the QA forum, but have had no hits so far....thus the reason for posting here.
So, about 6mos ago, my Nexus 10 stopped working and I couldn't get it back working...eventually moved onto a new tablet, which now I hate....
Anyway, I figured I'd head back to my N10 because I loved it. However, one of the reasons I left it was because it was stuck in bootloop and I was pretty sure it was bricked.
The bad news, I have followed MANY, if not ALL, of the suggestions on getting it back, I just cannot get it to boot. The good news, fastboot connects with the tablet. So, some specifics:
The tablet WILL boot into fastboot and I can send commands and the tablet is unlocked (also, I believe someone said they had issues because they had an older version of ADB and Fastboot. I'm pretty sure I downloaded the 'most current' version 1.4.3). So, with that, I was able to do the fastboot erase functions, such as cache, userdata, system, etc... and then also load the bootloader (mantafm01) and also send the stock .zip file (image-mantaray-....) and the tablet appears to load everything fine. Thumbs up, right? However, when it reboots it stops at the 'erasing' android bot and will not pass that. I left the tablet in that state for a few minutes all the way up to 3 days...no success.
I also tried the above using Wugfresh only to have the same thing occur. So, basically, I am stuck at 'erasing' and I don't know what to do. I feel confident that the tablet has the ability to be brought back to life, I just cannot figure out how/why all of the attempts lead to the same issue.
What I can also tell you is that while fastboot 'sees' the tablet, the tablet does not appear as a device in "My Computer" like it normally did when connecting via USB. I am using the original USB cable and have tried on multiple computers, all to no avail. I've downloaded/installed the drivers, as instructed on many links. Also, while I can get to the 'Recovery Mode' by pressing Power, Volume Up, Volume Down, if I choose "Recovery Mode" on the tablet, it reboots and goes to the 'erasing' screen. I have tried flashing TWRP on the tablet using fastboot as well. And, sometimes, not all the time, the TWRP blue/black screen appears but it will not progress past that screen (i.e., it doesn't go into recovery).
So, if you can, please help. I believe I have followed all of the instructions, but I have to be missing something or not following something correctly. I'm stoked that it looks like it's only soft-bricked, I just can't get it un-bricked.
Thanks in advance! I'm at my wits' end
Try fastbooting a recovery like TWRP thati s updated then flash a rom.
disclaimer: I might be no help at all!
You have fastboot -- go learn all the fastboot commands... you need to know the tools and figure a solution!
erase... hmm? why? What about factory reset? I see you are not using LOS 13 but stock image... need root? Basically, I would factory reset/wipe sdcard, then install recovery (TWRP) [okay, so first you would need to use fastboot to install custom recovery)...THEN, push (fastboot an image.zip (LOS or stock) to sdcards, install, and reboot!
Good to have WUG... another tool in the chest (I have never seen it or used it)
Ok, so one clue is that if your computer cannot see it, that says to me RED FLAG... ADB drivers? but you say fastboot works, hmm... I think this is the problem... Koush's universal ADB drivers? official Google drivers? Could these help!
Erasing screen? Hmm...
I would say, for the hell of it, try flashing different ROMs, Recoveries, and Drivers.... you are basically trying to...
Factory Reset/wipe SDcard [system, cache, ... everything], Flash custom recovery (optional), then, some how (fastboot or mycomputer) get an image on to /sdcard, then, install, then, reboot!
Good luck!
luckyheel said:
I really need the help of one or more of this forums intelligent minds. As I'm sure you'll see, I've posted this in the QA forum, but have had no hits so far....thus the reason for posting here.
So, about 6mos ago, my Nexus 10 stopped working and I couldn't get it back working...eventually moved onto a new tablet, which now I hate....
Anyway, I figured I'd head back to my N10 because I loved it. However, one of the reasons I left it was because it was stuck in bootloop and I was pretty sure it was bricked.
The bad news, I have followed MANY, if not ALL, of the suggestions on getting it back, I just cannot get it to boot. The good news, fastboot connects with the tablet. So, some specifics:
The tablet WILL boot into fastboot and I can send commands and the tablet is unlocked (also, I believe someone said they had issues because they had an older version of ADB and Fastboot. I'm pretty sure I downloaded the 'most current' version 1.4.3). So, with that, I was able to do the fastboot erase functions, such as cache, userdata, system, etc... and then also load the bootloader (mantafm01) and also send the stock .zip file (image-mantaray-....) and the tablet appears to load everything fine. Thumbs up, right? However, when it reboots it stops at the 'erasing' android bot and will not pass that. I left the tablet in that state for a few minutes all the way up to 3 days...no success.
I also tried the above using Wugfresh only to have the same thing occur. So, basically, I am stuck at 'erasing' and I don't know what to do. I feel confident that the tablet has the ability to be brought back to life, I just cannot figure out how/why all of the attempts lead to the same issue.
What I can also tell you is that while fastboot 'sees' the tablet, the tablet does not appear as a device in "My Computer" like it normally did when connecting via USB. I am using the original USB cable and have tried on multiple computers, all to no avail. I've downloaded/installed the drivers, as instructed on many links. Also, while I can get to the 'Recovery Mode' by pressing Power, Volume Up, Volume Down, if I choose "Recovery Mode" on the tablet, it reboots and goes to the 'erasing' screen. I have tried flashing TWRP on the tablet using fastboot as well. And, sometimes, not all the time, the TWRP blue/black screen appears but it will not progress past that screen (i.e., it doesn't go into recovery).
So, if you can, please help. I believe I have followed all of the instructions, but I have to be missing something or not following something correctly. I'm stoked that it looks like it's only soft-bricked, I just can't get it un-bricked.
Thanks in advance! I'm at my wits' end
Click to expand...
Click to collapse
Why not try this
I have not had this problem with my Nexus 10 but I did once with my Nexus 7 and it may help you.
Instead of trying to flash TWRP and run it (which is not working for you) why not boot into a temporary copy of TWRP and then work from that? To flash TWRP normally (persuming you had renamed the img file to TWRP which makes it easier) you would enter 'fastboot flash recovery twrp.img'. Instead of doing that type 'fastboot boot twrp.img'. This boots into TRWP and from there you will be able run all the options and from there flash TWRP and other images as normal.
If you are having problems with drivers have you used 'USBDeview' ? Run this as Administrator and delete all references to any phone or tablet USB driver and particularly look for devices with Vendor ID '18d1' or '04e8'. Just select them, right click on them and select 'Uninstall Selected Devices'. When they are all cleared reboot your computer and plug your tablet in and it should install the correct driver.
Another option I used successfully with a Nexus 7 in a boot loop was to connect it while running Linux. I don't have a Linux on a computer so I installed one in 'Oracle VM VirtualBox' I don't know Linux but after Googling for help I installed Peppermint Linux and then ADB for Linux. I downloaded the 'TWP' image into a folder in Linux and any other images I wanted. Connect your tablet to the USB port and then on the top menu in VirtualBox select 'Devices' then 'USB' and tick the option which shows your tablet. I then went into what we call a command prompt in Windows but which they call 'Terminal'. Then type 'ADB devices' and if you see it on the list use ADB instead of fastboot. As I mentioned my Nexus 7 was in a boot loop so I typed 'ADB wait-for-device' and as soon as it looped to a point where ADB could see it then the looping stopped and I could flash the images and recover the tablet.
All the best. I hope you are successful.
As long as you can get into bootloader mode, your good.
NOW
If you can't get into boot loader mode? as far as I know...
You're ****ed.
Unless you want to set up usb boot (might not work on Exynos, idk, this is magic to me) and solder the connectors and flash it like they do in factories. That's next level **** too, and considering an N10 is 100$ on amazon you're better off just grabbing a new one.

[Q] Complete noob needs help bypassing lock screen

Hi all; thanks for stopping by,
I've looked through multiple seemingly related threads but have been unable to find adequate answers and I am in way over my head to begin with, so please bear with me. Recently my LG G7 ThinQ became totally unresponsive so I figured I'd just use my old Moto G4 Plus while I work on fixing the G7. Problem is, the phone is locked and I have no idea what my swipe password is and I don't want to just completely wipe the phone as there is sentimental content on the phone which I'd like to access anyway.
The G4 Plus is OEM locked but I can access the bootloader, USB debugging is enabled, and I have an SD card. It is "athene_retail," operating on Android 7.0, and I do not have TWRP or CWM or the like installed on the phone. My PC is running Windows 10. Part of my problem is I'm not entirely sure how all this is supposed to work, but after hours of disorganized research I decided this thread was my best bet: https://forum.xda-developers.com/showthread.php?t=2620456 , so I have downloaded a lot of files and whatnot but am struggling with troubleshooting myself as I am likely not using them properly anyway. I tried the simplest-looking Methods -- 1 and 5 -- without success.
The problem I seemed to run into with Method 1 is at step #4 with "Apply update from ADB" and "Apply update from SD card" in Recovery Mode. What would happen is I'd "mount" the "/system" and proceed to choose one of the aforementioned "Apply update" options and the screen would just go black and then after a few seconds it would revert to a "No command" screen. Reading more into Method 1's instructions it seems like I might have to install TWRP or CWM onto my phone in order for this to work, but if that's right, how am I supposed to get them onto the phone if not through those options?
The problem I kept running into with Method 5 is "adb shell" would return "error: closed" and I haven't been able to determine why exactly. I opened cmd.exe from within the ADB folder and got "daemon started" and was able to attach device "emulator-5554" but after this point even "adb usb" would return "error: closed." I tried killing and restarting the server and a couple other potential solutions I found but to no avail. I am using
Code:
Android Debug Bridge version 1.0.41
Version 30.0.3-6597393
Any help would be greatly appreciated! :good:
hackmythinq said:
Hi all; thanks for stopping by,
I've looked through multiple seemingly related threads but have been unable to find adequate answers and I am in way over my head to begin with, so please bear with me. Recently my LG G7 ThinQ became totally unresponsive so I figured I'd just use my old Moto G4 Plus while I work on fixing the G7. Problem is, the phone is locked and I have no idea what my swipe password is and I don't want to just completely wipe the phone as there is sentimental content on the phone which I'd like to access anyway.
The G4 Plus is OEM locked but I can access the bootloader, USB debugging is enabled, and I have an SD card. It is "athene_retail," operating on Android 7.0, and I do not have TWRP or CWM or the like installed on the phone. My PC is running Windows 10. Part of my problem is I'm not entirely sure how all this is supposed to work, but after hours of disorganized research I decided this thread was my best bet: https://forum.xda-developers.com/showthread.php?t=2620456 , so I have downloaded a lot of files and whatnot but am struggling with troubleshooting myself as I am likely not using them properly anyway. I tried the simplest-looking Methods -- 1 and 5 -- without success.
The problem I seemed to run into with Method 1 is at step #4 with "Apply update from ADB" and "Apply update from SD card" in Recovery Mode. What would happen is I'd "mount" the "/system" and proceed to choose one of the aforementioned "Apply update" options and the screen would just go black and then after a few seconds it would revert to a "No command" screen. Reading more into Method 1's instructions it seems like I might have to install TWRP or CWM onto my phone in order for this to work, but if that's right, how am I supposed to get them onto the phone if not through those options?
The problem I kept running into with Method 5 is "adb shell" would return "error: closed" and I haven't been able to determine why exactly. I opened cmd.exe from within the ADB folder and got "daemon started" and was able to attach device "emulator-5554" but after this point even "adb usb" would return "error: closed." I tried killing and restarting the server and a couple other potential solutions I found but to no avail. I am using
Code:
Android Debug Bridge version 1.0.41
Version 30.0.3-6597393
Any help would be greatly appreciated! :good:
Click to expand...
Click to collapse
LMSA has a pin reset, you could try that.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
hackmythinq said:
The problem I kept running into with Method 5 is "adb shell" would return "error: closed" and I haven't been able to determine why exactly. I opened cmd.exe from within the ADB folder and got "daemon started" and was able to attach device "emulator-5554" but after this point even "adb usb" would return "error: closed." I tried killing and restarting the server and a couple other potential solutions I found but to no avail. I am using
Code:
Android Debug Bridge version 1.0.41
Version 30.0.3-6597393
Any help would be greatly appreciated! :good:
Click to expand...
Click to collapse
"emulator-5554" ? This is a emulator and not your Moto G4. Are you using any emulator? If so, stop it and connect your G4.Once your G4 is connected to ADB, it should show your G4's Serial Number in list of devices attached.
[email protected]!$h said:
"emulator-5554" ? This is a emulator and not your Moto G4. Are you using any emulator? If so, stop it and connect your G4.Once your G4 is connected to ADB, it should show your G4's Serial Number in list of devices attached.
Click to expand...
Click to collapse
Thanks for the reply.
That did seem odd but I'm a noob, so I do have BlueStacks installed on my laptop but I don't believe it was even running at the time. Could that be it? In which case, that means my laptop wasn't even recognizing the phone at all to begin with? Hmm, ok, well I think I found the problem: when I click "adb.exe" a black screen (possibly cmd?) flashes on-screen for a tiny fraction of a second and that's it. Should it be doing something more than that? Does it have a GUI?
hackmythinq said:
Thanks for the reply.
That did seem odd but I'm a noob, so I do have BlueStacks installed on my laptop but I don't believe it was even running at the time. Could that be it?
Click to expand...
Click to collapse
Yes, it could be bluestacks. It's adb connection runs in the background.
In which case, that means my laptop wasn't even recognizing the phone at all to begin with? Hmm, ok, well I think I found the problem: when I click "adb.exe" a black screen (possibly cmd?) flashes on-screen for a tiny fraction of a second and that's it. Should it be doing something more than that? Does it have a GUI?
Click to expand...
Click to collapse
adb doesn't have any GUI and cmd flashing for a second is general behaviour when you run adb.exe. You should always run it from command prompt like you did before.
try installing Moto drivers : https://support.motorola.com/in/en/drivers
if already installed better try different port/cable/pc

Categories

Resources