I first posted this in MrRobinson's excellent thread at http://forum.xda-developers.com/showpost.php?p=35165945&postcount=1610, but decided others might benefit from it that may not be following his instructions because they're already rooted...
For now, just see my instructions in the post mentioned above. Once I get off work this evening I will be updating this post with more detailed information. At least one other user has followed these instructions and reported that his flash counter remains at 0, even after multiple reboots and custom recovery actions.
The usual disclaimers about bricking your phone, blowing up your grandmother's house, drowning your dog, etc. apply. I'M NOT RESPONSIBLE!!!
Reserved - just in case...
I can confirm this method works as described. I also added instructions in the same thread on how you can still use this method if you happen to have already upgraded to JB via the traditional method (ie via ODIN or Kies) and have a count or custom status. It requires reverting to stock ICS and recovery and then moving forward with the above process, and the end result is Rooted JB with Custom Recovery and retaining official rom status with no counter increments.
whats the point.. if you put a custom recovery on it updates the counter anyway.. on every boot. unless you root and remove certain files.. and if you are rooted and remove those. you can use triangle away anway.
If you revert to ics, then flash jb without the accompanying bootloaders you don't have to worry the flash counter. Why is that important? In case you need to warranty it and can't get to triangle away to reset it. And some of us like to say its never been tripped
Btw, I'm running rooted stock with twrp and my counter is still 0. And i installed twrp after flashing jb.
lgkahn said:
whats the point.. if you put a custom recovery on it updates the counter anyway.. on every boot. unless you root and remove certain files.. and if you are rooted and remove those. you can use triangle away anway.
Click to expand...
Click to collapse
That's the point. I flashed and KEPT my custom recovery, and it does not increase the counter no matter how often I use it. I haven't tried loading a different custom recovery now that I'm on JB, but so far all is well.
By the way, sorry I haven't followed up on the OP. Been very busy.
78Staff said:
I can confirm this method works as described. I also added instructions in the same thread on how you can still use this method if you happen to have already upgraded to JB via the traditional method (ie via ODIN or Kies) and have a count or custom status. It requires reverting to stock ICS and recovery and then moving forward with the above process, and the end result is Rooted JB with Custom Recovery and retaining official rom status with no counter increments.
Click to expand...
Click to collapse
Thanks for the other post. I was beginning to think no one even cared. I'll see if I can incorporate your info into the OP when I finally get around to it...
lgkahn said:
whats the point.. if you put a custom recovery on it updates the counter anyway.. on every boot. unless you root and remove certain files.. and if you are rooted and remove those. you can use triangle away anway.
Click to expand...
Click to collapse
You're doing it wrong. Mine still displays 0 and official after installing multiple recoveries, countless zip flashes to include AOKP and TW ROMs and approx 4-5 Odin flashes. My wife's recently rooted and jb'd S3 also says the same thing.
Sent from my SAMSUNG-SGH-I747 using xda premium
Are any of you having SD card issues with the stock version of JB?
LAKsupply said:
Are any of you having SD card issues with the stock version of JB?
Click to expand...
Click to collapse
Nope. Have you tried reverting to ICS to see if the problem persists?
Sent from my SAMSUNG-SGH-I747 using xda premium
d3athsd00r said:
You're doing it wrong. Mine still displays 0 and official after installing multiple recoveries, countless zip flashes to include AOKP and TW ROMs and approx 4-5 Odin flashes. My wife's recently rooted and jb'd S3 also says the same thing.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
no that is becuase one of the flashes you did removed those recovery files that comes with stock jb.. or replaced the kernel that reflashes them..
normal upgrade from ics to stock jb.. will reset counter on every boot unless you change the kernel or remove the recovery image.
d3athsd00r said:
Nope. Have you tried reverting to ICS to see if the problem persists?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
It's fine on ICS... this is Jedi Invasion JB and the KT747 kernel. I wasn't sure if it was just the ROM and then noticed that others with different roms and stock roms had the same issues. I'm wondering if it wasn't an issue in the initial JB release (this is a ported T Mobile rom) that the dev built this rom off of. I'll flash another JB version and see if the problem persists.
lgkahn said:
no that is becuase one of the flashes you did removed those recovery files that comes with stock jb.. or replaced the kernel that reflashes them..
normal upgrade from ics to stock jb.. will reset counter on every boot unless you change the kernel or remove the recovery image.
Click to expand...
Click to collapse
I.E. I did it right. Doing it right the first time keeps you from having to fix it later.
Sent from my SAMSUNG-SGH-I747 using xda premium
So... it appears my previous issue was a bad sd card. It's kind of a big coincidence that the old card didn't work with the Jedi rom, and now the new card doesn't work with any rom. I just flashed AOKP and the correct KT747 kernel, and no love. I pulled the 32g sd card and fed it my wife's old 8g card, and it works perfectly. Is there a such thing as a rom cooking an sd card?
great find! followed the instructions with mobile odin and worked like a charm, I came from a jb aosp rom, but first I nandroid back to an ics-lg1 backup I did a few months back, no counter tripping after a few reboots into recovery
one question, is there any thread where I can find mods for this 4.1 TW stock jelly bean, like power menu, toogles, kill back button,tether etc if anyone has a link please share
many thanks!
When your sdcard went did it say damaged? That happened to me going from ics to jb mr robinsons official stock. So i put in a brand new card, then it tells me under about status is modified which it wasnt when the first sd card worked. Even odder my pc couldnt see the card, so i thought it truly was damaged. I put it back in just to try a day later and all of a sudden i can format it within the phone, which, I due and then it works again and the modified under status is back to normal. Im gonna go through the source of that package this week and see if I can find whats up and what could of tripped and then reverted that counter.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Right on this worked great! And now don't have to worry about the stupid flash counter
sent from the dark side of the universe....
I followed the method in this thread (using mobile odin to go from rooted ICS to rooted JB). It was pretty easy and it worked great. However, after the first restart, I started having a strange problem. Every 5 minutes, the phone will lose its network connection for approximately 30 seconds. This appears as red on the "Mobile network signal" under battery usage details, and I'm unable to make any calls. This drop happens like clockwork. You could set your watch by it.
I've tried everything (uninstalling certain programs, flashed different modems, factory reset, etc) and nothing worked. I reverted back to ICS and then redid the method from this thread, and the same thing happened (JB worked great until I restarted for the first time, etc..
Any ideas? For a while I thought it was some weird issue with the analog clock widget.... But getting rid of that didn't help. And I've tried every possible google search on this issue but I can't find anything. For now I'm back to ICS.
Yea that is weird maybe just try it over again fresh odin ics and go from there. Almost seems like something didn't take going thru the flash process
sent from the dark side of the universe....
did you check the apns? right after I did the flash, it didnt have the "ATT PTA" apn so I had to manually add it
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Related
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.
Trying to install a leak thru stock recovery. Does anyone Known how to get past that issue? Thanks
Jake
themadzionist said:
Trying to install a leak thru stock recovery. Does anyone Known how to get past that issue? Thanks
Jake
Click to expand...
Click to collapse
As far as I can tell, I believe it means you're rooted still. I had the same problem so I Odin'd stock UVALH2 and then installed the leak without issue.
Not trying to hijack this thread but have been wondering why do you guys try to install leaks throw stock recovery. It is super easy to root this phone. Why not root install custom recovery then jush flash leaks?
Sent from my SGH-T999
Because you have to be 100% stock to install the leaks. This is the source of the error btw op. Prob not root but a custom recovery. Must be stock everything, modem and kernel must match too.
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Because you have to be 100% stock to install the leaks. This is the source of the error btw op. Prob not root but a custom recovery. Must be stock everything, modem and kernel must match too.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
This is just not true. I install those OTA leaks every time they are released. Never once used stock recovery to do it.
Aerowinder said:
This is just not true. I install those OTA leaks every time they are released. Never once used stock recovery to do it.
Click to expand...
Click to collapse
Same here, I didn't come from a stock rom. Oh well.
So are you flashing the deodexed roms then?
Im talking about the actual ota you download from somewhere like sammobile.
It patches the existing system (UVDLI8 patches UVALI5) if anything is modded in UVALI5 the patch wont work, or if it does it can cause problems.
If you're flashing roms from development section then yes you can flash normally with custom recovery. But those roms are based on the otas, they're not the actual otas themselves.
Sent from my SGH-T999 using xda app-developers app
I don't bother with TW custom roms. Not really my thing, but I understand why people might want them.
I flash the OTA updates from the link in my signature (sammobile) in order to pull modems. Although there hasn't been a point lately, because you are working at the speed of light. But I flashed UVALEM, UVALH2, I1, 2, 3, 4, 5, 6, you get the idea.
Are you using TWRP? That recovery might not work with the OTA updates, but I've proven myself, and through many other people, that you can indeed flash OTA leaks from sammobile with CWM Touch 6.0.1.2. I'm unsure about the workings of TWRP because I don't use it. I don't use it because I don't like the buggy keyboard.
Yeah i tried everyway possible. The only way that worked was going uvahl2 thru odin, and then thru stock recovery i applied the ota jb uvdli7 from external sd. It was the only way to get it to work. I think the reason why the error message was coming up was because even though i unrooted my phone, the phone status still said "modified". Once i reflashed hl2 and it didn't say modified it updated the leak.
I think its going to take a video to prove you don't need stock recovery for this operation.
Aerowinder said:
I don't bother with TW custom roms. Not really my thing, but I understand why people might want them.
I flash the OTA updates from the link in my signature (sammobile) in order to pull modems. Although there hasn't been a point lately, because you are working at the speed of light. But I flashed UVALEM, UVALH2, I1, 2, 3, 4, 5, 6, you get the idea.
Are you using TWRP? That recovery might not work with the OTA updates, but I've proven myself, and through many other people, that you can indeed flash OTA leaks from sammobile with CWM Touch 6.0.1.2. I'm unsure about the workings of TWRP because I don't use it. I don't use it because I don't like the buggy keyboard.
Click to expand...
Click to collapse
Lol! Im just usually online when they drop! Theres only been a couple where I wasn't.
If cwm touch recovery does flash these otas as is then it just means they've disabled the check the ota does to verify the system meets the requirements. Or they just disable the recovery check/patch to protect their own recovery. I hope its the latter.
Not saying it cant be done but till now I hadn't heard of it. I use TWRP (just personal preference) but actually never bothered to try with it becsuse too many people early on got errors like the OP when anything wasn't matching stock.
I use Mobile Odin for the otas since it not only allows me to meet the stock requirements but it also injects root so you never have to worry about rerooting or anything.
At this point I just want to know how CWM does the otas. Does it completely disable the system check, or just the recovery part of that check.
Sent from my SGH-T999 using xda app-developers app
The zip file still runs the verification process. I've always done it properly, so I don't know what a flashing failure looks like. I have a background in programming, and I'm an amateur for sure, but I suspect that when the update checks for stock recovery, it thinks CWM is the stock recovery. I'm not sure of the code behind this, but I equate it to user-agents in browsers. CWM is saying it is stock recovery, OTA update accepts that, or some such. Without seeing the code, I can't say for sure, but this is my guess.
You get the option to disable the recovery patch, and to keep root when you attempt to exit recovery after the OTA flash.
I never saw much use for Mobile Odin. I did buy it, because the dev is amazing, but I've never used it. It allows you to flash zip files? I've always just done it through CWM. I flash everything through CWM... even other recoveries.
However it does it, I guess it works. Only reason I wanted to know if it bypassed the entire check is because that could cause problems for the more inexperienced.
Yeah, I love Chainfires work. The ability to flash zips with Mobile Odin was just added a few weeks ago and has worked flawlessly for me.
Sent from my SGH-T999 using xda app-developers app
fix it
you need to flash your kernel to man. most stock kernel wouldnt work with cyanogenmod. Update your kernel with unofficial kernel that are compatible with your device
raaaaarrrr!!!
Has no one figured this out yet...i unrooted my phone using odin mobile ...then attempted to do the 4.3 manual update and im getting the same errors! this is bs...i even tried to use odin to flash mdl and it dint do anything to my phone. very unhappy.
atheistics1 said:
Has no one figured this out yet...i unrooted my phone using odin mobile ...then attempted to do the 4.3 manual update and im getting the same errors! this is bs...i even tried to use odin to flash mdl and it dint do anything to my phone. very unhappy.
Click to expand...
Click to collapse
Well, first, there is not an Odin flashable 4.3 file, but you said you tried to flash MDL? Not sure what this is exactly. The most likely issue is you are using an incompatible recovery. Probably one that is too old.
I think you are totally confused between odin flashable files and recovery flashable files....
Okay so maybe this will help...omni version is jfltecan...which is Canadian and my baseband is l720vpuemja ...that's sprint which my phone is...I'm getting no data...and I'm not able to revert back to 4.3 or 4.2.
Sent from my SGH-I337M using XDA Premium 4 mobile app
you should probably consider asking in your devices forum. if you use anything here youll likely brick.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
wolverine
themadzionist said:
Trying to install a leak thru stock recovery. Does anyone Known how to get past that issue? Thanks
Jake
Click to expand...
Click to collapse
Just downgrade to 4.0.4 and install cwm then flash it through it. it works for me.
So I rooted my phone with cf-auto root on stock firmware and also installed CWM. What I do not know is does flashing it afterwards with stock firmware remove CWM? also does that flash remove all the "Pimp my Rom" tweaks? Because after I flashed my phone, i noticed that I still have all my data there, which is different for me since I had an iphone not too long before having the note 2, and when I reformat my iphone, everything gets erased. I faintly researched and looked up, found out that there are 2 stock firmwares, one that erases everything and one that doesn't. I am not sure if that is true. What difference would the two have if it is true?
When u go back to stock ..it will go back to the way you bought it.....it will not erace your data...will remove cwm
Sent from my SAMSUNG-SGH-I317 using xda premium
thanks for the reply! much appreciated. I am now looking into deodexing my stock rom. however, it seems quite difficult :/
I bought a T-Mobile Galaxy S 3 LTE with model number SGH-T999L. I used Odin V3 1.85 to flash TWRP recovery and CyanogenMod 10.0.0.
Everything went well but my camera doesn't work. On launching the camera, I get a "Can't connect to camera" error and it quits. The same behavior is observed when using other camera apps. I tried the instructions in this thread(http://forum.xda-developers.com/showthread.php?t=2239414) but it did not fix my problem. I now want to go back to my stock ROM. I successfully downloaded and flashed stock recovery using Odin. However, Odin fails when I try to flash the stock ROM obtained from the samsung website. It gives me a "write failed" error and stops. Any tips or suggestions to help me out would be appreciated. Thanks
Is it supposed to use T999 firmware?
Only odin flash T999L firmware. I dont see it released yet at samsing-updates.com though.
Maybe samfirmware.com? I can look later.
Sent from my SGH-T999 using xda premium
re: sure fix
newidforu said:
I bought a T-Mobile Galaxy S 3 LTE with model number SGH-T999L. I used Odin V3 1.85 to flash TWRP recovery and CyanogenMod 10.0.0.
Everything went well but my camera doesn't work. On launching the camera, I get a "Can't connect to camera" error and it quits. The same behavior is observed when using other camera apps. I tried the instructions in this thread(http://forum.xda-developers.com/showthread.php?t=2239414) but it did not fix my problem. I now want to go back to my stock ROM. I successfully downloaded and flashed stock recovery using Odin. However, Odin fails when I try to flash the stock ROM obtained from the samsung website. It gives me a "write failed" error and stops. Any tips or suggestions to help me out would be appreciated. Thanks
Click to expand...
Click to collapse
Why not reflash the stock ODIN flash rom and make sure it all works ok for you, that will tell you exactly what the problem is.
If the stock rom is working properly, then there is only one thing left which is the culprit and that is the CM10/AOKP/AOSP
or PORTED roms which many people seem to like flashing.
The CM10/AOKP/AOSP and ported roms are excellent if you are a developer or if you like to do a lot of experimentation with your phone.
So the thing to do now is reboot your phone to recovery mode, do a "Factory Reset", "Wipe Cache", "Wipe System" and "Wipe Dalvik".
When that's done Open Odin and put the stock rooted T999 Tmobile Jellybean 4.1.2 into Odin's PDA slot, go into download mode
and once you see Odin is connected to the phone start the flash. Have patience for the phone to boot after its done flashing.
Here is the stock rooted Odin flash T999 Tmobile Jellybean 4.1.2 rom that you can download if you like: T999_UVDMD5
Official JB Firmware - Latest JB 4.1.2 Firmware
My suggestion to you is to only flash Samsung T999 Tmobile stock based Jellybean 4.1.1 or 4.1.2 roms in the future.
But who am I to say whats best..... This is just my personal opinion...... Which usually is not worth a dime. LOL
Sorry, but untill we know more about it, I would not flash T999 firmware onto the T999L.
Its only been out a day and tgey are different model phones with different hardware.
If you decide to try anyway, please post your results
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Sorry, but untill we know more about it, I would not flash T999 firmware onto the T999L.
Its only been out a day and tgey are different model phones with different hardware.
If you decide to try anyway, please post your results
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I am a newbie. I thought the T999 was the same as the T999L. That would explain why Odin doesnt flash stock T999 onto my device. Can anyone here post a link to the stock SGH-T999L ROM?
Just did a quick check and I dont see that the firmware has been made available for download yet.
If you want stock I would flash one of the stock based custom roms via recovery for now.
Out of curiosity, what is your current baseband version?
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Just did a quick check and I dont see that the firmware has been made available for download yet.
If you want stock I would flash one of the stock based custom roms via recovery for now.
Out of curiosity, what is your current baseband version?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Baseband version is T999LUVAMB7. Still waiting for stock ROM to be released on samsung-updates or sammobile.
newidforu said:
Baseband version is T999LUVAMB7. Still waiting for stock ROM to be released on samsung-updates or sammobile.
Click to expand...
Click to collapse
I had the same issue with the same phone. Got it 2 weeks ago haha. Did you happen to make a backup first using CWM Recovery? If so, you can just restore that backup and you'll have your camera functionality back. It's pretty annoying switching back and forth from CM10.1 back to stock just to take pictures but Rom manager makes it pretty quick and effortless.
Actually now that I think of it, they prob wont release the original firmware. Seems like the first build is never available, only when an update is released do we get firmware we csn download.
I am working with another member on getting something going for the T999L, but right now we are stuck until a verified safe method of rooting is found. (Dont want to flash a recovery or cf autoroot w/o knowing it wont screw something up)
Itll happen, but we just gotta be patient.
Just reread the op and see that you say you flashed TWRP. So you were able to initially gain root without any problems?
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Actually now that I think of it, they prob wont release the original firmware. Seems like the first build is never available, only when an update is released do we get firmware we csn download.
I am working with another member on getting something going for the T999L, but right now we are stuck until a verified safe method of rooting is found. (Dont want to flash a recovery or cf autoroot w/o knowing it wont screw something up)
Itll happen, but we just gotta be patient.
Just reread the op and see that you say you flashed TWRP. So you were able to initially gain root without any problems?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I used Odin to flash Clockwork Mod recovery first. I did not like Clockwork Mod's interface and reflashed with TWRP. I had no problems to gain root with either of these methods. I also tried Cyanogenmod stable 10.0.0 and then 10.1 RC2 without any problems. As far as I can tell, all apps work except for the camera. One word of caution though. As you can see from my posts, I am new and dont know what I am doing. I might have just gotten lucky since my device is still unbricked. I had only one "scary" moment during the entire process. I used TWRP to wipe my phone clean and was stuck with no OS install file. ADB sideload did not work since it could not recognize the device at that point. Luckily, I had a micro SD card lying around and was able to put in a new OS install file using my laptop and then TWRP was able to handle it.
tsticge aye
faytx1 said:
I had the same issue with the same phone. Got it 2 weeks ago haha. Did you happen to make a backup first using CWM Recovery? If so, you can just restore that backup and you'll have your camera functionality back. It's pretty annoying switching back and forth from CM10.1 back to stock just to take pictures but Rom manager makes it pretty quick and effortless.
Click to expand...
Click to collapse
Wish I had made a backup! Could you zip up the files contained inside "/system/cameradata/" folder and post a link here? It would help me and anyone else with the same problem restore the camera's functionality. In case you want to try it out, follow the instructions in this link but using the files from your stock backup
http://forum.xda-developers.com/showthread.php?t=2239414
newidforu said:
Wish I had made a backup! Could you zip up the files contained inside "/system/cameradata/" folder and post a link here? It would help me and anyone else with the same problem restore the camera's functionality. In case you want to try it out, follow the instructions in this link but using the files from your stock backup
http://forum.xda-developers.com/showthread.php?t=2239414
Click to expand...
Click to collapse
Here is the cameradata folder from the T999L.
http://d-h.st/Ciy
Good Luck!
How did you get Cyanogenmod installed on the t999l every time i try it aborts with status 7
Mine was failing with this same error. I reverted back to stock, re rooted, then downloaded the flash directly to the phones internal storage. Worked like a champ. I think in my case, there is an issue with the SD card, its kind of old.
Sent from my SGH-T999 using xda app-developers app
Beefstew said:
Mine was failing with this same error. I reverted back to stock, re rooted, then downloaded the flash directly to the phones internal storage. Worked like a champ. I think in my case, there is an issue with the SD card, its kind of old.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
You reverted to stock on the T999L? please exspain how that was done
Re flashed stock ROM using Odin. I believe I got the file from Samsung's website, but I'm not positive of that. I do know its huge, over 1 gig. If you need help with the re flash I know there are already how to's on here about that, so I won't go into it here.
Sent from my SGH-T999 using xda app-developers app
You must be using a T999 as your sig indicates, not a T999L. Am I correct?
Sent from my SGH-T999 using xda premium
Don't I feel like a tool now. Yes Doc, plain old t999 here. Now that I read back through the whole thread here I see that I was being a bit redundant. Now I will return to my closet under the stairs.
Sent from my SGH-T999 using xda app-developers app
No worries! We all do stuff like that from time to time!
Sent from my SGH-T999 using xda premium
So, today I flashed MIJJz Goodness Noteworthy 1.0.8. Everything went well. I also changed modems to JC1. Didn't like the rom (personal opinion) and tried to go back to stock. I went through Galaxy note2 toolkit initially and failed. Tried the old fashioned flash and failed. Tried the oneclick and failed. Every time the phone fails to go back to stock the only way I have been able to get it to work again is by using odin to flash boot-stock-alj1-SPHL900.tar from my galaxy note2 toolkit folder. the rom is still there.
So as the title states, lets assume I'm completely retarded.....can someone please hold my hand and walk me through returning my phone to stock?
Update: In addition i have flashed twrp, wiped everything, and attempted a stock flash zip from sd card.....failed. if i do the same for the goodness noteworthy rom.....success. i dont get it.
Update: I have attempted another rom (Illusion) and no dice. It seems I'm currently stuck with Goodness or nothing.
Update: I have made sure that no boxes were checked in TWRP settings. All attempts to flash fail except for the Goodness Noteworthy Rom.
[PROBLEM SOLVED] The issue was that my Odin version and drivers version was too old. I updated both and the flash worked as advertised.
Have you tried the return to stock zip that unroots resets flash counter and installs stock rom?
Sent from my SPH-L900 using Tapatalk
I am fairly certain that I have tried that, but for the sake of being thorough, let's assume that I have not. Could you please point me in the direction of this download? I'm going to take the "ultra dummy approach" because chances are this problem has more to do with the operator (me) than with the software.
Aviatortbyrd said:
I am fairly certain that I have tried that, but for the sake of being thorough, let's assume that I have not. Could you please point me in the direction of this download? I'm going to take the "ultra dummy approach" because chances are this problem has more to do with the operator (me) than with the software.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2086769
[ROM][RESTORE][5-12-13]Back to UNROOTED Stock with Auto Flash Count Reset
Just make sure you read
Sent from my SPH-L900 using xda app-developers app