Database Users

Stuck waiting for adb mode\Failed remote bootloader

Hey, I'm pretty new to rooting, but I don't see where I did a mistake here or why this doesn't work.
- So I installed the toolkit, including the adb drivers (an error occured, but beneath it it said that this error means the drivers are installed anyway)
- then I connect my nexus 7 (usb debugging enabled). a long digit/letter code shows next to the device, which I take is the serial code.
- Then I go into backup, nandroid backup, as I want to backup my whole system before rooting. I chose NO in the options as it's the stock ROM.
Then it gets stuck here:
Code:
Booting into fastboot mode
downloading boot.img...
FAILED (remote bootloader is locked.)
Finished. total time: 0.023s
Your tablet will now boot into Android
Waiting for adb Mode
Meanwhile my tablet shows Fastboot mode in red at the top; it shows serial number, mw version, bootloader version, baseband version (N\A), serial number, signed (not defined yet), product name; and "Lock state - locked" in red at the bottom.
This is about all the information there is.
[EDIT]: Ok I found the option to unlock the bootloader in the toolkits... However, this resulted in me losing all my data on the phone. Which means, that in order to save my data I need to go through a process which deletes all my data?? Or maybe I shouldn't have chosen nandroid... Well, anyway. I'm thankful someone programmed this, but if you care for another user's opinion: not enough detailed documentation, at least not in the right order.

Soft bricked after OTA update (network unavailable, can't enter Android)

Hi!
I received a bricked teenager's phone to fix, but I don't know if this is possible at all. Maybe someone can help me or at least tell me if this is a hopeless case or not:
The device is a Xiaomi Redmi Note7 (lavender), model M1901F7G. It is soft bricked - I can't start Android to check the MIUI version (suppose it was 11.0.4.something or 11.0.7.something) nor are usb-debugging and/or oem-unlock enabled. This Note7 is on stock firmware and has always been, has never been rooted and as far as I know nothing has ever been done that is beyond official/public Xiaomi updates.
The error description is the device received an update over the air. After installation was completed the Android start failed with the error message "The system has been destroyed". It was still possible to start Android after the command "fastboot continue". Nevertheless the device was in a buggy state: time/date were completely wrong and what was worse: no network connection anymore, not with LTE and also not with WiFi.
In this buggy state userdata has been cleaned. This was to do a 'soft' attempt to repair and not to reset to factory defaults directly - probably not a smart idea, but anyway. Afterwards the phone came up with an initial installation wizard (language and region selection) and reports the device is locked with a Mi Account and needs to be activated. I have access to this account's credentials, but activation fails as there is still no network access available (same as before: no LTE, no WiFi). So I don't see any possiblility to let me enter Android to enable usb-debugging and oem-unlock.
I can access the Note7 via fastboot, but not with adb everything seems to be locked:
Code:
>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.021s]
finished. total time: 0.023s
So I doubt it is possible to do a complete wipe and flash an (older) firmware.
All in all it appears quite strange to me the phone got these problems after an OTA update. I couldn't find any information about others having the same symptoms with a MIUI 11.0.x update on a Redmi Note7. So, might this be a (hidden) hardware defect?
The phone has been bought in 07/2019, it should still be in warranty. My backup solution is to return it to the shop, but I estimate RMA to be processed in 2-4 weeks only (a nightmare for a teenager without smartphone) and I'm still not sure if this case is covered by warranty. Means I - and especially the owner of that device - would be happy if there would be a way to fix it!
Any hints and solutions are highly appreciated!
Kind regards,
Andy

You can not install older version firmware without rooting. Only new version and maybe same version
Maybe this guide can help if you can get into recovery mode (vol up + power)

Thanks a lot! Your guide helped and it worked!
I didn't know which version was installed and also not from which region. So I ended up with some trial and error. I assumed it would be a European or Global version though and just tried the newest ones I could get. In the end I was successfull with MIUI 11.0.7.0 Europe Stable OTA ROM <can't post links yet: bigota[dot]d[dot]miui[dot]com/V11.0.7.0.PFGEUXM/miui-blockota-lavender_eea_global-V11.0.4.0.PFGEUXM-V11.0.7.0.PFGEUXM-35b08eb301-9.0.zip >.
Code:
* Miui sideload made by Francesco Tescari, updated 02 Feb 2018 *
* Checking device status *
* Getting recovery info *
* Creating file MD5 hash *
* Querying ota update server, attempt #0 *
Data partition format might not be necessary and will NOT be done automatically after installation.
If the device doesn't reboot or some apps crash after reboot, you need to manually format the device using "format-data" command!
* Starting sideload *
Sending file to the device... (~100%)
Checking file checksum...
Installing file on the device... (~42%)
* Sideload output: Installation_complete. *
* Rebooting... *
Installation SUCCEEDED!
Please check your device status after reboot to make sure everything is right!
If everything is right and you want to show your gratitude you can offer me a beer by making a donation to this project, do you want to make a donation? [Y/n]
So thanks again! You safed me a couple of hours trying to find out a solution and made a teenager super having for having her phone back! :good:

moto g7 impatience and a bricked phone?

Alright. I am taking full responsibility for the stupid things I have done in the impatience of a Sunday afternoon, so I'm ready to accept that I just bricked my only phone.
So I decided that I wanted to root my phone, so without any previous experience or understandings of the systems, twrp and Magdisk.
My issues started when I tried to unlock the bootloader, and upon every single boot, it would briefly display that I had a "badkey", but I ignored that because it was still booting.
I then installed minimal ADB and fastboot and first flashed twrp, and then magdisk. Thats when the first issue started.
my phone was now stuck in a bootloop, saying something similar to my "badkey" error message, but in place of "badkey" was just "n/a"
This was bad. Really bad.
Next, I tried to fix it using my limited rushed knowledge, so I tried to flash a default moto g7 rom on to the phone. This was also a VERY big mistake.
This flash landed me into a phone that now displays absolutely nothing, and the only proof that I have that any of it even works is that, when plugged into my PC, it shows up on my COM4 port as Qualcomm HS-USB QDLoader 9008 (COM4).
Now here I am, at the mercy of the universe. If anyone has an idea or a similar experience or solution, please go ahead and share. If not, let this be a precautionary tale: Never rush; Never be impatient.

