I am beyond ecstatic, after 3 months of research, trial and error, I fixed my tablet!!
I am pleased to announce a fix to the dreaded QDLOAD 9008 brick! I've written this tutorial on the one tablet experimented on (LG-V410 aka Gpad 7.0 LTE US ATT), but I'm pretty certain others may find this helpful to other qualcomm msm based devices.
Background: I maintain that I can fix anything I break so I did the worst thing and corrupted the data on my LG GPAD LTE 7.0 (V410). As a result the tablet wouldn't go into any mode, no lights, even when charging, no screen image or light, nothing. When I plugged it into my computer, it wasn't even recognized, windows told me the device was having a problem. After a little experimentation I got it recognized (held power while connected to power cycle) by the computer as "QD BULK". Further research I found some drivers for Qualcomm devices and got the computer to recognize it as "QDLOADER 9008". I thought this was great news but from there got no where. I tried qpst, qfuse, hyperterminal, LG B2C, LG SUPPORT TOOL, EFS Professional, miflash, blankflash, etc... everything I tried got me nowhere. After 3 months, It is now fully operational and apparently CARRIER UNLOCKED, talk about a pot of gold at the end of a rainbow!!
WORD OF WARNING: This is not a simple matter, 9008 most likely means your Grand Partition Table is corrupted, and the poor thing doesn't have a clue how to function. My method is NOT GUARANTEED in any way, I will not be responsible if you turn your paper weight of a device into permanent paper weight or half functioning paper weight etc...PROCEED WITH CAUTION, this is not for the feint of heart nor a simple fix!! You've been warned!
PreRequisites:
-Windows (for expanding the KDZ) (there may be a linux alternative to LGFirmwareExtract)
-Linux and some basic experience with dd and navigating the terminal (I used ubuntu) --(again, nearly everything I'm about to explain can probaly be translated to another os.)
-KDZ for your device. http://forum.xda-developers.com/g-pad-10/general/kdz-lg-g-pad-7-0-v410-t3224867
-Replacement aboot and boot (see attached)
-KDZ Extractor ---http://forum.xda-developers.com/showthread.php?t=2600575
-TWRP http://forum.xda-developers.com/g-pad-10/development/recovery-twrp2-8-5-0lgv400-410-t3049568
-Fasboot and ADB http://forum.xda-developers.com/showthread.php?t=2588979
-A modified rom like Cyanogen mod etc... http://download.cyanogenmod.org/?device=v410
-16GB microsd card + a way of directly writing to it (i.e. usb card reader etc..) a second one is helpful but not required.
-Most important, Patience, beer, more patience, and more beer...
To teach a man to fish, some pertinent understanding: First thing to understand is how your main board works. Personally I disassembled my device and cross referenced every chip to do this, Good news is you don't have to. When power goes to the device, the SoC (system on a chip) looks to built in storage media for booting instructions (think low level here) and that in turn fires up everything else and then loads your kernel etc... You may be aware, there are two different types of computer systems out there, the old method used a BIOS, and the current uses UEFI. Older machines, when power was given to the system, the BIOS was responsible for firing up peripherals and finding the bootloader etc... UEFI (Unified Extended Firmware Instruction) however, relies on firmware on storage media to do all that.
For example, an x86 PC with a bios, when power is given to the board, the bios runs the show, testing equipment and waking up devices, then when it's ready, it looks to external media for a little magic byte at the end of the first sector of that media to indicate that it is bootable and in turn will boot (let those instructions take over). This style of booting media is called MBR or Master Boot Record.
Modern machines and most mobile devices use GPT or global partition table. There are quite a few advantages to GPT one primary being the possibility of many many more primary partitions, (MBR was very limited). The GPAD 7 LTE has 34 partitions to put things in perspective. When your device is stuck in 9008 mode, it is because it doesn't have a clue how to boot, most likely your GPT is corrupted. Fortunately, at least with the Gpad 7.0 this information does not have to be on the onboard internal memory chip. For this fix we will be constructing an sdcard to have all this info to get into a mode capable of writing to the emmc.
Without Further Ado, Here are the steps:
]PLUG THE TABLET INTO A CHARGER while you do the following (you may think it's been off and fully charged, but in reality it's probably been trying to boot over and over again while looking lifeless)
1.) Get the KDZ for your device (stock firmware)
2.) Extract the DZ using LGFirmwareExtractor
3.) Extract all the .bin files from the DZ using LGFirmwareExtractor
3b.) V410 US LTE ONLY - Replace aboot and boot with the files I attatched --I was fortunate enough to back them up before I hosed my tablet and they proved invaluable as the ones in the KDZ I linked to were causing strange graphic issues.
4.) open a terminal in linux and dd the sdcard with the file you extracted called "PrimaryGPT...."
I.E. "sudo dd if=/PATHTODZFILES/PrimaryGPT_0.bin of=/dev/sdx" (BE CERTAIN of the of= path, you can find yourself with more problems if you get that wrong) (run "sudo fdisk -l | less" first to verify what your sdcard's path is.)
This is where it gets tedious...:
5.) Do some hand stretches and start charting all 34 partitions on paper. Your sdcard is now partitioned with GPT and you need to know the name of each partition and its path. I.e. ("Partition name: LAF Located at /dev/sdXx")
6.) now for the fun part: dd every .bin to the corresponding partition EXCEPT: laf.bin and any of the system_xxxxx.bin files. (laf disables fastboot and the next step will bring you to a useless LG firmware download mode)( I.e. sudo dd if=/PATHTODZFILES/laf_xxx.bin of=/dev/sdXx) If some fail out, don't fret too much, I'm currently uncertain which ones are required and don't feel like corrupting my tablet again to figure that out. If the next step doesn't work you may need to revisit this step and ensure everything was accurate. It's easy to write down the wrong location for a partition and throw everything off
7.)Unmount your sdcard and put it in the tablet
8.) Press and hold power and volume up...If all went well, there is suddenly life to your paperweight!! Congratulate yourself and prepare for more fun... If nothing happened, revisit the above steps, more than likely something got flashed to the wrong partition.
9.)Now that you have fastboot, plug your tablet into the computer and use the following command: "fastboot boot TWRP.img" (or whatever the name or path is for your downloaded TWRP image.
10.) You should now be in TWRP and now your device is ADB ready, we are close to the home stretch...
11.) Now we need to load up an sdcard with all those dz files (except for laf and system images) and the custom rom like cyanogen mod. (if you only have the one sdcard you can unmount it and remove it while the table is in TWRP...crazy right?, if you opt for this, reformat the sdcard to ext or fat or whatever you please so the tablet can see all the bin files) Then put the sdcard into the tablet. You may need to remount the card in twrp before proceeding...
12.) Now from your computer type the following command "adb shell".
13.) now just like you did with the sd card dd PrimaryGPT_0.bin to the internal memory card, with the following command: dd if=/sdcard/PrimaryGPT_0.bin of=/dev/block/mmcblk0
14.) Grab the paper you wrote all the partitions down on and start doing the same thing you did to the sdcard to your tablet. You'll adjust the following command accordingly: "dd if=/sdcard/PARTITIONNAME.bin of=/dev/block/mmcblkpX (X being the partition number)
(again skip all system bin's and laf_xxxx.bin. Flashing laf disables fastboot on LG devices.)
15.) now time to install your custom rom, go through the prompts, clear your cache, and delvik cache and choose power off.
If all went well, you now have a tablet again, that's unlocked too!!!!! If not, don't lose faith, revisit the steps and ensure you didn't mistype or overlook something, this is so tedious it's easy to do. For instance, if you mistype your of=xxx it will create the file instead and give no error.
Post with your success stories, questions or difficulties and I'll try to help.
Yours Truly,
TheKiln
UPDATE/WARNING: Do not at any time under any circumstances dd directly from your host computer to the internal memory on your tablet, only do this via the asb shell. This may render a mode that I have not yet found a fix to, I will be working on it soon but from initial observation may be more complicated then the above instructions. With any invasive hacks like this tutorial there is always the possibility of making matters worse, so exercise caution and patience.
Quick Update/Revision : I am actively experimenting with this device and wanted to share that if your sbl1 and sbl1b partition is corrupt I have confirmed it will also cause 9008 mode. Therefore, it may be best to determine if the table is corrupt (try "parted /dev/block/mmcblk print"), and if not instead of wiping rewriting mmcblk0 try restoring sbl1 and sbl1b first. The V410 boots in the following order from what I can tell slb1->aboot->boot->system. So far I haven't found a downside to my prior instructions but to be less invasive just in case it might be wise to try this amendment.
I know my grand partition is corrupt, because after doing fastboot erase, basically everything, it came up as /dev/sdb. In a panic, I had deleted all the partitions, so now obviously my emmc storage is one big formated 16gb HD that cannot be seen in windows or linux no longer.
I just tried your method, found this post by doing a google search for:
sudo dd if=PrimaryGPT_0.bin
Had been doing just this, including the laf and many other ways. Am still getting the same thing though when putting the sdcard in the tablet, shows a 0% battery.
with the sdcard in the tablet I do get:
Bus 003 Device 063: ID 05c6:f006 Qualcomm, Inc.
Then after a few minutes, leaving it plugged into the USB I get:
Bus 003 Device 058: ID 1004:61a1 LG Electronics, Inc.
Also, with the sdcard in I do get KDZ_FW_UPD_EN to start updating but then get a perimeter error.
bethnesbitt said:
I know my grand partition is corrupt, because after doing fastboot erase, basically everything, it came up as /dev/sdb. In a panic, I had deleted all the partitions, so now obviously my emmc storage is one big formated 16gb HD that cannot be seen in windows or linux no longer.
I just tried your method, found this post by doing a google search for:
sudo dd if=PrimaryGPT_0.bin
Had been doing just this, including the laf and many other ways. Am still getting the same thing though when putting the sdcard in the tablet, shows a 0% battery.
with the sdcard in the tablet I do get:
Bus 003 Device 063: ID 05c6:f006 Qualcomm, Inc.
Then after a few minutes, leaving it plugged into the USB I get:
Bus 003 Device 058: ID 1004:61a1 LG Electronics, Inc.
Also, with the sdcard in I do get KDZ_FW_UPD_EN to start updating but then get a perimeter error.
Click to expand...
Click to collapse
Ive seen the exact mode you are referring to. Three possibilities:
1.) unplugged, hold down the power button for 30 seconds (or less if fastboot comes up)
2.) your sd card does not have all the necessary partitions to boot (which i just confirmed are specifically rpm, rpmb, tz, tzb, sbl1, sbl1b, PrimaryGpt(has to be done first), aboot and abootb)
3) They didn't dd quite right. from my active testing Ive found if you script the dd'ing it doesn't quite flash right, unless you add a delay after each step.
Its actually a very good sign you are seeing the 0% battery logo, sounds like you are almost there. Let me know what happens. Ill be happy to help guide you. Ive dedicated my v410 as a dev board so Im constantly running tests and reverse engineering it.
The 0% only shows up with the sdcard in, after I remove it, nothing. Tried wall charging it all night, that did nothing.
My theory is that if there was some way to mount the raw emmc and dd the primarygpt.bin to the raw emmc hd then the rest would be not problem.
I deleted the original EMMC partitions in gparted under linux after doing an erase fastboot -w laf, system, etc... something like that. After that the tablet did not show up again in gparted as soon as I unplugged it.
Right now I'm zero dd'ing my 16gb sd card, dang dd'ing seems to glue the partitions to the sdcard, If I try to fdisk the sdcard or delete the partitions using gparted, as soon as I dd the primarygpt.bin the old files reappear. Need to start fresh with 0s to the card.
In windows I can actually install specific lg drivers while in qualcomm hs_usb 9008 mode. The interesting thing with the sdcard in I can install the LG Android Net USB serial driver, which will not work while in 9008 mode.
bethnesbitt said:
The 0% only shows up with the sdcard in, after I remove it, nothing. Tried wall charging it all night, that did nothing.
My theory is that if there was some way to mount the raw emmc and dd the primarygpt.bin to the raw emmc hd then the rest would be not problem.
I deleted the original EMMC partitions in gparted under linux after doing an erase fastboot -w laf, system, etc... something like that. After that the tablet did not show up again in gparted as soon as I unplugged it.
Right now I'm zero dd'ing my 16gb sd card, dang dd'ing seems to glue the partitions to the sdcard, If I try to fdisk the sdcard or delete the partitions using gparted, as soon as I dd the primarygpt.bin the old files reappear. Need to start fresh with 0s to the card.
In windows I can actually install specific lg drivers while in qualcomm hs_usb 9008 mode. The interesting thing with the sdcard in I can install the LG Android Net USB serial driver, which will not work while in 9008 mode.
Click to expand...
Click to collapse
The 0% comes up when your sdcard is inserted because you are close to getting it done. You're going to have your computer running all night on the zero'ing but I can assure you that will be in vein. The whole point of this tutorial is so you can get into a mode in which you can flash the emmc. I can tell you are a little lost in the steps so pm me and I'll help you out. Also a word to the wise, you can try all you want with windows and the 9008 drivers, but seriously there is nothing out there specific to the v410 thats going to help you "engage" the 9008 mode. Not being stubborn I've just literally tried it all. If it's any credit I am clinically OCD. I can't sleep till I figure things out.
Finally, I see a hope is shining here!
I bricked my LG VK810, when I was trying to flash twrp, I refered to v500 pad instead and I flashed wrong img files (aboot, boot, sb1, sb2, sb3, tz & twrp.img) "only those 6 files" so I only need to replace those with the correct files, which I downloaded now.
I do not have Ubuntu, however I have CentOS, which i have not used for couple of years, so I forgot how to use it. also do I still need to use the LG Firmware Extractor?
please help
thekiln said:
This is where it gets tedious...:
5.) Do some hand stretches and start charting all 34 partitions on paper. Your sdcard is now partitioned with GPT and you need to know the name of each partition and its path. I.e. ("Partition name: LAF Located at /dev/sdXx")
6.) now for the fun part: dd every .bin to the corresponding partition EXCEPT: laf.bin and any of the system_xxxxx.bin files. (laf disables fastboot and the next step will bring you to a useless LG firmware download mode)( I.e. sudo dd if=/PATHTODZFILES/laf_xxx.bin of=/dev/sdXx) If some fail out, don't fret too much, I'm currently uncertain which ones are required and don't feel like corrupting my tablet again to figure that out. If the next step doesn't work you may need to revisit this step and ensure everything was accurate. It's easy to write down the wrong location for a partition and throw everything off
Click to expand...
Click to collapse
Please please please help, how to do those steps!
nmnm4alll said:
Please please please help, how to do those steps!
Click to expand...
Click to collapse
I am not certain exactly which partitions have to be flashed, the attached note I made was from what I can tell so far. I was simply noting that it may be best to try one partition at a time vs doing them all at once, it is at your own descretion. So as far as listing the partitions, I'm not familuar with the centos distro but in Ubuntu it is something to the effect of fdisk /dev/sdb -l or gdisk /dev/sda then p. I hope that answers your question, If not please be more specific to your exact question.
thekiln said:
I am not certain exactly which partitions have to be flashed, the attached note I made was from what I can tell so far. I was simply noting that it may be best to try one partition at a time vs doing them all at once, it is at your own descretion. So as far as listing the partitions, I'm not familuar with the centos distro but in Ubuntu it is something to the effect of fdisk /dev/sdb -l or gdisk /dev/sda then p. I hope that answers your question, If not please be more specific to your exact question.
Click to expand...
Click to collapse
Thank you very much for your response, I am sorry I have never flashed partitions before, sbut I noticed gparted is not on CentOS, so I downloaded Puppy precise Linux as I was able to find gparted and I tried using it as shown in this video, https://www.youtube.com/watch?v=6z1Tu9l8WNc
But I am confused now about how big and what are the formats for the 34 partitions which need to be created?
nmnm4alll said:
Thank you very much for your response, I am sorry I have never flashed partitions before, sbut I noticed gparted is not on CentOS, so I downloaded Puppy precise Linux as I was able to find gparted and I tried using it as shown in this video, https://www.youtube.com/watch?v=6z1Tu9l8WNc
But I am confused now about how big and what are the formats for the 34 partitions which need to be created?
Click to expand...
Click to collapse
Flashing PrimaryGPT_0.bin will automatically create the partitions. Flashing the individual partitions will give each partition the data needed. There should be no need to manually create partitions, if no partitions show up in gparted, the problem goes back to primarygpt, as that is the partition table.
I am not quite sure what you mean by:
thekiln said:
5.) Do some hand stretches and start charting all 34 partitions on paper. Your sdcard is now partitioned with GPT and you need to know the name of each partition and its path. I.e. ("Partition name: LAF Located at /dev/sdXx")
Click to expand...
Click to collapse
how to can I get the Partition names?
Edit: I finally was able to get Ubuntu installed on my computer, so please instruct accordingly, sorry I have been googling everything you have mentioned in your OP with no luck!
Thanks in advance.
nmnm4alll said:
I am not quite sure what you mean by:
how to can I get the Partition names?
Edit: I finally was able to get Ubuntu installed on my computer, so please instruct accordingly, sorry I have been googling everything you have mentioned in your OP with no luck!
Thanks in advance.
Click to expand...
Click to collapse
For the names I like to use "parted /dev/sdb" then "print" (sdb being the location of the sd card, might be sdc, sdd, etc..)
thekiln said:
For the names I like to use "parted /dev/sdb" then "print" (sdb being the location of the sd card, might be sdc, sdd, etc..)
Click to expand...
Click to collapse
Thanks for the command line, I came up with this 36 partitions
https://www.dropbox.com/s/bw8nj317y3v7pw6/VirtualBox_Ubunto_05_01_2016_08_59_03.png?dl=0
now how do I know each partition's path?
you have mentioned "I.e. ("Partition name: LAF Located at /dev/sdXx")"
so do I type for example: "modem: LAF located at /dev/sdb1" (sdb1 is my sdcard's path)?
thekiln said:
6.) now for the fun part: dd every .bin to the corresponding partition EXCEPT: laf.bin and any of the system_xxxxx.bin files. (laf disables fastboot and the next step will bring you to a useless LG firmware download mode)( I.e. sudo dd if=/PATHTODZFILES/laf_xxx.bin of=/dev/sdXx) If some fail out, don't fret too much, I'm currently uncertain which ones are required and don't feel like corrupting my tablet again to figure that out. If the next step doesn't work you may need to revisit this step and ensure everything was accurate. It's easy to write down the wrong location for a partition and throw everything off
Click to expand...
Click to collapse
Those are the files got extracted from the DZ file
https://www.dropbox.com/s/z3ebiy4vvnsy9oo/Untitled.png?dl=0
and this is a screenshot in Ubuntu after copying the file on a 64 memory stick and mounting it
https://www.dropbox.com/s/gqn35n1npklq8ld/VirtualBox_Ubunto_05_01_2016_09_30_15.png?dl=0
Do I just type: "sudo dd if=/media/mike/MEMORY/aboot_153600.bin of=/dev/sdb1" and so on for all .bin files?
Please try to write command lines as I do not have experience with Linux
I'll be honest and blunt, if you do not have experience with linux, a simple keystroke mistake could wipe your entire computer. I can't in good conscience recommend touching dd if you're not familiar with it. Not trying to be condescending or anything just really dangerous tools we are working with here.
it have problem
wow !!! i can see the LG logo in my tablet !!!
but i can't run next step !!!
pushed power + volume up button but i never changed screen !!
This is written on the screen.
"boot certification verify"
please help me i copy 34 partition on SDcard after that what can i do? please answer , this does not work (( 8.) Press and hold power and volume up...If all went well, there is suddenly life to your paperweight!! Congratulate yourself and prepare for more fun... If nothing happened, revisit the above steps, more than likely something got flashed to the wrong partition.
Issue
Hello, I've successfully followed the tutorial until step 9. When i flash TWRP it reboots and comes back to the fastboot screen.
If I hold the vol+ button when it is booting, the download mode screen flashes for a second and then it comes back to the fastboot.
I haven't been able to to anything else and would be very grateful if someone could help me with this.
Apparently there is no bootloader so it is stuck
I attached a picture of my screen
LG G Pad 7.0 V400
Is there a way to unlock Qualcomm 9008 from LG V400?
Finally my dead tablet went into fastboot mode.
Except windows cannot find a fastboot driver and fastboot command can't locate the device either. Any suggestions?
Related
How to Access HPA
How to access HPA Partiton and extract all driver
Hello all.
I need Recovery Partition on English.
I talk with Pof he say that me must English Recovery partiton.
Please Send to my.
Thanks in advance!!!
I have sent the copy of my HPA partition to danielherrero which was hagving the same problem as you, and he could recover his vista with it, the problem is that my recovery partition installs a Spanish language Vista, which will not be good for you (as you might not understand spanish), so if someone could dump an HPA in english, this would be useful to people who lost it.
Instructions to dump and restore the recovery partition are on my blog:
http://pof.eslack.org/blog/2008/04/...re-the-vista-recovery-partition-on-htc-shift/
I can if acess to FTP/HTTP server for upload a Image and all software for HTC Shift and access for all people needet
pof said:
I have sent the copy of my HPA partition to danielherrero which was hagving the same problem as you, and he could recover his vista with it, the problem is that my recovery partition installs a Spanish language Vista, which will not be good for you (as you might not understand spanish), so if someone could dump an HPA in english, this would be useful to people who lost it.
Instructions to dump and restore the recovery partition are on my blog:
http://pof.eslack.org/blog/2008/04/...re-the-vista-recovery-partition-on-htc-shift/
Click to expand...
Click to collapse
hello
i dont mind doing that on my english shift..ive had quick look at the page discribing how to do it but being a bit of a thicko it would great if you could send step by step destructions for me..i have the capability of loading it onto external drive where i could give you access to upload..please advise me if you wish
pof said:
I have sent the copy of my HPA partition to danielherrero which was hagving the same problem as you, and he could recover his vista with it, the problem is that my recovery partition installs a Spanish language Vista, which will not be good for you (as you might not understand spanish), so if someone could dump an HPA in english, this would be useful to people who lost it.
Instructions to dump and restore the recovery partition are on my blog:
http://pof.eslack.org/blog/2008/04/...re-the-vista-recovery-partition-on-htc-shift/
Click to expand...
Click to collapse
Yes, It saved my shift from SAT and several weeks out of home. Thanks again Pau
pd: Remove SD when dumping/restoring....
It takes 4 hours to dump or restore.
Pau....Maybe when I copied your fist MB did the trick?
plasticplanet said:
hello
i dont mind doing that on my english shift..ive had quick look at the page discribing how to do it but being a bit of a thicko it would great if you could send step by step destructions for me..i have the capability of loading it onto external drive where i could give you access to upload..please advise me if you wish
Click to expand...
Click to collapse
Basically you need:
~1Gb USB stick
~3,5 Gb of free space on your Vista partition
1) Install Slax on the USB pendrive, follow instructions here:
http://www.pendrivelinux.com/2006/09/20/all-in-one-usb-slaxzip/
2) Reboot your Shift
3) Press Fn+F10 to choose the boot device, select USB pen drive
4) Slax boot menu will appear, choose the first option (KDE)
5) Open a Konsole (Terminal program), right next to the "K" menu in the menu bar.
6) Type the following command:
Code:
# dd if=/dev/hda of=/dev/hda1/shift-vista-recovery.bin bs=1 skip=36773560320
7) This will last about 4 hours, keep your Shift on charger and wait until it finishes. When it finishes you'll see something similar to this:
Code:
3226976256+0 records in
3226976256+0 records out
3226976256 bytes (3.2 GB) copied, 11938 s, 270 kB/s
8) Now reboot into Vista again, the backup of the HPA holding the vista recovery will be in c:\shift-vista-recovery.bin
9) Zip or Rar the 'shift-vista-recovery.bin' file and upload it somewhere, keep in mind this is a big file so you might want to split it in several volumes before uploading it.
10) There is no 10
That's all, feel free to ask if some point is not clear enough.
On Privet messegi send to Pof and plasticplanet FTP access for upload a HPA Partition on English or ES.
pof said:
6) Type the following command:
Code:
# dd if=/dev/hda of=/dev/hda1/shift-vista-recovery.bin bs=1 skip=36773560320
7) This will last about 4 hours
Click to expand...
Click to collapse
not really 4 hours, for me that only did 98MB in 4 hours, and I had to use /mnt/hda1 anyway.
so tell me why is bs set to 1?
is bs=16384 fine? because that's how i did it in the end.
any way to verify the contents?
P.S: oh yes and my shift is hardspl'ed man!!
Probably I am in wrong but that command is dumping the last 3GiB of hda disk to the first partition of the same partition. Wouldnt be safer to dump to the sd or a usb pen?
no, the source is /dev so the hw device, like the whole hdd on windows
and the dest is /mnt/hda1 so the partition like C: on windows
the HPA "partition" is not part of the visible partition. no risk....
and the proper and FAST command is (if you are using the slack usb distro that pof linked to in his description) :
dd if=/dev/hda of=/mnt/hda1/shift-vista-recovery.bin bs=16384 skip=2244480
I assume similar method works for copying it back (the point is bs=16384).
if you want to be sure your shift has a partition of the exact same size, then read dmesg until you find the HPA (host protected area) information, should say what it said for pof and for me:
sda: Host Protected Area detected.
current capacity is 71826615 sectors (36775 MB)
native capacity is 78126048 sectors (40000 MB)
sda: Host Protected Area disabled.
sda: 78126048 sectors (40000 MB), CHS=16383/255/63
(ignore the "sda" part of course)
someone downloaded the backup I uploaded and confirmed it works.
cmonex said:
so tell me why is bs set to 1?
is bs=16384 fine? because that's how i did it in the end.
Click to expand...
Click to collapse
"bs" was set to 1 because I was too lazy to do the maths
Yes, you can increase it as long as you change the "skip" part too.
I have a problem.
I have two shift devices, one got screwed trying to install ubuntu MID and the other one is fine
I've tried your method with dd to the to copy the recovery partition from the working shift however it always fails during the fn f3(same failure that I got even before restored the image). IT starts the restore but fails somewhere along the line at 2%.
I noticed my hpa is at a slightly different location to yours using dmesg. Probably because it has office in it. How do I calculate the seek/skip
Also I tried doing a dd from higher on the drive just to see if I can atleast pick it up as excess got the same error.
Any help guys
btw good work on everything else you all have done
ok i got it..you guys were slightly off in your calculations so i wasn't sure that the address you got was by 512. Anyhow I have the .bin dump for anyone who needs it for the vista with office demo or those who partition size is different to that of the above postings. I also took it a little higher just to ensure i don't miss any of the partition
BTW posting from the previously bricked shift
Could you please stick this thread.
pof
Could you please stick this thread too. It has a lot of useful information.
Thanks
Ram
Hi there
if someone have a german Recovery partition Image for me, please let me know
My new HTC Shift has a Recovery Partiton but don´t boot with this. Don´t know why.
Maybe a recover of this partition may be work
But only for testing, i have made (before starting the Shift first time) a complete Acronis Image
I have a somewhat related question. I've basically busted my Vista recovery partition, long story short, I decided to try out ubuntu mid and didn't realize it was going to wipe my whole hdd (installed on my other laptops the regular images of ubuntu hardy and it asked me to specify partitions etc., but the mid didn't and I was half awake or vice versa).
I have now installed XP, and even though ubuntu mid appears to have wiped the HPA, it is still hidden from windows. I don't plan on going back to Vista (if I have to, I will just throw the thing out, xp just gave it a new lease on life). Is there a safe and easy way to unhide the hidden partition and use it, without having to install linux and without affecting my XP install (took too long to get it running and I'd rather give up the 3GB than have a go at it again, at least not until I really have to)?
I suppose I managed to unhide it, whiped it out and put it together with the rest of my HDD. Though now I used about 3GB with Acronis and created my own hidden/protected partition with XP completely set-up and some essential software. Worked like a charm.
Restore recovery partition
What is the correct command for restoring the rescovery partition bin file?
I used "dd if=/dev/hda of=/mnt/hda1/shift-vista-recovery.bin bs=16384 skip=2244480" to create the dump file.
I need you.
Hello.
I had installed ubuntu 8.04 and it run good, but the resolution was horrible.
With vista, the virtual resolution permits work without external panel, for not very long time, of course.
I don't now what i do wrong, and now i can't recovery the Vista by the recovery partition. I have installd a Vista Bussiness from a copy and with the activation key from my htc shift and it works good.
I wouid like recovery the recovery partition of my htc.
know you where i could get the "shift-vista-recovery.bin" image from?
thanks. and "help" me please
Hello, I've spent several hours searching a solution for this problem, both on this forum as well as others. But still unable to find one I try my luck here.
This is the case:
U8800 bought in Sweden a couple of weeks ago. Installed SuperBoot r1 and CWM 4.0.0.5 Perfect Recovery from XDA forums. Installed Oxygen 2.2.2 r4, worked fine until yesterday. When it got stock at the screen lock. Pulled battery and then it was stuck in a boot loop showing only the IDEOS-logo. Tried to get into recovery with Vol+ and power. But still only gets to IDEOS-logo and then reboot after about 10 seconds.
I'm able to get into bootloader (pink-screen) by Vol+, Vol- and Power. Have tried to replace boot.img and recovery.img with others (original backup, CWM 5.0.2.3) in both Ubuntu 11.10 and Win 7). But still unable to reach recovery. And next time I start bootloader and check it's still the same boot.img and recovery.img as it was before I replaced them.
Seems like I'm unable to write to image folder somehow. It looks good when I disconnect it from the computer. Have tried "safe removal" in both Ubuntu and Windows, no difference. Also tried to rename the files to boot_backup.img and recovery_backup.img and then put the new files in there. But next time I start bootloader they are once again restored to how they were before (same file size as before) and the renamed files doesn't exists any more.
Have also tried to install B136 stock ROM via bootloader, looked good at first but when it was finished it said "Installation failed" (or something similar)...
Read somewhere modding the build.prop could cause boot loops, but I haven't touched that and therefore doesn't have any backup of it either.
Any ideas?
Yep, it looks like your bootloader may be corrupt...Do the following:
Boot the phone in Bootloader (pink screen) by pressing Vol+, Vol- and Power and connect the USB cable. Copy all the files you can find on that partition (this will be your backup) and format the partition with FAT32 file system, create a folder named "image" and copy the following files on there.
EMMCBOOT - http://www.mediafire.com/?lb6ifvgk72iru4a
AMSS.MBN - http://www.mediafire.com/?d6r45q6p5gew59v
Recovery.img - http://www.mediafire.com/?57njygc8oianjac
Boot.img - http://www.mediafire.com/?6d5i0714a7o9z97
Once you've done this, take the battery out and boot into Recovery and flash a new Rom (VOL+ and Power.)
Let me know how this goes...
Thank you very much for your help!
However when I try to format the partition windows says it couldn't complete the format. Tried both to right click > format and disk management > format. FAT32/std fast format as well as regular/slow. Neither work. If I do a regular format it goes at normal rate up to 100% and then says the disk isn't formatted...
I don't know if I dare to remove the partition and make a new in disk management, feels like I would screw something else up then?
Any tips?
Have tried to format in Ubuntu 11.10 as well, with the standard tool it didn't complain, but it didn't format it either. Installed GParted and tried that, it did seem to work and said it had successfully formatted it. But yet the image-folder still remains on the boot partition...
Run a systemcheck with the disk management in Ubuntu and it said the file system was OK.
I'm almost out of ideas now...
I don't think you're actually formatting the drive as the "image" folder should be gone once the format is done.
Try using a windows PC, I know that Gparted and Ubuntu can be a bit tricky sometimes...
Also, you've definitely installed the drivers for the cable?
On Windows 7 the drivers are being automatically installed, so maybe you should try that...
I've tried Windows 7 several times (the only Windows I use). It's very weird the files just wont go away. I have taken Shift+Del on the image folder several times and they are removed just as any other files on the computer. Then the next time I connect it the very same files (58 MB) are back! When I do a format the computer shows the disk empty, but when the error window comes up the files are back... In ubuntu GParted shows the partition empty, but after a re-scan the 58 MB are back...
Can try to see if I can make a screen recording to see if I'm doing it wrong somehow.
Thanks for your support!
I have a short screencast on screenr illustrating the problem, but unable to post a link I'll try to describe it.
screenr(dot)com(slash)WMls
Pastasallad said:
I have a short screencast on screenr illustrating the problem, but unable to post a link I'll try to describe it.
screenr(dot)com(slash)WMls
Click to expand...
Click to collapse
Seen your screencast...it's a bit unclear. Sent you a PM, hopefully we'll be able to sort this out.
Same problem here h ttp//forum.xda-developers.com/showthread.php?t=1318647
The bootloader seemed to be beyond rescue. Nothing seemed to help, tried several drivers and computers. But the partition seemed locket somehow, couldn't replace the files. Tried to flash in stock ROM 136 and 138. Both failed unless you removed the cust update file. Then it succeeded, but still bootloop when it restarted.
So the phone is now returned for service.
Thanks katu2006 for all the help!
I have a sprint phone that can only get into bulk mode. I followed this guide: http://forum.xda-developers.com/showthread.php?t=2582142 and everything works fine except for the dd command. When I write to a partition (well at least aboot and recovery since those are the only 2 I've tried) and then cmp the image to the partition I just wrote to only the first 64k bits match out of the 1MB partition. I've tried ubuntu fatdog and gparted and all have the same problem. What's weirder is that before I borked my phone I used the Zv8_aboot.img that is around and when I just try to rewrite that image it is still only the first 64k bits that match so it's like I'm not writing to the write part of the partition because the img and the partition should match.
I didn't make a backup of the aboot partition before doing all of this so if anyone else has a sprint phone with a ZV8_aboot.img in the aboot partition, and has access to bulk mode can you use dd to make an image of the partition so that I can try to at least get my aboot back? After that I'll try this: http://forum.xda-developers.com/showthread.php?t=2708466&page=2 to get into fastboot.
Also, for anyone else that has no download mode and no recovery you can get into bulk mode by going into factory reset mode. I can't remember the exact button presses for that but after you are in and you hit power 3 times your phone shouldn't reset (you might have to have a custom recovery installed for that to be the case though) but it will end up going into bulk mode; it did for me anyway.
sorry for responding to my own thread, the edit of the 1st post just wasn't saving
Alternatively does anyone know an alternative to DD?
Update:
Tried on different computer, tried with my tongue sticking out at a 33 degree angle, tried with ddrescue, always the same thing..... fts
Update
I finally looked at the entire hex file for aboot and I found that it seems to write everything fine except for the bits between 65537 and 122880, 64k-120k or sectors 129 to 240 given 512bit sector sizes. This seems really odd. I think my only hope would be getting a good aboot from someone's sprint and writing only to the other sectors and not 129 to 240. Even then I might have to figure out if 129 through 240 aren't changed or are somehow purposefully scrambled when written to through hardware.... this is so lame.
So if you have a sprint phone with a zv7 or zv8 aboot and can get into bulk mode I'd very much like a copy of your aboot.img when you do a raw copy of it using dd.
going to reply to myself cause
I need to help someone in the development forum, so I need 6 more posts to post there
more self posting
self posting is natural there's no need to be ashamed
man this is annoying why 10 posts
If anyone can help me to create a loop back device that maps to the sectors in question, I'd appreciate the help.
ya, i setup a loop back device
losetup -o 65536 --sizelimit 57344 /dev/loop3 /dev/sdi5
Omg it has worked so far!!!!
setting up a loopback device over the sectors that weren't writing correctly has so far worked for aroot... I think I want to do the same for the recovery and see my phone actually boot first though
Works but.....
This is going to take forever, I guess I better figure out how to right scripts since I'm manaully putting in 4 commands to go 64k at a time out of 16MB.... fml
SOLVED
I did it my way..... oh franky
How to unbrick by sdcard from 9008 without QFIL
This method works ONLY for qualcomm devices (ANY non-UFS!!) which are already in QDL/EDL/9008 mode!
This method does *not* work for:
Samsung devices in general.
Details:
Samsung is doing things completely different while ofc a qcom based Samsung works with the same principal as "normal" devices. Just the process of building an hnbrick sdcard is different as you can get the pit (partition list) by heimdall but not a flashable gpt. Instead search for "sboot sdcard unbrick" or "sboot sdcard <your model>" . The important part here is "sboot" as that one will be loaded by the iROM when flashed properly (+other stuff).
UFS devices (so not for the G5 or later).
Details:
9008 bricks are not fixable on UFS NAND devices by booting from an SD card. The boot path is stored in QFPROM (on the CPU) and it is something like /dev/block/sdb or /dev/block/sde. On eMMC devices, the boot path is /dev/block/mmcblk0. If you have a 9008 brick, the SD card is seen as /dev/block/mmcblk0 so the phone will boot from it on an eMMC device since that IS the boot path. There is no way to make the SD card appear as /dev/block/sdX. And there is no way to change the boot path once you have a 9008 brick without a firehose. If you have a signed firehose, then you can fix your phone without needing an SD card As for cross flashing. I checked the RSA signature for the H930, H932, H933, and US998 and they are all different. If you flash any of the signed firmware (xbl, abl, hyp, modem, etc) from one of those devices, then you have a 9008 brick and no way to fix it yourself.I didn't bother checking the Verizon or Sprint models since they are even more locked down than the H932 is, but it appears from reading this thread that they have the same key as the US998 (I am not going to waste my time checking).-- Brian
Click to expand...
Click to collapse
If your device is connected and not detected like that the external sdcard method will NOT work for you.
On the LG G4 you can force the sdcard mode by following post #2 . I guess every device has a way to force that mode so google is your friend.
Hint --> If you have no sdcard and own a H815 device (only then) you can make use of these validated QFIL process here
Requirements
1) Ok first of all what you need is Linux. I highly recommend FWUL ( https://bit.do/FWULatXDA ) but any Linux is sufficient if you can handle it.
2) LG models only: you need the latest SALT version ( https://bit.do/SALTatXDA ) which is already included since FWUL v2.5 (one of the reasons why I recommend FWUL).
If you decide to use FWUL and start SALT it should prompt you when an updated SALT version is available. To be sure: just click the Update button in SALT once started.
3) you need an external sdcard which is (to be sure) bigger then your internal storage (the sdcard must have the same size of your internal storage! so in theory a 32GB card should work fine but some cards are sold as 32GB but the real size is less , i.e. 29 GB). Thats the most critical part here as the GPT will be invalid if it does not fit with the sdcard. you can't edit the GPT though as then internal checksum may fail and so it will not work to boot from the sdcard. so ensure you have a bigger sized sdcard to workaround any issues related to this.
4) Another important requirement for that external sdcard is: speed! If you want to ensure that you do not struggle ensure it is at least a class 10 card with UHS. It MIGHT work without UHS and it MIGHT work even on slower cards down to class 4 but when the storage is too slow the device rejects to boot from it as it ran into timeouts and so marking the sdcard as "not good enough" to boot from it.
Of course you can first try a lower speed sdcard but if you encounter issues here then it is likely related to the speed of the sdcard.
5) you need a 100% matching firmware (e.g a KDZ on LG's) for your device model - and very important: with a matching ARB of your current installed firmware!
If your current installed firmware has a higher ARB then the one you flash on the sdcard it will NOT work!
Find out what ARB means here https://bit.do/antirollg4
Steps
1. Boot FWUL (or ur personal Linux)
2. LG models only: Start SALT - ensure that it is v3.5 or higher
3. Extract the firmware file (e.g KDZ) but usually not all partitions are needed - just the bootloader stack
(depends on your device - the following is for any LG G4 model):
Primary GPT
sbl1
aboot
pmic
rpm
tz
laf
sdi
hyp
If you have not all or any of these (first check the note about UFS above) then you must identify your bootloader stack first.
A good start for this is here: https://lineageos.org/engineering/Qualcomm-Firmware but you may have to just try and error here.
For a quick & dirty try: flash every partition which is smaller then 150 MB (i.e. leave out system, cache, userdata and such).
4. Clean dmesg by opening a terminal and type:
Code:
sudo dmesg -c >> /dev/null
5. Connect your external sdcard to FWUL
6. Type this in the terminal:
Code:
dmesg
and find the connect messages there pointing to the device name. usually you see something like "mmcblk0" but sometimes it's different named like sdc or sdd or similar.
We do not need the pXX here. So if you see mmcblk0p1 we need only mmcblk0. If you see a sdc1 or sdd1 we just need sdc or sdd without the number.
7. The device name is needed now! Ensure it has the correct size by typing this in the terminal:
Code:
sudo fdisk -l /dev/mmcblk0
(replace mmcblk0 if you your device is named different in step 6).
This is important because the next step will erase your sdcard completely!
All your data get lost!
So if you choose the wrong one you may overwrite your PC storage in worst case! So double check this before proceeding.
You can do so by disconnecting the sdcard and if the command in this step gives a message about the device cannot be found - connect device again and re-do the above command. if it shows then again your device all is fine
8. Now flash the GPT (partition table) to your device in a terminal:
Change into the folder where you extracted the backup. If you leaved the default on SALT it's /tmp/extracteddz:
Code:
cd /tmp/extracteddz
sudo -s
dd if=PrimaryGPT.gpt of=/dev/mmcblk0 (replace mmcblk0 if you your device is named different in step 6)
sync
hint: do not close the terminal
9. Disconnect the sdcard and connect it again
10. Now flash the rest in a terminal:
First check if the GPT has been flashed fine:
Code:
ls -la /dev/disk/by-partlabel/
if you get nothing as a result or an error message something went wrong. Go back to step 4!
Move to the folder where you extracted the backup. If you leaved the default on SALT it's /tmp/extracteddz:
Code:
cd /tmp/extracteddz
LG G4 - ONLY - Flashing instructions for locked or official unlocked phone (If you UsU'd your device skip this!)
Code:
dd if=sbl1.bin of=/dev/disk/by-partlabel/sbl1
dd if=aboot.bin of=/dev/disk/by-partlabel/aboot
dd if=hyp.bin of=/dev/disk/by-partlabel/hyp
dd if=pmic.bin of=/dev/disk/by-partlabel/pmic
dd if=rpm.bin of=/dev/disk/by-partlabel/rpm
dd if=tz.bin of=/dev/disk/by-partlabel/tz
dd if=laf.bin of=/dev/disk/by-partlabel/laf
dd if=sdi.bin of=/dev/disk/by-partlabel/sdi
[B][COLOR="Red"][SIZE="4"]sync[/SIZE][/COLOR][/B]
Do [B][U]not forget[/U][/B] that last ("sync") command!! Otherwise it will very likely not work!
LG G4 - ONLY - Flashing instructions for an UsU'd device
Besides the KDZ extract you also need to grab the UsU unlock zip of your device model first then do this:
Code:
dd if=sbl1.bin of=/dev/disk/by-partlabel/sbl1
dd if=hyp.bin of=/dev/disk/by-partlabel/hyp
dd if=pmic.bin of=/dev/disk/by-partlabel/pmic
dd if=rpm.bin of=/dev/disk/by-partlabel/rpm
dd if=tz.bin of=/dev/disk/by-partlabel/tz
dd if=sdi.bin of=/dev/disk/by-partlabel/sdi
dd if=laf_UsU.img of=/dev/disk/by-partlabel/laf
dd if=aboot_UsU.img of=/dev/disk/by-partlabel/aboot
dd if=rawres_UsU.img of=/dev/disk/by-partlabel/raw_resources
[B][COLOR="Red"][SIZE="4"]sync[/SIZE][/COLOR][/B]
Do [B][U]not forget[/U][/B] that last ("sync") command!! Otherwise it will very likely not work!
11. Now everything is prepared. Take out your sdcard. Take out the battery and disconnect cable. Plugin the external sdcard. Put battery back.
Start the device in fastboot mode and use fastboot flash partition imagename.img
If there is no fastboot possible open the download mode.
For example on the LG G4:
Press volume up (only this) and keep it pressed.
Then connect USB cable while still keep the pressure on volume up for 20 seconds.
The download mode should come up.
Congrats you can now use e.g. LGup (or for Samsung, ODIN etc) for unbricking by flashing a regular firmware on it (beware of the ARB again).
Have fun! :highfive:
Support / TG group
Of course in this thread but also by Telegram. I have created a generic group for all stuff around Android : here.
Note:
be polite, don't ask to ask, be patient(!), respect the timezones, help others.
,-
Force SDCARD boot
How-To force booting from sdcard (LG G4 only) (e.g. when the device is NOT in 9008 / QDL mode)
You may know the 2-pin-bridge method which can enforce the 9008/QDL mode (on the back of the main board which is shown when disassembling the back cover).
Now you may think: you can enforce that mode by bridging these pins and then you could boot from sdcard as this guide here says 9008 mode is a requirement.
The answer is: NO. This will NOT work!
But there seems to be a way (which I personally never have tested!) to force that sdcard boot by doing the following.
Be aware: You do this on your own risk! Do not cry if something is failing/destroyed/whatever. Its totally up to you to proceed or not but its on your own risk like always when following guides.
prepare the sdcard as described in the above guide
insert the sdcard in the device
remove battery of the device
unplug usb cable
disassemble the back cover by loosen all screws
disassembling the mainboard like described here: fixit guide
on the FRONT of the mainboard find 5 (DAT0) and 6 (GND) as shown in the picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bridge these both and while bridging plugin the usb cable - WITHOUT TOUCHING anything with your fingers/body/soul on the mainboard!!!!
Keep thumbs pressed.. it may work if you flashed the correct files, with a matching ARB, in a correct way and [fill-on-on-whoever-u-believe-in] is with you
marzsalim said:
5. Connect sdcard with mobile ? Or sdcard just connect to pc? Please reply to me
Click to expand...
Click to collapse
Like I wrote to FWUL so yes to your PC where FWUL is running
Sent from my LG-H815 using XDA Labs
it seems either ubuntu 17.10 messes something up or salt 3.6-6 stable can't find partitions and i've downloaded two different h812 kdz.
commandervadeo said:
it seems either ubuntu 17.10 messes something up or salt 3.6-6 stable can't find partitions and i've downloaded two different h812 kdz.
Click to expand...
Click to collapse
This is happening to me too?
commandervadeo said:
it seems either ubuntu 17.10 messes something up or salt 3.6-6 stable can't find partitions and i've downloaded two different h812 kdz.
Click to expand...
Click to collapse
Shepxda said:
This is happening to me too?
Click to expand...
Click to collapse
upload the log after extracting a KDZ:
advanced menu -> Logfile -> upload button -> share the link
steadfasterX said:
upload the log after extracting a KDZ:
advanced menu -> Logfile -> upload button -> share the link
Click to expand...
Click to collapse
No, you see, when you select the KDZ and the location to extract to, no partitions are available to choose from. It's just a blank page
Shepxda said:
No, you see, when you select the KDZ and the location to extract to, no partitions are available to choose from. It's just a blank page
Click to expand...
Click to collapse
Yes. After this do what I said above. Give me the log.
Sent from my LG-H815 using XDA Labs
Hi, I have an H811 bricked this way, as it is bricked, I cannot check antirollback on phone's android.
On the rear label (the one with serial number near to battery) I can see model (H811) and it says H/W 1.0, S/W V10d
I search and saw that there is not V10d kdz for H811, is that data useful? Which kdz will be the best choice to use?
birry said:
Hi, I have an H811 bricked this way, as it is bricked, I cannot check antirollback on phone's android.
On the rear label (the one with serial number near to battery) I can see model (H811) and it says H/W 1.0, S/W V10d
I search and saw that there is not V10d kdz for H811, is that data useful? Which kdz will be the best choice to use?
Click to expand...
Click to collapse
do you remember at least if you had installed Android marshmallow or lollipop? Any chance that you have made a TWRP backup in the past? Or did you never unlocked your device?
Sent from my LG-H815 using XDA Labs
steadfasterX said:
do you remember at least if you had installed Android marshmallow or lollipop? Any chance that you have made a TWRP backup in the past? Or did you never unlocked your device?
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Never upgraded Android, I guess it was lollipop. No backups or unlock also, it just bootlooped and I bricked it trying to install a H812 image with lgup (I know which image I tried if it is useful, I remember editing a value because lgup was refusing to install h812 image on the h811, I didn't find h811 image for lgup bootloop flashing fix).
This was my reference when I destroyed the phone [emoji14]
https://www.reddit.com/r/lgg4/comments/45gfg2/dae_g4_series_msm_big_core_disable_tool_guide/
birry said:
Never upgraded Android, I guess it was lollipop. No backups or unlock also, it just bootlooped and I bricked it trying to install a H812 image with lgup (I know which image I tried if it is useful, I remember editing a value because lgup was refusing to install h812 image on the h811, I didn't find h811 image for lgup bootloop flashing fix).
This was my reference when I destroyed the phone [emoji14]
https://www.reddit.com/r/lgg4/comments/45gfg2/dae_g4_series_msm_big_core_disable_tool_guide/
Click to expand...
Click to collapse
well..omg..
ok so the h812 has no ARB. The h811 has. Here is the reason for your hard brick. Do not cross flash random files without knowing what you do really.
Start with 10h which is ARB 1 for the h811: http://downloads.codefi.re/autoprime/LG/LG_G4/H811/H81110H
download the single files or the KDZ and use SALT to extract. then follow the rest of the guide above.
if that fails to boot go on with ARB 2 : http://downloads.codefi.re/autoprime/LG/LG_G4/H811/H81110N
I would not recommend to go further then that as u otherwise will increase your ARB for sure.
The next step if that all above still fails would be to use QFIL with proper files for the h811 but beware: there are QFIL files marked as h811/h815/... which in fact are converting your device to a ls991. Best is to search XDA for other users reports which files gave them a good result.
Last but not least if your device is ARB 3 or higher all the above will fail (including the QFIL method) and your only chance to bring back life is the sdcard method described here but using ARB 3 or higher files.
.
I hate to say it but Im here....
LGG4 - 815eur - new frankenphone (new to me, chinese refurb) - received jan
never had a sim in it. only kept it on to see how long the battery would last in idle mode (airplane mode on, no wifi active)(14 days!) - LGUP to MM
still stock - no google play services installed yet, I was waiting for the UsU (woohoo steadfasterX!!, where do I send my bounty contribution?)
I was downloading all the required files for FWUL / Virtual Box last night, I was going to spend the afternoon getting to know the process/Arch linux, before attempting to mess with my phone... I was adjusting the pull down notification settings and it froze.
I waited till this AM, hoping maybe it would sort itself out. NOPE. Battery at 0.
Im at the logo bootloop with pulsing blue LED.
I have read the entire thread, I wanted to make sure that this workaround is the proper "fix" for this type of bootloop.
I was at v20k IIRC and I know for a fact my ARB was 0.
Im not sure where to dl the required files from several sources Ive tried, dont leave me feeling confident its a trusted source.
Any thoughts on what may have happened?
cheers
ac
steadfasterX said:
well..omg..
ok so the h812 has no ARB. The h811 has. Here is the reason for your hard brick. Do not cross flash random files without knowing what you do really.
Start with 10h which is ARB 1 for the h811: http://downloads.codefi.re/autoprime/LG/LG_G4/H811/H81110H
download the single files or the KDZ and use SALT to extract. then follow the rest of the guide above.
if that fails to boot go on with ARB 2 : http://downloads.codefi.re/autoprime/LG/LG_G4/H811/H81110N
I would not recommend to go further then that as u otherwise will increase your ARB for sure.
The next step if that all above still fails would be to use QFIL with proper files for the h811 but beware: there are QFIL files marked as h811/h815/... which in fact are converting your device to a ls991. Best is to search XDA for other users reports which files gave them a good result.
Last but not least if your device is ARB 3 or higher all the above will fail (including the QFIL method) and your only chance to bring back life is the sdcard method described here but using ARB 3 or higher files.
.
Click to expand...
Click to collapse
Cool!! It worked like a charm with H81110H file :laugh::laugh::laugh:
Now I can run it into download mode and I could see that info on SALT:
Device model: LG-H811
Firmware (laf): H81120v
Firmware (system): LGH811AT-01-V20v-310-260-APR-25-2017-ARB03+0
Carrier: TMO
Country: US
UsU: no
GPT compatibility: H811
LAF protocol: 1000001
AntiRollBack: 3
I don't want to make a mistake so now that it boots in download mode I will wait for options, which is the best choice now? Updating it with a .tot with LGUP (for the bootloop) or installing other rom (perhaps one with bootloop workaround)
Thanks for your great work!
Vishnuisgod said:
I hate to say it but Im here....
LGG4 - 815eur - new frankenphone (new to me, chinese refurb) - received jan
never had a sim in it. only kept it on to see how long the battery would last in idle mode (airplane mode on, no wifi active)(14 days!) - LGUP to MM
still stock - no google play services installed yet, I was waiting for the UsU (woohoo steadfasterX!!, where do I send my bounty contribution?)
I was downloading all the required files for FWUL / Virtual Box last night, I was going to spend the afternoon getting to know the process/Arch linux, before attempting to mess with my phone... I was adjusting the pull down notification settings and it froze.
I waited till this AM, hoping maybe it would sort itself out. NOPE. Battery at 0.
Im at the logo bootloop with pulsing blue LED.
I have read the entire thread, I wanted to make sure that this workaround is the proper "fix" for this type of bootloop.
I was at v20k IIRC and I know for a fact my ARB was 0.
Im not sure where to dl the required files from several sources Ive tried, dont leave me feeling confident its a trusted source.
Any thoughts on what may have happened?
cheers
ac
Click to expand...
Click to collapse
This unbrick will work only when you bricked your phone. It's not an ilapo fix and your description sounds like one. Your best chance is using a modded boot image with just 4 cores enabled. That requires an unlocked phone though.. There is a guide from me to create such boot images here on XDA.
birry said:
Cool!! It worked like a charm with H81110H file :laugh::laugh::laugh:
Now I can run it into download mode and I could see that info on SALT:
Device model: LG-H811
Firmware (laf): H81120v
Firmware (system): LGH811AT-01-V20v-310-260-APR-25-2017-ARB03+0
Carrier: TMO
Country: US
UsU: no
GPT compatibility: H811
LAF protocol: 1000001
AntiRollBack: 3
I don't want to make a mistake so now that it boots in download mode I will wait for options, which is the best choice now? Updating it with a .tot with LGUP (for the bootloop) or installing other rom (perhaps one with bootloop workaround)
Thanks for your great work!
Click to expand...
Click to collapse
You're referring to what TOT? The one containing just the aboot?
Sent from my LG-H815 using XDA Labs
steadfasterX said:
This unbrick will work only when you bricked your phone. It's not an ilapo fix and your description sounds like one. Your best chance is using a modded boot image with just 4 cores enabled. That requires an unlocked phone though.. There is a guide from me to create such boot images here on XDA.
You're referring to what TOT? The one containing just the aboot?
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Yes, anything that patches the bootloop. I am a bit confused with partition structure, the cpu workaround is done editing something in the aboot partition?
I just would like to patch the bootloop (I prefer to have the four tiny cores enabled instead of just one as it normally does and installing stock Rom).
birry said:
Yes, anything that patches the bootloop. I am a bit confused with partition structure, the cpu workaround is done editing something in the aboot partition?
I just would like to patch the bootloop (I prefer to have the four tiny cores enable instead of just one as it normally does and installing stock Rom
Click to expand...
Click to collapse
There are 2 patches available. The one with tot and the boot image one.
The TOT one which is something between 4 and 10 MB contains just the aboot one and disables the cores in the aboot itself.
The boot image one is made in the kernel cmdline
Both have the same effect.
The difference : the TOT aboot fixes it permanently (as long as you don't reflash a kdz/tot again). So you can flash custom ROMs without needing to care about it.
The boot image adjustment instead does not touch your aboot but needs to be done on ever new boot image you want to use.
Sent from my LG-H815 using XDA Labs
So then I have the patch that just contains the aboot partition (files are of exactly 4mb)
Downloaded from here: https://www.reddit.com/r/lgg4/...m_big_core_disable_tool_guide/
The problem is that there are several models in the file that I downloaded from there but H811 is missing, I cannot find a tot with just aboot for H811, is this really available? I would prefer to write a tot with just aboot that leaves all cores enabled and the faulty ones disabled, not just one core enabled as those tots does.
birry said:
So then I have the patch that just contains the aboot partition (files are of exactly 4mb)
Downloaded from here: https://www.reddit.com/r/lgg4/...m_big_core_disable_tool_guide/
The problem is that there are several models in the file that I downloaded from there but H811 is missing, I cannot find a tot with just aboot for H811, is this really available? I would prefer to write a tot with just aboot that leaves all cores enabled and the faulty ones disabled, not just one core enabled as those tots does.
Click to expand...
Click to collapse
Afaik there is none for the h811 and I highly recommend to not use any of the others to avoid bricking your phone again. So it seems you're stuck with modifying boot images
Sent from my LG-H815 using XDA Labs
Ok then, I will try this firmwares: https://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
Consider that ARB is 3, which firmware would be the correct one to use?
Edit: now after a pair of boots it started to get download mode in a random way, sometimes it does and sometimes it does not, could it be because I used a ARB 1 extrated kdz?
Hi,
I do have some MK903V TV Sticks that came with Android 4.4.2 and some with Android 7.1.
I thought I could potentially just clone the complete flash from one device to another using AndroidTool v2.3, but that failed.
I used "ExportImage" from "Advanced Function" to export the flash from 0 to 0x00E90000. I then selected the exported file and flashed it to Address 0x00000000 and name "system" using the "Download Image" tab.
The AndroidTool said it uploaded the file and verified okay. But after that I re-exported few blocks from 0x0 and found that the flash was not overwritten. The device did not boot (no HDMI signal).
I re-exported the system partition and found that it wrote the full backup into the system partition instead.
So basically the Tool used the "name" column and completely ignored the "address" column?
Is there a way to just write the complete flash using AndroidTool v2.3 ignoring partitions? I basically just want to mirror a device to another.
Okay, so I guess I understood that "LOADER" is actually aware of all partitions on the device and also their use/format. The "Address" column seems to be ignored completely. I guess this is only relevant for "MASK ROM" mode devices?
I found out by trying to write to "parameter" partition, hoping it would write to 0x00. But instead it wrote into the first partition at 0x08 and properly wrote the header in front of it with the size of the written data.
So, I now know how to properly extract the "parameter" image from another device and I assume all other partitions can be simply dumped and written without any magic happening to them? But I need to write them partition by partition?
For my understanding... The LOADER mode / the green "Loader" row in AndroidTool is something that is not on the flash, right? But it obviously reads the flash and its partitions.
If I'm right, I cannot brick the device as long as I don't flash a different "Loader" (which I don't have anyways as I cannot extract it from another device).
But: When I mess up the "parameter", will LOADER mode still boot fine and allow me to rewrite "parameter"?
Is "Loader" always booting "uboot" next, which then decides on booting into "kernel" or "recovery" if "R" is pressed?
Okay, I have so many questions and I can't really find any documentation :/
So at least I'll continue my self conversation here.
The bootloader of the RK3288 - and I'm still not sure what exactly it is - has two modes, LOADER and MASKROM.
I think in LOADER mode it is aware of partitions and makes sure users can only flash data to specific partitions. However, you can also update the partitions (and other stuff?) by writing to "parameter", which is part of the first few blocks of the flash.
In MASKROM mode it is not aware of any contents of the flash and you can basically write over the complete flash. In this mode the AndroidTool will actually use the Address column to flash data (I think).
I'm not exactly sure what triggers MASKROM mode but I guess the bootloader boots MASKROM mode if it cannot find "valid" data on the flash.
For example
erases the Flash and IDB, which forces the device from LOADER into MASKROM mode.
I also found lots of instructions that tell you to short two pins on the NAND Flash chip of the device to trigger MASKROM mode. None of these instructions tell you why you do it and how it works, but I guess it just disables the Flash so the bootloader reads back all zeroes or anything like that?
I also cannot find any information what IDB is, what it stands for and where it is stored, but it seems to play an important role here :/
There are multiple Versions of the "bootloader". e.g. https://github.com/neo-technologies/rockchip-bootloader / https://forum.xda-developers.com/t/rk-bl-rockchip-bootloader-collection.3739510/ lists RK3288Loader_uboot_Apr182014_155036.bin, RK3288Loader_uboot_Apr212014_134842.bin, RK3288Loader_uboot_V2.17.02.bin, RK3288Loader(L)_V2.17.bin, RK32xxLoader(L)_uboot_V2.15_replace_ddr.bin
They obviously do some things differently, but I'm not sure if this is relevant for "normal" operation of the device or just if you need to do special things. e.g.
Running Android or Linux from an SD card on a RK3288 device - An easy way to dual boo
If you are interested in dual booting Android and Linux on your RK3288 device or you simply want to try a different Android ROM or Linux distro without flashing the device, then use this method of booting from an SD card. You will need a PC...
forum.xda-developers.com
says that RK3288Loader_uboot_V2.17.02.bin is required to boot from SD card. So earlier versions can't do that?
Can I flash these Loaders to any RK3288 device (I guess?) or are they device specific? Can I downgrade? Can I flash them in LOADER and MASKROM mode? Many things I don't understand properly...
The filenames usually contain "uboot". I guess that's not because they include uboot, but because the bootloader starts U-Boot from the "uboot" partition on a regular boot?