Database Users

Get Fastboot mode on Indian Model

Hey Everyone!
Its not new that there is quite some chaos regarding the fastboot mode on our device. Though some could access it, others could not. All that would happen when I tried to reboot into bootloader was that it would get stuck on the boot logo. Many said that the bootlogo itself was the fastboot mode. However lsusb on my linux term would not recognize anything attached. So I was quite sure there was some issue. Recently when I was having a chat with Nori, I could confirm that the same. It so happens that when he boots into fastboot mode, there appeared a tiny text at the left bottom of the screen would appear saying the device was in fastboot mode.
A little bit of research and experimentation, I figured out that there was an issue in the appsboot image on the Indian version. So, I flashed the Taiwan version of the aboot on my device and VOILA! I had fastboot mode! Here is how you can get it.
BEFORE I GO ANY FURTHER, I MUST WARN YOU THAT THIS IS HIGHLY RISKY IF DONE WRONG! THERE IS A RISK OF HARD BRICKING YOUR DEVICE! AND I AM NOT RESPONSIBLE FOR WHATSOEVER THAT HAPPENS TO YOUR DEVICE.
1) Head over to http://140.115.126.139:808/gplus_e7/E7_0301_v5832_IMG/ or here
2) Download the aboot.img and save it to the root of your sdcard.
3) Open up a terminal emulator or adb shell and type in the following code.
Code:
su
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
4) Thats it.. Now reboot into bootloader using any rebooter or using adb and you should see something like this
{
"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"
}
(sorry for all the dust.. should have viped it I guess.. well, atleast shows how good the camera is..)
Good Luck!!

hi.
my device goes to fastboot mode but fastboot command is not working on it.. what can be pb..?
\Desktop\GenerelMobile_Elite>fastboot oem unlock
< waiting for device >
pc detects is "Android Composite ADB Interface" in the device manager..
adb reboot-bootloader is working or wol down + power on..device goes to fastboot mode..
but not working on root directory..
Code:
[email protected]_MOBILE:/ # fastboot reboot
fastboot reboot
[B]sh: fastboot: not found[/B]
127|[email protected]_MOBILE:/ #

this should be closed this does not work

gaganpattanayak said:
this should be closed this does not work
Click to expand...
Click to collapse
It works fine for me. Have you followed the instructions properly?

Yes it goes to the screen and then if you give a fastboot command something seems to happen but nothing happens

HI , my phone gionee e7 is in fastboot mode..I dont know how it got into this mode .. can you tell me how to exit from this mode and get the phone started

my fone is stuck on fastboot mode how to get over it ?

Can't install ADB, TWRP, or OS

Guys, I think I messed up big league. I set a pin on startup and I'm guessing that encrypted my "system" partition. After trying and failing to decrypt that with the PIN I had set to use on startup I tried wiping "dalvik", "cache", "system", and "data". Then I flashed DrakenFX's B15 stock ROM, but it's still asking for PIN on startup. When I rebooted, I was faced with the stock recovery. ADB won't install on my computer, so I don't know how to flash recovery back onto the device. (Do I need the device powered on and in an OS for ADB to recognize the device and install the correct drivers?) TWRP says there is no OS installed. So, I guess my question is this: How do I decrypt my device and get back into an OS.
Thanks a million for your help in advance.

TheWoerbler said:
Guys, I think I messed up big league. I set a pin on startup and I'm guessing that encrypted my "system" partition. After trying and failing to decrypt that with the PIN I had set to use on startup I tried wiping "dalvik", "cache", "system", and "data". Then I flashed DrakenFX's B15 stock ROM, but it's still asking for PIN on startup. When I rebooted, I was faced with the stock recovery. ADB won't install on my computer, so I don't know how to flash recovery back onto the device. (Do I need the device powered on and in an OS for ADB to recognize the device and install the correct drivers?) TWRP says there is no OS installed. So, I guess my question is this: How do I decrypt my device and get back into an OS.
Thanks a million for your help in advance.
Click to expand...
Click to collapse
The only way to really decrypt your phone is by formating it, as for twrp try fastboot instead of adb is going to be easier and then download the OS of your choice if u need further help pm me ill help u through teamviewer

