Database Info

Cyanogenized Rogers - Build-Environment [v3.3]

This is a build-environment which adds all that great stuff from CyanogenMod to the rogers-rom.
This will add following features to CyanogenMod (Version 3.4) like:
* Enhanced ramdisk to mount partitions with noatime/nodiratime (perf boost)
* Apps2SD via AUFS (same as UnionFS) enabled by default!
* Uses Ext3 for Apps2SD
* Optimized kernel (no debug options, cfq iosched)
* Maximum CPU scaling frequency set to 528MHz
Thanks to all involved people ... jesusfreke, haykuro, virtudude (thanks for sharing the build-environment), CYANOGEN and all I didn't mention!
*** AT YOUR OWN RISK ***
This build-environment will generate a very *** experimental *** rom for you.
Like the original ROM from haykuro, this requires SPL 1.33.2005 - info about this SPL is available here:
(*** WARNING - Potential Bricking - Read carefully *** )
http://forum.xda-developers.com/showpost.php?p=3816278&postcount=3
Downloads:
Build-Environment:
http://drop.io/kaobiore/asset/rogers-cyanogenized-v3-3-build-tar-gz
Have fun!
-kaobiore-

Is the boot.img the major difference? Can I just flash it instead of installing the whole ROM if I'm currently on Soulife's Roger's ROM?

Very theoretically yes ... but yeah ... it would be really hard to do (using different methods of flashing / replacing files).
If you really want to do it ... drop me a private message (remember ... it will be quite hard to do - you know what fastboot and adb is?) and will give you instruction how to do it.
But anyway ... I've included the build-environment (which was created originally by jesusfreke and was adepted by virtudude for rogers) and this could be used by other devs or even you to build your own rom.

