Develop Bugs

Rooting LG H735 G4 Beat

hi, tried to search everywhere but to no avail soo far.. does anyone knows if there is an existing root guide for LG G4 Beat? its sort of a diff model but there's no sub for it so i guess ill put it at here since its still under G4 family.. :/

Do you have Android 5.0 or 5.1 installed?
First of all. Before you start to try root, download the kdz file for your phone.
The kdz is needed if something went wrong (e.g. phone not booting).
You can use the LG Flash Tool to flash the kdz to a bricked phone.
Use this link with your IMEI:
Code:
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=IMEI
If it works, please post the download link for the "kdz".
Or better post the output too, but delete your IMEI!
Your link will only work if you type:
csmgdl.lgmobile.com/dn/downloader.dev?fileKey=
and then add the rest of your url instead of the given link.

It's worth trying. You need to get a partition layout. Then @autoprime will give a full command to run in DL mode for dumping the system image, and flashing it once it's been injected with root. I can inject it for you once you have the system.img dump.

I wrote an guide how you can extract the GPT and calculate the dd parameters:
[How to] Determine dd Parameters For All LG G4 Models
http://forum.xda-developers.com/g4/h...lg-g4-t3184867
Do you know how to work with linux?
Please post the outputs of gdisk into a HIDE and CODE tag. Thank you.
Maybe you are a advanced user and can Inject root yourself with the autoroot.sh method (Inject_Root_G4.zip)?
Or do you need help?
I think you have Android 5.1.1 installed, so it is not possible to use Kingroot to root your device. Is that right?

dominik-p said:
I wrote an guide how you can extract the GPT and calculate the dd parameters:
[How to] Determine dd Parameters For All LG G4 Models
http://forum.xda-developers.com/g4/h...lg-g4-t3184867
Do you know how to work with linux?
Click to expand...
Click to collapse
Wow, thanks for that guide! I've been trying to figure out how to find the right dd params forever.

tabp0le said:
Wow, thanks for that guide! I've been trying to figure out how to find the right dd params forever.
Click to expand...
Click to collapse
Pleasure.
I think some people also knew how to do it, but no one wanted to write a guide.
AND ALWAYS CONSIDER:
You can brick your phone if you don't know what you are doing.
Backup your files before you change anything.

