Sadly, my first post on XDA is a major problem with my SPH-L710. I found a ROM built specifically for the Sprint variant of the Galaxy S III, and it was a vanilla AOSP Android ROM, built from source by the developer. I read that it was all custom built and freshly made, except for a few things, including the kernel (which was I believe borrowed from CM 10) to get the ROM to actually work. So I flashed it after doing a factory wipe/reset in CWM Recovery, and set it up, and MY GOSH this ROM was A Nexus and a half! It was gorgeous! So I thought, hey, why not try to get a kernel to overclock and make this gorgeous ROM run faster and smoother. I found a kernel on XDA called matrix or matr1x kernel, and flashed the 3.4.y version. What I noted on the kernel's page was that there was a 3.0.y and a 3.4.y, which are NOT interchangeable, and I have a feeling that I made the wrong choice. I used CWM Recovery to install the kernel (also probably wrong, I should've used mobile odin...) and rebooted the phone. It died there. Black, unresponsive screen. Buttons do nothing. Had some help before now, and learned that the phone is trying to boot, but crashing ten seconds or so in. If anyone has any ideas or solutions, please don't hesitate to share.
Where did you find this kernel? Cause if it's not built specifically for the Sprint GS3 that's where you went wrong.
Try reflashing the rom if you can get into recovery.
Sent from the future via Xparent Green Tapatalk 2
edfunkycold said:
Where did you find this kernel? Cause if it's not built specifically for the Sprint GS3 that's where you went wrong.
Try reflashing the rom if you can get into recovery.
Sent from the future via Xparent Green Tapatalk 2
Click to expand...
Click to collapse
As Ed said (hey, that rhymes!), if you can't get into recovery or download mode, you're kind of screwed.
If you flashed a kernal made for the US GS3 (and not the international version, i9300), you're not hard-bricked, just soft-bricked. Those are much easier (and cheaper) to fix.
Let's first see if you can get into recovery mode.
First off, boot into recovery (power off phone, then power on phone while holding Up and the home button).
How to fix your phone if you can access Recovery Mode.
If that works, you can just restore your nandroid backup you made before trying out a new Rom/Kernal. You made a nandroid backup, right? Right?!?!?!
If you didn't, you're not completely screwed. You can re-flash the Rom you originally had installed (which should wipe out the custom kernal and replace it with the one from the Rom. I'd recommend, though, that you wipe system, data, cache and dalvik cache before flashing it. That'll make sure nothing is left behind from the kernal.
If that doesn't work, you can try getting into download mode
How to get into download mode.
Boot into recovery (power off phone, then power on phone while holding Down and the home button).
How to fix your phone if you can access Download Mode.
You're going to have to flash a stock tar file. I'd recommend Sextape's stock rooted md4 file from their forums, but there are other tar files floating around if you care to find them. Just follow the directions on their page and you'll have your phone back up and running again.
If you can't access Download or Recovery mode, then:
How to fix your hard-brick. (JTAG Repair)
Well, if you can't access either Recovery or Download mode, congratulations, you have officially hard-bricked your phone. The only way to get the phone back to working order it to get a JTAG repair. There are a number of sites that do this, and the typical cost is around $60. Just search google for "JTAG Repair galaxy S3" and you'll find them easily.
Hopefully this has helped.
Well he either bricked it, kicked it or is just simply lost.
Sent from the future via Xparent Green Tapatalk 2
Source of the ROM!
I found the ROM I used, and will reflash when I get my phone back from the Sprint shop. I recommend this highly to anyone with a Sprint version of the Galaxy 3 III. Here's the thread, and maybe you'll understand the issue with a new kernel better and have a good time.
http://forum.xda-developers.com/showthread.php?t=2216538
thenexusgeneration said:
I found the ROM I used, and will reflash when I get my phone back from the Sprint shop. I recommend this highly to anyone with a Sprint version of the Galaxy 3 III. Here's the thread, and maybe you'll understand the issue with a new kernel better and have a good time.
http://forum.xda-developers.com/showthread.php?t=2216538
Click to expand...
Click to collapse
You should also understand that you can't just flash any kernel made for the same android version. It had to be made for your phone as well or else it contains useless instructions.
I don't see any matrix kernel in our forums either.
CNexus said:
You should also understand that you can't just flash any kernel made for the same android version. It had to be made for your phone as well or else it contains useless instructions.
I don't see any matrix kernel in our forums either.
Click to expand...
Click to collapse
Thank you Cnexus, I bite my tongue last night because the question posted to him was where did he find the Kernel not the rom. Since I couldn't find this kernel and obviously you couldn't either it's not a Sprint variant kernel. If he flashes that kernel again he will be taking another ride to Sprint.
Sent from the future via Xparent Green Tapatalk 2
I still want to know if he was actually hard bricked! I was hoping it was only a soft brick. But I guess my thirst for knowledge will never be quenched.
Sent from my SPH-L710 using xda app-developers app
The Kernel!
So, I found the kernel on XDA, and it is here: http://forum.xda-developers.com/showthread.php?t=2134894 And I don't think any of us will ever know what I managed to do to my phone. I flashed the 3.4.y version, and I believe my ROM was a 3.0.y based one. Have fun guys.
topherk said:
I still want to know if he was actually hard bricked! I was hoping it was only a soft brick. But I guess my thirst for knowledge will never be quenched.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Topherk if he did flash the BMS then he wasn't hard bricked at all. But in his OP he said he flashed Matrix Kernel how he got matrix from BMS is beyond me. He could have simply wiped all data reflash ed his rom and booted back up. So you where right no brick at all.
Sent from the future via Xparent Green Tapatalk 2
Related
My phone kept looping on the loading screen, so i pulled the battery and got in CWM. When i did a data wide so i can restore from a saved file the phone got stuck on wiping.
So i pulled the battery and the phone kept on looping the samsung logo and would not go back to CWM, got inside ODIN and tried the stock one click EL29 ODIN method, everything flashes but gets stuck on data.bin. i re-start the process to only be stuck in the same data.bin step. the ODIN one click pro does not stop responding it just gets stuck.
I tried the ODIN method where i load the stock none rooted tar file in pda mode, this method completely passes but when it restarts it goes back to loop mode.
I tried getting into recovery mode but it loops also (Holding Volume up and power)
I am currently trying a different ODIN oneclick TAR file, maybe this will work, i will update when it finishes.
I do not know what to do next, i have flashed all individual files in ODIN also.
http://forum.xda-developers.com/showthread.php?t=1525495
Seriously again and you can't search.......you are bricked.....
http://forum.xda-developers.com/showthread.php?t=1504808
And you were using a ics kernel with cwm huh ?
Sent from my SPH-D710 using Tapatalk 2
I did search all over xda and androidcentral, i was in ics 4.0.4. Thanks for the links i left the phone flashing, when i get home i will read those threads. If it all fails ill just go to sprint tech bench and get a refurbish replament.
You were on a ics ROM ?
Used a ics kernel to wipe data ?
Were using ROM manager?
Using touch cwm ?
Didn't read OP for the ROM either ?
Almost all ics roms will tell you not to use a ics kernel with cwm that is the cause of the bricks ...
If you can answer yes to any of the above you didn't read enough... There are a dozen threads about bricking phones on here that would have saved your phone....good luck at sprint getting it replaced
Sent from my SPH-D710 using Tapatalk 2
mrperez816 said:
I did search all over xda and androidcentral, i was in ics 4.0.4. Thanks for the links i left the phone flashing, when i get home i will read those threads. If it all fails ill just go to sprint tech bench and get a refurbish replament.
Click to expand...
Click to collapse
What were u using to flash ? The OP of every aosp ROM Wether cm9 codename aokp all say to flash the el26 cwm kernel and flash from there and if going back to GB to use a stock tar and then go from there ...
Sent from my SPH-D710 using Tapatalk 2
i had CWM, i was running ics 4.0.4 fine build 30 since it came out. It just started the stupid animation loop and thats when i decided to do a data wipe in CWM. but then i did the ODIN One Click and it gets stuck on data.bin.
I work for Sprint....
This is my first time ever posting on any forums and i have been flashing since the EVO came out, i have flashed ICS to the EVO 4G and back to GB with no issues, this phone is the first to give me such issues.
mrperez816 said:
i had CWM, i was running ics 4.0.4 fine build 30 since it came out. It just started the stupid animation loop and thats when i decided to do a data wipe in CWM. but then i did the ODIN One Click and it gets stuck on data.bin.
I work for Sprint....
This is my first time ever posting on any forums and i have been flashing since the EVO came out, i have flashed ICS to the EVO 4G and back to GB with no issues, this phone is the first to give me such issues.
Click to expand...
Click to collapse
Samsung screwed us by changing some partitions and until we get source to know what they did its best to follow the OP to a T because no one has bricked when using a GB kernel to wipe or flash ....just the ics ones
Yes I had og evo nexus s and 3d ....this one sucks to have to flash the way we do but its the better phone so you do what you have to
Sent from my SPH-D710 using Tapatalk 2
You could have not said it any better lol, i on purpose broke my photon 4g and one of the replacements on the list was the E4GT and got that one sent to me lol, such an amazing phone but issues like this kill me. i did that rouge in odin and it just loops on the android with the box but does not do anything else.
Ill keep trying different things, custom count is at 3 maybe by the time i give up it might be in the 100's because i wont get a replacement till tuesday...
mrperez816 said:
You could have not said it any better lol, i on purpose broke my photon 4g and one of the replacements on the list was the E4GT and got that one sent to me lol, such an amazing phone but issues like this kill me. i did that rouge in odin and it just loops on the android with the box but does not do anything else.
Ill keep trying different things, custom count is at 3 maybe by the time i give up it might be in the 100's because i wont get a replacement till tuesday...
Click to expand...
Click to collapse
The no data tar will completely flash but won't boot on it but you can put it back to stock like that with sfhub el29 no data
Some one in the data thread I gave u did remap the data partition to his Sd card and rigged it .... That could work until you get replaced
Sent from my SPH-D710 using Tapatalk 2
Just odin the el26+cwm kernel and reboot into recovery and wipe and flash like normal. I had the bootloop before snd this worked for me.
EL26+CWM Kernel link: http://db.tt/0QJkleJR
Edit: just read your whole post and it does sound like your bricked. You can try what I stated above, but I don't think it will work.
Sent from my SPH-D710 using Tapatalk 2 Beta-5
mrperez816 said:
i had CWM, i was running ics 4.0.4 fine build 30 since it came out. It just started the stupid animation loop and thats when i decided to do a data wipe in CWM
Click to expand...
Click to collapse
This is where your /data partition got corrupted. The data wipe in ICS-based CWM.
mrperez816 said:
but then i did the ODIN One Click and it gets stuck on data.bin.
Click to expand...
Click to collapse
ODIN OneClick is just serving as the messenger to tell you your /data partition is corrupted. You could have used CWM, ODIN, ODIN OneClick, etc. They would all tell you the same thing. The EMMC memory is actually damaged, it isn't just a partition data problem.
It is unfortunate to have the issue with ICS-based kernels and custom recovery, but that is why all the threads stress using GB-based kernels with custom recovery to do your flashing.
Lesson learned. At least you work for Sprint and can probably get things resolved with less hassle.
Yeah lesson learned. I just did the repair ticket on it and will have one on tuesday.
When the new one comes i will go straight to ICS build 31, and not even mess with anything else.
Its just amazing how we cant figure out a way to format/partition the currupted /data.
mrperez816 said:
Its just amazing how we cant figure out a way to format/partition the currupted /data.
Click to expand...
Click to collapse
It isn't a format issue.
The hardware emmc memory is damaged.
JTAG bitblasting would have overwrote everything if it was fixable. That is failing in this case.
So basically you are asking why we can't reformat a hard drive that crashed and make it work.
You are doing what's right. I had to flash the one click Odin 3 times to get out of a boot loop after trying to restore a GB ROM MD5 from a ICS kernel. Learned the hard way. But if you can get to DL mode, you can usually fix it. After the third time i was able to get into standard Android recovery and do a factory data reset. Then flashed the rom again and it booted right up. I was lucky though. Hope it works out.
PHONE WONT BOOT AFTER USING ALPHA 6 ICS(darchstar)
I was using this rom since it came out and haven't had 1 problem. after just using it normally it froze. did a battery pull and tried to reboot but was stuck on logo with the cm9 animation. so i went to recovery mode i had an error. i tried doing a format and froze. so i did another battery pull and now my phone wont boot into recovery or download mode. all i get is a blue led light. any ideas?
I'd like to think that putting BIGGER red text in the OP's might help but apparently not...
Sent from my SPH-D710 using xda premium
Oops, ignore me
Sent from my SPH-D710 using xda app-developers app
xDarkStarx27 said:
I was using this rom since it came out and haven't had 1 problem. after just using it normally it froze. did a battery pull and tried to reboot but was stuck on logo with the cm9 animation. so i went to recovery mode i had an error. i tried doing a format and froze. so i did another battery pull and now my phone wont boot into recovery or download mode. all i get is a blue led light. any ideas?
Click to expand...
Click to collapse
Your /data partition is dead. Formatting/ wiping from ICS recovery is VERY BAD, it makes bricks.... time to use insurance/TEP... sfhubs post on this page applies to you as well...
Sent from my SPH-D710 using xda app-developers app
Hey guys. So, I've been rooting for quite a while now. My most recent is the Epic 4g Touch. I've had it for the past 2 months and just recently managed to stump myself. There is a new kernel out there called fluxxi ics kernel. Well, I flashed it after I flashed my AOKP ICS rom, and now my phone won't boot. Normally, I would just reflash the stock el26.tar file with odin. However, all of a sudden my computer won't recognize my phone. So I'm at a loss. I did some research on the usb jig, and I'm curious as to whether or not I should get it. Would it help in my computer finding my phone due to the reset, or do I needa JTAG? Thanks in advance guys. Hope for some answers soon.
You flashed a kernel that is for I-9100 it's Galaxy S2 yes but totally different phone. So it seem's like you are still able to get into download mode am I correct, but the computer no longer recognizes your phone? I don't think a jig will help if this is the case your best bet is sending out for JTAG repair. Hopefully you will get this straightened out and this will be a lesson learned not to flash any random kernel.
Did you not read that you were in the wrong section and about to flash an international kernel for a different phone?
Install/reinstall the usb drivers needed, including the international drivers if that helps, than just Odin one of sfhubs Odin one clicks.
Sent from my SPH-D710 using Tapatalk
Thanks for the quick replies guys. The kernel isn't an international one. The forum said it was designed for all Galaxy S2's, including the Epic Touch 4G. And it does work, as long as you flash it before the ROM and not after. When I enter download mode, it still says I'm running the D710 with a custom binary and yada yada yada. The international drivers won't help me in this situation it seems.
Just to give yall some more info, I'm running AOKP Build 37. Everything I have found online so far has said they work well together. If there were a way I could either mount the external sd card to the phone (which when I try to do in recovery, it says it can't be found) or if I could mount the phone to my pc, I'd be set.
Do you have mobile Odin?
Sent from my SPH-D710 using Tapatalk
I do, but the phone will not boot past the Galaxy logo.
griffthegreat said:
Thanks for the quick replies guys. The kernel isn't an international one. The forum said it was designed for all Galaxy S2's, including the Epic Touch 4G. And it does work, as long as you flash it before the ROM and not after. When I enter download mode, it still says I'm running the D710 with a custom binary and yada yada yada. The international drivers won't help me in this situation it seems.
Click to expand...
Click to collapse
Could you please direct me to to this forum and to where it says that this was designed for all Galaxy S2, including the Epic Touch 4G only reference I seen on this kernel is that it is an I-9100. Might give us more reference and info also.
griffthegreat said:
Thanks for the quick replies guys. The kernel isn't an international one. The forum said it was designed for all Galaxy S2's, including the Epic Touch 4G. And it does work, as long as you flash it before the ROM and not after. When I enter download mode, it still says I'm running the D710 with a custom binary and yada yada yada. The international drivers won't help me in this situation it seems.
Click to expand...
Click to collapse
Wouldn't the ROM overwrite the kernel anyways. Every ROM has a kernel baked into it unless you removed it first then flash. I'm never heard of a kernel that needs to be flashed before the ROM unless you need to use it's recovery like el26.
Sent from my SPH-D710 using Tapatalk 2
sol_671 said:
Wouldn't the ROM overwrite the kernel anyways. Every ROM has a kernel baked into it unless you removed it first then flash. I'm never heard of a kernel that needs to be flashed before the ROM unless you need to use it's recovery like el26.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Yes, ROM would overwrite.
Sent from my SPH-D710 using Tapatalk
I think you may of missed read something my friend. Also for future reference I would only flash things from my section of whatever forum you are in. Something as critical to the survival of your phone as a kernel or a modem I would not flash on a whim from anywhere else outside of xda.... I hope you get your phone back up and running and hopefully this will make you and others more cautious in the future.
Question - did you post a thread in the area that you got the kernel?
just use odin one lick
I'm someone, like others I've saw, that are coming over here from the EVO 3d after having to go through asurion.
As a good XDA member, I read through the stickies.
I wanted to confirm what I've learned.
ICS for you guys is rather different. I'm seeing many versions of ICS, I'm guessing leaks at different stages (haven't seen many leaks on phones in a while).
I also saw that wipe in custom recoveries is a REALLY bad idea.
In fact it said not to use custom recoveries with ICS stuff.
So why does Calkulin's E4GT rom say you MUST use a custom recovery?
I thought I saw something crazy that said it depends what version you are on for the method you root. But I can't find that again. It seems weird, but please tell me that's wrong and there's only one way to really root.
karate134 said:
I'm someone, like others I've saw, that are coming over here from the EVO 3d after having to go through asurion.
As a good XDA member, I read through the stickies.
I wanted to confirm what I've learned.
ICS for you guys is rather different. I'm seeing many versions of ICS, I'm guessing leaks at different stages (haven't seen many leaks on phones in a while).
I also saw that wipe in custom recoveries is a REALLY bad idea.
In fact it said not to use custom recoveries with ICS stuff.
So why does Calkulin's E4GT rom say you MUST use a custom recovery?
I thought I saw something crazy that said it depends what version you are on for the method you root. But I can't find that again. It seems weird, but please tell me that's wrong and there's only one way to really root.
Click to expand...
Click to collapse
You have to use a specific recovery to flash stuff, called the EL26/29 recovery. It's based on 5.0.2.7 (?) of ClockWorkMod recovery. This is generally accepted as the safest way to flash. Flashing from an ICS based recovery has been known to brick devices.
Samsung devices have Odin, much like HTC devices have Fastboot. We're able to put the device in Odin (download) mode and flash just about anything. There's even an app version called Mobile Odin that allows you to Odin flash directly from the phone without having to plug in.
Correct me if wrong but i think there is only an issue with ics recovery when wiping due to the emmc bug (partition corruption). Thats whats causing the bricks. There are plenty workarounds though. I use ics recovery to flash things, i just make sure to never wipe anything using the recovery. I use calk's format all zip and modified format zip whenever i need to wipe.
puff601 said:
Correct me if wrong but i think there is only an issue with ics recovery when wiping due to the emmc bug (partition corruption). Thats whats causing the bricks. There are plenty workarounds though. I use ics recovery to flash things, i just make sure to never wipe anything using the recovery. I use calk's format all zip and modified format zip whenever i need to wipe.
Click to expand...
Click to collapse
Correct they have come up with ways to use ICS recovery to update and flash certain things. Honestly since the OP is new to Epic Touch I would stick with the very simply odin of el26 recovery and flashing anything you need while in ICS.
agat's threads have great info if you are a stock software guy with ways to flash and upgrade while on ICS. Honestly GB is pretty damn polished and there are some awfully nice roms for it as well and you have no worries at all with how you flash. sfhub has quite a few threads with his odin one click methods which have been a god sent for a lot of us here.
First decide what you want to do then any one of the OP's will direct you in the right direction. Also if you can read up on the How not to brick your phone threads/stickies in general I believe
Would be a better idea to use the cm9 direct boot Odin file. Much easier than pulling the battery 10 times. Read all the release notes on the cm9 wiki and you'll have safe flashing.
Sent from my awesomely EPIC Phone
Rooster-just curious, why would you need to pull the battery? I've flashed plenty of roms and haven't had to pull the battery once...
Karate-the easiest easy to just gain root access is to use sfhub's one click rooted el29-just boot into download mode (vol up + power), plug into the computer and click start...easy peasy
And as playya said, the OP's of any of the rom threads all have great info and directions to keep you flashing safely. Good luck and happy flashing!
Sent from my wickedly sensational e4gt
Sunsparc said:
You have to use a specific recovery to flash stuff, called the EL26/29 recovery. It's based on 5.0.2.7 (?) of ClockWorkMod recovery. This is generally accepted as the safest way to flash. Flashing from an ICS based recovery has been known to brick devices.
Samsung devices have Odin, much like HTC devices have Fastboot. We're able to put the device in Odin (download) mode and flash just about anything. There's even an app version called Mobile Odin that allows you to Odin flash directly from the phone without having to plug in.
Click to expand...
Click to collapse
Can you a link to el2? Recovery
Sent from my SPH-D710 using xda premium
http://forum.xda-developers.com/showthread.php?t=1416477
Check this thread out, make sure to read all the directions and you should be able to find the auto root package where you can add cwm recovery to the kernel
Sent from my wickedly sensational e4gt
karate134 said:
I'm someone, like others I've saw, that are coming over here from the EVO 3d after having to go through asurion.
As a good XDA member, I read through the stickies.
I wanted to confirm what I've learned.
ICS for you guys is rather different. I'm seeing many versions of ICS, I'm guessing leaks at different stages (haven't seen many leaks on phones in a while).
I also saw that wipe in custom recoveries is a REALLY bad idea.
In fact it said not to use custom recoveries with ICS stuff.
So why does Calkulin's E4GT rom say you MUST use a custom recovery?
I thought I saw something crazy that said it depends what version you are on for the method you root. But I can't find that again. It seems weird, but please tell me that's wrong and there's only one way to really root.
Click to expand...
Click to collapse
Im one of those that went through insurance too and ended up with this today and i gotta say I love it!
Sent from my SPH-D710 using XDA
im also coming over from the evo4g and evo3d not because of insurance wanted something different and im loving the phone so far..i will say i was lost at first with odin and el29 its a different way of doin stuff but not hard at all
Welcome, I recently made the switch as well. The screen is incredible after looking at the E3D for so long. Seriously, I stop to look at how pretty it is at least once every day.
SkuzFoz said:
Welcome, I recently made the switch as well. The screen is incredible after looking at the E3D for so long. Seriously, I stop to look at how pretty it is at least once every day.
Click to expand...
Click to collapse
Yup! It truly is amazing!
Sent from my SPH-D710 using XDA
With all of the forums merged it was so hard to get a read on the real amount of IMEI Problems by AT&T Users.
So a quick poll / count. Who has lost their IMEI on AT&T.
crawlgsx said:
With all of the forums merged it was so hard to get a read on the real amount of IMEI Problems by AT&T Users.
So a quick poll / count. Who has lost their IMEI on AT&T.
Click to expand...
Click to collapse
I lost my IMEI on my first Sgs3, went flash happy (only AT&T ROMs) but still had data and cell. Not sure where I lost it, but I noticed when I was flashing back to rooted stock from early CM10 preview (official) is when I noticed.
So far with my new phone, I've done the same and still have it. I'm now running Aokp jellybean.
I've had no problems as of today but the fear of losing my imei has definitely caused me to not experiment as much as I would like to! I've rooted, installed CWM-Touch, flashed Ktoonsez Kernel, and flashed back to the AT&T Kernel. I'm honestly afraid to try CM as it seems that ALOT of the people who have lost their IMEI had flashed CM10 or CM9. I bought a Galaxy Tab 2 7" a few months back and it's become my tinker toy to flash ROM's and mess with. I don't want to screw up my $500 Galaxy S3, I like it too much!
I voted as flashed a few, but really it is probably closer to many. Only AOSP based ROMs though. CM9, CM10, and AOKP plus updates for each. Also both Faux and Ktoonsez kernels at various times. IMEI still present.
I do make sure that I flash the EXACT same way every time though since it has worked so far. Only thing I have changed now is moving from latest non-touch CWM (installed through ROM Manager) to latest TWRP (through Goo Manager).
If I end up losing my IMEI without adding variables to my flash process, I will start to believe it is a random occurrence. Until then I have to think partial user error coupled with a bad update script or recovery.
I ALWAYS download the file straight to my phone via WiFi.
Reboot into recovery. Wipe>Factory reset.
Flash ROM.
The last couple days since moving to TWRP I have felt more ballsy and did things a bit differently.
For the first time, I also wiped cache and Dalvik before flashing JB AOKP last night
Still no issues.
Today I decided to flash the ktoonsez JB kernel. I usually only download via WiFi at home (just to keep minimal variables in flashes) but today I did it at work via WiFi. Still have IMEI.
I have NEVER done a Format System so not sure if that might break something.
My process has been if it isn't breaking, try to keep the process as consistent as possible. If something does go wrong, I can say what I did differently. I also haven't had any trouble with the ROMs I flashed despite only doing factory reset then flash.
How do I know if I have any issues with this. What do I look for. I found out and mines good.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
spacecasespiff said:
How do I know if I have any issues with this. What do I look for. I found out and mines good.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I know you found out, but when it happens you will know.
In some cases it seems as though you only get Edge at your maximum speed, in others your mobile data completely died. Generally speaking, there was a lot of confusion and some issues with clarity regarding the issue.
It's possible that there are several different (but vaguely related) issues going around, now that we have our own carrier based forums that should actually help clear it up in my opinion.
Hopefully we will all reach a general consensus on the acceptable recovery (my vote is TWRP!) and method of flashing. The only thing I've personally considered is that it might be an issue with the files transferring via MTP (only because I've never used a phone with MTP instead of mass storage).
I don't think people should be THAT afraid to flash though. If your flash counter is at 0, Samsung should do a warranty swap for you. In addition, it seems like 2 in 25 people (read: NOT FLASHES, but people.) seem to get the issue based only off of the very small number of people in this poll so far.
The reason the issue is so feared is because those that do get it will inevitably be far more vocal than those that don't as they try to find a solution and vent their frustration. Most of the people in the major thread about it didn't have the issue, but were afraid they might lose their IMEI.
I flashed the stock rooted tar that doesn't trip your counter, then injected CWM with dd. I've flashed everything with CWM since then, CM10 included (once) and I still have my IMEI. I'm running AOKP JB now.
I'm about to root and cwm what's your guys input on the best ways
Sent from my SAMSUNG-SGH-I747 using xda premium
yokken said:
I flashed the stock rooted tar that doesn't trip your counter, then injected CWM with dd. I've flashed everything with CWM since then, CM10 included (once) and I still have my IMEI. I'm running AOKP JB now.
Click to expand...
Click to collapse
What's this dd you speak of sir
Sent from my SAMSUNG-SGH-I747 using xda premium
As always, check your apn before freaking out! It may have gotten deleted while flashing a rom. It happened to me
Yes, I freaked out.
Sent from my SGH-I747M using xda premium
tyshemi said:
What's this dd you speak of sir
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
If you read the thread I mentioned (How to root without tripping flash counter) it mentions "injecting" CWM using a tool called dd.
yokken said:
If you read the thread I mentioned (How to root without tripping flash counter) it mentions "injecting" CWM using a tool called dd.
Click to expand...
Click to collapse
Yea I have read that many times there guy thanks for input just solidifying it all
Sent from my SAMSUNG-SGH-I747 using xda premium
ppl who scared to flash
Go for nontrip flash root + CWM topic - worked for so many people without issues.
The only way to screw up IMEI with these ROMs is via Odin, I think. Odin is a scary tool without much documentation, and in past used to be buggy.
Once you get CWM - do not use Odin.
bravomail said:
Go for nontrip flash root + CWM topic - worked for so many people without issues.
The only way to screw up IMEI with these ROMs is via Odin, I think. Odin is a scary tool without much documentation, and in past used to be buggy.
Once you get CWM - do not use Odin.
Click to expand...
Click to collapse
I have to use Odin for root initially don't I ? Then use it for cwm or u recommend Rom manager ? Im just wanting stock Rom like yours for now
Sent from my SAMSUNG-SGH-I747 using xda premium
bravomail said:
Go for nontrip flash root + CWM topic - worked for so many people without issues.
The only way to screw up IMEI with these ROMs is via Odin, I think. Odin is a scary tool without much documentation, and in past used to be buggy.
Once you get CWM - do not use Odin.
Click to expand...
Click to collapse
Odin is a scary tool indeed. Someone in the IMEI thread said if I was feeling feisty to flash stock nonrooted OTA ROM via Odin straight from JB AOKP. IMEI is still intact after all that I have done. :laugh:
EDIT: Also, anyone who reads this. Try out TWRP. We need more people flashing with TWRP, if an IMEI goes missing while using it we can rule out CWM being the problem as some have suggested.
codycorexxx said:
Odin is a scary tool indeed. Someone in the IMEI thread said if I was feeling feisty to flash stock nonrooted OTA ROM via Odin straight from JB AOKP. IMEI is still intact after all that I have done. :laugh:
EDIT: Also, anyone who reads this. Try out TWRP. We need more people flashing with TWRP, if an IMEI goes missing while using it we can rule out CWM being the problem as some have suggested.
Click to expand...
Click to collapse
Ive done this, not once but twice. Once coming from Aokp and once from cm10. Imei still intact :good:
Lmao, funny thing is i was deathly scared of the imei issue and very well versed on it, and i never knew it was "dangerous" till i read your post just now.
Hey Guys,
I know it is probably not possible, but in case it is, I wanted to post the question.
I have been working with MotoDefier for a few days now learning about the new model S3 (SGH-T999L). Because there is no firmware available for download yet, we are trying to find a way to either pull the stock recovery before rooting, or figure a way to root without flashing CWM or TWRP first.
The ultimate goal here is to pull all of the parts that are included in firmware updates, and create the firmware from there. This way, if anyone runs into problems, they will be able to Odin back to stock.
Moto has already tried several different rooting methods, including CF-AutoRoot, and has had no luck so far. So if anyone has any ideas on how we can get this done, please do share!
Thanks!
Doc
This may be out of place but perhaps the 999l is closer recovery to the s4? I don't know. But have you tried to pull it with the paid version of the s3 toolkit?
I wish I could help. Sorry Doc
Sent while sleeping in chair.
Doesnt the toolkit flash recovery though? Ive never actually used it. Ill look into it though, thanks.
As far as it being closer to the S4, im just not sure. I do know you can root by flashing the T999 CWM or TWRP, then superuser. Plus.from what I see the overall layout is the same as the original T999.
Thanks for the reply!
Sent from my SGH-T999 using xda premium
I don't have an answer for your question, but wouldn't the only way be through flashing an insecure kernel (exploit)? Then you could push SU and you would have your recovery. But then you lose the kernel.
Can't you download the firmware through Kies? I know it's not on sammobile, but I would think that Kies would be able to restore the factory image. The prospect of Kies not being able to do this is ridiculous. If that's the case, it's even more useless than I previously thought.
Aerowinder said:
I don't have an answer for your question, but wouldn't the only way be through flashing an insecure kernel (exploit)? Then you could push SU and you would have your recovery. But then you lose the kernel.
Can't you download the firmware through Kies? I know it's not on sammobile, but I would think that Kies would be able to restore the factory image. The prospect of Kies not being able to do this is ridiculous. If that's the case, it's even more useless than I previously thought.
Click to expand...
Click to collapse
I was actualy thinking the same thing about the kernel. Just sent a PM to one of the guys who already rooted to see if they would pull the boot.img for me. Im not worried about losing the kernel, as I will still have the original copy after setting it to insecure.
Moto already tried getting the firmware through kies, but it didnt work. We figure that its because there is no publicly released firmware to begin with. As to the uselessness of Kies......completely!
.......I was just thinking, when you flash CM, it flashes its own kernel with it, right? (Its been a long time since Ive messed with CM, sorry). If thats the case, i wont be getting the kernel from the guy I PM'd.
Does anyone else have the new model T999L? If so have you rooted yet, or do you plan to? If so, please PM me if you are willing to help us out with this.
And by all means, hit me with any other ideas you guys may have!
Yes, it flashes it's own battery hog kernel.
Well, I hope I dont jinx anything by announcing too early, but I think we got it!
It appears that using the motochopper exploit did the job. It was originally created for a Motorola device, but as it turns out it will work on a number of Qualcomm based devices.
I got the info from the S4 forums.
It appears the main thread is in the ATT forum here:
http://forum.xda-developers.com/showthread.php?t=2252248
Here it is reposted in the Tmobile S4 forum:
http://forum.xda-developers.com/showthread.php?t=2258633
Just wanted to share in case anyone's interested in taking a look.
Note: it looks like the latest updates may have been patched against this exploit. Just fyi.
Sent from my SGH-T999 using xda premium
I love you Doc. (Hetero)
Sent while sleeping in chair.
Lol!
Be sure to hit thanks when you see MotoDefier. He took all the risk and did all the hard work! I mostly just helped with ideas and such. (Most of which didnt work!)
Ill be working tonight and tomorrow on getting some sort of flashable firmware put together so you guys have a way back to stock if need be.
Also I have a deodexed rom based on the T999L almost ready in case anyone wants to mess with it. Just got to double/triple check my work and test first. There are a few differences from the original T999 so im curious to see if any of it is noticeable while its running.
Let the fun begin!
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Doesnt the toolkit flash recovery though? Ive never actually used it. Ill look into it though, thanks.
As far as it being closer to the S4, im just not sure. I do know you can root by flashing the T999 CWM or TWRP, then superuser. Plus.from what I see the overall layout is the same as the original T999.
Thanks for the reply!
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
What I meant was pulling files from device without pushing anything to it. I believe this is an option within the toolkit, not sure if paid version required. Hmmm.
Sent from my Transformer Prime TF201 using xda premium
What I was getting at, was that we didnt want to use the toolkit because it flashes recovery. And I could be mistaken, but Im pretty sure the toolkit requires you to root first, then it can pull system firmware for you. Either way though, we got what we needed. I am uploading files now and will post shortly.
Note that most of what I am doing is currently untested. I do not have a T999L, and I dont want to take the chance of flashing certain parts of the T999L to it. I am confident that it will work, or i wouldnt release any of it, but just for full disclosure.....!
I dont believe it needs root and it wont do anything you dont want it to do unless you tell it to do it. All of that aside, I wasnt trying to pimp the toolkit, I just thought it might work, but as I have little knowledge about that which I am talking, I'll just defer to you fellows as you seem to know a thing or two about a thing or two.
:screwy:
Sent while sleeping in chair.
I have the T999L, I used the Toolkit to flash TWRP and then updated it to 2.5.0.0 from Doc's page, I then flashed SuperSU 1.30, wiped Cache and Dalvik, then rebooted. Bam, Rooted. But it not 100%, ROM Manager doesn't seem to have root, but Adfree Android, TiBackup and ES File Explorer. I'm going to uninstall ROM Manager and then reinstall to see if that helps.
Thanks again to DocHoliday77 for his help.
EDIT: I found out why ROM Manager was failing, BusyBox was not installed. I installed it and everything works.