My brother gave me his XT1032 for fixing, so far this is pretty easy but there is something wrong this time
* TWRP does not delete anything from data, system, sdcard, etc
I have tried everything
* Wiping all partitions
* Mounting everything
* Flashing the original firmware through fastboot
But it seems like it still does not delete anything from the phone or at least overwrite the stuff.
Can anyone help me?
Thanks in advance.
Some Moto G seem to develop (unfixable?) hardware issues with the eMMC. After wiping your partitions in TWRP (and before rebooting), pull a kernel log (adb shell dmesg > dmesg.txt) and look for error messages containing "mmc".
_that said:
Some Moto G seem to develop (unfixable?) hardware issues with the eMMC. After wiping your partitions in TWRP (and before rebooting), pull a kernel log (adb shell dmesg > dmesg.txt) and look for error messages containing "mmc".
Click to expand...
Click to collapse
This is what I get, I really don't know what to do with this info or what it means ._.
I am really sorry to waste your time but could you see if there is something fixable?
zeratos said:
This is what I get, I really don't know what to do with this info or what it means ._.
I am really sorry to waste your time but could you see if there is something fixable?
Click to expand...
Click to collapse
That doesn't look like a log from TWRP after wiping anything. Anyway, I'm seeing lots of errors like this:
Code:
<3>[ 25.030812,0] end_request: I/O error, dev mmcblk0, sector 1572456
<4>[ 25.030829,0] quiet_error: 54 callbacks suppressed
<3>[ 25.030840,0] Buffer I/O error on device mmcblk0p33, logical block 165357
<4>[ 25.030851,0] lost page write due to I/O error on mmcblk0p33
<3>[ 25.030881,0] Buffer I/O error on device mmcblk0p33, logical block 165358
which indicates that the kernel can't write to the device. I may be wrong but I believe that this is an unrecoverable hardware error.
_that said:
That doesn't look like a log from TWRP after wiping anything.
Click to expand...
Click to collapse
I know, it's because TWRP is not wiping anything, it says it did but everything stays the same, I am using twrp-3.0.2-2-falcon and the log was done after wiping everything and pulling the log before rebooting btw :/
_that said:
Anyway, I'm seeing lots of errors like this:
Code:
<3>[ 25.030812,0] end_request: I/O error, dev mmcblk0, sector 1572456
<4>[ 25.030829,0] quiet_error: 54 callbacks suppressed
<3>[ 25.030840,0] Buffer I/O error on device mmcblk0p33, logical block 165357
<4>[ 25.030851,0] lost page write due to I/O error on mmcblk0p33
<3>[ 25.030881,0] Buffer I/O error on device mmcblk0p33, logical block 165358
which indicates that the kernel can't write to the device. I may be wrong but I believe that this is an unrecoverable hardware error.
Click to expand...
Click to collapse
Man, that sucks, do you know what may have caused of this? Or was this just a bad luck generated error?
Thank you for your time BTW.
zeratos said:
Man, that sucks, do you know what may have caused of this?
Click to expand...
Click to collapse
No idea, I've seen similar reports from other users in this forum but no information about possible causes.
Related
props to scotty & tmzt
BE CAREFUL WHAT PARTITION YOU'RE DD'ING INTO OTHERWISE YOU'LL END WITH A BRICK.
Instructions
1: Get VISIONary from the market and do a temp root
2: download http://rapidshare.com/files/429891451/dhd_root.zip and extract.
Place these files in /sdcard/ on your DHD (you only need 1 of the .ko, depending on your kernel version - check with uname -a in adb shell)
Go to adb shell, switch to root (su) and do the following:
insmod /sdcard/wp-(version).ko
for example: insmod /sdcard/wp_g5ed1769.ko
This will disable wp (will be enabled on reboot though...)
dd if=/sdcard/hboot_eng.nb0 of=/dev/block/mmcblk0p18
This will install engineering hboot
BE CAREFUL - DOUBLE CHECK THE PARTITION
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21
OR
save recovery.img somewhere on your HDD, open a shell/cmd in that directory and:
fastboot flash recovery recovery.img
Both ways will install an unsecured recovery (not clockwork yet)
The module is for the release version of DHD (2.32.21-g5ed1769)
If you have another one, you can easily mod it:
check your version via:
cat /proc/version
Download a Hex Editor, search for vermagic in the wp_g5ed1769.ko, and replace patch version with:
g5ed1769
Save
Reload to sdcard and follow instructions from the top.
You can now PERMROOT (once you load the module, just push su and Superuser.apk to /sdcard/)
and
copy su to /system/bin/
and Superuser.apk to /system/app/
Don't forget to suid su:
su
chmod 4755 /system/bin/su
NOTE:
once you load the module, you can confirm a successful load via:
dmesg|tail
here's a sample output
<3>[ 881.934631] mmc0: DMA channel flushed (0x80000004)
<3>[ 881.935241] Flush data: 00000000 00000000 00000103 c0088008 c7e38000 00000001
<6>[ 881.935913] mmc0: Controller has been reset
<6>[ 881.936279] mmc0: Worked around bug 1535304
<3>[ 881.941802] mmcblk0: error -110 sending status comand
<3>[ 881.942443] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
<3>[ 881.943084] mmcblk0: error -5 transferring data, sector 327712, nr 8, card status 0x0
<6>[ 881.943695] mmc0: reinit card
<4>[ 881.944030] mmc0: Starting deferred resume
<6>[ 882.010437] mmc0: Deferred resume completed
What about adb pushing su and Superuser.apk WHILE flashing a STOCK ROM via RUU? The eventual signatures check is in the beginning only and thus irrelevant for this procedure.
During this length process, the real SYSTEM: is unlocked, and we should be able to do anything we want during that time.
Basically, we just need to check till /system/bin/su is copied from the RUU, THEN push ours, in order to prevent overwriting by the stock one.
This SHOULD, at least in theory, allow us to have persistent root. Can anybody check that?
While flashing the via RRU every file that is pushed is sig checked... Besides we cant push spcific files in RRU anyway :-|
And before anyone says recovery ADB is locked down in recovery so cant push anything that way :-(
Tbh we have two hopes... Have a singed test recovery to flash we need a shipping desire hd to test this -- (first desire root type)
And the G2 root ppl the hd will have the same protection as the G2
Sent from my GT-I9000 using XDA App
I was just pushing ideas around, things I need to check anyway.
It's hard to do any real work without a device to work on (yet - should be shipped by next week).
It WOULD be great if anyone could come forward with a test/engineering device I could work with. Maybe a test/engineering partitions dump?
Since I am *still* waiting for my device (thanks HT...) and can't field test any of my ideas, I've been filing a few of them in the G2 forum.
The latest one being http://forum.xda-developers.com/showpost.php?p=8818111&postcount=184
adwinp said:
Since I am *still* waiting for my device (thanks HT...) and can't field test any of my ideas, I've been filing a few of them in the G2 forum.
The latest one being http://forum.xda-developers.com/showpost.php?p=8818111&postcount=184
Click to expand...
Click to collapse
Getting my HD on Friday hopefully will hand it over to team villainrom and see what we can do grrrr
R.E is a b*****.
If only we had access to an engineering device, we could dump pmem (since we know at what address HBoot is loaded anyway), compare that to a retail device, and try some binary patching the HBoot via userland and/or a module....
I have just thought about it: can the lock be related to path, not to address or something? Maybe you could symlink /system somewhere in /data (somewhere that is writable normally) and write through this symlink? Kinda improbable but worth trying...
Sent from my HDfied HTC Desire
Sent from my HDfied HTC Desire
K900 said:
I have just thought about it: can the lock be related to path, not to address or something? Maybe you could symlink /system somewhere in /data (somewhere that is writable normally) and write through this symlink? Kinda improbable but worth trying...
Sent from my HDfied HTC Desire
Sent from my HDfied HTC Desire
Click to expand...
Click to collapse
Unfortunately it doesn't work that way.
;]
A symlink inherits all properties of the parent.
It's like trying to change tires in a car with a broken down engine. You won't be able to drive it, no matter what the tires.
adwinp said:
Unfortunately it doesn't work that way.
;]
A symlink inherits all properties of the parent.
It's like trying to change tires in a car with a broken down engine. You won't be able to drive it, no matter what the tires.
Click to expand...
Click to collapse
I think the lock is not in the FS, it's somewhere lower level, so it just might work
Sent from my HDfied HTC Desire
K900 said:
I think the lock is not in the FS, it's somewhere lower level, so it just might work
Sent from my HDfied HTC Desire
Click to expand...
Click to collapse
We do know where the lock is; here, have some nice reading (the parts pertaining to emmc):
http://forum.xda-developers.com/showthread.php?t=803208
adwinp said:
We do know where the lock is; here, have some nice reading (the parts pertaining to emmc):
http://forum.xda-developers.com/showthread.php?t=803208
Click to expand...
Click to collapse
Oh, then it's a phail.
Sent from my HDfied HTC Desire
K900 said:
Oh, then it's a phail.
Sent from my HDfied HTC Desire
Click to expand...
Click to collapse
No. http://tjworld.net/wiki/Android/HTC/Vision/HbootAnalysis
Great work is being done by "IntuitiveNipple".
adwinp said:
No. http://tjworld.net/wiki/Android/HTC/Vision/HbootAnalysis
Great work is being done by "IntuitiveNipple".
Click to expand...
Click to collapse
Not rooting at all, just my idea
Sent from my HDfied HTC Desire
hey, first post in the android section, still awaiting the arrival of DHD, after alot of reading about getting root, i was thinking, as mentioned above somewhere, the update process does'nt allow pushing of specific files, this got me thinking of a Windows Live games security wich was supposed to block those pesky cheaters of using RAM intercepts of running processes.
isn't it a possibility to intercept the write buffer before it outputs to device and replace neccesary files to gain root access? in other words, patch it with superuser.akp via injection or disable nand security listening?
run a rom installer with a signed rom > output to virtual device(or buffer) > patch the neccesary files > (output altered dataflow in sections we need so physical device still believes its signed as the checks are still there on update.) to physical device
could this work?
What about change one of signed file from oficial ROM/OTA update?
As far as I understand digital signature is based on SHA-1 which is kind of "broken".
So we have to choose some file in official update zip, change its contents to "useful_part+garbage_to_match_sha1" and update
just google "sha-1 broken"
Golomidov said:
What about change one of signed file from oficial ROM/OTA update?
As far as I understand digital signature is based on SHA-1 which is kind of "broken".
So we have to choose some file in official update zip, change its contents to "useful_part+garbage_to_match_sha1" and update
just google "sha-1 broken"
Click to expand...
Click to collapse
It's almost impossible to get a sha1 hash to match. But I wonder if we can reverse engineer the RUU and make it skip hash checks or check against the modified file's hash
Sent from my HDfied HTC Desire
@WendigoNL: the ruu itself doesn't do anything. All the work is done by HBoot.
adwinp said:
@WendigoNL: the ruu itself doesn't do anything. All the work is done by HBoot.
Click to expand...
Click to collapse
i thought the ruu does something?
doesn't send adb reboot bootloader and then fastboot oem -78 command? and put it in ruu mode?but before all that, doesn't it push the rom.zip somewhere? :S
sorry just want clarification. i know this method won't work as the bootloader will check the signed keys on the zip file so you can't hijack the rom.zip file, i.e. in the temp folder replace rom.zip with a test ruu or even a custom rom with SU and and custom recovery pushed in the zip file.
i may be completely wrong and look forward to your answer adwinp.
i may try this when i get home but i know htc arnt THAT stupid
New baseband in 1.32.405.6 update, version number: 12.28b.60.140eU_26.03.02.26_M
Hi guys, I did google and tried some tricks for a while, here's the problem:
When tried reach /sdcard from recovery-clockwork-touch-5.8.0.2-crespo, it just said:
E:unable to write to ums lunfile
Click to expand...
Click to collapse
dmesg (full version on pastebin):
<3>[ 4.306209] mmc0: error -110 whilst initialising MMC card
<7>[ 4.307670] Universal : Card status 1
Click to expand...
Click to collapse
cat /proc/kmsg | grep mmc0:
~ # cat /proc/kmsg | grep mmc0
<6>[ 2.668910] mmc0: SDHCI controller on samsung-hsmmc [s3c-sdhci.0] using ADMA
<3>[ 4.306209] mmc0: error -110 whilst initialising MMC card
Click to expand...
Click to collapse
The weird thing is that I've read a post said "fast oem lock, fast oem unlock" will do the trick. So my bootloader is locked again. But "fastboot oem unlock" said "Erase Failed"
Btw, I've tried [APP] Linux Tool for Bricked Nexus S after firmware update and don't know how to do with it ("Injection Failed" in bootloader and recovery screen).
I'm on a archlinux box, please help me. Thank you.
..
Hi,
Thank you for the reply. Will try to flash the bootloader and the hairdryer thing when come back home.
Btw, I flash the recovery back to recovery-clockwork-5.0.2.0-crespo with adb in recovery mode:
adb push recovery-new.img /sdcard/recovery-new.img
adb shell flash_image recovery /sdcard/recovery-new.img
Click to expand...
Click to collapse
Hope this may help someone else. (The /sdcard there is not the "real" sdcard, it's a folder or mount point.)
..
Ok, I flashed the bootloader from recovery, still "erase fail" when "fastboot oem unlock".
I tried to flash all *.img found in stock rom .zip file, and push the /system (no idea what I was doing...). No miracle happened.
I'm not sure about the "flash-chip" and "parted" you mentioned, but I'll try it, thank you.
-.-.- Updated 2012.4.30 -.-.-
For those still interesting: I bring the phone to a local repair store. The guy changed the chip, and boot the phone with success. But after the reboot, the screen freeze come again... (THE END)
..
Hi All,
I have been flashing back and forth a bit from CM9 to CM10 to try things out. Today, I attempted to restore back to CM9 and it hung for over an hour, so I hard restarted it. Now, I can't restore anything, because it hangs on the /cache partition. I also receive the message while in recovery mode
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Click to expand...
Click to collapse
I am able to get adb shell in recovery mode and I have gone through the steps to check for a bad emmc, which did not indicate badness. I have attempted to use umount from the shell on /cache, which just hangs. In recovery mode, over adb shell, I can ls and cat any of the files in /cache without apparent issue.
I have attempted Super Wipe, factory reset, manual formatting, and wipe cache, all to no avail (they all just hang).
I am running CWM 6.0.1.1.
dmesg has a message about an ext4 error, that makes me suspicious, but I don't know what to do about it.
<4>[ 8.431030] EXT4-fs warning (device mmcblk0p26): ext4_clear_journal_err:4154: Filesystem error recorded from previous mount: IO failure
<4>[ 8.442413] EXT4-fs warning (device mmcblk0p26): ext4_clear_journal_err:4155: Marking fs in need of filesystem check.
<4>[ 8.462036] EXT4-fs (mmcblk0p26): warning: mounting fs with errors, running e2fsck is recommended
<6>[ 8.475463] EXT4-fs (mmcblk0p26): recovery complete
<6>[ 8.489562] EXT4-fs (mmcblk0p26): mounted filesystem with ordered data mode. Opts:
<6>[ 9.242095] key released
<6>[ 9.243774] key released
<6>[ 9.442749] msmsdcc_runtime_suspend: Enter WIFI suspend
<6>[ 9.542755] fsa9480 5-0025: fsa9480_init_detect
<6>[ 9.547424] fsa9480 5-0025: dev1: 0x0, dev2: 0x0
<2>[ 13.382751] EXT4-fs error (device mmcblk0p26): ext4_init_inode_table:1293: comm ext4lazyinit: Something is wrong with group 0
<2>[ 13.382751] Used itable blocks: 403itable unused count: 0
<2>[ 13.382781]
<3>[ 13.411773] Aborting journal on device mmcblk0p26-8.
<2>[ 13.429321] EXT4-fs (mmcblk0p26): Remounting filesystem read-only
Click to expand...
Click to collapse
Apparently my full dmesg output was too long, so if you need anything else please ask.
Thanks in advance for any help!
I am experiencing the same thing (I think) as the OP.
I had been running alpha2 of TeamChopsticks CM10. I installed the new recovery for the skyrocket (downloaded from teamchopsticks.org). Then rebooted into recovery. formatted /system -> installed alpha3 -> installed gapps -> installed darkside-wipe-cache-only -> rebooted. Then my phone just hung on the boot animation for 10+ minutes.
After rebooting I thought I would try to install alpha2 again. I tried to format /system, and it hung.
So I rebooted again, and tried to restore a backup. That hung on "Restoring .android_secure..."
So, I rebooted again. This time I tried a factory reset. It hung on "Wiping cache..."
After rebooting this time, I selected "show log" in CWM, which shows this (I don't know if this is helpful/related):
Code:
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Can't partition unsafe device: /dev/block/mmcblk1p1
I:Can't format unknown volume: /external_sd
I have also tried Fixing Permissions in CWM, with no apparent change.
Also, any time I perform an action in CWM (show logs, fix permissions, etc.) and select "go back" in the menu, the menu disappears. I am still in recovery (still see the CWM logo in the background, and see the text from my previous action), but buttons do nothing and there is no menu.
Any help would be appreciated.
Josh
---------- Post added at 10:58 AM ---------- Previous post was at 10:20 AM ----------
Another follow up to my previous post:
I have tried to reinstall cm9 and cm10 alpha2.
With each I format /system, then when I select "Go Back" in the CWM menu the menu disappears (as I mentioned before). So, I reboot, then install zip from SD -> select the cm zip and get this:
Code:
CWM-based Recovery v6.0.1.1
-- Installing: /sdcard/cm-9-20120715-EXPERIMENTAL-skyrocket-beta1.zip
And nothing after that. It will just sit there.
Don't use darkside wipe, reflash sk8ers recovery From his thread
Posted w/xda app w/ i727R
MY STICKIES
| ROMS | KERNELS | FIRMWARE | RADIOS | HOWTO'S | GUIDES | INFo |
NEWB GUIDES TO: RESTORE TO STOCK | USE ODIN | INSTALL CWM | ROOT |
vincom said:
Don't use darkside wipe, reflash sk8ers recovery From his thread
Click to expand...
Click to collapse
Interestingly (and perhaps ironically), looks like sk8er may be adding the Darkside Tools option in a forthcoming Recovery....
http://forum.xda-developers.com/showpost.php?p=30639023&postcount=267
That's pretty hilarious, so Darkside Wipe is apparently the way to go, except it doesn't work in my case.
So, I tried installing that recovery but it won't install (just like everything else).
I get this:
Code:
CWM-based Recovery v6.0.1.1
-- Installing: /sdcard/cwm6012touch_v11.zip
Is there a way to install his recovery that I am not aware of?
Thanks,
Josh
Fantastic! With some help from the TeamChopsticks IRC channel, particularly sk8erwitskil, I installed CWM Touch 6.0.1.2 and was able to restore a backup of CM9 without an issue. Now that I can do that, I'm going to give CM10 alpha 3 another go.
Please see http://forum.xda-developers.com/showthread.php?t=1777970 for any further help with the recovery.
Cheers!
cthrax said:
Fantastic! With some help from the TeamChopsticks IRC channel, particularly sk8erwitskil, I installed CWM Touch 6.0.1.2 and was able to restore a backup of CM9 without an issue. Now that I can do that, I'm going to give CM10 alpha 3 another go.
Please see http://forum.xda-developers.com/showthread.php?t=1777970 for any further help with the recovery.
Cheers!
Click to expand...
Click to collapse
Why could u install the recovery and what was the solution
Posted w/xda app w/ i727R
MY STICKIES
| ROMS | KERNELS | FIRMWARE | RADIOS | HOWTO'S | GUIDES | INFo |
NEWB GUIDES TO: RESTORE TO STOCK | USE ODIN | INSTALL CWM | ROOT |
I didn't do anything special to install recovery. I pushed the zip to my external card and installed it via the recovery. I assume the cache was not needed to be overwritten for the recovery install.
cthrax said:
I didn't do anything special to install recovery. I pushed the zip to my external card and installed it via the recovery. I assume the cache was not needed to be overwritten for the recovery install.
Click to expand...
Click to collapse
thats the way its done, i just dont understand why you couldnt do it the first place, and the cache has nothing todo with recovery just the rom
Ah, that's a confusion of terms. The original issue was that I could not restore from a backup. Or install a new rom. Apparently installing a new recovery was not an issue, I just didn't know that installing that would help at the time.
I just wanted to follow up that I was able to get my phone back thanks to help from Meanstreak242 in the IRC channel.
I ended up using an adb shell to dd the recovery image to the recovery partition (I *think* it was partition 22).
joshjryan said:
I just wanted to follow up that I was able to get my phone back thanks to help from Meanstreak242 in the IRC channel.
I ended up using an adb shell to dd the recovery image to the recovery partition (I *think* it was partition 22).
Click to expand...
Click to collapse
I'm gonna give this a go as well. Vin, seems you were onto something regarding usage in adb. I've been getting really familiar with it since. And now check out his results. Hopefully this'll work out for me too!!
KillaT21 said:
I'm gonna give this a go as well. Vin, seems you were onto something regarding usage in adb. I've been getting really familiar with it since. And now check out his results. Hopefully this'll work out for me too!!
Click to expand...
Click to collapse
Another no go. Cthrax, can you post or pm me exactly what you did?
KillaT21 said:
Another no go. Cthrax, can you post or pm me exactly what you did?
Click to expand...
Click to collapse
1. Mount phone as USB device
2. Copy newer version of ClockWorkMod Touch
3. Go back into recovery and "install zip from flash"
4. Reboot and restore backup.
5. Profit!
cthrax said:
1. Mount phone as USB device
2. Copy newer version of ClockWorkMod Touch
3. Go back into recovery and "install zip from flash"
4. Reboot and restore backup.
5. Profit!
Click to expand...
Click to collapse
well I didnt have the exact circumstance of doing a restore. I just need to format my partitions so that would hopefully allow me to flash something else. My system basically tries its hardest to stay as Read Only. Even when I mount the system, nothing. I was hoping that with a new recovery I could. It "flashes", but once i reboot, its the same o Clockworkmod Recovery v5.8.1.3
KillaT21 said:
well I didnt have the exact circumstance of doing a restore. I just need to format my partitions so that would hopefully allow me to flash something else. My system basically tries its hardest to stay as Read Only. Even when I mount the system, nothing. I was hoping that with a new recovery I could. It "flashes", but once i reboot, its the same o Clockworkmod Recovery v5.8.1.3
Click to expand...
Click to collapse
Maybe your variant of the problem is closer to what joshjryan did then. He had to use adb shell to manually use dd to copy the bits over. Hopefully he's watching and can chime in with some more comments.
Well, joshjryan, I hope youre reading this too.
This caught my attention after a dmesg:
<6>[ 1478.616302] EXT4-fs (mmcblk0p24): mounted filesystem with ordered data mod
e. Opts:
So then I
~ # parted /dev/block/mmcblk0p24
parted /dev/block/mmcblk0p24
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p24
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: Generic SD/MMC Storage Card (sd/mmc)
Disk /dev/block/mmcblk0p24: 627MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Could this be the cause??
Number Start End Size File system Flags
1 0.00B 627MB 627MB ext4
(parted)
cthrax said:
Maybe your variant of the problem is closer to what joshjryan did then. He had to use adb shell to manually use dd to copy the bits over. Hopefully he's watching and can chime in with some more comments.
Click to expand...
Click to collapse
This does sound similar to what I was seeing.
I also was not able to actually install the new recovery. So I did this:
I extracted cwm0612touch to get recovery.img
Then I mounted my phones SB by USB and copied recovery.img to my sd card
Then in the adb shell to my phone I used dd to copy the image to the appropriate partition
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
Hopefully that does the trick for you!
joshjryan said:
This does sound similar to what I was seeing.
I also was not able to actually install the new recovery. So I did this:
I extracted cwm0612touch to get recovery.img
Then I mounted my phones SB by USB and copied recovery.img to my sd card
Then in the adb shell to my phone I used dd to copy the image to the appropriate partition
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
Hopefully that does the trick for you!
Click to expand...
Click to collapse
It didnt. It installed to the right partition, but after reboot, cwmtouch5.8.1.3 is there again
Is it something in my reboot/boot that causes that?
Hey Guys,
For the past few weeks, I have been suffering from file system corruption on my /data partition, and have been trying to fix it. The phone gives me SOD's and random reboots (kernel related) and the last kmsg.logs tell me about ext-4 fs errors and journal corruption ( something along the lines of that). I have ran e2fsck on /data, /cache/, and /system and it always fixes all the errors but after time they always re-appear and I know because of an SOD or reboot, and lather, rinse, and repeat. I came to the conclusion that maybe there are newly developed bad blocks on the internal NAND which continuously corrupt the filesystem by reading and writing to them, and I want to get them marked. Running e2fsck -c gave me: Badblocks not found, and so I searched on what to do. I came across a thread that said push the Badblocks binary to sbin and tried that, but now I get "Illegal Instruction" instead of No Badblocks Binary. What can I do to mark these blocks? Is there an alternative to at least check to see if bad blocks are present? Thanks in advance.
Hello T-R42/K-R42/CS918 owners,
i have a problem with wifi: it does not work more
BUT perhaps you could help me and others with similar problems:
open the terminal and type: cat /sys/class/rkwifi/chip
and post the result on this thread , adding the model and board version you have (if you know it)
Thanks a lot!
Vicolodo said:
Hello T-R42/K-R42/CS918 owners,
i have a problem with wifi: it does not work more
BUT perhaps you could help me and others with similar problems:
open the terminal and type: cat /sys/class/rkwifi/chip
and post the result on this thread , adding the model and board version you have (if you know it)
Thanks a lot!
Click to expand...
Click to collapse
I have "[email protected]" changed from "[email protected]" after I executed the command with su or without, the result is the same, Nothing else displayed. My board verion 1.0 AP6210 wifi chip.
buhohitr said:
I have "[email protected]" changed from "[email protected]" after I executed the command with su or without, the result is the same, Nothing else displayed. My board verion 1.0 AP6210 wifi chip.
Click to expand...
Click to collapse
thank you!
i found that RK901 is hard-coded into the kernel, as you can read here:
it depends on the parameters used compiling the kernel:
in fact i found this:
https://github.com/gripped/MK808-he...net/wireless.orig/wifi_sys/rkwifi_sys_iface.c
i am not an expert, but i think that is the kernel procedure that writes the attributes of the class for wifi on the file system,
one of which is the file /sys/class/rkwifi/chip
the fact that we have all RK901 is because all (almost) our kernels have been compiled with the configuration
#ifdef CONFIG_RK901
I dont know if my device instead should use a different kernel (compiled with other configuration),
but i think that probably RK901 is the right value also for my device
This because i think that the cause of my problem is different:
seems that the problem is caused by an error returned by the insmod (insert module) procedure
(called by the load driver procedure ,
that perhaps it is something like what can be found here
https://github.com/aloksinha2001/pi****u-3.0.8-alok/blob/master/RK30_MT5931_MT6622/wifi/wifi.c
)
The insmod function does these two things:
- allocates memory for the driver and loads the file (rkwifi.ko) on this area:
module = load_file(filename_release, &size);
- initialize the module
ret = init_module(module, size, args);
One of this two events went wrong, because i am sure insmod in my case returns -1
I went to this conclusion following the logcat trace and searching infomations on the web, as you can see here
http://www.freaktab.com/showthread.php?11523-why-wifi-not-working-here-there-is-the-answer
i read somewhere that the init_module may return error when the user has not the permission to insert the module into the kernel...
so can be that some permission is missing ...like a problem caused by rooting, where i have no more root permissions after flashing the ROM...or something like that...
do you have any suggestion?
Thanks a lot!
I still believe you haven't flash the full rom correctly. You need to reflash a full stock rom where it will reformat your nano and replacing all the correct files with all the correct permission. Currently you are trying to fix many holes in the rom/kernel and just a big waist of time. When you reformat your device and flash a full rom it should address all the issues. I have been working on so many Android devices and if you could format and reflash the stock rom, it solved everything unless your hardware is in question. One thing I noticed is that if you have a proper flash your device should be seen by your PC. Once your pc communication is fixed, you should able to flash full rom using batch tool. Before you flash the full rom, the batch tool is going to do a low level formatting (which did help me in the past where I soft brick my device). So the key thing here is focus on make your pc see your device. First start with the bootloader, then recovery, then the rest. Your nano is properly corrupted, so you need to reformat the nano and reflash the bootloader.