Database Develop

[Q] Stuck at Padlock with X screen after repeated flash attempts

The title mostly sums it up, I have a Nexus One and unlocked the bootloader to install CM 6.0. I tried Amon's RA recovery image but kept getting file corrupted errors from the .zip files even after verifying the md5 checksums. I was able to get past that problem thanks to Fubaya in another thread pointing out that there are recovery images that allow you to ignore the checksums.
I have now been able to load ROMs from .zip off the SD card, but no matter which one I try (eViL's Sense, CM6, Kang-O-Rama or stock) or how many times I try it, I can't get it to load past the 'X' with the padlock screen at boot. It will sit there for about a minute, then reboot into recovery. I have wiped everything on the phone multiple times but no luck. It just sits there until I pop the battery out. Any idea's what could cause this problem? The recovery image does not show any errors and looks like it flashes successfully

the file corruption errors are a bit troubling.. have you tried re-installing the recovery before proceeding? perhaps the flashing itself is not being done correctly.
often times being stuck at the X can be fixed by wiping the dalvik-cache from recovery, but your problem might be deeper than that.
try putting on amonRA's recovery again and see if that makes a difference.

Uh yeah, you shouldn't be getting any checksum errors. Sounds like something isn't transferring correctly.
As I understand it as long as you have the recovery on there properly (you HAVE to install it correctly AND remove a few files if you're using the stock ROM otherwise it'll wind up at the stock recovery!) you'll "never" be able to brick your phone, with the exception of when flashing the radio apparently..
But flashing with corrupted files still doesn't seem like a great idea, so I'd figure out why this is happening. Can you pull the card out of the phone, put it in a card reader, and check the checksum with md5sum or whatever checksum the particular ROM used... md5 isn't very popular anymore, but it is fast and probably still used a lot for non-secure things, like verifying a transfer etc..

I've tried reflashing recovery multiple times and never seem to have a problem getting in there, either with Clockwork or with Amon. I also tried copying the .zip files back off of the SD card and re-checked the md5sum, it looks like the file is still unmodified so I have a hard time believing that it's corrupt. It does this with multiple SD cards as well, so I don't think its the card either.
I was able to get CM 6 to boot a couple times but the first time didn't seem to work right some error kept popping up that needed to be force closed over and over. So I reflashed and then was stuck in a boot loop with the CM logo. Since then, I have not been able to flash with anything.
Does this sound like some sort of hardware problem with the phone itself?

what radio are you running

4.06.00.12_7. I had Froyo running on here previously, and like I mentioned above, it booted into CM6 once but never came back after a second reboot. I tested and was able to make a call when it was running.

Flash the Recovery via ADB, not the SD card.
Do you still get checksum errors then?

I can't seem to get the phone to show up as an ADB device, I just get "device not found". After doing some reading, it looks like I did not enable USB debugging before flashing. Is there a way to enable this from recovery?
EDIT- Looks like the driver had uninstalled, I now have the driver back up and it shows up under ADB Device as being in recovery.
I copied the Kang-o-rama-1.0-Final.zip over via ADB and then tried to flash from SD Card from within Amon. It still shows E:Corrupt file: with a random file from within the zip as failing and then says verification failed.
Is it possible there is some sort of corruption elsewhere in the phone besides the SDCard that is causing these errors? It seems that whatever is causing the corrupt file errors (even though the .zip files pass the md5sum) is likely the root problem I am experiencing. Any ideas what else I could try to fix this?

[Q] Galaxy S won't boot: can't mount sdcard, mmcblk0p2

Hey,
A friend gave me his Galaxy S after another friend of him got it into this following state (I'm not sure what exactly he did or tried to do):
The phone is stuck in a boot loop, sometimes it shows the first frame of the boot animation for a second before booting again. When I start it in recovery mode (Android System Recovery (3e)) I get this error messages:
Code:
-- Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:can't mount /sdcard
your storage not prepared yet. please use UI menu
for format and reboot actions
The phone does not have an SD card in it.
After reflashing with the same firmware as original, I get these errors:
Code:
-- Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:can't mount /sdcard
your storage not prepared yet. please use UI menu
for format and reboot actions
meida files copy failed.
-- Wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting /cache...
Deleting Meta Data
Data wipe failed.
I've tried flashing different firmwares too, including rooted ones, and the results were the same except for a case where the first error was about not being about to mount mmcblk0p1 instead of sdcard, and another case where another firmware cause the phone to appear to boot, but after a minute or too it got stuck on a black screen and stopped responding.
I followed many different guides on how to fix similar problems, but none of them actually worked.
Please help, thanks a loooot in advance.

http://forum.xda-developers.com/showthread.php?t=1134975
Maybe it will help?

Thanks for the reply. Solutions 1-3 are irrelevant, as I can get into download mode, but even after flashing, any version, the problem is still there. I tried solution 4 (dbdata flash), but it doesn't solve anything. Are there any other partitions I can flash and might be able to solve this?

Ok, next thread
http://forum.xda-developers.com/showthread.php?t=1069867
Maybe here is solution?

Tried flashing the files there and no luck, still the same error. =/
I sent Faria, who said he has tools for solving this problem in that topic a PM, hopefully he'll share his tools with the community.
Meanwhile, I don't mind trying different solutions.
I also noticed something – if I keep the phone in the boot loop for a long time, it will eventually get to either a loop of the carrier boot animation (Which normally doesn't loop), or actually boot for one time. (When it booted I tried to power it off and see if it would boot again normally, and it didn't =/)

i have this kind of error few months ago, what i do was, flash pit file only with repartition, then flash pda, phone & csc.... agn flash this dbdata.rfs file, should fix the issue.

Just tried it, no luck, exactly the same error as before. =/

ops... sorry to heard that, at least it work for me but too bad not for u.....

I have the exact same error message and problem . Really hope someone can find a fix for this because I've spent hours and hours

Yep, EXACTLY same problem as OP and NO fixes for me yet. Tried everything from this thread and other threads. Let's see who's the real king of knowledge who can fix this.

any luck with this issue?

In my case it was solved by Click, but as in thread: for some people it works with repartition, while for some - without.
Or, try it Here I'd pay attention to page 2, Darky's resurrection... maybe looking for newer version at Darkyrom.

spamtrash said:
In my case it was solved by Click, but as in thread: for some people it works with repartition, while for some - without.
Or, try it Here I'd pay attention to page 2, Darky's resurrection... maybe looking for newer version at Darkyrom.
Click to expand...
Click to collapse
thank you spamtrash.
i tried all this various methods. i was able to boot into android but after reboot, it never got into android anymore. stuck in boot loops. ill try Darky's resurrection now, its the last option i havent tried yet. i cant believe there are no scripts or smth to fix and rebuild file system in such cases.

ambrozic said:
thank you spamtrash.
i tried all this various methods. i was able to boot into android but after reboot, it never got into android anymore. stuck in boot loops. ill try Darky's resurrection now, its the last option i havent tried yet. i cant believe there are no scripts or smth to fix and rebuild file system in such cases.
Click to expand...
Click to collapse
Any Luck????????

I'd be interested with results as well. As last hope, you can try http://forum.xda-developers.com/showthread.php?t=1330491 this one, but it requires hardware mod...
Sent from tam-tam drum

any update or fix?
Someone found any fix for this?

Yep!
Hi guys!
Yep - probably I found the solution. One month ago I have bought i9000 with this problem (as broken). Finally I managed to start that SGS and even install ICS on it. The problem is (as I suppose) that internal flash memory is broken and You have to move /data partition to external SD card. So some flashes, some changes in files and repartitioning of SD card does the thing.
Currenty I am in the middle of preparing a tutorial to be pushed on YT to show how I managed to solve the problem. Stay tuned
Best regards

this is a hope.. =)=)=) please send me a tutorial. thanks

