Related
I have flashed the new CyanogenMod and the Cyanogen Recovery 1.4 and when I wipe everything and flash, it'll load up and I can use the phone 100% perfectly, but once I reboot my phone, or turn it off and on, it never goes past the green boot screen. Anyone have any solutions/reasons why it does that? It's with every single Cyanogen mod too, i've tried several of them.
Probably because you have a lot of apps?
If not, reflash it.
tmc_adio07 said:
I have flashed the new CyanogenMod and the Cyanogen Recovery 1.4 and when I wipe everything and flash, it'll load up and I can use the phone 100% perfectly, but once I reboot my phone, or turn it off and on, it never goes past the green boot screen. Anyone have any solutions/reasons why it does that? It's with every single Cyanogen mod too, i've tried several of them.
Click to expand...
Click to collapse
what do you actually flash and what is the actual process, you shouldnt have any issues after it boots up the first time, wipe everything and make an exterior partition meaning get rid of your cyanogen recovery 1.4 and get amon ra's latest... look in the dev section and read up on cyan's page on how to flash the rom
mt3g said:
what do you actually flash and what is the actual process, you shouldnt have any issues after it boots up the first time, wipe everything and make an exterior partition meaning get rid of your cyanogen recovery 1.4 and get amon ra's latest... look in the dev section and read up on cyan's page on how to flash the rom
Click to expand...
Click to collapse
Thanks for help man, right now I'm running dwang's rom 100% perfect w/ no issues at all. it can reboot and everything just fine. I'm just a little worried on going back and trying to flash cyanogens.
When I installed it, I first did the root process, downloading the .apk file and going through all that part smooth, then I downloaded and flashed the Cyanogen Recovery 1.4, and from there I downloaded the two files (DRC83_base and the latest cyan's rom, i forgot the version #) and applied update from SD, first doing DRC83 and right after doing the rom itself, without rebooting the phone. It loads up A-OK and I can installl the apps and go about my business, but once I need to restart my phone, it just never turns back on. I'm puzzled completely...I even did the whole unroot and reroot thing and STILL i'm not having any luck.
K I got confused in there some where did you flash a cyan rom at all in there I read that you flashed the drc83 zip file but sounds like you just flashed that and booted the phone lol... never tried that but.... any way it seems like you are doing everything correct onlything I could suggest is make sure you have the correct htc base image, and make sure you wipe and repair everything!!!!! and also try a differant download of cyanogen as you might have gotten a bad one or something I have never had any issues with a cyanogen rom except maybe a FC back on 4.0xx or something
兄弟，估计你刷成砖了。同情ing。。
over the last few days I've flashed a number of ROMs, mostly the Google Edition 4.2.2 and 4.3 ones and every single one of them eventually fails to boot hanging on the Samsung bootloader screen. and i say eventually because the first boot is almost always flawless, but then each time i reboot or power down, its almost guaranteed to loop.
I've tried so many different combinations that there's really not a single path I've taken every time, but the general steps are:
-root original firmware using motochopper
-install TWRP via GooManager
-reboot recovery and wipe everything, typically I do Advanced and select everything, then format Data
-then flash through ADB sideload, I do this since I wipe everything before flashing and I don't have an external SD card
-immediately after flashing ROM, I flash loki-doki also through ADB sideload. some of the ROMs I tried said they were lokied, but I still got the ATT invalid ROM message, so I reflashed with loki and it worked.
-then reboot system and the first time it comes up and works fine on every ROM I've tried
But if I power down or restart, on a very rare occasion it'll come up, but almost every time it hangs on bootloader screen. I also noticed once it's stuck on bootloader, power button becomes unresponsive, sometimes holding it powers down device, sometimes does nothing (have to press and hold twice)
If I flash back to stock using Odin, it works, boots, reboots, powers down just fine.
I've also tried flashing with a ROM and then immediately after with the stock ATT kernel, also booted up fine, but looped on restart.
Could this be hardware issue?
I'm about to give up on this and go back to stock for good, which would be really disappointing, can anyone help?
Flash a KT kernel and see what happens, I suppose you know which one correct?
TheAxman said:
Flash a KT kernel and see what happens, I suppose you know which one correct?
Click to expand...
Click to collapse
I assume KT means http://forum.xda-developers.com/showthread.php?t=2292341 ?
I've tried that too with jamal2367's 4.2.2 GE ROM (http://forum.xda-developers.com/showthread.php?t=2341794). It refused to boot all together.
First time I flashed with AOSP version since I thought that was an AOSP ROM, then reading more comments in the other thread it said I needed the TW version for GE ROMs, so I tried that too. Either way, neither of them booted at all, even the first time, so I gave up on KT and only used either ROMs' included kernels or ATT stock.
It is not a hardware issue, I am guessing that you have a US ATT G4 correct? I would odin back to stock, and restart the process again, this is assuming you tried the correct TW kernels. Because I know this error and all it requires is a simple flash of the correct kernel.
TheAxman said:
It is not a hardware issue, I am guessing that you have a US ATT G4 correct? I would odin back to stock, and restart the process again, this is assuming you tried the correct TW kernels. Because I know this error and all it requires is a simple flash of the correct kernel.
Click to expand...
Click to collapse
OK I'll try one more time from scratch, can you verify I'm using the right stuff though for US ATT Galaxy S4:
ROM: http://forum.xda-developers.com/showthread.php?t=2341794
Kernel: http://forum.xda-developers.com/showthread.php?t=2292341 (TW one, specifically http://goo.gl/SiDjB)
And any idea why the ROM's kernel wouldnt work after being lokied?
collegebored said:
OK I'll try one more time from scratch, can you verify I'm using the right stuff though for US ATT Galaxy S4:
ROM: http://forum.xda-developers.com/showthread.php?t=2341794
Kernel: http://forum.xda-developers.com/showthread.php?t=2292341 (TW one, specifically http://goo.gl/SiDjB)
And any idea why the ROM's kernel wouldnt work after being lokied?
Click to expand...
Click to collapse
You know, I don't even look at anything that says loki anymore, I flash the rom I want and use MY carriers kernel, bootloops and hangs are just not there, I do not see these issues everyone has, because, I have this procedure everytime. So...
Btw, your good on your files you want to flash, but, if this does not work ie, GE and that kernel, try a TW rom with the kernel, bet it boots properly. I do not give a rats
a$$ about goole roms. They are not worth it. Btw, I use this procedure on TW and aosp roms, no issues. Just because it says it loki'ed, flash the kernel you know works, loki just confuses people.
The Ax says again an again..My opinion only!
Good luck sir.
BTW, I ran that rom with the kernel you chose, it should work just fine. Remember, flash the TW version.
Thanks Ax for your help here, your welcome.
Phone stuck on "Samsung - Custom" screen after creating TWRP backup. Help please?
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Simonzi said:
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Click to expand...
Click to collapse
There are no less than a dozen similar threads about similar problems already. Have you looked at those threads for a possible solution yet? You can find them by using the search function or better yet just doing a visual search of the first few pages of the "General" and "Q&A" sections. Good luck.
Sounds like a ROM and kernel issue. Try flashing a ROM with a loki'd kernel.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Tylorw1 said:
Sounds like a ROM and kernel issue. Try flashing a ROM with a loki'd kernel.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
I don't see how that could be the case. I didn't flash anything. I just loaded TWRP, created a backup, and rebooted my phone. No ROM\kernel change. Nothing more than creating a backup in TWRP.
scott14719 said:
There are no less than a dozen similar threads about similar problems already. Have you looked at those threads for a possible solution yet? You can find them by using the search function or better yet just doing a visual search of the first few pages of the "General" and "Q&A" sections. Good luck.
Click to expand...
Click to collapse
I tried searching, the closest one I could find on the first few pages was this one. I just didn't see any specific to my situation because nothing was flashed. Like my response to Tylorw1, all I did was boot into recovery, create a backup, and reboot my phone. Didn't flash a ROM, change a kernel, format anything, etc...
I has this same problem... It happened after every single reboot after flashing various ROMs or anything.. I gave up and went back to CWM and haven't had the problem since :good:
Sent from my SGH-I337 using xda app-developers app
Simonzi said:
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Click to expand...
Click to collapse
what version of twrp? if it is 2.6.?.? then get off of it, also, what I did was pull battery for 3min, it booted fine....go back to early version of twrp...
STVERDI said:
I has this same problem... It happened after every single reboot after flashing various ROMs or anything.. I gave up and went back to CWM and haven't had the problem since :good:
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I've wanted to go back to CWM. That's what I had on my S3. Only thing stopping me, is all my nandroid backups for my S4 are done with TWRP, and I don't want to run into a situation where I need them, and them not being compatible
TheAxman said:
what version of twrp? if it is 2.6.?.? then get off of it, also, what I did was pull battery for 3min, it booted fine....go back to early version of twrp...
Click to expand...
Click to collapse
Nope, still on 2.5.0.2. Finally, after a third complete wipe/format and restore from the back I had created (the one that started the whole issue), it works fine. Such a huge pain in the ass.
a user had to boot back into twrp and wipe data/factory reset yesterday to fix this issue.
Simonzi said:
I've wanted to go back to CWM. That's what I had on my S3. Only thing stopping me, is all my nandroid backups for my S4 are done with TWRP, and I don't want to run into a situation where I need them, and them not being compatible
Nope, still on 2.5.0.2. Finally, after a third complete wipe/format and restore from the back I had created (the one that started the whole issue), it works fine. Such a huge pain in the ass.
Click to expand...
Click to collapse
And you have to be ****ing kidding me. I rebooted into recovery while typing my initial response, just to verify I was still on the 2.5.x.x TWRP. Booted up TWRP, verified that, choose "Reboot System", and same thing. Back to sitting at the Samsung screen. Nandroid backups or not, ditching TWRP as soon as I get it able to boot back up.
Even worse off now than when I started. After my last post, where my phone was doing the same "stuck on Samsung logo" thing, just from booting into TWRP, I decided to swap to a different recovery. Searched for "switch from TWRP to CWM", and found my own post I had made a few months ago, but never went through.
Following those instructions now, I decided on the PhilZ CWM. Head over to that thread, grab the loki'd zip, load up TWRP, and flash the zip. Now I can't even boot into recovery!! It just freezes on the Samsung screen with the blue "recovery booting" text.
Can still get into download mode, so I tried using ODIN to flash PhilZ jflteatt.tar.md5 file, and it fails.
At this point, waiting for the stock 1.6 firmware package to download, so I can just ODIN that.
If anyone has any other suggestions though, they'd be great. Have an hour to try while waiting for that to download
somebody had mentioned this...
http://forum.xda-developers.com/showpost.php?p=44629460&postcount=8
make sure you have the correct firmware and proceed as you are. likely your best bet.
Simonzi said:
Even worse off now than when I started. After my last post, where my phone was doing the same "stuck on Samsung logo" thing, just from booting into TWRP, I decided to swap to a different recovery. Searched for "switch from TWRP to CWM", and found my own post I had made a few months ago, but never went through.
Following those instructions now, I decided on the PhilZ CWM. Head over to that thread, grab the loki'd zip, load up TWRP, and flash the zip. Now I can't even boot into recovery!! It just freezes on the Samsung screen with the blue "recovery booting" text.
Can still get into download mode, so I tried using ODIN to flash PhilZ jflteatt.tar.md5 file, and it fails.
At this point, waiting for the stock 1.6 firmware package to download, so I can just ODIN that.
If anyone has any other suggestions though, they'd be great. Have an hour to try while waiting for that to download
Click to expand...
Click to collapse
Stock 1.6 firmware package?
Make sure you get the correct firmware? Go to SamMobile and get the stock firmware from there or go to Adam Outlers "Stock firmware ODIN" thread in the General section (the AMDL firmware link is in that thread you just have to look for it).
scott14719 said:
Stock 1.6 firmware package?
Make sure you get the correct firmware? Go to SamMobile and get the stock firmware from there or go to Adam Outlers "Stock firmware ODIN" thread in the General section (the AMDL firmware link is in that thread you just have to look for it).
Click to expand...
Click to collapse
Yeah, I meant 1.6gb firmware package. Just forgot the "gb". That's what I'm currently downloading, but trying to recover it with Kies while waiting.
I would like to report I had the same problem.
After changing roms and making a nandroid, and then deciding to switch roms again, I ran into the stuck at Samsung Custom with a lock boot screen. Most roms would boot up once, but a restart or power down would lead to being stuck. I was flashing through TWRP.
I went into TWRP and flashed OUDHS recovery which overrode TWRP and wiped/flashed through OUDHS a new rom.
Problem solved.
S3 at&t stuck in TWRP booting screen.
xBeerdroiDx said:
a user had to boot back into twrp and wipe data/factory reset yesterday to fix this issue.
Click to expand...
Click to collapse
Im new to custom roms, I pressed ok for an update on my phone, after the update was complete my phone shut off and booted into TWRP and now I can't get back to my android screen nor make calls etc. HELPPPPPPPP PLEASSSSSEE I have been trying to fix my phone since july and I have been using this cheap phone that don't even get internet. I have an S3 1747 at&t
Lnjames said:
Im new to custom roms, I pressed ok for an update on my phone, after the update was complete my phone shut off and booted into TWRP and now I can't get back to my android screen nor make calls etc. HELPPPPPPPP PLEASSSSSEE I have been trying to fix my phone since july and I have been using this cheap phone that don't even get internet. I have an S3 1747 at&t
Click to expand...
Click to collapse
Wrong forum. Please go to the s3 section with your question.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Had this problem just now, solved it by fixing permissions.
I am running an MDL based S4, and screwed the pooch. I was going to wipe the internal storage and made the mistake of doing it through TWRP 2.5. Now, I have the same problem of being stuck on the custom boot screen. I have tried to change from TWRP to OUDHS Recovery, but still boot loops to Custom screen. I have tried fresh installs of 4.2 ROMs and 4.4.2 Google Editions. Do I need to flash via ODIN?
Flame away....I know better than this!!!!
Help would be greatly appreciated.
Sent from my GT-N8013 using Tapatalk 4
I'm running an S4 and have this very weird issue where after installing a custom rom, the phone would reboot and load the rom successfully, but if I ever reboot it, it never wants to go past the Samsung logo.
If I try entering TWRP and fixing permissions or factory reset, it just comes up with errors and fails. The only way around it is to format data, then reflash the rom.
But now I have a nandroid backup so everytime I reboot, I basically have to reflash the rom.. It's happened on at least 2 roms!
I've used the search function on the forums and found a thread was inconclusive so I've made this thread.
Thanks in advance
(This is my first Android phone too, so I'm not 100% familiar with all the different software and techniques, but I can definitely learn!)
Try flashing the ROM with the latest stock CWM. TWRP can cause issues.
Kesh09 said:
I'm running an S4 and have this very weird issue where after installing a custom rom, the phone would reboot and load the rom successfully, but if I ever reboot it, it never wants to go past the Samsung logo.
If I try entering TWRP and fixing permissions or factory reset, it just comes up with errors and fails. The only way around it is to format data, then reflash the rom.
But now I have a nandroid backup so everytime I reboot, I basically have to reflash the rom.. It's happened on at least 2 roms!
I've used the search function on the forums and found a thread was inconclusive so I've made this thread.
Thanks in advance
(This is my first Android phone too, so I'm not 100% familiar with all the different software and techniques, but I can definitely learn!)
Click to expand...
Click to collapse
go into the wipe options on twrp - go to advanced and select - cache, dalvik, system, data - swipe
then do a normal full wipe
reflash the chosen rom
power off rather than reboot
then power up
something gets fracked with the wipes somewhere and thats how i fixed it.
either that or flash philz recovery through odin and do a "new rom" wipe
Gotcher said:
Try flashing the ROM with the latest stock CWM. TWRP can cause issues.
Click to expand...
Click to collapse
For some reason, whenever I install CWM, it keeps getting stuck at "recovery booting" and once in maybe 30 times it works, haven't got it to work in a while.. Not sure what's happening, but if I flash TWRP again, it boots up fine. Am I doing anything wrong? Using Philz touch..
scottyf79 said:
go into the wipe options on twrp - go to advanced and select - cache, dalvik, system, data - swipe
then do a normal full wipe
reflash the chosen rom
power off rather than reboot
then power up
something gets fracked with the wipes somewhere and thats how i fixed it.
either that or flash philz recovery through odin and do a "new rom" wipe
Click to expand...
Click to collapse
This hasn't worked for me, and yeah, I can't seem to get CWM to like my phone..
Kesh09 said:
For some reason, whenever I install CWM, it keeps getting stuck at "recovery booting" and once in maybe 30 times it works, haven't got it to work in a while.. Not sure what's happening, but if I flash TWRP again, it boots up fine. Am I doing anything wrong? Using Philz touch..
This hasn't worked for me, and yeah, I can't seem to get CWM to like my phone..
Click to expand...
Click to collapse
try flashing the rom twice in succession. it will stick eventually but its just getting the right combo. these S4's are a right pain in the ass just now.
also another option would be downloading a rom with Aroma installer onto a micro sd and see if that gets you out of the problem. ive found on other devices ive had that a rom with Aroma can sometimes get you moving (id suggest Omega rom as a good solid base)
scottyf79 said:
try flashing the rom twice in succession. it will stick eventually but its just getting the right combo. these S4's are a right pain in the ass just now.
also another option would be downloading a rom with Aroma installer onto a micro sd and see if that gets you out of the problem. ive found on other devices ive had that a rom with Aroma can sometimes get you moving (id suggest Omega rom as a good solid base)
Click to expand...
Click to collapse
The rom I'm flashing (twice) now is Omega actually!
I'll see how this goes! Hoping it's okay!
..
try to install another rom clean & stable and do full wipe or trust me the best to turn the phone to default firmware.
Kesh09 said:
The rom I'm flashing (twice) now is Omega actually!
So are you suggesting I install Omega, get it run, then install Aroma installer and reinstall it?
Click to expand...
Click to collapse
no i just meant flash the rom twice IF it didnt have Aroma.
try GoldenEye rom from micro sd (obviously downloaded and placed on the card through a pc and put back in the phone).
Or as above - you might have to start from scratch and use Odin to revert back to stock and re-root etc again.
Although i said Aroma sometimes helps, being honest it was a rom with Aroma that started causing me a similar issue in the first place (Not Omega or Foxhound though)
No luck guys... I think I'd rather start from a stock rom too. When I created my stock rom backup, it was through nandroid and an CWM format, but CWM did work, it froze when it was checking for MD5 or something...
But now I'm trying to find the right firmware for my phone, is there any thing I need to look out for? Gt-i9505 from Australia?
http://forum.xda-developers.com/showthread.php?t=2265477
In that thread, there's two of them, I'm downloading the one closest to when I bought it which was June
So this morning, on my ATT GS4 NC1, I went into safestrap and created a new installation on rom slot 1. I guess that's what you call it. I pressed rom slot 1, then wiped, then installed hyperdrive. The install went fine and afterwards, I installed the NC1 module.zip and the SU zip file (both found in the "all things att" thread under "NC1 instructions".
Once it was done, I rebooted but what it did was boot to the regular stock rom. All my screens were the same (app placements, settings, etc) but I noticed I had no cell signal. I went to settings>mobile network and it said something about needing to install a sim card. Sorry I can't remember exactly what it said.
Anyhow, I went into safestrap, rebooted and then activated the stock rom slot and booted. Everything is fine.
What happened? Any ideas as to what happened? As of right now, I am running on the stock slot using the stock rom pending suggestions from you all.
Thanks!
KitKat ROMs will work only when flashed to stock slot.
jmjoyas said:
KitKat ROMs will work only when flashed to stock slot.
Click to expand...
Click to collapse
Ok, that makes sense. I just did it using the stock slot and it works. thanks!
burgertime78 said:
Ok, that makes sense. I just did it using the stock slot and it works. thanks!
Click to expand...
Click to collapse
Hmm I've been wondering this since I've not had success in doing so either. So what your saying is that it HAS to be done on STOCK slot in order for the rom to work? I've been scratching my head to why it refused to work for me. So it's safe? I had accidentally erased my stock rom cause I wiped that slot by mistake. So what's the procedure? Wipe the stock slot then install the rom on it then reboot? And how would I go about getting the stock back by clearing it again and installing the back up on the same slot? Please enlighten us cause I already got stuck on the black galaxy screen losing the safestrap and I had to odin the stock tar again.
I'm on NB1 4.4.2 and off course SS 3.72 beta. Thanks.
Wanabedev83 said:
Hmm I've been wondering this since I've not had success in doing so either. So what your saying is that it HAS to be done on STOCK slot in order for the rom to work? I've been scratching my head to why it refused to work for me. So it's safe? I had accidentally erased my stock rom cause I wiped that slot by mistake. So what's the procedure? Wipe the stock slot then install the rom on it then reboot? And how would I go about getting the stock back by clearing it again and installing the back up on the same slot? Please enlighten us cause I already got stuck on the black galaxy screen losing the safestrap and I had to odin the stock tar again.
I'm on NB1 4.4.2 and off course SS 3.72 beta. Thanks.
Click to expand...
Click to collapse
Not really sure how 'safe' it is. What I did was use safe strap to create rom slot 1 and installed the rom there. It didn't work so I just went back and installed the rom in the 'stock' slot the same way - wiping first. that worked.
before I did anything, I did a full backup in safestrap. I backed up to my SD card. I'm glad I did because the rom I installed - hyperdrive - did a couple things I didn't like so I was able to reboot to recover(safestrap) and restore my backup to the stock slot. now I am back the way I Was before I messed around.
I'm still looking at other roms but I feel good I Was able to restore the backup.
here are the steps I took (I'm a noob, this may not be perfect)
1) boot to recovery in safestrap
2) make sure 'stock' is active - this means that the 'install button' is red
3) perform advanced wipe on stock slot - all but external sd card
4) press 'install' and install the rom
5) exit installer and then install NC1 ATT module
6) then install SU module
7) reboot - all is good
Awesome!
burgertime78 said:
Not really sure how 'safe' it is. What I did was use safe strap to create rom slot 1 and installed the rom there. It didn't work so I just went back and installed the rom in the 'stock' slot the same way - wiping first. that worked.
before I did anything, I did a full backup in safestrap. I backed up to my SD card. I'm glad I did because the rom I installed - hyperdrive - did a couple things I didn't like so I was able to reboot to recover(safestrap) and restore my backup to the stock slot. now I am back the way I Was before I messed around.
I'm still looking at other roms but I feel good I Was able to restore the backup.
here are the steps I took (I'm a noob, this may not be perfect)
1) boot to recovery in safestrap
2) make sure 'stock' is active - this means that the 'install button' is red
3) perform advanced wipe on stock slot - all but external sd card
4) press 'install' and install the rom
5) exit installer and then install NC1 ATT module
6) then install SU module
7) reboot - all is good
Click to expand...
Click to collapse
Holy freaking crap dude thanks! I had feeling that was the way to do it. Thanks allot man, I'm currently organizing the folders, widgets and what not so i don't have to do it again if anything. I'll venture into it tomorrow. Again thanks! You answered a long awaited question.
Just tried a tmobile rom using a "SuperSU-v1.93.Zip" and got caught in a bootloop on the set up screen and even after on the main screen. Is that the same zip you used? If not can you link me? I wonder what the hell or if anyone else has been successful with a Damn tmobile rom, i used (the warp drive rom and 2 others on the list). God it was so cool when i saw the tmobile boot screen, ugh. And to make matters worse i found out that i have a faulty motherboard with the (no Sim, phone will reboot message). Damn I'm loving this stuff, just been running into some bad luck.