Hello
Basically, I have a device which was sim unlocked from factory. I decided to mess with custom ROMs, realised they were not as good as stock, so I reflashed the stock ROM using MSMDownloadTool, which worked fine until recently when my IMEI number vanished somehow, and now my phone has locked the bootloader, doesn't allow me to open it, no SIM card works, WiFi keeps dropping
I tried several things, reflashing, resetting, nothing works.
Basically, what I've realised is that the only way I can flash anything in the phone is via edl, which works only with MSMDownloadTool which only allows you to flash the stock ROM again, with the stock recovery and stock boot.
So now I've been playing around with .ops files, extracting them, and messing with the settings.xml file, to see if I can get TWRP or magisk to install via MSMDownloadTool.
So Far, here's all that I've gathered,
</program>
-<program multiImage="false" start_sector="185018" start_byte_hex="0x2d2ba000" size_in_KB="102400.0" readbackverify="false" physical_partition_number="4" partofsingleimage="false" num_partition_sectors="25600" label="recovery_a" file_sector_offset="0" SECTOR_SIZE_IN_BYTES="4096">
<Image SizeInByteInSrc="104857600" SizeInSectorInSrc="204800" FileOffsetInSrc="11569702" readbackverify="true" Sha256="11af9924c25347226a644b702ca0b6dac540f9b034804349c72948a63db0a4dd" ID="0" sparse="" filename="recovery.img"/>
</program>
This is the bit of the .xml file that involves installing the recovery.img
I realize I have to change the size_in_KB, SizeInSectorInSrc , SizeInByteInSrc, and I'm assuming remove the Sh256 as the file is different, change the num_partition_sectors as the file size is different. However, if I change the num_partition_sectors, then I'd have to change it in every other bit of the .xml file too.
Would this then work, or do I need to do more? I would appreciate any help from anyone else who is interested
Thanks
Related
I have the LG v10 from T-Mobile. I bought the phone a few weeks ago and it had Marshmallow installed. Somehow I managed to install TWRP/SuperSU, but then had issues and flashed the official/stock MM image with LGUP. Afterwards I discovered that MM for this device is not currently rootable, and TWRP cant be flashed via fastboot because MM blocks it. So I returned the device to T-Mo store, lied and said it force-upgrade to MM and had began freezing up. They did an in-store trade for an identical model that had 5.1.1 Lollipop.
The device is currently still in factory condition in every way, with the exceptions that I unlocked the bootloader via fastboot and installed TWRP. Nothing else is modified yet and no custom ROMs have been flashed.
I recently became aware that there is no stock LP image for the T-Mo v10, only MM images are available. After all the issues I've had, I'm now paranoid and want to have a complete dump of the phone's entire contents (partitions, bootloader, system, etc) that is in KDZ or TOT format, and can be reflashed with the standard tools available. Since there is nothing official then I would have to do this myself. This would be useful in the event that I run into lots of issues and need to do a emergency stock restore.
I found a thread by XDA user @tungkick, in which he created a modified dump of the device while it was running LP. However, because it was unofficial and he didn't disclose this upfront, his thread was shut down. His file bricked multiple MM users. I assume it would work if one was still on LP and hadn't upgraded to MM. Not to mention that I cant seem to find his file anywhere. So I figure the safest way is to do this myself. I would be willing to make this file available to the community when finished, with full disclosure that it is unofficial. But the problem is, I don't know how.
I know that the Linux dd command can be used to dump images of various things, and I have read that this can be done on PC by connecting to the device via ADB or fastboot. This would hopefully result in an image file that contained the contents of all the device's partitions.
But another issue would be converting it to KDZ or TOT. And it would have to be done in such a way that it would be flashable with the standard tools.
Can someone please give me a technical understanding of the tools and knowledge I would need to undertake this? Would it be too complicated for someone like myself that has little Android/Linux experience (but is generally competent with computers/technology)?
Thanks for any advice!
Noone can help me with this?
To the mods/admins: I think maybe I posted this in an area where it is unlikely to get any useful answers. Can someone move the thread to the Help& Troubleshooting area of the general LG v10 forum (not here in the T-Mobile subforum)? Thanks!
I think it's just that if that could. have been done someone would have done it already. Even tungkick didn't make one for tmobile for some reason. I think because he made his root injected files from official lg files and lg has not released a kdz or tot for tmobile LP.
Just my observation... I could be wrong.
Sent from my pretty nifty brand new LG V10
@ planetbeen: I don't see why it wouldn't be possible. Linux's dd program can dump almost any connected device that it can see. But then it needs to be converted into a standard TOT/KDZ that can be flashed with any standard software. Which is why I want to create an unofficial backup of the entire phone before modifying it further, so I can do an emergency restore if necessary. I just need the right instructions from people who have the technical expertise.
I had trouble with my old LG v10, I had used LG's LGUP program to flash it to Marshmallow from my PC, only to realize that it couldn't be rooted or have a custom recovery. And I also discovered that I couldn't downgrade to Lollipop. So I returned the phone to the store and exchanged it for an identical model that still had LP. I just told them it had auto-upgraded to MM and started crashing. They exchanged, no questions. Before this I had various issues, like GPS crashing randomly when turning it on, Bluetooth also doing the same thing, and the Settings app also crashed sometimes when accessing the Security menu. I had flashed multiple ROMs, but stock-based and CM/AOSP-based, but kept running into issues, oftentimes the same ones. So I figured that something in the phone had become corrupt and figured that flashing stock MM would fix everything. Big mistake. I'll never let this phone upgrade again until MM is solidly hacked, which from what I've read may be a long time away. I paid enough for this phone and I really value hackability. I'm not the average Joe that just uses my phone for Facebook, etc. To me, if a phone cant be hacked, then buying/owning it is a waste of time/money. Same thing with every computer/electronics device I've ever owned.
Thanks again!
It looks like I'm going to have problems getting answers from knowledgable people, so instead of waiting, I'm going to take a little initiative and at least try to do the dump with dd. I found a post by @tungkick that says to enable USB debugging and make a backup file via dd with the 'adb shell' and 'su' commands. Is the following syntax correct?
dd if=/dev/block/mmcblk0 of=/sdcard/H901.bin bs=1024 count=6291456
Do I run these commands from a PC via command line while connected via USB? Or directly on the device in a terminal emulator? Or do I need to run the command while in fastboot/bootloader mode, while Android is powered down?
Thanks again!
Stock use tool extract kdz then choose file dz (use lgup)
remember can not flash if phone update 6.0
Never downgrade because phone brick now.
version 5.1.1
https://drive.google.com/file/d/0B_Hol5T47S-bQkJVemgzMDV0Nzg/view?usp=sharing
@ tungkick: Thanks for the info. I had used the dd command to dump my phone to external SD before, but the file was 6GB! I was unable to use Tool KDZ Extract to extract the *.dz from the *.kdz file you provided. I was able to flash your KDZ with LGUP, but it boots me into TWRP recovery near the end.
Do you mind if I publicly distribute a mirror copy of your file on my Dropbox, so that it will be available to others that need the stock LP firmware for this device?
Thanks again!
I just wanted to say that flashing your KDZ has possibly screwed up my device permanently. Your image has TWRP, not the stock recovery, and is pre-rooted with SuperSU. Normally this would be good but...............
Near the end of LGUP, the device boots into TWRP. System and MicroSD are mounted, but nothing else (data, cache, dalvik, etc). I was able to obtain a stock recovery *.img, then copied it over to my MicroSD while in recovery. Then I flashed it, booted the phone into stock recovery, and performed a factory reset. Afterwards I booted into system, and all looked good, until it got to the "Checking connection" screen, then a lot of apps started force-closing repeatedly. Because of this I can't get to the Home screen, and no amount of factory reset is working. It just keeps happening over and over again.
How to get out of this mess, anyone?
Help please!!!
Still looking for a solution and would really appreciate any help!
My theory is that the /cache and /data partitions somehow got corrupted during the flash. So I tried booting into FastBoot mode and issueing the commands:
fastboot erase cache
fastboot format cache
fastboot erase userdata
fastboot format userdata
It just says something something along the lines of "remote: cant format/erase in an unlocked state". If I relock the bootloader, it says that it cant erase/format in a locked state.
TWRP still cant read those partitions (they won't mount and cant be mounted), and the apps still start force-closing almost immediately after rebooting into system, before I can complete the setup, preventing me from getting to the home screen.
@ tungkick: Is there any possibility we can arrange a TeamViewer meeting to fix this?
Thanks!
OK, I'm at my limit here. I've been tampering with this phone a lot of time, I have it since 2016. Right now I'm not using it but I wanna give it away as a gift. The thing is, when I turned it on, it didn't detect the SIM card, so I wanted to flash the Stock Rom back to see what would happen. I did that, same deal.
So now the phone boots up, but I have no way of making calls, receiveing messages, etc.
Here's the list of things that I did:
Unlocked Bootloader
Rooted (right now I'm unrooted)
Installed TWRP 3.0.2.0 recovery.
Flashed all kinds of new custom ROMs
Installed Stock ROM via EMUI microSD (dload folder method)
Installed an unpacked Stock ROM (UPDATE.APP) via fastboot
I hope I can fix it somehow, I've tried installing other ROMs, taking out the SIM card and testing other ones, testing different versions of TWRP, ADB sideloading, blahblahblah. Any help is appreciated, as every thread that I find about this phone is extremely outdated and most links are down.
PD: Phone is a Huawei y6 SCL-l03 from Argentina, I use it with Telefonica, Personal company.
If it helps: when I tried to manually install the UPDATE.APP from the stock ROM via fastboot, the "CUST.IMG" failed to "write". I heard it has to do something with the kernel, I have absolutely no idea. OS worked anyways, just in case I reinstalled everything through EMUI.
Hello,
I was installing different custom ROMS for this phone, then reverted back to Stock ROM. It updated itself, and IMEI got erased somehow.
Is there any way possible to flash a custom ROM, or even custom recovery using MSMDownloadTool? I had a global version N10, so it was sim unlocked and bootloader unlockable, and I do actually have my IMEI on the back of my box, but can't put it into my phone as I have to root it. But I can't root it because the bootloader is now locked, and the bootloader is now locked because there is no IMEI......
This leaves me locked out of fastboot, so the only option is edl, which works just fine. However, only MSMDownloadTool is compatible with this mode, and it only installs Stock ROMs.
I tried extracting the .OPS files, replacing the stock recovery with twrp (and then renaming it to recovery.img), repacking the .ops then installing it. It installs, but then never boots and is just stuck in edl mode until I reflash the normal stock rom with the stock recovery.
What Do I do?
Thanks
CrustyBurger33 said:
Hello,
I was installing different custom ROMS for this phone, then reverted back to Stock ROM. It updated itself, and IMEI got erased somehow.
Is there any way possible to flash a custom ROM, or even custom recovery using MSMDownloadTool? I had a global version N10, so it was sim unlocked and bootloader unlockable, and I do actually have my IMEI on the back of my box, but can't put it into my phone as I have to root it. But I can't root it because the bootloader is now locked, and the bootloader is now locked because there is no IMEI......
This leaves me locked out of fastboot, so the only option is edl, which works just fine. However, only MSMDownloadTool is compatible with this mode, and it only installs Stock ROMs.
I tried extracting the .OPS files, replacing the stock recovery with twrp (and then renaming it to recovery.img), repacking the .ops then installing it. It installs, but then never boots and is just stuck in edl mode until I reflash the normal stock rom with the stock recovery.
What Do I do?
Thanks
Click to expand...
Click to collapse
If your bootloader was relocked, encryption and partition checking were enabled again.
TWRP would only cause your phone to register as modified and lock itself...and due to streamlining of a lot of functions, you can't even use the dialer to enter the menu needed.
Best you can do is totally wipe everything on your phone and generate a new android ID. (You have to do this from the actual OS instead of recovery though. Recovery format uses predetermined instructions. The format option from the android settings panel has a different set of instructions and one of them is to generate a new android ID, which includes IMEI)
Thanks for the reply, although im kinda confused by your answer. How do I generate a new android ID? (what does that even mean lol). I checked in my settings and I can't find any "format option"
CrustyBurger33 said:
Thanks for the reply, although im kinda confused by your answer. How do I generate a new android ID? (what does that even mean lol). I checked in my settings and I can't find any "format option"
Click to expand...
Click to collapse
Android ID is what determines your phone is the phone it claims to be when pinging google services.
Move any files you want to keep to somewhere safe. Format your phone, android will push you a new id number. It won't fix your IMEI, but it'll keep your phone from being absolutely useless in the process.
After your phone is formated and has booted back into the OS, you can enable adb. Adb into fastboot, use fastboot to determine if your device is still bootloader unlocked using the fastboot oem device-info command
ninjasinabag said:
After your phone is formated and has booted back into the OS, you can enable adb. Adb into fastboot, use fastboot to determine if your device is still bootloader unlocked using the fastboot oem device-info command
Click to expand...
Click to collapse
I tried everything you said, reset everything, still no IMEI, and even if the Android ID is different it hasn't really changed anything. Just to be clear, when I flashed the stock ROM earlier, everything worked as intended apart from the SIM card (which doesnt work at all) and the WiFi (which keeps dropping after 5 seconds of connection). Those problems persist even now.
Guess I'll be messing around with the SMT mode in MSMDownloadTool since I've already lost my IMEI, see what I can do from that. If there's anything I do actually end up finding out, I'll post it on xda.
Update
I installed an update by download a zip, installed update via settings. System rebooted to complete update, and somehow the oem unlock option opened!!
From this point, fixing it will be pretty straight forward I think
Thanks for your help
CrustyBurger33 said:
Update
I installed an update by download a zip, installed update via settings. System rebooted to complete update, and somehow the oem unlock option opened!!
From this point, fixing it will be pretty straight forward I think
Thanks for your help
Click to expand...
Click to collapse
Nice! If everything is working properly besides the IMEI at this point, there's a couple of PC applications you can use.
I'd recommend write dual imei, not gonna post a link since IMEI fudging is against the rules (even if you're just trying to repair your IMEI)
Use the IMEI that's on your device sticker or on your phone packaging specifically.
Either way, hoping you get your phone back up to 100%.
As it turns out, it's not easy at all. My WiFi has exactly the same issue... keeps dropping, No SIM card, no baseband version. What's crazy is that I have rooted, and even repaired the IMEI via a tool. If I read the IMEI via the tool (and different ones just to be sure), they will all show the IMEI the same as the one that I wrote (which were the original ones).
But for some reason the phone still doesnt recognize it. I reboot it. Same story. The tool recognizes, the phone doesn't. I know for a fact that the issue cannot be hardware, at least for WiFi. If it was, it wouldn't connect to any network, but it does, and then disconnects after a few seconds. I think I have been all over every post on the internet regarding this issue, but still no luck.
Honestly, check with OnePlus if you're under the 1 year warranty window. This sounds like an issue that can really only be fixed with a replacement device.
CrustyBurger33 said:
As it turns out, it's not easy at all. My WiFi has exactly the same issue... keeps dropping, No SIM card, no baseband version. What's crazy is that I have rooted, and even repaired the IMEI via a tool. If I read the IMEI via the tool (and different ones just to be sure), they will all show the IMEI the same as the one that I wrote (which were the original ones).
But for some reason the phone still doesnt recognize it. I reboot it. Same story. The tool recognizes, the phone doesn't. I know for a fact that the issue cannot be hardware, at least for WiFi. If it was, it wouldn't connect to any network, but it does, and then disconnects after a few seconds. I think I have been all over every post on the internet regarding this issue, but still no luck.
Click to expand...
Click to collapse
Hi I have a similar problem.. My phone oneplus 8t is stuck in 'SMT Download failed error' mode. I was tryimg out custom roms which has caused this. My phone says can only be fixed via SMT Download mode. Can you help me out using the SMT download mode? I have tried MSM Tool normally to unbrick my phone but it doesn't work.
hello @nightfury04
If you have a Oneplus 8T you have to download the appropriate MSMDownloadTool (specifically for it) and make sure the version is correct too. Is your phone global/ locked to a carrier?
My question is how do I flash it back to stock I tried just flashing the kernel back to it like someone suggested but I'm getting a lot of cant load file cannot determine image file name I'm new to this I used Odin a bit with samsung is there such a tool for the nord the problem I think was my phone updated while waiting for the token and I think I got my patch file before I unlock the bootloader then turn around and mixed it up with the boot image I made after unlocking the bootloader I've already wiped it clean I didn't back it up because it was clean I figured I had the md5
Look inside here:
OnePlus Nord Flash File Firmware (Stock Rom) Free Download
OnePlus Nord Firmware Flash File can be used for fixing hang on the logo or removing all screen locks. This file will erase FRP and Pattern, Password lock
www.gadgetsdr.com
Thankyou
5ggggg said:
My question is how do I flash it back to stock I tried just flashing the kernel back to it like someone suggested but I'm getting a lot of cant load file cannot determine image file name I'm new to this I used Odin a bit with samsung is there such a tool for the nord the problem I think was my phone updated while waiting for the token and I think I got my patch file before I unlock the bootloader then turn around and mixed it up with the boot image I made after unlocking the bootloader I've already wiped it clean I didn't back it up because it was clean I figured I had the md5
Click to expand...
Click to collapse
If everyone wasnt so intrested in making someone feel dumb or looking like a smart pants all this jibberish could be explained easy I'm sure but I like so many other people that have been stuck dealing with this issue will have to just move on to another phone I hope this post helps someone avoid all these how to s that just leave you with a screwed up phone
i grabbed this for one purpose, reading manga, mostly on the SJ app, only i didnt think when buying it that the app wouldnt work on it, so i figured OK then just whack a custom on there, so i went to try and unlock the BL, nope just fires back "command not allowed" so i thought fine do it the old fashioned way, i got root and as per the instructions DDd the twrp image over the FOTA partition but no amount of reboots worked
i then downloaded the official twrp util from the play store, said it all flashed OK, even tried multiple versions but still no matter what i try i cant get into twrp and as such cant load in lineage etc. the only thing i thought may work was Philz but the files seem to be gone for that.
anyone know if its even still possible to get twrp on a BL locked device?
Emba4 said:
i grabbed this for one purpose, reading manga, mostly on the SJ app, only i didnt think when buying it that the app wouldnt work on it, so i figured OK then just whack a custom on there, so i went to try and unlock the BL, nope just fires back "command not allowed" so i thought fine do it the old fashioned way, i got root and as per the instructions DDd the twrp image over the FOTA partition but no amount of reboots worked
i then downloaded the official twrp util from the play store, said it all flashed OK, even tried multiple versions but still no matter what i try i cant get into twrp and as such cant load in lineage etc. the only thing i thought may work was Philz but the files seem to be gone for that.
anyone know if its even still possible to get twrp on a BL locked device?
Click to expand...
Click to collapse
For stock firmwares and locked booloaders look at this thread
https://forum.xda-developers.com/t/devdb-twrp-philz-touch-xzdualrecovery-2-8-26-release.2261606/