Related
So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?
I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app
iamdofus said:
I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.
Do you by chance have a refurbished s2?
The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?
es0tericcha0s said:
The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?
Click to expand...
Click to collapse
OK thanks for reply, I have one more solution give me. Some time I will give try that it worked for me.
Sent from my SGH-T989 using XDA Premium 4 mobile app
es0tericcha0s said:
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.
Click to expand...
Click to collapse
ok lets stat it with this
1) download both the scripts of infamous wipe cache and infamous super wipe.
2) format your both SD card with PC (FAT32)
2) put both these wipe files and and your rom file ( i prefer try slimbean rom first)
3) Now in twrp 2.6.0.0- follow the steps
i) format your phone with twrp options
ii) again format your phone with infamous super file. (by going in to INSTALL ZIP file option in TWRP)
iii) than format with infamouse cache file (by going in to INSTALL ZIP file option in TWRP)
iv) install your rom and compatiable GAPPS zip file.
v) after installing or somewhere between procedure if twrp says something about supersu birnaries are not correct than click on DO . NOT FIX
vi) again format infamouse cache wipe.
vii) now FINALLY reboot the rom.
it should work, and it worked for me. if u sucessfully run the rom than you can eailsy run all the AOSP roms in this forum. Again If you try this please do tell me what happend.
Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!
es0tericcha0s said:
So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?
Click to expand...
Click to collapse
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?
UltimaniumX said:
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?
Click to expand...
Click to collapse
Yep, very much phone specific. Used same recovery, same rom zip and gapps off the same external SD card, to be certain. That one updated just like every other S2 I've done. And it's the Tmo version. The At&t models are i777 S2 or i727 S2 Skyrocket. The i9100 is international and has a physical home button. But the phone was not modified at all. No root, custom recovery, etc. I was only able to resolve it by first starting with an AOSP 4.1.2 rom and working my way up to 4.4. One of the weirder issues I've come across.
es0tericcha0s said:
Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!
Click to expand...
Click to collapse
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?
tpag02 said:
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?
Click to expand...
Click to collapse
Sorry, I don't pay attention to the notifications on XDA very often. I don't usually browse the S2 forums unless needed because I have an N5, but anyway... The 4.1.2 rom you used, was it TW or AOSP type? I used 2.6.0 to wipe everything, then used cache and superwipe zips then 4.1.2 AOSP type rom then cache wipe zip again then after that booted, I was able to go back to 2.6.1 and flash a 4.3 via wiping, wipe zips, installing rom then cache wipe again. After that, repeated with a KK rom and now it loads roms just like it should. If you want more precise help, feel free to hit me up on Hangouts with my username: es0tericcha0s. Good luck! I know how frustrating it can be when it gets a little out of whack like this...
I'm in the same boat
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.
DennyTek said:
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.
Click to expand...
Click to collapse
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?
TMO 4.1.2
es0tericcha0s said:
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?
Click to expand...
Click to collapse
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
yep
wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
ya, well at least I am anyways
wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I had tried with and without and did not make any difference.
DennyTek said:
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/
Click to expand...
Click to collapse
I just started working on a VZW S3 on T-Mobile service that has this issue. Happens on stock VZW 4.1.2, stock T-Mobile 4.1.2 rom, custom 4.1.2 T-Mobile rom, and stable CM 10.2. Weirdest thing... full wipes including /system inbetween each flash. Changed the modem too. Nothing helps. Pretty sure it's a bad board at this stage.
Cool beans, 0! Having this exact problem, will try your method for my s2, btw which aosp 4.1.2 did u use? Can I get a link? Thanks been having the problem for a few months now and just gave up haha, been super thirsty for that beanstalk kk build
One last thing can u also provide a link to the 4.3 that u used? I really want it to work and want to follow what u did to the , megabyte
Since I just created an account here, I cannot post this as a reply on its rightful thread, but hopefully someone will see my question here.
I have used many different ROMS, and I had just installed GOOGLE EDITION 4.4.2 BY Danvdh, Kryten2k35 & Ktoonsez (http://forum.xda-developers.com/showthread.php?t=2539361) after installing this ROM, I quickly realized my phone showed I had no service, even in areas where I know I did.
I then tried to install the Wicked v10 ROM, as I have heard many good things about it. However, After running the Aroma installer, I was unable to boot into the Wicked ROM. My S$ just kept booting into the Googe Edition Rom.
tl;dr: After running the Aroma installer succsesfully, my S4 boots into my old ROM ( GOOGLE EDITION 4.4.2 BY Danvdh) and does not boot in into the Wicked v10 ROM.
Did you performed a FULL wipe?
☞ Sent from here ☜
baseballfanz said:
Did you performed a FULL wipe?
☞ Sent from here ☜
Click to expand...
Click to collapse
Not the internal sd, but I usually never have to, also the Aroma installer has a wipe function.
spmiller said:
Since I just created an account here, I cannot post this as a reply on its rightful thread, but hopefully someone will see my question here.
I have used many different ROMS, and I had just installed GOOGLE EDITION 4.4.2 BY Danvdh, Kryten2k35 & Ktoonsez (http://forum.xda-developers.com/showthread.php?t=2539361) after installing this ROM, I quickly realized my phone showed I had no service, even in areas where I know I did.
I then tried to install the Wicked v10 ROM, as I have heard many good things about it. However, After running the Aroma installer, I was unable to boot into the Wicked ROM. My S$ just kept booting into the Googe Edition Rom.
tl;dr: After running the Aroma installer succsesfully, my S4 boots into my old ROM ( GOOGLE EDITION 4.4.2 BY Danvdh) and does not boot in into the Wicked v10 ROM.
Click to expand...
Click to collapse
What recovery are you using? Is it the most recent version of that recovery?
Skipjacks said:
What recovery are you using? Is it the most recent version of that recovery?
Click to expand...
Click to collapse
CWM Touch Req0very v1.0.3.3
I have no clue if its the most recent
spmiller said:
CWM Touch Req0very v1.0.3.3
I have no clue if its the most recent
Click to expand...
Click to collapse
I've had lots of issues with TWRP recovery, I would get bootloops with the 4.4 roms and typically the only solution was to downgrade to one of my old backups. I've switched to CWM with no issues but don't use the touch version, you may want to install the non touch recovery just to eliminate that as a potential cause of the problem. Regardless make sure you're on the most current recovery rev.
spmiller said:
Since I just created an account here, I cannot post this as a reply on its rightful thread, but hopefully someone will see my question here.
I have used many different ROMS, and I had just installed GOOGLE EDITION 4.4.2 BY Danvdh, Kryten2k35 & Ktoonsez (http://forum.xda-developers.com/showthread.php?t=2539361) after installing this ROM, I quickly realized my phone showed I had no service, even in areas where I know I did.
I then tried to install the Wicked v10 ROM, as I have heard many good things about it. However, After running the Aroma installer, I was unable to boot into the Wicked ROM. My S$ just kept booting into the Googe Edition Rom.
tl;dr: After running the Aroma installer succsesfully, my S4 boots into my old ROM ( GOOGLE EDITION 4.4.2 BY Danvdh) and does not boot in into the Wicked v10 ROM.
Click to expand...
Click to collapse
Are you certain you are flashing Wicked? Maybe you selected the wrong Rom to flash. I asked that for two reasons. 1) If you flash Rom A, it cannot boot to Rom B. 2) I don't remember the Wicked v10 aroma having any wipe features. I could be wrong on number 2 because it's been a while since I ran Wicked.
Tapatalk Pro 4 - GS4(M919)
?dbombRom is dbestRom?
phrotac said:
Are you certain you are flashing Wicked? Maybe you selected the wrong Rom to flash. I asked that for two reasons. 1) If you flash Rom A, it cannot boot to Rom B. 2) I don't remember the Wicked v10 aroma having any wipe features. I could be wrong on number 2 because it's been a while since I ran Wicked.
Tapatalk Pro 4 - GS4(M919)
?dbombRom is dbestRom?
Click to expand...
Click to collapse
No I'm flashing Wicked
Sent from my SGH-M919 using Tapatalk
spmiller said:
Since I just created an account here, I cannot post this as a reply on its rightful thread, but hopefully someone will see my question here.
I have used many different ROMS, and I had just installed GOOGLE EDITION 4.4.2 BY Danvdh, Kryten2k35 & Ktoonsez (http://forum.xda-developers.com/showthread.php?t=2539361) after installing this ROM, I quickly realized my phone showed I had no service, even in areas where I know I did.
I then tried to install the Wicked v10 ROM, as I have heard many good things about it. However, After running the Aroma installer, I was unable to boot into the Wicked ROM. My S$ just kept booting into the Googe Edition Rom.
tl;dr: After running the Aroma installer succsesfully, my S4 boots into my old ROM ( GOOGLE EDITION 4.4.2 BY Danvdh) and does not boot in into the Wicked v10 ROM.
Click to expand...
Click to collapse
No service? You flashed the modem through odin before flashing a custom rom through recovery right?
Did you by any chance flash a dual boot patcher? If you went through aroma successfully when you flashed wicked and booted into Aosp when done, it sounds like dual boot. From what I understand you have to have a TW ROM as the primary ROM or you may have issues. There's a ROM switcher app here http://forum.xda-developers.com/showthread.php?t=2447534 this is just a suggestion. I'm not assuming you actually installed dual boot but it's worth the try. Good luck!!
Sent from my SGH-M919 using xda app-developers app
mrzhadow said:
Did you by any chance flash a dual boot patcher? If you went through aroma successfully when you flashed wicked and booted into Aosp when done, it sounds like dual boot. From what I understand you have to have a TW ROM as the primary ROM or you may have issues. There's a ROM switcher app here http://forum.xda-developers.com/showthread.php?t=2447534 this is just a suggestion. I'm not assuming you actually installed dual boot but it's worth the try. Good luck!!
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I have installed the Liquidsmooth ROM instead of Wicked and I like it a lot, so I don't think I'll make an attempt to switch.
Sent from my SGH-M919 using Tapatalk
Have a N7105T on stock 4.1 + root + Philz Touch CWM, and am having trouble flash ROM's other than HashCheck (4.1).
Have tried PACMAN all-in-one (4.3) and Omni (4.4) as both 'N7100' and 't0lte' variants, with similar results for both.
The N7100 variants install but mobile not recognised.
The t0lte variants refuse to install. From what I can tell, it is failing to assert it is on a N7105T. EDIT: The Omni 4.4 ROM reports that I am 't03g'.
My process in each of these cases has been to perfom the installs from recovery: wipe/factory reset (clean for ROM), install zip, install google apps, wipe cache, wipe dalvik, boot to rom. I have an IMEI backup using the QPST tool.
I'm not touching modems at this stage. Also haven't run a stock 4.3 rom yet.
Others are obviously on 4.3/4.4 custom ROM's. I've been scouring xda for help but can't find the relevant advice. What am I doing wrong?
EDIT: after seeing the Omni assert failure reporting 't03g' it now appears 't03g' matches the N7100, but I definitely have a N7105T. Refer: link autoroot.chainfire.eu and teamw.in/project/twrp2/115 where t03g is N7100 variant. As the t0lte ROM variants are aborting due to failing their asserts to identify my phone, is this a ROM build problem? Can't ask this in the dev section because despite being a 3 year member, haven't needed to post before. Can anyone suggest what info I could get from my phone that may be used by the ROM's to identify my phone?
SOLVED: PACMAN and OMNI ROM's hardware assertions for t0lte not including my N7105
norkle said:
Have a N7105T on stock 4.1 + root + Philz Touch CWM, and am having trouble flash ROM's other than HashCheck (4.1).
Have tried PACMAN all-in-one (4.3) and Omni (4.4) as both 'N7100' and 't0lte' variants, with similar results for both.
The N7100 variants install but mobile not recognised.
The t0lte variants refuse to install. From what I can tell, it is failing to assert it is on a N7105T. EDIT: The Omni 4.4 ROM reports that I am 't03g'.
Click to expand...
Click to collapse
Well it would appear the t0lte ROMs failing install at the assertion were the clue. The Omni ROM provided helpful information by advising I had a t03g (N7100) leading me to guess it wasn't detecting correctly.
Went into the Omni t0lte nightly ROM and modified the update-script to include 't03g' in the assertions (note: this is dangerous - t03g is normally the non-LTE N7100's) and installed using PhilzTouch recovery (with gapps and own modem). Modem and WiFi working beautifully, baseband being correctly detected etc. For anyone copying me, remember I had used the QPST to make an IMEI backup and am comfortable working with Odin/recovery etc.
Now, can anyone point me in the right direction to helping identify why my phone variant was failing the assertions, and who I should contact to update ROM's? I presume they are working on something common upstream, eg. CM.
another post
156 views and no input. A guy could feel like a ghost around here.
29445236
I would really appreciate some input on this. Anyone know the likely point of call for fixes in identifying N7105T vs N7105/N7100?
Finally worked out the problem was a N7100 recovery on a N7105 device. Updated recovery, worked and installed ROM, all better.
Info in case others make the same mistake.
am I able to flash this StockMOD Custom ROM 4.3 RLS2.1 for att or tmobile, over my existing stock 4.4.2, my modem as of now is i747UCUFNE4 but the rom description says to flash the 4.3 modem or it wont get data? someone help me out
heres the rom url http://forum.xda-developers.com/showthread.php?t=2504903
do not flash the older modem. just flash the rom and youll be good to go.
DocHoliday77 said:
do not flash the older modem. just flash the rom and youll be good to go.
Click to expand...
Click to collapse
since im coming from stock 4.4.2 do I only wipe cache n dalvik before flashing
You will most likely have to factory reset since you are downgrading.
You can try just wiping dalvik, but if it hangs at boot youll have to factory reset.
one more question
DocHoliday77 said:
You will most likely have to factory reset since you are downgrading.
You can try just wiping dalvik, but if it hangs at boot youll have to factory reset.
Click to expand...
Click to collapse
Thank You I tried wiping cache n dalvik, it hung but I went back in to twrp n wiped cache n dalvik again after install, worked like a charm!!!!!
hank you very much but can you answer me one question is there anyway you or another could port the revolutionary s5 v3 to the i747 it looks so amazing they only have it for the s3 i9300 not the s3 i747
Afaik, porting from tbe i9300 is a pretty difficult process. The device is very different from ours. Not saying it isnt possible, but I dont think we've really ever had any ports from that device.
I wont be able to try as I just have too much on my plate already and not enough time as it is. Sorry....maybe someone else will tackle it....
DocHoliday77 said:
Afaik, porting from tbe i9300 is a pretty difficult process. The device is very different from ours. Not saying it isnt possible, but I dont think we've really ever had any ports from that device.
I wont be able to try as I just have too much on my plate already and not enough time as it is. Sorry....maybe someone else will tackle it....
Click to expand...
Click to collapse
well thank you very much for responding you've been a very patient n helping hand if you could maybe you could pass it around to some of the other developers you are in contact with I know of about 30 people personally that would love to have that on there i747 not counting the people ive seen on here asking for a rom from the s5 but no big deal THANKS AGAIN
I was watching this thread because I had the exact same question. I tried installing the "StockMOD Custom ROM 4.3 RLS2.1" and my S3 wouldn't even boot past the Samsung screen. I left it there for 15 minutes and nothing. I tried wiping dalvik/cache from recovery and then it wouldn't even get that far. From that point on when I tried to reinstall the ROM it would go by and then when it got to the rebooting stage it would tell me "No OS installed. Are you sure you want to reboot?", or something of that nature. I then installed the Deodex Debloat Version from here: http://forum.xda-developers.com/showthread.php?t=2540998 and it installed/booted on the first try. Only problem is that Wi-Fi does not work & not sure of what my next step should be to get Wi-Fi working. I came from 4.4.2 OTA. Should I install the 4.3 modem or try flashing the StockMOD Rom again? I'm confused because it was stated that it didn't need to be installed.
Edit: I installed the StockMOD ROM directly over top without wiping anything and it worked. If I just want the "Deodex Debloat" version should I wipe, reinstall that ROM, then install the 4.3 modem since it didn't work before?
Edit: Second time flashing the Deodex Debloat ROM & Wi-Fi is working but now I have no data/4G. Help! LoL.
plastic_green_head said:
I was watching this thread because I had the exact same question. I tried installing the "StockMOD Custom ROM 4.3 RLS2.1" and my S3 wouldn't even boot past the Samsung screen. I left it there for 15 minutes and nothing. I tried wiping dalvik/cache from recovery and then it wouldn't even get that far. From that point on when I tried to reinstall the ROM it would go by and then when it got to the rebooting stage it would tell me "No OS installed. Are you sure you want to reboot?", or something of that nature. I then installed the Deodex Debloat Version from here: http://forum.xda-developers.com/showthread.php?t=2540998 and it installed/booted on the first try. Only problem is that Wi-Fi does not work & not sure of what my next step should be to get Wi-Fi working. I came from 4.4.2 OTA. Should I install the 4.3 modem or try flashing the StockMOD Rom again? I'm confused because it was stated that it didn't need to be installed.
Edit: I installed the StockMOD ROM directly over top without wiping anything and it worked. If I just want the "Deodex Debloat" version should I wipe, reinstall that ROM, then install the 4.3 modem since it didn't work before?
Edit: Second time flashing the Deodex Debloat ROM & Wi-Fi is working but now I have no data/4G. Help! LoL.
Click to expand...
Click to collapse
if you flashed it without wiping cache n dalvik- dirty flash then it should have worked unless u came from another 4.4.2 rom mine is working fine
correct me if im wrong
If ypu updated to 4.4.2, and then flashed a 4.3 rom, you have to use either the MJ2 or kt747 kernel or wifi wont work.
DocHoliday77 said:
If ypu updated to 4.4.2, and then flashed a 4.3 rom, you have to use either the MJ2 or kt747 kernel or wifi wont work.
Click to expand...
Click to collapse
that's not entirely true im not using either n my wifi is fine im on
kernel 3.0.31.1804024
[email protected]#1
i upgraded ota to 4.4.2 n never flashed any kernel at all
DocHoliday77 said:
If ypu updated to 4.4.2, and then flashed a 4.3 rom, you have to use either the MJ2 or kt747 kernel or wifi wont work.
Click to expand...
Click to collapse
Why exactly will it not work to flash a MJB kernel?
Boston78 said:
that's not entirely true im not using either n my wifi is fine im on
kernel 3.0.31.1804024
[email protected]#1
i upgraded ota to 4.4.2 n never flashed any kernel at all
Click to expand...
Click to collapse
I would get either no wifi or no data depending on which modem was used after flashing the rom.
01 - Via TWRP (2.7.1.0) dirty flash d2att_4.3_MJB_Debloat_Deodex_v1.2.zip
02 - Reboot without wiping cache/dalvik = freeze at AT&T logo
03 - Wipe cache/dalvik = freeze at AT&T logo
04 - Factory Reset = success with the exception of no wifi
05 - Flash MJB modem = Wifi now enabled but no data. (baseband unknown/imei null)
06 - Flash NE4 modem = data/baseband/imei restored, but no wifi again
07 - Flash UCUEMJ2_Insecure_kernel.zip + wipe cache/dalvik & reboot = somplete succcess (wifi+data all working)
At least for my experience Doc is 100% correct. Not sure how you were able to flash the StockMOD ROM without having to flash a kernel. Especially when "How to flash" on the StockMOD page says "5. Flash Kernel (For WiFi)". Not saying you are lying, just that I don't understand why you didn't need to.
Boston78 said:
that's not entirely true im not using either n my wifi is fine im on
kernel 3.0.31.1804024
[email protected]#1
i upgraded ota to 4.4.2 n never flashed any kernel at all
Click to expand...
Click to collapse
Are you using this rom along with the included kernel? Or something different?
plastic_green_head said:
Why exactly will it not work to flash a MJB kernel?
I would get either no wifi or no data depending on which modem was used after flashing the rom.
01 - Via TWRP (2.7.1.0) dirty flash d2att_4.3_MJB_Debloat_Deodex_v1.2.zip
02 - Reboot without wiping cache/dalvik = freeze at AT&T logo
03 - Wipe cache/dalvik = freeze at AT&T logo
04 - Factory Reset = success with the exception of no wifi
05 - Flash MJB modem = Wifi now enabled but no data. (baseband unknown/imei null)
06 - Flash NE4 modem = data/baseband/imei restored, but no wifi again
07 - Flash UCUEMJ2_Insecure_kernel.zip + wipe cache/dalvik & reboot = somplete succcess (wifi+data all working)
At least for my experience Doc is 100% correct. Not sure how you were able to flash the StockMOD ROM without having to flash a kernel. Especially when "How to flash" on the StockMOD page says "5. Flash Kernel (For WiFi)". Not saying you are lying, just that I don't understand why you didn't need to.
Click to expand...
Click to collapse
As for why, starting in 4.3 (MJB) samsung moved the modules required for wifi to work. They are now included in a different partition. Custom kernels (or rather any kernel but the original stock) look for the modules (drivers) to be in /system/lib/modules (the location on earlier builds). Since they are not there, the system doesnt know how to use the wifi radio resulting in no working wifi.
We got lucky with the MJ2 kernel. It was the first 4.3 leak, and just by chance I tried it on a different leak (for the T999) while trying to figure out the wifi issue and it worked! They simply had not made the change in that test build. Pure luck! The kt747 kernel works because it was built from source and modified to use its own modules which are included in the kernel package.
It has been a good while, so as for where the modules are located now im not suren. But if you browse to /system/lib/modules and find wlan.ko, youll see it is symlinked to /system/lib/modules/prima/prima_wlan.ko. Youll also notice there is no prima folder or file. In older builds, the wlan.ko file was actually there.
Hope that made sense and hope I got most of it correct. (Going from memory)
DocHoliday77 said:
Are you using this rom along with the included kernel? Or something different?
As for why, starting in 4.3 (MJB) samsung moved the modules required for wifi to work. They are now included in a different partition. Custom kernels (or rather any kernel but the original stock) look for the modules (drivers) to be in /system/lib/modules (the location on earlier builds). Since they are not there, the system doesnt know how to use the wifi radio resulting in no working wifi.
We got lucky with the MJ2 kernel. It was the first 4.3 leak, and just by chance I tried it on a different leak (for the T999) while trying to figure out the wifi issue and it worked! They simply had not made the change in that test build. Pure luck! The kt747 kernel works because it was built from source and modified to use its own modules which are included in the kernel package.
It has been a good while, so as for where the modules are located now im not suren. But if you browse to /system/lib/modules and find wlan.ko, youll see it is symlinked to /system/lib/modules/prima/prima_wlan.ko. Youll also notice there is no prima folder or file. In older builds, the wlan.ko file was actually there.
Hope that made sense and hope I got most of it correct. (Going from memory)
Click to expand...
Click to collapse
whatever kernel that was built into the rom is what im on I listed it in my reply before, I haven't flashed anything else ONLY THE ROM, mine booted right up n works great,
The more I think about it, it makes sense to me in both situations.
Id expect it to work on 4 4.2 because the wifi drivers are still in the same location, so as long as youre on 4.3 or above, it should work, as it apoears to do for you. But there are ithers who it did not work for and they have to use one of those other kernels. So it could be newer drivers not being compatible. Either way, if wifi is not working, I do know the kernel change will fix it.
DocHoliday77 said:
The more I think about it, it makes sense to me in both situations.
Id expect it to work on 4 4.2 because the wifi drivers are still in the same location, so as long as youre on 4.3 or above, it should work, as it apoears to do for you. But there are ithers who it did not work for and they have to use one of those other kernels. So it could be newer drivers not being compatible. Either way, if wifi is not working, I do know the kernel change will fix it.
Click to expand...
Click to collapse
well I have a twrp backup of it on my phone if you have some way of opening it, maybe somehow I could send it to you n whatever you find may be a tremendous help to you in how to fix the wifi n not having to flash the other kernels
I dont think there would be anything in a nandroid backup that would help. But tbh, right now I have no intention of digging into it any further. First because we already do have a pretty simple solution, and second because im already swamped with other projects and problems I've promised others I would work on.
I've been trying for over a month to get wicked rom installed on my n3 n900t . I'm rooted bootloader unlocked with twrp installed. I've had no issue installing any other rom on this phone I'm currently running alliance 5.0 and resurrection remix 6.0.1 and they work great but I would like to see what wicked is like. ( what it does when trying to install ) OK I have the wicked rom saved to my SD card with 4.4.2 gapps I'll restore my phone to alliance rom which is 4.4.2 and is says in the install it needs to be a 4.4.2 bootloader to install wicked, I'll go into twrp do a full wipe data, delvic,system, wipe it out then install the ROM and gapps package and it'll start to do its thing then get to where it says aramullz xda ( something? ) the progress bar will stop and it'll self boot itself out of twrp and go back to alliance rom and which will be messed up due to doing a full wipe. I like to figure things out on my own that's the fun part but this one's got me. Thanks for any advice.
Did you use terminal or Samsung Phone Info app to verify the bootloader in the phone?
I installed compullsion kernel 4.4.2 before and that failed, tried installing it while flashing the rom and gapps that failed, tried the other older versions of wicked v5 and v4 and v1 they all act exactly the same. I even wiped the whole phone completely cause I got Pissed due to failure ( lol ) flashed a fresh AP in Odin and tried everything again and still failed. I'm in the process of trying to convert the zip file to a tar md5 but having issues that Odin won't except the files cause the ( tar archived ) and I did flash the 4.4.2 bootloader as well. I'm beginning to think wicked doesn't like me.
My bootloader info should be 4.4.2
fastjohnson said:
this the info now which is useless because I'm on alliance 5.0 rom so it originally came from 4.4.2 chainfire zip.
Click to expand...
Click to collapse
Yes, looks like the phone is on 4.4.2 bootloader. Were you able to install the ROM?
audit13 said:
Yes, looks like the phone is on 4.4.2 bootloader. Were you able to install the ROM?
Click to expand...
Click to collapse
No still nothing I've tried everything I even wiped the entire phone installed the B4 Odin files AP and BL and CSC then flash chain fires autoroot file and twrp. The phone was basically stock 4.4.2. I tried all 3 wicked zips V1 V4 V5 and they all reacted the same way. And I already grabbed these files from different locations to make sure I didn't possibly get a bad batch. I've got every rom to flash on this no problem. Pacman, RR, alliance, slimroms, any cyan rom, I've come to terms no wicked for me. Lol
Lol, finally got wicked installed via flashfire. Twrp wouldn't do it. Super happy really fast rom.
What versions of twrp did you try? Just curious.
Using the newest 3.0.2 I think. Btw wicked rom so far is the most stable coolest rom I've experienced so far. I forsee it as my daily.
I have seen reports of some people having issues with 3.0 and higher so I stick with 2.87 for my devices.
No I actually didn't catch that. Besides that it refusing to install the wicked rom I haven't seen very many other issues. Well sometimes when im restoring a rom in twrp when it boots itll sometimes not in stall a lot of Google Play stuff and the UI will crash and I'll have to restore it again. I actually like the look and the button placement better in the version your using.