So recently I downloaded the cm12 nightly ROM on my Galaxy note 3 (sprint). Everything works fine, but I can't make/receive calls or text. I took it to the Sprint store and they told me to backup the ROM, then restore the backup of the stock ROM and do a profile update, then restore the custom ROM after that... Problem is that when I went back to the stock ROM I still had the problem, even after the profile update... this isn't my first time flashing ROMs, I've successfully flashed C-ROM and CM ROMs in the past and never came across this problem. Has anyone encountered a similar problem? And found a solution?
Odin stock tar file.
Ammar335i said:
So recently I downloaded the cm12 nightly ROM on my Galaxy note 3 (sprint). Everything works fine, but I can't make/receive calls or text. I took it to the Sprint store and they told me to backup the ROM, then restore the backup of the stock ROM and do a profile update, then restore the custom ROM after that... Problem is that when I went back to the stock ROM I still had the problem, even after the profile update... this isn't my first time flashing ROMs, I've successfully flashed C-ROM and CM ROMs in the past and never came across this problem. Has anyone encountered a similar problem? And found a solution?
Click to expand...
Click to collapse
What kernel are you using? You should be using the Stock CM12 Kernel with the same build date as your CM12 Install.
If you are running a different kernel on Official CM12 it will cause you to loose voice service. This issue started on April 03 2015 Nightly and hasn't been fixed yet.
What Radio/Baseband are you using? You should be on NH7 or NK4 when running CM12.
I will assume you are doing a clean install each time before flashing CM12 by performing a factory reset in recovery which wipes data, cache, and dalvik.
If you open up your dialer and dial *#*#4636#*#* it opens up a secret testing menu. Go to Phone Information and check if your "Set preferred network type:" is set as "LTE/CDMA". If it is not, do so and see if that changes anything.
Ammar335i said:
So recently I downloaded the cm12 nightly ROM on my Galaxy note 3 (sprint). Everything works fine, but I can't make/receive calls or text. I took it to the Sprint store and they told me to backup the ROM, then restore the backup of the stock ROM and do a profile update, then restore the custom ROM after that... Problem is that when I went back to the stock ROM I still had the problem, even after the profile update... this isn't my first time flashing ROMs, I've successfully flashed C-ROM and CM ROMs in the past and never came across this problem. Has anyone encountered a similar problem? And found a solution?
Click to expand...
Click to collapse
Sounds to me like you have bad download of CM12. I would download it again. Compare properties of both downloads see if you have the same number of bytes. Make sure you are rooted, stock OS, and a custom recovery installed. With the bootloader current binary and system status both having a "custom" status. Then try to flash CM12 through your custom recovery again. For more info just click flashing roms in my signature.
Get your carrier to check if your imei is blacklisted on their eir node connected to imeidb.org
Sent from my D5803 using XDA Free mobile app
rbeavers said:
Odin stock tar file.
Click to expand...
Click to collapse
Sorry I'm fairly new to this, you're gonna have to tell me how to find that
Sent from my SM-N9005 using XDA Free mobile app
Philux-X said:
What kernel are you using? You should be using the Stock CM12 Kernel with the same build date as your CM12 Install.
If you are running a different kernel on Official CM12 it will cause you to loose voice service. This issue started on April 03 2015 Nightly and hasn't been fixed yet.
What Radio/Baseband are you using? You should be on NH7 or NK4 when running CM12.
I will assume you are doing a clean install each time before flashing CM12 by performing a factory reset in recovery which wipes data, cache, and dalvik.
If you open up your dialer and dial *#*#4636#*#* it opens up a secret testing menu. Go to Phone Information and check if your "Set preferred network type:" is set as "LTE/CDMA". If it is not, do so and see if that changes anything.
Click to expand...
Click to collapse
I did the secret testing menu and changed the preferred network to LTE/CDMA and my calls started working and I started receiving sms (thank you). I can't send SMS though. Plus I lost data connectivity.
Also, I did do clean installs.
Sent from my SM-N9005 using XDA Free mobile app
Your on the wrong version of CM12. You need to be using hltespr. Your on hlte.
Download from here
http://download.cyanogenmod.org/?device=hltespr
Philux-X said:
Your on the wrong version of CM12. You need to be using hltespr. Your on hlte.
I tried downloading hltespr using TWRP but it kept saying unsuccessful, so I looked it up and others were having the same problem. So I switched to cwm recovery and it also said unsuccessful, and It gave the message saying that the ROM was hltespr and this device was hlte. Also all the other ROMs I downloaded in the past were all hlte and they worked fine.
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
The old versions might have worked, but the new ones will not because of telephony changes done by CM on April03. Its getting hung up on the device name from build.prop. At least that has been my experience in the past.
Do an advanced wipe. Data/System/Cache/Dalvik
Do a Reboot to recovery
Then flash hltespr.
I'm using TWRP 2.8.5 btw.
Other things to try if that does not work:
You can try flasing hltespr ontop of hlte and see if that works.
Try flashing ViSXN3N custom rom and then flash hltespr.
Philux-X said:
The old versions might have worked, but the new ones will not because of telephony changes done by CM on April03. Its getting hung up on the device name from build.prop. At least that has been my experience in the past.
Do an advanced wipe. Data/System/Cache/Dalvik
Do a Reboot to recovery
Then flash hltespr.
I'm using TWRP 2.8.5 btw.
Other things to try if that does not work:
You can try flasing hltespr ontop of hlte and see if that works.
Try flashing ViSXN3N custom rom and then flash hltespr.
Click to expand...
Click to collapse
Okay I'll try that now, what is ViSXN3N custom ROM? I can't find anything on it
Sent from my SM-N9005 using XDA Free mobile app
ViSXN3N is here
http://forum.xda-developers.com/showthread.php?t=2696396
Philux-X said:
ViSXN3N is here
http://forum.xda-developers.com/showthread.php?t=2696396
Click to expand...
Click to collapse
Same problem, it says that this is for sm-n900p hltespr and i have hlte... also i just noticed that the message i have on the bottom of my posts say sent from my Sm-N9005..? is my phone confused? lol
update
So I installed cm11 to see if it would work and it did... I guess that means it was just the ROM? Although I loved the interface of cm12, so im going to try and flash a different version to see if that works.
Turns out when I first rooted my phone I downloaded a hlte recovery. After flashing a hltespr recovery using Odin and then flashing the correct hltespr ROM, everything worked fine. Thanks for the help guys
Sent from my SM-N900P using XDA Free mobile app
Related
Anyone have an idea why every time I install an aosp rom it glitches at the Samsung boot screen then just goes black and I have to pull the battery? I've installed clean, jelly beans and jedi Rom without issue. Any help is appreciated.
Update your twrp then try again. Make sure your doing full wipes and flashing gapps
Sent from my SCH-I605 using Tapatalk 2
hopesrequiem said:
Update your twrp then try again. Make sure your doing full wipes and flashing gapps
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Just updated my TWRP to 2.4 and did what you suggested with the wiping and same problem.
The Samsung Galaxy screen glitches to half way off the screen, then goes off, then comes back on then the whole thing goes black and nothing.
I'm going to try another rom and see if it still does it as well.
dudeicles said:
Just updated my TWRP to 2.4 and did what you suggested with the wiping and same problem.
The Samsung Galaxy screen glitches to half way off the screen, then goes off, then comes back on then the whole thing goes black and nothing.
I'm going to try another rom and see if it still does it as well.
Click to expand...
Click to collapse
Even with another ROM it doesn't seem to want to work. It's really weird, because any Touchwiz ROM works fine, it only does it on AOSP roms..... I'm hoping someone knows what the fix for this is.
dudeicles said:
Even with another ROM it doesn't seem to want to work. It's really weird, because any Touchwiz ROM works fine, it only does it on AOSP roms..... I'm hoping someone knows what the fix for this is.
Click to expand...
Click to collapse
Odin to stock then re unlock and try this all again? I'm not sure what else you can try. I flip between aosp and tw almost daily
Sent from my SCH-I605 using Tapatalk 2
The Note 2 that couldn't...
Sent from my SCH-I605 using Tapatalk 2
1ManWolfePack said:
The Note 2 that couldn't...
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Heh I think I can I think I can...I was thinken are you trying to flash the file that the post links to because thats not the right one you need to get the note 2 lte one tolte..just a though I downloaded the wrong one first but caught it
http://changelog.bbqdroid.org/#t0lte/cm10.1/next
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Acery said:
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Click to expand...
Click to collapse
Yeah it can't hurt even if they don't say that
Sent from my SCH-I605 using Tapatalk 2
Acery said:
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Click to expand...
Click to collapse
Would it help in any way to change to CWM when flashing my AOSP roms?
dudeicles said:
Would it help in any way to change to CWM when flashing my AOSP roms?
Click to expand...
Click to collapse
I would try cwm, I had a gs3 that couodnt flash anything with cwm but could with twrp, my note was the opposite, cwm was awful on it.
Just ran into something very interesting . When I installed Rom Manager and flashed the CWM recovery, I rebooted and my boot screen did the exact same thing it was doing installing AOSP roms. It would seem my problem may just be CWM.
dudeicles said:
Just ran into something very interesting . When I installed Rom Manager and flashed the CWM recovery, I rebooted and my boot screen did the exact same thing it was doing installing AOSP roms. It would seem my problem may just be CWM.
Click to expand...
Click to collapse
I've heard too many issues with cwm to even try it. Twrp has been flawless for me so why switch? If it ain't broke, don't fix it.
Sent from my SCH-I605 using Tapatalk 2
Ok, so update - Odin'd back to stock and re-rooted using the Casual method. I have the most recent TWRP installed and when i install the AOSP rom it does the exact same thing. I'm thinking about videotaping what the boot animation does and maybe someone can look at it and see what the cause may possibly be.
If anyone has any other suggestions i'm all ears. Again, any rom based on STOCK works without issue (Clean Rom, Jelly Beans and Jedi), but only AOSP roms (And CWM) crash the phone at "Samsung Galaxy Note II" screen on startup.
Thanks for the suggestions so far, just weird it's not working. I may have the single note 2 to never run AOSP roms. LOL
so... oddly enough i still have trouble installing AOSP roms. the only AOSP rom i have been able to install so far is Paranoid Droid. I am slowly trying each one just to see which one i can force to work. Am I the only person who can't just flash whichever rom I want whenever?
Anyone with other ideas on this? I was frequently flashing back and forth between TW and AOSP. The other day I tried to flash AOSP again and get a failed message in TWRP. Already using latest version of TWRP. I then restore a backup of TW. Download again, verify md5, get failed message again. And yes, I wiped everything...same thing I do everytime. Now I have tried to DL and flash multiple different AOSP roms and I get failed everytime. Decided to try CWM recovery and that just aborts. I have NO problems flashing TW roms though
Follow the advice to Odin back to stock and start over. Otherwise, get a replacement and tell them it's acting weird and slow haha.
Sent from my SCH-I605 using xda app-developers app
Same here!!
spydersilk said:
Anyone with other ideas on this? I was frequently flashing back and forth between TW and AOSP. The other day I tried to flash AOSP again and get a failed message in TWRP. Already using latest version of TWRP. I then restore a backup of TW. Download again, verify md5, get failed message again. And yes, I wiped everything...same thing I do everytime. Now I have tried to DL and flash multiple different AOSP roms and I get failed everytime. Decided to try CWM recovery and that just aborts. I have NO problems flashing TW roms though
Click to expand...
Click to collapse
I currently have a Tmobile Note 2. And i recently ran into the same issue. I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb. I also notice that it changed my device id to an SGH-i317, which is an ATT Note 2. The rom was a port from an ATT rom of course, but if it was for ATT, it wouldn't work on my device right? I installed GOOmanager, and flashed the OPEN INSTALL SCRIPT. Which it flashed the ATT version. Everything still worked. I flashed back to stock, and updated OTA. Still nothing. I've also noticed that, if i can open the zip file on my pc, it will work on my phone. For some reason, The AOSP files read invalid. While the Touchwiz roms open like a regular zip file.
Any help is appreciated. Hope some of this info helps.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
slinky42 said:
I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
Click to expand...
Click to collapse
This is standard on 4.2.2 ROMs. It is related to the multi-user implementation.
slinky42 said:
I currently have a Tmobile Note 2. And i recently ran into the same issue. I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb. I also notice that it changed my device id to an SGH-i317, which is an ATT Note 2. The rom was a port from an ATT rom of course, but if it was for ATT, it wouldn't work on my device right? I installed GOOmanager, and flashed the OPEN INSTALL SCRIPT. Which it flashed the ATT version. Everything still worked. I flashed back to stock, and updated OTA. Still nothing. I've also noticed that, if i can open the zip file on my pc, it will work on my phone. For some reason, The AOSP files read invalid. While the Touchwiz roms open like a regular zip file.
Any help is appreciated. Hope some of this info helps.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
Click to expand...
Click to collapse
Did you ever get your phone to install the AOSP Roms? Mine worked when l just let the phone sit. Now it works fine all the time.
Sent from my SCH-I605 using xda app-developers app
I've had no luck with KitKat getting provisioned properly. Every time it shows no MIN or Mdn out prl. I can flash back to twrp and restore slimbean and have no connection issues. I've successfully flashed stock mc3 in cwm and gotten service then tried cm11 and no luck.
Anyone have any suggestions?
Use cwm recovery for kitkat
Sent from my SCH-I605 using XDA Premium 4 mobile app
Use CWM
nikhil.kdhand said:
Use cwm recovery for kitkat
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did. I was in twrp on slimbean. Flashed CWM touch, booted into CWM recovery. From there I factory reset and wiped system. Flashed CM11, PA_GAPPS 4.4 12/12/13 and had no service. Flashed Beans stock mc3 in CWM and had signal. Then tried CM11 again after having service in CWM with stock. At this point I'm back in TWRP with Slimbean.
Thanks in advance!
Hope you are using cm11 which is 2611 built
Sent from my SCH-I605 using XDA Premium 4 mobile app
cm11
nikhil.kdhand said:
Hope you are using cm11 which is 2611 built
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I previously had the same issue with the 2611 build and I'd now happening on the 12-9 build
Same Issue
Currently having the issue, i am always stuck in roaming and after surfing the web about the issue following some other phone guides as well i am still having the issue, after flashing kitkat, still no service. I also went back to stock and reset the phone as well, also tried doing a refresh on the antenna as well still no cigar.
problem solved!
joshsikora said:
Currently having the issue, i am always stuck in roaming and after surfing the web about the issue following some other phone guides as well i am still having the issue, after flashing kitkat, still no service. I also went back to stock and reset the phone as well, also tried doing a refresh on the antenna as well still no cigar.
Click to expand...
Click to collapse
After some thinking, I noticed that the mj9 stock ROM was available. I odin'd back to stock, ran casual, used odin to flash twrp 2.6.3.1, flashed beanstown stock odexed mj9 ROM. After verifying signal, I did factory reset from twrp, and installed sbrissen 12-9 ota 4.4 ROM and gapps 12-13. Success. Going to backup and try slimkat next, but thought I'd update you all.
Hi there,
My SIII i9300 has been rooted and flashed with CM from CM 10.x to 11.x. Hoewever, recently it started to not give any audio during voice calls trough the normal mic. Speakers do work.
So, i've tried reflashing, clearing cache / dalvik etc. To no avail.
I then tried stock rom and for some reason this seems to do the trick.
As i'm not really a great fan of the Samsung bloatware and the 'awesome' skin overlay of samsung i would like to fix this issue.
I also tried some different roms to no avail. ( Also, i installed cm 10.2 because that used to be working fine)
I then tried installing different modems via CWM and ODIN. (BUELK1) and (CEEL1). It's a dutch phone on vodafone.
Any information would be greatly appreciated!
Btw, currently i'm running CM 11 nightly see below. Android 4.4.2
My baceband is currently i9300CEELL1
Kernel version 3.0.64-CM-gb1c5066
CM 11-20140228
greetinges, Volc
Try installing the ROM before wiping everything, including System ( data is recommended, as long as you don't have something important not backed up). And with 4.4 try to use MK6 modem or higher.
Sent from my GT-I9300 using XDA Premium 4 mobile app
?
Andr3y29 said:
Try installing the ROM before wiping everything, including System ( data is recommended, as long as you don't have something important not backed up). And with 4.4 try to use MK6 modem or higher.
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi Andry!
Many thanks for your reply. So I should turn back stock, install cm and that mk6 without wiping? I'm not sure if cm will install without the wipe..
The mk6 modem, do you have any clue where to search it?
Regards,volc
volcomoo said:
Hi Andry!
Many thanks for your reply. So I should turn back stock, install cm and that mk6 without wiping? I'm not sure if cm will install without the wipe..
The mk6 modem, do you have any clue where to search it?
Regards,volc
Click to expand...
Click to collapse
I thought you found the modems on www.boeffla-kernel.de . You can find them in the Download section. Also, if you are on CM11 (or any other ROM actually), you should download the ROM tog want to flash on your external SD Card, reboot into recovery, wipe system, cache, dalvik cache and data, flash the ROM, reboot system and use it for a few moments at least ( I would recommend you do that so that you won't get bootloop). Then, reboot into download mode, connect phone to Odin and flash the ROM. I would recommend wipe shading cache and dalvik cache, just for a flawless experience.
Sent from my GT-I9300 using XDA Premium 4 mobile app
I saw this phone firsthand. (Hi volcomoo!)
The roms were flashed OK, double triple quadruple wiping probably wont make any difference.
The weird thing is that with CM installed there seems to be a hardware issue, when we flash the phone back to stock, everything works. I guess the developers will say "logcat or it didn't happen"....
sodeknetters said:
I saw this phone firsthand. (Hi volcomoo!)
The roms were flashed OK, double triple quadruple wiping probably wont make any difference.
The weird thing is that with CM installed there seems to be a hardware issue, when we flash the phone back to stock, everything works. I guess the developers will say "logcat or it didn't happen"....
Click to expand...
Click to collapse
Heuj Sodeknetters
Flashing the MK6 modem didn't work either. Tried dozens of roms. Anyone else might have a clue?
My google foo turned into dust so xda is all i got left ^^
We need to make a logcat of when it fails i guess
I had this problem before when i was runming stock . i just sent with the flow and after a month or so i got fixed by itself .
Hope i helped
Sent from my GT-I9300 using xda app-developers app
Hey Guys
I'm a experienced flasher but I have ran into a issue with flashing roms on my Note 3. I had recently just been running stock rooted rom (basically I rooted my phone the day it came out with Sprint and never have update anything). So when I noticed that ny son's note 3 (note rooted) got an update recently, I decided to look for an updated base and broadband for my phone, which I thought I had found. So after so help with figuring out which update I needed to do, I figured NH7 was the latest. Finally got my phone updated or so it appeared.
So this week I've been trying desperately to update to MOAR S5 PORT (NE5 based I believe) I followed the instructions carefully and tried all 3 versions. All failed. So I restored my phone. Tonight I tried flashing flashing Pac-man rom. Same thing happened. Failed during install.
Can you guys take a look at my setup and tell me what may be wrong? Doing a clean install each time.
Sent from my SM-N900P using XDA Premium 4 mobile app
UPDATED 10/24/2014:
I had to reflash all the Note 3 stock tar's in order. Then root with Chainfire Auto Root. Then install Clockwork MOD Recovery. Now I can flash roms.
shaun0207 said:
Hey Guys
I'm a experienced flasher but I have ran into a issue with flashing roms on my Note 3. I had recently just been running stock rooted rom (basically I rooted my phone the day it came out with Sprint and never have update anything). So when I noticed that ny son's note 3 (note rooted) got an update recently, I decided to look for an updated base and broadband for my phone, which I thought I had found. So after so help with figuring out which update I needed to do, I figured NH7 was the latest. Finally got my phone updated or so it appeared.
So this week I've been trying desperately to update to MOAR S5 PORT (NE5 based I believe) I followed the instructions carefully and tried all 3 versions. All failed. So I restored my phone. Tonight I tried flashing flashing Pac-man rom. Same thing happened. Failed during install.
Can you guys take a look at my setup and tell me what may be wrong? Doing a clean install each time.
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wipe wipe Wipe and when it fails to flash then restart recovery And it will flash then ....
So wipe 3 times. Then when it fails. Reboot to recovery and flash again? Do I need to wipe again before flashing?
Sent from my LGLS990 using XDA Free mobile app
shaun0207 said:
So wipe 3 times. Then when it fails. Reboot to recovery and flash again? Do I need to wipe again before flashing?
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
Any time you wipe the system partition, you MUST restart TWRP recovery before flashing the rom of your choice,.. or it'll fail every time.
Ok. I will try that noq
Sent from my SM-N900P using XDA Premium 4 mobile app
shaun0207 said:
Ok. I will try that now
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my SM-N900P using XDA Premium 4 mobile app
shaun0207 said:
Ok. I will try that noq
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Let us know how it goes. Happy flashing.
So I wiped everything. Tried to install and it failed. So i go to reboot to recovery and it ask me about superuser. But it doesnt install because their is no OS. REBOOT to recovery and it fails again
Do I need to format data?
Actually I dont even see a option in TWRP to format data
I wonder if I should try a dirty flash?
I would odin flash a full stock nh7. To get you all the way to nh7. I see you are still at nab on one. I had problems when they weren't all the same. I could be wrong.... I'm a noob. lol
Then, root with chanfires autoroot. Install your recovery. Then, flash your rom of choice.
NOTE: I said nh7.... but, if the rom you want to use isn't, then odin to nab or whatever the rom you want to run is. I don't know about downgrading, could make a brick.... lol
Research everything I said before you do anything! Or wait for someone to correct what's wrong with what I said! I take no responsibility for what you do to your phone!
one of your issues is you updated wrong! unless you were on nc5 you shouldnt jump right to nh7. you have to update in order to insure no issues. so if oyu were nqb or ever mi3 you need to go in order mi3>nab>nc5>nh7
Chainfires auto root.....http://download.chainfire.eu/362/CF-Root/CF-Auto-Root/CF-Auto-Root-hltespr-hltespr-smn900p.zip
Here is Supersu download.....so when you check to see if you have root.....it will all be good.......http://download.chainfire.eu/578/SuperSU/UPDATE-SuperSU-v2.14.zip
Odin v3.07.......http://forum.xda-developers.com/showthread.php?t=1738841
now you can try to go back to stock and flash whichever you are going to flash........or you can do a reflash of whatever you want....I have notice a losss of root also too.
also make sure to look into all those fixes for security patches xda has for our phone......download and scan with bluebox security and search for any open links that have a fix here on xda........
this happened to me the other weekend and it took an afternoon to dig all resources to figure out why and what i needed to do........I started rooting with a samsung moment......
I am back to stock.....no complaints.....but only did to get home before i go back to a rom.......hope we have helped....
Thanks guys. I will try all of these
shaun0207 said:
Thanks guys. I will try all of these
Click to expand...
Click to collapse
to get updates to stick via odin. remove sd card too. and when you update each version. boot to stock recovery wipe phone. flash again. what i do on each update. never had a single issue.
shaun0207 said:
Do I need to format data?
Click to expand...
Click to collapse
Yes you have to do that.. Also I believe you have to be in twrp 2.8 for kitkat I was having problems too until I installed the new Twrp!
bigkev904 said:
Yes you have to do that.. Also I believe you have to be in twrp 2.8 for kitkat I was having problems too until I installed the new Twrp!
Click to expand...
Click to collapse
I dont see a new TWRP. All I see is version 2,8
I installed all the updates back to back. I have TWRP installed and I'm on NH7 now. But I cant get root. Chainfire Auto took me back to stock recovery and I'm not rooted. So I flashed TWRP via Odin and flashed ChainFire Superuser v.2.14 and I'm still not rooted. All thought it say it worked. So WHen I reboot, what do I need to do then? I have SU installed
Ok guys. After flashing all the Roms in order via ODIN. I finally have NH7 working and rooted.
I just tried wiping system, data,dalvik and cache. Then I immediately rebooted to recovery and tried to flash MOAR V1. and Pac-man rom. Both failed.
One thing Im noticing in recovery is that the system is not mounted in when wiping. So I tried wiping with and without system being mounted and got the same result. One thing Im not sure about with flashing for the note is if the Data should be formatted before installing? However I dont see that option in TWRP.
This is the only phone Ive had this much trouble with when it came to flashing.
Any ideas?
Sent from my SM-N900P using XDA Premium 4 mobile app
Any chance someone can port this for use with our 900P?
http://forum.xda-developers.com/showthread.php?t=3170934
Thanks!
Sent from my hltespr using XDA Free mobile app
sixshooterz said:
Any chance someone can port this for use with our 900P?
http://forum.xda-developers.com/showthread.php?t=3170934
Thanks!
Sent from my hltespr using XDA Free mobile app
Click to expand...
Click to collapse
I've got my phone working on Cricket And have used that rom. I had to edit the build prop for it to flash
Sent from my SM-N910F using Tapatalk
wormy987123 said:
I've got my phone working on Cricket And have used that rom. I had to edit the build prop for it to flash
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
I managed to get it to flash but upon boot, it hung. I tried flashing a KK CM kernel and achieved the same result and restored back to a CM12.1 ROM. I'm going to mess with it a little more tonight.
Thanks for the feedback!
sixshooterz said:
I managed to get it to flash but upon boot, it hung. I tried flashing a KK CM kernel and achieved the same result and restored back to a CM12.1 ROM. I'm going to mess with it a little more tonight.
Thanks for the feedback!
Click to expand...
Click to collapse
I had to restart once, it hung on first boot. After that it booted fine. I ran it for a few hours but not my kinda rom. The CM kernel will hang it's samsung based
Sent from my SM-N910F using Tapatalk
How did you get it to boot?
This ROM boots without issue. No need to change kernels or anything else. That said, after booting I do not have any voice or data services available. I tried restoring the Sprint APN and, although it shows up, I still can't get connected to the Sprint network.
EDIT: Whenever I flash a new ROM, my method is always wipe system, data, dalvik cache, and cache 3 times then reboot to recovery and proceed with flashing as normal. With this ROM, after the first boot it seems to hang. Press and hold power til it reboots then you'll see the MIUI boot animation.
Sent from my hltespr using XDA Free mobile app