just want to let you know that T-Mobile firmware is ready for download
http://samsung-updates.com/device/?id=SGH-T999
Is this for odin
Sent from my SGH-T999 using Tapatalk 2
Can this be used with the t mobile variant
Sent from my SGH-T999 using Tapatalk 2
If this is for sprint, why does the title say T-Mobile..
Sent from my HTC One X using xda premium
Edit: In that case, thanks PP
Sent from my SGH-T999 using xda premium
Its for T Mobile.. if you click on the link it says its for the T999
I was wondering the same thing, but if it matters I went to the link and it says it's for T-Mobile T999UVALEM like the title
Sent from my SGH-T999 using xda app-developers app
Tweezydak1d said:
Is this for odin
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
yes it is - same firmware as you would get updting with kies
anthonykash said:
Can this be used with the t mobile variant
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
ye, it is tmobile version i am tired and made a typo - corrected thnks and gnite
my phone came with this firmware. is this just posted to revert to stock if on a custom rom or is there other significance?
Has anyone tried flashing yet?
Sent from my SGH-T999 using xda app-developers app
So this must mean we can flash fash back to stock with odin if we have problems.
yup! this is our fall back ROM. now we need a triangle away to reset the counter!
It Works
I decided to be the test monkey on this one.
I had a nandroid backup of when I screwed my system so badly it just boot looped repeatedly. Restored that with cwm, verified it was still hosed, unpacked this zip, used odin to burn the .tar.md5 to the phone as PDA, rebooted.
It does some gear chunking while booting the first time then reboots - don't panic yet! On second boot it does some more rebuilding, then 'WELCOME!'
Bonus: CWM now sees the actual external sdcard as /sdcard and can find things like roms and backups on it. Edit: This CWM finds .zips on the sdcard, but doesn't seem to know how to backup/restore.
So is this for un rooting our phones?
Sent from my SGH-T999 using xda premium
sizer99 said:
I decided to be the test monkey on this one.
I had a nandroid backup of when I screwed my system so badly it just boot looped repeatedly. Restored that with cwm, verified it was still hosed, unpacked this zip, used odin to burn the .tar.md5 to the phone as PDA, rebooted.
It does some gear chunking while booting the first time then reboots - don't panic yet! On second boot it does some more rebuilding, then 'WELCOME!'
Bonus: CWM now sees the actual external sdcard as /sdcard and can find things like roms and backups on it. Edit: This CWM finds .zips on the sdcard, but doesn't seem to know how to backup/restore.
Click to expand...
Click to collapse
What do you mean "This CWM" ? The tars we're talking about in this thread are completely stock from samsung, there is no CWM in these... please elaborate.
hiazn said:
What do you mean "This CWM" ? The tars we're talking about in this thread are completely stock from samsung, there is no CWM in these... please elaborate.
Click to expand...
Click to collapse
After burning this with Odin I ended up with a CWM that I didn't expect - and I've never seen one that actually recognized the external card. However, with all the things I've been trying it's quite possible I ended up burning a boot image I forgot about. I need to try reburning this and see if anything changes, but can't do it right now.
sizer99 said:
After burning this with Odin I ended up with a CWM that I didn't expect - and I've never seen one that actually recognized the external card. However, with all the things I've been trying it's quite possible I ended up burning a boot image I forgot about. I need to try reburning this and see if anything changes, but can't do it right now.
Click to expand...
Click to collapse
Sounds like a plan, let us know what you find.
is this actually
T999UVALEM
or
T999UVLEM
M9x3mos said:
is this actually
T999UVALEM
or
T999UVLEM
Click to expand...
Click to collapse
Mine stock is T999UVLEM, whats the difference between the two?
does this restore everything, including stock recovery, but resetting the counter?
Strange - I had kind of a weird experience with this. I flashed via Odin as usual (as I've done a 100x before) and when it rebooted, it still had remnants of the previous rom I had installed. I didn't get the "welcome" screen as if I was starting from a new factory rom. but at least it got me back to step 1 and I could flash the Lean 2.1 rom again to repair my screw ups.
Related
Hi,
I'm having issues installing CWM Recovery on my Rooted GN2. It's the Canadian variant, SGH-I317M.
It does go through the process of flashing the recovery, but never gets to saying PASS in ODIN. When I try to get into the Recovery, it still has the stock Samsung Recovery. It does, however trip the flash counter.
I'm followiing the instructions here: http://forum.xda-developers.com/showthread.php?t=1988785
This is what I get after flashing in ODIN.
Maybe a bad download? Have you checked to see if it installed? I dont usually recommend this but koush's Rom Manager supports our device now, you can use the app to flash it if your already rooted:thumbup:
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
In your screen shot it shows the f-reset box checked I believe it should be unchecked.
Slff said:
In your screen shot it shows the f-reset box checked I believe it should be unchecked.
Click to expand...
Click to collapse
I tried it with the f-reset box unchecked, and I got it to say PASS, but still no CWM...
cdshepherd said:
Maybe a bad download? Have you checked to see if it installed? I dont usually recommend this but koush's Rom Manager supports our device now, you can use the app to flash it if your already rooted:thumbup:
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
I've also tried to download the file again, and still... No dice...
BlueBagodah said:
I tried it with the f-reset box unchecked, and I got it to say PASS, but still no CWM...
I've also tried to download the file again, and still... No dice...
Click to expand...
Click to collapse
Try rom manager?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
cdshepherd said:
Try rom manager?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
ROM Manager doesn't have a Recovery for the Rogers i317M...
http://forum.xda-developers.com/showthread.php?t=1988785
Sent from my SAMSUNG-SGH-I317 using xda premium
twanskys204 said:
http://forum.xda-developers.com/showthread.php?t=1988785
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Thanks,
I've been following that thread, and it doesn't work. It will trip the flash counter, but doesn't actually install the recovery. It appears that I'm not the only one having this issue after the most recent OTA update...
Can u try and flash a kernel
Then try flashing cwm ...just a hunch
Sent from my SAMSUNG-SGH-I317 using xda premium
BlueBagodah said:
Thanks,
I've been following that thread, and it doesn't work. It will trip the flash counter, but doesn't actually install the recovery. It appears that I'm not the only one having this issue after the most recent OTA update...
Click to expand...
Click to collapse
I'm also having problems after the OTA update. Before OTA update, I was able to flash CWM without problems. Following exact same procedure as before when it was working. Only variable that changed is the OTA update.
wiser212 said:
I'm also having problems after the OTA update. Before OTA update, I was able to flash CWM without problems. Following exact same procedure as before when it was working. Only variable that changed is the OTA update.
Click to expand...
Click to collapse
I was able to install CWM by following this post: http://forum.xda-developers.com/showpost.php?p=36201055&postcount=54
But I'm starting to think that it may have been my fault the whole time...
While doing the 3 button combo to try to boot into Recovery, I was using Vol-DOWN, instead of Vol-UP. So I was going into download mode. I'm going to try flashing the CWM through ODIN again and see if I was just an idiot the whole time.
***EDIT***
It looks like I was just an idiot the whole time...
*facepalm*
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
.. so ROM manager doesnt work to insall cwm recovery after rooting on the i317m? i tried it and didnt succeed. i guess flashing is my only option but i dont want to lose anything on my phone. just install the bootloader/ recovery with no other changes. i want to start flashing some roms... jedi first.. skynote after.. any thoughts or help would be great!!
Clean rom I would suggest its awesome battery life I have a universal theme flashed over clean rom and a custom blue keyboard if I find the link to the themes ill post em on here
Sent from my sgh-1317 aka MY BLUE DEVIL using xda premium
Dewaynelives said:
Clean rom I would suggest its awesome battery life I have a universal theme flashed over clean rom and a custom blue keyboard if I find the link to the themes ill post em on here
Sent from my sgh-1317 aka MY BLUE DEVIL using xda premium
Click to expand...
Click to collapse
I thought of cleanROM but it is pretty stock. I feel if im going to flash any rom i might as well go with something modded and tweaked rather then stock, while keeping most of the note 2 and s-pen features. If i start finding them being a little buggy or draining my battery or anything, ill settle with cleanROM and just flash some custom mods.
i flashed my CWM through MobileODIN. worked like a charm. then i ran into issues with backing up to extSD, which ended up working after i formatted it but i took way longer then onto internal SD.
i know its off topic for this thread..Any suggestions or thoughts on the JEDI X9 and SKYNOTE roms will be great guys. Im all backed up and ready to flash pretty quick here.
I guess you have custom ROM. You must root and rename recovery restore files before you boot to android or stock recovery will be restored.
I wanted to try an AKOP ROM or two on my completely stock, never rooted Note 2 running the OTA UCALK7 update. I followed the guide here (flash the SU injected stock UCALJ2 image) to root and now my note gets stuck at the Samsung logo. I have tried the following:
Downloaded the completely stock UCALJ2 unrooted image and flashed via ODIN.
Tried flashing both stock and rooted ROMs on another computer using the stock USB cable.
Flashed CWM touch via ODIN after flashing rooted UCALJ2 image, it can boot to CWM but fails miserably most likely to the lack of root.
My guess is it's bricked because sammy closed the root hole in the UCALK7 update and flashing back to rooted UCALJ2 isn't enough to bypass the patched exploit. Is there an ODIN flashable complete UCALK7 image that I can try (I've looked to no end, all I can find are rooted zips flashable via CWM) or am I really up the creek?
Pull the battery.
Hold the Center Home Button + Vol Down + Power
Slide the battery in.
If you do this right you can get into odin before the Samsung logo. I just had the same problem because I flashed the wrong recovery. It worked for me.
shakabra said:
Pull the battery.
Hold the Center Home Button + Vol Down + Power
Slide the battery in.
If you do this right you can get into odin before the Samsung logo. I just had the same problem because I flashed the wrong recovery. It worked for me.
Click to expand...
Click to collapse
Thanks but I can get into Odin and flash the stock ROM just fine. It then reboots and gets stuck at the Samsung logo.
Once upon flash completely stock threw Odin.... do the three finger salute, go into stock recovery and factory reset... done
Sent from my SGH-I317 using xda premium
twanskys204 said:
Once upon flash completely stock threw Odin.... do the three finger salute, go into stock recovery and factory reset... done
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
The three finger salute lol:thumbup:
Sent from my GT-N7105 using Tapatalk 2
twanskys204 said:
Once upon flash completely stock threw Odin.... do the three finger salute, go into stock recovery and factory reset... done
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Thanks - I actually figured that part out since my second post. The phone boots after the factory reset however I don't get phone/data service. I've since tried flashing the two AT&T modems I could find, atti317ucalj2modemfixed.zip and ATT K7 Modem - Baseband.zip. Neither resolve the issue.
Cheack ur apn
Sent from my SGH-I317 using xda premium
twanskys204 said:
Cheack ur apn
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Thanks but I can't even enter the network configuration settings - it tells me to insert a SIM. My SIM is in the phone.
I'm having other problems too which I think are partition related. Apps are acting funny, saying there isn't space on the phone (dropbox can't download anything, etc). I'm trying to get TriangleAway installed so I can just RMA it but I can't even download it to my phone. Also a CWM fix permissions fails even though I grant it root access.
It's really simple..download firmware from Sammobile.com flash it in Odin.. u might get stuck on the Samsung screen, if that happens factory reset. Make sure your downloading right file...u r now messing with Odin and it doesn't forgive
Sent from my SGH-I317 using xda premium
twanskys204 said:
It's really simple..download firmware from Sammobile.com flash it in Odin.. u might get stuck on the Samsung screen, if that happens factory reset. Make sure your downloading right file...u r now messing with Odin and it doesn't forgive
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
I know what you're saying, I'm definitely using the right file and process. I'm a pretty seasoned veteran when it comes to rooting/odin/RSD/fastboot, etc. I've run custom ROMs on dozens of phones since the G1. What's happening to me is apparently not a common failure with the note 2 or GS3. Is there a PIT file available for the AT&T Note 2? I see one for the Verizon Note 2 but I wouldn't dare try to flash that.
There is a pit file around but I really don't think it's that.
And also just checking don't mean to insult ur intelligence but if u are using Odin it will be a .tar, if it's a recovery its I .zip
Sent from my SGH-I317 using xda premium
twanskys204 said:
There is a pit file around but I really don't think it's that.
And also just checking don't mean to insult ur intelligence but if u are using Odin it will be a .tar, if it's a recovery its I .zip
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Yeah, it's a tar file I'm flashing through Odin, got it from SamsungUpdates: Samsung-Updates.com-SGH-I317_ATT_1_20121005095854_bpaaavv07o.
I also tried flashing the stock ROM in deodex'd zip form after I got a custom recovery on there, still no dice. The non-functioning modem and lack of proper root/storage affects both Sammy and CM/AKOP based ROMs. I don't know about the modem part but I've seen weird things like this when the NAND starts going bad and things written to it don't "stick." I don't think that's the case here since it's only on its 4th or 5th flash. More than likely the latter problem is a file system issue. I have no idea about the radio.
I'm going to try and exchange it tomorrow. At least I got the flash count cleared and I'm back on a stock ROM (with the same problems).
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
Hello all
I unfortunately had to get a replacement for my S3 because the charging port got screwed up.
I tried to root the phone by installing CWM and it seemed to go fine. I did this with Odin using qbking77's methods and files.
I went to look for my zip file to flash and I could find no zip files at all.
It kept saying that E won't mount and stuff like that.
I had a stock recovery tar file for my GalaxyS3 from qbking77 that I used before to get to stock recovery for updates
I flashed it with odin and it said it flashed fine.
Phone seems to be working fine.
I went back to make sure it was there and it showed the little android guy with his heart spinning and then turning red and he died!
Several error messages came up in red.
Anyone ever hear about this and what did I do wrong?
I am sure I used the files I have used for my Galaxy before.
The phone still works so far thankfully!
Any advise and help would be appreciated.
Mike
mikeinstlouis said:
Hello all
I unfortunately had to get a replacement for my S3 because the charging port got screwed up.
I tried to root the phone by installing CWM and it seemed to go fine. I did this with Odin using qbking77's methods and files.
I went to look for my zip file to flash and I could find no zip files at all.
It kept saying that E won't mount and stuff like that.
I had a stock recovery tar file for my GalaxyS3 from qbking77 that I used before to get to stock recovery for updates
I flashed it with odin and it said it flashed fine.
Phone seems to be working fine.
I went back to make sure it was there and it showed the little android guy with his heart spinning and then turning red and he died!
Several error messages came up in red.
Anyone ever hear about this and what did I do wrong?
I am sure I used the files I have used for my Galaxy before.
The phone still works so far thankfully!
Any advise and help would be appreciated.
Mike
Click to expand...
Click to collapse
The issue is because of a change that was made to the Newer Devices. Use one of the Recoveries from THIS THREAD.
If it's a new s3 its a known issue with the phone...u need a modded recovery. Check here http://forum.xda-developers.com/showthread.php?t=2391616
Sent from my SPH-L710 using xda app-developers app
I am hoping that this means that I haven't fried that part of my phone and I can still install a recovery. Are these recoveries that I could use to root my phone or custom recoveries that I can revert to to get over the air updates. Thank you very much for your help you guys. I'm still kind of new with this even though I've been doing it for years
Sent from my SPH-L710 using XDA Premium HD app
mikeinstlouis said:
I am hoping that this means that I haven't fried that part of my phone and I can still install a recovery. Are these recoveries that I could use to root my phone or custom recoveries that I can revert to to get over the air updates. Thank you very much for your help you guys. I'm still kind of new with this even though I've been doing it for years
Sent from my SPH-L710 using XDA Premium HD app
Click to expand...
Click to collapse
Yes you can still use these Recoveries. I doubt you " fried " your device. Use these Recoveries in the Root process where you would use the older ones. Yes you can Revert them Back.
Then how can I revert back to get over the air updates? The stock recovery that I flashed showed the little Android guy had died..
Sent from my SPH-L710 using XDA Premium HD app
I think this should work for you just fine. Just be sure to not miss the step about the factory reset.
http://forum.xda-developers.com/showthread.php?t=1904099
[ROM/RESTORE][!MD4 OTA!](5-10)Quick Return to UNROOTED STOCK WITH FLASH COUNT RESET
Sent from my SPH-L710 using Tapatalk 2
From what I read you have to have a recovery to flash this.. I have no recover... And CWM won't let me do anything... That's my problem.. This new style of phone won't let me put on a functional recovery.. Does that make sense?
Sent from my SPH-L710 using xda premium
mikeinstlouis said:
From what I read you have to have a recovery to flash this.. I have no recover... And CWM won't let me do anything... That's my problem.. This new style of phone won't let me put on a functional recovery.. Does that make sense?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
In the OP of the thread I linked you it gives instructions on how to push the Recovery with ADB. It also has Recoveries you can do through ODIN.
TEAM MiK
MikROMs Since 3/13/11
Basically I do have common sense and and I'm pretty knowledgeable when it comes to working with phones but this problem I have is different.
I purchased this phone(I747) already bricked thinking I can fix since I have before. It goes to cwm 6.0.3.4 and boots to Odin. Last known os was cm but don't know what version. Not even clear what bootloader it's but when trying to boot up there's the blue cm Android guy.
So here's what I tried so far to fix my problem.
1. Tried to flash the mjb restore posted somewhere on here. Flashed with no errors but when I reboot still the blue Android.
2. Wipe and formatted the proper things and tried flashing a couple of roms but all gave me error 7.
3. Tried flashing a different recovery thru Odin, all passed but non stuck. Can't get rid of my current recovery.
4. Tried to Odin 4.3 firmware but that failed.
Kinda running out of ideas on what to try next, can someone help me figure out what I'm doing wrong or what's the problem?
Sent from my SM-N900T using XDA Premium 4 mobile app
donutkidd said:
Basically I do have common sense and and I'm pretty knowledgeable when it comes to working with phones but this problem I have is different.
I purchased this phone(I747) already bricked thinking I can fix since I have before. It goes to cwm 6.0.3.4 and boots to Odin. Last known os was cm but don't know what version. Not even clear what bootloader it's but when trying to boot up there's the blue cm Android guy.
So here's what I tried so far to fix my problem.
1. Tried to flash the mjb restore posted somewhere on here. Flashed with no errors but when I reboot still the blue Android.
2. Wipe and formatted the proper things and tried flashing a couple of roms but all gave me error 7.
3. Tried flashing a different recovery thru Odin, all passed but non stuck. Can't get rid of my current recovery.
4. Tried to Odin 4.3 firmware but that failed.
Kinda running out of ideas on what to try next, can someone help me figure out what I'm doing wrong or what's the problem?
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What did you try to flash? Status 7 means you don't have the right device for what you were trying to flash or that your build.prop was modified by the previous owner to another device name.
I believe you'll need to flash a ROM matching the current device name and work from there.
Although, I find it odd that flashing with Odin doesn't work. Have you tried flashing stock?
BWolf56 said:
What did you try to flash? Status 7 means you don't have the right device for what you were trying to flash or that your build.prop was modified by the previous owner to another device name.
I believe you'll need to flash a ROM matching the current device name and work from there.
Although, I find it odd that flashing with Odin doesn't work. Have you tried flashing stock?
Click to expand...
Click to collapse
Yep I tried stock 4.1.1 and 4.3 thru Odin and failed. I tried installing a new recovery thru the current recovery using a zip file and it went thru with no errors but reboot and nothing has changed. Something when flashing the restore and the bootloader.
Sent from my SM-N900T using XDA Premium 4 mobile app
donutkidd said:
Yep I tried stock 4.1.1 and 4.3 thru Odin and failed. I tried installing a new recovery thru the current recovery using a zip file and it went thru with no errors but reboot and nothing has changed. Something when flashing the restore and the bootloader.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can try flashing another/updated recovery through Odin. But until you find out what device your build.prop is setup to, you won't be able to flash a ROM through recovery.
BWolf56 said:
You can try flashing another/updated recovery through Odin. But until you find out what device your build.prop is setup to, you won't be able to flash a ROM through recovery.
Click to expand...
Click to collapse
I tried every recovery for this phone that's up to date so yeah I don't know what else to do. And how can I figure that out? The build.prop part?
Sent from my SM-N900T using XDA Premium 4 mobile app
donutkidd said:
I tried every recovery for this phone that's up to date so yeah I don't know what else to do. And how can I figure that out? The build.prop part?
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's in your System folder. Should be able to navigate to it using your recovery.
BWolf56 said:
It's in your System folder. Should be able to navigate to it using your recovery.
Click to expand...
Click to collapse
Will it still be there even if I formatted the system? If so what are the adb commands so I can pull it and post it?
donutkidd said:
Will it still be there even if I formatted the system? If so what are the adb commands so I can pull it and post it?
Click to expand...
Click to collapse
Hopefully it is. And I duno about the command, you'll have to look that one up (or perhaps someone here knows it).
If you formatted /system, its gone and shouldn't matter. But imo you should never format system manually. Otherwise you end up with nothing to boot or troubleshoot if things go wrong.
From your recovery, find where you can use the terminal emulator and enter
getprop ro.boot loader
This is what firmware you need to be flashing via odin.
Sent from my SGH-T999 using Tapatalk
Ok I will try that when I get home.
Sent from my SM-N900T using XDA Premium 4 mobile app
DocHoliday77 said:
If you formatted /system, its gone and shouldn't matter. But imo you should never format system manually. Otherwise you end up with nothing to boot or troubleshoot if things go wrong.
From your recovery, find where you can use the terminal emulator and enter
getprop ro.boot loader
This is what firmware you need to be flashing via odin.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Ok I did the getprop ro.bootloader command and it's I747UCDLK3. I have already tried the lk3 Odin but let me try to re download a fresh copy of it.
Sent from my SM-N900T using XDA Premium 4 mobile app
No dice, I even downloaded a 4.1.1 lk3 rom. It flashed and said successful so I rebooted and back to the blue Android. Is it possible NY partitions or whatever are corrupt and if so anyway to fix it?
Sent from my SM-N900T using XDA Premium 4 mobile app
I'm kinda at a loss. Wondering if its a partition not flashed by Odin that's been corrupted...
No idea if this'll help or not, but download this.
http://www.androidfilehost.com/?fid=23060877489996938
(It is a 16gb model right?)
Now flash firmware in Odin in like usual, but check the repartition checkbox, then click the PIT button and browse to and select the file I just linked. Verify.
Click start and cross fingers.
Another thing you can try...flash twrp with Odin, but uncheck auto reboot. After it says PASS, pull the battery. Put it back in and boot recovery. Hopefully it'll stick now.
Now you can try flashing some roms again, and use the built in file manager to look for any issues/anomalies.
I'm not sure what version LK3 is, but it sounds kinda old, so you may want to look for a 4.1.1 rom to start with. That shouldn't give you any status 7 errors. Or if you want to flash newer roms you'll need to edit the asserts in the updater script.
DocHoliday77 said:
I'm kinda at a loss. Wondering if its a partition not flashed by Odin that's been corrupted...
No idea if this'll help or not, but download this.
http://www.androidfilehost.com/?fid=23060877489996938
(It is a 16gb model right?)
Now flash firmware in Odin in like usual, but check the repartition checkbox, then click the PIT button and browse to and select the file I just linked. Verify.
Click start and cross fingers.
Another thing you can try...flash twrp with Odin, but uncheck auto reboot. After it says PASS, pull the battery. Put it back in and boot recovery. Hopefully it'll stick now.
Now you can try flashing some roms again, and use the built in file manager to look for any issues/anomalies.
I'm not sure what version LK3 is, but it sounds kinda old, so you may want to look for a 4.1.1 rom to start with. That shouldn't give you any status 7 errors. Or if you want to flash newer roms you'll need to edit the asserts in the updater script.
Click to expand...
Click to collapse
I honestly think I tried what you suggested already but just to triple check I will do so again in the morning and report back with hopefully good news.
Sent from my SM-N900T using XDA Premium 4 mobile app
@BWolf56
Do you guys have a recovery flashable package for the 4.1.1 or 4.1.2 firmware? (I'm guessing that's what LK3 is.)
If so maybe flashing that would help?
DocHoliday77 said:
@BWolf56
Do you guys have a recovery flashable package for the 4.1.1 or 4.1.2 firmware? (I'm guessing that's what LK3 is.)
If so maybe flashing that would help?
Click to expand...
Click to collapse
No, nothing for 4.1.1 (LK3).
I don't think that's his issue though. Last time I saw that issue was on the S1 (Captivate) and the solution was to use Heimdall.
If the repartition doesn't work though, I'm not exactly sure what will.
DocHoliday77 said:
@BWolf56
Do you guys have a recovery flashable package for the 4.1.1 or 4.1.2 firmware? (I'm guessing that's what LK3 is.)
If so maybe flashing that would help?
Click to expand...
Click to collapse
I was just reading what you said in this post - > ([Q] Can't flash stock rom through Odin, phone only boots in download mode. Help!) and it does sound awfully like my situation being that nothing sticks after flashing.
donutkidd said:
I was just reading what you said in this post - > ([Q] Can't flash stock rom through Odin, phone only boots in download mode. Help!) and it does sound awfully like my situation being that nothing sticks after flashing.
Click to expand...
Click to collapse
Do you have the actual link to that thread? Search is derping on me.
BWolf56 said:
Do you have the actual link to that thread? Search is derping on me.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2415409
Sent from my SM-N900T using XDA Premium 4 mobile app
donutkidd said:
http://forum.xda-developers.com/showthread.php?t=2415409
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ouff that's one bad issue, it can take a while to figure out which partition got messed up. And sadly, I can't be much help there :/