[Q] Trouble with flashing / /data is destroyed - Galaxy S 4 Q&A, Help & Troubleshooting

Hey Guys,
i have a big problem with my new S4 (i9505).
Ive rooted the Stockrom with Odin and then i flashed the Recovery, thats works well.
After this step ive tried to flash CM10.1.
The first boot works well, ive setup my phone, take a reboot and then i have a bootloop.
Ive go to the Recovery and i see that /data is destroyed.
Ive formating /data, flashed CM10.1 again, first boot works, second boot, /data is destroyed.
Then i flashed the prerooted XXUBF8-Firmware, flash the recovery, all works well. Then i flashed a alternative Kernel, my /data will be destroyed again. I have to format it, and to reflash the stock firmware.
My last try was to flash the minit-Framework. After this flash, i cant boot in my system, becaus my /data was destroyed.
I dont thought that my device is destroyed, because the Stock prerooted F8-Firmware (with custom recovery) works 2 weeks long without any problems (ive rebootet many times in the 2 weeks).
What i doing wrong?
And sorry for my bad english
Best regards

Just to follow you : what do you mean by "destroyed" ? Formatted partition ?
If so, try to do the following : flash stock ROM, then the recovery (I personally use Philz Touch based on CWM), do a factory wipe and then install the rom you want.

Hey,
thanks for answer.
When i have a bootloop and go to the recovery and want reflash a rom, the installer say: cannot mount /data, unknow partition. and then the setup breaks up.
After a format of the /data-Partition via Recovery, i can reflash the rom, and boot onetime.
Ive go "your way" and i have the some problem. After one Reboot my /data is destroyed.

Mmmm...in the Philz Touch recovery (based on ClockWorkMod but with a lot of improvements), there is an option called "wipe data for new rom install" or something similar... give it a try !

I will try it
Ive tried it with CWM / TWRP and have the same error.
But i will try it ) *flash*
Till later

androidnoobi said:
I will try it
Ive tried it with CWM / TWRP and have the same error.
But i will try it ) *flash*
Till later
Click to expand...
Click to collapse
Good luck ! As you can normally flash stock rom, you don't seem to have hardware issues so don't worry

omg Oo
I dont believ it -.-
All the trouble are only fail from CWM and TWRP??
Now with Philz it works perfectly.
Ive installed Bobcat, reboot, flashed minit, reboot, flash another Kernel, reboot .. and it works Oo
Great )
Thanks

Related

[Q] Stuck in bootanimation loop after flashing stock ROM

I flashed stock B136, then recovery screen showed up, like E: couldn't mount block 6 etc.
Then flashed B518, got pink screen, stuck bootanimation.Copied cwm 5.0.2.7. , went to recovery. wiped everything, but said couldn't mount /system. Then flashed again B518, stuck bootanimation again.But it is very slow like 2x.Now i have no idea what to do.
What can i do?
When did it say it can't mount /system?
Was it when you were formatting /system?
How about custom roms? Can you flash and use them?
rqmok said:
When did it say it can't mount /system?
Was it when you were formatting /system?
How about custom roms? Can you flash and use them?
Click to expand...
Click to collapse
First flashing stock B136 rom.After flash completed, automaticly went to recovery and said like : can't mount E : dev/block
Then flashed B518, copied 5.0.2.7 cwm in pink screen.Wiped everything, tried formatting system then i got the can't format system message
Can't use custom roms, because i want to sell it.But yes it flashed.

Reboots cause loops, TWRP cant mount data

ive tried a whole bunch of roms and the behavior seems to be very consistent.
Here's the scenario, same for every rom:
-boot into TWRP, advanced wipe -> wipe everything
-flash rom over adb sideload
-reboot system
-rom comes up just fine the first time, log into google, restore apps
-any time i reboot after, it sits on "Galaxy s4" boot screen, if I then reboot into recovery, TWRP asks for password because it can't mount partitions.
-only way ive found to get out of this is to format data, then reflash.. only until the first reboot again.
stock rom works flawless, the only custom rom that also worked flawless was task650's AOKP 4.2 rom, which was strange but i used it for couple months. now since i i updated to his latest 4.3 release the same issue came up, so i tried again a number of different roms.. no luck
ive exausted my google-fu and these forums, can someone please help... is this a kernel issue? bad hardware? am i just doing something very simple very wrong?
In twrp, just do the standard wipe, the one that you just swipe the wipe. I think your wiping too much.
Then install the Rom, kernel, and what else you may need, no need to side load it
jd1639 said:
In twrp, just do the standard wipe, the one that you just swipe the wipe. I think your wiping too much.
Then install the Rom, kernel, and what else you may need, no need to side load it
Click to expand...
Click to collapse
same thing, except this time it didnt even boot once, stuck on "galaxy s4" logo, then rebooting back into TWRP prompted a password coz it couldnt mount anything...
i think it gets stuck on boot logo because it cant mount partition same way TWRP cant, but i have no idea why it wouldnt be able to after a reboot or what could be screwing it up
Why don't you try flashing a new recovery?

Problem with flashing F2FS Recovery and ROM

Hello,
yesterday i tried to flash SlimKat with "All F2FS" (SlimKat).
I Followed the description and copied all files to my Nexus 7, flashed the new all f2fs twrp 2.7 via fastboot. Flashed the FormatPartition.zip rebootet and flashed ROM and Gapps. Till here, everything works great. But if I try to Format Data it says to me that I need to type in my password to decrypt partition. But I never set one.
The only way to bring my Nexus 7 booting was to flash stock rom and stock recovery via fastboot.
I´ve tried it two times but everytime i get the same problem.
Anyone know how to fix this?
P.S.: Sorry for my bad english
You get that error, because either you recovery or your partition is not f2fs. My guess is the second one. Try formating the Data partititon from your f2fs TWRP recovery.
This error is shown when I try to Format Data partition. And I realy have flashed both (right recovery and flashed the formatpartition.ZIP)
Sent from my P6-U06 using XDA Premium 4 mobile app
If I were you, I would revert back to full stock and start from there step-by-step.
Tried it a third time after flashing full stock. Also have downloaded the recovery and the zips a secound time. Now it works like it should
Thank you for your help

