Develop Bugs

Poor performance writing on /data

Hi all
My Galaxy Nexus with CM10 a week ago has started to lag a little bit, and the situation was getting worse day by day...
wipe didn't solve anything
so I tried to run some benchmark in order to understand if it's an hardware problem
with androbench I noticed that the write values are ridiculous
what can I do before bring it back to the manufacter?

When did you buy your Galaxy Nexus?
Can you please post a screenshot of the following App: http://forum.xda-developers.com/showthread.php?t=1693704
Maybe you're affected by this bug:
http://code.google.com/p/android/issues/detail?id=39154

Mine has similar results with androbench and is 2 weeks old. I have not deleted any big files also. The gotbrick app says that my emmc chip is unknown.
Sent from my Galaxy Nexus using xda premium

mariosraptor said:
The gotbrick app says that my emmc chip is unknown.
Click to expand...
Click to collapse
Is it a chip of type V3U00M?
You may try to remount /data and /cache (probably also /system) with the discard option and use dd/rm or Forever Gone to erase the empty blocks as suggested beginning at comment #25.
http://code.google.com/p/android/issues/detail?id=39154#c25

ph4zrd said:
Is it a chip of type V3U00M?
You may try to remount /data and /cache (probably also /system) with the discard option and use dd/rm or Forever Gone to erase the empty blocks as suggested beginning at comment #25.
http://code.google.com/p/android/issues/detail?id=39154#c25
Click to expand...
Click to collapse
Yes, is V3U00M. I read the comments there. I will try forever gone. Thank you
Sent from my Galaxy Nexus using xda premium

ph4zrd said:
Is it a chip of type V3U00M?
You may try to remount /data and /cache (probably also /system) with the discard option and use dd/rm or Forever Gone to erase the empty blocks as suggested beginning at comment #25.
http://code.google.com/p/android/issues/detail?id=39154#c25
Click to expand...
Click to collapse
yes, V3U00M!
I'll try the solution with adb (remount, dd and rm) later.
Thank you!

I just finished the forever gone solution. Tbh it is now worst than before.
Androbench took ages to finish and half the results.
So, to summirize. We should not try any solutions like this or via adb or any other that will make the device perform more slowly.
We bought a phone and expect it to work. Google should step up and fix every possible bug out there and ofcourse not introduce new ones.
Sent from my Galaxy Nexus using xda premium

mariosraptor said:
I just finished the forever gone solution. Tbh it is now worst than before.
Click to expand...
Click to collapse
Did you remount /data with -o discard before using Forever Gone?

ph4zrd said:
Did you remount /data with -o discard before using Forever Gone?
Click to expand...
Click to collapse
Nope. The app did not suggest that.
I will reflash the stock omage again.
Sent from my Galaxy Nexus using xda premium

mariosraptor said:
Nope. The app did not suggest that
Click to expand...
Click to collapse
The app isn't made for fixing this problem. It is made for overwriting free space on the sdcard.
So of course this doesn't fix it. The mount option does and is absolutely essential.
By simply using Forever Gone you only tried how bad this can get
mariosraptor said:
I will reflash the stock omage again.
Click to expand...
Click to collapse
This might temporarily help (a wipe of the system, cache and userdata partitions does), at least a little bit.
But it doesn't fix the problem. The phone will slow down again.
Step-by-step guide
1.
Make sure you have a eMMC chip of type V3U00M using this or this app as I mentioned above.
Otherwise it might be possible that the following commands HARD BRICK your phone.
You can also use the following command: cat /sys/class/block/mmcblk0/device/name
2.
Make sure your phone is rooted.
3.
Install and run this app.
This temporarily solves the problem, the phone will eventually begin to slow down again.
Type the following commands in a Terminal or preferably an adb shell:
Code:
[strike]su
mount -o remount,discard /data
dd if=/dev/zero of=/data/tmp.bin
rm /data/tmp.bin[/strike]
It WILL take a long time (up to 3 hours maybe) and your phone might soft-reboot like mine did. Therefore using adb would be better... Some users also reported a speedup when this is done in recovery mode (CWM/TWRP) via adb.
The dd command seems to fail, issuing a message similar to "no space left on device". This is normal as we don't give the command a particular file size so it fills the partition until no space is left on it. (That's what we want to do)
This temporarily solves the problem. After you reboot the remount option is lost and the phone will begin to slow down again.
Btw, you can also use the Forever Gone app instead of the dd/rm commands. So if you don't want to use the command line, apply Step 4 first (using Script Manager), reboot and then run Forever Gone.
4.
To prevent this, add the following code to a script and put it in the init.d folder (if your rom supports it) or use an app like Script Manager to run it on every boot. (Make sure it is started with root privileges!)
Code:
#!/system/bin/sh
mount -o remount,discard /data
mount -o remount,discard /cache
5.
Profit.
The only phones affected seem to be Galaxy Nexus GSM (i9250) models with the the V3U00M chip for which it is apparently essential to get TRIM/erase/discard commands or whatever for every single block deleted.
The only reported production dates of bad chips are 08/2012, 09/2012 and 10/2012 until now. Maybe chips produced earlier and/or later are also affected.
You can get the production date of you eMMC chip using the following command: cat /sys/class/block/mmcblk0/device/date
Additional information
Google Code Bugreport (already posted above)
Galaxy Nexus Storage Performance Over Time & TRIM
[Q] Why is my Nexus so sluggish?
My Galaxy Nexus is being very laggy...
[Q] Very slow and laggy Nexus
Other guide, some FAQ + patched kernel (for a specific ROM)
LagFix Tool
some eMMC chip types used at the beginning of 2012 (not affected, type VYL00M for GSM Nexus)
Benchmark of this chip on low-mem conditions
Maybe someone can make a flashable zip or something like that for automating this.
If enough people report this problem I might also do it.
I am not responsible for killing little kittens or your girlfriend getting pregnant by that.
Cheers!

