Database Info

[Q] Nexus s stuck on Google Screen

My Nexus s i9020T is stuck on the google screen. I was trying to root it and when it was done my phone rebooted and it got stuck on the google screen. My bootloader is unlocked and i was running on gingerbread 2.3.6 can somebody tell me how to resolve this issue using a mac

How long did you waited? Sometimes that Google logo could tale a long time. Try going through the root process again
Sent from my Nexus S using Tapatalk 2

Same problem
I got the same problem. i can access recovery mode but my phone is not getting detected in PC. just hangs on Google logo (white) :crying:
bootloader os locked also.
My Model is GT-I9020T.
please help.
thanks in advance.

You should try the usb jig sold on ebay for the Nexus S.. It will bring the phone to download mode so you can flash your firmware with odin.. To use odin on your mac you need to have Windows installed with a virtual machine or virtualbox..
---------- Post added at 03:40 AM ---------- Previous post was at 03:35 AM ----------
Kumar Anil said:
I got the same problem. i can access recovery mode but my phone is not getting detected in PC. just hangs on Google logo (white) :crying:
bootloader os locked also.
My Model is GT-I9020T.
please help.
thanks in advance.
Click to expand...
Click to collapse
Bad luck for you.. Since your bootloader is locked and you can't unlock it you can't do anything.. Also you are talking about stock Android recovery right..? No TWRP or CWM..?

same problem
thanks for replying.
actually
I have google nexus GT-I9020t. it hangs on google logo (white). fastboot oem unlock is not working. lock state : locked.
when i go into recovery mode and try to wipe data/factory reset, it says:
e:format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhc1.0/byname/userdata
if i try to flash using fastboot, it says run fastboot oem unlock command.
it is not detecting in odin also. i have installed the drivers though.
else it is going to recovery mode, showing the lock status and i can also go futher in format, data wipe menu.
anything i can purchase will help or not, i dont know.
please help.

Kumar Anil said:
thanks for replying.
actually
I have google nexus GT-I9020t. it hangs on google logo (white). fastboot oem unlock is not working. lock state : locked.
when i go into recovery mode and try to wipe data/factory reset, it says:
e:format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhc1.0/byname/userdata
if i try to flash using fastboot, it says run fastboot oem unlock command.
it is not detecting in odin also. i have installed the drivers though.
else it is going to recovery mode, showing the lock status and i can also go futher in format, data wipe menu.
anything i can purchase will help or not, i dont know.
please help.
Click to expand...
Click to collapse
I made a USB JIG And its showing me some screen. please Check and update.

Kumar Anil said:
I made a USB JIG And its showing me some screen. please Check and update.
Click to expand...
Click to collapse
I remember this screen when I first rooted my Nexus S GTi9023. About the Google logo keep showing, phone probably not finding correct bootloader. I have this issue when I tried jellyBam rom. Fortunalty I had the nandroid back up of other roms that I have tried and I pick up then CM 10.1.2 and choose its backup file for restoring bootloader. Here you me also flash bootloader from PC as well as.

vikaskanani said:
I remember this screen when I first rooted my Nexus S GTi9023. About the Google logo keep showing, phone probably not finding correct bootloader. I have this issue when I tried jellyBam rom. Fortunalty I had the nandroid back up of other roms that I have tried and I pick up then CM 10.1.2 and choose its backup file for restoring bootloader. Here you me also flash bootloader from PC as well as.
Click to expand...
Click to collapse
But how to flash a bootloader? when i try "fastboot oem unlock" it fails. and when it is locked i cant flash a bootloader. any suggestions?

Kumar Anil said:
But how to flash a bootloader? when i try "fastboot oem unlock" it fails. and when it is locked i cant flash a bootloader. any suggestions?
Click to expand...
Click to collapse
You need to accept the warning message, the screen you attached.
Have a look at redmondpie.com/unlock-nexus-s-bootloader-how-to-guide/ (sorry cant post link as i am new user)
As I said, its been a long time, since I rooted, so I guess, you need to use power key or volume key for any action.

fastboot oem unlock not working
vikaskanani said:
You need to accept the warning message, the screen you attached.
Have a look at redmondpie.com/unlock-nexus-s-bootloader-how-to-guide/ (sorry cant post link as i am new user)
As I said, its been a long time, since I rooted, so I guess, you need to use power key or volume key for any action.
Click to expand...
Click to collapse
I guess, USB debugging mode was not checked at the time of the crash. It is detecting in the fastboot devices command but not in ADB devices.
i did everything in the link, you provided me.
and any other way to force partion of somthing. Any Other Option.
FATSBOOT OEM COMMAND:
http://s10.postimg.org/r0rjcrxe1/fastboot_oem_failed.jpg
thanks in advance