I flashed boot.img without any side effects (that I've seen). Is there a way to verify whether or not I'm taking advantage of anything? I'm going to flash the whole build and check it out.

grokdesigns said:
I flashed boot.img without any side effects (that I've seen). Is there a way to verify whether or not I'm taking advantage of anything? I'm going to flash the whole build and check it out.
Click to expand...
Click to collapse
if you only flash boot.img:
wifi wont work ... app2sd is messed up
The better choice is to flash my build ...

Flashed the whole build without wiping from Soulife's Rogers' ROM. Everything seems to work fine. AUFS is working correctly (apps weren't automatically moved to SD, but that's fine). Nice build!

grokdesigns said:
Flashed the whole build without wiping from Soulife's Rogers' ROM. Everything seems to work fine. AUFS is working correctly (apps weren't automatically moved to SD, but that's fine). Nice build!
Click to expand...
Click to collapse
Are you already on a ext3-filesystem (apps2sd)?
You could check that by using "mount"-command in console - you should find a line similar to this:
/dev/block/mmcblk0p2 on /system/sd type ext3 (rw,noatime,nodiratime,errors=continue,data=ordered)

exactly what I want, thanks. downloading.

kaobiore said:
Are you already on a ext3-filesystem (apps2sd)?
You could check that by using "mount"-command in console - you should find a line similar to this:
/dev/block/mmcblk0p2 on /system/sd type ext3 (rw,noatime,nodiratime,errors=continue,data=ordered)
Click to expand...
Click to collapse
Yes I already had an ext3 partition and yes, I have that mount entry. I installed a new application and it correctly went to /system/sd/app, but my old programs are still in /system/intmem/app. Like I said, not a big deal, they're easily moved.

update wont install get:
E: Can't chown/mod /data/app
E:Failure at line 63:
set_perm_100 1000 0771 DATA:app
Installation aborted

nabzilla1990 said:
update wont install get:
E: Can't chown/mod /data/app
E:Failure at line 63:
set_perm_100 1000 0771 DATA:app
Installation aborted
Click to expand...
Click to collapse
I hit exactly the same problem, end up extract boot.img from update.zip and
flashed this way
Code:
# cat /dev/zero >> /dev/mtd/mtd2
write: No space left on device [this is ok, you can ignore]
# flash_image boot /sdcard/boot.img
works fine after that

so i do this before I flash the update

EDIT: Realized that HTC Sync was mentioned in the OP.

gladoo said:
I hit exactly the same problem, end up extract boot.img from update.zip and
flashed this way
Code:
# cat /dev/zero >> /dev/mtd/mtd2
write: No space left on device [this is ok, you can ignore]
# flash_image boot /sdcard/boot.img
works fine after that
Click to expand...
Click to collapse
Are you guys using the latest SPL from haykuro (1.33.2005)?
This SPL is mandatory - please see first post for info/instruction!

yes im using the latest spl but worked with those commands

kaobiore said:
Are you guys using the latest SPL from haykuro (1.33.2005)?
This SPL is mandatory - please see first post for info/instruction!
Click to expand...
Click to collapse
I am on the new SPL and am upgrading from virtuadude v3. I also get this error.
Code:
E: Can't chown/mod /data/app
E:Failure at line 63:
set_perm_100 1000 0771 DATA:app
Installation aborted
Is it possible that it has to do with having the lucid apps to sd previously? I am a linux noob, but that is the only thing I can think of.

glock30 said:
I am on the new SPL and am upgrading from virtuadude v3. I also get this error.
Code:
E: Can't chown/mod /data/app
E:Failure at line 63:
set_perm_100 1000 0771 DATA:app
Installation aborted
Is it possible that it has to do with having the lucid apps to sd previously? I am a linux noob, but that is the only thing I can think of.
Click to expand...
Click to collapse
Mmmmhh ... could be.
Could you please try to wipe before flashing my rom?
Are all others who are having this problem using an app2sd-card-mod?
If yes, which one?

did a wipe and fresh ex3 partition still gave me that error but fine after the commands really fast build love it

nabzilla1990 said:
did a wipe and fresh ex3 partition still gave me that error but fine after the commands really fast build love it
Click to expand...
Click to collapse
Mmmmh ... weird ... I going to remove this set_perm-command (update-script) and will upload version 2.
Sorry for that ...

I actually did do a wipe... I tried once again with a wipe... still the same issue. Tried using the info gladoo posted and ended up with a endless loop at the HTC screen... ended up going back to vurtuadude's for now... Hopefully this info helps.

Rooting CDMA Hero [Mac]

Root the CDMA Hero
Edit: I assumed that everyone knew that you needed the Android SDK to root. If you didn't know and/or don't have it, you can download it from here. http://developer.android.com/sdk/index.html. Extract it to a location of your choice. I put mine in /Users/Antonio(Would be your username)/Documents/Android/SDK
Now, this part is completely optional.
I'm going to show you how to add your sdk/tools directory to your .bash_profile file so you won't have to navigate to the folder each time.
Download this so you'll be able to see your hidden files http://www.mediafire.com/?diimft1ninn Run it, check "Show Hidden Files" then click Restart finder. Now, navigate to your home folder (/Users/%UserName%/) and see if there's a .bash_profile already there. If not, create with textedit.
Now add this to the file: export PATH=${PATH}:/Path/Of/Your/Sdk/Tools/Folder
Mine is /Users/Antonio/Documents/Android/SDK/tools
Now do not save it as rich text. If yours is in rich text, click on "Format" in the menu bar, and click "make plain text". Now save it as .bash_profile and uncheck "if no extension is provided, use .txt".
Now you can go back to Ghost and uncheck "Show all hidden files" and restart finder again.
Now, for rooting.
First, go to Settings > Applications>Development, and make sure USB Debugging is checked on your phone.
1. Download Asroot2 (http://zenthought.org/tmp/asroot2) and move it to your SDK/tools directory
2. Navigate to your SDK/tools folder (cd ~/Documents/Android/SDK/tools for me)(~ replaces /User/%Username% if you didn't know)
3. Then type:
Code:
./adb push asroot2 /data/local/
./adb shell chmod 0755 /data/local/asroot2
./adb shell
/data/local/asroot2 /system/bin/sh
And you should get:
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pipe_inode_info layout
Opening: /proc/857/fd/3
SUCCESS: Enjoy the shell.
4. Then type:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4775 su
At this point you should have root access.
Now, for the recovery image (gives you extra options like backing up with Nandroid, partioning SD, etc.)
1. Download the recovery image from here: http://forum.xda-developers.com/showthread.php?t=596879
2. If you are still in adb shell from rooting type in exit until you are out. You should be in the directory where you extracted the recovery image. If not go there (You can put it in the SDK/Tools folder and nav there). Type in the following:
adb push recovery-RA-heroc-v1.5.1.img /sdcard/
You should get something like 868 KB/s (3352576 bytes in 3.767s)
3. Type in adb shell. If you see a dollar sign ($) then type in su and press enter. If it is a pound sign (#) you are good. Now type in:
Code:
flash_image recovery /sdcard/recovery-RA-heroc-v1.5.1.img
Once that is finished you are done. To reboot into recovery type in adb shell reboot recovery.
Told you most of the steps are the same. I just copied from other members and slightly modified it for Mac.
Now, if we could get a moderator to merge all these "How to Root" threads.

Ugh... Doesn't seem to work on Macbook. Phone shows "USB Connected", but, see below...
Code:
michael-macbook:tools mglipin$ ./adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
michael-macbook:tools mglipin$ ./adb push asroot2 /data/local
error: device not found
michael-macbook:tools mglipin$
What's up?

Start HTC Sync on your phone Dont worry that it pops up with an error abbout not finding a PC.
Then when you do adb devices you should see your phones serial number.
Alsomake sure USB Debugging Settings >Applications > Development is turned on

Thanks for this! I ended up getting mine rooted last night, but i had no idea about the recovery image thing. I gotta get that Nandroid going so i start removing some of the Sprint/HTC bloat!

ajones7279 said:
Root the CDMA Hero
3. Type in adb shell. If you see a dollar sign ($) then type in su and press enter. If it is a pound sign (#) you are good. Now type in:
flash_image recovery /sdcard/recovery-RA-heroc-v1.2.3.img
Click to expand...
Click to collapse
I get to this step....and in my terminal it keeps coming up with
Code:
mtd: re-read error at 0x00440000 (Out of memory)
mtd: write error at 0x00440000 (Out of memory)
mtd: re-read error at 0x00440000 (Out of memory)
mtd: skipping write block at 0x00440000
mtd: write error at 0x00460000 (Out of memory)
error writing recovery: No space left on device
Any ideas???

SS70Chevelle said:
I get to this step....and in my terminal it keeps coming up with
Code:
mtd: re-read error at 0x00440000 (Out of memory)
mtd: write error at 0x00440000 (Out of memory)
mtd: re-read error at 0x00440000 (Out of memory)
mtd: skipping write block at 0x00440000
mtd: write error at 0x00460000 (Out of memory)
error writing recovery: No space left on device
Any ideas???
Click to expand...
Click to collapse
Unless you replaced your SD card with something > 4Mb then the 3.4Mb recovery image won't fit on the stock 2Mb SD card.
I ordered a 16Mb card myself from Amazon.

I'm pretty sure this has nothing to do with MicroSD card space. I have a 4 gig with lots of space.

I have a 2GB stock card and was able to flash. I initially had the same "Out of memory" error and fixed it by cleaning up my SD card -- copying off extra pictures, videos, podcasts, etc. I also rebooted for good measure, probably not necessary.

Thanks for the guide have everything working! The link to the recovery ROM is hard to get into, it is hosted here as well for anyone else that has a problem.
http://www.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-heroc-v1.2.3.img
I was also getting the same error message. I didn't do anything to my SDcard, I just died a battery pull and tried again and everything worked.

Ooops, nvm
It is a 2Gb card and the recovery is 3.4Mb.

gilroykilroy said:
Unless you replaced your SD card with something > 4Mb then the 3.4Mb recovery image won't fit on the stock 2Mb SD card.
I ordered a 16Mb card myself from Amazon.
Click to expand...
Click to collapse
It cant be the size of the SD card, I have well over 4GB free on my 8GB card. Does anyone know how much device memory you must have free to flash the recovery image?

It was definitely the device memory. I deleted about 10 programs and rebooted. After that it had no error messages.

5tr4t4 said:
I have a 2GB stock card and was able to flash. I initially had the same "Out of memory" error and fixed it by cleaning up my SD card -- copying off extra pictures, videos, podcasts, etc. I also rebooted for good measure, probably not necessary.
Click to expand...
Click to collapse
mactruc said:
I was also getting the same error message. I didn't do anything to my SDcard, I just died a battery pull and tried again and everything worked.
Click to expand...
Click to collapse
Same Here, the soft reset worked like a charm Just started my nandroid backup. Thanks again gentlemen.

herzzreh said:
Ugh... Doesn't seem to work on Macbook. Phone shows "USB Connected", but, see below...
Code:
michael-macbook:tools mglipin$ ./adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
michael-macbook:tools mglipin$ ./adb push asroot2 /data/local
error: device not found
michael-macbook:tools mglipin$
What's up?
Click to expand...
Click to collapse
Go to Settings > Applications > Development and make sure USB Debugging is checked. It was a step I left out (assumed people knew rather).

ajones7279 said:
Go to Settings > Applications > Development and make sure USB Debugging is checked. It was a step I left out (assumed people knew rather).
Click to expand...
Click to collapse
I can vouch for this as well, had the same issue, and this took care of it.
Thanks for the Mac guide! Worked flawlessly.

so, i'm quite definitely (and obviously, as you'll see) a complete android noob. i apologize in advance.
i followed the guide to the letter, and ran into the "out of memory" error. so i cleared out a few photos from the sd card and rebooted the phone, then tried the last step again. i typed "adb shell reboot recovery" at the command line, and my phone started to reboot, but when it hit the first HTC logo the screen went completely black, the charging light went off, and i couldn't turn the phone back on at all. i ended up popping the battery out and back in, then booted it back up just fine. it booted normally, as it always had, so i'm assuming i did something wrong and it's not "rooted".
basically my question(s) is/are:
a) when i ran into the "out of memory" error and rebooted, should i have started the guide from the beginning again? or was i right to just continue on from the step i left off at?
b) if it worked and i did in fact succeed in rooting the phone, how can i find out for sure that it's rooted? is there a failsafe way to tell me that it worked?
c) if i did something else wrong along the way.. what should i do?

ersocia said:
basically my question(s) is/are:
a) when i ran into the "out of memory" error and rebooted, should i have started the guide from the beginning again? or was i right to just continue on from the step i left off at?
Click to expand...
Click to collapse
I had the same issue. After the soft reset you should have done this:
Code:
mtd: re-read error at 0x004c0000 (Out of memory)
mtd: skipping write block at 0x004c0000
96-26-56-112:tools brynehobbs$ ./adb shell
$ su
# flash_image recovery /sdcard/recovery-RA-heroc-v1.2.3.img
# reboot recovery
ersocia said:
b) if it worked and i did in fact succeed in rooting the phone, how can i find out for sure that it's rooted? is there a failsafe way to tell me that it worked?
Click to expand...
Click to collapse
yeah dl PicMe from the market, its free and requires root to run.
ersocia said:
c) if i did something else wrong along the way.. what should i do?
Click to expand...
Click to collapse
Figure out where you made the mistake and try again.