5.
Profit.
The only phones affected seem to be Galaxy Nexus GSM (i9250) models produced after September 2012.
For the V3U00M chip it seems to be essential to get TRIM/erase/discard commands or whatever for every single block deleted.
according though to this my phone is not affected. it has been produced 2012-07(july). should i still proceed?

So I guess my sem32g on my toro should be OK. I get random lag and was wondering if that was it. Over 14 GB used but still about 12 GB free.
Sent from my Galaxy Nexus using Tapatalk 2

mariosraptor said:
according though to this my phone is not affected. it has been produced 2012-07(july). should i still proceed?
Click to expand...
Click to collapse
Seems like the date I posted is incorrect, sorry. Since your chip is not affected by the hard brick bug it should be safe to proceed.

ph4zrd said:
Seems like the date I posted is incorrect, sorry. Since your chip is not affected by the hard brick bug it should be safe to proceed.
Click to expand...
Click to collapse
it's ok.
i found my production date from here http://forum.xda-developers.com/showthread.php?t=1519606
i9250 made by samsung. bought it 2 saturdays ago

tiny4579 said:
So I guess my sem32g on my toro should be OK. I get random lag and was wondering if that was it. Over 14 GB used but still about 12 GB free.
Click to expand...
Click to collapse
Nearly all users which reported this problem until now had maguro phones with V3U00M chips, which does not necessarily mean that toro models didn't get problematic eMMC firmware.
You may try the discard mount option anyway.
---------- Post added at 09:31 PM ---------- Previous post was at 09:26 PM ----------
mariosraptor said:
it's ok.
i found my production date from here http://forum.xda-developers.com/showthread.php?t=1519606
i9250 made by samsung. bought it 2 saturdays ago
Click to expand...
Click to collapse
The production date of your eMMC chip may be of interest.
Can you post the output of the following command:
cat /sys/class/block/mmcblk0/device/date
Click to expand...
Click to collapse

ph4zrd said:
Nearly all users which reported this problem until now had maguro phones with V3U00M chips, which does not necessarily mean that toro models didn't get problematic eMMC firmware.
You may try the discard mount option anyway..
Click to expand...
Click to collapse
I'm somewhat scared to brick the device but the emmc check app says that I font have the brick bug. I also have the 11/2011 date.
Sent from my Galaxy Nexus using Tapatalk 2

tiny4579 said:
I'm somewhat scared to brick the device but the emmc check app says that I font have the brick bug. I also have the 11/2011 date.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=35027577&postcount=41
Probably it's better if you check for other solutions at first, like looking for CPU-consuming processes or doing a complete wipe (including fastboot erase userdata or similar)...