Can you boot in jelly bean?? Strange issue!
Sent from my Nexus 7 using xda app-developers app

Can't update my phone.

Hi, I have a Moto G 1st Gen xt1033 Dual Sim. The phone, to my knowledge is completely stock, it is unrooted and I haven't tampered with anything developer-wise. The problem is that I can't seem to update the phone. I get an OTA message telling me the update is ready, I download it, my phone shuts down and then it reboots normally. Not only that, but it also enters a bootloop of about 5 boots. Afterwards, nothing happens, the update is unsuccessful. What also bothers me is that I can't enter recovery. I can select the option from the menu that appears after I press the volume down key+power button, but it just boots normally. Please help, I really want to update my phone and this is getting really annoying.

Sounds like your phone can't update and you cannot manually enter recovery mode.. Did you try re-flashing stock recovery?

I didn't, can you maybe link me to a thread that can help me do that?
Sent from my XT1033 using XDA Free mobile app

Search for your stock ROM here: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1
If you find it, download it, unzip, use fastboot commands to flash the recovery by typing "fastboot flash recovery recovery.img" with the quotes when your phone is in fastboot mode and connected to your PC.

Alright, I'll see what I can do. Does this delete any of my files?
Sent from my XT1033 using XDA Free mobile app

No, it should not wipe your data. Just in case, make sure all of your data file are backed up somewhere else before doing any flashing.
Do you have an unlocked bootloader? I recommend unlocking the bootloader after making your backup. Restoring the phone after a bad flash is always easier with an unlocked bootloader.

Alright, I found my stock firmware, it contains a recovery.img, I set up fastboot, and I'm ready to flash the image. Do I need to uninstall the current recovery or can I just flash over it?

Also, my bootloader is locked, and I would prefer not unlocking it unless it's absolutely necessary.. Do I need to put the recovery.img into a specific folder before entering the fastboot command?

Just put recovery.img in the same folder as your fastboot command.
Just flash over the existing recovery.
If it will not flash, you may have to find a different rom or unlock the bootloader.

I managed to do everything you said. I even unlocked the bootloader and had a bit of a scare cause it got bricked so I had to eventually do a full wipe.. Afterwards I flashed the recovery, installed the 4.4.4 update and got the 5.0 update immediately. Running 5.0 now thanks to you!

[Q] Moto G - TWRP/CWM Do Not Open in Bootmode

I've followed instructions to unlock my bootloader which is done. I'm not sure if - "Device is unlocked. Status Code 3:" is correct or not, but that is what I see.
After unlocking I flashed TWRP 2.6.3.0-xt1032.img and it flashed correctly according to adb (attached). When I reboot the phone into bootloader and select recovery the screen just goes blank. I also tried "recovery-clockwork-touch-6.0.4.7-falcon.img", which seemed to flash OK in adb. The bootloader screen goes blank when I select recovery on the phone for CWM as well.
Both recovery flashes showed a similar result on the phone - this paste is for CWM
In Moto bootmode:
USB Connected
cmd: getvarartition-type:recovery
cmd: getvar:max-download-size
cmd: download:07b2000
cmd: flash:recovery
Mismatched partition zize (recovery)
The phone has stock Android 5.0.2 installed and still works, but I can't get any further than flashing the recovery image in adb. I did flash the logo.bin in adb and it seemed to flash correctly .
I'm running Windows 8.1, USB 3 ports.
Is there something I'm missing, or a different way to do the root? I'm stuck at this point, but luckily can run with the stock ROM for now.
I would appreciate any help I can get, Thanks

both recoveries you have used are seemingly outdated for lollipop bootloader. i would suggest you to try out the newly built TWRP (which is not yet publicly released) cant post URLs here yet but search for '[RECOVERY][falcon]TWRP 2.8.7.0 touch recovery [2015-06-24]' here in XDA
---------- Post added at 11:14 PM ---------- Previous post was at 11:03 PM ----------
here is the URL: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621

