I'm looking for the PIT files for Sprint's Note 4. Or does anyone know if the PIT for SM-N910F will work. Is the (F) version compatible in all of the Sprint versions. I.E. when looking for Sprint programs there is no SM-N910(P) but always a SM-N910(F). Is it safe to use the F version? Or is there a safe way to update/redo the bootloaders? I flashed some bad files with Odin right around the BOB7 udate and my device has been spinning in circles around that since. Even if I go full stock and Odin the latest firmware my device is set back to that period from a protected file that is in between bootloaders. I can't touch it. The closest I can get is with a terminal command from TWRP [/sbin/recovery] I can then chmod the files and erase or do whatever with them but they are restored in cold boot. Even after flashing the official firmware it reverts to the files from BOB7. What's really crazy is I'm running stock firmware so can not use xposed but if I mount data and system wipe and then run uberwipe my device will boot with xposed apps functional. It is as if I am running two ROMS one that can not be removed or changed. I can see it happening but not from where exactly. In cold boot it loads the RO biuld from /dev/block/platforms/msm_scc1.by_name/hidden. I can find everything but the hidden. In the stock recovery logs it says the command to fix it is wipe_data_crypto but I can't accomplish it. Any suggestions?
PIT for Sprint Note 4 is here:
http://www.sammobile.com/forum/showthread.php?p=137840 No links are permitted by the developer; please respect that.
Not experiencing what you have and not attempting to fix what isn't broken, can't say what works but from what you describe, it sounds like you may have attempted to flash an older bootloader which isn't advised.
You may consider it's risky to try to undo that but first verify your reactivation lock is disabled. If your eMMC is OK, it might be OK to try to Odin PIT with repartition and nand erase all with an acceptable tar OG5 or higher loaded in AP slot. Always use PIT for repartition but only use if needed. And use at your own risk.
No guarantee but consider the risk and IF you have an issue with boot after Odin, you may need to factory reset in stock recovery and try the stock tar again (it's important to try that first without panicking). Always power down and pull battery before flashing stock tar. Also make sure you have ample battery charge. These days, 80% is recommended because there's a lot of weak batteries out there. Consider a new battery if older than 12 months or requiring frequent charging or phone shuts down before 0%. (I don't recommend full discharge, just that some batteries start shutting down around 20% when going bad. It only gets worse after that.)
Sent from my SM-N930P using Tapatalk
samep said:
PIT for Sprint Note 4 is here:
http://www.sammobile.com/forum/showthread.php?p=137840 No links are permitted by the developer; please respect that.
Not experiencing what you have and not attempting to fix what isn't broken, can't say what works but from what you describe, it sounds like you may have attempted to flash an older bootloader which isn't advised.
You may consider it's risky to try to undo that but first verify your reactivation lock is disabled. If your eMMC is OK, it might be OK to try to Odin PIT with repartition and nand erase all with an acceptable tar OG5 or higher loaded in AP slot. Always use PIT for repartition but only use if needed. And use at your own risk.
No guarantee but consider the risk and IF you have an issue with boot after Odin, you may need to factory reset in stock recovery and try the stock tar again (it's important to try that first without panicking). Always power down and pull battery before flashing stock tar. Also make sure you have ample battery charge. These days, 80% is recommended because there's a lot of weak batteries out there. Consider a new battery if older than 12 months or requiring frequent charging or phone shuts down before 0%. (I don't recommend full discharge, just that some batteries start shutting down around 20% when going bad. It only gets worse after that.)
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
Yes I'm getting ready to flash bootloaders big AF. I will two the pit files first but if that doesn't work I've got a list. Involves downgrading to kit kat, rooting with auoto root (can't screw me thrice) running triangle away to lose the warranty bit, installing xposed and wanam so as to make it read official. Once samsungs stuff isn't all a scared anymore I delete the /dev/block/platform/msm1_byname/hidden/rape the dumbass that used to trust developers he didn't know until he knew better and the rape was done.
I'm not really looking to flash boot loaders per say. I realized that you can only install a newer version and I TiVo I'm out of updates if I need a new bootloader. Just went to erase the obtrusive piece of poo hidden in between the 2 bootloaders. I'm not even sure theres supposed to be 2 bootladers. I look at samsuny stock firmware it's nothing like the billithera of extra stuff I have on my device. Can't say for sure who caused it because I did some retarded stuff when I was even greener than I am now. But whether it be auto root or srs unlock that super su is obtrusive as it gets. The purpose of root was flee me the user to gain access tip everything. The whole limiting the user and granting permission to every creepy fook on this planet to stock me and my kids is not what I had in mind. These people are so adamant about their creepy stalking not only is my devices esp network cut by 90% they do dangerous stuff like hidden robuilds that has a value of 1 where the radio don't shut off I airplane mode.
samep said:
PIT for Sprint Note 4 is here:
http://www.sammobile.com/forum/showthread.php?p=137840 No links are permitted by the developer; please respect that.
Not experiencing what you have and not attempting to fix what isn't broken, can't say what works but from what you describe, it sounds like you may have attempted to flash an older bootloader which isn't advised.
You may consider it's risky to try to undo that but first verify your reactivation lock is disabled. If your eMMC is OK, it might be OK to try to Odin PIT with repartition and nand erase all with an acceptable tar OG5 or higher loaded in AP slot. Always use PIT for repartition but only use if needed. And use at your own risk.
No guarantee but consider the risk and IF you have an issue with boot after Odin, you may need to factory reset in stock recovery and try the stock tar again (it's important to try that first without panicking). Always power down and pull battery before flashing stock tar. Also make sure you have ample battery charge. These days, 80% is recommended because there's a lot of weak batteries out there. Consider a new battery if older than 12 months or requiring frequent charging or phone shuts down before 0%. (I don't recommend full discharge, just that some batteries start shutting down around 20% when going bad. It only gets worse after that.)
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
I appreciate the advice. I hope to avoid allot with the PIT. That's what flashfire back up says it needs. Shutting the phone of is a good idea. The recovery log was actually making fun of me for not. Along with the simple command I needed to open /sbin/recovery then wipe cane and data crypto. The /sbin/recovery was an eye opener (try it from the emulator in twrp to see if root has crippled you. The thing is most of us use a universal supersu update to reinstall and that is not good. That is written to take out the marines if that's what it takes to accomplish root. Remember the food old days when superuser binary was a line compatible with your cu?
Anyways another good command people don't know is if odin fails don't pull the battery. I put am s4 tip sleep forever that way. volumedwn home and power reatart the bootloader and wipe the cache for the software out is rejecting.
Yes I'm getting ready to flash bootloaders big AF. I will two the pit files first but if that doesn't work I've got a list. Involves downgrading to kit kat, rooting with auoto root (can't screw me thrice) running triangle away to lose the warranty bit, installing xposed and wanam so as to make it read official. Once samsungs stuff isn't all a scared anymore I delete the /dev/block/platform/msm1_byname/hidden/rape the dumbass that used to trust developers he didn't know until he knew better and the rape was done.
I'm not really looking to flash boot loaders per say. I realized that you can only install a newer version and I TiVo I'm out of updates if I need a new bootloader. Just went to erase the obtrusive piece of poo hidden in between the 2 bootloaders. I'm not even sure theres supposed to be 2 bootladers. I look at samsuny stock firmware it's nothing like the billithera of extra stuff I have on my device. Can't say for sure who caused it because I did some retarded stuff when I was even greener than I am now. But whether it be auto root or srs unlock that super su is obtrusive as it gets. The purpose of root was flee me the user to gain access tip everything. The whole limiting the user and granting permission to every creepy fook on this planet to stock me and my kids is not what I had in mind. These people are so adamant about their creepy stalking not only is my devices esp network cut by 90% they do dangerous stuff like hidden robuilds that has a value of 1 where the radio don't shut off I airplane mode.
samep said:
PIT for Sprint Note 4 is here:
http://www.sammobile.com/forum/showthread.php?p=137840 No links are permitted by the developer; please respect that.
Not experiencing what you have and not attempting to fix what isn't broken, can't say what works but from what you describe, it sounds like you may have attempted to flash an older bootloader which isn't advised.
You may consider it's risky to try to undo that but first verify your reactivation lock is disabled. If your eMMC is OK, it might be OK to try to Odin PIT with repartition and nand erase all with an acceptable tar OG5 or higher loaded in AP slot. Always use PIT for repartition but only use if needed. And use at your own risk.
No guarantee but consider the risk and IF you have an issue with boot after Odin, you may need to factory reset in stock recovery and try the stock tar again (it's important to try that first without panicking). Always power down and pull battery before flashing stock tar. Also make sure you have ample battery charge. These days, 80% is recommended because there's a lot of weak batteries out there. Consider a new battery if older than 12 months or requiring frequent charging or phone shuts down before 0%. (I don't recommend full discharge, just that some batteries start shutting down around 20% when going bad. It only gets worse after that.)
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
by chance i got one of these thats only in qloader9008 you got any ideas on that i am downloading the debrick img from sammobiles rite now. aint really ever had this issue on a samsung only lgs
thanks in advance man
TheMadScientist420 said:
by chance i got one of these thats only in qloader9008 you got any ideas on that i am downloading the debrick img from sammobiles rite now. aint really ever had this issue on a samsung only lgs
thanks in advance man
Click to expand...
Click to collapse
You may have discovered this thread. I haven't had the issue or tried fixing one bricked but marked this thread because of all the theories, examples and links, it seemed a place to start for answers but I couldn't know without experiencing an issue, myself. What works? Don't know.
http://forum.xda-developers.com/showpost.php?p=63848150&postcount=1
It's probably a starting point but nothing new if you've devoted time with success in finding methods to try. It suggests also it could be the eMMC failing which is all too common for Note 4. Either way, if it's just bricked, maybe you recover it. If it's component failure, main board replacement should fix it. Main boards can be found on eBay and Amazon but I think they're all used or remanufactured boards. Samsung repair may be an alternative if you're not to inconvenienced by waiting. Just recently, I got a quote from my local uBreakItIfixIt and the guy said it's not a fixed estimate store to store but he'd only charge $10 to replace a main board in store.
Best wishes for timely procedure or economical repair.
Sent from my SM-N930P using Tapatalk
samep said:
You may have discovered this thread. I haven't had the issue or tried fixing one bricked but marked this thread because of all the theories, examples and links, it seemed a place to start for answers but I couldn't know without experiencing an issue, myself. What works? Don't know.
http://forum.xda-developers.com/showpost.php?p=63848150&postcount=1
It's probably a starting point but nothing new if you've devoted time with success in finding methods to try. It suggests also it could be the eMMC failing which is all too common for Note 4. Either way, if it's just bricked, maybe you recover it. If it's component failure, main board replacement should fix it. Main boards can be found on eBay and Amazon but I think they're all used or remanufactured boards. Samsung repair may be an alternative if you're not to inconvenienced by waiting. Just recently, I got a quote from my local uBreakItIfixIt and the guy said it's not a fixed estimate store to store but he'd only charge $10 to replace a main board in store.
Best wishes for timely procedure or economical repair.
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
i dont know the problem seems to have been in a update.. playing with it for a while it started charging and turned on and finished a update....
i got a s6 active did the same thing to me just started working i run it for like 6 months no probs
of coarse its on sprints black list just found out due to non payment of ezpay. but ill deal with that on my own as such talks are downed and frowned upon.
man i got this thing for 20 bucks.... even if nothing else my buddy needs a screen for one in his shop. but most def thank you for responding..
too further your post i do all my own repairs ussually the cheapest route currently behind the wheel of a unrootable verizon note 5 and a lgg4 which is rooted but no twrp method available. each i have very little invested in.
I never could find the files. The link was valid, samep, it just refused to let me have them. It turns out it is easier to get them off your own device and I've zero doubt they are for the 32gb Sprint Note 4. At least mine anyways. I tried the down grade to kitkat which would have worked because it downgrades you boatloader at least according to the page. I got a failed md5. So it wouldn't supirise me if these pit files are different than what the stock one was. Hard to tell what you have, for sure, when you are a flash junk that trusts random people on the inter web. At least I was/did. I gave myself this when it was brand new. It was hard to get it going again. I back up worked with plasma kernel then on the next official it was right again, well almost, I've had this problem almost two years now. I went without root for a while so didn't notice.
I
I hope this fixes it. If not I'll find the right files for the kk downgrade. It would be sweet to go back anyways. I'll leave a link in the next thread for the pit.
TheMadScientist420 said:
i dont know the problem seems to have been in a update.. playing with it for a while it started charging and turned on and finished a update....
i got a s6 active did the same thing to me just started working i run it for like 6 months no probs
of coarse its on sprints black list just found out due to non payment of ezpay. but ill deal with that on my own as such talks are downed and frowned upon.
man i got this thing for 20 bucks.... even if nothing else my buddy needs a screen for one in his shop. but most def thank you for responding..
too further your post i do all my own repairs ussually the cheapest route currently behind the wheel of a unrootable verizon note 5 and a lgg4 which is rooted but no twrp method available. each i have very little invested in.
Click to expand...
Click to collapse
Did you fix it? Your right totally worth it for the screen. You can unlock the imei. I only did it once just because some people are so adamant you can't. I like to believe anything is possible. I don't feel bad about getting those non paid because the phone companies are the thieves. Especially in the US. They bury a lot of people locking you down to have a phone and the policy on being to stupid to fix anything is raw. With two kids I paid out a lot of dead phones. It takes rooting one phone to have bested the entire knowledge of tech at sprint. That's the hard part. If they sold parts it would be nothing.
TheMadScientist420 said:
by chance i got one of these thats only in qloader9008 you got any ideas on that i am downloading the debrick img from sammobiles rite now. aint really ever had this issue on a samsung only lgs
thanks in advance man
Click to expand...
Click to collapse
Sent from my SM-N910P using XDA-Developers mobile app
PIT_SM_N910P
https://mega.nz/#!cJREFYqS
Sent from my SM-N910P using XDA-Developers mobile app
planb234 said:
Did you fix it? Your right totally worth it for the screen. You can unlock the imei. I only did it once just because some people are so adamant you can't. I like to believe anything is possible. I don't feel bad about getting those non paid because the phone companies are the thieves. Especially in the US. They bury a lot of people locking you down to have a phone and the policy on being to stupid to fix anything is raw. With two kids I paid out a lot of dead phones. It takes rooting one phone to have bested the entire knowledge of tech at sprint. That's the hard part. If they sold parts it would be nothing.
Sent from my SM-N910P using XDA-Developers mobile app
Click to expand...
Click to collapse
Y3a it just decided it was gonna start workin heck yea.
The battery is trashed on it. Im gonna order one here soon
Ive flashed a few roms on it. Rooted. But everytime i restart it the bat percentage is totally diffrent.. thank you. I got a s6 once same way
Wouldnt do nothing. Plyin with it and decided to boot up.
Again i know talks of bad imeis are not good conversation. But i use cdma workshop and basicly took a old sammy i had that was junk and destroyed it. Took the sticker and rewrite a new iemi. Havent done it yet but. When i get there i know i can.
Ofcoarse now i cant unlock it even if i follow all the guides. Ive tried and tried.
TheMadScientist420 said:
Y3a it just decided it was gonna start workin heck yea.
The battery is trashed on it. Im gonna order one here soon
Ive flashed a few roms on it. Rooted. But everytime i restart it the bat percentage is totally diffrent.. thank you. I got a s6 once same way
Wouldnt do nothing. Plyin with it and decided to boot up.
Again i know talks of bad imeis are not good conversation. But i use cdma workshop and basicly took a old sammy i had that was junk and destroyed it. Took the sticker and rewrite a new iemi. Havent done it yet but. When i get there i know i can.
Ofcoarse now i cant unlock it even if i follow all the guides. Ive tried and tried.
Click to expand...
Click to collapse
There's a couple of ways to calibrate the battery. the easiest is a root app in Play "Battery Calibrator" it resets the stats at 100% Another is *#0228# I believe you calibrate it then let it run all the way dry then charge it to full with the system off. Not too hard to find if you want to give it a shot. It's hard to say what the problem is. I just got a new one because the old was dying at 30%. I use both and they take turns on which one is weak. Neither is a problem with out root. I probably have too much working Or to much stuff in the background.
I've heard that about changing the sticker. i only change the sticker if I used another phone for the screen. It matches what is in the board that way, If you take it in the store to get it activated they may be a little less confused.
I took an S4 that was compiled of 3 previous ones and my daughters that just stoppede working to get activated at sprint. Of course he couldn't. His story the same "When you work on them .. . He was pretty adamant that as it. I couldn't figure out how that affected both of them. So i took it home and activated it myself. Turns out the S4 is a dual band so he generally has a 50% succes rate it will turn on in the mode.
The sticker definitly won't get it activated. I've got an LG3 that was given to me by some who did't care about sprint anymoe that was Imei locked out activated. It was $100 bucks for the server. The server was. It unlocked a s5 also that a jerk sold me was clean. It unlocked it too. It was through verizon so i never activated it. I was trying to flop it to sprint when it disappeard .I unloced my note 4 with it to. The SIM so the APNs aere never locked altough I'm not positve it could have been GTidonetehapp that did it. I did' know what I ws doing, I just like plaing with them. No real reason to unlock a phone you own. Well ther is the hotspot. I'm pretty sure that's how I crumbed up my note and my puter to. I dropped exec files in my win 32 folder and flashed in something with a crazy odin to get my phone unlocked. But again not positive, thier stuff workied so it was just to give my equiment herepes.
planb234 said:
PIT_SM_N910P
https://mega.nz/#!cJREFYqS
My bad. I did not know that there has to be a key for mega. This one should do better.
Fwd: https://www.dropbox.com/sh/b0b3ywj5rbiec7h/AAAUM9TvOLUCDPJXXZTZBd_Ea?dl=0
Click to expand...
Click to collapse
planb234 said:
There's a couple of ways to calibrate the battery. the easiest is a root app in Play "Battery Calibrator" it resets the stats at 100% Another is *#0228# I believe you calibrate it then let it run all the way dry then charge it to full with the system off. Not too hard to find if you want to give it a shot. It's hard to say what the problem is. I just got a new one because the old was dying at 30%. I use both and they take turns on which one is weak. Neither is a problem with out root. I probably have too much working Or to much stuff in the background.
I've heard that about changing the sticker. i only change the sticker if I used another phone for the screen. It matches what is in the board that way, If you take it in the store to get it activated they may be a little less confused.
I took an S4 that was compiled of 3 previous ones and my daughters that just stoppede working to get activated at sprint. Of course he couldn't. His story the same "When you work on them .. . He was pretty adamant that as it. I couldn't figure out how that affected both of them. So i took it home and activated it myself. Turns out the S4 is a dual band so he generally has a 50% succes rate it will turn on in the mode.
The sticker definitly won't get it activated. I've got an LG3 that was given to me by some who did't care about sprint anymoe that was Imei locked out activated. It was $100 bucks for the server. The server was. It unlocked a s5 also that a jerk sold me was clean. It unlocked it too. It was through verizon so i never activated it. I was trying to flop it to sprint when it disappeard .I unloced my note 4 with it to. The SIM so the APNs aere never locked altough I'm not positve it could have been GTidonetehapp that did it. I did' know what I ws doing, I just like plaing with them. No real reason to unlock a phone you own. Well ther is the hotspot. I'm pretty sure that's how I crumbed up my note and my puter to. I dropped exec files in my win 32 folder and flashed in something with a crazy odin to get my phone unlocked. But again not positive, thier stuff workied so it was just to give my equiment herepes.
Click to expand...
Click to collapse
I do my own i jusf activate sim cards the sticker is basicly for my refrance i sell a lot of phones but i keep ones like this for myself. So theres no issues i just swap sims all the time so no need for activations
planb234 said:
I never could find the files. The link was valid, samep, it just refused to let me have them. It turns out it is easier to get them off your own device and I've zero doubt they are for the 32gb Sprint Note 4. At least mine anyways. I tried the down grade to kitkat which would have worked because it downgrades you boatloader at least according to the page. I got a failed md5. So it wouldn't supirise me if these pit files are different than what the stock one was. Hard to tell what you have, for sure, when you are a flash junk that trusts random people on the inter web. At least I was/did. I gave myself this when it was brand new. It was hard to get it going again. I back up worked with plasma kernel then on the next official it was right again, well almost, I've had this problem almost two years now. I went without root for a while so didn't notice.
I
I hope this fixes it. If not I'll find the right files for the kk downgrade. It would be sweet to go back anyways. I'll leave a link in the next thread for the pit.
Click to expand...
Click to collapse
I do believe you have to sign into Sammobile to download files.
The PIT can also be found in the first stock tar for each OS update; the developer I linked says that the PIT hasn't changed. I've seen methods to extract PIT from phone but they don't match md5 when checked. I checked your linked PIT in the post above and it doesn't match either. I wouldn't recommend using that one.
If your phone has ever updated beyond OB7, you can't Odin full stock KitKat tars or OB7 stock tar. The bootloader will block the Odin flash.
Not looking at your phone, it's hard to say what's going on. But I hope the feedback helps. Ask if you have further questions; I'll try to reply, but I haven't experienced what you've having issues with. Best wishes for resolution.
Sent from my SM-N910P using Tapatalk
samep said:
I do believe you have to sign into Sammobile to download files.
The PIT can also be found in the first stock tar for each OS update; the developer I linked says that the PIT hasn't changed. I've seen methods to extract PIT from phone but they don't match md5 when checked. I checked your linked PIT in the post above and it doesn't match either. I wouldn't recommend using that one.
If your phone has ever updated beyond OB7, you can't Odin full stock KitKat tars or OB7 stock tar. The bootloader will block the Odin flash.
Not looking at your phone, it's hard to say what's going on. But I hope the feedback helps. Ask if you have further questions; I'll try to reply, but I haven't experienced what you've having issues with. Best wishes for resolution.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Yeah it didn't work . It just shut down . I'll explain what has going on. Thank you for this post. It's good to know there's more options.
I actually did take a note 4 and s4 back. It dependes on how they upgraded. The bootloader doesn't change in an fota. I could do the s4 again now.
Thanks again for the awesome info.
TheMadScientist420 said:
I do my own i jusf activate sim cards the sticker is basicly for my refrance i sell a lot of phones but i keep ones like this for myself. So theres no issues i just swap sims all the time so no need for activations
Click to expand...
Click to collapse
You don't have to unlock the SIM or anything? Even if you do that's a lot less than getting the imei forgot about. Don't you have to get an msl from a comany. I know it's very possible send easy in free countries but i live in murica. You pay and pay here and the still put a cap on the data. If we're not careful we may use up all that data and then there would be no way to watch us 24-7 just we might go rogue.
A sticker that changes the sim? Details please.
samep said:
You may have discovered this thread. I haven't had the issue or tried fixing one bricked but marked this thread because of all the theories, examples and links, it seemed a place to start for answers but I couldn't know without experiencing an issue, myself. What works? Don't know.
http://forum.xda-developers.com/showpost.php?p=63848150&postcount=1
It's probably a starting point but nothing new if you've devoted time with success in finding methods to try. It suggests also it could be the eMMC failing which is all too common for Note 4. Either way, if it's just bricked, maybe you recover it. If it's component failure, main board replacement should fix it. Main boards can be found on eBay and Amazon but I think they're all used or remanufactured boards. Samsung repair may be an alternative if you're not to inconvenienced by waiting. Just recently, I got a quote from my local uBreakItIfixIt and the guy said it's not a fixed estimate store to store but he'd only charge $10 to replace a main board in store.
Best wishes for timely procedure or economical repair.
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
I've been trying to reply to this for 2 days. You see it's not the way my phone runs that is the issue it is my network that is completely raped. I can't lose my parasite. I screwed up my bootloader petty bad when I was learning about Samsung. If you ask how to unlock a bootloader the most common answer you get is "you don't, you use auto root". Auto root is as amazing for sure but I can tell there is a lot of people who don't read anything and just do. The the disclaimer is "don't use this with a locked boot loader, you will likely brick your device." As i mentioned I'm a flash junky. I didn't know once you blew the hole in thy boot you only needed a custom recovery forever. I like changing roms so i rooted with it a couple more times. Things for real bad after I ran the kitkat auto root on lollipop. I could use one of my back ups and add plasma kernel for a few months until the next update. Worse than that i flashed a something from an unlock sight with a special version of Odin. I didn't even need to because i had all ready changed the csc to xas so my apns were open. The effects were scary but cool. I got locked out of my phone for awhile except for virtual access on my puter screen. My home network for straight raped after that. I had everything set to home and share because i didn't think there would be even more bored than me so as to waste there life watching my life. There is and they are smart as #. I go in intervals of being angry to amazed. I thought they were gone but no. I was not keen on interweb when i got on here. Now that i could protect myself I can't keep the evil at bay because it lurks in the dark spaces I can't reach. FlashFire says it can remove the seemles. It is incredible to but I don't think so. It definitely can't mine. What's crazy is I've had a couple new bootloaderers since then but it remains. I'm with out root at the moment and am able to look at some of the data and dev were files. I can see the usb files that block adb is in but still no. Even though auto root totally changes the way and where from the device boots, I'm needing to extract or other wise terminate what is probably one card a ftp or smb. I can see in my win logs that if uses a machine to confuse the system in a barrage of security log ins while opening a door for daddy. I had the xml explaing how it's done but then a brand new 125gb card magically went to sleep forever. Some script out there is beyond amazing to me. Virtual net adapters that aren't on top of actual hardware blow my mind. It would have never crossed my mind in a million years they there is going to be a need for antivirus software on hardware like a Bluetooth keyboard.
planb234 said:
You don't have to unlock the SIM or anything? Even if you do that's a lot less than getting the imei forgot about. Don't you have to get an msl from a comany. I know it's very possible send easy in free countries but i live in murica. You pay and pay here and the still put a cap on the data. If we're not careful we may use up all that data and then there would be no way to watch us 24-7 just we might go rogue.
A sticker that changes the sim? Details please.
Click to expand...
Click to collapse
this device had a bad iemi person i got it from said they didnt pay for it on the sprint ezpay.
i checked and that was the truth. so i changed the iemi with another old sammy i had and put the sticker in for my records. so i know what the new iemi is without the device being turned on.
im trying to sim unlock it so i can use it on domestic gsm but no go sofar always invalid sim.
i guess i need to take this dissussion to another thread as so i dont get to far off the orig topic here
@planb234
I'm not following well what you've tried since getting a PIT file. Did you get the PIT file from Sammobile yet? Did you try the latest stock tar? If older ones, which ones fail?
If Odin fails, can you post the log and text on screen?
I believe what you're talking about is not needing to root if flashing a custom ROM. After a stock tar, you could Odin TWRP and flash a custom ROM. Custom ROMs include root and su. If using Chainfire Auto Root for Note 4, make sure to use the right one and latest for Lollipop and Marshmallow. KitKat had its own Auto Root. But the auto root uses a modified stock recovery which may make its use redundant if flashing a custom or even wanting just TWRP for backups if stock rooted.
Some fun facts for you:
The bootloader on Sprint Note 4 is unlocked. Flashing a stock tar will un-root it. Factory reset will cause you to lose systemless root. But flashing a full stock tar successfully will replace the bootloader. If you're trying to flash OB7 or older KitKat stock tar, your bootloader won't be replaced. As far as OTA, it patches existing baseband, bootloader and effected system files and partitions that need patched. Even if it's just a revision number in the update, it gets rolled up to match the update revision. While I feel stock tar updates are full and need no patching, the patching is sequential and should match the Odin'd bootloader and baseband once sequentially rolled up accordingly. So IMO, a patched bootloader is same as newly Odin'd bootloader. I could be wrong about the patching so not necessarily a fact.
I think your problem is unsuccessful flash of full stock tar. A blown eFuse may cause that but from what I've read in past posts of others that had issues back then is that flashing the correct stock tar after full wipe in stock recovery overcomes the flash. It leads me to believe it's only activating reset protection to try to roll the bootloader back to OB7 or KitKat. Maybe I'm wrong but if your phone isn't suffering a hardware issue, you should be able to recover it.
Other bootloaders between OB7 and OG5 like OE1 and OF5 were also exhibiting an inability to downgrade but bootloaders OG5 and up can so far can be downgraded to OG5. I haven't tried downgrading bootloader to OE1 or OF5 though.
I've seen phone info from posters claiming to roll their bootloader back to OB7 or older and they've actually reported a newer bootloader, post OB7.
As far as I know, the only true way to get KitKat ROM to flash and boot is to flash a newer kernel after ROM flash, but prior to initial boot attempt. Currently, I'm only aware of Android 5.1.1 kernel and post OB7 bootloader booting a KitKat ROM after bootloader is updated beyond OB7.
If you're capable of doing otherwise, I'd like to see legit screenshot of phone info or galaxy tools application.
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Sent from my SM-N910P using Tapatalk
Related
Hey guys, sorry for posting this, but im desperate and have read until my eyes are falling out of my skull. I am willing to work with any dev if they need specific work/software ran/info to make this happen. Is there, or is there not clear concise directions on rooting SGH-T889v (wind mobile variant of note 2)?
remember we use AWS for our signal, the modem stuff is all different. this is were my expertise kinda falls short. BUT I AM WILLING TO HELP TO MAKE THIS HAPPEN. As far as iv'e seen there are no current methods of rooting this phone which is a damn shame considering its horsepower. i saw the all in one toolkit for note 2's, and i simply cannot afford to donate to unlock the functionality of the update that supports wind. So only ONE guy knows how? I believe dev's should get paid and should accept donations, they are the real workers and smart guys. I don't work for free either, However this kinda defeats the purpose of the ecosystem we fought so hard to have.... open and accessible platforms were we the users are in control. By with holding the method, its no longer donating, it's close sourcing ala apple,microsoft, etc. Zero offence to that guy, id just really love to "own" MY phone. Can someone PLEASE help? pass the word? anything? a peep?
gh0stpirate said:
Hey guys, sorry for posting this, but im desperate and have read until my eyes are falling out of my skull. I am willing to work with any dev if they need specific work/software ran/info to make this happen. Is there, or is there not clear concise directions on rooting SGH-T889v (wind mobile variant of note 2)?
remember we use AWS for our signal, the modem stuff is all different. this is were my expertise kinda falls short. BUT I AM WILLING TO HELP TO MAKE THIS HAPPEN. As far as iv'e seen there are no current methods of rooting this phone which is a damn shame considering its horsepower. i saw the all in one toolkit for note 2's, and i simply cannot afford to donate to unlock the functionality of the update that supports wind. So only ONE guy knows how? I believe dev's should get paid and should accept donations, they are the real workers and smart guys. I don't work for free either, However this kinda defeats the purpose of the ecosystem we fought so hard to have.... open and accessible platforms were we the users are in control. By with holding the method, its no longer donating, it's close sourcing ala apple,microsoft, etc. Zero offence to that guy, id just really love to "own" MY phone. Can someone PLEASE help? pass the word? anything? a peep?
Click to expand...
Click to collapse
Who says there is no way....use donated version of toolkit ...its in there
Sent from my SGH-T889 using Tapatalk 2
If you don't mind the flash counter, you could simply use an Odin flashable (N7100) CWM tar, push the superuser zip of your choosing to /data/media/ (linked to /sdcard/) and install that from CWM.
What I know is that the rooting part is all fine and dandy, sure its a little harder than the rest, but its okay, it not too hard. The problem I keep reading is that the ROMS aren't truly compatible with the device, as data become atrociously slow. A method one, respected fellow, recommended we take was to flash a modem that is "for" our device variant. I say that because people reported bootloops due to it. Also there's a greater chance for our device to lose its IMEI number...not sure if these problems have been resolved. But yeah your problem really isn't rooting its the whole deal afterwards, again I am going by what I've read, I myself do not wish to take the chance of it becoming unusable, so i stay far until I got time to research more and some brilliant helpful mind comes along and solves all problems.
true
MCRHAZ said:
What I know is that the rooting part is all fine and dandy, sure its a little harder than the rest, but its okay, it not too hard. The problem I keep reading is that the ROMS aren't truly compatible with the device, as data become atrociously slow. A method one, respected fellow, recommended we take was to flash a modem that is "for" our device variant. I say that because people reported bootloops due to it. Also there's a greater chance for our device to lose its IMEI number...not sure if these problems have been resolved. But yeah your problem really isn't rooting its the whole deal afterwards, again I am going by what I've read, I myself do not wish to take the chance of it becoming unusable, so i stay far until I got time to research more and some brilliant helpful mind comes along and solves all problems.
Click to expand...
Click to collapse
i think thats the issue, we just generally need someone more brilliant xD as per the "gentleman" that again, suggested using the donating kit, please re-read my post. whats this business about a flash counter????
darn shame still nothing regretting purchasing this phone completely due to this :/
I used the toolkit to root my N2 (Videotron T889v) without any problems. Just used the T-Mobile option since they are the same phone, just different software. The only difference is the modem from what I've read. Rooting does not change the modem that you currently have right now. If you decide you want to install a custom rom, then you may have to flash your modem back. I am currently using Jedi X rom without any problems and I can honestly say that it's faster than stock. He also provides a link with our modem so we can flash it after the install. All the T-Mobile software has been taken out, so you won't have to deal with any of it. Here are the links for the toolkit and rom.
Toolkit - http://forum.xda-developers.com/showthread.php?t=1957720
Jedi X rom - http://forum.xda-developers.com/showthread.php?t=1987634
There are 2 Jedi Roms available. Jedi X has the multi-window function working but no wifi calling. I believe the other is called Jedi Master and that one has wifi calling but no multi-window. I'm not sure if the wifi calling is a T-Mobile thing but I never installed that rom and can't really give much more info on it. In the end, you can always go back to stock if you're not satisfied. You can find a copy of your stock rom at sammobile. I would suggest making sure it's still available before doing anything.
As for the OP, this is my first time dealing with a flash counter although not my first time rooting. The flash counter is some type of software that Samsung puts in their phones to be able to tell if you have "tampered" with the phone's software. From what I've noticed, when you put your phone in the "download" state and install anything, that triggers the counter to rise. If you send your phone to Samsung for service and the counter is not 0, they will deny service since you would have broken your warranty. There is a program called Triangle Away that will return your counter back to 0, should you need to return the phone to Samsung. Although in my case it would only take it back down to 1 using their instructions. I finally got it back to 0 by adding an extra step. From what I've read, I think it depends on the kernel that you're using. Here is the link for the program.
Triangle Away - http://forum.xda-developers.com/showthread.php?t=1494114
I'm not an expert on any of this, just trying to help. I can say that I've rooted, unrooted and reset my flash counter back to 0 along with my stock Videotron rom.
Good luck
JDLS said:
I used the toolkit to root my N2 (Videotron T889v) without any problems. Just used the T-Mobile option since they are the same phone, just different software. The only difference is the modem from what I've read. Rooting does not change the modem that you currently have right now. If you decide you want to install a custom rom, then you may have to flash your modem back. I am currently using Jedi X rom without any problems and I can honestly say that it's faster than stock. He also provides a link with our modem so we can flash it after the install. All the T-Mobile software has been taken out, so you won't have to deal with any of it. Here are the links for the toolkit and rom.
Toolkit - http://forum.xda-developers.com/showthread.php?t=1957720
Jedi X rom - http://forum.xda-developers.com/showthread.php?t=1987634
There are 2 Jedi Roms available. Jedi X has the multi-window function working but no wifi calling. I believe the other is called Jedi Master and that one has wifi calling but no multi-window. I'm not sure if the wifi calling is a T-Mobile thing but I never installed that rom and can't really give much more info on it. In the end, you can always go back to stock if you're not satisfied. You can find a copy of your stock rom at sammobile. I would suggest making sure it's still available before doing anything.
As for the OP, this is my first time dealing with a flash counter although not my first time rooting. The flash counter is some type of software that Samsung puts in their phones to be able to tell if you have "tampered" with the phone's software. From what I've noticed, when you put your phone in the "download" state and install anything, that triggers the counter to rise. If you send your phone to Samsung for service and the counter is not 0, they will deny service since you would have broken your warranty. There is a program called Triangle Away that will return your counter back to 0, should you need to return the phone to Samsung. Although in my case it would only take it back down to 1 using their instructions. I finally got it back to 0 by adding an extra step. From what I've read, I think it depends on the kernel that you're using. Here is the link for the program.
Triangle Away - http://forum.xda-developers.com/showthread.php?t=1494114
I'm not an expert on any of this, just trying to help. I can say that I've rooted, unrooted and reset my flash counter back to 0 along with my stock Videotron rom.
Good luck
Click to expand...
Click to collapse
so you flashed the modem that ptmr3 provided for the t889v along with his jedi x rom and all good is good? no signal issues ? you get hspa+?
First Post:
I'm on Wind Mobile T889v Note 2. And I cant wait for this phone to get rooted so that I can run debian or whatever have you full blow linux desktop experience on my phone.
The current limited version of android on its own is too limiting for the processing beast that this phone is.
MCRHAZ said:
so you flashed the modem that ptmr3 provided for the t889v along with his jedi x rom and all good is good? no signal issues ? you get hspa+?
Click to expand...
Click to collapse
That is correct. Never had any issues whatsoever. Always get full signal strength, no disconnections and overall great service. As long as you flash after the rom, you will get your modem back. To be honest, the rom itself has never changed my modem, I always just flash it in case it's just reporting it as an error. In the directions it states that it will change it but I always check it and it has remained the same every time.
you mean by letting bootup and set up first then go back to twrp or cwm? and then flash the modem...my exams are done hoping to do it by tomorrow.
MCRHAZ said:
you mean by letting bootup and set up first then go back to twrp or cwm? and then flash the modem...my exams are done hoping to do it by tomorrow.
Click to expand...
Click to collapse
After you flash the rom (if you're flashing Jedi) you need to let it sit for 10 minutes on the first boot up (after the android logo, just use the reboot option after the 10 minutes). Once you've booted up and finished your setup, just go back into cwm or twrp and flash the modem.
how did you reset the flash counter with triangle away? it doesnt seem to work on my 889V
Sent from my GT-N7105 using xda app-developers app
Hey Guys,
I have read a burch of different threads about my problem and nothing has seemed to help or it was too advanced for me to understand. So here it is:
I tried to root my S3 and at first Oden 307 said the root failed, then i was able to try a different file and it said pass. but now when it boots up it gets stuck on the samsung galaxy s3 screen. I can still get into download mode and recovery mode. I have already tried the factory reset in recovery mode. Please help I have only had this phone a month. At this point I dont even care rooted or not I just want my phone back lol
Thanks for any help
+rep
garrett.burn said:
Hey Guys,
I have read a burch of different threads about my problem and nothing has seemed to help or it was too advanced for me to understand. So here it is:
I tried to root my S3 and at first Oden 307 said the root failed, then i was able to try a different file and it said pass. but now when it boots up it gets stuck on the samsung galaxy s3 screen. I can still get into download mode and recovery mode. I have already tried the factory reset in recovery mode. Please help I have only had this phone a month. At this point I dont even care rooted or not I just want my phone back lol
Thanks for any help
+rep
Click to expand...
Click to collapse
First you need to tell us which build you were on, and then what build did you try flashing...
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
BIGSAMDA1st, can I call you "Sam?" Your post count would indicate you've got more experience than I do so I thought I'd ask: aren't all the Sprint S3s on the MK3 build by default? Or are there inconsistencies within the Sprint-branded line of S3s?
Oh man. At least you've still got access to the download console. Can you also access the recovery console? Also, sounds like you're new to rooting (I could be wrong, just going on your comment about certain techniques being too advanced for you to wrap your head around). If you're new, you really picked both one hell of a time and one hell of a phone to cut your teeth on. Samsung's official 4.3 update (which, for all I know, is shipped standard now) comes with the KNOX bootloader which is, in certain situations, basically a bomb designed to ruin your week... and your phone. In particular, it has a REALLY nasty reaction to attempts at downgrading to the old (and much happier) bootloader. It also seems to really hate the older versions of TriangleAway (might hate the new one too, for all I know. I won't touch it anymore). It has other ways to make you hate life as well, but those are two big ones.
How to tell if you have the KNOX bootloader: Did you install the official OTA update to 4.3? If so, you've got the bomb. Did your phone come with 4.3 right out of the box? If so, you've probably got the bomb. Are you still unsure? Look in your Download console for red text that says something like "Warranty Void Bit" or anything that mentions KNOX. If so, you guessed it, you've got the bomb.
If you have the Warranty Void thing listed, then check to see: is it a 0, or is it a 1? If it's a zero, don't do anything else with trying to flash your ROM or root the device until we try some things in your Recovery Console (assuming it's also accessible). Once that flag is tripped, there's no going back... Not a huge deal if it's just a personal device, assuming you're not still under warranty... If you are, well, don't trip that bugger if you can avoid it.
FallenZen said:
BIGSAMDA1st, can I call you "Sam?" Your post count would indicate you've got more experience than I do so I thought I'd ask: aren't all the Sprint S3s on the MK3 build by default? Or are there inconsistencies within the Sprint-branded line of S3s?
Oh man. At least you've still got access to the download console. Can you also access the recovery console? Also, sounds like you're new to rooting (I could be wrong, just going on your comment about certain techniques being too advanced for you to wrap your head around). If you're new, you really picked both one hell of a time and one hell of a phone to cut your teeth on. Samsung's official 4.3 update (which, for all I know, is shipped standard now) comes with the KNOX bootloader which is, in certain situations, basically a bomb designed to ruin your week... and your phone. In particular, it has a REALLY nasty reaction to attempts at downgrading to the old (and much happier) bootloader. It also seems to really hate the older versions of TriangleAway (might hate the new one too, for all I know. I won't touch it anymore). It has other ways to make you hate life as well, but those are two big ones.
How to tell if you have the KNOX bootloader: Did you install the official OTA update to 4.3? If so, you've got the bomb. Did your phone come with 4.3 right out of the box? If so, you've probably got the bomb. Are you still unsure? Look in your Download console for red text that says something like "Warranty Void Bit" or anything that mentions KNOX. If so, you guessed it, you've got the bomb.
If you have the Warranty Void thing listed, then check to see: is it a 0, or is it a 1? If it's a zero, don't do anything else with trying to flash your ROM or root the device until we try some things in your Recovery Console (assuming it's also accessible). Once that flag is tripped, there's no going back... Not a huge deal if it's just a personal device, assuming you're not still under warranty... If you are, well, don't trip that bugger if you can avoid it.
Click to expand...
Click to collapse
First thing is THANK YOU and as i am a noob, where is the +rep button for you? Second and maybe you could help with this, since I posted this I was able to flash back to the official 4.3 :/ so I got my phone back but made my life harder in the process...I got clockwork recovery working and I was able to flash KNOX app remover .zip and I flashed team epic v5..it said everything was installed I rebooted and Im stll not rooted..Supersu says something about not having binary something another and root checker says I dont have root access. According to the step by step I followed I should be rooted :/ Any advise other than nex time dont upgrade to 4.3? lol
-Thanks Bro
BIGSAMDA1ST said:
First you need to tell us which build you were on, and then what build did you try flashing...
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
Click to expand...
Click to collapse
Im not quite sure what you are looking for but it says "Build Number JSS15J.L10VPUCMK3" And its a GS3 4.3 Model SPH-L710
Thanks for the reply
Hey mate,
I'm not familiar with the method of rooting 4.3 that you used. I'm glad to hear you got around the soft brick though! As far as running a rooted 4.3, I can tell you that what I wound up using was CNexus's pre-rooted ROM and the various fixes (s)he's compiled here:
http://forum.xda-developers.com/showthread.php?t=2541900
I've also shared my personal installation notes as well as hosted the files that worked for me on my Google Drive. That information is here:
http://forum.xda-developers.com/showthread.php?t=2560478&page=3
You shouldn't need the files I've got hosted on my Drive though... The ones CNexus has assembled in that thread should work just fine (that's where I got most of them, after all).
I cannot speak to whether or not any of the steps in my notes will trip your KNOX Warranty Void bit since I tripped mine (and damn near hard-bricked my phone) before I even knew what the KNOX bootloader was, let alone that Samsung had gone ahead and installed it for me.
I hope that helps.
-Zen
I've been rooting since OG Evo days, but only played with that, the s2, and s3. Rooting was easy as pie. But with all this knox stuff I'm wary.
I recently read reports of people sending in their phones to both Samsung and tmobile and getting it back with knox restored but still maintaining sim unlocks. So obviously it's a well kept firmware they flash or perhaps signatures.
This in mind I used kingoapp, and root was easy. Just decline the recovery install and you'll maintain 0x0. But after this new information I'm still worried to trip knox for fear those restores we're just a fluke.
Anybody have luck with safestrap? I heard/read it doesn't replace recovery so it also won't trip knox? Also, as long as I don't flash kernels or recovery I'll be good right? Like i can delete bloat or install at root level to /system and I'll be fine?
Sent from my SM-N900T using XDA Premium 4 mobile app
Naturesretard said:
I've been rooting since OG Evo days, but only played with that, the s2, and s3. Rooting was easy as pie. But with all this knox stuff I'm wary.
I recently read reports of people sending in their phones to both Samsung and tmobile and getting it back with knox restored but still maintaining sim unlocks. So obviously it's a well kept firmware they flash or perhaps signatures.
This in mind I used kingoapp, and root was easy. Just decline the recovery install and you'll maintain 0x0. But after this new information I'm still worried to trip knox for fear those restores we're just a fluke.
Anybody have luck with safestrap? Also, as long as I don't flash kernels or recovery I'll be good right? Like i can delete bloat or install at root level to /system and I'll be fine?
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
As long as you just root it nothing happens system will be fine .... Plssss hit thanksss.....
Sent from my HTC Desire C using XDA Premium 4 mobile app
pvinayraju2k4 said:
As long as you just root it nothing happens system will be fine .... Plssss hit thanksss.....
Sent from my HTC Desire C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the info. However in the future there's no need to request we thank. I've learned most people here on xda thank quite often, myself included.
Sent from my SM-N900T using XDA Premium 4 mobile app
Naturesretard said:
Thanks for the info. However in the future there's no need to request we thank. I've learned most people here on xda thank quite often, myself included.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
First off, the above poster is wrong... can't believe he asks for a thank. When you install a custom recovery, that is when you trip Knox. There a method to install a custom ROM w/o a recovery using Mobile Odin Pro. I know nothing about that but have read here that it works. You just can't flash custom kernel. I went ahead and flash a custom recovery because I don't care about Knox and will never send this phone to Samsung for warranty repair.
asianflavor said:
First off, the above poster is wrong... can't believe he asks for a thank. When you install a custom recovery, that is when you trip Knox. There a method to install a custom ROM w/o a recovery using Mobile Odin Pro. I know nothing about that but have read here that it works. You just can't flash custom kernel. I went ahead and flash a custom recovery because I don't care about Knox and will never send this phone to Samsung for warranty repair.
Click to expand...
Click to collapse
Just the fact most of us have insurance plans; if we discover a problem such as faulty gps or screen displacement, etc, tmobile fixes it for us anyway, right?
So it really doesn't matter if we trip knox, correct???
Sent from my SM-N900T using XDA Premium 4 mobile app
Naturesretard said:
Just the fact most of us have insurance plans; if we discover a problem such as faulty gps or screen displacement, etc, tmobile fixes it for us anyway, right?
So it really doesn't matter if we trip knox, correct???
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
From everything I read, yes.
Sent from my SM-N900T using Tapatalk
asianflavor said:
First off, the above poster is wrong...
Click to expand...
Click to collapse
He's not wrong. There are a couple different methods of rooting that don't require a custom recovery, therefore don't trip Knox.
Sent from my SM-N900T using Tapatalk
asianflavor said:
From everything I read, yes.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
I guess I shouldn't bother with safestrap then. Was planning on trying to pay off the note 3 and keep it anyway instead of jumping again this year.
Either way it won't matter...until I do eventually get a new handset but even then I know enough about rooting I shouldn't need to repair this one once paid off and detached from my account.
my next question is then should I TWRP or cwm? I tried CWM for the first time since gingerbread on my s3 and fell in love with it
Sent from my SM-N900T using XDA Premium 4 mobile app
Hey Nature! just wanted to add my 0.02, ok theres a difference between rooting, and a difference between flashing recoveries,kernels,roms,and what have you.
ill give a brief explanation in the differences. The Colors of the titles indicate how safe/dangerous it is to modify one of these things and wether it will void your warranty, Green=Wont void your warranty, and easily reversible. Orange=Void Warranty, Reversible, But starting to get Dangerous, Red=Definitely VVoids Warranty, and if screwed up, could ruin/brick your devvice Definitely Voids Warranty, and if screwed up, could ruin/brick your devvice
Rooting: When you are rooting your device, you are basically forcing your stock version of android to allow you (the user) root access, therefore allowing you to bypass/allow signature verification for apps, now this could be anything from homebrew apps that you are making yourself...to the naughty pirated apps, and i dont encourage the latter. By giving yourself root access to your phone, your allowing the next to happen:
Flashing a Custom Recovery: Ok ill explain this as simple as i can...Mostly all if not ALL android phones have a stock recovery, this is a safeguard in case some kind of software fault happened in the phone(stock software fault or what have you). Flashing a custom recovery would be your next step after Rooting a device (IF) you want to go further than apps, meaning Kernels, Roms etc. Now the reason you must Root your device in order to install a custom recovery, is because like explained above signature verification....Now this is when you begin to tread in warranty territory, once flashing a custom recovery...your warranty has become VOID, however what the custom recovery allows you to do is a multitude of things, but the most major is Flashing .ZIP files, which most roms are in the form of, now not only Roms are in ZIP files, so are kernels,mods,baseband firmwares, etc, with that being said, different phones/devices use different methods of flashing roms, lets say for example you somehow screwed something up on a samsung really bad, and it wont boot, however, you can still get into download mode...then you're safe, because samsung uses Odin to flash the entire phone back to stock meaning Recovery/aBoot/Data/System and bring you right back, but if you hard brick it, theres only 3 ways out from that...and they all suck....number one, is call me and send it to me to Jtag it for you ..but it takes long and its not that cheap, #2, Desolder the chip (whichever it is on the device that has caused the problem) and replace it...and thats not an easy task at all, ive done it once to an S3 successfully, after that i never wanted to do it again, and this was back when they were really expensive, and lastly....#3.....and this one is the worse....go buy a new one SO BE CAREFUL!
ROMS: So now that we have a custom recovery, a rom is basically a heavily modified version of Android! and let me tell ya, i love them...i love so many of them, there are sooo many different things that you can do with roms, but the most desired from what ive gathered, is so people can remove the bloatware that comes with their phone when they buy it from the carrier/manufacturer. Thats not all tho, there is way too much to get into, but some roms allow you to Overclock your phones CPU/GPU, and change the Behaviors of the phones hardware, and the major component in roms that allows that is the Kernel.
Kernel: Now dont totally quote me here, im still learning kernels, but a kernel is basically the binary software in the phone, almost like a bios that when modified from stock, changes the behavior of the MOST of the hardware, not all. Now i could be wrong and anyone please feel free to correct me, now i do want to give you a shot of my own advice here...if you dont know what you are doing, kernels are dangerous to a noobie..before i started messing with roms and kernels, i tried to get the best understanding i could, and ill be honest with you, i blew up a couple S3's doing so. but im still learning. so if you're unweary or still not educated enough in the hobby to get too it, please read more up on it, because as none of these guys here that are devs nor people like myself that are trying to help intend to destroy your device on you, so please be careful for your own device's safety, and to save yourself money and a broken heart.
Knox: Ok now correct me if im wrong here, because im still learning as this is new to me, i only saw it on the MJA bootloader on the S4 on Jellybean from Sprint when they first OTA'd it, but knox looks to be Samsungs pathetic try of not lettings us Access the devices binary software, like an encryption, or to only let us access and modify certain things, also samsung has added a flash counter, which will tell them how many times you have flashed a new rom, however there are ways around these things, google and the search bar are you best friends to start, and we can help too.
I Hope this helped and shed some light on some information, and please if anyone has anything to add or to correct me if im wrong anywhere please do so ^_^
P.S. To be totally honest, theres always a way to restore your device and even get the flash counter back to 0 again and put everything back to normal, if an experienced tech looks at it and puts it in download mode unless all is restored, hell be able to see everything, but honestly, if you pay off the phone, you havve nothing to worry about, but then again, i dont care much for warranties, so it all depends on how savvy with fixing problems when they go wrong, but if you ever need i can help you, im pretty experienced when it comes to everything but developing atm, i was a microelectronics major in college, so my expertise is mainly in hardware i.e. if you hard/soft brick the devvice i can usually get it out of that.
please excuse my typing, i type extremely fast, and i have a mechanical keyboard and i think some lettings are startings to give way such as the V key.
---------- Post added at 01:45 AM ---------- Previous post was at 01:29 AM ----------
Naturesretard said:
I guess I shouldn't bother with safestrap then. Was planning on trying to pay off the note 3 and keep it anyway instead of jumping again this year.
Either way it won't matter...until I do eventually get a new handset but even then I know enough about rooting I shouldn't need to repair this one once paid off and detached from my account.
my next question is then should I TWRP or cwm? I tried CWM for the first time since gingerbread on my s3 and fell in love with it
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh and please i Highly suggest using Philz Touch!
Code:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltetmo
Thats for the HLTETMO version, which is our versions in this forum, all credit to phil ofcourse, it is basically CWM, but so much more user friendly and advanced with much more options, there are two files there, you obviously want the latest version, and there are two ways to do it, if you download the tar.md5 you must use Odin, and put your phone in download/odin mode, very easily done (turn it off unplug usb and press Home+Vol Dwn+Pwr) then once the screen pops up press Vol Up and then plug the USB in, and follow the instructions of w/e tutorial you are ready, but be very careful in odin mode, if you disturb the phone while its flashing you will most likely brick it, and the .zip is considering you already have a custom recovery and you can just flash it through there.
MasterSe7en said:
Hey Nature! just wanted to add my 0.02, ok theres a difference between rooting, and a difference between flashing recoveries,kernels,roms,and what have you.
ill give a brief explanation in the differences. The Colors of the titles indicate how safe/dangerous it is to modify one of these things and wether it will void your warranty, Green=Wont void your warranty, and easily reversible. Orange=Void Warranty, Reversible, But starting to get Dangerous, Red=Definitely VVoids Warranty, and if screwed up, could ruin/brick your devvice Definitely Voids Warranty, and if screwed up, could ruin/brick your devvice
Rooting: When you are rooting your device, you are basically forcing your stock version of android to allow you (the user) root access, therefore allowing you to bypass/allow signature verification for apps, now this could be anything from homebrew apps that you are making yourself...to the naughty pirated apps, and i dont encourage the latter. By giving yourself root access to your phone, your allowing the next to happen:
Flashing a Custom Recovery: Ok ill explain this as simple as i can...Mostly all if not ALL android phones have a stock recovery, this is a safeguard in case some kind of software fault happened in the phone(stock software fault or what have you). Flashing a custom recovery would be your next step after Rooting a device (IF) you want to go further than apps, meaning Kernels, Roms etc. Now the reason you must Root your device in order to install a custom recovery, is because like explained above signature verification....Now this is when you begin to tread in warranty territory, once flashing a custom recovery...your warranty has become VOID, however what the custom recovery allows you to do is a multitude of things, but the most major is Flashing .ZIP files, which most roms are in the form of, now not only Roms are in ZIP files, so are kernels,mods,baseband firmwares, etc, with that being said, different phones/devices use different methods of flashing roms, lets say for example you somehow screwed something up on a samsung really bad, and it wont boot, however, you can still get into download mode...then you're safe, because samsung uses Odin to flash the entire phone back to stock meaning Recovery/aBoot/Data/System and bring you right back, but if you hard brick it, theres only 3 ways out from that...and they all suck....number one, is call me and send it to me to Jtag it for you ..but it takes long and its not that cheap, #2, Desolder the chip (whichever it is on the device that has caused the problem) and replace it...and thats not an easy task at all, ive done it once to an S3 successfully, after that i never wanted to do it again, and this was back when they were really expensive, and lastly....#3.....and this one is the worse....go buy a new one SO BE CAREFUL!
ROMS: So now that we have a custom recovery, a rom is basically a heavily modified version of Android! and let me tell ya, i love them...i love so many of them, there are sooo many different things that you can do with roms, but the most desired from what ive gathered, is so people can remove the bloatware that comes with their phone when they buy it from the carrier/manufacturer. Thats not all tho, there is way too much to get into, but some roms allow you to Overclock your phones CPU/GPU, and change the Behaviors of the phones hardware, and the major component in roms that allows that is the Kernel.
Kernel: Now dont totally quote me here, im still learning kernels, but a kernel is basically the binary software in the phone, almost like a bios that when modified from stock, changes the behavior of the MOST of the hardware, not all. Now i could be wrong and anyone please feel free to correct me, now i do want to give you a shot of my own advice here...if you dont know what you are doing, kernels are dangerous to a noobie..before i started messing with roms and kernels, i tried to get the best understanding i could, and ill be honest with you, i blew up a couple S3's doing so. but im still learning. so if you're unweary or still not educated enough in the hobby to get too it, please read more up on it, because as none of these guys here that are devs nor people like myself that are trying to help intend to destroy your device on you, so please be careful for your own device's safety, and to save yourself money and a broken heart.
Knox: Ok now correct me if im wrong here, because im still learning as this is new to me, i only saw it on the MJA bootloader on the S4 on Jellybean from Sprint when they first OTA'd it, but knox looks to be Samsungs pathetic try of not lettings us Access the devices binary software, like an encryption, or to only let us access and modify certain things, also samsung has added a flash counter, which will tell them how many times you have flashed a new rom, however there are ways around these things, google and the search bar are you best friends to start, and we can help too.
I Hope this helped and shed some light on some information, and please if anyone has anything to add or to correct me if im wrong anywhere please do so ^_^
P.S. To be totally honest, theres always a way to restore your device and even get the flash counter back to 0 again and put everything back to normal, if an experienced tech looks at it and puts it in download mode unless all is restored, hell be able to see everything, but honestly, if you pay off the phone, you havve nothing to worry about, but then again, i dont care much for warranties, so it all depends on how savvy with fixing problems when they go wrong, but if you ever need i can help you, im pretty experienced when it comes to everything but developing atm, i was a microelectronics major in college, so my expertise is mainly in hardware i.e. if you hard/soft brick the devvice i can usually get it out of that.
please excuse my typing, i type extremely fast, and i have a mechanical keyboard and i think some lettings are startings to give way such as the V key.
---------- Post added at 01:45 AM ---------- Previous post was at 01:29 AM ----------
Oh and please i Highly suggest using Philz Touch!
Code:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltetmo
Thats for the HLTETMO version, which is our versions in this forum, all credit to phil ofcourse, it is basically CWM, but so much more user friendly and advanced with much more options, there are two files there, you obviously want the latest version, and there are two ways to do it, if you download the tar.md5 you must use Odin, and put your phone in download/odin mode, very easily done (turn it off unplug usb and press Home+Vol Dwn+Pwr) then once the screen pops up press Vol Up and then plug the USB in, and follow the instructions of w/e tutorial you are ready, but be very careful in odin mode, if you disturb the phone while its flashing you will most likely brick it, and the .zip is considering you already have a custom recovery and you can just flash it through there.
Click to expand...
Click to collapse
Ty for the explanation. Unfortunately, that is if you took the time to write that or just copied, I knew most if not all of the risks. As I said earlier I've been rooting since gingerbread.
However, it's quite informative and anybody else who is new to rooting shall find it helpful.
Kernels are more or less a bios, if you will. But they are specific to builds. You can't use aosp on tw and vice versa. There are other key features but I can't remember off the top of my head. Basically no kernel =/= no phone or no features such as camera.
You're right about the s4, but if I'm not mistaken it was believed to be an eFuse, as was for the note 3 too. Although other members have said they got it back reset, 0x0, and sim unlocks intact to fix other issues like broken gps. Therefore it is believed to be software at a signature level.
And I'll look into philz, loved it on the s3. If you ever have q's about root feel free to pm me
Sent from my SM-N900T using XDA Premium 4 mobile app
Towle said:
He's not wrong. There are a couple different methods of rooting that don't require a custom recovery, therefore don't trip Knox.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Wow... must have read that post wrong. Been working way too much. Sorry about that but looks like we have some great info added here.
Naturesretard said:
Ty for the explanation. Unfortunately, that is if you took the time to write that or just copied, I knew most if not all of the risks. As I said earlier I've been rooting since gingerbread.
However, it's quite informative and anybody else who is new to rooting shall find it helpful.
Kernels are more or less a bios, if you will. But they are specific to builds. You can't use aosp on tw and vice versa. There are other key features but I can't remember off the top of my head. Basically no kernel =/= no phone or no features such as camera.
You're right about the s4, but if I'm not mistaken it was believed to be an eFuse, as was for the note 3 too. Although other members have said they got it back reset, 0x0, and sim unlocks intact to fix other issues like broken gps. Therefore it is believed to be software at a signature level.
And I'll look into philz, loved it on the s3. If you ever have q's about root feel free to pm me
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ahh nate, i misunderstood, i thought you were new to rooting but just knew some of the basics, but were unclear of some others, but yeh, i typed that all up, no copy and paste here otherwise i would've credited the Author ^_^ but i hope it was Helpful, im sure its plastered and posted evverywhere around here, but maybe ill make a Write up somewhere to clarify things, because when i was learning, everything was scattered and i had to collect all the information.
MasterSe7en said:
ahh nate, i misunderstood, i thought you were new to rooting but just knew some of the basics, but were unclear of some others, but yeh, i typed that all up, no copy and paste here otherwise i would've credited the Author ^_^ but i hope it was Helpful, im sure its plastered and posted evverywhere around here, but maybe ill make a Write up somewhere to clarify things, because when i was learning, everything was scattered and i had to collect all the information.
Click to expand...
Click to collapse
You Be Surprised How Often that happens. I'd sticky if I could
Sent from my SM-N900T using XDA Premium 4 mobile app
Naturesretard said:
You Be Surprised How Often that happens. I'd sticky if I could
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey Nate! **WAVE**
lol well i posted a new thread on it, so i hope it helps the newer guys and it'd be nice if it was stickied, like i said tho, its plastered everywhere around here and on google even, but its nice to try to help my Fellow note 3'ers
My wife and I have decided to hang onto our Note 7s, because why risk it with just one when you can play life in hard-mode? Sadly, she upgraded via the forced OTA, not knowing any better. Now that her battery is limited to 60%, she's extremely irritated by the popup notice she has to close every time the screen is turned on. I have tried searching, but cannot find instructions on resetting the phone back to stock (pre-OTA). Any help would be greatly appreciated. Thanks.
* Please spare this thread of the "omg you're crazy, return your bombs immediately" posts.
NarcissusV said:
My wife and I have decided to hang onto our Note 7s, because why risk it with just one when you can play life in hard-mode? Sadly, she upgraded via the forced OTA, not knowing any better. Now that her battery is limited to 60%, she's extremely irritated by the popup notice she has to close every time the screen is turned on. I have tried searching, but cannot find instructions on resetting the phone back to stock (pre-OTA). Any help would be greatly appreciated. Thanks.
* Please spare this thread of the "omg you're crazy, return your bombs immediately" posts.
Click to expand...
Click to collapse
Hi, well I won't say your crazy because I truly love my N7 and was very reluctant to do as requested and return and purchase a new phone. But I finally relented and bought the new Google Pixel Xl and have now been waiting over a month to receive it. Called Verizon last week they said I would have it Monday(yesterday), never did get it. Meanwhile I've managed to keep postponing this update I knew was the battery limiting ota for more than a week now. That is until tonight when I accidentally hit update. I am extremely pissed as I work for a government contractor and am constantly on my phone, and now must deal with only a 60% max battery to get me through a day when even a fully charged one couldn't. My only thought is maybe if I rooted the phone I would somehow be able to do something that way, perhaps by flashing the original factory software prior to the OTA. But I am just waiting on my new replacement and don' t really want to root for what could only be a day then un root to send back when my Pixel XL arrives. But it may be worth a shot on your wife's N7. Although I understand your decision to keep your N7's , as I really love mine, this deliberate hijacking of my personal property by Samsung and Verizon, has only streangthened my resolve to never purchase another Samsung phone again, I've owned every Note that has been made and as much as I love owning and using them, this will be the last time I allow them to take my money and reneder my phone useles. Samsung may not go under because of losing me as a customer, but they are definatally feeling the loss of the many who chose a different brand to replace their N7's. Good luck to you with your wife's N7. Please update if you try the root method so that others may also benefit.
Best wishes.
LvnInOC
Sadly, I believe it's impossible to revert back to 100% battery if you've already taken the update.
Get the PHE firmware from SamFirm, since SamMobile has removed all US Note 7 firmware, and use Odin to reflash it and then block the PK1 update (60% battery) with PDP or PDP+ (use manual mode to enter the package names) by disabling these 2 packages.
com.sec.android.soagent
com.samsung.sdm
Interpretation please
Woofa59 said:
Get the PHE firmware from SamFirm, since SamMobile has removed all US Note 7 firmware, and use Odin to reflash it and then block the PK1 update (60% battery) with PDP or PDP+ (use manual mode to enter the package names) by disabling these 2 packages.
com.sec.android.soagent
com.samsung.sdm
Click to expand...
Click to collapse
For those of us who have not yet learned the technical jargon, could someone help with more details about exactly how to do what you described. Is there a another thread or instructions somewhere that would detail this step-by-step for the novice? Better yet, if there is someone in the Tucson/Phoenix Arizona area who is in EXPERT at doing these and have been successful, I would be happy to pay a small success fee to have them do this for me..
garybiz said:
For those of us who have not yet learned the technical jargon, could someone help with more details about exactly how to do what you described. Is there a another thread or instructions somewhere that would detail this step-by-step for the novice? Better yet, if there is someone in the Tucson/Phoenix Arizona area who is in EXPERT at doing these and have been successful, I would be happy to pay a small success fee to have them do this for me..
Click to expand...
Click to collapse
Here's a link to what I believe he's talking about: http://samfirm.net/threads/update-safely-firmware-galaxy-note7-all-model-22-09-2016.119/ For Verizon, click the link next to the SM-N930V with the long filename. Be careful which download button you press! I downloaded the file, which is 2.66 GB, and scanned it with antivirus. FYI, I have not tried flashing the ROM yet as my phone has not been updated.
You'll also need the Odin software, which there is a link to, with instructions, towards the bottom of that page. EDIT: After looking more closely, the download link for Odin is impossible to read. Here is a better link: http://odindownload.com/download/#.WCzsCCRGZgE If none of this makes sense, dig in to the XDA forums. Everything you need is here.
Please report back if this actually works!
Also, PDP = Package Disabler Pro: http://forum.xda-developers.com/verizon-note-7/help/update-forced-to-phone-verizon-t3495730
Verizon shut down service ?
chrisnosleep said:
Here's a link to what I believe he's talking about: http://samfirm.net/threads/update-safely-firmware-galaxy-note7-all-model-22-09-2016.119/ For Verizon, click the link next to the SM-N930V with the long filename. Be careful which download button you press! I downloaded the file, which is 2.66 GB, and scanned it with antivirus. FYI, I have not tried flashing the ROM yet as my phone has not been updated.
You'll also need the Odin software, which there is a link to, with instructions, towards the bottom of that page. EDIT: After looking more closely, the download link for Odin is impossible to read. Here is a better link: http://odindownload.com/download/#.WCzsCCRGZgE If none of this makes sense, dig in to the XDA forums. Everything you need is here.
Please report back if this actually works!
Also, PDP = Package Disabler Pro: http://forum.xda-developers.com/verizon-note-7/help/update-forced-to-phone-verizon-t3495730
Click to expand...
Click to collapse
Thanks,
BUT, what is your opinion - will / can verizon stop service to all N7 phones eventually. Then all this is for nothing . What is the consensus on that one ???
chrisnosleep said:
Here's a link to what I believe he's talking about: http://samfirm.net/threads/update-safely-firmware-galaxy-note7-all-model-22-09-2016.119/ For Verizon, click the link next to the SM-N930V with the long filename. Be careful which download button you press! I downloaded the file, which is 2.66 GB, and scanned it with antivirus. FYI, I have not tried flashing the ROM yet as my phone has not been updated.
You'll also need the Odin software, which there is a link to, with instructions, towards the bottom of that page. EDIT: After looking more closely, the download link for Odin is impossible to read. Here is a better link: http://odindownload.com/download/#.WCzsCCRGZgE If none of this makes sense, dig in to the XDA forums. Everything you need is here.
Please report back if this actually works!
Also, PDP = Package Disabler Pro: http://forum.xda-developers.com/verizon-note-7/help/update-forced-to-phone-verizon-t3495730
Click to expand...
Click to collapse
Using that link, next to the SM-N930V has a link to the PHE firmware, which is precisely what I don't want, correct? If I'm correct, I'm guessing the PH1 firmware is what I would want to flash, yes? Is it as simple.? Just...flashing back the stock PH1 firmware via ODIN? I see people having issues that try and root after accepting the PHE update, so why wouldn't they be able to just do this (flash PH1 and complete the root process)?
FYI: PH1 stock firmware here: http://forum.xda-developers.com/ver...-your-verizon-note-7-and-quick-guide-t3443994
First off, I am a newbie here, so please be kind.
I have a Samsung Galaxy Note 4 (SM-N910V), running Android 6.0.1 stock Verizon ROM.
I have been getting some strange battery issues. Not charging to 100%, shutting off at 35%, stuff like that.
I have wiped the cache partition and done a factory reset with no luck.
I have replaced the battery.
When I boot into recovery mode, I get dead Android, no command.
I don't know if the problems are related, but I suspect so.
Don't know what else to do. Any help would be appreciated.
soccerplayer00321 said:
First off, I am a newbie here, so please be kind.
I have a Samsung Galaxy Note 4 (SM-N910V), running Android 6.0.1 stock Verizon ROM.
I have been getting some strange battery issues. Not charging to 100%, shutting off at 35%, stuff like that.
I have wiped the cache partition and done a factory reset with no luck.
I have replaced the battery.
When I boot into recovery mode, I get dead Android, no command.
I don't know if the problems are related, but I suspect so.
Don't know what else to do. Any help would be appreciated.
Click to expand...
Click to collapse
Do you have an unlocked bootloader (root)? You could try reflashing twrp with odin to get recovery back.
No, not rooted. Have always been afraid to brick the device. If that is the direction that I have to go then I will give it a shot. I figure there are enough directions on here I could probably figure it out.
soccerplayer00321 said:
No, not rooted. Have always been afraid to brick the device. If that is the direction that I have to go then I will give it a shot. I figure there are enough directions on here I could probably figure it out.
Click to expand...
Click to collapse
If you don't want to root, you could try flashing the cpd1 firmware with odin and that should overwrite what might be throwing off your battery calibration. Unless it's a hardware problem that is. Are you comfortable using odin? Also if you have no interest in rooting, you could flash the most recent firmware.
I am a little familiar with Odin. I used it to put Android 6.0.1 onto my phone. Cpd1? This is the first that I am hearing (or reading) anything about cpd1. I would be interested in rooting, the biggest problem that I have with doing so is that most of the instructions that I have found are written for someone who has a better grasp of this stuff that I do. Do you know of any simple step-by-step walkthroughs? One that a newbie like myself could actually follow.
From what I've read about rooting, I am definitely interested, but still paranoid about bricking the phone. I do have an S5 as a backup if need be, so I am reluctantly willing to give it a shot.
soccerplayer00321 said:
I am a little familiar with Odin. I used it to put Android 6.0.1 onto my phone. Cpd1? This is the first that I am hearing (or reading) anything about cpd1. I would be interested in rooting, the biggest problem that I have with doing so is that most of the instructions that I have found are written for someone who has a better grasp of this stuff that I do. Do you know of any simple step-by-step walkthroughs? One that a newbie like myself could actually follow.
From what I've read about rooting, I am definitely interested, but still paranoid about bricking the phone. I do have an S5 as a backup if need be, so I am reluctantly willing to give it a shot.
Click to expand...
Click to collapse
I was just referring to the first mm firmware that ends with cpd1 and the reason I suggested that particular one was just in case you were thinking of rooting. If you use any of the "safe" firmwares you should be ok though. I agree about the rooting process, it's not the most user friendly thing I've ever seen, but it really isn't as bad as it looks. As long as your using the files provided in those threads there really isn't a huge risk in bricking your phone. Worst case scenario, you get into a jam that takes a little while to get out of so be sure that you leave yourself time to recover in case you can't use your phone for a couple hours. I think the worst part is the instability of kingroot which means you have to do all the adb commands as quick as possible and the fact that if you want mm you have to do the root process twice. These are the two posts that got me through it:
Lollipop
Marshmallow
Start with Lp first, it's necessary to unlock that before going to mm. If your problem is software related, installing the firmwares to root should fix things. Best of luck!
kevintm78 said:
I was just referring to the first mm firmware that ends with cpd1 and the reason I suggested that particular one was just in case you were thinking of rooting. If you use any of the "safe" firmwares you should be ok though. I agree about the rooting process, it's not the most user friendly thing I've ever seen, but it really isn't as bad as it looks. As long as your using the files provided in those threads there really isn't a huge risk in bricking your phone. Worst case scenario, you get into a jam that takes a little while to get out of so be sure that you leave yourself time to recover in case you can't use your phone for a couple hours. I think the worst part is the instability of kingroot which means you have to do all the adb commands as quick as possible and the fact that if you want mm you have to do the root process twice. These are the two posts that got me through it:
Lollipop
Marshmallow
Start with Lp first, it's necessary to unlock that before going to mm. If your problem is software related, installing the firmwares to root should fix things. Best of luck!
Click to expand...
Click to collapse
First off, thanks for your help. I appreciate it.
I finally got around to trying to do this with my phone and I can't even get past the first step. Install King Root, 4.8.5. I've tried 4.8.5 and 5.0, and neither one of them can get root access. Don't know what else to try.
soccerplayer00321 said:
First off, thanks for your help. I appreciate it.
I finally got around to trying to do this with my phone and I can't even get past the first step. Install King Root, 4.8.5. I've tried 4.8.5 and 5.0, and neither one of them can get root access. Don't know what else to try.
Click to expand...
Click to collapse
Did you ever have any luck with kingroot? If you haven't tried already, do a factory reset before you start the process and if it fails uninstall, reboot, reinstall and try again. I know it's a frustrating process and it seems to take most people many tries. When it fails on you how far does it get?
Kingroot was really frustrating. It would never get past 52%. After countless tries I moved to kingoroot. Kingo root worked on first try. Glad I unlocked and rooted my note 4
Sent from my SM-N910V using XDA-Developers mobile app
kevintm78 said:
Did you ever have any luck with kingroot? If you haven't tried already, do a factory reset before you start the process and if it fails uninstall, reboot, reinstall and try again. I know it's a frustrating process and it seems to take most people many tries. When it fails on you how far does it get?
Click to expand...
Click to collapse
No luck on Kingroot. It usually dies around 25% or so. Sometimes a little before that and sometimes after that. It never even got into the 35% range.
What I think I am going to do is go back to kitkat, original samsung rom. Try Kingoroot and see if that works. If not, I will push lolipop to it and try kingoroot again. If that doesn't work, I will try to push Marshmallow to it and try one more time. Hopefully one of them will be successful.
Ive never had issues bringing a device back on OS but this N4 is kicking my a&% bad. bought a used ( basically new ) sm-n910v it was updated to 6.0.1 mm and I'm not crazy about the MM I like KK and ive tried every firmware file known to man ive tried to slowly step back from 6.0 to 5.1.1 then 5.0 then 4.4.4 and they all fail says binary fused to boot 1 or something else and with 5.1.1 gets right to the end 99% then fails. would like to root and BL unlock any suggestions would be great. thanx in advance.
fastjohnson said:
Ive never had issues bringing a device back on OS but this N4 is kicking my a&% bad. bought a used ( basically new ) sm-n910v it was updated to 6.0.1 mm and I'm not crazy about the MM I like KK and ive tried every firmware file known to man ive tried to slowly step back from 6.0 to 5.1.1 then 5.0 then 4.4.4 and they all fail says binary fused to boot 1 or something else and with 5.1.1 gets right to the end 99% then fails. would like to root and BL unlock any suggestions would be great. thanx in advance.
Click to expand...
Click to collapse
I believe you can only get root on kk with a developer edition version of the v model. If it's a retail version and you want root it has to be at least 5.1.1 unfortunately. Have you tried the links in this post? Imo those are the best guides that I've seen to get your bootloader unlocked.
kevintm78 said:
I believe you can only get root on kk with a developer edition version of the v model. If it's a retail version and you want root it has to be at least 5.1.1 unfortunately. Have you tried the links in this post? Imo those are the best guides that I've seen to get your bootloader unlocked.
Click to expand...
Click to collapse
Yah I've tried most of them 5.1.1 gets to 98% then pooches out its exciting then bombs out, lol 4.4 doesn't get passed cache then fails. I'm using Odin 30.9, high quality data cable, thing is I can't move 》 till I can root to unlock the bootloader. My CID is 150 so that's good and I'm factory resetting the phone and pulling the SD card so it cannot mess with the flash. I'm running the NO_ A boot firmware that flashed perfect. Maybe I'm doing something wrong but I'm following the directions to the point.
fastjohnson said:
Yah I've tried most of them 5.1.1 gets to 98% then pooches out its exciting then bombs out, lol 4.4 doesn't get passed cache then fails. I'm using Odin 30.9, high quality data cable, thing is I can't move 》 till I can root to unlock the bootloader. My CID is 150 so that's good and I'm factory resetting the phone and pulling the SD card so it cannot mess with the flash. I'm running the NO_ A boot firmware that flashed perfect. Maybe I'm doing something wrong but I'm following the directions to the point.
Click to expand...
Click to collapse
It may not make a difference, but there is a newer version of Odin here that you could try.
kevintm78 said:
It may not make a difference, but there is a newer version of Odin here that you could try.
Click to expand...
Click to collapse
I'll give it a shot, right now I'm a Lil burned out on trying this because my other phone LG g4 is boot looped for no reason so I'm down to just my N4 and my N3 my gf has it. I forsee a big cup of coffee at 3am and let the flashing begin. Oh FYI I did try I think Odin 3.10 version it failed quicker so I'll try this version in the morning. I appreciate your help very much you'll be the 1st to know if it pushes through. Merry Christmas btw.
back on topic, I'm seeing kernel wakelocks for msm_hsic_host on Oscar kernel v1.3 but I'm pretty sure that was not always the case. Since that kernel hasn't been updated in a little while, I'm looking at others. Anyone got a preferred kernel with JasmineROM 7?
fz798 said:
back on topic, I'm seeing kernel wakelocks for msm_hsic_host on Oscar kernel v1.3 but I'm pretty sure that was not always the case. Since that kernel hasn't been updated in a little while, I'm looking at others. Anyone got a preferred kernel with JasmineROM 7?
Click to expand...
Click to collapse
Reflashed and thought the wakelocks were gone, but not so. msm_hsic_host appears to be related to cellular.
flyers00 said:
Kingroot was really frustrating. It would never get past 52%. After countless tries I moved to kingoroot. Kingo root worked on first try. Glad I unlocked and rooted my note 4
Click to expand...
Click to collapse
What I've noticed with this bootloader unlock is, like right now I'm 5.1.1 and my bootloader is unlocked but not rooted. OK if I use the the no A boot 6.0.1 file to flash mm it's stay unlocked and you can be rooted but if you use the normal full firmware 6.0.1 cpd1 file you lose your unlocked BL and back to start. Normally you unlock a BL it's stays unlocked no matter what you do. OK bugs with the no A boot 6.0.1 mm file no WiFi that's it. I really dislike 5.1.1 it sucks so there's not a lot of choices here. Good work on this exploit though.