H811 (Tmobile G4) stuck in bootloop, can only enter download mode - G4 Q&A, Help & Troubleshooting

I can't enter recovery, only download mode. Using the send_command.exe tool, i am able to log in and dig around the file system. looks like my /dev filesystem is completely wiped out:
#df
Filesystem Size Used Free Blksize
/dev 1.37G 8.00K 1.37G 4096
/system 4.05G 3.14G 937.16M 4096
/cache 1.17G 2.04M 1.16G 4096
/data 22.73G 370.52M 22.37G 4096
/persist 27.48M 56.00K 27.43M 4096
#
notice that /dev is only 8.00K large (out of 1.37G). I have backups of all the partitions images on my hard drive and external SD card, trouble is i dont know how to restore those images as only download mode works. I have tried to re-flash a stock h811 KDZ using the LG Flash Tool 2014, which re-flashes fine, but still stick in bootloop. anyone have any ideas as to how i should proceed from where?

duuuuudeeeeeeeee

sidog said:
I can't enter recovery, only download mode. Using the send_command.exe tool, i am able to log in and dig around the file system. looks like my /dev filesystem is completely wiped out:
#df
Filesystem Size Used Free Blksize
/dev 1.37G 8.00K 1.37G 4096
/system 4.05G 3.14G 937.16M 4096
/cache 1.17G 2.04M 1.16G 4096
/data 22.73G 370.52M 22.37G 4096
/persist 27.48M 56.00K 27.43M 4096
#
notice that /dev is only 8.00K large (out of 1.37G). I have backups of all the partitions images on my hard drive and external SD card, trouble is i dont know how to restore those images as only download mode works. I have tried to re-flash a stock h811 KDZ using the LG Flash Tool 2014, which re-flashes fine, but still stick in bootloop. anyone have any ideas as to how i should proceed from where?
Click to expand...
Click to collapse
Did you factory reset after flashing the KDZ? Don't know if it makes any difference, was the KDZ the same version as was already on phone?

When I go to the factory reset option, my phone simply reboots - and foes back to its reboot loop. No recovery, all iI can do is enter simply enter download mode

What does it show up under device manager?
Sent from my LG-H811 using Tapatalk

device manager:
portable devices - LGE Android MTP Device
ports - LGE Mobile USB SErial Port
I'm thinking that if I can copy my .img backup files into the device, or mount the the external SD card while in the 'send_command.exe' interface, I can try to 'dd' restore eventually.

KDZ was the same as my phone (h811)

sidog said:
KDZ was the same as my phone (h811)
Click to expand...
Click to collapse
10a 10b 10c 10d? What version of the kdz for H811 did you have and which did you flash? Make sure they are the same.

H81110H_00.kdz - 10H, which is the same version as my phone.

sidog said:
H81110H_00.kdz - 10H, which is the same version as my phone.
Click to expand...
Click to collapse
Have you tried LG bridge on your PC? if it detects your phone, try to update it from there

yup, tried LG Bridge, it's just a light version of LG Support Tool...doesn't detect my phone...please note, I can only enter download mode

@sidog while your phone is bootlooping you can access adb and copy all your image backups back to your internal sdcard then dd them back to their various partitions
Sent from my LG-H815 using Tapatalk

i guess it depends on the nature of the boot loop culprit, but i myself cannot access adb at ANY time. ..... god does i've tried...is there something that i'm missing here?

did you find a solution to this? I'm kind of in the same boat...

nope, i'm still stuck...

Fix here:
http://forum.xda-developers.com/showthread.php?t=3107848
Sent from my LG-H811 using Tapatalk

that kdz flash method does NOT work for me. That was one of the first thing I tried. Flashed on multiple diff computers w/ no luck. As a last ditch effort, i even tried to flash the H810 model (HUGE MISTAKE). Now my phone won't even turn on

sidog said:
that kdz flash method does NOT work for me. That was one of the first thing I tried. Flashed on multiple diff computers w/ no luck. As a last ditch effort, i even tried to flash the H810 model (HUGE MISTAKE). Now my phone won't even turn on
Click to expand...
Click to collapse
Not good. Call LG for warranty replacement or your carrier.

