Hi everyone. Got a bootloop, so had to format the persist partition. I made a backup of it with adb before formatting, but forgot to save permissions/owners of every file.
Could anyone just make an "ls -l" in all folders of /persist? Thank you.
P.S. I'd appreciate if anyone makes a full image backup of /dev/block/platform/msm_sdcc.1/by-name/persist
To make it, just do a dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/sdcard/persist.img and post the file on any file hosting.
Slavon-93 said:
Hi everyone. Got a bootloop, so had to format the persist partition. I made a backup of it with adb before formatting, but forgot to save permissions/owners of every file.
Could anyone just make an "ls -l" in all folders of /persist? Thank you.
P.S. I'd appreciate if anyone makes a full image backup of /dev/block/platform/msm_sdcc.1/by-name/persist
To make it, just do a dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/sdcard/persist.img and post the file on any file hosting.
Click to expand...
Click to collapse
Why don't you just try doing a factory reset after bootloop?
Anyways,here's the file that you were asking for-
https://drive.google.com/file/d/0BxysuRdzsJeWNi02b0NmSUVwbE0/view?usp=drivesdk
Mr.Ak said:
Why don't you just try doing a factory reset after bootloop?
Anyways,here's the file that you were asking for-
https://drive.google.com/file/d/0BxysuRdzsJeWNi02b0NmSUVwbE0/view?usp=drivesdk
Click to expand...
Click to collapse
Because it was a bootloop just right after a flashed the ROM on a completely clean factory reset device. Now I understand that it was a problem with the ROM, that's why I made a backup. And your image will help me know if I miss any files in this partition and know their permissions.
Slavon-93 said:
Because it was a bootloop just right after a flashed the ROM on a completely clean factory reset device. Now I understand that it was a problem with the ROM, that's why I made a backup. And your image will help me know if I miss any files in this partition and know their permissions.
Click to expand...
Click to collapse
Which ROM?
Mr.Ak said:
Which ROM?
Click to expand...
Click to collapse
hyperUnicorns. For some reason any build I try to install since the end of June gives me reboots. I thought it was some incompatibility with Multirom 33e and MIUI, but after I flashed the full Cyanogen package, nothing changed, that led me to google and some posts, saying it can be a damage of persist partition.
Slavon-93 said:
hyperUnicorns. For some reason any build I try to install since the end of June gives me reboots. I thought it was some incompatibility with Multirom 33e and MIUI, but after I flashed the full Cyanogen package, nothing changed, that led me to google and some posts, saying it can be a damage of persist partition.
Click to expand...
Click to collapse
That rom worked fine for me..maybe it doesn't support multi-rom.
I think you should ask on the rom's thread.
Related
Hello,
I recently rooted and installed a custom ROM CM10 nightly onto my transformer, and proceeded to wipe data as normal. I went to do it, and it was taking a long time, 5-6-7-8 mins passed and I thought something is wrong. So I force turned it off. Not that all it said for that time was "formatting /data..." or something.
Well, it failed to boot as expected, so I tried wiping again with no luck. Went and flashed TWRP recovery and it's showing errors:
E:Unable to mount '/data' (tw_mount)
E:failed to mount /data (Invalid argument)
I'm not sure how to proceed due to lack of knowledge. I noticed there's a file manager and terminal on this recovery so perhaps it can be fixed using those, or ADB or something.
Either way, I would like to request help from the TF300T community.
Thanks in advance,
Kris
Problem solved. Made a new blob without the bootloader included and flash it, then the system told me the data was unreadable and it fixed itself after that.
linkandzelda said:
Problem solved. Made a new blob without the bootloader included and flash it, then the system told me the data was unreadable and it fixed itself after that.
Click to expand...
Click to collapse
Greetings. I did, so far as I can tell, this exact same thing. I feel like I'm taking crazy pills.
Kind of wandering if someone put a "wipe data" label on the "destroy your transformer" button by mistake.
Can you please elaborate on what you mean by "made a new blob without the bootloader included"?
Are you meaning new zip without the boot.blob? I'm tripping over the words. Or maybe I simply do not understand what you are meaning.
I would be so grateful if I could get anywhere with this.
ogredeschnique said:
Greetings. I did, so far as I can tell, this exact same thing. I feel like I'm taking crazy pills.
Kind of wandering if someone put a "wipe data" label on the "destroy your transformer" button by mistake.
Can you please elaborate on what you mean by "made a new blob without the bootloader included"?
Are you meaning new zip without the boot.blob? I'm tripping over the words. Or maybe I simply do not understand what you are meaning.
I would be so grateful if I could get anywhere with this.
Click to expand...
Click to collapse
I don't remember the specifics, but are you familiar with using fastboot to flash .blob files? You use this to flash the new recoveries over, etc. First off I used the blob tools I found around here to extract the various parts of the stock blob I got from the ASUS site. After that, I rebuilt it simply containing the system and the kernel. Then I flashed that .blob file to the device, and it decided to boot up and tell me my data was ruined and gave me the option of fixing it. So, I let it fix itself and that's how I got out if it.
linkandzelda said:
I don't remember the specifics, but are you familiar with using fastboot to flash .blob files? You use this to flash the new recoveries over, etc. First off I used the blob tools I found around here to extract the various parts of the stock blob I got from the ASUS site. After that, I rebuilt it simply containing the system and the kernel. Then I flashed that .blob file to the device, and it decided to boot up and tell me my data was ruined and gave me the option of fixing it. So, I let it fix itself and that's how I got out if it.
Click to expand...
Click to collapse
i had the same problem during flashing cm10 on my brandnew tf300t.
the system could not mount /data...
...solved this problem with the "wipe -> format data" command in TWRP.
sounds too easy?
How can you Wipe Data, if the /data isn't/can't be mounted?
I'm having this same issue with my RazrMaxx...
I posted my issue here: http://forum.xda-developers.com/showthread.php?p=35222826#post35222826
Z1013 said:
i had the same problem during flashing cm10 on my brandnew tf300t.
the system could not mount /data...
...solved this problem with the "wipe -> format data" command in TWRP.
sounds too easy?
Click to expand...
Click to collapse
Well, in my opinion, I think the rom wasn't readable or working. If you have taken a backup before flashing the nightly rom, you can restore it.
linkandzelda said:
I don't remember the specifics, but are you familiar with using fastboot to flash .blob files? You use this to flash the new recoveries over, etc. First off I used the blob tools I found around here to extract the various parts of the stock blob I got from the ASUS site. After that, I rebuilt it simply containing the system and the kernel. Then I flashed that .blob file to the device, and it decided to boot up and tell me my data was ruined and gave me the option of fixing it. So, I let it fix itself and that's how I got out if it.
Click to expand...
Click to collapse
Just did this with my tf300t last night. Do you still have the blob files?
After formatting /system (via CWM) and installing CM11 the WiFi on my I727 fails to turn on. CatLog reports "WifiStateMachine: Failed to load driver".
I've read in various other threads that an Android device's /persist directory should have the driver files, but that directory is empty (did "ls -l" through rooted shell). Would anyone be able to post a listing of that directory from their 'rocket or otherwise provide some insight into what is going on here?
Thanks,
INCANDE
INCANDE said:
After formatting /system (via CWM) and installing CM11 the WiFi on my I727 fails to turn on. CatLog reports "WifiStateMachine: Failed to load driver".
I've read in various other threads that an Android device's /persist directory should have the driver files, but that directory is empty (did "ls -l" through rooted shell). Would anyone be able to post a listing of that directory from their 'rocket or otherwise provide some incite into what is going on here?
Thanks,
INCANDE
Click to expand...
Click to collapse
I think you should not format /system. I have seen this causing problems to other devices too.. I suggest you to try flash a ROM without flashing /system.. You can either do factory reset and wipe all cache..
na4co said:
I think you should not format /system. I have seen this causing problems to other devices too.. I suggest you to try flash a ROM without flashing /system.. You can either do factory reset and wipe all cache..
Click to expand...
Click to collapse
Thanks. I have to admit I've heard the same thing, but I did so to rid the device of GApps (including Google Play/Services). I'd be curious to know of a better way of accomplishing that.
INCANDE said:
Thanks. I have to admit I've heard the same thing, but I did so to rid the device of GApps (including Google Play/Services). I'd be curious to know of a better way of accomplishing that.
Click to expand...
Click to collapse
A better way is you can flash ROM without gapps if you don't want them..
na4co said:
A better way is you can flash ROM without gapps if you don't want them..
Click to expand...
Click to collapse
+1 or if you've already flashed them and want to get rid of them just delete 70-gapps.sh from /system/addon.d and re-flash the ROM.
I'm noticing that FlashFire has the option to backup the system parition file based. I'm wondering if someone who has flashed the PR ROM could simply do a restore of a STOCK ATT system partition backed up this way and if it would work? If anyone wants to try, I can make a backup and upload it and post a link.. Let me know!
petermg said:
I'm noticing that FlashFire has the option to backup the system parition file based. I'm wondering if someone who has flashed the PR ROM could simply do a restore of a STOCK ATT system partition backed up this way and if it would work? If anyone wants to try, I can make a backup and upload it and post a link.. Let me know!
Click to expand...
Click to collapse
Sounds like a hard brick waiting to happen.
uly609 said:
Sounds like a hard brick waiting to happen.
Click to expand...
Click to collapse
Yeah.. probably right. It was real late when I posted that LOL
Actually doing a system restore via file based shouldn't hard brick the phone. Only if it was raw based possibly, but either way it would only be the system position so the kdz/tot would still be able to be flashed to the phone as before. This might work! Or at least be a good base to try.
petermg said:
Actually doing a system restore via file based shouldn't hard brick the phone. Only if it was raw based possibly, but either way it would only be the system position so the kdz/tot would still be able to be flashed to the phone as before. This might work! Or at least be a good base to try.
Click to expand...
Click to collapse
I agree with this theory. It should only flash the system over the system. You would have to make sure the boot loader is correct for the system rom. So say a 10b bootloader for an equivalent 10bPR rom.
(If any of the above is confusing or slightly off, I blame it on the fact I have been battling a bad virus this week with a bad headache.)
I just warrantied my PR rom device a few weeks ago, or else I would have tried this for you.
Edit: You would also have to edit the script in the file to flash to designate the correct partition to flash the system to.
CAG-man said:
I agree with this theory. It should only flash the system over the system. You would have to make sure the boot loader is correct for the system rom. So say a 10b bootloader for an equivalent 10bPR rom.
(If any of the above is confusing or slightly off, I blame it on the fact I have been battling a bad virus this week with a bad headache.)
I just warrantied my PR rom device a few weeks ago, or else I would have tried this for you.
Edit: You would also have to edit the script in the file to flash to designate the correct partition to flash the system to.
Click to expand...
Click to collapse
Unless it just extracts the tar'd files it copied from the system partition of the stock device. Still some ambiguity regarding that app. For example, it shows no option to allow me to make backups on the external SD card...
petermg said:
Unless it just extracts the tar'd files it copied from the system partition of the stock device. Still some ambiguity regarding that app. For example, it shows no option to allow me to make backups on the external SD card...
Click to expand...
Click to collapse
I would think it still needs an address as to where to put the extracted files.
I will look and see if I have any twrp backups on my computer from some of the roms I made. I have never fully looked through and studied the backups as much as I used them for system dumps. It just seems to make since that the recovery would need to know where to write the system files. Just flashing an app is alright without the address.
In writing the flashing script for ROMs, I have always had to give the recovery the address as to where to write the system files or else it would result in a flash failure or soft brick.
I may be writing my scripts wrong too. I just know what works for me.
My mmc got fried while formatting my /system and /data partition using twrp, so I moved my /system and /data partition to sd-ext partitions which I made using 4EXT recovery using delta-roh Turbo-DATA mod.
Here is what my partitions look like
1st partition -> SD-card -> vfat
2nd partition -> sd-ext -> /system -> ext4
3rd partition -> sd-ext2 -> /data -> ext4
Currently I have cm-11 by Ivanich on my phone but cant install Gapps. I ve been editing the update-binary in the Gapps zip but it always returns me the error that
"This Gapps pkg is for android version 4.4.x ...... Your rom : 2.3.7"
But I have a kitkat installed. I am guessing that its not reading the build.prop correctly. So how do I install Gapps ?
Any help is appreciated ...
More info about my phone
S-off
Bootloader unlocked
Rooted
Recovery : 4EXT
Rom : CM-11 by Ivanich
A recovery with modified ramdisk might be necessary. Maybe @hinxnz can help you with that.
Ok. Can i use the android kitchen to unpack recovery.img and modify it ?
If yes what modifications do I need to make it work ?
Wahaj.47 said:
Ok. Can i use the android kitchen to unpack recovery.img and modify it ?
If yes what modifications do I need to make it work ?
Click to expand...
Click to collapse
Yes you can use AIK for recovery image, you'll need to modify fstab like you did with the boot image. I have never unpacked 4ext though and it's a bit outdated now but I've always used ivanich's twrp builds when modifying recovery.
Otherwise you could just modify the updater script in the gapps package to not mount data etc but this will have to be done every time.
Edit: I just read your first post and I'm not sure how you even flashed ROM if your system partition is bad, did you modify the ROMs updater script to flash it to your new system on sd-ext or something? If so gapps could be reading your old system, then I'm thinking is it actually bad or just your data partition is...
hinxnz said:
Yes you can use AIK for recovery image, you'll need to modify fstab like you did with the boot image. I have never unpacked 4ext though and it's a bit outdated now but I've always used ivanich's twrp builds when modifying recovery.
Otherwise you could just modify the updater script in the gapps package to not mount data etc but this will have to be done every time.
Edit: I just read your first post and I'm not sure how you even flashed ROM if your system partition is bad, did you modify the ROMs updater script to flash it to your new system on sd-ext or something? If so gapps could be reading your old system, then I'm thinking is it actually bad or just your data partition is...
Click to expand...
Click to collapse
Yep I modified the roms updater script to mount sd-ext as /system and sd-ext2 as /data.
I cant modify the gapps updater script because its just a dummy file and all the code is in update binary and it needs some experienced programming .
I ll try modifying the recovery's fstab and post the results.
"/etc/recovery.fstab" is that the file I need to modify ?
Edit:
I also tried adding the gapps to the rom zip itself and flashed it but that made the rom useless because it kept rebooting.
Wahaj.47 said:
Yep I modified the roms updater script to mount sd-ext as /system and sd-ext2 as /data.
I cant modify the gapps updater script because its just a dummy file and all the code is in update binary and it needs some experienced programming .
I ll try modifying the recovery's fstab and post the results.
"/etc/recovery.fstab" is that the file I need to modify ?
Edit:
I also tried adding the gapps to the rom zip itself and flashed it but that made the rom useless because it kept rebooting.
Click to expand...
Click to collapse
Just open update binary with a program like note++ if using windows.
I haven't modified recovery for a little while and haven't got the files in front of me but there are a couple to modify to get everything working, just have a peek round in the folders.
hinxnz said:
Just open update binary with a program like note++ if using windows.
I haven't modified recovery for a little while and haven't got the files in front of me but there are a couple to modify to get everything working, just have a peek round in the folders.
Click to expand...
Click to collapse
I have been messing around with the update binary but honestly man I ve got know idea, I am not even close to fixing the damn problem.
I haven't tried modifying the recovery fstab yet. I am gonna do it and see what happens.
Wahaj.47 said:
I have been messing around with the update binary but honestly man I ve got know idea, I am not even close to fixing the damn problem.
I haven't tried modifying the recovery fstab yet. I am gonna do it and see what happens.
Click to expand...
Click to collapse
If you want, upload your recovery image and I'll modify it for you.
hinxnz said:
If you want, upload your recovery image and I'll modify it for you.
Click to expand...
Click to collapse
First I tried using the google installer to install gapps but playstore kept crashing so I ruled that out.
Then I modified the recovery.img and flashed pa-gapps-4.4 and it worked . The playstore was still crashing but updating google play service has fixed it, but I am not sure about this, gonna keep testing for a while. Atleast now I have gapps
Thank you very much
I was getting random reboots on cm-11 so I ve moved on to cm-12.1. Can this be a battery fault ?
Wahaj.47 said:
I was getting random reboots on cm-11 so I ve moved on to cm-12.1. Can this be a battery fault ?
Click to expand...
Click to collapse
If you mean shutdowns then yes, otherwise if rebooting then it's something else.
If a full reboot happens, it will show in /proc/last_kmsg
hinxnz said:
If you mean shutdowns then yes, otherwise if rebooting then it's something else.
If a full reboot happens, it will show in /proc/last_kmsg
Click to expand...
Click to collapse
I am not experiencing any reboots on cm-12.1, but its lagging a bit. And phone turns off when taking picture with flash on.
Hi, you can see my question.
I've try wipe, but only data works. And no change.
I've try to réinstall the custom rom, you can see result.
Ttry to flash stock rom with odin, odin failed.
and try to réinitialise with smart switch ( he say me i havent tow slot for sim, i know). And ... nothing change.
The device has been already root, and i've already change for this custom rom with no problem.
Thanks for your help.
Edit: with format data after wipe data and after reboot on twrp, no red line, i've install the rom. good : i've the rom, bad : the problem is come back.
Just for to be sur, this screenshoot is just a example. Other installation make me the same error.
This rom work really good and other people haven't any problems.
Send me the kernel and I disable /data ecncrypting for you
DThrawn said:
Hi, you can see my question.
I've try wipe, but only data works. And no change.
I've try to réinstall the custom rom, you can see result.
Ttry to flash stock rom with odin, odin failed.
and try to réinitialise with smart switch ( he say me i havent tow slot for sim, i know). And ... nothing change.
The device has been already root, and i've already change for this custom rom with no problem.
Thanks for your help.
Edit: with format data after wipe data and after reboot on twrp, no red line, i've install the rom. good : i've the rom, bad : the problem is come back.
Click to expand...
Click to collapse
do't worry it is normal i explain you
when you format with twr the data is readable
and the first time starting system Samsung encrypt the file so txr can't mount again data
but don't care about it
DThrawn said:
Edit: with format data after wipe data and after reboot on twrp, no red line, i've install the rom. good : i've the rom, bad : the problem is come back.
Click to expand...
Click to collapse
It's all because kernel has encrypted /data and data encrypts after a reboot. Some changes in the kernel solve your problem. Data will mount always after some changes in the kernel
maxx35000 said:
do't worry it is normal i explain you
when you format with twr the data is readable
and the first time starting system Samsung encrypt the file so txr can't mount again data
but don't care about it
Click to expand...
Click to collapse
Forgetten said:
It's all because kernel has encrypted /data and data encrypts after a reboot. Some changes in the kernel solve your problem. Data will mount always after some changes in the kernel
Click to expand...
Click to collapse
Ok, I understand more why it's all my recovery is down. my device work good also with what you said i'm more quiet.
But why reinitialisation with switch, let the same problem. The kernel is not reinitialised to ?
I've try to modify selinux permissions before to install a sound mod and create an folder init.d. Is it possible the problem stay cause that?
DThrawn said:
Ok, I understand more why it's all my recovery is down. my device work good also with what you said i'm more quiet.
But why reinitialisation with switch, let the same problem. The kernel is not reinitialised to ?
I've try to modify selinux permissions before to install a sound mod and create an folder init.d. Is it possible the problem stay cause that?
Click to expand...
Click to collapse
I don't sure about that but you should mount your /data using patched kernel. Send it to pm and I patch them to mount data fully
Forgetten said:
I don't sure about that but you should mount your /data using patched kernel. Send it to pm and I patch them to mount data fully
Click to expand...
Click to collapse
I'm a old beginner, I don't know where is the kernel and I don't know if it's sur to give mine cause i don't know what information of my device is in.
I appreciate your help but i can't give anything what a I don't know.
DThrawn said:
I'm a old beginner, I don't know where is the kernel and I don't know if it's sur to give mine cause i don't know what information of my device is in.
I appreciate your help but i can't give anything what a I don't know.
Click to expand...
Click to collapse
OK. Say. Which ROM do you use?
Forgetten said:
OK. Say. Which ROM do you use?
Click to expand...
Click to collapse
I use the evo-grace V1.2 J7 2016, but I ve never had problem before trying install sound mod with modification of selinux permission.
Unmount data always but not important, but some install, wipe or backup impossible it's new.
Flash before formatting data.
https://www.androidfilehost.com/?fid=24591000424951049
ashyx said:
Flash before formatting data.
https://www.androidfilehost.com/?fid=24591000424951049
Click to expand...
Click to collapse
Thanks, work realy fine. no red line at all.
Also i lose root and the problem come back when i try to reinstall the rom evo-grace, cause she's rooted and she has its own no encrypted file, i think.
DThrawn said:
Thanks, work realy fine. no red line at all.
Also i lose root and the problem come back when i try to reinstall the rom evo-grace, cause she's rooted and she has its own no encrypted file, i think.
Click to expand...
Click to collapse
When you flash anything that modifies or replaces the boot partition you need to reflash the patch afterwards or the data partition will be re-encrypted.
ashyx said:
When you flash anything that modifies or replaces the boot partition you need to reflash the patch afterwards or the data partition will re-encrypted.
Click to expand...
Click to collapse
Yes, i've can make some backup and install like that. It's help me. And now i've install permanetly the rom of max35000, , he have make some good modification. Problem solved with help of you to.
Thanks for have take a time for look that.
Forgetten said:
Send me the kernel and I disable /data ecncrypting for you
Click to expand...
Click to collapse
Hi my bro
Please help me
How can i make disablr / data ecncrypting ??
I have j710f frp on with pattern
Can i open it without losing data ??
---------- Post added at 10:09 PM ---------- Previous post was at 10:00 PM ----------
How can i make a kenel to disable data ecncrypting ??