Hello,
This is the question and the answer on the same post. (I hope I'm posting on the right place)
As you can read from this post and next three pages since, I have problems with persist partition after being formated by accident with CWM
The problem with formating PERSIST partition is that you will kill your wifi. And will not turn on anymore, buttons will look grayed out, etc. There are many threads about, here on XDA.
And of course, you will be unable to re-flash the partition with rsd or fastboot. (Flashing back your original and full stock will not help)
I was pointed to the fix for this accident which is on this post on Atrix HD section. (credit to the guys who helped me)
And thanks to post above I was able to fix my phone´s wifi and bring back to life.
But, after decompress the IMG file of persist partition I saw the WCNSS_qcom_wlan_nv from stock XT925 ROM has only 28 KB. So small compared with Atrix file. On the post fix above you will find the same file but with 1.7 MB
I tested the fix using both. And any file will work. The one from Atrix thread or the one from your own persist partition or the ones here.
Brief instructions:
You have to copy the file WCNSS_qcom_wlan_nv to the persist partition on home root, aka /persist
(Don't worry if you see an empty folder)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then. Apply the permissions as follows
Then. Restart. your phone will create the rest of the files and links there.
That's it .
Below you will find four files extracted of several Roms. Rename it to delete the words up to W.
However, all files has the same size and same md5. So. Code is the same for each.
Anyway, is up to you.
One interesting thing I watch with this problem is: the MAC Address did not change at all.
You can change between the files and MAC will remain.
Linuxser said:
Hello,
This is the question and the answer on the same post. (I hope I'm posting on the right place)
As you can read from this post and next three pages since, I have problems with persist partition after being formated by accident with CWM
The problem with formating PERSIST partition is that you will kill your wifi. And will not turn on anymore, buttons will look grayed out, etc. There are many threads about, here on XDA.
And of course, you will be unable to re-flash the partition with rsd or fastboot. (Flashing back your original and full stock will not help)
I was pointed to the fix for this accident which is on this post on Atrix HD section. (credit to the guys who helped me)
And thanks to post above I was able to fix my phone´s wifi and bring back to life.
But, after decompress the IMG file of persist partition I saw the WCNSS_qcom_wlan_nv from stock XT925 ROM has only 28 KB. So small compared with Atrix file. On the post fix above you will find the same file but with 1.7 MB
I tested the fix using both. And any file will work. The one from Atrix thread or the one from your own persist partition or the ones here.
Brief instructions:
You have to copy the file WCNSS_qcom_wlan_nv to the persist partition on home root, aka /persist
(Don't worry if you see an empty folder)
View attachment 2661839
Then. Apply the permissions as follows
View attachment 2661840
Then. Restart. your phone will create the rest of the files and links there.
That's it .
Below you will find four files extracted of several Roms. Rename it to delete the words up to W.
However, all files has the same size and same md5. So. Code is the same for each.
Anyway, is up to you.
One interesting thing I watch with this problem is: the MAC Address did not change at all.
You can change between the files and MAC will remain.
Click to expand...
Click to collapse
hello!
I do not understand because if everyone could fix with this method , I could not . I've tried on es explorer, root explorer, x plore and the permissions part too. but the wifi still gret and i not turn on ... Might you know what this happening? can be the own wifi problem (chip ) into the phone?
Hi.
What was you triyng for?
Did you lost the file?
Remember this file is for JB.
Related
When you take a look at the original ROM file for the ACE device you will see this files below:
- hboot... bla, bla, bla (which is self spelling)
- boot.img (...no comment...)
- recovery.img (...no comment again...)
- system.img (...we all know what's inside)
...a few more files and...
- lib.img (...uhhh??? what's this???)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When you open the lib.img there you can find all the files which belongs to the /system/lib folder.
So far - everything seems to be O.k. BUT now my problem and question.
When I use the PD98IMG.zip to install my device and do a backup with the RECOVERY tool and create .tar files - the /system/lib folder within the backup is empty.
When I do a wipe of my device and erase EVERYTHING on it and I try to restore my backup file this fails. This was driving me nearly crazy until I have found that the /lib folder has his own partition.
First I need to restore the original PD98IMG.zip and after this I'm able to successfully restore my backup.
On the one hand this is a great thing because this will offer more space within the /system partition and this will give the DEV's more options for porting ROM's from and to other devices.
On the other hand - where the hell is the /lib folder or partition or whatever located on the DHD device???
Regards!
I think these files are from the Sense 3.0 leaked ROM for ace rite?
For some reason they've made a separate lib.img & if you want to know how exact & where it is extracted during the installation, unpack boot.img & check init.rc / init.spade.rc..
You'll see few lines in either of the files related to extraction of lib.img..
hope this helps
fshami said:
I think these files are from the Sense 3.0 leaked ROM for ace rite?
For some reason they've made a separate lib.img & if you want to know how exact & where it is extracted during the installation, unpack boot.img & check init.rc / init.spade.rc..
You'll see few lines in either of the files related to extraction of lib.img..
hope this helps
Click to expand...
Click to collapse
Yep m8, this is related to the leaked 3.06 ROM for the ACE.
I guess this might be interesting for some DEV's and this is also a thing which needs to be covered by the guy's who are developing the kernels and ramdisk for the ACE.
Also the 4EXT Recovery should be adjust for the ACE device.
From my point of view this is a good solution to get more space on the /system partition.
The next thing is /data/at folder within the original dzdata.img and the sub folders. This folders will be mounted automatically to the /system partition. Don't know how...
Let me give an example for WhatsApp.apk
The original dzdata.img contains this folder structure:
/data/app
/data/at/app
/data/at/lib
/data/at/plugin
If I store this file within /data/at/app I can use WhatsApp without creating an hard link to the /system/apps folder.
All this things might be interesting for the DEV's.
Just a quick (related) question. How do you unpack dzdata.img?
It might not be a hidden/new partition. Quite the contrary. Notice that with the 3.06, there's a new hboot shipped. I'm theorizing, that it changes the partition layout, chopping up /system into smaller partitions. Now, as we all probably use the eng hboot and a custom update-script for unsigned roms, this doesn't concern us.
Or at least that's my theory. I remember in the sapphire/magic days, the new radio would allot more flash space to /system to fit in SenseUI, while old radio would allot more space to /data.
So this morning I made a Nandroid backup (everything was acting normal) and I flashed the LeeDroid ROM then his insecure boot image since my phone wouldn't boot without that. Since then, my phone just will not recognize the internal SD card from Android (although, it is fine in Recovery). I posted about this in the LeeDroid thread because I thought it was ROM specific, but I just restored my Nandroid and the issue persisted. I have no clue what happened here. Any ideas?
Not sure if it is related but since I flashed the new ROM (even after restoring) I get that Android is Upgrading (runs through all apps optimizing) screen on each boot. Is this related to the boot img? Would the boot img have restored when I ran the Nandroid?
hah2110 said:
Not sure if it is related but since I flashed the new ROM (even after restoring) I get that Android is Upgrading (runs through all apps optimizing) screen on each boot. Is this related to the boot img? Would the boot img have restored when I ran the Nandroid?
Click to expand...
Click to collapse
Hi I saw your issue in the LeoDroid thread also. I think if I were you I would flash the stock HTC recovery and do a factory reset with that. Or flash a RUU file.
To answer your question though, if you restore a nandroid it does include your old boot.img
dc211 said:
Hi I saw your issue in the LeoDroid thread also. I think if I were you I would flash the stock HTC recovery and do a factory reset with that. Or flash a RUU file.
To answer your question though, if you restore a nandroid it does include your old boot.img
Click to expand...
Click to collapse
Why would the recovery be involved though? I don't get what caused this. The Recovery console sees my memory card just fine.
Ok so in ROM Toolbox - Root Browser, the sdcard shows up as a file, not a folder. When I click on it, it has empty contents. Does this help? I have full permissions on the file. The sdcard is pointed to /mnt/sdcard but when I specifically go there, it is empty. When I check permissions on sdcard under mnt, they are all unchecked and when I check them off, it is unsuccessful... ARGH
Could someone post their fstab file for me so I can mimic it and push to the phone, I think it is related.
Thanks
Ok so I do have an fstab file and here are the contents
dev_mount sdcard /mnt/sdcard emmc /devices/platform/msm_sdcc.1/mmc_host
Is that correct? Why does the mount command in the shell day fstab not found or corrupt?
Sent from my HTC One S using Tapatalk 2
May be a stupid question, but in settings it doesn't show anything under Phone Storage? What do you see there? Can you try to format it? Can you put a screen shot of your Storage settings? Here is what mine looks like.
You say you can access SDCard from Recovery, did you try to go to Mount and Storage and format SDCard?
FYI I'm on leedroid.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It says phone storage and total space and available space are "unavailable".
hah2110 said:
It says phone storage and total space and available space are "unavailable".
Click to expand...
Click to collapse
Do you have important files on the sdcard your trying to recover? If not have you gone back to a stock recovery and tried to clear storage yet?
I'm running ICS v9.3.4.17 on my unlocked (but not yet rooted) TF300T. It's essentially in the same state as coming out of the box (no apps, using a temp gmail account to initially keep it "clean" while unlocking, installing nvflash, etc). I followed AndroidRoot.mobi's nvflash install instructions and everything appeared to go correctly. Is there any way to know my files were generated correctly? Below is a screen print of all my backup files:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm not sure if the file sizes are version or device specific, but are they all there and approximately the expected size?
I've copied them to 3 locations, but got thinking about it. Call me overly backup conscious, but I'd be better covered with two separately generated sets. If one is bad, it doesn't matter how many copies I have. But having another set will give me a better chance to recover if the need arises (and if I find I have a bad nvflash blob file).
For other's info, I'd originally asked about re-running the "fastboot -i 0x0b05 boot nvfblobgen.img" command to generate a new set. In preparation for recreating one, I moved the /sdcard/AndroidRoot folder to another location. I happened to reboot and noticed the AndroidRoot folder and its contents are automatically recreated upon rebooting. So for these files, there's no need to re-run the fastboot command for another set.
I did notice one "issue" viewing the /sdcard/AndroidRoot folder in Windows 7 after the initial reboot. While they display fine via my TF300T's File Manager, it took either disconnecting/reconnecting my usb cable or rebooting one more time for them to display correctly in Windows 7.
I still plan on re-running nvflash to create a new bricksafe.img, factory-config.img, and unlock-token.img set just to be extra safe.
wha2do said:
I'm running ICS v9.3.4.17 on my unlocked (but not yet rooted) TF300T. It's essentially in the same state as coming out of the box (no apps, using a temp gmail account to initially keep it "clean" while unlocking, installing nvflash, etc). I followed AndroidRoot.mobi's nvflash install instructions and everything appeared to go correctly. Is there any way to know my files were generated correctly? Below is a screen print of all my backup files:
I'm not sure if the file sizes are version or device specific, but are they all there and approximately the expected size?
I've copied them to 3 locations, but got thinking about it. Call me overly backup conscious, but I'd be better covered with two separately generated sets. If one is bad, doesn't matter how many copies I have. But having another set will give me a better chance to recover if the need arises (and I find I have a bad nvflash blob file).
Can I rerun the "fastboot -i 0x0b05 boot nvfblobgen.img" command to generate a new set? While I'm at it, I figure I should be able to rerun nvflash and create a new bricksafe.img, factory-config.img, and unlock-token.img... Is that possible and does it make sense?
Thanks!
Click to expand...
Click to collapse
I have the same files and even tried recovering with the bricksafe.img, same sizes aswell.
totaltmega said:
I have the same files and even tried recovering with the bricksafe.img, same sizes aswell.
Click to expand...
Click to collapse
Thanks for the confirmation. I dislike relying on an unverified backup only to find out too late that it's not valid or usable! And out of curiosity, you went through a recovery successfully? It'd be great if you had a link to the thread/post you followed.
I had missed one step after upgrading the jb bootloader (didnt force shutdown after upgrade, just let it load) and were stuck with official jb with no root or recovery, so i tried to use nv flash and messed up even more , post 3 in this thread helped me get the bootloader to work so I cound install TWRP again using fastboot.
I do not recommend testing it "just for fun" but it worked for me. Search for "nvflash restore" if you have any problems.
totaltmega said:
I have the same files and even tried recovering with the bricksafe.img, same sizes aswell.
Click to expand...
Click to collapse
I'm curious about your sizes matching mine; more specifically my unlock-token.img file size matching yours. Maybe fine if you used your unlock-token.img file when you did your recovery. If didn't use, might want to (if you still can) go back and recreate it and compare with your original...see below why.
Being OCD on backups, I created a new bricksafe.img, factory-config.img, and unlock-token.img and compared the files. I was a bit surprised to see factory-config.img and unlock-token.img were not exact copies of the original set created. Factory-config.img had some bits that varied, but was mostly the same. I'm figuring it's something "internal" as I haven't changed anything on my table between runs and is fine...
But seeing a large size change between the two unlock-token.img files, I went back through my logs, etc. Lo and behold, I had a typo and hadn't changed the partition from 14 to 7! So I had made duplicate backups of the factory-config partition by accident. The actual file size is 8,192 KB and not 5,120 KB.
That could have been a real problem down the road if ever I need to recover (assuming this file is vital to the particular recovery procedure). So if nothing else...the lesson to learn is always double check what you've done to make sure!
Hi all,
everytime I reboot the phone I get this error message.
I think it's because I used titanium backup to delete 3 files which had to do with korean / hindu and another language file or something similar...
besides the screenshot, I have no idea how to provide logs.
Appreciate the assistance.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Attached LOGCAT
Pretty sure it's the files you deleted. Are you on stock rom? If so, just flash the system.img. If custom Rom, dirty flash it
If I'll flash system.img, then I'll lose some settings.
Is there a way to download the system apps or open the .img file?
if none of the above, can you please see if there's an error in the logcat?
gil80 said:
If I'll flash system.img, then I'll lose some settings.
Is there a way to download the system apps or open the .img file?
if none of the above, can you please see if there's an error in the logcat?
Click to expand...
Click to collapse
Download a stock rom zip (make sure you get the deodex or odex one that matches your current set up) and open zip. Browse to /system/app/ and pick the apks you need. Move them to your internal storage and use a file explorer with root access to copy to the /system/app folder in your phone. Make sure you change the permissions and reboot. IF that is what caused it, that will get you back to normal. If it doesn't, then just dirty flash. You really won't lose that much stuff.
Also, sometimes just clearing caches and fixing permissions in recovery can help, and if it doesn't, it won't make it worse.
If you need more help, make sure you post quote or hit me up on Hangouts.
es0tericcha0s said:
Download a stock rom zip (make sure you get the deodex or odex one that matches your current set up) and open zip. Browse to /system/app/ and pick the apks you need. Move them to your internal storage and use a file explorer with root access to copy to the /system/app folder in your phone. Make sure you change the permissions and reboot. IF that is what caused it, that will get you back to normal. If it doesn't, then just dirty flash. You really won't lose that much stuff.
Also, sometimes just clearing caches and fixing permissions in recovery can help, and if it doesn't, it won't make it worse.
If you need more help, make sure you post quote or hit me up on Hangouts.
Click to expand...
Click to collapse
looking at the logcat I uploaded I searched for "fatal" and it found 1 fatal issue which is com.android.systemui and it appears to be something with the battery icon which I changed using GravityBox. But the change was a week ago so I don't know what was changed.
Switching back to stock battery icon and I no longer have this issue.
But it seems that I have more errors on the log file. Do you of a forum which can assist with understanding the errors I have and how to fix them?
gil80 said:
looking at the logcat I uploaded I searched for "fatal" and it found 1 fatal issue which is com.android.systemui and it appears to be something with the battery icon which I changed using GravityBox. But the change was a week ago so I don't know what was changed.
Switching back to stock battery icon and I no longer have this issue.
But it seems that I have more errors on the log file. Do you of a forum which can assist with understanding the errors I have and how to fix them?
Click to expand...
Click to collapse
I get this after a titanium backup restore. No idea why it does it I mean isn't that what titanium backup is for?
Hello everyone, I bought an LG L70 Dual D325F which was soft-bricked hoping it as to be easily fixed via flashing the stock firmware, but to my great surprise, I was unable to access the download mode, I was facing the "DemiGod Crash Handler : DBI Err Fatal!"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then I tried this tutorial, but I after following the thread, the device switch to Qualcomm HS-USB QDLoader 9008, thus I started searching a solution, then I found out about this method, which involved the use of an SD Card, thus it did worked out, and I was able to boot to download mode in order to flash the firmware, but the firmware flashing was getting stuck and then reset while displaying 'ASSERT' in Red at 7%, sometimes at 15% and the maximum I did reach was 33%, before restarting again.
Then after spending hours on google, I found out that the it is normal and that I should keep forcing until 100%, but after my attempt to 33%, the process wouldn't past 7%, thus I googled for another method then I came across a method involving BoardDiag 3.99, thus when I tried it out, but during the test, it EMMC test fails and output the following:
Note: I used the other driver, this was just to show the error which was being output.
Despite that, I did continue with the method and flash the imgs. Then I decided to look inside the files and found out the partition.txt was incorrect, thus I did calculate and created my own using the files from my stock extracted firmware. But still it didn't worked out, thus after I googled, I came across a tutorial which was meant for LG G3 unbrick using BoardDiag, and it the tutorial, the guy mentioned that use the option erase and then switch it back to Read/Write, and it should fix the error, but it didn't worked out. and the EMMC partition was completely wiped. then check I checked the rawprogram xml in BoardDiag, It looked like it was incorrect, but I wasn't able to edit it properly, so I gave up on this one.
Then the next day, I googled and came across a tutorial from XDA that shows how to fix an LG L7 P715, so I started following the tutorial as from Step 4, but I was unable to continue as the application was search for the Sahara XML, I wasn't able to get my hands on. After some research I found out the provided files wasn't compatible with my device, thus I finally got my hands on some of the files.
1. MPRG8x10.hex (It is the eMMC programmer file to help download the bootloader into eMMC, and I guess it can be used with all Snapdragon 200 MSM8x10 processor. And I've already got this file somehow).
2. 8x10_msimage.mbn (It is the bootloader image file and specific to the phone. I wasn't able to get the file, because I wasn't able to determine the proper bootloader file for the device from the stock firmware.)
3. Raw XML and Patch XML files (These XML files contain the partition details of phone. And I don't have these two. And I was unable to even a edit the files properly as I wasn't able to exactly understand what was going on, so I gave up on this one.).
Then the next day, I tried again using the SD Card method, but once the SD Card is inserted, the device shows the Demi-God Crash error. Thus when I hooked it up to my computer, I saw the EMMC as a removable partition but I was unable to format it, thus I tried writing the partition table (PrimaryGPT) to the device, but no success. Then I download a full dump for the D325 and wrote it to the EMMC, but still fails to boot as the EMMC is clean once I unplug it and plug it again. Thus when I hooked up the SD Card through a card reader to my device, it shows that the SD Card was partitioned as a regular emmc for a phone to boot, I did try to to backup the partition table and then restore it to the EMMC, but still in vain. Then I tried to write the files manually using linux to partitions manually, including the system partition, which I did merge the different bin files to one img and then flash it, I took about 10min to fully write it. But still it didn't boot. Well I'm stuck here (am currently trying to write the full dump to the SD card and try to boot of it, if it does boot). I hope that someone will be able to help me out to fix this issue. Thanks in Advance!
Hello,
As a Senior Member you should be able to navigate the site and find the answers you are looking for.
XDA Assist is to help new members navigate the site.
Please have a look at the 2 sticky threads at the top of XDA Assist if you have any further questions.
Thread closed.
Thanks,
Sloth