[Q] SCH-i905 - Can't Factory Reset & Can't Flash - Galaxy Tab 10.1 Q&A, Help & Troubleshooting

Hi Guys
I am new to playing around with android but not to electronics. I have a Verizon Samsung Galaxy Tab 10.1 16gb (SCH-i905) with current 4g service.
Here is the problem I am having:
It started yesterday, I was browsing the web and the tablet froze and then rebooted. After the reboot programs randomly freeze and crash, if I reboot anything I have downloaded is gone and anything I deleted is back and I can't install or remove apps. I figured I had something corrupted and a factory wipe would fix it. Unfortunately when I perform a factory wipe from the menus or through Android recovery nothing happens. The tablet boots up like nothing was erased. Still has all my accounts, security pin, apps, and so on.
So after that I figured I would flash the tablet, I found the thread here in the development forum with the stock 3.2 image to load through ODIN. I downloaded everything, followed the instructions. ODIN says the flash was successful but when the tablet reboots it still has all my info and is running 4.0.4. I have tried this multiple times. I have tried loading CWM with ODIN but it will not stick.
Any thoughts? If you need more information I will get it, I am just stuck and can't find anything that helps me with this problem!
Thanks for your help!!!

If you want cwm to load after you install it using odin, then you must immediately boot the tablet into recovery without letting it run normally. During the normal boot process, CWM is deleted and the stock recovery is restored. Therefore once Odin finishes installing CWM, hold the volume up button and once you get to the recovery mode you will be running CWM instead of the stock recovery module.
Regards,
Michael

Yes, I did read that in the multiple thread about installing CWM and have gone into recovery directly after ODIN reboots the tablet, however it is still only the stock recovery app.
Any ideas why the factory reset / data wipe won't work?

So after several more hours working on this problem I think I have come across the root cause. I believe that my internal storage has corrupted and is now only mounting in Read-Only mode. From everything I can find online, without having root access previously, this is a no go for fix it yourself.
In case anybody happens on this post down the road, I have been unable to find a resolution and it would appear I must sent the unit back to Samsung for repair.

Mixinitup4Christ said:
So after several more hours working on this problem I think I have come across the root cause. I believe that my internal storage has corrupted and is now only mounting in Read-Only mode. From everything I can find online, without having root access previously, this is a no go for fix it yourself.
In case anybody happens on this post down the road, I have been unable to find a resolution and it would appear I must sent the unit back to Samsung for repair.
Click to expand...
Click to collapse
factory reset through the stock recovery should be able to get you out of it (RO filesystem).

pershoot said:
factory reset through the stock recovery should be able to get you out of it (RO filesystem).
Click to expand...
Click to collapse
I guess that blows my theory out of the water. I can't make heads or tails with this. No matter what I do, Menu Factory Reset, Recovery Wipe/Reset, ODIN Flash Stock EG01 firmware, ODIN flash CWM Recovery as soon as this device reboots I am right back where I started....... GAH!!!
Thanks for letting me know I'm probably wrong.

Mixinitup4Christ said:
I guess that blows my theory out of the water. I can't make heads or tails with this. No matter what I do, Menu Factory Reset, Recovery Wipe/Reset, ODIN Flash Stock EG01 firmware, ODIN flash CWM Recovery as soon as this device reboots I am right back where I started....... GAH!!!
Thanks for letting me know I'm probably wrong.
Click to expand...
Click to collapse
it has to be factory reset through the stock recovery (it will format /data), not through CWM.

rozeins gone
pershoot said:
it has to be factory reset through the stock recovery (it will format /data), not through CWM.
Click to expand...
Click to collapse
Yup, done that multiple times. I'll take video of it if you want, Factory Reset in stock recovery has no effect.

Mixinitup4Christ said:
Yup, done that multiple times. I'll take video of it if you want, Factory Reset in stock recovery has no effect.
Click to expand...
Click to collapse
odin flash CWM (you can use 6.0.2.8 in JB CM10 folder on droidbasement), boot it and try to format the /system partition first then /data.