it was a bad craigslist purchase on my part (bad imei after 2 months). Tried to salvage the situation but zero'ing on the imei but looks like I hard bricked it in the process. I'm just gonna but this brick in the closet until someone comes up w/ a solution (i kindda doubt it at this point, but you never know).

sidog said:
it was a bad craigslist purchase on my part (bad imei after 2 months). Tried to salvage the situation but zero'ing on the imei but looks like I hard bricked it in the process. I'm just gonna but this brick in the closet until someone comes up w/ a solution (i kindda doubt it at this point, but you never know).
Click to expand...
Click to collapse
Have u at least tried calling LG?
Sent from my LG-H811 using Tapatalk

Related

How to backup your modem.

There is a modem for the optimus G here:
http://downloads.codefi.re/houstonn/lgog/modem/E975_E977_E976
but it is from firmware 10b. You may want to try if it works better than your firmware. In this case, it is better if you make a backup of your current modem firmware, so you can go back to your version. Here I will write instructions to backup your modem, so you can restore it if you need.
Probably some of you know this already and feel like these are old news, but maybe we can build a modem firmware library.
You need root and a way to make an adb connection to your phone. If you cannot use adb, you can always use a terminal emulator on your phone, but this makes it a bit harder to type the commands. Also, this is for people who understand what they are doing. If after reading the tutorial you don't understand what the commands do, please don't try it. Or at least don't make me responsible if your phone bricks. Here we go.
NON NEEDED STEPS: This steps are here to show why this works.
1-Connect to your phone by adb.
2- On the terminal type :
Code:
mount
You'll see the following (amongst other things):
Code:
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,context=u:object_r:radio_efs_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
This means that the partition containing the firmware is /dev/block/platform/msm_sdcc.1/by-name/modem and it is mounted at /firmware.
NEEDED STEPS
1- Connect by adb
2- On the terminal type
Code:
su
Check if confirmation is needed on the phone screen. If needed, accept.
3-
On the terminal type:
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/modem.img
4-You will receive the following after some seconds:
Code:
131072+0 records in
131072+0 records out
67108864 bytes transferred in 29.959 secs (2240023 bytes/sec)
5-Type
Code:
exit
exit
adb pull /sdcard/modem.img
6-Now you have your backup.
HOW TO PACK THIS BACKUP FOR FLASH:
1-Download the file: cwm-lgog_e975-europe-10b_modem.zip from http://downloads.codefi.re/houstonn/lgog/modem/E975_E977_E976
2-Open the zip file and replace the existing modem.img with your file
3-Rename the file to something meaningful, like cwm-lgog_e975-europe-10f_modem.zip
After these steps, you should be able to flash any modem, knowing that you can go back to your old version.
You can upload the packed files here, so we can have a library. I will upload the modem from european 10f version here. I tested it and it works correctly, but I won't take any responsibility for what you do with this file.
Good luck.
All this info is obtained from examining the houstonn LGOG modem flasher from team codefire, so all thanks go to them. Thanks.
Very nice tutorial man. It will help newbies like me to back up and restore our modem.img, especially those who have F180* phones that wants or being converted to E975. Nice job. :good:
Nice,i'll add this to the Freaking Annoying Questions.
Sent from Asylum via LG E975/smart phones,dumb people.
Nice job.. Its work in e977 with 10a firmware?
Thx.
Sent from my LG-E975 using xda app-developers app
You should be able to backup your e977 modem following this tutorial.
renatonolo said:
Nice job.. Its work in e977 with 10a firmware?
Thx.
Sent from my LG-E975 using xda app-developers app
Click to expand...
Click to collapse
could you please do the same thing for the misc partition and upload it somewhere?
I saw that freegee is touching this one so please mention if your phone was opened with freegee.
sonty said:
could you please do the same thing for the misc partition and upload it somewhere?
I saw that freegee is touching this one so please mention if your phone was opened with freegee.
Click to expand...
Click to collapse
I am sorry, I am not going to upload my misc partition, as this partition contains my IMEI.
I can, however, tell you how to backup it:
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/misc of=/sdcard/misc.img
Can I ask why you need that?
dapaua said:
I am sorry, I am not going to upload my misc partition, as this partition contains my IMEI.
Can I ask why you need that?
Click to expand...
Click to collapse
I had no idea the IMEI is also there. I asked for it because the baseband version is also stored there and it's kind of odd to know I'm flashing the modem from EU-10f and the displayed version is TW-10a. I'm still hoping to solve that issue.
Ah, OK. Tomorrow I'll check if the misc partition can be mounted, this would make editing it much easier.
dapaua said:
Ah, OK. Tomorrow I'll check if the misc partition can be mounted, this would make editing it much easier.
Click to expand...
Click to collapse
I think it is not possible to mount the misc partition.
“In any case, the misc partition isn't a "filesystem" partition as you are familiar with. It is actually just a simple data structure. In fact, only the system, cache, and userdata partitions are actually filesystem partitions, and the cache partition is only a filesystem partition part of the time -- during radio and spl updates, it also is used as a simple data structure with a header field and a payload field...”
http://forum.xda-developers.com/showpost.php?p=7254425&postcount=3
I was trying to find some additional info about this structure but without success so far.
On may F180K the misc partition has 16 777 216 Bytes. Some interesting offset:
0x8000 – 0x800E IMEI (15Bytes)
0x8800 – 0x8824 Baseband version (37Bytes)
0x9000 – 0x9024 Baseband version (37Bytes)
CyanogenMod display the last one data on the Settings->About phone->Baseband version
jumper8 said:
I think it is not possible to mount the misc partition.
“In any case, the misc partition isn't a "filesystem" partition as you are familiar with. It is actually just a simple data structure. In fact, only the system, cache, and userdata partitions are actually filesystem partitions, and the cache partition is only a filesystem partition part of the time -- during radio and spl updates, it also is used as a simple data structure with a header field and a payload field...”
http://forum.xda-developers.com/showpost.php?p=7254425&postcount=3
I was trying to find some additional info about this structure but without success so far.
On may F180K the misc partition has 16 777 216 Bytes. Some interesting offset:
0x8000 – 0x800E IMEI (15Bytes)
0x8800 – 0x8824 Baseband version (37Bytes)
0x9000 – 0x9024 Baseband version (37Bytes)
CyanogenMod display the last one data on the Settings->About phone->Baseband version
Click to expand...
Click to collapse
Thanks.
You are totally right, this partition is not a filesystem. And it is mostly empty, it's all zeros except for some bytes. Most of it are text strings, but there are some small binary parts.
I think the 0x8800 - 0x8824 part is the original firmware version.
I wouldn't touch that partition, seems too dangerous .
dapaua said:
I wouldn't touch that partition, seems too dangerous .
Click to expand...
Click to collapse
freegee touches it. I see it made a backup and the difference is that it changed some bytes to 0 (offsets 0x40-0x52), then wrote ANDROID-BOOT at offset 0x4000. the rest is the same. it seems there's nothing like a crc so basically I could write whatever I want in that version field. the bad part is that as an user you'll never know what modem version you have since its version is not stored on the modem partition. I wonder who came up with this system and what was he thinking.
thanks for the clarification. offtopic over .
sonty said:
I had no idea the IMEI is also there. I asked for it because the baseband version is also stored there and it's kind of odd to know I'm flashing the modem from EU-10f and the displayed version is TW-10a. I'm still hoping to solve that issue.
Click to expand...
Click to collapse
Some time ago I had the same issue. I solved it by modifying binary data on the misc partition. I was done this only on CM10.1 (F180K). I don’t know if it will work on other custom rom especially stock one.
Today I’ve done this one more time for preparation the following procedure. Maybe some one will use it on the future.
STEPS:
0. Backup the misc partition with your recovery. I was used CWM Advance Edition PhilZ Touch 5:
Backup and Restore-> Custom Backup and Restore->Custom Backup Job->Backup misc (*)
I’m not sure if all CWMs version support misc partition backup. TWRP not support it right now.
1. Dump the misc partition to /sdcard.
Code:
adb wait-for-device
adb root
adb shell "dd if=/dev/block/platform/msm_sdcc.1/by-name/misc of=/sdcard/misc_orig.img"
OUTPUT:
32768+0 records in
32768+0 records out
16777216 bytes transferred in 6.539 secs (2565715 bytes/sec)
2. Pull the image to your PC
Code:
adb pull /sdcard/misc_orig.img misc_orig.img
3. Edit downloaded image file by your favorite hex editor (e.g. Notepad++ with Hex-Editor plugin)
Find both baseband name strings (mine were on offset 0x8800 and 0x9000) and change them (CM10.1 use the last one to set gsm.version.baseband in file /system/bin/fetch-swv).
REMEMBER:
- Do not use regular text editor (like Notepad or vi) – they can add some extra characters to the file.
- If possible try to modify only bytes responsible for original baseband name. If the new name is shorter, simply put spaces char (0x20) to clear unwanted chars. If you need to put the longer name, be careful. I don’t know the max size for this string. There are dozens of zeros behind the baseband name on my image file. So, for testing I added extra 20 Bytes text. The new baseband name was shown without problem.
4. Push the modified image file to your phone
Code:
adb push misc_orig.img /sdcard/misc_mod.img
Check if size of the original and modified files are equal.
5. Write the modified image to the misc partition
Code:
adb shell "dd if=/sdcard/misc_mod.img of=/dev/block/platform/msm_sdcc.1/by-name/misc "
OUTPUT:
32768+0 records in
32768+0 records out
16777216 bytes transferred in 4.183 secs (4010809 bytes/sec)
6. Reboot your phone
DONE.
Hi all,
I just create a .zip to backup your modem / baseband / radio with your recovery (CWM / TWRP...)
ok as a newbie i cant figure out how to back up modem using adb... but after reading stuff what i did :
downloaded "Android Terminal Emulator" from playstore
open emulator in phone wrote as u mentioned :
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/modem.img
after some seconds this came out :
131072+0 records in
131072+0 records out
67108864 bytes transferred in 15.229 secs
then :
exit
exit
after that i checked sdcard but there was no img file...
then i open file manager from the phone and there it was my precious :laugh:
size = 64mb... is it normal?
anyway .. made a new folder "modem" copied the img file into modem folder (using file manger) again connected the phone to pc copied the modem folder on my desktop...
hope it will help new guys here like me :good:
after installing the European kitkat I lost my LGOG E977 modem, anyone have some backup there to help me?
how to fix this?
:crying::crying::crying::crying::crying::crying::crying::crying::crying:
pedro5148 said:
after installing the European kitkat I lost my LGOG E977 modem, anyone have some backup there to help me?
how to fix this?
:crying::crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
root using towelroot. unlock and install custom recovery using freegee and flash the modem in this post via recovery: http://forum.xda-developers.com/showpost.php?p=54016773&postcount=4
akahroba said:
root using towelroot. unlock and install custom recovery using freegee and flash the modem in this post via recovery: http://forum.xda-developers.com/showpost.php?p=54016773&postcount=4
Click to expand...
Click to collapse
I already did that, did not work out ...
any more solution?
pedro5148 said:
I already did that, did not work out ...
any more solution?
Click to expand...
Click to collapse
Get back to JB and wait for your midel update
Back to JB I recovered the IMEI, but I have no carrier signal.
So do the root with towelroot, unlock custom recovery with FreeGee, do I back up EFS, and when I restart the machine it loses the IMEI.
So I install the modem and E97710b.kdz for E97710b model recover EFS and nothing happens, still no sign of the operator ...
---------- Post added at 02:22 PM ---------- Previous post was at 02:22 PM ----------
akahroba said:
Get back to JB and wait for your midel update
Click to expand...
Click to collapse
even going back to JB, I continued without the modem

