Database Info

[Q] Switch from CWM to TWRP

I have CWM installed now, but I need to RMA because of some excessive screen bleeding in the upper left corner of my N5. On the return to stock thread, there is a section that involves resetting the tamper flag, and it says that it works best with TWRP.
I've only used CWM before, so can I just download TWRP and flash it in adb the same way I initially installed CWM?
Thanks for any help.

vinnycogs820 said:
I have CWM installed now, but I need to RMA because of some excessive screen bleeding in the upper left corner of my N5. On the return to stock thread, there is a section that involves resetting the tamper flag, and it says that it works best with TWRP.
I've only used CWM before, so can I just download TWRP and flash it in adb the same way I initially installed CWM?
Thanks for any help.
Click to expand...
Click to collapse
yes just download the .img from twrp website and flash in recovery. "fastboot flash recovery filename.img"

Boblank said:
yes just download the .img from twrp website and flash in recovery. "fastboot flash recovery filename.img"
Click to expand...
Click to collapse
awesome thanks man, that worked perfectly. one other question if you know this, when I do the factory reset in CWM and in TWRP, it seems to get hung up and never finishes. Is there anything I can do to make sure that it fully wipes?
I was going to play around with a few ROMs before my new N5 gets here.

vinnycogs820 said:
awesome thanks man, that worked perfectly. one other question if you know this, when I do the factory reset in CWM and in TWRP, it seems to get hung up and never finishes. Is there anything I can do to make sure that it fully wipes?
I was going to play around with a few ROMs before my new N5 gets here.
Click to expand...
Click to collapse
I don't know why TWRP hangs during factory reset, but you can get the same result using fastboot. Just flash the userdata partition and erase the cache partition.

Encrypted phone now cant use CWM backup and adb

Hello guys, having a bit of a dilemna here as only took the plunge to root today and is my first time in doing so. What I have done is updated to 4.4.2 KitKat OTA and then rooted my moto g. I used the superboot method and got the horrible pink screen and had to manually install supersu, however the device is rooted and obviously the bootloader is unlocked. I then proceeded to put everything back on my phone and then encrypted my phone.
However, I tried to get into recovery (stock) and was fronted with the on its back android with its belly open and red "!" in a triangle. I got this before I even unlocked to bootloader. Anyhow, I wanted to use a custom recovery so I could manage different ROMs in ROM manager etc, so I flashed CWM6046-MotoG44.img (CMW ver. 6.0.4.6) and all was swell.... until i wanted to make a backup.
I did a little searching around and was stumped until I found a post suggesting that CMW couldnt mount storage because the device was encrypted.
What I would like to know if at all possible; what would be the best course of action to take, as im unsure what will/could brick/break my device and as its encrypted I dont think adb commands are pushed as when flashing the recovery image, my device was listed in fastboot devices but not adb devices.
Should I flash a stock image and go from there, put everything back on yada yada yada and NOT encrypt the device, or....
Should I do a factory reset? will this brick my device/lose root access? or will I be able to re root?
I really appreciate any input you guys can give me, and for the meantime im just going to leave my device as it is and not flash anything else,
Many thanks and best regards,
voosh

Anybody have any ideas?

Can anybody help me here. Need to get this sorted so I can flash a custom ROM. Thanks

Bump...................

voosh710 said:
Hello guys, having a bit of a dilemna here as only took the plunge to root today and is my first time in doing so. What I have done is updated to 4.4.2 KitKat OTA and then rooted my moto g. I used the superboot method and got the horrible pink screen and had to manually install supersu, however the device is rooted and obviously the bootloader is unlocked. I then proceeded to put everything back on my phone and then encrypted my phone.
However, I tried to get into recovery (stock) and was fronted with the on its back android with its belly open and red "!" in a triangle. I got this before I even unlocked to bootloader. Anyhow, I wanted to use a custom recovery so I could manage different ROMs in ROM manager etc, so I flashed CWM6046-MotoG44.img (CMW ver. 6.0.4.6) and all was swell.... until i wanted to make a backup.
I did a little searching around and was stumped until I found a post suggesting that CMW couldnt mount storage because the device was encrypted.
What I would like to know if at all possible; what would be the best course of action to take, as im unsure what will/could brick/break my device and as its encrypted I dont think adb commands are pushed as when flashing the recovery image, my device was listed in fastboot devices but not adb devices.
Should I flash a stock image and go from there, put everything back on yada yada yada and NOT encrypt the device, or....
Should I do a factory reset? will this brick my device/lose root access? or will I be able to re root?
I really appreciate any input you guys can give me, and for the meantime im just going to leave my device as it is and not flash anything else,
Many thanks and best regards,
voosh
Click to expand...
Click to collapse
When you get the dead android hold power button for ten seconds then tap the power button,that should get you into stock recovery ,then navigate to wipe data factory reset ,you shouldn't lose root but you will lose da ta and apps