Ready
So.
Finally I had some time to add voice recording to my movie and volia - is ready.
I hope it will help at least somehow.
I am not sure if this manual will help in Your case(s), but it might be at least a hint
Best regards
Fteller.

^ So, umm, where's the link for your YT video? Thanks.

Silm 3.0 bootloop hell [solved]

Hi all
I'm avoiding posting on the Slim thread as this ends up being a bit of a mess.
I've been using Slimbean 3.0 since last Thursday without major issues (nothing big, I was just waiting for the right moment to do a full backup and clean everything).
What happens is that my phone dies while coming back home from work and when I try to reboot it start bootlooping. There's no way I can get it back to life.
At this point I can get to download mode, but nothing else.
Yesterday I've been suggested to start looking into flashing something like CM10 and so I did.
By following these instruction http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd I manage to flash via heimdall CWM speedmod kernel without problems.
I finally have CWM working.
From there I can't get adb detect the device. The only way I can upload the rom is via CWM itself and so I did: I upload both Slimbean 4.2.1 RC1 and Slim_Gapps and cm10.0, just in case.
What I'm trying next is a full wipe to start from clean: full wipe/factory reset works OK, but when I try to format /system I get:
Code:
E:Can't mount /dev/block/st19 to /system with parameters auto llw,check=no
(File exists)
Error mounting /system/!
Skipping format...
Done.
This is the point where I'm at.
If I try to flash Slim I get (error 0), being unable to format system for the same above reason.
If I try to flash cm10.0 it doesn't even pass the device assertion check.
Now I'm particularly clueless. Do I need a different CWM that better supports Slim? Or is the system error something that is inherently wrong with my current status?
Any help is greatly appreciated.
PS: I was trying to find help on #freenode with no luck, I'm available there if anyone wants to help, my nick is ThePeach.
UPDATE: ok it seems that by trying to flash Slimbean it actually replaced the CWM with the one I was used to that comes with Slim and finally managed to format /system and flash Slim correctly without problems.
Yay!
I really hope nobody will ever find himself in this kind of mess...

