How to fix I/O errors in CWM and TWRP? - T-Mobile Samsung Galaxy Note II

So I've been doing a lot of stuff with recoveries, and to make a long story short, I can't get rid of a few messages in both TWRP and CWM (installed both to try and fix) no matter what I do. I've tried factory reset, deleting system, cache, dalvik, battery, fix permissions, everything. The E: errors just stay there.
I've heard you need to do a full fastboot wipe for your phone and delete the entire internal SD card, before reinstalling everything. I herad you have to install software on your phone and stuff. I have no idea how to do this for Galaxy Note II, so could someone provide me a link to all the downloads, and all the steps I need to do? I know I'm asking for a lot, but I really just want my phone to work again. Thank you.
EDIT: I did a clean wipe of the internal SD card and all is fixed! Running stock now rooted, and it's working great. So problem solved, and I did backup my data first.

Related

[Q] Need some serious help =/

I was in the middle of installing cm7 r2 and I managed to drop my phone and it got shut off. Now when I turn it on it won't get past the first screen, then it resets and brings me to clockworkmod recovery. So I hope there's a way to fix this since I have access to that, but I can't find anything cause really, I don't know what to look for. Any help would be grealy appreciated.
Kaymor said:
I was in the middle of installing cm7 r2 and I managed to drop my phone and it got shut off. Now when I turn it on it won't get past the first screen, then it resets and brings me to clockworkmod recovery. So I hope there's a way to fix this since I have access to that, but I can't find anything cause really, I don't know what to look for. Any help would be grealy appreciated.
Click to expand...
Click to collapse
If you can access the bootloader and recovery, then you're most likely fine, and have nothing to worry about. Unless, of course, something was damaged internally (hardware wise) when you dropped it. Do you have any nandroid backups that you made with clockwork recovery? If you do, all you should need to do is restore that backup. I like to do a full wipe (data/factory reset, cache, dalvik cache) before restoring a backup. If you don't have any nandroid backups, then just use clockwork recovery to install the rom. Assuming CM7 rc2 is already on your sd card ( if it's not, just put CM7 and Gapps on your sd card ), go into clockwork recovery, and select wipe. Wipe data/factory reset, wipe cache, wipe dalvik cache (under advanced). Go to 'install zip from sd card', find the CM7 rc2 zip. Select it, and let it flash. Once it completes, go back to install frm sd card, and flash the Gapps. Once that's done, reboot. That *should* get you going again. Good luck.
i would try wipe caches, restoring my back up and make sure everything works, then star the process to install cm7 all over again
k2buckley said:
If you can access the bootloader and recovery, then you're most likely fine, and have nothing to worry about. Unless, of course, something was damaged internally (hardware wise) when you dropped it. Do you have any nandroid backups that you made with clockwork recovery? If you do, all you should need to do is restore that backup. I like to do a full wipe (data/factory reset, cache, dalvik cache) before restoring a backup. If you don't have any nandroid backups, then just use clockwork recovery to install the rom. Assuming CM7 rc2 is already on your sd card ( if it's not, just put CM7 and Gapps on your sd card ), go into clockwork recovery, and select wipe. Wipe data/factory reset, wipe cache, wipe dalvik cache (under advanced). Go to 'install zip from sd card', find the CM7 rc2 zip. Select it, and let it flash. Once it completes, go back to install frm sd card, and flash the Gapps. Once that's done, reboot. That *should* get you going again. Good luck.
Click to expand...
Click to collapse
I'm pretty sure no hardware was damaged. Sadly I didn't care enough about the stuff I'd lose to make a back up. I did assume I'd be able to put the rom on my sd card but I can't find a single download for cm7...but thanls for the help, I'm glad to know my phone can be saved , now off to find this file...
Found it, will update if phone will work
Kaymor said:
I'm pretty sure no hardware was damaged. Sadly I didn't care enough about the stuff I'd lose to make a back up. I did assume I'd be able to put the rom on my sd card but I can't find a single download for cm7...but thanls for the help, I'm glad to know my phone can be saved , now off to find this file...
Click to expand...
Click to collapse
Look here, gapps are on the bottom of the page, CM7 will be somewhere in the middle
http://wiki.cyanogenmod.com/index.php?title=Latest_Version#HTC_Evo_4G
EDIT: you seem to have found it
Kaymor said:
I'm pretty sure no hardware was damaged. Sadly I didn't care enough about the stuff I'd lose to make a back up. I did assume I'd be able to put the rom on my sd card but I can't find a single download for cm7...but thanls for the help, I'm glad to know my phone can be saved , now off to find this file...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=956187
All the downloads you need should be in the first few posts of this thread. Don't forget about gapps, otherwise you won't have google apps. And once you get everything up and running and stable, I suggest creating a nandroid backup! It only takes about 5-10 minutes, and can save you some real hassles in certain situations. And, since you can't boot into the ROM, you have a couple options to transfer the files to your sd card. 1) Take your sd card out of the phone, and put it in a card reader/adapter, and into your computer. 2) Put it in a different phone to transfer the files 3) the easiest way, is while you're in clockwork recovery, there should be a setting called 'usb ms togge' or something similar to that (i use AR recovery, and that's waht it's called in Ar), and that should mount your sd as a disk drive to your computer. Good luck.
Edit: I took too long, you found it already! Nice. Let us know if it all works out, or if you need more assistance.
Hooray! Phone works again!!! Thanks everyone so much for the quick and helpful replies, I'm impressed by the such friendly community!
Kaymor said:
Hooray! Phone works again!!! Thanks everyone so much for the quick and helpful replies, I'm impressed by the such friendly community!
Click to expand...
Click to collapse
You're welcome! Glad you're back up and running again! And yes, XDA is a great community, and houses many knowledgeable, friendly, and very smart people. Welcome aboard.

[Q] CM7 RC1 won't restore

so i have been using CM7 RC1 w/ stock kernel for a while now, without any issues. i was reading up and wanted to try the new incredikernel though, for the governor rather than using setcpu/juice defender for increased battery life.
so i did a titanium backup, then in Clockwork did a full backup before i started messing with anything. i then mounted to computer to put the kernel on the SD card. i did this, but was confused where to actually put the .zip file so that CW would see it. SD card or internal memory? i've had this issue before.
anyway, i didn't find the .zip when i booted into recovery, so i went to re-mount to USB to move it over to the other directory, and everything seized up on me. trying to mount USB basically froze my phone. re-booting did not fix, when i try to go into CM settings or try to mount USB same freezing would happen.
OK fine, i just did a nandroid backup so i figured it wasn't a big deal since i haven't actually made any changes yet and so i restored. then it would not boot. got stuck at the CM7 bootloader. ****. so i tried an earlier restore point, from a few months ago. that worked (also CM7-RC1 when i first put it on). i didn't wipe cache/dalvik when i tried the first time, so i wiped now and then tried to restore the most recent backup again. still, no luck.
so i've been living with the older restore trying to get everything how it was before. another note, i had installed a battery meter (RC1 did not come with one), and when trying to flash this, got stuck at the same bootloader screen again. another thing to note is that i have been updating CW to the latest version when it is available, but all versions are 3.xx. the latest i think i went from 3.0.0.5 to 3.0.0.8. just trying to include as much info as possible here...
any ideas? it's frustrating because i haven't actually been installing anything new. at this point i just want my phone the way it was, i.e. getting the latest restore point to work. it won't, but older restore versions will work. did CW mess up the backup, is it corrupt? is this a CM7 issue or CW? help please!
if this is in the wrong forum, apologies, it wouldn't let me post in the dev thread due to lack of posts.
Did you do a complete wipe before trying to restore your backups? In recovery, wipe data/factory reset, wipe cache, wipe dalvik cache, format boot, system, data and cache.
Sent from my ADR6300 using XDA App
k_nivesout said:
Did you do a complete wipe before trying to restore your backups? In recovery, wipe data/factory reset, wipe cache, wipe dalvik cache, format boot, system, data and cache.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
i did not do that before. i just tried though, and same result. stuck in CM7 boot loop.
wtf happened to my backup!
That happened to me once. Try this. Save everything on your sd card to your computer. Reformat card. Then put just the nandroid back on card. It might help.
Yeah sounds like it may be an issue with the SD card or your backup..
Sent from my ADR6300 using XDA App

[Q] In need of some assistance.

So i have flashed for awhile and never have encountered this problem. i was on lbj7 i went back to stock. did Ota upgrade to 4.1.2, rerooted flashed another rom and now all it does is forceclose. How do i clean the system completly so i can reflash a fresh clean install. I normally wipe Delvik+cache+ factory what else can i include to insure i have a 100% clean flash?. Any and all help is appreciated thanks!
Wipe internal storage will erase anything on the internal just as it states. What ROM are you trying to flash? Also what recovery do you have and is it up to date. If you want the ultimate clean install I do this, make sure the and if you need gasps or any other file is on the external card
Wipe data, cache, dalvick, system this removes the ROM, internal and maybe even format data. Flash ROM wipe cache and dalvick and if you need to gasps the wipe cache and dalvick the boot. But make sure your recovery is up to date, I use twrp which is on 2.4.4 right now. And you have the correct gasps if needed. Good luck.
Sent from my SPH-L710 using Tapatalk 2
Hey Thanks Giantay.. I am trying to reflash Goodness 9.0.4. Its forceclosing Touchwiz and Apex and all the other.. I seem to have a Wakelock aswell Media is stuck at 40% Battery Useage. I use Cwm. Maybe i should switch to Twrp..
thaset said:
Hey Thanks Giantay.. I am trying to reflash Goodness 9.0.4. Its forceclosing Touchwiz and Apex and all the other.. I seem to have a Wakelock aswell Media is stuck at 40% Battery Useage. I use Cwm. Maybe i should switch to Twrp..
Click to expand...
Click to collapse
To install TWRP the easiest way just download Goomanager from the Play Store here https://play.google.com/store/apps/...anager&feature=nav_result#?t=W251bGwsMSwyLDNd open it go to settings and select Install OpenRecoveryScript, This will download and install TWRP's newest recovery. You could also check the md5sum to see if it's a good download. Sometimes the files that you download are corrupted but I have never had it happen, and I have flashed endless amounts of ROMs on different phones, but it happens people say. I am unfamiliar with that specific ROM but try searching in the thread for it to see if anyone else has had similar experiences and have a way to fix it. Searching is your friend, search and read a lot will ussually solve your problem, and if you don't turn up anything don't be afraid to ask a question instead of doing something that might be unsafe or worries you.
I did as u suggested and just tried re flashing using Twrp. Awaiting Results as first boot aproaches. Thanks again for the helping hand.
Just a heads up. Try and hit the thanks button on these forums if people help you in any way. I don't really care about it but it helps some people especially devs and what not.

[Q] "gapps stopped" loop after CWM restore

Hi,
I was frustrated with the delay in T-Mobile's release of KitKat for the GSIII, so I decided to root my phone last night in order to try flashing CM11 on it. Rooted my phone with Towelroot, installed ROM Manager and CWM, and created backups on Kies and through CWM. Then I proceeded to do data wipe/factory reset, cache wipe, and /system format. Tried to flash CM11, but got a status 7 error.
I freaked out, so I decided to restore everything from the backup I'd created. Restoration seemed like a success, but now I get the error "Unfortunately, the process com.google.process.gapps has stopped" in an endless loop, and it prevents me and any apps from doing anything. I tried clearing dalvik cache in recovery, but the problem still persists. Read on a few threads that I should flash to stock firmware via Odin, but I'm currently on a macbook, so I can't install it.
tl;dr - Prepped to flash CM11, reached status 7 error, got freaked out, and did restore via CWM, only to get infinite loop of gapp crashes. No access to Odin or PC. Not hard bricked or soft bricked, but essentially useless phone. Help? );
if you can still get to recovery, download latest gapps and flash that
Did you factory reset before or after you restored your back up?
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Try to factory reset again
vvnn said:
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Click to expand...
Click to collapse
If I'm not mistaken, there is some device ID that will change each time you flash a new rom. It may be something to do with this ID not matching the one in the restored data. Purely a guess but seems logical to me.
Anyway, factory resetting will most likely solve this for you, but I wanted to add that except in certain circumstances, you shouldn't ever manually format /system. (and one format on any partition is sufficient. There shouldn't be any need to format multiple times). If you format /system, you are wiping the O/S off of your device. Then what happens if you have problems flashing a rom, or firmware? I've seen it happen many times and I often end up spending a couple of days working with them just to get the thing to boot up again!
When you flash a rom, the first thing it does is format /system. So there is just no need to do this manually. At least if the rom fails to flash (such as failing the assert checks), youll still have something to boot into. Hope this helps in the future!
I have had the exact same issue. I have a Samsung note 2 N7105. I rooted made a backup in CWM and flashed ditto n3/s5 rom made another backup in CWM. No issues. Got a bit cocky seen as it was my first time doing anything like that. My next adventure was to try a custom kernel (agni). This didn't go so well, so I tried to do a restorw to my working backup of ditto n3/s5 rom through CMW. restore went smoothly and the phone booted. once I opened the lock screen I got the gapps error as described. I had to do a factory reset to get the phone working and then re-flashed ditto n3/s3. I've since flashed other roms and when ever I try to do a restore, I get the issue described. Note I am using the latest CWM. I putting off flashing and trying any other ROMs because of this issue. I do love dn3/s5 but id love to try others. Anyone can help it would be appreciate.

