Related
I am at my wits end right now. I can see my phone on com3 when it is booted up all the way, but it will not see it when in download mode. I erroneously flashed this file earlier, forgetting I did not have a regular GSII: I9100_APBOOT_I9100XXKP2_CL17109_REV02_eng_mid_ship.tar.md5
What other information would help diagnose this problem?
I currently have stock EL26 installed.
Alternatively, is it safe to install CM9 from this recovery? Seems to me I should resolve this first..
edit: I do not have an unrecognized device, I have tried more than one usb cable and port
Try this:
Redownload the drivers for the phone, install them and let your cpu reset. See if Odin sees your phone then.
I know with my GT10.1 it takes a few seconds more for Odin to see it so... But my ET4G pops up pretty fast.
The EL26/CWM is the kernel/recovery that you want to use when your flashing CM9 Alfa 5 and below.
But like you said... You may want to figure out why Odin isn't seeing your phone when it's in download mode.
Also... Do you have Kies installed on your cpu??? It'll cause problems with Odin to.
Have you tried Mobile Odin for what you want to do. I do almost everything involving CM and flashing with it. Works like a charm.
Sent From My Galaxy Class Star Fighter...
How in the hell do you forget you don't have a international version?! Smh
Sent from my SPH-D710 using xda premium
fryingpan0613 said:
How in the hell do you forget you don't have a international version?! Smh
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
WoW... He just edited his post as I was replying... Doesn't flashing an international tar mess up the bootloader??? I'm really not to sure where you go next.
If his phone still boots up okay couldn't help still use Mobile Odin and flash the right setup.
What was that old school Saturday morning psa... "Reading is fundamental" or something like that.
Sent From My Galaxy Class Star Fighter...
What is the right setup to use? A fresh GB rom install? I am at a loss at this point.
Yeah I ****ed up, I have not messed with my phone in many months.
Edit: driver reinstall did not work, do not have kies installed. mobile odin works on GB then? I can use the e4gt-autofix if that makes a difference. Updating from the stock recovery does not seem to work, it will start, then give me the ! triangle with sad android.
hilo4321 said:
What is the right setup to use? A fresh GB rom install? I am at a loss at this point.
Yeah I ****ed up, I have not messed with my phone in many months.
Edit: driver reinstall did not work, do not have kies installed. mobile odin works on GB then? I can use the e4gt-autofix if that makes a difference. Updating from the stock recovery does not seem to work, it will start, then give me the ! triangle with sad android.
Click to expand...
Click to collapse
Unfortunately my friend, I think you are hosed. The international PIT file is exceptionally different from the one we use for our phone. I don't remember the specifics but basically it remaps your partitions and causes USB to not work correctly. Your best bet is to try a JTAG service. I've heard MobileTechVideos.com is pretty well rated.
Sorry!
My phone is currently functioning properly when booted up. What are the implications of this beyond not being able to change roms (and not having a notification bar..wtf)?
Edit: ok I take it back, mass storage is not working either. also, I am definitely willing to buy Mobile Odin if anyone has any ideas.
hilo4321 said:
What is the right setup to use? A fresh GB rom install? I am at a loss at this point.
Yeah I ****ed up, I have not messed with my phone in many months.
Click to expand...
Click to collapse
Not getting on you m8 but... Flashing a rom for another device even if it's the same model is really really bad. Like rwilco said, yes the International GS2 and our ET4G's are the same devices but there software is very different.
hilo4321 said:
My phone is currently functioning properly when booted up. What are the implications of this beyond not being able to change roms (and not having a notification bar..wtf)?
Click to expand...
Click to collapse
Well... Like you said, most likely you will not be able to make any changes as in roms, kernels or things like that. And if you have any hardware issue you won't be able to get any support from Sprint. And you sure as hell won't be able to receive any OTA's from Sprint or Samsung.
Can you do something for use... Go to "Settings" then "About Phone" and under "Model Number" & "Baseband Version" and tell us what it says there.
I'm not really sure this would/can help you but if your phone still boots and runs you maybe able to Odin the right tar file and see if that fixes it. I mean it could work but I really doubt it. And what's the worst that could happen... It could brick it, then you could file an insurance claim... Just saying...
Where did you get the file from that you flashed??? Most likely not from this (ET4G) forum, should have read up a bit more before you started messing around with flashing roms again. Some things aren't easily fixable.
Sent From My Galaxy10.1 Class Starship....
I am a lucky SOB. I was able to use e4gtauto-sfx to put el29/CWM back on to my phone, and as a result I restored my nandroid backup. I have full function back, except, of course, no odin in download mode.
My baseband is S710.10 S.EK02 with standard model number sph d710.
I believe it came from the android forums, but like i said it was in the SGII area.
What tar file would I be looking for?
Doing some research m8... Give me a few mins....
Make sure you have Mobile Odin installed.
Sent From My Galaxy Class Star Fighter...
hilo4321 said:
I am a lucky SOB. I was able to use e4gtauto-sfx to put el29/CWM back on to my phone, and as a result I restored my nandroid backup. I have full function back, except, of course, no odin in download mode.
Click to expand...
Click to collapse
Ok... Yes you are my friend!!!! But I fear we are not completely out of the woods as of yet. You still have the "no Odin in download" thing still. And that could still be an issue, but at least your back up and running.
hilo4321 said:
My baseband is S710.10 S.EK02 with standard model number sph d710.
Click to expand...
Click to collapse
This is telling me that your on an older baseband... I'm running CM9 and my baseband reads "EL29" which I think is the most resent/updated baseband. I don't want to scare you but I really wish a dev would jump in here and shed some of there wisdom. (I'm almost to the point where I'm winging it.) But I feel we need to get your baseband to EL29.
hilo4321 said:
I believe it came from the android forums, but like i said it was in the SGII area.
Click to expand...
Click to collapse
From now on promise us you'll just use this site and forum for all of your download needs.... Please.
hilo4321 said:
What tar file would I be looking for?
Click to expand...
Click to collapse
Try this post... http://forum.xda-developers.com/showthread.php?t=1433101
Follow the instructions for the Android Install, about halfway down in the first post.
Sent From My Galaxy10.1 Class Starship....
Oh sweet Jesus, I promise.
Now when I do this will this wipe everything? I'm not terribly clear on that. Seems to me that it will.
I really appreciate the help man.
There are 2 different versions... One will wipe everything and one will leave all of your user data intact.
And like I said, I'm not a 100% sure this will fix it but I think we are moving in the right direction.
And not a problem... It's helping me learn more about what goes on inside our devices.
I am still a little worried about your bootloader though. If that was jacked up by flashing the wrong rom I don't know if this will fix it.
Question, when you hook up your device to your cpu when it's booted up are you still able to do things like transfer files and such???
Sent From My Galaxy10.1 Class Starship....
I can use mass USB now. I wont be able to test the el29 now though as I'm away now. I will report back when I can.
hilo4321 said:
I can use mass USB now. I wont be able to test the el29 now though as I'm away now. I will report back when I can.
Click to expand...
Click to collapse
That's great brother.... I'm really glad I could help ya get up and running to the point where you can a least have a use able device.
Sent From My Galaxy10.1 Class Starship....
EL29 was the last version of Gingerbread put out. You'll be able to use mobile Odin to flash stuff but you'll never get the USB to recognize in DL mode. I think jtag might be the only way to restore complete functionality.
---------- Post added at 11:42 PM ---------- Previous post was at 11:36 PM ----------
For now you'll be alright as long as you can get into recovery mode fine then you can flash modems in there(since mobile Odin can't flash them for our phone).
Your baseband (modem) should not matter and changing it won't have any affect on your problem. Good luck and let us know how out turns out.
Solved
I am posting now in case someone comes upon this post down the road.
I am now running cyanogen 9 on my e4gt. This thread saved me, as I was finally able to get odin to work. With that, I was able to flash a new recovery onto my phone (I used StockCWM-EL26). Then once I got that on there I flashed over to the Beta 1 build of Cyanogenmod for e4gt.
I'm sorry I can't be more clear or provide links, it took me a lot of crawling around the forums to figure this out. Perhaps someone more knowledgeable than I can clean up/expand my post. Let me tell you though, it feels really good to get this thing running smoothly again.
If you have any questions I'll try to help.
Good luck, idiot!
That's awesome dude. Remember stay in this forum :beer::thumbup:
sent from MY BAD A$$ ET4G
Hello all,
I am facing problems with my SIII right now. I was running AOKP but due to the bluetooth not being able to sync with my stereo, I decided to go back to stock rooted. I just flashed back the stock rooted image using Odin, but now my phone sits at the Samsung screen with the blue notification light on. I have tried rebooting, and it gets to this point (after the rethink possible screen) and just sits. I am thinking another flash in Odin is in order? Is there a stock, non root image I can flash via odin? I am just really lost for ideas right now and any input would be appreciated! Thanks!
Update:
I tried flashing with odin again and this time I got a failed. It was in the process of flashing the "system". I am kinda starting to freak out. I am hoping that it's just the file I'm using (though it just worked not even a few days ago.) I am trying again and if this one bombs out, I think I am going to try a different file. The one I am downloading to try next is the "stock unroot" from the how-to video. Anyone have any luck with this?
Another Update:
I just re-flashed with odin, this time it says it successfully completed but once again it's stuck at the flashing Samsung logo with the indicator led on.... I am starting to really freak out lol. I have another file downloading that is supposedly just stock, no root or anything...
rakhov said:
Hello all,
I am facing problems with my SIII right now. I was running AOKP but due to the bluetooth not being able to sync with my stereo, I decided to go back to stock rooted. I just flashed back the stock rooted image using Odin, but now my phone sits at the Samsung screen with the blue notification light on. I have tried rebooting, and it gets to this point (after the rethink possible screen) and just sits. I am thinking another flash in Odin is in order? Is there a stock, non root image I can flash via odin? I am just really lost for ideas right now and any input would be appreciated! Thanks!
Update:
I tried flashing with odin again and this time I got a failed. It was in the process of flashing the "system". I am kinda starting to freak out. I am hoping that it's just the file I'm using (though it just worked not even a few days ago.) I am trying again and if this one bombs out, I think I am going to try a different file. The one I am downloading to try next is the "stock unroot" from the how-to video. Anyone have any luck with this?
Click to expand...
Click to collapse
Actually have the exact same situation going on right now, I will post if I can find a fix. Downloading an alternate stock build I found now and will let you know how it goes.
Glad to have a partner in crime
http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-att-galaxy-s3-sgh-i747/
This is the file/procedure I am going to try next. Good luck and I will stay posted with any info, likewise!
rakhov said:
Glad to have a partner in crime
http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-att-galaxy-s3-sgh-i747/
This is the file/procedure I am going to try next. Good luck and I will stay posted with any info, likewise!
Click to expand...
Click to collapse
Thats exactly what Odin is working on loading now, Download had just finished.
avarize said:
Thats exactly what Odin is working on loading now, Download had just finished.
Click to expand...
Click to collapse
Wicked, well good luck solider....Does anyone know the signifigince of the led being on? It looks like it is slightly pulsating too...I hope this isn't the "sorry, you just broke it" notification XD
rakhov said:
Wicked, well good luck solider....Does anyone know the signifigince of the led being on? It looks like it is slightly pulsating too...I hope this isn't the "sorry, you just broke it" notification XD
Click to expand...
Click to collapse
I've always noticed the LED being on during boot (or some of the boot) and it was also on when I had a bootloop during cm9 so I don't think it means anything.
Fair enough, I guess I never paid that much attention till now when things don't work heh. I do recall reading about someone else having the similar issue using odin...I am trying to find the post and if there was any follow up on it.
rakhov said:
Fair enough, I guess I never paid that much attention till now when things don't work heh. I do recall reading about someone else having the similar issue using odin...I am trying to find the post and if there was any follow up on it.
Click to expand...
Click to collapse
Didn't seem to have any luck with that download/odin. Still stuck, Trying a few more things, although I am a bit lost as to what to do from here.
---------- Post added at 02:52 AM ---------- Previous post was at 02:51 AM ----------
avarize said:
Didn't seem to have any luck with that download/odin. Still stuck, Trying a few more things, although I am a bit lost as to what to do from here.
Click to expand...
Click to collapse
Correction : Used that link you had posted, it was still stuck so I loaded up the toolkit and used option 20 for reboot options to force it into default recovery, wiped data & cache from there and let it reboot, it seemed to have hung but waited a few minutes and it came back to life. Back to complete stock here now, hope it works for you.
avarize said:
Didn't seem to have any luck with that download/odin. Still stuck, Trying a few more things, although I am a bit lost as to what to do from here.
---------- Post added at 02:52 AM ---------- Previous post was at 02:51 AM ----------
Correction : Used that link you had posted, it was still stuck so I loaded up the toolkit and used option 20 to force into default recovery, wiped data & cache from there and let it reboot, it seemed to have hung but waited a few minutes and it came back to life. Back to complete stock here now, hope it works for you.
Click to expand...
Click to collapse
When you say toolkit are you talking about the one from the thread labled [SAMSUNG GALAXY S3 QCOM TOOLKIT V2.3] Drivers Backup Root CWM BusyBox + MORE [ATT]? And if so you just opened it and used option 20? nothing else? This sounds great if it works hehe.
rakhov said:
When you say toolkit are you talking about the one from the thread labled [SAMSUNG GALAXY S3 QCOM TOOLKIT V2.3] Drivers Backup Root CWM BusyBox + MORE [ATT]? And if so you just opened it and used option 20? nothing else? This sounds great if it works hehe.
Click to expand...
Click to collapse
Should have explained a bit better. Yes that toolkit
While it was stuck at samsung screen.
1 For AT&T (Obviously)
20 For reboot options
1 For recovery.
Then wipe data/cache
Then wiped cache (no idea why)
then rebooted.
When i did an Odin to stock I also froze on the Samsung logo. I had to boot to recovery and do a factory reset I side recovery to get it to boot. Keep in mind everything will be deleted though
Sent from my SAMSUNG-SGH-I747 using xda premium
That is exelent. I am downloading the toolkit right now and will report back shortly.
Once you got it to boot, did you still have root? I am wondering if you flashing the "stock rom" that I posted, if that had any impact. I have only pushed the root66 file, so I am expecting root when(if XD) I get this thing going again. I appreciate you being more thorough with your instructions, and will report back with my results as soon as I get some
Also, are we loners on this? I am not seeing any other posts about going back to stock/stock rooted from modded roms using odin? I am trying to figure out the best method to go back to stock. I made a nandroid and I am sure that would work, but all of this word about having to flash different kernels and bluetooth/wifi drivers to get stock working properly makes me wonder if just using odin is the easiest method, as it restores everything on the phone (to my knowledge).
crash822 said:
When i did an Odin to stock I also froze on the Samsung logo. I had to boot to recovery and do a factory reset I side recovery to get it to boot. Keep in mind everything will be deleted though
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
That is great, this may sound a little silly, but how do I boot to recovery? Thanks!
UPDATE:Nvm, google hehe. I just did the factory reset...Things are looking good so far, the haptic lights turned on at least...BOOM! We are good gentlemen. It looks like all it took was the recovery wipe. This is great news! I will try to figure out how to mark this as solved, and you crash822, you get a thanks
NP sir. We all have to start somewhere. Luckily for me I was already planning on doing a full wipe so I backed up everything I wanted to keep from my phone onto my computer before using odin.
I seem to be having the same issue. I've downloaded the toolkit as you guys have suggested. are you guys in download mode on the phone while you use this? it seems to want me to be in debugging mode and i can't get to that. I've tried a factory reset with no luck.
It all started here:
http://support.t-mobile.com/thread/44716
I griped on the T-Mobile forums about the struggle I've had in finding a smooth ROM for my T999. And I made an off-handed comment in another thread that got me pointed in the right direction hopefully. I'm looking for other T999 owners that have this problem.
The problem on DMD5 is all related to (apparently) intensive tasks. Playing games, mostly. Temple Run 2 and Fruit Ninja, neither of which are all that intensive, were nigh-on unplayable. Other games like Scramble with Friends would lag and stutter a bit, too. So after a lot of searching, I reverted to a pre-rooted T999UVDLJC with the matching baseband, so that way my phone doesn't try to update itself OTA. And performance is pretty good. But I'd like to think that I'm not alone, and I found I'm not alone in this thread:
http://forum.xda-developers.com/showthread.php?t=2326763&page=33
At the bottom of this page and the top of the next one, I found at least one kindred spirit that has a rev0 phone and has the same issue with DMD5.
NO other ROM has this issue. I've tried all of the official Samsung ROMs and I have tried official CM10.1 nightlies and the official 10.1 stable release and performance is very good on all of them. But it took a huge serious nosedive on T999UVDMD5.
So I'm curious about two things:
Does DMD5 run well on your phone? Particularly with games - that's where it was most notable, but even TWLauncher is laggy for me.
How old is your phone? According to the box for my phone it was built 6/30/2012.
If you are affected, could you help us all out on the T-Mobile support forum, and post a message in my thread at the top of the page? If we can get T-Mo and/or Samsung to look into it maybe we won't get left behind. I plan on using this phone for another year or more and I'd rather get the official updates in the future, too.
Update July 6, 2013: I found out thanks to help from people in this thread that I can run mismatched modem firmware/ROM and with the JLC modem on MD5 ROM, my phone runs fantastic. Or at least it has for about 2 hours - usually issues have shown themselves by now, and since they haven't cropped up I'm calling this resolved.
When you were on MD5, how did you update to it? OTA? Odin? Recovery flashable ROM?
And how much data have you been carrying over? (When did you last wipe data/factory reset, without restoring backups?)
Sent from my SGH-T999 using xda premium
---------- Post added at 01:03 AM ---------- Previous post was at 12:50 AM ----------
Btw, I'm on MD5, completely stock right now. Hw is Rev. 0
I get very little lag, if any, ever. Simple games or even intensive games run very fluidly for me.
For example, I just got Man of Steel when it went on sale and it works almost perfectly. Disney, Gameloft, EA games have all worked just fine.
The only MD5 issues I've seen around here seem to occur when someone is using a mixed build with the MD5 radio. And then its only been reports of heat issues and slight battery issues. Haven't seen much of anything regarding poor performance.
Sent from my SGH-T999 using xda premium
Please do not check "yes this is a question" if it is "info gathering" as all Q's are moved to Q&A. I will edit the title for you.
FNM
DocHoliday77 said:
When you were on MD5, how did you update to it? OTA? Odin? Recovery flashable ROM?
And how much data have you been carrying over? (When did you last wipe data/factory reset, without restoring backups?)
Sent from my SGH-T999 using xda premium
---------- Post added at 01:03 AM ---------- Previous post was at 12:50 AM ----------
Btw, I'm on MD5, completely stock right now. Hw is Rev. 0
I get very little lag, if any, ever. Simple games or even intensive games run very fluidly for me.
For example, I just got Man of Steel when it went on sale and it works almost perfectly. Disney, Gameloft, EA games have all worked just fine.
The only MD5 issues I've seen around here seem to occur when someone is using a mixed build with the MD5 radio. And then its only been reports of heat issues and slight battery issues. Haven't seen much of anything regarding poor performance.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I've tried all of the above. I even let Kies install it once. I've used TriangleAway and Odin to install 4.0.4 and let it do all the OTAs. Iv'e done factory resets and I've told setup not to restore my data to the phone and started from scratch. I used a flashable ZIP with the pre-rooted ROM, and when I did that I also got the DMD5 modem flashable ZIP to go along with it. I've tried not rooted. I've tried custom kernels, and I've tried stock. Odin completely stock and flashable zip totally customized. I've played with custom DMD5-based ROMs with the v6 script and I've tried not. I'm way out of ideas right now.
Sorry, @kennyglass123, I didn't realize I'd checked that box.
Starting to think all of them have "rev 0" for the CPU identifier, so that may not be the way to tell who has what.
Just to be clear, did you ever Factory Reset, then Odin flash MD5 (not mobile odin btw), and factory reset again to ensure internal sd was cleaned out too? If for MD5, you only flashed the Rom and Modem, you would have been on a mixed build. Also, many devs suggest waiting an hour before starting with any testing or reconfiguring. I'm not convinced this is always necessary, but they do usually kno more than me!
Don't get me wrong. I'm not trying to argue against your point, just to make sure not only that you've covered all angles, but that anyone who wants to back up your claim has also done the same.
As for the revision number, it may still be relevant as mine would have been among the first built too. We would need to find at least several others with the same, and different, to know for sure if it matters here.
Its always possible too that you got the unlucky pick of the hardware. (Just as possible though that I got a lucky pick)
Anyway, if you really are having that bad of problems with it, you may want to check if its still under warranty. I don't believe its the norm though.
Sent from my SGH-T999 using xda premium
Yeah I'm pretty sure, but I'm willing to do anything at this point. I'll do it again. I've stashed the Odin tar.md5 file on my backup hard drive, so I'll back up my working config and flash it again. Worst case scenario is that I re-root it, re-install recovery, and then restore my backup. Should take an hour max.
Use the root66 version of the firmware. Its pre rooted and is what I am running right now. Root alone won't have any negative effect, but will allow for much better troubleshooting.
Aside from that, keep it as clean from restored data as possible. Even a single corrupted contact entry can cause services to hang and eat up resources. I wouldn't even flash a recovery until you're ready to restore something.
(I use Mobile Odin Pro and it almost completely replaces the need for cwm or twrp. The only thing it can't do yet is make a nandroid backup.)
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Use the root66 version of the firmware. Its pre rooted and is what I am running right now. Root alone won't have any negative effect, but will allow for much better troubleshooting.
Aside from that, keep it as clean from restored data as possible. Even a single corrupted contact entry can cause services to hang and eat up resources. I wouldn't even flash a recovery until you're ready to restore something.
(I use Mobile Odin Pro and it almost completely replaces the need for cwm or twrp. The only thing it can't do yet is make a nandroid backup.)
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
So the root66 is an Odin image? I assume you're talking about this: http://forum.xda-developers.com/showthread.php?t=1771687
I've got it downloading now. Thanks for all your suggestions. I've not heard of Mobile Odin Pro, is it a custom recovery?
Whoops - found the Mobile Odin thread on XDA and got the lite version and the T999 flashing kernel. I'll give it a go.
Regarding The AOSP MD5 issues: the same thing is happening to me on stock. Have to use LJC or the battery sucks. What are your reboot habits like?
DocHoliday said:
If for MD5, you only flashed the Rom and Modem, you would have been on a mixed build. Also, many devs suggest waiting an hour before starting with any testing or reconfiguring. I'm not convinced this is always necessary, but they do usually kno more than me!
Click to expand...
Click to collapse
There is no possible way it could be necessary. Proof or it's placebo.
DeerSteak said:
So the root66 is an Odin image? I assume you're talking about this: http://forum.xda-developers.com/showthread.php?t=1771687
I've got it downloading now. Thanks for all your suggestions. I've not heard of Mobile Odin Pro, is it a custom recovery?
Click to expand...
Click to collapse
Yes, root66 is basically just 100% stock firmware, only rooted. Itll download as a .7z file. Just extract it and use the .tar.md5. You have the correct thread.
Mobile Odin is one of my all time favorite apps. Its from Chainfire if you are familiar with him. (SuperSU)
Its not a recovery exactly. What it does is reboots using what's called a flash kernel. This allows it to flash firmware like PC Odin, but also can flash roms that are made for recovery flashing. It doesn't replace the stock recovery like cwm/twrp either, so it also won't trip the flash counter. (I know that doesn't really matter with Triangle Away available (also by Chainfire)).
The only two drawbacks, (minor imo) are that it can't create nandroids, and it doesn't flash the FULL firmware (this is by design though).
I wouldn't bother with it right now, but definitely check it out after testing all this. Theres a free, lite, version here on xda. Ill send more info from my computer later.
Sent from my SGH-T999 using xda premium
---------- Post added at 11:51 AM ---------- Previous post was at 11:49 AM ----------
DeerSteak said:
Whoops - found the Mobile Odin thread on XDA and got the lite version and the T999 flashing kernel. I'll give it a go.
Click to expand...
Click to collapse
Don't use Mobile Odin for testin right now. It doesn't flash the full firmware.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Yes, root66 is basically just 100% stock firmware, only rooted. Itll download as a .7z file. Just extract it and use the .tar.md5. You have the correct thread.
Mobile Odin is one of my all time favorite apps. Its from Chainfire if you are familiar with him. (SuperSU)
Its not a recovery exactly. What it does is reboots using what's called a flash kernel. This allows it to flash firmware like PC Odin, but also can flash roms that are made for recovery flashing. It doesn't replace the stock recovery like cwm/twrp either, so it also won't trip the flash counter. (I know that doesn't really matter with Triangle Away available (also by Chainfire)).
The only two drawbacks, (minor imo) are that it can't create nandroids, and it doesn't flash the FULL firmware (this is by design though).
I wouldn't bother with it right now, but definitely check it out after testing all this. Theres a free, lite, version here on xda. Ill send more info from my computer later.
Sent from my SGH-T999 using xda premium
---------- Post added at 11:51 AM ---------- Previous post was at 11:49 AM ----------
Don't use Mobile Odin for testin right now. It doesn't flash the full firmware.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
OK awesome, I will check it out. I think what I'm going to do right now is just reset the flash counter, flash the Odin image, and then factory reset and set it up as a new phone. Does that sound reasonable? If I reboot into CWM after triangle away, it trips the flash counter again, at least that's what it seems to do, so I can't do anything other than reboot to download after Triangle Away.
Aerowinder said:
Regarding The AOSP MD5 issues: the same thing is happening to me on stock. Have to use LJC or the battery sucks. What are your reboot habits like?
There is no possible way it could be necessary. Proof or it's placebo.
Click to expand...
Click to collapse
I don't reboot unless the battery dies, or I was rebooting a lot when I was on MD5 trying to get stuff to work well. Generally I try not to mess with a good thing.
DeerSteak said:
OK awesome, I will check it out. I think what I'm going to do right now is just reset the flash counter, flash the Odin image, and then factory reset and set it up as a new phone. Does that sound reasonable? If I reboot into CWM after triangle away, it trips the flash counter again, at least that's what it seems to do, so I can't do anything other than reboot to download after Triangle Away.
Click to expand...
Click to collapse
That sounds fine. Remember, if you factory reset with stock recovery installed, it will wipe internal sdcard.
As long as you have cwm or twrp, the flash counter will always be at 1. I wouldn't worry about that for now though. It won't affect overall operation.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
That sounds fine. Remember, if you factory reset with stock recovery installed, it will wipe internal sdcard.
As long as you have cwm or twrp, the flash counter will always be at 1. I wouldn't worry about that for now though. It won't affect overall operation.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
OK, I won't mess with it too much then. I've backed up my internal storage already and I've backed up my SMS using SMS Backup and Restore. That thing has been very handy keeping copies of my texts while I screw with this.
Cool, sounds like you're good to go! Good luck! And let us know how things seem to be acting after flashing.
Don't forget to factory reset after flashing md5.
:thumbup:
Sent from my SGH-T999 using xda premium
OK I got as far as the factory reset and then it was time to paint. My daughter's bedroom wasn't going to paint itself. I finally came back to the phone and it was patiently waiting for me to log in. I logged in and installed just a couple apps while I ate lunch, and then it sat until we were done painting and cleaning up. Logged into Facebook and Twitter, set up Google Now and updated Samsung apps. Once all that was done, I fired up Temple Run 2 and it was OK at first, but within 3-4 minutes it was choppy and laggy again. The phone never got warm to the touch. It just ran poorly. I exited out and killed all apps with the built-in task manager, and went back to the game. Not really any better. It's just super choppy. I even turned down all the graphics options in the settings for the game and that made zero difference.
Eventually I gave up. Restored my 4.1.1 backup, fired up some stuff, performance was great. It's just the combination of my phone and that software. No idea what it is at this point. I do appreciate all the assistance you guys have lent me.
Right now I'm on T-mo and was waiting out the 60 days before I ported my wife's number in to my account. Now that that's over, I'll eventually port in her number. She's extremely happy with her iPhone 4s and insists she's not interested in an iPhone 5, so what I'll probably do is use the ability to get new hardware as an excuse to get a Galaxy S4. WHen I first came to T-mo I just got a SIM and bought the phone used - found out later on that I should have just bought a phone through T-mo because I can't get a new phone on a payment plan for a year unless it's as part of a new line. She'll be a new line, so I'll get a phone.
This hasn't put me off on Samsung or even on the GS3 - it's just my phone has a weird issue of some sort. And the people here have been super awesome. Thanks tons for all your advice. In the meantime I'll run JLC and leave well enough alone.
DeerSteak said:
OK I got as far as the factory reset and then it was time to paint. My daughter's bedroom wasn't going to paint itself. I finally came back to the phone and it was patiently waiting for me to log in. I logged in and installed just a couple apps while I ate lunch, and then it sat until we were done painting and cleaning up. Logged into Facebook and Twitter, set up Google Now and updated Samsung apps. Once all that was done, I fired up Temple Run 2 and it was OK at first, but within 3-4 minutes it was choppy and laggy again. The phone never got warm to the touch. It just ran poorly. I exited out and killed all apps with the built-in task manager, and went back to the game. Not really any better. It's just super choppy. I even turned down all the graphics options in the settings for the game and that made zero difference.
Eventually I gave up. Restored my 4.1.1 backup, fired up some stuff, performance was great. It's just the combination of my phone and that software. No idea what it is at this point. I do appreciate all the assistance you guys have lent me.
Right now I'm on T-mo and was waiting out the 60 days before I ported my wife's number in to my account. Now that that's over, I'll eventually port in her number. She's extremely happy with her iPhone 4s and insists she's not interested in an iPhone 5, so what I'll probably do is use the ability to get new hardware as an excuse to get a Galaxy S4. WHen I first came to T-mo I just got a SIM and bought the phone used - found out later on that I should have just bought a phone through T-mo because I can't get a new phone on a payment plan for a year unless it's as part of a new line. She'll be a new line, so I'll get a phone.
This hasn't put me off on Samsung or even on the GS3 - it's just my phone has a weird issue of some sort. And the people here have been super awesome. Thanks tons for all your advice. In the meantime I'll run JLC and leave well enough alone.
Click to expand...
Click to collapse
Before you give up, try debloating your install. I will PM you a link to the one I made. Backup first.
Aerowinder said:
Before you give up, try debloating your install. I will PM you a link to the one I made. Backup first.
Click to expand...
Click to collapse
OK i'll give it a go. Thanks.
Should I re-flash the MD5 modem?
I'd flash the LJC firmware, Third firmware link in my sig. LJC link is buried in the OP.
Aerowinder said:
I'd flash the LJC firmware, Third firmware link in my sig. LJC link is buried in the OP.
Click to expand...
Click to collapse
OK I see it there. So I should use the LJC modem/firmware with the DMD5 debloat ROM you're going to PM the link for to me? Will they work if they're mismatched? I assumed (not that I'd bothered asking before) that they'd all have to be the same.
--- Mods, didn't want to post in Android Development and clutter that section, thought General would be a bit better. My deepest apologies if I'm yet in the wrong section, just move it and tell me. Thank you. ---
Alright guys, tried to do some searching on this topic - no help found. So i'm resorting to what I hate to do, flooding the forums with more topics. Little bit of background to help troubleshoot, I've been rooting and rom-ing for about 4 years now with all Verizon Samsung phones (locked bootloaders and all that fun stuff) but just switched to sprint recently and having a few issues with roms.
On to my issue...
My phone has been experiencing a bunch of lag lately. So bad where the phone locks up for about 5 to 7 seconds about 3-4 times an hour and it is getting annoying as it's locking it at some crucial points. So, I have TWRP on there, rooted on stock 4.4 and tried to flash CM12 nightlies for this phone (the Sprint version). TWRP refused to install it, saying that the phone itself was the trlteTMO version and couldn't flash the trlteSPR roms. I flashed the TMO CM12 nightly and it flashed perfectly fine, but my service didn't work. I believe I got 3G/LTE and calling (unsure, can't confirm.) But no texts went through. But what the great part was, is that it did not stutter and Lollipop was absolutely f-in' gorgeous. So i'm assuming the phone accepted the software, but the radios weren't correct. I loved CM12 so much, but I use XPOSED for a few things. (Basically just Keepchat), So i'm okay with going to CM12 if someone can get my Sprint phone, which i got through Sprint, to work with Sprint roms. I'm at a brick wall.
Mind you that I have access to a windows computer, but it's junk and would rather flash using ODIN PRO on my phone, or just using my recovery. I use a Macbook Pro as my daily, but I can't get heimdall to work as i once did on my S3. I can't even find support or any downloads for it. So, i'm pretty much back to noob status and just need some good guidance. Thank you for reading, and help me flash something new!
Did you use the correct recovery for spr? Is only thing I can think of.... Maybe you flashed the tmo recovery
spleef said:
Did you use the correct recovery for spr? Is only thing I can think of.... Maybe you flashed the tmo recovery
Click to expand...
Click to collapse
Definitely checking that. Sounds like it could be a very good reason for it to reject the tar.
Branski81 said:
Definitely checking that. Sounds like it could be a very good reason for it to reject the tar.
Click to expand...
Click to collapse
Using a .tar file in recovery could be your 1st problem....
Sent from my SM-N910P using Tapatalk
I agree with spleef. There's no other reason I can think of that would cause TWRP recovery to not install a sprint rom and give you that error message. You should really double check the tar files bwhen downloading them and definitely before flashing them with odin. Another thing, you are very brave for knowlingly flashing a T-Mobile rom on your Sprint phone. Seriously, you might want to Odin back to the stock. Sprint NK2 rom .tar and startb over fresh. It would be in your best interest at this point.
BigJPNut said:
Using a .tar file in recovery could be your 1st problem....
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Excuse me, you're right. The recovery file was not tar. You're correct though, that does seem as it would just a littttttle bit of an issue..
---------- Post added at 12:15 AM ---------- Previous post was at 12:11 AM ----------
tx_dbs_tx said:
I agree with spleef. There's no other reason I can think of that would cause TWRP recovery to not install a sprint rom and give you that error message. You should really double check the tar files bwhen downloading them and definitely before flashing them with odin. Another thing, you are very brave for knowlingly flashing a T-Mobile rom on your Sprint phone. Seriously, you might want to Odin back to the stock. Sprint NK2 rom .tar and startb over fresh. It would be in your best interest at this point.
Click to expand...
Click to collapse
I cannot fully confirm that it was the wrong TWRP as the only recoveries I had on my computer and phone storage were sprint versions.
I did however reinstall the sprint recovery again after having to flash back to stock due to a random bootloop issue. So after reflashing 4.4 stock, reinstalling the recovery and restoring to a previous backup, I am now clean flashed on 5.0.2 all cellular features working on CM12 Official.
Mods, if you could please close or delete this thread, that would be appreciated.
Thank you @spleef, I'm sure you were correct anyways.
/end
[email protected]
I feel your pian. Same somewhat similar happend to me on the Snapdragon S5.
I did a factory reset. Hook up to Kies3. Upgraded to NK2. Did a little Coding.Wiated for Lolipop to role out Official. Rooted debloated N knox free. Found in General tips and tricks.
All OS is running Super Fast-
Started out with having problems with freedompop, it suddenly started using up all my data for texts and calls, even though I'm on unlimited calls and texts. Tried to root the phone and bricked it.
Then I managed to unbrick with Odin reloading TWRP recovery.
Have now tried 3 or 4 ROMs and they all boot loop. I also upgraded the bootloader because I read you have to have a bootloader that can handle later android like 4.4 or 5.1. Now someone told me they never bothered with that and had no problem, so maybe the new bootloader is causing my boot loop problem? I've tried 2 bootloaders that can handle 4.4 and still get boot loop.
At this stage I'd be happy just to go back to 4.3 stock if it would get my phone working again.
I did notice that it didn't seem to be able to find any checksums when it was flashing, and just bypassed them. could that be it?
padosaurus said:
Started out with having problems with freedompop, it suddenly started using up all my data for texts and calls, even though I'm on unlimited calls and texts. Tried to root the phone and bricked it.
Then I managed to unbrick with Odin reloading TWRP recovery.
Have now tried 3 or 4 ROMs and they all boot loop. I also upgraded the bootloader because I read you have to have a bootloader that can handle later android like 4.4 or 5.1. Now someone told me they never bothered with that and had no problem, so maybe the new bootloader is causing my boot loop problem? I've tried 2 bootloaders that can handle 4.4 and still get boot loop.
At this stage I'd be happy just to go back to 4.3 stock if it would get my phone working again.
Click to expand...
Click to collapse
Downgrading boootloader will give u a nice shiny paperweight! What device you on reg s3 triband, bootloder?
Sent from my SPH-L710T using XDA Free mobile app
padosaurus said:
I did notice that it didn't seem to be able to find any checksums when it was flashing, and just bypassed them. could that be it?
Click to expand...
Click to collapse
Unless you downloaded an md5 file separately, then it will skip the checksum, because you didn't provide one. No big deal, as long as you checked it yourself.
Stop changing bootloaders or you will brick. Nj2 is fine for all current roms. By boot loop you mean it stayed in boot animation? Because lollipop roms do that. Sometimes if it stays for a loooong time, I boot to recovery then straight back to system and it starts optimizing right away. But you may just have to be patient.
(I can't seem to log back on with my other account and it made me start a new account using google....)
I've tried these roms:
aicp_d2spr_lp-10.0-NIGHTLY-20151210.zip
ND8_STOCK_ODEX_ROOTED.zip
and these bootloaders:
L710-ND8-Bootloader.tar
KT747-TW-KK-4.4-SPR-05-13-2014.zip
Is this the info you asked for? I don't know what reg s3 triband is.
I've gone back and forth between the above bootloaders but I think they are the same level bootloaders and the phone hasn't bricked so hopefully that's not the problem. someone else said I needn't have changed the original bootloader to try higher roms like 4.4 or 5.1, but I don't know.
hilla_killa said:
Downgrading boootloader will give u a nice shiny paperweight! What device you on reg s3 triband, bootloder?
Sent from my SPH-L710T using XDA Free mobile app
Click to expand...
Click to collapse
---------- Post added at 04:42 AM ---------- Previous post was at 04:34 AM ----------
madbat99 said:
Unless you downloaded an md5 file separately, then it will skip the checksum, because you didn't provide one. No big deal, as long as you checked it yourself.
Stop changing bootloaders or you will brick. Nj2 is fine for all current roms. By boot loop you mean it stayed in boot animation? Because lollipop roms do that. Sometimes if it stays for a loooong time, I boot to recovery then straight back to system and it starts optimizing right away. But you may just have to be patient.
Click to expand...
Click to collapse
KT747-TW-KK-4.4-SPR-05-13-2014.zip is the bootloader that is currently loaded, should I just leave that one?
the rom that's loaded now is supposed to be stock 4.4. It does the fancy sprint splash screen, then the word SAMSUNG appears and just stays there forever, with a blue shadow fading in and out.
Maybe I should try a different ROM? The other one I tried is aicp_d2spr_lp-10.0-NIGHTLY-20151210.zip, that also boot loops with a spinning pattern with icy android robot.
---------- Post added at 05:39 AM ---------- Previous post was at 04:42 AM ----------
madbat99 said:
Unless you downloaded an md5 file separately, then it will skip the checksum, because you didn't provide one. No big deal, as long as you checked it yourself.
Stop changing bootloaders or you will brick. Nj2 is fine for all current roms. By boot loop you mean it stayed in boot animation? Because lollipop roms do that. Sometimes if it stays for a loooong time, I boot to recovery then straight back to system and it starts optimizing right away. But you may just have to be patient.
Click to expand...
Click to collapse
So I shoulda/coulda checked the checksum myself?
paddosaurus said:
(I can't seem to log back on with my other account and it made me start a new account using google....)
I've tried these roms:
aicp_d2spr_lp-10.0-NIGHTLY-20151210.zip
ND8_STOCK_ODEX_ROOTED.zip
and these bootloaders:
L710-ND8-Bootloader.tar
KT747-TW-KK-4.4-SPR-05-13-2014.zip
Is this the info you asked for? I don't know what reg s3 triband is.
I've gone back and forth between the above bootloaders but I think they are the same level bootloaders and the phone hasn't bricked so hopefully that's not the problem. someone else said I needn't have changed the original bootloader to try higher roms like 4.4 or 5.1, but I don't know.
---------- Post added at 04:42 AM ---------- Previous post was at 04:34 AM ----------
KT747-TW-KK-4.4-SPR-05-13-2014.zip is the bootloader that is currently loaded, should I just leave that one?
the rom that's loaded now is supposed to be stock 4.4. It does the fancy sprint splash screen, then the word SAMSUNG appears and just stays there forever, with a blue shadow fading in and out.
Maybe I should try a different ROM? The other one I tried is aicp_d2spr_lp-10.0-NIGHTLY-20151210.zip, that also boot loops with a spinning pattern with icy android robot.
---------- Post added at 05:39 AM ---------- Previous post was at 04:42 AM ----------
So I shoulda/coulda checked the checksum myself?
Click to expand...
Click to collapse
Well kt747 is not a bootloader, its a kernel. And it's a kernel for stock 4.4.2. Stop flashing random things or you will destroy your phone. The difference between regular and triband s3 is big. Regular is sph-l710, the triband is sph-L710t. That little t makes all the difference. You need to check your model number.
Use odin to flash nj2 stock .tar and start fresh.
Get it here
You will also need the freedompop messaging app for your phone to work.
Got it back again with the nj2 stock.tar! Many thanks
Can't get freedompop messager because google play thinks it's already installed.
Mine says SPH -L710 on label behind battery, so I guess it's not triband?
CAn I now root and install a custom rom eg with android 5.1 and is it worth the trouble?
madbat99 said:
Well kt747 is not a bootloader, its a kernel. And it's a kernel for stock 4.4.2. Stop flashing random things or you will destroy your phone. The difference between regular and triband s3 is big. Regular is sph-l710, the triband is sph-L710t. That little t makes all the difference. You need to check your model number.
Use odin to flash nj2 stock .tar and start fresh.
Get it here
You will also need the freedompop messaging app for your phone to work.
Click to expand...
Click to collapse
paddosaurus said:
Got it back again with the nj2 stock.tar! Many thanks
Can't get freedompop messager because google play thinks it's already installed.
Mine says SPH -L710 on label behind battery, so I guess it's not triband?
CAn I now root and install a custom rom eg with android 5.1 and is it worth the trouble?
Click to expand...
Click to collapse
Google freedompop apk itll take you where u need to be! Some people have trouble dling it from google play check it out! Valuable info for you!
Sent from my SPH-L710T using XDA Free mobile app
paddosaurus said:
Got it back again with the nj2 stock.tar! Many thanks
Can't get freedompop messager because google play thinks it's already installed.
Mine says SPH -L710 on label behind battery, so I guess it's not triband?
CAn I now root and install a custom rom eg with android 5.1 and is it worth the trouble?
Click to expand...
Click to collapse
It is not a triband. Congrats on fixing it. Yes you can now easily root, using odin to flash the most recent twrp tar file for d2spr (our s3's codename).
5.1.1 roms were (are) worth it for me, but everyone's taste is different. I'm actually running aicp 11 (marshmallow 6.0.1) right now!