Hi,
Device : MANN Zug3 (Qualcomm msm8610)
My phone was bricked after flash system.img. Now the only way I can access my phone is fastboot. I tried serveral way to create & modify system.img then flash to system partition using command
"fastboot flash system system.img"
It got chunk file error because max download size is about 512MB but my system.img (I got system.img by porting from the phone using "dd if= of= command") is more than that so I tried
"fastboot flash -S 768M system system.img"
then i got "Failed : data too large"
I also have stock rom but it was separted to 13 files with name
systm_1.img
systm_2.img
systm_3.img
...
systm_13.img
But I dont know how to flash them.Is there solution to flash these files into system partition?
Can anyone help me to unbrick my phone please .....
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]
Hi!
I recently bought a NUU X5 mobile from banggood. Sadly it went out of stock and they only sent me the Indian version instead of the Global one I originally ordered...
Anyway it worked ok but I wanted to root it by installing TWRP and then Magisk, which I have done a couple of times with other phones.
What I did was:
Code:
>fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 26.177s]
finished. total time: 26.179s
>fastboot flash recovery TWRP.img
target reported max download size of 134217728 bytes
sending 'recovery' (5944 KB)...
OKAY [ 0.274s]
writing 'recovery'...
OKAY [ 0.149s]
finished. total time: 0.425s
Sadly, I didn't backup the stock recovery before with the SP Flash Tool. I didn't think it was a big deal and I never had problems with it, though the TWRP is not an official release. But I thought in the worst case the recovery does not work but what really happened after that:
The mobile went into a boot loop. And I cannot get into the recovery or even fastboot any more!
I didn't know the recovery is even used during a normal boot!
I think what I would need is a stock X5-IN-01 firmware.
The guys at needrom.com only have
X5-AM-02 - full_hct6750_66_n-user 7.0 NRD90M
X5-EU-01 - full_hct6750_66_n-user 7.0 NRD90M
and they also want money for me to download it!
However I found in the internet
Nuu_X5_MT6750_20170308_7.0.zip
which turns out to be the X5-EU-01 firmware. I would pretty much even prefer this firmware over the indian version to get all LTE bands, but for now I would be happy if I even got the damn thing to boot again
So I started experimenting with the SP Flash Tool which can still access the phone.
The scatter file that is delivered with the firmware does not match the actual setup of the phone.
The EU firmware has an extra partition "persdata" which the IN firmware does not have.
I created a modified scatter file which matches my partitions. (I got the partition info from the GLB_xxx.log trace file from the SP Flash Tool). Then I backuped everything (too late for the recovery...).
Then I flashed only the recovery from the EU firmware. To my surprise, the firmware now displays the boot screen again (was totally black and no backlight before)! But it does not boot, after quite some time it resets so it's a much slower bootloop now.
I then tried to flash different partitions with the EU firmware stuff, I ended up flashing everything except the preloader and the md1dsp (which I read should maybe not be touched?). I'm not touching the preloader because I think if it is gone, I cannot get in with SP Flash Tool any more, is that right?
Anyway, when I flashed everything except preloader and md1dsp, the display was black (no boot screen), but backlight was on. The phone was actually booting! ADB was possible but no working screen.
Then I tried flashing back one by one the backuped IN partitions. It ended when flashing the "lk" partition. With the original IN "lk" partition in place, I have a boot screen but no boot. With the EU "lk" partition, I have a non-working screen and boot. What does the "lk" partition even contain?
Now I need your help guys!
What to do? I cannot find the IN stock fw anywhere. Is it possible to download it from the NUU OTA update server? Or does anyone have such a phone and can provide the stock recovery? Or should I erase everything reformat and put in the complete EU firmware including new preloader and persdata? To my knowledge the hardware is the same, at least it has exactly the same specs.
Any help is very much appreciated.
Manu
NUU X5
manutest said:
Hi!
I recently bought a NUU X5 mobile from banggood. Sadly it went out of stock and they only sent me the Indian version instead of the Global one I originally ordered...
Anyway it worked ok but I wanted to root it by installing TWRP and then Magisk, which I have done a couple of times with other phones.
What I did was:
Code:
>fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 26.177s]
finished. total time: 26.179s
>fastboot flash recovery TWRP.img
target reported max download size of 134217728 bytes
sending 'recovery' (5944 KB)...
OKAY [ 0.274s]
writing 'recovery'...
OKAY [ 0.149s]
finished. total time: 0.425s
Sadly, I didn't backup the stock recovery before with the SP Flash Tool. I didn't think it was a big deal and I never had problems with it, though the TWRP is not an official release. But I thought in the worst case the recovery does not work but what really happened after that:
The mobile went into a boot loop. And I cannot get into the recovery or even fastboot any more!
I didn't know the recovery is even used during a normal boot!
I think what I would need is a stock X5-IN-01 firmware.
The guys at needrom.com only have
X5-AM-02 - full_hct6750_66_n-user 7.0 NRD90M
X5-EU-01 - full_hct6750_66_n-user 7.0 NRD90M
and they also want money for me to download it!
However I found in the internet
Nuu_X5_MT6750_20170308_7.0.zip
which turns out to be the X5-EU-01 firmware. I would pretty much even prefer this firmware over the indian version to get all LTE bands, but for now I would be happy if I even got the damn thing to boot again
So I started experimenting with the SP Flash Tool which can still access the phone.
The scatter file that is delivered with the firmware does not match the actual setup of the phone.
The EU firmware has an extra partition "persdata" which the IN firmware does not have.
I created a modified scatter file which matches my partitions. (I got the partition info from the GLB_xxx.log trace file from the SP Flash Tool). Then I backuped everything (too late for the recovery...).
Then I flashed only the recovery from the EU firmware. To my surprise, the firmware now displays the boot screen again (was totally black and no backlight before)! But it does not boot, after quite some time it resets so it's a much slower bootloop now.
I then tried to flash different partitions with the EU firmware stuff, I ended up flashing everything except the preloader and the md1dsp (which I read should maybe not be touched?). I'm not touching the preloader because I think if it is gone, I cannot get in with SP Flash Tool any more, is that right?
Anyway, when I flashed everything except preloader and md1dsp, the display was black (no boot screen), but backlight was on. The phone was actually booting! ADB was possible but no working screen.
Then I tried flashing back one by one the backuped IN partitions. It ended when flashing the "lk" partition. With the original IN "lk" partition in place, I have a boot screen but no boot. With the EU "lk" partition, I have a non-working screen and boot. What does the "lk" partition even contain?
Now I need your help guys!
What to do? I cannot find the IN stock fw anywhere. Is it possible to download it from the NUU OTA update server? Or does anyone have such a phone and can provide the stock recovery? Or should I erase everything reformat and put in the complete EU firmware including new preloader and persdata? To my knowledge the hardware is the same, at least it has exactly the same specs.
Any help is very much appreciated.
Manu
Click to expand...
Click to collapse
I too have this phone and tried to root to no avail. Now my phone is in bootloop and i cant find correct firmware to flash to phone to fix it! Please someone help! All the firmware thats available for this phone on internet will not work for some reason. Very desperate...
manutest said:
Hi!
I recently bought a NUU X5 mobile from banggood. Sadly it went out of stock and they only sent me the Indian version instead of the Global one I originally ordered...
Anyway it worked ok but I wanted to root it by installing TWRP and then Magisk, which I have done a couple of times with other phones.
What I did was:
Code:
>fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 26.177s]
finished. total time: 26.179s
>fastboot flash recovery TWRP.img
target reported max download size of 134217728 bytes
sending 'recovery' (5944 KB)...
OKAY [ 0.274s]
writing 'recovery'...
OKAY [ 0.149s]
finished. total time: 0.425s
Sadly, I didn't backup the stock recovery before with the SP Flash Tool. I didn't think it was a big deal and I never had problems with it, though the TWRP is not an official release. But I thought in the worst case the recovery does not work but what really happened after that:
The mobile went into a boot loop. And I cannot get into the recovery or even fastboot any more!
I didn't know the recovery is even used during a normal boot!
I think what I would need is a stock X5-IN-01 firmware.
The guys at needrom.com only have
X5-AM-02 - full_hct6750_66_n-user 7.0 NRD90M
X5-EU-01 - full_hct6750_66_n-user 7.0 NRD90M
and they also want money for me to download it!
However I found in the internet
Nuu_X5_MT6750_20170308_7.0.zip
which turns out to be the X5-EU-01 firmware. I would pretty much even prefer this firmware over the indian version to get all LTE bands, but for now I would be happy if I even got the damn thing to boot again
So I started experimenting with the SP Flash Tool which can still access the phone.
The scatter file that is delivered with the firmware does not match the actual setup of the phone.
The EU firmware has an extra partition "persdata" which the IN firmware does not have.
I created a modified scatter file which matches my partitions. (I got the partition info from the GLB_xxx.log trace file from the SP Flash Tool). Then I backuped everything (too late for the recovery...).
Then I flashed only the recovery from the EU firmware. To my surprise, the firmware now displays the boot screen again (was totally black and no backlight before)! But it does not boot, after quite some time it resets so it's a much slower bootloop now.
I then tried to flash different partitions with the EU firmware stuff, I ended up flashing everything except the preloader and the md1dsp (which I read should maybe not be touched?). I'm not touching the preloader because I think if it is gone, I cannot get in with SP Flash Tool any more, is that right?
Anyway, when I flashed everything except preloader and md1dsp, the display was black (no boot screen), but backlight was on. The phone was actually booting! ADB was possible but no working screen.
Then I tried flashing back one by one the backuped IN partitions. It ended when flashing the "lk" partition. With the original IN "lk" partition in place, I have a boot screen but no boot. With the EU "lk" partition, I have a non-working screen and boot. What does the "lk" partition even contain?
Now I need your help guys!
What to do? I cannot find the IN stock fw anywhere. Is it possible to download it from the NUU OTA update server? Or does anyone have such a phone and can provide the stock recovery? Or should I erase everything reformat and put in the complete EU firmware including new preloader and persdata? To my knowledge the hardware is the same, at least it has exactly the same specs.
Any help is very much appreciated.
Manu
Click to expand...
Click to collapse
Manu, can you please upload and share your modified scatter file and stock firmware files...Please and thank you!
Still need the India firmware ver? i hv the latest update: X5-IN-23_20190114-1843.
Buy x5 Indian version
Hi. I need the Indian version firmware. Hope u can help me.
Maybe you can upload it to mega or Dropbox and I can download it from there.
Thanks
Avi
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