Related
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.
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.
Hello, normally I do lots of research and searching in order to figure out problems for myself, but this one I have been stuck on for weeks.
I am on SGH-T999v, here is my issue.
I am trying to use either the latest 1.5 Spirit Rom, or M4 gummy Rom in combination with KTOONSEZ Kernel from here.
If I try to flash the kernel with latest versions of those roms, my baseband says "UNKNOWN" and my IMEI gets zero'd out.
Also it tells me that I have no sim card inserted. I have tried formatting dalvic/cache before and after installation of kernel as well as fixing permissions.
Both Spirit 1.5 and Gummy M4 work no problem without the custom kernel installed.
Also, on only 1.1 Spirit and M3 gummy, am I able to use the custom KT kernel and still have my signal.
Okay now here is the strange part of the problem.
Currently I am using the custom recovery TWRP that lets me use multiboot from here
And after successfully creating a multiboot rom, I go ahead and install Gummy M4 + Gapps + KT Kernel and boot it up, to find out that it actually works perfectly fine.
My baseband shows up, and my signal connects.
Also the version im using of the recovery menu is V2.11
I am just wondering why is it that the rom + custom kernel doesn't work with a regular flash, and that it only seems to work when I multiboot it?
What I want is to not have to create a multiboot rom in order to use this, I want to actually flash these to my phone.
Please help me, anyone who has any idea of what I am talking about..Sorry if I have not been clear enough. Thank you/.
Edit: I also forgot to mention that I have tried flashing the stock modem after the kernel + rom installation through odin, that did nothing.
Hey Guys,
I just got a new Samsung Galaxy S3 SGH-I747 in the mail and I immediately started to install Cyanogenmod. I have installed it on two S3's in the past, but this time I had no idea about the new bootloader problems after Android 4.3 (I think?). I got CWM touch installed with no problems via Odin, but when I tried to use the Unified Android Toolkit thing to root and stuff I got stuck in a boot loop. The phone would not boot past the Samsung logo, not the animated one with the purple light, but the one that shows the phone model.
I have tried everything I could think of and all that I tried to google for the past couple hours to no avail. I stupidly did not make a backup of my stock ROM, and I couldn't find a stock 4.4.2 ROM except this one that says it is stock but with root. I flashed that ROM and then it booted past the Samsung logo and the animated one, but is now stuck on the AT&T logo. I looked up that problem and couldn't find any real information on that problem except one thread where it said I should install Kies and let it do the Firmware Upgrade and Initialisation option. That failed and then my phone would only turn on straight to download mode.
I reflashed CWM and that worked so I thought that if I tried to install Cyanogenmod 11 it might work because that ROM is 4.4.1 or higher (Again, I think?). Now it's back into the loop where it makes it past the samsung stuff but then gets stuck on the AT&T logo. Is there anything I can do?
Thanks,
Jemimacakes
Did you try wiping cache, data, and Dalvik in CWM?
Did you try installing CM10.2 from CWM?
audit13 said:
Did you try wiping cache, data, and Dalvik in CWM?
Did you try installing CM10.2 from CWM?
Click to expand...
Click to collapse
Yes, I have tried clearing stuff in both CWM and stock recovery. Im not sure about the Dalvik one though, unless that is cleared when you do factory reset and clear cache I didnt do it. I can try flashing CM10.2 ( which I would prefer to have over 11), but my understanding is that my boot loader will not let me install anything that uses any lower versions of android, but I'll give it a shot and let you know.
Ok guys,
I tried to install Cyanogenmod 10.2 and when I put it on my sd card and tried to install it with CWM It threw and ton of errors that look like this.
assert failed: getprop("ro.bootloader") == "I747UCDLK3" || getprop("ro.bootloader") == "I747UCDMG3" || etc etc.
Im not super experienced with programming, but im guessing that CM10.2 can find any bootloader it can use? Im not sure what my bootloader is if that is the case, but I can boot into recovery so I must have something, right?
Anything I can do?
Thanks
Jemimacakes
You should try flashing cm10.2 just to see if you can get your phone to boot. By booting the phone, you can determine your bootloader and modem.
Edit: okay, cm10.2 doesn't work. Are you running the latest version of cwm? Maybe try twrp?
Hey,
I did have the latest version of CWM, but I tried it on TWRP and got the same errors
audit13 said:
You should try flashing cm10.2 just to see if you can get your phone to boot. By booting the phone, you can determine your bootloader and modem.
Edit: okay, cm10.2 doesn't work. Are you running the latest version of cwm? Maybe try twrp?
Click to expand...
Click to collapse
Hey,
I have now tried both custom recoveries and gotten the same errors on both, and I made sure I had the latest version of each. Can I flash the firmware from 4.3 and then install CM10.2? Will that work? I really don't want to hard brick my phone.
EDIT: I installed ADB to find out what my bootloader was, and it returned that I had the NE4 version. Is there a way to get the MJB version safely so I can install 10.2?
At this point I just want it to boot up to anything, so if that is easier to do than get CM to work then im completely open.
You cannot go back to MJB from NE4.
How did you try to install CM the first time? Did you use the install manager or a custom recovery?
The last time I installed CM on a i747 was back when the phone was on 4.1.1. The second phone I installed it on was the international version of the phone, also on 4.1.1. I used a custom recovery both times. I bet if I would have used the new installer on this phone it would have worked, but I was trying some other stuff because I was curious and ended up breaking it.
IT BOOTED!
I reflashed the stock firmware + root, reinstalled stock recovery and wiped everything I got it to boot into its stock ROM. From this point, where do I go? Will the CM installer work or will it just brick it again?
Thanks
Jemimacakes
I would copy a custom rom such as cm11 to the internal and external sd card.
I would then download the latest version of philz touch for the d2lte. Get Odin 3.07. Put the phone in download mode, open Odin, uncheck all options except f reset time. Flash philz, when you see reset in the status window, remove USB cable, remove battery, insert battery, boot into recovery, create a nandroid of your current rom, flash cm11, wipe cache, wipe data, wipe dalvik, reboot.
audit13 said:
I would copy a custom rom such as cm11 to the internal and external sd card.
I would then download the latest version of philz touch for the d2lte. Get Odin 3.07. Put the phone in download mode, open Odin, uncheck all options except f reset time. Flash philz, when you see reset in the status window, remove USB cable, remove battery, insert battery, boot into recovery, create a nandroid of your current rom, flash cm11, wipe cache, wipe data, wipe dalvik, reboot.
Click to expand...
Click to collapse
Which version of CM11 should I get. On the site I see that the last version of CM11 for the I747 (d2att) was released on feburary 16, is this one based on 4.4.2?
EDIT: Also, I should copy CM11 to both the internal and external storage? Why is this?
You should be using roms made for the d2lte.
I suggest both because cwm or twrp may see one but not the other. This doesn't usually happen but I am always paranoid about something going wrong as flashing always involves risk and I like to minimize risks and be prepared for disaster.
audit13 said:
You should be using roms made for the d2lte.
I suggest both because cwm or twrp may see one but not the other. This doesn't usually happen but I am always paranoid about something going wrong as flashing always involves risk and I like to minimize risks and be prepared for disaster.
Click to expand...
Click to collapse
Alright, but I have the at&t version of the phone. Are they both compatible with one another?
EDIT: OK, correct me if im wrong, but my new understanding is that CM now has releases for general versions of phones, so the most recent update of CM for my phone is the d2lte, not d2att?
Before unified builds for the msm8960 were started, the i747 was known as the d2att and the i747m was known as the d2can.
audit13 said:
Before unified builds for the msm8960 were started, the i747 was known as the d2att and the i747m was known as the d2can.
Click to expand...
Click to collapse
Hello again,
Thanks a ton Audit, my phone is up and running with the latest cyanogen nightly! A recap for anyone who might come across with a similar problem.
1. I installed a ROM using an older version of android onto a phone with the new bootloader (NE4), softbricking it.
2. I installed the stock ROM + root from this link using Clockworkmod
https://www.androidfilehost.com/?fid=23501681358550126
3. Installed the stock Recovery from this link and did wiped my data and both caches
https://www.androidfilehost.com/?fid=23681161096070493
4. I rebooted the phone and waited at the AT&T logo for a while, and it booted up normally!
5. I installed the most recent version of Philz Touch Recovery for the d2lte, made a nandroid for safety, and then install the latest nightly of CM11 for the d2lte.
6. It works!
Thanks again to Audit for helping me out!
Jemimacakes
I'm glad it all worked and I was able to help in some way.
It's great that you posted your solution in case it helps other people in a similar situation.
I think i'm in a similar place - a few questions. You used cwm to install the stock ROM? I thought you needed to use odin. Also, why did you need to install the stock recovery (and did you just flash the .zip in cwm)? Also, that stock rom you linked to is 4.4, right? Would that work if I was on 4.3?
Before flashing anything, I suggest you confirm your bootloader and modem. Flashing the wrong combination of modem and bootloader could hard brick your phone.
If your phone does not boot, try flashing Philz Touch for the d2lte and flash the latest cm11. Hoepfully, this will get your phone running so you can confirm the bootloader and modem. CM11 does not flash a modem or bootloader.
My phone is a 4.3 official Samsung and is properly rooted. I have downloaded CM13 and Gapps onto my external SD card and went into CWM recovery mode. I firstly backed up everything (thankfully) and performed a wipe data/factory reset followed by installing CM13. However when I run CM13 almost immediately an error pops up saying "this package is not for device: this device is d2spr" along those lines. Any help would be appreciated; thanks!
BTW forgot to mention I completely removed Knox from my phone so that I could root it.
I had a similar issue, but with TWRP. As I have a Canadian S3, so I downloaded the "d2can" build of TWRP.
When I tried to flash the CM13 "d2tmo" package, it resulted to an error, saying that it cannot install the package as my device was a "d2can".
I did a quick search on Google to find out that, for TWRP at least, both recovery and package device must match. Maybe a wrong version of the recovery was installed in your case?
Did you use CyanogenMod app? From memory, it seems you can edit the device name. Try to change it to "d2tmo" as explained on the CyanogenMod SGS3 FAQ (search "SGS3FAQ" on Google).
The "d2can" is the moniker for the s3 from Rogers, Telus, and Bell and the d2att is the moniker for the AT&T version of the s3.
The s3 development for the d2can and d2att was unified into the d2lte.
The cm13 for the d2tmo is not installing because the updater script is looking for a particular model.
Did you try flashing twrp for d2tmo?
audit13 said:
The "d2can" is the moniker for the s3 from Rogers, Telus, and Bell and the d2att is the moniker for the AT&T version of the s3.
The s3 development for the d2can and d2att was unified into the d2lte.
The cm13 for the d2tmo is not installing because the updater script is looking for a particular model.
Did you try flashing twrp for d2tmo?
Click to expand...
Click to collapse
Actually, it seems (based on the page "Information: Samsung Galaxy S III LTE ("d2lte")" in the CyanogenMod Wiki) that S3 development was unified into "d2lte" only between CyanogenMod 11 M3 and M12 releases.
The SGS3FAQ page refers explicitly to the "d2tmo" build for the SGH-T999 and SGH-T999V for CM 12.1 and newer releases.
Hmm, seems that cyanogen has gone back to using d2att for newer releases as indicated here: https://download.cyanogenmod.org/?device=d2att
The i747 and i747m should work on d2att builds.
That wiki page was last updated in February, 2014?
I used to have an s3 from wind and I used twrp for the d2tmo to flash ROMs.
audit13 said:
The "d2can" is the moniker for the s3 from Rogers, Telus, and Bell and the d2att is the moniker for the AT&T version of the s3.
The s3 development for the d2can and d2att was unified into the d2lte.
The cm13 for the d2tmo is not installing because the updater script is looking for a particular model.
Did you try flashing twrp for d2tmo?
Click to expand...
Click to collapse
Yeah I just tried with d2tmo, same results. I went to download the d2spr and flash it onto my phone and it worked. Turns out my phone has misleading stickers saying that it is a T model brand; it turns out it is a sprint. So after wiping out my phone completely, including davlik cache and cache partition. After this I flashed Gapps 6.0 ARM and rebooted my phone. After this a bunch of errors start popping up in the setup phase that play store has crashed and google frameworks has crashed etc. The apps are not there in my applications so I can't mess around with the settings and also I am locked out of most of my applications which suddenly crash followed by a rude avalanche of google apps crashing messages. Further assistance is required <3 I am a newbie at this so please be gentle.
Oh and if it helps, I cannot access file manager at all without crashing. So... Yeah.
Does the sprint phone have a locked bootloader? Probably not if it took twrp.
Maybe flash back to stock if possible with Odin and start over?
audit13 said:
Does the sprint phone have a locked bootloader? Probably not if it took twrp.
Maybe flash back to stock if possible with Odin and start over?
Click to expand...
Click to collapse
I would try that thanks. Will tell you results bu tomorrow; kinda busy now
Ok it still doesn't work; after rebooting to the old stable os and then to CM13 is fine, but gapps is still screwing up big time. Any suggestions?
Have you tried different versions of the cm13 gapps?
audit13 said:
Have you tried different versions of the cm13 gapps?
Click to expand...
Click to collapse
Yeah I have, recovery mode just won't boot it at all saying that it is not compatible, and then it would abort then soft brick my phone in a never ending booting loop. So yeah, not fun. I tried installing the gapps of a different version; so far I have only used pico which resulted in the rom working, but all google applications would just crash continuously making it unbearably annoying to do anything with the popup screens.
I have tried micro however it would continuously reboot over and over for about 15 min so I can almost assume that it doesn't work so I reinstalled the stable 4.3 android version that I am at now.
Despite going through hell I have learnt a lot. However I want to get this done so I can enjoy the custom rom. Yet again any more suggestions please bring it up, thanks!
Try banks gapps?
audit13 said:
Try banks gapps?
Click to expand...
Click to collapse
I'll give that a go hang on....
It didn't work. While I was flashing it, it would say:
Finding update package...
Opening update package...
Installing update...
Installation aborted
Any more suggestions ?
This is my screen. The files have somewhat installed but are stored elsewhere?
http://imgur.com/a/v3cIW
http://imgur.com/jrVq6Nd
Hey guys thanks for everything. The problem was solved by installing a different twrp. The old one I was using was apparently corrupted and screwed up my current phone, heh the chances of that?? Lots of love <3<3<3