Thanks for the reply but I have already installed the cwm custom recovery. Should I add that I'm still able to access device, my problem mainly is getting rid of encryption as I can't use cwm while device is encrypted and can only do so by factory reset or flashing a stock ROM, but unsure of which option to take. Many thanks and best regards

kieranc88 said:
When you get the dead android hold power button for ten seconds then tap the power button,that should get you into stock recovery ,then navigate to wipe data factory reset ,you shouldn't lose root but you will lose da ta and apps
Click to expand...
Click to collapse
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview try this cwm it worked for me,I'm not too clued up on encryption but I'm guessing you can't read/write to phones system to easily with it on so I'd guess it conflicts with root
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
kieranc88 said:
When you get the dead android hold power button for ten seconds then tap the power button,that should get you into stock recovery ,then navigate to wipe data factory reset ,you shouldn't lose root but you will lose da ta and apps
Click to expand...
Click to collapse
voosh710 said:
Thanks for the reply but I have already installed the cwm custom recovery. Should I add that I'm still able to access device, my problem mainly is getting rid of encryption as I can't use cwm while device is encrypted and can only do so by factory reset or flashing a stock ROM, but unsure of which option to take. Many thanks and best regards
Click to expand...
Click to collapse
So when you boot to recovery can you access recovery options or do you get dead robot

kieranc88 said:
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview try this cwm it worked for me,I'm not too clued up on encryption but I'm guessing you can't read/write to phones system to easily with it on so I'd guess it conflicts with root
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
So when you boot to recovery can you access recovery options or do you get dead robot
Click to expand...
Click to collapse
I did get a dead robot. So I flashed CWM custom recovery. I now get the cwm recovery and options, but I can't make a backup becausey filesystem is encrypted, so would like to know the best way to decrypt by means of flashing a new or ROM or simply doing a factory reset within tho phones menus.
Many thanks

voosh710 said:
I did get a dead robot. So I flashed CWM custom recovery. I now get the cwm recovery and options, but I can't make a backup becausey filesystem is encrypted, so would like to know the best way to decrypt by means of flashing a new or ROM or simply doing a factory reset within tho phones menus.
Many thanks
Click to expand...
Click to collapse
OK,you need to boot into cwm and choose the wipe data factory reset option from cwm, I tried to wipe my phone before from the phones menu and because it had a custom recovery it didn't work,but if you boot cwm-wipe data/factory reset it will remove encryption.

Any luck???

kieranc88 said:
Any luck???
Click to expand...
Click to collapse
Sorry, I fell asleep lol was a long day.
Going to try it now and will keep you posted, Cheers.
EDIT - Didnt work - failed to mount storage because "android secure"
Factory reset within the phone also didnt work - The phone reset and the android with the blue thing in its stomach was stuck in a loop, probably because of custom recovery.
Is there a stock recovery I can flash to factory restore the phone?
EDIT 2 - Flashed this recovery - http://forum.xda-developers.com/showthread.php?t=2578243
Now when I boot into recovery it just boots into the phone regularly. When performing a factory reset now the android doesnt even appear and the phone boots regularly again, still encrypted

