Newb question, and since I am new to this phone, I was wondering, has anyone been able to get into fastboot on this firmware? Because I did some digging, and I was able to get into the AP Fastboot mode.
I've made research on how this firmware is "unbreakable" and I wanted to know if I've gotten a little closer.
TheForceUnleashed said:
Newb question, and since I am new to this phone, I was wondering, has anyone been able to get into fastboot on this firmware? Because I did some digging, and I was able to get into the AP Fastboot mode.
I've made research on how this firmware is "unbreakable" and I wanted to know if I've gotten a little closer.
Click to expand...
Click to collapse
You should be able to get into fastboot on any firmware. If you can't get into fastboot, then there are bigger issues.
Thanks for the info
Related
Hey guys, was trying to unlock Atrix 4G. i was flashing an unlockable bootloader and it failed and now it boots directly to fastboot. I have NO idea what to do. It seems like im wrecked at this point. I need big help, and I need it fast. Thank you. Please help me.
Have you tried issuing the unlock commands in fastboot yet?
Runn3rLogic said:
Hey guys, was trying to unlock Atrix 4G. i was flashing an unlockable bootloader and it failed and now it boots directly to fastboot. I have NO idea what to do. It seems like im wrecked at this point. I need big help, and I need it fast. Thank you. Please help me.
Click to expand...
Click to collapse
i need more info on what phone specs are
like at&t or canada or timbucktoo
it makes a difference but at this
time i would say use fastboot mode
and a pc in cmd to flash pudding
Sent from my MB860 using Tapatalk
Is it only loading to fastboot or is it saying anything about no OS found?
Runn3rLogic said:
Hey guys, was trying to unlock Atrix 4G. i was flashing an unlockable bootloader and it failed and now it boots directly to fastboot. I have NO idea what to do. It seems like im wrecked at this point. I need big help, and I need it fast. Thank you. Please help me.
Click to expand...
Click to collapse
Sounds like the soft-brick portion of the procedure, my RSD failed (so it said) but actually went through. So you'll need to continue through with the next steps.
Open CMD, direct the directory to where you put the fastboot package on your C: (IE: 'cd c:\path\to\directory). Confirm you're in the correct path and didn't receive any errors and type in the command "fastboot oem unlock" It will reply a warning about breaking warranty, etc., and also a lengthy ID for your phone.
Now type 'fastboot oem unlock ####' where #### is your ID. And finally 'fastboot reboot'. Your phone will obviously restart and you can close out of the command prompt.
Try a linux live distro + linux sbf_flash
I had similar problems with my atrix. I ended up doing the following successfully.
1) Download a "live" linux distro. Damn small linux is a nice, fast, download. Ubuntu is fairly popular (I used Sabayon, but it doesn't really matter).
2) Boot into it.
3) Go to the International House of Pudding thread and download the linux sbf_flash program.
4) Follow the unlocking instructions.
5) Reboot back into windows and you're done.
I don't know why RSD_Lite didn't like my computer's hardware, but it didn't. I'm imagining you're in the same boat. This did get my atrix fixed, though. Make sure you flash CW romracer recover too.
Good luck.
Ok, so I have nexus 6p that has entered into the dreaded bootloop right before i was able to upload my photos from my recent vacation. I am able to get into fastboot and recovery mode and was wondering if there is a way to get my photos off of it. I have been trying to use NRT pull command but it is giving me ABD Recovery device was not found. (phone is on bootloader) and I have no idea how to fix this. Any help would be greatly appreciated.
Edit:locked bootloader and no USB Debugging
brenster21 said:
Ok, so I have nexus 6p that has entered into the dreaded bootloop right before i was able to upload my photos from my recent vacation. I am able to get into fastboot and recovery mode and was wondering if there is a way to get my photos off of it. I have been trying to use NRT pull command but it is giving me ABD Recovery device was not found. (phone is on bootloader) and I have no idea how to fix this. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Hello... What happened to your phone? Maybe it's yet time to fix your bootloop. Since you have access to recovery, it's not totally dead...
I guess you have the stock recovery?
Boot into recovery and select: apply update from ADB. From here, see if your device is recognized: ADB devices. Maybe you can try to pull your files from here. I'm not sure it will works, but worth to try!
Good luck...
5.1 said:
Hello... What happened to your phone? Maybe it's yet time to fix your bootloop. Since you have access to recovery, it's not totally dead...
I guess you have the stock recovery?
Boot into recovery and select: apply update from ADB. From here, see if your device is recognized: ADB devices. Maybe you can try to pull your files from here. I'm not sure it will works, but worth to try!
Good luck...
Click to expand...
Click to collapse
Ok so I booted into recovery mode and managed to get into apply update from ADB, now what do i? sorry i am total noob to this.
brenster21 said:
Ok so I booted into recovery mode and managed to get into apply update from ADB, now what do i? sorry i am total noob to this.
Click to expand...
Click to collapse
Try:
adb devices
Do you have a serial number displayed?
About adb pull, I'm not sure about the syntax, you'll have to find d it yourself.
Good luck...
brenster21 said:
Ok, so I have nexus 6p that has entered into the dreaded bootloop right before i was able to upload my photos from my recent vacation. I am able to get into fastboot and recovery mode and was wondering if there is a way to get my photos off of it. I have been trying to use NRT pull command but it is giving me ABD Recovery device was not found. (phone is on bootloader) and I have no idea how to fix this. Any help would be greatly appreciated.
Click to expand...
Click to collapse
BLOD is usually indicated when you have no recovery mode. Is your bootloader unlocked? Even if you are locked you can still apply an OTA and maybe fix your phone. Side loading an OTA will not wipe your data but may help recover your phone.
v12xke said:
BLOD is usually indicated when you have no recovery mode. Is your bootloader unlocked? Even if you are locked you can still apply an OTA and maybe fix your phone. Side loading an OTA will not wipe your data but may help recover your phone.
Click to expand...
Click to collapse
My bootloader is locked and I dont have usb debugging enabled, I already got the RMA approved by google so now i am just trying to save my pictures. Also I have been having little luck getting NRT working with my phone(driver issues)
brenster21 said:
My bootloader is locked and I dont have usb debugging enabled, I already got the RMA approved by google so now i am just trying to save my pictures. Also I have been having little luck getting NRT working with my phone(driver issues)
Click to expand...
Click to collapse
Locked bootloader and no usb debugging would have been useful information in your OP. Good luck to you.
v12xke said:
Locked bootloader and no usb debugging would have been useful information in your OP. Good luck to you.
Click to expand...
Click to collapse
Sorry, my last 3 phones i had usb debugging for pdanet back when I was on verizon, now on google fi i just never enabled it. Do I have any hope?
Hi all,
I've been trying for hours to root my Samsung Galaxy Tab A (SM-T510) and am completely stuck...
I have managed to unlock the bootloader, enabled developer mode, that is fine but when moving to Odin I'm getting stuck, have read all kinds of guides and can't get past the next stage.
I'm actually unclear as the the correct steps, my only reason for rooting is because I need to issue this command so that I can have the device boot automatically when the charger is connected:
Code:
fastboot oem off-mode-charge 0
Do I first use Odin to load twrp and then I install the ROM? I'm not sure of that part.
One other thing I'm noticing is that when I try and and use Odin to flash twrg is that on the tablet in red it says 'Only official released binaries are allowed to be flashed', is this relevant and how to resolve?
One thing I have successfully done is to flash back the stock ROM from Sammobile (via Odin) and that worked fine.
Would really appreciate some help on this. I do not have a preference on which ROM to load, I just need to be able to run the above command.
Thanks in advance!
There are a lot of great video tutorials on YouTube. Just search for Odin flashing tutorials and watch a recent one.
Also these types of posts should go into the General forum and not the Development one.
gavin watson said:
Hi all,
I've been trying for hours to root my Samsung Galaxy Tab A (SM-T510) and am completely stuck...
I have managed to unlock the bootloader, enabled developer mode, that is fine but when moving to Odin I'm getting stuck, have read all kinds of guides and can't get past the next stage.
I'm actually unclear as the the correct steps, my only reason for rooting is because I need to issue this command so that I can have the device boot automatically when the charger is connected:
Code:
fastboot oem off-mode-charge 0
Do I first use Odin to load twrp and then I install the ROM? I'm not sure of that part.
One other thing I'm noticing is that when I try and and use Odin to flash twrg is that on the tablet in red it says 'Only official released binaries are allowed to be flashed', is this relevant and how to resolve?
One thing I have successfully done is to flash back the stock ROM from Sammobile (via Odin) and that worked fine.
Would really appreciate some help on this. I do not have a preference on which ROM to load, I just need to be able to run the above command.
Thanks in advance!
Click to expand...
Click to collapse
Samsung devices do not support FASTBOOT nor do they have a FASTBOOT mode, So you will not be able to do this even if you root.
gavin watson said:
Hi all,
I've been trying for hours to root my Samsung Galaxy Tab A (SM-T510) and am completely stuck...
I have managed to unlock the bootloader, enabled developer mode, that is fine but when moving to Odin I'm getting stuck, have read all kinds of guides and can't get past the next stage.
I'm actually unclear as the the correct steps, my only reason for rooting is because I need to issue this command so that I can have the device boot automatically when the charger is connected:
Code:
fastboot oem off-mode-charge 0
Do I first use Odin to load twrp and then I install the ROM? I'm not sure of that part.
One other thing I'm noticing is that when I try and and use Odin to flash twrg is that on the tablet in red it says 'Only official released binaries are allowed to be flashed', is this relevant and how to resolve?
One thing I have successfully done is to flash back the stock ROM from Sammobile (via Odin) and that worked fine.
Would really appreciate some help on this. I do not have a preference on which ROM to load, I just need to be able to run the above command.
Thanks in advance!
Click to expand...
Click to collapse
RTFM!!! There was a post just yesterday in the discussion forum on how to unlock the bootloader and that has to be done FIRST. Until recently, the only Samsung tablet with locked bootloaders were those tied to a "carrier". That is no longer true. In oder to flash ANYTHING other than a stock ROM, you must first UNLOCK THE BOOTLOADER!!!!!!! And you DON"t do it with ADB or fastboot.
My OP6T had Ubuntu Touch (equivalent to Android 9) installed on it. When it broke, I tried to flash TWRP (version 3.3.1) to clear and reinstall Ubuntu Touch. For some reason it wouldn't boot, so I foolishly decided to flash TWRP onto every single partition. This only succeeded in breaking recovery mode. Following some advice I used the 6T MsmDownloadTool v4.0.58 (OOS v9.0.11), which fixed recovery mode, but not Android - it just showed the booting animation in a infinite loop (bootloop).
I've attached an image I found online showing the screen: bootloop
The issue is that I cannot flash in fastboot mode as the bootloader was relocked by MsmDownloadTool, *and* I cannot get into Android to enable OEM mode/USB debugging. I seem to have encountered a paradox where fastboot mode requires the permissions to be enabled in Android, but I can't boot to Android to enable those permissions, nor can I flash anything else to fix Android.
Is this possible to solve?
AOnePlus6TDestroyer said:
My OP6T had Ubuntu Touch (equivalent to Android 9) installed on it. When it broke, I tried to flash TWRP (version 3.3.1) to clear and reinstall Ubuntu Touch. For some reason it wouldn't boot, so I foolishly decided to flash TWRP onto every single partition. This only succeeded in breaking recovery mode. Following some advice I used the 6T MsmDownloadTool v4.0.58 (OOS v9.0.11), which fixed recovery mode, but not Android - it just showed the booting animation in a infinite loop (bootloop).
I've attached an image I found online showing the screen: bootloop
The issue is that I cannot flash in fastboot mode as the bootloader was relocked by MsmDownloadTool, *and* I cannot get into Android to enable OEM mode/USB debugging. I seem to have encountered a paradox where fastboot mode requires the permissions to be enabled in Android, but I can't boot to Android to enable those permissions, nor can I flash anything else to fix Android.
Is this possible to solve?
Click to expand...
Click to collapse
You can try booting with the twrp.img. "fastboot boot name.img" using that ADB command. If that does not work the only other option is to completely retore your phone using msmdownload tool. This method will also depend on whether you have the international version or the T-Mobile version as there are different approaches depending on the type of phone. Read and study carefully how to proceed. If the msm tool does not work I'm pretty damn sure there are no other options.
rogerrulez said:
You can try booting with the twrp.img. "fastboot boot name.img" using that ADB command. If that does not work the only other option is to completely retore your phone using msmdownload tool. This method will also depend on whether you have the international version or the T-Mobile version as there are different approaches depending on the type of phone. Read and study carefully how to proceed. If the msm tool does not work I'm pretty damn sure there are no other options.
Click to expand...
Click to collapse
He can't boot into anything with bootloader locked. This is why msm tool sucks and people should stop recommending it for any little problem.
Only option now is to use msm tool again and hopefully get something working
Even with the bootloader locked you still should be able to boot the recocery image.
I have the 6T and 7T Pro. When I messed up my 6T my only hope was the msmdownloadtool. But make sure it's the right one.
When I had to use the msm download tool it did lock the bootloader. But I was able to unloack it again from the ADB command prompt at the bootloader screen by typing fastboot oem unlock. But this can only be done if it is set in developer options.
I spent alot of time trying to figure it out but later found outthat I was using the wrong msm tool.
Good luck. I hope you get it and running again because the 6T is still a very good phone.
Brettroth said:
He can't boot into anything with bootloader locked. This is why msm tool sucks and people should stop recommending it for any little problem.
Click to expand...
Click to collapse
Are there more suitable tools for fixing a broken recovery mode? It did successfully do that.
rogerrulez said:
Even with the bootloader locked you still should be able to boot the recocery image.
Click to expand...
Click to collapse
How?
rogerrulez said:
When I had to use the msm download tool it did lock the bootloader. But I was able to unloack it again from the ADB command prompt at the bootloader screen by typing fastboot oem unlock. But this can only be done if it is set in developer options.
I spent alot of time trying to figure it out but later found outthat I was using the wrong msm tool.
Good luck. I hope you get it and running again because the 6T is still a very good phone.
Click to expand...
Click to collapse
Thank you! And yes, I tried that command but it is probably unset in the developer options (which I cannot reach, as Android isn't working anymore). I guess I'm using the incorrect version - how do you identify the correct one? I think I've used both the T-Mobile one and the other. I don't think the phone is T-Mobile, but I'm not sure how to identify whether it is or not.
It is very easy to convert a t-mobile variant to the international version. If you bought the phone used you would not know. One tell tale sign could be if you sim card holder supports either one or 2 sims. But that's not a sure way either because you can buy a replacement sim card holder. The fastet was would be to look up the IMEI # and see what variant of the 6 you have.
As for the msm tool you would needd a modified version of that tool. You first use it to downgrade to Android 9. Then you have to upgrade that verion of android 9 to a slightly higher version before you are able to fully upgrade feely to 10 than 11 if you wanted.
If you have the international version pretty much and version of the msm tool would work but a modified version would be best.
However, the first step is to find out which variant you have.
When you used the msmdownload tool which version did you use, and did it finish the job ?
If you have the t-mobile vesion there is a thread on here that gives you step by step instructions to convert from t-mobile to international along with the links to download the software. And even the modified version will know what variant you have simply by not working.
If you are able to get into the bootloader than you have a great chance of fixing your phone. Your phone is bootlooping so that tells me you can access the bootloader screen.
When I bricked mine I thought it was gone forever, I spent several days working on it but I was able to restore it. But I would never use the ubuntu rom on any phone that I care for.
When you are at this level it is very important you proceed with caution and don't just start flashing anything you can find. It will nake matters much worse.
rogerrulez said:
Even with the bootloader locked you still should be able to boot the recocery image.
Click to expand...
Click to collapse
Wasn't sure about that. If that's the case, can you also flash from twrp then?
Brettroth said:
Wasn't sure about that. If that's the case, can you also flash from twrp then?
Click to expand...
Click to collapse
No. Not without an unlocked bootloader. But booting into twrp would give you the ability to flash a ROM tho.
rogerrulez said:
No. Not without an unlocked bootloader. But booting into twrp would give you the ability to flash a ROM tho.
Click to expand...
Click to collapse
That's what I meant. Flash a ROM from twrp. Ok so if that works this guy can fix everything from there. Gonna be a hassle tho. Instead of rebooting to recovery I think you would have to shut off phone and fastboot boot back into twrp to change slots right?
Somehow I feel like that won't work but I'm not locking my bootloader to test it
rogerrulez said:
The fastet was would be to look up the IMEI # and see what variant of the 6 you have.
Click to expand...
Click to collapse
I'm afraid I can't' find it... It is dual-sim though.
rogerrulez said:
When you used the msmdownload tool which version did you use, and did it finish the job ?
Click to expand...
Click to collapse
I used a few - both T-Mobile and not. They all succeeded with (seemingly) no error, but didn't fix the bootloop.
rogerrulez said:
If you have the t-mobile vesion there is a thread on here that gives you step by step instructions to convert from t-mobile to international along with the links to download the software. And even the modified version will know what variant you have simply by not working.
Click to expand...
Click to collapse
I see, but won't that need me to be in Android to be able to run the software?
rogerrulez said:
If you are able to get into the bootloader than you have a great chance of fixing your phone. Your phone is bootlooping so that tells me you can access the bootloader screen.
Click to expand...
Click to collapse
Yup, fastboot and recovery mode work fine. The bootloader is locked though, else installing TWRP, etc. would be easy.
rogerrulez said:
When you are at this level it is very important you proceed with caution and don't just start flashing anything you can find. It will nake matters much worse.
Click to expand...
Click to collapse
Yeah...
rogerrulez said:
Even with the bootloader locked you still should be able to boot the recocery image.
Click to expand...
Click to collapse
It doesn't do it automatically. Is there another way to boot it?
Brettroth said:
Somehow I feel like that won't work but I'm not locking my bootloader to test it
Click to expand...
Click to collapse
As far as I can tell there's no way to flash TWRP without unlocking the bootloader. And there doesn't seem to be any way to do that without getting into Android. And I can't get into Android...
Someone else suggested using this tool (https://github.com/bkerler/edl) as a last-ditch attempt. I'm going to give it a try and hope for the best!
Thank you both for your suggestions.
Asus' unlock tool for M1 is dead (network error, guess they just cut the line for older models). Attached one I had in my backup from who knows how long ago, since I couldn't find any working links anymore.
Trying unlock tool for newer devices throws "Device model is not supported".
Dev. menu option for OEM Unlock is not available in neither of "official" images.
Max Pro's unlock doesn't work for this device.
So am I really stuck with Android 10 Beta release? I guess it is kind of "win" considering this release isn't completely bloated by Asus, but it would still be nice to get TWRP and Lineage on it. Not to mention I really wanted to give the Postmarket try on this device.
I'm more than willing to be lab rat if anyone wants to try.. stuff.. on my device, at this point I wouldn't even mind if it got bricked in progress.
Alright I have not given up on this, yet. I've stumbled upon post from one of the Asus' moderators on their forums:
For ZB555KL, there will no longer be any system updates and maintenance (including server).
Sorry for any inconvenience it may cause.
Click to expand...
Click to collapse
What this means is there is no official way to unlock this phone anymore, as their unlock app has nothing to communicate with.
In the same thread, another user posted this:
I dont know if you are still looking for this but after working on it for hours what you are looking for is:
in fastboot mode type:
fastboot oem enable-unlock-once
will unlock the bootloader for you until the phone is reset. Just have to do it everytime you reboot back into fastboot.
Also if you're flashing recovery, these other 2 commands may prove useful:
fastboot oem reboot-recovery
fastboot oem reboot-recovery-wipe
Cheers!
Click to expand...
Click to collapse
Indeed using this, I was able to flash recovery. Multiple actually: TWRP, stock from step 3 of the post, OrangeFox, stock again.
Why? Well, booting into any recovery leaves me hanging on black screen.
I've tried TWRP, OrangeFox. Nothing. I have found stock recovery image as well, which I have flashed. Got black screen again. BUT. Thanks to the stock recovery image I've figured out it was actually working, since after pressing some buttons randomly (kind of stupid, I know, but I though its bricked at that point anyway) I've managed to wipe data and was presented with fresh startup. I'm thinking both TWRP and OrangeFox worked as well, its the screen that doesn't want to show things for some reason while in recovery.
So if any of you got any ideas why would any recovery present me with blank screen and how should I deal with it, I'm all ears. Or eyes..