koshikas said:
both recoveries you have used are seemingly outdated for lollipop bootloader. i would suggest you to try out the newly built TWRP (which is not yet publicly released) cant post URLs here yet but search for '[RECOVERY][falcon]TWRP 2.8.7.0 touch recovery [2015-06-24]' here in XDA
---------- Post added at 11:14 PM ---------- Previous post was at 11:03 PM ----------
here is the URL: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Click to expand...
Click to collapse
I tried and same result. After flashing with adb - disconnect USB , boot into bootloader, down to recovery, push power button and blank screen. Normal power up does the same thing as does factory. Ad I can confirm the version is 41.18.
Thanks

jjcdennis said:
I tried and same result. After flashing with adb - disconnect USB , boot into bootloader, down to recovery, push power button and blank screen. Normal power up does the same thing as does factory. Ad I can confirm the version is 41.18.
Thanks
Click to expand...
Click to collapse
these blank screens are quiet frustrating, can you get hold of the stock firmware for your model and flash back the stock recovery first and then try again with latest custom recoveries

koshikas said:
these blank screens are quiet frustrating, can you get hold of the stock firmware for your model and flash back the stock recovery first and then try again with latest custom recoveries
Click to expand...
Click to collapse
I had problems last weekend after trying to go to CM12.1 after rooting and ending up in a bootloader loop. I ended up using a KitKat stock rom and mfastboot2 and typed in all of the lines - it worked. The phone then updated to 5.0.2 via auto update.
I don't have that stock from the network update, but found this one - XT1034_Retail_Canada_502_Stock_Untouched which contains 3 files, Meta-inf, system and boot.img. I don't see a recovery in the folder. I'm not really sure what to look for and how to do this.
Thanks

jjcdennis said:
I had problems last weekend after trying to go to CM12.1 after rooting and ending up in a bootloader loop. I ended up using a KitKat stock rom and mfastboot2 and typed in all of the lines - it worked. The phone then updated to 5.0.2 via auto update.
I don't have that stock from the network update, but found this one - XT1034_Retail_Canada_502_Stock_Untouched which contains 3 files, Meta-inf, system and boot.img. I don't see a recovery in the folder. I'm not really sure what to look for and how to do this.
Thanks
Click to expand...
Click to collapse
make sure you get exactly a stock ROM that is made for your model. trying firmware made for other models is surefire way of bricking you phone. usually the stock firmware images ending with '*.xml.zip' do have a 'recovery.img' in them.

koshikas said:
make sure you get exactly a stock ROM that is made for your model. trying firmware made for other models is surefire way of bricking you phone. usually the stock firmware images ending with '*.xml.zip' do have a 'recovery.img' in them.
Click to expand...
Click to collapse
Thanks again.
If I find a correct ROM (I do have a KitKat 4.4.4 version), do I flash back with adb, or with mfastbootv2?
The ROM I showed was from here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
I have also found a firmware link on this thread "http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795" that looks to be in the correct format. There are thorough instructions on how to flash the firmware, but I am not sure if this will fix my issue or not.
Would appreciate any advice on how to proceed.
Thanks

I finally understood your comment "...can you get hold of the stock firmware for your model and flash back the stock recovery first and then try again with latest custom recoveries". I got a copy of the stock firmware, extracted the recovery from it and flashed it via adb to the phone - ok. I then tried to get into phone fastboot recovery, but was faced with the blank screen again. I flashed twrp 2.8.7.0 and the same thing in fastboot recovery - blank screen. I also tried cwm 6.0.5.1 and the same thing, blank screen.
ADB sees the device and accepts the commands, but the Motorola fastboot recovery doesn't open any of the recoveries. Nothing else in the bootloader seems to work ie: Factory - blank screen.
Every one of the recovery files other than the stock recovery shows a pink colored error "Mismatched partition size (recovery).
Anybody have any ideas as to what I can do to get a recovery to work?
Is there a different way to root this phone?

@jjcdennis i think you should post this to one of the active threads, since nobody with experience (this is well beyond mine) has dropped in yet. i would highly recommend; http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621

Moved to http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621

How to Downgrade bootloader 41.1A to 41.18 or 41.19

please..
i have problem with bootloader version 41.1A
i want to Downgrade to version 41.18 or 41.19
anyone know ..??
please share it
thank you

Up
Me too
My bootloader v 41.1A I downgrade 41.18 Help

Why do you need to downgrade? Messing with Bootloaders can destroy your phone.

even i want to downgrade... I cant flash custom recovery on 41.1A

poran123 said:
even i want to downgrade... I cant flash custom recovery on 41.1A
Click to expand...
Click to collapse
Bootloader cannot be downgraded. You're stuck on w/e version you have currently installed.

