My 9003 can't work from last week.
I just got the "com.sec.android.app.twlaucher" broken(force close) and all other applications are also broken even I flashed with any new ROM.
The whole broken story is here:
1. I installed XXKPQ with CWM, and created a backup with CWM
2. Then flashed it with DDKP2 by Odin
3. I got a application broken, and tried to backup DDKP2 with CWM and stopped by incident
4. I tried to restore OS with the backup in step 1
5. I got many Force Close after I restored the OS
6. I tried to flash with any ROM, but always got Force close for any application(even the com.sec.android.phone)
Can anyone give advice for it?
Or I have to change a new memory chip?
Thanks!
realcode said:
My 9003 can't work from last week.
I just got the "com.sec.android.app.twlaucher" broken(force close) and all other applications are also broken even I flashed with any new ROM.
The whole broken story is here:
1. I installed XXKPQ with CWM, and created a backup with CWM
2. Then flashed it with DDKP2 by Odin
3. I got a application broken, and tried to backup DDKP2 with CWM and stopped by incident
4. I tried to restore OS with the backup in step 1
5. I got many Force Close after I restored the OS
6. I tried to flash with any ROM, but always got Force close for any application(even the com.sec.android.phone)
Can anyone give advice for it?
Or I have to change a new memory chip?
Thanks!
Click to expand...
Click to collapse
Dont restore the backup of one firmware over another firmware.
Flash xxkpe twice aand over it flash xxkpq with factory reset after flashing each time. Use this guideforum.xda-developers.com/showthread.php?t=1133787
Sent from my GT-I9003
I tried to format the data, but it didn't work. I can see the previous installed application broken even I flashed with new ROM(Re-partion).
It seems something was locked by system.
Follow this guide to flash XXKPQ Check if everything works well. Try to restore your CWM backup
I tried to flash XXKPE/XXKPQ, but I got a wrong message "E: failed to mount /data (Invalid argument)" when the phone startup".
And the phone repeated to restart, I can't the normal phone.
It seems there is something wrong with the partion of /data.
Is there other way to fix it?
the /data is ext4, I am not sure XXKPQ support ext4 or not.
When flashing XXKPE with pit and all the other stuff you should see Re-Partition checked. Then everything should be formatted with the standard RFS filesystem unless you convert it. The stock Kernel doesn't support ext4, but that doesn't mean that you can't try to flash a Kernel that supports ext4.
Did you let the phone boot up completly after every flash?
I didn't let XXKPE boot up completely after flash.
It seems that the /data partion was not reset in flashing with the "Re-partion" selected.
I got error message when I tried to check the disk status.
/sbin # fsck.ext4 /dev/block/mmcblk0p3
fsck.ext4 /dev/block/mmcblk0p3
e2fsck 1.41.6 (30-May-2009)
/dev/block/mmcblk0p3: recovering journal
fsck.ext4: unable to set superblock flags on /dev/block/mmcblk0p3
Related
So it has come to my attention that when you restore a firmware via nandroid backup It does not restore the default ext4 partition that you convert. I found this out today when I had hoped my constant flashing would lead to XXKPN not booting unless I used CFRoot when flashing from Cranium [XXKPH]. Only to find out the firmware booted . Now this got me in surprise only because default partition is rfs and not supposed to be able to boot if set partition format was ext4. All default Samsung firmwares come with rfs partition.
Code:
Note: Next time you flash to a new firmware and back, you are required to flash the ext4 script then restore your nandroid backup for that respective firmware.
Misledz said:
So it has come to my attention that when you restore a firmware via nandroid backup It does not restore the default ext4 partition that you convert. I found this out today when I had hoped my constant flashing would lead to XXKPN not booting unless I used CFRoot when flashing from Cranium [XXKPH]. Only to find out the firmware booted . Now this got me in surprise only because default partition is rfs and not supposed to be able to boot if set partition format was ext4. All default Samsung firmwares come with rfs partition.
Code:
Note: Next time you flash to a new firmware and back, you are required to flash the ext4 script then restore your nandroid backup for that respective firmware.
Click to expand...
Click to collapse
I thought everyone knows this Because
1. before converting to ext4 you make backup. And if it will restore filesystem you will never get ext4 (it will always put rfs from backup)
2. when you make backup you can see that it backups files, not partition.
Mods please Sticky this thread and lock it by Misledz's permission before the thread is noob killed
Tapashocked via my gt-I9003 with a random keyboard of my choice !
I think mod should murge this info in already available sticky thread. Making lot of thread sticky will not be a good idea.
vishal24387 said:
I think mod should murge this info in already available sticky thread. Making lot of thread sticky will not be a good idea.
Click to expand...
Click to collapse
I have to agree, although this is helpful information, having too many stickied threads could become a problem.
falex007 said:
I thought everyone knows this Because
1. before converting to ext4 you make backup. And if it will restore filesystem you will never get ext4 (it will always put rfs from backup)
2. when you make backup you can see that it backups files, not partition.
Click to expand...
Click to collapse
I too already know this by reading skin's original post on ext4.
Instructions were to make nandroid backup -> convert to ext4 -> restore backup -> reboot.
After that u will have ext4 partitions.
So after you anything restore from backup, u will still have ext4.
Yeah but this came as a surprise, I didn't expect that the file system gets overwritten. Some cases flashing to another firmware kicks you into a bootloop due to ext4 previously there, but there are times when the firmware boots which got me in wtf is happening kind of scenario.
When I used cranium or any custom ROM usually does Ext4 by default, but upon flashing XXKPN on top of it, it worked? Which isn't supposed to, So what I'm confused is, What is responsible for the rfs file format, the pit? or the firmware? , and does clearing cache partition reset to rfs?
Because flashing XXKPH->XXKPN->XXKPH without use of pit works and this is without CFRoot
Yes for what this pit file for ? Means for what partition.is it convert file system to rfs ?
Hey guys, i didn't found my problem in other topics, so i opened a new .
So here is the deal, i have the Kisadworx ROM installed now in my Samsung galaxy 3 i5800, and already tried the Kyrillos and both of them have this same issue. When the phone shutdown for low battery, i put it to recharge and when i boot it, it wiped all i have saved. Apps, configs, widgets....just everything. i have no clue why...some one have faced this issue before?
Note: when i enter in recovery mode and try to wipe data/factory reset it shows a message:
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/ log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
I don't know if this error is related but ok ....
Plz someone could help me?
I had this issue days ago, and it happened to me while I simply only turned off and on my phone.
This is probably caused by bad data and cache(?) partition or by bad (wrong) filesystem used. Try re-flashing STOCK rom eg. XXJPQ and over it custom rom of your choice. If the problem persists, try flashing custom kernel (g3mod) and convert file systems like this:
stl6 - ext4
stl7 - ext4
stl8 - ext2
I never had any issues with g3mod kernel's recovery with theese filesystems.
In gingerbread ROMs I had never issues with data or recovery.
bielmontes said:
Hey guys, i didn't found my problem in other topics, so i opened a new .
So here is the deal, i have the Kisadworx ROM installed now in my Samsung galaxy 3 i5800, and already tried the Kyrillos and both of them have this same issue. When the phone shutdown for low battery, i put it to recharge and when i boot it, it wiped all i have saved. Apps, configs, widgets....just everything. i have no clue why...some one have faced this issue before?
Note: when i enter in recovery mode and try to wipe data/factory reset it shows a message:
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/ log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
I don't know if this error is related but ok ....
Plz someone could help me?
Click to expand...
Click to collapse
Do you have an ext partition on your phone?
I got into similar problems with the scripts related to ext partition long ago
I too get the recovery error and it is not of any problem to us . This is solved by using g3mod kernel
hey guys, i followed as twinky444 said and it apparently worked. I reinstalled the stock ROM but a got the samsung bootloop, then a tried again and i made it, after, i installed the kyrillos 10.5 and it''s currently working, with no problems of data lost. I think it was some corrupted data problem. Thank you very much guys
bielmontes said:
hey guys, i followed as twinky444 said and it apparently worked. I reinstalled the stock ROM but a got the samsung bootloop, then a tried again and i made it, after, i installed the kyrillos 10.5 and it''s currently working, with no problems of data lost. I think it was some corrupted data problem. Thank you very much guys
Click to expand...
Click to collapse
If u checked ur available memory when u had the problem, u probably had 0.00kb available. Just saying.
Sent from my GT-I9003 using xda app-developers app
bielmontes said:
hey guys, i followed as twinky444 said and it apparently worked. I reinstalled the stock ROM but a got the samsung bootloop, then a tried again and i made it, after, i installed the kyrillos 10.5 and it''s currently working, with no problems of data lost. I think it was some corrupted data problem. Thank you very much guys
Click to expand...
Click to collapse
If youre going from ROM that uses other filesystems than stock samsung's RFS filesystem such as ext2, ext4, so by flashing the stock ROM causes the bootloop WILL be there. (because the stock kernel doesn't support other filesystems than RFS) You need after flashing stock ROM pull the battery, reinsert it, reboot into recovery by pressing 3-keys combo and then "wipe data - factory reset" in recovery and then "wipe cache partition".
After this, the /data and /cache partition gets either mounted again or reformatted (not sure) with the rfs filesystem and the system will be able to boot.
BTW/little hint: You can see for couple of seconds after flashing the stock rom the phone boots into recovery, shows a couple of lines and there are 2 lines that are RED and say something like
DATA: blablabla... !
CACHE: blablabla... !
This process applies to the ROMs such as Purumod, Kyrillos and maybe others what have other filesystems used than the one used by the stock ROM (RFS).
Thats the description of the "bootloop" problem.
BTW... glad we could help and this has been fixed!
I tried upgrading my old phone,a S1 i9000 to cm10 which resulted in a bunch of errors. I than tried to flash back to stock,however i was still getting:
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.
system unable to Format /data...Internal SD card cannot be mounted and such.
I first tried flashing dbdata.rfs,didn't help
Then i tried doing this http://forum.xda-developers.com/show...8#post30415128 (Flash a JVU+Root with a 512 Pit (repartition ticked) ...)
I also tried flashing just pit with rep,and then JVU, ( http://forum.xda-developers.com/showthread.php?t=817186 )
Then i found this- http://forum.xda-developers.com/showpost.php?p=31017954&postcount=5335
And tried to flash a speedmod kernel (fixed JVU kernel) in order to get the "universal lag fix menu" on cwm. However after i flash it i don't have cwm anymore.
I've been working on this for hours...please help.. What do i do?
EDIT: Flahsed very old version stock jp something,got same message on recovery but then booted.. into...cm10 . I just got the boot and then black screen.
Edit:Fixed everything with this lifesaving manual http://androidspin.com/2009/11/06/m...rd-wpartedgoto-ext34-from-adb-no-livecd-reqd/ I got my phone back!
akjfhdk said:
I tried upgrading my old phone,a S1 i9000 to cm10 which resulted in a bunch of errors. I than tried to flash back to stock,however i was still getting:
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.
system unable to Format /data...Internal SD card cannot be mounted and such.
I first tried flashing dbdata.rfs,didn't help
Then i tried doing this http://forum.xda-developers.com/show...8#post30415128 (Flash a JVU+Root with a 512 Pit (repartition ticked) ...)
I also tried flashing just pit with rep,and then JVU, ( http://forum.xda-developers.com/showthread.php?t=817186 )
Then i found this- http://forum.xda-developers.com/showpost.php?p=31017954&postcount=5335
And tried to flash a speedmod kernel (fixed JVU kernel) in order to get the "universal lag fix menu" on cwm. However after i flash it i don't have cwm anymore.
I've been working on this for hours...please help.. What do i do?
EDIT: Flahsed very old version stock jp something,got same message on recovery but then booted.. into...cm10 . I just got the boot and then black screen.
Edit:Fixed everything with this lifesaving manual http://androidspin.com/2009/11/06/m...rd-wpartedgoto-ext34-from-adb-no-livecd-reqd/ I got my phone back!
Click to expand...
Click to collapse
Edit:Fixed everything with this lifesaving manual http://androidspin.com/2009/11/06/m...rd-wpartedgoto-ext34-from-adb-no-livecd-reqd/ I got my phone back!
Can't flash anything through recovery. (failed to mount "/cpefs" (Invalid Response)
I recently got this phone and I've been trying to install a custom rom, however, I can't seem to do anything while using TWRP. For some reason the file explorer shows no files and no /storage folder. It also says that the /system partition weights 0MB. I've already tried formatting the /data partition from EXT4 to extFAT, but it won't let me because it cannot mount the "/cpefs" partition, which I've been unable to find any information about.
I can flash the stock firmware trough ODIN, and I can flash the recovery. The internal storage works fine, but nothing shows up when I open TWRP.
I've tried formatting the data partition, repairing it, changing the partition format, wiping, installing a custom rom, installing superSU. But it won't allow me to do any of those things. Either "/data" can't be mounted, or "/cpefs" can't be mounted while formatting /data.
Cepillado said:
I recently got this phone and I've been trying to install a custom rom, however, I can't seem to do anything while using TWRP. For some reason the file explorer shows no files and no /storage folder. It also says that the /system partition weights 0MB. I've already tried formatting the /data partition from EXT4 to extFAT, but it won't let me because it cannot mount the "/cpefs" partition, which I've been unable to find any information about.
I can flash the stock firmware trough ODIN, and I can flash the recovery. The internal storage works fine, but nothing shows up when I open TWRP.
I've tried formatting the data partition, repairing it, changing the partition format, wiping, installing a custom rom, installing superSU. But it won't allow me to do any of those things. Either "/data" can't be mounted, or "/cpefs" can't be mounted while formatting /data.
Click to expand...
Click to collapse
Which phone you're using?
J7 Pro?
Secondly make sure to enable OEM unlock options from the stock ROM's Developer option!
Thirdly check the recovery patches etc of the desired recovery's webiste (you're using) and flash it through the recovery if you're facing the problem!
It'll work, mostly some users said they fixed this by the above mentioned step!
If no luck, maybe someone will sort it out for ya, soon! :laugh:
Good Luck! :good:
sosukeaizen said:
Which phone you're using?
J7 Pro?
Secondly make sure to enable OEM unlock options from the stock ROM's Developer option!
Thirdly check the recovery patches etc of the desired recovery's webiste (you're using) and flash it through the recovery if you're facing the problem!
It'll work, mostly some users said they fixed this by the above mentioned step!
If no luck, maybe someone will sort it out for ya, soon! :laugh:
Good Luck! :good:
Click to expand...
Click to collapse
Thanks for your reply. The model of the phone is SM-J710MN. The OEM unlock option is enabled, otherwise I wouldn't be able to flash the recovery. I am trying to use TWRP. Where would I find a recovery patch for this model?. Everything works fine in the recovery, but it won't let me wipe/format/repair or change ANY partition. It can't mount anything, and the error that I see the most often is that it cannot mount the /cpefs partition.
Cepillado said:
Thanks for your reply. The model of the phone is SM-J710MN. The OEM unlock option is enabled, otherwise I wouldn't be able to flash the recovery. I am trying to use TWRP. Where would I find a recovery patch for this model?. Everything works fine in the recovery, but it won't let me wipe/format/repair or change ANY partition. It can't mount anything, and the error that I see the most often is that it cannot mount the /cpefs partition.
Click to expand...
Click to collapse
try flashing a lower version of the same frimware you've already installed e.g if the latest is nougat 7.1.1 with the recent security update, try flashing with another nougat version that is lower to the recent one's security patch #
I searched for an answer and noticed it's a common issue. I am trying to flash a kernel on to my already flashed rom. I was wondering if there is a more current fix. More importantly, how can this be avoided in the future. Thank you guys!
Its caused by a bug/error with either the filesystem or encryption.
Did you wipe data after flashing the new ROM? Data from stock usually doesn't work with custom ROMs.
Do you have a PIN/password on Android?
Are you using the latest build of TWRP?
Press the menu button at the bottom of the screen in TWRP and post what the error message is in the red text.
It's caused by no root access
djhulk2 said:
It's caused by no root access
Click to expand...
Click to collapse
Something is probably wrong with the data partition. TWRP should always have root access.
Try in TWRP:
Wipe > Format Data > Slide to format
This will erase the data partition, so backup everything to a PC in Android first if needed. It should allow TWRP to mount /data again.
KemikalElite said:
Something is probably wrong with the data partition. TWRP should always have root access.
Try in TWRP:
Wipe > Format Data > Slide to format
This will erase the data partition, so backup everything to a PC in Android first if needed. It should allow TWRP to mount /data again.
Click to expand...
Click to collapse
I've debated on doing this. I'm not worried about losing pictures texts etc as they're backed up.
I read that it essentially leaves the device with no OS. If that's wrong please let me know!
I have found that if I choose Slot A and reboot system it reboots me in to TWRP. If I choose Slot B it runs the OS like normal (except I still have issues using Facebook and it's services).
The ROM works and I can perform all the custom mods on it. I just want to flash a kernel and the problem persists. 0 mb in storage.
It's trial and error at this point. Fail fast fail forward. I have another phone I can use but I love the OnePlus. Any help will be appreciated!
https://andi34.github.io/faq/faq_twrp.html
I'm not willing to risk it until I know how to get the custom ROM on to the storage to flash it.
Yes formating by typing in yes will wipe it all,everything including pictures, with no rom on it at all. If u choose to do that, don't close twrp. Instead you should be able mount after wards, once mounted transfer the magisk zip, twrp, and your custom rom(has to be 1.5gb not 200mb through magisk). Flash magesik, install ram disk twrp, install rom. That was a method I've done before but if u want to keep everything there is other way
fastboot boot twrp.img, that command boots twrp if u have it or don't, installing to ram disk makes it permant...this boot command is just a one time thing each time. It's what I do when new firmware update, I loose root but I regain it each time
Never heard of formating data removing the OS, that would be if you wipe the system and normal wipe is like a factory data reset and therefore will not wipe your phone of the OS
djhulk2 said:
Yes formating by typing in yes will wipe it all,everything including pictures, with no rom on it at all. If u choose to do that, don't close twrp. Instead you should be able mount after wards, once mounted transfer the magisk zip, twrp, and your custom rom(has to be 1.5gb not 200mb through magisk). Flash magesik, install ram disk twrp, install rom. That was a method I've done before but if u want to keep everything there is other way
fastboot boot twrp.img, that command boots twrp if u have it or don't, installing to ram disk makes it permant...this boot command is just a one time thing each time. It's what I do when new firmware update, I loose root but I regain it each time
Click to expand...
Click to collapse
I attempted to format. It said
"failed to mount /data (device or resource busy)
"unable to mount storage"
Try this in recovery, sometimes its known to work.
Wipe > Advanced Wipe > Check Data and press Repair or Change File System > Change File System > Change it to EXT2.
Repeat the same process selecting Ext4
Wipe > Advanced Wipe > Check Data and press Repair or Change File System > Change File System > Change it to back to EXT4.
Try formatting data after this.
drey4211 said:
I attempted to format. It said
"failed to mount /data (device or resource busy)
"unable to mount storage"
Click to expand...
Click to collapse
Since you dont care about the data on the phone I would just do 1 of 2 things. 1st I would reflash twrp on to you phone if that doesn't work then I would just grab the fastboot ROM and just flash your phone back to full stock reroot and install twrp from scratch. I would not try to start repairing partitions. I wouldn't want to worry about screwing up the EFS partition
Well in an update, I formatted the
Storage and now I'm stuck in bootloader screen. It's unlocked but I'm having a hard time flashing a ROM through adb.
I use the twrp version 3.3.1-2
Best would be to just use fast command to boot it
But it should be under wipe/format data/then type in yes
That was what I was trying to have you avoid. If your can boot to fastboot download the fastboot ROM I told you to and run the flash-all.bat file. If your on 9.5.8 make sure you use the fastboot ROM of the same version. Do not flash azip of a different version firmware like 9.5.7.
It happens to me any time I'm in twrp and flash a rom then reflash twrp. It doesn't matter if I flash Magisk or not the issue always happens. What I do is use a USB C flash drive and plug it in when I want to flash/backup a rom. This way I can always access it. After flashing any rom then booting I'm always able to access my internal storage again. It seems like a bug in twrp.
The strange part is when this bug happens your files are encrypted in a 0 folder but you can still copy from your PC to your internal storage while in twrp.
I essentially soft bricked my device. Called OnePlus and they got me up and running. That's awesome that they have that service!
Are you removing all security? Pattern, pin and fingerprints? Are you decrypted? Never had an issue with flashing a ROM causing these issues which is why I'm asking. Something you've done at some point is causing this
I'm not sure what that was. Ironically enough I am now stuck in TWRP boot loop. Hopefully I can figure this out otherwise I have to call oneplus again.
I will admit I may not know everything but it's trial and error. I don't have anyone to really teach me this so I try to read the forums and learn. You guys have been great!
ajsmsg78 said:
It happens to me any time I'm in twrp and flash a rom then reflash twrp. It doesn't matter if I flash Magisk or not the issue always happens. What I do is use a USB C flash drive and plug it in when I want to flash/backup a rom. This way I can always access it. After flashing any rom then booting I'm always able to access my internal storage again. It seems like a bug in twrp.
The strange part is when this bug happens your files are encrypted in a 0 folder but you can still copy from your PC to your internal storage while in twrp.
Click to expand...
Click to collapse
I've the same issue.. did you find a fix? So annoying