Ok the problem seems partially solved, thank you very much!
The benchmark result is not great, but the phone it's finally usable.
Look at the attachment, Random write is still bad (I think)
But I repeat the phone it's going well.
My chip date ->
Code:
[email protected]:/ # cat /sys/class/block/mmcblk0/device/date
08/2012

my production is as the friends above from the output of the command 08/2012
edit: the script does not seem to work.
when in smanager i select su, boot and then run i get this:
tem/bin/sh '/01discard'
unknown option --0mount: invalid option -0
unknown option --0mount: invalid option -0

monossidoz said:
Look at the attachment, Random write is still bad (I think)
Click to expand...
Click to collapse
According to this thread
http://forum.xda-developers.com/showthread.php?t=1971852
your random write performance is normal. I'm getting similar results.
Great sequential write performance btw!

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

Stuck in Safe Mode / Decrypt storage

Hi, a little background first. My phone is s-Off, bootloader is unlocked and I have a been running rooted custom roms since day 1 that I had this phone. I always ran good except that 2 months ago it started rebooting for no reason. I change my rom from InsertCoin to LeeDroid thinking that my help but no change. Now, yesterday was phone rebooted in the middle of playing a YouTube video right into safe mode asking for a password to Decrypt storage which I never encrypted.
I found a few threads about it. Here's what I tried:
- wipe user data: tried that with fastboot erase userdata and also fastboot format userdata, both failed.
- I went into TWRP to wipe data, said it ran successfully but it didn't since all my pictures and other personal files.
- I tried restoring a known working backup I had and it failed too
- fastboot oem lock fails
- fastboot rebootruu reboots in a blackscreen (no HTC logo in the background) then completely reboots back in safemode.
Any idea what I should try next?
Thanks a lot

anyone? I really desperate right now :crying:

stoned99 said:
- I went into TWRP to wipe data, said it ran successfully but it didn't since all my pictures and other personal files.
Click to expand...
Click to collapse
This is working correctly. You need to go into the advanced wipe options, and select Internal Storage to wipe that partition.
Try the "Format Data" option, and see if that helps.
stoned99 said:
- fastboot oem lock fails
Click to expand...
Click to collapse
I don't ever recommend doing this on an s-off device (for troubleshooting purposes). It doesn't enable anything that isn't already enabled under s-off (running RUUs is the most common reason); but can leave you stuck unable to do a heck of a lot of things (installing custom recovery, ROMs, etc.).
Does your version have an RUU that you can try?