J0nhy said:
The only way to really decrypt your phone is by formating it, as for twrp try fastboot instead of adb is going to be easier and then download the OS of your choice if u need further help pm me ill help u through teamviewer
Click to expand...
Click to collapse
*EDIT* So the ADB installer ver. 1.4.3 wasn't playing nice with Windows 10. I installed the 1.3.0 installer and it worked right away.
Thanks! I'm back into DrakenFX's B15 ROM, now I need to figure out how to get ADB and fastboot drivers to install correctly. Every time I run the ADB+Fastboot installer, I go through the process and it says "0 Files Copied." Any help there?

TheWoerbler said:
*EDIT* So the ADB installer ver. 1.4.3 wasn't playing nice with Windows 10. I installed the 1.3.0 installer and it worked right away.
Thanks! I'm back into DrakenFX's B15 ROM, now I need to figure out how to get ADB and fastboot drivers to install correctly. Every time I run the ADB+Fastboot installer, I go through the process and it says "0 Files Copied." Any help there?
Click to expand...
Click to collapse
This is the adb and fastboot i use:
https://mega.nz/#!FdARiCIJ!QM_sfJ_JNBNv5HvjyNycVVZCSN6fUP5gVZdXKpUOAbo
To use it simply unzip the files then shift and left click and then click "open command window here" if you want to use adb type abd then whatever same thing with fastboot
{
"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"
}

Weird . Phone Unlocked FRP Locked at Bootloader.

Just today i tried to update my Rooted device by first flash in orignal Recovery to update system.
Yet at Bootloader it shows like this
{
"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"
}
then i tried following commands with adb and this is output:
fastboot flash recovery xxx.img
FAILED: Command not allowed
fastboot oem unlock MyCode
FAILED:Command not allowed
fastboot oem lock MyCode
FAILED:Type root is risk
fastboot get oem-info
FAILED:Command not allowed
right now any command on fastboot are not allowed
my phone is working perfectly fine except in "develop mode" that OEM UNLOCK option is grayed out probly cuz the phone is unlocked yet FRP is locked.
and i can't relock or unlock the phone or get lock info on this or flash in recovery or anything .
i'm still with TWRP custom recovery now and i'm trying to update system.
can someone help me plz If i can excute just ONE of those Commands above. i think can solve everything.

Did you try to rebrand your phone?
If you got a backup of your original oem-info, restore it in twrp.
Then try again.

you mean like OTA restore and might lose everything? can't really risk that.
i'm perfectly fine with current statu and only reason i'm trying to flash recovery is trying to update my System. after last time's OTA wipe and install then restore i lost all chat record and everything even though i backed up everything.

How about factory reset devices and re-enable
Developer options > OEM unlocking (Enable this one)

@Bigbearxl
Since i've already Unlocked the phone i can not enable >OEM unlocking
That's why i've been trying to re-lock the phone to enable it then unlock again see if i can get FRP unlocked.
yet i can't excute any command on fastboot right now even lock/unlock
Well i haven't really tried <factory reset> because i have TWRP on my recovery. How does factory reset works? wipe every data of my phone or just unroot or restore yet still keep my datas remain?

I think the reason for "phone unlocked frp locked" and fastboot commands not working is that you somehow messed up your oem-info.
If you got a twrp backup restore just the oem-info. Afterwards you should be able to use fastboot again, but still need to unlock. But don't worry, since your phone is still unlocked it should be without low level factory reset.

how does factory reset works? it warns me that it will erase all data incluid music and photos and some app's document which means my game savings and chat history and so on. Is that right?

Yes, that's right.

i have same problem,any one help?

For All those information above. I believe so much for me to do is 1. Factory reset might get my OEM UNLOCK option in develop working again .2. go to fastboot and get those commands working.
yet those steps will erase my data and everything.
I'm wating because i'm trying to find a better way to unlock FRP without Erasing everything in my phone.
Anyway thank you guys for your associate. I appreciate your help.

[Solved] P10 Lite: Erecovery missing after Unlocking & FRP Locked

I am on EMUI 5.1.1. I unlocked my P10 Lite with dc-Unlocker.
Than I was trying to flash TWRP, but was using the wrong command. Instead of:
.\fastboot.exe flash recovery_ramdisk .\recovery.img
Click to expand...
Click to collapse
I was using:
.\fastboot.exe flash recovery .\recovery.img
Click to expand...
Click to collapse
Now FRP is locked. And I am not able to boot to erecovery any more:
Func NO: 11 (recovery image)
Error NO: 2 (Load failed)
Click to expand...
Click to collapse
Is there any change installing Stock EMUI for new?

Give it a try
Error mode - Func 11 and 2
Please guys, help me, I still can boot into fastboot, but can't boot into twrp(even flashing it via fastboot recovery_ramdisk) or erecovery
forum.xda-developers.com

The main problem seems to be that PHONE is UNLOCKED but FRP is LOCK.
I have no clue how to unlock this damn FRP.

FRP UNLOCK

Was able to solve the problem.
Installed with dload EMUI 8.0.0
Reset the phone to defaults
Reactivated OEM unlock

temper999 said:
Was able to solve the problem.
Installed with dload EMUI 8.0.0
Reset the phone to defaults
Reactivated OEM unlock
Click to expand...
Click to collapse
I need help with fixing this Google look. The above YouTube guide is not working as YouTube wants to be first updated, putting me in a loop, as user details are again requested, but frp lock is stopping me.
Where to get this download or a full factory image to overwrite the lock?

I currently only found is this the a good url? https://huaweidl.com/download/mate-10-lite/rne-l21/8-0-0-342/

temper999 said:
I am on EMUI 5.1.1. I unlocked my P10 Lite with dc-Unlocker.
Than I was trying to flash TWRP, but was using the wrong command. Instead of:
I was using:
Now FRP is locked. And I am not able to boot to erecovery any more:
Is there any change installing Stock EMUI for new?
Click to expand...
Click to collapse
the correct comand is
fastboot flash recovery_ramdisk TWRP....
the best way is to put the TWRP or system image or what ever you want to flash by fastboot mode into the adb folder
adb folder with adb and fastboot and son on just put (for example the adb folder on my PC--->look the Picture)
{
"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"
}
then just mark the image you want to flash (mark it completly)
then in adb you just need the right comand
good luck
solong
speedson

Problem with recovey installation

Hello everyone, I recently installed via twrp 3.5.0.9 the new official V12.0.5.0.QFJEUXM rom from the latest xiaomi eu stable rom (xiaomi.eu_multi_HMK20MI9T_V12.1.2.0.RFJCNXM_v12-11). I just wanted to see how it was, now, I can not install the recovery again to install the xiaomi eu. Someone know how to help me.
It is as if it does not recognize the device when I send it the adb command, although in principle it does.
Thank you first of all.
{
"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"
}

viru78 said:
Hello everyone, I recently installed via twrp 3.5.0.9 the new official V12.0.5.0.QFJEUXM rom from the latest xiaomi eu stable rom (xiaomi.eu_multi_HMK20MI9T_V12.1.2.0.RFJCNXM_v12-11). I just wanted to see how it was, now, I can not install the recovery again to install the xiaomi eu. Someone know how to help me.
It is as if it does not recognize the device when I send it the adb command, although in principle it does.
Thank you first of all.View attachment 5294485View attachment 5294487
Click to expand...
Click to collapse
Before flashing, try: fastboot devices
In Developer options, is OEM unlocking and ADB debugging enabled?
If fastboot devices does not recognize device, try another USB cable or uninstall USB drivers and try again

Yes , OEM unlocking and ADB debugging is enabled, and i had tried with original cable and other one. Thanks for your answer i will keep trying.
"Before flashing, try: fastboot devices" it doesn´t work.

Don't type reboot bootloader if you are already in fastboot
Just flash recovery.
Your address is long, try c:\adb\twrp.img

viru78 said:
Yes , OEM unlocking and ADB debugging is enabled, and i had tried with original cable and other one. Thanks for your answer i will keep trying.
"Before flashing, try: fastboot devices" it doesn´t work.
Click to expand...
Click to collapse
Seems that something is wrong with your USB driver on the PC - adb devices works but fastboot devices does not (where Bootloader is unlocked and OEM Unlocking enabled)
Try uninstalling the USB driver(s) on the PC or try another PC

yaro666 said:
Don't type reboot bootloader if you are already in fastboot
Just flash recovery.
Your address is long, try c:\adb\twrp.img
Click to expand...
Click to collapse
Or copy the (twrp) img file right into the ADB folder on the PC, and go with CMD into the ADB folder before running adb/fastboot commands
Then no paths are needed, just like:
fastboot flash recovery twrp.img
But that will not help him as long as fastboot devices fails

I thought about address length, sometimes adb has problem with it, worth a try

fixed, thanks for your answers, the problem was the laptop and drivers, i have had used other pc and install without problems.