Database Info

Corrupt internal SD Card

Hi Folks.
Ok here is my situation, I have a rooted and unlocked TF700.
I flashed Zeus 4 and all worked well, then flashed (after full wipe) PARANOIDANDROID 2.15 and again everything was great,
Yesterday I flashed Baked Bean 4 (again after a full wipe) and apart from some SD issues all seemed ok,
I then decided to restore my TWRP backup of Zeus as I needed to use my 64gig msd card.
After a full wipe and restore Zeus started up but the dpi was messed up (160) I think (way small)
I was seeing loads of FC's and file manager showed my internal SD as being empty. Rebooted to recovery and tried the "Format Data" option
It failed right away with this message "E: Unable to format data."
I have tried flashing the stock .26 rom via TWRP and I have the same issue, dpi set to 160 and internal sd not mounted.
It seems my Internal sd is corrupt
What is the procedure to reformat it via ADB or fastboot? (I have searched but the results I found relate to other devices and I dont want to simply follow instructions that might cause further harm to my TF700)
I have followed the NVflash brick proof procedure and have all relevant files backed up (I did this before flashing the last 2 roms)
Please can some one point me in the right direction
Thanks a lot
Jules

I always wipe cache, system, internal, davic and then do a factory reset.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app

When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right? What rom you have on your device right now?

Pretoriano80 said:
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right. What rom you have on your device right now?
Click to expand...
Click to collapse
Yip extracted the zip from the zip file and copied it to my ext sd and flashed it via TWRP
I have an unusable Zeus4,
Im about to try a full wipe again and then flash .26 again
EDIT
After flashing .26 and selecting reboot I get the "No OS installed! Are you sure you wish to reboot?" message

Looks like the system partition is corrupted, but i'm not sure. I think you should come here on IRC and maybe someone with more experience will help you - - http://webchat.freenode.net/?channels=asus-transformer

Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:

ZaJules said:
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
Click to expand...
Click to collapse
This same thing happened to me with my Prime when I was getting ready to send it off for RMA because of a broken HDMI port. Since I was unlocked I was advised to restore to stock before sending it in. However, before I got the chance to do that I started getting the "E: Unable to format data." error that you were. I ended up erasing all partitions from fastboot and putting a note in the box that it wouldn't boot after an OTA. I managed to get away with it and wasn't charged for fixing it
For future reference it would be really helpful to know how you fixed this. Did you do something like what is in this thread: http://forum.xda-developers.com/showthread.php?t=1803343.
Did you ever figure out how CM10 messed up your Infinity? I was running CM9 on my Prime when I got this error. Thanks!

It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.

Pretoriano80 said:
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Click to expand...
Click to collapse
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?

paddycr said:
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
Click to expand...
Click to collapse
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.

Pretoriano80 said:
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Click to expand...
Click to collapse
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.

okantomi said:
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
Click to expand...
Click to collapse
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...

Pretoriano80 said:
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Click to expand...
Click to collapse
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.

okantomi said:
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
Click to expand...
Click to collapse
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.

Pretoriano80 said:
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Click to expand...
Click to collapse
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.

okantomi said:
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
Click to expand...
Click to collapse
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...

Pretoriano80 said:
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Click to expand...
Click to collapse
I'm using TWRP 2.2.2.1, I back up boot, system and data only, and I don't use compression.

TF 300T Partitions

