Related
I'd like to share some experience on hacking SHARP Android phones.
In the past I have published 102SH unlock and a tool helping users outside Japan to obtain OTA.
About rooting.
We have following preconditions.
a. Locked bootloader.
b. aboot without fastboot facilities.
c. kernel driver preventing read/write to certain partitions.
d. eMMC hardware write protections on certain blocks(including boot, recovery, system, etc.), enforced by power on write protection. This cannot be disabled unless a power off. Please refer document of eMMC datasheet.
For a or b it does not affect rooting.
For c, if we have kernel exploit it's not the case.
For d, you cannot write to protected blocks after the phone booting into Android. So even with temp root and patched kernel you can do nothing making root persist.
Someone mentioned loki. First it's an *old* LK exploit in 2013. Second boot is eMMC write protected. So it's over.
Also someone mentioned fi01's root tools. It's useless here since it's too outdated for this phone. I know every detail of the exploits inside the tool.
Therefore the two ways are all wrong.
What does the right way rooting this phone like?
a. We have to find several exploits and the final one should be kernel exploit. If I'm not going wrong, we could turn off eMMC power and set Qualcomm download magic in SMEM, then a hot reboot should bring the device into download mode with all partition writable.
b. We could try to find exploit or backdoor in sbl1/aboot.
I hope this thread becoming a serious technic discussing thread and more powerful devs joinning in.
2015.4.12
I'm going to give up on this phone.
I still don't have a 306SH SBL1 dump, too lazy to do it. The following result is based on a 305SH SBL1 dump received from someone.
Modem dump here if anyone interested.
https://www.dropbox.com/s/syulmij77qtzb7q/modem.bin.306sh.S8216.tar.xz?dl=0
And a 305SH SBL1 dump is attached.
Power on this phone with Volume Up pressed brings this device boot into FLDR mode, which can load and run code in SBL1. But unfortunately, there are complicated checks(possible RSA protected) before jumping to the code. Code will be loaded to 0x20000000 and the entry point is 0x20000050.
This will show you more on how to talk to the phone over USB cable.
Code:
lsusb -v -d 04dd:933a
The protocol is simple:
op: 1 byte(== 0x00)
size: 4 byte(BE order)
flag: 1 byte(== 0xFF causes loaded address changes to 0xf8002000 other than 0x20000000)
data: size byte(s)
sum: 1 byte(== ~sum of all bytes in from op)
Then the phone replies 010201fb which means failure and reboots, on success it will reply 010200fc.
On success, there is further checking on the outgoing data. If the check fails, the phone will go to EDL mode(aka emergency download mode, USB VID=Qualcomm and PID=9008, some guys may be familiar with it.)
Another simple operation in this mode is displaying the phone's code name.
By sending 3001ce the phone will reply 3109[8 bytes string][1 byte sum]. For my 306SH Boost Mobile variant, this string is "PB25".
Sent from my MI 4C using XDA Free mobile app
goooooooood job!
tewilove said:
I'd like to share some experience on hacking SHARP Android phones.
In the past I have published 102SH unlock and a tool helping users outside Japan to obtain OTA.
I approtiate FlowSwitch's work and he is my idol.
About rooting.
We have following preconditions.
a. Locked bootloader.
b. aboot without fastboot facilities.
c. kernel driver preventing read/write to certain partitions.
d. eMMC hardware write protections on certain blocks(including boot, recovery, system, etc.), enforced by power on write protection. This cannot be disabled unless a power off. Please refer document of eMMC datasheet.
For a or b it does not affect rooting.
For c, if we have kernel exploit it's not the case.
For d, you cannot write to protected blocks after the phone booting into Android. So even with temp root and patched kernel you can do nothing making root persist.
Someone mentioned loki. First it's an *old* LK exploit in 2013. Second boot is eMMC write protected. So it's over.
Also someone mentioned fi01's root tools. It's useless here since it's too outdated for this phone. I know every detail of the exploits inside the tool.
Therefore the two ways are all wrong.
What does the right way rooting this phone like?
a. We have to find several exploits and the final one should be kernel exploit. If I'm not going wrong, we could turn off eMMC power and set Qualcomm download magic in SMEM, then a hot reboot should bring the device into download mode with all partition writable.
b. We could try to find exploit or backdoor in sbl1/aboot.
I hope this thread becoming a serious technic discussing thread and more powerful devs joinning in.
Sent from my MI 4C using XDA Free mobile app
Click to expand...
Click to collapse
you can change DIAG by enter ##3424# and enter MSL code, it need a driver, i think if we change DIAG, we can root it from another mode
Don't spam.
Sent from my MI 4C using XDA Free mobile app
tewilove said:
Don't spam.
Sent from my MI 4C using XDA Free mobile app
Click to expand...
Click to collapse
who ?
tewilove said:
I'd like to share some experience on hacking SHARP Android phones.
In the past I have published 102SH unlock and a tool helping users outside Japan to obtain OTA.
I approtiate FlowSwitch's work and he is my idol.
About rooting.
We have following preconditions.
a. Locked bootloader.
b. aboot without fastboot facilities.
c. kernel driver preventing read/write to certain partitions.
d. eMMC hardware write protections on certain blocks(including boot, recovery, system, etc.), enforced by power on write protection. This cannot be disabled unless a power off. Please refer document of eMMC datasheet.
For a or b it does not affect rooting.
For c, if we have kernel exploit it's not the case.
For d, you cannot write to protected blocks after the phone booting into Android. So even with temp root and patched kernel you can do nothing making root persist.
Someone mentioned loki. First it's an *old* LK exploit in 2013. Second boot is eMMC write protected. So it's over.
Also someone mentioned fi01's root tools. It's useless here since it's too outdated for this phone. I know every detail of the exploits inside the tool.
Therefore the two ways are all wrong.
What does the right way rooting this phone like?
a. We have to find several exploits and the final one should be kernel exploit. If I'm not going wrong, we could turn off eMMC power and set Qualcomm download magic in SMEM, then a hot reboot should bring the device into download mode with all partition writable.
b. We could try to find exploit or backdoor in sbl1/aboot.
I hope this thread becoming a serious technic discussing thread and more powerful devs joinning in.
Sent from my MI 4C using XDA Free mobile app
Click to expand...
Click to collapse
Forgive me as ive never held a sharp android phone let alone worked on on. but i have a few questions regarding the "knowns" of this device. ive worked on many other devices and it was "known" to have a locked bootloader up until i packed teh cwm/twrp correctly and showed them they dont have a locked bootloader.
sprint is fairly open about bootloaders so why would this one be locked? is there a trend in sharp locked bootloader phones? has someone flashed a custom boot.img/recovery and been presented with a locked bootloader warning screen?
trying to find out some more information and this seemed teh most informed one.
shabbypenguin said:
Forgive me as ive never held a sharp android phone let alone worked on on. but i have a few questions regarding the "knowns" of this device. ive worked on many other devices and it was "known" to have a locked bootloader up until i packed teh cwm/twrp correctly and showed them they dont have a locked bootloader.
sprint is fairly open about bootloaders so why would this one be locked? is there a trend in sharp locked bootloader phones? has someone flashed a custom boot.img/recovery and been presented with a locked bootloader warning screen?
trying to find out some more information and this seemed teh most informed one.
Click to expand...
Click to collapse
Hey! I remember you from the galaxy avant forum. Thanks for your work on that phone. Are you interested in trying to obtain root for this phone? I am going to try and make a bounty for this phone, but I am unsure as how to do so.
Let me know if I can be of assistance to you.
Quickdraw996 said:
Hey! I remember you from the galaxy avant forum. Thanks for your work on that phone. Are you interested in trying to obtain root for this phone? I am going to try and make a bounty for this phone, but I am unsure as how to do so.
Let me know if I can be of assistance to you.
Click to expand...
Click to collapse
my buddy autoprime and i used to chat about this phone, we both wanted one when it launched but neither we willing to just get one. i was hoping the price would have died down a bit but its held strong. at any rate right now im just looking for info, ive never worked on a sharp device before and im unfamiliar with how their bootloaders run in comparison to samsung/lg
shabbypenguin said:
my buddy autoprime and i used to chat about this phone, we both wanted one when it launched but neither we willing to just get one. i was hoping the price would have died down a bit but its held strong. at any rate right now im just looking for info, ive never worked on a sharp device before and im unfamiliar with how their bootloaders run in comparison to samsung/lg
Click to expand...
Click to collapse
How would one go about figuring out such things? I have not tried to get to recovery, download mode, etc yet.
Quickdraw996 said:
How would one go about figuring out such things? I have not tried to get to recovery, download mode, etc yet.
Click to expand...
Click to collapse
@parkerlreed on reddit answered a few of my questions. in teh past if i was able to root a device i could just compile recovery and root everyone then for devices like samsung, without knowing the bootloader situation or how to flash software on this device im left a bit clueless atm.
shabbypenguin said:
@parkerlreed on reddit answered a few of my questions. in teh past if i was able to root a device i could just compile recovery and root everyone then for devices like samsung, without knowing the bootloader situation or how to flash software on this device im left a bit clueless atm.
Click to expand...
Click to collapse
How can I test to see if the bootloader is locked?
Quickdraw996 said:
How can I test to see if the bootloader is locked?
Click to expand...
Click to collapse
Without root, the only option is something fairly stupid that could render your device non-booting.
shabbypenguin said:
Without root, the only option is something fairly stupid that could render your device non-booting.
Click to expand...
Click to collapse
****, figured as much.
shabbypenguin said:
Without root, the only option is something fairly stupid that could render your device non-booting.
Click to expand...
Click to collapse
I... might be up for this. Mother is moving over to Verizon prepaid. I would then have a Moto G to use as my main phone, leaving the Aquos for testing. I'll report back if this turns out to be the case.
Well... This is interesting... The day before I get my new phone to replace my Crystal (cracked digitizer), people with Android experience show interest... Oh well... :silly:
What has made things difficult is that it does some weird stuff without any clue to us as to what it's doing.
USB in computer then Vol Up + Pwr: Phone vibrates once, the Notification LED turns White and installs something on my laptop. The install does not finish before the phone turns off roughly 15 seconds later. That install does not happen again when tried a second time.
Vol Up THEN USB in computer THEN when the LED turns Red hold Pwr: Windows audibly cues a device connect and the screen turns on displaying Charging with a battery logo. The screen then turns off and Windows audibly cues a disconnect. After the audio cue the phone vibrates for roughly 6 seconds, stops, vibrates for another 2 (vibrated for 15 seconds on other tries), and LED turns White (another audio connect cue) for about 15 seconds and turns off (audio disconnect cue).
I started a thread here: http://forum.xda-developers.com/aquos-crystal/help/download-mode-306sh-t3005531 but have not been able to recreate it again...
There is another thread where I posted where the Crystal would endlessly vibrate off and on...
I will still keep the Crystal and might stick around to do some experimental stuff to try to figure things out since it won't be my daily driver anymore. Hope this helps.
I have seen that exact behavior on mine. When I got the solid white LED, I quickly ran adb and fastboot but neither showed the device (on Linux so I don't have to worry about drivers installing). I've also seen it show up as a USB device while powered off and charging but same deal there. I think it just does that so it can register charging from Windows.
I'll try to get a writeup of all the exact behavior.
---------- Post added at 10:22 PM ---------- Previous post was at 09:56 PM ----------
Ok here it goes...
Powered off:
Unplugged:
Hold Vol Up + Power + release shortly after = White light for 15 seconds
Hold Vol Down for 5 seconds + Press and hold Power for a few seconds and continue to hold Vol down = Recovery mode
Plugged: Red light for charging. Device shows up to computer under the generic USB VID/PID ID 04dd:933a Sharp Corp.
Hold Vol Up + Power + release shortly after = same as above. adb nor fastboot -i 0x04dd see the device
Hold Vol Down for 5 seconds + Press and hold Power for a few seconds and continue to hold Vol down = Same as above. Plugging it in after entering recovery shows no devices on the computer.
"Vol Up THEN USB in computer THEN when the LED turns Red hold Pwr: " as mentioned above just seems to go into charging mode then does a small reset and goes back into charging mode.
Holding just power and continuing to hold it: Device starts to boot up, turns back off due to long holding power, and then starts to vibrate if you continue to hold power. Doesn't stop until power is released.
I am able to get my device recognized by adb/fastboot, however when I try to do an oem unlock, it says it is "waiting for device" even though it is connected and was just working fine. Any help?
Someone else says that they have possibly unlocked their bootloader via the command I typed, but no matter what I try, it will not stop "waiting for [my] device"
Quickdraw996 said:
I am able to get my device recognized by adb/fastboot, however when I try to do an oem unlock, it says it is "waiting for device" even though it is connected and was just working fine. Any help?
Someone else says that they have possibly unlocked their bootloader via the command I typed, but no matter what I try, it will not stop "waiting for [my] device"
Click to expand...
Click to collapse
Are you sure it's even seeing the device? fastboot devices would show it. Also what device do you have exactly? 04dd is the vendor code for Sharp...
parkerlreed said:
Are you sure it's even seeing the device? fastboot devices would show it. Also what device do you have exactly? 04dd is the vendor code for Sharp...
Click to expand...
Click to collapse
I have a Sharp Aquos Crystal.
Typing in "adb devices" shows my device, I have not tried typing in "fastboot devices" though, will try that later today.
I simply typed what was listed in another Sharp Aquos Crystal thread and it appears that they may have unlocked their bootloader.
Quickdraw996 said:
I have a Sharp Aquos Crystal.
Typing in "adb devices" shows my device, I have not tried typing in "fastboot devices" though, will try that later today.
I simply typed what was listed in another Sharp Aquos Crystal thread and it appears that they may have unlocked their bootloader.
Click to expand...
Click to collapse
If it's showing up under adb then it's not in fastboot mode. That's the issue here. Actually trying to figure out if there is a fastboot mode and how to get to it. And then on top of that seeing if a bootloader unlock works.
EDL (Emergency Download) Mode has been removed/ disable from MIUI 8.1 onwards and Redmi 4A later Xiaomi devices. So you can flash MIUI Fastboot ROMs on your device by using Fastboot mode only, if your bootloader is unlocked. And, we can't use Qualcomm Jig Cable(s) also now.
So, we have only one way to know Qualcomm HS-USB QDLoader 9008 port from PC. It's Test Point Method. This method will work with every MIUI ROMs (Upgrade/ Downgrade) , Locked Bootloader/ Unlocked Bootloader and also work to recover from a Dead boot device (Bricked).
While touching these two points with a metal tweezers plugin the usb cable to the phone and PC will make the phone enter edl mode. You can then release the tweezers.
Bro edl mode is not removed. It's just moved to fastboot. You can enter edl easily by "fastboot oem edl" command. Hope this helped :laugh:
rkmadotra said:
Bro edl mode is not removed. It's just moved to fastboot. You can enter edl easily by "fastboot oem edl" command. Hope this helped :laugh:
Click to expand...
Click to collapse
Thanks for the explanation, in any case tere can be situations that fastboot it's not available, hard but possible, in that case that info is helpful...
TioCareca said:
Thanks for the explanation, in any case tere can be situations that fastboot it's not available, hard but possible, in that case that info is helpful...
Click to expand...
Click to collapse
In any case, the bootloader muz be unlocked to initiate EDL using ADB fastboot..
rkmadotra said:
Bro edl mode is not removed. It's just moved to fastboot. You can enter edl easily by "fastboot oem edl" command.
Click to expand...
Click to collapse
:laugh::laugh::laugh:
what make you think they are so lame ? the result is :
failed ! remote device is locked. eom edl is not allowed
adrenochrome25 said:
:laugh::laugh::laugh:
what make you think they are so lame ? the result is :
failed ! remote device is locked. eom edl is not allowed
Click to expand...
Click to collapse
What makes you think I'm so lame as well. I have used this command and flashed my mi max 2 with fastboot rom. Tho I don't remember if bootloader was locked or unlocked. Probably it was unlocked. But still no issues as anyone can unlock thier bootloader officially.
i wasnt intended at you. it seems they forgot some ways when they first deployed the edl blocking access but with the most recent "roms" they have blocked every access way to edl when bootloader is locked : adb, fastboot & cable
the only way left is from internal pins, but we can expect they will hide them even better on new phones.
Today it's much worth to wait 72h (+30days if you just already unlocked another one today) than opening the models that have "non removable" batteries and risking to leave traces/damages
it's really a shame that xiaomi lock their phone this way, it's a very bad message at the users (fastboot is so much restricted that you cant even switch between stable&dev anymore with locked bootloader) but we still have the chance that they allow unlocking and that this unlocking is a real one allowing full control
Fastboot rom isn't needed untill we brick our device and we can't brick the device untill we have unlocked bootloader. So basically edl mode will work when it's really needed.
It doesn't work for my MM2. Got it since 4/12/17. Didn't know i need to login to mi acc to register my device, set usb debugging, developer's mode, unlock status...I had the phone for less than 2 hrs after updating to MIUI 9 from ver 8 (using the updater app) before it suddenly froze up, crashed and went into bootloop. I tried contacting xiaomi svc ctr but those clowns refused to help saying my device is china export.
I cldn't even get them to help me register my device on my mi acc using the imei & s/n info. So if anyone could offer some suggestions as to how I could ressurrect my phone, I wld be most grateful. Failing which the only avenue is to bring it to a svc ctr in China to get them fix it.
Rgds
My test points don't seem to work
I opened up my mi max2 and followed the steps to short the testpoints but my pc doesn't seem to pick up the Qualcomm device.
Anyway to trigger the thing so that the Qualcomm device can be detected?
Nike Lee said:
I opened up my mi max2 and followed the steps to short the testpoints but my pc doesn't seem to pick up the Qualcomm device.
Anyway to trigger the thing so that the Qualcomm device can be detected?
Click to expand...
Click to collapse
I managed to short the test points and got the Qualcomm HSB device on the device mgr, flashed the mi max2 with the latest global stable (V9.2.1) rom. But the phone is still stuck at the Android logo with 3 dots...
I wld have thought EDL flashing wld have wiped out everything on the phone and start afresh?
I am now thinking of formatting the entire phone and reflashing it again. How wld I do that?
Thanks for any inputs.
Hi, Does EDL with test point flashing refresh the boot partitions?
I have shorted the test points and successfully reflash the phone with the latest stable global ROMs (even back to MIUI 8.5.6) but just couldn't get the phone past the MI/Android logo after restarting it
If the boot partition files have been messed up and EDL flashing is not refreshing these files, no matter how many times I try to EDL flash the device, it's not going to help. Pls correct me if I am wrong.
Any other options I can try?
rkmadotra said:
Bro edl mode is not removed. It's just moved to fastboot. You can enter edl easily by "fastboot oem edl" command. Hope this helped :laugh:
Click to expand...
Click to collapse
bro thank u so muchhhhhhhhhhhhhhhhhhhhhhhh. it worked im so happy now...........was trying since hours....but u helped me mannn
Hello I am posting in Q&A because I'm a new XDA user, I was not allowed to post in the dev channel.
I have an Essential phone that has been working great for the past few years, no issues, and it was running standard build receiving OTA updates, until the very last update, which soft bricked the phone.
The phone was never enabled in developer mode while in Android, and now, I can't boot the phone into android at all. The only thing I can do is get into fastboot.
Fastboot state shows DEVICE STATE - locked
Any commands I try to unlock flashing, or change slots, anything at all, I get the error that the device is locked so all commands to unlock fail.
Is there any way to unlock device state from fastboot? I saw a youtube video showing a way to use a chopped USB cable to enter emergency / EDL mode for Qualcomm-based Android devices, but have not seen anyone post that this was successful with the Essential
Does anyone know of any method to be able to unlock flashing from fastboot? Or any other method to un-brick an essential? I've attempted everything, on both Mac and PC, nothing works.
On mac or PC, I can query the device in fastboot and get a response, I just can't do anything to unlock anything!!
Many thanks in advance for any suggestions!
Same problem
Same thing happened to me. Same day as you. I can get fastboot but not adb but since the device is locked I can't flash. I've only had the phone about 6 months so I contacted customer support and they offered to replace the phone.
It might be a known issue because they didn't even try to address the fact that I could get fastboot connected but not adb. They just offered to replace.
Thanks for the info! I am -at least in this case- unfortunately an early adopter. I bought two essentials at the beginning of the pre-release.
Essential support checked my serial number and said the phone was out of warranty.
Has anyone been able to force the Essential into EDL mode to recover that way? It looks like you have to latch one of the USB pins to ground, or 5V, but I haven't found any detailed instructions on how to make this work on the essential...
Thanks again
Justin
I'm sure things have changed and I'm wrong, but if you can get into the fastboot menu can't you just cycle through the options until you get to recovery and then flash an official release from Essential?
I may be thinking of LG or something but this should be possible as long as it's newer than the current software installed because it will see it as an official update and allow the flash.
Thanks but unfortunately, when I try and do that, the phone just does the same thing, it hangs forever on the initial boot screen white Android text with the circle/square logo...
That's why I've been looking into the more direct hardware version of forcing the phone into EDL mode, which is supposed to be possible with all Qualcomm based phones.
I've just not found the time yet to find a USB-C cable I'd be happy to cut in half and short the pins on! Which is why I was hoping someone might have tried this with an essential before to know if it was successful before I start trashing good cables
Thanks again for your reply!
JB
justinbaird said:
Hello I am posting in Q&A because I'm a new XDA user, I was not allowed to post in the dev channel.
I have an Essential phone that has been working great for the past few years, no issues, and it was running standard build receiving OTA updates, until the very last update, which soft bricked the phone.
The phone was never enabled in developer mode while in Android, and now, I can't boot the phone into android at all. The only thing I can do is get into fastboot.
Fastboot state shows DEVICE STATE - locked
Any commands I try to unlock flashing, or change slots, anything at all, I get the error that the device is locked so all commands to unlock fail.
Is there any way to unlock device state from fastboot? I saw a youtube video showing a way to use a chopped USB cable to enter emergency / EDL mode for Qualcomm-based Android devices, but have not seen anyone post that this was successful with the Essential
Does anyone know of any method to be able to unlock flashing from fastboot? Or any other method to un-brick an essential? I've attempted everything, on both Mac and PC, nothing works.
On mac or PC, I can query the device in fastboot and get a response, I just can't do anything to unlock anything!!
Many thanks in advance for any suggestions!
Click to expand...
Click to collapse
I have the exact same problem,
My phone is stuck on Essential log when I turned it on,
I can access Bootloader normally but the device is locked so I cannot flash it,
Recovery is corrupted, when I try to star it, it shows only the the Essential log and freeze so I can not format or wipe or sideload.
OEM Locked and unchecked
USB Debugging is unchecked
and I can't flash anything,
Did you managed to unlock it through Fastboot command or any other way ?
I wish I can just login to the recovery or unlock it so I can flash it clean,
Kindly help me if you found a way out
Thank you
Can anyone with this device provide the exact steps to unlock the bootloader. I have tried the many ways offered via google search and none seem to work. I have USB debugging and OEM unlock allowed in the device settings. I can boot into the bootloader via keys and using ADB. I've tried various key combos to get to the page (supposedly available) that allows one to switch the bootloader from locked to unlocked - no luck.
All help appreciated.
Do you mean that the command fastboot oem unlock doesn't work?
Note that: Unlocking bootloader wipes all device's data!
XDHx86 said:
Do you mean that the command fastboot oem unlock doesn't work?
Note that: Unlocking bootloader wipes all device's data!
Click to expand...
Click to collapse
Thanks for your reply and new suggestion. No that does not work either. I go to bootloader download mode, enter the command "fastboot oem unlock" and get "waiting on device". I am connected to the device as I get a response when queried "adb devices". Any other thoughts/suggestions?
[email protected] said:
Thanks for your reply and new suggestion. No that does not work either. I go to bootloader download mode, enter the command "fastboot oem unlock" and get "waiting on device". I am connected to the device as I get a response when queried "adb devices". Any other thoughts/suggestions?
Click to expand...
Click to collapse
You're supposed to boot the device to fastboot/bootloader by adb reboot bootloader not download mode.
Also to detect the device in fastboot the command is fastboot devices
Please if you're new to this stuff then don't do it. May I ask why you're trying to unlock bootloader?
XDHx86 said:
You're supposed to boot the device to fastboot/bootloader by adb reboot bootloader not download mode.
Also to detect the device in fastboot the command is fastboot devices
Please if you're new to this stuff then don't do it. May I ask why you're trying to unlock bootloader?
Click to expand...
Click to collapse
Again, thanks for your reply. I have previously installed Lineage on a Fire HD8. So not quite a newbie but everyone is new once - right? I am trying to install Lineage on this SM-T290.
The command "fastboot devices" is not returning anything but "adb devices" does which leads me to believe my hardware connections are correct. "adb reboot bootloader" does take me to the bootloader but it indicates download mode.
I suspect I am missing something simple. Your help is appreciated. Thanks
You need to enable OEM unlock and debugging mode first. And make sure the PC is allowed to debug on your phone.
Also if fastboot command doesn't return anything then most likely you need the correct device driver, you can get it from here.
Alternatively you can try this method:
Boot to download mode.
Long press volume up. This will wipe your data and automatically reboot.
After reboot you should have unlocked bootloader and OEM unlock option greyed out in the settings.
Installing custom ROM doesn't make your device better.
XDHx86 said:
You need to enable OEM unlock and debugging mode first. And make sure the PC is allowed to debug on your phone.
Also if fastboot command doesn't return anything then most likely you need the correct device driver, you can get it from here.
Alternatively you can try this method:
Boot to download mode.
Long press volume up. This will wipe your data and automatically reboot.
After reboot you should have unlocked bootloader and OEM unlock option greyed out in the settings.
Installing custom ROM doesn't make your device better.
Click to expand...
Click to collapse
Thanks but still no go.
I have enabled usb debugging and enabled OEM unlock (both done previously)
I have (had) installed latest drivers previously
adb devices returns my unit data
adb reboot bootloader command puts device in "download mode !!"
fastboot devices returns "waiting on device"
fastboot oem unlock also returns "waiting on device"
Attempted your alternative method, no go
I understand custom ROM doesn't make device better. I like the learning challenge. Hope you understand. Appreciate your help thus far and any other ideas you might have.
This is 100% driver issue, I already provided the driver link.
The device driver may be different from internet provided driver through windows device manager. Or the driver installed upon connecting the device.
XDHx86 said:
This is 100% driver issue, I already provided the driver link.
The device driver may be different from internet provided driver through windows device manager. Or the driver installed upon connecting the device.
Click to expand...
Click to collapse
Thanks. I had installed a driver from the link you supplied (there were a few options). I'll try others. I appreciate all your help!
Here's how I did it.
Enable Developer mode, usb debug, OEM unlock (you've already done those, by the sound of things).
Power the tablet OFF.
Have your USB cable plugged into the computer but NOT the tablet.
Hold the volume up AND volume down keys simultaneously, then connect the USB cable.
The tablet will vibrate and show a blue-green screen, with Warning at the top and a white triangle with an exclamation mark at the bottom. (This is different from download mode.)
From here, long-press volume up to go into device unlock mode. Follow the instructions.
Heeni said:
Here's how I did it.
Enable Developer mode, usb debug, OEM unlock (you've already done those, by the sound of things).
Power the tablet OFF.
Have your USB cable plugged into the computer but NOT the tablet.
Hold the volume up AND volume down keys simultaneously, then connect the USB cable.
The tablet will vibrate and show a blue-green screen, with Warning at the top and a white triangle with an exclamation mark at the bottom. (This is different from download mode.)
From here, long-press volume up to go into device unlock mode. Follow the instructions.
Click to expand...
Click to collapse
Thanks again but no luck. Let's start with some basics:
My device is a Galaxy Tab A SM-T290 8.0 2019 one UA core version 2.1
Android 10
When I, with power off, press both UP & DOWN volume keys simultaneously, wait a few seconds, insert the USB cable (already in computer), I get a vibration but then a circle with a lightning bolt that shows the battery charge status. The screen does not go blue-green and there is no warning.
I have tried releasing the buttons after the vibration and after I see the battery power circle. No change.
I continue to appreciate your help but feel I am missing something simple or my device is not same as yours.
Let me know if you have given up!
[email protected] said:
Thanks again but no luck. Let's start with some basics:
My device is a Galaxy Tab A SM-T290 8.0 2019 one UA core version 2.1
Android 10
When I, with power off, press both UP & DOWN volume keys simultaneously, wait a few seconds, insert the USB cable (already in computer), I get a vibration but then a circle with a lightning bolt that shows the battery charge status. The screen does not go blue-green and there is no warning.
I have tried releasing the buttons after the vibration and after I see the battery power circle. No change.
I continue to appreciate your help but feel I am missing something simple or my device is not same as yours.
Let me know if you have given up!
Click to expand...
Click to collapse
I see that your tablet has One UA core.
That may make a difference. I can't remember now where I saw it (somewhere on these forums), but I recall seeing that One UI Core is more locked down than the "ordinary" One UI version. Incidentally, I get the same response as you if I plug the tablet into a charger (not computer) while pressing both volume keys.
I'll mention at this point that I'm on the point of going back to stock and relocking the bootloader, because I've not been able to have a custom ROM or recovery and a screenlock (PIN, password, or pattern) at the same time, and no one seems to know any workaround for this. I'm starting to wonder if my tablet is somehow odd.
It's a nice piece of hardware, but a right pain to do any mods to, and Samsung's extra security "features" can cause problems.
Heeni said:
I see that your tablet has One UA core.
That may make a difference. I can't remember now where I saw it (somewhere on these forums), but I recall seeing that One UI Core is more locked down than the "ordinary" One UI version. Incidentally, I get the same response as you if I plug the tablet into a charger (not computer) while pressing both volume keys.
I'll mention at this point that I'm on the point of going back to stock and relocking the bootloader, because I've not been able to have a custom ROM or recovery and a screenlock (PIN, password, or pattern) at the same time, and no one seems to know any workaround for this. I'm starting to wonder if my tablet is somehow odd.
It's a nice piece of hardware, but a right pain to do any mods to, and Samsung's extra security "features" can cause problems.
Click to expand...
Click to collapse
Hey! Once again want to thank you for hangin' in with me on this. So, it seems we have slightly different machines. I purchased mine at COSTCO. They offer a lot of good stuff at low prices. I've noticed, however, they tweak their offerings a little bit so they can honestly say "you can't get this somewhere else." Perhaps the difference in our machines explains that.
I definitely had my unit plugged into the USB port on my computer, not a power supply.
My only purpose in attempting this was the satisfaction of doing it and having two tablets with different operating systems.
Thanks again for your help. All the best!
Here's the reference to One UI Core that I was thinking of: https://forum.xda-developers.com/t/root-for-sm-t290-tab-a-8-0-2019.3965624/post-84355183
I'm not based in North America, and the local market isn't big enough to have retailer-specific variants (or, at least, I've never heard of any), so I probably have a standard item. But from what I've read, specially locked-down items are reasonably common in the US. Which doesn't make it any less frustrating.
Heeni said:
Here's the reference to One UI Core that I was thinking of: https://forum.xda-developers.com/t/root-for-sm-t290-tab-a-8-0-2019.3965624/post-84355183
I'm not based in North America, and the local market isn't big enough to have retailer-specific variants (or, at least, I've never heard of any), so I probably have a standard item. But from what I've read, specially locked-down items are reasonably common in the US. Which doesn't make it any less frustrating.
Click to expand...
Click to collapse
I read the post and tried the extra step of holding the up volume key when the power screen came on. It also didn't work. Unless something new shows up, my quest to unlock this bootlocker is over. I'll find some other technical challenge to chase.
I had the thought of contacting Samsung to see if they would tell me how to do this. My unit is well out of warranty so why should they care? Likely they wouldn't tell me anything but .....
I'm on Denver CO. Where are you? In my work and fun travels I've had the opportunity to visit many parts of the world. Perhaps I've been to your country?
Again thanks for all your help. I could not have gotten as far as I did without it.
I'm in Auckland, New Zealand. It's a good place to live but not if you want cheap tech. Freight costs tend to be high.
Heeni said:
I'm in Auckland, New Zealand. It's a good place to live but not if you want cheap tech. Freight costs tend to be high.
Click to expand...
Click to collapse
Never been to New Zealand. On the bucket list as it seems a beautiful place to live. Been to your close neighbor Austrailia a number of times. Want to go there again to snorkel on the barrier reef. All the best!
[email protected] said:
I read the post and tried the extra step of holding the up volume key when the power screen came on. It also didn't work. Unless something new shows up, my quest to unlock this bootlocker is over. I'll find some other technical challenge to chase.
I had the thought of contacting Samsung to see if they would tell me how to do this. My unit is well out of warranty so why should they care? Likely they wouldn't tell me anything but .....
I'm on Denver CO. Where are you? In my work and fun travels I've had the opportunity to visit many parts of the world. Perhaps I've been to your country?
Again thanks for all your help. I could not have gotten as far as I did without it.
Click to expand...
Click to collapse
Try method below. It worked for me.
Root for SM-T290 (tab a 8.0 2019)
Hi guys, I just bought an SM-T290 for my wife and I was unable to find any info here about rooting it. As most Tab-A tablets "are here", can I use a guide (and twrp) for an older tablet for this newer model?
forum.xda-developers.com
bignikescar said:
Try method below. It worked for me.
Root for SM-T290 (tab a 8.0 2019)
Hi guys, I just bought an SM-T290 for my wife and I was unable to find any info here about rooting it. As most Tab-A tablets "are here", can I use a guide (and twrp) for an older tablet for this newer model?
forum.xda-developers.com
Click to expand...
Click to collapse
Holding vol up and down, with the tablet off, and plugging in the USB from PC to tablet, works. And it makes no difference which end of the cable you plug in last, so long as the buttons are already pressed before both ends are attached.
XDHx86 said:
Do you mean that the command fastboot oem unlock doesn't work?
Note that: Unlocking bootloader wipes all device's data!
Click to expand...
Click to collapse
You do not need a PC to unlock the bootloader. Turn off the device, then you will want to do Volume Up + Volume Down + USB Cable, and then Long Press Volume Up, and then press Volume Up again.
hi guys, i have a oneplus 8 pro model phone. I tried to install OTA with a program called Fastboot Enchancer. However, after the installation was complete, my phone did not turn on again. Fastboot mode, and recovery mode won't boot. It doesn't open in edl mode, which is the only one I trust and use often. When I connect it to the computer, it does not respond at all. I have done recovery with edl mod many times with MSM tool, but now I can't. Looking forward to your help and ideas.
If your device no longer ever appears as a USB device and the screen is not helpful and you've tried all the "magic" gestures like holding down 3 buttons and standing on your head, then you'll have to do something different.
This kind of thing happens when something is broken, but it's not broken enough that it realizes that it's broken.
Life is easier when it's totally broken.
Possibilities are:
1) find the EDL test points inside and connect them while reseting.
2) disable data lines or clock to the flash so that it can't read anything and knows that it can only go to EDL.
3) JTAG to fix the problem or else just wipe the SBL so that it goes to EDL.
4) Use a USB UART. Maybe it's getting as far as u-boot and you can stop it and make it go to fastboot.
x_files_X said:
hi guys, i have a oneplus 8 pro model phone. I tried to install OTA with a program called Fastboot Enchancer. However, after the installation was complete, my phone did not turn on again. Fastboot mode, and recovery mode won't boot. It doesn't open in edl mode, which is the only one I trust and use often. When I connect it to the computer, it does not respond at all. I have done recovery with edl mod many times with MSM tool, but now I can't. Looking forward to your help and ideas.
Click to expand...
Click to collapse
Sometimes you have to hold VolUp + VolDown + Power for a long time before anything happen. As far as i know we dont know about any EDL points ant the op8 and we have the button combo anyway.
SInce you post on the op8pro forum you probably have a op8pro (obviously) and since you used fastboot i guess you simly hard bricked you phone beyond repair. Your phone RAM is overvolted and dead. And i dont think JTAG or anything else next to a motherboard swap can help you here.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Renate said:
If your device no longer ever appears as a USB device and the screen is not helpful and you've tried all the "magic" gestures like holding down 3 buttons and standing on your head, then you'll have to do something different.
This kind of thing happens when something is broken, but it's not broken enough that it realizes that it's broken.
Life is easier when it's totally broken.
Possibilities are:
1) find the EDL test points inside and connect them while reseting.
2) disable data lines or clock to the flash so that it can't read anything and knows that it can only go to EDL.
3) JTAG to fix the problem or else just wipe the SBL so that it goes to EDL.
4) Use a USB UART. Maybe it's getting as far as u-boot and you can stop it and make it go to fastboot.
Click to expand...
Click to collapse
Is there any documentation of the OP8pro about the steps you mention? For example we had a discussion about edl points some days ago and the guy could not find them. And we came to the conclusion the wont help because we already have the button combo.
If the ram is overvolted and fried, which is most likely the case because anything else wont keep the phone away from EDL. Nothing can help to repair a dead ram.
I was listing 4 alternatives above.
Why do you think the RAM is dead?
EDL itself doesn't use any external RAM. There's a bit of static RAM on the chip and it uses that.