[Q] MIUI 1.9.16 w/ Glitch = Issue - Fascinate Q&A, Help & Troubleshooting

I took a plunge back to MIUI and decided to install Glitch today..
Now when I reboot it goes to a CWM 4..something. I hit the fix permission button to try and clean up some FC's but now the phone wont boot past the Glitch Galaxy screen. I can even 3 finger back into CWM.
Anyone know what happened and how i can get past it?

You won't be able to flash any of the "newer" kernels to an old version of GB/Miui. When I tried this I was able to 3 finger into recovery though and reinstall Miui. However sounds like you need to Odin back to stock then reflash. I've found JTs 912 kernel works best with Miui 916. Miui 1028.1 over on the other site is fully functional, I recommend you update to that of.you wish to try the newer kernels.

Same thing happened to me last night. I didn't ODIN back to stock. I just
I followed this http://wiki.cyanogenmod.com/wiki/Samsung_Fascinate:_Full_Update_Guide
I just re-flashed recovery with heimdall and wiped everything then did a full restore of a previous backup I made.

Related

[Q]- I just tryed to install CM7 and now

I have a Vibrant and have used many other roms but have flashed any thing like 6 months so I wanted to try something new and saw that CM7 was working now. I flashed back to stock, than flashed to whatever the link is right after install talking about froyo bootloaders at this link http://forum.cyanogenmod.com/topic/17020-all-models-cyanogenmod-7-for-samsung-galaxy-s-phones-build-20110303/ than tryed to install it "the hard way" but now it just keeps rebooting try to reflash ClockworkMOD recover or something. any ideas?
I did the same thing. You need to be on a froyo rom to install CM7.
I odin'd back to stock, installed Bionix -v 1.2.1 then disabled voodoo. I then cold booted into CWM and installed CM7. Worked good that way.
how did you do that. it just keeps going in a circle booting.
You will need to go into download mode.
Phone off (battery pull), hold vol up and down together, while holding - plug in USB.
Odin should then recognize it.
Re Odin back to stock, root, upgrade to a froyo rom then upgrde to CM7.
okay I just got back to stock again, at least it looks like it! But I am still getting an odd thing. when the phone is booting the first screen that comes up is not vibrant its gt-I900 any ideas?
yay ur getting the 1900 bootloader because u have both on ur phones!
how do I fix this? I just flashed back to Bio 1.2.1 and its still there
well now I did it... think I just really bricked it this time. I did what the post by a400meter said to do at this link http://forum.xda-developers.com/archive/index.php/t-756832.html and now it wont even turn on!

[Q] CM7 and GlitchV13

I lurked around the GlitchV13 forum for a good long time and didn't find an answer to this.. and because I've only been lurking for about a year I wasn't able to post anything, so it's about time I guess.
I'm having problems with the GlitchV13 kernel. Maybe I'm just being dumb and don't see something here. some help would be greatly appreciated.
I flashed GlitchV13 on my CM7.1 using CWM 5.0.2.7. No problems at all. Running great for two days. Suddenly, my phone won't connect to wifi. Cycled airplane mode and nothing popped up, so I did a reboot.. annnd got stuck in a bootloop between the CM splash and my lockscreen (wtf). Rebooted again, and now I'm stuck on the CM7 screen. Tried to Odin CWM4, still no bueno, and I get a "E:Can't mount recovery/log/"blahblahblah.
Admittedly, this happened one time before- I did a clean install from stock. Then I got gutsy and flashed GV13 again. Any idea why this is happening? After I flashed Glitch I didn't touch any other recoveries, nor did I try to push anything with Odin or Heimdall.
I really just don't wanna flash back to stock again, and a new solution to why this is happening would be super!
Thanks in advance.
EDIT: Got it. Glitch comes packaged with 4.x CWM, while CM7 comes packaged with 5.0.2.7. Any way to reconcile the two? Worth it to push 4.x over 5.x, flash Glitch then backup so I don't have to do a full restore to CM7?
I had the wifi problem on the stock kernel once, so I dont think that problem is with Glitch.
I also just flashed the latest kernel version and they have updated CWM to 5.0.2.7.
That being said are you sure the recovery is making this much trouble on the phone? Usually it doesn't make a difference (besides backups and whatnot).
The glitch recovery has a few extra features that the CM7 recovery does not.
one being able to wipe dalvik and cache at the same time. (very minor but its more convenient)
I personally think its worth it.

[Q] How to install CM10 over JB?

I've got a Galaxy S III and it worked more than perfect before I decided to get the JB update in Kies. Now the physical buttons happen to freeze all the time (the phone itself works), if the screen is on, I can touch everything, apps work, but back/home/menu/screen off don't. It's terribly frustrating to have such an expensive phone and having such an experience with it.
Anyway, I flashed from Sammobile every possible stock ICS and all of them get me stuck in the splash screen as if it's soft bricked, and ALL the stock JBs have the same button problem. Now I thought to myself the only way to go is CM.
The question is: how to I install CM (9, 10 whichever!) over my JB? Or better still (although I gave up on it) how do I get back to the good old flawless stock ICS?
Thank you in advance!
It's basic. Install a recovery, then grab your desired Rom (cm10 or whatever) then backup your apps with Titanium, and reboot in recovery, wipe all partitions (data, cache, dalvick, system) then flash your room, bit and restore your apps.
I did just that, but I get error status 7 when flashing with every version of CM10 i downloaded. When I googled the error I saw it has to do with the kernel not matching the ROM or something...
Strange as kernel provided with Rom is designedto work with. What version of cwm are you using? Try with twrp recovery.
I noticed I didn't have the last version of CWM so I installed it but got the same error. Then I tried TWRP and it worked like a charm! I especially like the touch version. Thanks a lot for your advice, help and everything!

[Q] galxy s4 rom problem

for some reason every time I flash a new rom on my phone it will go fine after the initial reboot it will boot up fine, but after I reboot the next time it just sticks on the custom padlock screen, iv let it sit for a hour and it wont go past, if I flash rom again it will do the same thing, iv flashed hyperdrive rls4, it worked fine for a while but when I went to rls5.7 it started doing this, so I tried going back to 4, it would do the same thing, iv also flashed synergy, rls6 and 7, and the stock rooted deodexed rom, it all does the same thing, iv odin back to stock and rerooted, it still does it when I flash the new rom, I go by the instructions exwhyactly when flashing, data wipes and everything, anyone got any ideas why this happens
what kernel are you flashing? Must be a loki kernel.

[q] help!! Note down

So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
dar101978 said:
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
Click to expand...
Click to collapse
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
CalcProgrammer1 said:
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
Click to expand...
Click to collapse
Thanks thats what i did, I just basically had to use KIES to use the emergency recovery, then root my phone again. My question is what version of TWRP causes this? cause i used the newest version i could find off GOO. My other concerne is, will it accept or be safe to use a custom ROM? Well i gues ill find out :laugh: THANKS AGAIN!
Everyone with the sgh-i717 is having problems with the latest TWRP and the most stable version is 2.5.0.0. Go with that one or you'll be starting all over again I imagine. And don't just stop at the download link in the OP's, read the thread and find out what's going on. The problems with TWRP have been going on for a while and the development threads have a lot of comments about the latest build causing problems. Good luck! :good:

Categories

Resources