Bootloop on any custom rom? - Sony Xperia M2

Hello guys!
I have weired problem...
I have bootloop on any custom rom
I tested SlimROM and CM 12.1
Infinite bootanimation
Halp :/

1: Unlock your bootloader, do this http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/ or watch videos It's generally the same method in how to unlock bootloaders and make sure you install your drivers phone drivers and flashmode and fastboot drivers very easy there is a small .exe file in flashtools that you use it has the drivers
Step 2: Do this http://forum.xda-developers.com/xperia-m2/general/unlocked-bl-root-sony-xperia-m2-android-t3214498
Step 3: Download this file from here http://forum.xda-developers.com/xperia-m2/orig-development/rom-cyanogenmod-12-developement-t2971213 and then flash it through Flashtools
Step 4: ???
Step 5: Profit
PM me for any doubt for more clarity

Still doesn't work (bootloop on cm bootanimation)
(Flashtool version 0.9.18.6)
1. I flashed 18.6.A.0.175 CE1 (D2303)
2. I installed Xperia M2 (Open devices) TA update (via emma from sony)
3. I did everything on this thread execept flashing "special ftf" (Upgrade your bootloader via Emma or by flashing this FTF I made)
Code:
http://forum.xda-developers.com/xperia-m2/general/unlocked-bl-root-sony-xperia-m2-android-t3214498
4. I flashed CyanogenMod 12.1 09/11/2015 via recovery (after wipe data & factory reset in cmw)
5. bootloop on cm 12 logo
What's wrong ;--;

Nevvy said:
Still doesn't work (bootloop on cm bootanimation)
(Flashtool version 0.9.18.6)
1. I flashed 18.6.A.0.175 CE1 (D2303)
2. I installed Xperia M2 (Open devices) TA update (via emma from sony)
3. I did everything on this thread execept flashing "special ftf" (Upgrade your bootloader via Emma or by flashing this FTF I made)
Code:
http://forum.xda-developers.com/xperia-m2/general/unlocked-bl-root-sony-xperia-m2-android-t3214498
4. I flashed CyanogenMod 12.1 09/11/2015 via recovery (after wipe data & factory reset in cmw)
5. bootloop on cm 12 logo
What's wrong ;--;
Click to expand...
Click to collapse
Which recovery did you use?

Maybe you have new period device?

Boulton9610 said:
Which recovery did you use?
Click to expand...
Click to collapse
TWRP 2.8.70
@rafix96 what do you mean?
btw my bootloader is unlocked

Did you do the RIC disabled step?
Also flash again and wait it takes upto 20 30 minutes
---------- Post added at 08:42 PM ---------- Previous post was at 08:40 PM ----------
Okay you missed a step when flashing via recovery
Go to wipe area select all boxes and wipe and then install cyanogen - factory reset doesn't wipe os

ARandomIndian said:
Did you do the RIC disabled step?
Also flash again and wait it takes upto 20 30 minutes
---------- Post added at 08:42 PM ---------- Previous post was at 08:40 PM ----------
Okay you missed a step when flashing via recovery
Go to wipe area select all boxes and wipe and then install cyanogen - factory reset doesn't wipe os
Click to expand...
Click to collapse
Yes i disabled RIC
I selected all boxes in wipe area and I installed cyanogen and still bootloop

Nevvy said:
Yes i disabled RIC
I selected all boxes in wipe area and I installed cyanogen and still bootloop
Click to expand...
Click to collapse
Can you reflash the bootloader using Flashtools?
Also repeat all steps carefully
Could you confirm you did everything?

ARandomIndian said:
Can you reflash the bootloader using Flashtools?
Also repeat all steps carefully
Could you confirm you did everything?
Click to expand...
Click to collapse
Same effect still bootloop

Nevvy said:
Same effect still bootloop
Click to expand...
Click to collapse
Okay do this, first redownload recovery and cyanogenmod again
Flash the newly downloaded TWRP again and then go to factory defaults do that and then go to "Wipe" and select everything and then wipe
Now switch off wait 1 minute and then reboot into recovery mode and flash the newly downloaded Cyanogenmod again
If it still doesn't work best option will be to flash the official 5.1.1 firmware and repeat; but i suggest trying to find a compatible CWM recovery and try with that

ARandomIndian said:
Okay do this, first redownload recovery and cyanogenmod again
Flash the newly downloaded TWRP again and then go to factory defaults do that and then go to "Wipe" and select everything and then wipe
Now switch off wait 1 minute and then reboot into recovery mode and flash the newly downloaded Cyanogenmod again
If it still doesn't work best option will be to flash the official 5.1.1 firmware and repeat; but i suggest trying to find a compatible CWM recovery and try with that
Click to expand...
Click to collapse
Still f*cking bootloop m8 :/

May be you have m2 model rev5 as there seems to be a problem with this specific model see cm thread on here
D2303 5.1 customised NCB LB rooted Nuts t2u dual recovery bravia engine+x-reality debloated

Alright cm topic says it supports all devices but I've never heard of rev5 or something maybe you can ask them to add support?
Okay hold on do you mean d2305 is revision 5? If so it works fine mine is that and I installed cyanogenmod just fine

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I guess it's not rev5

