Database Info

N5 Help : No debugging mod, No Recovery

Hi,
I Got some problems with my Nexus 5 last days. First it was the power button problem and it was restarting all the time. I cleaned and it seems ok now.
But NOW my android is not restarting. I don't know if it was due so many restarts during the last few days ... The point is : Or it stocks at the '' GOOGLE '' screen, or it goes to the last part with some colorful stuffs '' gifs loading '' FOREVER.
I Don't have the USB Debugging mode ON so I can't do anything from ADB using my computer.
I Cant access recovery mode ( ALL STOCK SOFTWARE ). When i open the recovery mode it just shows the android with red triangle and NO OPTIONS. Neither Reset and other options that should be there.
I really don't now how to proceed from now.
Any tips?
Thanks !

When you enter recovery, you are suppose to see th dead android with the red triangle. When you see this, hold the power button and press volume up to enter recovery.

That's what i tried to say , sorry. Even doing that nothing happens. None options are shown.

Try reflashing recovery.img file

Hi,
After sometime I'm able to access the recovery mode. But my device are still dead.
Now ,when I open recovery mode it shows right this at the first screen
'' Supported API: 3
E: failed to mount /cache ( Invalid Argument) "
I've already tried to wipe cache/FR and it shows just a lot of problems in creating/wiping partitions.
I tried as well to run the flash-all.bat from the latest android version files from android website but nothing worked.
Any tips to proceed?

Trying to flash using cmd, file by file i got erros like that
'' erasing cache/userdata/system(all those)
FAILED ( remote: failed to erase partition)
Finished. Total time 0.2s ''
For all files from bootloader.img to syustem/recovery/radio/userdata/cache
edit : I've use '' fastboot oem unlock '' , but didn't worked as well.

When you unlock the bootloader, does the bootloader relock itself when the phone reboots?

Yes, after I reset the bootloader relock itself !

Since the bootloader relocks itself after a reboot, the motherboard memory is damaged; therefore, you will need to replace the motherboard.

[Softbricked Phone] Help needed

Hi everyone.
3 days ago, my OPO has gone softbricked during the night while charging. Don't know why, i haven't make any change during the past days.
Anyway, it's current state:
- Stuck on boot screen (screen with "Cyanogen Mod Ready")
- Can access fastboot
- Can access TWRP recovery
- Bootloader is unlocked
- Phone is found in the PC "Device Manager"
- No change if using an other cable or USB port
And what i can't do:
- with adb tools : phone is not found with cmd adb devices (no answer in "list of devices attached"), changing drivers multiple times don't change that
- during recovery : can't wipe data / cache / factory reset (it says "Unable to mount /data" "Unable to mount /cache", "Unable to mount storage")
- during fastboot : can't flash anything (for instance with the OPO Toolbox, the answer is always "FAILED (remote : flash write failure)", or with command fastboot flash XXXX get the same FAILED answer)
After reading internet threads and sites, it seems that the problem is a corrupted partition, but i can't find something which can solve my problem.
Any advises?
Thx in advance!

3th3lk4 said:
Hi everyone.
3 days ago, my OPO has gone softbricked during the night while charging. Don't know why, i haven't make any change during the past days.
Anyway, it's current state:
- Stuck on boot screen (screen with "Cyanogen Mod Ready")
- Can access fastboot
- Can access TWRP recovery
- Bootloader is unlocked
- Phone is found in the PC "Device Manager"
- No change if using an other cable or USB port
And what i can't do:
- with adb tools : phone is not found with cmd adb devices (no answer in "list of devices attached"), changing drivers multiple times don't change that
- during recovery : can't wipe data / cache / factory reset (it says "Unable to mount /data" "Unable to mount /cache", "Unable to mount storage")
- during fastboot : can't flash anything (for instance with the OPO Toolbox, the answer is always "FAILED (remote : flash write failure)", or with command fastboot flash XXXX get the same FAILED answer)
After reading internet threads and sites, it seems that the problem is a corrupted partition, but i can't find something which can solve my problem.
Any advises?
Thx in advance!
Click to expand...
Click to collapse
Is your bootloader unlocked?If not try it with this command:
fastboot oem unlock
Click to expand...
Click to collapse
After that try wiping your partitions via fastboot for ex.
fastboot erase userdata
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
Click to expand...
Click to collapse
And then try flashing again.
Hope it helps:good:
Regards,
acervenky

