Related
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
Recently, actually the day after getting a phone, it broke, somehow, while using king root, and I need to fix it quick as possible. Is it possible to flash a new rom onto a phone using the chromebook I have. I need to know quick before I get in trouble.:crying:
H4ck3rz said:
Recently, actually the day after getting a phone, it broke, somehow, while using king root, and I need to fix it quick as possible. Is it possible to flash a new rom onto a phone using the chromebook I have. I need to know quick before I get in trouble.:crying:
Click to expand...
Click to collapse
Hello H4ck3rz,
I have recently purchased a Samsung Chromebook Plus and I also recently got a Nexus 6. I have been looking into how to use fastboot in order to root and rom my Nexus. I have found some promising info on the subject:
I first found this XDA Article that gives more of an overview on enabling ADB and Fastboot on Chrome OS
https://www.xda-developers.com/guide-to-enable-adb-and-fastboot-on-chromeos/
That article refers to an actual XDA guide (tutorial thread) at the very end:
https://forum.xda-developers.com/showthread.php?p=38232908#post38232908
I've read through them both and they seem pretty straight forward. It helps to have a bit of command line knowledge, but the commands used are clear in the instructions.
There is a section in the tutorial that links back to the Chromium Project site where you'll have to find your specific device to learn how to get into developer mode (assuming you don't already know).
NOTE: I have not tried this yet, but I am 100% sure I am going to at some point soon. Probably some time this weekend. After I go through it, I will post again to let you know how it went, if you want to wait to hear about results before you try it.
Hope this helps.
Rk.
Update: I decided I to work on this last night and from the beginning I had problems. TL;DR - adb and fastboot are already part of the developer mode system on my Chromebook Plus. So the need to follow those guides isn't necessary for me.
I was not, however, able to do anything to my Nexus 6 from my Chromebook. Since the Plus only has USB Type-C ports, I bought a USB Type-C to Micro USB cord, but the Nexus wasn't being recognized properly. adb devices returned "????????????" devices, and I didn't get anything with fastboot. I can only surmise that it is the cord, because on my windows laptop, adb and fastboot work flawlessly while my Nexus 6 was connected with the included sync cable.
I'll post again if have more info to share. Sorry I couldn't be of more help.
Rk
rkwarner2 said:
Hello H4ck3rz,
I have recently purchased a Samsung Chromebook Plus and I also recently got a Nexus 6. I have been looking into how to use fastboot in order to root and rom my Nexus. I have found some promising info on the subject:
I first found this XDA Article that gives more of an overview on enabling ADB and Fastboot on Chrome OS
https://www.xda-developers.com/guide-to-enable-adb-and-fastboot-on-chromeos/
That article refers to an actual XDA guide (tutorial thread) at the very end:
https://forum.xda-developers.com/showthread.php?p=38232908#post38232908
I've read through them both and they seem pretty straight forward. It helps to have a bit of command line knowledge, but the commands used are clear in the instructions.
There is a section in the tutorial that links back to the Chromium Project site where you'll have to find your specific device to learn how to get into developer mode (assuming you don't already know).
NOTE: I have not tried this yet, but I am 100% sure I am going to at some point soon. Probably some time this weekend. After I go through it, I will post again to let you know how it went, if you want to wait to hear about results before you try it.
Hope this helps.
Rk.
Click to expand...
Click to collapse
Thanks for this! I can't find my windows laptop and all I have to use now is a Chromebook that does not have adb or fastboot installed. I followed the links and tutorials you shared and was able to install chroot (linux), install adb and fastboot on that linux, and then finally use it to load my phone into fastboot and flash TWRP on my nexus 5. You saved me so much trouble!
i3uu said:
Thanks for this! I can't find my windows laptop and all I have to use now is a Chromebook that does not have adb or fastboot installed. I followed the links and tutorials you shared and was able to install chroot (linux), install adb and fastboot on that linux, and then finally use it to load my phone into fastboot and flash TWRP on my nexus 5. You saved me so much trouble!
Click to expand...
Click to collapse
can you please help me. when I enter 'sudo adb devices' the device is seen. but it says unauthorized. Can you help me with a a step by step write up. I want to flash Android P on to my Pixel 2 XL.
Thanks
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!
Hello everyone,
I've been tinkering with my kindle attempting to flash TWRP so I could flash other ROMs on my Kindle Fire HDX 7 (3rd generation) but I have seemed to soft brick the device after using unlock.bat from https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982/post70881555#post70881555
The unlock.bat was supposed to unlock my bootloader, but now the device won't power on. If I plug it into the windows a bunch of partitions appear and windows prompts me if I want to format the various drives. If I plug my kindle into Linux, the 7 (i think) partitions show folders various different system functions.
Someone wrote in a separate forum that it's possible to restore kindle if I using something called eMMC Raw tool, but didn't really give any clear instructions.
If anyone could help me recover my device, that would be greatly appreciated. Thank you.
For some reason I can't upload a picture of the various files in the partition.
Side note: could I theoretically put CM 12 or anything else on one of the partitions instead of the stock ROM?
Praxxer1 said:
Hello everyone,
I've been tinkering with my kindle attempting to flash TWRP so I could flash other ROMs on my Kindle Fire HDX 7 (3rd generation) but I have seemed to soft brick the device after using unlock.bat from https://forum.xda-developers.com/ki...r-firmware-t3463982/post70881555#post70881555
The unlock.bat was supposed to unlock my bootloader, but now the device won't power on. If I plug it into the windows a bunch of partitions appear and windows prompts me if I want to format the various drives. If I plug my kindle into Linux, the 7 (i think) partitions show folders various different system functions.
Someone wrote in a separate forum that it's possible to restore kindle if I using something called eMMC Raw tool, but didn't really give any clear instructions.
If anyone could help me recover my device, that would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
Unlock.bat did not "soft brick" your device as the actions it performs are totally benign. More likely you got sloppy and flashed an incompatible aboot (via dd) or erased aboot and don't know how to recover. Me thinks it is the latter. Keep reading; you'll eventually stumble on posts that describe corrective actions. I will edit this post with a link as time permits.
You do not need "eMMC Raw Tool" whatever that is.
edit: https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post75284993
Davey126 said:
Unlock.bat did not "soft brick" your device as the actions it performs are totally benign. More likely you got sloppy and flashed an incompatible aboot (via dd) or erased aboot and don't know how to recover. Me thinks it is the latter. Keep reading; you'll eventually stumble on posts that describe corrective actions. I will edit this post with a link as time permits.
You do not need "eMMC Raw Tool" whatever that is.
edit: https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post75284993
Click to expand...
Click to collapse
Ah. I wish I had seen that thread before I started the process! You may be right about the compatible boot. I couldn't find the original aboot_vuln.mbn file mentioned in the thread I was following, but managed to find aboot.img file and flashed that hoping it was the same. I could have sworn though, that the device stopped working the second after I clicked the unlock.bat file (executed outside the fastboot screen), but could be wrong.
Only problem about the thread you linked, device isn't responding to any ADB or fastboot commands, but still shows that my PC recognizes the device as a fire device.
Thank you for your time, I'll keep reading through the thread you linked.
Praxxer1 said:
Only problem about the thread you linked, device isn't responding to any ADB or fastboot commands, but still shows that my PC recognizes the device as a fire device.
Click to expand...
Click to collapse
Likely a Windows driver issue. Suggest installing Motorola Device Manager here which includes composite USB drivers that work reliably with HDX devices. Need need to run MDM; just install it. After connecting the device you will need update the driver via Windows Device Manager. Bit of hit and miss with a non-functioning device. Cables and USB ports also play a huge role, especially with fussy bootloader/fastboot communications. Avoid external hubs, USB3 ports and add-on expansion cards. Change cables, ports, etc. Good luck.
Davey126 said:
Likely a Windows driver issue. Suggest installing Motorola Device Manager here which includes composite USB drivers that work reliably with HDX devices. Need need to run MDM; just install it. After connecting the device you will need update the driver via Windows Device Manager. Bit of hit and miss with a non-functioning device. Cables and USB ports also play a huge role, especially with fussy bootloader/fastboot communications. Avoid external hubs, USB3 ports and add-on expansion cards. Change cables, ports, etc. Good luck.
Click to expand...
Click to collapse
Thanks Davey, I'll definitely give it a try. Just as a bit more information on my situation, the device manager on windows does read Fire Device "ADB composite driver". I also have it connected to the PC using a Fastboot Cable. I will give all of this a try when I get home from work today.
If I am able to communicate with the device after installing the MDM drivers, should I attempt to restore the device? Or try to unlock and flash the stock ROM?
Praxxer1 said:
Thanks Davey, I'll definitely give it a try. Just as a bit more information on my situation, the device manager on windows does read Fire Device "ADB composite driver". I also have it connected to the PC using a Fastboot Cable. I will give all of this a try when I get home from work today.
If I am able to communicate with the device after installing the MDM drivers, should I attempt to restore the device? Or try to unlock and flash the stock ROM?
Click to expand...
Click to collapse
- dump the fastboot cable (all but useless on a HDX); this isn't a generic Android device
- ADB composite drivers come in many flavors; HDX bootloader only likes a few of them
- if/when you reestablish communication first step is to restore aboot and install TWRP; unlocking and ROM installation come later
- do not attempt to reinstall stock; frustration and heartache consume those who do
- again, this is not a run-of-the-mill Android gizmo; many of the tricks you learned in kindergarden do not apply to Amazon tablets
Davey126 said:
- dump the fastboot cable (all but useless on a HDX); this isn't a generic Android device
- ADB composite drivers come in many flavors; HDX bootloader only likes a few of them
- if/when you reestablish communication first step is to restore aboot and install TWRP; unlocking and ROM installation come later
- do not attempt to reinstall stock; frustration and heartache consume those who do
- again, this is not a run-of-the-mill Android gizmo; many of the tricks you learned in kindergarden do not apply to Amazon tablets
Click to expand...
Click to collapse
Lol I feel like I'm in kindergarten tinkering with this HDX. How do I restore aboot? clearly the image I flashed with was not the correct bootloader. Should I attempt to extract aboot from the stock ROM? Or would you be able to share you tool set/point me to a working link for aboot, TWRP, and ROMs (I've looked at 4 threads so far without working links)?
UPDATE: I managed to install the ADB MOT Composite driver, but still no response to simple ADB and Fastboot commands
Thanks again
Praxxer1 said:
Lol I feel like I'm in kindergarten tinkering with this HDX. How do I restore aboot? clearly the image I flashed with was not the correct bootloader. Should I attempt to extract aboot from the stock ROM? Or would you be able to share you tool set/point me to a working link for aboot, TWRP, and ROMs (I've looked at 4 threads so far without working links)?
UPDATE: I managed to install the ADB MOT Composite driver, but still no response to simple ADB and Fastboot commands
Thanks again
Click to expand...
Click to collapse
Not uncommon. Unfortunately, there is no 'fix script' moving forward as each situation is unique. If aboot is too damaged to support basic communication it's pretty much game over for the average laymen. You will need to comb the threads for information nuggets that may apply to your situation. Or cut your losses and move on. I am not big on trying to unbrick these pups unless one well versed in low level trouble shooting. Lousy ROI; has to be a labor of love including copious time researching, trying and (likely) failing. Good luck.
@draxie - for awareness; read back a few posts for context.
1-Click is your friend
Davey126 said:
Not uncommon. Unfortunately, there is no 'fix script' moving forward as each situation is unique. If aboot is too damaged to support basic communication it's pretty much game over for the average laymen. You will need to comb the threads for information nuggets that may apply to your situation. Or cut your losses and move on. I am not big on trying to unbrick these pups unless one well versed in low level trouble shooting. Lousy ROI; has to be a labor of love including copious time researching, trying and (likely) failing. Good luck.
@draxie - for awareness; read back a few posts for context.
Click to expand...
Click to collapse
Right... the symptoms described are the normal state of affairs
after 'fastboot erase aboot' and 'unlock.bat' does no such thing.
The post linked above and/or my original "Bulk mode" post both
have the necessary instructions to recover. Alternatively, 1-Click
can handle this, assuming access to either MacOS or Linux (for
the time being).
Here was a Guide. Someone said people don't care about Me or My Work so...
This doesnt work on US model of Xperia 5 IV ( XQ-CQ62) because Sony isnt allowing bootloader unlock in USA.
Meaning you cannot get unlock codes for your phone thru sony website ,thats a crucial step in this guide.
hello, i've tried flashing the patched file onto my device but it just seems to bootloop, i'm currently running 64.1.a.0.857
viper. said:
This doesnt work on US model of Xperia 5 IV ( XQ-CQ62) because Sony isnt allowing bootloader unlock in USA.
Meaning you cannot get unlock codes for your phone thru sony website ,thats a crucial step in this guide.
Click to expand...
Click to collapse
Wow......glad I got the JP version of a new phone for once! Otherwise it's still blowing my mind that Sony itself isn't scrutinizing root like damn-near every other manufacturer as of late.
It's been more than 7 years since I rooted my last phone. Now is everything very different. Thanks for the thread, I know what I will do this weekend.
Just got my 5IV (UK) and exactly the guide I was looking for but just a simple question
My last personal Sony was the Z3C and unlocking bootloader/rooting that had drm issues with the official camera etc
Does unlocking bootloader with 5IV have any app issues, do the camera apps all work exactly as before and any other imporant Sony apps?
Will I be able to use Sony OTA updates?
If all good, I'll be unlocking and rooting this weekend, cant wait.
Thanks
rawdealer said:
It's been more than 7 years since I rooted my last phone. Now is everything very different. Thanks for the thread, I know what I will do this weekend.
Click to expand...
Click to collapse
Bruh! You and me both!! I finally rooted my Asus Zenphone 6 this past October. A bunch of reading and forums lol. Also back 7-8 years ago there were plenty of Youtube videos. Now not so much! My Zenphone 6 just died today and I am 90% sure I'll be getting the Xperia 5IV which I was eyeing since announced. I was hoping my Zenphone would have given me one more year, but alas. I'm visiting here to get the scoop on rooting this in the event I want to. I feel your pain!
smudgy636 said:
hello, i've tried flashing the patched file onto my device but it just seems to bootloop, i'm currently running 64.1.a.0.857
Click to expand...
Click to collapse
HI, not sure if you solved it, had the same issue. So, as it gave an option to do full user reset (or something like that) I chose it. It then rebooted and I was back into the phone with the initial setup again.
I then re-installed the latest magisk app and it showed that magisk/root is installed.
As a test, I then installed f-droid and installed Adaway. I chose to configure in root mode,
the 'grant access' dialogue popped up and boom, root access provided.
Btw, if you do want to install Adaway too, enable systemless host in magisk preferences.
Trying it now... It's a bit of a hassle, but that's on Sony.
Edit: yep, works an absolute treat. One little remark: Wiping after installing Magisk isn't neccesary, afaict. Perhaps make it optional "in case of weird problems".
thany2 said:
Trying it now... It's a bit of a hassle, but that's on Sony.
Edit: yep, works an absolute treat. One little remark: Wiping after installing Magisk isn't neccesary, afaict. Perhaps make it optional "in case of weird problems".
Click to expand...
Click to collapse
So, no need to wipe all user data or?
how to hide root from GooglePay?
So I'm getting stuck on the OEM unlock bit. After entering the command I get this:
...
FAILED (remote: Command not supported in default implementation)
finished. total time: 0.004s
Click to expand...
Click to collapse
Any Ideas?
hasztagL said:
how to hide root from GooglePay?
Click to expand...
Click to collapse
Why would you need to? Play works perfectly fine with non-hidden root.
Either way, try enabling Zygisk in the Magisk manager. You might also have to check to enforce the DenyList, and check the Play app on the DenyList.
But really it's not neccesary in my experience. The only app that refuses to work properly is my banking app. In their infinite stupidity they demote rooted users to a PIN code instead of fingerprint, even though on a rooted device, the fingerprint is still more secure. But I digress, sorry.
Skv012a said:
So, no need to wipe all user data or?
Click to expand...
Click to collapse
I guess it was a catchall. Maybe if you've already been tinkering a lot, it might be a good idea to "start over", since Magisk can completely fluff up you phone if it's being interfered with. However, my phone was completely stock, other than being bootloader-unlocked, so in my case the answer is no, not needed.
No promises though. Just give it a go. Do have a backup ready.
thany2 said:
Why would you need to? Play works perfectly fine with non-hidden root.
Either way, try enabling Zygisk in the Magisk manager. You might also have to check to enforce the DenyList, and check the Play app on the DenyList.
But really it's not neccesary in my experience. The only app that refuses to work properly is my banking app. In their infinite stupidity they demote rooted users to a PIN code instead of fingerprint, even though on a rooted device, the fingerprint is still more secure. But I digress, sorry.
Click to expand...
Click to collapse
Google Wallet not work with root. With DenyList still not work.
Matrixclonk said:
So I'm getting stuck on the OEM unlock bit. After entering the command I get this:
Any Ideas?
Click to expand...
Click to collapse
It looks like you started fastboot mode. You should enter bootloader mode for the fastboot command for some reason
Also I had a problem in bootloader mode and had to manually update the driver in Windows for the phone.
When I was in bootloader, the adb devices and fastboot devices commands did not return anything, meaning the phone wasn't found.
So if someone else's phone isn't recognized in fastboot/bootloader mode you could try installing the driver manually like so:
Open the Device Manager in Windows and under under Other devices (probably), there will be a device named Android with a question mark (meaning no driver or problem with it.)
Then right click on it -> Update driver -> Browse my computer for drivers -> Let me pick from a list of available drivers... (you should have installed the drivers from windows (in file explorer, right click, install on the .inf file))
Then there under Android, from Google I had the ADB Interface driver which I selected and Installed it forcefully.
And after that fastboot comand worked normally.
alexdo said:
It looks like you started fastboot mode. You should enter bootloader mode for the fastboot command for some reason
Also I had a problem in bootloader mode and had to manually update the driver in Windows for the phone.
When I was in bootloader, the adb devices and fastboot devices commands did not return anything, meaning the phone wasn't found.
So if someone else's phone isn't recognized in fastboot/bootloader mode you could try installing the driver manually like so:
Open the Device Manager in Windows and under under Other devices (probably), there will be a device named Android with a question mark (meaning no driver or problem with it.)
Then right click on it -> Update driver -> Browse my computer for drivers -> Let me pick from a list of available drivers... (you should have installed the drivers from windows (in file explorer, right click, install on the .inf file))
Then there under Android, from Google I had the ADB Interface driver which I selected and Installed it forcefully.
And after that fastboot comand worked normally.
Click to expand...
Click to collapse
Thanks man, I was in fastboot because when I went to bootloader I always got the message waiting for device. Also weird I had to reinstall the driver each time i went into bootloader :S
@Miustone Hey. I rooted my phone following your guide and I have a question.
Sony have released an update was wodnering if I flash the latest update, will my settings/data be intact? Apparaently the update is only small, just wish I could flash that...not the whole 3.3GB
Thanks
After getting said from some Stock Tree ROM Cookers that People wont miss Me around Xperias (and that i havent developed that much), i just decided to take My Work offline and to remove also My Guides. Sorry for everyone who apprecciated My Contributions but You will get Stock FW based ROMs instead (one Day)! It wont have the quality or safeness of a good old SODP based ROM (since they refuse to work with it on a disrespectful way) but hope You will be fine with it somehow!
All the Best for the future,
Miu
Miustone said:
After getting said from some Stock Tree ROM Cookers that People wont miss Me around Xperias (and that i havent developed that much), i just decided to take My Work offline and to remove also My Guides. Sorry for everyone who apprecciated My Contributions but You will get Stock FW based ROMs instead (one Day)! It wont have the quality or safeness of a good old SODP based ROM (since they refuse to work with it on a disrespectful way) but hope You will be fine with it somehow!
All the Best for the future,
Miu
Click to expand...
Click to collapse
sad. i love your work.