Related
I see that the topic has been closed due to some people claiming it bricks devices when you try and flash something over it. My question is to Master, will you continue to support and update this ROM? I didn't plan on flashing Kana 2, but Kana 3 would have been what I flashed since I like to flash every other upgrade.
If not, could it be possible that the people who claimed to be bricked didn't disable Voodoo before they flashed another rom?
Lastly, can I ODIN back to JI6 even though the Kana rom was a 2.2 rom with Voodoo enabled?
I guess I'll just try ODIN'ing later.
I just think its people not following directions and new people just wanting to have the newest, latest thing and have no idea what it is they're doing. Its just easier to blame the mistakes on a faulty bootloader then to accept the fact they screwed up....just sayin
jmcghee1973 said:
I just think its people not following directions and new people just wanting to have the newest, latest thing and have no idea what it is they're doing. Its just easier to blame the mistakes on a faulty bootloader then to accept the fact they screwed up....just sayin
Click to expand...
Click to collapse
The ROM didn't even have the Sbl.bin
Master™ said:
The ROM didn't even have the Sbl.bin
Click to expand...
Click to collapse
Right..I know which made the stories even better...lmao
Master! Do you plan on updating Kana? I love the rom.
jmcghee1973 said:
I just think its people not following directions and new people just wanting to have the newest, latest thing and have no idea what it is they're doing. Its just easier to blame the mistakes on a faulty bootloader then to accept the fact they screwed up....just sayin
Click to expand...
Click to collapse
No. It's not because "directions were not followed properly" or because I "had no idea what I was doing". I personally at this point am not blaming Master for what happened either. As strange as it sounds and as much as I know it's easy to think "oh well they must have done something wrong" I assure you I didn't. I flashed a rom through clockwork the exact same way that I and everybody else does and has done countless times before, the install finished, I selected "reboot system now" from the clockwork recovery main menu, and that's it, phone was DOA. Trust me, I know what I am doing.
Alkaloid said:
No. It's not because "directions were not followed properly" or because I "had no idea what I was doing". I personally at this point am not blaming Master for what happened either. As strange as it sounds and as much as I know it's easy to think "oh well they must have done something wrong" I assure you I didn't. I flashed a rom through clockwork the exact same way that I and everybody else does and has done countless times before, the install finished, I selected "reboot system now" from the clockwork recovery main menu, and that's it, phone was DOA. Trust me, I know what I am doing.
Click to expand...
Click to collapse
I didn't single you out....and don't feel in any way that I was personally attacking you..I wasn't. I tried to help you on your problem yesterday but I don't feel the majority of the "bricks" happening can be blamed on a new sbl.bin...It may contribute to a few...possible... and this was a ROM without that file added...
So my comments are pertaining to this rom since this rom was the one in the subject line.
jmcghee1973 said:
I didn't single you out....and don't feel in any way that I was personally attacking you..I wasn't. I tried to help you on your problem yesterday but I don't feel the majority of the "bricks" happening can be blamed on a new sbl.bin...It may contribute to a few...possible... and this was a ROM without that file added...
So my comments are pertaining to this rom since this rom was the one in the subject line.
Click to expand...
Click to collapse
I know, and I appreciate you trying to help me. I apologize if I came off like an asshole. I'm just frustrated as hell, and on edge.
I think we got off track. Could I ODIN this back to stock with Voodoo enabled or do I have to turn it off before I do? LoL
No need to disable voodoo when flashing through Odin. It formats the partitions affected by voodoo back to the standard rfs file system.
*sends thanks*
I appreciate it. I don't mind ODIN'ing first before I flash a new rom just in case. I plan on sticking with this rom for a bit, it's nice.
It's generally a good idea to To flash back to stock via Odin between roms. I can tell you that I will never make the mistake of not doing so ever again.
getting to be far too familiar a scenario lately....
lately EVERY time i reboot my phone (running ics build 2, 3 and 4, stock kernel) it gets stuck on samsung logo.. somehow my phone will only boot into the frigging cm7 recovery which as im sure youre all aware is rather useless to fix any problems im having in ics and leaves me unable to flash, backup, or restore anything. it's quite frustrating and i have no idea how to fix it but by going back to bml, re-partitioning, then odin ei20 modem, cm7 fixed recovery, then flash back to ics but doin this every reboot it getting very tedious..
ive read about recovery loops, but the fix doesnt work for me as i cant mount the ICS /system partition in cm7 recovery...and ive been all over trying a zillion things to get it to work and havent pulled dmesg or logcat but if someone thinks it would be useful ..i wish i knew why EVERYTHING is great, then BANG, reboot and it's FML city.
i should add this phone is a replacement via insurance and that the entire time ive had it, i've been having this problem to varying degrees of intensity,.sometimes if i rebooted enough the ics boot animation would finally come up and freeze part way through, and in the first week with this phone is seemed fine. the first few times i rebooted and battery pulled until it started but this is the fourth time in two weeks ive found myself going back to repartition from odin and then back to ics.. the phone is only mine for a month,.
if nobody has any ideas ill be getting it replaced tomorrow in store. i have the no fee insurance replacement plan, but i would prefer not to have to use another as it's not under warranty and this would be my second replacement and this mes has to last me until the gnex hits uscc in hopefully april if it ever does because i'd rather switch to vzw than take any of usccs other offerings currently.. if they dont get the gnex it'll be time for me to move on...
anyway please advise.. thanks
http://exzacklyright.blogspot.com/2012/01/how-to-flash-ics-on-verizon-samsung.html
exzacklyright said:
http://exzacklyright.blogspot.com/2012/01/how-to-flash-ics-on-verizon-samsung.html
Click to expand...
Click to collapse
Thanks for the response. Sounds like a good guide for newbs but in my case information is redundant. I have no problems with the install, unless recovery switches to cm7 recovery during reboot and cannot manage to boot/flash/nandroid until I Odin stock ei20 with repartition and wipe out every bit of data I had. The posts about howto fix CWM bootloop for cm9 do not seem to work for me, as the post says.. Please reread the OP, ya got me excited thinking there was a solution ;-/ thanks anyway, maybe it will help another user.
wizayne said:
Thanks for the response. Sounds like a good guide for newbs but in my case information is redundant. I have no problems with the install, unless recovery switches to cm7 recovery during reboot and cannot manage to boot/flash/nandroid until I Odin stock ei20 with repartitions and wipe out every bit of data in had. The posts about howto fix cwm bootloop for cm9 do not seem to work for me, as the post says.. Please reread the OPEN, ya got me excited thinking there was a solution ;-/ thanks anyway, maybe it will help another user.
Click to expand...
Click to collapse
have you tried flashing glitch kernel to the phone. imo it sounds like a kernel issue and not so much a phone issue.
mkuehl06 said:
have you tried flashing glitch kernel to the phone. imo it sounds like a kernel issue and not so much a phone issue.
Click to expand...
Click to collapse
The problem started after using ics from alphalulz v1 on around build 3 team hacksung IMMEDIATELY AFTER flashing glitch kernel v14 build 4...I have since kept away from glitch on ics, and the problem remains.
Lately it hasn't been as bad though and it seems by hitting random buttons during boot that it will eventually start but reading tells me glitch v14 build 5 is still recovery bootloop ridden and I haven't seen a word about it in the OP for ANY ics components be it team hacksung roms or glitch kernel, and an issue like this which from reading is seemingly widespread *should* be mentioned.
Any suggestions?
In your op you said e120, what phone are you using. E120 isn't a fascinate build.
Sent from my SCH-I500 using XDA App
Ei20 is the latest and greatest version of gb/radio from uscc for the mesmerize, not that it'll change the outcome afaik to go to anything else... unfortunately ;-/
But it is a full flash package if ya open the tar up complete with movinand, sbl, radio, rfs, etc.. I think it is a 10 or 11 file package and I've used it a hundred times with making the switch from mtd to bml
wizayne said:
Ei20 is the latest and greatest version of gb/radio from uscc for the mesmerize, not that it'll change the outcome afaik to go to anything else... unfortunately ;-/
But it is a full flash package if ya open the tar up complete with movinand, sbl, radio, rfs, etc.. I think it is a 10 or 11 file package and I've used it a hundred times with making the switch from mtd to bml
Click to expand...
Click to collapse
That makes more sense to me now I know what phone your on. Try rootzwiki they have a mesmorize section, they can help ya out more than I can. I have fassy so idk much about mes
Sent from my SCH-I500 using XDA App
Hi am obviously new to these forums but not new to Android/Samsung development so I had custom roms installed on my I777 so I needed to revert back to stock in which I flashed a leak which apparently changed the pit so I was able to download all the stock files for Odin3 for my device in the Download Repository. My question is there any reason why my device just doesn't act as accurately as I though I remembered it being when it was stock. Is there any ultimately right process for flashing because most instructions including my own are all different, some say wipe cache and data first and battery pull then download mode Creepys says its not neccessary until after the flash as does ZedoMax. I've followed all of them and haven't understood why there is no ultimately right process if there is one at all using odin3 and one-click. And if this is the case what could possibly be going on with the force closes and hangups I'm getting? If someone is willing to take the time to help me with all these questions I'd greatly appreciate it.
Dunno if it'll help, but it won't hurt..
Boot into recovery and"fix permissions". *Should* help with the FC's - oh, and delete everything from your memory that you read on galaxys2root (zedomax). Whatever you've read from creepy, COMMIT to memory. The guy is ace!
Clay
Team Pirate
Sent from my PINK SGH-I777
clay101eve said:
Dunno if it'll help, but it won't hurt..
Boot into recovery and"fix permissions". *Should* help with the FC's - oh, and delete everything from your memory that you read on galaxys2root (zedomax). Whatever you've read from creepy, COMMIT to memory. The guy is ace!
Clay
Team Pirate
Sent from my PINK SGH-I777
Click to expand...
Click to collapse
I don't see the option for fix permissions first of all is that a cwm option? Also I know creepy is one of the best but what's wrong with gs2root? And I appreciate the help but which process is the ultimate right way? Do you flash pit,PDA,modem all together or is that incorrect?
GalaxyHackster85 said:
I don't see the option for fix permissions first of all is that a cwm option? Also I know creepy is one of the best but what's wrong with gs2root? And I appreciate the help but which process is the ultimate right way? Do you flash pit,PDA,modem all together or is that incorrect?
Click to expand...
Click to collapse
I don't remember for sure, but I don't think fix permissions in available in stock 3e recovery. It should be available in just about any custom recovery.
GalaxyS2Root, and it's owner who goes by the screen name zedomax, is a strictly commercial endeavour, designed to make money but not necessarily designed to help people. I think zedomax is a developer, but I'm not sure how good he is. Many of the offerings on that web site, and presumably on his dozens of other web sites for other phones, cause problems for folks, bricking phones, and other things. Further, he takes the work of developers here and posts their work on his sites without giving any attribution or remuneration. He's spread way too thin keeping up with all his various sites, and/or he just doesn't seem to care if his offerings cause problems. We've had so many people come to this forum with various problems due to GalaxyS2Root that when the name is mentioned, everyone is on it right away.
I would only use the pit to repartition on the I777 when everything else fails. It can be a help, but you should be sure that you are going to have a successful flash before you use it, since it repartitions the memory space of the phone.
Most firmware for the I777 has everything in one .tar file, which you put into the PDA slot. If you are flashing just a param.lfs or just a sbl.bin, then that goes into the PDA slot. You can also flash a modem at the same time as the rest of the firmware, using the Modem slot, but most firmware packages have the modem in them too.
So essentially the oneclicks are absolutely the only thing I need in order to ensure a 100% successful restocking? And if so am I always suppose to factory wipe/cache then battery pull (3e recovery doesn't have a power off option)? The reason why I ask so many questions is A. A lot of peoples data isn't accurate as you've stated and its better for me to have as much data as possible when potentially getting into these things. And B. I've been flashing my S2 like a madman with OCD because as soon as I'd get a force close or any sort of hiccup happened I assumed it was because I flashed it wrong when in fact I was just following some of the directions that I've aqquired from here or GS2Root and so far everything has flashed with the same results but as its been forever since my phone was purchased so I can recall if these are just the normal hiccups that come with the inconsistancy of android. So to me I'm just trying to.make sure that I'm doing things absolutely correct.
There is lots of material here to read. You can learn a lot about your phone by spending some time reading.
creepyncrawly said:
There is lots of material here to read. You can learn a lot about your phone by spending some time reading.
Click to expand...
Click to collapse
And you are absolutely correct and I have your guide bookmarked but with so many people having different takes on how to return to stock can you point me in a direction that's the completely right way of flashing your pit and attempt software. Or is your guide with one click the most surefire way to do it? Like I said before I'm a bit OCD when it comes to my phone so whenever I get a little hiccup I can't tell if those are just normal for I777 software or is it something I've done wrong which I probably haven't but it still worries me.
If you havn't done something absolutely ignorant, i.e. flash firmware for a different phone, then you should just use my guide with the linked one-click downloader. That package does not contain bootloaders or param.lfs. Those (the bootloaders and param) will always be good, and not needing replaced, if you only flash firmware from these forums and never flash leaked firmware (which usually contains bootloaders.) There should never, ever be a reason to use a pit file. As I said before, the phone has to be pretty seriously screwed before you need to repartition, and then it should be the absolutely last thing you try.
And inform yourself before you do any actual flashing. You should know exactly what you are doing to your phone, and also know what the remedy is before you do it. That way, you can avoid doing something stupid. If you really want to learn about your phone, read at least a little bit from the forums here every day for a few months, get involved in the discussions, and before you know it, you'll be one of the helpers.
Thank you so much for all of your prompt replies, I have been using the data from this site for quite some years now but never ran into any issues which required me to create an account (although I have wanted to), but for s**ts and giggles let me just say that due to the few hiccups I encountered and not knowing what would have caused them I have already flashed the pit and repartitioned as well as flashed the oneclick w/ bootloaders and param. Now asside from the few force closes that I ran into and the one time I bricked it and brought it back to fully functional is there any harm to the flashing of those tools that I've already done so far. Is there any negative side effects of what I've done that I may not be seeing or is it a case of well "there in the repository so theyre safe as long as I've flashed them correctly". And if so are these few force closes just everyday hiccups that every version of Android experiences and that I'm just overthinking it and it's just been a case of my ocd kicking me in the ass?
The danger in using those files is in the flashing. If a flash is inadvertantly interrupted or goes bad, then it can hard brick the phone. Once the flash is complete and successful, then you're fine. There are no side effects.
Force closes, and other anomalies can be caused by conflicting data is the system and data partitions. They can also be the result of bugs in the firmware distribution or in any of the various applications. To eliminate the first cause, following all the best proceedures when flashing such as wiping first, etc eliminates the possibility that the fc's are caused by improper proceedure.
With proper installation proceedure, and with a stable firmware, and with robust applications, you should experience little to no fc's.
creepyncrawly said:
The danger in using those files is in the flashing. If a flash is inadvertantly interrupted or goes bad, then it can hard brick the phone. Once the flash is complete and successful, then you're fine. There are no side effects.
Force closes, and other anomalies can be caused by conflicting data is the system and data partitions. They can also be the result of bugs in the firmware distribution or in any of the various applications. To eliminate the first cause, following all the best proceedures when flashing such as wiping first, etc eliminates the possibility that the fc's are caused by improper proceedure.
With proper installation proceedure, and with a stable firmware, and with robust applications, you should experience little to no fc's.
Click to expand...
Click to collapse
i did zedo then s2 unlock then aokp then siyah kernal change forgot to do triangle away then tryed a ota update messed up rom cwm messed up then i just did zedo again to get cwm again then i did aokp again then ran triangle away then i return to stock backup after root then odin flash for stock non root then i took stock and did ota update to 2.3.6 i dont think we will ever get 2.3.7 because google wallet is on 2.3.7 and we cant have it correctly .....on reboot it hangs so i did 3e wipe and cache delete reboot all has been good since batt has been outragously long on uckk7 but after ota update it shows as uckk6 i used a non rooted file maybe u used a rooted return to stock file ?anyway file i used was I777UCKH7-CL503881-No-BL as stated just used pda slot .....idk after all the custom roms theres a distinct feeling in knowing your stock again but have the ability to go and do it all over again i honestly just miss the torch feature and the easy brightness slider on the pulldown
im getting h+ but it doesnt seem like true h+ speed and i also lose h+ while holding the phone im waiting for this to change with tmobile and thier 1900mhz i hope it does or ill be looking into whats going on with the modem maybe
colorsharpkid said:
i did zedo then s2 unlock then aokp then siyah kernal change forgot to do triangle away then tryed a ota update messed up rom cwm messed up then i just did zedo again to get cwm again then i did aokp again then ran triangle away then i return to stock backup after root then odin flash for stock non root then i took stock and did ota update to 2.3.6 i dont think we will ever get 2.3.7 because google wallet is on 2.3.7 and we cant have it correctly .....on reboot it hangs so i did 3e wipe and cache delete reboot all has been good since batt has been outragously long on uckk7 but after ota update it shows as uckk6 i used a non rooted file maybe u used a rooted return to stock file ?anyway file i used was I777UCKH7-CL503881-No-BL as stated just used pda slot .....idk after all the custom roms theres a distinct feeling in knowing your stock again but have the ability to go and do it all over again i honestly just miss the torch feature and the easy brightness slider on the pulldown
im getting h+ but it doesnt seem like true h+ speed and i also lose h+ while holding the phone im waiting for this to change with tmobile and thier 1900mhz i hope it does or ill be looking into whats going on with the modem maybe
Click to expand...
Click to collapse
Honestly, I have no idea what you just said, or what you're asking.
qwertyaas said:
Honestly, I have no idea what you just said, or what you're asking.
Click to expand...
Click to collapse
Me either, sometimes punctuation goes a long way
Sent from team Pirate! Using Tapatalk 2
colorsharpkid said:
i flashed zedo then used s2 unlock. then i flashed aokp and siyah kernel. I forgot to do triangle away (because I used zedo) and then tried an ota update. This messed up my rom because I couldn't access cwm. then i flashed zedo again to get cwm back. After that i flashed aokp again and ran triangle away.
I then did a return to stock backup after root and an odin flash for stock non root. While on stock i did an ota update to 2.3.6. (some nonsense about 2.3.7 and Google wallet)
.....on reboot it hangs so i did 3e recovery wipe and wiped cache. Reboot has been good since. My batt has been outragously long on uckk7!! But, after an ota update it shows as uckk6 i used a non rooted file, maybe I should have used a rooted return to stock file?
Anyway, the file i used was I777UCKH7-CL503881-No-BL as stated and i just used pda slot .....idk, after all the custom roms theres a distinct feeling in knowing your stock again but have the ability to go and flash custom ROMs all over again. i honestly just miss the torch feature and the easy brightness slider on the pulldown.
im getting h+ but it doesnt seem like true h+ speed and i also lose h+ while holding the phone. im waiting for this to change with tmobile and thier 1900mhz i hope it does or ill be looking into whats going on with the modem maybe
Click to expand...
Click to collapse
Fixed... I think. And "zedo" refers to the sh;t zedomax has on gs2root.
Clay
Team Pirate
Sent from my Buttery Pink SGH-i777
Ok thats where I'm a bit concerned because I ran into an issue before where I was going to do a flash and it choked up on me (mind you it was a pit and tar flash repartition) and it bricked on me but I was able to reflash the same process again once the pc was ok again. I also had on flash that was the 2.3.5 leak but flashed over that and it was fine. Now with that said the phone flashed well, and now it runs generally like it should have in the first place. But my question is did that fluke flash do anything negative to the device behind the scenes that will never be ok again?
creepyncrawly said:
The danger in using those files is in the flashing. If a flash is inadvertantly interrupted or goes bad, then it can hard brick the phone. Once the flash is complete and successful, then you're fine. There are no side effects.
Force closes, and other anomalies can be caused by conflicting data is the system and data partitions. They can also be the result of bugs in the firmware distribution or in any of the various applications. To eliminate the first cause, following all the best proceedures when flashing such as wiping first, etc eliminates the possibility that the fc's are caused by improper proceedure.
With proper installation proceedure, and with a stable firmware, and with robust applications, you should experience little to no fc's.
Click to expand...
Click to collapse
Ok thats where I'm a bit concerned because I ran into an issue before where I was going to do a flash and it choked up on me (mind you it was a pit and tar flash repartition) and it bricked on me but I was able to reflash the same process again once the pc was ok again. I also had on flash that was the 2.3.5 leak but flashed over that and it was fine. Now with that said the phone flashed well, and now it runs generally like it should have in the first place. But my question is did that fluke flash do anything negative to the device behind the scenes that will never be ok again?
Sorry for double post but I wanted to make sure my questions are targeting creepy seeing as this thread is getting a bit off topic.
GalaxyHackster85 said:
Ok thats where I'm a bit concerned because I ran into an issue before where I was going to do a flash and it choked up on me (mind you it was a pit and tar flash repartition) and it bricked on me but I was able to reflash the same process again once the pc was ok again.
Click to expand...
Click to collapse
As far as I know, that would be fine. Someone with dev experience could look into partition sizes on the phone, and see what actually happened. As long as the firmware is functioning correctly, then I would assume the partition sizes are correct.
I also had on flash that was the 2.3.5 leak but flashed over that and it was fine.
Click to expand...
Click to collapse
I guess you didn't get a crippled bootloader. That was the main problem with some of the leaks.
Now with that said the phone flashed well, and now it runs generally like it should have in the first place. But my question is did that fluke flash do anything negative to the device behind the scenes that will never be ok again?
Click to expand...
Click to collapse
I don't know how to look behind the scenes... but I would think your phone is fine.
creepyncrawly said:
As far as I know, that would be fine. Someone with dev experience could look into partition sizes on the phone, and see what actually happened. As long as the firmware is functioning correctly, then I would assume the partition sizes are correct.
I guess you didn't get a crippled bootloader. That was the main problem with some of the leaks.
I don't know how to look behind the scenes... but I would think your phone is fine.
Click to expand...
Click to collapse
OK great info and definitely a relief but just out.of curiousity what are the repercussions of a bad bootloader flash or an improper pit flash? And how would we know that whatever pit or bootloaders flashed weren't for our phone or are corrupted data?
creepyncrawly said:
As far as I know, that would be fine. Someone with dev experience could look into partition sizes on the phone, and see what actually happened. As long as the firmware is functioning correctly, then I would assume the partition sizes are correct.
I guess you didn't get a crippled bootloader. That was the main problem with some of the leaks.
I don't know how to look behind the scenes... but I would think your phone is fine.
Click to expand...
Click to collapse
And trust me I absolutely appreciate all the responses the answer to my last question is all I needed to know to truly understand how the i777 works and functions and I commend you for that. I felt that trying to find all these answers would have been trying to find a needle in a haystack.
Also regarding the repartioning I just wanted to make sure that everything is correct in terms of space. My device is showing only 1.89gb of "Device Memory" at the bout of the "Storage" screen is this normal I though it was higher before but I cant quite remember.
I was running CM10 experimental (supposedly stable) build and was having way too many issues: reboots 5+ times a day, random freezes requiring hard reboot, etc etc. I tried uninstalling latest apps...nope. Tried fixing permissions...nope. Finally decided to reinstall the ROM. Used CWM wiped all 3 times, went to istall from zip, couldn't find the ROM anywhere. I installed an older ICS ROM I found in there and it did it's thing until it was time to boot up...now it's stuck in boot loop. I tried removing battery, turning off with both buttons, connecting to usb...not recognized. It just keeps going thru the booting process until it says "Have a nice day!" and then starts over. How do I get in to fix this? I'm screwed....and of course use my phone all day for business......sheesh. Are there ANY JB ROMs out there that are actually stable...like in real life?
Love this site, love all of you helpful folks....pulling my hair out at this point...;-(
You're kinda asking a lot since jb has to be ported over at the moment which naturally leads to glitches such as the restarts. This is the price you pay to run jb months and months before the note is officially updated. at which time the source code will be come available and we will have rock solid jellybean builds. Until then we take what we get. Run the latest release candidate of cm9 until then if you want something super stable.
Also don't you have a backup you can restore? I'm not allowed to feel sorry for you if you never backed up your device.
Sent from my SAMSUNG-SGH-I717 using xda premium
Thanks for the reply JR, your statement " jb has to be ported over at the moment which naturally leads to glitches such as the restarts" is Greek to me. Are you saying that since it is not an official JB update, there will always be glitches? um...ok.
Yes, I have a few backups in there...but as I said, it is stuck in opening boot loop and I don't know how to get in there to restore or flash another ROM. I may be missing a simple fix here but until I know what it is, I don't know what it is. I have used search under boot loop, for an hour and have not found one thread explaining how to get out of it.
Hopefully someone will excuse my ignorance and point me to a thread or explanation of how to get past the boot loop.
Cheers
do you know how to boot into recovery?
if you can, then do that, and restore one of your backups..
if you dont know how to boot into recovery, you shouldn't be flashing roms until you do
AFAIK that means pressing volume up, home, and power until recovery lights up. Done that many times and all I get is the intermittent vibe, no flash, no screen at all.
I've poured over threads and google all day...no love. Just people telling me to restore my backups...gee thanks.
I CAN get it into Odin....can I flash a ROM from there? I followed one tutorial but when selecting a ROM, it wanted a tar file and I either had the ROM zip or unzipped, a bunch of folders with no tar file in any of them.
I'm not a moron, just screwed myself somehow and am looking for some help fixing it. I thought that's what these forums were for.
hold volume up and down and power at the same time; after the first "samsung" on the screen, release the power button, and keep holding the volume up and down, until recovery appears...
XDA is a development forum, not a newbie forum, and there is an assumption that people who flash stuff to their phones will have the basic knowledge to know how to recover from some of the problems that arise when you do something to your phone that requires the knowledge on how to fix things
The fact that you dont know how to get into recovery properly tells me you didnt bother to read and study enough on how to recover from a problem if you have one, sort of like trying to replace your water pump without actually practicing on a car..
search the forums if you need to find .tar files to restore your phone via Odin back to stock; there are several posts and threads that will show you how, but, try to recover your back up first
This ^^^^^. You have jumped into the deep end without knowing how to swim. Watch videos, read how-to's and look up words if you don't understand them. A basic knowledge of computer hardware and how a computer works pre-boot will also go a long way
redman9 said:
Thanks for the reply JR, your statement " jb has to be ported over at the moment which naturally leads to glitches such as the restarts" is Greek to me. Are you saying that since it is not an official JB update, there will always be glitches? um...ok.
Click to expand...
Click to collapse
It means there is no official jelly bean for the note at this time. Our devs have to take jelly bean code and modify it to work on the note which generally means a few hickups here and there.
Sent from my SAMSUNG-SGH-I717 using xda premium
Well thank you all for the help you have given. I was not releasing the power button after the first Samsung flash and thus not finding recovery. I have a functioning phone now, at least. I do, dig deep trying to find answers, and only post when I am truly stuck.
glad you got it fixed!
Ok so I've been unhappy with the 4.0.4 official ATT update and its caused my phone once or twice a day to shut off and I have to pull the battery out. So I got the bright idea to root it. I'm not a stranger to this I had the captivate and infuse before this phone. I had roms on those with no issues. Now I followed this thread http://forum.xda-developers.com/showthread.php?t=1746181 and the phone crashes on bootup saying google account manager has stopped and wont even let me get past it. Then I tried another kernal SGH-I777-ATTGalaxyS2RootStockZedomaxKernel.tar and that just has a yellow ! up and never even gets any further
I've spent 7 hours now in a row reading posts, to be frank, the attitude here SUCKS. Instead of people answering the question they point you off to some post you already read 10 times before, already tried and it doesnt work. I've also tried just putting it back to factory with I777UCKH7-CL503881-No-BL.exe and that doesnt work either
Put your phone in download mode. (power it off, hold down the volume down button and insert the usb cable)
Flash this with Odin in the PDA slot, auto reboot the only thing checked:
http://d-h.st/UWm
So I'm assuming seven hours is a lot for you? I've been reading here for over a year and I'm still learning. Really to root all you would have had to do is flash a kernel in .tar format with Odin (our kernels come with cwm built in remember) obviously you would want one that's compatible with the version of android you're using. There is a lot of information here. But to say the " attitude here sucks" like you did..... Yer wrong. I know sometimes it seems harsh, but we're just trying to get people to do things for themselves and thus learn even more, positively influencing them in the end.
I think I see your problem. Perhaps if you drop the entitlement attitude you might get more help. No one here is obligated to help anyone. The people that do are unpaid volunteers willing to share their expertise. This is NOT the Help Desk. Remember that before you consider making another ungrateful post like this one.
XDA-dev's are free volunteers, first of all.
We are here for the last someyears and we had providing the best help for anyone related to the phones, eventough devs always repeat that dont mirror us, many people do mirror thier works and someone claims tgat they had done it and yet this site is considered as the best resources for android fanboys.
The another thing is that we are professionals who spare our minute free time for the betterment of phones and to.unlock the hidden capabilities of phone.
I could say to you that have patience and patience never makea you sad.....
BE GOOD
Sent from my GT-S5360 using xda app-developers app
If I was a moderator, the last 3 posters would be banned, permanently. Don't you guys have something better to do then to pick at the frustration comments of user who's phone is not working at the moment?
rodimus_prime said:
I've spent 7 hours now in a row reading posts, to be frank, the attitude here SUCKS. Instead of people answering the question they point you off to some post you already read 10 times before, already tried and it doesnt work. I've also tried just putting it back to factory with I777UCKH7-CL503881-No-BL.exe and that doesnt work either
Click to expand...
Click to collapse
Ever hear the expression "you catch more flies with honey than vinegar" ?
Everyone on this forum has been able to load custom firmware using the posts you've been linked to -- everyone except you. So, instead of getting upset with everyone else, take a deep breath and try again.
---------- Post added at 09:47 AM ---------- Previous post was at 09:46 AM ----------
r00t4rd3d said:
If I was a moderator, the last 3 posters would be banned, permanently.
Click to expand...
Click to collapse
Thankfully you're not a moderator.
rodimus_prime said:
Ok so I've been unhappy with the 4.0.4 official ATT update and its caused my phone once or twice a day to shut off and I have to pull the battery out. So I got the bright idea to root it. I'm not a stranger to this I had the captivate and infuse before this phone. I had roms on those with no issues. Now I followed this thread http://forum.xda-developers.com/showthread.php?t=1746181 and the phone crashes on bootup saying google account manager has stopped and wont even let me get past it. Then I tried another kernal SGH-I777-ATTGalaxyS2RootStockZedomaxKernel.tar and that just has a yellow ! up and never even gets any further
I've spent 7 hours now in a row reading posts, to be frank, the attitude here SUCKS. Instead of people answering the question they point you off to some post you already read 10 times before, already tried and it doesnt work. I've also tried just putting it back to factory with I777UCKH7-CL503881-No-BL.exe and that doesnt work either
Click to expand...
Click to collapse
Use the return to stock guide to go back to stock GB. Never go to another site other than ours as the other sites have ad kernels which break wifi or brick phones. Once you flash the GB stock go into 3e recovery and wipe by holding power and both volume buttons. Use the volume keys to move up and down and power to select. If power doesnt work then use home. Once you boot up you can set up or whatever. Next follow the Flash Custom Firmware Without Incrementing Flash Counter. Make sure to use a GB kernel in Mobile Odin. Now you can flash custom roms using CWM if you did it right. If you flash an ICS rom you can use Triangle Away to remove that triangle at boot up. You can also use a jig which is safer and able to be used on any version.
r00t4rd3d said:
If I was a moderator, the last 3 posters would be banned, permanently. Don't you guys have something better to do then to pick at the frustration comments of user who's phone is not working at the moment?
Click to expand...
Click to collapse
You need to be here more than a month to understand where those 3 posters are coming from.
7 hrs wasted. If you want help, shoot me a pm and I'll help you before I get hammered tonight. You have 4 hrs and counting....
jthatch12 said:
7 hrs wasted. If you want help, shoot me a pm and I'll help you before I get hammered tonight. You have 4 hrs and counting....
Click to expand...
Click to collapse
Or PM me cause I won't be hammered. Also reference the guide I posted as well.
I managed to get Serendipity 9.4 loaded on it and its seeming to work however I dont seem to be able to get anything else to not boot loop or fail
I'd be happy with a rooted ICS, dont really need all the fancy stuff but when I try to use this http://forum.xda-developers.com/showthread.php?t=1746181 I cannot get it to load stable, I get bootloops, non stop force closes.
I did seem to fix the power button issue, took it apart and swapped the button with a damaged i777 I had laying around here and thats working now, so really I just need the stock ICS on it and thats the extent of any tinkering I ever want to do with this phone again.
I picked up a Optimus G today as a replacement, god I hate it, the music sounds like garbage and the camera is worse. Theres about zero cases made for it. I have 13 days now to return it so I'm hoping I can resurrect my GS2.
It says to If flashing this from another base, you should perform a wipe data/factory reset before you flash this package, should I flash the package first? Seems like after that I only have 3E recovery instead of clockwork mod, which I need to flash the kernal, or should I do the kernal first? These things are not really detailed
rodimus_prime said:
I managed to get Serendipity 9.4 loaded on it and its seeming to work however I dont seem to be able to get anything else to not boot loop or fail
I'd be happy with a rooted ICS, dont really need all the fancy stuff but when I try to use this http://forum.xda-developers.com/showthread.php?t=1746181 I cannot get it to load stable, I get bootloops, non stop force closes.
I did seem to fix the power button issue, took it apart and swapped the button with a damaged i777 I had laying around here and thats working now, so really I just need the stock ICS on it and thats the extent of any tinkering I ever want to do with this phone again.
I picked up a Optimus G today as a replacement, god I hate it, the music sounds like garbage and the camera is worse. Theres about zero cases made for it. I have 13 days now to return it so I'm hoping I can resurrect my GS2.
It says to If flashing this from another base, you should perform a wipe data/factory reset before you flash this package, should I flash the package first? Seems like after that I only have 3E recovery instead of clockwork mod, which I need to flash the kernal, or should I do the kernal first? These things are not really detailed
Click to expand...
Click to collapse
If you wish to be on stock ICS go ahead and reboot into recovery and factory reset. Next turn off the phone and remove the battery. Plug in the usb to the phone while it's connected to your computer while holding both volume buttons. You should be in download mode now once you press the correct volume button. Now you can use Odin/Heimdall to flash Stock ICS. Note this does contain the EMMC Superbrick bug which is why you factory reset prior to flashing it. If you want a custom rom PM and I can tell you
rodimus_prime said:
It says to If flashing this from another base, you should perform a wipe data/factory reset before you flash this package, should I flash the package first? Seems like after that I only have 3E recovery instead of clockwork mod, which I need to flash the kernal, or should I do the kernal first? These things are not really detailed
Click to expand...
Click to collapse
Seems like your answer is in there already. Kernels can be flashed after with Odin. Use a kernel with CWM if you want that.