Huh i tried install SlimROM
http://forum.xda-developers.com/xperia-m2/orig-development/5-1-1-slimrom-xperia-m2-lte-t3244761
Click to expand...
Click to collapse
Bootloop too :/

You have updated your bootloader via Emma?
D2303 5.1 customised NCB LB rooted Nuts t2u dual recovery bravia engine+x-reality debloated

Nevvy said:
Huh i tried install SlimROM
Bootloop too :/
Click to expand...
Click to collapse
Hi
When you install SlimROM try make this: after success flashig rom in twrp goto Mount > and "tick" /system now back and goto Advanced > File Manager > system > vendor > lib > hw and delete file named "sensor.msm8226.so" and after that try to reboot yours phone
And let me know if it will help you. Because if it will work i make special build of SlimROM for people with that problem

[email protected] said:
You have updated your bootloader via Emma?
D2303 5.1 customised NCB LB rooted Nuts t2u dual recovery bravia engine+x-reality debloated
Click to expand...
Click to collapse
I tested both
Via Emma and via special ftf flashtool

pawcioo132 said:
Hi
When you install SlimROM try make this: after success flashig rom in twrp goto Mount > and "tick" /system now back and goto Advanced > File Manager > system > vendor > lib > hw and delete file named "sensor.msm8226.so" and after that try to reboot yours phone
And let me know if it will help you. Because if it will work i make special build of SlimROM for people with that problem
Click to expand...
Click to collapse
Ill try it tomorrow

Related

[HELP] HONOR 6 - Bricked - B805

