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
Related
Hello,
I was asked to forward my problem here so here it goes:
Not a long time ago I bought Asus ME302C FHD 10 and tried to root it. I followed a guide but I can't paste link just now.
Anyhow, the guide told me to flash rooted system image. I did every step correctly except that after i rebooted it, my device got stuck on logo screen, sometimes saying "no command".
I would like to undo that by getting unrooted system image for my device or rather get a working rooted system image. I am not sure about other possibilities as I am not experienced in android rooting or anything related. I do have fastboot up and working.
Thank you a lot in advance.
Edit: I figured out that Asus website has factory system images, however I don't really know which one to use because they all are for different countries and I am not sure what device is mine. Is there a way to check parameters of your device without booting it?
Edit2: I messed with the device more and found out that adb doesn't recognize device, as in, running 'adb devices' nothing gets listed. However, 'fastboot devices' does output my device, not sure where the problem is. Also, firmwares listed on asus website are zipped files and I don't know how to flash them. I tried 'fastboot flash system zippedfile.zip' but it would give me an error.
Solved
After few sleepless nights and loads of browser tabs opened I finally managed to fix my device.
All I needed was to use a different SKU firmware from Asus website. Now I can finally boot it thanks to XDA developers team and their useful information on the forums.
I'll try to get as straight tot he point as possible.
Been using my Mobile one touch pix 7 for a little over a year and always installed Ota updates. Well I rooted the tablet not too long ago, forgot which method I used, but was working fine.
an Ota update came through and totally forgot it was rooted, and tried to install it, at which point the whole tablet got bricked.
It ended up in recovery, and I selected due to failure, to format and wipe the data.
Anyhow, The unit will stay at the boot screen for a while then show command error and then show the recovery screen, my only options are:
reboot
update from sd card
update via adb
update via memory
reboot Bootloader
power off
Well I've tried updating by downloading system images via adb, they return a verification error.
I've tried using adb side load to try to install an Ota update file I found for it, returns a verification error.
I cannot get into download mode, fast boot mode I think does not work as windows reports 3 android devices, but the mobile update software cannot see anything, and fast boot gets stuck at waiting for devices.
I suspect the tablet is for lack of a better description totally bricked and just a paperweight.
I am at a loss of what to try from this point. I'm sure wiping the data after the failed update killed it completely but not sure.
Anyone have any guidance here? I've downloaded a few images from the web I found that say they are for this tablet model, but still getting verification error.
Is there any flashing software I can get that may be able to access the tablet or can I copy a file to the scared and have it try to run an update from there. I don't care if it is rooted or not, just want to get it usable again.
I can run Mac OS, windows 10, windows 7, windows xp, or even have no issue getting a linux version going, whatever will work best for this I can use it. windows 10 I was able to manually add the drivers but windows 7 is not letting me do it the same way. I can connect via adb sideload only, no other adb functions seem to work.
I'm not a total news when it comes to custom rooms, as I have done it with another tablet, and an android car radio, but those were pretty straight forward and bootable so never ran into a brick issue yet.
I have a feeling this is toast and I hope that is not the case.
If anyone here can help out, I would appreciate it.
Thanks again....
Need help here to. Been searching with no luck. Any my issue is.
Rooted kingroot, flashed twrp with flashify and now I'm stuck on twrp. Been searching for any custom stock rom. I forgot to unlock the bootloader but I did enable usb debugging (i didn't see any oem options).
Any k 28532Jonsunf of help would be greatly appreciated.
This sorta happen to me. I rooted pixi 7 with kingroot, and was able to delete a lot of bloatware. However, when I was using lucky patcher it pretty much messed up the play store. But it was fine. I could download stuff through the Internet. But sooner or later I needed to fix it. Tryed a lot of ways but it didn't help. So I factory reset the tabletand now im stuck at the Setup Wizard. It just won't let me let me through. I thought its was over, but then I get a message saying there is an update available. So I download it and installed it. But all I get at the end is error. So now I need to flash it with stock. I tried the img. too, but it doesnt show up in the recover menu. If you found a solution please tell me
Can anyoonneee help me find a good Custom Rom for the alcatel one touch pixi 7 (9006W)? Sucks that there's not much info for this device (probably cause the device sucks lol) I'm running on lollipop 5.0.2 and am not able to get OTA update due to rooting. Unrooting didn't help. It seems only answer is custom rom but don't want to risk bricking it as I don't have a computer at home. Also, I am new to this so if anyone can share some insight, I'd be eternally grateful
P.s
It's a t mobile device but I only use it on wifi.
Am using kingroot.
Have never installed a custom rom
****ing device is 8 gigs. 1 gig Ram.
Is it possible to get Nougat?
Help meeee lol
So I got a cheap android tablet and I wanted to root it. I was successful so I decided to install TWRP. I searched for my specific model and found an image on a german forum. I downloaded and flashed it and it got stuck in a reboot loop. So I looked at the image and it was for the QV1030. I tried to get it into recovery but couldn't. Many sources told me to hold Vol Up and Lock, and I tried this and more. Nothing would make it enter recovery mode. Then I read about SP Flash Tool and found the stock rom for the tablet and decided I would try to flash that. It kept coming up with an error, and every source online told me to format the flash except for the bootloader and then I could flash it. So I did. Now it doesn't show anything on screen, and SP Flash Tool comes up with error 6045. But it does show up in device manager under com ports as, "MediaTek USB Port" so I think I can still do something about it. I don't have any backups. I don't know what I'm doing. I require assistance please.
So I reflashed the entire backup and it come up with no error. The logo comes up and it plays the chime. The logo does this little shimmer effect and once it gets to this screen, it shimmers indefinitely. If I plug it in, it begins installing a driver and then stops part way through.
drsinclair said:
So I reflashed the entire backup and it come up with no error. The logo comes up and it plays the chime. The logo does this little shimmer effect and once it gets to this screen, it shimmers indefinitely. If I plug it in, it begins installing a driver and then stops part way through.
Click to expand...
Click to collapse
I left it for about 5 minutes and it finished the driver. I thought it froze but I was wrong. It shows up now on device manager under Portable Devices as, "MTP USB Device". I tried to see if it was listed as a device by ADB. It is not. Lets just say I've already learned a thing or two about this stuff. Good thing I did it on an 80 dollar chinese tablet and not my HTC One M9
drsinclair said:
I left it for about 5 minutes and it finished the driver. I thought it froze but I was wrong. It shows up now on device manager under Portable Devices as, "MTP USB Device". I tried to see if it was listed as a device by ADB. It is not. Lets just say I've already learned a thing or two about this stuff. Good thing I did it on an 80 dollar chinese tablet and not my HTC One M9
Click to expand...
Click to collapse
I got it to work again mostly. So I realized that I wasn't flashing the whole backup. Some things didn't have a path and I had to set it manualy. Now it has CFW for some reason, but I reset it and it works now. The only thing is WiFi is not turning on. Any ideas about that?
drsinclair said:
I got it to work again mostly. So I realized that I wasn't flashing the whole backup. Some things didn't have a path and I had to set it manualy. Now it has CFW for some reason, but I reset it and it works now. The only thing is WiFi is not turning on. Any ideas about that?
Click to expand...
Click to collapse
I actually want to upgrade this from Android 4.2.2 to a more recent version. Do you guys have any ideas about that?
So I've come to the conclusion that while the device is no longer bricked, the current installation is written over the old one and things are conflicting. I know this because I looked through the cache and found filenames referring to apps I had installed before breaking it. So would the solution be to wipe the system partition and reflash the system.img so everything is fresh? Or does the problem lie elsewhere.
I formated the system partition, used SP Flasher to flash system.img and then did a factory reset. The issue has still not been solved. And now that I have done that, I don't have root access anymore. Framaroot says it was successful and I restart and check root explorer on ES File Explorer and it doesn't work.
I gained root access using a different method. However the WiFi still doesn't work. I think it may be that the mac address information was from the backup I flashed from the internet, and therefore doesn't match. I found a guide that tells me how to hex edit a file and put in my real mac address, but it's unavailable under wifi. I don't have the sticker on the back that says it either. How else can I find it?
Turns out the mac address can be anything. I used SN Write tool and an AB DB for my chipset and it still didn't solve the problem. I have no idea what to do. Can anyone help me?
I fixed the issue by grabbing a different backup from some russian website and flashing the system.img and secro.img to it. It now works fine 100%. Thanks
help - link
drsinclair said:
I fixed the issue by grabbing a different backup from some russian website and flashing the system.img and secro.img to it. It now works fine 100%. Thanks
Click to expand...
Click to collapse
Hey man! I have the same problems with my QV 830. Can you give me the link for system.img and secro.img, please?
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!
Here you go:
https://1drv.ms/u/s!AshkuG2cY1T0xPZArSsy6iO1e_UnPw
This is a zip file with all the tools and files you need and instructions on how to use them.
What it covers:
Restoring bricked device (as long as download mode still works)
Unlocking bootloader (firmware dependent)
Rooting (any firmware)
Installing a custom recovery (any firmware)
Installing a custom ROM (any firmware)
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
robles4242 said:
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
Click to expand...
Click to collapse
Did you read my guide? You can't flash TWRP unless you successfully unlocked your bootloader with Casual, otherwise you are limited to SafeStrap. Also you can't restore with Kies, you have to use Odin and the files I've included to restore.
yambag said:
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
Click to expand...
Click to collapse
Nice to see people still looking for something like this, so my guide wasn't for nothing!
I was geeked to see this!! but then i got "This item might not exist or is no longer available"
I take it back.. i let it sit on the "failed" page for like 2 min, and randomly it popped up with a download!
Well the auto bootloader didn't work, so now i'm at the root section. However i'm getting an error where ADB isn't detecting my phone. USB debug is on, and i'm definitely in media mode and not installer. The phone shows up in windows and looks good, but adb doesnt detect. I opened command prompt and ran adb /? and found adb devices -l, and it reports "list of devices" and theres nothing in the list. I can't imagine why it's not seeing it. I tried turning on and off debug mode, switching from camera mode to media, changing usb ports. still nothing comes up, but windows sees it fine. grrrr
*edit, well since we can't delete posts i'll leave this here, because i have to. But what i did was re-open the "no you verizon" and it showed DISCONNECTED also. I changed usb ports like 3 times, turned usb debug on and off, changed from installer mode, to camera, to media mode, restarted the phone and the computer multiple times.. and then it just all of a sudden was detected again. So i went with it and it seems to have worked.
-it took 3 times to actually work, you noted it may take multiples, and it sure did. I ran it through the command prompt so i could read the text, and it took 5 times longer and reported much more stuff when it actually worked.
-final edit: if you can't unlock your bootloader, you're still stuck with ditto or alliance from 2014, and lots of apps won't update on android that old. So if you thought this guide was some holy grail, it is not. But still useful if you need the assist, so thanks to the author.
Hi, total noob here, I just bought Verizon note 2 at a yard sale but there is a pin I don't know. When I went to do a factory reset it booted into TWRP, so I am assuming is rooted. Do I need to be able to get into the phone to use your tools? I know nothing about TWRP. I would like to install a newer Android version and unlock it so I can use TMobile. Thanks
Something wrong...
when i try to load this file from the packages folder i get an error message:
"md5 error! Binary is invalid"
none of the other three works for me. they all come back ailed.
any suggestions?
awesome! thanks for posting this, just found my old note 2 and want to get it up and running again for the kids.
Kudos!
Used this to get my Note 2 up and going again temporarily until the Pixel 4a release...
NOTE: I had strange issues with Odin on my modern X570 board (USB 3.2 Gen 2) where I did not receive any errors, yet the process would randomly seem to time out. Sometimes I'd get stuck at flashing boot.img, sometimes it would hang up at the start, once I got to flashing system.img and it seemed to hang....
Used an older PC circa 2013, no issues! Not the first time I've had issues with this newer motherboard and older USB flashing interfaces; had the same issue on my Note 8 (RIP) as well.
excited to try this.
I'm on some rooted 4.4.2 stock-looking rom. Recovery doesn't look custom.
Hoping to be able to install a working Oreo or Pie ROM
great post, bought a couple of these for almost nothing and am having fun playing with them. sadly they are both 4.4.2 but its great fun anyway.
SilentNightx said:
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Click to expand...
Click to collapse
Thank you for sharing. Always difficult to find those tools after a few years!!!