ersocia said:
c) if i did something else wrong along the way.. what should i do?
Click to expand...
Click to collapse
Just about everything is reversable...and the nandroid backup will save you from just about anything.
However, if even that fails and you find yourself feeling like this guy:
http://forum.xda-developers.com/showthread.php?t=581963
You can always return to stock with the exes from here:
http://forum.xda-developers.com/showthread.php?t=559622

Ran into the memory problem, but I have root now.
I didnt do anything to the sdcard or the device memory, all I did was hit phone+power+menu to do the reboot then did the commands to flash the recovery image and now I am running my nandroid backup.
I love the recovery menu also much better than the recovery menu on my rooted G1, but missing the recovery shell. Is there a way to get into the shell from the recovery menu or is adb the only way in.
edit: nevermind about the recovery shell just realized you cant have a software keyboard in the recovery shell

i am having a hard time rooting my sprint htc hero
the stuff that ajones7279 posted is not enough from me as i have only had a mac and android phone a few weeks and don't know very much
i would be grateful if some one could give me detailed info on how to root my hero on a mac
thank you

k0ush recovery for EVO

I'm gonna go ahead and leave this here:
http://www.droidaftermarket.com/koush/recoveries/recovery-clockwork-1.8.1.5-supersonic.img
This recovery was prepared by Koush, who is most well-known as the maintainer of the DROID branch of CyanogenMod. I don't have access to the root exploit, so I can't test it. (I get fastboot remote: not allowed).

