Partition error - Nexus 4 Q&A, Help & Troubleshooting

So I went back to stock using wugs toolkit. I then rooted through the toolkit (all on 4.4.2) and it went fine. Then I factory reset to fix the storage issue. I then took to liquidrom files to my phone and the ak caf kernel. I went to boot loader then recovery. Backed up the current os. Then I wiped dalvic cache, cache, and system. Then I flashed both liquids but I got a partition error for both about not being able to update partitions. What do I need to do? I am worried please help
Sent from my Nexus 4 using xda app-developers app

Related

How do I get 4.1.2?

So, I have stock 4.1.1, unlocked with Clockwork. When I downloaded 4.1.2, I went to Clockwork and tried to flash it but I got an error. Now it says my "System is up to date" on 4.1.1. How can I get a 4.1.2 that won't require a wipe on stock? I don't want to wipe and go custom, I like this stock and don't want to screw with it very much.
Sent from my Nexus 7 using xda app-developers app
Errors are typically seen with modified system files or kernel. Depending on what the error says there are a couple ways to resolve the issue.
The most direct options involve flashing the system, kernel, and bootloader from the factory image followed by clearing the cache and dalvik cache. This will not affect user data.
Sent from my Nexus 7 using Tapatalk 2
comminus said:
Errors are typically seen with modified system files or kernel. Depending on what the error says there are a couple ways to resolve the issue.
The most direct options involve flashing the system, kernel, and bootloader from the factory image followed by clearing the cache and dalvik cache. This will not affect user data.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Hi, I have the problem that when I get the OTA, reboot and try flash I get an error. I assume this is because I.could have a modified filesystem.
Edit: I have error because I have CWM and not stock recovery.
Decided not to upgrade to 4.1.2 after reports of loss of sensitivity. I will wait.
=================
Sent from my HTC One X
Google Nexus 7
HTC One X

[Q] Incomplete TWRP Restore

Hello,
I have a Nexus 10 (manta) tablet and made a full nandroid backup 10 days ago of the stock+root Android installation. I did that so I would be able to revert back to it if need be after trying out CM 10.1. I found that CM still required some refinement for manta so I wiped the system, did a factory reset and wiped the dalvic cache, then tried restoring the previous backup I made, of the stock system. The backup folder is 2.46GB big and the /data partition is split between two archives. When restoring, the system partition and first data archive seem to backup properly, but after that, the tablet reboots, omitting the second data archive which is pertinent for me to restore all of my apps.
I've installed the latest TWRP, version 2.4.0.0 just in case there was a bug.
How can I fix this and get my tablet back to normal?
Thanks XDA,
Spike
Note: My tablet isn't bricked, I can still boot to the stock rom after doing the incomplete restore but my apps are incomplete.
Edit: I've just updated TWRP to 2.4.1.0 and get a little farther this time. It begins restoring the second /data archive but still reboots during the process.
I'm currently having this issue. Did you ever get it resolved?
Sent from my Nexus 7 using xda app-developers app
I had the same problem, posted a day ago or so about it, but I used this http://forum.xda-developers.com/showthread.php?t=2121673 and now everything is all good. I just flashed the super wipe zip and then restored and it did NOT reboot during the restore.
Sent from my Nexus 10 using xda app-developers app
I had this problem as well. It was really pissing me off, I think it happens when you have a large backup. Anyways, I just kept trying it, and on the third time it worked for me. Maybe I just got lucky. When restoring it wipes everything anyways, but you can try wiping data, system, and cache beforehand and see if it helps.
Sent from my SCH-I535 using Tapatalk 2
My backups are 10GB+ each(I basically make full images to restore to for each ROM) and I never had this issue in the dozens of restores I've done. I always factory reset, wipe cache/dalvik, and then format system(wipe ROM) in that order before restoring the image. In a worst case scenario you can factory image the tablet if the restore fails after the stock ROM has been wiped.
Also you said two archives? My backups are just 1 folder with the 5 partitions and 5 md5 files?
I had this issue as well, after trying to restore from checking out the Ubuntu preview. Ended up giving up on it and enjoying as best I can the clean install. Would still like to restore it if possible though.
I was "finally" able to do a full restore of a backup. I had to break up the restore process though. First I restored system and boot. Once that restored I restored data and was able to get a full data restore as well.
Sent from my Nexus 7 using xda app-developers app

