I recently reflashed Checkrom 4 to get rid of a theme, then flashed a kernel cleaning script, then the latest Speedmod, then JKay 13.4.1.
Now every time I reboot I get this error:
error reading data from the hardware interface
Can anyone tell me what is the problem here please?
Many thanks.
Remember if everything fails to fix your problem. You have 1 solution left.
Start over:
1. Backup your applications via Titanium Backup
2. Wipe everything in recovery.
3. Flash desired rom and kernel.
Have a good day.
Try flashing a clean ROM through ODIN first and then reflash it with the ROM you want.
Related
I don't know exactly what caused the issue. Maybe some recent apps since that was all that I had installed. I was running the latest AOKP ICS 4-28-12 and Siyah 3.1x. I forget the exact kernal number but it wasn't the version that I read about phone bricking (R6?).
So I wake up this morning and unlock my screen and there are popups for everything force closing. Not just foreground running apps but everything including background running apps. Every time an app autorestarts in the background the force close error msg pops up again. It was running fine just 6 hours prior since I was using it before bed.
Reboot. Same issue. CMW Recovery. Wipe cache/dalvik. Reflash AOKP and GApps. Reboot. Same force closing issue. WTF. Attach USB to comp and try to move a different ROM to my Internal SD but no dice. Comp isnt recognizing phone now. [email protected]#K! Reboot into download mode. All the ROMS I downloaded are ZIP format instead of TAR format. So this time my dumb self uses Odin to reflash the TAR file I used to root my phone. After this I realize "that TAR doesn't have a ROM attached to it."
So now I can only boot into download mode. Can't load CMW. Sadly I had to leave for work and I'm without my phone until I get home at midnight. I FEEL SO DISCONNECTED! ='(
Will a simple file conversion program be sufficient to convert ZIP to TAR so I can use ODIN to flash them later? Or will I have to follow the unbrick instructions to return to stock and then start over? And after reading about that one version of Siyah bricking phones I think I'm going to leave the NEAK kernal that comes with AOKP.
Thanks for your assistance!
No, you can't build a tar from a zip.
I don't and have never used aokp or cm9 or miui, but in my experience, when you start getting massive force closes, and if a fix permissions in recovery doesn't fix it, then you're best off starting over from scratch. If you have a working nandroid backup, use that. Otherwise, flash back to stock, wipe data/factory reset, and reinstall your rom from scratch.
There are plenty of tar and one-click downloaders available. See links in my signature.
I found this on the i9100 forums, instructive. Instead of installing a stock samsung firmware and kernel, just download a rooted package (maybe go back to Gingerbread for i777) then go from there.
http://forum.xda-developers.com/showthread.php?t=1457458
I'm interested to know how this recovery works for you, keep us posted! Best luck!
Any idea what would randomly cause the issue of mass force closures so I can prevent this from occuring again?
Did you do a Full Wipe when you first installed AOKP? I have ran into issues before with Rom Control by just wiping cache and dalvik and under the OP of AOKP Task even states coming from aokp or cm9 you Should be good but more likely than not, I would do a complete wipe *Factory Reset under CWM*. And when you restore your data with TiBu just restore missing apps and their data. Do not restore system data as that will be a major cause of mass FC... So first things first, I would use Odin to go back to UCKH7 *hopefully with CWM and Root* and than go back to Aokp since in my opinion is the best rom for our phones now.
HTH,
Charlie
dmnall said:
Did you do a Full Wipe when you first installed AOKP? I have ran into issues before with Rom Control by just wiping cache and dalvik and under the OP of AOKP Task even states coming from aokp or cm9 you Should be good but more likely than not, I would do a complete wipe *Factory Reset under CWM*. And when you restore your data with TiBu just restore missing apps and their data. Do not restore system data as that will be a major cause of mass FC... So first things first, I would use Odin to go back to UCKH7 *hopefully with CWM and Root* and than go back to Aokp since in my opinion is the best rom for our phones now.
HTH,
Charlie
Click to expand...
Click to collapse
I didn't do a factory wipe. I'm thinking I'll just do a factory wipe for any new rom installs. It's a little more work but if it helps prevent this sort of error I'll do it. And after reading about the bricking with that one version of Siyah I'm going to wait a couple weeks before any new installs to make sure other people have tested it first.
creepyncrawly said:
No, you can't build a tar from a zip.
I don't and have never used aokp or cm9 or miui, but in my experience, when you start getting massive force closes, and if a fix permissions in recovery doesn't fix it, then you're best off starting over from scratch. If you have a working nandroid backup, use that. Otherwise, flash back to stock, wipe data/factory reset, and reinstall your rom from scratch.
There are plenty of tar and one-click downloaders available. See links in my signature.
Click to expand...
Click to collapse
Well the first attempt didnt work using kernel + rooted UCKH7. Odin did everything it was supposed to but the phone locks at the initial Galaxy S II I-9100 ! screen. =(
Second attempt using I777_UCKH7_OCD_Root_No_BL and I'm able to get past the Galaxy S II I-9100 screen and the original AT&T boot animation shows but after the boot animation it just continuously reboots. ='(
Third attempt I tried Kernel + cache + rooted UCKK6 and after the reboot it actually rebooted into recovery mode. I thought that was a good sign so I reboot the phone normally and same issue as above. I try to reboot into recovery mode (Vol + - and pwr) again but it doesn't come up now. ='(
Forth attempt I tried Kernel + cache + rooted UCKK6 again. It reboots into recovery mode and I select the Factory Wipe option and reboot. There's a long delay after the AT&T boot animation and finally my phone starts up as if it was stock.
What a freakin nightmare! I was so worried my phone was a goner. None of the other ROMs I tried gave the option of booting into recovery mode which would have saved me so much time. Only the stock one did. The factory wipe was the key. So I'm definitely saving that file for safe keeping.
Thank you all for your suggestions and assistance. It's much appreciated.
This entire thread could have been avoided. By wiping completely. What is a complete wipe? Well, its the /system , /cache, /data, and /dalvik partition. Each of which are easily wiped in cwm in under 30 seconds. Flashing the kernel cleaning script doesn't hurt. Keep in mind these are your phones people it wouldn't hurt to do some research.
Sent from my SGH-I777 using Tapatalk 2
I'm running TWRP v2.3.0.1 and I've been having a lot of trouble the past few days trying to flash roms. I was on a stock rooted evo lte with s-on two days ago.
I decided to try out the cm 10 and used flash image gui to flash the boot and then was on cm 10. Decided that I wanted a more stable rom (gps wasn't working) So i went back and restored my original backup of my stock rooted evo. However, the wifi is not working (all it says is wifi - error, won't turn on). So i did a little research and thought maybe something with switching back and forth between kernels went wrong. I'll try to flash a sense based rom the same way i did cm 10. At this point i try to make another backup just incase and its going through everything in twrp and in the end it says backup failed. So i figure well the orignal backup I have is fine and continue
So i open meanrom up in flash image gui it does its thing (clear dalvik, cache). Reboot into recovery go to install meanrom and get the following:
"-mean rom logo-
Formatting and mounting partition...
e:error in /sdcard/meanrom-ics-v48-jewel-ltevo.zip
(status 1)
error flashing zip '/sdcard/meanrom-ics-v48-jewel-ltevo.zip'
updating partition details"
and twrp says FAILED, at this point i'm thinking maybe a bad download i'll try another rom/download
So at this point i restore my system and once again wifi is not working and try the same using freshrom. flash image gui, clear cache, etc. Reboot into recovery and gives me the same error and says failed.
So now i'm stuck on a stock rom backup that worked fine when i orginally backed it up but now wifi has an error? doesn't make any sense to me and i'm not sure why i'm unable to flash and roms or create new backups
Try flashing TWRP 2.2.2.0 in fastboot
i was able to fix wifi using vel7wil advice in this thread http://forum.xda-developers.com/showthread.php?t=1900759&highlight=wifi+error so for now everything is working on my backup. I'll see if i'm still having issues flashing roms now.
Hello, I'm having a bit of an issue here I can't install a ROM after trying CM10.1.
I was using CM10, up until awhile, when I deiced to give CM 10.1 a try (Alpha build I'm aware of the risks).
I have installed CM10.1 using Rom Manager Premium. The installation progress went smooth without any errors, before installing I've made a backup of my current ROM.
Once CM10.1 finished optimizing application it started giving errors, that it can't load up Setup Wizard stopped from working, I have rebooted into CMW, wiped Dalvik cache and user data, I have booted up again, and was still was getting the same error, so I decided to restore my previous ROM.
But when I have booted up into CWM, I have discovered that the backup I made isn't there, not on the Internal memory and not on the SD card.
The issue I'm having is that I can't instal CM10 back, when ever I try to install CM10 ROM ZIP using CMW from external SD I get an error (Status 7)
Is there any ODIN CM10 installation route?
Thank you!
Update 1:
I have manged to flash The Official Rom, But it can't boot up, it seems like it's stock on the animation screen, the animation moves, but doesn't boot up. What might be the issue?
Update 2:
Solved the problem by wiping use data, and resting it to factory settings.
Update 3:
Got it fixed, everything is running like it used to be. Shame that I lost all my personal DATA, specially the DICM folder :/
Step-by-step what I did:
1. Flashed boot.img of cm11<Kitkat 4.4.4>/zip and did a backup of stock ICS(last updated by Sony)(BackUp1) using CWM, I see version 6.0.5.0.
a)While backing-up, It said, coundn't create sd.ext.img, and I ignored it. <not sure of exact message >
2) Flashed cm11-<Kitkat 4.4.4>.zip. After reboot it works pretty well ,
a) but drains battery faster compared to ICS, want to go back to ICS(BackUp1),
3) Took a backup again using CWM (BackUp2) and rebooted phone to CWM-Recovery and selected BackUp1 to restore.
a)While restoring it says ' sd-ext.img not found...' and 'Restore completed...' and rebooted. I didn't see any life apart from screen glowing greyish. No response with power or other buttons.
4) Removed battery and tried restoring BackUp2, It said the same thing that 'sd-ext.img not found.. Skipping restore of sd-ext.img.... Restore completed....'
After rebooting with BackUp2 it works fine.
I tried 2-3 times, clearing caches and formatting system,data,cache to get BackUp1... no luck...
Questions:
1. How can I get the BackUp1 working?
A: restored after flashing vengeance kernel.
2. Is it with kernel, do I need to flash ICS kernel and restore BackUp1?
A: yes
3. Did CWM was installed through boot.img, part of CM11<kitkat version 4.4.4>.zip, I flashed to phone ?
A:yes
recently i have rooted my samsung s2 plus gt-I1901p, then installed supersu and rom manager....I wanted to flash custom rom. So first I done recovery clock mode 6.0.4.5 or something not sure than I done a backup and than I download pac man custom rom......and when I try to falsh it with rom manager did not work.....I try it manualy 3-4 times and also did not work... every time was some kind of error and after each time I done reboot system now and everything was normal...only after last boot somehow it could not reboot....it was md5 data error...I try it several times and finaly I did advanced recovery and start from data and aggain error......so I just turn it off and on and my phone was fine....but I did not have some of my app......viber, skype, rom manager....I try it to install rom manager aggain and than I had an errod code -24...what should I do know.
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
For more questions or to have full access please register an account on XDA forum.
Stand by
Good luck
XDA Visitor said:
recently i have rooted my samsung s2 plus gt-I1901p, then installed supersu and rom manager....I wanted to flash custom rom. So first I done recovery clock mode 6.0.4.5 or something not sure than I done a backup and than I download pac man custom rom......and when I try to falsh it with rom manager did not work.....I try it manualy 3-4 times and also did not work... every time was some kind of error and after each time I done reboot system now and everything was normal...only after last boot somehow it could not reboot....it was md5 data error...I try it several times and finaly I did advanced recovery and start from data and aggain error......so I just turn it off and on and my phone was fine....but I did not have some of my app......viber, skype, rom manager....I try it to install rom manager aggain and than I had an errod code -24...what should I do know.
Click to expand...
Click to collapse
This could be caused by the corruption of google play store files. You should reinstall rom and install the proper gapps file. Make sure to wipe system, cache, data and dalvik cache before reinstalling any rom. md5 errors are caused by the corruption of flashable cwm zip files. Try a different rom and this should fix your problems.
error-24
gsstudios said:
This could be caused by the corruption of google play store files. You should reinstall rom and install the proper gapps file. Make sure to wipe system, cache, data and dalvik cache before reinstalling any rom. md5 errors are caused by the corruption of flashable cwm zip files. Try a different rom and this should fix your problems.
Click to expand...
Click to collapse
thank you very much......I allready installed new ROM Cyanogenmod 11 and full GAPPS 4.4.2 with Rom Manager and everything is ok now.:good: