Related
I've read all the info I could find here on the brickbug regarding the CWM recovery and the 4.0.4 leaks, but one question that still perplexes me is:
Why does the ROM itself have anything to do with this issue if the flags from the kernel are what triggers the bad erase command in the first place?
I mean, at this point, the ROM isn't even loaded, is it, so why does it matter if we use a custom recovery, say from Siyah, for example, on a leaked ROM, since the CWM recovery is part of the kernel and not the ROM itself?
What am I missing?
donalgodon said:
I've read all the info I could find here on the brickbug regarding the CWM recovery and the 4.0.4 leaks, but one question that still perplexes me is:
Why does the ROM itself have anything to do with this issue if the flags from the kernel are what triggers the bad erase command in the first place?
I mean, at this point, the ROM isn't even loaded, is it, so why does it matter if we use a custom recovery, say from Siyah, for example, on a leaked ROM, since the CWM recovery is part of the kernel and not the ROM itself?
What am I missing?
Click to expand...
Click to collapse
On S2, cwm can be flashed without a kernel
Kernels based on stock and that only include cwm and root are affected if not specifically patched
Sent from my GT-I9100 using Tapatalk 2
donalgodon said:
I've read all the info I could find here on the brickbug regarding the CWM recovery and the 4.0.4 leaks, but one question that still perplexes me is:
Why does the ROM itself have anything to do with this issue if the flags from the kernel are what triggers the bad erase command in the first place?
I mean, at this point, the ROM isn't even loaded, is it, so why does it matter if we use a custom recovery, say from Siyah, for example, on a leaked ROM, since the CWM recovery is part of the kernel and not the ROM itself?
What am I missing?
Click to expand...
Click to collapse
Your missing nothing actually, you are totally right in the fact its the kernel itself, but since the kernel is part of the rom, when you flash with odin, that is the reason the warnings are about...
so the best thing is actually just avoid the specific roms, and have a known good kernel...
FWX
Hi all,
I have had my S3 since July '12 and in true Android style rooted it and started flashing ROM's left right and centre. Eventually I stuck on Omega, mainly because I got bored of continually flashing a ROM, installing my fave apps, restoring backups from Titanium, setting up my settings etc...
Christmas eve came and, having some time off work, I decided to start flashing some new ROM's...
Jump forward a few hours.... Tried CM10... liked it but wanted more of the Google/stock bits and pieces back so went to flash another ROM off XDA.
All of a sudden the phone goes off. Phone hard bricked. Wouldn't turn on, wouldn't charge... I shat myself.
I got a little brave and RMA'd to Samsung hoping that if its hard bricked they'll just swap the system board or whatever, and thankfully, a few weeks later and I have my phone back. Yay me!
First thing phone does when I connect to my home Wifi, OTA. Only a small update, and wasn't really paying attention as I was still setting up the phone.
Left it stock for a week and then decided I needed root. Rooted phone using the Samsung S3 all in on toolkit v7 from the XDA boards. All well.
So now I'm a little gun shy of flashing my phone, especially after reading a note in Christiano Matos' ROM thread for crDroid v11 about flashing various Bootloaders; and admittedly not properly understanding it as it seems a little Google-translate jumbled up.
Also http://crave.cnet.co.uk/mobiles/samsung-galaxy-s3-sudden-death-security-flaw-fixed-in-uk-50010094/ makes me a little nervous...
Is the 'hard brick' a hardware fault (and as such I wouldn't link it to any software or ROM I installed and something I'd hope my replacement phone wouldn't suffer twice) or a software issue that can be exploited (in which case which update is it that fixes it and do all decent ROM's include this update)?
And finally, what ROM do people suggest? I want to get rid of the Samsung bloat and have a nice speedy UI with plenty of battery life.
(ignore the FoxHound banner in my sig!!)
Post from crDroid thread:
Quote:
- SAMSUNG APPARENTLY SUDDEN DEATH PREVENT: AS YOU GUYS KNOW SOME S3 I9300 IS SUFFERING WITH A WEIRD BUG THAT SIMPLY ENDS IN SUDDEN DEATH .
USE WITH LAST STOCK, PERSEUS, BOEFFLA OR YANK55.LU KERNELS AND PHILZ RECOVERY.
THIS LATEST FIRMWARE XXELLA COMES WITH NEW BOOTLOADER APPARENTLY THAT FIX THIS BUG. THE BAD NEWS IS: THIS BOOTLOADER CAN ONLY BE INSTALLED THROUGH ODIN PACKAGE. BUT WE DON'T WANT THIS, RIGHT?
FLASHING THIS BOOTLOADER BECOME UNABLE TO GET BACK TO THE OLD ONE. BINARY COUNTER CAN'T BE RESETED (STAY ALWAYS WITH 1 COUNT).
HERE IS A LINK WITH BOOTLOADER FILES. ONLY FLASH IT WITH ODIN PC AND PUT IN PDA FIELD.
If you're scared then just don't do it.
I highly doubt your brick had anything to do with flashing ROMs, just Samsung ****ing up on the hardware front again.
You don't really need to flash any new bootloaders etc. because if it breaks like it did before,you know what's going to happen - Samsung will fix your phone, and that's it.
If you don't like the stock Samsung firmware, try CM10.1. Read about bugs etc. before you start crying about things not working though, because it still isn't, and most probably never will be 100% stable.
bortak said:
If you're scared then just don't do it.
I highly doubt your brick had anything to do with flashing ROMs, just Samsung ****ing up on the hardware front again.
Click to expand...
Click to collapse
Exactly what I thought, until I hardbricked my cousins S2 on the weekend. Never ever thought it could happen. Seems like Samsung is releasing firmware/kernels on the S2 that can hardbrick a phone whenever any sort of wipe is performed in cwm recovery.
Sticky from the S2 forum:
http://forum.xda-developers.com/showthread.php?p=36947154
Anyway, this is the last thing I wanted to hear. Fingers crossed it was just a one off and not actually related to flashing.
Sent from my GT-I9300 using xda premium
well, basically if you don't touch BOOTLOADER staff , it should be highly unlikely to brick devices , except in the case they released problematic firmware as once i bricked my Nexus S with problematic bootloader released by Google... damn it ...
only thing concerns me about S3 is SDS , but i have installed patched recovery and kernel i think i can breath a little easier now ... but still don't like taking ticking bomb around my pocket... it really sucks...
Seems like Samsung is releasing firmware/kernels on the S2 that can hardbrick a phone whenever any sort of wipe is performed in cwm recovery.
Click to expand...
Click to collapse
You are referring to the brickbug in _leaked_ firmware builds. All official releases by Samsung are not affected.
Also the bug is not only triggered by CWM but by every major operation when a kernel with the MMC_CAP_ERASE flag set.
but still don't like taking ticking bomb around my pocket... it really sucks...
Click to expand...
Click to collapse
Afaik the problem was related to a ****-up in the SSD's wear leveling - so if it is fixed it is fixed =)
Btw, just because it is _now_ impossible to reset the flash counter does not mean it will never be. Samsung does not use eFuse's so there is always a hidden switch that can be reset =)
For CM10 - I never expected the full functionality that Samsung's own firmware had, or at least not the polish and extra apps that are bundled but to be honest, I can live without SVoice, kies etc.
I have read the thread on SDS and have checked my phone with eMMC check (and also advised three others who I work with to check their S3's too), and I have also updated recovery (TWRP) to latest version so I should have some protection... shouldnt I?
I think I will stick with stock for now, see what comes in the future, and what Samsung release through OTA etc. (BTW phone was bought outright by me so is UK Unlocked, no branding).
Dear @OP.
Feel free to answer all your questions by yourself. I'd recommend you to stop being lazy, move your ass and read a few things, starting from here as it triggered your attention.
Furthermore, personally I would recommend you to read carefully this to avoid your threads being locked.
In relation to above, I'd like to recommend you visiting this section of XDA Froums, if you want to use something customized. If not, feel free to use this top secret trick to find Stock ROMS here on XDA....
Wow! Who knew! Consider me put in my place... [edit]
Now I will go and beat myself with a wet towel tied in a knot at the end.
If you want to flash the ELLA firmware then flash it but if you need to get bacck to an older bootloader to reset you counter with Triangle Away then flash the CWM Zip below in recovery.Its an oldr bootloader thats CWM flashable.Perfectly safe as Ive flashed it myself.The SDS problem will be in all i9300 models that have the emmc 0xf1 revision chip.You can check it with this app.Doesnt matter if it says you are safe or not as it wrongly checks for the error.
https://play.google.com/store/apps/...sIm5ldC52aW5hZ3JlLmFuZHJvaWQuZW1tY19jaGVjayJd
Flash an official firmware and then a custom kernel with the SDS patch fix.Im using yank555
cooza said:
If you want to flash the ELLA firmware then flash it but if you need to get bacck to an older bootloader to reset you counter with Triangle Away then flash the CWM Zip below in recovery.Its an oldr bootloader thats CWM flashable.Perfectly safe as Ive flashed it myself.The SDS problem will be in all i9300 models that have the emmc 0xf1 revision chip.You can check it with this app.Doesnt matter if it says you are safe or not as it wrongly checks for the error.
https://play.google.com/store/apps/...sIm5ldC52aW5hZ3JlLmFuZHJvaWQuZW1tY19jaGVjayJd
Flash an official firmware and then a custom kernel with the SDS patch fix.Im using yank555
Click to expand...
Click to collapse
Thanks for that Cooza; one thing there I didn't know; you can flash a 3rd party kernel to a stock firmware.
cooza said:
If you want to flash the ELLA firmware then flash it but if you need to get bacck to an older bootloader to reset you counter with Triangle Away then flash the CWM Zip below in recovery.Its an oldr bootloader thats CWM flashable.Perfectly safe as Ive flashed it myself.The SDS problem will be in all i9300 models that have the emmc 0xf1 revision chip.You can check it with this app.Doesnt matter if it says you are safe or not as it wrongly checks for the error.
https://play.google.com/store/apps/...sIm5ldC52aW5hZ3JlLmFuZHJvaWQuZW1tY19jaGVjayJd
Flash an official firmware and then a custom kernel with the SDS patch fix.Im using yank555
Click to expand...
Click to collapse
Kind sir,you can reset the counter on the new bootloader as long as you are running stock kernel and stock recovery! last night i flashed trough modile odin the stock kernel and the stock recovery over philz recovery ,and after i used triangle away without any problems!
bottom line short,with the new bootloader you cannot reset the counter while you are runing custom kernel and/or custom recovery!
Okay, before any of the regular contributors here say something nasty to me for asking a question that's been asked and answered, I want you to know that I have spent 2 days reading through -all- xda forums that might even -remotely- relate to my problem, without finding any answers. I also spent several hours searching all the common Android forums elsewhere, as well as, silly sites like Yahoo answers, etc., but have not been able to find the answer to my question. I'm the first to admit that reading the exorbitant amount of information in here causes my brain to short circuit due to all the numbers, versions, etc. It's like reading tax code; use C1.4.6 unless you've submitted b45.1. In that case, use d16.9, unless you've also filed a p32 in the last 2 years...if so, then....blah blah blah.
I love all you cell phone OS gurus and am quite envious of your ability to effortlessly wade through the technology involved in these phones. I wish, wholeheartedly, that I didn't have to ask any questions here because I know how irritated many of you become over people like me asking stupid questions, but I have no where else to turn. Believe me, if I could go elsewhere, I would, for your sake.
I was running 2.3.4, rooted, stock ROM. Froze the system with TB Pro to prevent the upgrade to 2.3.6. Unfroze it. Upgraded. Decided to unroot so I could sell my phone in favor of another. Ran Odin. Ran SuperOneClick. Ahhh...and there's the problem. SOC doesn't work with 2.3.6. So now, I don't know what to do. My phone is half rooted. I can't unroot and I can't reroot. I get the triangle, but TB Pro doesn't work because I'm not rooted, well. sort of not rooted. I guess I'm a little rooted. I don't know what to do next mainly because, every time I find what I think is a solution, I find another source that says, "DON'T DO IT! YOU'LL BRICK YOUR PHONE!" So, here I am, hoping someone will point me in the right direction without chastising me for asking a stupid question. I checked the solution in here and it's great, except, and I quote "Not working for KK6 2.3.6"
Thanks for any help....
So, what you need to do at this point is flash back to stock 2.3.4 using the instructions in the How to prepare your phone ... thread which is a sticky in the general section of this I777 forum. Since you were stock before, and evidently didn't flash any custom firmware, you should be fine flashing the stock distribution with Odin or Heimdall, or using the Odin one-click downloader.
First enter 3e recovery and perform a wipe data/factory reset, then do the Odin or Heimdall flash. The thread has instructions to clear your personal data as well.
Now, you know, I read that post along with all the stickies, about how to return the phone to stock, but I couldn't find any mention of whether or not it worked with a half rooted phone. I didn't want to be one of those people who blindly followed directions not intended for her situation, only to wind up bricking my phone or in a constant boot loop.
Thank you for not criticizing me for my apparent stupidity. I do my best.
Thank you so much for pointing me in the right direction.
tunie said:
Now, you know, I read that post along with all the stickies, about how to return the phone to stock, but I couldn't find any mention of whether or not it worked with a half rooted phone. I didn't want to be one of those people who blindly followed directions not intended for her situation, only to wind up bricking my phone or in a constant boot loop.
Thank you for not criticizing me for my apparent stupidity. I do my best.
Thank you so much for pointing me in the right direction.
Click to expand...
Click to collapse
You can't have a "half rooted" phone, and it wouldn't matter at all anyway since you're going to be booting into download mode in order to flash to stock.
Sent from my Zanpakuto using Getsuga Tensho!
First of all:
Understand what 'ROOT' is.
IT IS ADMINISTRATOR ACCESS TO YOUR DEVICE, NOTHING MORE, NOTHING LESS.
everything for 'root' resides in the OS under the /system partition...which means when you load a new/stock rom on it, everything in /system gets wiped...
root has nothing to do with recovery mode or download mode. you cant be 'half-rooted'. you either have administrator access or you dont, plain and simple.
When I rooted so very long ago, I used SGH-I777_ClockworkMod-Recovery_5.0.2.3 that I downloaded with su-3.0-efgh-signed. At the time, I didn't understand what this was. I only understood that this would root my phone. I didn't want to flash any custom ROM's because, to this day, I really don't understand what a ROM is. Yes, I've read about it. Still don't get it. So, did I flash a custom ROM? As far as I knew, all I did was root so I could use TBPro to backup and freeze, and use LBE to keep my information as private as possible.
<edit> So I've just reread many of your posts. You really are great at explaining this stuff and I thank you for that. It seems, from what I've read, that I can just do a factory reset and the phone should go back to its original state, with 2.3.4. Is that correct?
Thank you, again. I swear I'll be out of everyone's hair in here as soon as is humanly possible.
creepyncrawly said:
So, what you need to do at this point is flash back to stock 2.3.4 using the instructions in the How to prepare your phone ... thread which is a sticky in the general section of this I777 forum. Since you were stock before, and evidently didn't flash any custom firmware, you should be fine flashing the stock distribution with Odin or Heimdall, or using the Odin one-click downloader.
First enter 3e recovery and perform a wipe data/factory reset, then do the Odin or Heimdall flash. The thread has instructions to clear your personal data as well.
Click to expand...
Click to collapse
Pirateghost said:
First of all:
Understand what 'ROOT' is.
IT IS ADMINISTRATOR ACCESS TO YOUR DEVICE, NOTHING MORE, NOTHING LESS.
everything for 'root' resides in the OS under the /system partition...which means when you load a new/stock rom on it, everything in /system gets wiped...
root has nothing to do with recovery mode or download mode. you cant be 'half-rooted'. you either have administrator access or you dont, plain and simple.
Click to expand...
Click to collapse
Thank yes, I understood what root was which is why I did it. I just didn't understand the mechanics of getting there. Perhaps it's the same thing that made pre-med chemistry so difficult for me in college. I could do the work, but didn't get the big picture, so I couldn't build a knowledge base. Anyway, I see the triangle and GT I9100 at boot up, yet I cannot access TB Pro as it states I'm not rooted. So, I guess I did unroot, but didn't go all the way because 2.3.6 doesn't play nice with popular root/unroot apps. Thanks for explaining.
tunie said:
Thank yes, I understood what root was which is why I did it. I just didn't understand the mechanics of getting there. Perhaps it's the same thing that made pre-med chemistry so difficult for me in college. I could do the work, but didn't get the big picture, so I couldn't build a knowledge base. Anyway, I see the triangle and GT I9100 at boot up, yet I cannot access TB Pro as it states I'm not rooted. So, I guess I did unroot, but didn't go all the way because 2.3.6 doesn't play nice with popular root/unroot apps. Thanks for explaining.
Click to expand...
Click to collapse
The triangle has nothing to do with root. It only means you flashed a kernel using Odin.
Sent from my Galaxy Nexus
tunie said:
It seems, from what I've read, that I can just do a factory reset and the phone should go back to its original state, with 2.3.4. Is that correct?
Click to expand...
Click to collapse
No. When you do a wipe data/factory reset, this wipes the data partition but does not touch the system partition. So you will still have whatever firmware you started with, which in your case I believe is 2.3.6, but it will be put back to like it was when it was first installed.
That's why I recommended that you perform a wipe data/factory reset, and then flash the 2.3.4 stock firmware. The factory reset is so that when the new 2.3.4 stock firmware boots up, there will be no problems.
Pirateghost said:
The triangle has nothing to do with root. It only means you flashed a kernel using Odin.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Well thank you. I give up. Really, I do.
creepyncrawly said:
No. When you do a wipe data/factory reset, this wipes the data partition but does not touch the system partition. So you will still have whatever firmware you started with, which in your case I believe is 2.3.6, but it will be put back to like it was when it was first installed.
That's why I recommended that you perform a wipe data/factory reset, and then flash the 2.3.4 stock firmware. The factory reset is so that when the new 2.3.4 stock firmware boots up, there will be no problems.
Click to expand...
Click to collapse
Well, I actually understand that. Thank you. My concern now is whether or not I flashed a custom ROM. Clockworkmod appears to be a custom ROM, no? If it isn't, I know what to do, thanks to you. If it is a custom ROM, I don't know what to do next.
tunie said:
Well, I actually understand that. Thank you. My concern now is whether or not I flashed a custom ROM. Clockworkmod appears to be a custom ROM, no? If it isn't, I know what to do, thanks to you. If it is a custom ROM, I don't know what to do next.
Click to expand...
Click to collapse
clockwork mod is NOT a custom ROM. clockwork mod is RECOVERY and on this device it is compiled WITH the kernel.
YOU HAVE A CUSTOM/MODIFIED KERNEL
I really dont understand why you dont just follow creepyncrawly's advice and tutorials...you are making this out WAAAAAY harder than it really is.
Pirateghost said:
clockwork mod is NOT a custom ROM. clockwork mod is RECOVERY and on this device it is compiled WITH the kernel.
YOU HAVE A CUSTOM/MODIFIED KERNEL
I really dont understand why you dont just follow creepyncrawly's advice and tutorials...you are making this out WAAAAAY harder than it really is.
Click to expand...
Click to collapse
Just want to insure that I've relayed all the necessary information, correctly. I guess I have. Thank you and I'm sorry I took anyone's time.
tunie said:
Well thank you. I give up. Really, I do.
Click to expand...
Click to collapse
That dreaded yellow triangle show up when you flash a custom (non-stock) kernel. When you flash a stock kernel, it will go away. So... if you flash back to stock like I suggested, it will go away.
Pm me if you need more assistance
creepyncrawly said:
So, what you need to do at this point is flash back to stock 2.3.4 using the instructions in the How to prepare your phone ... thread which is a sticky in the general section of this I777 forum. Since you were stock before, and evidently didn't flash any custom firmware, you should be fine flashing the stock distribution with Odin or Heimdall, or using the Odin one-click downloader.
First enter 3e recovery and perform a wipe data/factory reset, then do the Odin or Heimdall flash. The thread has instructions to clear your personal data as well.
Click to expand...
Click to collapse
Thank you. It worked like a charm. Back to stock. Wonderful. Thank you so much. It wasn't as much a nail-biter as I thought it would be.
Wow! I need some help. I've acquired a Samsung Galaxy Note (i717, I believe) that shows all the signs of being healthy (appearance, touch screen, etc.) but persistently slows down at the ATT opening splash screen, begins to load Android, dies and reboots. Whatever variant rooted ROM I received it with (sluggish and unreliable) I have written over and now I can't get any farther than the Android settings screen. Therefore I do not know the exact version nor can I begin to set it up (wifi, etc.).
That's the 'presenting problem', so let me explain what I've done to this point (about 25 hrs. worth!). I have reloaded latest version of CWM (runs great) and then Padawan JB . . . same symptoms. I have loaded the ATT JB and ICS via the latest Odin successfully . . . with same symptoms. I have loaded TWRP (touch screen is snappy and works as it should) and Padawan JB again . . . with same symptoms. I have wiped caches before, after, and in between till I'm blue in the face, each time with the same symptoms. Most recently I have done a hard reset to native/factory settings . . . with no change! I've tried to scour the XDA (and any other sites) trouble shooting articles and seem to have come to a dead end.
Here's a couple things that I'm wondering: because I can't get deep enough into Android to check out the model number, could the phone be something other than an ATT model? At the top of the front face it simply says 'Samsung', not ATT at top and Samsung at bottom like my previous ATT Note. Right after boot I persistently get an ATT splash screen which would lead me to believe that it is ATT. Is there some other way to find model, say in TWRP? Do I need a phone specific version of Android? Second, everything seems to be working fine physically (i.e., no hardware problems). Could this thing have gotten a virus in an earlier life that's preventing the ROM from working right? I've not been able to get far enough to register it with my cell provider (second party, not ATT). Must you be up and running with the cell service to correctly load and use the ROM (wouldn't think so)? And if so, how without Android working? I've been using and playing with computers for 25 years, but I'm fairly new to the Android system (but learning fast!) Any help would sure be appreciated. I'd really like to resurrect this baby. I loved my first Note (till it fell off the car and disappeared).
pstrulm said:
Wow! I need some help. I've acquired a Samsung Galaxy Note (i717, I believe) that shows all the signs of being healthy (appearance, touch screen, etc.) but persistently slows down at the ATT opening splash screen, begins to load Android, dies and reboots. Whatever variant rooted ROM I received it with (sluggish and unreliable) I have written over and now I can't get any farther than the Android settings screen. Therefore I do not know the exact version nor can I begin to set it up (wifi, etc.).
That's the 'presenting problem', so let me explain what I've done to this point (about 25 hrs. worth!). I have reloaded latest version of CWM (runs great) and then Padawan JB . . . same symptoms. I have loaded the ATT JB and ICS via the latest Odin successfully . . . with same symptoms. I have loaded TWRP (touch screen is snappy and works as it should) and Padawan JB again . . . with same symptoms. I have wiped caches before, after, and in between till I'm blue in the face, each time with the same symptoms. Most recently I have done a hard reset to native/factory settings . . . with no change! I've tried to scour the XDA (and any other sites) trouble shooting articles and seem to have come to a dead end.
Here's a couple things that I'm wondering: because I can't get deep enough into Android to check out the model number, could the phone be something other than an ATT model? At the top of the front face it simply says 'Samsung', not ATT at top and Samsung at bottom like my previous ATT Note. Right after boot I persistently get an ATT splash screen which would lead me to believe that it is ATT. Is there some other way to find model, say in TWRP? Do I need a phone specific version of Android? Second, everything seems to be working fine physically (i.e., no hardware problems). Could this thing have gotten a virus in an earlier life that's preventing the ROM from working right? I've not been able to get far enough to register it with my cell provider (second party, not ATT). Must you be up and running with the cell service to correctly load and use the ROM (wouldn't think so)? And if so, how without Android working? I've been using and playing with computers for 25 years, but I'm fairly new to the Android system (but learning fast!) Any help would sure be appreciated. I'd really like to resurrect this baby. I loved my first Note (till it fell off the car and disappeared).
Click to expand...
Click to collapse
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory reset in between.
fbauto1 said:
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory
I would reflash cwm thru odin after that I would flash the latest TWRP 2.5. Then you can flash whatever. If padawan is givin u problems try something else like AOSP or AOKP. Padawan is TW based. JaimeD builds are pretty sweet.
sent from my GalaxySuperNote running OC Padawan JB
Click to expand...
Click to collapse
androidmechanic said:
fbauto1 said:
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory
I would reflash cwm thru odin after that I would flash the latest TWRP 2.5. Then you can flash whatever. If padawan is givin u problems try something else like AOSP or AOKP. Padawan is TW based. JaimeD builds are pretty sweet.
sent from my GalaxySuperNote running OC Padawan JB
Click to expand...
Click to collapse
If you want TWRP, flash TWRP. No need to flash CWM
Click to expand...
Click to collapse
AT&T Phones have a [logo}AT&T] on the top-center!!
But if you are in doubt, use kies to do a full recovery-restore [WILL ERASE EVERYTHING ON YOUR DEVICE].
See post #4 on this thread.
fbauto1 said:
androidmechanic said:
If you want TWRP, flash TWRP. No need to flash CWM
Click to expand...
Click to collapse
If you go thru Odin you would have cwm first. With the problems talked about, I would go back factory stock then re-root with Odin. Then thru cwm, flash twrp or whatever floats your boat.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
androidmechanic said:
If you go thru Odin you would have cwm first. With the problems talked about, I would go back factory stock then re-root with Odin. Then thru cwm, flash twrp or whatever floats your boat.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
fbauto1 said:
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
Click to expand...
Click to collapse
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
fbauto1 said:
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
Click to expand...
Click to collapse
androidmechanic said:
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
you are both actually correct, however, I am looking at PSTRULM's stats. if he is anything like me when I started, the more simple and less complication involved in the process, the more he may understand.
ANDROIDMECHANIC is stating the most basic and beginner way to do this and understand simply. after doing this a few times as I did, the basic mechanics of the process will become more fluent.
then he can make his own decisions as to methods which might be easier for him, without confusing.
I am sure you both are a huge help to everyone and I thank members such as yourself for your efforts. ME, I prefer baby steps, cause I know I can really EFF things up if I get confused
androidmechanic said:
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Just a reminder.. when flashing through Odin, make sure it's an ODIN-flashable tarball, i.e., you can't flash a recovery-type zip through Odin and vice versa.
I've beeing trying to change my ROM. I'm trying to install Clockworks recovery and it doesn't work. I've tried using Rom Manager, EZ recovery and doing it manually. Each time it just goes into the default recovery. I've also tried twrp. Any help?
GT-I9200T
Andriod version: 4.1.2
I assume you mean you have an I9100T ?
1) The reason your recovery isn't sticking after you reboot is because recovery is 'baked' into the kernel on the I9100, so any recovery flashed independently will only persist until the next reboot.
2) Do not use Rom Manager with the I9100. At all. Ever.. Eventually, it will break recovery & cause your phone to reboot. The only fix is to flash stock via Odin & do a factory reset. And as most people here don't make regular backup, it sucks to be you in this situation because you lose your data.
3) Easiest way to get CWM that will stick is to flash a custom kernel; you have several options, a search will reveal your choices (PhilZ seems to be what many people use these days for simplicity's sake). From there you can then flash whatever custom rom (or kernel) you want.
If you don't have an I9100, clarify exactly what you have & we'll organise mods to move your thread.
MistahBungle said:
I assume you mean you have an I9100T ?
1) The reason your recovery isn't sticking after you reboot is because recovery is 'baked' into the kernel on the I9100, so any recovery flashed independently will only persist until the next reboot.
2) Do not use Rom Manager with the I9100. At all. Ever.. Eventually, it will break recovery & cause your phone to reboot. The only fix is to flash stock via Odin & do a factory reset. And as most people here don't make regular backup, it sucks to be you in this situation because you lose your data.
3) Easiest way to get CWM that will stick is to flash a custom kernel; you have several options, a search will reveal your choices (PhilZ seems to be what many people use these days for simplicity's sake). From there you can then flash whatever custom rom (or kernel) you want.
If you don't have an I9100, clarify exactly what you have & we'll organise mods to move your thread.
Click to expand...
Click to collapse
Sorry, I've got a 19100T. My bad. As for losing data I don't mind, I've got my contacts backed up and that's all I need. It seems PhiZ is only for Galaxy S4's. :crying:
Also what about Rom Toolbox? Will that be bad aswell?
AcademyA said:
Sorry, I've got a 19100T. My bad. As for losing data I don't mind, I've got my contacts backed up and that's all I need. It seems PhiZ is only for Galaxy S4's. :crying:
Click to expand...
Click to collapse
No, PhilZ is not only for Galaxy S4's. The S4 version is a recovery only, as the partition layout on the I95x phones is different (kernel & recovery are separate). PhilZ for the I9100 is a kernel with recovery built into it.
You should be able to find the thread easily; I found it in 2.3 seconds with a Google search 'I9100 PhilZ XDA' at top of results. As to which file to use, you need to take the time to read the thread to work that out for yourself. Failure to read/learn before doing leads to busted phones.
MistahBungle said:
No, PhilZ is not only for Galaxy S4's. The S4 version is a recovery only, as the partition layout on the I95x phones is different (kernel & recovery are separate). PhilZ for the I9100 is a kernel with recovery built into it.
You should be able to find the thread easily; I found it in 2.3 seconds with a Google search 'I9100 PhilZ XDA' at top of results. As to which file to use, you need to take the time to read the thread to work that out for yourself. Failure to read/learn before doing leads to busted phones.
Click to expand...
Click to collapse
When finding the Kernel code, I type in getprop in terminal. I see stuff like the build number but I can't find the Kernel code anywhere. The only thing I see that is related to Kernel is ro.kernel.qemu: [0]
What are you doing in terminal ? You're overthinking this. I realise it's in the thread, but that's completely unnecessary nonsense
Phone settings/about device - build number.
My final post to this thread. You're on your own.
Alright! Everything's working now. Thanks for the help.