Related
I know this has been asked hundreds of times, and i searched the forums for days for a way to fix it, but with no use.
I have a rooted AT&T Galaxy SIII with JB 4.1.1. I am trying to install the CM 10.1(4.2.2) Nightly version, but i always get the infamous "Status 7 Installation Aborted" error.
Yes i am sure im downloading the correct ROM zip file for my phone and carrier.
I have CWM 6.0.2.1, and i followed the steps correctly. (Clear data -> Clear Cache Partition -> Clear Dalvik Cache -> install ROM)
I have tried so many times, i also re-rooted my phone, reinstalled CWM, and redownloaded different nightly versions of the ROM, as well as other ROMS like JellyBam.
I also tried to delete the assert lines in the update-script file, but that also wouldnt work.
Thank you. :good:
And please dont hate on me, im new to rooting and flashing. :crying:
Improper recovery.
samelaryan said:
I know this has been asked hundreds of times, and i searched the forums for days for a way to fix it, but with no use.
I have a rooted AT&T Galaxy SIII with JB 4.1.1. I am trying to install the CM 10.1(4.2.2) Nightly version, but i always get the infamous "Status 7 Installation Aborted" error.
Yes i am sure im downloading the correct ROM zip file for my phone and carrier.
I have CWM 6.0.2.1, and i followed the steps correctly. (Clear data -> Clear Cache Partition -> Clear Dalvik Cache -> install ROM)
I have tried so many times, i also re-rooted my phone, reinstalled CWM, and redownloaded different nightly versions of the ROM, as well as other ROMS like JellyBam.
I also tried to delete the assert lines in the update-script file, but that also wouldnt work.
Thank you. :good:
And please dont hate on me, im new to rooting and flashing. :crying:
Click to expand...
Click to collapse
BAM1789 said:
Improper recovery.
Click to expand...
Click to collapse
if you can boot into the phone, download ROM manager and update your cwm recovery. latest version is 6.0.2.8.
CM10 and 10.1 are picky about you having the most recent version. cheers
xBeerdroiDx said:
if you can boot into the phone, download ROM manager and update your cwm recovery. latest version is 6.0.2.8.
CM10 and 10.1 are picky about you having the most recent version. cheers
Click to expand...
Click to collapse
I did that and it worked thank you :good:
samelaryan said:
I did that and it worked thank you :good:
Click to expand...
Click to collapse
thats what we're all here for, buddy
Status 7: installation aborted.
xBeerdroiDx said:
thats what we're all here for, buddy
Click to expand...
Click to collapse
Hi guys, I'm having same issue but on N7000 international version. I'm able to go in the recovery mode and download mode but phone won't boot normally. It's stuck on Samsung logo so can you please advise something? How can I update CWM if that's the issue. I was on ICS 4.0.4 XXLRK before trying to install CM10.1 on Note.
Thanks in advance for your help.
perceptorz said:
Hi guys, I'm having same issue but on N7000 international version. I'm able to go in the recovery mode and download mode but phone won't boot normally. It's stuck on Samsung logo so can you please advise something? How can I update CWM if that's the issue. I was on ICS 4.0.4 XXLRK before trying to install CM10.1 on Note.
Thanks in advance for your help.
Click to expand...
Click to collapse
I would be doing my research in an N7000 forum, friend.
Also, your post seems confusing as you seem to be saying you also got a status 7 error but then you appear to have installed abroad and are stuck at the boot logo. If you successfully flashed the correct rom for your device without any errors, pull battery, replace and wipe data in recovery. Reboot
xBeerdroiDx said:
I would be doing my research in an N7000 forum, friend.
Also, your post seems confusing as you seem to be saying you also got a status 7 error but then you appear to have installed abroad and are stuck at the boot logo. If you successfully flashed the correct rom for your device without any errors, pull battery, replace and wipe data in recovery. Reboot
Click to expand...
Click to collapse
Apologies for both confusion and using the S3 that to find some help. I just found the situation quite familiar so I couldn't help myself from asking the question
On the situation, I was able to install CWM and am able to go to recovery or download mode but the error displays when I try to update the zip of any rom.
perceptorz said:
Apologies for both confusion and using the S3 that to find some help. I just found the situation quite familiar so I couldn't help myself from asking the question
On the situation, I was able to install CWM and am able to go to recovery or download mode but the error displays when I try to update the zip of any rom.
Click to expand...
Click to collapse
If the phone itself is functioning fine but you simply cannot flash a new rom or rom update, you need to update your recovery. Go to clockworkmods website and download version 6.0.1.2.
xBeerdroiDx said:
If the phone itself is functioning fine but you simply cannot flash a new rom or rom update, you need to update your recovery. Go to clockworkmods website and download version 6.0.1.2.
Click to expand...
Click to collapse
Right now, phone doesn't get pass Samsung boot logo so will I be able to update new CWM using Odin? (Sorry, if the question appears to be basic or stupid)
perceptorz said:
Right now, phone doesn't get pass Samsung boot logo so will I be able to update new CWM using Odin? (Sorry, if the question appears to be basic or stupid)
Click to expand...
Click to collapse
I would take up this situation in the correct forum. The more we discuss your device issues the more likey you are to download the wrong file or use a procedure not designed for your device software.
If you came from stock, flashed a rom and are stuck at the samsung logo, boot into recovery, wipe data and cache. Reboot to see if that helped. If not, seek advice in the N7000 forum. Cheers
Thanks for the guidance.
ATT LG Optimus G Pro Here
I used newest FreeGee , Installed TWRP & Now im stuck in recovery mode. I flashed gummy rom first time & It worked. Ran into problem after I installed the Google apps so I did a factory reset, wiped everything to try again to install gummy rom. Now I'm stuck in TWRP. I also used ADB sideload commands to push the rom to phone & It did push it, except now. When I try to install the rom, It keeps saying FAILED. Can someone tell me what im doing wrong?
newgeek- I don't know if the AT&T version of this is very different to my F240 version but I am familiar with that 3rd screen you posted with the "secure booting error" or something like that.
What about just pulling that battery out and doing factory reset and start over from the beginning ?
LL13-
newgeek35 said:
ATT LG Optimus G Pro Here
I used newest FreeGee , Installed TWRP & Now im stuck in recovery mode. I flashed gummy rom first time & It worked. Ran into problem after I installed the Google apps so I did a factory reset, wiped everything to try again to install gummy rom. Now I'm stuck in TWRP. I also used ADB sideload commands to push the rom to phone & It did push it, except now. When I try to install the rom, It keeps saying FAILED. Can someone tell me what im doing wrong?
Click to expand...
Click to collapse
Try to push another ROM via adb, I read in the general Section that there were some Gummy files that weren't the right size, just download CM11 and try to flash it, TWRP is saying that the flash failed, that's why you are stuck in recovery.
Erik
The phone currently has no OS , I also tried to mount my 64gb sd card to install off of that & It gives me a mounting error for SD CARD. I have tried several other roms & No luck , Keeps giving me FAILED. Is this because of the secure boot perhaps? I'm totally clueless why it's not taking it. I'm running my nexus 4 with the gummy rom without a hitch.
Why not try a different SD card ? If that SD card was in the phone when all this happened maybe something is on the card that's bad ?
LL13-
I borrowed a 2GB SD CARD & It mounts but same thing as before FAILED. Tried both gummy & CM 10.2
newgeek35 said:
I borrowed a 2GB SD CARD & It mounts but same thing as before FAILED. Tried both gummy & CM 10.2
Click to expand...
Click to collapse
It looks like an error with the updater script, maybe something twrp isnt reading or executing? try a different rom.
At worst try a different Recovery.
ADDED:2/4/2014: I would avoid twrp on freegee, i've heard others have issues and it may have something to do with your situation.
Also, I noticed your twrp says 2.6.1.0, am I mistaken or is the newest teamwin 2.6.3.1? That number don't look right.
If possible try to flash madmacks twrp or cwm 6.0.4.6.
1.Try to Flash a ROM via sideload
2. you can end the recovery boot loop by using adb commands, there are two methods try them
http://forum.xda-developers.com/showpost.php?p=49370751&postcount=70
and
http://forum.xda-developers.com/showpost.php?p=48136185&postcount=268
I had the same issue seems like the are some problems with TWRP on this particular phone I flashed the regular clockworkmod and it works perfect.I tried on another phone with same results.
Right now
Flash stock rom
root
use freegee to install regular cwm I tried rom manage but recovery did not installed
the flash another rom if thats what you really want but copy rom directly to sd card instead
Its not just twrp apparently the new update of freegee installs the wrong bootloader/image on our phone. It bootloops anyone that uses it.
Sent from my LG-E980 using XDA Premium 4 mobile app
Use Madmack's hacked TWRP located in his CM threads. Best recovery for our device from what I've seen/tested.
Sent from my AICP 4.4 LG-E980
Neroga said:
Use Madmack's hacked TWRP located in his CM threads. Best recovery for our device from what I've seen/tested.
Sent from my AICP 4.4 LG-E980
Click to expand...
Click to collapse
Madmack's TWRP is reliable when you want to have no bootloops into your recovery. But i have the problem, that i cannot flash any other roms and it shows, that my LG E986 isnt recognized as a suitable device for the rom and it aborts the procedure. Although on the other recoveries it worked fine...
Is there something what i have to do except switching recoveries to my phone's death?
I used ADB to push the stock rom back to device & It took it's sweet time but it worked. I sold the phone to a friend of mine LOL! They wont know the difference.
Okay, everything seemed fine on my s2 until the latest CM download. I install it though CWM and it seems fine but then it says
set_metadata_recursive: some changes failed
E:Error in /sdcard/firmware/cm-11-20140619-NIGHTLY-hercules.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
Firmware is just the folder name for where i keep the files i may flash to it. I have tried other
I tried to install CM 10.2.0 and it seems to work. but then when i try and boot, it goes to the splash screen and just stays there. Did I do something wrong that is causing this?
Spud37 said:
Okay, everything seemed fine on my s2 until the latest CM download. I install it though CWM and it seems fine but then it says
Firmware is just the folder name for where i keep the files i may flash to it. I have tried other
I tried to install CM 10.2.0 and it seems to work. but then when i try and boot, it goes to the splash screen and just stays there. Did I do something wrong that is causing this?
Click to expand...
Click to collapse
"Set metadata recursive" probably means you are using a recovery that is too old.
@Spud37
Yes, it means your recovery is outdated. Here is a download link for the latest TWRP that you can flash in Odin as PDA. http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.7.1.0-hercules.tar
This link came from teamwins website (teamw.in)
Sent from my SGH-T989
jrc2 said:
@Spud37
Yes, it means your recovery is outdated. Here is a download link for the latest TWRP that you can flash in Odin as PDA. http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.7.1.0-hercules.tar
This link came from teamwins website (teamw.in)
Sent from my SGH-T989
Click to expand...
Click to collapse
Well there is another issue with my phone that I have actually worked around for awhile now. The MircoUSB on the phone is broken. I bought an extra battery and swap it, I also just use the SD card to copy anything to the phone. Is there a way for me to flash the phone with the new TWRP from the sd card. Why would the older TWRP not install CM 10.2.0 ROM? Do I have to go older perhaps? Thanks though. Knowing is half the battle
EDIT: Going to try and install 10.1.0 and see if it will let me boot. I figure once I can get it to boot, it will be easier to update the Recovery on the phone.
EDIT 2: No problems or errors occured when I installed CM 10.1.0.zip. However it still got stuck in a boot loop. I did however find a file called superwipe for the T mobile S2. I am wondering if that could help
EDIT 3: Okay so the superwipe worked and i am now running 10.1.0, Is it possible to install a Recovery from the phone without using odin?
What all did you wipe when you installed 10.1? There is a way to update the recovery if you can get the phone to boot. What is the latest thing you got to boot on your phone?
Sent from my HP Slate 7 using Tapatalk
jrc2 said:
What all did you wipe when you installed 10.1? There is a way to update the recovery if you can get the phone to boot. What is the latest thing you got to boot on your phone?
Sent from my HP Slate 7 using Tapatalk
Click to expand...
Click to collapse
I had wiped everything, formatted and fixed permissions, it didn't work. It wasn't until i found the Superwipe that installation worked and i was able to boot to 10.1.0. How can i update/change the recovery from the phone.
Thanks
Spud37 said:
I had wiped everything, formatted and fixed permissions, it didn't work. It wasn't until i found the Superwipe that installation worked and i was able to boot to 10.1.0. How can i update/change the recovery from the phone.
Thanks
Click to expand...
Click to collapse
It is a lot more risky if your usb port doesn't work, since you can't flash back to stock in Odin if something goes wrong. I would recommend that you get someone to fix that USB port before you make too many changes.
DISCLAIMER: I am not responsible for anything that happens to your phone. These changes could brick your phone if something goes wrong. Proceed at your own risk!
Okay, now for the tutorial. These instructions are assuming that you are already rooted. Download this file and make sure you check the md5sum. Rename it to TWRP.img and move it to /storage/sdcard. This will make the next steps easier. If you move the file somewhere else, make a note of the location of the file. If you have not already, install the terminal emulator app form the Play Store. Open it and type the following lines in it.
Code:
su
[CLICK ENTER]
Code:
dd if=/storage/sdcard/TWRP.img of=/dev/block/mmcblk0p22
(Change the path to wherever you moved the file to) [CLICK ENTER]
Reboot into recovery and wipe cache and dalvik. Reboot. If recovery says that system recovery will override it on reboot, click fix. This should update your recovery.
Have a good afternoon,
jrc2
[Q] Need help in solving "Unfortunately, settings have stopped working" error
Problem: My unrooted SGH-I747 model AT&T GS3 recently gave me this error whenever trying to access the settings. The error shows up even after a full factory reset and I can no longer access my phone. Stuck a little after the language selection in the beginning stages of the setup.
Attempted fixes: Obviously, the initial factory reset. Then clearing the cache + factory reset.
After those failed to work, I tried to flash to a AT&T stock rom from this forum (http://forum.xda-developers.com/showthread.php?p=33570269#post33570269) using Odin. I tried to use the first row of downloads but the first row but it did not have a MD5 file, so I used the second row of downloads instead but this rom failed to install. My guess is that it may be too old of a version.
I would appreciate any help.
[SOLVED]
The problem may have arose from a critical error in the phone's software that had affected the OS system of the phone. I resolved the issue by flashing a new custom OS (cyanogenmod) to my phone. These are the steps that I took:
1. Installing Odin (http://forum.xda-developers.com/showthread.php?t=1722686)
2. Rooting my cellphone with CFAutoRoot using Odin (http://forum.xda-developers.com/showthread.php?t=1725839)
3. Installing a custom recovery TWRP -- highly recommended very user friendly (http://forum.xda-developers.com/showthread.php?t=1793224)
4. Installing a new custom rom through TWRP-- used Cyanogen (http://forum.xda-developers.com/showthread.php?t=1778270)
5. Installing gapps (http://opengapps.org/?api=5.1&variant=nano)
6. Identifying the correct bootloader by downloading and installing Samsung Phone Info by vndnguyen through the Play Store.
7. Installing the correct bootloader and modem (http://forum.xda-developers.com/galaxy-s3-att/general/rooted-ucufnj1-stock-rom-t2985006)
Please refer to respective installation guides for more instructions regarding installation of any new software.
I hope this helps anyone who may have run into the same problem.
Before attempting to flash anything, confirm the bootloader on your phone. An easy way to determine if the bootloader is 4.3 or newer, boot into download mode. If you see anything about warranty bit, your phone has at least a 4.3 bootloader and no attempts should be made to flash anything from sammobile.com.
If you have a 4.3 or newer bootloader, I recommend flashing a custom recovery such as TWRP, and then flashing a stock ROM from recovery.
First off, thank you for the reply audit!
Now I have officially rooted my phone using CF-Autoroot and have installed TWRP. I have also confirmed that the bootloader is at least 4.3 because it does show the warranty bit.
Which of the stock roms are compatible with this bootloader?
Do you want to stay on a stock ROM? If not, you could flash a custom ROM such as cm12.1 using TWRP. Once you have flashed a custom ROM, you can look under settings to determine the baseband on the phone which is another clue as to which bootloader is on your phone.
audit13 said:
Do you want to stay on a stock ROM? If not, you could flash a custom ROM such as cm12.1 using TWRP. Once you have flashed a custom ROM, you can look under settings to determine the baseband on the phone which is another clue as to which bootloader is on your phone.
Click to expand...
Click to collapse
Just to be clear, cm12.1 is the cyanogenMod nightly?
Yup. If you flash it, your baseband may be unknown which tells me you are probably not running a 4.4.2 bootloader and modem.
audit13 said:
Yup. If you flash it, your baseband may be unknown which tells me you are probably not running a 4.4.2 bootloader and modem.
Click to expand...
Click to collapse
I'll try it out and see if I can get past the language screen this time.
Got the latest Cyanogenmod Zip file onto my phone. Tried flashing it through TWRP with the install option but it failed.
Log reads that no MDS file was found, detected filesystem ext4 for /dev/block/platform msm_sdcc.1/byname system. Can't install this package on top of incompatible data.
CM12.1 won't have an md5 file. You're trying to install cm12.1 for the d2att or d2lte? You're running the latest TWRP which I believe is 2.8.7.0? or 2.8.7.1?
5K posts.
"all i can really do , is stay out of my own way and let the will of heaven be done"
I'm pretty sure that CM de-unified the variants for CM 12.
From: https://wiki.cyanogenmod.org/w/D2lte_Info
Note: Unified device
Between the release of CM 11 M3 and CM11 M12, all Qualcomm-based variants of this device were merged into a single build: d2lte. The device information pages for the individual variants should be used to reference any device-specific unlock instructions, download recoveries, to build CM 10.2, or to install CM 12.1: d2att, d2cri, d2mtr, d2spr, d2tmo, d2usc, d2vzw.
Click to expand...
Click to collapse
I think this was just to make searching a bit harder/ more complicated.
audit13 said:
CM12.1 won't have an md5 file. You're trying to install cm12.1 for the d2att or d2lte? You're running the latest TWRP which I believe is 2.8.7.0? or 2.8.7.1?
Click to expand...
Click to collapse
For d2att and running 2.8.7.0 for TWRP.
You should be good then.
The file should be left unzipped/unrared when using it right? I'm using it as such but it keeps returning the same error message saying that it won't install it.
Yes, leave it zipped. What is the TWRP error message?
The error log:
detected filesystem ext4 for /dev/block/platform msm_sdcc.1/byname system.
Can't install this package on top of incompatible data.
Please try another package or run a factory reset
E: Error executing updater binary in zip '/sdcard/Download/cm-12.12015913-NIGHTLY-dtatt.zip
Error flashing zip '/sdcard/Download/cm-12.120150913-NIGHTLY-D2att.zip
Weird, did you do a full wipe before trying to install?
Can't believe it was that simple. I thought I had already made the wipe when I did it with the original recovery but making a second wipe through TWRP actually helped make it happen. I finally got through and have full access to my phone.
Unfortunately, the cell service doesn't seem to work but I'm guessing that I need to do more for the set up?
Edit: Not recognizing the sim card for some reason
Sounds like you need to update the bootloader and modem to the older KK version which I think is ne4.
Sorry for the late reply I've been busy the past week. I'm guessing the modem won't work without the proper bootloader? I've tried flashing the latest and original modem from the Modem list (http://forum.xda-developers.com/showthread.php?t=1831898). While they installed successfully I still don't get a signal.
I was worried which bootloader to take because it may lead to bricking. Which one are you referring to and are they in the Bootloader updates topic here? (http://forum.xda-developers.com/showthread.php?t=2321310)
Stuck at "Patching System Image Unconditionally" when flashing CM12.1 via TWRP
Just got a Note 4, proceeding with the usual root and installation CyanogenMod ASAP
Everything was going smoothly until the actual flashing of CyanogenMod, whenever I try to flash it, it just gets stuck on "patching system image unconditionally" and doesn't progress beyond that point
Steps I've taken so far:
1) unboxed phone, was running Android 6.0 (I think, maybe 6.0.1)
2) Rooted with Chainfire's Auto Root
3) Flashed TWRP 3.0.2-0 via Odin 3.09 as per TWRP's instructions
4) Ensured that I could boot both to the stock ROM and TWRP
5) Copied cm12.1 and gapps to Note 4's internal storage (sd card hasn't come in yet, normally I put it onto sd card)
6) Did default factory wipe from TWRP
7) Attempted to flash cm12.1, ran into issue
I didn't make a backup of the stock ROM so now the phone has a recovery but no actual OS, as I had to pull the battery out to get it to do anything beyond being stuck at the patching system image step
I'm redownloading cm12.1 in case maybe there was a problem with the .zip itself, I know it's bad practice but I never check md5 sums
I've found other threads that suggested flashing the stock ROM for some reason, but they were for other phones and I'm not sure if it's related to the Note 4.
I've seen some mention of the bootloader being locked, but I don't know how to tell if the bootloader is locked or not. I see the same exact boot screen that I saw with my Note 3, S4, S3, etc. Could the issue be the bootloader?
I've also found this thread, but I can't get TWRP to mount in Windows, it keeps saying the driver failed to install. MTP transfers worked fine with the stock ROM was still there, but for some reason it doesn't work with the Mount option in TWRP. I'm downloading the Android SDK so I can try using adb
If anyone else has run into this, can you advise me on what to do from here?
EDIT: Nevermind, fixed it. Changed system partition's filesystem to F2FS via TWRP, and this allowed CM and gapps to flash with no issue. Now booted into CM But hopefully this will be helpful if anyone else has this issue
EDIT2: Buuuuut now the WiFi's not working. It just gets stuck at "turn on WiFi" but nothing actually turns on, and the on/off button for WiFi in settings is grayed out. IT NEVER ENDS
CyanogenMod Thread
Reddit Thread
EDIT3:
WiFi and Settings Issue seems to be resolved
I think the problem had something to do with the baseband version
As per Trex's post (http://forum.xda-developers.com/showpost.php?p=69520362&postcount=2), I had to revert back to the OK1 baseband
Now everything seems to work fine
As for TWRP not working and just going to a black screen, I redownloaded it from the TWRP website and it worked fine
So now both TWRP and CM are installed and working, WiFi works, and Settings don't crash.
Now I've encountered an issue where the camera doesn't focus, and I'm wondering if there's still some plastic film on the camera lens, but I've been picking at it and nothing is coming off and I'm afraid of damaging the plastic if I keep trying...
AbuFiraas said:
Just got a Note 4, proceeding with the usual root and installation CyanogenMod ASAP
Everything was going smoothly until the actual flashing of CyanogenMod, whenever I try to flash it, it just gets stuck on "patching system image unconditionally" and doesn't progress beyond that point
Steps I've taken so far:
1) unboxed phone, was running Android 6.0 (I think, maybe 6.0.1)
2) Rooted with Chainfire's Auto Root
3) Flashed TWRP 3.0.2-0 via Odin 3.09 as per TWRP's instructions
4) Ensured that I could boot both to the stock ROM and TWRP
5) Copied cm12.1 and gapps to Note 4's internal storage (sd card hasn't come in yet, normally I put it onto sd card)
6) Did default factory wipe from TWRP
7) Attempted to flash cm12.1, ran into issue
I didn't make a backup of the stock ROM so now the phone has a recovery but no actual OS, as I had to pull the battery out to get it to do anything beyond being stuck at the patching system image step
I'm redownloading cm12.1 in case maybe there was a problem with the .zip itself, I know it's bad practice but I never check md5 sums
I've found other threads that suggested flashing the stock ROM for some reason, but they were for other phones and I'm not sure if it's related to the Note 4.
I've seen some mention of the bootloader being locked, but I don't know how to tell if the bootloader is locked or not. I see the same exact boot screen that I saw with my Note 3, S4, S3, etc. Could the issue be the bootloader?
I've also found this thread, but I can't get TWRP to mount in Windows, it keeps saying the driver failed to install. MTP transfers worked fine with the stock ROM was still there, but for some reason it doesn't work with the Mount option in TWRP. I'm downloading the Android SDK so I can try using adb
If anyone else has run into this, can you advise me on what to do from here?
EDIT: Nevermind, fixed it. Changed system partition's filesystem to F2FS via TWRP, and this allowed CM and gapps to flash with no issue. Now booted into CM But hopefully this will be helpful if anyone else has this issue
EDIT2: Buuuuut now the WiFi's not working. It just gets stuck at "turn on WiFi" but nothing actually turns on, and the on/off button for WiFi in settings is grayed out. IT NEVER ENDS
Click to expand...
Click to collapse
You must flash 5.1.1 ok1 bootloader to get wifi work
I suggest you first flash 5.1.1 firmware in odin
Then flash twrp. Tar file in odin.
Then make full wipe
Flash cm rom + gapps
You will get clean rom install without any errors
Hope this will help
Trex888 said:
You must flash 5.1.1 ok1 bootloader to get wifi work
I suggest you first flash 5.1.1 firmware in odin
Then flash twrp. Tar file in odin.
Then make full wipe
Flash cm rom + gapps
You will get clean rom install without any errors
Hope this will help
Click to expand...
Click to collapse
Okay I'll give that a shot. Are "5.11 ok1 bootloader" and "5.1.1 firmware" the same thing? And do you know where I can find it/them?
Just flashed OK1 via Odin via this thread, but it's just boot looping over and over
EDIT: Did a simple factory wipe and it's working fine now. Currently running unrooted Stock 5.1.1, Baseband N910PVPS4COK1. So I'm basically starting from the beginning, whereas before it was on 6.0 but now it's 5.1.1
Am now rooted but I can't get TWRP installed, I flash it and try to boot to recovery but it just boots to a black screen
Issue seems to be resolved, edited original post
AbuFiraas said:
Okay I'll give that a shot. Are "5.11 ok1 bootloader" and "5.1.1 firmware" the same thing? And do you know where I can find it/them?
Click to expand...
Click to collapse
Go to download mode and check exact model number
Tell me model number and i give you links for bootloader and firmware
Trex888 said:
Go to download mode and check exact model number
Tell me model number and i give you links for bootloader and firmware
Click to expand...
Click to collapse
It's working now, I found another post that had all the various stock firmwares on there. Now the issue I'm having is that my camera doesn't focus at all, but I don't know if it's a hardware or software issue. I never checked the camera before rooting the first time. Gonna try going back to unrooted stock again but if that doesn't change anything, I might have to take it to a Sprint store and get a replacement. Hopefully they don't notice the KNOX trip... lol