I don't respond for What-So-Ever done any damage to your Phone, You must accept this risk with yourself..
I want to share the method and discussion about This method. Is it possible we can use to fix qhsusb_bulk (qualcomm 9006) ..
Hi all,
I'm trying find a new method to fix brick qhsusb_bulk(qualcomm 9006) . First I need to do my phone has brick before.I don't the right way
how to make my phone has brick No Download Mode/Recovery/qhsusb_bulk(qualcomm 9006) to test and If I'm doing a wrong way this is a risk for me.
Today I try to make my phone has bricked by flash stock LP boot without Bump (My current firmware is D80230b) . Oh it's show qhsusb_bulk(qualcomm 9006) in device manager and so many drive show in my computer .But I can enter to recovery mode .I think it is enough to simulate how to fix brick without to use Ubuntu,Then try to fix by dd for windows it's working.Maybe this is a choice for people to fix brick without to use Ubuntu.
{
"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"
}
Require program
1. dd for windows
2. AOMEI Partition Assistant Standard Edition
3. Bump boot for D80230b
How to work
1. After install AOMEI Partition Assistant Standard Edition > Open it
you will see in picture as below
2. In picture above Disk1,Disk2 is a Harddrive in my computer Disk3 is a Harddrive in my phone
3. In disk3 we focus in File system is Fat16/Other/Ext4 or something that isn't Unallocated.We can mapping in G2 partition ex.
In picture FAT16 is a first partition has size 64 MB When we are mapping to G2 partition it is modem or boot partition is a number
7 in G2 partition in AOMEI Partition we can mapping as picture below
- D802 Partition
Number Start (sector) End (sector) Size Code Name
1 32768 163839 64.0 MiB 0700 modem
2 163840 165887 1024.0 KiB FFFF sbl1
3 165888 166911 512.0 KiB FFFF dbi
4 196608 197631 512.0 KiB FFFF DDR
5 229376 231423 1024.0 KiB FFFF aboot
6 231424 233471 1024.0 KiB FFFF rpm
7 262144 294911 16.0 MiB FFFF boot
8 294912 296959 1024.0 KiB FFFF tz
9 296960 296961 1024 bytes 0700 pad
10 327680 333823 3.0 MiB FFFF modemst1
11 333824 339967 3.0 MiB FFFF modemst2
12 339968 339969 1024 bytes FFFF pad1
13 360448 393215 16.0 MiB FFFF misc
14 393216 458751 32.0 MiB 0700 persist
15 458752 491519 16.0 MiB FFFF recovery
16 491520 497663 3.0 MiB FFFF fsg
17 524288 525311 512.0 KiB FFFF fsc
18 525312 526335 512.0 KiB FFFF ssd
19 526336 526337 1024 bytes FFFF pad2
20 526338 527361 512.0 KiB FFFF encrypt
21 557056 573439 8.0 MiB 0700 drm
22 573440 589823 8.0 MiB 0700 sns
23 589824 655359 32.0 MiB FFFF laf
24 655360 720895 32.0 MiB FFFF fota
25 720896 786431 32.0 MiB 0700 mpt
26 786432 787455 512.0 KiB FFFF dbibak
27 787456 789503 1024.0 KiB FFFF rpmbak
28 789504 791551 1024.0 KiB FFFF tzbak
29 791552 791567 8.0 KiB FFFF rct
30 819200 6488063 2.7 GiB 0700 system
31 6488064 7733247 608.0 MiB 0700 cache
32 7733248 7897087 80.0 MiB 0700 tombstones
33 7897088 7929855 16.0 MiB 0700 spare
34 7929856 8028159 48.0 MiB 0700 cust
35 8028160 60948479 25.2 GiB 0700 userdata
36 60948480 61071326 60.0 MiB 0700 grow
4. After we get information of partition we can use dd for windows to fix that partition
dd if=droidth-boot.img of=\\?\Device\HarddiskVolume306
I use all concept then make useful tool for fix qhsusb_bulk (qualcomm 9006)
[TOOLS] SRK Tool 2.0 - Tool for LG Mobile - 20150501
Or we can use command line from windows instead of AOMEI Partition Assistant Standard Edition 5.6
No need to use Ubuntu.This is a concept that we can apply to fix brick
Sure it will be useful for a lot of person! Great work @somboons!
Thanks for reply
I have tested 100% it can fix qhsusb_bulk
please see in my page
https://www.facebook.com/droidth
Is there any way to force qhsusb_bulk mode?
G2 bricked with QHSUSB_BULK (Qualcomm 9006) detected on computer is ALREADY FIXABLE.
Check link below. Download proper files for your G2. Same model of course.
Just run 1harddisk.exe then select right model of your phone from the menu. Then just wait for it to finish. Remove phone from USB, remove battery and reinsert again. Hold volume up and plug phone to computer. That's it.
Credits: Tungkik
http://forum.xda-developers.com/lg-g2/general/unbrick-lg-g2-qhsusbbulkqualcomm-9006-t2939627
I can confirm, i repaired my friend phone via windows today, i flashed all partitions. One was failed - persist. But phone success joined to download mode
Ganjax said:
I can confirm, i repaired my friend phone via windows today, i flashed all partitions. One was failed - persist. But phone success joined to download mode
Click to expand...
Click to collapse
Thank you very what variant ?
D802. Partitions:
sbl1
aboot
dbi
tz
laf
misc
rpm
Correctly flashed
Ganjax said:
D802. Partitions:
sbl1
aboot
dbi
tz
laf
misc
rpm
Correctly flashed
Click to expand...
Click to collapse
I have tested on D802 it work too. I already have merged in my tool.But I need partition number of other variant for make sure my tool can work in other variant.
Everybody who have F320L/K ,D801,D806,D803,VS980 Please use this command then send .txt file to me I will add in my tool,
Thank you
ll /dev/block/platform/msm_sdcc.1/by-name/ > /sdcard/droidth-partitions.txt
Click to expand...
Click to collapse
Maybe you know why persist was unable to flash? Misc volume17 was correctly flashed, and persist volume18 0bytes record in and 1byte record out.
As I have posted days ago. There is already a tool for windows to fix this kind of brick for different models of G2. Anyways credits to Tungkik from Vietnam.
F320
dd if=modem.img of=\\?\Device\Harddisk1\Partition1
dd if=sbl1.img of=\\?\Device\Harddisk1\Partition2
dd if=dbi.img of=\\?\Device\Harddisk1\Partition3
dd if=aboot.img of=\\?\Device\Harddisk1\Partition5
dd if=rpm.img of=\\?\Device\Harddisk1\Partition6
dd if=boot.img of=\\?\Device\Harddisk1\Partition7
dd if=tz.img of=\\?\Device\Harddisk1\Partition8
dd if=misc.img of=\\?\Device\Harddisk1\Partition13
dd if=recovery.img of=\\?\Device\Harddisk1\Partition15
dd if=laf.img of=\\?\Device\Harddisk1\Partition24
D802
dd if=modem.img of=\\?\Device\Harddisk1\Partition1
dd if=sbl1.img of=\\?\Device\Harddisk1\Partition2
dd if=dbi.img of=\\?\Device\Harddisk1\Partition3
dd if=aboot.img of=\\?\Device\Harddisk1\Partition5
dd if=rpm.img of=\\?\Device\Harddisk1\Partition6
dd if=boot.img of=\\?\Device\Harddisk1\Partition7
dd if=tz.img of=\\?\Device\Harddisk1\Partition8
dd if=misc.img of=\\?\Device\Harddisk1\Partition13
dd if=recovery.img of=\\?\Device\Harddisk1\Partition15
dd if=laf.img of=\\?\Device\Harddisk1\Partition23
VS980
dd if=modem.img of=\\?\Device\Harddisk1\Partition1
dd if=sbl1.img of=\\?\Device\Harddisk1\Partition2
dd if=dbi.img of=\\?\Device\Harddisk1\Partition3
dd if=aboot.img of=\\?\Device\Harddisk1\Partition5
dd if=rpm.img of=\\?\Device\Harddisk1\Partition6
dd if=boot.img of=\\?\Device\Harddisk1\Partition7
dd if=tz.img of=\\?\Device\Harddisk1\Partition8
dd if=misc.img of=\\?\Device\Harddisk1\Partition13
dd if=recovery.img of=\\?\Device\Harddisk1\Partition15
dd if=laf.img of=\\?\Device\Harddisk1\Partition24
D800
dd if=modem.img of=\\?\Device\Harddisk1\Partition1
dd if=sbl1.img of=\\?\Device\Harddisk1\Partition2
dd if=dbi.img of=\\?\Device\Harddisk1\Partition3
dd if=aboot.img of=\\?\Device\Harddisk1\Partition5
dd if=rpm.img of=\\?\Device\Harddisk1\Partition6
dd if=boot.img of=\\?\Device\Harddisk1\Partition7
dd if=tz.img of=\\?\Device\Harddisk1\Partition8
dd if=misc.img of=\\?\Device\Harddisk1\Partition13
dd if=recovery.img of=\\?\Device\Harddisk1\Partition15
dd if=laf.img of=\\?\Device\Harddisk1\Partition23
L01F
dd if=modem.img of=\\?\Device\Harddisk1\Partition1
dd if=sbl1.img of=\\?\Device\Harddisk1\Partition2
dd if=dbi.img of=\\?\Device\Harddisk1\Partition3
dd if=aboot.img of=\\?\Device\Harddisk1\Partition5
dd if=rpm.img of=\\?\Device\Harddisk1\Partition6
dd if=boot.img of=\\?\Device\Harddisk1\Partition7
dd if=tz.img of=\\?\Device\Harddisk1\Partition8
dd if=misc.img of=\\?\Device\Harddisk1\Partition13
dd if=recovery.img of=\\?\Device\Harddisk1\Partition15
dd if=laf.img of=\\?\Device\Harddisk1\Partition24
Ganjax said:
Maybe you know why persist was unable to flash? Misc volume17 was correctly flashed, and persist volume18 0bytes record in and 1byte record out.
Click to expand...
Click to collapse
For those partition I thing we no need to flash if you see in program same partition don't use diak space
devcon69 said:
As I have posted days ago. There is already a tool for windows to fix this kind of brick for different models of G2. Anyways credits to Tungkik from Vietnam.
F320
dd if=modem.img of=\\?\Device\Harddisk1\Partition1
dd if=sbl1.img of=\\?\Device\Harddisk1\Partition2
dd if=dbi.img of=\\?\Device\Harddisk1\Partition3
dd if=aboot.img of=\\?\Device\Harddisk1\Partition5
dd if=rpm.img of=\\?\Device\Harddisk1\Partition6
dd if=boot.img of=\\?\Device\Harddisk1\Partition7
dd if=tz.img of=\\?\Device\Harddisk1\Partition8
dd if=misc.img of=\\?\Device\Harddisk1\Partition13
dd if=recovery.img of=\\?\Device\Harddisk1\Partition15
dd if=laf.img of=\\?\Device\Harddisk1\Partition24
D802
dd if=modem.img of=\\?\Device\Harddisk1\Partition1
dd if=sbl1.img of=\\?\Device\Harddisk1\Partition2
dd if=dbi.img of=\\?\Device\Harddisk1\Partition3
dd if=aboot.img of=\\?\Device\Harddisk1\Partition5
dd if=rpm.img of=\\?\Device\Harddisk1\Partition6
dd if=boot.img of=\\?\Device\Harddisk1\Partition7
dd if=tz.img of=\\?\Device\Harddisk1\Partition8
dd if=misc.img of=\\?\Device\Harddisk1\Partition13
dd if=recovery.img of=\\?\Device\Harddisk1\Partition15
dd if=laf.img of=\\?\Device\Harddisk1\Partition23
VS980
dd if=modem.img of=\\?\Device\Harddisk1\Partition1
dd if=sbl1.img of=\\?\Device\Harddisk1\Partition2
dd if=dbi.img of=\\?\Device\Harddisk1\Partition3
dd if=aboot.img of=\\?\Device\Harddisk1\Partition5
dd if=rpm.img of=\\?\Device\Harddisk1\Partition6
dd if=boot.img of=\\?\Device\Harddisk1\Partition7
dd if=tz.img of=\\?\Device\Harddisk1\Partition8
dd if=misc.img of=\\?\Device\Harddisk1\Partition13
dd if=recovery.img of=\\?\Device\Harddisk1\Partition15
dd if=laf.img of=\\?\Device\Harddisk1\Partition24
D800
dd if=modem.img of=\\?\Device\Harddisk1\Partition1
dd if=sbl1.img of=\\?\Device\Harddisk1\Partition2
dd if=dbi.img of=\\?\Device\Harddisk1\Partition3
dd if=aboot.img of=\\?\Device\Harddisk1\Partition5
dd if=rpm.img of=\\?\Device\Harddisk1\Partition6
dd if=boot.img of=\\?\Device\Harddisk1\Partition7
dd if=tz.img of=\\?\Device\Harddisk1\Partition8
dd if=misc.img of=\\?\Device\Harddisk1\Partition13
dd if=recovery.img of=\\?\Device\Harddisk1\Partition15
dd if=laf.img of=\\?\Device\Harddisk1\Partition23
L01F
dd if=modem.img of=\\?\Device\Harddisk1\Partition1
dd if=sbl1.img of=\\?\Device\Harddisk1\Partition2
dd if=dbi.img of=\\?\Device\Harddisk1\Partition3
dd if=aboot.img of=\\?\Device\Harddisk1\Partition5
dd if=rpm.img of=\\?\Device\Harddisk1\Partition6
dd if=boot.img of=\\?\Device\Harddisk1\Partition7
dd if=tz.img of=\\?\Device\Harddisk1\Partition8
dd if=misc.img of=\\?\Device\Harddisk1\Partition13
dd if=recovery.img of=\\?\Device\Harddisk1\Partition15
dd if=laf.img of=\\?\Device\Harddisk1\Partition24
Click to expand...
Click to collapse
D800
lrwxrwxrwx root root 1970-01-21 01:15 laf -> /dev/block/mmcblk0p24
24 not 23
مرحبا
Can you help me?
Hey! Something similar happend to my Cubot ZORRO 011 when I tried to update to a newer firmware. Used CWM to wipe /data, /system and /cache. CWm said Update complete. When I chose reboot device CWM said "Root access missing. Root?" I chose yes.. (I wasn't rooted). I got the boot animation and sound but then it went screen black. I have the QHSUSB_BULK in deice manager. Cubot 001 has Qualcomm Snapdragon 410 MSM8916. I have 12 partitions. One is 68MB and has a folder called "image". 10 are empty and not formated (for windows anyway) and the last one is external SD. I would really appreciate any help.
Familotel said:
Hey! Something similar happend to my Cubot ZORRO 011 when I tried to update to a newer firmware. Used CWM to wipe /data, /system and /cache. CWm said Update complete. When I chose reboot device CWM said "Root access missing. Root?" I chose yes.. (I wasn't rooted). I got the boot animation and sound but then it went screen black. I have the QHSUSB_BULK in deice manager. Cubot 001 has Qualcomm Snapdragon 410 MSM8916. I have 12 partitions. One is 68MB and has a folder called "image". 10 are empty and not formated (for windows anyway) and the last one is external SD. I would really appreciate any help.
Click to expand...
Click to collapse
You need system dump from any working phone of ur model...
Then u can fix it.....
aftabalam8c2 said:
You need system dump from any working phone of ur model...
Then u can fix it.....
Click to expand...
Click to collapse
If I have the official ROM (Android 4.4.4) does that help? Thx 4 answering
Familotel said:
If I have the official ROM (Android 4.4.4) does that help? Thx 4 answering
Click to expand...
Click to collapse
System dum is different from stock rom
Its like nandroid backup.
System dump is the exact copy of phone partition.
Try to find any running one.
Then u can unbrick it.
Related
Hey
I found another post which details a way to get all of the relevant files together from your device, and then bundled into a tar, so that you can use Odin to reflash your own 'custom' backup. I have put the commands below, does anyone know how to tailor this for the SGS2 ? The \dev\block\* devices are different as when i try through adb shell or terminal emulator it doesn't recognise the devices ::
Sys:
dd if=/dev/block/stl10 of=/sdcard/factoryfs.rfs bs=4096
Kernel:
dd if=/dev/block/bml8 of=/sdcard/zImage bs=4096
Recovery:
dd if=/dev/block/bml9 of=/sdcard/recovery.bin bs=4096
(personal info)
Cache:
dd if=/dev/block/mmcblk0p3 of=/sdcard/cache.rfs bs=4096
DBData:
dd if=/dev/block/stl11 of=/sdcard/dbdata.rfs bs=4096
Data:
dd if=/dev/block/mmcblk0p1 of=/sdcard/movinand.bin bs=4096
and then to make the image for Odin to flash:
tar -H ustar -c cache.rfs dbdata.rfs factoryfs.rfs movinand.bin recovery.bin zImage > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
Any help appreciated
Thanks
I'm interested in this, too!
hi sea_salt !
I got the commands from another post:
dd if=/dev/block/mmcblk0p1 of=/sdcard/p1-EFS.img bs=4096
dd if=/dev/block/mmcblk0p4 of=/sdcard/p4-PARAM.img bs=4096
dd if=/dev/block/mmcblk0p5 of=/sdcard/p5-KERNEL.img bs=4096
dd if=/dev/block/mmcblk0p8 of=/sdcard/p8-MODEM.img bs=4096
dd if=/dev/block/mmcblk0p9 of=/sdcard/p9-FACTORYFS.img bs=4096
dd if=/dev/block/mmcblk0p12 of=/sdcard/p12-HIDDEN.img bs=4096
I have tried them using adb shell and they work .
The question is how do i get them now into a .tar/.md5 so that Odin can flash them ?
spoonflames said:
hi sea_salt !
I got the commands from another post:
dd if=/dev/block/mmcblk0p1 of=/sdcard/p1-EFS.img bs=4096
dd if=/dev/block/mmcblk0p4 of=/sdcard/p4-PARAM.img bs=4096
dd if=/dev/block/mmcblk0p5 of=/sdcard/p5-KERNEL.img bs=4096
dd if=/dev/block/mmcblk0p8 of=/sdcard/p8-MODEM.img bs=4096
dd if=/dev/block/mmcblk0p9 of=/sdcard/p9-FACTORYFS.img bs=4096
dd if=/dev/block/mmcblk0p12 of=/sdcard/p12-HIDDEN.img bs=4096
I have tried them using adb shell and they work .
The question is how do i get them now into a .tar/.md5 so that Odin can flash them ?
Click to expand...
Click to collapse
hey this sounds great. thanks for your reply!
Does EFS, PARAM, KERNEL, MODEM, FACTORYFS, HIDDEN contain ALL stuff of the sgs2-phone's-rom and data, so that it can be used to completetely backup the device?
but I suppose that these adb-commands only work when you already have a root-kernel, or not?
are there the same commands to use adb to restore all this stuff?
dd if=/dev/block/mmcblk0p4 of=/mnt/sdcard/mmcblk0p4.img
dd if=/dev/block/mmcblk0p5 of=/mnt/sdcard/mmcblk0p5.img
dd if=/dev/block/mmcblk0p13 of=/mnt/sdcard/mmcblk0p13.img
dd if=/dev/block/mmcblk0p28 of=/mnt/sdcard/mmcblk0p28.img
dd if=/dev/block/mmcblk0p29 of=/mnt/sdcard/mmcblk0p29.img
dd if=/dev/block/mmcblk0p30 of=/mnt/sdcard/mmcblk0p30.img
all of these are blank or almost blank for me and tis causing my 3g not to work..
if someone can dump them and upload, i'd be really happy
usual command is adb shell
su
dd if=/dev/block/mmcblk0p4 of=/mnt/sdcard/mmcblk0p4.img
dd if=/dev/block/mmcblk0p5 of=/mnt/sdcard/mmcblk0p5.img
dd if=/dev/block/mmcblk0p13 of=/mnt/sdcard/mmcblk0p13.img
dd if=/dev/block/mmcblk0p28 of=/mnt/sdcard/mmcblk0p28.img
dd if=/dev/block/mmcblk0p29 of=/mnt/sdcard/mmcblk0p29.img
dd if=/dev/block/mmcblk0p30 of=/mnt/sdcard/mmcblk0p30.img
mmcblk0p5 has the cid and imei and mmcblk0p13 says SkaBHT231V208772 other files are empty for me
ercineker said:
mmcblk0p5 has the cid and imei and mmcblk0p13 says SkaBHT231V208772 other files are empty for me
Click to expand...
Click to collapse
thank u!
i there,
I'm working at creating a solution for JTAG repair on the SGS III USC model and I'm in need of a SCH-R530M SBL dumps and a few other zones. I need a rooted user to simply perform the following command from a terminal on the phone, or while using ADB SHELL under the su user. Once at the command line issue this command, then simply upload the files which end up on your sdcard to me here. That's it!
Thanks in advance!
Code:
dd if=/dev/block/mmcblk0p2 of=/sdcard/sbl1 bs=4096
dd if=/dev/block/mmcblk0p3 of=/sdcard/sbl2 bs=4096
dd if=/dev/block/mmcblk0p4 of=/sdcard/sbl3 bs=4096
dd if=/dev/block/mmcblk0p5 of=/sdcard/aboot bs=4096
dd if=/dev/block/mmcblk0p6 of=/sdcard/rpm bs=4096
dd if=/dev/block/mmcblk0p7 of=/sdcard/boot bs=4096
dd if=/dev/block/mmcblk0p8 of=/sdcard/tz bs=4096
dd if=/dev/block/mmcblk0p9 of=/sdcard/pad bs=4096
dd if=/dev/block/mmcblk0p10 of=/sdcard/param bs=4096
dd if=/dev/block/mmcblk0p18 of=/sdcard/recovery bs=4096
tomy1986.nt said:
i there,
I'm working at creating a solution for JTAG repair on the SGS III USC model and I'm in need of a SCH-R530M SBL dumps and a few other zones. I need a rooted user to simply perform the following command from a terminal on the phone, or while using ADB SHELL under the su user. Once at the command line issue this command, then simply upload the files which end up on your sdcard to me here. That's it!
Thanks in advance!
Code:
dd if=/dev/block/mmcblk0p2 of=/sdcard/sbl1 bs=4096
dd if=/dev/block/mmcblk0p3 of=/sdcard/sbl2 bs=4096
dd if=/dev/block/mmcblk0p4 of=/sdcard/sbl3 bs=4096
dd if=/dev/block/mmcblk0p5 of=/sdcard/aboot bs=4096
dd if=/dev/block/mmcblk0p6 of=/sdcard/rpm bs=4096
dd if=/dev/block/mmcblk0p7 of=/sdcard/boot bs=4096
dd if=/dev/block/mmcblk0p8 of=/sdcard/tz bs=4096
dd if=/dev/block/mmcblk0p9 of=/sdcard/pad bs=4096
dd if=/dev/block/mmcblk0p10 of=/sdcard/param bs=4096
dd if=/dev/block/mmcblk0p18 of=/sdcard/recovery bs=4096
Click to expand...
Click to collapse
Reported your other thread - Reporting this one. USE THE APPROPRIATE DEVICE FORUM. One of the simplest rules!
Thread Closed.
OP Please follow the rules about double posts... Also please post in the correct sections.
DISCLAIMER: THIS IS VERY DANGEROUS COMPARED TO A NORMAL ROM FLASH. DO NOT DO THIS IF YOU DON'T KNOW WHAT YOU'RE DOING OTHER THAN FLASHING ROMS.
IF SOMETHING GOES WRONG, YOU HAVE ONLY YOURSELF TO BLAME. YOU HAVE BEEN WARNED.[/B]
To convert to Nexus 4
First off, there are a few issues.
-SDCard doesn't work.
-Capacitive buttons aren't working. No known way to fix it.
First off, lets flash the N4 Rom.
1) Install LGNPST - Use tSilenzio's AutoLGNPST - http://www.oudhitsquad.com/android/LGE/Firmware/Tools/AutoLGNPST-tSilenzio.zip
2) Download the Nexus 4 Image - https://www.androidfilehost.com/?fid=9390248398092765463
3) Rename the extracted .tot file to a .bin file
4) Put the phone in Download mode. Volume Up + Volume Down While inserting USB cable.
5) Open LGNPST and select the phone - Should be Com[Number]
6) In the DLL section, select LGNPST_LS970.dll
7) In the file selection, select the previously renamed Nexus 4 bin file.
8) Start the flashing process and hold your breath.
9) When it hits 67%, your phone should start booting. DO NOT UNPLUG YET.
10) At 85%, an error will occur saying that the phone was unplugged. Ignore it and close LGNPST. The image is fully flashed.
11) Hold Volume Up + Power to put the phone into FASTBOOT mode.
12) Download the recovery from here and place it into your fastboot directory. - http://forum.xda-developers.com/showthread.php?t=2010984
13) Download the following 3 files and place them on the MicroSD card. - http://d-h.st/cFA - http://d-h.st/yUQ - http://d-h.st/0dH
14) While still in fastboot, type "fastboot boot recovery.img" - This will put the phone on the custom recovery. Make sure the SD card is in.
---Here, we're going to fix the partition tables for 16GB of space and replace the backup GPT so that we can't hardbrick from the backup GPT.
15) Run adb shell to get into a root shell in recovery.
16) Copy the modified DD onto the phone
Code:
# cp /external_sd/dd /
# chmod 755 /dd
17) Backup the partition tables incase something goes wrong.
Code:
# /dd if=/dev/block/mmcblk0 of=/external_sd/pgpt8G.img bs=512 count=34
# /dd if=/dev/block/mmcblk0 of=/external_sd/sgpt8G.img bs=512 skip=30777311
18) Unmount the filesystems so that you can overwrite the partition table.
Code:
# umount /data
# umount /cache
19) Make sure nothing is mounted. It should return this (Other than partition size):
Code:
# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 911.7M 48.0K 911.6M 0% /dev
/dev/block/mmcblk1p1 59.4G 4.8G 54.6G 8% /external_sd
20) Move the partitions to their new locations. This may take a couple minutes.
Code:
# /dd if=/dev/block/mmcblk0 of=/external_sd/DDR bs=512 skip=15267840 count=2015
# /dd if=/external_sd/DDR of=/dev/block/mmcblk0 bs=512 seek=30775296 conv=notrunc
21) Install the new partition tables.
Code:
# /dd if=/external_sd/sgpt16G.img of=/dev/block/mmcblk0 bs=512 seek=30777311 conv=notrunc
# /dd if=/external_sd/pgpt16G.img of=/dev/block/mmcblk0 bs=512 seek=0 conv=notrunc
22) Make sure no errors occurred. Run 'parted /dev/block/mmcblk0' and check that it returns the same as the below.
Code:
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
Model: MMC 016G92 (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.2MB 524kB sbl1
3 68.2MB 68.7MB 524kB sbl2
4 68.7MB 70.8MB 2097kB sbl3
5 70.8MB 71.3MB 524kB tz
6 71.3MB 94.4MB 23.1MB boot
7 94.4MB 117MB 23.1MB recovery
8 117MB 118MB 799kB m9kefs1
9 118MB 119MB 799kB m9kefs2
10 119MB 120MB 799kB m9kefs3
11 120MB 121MB 524kB rpm
12 121MB 121MB 524kB aboot
13 121MB 122MB 524kB sbl2b
14 122MB 124MB 2097kB sbl3b
15 124MB 124MB 524kB abootb
16 124MB 125MB 524kB rpmb
17 125MB 125MB 524kB tzb
18 125MB 126MB 524kB metadata
19 126MB 143MB 16.8MB misc
20 143MB 159MB 16.8MB ext4 persist
21 159MB 1040MB 881MB ext4 system
22 1040MB 1627MB 587MB ext4 cache
23 1627MB 15.8GB 14.1GB ext4 userdata
24 15.8GB 15.8GB 524kB DDR
25 15.8GB 15.8GB 507kB grow
23) If something different was returned, run the below code to restore the previous partition tables.
Code:
# /dd if=/external_sd/sgpt8G.img of=/dev/block/mmcblk0 bs=512 seek=30777311 conv=notrunc
# /dd if=/external_sd/pgpt8G.img of=/dev/block/mmcblk0 bs=512 seek=0 conv=notrunc
24) Exit the shell and type 'adb reboot bootloader' or reboot the phone while holding Volume Up.
25) Check that you're in fastboot mode and exit the following commands - This will fix the filesystem to take up the entire partition.
Code:
fastboot erase userdata
fastboot format userdata
fastboot -w
26) Boot the phone and update as needed. Then, put this on the phone and flash in recovery.
27) You are now working other than the SD card and Capacitive buttons.
Credits:
http://forum.xda-developers.com/showthread.php?t=2117576
http://forum.xda-developers.com/showthread.php?t=2099784
http://forum.xda-developers.com/showthread.php?t=2160124
http://forum.xda-developers.com/showthread.php?t=2146816
To convert from Nexus 4
This assumes that you have read the Convert to section.
1) Wipe the phone. Go into fastboot mode [Vol Up + Power] and execute the following commands. This is to prevent corrupted data partitions.
Code:
fastboot -w
fastboot format system
fastboot format userdata
fastboot format cache
fastboot format data
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase data
2) LGNPST back to stock. You will do this twice to fix some issues.
To get into download mode, turn the phone off and hold Vol Up + Vol Down while inserting the USB cable.
3) Download these 2 images. Mar. 8, 2013 and Sept. 29, 2012
4) Flash the Mar. 8, 2013 firmware in LGNPST (See above for how to flash firmware in LGNPST. As before, the phone will start booting at 67% and LGNPST will show an error at 85%. Ignore the error and close LGNPST.
5) Restart the phone in download mode and now flash the Sept. 29, 2012 firmware. If you don't, your /SDCARD may be corrupted and you cant root.
6) Root the phone and unlock the bootloader. See here
7) If that doesn't work, try Teenybin.
8) Some partitions are broken. Go into CWM recovery and open an 'adb shell'.
9) Execute the following code. This will backup the broken partitions and wipe them.
Code:
dd if=/dev/block/mmcblk0p15 of=/sdcard/mmcblk0p15.bak
dd if=/dev/block/mmcblk0p16 of=/sdcard/mmcblk0p16.bak
dd if=/dev/block/mmcblk0p19 of=/sdcard/mmcblk0p19.bak
mke2fs -T ext4 /dev/block/mmcblk0p15
mke2fs -T ext4 /dev/block/mmcblk0p16
mke2fs -T ext4 /dev/block/mmcblk0p19
---You should now be back to stock--- LGNPST again if you want 'True Stock'
Let me know if you see anything wrong and please leave nasty comments at the door.
Ok, granted. This is more about recovering from flashing to Nexus 4 than about flashing to it. Basically, DON'T DO IT, as it doesn't seem to be worth it. We have AOSP and Cyanogen, etc.
I just posted this because I bought a phone that was flashed and went through hours of work fixing it.
Please read this before you think about flashing. http://forum.xda-developers.com/showpost.php?p=36735476&postcount=149
Its not worth it so much now but it was great when first released and it doesn't take that long to revert your phone. I went back and fourth like 5 times and my phone is fine. I think there is a low chance of your phone bricking as long as you follow instructions. The conversion is still a good option to have.
Sent from my LG Optimus G using XDA Premium 4 mobile app
Dr0!dFreek said:
Its not worth it so much now but it was great when first released and it doesn't take that long to revert your phone. I went back and fourth like 5 times and my phone is fine. I think there is a low chance of your phone bricking as long as you follow instructions. The conversion is still a good option to have.
Sent from my LG Optimus G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, it seems nice to have the ability to do so, which is why I wrote the guide (and to give a single comprehensive guide that works).
It's nice to have a perfectly working KitKat rom the day its released, which is why I converted (When KK was released), but now, it doesn't seem worth it (We have AOSP). If you want MultiRom and franco kernel (Like I did), then its nice to have, but otherwise, most people don't need it.
alastair53 said:
13) Download the following 3 files and place them on the MicroSD card. - http://d-h.st/cFA - http://d-h.st/yUQ - http://d-h.st/0dH
Click to expand...
Click to collapse
Is this part SPYWARE? the 3 files downloads a exe and is detetected as virus or something.
I just got a fresh Fire HD 7 with 4.1.1, and updated it first to 4.5.3, and then to 5.2.2u2 with 5.2.0 bootloaders. While doing so, I kept track of the state of all the internal partitions that the updates do not seemingly touch (see this post for partitions http://forum.xda-developers.com/fire-hd/help/internal-memory-structure-hidden-t3122246 )
I've been using a simple script pasted from adb window on the PC side (needs root access):
Code:
adb shell
su
dd if=/dev/block/mmcblk0p1 of=/sdcard/01_pro_info.img
dd if=/dev/block/mmcblk0p2 of=/sdcard/02_pmt.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/03_tee1.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/04_tee2.img
dd if=/dev/block/mmcblk0p5 of=/sdcard/05_uboot.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/06_boot.img
dd if=/dev/block/mmcblk0p7 of=/sdcard/07_recovery.img
dd if=/dev/block/mmcblk0p8 of=/sdcard/08_kb.img
dd if=/dev/block/mmcblk0p9 of=/sdcard/09_dkb.img
dd if=/dev/block/mmcblk0p10 of=/sdcard/10_misc.img
dd if=/dev/block/mmcblk0p11 of=/sdcard/11_persisbackup.img
cd /sdcard/
md5 *.img
rm *.img
cd /sdcard/
I can now compare 2 different Fires (old & new), and also the new Fire on the path from 4.1.1 to 4.5.3 to 5.2.0
Between the 2 different Fires, the only partition that has the same md5 is :
72fe4bd35179bc299674c781033ae1f7 10_misc.img
The other dark partitions differ between the 2 Fires (pro_info, pmt, kb, dkb)
Now, on the new Fire, partition that always changes between boots is :
8c72758dff50208f74b7bbc12725e46a 11_persisbackup.img
(so this is probably the boot counter lives and so on)
Finally, when the new Fire went from 4.1.1 to 4.5.3, (pro_info, pmt, kb, dkb) all stayed the same. But when I updated it to 5.2.0 bootloaders, dkb changed md5. The other 3 are still the same.
It'd be nice to run this script on a Fire with 5.2.2u2 bootloaders, and see if persisbackup is the same.
It could be possible to replace some of these dark partitions, and convert the Fire into an "unbricking" state.
Just to confirm: One can copy your whole script and paste it into the CMD window. It runs and doesn't do anything to the Fire HD. It just gets info that can help you, right? Whoever does this can drag the mouse over all the output to select it and hit ENTER to copy to clipboard, then paste it into a post for you.
I ask because my guide doesn't install the 5.2.0 bootloaders, so anyone who used it in the last month or so will have 5.2.2.u2 bootloaders. If no one else jumps in, perhaps @comapro or @benyaki or @sunilzs would have the time to run it for you.
If time permits tomorrow, I'll run that for you. (And if I remember!)
benyaki said:
If time permits tomorrow, I'll run that for you. (And if I remember!)
Click to expand...
Click to collapse
Here you go. Hope I did it correctly. If you need anything else, let me know.
Code:
C:\adb>adb shell
su
dd if=/dev/block/mmcblk0p1 of=/sdcard/01_pro_info.img
dd if=/dev/block/mmcblk0p2 of=/sdcard/02_pmt.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/03_tee1.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/04_tee2.img
dd if=/dev/block/mmcblk0p5 of=/sdcard/05_uboot.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/06_boot.img
dd if=/dev/block/mmcblk0p7 of=/sdcard/07_recovery.img
dd if=/dev/block/mmcblk0p8 of=/sdcard/08_kb.img
dd if=/dev/block/mmcblk0p9 of=/sdcard/09_dkb.img
dd if=/dev/block/mmcblk0p10 of=/sdcard/10_misc.img
dd if=/dev/block/mmcblk0p11 of=/sdcard/11_persisbackup.img
cd /sdcard/
md5 *.img
rm *.img
cd /sdcard/[email protected]:/ $ su
dd if=/dev/block/mmcblk0p1 of=/sdcard/01_pro_info.img
dd if=/dev/block/mmcblk0p2 of=/sdcard/02_pmt.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/03_tee1.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/04_tee2.img
dd if=/dev/block/mmcblk0p5 of=/sdcard/05_uboot.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/06_boot.img
dd if=/dev/block/mmcblk0p7 of=/sdcard/07_recovery.img
dd if=/dev/block/mmcblk0p8 of=/sdcard/08_kb.img
dd if=/dev/block/mmcblk0p9 of=/sdcard/09_dkb.img
dd if=/dev/block/mmcblk0p10 of=/sdcard/10_misc.img
dd if=/dev/block/mmcblk0p11 of=/sdcard/11_persisbackup.img
cd /sdcard/
md5 *.img
rm *.img
cd /sdcard/dd if=/dev/block/mmcblk0p1 of=/sdcard/01_pro_info.img
dd if=/dev/block/mmcblk0p2 of=/sdcard/02_pmt.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/03_tee1.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/04_tee2.img
dd if=/dev/block/mmcblk0p5 of=/sdcard/05_uboot.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/06_boot.img
dd if=/dev/block/mmcblk0p7 of=/sdcard/07_recovery.img
dd if=/dev/block/mmcblk0p8 of=/sdcard/08_kb.img
dd if=/dev/block/mmcblk0p9 of=/sdcard/09_dkb.img
dd if=/dev/block/mmcblk0p10 of=/sdcard/10_misc.img
dd if=/dev/block/mmcblk0p11 of=/sdcard/11_persisbackup.img
cd /sdcard/
md5 *.img
rm *.img
cd /sdcard/[email protected]:/ # dd if=/dev/block/mmcblk0p1 of=/sdcard/01_pro_info.img
256+0 records in
256+0 records out
131072 bytes transferred in 0.105 secs (1248304 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p2 of=/sdcard/02_pmt.img
8192+0 records in
8192+0 records out
4194304 bytes transferred in 1.357 secs (3090865 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p3 of=/sdcard/03_tee1.img
10240+0 records in
10240+0 records out
5242880 bytes transferred in 2.069 secs (2534016 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p4 of=/sdcard/04_tee2.img
10240+0 records in
10240+0 records out
5242880 bytes transferred in 1.930 secs (2716518 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p5 of=/sdcard/05_uboot.img
1024+0 records in
1024+0 records out
524288 bytes transferred in 0.128 secs (4096000 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p6 of=/sdcard/06_boot.img
16384+0 records in
16384+0 records out
8388608 bytes transferred in 2.146 secs (3908950 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p7 of=/sdcard/07_recovery.img
16384+0 records in
16384+0 records out
8388608 bytes transferred in 2.113 secs (3969999 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p8 of=/sdcard/08_kb.img
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.323 secs (3246365 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p9 of=/sdcard/09_dkb.img
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.265 secs (3956890 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p10 of=/sdcard/10_misc.img
1024+0 records in
1024+0 records out
524288 bytes transferred in 0.131 secs (4002198 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p11 of=/sdcard/11_persisbackup.img
32768+0 records in
32768+0 records out
16777216 bytes transferred in 4.256 secs (3942015 bytes/sec)
[email protected]:/ # cd /sdcard/
[email protected]:/sdcard # md5 *.img
40ab8a444a6bb38a77c8b023c8c28498 01_pro_info.img
976b7613ac6ccd0f8221b5dc13d01676 02_pmt.img
a25016f54a524f93e0c1225539273404 03_tee1.img
eb83b62828a361f33c6ed0ac62c872e7 04_tee2.img
233387047f6eb2e5e9f760cfc3adb5c7 05_uboot.img
e9a0260c940a03510662c74ee269c72e 06_boot.img
7082205b20052ae93c9215460de8f891 07_recovery.img
96b0de56e2e022e07e6dbaa0df49fcae 08_kb.img
32dadf8d79d0749dd054b11bd34051bf 09_dkb.img
72fe4bd35179bc299674c781033ae1f7 10_misc.img
ef16264f4b03b8879441e49478587528 11_persisbackup.img
[email protected]:/sdcard # rm *.img
[email protected]:/sdcard # cd /sdcard/
[email protected]:/sdcard #
benyaki said:
Here you go. Hope I did it correctly. If you need anything else, let me know.
Code:
[email protected]:/sdcard # md5 *.img
40ab8a444a6bb38a77c8b023c8c28498 01_pro_info.img
976b7613ac6ccd0f8221b5dc13d01676 02_pmt.img
a25016f54a524f93e0c1225539273404 03_tee1.img
eb83b62828a361f33c6ed0ac62c872e7 04_tee2.img
233387047f6eb2e5e9f760cfc3adb5c7 05_uboot.img
e9a0260c940a03510662c74ee269c72e 06_boot.img
7082205b20052ae93c9215460de8f891 07_recovery.img
96b0de56e2e022e07e6dbaa0df49fcae 08_kb.img
32dadf8d79d0749dd054b11bd34051bf 09_dkb.img
72fe4bd35179bc299674c781033ae1f7 10_misc.img
ef16264f4b03b8879441e49478587528 11_persisbackup.img
[email protected]:/sdcard # rm *.img
[email protected]:/sdcard # cd /sdcard/
[email protected]:/sdcard #
Click to expand...
Click to collapse
I think the issue is pretty tough. KB and DKB look like candidates to have clues for bricking. Most of "dark" partitions are non-trivially different between the 2 Fires I have, so overwriting them with different copies is probably not advisable
Actually, what would really help is to run md5 before running 5.2.2u2 bootloaders for the 1st time, and then after to see if it's just DKB that changed. One could back up these partitions before playing with the device, so if 5.2.2u2 bootloaders get accidentally loaded, there could be a way to go back.
Fire 7 2015 has similar bricking phenomenon (5.0.1 to 5.1.1 transition). So it might be safer to attempt to explore it with Fire 2015. One just captures all the partitions under 5.0.1, loads up the 5.1.1 bootloaders, captures all the partitions again. Then the 5.1.1 bootloaders and the relevant partitions (those that changed) is overwritten by 5.0.1 copies, to see if that allows 5.0.1 to boot again. If not, at least those Fires are still under warranty.