Hey all
I have bricked my t-mobile V20 trying to network unlock it.
Anyway, I have been investigating solutions to this problem, and well, let's say there is no easy solution for most people.
The problem as I see it, is that this chipset (msm8996), while not exactly super new, is for all intents and purposes VERY new indeed. Because of the widespread use of UFS NAND introduced with this cpu. Almost all phones based on these newer qualcomm chips use this modern storage, which works as a multi-LUN device. Meaning it will show as several independent logical storage devices depending on configuration. V20 has 7, or at least the H918 does.
In short, it means the storage device is no longer mounted in mmcblk0, but on /dev/sda sdb sdc... etc depending on how many LUN's.
So the community has not catched up yet to this new development. (Well I guess hard-brick has always been a pain for many phones, but this makes it worse)
Now there are, I think, 5 ways to approach the 9008 mode in this instance.
*JTAG: Bypass all this QC hodge-podge and program the darn NAND directly.
*USB with Box: Some type of box with the capability to program your specific phone. Proprietary, closed source, have to pay.
*USB with firehose: Program yourself with programs like QFIL. Need device specific "prog_ufs_firehose_8996*.elf" file. LG has not released this. Can probably only be leaked, which happens on occasion.
*Enter DL or 9006 mode: It may be possible to short certain test points on the motherboard, which will put the phone into 9006 or Download Mode. Would require instructions, or the Service Manual.
*SD-Card Rescue: Make an sdcard with the required partitions. Some say this can't be done on newer QC chips with UFS because of the aforementioned multi-LUN situation.
I have been looking into this SDCARD method, and I found some info on the DragonBoard 820C (which uses msm8996, with UFS). This board has 6 LUN's, so it's multi-lun just like V20.
If you see here: DragonBoard, there is listed a method of SD CARD rescue. The tools can be found here: db-boot-tools
Unfortunately I don't have a full dump of my partitions, so I only have the ones included in the TOT, or KDZ files. I tried making a image using those files, it didn't work, but something interesting happened. With this sd card inserted the phone does not show the qdloader 9008 port on my pc, actually nothing shows. I did double check using a normal card inserted, and yes with normal storage card qdloader 9008 mode appears.
So this is interesting and makes me think I should try some more with this, but I need someone with a T-Mobile H918 to dump their partitions. EFS is not needed (where the imei is).
Update: I currently don't need a dump (Except for engineering firmware).
Update2: I could not make the SD-Card boot work, see here (with normal firmware).
List partitions
Command: ls -l /dev/block/platform/soc/624000.ufshc/by-name/
Or this: ls -al /dev/block/bootdevice/by-name/
Then dd the relevant partitions not listed above: dd if=/dev/sd*1/2/3/4... etc of=/sdcard/"filename".img
As an example, maybe you can do it other ways, perhaps with an app.
You can also use the patched LGUP to dump partitions. Should be the simpler method.
In any case I will be grateful for your assistance, as I'm sure many others will if this pans out.
Engineering Rom: I got an idea, if I can't get this to work then maybe it's because the support isn't compiled in the bootloader. If I could get the eng-firmware (for H918) to test that it would be great. So please if you have an eng device or a dump of that, I would be thrilled try it out.
Update: Below I've attached a zip with a limited partition layout, and the commands to dump from adb. Use the patched LGUP for Engineering firmware. (actually, with engineering formware I need all, or most of the partitions. PM me if you have such a device)
Support your work. Lg
China user
I would certainly go the QPST/QFIL/Firehose method & my strategy would be to restore Download mode.
I'm sure once that has happened you can restore full firmware with the patched LGUP method here
Prowler_gr said:
I would certainly go the QPST/QFIL/Firehose method & my strategy would be to restore Download mode.
I'm sure once that has happened you can restore full firmware with the patched LGUP method here
Click to expand...
Click to collapse
Yes, but how would you go about doing that without the required firehose file? LG apparently uses certificate or some signing, so you can't use just any file.
Although that patched LGup is nice. If I had known about that tool before I messed up, I probably would not have messed up. Because then I wouldn't be afraid of loosing root, and just flashed H910pr with LGup, then flash back with the patched one later.
Edit: As I have later found out ^^this would not be a good idea. The result would be the same - BRICK Hard. Just as a precaution for anyone contemplating doing so. The H918 can not be flashed with any other V20 firmware, neither can you flash H918 firmware on any other V20.
askermk2000 said:
Yes, but how would you go about doing that without the required firehose file? LG apparently uses certificate or some signing, so you can't use just any file.
Although that patched LGup is nice. If I had known about that tool before I messed up, I probably would not have messed up. Because then I wouldn't be afraid of loosing root, and just flashed H910pr with LGup, then flash back with the patched one later.
Click to expand...
Click to collapse
I don't pretend to know the answer, but I believe that the firehose file is not any type of signed LG file, but just a partition layout (mbn or elf) file that can be generated from a .kdz file...
Make sure you use QPST_2.7.460 or later which supports MSM8996...
Google is your friend but you can start reading from here & here
Prowler_gr said:
I don't pretend to know the answer, but I believe that the firehose file is not any type of signed LG file, but just a partition layout (mbn or elf) file that can be generated from a .kdz file...
Make sure you use QPST_2.7.460 or later which supports MSM8996...
Google is your friend but you can start reading from here & here
Click to expand...
Click to collapse
Well, there is a difference between an MPRG and MSIMAGE/Singleimage. I believe you are thinking about the latter here. Those can be generated, but are of little use without a programmer file (mprg/firehose).
askermk2000 said:
Well, there is a difference between an MPRG and MSIMAGE/Singleimage. I believe you are thinking about the latter here. Those can be generated, but are of little use without a programmer file (mprg/firehose).
Click to expand...
Click to collapse
Remember we only aim to get bootloader mode, not the full layout...
Btw I probably wouldn't mind wasting $5 on this
Prowler_gr said:
Remember we only aim to get bootloader mode, not the full layout...
Click to expand...
Click to collapse
Yes I know. But Qualcomm and LG has made that very difficult for us. All the common info on the web so far is outdated, or doesn't work because of missing firehose file.
Except for possibly SDcard method.
Having read your OP again, of how you SD card affects how windows detects your phone, I believe this may be a good step to our solution. of getting the phone recognised in download mode
Prowler_gr said:
Having read your OP again, of how you SD card affects how windows detects your phone, I believe this may be a good step to our solution. of getting the phone recognised in download mode
Click to expand...
Click to collapse
Do you have brick as well?
I looked at that page, and pretty sure I've looked at it before. There is nothing there that can be of use.
askermk2000 said:
Do you have brick as well?
I looked at that page, and pretty sure I've looked at it before. There is nothing there that can be of use.
Also I'm very suspicious of that Aryk site. They don't seem to know what their talking about many times, their downloads dubious with viruses and the like. On the page you linked they claim QHSUSB_BULK is the same as 9008, while it is actually 9006.
It almost seems like that site was set up solely for the purpose of spreading malware or something. Just cobble up something random and presenting it like information, like with algorithms and bots or whatever.
I think there a lot of that stuff going on in the "gms" business. Like for example, on gsmarena I found a sticky thread which supposedly had files to repair a LG V20 which has been stuck in bootloop because of "use of cheap chinese usb-c cable". Anyway, that archive had some files, including a *prog_ufs_firehose_8996_lite.elf*. That file did not work, and there was an instructions file there also, in XLS format which contained virus.
Come to think about it. This whole crap with qualcomm "security" stuff seems like just a way to create the sub-market of gsm repair boxes. Well, who knows, just a guess on my part. But there's something fishy about the whole thing.
Click to expand...
Click to collapse
I was, I'm now unbricked (I worked out the method with the LGUP patch).
What I'm suggesting (as the website describes) is to write the v20 boot image to an SD card using Win32DiskImager/, & see if your device will boot with it, & then upgrade with LGUP.
I've got the H990DS variant (I can send you my boot image to try)
Prowler_gr said:
I was, I'm now unbricked (I worked out the method with the LGUP patch).
What I'm suggesting (as the website describes) is to write the v20 boot image to an SD card using Win32DiskImager/, & see if your device will boot with it, & then upgrade with LGUP.
I've got the H990DS variant (I can send you my boot image to try)
Click to expand...
Click to collapse
I would welcome a boot image, or images of partitions. That's why I started this thread mostly.
askermk2000 said:
I would welcome a boot image, or images of partitions. That's why I started this thread mostly.
Click to expand...
Click to collapse
link removed
Prowler_gr said:
...removed
Click to expand...
Click to collapse
Ok, I got it. Thx
Will try with this. Did you get it with LGUP ?
I extracted it from my phone
Prowler_gr said:
I extracted it from my phone
Click to expand...
Click to collapse
Im in this to but i have a lg g5 msm8996 board
me and him have been trying to work very closely to get a fix for msm8996 in gen of coarse he is worried about v20 me g5 but common interests.
i dont wanna knock any v20 discussions off track so im here but im sitting in the corner most quietly
he is def on the right track i have dealt with many hardbricks in the past
and the no reconition on pc is most def a good step
my problem is being a new moderator plus my job plus after hours work i dont have time to test a lot of stuff any more he has bought a lot of info to my eyes and am trying to work on what i can.
look and 8994 g4 it took 2 years for a hardbrick fix to come about only from people doing the same as we are
TheMadScientist420 said:
Im in this to but i have a lg g5 msm8996 board
me and him have been trying to work very closely to get a fix for msm8996 in gen of coarse he is worried about v20 me g5 but common interests.
i dont wanna knock any v20 discussions off track so im here but im sitting in the corner most quietly
he is def on the right track i have dealt with many hardbricks in the past
and the no reconition on pc is most def a good step
my problem is being a new moderator plus my job plus after hours work i dont have time to test a lot of stuff any more he has bought a lot of info to my eyes and am trying to work on what i can.
look and 8994 g4 it took 2 years for a hardbrick fix to come about only from people doing the same as we are
Click to expand...
Click to collapse
We agree he's on the right path (about SD method), that's why I sent him my boot image & suggested he burns it into an sd card. I'm hoping he only needs to boot with it & everything else would be straight forward
I burned the *.img file directly onto a 64gb uSDXC card. It creates a single 63gb fat mbr partition on the card. So it seems you managed to make a single complete image of your entire UFS chip. Have no idea how though, but I've not exactly had the chance to look into that myself because of brick.
The image, burned this way did not work, it's not even recognized by the phone as a boot image. I will see if I can perhaps extract the file from within the img-file and split that somehow.
Because windows can't edit/remove partitions on external devices, I used linux, since ubuntu's standard tools there can simply burn the image directly onto the device, automatically removing any partition scheme in the process.
That win32diskimager program is strange because it can not target device directly, but only mountpoint, and because my card was already formatted with numerous partitions from before, I could not use that program.
Prowler_gr said:
We agree he's on the right path (about SD method), that's why I sent him my boot image & suggested he burns it into an sd card. I'm hoping he only needs to boot with it & everything else would be straight forward
Click to expand...
Click to collapse
That has always been the rite track just to get to download mode.
I thank you for providing the files. Its always stressful when dealing with owns hardbrick. ive spent hours of burning images to mine lol even fried a couple sd cards
but most def seems as if you are knowledgeable also in this area so id love to keep you in this loop
If we all can pull this off. We will be the next heros of the day lol also if u are interested in reading some suposedly the s8+ also has same boards so even may be able to piece stuff from there
and i know sammys have been booted of sd in the past.
the more people we can get the better
Related
ROM for recovery G2X under the NVFLASH
This method necessary!
If the device is not loaded and not firmware in other ways! (If you downloaded the wrong firmware in the device)
I took the unpacked program files KDZ and added to them NVFlash and created BAT file!
Download ROM: http://www.mediafire.com/?wfokxjxi7rfoaey
Mirror: http://www.megaupload.com/?d=C5LBU3DS
Download APX driver: http://www.mediafire.com/?k559zgjlqkd5ted
Installation Instructions:
Download both files
Unpack it to the C drive to their respective folder
Remove the battery
Hold Vol Up/Down (and keep them held)
Insert the USB cable
Install APX driver from the your APX folder
For windows 7(and vista? please confirm):
Open Device Manager in Windows and you should see "APX Device" listed with an error
Right click on the APX device
Select 'Update driver software'
Select 'Let me pick...'
Select 'Have disk'
Browse to directory you extracted the APX Driver
Select the *entire* 'APX Driver' folder
Accept any warnings, including the big red alert (you may need to disable UAC)
Now in Device Manager under 'USB Controllers' you should have an 'NVIDIA USB Boot-recovery driver for mobile devices'
If not, uninstall the driver, reboot, rinse and repeat
Unplug everything
Hold Vol Up/Down (and keep them held)
Insert USB cable
open your ROM folder:
Run Flash.bat file and wait for the process
After the logo appears on the LG phone
Unplug USB cable
Insert the battery
enjoy!
After that, I recommend to firmware device with help programms KDZ or LG Mobile Update
I'm confused as to what this is? I'm guessing stock rom flash through nv flash? Kind of like odin for samsung phones?
Sent from my LG-P999 using XDA App
Can't wait to check this out when I get home later. Regarding the kdz file, what exactly were you able to unpack from it? I've been able to extract 2 files (a very large .wbd file and a .dll file) but I couldn't figure out how to unpack them further, specifically the .wdb file.
ILUHA_89 said:
I took the unpacked program files KDZ and added to them NVFlash and created BAT file!
Click to expand...
Click to collapse
Can you post the DLL for the G2X so we can use the LG Utilities to unpack KDZ files for this device please. So far we have been unable to get the proper DLL that enables us to unpack these files. If you unpacked the KDZ you must have the DLL unless you used another method to extract the files from the KDZ. Please elaborate on how you accomplished this. Both phburks and I have been working on this and so far we have had no success.
Smallsmx3 said:
I'm confused as to what this is? I'm guessing stock rom flash through nv flash? Kind of like odin for samsung phones?
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
It is for people that have mucked up their phones to the point where LG Updater and KDZ Flash are not possible. This can be caused by many issues including, but not limited to, people flashing the O2X baseband to a G2X device. This method is purported to flash the entire Gingerbread ROM at the lowest possible hardware level. Hopefully this method is legit, but nobody has confirmed they have done it yet with the exception of the OP. Yes it is similar to ODIN for the Samsung but operating at an even lower level. With the NVFlash capability Tegra2 devices are virtually unbrickable.
jboxer said:
Can you post the DLL for the G2X so we can use the LG Utilities to unpack KDZ files for this device please. So far we have been unable to get the proper DLL that enables us to unpack these files. If you unpacked the KDZ you must have the DLL unless you used another method to extract the files from the KDZ. Please elaborate on how you accomplished this. Both phburks and I have been working on this and so far we have had no success.
It is for people that have mucked up their phones to the point where LG Updater and KDZ Flash are not possible. This can be caused by many issues including, but not limited to, people flashing the O2X baseband to a G2X device. This method is purported to flash the entire Gingerbread ROM at the lowest possible hardware level. Hopefully this method is legit, but nobody has confirmed they have done it yet with the exception of the OP. Yes it is similar to ODIN for the Samsung but operating at an even lower level. With the NVFlash capability Tegra2 devices are virtually unbrickable.
Click to expand...
Click to collapse
You described it right!
This method has helped resurrect my device!
ZeroT| Demented said:
So the point of this utility if it works is to make the g2x un f***able like even if u do u can fix?
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Yes. It is almost as good as JTAG flashing the device. For Galaxy S devices using ODIN you still have to have the 'software download' mode working in the ROM and it is possible to brick a Galaxy S beyond the point of even getting this mode to be accessible leaving you the only way to fix the device through disassembling it and flashing via the JTAG pads. Using the NVFlash method you are flashing directly to the hardware through they Hynix flashing chip. I had another phone with a similar capability (I-Mobile i858 - Yuhua Touchstone device) and no matter how badly I F'd it up (I was developing custom roms for it) I had the similar low level flashing tool that could reflash the phone to stock so I could start over with a clean slate. If this method is legit, this is a big boon to the dev community for this device.
jboxer said:
Can you post the DLL for the G2X so we can use the LG Utilities to unpack KDZ files for this device please. So far we have been unable to get the proper DLL that enables us to unpack these files. If you unpacked the KDZ you must have the DLL unless you used another method to extract the files from the KDZ. Please elaborate on how you accomplished this. Both phburks and I have been working on this and so far we have had no success.
It is for people that have mucked up their phones to the point where LG Updater and KDZ Flash are not possible. This can be caused by many issues including, but not limited to, people flashing the O2X baseband to a G2X device. This method is purported to flash the entire Gingerbread ROM at the lowest possible hardware level. Hopefully this method is legit, but nobody has confirmed they have done it yet with the exception of the OP. Yes it is similar to ODIN for the Samsung but operating at an even lower level. With the NVFlash capability Tegra2 devices are virtually unbrickable.
Click to expand...
Click to collapse
After trying to firmware device with program KDZ or LG Mobile Update in folder C: \ ... \ Aplication Data \ folder appears "LGMOBILEAX" which contains the firmware files!
That's All
ILUHA_89 said:
After trying to firmware device with program KDZ in folder C: \ ... \ Aplication Data \ folder appears "LGMOBILEAX" which contains the firmware files!
That's All
Click to expand...
Click to collapse
So you got them after the LG Updater extracted the KDZ into its component files. phburks and I didn't get that far as we didn't want to connect our already updated devices to the updater. To get to the point you did where you could grab the individual files you would have had to click the start update button. Good work.
I have 7-zip on my computer but I am unable to open up the file I just downloaded. Can you put it in another format and upload to megaupload or mediafire please? I don't want to go through that Russian site again as I got an invalid download. Also, please post the baseband file as a separate download.
jboxer said:
So you got them after the LG Updater extracted the KDZ into its component files. phburks and I didn't get that far as we didn't want to connect our already updated devices to the updater. To get to the point you did where you could grab the individual files you would have had to click the start update button. Good work.
I have 7-zip on my computer but I am unable to open up the file I just downloaded. Can you put it in another format and upload to megaupload or mediafire please? I don't want to go through that Russian site again as I got an invalid download. Also, please post the baseband file as a separate download.
Click to expand...
Click to collapse
I downloaded the 7-zip file to the sdcard on my phone but I won't be home to try opening it for several hours because I'm at seaworld. Lol
Hopefully you guys can get this sorted out. Sounds promising so far.
phburks said:
I downloaded the 7-zip file to the sdcard on my phone but I won't be home to try opening it for several hours because I'm at seaworld. Lol
Hopefully you guys can get this sorted out. Sounds promising so far.
Click to expand...
Click to collapse
I won't be able to look at it until tomorrow as it is 11:31 p.m. here and time to go to bed. :-O ZZZzzzzz
How about posting a mirror???? the site will not let me download.... unless i visit a sponsor and purchase something... lol
i'll try it out and report back
........... Works like a charm
here mirror link
http://www.megaupload.com/?d=C5LBU3DS
What we really need is for someone to tell us how to create the config files for NVFlash so we can flash the baseband only. The new baseband is there and named 'P999_MDM.bin' if I am remembering correctly. No reason to flash an entire ROM when all someone wants is the updated baseband. If we can get the older baseband file also this tool could be used to revert the baseband also, if someone wanted to do that.
web_ninja said:
How about posting a mirror???? the site will not let me download.... unless i visit a sponsor and purchase something... lol
Click to expand...
Click to collapse
You don't have to buy anything. You just click on one sponsor site and it opens a new window. Thirty seconds later it will enable a download link. You need to click download two or three times if I remember correctly. I am at work now. I can mirror it in about ten hours if nobody else has done it yet. I looked at the files briefly and it looks legit.
Is this supposed to have a command interface? Or are you still typing in commands yourself?
I edited a cap!
Changed link to Mediafire
omarsalmin said:
Is this supposed to have a command interface? Or are you still typing in commands yourself?
Click to expand...
Click to collapse
Good question - that is what I am looking for rather then having to mess with the nvflash commands directly.
Update - this setup is similar to Paul's stock ROM recovery setup on modeco.com. As with his, you only have to "Run Flash.bat file and wait for the process". When I could not get off of the LGupdater screen by any other means, I ran this file from his post and it ran flawlessly - but of course I ended up with a 990's device. I tried to get back with other tools and firmware, but was never able to do it.
If this works OK, you would be able to restore your data, apps, or a nandroid and you are back in business.
I spent a week trying to restore my original (and best device as it turns out), so I am not going to fool with this right now myself. I did compare the config files from bot Paul's and this firmware and they are different - which looks real promising, as they are different.
HELP! I tried to use this and the tool failed, now I am getting ZERO response from the device. I can't even boot to APX. I'm freaking out right now!
EDIT: I managed to get the process restarted and the phone is in the process of rebooting. Hoping for the best.
EDIT 2: Phone booted up and it was all restored but for some reason the baseband was not updated :\
Did you run by using the flash.bat file? Did you hold volume up and down for the entire flash process?
Sent from my LG-P999 using Tapatalk
AimanF said:
HELP! I tried to use this and the tool failed, now I am getting ZERO response from the device. I can't even boot to APX. I'm freaking out right now!
EDIT: I managed to get the process restarted and the phone is in the process of rebooting. Hoping for the best.
EDIT 2: Phone booted up and it was all restored but for some reason the baseband was not updated :\
Click to expand...
Click to collapse
Did you have old of new baseband on before flashing? What was the state of your G2X before running this?
UPDATE: It appears that this works - but would like to 100% confirm. After all the disasters that occurred from running the LGupdater tool, this would be an important fix and should be stickied at some point. Current members know of the updater problems, but new buyers and member may not - so many may still have this problem down the road.
Therefore, I believe this is an important enough item to bring to closure and make readily available.
U saved my phone's life
THANK YOU THANK YOU
followed instructions restored completley to stock just like how i got phone out of box 2 weeks ago.
I was running eaglesblood v8 and had altered the vold.fstab file to switch mounts
from sdcard to internal and after that point i rebooted and media scanner said damaged sd card well i figured it just to be like an extension of a permission of sorts. and thought if formated it would the paths would switch no problem.
im actually kind of having a hard time rembering exactly what steps i did take to **** it up royally. but went into clockwork 5 to flash another rom from internal storage or same i cant rember now and did factory reset then all hell broke loose .
couldnt mount nothing except for system i tried formating sd card even though i dont have one probally ended up formating internal lol. formated system,
re flashed all recoverie versions including stock. i was getting so mad i called google HA by the way they got some pretty good music when u have to hold.
only thing i didnt try was to load up a rom on sd card and mount that but i really doubt it would have worked and plus i couldnt even use phone to do it lol
i need to go buy drive saved me some serious cash I would say this should be enough confirmation!!
Hi all, I have completely screwed my surface rt last night.
I was trying to do a reset and it wasn't working then I tried a bunch of other things ive read on the forum and my surface wont even boot up. its just in a constant loop ive trying to do an automatic repair and diagnosing and keeps bringing me to the boot menu.
I made a recovery usb but it doesn't seem to be working so im assuming the OS was already corrupt hence the reason the reset option in "change pc settings" wasn't working.
I would really love if someone could upload a recovery image of their surface rt. I cannot find one any where and the ones I have found they have pulled the links down.
hope someone can help me out here.
cheers.
adam_4049 said:
Hi all, I have completely screwed my surface rt last night.
I was trying to do a reset and it wasn't working then I tried a bunch of other things ive read on the forum and my surface wont even boot up. its just in a constant loop ive trying to do an automatic repair and diagnosing and keeps bringing me to the boot menu.
I made a recovery usb but it doesn't seem to be working so im assuming the OS was already corrupt hence the reason the reset option in "change pc settings" wasn't working.
I would really love if someone could upload a recovery image of their surface rt. I cannot find one any where and the ones I have found they have pulled the links down.
hope someone can help me out here.
cheers.
Click to expand...
Click to collapse
Next time do a search. You would have found a thread on this. And, as was said in the aforementioned thread these recoveries are device specific, so even if I got mine to you, it wouldn't work for you. Take it to Microsoft and have them replace it.
C-Lang said:
Next time do a search. You would have found a thread on this. And, as was said in the aforementioned thread these recoveries are device specific, so even if I got mine to you, it wouldn't work for you. Take it to Microsoft and have them replace it.
Click to expand...
Click to collapse
i did do a search and nothing has been able to help me so far. i also did read that it is device specific but have also read it has worked for some people. unfortunatley in australia we do no have any microsoft stores so its not that easy to just take it somewhere.
I feel like there are files missing from c drive. Almost like it started to do a restore then stopped halfway. In which I have never been able to get it to that stage for that to be the case.
I did some reading and was able to find the recover partition and tried to run the install.wim file from which I understand to basically be the “OS”. When I try to run it it says “no such interface supported”
From what I understand there is just no way to do a fresh install on these things regardless of what the problem is which is disappointing on Microsoft’s behalf.
C-Lang said:
And, as was said in the aforementioned thread these recoveries are device specific, so even if I got mine to you, it wouldn't work for you.
Click to expand...
Click to collapse
No. Those recovery images are device-type specific. Not device-specific. You can safely take one WIM file from the recovery partition of your device and use it to recover a different device of the identical model.
adam_4049
I see that you were able to start a restore process and it fails in the middle.
You may try the following: boot into the command line mode and format the boot partition (probably drive C: ). This would fix the disk errors if they are present, but you'll lose everything. Use diskpart tool to find the disk letter. Be careful with diskpart - do not delete partitions or issue "clean" command.
Then assign the letter to recovery partition with diskpart (say, R: ), then expand WIM file from the recovery partition with the command like this:
Code:
Dism /apply-image /imagefile:R:\RecoveryImage\install.wim /index:1 /ApplyDir:c:\
R:\RecoveryImage\install.wim - a path to install.wim on the recovery partition.
More info: http://technet.microsoft.com/en-us/library/hh824910.aspx - you need only "Dism /apply-image" part, bcdboot is unnecessary. Lets hope that "apply-image" option is present on RT.
This would forcibly expand the WIM file to your disk C:. Or at least you'll be able to see why it fails.
This may help. Or may completely brick the device and you'll need to go to service. So use it on your own risk. And you should be familiar with the command line - so don't ask how to use diskpart.
I had a problem with the recovery process when I've played with BCD and added a boot from VHD option. Had to delete that extra boot setting - and then recovery went fine. But I assume that you have not played with BCD.
Yeah, looks like people dont use search, what you want is a nice useful soul that creates a USB recovery from his EN-UK Surface_RT and puts it up on Copy, or Dropbox or something like that...
Hi
I am new to hacking android. I have built linux distros in the past, and have worked with Linux for 15 years,
I have just rooted a ZTE V965. It doesn't come pre-installed with Play store, and has all sorts of ZTE-specific Chinese apps. It has a good baseband circuit, a good screen, reasonable camera and I think is a great value phone, apart from the awful UI.
It is an android phone, although heavily customised. It has an MTK6589 processor coupled with 4Gb ROM and 512Mb RAM.
I have other phones which operate a much more "Vanilla" android. For example, the Guophone 9105 which also uses an MTK6589. This has a troubling tendency to reboot every random interval. Approx 6 times a week.
I have had success in the past running Linux systems built for much earlier kernels on later kernels. This suggests the ABI (application binary interface) for the Linux kernel changes rather slowly.
I am wondering how well the userland apps are separated from the kernel and drivers on Android.
Specifically, is it feasible to dump all the UI stuff from one phone onto another then change the init to launch the other UI?
Would this risk bricking the phone, or would the shell commands and ADB infrastructure still likely operate?
I guess I should change the bootloader to one that supports fastboot first, right? Is ther a how-to on achieveing this from the root shell?
Thanks for any thoughts
Nick.
Nick Hill said:
Hi
I am new to hacking android. I have built linux distros in the past, and have worked with Linux for 15 years,
I have just rooted a ZTE V965. It doesn't come pre-installed with Play store, and has all sorts of ZTE-specific Chinese apps. It has a good baseband circuit, a good screen, reasonable camera and I think is a great value phone, apart from the awful UI.
It is an android phone, although heavily customised. It has an MTK6589 processor coupled with 4Gb ROM and 512Mb RAM.
I have other phones which operate a much more "Vanilla" android. For example, the Guophone 9105 which also uses an MTK6589. This has a troubling tendency to reboot every random interval. Approx 6 times a week.
I have had success in the past running Linux systems built for much earlier kernels on later kernels. This suggests the ABI (application binary interface) for the Linux kernel changes rather slowly.
I am wondering how well the userland apps are separated from the kernel and drivers on Android.
Specifically, is it feasible to dump all the UI stuff from one phone onto another then change the init to launch the other UI?
Would this risk bricking the phone, or would the shell commands and ADB infrastructure still likely operate?
I guess I should change the bootloader to one that supports fastboot first, right? Is ther a how-to on achieveing this from the root shell?
Thanks for any thoughts
Nick.
Click to expand...
Click to collapse
Hi Nick, I have the same phone. I'm also very new to android, last phone was iOS and before that windows. I managed to root the V965 using Vroot. I also managed to install SuperSU and CWM. However, the CWM is not fully functional, I can only do a factory reset, not install any packages or roms. Probably the phone has a locked bootloader. I can't check, because the USB driver with the phone doesnt support fastboot.
I really need to get google play working in this phone, read a lot of stuff, tried many things, but I havent succeeded yet. Please let me know if you make any progress.
In China they are flashing this phone, found some ROMs even, but I am not sure how they manage and google translate isn't much help there.
http://www.romjd.com/Device/zte-v965/hot/all/1
Hmmm my V965 is having some issues now
After a factory reset, the setup wizard keeps crashing. Even after another resest. So I can't get in the phone anymore.
Any chance you can send me the USB drivers that are on the phone? My phone isnt deteceted anymore, so I can't access the drivers, which I want to reinstall. And of course they are not on the ZTE website.
Byte_Me said:
Hmmm my V965 is having some issues now
After a factory reset, the setup wizard keeps crashing. Even after another resest. So I can't get in the phone anymore.
Any chance you can send me the USB drivers that are on the phone? My phone isnt deteceted anymore, so I can't access the drivers, which I want to reinstall. And of course they are not on the ZTE website.
Click to expand...
Click to collapse
Hi
You can temporarily download the ZTE v965 USB drivers from
www dot nickhill dot co dot uk forward slash ztev965usb dot zip
Byte_Me said:
Hi Nick, I have the same phone. I'm also very new to android, last phone was iOS and before that windows. I managed to root the V965 using Vroot. I also managed to install SuperSU and CWM. However, the CWM is not fully functional, I can only do a factory reset, not install any packages or roms. Probably the phone has a locked bootloader. I can't check, because the USB driver with the phone doesnt support fastboot.
Click to expand...
Click to collapse
Fastboot and ADB appear to be standard protocols, at least on my Ubuntu, which don't need special drivers. However, it does appear that the stock boot loaader on the v965 does fail to incorporate the fastboot option.
If you remove the battery, replace it then turn on holding the volume down, you will get a menu, but fastboot is not there.
I don't know for a fact, but I do suspect that if you have access to the running android system as root, then you could in principle change any of the internal flash data. Therefore, in principle, I guess you could replace the boot loader or anything else in the running android system. Anyone please correct me if I am wrong, or confirm if I am right.
The feature set of this phone seems to be the same as the feature set of my Guophone. MTK6589, dual SIM, etc. So this image may be a good place to start if considering a transplant.
If you have ROMs, then perhaps it is possible to flash the ROM from a root terminal. I'm thinking add the uncompressed ROM to the Micro SD card, then using the dd command, block copy it to the appropriate image area on the internal ROM, reboot, reset to factory defaults.
If anyone more experienced than me with the nuts and bolts of Android can confirm or deny this will work, or where it should be put, please let me know.
An important factor is that the NAND is not locked on the ZTE V965. So if you have a root shell on the phone, you can issue the following command:
mount -o remount,rw /[email protected] /system/
Once you have done this, you will have read/write access to the system partition.
The only thing I then need to know is what should I avoid changing that may break the ADB bridge/root console?
And is all the UI stuff kept together, if so, where?
Shuffle it around a bit, make a new ROM
Thanks for the driver!
Unfortuntely it doesn't help
I found out the culprit, I tried to install gapps (google apps package) to the system app folder. I thought these changes would be reversed with a factory reset, but they are not. Setupwizard.apk keeps crashing and is preventing me from accessing my phone, so I must find a way to remove it from the system app folder. However, since this error occurred, I am not able to contact the phone in any way from the PC. Adb toolkit does not detect it, even when I reinstalled your driver. It's quite puzzling, I dont understand why in recovery mode I cannot connect adb-toolkit anymore.
Got my V965 working again, but it was a lot of hassle with shell access. Still not fully functional, no drives detected when i connect to USB, which is quite annoying, but not more than that. If you ever make any progress with google apps or flashing, please keep me informed, that would make this phone much more useable. I'll also keep hacking away at it, but without a bootloader unlock (I still think this is the problem), I don't think it will be possible.
I'm convinced it's possible to flash the phone, it seems they do it a lot in China.
I found a website with a couple of custom ROMs specific for the V965:
http://www.romjd.com/Rom/Detail/17086
And what I suspect is a rooting & flashing tool. Rooting works, I haven't figured out flashing yet.
http://dl.vmall.com/c0xa12brvo
I've also tried flashing from the settings - update menu in the phone, but it never finds the ROM (update.zip)
I did find another problem, I can't be reached on my phone, it always goes to voicemail. Same SIM in another phone works fine. No idea what's causing this.
Byte_Me said:
Got my V965 working again, but it was a lot of hassle with shell access. Still not fully functional, no drives detected when i connect to USB, which is quite annoying, but not more than that. If you ever make any progress with google apps or flashing, please keep me informed, that would make this phone much more useable. I'll also keep hacking away at it, but without a bootloader unlock (I still think this is the problem), I don't think it will be possible.
Click to expand...
Click to collapse
Hi
I might be able to help you with the problem.
I have a mint, unused ZTE v965. I have used MTK Droid root and tools to extract a backup of the entire new phone. It is currently uploading to www dot nickhill dot co dot uk forward slash ZTE-V965_new_backup.zip
You should be able to write this back to your phone using flashtool.exe.
I don't know for sure if this will work, so entirely at your own risk! Just trying to help. If unsure, ask around.
I am new to this forum, so please remember to click the thanks button if you find anything I have done helpful!
Meanwhile, the MTK droid root and tools has a function to remove much of the chinese stuff (once the system has been installed) and there is always the cyanogenmod gapps package. This may be worth investigating.
Nick Hill said:
Hi
I might be able to help you with the problem.
I have a mint, unused ZTE v965. I have used MTK Droid root and tools to extract a backup of the entire new phone. It is currently uploading to www dot nickhill dot co dot uk forward slash ZTE-V965_new_backup.zip
Click to expand...
Click to collapse
The file size should be 635,972,093 bytes and should finish uploading at 04:00 GMT
md5sum 17ecfdd1040d5dbfab70a3adbc24e07a
Thanks for the ROM, i'll give it a go. I will try to install it using the update option in the settings, that seems the safest.
Be careful with gapps. setupwizard.apk + factory reset = a lot of problems (if you install in system app folder)
OMG that tool is awesome. created CWM boot, installed your ROM, then installed a clean ROM, then installed gapps, all working!!!
Byte_Me said:
OMG that tool is awesome. created CWM boot, installed your ROM, then installed a clean ROM, then installed gapps, all working!!!
Click to expand...
Click to collapse
Firstly, I'm glad it's working for you.
Secondly, which tools did you use? Did you unpack the zip, open flashtools, select the scatter file then program the phone, or did you use some other method?
Which clean ROM did you then install, and how did you install it?
Did you then use MobileUncle to install CWM then use the cyanogenmod 10.1 gapps, or did you do something different?
It is useful to remember that MTKdroidtools has a useful function to remove chinese stuff. I think if more people contributed to the list of Chinese files that are safe to remove, that would be blade.
A detailed step-by-step guide might be helpful for anyone else with the same problem. One of the general problems I find is that there are plenty of guides around referring to this program, or that program, but few are detailed enough for someone who doesn't already know about those programs to use.
I pretty much bricked a Lenovo A766 yesterday, and it took several hours to learn about the tools to eventually unbrick it.
I would have rather spent my time understanding what is really going on, rather than spending my time learning vaguely what tool achieves what end result. If I understood more about the Android system, and built that knowledge on my understanding of Linux, I reckon I could achieve much more.
One thing I notice is that tablets and smartphones are actually replacing desktops and laptops. February this year, windows machines were down 7% YOY. I use Ubuntu for my main computer. Using these tools on Windows led me to significant frustration! This has led me to understand why there is a move. Maybe the tools provided for windows need to eventually move to android. We could then potentially use USB OTG to service other android devices. MTKdroidtools and flashtools runnng as a host on a separate Android system would be cool.
Nick Hill said:
Firstly, I'm glad it's working for you.
Click to expand...
Click to collapse
Thanks, me too
Secondly, which tools did you use? Did you unpack the zip, open flashtools, select the scatter file then program the phone, or did you use some other method?
Click to expand...
Click to collapse
I used MTK tools as described in that topic, rooted, made backup, installed CWM
Which clean ROM did you then install, and how did you install it?
Click to expand...
Click to collapse
I used the update tool from CWM to flash this ROM:
http://www.romjd.com/Rom/Detail/17086
That ROM is not very clean though, You might as well clean your own ROM
Did you then use MobileUncle to install CWM then use the cyanogenmod 10.1 gapps, or did you do something different?
Click to expand...
Click to collapse
CWM is installed using MTK Droid Root and Tools:
http://forum.xda-developers.com/showpost.php?p=44660171&postcount=417
This gapps version I installed: gapps-jb-20121011-signed
It's installed using CWM bootloader: install .zip package
It is useful to remember that MTKdroidtools has a useful function to remove chinese stuff. I think if more people contributed to the list of Chinese files that are safe to remove, that would be blade.
Click to expand...
Click to collapse
I used the delete China function, but it didnt catch very much. But with all the functions available now, it's quite easy to clean manually.
A detailed step-by-step guide might be helpful for anyone else with the same problem. One of the general problems I find is that there are plenty of guides around referring to this program, or that program, but few are detailed enough for someone who doesn't already know about those programs to use.
Click to expand...
Click to collapse
Yes, I plan to make a topic for this phone, but at the moment I am still testing many things.
I pretty much bricked a Lenovo A766 yesterday, and it took several hours to learn about the tools to eventually unbrick it. I would have rather spent my time understanding what is really going on, rather than spending my time learning vaguely what tool achieves what end result. If I understood more about the Android system, and built that knowledge on my understanding of Linux, I reckon I could achieve much more.
Click to expand...
Click to collapse
I know how you feel, I was ready to toss this phone in the trash
One thing I notice is that tablets and smartphones are actually replacing desktops and laptops. February this year, windows machines were down 7% YOY. I use Ubuntu for my main computer. Using these tools on Windows led me to significant frustration! This has led me to understand why there is a move. Maybe the tools provided for windows need to eventually move to android. We could then potentially use USB OTG to service other android devices. MTKdroidtools and flashtools runnng as a host on a separate Android system would be cool.
Click to expand...
Click to collapse
I have no idea about the possibilities there. I'm not a programmer, just someone who is good with computers and knows a little bit of everything.
PS. I could also use some thanks as well, maybe get some respect around here
Nick Hill said:
...
Click to expand...
Click to collapse
Did you give it a try yet? Another user did and google apps are working for him, so thats 2 for 2.
Are you still on your original ROM? If so, I have a question for you. Do you get notification badges on your icons, for instance, when you have a missed call, is there a red box with a 1 on the phone icon? Also, do your contacts get ID-ed when they call you? I have some problems with that, caused by the country code prefix. I am still running that ROM I downlaoded from the Chinese forum, but if your ROM doent have these issues, I will switch back ASAP.
Nick Hill said:
Firstly, I'm glad it's working for you.
Click to expand...
Click to collapse
as you are a Lenovo a766 owner, may you help me with this?
http://forum.xda-developers.com/showthread.php?p=49076877#post49076877
Where are configuration settings stored accross factory resets?
I have come to the (perhaps erroneous) conclusion that the user interface and what the user will experience is governed primarily from:
the APKs in
/system/app/
/system/vendor/operator/app/
and the configuration files pertaining to the installed apps, which is located at:
/data/user/0/
I guess that when the android device is factory reset, the /data partition is completely cleared, right?
Is there a set of standard configurations which are unpacked from somewhere into /data/user/0/ after a factory reset, or is it normal for all configurations to be stored in their respective APKs?
Hey, I have really basic information about computers and OSs so I really need some explanations for the case of android smartphone (qualcomm mainly). So let me tell you first what I know (I hope that this is true): For a computer they use EEPROM and it's a type of ROM which is erasable. The bios is stored there and it's the first thing loaded when starting the computer. (It's is easily updatable as I have already updated my bios). For the case of android smartphones I think that they use NVRAM, but I don't know what is NVRAM physically? is it a build-in memory separated from storage devices like on computers?! or is just a partition of internal storage? (internal storage I mean /dev/block/mmcblk0). I found that NVRAM can only be erased using JTAG on some websites but I found that device cloning is done copying mmcblk0 from one phone to another, so that means that NVRAM is located in mmcblk0. And if NVRAM is just a part of mmcblk0 so why is it a read only memory? we can easily write to other partitions, so why not NVRAM?! I'm really confused...
Please share your knowledge, I really need years of studying electronics and computer science to know all this by myself... Thank you all!!
AmineBY said:
Hey, I have really basic information about computers and OSs so I really need some explanations for the case of android smartphone (qualcomm mainly). So let me tell you first what I know (I hope that this is true): For a computer they use EEPROM and it's a type of ROM which is erasable. The bios is stored there and it's the first thing loaded when starting the computer. (It's is easily updatable as I have already updated my bios). For the case of android smartphones I think that they use NVRAM, but I don't know what is NVRAM physically? is it a build-in memory separated from storage devices like on computers?! or is just a partition of internal storage? (internal storage I mean /dev/block/mmcblk0). I found that NVRAM can only be erased using JTAG on some websites but I found that device cloning is done copying mmcblk0 from one phone to another, so that means that NVRAM is located in mmcblk0. And if NVRAM is just a part of mmcblk0 so why is it a read only memory? we can easily write to other partitions, so why not NVRAM?! I'm really confused...
Please share your knowledge, I really need years of studying electronics and computer science to know all this by myself... Thank you all!!
Click to expand...
Click to collapse
Well, I didn't understand a damn thing you just just said, but I can tell you this:
ROM, in the Android world, means the OS or firmware the device runs on. Like Windows or Linux. You can have the stock ROM, which is what the device ships with. Or, if the device allows it, you can install a custom ROM, such as Cyanogenmod.
"ROM" can mean other things in different contexts. You can find these out for yourself by using this thing called "google". But in the Android world, it simply means the operating system.
Planterz said:
Well, I didn't understand a damn thing you just just said, but I can tell you this:
ROM, in the Android world, means the OS or firmware the device runs on. Like Windows or Linux. You can have the stock ROM, which is what the device ships with. Or, if the device allows it, you can install a custom ROM, such as Cyanogenmod.
"ROM" can mean other things in different contexts. You can find these out for yourself by using this thing called "google". But in the Android world, it simply means the operating system.
Click to expand...
Click to collapse
Thanks for the quick reply! but I'm not talking about ROM files. I'm asking about this http://en.wikipedia.org/wiki/Read-only_memory
Of course I already tried googling it but it's just general information, I'm searching for information about android hardware (qualcomm mainly).
Any idea about android devices ROM (Read Only Memory) please?!
I'm not sure about low-level stuff (like the actual bootloader, which probably is isolated on different ROM chips on various devices), but most of what we normally consider the "ROM" -- i.e. the Android system software discussed above -- and even a sort of miniature OS for performing updates called the recovery -- is stored on a flash memory chip (sometimes eMMC) within the phone. Definitely not NVRAM/EEPROM, though the bootloader could be on one of those.
maclynb said:
I'm not sure about low-level stuff (like the actual bootloader, which probably is isolated on different ROM chips on various devices), but most of what we normally consider the "ROM" -- i.e. the Android system software discussed above -- and even a sort of miniature OS for performing updates called the recovery -- is stored on a flash memory chip (sometimes eMMC) within the phone. Definitely not NVRAM/EEPROM, though the bootloader could be on one of those.
Click to expand...
Click to collapse
Thanks! I think some information should be on NVRAM, if not why do people use JTAG to unlock devices?! Flash memory can be edited easily using usb cable only...
AmineBY said:
Thanks! I think some information should be on NVRAM, if not why do people use JTAG to unlock devices?! Flash memory can be edited easily using usb cable only...
Click to expand...
Click to collapse
I don't think it's possible to edit flash memory with USB cables alone on most devices; that's actually rather tough and requires a phone that's had its bootloader unlocked (even then, official bootloader unlocks -- like HTC's -- don't always let you write over certain bits of it). Not quite sure about the JTAG stuff -- that reaches the limits of my knowledge.
Hello everyone, I'm a total noob but I solved a problem which I couldn't find the answer to, so I thought I'd share. Please take care following my noob advice, I'm not responsible for anything which goes wrong with your phone (and if it gets complex, I probably don't have the skills to help)!!
What was my problem?
When I went from Nougat to Oreo, my radio broke (no cell reception). However I had the files from LGUP, so I could flash "fsg" "modem" "modemst1" and "modemst2" in fastboot (as explained here) which did indeed fix my modem problem, giving me back radio and data. However, this also made the fingerprint scanner disappear from my phone's settings menu. As far as I could tell, this wasn't a problem related to encryption (as discussed in AO ROM thread a lot, which is what I'm now running), rather 'twas a problem with the firmware! So I was loving Alpha Omega, but left without fingerprint scanner since radio isn't really optional on a phone.
Solution?
Please remember, I'm a noob and have only done this for my own phone, a h910, I don't know if i will work for you or on other models!!
Basically, I mish-mashed the two modem files from Oreo and Nougat, to get both things working!
Steps I took:
1) Use Linux - I couldn't get the files to open properly in windows, and didn't find a way to write to the image files.
2) Find a stock "modem.img" file from Oreo (i searched on google "stock oreo h910 modem and it came straight up) - I think I am too new on this forum to post outside links so you'll have to search for it.
3) Find a stock modem file from nougat (I used my original LGUP dump file from nougat, renamed to .img) I'm not sure if it is important that this came from your phone or not, if you followed all the instructions on the dirtysanta root guide, you'll have this as part of your LGUP backup.
NOTE: both of these files were 86 Mb (helped me feel confident I'd found the right thing on google)
4) Create backup copies of both, and append ".img" to your LGUP "modem" file. Call the backup of your OREO modem (the one you got off of google) "MyModem.img", just to keep it clear for later.
5) Mount the NOUGAT img first in a terminal (might have to make a mount point first), for me this was like this:
Code:
sudo mkdir /mnt/modemfiles
mount -o loop /path/to/your/nougat-modem-file.img /mnt/modemfiles
You obviously have to put the file path to where you saved your NOUGAT modem image - the one from LGUP!
6) You should now be able to see the nougat modem .img mounted as a disk in "places" on your file explorer. Go there, and copy the contents into a new folder somewhere easy to find (make a folder on your desktop called NougatModem.) There are two folders iniside, one called "image" and one called "verinfo".
7) Now you can un-mount, as we have what we need from it, easiest to do by just right-clicking it in file explorer and select unmount.
8) Next we will mount the image which will become your new (hopefully working!) modem, but it has to be writeable, so using the same mount point we would do
Code:
sudo mount -o loop,rw /path/to/MyModem.img /mnt/modemfiles
Remember that "MyModem.img" should be your backup OREO image - where all the firmware works but you don't get radio.
9) Now basically comes replacing a few files in the OREO modem (which we have mounted) with ones from your original NOUGAT backup (which are in that folder on your desktop). I couldn't remember if cp command replaced things with the same name, so I used rm to remove files, and then cp to replace them once they were gone.
a) first it is the folder called modem_pr, inside image
Code:
sudo rm -R /mnt/modemfiles/image/modem_pr/
b)next were all the files in the image directory which were modem.SOMETHING
Code:
sudo rm /mnt/modemfiles/image/modem.*
10) Finally we have to replace those files and the folder with the same things from our NOUGAT folder which is on our desktop, using the copy command. I will put the commands as if you did name that folder NougatModem
a) so first the folder which we removed
Code:
sudo cp -r ~/Desktop/NougatModem/image/modem_pr/ /mnt/modemfiles/image/
b) now all the files again, using the wildcard for the different extensions
Code:
sudo cp ~/Desktop/NougatModem/image/modem.* /mnt/modemfiles/image/
So if all went to plan, you now have an image (which you can unmount), called MyModem.img, which you can flash in fastboot to the modem parition (fastboot flash modem /path/to/MyModem.img) and if it works for you like it did for me, you have cell reception, data (after putting in APN if it's needed) and fingerprint scanner all working on OREO. Again, I'm on Alpha Omega, loving the rom and now going to go play a bit.
I've not been on the forum long, but have just gained a HUGE insight into how much time people put into making guides and helping others learn (this has taken me ages haha). Thanks to everyone for your hard work and community spirit, please let me know if this works for you or if it provides any interesting insight as I really did it blind (I had no idea if it would work, and was just making some slightly educated guesses - I got lucky!). Also, if the instructions are hard to follow and you have a hint, I'm happy to edit them to make them clearer.
ENJOY!!
PS - I know the linux commands could be better haha, using more than one mount point too might have been easier, but I figured that I'd just keep it exactly the same as how I did it since I'm a noob and would be more likely to screw something up in the instructions, if I changed it without trying at the same time!
EDIT: I could also upload my "patched" modem image, but not sure if it will work for other people's phones, or if it has "personal" or unique info in it (basically if it would be safe to do so) - If someone who knows tells me it'd be good to go, I'm happy to share it if it would save people from having to go through the whole process. I guess I hope posting all this will be a learning thing for others too Gotta have some justification haha!!
You are to be commended on your well presented write up. But I'm sure there is an easier way to get data and fingerprint working without going through all of that.
I don't have an original H910 device but I did flash H910 oreo kdz on my device and data did not work at all. Didn't test fingerprint. All I did was flash modem using lgup patched from another variant and that solved it.
ezzony said:
You are to be commended on your well presented write up. But I'm sure there is an easier way to get data and fingerprint working without going through all of that.
I don't have an original H910 device but I did flash H910 oreo kdz on my device and data did not work at all. Didn't test fingerprint. All I did was flash modem using lgup patched from another variant and that solved it.
Click to expand...
Click to collapse
Thank you for the commendation haha! What a mission!
So I'm guessing you flashed a different version's KDZ?? As far as I'm aware from lots of reading here on xda, there are no KDZ files for the h910. For me the kdz from h915 worked perfectly for example, apart from data. And that was the story with a few things I flashed, KDZ or ZIPs, they would break data, I'd flash the modem, and that would break the fingerprint scanner. Hence this long-winded solution lol.
If you have an original h910 kdz that people don't know about that'd be interesting in itself!!
No, I flashed a H910 ZIP that someone kindly uploaded here somewhere. Then I flashed back the modem from a Verizon kdz.
You are the best, I have been trying to solve this for a long time, I tried flashing many things it thanks to you I now have a working fingerprint and data. Although I am a complete noob for using linux I just used it for the first time using live boot. This is a challenge for noobs but worth it at the end and big thanks.
Why not just cross flash to us996 and walk away? 0_o You get a newer modem this way. I think you have to enable bands on some devices but on h910 I don't think even this matters. You are just downgrading the modem and keeping the new bootstrap. Still from what I read this is encryption issue. There was a supposedly a rsa key change during the update... without them matching the bootstrap will not will not load fingerprint software as it's not trusted unless it matches.
Vortell said:
Why not just cross flash to us996 and walk away? 0_o You get a newer modem this way. I think you have to enable bands on some devices but on h910 I don't think even this matters. You are just downgrading the modem and keeping the new bootstrap. Still from what I read this is encryption issue. There was a supposedly a rsa key change during the update... without them matching the bootstrap will not will not load fingerprint software as it's not trusted unless it matches.
Click to expand...
Click to collapse
So should I flash the whole ROM or just the modem of us996 to have both working?
DesrtSailor said:
You are the best, I have been trying to solve this for a long time, I tried flashing many things it thanks to you I now have a working fingerprint and data. Although I am a complete noob for using linux I just used it for the first time using live boot. This is a challenge for noobs but worth it at the end and big thanks.
Click to expand...
Click to collapse
Just wanted to say that made my day when I read that the original post had helped you out Cheers for letting me know
Awesome!! Thanks for this. Where did you get the idea of what files to change? Just curious.
I am still tinkering. I have an LGUP dump from:
ATT Stock
A-O Nougat install
A-O Oreo install
I was mix and matching the modem files with various modemst1 and modemst2 files. I did this because it seemed that I got better signal strength with the A-O Nougat install... but I got the kernel panic/modem crash whenever I lost signal on the phone. But with this hand made modem file - no crash. But now I am going to continue mix/match and see what crashes and what gives the best signal strength.
Anyway thanks a bunch!!
Please give me the patched modem file, please send it to [email protected]
I would root then try activity launcher or some sort if hidden menu launcher to get band menu. Alternatively get Network signal guru and lock bands. That how i did it in los 17.1 not sure if it would work on stock. I went from hspa to lte doing it in h915(it's a Canadian h910). I even crossflashed to us996 and left it that way. Says it even says band 66 was unlocked in the app but it has not been tested yet. Either way I got band 4 and 12 once I did this.