Related
So, here is the firmware flash guide for B15Q. It assumes either a Win7 x86 machine or a x64 with driver signature verification disabled (but Win8/8.1 in any variant or W7x64 is NOT RECOMMENDED).
I assume no warranty for bricked devices, especially not if you manage to kill your PRELOADER or DSP_BL. Double and triple check before downloading.
0) Driver and toolkit setup
Get the driver set, scatter file and spFlashTool from this thread: http://forum.xda-developers.com/general/general/stock-rom-cat-b15q-rom-development-t2988774
Remove back shell from phone, remove battery (!)
Attach phone via USB. Windows should now, approx. once every 2-3s, make a sound similar as if you put in a USB stick and then pull it out again.
Start=>Run=>devmgmt.msc, in the View menu choose "Devices by connection"
Click yourself through the tree until you find an unknown device (MT65xx Preloader or similar)
Rightclick on the device and press "Install drivers"; you shall find the drivers in "MTKUsbAll_0.9.2\New inst. win 7&8x64" folder.
Launch "SP Flash Tool v5.1352.01\flash_tool.exe"
In the tab "Download", click on the "Scatter loading" button and select the downloaded file "MT6582_Android_scatter.txt". spFlashTool usually remembers this across restarts.
Unplug the phone at the computer side if you want to work with it later (the MicroUSB ports don't like too many inserts, they wear out physically).
A) ReadBack for backup of existing firmware/userdata
This will involve a ****load of typing for the first readback.
Open the scatterfile using Notepad++ or any editor capable of handling UNIX line endings, NOT notepad
You will see a lot of blocks like
Code:
- partition_index: SYS0
partition_name: PRELOADER
file_name: preloader.bin
is_download: true
type: SV5_BL_BIN
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0xC00000
region: EMMC_BOOT_1
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BOOTLOADERS
reserve: 0x00
In spFlashTool, select the "Readback" tab.
For all the blocks you see in the scatterfile (IDs 0-23), repeat the following:
Click "Add"
Double-click on the newly appeared row
Choose a filename (e.g. preloader.bin for the first block; some blocks will have name = NONE, use the partition_name here for the filename) and click SAVE
A window "Readback block start address" will appear
Choose Type = "hex". Copy (Ctrl+C,Ctrl+V, and take care to exactly select the hex value! Do NOT type the hex values by hand!) the value from linear_start_address (with the 0x) into the "Start address" box and the partition_size value in the "Length" box, press OK.
Unless you are at the SYS23 partition BMTPOOL, proceed to the next block, repeat from above.
The SYS23 partition can not be backed up, because it has invalid lengths. Do not enter it into spFlashTool.
CHECK THE VALUES FOR START ADDRESS AND LENGTH IN THE TABLE. CHECK THEM ANOTHER TIME.
Press "Read back" button at the top.
Plug in the phone with the battery removed(!) and wait. This process will take time and consume approx. 3-4GB of disk space.
Archive the files you created somewhere safe. Do NOT distribute anything to other people except the BOOTIMG, RECOVERY and ANDROID partitions, because the other partitions contain data that is hardcoded to your board (e.g. IMEI/MAC addresses, sensor calibrations,...) or your private data and app data (SYS22/USRDATA).
If you want a full backup to disassemble by hand lateron (aka you trust in nothing going wrong and don't want to do the hard work except when you need it), just create one readback section with start=0x0 and length=0xE5720000 - this backups everything in one file.
B) Download for flashing new firmware
In spFlashTool, select the "Download" tab
In the dropdown box below the scatter file, keep it at "Download only" or set it if this is not the case
Uncheck all the boxes in the table
Double click on the "Location" column of the BOOTIMG, RECOVERY, ANDROID or USRDATA rows which you want to flash, select the appropriate image file.
Check that you selected the correct images for the correct partitions!
CHECK THAT ONLY THE ROWS WHICH YOU WANT TO FLASH ARE CHECKED. ESPECIALLY, NEVER EVER CHECK THE PRELOADER, MBR AND EBR PARTITIONS. YOU HAVE BEEN WARNED.
Press Download
Plug in the phone with the battery removed and wait. spFlashTool will tell you when it's done.
Unplug phone from computer (!) and put in the battery.
If you get an error "PMT changed for the ROM; it must be downloaded", reboot your machine.
When you have a running ROM on it, you may also try to keep the battery in the phone during flashing; just press Download on the PC, then select Shutdown in the Android menu that appears after holding Power pressed. Once the phone has shut down, it will vibrate shortly and then be detected by spFlashTool. I also recommend using a high-quality USB cable and not a worn out one because USB cables with worn out plugs may lead to issues during transmission.
NAND reflush?
Excellent stuff you wrote here - thank you.
Any hints on how to resurrect dead B15Q that has damaged/erased NAND or a Preloader?
In this link http: // forum . xda-developers . com/ showthread.php?t=1943442 a forum member
claims that mt65xx have META mode even if they appear dead - like mine B15Q is right now - and could be
revived with SPFT and proper W7 drivers.
Does under those circumstances PRELOADER might be reflashed?
I read just afterwards that one should not do fully ticked Memory Test as it silently reformats NAND.
I guess this is what happened in my case.
Also, a reason to do this test was that reflashing the phone with 1.010 BOOTIMG, ANDROID and RECOVERY, having it back for a brief moment and then upgrading it via OTA to 1.019 that had bricked it in a reboot loop.
Any clue would be welcome.
uhuru-meditation said:
Excellent stuff you wrote here - thank you.
Any hints on how to resurrect dead B15Q that has damaged/erased NAND or a Preloader?
In this link http: // forum . xda-developers . com/ showthread.php?t=1943442 a forum member
claims that mt65xx have META mode even if they appear dead - like mine B15Q is right now - and could be
revived with SPFT and proper W7 drivers.
Does under those circumstances PRELOADER might be reflashed?
I read just afterwards that one should not do fully ticked Memory Test as it silently reformats NAND.
I guess this is what happened in my case.
Also, a reason to do this test was that reflashing the phone with 1.010 BOOTIMG, ANDROID and RECOVERY, having it back for a brief moment and then upgrading it via OTA to 1.019 that had bricked it in a reboot loop.
Any clue would be welcome.
Click to expand...
Click to collapse
Bigal1337's image should also contain a preloader, but I guess in your total-dead state it'd be better to send in the device for warranty... after all no one can prove what exactly zeroed out your NAND.
harddisk_wp said:
.....but I guess in your total-dead state it'd be better to send in the device for warranty... after all no one can prove what exactly zeroed out your NAND.
Click to expand...
Click to collapse
It is all OK now and B15Q is alive and works well, as it did before the "big brick" Christmas blackout.
The main thing is that thanks to MTK low-level USB communication on chipset as is in B15Q makes it "unbrickable", really.
The other thing is my bad clicking around and "checking memory" while not really knowing what I am doing.
As well as Windows x64 drivers, admin rights and all the other voodoo lurking in there.
What troubles me more is how come that CAT ppl. allowed "bricking" device upon system update, while root or no root shouldn't really matter there?
They sell it unlocked, so they should sell it, as well, with an easy option to root it. As Nexus One from Google had this "build-in" option.
I still hope that future updates will not have the same behaviour and also that there will be an alternate option for some other flavour of Android.
uhuru-meditation said:
It is all OK now and B15Q is alive and works well, as it did before the "big brick" Christmas blackout.
The main thing is that thanks to MTK low-level USB communication on chipset as is in B15Q makes it "unbrickable", really.
The other thing is my bad clicking around and "checking memory" while not really knowing what I am doing.
As well as Windows x64 drivers, admin rights and all the other voodoo lurking in there.
What troubles me more is how come that CAT ppl. allowed "bricking" device upon system update, while root or no root shouldn't really matter there?
They sell it unlocked, so they should sell it, as well, with an easy option to root it. As Nexus One from Google had this "build-in" option.
I still hope that future updates will not have the same behaviour and also that there will be an alternate option for some other flavour of Android.
Click to expand...
Click to collapse
I think I have found something... this chinese rooter apparently messed with internal symlinks, and the firmware update broke as it assumed "stock" contents...
Another reason not to trust rooters where one can't even read the description because its chinese...
harddisk_wp said:
Another reason not to trust rooters where one can't even read the description because its chinese...
Click to expand...
Click to collapse
I agree there. I gave up on rooting B15Q.
On the side note: lately I had 2 spontaneous reboots after this reflash and resurrect.
It happened after I used "official" messaging app more precisely after I send a message and close the app..
.
Did anyone noticed this? - it is 1022 I have up and running.
Other than that it works fine.
Hello,
I tried your workaround but haven't succeeded yet. And yes my phone also is bricked, unfortunately.
My phone halts where you have to choose a language after a factory reset. At that moment I get some messages that some services had stopped. Like Google keyboard, Youtube and some more. I can click OK but this doesn't get me passed these messages and they reappear. I only can switch off the phone.
I tried your workaround on a x64 machine (and got the PMT message) because that's what I have. I am preparing a x86 machine which has XP on it but on launching SP Flash Tools I get the message the configuration of the computer is not correct. Will W7 32-bits do the trick?
Also two more questions.
The downloaded images are : boot.img, recovery.img, system.img and uboot.img.
In your explanation you're mentioning : BOOTIMG, RECOVERY, ANDROID or USRDATA.
I presume that in SP Flash Tool I have to use the system.img in the row ANDROID?
Or should it be in the row USRDATA?
You don't use uboot.img. What's the reason for that? For what purpose is this image?
Update 19 april 2015.
I managed bringing back my phone to life. I did another attempt by rebooting my 64-bits computer (as you wrote in the beginning) because at that moment I didn't had a 32-bits machine. It worked wonderwell. So, I'm using my phone again. Like uhuru-meditation I give up rooting for the moment. Nevertheless Android 4.4.2 I still like this phone. Hope it won't let me down after this major reset. Keep fingers crossed.
harddisk_wp many thanks for your hard working in making this workaround. It sure has cost you more then an hour's work.
I hope you read my questions and can or will answer them.
CAT B15 help
Hi guys, i'm sorry i have to ask this in this forum but i've been asking for a couple of months now, and got no answer. I have a CAT B15 (not the B15Q). It is single sim version (IMEI write on the back) and i managed to do plenty of things in it. I swapped memory and worked fine, and even i installed a Dual Sim android rom and i managed to use the secondary Sim bay in it (that was tapped with a plastic fake sim) and used the phone with 2 sims for like 2 weeks. Then i started to play with deodex and build.prop and softbricked the phone, but it was piece of cake since it is easy to unbrick. The problem was that i wrongly flashed the phone with scatter file, and flashed all partitions in it, EBR1, MBR, UBOOT, etc, etc. The result was a non-working dual SIM phone. Everything works, but the SIMS, it does not detect any SIMs in it, in any of the SIM bays, and the IMEIs are wrong numbered. I did no buckup of the phone so i'm pretty screwed. I've been asking for someone to upload the EMEA_SS or US_SS ROM for the CAT B15, but nobody responded. I thaught maybe the CAT B15Q has a similar software/bands flashing partitions, but that i leave to you for answer. Anyway, if any of you has the possibility of taking the images of a single sim CAT B15 it would save me this awesome phone for me. I'm also willing to give a 20GB account of ownCloud server for 1-year free of charge if storage space is needed, no problem. This are the links i've been searching and asking.
All About CAT B15: http://forum.xda-developers.com/show....php?t=2430904
Root for Catterpillar B15: http://forum.xda-developers.com/show....php?t=2263455
Best regards,
2 Questions
Good day
I have the same questions as a previous user, but I cannot find any answer to it:
"Also two more questions.
The downloaded images are : boot.img, recovery.img, system.img and uboot.img.
In your explanation you're mentioning : BOOTIMG, RECOVERY, ANDROID or USRDATA.
I presume that in SP Flash Tool I have to use the system.img in the row ANDROID?
Or should it be in the row USRDATA?
You don't use uboot.img. What's the reason for that? For what purpose is this image?"
Could you please help with these? Should I use uboot.img as well? And does system.img go to the Android row?
I added this 3d question later: is it safe to flash SS phone with the DS file?
Kind regards
"PMT changed for the ROM" and SP Flash Tool version
Hello,
I'd like to say big thanks and report that my B15Q was saved thanks to this thread, after a failed upgrade to the 1.016.00 firmware (due to the Chinese root app).
Moreover, I would like to point out that the procedure worked only with the v5.1352.01 version of SP Flash Tool. All other versions I've tried bailed out with the "PMT changed for the ROM; it must be downloaded" message. Unfortunately, the thread which is listed in the instructions refers to a version of SP Flash Tool more recent than v5.1352.01. A link to the said version can be found in this post: http://forum.xda-developers.com/showpost.php?p=58810386&postcount=4
Regards,
Aurél
harddisk_wp said:
0) Driver and toolkit setup
Get the driver set, scatter file and spFlashTool from this thread: http://forum.xda-developers.com/general/general/stock-rom-cat-b15q-rom-development-t2988774
Remove back shell from phone, remove battery (!)
Attach phone via USB. Windows should now, approx. once every 2-3s, make a sound similar as if you put in a USB stick and then pull it out again.
Start=>Run=>devmgmt.msc, in the View menu choose "Devices by connection"
Click yourself through the tree until you find an unknown device (MT65xx Preloader or similar)
Rightclick on the device and press "Install drivers"; you shall find the drivers in "MTKUsbAll_0.9.2\New inst. win 7&8x64" folder.
Launch "SP Flash Tool v5.1352.01\flash_tool.exe"
...
...
If you get an error "PMT changed for the ROM; it must be downloaded", reboot your machine.
Click to expand...
Click to collapse
my b15 loopboot
Hello such greetings from Venezuela have a cat b15q dual sim to load the firmware with sp flashtool v3 makes the whole process but remains frozen on the logo even doing a wipe and there no moves have the rom that is posted here I can I am doing wrong excuse my English but I use a translator
Thanks on advanced . Worked fine on my b15q cat . Really much apreciated .
Hello, I'd like to say big thanks and report that my B15Q was saved thanks .Thanks this rom launch perfect
uhuru-meditation said:
It is all OK now and B15Q is alive and works well, as it did before the "big brick" Christmas blackout.
The main thing is that thanks to MTK low-level USB communication on chipset as is in B15Q makes it "unbrickable", really.
...
Click to expand...
Click to collapse
Would you please care to share how you achieved that?
(Following some guide which said that upon ""PMT changed for the ROM..." error one should format the device before downloading, we did that (after reading back everything) but unfortunately, spFlashTool doesn't like the readback PRELOADER partition we extracted.)
goodnight I hope will help me have a cat b15q and remained in recovery mode and I need to flash it revive hope help me thank you .. I'm from Venezuela and one who does not get that software. Excuse my English but q use the translator
CAT B15Q - My Rear Camera doesn't work anymore
Good evening everyone.
After a bad update, my rear camera on CAT B15Q doesn't work anymore. I read all the posts here and I'm using Windows Vista Home Premium 32 bits. I downloaded all the necessary files and when I open the SP Flash Tool, I think it didn't recognize my smartphone and when I try to download any file to the phone the status bar on SPFT still stopped, like if anything is going on. I buy this B15Q on Paraguay. Could this fact be my problem? Anyone could help me, please???
So I got a cheap android tablet and I wanted to root it. I was successful so I decided to install TWRP. I searched for my specific model and found an image on a german forum. I downloaded and flashed it and it got stuck in a reboot loop. So I looked at the image and it was for the QV1030. I tried to get it into recovery but couldn't. Many sources told me to hold Vol Up and Lock, and I tried this and more. Nothing would make it enter recovery mode. Then I read about SP Flash Tool and found the stock rom for the tablet and decided I would try to flash that. It kept coming up with an error, and every source online told me to format the flash except for the bootloader and then I could flash it. So I did. Now it doesn't show anything on screen, and SP Flash Tool comes up with error 6045. But it does show up in device manager under com ports as, "MediaTek USB Port" so I think I can still do something about it. I don't have any backups. I don't know what I'm doing. I require assistance please.
So I reflashed the entire backup and it come up with no error. The logo comes up and it plays the chime. The logo does this little shimmer effect and once it gets to this screen, it shimmers indefinitely. If I plug it in, it begins installing a driver and then stops part way through.
drsinclair said:
So I reflashed the entire backup and it come up with no error. The logo comes up and it plays the chime. The logo does this little shimmer effect and once it gets to this screen, it shimmers indefinitely. If I plug it in, it begins installing a driver and then stops part way through.
Click to expand...
Click to collapse
I left it for about 5 minutes and it finished the driver. I thought it froze but I was wrong. It shows up now on device manager under Portable Devices as, "MTP USB Device". I tried to see if it was listed as a device by ADB. It is not. Lets just say I've already learned a thing or two about this stuff. Good thing I did it on an 80 dollar chinese tablet and not my HTC One M9
drsinclair said:
I left it for about 5 minutes and it finished the driver. I thought it froze but I was wrong. It shows up now on device manager under Portable Devices as, "MTP USB Device". I tried to see if it was listed as a device by ADB. It is not. Lets just say I've already learned a thing or two about this stuff. Good thing I did it on an 80 dollar chinese tablet and not my HTC One M9
Click to expand...
Click to collapse
I got it to work again mostly. So I realized that I wasn't flashing the whole backup. Some things didn't have a path and I had to set it manualy. Now it has CFW for some reason, but I reset it and it works now. The only thing is WiFi is not turning on. Any ideas about that?
drsinclair said:
I got it to work again mostly. So I realized that I wasn't flashing the whole backup. Some things didn't have a path and I had to set it manualy. Now it has CFW for some reason, but I reset it and it works now. The only thing is WiFi is not turning on. Any ideas about that?
Click to expand...
Click to collapse
I actually want to upgrade this from Android 4.2.2 to a more recent version. Do you guys have any ideas about that?
So I've come to the conclusion that while the device is no longer bricked, the current installation is written over the old one and things are conflicting. I know this because I looked through the cache and found filenames referring to apps I had installed before breaking it. So would the solution be to wipe the system partition and reflash the system.img so everything is fresh? Or does the problem lie elsewhere.
I formated the system partition, used SP Flasher to flash system.img and then did a factory reset. The issue has still not been solved. And now that I have done that, I don't have root access anymore. Framaroot says it was successful and I restart and check root explorer on ES File Explorer and it doesn't work.
I gained root access using a different method. However the WiFi still doesn't work. I think it may be that the mac address information was from the backup I flashed from the internet, and therefore doesn't match. I found a guide that tells me how to hex edit a file and put in my real mac address, but it's unavailable under wifi. I don't have the sticker on the back that says it either. How else can I find it?
Turns out the mac address can be anything. I used SN Write tool and an AB DB for my chipset and it still didn't solve the problem. I have no idea what to do. Can anyone help me?
I fixed the issue by grabbing a different backup from some russian website and flashing the system.img and secro.img to it. It now works fine 100%. Thanks
help - link
drsinclair said:
I fixed the issue by grabbing a different backup from some russian website and flashing the system.img and secro.img to it. It now works fine 100%. Thanks
Click to expand...
Click to collapse
Hey man! I have the same problems with my QV 830. Can you give me the link for system.img and secro.img, please?
Hello,
A friend of friend of mine unlocked bootloader on his G5, then some magical stuff probably happened, because secure boot got stuck on boot verification failrue with probably most common issue, signature length mismatch. We're trying to get it to work now, but we can't seem to find a solution to it. Fastboot doesn't work, because secure boot gets tripped in every bootmode. Does anybody have an idea which pins to short out on motherboard for boarddiag operation or something? I'd really appreciate that.
Download Mode should still work.. even with the secure boot tripped msg.. as long as they didn't mess with the download mode partition on purpose before this all happened.
The unique programmers required for the G5 for BoardDiag to work are not public so forcing your way into 9008 won't get you anywhere.
He isn't able to fire up download mode either. He says that it prints different_hash error there. I'd probably have to take another one of the same model(H850, I believe) and mirror kernel and bootloader from it, but I don't have eMMC programmer, nor physical access to that phone.
[/COLOR]
autoprime said:
Download Mode should still work.. even with the secure boot tripped msg.. as long as they didn't mess with the download mode partition on purpose before this all happened.
The unique programmers required for the G5 for BoardDiag to work are not public so forcing your way into 9008 won't get you anywhere.
Click to expand...
Click to collapse
Keij0 said:
He isn't able to fire up download mode either. He says that it prints different_hash error there. I'd probably have to take another one of the same model(H850, I believe) and mirror kernel and bootloader from it, but I don't have eMMC programmer, nor physical access to that phone.
Click to expand...
Click to collapse
Keij0 said:
He isn't able to fire up download mode either. He says that it prints different_hash error there. I'd probably have to take another one of the same model(H850, I believe) and mirror kernel and bootloader from it, but I don't have eMMC programmer, nor physical access to that phone.
Click to expand...
Click to collapse
bumping old thread, i know. Did we ever establish either board diag files for g5 or any solution to No download mode issue with it reporting Different Hash when attempting to enter it? My phone boots fine but no DL mode......backstory: I have a RS988 that i attempted to repair for a friend after they locked it with frp, i removed the frp, via creating a apparently incorrectly modified firmware via my z3x's firmware maker feature(it copies the partitions available on the device into a new firmware file). it doesn't have rs988 listed as a model available to edit so(like normally works with devices, i used vs986(or whatever verizon's variation was, i know rookie mistake) but I believe i have screwed up because since writing the modified firmware i can get into the OS fine but can not enter DL mode again without the "Different Hash" issue. I believe shortwire plus board diag fix could be resolution but could use some feed back . @autoprime Anything i can do to rewrite those partitions manually with the RS988 variant's original kdz and any type of serial connection/jtag/virtual com ports/tty/AT+/linux computer, lol anything? I'm pretty much equipped for anything except jtag but even that can be arranged lol
Hi
I just got a third LMX210 today to add to my collection. Lol really im just trying to solve a problem. I bought a ulma to replace cm and i came across a ulm model and decided to just replace my cm today. The problem is that all three of these phone which normally have easily unlockable bootloaders will not boot into fastboot. The fortune 2 will not even boot into recovery. They all will boot into a blank screen with the android robot and will boot into download mode.
The natural solution would be to install an older or even plain stock firmware. But say you dont have a windows 10 or Mac computer. I havent found a way to flash lg firmware using a linux distribution yet.
On the other phones i tried removing the laff partition to force the phone into fastboot by plugging into pc while holding the volume up button. This did nothing but repeat the logo until the button released.
Yes usb debugging was enabled and adb was used to try these procedures. The drones at lg know nothing and ask to send the phones in for repair.
Short of re-installing the stock firmware there has to be way to get past this. And to tell you the truth i dont have a way to flash the stock firmware so i dont even know if that will work.
Ok guys got any ideas?
Update.
Ok spent 4 hours on a windows pc today trying to flash firmware and install qcom drivers thinking the download errors were due to the drivers. Then at the last moments went to Tecknights page and downloaded and installed the lgup dual mode program.
So the bastitches of higher android office decided to screw everyone out of bootloader unlocking. The ARB numbers have recently (like in the past 3 months) been changed to 003. Meaning you cannot flash firmware with an ARB number lower than 003.
But that doesnt stop us completely. Two ideas initially popped into my head. Hex edit the .kdz so that the ARB number matches the phone. Or lol split the .kdz into its seperate partition images then wipe the partitions and use qdl or lgup to repair the now bricked phone. No device data no ARB no problem.
Im hoping the former works over the latter but ill keep you informed.
But really guys thats extreme and i cant see too many folks going through the wipe process to enable fastboot. So we have to find an easier way.
Is there any way to know what partition the ARB protection resides in? If those parts could be wiped im thinking it might fool the flashtool into thinking that there isnt any protection.
one of your devices is MTK isn't it? can't you use SP Flash Tool like for other Mediatek devices? you should be able to flash images to emmc_user with locked bootloader, for example boot, recovery, system, ... all you need is a correct scatter file (which you could create with WwR MTK)
So your saying finish porting my recovery and use sp flash tools to install it. See i have been curious about that procedure and how not having an unlocked bootloader would effect flAshing from recovery. I was thinking brick. But its worth a try if it wont brick and i get full Root with magisk. Ty
Btw when i was porting my recovery i ran into a rather large well too large problem. When i went repack using abdroid image studio which i have used in the past with out problem, it would not shrink the image back down even though i was only trading a few files. How do i fix that
start with readback boot / recovery. then try to unpack, so you will know the scatter is right (at least, for this partitions) or compare files with your already existing backup files
no problems here with unpacking/ repacking with AIK
IDEA:::: ok so for the Qcom boards i have a solution possibly. I know that the older software versions have working fastboot and recovery going and can be boot loader unlocked. That tells me that a fota uodate is screwing things up.
PROBLEM:::: ARB my fortune 2 will not let me install at all anything before ARB3.
ARB_location:::: bootloader
Solution:::: download and extract the stock .kdz for device with working features. Wipe parts bootloader and laf using qpst and reinstall. Solves two problems in one go. Allows fastboot and and bootloader unlock and future re-install of stock firmware
may work but remember your bootloader is locked and you need to by-pass this via testpoint (or at least previously enabled oem unlocking and don't lost these setting) otherwise sahara will fail
well it was an idea. I just did some fact checking and also looked at the files dumped from the .dz dump of the fortune 2 stock rom. PBL or primary bootloader cannot be removed or flashed according to a thread it is a pernanent installation.
But upon more reading i can flash my recovery and boot.img using qfil in qpst along witn every thing else. But i need to know wether qfil reads ARB info and if so where i can find it in the firmware so i dont flash that img but instead pull it from phone as is.
i would really like to know what the twitterpating deal is with these LMX210 phones. ok when i firsr got my fortune 2 i bought it for two reasons the rootability of the device and the fact that tje msm8937 board came pre-installed with otg software by default which in my eyes meant no more freaking computer to use adb.
Well it is all there the drivers the software. but guess what. it doesnt work. i have no idea whats stopping it all from working but even lsusb doesnt bring a twitch or hint of reading any thing over the usb.
does any one know how to fix this
Yo. There is definitely ways to flash on linux using virtual machines, wine etc to run windows apps but you got ahold of a windows box to use. IF it is in EDL mode (Qualcomm mode with a driver saying 9008 in it..) then there is still faith you can revive it. You will need the firmware dumped from someone then youll need to run a program creating XML files for the phones firmware parition files. Youll next need a firehose which is what they call the programmers for EDL that send through the commands and firmware in a low low level that these programs like LGUP just do not do yet (don't know why..... Im waiting for someone to program the LGUP dev version with an EDL mode using emmcdl along with a way to create XML files too. Who knows maybe it will happen if we bring it up enough. The hardest problem youll have is getting a proper emmc programmer for the phone. I can source a lot so if teknight doesnt have something to help with EDL just get ahold of me and ill see what I have and send you some stuff.
Man i have been trying to unbrick the LMX-210 CV1 devices since last year. Tek has nothing but supports the work in hope of finding a solution. I have a ton of fire hoses and saharas all of which have cost me nothing but frustration. I have almost every qpst made and have tried them all with my firehose and saharas. Thr only thing i havent done is pull the mbns off my phones and try them. Trust me system dumps are crap.
The only sign of life i came by was flashing an sd card with the gpt and then flashing each partition manually using ubuntu. In return i got the battery logo but thats it.
Would love to figure it out though
By the way I have been compiling kernels. I call it the jokerfish kernel. Its packed full of drivers and debugging features plus gpu idlers boosters and all those crazy fishy thIngs. Its got governors and wire guard. Otg support. Io schedulars and overclocks. Cpu hotplugging and fast charge.
Now i cant figure out how to get fast charge to work but its set up for msm-otg phy-msm-otg qpnp-smbcharger and smb135x.
All that and not a single panic to reboot in over a week and 1/2 which is how long its been compiled. I used tweaks from the dragonheart kernel source and ported them over and did a lil c++ magic.
It has kcal too but n0 app supports it. All kinds of media and sound codecs as well. You think it would be slow but my compiling and coding skills are as mad as me. Hahahaha.'
But dont Take my word for as the gentle over there on your couch. See that smile? Hes as happy as fish in a pond.
Just remember Duhjoker is in no way responsible for bricked devices so try it at the risk to yourself.
This particular fishy thingy works for msm8917 cv1 devices like aristo 2 and k8+ which have been tested by the madman himself.
If you like you could thank me but the permanent smiles on your faces will be just as loved.
lol so fast_charge is working on the kernel but you have to add a custom tunable to a kernel app to get it going. Just add the path
/sys/class/power_supply/usb/uevent
Then you will get a choice of values to manipulate
hi
the other day i tried to dd in a bootloader to add fastboot to my K8+ (2018) LMX210ULMA and wiped my preloader. The device uses an mt6750 chipset and i had made a back up so i have the approriate software to restore it, i even have the scatter file.
The problem is that there is no da_pl.bin file for lg phones to use sp flashtool, i have no download mode and no fastboot.
i have two pc`s one running ubuntu the other windows 7.
i would appreciate any help
any help at all
ok so ive found some versions of sp flash tool that are supposed to get around the authorization stuff and i have an auth file but i keep getting brom errors. the same one in fact. on linux ifs 0x00. ive been looking at and following the tutorials ivs made android rules and all kinds of things but i cant get it to flash. it started to befote i added the stuff in the tutorials. The red line would go acrross the bottom but now i just get the brom errots.
Thumb up for boldness... :good:
Now you have some interesting project there.
Keep us update if you manage to find out any solution.
No idea how to help but Good luck!
https://blog.hovatek.com/so-whats-all-this-talk-about-meditek-secure-boot-and-da-files/
https://ifindhub.com/download-mtk-secure-boot-da-loader-files-mtk-devices.html
ill get there eventually. I have been looking at all the config and ini files and i hate to say it but security might be essier than you think to overcome. just have to erase a few lines here and there and teplace some as needed. idk ty. Dont worry ill keep you guys posted
i really think sometime we over think and see past the easiest solutions. but what do i know im trying to flash an mtk preloader on an lg phone.
im actually trying to unbrick a few phones. two qc `s and the mtk. I kinda bricked one of my lmx210`s on purpose not thinking it would brick. well jokes on me.
Im have a couple questions maybe somebody can help with. In the past couple months on my journey through madness i have tried a few hindred different ways and more flashtools than you could imagine. So far nothing has worked but ive learned alot of theory.
so far though i know that the mtk board is in bootrom mode. We will get back to that as i have an idea....
ok on the qc boards we have the dreaded 9008 mode. I made some progress today. i wanted to see if the LMX210 could boot from SD card instead of the internal. I believe it can but im having trouble with what to do next. p
i used dd to flash the gpt on my sdcard then formatted the partitions to the proper filesystem. when i plugged it in to the usb it lit up but did not boot. But it lit up for the first time since bricking.
But it only lights up with usb plugged in. Add the batrery and it goes dead. It also doesnt show 9008 mode any more.
i went back and changed the boot and recovery images to reflect using the mmcblk system and now windows device manager can see it. But no boot. im wondering first if i might need a special boot loader to boit from sd and two if i might be able to use the same trick to get the mtk running
Some LG firmwares include some files for SPFT, like LGX240ARAT and LGX230HAT.
but do they work with MT6750? In LGX240ARAT there is a dll that mentions MT6755,
but not MT6750. Newer versions probably needed. Or maybe you could hack it. ??...
part of my problem is not knowing what scatter file to use. these phones have thier info all twaktup. the mtk gives several different board/chip types. like we have 6722, 6755, 6750, 6736 and so on. im pretty sure though its a 6750 board with 6755 chipset but do i use the scatter for the board or the chipset.
Ok idea!!
I can pick the phone up as bootrom mode on port in my ubuntu as /dev/ttyACM0.
That means i can write to it. How can i dd the preloader.bin to the right place on there
Duhjoker said:
Ok idea!!
I can pick the phone up as bootrom mode on port in my ubuntu as /dev/ttyACM0.
That means i can write to it. How can i dd the preloader.bin to the right place on there
Click to expand...
Click to collapse
As I don't know much about but have played a bit with these.
https://gitlab.com/zeroepoch/aftv2-tools
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
And there is tools like eMMC Pro, etc. that might work too... ?
I think the m250 did answer to some handshake but there was some problems
because I didn't continue testing those py scripts...
I would try what I could read from it first. From those scatter files I guess that
preloader is on its own partition. The other one should start with partition table, pgpt .. ??
CXZa said:
As I don't know much about but have played a bit with these.
https://gitlab.com/zeroepoch/aftv2-tools
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
And there is tools like eMMC Pro, etc. that might work too... ?
I think the m250 did answer to some handshake but there was some problems
because I didn't continue testing those py scripts...
I would try what I could read from it first. From those scatter files I guess that
preloader is on its own partition. The other one should start with partition table, pgpt .. ??
Click to expand...
Click to collapse
Hi,
If you can reach bootROM mode by pressing any of the volume keys while you connect the phone (Mediatek Inc. MT6627) you should be able write and read the EMMC with amonet.
The tool needs some modifications in order to make it work to MT6750. You can probably try with the mt6753 version which may work for MT6750:
https://github.com/Dinolek/amonet
For reference, use this commit:
https://github.com/R0rt1z2/amonet/commit/6b57d0a99f42739d3b3b2ce962b32ecb8fefd950
Contains all the stuff that needs to be edited in order to make it work for that phone
Regards!
Thank you i can give it a try. Its already in bootrom mode though and accepts the handshake. The problem is that the py command that flashes the preloader and stuff on it also wants to flash other stuff as well that i dont have or does not work with the board.
The py command needs to be modified to only flash the preloader, lk.bin, laf and twrp. If those items only could be flashed i could bring the rest of the device up using lgup
I have tried to modify the commands myself to include just those items but it errors. I dont know enough about the python language to be able to do it on my own.
Duhjoker said:
Thank you i can give it a try. Its already in bootrom mode though and accepts the handshake. The problem is that the py command that flashes the preloader and stuff on it also wants to flash other stuff as well that i dont have or does not work with the board.
The py command needs to be modified to only flash the preloader, lk.bin, laf and twrp. If those items only could be flashed i could bring the rest of the device up using lgup
I have tried to modify the commands myself to include just those items but it errors. I dont know enough about the python language to be able to do it on my own.
Click to expand...
Click to collapse
PM me if you need help editing the python script
Regards.
I really appreciate your offer for help. I was looking at the reference for porting and now that i can see the things that would need changing why not go ahead and unlock the bootloader while we are at it. We could save a ton of devices and at the same time give them th3 extra value of being able to twrp and root them.
I have been looking for some way to unLock the bootloader on these phones for days and though it will be some work being able to reflash the preloader AND unlock the bootloader which was my main intent when i bricked it would be worth the extra effort.
Rortiz2 said:
PM me if you need help editing the python script
Regards.
Click to expand...
Click to collapse
I couldnt post the main.py script in the pm but i can attach it here. Thank you so much.
Here is the raw preloader extracted using salt on my pc.
Ok so i went through your source code for the meizu m2 amonet to match it with source code for the mt6750 and i only had to change a couple things. Its pretty much identical to the commit you pointed me too.
As far as i can see your amonet should work just fine with the sp200/lm-x210ulma boards. I did add my .img files to the bin folder though.
Any way i keep getting errors.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 501, in read
'device reports readiness to read but returned no data '
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
During handling of the above exception, another exception occurred:
Rortiz2 said:
Hi,
Contains all the stuff that needs to be edited in order to make it work for that phone
Regards!
Click to expand...
Click to collapse
Hi,
Didn't continue experiments but now also @Duhjoker might be interested about this last new development...
[EXPLOIT] [BOOTLOADER] Mediatek based LG K10 2017 M250 bootloader secure boot bypass. by @OficerX
https://forum.xda-developers.com/lg-k10/how-to/exploit-mediatek-based-lg-k10-2017-m250-t4183545
MT6755 and MT6750 are essentially the same, MT6750 is cheaper and slower version of MT6755, these are compatible, you can use tools for 6755 on 6750.
Here (https://github.com/arturkow2000/lgk10exploit) you have tools that can help you flash preloader (write_boot0.py), these should work on your device.
Open config.py set BR_DEV_PATH to /dev/ttyACM0
then write: python write_boot0.py --brom path_to_your_preloader_bin
This is slow process, may take few minutes (you will see progress while flashing).