i think i got the link for the KDZ.. but when i
dominik-p said:
Do you have Android 5.0 or 5.1 installed?
First of all. Before you start to try root, download the kdz file for your phone.
The kdz is needed if something went wrong (e.g. phone not booting).
You can use the LG Flash Tool to flash the kdz to a bricked phone.
Use this link with your IMEI:
[CODEcsmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=IMEI[/CODE]
If it works, please post the download link for the "kdz".
Or better post the output too, but delete your IMEI!
Your link will only work if you type:
csmgdl.lgmobile.com/dn/downloader.dev?fileKey=
and then add the rest of your url instead of the given link.
Click to expand...
Click to collapse
ok i think i did it correctly.. heres the link
downloader.dev?fileKey=FWDEYI0132FMAUI263CCLO1/H73510b_00.kdz (had to cut it short cuz forum would not let me post new link :/ csmgdl.lgmobile.com/dn/ was before 'downloader')
heres the output file..
<response req_cmd="auth_model_check" status="OK">
<auth_model_check><result>OK</result>
<esn>-----MYIMEI----</esn>
<model>LGH735</model><suffix>ASEATS</suffix><msn>508KPUU032390</msn><esn_date/>
<sw_version>H73510B_00</sw_version>
<sw_url>fileKey=FWDEYI0132FMAUI263CCLO1/H73510b_00.kdz</sw_url> pkg03.lime.gdms.lge.com/dn/downloader.dev?
<sw_locale_url/><sw_recommand_uri/><app_version/><app_url/>
<cs_em_flag>N</cs_em_flag>
<cs_em_uri>N</cs_em_uri>
<chip_type>EG</chip_type>
<prod_type>2</prod_type>
<buyer>SEA</buyer>
<file_name>H73510b_00.kdz</file_name>
</auth_model_check></response>
and yes its 5.1..
would be nice if theres a step by step guide cuz last phone i tired rooting was prolly galaxy tab and it was wayy easier :/

Ok, well done. Is 10b the same version as currently installed on your device?
Some other details would be interesting:
Do you have an unbranded device?
Where did you buy it / where do you live? (country)
Are you an advanced user? Do you know how to work with linux?
The next steps will be:
Calculate your dd parameters and backup your system partition into a img file. Read my guide:
[How to] Determine dd Parameters For All LG G4 Models
http://forum.xda-developers.com/g4/h...lg-g4-t3184867
Please post the outputs of gdisk into a HIDE and CODE tag.
Post your calculated dd parameters, so that we can verify it.
IMPORTANT: Keep the original (unchanged) system.img on your computer (zip it).
Then:
Copy the img file to a linux system and mount it. Create a testfile (test.txt) on the mounted system partition.
Copy the img file back to your phone and try to "dd" it back over your system partition.
Check if you see the testfile on your system partition.
If that worked you have successfully overwritten your system partition.
Then:
Try to inject root with the Inject_Root_G4.zip on your linux system.
Copy the new img file to your phone and "dd" it over your system partition.
Please ask if you are not 100% sure what to do.
You are responsible for what you are doing with your device.
Backup all your data (photos, videos, messages...) before going one step further.

dominik-p said:
Ok, well done. Is 10b the same version as currently installed on your device?
Some other details would be interesting:
Do you have an unbranded device?
Where did you buy it / where do you live? (country)
Are you an advanced user? Do you know how to work with linux?
The next steps will be:
Calculate your dd parameters and backup your system partition into a img file. Read my guide:
[How to] Determine dd Parameters For All LG G4 Models
http://forum.xda-developers.com/g4/h...lg-g4-t3184867
Please post the outputs of gdisk into a HIDE and CODE tag.
Post your calculated dd parameters, so that we can verify it.
IMPORTANT: Keep the original (unchanged) system.img on your computer (zip it).
Then:
Copy the img file to a linux system and mount it. Create a testfile (test.txt) on the mounted system partition.
Copy the img file back to your phone and try to "dd" it back over your system partition.
Check if you see the testfile on your system partition.
If that worked you have successfully overwritten your system partition.
Then:
Try to inject root with the Inject_Root_G4.zip on your linux system.
Copy the new img file to your phone and "dd" it over your system partition.
Please ask if you are not 100% sure what to do.
You are responsible for what you are doing with your device.
Backup all your data (photos, videos, messages...) before going one step further.
Click to expand...
Click to collapse
what do u mean 10b?
not really unbranded i guess? its a mid-tier version of the LG G4.. this is the phone.. http://www.lg.com/sg/mobile-phones/lg-G4-Beat
dont think its out at the US yet
bought it at Singapore as i recontacted my phone
nope i dont know how to use linux and im %100 not sure what to do :crying:

Ok so you are not a advanced user?
10b is the version of the kdz file. Goto Settings->Phone info->software version on your phone and post your software version.
First of all: It is not possible to root your phone without linux!
You don't have to install a linux on your computer (physically) but at least in an virtual environment (virtualbox, vmware player) or as a live distribution.
What you can do without linux is try to extract the GPT.
Which OS is installed on your computer (Win 7, 8, 10)?
Download the LG_Root.zip from
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
It contains the Send_Command.exe
You need this tool to open a special console when your phone is in download mode.
Do you know this tool and how to enter the download mode?

dominik-p said:
Ok so you are not a advanced user?
10b is the version of the kdz file. Goto Settings->Phone info->software version on your phone and post your software version.
First of all: It is not possible to root your phone without linux!
You don't have to install a linux on your computer (physically) but at least in an virtual environment or as a live distribution.
What you can do without linux is try to extract the GPT.
Which OS is installed on your computer (Win 7, 8, 10)?
Download the LG_Root.zip from
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
It contains the Send_Command.exe
You need this tool to open a special console when your phone is in download mode.
Do you know this tool and how to enter the download mode?
Click to expand...
Click to collapse
no im not an advanced user..
its software version is : V10b-SEA-XX
so i guess its a 10b?
im using windows 7 right now

Yes you have 10b installed now.
The XX means that it is unbranded.
SEA means southeast asia.
Win 7 is fine. Send_Command will work.
Download the zip from the above-mentioned thread.
Then:
Power off your device
When the device is powered off, hold volume up and insert a USB cable connected to the PC
Wait for the drivers to install
Click to expand...
Click to collapse
and follow the steps 7-9.

dominik-p said:
Yes you have 10b installed now.
The XX means that it is unbranded.
SEA means southeast asia.
Win 7 is fine. Send_Command will work.
Download the zip from the above-mentioned thread.
Then:
and follow the steps 7-9.
Click to expand...
Click to collapse
so i just download it, put it at desktop and skip all the methods till 6-9? do i have to enable developer mode before doing it?

No you don't need developer mode.
But it is no problem if you enabled it.
Are you able to open the console with Send_Command.exe?

dominik-p said:
No you don't need developer mode.
But it is no problem if you enabled it.
Are you able to open the console with Send_Command.exe?
Click to expand...
Click to collapse
i opened send_command.exe but it just closes back.. mine is at COM1 but idk how to change it
Update: it says NOTE: Do not attempt this on devices with 5.1.1 , at the time this method was posted it worked on many firmware 5.0.2 should i still go for it? im using 5.1.1

We won't follow the guide. We will do it like here:
http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765
(You will also find the thread is linked there.)
The thread is just a good help for the Send_Command tool.
You don't have to change the COM port.
Are you in download mode? Do you see the "Firmware Update" screen?
Use the ports.bat and note the "netdiag" COM port.
Inside of LG_Root folder hold shift and right click a blank space you should see "Open command window here"
Click to expand...
Click to collapse
Then enter:
Code:
Send_Command.exe \\.\COM#
Replace # with your number.

dominik-p said:
We won't follow the guide. We will do it like here:
http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765
(You will also find the thread is linked there.)
The thread is just a good help for the Send_Command tool.
You don't have to change the COM port.
Are you in download mode? Do you see the "Firmware Update" screen?
User ports.bat and note the "netdiag" COM port.
Then enter:
Code:
Send_Command.exe \\.\COM#
Replace # with your number.
Click to expand...
Click to collapse
Yup its in download mode i have the firmware update on my screen.. still to no avail i also installed LG driver and restarted.. opened send_command.exe it just closes back
or do i just enter the script after the # after special command? at because im now at this part http://i.imgur.com/fre9Z9l.png just that when i double-click send command it just closes back

dreamnoob said:
Yup its in download mode i have the firmware update on my screen.. still to no avail i also installed LG driver and restarted.. opened send_command.exe it just closes back
or do i just enter the script after the # after special command? at because im now at this part http://i.imgur.com/fre9Z9l.png just that when i double-click send command it just closes back
Click to expand...
Click to collapse
are you opening send command from the command prompt?

Do NOT double click on the Send_Command.exe
READ again:
Inside of LG_Root folder hold shift and right click a blank space you should see "Open command window here"
Click to expand...
Click to collapse
Then enter "Send_Command.exe \\.\COM#"

dominik-p said:
Do NOT double click on the Send_Command.exe
READ again:
Then enter "Send_Command.exe \\.\COM#"
Click to expand...
Click to collapse
oh okay means im on the right path..
so now i just do this as follows?
Type "id" and press enter (no quotes).
You should get back some text starting with "uid=(0)root gid=(0)root". If not, press CTRL-C, and do step 9 again (the application sometimes doesn't respond on the first command).
Run the command specified in the section below titled 'Commands to Run' to flash the rooted system image.
After a few minutes of sitting, you should get back a "#" prompt. This indicates the process has finished.
Type "LEAVE" (no quotes) and press enter. Your phone should reboot, and your phone will be rooted.

[6039] - ***GUIDE*** - How to return the fastboot commands on already upgraded device

Your warranty is void. I'm not responsible if your device is hard bricked by using the procedure below. The method described below has been tested on 6039Y, 6039S, 6039H (with the archives for 6039Y) and 6039K (with the 6039S archive) and is confirmed that it works.
What to expect on successful completion:
- you will have access to the fastboot commands (removed by the latest upgrade).
- you should be able to check for OTA updates and to download them, but you will not be able to install them.
What's needed:
-------------------
1. I hate when I must say this ... but ... a Windows PC.
2. QPST version 2.7.422 (you can find it on the net as 2.7 build 422). This is a link to one such version (found through Google). If there are problems with this link please let me know. I will try to find another one (you can do it yourself too).
3. Drivers in order the device to be recognized when is in Download mode. Install Mobile Upgrade Q 4.8.7 the necessary drivers are installed with it. It can be downloaded from here.
4. The files from the archives below. Please use the archive which is especially for your device ... in theory if you use the archive for different device (e.g. the archive for 6039S on 6039Y (with the standard partitions)) you should have a repartitioned device at the end, and only the resize2fs command should be enough to start to utilize the whole memory chip ... but you will loose the possibility to sweat a little bit when do the repartitioning by following the guide for it .
- 6039Y (8GB stock partition sizes) (md5sum: 860789bedb63da5c5976c24825c29d47)
- 6039Y (repartitioned by following the repartitioning guide) (md5sum: c2f8ff3cfc683e46fbf5d797103de71b)
- 6039S (md5sum: dfd04067230b5709729c70cac61ffd52)
How to proceed:
--------------------
1. Install all the necessary software.
2. Unpack the downloaded archive for your device.
3. Power off the device. Connect it with the USB cable to the PC. Wait the battery symbol to disappear and hold both volume keys and the power button. You should see a red screen with a warning sign and a scheme. Then hold the volume up button. The display will stay lit but nothing will be shown on it from now on until the end of the procedure.
4. When the device is in Download mode under the windows device manager -> Ports (COM & LPT) you should see Android HS-USB QDLoader 9008 (COMXX)
5. Open the windows explorer and find the installation folder of QPST (mine is under Program Files (x86)\Qualcomm\QPST). From the bin sub-directory start QFIL as administrator.
6. In QFIL the COM port number as seen under the windows device manager should be selected automatically.
7. The rest must be done from QFIL:
- Programmer path: _____ - Click on the Browse button against it and from the extracted archive select prog_emmc_firehose_8916.mbn
- Search Path: _____ - if the path is not selected automatically after the programmer selection click on the Browse button against it and select the folder where the archive has been extracted.
- Load XML - click on it and first select rawprogram0.xml from the archive, then the patch0.xml file.
- Click on the Download button. The process should finish quickly (few seconds ... up to a minute). If everything is OK the phone will be restarted automatically and the fastboot commands will be available again.
(If you feel unsure to proceed or not but your device is already in download mode ... disconnect the USB cable and hold both volume keys and the power button to restart it).
Screenshots from QFIL is possible to be provided later ...

Reserved....

Alright I guess I'll be the guinea pig here.... Few questions beforehand:
I currently have the 6039Y version without having repartitioned... Using the repartitionned one would directly give me a repartitionned memory? Did I understand that correctly?
Did I dream about you saying that you might have a way to fix hard bricks? Because I might very well brick mine with my usual luck
About the updates... If there were any later OTA updates (I know it's unlikely) would there be a way to apply them still?

Rorshan said:
Alright I guess I'll be the guinea pig here.... Few questions beforehand:
I currently have the 6039Y version without having repartitioned... Using the repartitionned one would directly give me a repartitionned memory? Did I understand that correctly?
Did I dream about you saying that you might have a way to fix hard bricks? Because I might very well brick mine with my usual luck
Click to expand...
Click to collapse
In theory yes, but is untested. Yes, hard bricks should be fixable with these tools and with slightly different files. But as this requires a full copy of the memory chip and for the moment I have such copy only from my device, I can recover only my device (or others which will become the same as mine ... this means radio, languages, apps etc. ).
About the updates... If there were any later OTA updates (I know it's unlikely) would there be a way to apply them still?
Click to expand...
Click to collapse
Yes, but modified
Edit: What do I do here? I guess a missing font file shouldn't bother me, but still I'd like some advice here
Click to expand...
Click to collapse
No idea ... try with ignore. I didn't have have any problems with mobile upgrade q.

petrov.0 said:
In theory yes, but is untested. Yes, hard bricks should be fixable with these tools and with slightly different files. But as this requires a full copy of the memory chip and for the moment I have such copy only from my device, I can recover only my device (or others which will become the same as mine ... this means radio, languages, apps etc. ).
Yes, but modified
No idea ... try with ignore. I didn't have have any problems with mobile upgrade q.
Click to expand...
Click to collapse
Untested doesn't sound nice... I guess I'll go with the normal way and worry about the repartition afterwards.
I cancelled the install and reinstalled with no issue
I guess this is it. Either way I'll come here to cry, be it from joy or sadness/anger
---------- Post added at 07:46 PM ---------- Previous post was at 07:26 PM ----------
Well I'm done and my phone resetted just fine... I freaked for a minute when it took a bit longer than usual for my phone to pick up signal.
And......
fastboot -i 0x1bbb devices
48fee072 fastboot
Click to expand...
Click to collapse
I haven't tried TWRP yet since I don't really know what version I should be using... Any idea @petrov.0 ?

Rorshan said:
Untested doesn't sound nice... I guess I'll go with the normal way and worry about the repartition afterwards.
I cancelled the install and reinstalled with no issue
I guess this is it. Either way I'll come here to cry, be it from joy or sadness/anger
---------- Post added at 07:46 PM ---------- Previous post was at 07:26 PM ----------
Well I'm done and my phone resetted just fine... I freaked for a minute when it took a bit longer than usual for my phone to pick up signal.
And......
I haven't tried TWRP yet since I don't really know what version I should be using... Any idea @petrov.0 ?
Click to expand...
Click to collapse
For normal use (flashing) the latest from 12.09.2015. For the repartitioning boot with the one from the repartitioning thread.

Thanks! I will try it now!
EDIT:
It all works

petrov.0 said:
For normal use (flashing) the latest from 12.09.2015. For the repartitioning boot with the one from the repartitioning thread.
Click to expand...
Click to collapse
Alright TWRP seems to work fine, I'm doing backups at the moment. Thank you so much! You're such a lifesaver. Quick last question... I think I'm going to root and repartition. Does it matter at all which I do first?

Rorshan said:
Alright TWRP seems to work fine, I'm doing backups at the moment. Thank you so much! You're such a lifesaver. Quick last question... I think I'm going to root and repartition. Does it matter at all which I do first?
Click to expand...
Click to collapse
This question is for the other thread ... but no, it doesn't matter.

Do you feel its safe to test this on 6039s?

xStealth said:
Do you feel its safe to test this on 6039s?
Click to expand...
Click to collapse
Well good question. The files for the S have been generated only on the base of the partition numbers (not their names) and their sizes ... they look the same as those on the Y but ... I think it's safe.

xStealth said:
Do you feel its safe to test this on 6039s?
Click to expand...
Click to collapse
Can further confirm that this worked on my 6039S. No bricking, and fastboot works as promised!
A BIG thanks petrov.0!

Bradlee22 said:
Can further confirm that this worked on my 6039S. No bricking, and fastboot works as promised!
A BIG thanks petrov.0!
Click to expand...
Click to collapse
He already did this. Read the first line from the first post.

petrov.0 said:
He already did this. Read the first line from the first post.
Click to expand...
Click to collapse
Oh, right on. I wasn't sure who had confirmed it at that point. Thanks again for all your work on this!

Update
The link and the md5sum in the first post for the repartitioned 6039Y have been updated as one of the files was missing from the archive. Thanks @kkkk2222 for finding the error.

Worked a treat, fantastic work folks.
http://www.modaco.com/news/android/you-can-turn-your-8gb-idol-3-47-into-a-16gb-really-r1521/
Used Parallels on a Mac, no problem!
P

@petrov.0
For those who end up stuck in bootloops(on both 6039's and 6045's) with factory recovery is there a way this method could be used to either 1) flash twrp to the device or 2) force the device into bootloader?
If a user can get to bootloader (and has fastboot) then they could attempt to fix their own issue.

famewolf said:
@petrov.0
For those who end up stuck in bootloops(on both 6039's and 6045's) with factory recovery is there a way this method could be used to either 1) flash twrp to the device or 2) force the device into bootloader?
If a user can get to bootloader (and has fastboot) then they could attempt to fix their own issue.
Click to expand...
Click to collapse
1. Yes, it should be possible by using the same tools with different files. But if they flash their system image backup this will lead to a big mess ... they will have a partially upgraded device. Probably if they use the fix permissions option or force the reinstall of SuperSU from the recovery this will be the end of the bootloops (these are unconfirmed speculations though). I need the gpt table from the device (6045) to generate the necessary files.
Code:
dd if=/dev/mmcblk0 of=<path to the sd_card>/gpt.bin bs=512 count=34
2. No.

