CUSTOM ROM FLASHING GUIDE
So finally we have a stable LOS rom and slowly we'll be getting many more n to help everyone these are the steps u should follow to succesfully install custom roms.
STEPS
Starting of most of you will be coming from locked bootloader/ unlocked and never installed anything before if thats the case
unlock through guides already present but remember always STICK TO LATEST STOCK FIRMWARE
Download latest platform tools from here https://developer.android.com/studio/releases/platform-tools
Users coming from stock need to backup internal storage n all other data As stock data is encrypted custom roms cant be flashed without wiping first
To format go to fastboot and run
Code:
fastboot format -w userdata
or simply
Code:
fastboot -w
now ur internal storage is wiped completely along with userdata
Next step is to flash twrp , when ur in fastboot u can see the active slot , this is the slot you need to flash custom rom over
so we need to switch to the inactive slot to do that :
Code:
fastboot set_active a
or
Code:
fastboot set_active b
whichever is the inactive one
once we are in the inactive slot its time to flash TWRP.
find the download link here https://forum.xda-developers.com/zenfone-5z/development/recovery-twrp-3-2-3-x-t3849245
Flash TWRP BOOT IMG by :
Code:
fastboot flash boot twrp.img
For instance if my active slot was B where i had stock rom installed , i will flash TWRP to A, now after finishing above step, u need to reboot to recovery
Go To REBOOT and select slot B ( considering above assumption)
WIPE : go to wipe then select
Data
sytem
Cache
NO NEED TO FORMAT INTERNAL STORAGE IF ALREADY FORMATTED VIA FASTBOOT
This applies even if switching between custom ROMS
If u dont plan on formatting internal storage everytime , my advice would be to flash DFE ( DISABLE FORCE ENCRYPTION )
With this ur custom ROM wont encrypt DATA , and u can switch between roms without wiping internal storage ( WARNING: formatting from fastboot will wipe internal & app data n other userdata must be wiped if switching between two different ROMS) DFE will be linked below
DFE MUST BE FLASHED ON BOTH SLOTS BUT MAINLY UR ACTIVE SLOT WHERE U WILL BE USING CUSTOM ROM
DEFAULT TWRP BEHAVIOUR FOR A/B PARTITION DEVICES IS : ROMS WILL ALWAYS BE FLASHED ON INACTIVE SLOT , i.e: IF TWRP IS ON SLOT A , ROM WILL BE FLASHED ON SLOT B AND VICE VERSA
So for Clarity , lets assume my stock rom was in slot B
Then u need to select SLOT A in reboot settings fo TWRP
Flash ROM
FLASH TWRP ZIP , As Recovery img comes with BOOT.img (since we dont have recovery partition) every time u flash a boot img recovery will be replaced, thus in this case since laos rom or any other comes with their own recovery u need to flash TWRP zip
Most IMPORTANT STEP : After u flash CUSTOM ROM, IT IS ALWAYS RECOMMENDED TO :
REBOOT TO RECOVERY
Click to expand...
Click to collapse
Now since we flashed to OUR ACTIVE SLOT : B, twrp will boot to SLOT B Automatically ( CONSIDERING U FLASHED TWRP ZIP AFTER ROM)
GAPPS AND ADD ON ZIPS ( LIKE MAGISK, MODULES ETC) IS RECOMMENDED TO BE FLASHED ON THE SAME SLOT AS YOUR ROM , AND PREFERABLY TWRP OF THE SAME SLOT
REBOOT ENJOY
Links
Dfe - see attachment
Twrp zip - see attachment
Just for understanding...
what are these slot-A and B?
What could be the size of each slot?
Is this phone partition table unlike any other?
Thanks for the guide dude.
This is what i have understood.
If stock rom is on slot A
Then we have to fastboot flash twrp on slot B
And from that twrp we have to flash custom rom and twrp zip on slot A
Please correct me if I'm wrong.
TechnoTrons said:
Thanks for the guide dude.
This is what i have understood.
If stock rom is on slot A
Then we have to fastboot flash twrp on slot B
And from that twrp we have to flash custom rom and twrp zip on slot A
Please correct me if I'm wrong.
Click to expand...
Click to collapse
Correct!
TechnoTrons said:
Thanks for the guide dude.
This is what i have understood.
If stock rom is on slot A
Then we have to fastboot flash twrp on slot B
And from that twrp we have to flash custom rom and twrp zip on slot A
Please correct me if I'm wrong.
Click to expand...
Click to collapse
Yes correct :good:
DroneJC said:
Just for understanding...
what are these slot-A and B?
What could be the size of each slot?
Is this phone partition table unlike any other?
Click to expand...
Click to collapse
Slot A and Slot B are partitions and its size are same.
It is 2 different blocks in a given memory.
No phone partition layout is different in AB scheme. they both are completely isolated.
do we need to unlock the bootloader before this. If yes, how to do it
Edit- Found it and was able to unlock the bootlocker using the app from Asus Support.
Thank You for this wonderful guide. Have now been able to successfully flash the Pixel experience ROM on the phone.
This is exciting, finally some nice roms for 5Z! Will be playing with this over the weekend. Thank you for your work!
Thanks a lot for your comprehensive guide, got to unlock the bootloader and flash twrp as per the guide.
However, I have a problem booting the ROM; the ROM installs perfectly well and I can reboot into recovery but can't get past the "ASUS" screen upon actually trying to boot the ROM.
Am I missing something? I followed everything down precisely and I honestly don't know what am I messing up.
A little help would be appreciated.
Xadus said:
Thanks a lot for your comprehensive guide, got to unlock the bootloader and flash twrp as per the guide.
However, I have a problem booting the ROM; the ROM installs perfectly well and I can reboot into recovery but can't get past the "ASUS" screen upon actually trying to boot the ROM.
Am I missing something? I followed everything down precisely and I honestly don't know what am I messing up.
A little help would be appreciated.
Click to expand...
Click to collapse
Sure! start of by telling which vendor u were on in stock? .72 is needed for roms ..and looking at ur station I think probably flashing from wrong slot
Rohan purohit said:
Sure! start of by telling which vendor u were on in stock? .72 is needed for roms ..and looking at ur station I think probably flashing from wrong slot
Click to expand...
Click to collapse
I was at .72 itself and my active slot was b, I switched the active slot to a and flashed the the twrp.
Booted into the twrp and switched the slot to b (where my stock is installed) - wiped the data as told and installed the pixel experience ROM - flashed the permanent twrp again and rebooted to twrp (just to check since gapps are already pre-installed in pixel experience).
Rebooted the whole device again from twrp and the loops starts.
Xadus said:
I was at .72 itself and my active slot was b, I switched the active slot to a and flashed the the twrp.
Booted into the twrp and switched the slot to b (where my stock is installed) - wiped the data as told and installed the pixel experience ROM - flashed the permanent twrp again and rebooted to twrp (just to check since gapps are already pre-installed in pixel experience).
Rebooted the whole device again from twrp and the loops starts.
Click to expand...
Click to collapse
Ok u just said data , but system and cache have to be wiped too..if u did then maybe once after wiping reboot to bootloader and select slot as a n then boot to twrp n flash rom
Rohan purohit said:
Ok u just said data , but system and cache have to be wiped too..if u did then maybe once after wiping reboot to bootloader and select slot as a n then boot to twrp n flash rom
Click to expand...
Click to collapse
I meant the data, system and cache just as mentioned in the guide.
I tired the same process switching to different slot (a/b) as well but it still results in a bootloop.
Xadus said:
I meant the data, system and cache just as mentioned in the guide.
I tired the same process switching to different slot (a/b) as well but it still results in a bootloop.
Click to expand...
Click to collapse
If ur following the steps right then a bootloop of that sort could be due to encryption, I suggest u do fastboot format -w userdata
Rohan purohit said:
If ur following the steps right then a bootloop of that sort could be due to encryption, I suggest u do fastboot format -w userdata
Click to expand...
Click to collapse
I did wipe the userdata as well before doing anything.
And i did flash "disableforceencryption.zip" as well during the guide.
Xadus said:
I did wipe the userdata as well before doing anything.
And i did flash "disableforceencryption.zip" as well during the guide.
Click to expand...
Click to collapse
I'd suggest u to follow again properly since all the roms boot but first boot takes a while so maybe u need to wait
Rohan purohit said:
I'd suggest u to follow again properly since all the roms boot but first boot takes a while so maybe u need to wait
Click to expand...
Click to collapse
Maybe i will give another try in the future, for now i flashed the stock as i was frustrated by the whole thing.
Thanks a lot for your help though.
Xadus said:
Maybe i will give another try in the future, for now i flashed the stock as i was frustrated by the whole thing.
Thanks a lot for your help though.
Click to expand...
Click to collapse
I have exactly same problem as you, how did you even flashed the stock rom?
stefanivan97 said:
I have exactly same problem as you, how did you even flashed the stock rom?
Click to expand...
Click to collapse
Use unbrick method, raw firmware in the root guide. Download updates from Asus site and copy into internal memory for latest version. You can try installing whatever you want and if you mess up you can always flash_all cmd and start over.
Related
Hi Guys,
My Mi3 is bricked.I did a repartition some months back and I wanted to install MIUI 7.I used Miflash but it is showing size too large error while flashing.My recovery is replaced with stock recovery.I tried to use ADB to push the file,that is also not working as it is shoing device not found while I am in recovery.I installed Miphonemanager as well for that.But there is no luck.I am out of ideas.Can anyone please help me.
Can anyone let me know which driver I need to choose in driver manager for android in desktop? Currently I tried CMCC Composite ADB driver and Xiaomi Android Interface.
Flash latest TWRP first. What happened during repartition?
You can allways acces the eeprom writer through short circuiting the sim card, there are a lot of tutorials, the only way to brick this phone is breaking its hardware
nsakhare said:
Hi Guys,
My Mi3 is bricked.I did a repartition some months back and I wanted to install MIUI 7.I used Miflash but it is showing size too large error while flashing.My recovery is replaced with stock recovery.I tried to use ADB to push the file,that is also not working as it is shoing device not found while I am in recovery.I installed Miphonemanager as well for that.But there is no luck.I am out of ideas.Can anyone please help me.
Can anyone let me know which driver I need to choose in driver manager for android in desktop? Currently I tried CMCC Composite ADB driver and Xiaomi Android Interface.
Click to expand...
Click to collapse
Install custom recovery through fast boot mode... Then flash the repartition revert zip .. There is one revert zip in miui forum which ends like this "....EIPerroVerde". Only this revert zip works..Then use miflash .. It should work..
Sent from my MI 3W using Tapatalk
aniketkuber said:
Install custom recovery through fast boot mode... Then flash the repartition revert zip .. There is one revert zip in miui forum which ends like this "....EIPerroVerde". Only this revert zip works..Then use miflash .. It should work..
Sent from my MI 3W using Tapatalk
Click to expand...
Click to collapse
The correct repartition zips can be found in the thread in my signature.
Reproduced here for Tapatalk or mobile users:
http://forum.xda-developers.com/xiaomi-mi-3/general/extremely-useful-flashable-zips-t3080860
The Dork Knight Rises said:
The correct repartition zips can be found in the thread in my signature.
Reproduced here for Tapatalk or mobile users:
http://forum.xda-developers.com/xiaomi-mi-3/general/extremely-useful-flashable-zips-t3080860
Click to expand...
Click to collapse
Hey Knight (didn't want to call you Dork :angel: )
I have a messed up phone,
2 questions here :
1- Would repartitioning reset ALL the partitions ?
2- When installing a ROM with fastboot, will ALL the partitions be filled with the necessary data ?
(I'm in doubt because of IMEI data)
Btw, can anyone point me to a link with WORKING fastboot ROM downloads ?
Inonotting said:
Hey Knight (didn't want to call you Dork :angel: )
I have a messed up phone,
2 questions here :
1- Would repartitioning reset ALL the partitions ?
2- When installing a ROM with fastboot, will ALL the partitions be filled with the necessary data ?
(I'm in doubt because of IMEI data)
Btw, can anyone point me to a link with WORKING fastboot ROM downloads ?
Click to expand...
Click to collapse
Repartitioning will wipe both your system partitions [EDIT: Seems I was wrong?]. If you want to use MIUI 7, you can use either extended partition, or stock partition using the zip from my link.
For fastboot I guess you'll need stock.
No, installing a MIUI fastboot ROM shouldn't touch your IMEI. But yeah everything else can be overwritten, depending on which bat file you use when flashing.
The process I'd recommend right now is to flash TWRP IMG using fastboot(use the 15-second ADB installer and look up a tutorial on how to flash an IMG. Basically just put the IMG into the adb/fastboot installation directory and then open a terminal window and then fastboot flash)
And as for MIUI fastboot ROM, you just gotta find the thread on MIUI forums. Google can help
The Dork Knight Rises said:
Repartitioning will wipe both your system partitions. If you want to use MIUI 7, you can use either extended partition, or stock partition using the zip from my link.
For fastboot I guess you'll need stock.
No, installing a MIUI fastboot ROM shouldn't touch your IMEI. But yeah everything else can be overwritten, depending on which bat file you use when flashing.
The process I'd recommend right now is to flash TWRP IMG using fastboot(use the 15-second ADB installer and look up a tutorial on how to flash an IMG. Basically just put the IMG into the adb/fastboot installation directory and then open a terminal window and then fastboot flash)
And as for MIUI fastboot ROM, you just gotta find the thread on MIUI forums. Google can help
Click to expand...
Click to collapse
Thanks ... but ....
I was under the impression that there were many more partitions (about 28).
Check this site:
http://en.miui.com/thread-138246-1-1.html
Basically, I'm looking for an easy way out to make a REAL factory reset from PC.
Inonotting said:
Thanks ... but ....
I was under the impression that there were many more partitions (about 28).
Check this site:
http://en.miui.com/thread-138246-1-1.html
Basically, I'm looking for an easy way out to make a REAL factory reset from PC.
Click to expand...
Click to collapse
Well there ARE a LOT of partitions on any device, but the important ones are system, boot, data, cache, modem etc.
That guide seems to manually mess with the partition table, so it gets down and dirty.
The easiest thing would be to do what I said, flash TWRP or CWM r7 by furniel and then the proper stock partition zip. Then use MiFlash or recovery to flash any ROM.
I think I'm back online
The Dork Knight Rises said:
Well there ARE a LOT of partitions on any device, but the important ones are system, boot, data, cache, modem etc.
That guide seems to manually mess with the partition table, so it gets down and dirty.
The easiest thing would be to do what I said, flash TWRP or CWM r7 by furniel and then the proper stock partition zip. Then use MiFlash or recovery to flash any ROM.
Click to expand...
Click to collapse
OK,
I followed your links and flashed :
First : Repartition to Stock Layout
Then : Repartition to 1.2GB Single System
Strange, after this, I did a normal reboot, it rebooted into my old ROM.
Shouldn't that have been erased after partitioning ?
Anyway,
Then I flashed ; update-XenonHD-08-08-15-signed-.zip
WAIT WAIT .....
as I'm typing, I'm flashing update-XenonHD-09-05-15-signed-cancro.zip,
first ROM in a few weeks that seems to be installing.
Let me check is it really installed .... YEP .... progress
Flashing : pa_gapps-modular-pico-5.1-20150418-signed
Everything seems to be going smooth
OK, for the time being .... all good.
Thanks a lot :good:
If your device cannot boot, flash it thru fastboot mode. See the full detailed tutorial on en.miui.com
Well you can directly flash with miflash even with the extended partition. Just edit the fastboot script (.bat extension with windows) and search for line
fastboot flash system+system1
And then delete system1
Fastboot flash system
And use those script for flashing via miflash
Ok guys, this is a sureshot guide for
PROBLEM
* anyone wanting to decrypt their op3 but stuck at 1+ boot screen(Or not able to boot any custom ROMs.) and only able to restore twrp backups
* After using fastboot format userdata twrp and about phone shows only 32gb phone memory(where the hell is my rest of 32gb )
* Fastboot format userdata resulting in Stuck at boot screen or simply an unbrick trick to return to Stock OOS in unencrypted stage
SOLUTION
1. Use method 2 of Mega unbrick guide to restore your phone to stock partitions found here
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
2. After the flashing is complete do not reboot the phone instead reboot directly into bootloader.
3. In fastboot mode flash modded twrp 3.0.2.22 using command ''fastboot flash recovery recovery.img'' found here
http://forum.xda-developers.com/devdb/project/?id=15934#downloads
4. Reboot directly into twrp and using mtp mode copy latest elemental x kernel or bluspark kernel zip for OOS and SYSTEM supersu.zip into the internal storage. System supersu.zip here OR directly proceed to step 8
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip
5. Now flash system supersu.zip and directly after that kernel.zip
6. Now again reboot to recovery directly and from twrp boot into system.
7. After boot up you system should be decrypted. You can check in security settings.
8.Reboot recovery and flash required firmware + modem zip found here
http://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
9.wipe data +cache +dalvik +system
10. Flash any rom of your choice and go flashoholic, use multirom or whatever you want.
Pheww. Thanks.
Man, Finally the SystemRoot (V4A, MultiROM etc) as we discussed a couple of weeks back with this hassle at the Mega Unbrick and Decrypt guides threads...:highfive:
I saw your post on MultiROM but maybe it got moved I guess...
So are you able to cross flash anything now ?
thanks.
Ashtrix said:
Man, Finally the SystemRoot (V4A, MultiROM etc) as we discussed a couple of weeks back with this hassle at the Mega Unbrick and Decrypt guides threads...:highfive:
I saw your post on MultiROM but maybe it got moved I guess...
So are you able to cross flash anything now ?
thanks.
Click to expand...
Click to collapse
anything... even multirom works flawless.
I will give this a try, Or will try to Flash the EX then perform parts of this since they support Kexec, to see what works, I have data and lot of apps working them again is a real pita with my schedule...
Thanks but, this is basically what i have done to decrypt my op3, i just used the CypherOs ROM instead OxygenOs, fastboot format userdata, reboot to recovery, flash rom, flash elementalx, and i didnt flash Supersu(dont know if thats causing my problem, i dont think so), i also did fastboot format userdata without being stuck at boot logo and still no 32gb, dont know whats the problem
ach3fck said:
Thanks but, this is basically what i have done to decrypt my op3, i just used the CypherOs ROM instead OxygenOs, fastboot format userdata, reboot to recovery, flash rom, flash elementalx, and i didnt flash Supersu(dont know if thats causing my problem, i dont think so), i also did fastboot format userdata without being stuck at boot logo and still no 32gb, dont know whats the problem
Click to expand...
Click to collapse
its different fastboot format userdata causes this Dont know why. I suggest method in the OP. Read carefully and follow it.
nikhilsnigam said:
its different fastboot format userdata causes this Dont know why. I suggest method in the OP. Read carefully and follow it.
Click to expand...
Click to collapse
Aham, so the format userdata causes it, thanks for that. i want to ask you something, after restoring completely with Msmdownloadtool(method2) can i directly reboot to recovery then sideload CB 3.5.5 and then reboot to fastboot and continue with the tutorial? What im saying is my device is decrypted as long it doesnt boot, am i right?
ach3fck said:
Aham, so the format userdata causes it, thanks for that. i want to ask you something, after restoring completely with Msmdownloadtool(method2) can i directly reboot to recovery then sideload CB 3.5.5 and then reboot to fastboot and continue with the tutorial? What im saying is my device is decrypted as long it doesnt boot, am i right?
Click to expand...
Click to collapse
Yes you can but you will be encrypted again. so after msm method reboot fastboot and flash modded twrp. reboot recovery flash CB or OOS. flash supersu flash kernel. Agin flash twrp.img from recovery itself and reboot recovery. After that reboot system and you are good to go. Make sure you have enough system space before flashing supersu and kernel. frow twrp file manager delete unneeded system apps 1st. DO NOT REBOOT in between.
nikhilsnigam said:
Yes you can but you will be encrypted again. so after msm method reboot fastboot and flash modded twrp. reboot recovery flash CB or OOS. flash supersu flash kernel. Agin flash twrp.img from recovery itself and reboot recovery. After that reboot system and you are good to go. Make sure you have enough system space before flashing supersu and kernel. frow twrp file manager delete unneeded system apps 1st. DO NOT REBOOT in between.
Click to expand...
Click to collapse
But i need unlocked bootloader to flash twrp, so i guess i need to unlock after i use Msmdownload tool right?
ach3fck said:
But i need unlocked bootloader to flash twrp, so i guess i need to unlock after i use Msmdownload tool right?
Click to expand...
Click to collapse
your bootloader doesn't get locked
nikhilsnigam said:
your bootloader doesn't get locked
Click to expand...
Click to collapse
Sorry to bother you, but i have one more question, i used Msmdownloadtool before, but only in Qualcomm download mode, can i use fastboot or i have to boot to EDL(qualcomm download mode)? And again sorry for taking your time.
ach3fck said:
Sorry to bother you, but i have one more question, i used Msmdownloadtool before, but only in Qualcomm download mode, can i use fastboot or i have to boot to EDL(qualcomm download mode)? And again sorry for taking your time.
Click to expand...
Click to collapse
you have to use qualcomm download mode by switching off your phone. pressing vol up button and connecting to usb.
nikhilsnigam said:
you have to use qualcomm download mode by switching off your phone. pressing vol up button and connecting to usb.
Click to expand...
Click to collapse
Yeah, i know that, thanks a lot, will try later all of this since i have no time now, will report how it went.Thanks!
I was running Freedom OS CE 2.5 and I dirty flashed official OOS 4.1.0 and got into a bootloop.
I restarted the phone into twrp and it told me that it was read only so I wasn't seeing any zip files. I tried to use repair in the Wipe section by changing file format. I think I chose FAT...I honestly can't remember. But when I swipe to repair and I got stock on updating partition. So I restarted the device into twrp again but this time I'm stock on just the splash screen....won't start.
All I'm getting into is bootloader mode.
Help please
Use fastboot to wipe recovery and flash TWRP again. Alternatively, directly sideload your ROM.
Anova's Origin said:
Use fastboot to wipe recovery and flash TWRP again. Alternatively, directly sideload your ROM.
Click to expand...
Click to collapse
Thank you so much. But what about how I tried changing the format from what it was originally? Should I be worried or that's a minor issue?
ddaharu said:
Thank you so much. But what about how I tried changing the format from what it was originally? Should I be worried or that's a minor issue?
Click to expand...
Click to collapse
You should reformat those partitions that you've changed. Ext4 or f2fs for /data and ext4 for all other partitions. This can be done through either fastboot or TWRP.
Anova's Origin said:
You should reformat those partitions that you've changed. Ext4 or f2fs for /data and ext4 for all other partitions. This can be done through either fastboot or TWRP.
Click to expand...
Click to collapse
Are these the commands I should use?
c:\adb>fastboot erase recovery
c:\adb>fastboot flash recovery twrp
Well as you said, after this I can reenter recovery and reformat the partitions and I should be fine right?
Thanks for all your help man...
ddaharu said:
Are these the commands I should use?
c:\adb>fastboot erase recovery
c:\adb>fastboot flash recovery twrp
Well as you said, after this I can reenter recovery and reformat the partitions and I should be fine right?
Thanks for all your help man...
Click to expand...
Click to collapse
Dont forget the ".img" when referring to images"
c:\adb>fastboot flash recovery twrp.img
Anova's Origin said:
Dont forget the ".img" when referring to images"
c:\adb>fastboot flash recovery twrp.img
Click to expand...
Click to collapse
One last question. Is there any twrp version you'll recommend? Or anyone is good?
ddaharu said:
One last question. Is there any twrp version you'll recommend? Or anyone is good?
Click to expand...
Click to collapse
3.0.4-1 has proven to be the most stable so far.
I've also been using 3.1.0-1 for a while and haven't noticed any issues.
Avoid 3.1.0.0 though, as there has been many reports of issues with it.
Anova's Origin said:
3.0.4-1 has proven to be the most stable so far.
I've also been using 3.1.0-1 for a while and haven't noticed any issues.
Avoid 3.1.0.0 though, as there has been many reports of issues with it.
Click to expand...
Click to collapse
MY PHONE IS RUNNING AGAIN! thanks for your help man.
Btw! Seeing that the positions were somewhat corrupted, I actually had to use stock recovery to sideload the stock ROM then flash TWRP and finally on freedom is 2.6.1
Thanks again, mate. :highfive:
ddaharu said:
I was running Freedom OS CE 2.5 and I dirty flashed official OOS 4.1.0 and got into a bootloop.
I restarted the phone into twrp and it told me that it was read only so I wasn't seeing any zip files. I tried to use repair in the Wipe section by changing file format. I think I chose FAT...I honestly can't remember. But when I swipe to repair and I got stock on updating partition. So I restarted the device into twrp again but this time I'm stock on just the splash screen....won't start.
All I'm getting into is bootloader mode.
Help please
Click to expand...
Click to collapse
I faced a similar issue with twrp , just try to flash twrp again using fastboot mode , in case it does not work again then try to flash it a few more times , it would surely work , I have already tried it , but before that try to factory reset ur phone using twrp and reboot to twrp and only use the first method if the problem exists after that
9891ishu said:
I faced a similar issue with twrp , just try to flash twrp again using fastboot mode , in case it does not work again then try to flash it a few more times , it would surely work , I have already tried it , but before that try to factory reset ur phone using twrp and reboot to twrp and only use the first method if the problem exists after that
Click to expand...
Click to collapse
Thanks. I got through.
Im reading how to mod this Mi A2, I've modded a lot of Android Phones (till Samsung Galaxy S I..), but Im reading that this Xiaomi Mi A2 isnt too simply to mod, for example: unlock bl, flash recovery, flash rom/gapps/root/kernel/extra stuffs and reboot.
Im reading that this phone to get modded, require:
<!-- I have to be on stock Oreo?? --!>
unlock bl
flash unlock_critical
fastboot -w
fastboot set_active b
boot on twrp from fastboot
wipe all (format data, wipe system/data ecc..)
flash rom
flash twrp installer (so i can boot to recovery without pc)
switch your active slot, ie: to A if you are on B and to B if you were on A (reading on mi a2 forum, I assumed that this step must be done with computer using fastboot: 'fastboot set_active b OR a' - this is right?)
reboot recovery
flash Gapps
flash Magisk
reboot
Thanks to who want to help or fix my errors.. Im only asking if these steps are right!
Francesco0301 said:
<!-- I have to be on stock Oreo?? --!>
Click to expand...
Click to collapse
I unlocked mine in stock oreo, but I don't think you have to be in oreo to unlock bl. Some Custom ROMs, though, were only flashable in stock oreo (because pie vendor is unstable or something), but I think after 10.0.2 most of Custom ROMs was updated to be flashable over stock pie (the thread might be not updated, but you're actually able to, read few last pages or search around the thread of course just to make sure, it's ROM dependent).
Francesco0301 said:
unlock bl
flash unlock_critical
Click to expand...
Click to collapse
As for the unlocking steps --correct me if I'm wrong as it was from memory-- I think there are 3 unlock, OEM unlock, flashing unlock, and flashing_critical unlock.
Francesco0301 said:
fastboot -w
fastboot set_active b
boot on twrp from fastboot
wipe all (format data, wipe system/data ecc..)
Click to expand...
Click to collapse
If you fastboot -w, I don't think you need to wipe data again.
Francesco0301 said:
switch your active slot, ie: to A if you are on B and to B if you were on A (reading on mi a2 forum, I assumed that this step must be done with computer using fastboot: 'fastboot set_active b OR a' - this is right?)
Click to expand...
Click to collapse
You could do this in twrp in the "reboot" section. Select the slot, then reboot to recovery. You'll know what I mean when you boot TWRP, it's a new addition in TWRP compared to non-A/B-partition-device-thing you used to mod.
Francesco0301 said:
flash Gapps
flash Magisk
Click to expand...
Click to collapse
Keep in mind if you want to flash custom kernel, it is to be done before Magisk. Imagine having a boot.img from custom rom zip flashed to your system, that boot.img must be modified in this order: TWRP -> Custom Kernel -> Magisk. It will break each other if not in that order.
If you already flashed everything including magisk, using the device, THEN decided that you want a custom kernel, what you'd do is grab boot.img from custom rom zip, fastboot flash boot_a boot.img (if you flash rom on b, vice versa), then basically you repeat from fastboot set_active b then boot twrp yada yada until you flash magisk EXCEPT wipe, rom, and gapps. Do so so it's clean and with minimal issue. The order is important.
And for some Custom ROMs you need to flash custom kernel for it to boot, so keep an eye to the thread whether you need it or not. Or maybe telegram, as sometimes they haven't updated their thread but say something in telegram group. It's a good idea to join the group for news or to search around some information.
But yeah everything else is correct afaik. I hope what I say is clear and understandable enough. Happy modding!
Francesco0301 said:
fastboot set_active b
Click to expand...
Click to collapse
Pretty much everything is good but just make sure of your active parition and set the other so it might be fastboot set_active a (if you're active parition is b and vice versa) , but i was exactly like you but modding the mi a2 is not that hard just needs a bit more understanding
Hi, sorry for bad English.
I'm having trouble installing Custom ROMs on my Mi 8 Global. Any custom rom I install, after reboot on TWRP, the mobile does not start, it only stays on the fastboot screen or returns to the TWRP.
I already unlocked the bootloader, ADB ON, drivers installed on PC, TWRP OK, all neededs WIPEs ...
I can only install the STOCKs ROMs. I think the problem is when doing FLASH in the ROMs. It may be that I can only install ROM by Fastboot, but by Recovery not.
In the TWRP LOG, there is not a single error after installing the ROMs, always success.
I follow all the tutorials, but never start the system after installing by recovery.
Another thing I noticed is that when I install the custom rom, if I go in the TWRP file browser and go there in the SDCard folder, the files do not appear as it usually gets, such as the "Android" folder for example.
I've had several Androids since the Galaxy Y time and I've never had this problem.
Any idea?
format data "yes" then flash dm variety fix re oot recovery then flash any rom
Sent from my MI 8 using Tapatalk
altvolt74 said:
format data "yes" then flash dm variety fix re oot recovery then flash any rom
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
I followed all the tutorials, including the WIPEs
try another dm variety or recovery ........make sure is format data and not just wipe it and last ensure ur in pie firmware and not oreo
Sent from my MI 8 using Tapatalk
altvolt74 said:
try another dm variety or recovery ........make sure is format data and not just wipe it
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
Ill try this. Thanks!
null
I have the same problem as you, and my rom is only 10gb. Other roms can't recognize it. How do you solve this problem?
not
altvolt74 said:
try another dm variety or recovery ........make sure is format data and not just wipe it and last ensure ur in pie firmware and not oreo
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
i tried ,very bad,my phone still into fastboot.
Bruno Wagner said:
Hi, sorry for bad English.
I'm having trouble installing Custom ROMs on my Mi 8 Global. Any custom rom I install, after reboot on TWRP, the mobile does not start, it only stays on the fastboot screen or returns to the TWRP.
I already unlocked the bootloader, ADB ON, drivers installed on PC, TWRP OK, all neededs WIPEs ...
I can only install the STOCKs ROMs. I think the problem is when doing FLASH in the ROMs. It may be that I can only install ROM by Fastboot, but by Recovery not.
In the TWRP LOG, there is not a single error after installing the ROMs, always success.
I follow all the tutorials, but never start the system after installing by recovery.
Another thing I noticed is that when I install the custom rom, if I go in the TWRP file browser and go there in the SDCard folder, the files do not appear as it usually gets, such as the "Android" folder for example.
I've had several Androids since the Galaxy Y time and I've never had this problem.
Any idea?
Click to expand...
Click to collapse
1. wrong section
2. which twrp do you use, which firmware do you use...., what a rom do wanna flash
unlock bootloader , flash this Twrp
reboot to trwp, factory rest with "yes" reboot again to trwp flash the rom that u want
Bruno Wagner said:
I followed all the tutorials, including the WIPEs
Click to expand...
Click to collapse
Follow this step
1. Copy Miui rom 9.0.zip and which rom you want to sdcard.
2. Boot into twrp, then wipe data, cache.
3. Install Miui rom 9.0.zip (dont reboot after done)
4. In twrp, choose reboot twrp again, then then wipe data, cache
5. Install any custom rom you want. And flash disable dm-variety
6. Done and reboot
romano19 said:
Follow this step
1. Copy Miui rom 9.0.zip and which rom you want to sdcard.
2. Boot into twrp, then wipe data, cache.
3. Install Miui rom 9.0.zip (dont reboot after done)
4. In twrp, choose reboot twrp again, then then wipe data, cache
5. Install any custom rom you want. And flash disable dm-variety
6. Done and reboot
Click to expand...
Click to collapse
I ll try this. Thank u
You have to format data via typing "yes", it is not wiping data, it is button in twrp. After that everything gonna be ok.
maybe you should flash a miui based on android pie （globe developer version）
then use the latest twrp recovery （both wzsx and black pitch is ok）
Murik01 said:
You have to format data via typing "yes", it is not wiping data, it is button in twrp. After that everything gonna be ok.
Click to expand...
Click to collapse
Yes, I do. Dont work
Bruno Wagner said:
I ll try this. Thank u
Click to expand...
Click to collapse
Did you do something or you fix your problem?
NewbyCmUser said:
Did you do something or you fix your problem?
Click to expand...
Click to collapse
No, not a tip has solved the problem. Yesterday I spent all day trying different things, searching in several sites but nothing works. I'll have to settle for the ROM stock.
I had the same problem installing pixel experience you need to flash stock fastboot rom via miflash be careful, do not select the relock option, then install twrp, wipe system, caches and data and install your custom rom It worked for me.
Murik01 said:
You have to format data via typing "yes", it is not wiping data, it is button in twrp. After that everything gonna be ok.
Click to expand...
Click to collapse
i had same problem. and this format data has worked with "miui_MI8Global_8.12.20_c7a9af8587_9.0" i can flash it. phone working now but i will change rom tomorrow again.. i guess it will be brick in a couple days
Problem solved!
Sorry bad english, translated by Google Translate ...
Now I've been able to install custom ROMs. :laugh:
I tested Havok and Pixel Experience.
I'll speak the steps I did:
1 - Install the Stock Pie: MIUI Global Stable 10.1.2.0 (dipper_global_images_V10.1.2.0.PEAMIFI_20181211.0000.00_9.0_global_0099f5af5f)
Install with XiaomiMiFlash, at the bottom, check the option "Clean All".
NO INSTALL ON TWRP MODE.
2 - Start the system normal and make ADB ON
3 - Make Root
4 - Start the system normal again
5 - Install TWRP: recovery-TWRP-3.2.2-0711-XIAOMI8-CN-wzsx150 (use this version)
6 - WIPE > Advanced> System, Data, Cache
7 - Flash ROM: PixelExperience_dipper-9.0-20190111-2226-OFFICIAL
8 - Reboot System
9 - Ready!
10 - Optional Step (*recommended*) - Go again in TWRP and Wipe > System, Data, Cache, Internal Storage > Flash ROM > Reboot.
After this procedure I was able to install custom roms without problems.