redpoint73 said:
This is working correctly. You need to go into the advanced wipe options, and select Internal Storage to wipe that partition.
Try the "Format Data" option, and see if that helps.
I don't ever recommend doing this on an s-off device (for troubleshooting purposes). It doesn't enable anything that isn't already enabled under s-off (running RUUs is the most common reason); but can leave you stuck unable to do a heck of a lot of things (installing custom recovery, ROMs, etc.).
Does your version have an RUU that you can try?
Click to expand...
Click to collapse
thanks a lot for the reply. I tried the format option. Typed yes in the field. It said Updating Partitions details.... done. But when I go in the file manager I can see I didn't lose anything. Also if I mount my sdcard (data/media) and delete all the files from my PCs. all the files are being deleted. I rebooted the phone and they are all back.
Yes I have a RUU. I ran both using the exe which failed saying it could be an issue with the usb cable or something. Tried with the zip file renamed to img file (can't remember the exam name), hboot detected it then asked me if I wanted to update, I select yes by using volume 1, then I saw Update, 1 or 2 second later the phone rebooted in a black screen (not RUU), then rebooted in safe mode again asking to Decrypt Storage.
I tried the info found here http://android-revolution-hd.blogspot.ca/2014/09/how-to-fix-random-reboots-on-htc-one-m8.html but it didn't fix my data partition. Here's the output.
~ # ←[6n/tmp/fsck.ext4 -fn /dev/block/mmcblk0p47
/tmp/fsck.ext4 -fn /dev/block/mmcblk0p47
e2fsck 1.42.9 (28-Dec-2013)
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix? no
Inode 360574 was part of the orphaned inode list. IGNORED.
Deleted inode 368721 has zero dtime. Fix? no
Inode 426053 was part of the orphaned inode list. IGNORED.
Inode 426055 was part of the orphaned inode list. IGNORED.
Inode 696341 was part of the orphaned inode list. IGNORED.
Inode 712757 was part of the orphaned inode list. IGNORED.
Inode 745473 was part of the orphaned inode list. IGNORED.
Inode 1236999 was part of the orphaned inode list. IGNORED.
Inode 1237006 was part of the orphaned inode list. IGNORED.
Inode 1237021 was part of the orphaned inode list. IGNORED.
Inode 1237022 was part of the orphaned inode list. IGNORED.
Inode 1237036 was part of the orphaned inode list. IGNORED.
Inode 1237043 was part of the orphaned inode list. IGNORED.
Inode 1237046 was part of the orphaned inode list. IGNORED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(1159609--1159624) -(1170414--1170429) -1562594 -(15
65703--1565709) -1704549 -(2531003--2531013) -2743942 -(3047984--3047992) -34477
28 -(4796517--4796523) -6504126 -6504155 -6504168 -6504725
Fix? no
Free blocks count wrong (2592986, counted=2598704).
Fix? no
Inode bitmap differences: -360574 -368721 -426053 -426055 -696341 -712757 -7454
73 -1236999 -1237006 -(1237021--1237022) -1237036 -1237043 -1237046
Fix? no
Directories count wrong for group #52 (27, counted=26).
Fix? no
Free inodes count wrong (1653079, counted=1650912).
Fix? no
/dev/block/mmcblk0p47: ********** WARNING: Filesystem still has errors *********
*
/dev/block/mmcblk0p47: 9897/1662976 files (29.1% non-contiguous), 4058918/665190
4 blocks
Click to expand...
Click to collapse

stoned99 said:
thanks a lot for the reply. I tried the format option. Typed yes in the field. It said Updating Partitions details.... done. But when I go in the file manager I can see I didn't lose anything. Also if I mount my sdcard (data/media) and delete all the files from my PCs. all the files are being deleted. I rebooted the phone and they are all back.
Yes I have a RUU. I ran both using the exe which failed saying it could be an issue with the usb cable or something. Tried with the zip file renamed to img file (can't remember the exam name), hboot detected it then asked me if I wanted to update, I select yes by using volume 1, then I saw Update, 1 or 2 second later the phone rebooted in a black screen (not RUU), then rebooted in safe mode again asking to Decrypt Storage.
I tried the info found here http://android-revolution-hd.blogspot.ca/2014/09/how-to-fix-random-reboots-on-htc-one-m8.html but it didn't fix my data partition. Here's the output.
Click to expand...
Click to collapse
i would run a full ruu of the dev edition exe in fastboot usb mode and see if that fix the problem

toysoldierq said:
i would run a full ruu of the dev edition exe in fastboot usb mode and see if that fix the problem
Click to expand...
Click to collapse
Thanks. I already tried running the DEV RUU zip file by renaming it to that PXXXIMG.zip without a success. Since fastbootruu doesn't work I can tried it. Regarding the dev edition exe, I can't find it anywhere, only found the zip one. Do you know where I could find it?

stoned99 said:
Thanks. I already tried running the DEV RUU zip file by renaming it to that PXXXIMG.zip without a success. Since fastbootruu doesn't work I can tried it. Regarding the dev edition exe, I can't find it anywhere, only found the zip one. Do you know where I could find it?
Click to expand...
Click to collapse
Right here: http://www.htc.com/us/support/htc-one-m8/news/
But you need to change to the appropriate CID and MID. Plus, if your version's RUU exe didn't work, I don't see how this will be any different.
To be clear, you usually run the RUU in bootloader-fastboot mode, not RUU mode (it will boot to that itself once you run the RUU).
But if you have a fundamental USB connectivity issue, it really doesn't matter, and it still won't run. Try different cables, different USB ports, even another PC.

redpoint73 said:
Right here: http://www.htc.com/us/support/htc-one-m8/news/
But you need to change to the appropriate CID and MID. Plus, if your version's RUU exe didn't work, I don't see how this will be any different.
To be clear, you usually run the RUU in bootloader-fastboot mode, not RUU mode (it will boot to that itself once you run the RUU).
But if you have a fundamental USB connectivity issue, it really doesn't matter, and it still won't run. Try different cables, different USB ports, even another PC.
Click to expand...
Click to collapse
This is not a USB issue. The problem itself seems to be an ext4 corruption issue. When trying to restore my backups, it fails when trying to restore /data/media. I can't delete/format it either. I'll try the RUU exe but doubt it will work. Thanks for the help

stoned99 said:
This is not a USB issue.
Click to expand...
Click to collapse
You said in Post #4:
stoned99 said:
Yes I have a RUU. I ran both using the exe which failed saying it could be an issue with the usb cable or something.
Click to expand...
Click to collapse
I'm not saying the USB connectivity is causing the main Safe Mode/Decrypt Storage issue. But it does seem to be keeping the RUU from running, based on your previous post.
Also, I'm pretty sure I've seen this similar issue posted before (encrypted storage asking for password, when encryption wasn't selected by the user). From what I remember, the format storage option in TWRP (that you already tried) was the solution. But you might just search for those threads, to see if my recollection on the fix is incorrect; or if other fixes were found.

redpoint73 said:
You said in Post #4:
I'm not saying the USB connectivity is causing the main Safe Mode/Decrypt Storage issue. But it does seem to be keeping the RUU from running, based on your previous post.
Also, I'm pretty sure I've seen this similar issue posted before (encrypted storage asking for password, when encryption wasn't selected by the user). From what I remember, the format storage option in TWRP (that you already tried) was the solution. But you might just search for those threads, to see if my recollection on the fix is incorrect; or if other fixes were found.
Click to expand...
Click to collapse
Indeed, I looked at a few posts with that format storage issue and there was basically 2 solutions: 1) format data in TWRP. 2) Repair ext4 filesystem which didn't work either.
PS: Just saw that the link you gave me is for the Sense version, not the Google Edition. That's what I already tried and failed.

stoned99 said:
Indeed, I looked at a few posts with that format storage issue and there was basically 2 solutions: 1) format data in TWRP. 2) Repair ext4 filesystem which didn't work either.
PS: Just saw that the link you gave me is for the Sense version, not the Google Edition. That's what I already tried and failed.
Click to expand...
Click to collapse
You asked for Developer's Edition. Dev Edition and Google Play Edition (GPE) are 2 completely different things. Dev Edition is always Sense.
I've never seen an RUU.exe for GPE.

