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!
Related
Did my best to avoid having to ask for help, but looks like I've run out of ideas. I've got a 7840 that currently refuses to boot past the recovery screen, thanks (probably) to my own incompetence. Here's what happened along the way to this point:
First, probably important to note: my tablet is a Chinese-released 7840 running 5.0.2 Lollipop. The hardware is identical from what I can tell, but the software was definitely a bit tweaked as there were no Google services installed. (And sideloading any of the Google services always failed no matter how I went about it.) This is basically why I decided to start messing around with things.
Attempted to load the developer firmware. Wound up in the dreaded "Intel Inside" bootloop, but thanks to @xBIGREDDx and his unbrick.zip (http://forum.xda-developers.com/showpost.php?p=60663442&postcount=2) I was able to return to normal booting. No matter how many times I attempted to flash the open source firmware, I always got stuck in the bootloop and had to flash the unbrick.zip to be able to do anything. No ability to exit the bootloop in order to reach the bootloader meant this was a big impasse.
I then decided to use the tethered CWM method to root the device for the purposes of giving sideloading the Play Store another try. That worked just fine and I was able to root my 7840 without a hitch. I then created a nandroid backup (which suspiciously didn't generate an MD5 file) in case I managed to really screw things up trying to sideload the Google Services.
That's when I thought wiping and recovering the 4.4.4 Kit Kat nandroid backup might be a good idea. This of course didn't work, so I wiped and restored my own 5.0.2 backup. However, at this point things wouldn't boot no matter what I did. I would see the boot screen with the Dell logo and the Lollipop-style ANDROID text, but after a couple of minutes everything would reboot and after a couple of tries the device would boot to recovery and just sit.
After fiddling around with trying different restore methods, I decided to see if I could flash the developer firmware to no avail. (Unable to write to OSIP, security error, etc.) Then I gave @anggusss's 5.0.1 OTA update.zip a try. (http://forum.xda-developers.com/showpost.php?p=60632439&postcount=21) That gave me a different error:
"Can't install this package (Fri Apr 24 13:29:34 CST 2015) over newer build (Fri Apr 24 13:58:18 CST 2015)."
Frustrating to see that a build a half hour newer might be all I need. So, if any of you happen to have captured the 5.0.2 OTA build (or can help me tweak the 5.0.1 build to report itself as newer), would you mind giving me a hand? Would be most appreciative. I've written to Dell open-source support but don't expect to hear back for another week or so. It'd be nice to not be using the Venue as a paperweight for a week.
wirebook said:
No matter how many times I attempted to flash the open source firmware, I always got stuck in the bootloop and had to flash the unbrick.zip to be able to do anything. No ability to exit the bootloop in order to reach the bootloader meant this was a big impasse.
Click to expand...
Click to collapse
Out of interest, how was the tablet booted when you flashed the unbrick.zip (did you volup + power or just regular boot?) ?
Going back to the open-source firmware won't help, because they 4.x to 5.x transition included a re-partitioning, and the bootloader in the 4.x firmware doesn't understand the new partition scheme.
If you boot with the vol. down key held, do you get into fastboot mode? If you can, then you should be able to flash a system image and boot image. I have those pulled from my device; I can post them for you to try later tonight.
anggusss said:
Out of interest, how was the tablet booted when you flashed the unbrick.zip (did you volup + power or just regular boot?) ?
Click to expand...
Click to collapse
I've never gotten vol. up + power to do anything, is that normal? Only vol. down + power, and that'll get me into fastboot mode.
xBIGREDDx said:
Going back to the open-source firmware won't help, because they 4.x to 5.x transition included a re-partitioning, and the bootloader in the 4.x firmware doesn't understand the new partition scheme.
If you boot with the vol. down key held, do you get into fastboot mode? If you can, then you should be able to flash a system image and boot image. I have those pulled from my device; I can post them for you to try later tonight.
Click to expand...
Click to collapse
Ah, well this sounds like it's my problem, then. If you can get those images to me to try I'd be most appreciative! Should be able to give it a shot as I'm still able to get into fastboot.
wirebook said:
Ah, well this sounds like it's my problem, then. If you can get those images to me to try I'd be most appreciative! Should be able to give it a shot as I'm still able to get into fastboot.
Click to expand...
Click to collapse
system.img
This is inside a .zip file because I don't know how to get only the important bits, so I got the whole /system partition. Just unzip then 'fastboot flash system system.img'
boot.img
This is straight from the OTA zip.
You will be pre-rooted. Let me know if this goes well. :good:
xBIGREDDx said:
system.img
This is inside a .zip file because I don't know how to get only the important bits, so I got the whole /system partition. Just unzip then 'fastboot flash system system.img'
boot.img
This is straight from the OTA zip.
You will be pre-rooted. Let me know if this goes well. :good:
Click to expand...
Click to collapse
Thanks a lot for those! Flashed both boot and system, though the system gave me some sort of error on my machine ("Invalid sparse file format at header magi") and then continued to flash something ("sending sparse 'system'"). I saw the red text of some sort of error on the tablet but wasn't able to read it fast enough. The system flash did seem a bit suspiciously fast, though...
Anyway, now waiting to see if anything boots. Been sitting on the Dell/Powered By Android screen for a couple of minutes, though, so if nothing else it looks like I've at least found myself in a new place. Will try reflashing if no improvement and then get back with results!
Sorry if this is considered spamming my own thread, but didn't seem right to just edit my earlier post.
Couldn't get the system image to flash. First got the error about needing to flash as a sparse system, which seemed to be fine. But when the device tried to write the sparse chunk to the partition, it threw an error. ("remote: flash_cmds error!") Thought this might've been a bug of my particular version of adb/fastboot, but updating or trying a different version didn't work any better. In fact, things got worse as I can't even run fastboot on my machine (Windows) anymore without the program crashing on me.
Jumped over onto my Mac and things seemed to be going better, but no progress was made. Still threw that error whenever it came time to write that first sparse chunk. Might my partition table be totally out of whack? (If so, how do I go about fixing it without easy access to an adb shell?)
In other news, I realized the back of the tab has "Venue 8 784001" engraved on it, so there might be hardware / bootloader changes that I can't beat...
Well, I'm not 100% sure it's going to be able to flash the system.img correctly, I thought I could just pull it from my device and it would flash fine, but apparently not. It would be interesting to see what your partition table looks like, but I don't know of a way to get that without having a root shell.
If you have a hex editor or know how to use dd, try chopping off like 200 MB from the end of the image (I think it's all zeroes for at least that much) and see if it flashes then.
If you don't know how to do that, I could upload a modified image for you.
xBIGREDDx said:
Well, I'm not 100% sure it's going to be able to flash the system.img correctly, I thought I could just pull it from my device and it would flash fine, but apparently not. It would be interesting to see what your partition table looks like, but I don't know of a way to get that without having a root shell.
If you have a hex editor or know how to use dd, try chopping off like 200 MB from the end of the image (I think it's all zeroes for at least that much) and see if it flashes then.
If you don't know how to do that, I could upload a modified image for you.
Click to expand...
Click to collapse
wirebook said:
Sorry if this is considered spamming my own thread, but didn't seem right to just edit my earlier post.
Couldn't get the system image to flash. First got the error about needing to flash as a sparse system, which seemed to be fine. But when the device tried to write the sparse chunk to the partition, it threw an error. ("remote: flash_cmds error!") Thought this might've been a bug of my particular version of adb/fastboot, but updating or trying a different version didn't work any better. In fact, things got worse as I can't even run fastboot on my machine (Windows) anymore without the program crashing on me.
Jumped over onto my Mac and things seemed to be going better, but no progress was made. Still threw that error whenever it came time to write that first sparse chunk. Might my partition table be totally out of whack? (If so, how do I go about fixing it without easy access to an adb shell?)
In other news, I realized the back of the tab has "Venue 8 784001" engraved on it, so there might be hardware / bootloader changes that I can't beat...
Click to expand...
Click to collapse
When you dump an image is raw.ext4 it has to be converted to sparse image format for android 5.0.2
social-design-concepts said:
When you dump an image is raw.ext4 it has to be converted to sparse image format for android 5.0.2
Click to expand...
Click to collapse
Well I found the source for img2simg but it won't do me much good... you wouldn't happen to have a pre-built tool handy would you?
xBIGREDDx said:
Well I found the source for img2simg but it won't do me much good... you wouldn't happen to have a pre-built tool handy would you?
Click to expand...
Click to collapse
I think the image you passed me already employed some kind of compression on it, as I was getting errors about an invalid sparse data header or something like that. (The size on the disk was also less than the reported image size.) Unfortunately I'm unable to mount or convert it on any of my machines so I'm a bit useless.
Thanks everyone for all the help you've been, by the way!
wirebook said:
I think the image you passed me already employed some kind of compression on it, as I was getting errors about an invalid sparse data header or something like that. (The size on the disk was also less than the reported image size.) Unfortunately I'm unable to mount or convert it on any of my machines so I'm a bit useless.
Thanks everyone for all the help you've been, by the way!
Click to expand...
Click to collapse
It's just a dump straight from my system partition. I don't have my tablet with me so I'm not certain on file paths but essentially I did:
dd if=/dev/block/by-name/system of=/storage/sdcard1/system.img
So it's a raw dump of the system partition, whatever happened to be in there.
I think the fastboot command tries to sparse things on its own, but fails?
If you want to try re-partitioning (could be dangerous, could be harmless), try these commands with the partition file from the OTA package:
EDIT: For anyone else coming along, don't do this, it didn't work out well for wirebrook. /EDIT
Code:
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl kk2lp_partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase cache
fastboot oem stop_partitioning
You may also want to erase data while you're in there.
xBIGREDDx said:
It's just a dump straight from my system partition. I don't have my tablet with me so I'm not certain on file paths but essentially I did:
dd if=/dev/block/by-name/system of=/storage/sdcard1/system.img
So it's a raw dump of the system partition, whatever happened to be in there.
I think the fastboot command tries to sparse things on its own, but fails?
Click to expand...
Click to collapse
That must be what's happening. I'll fiddle with things a bit more later on. It's a bummer there aren't any custom ROMs I could simply flash as an alternative to getting stock up and running...
xBIGREDDx said:
Well I found the source for img2simg but it won't do me much good... you wouldn't happen to have a pre-built tool handy would you?
Click to expand...
Click to collapse
xBIGREDDx said:
It's just a dump straight from my system partition. I don't have my tablet with me so I'm not certain on file paths but essentially I did:
dd if=/dev/block/by-name/system of=/storage/sdcard1/system.img
So it's a raw dump of the system partition, whatever happened to be in there.
I think the fastboot command tries to sparse things on its own, but fails?
Click to expand...
Click to collapse
It's looking for the sparse magic header that's not there I can when I get home you could also try to use 7zip to compress it to a .gz but I believe Intel stopped support for that format in 4.4.4.
I'm at work I have it at home if your on Linux and want to convert it.
social-design-concepts said:
It's looking for the sparse magic header that's not there I can when I get home you could also try to use 7zip to compress it to a .gz but I believe Intel stopped support for that format in 4.4.4.
I'm at work I have it at home if your on Linux and want to convert it.
Click to expand...
Click to collapse
Not sure this'll be useful for me any more because... (see below)
xBIGREDDx said:
If you want to try re-partitioning (could be dangerous, could be harmless), try these commands with the partition file from the OTA package:
Code:
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl kk2lp_partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase cache
fastboot oem stop_partitioning
You may also want to erase data while you're in there.
Click to expand...
Click to collapse
Gave this a shot and partitioning seemed to work just fine. Flashing the OTA boot.img worked just fine, and attempting to flash your system.img once again threw an error at me. Thought I'd perform a reboot at this point (bad idea!) to see what I was working with and then I found myself with @anggusss' USB screen. (http://forum.xda-developers.com/showpost.php?p=60675581&postcount=5) Probably should've tried flashing a something else just to see if that did anything.
Guessing I've now got a brick, because I'm no longer able to get it to register with Fastboot. I can, however, flash the open-source firmware and the unbrick.zip firmware, which reacts exactly like when @anggusss did it. We'll have to see if Dell ever gets back to my original query for help, otherwise might have to look into contacting Dell for a replacement.
You might have better luck, just using one of the tethered TWRP recoveries, If someone with a working system backups up system via TWRP recovery and shares it you could use the TWRP recovery to restore it.
I have Linux version tethered TWRP up and SDC has Windows version of tethered TWRP up.
Linux version
http://forum.xda-developers.com/android/development/linux-version-twrp-2-8-6-0-tethered-t3123075
Windows Version
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
vampirefo said:
You might have better luck, just using one of the tethered TWRP recoveries, If someone with a working system backups up system via TWRP recovery and shares it you could use the TWRP recovery to restore it.
I have Linux version tethered TWRP up and SDC has Windows version of tethered TWRP up.
Linux version
http://forum.xda-developers.com/android/development/linux-version-twrp-2-8-6-0-tethered-t3123075
Windows Version
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Click to expand...
Click to collapse
Thanks for the thought, but if I can't get into Fastboot mode (or get the computer to recognize the device as being in Fastboot mode)... kinda unable to use it.
wirebook said:
Gave this a shot and partitioning seemed to work just fine. Flashing the OTA boot.img worked just fine, and attempting to flash your system.img once again threw an error at me. Thought I'd perform a reboot at this point (bad idea!) to see what I was working with and then I found myself with @anggusss' USB screen. (http://forum.xda-developers.com/showpost.php?p=60675581&postcount=5) Probably should've tried flashing a something else just to see if that did anything.
Guessing I've now got a brick, because I'm no longer able to get it to register with Fastboot. I can, however, flash the open-source firmware and the unbrick.zip firmware, which reacts exactly like when @anggusss did it. We'll have to see if Dell ever gets back to my original query for help, otherwise might have to look into contacting Dell for a replacement.
Click to expand...
Click to collapse
Oh man, sad to hear, I've done that successfully in the past, they must have changed something in the process. I check just about every day for an update to the dev. firmware. Last time around it took them just over two months from release, so maybe, end of June?
xBIGREDDx said:
Oh man, sad to hear, I've done that successfully in the past, they must have changed something in the process. I check just about every day for an update to the dev. firmware. Last time around it took them just over two months from release, so maybe, end of June?
Click to expand...
Click to collapse
Fingers shall stay crossed till the end of the month, then! Contacted Dell Support and- just as I predicted- they don't want to help out. Something about being unable to do anything at all for Dell products purchased outside of their support areas (US and Canada). What a joy of a phone call that was...
An internet search landed me on guides for unbricking the Asus Zenfone displaying a similar USB symbol. They used the xFSTK Downloader to flash a set of files which then gave them renewed access to the bootloader (and thus fastboot). Played around with the xFSTK-Downloader and Manufacturing Flash Tool apps and can see the 7840 and even flash the (open-source and unbrick.zip) firmware, however I'm at a loss for what I might use for the Operating System flash files. Anybody have any thoughts?
Feel like I'm so close to getting this thing unbricked. If I could just figure out where to find the .bin "OS Image" that the tool wants...
Edit: Would also need the droidboot binary. FIngers crossed for Dell to release all of this soon...
EDIT: no longer need this. It is possible to make your own...
There is a chance that I may not have fried my V10 by shorting the test point, but to test that I need a full Nougat dump (something I can not believe I didn't make from my own phone -- I only have a full MM dump).
If there is someone that has rooted Nougat AND flashed all the Nougat partitions (v30b_update.zip and full_nougat.zip), and is willing to do a full dump, please let me know.
It is preferable if you have access to Linux because you will need to null out some partitions that have private data, and it is much easier to explain how to do it on Linux.
Lastly, this image will be 64gigs uncompressed, but it compresses very well.
Thanks,
-- Brian
Wish I can help, but mine is not rooted..
Hopefully I can bring my phone back to life (one way or another) so I can continue on. I got my board of eBay, but it was more dead than my current board.
runningnak3d said:
Hopefully I can bring my phone back to life (one way or another) so I can continue on. I got my board of eBay, but it was more dead than my current board.
Click to expand...
Click to collapse
That sounds bad. Hopefully someone will upload it.
if i can downgrade it , ill re upgrade to rooted nougat and get a dump but i dont know how to dump and dont have the image for downgrade.
@runningnak3d There's a guy selling one in General. Perhaps you can get a dump off of him?
@runningnak3d I currently have one V10 that I cannot get past the Checking Updates screen in the setup wizard on Nougat (with TWRP) which I am considering performing a KDZ wipe and another that went black screen after I flashed MM (also with TWRP). If I do a KDZ wipe on the first one, I could do a dump for you but I would have to look up how to. You are also welcome to buy the board from the second V10 from me but I'm unsure if you can revive it.
Thanks all, but everything I needed to make my own was staring me in the face.
-- Brian
i will help if i can , but didnt have root yet
@runningnak3d I'm in a need of a Nougat dump for H901, to make a bootable sdcard. Could you share yours or guide how to make one from nougat kdz?
Due to messing the aboot partition (while trying to shut the "big cores" off) the phone does not boot, nor enter download mode. On powering on, it only vibrates. QPST does not work with the phone put into 9008, it returns "target may be unstable". Before that, the phone was rooted, with bootloader unlocked, updated to nougat via the recovery, with the ZIPs.
Any help would be greatly appreciated
Be glad to, and it is easy, but you need dd. If you use Windows, there may be some program that can do something similar, but I haven't used Windows in years. You can always install a very basic Cygwin environment...
* Insert 64gig SD card
* Dump KDZ
* dd if=PrimaryGPTxxxxxx of=/dev/mmcblk0
The xxxxx above is because I can't remember what it gets dumped as, but it will be obvious.
Once you have the partition table on the sdcard, get a list of the partitons:
* gdisk -l /dev/mmblck0
Then proceed to flash the rest of KDZ onto their individual partitions.
For example, I believe that modem was partition 1, so:
* dd if=modemxxxxx of=/dev/mmcblk0p1
Repeat for every partition from the KDZ except system (unless you want to fully boot from the SD card). Also, you can flash recovery with TWRP, and then you can boot from the SD card to recovery and then you only need to flash your aboot partition, so you don't have to use download mode to flash the entire KDZ.
Let me know if you need me to clarify anything.
EDIT: If you do boot to recovery from the SD card, you will need to make sure to flash the correct device. When you go into an adb shell, you will have two mmcblk devices (mmcblk0 and mmcblk1). I don't remember which will be which, so to be safe flash the aboot partition on both...
-- Brian
@runningnak3d Thank you for your reply! I have Ubuntu 17 as a bootable DVD. Does the sdcard have to be formatted in a specific filesystem before doing this? Another question I have, is that the sdcard shows up as dev/sdd for me but it also shows that dev/sdd1 exists on it, so to which should I dd the GPT table to?
I tried to dev/sdd and wrote the rest of KDZ to the partitions, but the phone has not booted (its 64gb sd hc class 10 card). After dd-ing the PrimaryGPT, the terminal mentions that backupGPT is corrupted and that MBR is protective on the sdcard. Also, GParted shows "unknown" for each partition, and modem partition shows up as fat16 one.
Perhaps I should try different nougat KDZ? the phone's sticker under battery says it's H901, so was written in the phone under settings menu (phone also had t-mobile bloatware) and in LGUP when updating to MM, yet the motherboard has VS990 written on it.
My phone said vs990 on the board as well, so that isn't the issue. You need to flash a few partitions from the phone that aren't in the KDZ ... you will have to get someone to dump them for you.
The only place I had them was on an SD card that I have already wiped since I don't have a v10 anymore.
I will have to look in SBL1 to get you a list that you will have to ask for.
They are all just firmware, and contain nothing specific to a users phone, so anyone with a rooted Nougat phone can safely dump them for you.
Please bear with me. I am currently trying to revive my H910 and I order an H918 that I am going to use to help someone with, but I will try to get you the info ASAP.
H901 VS990 board 9008 brick help
@runningnak3d Hey, you seem like an expert at unbricking V10s. I have a H901 that has vs990 motherboard in it. It bricked while I was updating through LG Bridge. I now only have access to qualcomm 9008 mode.
From my understanding, there are 2 ways to solve this. QFIL or booting from dump image through sdcard. The qfil way didn't work for me, since there aren't any compatible .mbn files and xml for VS990 owners. So my only other option is getting to download mode via sdcard method, and I need the dump files for that. If I do what you've told @Mr_pringle, would my phone enter download mode? What exactly would I have to do? Thanks
@N3XTN3XUS What version were you on, and what version did LG Bridge try to update you to?
runningnak3d said:
@N3XTN3XUS What version were you on, and what version did LG Bridge try to update you to?
Click to expand...
Click to collapse
mm to nougat. Do you have the dump img for mm by any chance?
Unfortunately you are going to have to roll your own with the instructions I gave above.
In order to do that, you need to find out what model you should be flashing. I know you said your board said VS990, I am sitting here looking at my dead board, and it says VS990 on it as well, so H901 Nougat *should* have worked for you. I don't have any idea where you should start looking, but you do need to know that before making an SD card or even if you make a perfectly good card, it won't work
-- Brian
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
Help!
I've had a verizon V30 I unlocked and rooted via the frankenstein method a few years ago.
I was running out of space recently and did some cursory research about 'my verizon' app and it was pretty large, so I made a titanium backup and then deleted it. Also did this for the basic 'messages' app built in.
Noticed the phone was a little laggy and having some hang issues after that so I rebooted. It's stuck on a Verizon splash screen with a few colorful dots.. seems stuck there.
I've tried clearing the cache and booting into safe mode all with the same result. I really do not want to do a factory reset.
What are my next steps for troubleshooting this or trying to restore that program? Any help is appreciated--I've tried to search a bit but not finding a good first step towards trying to resolve this.
Thanks!
water- said:
Help!
I've had a verizon V30 I unlocked and rooted via the frankenstein method a few years ago.
I was running out of space recently and did some cursory research about 'my verizon' app and it was pretty large, so I made a titanium backup and then deleted it. Also did this for the basic 'messages' app built in.
Noticed the phone was a little laggy and having some hang issues after that so I rebooted. It's stuck on a Verizon splash screen with a few colorful dots.. seems stuck there.
I've tried clearing the cache and booting into safe mode all with the same result. I really do not want to do a factory reset.
What are my next steps for troubleshooting this or trying to restore that program? Any help is appreciated--I've tried to search a bit but not finding a good first step towards trying to resolve this.
Thanks!
Click to expand...
Click to collapse
Early on with the verizon V30 roms I found that uninstalling some of the bloatware caused boot loops. From then on I just froze them; doesnt help your space situatuon though...
If no other suggestions, you could try a dirty flash of the ROM you were running (assuming you flashed TWRP zip).
I believe you'll need MyVerizon anyway, as this is what enables VOLTE and VOWIFI on Verizon (for me, at least). So I would not recommend removing it anyway.
Granted, you're past that. I would think that dirty-flashing the ROM should restore it, potentially? That could be one way to get back to running. Another way might be to reload the APK somehow. You might need to use TWRP to do that, unless there's another way to do it from a TiBu backup? If I can help in some way (I'm on VS996) I'm happy to try.
Unless you actually deleted the apps from System, it's almost certain that a Factory Reset will solve it. But I can understand your reluctance.
I'm not sure a dirty flash will help, since the problem is your data partition. You already tried deleting cache (I presume in TWRP).
And I agree that if you could somehow reload the apk, that might do it. Does ADB install work in TWRP, despite no OS? If so, that's worth trying. First pull the apks you removed from System to your computer, then run adb install apk-filename.
But FIRST make a full TWRP data backup of what you have now!
If you have to Factory Reset, you can use TiBu to restore your user apps from that backup. I haven't tried that in years, but I assume TiBu still has this feature.
Fingers crossed for you :fingers-crossed:
And for others who see this: Careful, selective debloating IS possible, but it always starts with a full backup: TWRP if rooted, otherwise LG Backup, (which saves app data and most OS settings).
Thanks all for responses, appreciated so much. In a bit of a pinch as I needed my phone for a backpacking trip last weekend, I just moved forward as best I could on Friday. Generally I tweak my phone enough to unlock/root then let it be. I guess I got greedy/complacent try trying to de-verizonify it and clear some space as much as possible.
Two things
1) Immediate solution, and still seeking some advice:
I used LGUP to flash the Android 9 kdz as an upgrade I think to the phone. Because I had TWRP as my recovery that ran into an encryption error (I subsequently saw this caveat/warning further down in one of ChazzMatt's posts), and due to that was required to wipe/clear everything.
So now I have 'benefits' of Android 9 but no root. However my bootloader is still unlocked.. so I am still seeking advice how I can get Android 9 root. Please don't tell me I have to go back to 8 and do some stuff before going back to 9 with root. I didn't actually see in any guide how to root on 9. But it is possible I missed it/just need to apply same sequence as shown as on the guide for doing so on 8.
I'm on 30c version of PIE and keep getting bugged to install a system update which I keep putting off because I'm leery of that..but I can't freeze the process without root.
Also because I flashed the stock OS, that means I lost the custom recovery, I don't have TWRP anymore (this seems so, but looking for confirmation), right?
2) retrospect, and a question for future reference
After all this I realized like an idiot I had a TWRP backup made in 2018 after I first unlocked and rooted it. Just hanging out on my SD card, which I could have accessed via TWRP before I flashed the KDZ. If I would have restored that it would have re-installed the OS and retained my data. Is that considered a dirty flash though, like it might not have worked or had subsequent problems?
And secondly on the SD card, I found all the 'dank memes' and other downloads I was worried I'd lost, so most of the data loss tragedy :silly: was averted (main pics backup to cloud, learned that lesson after lg g4 hardware bootloop pain).
water- said:
1) Immediate solution, and still seeking some advice:
I used LGUP to flash the Android 9 kdz as an upgrade I think to the phone. Because I had TWRP as my recovery that ran into an encryption error (I subsequently saw this caveat/warning further down in one of ChazzMatt's posts), and due to that was required to wipe/clear everything.
So now I have 'benefits' of Android 9 but no root. However my bootloader is still unlocked.. so I am still seeking advice how I can get Android 9 root. Please don't tell me I have to go back to 8 and do some stuff before going back to 9 with root. I didn't actually see in any guide how to root on 9. But it is possible I missed it/just need to apply same sequence as shown as on the guide for doing so on 8.
Click to expand...
Click to collapse
With unlocked bootloader on Pie, here's how you reinstall TWRP (IF you are on firmware with fastboot flash commands). Yes, I made a standalone post for this -- but if you read it it's basically just Section 6 of WTF Instructions. However, I had to make a standalone post because too many people kept thinking they had to downgrade back to Oreo, etc.
So, you can reinstall TWRP on Pie if you have unlocked bootloader. The problem is you need to fastboot flash commands to do that. VS996 firmware does not have that, which is why VS996 owners have to TEMPORARILY convert to US998 in the first place to unlock bootloader, install TWRP and root. Yes, your bootloader is already unlocked, but on VS996 you don't have the necessary fastboot flash commands to reinstall TWRP.
Thus, you will need to go back to US998 firmware (flashing KDZ via Dev Patched LGUP) to get fastboot flash commands. You can do it the hard way (US998 Pie KDZ) or you can do it the easy way (US998 Oreo KDZ). With already unlocked bootloader, you don't need to go back early Oreo, you can go to last Oreo. I don't recommend flashing US998 Pie for this, as there's too many people who have trouble with US998 Pie (stuck on LG logo, etc). You just need to temporarily get fastboot flash commands, and get TWRP reinstalled.
That post I have linked in the first sentence is for unlocked Bootloader with fastboot flash commands, on any stock firmware (Pie, Oreo, even Nougat if you wanted that for some reason).
Once you reinstall TWRP, then you can go back to VS996 Pie firmware via TWRP flashable zip.
Thanks for your response, now and two years ago.. super appreciated
I only need to get to the point to put the phone in debug mode (with access to fastboot) to get TWRP installed after flashing the recent oreo kdz. After TWRP installed follow your instructions (thanks!) to flash TWRP pie..
I'll probably give it a go this weekend or tomorrow evening, but do you have a recommended link to US998 Oreo kdz? https://androidfilehost.com/?fid=1395089523397933445 is fine?
Whereafter I'll follow your instructions for installing it (using LGUP patched) at: https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99820a040330-kdz-t3786337
In the ROM section, go to ChazzMatt's US998 Pie KDZ thread. It also has instructions for rolling back to Oreo. Follow them to the t.
Make sure to use the Pie-compatible LGUP version in there when you roll back, and install it exactly as described in that thread.
His US998 Oreo thread will have a download link for Oreo 20h (the latest Oreo). Otherwise it's easy to find on lg-firmwares.com.
Good luck to you
Ok really that was pretty easy and not bad once I got everything lined up, did it in maybe 30 minutes or less. I'm in Pie with root now and TWRP recovery. Thank you for the help!
Two points:
1) after flashing TWRP, I got some issues when wiping, I was able to flash the VS996 ROM but kept seeing some red "twrp can't mount system" or something like this. It would be a hassle but do I need to go back and reformat/reflash? or do it dirty at least?
2) maybe related to the above, maybe (probably not) not.. and I realize magisk and other avenues might cover it these days but I'm trying to debloat the TWRP flashed VS996 ROM with Titanium Backup.. stuff like NFL and slacker radio, google music.. like I did on Oreo. But Titanium keeps giving me an error about 'can't find the apk' -- Ti says I have root. I have read a bit that Android 10 really packages the apps in there so it's not like you can just remove the ones you want. is this the case for 9 too?
suggestions for alternative tool if Titanium is kind of a dinosaur in that regard?
Thanks
Well done!
1) It's best to use Format Data in TWRP to avoid that mounting error. Unless you are certain you have no mounting problems, I would recommend doing that before spending more time setting up the OS.
2) Before trying to freeze apps with TiBu, see if they can be Disabled in the regular Apps menu. Most of the "optional" bloatware can. Of course make a TWRP backup before freezing anything with TWRP!
Water-, there is already a debloated Verizon 99630c rom out there somewhere, if you would like to try it. I'm on it now.
Sorry, I can't link it. It was made by micromod777. So do a search for him.
I also use tibu, but there is another app (?) out there called migrate that backs everything up. You might look for it and try it. (I did use it a month or so ago myself just to try it - - worked for me).
water- said:
Ok really that was pretty easy and not bad once I got everything lined up, did it in maybe 30 minutes or less. I'm in Pie with root now and TWRP recovery. Thank you for the help!
Two points:
1) after flashing TWRP, I got some issues when wiping, I was able to flash the VS996 ROM but kept seeing some red "twrp can't mount system" or something like this. It would be a hassle but do I need to go back and reformat/reflash? or do it dirty at least?
Click to expand...
Click to collapse
You're welcome!
See points "f" and "g" of the screenshot. When you were installing TWRP I think you missed the "format data" part... And/or possibly the "reboot recovery" step immediately after.
If you were reading in an app (XDA or Tapatalk) instead of web browser, it's possible that section was truncated and you didn't see it.
ChazzMatt said:
You're welcome!
See points "f" and "g" of the screenshot. When you were installing TWRP I think you missed the "format data" part... And/or possibly the "reboot recovery" step immediately after.
If you were reading in an app (XDA or Tapatalk) instead of web browser, it's possible that section was truncated and you didn't see it.
Click to expand...
Click to collapse
hmmm
it's possible.. ..i definitely gave formatting a shot (hence the red errors.) and believe I rebooted to recovery.
Where I'm at now, OS booting/operating flawless (bloat aside) and root verified, can boot back into TWRP no problem...
recommended course of action?
water- said:
hmmm
it's possible.. ..i definitely gave formatting a shot (hence the red errors.) and believe I rebooted to recovery.
Where I'm at now, OS booting/operating flawless (bloat aside) and root verified, can boot back into TWRP no problem...
recommended course of action?
Click to expand...
Click to collapse
Sorry, I'm in another hemisphere for several weeks on leave of absence for family matters. Didn't see this until now. Hope you got it worked out.
ChazzMatt said:
Sorry, I'm in another hemisphere for several weeks on leave of absence for family matters. Didn't see this until now. Hope you got it worked out.
Click to expand...
Click to collapse
Not a problem at all! Maybe you mistook this post for another, as you'd fairly promptly replied to me through here over the last two weeks! much to my appreciation.
Basically I'm saying when I was doing some of the wipe functions in TWRP before flashing the new OS, and while flashing it, I saw some red mount system error messages.
However my phone is fully functional, I can reboot into TWRP recovery, I'm not noticing any functional issues with it right now.
Can I ignore because functional phone and recovery access = functioning fully! or is there some check I should do or whatnot. I mean I could clear data and start over again but It's been a week+ of customizing and getting it how I like it, kind of a hassle if it's not needed/necessary.
Thanks
water- said:
Not a problem at all! Maybe you mistook this post for another, as you'd fairly promptly replied to me through here over the last two weeks! much to my appreciation.
Basically I'm saying when I was doing some of the wipe functions in TWRP before flashing the new OS, and while flashing it, I saw some red mount system error messages.
However my phone is fully functional, I can reboot into TWRP recovery, I'm not noticing any functional issues with it right now.
Can I ignore because functional phone and recovery access = functioning fully! or is there some check I should do or whatnot. I mean I could clear data and start over again but It's been a week+ of customizing and getting it how I like it, kind of a hassle if it's not needed/necessary.
Thanks
Click to expand...
Click to collapse
Do you have encryption on? TWRP will show a mount error upon start, and prior to the passcode being entered.
So,
This may seem mundane to some of you, and I apologize. But I'm hitting a wall with this Pixel. I cannot use Fastboot normally because I can't get access to any of the internal partitions. I have a list of them that I looked up, but fastboot will not allow me to use any fastboot flash or flashing commands that I need to flash a new ROM.
I've unlocked bootloader - Duh - (been doing this a little while)
Rebooted
Reenabled ADB - #adb reboot bootloader (works fine)
Sending files --> ADB and fastboot both will serve the image or file to the phone, but the phone fails on "partition does not exist" on every time.
I have tried re-flashing this device with the android flashing tool through Google (works fine and I'm currently running the 13 Beta T3B3). Would straight flashing from a zip file help?
I want to be running LoS but I cannot get even the vendor_boot or boot image to flash. Everything seems to be software/firmware locked and I've tried the fastboot commands to unlock certain partitions and things like that from what I can tell in the changes to fastboot. So my question is:
What am I missing? I have even got it to boot into LoS and things worked, but you could tell something was very wrong with the flash and major app/gapp issues. This was accomplished with the flash tool flashing the partitions "boot" and "vendor_boot" and "dtbo" for me to get me into the LoS recovery. From there I reset and installed via sideload like normal, flashed the rest of the partitions listed with LoS and I cannot get a working build without major app issues and major stability issues. CLI will also not give me any info on why these can't be flashed, of course, but that's not how this should work. I know it should be more stable than it is just because it's a Pixel (one would think - has been in the past) It's a Global model GB7N6 and I don't understand what the hold up is.
Any help or suggestions would be greatly appreciated! Thanks!
You need to flash the regular factory image first, not the beta!!
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
See instructions
To be fair, I just flashed the beta as a last ditch. Every try I've done was with production software.
I will absolutely try this though. Anything to straighten this mess out.
XGX5309 said:
To be fair, I just flashed the beta as a last ditch. Every try I've done was with production software.
I will absolutely try this though. Anything to straighten this mess out.
Click to expand...
Click to collapse
Hi friend
If prior attempts to fix the problem in GetSimple CMS failed, it could be worthwhile to try the beta version as a last resort. A alternative strategy can occasionally assist in solving the issue Free Fire