I am unable to get into fastboot mode on my At&t Motivate 2. I do have OEM unlock, but when I use adb reboot fastboot, or hold the power key + up vol. It get's stuck on the screen saying => FASTBOOT mode... I am not sure what I am doing wrong (if I am). It's model number is EA211002. It stays on this screen no matter how long i leave it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Be happy, you sucessfully entered Fastboot mode. Now direct Fastboot on PC per Windows CMD and/or PowerShell what action(s) to perform.
Fastboot Commands List and Cheat Sheet with Explanation
Fastboot is a command-line tool for Android. You can execute Fastboot commands to flash and boot factory and TWRP recovery images.
technastic.com
I have the same phone does anyone have the stock firmware ?
also where did you get the fastboot drivers for it? can you sent them to me ? please @jwoegerbauer @Synaronel
@IXDevoXI
Latest ADB and Fastboot drivers you can obtain here:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
I finally figured out the whole fastboot thing with this phone lol and which one you need to be in and so forth it is the most confusing phone I’ve ever tried to root but now I’m left with that stupid dm-verity corrupt issue
Related
There is some similiar threads about this, but I still haven't found solution to my problem. I also tried to post this same problem on general: (TF300TG)For All Your Jelly Bean discussions-problems, but I thought if this was better on troubleshooting.
I got problem with recovery/fastboot on tf300tg..
Background: I haven't root my tf300tg, I got 4.2.1 (10.6.2.11) and I have unlocked bootloader from Asus support and installed APX drivers to windows 7 which works with tf300tg. (even when it's not so needed?) Also I got USB debugging on.
Problem: When I press (Vol Down + Start) to get in bootloader and try to start RCK it gives me error ("Virhe" means error in finnish).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Second Problem: If I can't use recovery I could try to use fastboot. I downloaded ADB and tried to follow instructions but there is one problem with this. I can use fastboot only when my tf300tg is on normal mode. So I can't use fastboot in recovery or in bootloader mode. I'm not sure if I should use fastboot in normal mode (don't know if it's safe?) to install TWRP 2.6.0 (for tf300tg)
Normal mode:
APX mode/Bootloader mode:
EDIT: After 5 hours of finding, I found that reason was ADB version. Fixing this problem was download: minimal adb and fastboot program to windows.
Thread for this information was: http://forum.xda-developers.com/showthread.php?t=2777730
Hi there, I've managed to root Wikipad on newest update
Works only on windows7 ( I used VMware ) unless you find a driver for windows8
1. Install driver in package
2. reboot PC
3. make sure you've got dev mode enabled with usb debugging on
4. read README.txt file
readme states:
1. power off device; RECOVERY : once off hold VOL+ and power for 5 s; pressing VOL- choose fastboot protocol pressing VOL+
2. run 'insecurebootflash.bat'
3. once rebooted go to fastboot protocol again
4. in Windows process manager kill adb and fastboot .exe
5. run 'cwmrecoveryflash.bat'
6. in developer's mode on device enable USB debugging and connect your Wikipad
10. run 'run.bat'
you're rooted
cortex69 via insecure boot made by myself
root method via motorchop (or something, can't remmeber exactly)
Click to expand...
Click to collapse
here's the link:
https://drive.google.com/file/d/0B54wdkjMEJKAVHZtaUhKVmliSDg/view
here's a proof
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If anyone wants to use it or edit it go ahead. I have only built insecure boot.img
if you're not sure about you can try just to boot to boot.img
fastboot devices
fastboot boot boot.img
fastboot reboot
If anyone who has 4.1.1 installed and rooted Wikipad and is able to download but NOT INSTALL update firmware and pull it out, I am waiting for that someone. I will gladly take over the firmware and do my best to make it customizable and rooted. Might even take a look at kernel
Hello everyone! I encountered an issue, that is new for me, and I want to know more information. I tried to flash a MTK device that now has Android 10 installed with Android 11 to test it out, out of curiosity. I installed the Treble App on my device and it shows me all the information about what image should I chose and how to flash it. But I saw a new detail that made me curious. It said to use fastbootd instead of fastboot, or during the flashing I would get the error that the partition does not exist. Now I get a doubt... I checked the Android page about the new installation of GSI images on Android 10 devices, but it doesn't explain that much. Should the fastbootd be activated by the manufacturer or do I hve to activated somehow? Because as it says on the Android page if I give the command in ADB " adb reboot bootloader" the device should open directly fastbootd without entering recovery, which my device doesn't do it... So what is the "mystery" about the new dynamic partitions and the fastbootd? Regards and thanks in advance!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
adb reboot bootloader
became obsolete starting with Android 10
You have to run
Code:
adb reboot fastboot
fastboot reboot fastboot
More info here:
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
jwoegerbauer said:
Code:
adb reboot bootloader
became obsolete starting with Android 10
You have to run
Code:
adb reboot fastboot
fastboot reboot fastboot
More info here:
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
Thank you very much for your reply! I'm gonna test it to see if it works!
Hi,
I am fairly new to flashing and rooting android devices. I managed to root my tablet a few months ago using the following sc00ter98 procedure:
Pad 11 (TB-J606F) Unlock! Magisk! RoooooT !!!
https://4pda.to/forum/index.php?showtopic=1014576&view=findpost&p=107199725 Translator from Russian: https://www.deepl.com/translator 😁🙃(y)
forum.xda-developers.com
But after that I noticed that my tablet no longer received Android updates, I wanted to manually update Android using the LMSA utility. I made a backup of my data before that so I could afford to lose everything. But once the process was finished my system won't boot anymore. In fact I am stuck on a menu at startup not knowing what to do.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the only menu I have access to. I can change the "START" with volume buttons and there are :
Restart bootloader
Recovery Mode
Power off
Boot to FFBM
Boot to QMMI
But watherver I choose, this only reboot the tablet and then go back to this menu.
I would then very much need your know-how if you please!
Thans by advance,
Jiddu
Run this command:
fastboot set_active a
It worked very well !! Big Thanks !
What was the point after my "Rescue" action with LMSA ?
AndroPlus said:
Run this command:
fastboot set_active a
Click to expand...
Click to collapse
Failed : Slot change is not allowed in Lock State. Help me
I'm on OP8T, the current status is:
- I can access fastboot
- I can access orangefox recovery (so I could boot to EDL mode, but it seems to not work)
- I can use ADB from my computer
- I can't boot any OS
The problem: I have some partitions that seems corrupted because they aren't automatically mounted when I boot to recovery. I tried to clean data and flash crdroid rom but both operations have errors (all partitions have the error "the partition can't be mounted").
Other problem: Unbrick tool doesn't work, it seems to not recognize the device and not start the flashing. I followed the guide in the official thread https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/ but when I press volume buttons the smartphone doesn't go in EDL mode (because it's not recognized by the unbrick tool). It seems to not go in EDL mode even from recovery (using the "reboot to EDL").
Is there a way to flash stock oxygen os in order to "re-build partitions"?
Try putting your PC in test mode:
Press windows key (on keyboard) + x
This brings up a menu, click on powershell (administrative). Powershell is like a command prompt.
In powershell enter this command:
bcdedit /set testsigning on
Once it says successful, reboot your PC and then try MSM tool again.
Let me know how it goes.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I solved installing the driver manullay because the phone was recognized as QHUSB_BULK and not as QDLOADER 9008
Try also to look at this thread with proper driver installation.