Xalllle said:
Alright. I am taking full responsibility for the stupid things I have done in the impatience of a Sunday afternoon, so I'm ready to accept that I just bricked my only phone.
So I decided that I wanted to root my phone, so without any previous experience or understandings of the systems, twrp and Magdisk.
My issues started when I tried to unlock the bootloader, and upon every single boot, it would briefly display that I had a "badkey", but I ignored that because it was still booting.
I then installed minimal ADB and fastboot and first flashed twrp, and then magdisk. Thats when the first issue started.
my phone was now stuck in a bootloop, saying something similar to my "badkey" error message, but in place of "badkey" was just "n/a"
This was bad. Really bad.
Next, I tried to fix it using my limited rushed knowledge, so I tried to flash a default moto g7 rom on to the phone. This was also a VERY big mistake.
This flash landed me into a phone that now displays absolutely nothing, and the only proof that I have that any of it even works is that, when plugged into my PC, it shows up on my COM4 port as Qualcomm HS-USB QDLoader 9008 (COM4).
Now here I am, at the mercy of the universe. If anyone has an idea or a similar experience or solution, please go ahead and share. If not, let this be a precautionary tale: Never rush; Never be impatient.
Click to expand...
Click to collapse
The bad key and n/a are normal for moto.
The Qualcomm deal is
Emergency download mode (edl)
You need to find a river blankflash
A bunch of threads on this.
There's one here
https://mirrors.lolinet.com/firmware/moto/river/blankflash/
It may work...
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
The bad key and n/a are normal for moto.
The Qualcomm deal is
Emergency download mode (edl)
You need to find a river blankflash
A bunch of threads on this.
There's one here
It may work...
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
I tried lauching blank-flash, and im getting this in response:
[ 0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 4.010] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.010] Check qboot_log.txt for more details
[ 4.010] Total time: 4.011s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
Can I get past this?

Xalllle said:
I tried lauching blank-flash, and im getting this in response:
[ 0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 4.010] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.010] Check qboot_log.txt for more details
[ 4.010] Total time: 4.011s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
Can I get past this?
Click to expand...
Click to collapse
Nevermind! I got it working by A. Trying it a billion times and B. trying it on another pc. For some reason, that made it work.

How to recover from a dead bootloader of Oneplus 6T [Resolved]

I am trying to unlock the bootloader of the oneplus 6T I have. After got the unlock tocken(.bin) file from Oneplus support, I did the command:
./fastboot flash cust-unlock ../unlock_code.bin
Sending 'cust-unlock' (0 KB) OKAY [ 0.005s]
Writing 'cust-unlock' ^C
^C^C^C^C^C^C
So the fastboot program is hung when writing to the bootloader flash flash I guess. After powering down the phone, I can't power it up anymore -- the bootloader is dead (bricked).
I hope someone had this experience before can shed me some light or point me to some posts.
Updates:
I got this pointer: https://forum.xda-developers.com/t/...totally-sleep-dead-boot-mode-via-usb.1701471/ But it is for OMAP based.
Oneplus6T uses Qualcomm “Snapdragon” series of SoC
Got this thread: https://forum.xda-developers.com/t/tool-6t-msmdownloadtool-v4-0-59-oos-v9-0-13.3867448/ -- will update on this one
As a courtesy, I am hrer to update with a resolved status so that others can be aware of:
1) Google online for a more intuitive introduction and step by step guide on how to use MSM tool to update bootloader(s). There are multiple stages of bootloading and each has one bootloader.
2) It is not hard to get the MSM tool to see the device connected. But it is common that the tool can't update the device bootloaders/images, with the error "Sahah protocol ... " type of message. THe reason I guess is the following.
3) It is very hard to be sure if your device is in EDL mode just right for the MSM tool to talk to. I don't know what stage the device has to be in for the MSM to work correctly. It is very hard to even know what stage the device is in. SO VERY SADLY, it is a try and error and retry game. Many suggested things to try but I found the most useful one is the volume up and down button pressed together and then with power button, ALL THREE pressed for some seconds after the device is powered down. But you don't even know how long it takes to power down the device .... etc. So try the all three button procedure as many as you, with luck you will be able to see that the MSM tool will start to update.
4) I am brandnew noob in the android world. There are so much to learn about this giant world of android-ing. There are so many terms (technical/no-tech), versions of kernel/OS/Apps/Framework/devices/vendors/ROMs/etc. Instructions online are very helpful, but some of them are obsolete (be careful). Some of them are not detailed enough and some of them are just an experience of one try and some of them ..... it is not as straight forward as you imagined (as always in the software/hardware world).
5) I still am not sure what caused the failure of my first try to unlock the 6T. I guess it is due to the fact that I did it on Linux and it hasn't got an update driver. Eventually I did the unlock on Windows 10.
Some other useful links:
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
[OP6T][LATEST 10.3.8] Collection of unbrick tools
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com

[HELP] - Workaround to unlock bootloader

Hi, good day!
Currently following an instruction from sony developer website on how to unlock the bootloader of my XZ2 Premium.
After ticking the OEM unlock, and checking the 'Bootloader unlock allowed', it still says 'No'.
I have H8116 model
I'm about to type the IMEI, but, upon checking the bootloader unlock allowed status, it says 'No'.
Thank you in advance.