redpoint73 said:
You asked for Developer's Edition. Dev Edition and Google Play Edition (GPE) are 2 completely different things. Dev Edition is always Sense.
I've never seen an RUU.exe for GPE.
Click to expand...
Click to collapse
Oops my bad then. Sorry, probably my bad cold/sinusitis. I'm having a hard time concentrating.
Ok, so I tried that exe already and it didn't work. Any other ideas?

stoned99 said:
Oops my bad then. Sorry, probably my bad cold/sinusitis. I'm having a hard time concentrating.
Ok, so I tried that exe already and it didn't work. Any other ideas?
Click to expand...
Click to collapse
do you have teamviewer if so get it and let me help you, message private with the login and password.

stoned99 said:
Oops my bad then. Sorry, probably my bad cold/sinusitis. I'm having a hard time concentrating.
Click to expand...
Click to collapse
Heh, no worries. The last couple weeks have been rough for me (as far as illnesses), as well. And Dev Ed vs. GPE is a fairly common mistake.
Hopefully toysoldierq can help you out. You've tried everything I can think of.

redpoint73 said:
Heh, no worries. The last couple weeks have been rough for me (as far as illnesses), as well. And Dev Ed vs. GPE is a fairly common mistake.
Hopefully toysoldierq can help you out. You've tried everything I can think of.
Click to expand...
Click to collapse
I think he did not do the whole process going back to sense using this 1.54.401.5-W_Splash

toysoldierq said:
I think he did not do the whole process going back to sense using this 1.54.401.5-W_Splash
Click to expand...
Click to collapse
Sorry I'm back now. So what do you think I didn't try? Using the sense exe ruu? I tried it but it failed.
BTW regarding team viewer I'm not sure if that will really help since you won't be able to see my phone. I know how to use adb, fastboot, etc so if you have an idea of what I should try I would sure try it. Thanks a lot

stoned99 said:
Sorry I'm back now. So what do you think I didn't try? Using the sense exe ruu? I tried it but it failed.
BTW regarding team viewer I'm not sure if that will really help since you won't be able to see my phone. I know how to use adb, fastboot, etc so if you have an idea of what I should try I would sure try it. Thanks a lot
Click to expand...
Click to collapse
i have fix m8 phones over teamviewer already son im way ahead of you, if you want me fix the issue let me know or i can tell u what u need to do choice is yours.
step 1 well i reflash the gpe rooted rom
step 2 i change his mid to dev edtion one
step 3 change his cid to super cid
step 4 i flash 1.54.401.5-W_Splash and let him wipe data and cache in stock recovery
step 5 change his cid to dev
step 6 ran dev ruu the lateset