pershoot said:
odin flash CWM (you can use 6.0.2.8 in JB CM10 folder on droidbasement), boot it and try to format the /system partition first then /data.
Click to expand...
Click to collapse
Will Do, ODIN3 1.85?

pershoot said:
odin flash CWM (you can use 6.0.2.8 in JB CM10 folder on droidbasement), boot it and try to format the /system partition first then /data.
Click to expand...
Click to collapse
HI Pershoot!
I forgot to say thanks for your help!! I appreciate someone smarter than me lending a hand.
That said, I just tried to flash CWM from DB Galaxy Roms/CM10 folder. Upon reboot the tablet still entered stock recovery, I have tried this several times, but this time I took a video. If you feel so inclined to watch it maybe you can catch me doing something wrong....
Again thanks for your help!!
Video of me doing the Stock Recovery Factory Reset
Video of me attempting to flash CWM from droid basement

Mixinitup4Christ said:
HI Pershoot!
I forgot to say thanks for your help!! I appreciate someone smarter than me lending a hand.
That said, I just tried to flash CWM from DB Galaxy Roms/CM10 folder. Upon reboot the tablet still entered stock recovery, I have tried this several times, but this time I took a video. If you feel so inclined to watch it maybe you can catch me doing something wrong....
Again thanks for your help!!
Video of me doing the Stock Recovery Factory Reset
Video of me attempting to flash CWM from droid basement
Click to expand...
Click to collapse
I had to do this on mine. http://techne.alaya.net/?p=8829. I rooted and modified the file described in the steps. Weirdly enough it still booted into stock recovery the first time I installed CWM. I installed CWM one more time and the tablet now boots into CWM.

Related

[Q] Please help newbie with semi-bricked phone

Hi guys, I got a SGS2 just over a week ago, on Bell/Virgin network in Canada. Suffered from the battery drain issue due to being stuck with crappy UGKG2 firmware which my provider still hasn't updated.
I decided to update it myself, and did a ton of research. I successfully got Root tonight by flashing CF-Root-SGS2_ZS-OZS_KG2-v4.1-CWM4 kernel with Odin. In case it matters, I did NOT flash back my stock Kernel, so I still had the insecure kernel installed. From there, I backed up my apps with Titanium.
Went into CWM and selected boot into CWM Recovery. I followed the steps on the wiki, including creating a backup file. My only hint of what I might have done wrong was I originally selected to flash update.zip, and that process failed. I then went to the directory in which cyanogenmod is stored on my SD card, and selected that, then it installed ok. I had downloaded update-cm-7.10-GalaxyS2-signed and that's what I put on the phone. I then also installed the Google Apps.
I then hit reboot, and it only goes to the Samsung screen with the yellow triangle and just hangs there for a few minutes. Not knowing what else to do, I popped the battery out. I have since learned that I can turn it on and off, but it never goes past that screen. Wouldn't go into the recovery or download modes, always that screen. Luckily, I saw somewhere to do the 3 button thing WHILE in that screen, and that works. So I can get to recover, and download modes. So, I think I'm ok. I checked, and it does connect to Odin still.
I just want to know EXACTLY what I should do at this point. I don't want to fully brick it. There are actually two recovery files on the phone... not sure why... Or which one to pick. Should I just flash stock firmware back with Odin? One of my main goals is to get off 2.3.3 so I can have more than 8 hours of battery...
Thanks,
Rob
Boot into tecovery, do a full wipe again. (Wipe data/factory reset, wipe cache partition, advanced>wipe dalvik cache).
Now install CM7 zip twice in a row without reboot. It may take a few minutes for reboot since system is rebuilding dalvik cache. Be patient. After you see the home screen, reboot again.
Sometimes, CM won't install properly with CF root recovery. In that case reboot into download mode, flash codeworkx cwm kernel via ODIN.
http://forum.xda-developers.com/showthread.php?t=1118693
Now reboot into recovery and do full wipe and twice-install !
Ok, working now with the flash twice thing. Well that's weird, would be great if it was in the wiki page...
Thanks!
Rob

[Q] Bootloop comes out of nowhere

