[Q] ***Wicked ROM v10 Not Installing/Booting*** - T-Mobile Samsung Galaxy S 4

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

Related

trouble installing hyperdrive rom

hy everybody , i have been trying to install hyperdrive rom rl10 on mt at&t galaxy s3 i have follow every step ,fix, i even flash kt747 kernel and nothing i'm still stuck on boot it won't pass the first boot animation , i also flash xone kernel and still the same it will get stuck on first animation boot even after 7 minutes it wont do anything.:crying:
angeltouch 4g said:
hy everybody , i have been trying to install hyperdrive rom rl10 on mt at&t galaxy s3 i have follow every step ,fix, i even flash kt747 kernel and nothing i'm still stuck on boot it won't pass the first boot animation , i also flash xone kernel and still the same it will get stuck on first animation boot even after 7 minutes it wont do anything.:crying:
Click to expand...
Click to collapse
What model do you have? Carrier? What option did you first choose for a kernel?
You're like the 50th user in here this week with this issue on hyperdrive. It would appear the device type in the build.prop is being is being edited and there is a conflict during the boot process causing this soft brick. Anyone with more knowledge than this please chime in.
If you can still get back into recovery, your options are probably to restore a backup or flash another rom. In download mode you could flash stock stock rooted via odin. If your s3 is not recognized on your pc, there is a flashable stock firmware zip in the link in my signature. In post #2 at the bottom
xBeerdroiDx said:
What model do you have? Carrier? What option did you first choose for a kernel?
You're like the 50th user in here this week with this issue on hyperdrive. It would appear the device type in the build.prop is being is being edited and there is a conflict during the boot process causing this soft brick. Anyone with more knowledge than this please chime in.
If you can still get back into recovery, your options are probably to restore a backup or flash another rom. In download mode you could flash stock stock rooted via odin. If your s3 is not recognized on your pc, there is a flashable stock firmware zip in the link in my signature. In post #2 at the bottom
Click to expand...
Click to collapse
hi beerdroid i have at&t sgh-i747
i choose the ziggy kernel in aroma thats the only option for at&t , i did try with the verizon with the zeus kernel,deviant kernel, and stock kernel all with no luck , yea i seen a lots of users with the same problem , yes i can still pull out the battery and do the process again with a different kernel , i have try kt747 kernel ,xone kernel and devil's reject kernel all with no luck , phone will boot but it will get stock on first animation boot , and i have no clue when you say build.prop
angeltouch 4g said:
hi beerdroid i have at&t sgh-i747
i choose the ziggy kernel in aroma thats the only option for at&t , i did try with the verizon with the zeus kernel,deviant kernel, and stock kernel all with no luck , yea i seen a lots of users with the same problem , yes i can still pull out the battery and do the process again with a different kernel , i have try kt747 kernel ,xone kernel and devil's reject kernel all with no luck , phone will boot but it will get stock on first animation boot , and i have no clue when you say build.prop
Click to expand...
Click to collapse
i'm trying to do is installing the rls 9 and then update see if this help
So the very first time you flashed hyperdrive, you selected at&t and the ziggy kernel and it didn't work? I'm assuming you gave it plenty of time on the first boot up. Someone correct me if I'm wrong but hyperdrive is a verizon base, yes? If so, this might be the source of your problem, even though it is a "multi-carrier" rom. You can try wiping data, cache and dalvik in recovery then rebooting. Like i said, though, you will probably have to another route (restore backup or flash new rom). When you successfully boot up next, I would imagine your model is different in about phone
xBeerdroiDx said:
So the very first time you flashed hyperdrive, you selected at&t and the ziggy kernel and it didn't work? I'm assuming you gave it plenty of time on the first boot up. Someone correct me if I'm wrong but hyperdrive is a verizon base, yes? If so, this might be the source of your problem, even though it is a "multi-carrier" rom. You can try wiping data, cache and dalvik in recovery then rebooting. Like i said, though, you will probably have to another route (restore backup or flash new rom). When you successfully boot up next, I would imagine your model is different in about phone
Click to expand...
Click to collapse
i'm trying to do whay tou are saying but this aroma installer keeps freezing is driving me nuts
angeltouch 4g said:
i'm trying to do whay tou are saying but this aroma installer keeps freezing is driving me nuts
Click to expand...
Click to collapse
Are you using twrp or cwm for recovery? Twrp is recommended for aroma
xBeerdroiDx said:
Are you using twrp or cwm for recovery? Twrp is recommended for aroma
Click to expand...
Click to collapse
cwm
angeltouch 4g said:
cwm
Click to expand...
Click to collapse
If you're really wanting to get this particular rom going, changing to twrp might help. In my signature there is a link. Near the bottom of post #2 flashable recovery zips are mentioned. Download the twrp one and throw it on your phone. Boot into recovery and flash it. Reboot recovery. Wipe data, cache and try flashing the rom again.
xBeerdroiDx said:
If you're really wanting to get this particular rom going, changing to twrp might help. In my signature there is a link. Near the bottom of post #2 flashable recovery zips are mentioned. Download the twrp one and throw it on your phone. Boot into recovery and flash it. Reboot recovery. Wipe data, cache and try flashing the rom again.
Click to expand...
Click to collapse
ok i'll do that to see if helps thanks
hrsema and
angeltouch 4g said:
ok i'll do that to see if helps thanks
Click to expand...
Click to collapse
now i got the boot animation hyperdrive sbreen94 how much you think i have to wait it looks like is stock?
angeltouch 4g said:
now i got the boot animation hyperdrive sbreen94 how much you think i have to wait it looks like is stock?
Click to expand...
Click to collapse
It could take 10 or so minutes for the initial boot. If it takes a lot longer, you can try booting back onto recovery to wipe data and cache again. If this does not work, I would go another route
xBeerdroiDx said:
It could take 10 or so minutes for the initial boot. If it takes a lot longer, you can try booting back onto recovery to wipe data and cache again. If this does not work, I would go another route
Click to expand...
Click to collapse
ok , if not i'll try to flash some other kernels to see if it boots up , i f not i'll just give up on this rom and go back to synergy
When you're back up and running on a rom, go into settings > about phone and tell me what your device is listed as. You may have small issues down the road if your phone has been designated as an SCH-I535 or anything other than SGH-I747. That's an easy build.prop fix, though. Good luck
xBeerdroiDx said:
When you're back up and running on a rom, go into settings > about phone and tell me what your device is listed as. You may have small issues down the road if your phone has been designated as an SCH-I535 or anything other than SGH-I747. That's an easy build.prop fix, though. Good luck
Click to expand...
Click to collapse
ok i'll do that and let you know
model number samsung-sgh-i747
baseband number i747ucdlk3
angeltouch 4g said:
model number samsung-sgh-i747
baseband number i747ucdlk3
Click to expand...
Click to collapse
Good. Congrats. What rom did you end up on?
synergy thats were i was before trying to flash hyperdrive
The upside: now you can post in development threads
ok