I have update my H60-L04 (asia) to emui4.0 but bricked... i need the full rom of H60-L04C470B805 to unbrick it.. i have try the india version,B803, but it wont work... any idea for this? Thanks
roythen said:
I have update my H60-L04 (asia) to emui4.0 but bricked... i need the full rom of H60-L04C470B805 to unbrick it.. i have try the india version,B803, but it wont work... any idea for this? Thanks
Click to expand...
Click to collapse
Put the phone in fastboot mode, install CWM or TWRP, copy the backup to SD/clockworkmod/backup or SD/TWRP/backup and restore it
Choose a backup
Backup B803
https://mega.nz/#!adYwhRKI!2cSUEQYOJu_BVIFwKpA30TV3ptfsDEyx6iARlfzLhZg
Backup B805
https://yadi.sk/d/aQ2ess6WnUW3C
Backup B807
https://mega.nz/#!6dIzhTza!Zz9nPJpCZwSJ9yiLTsuI3x1tu0K6BE2HNYjX5gCxXiI
Backup B810
https://mega.nz/#!PEpQgaQZ!472a_bzdP4pACHvk77wsuDw53KmViDGWVhw-PRiZD_Q
Junior Member
12 posts
Thanks: 3
i just Downgraded from B810 to B550
1- We need to use a clean B810 (or i think any of this H60-L04C675B8007
H60-L04C675B8006
H60-L04C675B8010
H60-L04C675B8004
H60-L04C675B8003
H60-L04C151B8002
H60-L04C151B8001) it is in VERLIST.img inside UPDATE.APP
2- We need to use boot.IMG B803 - Recovery.IMG B803
3- Use the downgraded package https://drive.google.com/file/d/0ByJ...w?pref=2&pli=1
4- Use full room B550
(and may be this done because i Change location to (hw/normal) first) this link https://www.youtube.com/watch?v=36L-...ature=youtu.be
adhamamar said:
Junior Member
12 posts
Thanks: 3
i just Downgraded from B810 to B550
1- We need to use a clean B810 (or i think any of this H60-L04C675B8007
H60-L04C675B8006
H60-L04C675B8010
H60-L04C675B8004
H60-L04C675B8003
H60-L04C151B8002
H60-L04C151B8001) it is in VERLIST.img inside UPDATE.APP
2- We need to use boot.IMG B803 - Recovery.IMG B803
3- Use the downgraded package https://drive.google.com/file/d/0ByJ...w?pref=2&pli=1
4- Use full room B550
(and may be this done because i Change location to (hw/normal) first) this link https://www.youtube.com/watch?v=36L-...ature=youtu.be
Click to expand...
Click to collapse
link downgrade package not work
Steve Giordano
which build num you use?is the rom is clean?what is your location?
Billion Thanks to you guys.. my phone works again.... but dunno how to root it.... any idea.... i already a week finding solution.. and i almost plan to buy a new phone....
adhamamar said:
Steve Giordano
which build num you use?is the rom is clean?what is your location?
Click to expand...
Click to collapse
My location is Italy, My last rom is L04-C432B805 .
the rom isn't clean..
Please help! :crying:
@Steve Giordano, i try that already. and my phone got back to kitkat... you better flash to twrp recovery then flash twrp back up 803 full stock. in that senario i do wipe cache and factory reset before proceed to rollback. it really work. just make more perservance
Jessie17 said:
@Steve Giordano, i try that already. and my phone got back to kitkat... you better flash to twrp recovery then flash twrp back up 803 full stock. in that senario i do wipe cache and factory reset before proceed to rollback. it really work. just make more perservance
Click to expand...
Click to collapse
After flash twrp recovery with fastboot i can't acces on it... (button vol + and poweroff) :crying:
sorry for my bad english!
Steve Giordano said:
After flash twrp recovery with fastboot i can't acces on it... (button vol + and poweroff) :crying:
sorry for my bad english!
Click to expand...
Click to collapse
You can help users if they give the correct information!
You have unlocked the bootloader? If you have unlocked the bootloader when you put the devices into fastboot mode you get a message in red phone unlocked
If the phone not unlocked it is useless to flash the recovery or twrp
If the phone is unlocked cwm and twrp work to 100%
panamera2011 said:
You can help users if they give the correct information!
You have unlocked the bootloader? If you have unlocked the bootloader when you put the devices into fastboot mode you get a message in red phone unlocked
If the phone not unlocked it is useless to flash the recovery or twrp
If the phone is unlocked cwm and twrp work to 100%
Click to expand...
Click to collapse
My phone have Unlocked bootloader.
this is when flash TWRP recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Steve Giordano said:
link downgrade package not work
Click to expand...
Click to collapse
https://drive.google.com/file/d/0ByJkSOohdNz_NWtGclJmVTYtZUk/view?pref=2&pli=1
Steve Giordano said:
My phone have Unlocked bootloader.
this is when flash TWRP recovery.
Click to expand...
Click to collapse
Try the latest version of TWRP v4
TWRP_2.8.7.0_EN_EMUI_4.0_v4.img
https://drive.google.com/folderview...sharing&tid=0By4NGNfKPDLBQTZ2S0licGhjNmc#list
Download adb here
http://www.mediafire.com/download/o5ruw752ked884u/adb+H60.zip
Copy TWRP_2.8.7.0_EN_EMUI_4.0_v4.img in the adb folder
turn off the device and boot into fastboot mode
in adb folder run cmd.exe as administrator and type these commands:
fastboot devices
If the device is recognized correctly displaying a series of numbers
Then type
fastboot flash recovery TWRP_2.8.7.0_EN_EMUI_4.0_v4.img
fastboot reboot
Disconnect the USB cable and press volume up + power (press 8 - 10 seconds) to enter into recovery
If it works to restore a backup
panamera2011 said:
Try the latest version of TWRP v4
TWRP_2.8.7.0_EN_EMUI_4.0_v4.img
https://drive.google.com/folderview...sharing&tid=0By4NGNfKPDLBQTZ2S0licGhjNmc#list
Download adb here
http://www.mediafire.com/download/o5ruw752ked884u/adb+H60.zip
Copy TWRP_2.8.7.0_EN_EMUI_4.0_v4.img in the adb folder
turn off the device and boot into fastboot mode
in adb folder run cmd.exe as administrator and type these commands:
fastboot devices
If the device is recognized correctly displaying a series of numbers
Then type
fastboot flash recovery TWRP_2.8.7.0_EN_EMUI_4.0_v4.img
fastboot reboot
Disconnect the USB cable and press volume up + power (press 8 - 10 seconds) to enter into recovery
If it works to restore a backup
Click to expand...
Click to collapse
Ora funzionaaa va in recovery!!!!
Now work! go in recovery!
Very Thanks @panamera2011
panamera2011 said:
Put the phone in fastboot mode, install CWM or TWRP, copy the backup to SD/clockworkmod/backup or SD/TWRP/backup and restore it
Choose a backup
Backup B803
https://mega.nz/#!adYwhRKI!2cSUEQYOJu_BVIFwKpA30TV3ptfsDEyx6iARlfzLhZg
Backup B805
https://yadi.sk/d/aQ2ess6WnUW3C
Backup B807
https://mega.nz/#!6dIzhTza!Zz9nPJpCZwSJ9yiLTsuI3x1tu0K6BE2HNYjX5gCxXiI
Backup B810
https://mega.nz/#!PEpQgaQZ!472a_bzdP4pACHvk77wsuDw53KmViDGWVhw-PRiZD_Q
Click to expand...
Click to collapse
can i use any of these backups to downgrade from B805 or i have to use the b805 backup?? plz note that my phone isn't bricked, i just want to downgrade from b805 eu version and all downgrade packages are indian..
will this work??
monmon20077 said:
can i use any of these backups to downgrade from B805 or i have to use the b805 backup?? plz note that my phone isn't bricked, i just want to downgrade from b805 eu version and all downgrade packages are indian..
will this work??
Click to expand...
Click to collapse
I do not know, these backups found them on Honor 6 4pda
With google, search Honor 6 4pda, use the translator, and look if are suitable for you.
I'm sorry, but my phone is L02
monmon20077 said:
can i use any of these backups to downgrade from B805 or i have to use the b805 backup?? plz note that my phone isn't bricked, i just want to downgrade from b805 eu version and all downgrade packages are indian..
will this work??
Click to expand...
Click to collapse
it's not possible.... I'm in your situation
luis_20_p7 said:
it's not possible.... I'm in your situation
Click to expand...
Click to collapse
is there any solution for us.. when i try to upgrade to any version b806 or above it fails at 5% and when i try to downgrade using any downgrade package it fails at 36% coz all downgrade packages are indian version and my b805 is eu... i'm afraid i won't be able to upgrade my phone to the stable version of android M.. and the battery draining in b805 is very annoying... what can we do??
Hi guys, you have look here?
http://pantomath.xyz/how-to-unbrick-honor-6-from-android-m/
Sent from my H60-L02 using Tapatalk
panamera2011 said:
Hi guys, you have look here?
http://pantomath.xyz/how-to-unbrick-honor-6-from-android-m/
Sent from my H60-L02 using Tapatalk
Click to expand...
Click to collapse
i tried this methode many times.. never worked for me coz all downgrade packs in that thread are indian and my b805 version is eu... is there any other source for downgrade packs other than this site??

