How does a Telus owner flash a rom for the T989 without boot loops? Is there a kernel or radio they have to flash?
Every Rom comes with a kernel. Well almost every Rom does. You just need to flash it normally. Telus and T-Mobile are completely identical. Shouldn't cause bootloops. sounds like user error?
Sent from my SGH-T989 using xda app-developers app
Teo032 said:
Every Rom comes with a kernel. Well almost every Rom does. You just need to flash it normally. Telus and T-Mobile are completely identical. Shouldn't cause bootloops. sounds like user error?
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
That's what I thought and I guess it could be user error, but I've tried to help several different Telus users that get bootloops unless the rom is specifically for the Telus. One finally got it to work by flashing a different radio but he never got back to me about which radio.
Radio shouldn't be the problem with the bootloop. Might it be the way you're flashing?
Sent from my SGH-T989 using xda app-developers app
Teo032 said:
Radio shouldn't be the problem with the bootloop. Might it be the way you're flashing?
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Its not me . I don't have the Telus. It was 2 or 3 different Telus users trying different roms. One was trying CM9, another Jedi Mind Trick, and I can't even remember the other. They would either get a boot loop or stuck at the boot up screen. I started thinking maybe it was something different a Telus user had to use. It sounded like they were flashing right and using Darkside Super and Cache wipe.
The one trying Jedi was told to update his radio and it worked. So that got me wondering about Telus and radios. I dunno ..
Depends on their recovery. The wipe scripts might not be preferred anymore. If they're flashing from gb then yeah they probably need to change to a ics radio.
Sent from my SGH-T989 using xda app-developers app
I haven't had any problems running T-Mobile ROMs and I'm with Telus. I've used 3 or 4 different GB ROMs, 3 ICS ROMs and one JB ROM. Some were Telus specific while others weren't.
All ROMs/kernels/radios were flashed using non touch cwm 5.0.2.7. I also use the darkside scripts.
mintharis said:
I haven't had any problems running T-Mobile ROMs and I'm with Telus. I've used 3 or 4 different GB ROMs, 3 ICS ROMs and one JB ROM. Some were Telus specific while others weren't.
All ROMs/kernels/radios were flashed using non touch cwm 5.0.2.7. I also use the darkside scripts.
Click to expand...
Click to collapse
Thanks, I talked to another Telus user who hasn't had a problem either. I guess it was just a user error with the other folks.
I have a boot loop problem with my Koodoo T989D on stock TLLG2 rom.
First I odin the recovery 5.0.2 to flash UVLH1, and then flash the CM10 10/22.
Next reboot the phone and it hangs at the CM10 boot animation screen.
Tried to odin back the UVLH1 stock rom but it fails to write at amss.bin.
Tried the Darkside cache wipe but doesn't make a difference
Can someone give me any suggestion?
RA017 said:
I have a boot loop problem with my Koodoo T989D on stock TLLG2 rom.
First I odin the recovery 5.0.2 to flash UVLH1, and then flash the CM10 10/22.
Next reboot the phone and it hangs at the CM10 boot animation screen.
Tried to odin back the UVLH1 stock rom but it fails to write at amss.bin.
Tried the Darkside cache wipe but doesn't make a difference
Can someone give me any suggestion?
Click to expand...
Click to collapse
Did you make a nandroid backup before you flashed UVLH1? Did you try to Odin back to the stock Koodo rom?
RA017 said:
I have a boot loop problem with my Koodoo T989D on stock TLLG2 rom.
First I odin the recovery 5.0.2 to flash UVLH1, and then flash the CM10 10/22.
Next reboot the phone and it hangs at the CM10 boot animation screen.
Tried to odin back the UVLH1 stock rom but it fails to write at amss.bin.
Tried the Darkside cache wipe but doesn't make a difference
Can someone give me any suggestion?
Click to expand...
Click to collapse
Use this recovery
http://forum.xda-developers.com/showthread.php?t=1844637
I had the same problem
supersain08 said:
Use this recovery
http://forum.xda-developers.com/showthread.php?t=1844637
I had the same problem
Click to expand...
Click to collapse
Thanks for your suggestion, I'll double check tonight.
FYI, last night I tried ODIN the T989D image (not T989) and finally it flash successfully with the modem.
Related
I'm currently running the stock EL29 with root and CWM but whenever I try to install a custom rom (AOPK, CM9, etc...) through CWM, it says "Instillation Aborted" as if they weren't made for this phone when I know they were. What's going on?
.HaVoC. said:
I'm currently running the stock EL29 with root and CWM but whenever I try to install a custom rom (AOPK, CM9, etc...) through CWM, it says "Instillation Aborted" as if they weren't made for this phone when I know they were. What's going on?
Click to expand...
Click to collapse
Silly question, and not assuming, did you use autoroot for cwm?
May want to Odin to el26 and autoroot cwm ans try it that way.
I personally Odin back to el29, autoroot, and (knock on wood) never had an issue.
Sent from my SPH-D710 using XDA
.HaVoC. said:
I'm currently running the stock EL29 with root and CWM but whenever I try to install a custom rom (AOPK, CM9, etc...) through CWM, it says "Instillation Aborted" as if they weren't made for this phone when I know they were. What's going on?
Click to expand...
Click to collapse
Usually that happens on a bad download. Did you download them on your phone or PC?
It turns out that is was just the version of CWM that I was using but now I have a new problem. I flashed CM9 and everything worked EXCEPT the data connection so then I flashed AOPK and had the same problem. The only way I can get online is via wifi. How do I fix this?
.HaVoC. said:
It turns out that is was just the version of CWM that I was using but now I have a new problem. I flashed CM9 and everything worked EXCEPT the data connection so then I flashed AOPK and had the same problem. The only way I can get online is via wifi. How do I fix this?
Click to expand...
Click to collapse
Check you baseband in settings>about phone. If it says unknown then just flash a modem of your choice. This has happen to me. On several occasions.
Sent from my SPH-D710 using xda premium
.HaVoC. said:
It turns out that is was just the version of CWM that I was using but now I have a new problem. I flashed CM9 and everything worked EXCEPT the data connection so then I flashed AOPK and had the same problem. The only way I can get online is via wifi. How do I fix this?
Click to expand...
Click to collapse
Cool that ya got to flash from though!
Sorry, I don't use CM9.
I can try on my other e4gt later and test though.
Sent from my SPH-D710 using XDA
krazy_smokezalot said:
Check you baseband in settings>about phone. If it says unknown then just flash a modem of your choice. This has happen to me. On several occasions.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
It says "S710.10 S.EL29"
Isn't EL29 for GB only or something?
.HaVoC. said:
It says "S710.10 S.EL29"
Isn't EL29 for GB only or something?
Click to expand...
Click to collapse
No its ok to have an older modem and be running ICS. They can be "mismatched."
slick_rick said:
No its ok to have an older modem and be running ICS. They can be "mismatched."
Click to expand...
Click to collapse
And I have found, in the boonies that I'm in, el29 modem works the best for me on any ics builds..
Sent from my SPH-D710 using XDA
.HaVoC. said:
It says "S710.10 S.EL29"
Isn't EL29 for GB only or something?
Click to expand...
Click to collapse
Did u get it to work yet?? Try to Odin stock gb el29 rom. And start from scratch...
Sent from my SPH-D710 using xda premium
krazy_smokezalot said:
Did u get it to work yet?? Try to Odin stock gb el29 rom. And start from scratch...
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I started from scratch and followed all the steps until I ended up in the same boat. AOKP Build 38 working perfectly EXCEPT data. I tried the EL29 and FE10 kernels but neither made a difference.
.HaVoC. said:
I started from scratch and followed all the steps until I ended up in the same boat. AOKP Build 38 working perfectly EXCEPT data. I tried the EL29 and FE10 kernels but neither made a difference.
Click to expand...
Click to collapse
Try going back to gingerbread and flashing the EL26 kernal. Then flash the ICS rom you want through that recovery.
AOKP and CM9 have problems with data. every time you or system turn off screen say goodbye to data until 1.enable disable airplane mode or 2.reboot that's the main reason I stay away from these awesome roms until source arrives.
These roms are the best. IMO
1.odin back to stock el29 full reset oc
2.boot update profile and prl
3.copy the rom files to sd
4.turnitoff it off
4.enter download mode and flash el26+cmw for AOKP or el29+cwm direct boot for CM9
5.clear cache, factory data reset, clear dalvik on advance menu
6.go back and select install zip from sd card and choose the rom and flash it
7.flash gapps if apply
8.go back and select reboot system
9.enjoy these awesome roms.
Sent from my SPH-L710 using Tapatalk 2
I think I FINALLY got it to work. I started stock with rooted EL29 Odin-OC, flashed the "StockCWM-EL26.tar.m5d" in Odin, flashed the AOKP build 37 rom, flashed gapps, then flashed the FE16 kernel AND modem. When I rebooted the data was working.
Not that I am advocating this, and I am far from an expert, but I odin flash a stock rooted rom (SPH-D710.FC22_CL287574_ROOTED-oc-sfx) without going back to el29 just to have a nice clean stock rom to flash over with something else (like FIFO2). I just try to make sure I do everything in the same session so I don't get stuck in a stock recovery.
My order when flashing (non-Odin):
calkulin's format all
Modem (sometimes...if newer is available)
Rom
Kernel (with a custom recovery; sometimes the roms come with a stock recovery so if you reboot before installing a custom one, you'll have to either use odin to flash a custom recovery or mobile Odin)
any additional items that the rom didn't include (like gapps, etc.)
reboot
---------- Post added at 02:09 AM ---------- Previous post was at 01:58 AM ----------
Another thing to keep in mind is that AOKP was ported to the E4GT. That could cause issues depending on what you're coming from. Make sure to read all the instructions from the dev before flashing. If the worst happens, buy insurance on your phone and smash it...That's what I did with my evo when I bricked it.
whenever i flash any custom rom whether the rom version is android 4.2/4.1.2/4.1.1 , my phone has no bootscreen and a messed up flashscreen when it sais (samsung galaxy note 2 GT-N7100) but then after waiting the appropriate time, the rom works fine but same problem when rebooting... i attached the flashcreen and how it looks like, i have no idea why this happens.i just press the lockscreen after rebooting and waiting and the rom works normally. i rooted using the Galaxy Note II Toolkit v3.0.0 GSM. i first experienced this right after flashing and entering recovery(cmw) but twrp worked fine then, now any rom i flash i experience this,
Is anyone faceing a similar problem or can help in anyway ?
stock rom works fine btw
try flashing Philz recovery
dr.ketan said:
try flashing Philz recovery
Click to expand...
Click to collapse
is philz recovery in the link u posted because i cant see it,
inorder to install it, i flash stock rec then philz via odin right?
http://forum.xda-developers.com/showthread.php?t=2028103
yes flash tar file with odin (no need to flash stock, straight way flash with odin)
dr.ketan said:
http://forum.xda-developers.com/showthread.php?t=2028103
yes flash tar file with odin (no need to flash stock, straight way flash with odin)
Click to expand...
Click to collapse
this is the second picture... i flashed philz and still same problem! stock works fine :S its making me crazy!
I have the same screen after installing cm 10.1 ... never tried to wait some time to boot.... tried several times with several recoveries... result the same. Before used s3 i9300 and never had such issue. Hope someone will help
Sent from my GT-N7100 using xda premium
T511 said:
I have the same screen after installing cm 10.1 ... never tried to wait some time to boot.... tried several times with several recoveries... result the same. Before used s3 i9300 and never had such issue. Hope someone will help
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
tell me a rom you tried that works fine with the bootanimation and everything please! because so far ive tried several! non have worked. and what recovery are you using?
karlada said:
tell me a rom you tried that works fine with the bootanimation and everything please! because so far ive tried several! non have worked. and what recovery are you using?
Click to expand...
Click to collapse
I tried rom managers cwm and twrp manager and cm 10.1 rom only. Tried several times and no luck. Same screen after install.
Sent from my GT-N7100 using xda premium
Hi, wondering if anyone can help.
I was running my note 2 n7100 on Omega rom v15 with perseus kernal v35. It was fine, until yesterday my phone started rebooting.
I reflashed Omega rom, I unrooted and reflashed stock rom, I rooted and tried other roms.. however, im still having problems.
Once the phone has restarted and got to home screen, whenever I do anything, the phone reboots. (on Cm10.1 rom varients - jellybam and pa3.5)
When using stock rom and omega rom the phone doesn't even go past the samsung galaxy note II logo screen.
I've read somewhere, that reflashing the bootloader may help, so I may give that a try..
Does anyone else have any ideas or similar problems?
Hi
Never had this issue but if I were you, I think I'll do all Wipe & format options from my recovery and then I'll flash a Factory firmware via Odin.
Memphis_ said:
Hi
Never had this issue but if I were you, I think I'll do all Wipe & format options from my recovery and then I'll flash a Factory firmware via Odin.
Click to expand...
Click to collapse
He did that.
Could be A hardware issue.
Sent from my GT-N7100 using xda premium
UtkarshGupta said:
He did that.
Could be A hardware issue.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Flashing a stock rom isn't a clean installation so this is not what I suggested.
Am I the only one with videotron that is getting the error when trying to flash any of the new MD5 rom. Did a FW and tried all of the new rom's and no matter which one I install I'm getting the error process.android.phone FC. Even went back to stock and nothing is working
Thanks
rener78 said:
Am I the only one with videotron that is getting the error when trying to flash any of the new MD5 rom. Did a FW and tried all of the new rom's and no matter which one I install I'm getting the error process.android.phone FC. Even went back to stock and nothing is working
Thanks
Click to expand...
Click to collapse
Perhaps this T999 4.1.2 firmware update was not meant for your videotron phone.
It looks like you will need to get a hold of the stock Odin flash rom for your phone
and Odin flash it before you can do anything else.
Here is the link for the Odin Flash stock Videotron firmware for your phone in case you want
to flash it and start over again: http://www.androidfilehost.com/?fid=9390225151984927270
Misterjunky said:
Perhaps this T999 4.1.2 firmware update was not meant for your videotron phone.
It looks like you will need to get a hold of the stock Odin flash rom for your phone
and Odin flash it before you can do anything else.
Here is the link for the Odin Flash stock Videotron firmware for your phone in case you want
to flash it and start over again: http://www.androidfilehost.com/?fid=9390225151984927270
Click to expand...
Click to collapse
I did that and I still got the error :s
re: fc
rener78 said:
I did that and I still got the error :s
Click to expand...
Click to collapse
Try this:
Go into CWM or TWRP recovery and "Fix Permissions" then reboot.
If you still have the problem go into CWM or TWRP again and do a
factory reset/wipe cache/wipe dalvik cache but do not wipe system.
After doing that fix permissions again and reboot the phone.
Thanks alot but I give up I've tried what you told me and I still get the error. I guess it's just not ready as you said...Thanks alot again
Misterjunky said:
Try this:
Go into CWM or TWRP recovery and "Fix Permissions" then reboot.
If you still have the problem go into CWM or TWRP again and do a
factory reset/wipe cache/wipe dalvik cache but do not wipe system.
After doing that fix permissions again and reboot the phone.
Click to expand...
Click to collapse
Are you just trying to flash the firmware? If so is there any you can flash so that its back to normal and working? You mentioned the error happened when trying to use the vtron fw is why I ask.
If you can get it working, flash jovys stock rom instead of the firmware. I dont see why this wont work if your up and running beforehand.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Are you just trying to flash the firmware? If so is there any you can flash so that its back to normal and working? You mentioned the error happened when trying to use the vtron fw is why I ask.
If you can get it working, flash jovys stock rom instead of the firmware. I dont see why this wont work if your up and running beforehand.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I tried to flash Jovy's stock MD5 rom and got the FC error, so I decided to go back to rooted stock and then flashing back Jovy's and other MD5 rom and still getting the FC. Will now try Jamieson rom and see from there again. Will post the results.
EDIT Still a no go under Infamous as well. Freaking mad
Thanks
Thats odd. It should work. Let me know how the other goes. Im out until a little later tonight so may not reply for a bit. Good luck!
Sent from my SGH-T999 using xda premium
I'm with Videotron I did get that error, try an original AOSP or CM ROM... Sometimes other ROMS implements T-Mobile features that our SIM i'snt compatible like the Mobile HotSpot App. And dont forget to fully wipe and factory reset it after !
Do you happen to have mobile odin pro? If so, try flashing the root66 firmware that way. Deselect the modem and flash.
Be prepared with a backup and with odin and your stock firmware though, just in case.
The more I think about it, the more I wonder if its a kernel issue. Youre still using your vtron 4.1.1 kernel with tmobiles 4.1.2 system. Before trying the fw, try flashing the kernel that comes with md5. If you cant find it ill post it up in a while.
I dont know how likely this is the prob, but may be worth trying...
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Do you happen to have mobile odin pro? If so, try flashing the root66 firmware that way. Deselect the modem and flash.
Be prepared with a backup and with odin and your stock firmware though, just in case.
The more I think about it, the more I wonder if its a kernel issue. Youre still using your vtron 4.1.1 kernel with tmobiles 4.1.2 system. Before trying the fw, try flashing the kernel that comes with md5. If you cant find it ill post it up in a while.
I dont know how likely this is the prob, but may be worth trying...
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Thanks again I have tried with a 4.1.2 kernel and it's still not working, I couldn't find anywhere the kernel coming with MD5. Looked in [Baseband] ALL T999(V) Modems! w/ MAP and Data Tweaks! and couldn't find it aswell.
Cause I used multi-carrier rom 4.1.2 before, Sprint, AT&T, Verizon but for some reason this one is giving a hell of a time.
Even tried an AT&T port of this T-mobile update and it wasn't working
Thanks alot again I really appreciate it
Well there's an update. None of the MD5 rom is working for me I always get the error. But 4.1.2 ports from other carriers are working. Really strange. So I guess I just need to wait for the official update.
**Edit** Well stockorama is actually working.. Weird
Is there anyone with a videotron sgs3 running an MD5 rom?? Cause I can't, only stockorama 2 other than that I cannot..
I recently bought, and finally rooted my sprint sph-l710. I have flashed two roms, hyperdrive, and moar roms. My problem is that i cant flash anything else, only those two roms. Is there a fix?
bigchuq said:
I recently bought, and finally rooted my sprint sph-l710. I have flashed two roms, hyperdrive, and moar roms. My problem is that i cant flash anything else, only those two roms. Is there a fix?
Click to expand...
Click to collapse
What do you mean you can't flash anything else? When you flash, are you wiping everything clean each time before flashing ROMs or are you dirty flashing?
tkepk181 said:
What do you mean you can't flash anything else? When you flash, are you wiping everything clean each time before flashing ROMs or are you dirty flashing?
Click to expand...
Click to collapse
yes, i'm wiping everything, whenever i try to install any other rom i have some type of error. i'm new to this so please excuse my noobness. i've tried to flash a stable cm10, among others with no luck.
Do you have the md4 boot loader?
Sent from my SPH-L710 using xda app-developers app
The new S3 have been modded by Sprint /Samsung and require a modded recovery in order to mount storage. The other issue is that you can not flash an aosp style rom. You should be able to flash any TW rom but it won't allow aosp roms to flash. None of the developers have a new S3 so until someone gets one ir someone volunteers one this won't be solved.
Remember search is your best friend, Have a great day!
IDontKnowMang said:
Do you have the md4 boot loader?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I believe so, but i'm not sure is that @ the end of the build number? If so, yes
bigchuq said:
I believe so, but i'm not sure is that @ the end of the build number? If so, yes
Click to expand...
Click to collapse
If your getting a status 7 error that is the bootloader error flash this in recovery it will update all your firmware and bootloader. http://db.tt/Qt6NcH0a
After flashing this make sure you reboot the phone then try going back into recovery and flashing the rom you want.
Remember search is your best friend, Have a great day!
Is this still a legit fix even after the 4.3 upgrade?
I just tried this and now my phone wont even power on.