[Q] OTA update not working

I have a nexus 4 which I rooted successfully and installed cm 10.1 on android 4.2.2 factory. I installed one of the nighty roms last week and it has been working fine.
today I tried to flash the cm-10.1-20130304-EXPERIMENTAL-mako-M2.zip which was an OTA update.
I used the update option in settings and after updating to cm-10.1-20130304-EXPERIMENTAL-mako-M2.zip successfully I wasn't sure what to do,
I knew that I had to install the gapps again but wasn't sure how. So went back to square one, booted into recovery, did a factory reset, cache wipe, delvick cache wipe and reinstalled cm-10.1-20130304-EXPERIMENTAL-mako-M2.zip and then installed the gapp package. After that my my google apps don't work, have done restore with Titanium backup and still not working . Don't know what to do.
I have gone back and wiped cache and delvic cache again and reinstalled the gapps but still none of google apps will run.
should I do a factory reset and start the whole procedure over again and reinstall everything?
Do a full wipe, flash cm10.1 and gapps and I recommend flashin Francis kernel. Make sure its the latest
Sent from my Nexus 4 using xda premium

[Q] Defy does only RSD help ?

Hello,
My Defy red lense was using CM10 from Quarx nightly 30.11. Everything was OK.
Yesterday my signal was lost (I thought RIL bug happened) so i normally reboot it. But booting stopped on cyan logo so i put out battery. After this phone booted almost ok but he stayed on "System updating... Running apps" (I translated this from Polish hope you know what I mean)
So I tried wipe Cache i Davlik and after boot was this application counting stuff and then again stayed on this "System updating...."
So I flashed same CM10 nightly. Wiped cache before and after. But it didn't help. Then I flashed some previous builds same way but nothing helped.
The last thing I did was flashing latest CM10.2 and gapps minimal for it. But still nothing. So right now once boot stop on cyan logo after putting out battery it boots further but stays on "System updating.." I waited long time even once I forgot to check and my phone was warm and battery drains very quickly (but I can charge no problem)
So my question is does only RSD help me or can I somehow revive my defy ?
Sorry for bad English.
System+ data+ cache wipe, and flash cm again
Sent from my MB526 using Tapatalk 4
thekguy said:
System+ data+ cache wipe, and flash cm again
Sent from my MB526 using Tapatalk 4
Click to expand...
Click to collapse
Can I somehow backup sms messages before this ?
Try entering recovery and backup data. Then after flash don't restore from twrp directly use nandroid manager to extract data from it. If backup fails at any point that means the partition was too damaged to yield any useful data.
Sent from my MB526 using Tapatalk 4
thekguy said:
Try entering recovery and backup data. Then after flash don't restore from twrp directly use nandroid manager to extract data from it. If backup fails at any point that means the partition was too damaged to yield any useful data.
Sent from my MB526 using Tapatalk 4
Click to expand...
Click to collapse
Thank you very much for your help.
I have one more question.
In TWRP I pressed Wiped->Advanced wipe-> wipe dalvik, cache, data, system. Then I flashed 10.2 ROM after that gapps for it. No wipes after flashing or between. System booted up fine. It started with Cyan account then I had to enter google account and phone did restoring and everything was great. Even my apps was automatically downloaded. But I bricked again after I installed SuperSU through recovery (needed for Nandroid Manager).
So again I wiped dalvik, cache, data, system. Then flashed like before. But know its only cyan account config and after that just Trebuchet.
I can add Google account manually but it doesn't have restore option.
Can you tell me what more should I wipe to get it like it was at the first time.
For getting it to account restore wipe data
Sent from my MB526 using Tapatalk 4
thekguy said:
For getting it to account restore wipe data
Sent from my MB526 using Tapatalk 4
Click to expand...
Click to collapse
It didn't help. Just cyan account appear and after that Trebuchet shows up.
Are you flashing gapps again? The restore account appears after a clean install(wipe system, data, cache + flash cm and then gapps)
Sent from my MB526 using Tapatalk 4
thekguy said:
Are you flashing gapps again? The restore account appears after a clean install(wipe system, data, cache + flash cm and then gapps)
Sent from my MB526 using Tapatalk 4
Click to expand...
Click to collapse
Yes. I did it like you wrote. In TWRP wipe -> Advanced -> checked system,data,cache,dalvik then Install CM10 and gapps at once (2 zips selected)
No wipes or reboots between ROM and gapps. None reboots after wiping.
Should I reboot after something ? Or wipe between ROM and gapps ?
So what you're saying is that repeating the same procedure, given identical starting points, you're getting different outcomes:what: . I have no idea how that screen is failing to show up, maybe due to full system partition, wrong gapps. I have always been able to restore directly after cm setup even without the elaborate wiping sequence. Not sure why this is happening
Sent from my MB526 using Tapatalk 4
thekguy said:
So what you're saying is that repeating the same procedure, given identical starting points, you're getting different outcomes:what: . I have no idea how that screen is failing to show up, maybe due to full system partition, wrong gapps. I have always been able to restore directly after cm setup even without the elaborate wiping sequence. Not sure why this is happening
Sent from my MB526 using Tapatalk 4
Click to expand...
Click to collapse
Gapps which I used are gapps-CM10.2_ONLY-20130813-minimal_edited_20131023.zip
I don't know if it has any meaning but at first time I didn't have my SIM card inside phone. But later I tried with SIM in and without it.
It looks like android keeps something on SD card or something is not wiped good enough.
I restored the broken ROM and after that I did all the wipe but nothing change. After cyan account Trebuchet welcomes me :/
So next thing I did was wiping data,system,cache,dalvik then I chose factory reset. After that i flashed ROM then right after this flashed gapps (not selecting 2 zips) and after reboot Google restore appeared.
However the apps didn't restore automatically because of this attempts when I add Google manually.
I don't know the exact reason but maybe this thread will help someone.
Thank you for your help.

