Since i got as a gift this phone (used) i got an issue with the boot logo.
It seemed to be a stable bootloader and a stock recovery, also a stock rom, but when i turned on this phone, always all the boot logo disapears and shows a black display during the process. When the boot animation starts it's all normal. I'm almost sure the phone has never rooted or flashed before.
As an extra, yesterday i've unlocked the phone's bootloader successfuly and tried to flash a TWRP recovery into it.
When i tried to flash the recovery the adb tools tolde everything was fine, but when i turn on my phone it's like never flashed that before, the original recovery appears like nothing happened.
Also, when i unlocked the recovery and tried to flash the TWRP recovery, the ADB tools showed these messages during all the process.
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
What can i do?
Are you using win10 ?, and are you using commands
Enviado desde mi XT1563 mediante Tapatalk
flopezm said:
Are you using win10 ?, and are you using commands
Enviado desde mi XT1563 mediante Tapatalk
Click to expand...
Click to collapse
Yes & yes
acibo123 said:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
What can i do?
Click to expand...
Click to collapse
Can you do this:
adb devices
adb reboot bootloader
fastboot reboot bootloader
?
When you are there then you should do this (while the new recovery image is in the same folder as adb)
fastboot flash recovery xyz.img
Then you should have the new recovery working.
If you can't reboot the bootloader using fastboot command, then you need the appropriate drivers. I'd advice to install Motorola Device Manager or something similiar. All steps are well documented over this forum...
Dio-Genes said:
Can you do this:
adb devices
adb reboot bootloader
fastboot reboot bootloader
?
When you are there then you should do this (while the new recovery image is in the same folder as adb)
fastboot flash recovery xyz.img
Then you should have the new recovery working.
If you can't reboot the bootloader using fastboot command, then you need the appropriate drivers. I'd advice to install Motorola Device Manager or something similiar. All steps are well documented over this forum...
Click to expand...
Click to collapse
I can do that, and aperently looks that the new recovery has successfuly installed, but no. When i get into recovery, the phone shows me the stock recovery.
acibo123 said:
I can do that, and aperently looks that the new recovery has successfuly installed, but no. When i get into recovery, the phone shows me the stock recovery.
Click to expand...
Click to collapse
Using the most recent TWRP?
Sometimes I had to flash several times, too, before it snapped...
Dio-Genes said:
Using the most recent TWRP?
Sometimes I had to flash several times, too, before it snapped...
Click to expand...
Click to collapse
Yea, the most recent. I'm thinkin about the idea of flashing the recovery by the app. But TWRP doesn't have support for my device, only fot the Moto X Style
acibo123 said:
Yea, the most recent. I'm thinkin about the idea of flashing the recovery by the app. But TWRP doesn't have support for my device, only fot the Moto X Style
Click to expand...
Click to collapse
Did you check for the drivers again. Especially for the ones when the device is in fastboot mode...
Does it show up when bootloader is running like
fastboot devices
Does ist show up and is it connected?
Which USB Port are you using? 2.0 or 3.0? This seems to make a big difference, you only should use 2.0 though it worked for me with 3.0 either. But, for example, the Motorola Device Manager doesn't see the device when connected to 3.0 USB port (over here).
Dio-Genes said:
Did you check for the drivers again. Especially for the ones when the device is in fastboot mode...
Does it show up when bootloader is running like
fastboot devices
Does ist show up and is it connected?
Which USB Port are you using? 2.0 or 3.0? This seems to make a big difference, you only should use 2.0 though it worked for me with 3.0 either. But, for example, the Motorola Device Manager doesn't see the device when connected to 3.0 USB port (over here).
Click to expand...
Click to collapse
1. Yes, i've checked
2. Yes, it appears.
3. Everything's in order, except those i have mentioned before.
4. I've used always 2.0
Anything more can you suspect?
acibo123 said:
1. Yes, i've checked
2. Yes, it appears.
3. Everything's in order, except those i have mentioned before.
4. I've used always 2.0
Anything more can you suspect?
Click to expand...
Click to collapse
Well, no, nothing more that I could suggest...
Dio-Genes said:
Well, no, nothing more that I could suggest...
Click to expand...
Click to collapse
Do you know how can i get the missing files showed at te console (Writen in the post)?
acibo123 said:
I can do that, and aperently looks that the new recovery has successfuly installed, but no. When i get into recovery, the phone shows me the stock recovery.
Click to expand...
Click to collapse
What do you do after flashing TWRP? If you boot system your TWRP will be overwritten by stock recovery, so you need to boot TWRP straight after flashing it to keep it.
minimale_ldz said:
What do you do after flashing TWRP? If you boot system your TWRP will be overwritten by stock recovery, so you need to boot TWRP straight after flashing it to keep it.
Click to expand...
Click to collapse
And how can i do that?
acibo123 said:
And how can i do that?
Click to expand...
Click to collapse
since you flash TWRP in fastboot mode you can boot TWRP after flashing it from the screen you're on, just navigate to "recovery" with volume buttons and press power button to confirm.
minimale_ldz said:
since you flash TWRP in fastboot mode you can boot TWRP after flashing it from the screen you're on, just navigate to "recovery" with volume buttons and press power button to confirm.
Click to expand...
Click to collapse
Oh, i forgot mention i can't enter into fastboot mode by that method
acibo123 said:
Oh, i forgot mention i can't enter into fastboot mode by that method
Click to expand...
Click to collapse
really, why? You can also enter
Code:
fastboot reboot
after flashing TWRP and hold power + volum down buttons straight after your screen goes blank to re-enter fastboot mode. I'm not sure if this is enough for TWRP not to be overwritten though, but worth trying out.
EDIT: or you can try this: https://twrp.me/app/
minimale_ldz said:
really, why? You can also enter
Code:
fastboot reboot
after flashing TWRP and hold power + volum down buttons straight after your screen goes blank to re-enter fastboot mode. I'm not sure if this is enough for TWRP not to be overwritten though, but worth trying out.
EDIT: or you can try this: https://twrp.me/app/
Click to expand...
Click to collapse
Thanks for the suggestions, but don'd worry, i ussualy get the fastboot mode by entering
fastboot reboot bootloader/recovery
But i'm afraid that the buttons issue will cause troubles if phones get bricked.
Which "latest" TWRP version are you using exactly? As far as I know, there's only one version and it's unofficial
Sent from my Motorola XT1563 using XDA Labs
The Analog Kid said:
Which "latest" TWRP version are you using exactly? As far as I know, there's only one version and it's unofficial
Sent from my Motorola XT1563 using XDA Labs
Click to expand...
Click to collapse
To be exactly 3.1.0
acibo123 said:
To be exactly 3.1.0
Click to expand...
Click to collapse
That's 3.1.0-r1...?
Sent from my Motorola XT1563 using XDA Labs
Related
i keep trying to install various images of twrp (3022, 21, 3001) and none of them ever appear on the phone. all i get is what's seemingly the stock recovery with the starry top half and oneplus logo at the top. any solution to this? bootloader is unlocked and usb debugging is enabled in oxygen 2.2.1
nvm fixed it by flashing the very first version of twrp that was listed on the site
Quote100 said:
i keep trying to install various images of twrp (3022, 21, 3001) and none of them ever appear on the phone. all i get is what's seemingly the stock recovery with the starry top half and oneplus logo at the top. any solution to this? bootloader is unlocked and usb debugging is enabled in oxygen 2.2.1
Click to expand...
Click to collapse
You just have to make sure to reboot directly to recovery/twrp after the flash... The new recovery will not stay if you reboot to system or bootloader after the flash.
jflow36 said:
You just have to make sure to reboot directly to recovery/twrp after the flash... The new recovery will not stay if you reboot to system or bootloader after the flash.
Click to expand...
Click to collapse
I did this by mistake and I want my custom recovery(twrp) back!what do I do?pls help
Install latest recovery turn off phone by long pressing power key and use recovery key combo
Sent from my ONE A2005 using Tapatalk
fburgos said:
Install latest recovery turn off phone by long pressing power key and use recovery key combo[/QUOTE
The stock recovery won't show or read the img file ..
Click to expand...
Click to collapse
Bingi46 said:
fburgos said:
Install latest recovery turn off phone by long pressing power key and use recovery key combo[/QUOTE
The stock recovery won't show or read the img file ..
Click to expand...
Click to collapse
-download minimal adb and drivers for pc
-Unlock bootloader.
-Fastboot flash recovery twtlatest.img
-Long press power off
-Use combo key to directly boot into recovery
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
Hello all, I have a Lenovo a6000 smartphone. It was owned by my friend. She had a problem with the android os, so she went to a local store and the there it got hard bricked. Now if I turn it on it only vibrates once. no backlight or any picture. If I press and hold vol- and power buttons together LCD backlight turns on but no display. then it goes off and then again turns on. PC does not detect it. Can anyone help me getting it out from this state?
arnab8820 said:
Hello all, I have a Lenovo a6000 smartphone. It was owned by my friend. She had a problem with the android os, so she went to a local store and the there it got hard bricked. Now if I turn it on it only vibrates once. no backlight or any picture. If I press and hold vol- and power buttons together LCD backlight turns on but no display. then it goes off and then again turns on. PC does not detect it. Can anyone help me getting it out from this state?
Click to expand...
Click to collapse
Try qfil method
JovanSijacki said:
Try qfil method
Click to expand...
Click to collapse
Can you give the link please..... please note the phone is no longer detected in pc
arnab8820 said:
Can you give the link please..... please note the phone is no longer detected in pc
Click to expand...
Click to collapse
You need to have adb and fastboot drivers for your phone to correctly get detected.
Here's the LINK FOR QFIL TUTORIAL. You'll need another set of drivers called as the QCOM drivers which are mentioned in the tutorial from the above link.
Hope this helps.
I already have installed the drivers. Still not detected. Even the device manager does not show a device is connected
sasukay said:
You need to have adb and fastboot drivers for your phone to correctly get detected.
Here's the LINK FOR QFIL TUTORIAL. You'll need another set of drivers called as the QCOM drivers which are mentioned in the tutorial from the above link.
Hope this helps.
Click to expand...
Click to collapse
Here the phone connects in Qualcomm hs-USB...... mode. But in case of mine, it does not even show up in the device manager.
arnab8820 said:
Here the phone connects in Qualcomm hs-USB...... mode. But in case of mine, it does not even show up in the device manager.
Click to expand...
Click to collapse
You should try changing the usb cable you are using. Or maybe that guy in the local repair shop didn't put the sub PCB board back correctly.
sasukay said:
You should try changing the usb cable you are using. Or maybe that guy in the local repair shop didn't put the sub PCB board back correctly.
Click to expand...
Click to collapse
There is only one pcb in it. Changing the cable does not make a difference
One update. I can get into the fastboot mode. But the bootloader is locked. What to do?
arnab8820 said:
One update. I can get into the fastboot mode. But the bootloader is locked. What to do?
Click to expand...
Click to collapse
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
Code:
fastboot devices
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful, type in
Code:
fastboot flash recovery recovery.img
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
sasukay said:
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful, type in
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
Click to expand...
Click to collapse
Thanks! I will try it and post the results.
Btw are you sure it does not come with a locked bootloader? I tried to flash the stock recovery and got an error saying "unknown command or device is lock"
arnab8820 said:
Thanks! I will try it and post the results.
Btw are you sure it does not come with a locked bootloader? I tried to flash the stock recovery and got an error saying "unknown command or device is lock"
Click to expand...
Click to collapse
Yeah bro I'm 100% positive. I think unknown command is displayed when you flash the wrong version of recovery.
You can also try
Code:
fastboot boot recovery.img
Sometimes only this works which temporarily boots into the custom recovery.
sasukay said:
Yeah bro I'm 100% positive. I think unknown command is displayed when you flash the wrong version of recovery.
You can also try
Sometimes only this works which temporarily boots into the custom recovery.
Click to expand...
Click to collapse
Ok friend i will post the results tonight
sasukay said:
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
Code:
fastboot devices
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful, type in
Code:
fastboot flash recovery recovery.img
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
Click to expand...
Click to collapse
Tried the above method but no luck it gives an error: "unknown command or device is lock".
arnab8820 said:
Tried the above method but no luck it gives an error: "unknown command or device is lock".
Click to expand...
Click to collapse
Try this with the CWM recovery too.
BTW does your device gets detected by fastboot devices command? Also, have you tried the QPST method?
sasukay said:
Try this with the CWM recovery too.
BTW does your device gets detected by fastboot devices command? Also, have you tried the QPST method?
Click to expand...
Click to collapse
Device gets detected by fastboot devices command. I cant try qpst because the device is not detected in any other mode except fastboot. I hv all the drivers installed
arnab8820 said:
Device gets detected by fastboot devices command. I cant try qpst because the device is not detected in any other mode except fastboot. I hv all the drivers installed
Click to expand...
Click to collapse
You've tried booting into Download mode? It requires you to press the VOL UP + POWER KEY, then you need to select the Download mode in it to perform flashing through QPST.
Also, you never mentioned what android version was the device on, earlier.
sasukay said:
You've tried booting into Download mode? It requires you to press the VOL UP + POWER KEY, then you need to select the Download mode in it to perform flashing through QPST.
Also, you never mentioned what android version was the device on, earlier.
Click to expand...
Click to collapse
If i press and hold vol up and power key together the phone only vibrates once and shows nothing. And i think my friend applied the lollipop update on it. She is not sure.
arnab8820 said:
If i press and hold vol up and power key together the phone only vibrates once and shows nothing. And i think my friend applied the lollipop update on it. She is not sure.
Click to expand...
Click to collapse
Try fastboot oem unlock
arnab8820 said:
Tried the above method but no luck it gives an error: "unknown command or device is lock".
Click to expand...
Click to collapse
I think you are missing something (maybe).
The command is "fastboot flash recovery recovery.img"
If the recovery files name is twrp.img then command will be "fastboot flash recovery twrp.img".
I'm trying to install TWRP recovery on my essential phone. this is the guide i am using, though pretty much every guide i found follows the same commands:
https://android.gadgethacks.com/how-to/install-twrp-recovery-essential-ph-1-0187660/
The command to determine my current slot returned that i am on slot_b, and when i try to flash the twrp img to slot_a, it sits trying to write. it never crashes but doesn't get anywhere. nothing is happening either in the command prompt window or on the phone screen.
I'm not sure what the issue is. I've updated the android sdk to the newest version and confirmed that I'm using that version of fastboot. I've also updated essential's windows drivers for the device, and rebooted the bootloader several times.
EDIT: I have noticed that on the phone screen when in the bootloader, it says "SECURE BOOT - yes". i don't know if this is important, but when i ran "fastboot oem device-info" it said true for unlocked and unlocked-critical.
Ricx94 said:
I'm trying to install TWRP recovery on my essential phone. this is the guide i am using, though pretty much every guide i found follows the same commands:
https://android.gadgethacks.com/how-to/install-twrp-recovery-essential-ph-1-0187660/
The command to determine my current slot returned that i am on slot_b, and when i try to flash the twrp img to slot_a, it sits trying to write. it never crashes but doesn't get anywhere. nothing is happening either in the command prompt window or on the phone screen.
I'm not sure what the issue is. I've updated the android sdk to the newest version and confirmed that I'm using that version of fastboot. I've also updated essential's windows drivers for the device, and rebooted the bootloader several times.
EDIT: I have noticed that on the phone screen when in the bootloader, it says "SECURE BOOT - yes". i don't know if this is important, but when i ran "fastboot oem device-info" it said true for unlocked and unlocked-critical.
Click to expand...
Click to collapse
Have you the latest twrp.img from the twrp.me site?
Do you have a type c to USB connector thing? Bluetooth keyboard?
If yes, fastboot flash boot twrp.img.
You might need the Bluetooth keyboard in case of not having touch response.
dirtyreturn said:
Have you the latest twrp.img from the twrp.me site?
Do you have a type c to USB connector thing? Bluetooth keyboard?
If yes, fastboot flash boot twrp.img.
You might need the Bluetooth keyboard in case of not having touch response.
Click to expand...
Click to collapse
i do have the newest file. i even tried redownloading it thinking the file might have been corrupted.
i haven't gotten to the part where i would need a usb otg keyboard yet, though i have one for when i make it that far.
I would check out the PH1 Development Telegram Channel as if your on stock they have boot images with TWRP and root already added and then all you have to do is fastboot flash the patched image and you will have TWRP with working touch and root as well. Here is the link to the channel if your interested https://t.me/EssentialPH1DEV
dirtyreturn said:
Have you the latest twrp.img from the twrp.me site?
Do you have a type c to USB connector thing? Bluetooth keyboard?
If yes, fastboot flash boot twrp.img.
You might need the Bluetooth keyboard in case of not having touch response.
Click to expand...
Click to collapse
robertbarber said:
I would check out the PH1 Development Telegram Channel as if your on stock they have boot images with TWRP and root already added and then all you have to do is fastboot flash the patched image and you will have TWRP with working touch and root as well. Here is the link to the channel if your interested https://t.me/EssentialPH1DEV
Click to expand...
Click to collapse
I'm not having issues with touch yet. haven't even made it far enough to know if I'm having an issue with touch in twrp...
I can't flash anything for some reason.
I'm stuck at "Sending 'boot_b' (48712 KB)" and nothing happens. every post I've seen says this should take less than 2 seconds but I've waited up to 10 minutes some tries and nothing happens. i need to restart the bootloader after trying this each time before it will let me try again.
Ricx94 said:
I'm not having issues with touch yet. haven't even made it far enough to know if I'm having an issue with touch in twrp...
I can't flash anything for some reason.
I'm stuck at "Sending 'boot_b' (48712 KB)" and nothing happens. every post I've seen says this should take less than 2 seconds but I've waited up to 10 minutes some tries and nothing happens. i need to restart the bootloader after trying this each time before it will let me try again.
Click to expand...
Click to collapse
Did you do the two unlock commands via fastboot? Firstly.?(not intending to dumb you down or anything)
Did you try with just - fastboot flash boot twrp.img ?
P.S. !! Definitely check out the posted telegram channel! Super helpful group of people.
dirtyreturn said:
Did you do the two unlock commands via fastboot? Firstly.?(not intending to dumb you down or anything)
Did you try with just - fastboot flash boot twrp.img ?
P.S. !! Definitely check out the posted telegram channel! Super helpful group of people.
Click to expand...
Click to collapse
I did fastboot flashing unlock and unlock_critical. Those seemed to work it shows up as being unlocked and factory reset.
To try to flash twrp I ran fastboot flash boot_a (also tried boot_b and boot) twrp.img and it tried to send but just sits trying and isn't getting anywhere.
Ricx94 said:
I did fastboot flashing unlock and unlock_critical. Those seemed to work it shows up as being unlocked and factory reset.
To try to flash twrp I ran fastboot flash boot_a (also tried boot_b and boot) twrp.img and it tried to send but just sits trying and isn't getting anywhere.
Click to expand...
Click to collapse
https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
Ricx94 said:
I did fastboot flashing unlock and unlock_critical. Those seemed to work it shows up as being unlocked and factory reset.
To try to flash twrp I ran fastboot flash boot_a (also tried boot_b and boot) twrp.img and it tried to send but just sits trying and isn't getting anywhere.
Click to expand...
Click to collapse
Are you using cmd or power shell for Windows. What ports are you using,2.0 or 3.0 and which type of cord. A-c or c-c
Sent from my PH-1 using Tapatalk
dazeone said:
Are you using cmd or power shell for Windows. What ports are you using,2.0 or 3.0 and which type of cord. A-c or c-c
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I've tried both CMD and Powershell
my computer only has USB 3.0 and 3.1 ports, all type A, so I'm using USB A-C cables. the cables are both only USB 2.0.
so I'm not sure why i tried this but it seemed to work...
I sent the flash command and when it got to the part it normally freezes at, i restarted the bootloader using volume and power keys on the phone. then while it was restarting i sent the command again, and as soon as it got to the bootloader the command activated and worked instantly. now I'm toying around with this newfound knowledge and i think i have twrp working. just wiped phone again and installed AOSIP so here we go
Ricx94 said:
so I'm not sure why i tried this but it seemed to work...
I sent the flash command and when it got to the part it normally freezes at, i restarted the bootloader using volume and power keys on the phone. then while it was restarting i sent the command again, and as soon as it got to the bootloader the command activated and worked instantly. now I'm toying around with this newfound knowledge and i think i have twrp working. just wiped phone again and installed AOSIP so here we go
Click to expand...
Click to collapse
Sorry... I didn't read...
When you are stuck at waiting for device .. if you unplug... Run the command... And then plug in... It will sometimes take...
Why... I don't know
Sent from my PH-1 using Tapatalk
Ricx94 said:
so I'm not sure why i tried this but it seemed to work...
I sent the flash command and when it got to the part it normally freezes at, i restarted the bootloader using volume and power keys on the phone. then while it was restarting i sent the command again, and as soon as it got to the bootloader the command activated and worked instantly. now I'm toying around with this newfound knowledge and i think i have twrp working. just wiped phone again and installed AOSIP so here we go
Click to expand...
Click to collapse
Nice to hear! Be sure to have the twrpinstaller.zip handy to flash after the ROM!! This preserves twrp.
rignfool said:
Sorry... I didn't read...
When you are stuck at waiting for device .. if you unplug... Run the command... And then plug in... It will sometimes take...
Why... I don't know
Click to expand...
Click to collapse
I need to send the command while the bootloader is restarting. It works consistently for me. Unplugging and repluging won't do it; only restarting bootloader. I honestly can't explain it but it's working great.
Ricx94 said:
I need to send the command while the bootloader is restarting. It works consistently for me. Unplugging and repluging won't do it; only restarting bootloader. I honestly can't explain it but it's working great.
Click to expand...
Click to collapse
HOLY CRAP THANK YOU
I've been going insane and this worked for whatever reason. You are awesome!
Zach Alt said:
HOLY CRAP THANK YOU
I've been going insane and this worked for whatever reason. You are awesome!
Click to expand...
Click to collapse
Glad i could be of service
Hi everyone, i have an Oneplus 8 pro BA european one.
I was in 10.5.6 rooted and with xXx rom 11.0
I did this to install 10.5.8 update:
Before all Disable all magisk modules
- Update the Rom: settings> System> System upgrade. WITHOUT REBOOT;
- Open Magisk Manager;
- In Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
After reboot magisk seems to be unnistalled:
https://ibb.co/55hJjwH
And also i cant enter into bootloader, i tried first selecting bootloader mode after pressing power buttom,
but in enters in recovery mode not bootloader mode. Then i tried to use ADB commands, adb reboot bootloder. It goes
into recovery again. Finally i tried to select bootloader mode in the recovery, but nothing...
Any idea?
https://youtu.be/mWpstCqT5gw
jumpet said:
Click to expand...
Click to collapse
Isn't that the bootloader itself???
Nandan.R.D said:
Isn't that the bootloader itself???
Click to expand...
Click to collapse
The category of the video is comedy .....
mohammed510 said:
The category of the video is comedy .....
Click to expand...
Click to collapse
:silly::silly::silly:
Nandan.R.D said:
Isn't that the bootloader itself???
Click to expand...
Click to collapse
It is
Lol? comical vid...
Why this thread exists?
Nandan.R.D said:
Isn't that the bootloader itself???
Click to expand...
Click to collapse
didnt knew it was, cause i did fasboot list devices command and nothing happens.
People use to laught at you instead help you btw. Very sad life they have.
[/QUOTE]And also i cant enter into bootloader, i tried first selecting bootloader mode after pressing power buttom,
but in enters in recovery mode not bootloader mode. Then i tried to use ADB commands, adb reboot bootloder. It goes
into recovery again. Finally i tried to select bootloader mode in the recovery, but nothing...
Any idea?[/QUOTE]
Hm...I'm in a similar constellation, after update to 10.5.8 I lost magisk and so root. Somehow the extraction of 10.5.8's boot.img and conversion into magisk_patched.img didn't help me regain boot, but ends in crashdump. But from here, I always can get back to bootloader with long pressing vol+ and power, when screen turns black let go both buttons and immediately press vol- and power which brings me back to recovery, from here into bootloader. reflash stock boot.img and I'm fine, but still no root, of course.
ok now, did you try to simply reflash 10.5.8 from settings/system/systemupdate/local upgrade? :fingers-crossed::fingers-crossed::fingers-crossed:
jumpet said:
didnt knew it was, cause i did fasboot list devices command and nothing happens.
People use to laught at you instead help you btw. Very sad life they have.
Click to expand...
Click to collapse
You are getting in to bootloader , I saw some discussion on the how to root without twrp thread , go check there people are having same issue and I think it works for a dude there and mentioned how he did so :good:
I'm having the same problem. After trying this I get into the CrashDump Mode and can't get out no matter what. Tried to get into the recovery to get fastboot or something but it brings me back to CrashDump Mode. Anybody know how to fix this? kind of don't want a brick here with me... Thanks in advance!
RobotPanda0961 said:
I'm having the same problem. After trying this I get into the CrashDump Mode and can't get out no matter what. Tried to get into the recovery to get fastboot or something but it brings me back to CrashDump Mode. Anybody know how to fix this? kind of don't want a brick here with me... Thanks in advance!
Click to expand...
Click to collapse
you saw my above post? I can always get back to stock recovery like this :fingers-crossed:
jomansch said:
you saw my above post? I can always get back to stock recovery like this :fingers-crossed:
Click to expand...
Click to collapse
I can get into fastboot actually by holding both volume buttons but as soon as I try to get into recovery the screen stays black and my PC says USB device not recognized. I flashed the stock boot image from 10.5.6 but it didn't work as it just goes back to CrashDump Mode...
RobotPanda0961 said:
I can get into fastboot actually by holding both volume buttons but as soon as I try to get into recovery the screen stays black and my PC says USB device not recognized. I flashed the stock boot image from 10.5.6 but it didn't work as it just goes back to CrashDump Mode...
Click to expand...
Click to collapse
try flashing the stock boot.img to both slots ... fastboot set_active (slot), do this for each slot. then fastboot flash boot boot.img (in my case it doesn't matter which slot is set active, my OP8pro does boot anyway). then fastboot boot boot.img. good luck:fingers-crossed:
jomansch said:
try flashing the stock boot.img to both slots ... fastboot set_active (slot), do this for each slot. then fastboot flash boot boot.img (in my case it doesn't matter which slot is set active, my OP8pro does boot anyway). then fastboot boot boot.img. good luck:fingers-crossed:
Click to expand...
Click to collapse
Thank You SO MUCH. I had to set the active slot to slot b in my case and like you said flash the stock boot.img and booted right up! Again, Thank you so much!
i want to move to lineageos from the custom rom, but i have this problem, tried to google solutions in different ways but i can't find people with the same issue.
phone works fine otherwise, but when i have it completetly OFF and try to start it by holding power+voldown keys i go into fastboot (i can tell cuz if i dont touch it it stays on a black screen with lil to no light). and as soon as i press the power key (effectively choosing to do a reboot), it powers off and on and goes on to boot my old config.
btw i have enabled OEM and usb debugging. but i haven't got root access cuz it's my understanding that to get that i need to do some things to it in fastboot hooked up to a pc with ADB minimal.
any ideas?
hello there! I have the exactly same issue here.. Volume DOWN + Power goes to black screen....
However i could find out that it is, indeed entering in the fastboot as i was able to send commands and unlock the bootloader through the CMD.. But now i cannot get to install the TWRP (get some error). Did you solved it? anyone can help?
alexestanislau said:
hello there! I have the exactly same issue here.. Volume DOWN + Power goes to black screen....
However i could find out that it is, indeed entering in the fastboot as i was able to send commands and unlock the bootloader through the CMD.. But now i cannot get to install the TWRP (get some error). Did you solved it? anyone can help?
Click to expand...
Click to collapse
i just figured it out, what commands are u using to install twrp?
well, for anyone in the future wondering about this **** u gotta make sure the usb port in your pc is 2.0, a 3.0 will return failed access to the unlock data or the flash boot command for twrp
and u gotta use >fastboot flash boot ''twrp file name''.img
also, for this specific model evert or moto g6 plus if u using the lineage official release make sure the number after the mindthegapps file matches your version of android, i ****ed that up many times until i realized i was trying to install MTG 10 in android 13. what a ****head am i!
oh, and finally if u are in fastboot and can't see anything, the path to recovery (and hopefully twrp) is to press 2 times voldown and 1 time power
vesp9 said:
well, for anyone in the future wondering about this **** u gotta make sure the usb port in your pc is 2.0, a 3.0 will return failed access to the unlock data or the flash boot command for twrp
and u gotta use >fastboot flash boot ''twrp file name''.img
also, for this specific model evert or moto g6 plus if u using the lineage official release make sure the number after the mindthegapps file matches your version of android, i ****ed that up many times until i realized i was trying to install MTG 10 in android 13. what a ****head am i!
oh, and finally if u are in fastboot and can't see anything, the path to recovery (and hopefully twrp) is to press 2 times voldown and 1 time power
Click to expand...
Click to collapse
Also, in other topic they pointed out that some Moto G6 Plus have only ONE partition, so you cannot FLASH a recovery (because they dont have a partition for that).. you can ONLY boot on TWRP, if you Flash the TWRP on the partition you cant have a OS at same time..
vesp9 said:
well, for anyone in the future wondering about this **** u gotta make sure the usb port in your pc is 2.0, a 3.0 will return failed access to the unlock data or the flash boot command for twrp
and u gotta use >fastboot flash boot ''twrp file name''.img
also, for this specific model evert or moto g6 plus if u using the lineage official release make sure the number after the mindthegapps file matches your version of android, i ****ed that up many times until i realized i was trying to install MTG 10 in android 13. what a ****head am i!
oh, and finally if u are in fastboot and can't see anything, the path to recovery (and hopefully twrp) is to press 2 times voldown and 1 time power
Click to expand...
Click to collapse
Tried to do that, but stills black screen after 2 volume down plus power
alexestanislau said:
Tried to do that, but stills black screen after 2 volume down plus power
Click to expand...
Click to collapse
u want to enter twrp? make sure a copy of the file its on sd and do ''fastboot devices'' first to make sure connection is ok. then ''fastboot boot (twrp.img)''
changing twrp.img to the exact name of your file. on usb 2.0 or it won't work
vesp9 said:
well, for anyone in the future wondering about this **** u gotta make sure the usb port in your pc is 2.0, a 3.0 will return failed access to the unlock data or the flash boot command for twrp
and u gotta use >fastboot flash boot ''twrp file name''.img
also, for this specific model evert or moto g6 plus if u using the lineage official release make sure the number after the mindthegapps file matches your version of android, i ****ed that up many times until i realized i was trying to install MTG 10 in android 13. what a ****head am i!
oh, and finally if u are in fastboot and can't see anything, the path to recovery (and hopefully twrp) is to press 2 times voldown and 1 time power
Click to expand...
Click to collapse
I have the same issue.
After it boots into TWRP, the screen correctly display TWRP or is still black?
Tiki Thorsen said:
I have the same issue.
After it boots into TWRP, the screen correctly display TWRP or is still back?
Click to expand...
Click to collapse
it correctly displays TWRP, it's black just in fastboot.
u can use adb while in fastboot to order it to boot twrp, that's how i did it. or i guess u could hypothetically make it go into recovery mode (twrp if installed) by moving blindly using vol + or - but i'm not sure.
vesp9 said:
it correctly displays TWRP, it's black just in fastboot.
u can use adb while in fastboot to order it to boot twrp, that's how i did it. or i guess u could hypothetically make it go into recovery mode (twrp if installed) by moving blindly using vol + or - but i'm not sure.
Click to expand...
Click to collapse
Oh that's a relief! I was planing unlock the bootloader and flash LineageOS this weekend. I will report back how it goes.
Tiki Thorsen said:
Oh that's a relief! I was planing unlock the bootloader and flash LineageOS this weekend. I will report back how it goes.
Click to expand...
Click to collapse
remember to use usb 2.0 (not 3.0). this made me waste so much time
vesp9 said:
remember to use usb 2.0 (not 3.0). this made me waste so much time
Click to expand...
Click to collapse
Indeed, I struggle with that on my G7 Plus, cheers!
Update; After successfully unlocking the bootloader, I boot to the Pixel Experience recovery and the screen remains black.
But if I boot to TWRP, it does display it correctly.
Tiki Thorsen said:
Update; After successfully unlocking the bootloader, I boot to the Pixel Experience recovery and the screen remains black.
But if I boot to TWRP, it does display it correctly.
Click to expand...
Click to collapse
i'm guessing the pixel experience recovery is a custom recovery mode, right? maybe the black screen it's a thing with factory menus? idk
vesp9 said:
i'm guessing the pixel experience recovery is a custom recovery mode, right? maybe the black screen it's a thing with factory menus? idk
Click to expand...
Click to collapse
Yes, is just like the LineageOS recovery.
I always replace the Rom's recovery with TWRP in any case.