Related
Anyone else have this problem?
numus said:
Anyone else have this problem?
Click to expand...
Click to collapse
So is fastboot the problem or are you trying to boot to recovery through the bootloader. I would use ADB instead of fastboot. But if what you're asking is that you want to boot to recovery from the bootloader, just connect your USB cable to your computer and then select recovery in the bootloader.
CharliesTheMan said:
So is fastboot the problem or are you trying to boot to recovery through the bootloader. I would use ADB instead of fastboot. But if what you're asking is that you want to boot to recovery from the bootloader, just connect your USB cable to your computer and then select recovery in the bootloader.
Click to expand...
Click to collapse
Pretty sure it is fastboot... You use the volume rocker to select recovery and hit the power button... It shows the Bootscreen but doesn't go any further than that.
Edit: it says in red FASTBOOT MODE.. When i select recovery it goes tot he google screen (witht he unlock icon) and doesn't go any further than that.
numus said:
Anyone else have this problem?
Click to expand...
Click to collapse
I'm having trouble too. I have it plugged in to my laptop. When I select "Recovery" and press Power, it just reboots, and then boots into Android.
No recovery.
So I'm gonna try TWRP..
i had the same issue this is what i did
download new recovery h**p://goo.im/devs/OpenRecovery/grouper/openrecovery-twrp-2.2.1.4-grouper.img
then in fastboot
fastboot erase recovery
fastboot flash recovery name_of_recovery.img
wait 15 seconds
unplug usb cable
then use volume keys to boot in to recovery
hope this helps
so any solution at the same screen, same problem.
dj_denims said:
i had the same issue this is what i did
download new recovery h**p://goo.im/devs/OpenRecovery/grouper/openrecovery-twrp-2.2.1.4-grouper.img
then in fastboot
fastboot erase recovery
fastboot flash recovery name_of_recovery.img
wait 15 seconds
unplug usb cable
then use volume keys to boot in to recovery
hope this helps
Click to expand...
Click to collapse
You want to be in the bootloader mode and select recovery. The trick is that to do that, you have to have your Asus USB cable connected to a live usb port when you do it, and it usually works if recovery isn't damaged.
And you can also use Wug's toolkit on the computer, or if you can boot the tablet, you can use goo manager to reboot to recovery, or the Trinity kernel app, or your rom's advanced power menu.
With the USB cable attached from the computer to tablet, here's what I did:
- Went to bootloader
- Did "fastboot erase recovery"
- Did "fastboot flash recovery IMG"
- Then boot to recovery manually from the device itself via volume buttons and Power
Hasn't failed me yet when trying out different recoveries. There was some issue a while back where you had to have the USB cable hooked to your computer and Nexus 7 in order to get to recovery. Not sure if the bug still exists, but it may be worth trying with the cable in.
Also you probably have to have an unlocked bootloader (lock at bottom of Google boot screen).
dj_denims said:
i had the same issue this is what i did
download new recovery h**p://goo.im/devs/OpenRecovery/grouper/openrecovery-twrp-2.2.1.4-grouper.img
then in fastboot
fastboot erase recovery
fastboot flash recovery name_of_recovery.img
wait 15 seconds
unplug usb cable
then use volume keys to boot in to recovery
hope this helps
Click to expand...
Click to collapse
Thanks for that.
That worked for me
Does the USB port you're plugged into need to be a computer with the fastboot drivers already installed? My unit freezes up in bootloader every time I plug in any live USB cable, whether it's a computer or not. My recovery is fine, but with the bootloader constantly freezing I'm not able to install the N7 drivers on my computer, let alone input any fastboot commands. And no, I don't have access to the computer with the drivers already installed sadly.
Sent from my SGH-T989 using xda premium
Turn it off plug USB lead into PC/laptop and nexus hold volume up and down and turn it on, or it also works via my otg cable in my s3 also, its a bug..
Sent from my Nexus 7 using Tapatalk 2
a stupid bug.buoght yesterday,rooted and unlocked.downloaded 10 roms,all kernels,and now that i'm ok to begin test i tried without luck to enter recovery from fastboot (i didn't know this fact)but my cable was inserted on pc usb port...and strange it doesn't work.yestrerday via fastboot i flashed twrp recovery that i love and use also on mine gnexs.i'm on stock rom yet,and without "reboot to recovery" option in powermenu.i reflashed twrp,cwm touch (in fastboot manually)then the same but with a rootkit,no luck.i began to think i have a problem in my device and i don't know how to do because it's a secondary bug for assistance i think..and i read this post.don't even tried commands in few posts ago,already did same things an hour ago.i installed quickboot frm playstore and now i can boot on TWRP.use this for today,when i begin to test roms i'll have the powermenu option!
Sad this,i'm a bit anxious of this bug,because i soft brick gnex every 2\3 days,always trying things and stuff,kernel with modifications by me etc,and i often have to go in cwm via devices off and fastboot before...i see that my tab attacched at pc don't enter recovery from fastboot mode..and it's a problem for me.hope someone discover where is this bug and find a workaround\fix fro that.
cheers
sert00 said:
a stupid bug.buoght yesterday,rooted and unlocked.downloaded 10 roms,all kernels,and now that i'm ok to begin test i tried without luck to enter recovery from fastboot (i didn't know this fact)but my cable was inserted on pc usb port...and strange it doesn't work.yestrerday via fastboot i flashed twrp recovery that i love and use also on mine gnexs.i'm on stock rom yet,and without "reboot to recovery" option in powermenu.i reflashed twrp,cwm touch (in fastboot manually)then the same but with a rootkit,no luck.i began to think i have a problem in my device and i don't know how to do because it's a secondary bug for assistance i think..and i read this post.don't even tried commands in few posts ago,already did same things an hour ago.i installed quickboot frm playstore and now i can boot on TWRP.use this for today,when i begin to test roms i'll have the powermenu option!
Sad this,i'm a bit anxious of this bug,because i soft brick gnex every 2\3 days,always trying things and stuff,kernel with modifications by me etc,and i often have to go in cwm via devices off and fastboot before...i see that my tab attacched at pc don't enter recovery from fastboot mode..and it's a problem for me.hope someone discover where is this bug and find a workaround\fix fro that.
cheers
Click to expand...
Click to collapse
Paragraphs dude? Or at the very least, proper spacing.
On stock rooted rom, flash latest TWRP recovery. openrecovery-twrp-2.2.2.0-grouper.img
adb reboot bootloader
fastboot flash recovery openrecovery-twrp-2.2.2.0-grouper.img
Then install Rom Toolbox. Use the "Rebooter" to Reboot recovery, and you should have no issues.
..
mvmacd said:
Paragraphs dude? Or at the very least, proper spacing.
On stock rooted rom, flash latest TWRP recovery. openrecovery-twrp-2.2.2.0-grouper.img
adb reboot bootloader
fastboot flash recovery openrecovery-twrp-2.2.2.0-grouper.img
Then install Rom Toolbox. Use the "Rebooter" to Reboot recovery, and you should have no issues.
Click to expand...
Click to collapse
I did this and I still can't boot into recovery. The only way I can boot into recovery is if I use the fastboot command. The rom toolbox does not work for me.
similar problem
I have somewhat similar problem. Well, actually the problem is not very uncommon the way it looks, but usual solutions do not work.
Basically I have erased my old rom (rebooted to recovery from aokp menu) and erased my rom. I've tried mounting the device from the recovery mode, but it was not recognised on my PC. I assumed that this was an Win8 issue.
Once I've rebooted, I could no logger boot to recovery (after selecting recovery all I got was google logo). I've thought of flashing recovery via fastboot, but bootloader seams to freeze with usb cable in (no matter the cable) and resetting does not help (the way it helped others). Also I cannot fastboot at that time either as PC (neither win8 nor win7 machine can see the device).
Any ideas would be appreciated.
When the bootloader freezes with the usb cable plugged into a PC, it is a driver issue. Uninstall and reinstall the drivers. I have experienced this on a win7 x64 system.
It isn't a driver issue as the same thing happens when connecting to a charger and not the PC.
It happens on mine as well.
Well it wouldn't crash with wall charger if it was a PC driver issue.
In either case, I've actually figured out what's the problem. It seems that usb connector is not very reliable. If the it usb connection is poor, the bootloader crashes. To avoid this issue you have to bend the cable towards the screen to ensure the proper connection. It load that way just fine.
Edit: or not... probably bending just removed the connection completely...
Edit2: did not figure out what was the problem, but after playing around some more, the phone has popped up in computer manager and I was able to continue from there. After flashing the recovery (twm -> cwm), the bootloader un-froze as well.
I'm not new to clockwork recovery, and I have flashed many Roms on my Nexus 7........ today I did a full back up of my latest ROM and I downloaded the latest version of the bug less beast .....I let rom manager do the back up and flash......then there was an error flashing the new rom and an abort and a reboot.......no im stuck on the google screen with the little un-locked lock at the bottom of the screen......if I reboot and go into recovery it just goes back to the google screen and stays there.....any clue as what I should do ??
Search around the forums for solutions.
Use the Wugs toolkit to make your work easier.
It's not bricked its standard procedure you just need to plug it in
Sent from my ADR6425LVW using xda premium
download .zip from google and restore it to your tablet (this is full wipe)
a1exus said:
download .zip from google and restore it to your tablet (this is full wipe)
Click to expand...
Click to collapse
To manually enter recovery from the bootloader on devices prior to 4.1.2 (don't know if it was fixed. its a glitch from google in the bootloader) you must have the USB (OEM of course) connected to a USB port on the computer. Then you can boot to bootloader and use the volume buttons to enter recovery. It may take trying a few times, like connect to usb port before powering on, connect to USB port once you're in the bootloader, etc, but that's your only issue unless when you panicked you tried some other solutions.
CharliesTheMan said:
To manually enter recovery from the bootloader on devices prior to 4.1.2 (don't know if it was fixed. its a glitch from google in the bootloader) you must have the USB (OEM of course) connected to a USB port on the computer. Then you can boot to bootloader and use the volume buttons to enter recovery. It may take trying a few times, like connect to usb port before powering on, connect to USB port once you're in the bootloader, etc, but that's your only issue unless when you panicked you tried some other solutions.
Click to expand...
Click to collapse
My recovery is not working I flashed clockwork mod and something happened to the recovery.....its like it not there....there is an option for it but when I enter it it just goes back to the google screen
GCSM said:
My recovery is not working I flashed clockwork mod and something happened to the recovery.....its like it not there....there is an option for it but when I enter it it just goes back to the google screen
Click to expand...
Click to collapse
dude, i'm told you what you need to do, i had erased manually my bootloader,recover,system,data and i was able to restore w/ what i told you it worked w/out any issues
Get fastboot. plug into your computer and do these:
fastboot flash recovery recovery.img (recovery.img is whatever file you have for recovery. IMO, get the newest touch recovery from CWM and have it in the same directory as fastboot)
fastboot reboot-bootloader
From there, leave it PLUGGED IN and get back into recovery. Worked for me.
Could someone please help.
I've just updated from KK 4.4.4. to Lp 5.0.1 via OTA updates.
Then I tried to install TWRP 2.8.6.0 using Odin 3.10.6 (and 3.09), but I can't boot into TWRP, it just goes into Android System Recovery (or whatever it's called).
Before I updated, I could successfully use TWRP, root and create/restore backups etc. But, since the OS update I can't (plus I will have lost root, as I downloaded/installed the KK ROM as a "clean install".
From looking around various sites and watching videos. I think I need to side load TWRP using ADB.
But, I've visited the Dev. site, downloaded the SDK zip files. Extracted them, but the folder that should contain the files (platforms) is empty.
So, I downloaded the exe file. It wouldn't allow me to install it as I don't have Java installed.
I downloaded and tried to install Java, but it fails to install. Just F typical.
Could someone offer an easy to follow step by step advice and maybe post the files I need to use (if I do need to use ADB).
I'm using 910F and USB debugging is allowed.
Thank you.
************ EDIT ************
Never mind. I had to flash the Lp 5.0.1 stock ROM to fix the problem and now TWRP works.
******************************
Is reactivation lock enabled? If yes, disable and try again
abdyasar said:
Is reactivation lock enabled? If yes, disable and try again
Click to expand...
Click to collapse
abdyasar said:
Is reactivation lock enabled? If yes, disable and try again
Click to expand...
Click to collapse
Thank you for your help.
The reactivation lock is disabled.
To update my OP, other things I've tried:
I've downloaded and installed the basic files for ADB as well as the full SDK.
Some site say to update the ADB files to the Google USB Drivers (found in the SDK). It just says I'm up to date when I try to find newer drivers via Device Manager.
Tried flashing CWM instead of TWRP using Odin.
Tried installing TWRP (zip) when in the Android System Recovery mode via SD card.
When using ADB. My device is listed when I type "adb devices".
But when I type "fastboot flash recovery <the name of the TWRP file .IMG> I just get "waiting for device".
I get this message if I'm in Bootloader mode or using the phone "normally".
Hopefully it works out
Firstly download TWRP from the website : https://dl.twrp.me/trltexx/twrp-2.8.6.0-trltexx.img.tar.html
Then turn your device off and remove the battery for around 10 seconds (make sure the device isn't connected to any charger or anything via the USB cable).
Then after the 10 seconds put the battery back into the device and hold the home, volume down and power button.
Once you are in download mode and it says 'Downloading', plug your device into computer using the USB cable.
Open up Odin as admin and make sure no security software is interfering; once your device shows up in Odin select 'PDA' and then browse to the directory of the recovery file.
Then press start, however while it's flashing press the volume up and home button and this should boot the device directly into recovery. This is important as sometimes stock firmware might revert to stock recovery if you don't boot into recovery at least once.
I hope this helps you out.
UPDATE:
Crap, I didn't read that it worked out XD Ignore me ;P
Battlehero said:
Firstly download TWRP from the website : https://dl.twrp.me/trltexx/twrp-2.8.6.0-trltexx.img.tar.html
Then turn your device off and remove the battery for around 10 seconds (make sure the device isn't connected to any charger or anything via the USB cable).
Then after the 10 seconds put the battery back into the device and hold the home, volume down and power button.
Once you are in download mode and it says 'Downloading', plug your device into computer using the USB cable.
Open up Odin as admin and make sure no security software is interfering; once your device shows up in Odin select 'PDA' and then browse to the directory of the recovery file.
Then press start, however while it's flashing press the volume up and home button and this should boot the device directly into recovery. This is important as sometimes stock firmware might revert to stock recovery if you don't boot into recovery at least once.
I hope this helps you out.
UPDATE:
Crap, I didn't read that it worked out XD Ignore me ;P
Click to expand...
Click to collapse
Thanks for the reply.
Yes, I did fix it by re-flashing.
But, the info will be useful if I get into a similar situation again. Or will help anyone else who's stuck.
Hi,
I rooted my ZTE Axon 7 UK version, A2017G and i accidentally formatted the system, currently i have the US version of the software running but i dont have any WIFI
thanks for the help in advance
Can't help you with the European system
But have you tried flashing B20 boot.img from tenfar tool ? Might solve your wifi issue...
If that works, it's awesome !
shia786 said:
Hi,
I rooted my ZTE Axon 7 UK version, A2017G and i accidentally formatted the system, currently i have the US version of the software running but i dont have any WIFI
thanks for the help in advance
Click to expand...
Click to collapse
djona12 said:
Can't help you with the European system
But have you tried flashing B20 boot.img from tenfar tool ? Might solve your wifi issue...
If that works, it's awesome !
Click to expand...
Click to collapse
the A2017G have a FULL FACTORY UPDATE IMAGE (B02) you guys are actually lucky in that department, us A2017U we wish had one.
here : http://forum.xda-developers.com/axon-7/how-to/a2017g-b02-update-released-europe-t3440619
i cannot seem to find tenfar tool anywhere
DrakenFX said:
the A2017G have a FULL FACTORY UPDATE IMAGE (B02) you guys are actually lucky in that department, us A2017U we wish had one.
here : http://forum.xda-developers.com/axon-7/how-to/a2017g-b02-update-released-europe-t3440619
Click to expand...
Click to collapse
i have found the tool but i think i flashed the US version of the boot image now my phone does not boot up at all,
it goes to stock recovery
if i turn the phone on then it goes to ZTE LOGO for about half a second then the screen goes blank
i can access fastboot but only through stock recovery which when i go to bootloader i cannot run any fastboot commands, even if i run fastboot reboot it does not reboot the phone at all
shia786 said:
i cannot seem to find tenfar tool anywhere
Click to expand...
Click to collapse
Got the same problem, i've formatted the system and now i can only go to the stock recovery, i can't reboot to edl mode by pressing both volume buttons doing this a Handset Diagnostic Interface (DFU) appears in my Device Manager instead of Qualcomm USB device, so i can't install a TWRP.
shia786 said:
i cannot seem to find tenfar tool anywhere
Click to expand...
Click to collapse
Cricius said:
Got the same problem, i've formatted the system and now i can only go to the stock recovery, i can't reboot to edl mode by pressing both volume buttons doing this a Handset Diagnostic Interface (DFU) appears in my Device Manager instead of Qualcomm USB device, so i can't install a TWRP.
Click to expand...
Click to collapse
As I said before, YOU GUYS have full update file posted the link (thread) about... You DON'T need @tenfar tools to use the FULL A2017G update (B02) , download the file (like 2.2gb I guess) and flashed using stock recovery.
DrakenFX said:
As I said before, YOU GUYS have full update file posted the link (thread) about... You DON'T need @tenfar tools to use the FULL A2017G update (B02) , download the file (like 2.2gb I guess) and flashed using stock recovery.
Click to expand...
Click to collapse
When I press update from SD card it comes up with cannot update from SD card, when I try to do ADB side load and says cannot read file
shia786 said:
When I press update from SD card it comes up with cannot update from SD card, when I try to do ADB side load and says cannot read file
Click to expand...
Click to collapse
Try enable " OEM Unlocking " under developers option and try again
DrakenFX said:
Try enable " OEM Unlocking " under developers option and try again
Click to expand...
Click to collapse
I cannot access the software at all, all I got is stock recovery
shia786 said:
I cannot access the software at all, all I got is stock recovery
Click to expand...
Click to collapse
Try using that same full update with twrp,
As title said you can boot only to TWRP? From there you may be able to flash the zip.
DrakenFX said:
Try using that same full update with twrp,
As title said you can boot only to TWRP? From there you may be able to flash the zip.
Click to expand...
Click to collapse
I no longer have access to TWRP recovery as I flashed stock recovery to install the firmware file using stock recovery but somehow the os got screwed up and now the only thing I have access to is stock recovery
shia786 said:
I no longer have access to TWRP recovery as I flashed stock recovery to install the firmware file using stock recovery but somehow the os got screwed up and now the only thing I have access to is stock recovery
Click to expand...
Click to collapse
You can just boot into TWRP using tenfar tools and Flash the zip.
DrakenFX said:
You can just boot into TWRP using tenfar tools and Flash the zip.
Click to expand...
Click to collapse
For me to use the tool I need to access the phone in edl mode which I cannot do because I do not have access to ADB
shia786 said:
For me to use the tool I need to access the phone in edl mode which I cannot do because I do not have access to ADB
Click to expand...
Click to collapse
and not having access to adb, you meant don't have a PC/Laptop?
Cuz there is an alternative way how to boot to " edl "
- turn your phone completely off
- press and hold Volume DOWN & UP
- plug your device to your PC/Laptop
DrakenFX said:
and not having access to adb, you meant don't have a PC/Laptop?
Cuz there is an alternative way how to boot to " edl "
- turn your phone completely off
- press and hold Volume DOWN & UP
- plug your device to your PC/Laptop
Click to expand...
Click to collapse
so what i mean by i cannot access ADB is that the phone has stock recovery in which there is no ADB functionality, i cannot access the OS so i cannot use ADB that way either,
i tried the method above to go into edl mode but it just goes onto a black screen where the led light flashed red and green and the computer does not recognise anything being plugged in, not even the system sound,
I have the correct drivers installed as i used his before when the OS was working
shia786 said:
so what i mean by i cannot access ADB is that the phone has stock recovery in which there is no ADB functionality, i cannot access the OS so i cannot use ADB that way either,
i tried the method above to go into edl mode but it just goes onto a black screen where the led light flashed red and green and the computer does not recognise anything being plugged in, not even the system sound,
I have the correct drivers installed as i used his before when the OS was working
Click to expand...
Click to collapse
Hi,
I have the exact same issue
Did you find a way to get your phone booting again ?
DrakenFX said:
and not having access to adb, you meant don't have a PC/Laptop?
Cuz there is an alternative way how to boot to " edl "
- turn your phone completely off
- press and hold Volume DOWN & UP
- plug your device to your PC/Laptop
Click to expand...
Click to collapse
That doesn't work on the A2017G, you have to use "adb reboot edl", so you see the problem. Also, the A2017G doesn't actually have an EDL mode but something very similar that's ZTE call Handset diagnostic Interface - quite why, who knows, this is ZTE after all...
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.