XT1575 February 2016 Security Update OTA (24.201.3.en.US) + Updated Stock ROM

Pulled from my US X Pure Edition.
Place in Internal Storage and flash in recovery.
Untested with flashing via TWRP as I've waited all day on complete stock ROM to capture and pull this zip.
MUST BE ON STOCK RECOVERY TO FLASH IT. If you flash it in TWRP and boot loop, without making a backup beforehand, you're on your own. You should've made a backup AS ALWAYS.
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
February 2016 Security Update OTA
Google Drive: blur_version.24.11.18.clark_retus.retus.en.us (flash in stock recovery ONLY)
MD5: e08d5e837d59d9b4ecd88f15ba2906f7
Stock odexed ROM with the February 2016 Security Update applied. No root. Flash in TWRP.
Google Drive: stock_marshmallow_for_moto_x_pure_edition-mphs24.49-18-3 (flash in TWRP)
MD5: 2a1505d2626aa1ef1d18da904a3d5093
Modified boot.img post for use with traditional SuperSU root by DaMadOne here:
http://forum.xda-developers.com/showpost.php?p=65541582&postcount=61
Stock 6.0 Marshmallow Recovery:
IMG version
Google Drive: stock-6.0-mph24.49-18-recovery.img (flash in fastboot or TWRP)
MD5: 2ac9b589a3dc14d4000cbbe082b36ba9
ZIP version
Google Drive: stock-6.0-mph24.49-18-recovery.zip (flash in TWRP)
MD5: a59bb1d9eca25608658cd67f7b4707c2
NOTE: If you get "No command" while booting into stock recovery, hold the power button and press up on the volume key. Options should now be available. I'm not sure why it does that but it used to do it on Nexus devices (and probably still does.)
Spasticdroid said:
Pulled from my US X Pure Edition.
Place in Internal Storage and flash in recovery.
Untested with flashing via TWRP as I've waited all day on complete stock ROM to capture and pull this zip.
Screenshots:
Google Drive: blur_version.24.11.18.clark_retus.retus.en.us
Click to expand...
Click to collapse
So is this captured ota or a stock twrp backup
Google~Android said:
So is this captured ota or a stock twrp backup
Click to expand...
Click to collapse
Spasticdroid said:
capture and pull this zip.
Click to expand...
Click to collapse
It's the OTA.
Hi do you know how to flash this using twrp? I tried and it failed. Thank you in advance.
Hey dude, I just got the notification. I'm using the stock ROM, rooted and obviously bootloader unlocked, also using xposed, do you know if it's safe for me to install the update from the notification? I just don't want to screw it and start from scratch.
I flashed supersu 2.66 as I had done previous but wouldn't boot past the logo. Anyone gotten this rooted?
Nexus 10
Vinrock2244 said:
Hi do you know how to flash this using twrp? I tried and it failed. Thank you in advance.
Click to expand...
Click to collapse
What error? Where's your recovery log?
Doesn't work with TWRP 3.x? Use an older version.
Doesn't work with the older TWRP 2.x? Use TWRP 3.x.
Not working with TWRP period? Flash stock recovery, flash the OTA, put TWRP back.
blkcr said:
Hey dude, I just got the notification. I'm using the stock ROM, rooted and obviously bootloader unlocked, also using xposed, do you know if it's safe for me to install the update from the notification? I just don't want to screw it and start from scratch.
Click to expand...
Click to collapse
I don't use Xposed so I wouldn't know if the OTA will work even after uninstalling it. Also, if you're not using systemless root, you'll have to wipe clean. Back up data apps using Titanium or similar. Systemless root however restores original kernel and files.
rocketsaucev2 said:
I flashed supersu 2.66 as I had done previous but wouldn't boot past the logo. Anyone gotten this rooted?
Nexus 10
Click to expand...
Click to collapse
2.67 systemless works fine.
Spasticdroid said:
2.67 systemless works fine.
Click to expand...
Click to collapse
Do you have a link handy? Is it just twrp flashable?
Nexus 10
Also in for a twrp flashable version
rocketsaucev2 said:
Do you have a link handy? Is it just twrp flashable?
Nexus 10
Click to expand...
Click to collapse
Google SuperSU Beta. Should be the first link to Chainfire's thread.
Run this in a Terminal app (with su) or TWRP's Terminal
Code:
echo "SYSTEMLESS=true" >> /data/.supersu
Then flash SuperSU 2.67.
Spasticdroid said:
Google SuperSU Beta. Should be the first link to Chainfire's thread.
Run this in a Terminal app (with su) or TWRP's Terminal
Code:
echo "SYSTEMLESS=true" >> /data/.supersu
Then flash SuperSU 2.67.
Click to expand...
Click to collapse
Got it. Thanks
Nexus 10
Just popped up on mine as well. Small.
Interesting, the zip contains baseband patches but the version in the OP remained the same. Anyone notice any differences in reception?
Decided to give this a go... Have combined storage and was on a custom stock rom with xposed and viper.
Flashed stock system and recovery, did not wipe data.
Reboot system, let everything update, verify combined storage untouched.
Stock recovery could not find the update since I have combined storage.
Tried TWRP with no success
Flashed stock recovery and sideloaded the update
Update flashed succesfully
Reboot to bootloader and flash TWRP and kernel of choice.
Reboot system
Reboot to bootloader and flash super su, xposed etc.
2.67 non systemless did not work for me. 2.64 worked fine as usual. Well maybe not, getting a lot of system fc's. Will update once I have it worked out.
So flashing 2.62-3, then flashing 2.64 got me out of bootloops and system fc's. Seems to be good to go now.
I am very interested in systemless root specifically for the security updates and benefits of root.
Using this guide
http://forum.xda-developers.com/showpost.php?p=64624664&postcount=454
and SuperSU beta should all be ok?
I am ATM on trupurexmm 2.6.2, frankenclark v0.7, xt1575 and twrp 3.0.0-1.
Can someone on an untouched stock system pull /system after the update and upload it for me? I would like to create a flashable zip so we don't have to go through all this nonsense to update.
Is there any detailed guide on how to make this OTA update work on a machine with root + twrp?
blkcr said:
Hey dude, I just got the notification. I'm using the stock ROM, rooted and obviously bootloader unlocked, also using xposed, do you know if it's safe for me to install the update from the notification? I just don't want to screw it and start from scratch.
Click to expand...
Click to collapse
Same boat here. Stock rooted with Xposed. Rooted with 2.62.
---------- Post added at 09:02 AM ---------- Previous post was at 08:54 AM ----------
There is a stock 6.0 twrp backup file available. Perhaps you could restore that, take the OTA, then root again?
bostonirishguy13 said:
Same boat here. Stock rooted with Xposed. Rooted with 2.62.
---------- Post added at 09:02 AM ---------- Previous post was at 08:54 AM ----------
There is a stock 6.0 twrp backup file available. Perhaps you could restore that, take the OTA, then root again?
Click to expand...
Click to collapse
I was thinking of this same thing.
For I, I have a stock non root twrp backup. Was thinking of flashing the stock ota mm that I have then flashing the recovery to stock then take the ota. Install twrp, then root.
Sent from XT1575,TPXMM 2.6.2,Frankenclark v0.7
shoman94 said:
Can someone on an untouched stock system pull /system after the update and upload it for me? I would like to create a flashable zip so we don't have to go through all this nonsense to update.
Click to expand...
Click to collapse
I was going to keep this to myself and one other person on here. It's unmodified, meaning no root, and odexed. Only converted to be flashable.
Also note that I have included other items in the ROM including radios/modem and an unmodified logo.bin, meaning you will get the "bootloader unlocked" splash.
Too lazy to make a thread for it. Any one wants to? Have at it.
https://drive.google.com/file/d/0B5AiGacWcBRzMTBlWmppOC1DS3c/view?usp=docslist_api
Sent from my XT1575 using Tapatalk