Okay so I'm stuck on 41.1A and my phone will continue to restart itself and then stuck in bootloop till the battery dies... and then when I connect it to the charger boot's up normally...

@lost101
Can you please let me know how to check bootloader version?
I am using Moto G XT1033 model(Asia).
It was updated to Lollipop 5.0.2 by Motorola Stock Lollipop update.
Later on I had unlocked bootloader and downgraded it to Kitkat 4.4.4 using this thread.
I don't have any clue about current version of bootloader in my Moto G.
I want to try Lollipop 5.1 Optimized stock rom link here, so just wanted to ensure compatibility of bootloader so that my phone works after flashing it.

kalpesh.fulpagare said:
@lost101
Can you please let me know how to check bootloader version?
Click to expand...
Click to collapse
Enter bootloader (hold volume-down while turning it on), read text on screen (second line).

I too want to know if there is a way to downgrade or at least reflash my damaged bootloader which is causing weird behaviour.
Sent from my Nexus 6P using Tapatalk

I have the exact same problem.
Stuck on 41.1A
Was on a slim6 rom before. Tried to return to STOCK_ASIA_RETAIL. All fastboot commands successfully executed but no apparent change. I have the exact same wallpaper, the same layers RRO navbars, everything. I would not need to go to STOCK but since the slim installation is unstable and everything force closes, the phone is unusable.
Additional note: Somehow even TWRP is stuck in the splash screen, so cant flash any other ROM. Even tried to access TWRP using adb, but the TWRP service fails to start.
I fastboot flashed phillz recovery, stock recovery & newer TWRP versions, but nothing happens. Phone still stuck in TWRP screen.
To my surprise I was able to pull my personal files from the internal SD using ADB (which still works btw).
But I'm left with a phone in a zombie unusable condition, it just doesn't react to anything.
Any help from the XDA community would be greatly appreciated. I am still keeping my fingers crossed, so that one day a guide comes up to brick my device (STOCK 5.1 bootloader) and unbrick it using some sort of unbrick tool.

Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too

SLATE21&MOTOG said:
Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too
Click to expand...
Click to collapse
Creating such a zip is possible, but flashing it may either not work or hard brick your phone.

How to install working recovery on 41.1A bootloader
I had the situation on my Moto G XT1039 where I had formatted the partitions on my phone (using my old CWM recovery), then flashed the 41.1A bootloader, but 41.1A would not allow me to flash any recovery.
So I had a working bootloader, but no recovery and no OS. And apparently no way to install a recovery, to install an OS...
I got the phone back like this:
- Flashed 4.4.4 stock manually using the bootloader (if you do this, DO NOT flash the 4.4.4 motoboot.img, according to everything on here that will permanently brick your phone; I am not sure about partition gpt.bin - I flashed this, but I was already on the 4.4.4 partition layout anyway). Do flash boot.img, that is the OS boot.
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
From there I now had the correct recovery in place to flash the 5.1 Optimized distro (which I would definitely recommend - clean, stable, excellent battery life!).
Yay!

Bmju said:
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
Click to expand...
Click to collapse
Why didn't you simply fastboot flash a TWRP image?

_that said:
Why didn't you simply fastboot flash a TWRP image?
Click to expand...
Click to collapse
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.

Bmju said:
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.
Click to expand...
Click to collapse
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.

_that said:
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.
Click to expand...
Click to collapse
Thanks! I definitely tried that first! Maybe this bit I didn't make clear in my post, but actually:
- fastboot boot was only working for me with older recovery ROMS, i.e. the older CWM recovery which I mentioned, which I had lying around from when I first rooted my phone on 4.4.4, and also - not that it's much use - with the recovery in the 4.4.4 image, which just brings up the dead Android logo
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.

Bmju said:
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
Click to expand...
Click to collapse
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Bmju said:
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
Click to expand...
Click to collapse
That doesn't make any sense. Not that I don't believe you, I just can't explain how fastboot could fail writing recovery but succeed in writing a different partition.
Bmju said:
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.
Click to expand...
Click to collapse
Thanks for sharing your experience though, maybe it will help someone who has the same weird issue.

_that said:
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Click to expand...
Click to collapse
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)

Bmju said:
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)
Click to expand...
Click to collapse
Yes, I've got that one too, but my flashed recovery then worked fine. However I upgraded my bootloader by installing the complete 5.1 stock ROM, maybe your bootloader update was somehow incomplete.

No bootloader/fastboot

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...