Hey there
I'm in need of some help!
Phone: I9300 international 16gb
ROM: PA 4.2 beta 2/4
Kernel: stock PA/Devil v2.3.2/Googy-Max2 v2.1.8/2.2.0/2.2.1 final
Recovery: CWM 6.0.4.6 / Philz touch 6.25.0 / latest devil recovery
Problem:
I came from AOSPA 4.2 beta 1 or 2 (think it was 2) and wanted to try devil kernel with f2fs.
So I downloaded the devil recovery found here:
http://forum.xda-developers.com/show...postcount=1116
and downloaded latest PA (4.2 beta 4 04/09/2014) along with day-0 gapps minimal package.
Also I saved devil kernel to my ext sdcard. Ready to go I thought.
Rebooted to recovery...
Flashed devil recovery...
Rebooted recovery...
Did nandroid backup to ext sdcard...
formated /system /data + /datamedia & /cache as f2fs
Flashed latest PA 4.2 beta4...
Flashed gapps...
Flashed devil kernel...
Wiped data & /cache just to be sure
Rebooted...
After the first boot i got
com.android.phone forceclosing over and over again. As soon as I press the OK button the message reappears, giving me no time at all to sort things out while android is running. Next I rebooted to recovery, formated again (f2fs) did a clean reflash, rebooted and got the same problem.
So I wanted to switch back to my working rom, rebooted to recovery, formated everything back to ext4 and restored my backup.
Just to be sure I wiped /cache & dalvik-cache before i rebooted to my old rom (PA 4.2 beta 2 with googy-max2 v2.2.1).
Boot succeeded but I got the same forceclose. This was the first time I realized something just isn't right. Reboot to recovery, restored AGAIN, flashed devil kernel on top -> bootloop. Tried clean installing PA 4.2 beta 4 without custom kernel -> bootloop, switched recovery to CWM v4.0.4.6 and tried restoring my backup from there -> bootloop.
Thought I messed up my partitions, found an Odin package with CWM 6.0.4.4 included, flashed it together with 16gb .pit file and re-partition checked.
As I had 13 partitions before I can confirm via ADB that it did indeed repartition my sdcard.
Restored my backup -> bootloop, for test purposes I tried latest NeatROM light.
Booted & working like a charm. No hickups.
Updated recovery to latest Philz touch (v6.25 somewhat).
Restoring my backup or flashing PA results in bootloops no matter how eager I format /system /cache /data + /data/media before.
/efs is accessible and seems fine. /preload not so much. I noticed it just after flashing Philz touch recovery that whenever I try to format /preload it failes. Can't even mount it (not in recovery menu, nor via adb).
Could /preload (/dev/block/mmcblk0p10) not being able to mount cause these bootloops? Why would NeatROM run just fine then (Sammy based ROM)? Is the /preload partition supposed to behave like that and if not, what could I do to get things going again?.
I'm pretty desperate for help. Thanks in advance for reading that whole text!
//Edit: I hope this is not considered spam, I posted the same text in another thread!
Related
does anyone know about cwm? having some weird /cache issues... reminiscent of the eMMC problems on the HTC desire. Any help would be appreciated! (i use infectedrom nightlys, my restored version loads fine, latest version does NOT, and presents the issues below...)
I downloaded, wiped like normal, flashed... and then got a list of CWM errors... cannot mount /cache/recovery/xxxxxxxxx (5 of them). cannot open either.
mount /command
mound /log
open /log
mount /last_log
open /last_log
any ideas on what to do??
****edit***** so I restored. worked great. downloaded a new copy of r194. md5 match check. matched. wiped data/factory reset (passed on cache wipe option thinking maybe it would prevent this error)... seemed to flash okay. no /cache mounting error message after flashing. rebooted system. now my phone is stuck on the initial "htc" white loading screen that pops up first when booting. been stuck like this for around 5 minutes. normally a new flash loads much faster than this. battery pull. rebooted to recovery. same error message.
cwm3.1.0.2. been working for a couple months now. dunno what to do. restoring last working version until i figure out what to do. help plz!
Afaik, CWM 5.0.2.1 is the latest version. Maybe you must update that to flash the new ROM.
Maybe restore a working setup, and in ROM Manager, update CWM via the first option @ top of list in ROM Manager. Flash it (CWM Recovery) a couple times.
Also, in ROM Manager, menu, settings, erase recovery s/b checked.
Then make a backup of the working setup with the new cwm version, then do full wipe : factory reset, cache, dalvik, and system (in advanced) then flash new ROM.
There's this also :
http://forum.xda-developers.com/showthread.php?t=1179386
Sent from my HTC ThunderBolt using XDA Premium App
haha! thank you. had to use rommanager and update CWM. flashed like a charm after i updated. thanks!!
Hi!
I have a Samsung Fascinate (SCH-I500) which i bought from Reliance (India). The phone came with 2.1 eclair and i upgraded to Froyo (EH19) using the official release that i found on the forum. Later on, i odined the red recovery & then flashed geewiz 2.8 system & kernel edify version using CWM. Everything was working fine. Next i tried to install AOKP M5 ICS Rom but noticed i was not able to get 1x/3G Data in spite of flashing the data fix files for ICS. So i Odined EH19 (Froyo) again to go back to stock. Now here is where the problem started:
Whenever i am trying to upgrade to geewiz 2.8 edify again, I am getting this message
Restoring data...
Restoring datadata...
E:cant mount /dev/block/stl10
(file exists)
Error Mounting /datadata/!
Skipping format...
E:Cant mount /dev/block/stl10
(file exists)
Cant Mount datadata/!
And then the phone does not boot beyond the Verizon wireless screen.
Please help me get out of this situation. I know i have written a long story nut i just wanted you all to know where i was before this problem started.
Also note that I am not able to Odin any other radio other than that of Official Reliance(my carrier). Is this kind of some locking done on the phone by my carrier? Can it be removed so that i can odin a better radio like eh03 or FC27?
Looks like you are missing some steps from what you have written. Check out droidstyles guide that is here in the fascinate. Follow the instructions.
Sent from my SCH-I500 using Tapatalk
I had followed the guide as it is. I just replaced the EH 03 stock rom with the EH 19 STOCK rom from our local carrier ie Reliance
Sent from my SCH-I500 using XDA
Format Your MicroSD
Just a guess here, but maybe try formatting your MicroSD card?
And also, did you try to flash GeeWiz immidiately after restoring to stock?
I odined stock rom. Booted the phone completely. Switched off. Restarted in recovery and then flashed geewiz rom and kernel.
As of now, nor tried formatting the SD card. Will try it and let you know
Sent from my SCH-I500 using XDA
As per your steps above, I don't see where you flashed cwm recovery after flashing stock rom, so that would explain you not being able to flash anything else. Maybe you did, but the steps you listed that you did leave out important steps in each of your posts. Like I said maybe you didn't miss steps but what your wrote is different then. Hope this helps you catch your mistake maybe. Good luck
Sent from my SCH-I500 using Tapatalk
Here is the process i followed in detail:
Started with EH19 rom (froyo) with EH19 radio
Copied GeeWiz 2.8 ROM (EDIFY Update-Zip) &GeeWiz 2.8 Kernel (EDIFY Update-Zip) to root of sd card.
Odined RED RECOVERY 2.5.1.x
Shut down phone.
Started phone in recovery using 3 finger.
Wiped data & cache
Installed Geewiz rom & then kernel
Rebooted the phone (using recovery)
Phone booted completely. Gingerbread install was successful.
GB to ICS
I copied all necessary file for moving up to ICS. (AOKP M5 ) ie
teamhacksung_fascinatemtd-ota-eng.BUILD1
cwm4_fixed_for_cm7-ODIN
aokp_fascinatemtd_Milestone-5-Glitched-2012-04-29-08_44
gapps-ics-20120422-signed
Data_fix_ISC
Odined CWM
Rebooted phone to CWM recovery
Installed THS
Rebooted completely
From Phone menu, rebooted to recovery
Installed AOKP, then gapps & then Data fix files
Rebooted
ICS installed properly but without 1x/3G Data
So flashed data fix files again but data still dint work
So decided to move back to Froyo
ICS to froyo
Shut down phone.
Went into download mode
Odined EH19 rom with Atlas Partition 2.2
Switched on Phone
Phone showed some errors in erasing data & formating data.
But still booted up & am able to use the phone normally.
Next i tried to install Geewiz again
Odined RED RECOVERY 2.5.1.x
Shut down phone.
Started phone in recovery using 3 finger.
Wiped data & cache
Installed Geewiz rom & then kernel
Rebooted the phone (using recovery)
Phone displayed the following message
Restoring data...
Restoring datadata...
E:cant mount /dev/block/stl10
(file exists)
Error Mounting /datadata/!
Skipping format...
E:Cant mount /dev/block/stl10
(file exists)
Cant Mount datadata/!
I think this is what i have done till now. Dont think i have missed writting any steps now. Pls check & tell me where i went wrong.
Try a different recovery.
I have seen errors of this type before, and they are generally fixed by using a different recovery. Try TWRP. And by the way, I think the reason you didn't have data in ICS is that your data fix for android 2.x is incompatible with android 4.x.
I don't see where you rebooted after installing aokp and then went back into recovery from the menu and installed gapps and then rebooted to aokp and signed in to your Google account
Sent from my SCH-I500 using Tapatalk
Hi guys,
First, let me start off with some information about my setup:
Phone: Galaxy S3 i9300
Rom: Omega v5.0 AOPK (No modded kernel, modem or anything; "stock" Omega 5.0 AOPK)
I downloaded and flashed (via CWM) this camera which I downloaded via Omega Files. I then went on to boot and got stuck on bootanimation. I took out my battery, reinserted, booted in recovery and cleared /data, /cache and dalvik cache. Rebooted the phone, and yet again it's stuck on boot animation.
Any tips on what I might've done wrong / what I can do to fix it?
Restore the nandroid you made just before you flashed the mod, if you didn't then do a super wipe and flash your whole ROM again - pray that your efs folder and partition is still intact.
boomboomer said:
Restore the nandroid you made just before you flashed the mod, if you didn't then do a super wipe and flash your whole ROM again - pray that your efs folder and partition is still intact.
Click to expand...
Click to collapse
How do I do a super-wipe? I have an EFS-backup so I guess that part should be safe.
Could I reflash the rom through recovery (which still works)?
If you have Philz recovery then that option is built in, otherwise format system, data, cache, preload and delete the android folder of your internal sd card.
Flash the ROM either through recovery or Odin.
boomboomer said:
If you have Philz recovery then that option is built in, otherwise format system, data, cache, preload and delete the android folder of your internal sd card.
Flash the ROM either through recovery or Odin.
Click to expand...
Click to collapse
Reflashing through recovery worked. Great! Thank you so much
I suppose a nandroid backup is in order. Is there any particular way that's best for such a task, or can I simply do it from CWM?
Get the ROM back to how you like it, make a nandroid in CWM then repeat regularly - simple.
Hello.
This problem has appeared after i flashed the latest Dorimanx kernel (Kernel_Dorimanx-V9.43-[12-16]-[24-10]-JB-SGII-PWR-CORE). Today, after i flashed the latest ressurection remix ROM, i wanted to flash a kernel too. So i booted into recovery, flashed Dorimanx's kernel with no problems, rebooted, and noticed that my keyboard was lagging. So i decided to restore a previous backup from before i flashed the kernel, but when i got into recovery, and select to instal zip from sdcard, i got the following error: E: can't mount /sdcard. The thing is, when i restart my phone, i can acces my files with no problems (music, photos etc), but when i try to do it from recovery, i will not load the sdcard. Other than that, phone is working fine. No bootloops, no lag, just the mounting problem of the sdcard. I feel i should mention that i get an error even when trying to mount it directly from the recovery tab "mounts and storage". I hope you can get back to me and this soon, because this problem will prevent me from flashing any future roms/kernels or doing backups/restores.
cosminpislariu said:
Hello.
This problem has appeared after i flashed the latest Dorimanx kernel (Kernel_Dorimanx-V9.43-[12-16]-[24-10]-JB-SGII-PWR-CORE). Today, after i flashed the latest ressurection remix ROM, i wanted to flash a kernel too. So i booted into recovery, flashed Dorimanx's kernel with no problems, rebooted, and noticed that my keyboard was lagging. So i decided to restore a previous backup from before i flashed the kernel, but when i got into recovery, and select to instal zip from sdcard, i got the following error: E: can't mount /sdcard. The thing is, when i restart my phone, i can acces my files with no problems (music, photos etc), but when i try to do it from recovery, i will not load the sdcard. Other than that, phone is working fine. No bootloops, no lag, just the mounting problem of the sdcard. I feel i should mention that i get an error even when trying to mount it directly from the recovery tab "mounts and storage". I hope you can get back to me and this soon, because this problem will prevent me from flashing any future roms/kernels or doing backups/restores.
Click to expand...
Click to collapse
Put philz kernel into your internal sd card or the kernel which you were using previously and flash it from recovery then reboot to recovery again. Now try to restore your nandroid backup.
Hope it helps.
Good luck :thumbup:
Hi all,
I am on 4.4.4 and used TWRP in past, now I am on Philz Touch latest recovery.
I first cleaned data and system and tried to flash a different rom, it flashed fine but when I tried to flash 4.4.4 Gapps recovery restarted and it kept restarting if I tried to flash that Gapps so I cleaned again and only flashed the Rom this time, rebooted and my system restarted to recovery.
I manually tried to format all partitions but got
"E:format_volume: make_ext4fs failed on /dev/block/mmcblk0p10
E:Error formatting /preload!"
while formatting preload partition.
I google about this and search in xda too and found few threads suggesting to format /preload partition using TWRP recovery so I tried to flash TWRP but it stuck on it's flash screen. I tried to flash old version using Odin as well as new one but it keeps hanging on the it's flash screen. Flashing Philz via odin works every time but not TWRP.
So it looks like I am not able to format /preload partition, I am not able to flash any rom or gapps and not able to flash any version of TWRP recovery.
I am able to take a backup of my phone and restore it without any problem including my internal sd card using Philz Touch though just for the info.
So any suggestions friends?
Thanks.
Edit:
Flashing normal cwm and flashing TWRP after removing TWRP folder from internal memory helped to boot into TWRP. Also I was able to format /preload using normal CWM recovery however flashing anything using any recovery whether it's TWRP or Philz Touch simply boot my phone back into recovery itself and nothing works.
Even a clean flash doesn't work and flashing only a simply rom file will not work and boot my phone directly into recovery so it looks like my memory is corrupted or something similar.
I would appreciate any kind of suggestions related to my problem. Thanks.
Update :
Thankfully it was only my memory card which got corrupted and thus corrupted my rom files too so changing those files fixed my issue..
Sent from my "GT-I9300/1+1" powered by Carbon Rom & Boeffla/ak Kernel
Fueled by 7000mAh ZeroLemon Battery