OTA update for F1f

A new official ColorOS udpate from OPPO is available in my region and at least all Europe I guess.
This is version F1fEX_11_170327. A copy of the OTA update package is here if anyone needs it: F1EX_11_OTA_896-897_patch_201703271119_3cf702307f.zip on MEGA (56.0 MB).
A few screenshots if you want to see the changelog: http://imgur.com/a/5UiiQ
Before:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After, full about phone capture: http://imgur.com/CIbWrWX
This is still Android 5.1.1 with a 3.10.28 kernel. No Marshmallow
I'm a bit amazed by the continuous support from OPPO, and especially the security patches integrated in those updates. I was not expecting this from this brand. This is part of what's preventing me from completely switching to LineageOS. This is my only smartphone and I need it to just work.
Now I wish I can unroot my phone, lol
You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.
kdd998 said:
You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.
Click to expand...
Click to collapse
Thank you!
But where can I get stock recovery?
You can extract recovery.img from the ColorOS zip.
If someone were to flash this via twrp. When they have followed this thread
https://forum.xda-developers.com/op...pdates-rooted-unlocked-devices-t3395034/page8
They would loose twrp and lose he unlocked bootloader correct?
This zip is only for OPPO*recovery, not for TWRP. It needs to be modified. If modified, I don't think recovery or unlocked state would change as recovery is not included in the original zip.
kdd998 said:
This zip is only for OPPO*recovery, not for TWRP. It needs to be modified. If modified, I don't think recovery or unlocked state would change as recovery is not included in the original zip.
Click to expand...
Click to collapse
The update zip does contain and flash the locked bootloader(emmc_appsboot.mbn) and also the update zips never contain a recovery.img but do have a script(install_recovery.sh) and patches that patch the latest recovery onto latest boot.img and flash it to recovery. So, yes, flashing it will lock everything down. Modifying it to remove bootloader and recovery is easy enough( I'm happy to do it) but it will also check the current build version on the phone before flashing and refuse to flash unless the rom has been updated to the "896" level, which I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now). There is a new download of full rom available for the 896 version which could also be modified to install from twrp without bootloader and recovery but it does require a full wipe. If enough people want it, I guess it would be good to have a more up to date full clean install of colouros.
Do you think it's worth the effort?
MiniBlu said:
The update zip does contain and flash the locked bootloader(emmc_appsboot.mbn) and also the update zips never contain a recovery.img but do have a script(install_recovery.sh) and patches that patch the latest recovery onto latest boot.img and flash it to recovery. So, yes, flashing it will lock everything down. Modifying it to remove bootloader and recovery is easy enough( I'm happy to do it) but it will also check the current build version on the phone before flashing and refuse to flash unless the rom has been updated to the "896" level, which I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now). There is a new download of full rom available for the 896 version which could also be modified to install from twrp without bootloader and recovery but it does require a full wipe. If enough people want it, I guess it would be good to have a more up to date full clean install of colouros.
Do you think it's worth the effort?
Click to expand...
Click to collapse
It would be nice if we ever go back to color os. But don't rush it. Take your time. Its not a big rush. But I would rather the time be spent in lineage first. Up to you
MiniBlu said:
I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now).
Click to expand...
Click to collapse
I have a 010 to 896 patch here if needed: https://mega.nz/#!hxxDxAwb!nLa3aDvz3GubMcTaxqaLowRujDt6UKcn0DohuhkclXY
Thanks for all the info. From my point of view, I don't think it's worth the effort. I'd rather work on LineageOS (maybe I'll have time on monday to try new things)
Deleted
kdd998 said:
You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.
Click to expand...
Click to collapse
what if i still have my stock recovery? can i just flash spectrum os then flash color os to unroot my device? coz i rooted my device also using kingroot. i cant update ota.
wakaranay said:
what if i still have my stock recovery? can i just flash spectrum os then flash color os to unroot my device? coz i rooted my device also using kingroot. i cant update ota.
Click to expand...
Click to collapse
https://www.google.com.au/amp/m.wikihow.com/Unroot-Android?amp=1
That would be the hardest way in my opinion. Try these first.
I would use the supersu app first and if that doesn't work then use the manual delete
Jamie_oppo said:
https://www.google.com.au/amp/m.wikihow.com/Unroot-Android?amp=1
That would be the hardest way in my opinion. Try these first.
I would use the supersu app first and if that doesn't work then use the manual delete
Click to expand...
Click to collapse
both not working. i cant still update tru ota
wakaranay said:
both not working. i cant still update tru ota
Click to expand...
Click to collapse
Have you unlocked your bootloader?
Jamie_oppo said:
Have you unlocked your bootloader?
Click to expand...
Click to collapse
locked bootloader
wakaranay said:
locked bootloader
Click to expand...
Click to collapse
I guess flashing spectrum then color os should work. Not 100% but if you get to spectrum then it will work
Jamie_oppo said:
I guess flashing spectrum then color os should work. Not 100% but if you get to spectrum then it will work
Click to expand...
Click to collapse
thanks. i guess firmware flashing will also work. but i dont know what firmware or when i can get that firmware
wakaranay said:
thanks. i guess firmware flashing will also work. but i dont know what firmware or when i can get that firmware
Click to expand...
Click to collapse
Read post 3 of this thread. Miniblu made a firemware zip. Oops sorry didn't include a link
https://forum.xda-developers.com/oppo-f1/development/rom-unofficial-cyanogenmod-13-t3542718/page23
How to re install the original recovery :crying:

(Guide) Relock Bootloader/Back To Stock.

This guide is for those who are on unlocked bootloader/custom roms and want to go back to realme UI 1.0 and relock
Needless to say, me, and the makers of realme flash-tool and TWRP/other recoveries wouldn't be responsible for any damage caused to your device. Having said that, this method has been tested and should be fine for realme UI 1.0.
First things first, if you are on custom rom or on rooted stock rom you need to revert to unmodified stock rom.
*Warning :-Make absolutely sure that you are not relocking by flashing an older version, always flash the current or newer i:e If you unlocked while being on version A.19 make sure to flash A.19 and/or newer versions and not A.17. While I'm not sure if this will result in a brick or not and have no intentions of trying, this may result in a hardbrick.*
Links to firmware (RMX2061/EUxxxxxxx.ozip). Search for realme 6pro from the list.
IN.- https://www.realme.com/in/support/software-update
EU.- https://www.realme.com/eu/support/software-update
*Do not lock bootloader while on custom rom.*
*Do not lock bootloader if you're rooted.*
*Do not lock bootloader with any custom partitions even vbmeta with disabled verity and verification.*
IF YOU DO SO YOU'LL END UP WITH A BRICK WHICH CAN ONLY BE FIXED AT A SERVICE CENTER. YOUR PHONE WILL DISPLAY AN ERROR MESSAGE SAYING PARTITONS ARE CORRUPT/DAMAGED.
Backup your stuff before proceeding.
There are three ways to revert to stock:
1. Using RFT (Realme Flashtool) by @sayaoks :-
Instructions provided on the thread.
https://forum.xda-developers.com/re.../tool-rtf-realme-flash-tool-to-flash-t4144969
2. Using TWRP (use the latest from the recovery section).
*Wipe>Format Data> type yes> format
*Reboot>reboot to recovery
*Install > Select .ozip> Swipe to flash
*Reboot
Do not select disable-vbmeta or avb_patcher or anything of that sort.
Recommended-
https://forum.xda-developers.com/realme-6-pro/development/recovery-twrp-recovery-t4171759
3. Using stock recovery.
From system:- To flash using stock recovery, download and put the .ozip in the root of storage and from realme file manager tap on it. It will start Flashing in the stock recovery.
From recovery:- Download and put the .ozip in the root of storage, then reboot to recovery.
Your Language> Install from storage> enter password(only if you have one)> Phone/SDcard and then select the .ozip.
Any custom recovery.img/boot.img should now be replaced with stock.
After flashing is successful and the device has booted to stock rom reboot to the bootloader.
If you want to be extra careful, and used RFT or TWRP/Custom Recovery to flash stock rom, you can flash the fw again using stock recovery after the phone has booted up(steps mentioned above).
Connect the phone to PC and enter command
Code:
fastboot flashing lock
Now on the phone select lock bootloader with the help of volume up and power buttons.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wait for it to complete... and you will boot into the OS with a locked bootloader.
Thanks to @Satham spot & @sayaoks
I'm on RMX2063_11_A35 I can't find an update more recent than RMX2061EU_11.A.26 Can I use this method and update via OTA and then lock the bootloader?
Andres88z said:
I'm on RMX2063_11_A35 I can't find an update more recent than RMX2061EU_11.A.26 Can I use this method and update via OTA and then lock the bootloader?
Click to expand...
Click to collapse
A35 is the latest version for IN firmware. Latest for EU is A28, which is up on realme EU website.
If you want A35 firmware just visit the Indian downloads page.
And yes you can update to a newer version than whatever you unlocked on and then lock on the newer version. Make sure everything is just stock meaning no twrp,patched boot and/or custom recovery.
Don't have a brick to use the rmx2061 model? instead of device 2063, what method do you recommend.
Andres88z said:
Don't have a brick to use the rmx2061 model? instead of device 2063, what method do you recommend.
Click to expand...
Click to collapse
Well I know someone having Indonesian/Indian model and locking on the EU firmware. It didn't brick but not sure what will happen in the future when an OTA drops.
Lock on the same firmware as the device, like eu device with eu fw and so on (just to be safe).
You can use any methods to get to stock, just to be extra sure, when the phone boots up after flashing stock and before locking, put the fw in the root storage of the phone and re-flash again with the stock recovery. And then proceed to lock.
thanks to carry out the process and start correctly, I got an update of only 300 mb ls which gave me an error, but soon the same RMX2063a1135 came out but 3.5 gb which if it was installed and now I am as I started, without root or magisk, The question is, since the most recent was installed via ota, can I close the bootloader?
Andres88z said:
thanks to carry out the process and start correctly, I got an update of only 300 mb ls which gave me an error, but soon the same RMX2063a1135 came out but 3.5 gb which if it was installed and now I am as I started, without root or magisk, The question is, since the most recent was installed via ota, can I close the bootloader?
Click to expand...
Click to collapse
Yes
can i use orange fox recovery ? which one should i wipe if i use orange fox recovery?
Can this guide help me rollback my realme 6 pro from android 11 beta to android 10? If it does, which steps do I need to add or change. Thanks
noside_143 said:
Can this guide help me rollback my realme 6 pro from android 11 beta to android 10? If it does, which steps do I need to add or change. Thanks
Click to expand...
Click to collapse
Yes but you must use the latest Android 10 image, seem realme blocks to downgrade to older version than this
I have installed custom rom and I need to return to stock rom
all stock versions I found are ui 1.0 only
I unlocked the bootloader while using latest ui 2.0
what should I do to return to stock rom please ?
kiro_koko said:
I have installed custom rom and I need to return to stock rom
all stock versions I found are ui 1.0 only
I unlocked the bootloader while using latest ui 2.0
what should I do to return to stock rom please ?
Click to expand...
Click to collapse
You can use RUI 2.0 to lock. Just be sure that all partitions are stock. Use the .ozips made by @ctapchuk

