Related
Modified boot.img of a rom is required to be flashed on that rom so that it works with TWRP.
Enabling ADB during first boot creates a way out in case your phone bootloops or stuck at MI logo and also hardbricked.
Many people hardbricked their phone while flashing MIUI based roms through TWRP, and they had to test-point to bring their phone back to life, my mod enables adb during boot and so people who used my mod and hardbricked their phone can access adb when their phone is stuck at MI logo or bootlooping and thus revive their phone.
Tools needed:-
1)Notepad++ (google it and download)
2)Android Image Kitchen(AIK) http://forum.xda-developers.com/attachment.php?attachmentid=3638835&d=1454959265
Steps:-
1)Download the required rom and extract its boot.img
2)Copy the boot.img to AIK folder and drag boot.img and drop it on unpackimg.bat
3)Open ramdisk folder and look for default.prop , open them with Notepad++
4)Editing default.prop Note:- This will enable adb at first boot
5)Change
Code:
ro.secure=1 to ro.secure=0
ro.adb.secure=1 to ro.adb.secure=0
ro.debuggable=0 to ro.debuggable=1
persist.sys.usb.config=none to persist.sys.usb.config=adb
delete the line ro.secureboot.devicelock=1 if present
OR (Alternate way)(recommended)
open ramdisk and look for fstab.qcom, open with notepad++ and search for ",verify" (without quotes) and delete it and save.
6)Now execute repackimg.bat, a image-new.img file will be compiled.
7)Flash the image-new.img through TWRP or through fastboot using "Fastboot flash boot image-new.img"
That's all
P.S:- Remember only use Boot.img specific for the miui version you wanna run, boot.img version not matching with MIUI version
will cause the Wifi to stop working.
Press thanks If this helped.:good:
Any queries feel free to ask me.:laugh:
Does the modified boot.img procedure need to be done for every ROM or just for the MIUI ROMs? I want to install the AOSP ROM and later CM 13 but I'm still not sure about the whole flashing process.
Sent from my Redmi Note 3 using XDA-Developers mobile app
SkinCoffin said:
Does the modified boot.img procedure need to be done for every ROM or just for the MIUI ROMs? I want to install the AOSP ROM and later CM 13 but I'm still not sure about the whole flashing process.
Sent from my Redmi Note 3 using XDA-Developers mobile app
Click to expand...
Click to collapse
modified boot.img is only for official MIUI roms, all other roms doesnt need it
Rajdip said:
modified boot.img is only for official MIUI roms, all other roms doesnt need it
Click to expand...
Click to collapse
So if I'm on Miui Official Global ROM 7.2.3 all I have to do is flash TWRP through fastboot, boot into it and flash the new ROM+GApps through it?
SkinCoffin said:
So if I'm on Miui Official Global ROM 7.2.3 all I have to do is flash TWRP through fastboot, boot into it and flash the new ROM+GApps through it?
Click to expand...
Click to collapse
exactly
Rajdip said:
exactly
Click to expand...
Click to collapse
Thank you! I just did it. It has booted and almost over in the "Optimizing apps" window. Thing is, I did forget to wipe system, data and cache before flashing, should I do it again or will it be fine like this?
EDIT: I rebooted the phone into recovery, wiped system, data and cache, flashed the ROM zip and wiped cache and dalvik cache. I booted the phone and it showed the Mi logo, then 4 circles screen flying around (green, red, blue and yellow) and it has been like this for like 5 min now.. Did I do something wrong? I'm starting to worry to be honest.
SkinCoffin said:
Thank you! I just did it. It has booted and almost over in the "Optimizing apps" window. Thing is, I did forget to wipe system, data and cache before flashing, should I do it again or will it be fine like this?
EDIT: I rebooted the phone into recovery, wiped system, data and cache, flashed the ROM zip and wiped cache and dalvik cache. I booted the phone and it showed the Mi logo, then 4 circles screen flying around (green, red, blue and yellow) and it has been like this for like 5 min now.. Did I do something wrong? I'm starting to worry to be honest.
Click to expand...
Click to collapse
it takes time to boot for the first time, did it boot now?
Rajdip said:
it takes time to boot for the first time, did it boot now?
Click to expand...
Click to collapse
Still hasn't booted. It has been on the flying circles screen for around 10 minutes now. Maybe fastboot twrp again and do the process all over again?
SkinCoffin said:
Still hasn't booted. It has been on the flying circles screen for around 10 minutes now. Maybe fastboot twrp again and do the process all over again?
Click to expand...
Click to collapse
Try again, goto TWRP, wipe system,data,cache,dalvik and flash the rom. Now reboot...
Rajdip said:
Try again, goto TWRP, wipe system,data,cache,dalvik and flash the rom. Now reboot...
Click to expand...
Click to collapse
So I shouldn't reinstall TWRP through fastboot?
EDIT: Ok so I restarted the phone and it booted normally into the ROM, everything seems alright. Will check if I have any problem, if I do I'll just reflash it.
SkinCoffin said:
So I shouldn't reinstall TWRP through fastboot?
Click to expand...
Click to collapse
No, first try what I said, dont wipe cache and dalvik after the rom is flashed
Rajdip said:
No, first try what I said, dont wipe cache and dalvik after the rom is flashed
Click to expand...
Click to collapse
Ok so I restarted the phone and it booted normally into the ROM, everything seems alright. Will check if I have any problem, if I do I'll just reflash it.
SkinCoffin said:
Ok so I restarted the phone and it booted normally into the ROM, everything seems alright. Will check if I have any problem, if I do I'll just reflash it.
Click to expand...
Click to collapse
okay
i do exactly like your tutor...i edit boot.img n delete ",verify"
repack than delete original boot.img, than use moded boot.img... but wifi doesn't work...
where my mistake...?
Mayoz said:
i do exactly like your tutor...i edit boot.img n delete ",verify"
repack than delete original boot.img, than use moded boot.img... but wifi doesn't work...
where my mistake...?
Click to expand...
Click to collapse
are you sure you are using the boot.img of the MIUI version you are flashing? there is two 7.2.3.0 version of boot.img one for global and one for china. Anyway try this and see if wifi works, goto TWRP(I hope you've already deleted the emmc_appsboot file), select mount and then tick on mount system as read only. Then flash the rom. This method will replace TWRP with MIUI recovery but your wifi should start working.
Rajdip said:
are you sure you are using the boot.img of the MIUI version you are flashing? there is two 7.2.3.0 version of boot.img one for global and one for china. Anyway try this and see if wifi works, goto TWRP(I hope you've already deleted the emmc_appsboot file), select mount and then tick on mount system as read only. Then flash the rom. This method will replace TWRP with MIUI recovery but your wifi should start working.
Click to expand...
Click to collapse
yes using the boot.img of the MIUI version to flashing...from recovery rom stable 7.2.3.0 china....maybe my mistake i replace emmc_appsboot file from miui forum...not delete "will replace TWRP with MIUI recovery...' still can booting? i already UBL...
Mayoz said:
yes using the boot.img of the MIUI version to flashing...from recovery rom stable 7.2.3.0 china....maybe my mistake i replace emmc_appsboot file from miui forum...not delete "will replace TWRP with MIUI recovery...' still can booting? i already UBL...
Click to expand...
Click to collapse
I didnt get you, can you be more clear?
Do I need to use Windows 64bits to flash TWRP?
Thanks.
pepemonje said:
Do I need to use Windows 64bits to flash TWRP?
Thanks.
Click to expand...
Click to collapse
no need 32bit works
Hello, I've followed a certain tutorial and flashed a fastboot Rom with modified emmc file in attempt to unlock bootloader by force because, even after two weeks of trying, I can't get a confirmation SMS from xiaomi to confirm sending an unlock request. After doing it and flashing TWRP onto my device, I'm still unable to enter recovery. Just shows a picture of device and a disconnected usb cable. I need to flash SuperSU in order to get root access.
Because this device is getting me really confused, please answer a couple of questions for me.
If I flash a recently uploaded global stable ROM 7.2.3.0. and flash TWRP with a modified boot image from this tutorial, will I finally be able to enter recovery and install SuperSU?
Flashing will probably relock my bootloader. Is it possible for me to finally enter TWRP and flash SuperSU after flashing the new boot image?
I've thought that I could enter TWRP just by unlocking the bootloader but it seems that I've missed something. I can't remember last time a phone got me this confused.
My only goal here is being able to enter TWRP and rooting my phone, I gave up on unlocking the bootloader officially because I can't ever get that confirmation SMS.
I appreciate the help!! :fingers-crossed:
Trying to flash a custom ROM, actually, when flashing pretty much all ROMS with 3.0.2, I get the following error: "mount: Failed to mount /dev/block/mmcblk0p39 at /cust: Device or resource busy" I believed this didn't pose a problem, since all ROMs had flashed fine, or so I thought, until I tried to flash one of HTCMania's customs and it had to change the system font, but didn't. Any ideas as to why this may be happening? Or how can this be fixed?
KillerDam said:
Trying to flash a custom ROM, actually, when flashing pretty much all ROMS with 3.0.2, I get the following error: "Failed to mount /dev/block/mmcblk0p39 at /cust: Device or resource busy" I believed this didn't pose a problem, since all ROMs had flashed fine, or so I thought, until I tried to flash one of HTCMania's customs and it had to change the system font, but didn't. Any ideas as to why this may be happening? Or how can this be fixed?
Click to expand...
Click to collapse
i have same problem in twrp,but with data,i have fix that by flash stock recovery,from stock recovery i have made wipe data factory reset and wipe cache and he work,it might work for you,so give a try
cristi.blidariu said:
i have same problem in twrp,but with data,i have fix that by flash stock recovery,from stock recovery i have made wipe data factory reset and wipe cache and he work,it might work for you,so give a try
Click to expand...
Click to collapse
How did you flash the stock recovery?
KillerDam said:
How did you flash the stock recovery?
Click to expand...
Click to collapse
By fastboot,and command is fastboot flash recovery recovery.img
cristi.blidariu said:
By fastboot,and command is fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Nope, didn't work, still can't mount cust partition, even after factory reset using stock recovery. I can only think about pushing the rom through sideload, but can't seem to figure out how. I'm about to give up and just return to Lollipop
KillerDam said:
Nope, didn't work, still can't mount cust partition, even after factory reset using stock recovery. I can only think about pushing the rom through sideload, but can't seem to figure out how. I'm about to give up and just return to Lollipop
Click to expand...
Click to collapse
Did you try to flash files via fastboot,or you try to restore your backup via twrp?
cristi.blidariu said:
i have same problem in twrp,but with data,i have fix that by flash stock recovery,from stock recovery i have made wipe data factory reset and wipe cache and he work,it might work for you,so give a try
Click to expand...
Click to collapse
cristi.blidariu said:
Did you try to flash files via fastboot,or you try to restore your backup via twrp?
Click to expand...
Click to collapse
Was trying to flash a ROM via TWRP, ROM flashes, but not correctly, since system font and other assorted things remain unchanged, and they should change.
KillerDam said:
Was trying to flash a ROM via TWRP, ROM flashes, but not correctly, since system font and other assorted things remain unchanged, and they should change.
Click to expand...
Click to collapse
K,wich rom?
cristi.blidariu said:
K,wich rom?
Click to expand...
Click to collapse
I have the same problem while trying to install sokkoban's rom from huaweip8lite blogspot.
After the error message extracting system hangs. After forced restart twrp recovery cannot boot again. Had to debrick my phone. :\
aelfwine88 said:
I have the same problem while trying to install sokkoban's rom from huaweip8lite blogspot.
After the error message extracting system hangs. After forced restart twrp recovery cannot boot again. Had to debrick my phone. :\
Click to expand...
Click to collapse
Edit:
I think this is caused by the install script doesn't unmount /cust mountpoint before trying to access it.
aelfwine88 said:
Edit:
I think this is caused by the install script doesn't unmount /cust mountpoint before trying to access it.
Click to expand...
Click to collapse
Do you have any idea how can it be fixed? Maybe which line could be missing or wrong and what would the correct syntax be.
cristi.blidariu said:
K,wich rom?
Click to expand...
Click to collapse
Nautilus ROM, and maybe Sokkoban's KangVIP iirc
KillerDam said:
Nautilus ROM, and maybe Sokkoban's KangVIP iirc
Click to expand...
Click to collapse
sorry for late answer,Nautilus rom is base on hw/eu location with build number C432B564,you need to flash location https://mega.nz/#!aB9kUDST!q_mT6cq9uEQjvscnbXBZq3B1X6BWsMk7iYKaDjfFzJU flash with twrp,then try to install Nautilus rom,for @sokkoban KangVIP you need chinese location,well i don't have that location you should search your self
KillerDam said:
Do you have any idea how can it be fixed? Maybe which line could be missing or wrong and what would the correct syntax be.
Click to expand...
Click to collapse
I think you need to unmount /cust before you start to work with it. I checked the original Chinese rom which was it converted from and those guys are unmounting all mountpoins in the beginning of the install script (META-INF\com\google\android\updater-script):
Code:
ifelse(is_mounted("/data"), unmount("/data"));
ifelse(is_mounted("/system"), unmount("/system"));
ifelse(is_mounted("/cust"), unmount("/cust"));
This goes before the "ui_print("Formatting cust...");" line.
Sokkoban doesn't do it in his script so I thing that should be the problem.
I just switched my location to cn the other day and tried to install the new KangVIP B569. It went well, but i couldn't figure out how to install gapps (and I needed my phone live again...) so I switched back sokoban's modded KangVIP B564 version which has the same error during install. But it didn't stucked this time at extracting system and I guess it flashed /cust fine as well. And that was at 3am and I did not have the spirit to try to fix the script and flash again... Anyway you can try the code above but I suggest to switch location to cn and go for the latest KangVIP B569 or sokoban's KangVIP B564 (and you can try the script fix before flash). If you go with KangVIP B569 and you can figure out how to install gapps to please share.
If you stuck with location switching or don't know how to get official cn 6.0 android (also requirement for the modded 6.0) drop me a message and I try to recollect how I done that.
Good luck.
I have rooted stock firmware installed in my Asus Zenfone 2 laser with bootloader unlocked.
Model : ZE550KL(Z00LD)
Kernel Version : 3.10.49-gf41b7aa
I have tried to install custom ROMs ( XenonHD , Lineageos and CosmicOS) but everytime phone stucks in boot just showing the logo. and I have waited for around 30mins.:crying:
How to install custom rom then? why is the phone always getting stuck there? Please help.
And I follow the following steps to install any custom rom:
1) Boot into TWRP Recovery.
2) Wipe dalvik, cache, system and data.
3) Install Rom.
4) Install Gapps.
5) Reboot.
Is your TWRP the permanent one? Or you'd have to flash it via fastboot evetytime?
eiPeiDweP said:
Is your TWRP the permanent one? Or you'd have to flash it via fastboot evetytime?
Click to expand...
Click to collapse
I have permanent TWRP 3.1 flashed.
I'm facing the same problem ?
Krishna_MDual said:
I have rooted stock firmware installed in my Asus Zenfone 2 laser with bootloader unlocked.
Model : ZE550KL(Z00LD)
Kernel Version : 3.10.49-gf41b7aa
I have tried to install custom ROMs ( XenonHD , Lineageos and CosmicOS) but everytime phone stucks in boot just showing the logo. and I have waited for around 30mins.:crying:
How to install custom rom then? why is the phone always getting stuck there? Please help.
And I follow the following steps to install any custom rom:
1) Boot into TWRP Recovery.
2) Wipe dalvik, cache, system and data.
3) Install Rom.
4) Install Gapps.
5) Reboot.
Click to expand...
Click to collapse
What error do you get ? And on what android version are you?
Lazynestor said:
What error do you get ? And on what android version are you?
Click to expand...
Click to collapse
There is no error but the Boot logo is just stuck, I wait for around 30mins then i stop.
I am on Android 6.0.1
Krishna_MDual said:
There is no error but the Boot logo is just stuck, I wait for around 30mins then i stop.
I am on Android 6.0.1
Click to expand...
Click to collapse
So the zip flashes successful?
Lazynestor said:
So the zip flashes successful?
Click to expand...
Click to collapse
Yes zip are flashed successfully.
I get one error "unable to Mount /asdf" though evetytime I flash anything from TWRP. But i ignore that error.
Krishna_MDual said:
Yes zip are flashed successfully.
I get one error "unable to Mount /asdf" though evetytime I flash anything from TWRP. But i ignore that error.
Click to expand...
Click to collapse
Wipe asdf and do a clean install
Hit the like button if I helped
Lazynestor said:
Wipe asdf and do a clean install
Hit the like button if I helped
Click to expand...
Click to collapse
I am not able to wipe /asdf. That's itself is another problem. I get the same error unable to Mount /asdf partition.
Krishna_MDual said:
I am not able to wipe /asdf. That's itself is another problem. I get the same error unable to Mount /asdf partition.
Click to expand...
Click to collapse
Did you try to mount it and then wipe?
Lazynestor said:
Did you try to mount it and then wipe?
Click to expand...
Click to collapse
I am not sure? How to wipe, tell me the steps please.
Krishna_MDual said:
I am not sure? How to wipe, tell me the steps please.
Click to expand...
Click to collapse
Its all there in twrp .
Lazynestor said:
Its all there in twrp .
Click to expand...
Click to collapse
Okay I will check.
EDIT : I checked and wiped the /asdf patition in TWRP and then reinstalled the custom ROM.
Now its working.
Thank you .. :laugh:
Facing the same problem.
I'm getting an error in twrp
Failed to mount factory
Don't know how to fix it.
foysal04 said:
Facing the same problem.
I'm getting an error in twrp
Failed to mount factory
Don't know how to fix it.
Click to expand...
Click to collapse
Explore the settings, make use of yourself
There's a option there find it..
Lazynestor said:
Explore the settings, make use of yourself
There's a option there find it..
Click to expand...
Click to collapse
I tried my best but I couldn't fix this error.
Can you please help me ? I wiped data, cache, system, asdf, internal storage etc but still facing this error.
Looking for compatible roms
Krishna_MDual said:
I have tried to install custom ROMs ( XenonHD , Lineageos and CosmicOS) but everytime phone stucks in boot just showing the logo. and I have waited for around 30mins.:crying:
Click to expand...
Click to collapse
I see that none of the roms that you mentioned (XenonHD , Lineageos and CosmicOS) seems to be currently available for Azus Zendone Laser 2 - Z00LD. Can anyone help me understanding which supported rom should I use for that device? Thanks.
Hi, I'm trying to flash custom roms. Recently I've tried DotOS, RR, Lineage OS, but every time I get 'error 7'. Can anyone help?
How do you install?
dead_alik said:
How do you install?
Click to expand...
Click to collapse
I have installed TWRP 3.2.1.2 recovery. Then boot my device into recovery. After that I wiped(factory reset) the device. Then open install and flash latest ROM, but every time I got error 7
flanker076 said:
I have installed TWRP 3.2.1.2 recovery. Then boot my device into recovery. After that I wiped(factory reset) the device. Then open install and flash latest ROM, but every time I got error 7
Click to expand...
Click to collapse
Try using the newer twrp 3.2.3. git version from the lineage thread, should fix this most likely
Twrp
flanker076 said:
I have installed TWRP 3.2.1.2 recovery. Then boot my device into recovery. After that I wiped(factory reset) the device. Then open install and flash latest ROM, but every time I got error 7
Click to expand...
Click to collapse
Bro, I use twrp 3.2.1 and I have never get error code -7
Download this link https://www.androidfilehost.com/?fid=746010030569959456
dead_alik said:
Bro, I use twrp 3.2.1 and I have never get error code -7/QUOTE]
still not working
Click to expand...
Click to collapse
flanker076 said:
dead_alik said:
Bro, I use twrp 3.2.1 and I have never get error code -7/QUOTE]
still not working
Click to expand...
Click to collapse
Do you cut gapps, magisk and custom rom from the pc with usb cable?
Click to expand...
Click to collapse
dead_alik said:
flanker076 said:
Do you cut gapps, magisk and custom rom from the pc with usb cable?
Click to expand...
Click to collapse
i copied those from pc, yes
Click to expand...
Click to collapse
flanker076 said:
I have installed TWRP 3.2.1.2 recovery. Then boot my device into recovery. After that I wiped(factory reset) the device. Then open install and flash latest ROM, but every time I got error 7
Click to expand...
Click to collapse
Instead of flashing twrp, try loading it through fastboot.
Boot into twrp with fastboot, wipe system, data, etc., reboot to fastboot, boot into twrp again and try flashing the rom this time. If it doesnt work try the new twrp 3.2.3.
flanker076 said:
dead_alik said:
i copied those from pc, yes
Click to expand...
Click to collapse
Its problem on me too. When I copy from pc with usb cable and flash zips get error code -7. You must download custom rom, gapps micro arm64 and magisk in your phone and copy or cut these zip files in your sd card. Because I do this and no error happened on my phone in twrp mode.)))
Click to expand...
Click to collapse
Mizuru said:
Instead of flashing twrp, try loading it through fastboot.
Boot into twrp with fastboot, wipe system, data, etc., reboot to fastboot, boot into twrp again and try flashing the rom this time. If it doesnt work try the new twrp 3.2.3.
Click to expand...
Click to collapse
I have tried both method, neither of them worked. I'll try again with 3.2.3
dead_alik said:
flanker076 said:
Its problem on me too. When I copy from pc with usb cable and flash zips get error code -7. You must download custom rom, gapps micro arm64 and magisk in your phone and copy or cut these zip files in your sd card. Because I do this and no error happened on my phone in twrp mode.)))
Click to expand...
Click to collapse
thanks for the suggestion. will try this method. also what ROM are you using?
Click to expand...
Click to collapse
flanker076 said:
dead_alik said:
thanks for the suggestion. will try this method. also what ROM are you using?
Click to expand...
Click to collapse
Try this method is working. I use Dotos rom with gapps micro arm64 and magisk 16.0 version. Not at all.)
Click to expand...
Click to collapse
Hello, I have an OP 5 with unlocked bootloader and i was rooted. So, I'm in 4.5.13, and i'm trying to install 5.1.5 but i need to be unrooted for this.
Somehow when i removed root (magisk) my phone entered in bootloop mode (i think that magisk lost the original boot img). I flashed the stock boot img and the phone booted normally and without root. However i think that some "crumbs" of the magisk or adway stayed in my system or phone partitions and my phone continues to say that he can´t install the OTA. I've already wiped cache and data in the recovery and tried to install with adb sideload but it fails.
I still have my OOS and is working fine, but I can't update... Any ideas?
Do you think that if I do the normal settings > restore factory settings will it work? Or that option will be also damaged?
Should i boot TWRP in fastboot, and try to do a factory reset and then flash 5.1.5?
For your information, i've never flashed anything besides magisk and the attempts to update. The rom is the original as also the recovery. To flash the magisk i always booted twrp connected by usb to my PC.
I apreciate all the help!!
pdalvares said:
I apreciate all the help!!
Click to expand...
Click to collapse
https://downloads.oneplus.com/oneplus-5/oneplus_5_oxygenos_5.1.5/
This is the full OOS ROM Zip with instructions to flash with either stock Recovery, or TWRP.
Dirk said:
This is the full OOS ROM Zip with instructions to flash with either stock Recovery, or TWRP.
Click to expand...
Click to collapse
Yo, i already tried it different ways, but thank you :/
pdalvares said:
Yo, i already tried it different ways, but thank you :/
Click to expand...
Click to collapse
Fastboot flash TWRP, format partitions and flash full OOS ROM and Magisk. What's the difficulty?
https://www.xda-developers.com/how-to-install-twrp/
Dirk said:
Fastboot flash TWRP, format partitions and flash full OOS ROM and Magisk. What's the difficulty?
https://www.xda-developers.com/how-to-install-twrp/
Click to expand...
Click to collapse
Ok i'm gonna try it i'm sorry for my noobish but you know the smartphone was expensive and i'm afraid to brick it someway :/
Just one question: when you say formating partitions you mean wipe data, cache, system and dalvik / ART cache right?
thanks alot for your help and im sorry for being noob xD
I've my nexus 7 with root and PureNexus rom and had an moto g with custom rom, twrp and root but somehow I'm afraid with the OP5 because it was very expensive to my pocket xD :silly:
pdalvares said:
Ok i'm gonna try it i'm sorry for my noobish but you know the smartphone was expensive and i'm afraid to brick it someway :/
Just one question: when you say formating partitions you mean wipe data, cache, system and dalvik / ART cache right?
thanks alot for your help and im sorry for being noob xD
I've my nexus 7 with root and PureNexus rom and had an moto g with custom rom, twrp and root but somehow I'm afraid with the OP5 because it was very expensive to my pocket xD :silly:
Click to expand...
Click to collapse
Even if you tried really hard it would be almost impossible to 'Brick' a Oneplus phone. We even have unbrick tools to revive dead devices. Oneplus phones are like zombies. Really hard to keep down. The price we usually pay for messing up is nothing more than having to do a clean install and having to set the phone up again. We've all been there!
Once you have TWRP installed you could try a simple swipe-to-wipe from the 'Wipe' menu in TWRP and then flash the full OOS ROM & Magisk. I would recommend going into the 'Advanced' sub menu from 'Wipe' and select every partition. This will erase your Internal Storage, so make sure you have a backup of everything on your PC. Once you've done this you should use the TWRP 'Reboot' menu to reboot back into Recovery. Copy the ROM and Magisk zips back to Internal Storage from PC and Install them from TWRP 'Install' menu.
Dirk said:
Even if you tried really hard it would be almost impossible to 'Brick' a Oneplus phone. We even have unbrick tools to revive dead devices. Oneplus phones are like zombies. Really hard to keep down. The price we usually pay for messing up is nothing more than having to do a clean install and having to set the phone up again. We've all been there!
Once you have TWRP installed you could try a simple swipe-to-wipe from the 'Wipe' menu in TWRP and then flash the full OOS ROM & Magisk. I would recommend going into the 'Advanced' sub menu from 'Wipe' and select every partition. This will erase your Internal Storage, so make sure you have a backup of everything on your PC. Once you've done this you should use the TWRP 'Reboot' menu to reboot back into Recovery. Copy the ROM and Magisk zips back to Internal Storage from PC and Install them from TWRP 'Install' menu.
Click to expand...
Click to collapse
I've made what you said but it gives me the error "Updater process ended with error: 7"
pdalvares said:
I've made what you said but it gives me the error "Updater process ended with error: 7"
Click to expand...
Click to collapse
Which TWRP are you using? It should be the latest Official version, or you could try the latest codeworkx from here:
https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/cheeseburger/recovery/
Error 7 is a generic error code. The useful information about the error is usually in the body of text.
If you can't get TWRP to play nicely you can use it to format partitions as mentioned before, and then use it to install the stock OOS recovery from the bottom of this page:
https://downloads.oneplus.com/oneplus-5/oneplus_5_oxygenos_5.1.5/
The stock recovery is an .img, so in the TWRP 'Install' menu you need to select Image instead of Zip at the bottom of the screen. Move the stock recovery .img to Internal Storage and flash it. Reboot into Stock Recovery and flash full OOS zip.
Dirk said:
Even if you tried really hard it would be almost impossible to 'Brick' a Oneplus phone. We even have unbrick tools to revive dead devices. Oneplus phones are like zombies. Really hard to keep down. The price we usually pay for messing up is nothing more than having to do a clean install and having to set the phone up again. We've all been there!
Once you have TWRP installed you could try a simple swipe-to-wipe from the 'Wipe' menu in TWRP and then flash the full OOS ROM & Magisk. I would recommend going into the 'Advanced' sub menu from 'Wipe' and select every partition. This will erase your Internal Storage, so make sure you have a backup of everything on your PC. Once you've done this you should use the TWRP 'Reboot' menu to reboot back into Recovery. Copy the ROM and Magisk zips back to Internal Storage from PC and Install them from TWRP 'Install' menu.
Click to expand...
Click to collapse
YO BRO i've made it. I installed other version of the OS and it's working! Now im gonna see if i can update it to the newest version
Thank you for encouraging me!
pdalvares said:
YO BRO i've made it. I installed other version of the OS and it's working! Now im gonna see if i can update it to the newest version
Thank you for encouraging me!
Click to expand...
Click to collapse
Let me know how you get on. :good:
Dirk said:
Let me know how you get on. :good:
Click to expand...
Click to collapse
It all works fine but when doing the OTA in the OOS to 5.1.4 the device reboots, enters in oxygenos recovery but it fails...
EDIT:
Could it be because the bootloader is unlocked?? Is it safe to lock it like i unlocked it? No problem?
pdalvares said:
It all works fine but when doing the OTA in the OOS to 5.1.4 the device reboots, enters in oxygenos recovery but it fails...
Click to expand...
Click to collapse
Work through the steps in post #8. Begin with the latest codeworkx TWRP and go from there.
Check this guide if you think you might be missing something:
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
Dirk said:
Work through the steps in post #8. Begin with the latest codeworkx TWRP and go from there.
Check this guide if you think you might be missing something:
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
Click to expand...
Click to collapse
It failed that way
ok so im gonna write here what it says:
" Installing zip file...
Checking for Digest file...
Skipping Digest check: no Digest file found vendor partition is not existed, exit ota!!
Updater process ended with ERROR: 7
error installiong...
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done "
pdalvares said:
It failed that way
ok so im gonna write here what it says:
" Installing zip file...
Checking for Digest file...
Skipping Digest check: no Digest file found vendor partition is not existed, exit ota!!
Updater process ended with ERROR: 7
error installiong...
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done "
Click to expand...
Click to collapse
Are you trying to OTA or full ROM? OTA is not going to work. Only full ROM .zip will get the job done.
Have you considered giving up on OOS for now and just try flashing a Custom ROM from TWRP? I'd recommend Dirty Unicorns Oreo for now until Pie ROMs mature. You can get their ROM from their website.. Should be no issue at all flashing it. Opengapps ARM64, 8.1 Nano is the Gapps i'd recommend.
Wipe in TWRP, Flash Firmware/ROM/Gapps/Magisk. Job done.
pdalvares said:
It failed that way
ok so im gonna write here what it says:
" Installing zip file...
Checking for Digest file...
Skipping Digest check: no Digest file found vendor partition is not existed, exit ota!!
Updater process ended with ERROR: 7
error installiong...
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done "
Click to expand...
Click to collapse
One more thing dude, i've flashed the 5.1.1 on top of the 4.5.14 without wiping, and it is taking along time to boot. I should wipe it? :/
pdalvares said:
One more thing dude, i've flashed the 5.1.1 on top of the 4.5.14 without wiping, and it is taking along time to boot. I should wipe it? :/
Click to expand...
Click to collapse
Initial boot can take some time.
I'm at a loss why your phone hates OOS, but it might love Custom ROMs. Give it some thought.
pdalvares said:
One more thing dude, i've flashed the 5.1.1 on top of the 4.5.14 without wiping, and it is taking along time to boot. I should wipe it? :/
Click to expand...
Click to collapse
MY BROTHER, i really needed to lock the bootloader, wiped everything and adb sideloaded 5.1.1. It booted at android 8 and then i ran the OTA's until the newest one and now i have my phone fully functional, with the latest update, and running all stock. Thank's alot for all the help. I don´t know how to thank you! Peace and see you one day!
EDIT:
Maybe one day I will try some custom ROM, like lineage or other best than that. For now im gonna stay like this for a while, just because yes
pdalvares said:
MY BROTHER, i really needed to lock the bootloader, wiped everything and adb sideloaded 5.1.1. It booted at android 8 and then i ran the OTA's until the newest one and now i have my phone fully functional, with the latest update, and running all stock. Thank's alot for all the help. I don´t know how to thank you! Peace and see you one day!
EDIT:
Maybe one day I will try some custom ROM, like lineage or other best than that. For now im gonna stay like this for a while, just because yes
Click to expand...
Click to collapse
Good news! :good:
You can see how resilient OP phones are. You can pretty much always get them back to a working condition. I can only guess but it sounds like you were right. Something was wrong with your Bootloader after the initial problems. Glad you got it sorted.