My fire 6 HD OS Was 5.1.2
1- I flashed it by OS 4.5.3 via adb
2- It started 4.5.3 then downloaded 4.5.5 ( automatic update)
3-then stop working at all .
in the PC device manager appears ( MT65xx preloader ) for few seconds then disappear then reappear etc etc etc .
any ideas ??
NOW I Installed the driver for ( MT65xx preloader )
then
it becomes
Media Tek PreLoader USB VCOM (Android)(COM6) in the device manager
but is also appear and disappears !!
any Ideas to complete ???
moroxoro said:
NOW I Installed the driver for ( MT65xx preloader )
then
it becomes
Media Tek PreLoader USB VCOM (Android)(COM6) in the device manager
but is also appear and disappears !!
any Ideas to complete ???
Click to expand...
Click to collapse
There is no known way to unbrick what you have.
On other hand, it is interesting that 4.5.5 now bricks after 5.1.2. Was it 4.5.5 or 4.5.5.1 (if you remember) ?
bibikalka said:
There is no known way to unbrick what you have.
On other hand, it is interesting that 4.5.5 now bricks after 5.1.2. Was it 4.5.5 or 4.5.5.1 (if you remember) ?
Click to expand...
Click to collapse
I think it was 4.5.5 by 80% but not sure .
could you please help my in
http://forum.xda-developers.com/fire-hd/help/help-friend-fire-hd-6-4th-please-t3356610
to try via sptools ?
just need scatter file
Any help ?!?
Sent from my LG-H818 using Tapatalk
?!؟
Sent from my LG-H818 using Tapatalk
I'm in same exact boat. This blows. I'll keep updated if I find anything useful. But seems pretty gloomy so far..
CJD14 said:
I'm in same exact boat. This blows. I'll keep updated if I find anything useful. But seems pretty gloomy so far..
Click to expand...
Click to collapse
Please see post 3. No solution. But can you tell us if you were on OS 5.1.2 OR 5.1.2.1 before you sideloaded 4.5.3? (5.1.2.1 has a March date.)
I assume sequence was same: On 5.1.2 (or 5.1.2.1), sideloaded 4.5.3, then 4.5.3 OTA upgraded to 4.5.5. And then what? It just wouldn't boot after 4.5.5 installed? Did you see progress bar and then it died? Black screen or do you see a logo? Thanks.
DoLooper said:
Please see post 3. No solution. But can you tell us if you were on OS 5.1.2 OR 5.1.2.1 before you sideloaded 4.5.3? (5.1.2.1 has a March date.)
I assume sequence was same: On 5.1.2 (or 5.1.2.1), sideloaded 4.5.3, then 4.5.3 OTA upgraded to 4.5.5. And then what? It just wouldn't boot after 4.5.5 installed? Did you see progress bar and then it died? Black screen or do you see a logo? Thanks.
Click to expand...
Click to collapse
My problem is a slightly bit different. I looked and it said i was on 4.1.1 or 4.1.3 i believe, was the original OS upon recieving the device.
I literally just opened the package set it up, then installed two apps and found that Kingo root I believe it was, successfully rooted the device for me. I was connected to WiFi so of course it automatically downloaded the current update. I couldn't find a way to stop the auto update but there was a notification saying an aupdate was available so I just cleared it and planned on not updating at all until I could confirm this wouldn't happen.
I added a few books from my nexus 7 and sideloaded moon reader, both using es file explorer. I then looked away and all the sudden the device turned off and started 'applying update' and I thought F#%K!!! I knew it was too late, and I didn't look into it enough to find a way to stop it. I didn't think it would just do it without my okay.
Makes me mad. But after the update finished it just goes directly to Fire System Recovery with the orange exclamation mark with reboot system or reset to factory defaults. It tries to reboot twice then goes to this every time. Both achieve nothing.
So unfortunately I am unaware of what update it downloaded and applied against my will. I'm assuming the latest if its possible to jump that high.
I've had and fixed so many devices from tablets to phones to iOS devices, this is the first and only time that a device that quickly became screwed up and not only that, apparently is unfixable.
Can't believe Amazon doesn't have a software like Samsung Kies or something. Come on amazon.
DoLooper said:
Please see post 3. No solution. But can you tell us if you were on OS 5.1.2 OR 5.1.2.1 before you sideloaded 4.5.3? (5.1.2.1 has a March date.)
I assume sequence was same: On 5.1.2 (or 5.1.2.1), sideloaded 4.5.3, then 4.5.3 OTA upgraded to 4.5.5. And then what? It just wouldn't boot after 4.5.5 installed? Did you see progress bar and then it died? Black screen or do you see a logo? Thanks.
Click to expand...
Click to collapse
It was on OS 5.1.2 then sideloaded 4.5.3 then upgrade to 4.5.5 just the progress bar I saw then diad . I Didnt see the logo .
Sent from my LG-H818 using Tapatalk
moroxoro said:
My fire 6 HD OS Was 5.1.2
1- I flashed it by OS 4.5.3 via adb
2- It started 4.5.3 then downloaded 4.5.5 ( automatic update)
3-then stop working at all .
in the PC device manager appears ( MT65xx preloader ) for few seconds then disappear then reappear etc etc etc .
any ideas ??
Click to expand...
Click to collapse
moroxoro said:
It was on OS 5.1.2 then sideloaded 4.5.3 then upgrade to 4.5.5 just the progress bar I saw then diad . I Didnt see the logo .
Sent from my LG-H818 using Tapatalk
Click to expand...
Click to collapse
This kind of reminds of the other bricking epidemic, when people tried to upgrade from 4.5.5.1 to FireOS 5 from Oct and bricked a lot. And the devices are no longer under warranty ...
I'm in the same boat. I was using 5.4.2, then sideloaded 4.5.3 (it was a mistake, the idea was to sideload 5.2.2), then manually upgraded to 5.2.2 (copy to device and update from settings menu). I went to dinner and when I returned there was a black screen. When connected to PC, MT65xx keeps appearing and disappearing.
Edit: these are the bin names, not necessarily the OS version.
I can help in creating MT8135 scatter (or at least I can try) but I need a working device first. Can someone with a working device PM me?
I also have a bricked Fire HD 6.
I have a similar situation where it blinks in and out as MT65xx preloader. Plugged in, its bootlooped with the amazon screen. Unplugged theres a low battery sign. Plugged in, there seems to be that with the lightning recharge symbol.
I think I'd successfully rooted and everything, using the "[ROOT] With Kingroot and Tools + Play Store + Launcher (Newbie Friendly)" guide, up until trying to use NOVA LAUNCHER to replace the stock launcher. I noticed the tool with the scripts had a script to do the swap, so since the "set nova as default" wasn't working I decided to do that. I got bootlooped at that point, then stupidly tried a factory reset in the TWRP boot menu to start everything from square one. It seemed more or less locked in that bootlooped state where my computer seemed unable to connect.
However a day later I managed to get to the TWRP boot menu. But then the battery symbol started showing up, and I can no longer get to that menu.
This is sad day.
Same boat but with a KF HD7 2014 4th gen. No updates?
psfp said:
I'm in the same boat. I was using 5.4.2, then sideloaded 4.5.3 (it was a mistake, the idea was to sideload 5.2.2), then manually upgraded to 5.2.2 (copy to device and update from settings menu). I went to dinner and when I returned there was a black screen. When connected to PC, MT65xx keeps appearing and disappearing.
Edit: these are the bin names, not necessarily the OS version.
Click to expand...
Click to collapse
Fixed using this method:
https://forum.xda-developers.com/fire-hd/development/video-linux-iso-unbrick-fire-hd6-hd7-t3474999
Related
Hey,
I'm trying to root my Kindle Fire HDX (3. Generation) at time but I'm facing a problem. I'm using the Fire OS 4.5.2 . I enabled ADB, allowed externed apps to get installed and installed the driver.
That's the problem
-I start my KFHDX TOOLKIT v0.95
-Press 1 to install the Towelroot
- towelroot v1 starts on my device
- I press make it rain and nothing happens.
The "make it ra1n" button gets orange but it seems like the program is frozen - no message. I can still leave the application but at the end of the day my device is not going throug the rooting process.
Can anybody help me with that ? It would help me a lot.
I'd love to answere your questions.
At this moment, you can't root 4.5.2.
Any idea on how long til root available for 4.5.2
I'm sure it is being worked, i just got a new 8.9 hdx on order and wanted to switch my clash of clans game.
just the right time of this thread..
i just tried the same method 30mins ago..
same here, 4.5.2, it says not supported..
pwbloomer said:
I'm sure it is being worked, i just got a new 8.9 hdx on order and wanted to switch my clash of clans game.
Click to expand...
Click to collapse
As far as I know, there's currently no one looking into a root exploit for the newer firmwares.
Dann, anyways thanks for the fast answeres.
Take care
Hi all,
I recently got a new Dell Venue 7 3740 (yeah, not my first choice, but it was free for buying a computer). Anyway, started reading up on how to root the thing. I have a couple of apps that require root.
I found this thread: http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
and also the main Dell page: http://opensource.dell.com/releases/Venue_7_3740_Merrifield/developer-edition/
Following Dell's guide to rooting appears to NOT root it. Installing Root Checker confirms I don't have root. Unbricked it and got it back up from 4.4.2 to 4.4.4. By reading the first guide for the 3840, my question is ...
Is the boot image linked there compatible with my 3740?
(yeah, I know this should be in the developer section ... unfortunately I don't have enough posts ... also, I am familiar with rooting/flashing/etc, my first device that I put CM7 on was the original Galaxy S1 ... and I have CM10 on my S3.)
Tried, failed
Yeah I got this tablet with a PC too and tried rooting. It FUBAR'd on me and I had to wrestle with unbricking it. Which sorry to say is a job and a half, the images on Dell's site are corrupt for this WiFi only version (no partition.tbl file, system image incomplete). Ending up downloading the LTE versions firmware to get the missing files and rewriting the batch as the file names for the fastboot commands were wrong too. And even then the tablet wouldn't boot, so I had to store the OTA on an SD card and use recovery to flash it. Unfortunately that leaves me with 4.4.2 and the dreaded clock and browser issues. And OTA doesn't work, it keeps saying no updates are available. Spoke with a Dell rep who said OTAs were suspended and to try again in a week but I think OTA was broken for me when I tried rooting and boot loader was unlocked (which the PDF on Dell's site warns you about).
So now I have a working tablet that skips hours ahead and has general stability issues.
reaper-death said:
Yeah I got this tablet with a PC too and tried rooting. It FUBAR'd on me and I had to wrestle with unbricking it. Which sorry to say is a job and a half, the images on Dell's site are corrupt for this WiFi only version (no partition.tbl file, system image incomplete). Ending up downloading the LTE versions firmware to get the missing files and rewriting the batch as the file names for the fastboot commands were wrong too. And even then the tablet wouldn't boot, so I had to store the OTA on an SD card and use recovery to flash it. Unfortunately that leaves me with 4.4.2 and the dreaded clock and browser issues. And OTA doesn't work, it keeps saying no updates are available. Spoke with a Dell rep who said OTAs were suspended and to try again in a week but I think OTA was broken for me when I tried rooting and boot loader was unlocked (which the PDF on Dell's site warns you about).
So now I have a working tablet that skips hours ahead and has general stability issues.
Click to expand...
Click to collapse
Hmm ... Interestingly enough, I ran through the unbrick procedure from Dell, and didn't have any issues with it whatsoever. I'm not sure if they updated the TGZ since you updated.
I have read that root is for ADB to start with. Can anyone confirm this? If so, then which package could I get for a superuser binary?
ProfM2 said:
Hmm ... Interestingly enough, I ran through the unbrick procedure from Dell, and didn't have any issues with it whatsoever. I'm not sure if they updated the TGZ since you updated.
I have read that root is for ADB to start with. Can anyone confirm this? If so, then which package could I get for a superuser binary?
Click to expand...
Click to collapse
I did this process just a couple days ago so everything I pulled from opensource.dell was current. The unbrick tgz on the site shows up as 128mb for the wifi only A1195 and the A5195 shows as 821mb (odd). When I extracted the tgz it said "unexpected end" or something like that on the system image. Then again when I extracted from that extracted tgz.
Following the root process initially worked and the temp cwm recovery let me flash the supersu update. It booted with su just fine and I tried a couple apps that needed root and they worked. Once I rebooted again the tablet showed up with a USB icon and would go no further. Never having dealt with Intel SoC drivers it took me a while to get them installed properly, and then I eventually understood what "full power off" meant lol.
Do you know how I can relock the bootloader and get OTA working again, assuming I'm already on 4.4.2 from the OTA zip installed via recovery?
Thanks.
reaper-death said:
I did this process just a couple days ago so everything I pulled from opensource.dell was current. The unbrick tgz on the site shows up as 128mb for the wifi only A1195 and the A5195 shows as 821mb (odd). When I extracted the tgz it said "unexpected end" or something like that on the system image. Then again when I extracted from that extracted tgz.
Following the root process initially worked and the temp cwm recovery let me flash the supersu update. It booted with su just fine and I tried a couple apps that needed root and they worked. Once I rebooted again the tablet showed up with a USB icon and would go no further. Never having dealt with Intel SoC drivers it took me a while to get them installed properly, and then I eventually understood what "full power off" meant lol.
Do you know how I can relock the bootloader and get OTA working again, assuming I'm already on 4.4.2 from the OTA zip installed via recovery?
Thanks.
Click to expand...
Click to collapse
You better redo the unbrick procces cause as you are now, you won't be able to update your tablet and 4.4.2 has some issues with the clock and browser. The best way to root is by thetered cwm, I did it and it's working great.
reaper-death said:
I did this process just a couple days ago so everything I pulled from opensource.dell was current. The unbrick tgz on the site shows up as 128mb for the wifi only A1195 and the A5195 shows as 821mb (odd). When I extracted the tgz it said "unexpected end" or something like that on the system image. Then again when I extracted from that extracted tgz.
Click to expand...
Click to collapse
This is quite odd. From the documentation, it appears that the A195 is for the LTE version, and the A150 is Wifi only. Since I have the 3740 Wifi only, I only pulled the A150 version.
The Unbricking process was very straightforward and everything went smoothly, and after it rebooted, it prompted that there was a system update from Dell, and that took me from the 4.4.2 from the TGZ, to 4.4.4
ProfM2 said:
This is quite odd. From the documentation, it appears that the A195 is for the LTE version, and the A150 is Wifi only. Since I have the 3740 Wifi only, I only pulled the A150 version.
The Unbricking process was very straightforward and everything went smoothly, and after it rebooted, it prompted that there was a system update from Dell, and that took me from the 4.4.2 from the TGZ, to 4.4.4
Click to expand...
Click to collapse
http://opensource.dell.com/releases/Venue_7_3740_Merrifield/developer-edition/Doc/OSS_A150&A195.pdf
* For Wifi-only device on A150 and Wifi / LTE device on A195
I see it now, I think I was misinterpreting the above statement which means I've been flashing the A195 rom this whole time. Thank you all for your help! :good:
After getting my 3740 back to "Unbricked" mode, and OTA upgraded to 4.4.4, it appears that I'm completely locked out of the rooting process.
I've tried to start over with the Dell info (unlocking bootloader), however, neither of my PC's will detect the tablet when using xFSTK (one PC - Win8.1-64bit, other XP-32bit). The tablet IS detected, however, it appears that the drivers are no longer correct(?).
I normally run Ubuntu, and thats where my Android development setup is on ... I see that xFSTK is available for Linux ... has anyone used it? or would I be better trying to fight Windows?
ProfM2 said:
After getting my 3740 back to "Unbricked" mode, and OTA upgraded to 4.4.4, it appears that I'm completely locked out of the rooting process.
I've tried to start over with the Dell info (unlocking bootloader), however, neither of my PC's will detect the tablet when using xFSTK (one PC - Win8.1-64bit, other XP-32bit). The tablet IS detected, however, it appears that the drivers are no longer correct(?).
I normally run Ubuntu, and thats where my Android development setup is on ... I see that xFSTK is available for Linux ... has anyone used it? or would I be better trying to fight Windows?
Click to expand...
Click to collapse
It is mentioned somewhere that the 3740 and the 3840 use the same firmware. Assuming that, what you can do is download the latest SuperUser zip, copy it to the internal or external storage, then use THIS, or THIS to root through CWM.
graphdarnell said:
It is mentioned somewhere that the 3740 and the 3840 use the same firmware.
Click to expand...
Click to collapse
Hmmm ... I took this to mean that I could use the same boot.img as the Venue 8, and tried the process from this thread: http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
NOPE. (Don't try, it'll cause the tablet to go into the "help my androids' fallen and can't get up" icon. )
ProfM2 said:
Hmmm ... I took this to mean that I could use the same boot.img as the Venue 8, and tried the process from this thread: http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
NOPE. (Don't try, it'll cause the tablet to go into the "help my androids' fallen and can't get up" icon. )
Click to expand...
Click to collapse
I'm curious as to what it is you're trying to do. Why do you insist on having a developer's root (just the use of ADB shell), as opposed to full root flashing SuperSu from custom recovery?
graphdarnell said:
I'm curious as to what it is you're trying to do. Why do you insist on having a developer's root (just the use of ADB shell), as opposed to full root flashing SuperSu from custom recovery?
Click to expand...
Click to collapse
I just want full root.
Most of the info that I've read on here and elsewhere are geared to the 3830/3840. Not as much for the 3740. So, by playing with the device and learning what works/doesn't work, possibly others may find this info useful to them.
I've been having issues seeing the device from XP, Win8.1 and Ubuntu, in the 'off' state of the tablet, when the PC should be seeing the merrifield. Just this morning, after bricking it last night, I discovered that my PC seems to see the device right away if I press Vol+ while plugging in the microUSB. (again, something that may help someone else) I was planning on double checking this info later today, to make sure that it wasn't a fluke.
I do appreciate both of the links that you've posted in this thread, and I will check them out. Of course, both are labelled for the Venue 8, not the Venue 7 that I have. Since I've gained knowledge on the unbrick process I feel more comfortable trying them.
I've installed (or tried to install) SuperSU from the Play store, but it didn't appear to help much, since I didn't have the custom recovery setup at that time. I'll work on that tonight.
ProfM2 said:
I just want full root.
Most of the info that I've read on here and elsewhere are geared to the 3830/3840. Not as much for the 3740. So, by playing with the device and learning what works/doesn't work, possibly others may find this info useful to them.
I've been having issues seeing the device from XP, Win8.1 and Ubuntu, in the 'off' state of the tablet, when the PC should be seeing the merrifield. Just this morning, after bricking it last night, I discovered that my PC seems to see the device right away if I press Vol+ while plugging in the microUSB. (again, something that may help someone else) I was planning on double checking this info later today, to make sure that it wasn't a fluke.
I do appreciate both of the links that you've posted in this thread, and I will check them out. Of course, both are labelled for the Venue 8, not the Venue 7 that I have. Since I've gained knowledge on the unbrick process I feel more comfortable trying them.
I've installed (or tried to install) SuperSU from the Play store, but it didn't appear to help much, since I didn't have the custom recovery setup at that time. I'll work on that tonight.
Click to expand...
Click to collapse
A quick word on getting the device recognized in off mode, what worked for me was it needs to be completely powered off and nothing showing on the tablet screen then connect and bring up the device manager. Whatever shows up needs to be "Intel SoC" so change the driver to that if needed. When flashing firmware to unlock the bootloader the device's boot screen will show an "Intel Inside" logo instead of the normal "Dell" logo. I ended up running xFSTK commands in advance (they'll wait) and then running over to hook up the tablet (powered off) via USB as for some reason it'll show up and then I hear "da-Dunk" in Windows (device disconnected) after a short while which interrupts the process (same with fastboot commands). This was the unbrick process in a nutshell for me and I'm leaving it now as is (OTA'd to 4.4.4) until hopefully the supposed update to Lollipop comes around and maybe some progress is made on rooting it.
Hope this helps you!
reaper-death said:
A quick word on getting the device recognized in off mode, what worked for me was it needs to be completely powered off and nothing showing on the tablet screen then connect and bring up the device manager. Whatever shows up needs to be "Intel SoC" so change the driver to that if needed. When flashing firmware to unlock the bootloader the device's boot screen will show an "Intel Inside" logo instead of the normal "Dell" logo. I ended up running xFSTK commands in advance (they'll wait) and then running over to hook up the tablet (powered off) via USB as for some reason it'll show up and then I hear "da-Dunk" in Windows (device disconnected) after a short while which interrupts the process (same with fastboot commands). This was the unbrick process in a nutshell for me and I'm leaving it now as is (OTA'd to 4.4.4) until hopefully the supposed update to Lollipop comes around and maybe some progress is made on rooting it.
Hope this helps you!
Click to expand...
Click to collapse
I have finally settled down and got the tablet rooted. What's really odd, was Win8.1 kept losing the proper driver. I'm not sure exactly why ... but suffice it to say, I got it working. It did appear to be more stable when I hit the Vol+ and plugged in the USB, but then again it may have been a coincidence.
Open source dell
If you follow the link to dell open source, they do have a detailed PDF download for unlocking the boot loader etc. The file was too large for me to upload on XDA. I just found it today while I was researching how to root this tablet. I have not had a chance to try it yet.
http://opensource.dell.com/
That doesnt work for 3740 lte. I;ve done everything that was in PDF. OTA image should be with unlocker bootloader and root but its not. ;/
Its adb root not su big difference
Does anyone have any idea to root dell venue 7 3740 lte
The open source is for venue 7 3740 wifi
how can i hard reset this device please tell me.
Mahisasur said:
how can i hard reset this device please tell me.
Click to expand...
Click to collapse
Reset any android tbalet with ...
Setting >>>>> Backup & Reset >>>>> Factory Data Reset >>>>> Reset Tablet >>> Erase Everything
Hi, I just (fully?) bricked my Fire HD 7 4th gen.
I tried powerpoint45 Linux ISO unbrick system, but with no luck. Handshake script recognize device and run ok but when i try to run ./reader.sh it just stuck forever. I read, in that case my device is hard bricked without option to unbrick it. But I also read, there is something like "special" fastboot cable. Is there any chance to unbrick in my case?
I've no recovery and OS. Device don't react on button, I tried many combinations. The only sign of live is get Fire HD connect to computer and see in device manager there is "MT65xx Preloader"' device.
I've disasembled back cover if this helps.
Can you provide more details? What version of fire OS are you on and what exactly did you do that caused the device to brick? Without at least knowing that much people won't be able to help.
Ok, I'll start from the beginning. I originally had FireOS 5.3.1.1 and successfully downgrade my Fire HD to FireOS 4.5.3 so I can root device and flash recovery (this tutorial -> https://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351). Then i follow this tutorial to get Lollipop ROM and root -> https://forum.xda-developers.com/fire-hd/general/root-os-5-1-2-kingroot-tools-play-store-t3371824. There are steps to do when OS is less than 4.5.5 (me). Tutorial said "upgrade OS to 5.1.2". I had sideloaded file update-kindle-20.5.4.2_user_542168620.bin but then i accidentally reset system (tutorial said to do factory reset and then restart system). Thats my flow to brick Fire HD 7 4th
Did you ever find a solution to this?
Hello, all!
I've been running Nexus v4.0.5 on my Thor device for a couple of years, but I'm more than ready for an upgrade. An upgrade to CM 14.1/LineageOS, to be exact.
At this point, I have a rooted Thor device with Safestrap v4.0.1 installed; Nexus v4.0.5 is installed in the STOCK ROM slot.
From what I understand, I need to unlock my boot loader, install TWRP, and then... something. Can anyone tell me how to go about unlocking my bootloader, installing TWRP, and doing everything else necessary to get CM 14.1 installed?
Oh, and if you're wondering exactly what I've done to this device thus far, check out this guide I made a few years ago. I've done all the steps outlined therein.
Thanks!
Rvby1 said:
Hello, all!
I've been running Nexus v4.0.5 on my Thor device for a couple of years, but I'm more than ready for an upgrade. An upgrade to CM 14.1/LineageOS, to be exact.
At this point, I have a rooted Thor device with Safestrap v4.0.1 installed; Nexus v4.0.5 is installed in the STOCK ROM slot.
From what I understand, I need to unlock my boot loader, install TWRP, and then... something. Can anyone tell me how to go about unlocking my bootloader, installing TWRP, and doing everything else necessary to get CM 14.1 installed?
Oh, and if you're wondering exactly what I've done to this device thus far, check out this guide I made a few years ago. I've done all the steps outlined therein.
Thanks!
Click to expand...
Click to collapse
See below; same steps apply. You do not need to remove SafeStrap or Nexus. Note all data will be lost; be sure to backup any important content.
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post72472618
Davey126 said:
See below; same steps apply. You do not need to remove SafeStrap or Nexus. Note all data will be lost; be sure to backup any important content.
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post72472618
Click to expand...
Click to collapse
I've gotten to the point where I need to upgrade TWRP to the latest version, but I can't seem to get fastboot to recognize the TWRP file.
I'm using the command
fastboot -i 0x1949 flash recovery thor-twrp-3.1.1-1
thor-twrp-3.1.1-1 is in platform-tools, and that's the directory I'm running these commands in.
Do you know what I'm doing wrong?
Thanks!
Rvby1 said:
I've gotten to the point where I need to upgrade TWRP to the latest version, but I can't seem to get fastboot to recognize the TWRP file.
I'm using the command
fastboot -i 0x1949 flash recovery thor-twrp-3.1.1-1
thor-twrp-3.1.1-1 is in platform-tools, and that's the directory I'm running these commands in.
Do you know what I'm doing wrong?
Thanks!
Click to expand...
Click to collapse
File ID appears to be incorrect; should be: thor-twrp-3.1.1-1.img
Davey126 said:
File ID appears to be incorrect; should be: thor-twrp-3.1.1-1.img
Click to expand...
Click to collapse
Hah, yeah, that's it. Totally forgot about file extensions.
So, I've gotten TWRP flashed, and I've flashed LineageOS and GAPPS according to the instructions here. When I try to boot up, though, I get stuck on the "Welcome to your Kindle Fire HDX" screen; it gives me the option to restore data from a previous device or start fresh. Since I don't have an internet connection on my device, I can't do anything related to my prior devices. And clicking on the start fresh option crashes the start-up program and sends be back to the language selection screen (which pops up just before the "Welcome to your Kindle Fire HDX" screen).
Now, before I flashed GAPPS, I didn't have this problem. The "Welcome to your Kindle Fire HDX" screen didn't show up, so I was able to set-up the OS and use it.
I've tried wiping the device, restarting, and reflashing LineageOS and GAPPS (both in a queue and one after another).
Any idea what's going on?
Rvby1 said:
Hah, yeah, that's it. Totally forgot about file extensions.
So, I've gotten TWRP flashed, and I've flashed LineageOS and GAPPS according to the instructions here. When I try to boot up, though, I get stuck on the "Welcome to your Kindle Fire HDX" screen; it gives me the option to restore data from a previous device or start fresh. Since I don't have an internet connection on my device, I can't do anything related to my prior devices. And clicking on the start fresh option crashes the start-up program and sends be back to the language selection screen (which pops up just before the "Welcome to your Kindle Fire HDX" screen).
Now, before I flashed GAPPS, I didn't have this problem. The "Welcome to your Kindle Fire HDX" screen didn't show up, so I was able to set-up the OS and use it.
I've tried wiping the device, restarting, and reflashing LineageOS and GAPPS (both in a queue and one after another).
Any idea what's going on?
Click to expand...
Click to collapse
- insure bootloader is unlocked; unlock again if uncertain
- be sure to wipe system & data partitions before flashing LinOS
- ROM and GAaps (7.1/arm/nano) should be flashed in one operation
- if still no joy downgrade to TWRP 3.0.0-1 then try again
- as a last resort flash Fire Nexus KTU84Q (just one file), boot and allow ROM to initialize, then return to TWRP and reflash LinOS + GAaps
The above may seem a bit random but there's a reason behind each suggestion and the order in which they are presented.
Davey126 said:
- insure bootloader is unlocked; unlock again if uncertain
- be sure to wipe system & data partitions before flashing LinOS
- ROM and GAaps (7.1/arm/nano) should be flashed in one operation
- if still no joy downgrade to TWRP 3.0.0-1 then try again
- as a last resort flash Fire Nexus KTU84Q (just one file), boot and allow ROM to initialize, then return to TWRP and reflash LinOS + GAaps
The above may seem a bit random but there's a reason behind each suggestion and the order in which they are presented.
Click to expand...
Click to collapse
So, I can't seem to get fastboot to run unlock because fastboot isn't recognizing my kindle as a device. When I go to Device Manager, my Kindle is under Portable Devices, and if I browse for drivers on my computer, I only get "MTB USB Device."
Any advice?
Rvby1 said:
So, I can't seem to get fastboot to run unlock because fastboot isn't recognizing my kindle as a device. When I go to Device Manager, my Kindle is under Portable Devices, and if I browse for drivers on my computer, I only get "MTB USB Device."
Click to expand...
Click to collapse
- download drivers from this post (prequisite section); unzip as needed
- open windows device manager
- tether device in fastboot mode
- take note of entries added; delete those devices
- remove tether and reattach (might have to reboot one/both devices)
- when Windows prompts for drivers direct it to those downloaded
Davey126 said:
- download drivers from this post (prequisite section); unzip as needed
- open windows device manager
- tether device in fastboot mode
- take note of entries added; delete those devices
- remove tether and reattach (might have to reboot one/both devices)
- when Windows prompts for drivers direct it to those downloaded
Click to expand...
Click to collapse
So, I can't seem to get into fastboot mode. I don't have a factory cable, and none of the commands listed here activate fastboot mode.
What should I do?
Sorry for my ignorance!
Rvby1 said:
So, I can't seem to get into fastboot mode. I don't have a factory cable, and none of the commands listed here activate fastboot mode.
What should I do?
Sorry for my ignorance!
Click to expand...
Click to collapse
We are all ignorant about 99.99% percent of the world around us with unique 'points of light' distinguishing various individuals; never apologize for being ignorant!
Possible solution:
- boot into TWRP (turn off tablet then restart by pressing <power>+<vol-down> together; release first logo appears)
- tether device to host PC (assumes Windows)
- tap Reboot
- tab Bootloader
Above sequence should place your tablet in 'fastboot mode'. If the word 'Ready' appears on the tablet screen the correct drivers are installed on the PC. If not follow previously posted procedure for updating drivers.
Davey126 said:
We are all ignorant about 99.99% percent of the world around us with unique 'points of light' distinguishing various individuals; never apologize for being ignorant!
Possible solution:
- boot into TWRP (turn off tablet then restart by pressing <power>+<vol-down> together; release first logo appears)
- tether device to host PC (assumes Windows)
- tap Reboot
- tab Bootloader
Above sequence should place your tablet in 'fastboot mode'. If the word 'Ready' appears on the tablet screen the correct drivers are installed on the PC. If not follow previously posted procedure for updating drivers.
Click to expand...
Click to collapse
True, true! Thanks for your kind words, Davey!
And thanks for your help with this, too!
I was able to boot into fast mode, and I went through the unlock process again. With that done, I tried to reflash LineageOS and GAPPS, but I ran into the same issue I did before. So I did a bit of googling (which I didn't exactly think to do before :C), and apparently this is a known issue for CM operating systems.
Here's the fix.
Swipe down (a few hundred times) to get the notification tray. Go to settings. Turn on wifi. Problem (probably) solved.
Thanks again for all your help, Davey! I wouldn't have gotten Nexus running back in the day without ya, and I wouldn't be running LineageOS right now if you hadn't been my savior a second time around. And in addition to my thanks, sorry for not googling first! It would have saved both of us a bit of trouble, haha.
Rvby1 said:
True, true! Thanks for your kind words, Davey!
And thanks for your help with this, too!
I was able to boot into fast mode, and I went through the unlock process again. With that done, I tried to reflash LineageOS and GAPPS, but I ran into the same issue I did before. So I did a bit of googling (which I didn't exactly think to do before :C), and apparently this is a known issue for CM operating systems.
Here's the fix.
Swipe down (a few hundred times) to get the notification tray. Go to settings. Turn on wifi. Problem (probably) solved.
Thanks again for all your help, Davey! I wouldn't have gotten Nexus running back in the day without ya, and I wouldn't be running LineageOS right now if you hadn't been my savior a second time around. And in addition to my thanks, sorry for not googling first! It would have saved both of us a bit of trouble, haha.
Click to expand...
Click to collapse
Hey - glad you got it working and left a solution that hopefully will help others who encounter the same issue. Enjoy your rejuvenated device!
Hi everyone!
I've one old Asus Transform TF103C aka K010.
I find out that it's possible to update to Android 5 (and I need it for some app).
Right now, my firmware it's WW2.2.33.143 but on the Asus support page, there is the WW2.2.33.144 update that it's mandatory before trying to install the update to Lollipop.
OTA doesn't find anything and either manual download works. The manuals say that after copying the file the system will recognize the update and ask me about...obviously, this doesn't happen.
Someone know an "how to" about?
Problem solved!
How did you solve it?
How did you do it? I have a perfectly good TF103c that is useless because the version of Android is too old. It probably has enough ompff in the hardware to run the latest android if it was available.
if you have TF103C you can install Windows or Linux on it i still searching for drivers ( for wifi sound and charging solution ) ..
For now if you install Windows or Linux on it and your battery die you will need manualy charge battery ..
FullMetalGlicoz said:
Problem solved!
Click to expand...
Click to collapse
how did you solve it?
Hello,
I have an old Asus Tablet of the transformer style (docked to a keyboard) model TF103C or K010. It came along with Android 4.4.2 installed. I rooted the device sometime ago, and can verify that is rooted by using the app “Root Check”.
It is still a nice tablet, but with such an old version of android it tends to be limited and with less features, hotfixes, etc. Long story short, I was trying to install a new rom in a little bit of a hurry, used adb to boot into recovery mode (adb reboot bootloader), and used some images and scripts that I downloaded for a similar device (not exactly mine)…Then I went ahead and used scripts – which mostly used fastboot.exe adb.exe. The problem now is that nothing has changed as far as I can see, and I am no longer able to boot in the quick boot mode (using “adb reboot bootloader”): whenever I try to reboot the K010 connected to my computer in quick boot mode it simply restarts, goes to the splash screen (“Asus in search of the incredible powered by android”) with the caveat that there is a red blinking red stripe at the bottom of the splash screen, and then it simply turns the K010 off (battery charging screen)
Is there any hope to enter into the quick boot mode and fix that mess? Thanks for any insights.