Related
I try to use the new version of Heimdall but when starting to flash I had the following error:
Code:
Heimdall v1.3.0, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -3
Is there anybody that could explain the problem ?
However my SGS-2 is detect in the utilities tab.
Thanks for your answers.
Django313 said:
I try to use the new version of Heimdall but when starting to flash I had the following error:
Code:
Heimdall v1.3.0, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -3
Is there anybody that could explain the problem ?
However my SGS-2 is detect in the utilities tab.
Thanks for your answers.
Click to expand...
Click to collapse
Heimdall is flashing software? Why not use Odin?
As far as I understand Heimdall is for use on Galaxy S, not S2.
theo80 said:
Heimdall is flashing software? Why not use Odin?
As far as I understand Heimdall is for use on Galaxy S, not S2.
Click to expand...
Click to collapse
Because Heimdall is stable, reliable, open-source, cross-platform, allows for a large degree of flashing freedom and is guaranteed to be legal. None of these are true for Odin. Although not necessarily overly important Heimdall also flashes substantially faster.
Also as of 1.3.0 Heimdall Frontend now supports Heimdall Firmware Packages, which are by far a superior than attempting to flash several description-less tar archives with Odin.
EDIT: Heimdall works with all Galaxy S devices, except the Droid Charge, which we've had difficulties with. Which is another advantage over Odin; one version of Heimdall works with all devices so there's less confusion about versions.
Django313 said:
I try to use the new version of Heimdall but when starting to flash I had the following error:
Code:
Heimdall v1.3.0, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -3
Is there anybody that could explain the problem ?
However my SGS-2 is detect in the utilities tab.
Thanks for your answers.
Click to expand...
Click to collapse
What OS are you running? If it's Windows make sure you follow the README and install the drivers.
@Benjamin Dobell
Yes, I use heimdall 1.3.0 on Kubuntu 11.04.
I read your e-mail and I try to launch Heimdall with sudo and it works !
but it's finished bad, resulting in a "half-bricked" SGS-2.
the flash of the datafs partition, when reaching 100% freeze and heimdall sent the error that it couldn't load datafs. ending the session...
I try twice flashing my phone:
- one with my own built heimdall-firmware-packages
- the other was custom flashing.
both failed.
The third flashing I made with odin in a virtualbox, and succeeded.
here is the results when launching Heimdall in a terminal :
Code:
[email protected]:~$ sudo heimdall-frontend
[sudo] password for didier:
Error: "/var/tmp/kdecache-didier" is owned by uid 1000 instead of uid 0.
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun fichier ou dossier de ce type
QFileSystemWatcher: failed to add paths: /home/didier/.config/ibus/bus
KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work
Error: "/tmp/kde-didier" is owned by uid 1000 instead of uid 0.
Error: "/tmp/ksocket-didier" is owned by uid 1000 instead of uid 0.
kdeinit4: Shutting down running client.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Error: "/tmp/ksocket-didier" is owned by uid 1000 instead of uid 0.
Error: "/tmp/kde-didier" is owned by uid 1000 instead of uid 0.
Error: "/var/tmp/kdecache-didier" is owned by uid 1000 instead of uid 0.
kbuildsycoca4 running...
Error: "/var/tmp/kdecache-didier" is owned by uid 1000 instead of uid 0.
Error: "/var/tmp/kdecache-didier" is owned by uid 1000 instead of uid 0.
Error: "/var/tmp/kdecache-didier" is owned by uid 1000 instead of uid 0.
Error: "/tmp/ksocket-didier" is owned by uid 1000 instead of uid 0.
Error: "/var/tmp/kdecache-didier" is owned by uid 1000 instead of uid 0.
[email protected]:~$
Django313 said:
@Benjamin Dobell
Yes, I use heimdall 1.3.0 on Kubuntu 11.04.
I read your e-mail and I try to launch Heimdall with sudo and it works !
but it's finished bad, resulting in a "half-bricked" SGS-2.
the flash of the datafs partition, when reaching 100% freeze and heimdall sent the error that it couldn't load datafs. ending the session...
I try twice flashing my phone:
- one with my own built heimdall-firmware-packages
- the other was custom flashing.
both failed.
Click to expand...
Click to collapse
In regards to sudo permissions being required, I just did a bit of searching and I found some information (although it may have been old) that Kubuntu's udev rules are in a different location to Ubuntu's. I also found separate information indicating that Kubuntu is using an outdated udev rules specification. Either of these two things would cause the -3 permissions error without running Heimdall as a super user.
Do you know exactly what the error was you received from Heimdall when flashing failed? The output from Heimdall Frontend only contains the permissions errors and aren't related to the flashing process. When you use Heimdall Frontend, Heimdall's output is displayed in "Status" section of the "Flash" tab so that it can easily be copy and paste.
By the way if your phone gets stuck in a "half-bricked" state again then it can usually be fixed by going to the "Utilities" tab and running the "Close PC Screen" action. This doesn't repair any corrupted files on device (if there are any). This literally just tells the phone that it should at least try boot up, instead of displaying the phone <--> PC screen.
Help please
trying to run heimdall 1.3.0 on Mac OS 10.5.8, I have qt/xcode installed, still doesn't seem to work. everytime i run frontend and try to detect my device (samsung captivate)or save my .pit file I get "FRONTEND ERROR Heimdall crash"
Any suggestions ?
ERROR: Failed to access device. libusb error: -12
Win7 x64
Installed drivers:
Heimdall v1.3.0, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Beginning session...
Handshaking with Loke...
Uploading PITERROR: Failed to send end session packet!
ERROR: Failed to send file part packet!
PIT upload failed!
Ending session...
Odin works, back to odin.
Problem with heimdall on mac 0s 10.5.8
Crappyvate said:
trying to run heimdall 1.3.0 on Mac OS 10.5.8, I have qt/xcode installed, still doesn't seem to work. everytime i run frontend and try to detect my device (samsung captivate)or save my .pit file I get "FRONTEND ERROR Heimdall crash"
Any suggestions ?
Click to expand...
Click to collapse
@benjamin
Problem solved after updating to osx 10.6
there seem to be issues between Heimdall 1.3 on Leopard 10.5 and certain binaries. Heimdall command line does not execute and just crashes.
I'm getting a similar error on Arch Linux running Heimdall v1.3.0 with my Fascinate:
Code:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: 4
I do have the proper udev rules in place:
Code:
$ lsusb | grep Samsung
Bus 002 Device 068: ID 04e8:6601 Samsung Electronics Co., Ltd Mobile Phone
I couldn't get Heimdall to even detect the device on my MacBook Pro running 10.6.8. I don't have access to a Windows machine to do further testing, and have had a lot of issues trying to update pretty much anything on my phone after I rooted and put a Superclean ROM on a few months ago. Here's my current setup: pastie.org/2358372
Today I tried to flash my SGS-II with heimdall 1.3.0 on Linux Kubuntu 11.04.
I used the latest firmware XXKH3 and it failed as it did with the firmware XXKG6 few weeks ago. Just after it downloaded the file "datafs" it freeze resulting in a half-bricked phone.
Certainly there is a bug in heimdall at this point because all the others files are correctly downloaded.
the question is : why ?
I'm on Mac OsX 10.6.8, and after tried to flash my firmware using the downloaded PIT from my device, Heimdall told me that there were an error with libusb while it was trying to upload the PIT.
My SGS got semi-bricked, and after putting it to download mode again and unchecking Repartition in Heimdall, everything was fine with the flashing.
So, the question is... is there a bug with repartitioning? is it possible to use my device's PIT to repartition?
Need new bootloader for EPIC? How do I tell?
All, I picked up an EPIC from someone and they put DK28 on it which is a bit of a dead end. All searches turned up needing Odin and I don't have a Windows box. I then found Heimdall and then this thread here:
http://forum.xda-developers.com/showthread.php?t=1353310
This all looks promising but then I've read where I need to update the bootloader if I'm using a Mac. My question is, with an EPIC of somewhat unknown past, how do I know if I have the right bootloader on it? DK28 is the leaked Froyo that never got OTA'd. I want to get this EPIC back onto the OTA track so it can get Gingerbread. I've found CWM flashable images but the modem seems to be the biggest struggle. Of course, if Heimdall works, the thread above looks like it will get me all that I want.
So if anyone can help and tell me how to figure out if I've got the right bootloader and won't get the black screen problem, that would be cool.
thanks peterb
Need some help please
My device got messed up and I know nothing about using Linux or fixing partitions with ADB, I have the partition tables I need to fix it but I have no clue and no one in our community knows how to change the "head" sectors from four to ONE. Please this is my partition list from heimdal
Entry Count: 14
Unknown 1: 15718400
Unknown 2: 1
Unknown 3: 0
Unknown 4: 0
Unknown 5: 7703
Unknown 6: 237
Unknown 7: 62704
Unknown 8: 18
--- Entry #0 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 1
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1
Unknown 2: 0
Unknown 3: 0
Partition Name: IBL+PBL
Filename: boot.bin
--- Entry #1 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 2
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1
Unknown 2: 0
Unknown 3: 0
Partition Name: PIT
Filename: YPG70_8G-0304.pit
--- Entry #2 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 3
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 5
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL
Filename: Sbl.bin
--- Entry #3 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 4
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 5
Unknown 2: 6226025
Unknown 3: 7143533
Partition Name: SBL2
Filename: Sbl.bin
--- Entry #4 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 5
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 20
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs
--- Entry #5 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 6
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 40
Unknown 2: 39021280
Unknown 3: 7143533
Partition Name: EFS
Filename: efs.rfs
--- Entry #6 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 7
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 30
Unknown 2: 36662408
Unknown 3: 0
Partition Name: KERNEL
Filename: zImage
--- Entry #7 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 8
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 30
Unknown 2: 6684793
Unknown 3: 3014771
Partition Name: RECOVERY
Filename: zImage
--- Entry #8 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 9
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1160
Unknown 2: 0
Unknown 3: 0
Partition Name: FACTORYFS
Filename: factoryfs.rfs
--- Entry #9 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 10
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 536
Unknown 2: 6684780
Unknown 3: 115
Partition Name: DBDATAFS
Filename: dbdata.rfs
--- Entry #10 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 11
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 256
Unknown 2: 115
Unknown 3: 115
Partition Name: CACHE
Filename: cache.rfs
--- Entry #11 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 12
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 7696
Unknown 2: 0
Unknown 3: 0
Partition Name: DATAFS
Filename: datafs.rfs
--- Entry #12 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 13
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 20516
Unknown 2: 0
Unknown 3: 0
Partition Name: USERFS
Filename: userfs_8G.rfs
--- Entry #13 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 0
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: GANG
Filename: inand_8G.bin
Ending session...
Rebooting device...
Heyo guys, idk if this can be seen as somehow relate to this topic, cuz its a diff problem with heimdall than originally mentioned in this thread, but my problem is that while trying to flash twrp, my sm-a750fn got half-bricked, and odin didnt want to flash the phones stock ROM, beeing stuck at establishing a connection, so i went and tried to flash it via heimdall-frontend, without sudo cuz else id have issues with the pit not beeing recognised, and everytime i try to flash smth, no matter what .img, be it recovery, boot, misc, etc, heimdall gets stuck at 93% and later gets a fail msg:
"Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Donate | Glass Echidna
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
0%
1%
2%
3%
4%
5%
[...]
80%
81%
82%
83%
84%
85%
86%
87%
88%
89%
90%
91%
92%
93%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: BOOT upload failed!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface..."
The phone also shows like bout 45% of progress:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've dealed with android nand boot for a week,but there is still a problem bothered me so much.the first time after android installed my phone can launch android system normally,but when I reboot,things become bad,it warming that there is noting in my nand .Can you tell me what happened to it with your knowledge and experience!thank you very much^^
nandmtd2_WriteChunkWithTagsToNAND chunk 7177 data c5663000 tags d4061da8
<4>[ 96.371551] packed tags obj 114 chunk 10 byte 2048 seq 33
<4>[ 96.379058] ext.tags eccres -1072003072 blkbad -737796660 chused 7173 obj 114 chunk10 byte 2048 del 0 ser 2048 seq 33
this is messeage, I face the same problem
Fully working nvflash(APX Mode) for Toshiba Folio 100
Working :
- bootloader (toshiba logo)
- fully working fastboot
issue :
- Blank MBR after flashing from fastboot
I'm working this based on [REQ] Toshiba folio 100 BCT and partition dumps Thread
And reference from Hacking the Toshiba AC100
I'm running this on Toshiba AS100 also known as Folio 100 wtih 8GB of internal storage
it should be working on 16GB version
files :
bootloader.bin --> Toshiba Folio 100 bootloader
busybox --> busybox v1.18.4
Fix-MBR.cmd --> Fix MBR after flashing from fastboot
folio100.xls --> my summary about partition table on folio 100 and ac100
new.bct --> downloaded form my folio 1000
NVFlash-Folio100.cmd --> all-in-one working nvflash and partition script
NVFlash.txt --> nvflash documentation
env.cmd --> start command prompt with adb,fastboot and nvflash support
flash.cfg --> i created this config file based on my summary
part.run --> parititon creation script
part.txt --> fdisk partition parameter
part-layout.txt --> Fdisk partition layout
Before you run NVFlash-Folio100.cmd you need to download CWM Recovery image from
Files needed :
1. cwm.img --> CWM Recovery
download from :
[RECOVERY][UPDATE] Unofficial port of ClockworkMod Recovery for folio100 - BETA
[recovery] CWM for Betelgeuse v0.3 - Now with USB support
note : extract the file until you got recovery.img,then rename it to cwm.img
2. boot.img --> Kernel image
3. system.img --> System partition image
4. recovery.img --> Recovery image
Download working ROM :
DISCONTINUED - [ROM][19-feb-2011] FolioMod v1.4 for Toshiba Folio100
Driver :
1. Toshiba Folio 100 ADB and Fastboot driver
This is standard Google USB Driver,i have modified some entries for working on Toshiba Folio 100
Download link
2. NVIDIA USB Boot-recovery driver also known as APX Driver
Download link
After you have all needed file double click NVFlash-Folio100.cmd
Connect your device using micro usb cable in APX mode
After finished flash from NVFlash your device will automatically boot to CWM Recovery
While CWM Recovery on standby menu,press any key to continue the script for partition and formating
After that just reboot your device.
If you just flashed your device using fastboot enter CWM Recovery and run Fix-MBR.cmd
Note :
APX mode --> On Toshiba boot screen press Power 4x then Vol- (if you have enter this mode,you need to full flash from NVFlash)
Fastboot mode --> On Toshiba boot screen press Power 3x then Vol-
Recovery mode --> On Toshiba boot screen press Power + Vol+
If you stuck on something just long press the power button,it will power off the device
if you're already flashed from NVFlash and unable to enter APX Mode,you need to disassembly your device.Disconnect cable from NAND and then power on the device.After it connected in APX mode,you can connect the NAND cable and flash it using NVFlash.
For disassembly reference Folio 100 Disassembly - Pictures
The NAND flash is connected using white short film cable.
Folio100-NVFlash-Final.zip download link
Thanks a lot! Great work!!!
what does it do?
Is it a Custom Rom or something else?
Crunon said:
what does it do?
Is it a Custom Rom or something else?
Click to expand...
Click to collapse
Fully working solution for bricked and corupted internal storage partition of Toshiba Folio 100.
Thanks so much.
I followed your guide and save my friend's table
need help please
nvramFolio stucks:
D:\temp\Folio100-NVFlash-Final>nvflash.exe --bct %bct% --setbct --bl %bl% --configfile %config% --odmdata 0x000c0075 --c
reate --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 2
chip sku: 0x8
chip uid: 0x17006181434001d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: new.bct
- 4080/4080 bytes sent
new.bct sent successfully
command failure: bootloader download failed
Click to expand...
Click to collapse
How long do I have to wait? I wait 15min.
then I tryed this:
D:\temp\Folio100-NVFlash-Final>nvflash.exe --bl %bl% --configfile %config% --odmdata 0x000c0075 --create --go
Nvflash started
uid read failed
Click to expand...
Click to collapse
I used driver from the link and in both cases I had done a hard reset.
THX for help!
Miraculix666 said:
nvramFolio stucks:
How long do I have to wait? I wait 15min.
then I tryed this:
I used driver from the link and in both cases I had done a hard reset.
THX for help!
Click to expand...
Click to collapse
If the process have failed,you need to turn off your device and then turn it back on before starting a new process.that why you got this :
Code:
Nvflash started
uid read failed
"UID read failed" is the message after power down.
I assume an error while flashing the bootloader. right?
The history for the error was:
-ICS_r4 cwm_0.3_Betelegeuse (all fine)
-update cwm5. & ICS_alpha (internal sd missing in ICS, internal sd acsessible in cwm)
-trying format and wipe from fastboot and cwm
-internal sd missing in cwm
-flashing back to cwm 0.3 & ICS_r4 (internal sd missing)
-flashing cwm5. & ICS_alpha (internal sd missing)
-found out partition table is corrupted (no info at fdisk)
-tryed to fix that way http://forum.xda-developers.com/showthread.php?t=1470823&page=18 boot.zip)
-tryed to fix that way http://bb2k.org/folio100wiki/index...._.28included_in_the_TV-Dock.29_doesn.27t_work
from adb and then I had this
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
~ # fdisk /dev/block/mmcblk0
fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 1944064.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: invalid flag 0x00,0x00 of partition table 5 will be corrected by w(rite)
Command (m for help): p
p
Disk /dev/block/mmcblk0: 15.9 GB, 15925772288 bytes
1 heads, 16 sectors/track, 1944064 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 129 32896 262144 83 Linux
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 32897 163968 1048576 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 163969 164224 2048 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 164225 1943360 14233088 5 Extended
Partition 4 does not end on cylinder boundary
Click to expand...
Click to collapse
-flashed update_createpart.zip (now only APX booting.)
I tryed:
D:\temp\Folio100-NVFlash-Final>nvflash.exe --bct new.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0
x000c0075 --create --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 2
chip sku: 0x8
chip uid: 0x17006181434001d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: new.bct
- 4080/4080 bytes sent
new.bct sent successfully
Click to expand...
Click to collapse
(stays at this point for a hour)
then I tryed:
nvflash.exe --configfile %config% --odmdata 0x000c0075 --create --format_all
Click to expand...
Click to collapse
and
nvflash.exe --bct %bct% --setbct --configfile %config% --odmdata 0x000c0075 --create
Click to expand...
Click to collapse
I made a reset after 15min in cause of no response.
should I disassemble? If yes, connecting nand with power on or
disconnect->on->off->connect->on->nvflash
Is it required that the power plug is connected?
If you intrested, i can guide you via gtalk.check my PM.
Here Full log of successful NVFlash-Folio100.cmd
folio dead
After programming with nflash I have a problem the folio will not start more ... Fix-MBR gives me this error log
connect your device in CWM Recovery
Premere un tasto per continuare . . .
28 KB/s (146 bytes in 0.005s)
The number of cylinders for this disk is set to 486016.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): Changing display/entry units to sectors
Command (m for help): First sector (2645008-31105023, default 2645008): First sector (2645008-31105023, default 2645008): Value is out of range
First sector (2645008-31105023, default 2645008): Value is out of range
First sector (2645008-31105023, default 2645008): Value is out of range
First sector (2645008-31105023, default 2645008): First sector (2645008-31105023, default 2645008): First sector (2645008-31105023, default 2645008): Value is out of range
First sector (2645008-31105023, default 2645008): Value is out of range
First sector (2645008-31105023, default 2645008): Value is out of range
First sector (2645008-31105023, default 2645008): First sector (2645008-31105023, default 2645008): First sector (2645008-31105023, default 2645008): Value is out of range
First sector (2645008-31105023, default 2645008): Value is out of range
First sector (2645008-31105023, default 2645008): Value is out of range
First sector (2645008-31105023, default 2645008): First sector (2645008-31105023, default 2645008): First sector (2645008-31105023, default 2645008): Value is out of range
First sector (2645008-31105023, default 2645008): Value is out of range
First sector (2645008-31105023, default 2645008): Using default value 2645008
Last sector or +size or +sizeM or +sizeK (2645008-2645999, default 2645999): Last sector or +size or +sizeM or +sizeK (2645008-2645999, default 2645999): Value is out of range
Last sector or +size or +sizeM or +sizeK (2645008-2645999, default 2645999): Value is out of range
Last sector or +size or +sizeM or +sizeK (2645008-2645999, default 2645999): Last sector or +size or +sizeM or +sizeK (2645008-2645999, default 2645999): Value is out of range
Last sector or +size or +sizeM or +sizeK (2645008-2645999, default 2645999): Value is out of range
Last sector or +size or +sizeM or +sizeK (2645008-2645999, default 2645999): Last sector or +size or +sizeM or +sizeK (2645008-2645999, default 2645999): Value is out of range
Last sector or +size or +sizeM or +sizeK (2645008-2645999, default 2645999): Value is out of range
Last sector or +size or +sizeM or +sizeK (2645008-2645999, default 2645999): Last sector or +size or +sizeM or +sizeK (2645008-2645999, default 2645999): Value is out of range
Last sector or +size or +sizeM or +sizeK (2645008-2645999, default 2645999): Using default value 2645999
Command (m for help):
Disk /dev/block/mmcblk0: 15.9 GB, 15925772288 bytes
4 heads, 16 sectors/track, 486016 cylinders, total 31105024 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 2048 526335 262144 83 Linux
/dev/block/mmcblk0p2 526336 2623487 1048576 83 Linux
/dev/block/mmcblk0p3 2623488 2627583 2048 83 Linux
/dev/block/mmcblk0p4 2627584 31105023 14238720 5 Extended
/dev/block/mmcblk0p5 2628608 2644991 8192 83 Linux
/dev/block/mmcblk0p6 2646016 4743167 1048576 83 Linux
/dev/block/mmcblk0p7 4744192 4754431 5120 83 Linux
/dev/block/mmcblk0p8 4754448 31105023 13175288 83 Linux
/dev/block/mmcblk0p9 2627600 2628607 504 83 Linux
/dev/block/mmcblk0p10 2645008 2645999 496 83 Linux
Partition table entries are not in disk order
Command (m for help): The partition table has been altered.
Calling ioctl() to re-read partition table
" "
" Please reboot your device "
" "
folio is dead??
retry with full flash from NVFlash-Folio100.cmd
puppet13th said:
retry with full flash from NVFlash-Folio100.cmd
Click to expand...
Click to collapse
After another flash, log this message:
extraneo said:
After another flash, log this message:
Click to expand...
Click to collapse
when you're getting this :
Code:
waiting device to bootup . . .
press any key if the device have entered CWM Recovery . . .
unmount /cache from recovery
then continue that nvflash script
puppet13th said:
when you're getting this :
Code:
waiting device to bootup . . .
press any key if the device have entered CWM Recovery . . .
unmount /cache from recovery
then continue that nvflash script
Click to expand...
Click to collapse
Thanks for help but no change. same message.
Great guide and great tools.
Just one question: after I've run the NVFlash-Folio100.cmd, you say to run fixmbr. This throws an error message
connect your device in CWM Recovery
Press any key to continue . . .
28 KB/s (146 bytes in 0.005s)
The number of cylinders for this disk is set to 485840.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): Changing display/entry units to sectors
Command (m for help): First sector (2627600-31093759, default 2627600): First se
ctor (2627600-31093759, default 2627600): Value is out of range
First sector (2627600-31093759, default 2627600): Value is out of range
First sector (2627600-31093759, default 2627600): Value is out of range
First sector (2627600-31093759, default 2627600): First sector (2627600-31093759
, default 2627600): First sector (2627600-31093759, default 2627600): Value is o
ut of range
First sector (2627600-31093759, default 2627600): Value is out of range
First sector (2627600-31093759, default 2627600): Value is out of range
First sector (2627600-31093759, default 2627600): First sector (2627600-31093759
, default 2627600): First sector (2627600-31093759, default 2627600): Value is o
ut of range
First sector (2627600-31093759, default 2627600): Value is out of range
First sector (2627600-31093759, default 2627600): Value is out of range
First sector (2627600-31093759, default 2627600): First sector (2627600-31093759
, default 2627600): First sector (2627600-31093759, default 2627600): Value is o
ut of range
First sector (2627600-31093759, default 2627600): Value is out of range
First sector (2627600-31093759, default 2627600): Using default value 2627600
Last sector or +size or +sizeM or +sizeK (2627600-2628607, default 2628607): Las
t sector or +size or +sizeM or +sizeK (2627600-2628607, default 2628607): Value
is out of range
Last sector or +size or +sizeM or +sizeK (2627600-2628607, default 2628607): Val
ue is out of range
Last sector or +size or +sizeM or +sizeK (2627600-2628607, default 2628607): Las
t sector or +size or +sizeM or +sizeK (2627600-2628607, default 2628607): Value
is out of range
Last sector or +size or +sizeM or +sizeK (2627600-2628607, default 2628607): Val
ue is out of range
Last sector or +size or +sizeM or +sizeK (2627600-2628607, default 2628607): Las
t sector or +size or +sizeM or +sizeK (2627600-2628607, default 2628607): Value
is out of range
Last sector or +size or +sizeM or +sizeK (2627600-2628607, default 2628607): Val
ue is out of range
Last sector or +size or +sizeM or +sizeK (2627600-2628607, default 2628607): Las
t sector or +size or +sizeM or +sizeK (2627600-2628607, default 2628607): Value
is out of range
Last sector or +size or +sizeM or +sizeK (2627600-2628607, default 2628607): Usi
ng default value 2628607
Command (m for help):
Disk /dev/block/mmcblk0: 15.9 GB, 15920005120 bytes
4 heads, 16 sectors/track, 485840 cylinders, total 31093760 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 2048 526335 262144 83 Linux
/dev/block/mmcblk0p2 526336 2623487 1048576 83 Linux
/dev/block/mmcblk0p3 2623488 2627583 2048 83 Linux
/dev/block/mmcblk0p4 2627584 31093759 14233088 5 Extended
/dev/block/mmcblk0p5 2628608 2644991 8192 83 Linux
/dev/block/mmcblk0p6 2646016 4743167 1048576 83 Linux
/dev/block/mmcblk0p7 4744192 4754431 5120 83 Linux
/dev/block/mmcblk0p8 4754448 31093759 13169656 83 Linux
/dev/block/mmcblk0p9 2627600 2628607 504 83 Linux
Partition table entries are not in disk order
Command (m for help): The partition table has been altered!
Calling ioctl() to re-read partition table
" "
" Please reboot your device "
" "
Press any key to continue . . .
Click to expand...
Click to collapse
I'm also getting "E: Can't mount /cache/recovery/command" and similar strings when CWM is running... At present, Folio100-NVFlash-Final is the only way I'm able to get the tablet working, and cannot install any other rom...
any advice on how/if this can be fixed?
yellowumbrella said:
Great guide and great tools.
Just one question: after I've run the NVFlash-Folio100.cmd, you say to run fixmbr. This throws an error message
I'm also getting "E: Can't mount /cache/recovery/command" and similar strings when CWM is running... At present, Folio100-NVFlash-Final is the only way I'm able to get the tablet working, and cannot install any other rom...
any advice on how/if this can be fixed?
Click to expand...
Click to collapse
I reported the same problem. NVflash contains a BUG??? ... perhaps it is better not to use it.
Well, it was/is my only option to get the tablet working at present. After my friend kicked it into apx mode, nvflash was the only solution (as far as I'm aware). And now if I try to flash other roms and fail, the only way to get the tablet working is to force apx and use nvflash...
Sent from my SGH-T849 using XDA
Hint : if you have entered CWM stage,the nvflash solution was working properly.
After that you need to create partition table for it
I have successfully done this for 8GB version.
Maybe the partition layout was diffrent between 8GB and 16GB.
I can try to help trought gtalk chat.
If you instrested , pm me.
Sent from my ST17i using Tapatalk
puppet13th said:
Maybe the partition layout was diffrent between 8GB and 16GB.
I can try to help trought gtalk chat.
If you instrested , pm me.
Click to expand...
Click to collapse
I have the same Problem with my 16gb Folio.
Recovery works, but thats all...
Can you poste the right way if it works with yellowumbrella?
I want to modify the Saihon X6 ROM, but the system.img is different from I've ever met, they put the system.img into 8 img, now do not know how to unpack/repack, I need help, need a detailed tutorial. Thank you
ht tp://pan.baidu.com/s/1pJAvLer
How can i unpack/repack like this system.img
ardager said:
I want to modify the Saihon X6 ROM, but the system.img is different from I've ever met, they put the system.img into 8 img, now do not know how to unpack/repack, I need help, need a detailed tutorial. Thank you
ht tp://pan.baidu.com/s/1pJAvLer
Click to expand...
Click to collapse
I used this on ubuntu
Run sudo mount-o loop system_1.img system
displays
Mount: wrong fs type, bad option, bad superblock on / dev/loop0,
Missing codepage or helper program, or Other Error
system log may have some important information,
try using dmesg | tail like a command.
Run dmesg | tail view LOG
display
[74.005499] audit_printk_skb: 18 callbacks suppressed
[74.005518] type = 1400 Audit (1360118240.727:23): AppArmor = "DENIED" operation = "capable" parent = 1 Profile = "/ usr / lib / Telepathy / mission-control-5 "pid = 1553 COMM =" mission-control "Capability = 23 capname =" sys_nice "
[74.415356] type = 1400 Audit (1360118241.135:24): AppArmor = "DENIED" operation = "Open" parent = 1 profile = "/ usr/lib/telepathy/mission-control-5" name = "/ usr / share / gvfs / remote-volume-monitors /" pid = 1553 comm = "mission-control" requested_mask = "r" denied_mask = "r" fsuid = 0 ouid = 0
[365.116251] EXT4-fs (loop0): bad geometry: Block count 97 656 Exceeds Size of device (32767 Blocks)
[579.113993] hrtimer: interrupt took 5,682,946 ns
[630.545278] EXT4-fs ( loop0): bad geometry: Block count ninety-seven thousand six hundred and fifty-six Exceeds Size of device (32767 Blocks)
[644.026965] EXT4-fs (loop0): Unrecognized Mount option "loop1" or Missing value
[670.312507] EXT4-fs (loop0): bad geometry: Block count ninety-seven thousand six hundred fifty-six Exceeds Size of device (32767 Blocks)
[788.599457] EXT4-fs (loop0): bad geometry: 76800 Block count Exceeds Size of device (1657 Blocks)
[1008.514549] EXT4-fs (loop0): bad geometry: Block count 97,656 exceeds size of device (32767 blocks)
file system_1.img
results
system_1.img: Linux rev 1.0 ext4 filesystem data, UUID = 57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
Phone: Galaxy S3 VZW 32GB
Recovery: TWRP 2.7.1.0
Mod: CM11 m8
Kernel, governer, etc all CM11 stock.
Problem:
Twice today the phone rebooted itself while performing large file copy operations. last_kmsg from both reboots basically look the same:
Code:
[40996.107363] Buffer I/O error on device mmcblk0p15, logical block 6751031
[40996.114291] Buffer I/O error on device mmcblk0p15, logical block 6751032
[40996.120761] Buffer I/O error on device mmcblk0p15, logical block 6751033
[40996.127476] Buffer I/O error on device mmcblk0p15, logical block 6751034
[40996.134160] Buffer I/O error on device mmcblk0p15, logical block 6751035
[40996.140813] Buffer I/O error on device mmcblk0p15, logical block 6751036
[40996.147528] Buffer I/O error on device mmcblk0p15, logical block 6751037
[40996.154181] Buffer I/O error on device mmcblk0p15, logical block 6751038
[40996.160926] Buffer I/O error on device mmcblk0p15, logical block 6751039
[41056.701656] ACDB=> get_hw_delay: Path = 0 samplerate = 48000 usec = 0 status 0
[41056.708065] afe_callback: cmd = 0x100dc returned error = 0x3
[41056.713681] afe_send_hw_delay: config cmd failed
[41065.991721] kgsl kgsl-3d0: |kgsl_late_resume_driver| late resume start
[41066.310781] cypress_touchkey 16-0020: not real interrupt (1).
[41117.725034] EXT4-fs error (device mmcblk0p15): ext4_mb_generate_buddy:741: group 113, 644 clusters in bitmap, 530 in gd
[41117.744476] Aborting journal on device mmcblk0p15-8.
[41117.764161] Kernel panic - not syncing: EXT4-fs (device mmcblk0p15): panic forced after error
[41117.764161]
[41117.773257] [<c0013ee8>] (unwind_backtrace+0x0/0xe0) from [<c0778f40>] (panic+0x88/0x1f8)
[41117.781344] [<c0778f40>] (panic+0x88/0x1f8) from [<c01a7134>] (ext4_handle_error+0x8c/0x98)
[41117.789738] [<c01a7134>] (ext4_handle_error+0x8c/0x98) from [<c01a7ca0>] (__ext4_grp_locked_error+0xe8/0x1c4)
[41117.799626] [<c01a7ca0>] (__ext4_grp_locked_error+0xe8/0x1c4) from [<c01b6618>] (ext4_mb_generate_buddy+0x25c/0x2e8)
[41117.810125] [<c01b6618>] (ext4_mb_generate_buddy+0x25c/0x2e8) from [<c01b8620>] (ext4_mb_init_cache+0x358/0x5f0)
[41117.820288] [<c01b8620>] (ext4_mb_init_cache+0x358/0x5f0) from [<c01b8db8>] (ext4_mb_load_buddy+0x278/0x2b4)
[41117.830085] [<c01b8db8>] (ext4_mb_load_buddy+0x278/0x2b4) from [<c01ba0fc>] (ext4_mb_find_by_goal+0x3c/0x23c)
[41117.840005] [<c01ba0fc>] (ext4_mb_find_by_goal+0x3c/0x23c) from [<c01ba9e0>] (ext4_mb_regular_allocator+0x4c/0x388)
[41117.850351] [<c01ba9e0>] (ext4_mb_regular_allocator+0x4c/0x388) from [<c01bc120>] (ext4_mb_new_blocks+0x1fc/0x5c0)
[41117.860728] [<c01bc120>] (ext4_mb_new_blocks+0x1fc/0x5c0) from [<c01b31d8>] (ext4_ext_map_blocks+0xfcc/0x15ac)
[41117.870739] [<c01b31d8>] (ext4_ext_map_blocks+0xfcc/0x15ac) from [<c018cf7c>] (ext4_map_blocks+0xf8/0x2e4)
[41117.880353] [<c018cf7c>] (ext4_map_blocks+0xf8/0x2e4) from [<c0190d4c>] (mpage_da_map_and_submit+0x114/0x57c)
[41117.890241] [<c0190d4c>] (mpage_da_map_and_submit+0x114/0x57c) from [<c0191908>] (ext4_da_writepages+0x340/0x5b8)
[41117.900496] [<c0191908>] (ext4_da_writepages+0x340/0x5b8) from [<c00ff3e0>] (do_writepages+0x24/0x38)
[41117.909713] [<c00ff3e0>] (do_writepages+0x24/0x38) from [<c00f6d14>] (__filemap_fdatawrite_range+0x60/0x6c)
[41117.919419] [<c00f6d14>] (__filemap_fdatawrite_range+0x60/0x6c) from [<c00f6de8>] (filemap_write_and_wait_range+0x34/0x68)
[41117.930436] [<c00f6de8>] (filemap_write_and_wait_range+0x34/0x68) from [<c0188ab0>] (ext4_sync_file+0xb4/0x414)
[41117.940447] [<c0188ab0>] (ext4_sync_file+0xb4/0x414) from [<c0158338>] (vfs_fsync_range+0x34/0x44)
[41117.949451] [<c0158338>] (vfs_fsync_range+0x34/0x44) from [<c0158368>] (vfs_fsync+0x20/0x28)
[41117.957874] [<c0158368>] (vfs_fsync+0x20/0x28) from [<c01586a0>] (sys_fdatasync+0x18/0x34)
[41117.966115] [<c01586a0>] (sys_fdatasync+0x18/0x34) from [<c000e000>] (ret_fast_syscall+0x0/0x30)
[41117.974874] CPU1: stopping
[41117.977529] [<c0013ee8>] (unwind_backtrace+0x0/0xe0) from [<c0012f6c>] (handle_IPI+0x100/0x1cc)
[41117.986258] [<c0012f6c>] (handle_IPI+0x100/0x1cc) from [<c0008670>] (gic_handle_irq+0xa8/0xb4)
[41117.994804] [<c0008670>] (gic_handle_irq+0xa8/0xb4) from [<c000ddbc>] (__irq_usr+0x3c/0x60)
[41118.003166] Exception stack(0xcb443fb0 to 0xcb443ff8)
[41118.008141] 3fa0: 75254dc0 752a4547 000001a4 00000564
[41118.016321] 3fc0: 00002000 00000010 00000612 75252000 bea932dc 75254f00 bea932ed 7522b6e8
[41118.024531] 3fe0: 40224e24 bea93268 40211be7 4021ab9c 80010030 ffffffff
[41118.131322] Rebooting in 5 seconds..
[41123.135045] Going down for restart now
[41123.138005] msm_restart : clear reset flag
Connected via ADB and ran e2fsck, but all appears ok.
Code:
e2fsck -pcfv /dev/block/mmcblk0p15
sh: badblocks: not found
/dev/block/mmcblk0p15: Updating bad block inode.
19845 inodes used (1.13%)
1139 non-contiguous files (5.7%)
19 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 19521/116/1
6040224 blocks used (86.35%)
0 bad blocks
1 large file
17771 regular files
1861 directories
0 character device files
0 block device files
5 fifos
0 links
191 symbolic links (185 fast symbolic links)
8 sockets
--------
19836 files
~ # ?[6ne2fsck -pcfv /dev/block/mmcblk0p17
e2fsck -pcfv /dev/block/mmcblk0p17
sh: badblocks: not found
/dev/block/mmcblk0p17: Updating bad block inode.
161 inodes used (0.30%)
19 non-contiguous files (11.8%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 153
34685 blocks used (16.13%)
0 bad blocks
0 large files
147 regular files
5 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
152 files
1) Did the file system already correct the previous errors, which is why none are detected now?
2) Any other commands/tests that can be run to determine really what is/was wrong?
any other thoughts on why this issue would occur?
Got another crash last night, again copying a lot of new music onto the phone from computer. Crash call stack is different this time though.
Code:
[ 7523.190689] Buffer I/O error on device mmcblk0p15, logical block 6850041
[ 7523.197373] Buffer I/O error on device mmcblk0p15, logical block 6850042
[ 7523.204241] Buffer I/O error on device mmcblk0p15, logical block 6850043
[ 7523.210711] Buffer I/O error on device mmcblk0p15, logical block 6850044
[ 7523.217395] Buffer I/O error on device mmcblk0p15, logical block 6850045
[ 7523.224140] Buffer I/O error on device mmcblk0p15, logical block 6850046
[ 7523.230732] Buffer I/O error on device mmcblk0p15, logical block 6850047
[ 7523.237721] Aborting journal on device mmcblk0p15-8.
[ 7523.288385] kgsl kgsl-3d0: |kgsl_late_resume_driver| late resume start
[ 7523.633754] cypress_touchkey 16-0020: not real interrupt (1).
[ 7524.010986] EXT4-fs error (device mmcblk0p15): ext4_journal_start_sb:328: Detected aborted journal
[ 7524.018982] EXT4-fs (mmcblk0p15): Remounting filesystem read-only
[ 7524.061985] Kernel panic - not syncing: EXT4-fs panic from previous error
[ 7524.062016]
[ 7524.069340] [<c00138c8>] (unwind_backtrace+0x0/0xe0) from [<c07b5180>] (panic+0x88/0x1f8)
[ 7524.077459] [<c07b5180>] (panic+0x88/0x1f8) from [<c01a0714>] (__ext4_abort+0xc0/0xe0)
[ 7524.085394] [<c01a0714>] (__ext4_abort+0xc0/0xe0) from [<c01a0b34>] (ext4_journal_start_sb+0x154/0x1b8)
[ 7524.094794] [<c01a0b34>] (ext4_journal_start_sb+0x154/0x1b8) from [<c018b140>] (ext4_dirty_inode+0x14/0x40)
[ 7524.104530] [<c018b140>] (ext4_dirty_inode+0x14/0x40) from [<c014e37c>] (__mark_inode_dirty+0x2c/0x1c4)
[ 7524.113839] [<c014e37c>] (__mark_inode_dirty+0x2c/0x1c4) from [<c0141c9c>] (file_update_time+0x100/0x120)
[ 7524.123392] [<c0141c9c>] (file_update_time+0x100/0x120) from [<c00f15a4>] (__generic_file_aio_write+0x2cc/0x428)
[ 7524.133586] [<c00f15a4>] (__generic_file_aio_write+0x2cc/0x428) from [<c00f1760>] (generic_file_aio_write+0x60/0xc8)
[ 7524.144085] [<c00f1760>] (generic_file_aio_write+0x60/0xc8) from [<c01819e4>] (ext4_file_write+0x258/0x2bc)
[ 7524.153821] [<c01819e4>] (ext4_file_write+0x258/0x2bc) from [<c012b108>] (do_sync_write+0x9c/0xd8)
[ 7524.162763] [<c012b108>] (do_sync_write+0x9c/0xd8) from [<c012b1ec>] (vfs_write+0xa8/0x130)
[ 7524.171095] [<c012b1ec>] (vfs_write+0xa8/0x130) from [<c012b414>] (sys_pwrite64+0x50/0x80)
[ 7524.179275] [<c012b414>] (sys_pwrite64+0x50/0x80) from [<c000de80>] (ret_fast_syscall+0x0/0x30)
[ 7524.188004] CPU1: stopping
[ 7524.190659] [<c00138c8>] (unwind_backtrace+0x0/0xe0) from [<c001294c>] (handle_IPI+0x100/0x1cc)
[ 7524.199357] [<c001294c>] (handle_IPI+0x100/0x1cc) from [<c0008670>] (gic_handle_irq+0xa8/0xb4)
[ 7524.207964] [<c0008670>] (gic_handle_irq+0xa8/0xb4) from [<c000dc3c>] (__irq_usr+0x3c/0x60)
[ 7524.216296] Exception stack(0xc6637fb0 to 0xc6637ff8)
[ 7524.221271] 7fa0: b65f8b76 b6ed66d7 b65f8b77 00000037
[ 7524.229481] 7fc0: 00000000 b6ed66da b65faba4 b65f8b54 b65f8b74 b796f610 b6ed5398 00000000
[ 7524.237630] 7fe0: 50704001 b65f8b3c b6ecb283 b6ebf55c 60030030 ffffffff
[ 7524.344360] Rebooting in 5 seconds..
[ 7529.347686] Going down for restart now
[ 7529.350708] msm_restart : clear reset flag
Wrong forum or the content too technical for people?
BSOD2600 said:
Phone: Galaxy S3 VZW 32GB
Recovery: TWRP 2.7.1.0
Mod: CM11 m8
Kernel, governer, etc all CM11 stock.
Problem:
Twice today the phone rebooted itself while performing large file copy operations. last_kmsg from both reboots basically look the same:
Code:
[40996.107363] Buffer I/O error on device mmcblk0p15, logical block 6751031
[40996.114291] Buffer I/O error on device mmcblk0p15, logical block 6751032
[40996.120761] Buffer I/O error on device mmcblk0p15, logical block 6751033
[40996.127476] Buffer I/O error on device mmcblk0p15, logical block 6751034
[40996.134160] Buffer I/O error on device mmcblk0p15, logical block 6751035
[40996.140813] Buffer I/O error on device mmcblk0p15, logical block 6751036
[40996.147528] Buffer I/O error on device mmcblk0p15, logical block 6751037
[40996.154181] Buffer I/O error on device mmcblk0p15, logical block 6751038
[40996.160926] Buffer I/O error on device mmcblk0p15, logical block 6751039
[41056.701656] ACDB=> get_hw_delay: Path = 0 samplerate = 48000 usec = 0 status 0
[41056.708065] afe_callback: cmd = 0x100dc returned error = 0x3
[41056.713681] afe_send_hw_delay: config cmd failed
[41065.991721] kgsl kgsl-3d0: |kgsl_late_resume_driver| late resume start
[41066.310781] cypress_touchkey 16-0020: not real interrupt (1).
[41117.725034] EXT4-fs error (device mmcblk0p15): ext4_mb_generate_buddy:741: group 113, 644 clusters in bitmap, 530 in gd
[41117.744476] Aborting journal on device mmcblk0p15-8.
[41117.764161] Kernel panic - not syncing: EXT4-fs (device mmcblk0p15): panic forced after error
[41117.764161]
[41117.773257] [<c0013ee8>] (unwind_backtrace+0x0/0xe0) from [<c0778f40>] (panic+0x88/0x1f8)
[41117.781344] [<c0778f40>] (panic+0x88/0x1f8) from [<c01a7134>] (ext4_handle_error+0x8c/0x98)
[41117.789738] [<c01a7134>] (ext4_handle_error+0x8c/0x98) from [<c01a7ca0>] (__ext4_grp_locked_error+0xe8/0x1c4)
[41117.799626] [<c01a7ca0>] (__ext4_grp_locked_error+0xe8/0x1c4) from [<c01b6618>] (ext4_mb_generate_buddy+0x25c/0x2e8)
[41117.810125] [<c01b6618>] (ext4_mb_generate_buddy+0x25c/0x2e8) from [<c01b8620>] (ext4_mb_init_cache+0x358/0x5f0)
[41117.820288] [<c01b8620>] (ext4_mb_init_cache+0x358/0x5f0) from [<c01b8db8>] (ext4_mb_load_buddy+0x278/0x2b4)
[41117.830085] [<c01b8db8>] (ext4_mb_load_buddy+0x278/0x2b4) from [<c01ba0fc>] (ext4_mb_find_by_goal+0x3c/0x23c)
[41117.840005] [<c01ba0fc>] (ext4_mb_find_by_goal+0x3c/0x23c) from [<c01ba9e0>] (ext4_mb_regular_allocator+0x4c/0x388)
[41117.850351] [<c01ba9e0>] (ext4_mb_regular_allocator+0x4c/0x388) from [<c01bc120>] (ext4_mb_new_blocks+0x1fc/0x5c0)
[41117.860728] [<c01bc120>] (ext4_mb_new_blocks+0x1fc/0x5c0) from [<c01b31d8>] (ext4_ext_map_blocks+0xfcc/0x15ac)
[41117.870739] [<c01b31d8>] (ext4_ext_map_blocks+0xfcc/0x15ac) from [<c018cf7c>] (ext4_map_blocks+0xf8/0x2e4)
[41117.880353] [<c018cf7c>] (ext4_map_blocks+0xf8/0x2e4) from [<c0190d4c>] (mpage_da_map_and_submit+0x114/0x57c)
[41117.890241] [<c0190d4c>] (mpage_da_map_and_submit+0x114/0x57c) from [<c0191908>] (ext4_da_writepages+0x340/0x5b8)
[41117.900496] [<c0191908>] (ext4_da_writepages+0x340/0x5b8) from [<c00ff3e0>] (do_writepages+0x24/0x38)
[41117.909713] [<c00ff3e0>] (do_writepages+0x24/0x38) from [<c00f6d14>] (__filemap_fdatawrite_range+0x60/0x6c)
[41117.919419] [<c00f6d14>] (__filemap_fdatawrite_range+0x60/0x6c) from [<c00f6de8>] (filemap_write_and_wait_range+0x34/0x68)
[41117.930436] [<c00f6de8>] (filemap_write_and_wait_range+0x34/0x68) from [<c0188ab0>] (ext4_sync_file+0xb4/0x414)
[41117.940447] [<c0188ab0>] (ext4_sync_file+0xb4/0x414) from [<c0158338>] (vfs_fsync_range+0x34/0x44)
[41117.949451] [<c0158338>] (vfs_fsync_range+0x34/0x44) from [<c0158368>] (vfs_fsync+0x20/0x28)
[41117.957874] [<c0158368>] (vfs_fsync+0x20/0x28) from [<c01586a0>] (sys_fdatasync+0x18/0x34)
[41117.966115] [<c01586a0>] (sys_fdatasync+0x18/0x34) from [<c000e000>] (ret_fast_syscall+0x0/0x30)
[41117.974874] CPU1: stopping
[41117.977529] [<c0013ee8>] (unwind_backtrace+0x0/0xe0) from [<c0012f6c>] (handle_IPI+0x100/0x1cc)
[41117.986258] [<c0012f6c>] (handle_IPI+0x100/0x1cc) from [<c0008670>] (gic_handle_irq+0xa8/0xb4)
[41117.994804] [<c0008670>] (gic_handle_irq+0xa8/0xb4) from [<c000ddbc>] (__irq_usr+0x3c/0x60)
[41118.003166] Exception stack(0xcb443fb0 to 0xcb443ff8)
[41118.008141] 3fa0: 75254dc0 752a4547 000001a4 00000564
[41118.016321] 3fc0: 00002000 00000010 00000612 75252000 bea932dc 75254f00 bea932ed 7522b6e8
[41118.024531] 3fe0: 40224e24 bea93268 40211be7 4021ab9c 80010030 ffffffff
[41118.131322] Rebooting in 5 seconds..
[41123.135045] Going down for restart now
[41123.138005] msm_restart : clear reset flag
Connected via ADB and ran e2fsck, but all appears ok.
Code:
e2fsck -pcfv /dev/block/mmcblk0p15
sh: badblocks: not found
/dev/block/mmcblk0p15: Updating bad block inode.
19845 inodes used (1.13%)
1139 non-contiguous files (5.7%)
19 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 19521/116/1
6040224 blocks used (86.35%)
0 bad blocks
1 large file
17771 regular files
1861 directories
0 character device files
0 block device files
5 fifos
0 links
191 symbolic links (185 fast symbolic links)
8 sockets
--------
19836 files
~ # ?[6ne2fsck -pcfv /dev/block/mmcblk0p17
e2fsck -pcfv /dev/block/mmcblk0p17
sh: badblocks: not found
/dev/block/mmcblk0p17: Updating bad block inode.
161 inodes used (0.30%)
19 non-contiguous files (11.8%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 153
34685 blocks used (16.13%)
0 bad blocks
0 large files
147 regular files
5 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
152 files
1) Did the file system already correct the previous errors, which is why none are detected now?
2) Any other commands/tests that can be run to determine really what is/was wrong?
Click to expand...
Click to collapse
Did you ever figure this out?
Was it transferring from SD to External SD? Or just to Internal?
Sent from my SCH-I535 using XDA Free mobile app
Nope, never figured this out and yes it's occurred more than once.
Seem to recall was transferring large file content from PC to Internal. Don't think it's happened with CM11m10 -- yet... but on the other hand I dont do large file transfers daily.
Still an issue with CM11m11 (or more likely the hardware). system reboot when deleting a ~300 MB file from within MX Player.
Code:
[52140.774902] Buffer I/O error on device mmcblk0p15, logical block 4134812
[52140.781556] end_request: I/O error, dev mmcblk0, sector 43663360
[52140.787874] Buffer I/O error on device mmcblk0p15, logical block 5046272
[52140.794405] end_request: I/O error, dev mmcblk0, sector 44711936
[52140.800387] Buffer I/O error on device mmcblk0p15, logical block 5177344
[52140.807254] Buffer I/O error on device mmcblk0p15, logical block 5242880
[52140.813846] Buffer I/O error on device mmcblk0p15, logical block 5275648
[57664.812106] EXT4-fs error (device mmcblk0p15): ext4_mb_generate_buddy:741: group 158, 2379 clusters in bitmap, 1936 in gd
[57664.822300] Aborting journal on device mmcblk0p15-8.
[57664.833928] Kernel panic - not syncing: EXT4-fs (device mmcblk0p15): panic forced after error
[57664.833928]
[57664.842962] [<c0013928>] (unwind_backtrace+0x0/0xe0) from [<c07abc78>] (panic+0x88/0x1f8)
[57664.851172] [<c07abc78>] (panic+0x88/0x1f8) from [<c01a257c>] (ext4_handle_error+0x8c/0x98)
[57664.859504] [<c01a257c>] (ext4_handle_error+0x8c/0x98) from [<c01a30e8>] (__ext4_grp_locked_error+0xe8/0x1c4)
[57664.869393] [<c01a30e8>] (__ext4_grp_locked_error+0xe8/0x1c4) from [<c01b1a60>] (ext4_mb_generate_buddy+0x25c/0x2e8)
[57664.879892] [<c01b1a60>] (ext4_mb_generate_buddy+0x25c/0x2e8) from [<c01b3a68>] (ext4_mb_init_cache+0x358/0x5f0)
[57664.890055] [<c01b3a68>] (ext4_mb_init_cache+0x358/0x5f0) from [<c01b4200>] (ext4_mb_load_buddy+0x278/0x2b4)
[57664.899852] [<c01b4200>] (ext4_mb_load_buddy+0x278/0x2b4) from [<c01b7ea4>] (ext4_free_blocks+0x578/0x9f0)
[57664.909436] [<c01b7ea4>] (ext4_free_blocks+0x578/0x9f0) from [<c01ac74c>] (ext4_ext_remove_space+0x6ec/0xe94)
[57664.919385] [<c01ac74c>] (ext4_ext_remove_space+0x6ec/0xe94) from [<c01aed00>] (ext4_ext_truncate+0x100/0x1d0)
[57664.929365] [<c01aed00>] (ext4_ext_truncate+0x100/0x1d0) from [<c0188a24>] (ext4_truncate+0xb4/0x174)
[57664.938582] [<c0188a24>] (ext4_truncate+0xb4/0x174) from [<c018d2c0>] (ext4_evict_inode+0x328/0x490)
[57664.947678] [<c018d2c0>] (ext4_evict_inode+0x328/0x490) from [<c0142c84>] (evict+0x94/0x158)
[57664.956101] [<c0142c84>] (evict+0x94/0x158) from [<c0139f50>] (do_unlinkat+0xe8/0x130)
[57664.963975] [<c0139f50>] (do_unlinkat+0xe8/0x130) from [<c000dec0>] (ret_fast_syscall+0x0/0x30)
[57665.072964] Rebooting in 5 seconds..
[57670.076779] Going down for restart now
[57670.079800] msm_restart : clear reset flag