Had ICScrewed running for 4+ months and out of nowhere phone won't boot and is stuck in samsung bootloop.
I have searched and can't seem to get any solutions to work. I have done so much crap I am thoroughly confused as to what I have done and what I haven't tried yet.
Someone please send me in the right direction.
Right now last thing I flashed was "I777UCKH7 OCD Root No BL" oneclick.
Any ideas? I appreciate your help!!
Something changed to trigger the bootloop. If you can pinpoint some event that occured just before it, that might help determine a solution.
From what you say, you must now have stock UCKH7 installed. If you can boot into 3e recovery mode, try a wipe data/factory reset, and clearing anything that it will let you clear. Don't remember the stock recovery very well.
Or, if the bootloop will let you get into 3e recovery, you could flash a custom kernel back onto the phone, enter recovery and clear cache and dalvik cache, etc. Also, if you have a nandroid backup, from custom recovery you can restore the backup to get your phone to boot again.
If you need specialized files to flash to recover the phone, you will find them in the Download Repository, linked in my signature.
creepyncrawly said:
Something changed to trigger the bootloop. If you can pinpoint some event that occured just before it, that might help determine a solution.
From what you say, you must now have stock UCKH7 installed. If you can boot into 3e recovery mode, try a wipe data/factory reset, and clearing anything that it will let you clear. Don't remember the stock recovery very well.
Or, if the bootloop will let you get into 3e recovery, you could flash a custom kernel back onto the phone, enter recovery and clear cache and dalvik cache, etc. Also, if you have a nandroid backup, from custom recovery you can restore the backup to get your phone to boot again.
If you need specialized files to flash to recover the phone, you will find them in the Download Repository, linked in my signature.
Click to expand...
Click to collapse
I didn't do anything I can think of that would trigger this. I can't get into 3e Recovery it says "Deleting Cryption Meta Data" and just reboots.
I flashed via odin "SGH-I777_ClockworkMod-Recovery_5.0.2.3.tar" That gets me into CWM Recovery... i wiped data/factory reset... cleared cache... doesn't help.
Then I tried SD card to load a custom ROM and everything on the external SD card is completely not what shows up when i have it in my computer.
I am so lost.
bdkvxd said:
I didn't do anything I can think of that would trigger this. I can't get into 3e Recovery it says "Deleting Cryption Meta Data" and just reboots.
I flashed via odin "SGH-I777_ClockworkMod-Recovery_5.0.2.3.tar" That gets me into CWM Recovery... i wiped data/factory reset... cleared cache... doesn't help.
Then I tried SD card to load a custom ROM and everything on the external SD card is completely not what shows up when i have it in my computer.
I am so lost.
Click to expand...
Click to collapse
I just got a custom rom onto /sd with Droid Explorer and renamed it update and it installed but is still stuck in bootloop.
Any ideas? I need my phone for my business I am soo screwed!
Flashed SiyahKernel v2.6.14 and with stock rom it works. Thanks!
Be sure to make a nandroid backup once you have it configured the way you want. Restoring a nandroid backup is the first thing I would try if that type of problem ever happens again.

Galaxy Player 4.0 Bricked

