Good eveing-
I'm not sure where to start. I have a kindle fire HDX 7, and just attempted to root the device yesterday. I was able to roll back to 3.2.8, then upgrade to 4.5.2 and successfully root the device. Everything was good.
I then toyed around with a few methods to install GAPPS. With each method, if I didn't achieve the desired results, I would factory reset, rollback to 3.2.8, upgrade to 4.5.2, root... etc. A process which I went through 3 or 4 times just to try and get access to the google play store. The final method was to use the steps layed out In This Thread, which is where my current problem started.
I was not able to get the play store working correctly. I then attempted to do a factory reset, and **** hit the fan. Upon reboot, I was greeted by the stock android welcome screen, asking me to select a language, and giving me the option to make an emergency call. My best guess is something in the "system" folders/files in the gapps zip doesn't jive with FireOS. From the provided setup screen, I am able to select a language and hit next, and then it takes me through to the FireOS wireless setup screen - and that's where things come to a halt. The process won't advance, the device is somewhat functional.. I can pull down the menu from the top, I can infact authenticate to wireless, I can fully access settings, I made a MAYDAY call... But I cannot get to a home screen. In theory - I believe this to be a "soft brick" as it doesn't do anything.. Though the operating system, is running.
I was toying around in ADB trying to get it to push the 3.2.8 bin image to /storage/emulated/0/, but it wasn't cooperating. After doing some research, I came to the conclusion that the stock USB cable won't work, and I need to order a Fastboot cable? Any truth to this?
I'm just looking for some direction here if anyone has any advice. Amazon said they won't replace it - so I'm kinda stuck at this point.
Any help is much appreciated!
http://forum.xda-developers.com/showpost.php?p=59186495&postcount=9
Hi - thank you for that link. Am I to take one of the Kindle setup bin's and rename it to an apk?
Just a little vague on the instructions.
NM - I'm following it now.. Didn't realize someone else had my problem. Hoping this works - will tune back once confirmed!
You saved my kindle - thank you!
Hi, I need your help PZ.
positivehxcgo said:
You saved my kindle - thank you!
Click to expand...
Click to collapse
I have same problem like you. so Follow OnyXis's thread but not solve the problem.
May i ask you a Q? how did you solve this problem? PZ. show me instruction....
thankyou!! have a nice day~
positivehxcgo said:
[Excerpt] ... I was toying around in ADB trying to get it to push the 3.2.8 bin image to /storage/emulated/0/, but it wasn't cooperating. After doing some research, I came to the conclusion that the stock USB cable won't work, and I need to order a Fastboot cable? Any truth to this?
Click to expand...
Click to collapse
For anyone who stumbles upon this post ...
Cables DO make a difference but a 'fastboot' cable is not necessarily the solution. HDX models do not respond to fastboot cables in the same way most other android devices do; they are effectively useless on this device for recovery purposes. However, a crappy cable can create all sorts of havoc, both with data transfer and charging. Whenever a tether isn't working as expected one of the first troubleshooting steps is to switch cables. Visually it is hard to tell the difference between a good/bad cable so you may have to go through a few. Fastboot cables are generally constructed to higher standards which may fool some HDX users into thinking that was the solution. More likely any high-quality USB cable would have done the trick.
I have solved this problem.
cjdfyd2 said:
I have same problem like you. so Follow OnyXis's thread but not solve the problem.
May i ask you a Q? how did you solve this problem? PZ. show me instruction....
thankyou!! have a nice day~
Click to expand...
Click to collapse
Follow Onyxis´s thread but not skip mark ´ and after rebooting you must skip wifi connect
And then u show start stable welcome display connect wifi. that´s all thankyou onyxis and who interest my problem have a nice day
Related
Unable to install MODULE, it says (please view the screen capture I posted in the thread)
Hi guys, I have a problem regarding my A13 android tablet device. It doesn’t matter if I will post the brand name of my tablet or whatever because what I only wanted to fix is this. When I follow every instruction written at this link, and following instructions 1-7, after reaching step 5 execute run.bat.
It displays the following image I screen captured. (And my tablet doesn’t reboot, it’s the sign that the computer can’t access my tablet.
View attachment 2445500
Obviously, my tablet is connected to the computer via USB cable after running the run.bat as administrator.
But what is the problem why it is happening to me. What can I do for this?
(Additional information: I already installed and followed this instruction on this same device with no error at all. But why does it happened to me even I installed this with success before. I don’t know and I know that I don’t change any system file on my tablet before, and I don’t know because, I have no idea why it happened? I didn’t change any file or modify file neither on my tablet nor from my PC.)
I hope there is an expert who can answer my question and give to me a solution. Thank you in advance if there is.
nooffensesite said:
Unable to install MODULE, it says (please view the screen capture I posted in the thread)
Hi guys, I have a problem regarding my A13 android tablet device. It doesn’t matter if I will post the brand name of my tablet or whatever because what I only wanted to fix is this. When I follow every instruction written at this link, and following instructions 1-7, after reaching step 5 execute run.bat.
It displays the following image I screen captured. (And my tablet doesn’t reboot, it’s the sign that the computer can’t access my tablet.
View attachment 2445500
Obviously, my tablet is connected to the computer via USB cable after running the run.bat as administrator.
But what is the problem why it is happening to me. What can I do for this?
(Additional information: I already installed and followed this instruction on this same device with no error at all. But why does it happened to me even I installed this with success before. I don’t know and I know that I don’t change any system file on my tablet before, and I don’t know because, I have no idea why it happened? I didn’t change any file or modify file neither on my tablet nor from my PC.)
I hope there is an expert who can answer my question and give to me a solution. Thank you in advance if there is.
Click to expand...
Click to collapse
You need to install ADB. I'll report the post to the moderators to get this post in the right section.
I will continue searching for that
thewadegeek said:
You need to install ADB. I'll report the post to the moderators to get this post in the right section.
Click to expand...
Click to collapse
Alright then thanks for the clue, it’s almost 3 days now since I nonstop looking for solution for this problem. I know that it’s a harsh to think that even a simple problem like was I don’t know how to search and fix. I hope you understand that I am almost losing my hope to solve this problem. At least when because I have written and shared my question on this forum. At least I found new idea again.
I never expect that the answer is only to install ADB.
That is my next goal now, to search how to enable ADB on my PC. I know that this problem that I need to fix was only from my PC, because the USB debugging mode on my tablet setting is already activated. And I checked that a dozen of times already.
And if you found something about my post was not in a right section. Then it’s a thankful for me if you can help me with that, because this is just the first day of my life that I started using this site, except for reading a thread as a guest.
It didn't work
I already installed adb using this tutorial on the link <--- (I’m sorry I can't provide the link outside of this site because, I am a new user yet.) But still, because my tablet problem is the touch screen that’s why I am trying to install the module to fix my device touch screen. But the most important part was that from what I need is to touch/tap on a notification area on tablet to activate the “usb mass storage” button.
My PC can’t detect my tablet because I didn’t tap the “usb mass storage” button yet.
And I can’t tap it because that’s it, I need to install the module first to fix the Touchscreen to allow me activate the button. Oh God, this is so terrifying event.
:crying: :crying: :crying:
Did you try booting into recovery?
YES,
thewadegeek said:
Did you try booting into recovery?
Click to expand...
Click to collapse
Yeah, my tablet can boot to recovery mode. Everything is okay from my tablet. The only problem was the touch screen and the unable me to install module by running the run.bat file.
The only way that I can boot to recovery is by using a USB laptop mouse. And entering settings>Backup & reset>Recovery Mode.
Tonight is the 4th day of my problem. And still I’m stuck up from Touch Screen Problem.
Is there any other way aside from using that module just to fix my touch screen?
I am not good using Linux, so if incase the other way to fix this was by using linux operating system. Then maybe, I should stick to using this module.
Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
NecroGi said:
Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
Click to expand...
Click to collapse
adb is not designed to be usable in bootloader mode. You need fastboot for that. If you have the fastboot.exe program in the same folder as your adb stuff, try this:
fastboot devices
If it reads, then all you need to do is fastboot flash the various .img files back to the tablet. There are tool kits that do this for you, but I prefer doing it manually as there are less chances of things messing up and if they do, you're more likely to know at what step which could be useful for further troubleshooting if need be. It is important to download the correct img files due to differences between the generations and wifi / data enabled ones. There is a flash-all script that you can find in the download of the factory images, which might make it easier, but you can just manually flash the separate files as sometimes you don't need to bother with them all (like the bootloader) though if the script works, then it'll be fine and might make it easier if you are not familiar with the commands.
If you don't have fastboot at all, just grab it from here: http://forum.xda-developers.com/showthread.php?t=2317790
Nexus img files: https://developers.google.com/android/nexus/images
Hit me up on Hangouts if you need more direction.
NecroGi said:
Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
Click to expand...
Click to collapse
You won't get adb in bootloader mode.
You have to use the fastboot command.
Please tell the OS on your computer.
Use the tool in my signature as an environment.
Download 7zip, and install that.
Then go here and download the proper image for your device.
It would either be "Factory Images "nakasi" for Nexus 7 (Wi-Fi)" or "Factory Images "nakasig" for Nexus 7 (Mobile)".
Grab the 4.4.2 version.
Extract the downloaded file with 7zip into the "Work" folder in the tool form my signature.
Then extract that "nakasig-kot49h-factory-83d93b5f.tar" file with 7zip.
Then go into the folder that came out of that, and extract the "image-nakasig-kot49h.zip" into the Work folder.
And enter the following commands while in bootloader.
Code:
fastboot oem unlock
fastboot erase userdata
fastboot erase system
fastboot erase recovery
fastboot erase cache
cd nakasig-kot49h
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
Make SURE you grab the correct image for your device. Wifi or Mobile.
I also assume that you know the .img files should be in the Work folder before you type thse commands into my tool.
Hey guys, first of all thank you for the speedy replies and steps I should follow.
Right now I'm using OSX but for the tablet I'm using a virtual Win7 machine to try and get this damn tablet to be recognized by the computer. The process is being delayed a little bit because my micro USB cords are being temperamental, meaning that the tablet has no juice, and when I mess with it (using the power + volume buttons to boot to bootloader/recover) the cord comes unplugged. I know automatically you guys are going to pinpoint this as the source of the issue (mainly because I would too), but it works fine if just laid flat and stays connected. It just has zero charge so when it disconnects/reconnects I literally have to power it back up, just need to wait for it to have some charge before I tinker with it more.
I will post updates after it charges.
Although I already thanked you guys, thanks again for speedy reply. It's much appreciated.
NecroGi said:
Hey guys, first of all thank you for the speedy replies and steps I should follow.
Right now I'm using OSX but for the tablet I'm using a virtual Win7 machine to try and get this damn tablet to be recognized by the computer. The process is being delayed a little bit because my micro USB cords are being temperamental, meaning that the tablet has no juice, and when I mess with it (using the power + volume buttons to boot to bootloader/recover) the cord comes unplugged. I know automatically you guys are going to pinpoint this as the source of the issue (mainly because I would too), but it works fine if just laid flat and stays connected. It just has zero charge so when it disconnects/reconnects I literally have to power it back up, just need to wait for it to have some charge before I tinker with it more.
I will post updates after it charges.
Although I already thanked you guys, thanks again for speedy reply. It's much appreciated.
Click to expand...
Click to collapse
I suggest to STOP!!!
If you are trying to restore the device and the cable disconnects in the middle of it, it might not be recoverable. That would be one of the few ways to really damage the tablet as they are pretty difficult to hard brick. Don't half ass it with stuff like this. A good cable is not THAT much and will certainly be cheaper than a new tablet or getting it to a point where you might have to send it somewhere for service.
I'm not familiar with Macs, but if you are more so, then this might be better than using a Virtual set up:
https://code.google.com/p/adb-fastboot-install/
es0tericcha0s said:
I suggest to STOP!!!
If you are trying to restore the device and the cable disconnects in the middle of it, it might not be recoverable. That would be one of the few ways to really damage the tablet as they are pretty difficult to hard brick. Don't half ass it with stuff like this. A good cable is not THAT much and will certainly be cheaper than a new tablet or getting it to a point where you might have to send it somewhere for service.
I'm not familiar with Macs, but if you are more so, then this might be better than using a Virtual set up:
Click to expand...
Click to collapse
It's actually working fine now (in the sense that the computer can now read it). The Virtual Machine also works just as good, but for some reason the toolkit I'm using won't properly return the tablet to the stock image using the SkipSoft Android ToolKit, so I'm going to have to try and find another way.
Thanks for your guys' help.
I used the almighty wipe feature of safesortrap and now i have no zips on the device, no way to put them on it, i tried adb push, sideload,etc. i do have a fastboot cable, although when it is plugged in to the fastboot cable, it wont turn on at all. my computer recognizes it as an unknown
device in safestrap, troubleshooting doesnt work. I have the OS I need, I just need a way of getting it onto the device. Any help is greatly appreciated! c: NOTE: 3rd gen kindle fire hdx 7. Also, is it possible when it is unbricked to unlock the bootloader in this situation?
Depends on the Fire OS version you had installed. Only versions below x.3.2.4 are unlockable (i.e. 3.2.3.2 or lower). Note that you can NOT downgrade below 3.2.8 once 3.2.8 or higher have been installed! Attempt would brick the device, thanks to rollback protection by amazon.
Which Safestrap version do you have installed, and what did you wipe?
Cl4ncy said:
Depends on the Fire OS version you had installed. Only versions below x.3.2.4 are unlockable (i.e. 3.2.3.2 or lower). Note that you can NOT downgrade below 3.2.8 once 3.2.8 or higher have been installed! Attempt would brick the device, thanks to rollback protection by amazon.
Which Safestrap version do you have installed, and what did you wipe?
Click to expand...
Click to collapse
I have Safestrap v4.01 and i wiped dalvik,data,cache, and system(im an idiot, i know lol). I had 4.5.2 installed, so no BL unlock.
InfiniteSpace said:
I have Safestrap v4.01 and i wiped dalvik,data,cache, and system(im an idiot, i know lol). I had 4.5.2 installed, so no BL unlock.
Click to expand...
Click to collapse
Don't be so quick, Safestrap v4 has a built-in System-wipe-protection, could've helped here.
Stay away from amazon's stock recovery! Using it with Safestrap installed will brick the device!
Try to get adb access, I think there's a thread somewhere here where a user was able to get access and to revive the HDX. May be the PDA drivers help regarding that. If not, try the original amazon drivers again.
Also try different USB cables, the HDX is surprisingly picky regarding cables. Fastboot cables won't work anyway btw.
You mean the PDANET drivers?
Nvm found it, trying this
I have adb access, i think it was the cable and im a noob, thank you for your time!
Kindle Fire THOR Black Screen wont connect to ADB
Okay so long long story short- my daughter has a kindle fire HD 7 inch version 3rd generation tablet. I did root it a while back and thought I had disabled the updates. However she accidentally so how allowed the updates and duringt the process it went black screen and wont boot or do anything at all. I have read countless forums and tried almost all the un-bricking tools out there as well as the commands in ADB. Currently what I have concluded is that the tools and typical un-bricking methods wont work since the tablet will not power on it wont connect to the computer in ADB mode and I have no idea if its in USB debugging mode at this time.
It will sorta power on (screen still blank- by holding the power button for 20 secs) and the computer "senses" it but at that point it will not be recognized by the PC, and give the error that the "USB device has malfunctioned". I have tried about everything out there- can you guys help me out to get the power back on at least where I can get the ADB to recognize the device? Thanks in advance.
Oh- I did purchase a fastboot cable as well but that did not help matters at all.....
Amazon: "3ft Fastboot Factory Cable For Motorola Unbrick Droid Xoom Fire by Atomic Market"
Athruz
Athruz said:
Okay so long long story short- my daughter has a kindle fire HD 7 inch version 3rd generation tablet. I did root it a while back and thought I had disabled the updates. However she accidentally so how allowed the updates and duringt the process it went black screen and wont boot or do anything at all. I have read countless forums and tried almost all the un-bricking tools out there as well as the commands in ADB. Currently what I have concluded is that the tools and typical un-bricking methods wont work since the tablet will not power on it wont connect to the computer in ADB mode and I have no idea if its in USB debugging mode at this time.
It will sorta power on (screen still blank- by holding the power button for 20 secs) and the computer "senses" it but at that point it will not be recognized by the PC, and give the error that the "USB device has malfunctioned". I have tried about everything out there- can you guys help me out to get the power back on at least where I can get the ADB to recognize the device? Thanks in advance.
Oh- I did purchase a fastboot cable as well but that did not help matters at all.....
Amazon: "3ft Fastboot Factory Cable For Motorola Unbrick Droid Xoom Fire by Atomic Market"
Athruz
Click to expand...
Click to collapse
You mentioned "THOR" in the title later expanding that to "HD 7". They are two distinctly different devices. For the purpose of this post I'll assume you are referincing a 3rd gen HDX 7 device (Thor). Unfortunately nothing can be done short of board replacement which is not cost effective given the current price point of pre-owned devices in good condition. As you probably read fastboot/factory cables are useless on HDX models which is the only way to communicate with an otherwise comatose device. Sorry for your daughter's loss. Poke around action sites like eBay; I have seen supposedly new 16GB HDX 7's going for $50-60 USD. If you daughter is younger a 5th gen 7" fire is a good alternative as it can be rooted and with several quality custom ROMs available you FireOS is not to you/her liking.
Thanks
Davey126 said:
You mentioned "THOR" in the title later expanding that to "HD 7". They are two distinctly different devices. For the purpose of this post I'll assume you are referincing a 3rd gen HDX 7 device (Thor). Unfortunately nothing can be done short of board replacement which is not cost effective given the current price point of pre-owned devices in good condition. As you probably read fastboot/factory cables are useless on HDX models which is the only way to communicate with an otherwise comatose device. Sorry for your daughter's loss. Poke around action sites like eBay; I have seen supposedly new 16GB HDX 7's going for $50-60 USD. If you daughter is younger a 5th gen 7" fire is a good alternative as it can be rooted and with several quality custom ROMs available you FireOS is not to you/her liking.
Click to expand...
Click to collapse
Thank you very much for the info - I was suspecting that unfortunately.
Question
Apologies, to hasty in getting a question onto the forums
I hope this is useful information. It took me a bit to figure it out due to a lot of conflicting information, since the procedure has changed, perhaps several times, since the first version of Android. Also, I'll probably forget myself.
Please note that I've performed these steps on Linux (Specifically Arch Linux). Others have pointed out that if you have issues executing step 7 from Windows, you may need to follow this post.
1. Install Android Studio, or otherwise obtain the latest versions of the adb and fastboot programs. I think Windows users also need to install a USB driver, but I run Linux, so I am not sure about that procedure.
2. Gain access to the developer options on the tablet. Go to the settings, and find the "about tablet" section. Scroll down to the "Software version" section and tap on that several times until it says that you are now a developer. Feel special.
3. Go to the new "Developer options" setting. Select "OEM unlocking." Also, I selected "USB debugging" as a straightforward way to reboot into the boot loader.
4. Connect to the computer on which you've installed adb and fastboot.
5. Type 'adb devices' to see your device listed. The tablet will ask you if you're sure you want to allow the computer access to it. Answer in the affirmative, and save that option.
6. Type 'adb reboot-bootloader' to do just that.
7. After you see the innards of your 'droid, type 'fastboot flashing unlock' . On Linux, you may need root permissions to do this. The tablet will ask you to confirm (select with up/down volume, and accept with the power button), and will then erase all of your data! I didn't worry about this as I'm all on Google services, and so they can be restored easily enough.
Huhu
and where is that for? What can I do after the bootloader is unlocked? Is there any alternative bootloader that I can use then?
Huhu
and where is that for? What can I do after the bootloader is unlocked? Is there any alternative bootloader that I can use then?
Click to expand...
Click to collapse
you are then able to flash another (custom) recovery, which would let you install unsigned zip-files, e.g. in order to get root.
Unfortunately, there is no recovery port by now.
I don't know if one could use the source code on Lenovo's website to port one, if not we would probably need an image dump directly from the device (if I'm not mistaken you need root to dump the recovery image).
I really would like to have root, but it still seems far away unless there's an experienced developer somewhere who owns the device.
I've already thought of starting a bounty thread...maybe enough people are willing to contribute so that developers might feel attracted.
Hello,
Do you think it would be possible to install Windows 10 on our android yoga book?
Thanks,
I faced with one question , when I typed the 'fastboot flashing unlock ', there was nothing occurred except the innards of driod :crying,and I also selected the oem unlocking
(All right, I solved it )
AndyVerne said:
I faced with one question , when I typed the 'fastboot flashing unlock ', there was nothing occurred except the innards of driod :crying,and I also selected the oem unlocking
(All right, I solved it )
Click to expand...
Click to collapse
can you tell me how to deal with it? I met the same problem.
Vsplorer said:
can you tell me how to deal with it? I met the same problem.
Click to expand...
Click to collapse
I used one exe for adb and fastboot which is written by others, and every thing went perfectly.
AndyVerne said:
I used one exe for adb and fastboot which is written by others, and every thing went perfectly.
Click to expand...
Click to collapse
can you tell me where to download the exe？ thanks a lot！
Vsplorer said:
can you tell me where to download the exe？ thanks a lot！
Click to expand...
Click to collapse
Here is the link of the exe, hope it will be helpful
https://forum.xda-developers.com/showthread.php?t=2588979
AndyVerne said:
Here is the link of the exe, hope it will be helpful
https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
thanks！
Missing Something?
I tried to follow the instructions above, but I might be missing something. After typing in 'adb reboot-bootloader' the Yoga Book reboots into a screen that says 'FASTBOOT MODE.' But when I type 'fastboot flashing unlock' it just says '< waiting for device >' and nothing ends up happening. What am I doing wrong?
jasonccheng said:
I tried to follow the instructions above, but I might be missing something. After typing in 'adb reboot-bootloader' the Yoga Book reboots into a screen that says 'FASTBOOT MODE.' But when I type 'fastboot flashing unlock' it just says '< waiting for device >' and nothing ends up happening. What am I doing wrong?
Click to expand...
Click to collapse
See this post:
https://forum.xda-developers.com/yoga-book/help/missing-usb-driver-cherry-trail-tablet-t3537008
Same here with Linux... The adb devices command shows the device but the flash command ends in 'waiting for device' and thats it. Damn
I relocked the bootloader, sinct then I got following message at the boot screen: bootloader error 01, please contact support.
After that the device is booting android properly. Anybody else experienced this and know how to get rid of the message?
Thx.
carepack said:
I relocked the bootloader, sinct then I got following message at the boot screen: bootloader error 01, please contact support.
After that the device is booting android properly. Anybody else experienced this and know how to get rid of the message?
Thx.
Click to expand...
Click to collapse
It's the price you pay for unlocking the bootloader. Affects many lower end devices, presumably using Intel chips. There is a solution for several devices - check around XDA - but I have not been able to get it to work with the YB.
For what it's worth, I would suggest those tempted to unlock the device and root it to check that you will be able to do what you want to do. Even rooted, I have found it impossible to get rid of the junk apps, so the whole exercise for me has been a waste of time. I'm waiting now to see if Lenovo will release the stock firmware. Until then, the YB is back in its box and I am a bit older and a bit wiser. Lenovo is junk.
carepack said:
I relocked the bootloader, sinct then I got following message at the boot screen: bootloader error 01, please contact support.
After that the device is booting android properly. Anybody else experienced this and know how to get rid of the message?
Thx.
Click to expand...
Click to collapse
i believe, this is due to android's security feature 'verified boot'. it warns that the system was somehow altered and can't be trusted - in other words that it is not an oem stock rom any more.
you might be able to get rid of it by flashing a complete stock rom, but i'm not sure.
zamzenos said:
It's the price you pay for unlocking the bootloader. Affects many lower end devices, presumably using Intel chips. There is a solution for several devices - check around XDA - but I have not been able to get it to work with the YB.
For what it's worth, I would suggest those tempted to unlock the device and root it to check that you will be able to do what you want to do. Even rooted, I have found it impossible to get rid of the junk apps, so the whole exercise for me has been a waste of time. I'm waiting now to see if Lenovo will release the stock firmware. Until then, the YB is back in its box and I am a bit older and a bit wiser. Lenovo is junk.
Click to expand...
Click to collapse
firstly, it has nothing to do with intel or lenovo or low end devices, because secure boot or verified boot is part of android - it is nothing more than a security feature to show whether system integrity (as provided by the vendor) is still valid.
secondly, why is Lenovo junk just because you are not able to get things done? i don't get it. i've already told you that it is possible to get rid of system apps, just use the right tools... e.g. 'Sytstem App Entferner' which definitely works. also i helped you to get your twrp backup working and i was also able to use the newest magisk root (v10.2) immediately, which you said was not possible. so i guess you shouldn't blame others for your shortcomings. the yb might surely have it flaws, bur no more or less than devices of other manufacturers.
danjac said:
i believe, this is due to android's security feature 'verified boot'. it warns that the system was somehow altered and can't be trusted - in other words that it is not an oem stock rom any more.
you might be able to get rid of it by flashing a complete stock rom, but i'm not sure.
firstly, it has nothing to do with intel or lenovo or low end devices, because secure boot or verified boot is part of android - it is nothing more than a security feature to show whether system integrity (as provided by the vendor) is still valid.
secondly, why is Lenovo junk just because you are not able to get things done? i don't get it. i've already told you that it is possible to get rid of system apps, just use the right tools... e.g. 'Sytstem App Entferner' which definitely works. also i helped you to get your twrp backup working and i was also able to use the newest magisk root (v10.2) immediately, which you said was not possible. so i guess you shouldn't blame others for your shortcomings. the yb might surely have it flaws, bur no more or less than devices of other manufacturers.
Click to expand...
Click to collapse
Let me start at the top:
1. My comments on Lenovo are no reflection on the useful tools you have provided us here, for which I have thanked you more than once. So no need to be defensive on that score.
2. If the unlock warning had its source in Android itself, we could expect the warning to bear its logo. I assume it bears the Intel logo because Intel is the author of it. In itself, this is of no importance. What is profoundly irritating is the fact that the security warning is followed by a completely unjustfied 5 second suspension. This is a penalty. Perhaps many do not mind this interference with their use of their devices, but I do. I'm not used to that kind of treatment and I don't take kindly to it.
3. My opinion of Lenovo has always been low, especially since their attempts some years ago to spike their devices with spyware. I regard Lenovo as an exploitative bottom feeder, supplying workaday gear and screwing their customers every way they can for an extra buck or two. I offered the YB to several of my friends. All turned their noses up at the mention of the manufacturer. Don't blame them.
4. If you do want to be of further assistance here, perhaps you can use your obvious technical skills and knowhow to work out how we can replace the Intel penalty with something more benign. I have tried, but can't find where the Intel warning is hidden.
I have downloaded and extracted the apk of the system app remover you mentioned. But until I can get rid of the Intel warning I won't bother to re-root the YB and test if it will clear the junk.
#carepack: at the moment, you must buy the stock firmware (and won't it be expensive!). All part of lenny's screw.
thx to all for youre response. my hope is that with next update the problem will solve by itself. We'll see. I were doin this ooi and was aware of things like that. So no drama for me.
@zamzenos
Buying the stock firmware? Could you provide more info about this?
carepack said:
thx to all for youre response. my hope is that with next update the problem will solve by itself. We'll see. I were doin this ooi and was aware of things like that. So no drama for me.
@zamzenos
Buying the stock firmware? Could you provide more info about this?
Click to expand...
Click to collapse
Yes, that could well do it. But will there be an update? There's a new 12" YB on offer. Could be our 10" version is history already. But we could then hope that they will release the stock.
Re buying the stock: https://forums.lenovo.com/t5/Android-Yoga-Series-Tablets/Lenovo-Yoga-Book-Firmware/td-p/3511903
zamzenos said:
Yes, that could well do it. But will there be an update? There's a new 12" YB on offer. Could be our 10" version is history already. But we could then hope that they will release the stock.
Re buying the stock: https://forums.lenovo.com/t5/Android-Yoga-Series-Tablets/Lenovo-Yoga-Book-Firmware/td-p/3511903
Click to expand...
Click to collapse
According to this:
http://www.androidpolice.com/2016/1...views-cite-software-issues-incredible-design/
We'll receive the nougat Update.
Greetings
Hello everyone,
I've been tinkering with my kindle attempting to flash TWRP so I could flash other ROMs on my Kindle Fire HDX 7 (3rd generation) but I have seemed to soft brick the device after using unlock.bat from https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982/post70881555#post70881555
The unlock.bat was supposed to unlock my bootloader, but now the device won't power on. If I plug it into the windows a bunch of partitions appear and windows prompts me if I want to format the various drives. If I plug my kindle into Linux, the 7 (i think) partitions show folders various different system functions.
Someone wrote in a separate forum that it's possible to restore kindle if I using something called eMMC Raw tool, but didn't really give any clear instructions.
If anyone could help me recover my device, that would be greatly appreciated. Thank you.
For some reason I can't upload a picture of the various files in the partition.
Side note: could I theoretically put CM 12 or anything else on one of the partitions instead of the stock ROM?
Praxxer1 said:
Hello everyone,
I've been tinkering with my kindle attempting to flash TWRP so I could flash other ROMs on my Kindle Fire HDX 7 (3rd generation) but I have seemed to soft brick the device after using unlock.bat from https://forum.xda-developers.com/ki...r-firmware-t3463982/post70881555#post70881555
The unlock.bat was supposed to unlock my bootloader, but now the device won't power on. If I plug it into the windows a bunch of partitions appear and windows prompts me if I want to format the various drives. If I plug my kindle into Linux, the 7 (i think) partitions show folders various different system functions.
Someone wrote in a separate forum that it's possible to restore kindle if I using something called eMMC Raw tool, but didn't really give any clear instructions.
If anyone could help me recover my device, that would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
Unlock.bat did not "soft brick" your device as the actions it performs are totally benign. More likely you got sloppy and flashed an incompatible aboot (via dd) or erased aboot and don't know how to recover. Me thinks it is the latter. Keep reading; you'll eventually stumble on posts that describe corrective actions. I will edit this post with a link as time permits.
You do not need "eMMC Raw Tool" whatever that is.
edit: https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post75284993
Davey126 said:
Unlock.bat did not "soft brick" your device as the actions it performs are totally benign. More likely you got sloppy and flashed an incompatible aboot (via dd) or erased aboot and don't know how to recover. Me thinks it is the latter. Keep reading; you'll eventually stumble on posts that describe corrective actions. I will edit this post with a link as time permits.
You do not need "eMMC Raw Tool" whatever that is.
edit: https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post75284993
Click to expand...
Click to collapse
Ah. I wish I had seen that thread before I started the process! You may be right about the compatible boot. I couldn't find the original aboot_vuln.mbn file mentioned in the thread I was following, but managed to find aboot.img file and flashed that hoping it was the same. I could have sworn though, that the device stopped working the second after I clicked the unlock.bat file (executed outside the fastboot screen), but could be wrong.
Only problem about the thread you linked, device isn't responding to any ADB or fastboot commands, but still shows that my PC recognizes the device as a fire device.
Thank you for your time, I'll keep reading through the thread you linked.
Praxxer1 said:
Only problem about the thread you linked, device isn't responding to any ADB or fastboot commands, but still shows that my PC recognizes the device as a fire device.
Click to expand...
Click to collapse
Likely a Windows driver issue. Suggest installing Motorola Device Manager here which includes composite USB drivers that work reliably with HDX devices. Need need to run MDM; just install it. After connecting the device you will need update the driver via Windows Device Manager. Bit of hit and miss with a non-functioning device. Cables and USB ports also play a huge role, especially with fussy bootloader/fastboot communications. Avoid external hubs, USB3 ports and add-on expansion cards. Change cables, ports, etc. Good luck.
Davey126 said:
Likely a Windows driver issue. Suggest installing Motorola Device Manager here which includes composite USB drivers that work reliably with HDX devices. Need need to run MDM; just install it. After connecting the device you will need update the driver via Windows Device Manager. Bit of hit and miss with a non-functioning device. Cables and USB ports also play a huge role, especially with fussy bootloader/fastboot communications. Avoid external hubs, USB3 ports and add-on expansion cards. Change cables, ports, etc. Good luck.
Click to expand...
Click to collapse
Thanks Davey, I'll definitely give it a try. Just as a bit more information on my situation, the device manager on windows does read Fire Device "ADB composite driver". I also have it connected to the PC using a Fastboot Cable. I will give all of this a try when I get home from work today.
If I am able to communicate with the device after installing the MDM drivers, should I attempt to restore the device? Or try to unlock and flash the stock ROM?
Praxxer1 said:
Thanks Davey, I'll definitely give it a try. Just as a bit more information on my situation, the device manager on windows does read Fire Device "ADB composite driver". I also have it connected to the PC using a Fastboot Cable. I will give all of this a try when I get home from work today.
If I am able to communicate with the device after installing the MDM drivers, should I attempt to restore the device? Or try to unlock and flash the stock ROM?
Click to expand...
Click to collapse
- dump the fastboot cable (all but useless on a HDX); this isn't a generic Android device
- ADB composite drivers come in many flavors; HDX bootloader only likes a few of them
- if/when you reestablish communication first step is to restore aboot and install TWRP; unlocking and ROM installation come later
- do not attempt to reinstall stock; frustration and heartache consume those who do
- again, this is not a run-of-the-mill Android gizmo; many of the tricks you learned in kindergarden do not apply to Amazon tablets
Davey126 said:
- dump the fastboot cable (all but useless on a HDX); this isn't a generic Android device
- ADB composite drivers come in many flavors; HDX bootloader only likes a few of them
- if/when you reestablish communication first step is to restore aboot and install TWRP; unlocking and ROM installation come later
- do not attempt to reinstall stock; frustration and heartache consume those who do
- again, this is not a run-of-the-mill Android gizmo; many of the tricks you learned in kindergarden do not apply to Amazon tablets
Click to expand...
Click to collapse
Lol I feel like I'm in kindergarten tinkering with this HDX. How do I restore aboot? clearly the image I flashed with was not the correct bootloader. Should I attempt to extract aboot from the stock ROM? Or would you be able to share you tool set/point me to a working link for aboot, TWRP, and ROMs (I've looked at 4 threads so far without working links)?
UPDATE: I managed to install the ADB MOT Composite driver, but still no response to simple ADB and Fastboot commands
Thanks again
Praxxer1 said:
Lol I feel like I'm in kindergarten tinkering with this HDX. How do I restore aboot? clearly the image I flashed with was not the correct bootloader. Should I attempt to extract aboot from the stock ROM? Or would you be able to share you tool set/point me to a working link for aboot, TWRP, and ROMs (I've looked at 4 threads so far without working links)?
UPDATE: I managed to install the ADB MOT Composite driver, but still no response to simple ADB and Fastboot commands
Thanks again
Click to expand...
Click to collapse
Not uncommon. Unfortunately, there is no 'fix script' moving forward as each situation is unique. If aboot is too damaged to support basic communication it's pretty much game over for the average laymen. You will need to comb the threads for information nuggets that may apply to your situation. Or cut your losses and move on. I am not big on trying to unbrick these pups unless one well versed in low level trouble shooting. Lousy ROI; has to be a labor of love including copious time researching, trying and (likely) failing. Good luck.
@draxie - for awareness; read back a few posts for context.
1-Click is your friend
Davey126 said:
Not uncommon. Unfortunately, there is no 'fix script' moving forward as each situation is unique. If aboot is too damaged to support basic communication it's pretty much game over for the average laymen. You will need to comb the threads for information nuggets that may apply to your situation. Or cut your losses and move on. I am not big on trying to unbrick these pups unless one well versed in low level trouble shooting. Lousy ROI; has to be a labor of love including copious time researching, trying and (likely) failing. Good luck.
@draxie - for awareness; read back a few posts for context.
Click to expand...
Click to collapse
Right... the symptoms described are the normal state of affairs
after 'fastboot erase aboot' and 'unlock.bat' does no such thing.
The post linked above and/or my original "Bulk mode" post both
have the necessary instructions to recover. Alternatively, 1-Click
can handle this, assuming access to either MacOS or Linux (for
the time being).