-flash stock firmware with newflasher
-boot once. Install magisk manager app and patch stock boot image. (You can find it in Martinx3 stock recovery) than copy patched boot image to your computer.
-in fastboot:
* fastboot erase system
*fastboot flash userdata userdata.img
*fastboot flash system yoursystemfile.img
Optionally if you want to flash gapps
*fastboot flash boot twrp.img
*fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Flash gapps in twrp and than select install image and choose patched_boot.img and select boot partition
if not just do
*fastboot flash boot patched_boot.img
*fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
*reboot
(To install magisk you need to boot once and then do fastboot flash boot patched_boot.img again)
Twrp you can find here https://forum.xda-developers.com/xp...recovery-twrp-3-2-2-0-touch-recovery-t3821597
Userdata.img-https://drive.google.com/file/d/1Ni_lU5jY3oQ4GDbezJ83BOLKNbLvU4ue/view
How copy patched boot image on computer? Thanks!
Connect your phone to pc and just copy it like a normall file. You can find it in download folder.
alexsmel1 said:
How copy patched boot image on computer? Thanks!
Click to expand...
Click to collapse
lolnwl said:
Connect your phone to pc and just copy it like a normall file. You can find it in download folder.
Click to expand...
Click to collapse
PS C:\ADB> fastboot flash patched_boot.img
unknown partition 'patched_boot.img'
error: cannot determine image filename for 'patched_boot.img'
---------- Post added at 04:00 PM ---------- Previous post was at 03:59 PM ----------
alexsmel1 said:
How copy patched boot image on computer? Thanks!
Click to expand...
Click to collapse
lolnwl said:
Connect your phone to pc and just copy it like a normall file. You can find it in download folder.
Click to expand...
Click to collapse
PS C:\ADB> fastboot flash patched_boot.img
unknown partition 'patched_boot.img'
error: cannot determine image filename for 'patched_boot.img'
How do i fix this? Thank!
alexsmel1 said:
PS C:\ADB> fastboot flash patched_boot.img
unknown partition 'patched_boot.img'
error: cannot determine image filename for 'patched_boot.img'
---------- Post added at 04:00 PM ---------- Previous post was at 03:59 PM ----------
PS C:\ADB> fastboot flash patched_boot.img
unknown partition 'patched_boot.img'
error: cannot determine image filename for 'patched_boot.img'
How do i fix this? Thank!
Click to expand...
Click to collapse
It should be fastboot flash boot patched_boot.img.
lolnwl said:
Connect your phone to pc and just copy it like a normall file. You can find it in download folder.
Click to expand...
Click to collapse
Before the fastboot flash patched_boot.img command, I requested twrp of my stock firmware.
fastboot flash boot twrp-xz2.img
* fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
After that, it booted into recovery and installed the patched_boot.img and select boot partition.
After that, it was loaded into the system after the logo was loaded, it disappears and the black screen remains on, after that the reboot is permanent.
Help please solve the problem.
I took the boot.img file from the latest aosp firmware from MartinX3. Maybe I did something wrong?
alexsmel1 said:
Before the fastboot flash patched_boot.img command, I requested twrp of my stock firmware.
fastboot flash boot twrp-xz2.img
* fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
After that, it booted into recovery and installed the patched_boot.img and select boot partition.
After that, it was loaded into the system after the logo was loaded, it disappears and the black screen remains on, after that the reboot is permanent.
Help please solve the problem.
Click to expand...
Click to collapse
Do all the steps from the instructions and it will work
lolnwl said:
Do all the steps from the instructions and it will work
Click to expand...
Click to collapse
I took the boot.img file from the latest aosp firmware from MartinX3. Maybe I did something wrong?
---------- Post added at 04:22 PM ---------- Previous post was at 04:21 PM ----------
lolnwl said:
Do all the steps from the instructions and it will work
Click to expand...
Click to collapse
I took the boot.img file from the latest aosp firmware from MartinX3. Did I do this correctly or did I do something wrong?
---------- Post added at 04:22 PM ---------- Previous post was at 04:22 PM ----------
lolnwl said:
Do all the steps from the instructions and it will work
Click to expand...
Click to collapse
I took the boot.img file from the latest aosp firmware from MartinX3. Did I do this correctly or did I do something wrong?
---------- Post added at 04:22 PM ---------- Previous post was at 04:22 PM ----------
lolnwl said:
Do all the steps from the instructions and it will work
Click to expand...
Click to collapse
I took the boot.img file from the latest aosp firmware from MartinX3. Did I do this correctly or did I do something wrong?
alexsmel1 said:
I took the boot.img file from the latest aosp firmware from MartinX3. Maybe I did something wrong?
Click to expand...
Click to collapse
Get the boot.img from stock martinx3 recovery.
lolnwl said:
Get the boot.img from stock martinx3 recovery.
Click to expand...
Click to collapse
You will forgive me, but I don’t know where to boot.img file. I have firmware 52.0.A.3.84, in the stock_twrp_xz2_52.0.A.3.84 folder there are only such files twrp-xz2.img and vbmeta.img. I apologize for so many problems that have arisen because of me.
alexsmel1 said:
You will forgive me, but I don’t know where to boot.img file. I have firmware 52.0.A.3.84, in the stock_twrp_xz2_52.0.A.3.84 folder there are only such files twrp-xz2.img and vbmeta.img. I apologize for so many problems that have arisen because of me.
Click to expand...
Click to collapse
First of all you should update stock to the newest version to update all driver(52.0.A.3.202 is the newest with twrp support) and than unpack stock twrp and go to twrp-stock-installer and copy boot.img
lolnwl said:
First of all you should update stock to the newest version to update all driver(52.0.A.3.202 is the newest with twrp support) and than unpack stock twrp and go to twrp-stock-installer and copy boot.img
Click to expand...
Click to collapse
Thanks! Where you need to get userdata.img?
https://drive.google.com/file/d/1Ni_lU5jY3oQ4GDbezJ83BOLKNbLvU4ue/view?usp=sharing
lolnwl said:
https://drive.google.com/file/d/1Ni_lU5jY3oQ4GDbezJ83BOLKNbLvU4ue/view?usp=sharing
Click to expand...
Click to collapse
I really appreciate your work. I did everything according to the instructions:
fastboot erase system
fastboot flash userdata userdata.img
Fastboot flash system system.img (PixelExperienceP-arm-aonly)
fastboot flash boot patched_boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
After that, my phone goes into reboot after the appearance of the logo. I do not know what to do. Sorry for the problems that I delivered. Help please fix it.
alexsmel1 said:
I really appreciate your work. I did everything according to the instructions:
fastboot erase system
fastboot flash userdata userdata.img
Fastboot flash system system.img (PixelExperienceP-arm-aonly)
fastboot flash boot patched_boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
After that, my phone goes into reboot after the appearance of the logo. I do not know what to do. Sorry for the problems that I delivered. Help please fix it.
Click to expand...
Click to collapse
Our device is ab partition!!! A only gsi will not boot! Download ab version and give it a try
lolnwl said:
Our device is ab partition!!! A only gsi will not boot! Download ab version and give it a try
Click to expand...
Click to collapse
Thank you very much my friend !!!!!!!!!!! Thanks to you, I managed to do it finally. I am very happy for your help !!!!!!!!! Thank!!!!: о: о: о
alexsmel1 said:
Thank you very much my friend !!!!!!!!!!! Thanks to you, I managed to do it finally. I am very happy for your help !!!!!!!!! Thank!!!!: о: о: о
Click to expand...
Click to collapse
no problem
Nice that you want to give us a gsi guide.
And now my critics :silly:
Code:
1. You don't need to erase the system.
Flashing a partition does it too.
And we may have the erase bug in the bootloader, where executing the erase command on its own may take more than only 1 second.
Code:
2. You can flash the system.img in the twrp.
And of course wipe the userdata, too (userdata and internal storage due to encryption).
Code:
3. A styled guide with the XDA forum bbcode would be nice. :)
MartinX3 said:
Nice that you want to give us a gsi guide.
And now my critics :silly:
Code:
1. You don't need to erase the system.
Flashing a partition does it too.
And we may have the erase bug in the bootloader, where executing the erase command on its own may take more than only 1 second.
Code:
2. You can flash the system.img in the twrp.
And of course wipe the userdata, too (userdata and internal storage due to encryption).
Code:
3. A styled guide with the XDA forum bbcode would be nice. :)
Click to expand...
Click to collapse
Thanks for your reply. Its my first guide so it may not be the best.
I tried to flash system.img from twrp but after that flashlight did not work so I chosed fastboot for flashing
lolnwl said:
Thanks for your reply. Its my first guide so it may not be the best.
I tried to flash system.img from twrp but after that flashlight did not work so I chosed fastboot for flashing
Click to expand...
Click to collapse
Then the flash light start working?
Technically twrp should do the same
Related
When i try to flash my factory image 5.0.1 on my nexus 5 (i got twrp recovery and DU rom) i got the message you will see in the picture... What shall i do? Thanks in advance.
Post a screenshot of your folder structure where the fastboot.exe and flash-all.bat are located. I guess you forgot to copy over the zip archive which contains the system.img / cache.img / userdata.img and so on.
experience7 said:
Post a screenshot of your folder structure where the fastboot.exe and flash-all.bat are located. I guess you forgot to copy over the zip archive which contains the system.img / cache.img / userdata.img and so on.
Click to expand...
Click to collapse
ok
Does the image-hammerhead zip file contain system.img file? If not you maybe got a corrupted download and have to d/l the factory image again...
experience7 said:
Does the image-hammerhead zip file contain system.img file? If not you maybe got a corrupted download and have to d/l the factory image again...
Click to expand...
Click to collapse
Yeah it does!..
Okay then try this:
1) Erase all partitions manually like this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
2) Then extract the content of the zip file and flash each img file manually like this:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
Bootloader and radio don't have to be flashed because they have - as I can see in your screenshot - successfully been flashed with the flash-all.bat.
experience7 said:
Okay then try this:
1) Erase all partitions manually like this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
2) Then extract the content of the zip file and flash each img file manually like this:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
Bootloader and radio don't have to be flashed because they have - as I can see in your screenshot - successfully been flashed with the flash-all.bat.
Click to expand...
Click to collapse
Does it need something like "fastboot reboot bootloader" after every command?
experience7 said:
Okay then try this:
1) Erase all partitions manually like this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
2) Then extract the content of the zip file and flash each img file manually like this:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
Bootloader and radio don't have to be flashed because they have - as I can see in your screenshot - successfully been flashed with the flash-all.bat.
Click to expand...
Click to collapse
i went to fastboot flash boot boot.img and im stuck on google logo
GiwrgosP- said:
Does it need something like "fastboot reboot bootloader" after every command?
Click to expand...
Click to collapse
Use this tutorial its helped me in past hope it will help you also>http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 Thanks to> @abaaaabbbb63
Mobile Solutions said:
Use this tutorial its helped me in past hope it will help you also>http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 Thanks to> @abaaaabbbb63
Click to expand...
Click to collapse
Thats what i did...
GiwrgosP- said:
Thats what i did...
Click to expand...
Click to collapse
Please explain what you did here? use 2nd method
What you did:
fastboot reboot bootloader
That's wrong. It's
fastboot reboot-bootloader
You only flashed stock kernel which is not compatible with DU ROM hence the bootloop.
Never mind. Just turn it off by holding power button. As soon as the screen is off also press vol down to boot in fastboot mode again.
Flash all the partitions like I said without reboot. After you've flashed all partitions type
fastboot reboot-bootloader
experience7 said:
What you did:
fastboot reboot bootloader
That's wrong. It's
fastboot reboot-bootloader
You only flashed stock kernel which is not compatible with DU ROM hence the bootloop.
Never mind. Just turn it off by holding power button. As soon as the screen is off also press vol down to boot in fastboot mode again.
Flash all the partitions like I said without reboot. After you've flashed all partitions type
fastboot reboot-bootloader
Click to expand...
Click to collapse
Thanks doing it right now, hope it works. I will post soon
GiwrgosP- said:
Thanks doing it right now, hope it works. I will post soon
Click to expand...
Click to collapse
Thank you soooooooo much you helped a lot THANKS
No problem mate Don't hesitate to use the forums thanks button if a post was valuable and helpful
experience7 said:
No problem mate Don't hesitate to use the forums thanks button if a post was valuable and helpful
Click to expand...
Click to collapse
I have already done this
So many people are finding the correct way to lock bootloader so i created this thread.Just firstly be sure that you have downloaded the correct stock rom/firmware for your device otherwise you will be complaining for no wifi and network issue.Just follow this steps and you will successfully relock your bootloader.If any issues just reply i will help.I used fasboot so you can just replace it by mfastboot if you use mfast.Your warranty is still void after relocking,now its your luck if the service center guys check it or not!
1.Download the stock rom/firmware of your device.
2.Extract it and paste its contents in the adb folder.
3.Make sure that usb debugging is on.
4.Now in the adb folder shift+right click and then in the pop click open command window here.
5.Type in the cmd [adb reboot bootloader],you can do this manually also by power down first then power button+volume down.
6.Type [fastboot oem lock begin] it would then say flash stock images etc.
7.Then enter this commands and make sure you get okay after each command or you can just run the bat file uploaded(do put it in the adb folder)
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem lock
fastboot reboot
8.Now your device will reboot with no bootloader unlock warning.
see this
i followed ur method but :crying::crying::crying:
samiran das 03 said:
i followed ur method but :crying::crying::crying:
Click to expand...
Click to collapse
If You Use XT1643 So Check This = http://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695
samiran das 03 said:
i followed ur method but :crying::crying::crying:
Click to expand...
Click to collapse
The problem with you is that you have flashed the old version of rom.Download the latest version of your phone rom.This error is caused when for eg. You currently have a rom version 2.0 ,and then try to flash rom 1.0.The bootloader gives an error.So you have to flash version 2.0.And the error imaged.not signed or corrupt is normal.
anhoxhrs said:
The problem with you is that you have flashed the old version of rom.Download the latest version of your phone rom.This error is caused when for eg. You currently have a rom version 2.0 ,and then try to flash rom 1.0.The bootloader gives an error.So you have to flash version 2.0.And the error imaged.not signed or corrupt is normal.
Click to expand...
Click to collapse
so what should i do now
plzz post the latest firmware
samiran das 03 said:
so what should i do now
plzz post the latest firmware
Click to expand...
Click to collapse
Send me screen shot of about phone
Plzz Check
Anything more u want???
samiran das 03 said:
Anything more u want???
Click to expand...
Click to collapse
Flash this https://drive.google.com/file/d/0B1N6dGU7FEXsSjR3QUtsRU1RTVk/viewAnd lock the bootloader with steps on the 1 post.
I tried using this firmware but its giving me same error.others are telling that the firmware which i am flasshing is old one.
But @swarupgolui told me to flash the lastest firmware
See this below
So what to do now?
samiran das 03 said:
So what to do now?
Click to expand...
Click to collapse
Whats Your Problem With lastest firmware?
swarupgolui said:
Whats Your Problem With lastest firmware?
Click to expand...
Click to collapse
Not done yet
I will do it tomorrow
samiran das 03 said:
So what to do now?
Click to expand...
Click to collapse
You tried the firmware in the link i gave?
anhoxhrs said:
You tried the firmware in the link i gave?
Click to expand...
Click to collapse
But in that my device is not mentioned
samiran das 03 said:
But in that my device is not mentioned
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B1N6dGU7FEXsSjR3QUtsRU1RTVk/view Just download this on chrome on your pc and flash.
Sure it will work na
---------- Post added at 05:20 PM ---------- Previous post was at 05:06 PM ----------
Mine is xt1643
samiran das 03 said:
Sure it will work na
---------- Post added at 05:20 PM ---------- Previous post was at 05:06 PM ----------
Mine is xt1643
Click to expand...
Click to collapse
It worked on mine i have same xt1643 32 gb
First I unlocked the bootloader, and then I tried to use chainfire's root method by flashing the boot-to-root-img through fastboot. The phone will no longer boot to system and I cant seem to get google's factory image to install via fastboot. The flash-all would only flash the bootloader and radio, but would fail after that. I also cannot manually flash the stock system.img file. I get an error that reads " remote: data too large ". Not sure how to get out of this so any help would be GREATLY appreciated.
Did you manually flash the boot and system.img to each slot?
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Fastboot flash system_a system.img
fastboot flash system_b system_other.img
Use these commands assuming your boot slot is slot_a...if your boot slot is slot_b then use
Fastboot flash system_a system_other.img
fastboot flash system_b system.img
Hope this helps!!!
You need to update your fastboot version....then the system file will flash for you. Only the newest supports large files.
Sent from my Pixel using Tapatalk
maulich said:
You need to update your fastboot version....then the system file will flash for you. Only the newest supports large files.
Click to expand...
Click to collapse
Good call...totally forgot about that man
BakedTator said:
Good call...totally forgot about that man
Click to expand...
Click to collapse
Thanks to both of you! I actually did get my phone to boot up just before you replied by flashing to boot.img to both slots. Just installed TWRP and flashed superSU after that to get root. All is well now!
removed
Does it boot for now?
Thank you, port miui
---------- Post added at 03:06 PM ---------- Previous post was at 02:28 PM ----------
Screenshot
so what? working?
Teonx said:
so what? working?
Click to expand...
Click to collapse
As the op said, the developer wants testers, so if you are interested test it and report.
akash_eric said:
Using ADB tool
Download the archive with the firmware
Extract It
Open Command Window in ADB tool
fastboot format system
fastboot format cache
fastboot format userdata
fastboot flash boot boot.Img
fastboot flash system system.img
Boot into the system
Click to expand...
Click to collapse
I think these teams will not work for Mi A1.
We need
fastboot flash boot_a boot.img or boot_b
fastboot flash system_a system.img or system_b
etc.
Danger: It will cause your machine to hang the logo, please do not install
PjLyTam said:
Danger: It will cause your machine to hang the logo, please do not install
Click to expand...
Click to collapse
you tried with twrp?
and can u give dmesg plz
Absolute
*******
[8.1.0] OPM1.171019.019.V9.6.2.0.ODHMIFE The
beta version of the official stable firmware Android 8.1.0 from June 13.
Self-made images for fastboot and TWRP.
Fastboot: Unzip the
image. In the same folder, unzip the utilities from the header. Flash one of the batch files:
flash_all.bat - for firmware with saving all the data .
flash_all_clean.bat - for the firmware to be clean (with the removal of all data).
Please note - the bootloader must be previously unlocked!
Both slots are stitched. Warning "Invalid sparse file format at header magic" ignore and wait for the process to finish.
TWRP:
Temporarily load TWRP. To flash an image.
The data is not erased.
Download:
Fastboot: https://drive.google.com/file/d/1KgpEBmFVgP6tkTa6eYq0baI_kCSCPQjK/view?usp=drivesdk
TWRP:https://drive.google.com/file/d/1wIFNV3tpwgLr0UPabK18BkWT8N6oVT5Z/view?usp=drivesdk
[/HIDE]
Please check if 5Ghz WiFi band working or not.
arkadeep2008 said:
Please check if 5Ghz WiFi band working or not.
Click to expand...
Click to collapse
Working bro
Do you keep OTA afterinstalling this?
5ghz is working but no downloading.... Connection is fine ...
Orig. Mac
Germany no volte...
No sd card fixxed (0byte)...
What has xiaomi fixxed ??
yasars said:
5ghz is working but no downloading.... Connection is fine ...
Orig. Mac
Germany no volte...
No sd card fixxed (0byte)...
What has xiaomi fixxed ??
Click to expand...
Click to collapse
I also checked. All previous bugs fixed now like sd card, volte, camera, recording,. 5ghz.
All r working fine as of now.
nestorojeda said:
Do you keep OTA afterinstalling this?
Click to expand...
Click to collapse
Because this is a leak (captured from mi sever) ota. Soo ota will not come. But we can use this. For daily use,. Witht prob if ota come. We need to flash via mi tool. Via choosing save data option
yasars said:
5ghz is working but no downloading.... Connection is fine ...
Orig. Mac
Germany no volte...
No sd card fixxed (0byte)...
What has xiaomi fixxed ??
Click to expand...
Click to collapse
Sd fix check this
Is Magisk and Root working properly on this Rom. ?
Thanks in advance
I am on 9.5.10 April Build, can I flash this beta w/o loosing data??
what is tools folder?
Correct me if I am wrong
1) download the zip
2) extract the zip.
3) flash flash_A.bat or flash_B.bat using mi flash tool.
[email protected] said:
what is tools folder?
Correct me if I am wrong
1) download the zip
2) extract the zip.
3) flash flash_A.bat or flash_B.bat using mi flash tool.
Click to expand...
Click to collapse
what is tools folder Means extract the zip. in adb minimal fastboot folder after then use flash flash_A.bat by just clicking
oe u can flash via manully by these commands
flash via manully commands..
fastboot oem unlock
fastboot flash modem_a modem.img
fastboot flash sbl1 sbl1.img
fastboot flash rpm rpm.img
fastboot flash tz tz.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash aboot aboot.img
fastboot flash boot_a boot.img
fastboot flash system_a system.img
fastboot flash lksecapp lksecapp.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash keymaster keymaster.img
fastboot set_active a
fastboot oem lock
fastboot reboot
arkadeep2008 said:
I am on 9.5.10 April Build, can I flash this beta w/o loosing data??
Click to expand...
Click to collapse
u need to wipe /data, but doesnt need to wipe your internal storage, i tried before without wiping anything and got bootlooped but after wiping /data via TWRP i got it booting
---
it seems file provided here is not TWRP version, mybad, u can find TWRP version in somewhere in the forum
vikashyadav said:
flash via manully commands..
fastboot oem unlock
fastboot flash modem_a modem.img
fastboot flash sbl1 sbl1.img
fastboot flash rpm rpm.img
fastboot flash tz tz.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash aboot aboot.img
fastboot flash boot_a boot.img
fastboot flash system_a system.img
fastboot flash lksecapp lksecapp.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash keymaster keymaster.img
fastboot set_active a
fastboot oem lock
fastboot reboot
Click to expand...
Click to collapse
Then i can flash this build with miflash and lock the bootloader?thank you
ruperxl89 said:
Then i can flash this build with miflash and lock the bootloader?thank you
Click to expand...
Click to collapse
Via mi tool that need some other files too. .
Soo i personally. Suggest u to. Flash
Via my given method. ,. Too easy then other methods
Or.yes bootloader. U can lock it. In that rom
vikashyadav said:
Via mi tool that need some other files too. .
Soo i personally. Suggest u to. Flash
Via my given method. ,. Too easy then other methods
Or.yes bootloader. U can lock it. In that rom
Click to expand...
Click to collapse
thank you, i will flash by fastboot and i will close the bootloader
---------- Post added at 09:47 AM ---------- Previous post was at 09:22 AM ----------
vikashyadav said:
Via mi tool that need some other files too. .
Soo i personally. Suggest u to. Flash
Via my given method. ,. Too easy then other methods
Or.yes bootloader. U can lock it. In that rom
Click to expand...
Click to collapse
Is it necessary to come from the latest version of rom stock to be able to flash this beta? I have done the manual process and it has stopped me in the bootloader, it does not start.
ruperxl89 said:
thank you, i will flash by fastboot and i will close the bootloader
---------- Post added at 09:47 AM ---------- Previous post was at 09:22 AM ----------
Is it necessary to come from the latest version of rom stock to be able to flash this beta? I have done the manual process and it has stopped me in the bootloader, it does not start.
Click to expand...
Click to collapse
Which version. R u u using now
Help
I am on stock 8.0 April build and I need to install this build. What steps do I need to follow to get the build up and running. I am a newbie so please detail me all the steps.
theUchihaBrat said:
I am on stock 8.0 April build and I need to install this build. What steps do I need to follow to get the build up and running. I am a newbie so please detail me all the steps.
Click to expand...
Click to collapse
Just follow all instructions that i mentioned. In thia thread.