So, I have the Samsung Fascinate from Verizon, had this phone when it was new and just found it again and it is much better than my blackberry, or so I thought. I am trying to install ICS build one by following http://forum.xda-developers.com/showthread.php?t=1238070: - I have been able to install PW but when I am trying to install ICS1.zip (I renamed for simplicity purposes) I get the following errors: E: Can't mount /cache/recovery/log and cache/recovery/last_log
I have read enough to know that I needed a class 6 or better SD card so I bought a Class 10 8 GB from Best Buy and gave it another shot. I have mounted and unmounted the SD card multiple times, and when installing it shows:
-- Installing: /sdcard/ICS Build 1.zo[
Finding update package...
Opening update package...
Installing the update...
Installation aborted.
Any suggestions are greatly appreciated by those with positive feedback or calling me ignorant and not finding the answer online. Again, thanks in advance.
P.S. Yes, I have installed everything up until step 19 is where it stops working
Hey, i have had this problem as well when installing ICS. First off i would recommend installing build 6 instead of build 6.1 because build 6.1 actually has more problems that build 6. you can get build 6 from here : http://rootzwiki.com/topic/16630-romicsiml74k-teamhacksungs-ics-port-for-fascinate-build-61-0201/
Now to fix your sd error, you need to use the odin program and flash your phone back to any stock firmware. Here is verizon stock EH03 : http://www.multiupload.com/4LC6JFCSFD I'm sorry it is such a large file, verizon puts a bunch of crap on their firmwares lol As for your sd card, i honestly do not think it makes a difference what class it is. I am using a class 2 16gb sd card and have never ever not been able to get something to work.
Now after that is done, and it has booted to stock verizon firmware, put the phone back into download mode and use the odin program again to flash a cwm recovery kernel. This one should do just fine, if for some reason it doesn't, let me know and i will upload mine and you can have it. http://forum.xda-developers.com/atta...2&d=1311907538
After you have used odin and flashed a cwm recovery, please power off your phone and hold down the volume up, down, and power keys at the same time till the samsung logo comes on, so you can go into the new recovery kernel that you flashed to it. Once there, go to the option where it says wipe data/factory reset. After that has completed, do the next option that says wipe cache. Once that is all done, you will say "install zip from sd card" and navigate to the .zip
Now here is where you have two options....you can either flash build 1 first and then build 6, or you can skip straight to build 6. Personally i would skip straight to build 6!! It should work just fine as long as you have wiped data and cache. The differences between build 1 and 6 are night and day and you would have to clear data and cache anyway after you had build 1, so you should be able to go strait to build 6. Other people i have helped went fine right to build 6
After installing the .zip, navigate to the option that says "reboot system now". if you encounter a boot loop that constantly goes into the cwm recovery, let me know! I have dealt with that first hand! let me know if you have questions
Also i recommend using the magnifying glass capacitive search key to make your selections when in cwm, because for some reason i feel using the power key was partly the reason i encountered the cwm boot loop
So you odined back to stock and then tried flashing build 1 in cwm4 fixed for mtd?
---------- Post added at 09:02 AM ---------- Previous post was at 08:59 AM ----------
kadin.zimmerman said:
Hey, i have had this problem as well when installing ICS. First off i would recommend installing build 6 instead of build 6.1 because build 6.1 actually has more problems that build 6. you can get build 6 from here : http://rootzwiki.com/topic/16630-romicsiml74k-teamhacksungs-ics-port-for-fascinate-build-61-0201/
Now to fix your sd error, you need to use the odin program and flash your phone back to any stock firmware. Here is verizon stock EH03 : http://www.multiupload.com/4LC6JFCSFD I'm sorry it is such a large file, verizon puts a bunch of crap on their firmwares lol As for your sd card, i honestly do not think it makes a difference what class it is. I am using a class 2 16gb sd card and have never ever not been able to get something to work.
Now after that is done, and it has booted to stock verizon firmware, put the phone back into download mode and use the odin program again to flash a cwm recovery kernel. This one should do just fine, if for some reason it doesn't, let me know and i will upload mine and you can have it. http://forum.xda-developers.com/atta...2&d=1311907538
After you have used odin and flashed a cwm recovery, please power off your phone and hold down the volume up, down, and power keys at the same time till the samsung logo comes on, so you can go into the new recovery kernel that you flashed to it. Once there, go to the option where it says wipe data/factory reset. After that has completed, do the next option that says wipe cache. Once that is all done, you will say "install zip from sd card" and navigate to the .zip
Now here is where you have two options....you can either flash build 1 first and then build 6, or you can skip straight to build 6. Personally i would skip straight to build 6!! It should work just fine as long as you have wiped data and cache. The differences between build 1 and 6 are night and day and you would have to clear data and cache anyway after you had build 1, so you should be able to go strait to build 6. Other people i have helped went fine right to build 6
After installing the .zip, navigate to the option that says "reboot system now". if you encounter a boot loop that constantly goes into the cwm recovery, let me know! I have dealt with that first hand! let me know if you have questions
Also i recommend using the magnifying glass capacitive search key to make your selections when in cwm, because for some reason i feel using the power key was partly the reason i encountered the cwm boot loop
Click to expand...
Click to collapse
Build 6 link is dead...and for most flashing build 1 or 2 first is the only way ics build 6 will install. Also many folks have had trouble with class 2 sd cards...your not doing anything special more so just lucky its working for you.
kadin.zimmerman said:
Now after that is done, and it has booted to stock verizon firmware, put the phone back into download mode and use the odin program again to flash a cwm recovery kernel. This one should do just fine, if for some reason it doesn't, let me know and i will upload mine and you can have it. http://forum.xda-developers.com/atta...2&d=1311907538
Click to expand...
Click to collapse
That link does not work for me just FYI. I am currently back to stock (it's what I do when I can't get it to work because I am not to big of a powerwash fan. I have cwm4 to cm7. I believe it is 4.0.1. But I will search for the latest cwm recovery and put it on and see if that fixes any issues. I also saw somewhere a few days back that people format their SD cards on their PC but I do not remember what format so if that is completely irrelevant since the SD card is brand new (Almost 12 hours old) let me know. I will keep you posted and see it works.
New link to build 6 : http://www.mediafire.com/?sjn6x76c48me9su
So if going right to build 6 didn't work, then you would just have to give it another try, but installing build 1 or 2 first. No big deal, however I do know people who have had it work just fine.
I never said i was doing anything special because i had a class 2 sd card. I simply find it hard to believe that the sd card would have that much of a bearing on whether or not you can install a rom on a phone. I realize some roms partition the sd card the way it wants it, but in the end, the rom is flashed onto the actual phone itself, not the sd card. I know what the difference is between different classes of sd cards so you don't have to explain.
---------- Post added at 03:58 PM ---------- Previous post was at 03:52 PM ----------
PushyFurball said:
That link does not work for me just FYI. I am currently back to stock (it's what I do when I can't get it to work because I am not to big of a powerwash fan. I have cwm4 to cm7. I believe it is 4.0.1. But I will search for the latest cwm recovery and put it on and see if that fixes any issues. I also saw somewhere a few days back that people format their SD cards on their PC but I do not remember what format so if that is completely irrelevant since the SD card is brand new (Almost 12 hours old) let me know. I will keep you posted and see it works.
Click to expand...
Click to collapse
Sorry i thought that link was working...here is the one i originally start out with when flashing from stock. : http://dl.dropbox.com/u/32493357/cwm4_fixed_for_cm7-ODIN.tar
Please don't hit me, dropbox link doesn't work either.
PushyFurball said:
Please don't hit me, dropbox link doesn't work either.
Click to expand...
Click to collapse
Give it another try, it is working for me when i click on it
When I go to "wipe data/factory reset" I still receive the errors about opening stuff and this is what it looks like
-- Wiping data...
Formatting /data...
Formatting /cache...
Error mounting cache!
Skipping format...
Formatting /datadata...
Error mounting /datadata!
Skipping format...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
E: Can't open/mount /cache/recovery/log & .../last_long
-Exactly what I am doing step by step including what is clicked-
From stock, I open odin, pull out the battery, connect to PC via USB cord, press vol - on the phone. Then, I click, PDA, go to ..../Downloads and find the cwm4_fixed_for_cm7-ODIN.tar file and populate that portion of odin and put alas.2.2.pit in the pit section with the re-partition clicked. After completed, I go to odin, hit reset while the phone is still connected and then disconnect the phone. I put the battery in the back, press vol +/- and power and hold that until I see Samsung (which I don't see so I hold it for about 45 seconds to a minute and it boots it CWMR 4.0.1.0) and start trying to clear stuff and that is when I get the errors. So what I have done this time, is formatted the SD card in the recovery menu which I saw was not suggested, and I am going to try to just do a fresh install and maybe it was in the wrong format, who knows.
Ok, turn your phone off, remove the memory card, and flash this kernel instead : http://dl.dropbox.com/u/32493357/CWM3_Voodoo.tar.md5
Then put the memory card back in and boot to recovery
---------- Post added at 04:50 PM ---------- Previous post was at 04:32 PM ----------
PushyFurball said:
When I go to "wipe data/factory reset" I still receive the errors about opening stuff and this is what it looks like
-- Wiping data...
Formatting /data...
Formatting /cache...
Error mounting cache!
Skipping format...
Formatting /datadata...
Error mounting /datadata!
Skipping format...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
E: Can't open/mount /cache/recovery/log & .../last_long
-Exactly what I am doing step by step including what is clicked-
From stock, I open odin, pull out the battery, connect to PC via USB cord, press vol - on the phone. Then, I click, PDA, go to ..../Downloads and find the cwm4_fixed_for_cm7-ODIN.tar file and populate that portion of odin and put alas.2.2.pit in the pit section with the re-partition clicked. After completed, I go to odin, hit reset while the phone is still connected and then disconnect the phone. I put the battery in the back, press vol +/- and power and hold that until I see Samsung (which I don't see so I hold it for about 45 seconds to a minute and it boots it CWMR 4.0.1.0) and start trying to clear stuff and that is when I get the errors. So what I have done this time, is formatted the SD card in the recovery menu which I saw was not suggested, and I am going to try to just do a fresh install and maybe it was in the wrong format, who knows.
Click to expand...
Click to collapse
Actually i have never put a pit file into odin. When ever i went back to stock i just did the stock .tar.md5 file and it worked fine. I am not sure what the pit file is used for so maybe i would not use that. Let me know if that voodoo recovery got rid of that error
So the good news first, not putting PIT on their got rid of the errors of mounting and whatnot. Bad news is...
-- Installing: /sdcard/ICS Build 1.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
That is the same for Voodoo Lagfix and cwm4.
Now when I tried just the Build 6, it is constantly going to "Samsung" over, and over, and over again.
Ok good you are making progress lol. So you did try it with build 1 initially and it didnt work? Thats strange because it usually does.
So have you gone completely stock without the pit file, loaded a cwm kernel, and then wiped data and cache and still no luck?
There are two different versions of ICS for the fasciante, one by alphalulz and the much better builds from teamhacksung. No matter what i tried and it didnt work on my device (before i eventually figured it out) , alphalulz's ICS V2 always would load on my device. It also loaded its own custom kernel as well, so when it installed, i would let it boot up to confirm the V2 version was working, and then i would clear all data and cache in the new kernel it gave you, and then would switch over to teamhacksungs builds.
here is the link to download the V2 rom : http://rootzwiki.com/topic/9687-rom-aosp-ics-extreme-alphalulz-v2-1118/
Oh. My. Goodness. We have a good sign that this beast is going to work with Teamhacksung's versions... I don't really know what I did, I went back to stock with the pit file, downloaded build 1 while this was processing, and booted it up after it was finished. Then from there, I put that file, original name on my SD card and turned off my phone. Pulled the battery and odin'd cwm4 to cm7 and unplugged. Put the SD card in, booted to recovery, wiped the appropriate files, clicked install zip from SD card, picked the original name, and BAM!, it worked. So now I am going to try to put on build 6 and will edit this post to let you know if it worked or not. I am so happy I could literally jump up and down screaming like a little girl.
----EDIT----
Well, that failed miserably. Stuck on Samsung screen now. So, I guess back to step one.
PushyFurball said:
Oh. My. Goodness. We have a good sign that this beast is going to work with Teamhacksung's versions... I don't really know what I did, I went back to stock with the pit file, downloaded build 1 while this was processing, and booted it up after it was finished. Then from there, I put that file, original name on my SD card and turned off my phone. Pulled the battery and odin'd cwm4 to cm7 and unplugged. Put the SD card in, booted to recovery, wiped the appropriate files, clicked install zip from SD card, picked the original name, and BAM!, it worked. So now I am going to try to put on build 6 and will edit this post to let you know if it worked or not. I am so happy I could literally jump up and down screaming like a little girl.
----EDIT----
Well, that failed miserably. Stuck on Samsung screen now. So, I guess back to step one.
Click to expand...
Click to collapse
Hey your getting closer...you will get it dont worry lol
so you just had build 1 working right?? go from build 1 to build 5 (being sure to clear data and cache) and then from build 5 to 6, ONLY clearing cache. Going from build 5 to 6 does not require a data reset.
I am a new proud member of having a Samsung Fascinate with 4.0.3 . Thank you so much for your help kadin.zimmerman!
-Thread Closed- ^_^
Now download ROM manager and do a backup so you can revert back to that state in case something goes wrong! I do backups about once a week
Sent from my SCH-I500 using XDA App
I installed FA16 (2012/1/16): ODIN CWM that was listed on the first page of the developement forum. There were no issues - only took a few minutes. Afterwards - nothing seems to have changed on my phone. the firmware is still 2.3.5, the kernel is still 2.6.35.7 and the build number is sch-i500-eh03. Have I missed something? The phone seems to be working OK. Note: I installed CWM from the ZIp file after I put it on the SD card in the root directory. Thanks for your help
No you haven't missed anything - you flashed a new recovery kernel. Do you know what the purpose of the recovery kernel is? The recovery does not effect your 2.3.5 operating system, the cwm recovery allows you to boot to it (by powering the phone completely down, and then holding the up volume, down volume, and power button simultaneously) and then you will be presented with a menu to install a custom rom such as the new android 4.0 or the cm7 cyanogen mod etc...so its pretty cool
Thanks for 'learning me'. Anyway, before i started playing with my Fascinate today, I had ver 2.2.1 installed - worked fine. After all the changes, I lost the Google search box on the home page - is there anyway I can get that back? I have the icon - just like the search box better. Thanks
Well what all changes did you do other than installing a recovery? Did you flash any files?
And you have 2.3.5 now right, so how did you get it. Did you do a Verizon over-the-air update or did you flash that file as well. I am just confused as to what you did because technically if all you did was install a recovery, it wouldn't mess with you Google search
kardin - recoveries and kernels are 2 completely different things. You keep saying CWM recovery kernel, but that doesn't make any sense. I'm not saying you don't understand what a kernel or recovery is, but they're not the same thing and I think you might confuse people when you say recovery kernel.
Related
Hi All, first time poster, long time lurker.
I previously had CM7 installed on my fascinate and that was the first time I ever rooted so it was a tad buggy and there were two CWM recoveries (JT’s red 2.5 & CWM 4.X fixed for CM7) installed. To get to JT’s I did the three finger salute, and to get to 4.X, I used long held the power button in CM7 and rebooted into recovery. Anyways I decided to right my wrongs and flash CM7 from scratch. I followed these instructions to the letter (started with Post #2 then moved onto post #1) ([http :// w w w .fascinateforums. c o m/forum/fascinate-rs-guides/2961-how-upgrade-cyanogenmod7.html[/url]) [sorry could not post links... please edit spaces for it to work], multiple times, and could not get it to work. If anyone could shed some advice, it would be greatly appreciated.
A brief overview of what I did.
1. Phone had CM7 Installed, w/ CWM4.0.1.0 and JT’s Red CWM 2.5… decided to reflash from the very beginning.
2. Downloaded DL09 & Atlas v2.2 PIT as defined in Post #2 in the instructions provided in the previous link.
3. Used odined, put DL09 in PDA, Atlasa v2.2 in PIT, checked off re-partition, and Started Odin. Success.
4. Did not turn on the phone, instead connected into Odin immediately after and flashed CWM4 that was fixed for CM7. Success
5. Used three finger method and got into blue CWM4.0.1.0
6. Wiped data three times… wiped cache three times… wiped Dalvik three times.
a.Note: While wiping data, it did not allow me to wipe “datadata” and skipped that part
b.Note: While wiping Dalvik, it said that it had wiped dalvik but the line to it mentioned a path not being found..?
7. Flashed the 7/17 build. Now the trouble begins…
a.Recovery says “Checking status of bml/mtd” then “installation complete.” Phone reboots into the SAMSUNG splash screen then to the SAMSUNG & CM7 splash screen. It never makes it to the skateborder screen and is just stuck on the SAMSUNG & CM7 screen.
b. How long am I supposed to wait here? I waited 10 minutes and it was still stuck… so I just battery pulled. Phone is restored to stock now (using steps 1-2).
I tried this method at least 3-4 times and it always gets stuck on the Samsung & CM7 Splash Screen and just stays there… I am probably doing something wrong but can’t catch it.
I also another method. In step 5, I also went to mount/storage in recovery and wiped /system in addition to wiping data/cache/dalvik. Afterwards I flash the 7/17 build and instead of it being stuck in Samsung & CM7 splash screen it was stuck in an infinite bootloop from SAMSUNG -> SAMSUNG & CM7 -> Recovery (for a quick second) and back to SAMSUNG. When it loops back to recovery it quickly says “Can’t mount” then “installation aborted” and then continues the infinite loop to Samsung => Samung/CM7, etc…
Currently i followed steps 1-2 above and got the phone back to stock and have been using it ever since like that. I miss CM7...
Any help would be greatly appreciated. This forum has provided a plethora of wealth, and I would love to contribute back one day.
Many thanks,
Pat
This may be placebo more than anything, but when I was having problems, I went back to the EB01 stock with atlas as opposed to DL09 and then rooted manually to rooted stock using super one click before flashing the fixed CWM. Things worked great after that.
Also, if all else fails, flash CM7 7/4 and then upgrade from there... even though 7/17 should be fine, 7/4 was considered the jumping off point for a while.
pmanliu said:
Hi All, first time poster, long time lurker.
I previously had CM7 installed on my fascinate and that was the first time I ever rooted so it was a tad buggy and there were two CWM recoveries (JT’s red 2.5 & CWM 4.X fixed for CM7) installed. To get to JT’s I did the three finger salute, and to get to 4.X, I used long held the power button in CM7 and rebooted into recovery. Anyways I decided to right my wrongs and flash CM7 from scratch. I followed these instructions to the letter (started with Post #2 then moved onto post #1) ([http :// w w w .fascinateforums. c o m/forum/fascinate-rs-guides/2961-how-upgrade-cyanogenmod7.html[/url]) [sorry could not post links... please edit spaces for it to work], multiple times, and could not get it to work. If anyone could shed some advice, it would be greatly appreciated.
A brief overview of what I did.
1. Phone had CM7 Installed, w/ CWM4.0.1.0 and JT’s Red CWM 2.5… decided to reflash from the very beginning.
2. Downloaded DL09 & Atlas v2.2 PIT as defined in Post #2 in the instructions provided in the previous link.
3. Used odined, put DL09 in PDA, Atlasa v2.2 in PIT, checked off re-partition, and Started Odin. Success.
4. Did not turn on the phone, instead connected into Odin immediately after and flashed CWM4 that was fixed for CM7. Success
5. Used three finger method and got into blue CWM4.0.1.0
6. Wiped data three times… wiped cache three times… wiped Dalvik three times.
a.Note: While wiping data, it did not allow me to wipe “datadata” and skipped that part
b.Note: While wiping Dalvik, it said that it had wiped dalvik but the line to it mentioned a path not being found..?
7. Flashed the 7/17 build. Now the trouble begins…
a.Recovery says “Checking status of bml/mtd” then “installation complete.” Phone reboots into the SAMSUNG splash screen then to the SAMSUNG & CM7 splash screen. It never makes it to the skateborder screen and is just stuck on the SAMSUNG & CM7 screen.
b. How long am I supposed to wait here? I waited 10 minutes and it was still stuck… so I just battery pulled. Phone is restored to stock now (using steps 1-2).
I tried this method at least 3-4 times and it always gets stuck on the Samsung & CM7 Splash Screen and just stays there… I am probably doing something wrong but can’t catch it.
I also another method. In step 5, I also went to mount/storage in recovery and wiped /system in addition to wiping data/cache/dalvik. Afterwards I flash the 7/17 build and instead of it being stuck in Samsung & CM7 splash screen it was stuck in an infinite bootloop from SAMSUNG -> SAMSUNG & CM7 -> Recovery (for a quick second) and back to SAMSUNG. When it loops back to recovery it quickly says “Can’t mount” then “installation aborted” and then continues the infinite loop to Samsung => Samung/CM7, etc…
Currently i followed steps 1-2 above and got the phone back to stock and have been using it ever since like that. I miss CM7...
Any help would be greatly appreciated. This forum has provided a plethora of wealth, and I would love to contribute back one day.
Many thanks,
Pat
Click to expand...
Click to collapse
In step three of your post you have to fully reboot after flashing dl09 with the atlas pit file to convert all your files back to rfs before trying to install cm7...by pushing the dl09 w/atlas pit and not rebooting youre not fully completing the dl09 install so pretty much you just needed to reboot fully after flashing dl09 thats all.
If your sitting on a running dl09 now, then just do everything you did before minus the atlas pit and dl09...basically flash recovery...boot immediately into cwr and flash the same build using your same method...you probably won't have the data/data wiping problem anymore either!
Edit..you can also try the previous posters instructions as they have worked for me as well in fact every time I have to go back the eb01 file is what I use but most have no trouble with dl09
Sent from my SCH-I500 using XDA App
OMG im having the exact problem and for me that eb01 install did no difference i was also Stuck on SAMSUNG & Cm7 and by the way there is no 7/04 build because JT updated his site and there is none left
izzjkjoe said:
OMG im having the exact problem and for me that eb01 install did no difference i was also Stuck on SAMSUNG & Cm7 and by the way there is no 7/04 build because JT updated his site and there is none left
Click to expand...
Click to collapse
Have you tried booting up the phone after the initial first two steps (PDA +atlas 2.2 Pit)?
I'm at work and have not been able to try anything yet... will do when i get home in a hour
I have tried full reboot after flashing DL09 and it still doesnt work... gets me into a boot loop again. It did fix the wiping datadata issue but no luck with CM7...
I also tried EB01 without any luck.
Additionally i tried JT's 2.5 CWM (Red) and also a newer CWM 3.x...
none of these work. This is day 3 of my rooting problems... thanks for the replies, any more advice would be greatly appreciated...
Try it again and record your steps exactly and post them and I'll try and see what went wrong...it could just be a corrupt download of one of your files or just a simple missed step. What build are you on and what rom are you trying to go to?
Edit: this is what I have done multiple time without a hitch
regardless of what build and rom your on..
-pull your battery
-odin official vzw EB01 (pda button only..just a reminder) and the atlas
2.2 pit file and check the repartition box (I use odin v.1.7, but it shouldn't matter) and let odin do it's thing
-install battery and fully boot and let it sit for a minute our two after it loads
-pull battery
-odin recovery jt's 3-30 fix all... (found in nitsuj's sticky in the development section under recoveries)
-insert battery
immediately three finger boot into recovery and wipe everything
-flash newest cm7 build..I can't remember the date (I used the 7/4 build to get on to cm7 but it has been removed but the latest on will work)
-reboot fully
-use power button menu and select reboot..recovery to get to new blue recovery
-Flash newest cm7 build (if applicable), gapps and or mtd kernel if desired without wiping
-reboot, and enjoy cm7
Sent from my SCH-I500 using XDA App
Just saw your post. Will give it a try now.
When i'm in a bootloop and it hits the recovery part of the loop, i was able to get the error message (via using a camcorder lol)
-- Installing
Finding update package
E: unknown value for path []
E: Can't mount
Installation aborted
hope this helps,
many thanks
patrick
-----
edit:
tried your method to the dot. I get stuck on trying to flash CM7. Now instead of boot looping it just says
E: Error in /sdcard/cm7new/update-cm-7.1.0-fascinate-kang-0717-signed.zip
(status 7)
installation aborted.
i'm redownloading the update and will see if replacing it on the sd card will work. Otherwise...
-----
redownloaded & replaced the cm7 zip file on SD card. No success.
No luck w/ your method posted either...
Oi...
this is upsetting
Download the recovery in the cm7 thread and repeat the same steps but use the recovery from the cm7 thread instead of 3-30 fix all and that should work
Sent from my SCH-I500 using XDA App
efan450 said:
Download the recovery in the cm7 thread and repeat the same steps but use the recovery from the cm7 thread instead of 3-30 fix all and that should work
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Did that... just goes back into the bootloop from recovery => SAMSUNG => SAMSUNG/CM7 (not the skateborder screen) and gives me this errorr:
-- Installing
Finding update package
E: unknown value for path []
E: Can't mount
Installation aborted
------
edit:
okay i decided to flash MIUI fascinate 1.7.15 instead of CM7 and see if that works.
Well MIUI is running, but the weird thing is i still get SAMSUNG/CM7 boot screen before the MIUI boot screen comes up...
i am so confused!
I went through that same nightmare trying to install MIUI. CM7 or MIUI would give me status 7, and sometimes CM7 would go through, but just bootloop like you mentioned.
I tried about everything, and the only thing that worked for me was to first flash the 7/4 CM7 release for CWM 4.x, then flash MIUI over that. With any luck, the same will work for you for newer CM7 releases.
Unfortunately, like someone mentioned, the file was removed for some reason or another. I've still got it, so I reuploaded it for you, but jt, if there was some particular reason it was removed, say the word and I'll delete this copy. Otherwise, it's probably best to keep it up for people with this issue.
So basically, wipe data/cache/etc., flash the 7/4 CM7 release. Get that running, then reboot into recovery from CM7. Don't use the three-button method. Then wipe again, and flash the zip for whatever release you want.
mediafire.com/?u1n0wcqbwpuvts2
Download that file and flash that...it's how I got in to cm7 for the first time from eb01...if you are still on miui you can flash this with the blue recovery, wipe all and install
Sent from my SCH-I500 using XDA App
Many thanks to both your help! It has been of great assistance.
I downloaded the CM7 file posted, and will flash tomorrow. MIUI is running on it's first shot, and i'm entranced by it (for the time being).
However i am liking CM7 better, although both have many similarities
pmanliu said:
Many thanks to both your help! It has been of great assistance.
I downloaded the CM7 file posted, and will flash tomorrow. MIUI is running on it's first shot, and i'm entranced by it (for the time being).
However i am liking CM7 better, although both have many similarities
Click to expand...
Click to collapse
No problem, glad to help. If you end up flashing it, give us an update. Hopefully it'll work that way.
I used Cyanogenmod for a while back when I was more into stock ROMs. On different devices, though. It wasn't bad. But I flashed MIUI a few days ago and haven't looked back since. It's a great ROM. MIUI or CM7 is your choice, and I haven't used CM7 enough to say much about it, but MIUI has my full support. I never thought I'd switch from UKB so easily.
efan450 said:
Try it again and record your steps exactly and post them and I'll try and see what went wrong...it could just be a corrupt download of one of your files or just a simple missed step. What build are you on and what rom are you trying to go to?
Edit: this is what I have done multiple time without a hitch
regardless of what build and rom your on..
-pull your battery
-odin official vzw EB01 (pda button only..just a reminder) and the atlas
2.2 pit file and check the repartition box (I use odin v.1.7, but it shouldn't matter) and let odin do it's thing
-install battery and fully boot and let it sit for a minute our two after it loads
-pull battery
-odin recovery jt's 3-30 fix all... (found in nitsuj's sticky in the development section under recoveries)
-insert battery
immediately three finger boot into recovery and wipe everything
-flash newest cm7 build..I can't remember the date (I used the 7/4 build to get on to cm7 but it has been removed but the latest on will work)
-reboot fully
-use power button menu and select reboot..recovery to get to new blue recovery
-Flash newest cm7 build (if applicable), gapps and or mtd kernel if desired without wiping
-reboot, and enjoy cm7
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
So you never used jt's cm7 fix odin package?
Nope..I was able to go to cm7 with cwm3-30 fix all with no problem and I was able to go to it from otb's 3.x.x.x recovery...either way I've been back and fourth a few times but never had to use the 4.x.x.x. fixed recovery...maybe I'm just lucky but I know a few others have had success with those recoveries as well...you just flash it like normal...wipe everything and install the 7/17 build...reboot...and just make sure if you want to flash gapps or the glitch kernel you use the power button menu to reboot recovery...no three finger booting anymore.
Sent from my SCH-I500 using XDA App
Solution
pmanliu said:
Did that... just goes back into the bootloop from recovery => SAMSUNG => SAMSUNG/CM7 (not the skateborder screen) and gives me this errorr:
-- Installing
Finding update package
E: unknown value for path []
E: Can't mount
Installation aborted
Click to expand...
Click to collapse
I was getting the exact same thing.
Started after I flashed the glitch v12 kernel on top of nightly #29. No problems.
Then I used ROM Manager to download nightly #35
Rebooted into CWM 4.0.1.5 orange via power button
Navigated to CWM folder to find nightly #35 to install from zip
Selected to install, checked for BML/MTD, said complete, auto rebooted
Boot loop with the above quoted errors, never gets to skateboard logo
Tried adb solutions, not enough time to issue adb commands before reboot
three fingered into cwm4 dark blue, got the usual expected E: can't find errors
tried restoring nandroid backup, auto reboots, no change, same errors as in quote
three fingered into cwm4 dark blue, tried flashing nightly #35 from RM download, no change
3fgered back into cwm4 dblue, flashed nightly #29 from SD that I had previously direct downloaded from cm7 nightly website, phone checked bml/mtd status, auto-rebooted, completed install.
Phone booted up normal with cm7 kernel, nightly #29, Data had been wiped
Used power button to reboot into recovery 4.0.1.5 orange
restored nandroid backup, rebooted
all is good! bazinga.
What I've learned from this is that using ROM Manager to download nightlies is risky. It may work fine if you use ROM Manager to download, wipe, and install, but if it fails during any of those (which it seems to do frequently) you could be out of luck with a headache. Best practice seems to be to download nightly directly from the cm7 website or copy it from your computer to the SD card and reboot via the power button into recovery and install that known good copy you downloaded via the cm7 website in the browser or transfered from your computer to the SD card. ROM Manager does something weird. This has occurred to me 3 separate times with ROM manager and with different nightlies. Also, it is worth noting that jt does not support the Glitch kernel for use with CM7 nightlies and a lot of issues seem to stem from using it. It is amazing when it works, but seems to add a lot of risk. YMMV
Let me know if this has helped or if anyone has any questions. Sorry for it being long, just trying to be thorough as there was no info out there to help me when this happened so I hope I can be of help to someone else.
ok i used nvflash and reloaded the full stock nvflash with cwm 5504 beta 15. i used the directions from ray waldo's website using team drh's files. i've tried 3 different roms and they all get stuck at the 3 birds. i wipe the tablet data, cache, and dalvik, plus repartition to wipe the drive and set it at 2048-0m every time per the instructions. i feel like i haven't missed a thing but i must be. i can nvflash back to the stock roms all day long but as soon as i try ics it get stuck. sorry for the noob post, i've been trolling here for well over a year and have rooted my phones and other tablets with no real problems. any help would be greatly appreciated.
So you can flash back to the stock version. That's a good thing.
You've also put on the Clockwork (I'm assuming with touch) and I assume you can get into the recovery mode.
Have you tried the G-Harmony rom? http://forum.xda-developers.com/showthread.php?t=1645420
I loaded G-Harmony last weekend on my wife's GTab and it worked without a hitch. I know that you can't have ANY previous version on before you try to put on (probably any but at least G-Harmony ICS) ICS.
She took her tablet to work with her this morning so I don't have it here to actually walk through CWM. Since I'm a VERY old man, my memory is kind of spotty and I've eaten since last weekend but here's pretty much what I remember how I did it.
1) Loaded the new CWM (you've already done that)
2) Booted into stock.
3) Rebooted into recovery mode (power and +)
4) there is an option for mount/erase (if I remember correctly). I erased everything that didn't move out of the way.
5) did a wipe data/factory reset
6) wiped every cache that I could find.
7) loaded rom from sdcard
8) rebooted
that seemed to work. You also need to wait about 20 minutes (assuming it worked) for gapps to update.
You might try this and come back here to let me know how it went.
Good luck,
Gregwa
i'm not seeing an option for mount/erase. basically what i do is repartition and that wipes the drive. is that where i'm going wrong? also i'm using only the internal sd to load the g-harmony.
aso i just noticed when i go to wipe the dalvik i get E:unknown volume for path [/sd-ext]. before i even wipe it. is this normal?
That might be the issue. In addition, the missing partition may be another issue.
Did you look under Mounts & Storage (or something like that) near the bottom of the CWM screen?
I'll have to wait until my wife gets home tonight and pry the GTab out of her fingers (she's now addicted to pocket frogs) to get the complete menu items for you if you can't find it.
It's now 10:27am Mountain Time (USA). Try checking back (if you didn't find it) around 8pm Mountain time (9 central, 10 eastern (I sound like an ad for a tv show, huh?)) and I should have the steps for you then.
Gregwa
Ok. With the help of food and a 4 foot crowbar, I was able to get ahold of her gtab for 5 minutes.
The top level menu items of CWMR are:
- Reboot System Now
- Install Zip From SDCard
- Wipe Data / Factory Reset
- Wipe Cache Partition
- Backup and Restore
- Mounts and Storage
- Advanced
- Power Off
What we are interested in right now are Wipe Data/Factory Reset, Wipe Cache Partition, Mounts and Storage and Advanced.
So starting from stock with CWMR Touch 5.5.0.4 Beta 15
Wipe Data/Factory Reset
Wipe Cache Partition
Under Mounts and Storage
Format /boot
Format /cache
Format /sdcard
Format /emmc
Format /data
Format /system
Then mount each in menu order.
Under Advanced
Wipe Dalvik cache
Then install zip from where ever you placed it (usually internal sdcard)
That SHOULD work. As far as I remember that's what I did.
Let me know how it goes.
Gregwa
so in mounts a storage all the stuff listed mount or unmount should read mount? or change them all to unmount?
I BELIEVE the mount/unmount are status & command both. In order to format one of the "drives", you'll need to mount it first.
So yes, you will need to mount before you format.
i i need to format each and then go back and unmount and remount each?
its getting late (11:30) and the beer is starting to kick in. i'm still getting that unknown sd error and everytime i get the 3 birds. i'll have to start again in the morning. thanks for the help. hopefully i'll get it tomorrow.
Yes, it is getting late.
Give it a try tomorrow and I'll try to check in every once and a while.
still no luck. i've followed your install plus many others just to see. i can put it back to stock and that seems to be about it.
Have you tried a lower version rom like GCombover?
You might try that and see if that (at least) works.
Gregwa
i just reloaded the original 1.1 bootloader with nvflash. i then install a version of cm7 with no problems. it booted right signed in open the updated to play store. i'm wondering if the nvflash file for the 1.2 bl might be corrupt.
still no luck. i reloaded all the 1.2 bootloader stuff from the team drh thread and tried their version and still get stuck at 3 birds.
I think that the 1.2 bl is the issue. Since you can deal with a 1.1 rom with no problems, we need to focus that.
Let me do some research and I'll get back to you this evening.
Gregwa
---------- Post added at 10:03 AM ---------- Previous post was at 09:57 AM ----------
I wasn't sure I could find this so quickly.
Here's jamcar's guide to upgrading the 1.1 bl to the 1.2. Have you tried it?
http://forum.xda-developers.com/showthread.php?t=1397728
gregwa said:
I think that the 1.2 bl is the issue. Since you can deal with a 1.1 rom with no problems, we need to focus that.
Let me do some research and I'll get back to you this evening.
Gregwa
---------- Post added at 10:03 AM ---------- Previous post was at 09:57 AM ----------
I wasn't sure I could find this so quickly.
Here's jamcar's guide to upgrading the 1.1 bl to the 1.2. Have you tried it?
http://forum.xda-developers.com/showthread.php?t=1397728
Click to expand...
Click to collapse
man i just can't win. this didn't help either.
so it looks like you are stuck with a 1.1 bl rom.
Just for grins and giggles, try going to the GTabCombOver page http://forum.xda-developers.com/showthread.php?t=1424963 and download the 1.1 version of their rom. If it works, then we know you (for some reason) have to deal only with 1.1 version roms for a while. This is a Honeycomb 3.0.1 version and it worked quite well on my wife's GTab. This will get you closer to your goal until we can find a way to get you up to 1.2 BL for real.
One good thing about GTabCombover is that you don't have to deal with wiping everything for good. The instructions are clear and easy.
I'll keep my body parts crossed for you.
Gregwa
i successfully loaded GTabCombOver with out any glitches. it definitly has something to do with the 1.2 bootloader. i wiped it out again and tried the aokp ics rom and again i'm stuck at the birds. i need to get titanium back up installed so i can save my stuff on GTabCombOver while i'm figuring out the bootloader thing.
your probably not going to beleive this but i just got a version of ics to load and work with the 1.1 bootloader!!!! now i just have to see how stable it is.
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
nashdude said:
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
Click to expand...
Click to collapse
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
I ran into something similar when I tried installing CWM 6.x.x. I chickened out and decided to run CM10 from SD instead, and I'm so happy on the performance now that I do!
I did the "unbrick" thing with "repart.img" to get the Tablet back to "out of the box" state and sighed of relief when it worked!
Yeah, I was afraid of that. I really didn't wanna go through the process of unbricking, but I guess there's no help for it.
troy9829 said:
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
Click to expand...
Click to collapse
Power + 'n' doesn't work on my NT either, I have to turn the device off, insert the SD with CWM, then plug in the (still turned-off) NT to a wall charger and allow it to boot up that way - then (and only then) do I boot into recovery, and without touching any buttons. Hopefully that helps
Dang, whoever thought this would be such a booger of a deal?!?
Okay, first off, let me apologize for coming off like a noob, but it seems there's so much information out there that everything's kinda bleeding together, so let me tell you where I'm at.
I've unbricked and restored the NT to stock 1.4.2
I tried rooting, but the only root I can find that is flashable from SD is the 5.5 CWM which is older than the CWM 6.xxx that every CM10 version calls for. So I went ahead and did the root, so now I have a stock NT with root access. This is where I'm getting stuck...
I'm at this point...
http://forum.xda-developers.com/showthread.php?t=1640958&highlight=cwm+1+4+2
...and it apparently requires you to reboot into CWM in order to install CWM?!?
I've found the CWM 6+ files I think I need, but when I try to follow the instructions, my NT won't kick over into recovery---it keeps booting straight to the rooted 1.4.2 stock rom. I've found guides that take you from stock 1.4.3 to CM10, some that take you from 1.4.2 to root, and I even found Indirect's CM7 (without the instructions on how to get CWM on there in the first place!). I even downloaded Rom Manager and tried to boot into recovery that way, but it said there was my device wasn't supported.
I've been staring at this dang screen for three hours, trying to find a step by step, and I'm coming up empty. Maybe I'm just too frustrated at this point and need a breather.
What I need to know is how to install CWM 6+ on a NT that's either rooted or stock 1.4.2 (I still have the unbrick SD card) so that I can boot into CWM. From there, I can make my way through installing CM10. Help. Please. Am about to chew the lining out of my cheek.
I don't know if this might be helpful? http://forum.xda-developers.com/showthread.php?t=2037368
Sent from my NookColor using Tapatalk 2
Not yet. I was expecting OTA to kick in, updating my current 1.4.2 to 1.4.3, but it hasn't. Honestly starting to think my NT doesn't want to be rehacked LOL
Okay, so here's what I'm doing at the moment...
I'm at rooted stock. I moved CWM 6.0.1.2, CM10, and gapps over to internal SD.
I booted into recovery with an older version CWM SD card (SD card image with Win32 > turned off NT > insert SD > plug in USB to autoboot)
While in recovery (from SD), I flashed CWM 6.0.1.2 , CM10 (meghd00t), and gapps-jb-20121011.
I reboot...
WE HAVE JOY!
Now to check to see if the thing's gonna run right (got a whole lotta "XYZ has stopped" error messages upon boot up)
Dangit, keep getting those error messages about Gapps stopping and Google Play, and other stuff. Not allowing me to do hardly anything I need to. I can't even boot into recovery from the home page---it still loads straight to the Rom. In order to get into recovery, I need to use the SD that I made to get into recovery in the first place. Going to wipe dalvik and the other caches to see if that helps...
After wiping the caches, I boot into CM10 with no error messages. I DL'd a game from my Gmail account, and it appears to be working properly. Thanks for the suggestions and for letting me vent
I just went thru this similar ordeal too. It took me over 3 weeks to finally find a recovery & cm10 combo. What I found is that I couldn't get ANY version of twrp to act right. Indirect's flashing tool was invaluable. I finally used it to flash a cwm 6.x from Laverne's thread. It seems that not all versions of cwm 6.x are compatible with certain cm10 roms too & by chance I hit a combo that finally worked! I'm staying with what I got for a while!
Sent from my Nexus 7 using Tapatalk 2
Hey, guys, I made a mess.
A long time ago I decided to try out CyanogenMod for my S3 and then everything went well. I got it up and running and it was a cool ROM but I decided to stick to stock at that time. So I looked for a tutorial online and managed to get it back to stock 4.1 Android running well and as usual.
The issue I had then was that I couldn't update my phone from Google's servers anymore. Every time the phone tried to update the firmware I'd get an error, no matter if I tried it through Kies, the phone or whatever. So I decided I'd just install a ROM for a more recent version.
I found a post on a tech blog here in Brazil saying that OmniROM promised they finally had a somewhat stable version of KitKat 4.4
I went on to install it to then find a beautiful, but still very glitchy ROM. My phone froze all the time and it was starting to bother me. My initial plan was to stick to it until it got better, get the daily updates and stuff, but my phone was way too unstable for that too. So I said to myself: "Okay, no problem, so let's get a stable ROM on this little guy."
I downloaded PA 4.3 and proceeded to get it on my phone. That's when the issues started happening. I couldn't find the .zip from CWM no matter where I put it, and my sdcard1 was full because of the previous backup I created (there was a problem with that too, MD5 mismatch, but I didn't lose anything important so that's okay).
Then I did something even more stupid. I figured, why not clean up the backup and get the .zip there, so maybe it'll show up? At that point the sdcard0 (internal storage) was all different and I couldn't find the .zip for the OmniROM, but when I was on CWM it showed up instead of PA's. The problem with that is that I somehow wiped out CWM and now I can't get to recovery. If I boot up my cellphone through OmniROM, it loads up fine but I can't download the ROM Manager or the superuser from the Play Store. I'm trapped with OmniROM and it's working even less well than at first.
What should I do? Is there a way back from this? I'd really like to have my phone running again soon, I need it to keep in touch with my parents since my grandma died recently.
Thank you in advance.
EDIT: Okay, some progress. I remembered that I got CWM on the phone through Odin and went through that again. I have CWM back but still, my internal storage fails to recognize the new .zip files and only shows OmniROM's. The folder is completely different when I connect the phone to my computer. I got to see the .zip files at the sdcard1 but CWM says they're bad files. I'll trust it and redownload/transfer again. We'll see what happens.
EDIT 2: Trapped again. Can't find anything on Google. It sure sucks to be me. I can't even figure out how to get everything back to stock so I can try again. Tried turning USB debugging off but it didn't make a difference. The CWM shows me the two OmniROM .zip files and my computer shows me the PA .zip files. I'm just...
first- try to flash newer cwm based recovey. I suggest philz (is has both Odin / cwm based install):
http://forum.xda-developers.com/showthread.php?t=2002953
after flashing is complete- try to download this rom:
http://forum.xda-developers.com/showthread.php?t=2060403
and check if you can see it.
(you can put it in your internal or external sd, philz can access them both)
Before installing the new rom, I strongly recommend doing a 'wipe to istall new rom', cache wipe and delvik.
good luck
Sent from my GT-I9300 using Tapatalk
Yay, thank you! I'm not trapped anymore. The PA rom I downloaded is still "bad", but that's probably its own fault. I'll wait until NeatROM's download is complete and try with that. I'll edit this if things turn out well.
Thanks again!
EDIT: So, I tried with NeatROM and it also says it's bad. But I only tried on the external storage, so maybe that could be it. My sdcard has been returning some really funky errors when I get it on my computer so I'm worried it might be a bit compromised (and I actually found it at a bus terminal, so it never really worked properly even after formatting).
Thing is when I did the wipe I picked the option that wipes it for a new ROM, so OmniROM is gone. Is there a way to get USB connection through CWM so that I can transfer NeatROM to the internal storage? I only have this one sdcard.
EDIT 2: Finally got it! Thanks so much, amirTor, my S3 is back on track! The sdcard was the bad one, not the file. But the PA ROM didn't work anyway. I might stick to NeatROM or maybe look later. I'm gonna take a week off of all this after so much trouble.
Glad I could help (even though it seems that you pretty much helped yourself...)
1)If you got Sandisk SD card, make sure to follow my post on thread: http://forum.xda-developers.com/showthread.php?t=2614170
2)You can mount your phone to be shown in your pc even when in recovery mode: Mounts and storage-> moun usb mass storage
3)You should definitely stick with neat- the best stock (and aosp) rom there is :good::good::good:
ps- hitting the 'thanks' button will be appreciated :angel:
Done and done!
So, maybe someone can help me out here. I wanted to install Kit Kat Killer. This is what happens:
Rooting Process
1. I used Odin to install the root automatically.
2. I verified the root.
3. SuperUser and BusyBox installed.
4. Used Odin to install TWRP.
Recovery
1. Booted into TWRP.
2. Accidentally forgot to Nandroid Backup.
3. Wiped internal data, wiped everything else except SD Card.
4. Went to install Kit Kat Killer. Got some failed messages about some usb folder being unable to be mounted.
5. Rebooted phone. Re-downloaded everything and moved to SD.
6. Still fails.
Google time...
1. Downloaded some files from the links/forums I came across. None of these two files will flash through Odin, saying FAIL!
a. N900PVPUBMJ4_N900PSPTBMJ4_N900PVPUBMJ4_HOME.tar
b. N900PVPUBMI3_N900PSPTBMI3_N900PVPUBMI3_HOME.tar
2. TWRP can't be added through ODIN anymore as far as I know. I was using version
Now...
1. TWRP is gone.
2. Phone is stuck in "ODIN MODE" for recovery (?).
3. I can't get past the Samsung Galaxy Note 3 screen.
4. When I get the yellow triangle about needing Kies3 for an emergency firmware repair, it does NOT recognize my phone. Yes, I am using Kies 3. It says I am using an unsupported phone.
5. It does say SW REV CHECK FAIL.
I am at a total loss here. I know it's a soft brick, but for the life of me, I can not figure out what to do next.
Thanks for all your help!!
Just got it back into TWRP mode. It keeps saying:
"E: Unable to mount /usbstorage"
Then when it tries to install KitKatKiller, it checks for the MD5 (on the SD too in the same directory), it says FAIL. I think this whole issue is based on the usbstorage thing.
Right now, I am going to download the latest Sprint stock ROM and see if I can flash it in TWRP. This will take at least 50 minutes to get going (30 for download/20 for file transfer). So plenty of time for you guys to jump in and say otherwise
Really, I appreciate all of your help!!! I am sure I made a n00b mistake. I had no real problems with my GSIII or EVO 4G once I got the hang of things
I think you guys can close this thread. I am not sure what the hell happened, but I wiped my SD card after copying the KitKatKiller ROM to another folder on the internal SD. I had forgotten to include the MD5 file in the same folder as well, but it finally installed. Right now, the phone is showing KitKatKiller logo spinning and booting up, so I presume the phone will be fine from this point, and if not, I will use Kies 3 to return it to stock and give it a try again. Again, you can close this thread, I feel like an idiot but it all worked out for some odd reason. I'm still not sure why I was getting "unable to mount usbstorage" errors.
Thanks again for everyone taking a look!!!!!!
jacobmiw said:
I think you guys can close this thread. I am not sure what the hell happened, but I wiped my SD card after copying the KitKatKiller ROM to another folder on the internal SD. I had forgotten to include the MD5 file in the same folder as well, but it finally installed. Right now, the phone is showing KitKatKiller logo spinning and booting up, so I presume the phone will be fine from this point, and if not, I will use Kies 3 to return it to stock and give it a try again. Again, you can close this thread, I feel like an idiot but it all worked out for some odd reason. I'm still not sure why I was getting "unable to mount usbstorage" errors.
Thanks again for everyone taking a look!!!!!!
Click to expand...
Click to collapse
Glad you figured your issues out. Just popped into tell you that twrp fails mounting USB because it's looking for an external USB. Not to worry its supposed to fail unless you have a USB drive plugged in through an otg cable.