Related
Hi everyone, i just had my Xperia Arc stuck at the bootscreen after doing these steps.
I previously had the Generic firmware of Xperia Arc S for my Arc, on Ice Cream Sandwich flavor of Android.
Today i started trying to figure out how to flash the CM 9 Rom, because i have it on my Kindle fire, but it failed.
I've did all the steps to Unlock my bootloader, and, even tho my phone is eligible for that ( i checked it on the services menu ), i could not Unlock it.
After retrieving the Key and running the fastboot i had the Message "Remote: oem unlock failed".
After giving up to unlock it, i decided to install "X-Parts" and install the CMW so i could flash the .zip file of the CM9 Right from the SDCard.
Ok, thats what i did:
1. Installed CMW
2. Wiped Data / Factory Reset
3. Wiped Cache
4. Flashed .zip from SDCARD
5. Zip Installed
6. Repeated steps 2 and 3 again
7. Rebooted
Since them, i am stuck at the Bootscreen with the word "Sony" on it, which leads me to think that the rom was not flashed properly, otherwise i would see the cyan / black bootscreen.
Also, i can't manage to boot into "recovery mode" again, i am pressing Power + Volume Down but it is not working.
Any idea of what can i do now ?
How can i install cm9 properly and unstuck my phone ?
Do i need to unlock my BL in order to install CM9 ?
Thanks in advance and sorry about this, but i am sort of desperate this time
Just tried to Flash the "boot.img" file found at the CM9 zip folder using FLASHTOOL, but it says:
"20/016/2012 15:16:27 - INFO - FASTBOOT Output:
sending 'boot' (4916 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s"
My device IS rooted, and i can garantee it.
Just extracted the Kernel.sin file from the .ftf Generic Firmware of ICS Android rom and tried to Flash using the Flashtool via Fastboot mode.
Same error saying that my device must be rooted.
marcelloLins said:
Just extracted the Kernel.sin file from the .ftf Generic Firmware of ICS Android rom and tried to Flash using the Flashtool via Fastboot mode.
Same error saying that my device must be rooted.
Click to expand...
Click to collapse
If the problem resides in rooting your phone, try this http://forum.xda-developers.com/showthread.php?t=1653188 remember, SEARCH is a friend!
in order to flash kernels via fastboot you need your bootloader unlocked
it is bootlooping on CM because you arent using right kernel
not too sure why your having issues unlocking it, but this is probably the first thing you need to tackle
all i can recommend is to keep trying
but im sure someone more helpfull will be along soon!!
and just FYI, just because nobody is answering doesnt mean you need to start a new thread in another section, especially development as its hard enough to navigate without usless threads. just search or use google!
firedeimos said:
If the problem resides in rooting your phone, try this http://forum.xda-developers.com/showthread.php?t=1653188 remember, SEARCH is a friend!
Click to expand...
Click to collapse
Do you understand that i can't even boot my phone ?
How am i supposed to Root it if i can't even make it boot ?
Please, any help here is welcome.
By the way, i AM searching, alot, for more than 4 hours already
its also worth noting that when it says device must be rooted, it is in relation to bootloader not being unlocked (as far as im aware)
yo-meister said:
its also worth noting that when it says device must be rooted, it is in relation to bootloader not being unlocked (as far as im aware)
Click to expand...
Click to collapse
So you are saying that i must try to Unlock my bootloader first, even tho i can't seem to make it boot ?
Not trying to be an ass, but i just can't seem to find a way to do it.
I have my IMEI wrote in a notepad file, but, once i try to unlock it's bootloader, it gives me an error. : "Remote: oem unlock failed!"
Not sure why this is happening, i am following the instructions on Sony Website...
to use a rom like CM, you need a custom kernel and to install a custom kernel you need to unlock bootloader
there are a few that dont require unlock but i havent personally tried these as mine is unlocked
its been a while since i unlocked mine but i seem to remember that you leave the last digit off when typing it in, someone confirm?
i was confused when i was putting in the number as it was longer than what was requested
yo-meister said:
to use a rom like CM, you need a custom kernel and to install a custom kernel you need to unlock bootloader
there are a few that dont require unlock but i havent personally tried these as mine is unlocked
its been a while since i unlocked mine but i seem to remember that you leave the last digit off when typing it in, someone confirm?
i was confused when i was putting in the number as it was longer than what was requested
Click to expand...
Click to collapse
I Love You.
Yes, i just did what you said.
We must ignore the LAST digit of IMEI, i was ignoring the first, since it was ZERO i thought that it would not matter.
Now that i have a new Bootloader Code, i used it and it worked.
Thanks a bunch, now, i must try to continue the process.
I will keep you guys updated
Update 1: The Bootloader is unlocked.
I tried to Flash the kernel.sin using the flashtool and seems like it was flashed correctly but i am still stuck in bootscreen.
Also, i still can't manage to boot in Recovery Mode to flash the CM9 from the SDCARD.
Any ideas?
Update 2: Flashed DoomKernel V04 Successfuly now i am trying to get into Recovery mode so that i can Finally Flash the cm9 rom in the sdcard.
wish me luck
Update 3: After booting into recovery mode, and trying to flash the CM9 .zip file, there is an error.
"Assert Failed: getprop..." From what i know of programming, this looks like the rom trying to assert that the values from the build.prop file must match either "LT18a","LT15i","LT15a" or "anzu".
Is there any way i can fix the file in order to make this "assert" directive works correctly ?
ha your welcome
i lost all my contacts when i first started all this, didnt backup with google account lol
now its just a case of...
put rom on SD CARD
BACKUP
wipe
flash kernel
flash rom
flash wifi modules (if required)
BOOT
and this is the first time i feel like i can say this...hit thanks if i helped haha
Just tried to Toggle the Assert Directives OFF from the DoomKernel but it is still checking for the asserts when trying to flash the Rom.
Any suggestions?
Just tried to Connect VIA ADB with the Phone in Recovery mode, and it worked.
My plan was to Pull the Build.prop file so i could edit and them, paste it back to the phone system so that the assert might work.
Here is the command i tried :
adb devices (OK)
adb pull /system/build.prop c:\build.prop
Error Message : remote object 'system/build.prop' does not exist
What can i do now ?
UPDATE 1: On Recovery Mode i just mounted the System and Data And Ext 2 Partitions and i still cannot seem to PULL the Build.prop File.
UPDATE 2: Flashed the Right kernel from the CM9 Pack, which is the FXP Team Kernel.
Tried to Flash again, now without assert verifications and i am receiving an error : E: Failed to Load Keys
marcelloLins said:
Just tried to Connect VIA ADB with the Phone in Recovery mode, and it worked.
My plan was to Pull the Build.prop file so i could edit and them, paste it back to the phone system so that the assert might work.
Here is the command i tried :
adb devices (OK)
adb pull /system/build.prop c:\build.prop
Error Message : remote object 'system/build.prop' does not exist
What can i do now ?
UPDATE 1: On Recovery Mode i just mounted the System and Data And Ext 2 Partitions and i still cannot seem to PULL the Build.prop File.
UPDATE 2: Flashed the Right kernel from the CM9 Pack, which is the FXP Team Kernel.
Tried to Flash again, now without assert verifications and i am receiving an error : E: Failed to Load Keys
Click to expand...
Click to collapse
So did you manage to get it work?
If not,this is what i would do:
1.Reflash stock fw
2.Root it
3.Install CWM
4.Try it,is it working,if yes flashed custom kernel for rom that i'm trying to flash
5.Then go to CWM and install rom and modules
6.Reboot the phone from CWM Menu and that should be it.It has to work.
I think these steps are easy to follow and no need to be a professional with programing to do it.Hope it will work for you.Cheers
pren22 said:
So did you manage to get it work?
If not,this is what i would do:
1.Reflash stock fw
2.Root it
3.Install CWM
4.Try it,is it working,if yes flashed custom kernel for rom that i'm trying to flash
5.Then go to CWM and install rom and modules
6.Reboot the phone from CWM Menu and that should be it.It has to work.
I think these steps are easy to follow and no need to be a professional with programing to do it.Hope it will work for you.Cheers
Click to expand...
Click to collapse
You mean Stock Firmware from Sony Ericson ?
Where can i find it ?
Is this one ?
http://uploaded.net/file/lpdhtmqi/LT15i_4.0.2.A.0.62_Generic Global World.ftf
I will try to flash it and see where i can get.
I just tried another flavor of CM9 (A nightly build) and i had the same error
marcelloLins said:
Just extracted the Kernel.sin file from the .ftf Generic Firmware of ICS Android rom and tried to Flash using the Flashtool via Fastboot mode.
Same error saying that my device must be rooted.
Click to expand...
Click to collapse
Try to flash an entire official firwmare with flashtool in flashmode mode (a 4.0.3 for easy rooting). So you ended with a working phone in a good mood. After that, root, install recovery, check if phone is always unlocked and try again with CM9.
spidermoon said:
Try to flash an entire official firwmare with flashtool in flashmode mode (a 4.0.3 for easy rooting). So you ended with a working phone in a good mood. After that, root, install recovery, check if phone is always unlocked and try again with CM9.
Click to expand...
Click to collapse
I am downloading this one :
http://uploaded.net/file/lpdhtmqi/LT15i_4.0.2.A.0.62_Generic Global World.ftf
Is there any problem with that ?
Update: These steps solved my problems:
1. Flash the 4.0.3 Android ICS Stock Firmware
2. Flash the Kernel from CM9
3. Wipe Factory and Cache
4. Flash the CM9
5. Flash Gapps
Reboot.
Thanks for all the help guys
Hey guys!
First sorry if this is wrong subforum, or there is an anserw for my problem. I spent about 5 hours on trying to do this.
Firstly I'm a noob in this subject.
I want to flash rom X - Gamer or True Smooth. ( are they any good?)
And I flashed generic .62 on my phone (Xperia Arc ) but I don't know what to do next.
I tried doing all those drivers, CWM, kernel things but I'm just lost now.
I can't learn all the things in one day..
Can someone give me links to best versions of things I need and say step by step how to do it? (or link to good toutorial)
Thank you so much for any help guys!
~ J
you need first flash kernel, then you must open cwm and set your zip file of rom from your sd card
So I need to paste it on SD card in zip? K.
When I'm trying to flash it in fastboot mode that appears "ERROR - This action can only be done in fastboot mode"
Do you have unlocked bootloader?
You have to place the ROM .zip file on the SDcard.
Depending on the bootloader status, you have to either install custom kernel for CWM Recovery or install one in system partition, latter being more riskier.
Someguyfromhell said:
Do you have unlocked bootloader?
You have to place the ROM .zip file on the SDcard.
Depending on the bootloader status, you have to either install custom kernel for CWM Recovery or install one in system partition, latter being more riskier.
Click to expand...
Click to collapse
Yup I've gott my bootlader unlocked.
So what next after placing .zip file on SD?
"- Copy ROM setup file to SD card
- Enter CWM and choose the setup file
- Follow instruction in AROMA installer, customize the ROM as you like and click Install. NOTICE: in Extra section, unchecked item means you don't like it to install with this ROM, so it will be removed if it's already existed (in case you re-install the ROM)"
These are isntructions, so how do I intall CWM correctly?
Phone is rooted, I've got recoveyx on it and i installed CWM for GB. But I can't acces recovery mode. I spammed back button, volume down, hold it..
Please help..
If you have unlocked bootloader, get custom kernel for GB (LuPuS or DooMKernel), flash it in fastboot mode, get into the recovery, factory reset, wipe /system and then install zip from sdcard and choose the ROM zip.
Having unlocked bootloader and then rooting phone, installing CWM via an app is useless, time-wasting and caused many issues.
Okay I'm lost again.. I flashed Lupus and my phone didn't want to start. Blue led flashed but screen was still black..
now I've got android version 2.3.4 (4.0.2.A.0.62) generic.
Bootloader is unlocked (100% sure)
Which kernel should I choose to make this work?
Sorry I'm so nooby in this subject
------------------------------------------------------------------------------------
K I kindof sorted everything. Thx for help!
[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)
Hello,
I've tried everything that the internet has to offer so far and still can't get the newest version to install on my phone without failing somewhere in the installation process.
I feel like asking for help isn't of much use, because it could be everything.
I tried resetting the phone completely with this guide: http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
After that I wanted to install the update again, and still no success.
Next time you make a thread regarding an issue be kind enough to tell us the state of your phone to the best of your knowledge, whether its working or not? does it show the oneplus logo or not..... these things matter plenty!
judging from the what you have mentioned in your post, your main issues is not being able to install the latest update.
try these steps
1. download this file https://www.androidfilehost.com/?fid=24591000424945019 [thanks to namman bhalla for his thread, http://forum.xda-developers.com/oneplus-3/how-to/mirrors-official-oxygen-os-roms-ota-t3410870]
2. copy and paste it onto your phone.
3. now boot into your phones recovery twrp preferred
4. from there choose the option which says..... click install new zip. and select the zip that you downloaded....
it should work if it doesn't, give us a detailed description of what and all you have done with your phone whether you have unlocked the bootloader, whether there is a custom recovery installer and most importantly whether you have nandroid backup of your device.
ajaysoranam said:
Next time you make a thread regarding an issue be kind enough to tell us the state of your phone to the best of your knowledge, whether its working or not? does it show the oneplus logo or not..... these things matter plenty!
judging from the what you have mentioned in your post, your main issues is not being able to install the latest update.
try these steps
1. download this file https://www.androidfilehost.com/?fid=24591000424945019 [thanks to namman bhalla for his thread, http://forum.xda-developers.com/oneplus-3/how-to/mirrors-official-oxygen-os-roms-ota-t3410870]
2. copy and paste it onto your phone.
3. now boot into your phones recovery twrp preferred
4. from there choose the option which says..... click install new zip. and select the zip that you downloaded....
it should work if it doesn't, give us a detailed description of what and all you have done with your phone whether you have unlocked the bootloader, whether there is a custom recovery installer and most importantly whether you have nandroid backup of your device.
Click to expand...
Click to collapse
I tried using that method and it failed, I can get into recovery just fine and my bootloader is unlocked because I flashed twrp
I have a backup I made in twrp.
I got the official support tool (MsMDownloadTool) and I could restore my phone to 3.1.2 but it still crashes apps and is very unstable.
If I now try to install the update again, or try to flash the full OxygenOS 3.2.1 or 3.1.2 I get the Error 7 ("system partition has unexpected contents").
I dont get this error because the system partition couldnt have been modified, because I didnt even start the phone , I just got into recovery and tried updating it.
I'm losing my mind on this.
Sorry if that was a ramble and isn't understandable
calm down!
boot into twrp, wipe system ,data, cache, dalvik. now try flashing the latest full rom i.e. 3.2.2.
try this and let me know....
if it didn't work give me step by breakdown of what you did.....
DeadlyVirez said:
I tried using that method and it failed, I can get into recovery just fine and my bootloader is unlocked because I flashed twrp
I have a backup I made in twrp.
I got the official support tool (MsMDownloadTool) and I could restore my phone to 3.1.2 but it still crashes apps and is very unstable.
If I now try to install the update again, or try to flash the full OxygenOS 3.2.1 or 3.1.2 I get the Error 7 ("system partition has unexpected contents").
I dont get this error because the system partition couldnt have been modified, because I didnt even start the phone , I just got into recovery and tried updating it.
I'm losing my mind on this.
Sorry if that was a ramble and isn't understandable
Click to expand...
Click to collapse
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