[Q] SIM not recognized - Help needed

Hi
My wife bought a Note 2 (N7100) in China, second hand. I thought it was stock, so I tried to update it manually (official update) with Odin. But of course it was rooted and with some chinese ROM (my guess since I saw chinese charachters).
That didn't work so I proceeded to install a custom rom. After trying over and over, my phone would not recognise the SIM no longer (it worked before I started out with this mess). I have basically tried installing multiple roms (4.1, 4.3, 4.4), Odin fails when trying offical roms, multiple modem zips etc. Dont know what to do.
Problem is that I can not get the PCode because there is no connection with the SIM. IMEI is on the back of the phone, but trying *272*#IMEI-code# doesn't give me nothing because i just get fail. Trying to download a official rom from china over baidu.com, but until now no luck. What would you do? Right now its a phablet with wifi, nothing else. Anyone have an idea how to fix this little mess I put myself into?
Flash custom recovery and TRY THIS method in ADB.
Confirm if they have the same efs address though, but I think it's the same.
cz4r3n said:
Flash custom recovery and TRY THIS method in ADB.
Confirm if they have the same efs address though, but I think it's the same.
Click to expand...
Click to collapse
Looks like my /efs/ partition is zero, nill nothing. What to do? Use it as a wifi phablet? I dont have linux, only mac, so I cant do these two steps, but I guess it does not matter since I can not open the efs.img file
linux# losetup /dev/loop0 efs.img
linux# fsck /dev/loop0
So the phone is impossible to fix now - right? /efs/ folder on phone is emtpy.
Found my IMEI number for this phone on Google Dashboard. Is it possible to restore the EFS image only using that?
mikasjoman said:
Found my IMEI number for this phone on Google Dashboard. Is it possible to restore the EFS image only using that?
Click to expand...
Click to collapse
Did you ever have a backup on your efs?If yes, then restore it.there are so many threads on how to restore your efs.
---------- Post added at 07:55 PM ---------- Previous post was at 07:44 PM ----------
mount efs in adb.
adb shell
su
mount
dd if=/dev/block/mmcblk0p3 of=/sdcard/mmcblk0p3.bin
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3
dd if=/sdcard/mmcblk0p3.bin of=/dev/block/mmcblk0p3
mmcblk0p3.bin
That is a no Or maybe. I made a copy to my harddrive with those instructions you linked to. Could I email the efs.img file to you and you check if its usable? Maybe it is just corrupt. I really don't know how to figure it out on this mac. If it was empty it should not be the 21 MB it is.
I did a "cat" on the efs.img file and it seems full of info.
Being the poor student I am, I wont be able to buy a new phone in some time