Hey XDA, I was hoping you could help me out here. I just don't know what to do anymore. So, here goes.
I decided to flash the Terrasilent kernal. All went well during installation. When I booted back into the stock rom after flashing my kernal, I saw that some system apps (gmail and market) were not installed. The icons were there, but they said they weren't installed. Also, all photos, videos, ect were gone. I already had them backed up, so no big deal. So, to try to fix it, I went into Odin and tried to reflash my stock rom through there. Everything worked fine, all was well. That's when I discovered my file system was messed up. Pretty much, it only displays /sdcard/Android, as well as /sdcard/DCIM/, /sdcard/LOST.DIR/ and /sdcard/external_sd/. So, I went ahead and attempted to reflash my kernal (custom kernal, terrasilent if you want to know.) to see if it would fix my ****. **** was not fixed, to say the least. And when Odin said it failed, I flipped out and did the stupidest thing imaginable; I unplugged my USB cable. So, I went and tried to boot up, and got the picture you get when you can't go into recovery, boot up or even download more. A cell phone connecting to a pc picture. So, then I tried following some guides on XDA to fix it, reflashed some stuff, and got close to fixing it. I reflashed my partition table and then tried to flash my terrasilent kernal once more, and it booted up into recovery with no issue. Btw, the kernal installs CWM recovery. But when I tried to reflash my stock rom, it didn't boot up. It said in Odin that it succeded, but in the recovery (which changed back to stock android recovery, I am not sure why) and I got a bunch of errors saying I'm missing all sorts of files. Like, E:failed to mount /cache (invalid argument) or E:copy_kernal_file :: Can't open /cache/recovery/recovery_kernal.log. XDA, please help me. I need this fixed, I can't afford to buy another phone, I'm broke. Help me.
DarkMuffin Inc said:
Hey XDA, I was hoping you could help me out here. I just don't know what to do anymore. So, here goes.
I decided to flash the Terrasilent kernal. All went well during installation. When I booted back into the stock rom after flashing my kernal, I saw that some system apps (gmail and market) were not installed. The icons were there, but they said they weren't installed. Also, all photos, videos, ect were gone. I already had them backed up, so no big deal. So, to try to fix it, I went into Odin and tried to reflash my stock rom through there. Everything worked fine, all was well. That's when I discovered my file system was messed up. Pretty much, it only displays /sdcard/Android, as well as /sdcard/DCIM/, /sdcard/LOST.DIR/ and /sdcard/external_sd/. So, I went ahead and attempted to reflash my kernal (custom kernal, terrasilent if you want to know.) to see if it would fix my ****. **** was not fixed, to say the least. And when Odin said it failed, I flipped out and did the stupidest thing imaginable; I unplugged my USB cable. So, I went and tried to boot up, and got the picture you get when you can't go into recovery, boot up or even download more. A cell phone connecting to a pc picture. So, then I tried following some guides on XDA to fix it, reflashed some stuff, and got close to fixing it. I reflashed my partition table and then tried to flash my terrasilent kernal once more, and it booted up into recovery with no issue. Btw, the kernal installs CWM recovery. But when I tried to reflash my stock rom, it didn't boot up. It said in Odin that it succeded, but in the recovery (which changed back to stock android recovery, I am not sure why) and I got a bunch of errors saying I'm missing all sorts of files. Like, E:failed to mount /cache (invalid argument) or E:copy_kernal_file :: Can't open /cache/recovery/recovery_kernal.log. XDA, please help me. I need this fixed, I can't afford to buy another phone, I'm broke. Help me.
Click to expand...
Click to collapse
I believe what you need to go is go into the android recovery by holding volume up + power. Once you get in there Wipe data/factory reset, and Wipe cache Partition because I believe it's bootlooping.
obscuresword said:
I believe what you need to go is go into the android recovery by holding volume up + power. Once you get in there Wipe data/factory reset, and Wipe cache Partition because I believe it's bootlooping.
Click to expand...
Click to collapse
It didn't work. What do I do now? I tried to flash the Terrasilent kernel over it (which came with CWM) and it gave me the CWM recovery and kernel, but still nothing works. I tried reflashing the rom too but I can't get it to boot, just download mode and recovery loads now.
DarkMuffin Inc said:
It didn't work. What do I do now? I tried to flash the Terrasilent kernel over it (which came with CWM) and it gave me the CWM recovery and kernel, but still nothing works. I tried reflashing the rom too but I can't get it to boot, just download mode and recovery loads now.
Click to expand...
Click to collapse
Well good thing is you're not hardbricked. Have you followed all these steps in this order?
http://forum.xda-developers.com/showpost.php?p=28849870
Do you have the 4.0 stock rom? (Don't use the one I linked since it's for the 5.0). Also did you try wiping the dalvick?
obscuresword said:
Well good thing is you're not hardbricked. Have you followed all these steps in this order?
http://forum.xda-developers.com/showpost.php?p=28849870
Do you have the 4.0 stock rom? (Don't use the one I linked since it's for the 5.0). Also did you try wiping the dalvick?
Click to expand...
Click to collapse
Yes, I followed all those steps perfectly. I have reflashed my stock rom multiple times before. And I have wiped dalvick cache when I was able to get into my CWM recovery a few times to no avail. My pc recognized the device just fine until today. I just flashed my .pit file and the terrasilent kernel through heimdall, and now my device isn't being read through Odin OR Heimdall. It is recognized by my pc but not by those programs. And yes I am in download mode. I also tried flashing back to stock before but the recovery just gave me a bunch of red text errors.
DarkMuffin Inc said:
Yes, I followed all those steps perfectly. I have reflashed my stock rom multiple times before. And I have wiped dalvick cache when I was able to get into my CWM recovery a few times to no avail. My pc recognized the device just fine until today. I just flashed my .pit file and the terrasilent kernel through heimdall, and now my device isn't being read through Odin OR Heimdall. It is recognized by my pc but not by those programs. And yes I am in download mode. I also tried flashing back to stock before but the recovery just gave me a bunch of red text errors.
Click to expand...
Click to collapse
I can't really see the photo, can you type out the error codes lol.

