Related
Can someone please let me know what I'm missing. I'm rooted, and have even flashed a couple ROMs successfully but most of them will fail to install withan error saying "E: No MD5 file found for [insert whatever ROM]. I'm running TWRP recovery (v.2.3.3.1)
Sprint Galaxy S III
esco_three said:
Can someone please let me know what I'm missing. I'm rooted, and have even flashed a couple ROMs successfully but most of them will fail to install withan error saying "E: No MD5 file found for [insert whatever ROM]. I'm running TWRP recovery (v.2.3.3.1)
Sprint Galaxy S III
Click to expand...
Click to collapse
In the settings (either in "advanced" or on the install menu) on TWRP you can choose to verify the MD5 sum. I believe that if you uncheck that option it should work.
Let me know if this works!
topherk said:
In the settings (either in "advanced" or on the install menu) on TWRP you can choose to verify the MD5 sum. I believe that if you uncheck that option it should work.
Let me know if this works!
Click to expand...
Click to collapse
I have tried that, for multiple ROMs, but still fails.
esco_three said:
I have tried that, for multiple ROMs, but still fails.
Click to expand...
Click to collapse
Are you on the latest version of TWRP? If not, try updating and see if that fixes it
And what rom is it thats failing?
CNexus said:
Are you on the latest version of TWRP? If not, try updating and see if that fixes it
And what rom is it thats failing?
Click to expand...
Click to collapse
I will try the latest version of TWRP and see if that works.
The fail has been happening on multiple ROMs. AOSPA 3.15: Hybrid Mode, MIUIAndroid v4.1 & Avatar ROM to name a few. All the same issue.
No MD5 file found
I am having the same issue! this happened on multiple ROMs from various developers, I have tried every thing suggested and verified rooted.
Badfish63 said:
I am having the same issue! this happened on multiple ROMs from various developers, I have tried every thing suggested and verified rooted.
Click to expand...
Click to collapse
It's not really an error, TWRP just checks to see if there's a corresponding md5 file with the md5 checksum for whatever it is that you're flashing
You can flash any rom perfectly fine without it, but I would make sure that you check the md5sum against the one that the ROM thread or ROM download site gives you
No MD5 file found
CNexus said:
It's not really an error, TWRP just checks to see if there's a corresponding md5 file with the md5 checksum for whatever it is that you're flashing
You can flash any rom perfectly fine without it, but I would make sure that you check the md5sum against the one that the ROM thread or ROM download site gives you
Click to expand...
Click to collapse
Thanks! But I can't seem to even do my first flash! I noticed in any of the ROMS I download for some reason it does not pull the MD5 file. I have downloaded from here XDA and other sites, and android forums. I don't get it. this should be fairly easy according to all the research I have done even before my first attempt.
no md5 file--please help
can someone help me. I am fairly new at custom rom work, but I rooted my galaxy note 3 (Verizon) using kingo, and installed safestrap (latest version) and attempted to install cm11 but while installing it does a md5 file check and says no md5 file found. when I reboot, the Samsung screen comes up and then it goes and stays black. I have to pull battery and go back to stock rom. I have tried reformatting my ext. storage and reinstall..no go. please help. thank you very much in advance.
west1986 said:
can someone help me. I am fairly new at custom rom work, but I rooted my galaxy note 3 (Verizon) using kingo, and installed safestrap (latest version) and attempted to install cm11 but while installing it does a md5 file check and says no md5 file found. when I reboot, the Samsung screen comes up and then it goes and stays black. I have to pull battery and go back to stock rom. I have tried reformatting my ext. storage and reinstall..no go. please help. thank you very much in advance.
Click to expand...
Click to collapse
You might have a better chance at an answer in the forum for your specific carrier and device, this is the forum for the Sprint Samsung Galaxy S3.
topherk said:
In the settings (either in "advanced" or on the install menu) on TWRP you can choose to verify the MD5 sum. I believe that if you uncheck that option it should work.
Let me know if this works!
Click to expand...
Click to collapse
I'm experiencing the same issue.
L710 currently Slimbean, updating to Slimkat 4.4.2 I get the fail for the MD5
I have TWRP 2.6.0.0
I don't see any uncheck MD5 option only in settings and these are already unchecked.
When flashing back to Slimbean 4.3 I get the error
E: error opening '/data/lost + found'
E: error no such file or directory
But it still passes and I'm on 4.3
Reivaj1803 said:
I'm experiencing the same issue.
L710 currently Slimbean, updating to Slimkat 4.4.2 I get the fail for the MD5
I have TWRP 2.6.0.0
I don't see any uncheck MD5 option only in settings and these are already unchecked.
When flashing back to Slimbean 4.3 I get the error
E: error opening '/data/lost + found'
E: error no such file or directory
But it still passes and I'm on 4.3
Click to expand...
Click to collapse
It finally worked!
I updated TWRP to the latest 2.6.3.1 and Slimkat flashed with no problems.
This new setup took me for a loop, wasn't expecting it. After all said and done, I am running. :good: :good:
Reivaj1803 said:
It finally worked!
I updated TWRP to the latest 2.6.3.1 and Slimkat flashed with no problems.
This new setup took me for a loop, wasn't expecting it. After all said and done, I am running. :good: :good:
Click to expand...
Click to collapse
I was going to suggest that you should try flashing over the new TWRP recovery. Best of luck!
Dolby
CNexus said:
Are you on the latest version of TWRP? If not, try updating and see if that fixes it
And what rom is it thats failing?
Click to expand...
Click to collapse
I am trying to flash dolby. The flash is successful but the app icon doesn't appear on the screen. In the recovery log it says md5 file not found. I've tried flashing viper too but the condition is the same. Please help.
Mr. Struck said:
You might have a better chance at an answer in the forum for your specific carrier and device, this is the forum for the Sprint Samsung Galaxy S3.
Click to expand...
Click to collapse
1. Installed Stock ROM, using Odin3_v3.11.2 (Run as Adminstrator)
N900XXUEBPB1_N900ODDEBPB1_N900DDUEBOB1_HOME.tar.md5
My "Samsung Galaxy Note 3 SM-N900" Running on 5.0 lollipop
2. I have rooted my "Samsung Galaxy Note 3 SM-N900" using followiing file using Odin3_v3.11.2 (Run as Adminstrator)
CF-Auto-Root-ha3g-ha3gxx-smn900
3. Later I've installed TWRP recovry, using Odin3_v3.11.2 (Run as Adminstrator)
twrp-3.0.2-0-ha3g.img_safe.tar
Now when I try to install MIUI for "Samsung Galaxy Note 3 SM-N900" port ROM, either getting Failed or If it is success my phone does not startup hung at SAMSUNG logo (Waited for nearly 2 hrs).
miui_n900_lushengduan_6.5.27_19d567b4f3_4.4.zip
miui_n9005_bhflower_6.5.27_e7133a52f8_4.4.zip
- Tried above method after wiping the cache and internal drive still the same.
- Tried to install from external card same error
- Tried to install from internal card same error
PLEASE HELP.I HAVE STRUGGLING FROM LAST 1 WEEK WITH ALL THE TRIEL AND ERROR METHOD.
Is there any solution to this problem? im also experiencing today.
my unit is galaxy n3 international im running with the rom cm 14.1 cyanogenmod using TWRP 3.0.2-1 and i want to install different rom's but i always got stuck whenever i swipe to flash the new rom it say's no md5 after a minute my system is restarting and nothing's happen.
ken041387 said:
Is there any solution to this problem? im also experiencing today.
my unit is galaxy n3 international im running with the rom cm 14.1 cyanogenmod using TWRP 3.0.2-1 and i want to install different rom's but i always got stuck whenever i swipe to flash the new rom it say's no md5 after a minute my system is restarting and nothing's happen.
Click to expand...
Click to collapse
Turn off md5 verification in twrp settings
I also have this problem on my galaxy alpha sm-g850f I'm running TWRP 2.8.7.0 it says "no Md5 file found" can someone help me
so, i flashed the kitkat bootloader from odin, then flashed the zip from philz touch recovery. the kernel splash screen stayed on for a long time, then the screen went out, and it loaded to the kernel splash, then to recovery. then i realized i hadnt wiped, so i flashed the kitkat stock rom through odin, installed philz touch recovery, did a full wipe, then installed the zip, and the same thing happened. being a new member with less than 10 posts i cant post on the official thread, so... whats the deal? what could the problem be?
EDIT: my bad everyone. i found a misleading link to philz, the newest version in that thread was not the newest version.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n5110/philz_touch_6.41.6-n5110.tar.md5 use this. if you have the same problem
tooandrew said:
so, i flashed the kitkat bootloader from odin, then flashed the zip from philz touch recovery. the kernel splash screen stayed on for a long time, then the screen went out, and it loaded to the kernel splash, then to recovery. then i realized i hadnt wiped, so i flashed the kitkat stock rom through odin, installed philz touch recovery, did a full wipe, then installed the zip, and the same thing happened. being a new member with less than 10 posts i cant post on the official thread, so... whats the deal? what could the problem be?
Click to expand...
Click to collapse
in aroma choose the stock kernel option. I had the same bootloop problem ....it kept going into recovery.
After choosing the stock kernel everything was smooth.
off course pls confirm that you are using the correct ROM version
for 5100 version is 1.2
1.3 is only for 5110
I didn't see any kernel options let me make a nandroid and run it again. and yeah I have the 5110. Thanks
hey, i reinstalled it, there were no kernel options, but i left the bootanimation option on stock samsung, and i had been using the XAR region, so i tried btu this time, because thats what the stock rom i have installed is. still crashes to recovery
EDIT: and after restoring my nandroid, i get to the rom splash screen, and it just loops there.
I have the same problem...Where is the Stock KK that u can flash thru Odin ???
ronny71 said:
I have the same problem...Where is the Stock KK that u can flash thru Odin ???
Click to expand...
Click to collapse
Here is the link to Stock KK:
http://www.sammobile.com/firmwares/3/?download=29611
Also download Odin v3.09 from the same link.
Then follow these instructions:
1) Unzip the Download zip file, you will get N5110XXDNE1_N5110OXADNE1_HOME.tar.md5
2) Put the tablet in Download mode
3) Install N5110XXDNE1_N5110OXADNE1_HOME.tar.md5 using "PA" option of ODIN.
4) It will take a while, let it finish.
5) If that works, reboot back to download mode
6) Install latest Philz recovery, using ODIN's PA option.
7) Reboot into recovery, and install any custom ROMS.
Note: This will trip your KNOX counter
pvsgh said:
Here is the link to Stock KK:
http://www.sammobile.com/firmwares/3/?download=29611
Also download Odin v3.09 from the same link.
Then follow these instructions:
1) Unzip the Download zip file, you will get N5110XXDNE1_N5110OXADNE1_HOME.tar.md5
2) Put the tablet in Download mode
3) Install N5110XXDNE1_N5110OXADNE1_HOME.tar.md5 using "PA" option of ODIN.
4) It will take a while, let it finish.
5) If that works, reboot back to download mode
6) Install latest Philz recovery, using ODIN's PA option.
7) Reboot into recovery, and install any custom ROMS.
Note: This will trip your KNOX counter
Click to expand...
Click to collapse
thats the thing.... i flashed it, i have stock rooted kitkat running fine, i have philz recovery running fine, but when i try to flash the custom kitkat rom, i wipe, flash the zip, the aroma installer boots i choose a few options, the aroma installer completes, then i reboot and it just crashes to recovery, no matter how many times i try, how many factory resets i do, anything. knox is tripped, but i can't run the rom. i had the 4.2.2 custom touchwiz from the same developer running fine, but then i decided i had to have kitkat, and.... nothing. it simply won't run.
if it matters, i am already running the same stock rom you linked to, 4.4.2 btu
EDIT: just for the record, i am not new to this in general, only this particular device - my sprint galaxy s3 is running carbon rom, my galaxy gear is running null rom, i flashed N3BULA on my dad's verizon galaxy note two, and ive already decided on a rom for the note 3 i am getting at the end of july.
this is just my first time encountering this problem, all assistance with this matter is greatly appreciated.
tooandrew said:
thats the thing.... i flashed it, i have stock rooted kitkat running fine, i have philz recovery running fine, but when i try to flash the custom kitkat rom, i wipe, flash the zip, the aroma installer boots i choose a few options, the aroma installer completes, then i reboot and it just crashes to recovery, no matter how many times i try, how many factory resets i do, anything. knox is tripped, but i can't run the rom. i had the 4.2.2 custom touchwiz from the same developer running fine, but then i decided i had to have kitkat, and.... nothing. it simply won't run.
if it matters, i am already running the same stock rom you linked to, 4.4.2 btu
EDIT: just for the record, i am not new to this in general, only this particular device - my sprint galaxy s3 is running carbon rom, my galaxy gear is running null rom, i flashed N3BULA on my dad's verizon galaxy note two, and ive already decided on a rom for the note 3 i am getting at the end of july.
this is just my first time encountering this problem, all assistance with this matter is greatly appreciated.
Click to expand...
Click to collapse
Ok, so first try to validate the MD5 of the file that you are installing.
if you are installing "CivZ-FlexNote8.0_KK-Rev1.3-N5110_signed.zip" then the MD5 should match as below:
b8abeb1ec9535ef526d02ef402788359
Validate the MD5 in PC as well as Tablet. Sometime you get a good download on PC, but when you copy it to Phone/tablet file might not get copied properly.
Second option you can try to install another 4.4.2 based ROM:
http://forum.xda-developers.com/showthread.php?t=2763274
Again validate the MD5 before installing.
pvsgh said:
Ok, so first try to validate the MD5 of the file that you are installing.
if you are installing "CivZ-FlexNote8.0_KK-Rev1.3-N5110_signed.zip" then the MD5 should match as below:
b8abeb1ec9535ef526d02ef402788359
Validate the MD5 in PC as well as Tablet. Sometime you get a good download on PC, but when you copy it to Phone/tablet file might not get copied properly.
Second option you can try to install another 4.4.2 based ROM:
http://forum.xda-developers.com/showthread.php?t=2763274
Again validate the MD5 before installing.
Click to expand...
Click to collapse
Md5 matches. I'm going to download am earlier update and dirty flash, see if that helps
Hey, those who were having problems, you probably got the wrong recovery. i had two versions of philz on my computer, and i flashed philz 5 instead of philz 6.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n5110/philz_touch_6.41.6-n5110.tar.md5
the other guy who was boot looping, that is the link to the recovery you should use. everything will be fine with that one
tooandrew said:
Hey, those who were having problems, you probably got the wrong recovery. i had two versions of philz on my computer, and i flashed philz 5 instead of philz 6.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n5110/philz_touch_6.41.6-n5110.tar.md5
the other guy who was boot looping, that is the link to the recovery you should use. everything will be fine with that one
Click to expand...
Click to collapse
Thanx my man...u hit it right on the head...Wrong Recovery...I hope everyone who has this problem reads ur post...Thanx again Buddy...:good::good:
Ok guys I am a noob (also new to these forums) and I'm having a lot of trouble with my phone. The other day, I rooted my phone using towelroot and confirmed it using root checker. then, I downloaded ROM manager as advised by a friend. i followed the instructions and installed Clockworkmod Recovery onto my AT&T Galaxy S3. Feeling I was finally ready to install a ROM, i tried to download Cyanogenmod 10.3.1 only to have it be "downloading" for over 14 hours without it completing. From there, i did some research and decided to utilize the Cyanogenmod Installer. it seemed to work perfectly, even showing the cyanogenmod logo under when my devicec turned on, until it told me to reboot my device. i entered clockworkmod recovery mode to officially reboot it. when i selected "reboot system now" it said "Root access possibly lost. Fix?". i was given the options to say "No" and "Yes - Fix root (/system/xbin/su). no matter which one i try, my phone boots to the stock touchwiz OS. I have installed and reinstalled both superuser, superSU, and ROM manager to no success. What am i doing wrong?
Try flashing Philz Touch via Odin and use that to flash a custom ROM.
From what I recall, CM ROMs are already rooted.
audit13 said:
Try flashing Philz Touch via Odin and use that to flash a custom ROM.
From what I recall, CM ROMs are already rooted.
Click to expand...
Click to collapse
CM is already rooted? What does that mean? I have a feeling that I will be unable to flash any ROMs due to my "possible loss of root access." Thank you for your patience as I am a noob and am very stressed out as this is my only phone.
I see two areas that are potential problems for flashing that rom. If it took 14 hours to download, its highly likely a corrupted download. But also, you may be on too new firmware. Cm uses asserts in the updater-script to check that you have the right base firmware/bootloader build. They dont update this so when newer firmware is released it will no longer flash because the script doesn't see it as allowed.
Anytime you have issues flashing something in recovery, you should copy the recovery log to sd. This will tell you what happened. I suspect it simply didn't flash, but without the log, theres no way we can tell what happened.
Also, you do not need to be rooted to flash anything from recovery. Just flash the recovery, then flash a rom from there. Nearly all roms you will ever see are already rooted. Non rooted roms are very rare and are generally only used as an alternate way to revert to stock.
I dont use cwm, but if im not mistaken, it seems to always ask to fix root. I dont know why, but I see people ask about it frequently.
I use TWRP, so try that, or philz as suggested by audit13. Just watch the flash progress for any errors and copy the log.
[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