My device shows less available storage than I know it actually has - after flashing

Hi,
I have a 16GB Nexus 4, running Android 5.1.1 LMY48I. I had recently flashed Google's stock rom (Android 5.1.1 LMY48I) on my Nexus 4. Later, I noticed that my Nexus thinks my internal storage capacity is 5.6 GB, while I know it should be a little less than 16 GB. That was really strange, and I figured that re-flashing stock rom might solve the bug. Unfortunately, my phone still believes I have less storage than I actually have.
I'd be happy if someone could explain why it happened, and more importantly - How I can fix it.
Thank you!
SOVED:
I managed to fix it by formatting the CACHE, SYSTEM and USERDATA partitions, then re-flashing the stock rom. I encountered a bootloop, so I decided to format again only the CACHE and USERDATA. Everything works now.
ido_doron said:
SOVED:
I managed to fix it by formatting the CACHE, SYSTEM and USERDATA partitions, then re-flashing the stock rom. I encountered a bootloop, so I decided to format again only the CACHE and USERDATA. Everything works now.
Click to expand...
Click to collapse
In the future, all you need to do is boot into the stock recovery after flashing the factory image and do a factory reset.
Sent from my Nexus 9 using XDA Free mobile app
I actually did tried this, but from some reason TWRP failed wiping the userdata partition...
ido_doron said:
I actually did tried this, but from some reason TWRP failed wiping the userdata partition...
Click to expand...
Click to collapse
Trwp is not the stock recovery.
Sent from my Nexus 9 using XDA Free mobile app
However, as much as I know, it should be able to wipe cache and user data. I tried to flash the stock recovery, but from some reason all I got is a green Android with exclamation mark on it... By the way, I also tried CWM and it failed too.
I ended up improvising something with ADB...

Categories

Resources