Database Info

[Q] task rpcrouter:15 blocked (CDMA)

Same as posted here "I have an HTC [differing: Touch Pro (Alltel CDMA)]. I followed the instruction on forum.xda-developers.com for [FRX*] but it [enters an endless loop] at "task rpcrouter:15 blocked for more than 120 sec". The solution that worked in that link does not solve the same problem with a CDMA RAPH800.
The solution given there (paraphrased from that thread):
Link to the fix. The issue is caused by not having a data plan; the install gets stuck in a loop looking for a signal.
The solution that worked for a GSM phone
download RIL file from http://forum.xda-developers.com/atta...9&d=1302817139 and place in the root of microsd.
download rootfs file from http://www.megaupload.com/?d=1NGCVCTT and place in the root of microso.
add to the end of /conf/froyo.user.conf file "/sdcard/libhtcgeneric-ril.so /lib/froyo/libhtcgeneric-ril.so" before the last "}"
Please help me find a solution for a CDMA phone - next month I'd like to take a dozen of these phones and use them as learning aids in a construction course for laborers, but I cannot start testing construction applications since I cannot get the OS to work.

I'm curious as to what happens when you format your microSD and run FRX7.1MR without anything additional. Could I get you to try this method without the additional stuff?
To be explicit, I'd like you to format your microSD with something other than the Windows method and I'd like you to download THIS (if you haven't already) and THIS. Extract the contents of both files to the root of your microSD. You should see a folder called "FRX07.1" and under that folder, you should see 3 folders and 7 files. Move the contents of that folder up to the root of the microSD. Look under the folder called "STARTUPS" and locate your device type (ie RAPH800) and copy over to the root of your microSD. Once done, run Haret on your phone and let me know what happens.

do you have an application you suggest for "format your microSD with something other than the Windows method"; sourceforge did not turn up anything.

forest.peterson said:
do you have an application you suggest for "format your microSD with something other than the Windows method"; sourceforge did not turn up anything.
Click to expand...
Click to collapse
use SDFormatter

wow that SDformatter link has a lot of popups - this link feels less like I just found a date at the bus-stop sdcard.org/downloads/formatter_3 ; but it will not install on either Server2008R2 x64 or Server2003 R2 SP2 x32.
I reformatted the microSd with the format tool in Server2008R2 as FAT format. Installed the files, and boom - I see little green guys swirling around the screen. After awhile a dialog appeared "Sorry! The process com.android.phone has stopped unexpectedly. Please try again"; the dialog closed and it seems like it works! Thank you. I will try again with the HPtool and as FAT32.
Now I just need to learn how to use Android - and the screen calibration seems off? Deleting ts-calibration and rebooting to calibrate.

Glad to hear using the latest bundle works for you! Yeah, that might be a slight issue with an outdated kernel. The main thing I wanted to do is get you booted up first!
Before we continue, make sure you make a backup of your current configuration by copying the contents of the microSD and either moving it to your computer or some other storage device. This way you know you have a "working" bundle.
Next we update the kernel package from HERE; might I suggest using THIS kernel package. Be sure to delete the old files (should be located under root of the microSD and called modules-xxx and zImage) first! Extract till you see two files then rename zImage-xxx to just zImage and feel free to delete the files you extracted from. I've always created my own ts-calibration file but just wanted you to have it, "just in case".
Additionally, you may also need to update the rootfs by deleting the file called rootfs and downloading THIS file. Extract the file and rename to just rootfs and be sure to place it where the file called Haret is (default location is root of the microSD).

files are downloaded and installed - everything seems to work

[Q] Unbrick LG Optimus Net

Wondering if there is anyone here willing to help me with this issue. I tried flashing the phone with the LG Tool and the .cab firmware file but it keeps giving me a fatal error. I also could not use the tool for converting it to .kdz. Please can someone give me instructions for unbricking this phone and or point me to a firmware that I can try flashing with Odin or a .kdz package? Can it be done from the memory card? I had CWM recovery installed but all I can get it to do his hang on the LG logo or go into emergency mode. Any help appreciated. Thanks.

Use this to download your original kdz.

post-mortem said:
Use this to download your original kdz.
Click to expand...
Click to collapse
Only downloads a 7.88MB file when the firmware is 95.6MB.
After following these instructions:
Step 1: Get drivers here and install them
LGUnitedMobileDriver_S4981MAN37AP22_ML_WHQL_Ver_3. 7.2.exe
Step 2: Reboot
Step 3: Make sure phone has at least 50% battery
Step 4: Get firmware here
Firmware LGL45CT2_01
Step 5: Download this and extract
KDZ_FW_UPD_EN.zip
Step 6: Put phone in emergency mode
To put the LGL45C into download/emergency mode:
1. With the phone powered off you hold Volume Down and Back at the same time.
2. While holding the keys insert a USB cable plugged into a PC or charger, in a couple of seconds the the screen should say emergency mode at the bottom.
Step 7: Follow these steps in order (This is from the extracted "KDZ_FW_UPD_EN.zip" ZIP)
Install msxml.msi
Disable antivirus software
Open UpTestEX_mod2_marwin.exe
Wait for the program to open
Look for "Encrypt cab file to kdz file"
Click the folder icon
Choose the location of the cab you downloaded for L45C firmware
Encrypt cab -> kdz Program will freeze up. DO NOT EXIT until program says Done!!! Otherwise it won't finish converting.
Close program
Open KDZ_FW_UPD.exe
"Type" choose CDMA
Choose in "Phonemode": Emergency
Click the folder icon and choose the kdz file that UpTestEX_mod2_marwin.exe just made.
Click Launch software update and enjoy!
I get:
"
[R&D Test Tools Log File]
13:06:25 : Launching SW update
13:06:25 : Unpacking KDZ
13:06:28 : KDZ file extraced
13:06:35 : Files were extracted.
13:06:35 : LGMobileDL Load.
13:06:35 : Port = -1
13:06:35 : Connecting to phone
13:06:44 : Check Phone mode = 2
13:06:51 : Phone type check.......
13:06:51 : LGMobileDL.DLL Loading....
13:06:51 : _SetAuthMark Ok : wAuthMark(13164)
13:06:51 : LoadLibrary Error(126)
13:06:53 : ===FINISHED===
"

I believe the KDZ flasher will work with the phone in emergency mode. It's a bit more dangerous than LGMDP, because you can brick the phone if you pull the battery, or if your computer happens to freeze during the flash.

post-mortem said:
I believe the KDZ flasher will work with the phone in emergency mode. It's a bit more dangerous than LGMDP, because you can brick the phone if you pull the battery, or if your computer happens to freeze during the flash.
Click to expand...
Click to collapse
Yes, but I can't seem to find a solution to the error.

13:06:51 : LGMobileDL.DLL Loading....
13:06:51 : _SetAuthMark Ok : wAuthMark(13164)
13:06:51 : LoadLibrary Error(126)
Click to expand...
Click to collapse
It's unable to load the .dll file. If that file is included in the files you downloaded, try downloading it again. If it's downloaded on the fly by the program you were running, try running it again, to force it to redownload the dll. Also, make sure there isn't another version re: 32 vs. 64 bit. Lastly, try doing the update on another computer.

post-mortem said:
It's unable to load the .dll file. If that file is included in the files you downloaded, try downloading it again. If it's downloaded on the fly by the program you were running, try running it again, to force it to redownload the dll. Also, make sure there isn't another version re: 32 vs. 64 bit. Lastly, try doing the update on another computer.
Click to expand...
Click to collapse
Still getting the same story on another PC.

Try this. Before you do the flash (the step which throws the error), look for LGMobileDL.dll on your computer, and replace it with this one or this one (they're different).

I'm sorry for bumping a nearly-year-old thread but I'm currently experiencing the same problems.
I successfully rooted my L45C but idiotically didn't do a backup and ran into some problems while playing around with it down the line. I am now stuck in a bootloop with CWM recovery.
I've tried the method that callihn tried (which I found on androidforums) and got the same results. I tried to force a system update with the LG Mobile Support Tool both to no avail. Replacing the LGMobileDL.dll (as suggested above) didn't help (the first link was dead for me as well).
I would love if it someone could help give me some insight on how to fix my problem.

DUDE, STOP!!
daihatsuboy said:
I'm sorry for bumping a nearly-year-old thread but I'm currently experiencing the same problems.
I successfully rooted my L45C but idiotically didn't do a backup and ran into some problems while playing around with it down the line. I am now stuck in a bootloop with CWM recovery.
I've tried the method that callihn tried (which I found on androidforums) and got the same results. I tried to force a system update with the LG Mobile Support Tool both to no avail. Replacing the LGMobileDL.dll (as suggested above) didn't help (the first link was dead for me as well).
I would love if it someone could help give me some insight on how to fix my problem.
Click to expand...
Click to collapse
K. Listen up. YOU ARE NOT BRICKED. DO NOT flash any of these solutions. If you can get into CWM recovery, you are GOLDEN. I wish
I could, as I am truly bricked. To truly brick it, just go to System>privacy>factory reset and then you can be where we are. What you want
is a copy of an LGl45c NANDROID backup. That's it, that's all. I have copies on my Linux partition (I'm in Windows now). You can email
me.
Do not lose ability to get to CWM. If you do, and all you can get to is the EMERGENCY download mode, you will find that the l45c is not
nearly as supported as you thought (just look at how many custom ROMs you could find). Flashing these firmware downloads may very well
brick your phone for real, especially since we are having difficulty finding the correct files that are not corrupt or really for a 'phone that may or
not be close....'.
I'd give you my phone number, but.... oh yeah, I'm bricked!!! lol!!! :cyclops:
Edit: Google for 'stock l45c images' (.img) files. They are hard to find. In fact, I did the same as you and couldn't find an original. I used
an older one. Know the definition of the word 'flash', and what you are flashing. You want to flash an .img, not a firmware update. (Firmware is the lowest. Think programming: machine>assembly>language). You are 'in assembly'. Yay!! Stay away from 'machine' !!)

Nandroid
COULD YOU PLEASE SEND ME THE BACKUPS!? Or any files you have for this phone!? Please and thank you!

what os did you use to flash the firmware my phone is bricked as well and none of these methods work, i always get load library error 126.

post-mortem said:
Try this. Before you do the flash (the step which throws the error), look for LGMobileDL.dll on your computer, and replace it with this one or this one (they're different).
Click to expand...
Click to collapse
Some of these links don't work any more. I've attached a ZIP archive of various versions of the LGMobileDL.dll file. I downloaded these versions from zhaodll.co (very skeptically at first), but ran them through my virus checked, then stripped the junk and identifier files that site added to the package.
Unfortunately, I haven't had success at using any of these modules with the KDZ program. I still either hit the LoadLibrary error ("LoadLibrary Error(126)"), or the KDZ program hangs.

post-mortem said:
It's unable to load the .dll file. If that file is included in the files you downloaded, try downloading it again. If it's downloaded on the fly by the program you were running, try running it again, to force it to redownload the dll. Also, make sure there isn't another version re: 32 vs. 64 bit. Lastly, try doing the update on another computer.
Click to expand...
Click to collapse
We are discussing a few different DLL files. I discovered that LGMobileDL.dll does not cause the problem. The absence of a different DLL file causes the problem (and the LGMobileDL reports the error).
Unfortunately, the download for this specific device (the CAB file) does not contain a DLL which the flasher application expects to use. LG's own "Mobile Support Tool" downloads a file from LG's servers and expects the package to contain this DLL file to process the flashing, but for the LGL45C, the package does not contain this DLL (again, from LG's own servers!).

HOW TO CHANGE imei FOR max OR spice mtkPHONES

Dear Reader,
I am getting questions about how to change IMEI and IMEI is invalid how to correct it.
Open ES explorer / Root explorer or any other tool and make your phone system to accept read and write. Norrnaly I use Android Root Tool kid. Open the tool kid and go to Remount option and in that make the System ----> read / write and (rootfs) read/ write. Also try to save your root.
I thought of using the reply channel to give the simple tutorial here.
1. Remove your battery and look at the scribes there. You will notice IMEI numbers there.
2. Just write down these numbers in a sheet. or store it in your system desktop.
3. You should have rooted phone.
4. Goto play store and install Mobileuncle MTK tool.
5. Open the mobile uncle tool and scroll to Engineering mode and click it.
6. Go to MTK section and click it.
7. You find Engineering mode pop up at the top and below it you notice the row with different section.
8. In that section you just slide and tap the connectivity section.
9. In the connectivity at the column below you touch CDS information
10.In the pop uo you tocuh the Radio information and you will get pbone 1 and below that phone 2.
11. Now you touch phone 1 and in the popup you touch the AT+
12. Once you touch the Key board will pop up. In the key board you type any single letter and cancel only the letter you have type.
13. Immediately you can notice the scribes that is required for you It looks like AT+EGMR=1,7""
14. you touch the first row and after 7 you can notice the simple "" and in that two inverted commas you delete one at the end.
15 after deleting that, just type the 15 degite number you have written down in the point no 2 here.
16. Verify your typed numbers and close the inverted commas "
17. Then touch the row which says SEND AT COMMAND
18. Once the pop up display indicates AT command successfully send.
It is all over for one of your sim, you have got the valid imei number.
Now repeat the same for phone 2.
This exercise is not required if you have saved your IMEI number using the same Mobile uncle tool. This tool has IMEI backup restore facility.
Just use that facility and back up your imei number not only in your mobile keep a copy some where in your laptop/ desktop.
If you have already saved and backed up there is no need for the above exercise.
thanks.
SOMETIMES AFTER CUSTOM ROM FLASH, THE IMEI MIGHT VANISH and also for frequent editors like me in general The AT COMMAND fail may occur. In such a cases I followed the procedure below.
If you have your CWM Back up at any time in your sd card in your laptop or desk top.
Then open it up and search for the data.ext4.tar file
open it up and look for the nvram in small letters.
Copy this and take/paste it into your sdcard.
Now use ES File Explore and make the root read and write acceptable in your phone.
Then go to the device in the ES File Explore and you can notice several section in the page and open the storage section. you find sdcard0 and sdcard1
Look for the nvram file that you have copied from cwm backp/data.ext4.tar and pasted in the sdcard.
After copying that file got the Device section in the ES File explores by pressing back button.
Now open the data folder and search for the nvram there.
Now touch your paste button in your ES File explore. A notice will pop up asking your permission to overwrite the file. You click/touch YES..
Now come out of the ES File explore and open your mobile uncle mtk tool and reboot your phone.
If the IMEI has not still recovered then, Follow the procedure listed in beginning. Now the SEND AT COMMAND FAIL MAY NOT OCCUR.
THANKS.

just worked
puduraja said:
Dear Reader,
I am getting questions about how to change IMEI and IMEI is invalid how to correct it.
Open ES explorer / Root explorer or any other tool and make your phone system to accept read and write. Norrnaly I use Android Root Tool kid. Open the tool kid and go to Remount option and in that make the System ----> read / write and (rootfs) read/ write. Also try to save your root.
I thought of using the reply channel to give the simple tutorial here.
1. Remove your battery and look at the scribes there. You will notice IMEI numbers there.
2. Just write down these numbers in a sheet. or store it in your system desktop.
3. You should have rooted phone.
4. Goto play store and install Mobileuncle MTK tool.
5. Open the mobile uncle tool and scroll to Engineering mode and click it.
6. Go to MTK section and click it.
7. You find Engineering mode pop up at the top and below it you notice the row with different section.
8. In that section you just slide and tap the connectivity section.
9. In the connectivity at the column below you touch CDS information
10.In the pop uo you tocuh the Radio information and you will get pbone 1 and below that phone 2.
11. Now you touch phone 1 and in the popup you touch the AT+
12. Once you touch the Key board will pop up. In the key board you type any single letter and cancel only the letter you have type.
13. Immediately you can notice the scribes that is required for you It looks like AT+EGMR=1,7""
14. you touch the first row and after 7 you can notice the simple "" and in that two inverted commas you delete one at the end.
15 after deleting that, just type the 15 degite number you have written down in the point no 2 here.
16. Verify your typed numbers and close the inverted commas "
17. Then touch the row which says SEND AT COMMAND
18. Once the pop up display indicates AT command successfully send.
It is all over for one of your sim, you have got the valid imei number.
Now repeat the same for phone 2.
This exercise is not required if you have saved your IMEI number using the same Mobile uncle tool. This tool has IMEI backup restore facility.
Just use that facility and back up your imei number not only in your mobile keep a copy some where in your laptop/ desktop.
If you have already saved and backed up there is no need for the above exercise.
thanks.
SOMETIMES AFTER CUSTOM ROM FLASH, THE IMEI MIGHT VANISH and also for frequent editors like me in general The AT COMMAND fail may occur. In such a cases I followed the procedure below.
If you have your CWM Back up at any time in your sd card in your laptop or desk top.
Then open it up and search for the data.ext4.tar file
open it up and look for the nvram in small letters.
Copy this and take/paste it into your sdcard.
Now use ES File Explore and make the root read and write acceptable in your phone.
Then go to the device in the ES File Explore and you can notice several section in the page and open the storage section. you find sdcard0 and sdcard1
Look for the nvram file that you have copied from cwm backp/data.ext4.tar and pasted in the sdcard.
After copying that file got the Device section in the ES File explores by pressing back button.
Now open the data folder and search for the nvram there.
Now touch your paste button in your ES File explore. A notice will pop up asking your permission to overwrite the file. You click/touch YES..
Now come out of the ES File explore and open your mobile uncle mtk tool and reboot your phone.
If the IMEI has not still recovered then, Follow the procedure listed in beginning. Now the SEND AT COMMAND FAIL MAY NOT OCCUR.
THANKS.
Click to expand...
Click to collapse
just worked charm for first imei but for second imei we need to select TA+EGMR=1,10"......":good::good::good::fingers-crossed::highfive::good:

[Q] Lost IMEI (NO SIM) - MTK MT6589M (Intex Aqua i-5)

Hello! I need some genius to find solution for my problem , my phone (Intex Aqua i-5) doesn't recognize any SIM Card and my IMEI is empty. The problem occurred when I flashed wrong recovery, somehow I got it working again by removing battery for 15 minutes, and holding power key for a minute before that, then flashed proper CWM recovery again via MobileUncle Tool., but now phone doesn't charge when its turned off, and doesn't recognize SIM. Everything else works fine.
This is IMPORTANT: Cant recover IMEI via PC (my usb port is broken (charging part is working but cant connect to PC, pins for data transfer are damaged). So IT'S NOT AN OPTION. But can transfer files from PC to Phone - Wifi transfer.
Need to recover IMEI trough phone! (there is numerous methods I've tried, gonna list them below)
- Engineer mode, - CDS info, Radio info, AT COMMAND - AT+EGMR=1,7,"1234567890XXX15" (tried variations with empty space before AT or before + , not working, gives me an error "AT command failed at sent ".
- Tried to generate original IMEI on the computer, write it to MP0B_001 file, transfer to phone, set permissions for it, transfer it to data/nvram/md/NVRAM/NVD_IMEI and replace file at destination with custom one (tried variations: all this but at the and making IMEI backup with MobileUncle Tools and restoring it, also tried different MP0B_001 generators, different permissions, tried deleting original file in NVD_IMEI folder first, then copying new one, etc). --- NO SUCCESS.
- Tried MTK65xx apk software for changing IMEI , NO SUCCESS. - got error msg: "pttycmd1 device NOT found!"
- Installing terminal emulator , writing for SIM 1 line of code: echo ‘AT+EGMR=1,7, “IMEI_NUMBER” ‘ >/dev/pttycmd1 and for SIM 2 this line: echo ‘AT+EGMR=1,10, “IMEI_NUMBER” ‘ >/dev/pttycmd1 - nothing happens , even after reboot..
I'm not allowed to post links for methods above, cause this is my first thread .
My phone is rooted, there is custom ROM on it. (MIUI V5 FOR INTEX AQUA I-5 ). And CWM recovery for this ROM.
Have backup of my STOCK ROM, but couldn't restore it via CWM, It is corrupted or something, but have original folders in it , NVRAM folder for example. (tried coping and flashing MP0B_001 from that folder to phone, but nothing).
Any other ideas guys?

Unless you find what file you need to overwrite. There is not much help any one can offer as editing the IMEI is illegal in many places so that the only approved way is restoring a backup with is hard to do in your case without a pc connection as those files will need to be flashed.

zelendel said:
Unless you find what file you need to overwrite. There is not much help any one can offer as editing the IMEI is illegal in many places so that the only approved way is restoring a backup with is hard to do in your case without a pc connection as those files will need to be flashed.
Click to expand...
Click to collapse
Thank you for your quick reply. I'm just looking the way to restore or flash my origina IMEI , which is written under my battery, or from my probably damaged backup. Pretty sure restoring original IMEI is not illegal and I'm aware that those files need to be flashed, but maybe someone knows how to flash it without usb connection, with CWM, MobileUncle etc..

ImYourMan said:
Thank you for your quick reply. I'm just looking the way to restore or flash my origina IMEI , which is written under my battery, or from my probably damaged backup. Pretty sure restoring original IMEI is not illegal and I'm aware that those files need to be flashed, but maybe someone knows how to flash it without usb connection, with CWM, MobileUncle etc..
Click to expand...
Click to collapse
It depends on the country and the laws. If you already know it needs to be flashed then all you have to do is get the files from the backup (hope it's not coruppted) and then make a zip to flash in recovery. There is not alot of development done with that chip set here so I am out of ideas.

Figured out why my nandorid backup cant be restored, and gives an error "error while flashing boot image". When I made a backup there was no boot.img file in it. (as you cant see below in log file) So I added a file from only stock rom found on the net (that stock Is not made for cwm and cant be flashed via cwm, just via SP Flash Too so I cannot use it). but my logic was that I can borrow missing boot.img and put it in my backup folder). So obviously its not solution.
Log file: (nandroid backup)
Backing up /boot...\c
02:18:25 Backing up /recovery...\c
02:18:25 Backing up /modem...\c
02:18:26 Backing up /system...\c
02:19:59 Backing up /data...\c
02:21:28 Backing up /cache...\c
02:21:30 Backing up /.android_secure...\c
02:21:34 Replacing old backup with new backup...\c
02:21:36 Generating md5sum...\c
02:22:04 Verifying md5sum...\c
02:22:05 Online Nandroid Backup Completed in 3 minutes 43 seconds!
###########################
But after this there is no boot.img at all in backed up files as you can see.
Files Backed-up:
"----rwxr-x 1 11264 Dec 8 02:21 cache.ext4.tar
----rwxr-x 1 530526720 Dec 8 02:21 data.ext4.tar
----rwxr-x 1 1024 Dec 8 02:18 modem.img
----rwxr-x 1 191 Dec 8 02:22 nandroid.md5
----rwxr-x 1 553781248 Dec 8 02:19 system.ext4.tar"
Why I dont have file boot.img in my backup and how can i fix it? :/
Someone said that I make another backup via cwm and keep just boot.img in it, then copy my old files in that new created folder , but i doubt it will work cause Im on custom ROM now (MIUI) and i want to restore stock (Andorid 4.2.1).
I started another thread here http://forum.xda-developers.com/general/help/stock-rom-intex-aqua-5-t3007603 in hope someone will upload stock ROM for my phone that is flashable with cwm.

BLU bricked, SPFlash Read yields encrypted contacts2.db, what next

I have a BLU phone that was my only source of contacts with no Google or backup (yes, I know). It was dropped a significant distance. It won't show any indication of charging or powering up, no lights or sounds. However when I plugged in the USB port I noticed the toggling of the USB driver install, typical for a MTK device so I decided to try to read from it with SPFlash tool.
To try to get at the contacts I downloaded a factory restore ROM and loaded the scatter file to see what location I needed to seek to find the user data for download. I first found userdata.img location from the factory scatter file and set up SPF under the ReadBack tab and used the Add button to specify a range beginning with and including the same numbers where the scatter file indicated the user data was, plus with SPF tool I stated I wanted the user data area read and saved as userdata.img. Now clicking on the read and then plugging the phone in with the read button pre-pushed, the SPF tool took off reading as soon as the dead phone USB was plugged in, operating just like I was flashing or writing to the phone. (Excitement was mounting.)
From here on my Windows machine I installed DiskInternals Linux Reader and mounted the userdata.img with that software and was able to navigate to the db file containing the contacts and the android call list located at
/data/data/com.android.providers.contacts/databases/contacts2.db.
Now the DiskInternals software allowed me to save the contacts2.db as a Windows file anywhere on the laptop but when I tried to open it with SQLite, it said the file is encrypted. I viewed the file using a Linux friendly editor (Context) and saw some names and numbers in readable text, but they were surrounded by tons of formatting and unprintable characters. (Looked something like a MS Word docx file.) I also tried the FireFox plugin for SQLite in addition to the SQLiteManager and the SQLite browser software. All of them said the file had a password that was needed to open it. (Exit excitement.)
Now it looks like my options are to either try to find someone or thing that can hack the password of the contacts2.db, locate the password perhaps hidden somewhere in a system.img that I can attempt to extract via the same method as I did the userdata, or I can try to assemble a working group of restore "parts" which include this userdata.img, adding it to some mix of the restore file and other IMG files I can possibly extract from the "bricked all but for flash tool" mostly dead phone. Theoretically, with such a reassembled package of IMG files I would then go look for an exact same model of this bricked phone and then try to load the new assembly of IMG files onto that good used phone.
I am open for suggestions of how to solve the puzzle. The objective is to get a list of readable contacts from the crashed phone and ideally get them exported into a format that can be input into another phone.
Thanks in advance.
P.S. Android 5.0 on the phone