Related
I have been having issues with CWM on my Fascinate for about 2 weeks now. Whenever I try to flash anything via CWM I get this message:
Samsung Recovery Utils
- for BML -
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
The "reboot system now" is highlighted and I cannot do anything to select apply update.zip
On the bottom part of the screen it says:
Install from package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
Now I have flashed back to D101 and did the ota update to DL09, and flashed the CWM via odin posted on a thread from the android central forum, it is basically a version of CWM for DL05 and DL09. (can't post outside links so I havent posted enough in this forum).
I have tried to apply the update.zip but whenever I do that, after about 25% of the way through it goes back to the error.
I have completely run out of ideas and the people at the android central forums have as well. I have tried everything that I can think of but obviously I am not doing something right.
Can anyone give me some suggestions as to what I can do to try to resolve this issue? Or if there is a way to flash a rom and kernel without CWM. I really do not want to be stuck with stock Fascinate so anything would be appreciated.
Thank you
You have to go into CWM immediately after flashing in Odin, before booting up, and flash a new kernel. DL09 breaks CWM on the stock kernel
Sent from my SCH-I500 using XDA App
I had that same issue until a user on another forum informed me that right after flashing cwm, replace battery and go immediately into recovery mode, do not let the phone boot normally.
Now I am able to add kernels and roms to my hearts content.
I'm in a similar situation except my error comes while trying to back up my ROM.
I did root via pushing rage.bin via ADB
Then I used ODIN to put CWMrecovery.tar on the phone.
Flashed CWM via ROM Manager.
At this point I did a full backup with TiBu and did a ROM Backup via ROM Manager.
After that I froze bloatware, 'upgraded' to the Sywpe Beta and De-binged.
At about this point I realized that I had lost Haptic so I flashed the DL09 stock Kernel and that problem was solved. I thought I was good to go until I tried to do another backup via ROM Manager.
When I ran the backup I got the same error as the OP. I ended up in 2e recovery. Since I'm new to this I just chose reboot phone. I did some searching last night but all the posts I found dealt with people flashing custom ROMs and I was getting tired I called it a night with the plans to do more searching today but then I came across this post.
I reviewed my notes and saw the other thread about CWM Recover mode and I checked and I can't reboot into CWM Recovery (via ROM Man) either. I end up in Android (2e) recovery.
I saw the post above me and I need to search on these instructions so I understand this step better.
"I had that same issue until a user on another forum informed me that right after flashing cwm, replace battery and go immediately into recovery mode, do not let the phone boot normally."
I don't seem to be able to boot (up and down key = Power buttong) into any recovery.
It seems like I need to repush CWM via Odin and then reflash via Rom Man but I'm leaving for a trip tomorrow so I'll wait for some input before trying anything since the phone is functionally working.
I'm new to rooting phones so some help with this error would be appreciated.
ezas said:
I'm in a similar situation except my error comes while trying to back up my ROM.
My phone is updated OTA DL09. Then rooted via ADB. I installed ROM Manager and flashed CWM. Since then I've done the usual root stuff. I noticed that haptic was not working and I fixed that by flashing a stock DL09 kernel. I have not flashed a custom ROM.
After de binging yesterday I went todo a back up via ROM Manager and got the same error as the OP. I ended up in 2e recovery. I didn't want to really screw up my phone guessing so I just chose reboot phone.
I was going to do more searching tonight but came across this post first.
I have done two successful back ups via ROM Manager, so after reading this post I assume it's flashing the kernel that got me to this error.
I'm new to rooting phones so some help with this error would be appreciated.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I don't use custom roms on my phone but from what I'm gathering on this...
You will need to put it back to DL09 stock...
Flash CWM via Odin..
http://forum.androidcentral.com/ver...s-hacks/54659-how-rooting-your-fascinate.html
Post 4 here will tell you how to do it.
After flashing CWM you will need to put your phone into recovery right away instead of letting the normal rom load. You will then flash over another kernel using CWM and that is it.
List of kernels can be found here:
http://www.samsungfascinateforum.com/custom-roms/list-of-custom-dj05-kernels-for-verizon-fascinate/
I have never put a new kernel or rom on my phone but from what i've read this is the jist of it.
You shouldn't have to flash back to stock...
1. Download all necessary files and place on root of your SD card (nonstock kernel, update.zip)
Edit: also add in the superuser and busybox zips, and flash those after kernel (step 5) and this will give you root back if you lost it updating
2. Flash modified CWM .tar with Odin
3. Replace battery and boot directly into recovery by holding both volume buttons down while powering on
4. Once in recovery, apply update.zip to get into CWM
5. Flash new kernel
6. Reboot, enjoy
Kevin and Rob
I followed the instructions to the letter over at AndroidCentral (including flashing busybox_su) and I'm back up and running with Haptic feedback and I'm watching a ROM backup via ROM Manager as I type this. I have not done a lot of testing yet but everything seems to be working fine.
Thanks for all the help.
Kevin Gossett said:
You have to go into CWM immediately after flashing in Odin, before booting up, and flash a new kernel. DL09 breaks CWM on the stock kernel
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Just did that and after I select Install zip from SD car, the screen goes black. When I press the home button it goes back to the green list but when I select anything from there, the screen goes black again.
I have tried flashing back to stock, updating to DL09 and flashing cwm again, but same issue.
OK I am getting really tired of dealing with this. Nothing I try works. I am just going to give up on the idea of installing roms and kernels on my fascinate. I have no idea what the problem is and nobody knows either.
Thanks for all those that helped.
When in CWM the home button turns the screen off. Use the back button or power button to select
Kevin Gossett said:
When in CWM the home button turns the screen off. Use the back button or power button to select
Click to expand...
Click to collapse
Shh, I had no idea about that. I assumed since in order to get to cement recovery you had to press home key that that is what you use while in recovery. Everything works now, thank you.
ok, I'm ready to sell this damn Fascinate on Craigslist for a peanut butter sandwich. I'm miffed with getting CWM working. I have pushed the updated version onto the phone via ODIN, immediately booted into recovery (got the red recovery), and it won't mount my SD card. I had a similar problem in green recovery - it could see my SD card, but wouldn't show me all the files - including the download folder. So I couldn't flash anything. I've tried this 100 different ways. There's nothing wrong with the SD card. It reads fine in the phone, files working other than CWM. Please help. I'm stuck on stock. Have mercy.
gadgetmom88 said:
ok, I'm ready to sell this damn Fascinate on Craigslist for a peanut butter sandwich. I'm miffed with getting CWM working. I have pushed the updated version onto the phone via ODIN, immediately booted into recovery (got the red recovery), and it won't mount my SD card. I had a similar problem in green recovery - it could see my SD card, but wouldn't show me all the files - including the download folder. So I couldn't flash anything. I've tried this 100 different ways. There's nothing wrong with the SD card. It reads fine in the phone, files working other than CWM. Please help. I'm stuck on stock. Have mercy.
Click to expand...
Click to collapse
Download updated CWM at this post: http://forum.xda-developers.com/showthread.php?t=942021
Fixed my CWM problems.
That is the file I used. Relief
Tried both through Odin and loading onto phone. No dice.
That is the file I used. Relief
Tried both through Odin and loading onto phone. No dice.
the home key always turns the screen off, u have to hit search button to turn on and go back
OK, just to make sure I'm not crazy, I tried again. First I downloaded the SuperClean 2.2 update to my SD card. I re-downloaded the updated update.zip file and put it at the root of my SD card. I flashed DL09.tar.md5 via Odin to get back to stock. That completed with no problem. I flashed the EB01 radio, no problem. Flashed the updated CWM. Immediately booted into recovery (red). Attempted to Apply update.zip. Errored out. Attempted to apply update from SD card. Here's the error I'm getting:
-- Install from SDcard...
Finding update package...
E:Can't mount/dev/block/mmcblk1p1 (or dev/block/mmcblk0)
(Invalid Argument)
E: Can't mount SDCard:Update.zip
Installation aborted
gadgetmom88 said:
OK, just to make sure I'm not crazy, I tried again. First I downloaded the SuperClean 2.2 update to my SD card. I re-downloaded the updated update.zip file and put it at the root of my SD card. I flashed DL09.tar.md5 via Odin to get back to stock. That completed with no problem. I flashed the EB01 radio, no problem. Flashed the updated CWM. Immediately booted into recovery (red). Attempted to Apply update.zip. Errored out. Attempted to apply update from SD card. Here's the error I'm getting:
-- Install from SDcard...
Finding update package...
E:Can't mount/dev/block/mmcblk1p1 (or dev/block/mmcblk0)
(Invalid Argument)
E: Can't mount SDCard:Update.zip
Installation aborted
Click to expand...
Click to collapse
I think I see what your issue is. The red CWM that you loaded via ODIN installs onto the phone itself. You no longer need an update.zip file containing CWM on your sdcard. As long as you have successfully booted into red CWM, your next step is to do a full wipe, and then choose the "install zip from sdcard" option. You should then be able browse your sdcard and select the zip file containing the rom.
DO NOT rename the zip file containing the rom to update.zip and then select the "apply update.zip" option, as that will definitely not work. That option expects to find the CWM recovery app in the update.zip file, and errors out if it's anything else.
Posted from my EB01 SuperClean Fascinate with Voodoo
Oh, and make sure you have the most recent new CWM file from jt1134. The post from him that had the first fixed CWM I think may have required an update.zip file, but the current, updated files in it do not. If you're not sure, download the latest one from that post for Odin, and flash it from Odin again. You will them no longer need update.zip for sure.
Posted from my EB01 SuperClean Fascinate with Voodoo
Roblovesbox said:
I don't use custom roms on my phone but from what I'm gathering on this...
You will need to put it back to DL09 stock...
Flash CWM via Odin..
http://forum.androidcentral.com/ver...s-hacks/54659-how-rooting-your-fascinate.html
Post 4 here will tell you how to do it.
After flashing CWM you will need to put your phone into recovery right away instead of letting the normal rom load. You will then flash over another kernel using CWM and that is it.
List of kernels can be found here:
http://www.samsungfascinateforum.com/custom-roms/list-of-custom-dj05-kernels-for-verizon-fascinate/
I have never put a new kernel or rom on my phone but from what i've read this is the jist of it.
Click to expand...
Click to collapse
Awesome, thanks for the links.
EDIT: This is not a result of ROM Manager, this is a result of installing Overstock 1.4.3 which also installs CWM recovery.
Not trying to be rude or anything, but I don't remember this ever not working.
I am having issues with 3e. No matter how carefully I follow the instructions (flash->reboot->reinstall packages always fails) when flashing recovery from current Rom Manager and Premium License, it does not work. Additionally, the premium license is persistent in my applications list and no premium ROMs ever show up in my download list. Even when I select Vibrant MTB and either 2.x or 3.x, all I get is a message that states current recovery will be used. I'm still going thru posts for a possible solution.
Try putting this in the root of your internal SD, reboot to recovery and reinstall packages twice.
Yeah, I was misinformed. This is not a result of ROM Manager, this is a result of installing Overstock 1.4.3 which also installs CWM recovery.
If anyone want to do this it is really simple with the SGS kernel flasher app. Download your overstock kernel of choice from here or your choice of kernel that includes CWM from the dev bible, unzip it, move the zimage to the internal phone memory and then choose that file as your kernel with the SGS Flasher.
Note: I have not been successful with going back to stock kernel when I tried to but that may have been because I didn't disable the lag fix.
jneal9 said:
Try putting this in the root of your internal SD, reboot to recovery and reinstall packages twice.
Click to expand...
Click to collapse
I'm 100% stock on 2.2Froyo except for root/unlock and am puzzled by this. I know it's not ROM Manager because it worked on my first SGS4G which died and totally bricked after a week (TMO exchanged it happily cause it wouldn't even go into download mode or charge).
What's in this update you linked? Cause I'm smart, but not as smart as most of the posters here and I recognize only a couple things in the file.
It installs CWM.
Are you using a Vibrant or SGS4G?
SGS 4G for TMobile.
BTW... I totally appreciate the help here. I don't know the ins-n-outs of the android phones like I do IOs, not that I'm all that up to date on that either.
Update... Still does not work. I get the failed signatures error and the update is aborted. I tried doing a factory reset and re-rooting the phone in case something didn't work correctly and get the same error. At this point, it's all gravy since the only thing I really needed was the unlock but now I'm in a "I just want to know how this works" mode.
Thanks for the help.
Ok yeah that my be the problem since that zip is for the Vibrant. So just to be straight, you are unable to get CWM on your SGS4G?
That's correct. I can't apply any update.zip nor does flashing CWM recovery work. It says it's flashing but then when I do the 3 button reboot to get to recovery, it's the 3e version still and when I go to reinstall packages, it starts but then fails as it tries to verify signatures.
Hi Folks,
I'm trying to get clockwork installed on a rooted stock firmware vibrant for a friend. Using ROM manager i've tried to install CWM and it says it is successful, however after trying to reboot into recovery and choosing re-install packages I get these errors:
E:Failed to verify Whole File Signature
E:signature verification failed
Installtion aborted
I tried flashing Vibrant (MTD) Clockwork Recover 3.x from ROM manager but it does the same thing.
Also tried the AIO tool from the sticky in the dev section and it doesn't work either. I chose the custom ROM but it doesn't push it to the phone or reboot it into recovery. (The install drivers option gave me a windows unhandled exception error)
I downloaded Heimdall but am not sure how it's used, can it flash any ROM or only specially formatted ones?
I've been searching these forums for a few days now and finding so much new and old processes to do things and I'm not very familiar with Samsung phones so any help is appreciated. Thank-you.
Re-Root it
Re-root the phone using One-click, when Baywolfs fails, one click always does it because it push's it through using ADB
CWM wont work unless the phone is proper ROOTED, youll know when its done right, cause youll see the super=user App after your done
Link: http://forum.xda-developers.com/showthread.php?t=739300
After that, un-install Rom manager, then re-install it, then while your connected to WIFI or provider, make sure you flash CWM recovery,
Re- download the ROM again, but dont open it!!
Then when you are ready to flash that ROM as a zipped file, DO NOT open it [ meaning UNZIP] or you'll continue to get the signature error.
Then either flash using reboot into recovery or install using CWM option of sd card install, either or works!! .
Are you having trouble getting past the stock 3e recovery? I've been trying to get past it for a few days but have been poking around learning the in/outs of this. I have not yet gotten Rom Manager to properly flash CWM Recovery... the stock 3e is stubborn. Once CWM recovery is done, your options open up for backups, restores and installing some custom roms.
I don't know what the solution is but I'm still looking around.
Hope this was on track...
Its stuborn in the sense its picky about free space. You'll need to free up some room in order to use CWM. Reference this thread for guidance -
http://forum.xda-developers.com/showthread.php?t=925400
I have had my N7 for a week now, and have unlocked and rooted it. I flashed the jr5 rom and it worked ok, but i decided I wanted to try the pure AOSP rom, so I did a data/cache/dalvik wipe and flashed the rom. It proceeded to boot and freeze at the Google screen. I rebooted into recovery, and attempted to restore from my backup (failed), flash the jr5 rom (failed), and reflash the AOSP rom (failed). I then decided to follow the instructions on ROOTZwiki and restore back to stock (although still unlocked). I restored to the factory image, and attempted to flash the CM10 AOKP rom, and was again met with the frozen Google screen. I made sure to wipe data and both caches each time i tried to flash a rom, but I always end up stuck at the Google screen. What could be causing this? I would really like to know if anyone has any idea, because I fully plan on running the full version of CM10 when it is released.
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
redmonke255 said:
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
yes i did a factory data reset each time. I am currently running v5.8.0.2 of cwm
could that be the problem? that my cwm is just outdated already?
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
CharliesTheMan said:
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for taking the time to help me. Before I do the goo-manager/twrp install, are there any inherent advantages or disadvantages of using twrp as opposed to cwm? Also, I hadn't thought to check md5s after moving the roms, so I will be doing that from now on.
Twrp works just fine.
In your recovery, can you mount and unmount all your partitions without any errors?
Sent from my Nexus 7
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
crache said:
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
Click to expand...
Click to collapse
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
simms22 said:
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
Click to expand...
Click to collapse
I don't like Twrp not being able to boot into recovery from holding the buttons, especially running into these loops during installs. Had the sameresults with cwm though.Now I am having this boot loop with TeamEOS as well as Skanky (neither package gapps) I however only loop if installing gapps after the rom or wiping caches.
If caches and system are wiped, gapps installed, then the rom I get a functioning system.Can anyone shed some light on what trigers specific loops or how to review tje errors / panics?
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
spked said:
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
Click to expand...
Click to collapse
Do you flash the rom and gapps and then reboot, or flash the rom, reboot, then flash gapps?
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
dirtyhamster73 said:
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
Click to expand...
Click to collapse
Can you get to bootloader?
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Jordanooo said:
Can you get to bootloader?
Click to expand...
Click to collapse
I finally got in, so I'm all set. Thanks! I have no idea why I was having a hard time...twrp wouldn't pop up once I was in boot loader. I must of tried like 20 times. Anyway....I'm in and I just reflashed and it was fine.
---------- Post added at 05:42 PM ---------- Previous post was at 05:40 PM ----------
armyboy11b said:
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm using twrp...for whatever reason I couldn't get it to pop up to reflash. But I'm good now. Thanks!
Recently my Galaxy S4 was having boot problems. It wasn't able to get past the "Samsung: Custom" logo. I was using TWRP 2.6 and the CM 10.2 8-19 nightly. I tried to do wipe all data and cache then re-flash the rom, no difference I tried to flash CWM Touch, no difference. At this point I figured something just went wrong when I originally rooted and flashed TWRP. I decided that it would be best to start from scratch and flash to stock in Odin.
I download a file from stockroms.net (can't post the full link as I'm a new member, but its a pretty easy website to navigate)
When the file is unzipped it has a .tar md5 file in it. I factory reset, wipe cache, and go into download mode. I boot up Odin 1.85 and load the .tar file into the PDA line. I make sure that the phone is connected fine, and I hit start. Everything goes fine, it says it passes and on the phone it appears everything went fine. After it reboots though, It wont make it past the "Samsung: Custom" logo again. It wont even hang on the logo, it will just shut off after a few seconds of showing it. I'm thinking that it's trying to boot, but cant. So I boot into the stock recovery, and it gives me this text at the bottom:
# Manual Mode #
-- Applying Multi-CSC...
successfully applied multi-CSC
E: failed to mount /data (invalid argument)
can't mount '/data' (invalid argument)
E: failed to mount /data (invalid argument)
So it looks to me that the phone is just unable to access the /data folder to boot into, and it gets stuck. How can I fix this?
EDIT: Also want to say that "repartition" was not checked in odin.
EDIT2: It seems that I fixed the problem, thanks for the help guys!
Can you do a factory reset in recovery?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
Can you do a factory reset in recovery?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Yes I did
You'll want to flash a different recovery until you find one that can fix your /data issue.
I have great luck with TWRP 2.5.0.2, though some others have said it causes problems when formatting /data on TW ROM's.
I use AOSP and have not had a problem since I last used TWRP 2.6 and subsequently went back to 2.5.0.2.
2.6 and some other recoveries just kinda suck.
It's amazing that a phone as popular as the Galaxy S4 has gotten such slow development process from CWM and TWRP. S3 recoveries were all rock solid within a month or so of release. We're not what, FIVE+ months into release and TWRP still hasn't gotten it 100% right. And I don't remember what the deal was with stock CWM (not Phillz which I have no experience with).
CZ Eddie said:
You'll want to flash a different recovery until you find one that can fix your /data issue.
I have great luck with TWRP 2.5.0.2, though some others have said it causes problems when formatting /data on TW ROM's.
I use AOSP and have not had a problem since I last used TWRP 2.6 and subsequently went back to 2.5.0.2.
2.6 and some other recoveries just kinda suck.
It's amazing that a phone as popular as the Galaxy S4 has gotten such slow development process from CWM and TWRP. S3 recoveries were all rock solid within a month or so of release. We're not what, FIVE+ months into release and TWRP still hasn't gotten it 100% right. And I don't remember what the deal was with stock CWM (not Phillz which I have no experience with).
Click to expand...
Click to collapse
I would just flash the .img recovery file straight through Odin correct?
EDIT: Sorry, I meant the .tar file
You should not get any files from stockroms.net. I have seen many people including myself try their stuff and fail. Always get you stuff from XDA.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
You should not get any files from stockroms.net. I have seen many people including myself try their stuff and fail. Always get you stuff from XDA.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'll try to remember that in the future. I actually just retried what I did with the stockroms.net file and the one that's in the sticky post here and it worked. I'm now back into TW and I'll be flashing a ROM in a bit. So thanks for the help guys, I guess I just needed to get my stuff from the right sources.
How did you fix it
Hello,
May I ask how did you fix the problem??
Thanks !
Fix #2
In my case rooting with CF-AUTO-ROOT fixed the data folder !