I accidentally deleted the data partition. Everything else works fine including Recovery/Fastboot. Normally I'd be using the Mega Unbrick Guide to restore the partition, but not an option right now for the 5 (128GB). Assistance would be appreciated. Maybe flashing a userdata.img would work?
I'd recommend you to completely wipe and flash Stock OOS from here : https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
That should sort all your problems related to partitioning. Let me know how it goes.
anmolkakkar said:
I'd recommend you to completely wipe and flash Stock OOS from here : https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
That should sort all your problems related to partitioning. Let me know how it goes.
Click to expand...
Click to collapse
Already tried flashing the Full ROM earlier, but that doesn't fix the missing partition. Unless flashing with Stock Recovery would make a difference. Need a link to stock recovery to try that
Was looking into dumping partitions off a working OP5.
https://forum.xda-developers.com/showthread.php?t=2450045
Don't have a second OP5 (128GB) to dump partitions, but I did generate some .img files using this method. Optimally, flashing a proper userdata.img through fastboot should fix the partition, I believe.
aenews said:
I accidentally deleted the data partition. Everything else works fine including Recovery/Fastboot. Normally I'd be using the Mega Unbrick Guide to restore the partition, but not an option right now for the 5 (128GB). Assistance would be appreciated. Maybe flashing a userdata.img would work?
Click to expand...
Click to collapse
fastboot format userdata ?
Hastaloego said:
fastboot format userdata ?
Click to expand...
Click to collapse
The partition doesn't exist right now. It cannot be mounted or formatted. If someone could use the guide above and pull a userdata.img from a 128GB OP5, pretty sure that would restore the partition if I flash it in fastboot.
aenews said:
The partition doesn't exist right now. It cannot be mounted or formatted. If someone could use the guide above and pull a userdata.img from a 128GB OP5, pretty sure that would restore the partition if I flash it in fastboot.
Click to expand...
Click to collapse
Have you tried going into TWRP > Wipe> advance wipe > data >change or repair filesystem > change filesystem> ext4?
This should help.
You can also try restore the nandroid uploaded on my thread
Sent from Funk Tuned 3T
flame360 said:
Have you tried going into TWRP > Wipe> advance wipe > data >change or repair filesystem > change filesystem> ext4?
This should help.
Click to expand...
Click to collapse
Thanks that worked! And much simpler and faster. I didn't realize there was an easy way to repair the filesystem in TWRP (derp) but that's awesome.
Funk Wizard said:
You can also try restore the nandroid uploaded on my thread
Sent from Funk Tuned 3T
Click to expand...
Click to collapse
Thanks for the tip!
Also I *think* I was able to extract a userdata.img after I fixed the partition. In case that's ever needed in the future...
aenews said:
Thanks that worked! And much simpler and faster. I didn't realize there was an easy way to repair the filesystem in TWRP (derp) but that's awesome.
Thanks for the tip!
Also I *think* I was able to extract a userdata.img after I fixed the partition. In case that's ever needed in the future...
Click to expand...
Click to collapse
Welcome buddy
Funk Wizard said:
Welcome buddy
Click to expand...
Click to collapse
So I managed to do the same thing, but with my system partition. I can't figure out what img to flash to system or where to get it from. Can anyone help me please?
Also, first thing I did was attempt to repair the partition via TWRP but no dice on that...
electronicghandi said:
So I managed to do the same thing, but with my system partition. I can't figure out what img to flash to system or where to get it from. Can anyone help me please?
Also, first thing I did was attempt to repair the partition via TWRP but no dice on that...
Click to expand...
Click to collapse
try flashing the stock zip from twrp.
electronicghandi said:
So I managed to do the same thing, but with my system partition. I can't figure out what img to flash to system or where to get it from. Can anyone help me please?
Also, first thing I did was attempt to repair the partition via TWRP but no dice on that...
Click to expand...
Click to collapse
Restore the Nandroid
Sent from my OnePlus5 using XDA Labs
Worked for me to on a OnePlus 3
flame360 said:
Have you tried going into TWRP > Wipe> advance wipe > data >change or repair filesystem > change filesystem> ext4?
This should help.
Click to expand...
Click to collapse
That did it on my girlfriends OnePlus3 thank you very much!
aenews said:
Thanks that worked! And much simpler and faster. I didn't realize there was an easy way to repair the filesystem in TWRP (derp) but that's awesome.
Thanks for the tip!
Also I *think* I was able to extract a userdata.img after I fixed the partition. In case that's ever needed in the future...
Click to expand...
Click to collapse
Can you please share the userdata.img for 128gb and also fastboot image files for one plus 5t, my phone is dead please help
Related
Hi,
can i boot into recovery when i formatted the /boot partition before ?
Havnt found any infos on googling...
I Just wonder if its safe to play around with /boot.
thanks for Help.
unic09 said:
Hi,
can i boot into recovery when i formatted the /boot partition before ?
Havnt found any infos on googling...
I Just wonder if its safe to play around with /boot.
thanks for Help.
Click to expand...
Click to collapse
I can only wish you good luck
just curious, why do u need to format the boot ?
antique_sonic said:
I can only wish you good luck
just curious, why do u need to format the boot ?
Click to expand...
Click to collapse
i dont know. I have installed Cyanogenmod and have to restore my stockfirmware because auf a bad vcf export. But if i dont touch the boot partition i cant start the stockfirmware after restore.
So i just want to be sure that nothing can happen if i restore /boot
unic09 said:
i dont know. I have installed Cyanogenmod and have to restore my stockfirmware because auf a bad vcf export. But if i dont touch the boot partition i cant start the stockfirmware after restore.
So i just want to be sure that nothing can happen if i restore /boot
Click to expand...
Click to collapse
i c.
so sorry, I have no idea, because I never flash CM before at all. But, there should be a guide on how to do without formatting boot partition. try to search.
unic09 said:
Hi,
can i boot into recovery when i formatted the /boot partition before ?
Havnt found any infos on googling...
I Just wonder if its safe to play around with /boot.
thanks for Help.
Click to expand...
Click to collapse
Boot and recovery are on different partitions, and recovery had its own kernel.
You can wipe boot and still enter recovery -- that's what it's designed for.
THX
jisoo said:
Boot and recovery are on different partitions, and recovery had its own kernel.
You can wipe boot and still enter recovery -- that's what it's designed for.
Click to expand...
Click to collapse
Tanks. That was the answer i want to hear
Hello,
so i backup my phone before i do anything risky. so i was trying to restore my phone (from yesterday backup) using twrp. everything went perfect and when my device rebooted after restore. it stuck on Google Logo. i tried 3 times but no luck. any help? i select Boot, Data, System, System.img
EDIT: should i select vendor / vendor.img ?? while restoring it ?
UPDATE: when i tried 4th time. my phone rebooted after about 72% and stuck on google logo.
Tried clearing cache? Also, what things did you precisely backup?
DJBhardwaj said:
Tried clearing cache? Also, what things did you precisely backup?
Click to expand...
Click to collapse
almost everything including vendor ; no cache
setul34 said:
almost everything including vendor ; no cache
Click to expand...
Click to collapse
I had the same issue when I backed up system image.
DJBhardwaj said:
I had the same issue when I backed up system image.
Click to expand...
Click to collapse
okay so any solution?
Try it without the system image.
DJBhardwaj said:
Try it without the system image.
Click to expand...
Click to collapse
i did but that did not install root / apps / settings. basically i just got data and stock rom.
setul34 said:
i did but that did not install root / apps / settings. basically i just got data and stock rom.
Click to expand...
Click to collapse
No idea, I myself haven't tried further.
Lets see if someone else comes up with something
setul34 said:
Hello,
so i backup my phone before i do anything risky. so i was trying to restore my phone (from yesterday backup) using twrp. everything went perfect and when my device rebooted after restore. it stuck on Google Logo. i tried 3 times but no luck. any help? i select Boot, Data, System, System.img
EDIT: should i select vendor / vendor.img ?? while restoring it ?
UPDATE: when i tried 4th time. my phone rebooted after about 72% and stuck on google logo.
Click to expand...
Click to collapse
Let me guess you are on TWRP 3.0.0.0?
Yes
oneandroidnut said:
Let me guess you are on TWRP 3.0.0.0?
Click to expand...
Click to collapse
@oneandroidnut Yes.
setul34 said:
@oneandroidnut Yes.
Click to expand...
Click to collapse
You don't backup system image, only backup system, data, and boot.
setul34 said:
@oneandroidnut Yes.
Click to expand...
Click to collapse
pm me if you are still having issues we can go to hangouts or something and i can walk you through
oneandroidnut said:
pm me if you are still having issues we can go to hangouts or something and i can walk you through
Click to expand...
Click to collapse
It'd be much better if you did this here, that way the solution is available for others to find, that's pretty much the entire point of the Q&A section. I'm confident it's just a case of selecting the wrong partitions to backup anyway.
Heisenberg said:
It'd be much better if you did this here, that way the solution is available for others to find, that's pretty much the entire point of the Q&A section. I'm confident it's just a case of selecting the wrong partitions to backup anyway.
Click to expand...
Click to collapse
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
oneandroidnut said:
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
Click to expand...
Click to collapse
That seems over-complicated. You only need to backup/restore system, data, and boot. Vendor is optional if you have Layers that you want to keep. Don't backup/restore system image or vendor image. That's the reason he got into this mess, be backed up and restored system image. I posted the solution a couple of posts back.
okay so i tried to recover Data System Boot, still didn't work. so i remove everything including twrp and installed stock rom. and then i installed twrp 3.0 and somehow it worked and my device is back on
oneandroidnut said:
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
Click to expand...
Click to collapse
this worked for me thankyou
Heisenberg said:
That seems over-complicated. You only need to backup/restore system, data, and boot. Vendor is optional if you have Layers that you want to keep. Don't backup/restore system image or vendor image. That's the reason he got into this mess, be backed up and restored system image. I posted the solution a couple of posts back.
Click to expand...
Click to collapse
i won't make that mistake again to backup vendor or system image.
Thanks @oneandroidnut @Heisenberg
setul34 said:
okay so i tried to recover Data System Boot, still didn't work. so i remove everything including twrp and installed stock rom. and then i installed twrp 3.0 and somehow it worked and my device is back on
this worked for me thankyou
i won't make that mistake again to backup vendor or system image.
Thanks @oneandroidnut @Heisenberg
Click to expand...
Click to collapse
No problem man glad it worked!!
I had the same problem.
I tried to restore a backup (MMB29Q - system+data+boot, done after installing the last factory image without root) and I got blocked on the Google logo. I tried twice without managing.
In the end I solved the problem installing supersu v2.68 zip before restarting.
It's as though the restore needs the root to work properly.
What do you think?
Thanks.
Hello everyone! I bring news from the TWRP developers from the #TWRP IRC channel! TWRP 3.0.2-1 has a fatal bug! If you backup and restore EFS it will brick you! Do not backup and restore EFS on 3.0.2-1! Use 3.0.2-0 instead! This has already been fixed in the newer builds!
If you have been bricked you NEED to Erase the EFS partitions and that will fix it immediately.
For the Nexus 6P go to TWRP. Then on PC Open Command Prompt with access to ADB ( Android Debug Bridge) and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB Shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This should fix it for ANY Nexus 6P users. Users on other phones with the same problem await instructions!
Hello everyone heres a guide on how i formated my le pro 3 720 64gb from ext4. please know that this will delete all of your data will be delete i strongly recommand doing a twrp or tatanium backup before hand! allso if this somehow ****s up i will not be hold responsible. i am simply showing you all how i did this to get my result. now with all the formalitys in place lets talk about what exactly the steps are after you backed up everything you want to keep download your feverite rom. the one i am ussing is turbos aokp destroyer ver2, download it unto your pc, allso make sure you have twro custom recovery that support the f2fs.
here is the one i ussed. https://drive.google.com/file/d/0B9ZMWt4u_wSDVkp3UlMxS1liMUE/view
after you have made sure your twrp support it and you backed up everything you need. boot into twrp, wipe/advanced wipe/check data/repair or change file system/chenge file system/ f2fs do the same for data and for cache. then connect you phone via the usb cable to a pc with minimal adb put the rom you decided to install on your le pro 3 into the minimal adb folder and call it something easy like Kitty. i do this all the time xD
then open a cammend windows as admin and type the fallowing code.
adb push push kitty.zip /sdcard
this will start your rom being moved from the pc unto your sdcard on your phone. and i allso belive its the safest way to do it dont qote me on that tho.
then you just install your kitty rom and you should be good to go. NOTE in my case with the destroyer 2 aokp from my good freind turbo i dont think the /system supports f2fs as it reformats it into the ext4 on installation, but data and cache will reamain f2fs at all times. and it does seem quite abit faster regardless. thanks everyone for reading and im sorry if this is done in a extreme noob fashion i hope you all will be able to understand whats going on and all. peace out and be sure to let me know how it turns out for you
Do you think it is good than format everything to install a Rom with the twrp in a normal way connecting a USB otg?
venezolano69 said:
Do you think it is good than format everything to install a Rom with the twrp in a normal way connecting a USB otg?
Click to expand...
Click to collapse
It might work. I've never used a otg in TWRP before but if it works I can't see why not.
DrTorretz1 said:
It might work. I've never used a otg in TWRP before but if it works I can't see why not.
Click to expand...
Click to collapse
OK thanx for the guide
venezolano69 said:
OK thanx for the guide
Click to expand...
Click to collapse
Your welcome hope it helps!
Thanks for the tutorial! one tip, system partition its not recommended to format to f2fs, because system its a "readonly" partition and ext4 is fastest than f2fs in read, you only need to change /data and /cache to f2fs to improve the performance of the device!
FYI, at the very least you can format your cache partition to F2FS without losing any data.
slgooding said:
FYI, at the very least you can format your cache partition to F2FS without losing any data.
Click to expand...
Click to collapse
I tried to format cache it didn't work I'm on 23s destroyer with the same twrp navigator v6
villarleg said:
Thanks for the tutorial! one tip, system partition its not recommended to format to f2fs, because system its a "readonly" partition and ext4 is fastest than f2fs in read, you only need to change /data and /cache to f2fs to improve the performance of the device!
Click to expand...
Click to collapse
Wow thanks village! I'm happy you enjoyed the guide also thanks for letting me know about the system I will put it up there!
venezolano69 said:
I tried to format cache it didn't work I'm on 23s destroyer with the same twrp navigator v6
Click to expand...
Click to collapse
Does it come up with a error or something? I'm not sure mine did it fine
slgooding said:
FYI, at the very least you can format your cache partition to F2FS without losing any data.
Click to expand...
Click to collapse
Yeah I suppose so. It works really well regardless
DrTorretz1 said:
Does it come up with a error or something? I'm not sure mine did it fine
Click to expand...
Click to collapse
Something like "not possible to mount"
venezolano69 said:
Something like "not possible to mount"
Click to expand...
Click to collapse
That sounds really strange. I'm sorry I can't assist further. Data should be the most important one annyways
Whenever i try to format data or cache to F2FS i get Failed to mount errors to both cache and data. But i still could flash the rom, tho i was getting a lot of lag sometimes and i thought it could be because of that. I guess this shouldnt happen, any idea?
EDIT: Fixed by updating twrp to 3.1.0.0
---------- Post added at 09:03 PM ---------- Previous post was at 08:26 PM ----------
Now i have other problem, im stuck at recovery without rom on sdcard, and i cant seem to use adb, it says my device is unauthorized when i type adb devices
Enamak said:
Whenever i try to format data or cache to F2FS i get Failed to mount errors to both cache and data. But i still could flash the rom, tho i was getting a lot of lag sometimes and i thought it could be because of that. I guess this shouldnt happen, any idea?
EDIT: Fixed by updating twrp to 3.1.0.0
---------- Post added at 09:03 PM ---------- Previous post was at 08:26 PM ----------
Now i have other problem, im stuck at recovery without rom on sdcard, and i cant seem to use adb, it says my device is unauthorized when i type adb devices
Click to expand...
Click to collapse
Do you have an otg?
venezolano69 said:
Do you have an otg?
Click to expand...
Click to collapse
I flashed the ROM thro sideload, all fixed now i also thought about otg but i didnt have one and didnt really want to get onde x)
Thanks anyway
Enamak said:
I flashed the ROM thro sideload, all fixed now i also thought about otg but i didnt have one and didnt really want to get onde x)
Thanks anyway
Click to expand...
Click to collapse
Otg is very good stuff, when you wipe everything you put Rom insidie the otg and you can flash everything you want
I have another problem.. I formated /cache /data (no problems, errors). After that I flashed "TURBO2012's China / US EUI 23s V8" (no problems, errors).
But DiskInfo from the playstore is showing me ext4 in /cache and /data ?
Does this work with LineageOS 13? Did this and flashed the ROM but it's been stuck on the boot screen for a while.
cherryduck said:
Does this work with LineageOS 13? Did this and flashed the ROM but it's been stuck on the boot screen for a while.
Click to expand...
Click to collapse
Same here. I tried it a few days ago with the latest Lineage nightly and started formatting all partitions with F2FS with the same outcome: stuck on bootscreen.
Gradually I returned my partitions to ext4 and only after I returned everything to 'normal' I got past the boot screen. Not even "cache" worked with F2FS.
Hello,
I read about partition A/B, but I would like to have more insight some points are not really clear in my head.
My OP6T is rooted on partition B, everything works fine on this partition
On partition A, It automatically boot into recovery
How can I have a fresh install on both partition ?
Does I have to root both partition ?
You don't have to root both partitions, your second partition is probably blank, you can flash a rom to that partition or just let it be, its not a must have for a working device and generally when you root magisk inserts intself into both partitions.
Dark Nightmare said:
You don't have to root both partitions, your second partition is probably blank, you can flash a rom to that partition or just let it be, its not a must have for a working device and generally when you root magisk inserts intself into both partitions.
Click to expand...
Click to collapse
Ok, thank you for quick answer.
how do you flash a rom only on one partition ?
when you wipe in TWRP, does it wipe both or only one partition ?
I would like to have both partition at the same stage of update in case one get broken.
It is possible to make a copy of one partition to the other ?
Soujyu51 said:
Ok, thank you for quick answer.
how do you flash a rom only on one partition ?
when you wipe in TWRP, does it wipe both or only one partition ?
I would like to have both partition at the same stage of update in case one get broken.
It is possible to make a copy of one partition to the other ?
Click to expand...
Click to collapse
Well the whole point of two partitions is to have one in the previous state if an update breaks the current one...
You can flash one of the fastboot roms or full zips available in the general section, but you may have to modify the zip files to only flash to a single slot as the zips currently flash to both slots.
Dark Nightmare said:
Well the whole point of two partitions is to have one in the previous state if an update breaks the current one....
Click to expand...
Click to collapse
that's my point, I want to copy my partition B to my partition A, then modify one or the other, for a period they will be at the same state but this will rapidly change
Dark Nightmare said:
You can flash one of the fastboot roms or full zips available in the general section, but you may have to modify the zip files to only flash to a single slot as the zips currently flash to both slots.
Click to expand...
Click to collapse
is it possible to wipe everything and make a fresh install on both ?
Soujyu51 said:
is it possible to wipe everything and make a fresh install on both ?
Click to expand...
Click to collapse
use fastboot rom.
dieandromeda said:
use fastboot rom.
Click to expand...
Click to collapse
I will need a bit more information please xD
Soujyu51 said:
I will need a bit more information please xD
Click to expand...
Click to collapse
Only system / boot are concerned by the slot organization. Read general texts and tutorials about that and fastboot use. Everything needed is on the internet.
Striatum_bdr said:
Only system / boot are concerned by the slot organization. Read general texts and tutorials about that and fastboot use. Everything needed is on the internet.
Click to expand...
Click to collapse
Thank you very much that is a big help in my questionning
I followed this
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
and use this one flash-all.bat
it boot on both partition
Thank you
Thanks!
It solved my problems
Hello!
I tried to do a clean install of MIUI Global (10.3.11, which came with the phone). I didn't install any other ROM before in this device. Wiped eveything (data, system, dalvik etc.), then flashed the ROM and Magisk.
Now, when I connect the phone via USB I cannot access my files. It only shows "internal shared storage" on Windows, and it's all empty. When I try to transfer a file it shows nothing, the file just don't go. While in recovery I can access the storage and transfer files.
*I did activate USB depuration in developer mode.
*I did change de USB mode to "transfer files"
*I reinstalled the ROM several times.
Maybe it's something to do with the format type of the storage?
I'd try to do a ROM fastboot but I cannot find the fastboot version of MIUI Global for MI 9T.
Please, help
Did you format data? I think you forgot this part, format data then you can wipe it if you want.(formatting will delete everything from your internal storage ofc)
Ohk Let Me Help You .
Have You Advance Swipe the internal storage..then rebooted to twrp Before flashing the ROM !!
GedeonTaylor said:
Did you format data? I think you forgot this part, format data then you can wipe it if you want.(formatting will delete everything from your internal storage ofc)
Click to expand...
Click to collapse
Thanks for the reply! Yes, I did.
It seems like the "/storage/emulated/0/........." is broken. I cannot do nothing on this folder. I tried to create a file/folder in it with Solid Explorer and it says that the directory wasn't found.
Any idea?
Dev_Kahl said:
Ohk Let Me Help You .
Have You Advance Swipe the internal storage..then rebooted to twrp Before flashing the ROM !!
Click to expand...
Click to collapse
I already tried this. I'll try once more to format data, wipe, reboot to TWRP and flash the ROM.
velkz said:
I already tried this. I'll try once more to format data, wipe, reboot to TWRP and flash the ROM.
Click to expand...
Click to collapse
Ohk seems like a complicated one ...Can You Flash The FASTBOOT ROM if I give you the link of the correct ROM for you device !! ( this is all I can help )
Dev_Kahl said:
Ohk seems like a complicated one ...Can You Flash The FASTBOOT ROM if I give you the link of the correct ROM for you device !! ( this is all I can help )
Click to expand...
Click to collapse
Yes, please! I didn't find any fastboot ROM for mi 9t.
GedeonTaylor said:
Did you format data? I think you forgot this part, format data then you can wipe it if you want.(formatting will delete everything from your internal storage ofc)
Click to expand...
Click to collapse
Noticed that when I try to wipe data after formatting it an error appears on TWRP: "error opening '/data/media' (No such file or directory". Is it normal?
Seems like the ROM isn't properly creating the directory, that's why I can't access it.
velkz said:
Yes, please! I didn't find any fastboot ROM for mi 9t.
Click to expand...
Click to collapse
http://c.mi.com/oc/miuidownload/detail?guide=2
Here You Go
Dev_Kahl said:
http://c.mi.com/oc/miuidownload/detail?guide=2
Here You Go
Click to expand...
Click to collapse
Thank you! Gonna try it and update here
Edit: FOUND THE FIX! All I had to do was fix the SELinux contexts on TWRP. Now everything is normal. Thank you both for trying to help
velkz said:
Thank you! Gonna try it and update here
Edit: FOUND THE FIX! All I had to do was fix the SELinux contexts on TWRP. Now everything is normal. Thank you both for trying to help
Click to expand...
Click to collapse
Velkz
How do you did that?
mauriciocardoso said:
Velkz
How do you did that?
Click to expand...
Click to collapse
Boot into TWRP -> Advanced -> Fix Contexts