Right I have UK Nexus 4, running 4.2.2, Developer Mode is enabled, but USB Debugging is not, it is not rooted.
How can I enable USB Debugging mode, without wiping everything on the phone as I need to use a program called MoboRobo before I wipe the phone (I need to backup messages, bookmarks and contacts)
I can't see anything on the screen at all, so if you are able to help and tell me I need to boot into Recovery mode, then pick an option I need to know how many times to press up or down, this is purely as I can't see a single thing on the screen at all.
I've been trying to follow this: http://forum.xda-developers.com/showthread.php?t=2177440
But I've no idea if that's correct for what I need to do (purely enable USB Debugging mode without wiping what's already on the phone)
Sorry if this has been covered, I've tried to search but the only thing that came close was a Nexus 7 where the user could still see the whole screen.
Ok first, let me ask a few questions.
1. Is your bootloader unlocked?
2. Do you have a custom recovery installed? If so, which one?
3. Will you have access to a working Nexus 4 in the near future? A replacement, a friend's, a family member's, a repaired version of your current phone, etc?
Johmama said:
Ok first, let me ask a few questions.
1. Is your bootloader unlocked?
2. Do you have a custom recovery installed? If so, which one?
3. Will you have access to a working Nexus 4 in the near future? A replacement, a friend's, a family member's, a repaired version of your current phone, etc?
Click to expand...
Click to collapse
1] No
2] No
3] No
JuicedToday said:
1] No
2] No
3] No
Click to expand...
Click to collapse
Hmm, that's a tough one then. Do you have adb set up on your computer? If not, follow the instructions posted here.
Setting up ADB for our device:
Download the AndroidSDK onto your computer.
Note: Google changes their mind every other week as to if this will be distributed as a .zip or an .exe. If you get an .zip file, simply extract the contents to your C:\ drive. For an .exe install it like you would any other program, but set the path directly to the C:\ drive when the installer asks.
Or...you can use this page to download the "ADB for Dummies AIO App."
This will automatically install ADB for you to your C:\ directory. It's very very simple this way.
If your platform-tools folder doesn't have a fastboot.exe, place this fastboot.exe file in your C:\android-sdk-windows\platform-tools (or possibly simply called tools, if you set up ADB ages ago) folder.
Now you have ADB installed! Congratulations.
Click to expand...
Click to collapse
Now I would boot into bootloader (Turn off device, then press volume down and power at the same time until it vibrates). Now, press volume down twice, then power button. It should vibrate. That'll boot your phone into recovery. Now set up the drivers:
Get the drivers:
Uninstall any previously attempted drivers if they don't work and move to the next.
Option One:
Navigate to the "Device Manager" (Control Panel > Device Manager) in Windows and Select the android device. Open the properties and select the "Install Driver" option. Pick the driver with "Install from disk." Ignore any warnings about the driver not being signed properly.
PDAnet's drivers may work if the above options don't. Simply install PDAnet (after uninstalling any previous attempted driver installations) to get the drivers.
Click to expand...
Click to collapse
To verify your computer is seeing your phone and that you're in recovery, open a cmd window in the location of your platform-tools folder under the Android SDK location (fastest way is to shift+right-click a blank area in the folder in Windows Explorer, Open command window here). then type "adb devices", and it should pop up with a device number followed by "recovery". If you've gotten this far, there is still hope.
Now what you're going to do is use the "adb pull" command to pull the files from your phone onto your computer. I'll try to see if I can figure out the locations of the files you need. One question: What browser are you using (not yet sure if it makes a difference, but in case I find out it does)
By the way, after typing all of that I realized that if you're signed into your Google account, your contacts should be synced with your account in the cloud, you should be able to pull them down on a new phone if you sign back into your account on that new phone. Same with your bookmarks if you're using Chrome or the default AOSP browser. In any case, it won't sync SMS so I'll still try to find out where they're located.
Johmama said:
Hmm, that's a tough one then. Do you have adb set up on your computer? If not, follow the instructions posted here.
Now I would boot into bootloader (Turn off device, then press volume down and power at the same time until it vibrates). Now, press volume down twice, then power button. It should vibrate. That'll boot your phone into recovery. Now set up the drivers:
To verify your computer is seeing your phone and that you're in recovery, open a cmd window in the location of your platform-tools folder under the Android SDK location (fastest way is to shift+right-click a blank area in the folder in Windows Explorer, Open command window here). then type "adb devices", and it should pop up with a device number followed by "recovery". If you've gotten this far, there is still hope.
Now what you're going to do is use the "adb pull" command to pull the files from your phone onto your computer. I'll try to see if I can figure out the locations of the files you need. One question: What browser are you using (not yet sure if it makes a difference, but in case I find out it does)
By the way, after typing all of that I realized that if you're signed into your Google account, your contacts should be synced with your account in the cloud, you should be able to pull them down on a new phone if you sign back into your account on that new phone. Same with your bookmarks if you're using Chrome or the default AOSP browser. In any case, it won't sync SMS so I'll still try to find out where they're located.
Click to expand...
Click to collapse
Appreciate your efforts. I did as you instructed, and once I'd got to the "adb devices" I get nothing showing. As the picture shows.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I use firefox and chrome, and googlemail, but I've set them to not sync for personal reasons. All my contacts were saved directly to the phone. Messages I'm not too fussed about, but it would be nice to be able to view them, possibly back them up.
I've apparently unlocked the bootloader via the Nexus 4 Toolkit. I've no idea if that's worked or not though as I can't see the screen and I don't know how to test.
JuicedToday said:
Appreciate your efforts. I did as you instructed, and once I'd got to the "adb devices" I get nothing showing. As the picture shows.
I use firefox and chrome, and googlemail, but I've set them to not sync for personal reasons. All my contacts were saved directly to the phone. Messages I'm not too fussed about, but it would be nice to be able to view them, possibly back them up.
I've apparently unlocked the bootloader via the Nexus 4 Toolkit. I've no idea if that's worked or not though as I can't see the screen and I don't know how to test.
Click to expand...
Click to collapse
Ok, let's try eliminating possible reasons for your phone not showing up. Try re-entering recovery mode with the steps I provided above, in case it didn't work. I know this will sound stupid, but it's worked for me in the past: try switching which port on your computer that your USB cable is plugged in to. Try a different cable altogether if you have a spare. Oh, make sure you're using a USB 2.0 cable/plug. Sometimes MTP doesn't play nicely and you need to do weird things to get it working.
I've gathered a few database file locations that you might be interested in. I *think* they are correct anyway. I pulled them onto my computer but I can't try to view them right now, it'd have to be this weekend when I could get around to it, as I'm moving and I'd need to get settled first (Internet up and whatnot). I can still help you troubleshoot adb though.
SMS:
/data/data/com.android.providers.telephony/databases/mmssms.db
Click to expand...
Click to collapse
Contacts
/data/data/com.android.providers.contacts/databases/contacts2.db
Click to expand...
Click to collapse
Browser (I'm not exactly sure which browser)
/data/data/com.android.browser/databases/browser.db
Click to expand...
Click to collapse
Once adb is up and running, you'd use these commands to pull the .db file onto your computer:
Code:
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db
Code:
adb pull /data/data/com.android.providers.contacts/databases/contacts2.db
Code:
adb pull /data/data/com.android.browser/databases/browser.db
Those would pull the .db files onto your computer inside of the platform-tools folder. Again, I'm not sure about this, and can't confirm till later in the weekend, but I think to view those on your computer you can download SQLite from here. More importantly, I assume you can just put those .db files into the proper folders on your new phone to restore them. You'd have to figure out the correct folder location depending on your new device, as the manufacturer or carrier sometimes switches them.
Still getting nothing showing under adb devices even after trying several USB ports with a couple of various data cables.
Think it's a lost cause! Guess I'll just have to plump for the screen when I can afford it. Or swap the screen over on my insurance replacement enable USB Debugging then swap the screen back.
Other option would be to sell my replacement, buy the screen and still have a few quid left over.. Choices choices!
Thanks for taking the time and effort though, appreciate it.
Just thought I'd give this one last try. The data at this point isn't of any concern. I need to wipe everything that is on the phone, if that means the OS as well, then that's fine.
Is there a way I can remove my apps, data, messages etc via USB cable without USB Debugging being enabled?
Thank you for your time.:good:
cracked scereen, tried command, debugging alreadfy enabled. says devivce offline. is that because i have no SIM in it>?
Johmama said:
Ok first, let me ask a few questions.
1. Is your bootloader unlocked?
2. Do you have a custom recovery installed? If so, which one?
3. Will you have access to a working Nexus 4 in the near future? A replacement, a friend's, a family member's, a repaired version of your current phone, etc?
Click to expand...
Click to collapse
I have this same issue. Rooted with TWRP, which does NOT allow you to toggle through the recovery menu with the volume buttons.
After hours googling, I STILL have not found a way to wipe everything from my phone. I tried using the Android Device Manager to erase everything, but that didn't work.
Please, any help on what to do is so much appreciated. Thanks.
ji_mestone said:
I have this same issue. Rooted with TWRP, which does NOT allow you to toggle through the recovery menu with the volume buttons.
After hours googling, I STILL have not found a way to wipe everything from my phone. I tried using the Android Device Manager to erase everything, but that didn't work.
Please, any help on what to do is so much appreciated. Thanks.
Click to expand...
Click to collapse
Looks like you're hijacking this thread, but just because I'm currently fighting a similar situation...
you can download the recovery image for CWM at http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.3-mako.img
and then reboot to bootloader, run "fastboot flash recovery cwm.img" (using the file you just downloaded, i usually just drag and drop onto cmd line)
That will get you the recovery installed that will be useful because you don't have to touch the screen.
After that, It's as simple as selecting wipe all. if you can't see the screen, then you'll have to do these steps (after installing CWM):
hold Vol- and Power until it turns off, then keep holding Vol- and push power again.
down, down, power - boots into recovery
down, down, power - gets you to wipe/factory reset page
down x 7, power - confirms wiping all data
Related
You have undoubtedly seen lot of Rooting guides for the Mytouch 3G Slide, claiming to root the phone:
wiki.cyanogenmod.com/wiki/TMobile_myTouch_Slide:_Full_Update_Guide
http://forum.xda-developers.com/showthread.php?t=1108316 New way to downgrade from 2.2 to 2.1
http://forum.xda-developers.com/showthread.php?t=999121 Ultra Easy Rooter [dbzfanatic][xologist]
http://forum.xda-developers.com/showthread.php?t=1025336 How-To [Root][NewLinks] The myTouch 3GS if you updated to Offical 2.2.1 and lost root
SuperOneClick doesn't work. Nothing works, I've tried them all several times from several different angles. Therer is some sort of NAND lock on the phone, above and beyond typical. Anyways.
None of the aformentioned guides work, so won't waste your time like I did. They are also all written by people who can not communicate well with other human life forms, and they assume you have a CS and/or IS degree, and also assume you have all the software installed on your machine that they have on theirs, and have all the same settings on your phone that you "should" have on yours and they also assume you are doing some "obvious" steps in the middle of their steps that you should know how to do. They won't tell you that, but they do. So here is the REAL definitive step by step guide, with pics, on how to do it. BTW, you don't need a gold card. You don't need to mess with any consol crap. This should take 15-20 minutes max. What we're basically going to be doing is downgrading to 2.1-update1, then rooting, then putting on the Cyanogen Mod, then adding the google apps (which are not included in the cyanogen mod). I've put as many pics as I could and tried to do a step by step that ANYONE can follow.
I was using Windows 7 64-bit SP1 and I think these are the things that you need to have set up, you may not need them but I was trying so many of everything that I don't even know if they are all required, I'm sure I missed some things, but I will keep editing this guide as needed)
*Make sure you have at least 25MB of free space on your phone's internal memory.
*Make sure you've backed everything up you want to (text messages, bookmarks, programs, etc) But the google cloud should keep most your other stuff okay. (email etc) http://tinyurl.com/3b4qp6q
*Turn USB Debugging on your phone. (Settings, applications, development > USB Debugging - check)
*Turn phone to charge mode only when you plug in the USB cable
*PDAnet was running on the PC (This is required it will install the correct driver for step 1, though it's a tethering app and you won't need it for that) - http://junefabrics.com/android/download.php
1. Plug in phone and go to device manager from control panel on your computer.
You open the "Android USB Devices" and see what driver it says.
If it says something like "Mytouch Slide 3G"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
go to Update driver > Browse my computer for driver software > Let me pick
pick this one: "ADB Device Interface" , say okay, etc.
If it does say "ADB Drvice Interface" you're good. Exit out of that.
2. Download "T-Mobile_myTouch_3G_Slide_Software_Update_2.15.531.3.exe" from here http://www.htc.com/us/support/t-mobile-mytouch-3g-slide/downloads/ (157MB)
3. Go to your temp windows folder. IF you do Start > Search %TEMP% it should pop up. Keep on eye on this folder as you do the next step. (Maybe sort by date modified to help)
4. Double Click the "T-Mobile_myTouch_3G_Slide_Software_Update_2.15.531.3.exe" file and have it extract everything. At the first main screen, just wait there with it open and not installed.
You hopefully should have seen some folders be created in your temp file. There were 2 on mine, like so, check them both out:
When you see the one that looks like this:
and has a folder structure like this:
that's the folder you want to copy. So:
5. Highlight the folder with "ARUWizard.exe" and "rom.zip" in it. Mine had about 74 files in it. Copy it, and copy it to another part of your hard drive, and rename that awful folder, sheesh. (not needed)
6. You can close out of the Rom Update Utility.
7. In that NEW copied folder, delete "rom.zip"
8. Download the ~140 MB "ESPRIMG.zip" from here: http://www.4shared.com/file/OsmF_ZD7/ESPRIMG.html
9. Put it into the folder that we copied out, and rename it from ESPRIMG.zip TO rom.zip
10. Now, while you are in that folder, "ARUWizard.exe" check check, next, etc.
11. This will downgrade your phone from 2.2.1 to 2.1-update1
12. Tada! Good job. Now, go download the lastest Cyanogen firmware ROM here: http://download.cyanogenmod.com/?type=stable&device=espresso
13. Rename the "update-cm-7.X.X-Slide-signed.zip" to "update.zip"
14. While you are doing this, download the lastest Google Apps from here: http://wiki.cyanogenmod.com/wiki/Latest_Version#Google_Apps Mine was called "gapps-gb-20110613-signed.zip" and put that on your phone's memory card as well, no renaming needed.
15. Turn off your phone and take out the memory card and put it in your computer (or turn the phone back into a mountable drive) and copy over the update.zip onto the root director of your memory card.
16. Hold "down volume" and "power" which will boot you into a techy looking screen. Ignore any errors, the volume up and down navigates, so go into "Recovery" Mode.
17. Once in the Recovery, you will see a device with a triangle. Press "Volume Up" & the "Power" button.
18. Select the option to Wipe data/factory reset. Then select the option to Wipe cache partition.
19. See the option to "apply sdcard:update.zip" ? Do it, with power as confirm. This will put the Cyanogen mod on your phone!
20. Reboot system now. Now, you should boot into Cyanogen 2.3.x! However, you will notice you don't have any of the google apps.
21. So, Now, go into your programs on the phone, and you will see "Rom Manager" a eye with a tophat. Say "Install Rom from SD Card" and pick the "gapps-gb-20110613-signed.zip" You may have to fiddle with the plugging in USB/etc to get access to this, you don't have to buy the program, it will do it, but you have to have it set up so you can see the MicroSDcard, etc.
It will reboot your phone and you will now and install all the google apps. The most important one is MARKET, so you can download stuff. It will now go through all the TOS for each google program you said you want. The rest the wizard should navigate you through properly.
Holy hell this was a terribly troubleshooting process which probably took me 20 hours to figure out they were ALL wrong. Big thanks to "Da Maestro" who helped me on Cyanogenmod.
Enjoy!
wait wait wait... so will this method revert the hboot from 1. whatever to the older version and allow S-OFF?!
yeah, I don't even know what you're saying, I'm such the nube. I don't think this deals with the S-On/Off problem though. I saw some other posts that fixed that. This method does nothing to do with that, as far as I know
All I'm saying is I have Cyanogen 7 on my phone and this is how I did it from 2.2.1 stock.
txdeathray said:
wait wait wait... so will this method revert the hboot from 1. whatever to the older version and allow S-OFF?!
Click to expand...
Click to collapse
as far as i'm aware of, there's no S-OFF after you upgrade to 2.2.1, so i was thinking if you can check your hboot by powering off your phone and then turn it on by holding down volume down and power button. hboot version should be on the very top of your screen.
Bootloader error
I get 140 bootloader version error from the RUU. So far I have not been able to get any of the root mrthods to work with my slide.
Any ideas?
nikolag said:
I get 140 bootloader version error from the RUU. So far I have not been able to get any of the root mrthods to work with my slide.
Any ideas?
Click to expand...
Click to collapse
Well at least your not alone in that club. Getting the same error, even using a goldcard. I guess back to the drawing board for us at least.
yeah I had that error too,
http://forum.cyanogenmod.com/topic/28205-stuck-on-step-8-rooting/
EDIT: To fix it, make sure PDANet it installed and that will install the driver so you can change it from "t-mobile mytouch 3G" to "ADB Device..." It's step 1.
raziel420 said:
Well at least your not alone in that club. Getting the same error, even using a goldcard. I guess back to the drawing board for us at least.
Click to expand...
Click to collapse
That is one thing I didn't see, although upon checking it,s not there, and I do have the android SDK installed :/
If it helps any I'm on windows 7 ultimate x64 (since the problem seems driver related).
*edit 1* I keep seeing places where it says to check for the ADB interface driver, but nobody seems to know how to actually install said driver, or where it can be found at.
*edit 2* Turns out that PDAnet is what supplies the ADB driver, so as it happens that IS required (and here I thought that was a stupid tethering app)
*Edit 3* So just to make sure I downloaded the software on the posted links just to make sure some of the other versions I had were not incompatable, and still no joy. At this point I've spent a good 6 hours trying to root this phone and growing significantly more annoyed with it. If anyone has any feel free to contact me, I'd really like to get this working.
hey thanks, I'll edit the guide to say it's required.
Same here, went through all of the steps, still keep getting the 140 error.
edit* went all the way through the steps again very thoroughly, still getting the same error 140. Any Ideas?
It was such a complicated process, dealing with all the other guides some part of them may have worked that I missed. Maybe you do indeed need to make a gold card. It didn't work (I think) on one MicroSD card so I changed to another one.
So I guess make a gold card and give it a try. This is the guide I used to make a gold card:
http://wiki.cyanogenmod.com/wiki/Howto:_Create_a_Goldcard
Thanks for helping me get this guide correct.
One thing I did have to do is change USB ports and USB cables, as stupid as that is, I know, I know. The ones in my monitor worked but the front ones on my computer didn't work with the ROM update utility, but I think the error code I was getting was 170 or 171 USB disconnect error.
dgrwe2512 said:
Same here, went through all of the steps, still keep getting the 140 error.
edit* went all the way through the steps again very thoroughly, still getting the same error 140. Any Ideas?
Click to expand...
Click to collapse
What if you were to save that rom.zip file directly on the SD card, as the update.zip file first? Would that load 2.1? Because the installer wont.
I'm going to try it....
Nope, didn't work.
The gold card would be great if I had a second sd card, guess I will have to go buy one if I want to regain root.
the gold card worked for me just fine after getting my replacement phone on 2.2.1 all i did was back up everything on my sd card make and use the gold card get root and put every thing back on my sd card just fine.
dgrwe2512 said:
Same here, went through all of the steps, still keep getting the 140 error.
edit* went all the way through the steps again very thoroughly, still getting the same error 140. Any Ideas?
Click to expand...
Click to collapse
Do you have PDANet Installed?
Yes, its installed and running. Also, I made a gold card out of my SD card and tried again, and still got the same error. I am starting to hate T-Mobile!
katbastard said:
the gold card worked for me just fine after getting my replacement phone on 2.2.1 all i did was back up everything on my sd card make and use the gold card get root and put every thing back on my sd card just fine.
Click to expand...
Click to collapse
Do you have a link to the Gold Card method that worked for you? I keep getting a bootloader error with this method, about ready to give up.
dgrwe2512 said:
Do you have a link to the Gold Card method that worked for you? I keep getting a bootloader error with this method, about ready to give up.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1025336
did this as it reads, i am not a super geek, just know how to follow a list of things to do. i rooted one other time before this when it was really hard to do still. i thought this way was easier
I'm kinda confused why there is gold card discussion here. The method outlined in the first post specifically says that you don't need a gold card. Does this method not work and is that why you are trying gold card stuff?
dgrwe2512 said:
Yes, its installed and running. Also, I made a gold card out of my SD card and tried again, and still got the same error. I am starting to hate T-Mobile!
Click to expand...
Click to collapse
I don't think should have it running while you root. (I would assume that would just cause problems.) You just need to install it for the usb drivers and make sure it works.
Today I decided to unleash my kfhd7 and install CyanogenMod.
After installing the 2nd Bootloader and the recovery, I 'accidentally' removed all my data in the hurry (anyway, I forgot to place the ROM on the SDCard folder before :silly. I was quite confident while doing this, based on my experience with other Android devices, I thought it would be easy to mount the SDCard folder to the computer using TWRP... But that wasn't the case. And my device was not recognize by ADB while in Recovery Mod.
After some research on the forum I noticed that the poor people who had this problem before had to reflash the stock image through the recovery. I used another method, mostly by finding a way to reinstall the drivers. So I decided to share my experience. I know that is maybe a bit noob, but I would enjoyed to find this tutorial while I was despaired and stuck on recovery mod.
Last precision : I am using Windows 8 (and I'm French, so pardon my French ).
What you need
ADB version 1.0.29 or higher you can find the version by typing "adb version" at the command terminal
Kindle Fire HD ADB drivers already installed, I guess it was the case if you were able to install the recovery. Other wise try to install it, you should find the the file executable easily on this forum.
The .zip file of whatever you want to flash, dont forget the gapps if you want to flash Cyanogen
That's all, no need of factory cable.
1. Install drivers
The first step is to reinstall the driver, considering the device was recognised before the flash but not anymore.
Open the Device Manager (hint: by typing directly devmgmt.msc)
You should see "Amazon Kindle Fire HD" under the "Other Devices"
Right click "update driver"
"Browse my computer for driver software"
"Let me pick from a list of device drivers on my computer"
"All devices" then next
At the bottom of the window you can choose a custom driver. Go this path:
C:\Windows\System32\DriverStore\FileRepository\android_winusb.inf_amd64_048d6e54936abbc3
The last number might be different (or may not, in fact I have no idea).
And voilà!!
Now adb should work.
2. Use sideload
You can now push your .zip to the sdcard, but TWRP have a really useful and smart way to do it.
Go into the advanced option of ADB. The click ADB sideload and swipe to start.
Just type
Code:
adb sideload yourfile.zip
and it's done! Don't forget to repeat it for googleapps if you need it.
For some reasons I had an error from TWRP complaining that he didn't find any OS installed. It worked anyway for me.
Just wanted to say merci bc.
Running the stock rom (rooted + 2nd boot-loader) I´ve flashed the "1.4 GHz(try me first)" by Maromi.
I made a backup before of everything but unfortunately moved. the files to my PC.
With the result of stucking at the blue Kindle logo.
A fastboot cable has been ordered but didn´t arrived in time before the week-end.
Just like you I´ve looked around quite a long time, tried several options but then your thread was the only solution!
By your advice I´ve sideloaded the last 7.3.1 (provided by hashcode) flashed and voilà - my kindle´s back!!
thx again!
Mistaz said:
Just wanted to say merci bc.
Running the stock rom (rooted + 2nd boot-loader) I´ve flashed the "1.4 GHz(try me first)" by Maromi.
I made a backup before of everything but unfortunately moved. the files to my PC.
With the result of stucking at the blue Kindle logo.
A fastboot cable has been ordered but didn´t arrived in time before the week-end.
Just like you I´ve looked around quite a long time, tried several options but then your thread was the only solution!
By your advice I´ve sideloaded the last 7.3.1 (provided by hashcode) flashed and voilà - my kindle´s back!!
thx again!
Click to expand...
Click to collapse
I'm glad that it was useful to you
I was affraid that I was the only one "enthusiastic" enough to do the mistake. :laugh:
gornog said:
Today I decided to unleash my kfhd7 and install CyanogenMod.
After installing the 2nd Bootloader and the recovery, I 'accidentally' removed all my data in the hurry (anyway, I forgot to place the ROM on the SDCard folder before :silly. I was quite confident while doing this, based on my experience with other Android devices, I thought it would be easy to mount the SDCard folder to the computer using TWRP... But that wasn't the case. And my device was not recognize by ADB while in Recovery Mod.
After some research on the forum I noticed that the poor people who had this problem before had to reflash the stock image through the recovery. I used another method, mostly by finding a way to reinstall the drivers. So I decided to share my experience. I know that is maybe a bit noob, but I would enjoyed to find this tutorial while I was despaired and stuck on recovery mod.
Last precision : I am using Windows 8 (and I'm French, so pardon my French ).
What you need
ADB version 1.0.29 or higher you can find the version by typing "adb version" at the command terminal
Kindle Fire HD ADB drivers already installed, I guess it was the case if you were able to install the recovery
The .zip file of whatever you want to flash, dont forget the gapps if you want to flash Cyanogen
That's all, no need of factory cable.
1. Install drivers
The first step is to reinstall the driver, either the device was recognised before the flash.
Open the Device Manager (by typing directly devmgmt.msc)
You should see "Amazon Kindle Fire HD" under the "Other Devices"
Right click "update driver"
"Let me pick driver on my computer"
"choose in a list..."
"All devices" then next
At the bottom of the window you can choose a custom driver. Go this path:
C:\Windows\System32\DriverStore\FileRepository\android_winusb.inf_amd64_048d6e54936abbc3
The last number might be different (or may not, in fact I have no idea).
And voilà!!
Now adb should work.
2. Use sideload
You can now push your .zip to the sdcard, but TWRP have a really useful and smart way to do it.
Go into the advanced option of ADB. The click ADB sideload and swipe to start.
Just type
Code:
adb sideload yourfile.zip
and it's done! Don't forget to repeat it for googleapps.
For some reason I had an error from TWRP complaining that he didn't find any OS installed. It worked anyway for me.
Click to expand...
Click to collapse
After following your steps I will get to the part where i have to click the last file for the drivers and after I do my computer will say that Windows was unable to find the drivers for the KFHD7, if you have any suggestions on what to do that would be greatly appreciated.
th3lawmak3r76 said:
After following your steps I will get to the part where i have to click the last file for the drivers and after I do my computer will say that Windows was unable to find the drivers for the KFHD7, if you have any suggestions on what to do that would be greatly appreciated.
Click to expand...
Click to collapse
Did ADB worked properly before, with drivers installed? If so you can try something else to reinstall it.
The first step are the same,
Right click "update driver"
"Browse my computer for driver software"
"Let me pick driver on my computer"
And try to find in the list if there is a "Kindle Fire" in the list of devices. You might be able to install it from here.
Otherwise try to reinstall the amazon adb driver (you can find it easily in this forum), and then eventually perform again the operation above.
Update software driver of Windows7 32 bit path :
C:\Windows\system32\driver\ android_winusb.inf
I've tried all your steps and plenty more all over this forum.. I can't figure out why my Kindle HD 8.9 wont connect properly so I could push the rom via ADB.. I basically fell through the same issue as you.. except I'm stuck at trying to get Windows to recognize the Kindle properly... This is what I get regardless of what driver, or .inf I push at it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
/10postprereq
EDIT: I got it working, thank you very much for your post.. Helped a lot
gornog said:
2. Use sideload
You can now push your .zip to the sdcard, but TWRP have a really useful and smart way to do it.
Go into the advanced option of ADB. The click ADB sideload and swipe to start.
Just type
Code:
adb sideload yourfile.zip
and it's done! Don't forget to repeat it for googleapps if you need it.
For some reasons I had an error from TWRP complaining that he didn't find any OS installed. It worked anyway for me.
Click to expand...
Click to collapse
For some reason I cannot get this to work. I must not be typing the command language properly.
adb sideload cm-10.1xxxx
I get the following message:cannot read "sideload"
Any thoughts here? Thanks!!
krakora said:
For some reason I cannot get this to work. I must not be typing the command language properly.
adb sideload cm-10.1xxxx
I get the following message:cannot read "sideload"
Any thoughts here? Thanks!!
Click to expand...
Click to collapse
Make sure the ROM or file you're sideloading is in the same directory from which you are sending the command, or replace the filename with the exact full path to the file.
Success
soupmagnet said:
Make sure the ROM or file you're sideloading is in the same directory from which you are sending the command, or replace the filename with the exact full path to the file.
Click to expand...
Click to collapse
Thanks soupmagnet. Yes and Yes.
First: I did not have the Android SDK tools set up properly. I watched the interwebs and took some time to learn the very basic ADB commands. Once I changed directories to the desktop (where my zips were sitting) the simple sideload was a snap. I did get "error closed" message a couple times and used "adb usb" seemed to restart the process. At the end of day, success, my Kindle is flipping awesome now, I know a bit more about pushing files using ADB, and all is good in the world.
Thanks again XDA Developers!
PS: As a side note... I was on 7.4.3 version of the Amazon software and when I installed TWRP and the bootloader. Flash fire makes you switch to 7.2.3 version of the bootloader. I think that is what hosed me in the process... I could only get to recovery and it was like the OS was gone afterwards. Anyways, if you get trapped in recovery, get ready to learn something. :good:
I'm having trouble getting ADB to recognize the sideload command. I have found 2 different places that it is installed on my computer.
Do I use the ADB in the Android SDK, or the one in the Kindle Fire First Aide folder? When I try to open the one in the Android SDK folder the CMD Prompt pops up and flashes loads of text before auto closing, I get the same thing from the KF First Aide folder.
I just need to get my rom.zip onto my Kindle Fire HD, but I am totally lost on where to go from here since I am stuck on either the Boot screen or the TWRP bootloader.
Any help you can offer would be greatly appreciated.
ButchTheKitty said:
I'm having trouble getting ADB to recognize the sideload command. I have found 2 different places that it is installed on my computer.
Do I use the ADB in the Android SDK, or the one in the Kindle Fire First Aide folder? When I try to open the one in the Android SDK folder the CMD Prompt pops up and flashes loads of text before auto closing, I get the same thing from the KF First Aide folder.
I just need to get my rom.zip onto my Kindle Fire HD, but I am totally lost on where to go from here since I am stuck on either the Boot screen or the TWRP bootloader.
Any help you can offer would be greatly appreciated.
Click to expand...
Click to collapse
You don't run ADB like a standalone program. It's just a series of commands to be used from the command line. In order for this to work, the adb executable/binary/whatever must be in the same directory from which you are entering the commands (research the 'cd' command for more details).
Also, for the "sideload" command to work, your device must be booted into TWRP and you have to execute the sideload function from the "Advanced" menu.
soupmagnet said:
You don't run ADB like a standalone program. It's just a series of commands to be used from the command line. In order for this to work, the adb executable/binary/whatever must be in the same directory from which you are entering the commands (research the 'cd' command for more details).
Also, for the "sideload" command to work, your device must be booted into TWRP and you have to execute the sideload function from the "Advanced" menu.
Click to expand...
Click to collapse
Thanks for the quick reply, I decided to just re-flash to the stock 8.1.4 and restart the process, only this time I made sure to put the .zip folder for the new Rom on the systems storage first. Seems to be working so far, CyanogenMod is installing as I type this.
Thanks so much for working on this though, you guys do amazing work.
Dam thank you man
man with out this tread i would be F in a major way i have suceded in bricking two kindle fires hd 7 in the last week
one is compleatly dead dead dead waiting on factory cable. the other i was able to rescue today because of your post
(op) post,
i am not new to ADB, but the kffa, twrp,and other programs used to do these projects never seem to work, for me always stop at a bad time
. The thread installing twrp-2nd bootloader on this site has major flaws i am new to this so i chose 1st timer treads
(thing for dummies) things like step by step instructions, like i was able to follow your instructions easily (although you should have used an address like C;/desktop/xxxx.zip insted of (your zipfile) in the sideload code example. after i figerd out that deal it was easly done 5 min later loaded the code into adb ADB sideload C;/desktop/kfhd7-amizon-os-7.4.3.zip and 5 min after that my kindle rebooted and was back to normal all files intact even my apps. like i never touch a thing. it upgraded back to 7.4.6 and reloaded my apps.
I followed the instructions to a tee 2 times on the "root and recovery w/TWRP" tread and both times wound up having the programs kffa, and twrp, flashfile. stop at some point during the process, and result in me bricking.
i could have missed something or maybe the step by step missed a step or maybe my jdk was f but both time
i was screwed.
I think maybe they don't see the reader as a novice, although most if not all readers here are a novice's of some kind and so leave out info needed to complete with success, the tread i mention earlier he steered away from the topic so many times it made it almost impossible to follow and only refereed to successful outcomes, like put this into the cmd line next do this. but not stopping to think what if the person reading didnt get that response from the command line what do i do then?
And thats just what happen to me both times everything was going great and he said put this adb code in and i couldn't get it to respond like he said or it stoped cant find device or just sit there and do nothing, screwed... im into it now cant back up cant go forward your screwed. anyway my rant over now. THANKS FOR MAKING THIS TREAD you saved my ass.
thelz said:
man with out this tread i would be F in a major way i have suceded in bricking two kindle fires hd 7 in the last week
one is compleatly dead dead dead waiting on factory cable. the other i was able to rescue today because of your post
(op) post,
i am not new to ADB, but the kffa, twrp,and other programs used to do these projects never seem to work, for me always stop at a bad time
. The thread installing twrp-2nd bootloader on this site has major flaws i am new to this so i chose 1st timer treads
(thing for dummies) things like step by step instructions, like i was able to follow your instructions easily (although you should have used an address like C;/desktop/xxxx.zip insted of (your zipfile) in the sideload code example. after i figerd out that deal it was easly done 5 min later loaded the code into adb ADB sideload C;/desktop/kfhd7-amizon-os-7.4.3.zip and 5 min after that my kindle rebooted and was back to normal all files intact even my apps. like i never touch a thing. it upgraded back to 7.4.6 and reloaded my apps.
I followed the instructions to a tee 2 times on the "root and recovery w/TWRP" tread and both times wound up having the programs kffa, and twrp, flashfile. stop at some point during the process, and result in me bricking.
i could have missed something or maybe the step by step missed a step or maybe my jdk was f but both time
i was screwed.
I think maybe they don't see the reader as a novice, although most if not all readers here are a novice's of some kind and so leave out info needed to complete with success, the tread i mention earlier he steered away from the topic so many times it made it almost impossible to follow and only refereed to successful outcomes, like put this into the cmd line next do this. but not stopping to think what if the person reading didnt get that response from the command line what do i do then?
And thats just what happen to me both times everything was going great and he said put this adb code in and i couldn't get it to respond like he said or it stoped cant find device or just sit there and do nothing, screwed... im into it now cant back up cant go forward your screwed. anyway my rant over now. THANKS FOR MAKING THIS TREAD you saved my ass.
Click to expand...
Click to collapse
Which thread did you use to install TWRP?
>>Sent from my homebuilt TARDIS running Android 4.3... Or maybe it's a rooted Kindle Fire HD running ChameleonOS<<
Adb sideload not working
Hi guys, i need your help please! I am at the twrp menu trying to open adb sideload and it says"starting adb sideload feature..." but it stays like that for ages. Any idea??
guidomagaldi said:
Hi guys, i need your help please! I am at the twrp menu trying to open adb sideload and it says"starting adb sideload feature..." but it stays like that for ages. Any idea??
Click to expand...
Click to collapse
Stunts has a nice write up on this exact thing here http://forum.xda-developers.com/showthread.php?t=2459498
LinearEquation said:
Stunts has a nice write up on this exact thing here http://forum.xda-developers.com/showthread.php?t=2459498
Click to expand...
Click to collapse
thanks! its working!
guidomagaldi said:
thanks! its working!
Click to expand...
Click to collapse
You're welcome. Stunts did the write up, I just laid it out for you to play out.
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers
Help please
gornog said:
Today I decided to unleash my kfhd7 and install CyanogenMod.
After installing the 2nd Bootloader and the recovery, I 'accidentally' removed all my data in the hurry (anyway, I forgot to place the ROM on the SDCard folder before :silly. I was quite confident while doing this, based on my experience with other Android devices, I thought it would be easy to mount the SDCard folder to the computer using TWRP... But that wasn't the case. And my device was not recognize by ADB while in Recovery Mod.
After some research on the forum I noticed that the poor people who had this problem before had to reflash the stock image through the recovery. I used another method, mostly by finding a way to reinstall the drivers. So I decided to share my experience. I know that is maybe a bit noob, but I would enjoyed to find this tutorial while I was despaired and stuck on recovery mod.
Last precision : I am using Windows 8 (and I'm French, so pardon my French ).
What you need
ADB version 1.0.29 or higher you can find the version by typing "adb version" at the command terminal
Kindle Fire HD ADB drivers already installed, I guess it was the case if you were able to install the recovery. Other wise try to install it, you should find the the file executable easily on this forum.
The .zip file of whatever you want to flash, dont forget the gapps if you want to flash Cyanogen
That's all, no need of factory cable.
1. Install drivers
The first step is to reinstall the driver, considering the device was recognised before the flash but not anymore.
Open the Device Manager (hint: by typing directly devmgmt.msc)
You should see "Amazon Kindle Fire HD" under the "Other Devices"
Right click "update driver"
"Browse my computer for driver software"
"Let me pick from a list of device drivers on my computer"
"All devices" then next
At the bottom of the window you can choose a custom driver. Go this path:
C:\Windows\System32\DriverStore\FileRepository\android_winusb.inf_amd64_048d6e54936abbc3
The last number might be different (or may not, in fact I have no idea).
And voilà!!
Now adb should work.
2. Use sideload
You can now push your .zip to the sdcard, but TWRP have a really useful and smart way to do it.
Go into the advanced option of ADB. The click ADB sideload and swipe to start.
Just type
Code:
adb sideload yourfile.zip
and it's done! Don't forget to repeat it for googleapps if you need it.
For some reasons I had an error from TWRP complaining that he didn't find any OS installed. It worked anyway for me.
Click to expand...
Click to collapse
Hey please help me I have donwloaded amazon kindle fire but it doesn't displays in my device manager furthermore in my computer I cant find driver software but yes in program files i do have amazon kindle folder, what should I do please help
First i want to say Speacial Thanks to @xyz`, @k4y0z, @diplomatic and @ggow who make it possible to get a costum rom on a fire 7(9th gen)!
But i needed informations from more sites to get it work and i want to collect all informations in this Thread to make it easier for noobs like me I hope thats okay, i only collect informations, credits goes to:
@k4y0z and @xyz` for the bootloader hack
@diplomatic for the temp root
@ggow for the lineageos for mustang
So i will show the hole way From Stock FireOs 6.3.1.2 until you boot LineageOs 14.1
In this Guide i will use the Software method to get into bootrom mode. Software method: use mtk-su to do the thing.
Careful: this will break your device… and then you fix it by installing a new OS.
Any OS above 6.3.1.2 needs to use the hardware method!
Here you can find the hardware method: https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
I flash some devices but that was the most difficult. It will help if you have some experience how to flash devices.
NOTICE :
Before you move further, make clear that rooting device -
Your warranty will be void
Some of functions may not work on rooted device, some function may get back with un rooting, some may never.
All your data on device will be lost
Flashing custom binaries may brick (Usually soft but can be hard brick too) your device, so follow it on your own risk!
If you are ready with condition, move further -
Click to expand...
Click to collapse
Make sure you read this guide completely before starting!
This Hardware you need:
Working Amazon Fire 7 2019 9th gen (tested with FireOs 6.3.1.2)
USB cable for Kindle Fire
empty USB drive (min. 2Gb)
computer that can boot from USB drive
Download This Software:
lubuntu-19.10-desktop-amd64.iso # get it here https://lubuntu.net and download the AMD64 version
rufus-3.9.exe # get it here https://rufus.ie
mtk-su_r21.zip # get it here https://forum.xda-developers.com/attachment.php?attachmentid=4971443
amonet-mustang.zip # get it here https://forum.xda-developers.com/attachment.php?attachmentid=4785431&d=1561925516
lineage-14.1-20190827-UNOFFICIAL-mustang.zip # get it here https://androidfilehost.com/?w=files&flid=297948
open_gapps-arm-7.1-mini-20200403.zip # go to https://opengapps.org and choose AMR -> 7.1 -> and a variant of your choice i use mini
Step 1 Prepare Usb Stick
################################
Okay first we make the usb stick ready with Lubuntu.
1.1 Start the rufus-3.9.exe
1.2 choose the Lubuntu image file and push start
1.3 it will ask ISO image mode or DD image mode, choose the DD image mode!
1.4 after that put these files to C:\ :
mtk-su_r21.zip
amonet-mustang.zip
lineage-14.1-20190827-UNOFFICIAL-mustang.zip
open_gapps-arm-7.1-mini-20200403.zip
1.5 Turn off your Computer!
Step 2 Boot Live Linux
################################
2.1 Turn on your Computer and boot from usb and start lubuntu
(2.1.1 If you use wlan connect with it)
2.2 Open a terminal window # (go to "start button" at the left corner choose -> system tools -> QTerminal)
2.3 type "sudo apt install python3 python3-serial android-tools-adb android-tools-fastboot" push enter
2.3.1 it ask you something, say yes
2.4 type "sudo apt-get remove modemmanager" push enter
2.4.1 it ask you something, say yes, if it done close this window
2.5 Click on the "Computer" icon on Desktop
2.6 Search your Windows device and copy the 4 files from step 1.4 to lubuntu home directory (make it easier later)
Step 3 Prepare kindle
################################
3.1 Go to settings and enable developer options (need to push the serialnummber multiple times)
3.2 Go to developer options Enable USB debugging
3.3 Connect kindle to computer
3.3.1 On the kindle,
3.3.2 pull down the menu,
3.3.3 click the USB charging, “tap for other USB options” and select PTP for “transfer photos”
3.3.4 Click Accept to allow permission for your computer.
Step 4 Temporary root (Terminal window1)
################################
4.1 Open the mtk-su_r21.zip
4.2 copy the arm folder to lubuntu home directory
4.3 Open a new terminal window
4.4 type "sudo adb push arm/mtk-su /data/local/tmp” push enter
once successful, run these commands:
4.5 type "adb shell" push enter
4.6 type "cd /data/local/tmp" push enter
4.7 type "./mtk-su" push enter
4.8 type "getenforce" push enter # Just to confirm it says Permissive
4.9 type "echo 0 > /sys/block/mmcblk0boot0/force_ro" push enter
4.10 type "dd if=/dev/zero of=/dev/block/mmcblk0boot0 bs=512 count=8" push enter
Dont close this window!. you will need it in a moment.
Step 5 Bootrom Mode (Terminal window2)
################################
5.1 Open the amonet-mustang.zip
5.2 copy the amonet-mustang folder to lubuntu home directory
5.3 Open a new terminal window
5.4 type "cd amonet-mustang/" push enter
5.5 type "sudo ./bootrom-step.sh" push enter
5.6 Go back to the first Terminal window and type "reboot" push enter
5.7 Go back to the second Terminal, the tablet should restart, and the amonet script will begin to run.
Press Enter to continue, it will start copying things. Should take about 4 minutes.
Once the script finished, the kindle will restart into fastboot mode.
5.8 All you will see if the amazon logo. to verify that the device is in fastboot mode go back to the first Terminal window
and type "sudo fastboot devices" push enter
it will list the device # if it find 1 device you make all right
Step 6 Fastboot & TWRP
################################
6.1 Go back to the second Terminal window
6.2 type "sudo ./fastboot_step.sh"
The tablet will flash some text and do a few things. give it a minute or two.
The tablet will flash and appear to restart, let it do its thing until the screen goes dark.
6.3 Tap the power button twice and TWRP will pop up.
SUCCESS! # TWRP (Team Win Recovery Project) is now installed and can be launched by holding down VOL Down (left most button from pwr) and Power when starting up the device.
(At this point you can try to put the files on a SD Card, but i try it with multiple ones and TWRP dont find one, if you have one that work you can jump to step 8.4)
Edit: or use adblink from here https://forum.xda-developers.com/fire-tv/themes-apps/adblink-v2-04-t3389826
Step 7 Set permissions to Copy
################################
7.1 In TWRP on you kindle push wipe -> push Format Data and Swipe to reset
7.2 Now we need to obtain the idVendor of the kindle.
Go to the first Terminal window and type "sudo dmesg" push enter look for idVendor"XXXX", for me, the ID was "18d1".
7.3 Next, you need to give the ”plugdev” group access to the device.
You are going to create a file and then change some permissions then restart the services.
7.4 type "sudo nano /etc/udev/rules.d/51-android.rules" # create the file
7.5 and type the following line: #(Change idVendor to your ID)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev"
7.6 push ctrl + x , and hit y to save. # push a button and it close but hold the terminal open
7.7 Now assign read permissions on the files, reload udev and reload the adb daemon:
7.7.1 type "sudo chmod a+r /etc/udev/rules.d/51-android.rules" push enter
7.7.2 type "sudo udevadm control --reload-rules" push enter
7.7.3 type "adb kill-server" push enter
7.7.4 type "adb start-server" push enter
(You may have to disconnect and connect again your device to the USB port) # i dont needed it
Step 8 Copy & Install LineageOs
################################
NOW you can copy the files using the adb push command, like we did before.
8.1 type "sudo adb push /lineage-14.1-20190827-UNOFFICIAL-mustang.zip /data/local/tmp/lineage.zip" push enter
8.2 type "sudo adb push /open_gapps-arm-7.1-mini-20200403.zip /data/local/tmp/gapps.zip" push enter
After it finish copying, use TWRP to install the image
8.3 In TWRP push install go to path /data/local/tmp/ # there you find lineage.zip & gapps.zip
8.4 Choose lineage.zip and swipe to install
8.5 After that go back and choose gapps.zip and swipe to install
8.6 if its done you can push "Reboot System"
You are Finaly Done LineageOs 14.1 will booting now! # it will take some time at the first boot
Edit:
Install the "sod-fix-test.zip" by using TWRP you can find it here https://forum.xda-developers.com/showpost.php?p=80621157&postcount=253 @Ziona
(This fix the charge issue)
i find so much usefull things at xda-developers to flashing much devices include this device
So for this device it was really difficult and i was think it will be great thanks when i collect all informations for other(and me for the next time ).
And i think, thats understandable for anyone. I Hope it will help other People too.
Sources:
Unlock & root By xyz` https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
Amazing Temp Root By diplomatic https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
LineageOS 14.1 By ggow https://forum.xda-developers.com/amazon-fire/orig-development/rom-lineage-14-1-t3957329
Thanks for the guide, do you know if this also applies to Fire OS 6.3.1.5 ? as I have a fire 7 mustang version
At first start i connet the fire 7 with wifi and it makes a small update to 6.3.1.4 then i make a factory reset with stock recovery and i was back to 6.3.1.2
Try the factory reset if that dont work and you are still on 6.3.1.5, dont try this Guide i only test it with a 6.3.1.2 device!
It's all good, followed your guide and I'm on lineage os now. Thanks again!
So just to understand, Cozzysa: you sis it with 6.3.1.5 ?
Hi, I try here, and I stooped in the step 4.6, the result is: No such file or directory.
What's wrong?
edit: I founded the error, in the step, please correct the folder temp to tmp.
lucas.lop said:
Hi, I try here, and I stooped in the step 4.6, the result is: No such file or directory.
What's wrong?
edit: I founded the error, in the step, please correct the folder temp to tmp.
Click to expand...
Click to collapse
Thanks! i edit it! if you find some other things tell me
nimrodk3 said:
So just to understand, Cozzysa: you sis it with 6.3.1.5 ?
Click to expand...
Click to collapse
Thats a good question
_SWaTcH_ said:
Thanks! i edit it! if you find some other things tell me
Thats a good question
Click to expand...
Click to collapse
I try here with 6.3.1.5 and don't work. I'm with this problem too.
lucas.lop said:
I try here with 6.3.1.5 and don't work. I'm with this problem too.
Click to expand...
Click to collapse
This guide will only work if you are on 6.3.1.2 or below.
MTK-su = Amazon Fire 7 2019 -- up to Fire OS 6.3.1.2 build 0002517050244 only
---------- Post added at 01:19 PM ---------- Previous post was at 01:10 PM ----------
---------- Post added at 01:22 PM ---------- Previous post was at 01:19 PM ----------
@_SWaTcH_
You might want to give credit to "diplomatic" for his temp root and you should possibly change to links to their threads.
For example 14.1 has this right next to the link to download. "*** Please do NOT create any mirrors ***"
I would also recommend a note that any OS above 6.3.1.2 needs to have the hardware unlock and link them over to the over thread.
Very nice instructions though!
Is no way out for 6.3.1.5?
lucas.lop said:
Is no way out for 6.3.1.5?
Click to expand...
Click to collapse
Go here for the hardware unlock method-
https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
Once you get into TWRP, you can install Lineage. You can put the lineage on your sdcard, or transfer to your download folder from a PC. You odnt have to use adb to push files. an easy way of transfering files is to use adblink from here...
https://forum.xda-developers.com/fire-tv/themes-apps/adblink-v2-04-t3389826
Or when plugged in set it to file transfer and it would come up as a removable media on a computer.
follow the instructions from the 14.1 thread for install.
Michajin said:
@_SWaTcH_
You might want to give credit to "diplomatic" for his temp root and you should possibly change to links to their threads.
For example 14.1 has this right next to the link to download. "*** Please do NOT create any mirrors ***"
I would also recommend a note that any OS above 6.3.1.2 needs to have the hardware unlock and link them over to the over thread.
Very nice instructions though!
Click to expand...
Click to collapse
Im sorry that i miss the credit for diplomatic :silly:
I add note that you need to use the hardware method for Os version above 6.3.1.2 and add links to their threads.
Device offline MTP Error
I follow everything flawlessly until step 7. None of my SD cards are recognized. So I follow the steps posted in Step 7. In my device list I see "omni mustang" then it says I cant access this drive. I do step 7 then go to push lineage onto the system it says device offline.
I have rebooted the tablet many times Disable MTP and Enabled MTP countless times.
Sorry this is all jumbled up. Hopefully you understand what I am trying to say.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nimrodk3 said:
So just to understand, Cozzysa: you sis it with 6.3.1.5 ?
Click to expand...
Click to collapse
Yeah it worked perfectly with the hardware hack
Ozed20 said:
I follow everything flawlessly until step 7. None of my SD cards are recognized. So I follow the steps posted in Step 7. In my device list I see "omni mustang" then it says I cant access this drive. I do step 7 then go to push lineage onto the system it says device offline.
I have rebooted the tablet many times Disable MTP and Enabled MTP countless times.
Sorry this is all jumbled up. Hopefully you understand what I am trying to say.
Click to expand...
Click to collapse
So i think you have install TWRP and you only need to copy the files to your fire 7, Michajin post a other way:
Michajin said:
Once you get into TWRP, you can install Lineage. You can put the lineage on your sdcard, or transfer to your download folder from a PC. You odnt have to use adb to push files. an easy way of transfering files is to use adblink from here...
https://forum.xda-developers.com/fire-tv/themes-apps/adblink-v2-04-t3389826
Or when plugged in set it to file transfer and it would come up as a removable media on a computer.
follow the instructions from the 14.1 thread for install.
Click to expand...
Click to collapse
Worked then broke
Not sure what happened. Got everything installed booted into lineage 14.1 downloaded apps browsed the web etc. I went into the list of apps and turned off auto start on things I wasn't planning to use the tablet for. Mail, messages, etc to save on memory usage these devices don't seem to come with much to spare. Then held the power button, clicked restart and it never came back, doesn't respond on the power button. Not sure where I need to go from here.
Additional Info: I had to use the hardware method since reset to factory took me back to 6.3.1.5
DrGuns4Hands said:
Not sure what happened. Got everything installed booted into lineage 14.1 downloaded apps browsed the web etc. I went into the list of apps and turned off auto start on things I wasn't planning to use the tablet for. Mail, messages, etc to save a memory usage. Then held the power button, clicked restart and it never came back, doesn't respond on the power button. Not sure where I need to go from here.
Click to expand...
Click to collapse
Hold the power button for about 10 seconds to do a power off...
It is a known issue with 14.1 Lineage rom for this. Did you install the sod patch? Check out the 14.1 thread here.... Post #566
https://forum.xda-developers.com/amazon-fire/orig-development/rom-lineage-14-1-t3957329/page57
Michajin said:
Hold the power button for about 10 seconds to do a power off...
It is a known issue with 14.1 Lineage rom for this. Did you install the sod patch? Check out the 14.1 thread here.... Post #566
https://forum.xda-developers.com/amazon-fire/orig-development/rom-lineage-14-1-t3957329/page57
Click to expand...
Click to collapse
Not sure what sod means. I did hold down the power button for quite a while and the tablet wouldn't turn on, but I can't say for certain it was 10 seconds I'll have to try again when I get home. Perhaps this patch should be in the installation instructions here if this is a known issue?
DrGuns4Hands said:
Not sure what sod means. I did hold down the power button for quite a while and the tablet wouldn't turn on, but I can't say for certain it was 10 seconds I'll have to try again when I get home. Perhaps this patch should be in the installation instructions here if this is a known issue?
Click to expand...
Click to collapse
Screen Of Death. You might have to pull the battery. The Developer who created the Rom has been unavailable, being custom roms expect bugs. Always good to look at the last few pages of any thread to know status and current issues. When the GGOW returns he will likely update the latest security patches and install the patches into the latest. Remember these are volunteers who have no obligation to do this. Some don't even accept donations.
Michajin said:
Screen Of Death. You might have to pull the battery. The Developer who created the Rom has been unavailable, being custom roms expect bugs. Always good to look at the last few pages of any thread to know status and current issues. When the GGOW returns he will likely update the latest security patches and install the patches into the latest. Remember these are volunteers who have no obligation to do this. Some don't even accept donations.
Click to expand...
Click to collapse
Thanks. This is my first time with a custom ROM. I got the tablet just to do chromecast control for my TV in the living room and realized quickly that Fire OS just felt to clunky to keep on the device. Guess I'll be learning how to do update patches since I think that lineage will still be the better solution overall. Any suggestion on where to look to understand how to do the updates? I followed this guide as a step by step assuming it would be the whole kit and kaboodle, so can't really say I understand what pieces I'd need to update or where to look to keep things up to date to the most stable version.
I spent the better part of 4 hours today setting up the connection between my new ATOTO S8 Pro and my laptop. After getting USB debugging working, and a functional adb shell, I pulled off everything that I could copy with the limited permissions I had.
To be clear, I have NOT rooted the headunit. I'm a little leery about doing it, as I don't want to break anything, and as of right now, there is no way to restore the headunit back to factory like you would with, say, a Pixel phone.
BUT, for those of you who are curious here is my compressed system dump (or rather, adb pull) of everything I could get my hands on while in a factory state.
https://drive.google.com/file/d/13llpDmcNc5pyKbOIePn1hdDYxXd5iPeP/view?usp=sharing
INTERESTING TIDBITS:
* There is a "fastboot mode". Accessed by the usual "adb reboot fastboot" (still seeing what I can do with it)
* After around 6m 30s, fastboot mode will automatically reboot the unit back into the OS. Fastboot activity MAY reset the idle timer, not sure yet.
* There is NO "recovery mode". "adb reboot recovery" simply reboots the unit. May or may not be a recovery like most phones. Still digging.
* Seems the bootloader is unlockable. I have not done it though. You can activate the "bootloader unlock" option in developer options.
* To access Developer Options, you do the usual button mashing on "About", but to access the actual menu, you need a play store program that will take you directly to it.
* The ONLY USB connection that USB debugging works on is USB1 --> Phone Link. For it to work, you need to change the "computer connection" to whatever the SECOND option is (I'm not translating it)
* File down the very end, outer part of the wire harness clip, and it will go in all the way and latch like it's supposed it. Just needs to clear the casing by 1/16" or less. EASY FIX!
If I find any more interesting things while I have this, I'll update the information here. If YOU decide to root yours, let me know how it goes. I don't have another $340 to spare to buy another one. I'm poor. lol
Subscribed. Thanks for reporting that adb can be done via the second usb connection menu option. I had given up not long ago but changed that last night and it did the trick.
kramttocs said:
Subscribed. Thanks for reporting that adb can be done via the second usb connection menu option. I had given up not long ago but changed that last night and it did the trick.
Click to expand...
Click to collapse
It was like the second thing I tried.
Doing some more probing in a few minutes. Going to see if there is a recovery mode that can be accessed.
So it looks like, if I'm reading things right, there is no root for Oreo using a "One-Click" method. I would have to have access to TWRP, CWM recovery, or something to flash SuperSU. Unless I'm forgetting a method....
When it comes to rooting, I am a consumer so excuse my ignorance. In the file dump does it have the boot.img? If so, is this anything helpful: https://forum.xda-developers.com/android/software-hacking/root-recovery-root-device-magisk-t3779454 ?
Silly/stupid question. I just connected my S8 Ultra up to my car this weekend. Do you use a double-ended USB-A to USB-A cable to connect to use ADB? Or is there another connection that I missed?
JMeister234 said:
Silly/stupid question. I just connected my S8 Ultra up to my car this weekend. Do you use a double-ended USB-A to USB-A cable to connect to use ADB? Or is there another connection that I missed?
Click to expand...
Click to collapse
I used a usb A to usb C as my laptop had the C port. I tried a usb A male to male adapter and that didn't work but it may have been the adapter. A true A to A male cable may work. Just make sure you change the usb setting in the menu of Developer tools.
If you don't know this already, you can access OEM settings on the ATOTO unit this way:
Settings>System, click this option four times continually>input 3368, you will enter into the OEM Settings
It did work for me. I eliminated the split screen view on the back up camera through this hidden menu.
BTW, I was able to get to developer's options without a separate app and interestingly my unit came with developer's options already turned on.
It is also not a guarantee that you can unlock the bootloader just because the option appears in developer's mode. These units use a very customized version of Android & it seems some things are still in the settings, but only cosmetically, they don't actually do anything.
We you or anyone able to root this device?
buffaloquinn said:
If you don't know this already, you can access OEM settings on the ATOTO unit this way:
Settings>System, click this option four times continually>input 3368, you will enter into the OEM Settings
It did work for me. I eliminated the split screen view on the back up camera through this hidden menu.
BTW, I was able to get to developer's options without a separate app and interestingly my unit came with developer's options already turned on.
It is also not a guarantee that you can unlock the bootloader just because the option appears in developer's mode. These units use a very customized version of Android & it seems some things are still in the settings, but only cosmetically, they don't actually do anything.
Click to expand...
Click to collapse
afoarun said:
We you or anyone able to root this device?
Click to expand...
Click to collapse
As far as I know, no one has rooted this device. Having bricked a much cheaper unit attempting root, I'm reluctant to be the first one to try on this one.
buffaloquinn said:
As far as I know, no one has rooted this device. Having bricked a much cheaper unit attempting root, I'm reluctant to be the first one to try on this one.
Click to expand...
Click to collapse
This might help.
System-Update-only-Applicable-to-S8-Ultra-Model-CA.zip
Shared with Dropbox
www.dropbox.com
Someone else has a firmware for S8 pro. So if you run I to problems you can at least reset back to an unbricked state, maybe. Haven't tried it yet. But I hope to use Magisck so I can get Kali Hunter to be installed.
JMeister234 said:
This might help.
System-Update-only-Applicable-to-S8-Ultra-Model-CA.zip
Shared with Dropbox
www.dropbox.com
Someone else has a firmware for S8 pro. So if you run I to problems you can at least reset back to an unbricked state, maybe. Haven't tried it yet. But I hope to use Magisck so I can get Kali Hunter to be installed.
Click to expand...
Click to collapse
I have an S8 Premium with the floating 10 inch screen. I'd have to be damn sure the firmware was an exact match before I'd attempt it.
buffaloquinn said:
I have an S8 Premium with the floating 10 inch screen. I'd have to be damn sure the firmware was an exact match before I'd attempt it.
Click to expand...
Click to collapse
This guy has the Atoto S8 Pro zip file.
PasadenaTX
forum.xda-developers.com
I can't get adb to work yet so that's all that's stopping me
Atoto just gave it to me when I told them my touchscreen didn't work and I only had a Bluetooth mouse at home...
kramttocs said:
Subscribed. Thanks for reporting that adb can be done via the second usb connection menu option. I had given up not long ago but changed that last night and it did the trick.
Click to expand...
Click to collapse
I actually don't see the USB debugging options in the developer options. I did the 3368 thing but nothing in that menu looks anything close to USB debugging, ie same as my phone.
Without that, I don't know how to adb shell into the unit.
JMeister234 said:
I actually don't see the USB debugging options in the developer options. I did the 3368 thing but nothing in that menu looks anything close to USB debugging, ie same as my phone.
Without that, I don't know how to adb shell into the unit.
Click to expand...
Click to collapse
I'll have to check later but I believe it was from the top right 3 dot menu.
kramttocs said:
I'll have to check later but I believe it was from the top right 3 dot menu.
Click to expand...
Click to collapse
1. I can confirm that I flashed/updated the S8 Ultra using the Dropbox zip file above and after it reset Android, it did nothing but reset my google credentials. My apps were still there.
But it also didn't brick my S8 Ultra .
It has the similar files as the Joying zip file which has the same chipset.
After the flash, my phone asked to authorize the adb debugging, while connected to the head unit. I'll see if I can get the head unit to turn on adb debugging so I can root it.
JMeister234 said:
Without pics it didn't happen...
Click to expand...
Click to collapse
Another?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
JMeister234 said:
1. I can confirm that I flashed/updated the S8 Ultra using the Dropbox zip file above and after it reset Android, it did nothing but reset my google credentials. My apps were still there.
But it also didn't brick my S8 Ultra .
It has the similar files as the Joying zip file which has the same chipset.
After the flash, my phone asked to authorize the adb debugging, while connected to the head unit. I'll see if I can get the head unit to turn on adb debugging so I can root it.
Click to expand...
Click to collapse
Any new developments?
buffaloquinn said:
Any new developments?
Click to expand...
Click to collapse
Well I brought my Ouya back from the dead with LineageOS, converted a Chromebook to GalliumOS for pen testing, or it can connect to Ouyas using adb, or analyze a Lenovo Smartclock to try and add APK's to it before giving up (as others on XDA have also done).
But for this? I can't get ADB to see the head unit. Because there is no ADB Debugging in any of the menus (yes its has Dev Options enabled). No idea how others have done it. If I reboot into Recovery it might show up in "adb devices" command but if the device is simply on, there's nothing returned.
JMeister234 said:
Well I brought my Ouya back from the dead with LineageOS, converted a Chromebook to GalliumOS for pen testing, or it can connect to Ouyas using adb, or analyze a Lenovo Smartclock to try and add APK's to it before giving up (as others on XDA have also done).
But for this? I can't get ADB to see the head unit. Because there is no ADB Debugging in any of the menus (yes its has Dev Options enabled). No idea how others have done it. If I reboot into Recovery it might show up in "adb devices" command but if the device is simply on, there's nothing returned.
Click to expand...
Click to collapse
I use one of the Play Store apps to get into Developer options and it does show an ADB debugging option and most of the other choices available in a typical Developer's menu. The one I use is the first one that comes up in the search on play store, I think the author is Singlebyte.
Hello,
A long time ago I was using a Nook Glowlight 3. I had rooted it, installed relaunchX and a bunch of readers. Later I switched to Boox Air (for size) and did not use the Nook for a long time.
Recently my son showed interest in reading books from a tablet, and I thought Nook would be suitable for him. However, since it was rooted, it was a bit complicated for him to navigate, so I decided to return it to its original state. Here is what I did to end up where I am now. I will be happy to elaborate on any of these, but I do not want to make my initial post too long, so people will be less likely to skip it.
1. I did a factory reset (by pressing home button during reboot), but this somehow erased the Nook launcher (or maybe I had erased it before, I am almost it was working before). After this reset, upon a boot, I would get past basic setup (timezones and wi-fi) and then get a blank screen.
2. Then using 5taps L-R trick, I turned on USB debugging again and rooted it again.
3. I installed relaunchX and Renate's launcher, but I could not tie them to the home button. I did not know how (I still do not know). I could launch them with adb shell and monkey command though.
4. I tried to get into recovery mode or fastbook through adb (by using things like "adb reboot recovery"), but did not succeed.
5. I downloaded and put the update.zip for this Nook and put it on / as well as /sdcard/ directories. Put Nook to sleep and waited a long time, but no success there either.
6. I was getting frustrated at this point and finally did something really stupid: I unzipped update to a directory under sdcard, remounted various partitions rw and tried to copy all the files coming from update.zip via a cp command. After a short while this command ran, I received an error message, something like "/bin/sh permission denied" (I guess it was referring to execute permissions not being present, and got kicked out of adb shell.
7. Now, the machine is going into factory reset upon boot and after the factory reset it reboots and goes into factory reset again. I tried interrupting the reboot multiple times, pressed various button combinations during reboot, but there are only two outcomes: power off or going into factory reset.
Is there anything I can do? If you can think of a software solution, I'd love to hear it.
I am not good with hardware, and I don't have any equipment (in particular I do not have a UART) but I am faculty member in a physics department in a university, so I can probably access any reasonable electronics equipment. I am willing to do some hardware tinkering, or perhaps to call on a favor or two from some of my experimental colleagues.
I am willing to try pretty much anything since my son is asking if I repaired the Nook almost everyday, and I would like to be able to honestly say I tried everything.
Thanks in advance for any help you may provide.
cheers,
ato
Manually installing an update.zip is not difficult, but that's not how to do it.
If it's really in a loop that you can't break and there's no ADB then you'll have to get more drastic.
One way is to use a UART and interrupt u-boot while it's booting and going to fastboot. From there you can flash a recovery and go to it, do a manual update, maybe fix something that's broken.
Another way is to defeat the flash memory on boot so that it goes to the ROM bootloader. From there you can use my imxlink.exe to load a modified bootloader that will go directly to fastboot,
Either of those two ways requires you opening the case. The Glow3 is not as bad as the Glow2, it doesn't use tape.
Thank you for your response. I can definitely open the case. I found some instructions here:
Barnes And Noble Nook Glowlight 3 Disassembly
This is a disassembly Guide For the nook...
www.ifixit.com
that looks doable.
It sounds like your second suggestion does not require additional equipment (except to open the case). Did you describe elsewhere on this forum how to defeat the flash memory on boot? I have read so many of your postings here in the last few weeks (and I am very grateful for those). I am guessing this might be something you already described before.
I can also order a UART. Will a CP2102 unit w/ 3.3 and 5V be adequate? I just think having a serial connection is so cool that I need to try it.
Yeah, any USB UART will do.
OTOH, I'm a bit more of a fan of the FTDI than the CP2102. I did have problems with a driver years ago but haven't touched them since.
If you fall in love with UARTs and want to use them on something modern, you might need 1.8V
I think that these are pretty cool in having selectable logic level.
https://www.amazon.com/DSD-TECH-SH-U09C5-Converter-Support/dp/B07WX2DSVB/
OTOH, anything will work for now.
I live in Turkey and that FTDI does not seem to be available here. I will keep your recommendation in mind though, thank you!
I ordered a CP2102. They had links to a driver on the order page, hopefully I will not have big problems. It should arrive in a few days.
I will try and open my glow3. Do I need to do anything special about the power? It is almost fully charged, so it would take a long time to drain the battery, but I can certainly try.
OK. I took a leap of faith and opened it up (I have a small window when my kids are sleeping), hopefully did not blow up anything.
Here is a photo in case it might help with someone looking to replace their nook glowlight 3 battery:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I need to tinker with J11, J12 or J13, I can tell that they are way beyond my soldering capabilities. Do I need to get some connectors?
Would more detailed pictures help?
cheers,
atakan
No, you don't need to solder unless you want to make it permanent.
Usually just sticking wires in holes and adding a bit of sideways pressure is enough to make good contact.
If you have those 0.025" gold pins (like on cable ends) they are a close fit to the hole and work great.
Do you have any resistors on hand? Maybe 100 ohms or so?
We can try to get you going before the UART arrives.
I do not have any resistors on hand, but I can pick some up in about an hour. I will do so.
Unfortunately I do not have any gold pins either, but i think I can find some 0.5mm cables, which are probably actually 0.025''.
I found some resistors including 100 ohms (but also 47, 1000 etc). I also found some cables that measure 3/128 inches, quite close to 0.025. I got my avometer and optician's screwdriver set
How should I proceed?
While waiting your reply, I will install the WinUSB driver from zadig, I am guessing I will need that.
Download from my sig imxlink.exe and nnglow3.img (Neo Noogie).
Get the attached ub3fb.img
Code:
C:\>imxlink.exe ub3fb.img nnglow3.img
Now connect from TP23 to your 100 ohm resistor to a ground on the board.
While doing that LONG press the power button.
As soon as Windows "bongs" or imxlink.exe reacts disconnect the resistor and sit back.
You might have to try it a few times. Windows might be slow the first time that it sees 15a2/0063 on USB.
Wow! Something happened. iMX Link is working and now saying waiting for Fastboot or ADB.
Before that, the red led for Bootloader was on briefly.
The screen is showing the nook image that it shows while starting to boot.
Mmm, do you have the drivers for fastboot already loaded?
Are you sure that it isn't in fastboot?
When you pull the USB cable and reinsert it does it go "bong"?
Check in devmgmt.msc with "Show all devices". Look for 18d1/d00d
Make sure that it has a driver.
It really should go Red - Yellow - Green.
If not, try doing it again.
I do not know what the drivers for fastboot are. How I check for them?
When I pull the cable it goes "bong", but not when I reinsert it, not upon further pulls.
I'll try again.
Well, if you never saw yellow, you don't have drivers or something.
Did you ever have fastboot working on your desktop?
It's the same "Google drivers" as for ADB.
If you see something with an exclamation mark in Device Manager (devmgmt.msc) that's it.
I know this stuff works because on my Glow3 I intentionally erased u-boot so that I could always reboot using imxlink.exe and get a direct choice of boot image.
No, I always used ADB on Linux before, and not on Windows, which it what I am using now.
It is trying to install i.mx6sl driver from windows update and failing.
I will look for this "Google drivers" for ADB
I installed the Google drivers. It now went to red, then yellow but not green.
It is now saying
Waiting for disconnect...
Waiting for ADB...
Quote the text please, I don't know what's going on.
What's the screen doing?
You probably need to install the drivers for ADB.
If your Linux system has ADB you should be able to plug it in now.
I am sorry, I am really a noob w/ Windows, I cannot even take a screenshot (I tried PrtSc button).
Here is the output:
C:\Users\ato\Downloads\renate>imxlink.exe ub3fb.img nnglow3.img
Waiting for bootloader or Fastboot or ADB...
Found iMX6SL
Load addr 87800400, DCD offset 002c, DCD size 0220
67 DCD ops processed
Write, addr 87800400, size 00039270
********************************************************************************
********************************************************************************
*********************************************************************
Jumping to 87800400
Device disconnected correctly
Waiting for Fastboot or ADB...
product i.mx6sl NTX Smart Device
version 0.5
Sending boot image, 6043648 bytes... ok
Waiting for disconnect...
Waiting for ADB...
I installed Google ADB drivers.
When I try to run ADB from Windows, for "adb devices -l" I get an empty list.
Should reboot into linux and try?