Develop Bugs

Can only boot into any 4.3rom ONCE after that any reboots get stuck at Google screen

Anybody else had this issue? I tried it on Shiny Rom and now CM 10.2 nightly. Get in one time with no issues, if I reboot I get stuck at the Google screen. The one way to get the phone usable is to do a completely factory data wipe and start all over.
I'm using TWRP, I've flashed tons of roms and I'm doing it no different than any of them. I do a complete wipe, install CM, GApps, reboot I get in one time. Do a reboot and then get stuck at Google screen.
This happened with both ShinyROM and 10.2 both are 4.3. They both had a valid MD5.
I have flashed PRIMEMD04_Bootloader-signed - One that came from Shiny ROM bootloader-toro-primelc03 - Stock (I believe)
Nothing worked, got the same issue.

GiZiM said:
Anybody else had this issue? I tried it on Shiny Rom and now CM 10.2 nightly. Get in one time with no issues, if I reboot I get stuck at the Google screen. The one way to get the phone usable is to do a completely factory data wipe and start all over.
I'm using TWRP, I've flashed tons of roms and I'm doing it no different than any of them. I do a complete wipe, install CM, GApps, reboot I get in one time. Do a reboot and then get stuck at Google screen.
This happened with both ShinyROM and 10.2 both are 4.3. They both had a valid MD5.
I have flashed PRIMEMD04_Bootloader-signed - One that came from Shiny ROM bootloader-toro-primelc03 - Stock (I believe)
Nothing worked, got the same issue.
Click to expand...
Click to collapse
The only time I get persistent Google screen is when I have a corrupt /userdata partition.
Try running e2fsck on mmcblk0p12 if you have one of those devices that get emmc corruption by changes in sdcard free space.
In case you need more information on this :
1. In TWRP Mount options, unmount Data. The command won't work on mounted partition.
2. In Advanced > Terminal Command, select the /dev/block folder. Then type in
Code:
e2fsck -n mmcblk0p12
("-n" option will cause no changes to your filesystem, it just shows a simulation of the file system correction tool's result.) If the result says the filesystem is "clean", then you have something else to worry about and its not corrupted /userdata.
3. If it starts checking for errors (there's a KILL button while running the command), your filesystem has errors. You can kill it, and then run
Code:
e2fsck -f -C 0 -y mmcblk0p12
(-f is for forced run, -C 0 will give you progress of completion of task, -y will say yes to all prompts (necessary), and mmcblk0p12 is the /userdata partition)
4. Let the command run until you don't see the KILL button (shouldn't be more than a couple of minutes). On running
Code:
e2fsck -n mmcblk0p12
again, it must show you a "clean" filesystem.
5. Just reboot to System. If your /userdata was corrupt, running this will mostly solve your problem.
Damn, I wish I had found such instructions to get over my horrendous time with corrupt partitions over six months from November 2012-April 2013.

Thank you! I will look into this but I would love to fix the cause.
I'm sure this is the issue because I cannot get the phone back into a working state until after doing a full factory wipe.
What would be causing 4.3 roms to corrupt my /userdata? Whatever it is it is happening after the first reboot after I get into the rom.
desktopfusion said:
The only time I get persistent Google screen is when I have a corrupt /userdata partition.
Try running e2fsck on mmcblk0p12 if you have one of those devices that get emmc corruption by changes in sdcard free space.
In case you need more information on this :
1. In TWRP Mount options, unmount Data. The command won't work on mounted partition.
2. In Advanced > Terminal Command, select the /dev/block folder. Then type in
Code:
e2fsck -n mmcblk0p12
("-n" option will cause no changes to your filesystem, it just shows a simulation of the file system correction tool's result.) If the result says the filesystem is "clean", then you have something else to worry about and its not corrupted /userdata.
3. If it starts checking for errors (there's a KILL button while running the command), your filesystem has errors. You can kill it, and then run
Code:
e2fsck -f -C 0 -y mmcblk0p12
(-f is for forced run, -C 0 will give you progress of completion of task, -y will say yes to all prompts (necessary), and mmcblk0p12 is the /userdata partition)
4. Let the command run until you don't see the KILL button. On running
Code:
e2fsck -n mmcblk0p12
again, it must show you a "clean" filesystem.
5. Just reboot to System. If your /userdata was corrupt, running this will mostly solve your problem.
Damn, I wish I had found such instructions to get over my horrendous time with corrupt partitions over six months from November 2012-April 2013.
Click to expand...
Click to collapse

Whatever my phone faces is not limited to 4.3. It has been happening since 4.1. Something to do with the eMMC of the phone itself. Gets corrupt too easily when the decreasing free sdcard space approaches 3 GB. Sometimes a battery pull can also cause it, sometimes a random reboot can cause it. Technically, 4.3 is supposed to solve this issue with TRIM execution in the background, but it hasn't helped me definitively yet.
It has been documented on these forums for this to happen to phones produced in August, September, October 2012.
In my case, I am quite sure that adding and/or deleting files larger than say 500 MB (for example Nandroid backups) causes this problem to happen at any time afterwards without notice (preceded by random reboot straight into stuck Google screen). I guess new ROMs can cause such issues if there is a large amount of app data deleted everytime, but this is just uninformed speculation.
I've setup Tasker profiles to autorun e2fsck through TWRP every morning before I wake up so I don't have these issues while awake. And one more profile to tell me every 8 hours if my sdcard has changed by a lot.
I hope this is all there is to your phone's problem!

Thanks this is very helpful, I will work on this tonight after work and see what I can come up with.
Right now it is showing as CLEAN but i'm running 4.2.2. Is there anything special to go from 4.2.2 to 4.3?
desktopfusion said:
Whatever my phone faces is not limited to 4.3. It has been happening since 4.1. Something to do with the eMMC of the phone itself. Gets corrupt too easily when the decreasing free sdcard space approaches 3 GB. Sometimes a battery pull can also cause it, sometimes a random reboot can cause it. Technically, 4.3 is supposed to solve this issue with TRIM execution in the background, but it hasn't helped me definitively yet.
It has been documented on these forums for this to happen to phones produced in August, September, October 2012.
In my case, I am quite sure that adding and/or deleting files larger than say 500 MB (for example Nandroid backups) causes this problem to happen at any time afterwards without notice (preceded by random reboot straight into stuck Google screen). I guess new ROMs can cause such issues if there is a large amount of app data deleted everytime, but this is just uninformed speculation.
I've setup Tasker profiles to autorun e2fsck through TWRP every morning before I wake up so I don't have these issues while awake. And one more profile to tell me every 8 hours if my sdcard has changed by a lot.
I hope this is all there is to your phone's problem!
Click to expand...
Click to collapse

Nothing special really.
Was the result Clean after a stuck Google logo?
You could pull battery at the stuck logo and go to TWRP and then check if it is clean. If it is indeed clean, then there's something else wrong that is completely different!

I'm going to give it a go tonight when I get home.
1. So pretty much backup everything, do a complete factory wipe of all data.
2. I'll do a adb push of the .zip for the rom and everything.
3. Flash rom and any other packages needed
4. Run that command see if it comes back clean
5. Reboot go into the rom
6. Reboot, if i get stuck at the Google screen run that script if it's not clean just keep running it?
desktopfusion said:
Nothing special really.
Was the result Clean after a stuck Google logo?
You could pull battery at the stuck logo and go to TWRP and then check if it is clean. If it is indeed clean, then there's something else wrong that is completely different!
Click to expand...
Click to collapse

It's running, it says "clone multiply-claimed blocks? <yes>"
How long does this normally run?
Edit: Running now for 4hrs

GiZiM said:
It's running, it says "clone multiply-claimed blocks? <yes>"
How long does this normally run?
Edit: Running now for 4hrs
Click to expand...
Click to collapse
Hey, sorry.
4 hours?! I've not had it run for more than 2 minutes, ever!
Did you run the -n option and let it say whether there is a corrupt partition? If yes then there may be a problem with the eMMC since its taking so long.
As a last resort, you could go completely stock via fastboot. [Formats /userdata partition, erases SDcard as well - take backup]

Lifesaving string of code.
desktopfusion said:
The only time I get persistent Google screen is when I have a corrupt /userdata partition.
Try running e2fsck on mmcblk0p12 if you have one of those devices that get emmc corruption by changes in sdcard free space.
In case you need more information on this :
1. In TWRP Mount options, unmount Data. The command won't work on mounted partition.
2. In Advanced > Terminal Command, select the /dev/block folder. Then type in
Code:
e2fsck -n mmcblk0p12
("-n" option will cause no changes to your filesystem, it just shows a simulation of the file system correction tool's result.) If the result says the filesystem is "clean", then you have something else to worry about and its not corrupted /userdata.
3. If it starts checking for errors (there's a KILL button while running the command), your filesystem has errors. You can kill it, and then run
Code:
e2fsck -f -C 0 -y mmcblk0p12
(-f is for forced run, -C 0 will give you progress of completion of task, -y will say yes to all prompts (necessary), and mmcblk0p12 is the /userdata partition)
4. Let the command run until you don't see the KILL button. On running
Code:
e2fsck -n mmcblk0p12
again, it must show you a "clean" filesystem.
5. Just reboot to System. If your /userdata was corrupt, running this will mostly solve your problem.
Damn, I wish I had found such instructions to get over my horrendous time with corrupt partitions over six months from November 2012-April 2013.
Click to expand...
Click to collapse
Holy mother of god.
This was a lifesaving string of code. I was convinced that I was going to have to buy a brand new phone. Kudos to you DesktopFusion. Thanks a lot!

Explanation as to why a corrupt userdata partition causes this issue
So, in case anybody was wondering, I would like to explain how I see the issue at hand (corrupt userdata partition).
Upon first boot, the ROM is getting set up and doesn't have any orders to check /userdata because well, there is none on the device. So why waste precious time being redundant (smart coders, right?). So the userdata partition is not checked.
However, now that the second boot is being performed, there is, by default in the system's repertoir, data put in by the user, so the bootloader is told to check the partition containing user data. Since the partition is corrupt, and the free space is technically "modified", it errors up and gets stuck.
I could be wrong, I'm not a developer of any sorts. Just a dude giving my point of view.

I got this trouble too last night. I'm flashing elia's 4.3 custom rom with under 5 gb free space. Got it boot twice,then got stuck at google's logo after trying flashing slim bean gapps. Flashing whole 4.3 stock firmware finally solve this. Maybe there is correlation between upgrading from 4.2.2 without upgrading the bootloader with this problem.
Sent from my Galaxy Nexus using Tapatalk 4

It ended up running for 6hrs and never finished, I did do the -n and it said it was CLEAN but still could not boot into the 4.3 ROM.
So ran it any way for 6hrs and no change as of right now I am unable to boot into ANY 4.3 ROM.
If eMMC was screwed up why can 4.2.2 roms work fine but not 4.3 roms? what's the difference?
desktopfusion said:
Hey, sorry.
4 hours?! I've not had it run for more than 2 minutes, ever!
Did you run the -n option and let it say whether there is a corrupt partition? If yes then there may be a problem with the eMMC since its taking so long.
As a last resort, you could go completely stock via fastboot. [Formats /userdata partition, erases SDcard as well - take backup]
Click to expand...
Click to collapse

BUMP still no 4.3 love

GiZiM said:
BUMP still no 4.3 love
Click to expand...
Click to collapse
Still not resolved?
Have you tried flashing completely stock factory image via fastboot?
Consider checking your flash memory with this app, "eMMC Brickbug Check"
Could you also put in here what Type and Date the eMMC chip was made as per the application?

desktopfusion said:
Still not resolved?
Have you tried flashing completely stock factory image via fastboot?
Consider checking your flash memory with this app, "eMMC Brickbug Check"
Could you also put in here what Type and Date the eMMC chip was made as per the application?
Click to expand...
Click to collapse
Sane chip
Ran memory check no issues
Type: SEM32G
Date: 10/2011
FW: 0x90

GiZiM said:
Sane chip
Ran memory check no issues
Type: SEM32G
Date: 10/2011
FW: 0x90
Click to expand...
Click to collapse
Rats. Falling short of ideas.
I might have missed your answer on whether you've tried flashing a stock Nexus image through fastboot, though.

I had basically the same problem coming from 4.2.2 to 4.3. I'm not sure if it was the bootloader upgrade, 4.3 CM alpha from early August, or the small amount of free space under 5GB, but it was definitely userdata corruption like desktopfusion is saying. I was finally able to fix the problem after a "fastboot -w" userdata and cache*format. This has to be done in fastboot, so hook your computer to your phone in twrp, run "adb pull /sdcard "drive:\pc_backup_location"" to backup your sdcard data (grab what you can if errors come up from badly named or corrupted files). Make sure you got md5verified recovery & bootloader images renamed to recovery.img & bootloader.img, and a rom.zip in your adb folder on the computer. Reboot to bootloader, still connected. **And make sure you're not forgetting any sdcard backup, or twrp backup if still functional, before this erase and format. Run "fastboot -w". Then "fastboot flash recovery recovery.img" and you should be good to reboot, adb transfer ROM.zip and other files to fresh sdcard, etc. There's info on this around to double check, and I just posted a little more detailed walkthrough on this a couple days ago. This definitely saved me though with an identical problem, so if the emmc error check doesn't pan out, I would give this a try. May the fastboot gods be with you.
@desktopfusion -Thanks for your post on the previous page! Copied and saved to mygiant android useful infos text file ... which will one day end up corrupting my userdata partition with my luck.

7175 said:
I had basically the same problem coming from 4.2.2 to 4.3. I'm not sure if it was the bootloader upgrade, 4.3 CM alpha from early August, or the small amount of free space under 5GB, but it was definitely userdata corruption like desktopfusion is saying. I was finally able to fix the problem after a "fastboot -w" userdata and cache*format. This has to be done in fastboot, so hook your computer to your phone in twrp, run "adb pull /sdcard "drive:\pc_backup_location"" to backup your sdcard data (grab what you can if errors come up from badly named or corrupted files). Make sure you got md5verified recovery & bootloader images renamed to recovery.img & bootloader.img, and a rom.zip in your adb folder on the computer. Reboot to bootloader, still connected. **And make sure you're not forgetting any sdcard backup, or twrp backup if still functional, before this erase and format. Run "fastboot -w". Then "fastboot flash recovery recovery.img" and you should be good to reboot, adb transfer ROM.zip and other files to fresh sdcard, etc. There's info on this around to double check, and I just posted a little more detailed walkthrough on this a couple days ago. This definitely saved me though with an identical problem, so if the emmc error check doesn't pan out, I would give this a try. May the fastboot gods be with you.http://forum.xda-developers.com/images/smilies/highfive.gif
@desktopfusion -Thanks for your post on the previous page! Copied and saved to mygiant android useful infos text file ... which will one day end up corrupting my userdata partition with my luck.
Click to expand...
Click to collapse
7175 nailed it. I tried flashing all sorts of different ROMs/gapps/Super SU combinations and tried different wipes/formats to no avail. I wish I would have found the instructions to "fastboot cleanse" the phone 4 or 5 hours ago. I have been reading through forums for several hours today and every suggested fix failed. 7175's fix was spot on for me. My phone was locking up at the Google screen with the lock every time I rebooted after installing a 4.3 ROM.
:highfive:

7175 said:
I had basically the same problem coming from 4.2.2 to 4.3. I'm not sure if it was the bootloader upgrade, 4.3 CM alpha from early August, or the small amount of free space under 5GB, but it was definitely userdata corruption like desktopfusion is saying. I was finally able to fix the problem after a "fastboot -w" userdata and cache*format. This has to be done in fastboot, so hook your computer to your phone in twrp, run "adb pull /sdcard "drive:\pc_backup_location"" to backup your sdcard data (grab what you can if errors come up from badly named or corrupted files). Make sure you got md5verified recovery & bootloader images renamed to recovery.img & bootloader.img, and a rom.zip in your adb folder on the computer. Reboot to bootloader, still connected. **And make sure you're not forgetting any sdcard backup, or twrp backup if still functional, before this erase and format. Run "fastboot -w". Then "fastboot flash recovery recovery.img" and you should be good to reboot, adb transfer ROM.zip and other files to fresh sdcard, etc. There's info on this around to double check, and I just posted a little more detailed walkthrough on this a couple days ago. This definitely saved me though with an identical problem, so if the emmc error check doesn't pan out, I would give this a try. May the fastboot gods be with you.
@desktopfusion -Thanks for your post on the previous page! Copied and saved to mygiant android useful infos text file ... which will one day end up corrupting my userdata partition with my luck.
Click to expand...
Click to collapse
Thanks for this...
First thought it was an issue with SlimRom, tried different kernels, problem wouldn't go away, then realised it was happening with every rom I flashed...

[Q] /data partition keeps getting corrupted

As the title says, the /data partition keeps getting corrupted on my SGH-i317 (AT&T model). It manifests itself as random lockups and reboots, eventually ending up in a no-boot condition. At this point I boot into Philz recovery and use an adb shell to run e2fsck, which fixes a bunch of things and then I can boot normally. This has happened three times in the last month. The first time it happened I was running CleanROM JB, and at that point I upgraded to dicksteele's DS-NE5v1, so I don't think the ROM is to blame. Any idea what could be doing this and/or how to prevent it? Could it be that the FLASH ram is failing? Is there a way to force an fsck at every boot?

Perhaps I spoke too soon...the phone locked up on me last night while we were both asleep (i.e. I woke up, the phone didn't, so I had to yank the battery). The first thing I did was an e2fsck, and it was clean, which leads me to think that the lockups are causing the corruption instead of the other way around.
A little more history: when I was on CleanROM there were no random lockups or reboots, it was a particular app that caused them when I would run it. I tried to uninstall that app, which caused more lockups/reboots, then becoming reboots just opening the Application Manager or trying to uninstall it with Titanium Backup, eventually ending up in a no-boot scenario. After a couple day's worth of pulling my hair out trying to install various recoveries and flashing new ROMs, I determined that it was a corrupted /data partition, found an article on how to e2fsck it and ended up on DS-NE5v1 (the last ROM I tried in the previous step). At that point I had random lockups/reboots until it eventually went no-boot again after a couple weeks. I've since gone through the same cycle twice, having to run an e2fsck to get it booting again.
Any ideas how to diagnose the random lockups?

I am no longer amused: the thing locked up on me again last night, but rebooted just fine after I yanked the battery. Just now it rebooted while sitting untouched on my desk, then rebooted again and locked up at the animated Samsung logo. The e2fsck said this:
Code:
e2fsck -fy /dev/block/mmcblk0p16
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 377887 has zero dtime. Fix? yes
Inodes that were part of a corrupted orphan linked list found. Fix? yes
Inode 378413 was part of the orphaned inode list. FIXED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(1433114--1433116) -1509879
Fix? yes
Free blocks count wrong for group #43 (22311, counted=22314).
Fix? yes
Free blocks count wrong for group #46 (11952, counted=11953).
Fix? yes
Free blocks count wrong (1075855, counted=1075859).
Fix? yes
Inode bitmap differences: -377887 -378413
Fix? yes
Free inodes count wrong for group #46 (5787, counted=5789).
Fix? yes
Free inodes count wrong (712361, counted=712363).
Fix? yes
/dev/block/mmcblk0p16: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p16: 24917/737280 files (3.6% non-contiguous), 1871209/2947068
blocks
Has anyone seen this behaviour before in DS-NE5v1 or any other ROM?

Mostlyhrmlss said:
I am no longer amused: the thing locked up on me again last night, but rebooted just fine after I yanked the battery. Just now it rebooted while sitting untouched on my desk, then rebooted again and locked up at the animated Samsung logo. The e2fsck said this:
Code:
e2fsck -fy /dev/block/mmcblk0p16
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 377887 has zero dtime. Fix? yes
Inodes that were part of a corrupted orphan linked list found. Fix? yes
Inode 378413 was part of the orphaned inode list. FIXED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(1433114--1433116) -1509879
Fix? yes
Free blocks count wrong for group #43 (22311, counted=22314).
Fix? yes
Free blocks count wrong for group #46 (11952, counted=11953).
Fix? yes
Free blocks count wrong (1075855, counted=1075859).
Fix? yes
Inode bitmap differences: -377887 -378413
Fix? yes
Free inodes count wrong for group #46 (5787, counted=5789).
Fix? yes
Free inodes count wrong (712361, counted=712363).
Fix? yes
/dev/block/mmcblk0p16: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p16: 24917/737280 files (3.6% non-contiguous), 1871209/2947068
blocks
Has anyone seen this behaviour before in DS-NE5v1 or any other ROM?
Click to expand...
Click to collapse
More than likely, there is a way to run the command as a script at boot. You can run just about anything as a script at boot using script manager & terminal emulator.
However, have you checked your chip? Some of them had SDS (Sudden Death Syndrome, aka Brick Bug) as I'm sure you're aware. There's an app called eMMC Brickbug Check you can use to check your chip.
Also, when was the last time you formatted data in recovery? Are you getting any errors like UIDs inconsistent or anything?
I don't know much about the e2fsck, but I'm sure if I were to run it right now on my perfectly running phone, it would return similar results. Honestly, IMO, random reboots, crashes, and boot failure sounds like a kernel problem to me. I don't know if you've tried yet, but it might be worth it to try a different kernel.

Without exception, the e2fsck comes back clean when the thing will boot, comes back dirty when it won't, and always boots afterwards. The check needs to be done with the partition unmounted. Since any script would be run from the /system tree, the /data partition would have to be mounted in order to read the script in the first place. Reminds me of something about a chicken and an egg
I formatted the partition when I installed DS-NE5v1, a couple months ago, right before the random problems started.
The eMMC Brickbug came back clean with a sane chip. I did notice that it reported the model as t0lteuc, it is a t0lteatt. Is that anything to be worried about?
The kernel is AGNi 3.0.101-India-v4.2.3_R2-OC-LTE-KitKat. Is there something better?

Mostlyhrmlss said:
Without exception, the e2fsck comes back clean when the thing will boot, comes back dirty when it won't, and always boots afterwards. The check needs to be done with the partition unmounted. Since any script would be run from the /system tree, the /data partition would have to be mounted in order to read the script in the first place. Reminds me of something about a chicken and an egg
I formatted the partition when I installed DS-NE5v1, a couple months ago, right before the random problems started.
The eMMC Brickbug came back clean with a sane chip. I did notice that it reported the model as t0lteuc, it is a t0lteatt. Is that anything to be worried about?
The kernel is AGNi 3.0.101-India-v4.2.3_R2-OC-LTE-KitKat. Is there something better?
Click to expand...
Click to collapse
Well as for agni, 4.23 is kinda old. I know he's since put out 4.24 and 4.25 for our note 2. A new onewith multiroom support was released today so I'll be testing that. To me the most stable versions are 4.24 and 4.25. But if you flash a new kernel be sure to wipe your init.d folder or you will have issues. I do it even when updating the same kernel just to be sure.
As for the build prop I'm not sure what tolteuc is, that is clearly a different country code... but i dont think it's a problem. International would be toltexx and at&t is tolteatt. But that's a rom thing, like mine currently has an s5 build prop so mine says klteatt and kltexx. If you're concerned about it, you can dig into your build prop and the files in your CSC folder. Sometimes these have conflicting information in them which can be a problem (but usually isn't)... sometimes people need to get correct CSC for their country or device and if they're having problems it can help to set the build prop to your original defaults (after making a backup, of course).
Running that command fixes whatever problems your having temporarily. Ok well that's good but you don't want to be running it all the time either. The best way in this case to test your memory & chip without replacing it or running a command constantly would be to Odin back to stock for a little while to see if it's still a problem.
Imo, you can start seeing problems on one rom and despite wiping & wiping, it can still carry over to any subsequent roms you flash. When you see a certain problem consistently, you need to take it back to stock because that's the only way to reset everything back to a clean slate... and if you still have the problem there & then you know it's probably hardware. However, I think it'll resolve whatever is causing these issues and you will be free to flash whatever you want after that. It's worth a try, better than trying to run a script at boot every boot.
This is all just my opinion and what I would do. I just saw that no one had helped you yet and that shouldn't happen here when you have a legitimate concern and you post in the correct section as you did.

I put in AGNi 4.2.8 today, and it crashed within an hour. I see a stock flash in my future...
BTW, perusing the AGNi Control app I found an option for FileSystems Checking on Boot, which is off by default. I don't suppose it could hurt, am going to try it.
Oh, and I really do appreciate the help...was beginning to think I was talking to myself

Mostlyhrmlss said:
I put in AGNi 4.2.8 today, and it crashed within an hour. I see a stock flash in my future...
BTW, perusing the AGNi Control app I found an option for FileSystems Checking on Boot, which is off by default. I don't suppose it could hurt, am going to try it.
Oh, and I really do appreciate the help...was beginning to think I was talking to myself
Click to expand...
Click to collapse
Lol I was surprised no one had helped yet! Yeah try the check file system setting, if you still have issues, try a stock flash. It's always helped me in the past. Too bad the new agni didn't solve it on its own... but hey maybe that check setting will help. I'm sure you'll get it sorted!

I did the stock flash and everything seems good, no crashes for a couple of days now. Thanks for your help!

Mostlyhrmlss said:
I did the stock flash and everything seems good, no crashes for a couple of days now. Thanks for your help!
Click to expand...
Click to collapse
That's excellent news! Glad to hear it!

boot into recovery without touchscreen

Hi guys.
I am a noob in device flashing and stuff, my knowledge is limited to installing Cyanogenmod following the manual.
So the task is challenging for me: digitizer broke on my Wildfire S and all I want is to backup contacts (there was no sync with google). The device was in pristine state (usb debugging off, usb charge only). So my plan was to install Clockwork recovery, make a full backup on SD card and then fetch the contacts from that image somehow. However, I haven't succeded so far and probably destroyed the data. But maybe there is still a hope!
I was able to flash CWM via fastboot and it went ok. However, the phone won't boot into recovery hanging on htc logo. Probably bootloader is incompatible with CWM? But I haven't found any manuals on bootloader-recovery compatibility. Maybe you guys know how to make a recovery boot?
Thank you!
*** UNLOCKED ***
MARVEL PVT SHIP S-ON RL
HBOOT-1.09.0099
CWM 5.0.2.0-saga
PS the phone boots fine into normal mode but the screen seem a bit wierd: the calendar widget and desktop icons are gone (see attachment).

From where did you get the recovery?

aWFSuser said:
From where did you get the recovery?
Click to expand...
Click to collapse
From clockworkmod.com/rommanager, link to image: download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.8-marvel.img

gaga666 said:
From clockworkmod.com/rommanager, link to image: download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.8-marvel.img
Click to expand...
Click to collapse
That should work. You can try
http://forum.xda-developers.com/showthread.php?t=2312904
or
http://forum.xda-developers.com/showthread.php?t=2605331

aWFSuser said:
That should work. You can try
http://forum.xda-developers.com/showthread.php?t=2312904
or
http://forum.xda-developers.com/showthread.php?t=2605331
Click to expand...
Click to collapse
I tried it again and it worked!!
Probably flashing gone wrong the previous time. However, I'm still unable to extract contacts: the database seems to be empty. I opened data.yaffs2.img generated by CWM with Yaffey, exported com.android.providers.contacts/databases/contacts2.db which is 129kb and opened it with sqlite browser. All tables are either empty or consist of 1 row (I checked tables contacts, raw_contacts, data and some more. Maybe HTC stores contacts elsewhere?

gaga666 said:
I tried it again and it worked!!
Probably flashing gone wrong the previous time. However, I'm still unable to extract contacts: the database seems to be empty. I opened data.yaffs2.img generated by CWM with Yaffey, exported com.android.providers.contacts/databases/contacts2.db which is 129kb and opened it with sqlite browser. All tables are either empty or consist of 1 row (I checked tables contacts, raw_contacts, data and some more. Maybe HTC stores contacts elsewhere?
Click to expand...
Click to collapse
Have you tried this - http://dorimanx.suckup.de/dorimanx-kernel-for-sg2-i9100/howto-sqlite-android-app-databases/
Android may store data in a format not understandable by all browser.

aWFSuser said:
Have you tried this - http://dorimanx.suckup.de/dorimanx-kernel-for-sg2-i9100/howto-sqlite-android-app-databases/
Android may store data in a format not understandable by all browser.
Click to expand...
Click to collapse
Yes, I tried console sqlite3 in Ubuntu as well. Select shows nothing and SELECT count(name) FROM view_v1_phones yields 0

aWFSuser said:
Have you tried this - http://dorimanx.suckup.de/dorimanx-kernel-for-sg2-i9100/howto-sqlite-android-app-databases/
Android may store data in a format not understandable by all browser.
Click to expand...
Click to collapse
I also uploaded the database to dropbox (I'm pretty sure it's empty, just in case someone could point out it's corrupted or it's the wrong database): https://www.dropbox.com/s/2t5sqlefos5717p/contacts2.db?dl=0

unable to backup data on twrp

Hello everyone, today while trying to do backup in twrp, I am continuously getting the error message as "createTarFork() process ended with ERROR: 255
Backup Failed.". I tried some solutions mentioned in the forums, but they seem to be having error with different folder. In the log I found that there is error in opening webviewgoogle, but I couldn't found that folder anywhere.
Invalid encryption mode 'ice:aes-256-cts'
Backing up System...
Invalid encryption mode 'ice:aes-256-cts'
Error opening: '/system/app/WebViewGoogle' (Structure needs cleaning)
I:Error in Generate_TarList!
Error creating backup.
I used codeworkx and Blu spark twrp and both seems to have the same issue. Kindly help me in doing a backup. Thanks in advance.

I use blue spark and the copy does it well but restoring a backup gives me an error because I can not mount the system and I also get the phrase that the system needs to be cleaned ... By when a functional twrp???

Princeland said:
I use blue spark and the copy does it well but restoring a backup gives me an error because I can not mount the system and I also get the phrase that the system needs to be cleaned ... By when a functional twrp???
Click to expand...
Click to collapse
I just skipped the back up and did format the data and clean installed the ROM and it worked. Earlier I was unable to restore due to mount system error but I just clicked the system in advanced->mount in twrp and restore the old backup...

Try deleting all paralell apps under the apps Section

galaxy s4 nutjob said:
Try deleting all paralell apps under the apps Section
Click to expand...
Click to collapse
It's not related to parallel apps. I checked this one already.

I had this problem a couple weeks ago:
So the first thing you do to fix the system partition not mounting is to download this tool: https://androidfilehost.com/?a=show&w=files&flid=38683
Tool looks like this: https://i.imgur.com/04L1h9b.png
Step one: Install drivers. Should be straightforward.
Step two: Make sure you device is connected. It detects it in fastboot and everything just press the refresh button a couple of times. In this case you're best off starting in fastboot mode.
Step three: Erase all data / Decrypt internal storage. https://i.imgur.com/2HZN1jK.png
Step four: Flash twrp. Make sure to select your device in the dropdown list. Then select recovery flasher and flash the one shown in screengrab. https://i.imgur.com/80N32db.png
Step five: reboot into recovery and flash what ever you want.
This tool is extremely usefull and quite timesaving. Make sure you explore it's features.
Note: I do not own the tool nor do I know the dev.
Happy to help

pinnekeshaar said:
Step three: Erase all data
Click to expand...
Click to collapse
Seriously, every time I read this, I think to myself, what sort of a pure evil person may hide behind such a malevolent advice?
Really, what's wrong with you, man? Were you, like, tortured as a child? Your loved ones murdered?
To give this sort of advices to people who want to god damn it BACKUP (that means, save and protect, not erase) their data.

lockywolf said:
Seriously, every time I read this, I think to myself, what sort of a pure evil person may hide behind such a malevolent advice?
Really, what's wrong with you, man? Were you, like, tortured as a child? Your loved ones murdered?
To give this sort of advices to people who want to god damn it BACKUP (that means, save and protect, not erase) their data.
Click to expand...
Click to collapse
Well I guess you've been right on time with your part of the advice. You know, three months later. Also, some people have brains and can think of the fact they need to backup their stuff before deleting everything.

Three months later I found this thread in Google.
And also, just in case, the thread is exactly about making backups.

Need a little help, please ....

I rebooted in to recovery (B partition) from custom ROM , ran Migrator Magisk module twice (as directions say-second run does FDR), booted into A partition of my Pixel XLto flash new ROM and for some reason EVERYTHING is encrpyted (do not have screen lock or pin applied) ..... I remember seeing something like this when I first got the device but cant recall how to deal with it.
Every attempt to adb sideload, adb push , etc not working ....

C.Hatfield said:
I rebooted in to recovery (B partition) from custom ROM , ran Migrator Magisk module twice (as directions say-second run does FDR), booted into A partition of my Pixel XLto flash new ROM and for some reason EVERYTHING is encrpyted (do not have screen lock or pin applied) ..... I remember seeing something like this when I first got the device but cant recall how to deal with it.
Every attempt to adb sideload, adb push , etc not working ....
Click to expand...
Click to collapse
So, I take it you were trying to 'migrate' to another ROM?
My suggestion is this, use this guide: https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3825866/
- Start fresh
- Do #4 'wipe data'

was just using the magisk migrator module - it backed up all my files on 1st run, then 2nd run it did FDR .... I would REALLY prefer not wiping my internal/sdcard ..... everything is still there but encrypted, unusable for the moment - hoping there is a workaround bc Ihave sooo much data that I havent backed up externally/cloud for a month or 3 .... got nothing I can boot from as well as no access to ALL the tons of stuff stored on my phone to flash .... was thinking to use Factory image but removing the [-w] from the bat file ..... would that work to keep my data integrity ?

Honestly, im wondering how things got encrypted when the process (xc for what im unsure the mod did extra besides FDR) is practically, if not identical, to the normal protocol for wiping>flashing for PIXEL XL

C.Hatfield said:
was just using the magisk migrator module - it backed up all my files on 1st run, then 2nd run it did FDR .... I would REALLY prefer not wiping my internal/sdcard ..... everything is still there but encrypted, unusable for the moment - hoping there is a workaround bc Ihave sooo much data that I havent backed up externally/cloud for a month or 3 .... got nothing I can boot from as well as no access to ALL the tons of stuff stored on my phone to flash .... was thinking to use Factory image but removing the [-w] from the bat file ..... would that work to keep my data integrity ?
Click to expand...
Click to collapse
...would that work to keep my data integrity ? Yes

will the modded flash-all.bat actually work with all the contents of the internal drive being encrypted?
I only ask bc of all the research Ive been doing for the last 4 hours, I had no idea that the current TWRP [3.2.3.1] made decryption on PIe possible .... I not ref to the PIN/lockscreen/Fingerprint decrypt either > more like decrypting the System partition like with Shamu/N6
**Also** found this during my harried research:
Encrypting does not completely delete the files, but the factory reset process gets rid of the encryption key. As a result, the device has no way it can decrypt the files and, therefore, makes data recovery extremely difficult.

C.Hatfield said:
will the modded flash-all.bat actually work with all the contents of the internal drive being encrypted?
I only ask bc of all the research Ive been doing for the last 4 hours, I had no idea that the current TWRP [3.2.3.1] made decryption on PIe possible .... I not ref to the PIN/lockscreen/Fingerprint decrypt either > more like decrypting the System partition like with Shamu/N6
**Also** found this during my harried research:
Encrypting does not completely delete the files, but the factory reset process gets rid of the encryption key. As a result, the device has no way it can decrypt the files and, therefore, makes data recovery extremely difficult.
Click to expand...
Click to collapse
Yes!
Yes, twrp-3.2.3-1 decrypts.
"**Also** found this during my harried research:
Encrypting does not completely delete the files, but the factory reset process gets rid of the encryption key. As a result, the device has no way it can decrypt the files and, therefore, makes data recovery extremely difficult."
Where did you find that? Link please.

Homeboy76 -
Very much appreciate the feedback !! This is the longest downtime I've experienced, likely-ever but I just couldn't make another move until I was certain it was the correct one.
Here is the link where I found the above info you asked about:
https://android.stackexchange.com/questions/149219/android-decrypt-sd-card-after-factory-reset?rq=1

C.Hatfield said:
Homeboy76 -
Very much appreciate the feedback !! This is the longest downtime I've experienced, likely-ever but I just couldn't make another move until I was certain it was the correct one.
Here is the link where I found the above info you asked about:
https://android.stackexchange.com/questions/149219/android-decrypt-sd-card-after-factory-reset?rq=1
Click to expand...
Click to collapse
Edit: Wrong link, it happens.

this is what it shows me:
It is in the default factory reset state ( like a new device ). You can't decrypt the device even if you wish to as the encryption password (generated from a combination of user lock screen PIN and encryption algorithm ) is lost
From Android's Factory Reset Does Not Wipe Your Data: Here's The Solution
Encrypting does not completely delete the files, but the factory reset process gets rid of the encryption key. As a result, the device has no way it can decrypt the files and, therefore, makes data recovery extremely difficult.

C.Hatfield said:
this is what it shows me:
It is in the default factory reset state ( like a new device ). You can't decrypt the device even if you wish to as the encryption password (generated from a combination of user lock screen PIN and encryption algorithm ) is lost
From Android's Factory Reset Does Not Wipe Your Data: Here's The Solution
Encrypting does not completely delete the files, but the factory reset process gets rid of the encryption key. As a result, the device has no way it can decrypt the files and, therefore, makes data recovery extremely difficult.
Click to expand...
Click to collapse
Yes, if you use this url: https://www.techtimes.com/amp/artic...oes-not-wipe-your-data-heres-the-solution.htm but that is not the url that was in your previous post. This is, https://android.stackexchange.com/questions/149219/android-decrypt-sd-card-after-factory-reset?rq=1
I think it is out dated: Android's Factory Reset Does Not Wipe Your Data: Here's The Solution By Anu Passary | May 27, 2015 11:07 PM EDT

hey homeboy76 tried the flash-all bat [-w removed] and the process went through w/o any issues but it immediately rebooted itself and within 30 seconds landed on the stock recovery & it said file may be corrrupt, TRY AGAIN or FDR ....
Do I have any other recourse to save my 100 GBs of data ??? or do I onlly have the unmoddded flash-all -w to do at this point ?

C.Hatfield said:
hey homeboy76 tried the flash-all bat [-w removed] and the process went through w/o any issues but it immediately rebooted itself and within 30 seconds landed on the stock recovery & it said file may be corrrupt, TRY AGAIN or FDR ....
Do I have any other recourse to save my 100 GBs of data ??? or do I onlly have the unmoddded flash-all -w to do at this point ?
Click to expand...
Click to collapse
Did you check the SHA256 of the March 2019 factory image?
I don't think it would hurt to try again. If it doesn't work you can try FDR or flash-all with [ -w] both will erase your internal storage.

Homeboy76 said:
Did you check the SHA256 of the March 2019 factory image?
I don't think it would hurt to try again. If it doesn't work you can try FDR or flash-all with [ -w] both will erase your internal storage.
Click to expand...
Click to collapse
Soooo, check this out .... I finally got a flash-all {no -w] to work and my phone booted - buuuuut it is STILL ENCRYPTED .... opening the root//file explorer I was horrified to see that everything is still encrypted .... it's soooo bizarre. apps from PS are restoring but I cannot get screenshots to save nor can I move any files from my laptop to my Pixel Xl. I wanted screeenshots so bad to show/post this bizarreness but -no- ....
I havent tried to boot into recovery yet or anything else .... so I dont even have root to look any deeper into the partitions. I was wondering if Titanium Backup would run and populate with proper app names, etc
Any more ideas from this unprecedented point bro >? BTW, the SHA256 was good/clean/proper.
BTW, when you flash a factory image, which facking partition (A or B) -should it- be flashed to or flashed "from" - I've let myself get quite confused >???? I have researched & read sooo much, my brain hurts (& is literally fried) .... I figured I would ask you so I could possibly get some firsthand clarification.

C.Hatfield said:
Soooo, check this out .... I finally got a flash-all {no -w] to work and my phone booted - buuuuut it is STILL ENCRYPTED .... opening the root//file explorer I was horrified to see that everything is still encrypted .... it's soooo bizarre. apps from PS are restoring but I cannot get screenshots to save nor can I move any files from my laptop to my Pixel Xl. I wanted screeenshots so bad to show/post this bizarreness but -no- ....
I havent tried to boot into recovery yet or anything else .... so I dont even have root to look any deeper into the partitions. I was wondering if Titanium Backup would run and populate with proper app names, etc
Any more ideas from this unprecedented point bro >? BTW, the SHA256 was good/clean/proper.
BTW, when you flash a factory image, which facking partition (A or B) -should it- be flashed to or flashed "from" - I've let myself get quite confused >???? I have researched & read sooo much, my brain hurts (& is literally fried) .... I figured I would ask you so I could possibly get some firsthand clarification.
Click to expand...
Click to collapse
I can't help you with the file encrypted problem. I've never read about anything like the problem you're having with encryption. TB might work. If your files are backed up on your computer, FDR.

https://forum.xda-developers.com/showpost.php?p=79273902&postcount=481
@C.Hatfield, continuing the discussion...
Topics
1) Forced encryption
2) Output of ls /data/misc/vold/*
3) Advanced approach

VR25-
First, I'll start with a sincere Thank You - I know you're busy with school & life, so I appreciate that you take the time to create such beneficial tools like Migrator. Having used Android OS since it's inception, I've learned a whole lot & seen a whole lot buuut not this craziness. I was unable to get any actionable help within the 2 weeks that I held out doing a full FDR ....
alas, I finally relented & did a full FDR with a full on flash-all.bat & ironically, it was only a couple hours before your response. I didn't read the response until now because I was afraid you'd posted an A, B, C unencryption method for me - in a small way, I'm glad it isn't that lol ....
As for the "did you..." questions you asked in Migrator thread, I followed my usual protocol & did not vary at all, except running the Migrator script 2x's before trying to install new ROM.