Develop Bugs

[Q] DINC won't clear user data, after using every trick I know

So, I recently acquired an Incredible, the second one I've owned. The first one I rooted, turned S-off and installed CM7 with zero difficulties, after that I rooted/flashed my Xperia Play CDMA with all the issues that accompany that device. (after the ease with which I modded my first DINC, the hoops through which I had to jump to unlock my bootloader blew my mind)
This DINC, though, refuses to clear user data. Even after multiple wipes via CWM, and multiple updates using the PB31IMG method, user data remains. Attmepts to preform a factory reset via HBOOT result in a balck screen with a red triangle and exclamation point.
I tried to install MIUI, thinking maybe a fresh rom would fix it, but it gets stuck at the room splash screen.
I've even tried recovering a clean CM7 install from my old incredible, but it gets stuck in a bootloop at the rom splash, same story trying to flash the .zip in recovery.
I've seen a few threads that deal with a few of these symptoms, but not the issue as a whole
Thanks in advance for any answers you guys have!
Cheers
I found a solution, finally. Admittedly, it was a bit drastic, but it worked, nonetheless.
I ended up disassembling both DIncs and putting the motherboard of the working device (with the smashed screen) into the device that was unable to format /data.
It was a bit touch and go for a bit, but my new DIY refubished phone is up and running.
Thanks for the help guys!

What error do you get? Can you upload the logs from /cache/ recovery after trying to wipe?
Sent from my Galaxy Nexus using Tapatalk 2

I'm still a bit of a noob, if you could point me towards some basic instructions on how to do that, I'll post a log when i get back to the house.
Last time I tried to logcat something in recovery, I nearly bricked my phone somehow.
Edit: It either gives me the red error triangle/exclamation point if i use HBOOT, or it gives me an error when trying to format the data partition on a recovery attempt.

mattdubuc said:
I'm still a bit of a noob, if you could point me towards some basic instructions on how to do that, I'll post a log when i get back to the house.
Last time I tried to logcat something in recovery, I nearly bricked my phone somehow.
Edit: It either gives me the red error triangle/exclamation point if i use HBOOT, or it gives me an error when trying to format the data partition on a recovery attempt.
Click to expand...
Click to collapse
Re-flash CWM recovery. The red triangle is a problem with recovery most likely. You can flash the latest CWM for the incredible from the app.
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.

tiny4579 said:
Re-flash CWM recovery. The red triangle is a problem with recovery most likely. You can flash the latest CWM for the incredible from the app.
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
Click to expand...
Click to collapse
The red triangle happens when you try to do a factory reset from hboot wile on cwm recovery. If you really need to do a factory reset, you will need to flash to the stock recovery first. http://dinc.does-it.net/Recoveries/Stock_4.08.605.15/PB31IMG.zip Then if it works or even if not flash back to cwm recovery http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip.

The weird thing is, that even after flashing PBG31IMG via HBOOT I'm retaining all the previous user data. I've tried formatting the internal drive, using a few different versions of the image, even manual formatting of /data via CWM, which only gives me an error. the same error as when I tried to restore a nandroid from my functioning DINC.

tiny4579 said:
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
Click to expand...
Click to collapse
So do i just make a .zip file out of the contents of /cache/recovery or is there something more to it?

mattdubuc said:
So do i just make a .zip file out of the contents of /cache/recovery or is there something more to it?
Click to expand...
Click to collapse
That should be fine. Try to wipe data in cwm again just so it logs it.
Sent from my Galaxy Nexus using Tapatalk 2

I'm having the same issue, even after reflashing a rom or hard reset my system is as it was before, but most apps don't work. After turning on device instantly shows many errors such as error in com.android.phone etc... While trying factory reset in Recovery (5.0.2.0) the only error that logs is "no app2sd partition found. Skipping format of /sd-ext ". What can you advise? Please help, tomorrow I'm going to another country and in this moment working phone is very needed Device S-OFF Rooted HBoot 0.92