Nandroid Restore Errors - com.google.process.gapps has Stopped

Hi Everyone,
Trying to see if there is a simple fix for this without having to wipe the device to factory.
Working with 4.4.4 on an insurance replacement (old power button went bad). Ran a Nandroid backup on my faulty device using CWM, and when restoring to the new device (after flashing the 4.4.4 deodexed rom, permissive kernel and modems) I am getting a looping error on process.gapps and Google Play services.
Looks like something got hosed post-restore and need some assistance wrangling this without having to do a hard reset.
I've tried:
- Clearing Cache
- Clearing Dalvik Cache
- Clearing cache on Google Play Services
Unfortunately, none of these options have been successful. Does anyone have a hammer and nails approach I can use here to stabilize the device? I have no problem with reinstalling Google Play Services or GApps, but in this state the device is challenging to navigate (popup after popup).
Thank you in advance for your feedback.
Did you wipe everything and then restore your nandroid?
serio22 said:
Did you wipe everything and then restore your nandroid?
Click to expand...
Click to collapse
Yes, wiped cache, dalvik cache and data/system.
Worked around CWM by installing TWRP and converting a spare MicroSD card to Fat32. From there was able to run a TWRP System/Data backup and image the new phone.
I've experienced this issue before with CWM, so assuming it's a defect in the System and or Data backup process.
Glad to be back up.
oblivion0 said:
Worked around CWM by installing TWRP and converting a spare MicroSD card to Fat32. From there was able to run a TWRP System/Data backup and image the new phone.
I've experienced this issue before with CWM, so assuming it's a defect in the System and or Data backup process.
Glad to be back up.
Click to expand...
Click to collapse
Good to know, thanks for the update

Categories

Resources