voosh710 said:
Sorry, I fell asleep lol was a long day.
Going to try it now and will keep you posted, Cheers.
EDIT - Didnt work - failed to mount storage because "android secure"
Factory reset within the phone also didnt work - The phone reset and the android with the blue thing in its stomach was stuck in a loop, probably because of custom recovery.
Is there a stock recovery I can flash to factory restore the phone?
EDIT 2 - Flashed this recovery - http://forum.xda-developers.com/showthread.php?t=2578243
Now when I boot into recovery it just boots into the phone regularly. When performing a factory reset now the android doesnt even appear and the phone boots regularly again, still encrypted
Click to expand...
Click to collapse
I kinda guessed that would happen because its not stock recovery,have u got a us version or international(is it xt1032 or xt1034?

kieranc88 said:
I kinda guessed that would happen because its not stock recovery,have u got a us version or international(is it xt1032 or xt1034?
Click to expand...
Click to collapse
Its a unlocked retail UK version, not sure if its xt1032 or xt1034 because I renamed it to Moto G.

voosh710 said:
Its a unlocked retail UK version, not sure if its xt1032 or xt1034 because I renamed it to Moto G.
Click to expand...
Click to collapse
You've got the same as mine,OK if that didn't work it might be because its jellybean, this is a recovery for the us version but its a KitKat recovery but worst that can happen is it won't boot to recovery, flash it and if doesn't work I'll see can I extract the recovery image from my phone, try it and get back to me asap fastboot flash recovery recovery.IMG
https://www.dropbox.com/s/66br4aiyzipu6x9/recovery.img

kieranc88 said:
You've got the same as mine,OK if that didn't work it might be because its jellybean, this is a recovery for the us version but its a KitKat recovery but worst that can happen is it won't boot to recovery, flash it and if doesn't work I'll see can I extract the recovery image from my phone, try it and get back to me asap fastboot flash recovery recovery.IMG
https://www.dropbox.com/s/66br4aiyzipu6x9/recovery.img
Click to expand...
Click to collapse
Flashed and still boots regularly .

voosh710 said:
Flashed and still boots regularly .
Click to expand...
Click to collapse
In the command line is it saying recovery sent

kieranc88 said:
In the command line is it saying recovery sent
Click to expand...
Click to collapse
Sent and finished ok

voosh710 said:
Sent and finished ok
Click to expand...
Click to collapse
How many times have you flashed it,try flashing two three timees

kieranc88 said:
How many times have you flashed it,try flashing two three timees
Click to expand...
Click to collapse
Actually, looking at the device it says "hab check failed for recovery"
However the other one (jellybean one i think that I linked to) never.
tried flashing 5 or 6 times no luck

Try this link to restore to 4.3 then ota to 4.4 again http://www.modaco.com/topic/366786-how-to-flash-to-the-standard-uk-rom/

[Q] Can't remove cm12

Hi! I recently installed a cm12 nightly on my nexus 5 and now I can't get rid of it ad return back to stock. I tried using nrt and doing it manually but after everything is finished my device doesn't reboot like it's supposed to, it just stays in fastboot mode and when I manually reboot it it boots into cm again and messages pop up saying that system UI has stopped etc so I can't use the device. I tried using force flash mode in nrt and although it did reboot it rebooted in cm again and the same messages pop up.
Any help is appreciated! Thank you!

Did you restore stock kernel?

.
I thought the google factory image would do that? Do i have to do it manually and if yes how do i do it?

ftsagkris said:
I thought the google factory image would do that? Do i have to do it manually and if yes how do i do it?
Click to expand...
Click to collapse
If you are using WugFreshs NRT you can do this within Advanced Utilities - Fastboot Flash - press Boot (Kernel). Restore stock one and then flash stock image.
You can also try if phone will boot up immediately after you restore kernel. If I remember wright, that is enough.

I should also note that when I try to manually install the factory image manually it successfully installs the bootloader the radio and all the other imgs except the system img. It fails to install that

ftsagkris said:
I should also note that when I try to manually install the factory image manually it successfully installs the bootloader the radio and all the other imgs except the system img. It fails to install that
Click to expand...
Click to collapse
It hapeness somethime, but just try again. It also hapenned to me. So. First select your device with current version of android you are using. Leave NRT to update all necessary files. Restore stock kernel. Flash stock image that you downloaded.
You should be ok.

I tried that. When i asked it to download it manually during hashcheck it said mismatched. So I installed it manually and then tried to factory reset with force flash mode off and it said system img was missing. So I enabled force flash and it said it couldn't load system.img. After that it booted in CM again

ftsagkris said:
I tried that. When i asked it to download it manually during hashcheck it said mismatched. So I installed it manually and then tried to factory reset with force flash mode off and it said system img was missing. So I enabled force flash and it said it couldn't load system.img. After that it booted in CM again
Click to expand...
Click to collapse
Hashcheck of what file?

That happened when I pressed boot(kernel) from advanced option. so it was the hashcheck of boot.img when i asked nrt to automatically download it

ftsagkris said:
That happened when I pressed boot(kernel) from advanced option. so it was the hashcheck of boot.img when i asked nrt to automatically download it
Click to expand...
Click to collapse
Pull boot.img from downloaded factory image and flash it.

zagorteney said:
Pull boot.img from downloaded factory image and flash it.
Click to expand...
Click to collapse
Ok. I have already done that. I tried formatting the device and did everything again. I manually installed everything but when I get to system.img I get an error message saying "cannot load system.img"
I also tried re-downloading the factory image from google's site to make sure that I didn't have any corrupted files but the same problem keeps coming up

ftsagkris said:
Ok. I have already done that. I tried formatting the device and did everything again. I manually installed everything but when I get to system.img I get an error message saying "cannot load system.img"
I also tried re-downloading the factory image from google's site to make sure that I didn't have any corrupted files but the same problem keeps coming up
Click to expand...
Click to collapse
Flash bootloader and radio first. Boot in fastboot. Fastboot flash recovery, boot and system. If this doesn't work I don't know how to help you.
Regards, Zagor

zagorteney said:
Flash bootloader and radio first. Boot in fastboot. Fastboot flash recovery, boot and system. If this doesn't work I don't know how to help you.
Regards, Zagor
Click to expand...
Click to collapse
I have done that several times now and it just won't flash system.img
Thank you very much for your help though.

ftsagkris said:
I have done that several times now and it just won't flash system.img
Thank you very much for your help though.
Click to expand...
Click to collapse
After flashing the bootloader/radio, you need to reboot the bootloader.
This is important.
I will put myself in recovery now.

zagorteney said:
After flashing the bootloader/radio, you need to reboot the bootloader.
Click to expand...
Click to collapse
Thank you. I knew that I have read almost every tutorial I could find online. I just did it on my mac and it worked. I don't know why it would't work on my pc.
Thank you very much for your time though!

ftsagkris said:
Thank you. I knew that I have read almost every tutorial I could find online. I just did it on my mac and it worked. I don't know why it would't work on my pc.
Thank you very much for your time though!
Click to expand...
Click to collapse
No problemo. I didn't do anything, but I really hate that things like that, hapeness to people like you.
I just remembered that I have exactly same situation and resolve it that way. That's why I preffered stock from then on.
Regards, Zagor

Stock OPO softbricked after last OTA update

I know there is another very similar thread that was just opened(http://forum.xda-developers.com/oneplus-one/help/completely-stock-oneplus-one-stuck-t3396207), but his solution didn't help me so I'm making this thread.
I really need to save my internal data, so only as a last resort will I wipe userdata to save my phone.
First of all my phone is completely stock. Locked bootloader, unrooted, stock recovery, and stock rom. Last thursday(June 9th), I got the CM13.1 OTA update which I installed and everything went normal. It finished installing, restarted and booted up, optimized apps, rebooted, but then optimized apps again and again. I thought it might help to just reboot my phone, but it didn't. So I immediately started looking around for solutions.
I can boot into recovery and fastboot mode and since I can boot into recovery I started with wiping cache(Stock Recovery>>Factory reset>>Wipe cache partition). It took ~20mins which seemed like an unusually long time, then I rebooted and it still got stuck in the "optimizing apps/reboot loop". Next, I set up USB drivers, ADB, and fastboot since it seems to be very important to have those set up. I used a few guides to get them properly set up and I checked that they were correct by checking that the cmds "adb devices" and "fastboot devices" returned my device, which they did. I saw someone saying he saved his friends OPO by just ADB sideloading a CM zip file, so it looked hopeful in my case. I downloaded cm 13.0 and 13.1 zip files and tried sideloading them with the cmd "adb sideload cm13.zip". I tried both and they both got to around 50% complete and the install failed. Some of the red text said, "Package expects build fingerprint of oneplus/bacon/A0001:5.1:6.0.1..... & E:Failed to install /sideload/packages.zip ". Next I tried installing TWRP, which looks like it requires an unlocked bootloader to flash it(even to to just boot into it). From all my research it looks like there's no way to unlock the bootloader without wiping data. Even the OPO toolkit says you need to wipe data to unlock your bootloader.
One thing I haven't looked too much into is using fastboot to save my device. This guide http://www.technobuzz.net/fix-bricked-dead-oneplus-one-easily/ shows to flash userdata userdata_64g.img, which I assume wipes userdata.
Maybe I'm just overlooking some simple fix, but if anyone can help me I would be eternally grateful.
Edit: I need my phone working and I'm tired of waiting for help, so I just did a factory rest. Also I've been getting tons of conflicting advice. Thanks everyone for the help anyways

kinda on the same boat here.
may i ask how you set up adb? i cant get it to work

mastersen901 said:
kinda on the same boat here.
may i ask how you set up adb? i cant get it to work
Click to expand...
Click to collapse
download and install the 15 second adb/fastboot installer (http://forum.xda-developers.com/showthread.php?t=2588979)
It'll create a folder: C:/adb, In that folder you can open a cmd prompt window to send cmds to your device through adb/fastboot. that folder is also where you place files that you want to flash or boot into.
Also for the USB drivers just download the oneplus one toolkit, or use this guide: http://www.technobuzz.net/install-oneplus-one-usb-drivers-windows/
the opo toolkit is in the 2nd method

Still looking for help. Phone status: After sideloading cm 12.1 it boots up but I get tons of errors saying com.android.phone failed/ android.system.acore failed which make my phone inoperable, also my phone usually reboots after ~10 seconds after booting up and getting errors.

when you flashed the stock zip via sideloading did you use the full zip or the incremental zip?

itechy said:
when you flashed the stock zip via sideloading did you use the full zip or the incremental zip?
Click to expand...
Click to collapse
The zip I sideloaded was cm-12.1-YOG4PAS1N0-bacon-signed.zip (http://builds.cyngn.com/cyanogen-os...be76f9310/cm-12.1-YOG4PAS1N0-bacon-signed.zip)
I'm pretty sure it's the full zip

woodhaus said:
The zip I sideloaded was cm-12.1-YOG4PAS1N0-bacon-signed.zip (http://builds.cyngn.com/cyanogen-os...e76f9310/cm-12.1-YOG4PAS1N0-bacon-signed.zip)
I'm pretty sure it's the full zip
Click to expand...
Click to collapse
You will have to flash the latest version as performing a downgrade without wiping data will cause issues like the ones you are seeing
Sent from my A0001 using XDA Labs

itechy said:
You will have to flash the latest version as performing a downgrade without wiping data will cause issues like the ones you are seeing
Sent from my A0001 using XDA Labs
Click to expand...
Click to collapse
I can't really find a full cm13.1 zip. On CyanogenMod I only see up to 13.0. I also don't know how to tell the difference between an incremental and full zip D:

woodhaus said:
I can't really find a full cm13.1 zip. On CyanogenMod I only see up to 13.0. I also don't know how to tell the difference between an incremental and full zip D:
Click to expand...
Click to collapse
Visit the support page I grabbed my full update zip from there https://cyngn.com/support
Sent from my A0001 using XDA Labs

itechy said:
Visit the support page I grabbed my full update zip from there https://cyngn.com/support
Sent from my A0001 using XDA Labs
Click to expand...
Click to collapse
Ohh! thanks! I was looking for this!

I just got around to sideloading the cm 13.1 zip. I'm still getting a bootloop /:
Edit: My phone reboots and optimizes apps after getting hung up on the cyanogen boot screen for a while.

I'm in the same situation.
It seems like a cache cleaning is needed but I have no idea whether it possible without a custom recovery and without a full adb support.

hibernick said:
I'm in the same situation.
It seems like a cache cleaning is needed but I have no idea whether it possible without a custom recovery and without a full adb support.
Click to expand...
Click to collapse
You can wipe cache partition in stock recovery also. To boot into recovery mode first power off your device. Press Volume down + Power button together until you see oneplus logo. When device is in recovery mode press volume down and select 'wipe cache partition' and press power button to confirm the action. Reboot after process completes.

saurav007 said:
You can wipe cache partition in stock recovery also. To boot into recovery mode first power off your device. Press Volume down + Power button together until you see oneplus logo. When device is in recovery mode press volume down and select 'wipe cache partition' and press power button to confirm the action. Reboot after process completes.
Click to expand...
Click to collapse
The same like woodhaus I have locked bootloader and there is no USB debug over adb.
I don't have a 'wipe cache partition' in the recovery.
The only things I can use are adb sideload and fastboot.

hibernick said:
The same like woodhaus I have locked bootloader and there is no USB debug over adb.
I don't have a 'wipe cache partition' in the recovery.
The only things I can use are adb sideload and fastboot.
Click to expand...
Click to collapse
I have wipe cache partition but it doesn't seem to do anything. also it takes like 35 minutes to complete

woodhaus said:
I have wipe cache partition but it doesn't seem to do anything. also it takes like 35 minutes to complete
Click to expand...
Click to collapse
How did you do it?
You told you are on stock recovery. Me either and I don't see such option in my recovery.

hibernick said:
How did you do it?
You told you are on stock recovery. Me either and I don't see such option in my recovery.
Click to expand...
Click to collapse
it's under the factory reset option from the main menu on stock recovery
stock recovery>factory reset> erase cache partition

woodhaus said:
it's under the factory reset option from the main menu on stock recovery
stock recovery>factory reset> erase cache partition
Click to expand...
Click to collapse
Oh, thanks. I didn't even go there.

Stuck on TWRP LOGO

Hey I've encountered this issue when my S7 Edge boots up it jumps to twrp but it's stuck on the teamwin logo screen and does not advance to menu.
It occurred when I tried to format the data partition to ext4 via twrp and it stuck there for hours so I rebooted it and now i'm stuck here!
I googled some solutions and few suggested flashing a stock via odin but when i try that it fails, flashing twrp also fails i'm sorta stuck right now.
this post https://forum.xda-developers.com/s7-edge/help/stuck-loading-twrp-t3834144 which is the closest scenario suggested adb flash but i can't seem to uncompress boot.img.lz4 with 7zip zstandard
if you know how or if you guys have fixed this issue before please drop a solution thank you in advance !

Boot to download mode and flash twrp again

kpwnApps said:
Boot to download mode and flash twrp again
Click to expand...
Click to collapse
Thanks for your answer, I have tried this like i mentioned and it does flash with success but when it boots to twrp it's just stuck on the teamwin logo, I have even flashed a newer version and i did notice the version changing in the logo but nothing happens.
EDIT: I ended up flashing a stock rom via odin and somehow it worked this time (I updated the usb drivers & changed the cable)

Dantefesse said:
Thanks for your answer, I have tried this like i mentioned and it does flash with success but when it boots to twrp it's just stuck on the teamwin logo, I have even flashed a newer version and i did notice the version changing in the logo but nothing happens.
EDIT: I ended up flashing a stock rom via odin and somehow it worked this time (I updated the usb drivers & changed the cable)
Click to expand...
Click to collapse
Okay then flash twrp again and in odin select nand erase. Dont worry this doesnt wipe your complete system only userdata

kpwnApps said:
Okay then flash twrp again and in odin select nand erase. Dont worry this doesnt wipe your complete system only userdata
Click to expand...
Click to collapse
doesn't Nand erase everything and you're left with download mode ? and why would I do it if i've managed to fix my previous issue ?

Dantefesse said:
doesn't Nand erase everything and you're left with download mode ? and why would I do it if i've managed to fix my previous issue ?
Click to expand...
Click to collapse
Nand erase all doesnt wip everything. Its a big myth. It is actually erasing userdata partition and if ur issue is fixed never mind

kpwnApps said:
Nand erase all doesnt wip everything. Its a big myth. It is actually erasing userdata partition and if ur issue is fixed never mind
Click to expand...
Click to collapse
nah bro, if his issue is fixed, then he needs to reflash the stock firmware, reflash TWRP, boot into twrp, go into the file manager and delete EVERYTHING on the internal storage.
just to be clear, OP, do NOT do any of that

youdoofus said:
nah bro, if his issue is fixed, then he needs to reflash the stock firmware, reflash TWRP, boot into twrp, go into the file manager and delete EVERYTHING on the internal storage.
just to be clear, OP, do NOT do any of that
Click to expand...
Click to collapse
Yea its just showing you dont understand anything. Erasing userdata partition is enough but yeah you know everything

kpwnApps said:
Yea its just showing you dont understand anything. Erasing userdata partition is enough but yeah you know everything
Click to expand...
Click to collapse
nah dude, just trying to insert some very missing humor here. I see it got a ton of traction with you