zslashy said:
I'm having the same issue, even after reflashing a rom or hard reset my system is as it was before, but most apps don't work. After turning on device instantly shows many errors such as error in com.android.phone etc... While trying factory reset in Recovery (5.0.2.0) the only error that logs is "no app2sd partition found. Skipping format of /sd-ext ". What can you advise? Please help, tomorrow I'm going to another country and in this moment working phone is very needed Device S-OFF Rooted HBoot 0.92
Click to expand...
Click to collapse
Same error if you flash stock GB sense and factory reset from recovery? You have the errors when booting and the apps are still there?
Sent from my Nexus 7 using Tapatalk 2

Thank you for reply, I solved reset issue by installing Amon Ra recovery. But the problem with apps still exists, it looks like system is restoring back up after reboot, I can do everything with system but after reboot it's like it was before with no changes made. Additionally, it seems that the problem is with emmc, just because when I delete EVERYTHING on it, after restart all files appear again!

I'm also getting an error when I try to manually format the data partition under >mounts and storage in CWM, I'm assuming that may be to blame for retained user data?
When I run show log after running only a manual /data format it displays:
6 black groups
32768 blocks per group. 32768 fragments per group
8112 inodes per group
superblock backups stored on blocks:
32768. 98304. 163840
The filesystem already has a journal,
tune2fs 1.41.6 (30-May-2009)
Setting current mount count to 1
Failure while running mke2fs
Error formatting /data!
mtd: succesfully wrote block at 0
I:Set boot command ""
I have no idea what that means really, or even if it's pertinent.

I had to remove the user info (owner data, phone number, etc) from my inc after canceling my contract with verizon. After about 25 different attempts to wipe it, I finally found something that worked (at least for me)
Tried running the RUU, could not reboot into HBOOT (version error)
Tried the RUU again, this time starting it after manually booting the phone to HBOOT. Got a little farther than before, but still errored out. Did not work. Disconnected phone, pulled battery, rebooted to HBOOT.
Factory reset in HBOOT got me stuck on the stock recovery screen. Battery pulled, could not boot.
Flashed CWM in HBOOT (by renaming to PB31IMG.zip), was able to get into CWM recovery.
Tried to flash the 2nd GB OTA in CWM, did not take. Every option I clicked in CWM gave me about 7 errors after sitting on the logo for a moment. Battery pull, reboot. Boots into CM9. >.<
Booted to my rom, saw about 300 force closes. Tried to reflash CWM from Rom Manager, got a bunch of force closes. Updated Rom Manager from market, reflashed CWM, and this time it worked.
Rebooted to CWM, wipe data/cache/dalvik, reboot.
This time I booted in CM9, but to the initial ICS set up (click next to begin, wireframe pic of Andy)
After skipping thru initial setup, I checked Settings>About Phone>Status. My phone number was removed, network is Unknown, and all my data was removed. Activation prompt appears on each boot.
Not sure if this will help, but worth a try. I think that the HBOOT factory reset is what cleared my data, and then I just needed to fix CWM so I could get back to a working ROM.

Yeah that's what I did in june except I just got service on mine but I would think that would help getting your data out forever. If that does not work I wouldn't know what to tell u besides grab a magnet. Lol
Sent from my Droid Incredible using xda premium

[Q] Softbrick after discharge /data/media is inaccessible

Hi there!
Got kind of a strange Problem with my Nexus:
I had big troubles last weak after i fully the battery by accident. I was stuck in a bootloop, so first thing i tried was a factory reset and restoring a nandroid backup. Didn't work, it randomly rebooted while restoring the backup. Same with a aokp rom i still had on my sd card.
Fastboot flashing didn't work either, i always got a "too many links" error.
It wasn't the usb cable, because i tried three, and it wasn't the pc, the drivers or the usb ports, cause i tried 3 different pcs, too.
At first i thought maybe the internal sd was corrupted somehow, but that didnt really make sense.
As a last resort i switched too odin, always hated it, didn't use it since the galaxy s first came out.
Guess what: It didn't work! It just got stuck at "sending data" or something like that while trying to flash a stock 4.2 rom.
What finally did the trick was:
After i ****ed up the whole device with odin and got the "phone exclamation mark pc" screen after turning it on, i tried flashing the attached zip with odin to get at least my recovery back, which worked after some tries.
After that i flash the slim rom via adb sideload and my nexus came to life again. Which didn't make sense at all, but i was happy.
UNTIL NOW:
I wanted to re calibrate my battery so i fully discharged the phone. And guess what: Same **** all over again.
I just can't get my head around it. It doesn't make sense at all, for me at least. It has to be some kind of hardware failure, but what?
Is there something like the bios battery on pc motherboards which is broken on my device? But flash storage doesn't need any current to save data, so....
I'm no Linux programmer but i'm no rookie either, so i don't think i commited any severe mistakes while trying to fix it. (well, despite odin being a failure in itself )
So, any ideas? I searched the forums a bit, but i didn't find anything similar, just the usual bootloop stuff.

