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!
This place has gotten a bit messy with all of the threads out there and it's especially confusing for those who are new to unlocking and rooting. Or, heck, to those who weren't around as the threads were being written and referenced. I've reposted my consolidated step-by-step list half a dozen times so far - and the steps seem to be working for folks - so I'm going to post it here. You're still going to have to visit the original threads, but hopefully this will serve as a clear outline for you.
Maybe we can also try to keep general unlocking and rooting questions ("I don't know where to start, help me!") to this thread to avoid cluttering up the other ones. Reserve questions in those threads for those specifically related to the OP ("I received ABC error after doing XYZ, what does it mean?"). If anyone sees general unlocking or rooting questions in other threads, maybe direct them here as a place to start. Make sense?
A list of FAQs can be found here in the second post.
Many thanks to @tenfar and @DrakenFX (among others with their help and suggestions!) for the tools and files they provided to make all of this happen.
Unlocking and Rooting your Axon 7
This set of steps has worked successfully for multiple folks (including myself) on the US/NA variant (A2017U) and stock B29. Folks with EU/global variant (A2017G) may have issues and as of right now, should proceed with caution. If you see any problems and/or have a different variant and need additional (or different) steps added, let me know. I will update the thread as necessary.
Copy everything off your internal storage that you don't want to lose.
Get all of the files you need from the steps below and put them on your microSD card.
Backup your boot and recovery (just in case) using the tool found here: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Using the same tool as above, flash TWRP (recovery) found in that thread. You do not need to flash the boot image!
Unlock the bootloader: http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Flash the bootstack and ROM for your variant: http://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Boot phone, set it up, whatever
Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
This will leave you with an unlocked bootloader, fully functioning TWRP (no data encryption issue), and a rooted phone. You will no longer be able to receive OTAs!
Putting Your Axon 7 Back to Stock
If you want to revert back to stock and re-lock your bootloader (eg. sending the phone in for warranty work or are selling it), you should be able to do that using the steps below. It worked for me, anyway, exactly as written below.
Copy everything off your internal storage that you don't want to lose. If you're not rooted (so already stock, but with unlocked bootloader), skip to step 6 below. Otherwise, continue.
Grab the "StockSystem" zip for your variant from this thread and place on your microSD card: http://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Reboot into TWRP and wipe system, data, dalvik, and cache
Flash the StockSystem zip and power off (doing so will restore stock boot but does not appear to restore recovery)
Boot into EDL mode and flash stock recovery only: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Power off the phone, plug from computer, and then boot into stock recovery (hold Vol+ and press Pwr, continue holding Vol+ until recovery comes up)
Select "Wipe data / factory reset" and then "Yes"
After that finishes, select "Reboot to bootloader"
Plug in your phone into your computer and do: fastboot oem lock (see second post if this doesn't work and says <waiting for device>)
Your phone will reboot and should have been totally wiped (including internal storage) by doing the above
This should leave you with a stock, locked, and unrooted phone that can take OTAs. Note: it's possible (in fact, likely) that an OTA could break the ability to unlock your bootloader and gain root again, so be careful about going back to stock if you think you'll want to unlock/root later on!
If you need any stock files for B20 or B27 (stock recovery for re-locking, for example), you can get them here: http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
What does disemmcwp do and why should I do it?
disable emmc (internal storage) write protection is what allows changes to system (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
I only see B27 files and not B29. Help!
If you're in any of the threads referenced in the OP that only have files marked as B27, you can use those even if you're on or upgrading to B29. If the thread has B29 files, use those.
Fastboot can't find my device.
If fastboot oem lock returns <waiting for device> or fastboot devices doesn't show anything, the most likely culprit is that Windows is using updated ADB drivers and you need to roll back. You can do this via Device Manager > right-click Android Device (or Kedacom USB device) / Android Bootloader Interface > Update driver > Browse my computer for driver software > Let me pick... > Choose older version (in this case, v9)
For #3, you might want to emphasize that only TWRP is needed, and that people can skip flashing a boot.img. I've seen people who want to unlock their bootloader asking where to find the modified boot.img for B29, which isn't needed.
And of course, thanks for the guide!
xtermmin said:
For #3, you might want to emphasize that only TWRP is needed, and that people can skip flashing a boot.img. I've seen people who want to unlock their bootloader asking where to find the modified boot.img for B29, which isn't needed.
And of course, thanks for the guide!
Click to expand...
Click to collapse
Excellent point. Done!
It would be nice if someone can post a video on YouTube. That would make it that much easier.
Thanks for your guide.
It will be good to post also the steps to lock it again, in case that we need to send the phone for warranty. Because this method does not void warranty, does it?
I think that it is only to push the backup fastboot and 'fastboot oem lock'
I have set up my phone now (with fingerprint security) and want to make a full backup in twrp. Is it true, that i must disable fingerpint and/or pin before i make an backup because when i restore backup with security enabled, that the phone was locked?
Also it would be nice a guide how to go back to stock and update to latest OTA.
Sent from my ZTE A2017G using Tapatalk
tasar said:
I have set up my phone now (with fingerprint security) and want to make a full backup in twrp. Is it true, that i must disable fingerpint and/or pin before i make an backup because when i restore backup with security enabled, that the phone was locked?
Click to expand...
Click to collapse
Yes you must disable your screen lock due to the encryption issue in MiFavor. If you do not disable your screen lock and restore your data, your pin/password/pattern would become wrong and your only option would be to factory reset. Fingerprint would still work but I wouldn't risk it.
dejikocv said:
Thanks for your guide.
It will be good to post also the steps to lock it again, in case that we need to send the phone for warranty. Because this method does not void warranty, does it?
I think that it is only to push the backup fastboot and 'fastboot oem lock'
Click to expand...
Click to collapse
razorsbk said:
Also it would be nice a guide how to go back to stock and update to latest OTA.
Click to expand...
Click to collapse
I've updated the OP with the relevant information. I haven't done it myself so I can't say what the exact screens are, but the steps should be pretty close and you should be able to figure it out.
If no one confirms (or corrects) the steps as I've written them, I'll go through the process before installing CM and update the steps to more accurately describe the process.
@rczrider
I'll updating my sticky thread/guide/info to direct everyone who want to unlock/root their devices, here to your thread....instead of having an outdated one with old info.
Can you also make a guide for g model with 05 update for unlocking and rooting and istalling twrp.
kodrnusa said:
Can you also make a guide for g model with 05 update for unlocking and rooting and istalling twrp.
Click to expand...
Click to collapse
This will be very helpful
Do I have to rollback to B20 or B27 to unlock bootloader?
@rczrider
I have tested the back to stock steps for you on the US model and for now those steps do not get you back to stock. I have wiped the right things and flashed the StockSystem zip multiple times but twrp lives through the wipe and StockSystem install. I'll try to get it working and report back.
Thanks for the great guide!
So, if I do this, no OTA updates. Can I just download the updates and flash them? Are they available anywhere? Or no updates, period, right now?
Orlando1193 said:
I have tested the back to stock steps for you on the US model and for now those steps do not get you back to stock. I have wiped the right things and flashed the StockSystem zip multiple times but twrp lives through the wipe and StockSystem install. I'll try to get it working and report back.
Click to expand...
Click to collapse
I was under the impression that @DrakenFX's StockSystem zip would overwrite boot, but I could be wrong in that. Have you tried doing the same process, but manually replacing recovery using @tenfar's tool and your own original recovery image?
If you don't have your original recovery, it (among other files for B20 and B27) can be found here: http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
baconboy said:
Thanks for the great guide!
So, if I do this, no OTA updates. Can I just download the updates and flash them? Are they available anywhere? Or no updates, period, right now?
Click to expand...
Click to collapse
Correct, no updates at all for the moment. As it stands, I believe we would need a modified/merged full zip that included the OTA's content. You definitely won't be able to receive OTAs officially.
Everytime i want unlock bootloader i get this error
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Great thread. Just wish this post was up 2 days ago. I just flashed B29 to my Axon from B20_Boot (which I now have read was a bad move. I just found out call audio & mic arent working). Good thing you put this post up. I have been scrambling through the threads to figure a solution. Just gonna flash back to B20 stock using TWRP :good:
Kevinkuensken said:
Everytime i want unlock bootloader i get this error
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
You probably haven't enabled OEM Unlock in Developer Options.
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
duraaraa said:
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei.
It's just a preliminary build so I can't promise anything/everything will work! Keep that in mind. I'm not responsible if you brick your device.
EDIT: Does not work with Mate 10 series.
DOWNLOAD LINK:
https://drive.google.com/open?id=0B45NCsO2AL_1NEh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei/comments/75uwkd/october_12_first_official_android_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you've got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don't mess around too much with TWRP, to be sure you don't brick your system!
Click to expand...
Click to collapse
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
AndDiSa said:
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
Click to expand...
Click to collapse
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
I've tried flashing the entire update.zip file in TWRP...but as noted TWRP is unable to mount internal storage. I'm not sure if I need to wipe and reformat first. I also have no clue whether the TWRP build I installed is properly compatible with the device. I had nothing to lose by giving it a shot.
thref23 said:
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
Click to expand...
Click to collapse
This will not work as the boot chain will be broken due to mismatching checksums. You need to have the correct images. To flash a OTA image you also need to have the standard recovery image installed ...
So...will someone correct please correct me if this is wrong?
If I were to flash a c00 oeminfo file, I could then install a c00 update.zip via dload folder?
Would c432 work as well (with a flashed oeminfo), even though the Euro hardware has different bands than my hardware?
There is now a full OTA on FF for C635.....still nothing for c636...
Finally, a full OTA is available for c636.
But the 'dload' method (update.app on an sd card) failed at 5%. And flashing ramdisk/recovery/erecovery/system images also failed.
Is this possibly because the OTA is B153, whereas my M5 was shipped B121?
(I hate to be that guy bumping his own thread, sorry)
I'm unbricked!
For those in a similar spot, looking to rebrand, or otherwise interested...
I finally e-mailed Funky Huawei for assistance. Their unbrick tool did not work. However, their e-recovery method worked perfectly (basically, you point your router's DNS to Funky Huawei, enter stock recovery and connect to wi-fi, and Funky Huawei's servers mimic Huawei's servers. If they do not have your firmware on their server, they will add it by request (provided it exists on the internet).
I paid $65 for a 30 day pass - a little steep, but I was impatient. I'm not sure if I could have gotten away with paying less. If you want to try and use my FH account over the next 30 days PM me (although I don't want to get carried away with that).
For those looking to rebrand, if you can flash an OEMinfo file successfully (FH has a rebrand tool and I have no clue how well it works), you should be able to use FH's erecovery method to flash firmware (don't blame me if something goes wrong).
One reason for the trouble I was having, if because I bootlooped after making a change to the vendor/build.prop file. This file was on the vendor partition, not the system partition, and for whatever reason the vendor partition cannot be flashed via fastboot (in theory it can be flashed, in reality it returns an error that doesn't have to do with the size of the partition).
Before reverting to FH, I finally got TWRP installled and functioning, and after all the attempts I made to recover my device, the same build.prop file which initially caused a bootloop was still in the /vendor folder. And TWRP wouldn't mount the system and vendor partitions as read/writeable - that was frustrating.
Now off to experiment with AOSP GSIs while I feel like I have little to lose...
Please help me
hello everyone,
i tried to rebrand my m5pro with help of ministryofsolutions. Something went wrong and my tablet (CMR-AL19) is stucked in the recovery mode. how can i fix it? Someone who ca help me? I will pay
Greeztings
Luigi
thref23 said:
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
Click to expand...
Click to collapse
Looking to start a discussion on rooting the unlocked version.
I have tried the root for other variants for this phone and does not work
hi would love to see my k8+ rooted. i have the lmx210ulma version mtk and android 7.1.2.
There are recoveries for this phone and i have a full partition dump i nade today using salt on my ubuntu 18.04 machine. when i say full i mean something like 30-50 .img files pulled.
Any way. The problem on my end is booting into fastboot mode or rebooting to the bootloader. i have tried ADB, recovery and key combinations with out ever getting there. I can however get the phone to download into recovery download mode just fine.
any help would be appreciated
https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434
Duhjoker said:
hi would love to see my k8+ rooted. i have the lmx210ulma version mtk and android 7.1.2.
There are recoveries for this phone and i have a full partition dump i nade today using salt on my ubuntu 18.04 machine. when i say full i mean something like 30-50 .img files pulled.
Any way. The problem on my end is booting into fastboot mode or rebooting to the bootloader. i have tried ADB, recovery and key combinations with out ever getting there. I can however get the phone to download into recovery download mode just fine.
any help would be appreciated
Click to expand...
Click to collapse
We are now in this forum. Why some dork mod moves these too early?
Why here, why not to the K8 forums instead?
The link I posted should work with your device...
Just got told to go to the k8 forums because im really just trying to get the bootloader unlocked. Temp root is nice but my plans involve a recovery and a fully rooted phone. Im trhing to develop a way to compile apps and operating systems completely on the device but i need full access.
Im looking for firmware for LG K8 2018 X210ULMG. Where can i find it ?
go to google and type in "LG K8 + LMX210ULM stock rom" you will get at least five pages or more.
Duhjoker said:
go to google and type in "LG K8 + LMX210ULM stock rom" you will get at least five pages or more.
Click to expand...
Click to collapse
I can't fin anywhere for X210ULMG. Try and when you will find paste here link because anywhere is this rom.
which android version do y0u have 9n your k8. I also need you to go to settings system software info and tell me the software versiion. And just for SandG no seriously, open up a terminal in terminal emulator and type getprop. im looking fir the value of
ro.lge.swversion_arb
to be of further assistance may i ask what exactly you are using it for? ie reflash stock fix brick or other. i can help you with the best plan of action and any other how to.
If you are still out there the ULMG and ULM are the same device. There is no ULMG stock rom. So you will need to flash your K8+ using the ULM firmware. If you are looking to roll back to get to the bootloader the lowest version you can find is a letter F version. None so far have an ARB value so happy flashing.
I myself own this device and its an easily rootable phone with bootloader unlock. Just flash the kdz with the lowest letter value then adb reboot bootloader and then in fastboot mode use fastboot oem unlock and your free to flash any cv1 device twrp recovery.img to the phone.
Just make sure to use either carliv image kitchen or android image studio to check and make sure that system, syatem.img, are both ext4 in recovery.fstab. System.img will probably be labled emmc which will cause failure to mount. Also cache and data as well. Firmware/modem should be labled as vfat. Just as if they were labled if you looked at original fstab.
To root just extract boot.img from kdz and patch using magisk and flash using fastboot flash boot boit.img then fastboot flash recovery recovery.img When booting into twrp first time flash no verity opt encrypt and make backup. Upon exiting make sure all parts are mounted or twrp loop will occur.
Duhjoker said:
If you are still out there the ULMG and ULM are the same device. There is no ULMG stock rom. So you will need to flash your K8+ using the ULM firmware. If you are looking to roll back to get to the bootloader the lowest version you can find is a letter F version. None so far have an ARB value so happy flashing.
I myself own this device and its an easily rootable phone with bootloader unlock. Just flash the kdz with the lowest letter value then adb reboot bootloader and then in fastboot mode use fastboot oem unlock and your free to flash any cv1 device twrp recovery.img to the phone.
Just make sure to use either carliv image kitchen or android image studio to check and make sure that system, syatem.img, are both ext4 in recovery.fstab. System.img will probably be labled emmc which will cause failure to mount. Also cache and data as well. Firmware/modem should be labled as vfat. Just as if they were labled if you looked at original fstab.
To root just extract boot.img from kdz and patch using magisk and flash using fastboot flash boot boit.img then fastboot flash recovery recovery.img When booting into twrp first time flash no verity opt encrypt and make backup. Upon exiting make sure all parts are mounted or twrp loop will occur.
Click to expand...
Click to collapse
I have problem because one month ago I flashed My K8 ULMG with kdz for Aristo 2 . I downloaded the software from Aristo 2 and made Brick through it.
Now it doesn't turn on, gives no sign of life, nothing. When connected to a laptop, the computer can only see Qualcomm HS-USB QDLoader 9008.
Do you know solution for it ?
There are two versions of the k8+ a qualcomm version and an mtk version. Did you read my post after your last reply. I was trying to help you determine that sort 0f thing.
As for a fix.... no as of currently there is no fix for either the qc or mtk versions once bricked. i am working on possible solutions but those are not going to be any time soon.
Your best bet at this point is to look for a used and damaged phone and replace the board in your phone with a different board. Find a k8+ lm-x210ulm or an aristo 2 board. They are cheap around $20 us and can be found with broken screens. They have no arb values so can be flashed and downgraded to get the boot loader unlocked and reflashed and upgraded after with guidance.
Dont feel to bad it happens. I have 4 boards that are trash but im still gonna try to unbrick them. But please what ever you do dont do it with out guidance. pm if you need and ill help.
Duhjoker said:
There are two versions of the k8+ a qualcomm version and an mtk version. Did you read my post after your last reply. I was trying to help you determine that sort 0f thing.
As for a fix.... no as of currently there is no fix for either the qc or mtk versions once bricked. i am working on possible solutions but those are not going to be any time soon.
Your best bet at this point is to look for a used and damaged phone and replace the board in your phone with a different board. Find a k8+ lm-x210ulm or an aristo 2 board. They are cheap around $20 us and can be found with broken screens. They have no arb values so can be flashed and downgraded to get the boot loader unlocked and reflashed and upgraded after with guidance.
Dont feel to bad it happens. I have 4 boards that are trash but im still gonna try to unbrick them. But please what ever you do dont do it with out guidance. pm if you need and ill help.
Click to expand...
Click to collapse
Did you found some method for unbrick this phone without motherboard change ?
I'd like to start by saying after 2 weeks of researching and piecing guides together to unbrick my phone was hell. But once i found the right route it took me less thank 10mins all from a simple tool called Fastboot Enhanced V1.3.0. Now this Nifty little tool took me from bricked phone which was saying "Your img(Boot, Recovery) have been destroyed please flash the right files or contact customer service to fix this problem to Unbricked in less than 10 minutes. It took me 2 weeks of researching but it's finally done. Now most of you will say well you could have use MSMTool or the MTK or even SP Flash Tool. Those are all fine and dandy and all but one problem with those. YOU have to SCOUR the internet to TRY to find files you need to actually be able to use them. I been over several guides. I had when a guide basically says this 1) DO THIS SKIP SKIP SKIP important parts 2) NOW DO THIS. Like WTH was i supposed to do in between 1 and 2. Todays guides lack thoroughism and complettioin. Guides these days take Half Ste;ps and then thrown together.
I will also leave a step by step instructions on how to use the Fastboot Enhanced V1.3.0 in DETAIL on how to get your phone from what mine did to Unbricked state. I will also attack Nord N200 5G DE2118 .img FIles for those who have a hard time scouring the internet for things. I for one get agitated and aggravated as hell when searching the internet for things. Especially when you have to pc things together. I will leave files if it's Fine by staff. Now these files have come directly from my OnePlus Nord N200 DE2118 extracted less than 2 hours ago 10:04 p.m. EST September 10th 2022. Can Only attach One File? and i can't even remove the accidental clicked bmp pic of COD BO Cold War Zombies.
Guide For Using Fastboot Enhanced V1.3.0
1) Download Fastboot Enhanced Tool from: https://forum.xda-developers.com/t/...enhance-payload-dumper-image-flasher.4310553/ from XDA Which is how I came across it. . The Tool is a WINDOWS ONLY Tool. (How many guides i came accross that didn't state whether it's for Windows or Linux) I use Dual Boot so I have both.
2) Install Fastboot Enhanced V1.3.0 and wait for it to finish. Now you will only have to be in Fastboot Mode to do any of this. I can't believe how a semi hard problem was fixed really easy
3) Now you will Have to Have a Payload.Bin File which can be found with any OEM Firmware for Your specific Phone. The Payload.bin allows you to be able to do a Payload Dump Using Fastboot enhance it is at this point if any of your partitions are missing or corrupt you will find out because it will tell you if you can understand the way it's explains it.
4) This Nifty little tool will tell you your device naem whether your phone is using secure boot or not, current slot your phone is using if you have an a/b partition scheme and the update Status. This is Listed Under basice properties. AGAIN MAKE SURE YOUR IN FASTBOOT MODE.
5) Next tab is the Partitions Tab which will List all your partitions currently on your phone . To the right of your listed partitions you will have and ACTIONS Tab. This is the tab where you can flash, erase, delete, create, and Resize your partitions. With this tool You CAN Flash Important Partions So be careful what you flash.
6) Next Tab Over is the Payload Dumper. This is the Tab where you need the Payload.bin File for your specific phone. this will give you payload version manifest size, metadata signatures size Metadata Signatures (Base64), data blobs, singatures size signatures (Base64) Fuill package Yes or No. Timestamp and block size. also under payload dumper tab another tab shows up called the Dynamic Partition Metadata. Now this will list your REALLY IMPORTANT Dynamic Partitions These are the partitions you don't want to flash anything over them. It will give you the Partition group size, which partitions are included and tells you wheter snapshot is enabled or not.
7) Under The payload Dumper tab the partitions tab gets a different Actions box. This time i'ts a box that let's you extract your .IMG files from your phone it allows for incremental as well as to ignore unknown operations and ignore checksums also under this partitions tab it gives you a checksum for each and every one of your partitionss. Ok now on to the Simple but yet comprehensive guide.
8) Now to start you want to add the Payload.bin to the Payload Dumper and then click on the Partitions tab. Once under this tab you will select each partition and hit the extract button and extract it to a folder named something like Flash FIles.
9) you hace to do this for each partition. Once done you will have your .IMG files from your exact phone for future use as well. You then want to click on the Fastboot Visualization tab and then click on Partitions.
10) Once under the partitions tab here, you will want to start flashing your .IMG files to the partitions. it should take you around 10 to 15 mins total to finish flashing everything.
11) Once your finished flashing you want to do a quick Terminal and do a FASTBOOT -W and then Fastboot Reboot and watch your phone start working again.
FEEL FREE TO LEAVE ANY COMMENTS SUGGESTIONS ON WHAT COULD HAVE BEEN BETTER OR IF IT'S NOT ENOUGH DETAIL. I TAKE CONSTRUCTIVE CRITICISM WITH A GRAIN OF SALT. THIS WAS MY FIRST GUIDE I EVER PUT TOGETHER. LOL THIS GUIDE TOOK ME LONGER THAN IT DID UNBRICKING MY PHONE.
BELOW YOU WILL FIND .IMG FILES FOR ONEPLUS NORD N200 DE2118
Thanks so much man. This phone has been an absolute pain in my ass to unbrick, the issue Ive had with Fastboot enchance is that all the firmware versions Ive found seem to contain images it doesnt recognize for the phone.
Do you have the original OTA for these , or the un-extracted payload.bin youd possibly be able to post?
So I went through the process without success, the only abnormalities I noticed were that my device did not have a partition for "my_carrier.img" , so that wasnt flashed.
And upon using the fastboot -w command, it did execute but at the end was given the message "Erase successful, but not automatically formatting.
File system type raw not supported."
Silent_Song1982 said:
Thanks so much man. This phone has been an absolute pain in my ass to unbrick, the issue Ive had with Fastboot enchance is that all the firmware versions Ive found seem to contain images it doesnt recognize for the phone.
Do you have the original OTA for these , or the un-extracted payload.bin youd possibly be able to post?
Click to expand...
Click to collapse
I found the way MSMTool works too. I'm going to probably write a guide for that too. MSMTool is so much easier.
Silent_Song1982 said:
So I went through the process without success, the only abnormalities I noticed were that my device did not have a partition for "my_carrier.img" , so that wasnt flashed.
And upon using the fastboot -w command, it did execute but at the end was given the message "Erase successful, but not automatically formatting.
File system type raw not supported."
Click to expand...
Click to collapse
I had a lot of issues with Fastboot Enhance too until I realized I was the one causing errors. Any logical partition it doesn't recognize you can create an empty partition wiht that name and it will resize it then copy it over. Also make sure whatever slot you're on, so say slot a, your logic paritions would be system_a, system_ext_a, vendor_a, product_a and odm_a except I dont see odm.img in the list of file by OP so I'm not sure if that will even help.
and now i have ran into HARD BRICKED mode trying to flash a custom from. phone will only load EDL and everytime I try msmtool I get the error Check OCDT CDT file empty please redownload it. and I scoured the internet for 4 days now and all I can find is stuff like What is .CDT extension but nothing about having and empty CDT file for android. getting frustrated with it now
Link575 said:
I had a lot of issues with Fastboot Enhance too until I realized I was the one causing errors. Any logical partition it doesn't recognize you can create an empty partition wiht that name and it will resize it then copy it over. Also make sure whatever slot you're on, so say slot a, your logic paritions would be system_a, system_ext_a, vendor_a, product_a and odm_a except I dont see odm.img in the list of file by OP so I'm not sure if that will even help.
Click to expand...
Click to collapse
here is the ODM file. if you might be able to post a cdt file much apppreciated
sorry took so long to upload it for you
MiniNinja2024 said:
here is the ODM file. if you might be able to post a cdt file much apppreciated
sorry took so long to upload it for you
Click to expand...
Click to collapse
Hey I appreciate it but I didn't need it I was just informing the poster above that the ODM file was missing and that might cause an issue when using Enhanced Fastboot. Not really sure what a cdt file is though, sorry.
Im in the US and have the unlocked N200, to unbrick mines i used the MSM tool and selected MetroPCS as my carrier. then after i had phone functionality i put the correct rom on my phone.
hitsndc said:
Im in the US and have the unlocked N200, to unbrick mines i used the MSM tool and selected MetroPCS as my carrier. then after i had phone functionality i put the correct rom on my phone.
Click to expand...
Click to collapse
my phones being recognized as a Oneplus A5000 for some reason now. and it's a Nord N200 i've also been stumped by the attached pic and my phone is stuck in EDL mode
hitsndc said:
Im in the US and have the unlocked N200, to unbrick mines i used the MSM tool and selected MetroPCS as my carrier. then after i had phone functionality i put the correct rom on my phone.
Click to expand...
Click to collapse
Can you link me to the MSM tool you used? I think there might be a few different versions of it floating around for the Nord N200. Mine was purchased unlocked
vipermark7 said:
Can you link me to the MSM tool you used? I think there might be a few different versions of it floating around for the Nord N200. Mine was purchased unlocked
Click to expand...
Click to collapse
this is my version
DE18CB_T-Mobile-MetroPCS_OxygenOS_11.0.1.7.zip | by Scanman0 for OnePlus Nord N200 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
also my phone is stuck in EDL mode and it registers as an android oneplus a5000 tablet for some odd reason i've tried just about every single n200 file out ever since my phone got stuck in EDL mode and evertime same result cdt file
also i had some with same version that i know personally send me his cdt file and same thing says it's empty
and my phone is the Metro-by Tmobile
vipermark7 said:
Can you link me to the MSM tool you used? I think there might be a few different versions of it floating around for the Nord N200. Mine was purchased unlocked
Click to expand...
Click to collapse
and i'm in Florida
Can someone please dump the firmware from this phone & upload it please?
cryptojoe37 said:
Can someone please dump the firmware from this phone & upload it please?
Click to expand...
Click to collapse
I gave up on this phone. no long working on it. Was having major pains with it.
I need the loader from the firmware
cryptojoe37 said:
I need the loader from the firmware
Click to expand...
Click to collapse
the loader ? bootloader?
michaelwaycraig67 said:
the loader ? bootloader?
Click to expand...
Click to collapse
abl/xbl partitions. perhaps some other.
zmashine said:
abl/xbl partitions. perhaps some other.
Click to expand...
Click to collapse
uploading now will give a link after uploaded
zmashine said:
abl/xbl partitions. perhaps some other.
Click to expand...
Click to collapse
2.74 GB file on MEGA
mega.nz
MiniNinja2024 said:
I'd like to start by saying after 2 weeks of researching and piecing guides together to unbrick my phone was hell. But once i found the right route it took me less thank 10mins all from a simple tool called Fastboot Enhanced V1.3.0. Now this Nifty little tool took me from bricked phone which was saying "Your img(Boot, Recovery) have been destroyed please flash the right files or contact customer service to fix this problem to Unbricked in less than 10 minutes. It took me 2 weeks of researching but it's finally done. Now most of you will say well you could have use MSMTool or the MTK or even SP Flash Tool. Those are all fine and dandy and all but one problem with those. YOU have to SCOUR the internet to TRY to find files you need to actually be able to use them. I been over several guides. I had when a guide basically says this 1) DO THIS SKIP SKIP SKIP important parts 2) NOW DO THIS. Like WTH was i supposed to do in between 1 and 2. Todays guides lack thoroughism and complettioin. Guides these days take Half Ste;ps and then thrown together.
I will also leave a step by step instructions on how to use the Fastboot Enhanced V1.3.0 in DETAIL on how to get your phone from what mine did to Unbricked state. I will also attack Nord N200 5G DE2118 .img FIles for those who have a hard time scouring the internet for things. I for one get agitated and aggravated as hell when searching the internet for things. Especially when you have to pc things together. I will leave files if it's Fine by staff. Now these files have come directly from my OnePlus Nord N200 DE2118 extracted less than 2 hours ago 10:04 p.m. EST September 10th 2022. Can Only attach One File? and i can't even remove the accidental clicked bmp pic of COD BO Cold War Zombies.
Guide For Using Fastboot Enhanced V1.3.0
1) Download Fastboot Enhanced Tool from: https://forum.xda-developers.com/t/...enhance-payload-dumper-image-flasher.4310553/ from XDA Which is how I came across it. . The Tool is a WINDOWS ONLY Tool. (How many guides i came accross that didn't state whether it's for Windows or Linux) I use Dual Boot so I have both.
2) Install Fastboot Enhanced V1.3.0 and wait for it to finish. Now you will only have to be in Fastboot Mode to do any of this. I can't believe how a semi hard problem was fixed really easy
3) Now you will Have to Have a Payload.Bin File which can be found with any OEM Firmware for Your specific Phone. The Payload.bin allows you to be able to do a Payload Dump Using Fastboot enhance it is at this point if any of your partitions are missing or corrupt you will find out because it will tell you if you can understand the way it's explains it.
4) This Nifty little tool will tell you your device naem whether your phone is using secure boot or not, current slot your phone is using if you have an a/b partition scheme and the update Status. This is Listed Under basice properties. AGAIN MAKE SURE YOUR IN FASTBOOT MODE.
5) Next tab is the Partitions Tab which will List all your partitions currently on your phone . To the right of your listed partitions you will have and ACTIONS Tab. This is the tab where you can flash, erase, delete, create, and Resize your partitions. With this tool You CAN Flash Important Partions So be careful what you flash.
6) Next Tab Over is the Payload Dumper. This is the Tab where you need the Payload.bin File for your specific phone. this will give you payload version manifest size, metadata signatures size Metadata Signatures (Base64), data blobs, singatures size signatures (Base64) Fuill package Yes or No. Timestamp and block size. also under payload dumper tab another tab shows up called the Dynamic Partition Metadata. Now this will list your REALLY IMPORTANT Dynamic Partitions These are the partitions you don't want to flash anything over them. It will give you the Partition group size, which partitions are included and tells you wheter snapshot is enabled or not.
7) Under The payload Dumper tab the partitions tab gets a different Actions box. This time i'ts a box that let's you extract your .IMG files from your phone it allows for incremental as well as to ignore unknown operations and ignore checksums also under this partitions tab it gives you a checksum for each and every one of your partitionss. Ok now on to the Simple but yet comprehensive guide.
8) Now to start you want to add the Payload.bin to the Payload Dumper and then click on the Partitions tab. Once under this tab you will select each partition and hit the extract button and extract it to a folder named something like Flash FIles.
9) you hace to do this for each partition. Once done you will have your .IMG files from your exact phone for future use as well. You then want to click on the Fastboot Visualization tab and then click on Partitions.
10) Once under the partitions tab here, you will want to start flashing your .IMG files to the partitions. it should take you around 10 to 15 mins total to finish flashing everything.
11) Once your finished flashing you want to do a quick Terminal and do a FASTBOOT -W and then Fastboot Reboot and watch your phone start working again.
FEEL FREE TO LEAVE ANY COMMENTS SUGGESTIONS ON WHAT COULD HAVE BEEN BETTER OR IF IT'S NOT ENOUGH DETAIL. I TAKE CONSTRUCTIVE CRITICISM WITH A GRAIN OF SALT. THIS WAS MY FIRST GUIDE I EVER PUT TOGETHER. LOL THIS GUIDE TOOK ME LONGER THAN IT DID UNBRICKING MY PHONE.
BELOW YOU WILL FIND .IMG FILES FOR ONEPLUS NORD N200 DE2118
Click to expand...
Click to collapse
I still do not understand what I have to flash to get an OS back on this device. All I have is fastboot... soft bricked. I have de2117 ( "best buy" model). Reading all these instructions and I am still very confused