Related
Someone tell me how I can clean my phone, I need to wipe it completely, and reinstall everything from scratch. Really wish I had rooted first, would have been alot easier, alot more resources for root.
Thariz said:
Someone tell me how I can clean my phone, I need to wipe it completely, and reinstall everything from scratch. Really wish I had rooted first, would have been alot easier, alot more resources for root.
Click to expand...
Click to collapse
Menu>Settings>SD & Phone Storage>Factory Reset
let me repeat my question, and get more specific. I need to wipe all data off my phone, everything.
Then I need to get the OS back on it.
Can someone tell me if you can do this without root, I need to completely clear all partitions AFAIK and then get a new CLEAN UNHACKED OS onto my phone.
Factory reset is not enough
RUU is not enough (alone anyway)
I need to get the flashable regions of my phone totally clear of malicious code.
bump for edit for previous
I don't think you have any options without root...only other option without root is boot into bootloader and clear storage.
For curiousity, what did you do that you need to undo and how could you have pushed "malicious code" onto other partitions without root?
unless you work for HTC or know somone that does, i thnk you are pretty boned, even contacting them directly all ive gotten is the usual "it cant be done" line so ....just wait for the hboot to get hacked and do it then i suppose..
What Android version are you on and your phone is currently rooted correct?
He stated in original post that it is NOT rooted.
4.24 gb EVO
hacked as hell
i think it was rooted before not to my knowledge, and flashed. also calendar exploited via google, I hope i can get some help outside the dev forum, because I i know they dont like questions there, thats why im posting here instead.
cant clean it now that i have OTA'd to GB.
I am finding alot of cool app engines along my trials and tribulations. makes me wish I had not stopped working in security several years back.
Someone gonna give a guy a hand? I am as trustworthy as they come if you are worried about anything getting out and about.
If it was rooted before, go into the bootloader and check if it says S-ON or S-OFF. If it's S-OFF, you can flash a recovery and now you're rooted again.
If it's S-ON, no, you can't do anything right now.
yeah im screwed
i just love it when my camera and speaker come on and monitor me all day and night long.
Thariz said:
yeah im screwed
i just love it when my camera and speaker come on and monitor me all day and night long.
Click to expand...
Click to collapse
Sigh...ok...I'll bite. Why do you think your phone is doing this? What evidence?
And does the tin foil mess up your hair?
i watch the logs, i see the mic and or cameras come on, i see the filesys filling where I cant go see it because im not root, i see the traffic as it xmits it from local host to local host, i see the traces of the encryption keys and stunnels. This is only one instance.
I hope there is someone around here who has something more to offer than the people outside the dev forums, im getting killed following the rules.
So let me get this straight and my apologizies for sounding confuzed becasue every reply has been all over the place and has been of no real help to you yet..
Your on GB version 4.24 correct? Previously Rooted without you knowing? Your trying to get back too 100% stock as well? I hope I'm following this so far.
1st, the easiest way, download Root Checker from the Market and that will tell you right off the bat if your rooted or not. If thats not possible, enter bootloader as stated before and verify S-Off at top of screen. If so, flash Amon_Ra Recovery (rename to PC36IMG.zip if not already and place on root of SD Card). Enter bootloader and let it scan, apply update and from there you can do what you need to do. If it says S-On but you know your rooted, go to xHausx Auto Root guide, download the Froyo 3.70.651 Stock rom and place on Root of Sd Card named PC36IMG.zip, enter bootloader, let it scan and apply update, that will take you too 100% stock Froyo with hBoot 2.10 and you can apply GB update if desired or root with whatever method of your choice.
Once again, sorry if this is not what you were wanting but its irritating when you get the run around and people talk about tin foil hats and ridiculous stuff...and agreed, very hard to follow rules when most replies are worthless.
Heaterz16 said:
He stated in original post that it is NOT rooted.
Click to expand...
Click to collapse
Read 1 post below yours, only way to figue out how to help is to know the details. Good 2 cents though.
I will give it a go, after I upgraded OTA it made me s-on, so i think im just screwed now.
I tried the ruu to go back but as you know it says too old files etc
i imagine this will do the same but i will try anything once, the guys at sprint gave me the go ahead to do whateever i need to do to try to backrev this thing, and if i brick it they will replace it so im up for ANYTHING PEOPLE
If you were originally s-off, the ota shouldn't have updated hboot. It can't turn you s-on, unless you reverse it yourself first..
Which means you were always s-on, and currently there is no way to assist you.
lets start over. are u S-OFF or S-ON? that will determine what ur options are.
Thariz said:
I will give it a go, after I upgraded OTA it made me s-on, so i think im just screwed now.
I tried the ruu to go back but as you know it says too old files etc
i imagine this will do the same but i will try anything once, the guys at sprint gave me the go ahead to do whateever i need to do to try to backrev this thing, and if i brick it they will replace it so im up for ANYTHING PEOPLE
Click to expand...
Click to collapse
There isn't anything that can be done for you at the moment. You said your s-on which means your not rooted which in turn means your bootloader is locked and you can't install a recovery and install the files you need to fix your problem. So I would call Sprint and tell em your device is being defective.
pnewgaard said:
Read 1 post below yours, only way to figue out how to help is to know the details. Good 2 cents though.
Click to expand...
Click to collapse
If you could read his original post, he said - it is currently not rooted - who cares if it was rooted before or not. He has S-ON = NOT rooted = he is out of luck...
That's my 3 cents
I assume since this is the AT&T Galaxy S 3 section, you already know that I have the SGH-i747 model.
So I've been looking for a while, and I can't find anyone that has caused my same problem the way I did. I'll give the entire story: After having my S3 for a while, I decided to try rooting. I did it successfully, and got CyanogenMod installed. I don't know what, but I wanted to go back to touchwiz. I loaded a backup because it was exactly what I had before CM. fast forward about a month and a half, AT&T keeps bugging me about some update. It's the 4.3 update, I find out, after I installed it. Now, here's the confusing part. The SuperUser app was left over, but I have no CWM and no root privileges. I used this watch?v=yuBuD9aL12o (Paste after yt url) tutorial to root and get SuperSU, and it worked. The phone restarted many times in that entire process, and in the end it worked. One forum told me to install and apk called EZ-Unlock12.apk to unlock my boot loader. (I have included the exact APK if you want to look at it.) It just said successful and I closed out. Now, I wanted to flash CWM again with ODIN. I installed the drivers, and booted up ODIN. This is when it happened. I loaded up the CWM.tar.md5 file into ODIN, (not exact file name but you get what I mean), and it did it's verification and said it was good. I don't remember having my phone plugged in while doing this. I went to shut down my phone and put it in DL/ODIN mode. But now it has happened. I tried to bring my phone back up, but it didn't give ANY feedback. The only possible way to make it do ANYTHING is to plug it in without the battery, and i get the red light. I think it may have been that boot loader unlock program that messed it up, but I can't say for sure.
TL;DR I hardbricked my phone and don't know what went wrong.
Is that app for the verizon version of the s3? I believe the AT&T version of the s3 is the SGH-i747; however, your post refers to the sch-747 in the first line. From everything I have read, there is no way to unlock the AT&T s3 bootloader.
Not sure if this would help: http://forum.xda-developers.com/showthread.php?t=2549068
audit13 said:
Is that app for the verizon version of the s3? I believe the AT&T version of the s3 is the SGH-i747; however, your post refers to the sch-747 in the first line. From everything I have read, there is no way to unlock the AT&T s3 bootloader.
Not sure if this would help: http://forum.xda-developers.com/showthread.php?t=2549068
Click to expand...
Click to collapse
I meant SGH-i747, sorry for any confusion.
Did you try the unbricking method I linked? I think that may be the only way to unbrick the phone since it appears that your bootloader has been corrupted. If the unbrick method doesn't work, you'll probably have to have it repair via jtag.
Were you able to get it back to normal state? I am in the same situation as you with the same problem and was wondering if i should go do the method someone provided or just go ahead and pay for a jtag service.
I got a new HTC One m8 from Tmobile a few weeks ago and instantly went to root and find out about S on and how I can get rid of it. I followed a rooting tutorial on unlockr diligently and unlocked bootloader and installed TWRP and SuperSU. I moved on to S-off the device and got to the last step of the tutorial where it starts to "chug" bottles(Firewater). After the first bottle, it tells me I'm out of luck and that my phone is patched. This confused me. Does this mean that my phone is forever stuck S-on? or does it mean that the developers of firewater haven't developed an S-off method for the newest version of HTC's software and that I simply have to wait.
This is just my first problem, even though I can't flash custom ROMs I was fine because I was willing to give the stock ROM a chance and just tweak it with root privileges, but no, the next time I had to restart for some various reason it starts bootlooping every few minutes. I swear I didn't do anything wrong when rooting. Is it just too new and the newest HTC software makes the rooting process obsolete making it impossible to root?
So I end up wiping the phone not being able to save all the pictures I took on my trip in the mountains. My phone is still rooted but the phone is wiped. I go about thinking the solution is fixed and when I decide to nandroid backup, I go into recovery, do a simple backup and when I restart it goes straight back to the infuriating bootloop. A simple nandroid backup shouldn't make it go into a bootloop.
So I decide to relock the bootloader, install the stock recovery and software again and start over. Maybe I really did mess up rooting. I go through the process again and low and behold my phone goes into a bootloop again.
I'm so sick and tired of this phone and I'm not sure why it always seems to happen to me. I follow the tutorials closely and it always ends up ****ting on me.
It recently went into a bootloop after a good 3 day run where I managed to keep the phone on the entire time. Had to restart because the wifi antenna wasn't working and another bootloop ensued. I decided to make this thread to see if any other new users are experiencing similar difficulties and seeing if anyone knows a cause or maybe a solution. Right now in the process of unrooting and going back to stock.
It would be a shame if there really is no way for me to unlock the full potential of my new phone. Almost wishing I had bought a nexus.
Thank you for anyone who was willing to read that and to anyone who takes the time to write a response. Thanks!
westonnate said:
I got a new HTC One m8 from Tmobile a few weeks ago and instantly went to root and find out about S on and how I can get rid of it. I followed a rooting tutorial on unlockr diligently and unlocked bootloader and installed TWRP and SuperSU. I moved on to S-off the device and got to the last step of the tutorial where it starts to "chug" bottles(Firewater). After the first bottle, it tells me I'm out of luck and that my phone is patched. This confused me. Does this mean that my phone is forever stuck S-on? or does it mean that the developers of firewater haven't developed an S-off method for the newest version of HTC's software and that I simply have to wait.
This is just my first problem, even though I can't flash custom ROMs I was fine because I was willing to give the stock ROM a chance and just tweak it with root privileges, but no, the next time I had to restart for some various reason it starts bootlooping every few minutes. I swear I didn't do anything wrong when rooting. Is it just too new and the newest HTC software makes the rooting process obsolete making it impossible to root?
So I end up wiping the phone not being able to save all the pictures I took on my trip in the mountains. My phone is still rooted but the phone is wiped. I go about thinking the solution is fixed and when I decide to nandroid backup, I go into recovery, do a simple backup and when I restart it goes straight back to the infuriating bootloop. A simple nandroid backup shouldn't make it go into a bootloop.
So I decide to relock the bootloader, install the stock recovery and software again and start over. Maybe I really did mess up rooting. I go through the process again and low and behold my phone goes into a bootloop again.
I'm so sick and tired of this phone and I'm not sure why it always seems to happen to me. I follow the tutorials closely and it always ends up ****ting on me.
It recently went into a bootloop after a good 3 day run where I managed to keep the phone on the entire time. Had to restart because the wifi antenna wasn't working and another bootloop ensued. I decided to make this thread to see if any other new users are experiencing similar difficulties and seeing if anyone knows a cause or maybe a solution. Right now in the process of unrooting and going back to stock.
It would be a shame if there really is no way for me to unlock the full potential of my new phone. Almost wishing I had bought a nexus.
Thank you for anyone who was willing to read that and to anyone who takes the time to write a response. Thanks!
Click to expand...
Click to collapse
If you wanna fix it quick then just do an RUU (t-mobile one) and after you've done that use Sunshine to root, unlock and S-OFF your phone. All though Sunshine costs $25 it is a sure fire to work.
You can find a tutorial for the RUU in the t-mobile forum I believe, not sure as im replying to this before I go to bed but it should have one. If by some chance "TMO" doesn't mean T-Mobile then my bad. Anyways if you get confused take your time and do your research or wait for someone else or me to assist you further.
Also if you used Xposed then that could be the problem, I've had it randomly bootloop me after days of use, just google the Xposed deactivate script zip or Uninstaller script and flash it to remove it. If you don't have it then don't do this part.
Lastly I doubt you'll regret buying an M8 after you get it setup properly, it's a great phone but of course that's just mine and a lot of people's opinion. Anyways good luck and hope one of my solutions fix it! If not then don't be afraid to ask more questions or request further assistance whether from me or someone else.
S1L3nTShaDoWz said:
If by some chance "TMO" doesn't mean T-Mobile then my bad.
Click to expand...
Click to collapse
It does, although T-Mobile is a huge carrier in Europe, and AFAIK only the US T-Mob variant has an RUU (and not immediately clear what version the OP has).
You can flash custom roms without s-off, and have you tried wiping cache and fixing permissions? Idk if that'd solve it or not but worth a try.
Hey guys,
I'm kinda new to the HTC/Android world, found this community a damn good place to find support.. But now I've hit a road block.
Basically, I've been eager to root from day 1 of getting my first htc handset, I came across from jailbreak and loved the fact of customizability with Android.
So I had the Google play edition(I think, all geared towards Google) running Kit Kat 4.4.4. Love it, big Google user so this all tied together lovely.
Here is the Situation.
I found a video on youtube, cannot provide URL as I'm in work at the moment, but it was root guide from scratch. Fresh windows OS, seemingly a phone fresh out the box.. you get the idea.
I used the Hasoon2000 tool to root the device. Installed ADB etc on my pc, signed up as a a dev, got the Key for device, sent in and received my .bin file. I got up to actually rooting my device, well pleased and happy. Using TWRP via Hasoon2000.
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Queried this on another forum, decided to continue to be patient... but no replies, in the mean time I restored my apps and have a fiddle, see what the root function can do for myself.
I installed "Freedom 1.0.6" and a program called "Market Share"- Hate iAP, some games are ridiculously priced for the smallest of things, I just wanted to sandbox plague inc. ;(
Now the device is stuck in a boot loop, phone starts up, see the home screen for a bout 40 seconds/ one minute.. Some times I unlock the device and it goes back to flash screen then.. others I boot an app and its slides away once more.
This happened close to 15x before I left for work this morning and I imagine its just going to repeat this and run the battery - I tried to stop this loop by going into TWRP and possibly choosing to boot system this way may of stopped it.. but when I was on the boot screen with those options.. It said Tampered at top of screen and S-On- which has scared me quite a bit..
What the hell has happened!?
I'm desperate to know and don't want to have this damn thing bricked! Please help.. try explain like I'm 5, as said I'm new to a lot of this! >.<
first off, if the screen comes on, its not bricked.
esenfur said:
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Click to expand...
Click to collapse
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
redpoint73 said:
first off, if the screen comes on, its not bricked.
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
Click to expand...
Click to collapse
Thank you for fast response.
Official OTA - being that the phone its self said "Update the OS" - I just accepted this, hit download and began install as a reboot- didnt spot implications. As said, noob, followed a tut. If it highlighted DO NOT UPDATE or.. IF U WANT UPDATE NOW FOLLOW THIS- Great, but nothing of the sort?
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Or do you have any links to tutorials I could possibly follow?
Side note- when this loop started I deleted
esenfur said:
Or do you have any links to tutorials I could possibly follow?
Click to expand...
Click to collapse
This is really your main issue. By following a YouTube video and using a Toolkit, you've failed to actually learn anything or gain any real understanding or knowledge. Do yourself a favor and ditch the tutorials and videos (and toolkit for that matter) and do it the old fashioned way . . . by reading. Videos and step-by-step guides do you no good when things go south (as you've now discovered). And with the prior proper knowledge (usually not gained by following tutorials) this whole mess probably would have never happened in the first place.
A cardinal rule of Android phone modding: DO NOT accept/download/install OTAs (official OS updates) on a modded device unless you know what you are doing, and what the result will be. If in any doubt, simply DO NOT do it.
esenfur said:
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Click to expand...
Click to collapse
.exe file is Windows specific. You are looking for a zip file, and it typically starts with "OTA". Don't remember where its saved to, so you will have to search for it. If you can't keep the phone running long enough to do so, mount the memory on your computer and search that way.
Deleting the OTA file worked for me on a past device, although one M8 user in the same position said deleting the file didn't get him out of the loop. Flashing your ROM again, or wiping the internal memory (backup any important personal data first) might be options for you.
redpoint73 said:
you've failed to actually learn anything or gain any real understanding or knowledge.
Click to expand...
Click to collapse
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
redpoint73 said:
Videos and step-by-step guides do you no good when things go south (as you've now discovered).
Click to expand...
Click to collapse
agreed.. theres FAR much more I need to learn.. its scary haha.
redpoint73 said:
DO NOT accept/download/install OTAs (official OS updates)
Click to expand...
Click to collapse
taken on board. I know with my jailbreaks in past it has been a pain, assumed Android would be alot more stable to over write- due to functionality of OS and unlocked features.
I was being generic when I said .exe- basically the installer..
I returned from work to see phone stopped looping.. i could stop the install and deleted the file ASAP.. but now what.. Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Try to re-flash the ROM, with stok ROM, using TWRP and clean install. It should work.
hack14u said:
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Click to expand...
Click to collapse
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
First of all once the bootloader is unlocked you don't have to relock it to get OTA.
As I undersand you have done the following:
1) Unlock using HTCDev-Method
2) flashed a custom revocery (TWRP in your case)
3) flashed a supersu too!?
To install the OTA means loosing root acces. Thus you have to re-root it after the OTA is done. The other problem ist that STOCK OTAs don't work with a custom recovery. Meaning you would have to flash a stock recovery first, install the OTA second (as long as you didn't change anything an just root), and re-root third.
Let's have a look which stock recovery you would need:
1) reboot to bootloader
2) connect the phone to you PC and open cmd in you adb/fastboot folder
3) enter "fastboot getvar all"
4) paste this information here (but DELETE the IMEI and SERIAL NUMBER before posting!!)
As soon as we know which stock recovery you need we will go on.
esenfur said:
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
Click to expand...
Click to collapse
I'm not saying there is anything "wrong" with the toolkit, per se. For the most part, it does what its intended to do.
But it also shortcuts the learning process, and facilitates folks rooting the phone without gaining the proper knowledge. This is a dangerous thing.
This is just my opinion. But I strongly believe it. If you can't accomplish these things without a toolkit, you shouldn't be rooting your phone in the first place.
Others use the toolkits, and love them. They are more than entitled to have their own opinion. But when things go south, the toolkits aren't going to help; and those folks don't have the proper knowledge and they come running here. So you tell me what is the "best" way to root the phone?
esenfur said:
I was being generic when I said .exe- basically the installer..
Click to expand...
Click to collapse
I already figured this was probably the case. But I found it better to provide the exact information on what file to delete; rather than leaving it open to the possibility of you and/or others being misinformed.
esenfur said:
Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
Click to expand...
Click to collapse
Sounds like you still have TWRP installed, so just flash SU or SuperSU to gain root.
After that, you can use Titanium Backup or similar app to find the update process and freeze it, to stop the update notifications.
Don't remember the exact process (this is where searching and reading comes in for you) but its something like "drm..." or "updater".
I have this situation before,what i do is find the right stock recovery and flash..after ota done flash back custom recovery..?
esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
At this point after seeing this, I would suggest you take some time and start reading. All of your answers are here in the forums. Knowledge is power and within the pages of this site you will find everything you need.
To take the OTA find a stock recovery, to flash ROM's find the one you like and flash via your favorite recovery.
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.