How To Guide RUI 3.0 Easy Rooting Guide - On GT NEO 2

This thread going to guide you on how you can root Realme GT NEO 2 Device with RUI 3.0 installed.
This boot image is fresh, and it's patched for root access.
Caution: Before flashing, you need to have your bootloader unlocked, for bootloader unlocking, go to this link and follow the procedure to get approval and unlock your device bootloader.
Link: https://forum.xda-developers.com/t/bootloader-unlock-realme-gt-neo-2-rmx3370-all-variants.4391679/
After you get approval, you are ready to root your device!
For this tutorial, I gonna use a windows device.
​WARNING!​
I am not responsible for anything. proceed at your own risk. Rooting or Unlocking the Bootloader voids the device warranty, keep it in your mind.
STEP - ONE​
Only follow this step, if you get approval for the bootloader, and you didn't unlock this device or your flashing environment needs to be configured. You need to visit the following link to set up your environment for flashing a custom boot image.
Link: https://njpsmultimedia.blogspot.com/2022/04/realme-gt-neo-2-bootloader-unlock.html you just need to follow the video tutorial on this website.
STEP - TWO​​It's assumed that your environment is properly configured. Let's flash this boot image to root your device.
Download this zip file from here https://drive.google.com/file/d/1Xk1yBp5EDCZbl3i3jMtOhjfaVtTCQqYB/view?usp=sharing and copy the boot.img file to platform-tools folder.
Then open the terminal and cd to the platform-tools folder.
Then, shut down your device and hold the vol up + vol down + power button together to boot this device into fastboot mode.
First, you need to run
Code:
fastboot devices
to check if your device is properly connected to the bootloader interface. If it shows something then your device is properly connected, If not, try to install the device driver, change the cable, or boot into the bootloader mode again.
If your device is connected properly, then you will see a screen like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And then run this command:
Code:
fastboot flash boot boot.img
Then,
Code:
fastboot reboot
You are done! Congratulation.
Note: This method was tested with Realme UI 3.0 android 12 on GT NEO 2. Do not try this method on RUI 2.0 or on other devices.
SCREENSHOTS​
Note ​
If you face NO WIFI, Sound issue on the C04 version, you are advised to flash this alternate version from here: https://forum.xda-developers.com/t/...uide-on-gt-neo-2.4435919/page-2#post-86985433
Do you lose all data ? On the root part the bootloader is already unlocked
theogr91 said:
Do you lose all data ? On the root part the bootlocker is already unlocked
Click to expand...
Click to collapse
- it is necessary to have the bootloader unlocked before flash (instructions on how to unlock the bootloader can be found in the video in the post above or here on the forum)
- after flash just install Magisk manager
no data loss, tested and functional
theogr91 said:
Do you lose all data ? On the root part the bootlocker is already unlocked
Click to expand...
Click to collapse
If your bootloader is already unlocked, no data loss. but If your device bootloader is not unlocked, then unlocking your device data will be erased.
Do we flash magisk or other way of root ?
theogr91 said:
Do we flash magisk or other way of root ?
Click to expand...
Click to collapse
You need not flash anything extra than flashing customized boot.img. Just simply follow this step and your device will be rooted.
Worked like charm thanks. Will the phone be ok after an OTA update ?
Help...After flashing boot image and rebooted , Wifi is not scanning the networks and I am unable to take calls but 4g(internet) is working fine. Please reply me for any fix. I followed the exact steps you mentioned. My Device Realme Gt neo 2 UI 3.0
mahesh.pujala said:
Help...After flashing boot image and rebooted , Wifi is not scanning the networks and I am unable to take calls but 4g(internet) is working fine. Please reply me for any fix. I followed the exact steps you mentioned. My Device Realme Gt neo 2 UI 3.0
Click to expand...
Click to collapse
In my case, all is fine.
You can try backup data and then reset your device through recovery.
theogr91 said:
Worked like charm thanks. Will the phone be ok after an OTA update ?
Click to expand...
Click to collapse
After the OTA update, you may need to flash this boot image again.
Help...After flashing boot image and rebooted , Wifi is not scanning the networks and I am unable to take calls but 4g(internet) is working fine. Please reply me for any fix. I followed the exact steps you mentioned. My Device Realme Gt neo 2 UI 3.0
Nurujjamanpollob said:
In my case, all is fine.
You can try backup data and then reset your device through recovery.
Click to expand...
Click to collapse
Thanks for the reply . Any way I reverted back to previous state by flashing stock boot image and firmeware. Now everthing works fine. I will think about rooting later..
Removed root and updated to RMX3370_11_C.04 is it safe to reflash root image on this version?
theogr91 said:
Removed root and updated to RMX3370_11_C.04 is it safe to reflash root image on this version?
Click to expand...
Click to collapse
I just tried this and it worked for me...
Meanwhile I realised that my wifi and my phone don't work anymore... I have no idea if this boot image is the cause.
Grobie13 said:
Meanwhile I realised that my wifi and my phone don't work anymore... I have no idea if this boot image is the cause.
Click to expand...
Click to collapse
I have no wifi after the flash and i have no twp on RMX3370_11_C.04 any way to fix it ?
theogr91 said:
I have no wifi after the flash and i have no twp on RMX3370_11_C.04 any way to fix it ?
Click to expand...
Click to collapse
No solution so far. I think first everything was fine, after flashing the magisk boot image it's gone worse... But I'm not sure.
I do not recommend updating on RMX3370_11_C.0. After flashing boot image (without Magisk) wifi no longer working.
I flashed clean firmware and lock bl i am done moding this device only adb debloat.. And after clean flash netflix still wont open login screen...
Grobie13 said:
No solution so far. I think first everything was fine, after flashing the magisk boot image it's gone worse... But I'm not sure.
Click to expand...
Click to collapse
What device variant you use? India or global?
Probably I gonna update this boot image today with latest update.
Nurujjamanpollob said:
What device variant you use? India or global?
Probably I gonna update this boot image today with latest update.
Click to expand...
Click to collapse
It's global respectively EU. But I start from scratch yesterday. I flashed twrp, format data and flashed magisk. But other people need your patched boot image. Thanks for providing.

Categories

Resources