Hi,
I am trying to get Lineage installed on my Oppo R7 Plus although I've run in to a snag and have been googling and going round in circles all day trying to find a solution. All the guides state to go in to recovery mode or bootloader, however my device doesn't have this. I understand Oppo released an update which removed the bootloader thus making it impossible to flash with a different ROM. One work around I've read is to flash an older version of ColorOS, and I have downloaded this from a link in another thread. However this still poses the same problem, I cannot flash it, as you need fastboot to do so, which is the problem, as I cant do this.... catch 22 !
Does anyone have a solution for this or should I just give up and sell the unit on Ebay ?
Any help appreciated.
This is a link to a color os with an unlockable bootloader. Place it in the root of your internal SD. Boot into recovery and flash with color is recovery. After flashing you can boot into fastboot and run fastboot OEM unlock and flash twrp. Only for r7plusf.
https://www.dropbox.com/s/xmh77xyinz2iero/R7plusfEX_11_OTA_012_all_201512251816.zip?dl=0
kishd said:
This is a link to a color os with an unlockable bootloader. Place it in the root of your internal SD. Boot into recovery and flash with color is recovery. After flashing you can boot into fastboot and run fastboot OEM unlock and flash twrp. Only for r7plusf.
Hi,
Thanks for the info but I can't boot in to recovery and flash, as the latest OS doesnt let me, which is the issue I am having, unless I've missed something?
Click to expand...
Click to collapse
Switch the phone off. Hold volume down and power until the oppo logo appears and it should boot into recovery.
I have used all the official firmware versions for this phone and they all allow booting into recovery.
=
kishd said:
Switch the phone off. Hold volume down and power until the oppo logo appears and it should boot into recovery.
I have used all the official firmware versions for this phone and they all allow booting into recovery.
Click to expand...
Click to collapse
I've tried this and it doesnt work, it never boots in to recovery. Ive also used ADB using adb reboot bootloader and other commands with no joy. From what I ascertained from reading other threads and posts elsewhere this is due to OPPO updating the OS and removing the option to do this. If you have their latest OS, you're pretty stuck., which I am Just wondered if there was any way around this before I gave up.
Edit: Just tried this one final time and it worked !! All the guides say hold volume up and power, not volume DOWN. Thanks very much for the input
Once you have flashed the older firmware you can hold volume up and power to get into fastboot to flash twrp
kishd said:
This is a link to a color os with an unlockable bootloader. Place it in the root of your internal SD. Boot into recovery and flash with color is recovery. After flashing you can boot into fastboot and run fastboot OEM unlock and flash twrp. Only for r7plusf.
https://www.dropbox.com/s/xmh77xyinz2iero/R7plusfEX_11_OTA_012_all_201512251816.zip?dl=0
Click to expand...
Click to collapse
Sir do you have this firmware for oppo f1 plus
---------- Post added at 08:24 AM ---------- Previous post was at 08:21 AM ----------
kishd said:
This is a link to a color os with an unlockable bootloader. Place it in the root of your internal SD. Boot into recovery and flash with color is recovery. After flashing you can boot into fastboot and run fastboot OEM unlock and flash twrp. Only for r7plusf.
https://www.dropbox.com/s/xmh77xyinz2iero/R7plusfEX_11_OTA_012_all_201512251816.zip?dl=0
Click to expand...
Click to collapse
Sir do you this firmasre for oppo f1 plus?
kishd said:
Switch the phone off. Hold volume down and power until the oppo logo appears and it should boot into recovery.
I have used all the official firmware versions for this phone and they all allow booting into recovery.
Click to expand...
Click to collapse
oppo ax7? im trying to root my ax7
kishd said:
This is a link to a color os with an unlockable bootloader. Place it in the root of your internal SD. Boot into recovery and flash with color is recovery. After flashing you can boot into fastboot and run fastboot OEM unlock and flash twrp. Only for r7plusf.
https://www.dropbox.com/s/xmh77xyinz2iero/R7plusfEX_11_OTA_012_all_201512251816.zip?dl=0
Click to expand...
Click to collapse
Thank you @kishd this was helpful, even 2 years later...
Related
Hi guys! Im on 4.4.4 with unlocked bootloader, the only way to root this device that i found on the internet is to use locked bootloader tutorials.
Is there any easy way to root unlocked bootloader D2303 on 4.4.4 18.3.1.C.1.15? I tried flashtool but when it installs towel root and i press make it rain! it says this device is not supported. Thanks in advance!
Here is one easiest way, but its over chinese app called KingRoot.
1. Download latest KingRoot.
2. Press Root button
3. Allow USB debug in Developer settings(Tap 10 times in Phone info on Build number to get Dev. settings)
4. Install Philz Recovery
5. Flash SuperSU V.249 BETA! Important!
6. Flash RICDefeat.zip
Same way is described here
http://forum.xda-developers.com/xperia-m2/general/how-to-permanently-root-xperia-m2-t3106534
But dont forget to flash SuperSU V2.49 BETA and RICDefeat & remove KingRoot apps.
Lothgar said:
Hi guys! Im on 4.4.4 with unlocked bootloader, the only way to root this device that i found on the internet is to use locked bootloader tutorials.
Is there any easy way to root unlocked bootloader D2303 on 4.4.4 18.3.1.C.1.15? I tried flashtool but when it installs towel root and i press make it rain! it says this device is not supported. Thanks in advance!
Click to expand...
Click to collapse
Update your bootloader using emma, then flash a recovery like CM12.1 Recovery from here: http://www.mediafire.com/download/lfub133wy5833bx/recovery.img and flash with it SuperSU zip and RICdefeat. Then you're done.
---------- Post added at 12:06 ---------- Previous post was at 12:05 ----------
Enycz11 said:
Here is one easiest way, but its over chinese app called KingRoot.
1. Download latest KingRoot.
2. Press Root button
3. Allow USB debug in Developer settings(Tap 10 times in Phone info on Build number to get Dev. settings)
4. Install Philz Recovery
5. Flash SuperSU V.249 BETA! Important!
6. Flash RICDefeat.zip
Same way is described here
http://forum.xda-developers.com/xperia-m2/general/how-to-permanently-root-xperia-m2-t3106534
But dont forget to flash SuperSU V.249 BETA and RICDefeat & remove KingRoot apps.
Click to expand...
Click to collapse
Actually that's a locked bootloader method.
And Kingroot also sends your IMEI info to chinese unknown servers...
linuxct said:
Update your bootloader using emma, then flash a recovery like CM12.1 Recovery from here: http://www.mediafire.com/download/lfub133wy5833bx/recovery.img and flash with it SuperSU zip and RICdefeat. Then you're done.
---------- Post added at 12:06 ---------- Previous post was at 12:05 ----------
Actually that's a locked bootloader method.
And Kingroot also sends your IMEI info to chinese unknown servers...
Click to expand...
Click to collapse
Thanks! Trying right now!
linuxct said:
Update your bootloader using emma, then flash a recovery like CM12.1 Recovery from here: http://www.mediafire.com/download/lfub133wy5833bx/recovery.img and flash with it SuperSU zip and RICdefeat. Then you're done.
---------- Post added at 12:06 ---------- Previous post was at 12:05 ----------
Actually that's a locked bootloader method.
And Kingroot also sends your IMEI info to chinese unknown servers...
Click to expand...
Click to collapse
Wait! How to flash recovery? Via flashtool by androxyde or emma?
EDIT: Tryed via fastboot the cm12 recovery, all what i got is grey screen with blue lines yey.
Lothgar said:
Wait! How to flash recovery? Via flashtool by androxyde or emma?
EDIT: Tryed via fastboot the cm12 recovery, all what i got is grey screen with blue lines yey.
Click to expand...
Click to collapse
But you have to do a fastboot flash recovery recovery.img . Did you do that ?
linuxct said:
But you have to do a fastboot flash recovery recovery.img . Did you do that ?
Click to expand...
Click to collapse
Yep.
Lothgar said:
Yep.
Click to expand...
Click to collapse
Then there's no reason to happen that. The lines appear when you boot it normally or when you try to enter recovery by keep holding the Vol- button?
In my D2303 is fine working...
linuxct said:
Then there's no reason to happen that. The lines appear when you boot it normally or when you try to enter recovery by keep holding the Vol- button?
In my D2303 is fine working...
Click to expand...
Click to collapse
The phone is off. I press the power button it vibrates, then for 5-6 second the screen is black. Then the lines shows up and no boot. Vol- pressed or not is the same.
EDIT: Reflashed now only if i try to enter recovery the lines shows up!
Lothgar said:
The phone is off. I press the power button it vibrates, then for 5-6 second the screen is black. Then the lines shows up and no boot. Vol- pressed or not is the same.
Click to expand...
Click to collapse
Go in fastboot mode and run fastboot erase recovery .
Again, I see no reason why this could be happening as this recovery runs in it's partition, isolated, so if you don't run it (Vol- button from the beggining) then it should not interfere with device boot up. Try flashing the latest kernel from the .15 ftf also.
linuxct said:
Go in fastboot mode and run fastboot erase recovery .
Again, I see no reason why this could be happening as this recovery runs in it's partition, isolated, so if you don't run it (Vol- button from the beggining) then it should not interfere with device boot up. Try flashing the latest kernel from the .15 ftf also.
Click to expand...
Click to collapse
I reflashed the recovery trough fastboot and now only if i try to boot recovery the blue lines shows up. I think that is a problem of the recovery.
Lothgar said:
I reflashed the recovery trough fastboot and now only if i try to boot recovery the blue lines shows up. I think that is a problem of the recovery.
Click to expand...
Click to collapse
Maybe is a screen driver problem, but on a D2303?? For me it's working
linuxct said:
Maybe is a screen driver problem, but on a D2303?? For me it's working
Click to expand...
Click to collapse
I remember that you gave me and alternative recovery for the locked bootloader becouse the standard doesn't working. Maybe the same issue?
Lothgar said:
I remember that you gave me and alternative recovery for the locked bootloader becouse the standard doesn't working. Maybe the same issue?
Click to expand...
Click to collapse
No, it shouldn't as the problem only was the GPIO Keys... Not screen driver problem... But yes, looks like you can't use the CM Recovery.
Format your fastboot partition with fastboot erase recovery and use the locked bootloader procedure... What a pity.
linuxct said:
No, it shouldn't as the problem only was the GPIO Keys... Not screen driver problem... But yes, looks like you can't use the CM Recovery.
Format your fastboot partition with fastboot erase recovery and use the locked bootloader procedure... What a pity.
Click to expand...
Click to collapse
I'll try but i dont know how to get the root because the procedure of downgrading the kernel doesn't work i tryed several times!
Here what i got:
Lothgar said:
I'll try but i dont know how to get the root because the procedure of downgrading the kernel doesn't work i tryed several times!
Here what i got:
Click to expand...
Click to collapse
But that pic is from CM recovery or from kernel downgrade?
And in what step you get stuck in the kernel downgrade root method?...
linuxct said:
But that pic is from CM recovery or from kernel downgrade?
And in what step you get stuck in the kernel downgrade root method?...
Click to expand...
Click to collapse
CM recovery. If i downgrade the kernel the adb doesn't start! And yes is enabled in the settings.
EDIT: Solved trying now for the locked bootloader method!
Installed philz recovery with locked bootloader method but i cant flash omnirom! (status 7)
I was trying to get the latest twrp '2.8.7.2'. I downloaded it and flashed the img to recovery and nothing seemed to happen so I tried flashing it to boot then I tried to reboot the system. Now when I try to turn it on I get stuck on the Google like it is turning but it just gets stuck. I tried Charging it now when I charge it I get stuck on the battery logo. When I try booting it Booting it into recovery(twrp) I get a black screen. I can tell the Screen is on because of the dim glow it gives off but it is not doing anything. Note: I am some what of a noob when it comes to this stuff, My nexus 5 was running Marshmallow, and I was running the Xtra smooth rom (it is very close to stock). Plz help. I have also just found out that the reason im getting the bootloop is I flashed the wrong version of TWRP need a fix PLZ HELP.
Did you try flashing stock recovery or twrp 2.8.7.1?
audit13 said:
Did you try flashing stock recovery or twrp 2.8.7.1?
Click to expand...
Click to collapse
I cant flash anything because it is stuck. If you can tell me how to do that it would be great. also I gave you the thanks thing.
Judah04 said:
I cant flash anything because it is stuck. If you can tell me how to do that it would be great. also I gave you the thanks thing.
Click to expand...
Click to collapse
All you have to do is boot into your bootloader (Power + Volume Up + Volume Down at the same time) and flash the stock recovery.
fastboot flash recovery recovery.img
Chances are you flashed an incorrect version of TWRP meant for another phone hence the boot loop.
asawoszc said:
All you have to do is boot into your bootloader (Power + Volume Up + Volume Down at the same time) and flash the stock recovery.
fastboot flash recovery recovery.img
Chances are you flashed an incorrect version of TWRP meant for another phone hence the boot loop.
Click to expand...
Click to collapse
When i boot into recovery mode the screen is on but it is black.
asawoszc said:
All you have to do is boot into your bootloader (Power + Volume Up + Volume Down at the same time) and flash the stock recovery.
fastboot flash recovery recovery.img
Chances are you flashed an incorrect version of TWRP meant for another phone hence the boot loop.
Click to expand...
Click to collapse
Also yes i do think I flashed the wrong TWRP. how do I flash the correct TWRP when I can't even get back into a tool to flash it?
Judah04 said:
When i boot into recovery mode the screen is on but it is black.
Click to expand...
Click to collapse
You dont need recovery, you need bootloader.
telep said:
You dont need recovery, you need bootloader.
Click to expand...
Click to collapse
Can you please explain to me exactly what to do. thank you. also my bootloader is unlocked. I also can get to fastboot so what is the diffrence between bootloader and fastboot.
Hold down the volume +, volume -, and power button. You'll be taken to a screen with the word START at the top. Now, connect the phone to your Windows computer using the USB cable, open a command prompt and type "fastboot flash recovery nameof twrpfile.img", press the enter key, use the volume button to select recovery, use the power button to enter recovery, press the power button, press volume + button, and you should enter TWRP.
Thank you but I do not own a windows computer
Then look up the respective commands. You flashed twrp over your kernel, you need to flash a proper boot.img (kernel) if you want the phone to boot. Fastboot is ran through bootloader. Flash the proper kernel in bootloader using fastboot.
wangdaning said:
Then look up the respective commands. You flashed twrp over your kernel, you need to flash a proper boot.img (kernel) if you want the phone to boot. Fastboot is ran through bootloader. Flash the proper kernel in bootloader using fastboot.
Click to expand...
Click to collapse
Thank you this sounds like it will work. But can you put it in more simple terms and give me links? plz. thx in advance.
Do you have access to a Windows computer to flash the commands? How did you flash TWRP?
audit13 said:
Do you have a computer?
Click to expand...
Click to collapse
I have a macbok air running mac os x 10.5.8.
audit13 said:
Do you have access to a Windows computer to flash the commands? How did you flash TWRP?
Click to expand...
Click to collapse
I flashed TWRP using the TWRP app it installed TWRP 2.8.7.1 I also unlocked the bootloader with a similar app.
This might help: http://forum.xda-developers.com/goo...olkit-root-twrp-recovery-unroot-11-6-t2515640
audit13 said:
This might help: http://forum.xda-developers.com/goo...olkit-root-twrp-recovery-unroot-11-6-t2515640
Click to expand...
Click to collapse
Just cheked it out I tried it and it didn't work but thx anyway. btw I am running android 6.0.
audit13 said:
This might help: http://forum.xda-developers.com/goo...olkit-root-twrp-recovery-unroot-11-6-t2515640
Click to expand...
Click to collapse
It might not have been working because I did not enable USB Debuging. :crying:
USB debugging is required for adb commands. With fastboot mode, debugging isn't necessary.
audit13 said:
USB debugging is required for adb commands. With fastboot mode, debugging isn't necessary.
Click to expand...
Click to collapse
Can you please walk me through this i am some what of a beginner when it comes to some of these things. I can try the tool kits agin but need help.
Hello, I have an Honor 6x, with unlocked bootloader, and wanted to install TWRP so I booted into bootloader
and flashed twrp.img via fastboot, but now everytime I want to boot TWRP it just shows the message:
Your device has been unlocked and
can't be trusted.
To learn more, visit:
*some link I can't post cause I'm new here*
Your device is booting now...
and then it is stuck in this state...
could I eventually boot into TWRP directly from bootloader via fastboot?
Please help guys, thanks in advance. :fingers-crossed:
What version of EMUI are you on? If you're on the 7.0 beta there isn't a working twrp for it.
jarebear603 said:
What version of EMUI are you on? If you're on the 7.0 beta there isn't a working twrp for it.
Click to expand...
Click to collapse
Indeed, i am on Nougat, is there any way to downgrade?
pt_2001 said:
Indeed, i am on Nougat, is there any way to downgrade?
Click to expand...
Click to collapse
I know for my device BLN-L24 there is instructions on the honor website on how to downgrade.
jarebear603 said:
I know for my device BLN-L24 there is instructions on the honor website on how to downgrade.
Click to expand...
Click to collapse
Hm, can't find it. Where exactly are these instructions?
Hello. Replying here as I don't need a new thread for a very similar issue.
Brand new 6x with EMUI 4. Unlocked bootloader successfully. Using adb/fastboot tool I boot into bootloader, then flash my twrp img. For some reason this goes fine with no errors but takes less than two seconds (cause for concern?).
Now from this point is where I am having trouble. Regardless of what I do, the phone only boots into the EMUI recovery screen. I am aware of holding the volume up key on the first boot after flashing twrp so that it won't be overwritten. I have rebooted the phone manually and also through fastboot while holding the volume up button.
In a new city and only internet I have is thru my phone so this process is really slow due to all the restarts etc. Thanks in advance for the help!
pt_2001 said:
Hello, I have an Honor 6x, with unlocked bootloader, and wanted to install TWRP so I booted into bootloader
and flashed twrp.img via fastboot, but now everytime I want to boot TWRP it just shows the message:
Your device has been unlocked and
can't be trusted.
To learn more, visit:
*some link I can't post cause I'm new here*
Your device is booting now...
and then it is stuck in this state...
could I eventually boot into TWRP directly from bootloader via fastboot?
Please help guys, thanks in advance. :fingers-crossed:
Click to expand...
Click to collapse
i have the same problem with my Honor 6X (BLN-L21) but my phone is stuck at this screen. boot normally, i get that screen. fastboot/rescue mode, i get that screen. recovery, i get that screen. erecovery, i get that screen. aaaand twrp recovery. i get that screen.
also my phone does some weird stuff with the battery level.
Android Nougat and TWRP 3.1.0-2 berlin
MintCrystal556 said:
i have the same problem with my Honor 6X (BLN-L21) but my phone is stuck at this screen. boot normally, i get that screen. fastboot/rescue mode, i get that screen. recovery, i get that screen. erecovery, i get that screen. aaaand twrp recovery. i get that screen.
also my phone does some weird stuff with the battery level.
Click to expand...
Click to collapse
Same problem here. I have a Honor 6x (BLN-L21) with Nougat on it (Build BLN-L21C432B360), unlocked it with the unlock pwd and tried to flash the TWRP (twrp-3.1.0-2-berlin.img) with 'fastboot flash recovery twrp-3.1.0-2-berlin.img'. After that I get always the same message after reboot or if I try to enter the recovery mode.
Any suggestions?
Thank you
Hi there,
I have found it. To get the TWRP Screen I had to press all 3 Buttons (Volume Up, Volume Down and Power) at startup.
Hope this helps.
Sadly this doesn't work here, on a BLN-L21C432B130 with EMUI 4.x and Android 6.x
3 Button start method brings up always the EMUI recovery screen.
Power Button + Volume up Button works fine here with all TWRP versions up to 3.1.0-0, but never on a newer one.
Additional hint: It works only if the USB cable isn't plug into the device and if the phone was powered down before. That must me the reason why I never get that up, if I'm rebootin using the command $ fastboot reboot cause for this the cable connection has to be used
@all who stuck in bootscreen...flash THIS TWRP...
[LG G4 H815] Just need to reboot into recovery directly...
I have kinda the same problem: I flashed TWRP and a friend of mine told me that I need to reboot into recovery directly after flashing TWRP because otherwise the system replaces TWRP again when I type "fastboot reboot". The problem is I cant shutdown the phone and also the key combination of the LG G4 is not rlly working, I tried it dozens of times on my other one... Is there ANY other way of booting to recovery from bootloader / fastboot? Thanks in advance!
P.S.: I read something about "boot twrp.img"... Is that an option or does it just also flash TWRP?
i had the problem, when the cell, automatic restarted and it stuck on this screens, but it never came back, i already tried flashing the cellphone, and i already tried adding a custom bootloader, but no luck, it gave me the information that it mismatch, and attempts to enter the bootloader, without luck, i also already tried to only boot with fastboot, and no luck, it stucks on the twrp or m screen or shows different issues like screen fading or rumbling without reason, attempted to enter the recovery and only got to normal recovery from android, attempted to sideload the zip, and got a verification error, and it fails, again, i cant install a custom recovery, it always fails, and i dont know what to do... i really need help, any suggestion?? i already searched and didnt found any tools, flasher tool v.2 not found, and other tools are not able to help as well, help!!
edit, forgot to add, its an moto g. 2013 , xt1032 ANDROID LOLLIPOP
x-fighter said:
i had the problem, when the cell, automatic restarted and it stuck on this screens, but it never came back, i already tried flashing the cellphone, and i already tried adding a custom bootloader, but no luck, it gave me the information that it mismatch, and attempts to enter the bootloader, without luck, i also already tried to only boot with fastboot, and no luck, it stucks on the twrp or m screen or shows different issues like screen fading or rumbling without reason, attempted to enter the recovery and only got to normal recovery from android, attempted to sideload the zip, and got a verification error, and it fails, again, i cant install a custom recovery, it always fails, and i dont know what to do... i really need help, any suggestion?? i already searched and didnt found any tools, flasher tool v.2 not found, and other tools are not able to help as well, help!!
edit, forgot to add, its an moto g. 2013 , xt1032 ANDROID LOLLIPOP
Click to expand...
Click to collapse
which bootloader?
locked?
which firmware?
flashed how?
Sent from my PH-1 using XDA Labs
sd_shadow said:
which bootloader?
locked?
which firmware?
flashed how?
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
i am unable to use other than the normal bootloader, htt p://cdn.droidviews.com/wp-content/uploads/2014/02/moto-g-bootloader-mode.jpg but mine says unlocked code 3, i used fastboot to attempted to flash the phone, and nothing changed. it has the stock firmware lollipop 5.0.2, codename falcon, i flashed it with fastboot, but no luck, attempted to added by sideload on the android recovery default, and it gives me the errorhttp s://i.imgur.com/nSFMea9.jpg and i am unable to add any file, it doesnt has external sd
x-fighter said:
i am unable to use other than the normal bootloader, htt p://cdn.droidviews.com/wp-content/uploads/2014/02/moto-g-bootloader-mode.jpg but mine says unlocked code 3, i used fastboot to attempted to flash the phone, and nothing changed. it has the stock firmware lollipop 5.0.2, codename falcon, i flashed it with fastboot, but no luck, attempted to added by sideload on the android recovery default, and it gives me the errorhttp s://i.imgur.com/nSFMea9.jpg and i am unable to add any file, it doesnt has external sd
Click to expand...
Click to collapse
https://m.imgur.com/nSFMea9
http://cdn.droidviews.com/wp-content/uploads/2014/02/moto-g-bootloader-mode.jpg
Sent from my PH-1 using XDA Labs
---------- Post added at 01:48 PM ---------- Previous post was at 01:47 PM ----------
neither one of those says what files you are trying to flash
Sent from my PH-1 using XDA Labs
attached
Sent from my PH-1 using XDA Labs
x-fighter said:
i am unable to use other than the normal bootloader, htt p://cdn.droidviews.com/wp-content/uploads/2014/02/moto-g-bootloader-mode.jpg but mine says unlocked code 3, i used fastboot to attempted to flash the phone, and nothing changed. it has the stock firmware lollipop 5.0.2, codename falcon, i flashed it with fastboot, but no luck, attempted to added by sideload on the android recovery default, and it gives me the errorhttp s://i.imgur.com/nSFMea9.jpg and i am unable to add any file, it doesnt has external sd
Click to expand...
Click to collapse
From the picture you uploaded, says that your bootloader is locked, so that is why you can't flash any custom recovery. First you need to unlock your bootloader first but BACKUP FIRST, cause it will erase your internal storage when you unlock your bootloader. After unlocked, then you can flash custom recovery. Hope that helps.
Edit: but if your bootloader is really already unlocked, than try this, flashed twrp, then power down your phone by pressing the power button, then boot to twrp by press power button + volume down buttom. Don't reboot to twrp using the option im bootloader mode or using adb.
tepar said:
From the picture you uploaded, says that your bootloader is locked, so that is why you can't flash any custom recovery. First you need to unlock your bootloader first but BACKUP FIRST, cause it will erase your internal storage when you unlock your bootloader. After unlocked, then you can flash custom recovery. Hope that helps.
Edit: but if your bootloader is really already unlocked, than try this, flashed twrp, then power down your phone by pressing the power button, then boot to twrp by press power button + volume down buttom. Don't reboot to twrp using the option im bootloader mode or using adb.
Click to expand...
Click to collapse
i will upload a more reccent one, where i already unlocked it, but i will try whaat you edited, thank you!! let me try and post results
Hello
I have a Google pixel 128 GB device but recently it got bricked after an ota update. Unfortunately my phone is not rooted or unlocked. So I could not do anything under fastboot, also adb is crashed.
So the phone is bricked. But it can be rectified using QPST is edl mode I suppose. But as of now there is no such development for qpst for Google pixel.
But there are many users they face the same issue recently.
Is there any chance of development for it?
you said bootloader ! you mean the phone can boot into bootloader mode ! after that you said edl mode ? i dont understand. please explain. i may help !
*The Phone Goes into Fastboot with no problems.
*In Fastboot Mode if i try to go to Recovery, The Phone Reboots and does not go to the Recovery But it Keeps on Rebooting.
So the Recovery Partition of the Phone might be Corrupted.
So im looking for ways to Flash the Recovery partition with QPST or any other methods.
Fastboot Doesn't Help Because the Bootloader is locked.
senthil19 said:
*The Phone Goes into Fastboot with no problems.
*In Fastboot Mode if i try to go to Recovery, The Phone Reboots and does not go to the Recovery But it Keeps on Rebooting.
So the Recovery Partition of the Phone might be Corrupted.
So im looking for ways to Flash the Recovery partition with QPST or any other methods.
Fastboot Doesn't Help Because the Bootloader is locked.
Click to expand...
Click to collapse
Download factory image, open up the .sh script as text, copy the fastboot commands about wiping and clearing userdata, cache , etc into a terminal using fastboot
Xdevillived666 said:
Download factory image, open up the .sh script as text, copy the fastboot commands about wiping and clearing userdata, cache , etc into a terminal using fastboot
Click to expand...
Click to collapse
I do believe I've tried this to no avail on a Verizon g-2pw4100-022-b (the "b" probably stands for "brickable").
I'm stuck in the same situation:
Power+vol down - bootloader
Bootloader to recovery - boot loop
Bootloader to barcodes - barcodes show
Edit: power on only leads to constant screen flashing unless you hold volume down for bootloader, at which point you can vol up once and power down.
Can't flash a recovery, can't flash an OTA since that requires adb sideload, which is part of recovery, and can't flash a factory image with the bootloader locked, which is only unlocked under development tools.
One thing to note is that in the bootloader screen, both "b/l" and the one below it (radio?) both say "n/a", which leads me to believe the December update from Verizon could be the cause.
Suggestions as to how to proceed are greatly appreciated.
senthil19 said:
Hello
I have a Google pixel 128 GB device but recently it got bricked after an ota update. Unfortunately my phone is not rooted or unlocked. So I could not do anything under fastboot, also adb is crashed.
So the phone is bricked. But it can be rectified using QPST is edl mode I suppose. But as of now there is no such development for qpst for Google pixel.
But there are many users they face the same issue recently.
Is there any chance of development for it?
Click to expand...
Click to collapse
I have a Reddit thread how to activate qpst .
You can also "adb reboot edl" if your PC can recognize your phone at least.
If not, power button and volume up(or down, I don't remember) for at least forty seconds sometimes brings it up
But then you'd need firmware to flash with qpst and I'm not sure how to go about doing that
---------- Post added at 07:44 AM ---------- Previous post was at 07:42 AM ----------
PoXFreak said:
I do believe I've tried this to no avail on a Verizon g-2pw4100-022-b (the "b" probably stands for "brickable").
I'm stuck in the same situation:
Power+vol down - bootloader
Bootloader to recovery - boot loop
Bootloader to barcodes - barcodes show
Edit: power on only leads to constant screen flashing unless you hold volume down for bootloader, at which point you can vol up once and power down.
Can't flash a recovery, can't flash an OTA since that requires adb sideload, which is part of recovery, and can't flash a factory image with the bootloader locked, which is only unlocked under development tools.
One thing to note is that in the bootloader screen, both "b/l" and the one below it (radio?) both say "n/a", which leads me to believe the December update from Verizon could be the cause.
Suggestions as to how to proceed are greatly appreciated.
Click to expand...
Click to collapse
Can you fastboot boot twrp ?
Are there any solutions to enter EDL Mode in google pixel without adb?