Hi acervenky,
Bootloader is unlocked, yes.
Unfortunately, wiping partitions with those commands didn't work.
For the 5 commands, i have the answer : FAILED (remote : failed to erase partition).
This phone is going to drive me insane!

So a little update status of my phone.
I have sent a question at request at the oneplus one support.
They have answered quite fast. They made a "rendez-vous" to try to unbrick it by phone but all that was tried have been already done.
They send me instructions for sending the phone to a factory in a foreign contry.
I have received the phone this afternoon, 1 week after it was sent.
Seems to work perfectely fine.
They say that they have changed the Motherboard, which is the problem here.
So if u have the same problem, don't hesitate to use the oneplus one support.
Is there a way to change the title to show that it was a motherboard problem?

All commands fail in fastboot

Hello everyone,
after unlocking my bootloader (on a Realme 5 Pro) to install TWRP and custom ROM, I am now stuck at trying to make fastboot do anything.
No matter which fastboot command I try, the phone won't execute it. I instantly get a "FAILED" and "(No error)" returned and the phone exits fastboot, showing some logo with a chinese message, as well as "press any key to shutdown" in the top left corner.
The only excpetions to that behaviour:
1. "fastboot devices" works as expected and recognizes the phone.
2. "fastboot boot [path to TWRP .img file]" sometimes gets stuck at "downloading boot.img..." indefinitely, sometimes it fails like all the other commands
3. "fastboot flash recovery [path to TWRP .img file]" gives an instant "FAILED", but the error message is "requested download size is more than max allowed"
I've tried re-locking and unlocking the bootloader, when unlocked both colorOS and fastboot recognize the bootloader as being unlocked.
I have no clue what to try at this point, hopefully someone can help me out?

Same problem here.
Mine is Realme 3 pro with the new version of realme UI, RMX1851, C.04, I have unlocked bootloader without downgrading it to color os 6, but now I cannot flash twrp in my device. After going into fastboot mode, after applying the commands, it says "FAILED" (remote: GetVar variable not found) and sometimes directly "ERROR"

The fix was an incredibly easy one, but I only found it/got the idea through a lot of googling... simply used a different PC (that I never used adb and fastboot with before), let windows search for drivers online, and BAM, it works!
Hopefully this will help someone in the future.
If you don't have more than one PC, I guess the best bet would be uninstalling all adb and fastboot related drivers.

Question Fastboot command issues on ROG 5

Am I the only one not being able to run Fastboot commands on the ROG 5?
I can connect with Fastboot fine and the device is identified but every command I try to run returns an error/denied on the Remote end (i.e from the device end). Simple read example: "Fastboot oem device-info" returns Remote: "Command not supported in default implementation", same with many others. Trying to flash TWRP to recovery_a (or b) returns "Remote: Unknown File or Directory". Tried everything I can think of. Does anybody have any good ideas for fixing this? Thanks in advance.

A lot of the _a partitions are only available by entering userspace fastboot (fastboot reboot fastboot) and that is a quick and easy way to soft brick.

twistedumbrella said:
A lot of the _a partitions are only available by entering userspace fastboot (fastboot reboot fastboot) and that is a quick and easy way to soft brick.
Click to expand...
Click to collapse
I soft bricked it once already but managed to get out of it. But I can't even do simple read commands let alone flashing anything, all Fastboot commands are sent to the device but return a Remote rejected/error. I also suspect the bootloader may still be locked despite having run the ASUS unlock tool and seeing the unlock warning on boot (I have no way of confirming). I may have to ask ASUS for some help...

Unlock TCL 20y (6156D) phone. Possible?