i9505 doens´t boot after flashing stock firmware

Hello
I was trying to update my friend´s i9505 to the latest AntaresOne CM12 build, but forgot to flash gapps, and since i coulnd´t for some reason enter CWM (the phone just reboots), i had to flash stock firmware over again so i could start over.
But now the phone isn´t booting even on stock firmware. That usually did the trick.
The wierd thing is that Phils Touch Recovery was working before, but ever since i used Triangle Away to reset binary counter, the recovery won´t boot up anymore.
The only way that i could get into Phils Recovery was to install the TWRP recovery installer, and throught the app i would tell it to flash, and it would reboot into Phils Recovery
Now since system isn´t booting, i can´t install and use the TWRP installer to reboot into recovery mode for me.
Tried to flash stock recovery, the same thing happens: the phone just black screens, vibrates and reboots.
Any ideas of why this might be happening?
Go to stock recovery if you can and wipe data/factory reset. Install stock ROM then.
@guguts
As clearly wrote in 1st post of my thread, you need to do "format /system" before installing ROM's builds starting from 26/11 one and latest ones, including 3/12 and the ones that will come in the future.
I strongly suggest you to take a look again at installation instructions, but this time carefully.
If you need anything else, write directly in its Q&A thread (you can find it in this section) where surely you can be helped more and better
Inviato dal mio GT-I9505
Flash a custom recovery with Odin. Uncheck auto-reboot before flashing.
Then boot into the recovery using the botton combo. Keep holding it as long as it takes to enter recovery.
Hey guys, i managed to work it out.
It was probably a loose vol up or home button, because i didn´t do anything but a few moments later i tried to enter stock recovery and it went fine.
The issue was not with the custom rom (which by the way is great, my friend says its running smooth).
The issue happened because i forgot to do i data wipe after installing the rom and prior to installing the stock rom.
So the stock ROM was trying to load using lollipop data and cache, and thats why it got stuck in the samsung logo.
As soon as i managed to enter stock recovery again, and made a data wipe, the stock room booted fine.
So i tried again, but this time didn´t forget to flash gapps, and even better, now Phils Recovery is booting up normally (go figure...)
So i formated /system and /data, flashed AntaresOne ROM and gapps, and everything went fine.
Just posting here in case anyone in the future goes througyht the same hassle.
Thank you so much for your work Antares.
Its people like you, quarx and pawtip (and many others top developers) that makes this community great.

Broken TWRP / CWM recoveries?

Hello all, I have an issue with recovery on my i9505 which hopefully someone can assist with?
I'm using the excellent Optimised CM12.1 and had TWRP 2.8.7.2 (f2fs) as my recovery all working fine. I've recently flashed the newest 2015-11-1 ROM over the top (clear cache and dalvik, but not data wipe) and all seemed great.
However, I went to 'reboot to recovery' in order to install exposed and got stuck on the teamwin splash screen of recovery. Every time I tried to power off it would bootloop into the same splash screen!
Using Odin I was able to flash a new recovery (TWRP 2.8.6.0) and reboot the phone as normal. All worked fine until I tried recovery again and found the same issue!
I've now got CWM (6.0.4.7) flashed to see if that would help but nothing is mounted when using that and so I cannot get to the zip files! When attempting to mount within CWM it errors and cannot mount.
I'm open to any suggestions and would like to learn why this is occurring. Let me know if there's any logs or files I can post that would help.
Many thanks in advance!
Stu
StuKeeler said:
Hello all, I have an issue with recovery on my i9505 which hopefully someone can assist with?
I'm using the excellent Optimised CM12.1 and had TWRP 2.8.7.2 (f2fs) as my recovery all working fine. I've recently flashed the newest 2015-11-1 ROM over the top (clear cache and dalvik, but not data wipe) and all seemed great.
However, I went to 'reboot to recovery' in order to install exposed and got stuck on the teamwin splash screen of recovery. Every time I tried to power off it would bootloop into the same splash screen!
Using Odin I was able to flash a new recovery (TWRP 2.8.6.0) and reboot the phone as normal. All worked fine until I tried recovery again and found the same issue!
I've now got CWM (6.0.4.7) flashed to see if that would help but nothing is mounted when using that and so I cannot get to the zip files! When attempting to mount within CWM it errors and cannot mount.
I'm open to any suggestions and would like to learn why this is occurring. Let me know if there's any logs or files I can post that would help.
Many thanks in advance!
Stu
Click to expand...
Click to collapse
Do not use CWM. It's outdated and not compatible with Lollipop.
You could try flashing a stock rom with .pit and re-partition. After that flash TWRP again.
Lennyz1988 said:
Do not use CWM. It's outdated and not compatible with Lollipop.
You could try flashing a stock rom with .pit and re-partition. After that flash TWRP again.
Click to expand...
Click to collapse
Thanks for the advice. I don't like CWM myself.. just tried it as an attempt to get TWRP flashed back properly!
I will go the stock re-flash route as a last resort. I'm sure it will fix the issue but is a little drastic.
What caused this? - is it something to do with the F2FS filesystem? TWRP recovery was working fine in order for me to flash the updated CM12.1 (2015-11-1).

Categories

Resources