Hey there!
I'm hoping that someone can help me out. My nephew who's a wanna-be geek was going to update my ROM (which didn't to be done really, but he wanted to show me what he was able to do). He went and downloaded the latest CM 11, rebooted and went into TWRP 2.7.0.1, did a factory reset, an advanced wipe, and did the Format Data. When he did that, it got stuck in a loop. Nothing happened. He tried to install the ROM he downloaded, and NOTHING! Long story short, by him doing the Format Data, he wiped out my partitions. TWRP, no matter what I try to do tells me it's unable to mount 'data' or 'media' etc. etc. Which is leading me to believe I have no partitions left. I've tried installing the latest update from Asus, and no dice. I've tried restoring backups that I have on my micro SD, and that's not working.
Can someone please help me and tell me how to fix this? Can I get my partitions back? I'm really hoping that I don't have to send this tablet off to Asus in Dallas, TX to have it repaired.
I'm using a loaner tablet from a rental store, hoping I can get my TF 300 fixed.
Any help is deeply and sincerely appreciated.
Omega
Sent from my SM-P600 using Tapatalk

I was about to suggest you look in the correct forum, but I see you posted there as well. Anyway, your partitions are probably okay, they have just been wiped out, that doesn't mean you lost them. Have you tried reflashing the recovery? Were you able to flash anything with said recovery before that? Wiping the partitions in the recovery shouldn't have any effect on the flashing functionality, no matter which partitions were selected (except for sdcard, since that's where the ZIPs are stored), so there might be a problem with the recovery itself. Are you sure you have the correct one for your device?

Duchman said:
I was about to suggest you look in the correct forum, but I see you posted there as well. Anyway, your partitions are probably okay, they have just been wiped out, that doesn't mean you lost them. Have you tried reflashing the recovery? Were you able to flash anything with said recovery before that? Wiping the partitions in the recovery shouldn't have any effect on the flashing functionality, no matter which partitions were selected (except for sdcard, since that's where the ZIPs are stored), so there might be a problem with the recovery itself. Are you sure you have the correct one for your device?
Click to expand...
Click to collapse
Hey there Duchman ...
Thanks for your reply. I have tried reflashing the recovery like you suggested. And after that tried to reinstall CM11.Afterwards reflashing the recovery it says “Unable to mount data." I don't know if I need to flash a more recent version of TWRP, if that would even help.
Before all of this happened I could flash almost any ROM of my choice as long as it was KitKat supported. All of my backups and restores are kept on my micro SD so they aren't accidentally deleted. As far as I know it's the correct version of TWRP. It's worked for me so far, ever since I updated to KitKat.
Sent from my SM-P600 using Tapatalk

Omega Recon said:
Hey there Duchman ...
Thanks for your reply. I have tried reflashing the recovery like you suggested. And after that tried to reinstall CM11.Afterwards reflashing the recovery it says “Unable to mount data." I don't know if I need to flash a more recent version of TWRP, if that would even help.
Before all of this happened I could flash almost any ROM of my choice as long as it was KitKat supported. All of my backups and restores are kept on my micro SD so they aren't accidentally deleted. As far as I know it's the correct version of TWRP. It's worked for me so far, ever since I updated to KitKat.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
You could try flashing a newer recovery first, I think 2.7.1.0 is available for your device. Also try doing a hard reset by cold booting - here's a how-to: https://www.youtube.com/watch?v=oTU38Ewh8qo (wipe the cache afterwards)
If that doesn't help, reverting to stock is probably your best option. Try this: http://forum.xda-developers.com/showthread.php?t=1757077 (be sure to grab the correct firmware and back up your files)
Have you tried installing any other custom ROM? Does it give you the same error when you try to restore your backup?

Here's what I've come across so far. I did the reset, and that did nothing.
Tried to flash the stock version, after a few seconds, TWRP popped up with FAILED.
I've tried flashing Omni ROM. It will flash, load up, and gets stuck at the boot screen or boot animation. This happens with just about every ROM I try to flash.
Been looking for TWRP 2.7.1.0. I'm not seeing it listed on TWRPs site. Where can I get a copy? Thanks!
Sent from my SM-P600 using Tapatalk

Here you go: http://forum.xda-developers.com/showthread.php?t=2772093
Also do try flashing another recovery, PhilZ for instance: http://forum.xda-developers.com/showthread.php?t=2597860
Did you try wiping all of the partitions again?

Re-installing OS after deleting everything in TWRP

Let me start out by saying your help is very much appreciated. I was on stock rom 4.4.2 and really never bothered with updating. I'm rooted(w/unlocked bootloader) and have made backups in TWRP and restored them without issue in the past.
I wanted to try installing the Chroma ROM, but I think i made a mistake by ticking off all the boxes and deleting everything first. I have 2 full backups on my USB-OTG drive along with the Chroma ROM. At the moment, I can't flash the ROM and I cant restore the backups I have on my USB-OTG drive. I try to restore them and it just goes back to the TWRP homescreen after one second. There's no OS, but I can boot into TWRP version 2.6.3.4. I suppose I shouldn't have wiped system before flashing the ROM? Did this happen because I tried flashing the ROM from my USB-OTG that it didn't flash? Should I have kept it on the root my SD Card?
What's the easiest way to get my backup up and running? Do I have to get a factory image back on the device? I'm so lost with what to do next.
Thank you all for your assistance.

Just fastboot the android system img of your choice
Sent from my Android M Nexus 5 yo!

[Q] Bootloop after flashing custom ROM. Fastboot and recovery still working.

Hey, so I just bought a Moto G LTE and got very excited about the amount of dev going on here (coming from an LG Optimus F6 which has almost none). Right way I unlocked the bootloader and rooted. So far so good. Then I flashed TWRP recovery and everything seemed fine. I downloaded the ParanoidAndroid ROM and flashed it, and the phone got stuck in a bootloop (with the PA boot animation). I then went back into recovery, did a reset and flashed BlissPop. Same issue (bootloop is now in the BP boot animation).
So now I'm not sure what to do. I can still get into recovery. I selected factory reset through recovery, and on the top of the screen it says "Factory Reset Complete", but on the log it says "Updating partition details..." and just stays like that. Rebooting just takes me back to the bootloop (still with the BlissPop animation).
Anyone have a clue what could be wrong here? Is there a way to check if there's anything I messed up along the way?
Thanks in advance for any help!

magnoidgoat said:
Hey, so I just bought a Moto G LTE and got very excited about the amount of dev going on here (coming from an LG Optimus F6 which has almost none). Right way I unlocked the bootloader and rooted. So far so good. Then I flashed TWRP recovery and everything seemed fine. I downloaded the ParanoidAndroid ROM and flashed it, and the phone got stuck in a bootloop (with the PA boot animation). I then went back into recovery, did a reset and flashed BlissPop. Same issue (bootloop is now in the BP boot animation).
So now I'm not sure what to do. I can still get into recovery. I selected factory reset through recovery, and on the top of the screen it says "Factory Reset Complete", but on the log it says "Updating partition details..." and just stays like that. Rebooting just takes me back to the bootloop (still with the BlissPop animation).
Anyone have a clue what could be wrong here? Is there a way to check if there's anything I messed up along the way?
Thanks in advance for any help!
Click to expand...
Click to collapse
Hello welcome, i think you will like this device.
First off, what exact version is it? the XT1039, XT1040?
Anyway. To flash a custom ROM you will need to:
Go to TWRP. Select Wipe and then Advanced wipe.
Then you check:
Dalvik Cache
Cache
Data
System
Internal Storage
Usually afrer come from Stock KK to any CM12 based or AOSP ROM from android 5.x you will need to wipe Internal Storage, something that factory Reset just wont do.
Then you will flash/install
Your Prefered ROM (Paranoid Android is great, BlissPop as well. I'm using Euphoria, another great ROM)
Flash the GAAPs (preferable the one who the dev of the ROM you have chosen say to)
And done. Reboot your device.

Pupet_Master said:
Hello welcome, i think you will like this device.
First off, what exact version is it? the XT1039, XT1040?
Anyway. To flash a custom ROM you will need to:
Go to TWRP. Select Wipe and then Advanced wipe.
Then you check:
Dalvik Cache
Cache
Data
System
Internal Storage
Usually afrer come from Stock KK to any CM12 based or AOSP ROM from android 5.x you will need to wipe Internal Storage, something that factory Reset just wont do.
Then you will flash/install
Your Prefered ROM (Paranoid Android is great, BlissPop as well. I'm using Euphoria, another great ROM)
Flash the GAAPs (preferable the one who the dev of the ROM you have chosen say to)
And done. Reboot your device.
Click to expand...
Click to collapse
Hey, thanks so much for the reply!
I'm not sure which exact version it is, is there a way to check without having to boot the phone?
I did the advanced wipe, however now when I click reboot it says "No OS Installed! Are you sure you want to reboot?" Now that I wiped the internal storage how do I flash the ROM (it was saved there and is now deleted)?
Thanks again.

magnoidgoat said:
Hey, thanks so much for the reply!
I'm not sure which exact version it is, is there a way to check without having to boot the phone?
I did the advanced wipe, however now when I click reboot it says "No OS Installed! Are you sure you want to reboot?" Now that I wiped the internal storage how do I flash the ROM (it was saved there and is now deleted)?
Thanks again.
Click to expand...
Click to collapse
You must always put the OS flash zip on a MicroSD card.
How ever you can put the USB cable on the PC at TWRP and it should reconize your phone so you can make a file transfer
YOu have done a nanobackup on a micro SD of your KitKat?
If you can't put the rom on a microSD Card (but i really advise you to do) or your PC wont see your phone on TWRP to copy the ROM there...
There is ADB Push
http://www.themobimag.com/install-rom-using-adb/

Good idea to use a microSD, don't know why I didn't think of that. I re-flashed from the SD and now everything works! Thanks so much for your help, really appreciate it!

magnoidgoat said:
Good idea to use a microSD, don't know why I didn't think of that. I re-flashed from the SD and now everything works! Thanks so much for your help, really appreciate it!
Click to expand...
Click to collapse
No problem m8, hope you enjoy the device

On an unrelated note: the one thing I love about my old phone is the stock music app. Is it possible to port it onto this one? I got the APK but when I try to install it it just says "Application not installed". Does this mean it's not possible to use it?

Pupet_Master said:
Hello welcome, i think you will like this device.
First off, what exact version is it? the XT1039, XT1040?
Anyway. To flash a custom ROM you will need to:
Go to TWRP. Select Wipe and then Advanced wipe.
Then you check:
Dalvik Cache
Cache
Data
System
Internal Storage
Usually afrer come from Stock KK to any CM12 based or AOSP ROM from android 5.x you will need to wipe Internal Storage, something that factory Reset just wont do.
Then you will flash/install
Your Prefered ROM (Paranoid Android is great, BlissPop as well. I'm using Euphoria, another great ROM)
Flash the GAAPs (preferable the one who the dev of the ROM you have chosen say to)
And done. Reboot your device.
Click to expand...
Click to collapse
Sence 7.0 ROM not working on Desire 820 Dual Sim
I followed one post on Dev ROM on this forum.
I tried installing the Sence 7.0 ROM on HTC Desire 820 Dual Sim and it installed without any problems but at the end when it asks for Reboot, phone restarted and got stuck in Bootloop.
Could you please help me resolve this problem?
You help will be really appreciated.

magnoidgoat said:
On an unrelated note: the one thing I love about my old phone is the stock music app. Is it possible to port it onto this one? I got the APK but when I try to install it it just says "Application not installed". Does this mean it's not possible to use it?
Click to expand...
Click to collapse
Prob it is not possible, you can try to make a titaniumbackup with said app, of this app and restore the backup on the new phone
---------- Post added at 04:56 ---------- Previous post was at 04:55 ----------
martin_kry said:
Sence 7.0 ROM not working on Desire 820 Dual Sim
I followed one post on Dev ROM on this forum.
I tried installing the Sence 7.0 ROM on HTC Desire 820 Dual Sim and it installed without any problems but at the end when it asks for Reboot, phone restarted and got stuck in Bootloop.
Could you please help me resolve this problem?
You help will be really appreciated.
Click to expand...
Click to collapse
This is not the HTC desire forum section, so i can't. Sorry

XT1034 Won't boot after re-flashing stock firmware

Ok guys I'm stumped on this one. I got the OTA notification for 5.1 yesterday on my XT1034 and so I decided to preempt any issues I might have and just flash everything back to stock 5.0.2 in order to install the update.
I was able to flash everything fine then went to reboot, got the unlocked bootloader screen and...... nothing. It just stayed on the unlocked bootloader screen. I figured I did something wrong so I reset back to fastboot mode, tried again and sure enough I missed sparsechunk 3. So I tried again, restarted, and.... same thing.
OK then, reset again and reboot into recovery mode. It booted to the Motorola splash screen, ok this is different..... nope still not loading. Reset again and try flashing a custom recovery.
CWM, flashed ok, reset again, Moto splash
TWRP, flashed ok, reset, Moto splash
Philz, flashed, reset, splash
OK.. so I'm clearly doing something wrong. Did some research and tried:
- formatting the cache and userdata partitions
> cache formatted fine, userdata refused to format, not supported for filesystem type 'raw'
- tried flashing again without erasing the partitions
> flashed fine, no change in booting
- tried flashing back to 4.4.4
> flashed fine, no change in booting
- tried flashing all the custom recoveries with 4.4.4, no change
- I found a thread where someone else had a somewhat similar issue, and apparently resolved by unlocking their bootloader
> mines already unlocked, but sure it can't hurt, tried again, but nothing since it's already unlocked
I looked for anyone that had a stock 5.1 image other than the OTA, but couldn't find anything. I gave up on trying stock and looked at some custom roms, but all of them just start with, unlock your bootloader, load a custom recovery and flash the update zip file.
Soooo I'm stumped. I've tried just about everything I can think of. I made backups of everything so I'm not worried about the data I just want a working phone again. I refuse to accept that it's borked at this point since I can still get to fastboot.

OK so, no clue what changed, but I was finally able to boot into recovery, Philz
I wiped and reformatted everything and tried flashing 5.0.2 again
rebooted and it still hung on the bootloader unlocked screen
I'll try flashing Philz again and updating through there

Captains log, startdate much too late oh clock
I reflashed Philz and wiped everything again, then sidloaded CM 12.
I'm just thankful to have a working phone again so I'll go with this for now.

tapman said:
Captains log, startdate much too late oh clock
I reflashed Philz and wiped everything again, then sidloaded CM 12.
I'm just thankful to have a working phone again so I'll go with this for now.
Click to expand...
Click to collapse
Have you tried installing the stock firmware again?
I'm having exactly the same problem, any recovery says it succeeded flashing but when i try to boot it, it goes to stock motorola recovery.

Sorry for being off-topic but what are requirements of receiving OTA?
Stock ROM, stock recovery and a locked or unlocked bootloader?

Umer520 said:
Sorry for being off-topic but what are requirements of receiving OTA?
Stock ROM, stock recovery and a locked or unlocked bootloader?
Click to expand...
Click to collapse
My experience is that you need to be unrooted, unmodified system partition and stock recovery
It's usually much easier to reflash a stock image and update than trying to unroot, uninstall, xposed tweaks, restore original build.prop settings, restore original hosts file, etc

moralesnery said:
Have you tried installing the stock firmware again?
I'm having exactly the same problem, any recovery says it succeeded flashing but when i try to boot it, it goes to stock motorola recovery.
Click to expand...
Click to collapse
I haven't tried reflashing the stock again over CM12, but I was able to find a link for stock 5.1 image, you can try going straight there skipping this whole pain.
Here's a link, you can also find it on the stock firmware sticky post that I can't seem to find anymore
https://www.androidfilehost.com/?fid=24052804347819474

tapman said:
I haven't tried reflashing the stock again over CM12, but I was able to find a link for stock 5.1 image, you can try going straight there skipping this whole pain.
Here's a link, you can also find it on the stock firmware sticky post that I can't seem to find anymore
https://www.androidfilehost.com/?fid=24052804347819474
Click to expand...
Click to collapse
Already tried to flash the full firmware again without luck, after rebooting the phone gets stuck at the Unlocked bootloader warning.
Thanks for the link.

tapman said:
My experience is that you need to be unrooted, unmodified system partition and stock recovery
It's usually much easier to reflash a stock image and update than trying to unroot, uninstall, xposed tweaks, restore original build.prop settings, restore original hosts file, etc
Click to expand...
Click to collapse
Yeah, I'll reflash stock firmware.
Just wanna confirm about bootloader.

Umer520 said:
Yeah, I'll reflash stock firmware.
Just wanna confirm about bootloader.
Click to expand...
Click to collapse
Yeah unlocking your bl doesn't affect ota's

moralesnery said:
Already tried to flash the full firmware again without luck, after rebooting the phone gets stuck at the Unlocked bootloader warning.
Thanks for the link.
Click to expand...
Click to collapse
I think at least in part what my issue was, was that the partition formatting got borked. If you can boot to a custom recovery you can wipe and reformat them. Then you should be able to reflash it normally.
I was just so tired of dealing with my phone at that point so I only tried once and gave up with stock, but I'm pretty sure that's what I need to do to fix it.