Related
Hello,
I recently uninstalled some (system / T-Mobile) apps with Titanium Backup. And I did not make a backup first. The phone still runs fine but the OTA fails.
I tried so far:
- RUU 1.28 -> does not work, because system is already 1.29
- find rom.zip and unpack -> Ok, but cannot unpack system.img, unyafs fails.
The file which the OTA misses, according to logfile is named: 4661_TMODE_Music_One.odex
If someone could sent me this file or upload it somewhere I would be thankful.
There is a good chance that there are more files missing, but the log stops after the first fail.
I see in the system.img that there are at least 4 files with similar names:
4661_TMODE_Music_One.odex
4661_TMODE_Music_One.apk
4662_TMDE_Games_One.odex
4662_TMDE_Games_One.apk
If anyone knows how to unpack these, this would also helpful.
deleted
I think the best way to get all your bloatware back is to lock the bootloader and then flash the 129 RUU. Here is the link for the RUU if its T-mobile uk.
http://www.filefactory.com/file/6y1...Radio_1.1204.105.14_release_260731_signed.exe
Once your back to stock you can unlock again with your unlock token, flash cwm and make a stock nandroid backup.
If you need a file factory password pm me.
No, it's T-Mobile Germany, so I guess this will not help.
At the moment I'm trying to unpack the files from the system.img, but none of the methods described in the forums are working.
It is almost crazy, I can see the filenames and contents (lots of "PK" headers for instance) within the system.img but I've no idea how to extract them.
Get in touch with football. He might be able to get the RUU for you.
ghori1989 said:
Get in touch with football. He might be able to get the RUU for you.
Click to expand...
Click to collapse
Ok, tried that, waiting for the reply.
Meanwhile I'm able to mount the system image with some modifications as ext4 image and copy the contents. If there is an interest for this, I propably could write some tool to make this automatic.
Anyway, it did not help me, because the versions of the files in the image do not match the ones expected from the OTA.
Hey guys,
It seems more and more people are receiving the new version of the P8000:
- Stock Android 6
- New fingerprint scanner that is moved slightly higher and is able to unlock phone from screen-off (I confirm this is working)
- Sim 2 is combined with the micro-sd (I haven't tried whether you can have them both in at the same time)
- Somethings new about the display, since people are reporting errors with it after flashing older roms.
Warning: do NOT flash other roms. We have no way to unbrick the soft bricks yet!
---
Other topics that refer to this version:
http://forum.xda-developers.com/elephone-p8000/general/rom-p8000-t3431571
http://forum.xda-developers.com/elephone-p8000/help/stock-rom-p8000b-t3434477
http://forum.xda-developers.com/elephone-p8000/general/p8000-version-announced-t3346848
---
For development:
- The phone does not come pre-rooted. We have no way to flash custom recovery yet. Any tips for getting root? I've tried such tools as Kingo and vRoot, they don't work.
- We need the blocks file (scatter file) for SP Flash Tools. MTKDroidTools reports "unknown rom structure". Any help? Would love to start working on this.
Looking forward to hearing from others who have this version/who can help me with these questions.
Thanks!
Emile
Nice! Can you provide a dump from /system and /boot maybe?
BlueFlame4 said:
Nice! Can you provide a dump from /system and /boot maybe?
Click to expand...
Click to collapse
I would, if I knew how to. Any pointers?
Emileh said:
I would, if I knew how to. Any pointers?
Click to expand...
Click to collapse
Sure thing. On a rooted device, go into adb shell.
Then use "mount" command to check which partitions are mounted. One should be "/dev/block/platform/mtk-msdc.0/by-name/system" or similar. Use "dd if=/dev/block/platform/mtk-msdc.0/by-name/system of=/storage/emulated/0/system.img bs=1M" to dump the system to the internal sdcard to the file "system.img". If adb complains that bs=1M is an invalid option, try again without that one. A system dump can take some time where you will not get any feedback, so be patient there
Do the same for boot. So "/dev/block/platform/mtk-msdc.0/by-name/boot" should be the way to go for the path. I cannot tell the definite pathes on Android 6.0 but I am rather sure they are more or less like this.
If you run into troubles, just ask
BlueFlame4 said:
Sure thing. On a rooted device, go into adb shell.
Then use "mount" command to check which partitions are mounted. One should be "/dev/block/platform/mtk-msdc.0/by-name/system" or similar. Use "dd if=/dev/block/platform/mtk-msdc.0/by-name/system of=/storage/emulated/0/system.img bs=1M" to dump the system to the internal sdcard to the file "system.img". If adb complains that bs=1M is an invalid option, try again without that one. A system dump can take some time where you will not get any feedback, so be patient there
Do the same for boot. So "/dev/block/platform/mtk-msdc.0/by-name/boot" should be the way to go for the path. I cannot tell the definite pathes on Android 6.0 but I am rather sure they are more or less like this.
If you run into troubles, just ask
Click to expand...
Click to collapse
Thank you for your great instructions! The problem is that we've yet to achieve root on this device. We don't have a custom recovery for this version of the P8000 yet and other 'standard' methods of rooting don't work for me.
(I'm pretty solid in shell, so I'll do this afterwards, but I guess root is actually the first step).
// Edit to say: it does not come pre-rooted
Since the elephone support on facebook didn't realize there are two different versions of the P8000 available, I still need a ROM to unbrick my phone.
flo1k said:
Since the elephone support on facebook didn't realize there are two different versions of the P8000 available, I still need a ROM to unbrick my phone.
Click to expand...
Click to collapse
Ok, we know that, but doesn't really help us
Can you write them an e-mail?
I will do
Edit: OK, see if there will be an answer.
Thank you flo1k!
I have e-mailed as well, and would like to post on the Elephone forum, but don't seem to have access (because of minimum post count, I guess)
Anyone willing to ask for a ROM for the new P8000 on the forum there?
ROM Dump
@BlueFlame4
I can provide ROM dump in two versions:
1) a dump from adress 0000 0000 to 9d80 0000 (apr. 2.5 GB in one file)
2) a readback generated with the scatter.txt of the 'old' 5.1 stock ROM (apr. 2.8 GB seperated in 23 files)
FrauHofrat said:
@BlueFlame4
I can provide ROM dump in two versions:
1) a dump from adress 0000 0000 to 9d80 0000 (apr. 2.5 GB in one file)
2) a readback generated with the scatter.txt of the 'old' 5.1 stock ROM (apr. 2.8 GB seperated in 23 files)
Click to expand...
Click to collapse
The second choice looks promising
Maybe a stupid question
where shall I upload the files - any preferred webspace?
I'm uploading the files - because they contain my NVRAM I send the link as PM as soon as the upload is finished
FrauHofrat said:
Maybe a stupid question
where shall I upload the files - any preferred webspace?
I'm uploading the files - because they contain my NVRAM I send the link as PM as soon as the upload is finished
Click to expand...
Click to collapse
Are you sure we're talking about the same version of the P8000? Cause as far as I know there isn't 5.1 available for this version... Right?
Just checking thank you for your help in any case!! Really looking forward to it.
// edit: ah, you just used the old scatter file. But does that one work for this version?
Emileh said:
Are you sure we're talking about the same version of the P8000? Cause as far as I know there isn't 5.1 available for this version... Right?
Click to expand...
Click to collapse
No, there is only one Firmware available - the mysterious P8000_6.0_20160516.
Btw, this Phone contains a new mainboard model "K06TS-L-V2.0.3" - the 'old' mainboard is moder "K05T...."
// edit: ah, you just used the old scatter file. But does that one work for this version?
Click to expand...
Click to collapse
No, it doesn't work resp. the phone boots with this firmware, but the LCD-driver is the wrong one - the display only shows coloured lines and blurry spots. And there are probabely some more bugs ....
FrauHofrat said:
No, there is only one Firmware available - the mysterious P8000_6.0_20160516.
Btw, this Phone contains a new mainboard model "K06TS-L-V2.0.3" - the 'old' mainboard is moder "K05T...."
No, it doesn't work resp. the phone boots with this firmware, but the LCD-driver is the wrong one - the display only shows coloured lines and blurry spots. And there are probabely some more bugs ....
Click to expand...
Click to collapse
But if the phone boots with the firmware, doesnt that mean that the scatter file of the regular P8000 works? Since it flashes the firmware correctly.
The problem is that I was not able to flash the 'readback files' to the faulty phone.
When selecting 'Only Download' at SP-Flashtool I got the error "PMT... must be download"
When selecting 'Firmware Upgrade" I got some BROM error code
In both cases I used the same scatter,txt which I used to 'readback' the firmware from the working phone
Actually I have to correct my statement in post #15:
I flashed the faulty phone with the last 5.1 stock ROM (160711) - with this stock ROM the phone boots up but LCD (and probably more things) is not working.
I have actually gotten alot further
You have the use the scatter.txt from Android 6.0, which works perfectly fine. I have been able to extract boot.img, system.img and recovery.img that way (using Readback in SP Flash Tools)
Which ones do you need?
They probably flash fine (only thing I've flashed so far are custom recoveries, and although my ported PhilZ starts, I havent gotten it to mount anything.)
A little warning: don't use anything that has anything to do with Android 5.1. Those scatter files don't work
These are great news!
"Which ones do you need?"
Probably all of them
Ok this contains the scatter file, preloader, system.img, boot.img and stock recovery.img
https://ehaffmans.stackstorage.com/index.php/s/uKGKCir0BociydU
You need SP Flash Tools v5, select the scatter file first, then deselect everything, and only select these 4 and manually select the correct files.
Btw, the name of the preloader file is wrong, don't worry. It came from this phone
I am of course not responsible for anything!
Can you guys please confirm this doesn't contain anything personal? Like personal files or IMEI or something. Thanks!
Phone stopped making any sounds.
what works: bluetooth, wifi, sim card (data + receiving texts, calls not tested)
what doesn't: sensors (rotating), camera, sound
dmesg https://pastebin.com/gY1pgn96
What was flashed that I can find/remember in no particular order
H810_UsU_unlock.zip
h810_21y_modem.zip
H810_UsU_baseband_flash-in-twrp.zip
G4_29a_N_modem_UsU.zip
LG-G4_VideoLag-Fix_EXTRACTME-AND-READ-THE-README.7z
h810_10o_UsU_bootloader_ARB2.zip
lineage-15.1-20190121-UNOFFICIAL-h810_usu.zip
lineage-15.1-20190409-UNOFFICIAL-h810_usu.zip
lineage-16.0-20190512-UNOFFICIAL-h810_usu.zip
and magisk + gapps
zip of sbl1 rpm tz pmic partitions attached.
On a side note I see h810_10o_UsU_bootloader_ARB2.zip that I forgot about earlier. Explains the ARB2 that the phone is at now. Looking back through my bash history I was having these issues before I flashed this.
@steadfasterX per request
You flashed so much stuff steadfaster can't even help you
baconbacon said:
Phone stopped making any sounds.
what works: bluetooth, wifi, sim card (data + receiving texts, calls not tested)
what doesn't: sensors (rotating), camera, sound
dmesg https://pastebin.com/gY1pgn96
What was flashed that I can find/remember in no particular order
H810_UsU_unlock.zip
h810_21y_modem.zip
H810_UsU_baseband_flash-in-twrp.zip
G4_29a_N_modem_UsU.zip
LG-G4_VideoLag-Fix_EXTRACTME-AND-READ-THE-README.7z
h810_10o_UsU_bootloader_ARB2.zip
lineage-15.1-20190121-UNOFFICIAL-h810_usu.zip
lineage-15.1-20190409-UNOFFICIAL-h810_usu.zip
lineage-16.0-20190512-UNOFFICIAL-h810_usu.zip
and magisk + gapps
zip of sbl1 rpm tz pmic partitions attached.
On a side note I see h810_10o_UsU_bootloader_ARB2.zip that I forgot about earlier. Explains the ARB2 that the phone is at now. Looking back through my bash history I was having these issues before I flashed this.
@steadfasterX per request
Click to expand...
Click to collapse
Perfect thx that explains a lot..
As you mentioned already the bootloader stack thing but also another one you flashed 21y modem .. I will need some time to investigate both things and come back to you asap
Update:
ok so the worst thing you had done was flashing the 21y modem. The problem with that one is that it is ARB 3 (see known ARB) and so blown fuses (in areas not related to the bootloader ARB but for firmware).
Anyways that will refuse using several parts of your firmware now.
There is no guarantee if the following would make things even more worse but that's what I would try:
extract the system and the modem partition of the 21y kdz
grab the "etc/firmware/venus.*" files from the extracted system partition and copy them to system/etc/firmware/ (mount "system" in TWRP before)
grab the "image/a2dsp.*" files from the extracted modem partition and copy them to /firmware/image (mount "Firmware" in TWRP before)
boot again and grab the dmesg as soon as possible
again that can make things even more worse so you do this on ur own risk.
Sent from my OnePlus 6T using XDA Labs
Before I do this, because hell why not , is the 21y here https://storagecow.eu/index.php?dir=Xda/LG+G4/H810/AT&T/ what I am looking for? Want to be sure before I make matters worse for myself.
baconbacon said:
Before I do this, because hell why not , is the 21y here https://storagecow.eu/index.php?dir=Xda/LG+G4/H810/AT&T/ what I am looking for? Want to be sure before I make matters worse for myself.
Click to expand...
Click to collapse
Yes the rar file. It will contain a TOT file (so you cannot use SALT to extract) .
TOTs require the windows software :
https://forum.xda-developers.com/showthread.php?t=2600575
Sent from my OnePlus 6T using XDA Labs
How do I grab the files out of system.img . I had to use WindowsLGFirmwareExtract-1.2.1.0-Release as the newest one would dump 20G+ junk files.
Code:
$ file system_691200.bin
system_691200.bin: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
I can't mount the file, after making it the size it wants with "truncate -s $((1159168*4096)) system_691200.bin" it will mount but then is completely empty. Repairing with fsck annihilates everything. What is the trick to dumping/mounting this?
modem.img mounted fine.
baconbacon said:
How do I grab the files out of system.img . I had to use WindowsLGFirmwareExtract-1.2.1.0-Release as the newest one would dump 20G+ junk files.
I can't mount the file, after making it the size it wants with "truncate -s $((1159168*4096)) system_691200.bin" it will mount but then is completely empty. Repairing with fsck annihilates everything. What is the trick to dumping/mounting this?
modem.img mounted fine.
Click to expand...
Click to collapse
The latest should work fine but you have to merge (!) the files once extracted which is a separate option in that tool. For mounting you could then use SALT (advanced menu) if you like
Sent from my OnePlus 6T using XDA Labs
It only extracts one system file, system_691200.bin, there is nothing to merge. That's with 1.2.6.1, I tried several different versions and all of them only list/extract one file. The tot I used is not corrupt (i believe), downloaded 3 more and they all had the same md5.
Do you know offhand if I would be able to push the system_691200.bin onto the phone and mount it just to grab those files?
baconbacon said:
It only extracts one system file, system_691200.bin, there is nothing to merge. That's with 1.2.6.1, I tried several different versions and all of them only list/extract one file. The tot I used is not corrupt (i believe), downloaded 3 more and they all had the same md5.
Do you know offhand if I would be able to push the system_691200.bin onto the phone and mount it just to grab those files?
Click to expand...
Click to collapse
ok when it lists only 1 file there it is only 1. Lemme check if I can do that today.
EDIT:
ah yea another reason why I hate that windows tool.. it extracts bull****.. trying to fix that but that can take some secs
EDIT2:
wow thats is really a stubborn crap.. Cannot mount, resize, fsck, fix, testdisk/photorec , ... (and yea I used DD to get the correct size, offset ...)
EDIT3: @baconbacon
no one is as stubborn as me lol..
ok I have not figured out why that crappy windows software does not extract it correctly but I searched and found another extractor here. (whoa.. that way I could make TOT files support available in SALT...)
compiled. ran. mounted. simply works..
so here you go: http://leech.binbash.it:8008/stock/LG/h810/21y_arb3
you just need: h810_21y_ARB3_system-etc-firmware.tgz
download that one.
extract it and follow the prev post here
jfi:
I am currently uploading the full system image and other stuff of that firmware as well (should be fully uploaded in 40 min or so)
.-
That fixed it completely! Sound works, rotation works, camera works. Installed the newest rom and the phone is quite snappy now. As a bonus it also fixed the video lag.
Thank you very much, you went above and beyond to help me fix this. Is that bitcoin address on your profile accurate?
baconbacon said:
That fixed it completely! Sound works, rotation works, camera works. Installed the newest rom and the phone is quite snappy now. As a bonus it also fixed the video lag.
Thank you very much, you went above and beyond to help me fix this. Is that bitcoin address on your profile accurate?
Click to expand...
Click to collapse
GREAT ! Glad we solved it.
I really hoped it will fix it and yea that's again a proof of fusing in modem and firmware files (due to flashing the 21y modem).. I will remove that one from the list so no one will go for the same journey.
yea my BTC is fine but given some thx click on any of my posts is fine too
have fun!
.-
Hello Guys,
i opened the thread in the Question&Answer Forum but somehow i have an different approach now that i learned how to rollback an firmware version with an locked bootloader. i dont know if it is possible, i more want to open like a discussion about it if this would be an thing someone could possibly do (and thats the reason im opening another thread for it, since it is not the same question anymore as in the other thread).
well, you can flash an image like EML-L29 8.1.0.129 to the device via the dload method. this image installs just fine, great. but now.. in my understanding the interesting part is this update.app. this update.app as far as my knowledge goes contains all this img files. you know, kernel system boot recovery etc.. wouldnt it be possible to simply replace the recovery.img with an twrp recovery.img, put the update.app back together, zip it in the necessary update_sdcard file and try to install it? i read about the tool "HuaweiUpdateExtractor", and this handy nice tool is showing the files.
another thought of me is: the installer is *verifying* the update.app somehow. but if it is verifying this file, there must be like a crc-file, some way of telling "this file is original" or "this file is okay". so maybe this is another part of the problem that i would have to take care of. but still i would need to know a lot more about the way the eRecovery works.
my ultimate goal is to solve the bootloader code problem since tackling it with dc-unlock and hcu wont work cause the security patch level seems already too high in the first versions of this phone. im basically search now ways around it - i know, there is actually no way to do it, but this is the reason why im opening this thread in hope to get some clues or ideas - and telling my own. oh and im pretty sorry if this is maybe annoying, i surely dont have any intention of spam the forums or stress too much on this topic (but it got me very interested).
Edit: i read in another board that it is nearly Impossible to switch the img files because they are encrypted. I guess it is not possible with this method so basically.. just ignore this thread. I guess there is really no way.
Also I think they have to do some checksum when flashing, so it's really impossible to just switch files...
About dload, i'm on 9.0.0.293 on EML-L29C432
I try the dload method to rollback to android 8.1, no success
i use an usb otg, created dload folder to root and place update.app extracted zip in dload folder
Also i created an "EML-L29_hw_eu" folder inside dload with again extracted from the hw zip file
When i use the dialer method, phone recognize the update.app file and reboot
after reboot to recovery, i have an error and i can't downgrade
What i did wrong ?
thanks
bender8125 said:
About dload, i'm on 9.0.0.293 on EML-L29C432
I try the dload method to rollback to android 8.1, no success
i use an usb otg, created dload folder to root and place update.app extracted zip in dload folder
Also i created an "EML-L29_hw_eu" folder inside dload with again extracted from the hw zip file
When i use the dialer method, phone recognize the update.app file and reboot
after reboot to recovery, i have an error and i can't downgrade
What i did wrong ?
thanks
Click to expand...
Click to collapse
well the biggest problem may be the image itself that you are trying to flash. if you take it from firmwarefinder, you will get most likely absolutely no success. you need to take one from androidhost.ru, the ones there worked for me. there you just put everything in the dload folder on your USB-Stick. oh and better use an full-OTA, not just an simple ota update, because that wont work (you cant just update a few files when you are already on EMUI 9). and on top of that: backup your phone first, because it is possible that after your downgrade you lose all data on your phone.
oh and another thing if you just want to get back to EMUI 8.1 (not a specific version you wish for), just use hisuite, because they are allowing the downgrade even more easily. the method i mentioned above is if you try to flash a specific version like i did with 8.1.0.120
Hi,
I have my 5T rooted with Magisk and TWRP recovery.
I've upgrated from OOS 9 to official OOS 10.0.1 flashing with TWRP as usual. I did a full nandroid backup before.
Everything went fine until I noticed that during the booting of the phone after the flashing, it didn't ask for the SIM code as it used to. And once the mobile had fully restarted, I could see 2 new icons on top of the screen picturing the 2 sim cards that can be contained in a OnePLus 5T. They were striken through, as if not present, when I had My SIM in Slot 1. And so, no mobile signal, no data network.
I tried switching Sim cards with another mpbile. My SIM worked fine in the other mobile and the other SIM was not recognized by my mobile.
I've read that I could be facing problems of damaged EFS. So I tried restoring through TWRP the EFS partition from the Nandroid I had done before. Nothing. Same thing with the modem partition. Nothing.
I tried then to restore the EFS from a safety backup that I had using Fastboot. Nothing.
I could still try to restore the full nandroid backup done at the beginning, but I forgot to take out pin protection code before taking the Nandroid, and I've read somewhere that it could be an issue after restoring the system. I might not be able to restart the phone and be obliged to factory reset, witch I would really like to avoid. And anyway, if restoring with Fastboot did not work, I wonder if the full restore would change anything.
Anyway, anybody has a magic idea about might be happening? A little help please??
Same problem!
I'm having the same problem. I have my 5T rooted with Magisk and TWRP recovery.
I've upgrated from OOS 9 to official OOS 10.0.1 flashing with TWRP as usual. I did a full TWRP backup before, including my EFS partition.
I'm seeing this too:
>"once the mobile had fully restarted, I could see 2 new icons on top of the screen picturing the 2 sim cards that can be contained in a OnePLus 5T. >They were striken through, as if not present, when I had My SIM in Slot 1. And so, no mobile signal, no data network."
I did the same thing and had the same no result.
>I've read that I could be facing problems of damaged EFS. So I tried restoring through TWRP the EFS partition from the Nandroid I had done >before. Nothing. Same thing with the modem partition. Nothing.
I'm looking for a solution too.
I came across this: https://forum.xda-developers.com/oneplus-5t/help/baseband-imei-lost-t3834334 and this: https://www.getdroidtips.com/how-to-repair-and-fix-imei-baseband-on-oneplus-5t-a5010/
I've been reluctant to try and rebuild the QCN file, but it might work.
Working on this
So I'm working on reprogramming the IMEI using the Qualcomm tools. I was able to use them to back up my phone and see the it still has the correct MEID.
However, the .gcn file linked to below isn't accepted, with a weird error: "The file model MSM8998 does not match the phone model MSM8998. Please select a file for the MSM8998."
I'm not sure what it isn't liking. In theory, I think I could just put the IMEI numbers into the QPST programming tool, but I'm not certain where they would go and the correct format for them (with the chksm at the end or not?).
This is as far as I've gotten. I'm looking for an alternate .qcn or .qcnx (which is the kind the tool generates when saving files).
rootlessabroad said:
I'm having the same problem. I have my 5T rooted with Magisk and TWRP recovery.
I've upgrated from OOS 9 to official OOS 10.0.1 flashing with TWRP as usual. I did a full TWRP backup before, including my EFS partition.
I'm seeing this too:
>"once the mobile had fully restarted, I could see 2 new icons on top of the screen picturing the 2 sim cards that can be contained in a OnePLus 5T. >They were striken through, as if not present, when I had My SIM in Slot 1. And so, no mobile signal, no data network."
I did the same thing and had the same no result.
>I've read that I could be facing problems of damaged EFS. So I tried restoring through TWRP the EFS partition from the Nandroid I had done >before. Nothing. Same thing with the modem partition. Nothing.
I'm looking for a solution too.
I came across this: https://forum.xda-developers.com/oneplus-5t/help/baseband-imei-lost-t3834334 and this: https://www.getdroidtips.com/how-to-repair-and-fix-imei-baseband-on-oneplus-5t-a5010/
I've been reluctant to try and rebuild the QCN file, but it might work.
Click to expand...
Click to collapse
Hi
I've found a code (*#06#) in a page that gives you the MEID. It worked for me. Hopefully, I have the correct MEID too. The code for the IMEI did not show anything. I'll check the lynks you posted later today.
Thanks for sharing!!
PS. I can not include the lynk to codes page as I'm too junior a member and XDA forums won't let me.
rootlessabroad said:
So I'm working on reprogramming the IMEI using the Qualcomm tools. I was able to use them to back up my phone and see the it still has the correct MEID.
However, the .gcn file linked to below isn't accepted, with a weird error: "The file model MSM8998 does not match the phone model MSM8998. Please select a file for the MSM8998."
I'm not sure what it isn't liking. In theory, I think I could just put the IMEI numbers into the QPST programming tool, but I'm not certain where they would go and the correct format for them (with the chksm at the end or not?).
This is as far as I've gotten. I'm looking for an alternate .qcn or .qcnx (which is the kind the tool generates when saving files).
Click to expand...
Click to collapse
So I've tried te rebuild the QCN file. But my issue is that I can't make the ADB comunicate with my mobile. It is as the mobile was not plugged in?? The usb debugging is activated. I can browse the mobile memory from the computer. But the ADB doesn't lynk with the mobile; when you type adb devices, it says List of devices attached and nothing after. Any idea what might be happening?
What about you rootlessabroad? could you fix it?
rootlessabroad said:
So I'm working on reprogramming the IMEI using the Qualcomm tools. I was able to use them to back up my phone and see the it still has the correct MEID.
However, the .gcn file linked to below isn't accepted, with a weird error: "The file model MSM8998 does not match the phone model MSM8998. Please select a file for the MSM8998."
I'm not sure what it isn't liking. In theory, I think I could just put the IMEI numbers into the QPST programming tool, but I'm not certain where they would go and the correct format for them (with the chksm at the end or not?).
This is as far as I've gotten. I'm looking for an alternate .qcn or .qcnx (which is the kind the tool generates when saving files).
Click to expand...
Click to collapse