I have no idea if this works, as I don't have an Evo. And since the root has not been released, I don't have any testers. Once the root is released, I'll fix this, should any problems arise. But, I given the stock recovery image, I was able to create this. It ought to work.

theillustratedlife said:
I'm gonna go ahead and leave this here:
http://www.droidaftermarket.com/koush/recoveries/recovery-clockwork-1.8.1.5-supersonic.img
This recovery was prepared by K0ush, who is most well-known as the maintainer of the DROID branch of CyanogenMod. I don't have access to the root exploit, so I can't test it. (I get fastboot remote: not allowed).
Click to expand...
Click to collapse
I have tried getting root as well and get the same error. Thanx for the post.

Koush said:
I have no idea if this works, as I don't have an Evo. And since the root has not been released, I don't have any testers. Once the root is released, I'll fix this, should any problems arise. But, I given the stock recovery image, I was able to create this. It ought to work.
Click to expand...
Click to collapse
koush do you have an Evo? I loved your CyanogenMod port for the Droid!
Sent from my HTC Evo 4G using Tapatalk

I have no idea if this works, as I don't have an Evo. And since the root has not been released, I don't have any testers. Once the root is released, I
Click to expand...
Click to collapse
koush do you have an Evo? I loved your CyanogenMod port for the Droid!
Sent from my HTC Evo 4G using Tapatalk
Click to expand...
Click to collapse
Wow, you quoted him saying he doesn't have an EVO and you still asked if he had an EVO... no, he doesn't.
Sent from my Droid using Tapatalk