You should never fully deplete a battery. Batteries have their own OS, which allows them to recalibrate themselves. When the system asks you for juice, give it to him.
a maguro wrote this.

I didn't do a full discharged, sorry for being unclear. I just used it until it turned off (5%), nothing more.
Edit:
Ok, i guess it is a real brick now. When i try flashing a rom via sideload, it gets stuck at "formatting data" and reboots after a while. flashing with odin doesn't work either.

Guess i got a bit closer to the core of the problem.
it seems like i have no /data partition on the sd card.
Rom flashing always gets stuck at formatting data. when i try to adb push a file to /data or data/media, it says "no such file or directory found".
When i try to unmount /data in cwm, nothing happens.
Any ideas?

Try adb pushing to /mnt/sdcard/ or /sdcard/ directly.. I remember an issue when i could not use adb with the data folder at all, unless i ran insecure adb from the android os.
or even /mnt/shell/emulated/0/

bodh said:
Try adb pushing to /mnt/sdcard/
Click to expand...
Click to collapse
Thanks, that worked. But still, i can't access the sd card via cwm, so that didn't really help. it says "couldnt open directory"
flashing with sideload still crashes at "Format and Mount System, Mount Data"
Why doesn't it create /system and /data?
Edit:
CWM Log says:
Can't partition non-vfat: datamedia

Why aren't you using fastboot?

bodh said:
Why aren't you using fastboot?
Click to expand...
Click to collapse
HansBaer2000 said:
Fastboot flashing didn't work either, i always got a "too many links" error.
Click to expand...
Click to collapse
That happens when i try to flash system
Seems that just my /data/media folder is gone, at least thats what TWRP tells me
Any way to bring it back? Or are my partitions corrupted?

I guess I missed that. Too bad there's not a manual of common fast boot errors and their causes. I read that the 'too many links error' often relates to bad drivers. I'd try universal naked drivers. Uninstall your current ones, then install. Make sure you're running fast boot as admin. Fast boot erase cache and fast boot format..also, perhaps your data/media got nested by subsequent flashes?

I don't think a low battery should cause any problems to the storage, however if you really have problems with partitions, perhaps try to flash odin with PIT file? (http://forum.xda-developers.com/showthread.php?t=1405327)

bodh said:
I guess I missed that. Too bad there's not a manual of common fast boot errors and their causes. I read that the 'too many links error' often relates to bad drivers. I'd try universal naked drivers. Uninstall your current ones, then install. Make sure you're running fast boot as admin. Fast boot erase cache and fast boot format..also, perhaps your data/media got nested by subsequent flashes?
Click to expand...
Click to collapse
Have tried both, the Samsung usb and the naked drivers before. Maybe i'll try a 4th PC and a 4th cable.
My Gnexi said:
I don't think a low battery should cause any problems to the storage, however if you really have problems with partitions, perhaps try to flash odin with PIT file? (http://forum.xda-developers.com/showthread.php?t=1405327)
Click to expand...
Click to collapse
Tried that multiple times. Flashing a PIT file only works, it repartitions just fine. Flashing a stock rom however always stops at "write NAND"

Are you using USB 2 ports? Try USB 3?
a maguro wrote this.

i would try, but my usb 3 doesn't recognize the phone in fastboot or adb mode, can't say why

Can't do anything in recovery after failed encryption attempt using CM11 Nightly.

