Related
My phone is quote slow and laggy and it's quite surprising seeing as this phone is meant to be known for it's speed and power.
I have rooted with cf-root , I don't really know if this means if I have a custom kernel.
All I want to know is if there is a custom ROM or kernel to help with this. If yes, which one. Many developers claim there stuff speeds up phones but obviously they're bias. I want neutral opinions from people with experience of different things.
Before people tell me to search I can only access the net through my phone and the drop down search button don't work.
First of all rooting your phone is good cos it now means that you can flash a custom ROM.Something that cant be done on stock.For the moment stay with CF-Root as they are basically stock rooted kernels and at the moment I dont think you need to get into overclocking and undervolting and all that stuff that more advanced kernels can do cos if you do it wrong yourve got problems.As for ROMs your right.All Devs will say that they have the best one and all happy users,yes like myself,will say they use the best one too.The problem is that everyone has different likes and needs.No one who has spent time on this site has ever only had ONE ROM on their phone.Its impossible to not turn into a flashaholic at some stage.The best you can do is read threads and try some.Not the answer you wanted but its the best and only way to find what you want.Try mine.I love it.The link is below the big blue Omega sign.Its the one that says "GB".If you dont like it then try something else.Theres really no other way to find out what you want unless you try for yourself.
I see.. So I simply download the custom ROM and install it through clockwork mod?
Do I have to back up my phone with titanium back up before I install custom roms?
anz2k8 said:
I see.. So I simply download the custom ROM and install it through clockwork mod?
Do I have to back up my phone with titanium back up before I install custom roms?
Click to expand...
Click to collapse
Step 1 - backup with titanium.
Step 2 - reboot into cwm or with the cwm app, create a backup. So, if you flash something that you don't like or if it wont boot, you can restore it. This is a complete system and data backup. A 1:1 copy of your phone setup, excluding modem which defaults to whatever you are running at the time of restore.
Step 3 - try some custom roms. I use Checkrom (older version - v2) and phone flies.
Anyway, something must be wrong with your setup because every rom I've used has been fast, even stock.
ps : sent you a pm.
Sent from my GT-I9100T
Once you get sorted then do an EFS backup.The EFS folder contains your IMEI number and if for whatever reason you should loose it or it becomes corrupt then you are in the poo.Download the "release.zip" and follow the easy instructions.
http://forum.xda-developers.com/showthread.php?t=1308546
I was using checkrom v4 and then v6 for a little while both with SiyahKernel which worked really well.
Currently using CM9 but I wouldn't go there until your comfortable fixing things and regularly flashing.
But definately select your rom and then try changing kernels if you think it will benefit you.
Sent from my GT-I9100 using Tapatalk
@cooza when should I back up this eps, everyone time I change ROM or everyone I change kernel? I don't even know what it is lol
@sxi200 you say there must be something wrong with my setup, could you explain in a little more detail what you think I should change please?
Just thought I would *Bump* the thread as i'm slightly desperate for the random rebooting. It happens approximately once or twice a day.
did u use wipe data/factory reset while installing a new rom?
expierienced some funny things like lag etc also while trying different roms,
my fault was not wiping the cache ...
anz2k8 said:
Just thought I would *Bump* the thread as i'm slightly desperate for the random rebooting. It happens approximately once or twice a day.
Click to expand...
Click to collapse
One Factory reset the phone this will wipe all data
Two upgrade firmware via Kies if firmware is available .
Three flash a later stock Samsung rom .
Four any of the answers already posted .
Five wait for Samsungs ICS update .
i see you have rooted but dont know what root is for or even any of the basics .
Read the guides and stickies .
Guide
http://forum.xda-developers.com/showthread.php?t=1125282
Its possible that you have rooted with a wrong file .
But you give zero information .
jje
Hi,
I rooted my GSII, using step 2c from the guide found here: http://forum.xda-developers.com/showthread.php?t=1311081 with the UCKK6 Stock + Root package found here: http://forum.xda-developers.com/showthread.php?t=1286432
Afterwards, I used CWM to flash PhoneBricker v2.7 (http://forum.xda-developers.com/showthread.php?t=1560759). After only a few minutes of use, my phone began locking up and rebooting randomly. It didn't matter what I was doing at the time. After reading through some threads, I tried wiping cache, factory reset, and flashing only the ROM again, to no avail. I also noticed the phone would get pretty hot when it would lock up.
I thought the ROM was the issue, so I flashed Mystic's Glory ROM (v.4.9.2beta) after wiping cache, factory reset. Same behavior.
I've resorted to restoring the first nandroid backup I did, which is just stock + root.
Would anyone have any suggestions? Thank you.
I'm not sure i have a suggestion, but i do have a couple of questions, maybe these will at least rule out some obvious possibilities:
- first, the obvious. This is probably not the issue in your case, but since this happens so often i figured I'd ask: we often see people here who have a different SGS2 variant than the I-777 the ROMs on this forum are for. Which variant of the SGS2 do you have? To use the ROMs here it should be I-777, which is AT&T's version of the SGS2, but NOT the skyrocket. If you have a skyrocket or a non-AT&T version, you need to get the ROMs from the appropriate forums.
-Since the FCs are happening with different ROMs, maybe the problem is being caused by an app or app restore method. Do the problems start before you even restore or install your apps, or after? If you are restoring apps with Titanium Backup, make sure you don't restore any system apps, only user apps. Restoring system apps with TiBu is known to cause problems, specially if you restore system apps that you backed up from a different base
Edit: still in the spirit of ruling out the obvious, when you wipe cache before installing the ROM, i assume you are ALSO wiping the dalvik cache?
wgoldfarb said:
I'm not sure i have a suggestion, but i do have a couple of questions, maybe these will at least rule out some obvious possibilities:
- first, the obvious. This is probably not the issue in your case, but since this happens so often i figured I'd ask: we often see people here who have a different SGS2 variant than the I-777 the ROMs on this forum are for. Which variant of the SGS2 do you have? To use the ROMs here it should be I-777, which is AT&T's version of the SGS2, but NOT the skyrocket. If you have a skyrocket or a non-AT&T version, you need to get the ROMs from the appropriate forums.
-Since the FCs are happening with different ROMs, maybe the problem is being caused by an app or app restore method. Do the problems start before you even restore or install your apps, or after? If you are restoring apps with Titanium Backup, make sure you don't restore any system apps, only user apps. Restoring system apps with TiBu is known to cause problems, specially if you restore system apps that you backed up from a different base
Edit: still in the spirit of ruling out the obvious, when you wipe cache before installing the ROM, i assume you are ALSO wiping the dalvik cache?
Click to expand...
Click to collapse
wgoldfarb,
I do, in fact, have the I777 variant.
Can you please tell me what you mean by FCs?
The random lockups/reboots began even before I started installing other apps. I do not have Titanium Backup. I installed the apps from the Play store.
Yes, I made sure to do a factory reset, wipe cache, and wipe dalvik cache.
Could it be an issue with the way the ROM is handling CPU usage? Perhaps there is a preset that is on by default that may be causing lockups.
I'm also wondering rooting using the UCKK6 package was the correct way, as opposed to rooting back to the UCKH7.
I appreciate your help.
What kernel are you running? That sounds like the issue to me
jthatch12 said:
What kernel are you running? That sounds like the issue to me
Click to expand...
Click to collapse
jthatch,
When I rooted, it remained as stock kernel (2.6.35.7).
When I flashed PhoneBricker and Mystic's Glory, I stayed with the kernels that were supplied by the ROM zip package.
wwjd3 said:
jthatch,
When I rooted, it remained as stock kernel (2.6.35.7).
When I flashed PhoneBricker and Mystic's Glory, I stayed with the kernels that were supplied by the ROM zip package.
Click to expand...
Click to collapse
You can't flash a "rom zip package" from the stock kernel with 3e recovery. You need to install a custom kernel with ClockworkMod Recovery first before you install a "rom zip package". So what you are saying is not making sense.
I really don't think it would make any difference whether you used the UCKK6 plus root or the UCKH7 plus root.
Whenever you change base, it is necessary to perform a wipe data/factory reset, and also recommended to wipe cache and to wipe dalvik cache. These should be performed from within Recovery. The wipe data/factory reset should not be performed from the phone settings.
If you flash a new firmware after doing the proper wipes in recovery before flashing, then the new firmware should run without problems, unless the download was bad, causing a bad flash. You should also check the md5 sum of the downloaded file to verify a good download before you flash it.
creepyncrawly said:
You can't flash a "rom zip package" from the stock kernel with 3e recovery. You need to install a custom kernel with ClockworkMod Recovery first before you install a "rom zip package". So what you are saying is not making sense.
I really don't think it would make any difference whether you used the UCKK6 plus root or the UCKH7 plus root.
Whenever you change base, it is necessary to perform a wipe data/factory reset, and also recommended to wipe cache and to wipe dalvik cache. These should be performed from within Recovery. The wipe data/factory reset should not be performed from the phone settings.
If you flash a new firmware after doing the proper wipes in recovery before flashing, then the new firmware should run without problems, unless the download was bad, causing a bad flash. You should also check the md5 sum of the downloaded file to verify a good download before you flash it.
Click to expand...
Click to collapse
I'm sorry. I failed to mention that after rooting, I used MobileOdin to flash a custom kernel (Siyah 2.6) with CWM (step 3a in the first link I provided). From there, before flashing PhoneBricker, I did a factory reset, cache wipe, dalvik cache wipe, all from within CWM. I did NOT perform factory reset from phone settings.
I have not performed a md5 sum check. I guess that would be the next step.
Wwjd3
You are now getting help from extremely knowledgeable people, so i wont even try to add any suggestions...you are in excellent hands
I only wanted to answer your question about "FCs". By FCs I meant forced closes...it's when an app has a problem or stops responding and you get a message saying the app had a problem and had to close. When you said your phone locks up i assumed you meant you were experiencing forced closes.
wgoldfarb said:
Wwjd3
You are now getting help from extremely knowledgeable people, so i wont even try to add any suggestions...you are in excellent hands
I only wanted to answer your question about "FCs". By FCs I meant forced closes...it's when an app has a problem or stops responding and you get a message saying the app had a problem and had to close. When you said your phone locks up i assumed you meant you were experiencing forced closes.
Click to expand...
Click to collapse
Ah, I understand. What I meant by lockup is that the system freezes. The capacitive buttons no longer respond. Neither do the volume/power buttons. The screen simply freezes, and I have to force a restart by holding down the power button for a number of seconds. I hope that makes sense.
Wow. Well, I hate to say it, but...lol I would go back to stock 2.3.4 with Odin, wipe everything, and try again. I mean that answer sucks. But it may help rule out some things and give u an idea if its hardware or software related. U could also try different kernels and using the kernel cleaning script, just Google it with xda in the search and it'll come up.
Sent from my SGH-I777 using Tapatalk 2
Phalanx7621 said:
Wow. Well, I hate to say it, but...lol I would go back to stock 2.3.4 with Odin, wipe everything, and try again. I mean that answer sucks. But it may help rule out some things and give u an idea if its hardware or software related. U could also try different kernels and using the kernel cleaning script, just Google it with xda in the search and it'll come up.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Phalanx7621,
heh. That's what I'm thinking of doing. Can someone clarify, though: according to the forum stickies, when flashing a custom kernel with CWM after rooting, there are only two available, correct? Daily Driver and Siyah.
Secondly, can you briefly describe what the kernel cleaning script accomplishes. I've seen the term in some posts, but didn't think it was relevant. Thank you.
wwjd3 said:
Phalanx7621,
heh. That's what I'm thinking of doing. Can someone clarify, though: according to the forum stickies, when flashing a custom kernel with CWM after rooting, there are only two available, correct? Daily Driver and Siyah.
Secondly, can you briefly describe what the kernel cleaning script accomplishes. I've seen the term in some posts, but didn't think it was relevant. Thank you.
Click to expand...
Click to collapse
1. Short answer - yes. Long answer - no (I remember a few other options floating around). For all intents and purposes, just pick one of those; either will accomplish what you need.
2. From what I remember about looking at the script, it wipes dalvik cache and deletes the contents of /etc/int.d (to prevent incompatible scripts across kernels - not exactly relevant since you're doing clean installs). No rom should have kernel specific scripts anyway. I think it wipes some system caches or something also.
Simba501 said:
not exactly relevant since you're doing clean installs). No rom should have kernel specific scripts anyway. I think it wipes some system caches or something also.
Click to expand...
Click to collapse
If I read correctly, Phalanx was offering up a secondary option to try out before taking the complete stock route which would make it relevant. However, if he does the return to stock... Then you're right, not gonna do much for him. (though it wouldn't hurt)
Clay
Team Pirate
Sent from my PINK SGH-I777
You've described following the correct procedure for rooting and flashing a custom firmware. I don't see anything in that procedure that could cause firmware problems, except perhaps corrupt downloads. But the odds are against getting two corrupd downloads in a row.
If it were my phone, I would probably flash back to stock, and run it a few days to see if it runs correctly, to rule out hardware problems. If there is developing hardware issues, bad memory perhaps, then it should be evident even on straight stock.
The next thing is to just start from scratch, and do everything over again. When I flashed SHOstock2 1.4.1 over 1.3.2 (change of base) I did everything right, but I got apps freezing and other problems, so much that the phone was unusable. I went back to 1.3.2 for a week, then flashed 1.4.2 successfully. So the answer could be just a bad flash even though you can't put your finger on the exact reason.
creepyncrawly said:
You've described following the correct procedure for rooting and flashing a custom firmware. I don't see anything in that procedure that could cause firmware problems, except perhaps corrupt downloads. But the odds are against getting two corrupd downloads in a row.
If it were my phone, I would probably flash back to stock, and run it a few days to see if it runs correctly, to rule out hardware problems. If there is developing hardware issues, bad memory perhaps, then it should be evident even on straight stock.
The next thing is to just start from scratch, and do everything over again. When I flashed SHOstock2 1.4.1 over 1.3.2 (change of base) I did everything right, but I got apps freezing and other problems, so much that the phone was unusable. I went back to 1.3.2 for a week, then flashed 1.4.2 successfully. So the answer could be just a bad flash even though you can't put your finger on the exact reason.
Click to expand...
Click to collapse
I just used your guide to return back to stock UCKH7. I am attempting to root again, this time using DooMLoRD's Easy Rooting Toolkit. Not having any luck with that one (complaining about "cannot stat files"). I'm looking through the I777 forums but there is no chatter about this issue. There is for other phones, however. And the search continues. Thanks for your help!
wwjd3 said:
I just used your guide to return back to stock UCKH7. I am attempting to root again, this time using DooMLoRD's Easy Rooting Toolkit. Not having any luck with that one (complaining about "cannot stat files"). I'm looking through the I777 forums but there is no chatter about this issue. There is for other phones, however. And the search continues. Thanks for your help!
Click to expand...
Click to collapse
How did you root your phone b4? which method?
Use that.
votinh said:
How did you root your phone b4? which method?
Use that.
Click to expand...
Click to collapse
I used method 2c, Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package with Modem using Odin3 One-Click Downloader previously. I was thinking of using a different method, since I ran into problems using Entropy512's method. Try something different.
-------------------------------------------------
EDIT:
I'm sorry, I was wrong. Since I had UCKK6 build previously I used Odin to flash the Kernel + cache + rooted UCKK6 system package found here: http://forum.xda-developers.com/showthread.php?t=1286432
So, using method 2c would, in fact, be a different method altogether. I'm beginning to think that initially rooting using Odin+UCKK6 package is what got me into trouble in the first place.
wwjd3 said:
I'm beginning to think that initially rooting using Odin+UCKK6 package is what got me into trouble in the first place.
Click to expand...
Click to collapse
It's as good a theory as any other... I guess.
Hello all,
I had the eMMC bug on my galaxy s2, even by being careful and reading a lot of guides before, I didn't read about the bug until it was too late...
It is currently being repaired by a samsung repair center... thanks again to all the persons who gave me support and advice during this sad episode !
Obviously, I don't want to brick it again...
I have read a lot more since, but to be on the safe side, can you confirm or correct the following ?
When I receive it, if it is on 4.0.4 official, I should NOT attempt any wipe or format.
if I want to flash CM9.1, first thing I have to do is:
install "Siyah S2-v5.0.1"
and then, I can do all the wipes/format in the world I want from CWM, correct ?
also, what is the best way to flash Syah from a stock rom ? Odin or temp CWM ?
can you give me the pros and cons of each solutions ? Is there any other solution ?
Before bricking my s2, I did a nandroid backup.
if I restore my nandroid backup from temp CWM, will it trigger the emmc bug again while restoring it ?
What is your advice, should I flash Siyah S2-v5.0.1 then restore from Siyah CWM my nandroid backup ?
My nandroid backup was done when I had stock 4.0.4 and from CWM temp.
Lastly, is it perfectly safe to flash from Odin GB --> ICS and ICS --> GB ? I have read you can hardbrick your phone going from ICS to GB... not sure how though...
Thank you guys
Hey sorry for this bad news...
So because next steps...
1) restoring nandroid
If u want to go ahead and not use the 4.0.4 any longer, just leave it, to be sure...
2) next steps
Personally I would say u can choose between two options:
- Flash another firmware + root + flashing ahead....
- flash the named Siyah + flash another Rom (with full wipe)
3) how
Because u will have a stock phone back, at least I'm sure about this , u can do the first option with searching a firmware on: http://www.sammobile.com/firmware/?page=3
Download and flash this via odin (I think u know how u do this)
If u choose the second way, it's quite the same thing but u won't flash the firmware, because u use the .tar u find from the kernel on http://d-h.st/Bcf
So hope this brings u further, buddy
CHEERS
Sent from my GT-I9100 using xda premium
megosu said:
Hello all,
I had the eMMC bug on my galaxy s2, even by being careful and reading a lot of guides before, I didn't read about the bug until it was too late...
It is currently being repaired by a samsung repair center... thanks again to all the persons who gave me support and advice during this sad episode !
Obviously, I don't want to brick it again...
I have read a lot more since, but to be on the safe side, can you confirm or correct the following ?
When I receive it, if it is on 4.0.4 official, I should NOT attempt any wipe or format.
if I want to flash CM9.1, first thing I have to do is:
install "Siyah S2-v5.0.1"
and then, I can do all the wipes/format in the world I want from CWM, correct ?
also, what is the best way to flash Syah from a stock rom ? Odin or temp CWM ?
can you give me the pros and cons of each solutions ? Is there any other solution ?
Before bricking my s2, I did a nandroid backup.
if I restore my nandroid backup from temp CWM, will it trigger the emmc bug again while restoring it ?
What is your advice, should I flash Siyah S2-v5.0.1 then restore from Siyah CWM my nandroid backup ?
My nandroid backup was done when I had stock 4.0.4 and from CWM temp.
Lastly, is it perfectly safe to flash from Odin GB --> ICS and ICS --> GB ? I have read you can hardbrick your phone going from ICS to GB... not sure how though...
Thank you guys
Click to expand...
Click to collapse
If it is 4.0.4, flash that kernel you mentioned, it's a safe one.
Then, all you have to do is whatever it is that you wanna do with it.
You are now very experienced with odin, DL mode and Recovery mode, you kept on trying to get your old SII back to the living (I was there, I saw you tried).
With your new device you have the chance to start clean, from scratch, forget about that nandroid back up, keep reading here on XDA and I ASURE you, you'll do 5 times better than the past.
BTW: you weren't affected by the brick bug, your device was kinda faulty after all. Brick bugged devices wouldt let you go into DL mode.
I strongly recommend you read the Stickies. The questions you've asked have been answered hundreds of times on here before. And that you've asked them is indicative of not knowing 'the basics'.
Surveys show people who read them have a 84% less chance of bricking their phone than people who don't (almost everyone who visits here & jumps into doing stuff with their phone without understanding the basics/how the phone & its firmware actually works first).
I have read the stickies... thank you for that
according to your survey, one who reads the stickies still has 16% of chance to brick his device, this is why I want to be extra sure and asked for advice about specific questions, not a lecture :/
It might be obvious for you, but not for everybody, so when somebody asks a question that seems silly for you, helping the guy by answering is more helpful than telling him to read stickies, and it helps also others who come across this thread not being 100% sure of what they understood from reading stickies.
in my case, I have read on the forum the following and I would appreciate some help to confirm if I gathered the correct information.
As I said previously, it might be obvious for you but it can help me and others NOT to brick their phone !
When I receive it, if it is on 4.0.4 official, I should NOT attempt any wipe or format.
if I want to flash CM9.1, first thing I have to do is:
install "Siyah S2-v5.0.1"
and then, I can do all the wipes/format in the world I want from CWM, correct ?
Click to expand...
Click to collapse
I also think I know the answer about this:
also, what is the best way to flash Syah from a stock rom ? Odin or temp CWM ?
can you give me the pros and cons of each solutions ? Is there any other solution ?
Click to expand...
Click to collapse
I think it is safer to flash through Odin as the temp CWM has the emmc bug. But Odin will change my binary counter and add the yellow triangle...
hence why I asked your advice
I haven't found the answer in the stickies about this one... maybe you know if it is safe to restore a nandroid backup ?:
Before bricking my s2, I did a nandroid backup.
if I restore my nandroid backup from temp CWM, will it trigger the emmc bug again while restoring it ?
What is your advice, should I flash Siyah S2-v5.0.1 then restore from Siyah CWM my nandroid backup ?
My nandroid backup was done when I had stock 4.0.4 and from CWM temp.
Click to expand...
Click to collapse
and lastly,
is it perfectly safe to flash from Odin GB --> ICS and ICS --> GB ? I have read you can hardbrick your phone going from ICS to GB... not sure how though...
Click to expand...
Click to collapse
same here, didn't find it in the stickies... and I saw different answers across the forum so it is hard to get conclusions out of it.
again, sorry if it is too easy for you or if you feel like it has been said somewhere else, but your answers can make the difference for people and avoid a brick.
And it doesn't hurt to repeat a correct information, it just confirm it and make it more noticeable.
Thanks for your help,
MistahBungle said:
I strongly recommend you read the Stickies. The questions you've asked have been answered hundreds of times on here before. And that you've asked them is indicative of not knowing 'the basics'.
Surveys show people who read them have a 84% less chance of bricking their phone than people who don't (almost everyone who visits here & jumps into doing stuff with their phone without understanding the basics/how the phone & its firmware actually works first).
Click to expand...
Click to collapse
easy now, you can ask whatever you want as long as you read/search first.
If you did, then it's all good, just because you are trying very hard to not messing up with your device.
I don't know what to put here...any ideas?
anyone to confirm if I got it right ?
I'm lost here; how are you doing with your new device anyways?
still at the repair cente, it is going to take ages
but at least I have time to "prepare", if somebody can answer to my questions of course
megosu said:
still at the repair cente, it is going to take ages
but at least I have time to "prepare", if somebody can answer to my questions of course
Click to expand...
Click to collapse
thought they gave you a new one.
what was the question again?
Well, basically all questions from http://forum.xda-developers.com/showpost.php?p=36480894&postcount=5
At least the first one:
Quote:
When I receive it, if it is on 4.0.4 official, I should NOT attempt any wipe or format.
if I want to flash CM9.1, first thing I have to do is:
install "Siyah S2-v5.0.1"
and then, I can do all the wipes/format in the world I want from CWM, correct ?
I'll try and help you out with a noob-friendly solution.
Remember emmc brickbug affects ONLY AND ONLY devices running 4.0.4 STOCK kernel. if you're running anything else, then u're safe.
if your new device comes with 4.0.4 stock, then the ONLY thing you need to do to be safe is flash a safe kernel (siyah is a valid option) through ODIN.
once u've done that, you will get root+permanent CWM.
Now all you need to do is start flashing, making backups or whatever you please !
Hope I shed some light on your issue pal.
Hugs.
Thank you,
So I got it right, I'll flash siyah first.
thanks again for taking the time to help.
Take care
Hello first time rooting this phone. Its a SGH-I777. I used the guide from galaxys2root.com/. At first it didnt work because my computer didnt recongnize my phone. I tried a different computer and it seemed successful until it rebooted. When the phone rebooted it did nothing but stay on the first screen. I still have the ability to get into Odin mode(download mode), but that is it. When i put the phone in download mode and use Odin it allows me to download the "zimage" but after rebooting it is the same exact thing. I have tried the one click root, one click factory restore. Tried restoring it on Kies. and nothing work took it to a store and the guy said he tried but it would stop in the middle of the download the only option i had with him was purchasing a new mother board for $80. Does anyone have a solution that can help me fix my phone.
Before i attempted to root it, it had OS 2.3.6 with kernal 2.6.35.7.
Go to the development section and read the stickies. There you will find stock rooted packages you can flash with Odin.
Sent from my SGH-I777 using xda premium
@jmula,
Enter recovery and perform a wipe data/factory reset. That may clear the failure to boot. If not you'll need to flash back to stock and start over.
The yellow trangle is a result of flashing a custom kernel using Odin or Heimdall, and is expected. You are not the first person having problems with the tools provided by GalaxyS2Root. In the future, I would recommend you avoid his site.
And... as suggested, read and study till you understand the basics. Then if you have questions, feel free to ask.
creepyncrawly said:
@jmula,
Enter recovery and perform a wipe data/factory reset. That may clear the failure to boot. If not you'll need to flash back to stock and start over.
The yellow trangle is a result of flashing a custom kernel using Odin or Heimdall, and is expected. You are not the first person having problems with the tools provided by GalaxyS2Root. In the future, I would recommend you avoid his site.
And... as suggested, read and study till you understand the basics. Then if you have questions, feel free to ask.
Click to expand...
Click to collapse
the only option that i have is to put the phone in download mode. when i try to download any kernel it reboots and does not go past the booting screen with the triangle.
jmula said:
the only option that i have is to put the phone in download mode. when i try to download any kernel it reboots and does not go past the booting screen with the triangle.
Click to expand...
Click to collapse
You should be able to enter recovery. Hold down all three buttons, vol+ vol- and pwr, continuously until the phone boots into recovery. It could take 10 or 15 seconds or more. If that is unsuccessful, then since you can enter download mode, you will need to flash back to stock, or stock plus root. That is not just a kernel, but the entire package. Please see the links in my sig for instructions.
The dropbox links in the download repository are temporarily suspended until probably Monday night or Tuesday as someone abused and over-downloaded. But the hotfile links still work.
creepyncrawly said:
You should be able to enter recovery. Hold down all three buttons, vol+ vol- and pwr, continuously until the phone boots into recovery. It could take 10 or 15 seconds or more. If that is unsuccessful, then since you can enter download mode, you will need to flash back to stock, or stock plus root. That is not just a kernel, but the entire package. Please see the links in my sig for instructions.
The dropbox links in the download repository are temporarily suspended until probably Monday night or Tuesday as someone abused and over-downloaded. But the hotfile links still work.
Click to expand...
Click to collapse
i Downloaded ''UCLE5 Stock ICS plus Root'' . i placed the phone in download mode started Odin and placed file in PDA. It starts but gets stuck at cache.img
jmula said:
i Downloaded ''UCLE5 Stock ICS plus Root'' . i placed the phone in download mode started Odin and placed file in PDA. It starts but gets stuck at cache.img
Click to expand...
Click to collapse
The next thing I would suggest is to try and flash the UCKH7 full stock package with bootloaders. However, as the dropbox links in the download repository are currently suspended, you will have to download it from SamFirmware. To be able to download, you will need to register for free if you havn't already. Search sgh-i777 in the upper right hand corner of the page, then download the I777UCKH7 version. Let us know if that will flash.
Ok it finally wokred after countless times of changing usb ports. I used the one click recovery. It restroed my phone to 2.3.4 i had 2.3.6. I tried to update by kies to 4.01 and it didnt work. Kies froze. The queestion is how do i safltey root the phone?
jmula said:
Ok it finally wokred after countless times of changing usb ports. I used the one click recovery. It restroed my phone to 2.3.4 i had 2.3.6. I tried to update by kies to 4.01 and it didnt work. Kies froze. The queestion is how do i safltey root the phone?
Click to expand...
Click to collapse
Flash a .tar version of a custom kernel with Odin. I always use an old siyah.tar, but that's just me. There are other methods floating around but that's the quickest and easiest for me. I think there's an old entropy dd.tar around somewhere too. But just flash it through Odin and you're good to go, assuming you flashed one for your version of android. If you just want to get into recovery to flash something this works as well.
There may be links to tar versions of the kernels in creepy's sig I don't remember offhand.
Ok since i do not want to brick my phone again where it is just stuck at the boot loop. I tried looking for ways to root and when i tried some of them my phone went back to the problem it had it the beginning. Should i just call it quits or do you guys have a guide?
jmula said:
Ok since i do not want to brick my phone again where it is just stuck at the boot loop. I tried looking for ways to root and when i tried some of them my phone went back to the problem it had it the beginning. Should i just call it quits or do you guys have a guide?
Click to expand...
Click to collapse
Give up???
I personally don't think flashing a kernel with odin is the best way to root. It increments the flash counter, for one thing, though I'm not sure how many people care about that anymore. I would suggest that you use the stock plus root package to root the phone with odin. See the links in my sig.
Guide... did someone say guide?
Feeling the pain....
creepyncrawly said:
@jmula,
Enter recovery and perform a wipe data/factory reset. That may clear the failure to boot. If not you'll need to flash back to stock and start over.
The yellow trangle is a result of flashing a custom kernel using Odin or Heimdall, and is expected. You are not the first person having problems with the tools provided by GalaxyS2Root. In the future, I would recommend you avoid his site.
And... as suggested, read and study till you understand the basics. Then if you have questions, feel free to ask.
Click to expand...
Click to collapse
First, to Creepy....you've been a great resource here and I read a lot of what you post and you got me out of the very jam being discussed here. I made the mistake of trying to root via the galaxys2root.com site (actually, I thought it was a different site...was redirected), got the i9100 screen and a boot loop...couldn't go anywhere. I came back here and found resources eventually unrooting my phone all the way back to 2.3.4, then moved to 2.3.6, then the stock android 4.0.3 which updated to 4.0.4.
But I still want to root (4.0.4 shuts itself down A LOT...more than 4.0.3) and I have a Galaxy note 10.1 with JB 4.1.2 and I LOVE IT! I feel on a mission to get rooted and try out some of the JB roms I see talked about here, but can't seem to find the best way to root. I've heard exynosabuse referenced here (no links to it though) and I don't want to use the wrong one and mess up my phone. I've been reading for weeks here and there's obviously a lot of great material, but I'm not sure which material is critical to understand, and which is "nice to know" but might not even apply, and which material isn't even right. Very frustrating.
Judi
judib said:
First, to Creepy....you've been a great resource here and I read a lot of what you post and you got me out of the very jam being discussed here. I made the mistake of trying to root via the galaxys2root.com site (actually, I thought it was a different site...was redirected), got the i9100 screen and a boot loop...couldn't go anywhere. I came back here and found resources eventually unrooting my phone all the way back to 2.3.4, then moved to 2.3.6, then the stock android 4.0.3 which updated to 4.0.4.
But I still want to root (4.0.4 shuts itself down A LOT...more than 4.0.3) and I have a Galaxy note 10.1 with JB 4.1.2 and I LOVE IT! I feel on a mission to get rooted and try out some of the JB roms I see talked about here, but can't seem to find the best way to root. I've heard exynosabuse referenced here (no links to it though) and I don't want to use the wrong one and mess up my phone. I've been reading for weeks here and there's obviously a lot of great material, but I'm not sure which material is critical to understand, and which is "nice to know" but might not even apply, and which material isn't even right. Very frustrating.
Judi
Click to expand...
Click to collapse
The ExynosAbuse application is the only practical way to root 4.0.4 without changing base. You can download it as an attachment in the OP of the developer's thread, but read through the thread first to understand its limitations and risks.
Alternatively, you could flash 4.0.3 plus root from the development forum. If you choose that route, please read the thread to understand how to install a custom kernel, which is recommended whether you plan to install a custom firmware or not. The custom kernel will contain ClockworkMod Recovery so you can flash the firmware of your choice if you wish.
There are really several routes you could choose. All of them work. Another would be to flash back to stock Gingerbread plus root. For that see my guide How to Flash Custom Binaries Without Ever Incrementing the Flash counter!! (link in sig)
Hmmmmm..
Well, I see that their are many, more experienced than me following this thread and my following comment is not meant to jump on the knowledge train here, but............... I had the same event happen as the orig poster earlier today. I had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII, What I did was go into recovery ,cleared the Dalvik cache and that is all I cleared. Then I re-installed the RR Rom .rar, which I keep on my SD, over everything and rebooted, it came back as it was 4 mins before . All I did after, was do a system restore(only) using Titanium BU. So when I see all the "clear and restore this and that" I started to doubt some of the more experienced than I. My 2 cents is, that, if one does not know EXACTLY ,how to correct an issue,leave it for our more knowledgeable brothers and sisters.
If I am wrong ,please except my appology.
b0bb said:
Well, I see that their are many, more experienced than me following this thread and my following comment is not meant to jump on the knowledge train here, but............... I had the same event happen as the orig poster earlier today. I had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII, What I did was go into recovery ,cleared the Dalvik cache and that is all I cleared. Then I re-installed the RR Rom .rar, which I keep on my SD, over everything and rebooted, it came back as it was 4 mins before . All I did after, was do a system restore(only) using Titanium BU. So when I see all the "clear and restore this and that" I started to doubt some of the more experienced than I. My 2 cents is, that, if one does not know EXACTLY ,how to correct an issue,leave it for our more knowledgeable brothers and sisters.
If I am wrong ,please except my appology.
Click to expand...
Click to collapse
I don't know what you're trying to get across here. Yes, restoring a backup nandroid works. Yes, you can try wiping cache and dalvik to see if it fixes an issue. Yes you can restore apps via titanium backup. All these things are indeed true.
Phalanx7621 said:
I don't know what you're trying to get across here. Yes, restoring a backup nandroid works. Yes, you can try wiping cache and dalvik to see if it fixes an issue. Yes you can restore apps via titanium backup. All these things are indeed true.
Click to expand...
Click to collapse
Well if you did not fully grasp what I was trying to get across,you seemed to get it correct with your statement.
b0bb said:
Well if you did not fully grasp what I was trying to get across,you seemed to get it correct with your statement.
Click to expand...
Click to collapse
And yet you say, "All I did after, was do a system restore(only) using Titanium BU." This may have worked for you, but this is an absolute recipe for disaster, and should not be given as a recommendation.
And further, from what you say, you did not have the "same event happen as the orig poster." Instead you "had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII." This is by far not the same as trying to root with a tool from GalaxyS2Root.
creepyncrawly said:
And yet you say, "All I did after, was do a system restore(only) using Titanium BU." This may have worked for you, but this is an absolute recipe for disaster, and should not be given as a recommendation.
And further, from what you say, you did not have the "same event happen as the orig poster." Instead you "had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII." This is by far not the same as trying to root with a tool from GalaxyS2Root.
Click to expand...
Click to collapse
Hey Bro, I think you think that I am challenging you, trust me I am not and I thank you for correcting me and putting me in my place, which is a bit phone techie challenged, I'll stick to building submarines. Thanks for what you do here.
b0bb said:
Hey Bro, I think you think that I am challenging you, trust me I am not and I thank you for correcting me and putting me in my place, which is a bit phone techie challenged, I'll stick to building submarines. Thanks for what you do here.
Click to expand...
Click to collapse
Not at all. I want people to help others here. I want you to help other here as well. But it is important to post only accurate information. Inaccurate information can cause someone to do the wrong action. So I always correct misinformation.
I'm fairly new to rooting and flashing kernels so sorry if I'm ignorant about all this. I have the latest version of TWRP (3.0.2-0). I would install the latest BluSpark zip (r128), wipe the data and cache and then format them into F2S2 and the phone would reboot fine. However, if I try and reboot the phone or turn it off and turn it back on again I just get stuck at the bootloading animation. Is there any advice or anything I do to prevent this? Did I install something wrong or using the wrong version of something? Thanks in advance for any and all help!
JudoFreak said:
I'm fairly new to rooting and flashing kernels so sorry if I'm ignorant about all this. I have the latest version of TWRP (3.0.2-0). I would install the latest BluSpark zip (r128), wipe the data and cache and then format them into F2S2 and the phone would reboot fine. However, if I try and reboot the phone or turn it off and turn it back on again I just get stuck at the bootloading animation. Is there any advice or anything I do to prevent this? Did I install something wrong or using the wrong version of something? Thanks in advance for any and all help!
Click to expand...
Click to collapse
Your title seems like bluspark have some kind of problem, but that's not the case. You should change that; the kernel works flawless and the problem is clearly you that doesn't know what you're doing. Read and learn from guides, videos and everything else before going flashing around.
And, of course, search. There are threads out there pointing out how to unbrick your phone and solve this kind of mistake.
(and you may have flashed the kernel for CM13, not the OOS kernel...)
Oedipus Rex said:
Your title seems like bluspark have some kind of problem, but that's not the case. You should change that; the kernel works flawless and the problem is clearly you that doesn't know what you're doing. Read and learn from guides, videos and everything else before going flashing around.
And, of course, search. There are threads out there pointing out how to unbrick your phone and solve this kind of mistake.
(and you may have flashed the kernel for CM13, not the OOS kernel...)
Click to expand...
Click to collapse
My apologizes if it seemed like I was implying or insinuating that something was wrong with the kernel, I was only stating it so that it would provide the necessary information for those at were interested in troubleshooting and saving them the hassle of asking. This is my first Android device, and first time rooting and I don't think it would be inappropriate to ask for a slight bit of patience. Again, I did not mean to imply something was wrong with the kernel, I am fairly certain it is something of my doing that I can (hopefully) repair.
Is there any guide that you would recommend specifically for the BluSpark kernel? I know for certain I donwloaded and installed the OOS version so I know that's not an issue.
I think you have to use an older version of twrp to flash this kernel. The recommended version of twrp is 2.8 I believe maybe this is your problem but I'm not sure since I am using cm13 based rom with this kernel.
Go dig through the Blu_Spark thread, I'm pretty positive he said he will never support using F2FS as no one's shown that it's either better or worse than EXT4 which has been trusted for years.
JudoFreak said:
I'm fairly new to rooting and flashing kernels so sorry if I'm ignorant about all this. I have the latest version of TWRP (3.0.2-0). I would install the latest BluSpark zip (r128), wipe the data and cache and then format them into F2S2 and the phone would reboot fine. However, if I try and reboot the phone or turn it off and turn it back on again I just get stuck at the bootloading animation. Is there any advice or anything I do to prevent this? Did I install something wrong or using the wrong version of something? Thanks in advance for any and all help!
Click to expand...
Click to collapse
You did a couple of things wrong. When you flash the kernel there is no need to wipe data. You basically reset your phone. Also, formating to f2fs after you flash the kernel will also wipe data and therefore reset the phone.
Your best bet is to start over from factory rom and kernel to get the phone to boot right and then do some research and reading before you start changing kernel and partition formats.
Search the question and answer forums for restoring to factory settings.
Good luck.
I have the same issue. after flashing latest build of blu_spark, phone stuck on boot screen .. i tried latest TWRP and Blu_Spark TWRP in his download section, neither worked for me. I did not format f2fs as I would like to keep it the same EXT4 .. any ideas how to solve this issue?