Ok we can try it over team viewer, give me a few minutes to install it and give you access

stoned99 said:
Ok we can try it over team viewer, give me a few minutes to install it and give you access
Click to expand...
Click to collapse
i gave you the instructions u can try that.

toysoldierq said:
i have fix m8 phones over teamviewer already son im way ahead of you, if you want me fix the issue let me know or i can tell u what u need to do choice is yours.
step 1 well i reflash the gpe rooted rom
step 2 i change his mid to dev edtion one
step 3 change his cid to super cid
step 4 i flash 1.54.401.5-W_Splash and let him wipe data and cache in stock recovery
step 5 change his cid to dev
step 6 ran dev ruu the lateset
Click to expand...
Click to collapse
Thanks much appreciated.
Would you reboot the phone between each steps? Maybe not because 2 and 3

How do I verify my system image backup?

I'm planning to root my G4 (LGH815 Germany) running v10b-EUR-xx. Before I'm attempting to root I took a backup using the following command:
dd if=/dev/block/mmcblk0 bs=8192 skip=55296 count=529920 of=/data/media/0/system.img
Is there any way of verifying the backup img before I proceed to root so I can be sure the backup is working in case something goes wrong during rooting?
There seems to be a difference between the size of my backup and the rooted image:
My backup: 4,341,104,640
Rooted img: 4,749,520,896
Why is there such a big difference?

b3n_ said:
I'm planning to root my G4 (LGH815 Germany) running v10b-EUR-xx. Before I'm attempting to root I took a backup using the following command:
dd if=/dev/block/mmcblk0 bs=8192 skip=55296 count=529920 of=/data/media/0/system.img
Is there any way of verifying the backup img before I proceed to root so I can be sure the backup is working in case something goes wrong during rooting?
There seems to be a difference between the size of my backup and the rooted image:
My backup: 4,341,104,640
Rooted img: 4,749,520,896
Why is there such a big difference?
Click to expand...
Click to collapse
The skip argument to dd tells it to skip reading 55296 blocks. Each block is 8192 bytes which means 55296*8192 bytes are being skipped, that brings it to total of 452,984,832 bytes, which is exactly the difference you have.
As for the reliability of your backup I suggest at least mounting it to see if structure is valid and files are there.
Sent from my LG-H815 using Tapatalk

Definately try mounting it. Search for "mount android image in windows" if you are using windows, or just mount it in Linux.

kuku2004 said:
The skip argument to dd tells it to skip reading 55296 blocks. Each block is 8192 bytes which means 55296*8192 bytes are being skipped, that brings it to total of 452,984,832 bytes, which is exactly the difference you have.
As for the reliability of your backup I suggest at least mounting it to see if structure is valid and files are there.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
In this case should I re-create my backup but put a skip count of 0 in to get a full image of the current system partition? Sounds like it would make more sense to have a full image rather than just a partial?

b3n_ said:
In this case should I re-create my backup but put a skip count of 0 in to get a full image of the current system partition? Sounds like it would make more sense to have a full image rather than just a partial?
Click to expand...
Click to collapse
Really don't know but I guess there's a reason for that skip, maybe the start is something fixed (zeroed?) so it would be a waste of space reading it.
Sent from my LG-H815 using Tapatalk

kuku2004 said:
Really don't know but I guess there's a reason for that skip, maybe the start is something fixed (zeroed?) so it would be a waste of space reading it.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Why would it be included in their image then? Maybe @autoprime could comment on this?

Sorry for the OT question, but how do I create a system.img backup without root?

creaky said:
Sorry for the OT question, but how do I create a system.img backup without root?
Click to expand...
Click to collapse
Look at the rooting thread you need to use the send_command tool and the basically revert the dd command.

b3n_ said:
Look at the rooting thread you need to use the send_command tool and the basically revert the dd command.
Click to expand...
Click to collapse
Thanks. I'll start sifting through.

So I was able to mount my image in Ubuntu and I can see all the folders/files in there. In case I have to restore, do I have to use seek=0 and I used the recommended skip when I created the image?

H811 (Tmobile G4) stuck in bootloop, can only enter download mode

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