Stuck at boot ani screen on all AOSP roms

I don't know if someone already posted this, but searched and couldn't find the answer. I get stuck at boot screen all on AOSP 4.2.2 roms that I tried, but with any TW roms are fine (no problem at all). Can anyone help? I want to run AOSP rom. Thanks.
I think you may be using a touch wiz kernel
You can find some aosp kernels in the original development thread
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta
jinxzn said:
I don't know if someone already posted this, but searched and couldn't find the answer. I get stuck at boot screen all on AOSP 4.2.2 roms that I tried, but with any TW roms are fine (no problem at all). Can anyone help? I want to run AOSP rom. Thanks.
Click to expand...
Click to collapse
which rom did you flash, and what did you flash?
the rom only?
the rom and GAAPS?
The rom and kernel?
you need to provide more details if you want to be helped..
Zachinater said:
I think you may be using a touch wiz kernel
You can find some aosp kernels in the original development thread
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I did flashed SOAPKernel along with aosp roms.
wase4711 said:
which rom did you flash, and what did you flash?
the rom only?
the rom and GAAPS?
The rom and kernel?
you need to provide more details if you want to be helped..
Click to expand...
Click to collapse
I flashed BeanStalk, SlimBean, CyanogenMod 10.1 official nightlies, FSC rom, and IllusionRom.
I have CWM Philz_Touch 5.07.1. Every time install a new rom, I wiped Caches + Data / Factory Reset 2x.
I flashed rom only, then flashed rom and GAPPS, those 2 didn't work, I even tried rom w/ SOAPKernel and still didn't work.
ok, you should try switching to TWRP, since most of the time people have zero issues flashing AOSP roms with TWRP.
Also, after all your wipes, flash the rom and GAAPS in the same session, and reboot..
I've done this exact procedure for years, and it works for me 99.98% of the time..
wase4711 said:
ok, you should try switching to TWRP, since most of the time people have zero issues flashing AOSP roms with TWRP.
Also, after all your wipes, flash the rom and GAAPS in the same session, and reboot..
I've done this exact procedure for years, and it works for me 99.98% of the time..
Click to expand...
Click to collapse
Switched to TWRP, and did all the wipes, install rom and GAAPS. Same thing.
Planning to flash stock rom, and redo all the root/recovery procedures all over again. Do you think I should do that?
it couldnt hurt...
some phones are just tempremental; do you have an SD card in your phone?
are you installing from the sd card or internal memory?
try installing from one or the other to see if that helps; sometimes it does...
wase4711 said:
it couldnt hurt...
some phones are just tempremental; do you have an SD card in your phone?
are you installing from the sd card or internal memory?
try installing from one or the other to see if that helps; sometimes it does...
Click to expand...
Click to collapse
I did try both, none work for me.
Thank you so much for your help thou. I'll now just install stock rom and re-root it, see how it goes.
jinxzn said:
I did try both, none work for me.
Thank you so much for your help thou. I'll now just install stock rom and re-root it, see how it goes.
Click to expand...
Click to collapse
good luck, and post back if you get it working properly
flashed stock rom and rooted and installed boot recovery, after all that, it's still not let me install any AOSP roms. Really don't why I can only flash TW roms but not AOSP roms.