petrov.0, first of all - thx for your great work. I have a theoretical question about QFIL and partition flashing. Is it necessary to flash all of this partitions in rawprogram0.xml:
sbl1.mbn
rpm.mbn
tz.mbn
hyp.mbn
aboot.mbn
gpt_main0.bin
gpt_backup0.bin
For working fastboot we need only aboot (emmc_appsboot) from previous firmware version (or i'm wrong?), if we short rawprogram0.xml only for aboot and gpt, like this:
Code:
<?xml version="1.0" ?>
<data>
<!--NOTE: This is an ** Autogenerated file **-->
<!--NOTE: Sector size is 512bytes-->
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="aboot.mbn" label="aboot" num_partition_sectors="2048" physical_partition_number="0" size_in_KB="1024.0" sparse="false" start_byte_hex="0xc18c000" start_sector="396384"/>
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="aboot.mbn" label="abootbak" num_partition_sectors="2048" physical_partition_number="0" size_in_KB="1024.0" sparse="false" start_byte_hex="0xc28c000" start_sector="398432"/>
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="gpt_main0.bin" label="PrimaryGPT" num_partition_sectors="34" physical_partition_number="0" size_in_KB="17.0" sparse="false" start_byte_hex="0x0" start_sector="0"/>
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="gpt_backup0.bin" label="BackupGPT" num_partition_sectors="33" physical_partition_number="0" size_in_KB="16.5" sparse="false" start_byte_hex="(512*NUM_DISK_SECTORS)-16896." start_sector="NUM_DISK_SECTORS-33."/>
</data>
Phone doesn't brick after flashing?
p.s. And another one question. Do you know where the testpoint on 6039Y located? After several my experiments (not with your files, i was bricked it by myself i have bricked phone. There is no download mode (9008 com port not appears in my case), only turned on LED on front panel. Any actions with holding both volume buttons and power button doesn't get success, i think in this case testpoint will help. But i don't know where is it. If somebody need - i can attach photo of PCB.

petrov.0 said:
1. Yes, it should be possible by using the same tools with different files. But if they flash their system image backup this will lead to a big mess ... they will have a partially upgraded device. Probably if they use the fix permissions option or force the reinstall of SuperSU from the recovery this will be the end of the bootloops (these are unconfirmed speculations though). I need the gpt table from the device (6045) to generate the necessary files.
Code:
dd if=/dev/mmcblk0 of=<path to the sd_card>/gpt.bin bs=512 count=34
2. No.
Click to expand...
Click to collapse
Code:
/mmcblk0 of=/storage/sdcard1/gpt.bin bs=512 count=34 <
dd: /dev/mmcblk0: No such file or directory
Now a cat of /proc/partitions shows 179 0 15267840 mmcblk0 so I have no idea why it says it's not found. [I can confirm none of the mmc* are under /dev. I have a find running to see where it says it is.....ok..for us it's in /dev/block/mmcblk0 ]
Just drop .zip off the end of the name..it's not actually zipped but couldn't upload a .bin.

Can someone with a rooted stock rom pull mmcblk0 via adb

Already extracted mmcblk0 can be found on the following thread here
Can someone with a rooted stock rom please pull the following partition and upload it here
Requirements
Rooted moto g5
TWRP recovery
Blank micro sd card (at least 32gb)
make sure adb debugging in enabled in dev options
enter TWRP recovery
Follow instructions from here but amend the extract command with the values given below
https://forum.xda-developers.com/showpost.php?p=76795590&postcount=1
If you have a 32gb varient use
dd if=/dev/block/mmcblk0 of=/storage/<STORAGE-ID>/mmcblk0.img bs=1048576 count=29820
and if you have a 16gb varient use
dd if=/dev/block/mmcblk0 of=/storage/<STORAGE-ID>/mmcblk0.img bs=1048576 count=14910
Please note this partition will be very large so compress it in a zip file as best you can and you will obviously need good internet connection and file storage to upload it
Please also enclude what varient the mmcblk0 was taken from with your upload

How to here
https://forum.xda-developers.com/showpost.php?p=76795590&postcount=1

but what we need is someone who has a motorola g5 cedric xt1671 that has root and twrp and can provide us with that file to be able to revive our cell phones

I don't have the stock ROM will it be fine

abhimanyuk said:
I don't have the stock ROM will it be fine
Click to expand...
Click to collapse
Prefer stock but it should work if you have a custom rom too

TheFixItMan said:
Prefer stock but it should work if you have a custom rom too
Click to expand...
Click to collapse
But it will include my device all info like imei serial number etc.
Will it be safe.

abhimanyuk said:
But it will include my device all info like imei serial number etc.
Will it be safe.
Click to expand...
Click to collapse
I'm asking for the bootloader block - I believe imei is on another partition
Either way it's up to you if you want to provide files
Google and research

TheFixItMan said:
I'm asking for the bootloader block - I believe imei is on another partition
Either way it's up to you if you want to provide files
Google and research
Click to expand...
Click to collapse
I was getting an error with that command so I have listed out all the partitions you can let me know which partition you need.
Device : XT1677
Variant: Amazon
ROM: Custom

abhimanyuk said:
I was getting an error with that command so I have listed out all the partitions you can let me know which partition you need.
Device : XT1677
Variant: Amazon
ROM: Custom
Click to expand...
Click to collapse
Try using the instructions here
With my method you probably have to mount the partition & I can't remember the commands
https://forum.xda-developers.com/showpost.php?p=76795590&postcount=1
If you don't have Linux/Ubuntu I presume you can use the terminal window in twrp - as long as it can get root access but better using Linux/Ubuntu either as stand alone or a virtual machine

TheFixItMan said:
Try using the instructions here
With my method you probably have to mount the partition & I can't remember the commands
https://forum.xda-developers.com/showpost.php?p=76795590&postcount=1
If you don't have Linux/Ubuntu I presume you can use the terminal window in twrp - as long as it can get root access but better using Linux/Ubuntu either as stand alone or a virtual machine
Click to expand...
Click to collapse
I have Linux installed. I will do that tomorrow Hope we will get the desired result.

Can anyone create a link for me to download this mmcdlk0 for the bike g5 xt 1672? because I need to put in a micro, so I recover my defective device in the bootloader. Thank you!

I'm still waiting for someone to provide the mmcblk0 partition
If you have a working rooted moto g5 see the first post

what's new, nobody could get the mmcblk0 file or esque do not want to help, this is the last straw.
just because I do not have another motorcycle g5 but towards the attempt, but good.
but it will be necessary to take it with a technician to the end that already came out a method to revive it through a box precisely Medussa pro, but we see light in that help us in this I think it will be the only alternative so far, or wait for the blank to come out flash that as I see it will take time.
what's new, nobody could get the mmcblk0 file or esque do not want to help, this is the last straw.
just because I do not have another motorcycle g5 but towards the attempt, but good.
but it will be necessary to take it with a technician to the end that already came out a method to revive it through a box precisely Medussa pro, but we see light in that help us in this I think it will be the only alternative so far, or wait for the blank to come out flash that as I see it will take time.
---------- Post added at 03:15 AM ---------- Previous post was at 03:11 AM ----------
https://www.youtube.com/watch?v=rJGsZuWkboo

You did it ?
gugsta said:
Can anyone create a link for me to download this mmcdlk0 for the bike g5 xt 1672? because I need to put in a micro, so I recover my defective device in the bootloader. Thank you!
Click to expand...
Click to collapse
You did it ? I'm having the same problem with the bike g5 xt1672 could you help me

dalissonetcaf said:
You did it ? I'm having the same problem with the bike g5 xt1672 could you help me
Click to expand...
Click to collapse
We are awaiting someone to upload the mmcblk0 partition for this device
Until that happens there is currently no known solutionn (other than motherboard replacement or specialist flash boxes) to revive a moto g5 with no access to the bootloader

Hi, I'm trying to make the mmcblk0.img but with the bs and count that says in the g5 forum, it only weighs 4GB.
can you give me the data
I think it has to do with the ram, the G5S is 3.

Happiness777 said:
Hi, I'm trying to make the mmcblk0.img but with the bs and count that says in the g5 forum, it only weighs 4GB.
can you give me the data
I think it has to do with the ram, the G5S is 3.
Click to expand...
Click to collapse
It's because of the file system. Fat32 can only handle files up to 4GB. Best way to get around this, is to first format the sdcard in exFAT or ext4 on your computer (sdcard reader).

Here is a mmcblk0 image someone sent me
Unzip it
Use an sd card boot image tool to create a bootable sdcard with the image (one that can handle a dd image)
You may need to format the sd card to ext4
If it works it may take a long time before it does boot from sd card
mmcblk0.zip
See below for how to write image
https://www.embeddedarm.com/blog/how-to-write-an-sd-card-image-linux-windows-mac-osx/

my mmcblk0 weighs 27.9 Gb (30,000,000,000)
Is it the right size?

Happiness777 said:
Friend and created the mmcblk0 but I am in doubt if the size is accurate
Click to expand...
Click to collapse
Either that link doesn't work or it's not accessible to me
Make sure the sd card is formatted to ext4 when you create the image
The image I posted is 15gb (once unzipped) but since I don't have this device I can't check it

Razer is bricked, please help. Need complete emmc image.

Bricked my razer a while back reinstalling the stock firmware. The cable unplugged from the phone and corrupted the storage. Cant enter recovery or bootloader. But according to some resources that i came across while doing some research, im able to interface with the device using the qualcomm hs-usb protocol. With that im able to directly access the devices storage. If anyone is willing to help, what id need is for you to wipe your device clean, and run these commands
Adb shell
Su
dd if=/dev/block/mmcblk0 of=/storage/sdcard1/backup.img bs=512 count=30535646
From there id be able to delete the partition table, and copy the devices storage config from the backup. Once thats established id be able to access bootloader recovery and system.
If anyone is able to help, id really appreciate it
Thanks

i too have done the exact same now stuck with a brick hope someone can help

slavix66 said:
Bricked my razer a while back reinstalling the stock firmware. The cable unplugged from the phone and corrupted the storage. Cant enter recovery or bootloader. But according to some resources that i came across while doing some research, im able to interface with the device using the qualcomm hs-usb protocol. With that im able to directly access the devices storage. If anyone is willing to help, what id need is for you to wipe your device clean, and run these commands
Adb shell
Su
dd if=/dev/block/mmcblk0 of=/storage/sdcard1/backup.img bs=512 count=30535646
From there id be able to delete the partition table, and copy the devices storage config from the backup. Once thats established id be able to access bootloader recovery and system.
If anyone is able to help, id really appreciate it
Thanks
Click to expand...
Click to collapse
hi any look on finding emmc or a work around for this?.i been at it all day i even resorted to opening device up to disconnect battery...nothing

parky169 said:
hi any look on finding emmc or a work around for this?.i been at it all day i even resorted to opening device up to disconnect battery...nothing
Click to expand...
Click to collapse
Nope nothing yet, we need either emmc development files for the phone, no likely to find. And with the qualcomm tools the corrupted storage can be re partitioned and again be written to.
However if someone with a working razer was to wipe the device clean, and dump partition info. Then the images can be written to the device, over writing the damaged partitions.

Black screen on my razer phone. can't access download or recovery. any help will be greatly appreciated. the computer makes a sound when I plug in the razer phone.

sinkoo1979 said:
Black screen on my razer phone. can't access download or recovery. any help will be greatly appreciated. the computer makes a sound when I plug in the razer phone.
Click to expand...
Click to collapse
Your razer is in a state known as EDL. I5s the qualcomm Emergency Download mode. Used to program your emmc storage. That is exactly what the few of us are experiencing, however with no owners of the device willing to share a default wiped image of their emmc, there is no way for us to remap the partitions appropriately in order to once again flash and access the bootloader.

If you could let me know how one would do it I might be able to help you before I sell my razer phone

Thank you, if you restore your phone back to factory settings, connect to pc via adb and run the command in the initial post. That command should (from what i read elsewhere) create a full backup of the partitions on your device. If you are successfull and are able to share through some cloud storage such as dropbox or something of the like, i should be able to restore my razer.

slavix66 said:
Thank you, if you restore your phone back to factory settings, connect to pc via adb and run the command in the initial post. That command should (from what i read elsewhere) create a full backup of the partitions on your device. If you are successfull and are able to share through some cloud storage such as dropbox or something of the like, i should be able to restore my razer.
Click to expand...
Click to collapse
im guessing i will need root to run those commands, atm i am performing a full nandroid backup of everything before i do the reset, my phone is rooted and has twrp installed on both a and b partions

extracted the files, the img is 13GB so gonna compress it before i upload it, hopefully it should work but will have to be tomorrow now

uploading the file now

ok done, heres the link
http://www.mediafire.com/file/j3j6pp3ym161t0q/backup.7z/file
you will need 7zip to extract it which you can get from here for free www.7zip.org

slavix66 said:
Bricked my razer a while back reinstalling the stock firmware. The cable unplugged from the phone and corrupted the storage. Cant enter recovery or bootloader. But according to some resources that i came across while doing some research, im able to interface with the device using the qualcomm hs-usb protocol. With that im able to directly access the devices storage. If anyone is willing to help, what id need is for you to wipe your device clean, and run these commands
Adb shell
Su
dd if=/dev/block/mmcblk0 of=/storage/sdcard1/backup.img bs=512 count=30535646
From there id be able to delete the partition table, and copy the devices storage config from the backup. Once thats established id be able to access bootloader recovery and system.
If anyone is able to help, id really appreciate it
Thanks
Click to expand...
Click to collapse
hi xda member dtronics has very kindly uploaded a complete back up approx 13gb
file.do you know how to use this to restore/repair our phones?.

Excellent, i will take a look and see if i can push it to the device in edl mode. The thread has been dead for a while, so it may take a while for me to review all the previous resources that led me to the point where i had posted this thread.
Thank you so very much!

This is the article I was using to attempt salvaging my phone.
https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Unfortunately I am in the EDL mode where my device storage is not recognized, so I am unable to tamper with it until the razer phones flash programmer or firehose files have been leaked.
Hopefully someone else may have success resurrecting their device using dtronic's backup and or with the information provided in the link.
Thank you any and all of you who have contributed or followed the thread. But my trail ends here unless the flash programmer files are somehow made available.

Unfortunately sadly I too couldn't work out a way to flash or recover razer phone with the upload from dtronics.thank you to all involved,but I think it's time to chuck the old razer in the bin.this is my first ever failure or perm bricked device since I started rooting etc with the HTC wildfire.
?

Tried Klinik handphone medan (google search). They have firehose for msm 8998 but I removed the usb cable when it was flashing (didn't look like it was flashing anything) now the computer don't even recognize the phone....
getting this message "Unknown USB Device (Device Descriptor Request Failed)".

parky169 said:
Unfortunately sadly I too couldn't work out a way to flash or recover razer phone with the upload from dtronics.thank you to all involved,but I think it's time to chuck the old razer in the bin.this is my first ever failure or perm bricked device since I started rooting etc with the HTC wildfire.
Click to expand...
Click to collapse
is there any way to pull the firehose and xml file from working razer phone? getting another one for cheap.
---------- Post added at 04:07 AM ---------- Previous post was at 04:07 AM ----------
slavix66 said:
This is the article I was using to attempt salvaging my phone.
https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Unfortunately I am in the EDL mode where my device storage is not recognized, so I am unable to tamper with it until the razer phones flash programmer or firehose files have been leaked.
Hopefully someone else may have success resurrecting their device using dtronic's backup and or with the information provided in the link.
Thank you any and all of you who have contributed or followed the thread. But my trail ends here unless the flash programmer files are somehow made available.
Click to expand...
Click to collapse
is there any way to pull the firehose and xml file from working razer phone? getting another one for cheap.

sinkoo1979 said:
is there any way to pull the firehose and xml file from working razer phone? getting another one for cheap.
---------- Post added at 04:07 AM ---------- Previous post was at 04:07 AM ----------
is there any way to pull the firehose and xml file from working razer phone? getting another one for cheap.
Click to expand...
Click to collapse
I wouldnt know for sure. But my understanding is the programmer files (firehose or sahara files) arent stored on the device. They are used by programmer interface to identify the processor as well as the storage media, possibly all harware for the device. If this were a more mainstream device the programmer files may have been available to us through a leak. Only way to fix it at this point would be to bring it to a shop, they should have access to the files one way or another.

I don't know, I don't have my razer phone any more, went and got myself a OnePlus 6t, the emmc file is still available to download from my post and still looking for people to mirror the file

One of the BEST things you can do to Moto Z Play XDA Community (Takes a while! ;) )

EDIT: THE DEVDB PROJECT HAS RISEN UP!
https://forum.xda-developers.com/moto-z-play/development/project-real-unbrick-hard-bricked-moto-t3927107
This is so easy to do, and can be sooo helpful if one day You will end with hard-brick.
If you have any questions send me a private message. :good:
Hey! My name is Jacob and I must tell you that there is one common problem with Moto Z Play - OTA after downgroading results in hardbrick :silly:
I have also bricked my device some days ago, since then I have gathered interesting info, probably all old and not so old blankflash files (these were used in the past to unbrick, but don't work now) and two tools, that allowed me to make proper rawprogram0, patch0 and gpt_main0.bin needed for making files, that will allow everyone to unbrick.
But this can be worth nothing without your help. Problem with unbricking, is that last OTA, updated chip security making unable to flash older chip firmware rendering all flashfiles useless. To make new one, I must get some files that are not present in the internet, but are present in ALL working phones. All I need is full mmcblk0 backup. If you want to help follow these easy-peasy instructions:
INFO: Procedure bellow excludes EFS, MODEMST1, MODEMST2, FSG, BACKUP partitions from backup. These are your phone specific partitions, that contain sensitive information like IMEI, serial numbers etc, but this guide shows how to avoid them while backing up so you don't have to worry about it
Prerequisites:
1. Your phone might be rooted (but doesn't have to be), definitelly should be working and not messed up too much.
2. You must have at least 32 GB micro sd card
3. Any ROM, even custom will be good, but if you have stock, you get +1 point
Steps:
1. If you have TWRP recovery, boot into it and go to step 2.
If you don't have, here is official one https://eu.dl.twrp.me/addison/ - rename it to "twrp.img" and boot to it with
Code:
fastboot boot twrp.img
2. Backup your /data partition and keep it in safe place
3. Format sdcard in ext4 (it is more robust and failsafe) or FAT32/exFAT (if you are on windows).[/URL]
4. Wipe /data on your phone and insert sdcard. Under "Mount" tab in TWRP, check box next to SD-CARD.
5. Open TWRP terminal emulator (It is in advamced tab), type "su" and run these command:
If you trust me that I won't do bad things with your IMEI:
Code:
dd if=/dev/block/mmcblk0 of=/[U][I]"Ext sd location here"[/I][/U]/Loader.img bs=4096
This just makes full-backup of your all partitions from Qualcomm chip.
OR
If you don't trust me:
Code:
dd if=/dev/block/mmcblk0p[B][COLOR="Red"]X[/COLOR][/B] of=/[B][COLOR="DeepSkyBlue"]Y[/COLOR][/B]/mmcblk0p[COLOR="Red"]X[/COLOR] bs=4096
Where X is number of partition from 1 to 54 BUT NOT: 27 (modemst1), 28 (modemst2), 29 (fsg)
and Y is location of your SD-CARD. This will only back up partitions without IMEI, and other phone-specific info.
6 Generated files will be HUGE (~27GB). Copy them to pc and upload to cloud. Maby https://mega.nz/ - probably only they have enough space for that file for free.
7 Post link here or send it to me via Private Message.
8 That's all! If you managed to get here, all comunity is grateful, :highfive: you will be included as biggest contribuor to the new thread I will make in near future!

If I find the time I will throw my old Z Play back to stock and try this. But can take a while before I have that time. Especially uploading that amount of data which would take me at least 12 hours. So if I do that, I will most likely get it into a split archive

Unfortunately I don't have a 32Gb sdcard. If there's another way to do this, I'm willing to help

Camarda said:
Unfortunately I don't have a 32Gb sdcard. If there's another way to do this, I'm willing to help
Click to expand...
Click to collapse
The only other way I know would be a USB C OTG adapter and a USB stick...

Artim_96 said:
If I find the time I will throw my old Z Play back to stock and try this. But can take a while before I have that time. Especially uploading that amount of data which would take me at least 12 hours. So if I do that, I will most likely get it into a split archive
Click to expand...
Click to collapse
Camarda said:
Unfortunately I don't have a 32Gb sdcard. If there's another way to do this, I'm willing to help
Click to expand...
Click to collapse
Thank you very much guys! You don't even know how much did you motivated me to continue research when I got your responses. If you will have any problem, ask me for advice - I will try to help. :highfive:
In case of Artim_96, you probably know this one, but to split dd image, you can use (obviously) "skip" parameter, for example:
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_1.img bs=4096 count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_2.img bs=4096 skip=10GB count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_3.img bs=4096 skip=20GB count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_4.img bs=4096 skip=30GB
In case of Camarda: ...
Code:
adb -d shell su -c busybox dd if=/dev/block/mmcblk0 bs=4096 > D:\mmc.bin
... should do the job, where "D:\mmc.bin" can be any other valid location on your pc.
To make this work, you must have root and busybox installed.

Bobernator said:
In case of Artim_96, you probably know this one, but to split dd image, you can use (obviously) "skip" parameter, for example:
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_1.img bs=4096 count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_2.img bs=4096 skip=10GB count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_3.img bs=4096 skip=20GB count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_4.img bs=4096 skip=30GB
Click to expand...
Click to collapse
that would be a solution, but I guess it's way easier to create one image, zip it and let it get split to about 5 GB chunks, and probably creating a check sum for each before upload
---------- Post added at 17:02 ---------- Previous post was at 16:56 ----------
but what I don't get: I should make a backup of /data, for what? And then I should connect the phone to my PC, but the following commands look very much like linux commands, so the connection to PC seems unneccessary. Plus, for what reason does the SD Card need to be ext4? the commands should work with exFAT too plus no windows system can read ext4. And there is no program to read it for Windows that's slow as hell

Artim_96 said:
that would be a solution, but I guess it's way easier to create one image, zip it and let it get split to about 5 GB chunks, and probably creating a check sum for each before upload
---------- Post added at 17:02 ---------- Previous post was at 16:56 ----------
but what I don't get: I should make a backup of /data, for what? And then I should connect the phone to my PC, but the following commands look very much like linux commands, so the connection to PC seems unneccessary. Plus, for what reason does the SD Card need to be ext4? the commands should work with exFAT too plus no windows system can read ext4. And there is no program to read it for Windows that's slow as hell
Click to expand...
Click to collapse
Sorry, I was in a bit hurry when I was writing tutorial. I have just corected misteakes in it. :silly:
That part with backing up /data and wiping it is just for Your comfort - You probably don't want to include all you photos, videos contacts etc, in the backup, I am wrong?
EDIT: You are right, solution with splitting archive is clearly better, becouse of smaller size and auto merging archives

Bobernator said:
Sorry, I was in a bit hurry when I was writing tutorial. I have just corected misteakes in it. :silly:
That part with backing up /data and wiping it is just for Your comfort - You probably don't want to include all you photos, videos contacts etc, in the backup, I am wrong?
EDIT: You are right, solution with splitting archive is clearly better, because of smaller size and auto merging archives
Click to expand...
Click to collapse
Would it help you to get /data too? It's my old phone, screen is quite damaged so there is nothing worth looking for on it. Plus it was completely wiped twice by flashing the firmware with flashfile and unlocking the bootloader again since flashing the firmware locked it.

Data partition is absolutely not needed, but thanks for asking!

zip compressing was totally worth it. It went from 29.1 GB to just 2.58 GB?

Artim_96 said:
zip compressing was totally worth it. It went from 29.1 GB to just 2.58 GB?
Click to expand...
Click to collapse
Thanks for support!
@Camarda - You are from Brasil, so you probably have different version of software, so if you will upload it, phones outside of Europe can be safed too. Do you still want to help?

Bobernator said:
Thanks for support!
@Camarda - You are from Brasil, so you probably have different version of software, so if you will upload it, phones outside of Europe can be safed too. Do you still want to help?
Click to expand...
Click to collapse
I just sent you the file, tell me if everything is ok

Thank you! Artim's backup is not working on my phone, and I suddenly realised that my exam ending my school are in less than month (!), so I didn't have time neither to write a thread, nor to reverse engineer the file, but I will try to find time and test your backup!
Ps. Don't worry about me beeing temporiarly inactive, this thread is my current target and I won't give up!

Bobernator said:
Thank you! Artim's backup is not working on my phone, and I suddenly realised that my exam ending my school are in less than month (!), so I didn't have time neither to write a thread, nor to reverse engineer the file, but I will try to find time and test your backup!
Ps. Don't worry about me beeing temporiarly inactive, this thread is my current target and I won't give up!
Click to expand...
Click to collapse
Bobernator, I'm just posting to let you know that I am very thankful for your efforts and to take as long as you need. I have a LATAM XT1635-02 that got bricked by an automatic update quite a few months ago. It's in fastboot state. If there is anything I can do to help, let me know.
I now own a XT1710-06, so if you think the files from it could be useful, let me know.

Welcome again! My exams have just ended (I hope they went well) I am temporally at my uncle's house so I don't have access to files and info I've gathered, but I will return to home at friday and even Easter will not stop me, becouse I have decided to start DevXDA project!
Stay with me guys

Fulcano said:
Bobernator, I'm just posting to let you know that I am very thankful for your efforts and to take as long as you need. I have a LATAM XT1635-02 that got bricked by an automatic update quite a few months ago. It's in fastboot state. If there is anything I can do to help, let me know.
I now own a XT1710-06, so if you think the files from it could be useful, let me know.
Click to expand...
Click to collapse
I think I you can easly fix your phone, since fastboot works. You will need factory update zip, it is pinned somewhere in this forum, but if you feel unsure (you can brick phone even harder with this method if it goes wrong), I can assist you during the weekend and share a link with correct zip.
And thanks for support!
Device which you have is Moto Z2 Play (albus) that have next version of the chip in Moto Z Play (addison). My plan is to fix addison by combining some of the firmware from it and albus, but these files are available freely and you don't need to send them.

Bobernator said:
I think I you can easly fix your phone, since fastboot works. You will need factory update zip, it is pinned somewhere in this forum, but if you feel unsure (you can brick phone even harder with this method if it goes wrong), I can assist you during the weekend and share a link with correct zip.
And thanks for support!
Device which you have is Moto Z2 Play (albus) that have next version of the chip in Moto Z Play (addison). My plan is to fix addison by combining some of the firmware from it and albus, but these files are available freely and you don't need to send them.
Click to expand...
Click to collapse
Thanks for the reply! Sorry, i've been quite busy with exams as well.
It's been a while since the phone is bricked, and i think fastboot was the wrong word. When it is plugged in it appears as a qualcomm device and the LED blinks, but other than that the phone does absolutely nothing. I remember being unable to unbrick it because of needing a `programmer.pem` file specific to the version of android that was installed.
The phone had an unlocked bootloader, twrp and supersu. It got stuck during an OEM update from 7.1.1 (i think) to 8.0.0. It was stuck for over four hours, I turned it off by force and then it never turned on again .
With regards to the Moto Z2 files, that's fantastic to hear. If there's anything else I can do to help, please say so. I've configured email alerts now so i'll get notified when you reply .
Thanks for the effort!