HTC6800 said:
Wow, you quoted him saying he doesn't have an EVO and you still asked if he had an EVO... no, he doesn't.
Sent from my Droid using Tapatalk
Click to expand...
Click to collapse
LOL my bad. how embarrassing
Sent from my HTC Evo 4G using Tapatalk

Nice!
NOT sent from an Android device using Tapatalk...

Deviation said:
Nice!
NOT sent from an Android device using Tapatalk...
Click to expand...
Click to collapse
I just spit on myself I laughed so hard at this, thanks

lol thats some funny ****!

Let me know if this recovery works!

Ah, nevermind. I see that the recovery partition is still not writable on the evo. Same half-ish root as the Desire.

Koush said:
Ah, nevermind. I see that the recovery partition is still not writable on the evo. Same half-ish root as the Desire.
Click to expand...
Click to collapse
Indeed. But you can use the script/push way that desire/etc use, and it should work fine.

How do we go about applying this IMG?

Can you do fastboot boot recovery.img, or is fastboot still locked out?

maejrep said:
Indeed. But you can use the script/push way that desire/etc use, and it should work fine.
Click to expand...
Click to collapse
as we're throwing out ideas here and i dont get my EVO until tomorrow, i see flash_image pushed over through the EVO-recovery.zip maejrep and toast posted, would that work here?

So I loaded up the root method that just got put up and pushed the recovery image to /system to try to flash it with flash_image but that failed, there is no write access to recovery.
Code:
# flash_image recovery recovery.img
flash_image recovery recovery.img
mtd: erase failure at 0x00000000 (I/O error)
mtd: erase failure at 0x00000000 (I/O error)
mtd: skipping write block at 0x00000000
[...]
mtd: erase failure at 0x004e0000 (I/O error)
mtd: erase failure at 0x004e0000 (I/O error)
mtd: skipping write block at 0x004e0000
error writing recovery: No space left on device

DDRBoxman said:
So I loaded up the root method that just got put up and pushed the recovery image to /system to try to flash it with flash_image but that failed, there is no write access to recovery.
Code:
# flash_image recovery recovery.img
flash_image recovery recovery.img
mtd: erase failure at 0x00000000 (I/O error)
mtd: erase failure at 0x00000000 (I/O error)
mtd: skipping write block at 0x00000000
[...]
mtd: erase failure at 0x004e0000 (I/O error)
mtd: erase failure at 0x004e0000 (I/O error)
mtd: skipping write block at 0x004e0000
error writing recovery: No space left on device
Click to expand...
Click to collapse
thats the error they report indicating NAND protection is still active. guess this confirms, as gathered from the other threads, seems NAND protection only unlocks /system with the current userdebug RUU we have when booted into recovery mode. means no write access to /recovery yet.
thanks for trying!
would it be worth trying to do the exact same flash_image of recovery from normal android mode? probably wont work either...

I put superuser 2.1 on it and tried to flash from adb while booted into android and su wont elevate me.

DDRBoxman said:
I put superuser 2.1 on it and tried to flash from adb while booted into android and su wont elevate me.
Click to expand...
Click to collapse
not positive how superuser interacts with all this newly modified system so ill throw out some ideas, hopefully something works.
try flash_image from connectbot on the phone and see if su elevates?
try removing superuser temporarily?

he probably needs to chmod 4755 su before using su.

Can't mount /sdcard

Hello Guys,
I am having a serious problem, I can not acces my SDCard with CWM, it keeps saying "Can't mount /sdcard" I really don't know what to do, I installed the Xperience Kernel and now nothing is working.
Adb Sideload is not working too when flashing the stock ROM, it keeps saying: "* failed to write data 'protocol fault (no status)' *"
I really have no idea what to do now.
Thanks
Fliwatt

Fliwatt said:
Hello Guys,
I am having a serious problem, I can not acces my SDCard with CWM, it keeps saying "Can't mount /sdcard" I really don't know what to do, I installed the Xperience Kernel and now nothing is working.
Adb Sideload is not working too when flashing the stock ROM, it keeps saying: "* failed to write data 'protocol fault (no status)' *"
I really have no idea what to do now.
Thanks
Fliwatt
Click to expand...
Click to collapse
Try this -> http://forum.xda-developers.com/showthread.php?t=1011355
Or this -> http://spafdroid.wordpress.com/2014/06/29/adb-sideload-failed-to-write-data-protocol-fault/
Power of google

Thank you, all of these did not work but I fixed it finally by installing a new recovery:
http://forum.xda-developers.com/showthread.php?t=2563599
Not the touch one.

XT1032 Somewhat bricked?

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.