I can't seem to flash CM7 on my Fascinate. I've downloaded the right recovery, and wiped data and dalvik, but it keeps looping to a new recovery screen and getting stuck at "waiting for SD card to mount" and counts down then reboots and tries it again. I've odined several times back to stock but to no avail.
time for a new sd card...class 6 or higher preferably.
droidstyle said:
time for a new sd card...class 6 or higher preferably.
Click to expand...
Click to collapse
Lol I'm using a class 10
Sent from my SCH-I500 using Tapatalk 2
swbf2lord said:
Lol I'm using a class 10
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
LOL... if you would post more information with your questions then you would get better answers
fwiw you dont need to wipe dalvik if you wipe data...the data wipe does all three
also sometimes you need to flash cm7 twice for it to stick
and there is a guide in the general section for flashing instructions...refer to section 3
droidstyle said:
LOL... if you would post more information with your questions then you would get better answers
fwiw you dont need to wipe dalvik if you wipe data...the data wipe does all three
also sometimes you need to flash cm7 twice for it to stick
and there is a guide in the general section for flashing instructions...refer to section 3
Click to expand...
Click to collapse
Honestly I didn't think it was important. I can't flash it twice though because it automatically goes to the boot logo after I flash.
Sent from my SCH-I500 using Tapatalk 2
swbf2lord said:
Honestly I didn't think it was important. I can't flash it twice though because it automatically goes to the boot logo after I flash.
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
cm7 has known to be finicky with certain sd cards. Normally anything class 6 or higher has no known issues, but that does not mean much. Fwiw I had a stock 16gb that always gave me fits trying to flash cm7...Sometimes it would take 15 tries before it would boot up.
You might try reformatting the sdcard or swapping in a different one aswell.
droidstyle said:
cm7 has known to be finicky with certain sd cards. Normally anything class 6 or higher has no known issues, but that does not mean much. Fwiw I had a stock 16gb that always gave me fits trying to flash cm7...Sometimes it would take 15 tries before it would boot up.
You might try reformatting the sdcard or swapping in a different one aswell.
Click to expand...
Click to collapse
Okay, thanks, I'll try another one
Argh! I got it to flash CM7, and it goes to the Cyanogenmod Galaxy S screen, but then it loops to the SD card screen, and says something about a file not being found, reboots, then starts the process all over again.
I also could not get CM7 to flash. I would restore to stock if I were you. And format SD card.
MultipleMonomials said:
I also could not get CM7 to flash. I would restore to stock if I were you. And format SD card.
Click to expand...
Click to collapse
I did both, even tried a new sd
Sent from my SCH-I500 using Tapatalk 2
did you try flashing THS build 1?
MultipleMonomials said:
did you try flashing THS build 1?
Click to expand...
Click to collapse
For CM7? No. Can you link me?
Sent from my SCH-I500 using Tapatalk 2
It may make no difference, but I've had various makes of microsd cards over the years and have had issues with all of some kind. Bought a Samsung class 6 16gb and have had zero, absolutely zero issues.
Look in Droidstyle's guide.
I can't seem to find it.
EDIT: Nvm, I found it, but the THS build isn't for CM7 according to the guide.
No, THS is a CM9 build. I would go with CM9 as I have had far fewer problems with it and ICS is better in general.
MultipleMonomials said:
No, THS is a CM9 build. I would go with CM9 as I have had far fewer problems with it and ICS is better in general.
Click to expand...
Click to collapse
Yeah I'm running AOKP right now. I want to run CM7 though, not ICS. That's the whole point of the thread.
Sent from my SCH-I500 using Tapatalk 2
Oh. Sorry. I thought you were coming from stock.
MultipleMonomials said:
Oh. Sorry. I thought you were coming from stock.
Click to expand...
Click to collapse
It's okay, thanks though.
Sent from my SCH-I500 using Tapatalk 2
Related
This thread is for anyone/everyone with questions or problems with jokers CM9 or the ICS-MIUI that spleef/the_bill have been working on. The point is to try to clean up the Dev thread with the repeated questions/problems.
Here is the main thread:
http://forum.xda-developers.com/showthread.php?t=1413349
[Ics] cm9 beta with camera CDMA/GSM/UMTS/HSDPA/WCDMA/roaming 3/10/12
And here is the fixes and mods thread:
http://forum.xda-developers.com/showthread.php?t=1514963
Photon CM9/MIUI V4 Fixes and Mods
sent from my MIUI MoPho
So my unicorn won't crap rainbows. I fed it fruit loops and all it crapped was at most like three colors. Glitter is funny because it farts sparkles but the sparkles won't boot.
Ideas?
It'd be nice if moto would like sneak out some unicorn food.
Sent from my MB855 using XDA
How's this for a noob/newb question?
So I'm using a Photon 4G, which is on SBF 198_7, is rooted and unlocked (obviously), and for some reason absolutely refuses to boot the CM9 Beta. Currently I'm flashing 0.3.3 but previous attempts with .4 had the same result. I follow the instructions step for step (meaning I format system, cache, and data as well as perform a factory reset in CWM (running 5.0.2.7-photon3, although I've also tried the newest of the versions posted by Jokersax). When I install and reboot the phone sits on the red circle screen.
My logcat says:
exec '/system/bin/sh' failed: No such file or directory (2)
which to me is saying that /system may not be mounted at all.... I've read the CWM 5.0.2.8 has this problem but not with 5.0.2.7. Any ideas on what I should try to get past this issue?
Thanks!
maarekelets said:
So I'm using a Photon 4G, which is on SBF 198_7, is rooted and unlocked (obviously), and for some reason absolutely refuses to boot the CM9 Beta. Currently I'm flashing 0.3.3 but previous attempts with .4 had the same result. I follow the instructions step for step (meaning I format system, cache, and data as well as perform a factory reset in CWM (running 5.0.2.7-photon3, although I've also tried the newest of the versions posted by Jokersax). When I install and reboot the phone sits on the red circle screen.
My logcat says:
exec '/system/bin/sh' failed: No such file or directory (2)
which to me is saying that /system may not be mounted at all.... I've read the CWM 5.0.2.8 has this problem but not with 5.0.2.7. Any ideas on what I should try to get past this issue?
Thanks!
Click to expand...
Click to collapse
jokersax11 said:
Or just flash the rom twice
Sent from my MB855 using XDA
Click to expand...
Click to collapse
Try this first, of course.
If no worky, then this miggghhhtt:
This are the steps to be able to boot into 4.0:
1. Wipe everything as usual in CWM by Joker
2. Flash 0.3.1 and only 0.3.1
3. Reboot, into 0.3.1
4. Let it sit for 1 minute, mess around in it for that time.
5. Reboot into Recovery(CWM by Joker).
6. Flash 0.4.0, gapps and or the usual.
7. You can now reboot into it.
Or just flash the rom twice
Sent from my MB855 using XDA
jokersax11 said:
Or just flash the rom twice
Sent from my MB855 using XDA
Click to expand...
Click to collapse
The issue comes from wiping system
Sent from my MB855 using XDA
Thank You for that. It's booting now.
Curious, but what magic is performed on the 2nd flash that makes it bootable?
---------- Post added at 01:38 AM ---------- Previous post was at 01:27 AM ----------
jokersax11 said:
The issue comes from wiping system
Sent from my MB855 using XDA
Click to expand...
Click to collapse
Since the instructions for coming from another rom says to format system, should the OP on the dev thread mention the double flash issue or is this something that doesn't happen that often?
maarekelets said:
Thank You for that. It's booting now.
Curious, but what magic is performed on the 2nd flash that makes it bootable?
---------- Post added at 01:38 AM ---------- Previous post was at 01:27 AM ----------
Since the instructions for coming from another rom says to format system, should the OP on the dev thread mention the double flash issue or is this something that doesn't happen that often?
Click to expand...
Click to collapse
I'll update the op soon enough. However a proper update script is better in the long run
Sent from my MB855 using XDA
How necessary is jokers cwm? I've been using it for ages but it doesn't read my sdcard so I have to copy everything from SD to emmc . Been too lazy to go back to romracers and try it out but with the output of cm9 and miui builds I find myself rebooting out of recovery due to forgetting to move files quite often
Sent from my MB855 using XDA
thatguy07 said:
How necessary is jokers cwm? I've been using it for ages but it doesn't read my sdcard so I have to copy everything from SD to emmc . Been too lazy to go back to romracers and try it out but with the output of cm9 and miui builds I find myself rebooting out of recovery due to forgetting to move files quite often
Sent from my MB855 using XDA
Click to expand...
Click to collapse
Those recoveries are made every time I build. I need to make a specific recovery update thats got everything working
Sent from my MB855 using XDA
thatguy07 said:
How necessary is jokers cwm? I've been using it for ages but it doesn't read my sdcard so I have to copy everything from SD to emmc . Been too lazy to go back to romracers and try it out but with the output of cm9 and miui builds I find myself rebooting out of recovery due to forgetting to move files quite often
Sent from my MB855 using XDA
Click to expand...
Click to collapse
I've been using jokers cwm and everything is on my sd card. It reads it just fine. I have the newer v3 recovery. Once I choose install zip it gives me the menu for either sd card or internal, along with "update". I would use jokers recovery just cause it seems to work :beer:
sent from my MIUI MoPho
bullfrog527 said:
I've been using jokers cwm and everything is on my sd card. It reads it just fine. I have the newer v3 recovery. Once I choose install zip it gives me the menu for either sd card or internal, along with "update". I would use jokers recovery just cause it seems to work :beer:
sent from my MIUI MoPho
Click to expand...
Click to collapse
Odd. Can't imagine why it won't read mine. I've just tried v2 and v3. Several downloads and flashes of each.
No dice
I've also tried ext3 and ext4 sdcard.
Wonder if its because they are partitioned?
Its really not that big of a deal , just a few extra steps for me.
Edit : I take that back, it is kinda a big deal as nandroid won't work due to not being able to read my sdcard.
Sent from my MB855 using XDA
that is weird, maybe it is because you card is partitioned. You might want to try a different card or format your existing. I usually do that every month or so, just to clean it up
sent from my MIUI MoPho
So i installed 0.3.2 on Friday and i corrupted it somehow by restoring all my CM 7 apps and data with TB. Oh well live and learn. This am i see now there is 0.4 and a new CWM. Argh i cant keep up! You da man joker. Gotta read up on the 0.4.0 install. Thanks.
bullfrog527 said:
that is weird, maybe it is because you card is partitioned. You might want to try a different card or format your existing. I usually do that every month or so, just to clean it up
sent from my MIUI MoPho
Click to expand...
Click to collapse
well its not the fact that my sdcard is partitioned. I tried a new one, fresh download of v3 and multiple flashes. Still wont read them. Going back to romracer for now.
Its the oddest thing...
Sent from my MB855 using XDA
Huh, I'm all out of ideas bro. Sorry
sent from my MIUI MoPho
If yours won't boot..
This has been a similar issue for me on .4 and the version before.
If it seems like you followed the instructions but you are still stuck at the motorola dual core screen try installing one of these kernels. http://forum.xda-developers.com/showthread.php?t=1520417
They are at the bottom of the post and I used the 1.0 ghz one.
It solved the problem both times for me! Idk if Jokers' CM9 comes with a kernel or if you are supposed to track one down but this worked for me ..
OK a couple things with CM9 0.4.0 i'm noticing. These may or may not be known. Camcorder lags badly and then crashes everything. No macro option in the camera. Also, is there a way in ICS to have USB storage enabled by default when connecting to computer as it is in GB?
jbb2388 said:
OK a couple things with CM9 0.4.0 i'm noticing. These may or may not be known. Camcorder lags badly and then crashes everything. No macro option in the camera. Also, is there a way in ICS to have USB storage enabled by default when connecting to computer as it is in GB?
Click to expand...
Click to collapse
the camcorder is a known issue, and i dont know about the usb. i dont use it much. i use wifi file explorer to move anything i need to my phone.
OK thanks. Sucks that you need 3 keystrokes to turn usb on. Another thing I'm noticing is that once the phone goes to sleep the backlighting on the soft keys does not come back on. I wish i was smart as the devs to help with this stuff. I don't wanna sound like i'm complaining. Just making some bugs known.
Hi all,
So I have been using CM9 since 00 and havent had a problem. This morning I go to turn on my Nook and I can't get past the Cyanoboot screen. Basically it just reboots back into the "n" screen 9 times before it spits me into recovery. The only thing I have tried to do so far is wipe user data and re-install CM9, but I have had no luck.
Any thoughts? Thanks.
Which version are you flashing? If its not the latest, .03, then this it may have expired.
Sent from my Xoom using Tapatalk
I have been trying to flash .02
I'll try to flash the most recent release right now.
Thanks.
Success! That worked. Thanks so much.
I've experienced this as well when a new CM9 build is released. Flashing the newest CM9 has fixed the problem and it boots right up.
CM9 self-flashing back to stock
So when cm9 alpha expires it just becomes unable to boot?
I ask because I went to bed last night with a working cm9 0.02, and woke up with stock nook 1.4.2; even cynogenboot has been removed from the sdcard
Little bit confused and possibly freaked out if this was BN's doing.
Oh well, time to try alpha 0.03 with kernel 3 I guess
danstiner said:
So when cm9 alpha expires it just becomes unable to boot?
I ask because I went to bed last night with a working cm9 0.02, and woke up with stock nook 1.4.2; even cynogenboot has been removed from the sdcard
Little bit confused and possibly freaked out if this was BN's doing.
Oh well, time to try alpha 0.03 with kernel 3 I guess
Click to expand...
Click to collapse
Not sure why you ended up with stock ROM, but it looks like the old build did expire. Try reflashing the .03 build.
Solar.Plexus said:
Not sure why you ended up with stock ROM, but it looks like the old build did expire. Try reflashing the .03 build.
Click to expand...
Click to collapse
Thanks, I'm working on it, but somehow clockworkmod got wiped from the sdcard as well.
danstiner said:
Thanks, I'm working on it, but somehow clockworkmod got wiped from the sdcard as well.
Click to expand...
Click to collapse
hmmm... imho the senior devs should speak up about this matter.
danstiner said:
Thanks, I'm working on it, but somehow clockworkmod got wiped from the sdcard as well.
Click to expand...
Click to collapse
Nothing should have been erased from your SD card. Are you sure you didn't format your card by accident?
Solar.Plexus said:
Nothing should have been erased from your SD card. Are you sure you didn't format your card by accident?
Click to expand...
Click to collapse
Very sure because my titanium pro backups and all other data was still there. It is possible that I wiped the recovery files from the sdcard sometime previously while cm9 was working.
However, my main worry is that I can't even get it to boot to cyanoboot so I can install alpha .03. I'll probably post on the thread I was using to make the sdcard (http://forum.xda-developers.com/showthread.php?t=1562130), but the normal re-partition, mark as active/bootable and copy in the files from meghd00t doesn't seem to be working.
Thanks for the help so far.
old_fart said:
hmmm... imho the senior devs should speak up about this matter.
Click to expand...
Click to collapse
No they shouldn't. The devs of cm9 say it expires in their thread. They say they will provide no support. It is marked as a development rom for a reason.
Sent from my Xoom using Tapatalk
Cubanluke88 said:
No they shouldn't. The devs of cm9 say it expires in their thread. They say they will provide no support. It is marked as a development rom for a reason.
Click to expand...
Click to collapse
spoken like a true . . . twenty first century man.
danstiner said:
Very sure because my titanium pro backups and all other data was still there. It is possible that I wiped the recovery files from the sdcard sometime previously while cm9 was working.
However, my main worry is that I can't even get it to boot to cyanoboot so I can install alpha .03. I'll probably post on the thread I was using to make the sdcard (http://forum.xda-developers.com/showthread.php?t=1562130), but the normal re-partition, mark as active/bootable and copy in the files from meghd00t doesn't seem to be working.
Thanks for the help so far.
Click to expand...
Click to collapse
I'm a little confused. Even if you can't get to Cyanoboot, you can still make a bootable CWM SD card and flash .03 from there.
Cubanluke88 said:
No they shouldn't. The devs of cm9 say it expires in their thread. They say they will provide no support. It is marked as a development rom for a reason.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Yeah, I agree with this. This ROM and even Fattire's great Cyanoboot is bound to have a for issues. That's why these forums and all these users are around here, to allow users to ask the community and help each other to learn about a device.
Cubanluke88 said:
No they shouldn't. The devs of cm9 say it expires in their thread. They say they will provide no support. It is marked as a development rom for a reason.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Agreed, I love this rom and miss having it already, but it is early alpha. Some kind of warning / countdown might be nice, but I'd much rather that effort keep being put into a working kernel 3
Maybe I partitioned wrong for cynoboot, going to try again.
---------- Post added at 01:21 PM ---------- Previous post was at 01:13 PM ----------
Solar.Plexus said:
I'm a little confused. Even if you can't get to Cyanoboot, you can still make a bootable CWM SD card and flash .03 from there.
Click to expand...
Click to collapse
Good point. I got CWM to boot so it shouldn't be more than a few minutes before I have alpha .03, and can install kindle app, and get back to reading my textbooks for finals tomorrow.
Sorry about that, a bit frazzled at this point in the semester. Thanks for all the help, I'll try and figure things out if this weird flashing back to stock happens again when .03 expires
danstiner said:
Sorry about that, a bit frazzled at this point in the semester. Thanks for all the help, I'll try and figure things out if this weird flashing back to stock happens again when .03 expires
Click to expand...
Click to collapse
I completely understand. Haha, I have 3 finals tomorrow morning and here I am sitting on the forums when I should definitely be preparing.
Just thought I'd let you all know. It's an old dog new tricks thing but I'm more comfortable with Koush.
6.0.3.2 both versions.
http://www.clockworkmod.com/rommanager
I saw this and was excited to see it since CWM/Rom Manager is what I am most comfortable with. The only concern I have is the "loki" issue that is used to get past the locked boot loader since they don't really say thet are using the loki method or not. Just wondering what the status of that is.
Also still squimish about flashing custom roms since my first try on this phone lead to a soft brick "custom unlocked" screen when i used TWRP.
They are using Loki.
Sent from my SCH-I545 using xda app-developers app
I just attempted this from my rooted s4 which had twrp on it.. and it worked!!! YAY!!
nice
Its awesome this is available for the S4 now. Always great to have options, but I think I will stick with TWRP for now. :fingers-crossed:
It's been so long since I have used CWM I don't know what the interface looks like now, lol. TWRP got so far ahead of them interface wise there was never a reason to go back on any of my other devices (TBolt, N7, KF). I may try it now just to try it. Plus I guess ROM control has a poor man's version of 4EXT's kernel control if I am not mistaken.
worked like a champ for me
Going to be tough to leave twrp
Sent from my SCH-I545 using Tapatalk 2
twp works with my 64gb microsd where cw I would have had to format to a fat32. Sticking with twp for sure.
balaams_ass said:
Just thought I'd let you all know. It's an old dog new tricks thing but I'm more comfortable with Koush.
6.0.3.2 both versions.
http://www.clockworkmod.com/rommanager
Click to expand...
Click to collapse
How are you guys installing the touch .IMG? I assume we can't boot fastboot and install from there..
Sent from my SCH-I545 using xda premium
zeroxg4 said:
How are you guys installing the touch .IMG? I assume we can't boot fastboot and install from there..
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
You install it from within ROM manager...it's an in app purchase
Sent from my Nexus 7 using xda premium
brizey said:
You install it from within ROM manager...it's an in app purchase
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Its offered as either and in app purchase or download from the link / post that I quoted...
Sent from my SCH-I545 using xda premium
Is that the same one as the in app purchase?
Sent from my SCH-I545 using Tapatalk 2
I had to leave twrp, I rebooted into recovery from touchwiz to install beans2 and I went into a boot loop. I made a backup, wiped everything and the install failed. So I tried to restore my backup and that failed. So I tried another backup and that too failed. I ended up having to Odin to stock so I installed CWR and so far so good. It was weird. I've been flashing since the of droid and I've had 15 different android phones since then and I've never had that happen. Oh well, I had titanium backups of everything and a backup of all mg text so I'm good now....
Sent from my SCH-I545 using Tapatalk 2
smalltownbird said:
I had to leave twrp, I rebooted into recovery from touchwiz to install beans2 and I went into a boot loop. I made a backup, wiped everything and the install failed. So I tried to restore my backup and that failed. So I tried another backup and that too failed. I ended up having to Odin to stock so I installed CWR and so far so good. It was weird. I've been flashing since the of droid and I've had 15 different android phones since then and I've never had that happen. Oh well, I had titanium backups of everything and a backup of all mg text so I'm good now....
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
I played out this almost IDENTICAL SCENARIO Friday on my S4 using TWRP. searching forums while trying to get back up and running led me to believe that TW had some issues in this regard....
Went to CWM and have been flashing without problem since. It's a shame, the interface on TW was STELLAR....
bkrickles said:
Is that the same one as the in app purchase?
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Yeah
I've just read somewhere in the last day or so that there was an issue with TWRP 2.5.0.3. that was causing issues. They were saying to go back to 2.5.0.2. and that will fix any issues you are having. I didn't update to .3, been on .2 since root & LOKI bypass without any problems at all. Just thought I'd throw that out there for anyone who hasn't heard about it.
Sent from my SCH-I545 using xda app-developers app
gsxcorey said:
twp works with my 64gb microsd where cw I would have had to format to a fat32. Sticking with twp for sure.
Click to expand...
Click to collapse
In the change log for version 2.4.4.0 it says "Update exFAT to latest commits". Does this mean you can Backup to extFat 64GB MicroSDXC memory cards?
DarkMenace said:
In the change log for version 2.4.4.0 it says "Update exFAT to latest commits". Does this mean you can Backup to extFat 64GB MicroSDXC memory cards?
Click to expand...
Click to collapse
I think so...not sure how they got the proprietary binaries.
You can use 64 GB cards in CWM if you format to fat32. I just formatted my card to fat32 and rest easy that pretty much anything ever made can read it.
Everyone has this thing where fat32 can't do 64 GB cards and that is simply not true. Windows won't do it natively but there are other format tools that will. The 32 in fat32 is not 32 GB, its 32 bits as in able to address 4 GB. So files are limited to 4 GB. That's why all the recoveries are breaking up the big repositories into volumes, so they don't exceed 4 GB. That 4 GB limitation is an issue for recording HD video...and that's about it.
edit: by the way, not saying you did not realize that...I got your question...just wanted to get that out there.
when i was doing my things in odin i forgot to flash the GBBootloaders.tar but CWM and Helly Bean flashed just fine. Am i going to need it? Should i flash it? Will flashing it cause a data wipe or bootloop?
skepticmisfit said:
when i was doing my things in odin i forgot to flash the GBBootloaders.tar but CWM and Helly Bean flashed just fine. Am i going to need it? Should i flash it? Will flashing it cause a data wipe or bootloop?
Click to expand...
Click to collapse
Sure u can do it now, should not cause any problems,,, no it won't wipe any data as far as i know.
hhp_211 said:
Sure u can do it now, should not cause any problems,,, no it won't wipe any data as far as i know.
Click to expand...
Click to collapse
but do i really need it?
skepticmisfit said:
but do i really need it?
Click to expand...
Click to collapse
Yes
BL - Bootloader - a.k.a. Boot Loader - This is the rudimentary software that kicks in when a phone is first powered up. Its only real goal is to get the operating system up and running. Some phones, like those from Motorola, have a "locked" bootloader, making it more difficult to use custom kernels. The Fascinate's bootloader was never locked. Here's where it gets complicated: bootloaders are broken down by Android version. There are Eclair bootloaders, Froyo bootloaders, and GB bootloaders. Just being on one version of Android, though, does not mean that you have the corresponding bootloader. It seems that stock Gingerbread phones don't use a Gingerbread bootloader. In fact, to put a GB bootloader on your phone (highly recommended for modern ROMs) you will need to flash a GB bootloader file.
skepticmisfit said:
but do i really need it?
Click to expand...
Click to collapse
These guys may know more than I do. But I've had my fascinates since we got the gingerbread OTA. And ive never flashed bootloader to it. I've been on damn near every android version except 4.3 and never had any issues
Sent from my VS920 4G using Tapatalk
bones420la said:
These guys may know more than I do. But I've had my fascinates since we got the gingerbread OTA. And ive never flashed bootloader to it. I've been on damn near every android version except 4.3 and never had any issues
Sent from my VS920 4G using Tapatalk
Click to expand...
Click to collapse
i ended up doing it. the only difference is the second boot logo shows up (the one after the first samsung logo).
my verdict is, if you forget to flash it initially with JT's CWM, you should be fine. flash it with JT's CWM image for best results.
I'm happy with my setup. Geewiz runs beautiful for me. Would love to try 4.3 but SD card won't let me. Just flashed bootloader on my bad cracked fassy and still no luck with the SD card. So. Its useless for me
Sent from my VS920 4G using Tapatalk
bones420la said:
I'm happy with my setup. Geewiz runs beautiful for me. Would love to try 4.3 but SD card won't let me. Just flashed bootloader on my bad cracked fassy and still no luck with the SD card. So. Its useless for me
Sent from my VS920 4G using Tapatalk
Click to expand...
Click to collapse
what kind of SD card is it?
Sandisk 16gb class 4. I've formatted it every way possible. And any mtd ROM puts me in a recovery loop. "Waiting for SD to mount"
Sent from my VS920 4G using Tapatalk
bones420la said:
Sandisk 16gb class 4. I've formatted it every way possible. And any mtd ROM puts me in a recovery loop. "Waiting for SD to mount"
Sent from my VS920 4G using Tapatalk
Click to expand...
Click to collapse
you tried a different SD card to make sure it's not the phone?
Yeah stock Samsung 16gb worked perfect. But someone stole it out my spare phone.
Sent from my VS920 4G using Tapatalk
---------- Post added at 08:44 PM ---------- Previous post was at 08:41 PM ----------
I've got 3 of the 16gb class 4 sandisks. And they all do the same. Unfortunately I believe its a fascinate problem. All the cards work perfect in lg spectrum, droid eris, and HTC touch pro 2 with nand android
Sent from my VS920 4G using Tapatalk
So the problem started when I flashed a 4.3 rom last friday. I formatted my internal memory in recovery mode because for some reason I only had 4 gigs of space and had moved everything over to the sd card. Once that was done phone said like 8 gigs available and thought everything was fixed. Well now if I turn off my phone it gets stuck in some kind of bootloop but it's not looping. It's just sits at the Samsung unlock symbol and custom screen. Doesn't loop just sits there. So one day I decided to format the internal memory again and the phone boots up like normal, but I can't power off the phone without going into recovery and formatting the internal memory every time. Any ideas on what is causing it or how I can make the Samsung custom boot stock instead so I can send it out.
I also have tried flashing another 4.3 rom and it doesn't seem to go away either.
I'm not an expert on how they have to make this stuff work with the mdk bootloader but I'm sure it's not hardware related. Have you tried flashing back to a 4.2 rom?
Sent from my SCH-I545 using Tapatalk 2
Downloading one now hopefully it will fix it.
Which recovery are you using? Make sure to wipe data, cache, and dalvik 3x each, then flash your rom
Sent from my SCH-I545 using Tapatalk 2
TWRP and I flashed hyperdrive still no luck still freezing in the same spot and have to actually format to get past it.
Anyone else have any idea on what else I can try?
BlackDynomitr said:
Anyone else have any idea on what else I can try?
Click to expand...
Click to collapse
What version of TWRP are you using?
Sent from my SCH-I545 using Tapatalk
I believe 2.5 I'm guessing only way to check is to go into recovery again.
BlackDynomitr said:
I believe 2.5 I'm guessing only way to check is to go into recovery again.
Click to expand...
Click to collapse
Yep that's the only one I've never had any issues with. TWRP 2.5.0.2
Edit: If your still having issues you could always Odin back with Stock firmware and get a clean start. I know its a pain lol
Sent from my SCH-I545 using Tapatalk
heath2805 said:
Yep that's the only one I've never had any issues with. TWRP 2.5.0.2
Edit: If your still having issues you could always Odin back with Stock firmware and get a clean start. I know its a pain lol
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Well I think that might work only thing I'm afraid is what if it doesn't turn on.
BlackDynomitr said:
Well I think that might work only thing I'm afraid is what if it doesn't turn on.
Click to expand...
Click to collapse
Well if it doesn't turn on after flashing stock firmware via Odin, you'll know its a hardware issue with it and your warranty should cover a new replacement.
Sent from my SCH-I545 using Tapatalk
I had this issue when I first got my phone. I bought it off Swappa, it was already running TWRP 2.5.0.2, giving me nothing but problems. I switch to Philz Touch and no longer have the issue.