Just flashed the the new images from MHC19I but left my recovery and userdata partition untouched. Before booting into system i booting into TWRP and was greeted with the enter password to decrypt the data partition.
The new Twrp is out now 3.0.0-1 HERE
Let me know if this helps guys and gals.
jerflash said:
Just flashed the the new images from MHC19I but left my recovery and userdata partition untouched. Before booting into system i booting into TWRP and was greeted with the enter password to decrypt the data partition. This never happened to me before so it must be something in the new bootloader image or boot image that is causing this.
Does anyone else see this? I was going to test downgrading the bootloader later on today to see if the block is gone but it looks like the "default password" for encryption may have changed.
Let me know guys.
Click to expand...
Click to collapse
New TWRP test builds already out there that take care of the issue.
rebretz000 said:
New TWRP test builds already out there that take care of the issue.
Click to expand...
Click to collapse
yes i see that and i am going to flash it now. i had to read through that whole thread though. i will post it above for others.
Thanks. The TWRP fix did the trick for me. To summarize for others, these are the steps I took after d/ling the new factory image:
adb reboot bootloader
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-03.51.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-03.61.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
fastboot reboot-bootloader
fastboot flash recovery twrp-test1-3.0.0-0-angler.img
fastboot reboot-bootloader
boot into TWRP -> Flash SuperSU
Reboot System -> Wait for cache to build
(optional) Open ElementalX app and install
Profit
johnny2678 said:
Thanks. The TWRP fix did the trick for me. To summarize for others, these are the steps I took after d/ling the new factory image:
adb reboot bootloader
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-03.51.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-03.61.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
fastboot reboot-bootloader
fastboot flash recovery twrp-test1-3.0.0-0-angler.img
fastboot reboot-bootloader
boot into TWRP -> Flash SuperSU
Reboot System -> Wait for cache to build
(optional) Open ElementalX app and install
Profit
Click to expand...
Click to collapse
I noticed that after flashing MHC19I (and N preview) I lost TWRP every time I booted into the system. Have you seen this? Over on another MHC19I thread, someone suggested renaming 'recovery-from-boot.p' from TWRP to avoid this.
This did happen to me with a broken system though, so maybe there were some checks triggered that made the system flash stock recovery again.
Awesome test build! It works like a charm
havanahjoe said:
I noticed that after flashing MHC19I (and N preview) I lost TWRP every time I booted into the system. Have you seen this? Over on another MHC19I thread, someone suggested renaming 'recovery-from-boot.p' from TWRP to avoid this.
This did happen to me with a broken system though, so maybe there were some checks triggered that made the system flash stock recovery again.
Click to expand...
Click to collapse
this happens because you booted into Android before flashing SuperSu or disabling the recovery-from-boot
when you flash the last item, in my case it was vendor.img, i clicked volume down on my phone, and went into recovery. i then selected SuperSu2.68 and flashed that. Then rebooted.
chaco81 said:
this happens because you booted into Android before flashing SuperSu
Click to expand...
Click to collapse
That would explain it. I didn't know SuperSu took care of this. Thank you
Is SuperSU 2.68 systemless as well? I'm on 2.67 still because I haven't seen any confirmation otherwise. Thanks!
Yes. I use the same version.
allen099 said:
Is SuperSU 2.68 systemless as well? I'm on 2.67 still because I haven't seen any confirmation otherwise. Thanks!
Click to expand...
Click to collapse
Just a quick question. Why does everyone suggest fastboot flashing with IMG files one by one? Why not just use the batch file included in the main Nexus image download? Assuming that most would want to keep apps and data intact, you simply need to remove the "-w" from the batch file as I understand it. In doing so, you keep all data/apps/SD card info, correct?
floepie said:
Just a quick question. Why does everyone suggest fastboot flashing with IMG files one by one? Why not just use the batch file included in the main Nexus image download? Assuming that most would want to keep apps and data intact, you simply need to remove the "-w" from the batch file as I understand it. In doing so, you keep all data/apps/SD card info, correct?
Click to expand...
Click to collapse
I was also wondering the same
Sent from my Nexus 6P using Tapatalk
floepie said:
Just a quick question. Why does everyone suggest fastboot flashing with IMG files one by one? Why not just use the batch file included in the main Nexus image download? Assuming that most would want to keep apps and data intact, you simply need to remove the "-w" from the batch file as I understand it. In doing so, you keep all data/apps/SD card info, correct?
Click to expand...
Click to collapse
mickyw1980 said:
I was also wondering the same
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you do that it will flash all of the images.... That includes the userdata.img which also wipes your device. This is something most people updating do not want. Plus it just gives you more control.
Sent from my Nexus 6P using Tapatalk
johnny2678 said:
Thanks. The TWRP fix did the trick for me. To summarize for others, these are the steps I took after d/ling the new factory image:
adb reboot bootloader
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-03.51.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-03.61.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
fastboot reboot-bootloader
fastboot flash recovery twrp-test1-3.0.0-0-angler.img
fastboot reboot-bootloader
boot into TWRP -> Flash SuperSU
Reboot System -> Wait for cache to build
(optional) Open ElementalX app and install
Profit
Click to expand...
Click to collapse
This allows you to keep encryption?
jerflash said:
If you do that it will flash all of the images.... That includes the userdata.img which also wipes your device. This is something most people updating do not want. Plus it just gives you more control.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No, it doesn't. If you remove the -w from the batch file, it won't overwrite your userdata. That's common knowledge here.
floepie said:
No, it doesn't. If you remove the -w from the batch file, it won't overwrite your userdata. That's common knowledge here.
Click to expand...
Click to collapse
That may be true but if you don't know to do that it will wipe everything. Just always been safer to do it individually.
Sent from my Nexus 6P using Tapatalk
gts24 said:
This allows you to keep encryption?
Click to expand...
Click to collapse
Looks like it does. Is there another way to tell?
{
"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"
}
Sent from my Nexus 6P using Tapatalk
I always flash system, boot, vendor through fastboot. Sometimes I also update the bootloader and the radio if there is a newer version available. All other IMG files are not necessary. It´s true that flashing the stuff one by one gives you more control ( and a dirty flash is also great for lazy guys like me who want to keep all their Apps, settings etc. ).
johnny2678 said:
Looks like it does. Is there another way to tell?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I just followed your flow chart , worked here as far as I can tell as well. (proper thanks button clicked )
When I flashed this morning and entered TWRP recovery it must of tripped something as the yellow "cannot check for corruption" warning changed to a red "Your device is corrupt" message. It still only shows for a few seconds before booting like normal. I can't really try anything until I get home, but will flashing the patched TWRP and booting into it be enough to change that back to the old yellow warning? Or do I need to reflash the system/boot packages again?
Related
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Fastboot flash the images. Then reroot.
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
TenderloinShadow said:
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=56921581&postcount=33
That post left out flashing recovery. The download should have 6 files. I flashed recovery at the end (but I don't think it matters how you flash the files, I could be wrong though).
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
di11igaf said:
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
Click to expand...
Click to collapse
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
ericplatham said:
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
Click to expand...
Click to collapse
You're right, now that I think about it, I believe I had to do that as well last time I flashed a factory image.
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
GatorsUF said:
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
Click to expand...
Click to collapse
maybe I'll write up a guide, but download the factory image, extract it. In there is a zip file, extract it too. Then Google 15 second adb install xda. That'll set up fastboot on your pc. Then boot into the bootloader and in a command window opened in the folder where the bootloader image is located run the commands:
fastboot flash bootloader bootloader.img. Note, use the full name of the bootloader.img
fastboot reboot-bootloader
fastboot -w
Open the folder where the boot, system, cache, system, and vendor images are located. Open a command window in that folder and run the commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Then you're done
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Then you're done
Click to expand...
Click to collapse
He will still have to reroot and flash custom recovery... but you got 95% of the process :laugh:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
rank78 said:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
Click to expand...
Click to collapse
Since its a small update you could probably get by just flashing the system and boot images. But I haven't tried it
Sent from my Nexus 5 using XDA Free mobile app
I'd flash everything as described to be safe, I just prefer simply flashing a zip and moving on.
Will updating thru adb wipe my device?
GatorsUF said:
Will updating thru adb wipe my device?
Click to expand...
Click to collapse
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, I have actually flashed a few times thru fastboot in the past so I'm not totally lost on the idea. I've always used tibu in the past, will Google restore my data too?
TenderloinShadow said:
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Click to expand...
Click to collapse
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
fhem said:
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
Click to expand...
Click to collapse
Why erase recovery twice?
Just dont flash stock recovery
fhem said:
STEP #1
fastboot flash bootloader {bootloader.img}
Click to expand...
Click to collapse
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Double_U said:
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Click to expand...
Click to collapse
Hi, Double_U...
Are you sure you've typed the EXACT command..?
Code:
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
Reboot the bootloader, enter fastboot, and try again.
Rgrds,
Ged.
How to flash a factory image | Return to stock | Unroot your Nexus 6P
Hello Nexus 6P Users!
This tutorial will show you how to reset/unroot/save your Nexus 6P by flashing the Google Factory Images.
{
"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"
}
WARNING!!!
This process will wipe your phone completely. Backup your storage before you continue.
I am also not responsible if anything goes wrong.
FOLLOW EVERY SINGLE STEP
or you will end up in a bootloop, or with a bricked phone, and we don't want that
Let's get started!!
Setting up
For this process, you will need to:
★Install adb and fastboot drivers. To do this, use this simple program:
http://forum.xda-developers.com/showthread.php?t=2588979
For MAC and Linux users: simply follow these instructions:
http://forum.xda-developers.com/showthread.php?t=2638673
Off-topic: installing ADB and Fastboot so easily, what a time to be alive!
★Download the latest factory images from here:
https://developers.google.com/android/nexus/images#angler
★Extract the archive you downloaded (Use WinRAR). It should look like this:
★Unlock your bootloader (In case you haven't already). Only follow step 1 from this thread:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Flashing the factory images
There is more than one way to flash these images. Each give the same results, but the first is for lazy (or smart) users
Method 1. Easy method.
★Power off your phone.
★Boot it in fastboot by pressing and holding Power Button + Volume Down at the same time.
★Connect your phone to your PC through your USB cable.
★Execute the flash-all.bat script (for Windows) or flash-all.sh(for MAC and LINUX) in the folder where you extracted the factory images.
**!!** For MAC: You'll have to edit the flash-all.sh, and add "./" before every fastboot command.
★Wait for everything to flash.
★After everything finished, select "Recovery" using the volume buttons.
★When a small dead Android appears, press Power Button + Volume UP.
★Select "Wipe data/factory data reset"
★Reboot. Your phone should be stock. :good:
Method 2. Long method (Same thing actually, but I'll mention it, just in case first one does not work)
★Extract the image-angler-xxxxxx.zip from the previously extracted folder somewhere easy to access (On C:\images for example. Make it easy to type). You will have the following files:
★In the new folder, from the original archive/folder, extract "bootloader-angler-angler-XX.XX.img" (rename it to bootloader.img) and "radio-angler-angler-XX.XX" (rename it to radio.img)
★Power off your phone.
★Boot it in fastboot by pressing and holding Power Button + Volume Down at the same time.
★Connect your phone to your PC through your USB cable.
★Open a CMD window.
★Type the following commands, in this order (If you have a different folder, change the path)
Code:
fastboot flash bootloader C:/images/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/images/radio.img
fastboot reboot-bootloader
fastboot flash system C:/images/system.img
fastboot flash vendor C:/images/vendor.img
fastboot flash userdata C:/images/userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:/images/boot.img
fastboot flash recovery C:/images/recovery.img
fastboot erase cache
fastboot flash cache C:/images/cache.img
★After everything finished, select "Recovery" using the volume buttons.
★When a small Android appears, press Power Button + Volume UP.
★Select "Wipe data/factory data reset"
★Reboot. Your phone should be stock. :good:
And now you have a brand new Nexus 6P (software wise, at least). Congratulations!
Credits and Thanks:
@Mr hOaX
Got some fastboot command "updates" from you
@Heisenberg
Really cool root tutorial
err.... Heisenberg's already have a tutorial on how to return to stock... not sure why we need a duplicate posting..
#9 How To Flash The Factory Images (And Return To Stock)
abaaaabbbb63 said:
Credits and Thanks:
Mr hOaX
Got some fastboot command "updates" from you
Heisenberg
Really cool root tutorial
Click to expand...
Click to collapse
Nice to see you here bro
Good job
This guy's tutorial will really save your nexus for sure
gd6noob said:
err.... Heisenberg's already have a tutorial on how to return to stock... not sure why we need a duplicate posting..
#9 How To Flash The Factory Images (And Return To Stock)
Click to expand...
Click to collapse
I thought that a separate thread would raise its visibility and would be easier to spot for users that do not know their way around XDA that well.
abaaaabbbb63 said:
I thought that a separate thread would raise its visibility and would be easier to spot for users that do not know their way around XDA that well.
Click to expand...
Click to collapse
Followed the instructions and im getting an error cant find the files
joeyac02 said:
Followed the instructions and im getting an error cant find the files
Click to expand...
Click to collapse
Can you describe what exactly did you do?
At which point did you encounter the error?
When I download the images it doesn't contains Angler-bootloader and Radio.img. It only contains one file with the boot.img, etc... I tried downloading all the 6.0.0 link and it's all the same . I don't understand.
Thank you for the post. Hope I don't need to use it tho. :good:
I cannot make phone calls through the phone app?
I followed directions step by step but every time I get to the dead android guy and hold vol up + pow. I do not get the "stock" recovery where I could choose to data/factory reset, I just get the little dead android guy again.
Any help?
Nice guide
Sent from my Nexus 6P using Tapatalk
From Heisenberg post says that
Note: You should never flash the userdata image. It doesn't take into consideration the storage capacity of the device and always allocates 32gb of storage. This is ok for the 32gb model, but for the 64gb and 128gb models you'll end up with much less storage capacity than you should have.
Click to expand...
Click to collapse
And I have 64gb of storage. should I wipe or flash?
cediedc said:
From Heisenberg post says that
And I have 64gb of storage. should I wipe or flash?
Click to expand...
Click to collapse
You can do both. Just in case, your storage spaces shows reductions after flashing (Like my 64GB variant shows 32 GB), you can fix it by wiping data from stock recovery.
If you're not willing to remove the data on your internal storage, you can skip flashing userdata.img.
tried to go back to stock but stuck on google logo..what to do?
jordy787 said:
tried to go back to stock but stuck on google logo..what to do?
Click to expand...
Click to collapse
Did you flash the the correct vendor.img, corresponding to your factory image?
DJBhardwaj said:
Did you flash the the correct vendor.img, corresponding to your factory image?
Click to expand...
Click to collapse
nope just the factory image from google..can you send me the link to the vendor img for latest stock build? and do i fastboot flash it? thanks
jordy787 said:
nope just the factory image from google..can you send me the link to the vendor img for latest stock build? and do i fastboot flash it? thanks
Click to expand...
Click to collapse
Vendor.img is already included in the factory image. If you used flash-all.bat script, it must have been flashed. What commands did you precisely use to flash the factory image?
cediedc said:
From Heisenberg post says that
And I have 64gb of storage. should I wipe or flash?
Click to expand...
Click to collapse
Don't ever flash it. It has no benefit and only causes problems. If you need to wipe your storage use this command:
Code:
fastboot format userdata
jordy787 said:
tried to go back to stock but stuck on google logo..what to do?
Click to expand...
Click to collapse
Did you wipe data with TWRP first? That's probably what's causing your problems. Vendor most likely has nothing to do with it.
Heisenberg said:
Did you wipe data with TWRP first? That's probably what's causing your problems. Vendor most likely has nothing to do with it.
Click to expand...
Click to collapse
I used the wug tool kit and it worked
Forgive My Poor English
I already post the recovery to develop section at HERE
RECOVERY FOR MI 8 SE
DOWNLOAD
drive.google.com/open?id=1X39kp3oBz-SYD-fNK-uEgD6VlUUG-WMq
HOW TO FLASH
Power off your phone and press volume down key and press power key to boot to Fastboot Mode
Download Fastboot tools...(Sorry I can't provide this tool)
open a command line(cmd or powershell in windows) and change directory to the directory where fastboot tool locate(cd PATH/TO/FASTBOOT/TOOL), then you can use fastboot simplely
use
Code:
fastboot flash recovery [PATH TO THE IMAGE FILE YOU DOWNLOADED]
to flash
then use
Code:
fastboot reboot recovery
to boot the recovery
IF YOUR BOOTLOADER IS LOCKED,but you wanna try it
You can use
Code:
fastboot boot [PATH TO THE IMAGE FILE YOU DOWNLOADED]
to boot the recovery(not flash recovery)
(not sure 100% success)
Do anything on YOUR OWN RISK
Pictures(and How to set language to English )
Pictures:
And How to set language to English(almost TWRP recovery can use this way)
Decrypt data partition (input your password or you cant mount data partition)
{
"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"
}
Next screen is 'Keep system partition read-only'
Left bottom is keep system RO,Right Buttom is change Language(no pic )
this is the Main screen and you can follow these steps to change Language to ENGLISH
Finally, something to start with
bao lu your QQ number
i dont understand why the board name is sirius... there is one allready , some Sony xperia z2
I hope you will post a little more detailed installation ...
Xiaomi devices:
Install TWRP via Fastboot mode, then install our ROM
Code:
fastboot flash recovery twrp.img
fastboot boot twrp.img
This will be all?
I presume i have to rename the recovery-TWRP-3.2.1-0629-XIAOMI8SE-CN-wzsx150.img to twrp.img ?
marcel112 said:
I presume i have to rename the recovery-TWRP-3.2.1-0629-XIAOMI8SE-CN-wzsx150.img to twrp.img ?
Click to expand...
Click to collapse
You don't need to rename any file to flash. For simplicity yes if you like.
_katho_ said:
You don't need to rename any file to flash. For simplicity yes if you like.
Click to expand...
Click to collapse
ok, let me refrace:
If i like to flash this recovery for the SE, for it to work, i have to follow the two comments, after renaming the .img to twrp.img
fastboot flash recovery twrp.img
fastboot boot twrp.img
After format data - reboot to recovery - wipe dalvik/etc... Install xiaomi.eu rom.
Stuck by bootloop
marcel112 said:
ok, let me refrace:
If i like to flash this recovery for the SE, for it to work, i have to follow the two comments, after renaming the .img to twrp.img
fastboot flash recovery twrp.img
fastboot boot twrp.img
Click to expand...
Click to collapse
Yes, that should work, it's the usual way to flash twrp.
i tried today to flash twrp, unsuccessfully
I installed fastboot and adb drivers ( flashed miui 10 beat using mi flash tool allready )
I enter fastboot on device
i open cmd prompt
i first enter: fastboot devices, then i get respons with devices number
When i enter command: fastboot flash recovery recovery.img
i get :
target reported max download size of 536870912 bytes
sending 'recovery' (29856 KB)...
but thats it........ nothing happens anymore!!
I tried and waited long time
Who can tell me what is going wrong
---------- Post added 6th July 2018 at 12:40 AM ---------- Previous post was 5th July 2018 at 11:46 PM ----------
I can put the phone in fastboot mode....
As soon as i connect phone to laptop, it takes 1 sec , then phone goes out off fastboot and in de left top corner are very very small letters.
I believe it says, press key to reboot, but like i say, very hard to read.
Phone reboots , then it gives battery in center off screen.
When i pess power again.
All goes normall and i can use phone as it should.
When i use updater app, and choose: reboot to recovery, it does like it should.
I can chooose reboot, wipe data and use mi assistent i believe.
Any idea would be awesome
skolarek said:
After format data - reboot to recovery - wipe dalvik/etc... Install xiaomi.eu rom.
Stuck by bootloop
Click to expand...
Click to collapse
You can try 'Disable DM-verify in 'Advance'...
maybe it work
marcel112 said:
i tried today to flash twrp, unsuccessfully
I installed fastboot and adb drivers ( flashed miui 10 beat using mi flash tool allready )
I enter fastboot on device
i open cmd prompt
i first enter: fastboot devices, then i get respons with devices number
When i enter command: fastboot flash recovery recovery.img
i get :
target reported max download size of 536870912 bytes
sending 'recovery' (29856 KB)...
but thats it........ nothing happens anymore!!
I tried and waited long time
Who can tell me what is going wrong
---------- Post added 6th July 2018 at 12:40 AM ---------- Previous post was 5th July 2018 at 11:46 PM ----------
I can put the phone in fastboot mode....
As soon as i connect phone to laptop, it takes 1 sec , then phone goes out off fastboot and in de left top corner are very very small letters.
I believe it says, press key to reboot, but like i say, very hard to read.
Phone reboots , then it gives battery in center off screen.
When i pess power again.
All goes normall and i can use phone as it should.
When i use updater app, and choose: reboot to recovery, it does like it should.
I can chooose reboot, wipe data and use mi assistent i believe.
Any idea would be awesome
Click to expand...
Click to collapse
ehhh,
you can try run this
fastboot boot [RECOVERY IMAGE YOU DOWNLOADED]
and the phone will boot to the recovery(but it still not flash into your phone)
and use the recovery to flash recovery
if you still get a stuck at
sending boot ......
trying change a computer or change a cable and retry it
q792602257 said:
ehhh,
you can try run this
fastboot boot [RECOVERY IMAGE YOU DOWNLOADED]
and the phone will boot to the recovery(but it still not flash into your phone)
and use the recovery to flash recovery
if you still get a stuck at
sending boot ......
trying change a computer or change a cable and retry it
Click to expand...
Click to collapse
Well i upgraded to succesfull flash twrp
after that i used fastboot boot twrp.img
I booted in twrp, changed the lang to english.
Choose keep system read only
Can use it, but when i tried to backup i get backup failed.
I also cant seem to find the internal storage... i can use the fiel manager, but i dont find the folders like in normal working mode
So i cant backup, flash magisk, so i dont dare to wipe and flash , lets say eu.rom
marcel112 said:
Well i upgraded to succesfull flash twrp
after that i used fastboot boot twrp.img
I booted in twrp, changed the lang to english.
Choose keep system read only
Can use it, but when i tried to backup i get backup failed.
I also cant seem to find the internal storage... i can use the fiel manager, but i dont find the folders like in normal working mode
So i cant backup, flash magisk, so i dont dare to wipe and flash , lets say eu.rom
Click to expand...
Click to collapse
the first screen is use to deecrypt data partition ,if you select cancel or input wrong password,you can't modify data partition
if you dont know the password,you can simply format data partition,but you will loose all data(include internal storage)
q792602257 said:
the first screen is use to deecrypt data partition ,if you select cancel or input wrong password,you can't modify data partition
if you dont know the password,you can simply format data partition,but you will loose all data(include internal storage)
Click to expand...
Click to collapse
whats should be the pasword?
Is that my pin how i unlock my device?
Edit:
And if i choose format data, then my internal partition will be wiped.
How can i flash a new zip file, like magisk or eu.miui rom.
Or after format data i can backup current china beta 10 8.7.5.
Then reboot in system, copy this eu miui rom zip to internal and reboot to twrp again.
Wipe device and flash the eu miui zip file?
What if i wipe and can flash eu miui file.
Can i flash using fastboot a rom?
I mean, can i go back to china beta rom?
I have a ch image 8.6.28
marcel112 said:
whats should be the pasword?
Is that my pin how i unlock my device?
Edit:
And if i choose format data, then my internal partition will be wiped.
How can i flash a new zip file, like magisk or eu.miui rom.
Or after format data i can backup current china beta 10 8.7.5.
Then reboot in system, copy this eu miui rom zip to internal and reboot to twrp again.
Wipe device and flash the eu miui zip file?
What if i wipe and can flash eu miui file.
Can i flash using fastboot a rom?
I mean, can i go back to china beta rom?
I have a ch image 8.6.28
Click to expand...
Click to collapse
The password is your pin code to unlock your phone,and you can mount data partition success
if you can't successfully mount data partition , you can
In the Recovery : Click Advance-> ADB SIDELOAD
and connect your phone to PC
use
Code:
adb sideload [PATH TO ROM ZIP FILE]
to flash without copy that zip file to your phone
also since you can mount data partition successfully,you can connect to PC, copy that zip file to Internal storage to flash
If you change your ROM,you can easily flash that 'fastboot rom' back via fastboot(WARNING : Do not flash wrong ROM,it may replace the bootloader)
and you can go back to china beta rom anytime you want(Just need flash the phone again)
maybe a little hard to understand , sorry for my poor English
Guys problem..
I made backup off miui 10 beta chinese
I wiped system/cache/data/dalvik..
Flashed new eu.miui 8.6.28 rom... install is all good.
When i boot, it is stuck in bootloop
(tried to look for : Disable DM-verify in 'Advance
I can see it not in advance..
Now i am stuck with non working phone..
Who can help me ( fast ?
marcel112 said:
Guys problem..
I made backup off miui 10 beta chinese
I wiped system/cache/data/dalvik..
Flashed new eu.miui 8.6.28 rom... install is all good.
When i boot, it is stuck in bootloop
(tried to look for : Disable DM-verify in 'Advance
I can see it not in advance..
Now i am stuck with non working phone..
Who can help me ( fast ?
Click to expand...
Click to collapse
You have to format Data!!
Superwitschi said:
You have to format Data!!
Click to expand...
Click to collapse
ok, i did format data
Now all is empty.
I rebooted into TWRP again.
I used USB-OTG to install the rom again.
All going well in install, no error
When i choose reboot, no message: No OS installed...
But still in bootloop!!
marcel112 said:
ok, i did format data
Now all is empty.
I rebooted into TWRP again.
I used USB-OTG to install the rom again.
All going well in install, no error
When i choose reboot, no message: No OS installed...
But still in bootloop!!
Click to expand...
Click to collapse
You can try 'install root' in Advance
maybe the bootloop is cause by the dm-verify in the bootloader
Will there be a TWRP version compatible with oxygen os V14 currently running on European Nord 2?
I tried previous TWRP guides for the Nord 2 but it didn't work.
Recovery OS's like TWRP works with all versions of the nord2 regardless of the update version.
More than likely you didn't follow all steps correctly. There are multiple mistakes you can make which results in the stock recovery OS being reflashed and the TWRP recovery being overwritten; I'm not completely sure of all the scenarios in which this happens, but you definitely made a miss-step somewhere.
I'm also running an EU nord variant with V14 and TWRP works fine, I've just noticed that after a few reboots TWRP partition gets overwritten by the stock OS again, in which case I just simply reflash the TWRP if i need to use it.
Zombnombs said:
Recovery OS's like TWRP works with all versions of the nord2 regardless of the update version.
More than likely you didn't follow all steps correctly. There are multiple mistakes you can make which results in the stock recovery OS being reflashed and the TWRP recovery being overwritten; I'm not completely sure of all the scenarios in which this happens, but you definitely made a miss-step somewhere.
I'm also running an EU nord variant with V14 and TWRP works fine, I've just noticed that after a few reboots TWRP partition gets overwritten by the stock OS again, in which case I just simply reflash the TWRP if i need to use it.
Click to expand...
Click to collapse
oh..ok i didn't know this. Thanls for the information
I actually followed the steps.
fastboot devices -> then flash the vbmeta -> then flash TWRP -> but then i cannot switch to the Recovery anymore.
Booting the phone works fine but i cannot access the recovery anymore and it always directly jumps me back to fastboot mode. I followed several videos and tutorials here but whatever i do what works for others seems to not work for me
Whenever i try it seems like the recovery is gone. Even stock recovery is not accessable anymore. I wonder what i did wrong or if i need to flash other files too.
Copaxy97 said:
oh..ok i didn't know this. Thanls for the information
I actually followed the steps.
fastboot devices -> then flash the vbmeta -> then flash TWRP -> but then i cannot switch to the Recovery anymore.
Booting the phone works fine but i cannot access the recovery anymore and it always directly jumps me back to fastboot mode. I followed several videos and tutorials here but whatever i do what works for others seems to not work for me
Whenever i try it seems like the recovery is gone. Even stock recovery is not accessable anymore. I wonder what i did wrong or if i need to flash other files too.
Click to expand...
Click to collapse
Assuming you've already unlocked bootloader and have all the mediatek drivers and ADB tools installed on your computer; Simply retry flashing vbmeta with the disable verity flag, then reflash twrp, and then reboot into recovery.
Make sure you've got a copy of the vbmeta.img and TWRP.img downloaded and place them in your ADB platform tools folder. Then run these commands
Make sure you shift-right click (for windows) on empty space in your platform tools folder and open powershel or command prompt (this is important), then send the following commands
Code:
fastboot devices
and wait for a response from your device to ensure it's connected
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
then
Code:
fastboot flash recovery [YourTWRPfileName]
eg my twrp file name is TWRPopn2.img so i type "fastboot flash recovery twrpopn2.img"
then
Code:
fastboot reboot recovery
Make sure your ADB terminal and phone both say the flash was succesful after each flash. If not, then you likely didn't flash the partition at all.
My guess is likely that you shift-right clicked to open the powershell window in the wrong folder, such as your desktop, in which case sending the flash commands cann't find the right file to flash? Just a theory. Definitely sounds like your recovery partition got wiped though. You could also try redownloading TWRP to make sure you're using the right version of it.
Zombnombs said:
Assuming you've already unlocked bootloader and have all the mediatek drivers and ADB tools installed on your computer; Simply retry flashing vbmeta with the disable verity flag, then reflash twrp, and then reboot into recovery.
Make sure you've got a copy of the vbmeta.img and TWRP.img downloaded and place them in your ADB platform tools folder. Then run these commands
Make sure you shift-right click (for windows) on empty space in your platform tools folder and open powershel or command prompt (this is important), then send the following commands
Code:
fastboot devices
and wait for a response from your device to ensure it's connected
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
then
Code:
fastboot flash recovery [YourTWRPfileName]
eg my twrp file name is TWRPopn2.img so i type "fastboot flash recovery twrpopn2.img"
then
Code:
fastboot reboot recovery
Make sure your ADB terminal and phone both say the flash was succesful after each flash. If not, then you likely didn't flash the partition at all.
My guess is likely that you shift-right clicked to open the powershell window in the wrong folder, such as your desktop, in which case sending the flash commands cann't find the right file to flash? Just a theory. Definitely sounds like your recovery partition got wiped though. You could also try redownloading TWRP to make sure you're using the right version of it.
Click to expand...
Click to collapse
Thanks for your help. I will try that again later.
What i can say i 100% opened the command prompt in the correct folder and the flash always said succesful.
I also thought about the command promt folder error before but it is correct. At least somehting got wiped (my recovery) but i simply cannot access it.
I will try again later and go over each step step by step and share ym results here. I hope i did a mistake because otherwise i don't know how to locate the problem.
Okey i did it again like the tutorial and also a second time like you said but it sadly didn't work.
{
"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"
}
This is my output from the command line. i use minimal ADB and fasstboot. But normal powershell by shift right click gives me the same output.
But when i try to reboot and boot into the recovery it just jumps to fastboot mode. So the stock recovery got flashed or removed then. But why i cannot boot into twrp?
Bootloader unlocked and based on the messages in the cmd everything fine.
Any ideas?
***Edit***
It worked now. If you ask me why, i don't know.
I did exactly the same in minimal adb and fastboot tools and on powershell. Both didn't work.
I did it in total 5 times and the last one in powershell randomly was succesful lol.
weird...
looks like the issue is more likely to do with your method of rebooting into recovery, as your reboot command did not seem to work.
Could be an issue with MinimalADB, or many other factors. If you're using the power button and volume keys combination, make sure you do it with your phone unplugged, as with the phone plugged in the combination boots to fastboot instead of recovery.
Zombnombs said:
looks like the issue is more likely to do with your method of rebooting into recovery, as your reboot command did not seem to work.
Could be an issue with MinimalADB, or many other factors. If you're using the power button and volume keys combination, make sure you do it with your phone unplugged, as with the phone plugged in the combination boots to fastboot instead of recovery.
Click to expand...
Click to collapse
Yeah might be true. I don't know.
Disclaimer: I am not responsible for bricked devices, dead SD cards, etc!
Warning: This procedure didn't work for some! Please test at your own risks!
Additional warning: do not relock your bootloader once your global rom is installed. You risk bricking your device.
1. Make sure your bootloader is unlocked
2. Download the images provided in the link below
3. Boot your device to recovery (hold volume up and power until reboot)
4. Wipe data
5. Boot your device to bootloader (hold volume down and power until reboot)
6. Connect your device to PC (make sure you have installed fastboot on your PC)
7. From windows command prompt cd into the folder containing the images
8. Install rooted or not boot image
Code:
fastboot flash boot boot.img
OR
Code:
fastboot flash boot boot_magisk.img
9. Run the following commands to flash all other images
Code:
fastboot flash dtbo dtbo.img
fastboot flash engineering_cdt engineering_cdt.img
fastboot flash metadata metadata.img
fastboot flash oplusreserve2 oplusreserve2.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash super super.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash userdata userdata.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
When flashing super.img, if you get the message Invalid sparse file format at header magic, this is fine.
9. You should then be able to boot into system
RMX3301 Stock files: https://drive.google.com/drive/folders/1-0pNU8DMhzQJjdIMYM_khqA5ASGqWatg
Mirror: https://mega.nz/folder/kw8w1QYR#Uro0gLle8Yr5uRZrqoyByg
{
"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"
}
Can anyone confirm this worked for them?
Great post. What is the Widevine level after installing the global rom? Furthrmore, does SafetyNet pass and do OTA updates work?
logmms said:
Great post. What is the Widevine level after installing the global rom? Furthrmore, does SafetyNet pass and do OTA updates work?
Click to expand...
Click to collapse
Google pay works, safetynet passes with Magisk module (probably good if you unroot and relock the bootloader but then you'll be stuck until realme unlocks the RMX3301).
but level 3 widevine unfortunately. Also some apps do detect that bootloader is unlock even with safetynet module.
Came here to say that this is working! Got my chinese version today and wanted to give it a try right away.
If this command takes a lot of time and seems like the console froze, don't panic!
Code:
fastboot flash vbmeta_vendor vbmeta_vendor.img
Almost every command took like 20 seconds, this one took almost 200, but it finishes eventually.
Also, you may end up stuck on a bootloop. But there's an easy fix, as myogui said on another thread:
Enter recovery mode, wipe data. Enter fastboot and then run the last 2 commands again:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
Now everything's working, and have been running the global rom all day flawlessly!
Does anyone know how to solve the bootloop problem? I tried the last 2 comands, Wipe Data, last 2 comands again... Flashing everything again... Nothing...
Any help would be very apreciate. Thanks.
UPDATE: It's working now.. lol... I tried flashing back to the Chinese version from myogui, still in bootloop.. Then I execute the comand "fastboot flash vbmeta vbmeta.img", bootloop... Then a tons of research... Then I downloaded a RMX3301 17.5GB .ofp file to try flashing from realme Flash Tool... Then I go to sleep... Then I woke up and just go to PC to fix this thing, but realme Tool didn't work, the Flash Tool said "CANNOT FIND CENTRAL DIRECTORY".... Then I just tried flashing here again with the files and comands above... what the hell, I'm screwed anyway... But this time worked.... LOL...
Big thanks guys!
Trying to lock again the bootloader... and then a message appears saying the flash was broken or something... now I can't even turn this thing off... Just keep flashing "realme Powered by android" screen rebooting again and again and again...
Oh my... to good to be true...
Tip: Just buy the global version.
No luck. Have tried all combinations of solutions and still stuck in bootloop. Have flashed it fresh 8 times and no luck. Also tried the last two commands above and no luck. And can't use OFP method as realme tool not updated for Gt 2 Pro
if you're stuck in bootloop try making sure you have the latest version of sdk platform tools, 33.0.1 worked for me.
try running the commands in this order
Code:
fastboot flash boot boot_magisk.img
fastboot flash dtbo dtbo.img
fastboot flash engineering_cdt engineering_cdt.img
fastboot flash metadata metadata.img
fastboot flash oplusreserve2 oplusreserve2.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash super super.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash userdata userdata.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
fastboot flash boot boot_magisk.img
then on your phone hit power button with start selected
Would relocking the bootloader after flashing the global brick me?
You would need to install Chinese rom again using another method of installation or wait for deep testing app to be available on global. But you could still use your device with the global version.
Bnblare said:
Would relocking the bootloader after flashing the global brick me?
Click to expand...
Click to collapse
Mine bricked, now it's hard brick... The closest that I got it to back to life was with QFIL, but something keep giving errors when I try to flash... Now I'm gonna try the MSM... If doesn't work maybe I'm gonna return the phone... Or wait until realme release a useful flash tool... Who knows...
I do not recomend locking back the phone based on my experience.
hacls said:
Mine bricked, now it's hard brick... The closest that I got it to back to life was with QFIL, but something keep giving errors when I try to flash... Now I'm gonna try the MSM... If doesn't work maybe I'm gonna return the phone... Or wait until realme release a useful flash tool... Who knows...
I do not recomend locking back the phone based on my experience.
Click to expand...
Click to collapse
Wow dude I'm sorry. Did you revert back to stock then try to relock the bootloader? Or did you try to relock while on the global?
myogui said:
You would need to install Chinese rom again using another method of installation or wait for deep testing app to be available on global. But you could still use your device with the global version.
Click to expand...
Click to collapse
Man.. I just wanna play call of duty again lol but it knows even tho my safetynet passes. the app can probably see it's L3 still. I guess I'll wait for realme to release the tool for this phone. I'm pretty sure flashing back to stock using the tool would safely lock the bootloader automatically
Bnblare said:
Wow dude I'm sorry. Did you revert back to stock then try to relock the bootloader? Or did you try to relock while on the global?
Click to expand...
Click to collapse
I tried to lock with the global ROM in it... Then this screen appears...
This photo are not mine, but it's the same screen... After that... Only in EDL mode...
hacls said:
I tried to lock with the global version... Then this screen appears...
View attachment 5591427
This photo are not mine, but it's the same screen... After that... Only in EDL mode...
Click to expand...
Click to collapse
your stuck with no fastboot and corrupted partitions. your gonna have to wait for someone to come out with a UnbrickMe zip or something. does adb recognize the phone?
hacls said:
I tried to lock with the global version... Then this screen appears...
View attachment 5591427
This photo are not mine, but it's the same screen... After that... Only in EDL mode...
Click to expand...
Click to collapse
Very sorry for you mate! I updated the OP to warn about this.
Bnblare said:
your stuck with no fastboot and corrupted partitions. your gonna have to wait for someone to come out with a UnbrickMe zip or something. does adb recognize the phone?
Click to expand...
Click to collapse
ADB doesn't recognize, like I said, for now on only in EDL mode.
Well, I gave up and paid a guy to flash via TeamViewer... And as I imagined... With MSM Download Tool was five clicks and it's done... Ridiculous easy... MSM would be a amazing tool if it were accessible... Unfreaking believable... Oh my...
But, anyway, it's solved. Thanks guys.