[Q] Accidentally formatted with TWRP - boot loop

I accidentally formatted my internal SD card with TWRP instead of factory reseting. I can get into recovery, but loading any ROM hangs at the loading screen. For awhile, TWRP was asking for a password, and then somehow I hit the magic combination of things to make that stop happening. I adb pushed an updated TWRP and reinstalling various ROMs.
All this started from trying to install Hyperdrive RLS8. I was running RLS7 fine, went for a clean install, spaced out and formatted the phone, flashed the ROM, and had a whole slew of stability problems. Things would randomly crash instantly, booted only 50% of the time, when it did, installing things would break it, tried various things to fix it, fixing permissions and wiping cache's and such, and results were unpredictable. Kept re-formatting and reflashing with different options until I finally realized that I was formatting it and that's probably what the whole problem was.
Currently I can't boot into a ROM, it hangs on the boot animation. I tried another clean install with RLS7, and the same thing happens. I'm assuming that I need to get back to stock somehow, but I'm not sure how. Odin has always confused me. I used the all in one tool to root awhile back, and I only used odin to send a kernel tar file. If I download a stock build, it's a zip file... so how can I odin it? Is that what I need to do? I'm imagining at this point that the file structure is messed up and I need to rebuild it somehow. I don't have my nandroid backup on this computer, so I haven't tried that yet.
You can either odin stock. It's about a 1.8gb file.
Or you can get a known working ROM on your sd card, factory reset wipe, wipe preload, wipe system, install known working rom+gapps+whatever, wipe cache and wipe dalvik. Reboot. If it sticks at the samsung logo pull the battery and then try to reboot again. Sometimes first boot can take a while. I'd give it 10 minutes before throwing in the towel lol
I bricked my phone by updating Hyperdrive (which I will never (curse words... lots of them) use again. Can someone tell me where to find this stock file? I've been searching long enough to get frustrated and delete several less diplomatic posts, settling with this one.
hey guys, I am a little confused. I just came to the S4 from a galaxy nexus, and I previously used CWM as my recovery option when doing clean install of new ROMS.
When I rooted my S4, I installed TWRP (via goomananger, version 2.5.0.2) because of people saying its much better (on the galaxy nexus forums). However, I keep reading issues of people being stuck in bootloops for TWRP when wiping data.
My question is -- what is this issue? Are you not supposed to clean flash with TWRP?? Or do you only do "factory reset" option in TWRP and not wipe the data?
As I am a little confused on this issue, is it more safe to just install most recent CWM and use that as recovery instead?
Thanks alot
No worries
uberpippi said:
I accidentally formatted my internal SD card with TWRP instead of factory reseting. I can get into recovery, but loading any ROM hangs at the loading screen. For awhile, TWRP was asking for a password, and then somehow I hit the magic combination of things to make that stop happening. I adb pushed an updated TWRP and reinstalling various ROMs.
All this started from trying to install Hyperdrive RLS8. I was running RLS7 fine, went for a clean install, spaced out and formatted the phone, flashed the ROM, and had a whole slew of stability problems. Things would randomly crash instantly, booted only 50% of the time, when it did, installing things would break it, tried various things to fix it, fixing permissions and wiping cache's and such, and results were unpredictable. Kept re-formatting and reflashing with different options until I finally realized that I was formatting it and that's probably what the whole problem was.
Currently I can't boot into a ROM, it hangs on the boot animation. I tried another clean install with RLS7, and the same thing happens. I'm assuming that I need to get back to stock somehow, but I'm not sure how. Odin has always confused me. I used the all in one tool to root awhile back, and I only used odin to send a kernel tar file. If I download a stock build, it's a zip file... so how can I odin it? Is that what I need to do? I'm imagining at this point that the file structure is messed up and I need to rebuild it somehow. I don't have my nandroid backup on this computer, so I haven't tried that yet.
Click to expand...
Click to collapse
Try using odin to flash to stock. Then re-root and install custom recovery and whichever rom. I had a similar problem posted here with no help from the big brains. Had to trial and error with caution on my own. Kinda disappointing since the answer is quite simple once you connect all the dots. Flashing in odin will fix yer internal storage problem because it redefines everything.
cidorov said:
Try using odin to flash to stock. Then re-root and install custom recovery and whichever rom. I had a similar problem posted here with no help from the big brains. Had to trial and error with caution on my own. Kinda disappointing since the answer is quite simple once you connect all the dots. Flashing in odin will fix yer internal storage problem because it redefines everything.
Click to expand...
Click to collapse
uberpippi said:
I accidentally formatted my internal SD card with TWRP instead of factory reseting. I can get into recovery, but loading any ROM hangs at the loading screen. For awhile, TWRP was asking for a password, and then somehow I hit the magic combination of things to make that stop happening. I adb pushed an updated TWRP and reinstalling various ROMs.
All this started from trying to install Hyperdrive RLS8. I was running RLS7 fine, went for a clean install, spaced out and formatted the phone, flashed the ROM, and had a whole slew of stability problems. Things would randomly crash instantly, booted only 50% of the time, when it did, installing things would break it, tried various things to fix it, fixing permissions and wiping cache's and such, and results were unpredictable. Kept re-formatting and reflashing with different options until I finally realized that I was formatting it and that's probably what the whole problem was.
Currently I can't boot into a ROM, it hangs on the boot animation. I tried another clean install with RLS7, and the same thing happens. I'm assuming that I need to get back to stock somehow, but I'm not sure how. Odin has always confused me. I used the all in one tool to root awhile back, and I only used odin to send a kernel tar file. If I download a stock build, it's a zip file... so how can I odin it? Is that what I need to do? I'm imagining at this point that the file structure is messed up and I need to rebuild it somehow. I don't have my nandroid backup on this computer, so I haven't tried that yet.
Click to expand...
Click to collapse
Yes this would probably be your best bet. I wouldn't say the answer "is quite simple when you connect the dots" though, because with that logic there would be no PC problems, you would just connect the dots and format the harddrive and Windows will redefine everything else for you!
But back to seriousness, you have to download a stock factory image and its actually a tar.md5 file and not a .zip because you cant flash zips through odin. The stock factory images can be found in the development section, and they are usually quite large files (2gb+ when extracted!) and you will have to download odin and make sure you have the latest usb drivers from samsung. Then its pretty straight forward, The threads in the development section have guides for how to use odin. The stock image contains all the partitions within in it and will effectively repartition your device when you flash it so no need to use a pit file.
Surge1223 said:
Yes this would probably be your best bet. I wouldn't say the answer "is quite simple when you connect the dots" though, because with that logic there would be no PC problems, you would just connect the dots and format the harddrive and Windows will redefine everything else for you!
But back to seriousness, you have to download a stock factory image and its actually a tar.md5 file and not a .zip because you cant flash zips through odin. The stock factory images can be found in the development section, and they are usually quite large files (2gb+ when extracted!) and you will have to download odin and make sure you have the latest usb drivers from samsung. Then its pretty straight forward, The threads in the development section have guides for how to use odin. The stock image contains all the partitions within in it and will effectively repartition your device when you flash it so no need to use a pit file.
Click to expand...
Click to collapse
Just to follow up, that's what I ended up doing. I used the "No-wipe" factory image, odin'd it, re-rooted (I don't know if I had to do that step, but I did), and then loaded my ROM of choice and it works perfectly now. Thanks!

Bootloop (Device Always Boots Into CWM)

Hi everyone, I have a problem with my phone.
It is no longer booting into the OS, instead it boots into the recovery mode.
So here's what happened. I was on Google Play Store looking for some utility apps, and found this "[ROOT] Rashr" app, read its details and got interested in it since I also do wanna try to back up my CWM Recovery. I don't even completely understand what it means, but as what the apps says, I really thought that with it, backing up my recovery will be very easy, just like how ROM is backed up when you do a NANDroid backup. So, after it was installed, I head on to its Back-Up section, ticked the box for "Recovery", and tapped on "Go", expecting that it would work. It said "Rebooting..." and booted to recovery mode, so I thought that I had to complete the "Recovery Back-Up" inside CWM, so I spent time looking through the options. And, this is where I discovered that CWM has a rainbow color mode. When I found out that no signs of back up could be done in CWM, I rebooted from within CWM. BUT, it still booted to Recovery Mode.
I tried . . .
Odin, but since it boots only to recovery, Odin isn't detecting it.
Wiped the data, cache partition, and Dalvik cache. Then restore.
Can this be fixed? I badly need help.
I have:
CWM Recovery v6.0.3.6 (used when I rooted the phone), updated to v6.0.4.5 (current)
Stock ROM 4.1.2
Recent NANDroid Backup
Any inputs will be very much appreciated. Thanks.
No intention of giving the "Rashr" app a bad name. I just didn't know how to use it.
Endroyed said:
My device is no longer booting into the OS, instead it boots into the recovery mode.
So here's what happened. I was on Google Play Store looking for some utility apps, and found this "[ROOT] Rashr" app, read its details and I got interested in it since I also do wanna try to back up my CWM Recovery. I don't even completely understand what it means, but as the apps says, I really thought that with it, backing up my recovery will be very easy, just like how ROM is backed up when you do a NANDroid backup. So, after it was installed, I head on to its Back-Up section, ticked the box for "Recovery", and tapped on "Go" with expecting that it would work. It said "Rebooting..." and it booted to recovery mode. And I thought that I had to complete the "Recovery Back-Up" inside CWM, so I spent time looking through the options. When I found out that no signs of back up could be done in CWM, I rebooted from within CWM. BUT, it still booted into Recovery Mode. Can this be fixed?
I have:
CWM Recovery v6.0.3.6 (used when I rooted the phone), updated to v6.0.4.5 (current)
Stock ROM 4.1.2
Recent NANDroid Backup
Click to expand...
Click to collapse
Flash Stock Revovery.
http://forum.xda-developers.com/showthread.php?t=2716953
Can Download From Here.
put into memory card.
and select install zip external-sd card select zip and flash it
Cheers!
manojkumar8552 said:
Flash Stock Revovery.
http://forum.xda-developers.com/showthread.php?t=2716953
Can Download From Here.
put into memory card.
and select install zip external-sd card select zip and flash it
Click to expand...
Click to collapse
I never thought the solution would be that simple. Hehe Thanks manoj. :good:
Finally fixed it!
What I did:
1) Flashed the stock Recovery. I was surprised it was able to boot to Android cause I was thinking that the zip is only the stock recovery. It had errors though. Home Screen won't appear or load.
2) When rebooted, it got stuck in SAMSUNG boot animation, but it was all good cause Odin was still able to detect it which means it can still be rooted. So . . .
3) Flashed CWM Recovery v6.0.3.6
3) Wiped data, cache partition, and Dalvik cache.
4) Restored the backup.
Endroyed said:
I never thought the solution would be that simple. Hehe Thanks manoj. :good:
Click to expand...
Click to collapse
No Problems Buddy !!!
Step by step getting all f,,,, Fundas of Android soon

Categories

Resources