Hey guys,
My password isn't working (never did) and I can't get much done in my phone. What to do?
So I was running CM11 on my LS980 and things were working great. I had a nandroid of the rooted stock software on my PC, and decided to encrypt my phone.
So I tried to encrypt my phone, the encryption went well (I think), but when I got to the screen where I type a number in, my code wouldn't work. I wrote it down, I made absolute sure I had it right. I selected the Pin option, as well as the option to automatically unlock the phone when the pin is entered correctly.
I typed the proper code in, and it just kept saying "try again." I have a nandroid backup of the rooted stock Rom saved to my computer, so I can fix this I think, but how do I get back in? I originally heard that wiping data/factory reset would get rid of encryption, but when I try this with my CWM 6.0.4.7 I get:
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
E: unknown volume for path [/sd-ext]
Formatting /sdcard/.android.secure...
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete.
Someone told me this has to do with the way CWM tries to format things (by mounting them first), and that I can go into mounts and storage. but which ones do I format there? I really don't want to mess anything up. Here are my options:
/boot
system
data
cache
persist
firmware
sns
persist-lg
mpt
/data and /data/media (/sdcard
Thanks!

Mods, please move
1. You are in the wrong section, this is not help and troubleshooting (I know more people will see it here) However, we learn from others mistakes and when you post in there people with the same problem might search and see a solution of how you solved your problem.
2. Not sure if adb works in recovery or if it will in your situation but I would try adb reboot recovery or try adb sideload and sideload a rom onto it.

This does not belong in the Development Section, read the Forum Rules on posting....Moved here, thanks.

jhr5474 said:
1. You are in the wrong section, this is not help and troubleshooting (I know more people will see it here) However, we learn from others mistakes and when you post in there people with the same problem might search and see a solution of how you solved your problem.
2. Not sure if adb works in recovery or if it will in your situation but I would try adb reboot recovery or try adb sideload and sideload a rom onto it.
Click to expand...
Click to collapse
Ok ****. So far I've always avoided having to use adb while rooting (rooted evo 4g, gs2, and lg g2). Guess it's time to learn. Any advice on where to start reading?

Judge Joseph Dredd said:
This does not belong in the Development Section, read the Forum Rules on posting....Moved here, thanks.
Click to expand...
Click to collapse
Hey thanks man
While you're here mind telling me why my profile pic doesn't show up on my posts?

Phone still encrypted after reflash/factory reset?

Hello,
I hope someone will be able to help with this, although it is very much a case of user error! I upgraded my G3 to Marshmallow using the steps detailed here:
http://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
It all worked perfectly until I decided to encrypt the handset. The encryption process worked as expected, but as I always did on previous Android versions, I used the CryptFS Password app to change the encryption password. The app advised that it was unable to change the password and that I should run the command via shell, which I did and it seemed to work. The problem is, I changed it to an alphanumeric password and my lock screen is just a numeric PIN, so upon reboot it prompts me to enter the password to decrypt but only allows me to enter numbers.
So, I kicked myself for not changing the lockscreen from PIN to password before rebooting, but figured I could just wipe/reflash and start again. However, when I reflash, I still get prompted for the encryption password at boot. So I figured I'd just enter the password wrong 30 times and factory reset the device that way, except that doesn't work either. It says it's going to reset, reboots to recovery (TWRP 2.8.7.0) and says it has reset, but then boots back to the encryption screen again (which now advises that I am -5 of 30 attempts!!).
Flashing CM13 or 12 works fine. I have settled on CM12 at the moment because it seems to be a bit more stable, but I'd ideally like to get back to stock Marshmallow. Is this possible?
I have tried wiping all partitions and data from within TWRP, and formatting partitions, all to no avail.
Is there any way I can reinstall stock Marshmallow?

Trying flashing marshmellow KDZ and it should reset everything
Let me know how things go

TTib said:
Hello,
I hope someone will be able to help with this, although it is very much a case of user error! I upgraded my G3 to Marshmallow using the steps detailed here:
http://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
It all worked perfectly until I decided to encrypt the handset. The encryption process worked as expected, but as I always did on previous Android versions, I used the CryptFS Password app to change the encryption password. The app advised that it was unable to change the password and that I should run the command via shell, which I did and it seemed to work. The problem is, I changed it to an alphanumeric password and my lock screen is just a numeric PIN, so upon reboot it prompts me to enter the password to decrypt but only allows me to enter numbers.
So, I kicked myself for not changing the lockscreen from PIN to password before rebooting, but figured I could just wipe/reflash and start again. However, when I reflash, I still get prompted for the encryption password at boot. So I figured I'd just enter the password wrong 30 times and factory reset the device that way, except that doesn't work either. It says it's going to reset, reboots to recovery (TWRP 2.8.7.0) and says it has reset, but then boots back to the encryption screen again (which now advises that I am -5 of 30 attempts!!).
Flashing CM13 or 12 works fine. I have settled on CM12 at the moment because it seems to be a bit more stable, but I'd ideally like to get back to stock Marshmallow. Is this possible?
I have tried wiping all partitions and data from within TWRP, and formatting partitions, all to no avail.
Is there any way I can reinstall stock Marshmallow?
Click to expand...
Click to collapse
try booting into twrp, go into command terminal, manually format data partition using command line, then reflash cm12 and wipe cache and dalvik (you may not need to reflash it but why not if you are going back to mm)
if your partitions are the same as mine this is the command you want to run.
mke2fs -T ext4 /dev/block/mmcblk0p44
make sure you don't format the wrong partition check that your variant has the same partition (grab an app called diskinfo and click on data partition then alter the last parameter to w/e ur data partition is)
mmcblk0p44 is the paramater you want to change if yours isn't identical. this should reset encryption as data is the partition that gets encrypted.
after all of this use a guide to install marshmallow (kdz or something)
(when i encrypted my data partition twrp could no longer mount the partition to format it, but if you use command land format it formats the partition without mounting it.)
i'm assuming this is your issue as well.

KronicSkillz said:
try booting into twrp, go into command terminal, manually format data partition using command line, then reflash cm12 and wipe cache and dalvik (you may not need to reflash it but why not if you are going back to mm)
if your partitions are the same as mine this is the command you want to run.
mke2fs -T ext4 /dev/block/mmcblk0p44
make sure you don't format the wrong partition check that your variant has the same partition (grab an app called diskinfo and click on data partition then alter the last parameter to w/e ur data partition is)
mmcblk0p44 is the paramater you want to change if yours isn't identical. this should reset encryption as data is the partition that gets encrypted.
after all of this use a guide to install marshmallow (kdz or something)
(when i encrypted my data partition twrp could no longer mount the partition to format it, but if you use command land format it formats the partition without mounting it.)
i'm assuming this is your issue as well.
Click to expand...
Click to collapse
Hi, thanks for the advice, I gave it a try last night. My /data partition was named /dev/block/mmcblk0p43 according to DiskInfo, so I made sure the partition was unmounted in TWRP and formatted it via the terminal following your instructions and then reflashed the MM zip from the original link and... still encrypted.
I haven't tried flashing the kdz yet, as I use Linux and I don't believe there is a way to flash kdz files using *nix. I'll have to wait until the weekend and I'll try and do it via a VM.
I don't understand how this encrypted partition is still even there. I have CM12 installed and working, it's showing the full amount of disk space available, I've done multiple wipes, formats and resets, yet the minute I put MM on it, the phone thinks it's encrypted again.
I do actually know the encryption key, is there any way I can unlock the phone via ADB or something similar?
Not sure if it's relevant, but my phone model is D855. I don't think I mentioned that before.
Thanks for the help, I really appreciate it!

TTib said:
Hi, thanks for the advice, I gave it a try last night. My /data partition was named /dev/block/mmcblk0p43 according to DiskInfo, so I made sure the partition was unmounted in TWRP and formatted it via the terminal following your instructions and then reflashed the MM zip from the original link and... still encrypted.
I haven't tried flashing the kdz yet, as I use Linux and I don't believe there is a way to flash kdz files using *nix. I'll have to wait until the weekend and I'll try and do it via a VM.
I don't understand how this encrypted partition is still even there. I have CM12 installed and working, it's showing the full amount of disk space available, I've done multiple wipes, formats and resets, yet the minute I put MM on it, the phone thinks it's encrypted again.
I do actually know the encryption key, is there any way I can unlock the phone via ADB or something similar?
Not sure if it's relevant, but my phone model is D855. I don't think I mentioned that before.
Thanks for the help, I really appreciate it!
Click to expand...
Click to collapse
very strange when i did that it got rid of my encrypted partition... i'm not sure what else to say except maybe see if someone will lend you a windows pc to do kdz flash.

KronicSkillz said:
very strange when i did that it got rid of my encrypted partition... i'm not sure what else to say except maybe see if someone will lend you a windows pc to do kdz flash.
Click to expand...
Click to collapse
I flashed the kdz via LGUP and... now the phone won't boot to anything except TWRP. Have tried restoring two previous nandroid backups, installing CM12 and MM, all install without reporting errors. LGUP detects it as an unknown device, so can't flash kdz again. Might have bricked this one. :crying:

Phew. Okay, solved! I followed the following guide to flash an old version of the stock firmware: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html.
Then, I upgraded, rooted, flash TWRP and finally installed MM again and it seems to be back to normal ("Android is starting" screen as we speak. Fingers crossed!). Thanks to everyone who helped me out with this one!

[HELP] XT1794 stuck at fastboot/twrp after infinite boot anim on the latest los16

Hi everyone, I was usually providing help on this forum, now i'm the one desperate for help after some unforeseen consequences.
Bear in mind I'm kind of a noob anyway.
I have seen the message on the telegram groups for our device regarding solving the los 17 problems with the ril and camera. So i have followed the steps. I flashed the last twrp 3.4 by jarl using the official twrp app and then rebooted to recovery, wiped everything beside the internal storage and tried flashing the last los 16 zip.
And then the disaster happened. firstly the log returned error 7 so i've rebooted to recovery again and attempted to flash the same zip again without wiping anything. well the flashing worked apparently but i couldnt boot into it as it showed me an infinite boot animation.
Then i rebooted to recovery and it prompted me with a decryption key request which i didn't set before. I cancelled the prompt and I moved forward and proceeded wiping everything including the internal storage thinking that was the problem. Maybe it was maybe it wasnt, now I'm no longer prompted by any decryption key, but I was hoping i could connect to my pc through mtp, transfer some zips and flash some functional rom. Even though I enable mtp and my pc detects the phone I can't access any storage nor the internal, nor the sd card.
I tried going through multiple versions of twrp as i can still access my bootloader and i can still flash recoveries through fastboot but i feel that i'm stuck and I dont know what i should try anymore.
Before trying all this I was on an older build of los16 with the oreo firmware.

First of all, use this TWRP: https://build.twrp.me/twrp-3.4.0-0-montana.img
Second of all, do not flash TWRPSARer (if you did). Make sure the LOS16 zip isn't corrupted (which normally causes error 7), then format system, data, cache, vendor and dalvik. Reflash LOS16 and boot

JarlPenguin said:
First of all, use this TWRP: https://build.twrp.me/twrp-3.4.0-0-montana.img
Second of all, do not flash TWRPSARer (if you did). Make sure the LOS16 zip isn't corrupted (which normally causes error 7), then format system, data, cache, vendor and dalvik. Reflash LOS16 and boot
Click to expand...
Click to collapse
I wasnt using the twrp sar, i was using the exact version you linked. And I can't flash any rom because i cant get the zip inside my internal memory.

You can try using adb sideload. adb sideload path/to/zip

worked like a charm. thanks a lot, Jarl.

And this, is the story of someone who didn't want to wait long enough for the ROM to boot
Nah JK, but long boot-times normally = Force Encrypt Enabled

Some random said:
And this, is the story of someone who didn't want to wait long enough for the ROM to boot
Nah JK, but long boot-times normally = Force Encrypt Enabled
Click to expand...
Click to collapse
it might have been the problem, but if it is it should be a disclaimer for that on the los16 page. the boot time is way longer than the usual.

Aythriel said:
it might have been the problem, but if it is it should be a disclaimer for that on the los16 page. the boot time is way longer than the usual.
Click to expand...
Click to collapse
Yes, I'll make sure to note that