Related
some guy successfully bricked his N1 as soon as he received it about 2 months ago. When this expensive brick reached my hand, he didn't even remember what he had done... and this brick had been through many many ppl for repair, so there is no way for me to know what exactly happened during the last 2 months...
Anyway, now it:
1. light doesn't turn on when charging(not sure yet whether it is actually charing)
2. trackball + power could gets it to fastboot screen, but none of the key is working then.
3. after single press of power button when powered off, red/green/blue/white color bar and 3 droids on the screen
so , now I cannot put it in fastboot nor recovery mode, stuck.
could there be anything I can do to rescue it?
ndep said:
2. trackball + power could gets it to fastboot screen, but none of the key is working then.
Click to expand...
Click to collapse
Verify this. Enter fastboot mode (connected to usb) and then try "fastboot devices" in a command prompt. It it reports a connected device then its definitely recoverable.
The only way that a N1 get bricked (software wise) is by upgrading a wrong radio, and unfortunetly the only way to recover it (now) is by sending it to Google/HTC
more explanation
thanks i did try that...fastboot devices could not detect anything,coz it just freezes at that screen and could not enter any mode using power and voldown button.
what puzzlrs me most is that screens with multicolor bars, how on earth does that happen?
britoso said:
Verify this. Enter fastboot mode (connected to usb) and then try "fastboot devices" in a command prompt. It it reports a connected device then its definitely recoverable.
Click to expand...
Click to collapse
update: the light turns orange now and then when charging, and it is actually charging no matter the light is on or not. ( using my own nexus to verify that )
Did you plugged it to your PC?
I knew a guy who bought a ''flashing device'' capable of formating any chipset over USB, so he could do a clean install of the Firmware again. Perhaps you could find one of these devices over ebay
britoso said:
Verify this. Enter fastboot mode (connected to usb) and then try "fastboot devices" in a command prompt. It it reports a connected device then its definitely recoverable.
Click to expand...
Click to collapse
That's assuming he has the android sdk installed with the correct drivers. We don't know if the op has.
@vegetaleb: the device you mentioned is somewhat mysterious... a search on ebay with "flash device" does not give me anything related, do you have a specific name?
@C.Slater: I do have them, coz I myself own a nexus too..
should be deleted, sorry
@vegetaleb: the device you mentioned is somewhat mysterious... a search on ebay with "flash device" does not give me anything related, do you have a specific name?
@C.Slater: I do have them, coz I myself own a nexus too..
edit: isn't there an option to delete this reply? I clicked the submit button twice,sorry.
does typing fastboot devices in the cmd prompt work for your non bricked nexus?
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Does holding power+trackball bring you to fastboot?
Yes=It's not bricked
No=Kiss it goodbye, it's bricked
Simple as that
TFJ4 said:
Does holding power+trackball bring you to fastboot?
Yes=It's not bricked
No=Kiss it goodbye, it's bricked
Simple as that
Click to expand...
Click to collapse
power+trackball will bring it to fastboot screen, note just the fastboot screen, it just freezes there. All the buttons does not work, and connecting to PC using a USB cable does not show "FASTBOOT USB".
However, it could enter HBOOT with power+voldown, I noticed it searches for passdiag.zip , passdiag.nbh, etc. Could I use this builtin function to flash it? which file in this post should I use?
http://android.modaco.com/content/g...-online-kitchen-optional-root-insecure-himem/
I tried to use the first one ( http://www.romraid.com/paul/nexusone/EPE76-update-nexusone-stock-images.zip ), rename to PASSDIAG.zip , but HBOOT is still complaining about "No Image"
Perhaps it's physically damaged!
It remembers me of my boss iphone that looked perfectly normal but couldn't get a FW installed because the power part has been damaged by water(power button couldn't work at all)
Try renaming it to passimg.zip and use hboot again.
speedyls91 said:
Try renaming it to passimg.zip and use hboot again.
Click to expand...
Click to collapse
tried PASSIMG.zip , still "No Image"...
You can send it to htc for repair but the downside would be that you would never know how to deal with this kind of problem yourself...
Continue the research and keep us posted ...
i maybe wrong but i think is it case-sensitive.....meaning PASSIMG.zip would fail but passimg.zip wouldn't.....Correct me if i'm wrong please....
Case sensitive
I'm pretty sure it is case sensitive. Used to be that way with other android and HTC devices. Can't imagine it's changed.
linux is case sensitive, for sure.
i say approach from the adb/fastboot route, using usb. first, ensure that you have all the correct drivers etc for adb use (the sdk, the usb drivers, and the device specific drivers).
try ur 'adb devices' command
if adb sees it, in normal mode, you should be okay. make sure the phone has 'usb debugging' turned on in settings
Hi,
I finally found the real method to boot our Amazfit watch into fastboot. It is difficult to success at any time, but you should be able to boot fastboot directly after some try.
Here is the procedure : (I've made a video : https://www.youtube.com/watch?v=ZlXoeq30vM0 )
When you try, I advice to put the watch in its charging base, the usb Cable connected to the base, but not on the PC.
Here are the steps to go in fastboot mode :
1) press the power button 2 seconds
2) release the button et repress it again without releasing it
3) when the screen of the watch switch off, plug the usb cable.
4) when the screen turn on, count from 1 to 4. At 4 release the power button. You are now in fastboot.
If it fails, try again. It is a little difficult.
Hope this helps.
kiralex
OMG!
edit:
how the hell do i get those files inside with only wastboot mode ... FFS
2nd edit: @Neuer_User, I have the pulled mmcblk0p7 on the storage, is there any possible way of pushing it back into the system via fastboot?
Guys, that is so great! And @kiralex1995 deserves highest thanks for his finding! We need to get a stickied post for this!!
@1immortal: I'll prepare instructions for you. You will need a modified boot image and then boot this. Then you can flash system from there!
Accidentally opened fastboot with a different method.
My device didn't show up under Windows 7, after I installed adb and fastboot drivers.
So with device connected to usb I typed adb kill-server, then adb start-server and adb wait-for-device then I switched it on and off... tadaa fastboot. See picture with command lines.
MyriaBoa said:
Accidentally opened fastboot with a different method.
My device didn't show up under Windows 7, after I installed adb and fastboot drivers.
So with device connected to usb I typed adb kill-server, then adb start-server and adb wait-for-device then I switched it on and off... tadaa fastboot. See picture with command lines.
Click to expand...
Click to collapse
Interesting. See if you can make it reproducable. That would be great!
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
I wrote some unbricking instructions and a flash script to recover bricked watches with @kiralex1995 method of entering fastboot.
Hope, it helps recover the small number of watches known to be bricked through flashing.
https://forum.xda-developers.com/sm...tches/tutorial-unbrick-huami-amazfit-t3547300
Neuer_User said:
Guys, that is so great! And @kiralex1995 deserves highest thanks for his finding! We need to get a stickied post for this!!
@1immortal: I'll prepare instructions for you. You will need a modified boot image and then boot this. Then you can flash system from there!
Click to expand...
Click to collapse
You're welcome
@kiralex1995 , Thanks a Gazillion !!!
it worked and with @Neuer_User help, the watch came back to life !!!
My fastboot method was reproducable on a different machine on Windows 10 . Needed 2 attempts. Seems a question of timing. Right before it happens, the computer makes the notification sound for 'new usb device detected'.
MyriaBoa said:
My fastboot method was reproducable on a different machine on Windows 10 . Needed 2 attempts. Seems a question of timing. Right before it happens, the computer makes the notification sound for 'new usb device detected'.
Click to expand...
Click to collapse
maybe you need to explain a little bit more detailed? is the watch running and completely booted when you connect to usb and type those adb commands or is it switched off? when you turn it on, how fast do you turn it off? i didn't get it yet. please explain a bit more.
MyriaBoa said:
Accidentally opened fastboot with a different method.
My device didn't show up under Windows 7, after I installed adb and fastboot drivers.
So with device connected to usb I typed adb kill-server, then adb start-server and adb wait-for-device then I switched it on and off... tadaa fastboot. See picture with command lines.
Click to expand...
Click to collapse
It is interesting. Does it work with out th.e adb kill-server and adb start-server commands? I do not see, how they could be involved...
The adb wait-for-server might be the key. So, when the watch is started, there is some USB communication on-going. I'd love to do some testing on that. Will do that for sure, when I get the development watch
I' m not near my computer, so I can't do more tests now.
As I wrote in my first post, it wasn't my intention to open fastboot, when it accindentally happened for the first time.
The kill and start commands were given, because my Windows 7 machine pretended not to see the watch in adb (only as usb), and I thought, maybe it's detected, when I turn it on while adb is waiting for device and the usb notification 'kicks in'.
But nothing happened, so I pushed the button, to turn the watch off again.
To my surprise the result was fastboot.
I repeated the same steps today on my Windows 10 computer that always detects the watch in adb and it opened fastboot again.
Could you specify for which build or version you tried this? I (unfortunately) had the update to 1.3.5 and there seems to be no way to enter fastboot. It also is not recognised as an adb device
I have a amazfit pace but he is stucked on a update screen and when I try entring in fast boot mode he doesn´t enter and goes to update again and don´t conclude that. What can I do?
Did anybody managed to get Amazfit 2 (stratos) to fastboot using this method? thx...
EDIT: Yes, I can confirm it works! However it is really kind of tricky. Embrace yourselves!
Many thanks to you guys for finding this out, you are the best!
Thanks.
kiralex1995 said:
Hi,
I finally found the real method to boot our Amazfit watch into fastboot. It is difficult to success at any time, but you should be able to boot fastboot directly after some try.
Here is the procedure : (I've made a video : https://www.youtube.com/watch?v=ZlXoeq30vM0 )
When you try, I advice to put the watch in its charging base, the usb Cable connected to the base, but not on the PC.
Here are the steps to go in fastboot mode :
1) press the power button 2 seconds
2) release the button et repress it again without releasing it
3) when the screen of the watch switch off, plug the usb cable.
4) when the screen turn on, count from 1 to 4. At 4 release the power button. You are now in fastboot.
If it fails, try again. It is a little difficult.
Hope this helps.
kiralex
Click to expand...
Click to collapse
can confirm that this method (sort of) works for stratos as well.
i guess the important part is the 4 seconds after the light goes on. i have done it in like the 8th try.
i guess pulling the usb cable and reattaching it is not really required...
Hello my device is waiting for the logo, it is not opening.
endrancer said:
can confirm that this method (sort of) works for stratos as well.
i guess the important part is the 4 seconds after the light goes on. i have done it in like the 8th try.
i guess pulling the usb cable and reattaching it is not really required...
Click to expand...
Click to collapse
Hi all together,
yes I can confirm that plugging the cable is not neccessary. Went back to stock yesterday. Got into fastboot on first try.
I'm trying that on an actual Stratos watch way longer than 40 minutes - maybe you could help me: I have an "A1619"-model with firmware 2.3.5.0. Same for other Stratos users?
Unlike in the linked video, when I'm at step #4, the "A."-logo appears after about 2 seconds again, so if I release the power button after 4, it's already visible and bootup goes on as normal. Did you notice the same behavior with the "A."-logo before accessing fastboot?
E-lian said:
I'm trying that on an actual Stratos watch way longer than 40 minutes - maybe you could help me: I have an "A1619"-model with firmware 2.3.5.0. Same for other Stratos users?
Unlike in the linked video, when I'm at step #4, the "A."-logo appears after about 2 seconds again, so if I release the power button after 4, it's already visible and bootup goes on as normal. Did you notice the same behavior with the "A."-logo before accessing fastboot?
Click to expand...
Click to collapse
Hello
I've bricked my Pace and cannot enter fastboot.
When I try to enter fastboot I have the same behaviour on my Amazfit Pace. Have You managed some how to enter the fastboot without connection to the PC?
So I looked around here and on the interwebz to find an answer to my question before I decided to state my question to you.
I just acquired the Sony Xperia X Compact (F5321; Android 7.1.1).
In order to get TWRP on it, I consulted a lot of online guides including those described here. Of which I thought this would be the most suitable:
https://forum.xda-developers.com/x-compact/development/recovery-twrp-3-1-1-xperia-x-compact-t3640914
So after:
having adb tools and fastboot incl. drivers (also tried the minimal)
developer options -- oem unlocking -- bootloader allowed to be unlocked; and developer options -- USB debugging -- debug mode when USB is connected
checking the service *#*#7378423#*#* , which shows "bootloader unlock allow : YES"
phone connected to PC
I encounter the following problem.
While the sony stock rom it comes with is running,
via adb I am able to feed the phone the following command with the respective outcome:
adb reboot fastboot (reboots into Android, with the LED lighting briefly up in red)
adb reboot recovery (reboots into Android, with the LED lighting briefly up in red)
adb reboot bootloader (boots down, but does not boot into Android; there is only a black screen and the LED is on and stays blue)
in any of those states, if I enter an adb command there is always this output as if the phone wasn't connected or recognized or off:
error: device '(null)' not found
So I am able to communicate commands to the phone when it is running. I assume this means my drivers are all in order, right?
Also. While it is off and disconnected from the PC.
I keep the power button and the volume down button pressed, the Sony Logo comes up and after that it takes turns with a black screen as long as I keep pressed.
I keep the power button and the volume up button pressed. It is followed by one short vibration, another short one, and the three in a row. And then no further reaction.
I feel pretty dumb, can anyone help me with how to enter any of the alternative boot options? Thanks in advance!
I just don't know if there is something I am not seeing or if there is plainly something wrong with the phone. Not knowing this for sure is driving me crazy. Hopefully this is something others might learn from, as well.
____________
little edit about the text format
From your description, it seems like TWRP was not installed correctly. But don't worry, on this phone you do not have to install the recovery to use it. You can boot straight into recovery from your PC while the phone is in 'fastboot' mode. The 'fastboot' mode is what you get when you do 'adb reboot bootloader'. The screen off, blue LED is signalling that the phone is ready for fastboot commands. You can then run:
Code:
fastboot boot <recovery image file>
The phone should load and run the recovery.
Please note that adb will not see your device while it is in fastboot mode. Likewise, fastboot does not work while the phone is accessible through adb. adb support comes from the ROM, but TWRP also supports adb, so you can also use adb while in TWRP.
Rendini said:
So I looked around here and on the interwebz to find an answer to my question before I decided to state my question to you.
I just acquired the Sony Xperia X Compact (F5321; Android 7.1.1).
In order to get TWRP on it, I consulted a lot of online guides including those described here. Of which I thought this would be the most suitable:
https://forum.xda-developers.com/x-compact/development/recovery-twrp-3-1-1-xperia-x-compact-t3640914
So after:
having adb tools and fastboot incl. drivers (also tried the minimal)
developer options -- oem unlocking -- bootloader allowed to be unlocked; and developer options -- USB debugging -- debug mode when USB is connected
checking the service *#*#7378423#*#* , which shows "bootloader unlock allow : YES"
phone connected to PC
I encounter the following problem.
While the sony stock rom it comes with is running,
via adb I am able to feed the phone the following command with the respective outcome:
adb reboot fastboot (reboots into Android, with the LED lighting briefly up in red)
adb reboot recovery (reboots into Android, with the LED lighting briefly up in red)
adb reboot bootloader (boots down, but does not boot into Android; there is only a black screen and the LED is on and stays blue)
in any of those states, if I enter an adb command there is always this output as if the phone wasn't connected or recognized or off:
error: device '(null)' not found
So I am able to communicate commands to the phone when it is running. I assume this means my drivers are all in order, right?
Also. While it is off and disconnected from the PC.
I keep the power button and the volume down button pressed, the Sony Logo comes up and after that it takes turns with a black screen as long as I keep pressed.
I keep the power button and the volume up button pressed. It is followed by one short vibration, another short one, and the three in a row. And then no further reaction.
I feel pretty dumb, can anyone help me with how to enter any of the alternative boot options? Thanks in advance!
I just don't know if there is something I am not seeing or if there is plainly something wrong with the phone. Not knowing this for sure is driving me crazy. Hopefully this is something others might learn from, as well.
____________
little edit about the text format
Click to expand...
Click to collapse
Switch the phone off.
To enter fastboot mode: Hold the Volume UP and connect your phone to the USB port of your PC. The blue LED should come on and provided you have correctly installed drivers, you will be able to use fastboot commands.
To enter bootloader/flashmode: Hold Volume DOWN button and plug USB cable to your PC. Green LED should lit up and provided you have correctly installed the drivers, you will be able to use Flashtool, Emma or other software to flash firmware files.
FAILED (remote: Command not allowed)
Hey guys!
First of all, thanks for taking the time!
So, confirming how to enter bootloader/flashmode is much appreciated, since I was very much in doubt about the fact that the screen stayed off. On other devices I always had something on the screen in recovery mode and the like.
Now I know it was problem with the drivers indeed. Also appreciated, the hint that adb and fastboot work separately. While the device was recognized by adb when it was turned on, it was not in fastboot mode because of missing drivers. Finally it is being recognized and I can address the device via fastboot command.
And yet, I have the next brick wall. Any command I send via fastboot is answered by this output:
Code:
FAILED (remote: Command not allowed)
up to this point, I have not found one command that is being acknowledged and triggers another output, so I think it is a general problem. Maybe still with the drivers. Any hints would be celebrated. Anyways, in the meantime I will keep on trying until I succeed or until I get too frustrated and send it back and never try Sony devices again
not kidding XD
Rendini said:
Hey guys!
First of all, thanks for taking the time!
So, confirming how to enter bootloader/flashmode is much appreciated, since I was very much in doubt about the fact that the screen stayed off. On other devices I always had something on the screen in recovery mode and the like.
Now I know it was problem with the drivers indeed. Also appreciated, the hint that adb and fastboot work separately. While the device was recognized by adb when it was turned on, it was not in fastboot mode because of missing drivers. Finally it is being recognized and I can address the device via fastboot command.
And yet, I have the next brick wall. Any command I send via fastboot is answered by this output:
Code:
FAILED (remote: Command not allowed)
up to this point, I have not found one command that is being acknowledged and triggers another output, so I think it is a general problem. Maybe still with the drivers. Any hints would be celebrated. Anyways, in the meantime I will keep on trying until I succeed or until I get too frustrated and send it back and never try Sony devices again
not kidding XD
Click to expand...
Click to collapse
because your bootloader is not unlocked. you have set your bootloader to allow unlocking in developers options, but you need to do the actual unlock using "fastboot unlock" command. you need a unique unlock code from Sony Developers portal and keep in mind that unlocking your device irrevocably deletes DRM keys. it is advisable that you backup your DRM keys before unlocking your device.
the problem is not Sony device, but your unability to read and follow guides and get yourself informed and educated before you dive into trial and error, finaly blaming manufacturer for your own faults...
Not sure how to title this forum post, but this is the best I got. Forgive my ignorance and lack of knowledge on these topics.
I was trying to root my Axon 7 mini. After some searching to find out how to unlock the bootloader (like needing JDK, older Android SDK version to run android.bat, etc.), I finally got it to work. Ran Recovery to "apply update from SD Card" (can not remember the file right now) and was then ready to load TWRP Recovery. When I rebooted to the recovery TWRP image, it told me something failed and the phone had to be factory reset. I took my SD card out in fear of my data being deleted and "accidentally" clicked the power button. It then reloaded with a password prompt where I typed some random password (1234 because I never set a pin password nor knew what to do here), clicked submit, and then gave me some error; now my phone doesn't work.
The Problem:
- I can enter bootloader, sometimes, but can only run fastboot commands; adb device does not detect phone so can't run adb commands (always says the server is old or something and reloads daemon successfully but never finds my device regardless). Also, I don't think I can get it to run in EDL mode; MiFlash gives out errors too when trying to flash recovery images.
- Recovery mode doesn't appear or work; not sure if the MiFavor command prompts on the phone is recovery or not, but it's safe to say this no longer appears. This is also where I believe the phone bootloops. I can get the fastboot commands to flash a TWRP recovery, but it never actually enters the TWRP dashboard.
- Can not turn off the phone... I think. None of the command options that appear on-phone shut it off; however, when the screen does stay black, I'm not sure if it's in EDL mode or plainly off.
- Device Manager shows the phone as different stuff (namely Kedacom USB Device and Portable Devices/MTB USB Device). Sometimes Qualcomm appears, but it depends. More often than not, when my device does appear, there's either an error code (like Code 10, Code 43) and/or the device is grayed out.
Conclusion:
I just want to get my phone to work normally again, if possible. Currently, I locked the oem to see if fastboot commands could still work and now I'm stuck at the ZTE logo, so can't try to unlock it right now. What are the proper tools, drivers, programs, etc I need to get this phone back to normal? I've scoured the web and these forums for 2 days now with no luck and lots of either missing info or obscure info.
I bought this at Best Buy, so I'm assuming it's US Axon7 Mini version in terms of drivers (not sure if the box specifies any info that could be useful here).
Un-brick Axon 7 Mini
Dear all,
I experienced the same issue with my phone after I tried to flash it with custom ROMs and recovery.
I thought I lost it as I was not able to enter adb mode (not recognized on the PC) or even not able to enter EDL mode with the button combination so not able to do anything with it.
Only watch it boot and display the ZTE logo.
After some research, here is what I had to do to get it recovered.
First thing you need to get is an EDL cable.
I let you search on your favorite site. Mine was a Generic eDL Deep Flash Qualcomm 9008 Cable 2 in 1 for Z3 X/Octopus.
Until you receive it, make sure you have the latest Qualcomm drivers installed on your PC.
You can find it easily.
Then, connect your phone and your PC with the EDL cable.
Press the button on your EDL cable (there should be one) for a few seconds and keep it pressed.
Then, press the power button and keep it pressed for at least 20 seconds.
At this stage, you should have both buttons pressed and after some time, you should feel the phone rebooting.
After 20 seconds, release the power button.
Then, after 10 other seconds, release the EDL cable button.
At this stage, your phone screen should stay black and your phone should appear in the device manager as Qualcomm USBHUB (or somehting similar)
You are in EDL mode and should be able to perform a recovery flashing using tuliptool.
Then I followed the steps I found here:
https://forum.xda-developers.com/axon-7-mini/how-to/updating-uk-version-zte-axon-7-mini-to-t3717933
If you are still stuck, pm me.
Be patient, all will be fine,
mariegalante55 said:
Dear all,
I experienced the same issue with my phone after I tried to flash it with custom ROMs and recovery.
I thought I lost it as I was not able to enter adb mode (not recognized on the PC) or even not able to enter EDL mode with the button combination so not able to do anything with it.
Only watch it boot and display the ZTE logo.
After some research, here is what I had to do to get it recovered.
First thing you need to get is an EDL cable.
I let you search on your favorite site. Mine was a Generic eDL Deep Flash Qualcomm 9008 Cable 2 in 1 for Z3 X/Octopus.
Until you receive it, make sure you have the latest Qualcomm drivers installed on your PC.
You can find it easily.
Then, connect your phone and your PC with the EDL cable.
Press the button on your EDL cable (there should be one) for a few seconds and keep it pressed.
Then, press the power button and keep it pressed for at least 20 seconds.
At this stage, you should have both buttons pressed and after some time, you should feel the phone rebooting.
After 20 seconds, release the power button.
Then, after 10 other seconds, release the EDL cable button.
At this stage, your phone screen should stay black and your phone should appear in the device manager as Qualcomm USBHUB (or somehting similar)
You are in EDL mode and should be able to perform a recovery flashing using tuliptool.
Then I followed the steps I found here:
https://forum.xda-developers.com/axon-7-mini/how-to/updating-uk-version-zte-axon-7-mini-to-t3717933
If you are still stuck, pm me.
Be patient, all will be fine,
Click to expand...
Click to collapse
I had a feeling an EDL cable was my only option left given everything I've looked up and the multiple methods I've tried. Wanted to avoid spending money on one but doesn't look like I have a choice given the circumstances - oh well. Regardless, thank you for the response and advice. Have to wait a while, though, to get the cable and test to see if this works.
If anyone else ever ends up in the same royally screwed situation as me, getting an EDL cable - or DIY one if you wanna be cheap and are confident enough to do so - is probably your saving grace.
Kuma21 said:
I had a feeling an EDL cable was my only option left given everything I've looked up and the multiple methods I've tried. Wanted to avoid spending money on one but doesn't look like I have a choice given the circumstances - oh well. Regardless, thank you for the response and advice. Have to wait a while, though, to get the cable and test to see if this works.
If anyone else ever ends up in the same royally screwed situation as me, getting an EDL cable - or DIY one if you wanna be cheap and are confident enough to do so - is probably your saving grace.
Click to expand...
Click to collapse
K, I can get tuliptool to work and run command, but i keep getting a "Failed: Unkown Error" response everytime i run a command. Can't unlock my bootloader, nor write a recovery disk due to this error. does anyone have any idea why this happens?
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.