[Q] LiquidSmooth locks up daily - HELP !!!

My phone locks up almost daily and I have to remove the battery and then put it back in to get it going again.
This cant be normal...
I have TeamWin loaded onto it and have installed LiquidSmooth using this. I wiped the Cache, Dalvik, System at least three times before installing LiquidSmooth. I have tried installing it a few times with the same result.
Still, the phone locks up and it generally locks up while I am on a call. It generally doesnt lock up while using an app or browsing.
I am getting kind of sick and tired of removing the back cover and pulling the battery daily....
Any thoughts ?? Help !
INFO:
Phone: Samsung Galaxy S3, AT&T, SGH -I747
Android version 4.2.2
LiquidSmooth: liquid_d2att-userdebug 4.2.2 JDQ39 eng.liquid.20130403.222500 test-keys
LiquidSmooth Version Liquid - JB-v2.1-OFFICIAL
Kernel version: [email protected] #167
(I did try installing AOKP as well, and that gives me an error installing, so I couldnt even get that going - maybe these problems are related??)
Shane24 said:
My phone locks up almost daily and I have to remove the battery and then put it back in to get it going again.
This cant be normal...
I have TeamWin loaded onto it and have installed LiquidSmooth using this. I wiped the Cache, Dalvik, System at least three times before installing LiquidSmooth. I have tried installing it a few times with the same result.
Still, the phone locks up and it generally locks up while I am on a call. It generally doesnt lock up while using an app or browsing.
I am getting kind of sick and tired of removing the back cover and pulling the battery daily....
Any thoughts ?? Help !
INFO:
Phone: Samsung Galaxy S3, AT&T, SGH -I747
Android version 4.2.2
LiquidSmooth: liquid_d2att-userdebug 4.2.2 JDQ39 eng.liquid.20130403.222500 test-keys
LiquidSmooth Version Liquid - JB-v2.1-OFFICIAL
Kernel version: [email protected] #167
(I did try installing AOKP as well, and that gives me an error installing, so I couldnt even get that going - maybe these problems are related??)
Click to expand...
Click to collapse
Hey man,
My suggestion is to use Odin to flash the stock image back to stock and see if the problem persists. If it does, I'd take it back to at&t for a new phone (if you've had it less than a year or you have some sort of insurance plan.)
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
---------- Post added at 02:23 AM ---------- Previous post was at 02:18 AM ----------
If flashing back to stock fixes it, its user error. Make sure you're up to date on everything, I.e boot loader, recovery, everything. If that does nothing for you maybe try flashing the new version of CWM and see if it'll flash right that way.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Is it just me or is your lean kernel like years old? Isn't the newest version 7.2?
Same with your rom.. 2.9 is out?
Sent from my SGH-I747 using xda premium
Yes, the kernel could be old. I have never updated it... I hate to admit, but I have no idea what the kernel does actually or how to flash a new one.
I have installed the ROM, but not the kernel obviously....
Any info on what a kernel does? Can I flash it easily with TeamWin ?
I can definitely upgrade the ROM to the latest version of liquidSmooth
Shane24 said:
Yes, the kernel could be old. I have never updated it... I hate to admit, but I have no idea what the kernel does actually or how to flash a new one.
I have installed the ROM, but not the kernel obviously....
Any info on what a kernel does? Can I flash it easily with TeamWin ?
I can definitely upgrade the ROM to the latest version of liquidSmooth
Click to expand...
Click to collapse
Hey man,
If you're going to be flashing custom ROMs you should probably learn what a kernel is. Use the search feature or simply use google. In fact, the xda TV channel just put out a video on kernels this week on YouTube.
Anyways, as I said previously, make sure EVERYTHING is up to date. Including the ROM version. Dont worry about flashing kernels until you have a solid understanding of what they are. I'm almost positive that you are just flashing out of order. Just start from scratch, make sure EVERYTHING is up to date. Good luck.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
yup, I got up to speed on kernels. (Thanks for the suggestions as I didnt know about Kernels, but now I do...)
So, the plan is to
- wipe: dalvic, cache, etc... (3X)
- install the Bionic Sheep 4.2.2 Kernel
- install ROM (I'll try Hyperdrive and DeadlyVenom and LiquidSmooth again)
- install Google Apps...
I have TeamWin installed obviously.
Hopefully this will get my phone back on track...
Shane24 said:
yup, I got up to speed on kernels. (Thanks for the suggestions as I didnt know about Kernels, but now I do...)
So, the plan is to
- wipe: dalvic, cache, etc... (3X)
- install the Bionic Sheep 4.2.2 Kernel
- install ROM (I'll try Hyperdrive and DeadlyVenom and LiquidSmooth again)
- install Google Apps...
I have TeamWin installed obviously.
Hopefully this will get my phone back on track...
Click to expand...
Click to collapse
Hyperdrive and Deadly venom are touchwiz ROMs, u can't flash bionic sheep with them!!! And u don't need to flash gapps with tw ROMs either!!
Also, u need to flash a kernel after u flash the ROM, otherwise it will be overwritten by the stock kernel for whatever particular ROM u are flashing. I would suggest sticking with the stock kernel for a bit and see how it runs!
Shane24 said:
yup, I got up to speed on kernels. (Thanks for the suggestions as I didnt know about Kernels, but now I do...)
So, the plan is to
- wipe: dalvic, cache, etc... (3X)
- install the Bionic Sheep 4.2.2 Kernel
- install ROM (I'll try Hyperdrive and DeadlyVenom and LiquidSmooth again)
- install Google Apps...
I have TeamWin installed obviously.
Hopefully this will get my phone back on track...
Click to expand...
Click to collapse
What the guy above me said about TW roms is correct. Flashing the wrong kernel is not a good idea. Here's what I do on every flash
- wipe system, data, caches, etc.
- flash rom( and gapps if necessary)
- boot up rom and let it settle for 5 min, then boot back into recovery
-flash correct kernel for the rom's version(check kernel number in about device and custom kernels op), then wipe both caches and fix permissions.
-reboot and enjoy:laugh:
DMF1977 said:
Hyperdrive and Deadly venom are touchwiz ROMs, u can't flash bionic sheep with them!!! And u don't need to flash gapps with tw ROMs either!!
Also, u need to flash a kernel after u flash the ROM, otherwise it will be overwritten by the stock kernel for whatever particular ROM u are flashing. I would suggest sticking with the stock kernel for a bit and see how it runs!
Click to expand...
Click to collapse
Which Kernel would I need to use then for Touchwiz ROM's ???
And which kernel for LiquidSmooth and AOKP ??
Shane24 said:
Which Kernel would I need to use then for Touchwiz ROM's ???
And which kernel for LiquidSmooth and AOKP ??
Click to expand...
Click to collapse
Like I said, I would suggest sticking with the packaged kernel that comes with whatever ROM that you are going to flash, run it for a few days, after that if u still feel the need for something more, go with a custom kernel! Ktoonsez makes an excellent kernel, one for tw, and one for aosp, u just have to pick the right one according to which ROM you're running!! Good luck...
DMF1977 said:
Like I said, I would suggest sticking with the packaged kernel that comes with whatever ROM that you are going to flash, run it for a few days, after that if u still feel the need for something more, go with a custom kernel! Ktoonsez makes an excellent kernel, one for tw, and one for aosp, u just have to pick the right one according to which ROM you're running!! Good luck...
Click to expand...
Click to collapse
I did try flashing AOKP with TouchWiz, and it gives me an error that it cant flash.
Is the kernel that Ktoonsez all part of the ROM and just one file ?
Ultimately, I would like to flash AOKP, but my Galaxy S3 wont allow it...
Shane24 said:
I did try flashing AOKP with TouchWiz, and it gives me an error that it cant flash.
Is the kernel that Ktoonsez all part of the ROM and just one file ?
Ultimately, I would like to flash AOKP, but my Galaxy S3 wont allow it...
Click to expand...
Click to collapse
What?
What DMF1977 was saying is just flash the ROM you desire to have on your device and just run the kernel that comes with the ROM. After running the ROM you chose for awhile, if you feel the need to flash a new kernel then and only then flash the correct version of Ktoonsez kernel. And its not surprising that if you tried to flash anything AOKP related with TW you got an error.
Just flash an AOKP ROM and Dont worry about flashing an additional kernel.
Goodluck
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Trouble flashing international ROMs on n900T

Hey guys,
So i've been reading up on how to install international ROMs on my tmo n900T. I've downloaded all the necessary wifi / network fix files and tmo kernels. However, whenever I try to install either Bobcat ROM or X-Note 13.0, after the Aroma install, everything in my internal SD card gets wiped....every time. This includes the /system folder, which means the phone won't boot.
I've tried both ROMs and it does it. I can install the TMO Jedi ROM just fine, which also uses Aroma. I've also tried to install both those roms from both Philz Touch Recovery and TWRP 2.7.0.0.
Any ideas what could be going wrong?
dirrtyswan said:
Hey guys,
So i've been reading up on how to install international ROMs on my tmo n900T. I've downloaded all the necessary wifi / network fix files and tmo kernels. However, whenever I try to install either Bobcat ROM or X-Note 13.0, after the Aroma install, everything in my internal SD card gets wiped....every time. This includes the /system folder, which means the phone won't boot.
I've tried both ROMs and it does it. I can install the TMO Jedi ROM just fine, which also uses Aroma. I've also tried to install both those roms from both Philz Touch Recovery and TWRP 2.7.0.0.
Any ideas what could be going wrong?
Click to expand...
Click to collapse
I've never tried those roms and Jedi is a great rom but as for using international rom, I am using Omega v12 (4.4.2), everything works, especially native bluetooth tethering (the reason i went International).
Good luck.
kadster007 said:
I've never tried those roms and Jedi is a great rom but as for using international rom, I am using Omega v12 (4.4.2), everything works, especially native bluetooth tethering (the reason i went International).
Good luck.
Click to expand...
Click to collapse
Thanks I might try out that ROM. I did some more research and I think my issue is common for a few international ROMs. I found the reason and some workarounds here:
http://forum.xda-developers.com/showthread.php?t=2490351&page=13
Going to give it a try now.

wicked rom will not install.

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.

Categories

Resources