I am using unlocked i927r in Indonesia. No issues when using GB either ICS, even it's stock or custom. Having a service issue when using developed JB. Been trying different developed ROMs but no luck. Back to ICS and have no issue.
I did wiping data, cache, dalvik, format system. Is there anything I missed?
hypehnx said:
I am using unlocked i927r in Indonesia. No issues when using GB either ICS, even it's stock or custom. Having a service issue when using developed JB. Been trying different developed ROMs but no luck. Back to ICS and have no issue.
I did wiping data, cache, dalvik, format system. Is there anything I missed?
Click to expand...
Click to collapse
Does it take away your baseband if so I'm having the same issue
Hypothesis: you have either UCKI3 or UCLG9 baseband which may not like JB.
What is your baseband, under "About phone"?
roothorick said:
Hypothesis: you have either UCKI3 or UCLG9 baseband which may not like JB.
What is your baseband, under "About phone"?
Click to expand...
Click to collapse
A lot of us with no service issues don't have a baseband version, its clearly noted as "UNKNOWN"
roothorick said:
Hypothesis: you have either UCKI3 or UCLG9 baseband which may not like JB.
What is your baseband, under "About phone"?
Click to expand...
Click to collapse
i927RUXKJ5
try installing literom .... select the latest modem during installation (it is selected by default) then install JB
I have the same problem (unknown baseband/IMEI on JB, no problems on GB or ICS). Changing the modem/baseband via LiteROM did not fix it. Currently on UCLH2 on ICS, which is not what I had before, and it says "unknown" in JB. I tried most of the others as well. The Rogers one seems to prevent my AT&T phone from booting.
How many of these "baseband unknown" threads do we really need?
Sent from my SGH-I927 using xda premium
People will probably keep posting them until it gets solved and stickied, don't you think? It's apparently not uncommon, and people are phrasing it in different ways in their titles, i.e. "Unable to use custom Roms" doesn't sound like the same issue, but it is.
All JB roms require you to update your baseband to the latest att ota regardless of your carrier. ULCJ3! There is a guide in the dev section I posted to get you there. Once your updated and have cwmr recovery back on the device, then and only then your service will work as long as you follow the instructions posted for that Rom!
Sent from my SGH-I927 using Tapatalk 2
Lysander said:
People will probably keep posting them until it gets solved and stickied, don't you think? It's apparently not uncommon, and people are phrasing it in different ways in their titles, i.e. "Unable to use custom Roms" doesn't sound like the same issue, but it is.
Click to expand...
Click to collapse
Doesn't matter. One thread will suffice. People see there is already a thread on the subject, they need to post there instead of opening a new thread. Reading is fundamental. :thumbup:
Sent from my SGH-I927 using xda premium
dbrannon79 said:
All JB roms require you to update your baseband to the latest att ota regardless of your carrier. ULCJ3! There is a guide in the dev section I posted to get you there. Once your updated and have cwmr recovery back on the device, then and only then your service will work as long as you follow the instructions posted for that Rom!
Sent from my SGH-I927 using Tapatalk 2
Click to expand...
Click to collapse
I'm using UCLH2 baseband with CM10.1. UCKI2 may not be compatible, but UCLG9 should be and UCLH2 most definitely is.
dman3285 said:
Doesn't matter. One thread will suffice. People see there is already a thread on the subject, they need to post there instead of opening a new thread. Reading is fundamental. :thumbup:
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
My point was that they may not realize there is already a thread on the subject.
Related
With all of the forums merged it was so hard to get a read on the real amount of IMEI Problems by AT&T Users.
So a quick poll / count. Who has lost their IMEI on AT&T.
crawlgsx said:
With all of the forums merged it was so hard to get a read on the real amount of IMEI Problems by AT&T Users.
So a quick poll / count. Who has lost their IMEI on AT&T.
Click to expand...
Click to collapse
I lost my IMEI on my first Sgs3, went flash happy (only AT&T ROMs) but still had data and cell. Not sure where I lost it, but I noticed when I was flashing back to rooted stock from early CM10 preview (official) is when I noticed.
So far with my new phone, I've done the same and still have it. I'm now running Aokp jellybean.
I've had no problems as of today but the fear of losing my imei has definitely caused me to not experiment as much as I would like to! I've rooted, installed CWM-Touch, flashed Ktoonsez Kernel, and flashed back to the AT&T Kernel. I'm honestly afraid to try CM as it seems that ALOT of the people who have lost their IMEI had flashed CM10 or CM9. I bought a Galaxy Tab 2 7" a few months back and it's become my tinker toy to flash ROM's and mess with. I don't want to screw up my $500 Galaxy S3, I like it too much!
I voted as flashed a few, but really it is probably closer to many. Only AOSP based ROMs though. CM9, CM10, and AOKP plus updates for each. Also both Faux and Ktoonsez kernels at various times. IMEI still present.
I do make sure that I flash the EXACT same way every time though since it has worked so far. Only thing I have changed now is moving from latest non-touch CWM (installed through ROM Manager) to latest TWRP (through Goo Manager).
If I end up losing my IMEI without adding variables to my flash process, I will start to believe it is a random occurrence. Until then I have to think partial user error coupled with a bad update script or recovery.
I ALWAYS download the file straight to my phone via WiFi.
Reboot into recovery. Wipe>Factory reset.
Flash ROM.
The last couple days since moving to TWRP I have felt more ballsy and did things a bit differently.
For the first time, I also wiped cache and Dalvik before flashing JB AOKP last night
Still no issues.
Today I decided to flash the ktoonsez JB kernel. I usually only download via WiFi at home (just to keep minimal variables in flashes) but today I did it at work via WiFi. Still have IMEI.
I have NEVER done a Format System so not sure if that might break something.
My process has been if it isn't breaking, try to keep the process as consistent as possible. If something does go wrong, I can say what I did differently. I also haven't had any trouble with the ROMs I flashed despite only doing factory reset then flash.
How do I know if I have any issues with this. What do I look for. I found out and mines good.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
spacecasespiff said:
How do I know if I have any issues with this. What do I look for. I found out and mines good.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I know you found out, but when it happens you will know.
In some cases it seems as though you only get Edge at your maximum speed, in others your mobile data completely died. Generally speaking, there was a lot of confusion and some issues with clarity regarding the issue.
It's possible that there are several different (but vaguely related) issues going around, now that we have our own carrier based forums that should actually help clear it up in my opinion.
Hopefully we will all reach a general consensus on the acceptable recovery (my vote is TWRP!) and method of flashing. The only thing I've personally considered is that it might be an issue with the files transferring via MTP (only because I've never used a phone with MTP instead of mass storage).
I don't think people should be THAT afraid to flash though. If your flash counter is at 0, Samsung should do a warranty swap for you. In addition, it seems like 2 in 25 people (read: NOT FLASHES, but people.) seem to get the issue based only off of the very small number of people in this poll so far.
The reason the issue is so feared is because those that do get it will inevitably be far more vocal than those that don't as they try to find a solution and vent their frustration. Most of the people in the major thread about it didn't have the issue, but were afraid they might lose their IMEI.
I flashed the stock rooted tar that doesn't trip your counter, then injected CWM with dd. I've flashed everything with CWM since then, CM10 included (once) and I still have my IMEI. I'm running AOKP JB now.
I'm about to root and cwm what's your guys input on the best ways
Sent from my SAMSUNG-SGH-I747 using xda premium
yokken said:
I flashed the stock rooted tar that doesn't trip your counter, then injected CWM with dd. I've flashed everything with CWM since then, CM10 included (once) and I still have my IMEI. I'm running AOKP JB now.
Click to expand...
Click to collapse
What's this dd you speak of sir
Sent from my SAMSUNG-SGH-I747 using xda premium
As always, check your apn before freaking out! It may have gotten deleted while flashing a rom. It happened to me
Yes, I freaked out.
Sent from my SGH-I747M using xda premium
tyshemi said:
What's this dd you speak of sir
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
If you read the thread I mentioned (How to root without tripping flash counter) it mentions "injecting" CWM using a tool called dd.
yokken said:
If you read the thread I mentioned (How to root without tripping flash counter) it mentions "injecting" CWM using a tool called dd.
Click to expand...
Click to collapse
Yea I have read that many times there guy thanks for input just solidifying it all
Sent from my SAMSUNG-SGH-I747 using xda premium
ppl who scared to flash
Go for nontrip flash root + CWM topic - worked for so many people without issues.
The only way to screw up IMEI with these ROMs is via Odin, I think. Odin is a scary tool without much documentation, and in past used to be buggy.
Once you get CWM - do not use Odin.
bravomail said:
Go for nontrip flash root + CWM topic - worked for so many people without issues.
The only way to screw up IMEI with these ROMs is via Odin, I think. Odin is a scary tool without much documentation, and in past used to be buggy.
Once you get CWM - do not use Odin.
Click to expand...
Click to collapse
I have to use Odin for root initially don't I ? Then use it for cwm or u recommend Rom manager ? Im just wanting stock Rom like yours for now
Sent from my SAMSUNG-SGH-I747 using xda premium
bravomail said:
Go for nontrip flash root + CWM topic - worked for so many people without issues.
The only way to screw up IMEI with these ROMs is via Odin, I think. Odin is a scary tool without much documentation, and in past used to be buggy.
Once you get CWM - do not use Odin.
Click to expand...
Click to collapse
Odin is a scary tool indeed. Someone in the IMEI thread said if I was feeling feisty to flash stock nonrooted OTA ROM via Odin straight from JB AOKP. IMEI is still intact after all that I have done. :laugh:
EDIT: Also, anyone who reads this. Try out TWRP. We need more people flashing with TWRP, if an IMEI goes missing while using it we can rule out CWM being the problem as some have suggested.
codycorexxx said:
Odin is a scary tool indeed. Someone in the IMEI thread said if I was feeling feisty to flash stock nonrooted OTA ROM via Odin straight from JB AOKP. IMEI is still intact after all that I have done. :laugh:
EDIT: Also, anyone who reads this. Try out TWRP. We need more people flashing with TWRP, if an IMEI goes missing while using it we can rule out CWM being the problem as some have suggested.
Click to expand...
Click to collapse
Ive done this, not once but twice. Once coming from Aokp and once from cm10. Imei still intact :good:
Lmao, funny thing is i was deathly scared of the imei issue and very well versed on it, and i never knew it was "dangerous" till i read your post just now.
Can I let the Tmobile Update download and flash if I am rooted on the stock ROM and have Clockwork recovery? I would use ota root keeper to disable root also before the update.
Sent from my SGH-T999 using Tapatalk 2
When it is rooted even if you try to use the OTA update it won't let you, while rooted, you could alternatively flash the update via ODIN w/ root support. Or try some of the sweet ROMs available , the reason I switched to a custom ROM because I was going to have to erase my phone anyway if I wanted to update, so I thought why not just try a custom ROM?
I use LiquidSmoothRC7, but if you want a more stock feel with touchwiz you can try Wicked, Wicked stays true to the "official stock ROMs" and just adds roots and tweaks the ROM to make it as stable as possible
If you are rooted, with a custom recovery, there is absolutely no reason for you to be playing around with Odin or OTAs... your updates are available in the development section
cobraboy85 said:
If you are rooted, with a custom recovery, there is absolutely no reason for you to be playing around with Odin or OTAs... your updates are available in the development section
Click to expand...
Click to collapse
OR you could listen to this dude
cobraboy85 said:
If you are rooted, with a custom recovery, there is absolutely no reason for you to be playing around with Odin or OTAs... your updates are available in the development section
Click to expand...
Click to collapse
Actually there is. There are 10 partitions rewritten with the Odin and OTA update. Only 5 get rewritten if you flash via custom recovery, so you don't get the full update.
Sent from my SGH-T999 using Tapatalk 2
zul8er said:
Can I let the Tmobile Update download and flash if I am rooted on the stock ROM and have Clockwork recovery? I would use ota root keeper to disable root also before the update.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
go to doc's thread, flash his firmware update, reboot, then flash whatever JB ROM you desire. there is absolutely no need to ODIN your phone with the OTA fw, resetting your device completely. you just need to make sure you flash the latest firmware first before you flash a ROM that is based off the latest OTA
cobraboy85 said:
go to doc's thread, flash his firmware update, reboot, then flash whatever JB ROM you desire. there is absolutely no need to ODIN your phone with the OTA fw, resetting your device completely. you just need to make sure you flash the latest firmware first before you flash a ROM that is based off the latest OTA
Click to expand...
Click to collapse
I stayed on 4.0.4 with the base of UVLH2 and just clean installed JB roms so should I update the base? Or is it already updated?
Sent from my SGH-T999 using xda app-developers app
Towle said:
Actually there is. There are 10 partitions rewritten with the Odin and OTA update. Only 5 get rewritten if you flash via custom recovery, so you don't get the full update.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Some of those 10 partitions that are getting rewritten are... for one, your recovery... so that makes 9 actually...
My point is, and I'm not trying to be argumentative in any way, merely objective, is that unless it is reformatting the ext4 partition to new file structure (for example) there should be no need to do this. I suppose I would ask somebody to define in depth "rewritten" and how exactly this is being done and why. Every single update we have had since the release of this device I have not once updated my own device with odin merely to put it back to stock. And I have run into zero issues. Seems like a waste of time to me unless there is something highly critical being restructured entirely. In the end, its all the same disk, and disk size for any given partition.
---------- Post added at 05:51 AM ---------- Previous post was at 05:47 AM ----------
neim81094 said:
I stayed on 4.0.4 with the base of UVLH2 and just clean installed JB roms so should I update the base? Or is it already updated?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
If you are on LH2, with that same baseband, I would go ahead and update your baseband via docs packaged update in his thread, and just reboot, then move on to the jelly bean updates. Do a factory reset through recovery before you flash the JB ROM tho since you are coming from a completely different version of android.
zul8er said:
Can I let the Tmobile Update download and flash if I am rooted on the stock ROM and have Clockwork recovery? I would use ota root keeper to disable root also before the update.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
If you want to avoid all the weird miscellaneous problems listed in the Q&A forum, update using Odin and the rooted rom in Docs' thread. If you choose not to use Odin do not be surprised if odd things happen.
Just stating my experience, I was rooted stock ics and ran the ota update. I was able to update, keep root and ran stock jelly bean without any problems at all.
Now I am running frosty jelly and still no problems at all. I am not saying for you to do it (dont want anyone blaming me) just stating that it can be done. Do whats most comfortable for you.
Sent from my SGH-T999 using xda app-developers app
jcbofkc said:
If you want to avoid all the weird miscellaneous problems listed in the Q&A forum, update using Odin and the rooted rom in Docs' thread. If you choose not to use Odin do not be surprised if odd things happen.
Click to expand...
Click to collapse
Again looking for some technical clarity here. Haven't had a single issue myself. With anything. And I have not factory odined my device once since I got it. It is not critical to do this, otherwise I would be suffering from "weird miscellaneous problems"
Hopin doc can jump in here and set me straight if I am wrong, but it seems to me you will be fine just updating your radios and then moving to the latest build (4.1.1) as long as you clear data before flashing your ROM of choice
cobraboy85 said:
Again looking for some technical clarity here. Haven't had a single issue myself. With anything. And I have not factory odined my device once since I got it. It is not critical to do this, otherwise I would be suffering from "weird miscellaneous problems"
Hopin doc can jump in here and set me straight if I am wrong, but it seems to me you will be fine just updating your radios and then moving to the latest build (4.1.1) as long as you clear data before flashing your ROM of choice
Click to expand...
Click to collapse
You could very well be correct. Not trying to debate you.
but....I am seeing thread after thread of issues. Based on experience I suggest using the full proof method. I have updated many phones using many different methods and never have problems, but apparently many have had issues.
I also hope Doc chimes in on this thread.
jcbofkc said:
You could very well be correct. Not trying to debate you.
but....I am seeing thread after thread of issues. Based on experience I suggest using the full proof method. I have updated many phones using many different methods and never have problems, but apparently many have had issues.
I also hope Doc chimes in on this thread.
Click to expand...
Click to collapse
Totally dig it. And yeah, just want to know what exactly is being done differently in odin
cobraboy85 said:
Totally dig it. And yeah, just want to know what exactly is being done differently in odin
Click to expand...
Click to collapse
If I understand the process correctly
ODIN flashes the entire phone OS like the kernel, Rom, baseband, etc
Using recovery to flash only updates the Rom,recovery,boot,kernel
Sent from my SGH-T999
neim81094 said:
If I understand the process correctly
ODIN flashes the entire phone OS like the kernel, Rom, baseband, etc
Using recovery to flash only updates the Rom,recovery,boot,kernel
Sent from my SGH-T999
Click to expand...
Click to collapse
Sorry, I will clarify, I am curious to know why Odin is such a critical issue. I know how it works as far as it being a flashing tool
I am not sure maybe it's just preference and how much you want to use your computer and what how much you want to download etc
Sent from my SGH-T999
neim81094 said:
I am not sure maybe it's just preference and how much you want to use your computer and what how much you want to download etc
Sent from my SGH-T999
Click to expand...
Click to collapse
The file used to flash with Odin is much larger because it is a complete rom. The OTA is a patch that attempts to patch and modify existing files.
I basically said that on the last post not the one you quoted
Sent from my SGH-T999
Finally got the time to Odin Route66 Jelly bean.
Sent from my SGH-T999 using Tapatalk 2
Everything good?
Development seems fragmented between all the different carriers.. even with a deodexed stock rooted rom are things "designed" for other carriers not compatible with my Sprint device?
Is it a matter of n7100 vs n7105? Or gsm/lte?
Sent from my SPH-L900 using xda app-developers app
You will probably brick your device flashing another carrier ROM. I say probably as I know of no one willing to experiment on our rather expensive device.
Sent from my SPH-L900 using Tapatalk 2
bleaktrotter said:
Development seems fragmented between all the different carriers.. even with a deodexed stock rooted rom are things "designed" for other carriers not compatible with my Sprint device?
Is it a matter of n7100 vs n7105? Or gsm/lte?
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
There are some "ports" that have been done between carriers. Know your carrier and flash only roms designed for or ported to that carrier.
All will run on sprint's variant. The radios may be compatible with the ROM with a few mods here and there. You can flash other stock ROMs. Just flash sprint's kernel with another carriers. You'll see a mostly functioning ROM. Only issues are radio related.
Sent from my SCH-R950 using XDA
na7q said:
All will run on sprint's variant. The radios may be compatible with the ROM with a few mods here and there. You can flash other stock ROMs. Just flash sprint's kernel with another carriers. You'll see a mostly functioning ROM. Only issues are radio related.
Sent from my SCH-R950 using XDA
Click to expand...
Click to collapse
I'd proceed here with caution. I've heard of borked boot/kernel image or worse hboot damage requiring either replacement or j tag service. YMMV.
Sent from my SPH-L900 using xda app-developers app
Thanks for the info. It sounds like it's only a matter of radio compatibility when flashing ROMs. If I flash stock sprint radios and a kernel made specifically for the L900 (stock or otherwise) I should be okay based on what I see here.
So it's only ROMs that are in question here? If there's a .zip mod for status bar, camera, gallery, etc, I shouldn't need to worry about what model it's for? Including n7105 international variant .zips -- I see no reason why that shouldn't work. These are all essentially the same device sans connectivity.
I don't mind flashing sketchy things, been doing that for years and haven't had a hard brick yet -- it's actually hard to do. I just want to know what the facts are about what is known to work or not work.
Sent from my SPH-L900 using xda app-developers app
Delete.
I wish you the best in your endeavors.
Sent from my SPH-L900 using xda app-developers app
na7q said:
All will run on sprint's variant. The radios may be compatible with the ROM with a few mods here and there. You can flash other stock ROMs. Just flash sprint's kernel with another carriers. You'll see a mostly functioning ROM. Only issues are radio related.
Sent from my SCH-R950 using XDA
Click to expand...
Click to collapse
NOT TRUE AT ALL...........if you flash an international variant rom, while you may get it to boot (doubtful), you will not have service and your IMEI/Baseband will be gone d/t the fact that the partitions are slightly different between the variants. the only fix for this is flashing a stock tar that will re-write your partitions and restore to stock. and it simply isnt as simple as just changing the partitions and kernel either.
so no, DO NOT FLASH other carrier variant roms to the Sprint variant
I flashed a att rom and a tmo theme to mine with success.and by success I mean didnt brick. Now as far as booting thats a diff story. The tmo theme booted with problems and the att rom just bootlooped. But as far as I know the partitions layout is the same(not counting the intl'. I havent looked yet) so i think ur safe to experiment with the average rom. I would check to make sure theres no radio or bootloader and you should be fine.
t3project said:
NOT TRUE AT ALL...........if you flash an international variant rom, while you may get it to boot (doubtful), you will not have service and your IMEI/Baseband will be gone d/t the fact that the partitions are slightly different between the variants. the only fix for this is flashing a stock tar that will re-write your partitions and restore to stock. and it simply isnt as simple as just changing the partitions and kernel either.
so no, DO NOT FLASH other carrier variant roms to the Sprint variant
Click to expand...
Click to collapse
Very true. How else was I to run every variant? Especially your sprint stock on mine? Which is us cellular. If you use the right kernel nothing will brick your phones. discussion over
Sent from my SCH-R950 using XDA
na7q said:
Very true. How else was I to run every variant? Especially your sprint stock on mine? Which is us cellular. If you use the right kernel nothing will brick your phones. discussion over
Sent from my SCH-R950 using XDA
Click to expand...
Click to collapse
No no no dont close the discussion. By all means anyone care to give a quick tutorial on what you did to get a different carrier's rom on your's
Sent from my SPH-L900 using xda premium
mackentosh said:
No no no dont close the discussion. By all means anyone care to give a quick tutorial on what you did to get a different carrier's rom on your's
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Open the zip and be sure the only things you see are boot.img, META-INF, and system. If so, flash and reboot. If it bootloops, plug in and use adb to run a logcat to see why it won't boot and attempt fix it. A kernel is not enough to brick you unless it gets flashed over the wrong partition. Which I don't believe is a concern here since the partitions are the same across all the note ii's.
Sent from my SPH-L900 using xda premium
billard412 said:
Open the zip and be sure the only things you see are boot.img, META-INF, and system. If so, flash and reboot. If it bootloops, plug in and use adb to run a logcat to see why it won't boot and attempt fix it. A kernel is not enough to brick you unless it gets flashed over the wrong partition. Which I don't believe is a concern here since the partitions are the same across all the note ii's.
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Do you have to switch boot.img or no
Sent from my SPH-L900 using xda premium
The CSC data needs to be replaced. The kernel should be fine. Some of the etc files should probably be replaced. The build.prop needs to be edited for Sprint/cdma.
Check the install script and compare it to sprints to make sure there arent any partitions being formatted differently. I have used a few different at&t roms on mine by doing the above.
na7q said:
Very true. How else was I to run every variant? Especially your sprint stock on mine? Which is us cellular. If you use the right kernel nothing will brick your phones. discussion over
Sent from my SCH-R950 using XDA
Click to expand...
Click to collapse
mackentosh said:
No no no dont close the discussion. By all means anyone care to give a quick tutorial on what you did to get a different carrier's rom on your's
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
i was referring to the international versions as was specifically stated in the post. even if you change the boot.img to the proper one it will not flash properly to the phone because the partitions are different on the INT version.
the US variants all have the same partitions and will flash properly with the carrier specific kernel minus a few bugs here and there. and doing what shiftr182 said will usually get rid of any other bugs.
billard412 said:
Open the zip and be sure the only things you see are boot.img, META-INF, and system. If so, flash and reboot. If it bootloops, plug in and use adb to run a logcat to see why it won't boot and attempt fix it. A kernel is not enough to brick you unless it gets flashed over the wrong partition. Which I don't believe is a concern here since the partitions are the same across all the note ii's.
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
mackentosh said:
Do you have to switch boot.img or no
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
YOU SHOULD change the boot.img to the proper kernel
ok so I finally got my sgh-t999L through warranty exchange, and i'm excited to play with it. I rooted it with motochopper and have been looking around, but can't find anything quite concrete, seeing as the original threads discussing the t999L are rather dated. What is the progress on the stock odin? have most roms updated their scripts to include the t999L? Can I flash my previous rom with little to no issues?
Fimrware and radios I'm already aware, albeit I'm concerned about mb7 as it feels a little hot during use. kernels and roms it seems are ok, but I'm curious if there are extra steps to do and such. I can flash twrp 2.6 through odin right?
Naturesretard said:
ok so I finally got my sgh-t999L through warranty exchange, and i'm excited to play with it. I rooted it with motochopper and have been looking around, but can't find anything quite concrete, seeing as the original threads discussing the t999L are rather dated. What is the progress on the stock odin? have most roms updated their scripts to include the t999L? Can I flash my previous rom with little to no issues?
Fimrware and radios I'm already aware, albeit I'm concerned about mb7 as it feels a little hot during use. kernels and roms it seems are ok, but I'm curious if there are extra steps to do and such. I can flash twrp 2.6 through odin right?
Click to expand...
Click to collapse
I wouldn't say any of it is dated...its barely been out over a month if I'm remembering right. And the development thread is still fairly active. I am stalled on the Odin part until we get another dump of some of the partitions, (motodefiers working on that) but this really is a non issue anyway. It may take an extra step or two but we can easily get the same result as a full firmware flash already.
Besides, other than kernel, system and recovery, everything should still be MB7 on your phone, and you should not be looking at changing that.
As far as roms having added the asserts, I don't know. The only way to know is to try them. Or open them and check the asserts.
And what is your previous rom? Cant tell you anything about it unless I know what it is. Why are you concerned over mb7 firmware. I wouldn't put much worry about that as its all that's available for now. What extra steps are you looking for? What is it you are trying to do?
And yes, you can flash 2.6.0.0 twrp.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
I wouldn't say any of it is dated...its barely been out over a month if I'm remembering right. And the development thread is still fairly active. I am stalled on the Odin part until we get another dump of some of the partitions, (motodefiers working on that) but this really is a non issue anyway. It may take an extra step or two but we can easily get the same result as a full firmware flash already.
Besides, other than kernel, system and recovery, everything should still be MB7 on your phone, and you should not be looking at changing that.
As far as roms having added the asserts, I don't know. The only way to know is to try them. Or open them and check the asserts.
And what is your previous rom? Cant tell you anything about it unless I know what it is. Why are you concerned over mb7 firmware. I wouldn't put much worry about that as its all that's available for now. What extra steps are you looking for? What is it you are trying to do?
And yes, you can flash 2.6.0.0 twrp.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Not dated like really old, but at that time you hadn't made much progress. Just found your thread about the stock rom. So you have made much progress. At the moment I was furrently running vanilla rootbox latest nightly, hiw would I check asserts? Not really worried about changing firmware, just felt a little hot. This being new I understand there are no other radios.
Also thanks for the quick reply
Sent from my SGH-T999L using xda premium
I don't see any reason it wouldn't work. I think I misunderstood something earlier, but ant rom you see in this forum should work fine, its just some won't flash without "help".
The asserts ar in the updater scripts. They determine if certain properties match before allowing something to flash.
Ill be posting a lot of info soon...
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
I don't see any reason it wouldn't work. I think I misunderstood something earlier, but ant rom you see in this forum should work fine, its just some won't flash without "help".
The asserts ar in the updater scripts. They determine if certain properties match before allowing something to flash.
Ill be posting a lot of info soon...
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Tyvm. It will come in handy. I haven't even gotten to the ROM flash yet, though I have installed twrp. Will be creating a new thread... But I'm having the WEIRDEST bug trying to pull everything off my internal SD on my t999. If its more than one file, windows gets stuck on "calculating time required to copy"
Sent from my SGH-T999 using xda premium
Make sure you install this MODEM. Without it, you'll have a phone that never deep sleeps. ever.
Click to expand...
Click to collapse
on the cm 10.2 instructions it says this to install a modem
do you we need to install this exact modem after each rom install (not just cm) or are there other stock att modems that should be flashed after a rom? I'm pretty new to rooting/flashing on LG. I had an optimus L9 but it seems things changed a little or maybe it's just the lingo. any help would be appreciated. I have decided to stick with LG from here on out so if you have a beginner's tutorial or guide that would explain alot of these things that would be very helpful. one more question I have is that on a roms OP it says to wipe data/cache/dalvik in addition to your system, is this good practice when installing any rom? would wiping the system erase cwm and any root files or am I wrong on that one?
As far as I can tell flashing modems doesn't actually do anything.
Sent from my LG-E988 using xda app-developers app
esimon311 said:
As far as I can tell flashing modems doesn't actually do anything.
Sent from my LG-E988 using xda app-developers app
Click to expand...
Click to collapse
I saw someone else say that but if flashing modems are pointless why would all the devs be saying to in their rom op
deadenz said:
I saw someone else say that but if flashing modems are pointless why would all the devs be saying to in their rom op
Click to expand...
Click to collapse
Probably because they are operating under the same misconceptions as everyone else. No shame there, because on other devices, it does work, but we have to deal with reality, and that reality is clear: flashing modems on the e980 via CWM/TWRP for reasons yet unclear does not actually change the modem.
Flashing via LG's ancient and super-crappy tools does.
I agree 100% I have tried flashing countless modems every which way possible... and never had it actually change my modem.
:thumbdown:
Sent from my LG-E988 using xda app-developers app