Related
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
Hi all! I'm new here so please refrain from flaming me...
I'm no noob to flashing the rom on my phone as I have successfully carried out the procedure multiple times. However, on this occasion things didn't go as planned. I began the procedure to update my S3 via odin to the new firmware that was released yesterday, however when the process got to 'system.img' the status bar just hung in the same place (just past the beginning of the bar) for a good 20 minutes... I panicked and unplugged my phone... BAD MOVE. I now get the error message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." and the only thing I can do is put my phone in odin mode, which I did, and tried to install the stock jelly bean rom, the exact same thing happened as before...
What should I do?
Thanks in advance
You tried to flash the stock firmware?
Sent from a very Wicked T999
alloycowboy said:
You tried to flash the stock firmware?
Sent from a very Wicked T999
Click to expand...
Click to collapse
Yes I did, and as I said, the exact same thing happened as before... :crying:
ExperimentalHDX said:
Hi all! I'm new here so please refrain from flaming me...
I'm no noob to flashing the rom on my phone as I have successfully carried out the procedure multiple times. However, on this occasion things didn't go as planned. I began the procedure to update my S3 via odin to the new firmware that was released yesterday, however when the process got to 'system.img' the status bar just hung in the same place (just past the beginning of the bar) for a good 20 minutes... I panicked and unplugged my phone... BAD MOVE. I now get the error message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." and the only thing I can do is put my phone in odin mode, which I did, and tried to install the stock jelly bean rom, the exact same thing happened as before...
What should I do?
Thanks in advance
Click to expand...
Click to collapse
Go to your phone thread and look for the unbrick package for the SGS3
Sent from my SGH-I997 using xda app-developers app
alexischino said:
Go to your phone thread and look for the unbrick package for the SGS3
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
Is this the thread called 'Welcome to your device, the Galaxy S III'? If not, I'd appreciate it if a link can be provided to this thread.
alexischino said:
Go to your phone thread and look for the unbrick package for the SGS3
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
I don't believe we have that for our model.
If you can still get download mode there's hope, maybe not a lot in this case, but there is some.
Try to flash cwm or twrp via odin. If successful boot recovery and try to flash a stock rom. Hopefully it only screwed up the system partition. ...
Never unplug till odin says either PASS, FAIL, or RESET. You may end up really lucky this time. If its taking a long time, just leave the room.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
I don't believe we have that for our model.
If you can still get download mode there's hope, maybe not a lot in this case, but there is some.
Try to flash cwm or twrp via odin. If successful boot recovery and try to flash a stock rom. Hopefully it only screwed up the system partition. ...
Never unplug till odin says either PASS, FAIL, or RESET. You may end up really lucky this time. If its taking a long time, just leave the room.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Yep, never unplug a phone when ur doing a update via odin or u will get a brick phone, i hope u can get CWM or twrp installed.......
Sent from my SGH-I997 using xda app-developers app
alexischino said:
Yep, never unplug a phone when ur doing a update via odin or u will get a brick phone, i hope u can get CWM or twrp installed.......
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
DocHoliday77 said:
I don't believe we have that for our model.
If you can still get download mode there's hope, maybe not a lot in this case, but there is some.
Try to flash cwm or twrp via odin. If successful boot recovery and try to flash a stock rom. Hopefully it only screwed up the system partition. ...
Never unplug till odin says either PASS, FAIL, or RESET. You may end up really lucky this time. If its taking a long time, just leave the room.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Thanks for your help so far guys... I'm going to try that now... I'll keep you posted...
Bad news... FAIL appears when I try...
Does it say fail when you try a full firmware flash?
Do you get any response at all when trying to boot recovery?
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Does it say fail when you try a full firmware flash?
Do you get any response at all when trying to boot recovery?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
When I try a whole firmware flash it just hangs right after it starts, and when I tried to boot recovery (was that what was previously suggested?) it says fail...
I previously suggested trying to flash recovery only using odin. Before you just said you can only boot to download mode, so I was asking what does it do when you try to boot into recovery?
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
I previously suggested trying to flash recovery only using odin. Before you just said you can only boot to download mode, so I was asking what does it do when you try to boot into recovery?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Oh right, my bad. When I try to boot into recovery the error screen saying to recover with Kies pops up.
Good news! I followed this http://forum.xda-developers.com/showthread.php?t=1905655 and I am now able to get into recovery mode. I guess my only option now is to wipe my data, install stock JB and everything should be ok?
Guys, even better news... That thread was the solution! My phone is now back to normal! I did lose a lot of pictures, but oh well, I'm glad I have my phone back to normal. Thanks for all your help! :good:
Wow! Ok, I am glad you got it working again, but you took a huge risk flashing that. Luckily its just the kernel aparently, but you should never flash anything from the international forum. More hard bricks have occured from flashing international stuff than anything else.
Just pointing this out so you or others reading this don't take it as meaning they can flash international roms and mods.
Glad it did work out for you though!
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Wow! Ok, I am glad you got it working again, but you took a huge risk flashing that. Luckily its just the kernel aparently, but you should never flash anything from the international forum. More hard bricks have occured from flashing international stuff than anything else.
Just pointing this out so you or others reading this don't take it as meaning they can flash international roms and mods.
Glad it did work out for you though!
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Thank you for the info! I keep that in mind so I don't run into any other problems. Now, I'm deciding whether I should try to install that firmware that caused the problem again... Even though I know what to do in the event that odin hangs, the results may not be the same... What do you think?
On a side note: It seems I only text messages and app settings, luckily I backed up my phone with Kies a few days ago so it's all good
ExperimentalHDX said:
Thank you for the info! I keep that in mind so I don't run into any other problems. Now, I'm deciding whether I should try to install that firmware that caused the problem again... Even though I know what to do in the event that odin hangs, the results may not be the same... What do you think?
On a side note: It seems I only text messages and app settings, luckily I backed up my phone with Kies a few days ago so it's all good
Click to expand...
Click to collapse
Before you do, check under the battery so you are certain of the phone model. There are 3 variants if the T999, and they cannot flash each others firmware.
Also, I don't believe you mentioned which firmware you tried, or I missed it, but which was it?
And i said it before, but do not unplug during flash. It may seem to take forever if it hangs, but it will eventually Fail out if it does.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Before you do, check under the battery so you are certain of the phone model. There are 3 variants if the T999, and they cannot flash each others firmware.
Also, I don't believe you mentioned which firmware you tried, or I missed it, but which was it?
And i said it before, but do not unplug during flash. It may seem to take forever if it hangs, but it will eventually Fail out if it does.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Okay, it's definitely the GT-I9300, and the firmware I tried to flash was this one from SamMobile:
GT-I9300 United Kingdom 2013 July 4.1.2 I9300XXEMG4 I9300OXAEMG4
And okay, it's just that it it hung for so long I thought "well, that's not right", panicked, then yeah, messed up my phone.
ExperimentalHDX said:
Okay, it's definitely the GT-I9300, and the firmware I tried to flash was this one from SamMobile:
GT-I9300 United Kingdom 2013 July 4.1.2 I9300XXEMG4 I9300OXAEMG4
And okay, it's just that it it hung for so long I thought "well, that's not right", panicked, then yeah, messed up my phone.
Click to expand...
Click to collapse
Ahhhh, well, I know now why it didn't brick your phone when you flsshed thst kernel! You do hsve the correct phone for that. So you will need to reverse what I told you and do not flsdh anything from this forum! Sorry for the confusion, I assumed you had a T999.
It sounds like you have the right firmware, but I know very little about the international models. They are very different than ours. You should definitely go to the International forum from here on. Very little info you get here will be relevant and you cannot use any of our roms or otherwise.
Good luck!
Sent from my SGH-T999 using xda premium
I am at the point where my AT&T Note 2 SGH-i317 either displays the Samsung Note II screen or I can go into the Odin screen. It will not open recovery.
If I try to install CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar.md5 using Odin, I get the message from the title.
Odin appears to load the factory 4.1 rom but I end up with the same message at the end.
I had successfully restored 4.1 using Odin and then the phone auto updated to 4.3. After that, I followed the instructions for installing Jedi Master but the phone won't restart. I tried to use the same files I got 4.1 back with (this has worked twice before from 4.3) but they will no longer work. Is there anything I can do to get the phone working again?
mid_life_crisis said:
I am at the point where my AT&T Note 2 SGH-i317 either displays the Samsung Note II screen or I can go into the Odin screen. It will not open recovery.
If I try to install CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar.md5 using Odin, I get the message from the title.
Odin appears to load the factory 4.1 rom but I end up with the same message at the end.
I had successfully restored 4.1 using Odin and then the phone auto updated to 4.3. After that, I followed the instructions for installing Jedi Master but the phone won't restart. I tried to use the same files I got 4.1 back with (this has worked twice before from 4.3) but they will no longer work. Is there anything I can do to get the phone working again?
Click to expand...
Click to collapse
Which version of odin are you using?
Can you enter stock recovery or only download mode?
If you can get into stock recovery if it says anything about knox then you have the new bootloader, which you should if you updated to 4.3 via an ota update or an odin file. If you have this we can skip a few steps. If you don't, we will basically be starting from the beginning.
Assuming you have the newer bootloader, this is what I need you to do.
Go to teamw.in and download the latest twrp and make sure it's the recovery.img.tar.md5 flash that through odin.
In the mean time start a fresh download of jedi masterx2. When that download finishes make sure you verify the md5 sum. This is key. One digit off and the entire download is bad and you'll end up bootlooping again.
Once you have twrp and a good download of jmx2 boot into twrp. Do a system wipe and then flash the rom.
Let me know how it works. Just be patient and we can get this fixed for you. As long as you can power on you can recover your phone and make it work.
Sent from my SM-N900T using XDA Premium 4 mobile app
I use an app called hash droid to verify md5
Sent from my Jedi MasterX Note 2
kushXmaster said:
Which version of odin are you using?
Can you enter stock recovery or only download mode?
If you can get into stock recovery if it says anything about knox then you have the new bootloader, which you should if you updated to 4.3 via an ota update or an odin file. If you have this we can skip a few steps. If you don't, we will basically be starting from the beginning.
Assuming you have the newer bootloader, this is what I need you to do.
Go to teamw.in and download the latest twrp and make sure it's the recovery.img.tar.md5 flash that through odin.
In the mean time start a fresh download of jedi masterx2. When that download finishes make sure you verify the md5 sum. This is key. One digit off and the entire download is bad and you'll end up bootlooping again.
Once you have twrp and a good download of jmx2 boot into twrp. Do a system wipe and then flash the rom.
Let me know how it works. Just be patient and we can get this fixed for you. As long as you can power on you can recover your phone and make it work.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Odin shows the Knox flag, so I assume I am on 4.3.
I cannot find this file, "recovery.img.tar.md5".
The most likely looking file I found was this, but it isn't an md5, "openrecovery-twrp-2.6.3.1-t0lteatt.img.tar".
In fact I find no files with an "md5" extension on that site.
mid_life_crisis said:
Odin shows the Knox flag, so I assume I am on 4.3.
I cannot find this file, "recovery.img.tar.md5".
The most likely looking file I found was this, but it isn't an md5, "openrecovery-twrp-2.6.3.1-t0lteatt.img.tar".
In fact I find no files with an "md5" extension on that site.
Click to expand...
Click to collapse
I apologize. For the recovery.img it needs to be the tar extension.
Once you push that to the device you're back in business.
Sent from my SM-N900T using XDA Premium 4 mobile app
kushXmaster said:
I apologize. For the recovery.img it needs to be the tar extension.
Once you push that to the device you're back in business.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I gave you a thanks because I truly appreciate the attempt to help me, but that wouldn't load either.
Fortunately the guy at the Samsung counter was able to use a Samsung loader to force 4.3 and the phone is working again.
Just curious - is your knox warranty counter back to zero in download mode?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
mid_life_crisis said:
I gave you a thanks because I truly appreciate the attempt to help me, but that wouldn't load either.
Fortunately the guy at the Samsung counter was able to use a Samsung loader to force 4.3 and the phone is working again.
Click to expand...
Click to collapse
Hmm that us interesting. I wonder why it wouldn't load...
What version of odin do you use? I've been using 3.07 for a long time with no issues.
I'm curious about the knox counter as well.
Sent from my SM-N900T using XDA Premium 4 mobile app
Zen Arcade said:
Just curious - is your knox warranty counter back to zero in download mode?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Neither counter reset. It still displays the count for custom roms and a "1" for the Knox toggle.
kushXmaster said:
Hmm that us interesting. I wonder why it wouldn't load...
What version of odin do you use? I've been using 3.07 for a long time with no issues.
I'm curious about the knox counter as well.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's 3.7
That's good and weird at the same time.
Its good because its what we expected AND that the Samsung person fixed your phone even though you tripped the KNOX bit.
Its weird because the Samsung person fixed your phone even though you tripped the KNOX bit.
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 :/