[Q] Paradox of damaged partitions

Well, hello. Not new here, but quite new in posting things, was always just reading what these guys are doing and followed their instructions. result was always being able to flash whatever on a selected device. But today i'm coming with a stupid problem that i hope somebody would help me solve.
2 days ago (and i will be full of details here) di flashed ARHD51.0 on my Htc One. everything went well (as usual with those roms) but i wanted to format my whole phone (i had like 5gbs of backups that i could not find (4 months i was xda-ing and googleing solutions for removing invisible backups that cwm made. and then i read this http://forum.xda-developers.com/showpost.php?p=48108231&postcount=2
as you well know, this is a member of trust on this site so i decided to follow those instructions and that backfired on me i must say. what happened next was that my phone was in a bootloop, recovery was dameged and adb (and still) could not read my device, fastboot would on the otherside.
I managed to flash new cwm (philz touch 6.0.4.6.) via fastboot and it worked. but in cwm messages are following (will copy just some of the lines because you will understand the problem)
failed to mount /dev/block/mmcblk0p39 on data ext4 (file exists)
failed to mount /data
failed to mount /cache
then something like failed to install /tmp/update.zip (that message was shown when i was trying to install stock rom)
and i sideloaded stock (fail), arhd (goes to 30%, freezes on writing data&system)
when exiting cwm, it asks me to reinstall the root because it is missing (even when i install it manually via usb otg or sideload and it says done, still root is non existant.
baseline is this: i formated the sd card, and tried to do as much as i could with all the logical things, my partitions are messed up and i'm missing boot.img and system files, unable to mount data/cache/sd card. Now i can do only so much to ask you. I can try to relock the bootloader and use the ruu (but i am s-on) i can try to send boot.img or something (but how when adb push is not working, "device not found") i can format the partitions but do not know how to format them from cmd or cwm.
currently i'm downloading stock deodexed and odexed stock roms and ruu. i already have su, philz touch advanced (planning to try to flash that only because of more options than standard philz cwm) and otg ready cable to use it if there is no help for adb push.
Anybody, please help because i will tryto fix this, but i'm afraid that if i mess the order of things that needs to be done, i could brick this totally, and in this area of damaged partitions i have no exact experiance.
Any help appreciated, and can be (gladly) rewarded on demand
sorry for funky and somewhere incorrect gramatic structure, if something is unclear about it, feel free to ask

kriistofor said:
failed to mount /dev/block/mmcblk0p39 on data ext4 (file exists)
Click to expand...
Click to collapse
HOLD YOUR HORSES!!
post a "fastboot getvar all" (leave the first 2 characters of serial number, IMEI, and MEID, and "xxxx"-out the rest)
and maybe a screenshot of bootloader
you either have a Sprint/Verizon HTC and/or the wrong recovery!!
so stop!!!! and post above needed information

nkk71 said:
HOLD YOUR HORSES!!
post a "fastboot getvar all" (leave the first 2 characters of serial number, IMEI, and MEID, and "xxxx"-out the rest)
and maybe a screenshot of bootloader
you either have a Sprint/Verizon HTC and/or the wrong recovery!!
so stop!!!! and post above needed information
Click to expand...
Click to collapse
sorry,sorry i sounded a bit overexcited and impulsive.
well, i have international htc, but the cwm (even though i downloaded the M7(gsm) version was the biggest problem for the phone (based on the name of the cwm it does not sound logical to me). Also, i used 6.0.4.6 non touch and it also was useless but i managed to solve this after two whole days of mind****ng myself and this phone.
SOLUTION:
relock bootloader (without this you can try anything as i did but it will fail if the problem is the same)
unlock bootloader
install twrp (for some reason after this cwm, no other cwm was able to format partitions or anything)
format data, or full wipe option
stock rom (installed deodexed 4.4.2)
root if want
problem was gone in 4 minutes, it booted faster than any other thing i've put on this phone (like in 2 minutes fully booted into welcome screen).
now it is running arhd 51.0, elementalX and is alive and well.
solution is probably effective wih all of those problems with corrupted or badly formated internal sd on One but i will say that people here are giving solutions that are logical and are working for others with similar problems. this one is for those who have tried all the things with reflashing recovery, rom, with bad adb experiance because of formatted card and are unable to sideload anything.
thank you for help because if I haven't succeded with this leap of faith i would more likely f*c? something up by myself. and thanks for reply, expected no one would give any

Wipe & Flashing has no effect

Hi,
I have a problem with my Moto G 2014 XT1068 which is described in topic: forums.androidcentral.com/moto-g-2013/391289-something-seriously-wrong-my-moto-g.html#post3668518
I can't do these steps, because dialog window shows up all the time, and i cant go further.
I have disabled usb debugging option and can't disable ART runtime.
First of all "Factory" in bootloader doesn't work. Wipe and factory reset via stock recovery has no effect; old android remains, the same using TWRP:
"E:Unable to open 'cache/recovery/.version' but ends successfully
and PHilz.
I've tried to flash many roms using many recoveries( TWRP - few versions up to 2.8.5 because 2.8.6 has display flickering bug, few Philz, and few others that also flicker) and fastboot and msfastboot(both on linux).
When i flash via fastboot or mfastboot using xml.zip roms everything looks ok, there are no errors, but flashing has no effect - I have still old ROM with old issue.
When i flash via different recoveries always some errors appears. For example flashing latest CM 12.1 nightly
via TWRP i get:
"E:Error executing updater binary in zip '/sideload/package.zip'
or via stock recovery (ADB sideload) get:
"(...)
Verifying update package...
E:Failed to verify whole-file signature
E:signature verification failed
Installation aborted."
Partition erase in fastboot despite "OKAY" message in CLI has no effect. As i understand this should remove all files from partitions.
This problem showed up when i discharged battery to 0% and turned on the phone.
Have you any ideas what should i try more?
Thanks in advance.

Hi,
I've tried other things to back my phone to life, like turn on usb debugging or even delete files, all via adb shell in recovery, but it is impossible. In TWRP or PhilzTouch I remount partitions with rw privileges, it look like I'm able modifying files via vi and cat to check results but when remount one more time old files still exist, so it is like there is some buffer? (maybe some security lock?), when try rm -rf files it shows up that i can't delete because it read only... (but mount says rw). After remount partitions with rw privileges wipe /data in twrp ended successfully but has no effect.
Do you know why everything looks ok, but it is not? Of course android boots up but is useless and after few minutes phone turns off.

i have the exact same problem with xt1064 that shuts off after bootanimation, all flashing and wiping look ok, but stuck in same result.
i read in some threads it's due to corrupt partitions and there's no solution yet to this problem, i hope this is not true, please share if you make any progress, i will do the same. best of luck.

Sounds like you both have a failed eMMC. If that is the case, and I'm certain it is, there is nothing that can be done to "save" or "restore" your devices.
Sent from my XT1031

hi, maybe any1 has already found a solution?

dihcar said:
i have the exact same problem with xt1064 that shuts off after bootanimation, all flashing and wiping look ok, but stuck in same result.
i read in some threads it's due to corrupt partitions and there's no solution yet to this problem, i hope this is not true, please share if you make any progress, i will do the same. best of luck.
Click to expand...
Click to collapse
I have exactly the same issue with my XT1063. Reading a lot for a solution, traying all without success.
Hopping someone can help us!