cant install rom after ruu

i had my phone unlocked s off and then something happened and it went s on still unlocked but erased everythin.i had to relock the bootloader with fast boot commands.i got thr phone to ruu but after its finished it says succesful now install rom.problem is i cannot get any rom to install with fastboot always get a error.so i have a phone that sits at the htc screen.any help woukd be greatly appreciated
gillim74 said:
i had my phone unlocked s off and then something happened and it went s on still unlocked but erased everythin.i had to relock the bootloader with fast boot commands.i got thr phone to ruu but after its finished it says succesful now install rom.problem is i cannot get any rom to install with fastboot always get a error.so i have a phone that sits at the htc screen.any help woukd be greatly appreciated
Click to expand...
Click to collapse
You won't be able to install a Rom again until you unlock the bootloader again. Depending on the software version is what will determine which method you will need to do.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
You won't be able to install a Rom again until you unlock the bootloader again. Depending on the software version is what will determine which method you will need to do.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
everything i do i get a bootloader err i cant even get my token id so i bassicaly have a paper weight
gillim74 said:
everything i do i get a bootloader err i cant even get my token id so i bassicaly have a paper weight
Click to expand...
Click to collapse
Try "fastboot erase cache" command. Did the ruu complete?
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
Try "fastboot erase cache" command. Did the ruu complete?
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
yeah the ruu completed but im pretty sure i have a corrupted data partition with no way of reapairing.came to this conclusing from help from another member
gillim74 said:
yeah the ruu completed but im pretty sure i have a corrupted data partition with no way of reapairing.came to this conclusing from help from another member
Click to expand...
Click to collapse
Are you able to go into stock recovery and do a factory reset? This should assist in fixing the days partition as it wipes /data
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
Are you able to go into stock recovery and do a factory reset? This should assist in fixing the days partition as it wipes /data
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
I ran him through this all earlier. I team viewered it.
Unfortunately, based on what he said happened and what it's doing now it's almost certainly got partition issues with internal. As its locked and s on I cannot do any adb commands to fix them. Resetting won't do anything as it doesn't repartition internal. It boots but cannot create /data files. Therefore it's softbricked until it gets Java carded.
dottat said:
I ran him through this all earlier. I team viewered it.
Unfortunately, based on what he said happened and what it's doing now it's almost certainly got partition issues with internal. As its locked and s on I cannot do any adb commands to fix them. Resetting won't do anything as it doesn't repartition internal. It boots but cannot create /data files. Therefore it's softbricked until it gets Java carded.
Click to expand...
Click to collapse
is java card the same as jtag
gillim74 said:
is java card the same as jtag
Click to expand...
Click to collapse
No, java card will s-off the phone while it is in bootloader. Jtag is a firmware editing tool to help fix borked phones.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
No, java card will s-off the phone while it is in bootloader. Jtag is a firmware editing tool to help fix borked phones.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
ok thank you
gillim74 said:
ok thank you
Click to expand...
Click to collapse
Jtag will most likely not fix your issue, but s-off and a correct ruu would.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
Jtag will most likely not fix your issue, but s-off and a correct ruu would.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
yeah its getting the s-off i have the problem with lol
Uzephi said:
Jtag will most likely not fix your issue, but s-off and a correct ruu would.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
Unfortunately my friend... No RUU will repartition hosed internal eMMC. A custom recovery on the other hand, would allow manual commands like e2fschk etc to be ran against the eMMC and thus restoring hosed partitions. It's a manual process that could be done with just a custom recovery installed. An ruu simply reflashes partitions by known names.... the names must exist in the partition table for the flashing to occur.
JTAG can fix the problem as JTAG can do block by block flashing. Essentially it's like manually programming the EMMC chip on a bench.
dottat said:
Unfortunately my friend... No RUU will repartition hosed internal eMMC. A custom recovery on the other hand, would allow manual commands like e2fschk etc to be ran against the eMMC and thus restoring hosed partitions. It's a manual process that could be done with just a custom recovery installed. An ruu simply reflashes partitions by known names.... the names must exist in the partition table for the flashing to occur.
JTAG can fix the problem as JTAG can do block by block flashing. Essentially it's like manually programming the EMMC chip on a bench.
Click to expand...
Click to collapse
Good to know. I know ruu has fixed "unable to mount" issues in the past. I guess this one is more severe than what I have helped fix before. Thanks for the clarification.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
Good to know. I know ruu has fixed "unable to mount" issues in the past. I guess this one is more severe than what I have helped fix before. Thanks for the clarification.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
I have had one or two of these that i was able to fix using adb commands via TWRP.
Here's the output of the last one I had on a VZW m8. Symptoms were phone would flash RUU fine. Would flash roms fine. Would even factory reset without *****ing... but when you tried to boot it couldn't create /data so it just sat on the white HTC screen. I ended up just running e2fsck on the ext4 partitions and then RUU'd once more. Then the phone booted. Obviously, these commands are not nice to any data that exists on the corrupted partitions but it does get the phone working again.
Three ext4's in a row..
mmcblk0p46: a8000000 00000200 "system"
mmcblk0p47: 40000000 00000200 "cache"
mmcblk0p48: 30000000 00000200 "userdata"
~ # ←[6ne2fsck -f -p -v /dev/block/mmcblk0p46
e2fsck -f -p -v /dev/block/mmcblk0p46
2899 inodes used (1.69%)
0 non-contiguous files (0.0%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 2808
632408 blocks used (91.90%)
0 bad blocks
0 large files
2718 regular files
92 directories
0 character device files
0 block device files
0 fifos
0 links
80 symbolic links (80 fast symbolic links)
0 sockets
--------
2890 files
~ # ←[6ne2fsck -f -p -v /dev/block/mmcblk0p48
e2fsck -f -p -v /dev/block/mmcblk0p48
8288 inodes used (0.51%)
588 non-contiguous files (7.1%)
6 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 7905/70
549232 blocks used (8.47%)
0 bad blocks
1 large file
6150 regular files
1817 directories
0 character device files
0 block device files
5 fifos
0 links
299 symbolic links (292 fast symbolic links)
8 sockets
--------
8279 files
And theres no trick or work around to get adb working on stock recovery right

How do I fix the partition table?

Today, I was trying to apply a theme to my ROM, and some how it messed up the partition table. The internal should be a little less than 64GB, its at 25GB right now. The recovery partition is corrupt as well, I can no longer load a recovery, I found an unstable version of TWRP which seems to work. How can I fix this issue? I have done my research and could not find anything.
mem101296 said:
Today, I was trying to apply a theme to my ROM, and some how it messed up the partition table. The internal should be a little less than 64GB, its at 25GB right now. The recovery partition is corrupt as well, I can no longer load a recovery, I found an unstable version of TWRP which seems to work. How can I fix this issue? I have done my research and could not find anything.
Click to expand...
Click to collapse
So you can you access TWRP ? If yes, can you plug your phone to your computer, and see it whith adb ? If you can see the phone, type
Code:
adb shell
, then
Code:
df
and post the output here.
So I managed to fix the phone. Here's what I did Incase someone gets the same issue
-I connected to the computer, via fastboot
-Make sure to have twrp 2.19 downloaded.
-fastboot boot (recovery IMG)
-Once booted in, wipe your phone completely, all partitions.
-Flash the OnePlus 3 stock ROM, I flashed community edition. This will fix the partition sizes.
-Boot the phone and go through the setup, then reset into recovery (OnePlus recovery) and do a factory reset. This will insure the partitions are correct.
After all this, I reflashed twrp and put freedom os on if. Works perfectly.
mem101296 said:
So I managed to fix the phone. Here's what I did Incase someone gets the same issue
-I connected to the computer, via fastboot
-Make sure to have twrp 2.19 downloaded.
-fastboot boot (recovery IMG)
-Once booted in, wipe your phone completely, all partitions.
-Flash the OnePlus 3 stock ROM, I flashed community edition. This will fix the partition sizes.
-Boot the phone and go through the setup, then reset into recovery (OnePlus recovery) and do a factory reset. This will insure the partitions are correct.
After all this, I reflashed twrp and put freedom os on if. Works perfectly.
Click to expand...
Click to collapse
Glad to see that your phone is repaired. Can you tell me what theme you have tried to install?
Lowxorx said:
Glad to see that your phone is repaired. Can you tell me what theme you have tried to install?
Click to expand...
Click to collapse
I tried to install black theme from the deity substratum theme.
mem101296 said:
I tried to install black theme from the deity substratum theme.
Click to expand...
Click to collapse
How is freedom OS ? Is it better than Resurrection Remix ?
aadityarulez said:
How is freedom OS ? Is it better than Resurrection Remix ?
Click to expand...
Click to collapse
It all depends on what you like best, I'm currently using the CE version of freedomos, which has a big UI change. Which is why I'm using freedom os. Resurrection remix is completely stock Android, besides their customize menu in the settings.
For my OnePlus One, I had Resurrection remix, have yet to try on one the 3, but I prefer freedom os, based of OSS 3.5.2 CE (I believe)
mem101296 said:
I tried to install black theme from the deity substratum theme.
Click to expand...
Click to collapse
Okay thanks, will try to avoid to use this theme ^^
Lowxorx said:
So you can you access TWRP ? If yes, can you plug your phone to your computer, and see it whith adb ? If you can see the phone, type
Code:
adb shell
, then
Code:
df
and post the output here.
Click to expand...
Click to collapse
I am having the same issue and I am unable to write to the device. Ive tried and researched all I could. I literally just got the phone a week ago and its a paperweight.
Here are my results.
adb shell
~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 2921544 20 2921524 0% /dev
tmpfs 2921544 32 2921512 0% /tmp
/dev/block/sda3 253920 148 248532 0% /cache
~ # 
Solo5010 said:
I am having the same issue and I am unable to write to the device. Ive tried and researched all I could. I literally just got the phone a week ago and its a paperweight.
Here are my results.
adb shell
~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 2921544 20 2921524 0% /dev
tmpfs 2921544 32 2921512 0% /tmp
/dev/block/sda3 253920 148 248532 0% /cache
~ # 
Click to expand...
Click to collapse
This has never failed to fix any OP3. problem i have come across.. whether simple or complete brick.. Gets the job done..
Thank the thread owner if useful
https://www.google.com/amp/s/forum....mega-unbrick-guide-hard-bricked-t3405700/amp/
dmilz said:
This has never failed to fix any OP3. problem i have come across.. whether simple or complete brick.. Gets the job done..
Thank the thread owner if useful
https://www.google.com/amp/s/forum....mega-unbrick-guide-hard-bricked-t3405700/amp/
Click to expand...
Click to collapse
Awesome! I will give it a try and report back. Thanks for the direction!
Solo5010 said:
Awesome! I will give it a try and report back. Thanks for the direction!
Click to expand...
Click to collapse
Suree

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

Categories

Resources