Hello,
I have a TCL 20y (model 6156D) phone and i'm trying to gain root access in any way.
I've tried to enable oem unlocking and go to fatboot mode, but the command
fastboot oem unlock returns "FAILED (remote: 'Command not supported in default implementation')".
On producer website i can't find this model and in the "repair software" this model (6156D) is missing.
I don't have any recovery file (stock or trwp), and i don't know how to dump original recovery to file (for install magisk, but anyway i think i can't flash modified versions without unlock bootloader).
Is there anything i can try?
---
Edit: I finally found the original flash tool at the following url:
Modello
www.tcl.com
https://www.tcl.com/content/dam/tcl-html/TCTService/support/tcl-20-r-5g/Mobile_Upgrade_S_Gotu2_v1.1.5_Setup.exe
It seems to support model 6156 and, with connected phone, it has downloaded a lot of files and created a folder "6156D-2ALCWE12\ANAJEAJ0" (model\version) with a lot of files with MBN extension and a zip with system.img inside.
Maybe these files may be useful to root the phone. Anybody knows how to open MBN files?
--
Edit: I've notice a strange thing. When I boot to recovery, i see two interesting options:
- Enter fastboot: this stats "fastbootd", a graphical menu with a few reboot options. In this phase the computer recognizes the phone with fastboot driver and list it with "fastboot devices" command.
- Reboot to bootloader: this clear the screen, writes "FASTBOOT>" in the low position of the screen. In this phase the computer recognizes the phone with adb driver and don't list it in fastboot devices nor adb devices.
I've also tried to flash magisk apk (renamed as zip) with adb sideload, but as expected i got Error 21.
Is there a way to sign any root manager or su binary and install it using this method?
What am i doing wrong?

Hi!
I've managed to unlock the bootloader on a TCL 20Y by following this guide: https://romprovider.com/tcl-20y-unlock-bootloader/.
I used the mtk_gui utility, which is really straightforward. The only tricky thing was going into brom/preloader mode - sometimes it works, other times it doesn't.. The trick is to hold both volume buttons while plugging in the USB cable to the computer.
Then, I've also managed to root the device with Magisk by patching both the boot_a.img and boot_b.img images and flashing them using fastboot by following the official guide: https://topjohnwu.github.io/Magisk/install.html.
Haven't yet played with the orange state disabler as I've read that it can result in a brick.
BR

Hey there!
With bevvare's help I was also able to root my TCL 20Y without much issue, though I encountered a few minor differences and details so we agreed it would be good if I wrote them down here.
Regarding the first guide used to unlock the bootloader:
The mtk_gui utility packed in the, as of today, latest release of mtkclient (1.52) refused to launch. That wasn't too bad seeing as the guide provides the necessary commands, but it's something to keep in mind.
In addition, I found that the phone would stop accepting commands after the first one was issued or after the log got too long*. This might have only been an issue on my end, but just in case, this is how i ran each command:
-Turn the phone off
-Hold the power button along with both vol+ and vol- (you may plug in the phone at this stage)​-While in the Recovery Mode screen, issue the command on your terminal​-Select the option to restart the device in the recovery screen, then hold both vol+ and vol- until the terminal starts printing output (the phone's screen will stay off while this happens)​-After the command has executed, unplug the phone (probably optional) and hold all three buttons again to restart and boot into recovery​Repeat as needed​​
* Remember how I mentioned the command seemed to fail if the log got too long? Well, this is what happened to me with the very first command on the guide (the one that erases three partitions at once). Just to be sure, I erased them separately using the same command.​​PS: booting into recovery first may not even be needed, I just found it easier that way.​
The guide provides two unlock commands, the first one being python mtk xflash seccfg unlock, this ran without issue and triggered the orange state warning on boot. The second command (fastboot flashing unlock) refused to work, but the bootloader was nonetheless unlocked.
Also, the guide provides the relock command right after the unlock one as if it were the next step to take. This might be obvious, but don't relock your bootloader until after you're done flashing the new boot image (even then there's no real reason to relock it).
Regarding Magisk's guide on patching boot.img:
Magisk failed to patch boot_b.img. This turned out to not be a problem because my device was using the boot_a partition as the active one (I used this guide to check https://krispitech.com/check-partition-slot-a-b/ )
In order to get the necessary files, namely boot_a.img and vbmeta_a.img, I used this guide to dump all the partitions within the phone into my PC: https://forum.xda-developers.com/t/...sing-mtk-client-oppo-reno6-5g-mt6877.4406069/
You may also decide to dump only the two partitions you need, in which case you could issue the following command instead: python mtk rl boot_a,vbmeta_a boot_a.img,vbmeta_a.img (this assumes your phone is also using partition A, adjust as needed).
If you used the above guide to dump all the partitions, the files you need will have the .bin extension, just rename them so they are .img files instead.
I recommend flashing vbmeta_a.img (it's optional and doesn't need to be patched in the Magisk app like boot_a.img). Otherwise your device will print a spooky warning at boot about being corrupt and demand you press the power button, which is annoying.