I converted my Verizon VS996 to a US998 with the Frankenstein method: US998 10b KDZ -> US998 20b -> Unlock + TWRP -> US998 20e. I get LTE on T-Mobile and AT&T on bands 2 and 4, but I never get band 12/17. I notice poorer reception overall too. The frankeinstein process is supposed to enable all the LTE bands the US998 has but it isn't accessing them. I tried unlocking LTE bands using the hidden menu while rooted, and selecting 12, 13, 17, 29, 30 leaves me with no LTE coverage. I also set the RAT selection to LTE only and I only get signal when selecting band 2 or 4. Also I see no band 12/17 cells on Rx Monitor.
My issue is now fixed I'll explain in detail later. For now.
What I've learned:
-The old stock modemst1 and modemst2 partitions remain after the cross-flash Frankenstein method*
*Unless the partition maps were conflicting/changed, all according to PrimaryGPT and the other GPT partitions. (modemst partitions would be rebuilt in a new place)
-These old modemst1 and modemst2 partitions are locked with the stock LTE bands, potentially causing issues, as in my case.
-Eg. the VS996 has no support for band 12, so it might not work after cross-flashing to US998
-The modemst1 and modemst2 partitions aren't always rebuilt well after erasing it with dd (I took a backup of modemst1 and modesmst2 after wiping with dd, opened them with hex viewers on windows, and realized they were not blank partitions with zeros. I guess these partitions are meant to be minimally read/writed on. modem partition was all zeros)
-All the V30 phones have identical modem chips, the bands are software locked
-My method could allow LTE band 71 unlocking... for use on T-Mobile. Except the H932 modem didn't work when I tried it before, but didn't bootloop/brick on my VS996 -> US998.
-abl and ablbak are the key partitions for bootloader unlock & check, booting, and fastboot access
-Leaving these two partitions alone from US998 when flashing to H933, AS998, or H931 leaves you with fastboot access
Process:
1. Flash the VS996 to US998 with unlocked LGUP in Partiton DL mode
2. Install TWRP via fastboot
3. Boot TWRP via fastboot
4. Factory reset, wipe data, cache, dalvik/art-cache, and internal storage. Repeat twice
5. Format/wipe data, type yes
6. Reboot to recovery
7. Flash Magisk 17.3, Disable_Dm-Verity_ForceEncrypt, and lg-rctd-disabler. (THIS ORDER. If this is not done, TWRP will be reverted to stock, eg. would only factory reset when triggered)
8. Boot system
9. Boot into recovery, factory reset, wipe data, cache, dalvik/art-cache, system. Repeat twice.
10. Format/wipe data, type yes
11. Wipe modem, modemst1, and modemst2 with dd:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 bs=16384
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2 bs=16384
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modem bs=16384
(Repeat above commands 3 times)
12. Reboot into recovery, flash my H931_20d.zip made from an H93120d dump.
13. Flash Magisk 17.3, Disable_Dm-Verity_ForceEncrypt, and lg-rctd-disabler. (THIS ORDER. If this is not done, TWRP will be reverted to stock, eg. would only factory reset when triggered)
*Most importantly, the H931 ZIP contains 36 stock H931 20d partitions. The modem, modemst1, and modemst2 partitons are critical in configuring/running the modem to its instructions stored within modemst1 and modemst2! These will ensure the converted phone has all the available LTE bands of the H931, including band 12, which is what I was not getting before.
*Guide isn't final, there are no links yet. I will update it later.*
patato21 said:
My issue is now fixed I'll explain in detail later. For now.
What I've learned:
-The old stock modemst1 and modemst2 partitions remain after the cross-flash Frankenstein method*
*Unless the partition maps were conflicting/changed, all according to PrimaryGPT and the other GPT partitions. (modemst partitions would be rebuilt in a new place)
-These old modemst1 and modemst2 partitions are locked with the stock LTE bands, potentially causing issues, as in my case.
Click to expand...
Click to collapse
Glad your issue is fixed but I disagree with some of your premise. If you flash from VS996 to US998 via DL Partition mode, the old modem partitions can't remain. You are overwriting all the partitions (including modem) with US998 KDZ via Frankenstein.
Tell me how you cross flashed?
In the Frankenstein thread you flash any North American variant (except H932) to Nougat US998 first via DL Partition (choosing all partitions), then do Master Reset and then upgrade to US998 Oreo. Some, like Canada H933, have to DL Partition at both stages. So, they have overwritten their partitions TWICE.
If you correctly DL Partition any North America V30/V30+ to US998 you WILL have these bands:
http://www.lg.com/us/cell-phones/lg-US998-Silver-lg-v30
US998
CDMA: 800 MHz CDMA
2G GSM: 850/900/1800/1900 MHz
3G UMTS (HSPA):850/900/1900/2100 MHz
4G LTE Bands: 1/2/3/4/5/7/12(17)/13/20/25/66
________
patato21 said:
-abl and ablbak are the key partitions for bootloader unlock & check, booting, and fastboot access
-Leaving these two partitions alone from US998 when flashing to H933, AS998, or H931 leaves you with fastboot access
Click to expand...
Click to collapse
Very interesting.
______________
[/COLOR]
patato21 said:
11. Wipe modem, modemst1, and modemst2 with dd
Click to expand...
Click to collapse
What is dd?
ChazzMatt said:
What is dd?
Click to expand...
Click to collapse
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 bs=16384
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2 bs=16384
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modem bs=16384
It wipes the modemst1/2 partitions. They're not reliably wiped this way.
dd = diskdump. name explains it
seadersn said:
dd = diskdump. name explains it
Click to expand...
Click to collapse
i call it diskdestroyer
patato21 said:
It wipes the modemst1/2 partitions. They're not reliably wiped this way.
Click to expand...
Click to collapse
try wiping these partitions with fastboot erase. see if these commands are available. they should be, never used erase on v30 til now. but worth a try.
Chazzmatt, I will pay you to do this to my phone!!!
Chazzmatt, I will pay you to do this to my phone!!! Please help me out!!!
Related
I've done lots of research on flashing firmware and still have some questions + notes to share.
First off the popular topics on this are often full of incomplete / bad info and broken links.
So RSDLite is the preferred method ? ..instead of manually doing it line by line in a fastboot/mfastboot console or with a .bat file (on Windows)
So.. some misc stuff now that i hope is useful
I noticed the config file for flashing this, XT1527_SURNIA_RETCA_5.0.2_LXI22.50-24.1_cid14_subsidy-TELUS_CFC.xml
loads, "slcf_rev_b_telus_v1.1.nvm" which holds carrier specific data.
Which would be ignored *I think doing it manually.
Also every guide on the web says this line,
mfastboot oem config carrier vzw
vzw is the carrier code for Verizon.. so why do people always flash Verizon info on all stock firmware packages ?
My carrier has code tkpca for Telus.
The info shared across the web (comes from this forum) is sloppy and inaccurate.
For example guides say back up the PDS partition before flashing but you can't.
And i think it's sym linked to a folder called persist (that resides on root)
(you can back it up by using RootExplorer to zip the folder up then copy it out)
There is lots of issues / problems to watch out for..
For example i encountered an error trying to flash Firmware packages with RSDLite.
It would always say "flashing failed on gpt.bin" (the first file to flash)
(supposedly the fix for that is to delete the getvar line)
Also most guides tell you to flash with fastboot or mfastboot (almost the same)
problem is some oem's have an extra sparsechunk file and others don't.
this could lead to some huge problems i bet.. like maybe a bricked phone.
The main problem i encountered was losing my signal after i flashed what some guy here advised.
I got the firmware package installed manually (after RSDLite failed)
But no matter what i couldn't get my phone setup with Telus.
Every time the phone started it launched some activating phone dialog for 30 minutes then fail.
I seen one guy here say he managed to upgrade like what i wanted to do from 5.0.2 to 5.1.1
But he was sort of vague.. saying he did not update the Radio.
So i had tried to use the radio from the stock Telus firmware posted online inserted into the USC or US v5.1 firmware folder but it made no difference re-flashing.
I think what "Radio" means is these two files in the firmware package..
fsg.mbn + NON-HLOS.bin
So i think that other guy i seen here on Telus removed those lines to flash those two radio files then he manually flashed the rest of them i am guessing..
So this is suppose to be my stock package..
XT1527_SURNIA_RETCA_5.0.2_LXI22.50-24.1_cid14_subsidy-TELUS_CFC.xml
It says in, "factory_version_info_cfc.txt"
Build Fingerprint: motorola/surnia_retca/surnia_umts:5.0.2/LXI22.50-24.1/2:user/release-keys
What does the "surnia_umts" part mean guys ?
Because i was told to flash,
SURNIA_USC_5.1_LPI23.29-15_cid9_subsidy-DEFAULT_CFC.xml
(So i could upgrade to v5.1 stock)
And after poking around in the files i think the USC part means USA & Canada ?
But my radio wouldn't work on that for LTE/cdma/auto prl
And this one says
motorola/surnia_usc/surnia_cdma:5.1/LPI23.29-15/18:user/release-keys
notice how it says "surnia_cdma" ?
Then,
SURNIA_RETUS_5.1_LPI23.29-15_cid9_subsidy-DEFAULT_CFC.xml
motorola/surnia_retus/surnia_umts:5.1/LPI23.29-15/19:user/release-keys
Then,
XT1528_SURNIA_VERIZON_5.1_LPI23.29-17_cid2_subsidy-DEFAULT_CFC.xml
motorola/surnia_verizon/surnia_cdma:5.1/LPI23.29-17/18:user/release-keys
So... does the build fingerprint info i posted above indicate different types of Radio connections maybe ?
surnia_cdma -vs- surnia_umts
Because i am suspicious this may be why i failed to fully update to v5.1 (my radio didn't work)
Here is a link to get Firmwares for 5.0.2 and 5.1.1 (for Otus + Surnia)
https://mega.nz/#F!rMIhDLgR!oq5Cz_XbgZLEEysmqoYtcA
Here is the commands to flash with mfastboot..
Code:
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot oem config carrier vzw
mfastboot oem fb_mode_clear
Note1:
I think you can add the line (below) to above (code/quote) to restart the phone when flashing finishes,
mfastboot reboot
What i like to do is add the following to the last line..
@pause
Then if you put the quoted lines into a windows .bat file it will pause for you
when it's finished so you can read what happens or save it to file etc
Note2: Some stock firmware use another line so you would need to add below to above code lines.
mfastboot flash system system.img_sparsechunk.6
Open the firmware file you download to see if there is 5 or 6 "sparsechunk" files.
and about this line below..
mfastboot oem config carrier vzw
"vzw" i think means for Verizon so look for your own code.. i think ? (mine is tkpca)
If you want to flash only the radio related files ? it's this below.. i am pretty sure.
Code:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
There is a lot more i learned while trying to flash my phone with stock Firmware.
I would like us to have a list of MD5 hash's to verify the downloaded .zip's we are sharing too.
Incomplete downloads happen.. always check and always back up as much as you can before flashing !
I used TWRP to make a backup ..it was quick and easy and i needed it and it worked
Here is some hash's i made.. post more if you got 'em guys
- 5.1
SURNIA_RETEU_EU_5.1_xt1524_LPI23.29-15.zip = MD5: b7bae69012df7c47ee370635a49de2d1
SURNIA_RETUS_5.1_LPI23.29-15_cid9_subsidy-DEFAULT_CFC.xml = MD5: 623419f42075a9b8b74c2d833bc4fa2d
SURNIA_USC_5.1_LPI23.29-15_cid9_subsidy-DEFAULT_CFC.xml = MD5: 6053bd6007214b4eb59c5e96c5dd4d7a
XT1528_SURNIA_VERIZON_5.1_LPI23.29-17_cid2_subsidy-DEFAULT_CFC.xml = MD5: 57196e77d89e04a3c6d6358a42563edc
- 5.0.2
XT1527_SURNIA_RETCA_5.0.2_LXI22.50-24.1_cid14_subsidy-TELUS_CFC.xml = MD5: 04f658169a5bc35c295973054ba85b67
There is also a bunch of codes you can enter in the dialer to open hidden menus
(i tested most of them)
*#*#759#*#* = RLZ
*#*#4636#*#* = INFO
*#06# = IMEI
Moto G Hard Reset
How to hard reset Wipe/Reset Data/Profile & internal storage, please use this code: *#*#786#*#*
Open Superuser App
*#*#1234#*#* or *#*#7873778#*#*
Manual Check Update
*#*#2432546#*#*
Motorola Service Menu (CQA Test)
*#*#2486#*#*
Click to expand...
Click to collapse
Lastly people need to be careful with downgrading versions or having locked bootloaders.
I'll try to answer more of your questions when I get off work tonight or tomorrow but in regards to UMTS that is required to get a GSM signal.
[email protected]
Hey y'all! Sorry to bug ya, but my XT1528 Vz Moto E is wifi-less I was tinkering around, trying to get s-off through a combination of sunshine+kingroot, and when I mucked that up, I just restored to the stock rom posted on Mega. Unfortunately, alot of errors popped up in fastboot and now wifi is unusable :crying: DOES ANYBODY KNOW HOW TO FIX THIS?
You restored the same version firmware you had when you bought it ?
Or a newer version or alternate carrier version ?
Also did you have 5.0 originally then put on 5.1 ?
I screwed up my wifi before doing that eh..
Make sure you have Otus or Surnia properly picked out (for which you have / need)
brookemels said:
Hey y'all! Sorry to bug ya, but my XT1528 Vz Moto E is wifi-less I was tinkering around, trying to get s-off through a combination of sunshine+kingroot, and when I mucked that up, I just restored to the stock rom posted on Mega. Unfortunately, alot of errors popped up in fastboot and now wifi is unusable :crying: DOES ANYBODY KNOW HOW TO FIX THIS?
Click to expand...
Click to collapse
S-Off? This is a Motorola S-off is for HTC. Also, I don't think you can fastboot flash a Verizon Moto E, as it's locked.
cmason37 said:
S-Off? This is a Motorola S-off is for HTC. Also, I don't think you can fastboot flash a Verizon Moto E, as it's locked.
Click to expand...
Click to collapse
You can't even unlock the bootloader on the VZ variant or mount system as r/w, so not sure what their S-off attempt did.
Ace42 said:
You can't even unlock the bootloader on the VZ variant or mount system as r/w, so not sure what their S-off attempt did.
Click to expand...
Click to collapse
Whatever he did, he most likely permanently screwed his phone up.
xpmule said:
You restored the same version firmware you had when you bought it ?
Or a newer version or alternate carrier version ?
Also did you have 5.0 originally then put on 5.1 ?
I screwed up my wifi before doing that eh..
Make sure you have Otus or Surnia properly picked out (for which you have / need)
Click to expand...
Click to collapse
So I solved the problem. Apparently, the theres TWO flavors of Verizon's 5.1, and I was flashing the older one. Also, I adapted my mfastboot commands to be similar to the ones in the script included in the firmware. So now wifis back in action! Thanks for your time!
cmason37 said:
S-Off? This is a Motorola S-off is for HTC. Also, I don't think you can fastboot flash a Verizon Moto E, as it's locked.
Click to expand...
Click to collapse
If I'm not mistaken, the Vz Moto E would be able to have S-off except there's no way to achieve even temp root on 5.1
cmason37 said:
Whatever he did, he most likely permanently screwed his phone up.
Click to expand...
Click to collapse
Sorry, but my phones up an running again also, I'm a girl xD
brookemels said:
So I solved the problem. Apparently, the theres TWO flavors of Verizon's 5.1, and I was flashing the older one. Also, I adapted my mfastboot commands to be similar to the ones in the script included in the firmware. So now wifis back in action! Thanks for your time!
Click to expand...
Click to collapse
Hi,
I am in a similar solution, can you send me the link for the verizon xt1528. THank you very much
brookemels said:
So I solved the problem. Apparently, the theres TWO flavors of Verizon's 5.1, and I was flashing the older one. Also, I adapted my mfastboot commands to be similar to the ones in the script included in the firmware. So now wifis back in action! Thanks for your time!
Click to expand...
Click to collapse
I also disabled my Wi-Fi accidentally. I had to get a new Moto E to replace it -- what did you do to restore it? Could you kindly detail the steps for noobs?
andxdrewx said:
I also disabled my Wi-Fi accidentally. I had to get a new Moto E to replace it -- what did you do to restore it? Could you kindly detail the steps for noobs?
Click to expand...
Click to collapse
Hey y'all! Sorry for silent! In between college and looking for exploits in the XT1528 bootloader, I have had NO time whatsoever :crying: Its rather aggravating, these variants of popular phones with locked down bootloaders! but after seeing Moto unlock the Vz X 2014 bl, I remain hopeful!
In order to do a proper restore, you need to get the XT1528_SURNIA_VERIZON_5.1_LPI23.29-17.5_cid2_subsidy-DEFAULT_CFC.xml.zip file from FileFactory/MEGA (link down bellow)
Flash in this order;
mfastboot getvar max-sparse-size
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase carrier
mfastboot erase cache
mfastboot erase userdata
mfastboot oem fb_mode_clear
Unfortunately, this will mean loosing your data, but better than a shiny brick!
MEGA: https://mega.nz/#F!p9sxCaqR!Ja2kfKiL_0Hi3_SsKizjKw!FlMx1A5R
FileFactory: http://www.filefactory.com/file/233...PI23.29-17.5_cid2_subsidy-DEFAULT_CFC.xml.zip
HAPPY FLASHING!
Connected to freedompop with the sprint version, flashed cm13, runs fine, but the phone number is wrong and I cannot make any calls to it.
My thought is to update prl and profile, which i cannot do in cm13. So I thought if i go back to 5.1.1 that would do it.
I cannot seem to find a stock specifically for my phone. If I can use a diff model rom for it, fine, but no clue which one that is.
Help!
I realize this isn't the answer you are looking for, but AFAIK, FreedomPop phones only use data to make calls (via the messaging app). The number you are assigned in About Phone>Status is only used to get you on the network to receive data. I know you can pay for "Premium Voice" that is supposed to make calls over cellular (and not data) but from what I have read, this is for outgoing calls only. Also, while the phone number in About Phone might be used to make the premium voide call, FreedomPop will put in forwards so that it looks like the call is coming from your regular FreedomPop number. Calls can't be received to this About Phone number. Here is a forum posting that mentions it: https://forums.freedompop.com/discussion/13935/cant-receive-calls
TL;DR - As long as your data connection works, the phone number in Settings>About Phone>Status is meaningless.
PS - I could be completely wrong about this!!
monkey3ddd said:
Connected to freedompop with the sprint version, flashed cm13, runs fine, but the phone number is wrong and I cannot make any calls to it.
My thought is to update prl and profile, which i cannot do in cm13. So I thought if i go back to 5.1.1 that would do it.
I cannot seem to find a stock specifically for my phone. If I can use a diff model rom for it, fine, but no clue which one that is.
Help!
Click to expand...
Click to collapse
Idk what the latest version of the Moto E XT1526 (sprint) firmware is, but I flashed Build LP123.29-18.S.11 for Boost and it works fine on my Sprint XT1526 running on Ring Plus. I got it here:
http://firmware.center/firmware/Motorola/Moto E (2nd gen-2015)/Stock/XT1526/
XT1526_SURNIA_BOOST_5.1_LPI23.29-18-S.11_cid9_subsidy-DEFAULT_CFC.xml.zip
I flashed it manually by using these instructions:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot oem config carrier spr
fastboot oem fb_mode_clear
That bootloader is version 80.0F. I do not know if that is the most recent bootloader version or not. If you have a later version of the bootloader - YOU SHOULD NOT FLASH A LOWER VERSION OF THE PARTITION TABLE (gpt.bin) OR THE BOOTLOADER (bootloader.img).
BEWARE - you should NOT try to downgrade the partition table or the bootloader. You should also never try to flash a partition table that is the incorrect version for the bootloader you are running!!! Doing so will either fail or result in a hard brick!!!!
Also, there is a file called MVNO Slayer that I installed to get free tethering on Ring+. Not sure if it would help your issue or not:
http://forum.xda-developers.com/mot...t/flashable-lte-fix-moto-e-6-x-boost-t3290719
I would try installing the MVNO Slayer first and see if that corrects your issue.
As was already mentioned, a device active on FreedomPop doesn't have an actual phone number. You need to either have the FreedomPop app installed, or use an alternative such as Hangouts Dialer. If you have root, you can extract the user name and password from the FreedomPop data (search for FreedomPop Google Voice integration for instructions) and enter them in the hidden SIP settings, which you can access using an app like Activity Launcher or AnyCut.. You would then be able to make and receive SIP calls using your FreedomPop number without having the FreedomPop app installed, but you wouldn't be able to send or receive SMS.
Thanks all, it was the freedompop app issue, never realized that, now I feel stupid.
Hello all. I am familiar with LG Aristo 2s and the like, but not so much with LG V30s.
My buddy has an LG V30 H932 T-mobile version and he has forgotten his PIN.
I would like to recover his userdata, then reset the phone and possibly even root it.
I used a modified LGUP utility to make complete partition images on my PC, including all these:
Spoiler: Partition images I have
BackupGPT.img
PrimaryGPT.img
abl.img
ablbak.img
apdp.img
boot
boot.img
cache.img
carrier.img
cdt.img
cmnlib.img
cmnlibbak.img
ddr.img
devcfg.img
devcfgbak.img
devinfo.img
dip.img
dpo.img
drm.img
eksst.img
encrypt.img
eri.img
factory.img
fota.img
fsc.img
fsg.img
ftm.img
grow.img
grow2.img
grow3.img
grow4.img
grow5.img
grow6.img
hyp.img
hypbak.img
keymaster.img
keymasterbak.img
keystore.img
laf.img
lafbak.img
limits.img
logfs.img
misc.img
modem.img
modemst.img
modemst2.img
mpt.img
msadp.img
operatorlogging.img
persist.img
pmic.img
pmicbak.img
pstore.img
qni.img
rawresources.img
rawresourcesbak.img
rct.img
recovery.img
recoverybak.img
rpm.img
rpmbak.img
sec.img
sns.img
srtc.img
ssd.img
storsec.img
storsecbak.img
system.img
toolsfv.img
tz.img
tzbak.img
userdata.img
xbl.img
Anyone familiar with how I could go about mounting and decrypting his userdata partition ?
I am very tech-capable--I have even created ROMs for the LG Aristo 2 and 2 +.
Thanks very much if anyone can help. My buddy has a bunch of un backed up pictures on the phone.
If it is truly encrypted with a PIN, then I am pretty sure there is almost zero way of recovering the data I am sorry. I certainly would not want it to be recovered trivially - that's the point.
Out of the box all Android devices are designed to backup data to the cloud - which is where data should be safely stored. If you turn that function off your need to find another method of recovering in the event of loss of access to the phones and it's local data . Data on the phone is effectively just a local cache to lower the latency of access, and mean you can keep using the phone when it is offline.
tecknight said:
Hello all. I am familiar with LG Aristo 2s and the like, but not so much with LG V30s.
My buddy has an LG V30 H932 T-mobile version and he has forgotten his PIN.
I would like to recover his userdata, then reset the phone and possibly even root it.
I used a modified LGUP utility to make complete partition images on my PC, including all these:
Spoiler: Partition images I have
BackupGPT.img
PrimaryGPT.img
abl.img
ablbak.img
apdp.img
boot
boot.img
cache.img
carrier.img
cdt.img
cmnlib.img
cmnlibbak.img
ddr.img
devcfg.img
devcfgbak.img
devinfo.img
dip.img
dpo.img
drm.img
eksst.img
encrypt.img
eri.img
factory.img
fota.img
fsc.img
fsg.img
ftm.img
grow.img
grow2.img
grow3.img
grow4.img
grow5.img
grow6.img
hyp.img
hypbak.img
keymaster.img
keymasterbak.img
keystore.img
laf.img
lafbak.img
limits.img
logfs.img
misc.img
modem.img
modemst.img
modemst2.img
mpt.img
msadp.img
operatorlogging.img
persist.img
pmic.img
pmicbak.img
pstore.img
qni.img
rawresources.img
rawresourcesbak.img
rct.img
recovery.img
recoverybak.img
rpm.img
rpmbak.img
sec.img
sns.img
srtc.img
ssd.img
storsec.img
storsecbak.img
system.img
toolsfv.img
tz.img
tzbak.img
userdata.img
xbl.img
Anyone familiar with how I could go about mounting and decrypting his userdata partition ?
I am very tech-capable--I have even created ROMs for the LG Aristo 2 and 2 +.
Thanks very much if anyone can help. My buddy has a bunch of un backed up pictures on the phone.
Click to expand...
Click to collapse
ul encry
Fisherman1 said:
If it is truly encrypted with a PIN, then I am pretty sure there is almost zero way of recovering the data I am sorry. I certainly would not want it to be recovered trivially - that's the point.
Out of the box all Android devices are designed to backup data to the cloud - which is where data should be safely stored. If you turn that function off your need to find another method of recovering in the event of loss of access to the phones and it's local data . Data on the phone is effectively just a local cache to lower the latency of access, and mean you can keep using the phone when it is offline.
ul encry
Click to expand...
Click to collapse
@Fisherman1,
Yes of course I understand the concept of data backup and cache, I just remembered being able to mount an encrypted userdata on an Aristo 2 using ubuntu in the past. However, I'm unsure whether it had a PIN or not.
It seems like I used encryptable=/path/to/backed/up/encrypt/folder or something like that, but I am probably not remembering it correctly. Also, I didn't get the data until backing it up was no longer an option.
Thank you very much for the help, my friend
Hey if anyone have these files please I need them.
What really actual happend to my phone is
I tried to cross flash to EA firmware because Verizon didn't pull the A12 before cross flashing I backed up FTM modem_a modem_b modemst1 modemst2 OP_a OP_b Sid_a and Sid_b. In the process og cross flash I lost my IMEI. Then I installed the verizon A11 kdz and try to restore my partition but IMEI didn't come back. Whenever I restore my backup partitions and boot to download mode directly from Edl LG UP recognize my phone as V600VM30A and it shows IMEI but when I flash the kdz or boot to system IMEI is zero. I just want to install v600vm30a firmware maybe it solve my problem. Thanks.
irfan64672 said:
Hey if anyone have these files please I need them.
What really actual happend to my phone is
I tried to cross flash to EA firmware because Verizon didn't pull the A12 before cross flashing I backed up FTM modem_a modem_b modemst1 modemst2 OP_a OP_b Sid_a and Sid_b. In the process og cross flash I lost my IMEI. Then I installed the verizon A11 kdz and try to restore my partition but IMEI didn't come back. Whenever I restore my backup partitions and boot to download mode directly from Edl LG UP recognize my phone as V600VM30A and it shows IMEI but when I flash the kdz or boot to system IMEI is zero. I just want to install v600vm30a firmware maybe it solve my problem. Thanks.
Click to expand...
Click to collapse
you have done big mistake when you didn't backup your Lun partition exactly the lun 5 partition which unclude your imei