Related
I am running v6.0.1.4 and it won't do anything.
It wont backup, restore, or install, it just freezes.
If I try to run a factory reset or a dalvic cache wipe it freezes too.
Nothing is working and I can't even start my phone because I tried to restore it and again, it froze.
Can anyone help me out here at all? I have no clue what to do, and I really would appreciate the help.
spuzwuzzel said:
I am running v6.0.1.4 and it won't do anything.
It wont backup, restore, or install, it just freezes.
If I try to run a factory reset or a dalvic cache wipe it freezes too.
Nothing is working and I can't even start my phone because I tried to restore it and again, it froze.
Can anyone help me out here at all? I have no clue what to do, and I really would appreciate the help.
Click to expand...
Click to collapse
Odin back to stock, or flash twrp and try that. Also this should not be in this section bud. Prepare to be flamed by the community
Sent from my SGH-T989 using xda app-developers app
I had the same thing happen to me when I updated to the latest one, it would freeze at either restoring, or wiping cache. Luckily I was able to just reboot, and everything was fine on the phone, I then downgraded to 5.XXX
I've been having the same issue on stock recovery, where it sometimes it freezes at wiping, then flash the one from rom manager and its all good. by the way mods please move the thread to Q/A
Wrong section bro. Please see the noob video.
Sent from my SGH-T989 using xda premium
You don't have to Odin stock or any of that stuff, just fastboot flash the 6.0.0.5 version (or that last one that worked for you) and you should be fine.
spuzwuzzel said:
I am running v6.0.1.4 and it won't do anything.
It wont backup, restore, or install, it just freezes.
If I try to run a factory reset or a dalvic cache wipe it freezes too.
Nothing is working and I can't even start my phone because I tried to restore it and again, it froze.
Can anyone help me out here at all? I have no clue what to do, and I really would appreciate the help.
Click to expand...
Click to collapse
Ok, don't panic. I've been having this twice a day every day for the past little while. I first started having this problem when I flashed MIUI JB, but very soon after every JB ROM out there started hanging on me, or killing my recovery in this fashion. It's fixable, though for the life of me I can't tell you what causes it.
Don't ODIN back to stock. Not yet anyway.
ODIN your very first recovery, just as if you are about to root your phone for the first time. ODIN CWM 5.0.2.7, not 6.0.1.4. Yes, it's ancient, I know. Catch your phone as it's rebooting after the flash, and get it to enter recovery. Don't let it boot into whichever ROM you have installed. Then go to MOUNT > MOUNT USB and attach your phone to the computer. Copy Darkside Superwipe over. Unmount from the computer and unmount from the phone. Then get CWM to run the script. You must superwipe your phone, so if you have something important, hope you have a backup. This time around it won't hang on you.
Your phone is recovered, you can now flash anything you want and it will work. You can restore your nondroid backup as well and this will also work. If your nandroid back is in the new CWM format, you will want to flash CWM v6 first. Feel free to flash whichever recovery works for you, but CWM 5.0.2.7 is your fallback recovery in case you need to recover your phone again. It is the only one that does not seem to get corrupted in this way.
You can ODIN back to stock now if you want to make absolutely sure everything is wiped clean, but in my experience this does not contribute much to the overall cleanliness of things: it's not called Superwipe for nothing. It doesn't hurt, though: as long as you do it AFTER you have superwiped, or not even ODIN will recover your phone. It really scared me once when I skipped the superwipe step and was left with a 100% stock phone which wouldn't boot.
---------- Post added at 10:28 PM ---------- Previous post was at 10:12 PM ----------
Careful with ODIN: Make sure you have NO PIT file selected, or you will kill your phone! Been there, done that, and I don't recommend it. Do it by the book!
kangelov said:
Ok, don't panic. I've been having this twice a day every day for the past little while. I first started having this problem when I flashed MIUI JB, but very soon after every JB ROM out there started hanging on me, or killing my recovery in this fashion. It's fixable, though for the life of me I can't tell you what causes it.
Don't ODIN back to stock. Not yet anyway.
ODIN your very first recovery, just as if you are about to root your phone for the first time. ODIN CWM 5.0.2.7, not 6.0.1.4. Yes, it's ancient, I know. Catch your phone as it's rebooting after the flash, and get it to enter recovery. Don't let it boot into whichever ROM you have installed. Then go to MOUNT > MOUNT USB and attach your phone to the computer. Copy Darkside Superwipe over. Unmount from the computer and unmount from the phone. Then get CWM to run the script. You must superwipe your phone, so if you have something important, hope you have a backup. This time around it won't hang on you.
Your phone is recovered, you can now flash anything you want and it will work. You can restore your nondroid backup as well and this will also work. If your nandroid back is in the new CWM format, you will want to flash CWM v6 first. Feel free to flash whichever recovery works for you, but CWM 5.0.2.7 is your fallback recovery in case you need to recover your phone again. It is the only one that does not seem to get corrupted in this way.
You can ODIN back to stock now if you want to make absolutely sure everything is wiped clean, but in my experience this does not contribute much to the overall cleanliness of things: it's not called Superwipe for nothing. It doesn't hurt, though: as long as you do it AFTER you have superwiped, or not even ODIN will recover your phone. It really scared me once when I skipped the superwipe step and was left with a 100% stock phone which wouldn't boot.
---------- Post added at 10:28 PM ---------- Previous post was at 10:12 PM ----------
Careful with ODIN: Make sure you have NO PIT file selected, or you will kill your phone! Been there, done that, and I don't recommend it. Do it by the book!
Click to expand...
Click to collapse
what do you mean my very first recovery? Also, I'm not familiar with Odin, I just install it on my pc right?
Miui JB is what I did too. Love me some Miui, but too many bugs. I can't even find the ICS Miui anymore...
spuzwuzzel said:
what do you mean my very first recovery? Also, I'm not familiar with Odin, I just install it on my pc right?
Miui JB is what I did too. Love me some Miui, but too many bugs. I can't even find the ICS Miui anymore...
Click to expand...
Click to collapse
Look, I'm sorry for your troubles but there is a good reason why we have four different sections. This thread being in DEVELOPMENT is only causing clutter. You will get much better help if its moved to its proper place, Q&A or general. Please PM a Mod to move this.
Sent from my SGH-T989 using xda premium
spuzwuzzel said:
what do you mean my very first recovery? Also, I'm not familiar with Odin, I just install it on my pc right?
Miui JB is what I did too. Love me some Miui, but too many bugs. I can't even find the ICS Miui anymore...
Click to expand...
Click to collapse
I am referring to the process you followed to install CWM on a stock phone. It didn't come with CWM already loaded, so you must have loaded it somehow. If not with ODIN, then what did you use?
kangelov said:
I am referring to the process you followed to install CWM on a stock phone. It didn't come with CWM already loaded, so you must have loaded it somehow. If not with ODIN, then what did you use?
Click to expand...
Click to collapse
I dont really know where to find 5.0.2.7. the website doesnt seem to have it. I used revolutionary
Thank you for your contribution to the development of the gs2.
Sent from my SGH-T989 using xda premium
Download the clock work mod app from playstore. Then your first choice after opening the apk, your first possible choice is flash cwm, do that. Pm me after that if you need help. he should be good now thanks
Sent from my SGH-T989 using xda app-developers app
Rushing said:
Download the clock work mod app from playstore. Then your first choice after opening the apk, your first possible choice is flash cwm, do that. Pm me after that if you need help. he should be good now thanks
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
There is no clockworkmod app, unless you mean rom manager. At least, I can't find any. Also, I can't even get my rom to load at all
spuzwuzzel said:
There is no clockworkmod app, unless you mean rom manager. At least, I can't find any. Also, I can't even get my rom to load at all
Click to expand...
Click to collapse
Now that you are in the right place, I will help you. It looks like you flashed a corrupted recovery. What you need to is Odin flash CWM. Go here
http://forum.xda-developers.com/showthread.php?p=27290471
Download Odin and recovery.tar, and Odin flash it. Will boot up just fine after. Don't fear Odin. Its safe as long as you are careful and READ!!
Sent from my SGH-T989 using xda premium
LoopDoGG79 said:
Now that you are in the right place, I will help you. It looks like you flashed a corrupted recovery. What you need to is Odin flash CWM. Go here
http://forum.xda-developers.com/showthread.php?p=27290471
Download Odin and recovery.tar, and Odin flash it. Will boot up just fine after. Don't fear Odin. Its safe as long as you are careful and READ!!
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Ya Odin flash the recovery tar is probably the easiest way to go
Sent from my Galaxy Nexus using xda app-developers app
Odin is a tool used internally by Samsung. As such, you can't expect Samsung to write you a manual. Be very careful, you can cause a lot of damage with it. It is powerful, though: it can bring your phone back from the brink of death. Or it can take a healthy phone and send it over the edge. What you are doing now is something every rooter does on day 1, and only after days and days of research. I am uncomfortable with what you are going to do now given that you have never done this before, but you have no choice: it's this or a useless phone.
Here's the rundown:
A PIT file is something like the Master Boot Record of your harddisk. Problem is, the first partition is something like your computer's BIOS: it tells your phone how to bootstrap. It can bootstrap into the normal mode, which runs Android, or it can initiate Download mode. Download mode is what ODIN needs to replace parts or all of your phone's software. If something goes wrong with that bootloader, your phone is something called a hard brick: it won't power on, it won't even run Download mode so that you can recover it back to stock. It is dead. If that ever happens, you need something called a JTAG flash: you send your phone out somewhere, and someone takes it apart, hopefully carefully, plugs a programmer into an engineering port on your phone's logic board, and reprograms the bootloader back again). Now with PIT file having the major potential to trash things completely, you really have to pay attention you don't load the wrong one. Problem is, the ODIN you just downloaded DOES come with a PIT file, and that PIT file is WRONG for your device. Follow the instructions! Follow the instructions really really carefully. Don't check off extra things! Don't uncheck things that should be checked! Don't add PIT files! Make sure you load the right file to the right place in ODIN. Your phone depends on it.
ODIN will program your phone from scratch, but you wouldn't want to use it too often. It's a dangerous tool, as you can imagine, and it is meant to replace your phone's software, not maintain it! That's why we have Recovery. Recovery is what you use to do basic maintenance to Android, such as factory reset and clean cache and stuff. With those custom recoveries out there, you gain the added ability to flash custom ROMs and a few other things as well, which is what this forum is all about. So, step one in anyone seeking to root their phone is, flash a custom recovery using ODIN, since you need Download mode for that. In an ideal world, you will never need to use ODIN again after you flash your custom recovery. Well, in the real world, you should needed it only very infrequently.
Your phone first got its custom recovery from a tool designed to automate things for you, and sent you flashing without ever giving you an idea how your phone works. Now you don't know how to recover your phone from a flash gone wrong: in the long run that tool did not do any favours to you. The steps I gave you will bring your phone back to life, it brought mine several times already. Something about those new JB ROMs corrupts every recovery I have tried. I don't know why, I don't know how, but it does it. To make matters worse, ODIN without a proper PIT file cannot repartition your phone and fix whatever mess caused the problem to begin with, so restoring stock directly won't do the trick, you need to flash custom recovery, to fix recovery, and then Superwipe to recreate and realign your system, data and cache partitions: that's a good chunk of your phone. So, after you do this, you should be back in business. From beginning to end, if you know what you are doing, the entire process should not take more than 30 minutes, but don't rush. Take your time: take hours, take days. Take all the time you need.
Read before you do anything, and ask if you don't understand.
I have this issue every now and then when I use the stock recovery (the one i use to root) with ODIN, where it get stuck on everytime i try to wipe or flash, What I used to do is factory stock with Odin, then realize the even though it froze on wiping factory data, the rom wiped!! so what i do know is install rom manager and flash their recovery and problem solve,
this thread is very useful thanks guys.
by the way i dont flash JB roms yet until I they completely fix the call issues so. do you think its not only JB roms?
gypsy214 said:
I have this issue every now and then when I use the stock recovery (the one i use to root) with ODIN, where it get stuck on everytime i try to wipe or flash, What I used to do is factory stock with Odin, then realize the even though it froze on wiping factory data, the rom wiped!! so what i do know is install rom manager and flash their recovery and problem solve,
this thread is very useful thanks guys.
by the way i dont flash JB roms yet until I they completely fix the call issues so. do you think its not only JB roms?
Click to expand...
Click to collapse
I have had the problem you describe as well. Some ROMs like certain recoveries better than others and if you end up with the wrong combo, they don't boot. Flashing the right recovery after that fixes it instantly, without even a need to reflash the ROM. No, this is a different problem.
We are talking about a problem where flashing a ROM corrupts your recovery so it will stop working on you completely: it just hangs, it won't restore, it won't flash anything. Also, one or more of the ROM partitions on your phone get corrupted somehow so that even ODIN back to stock doesn't get your phone working again (you end up with a fully stock phone that doesn't boot). Maybe the two are related, but I will let those who know more speak. I am just a regular guy who fiddles with his phone a lot more than he should.
As for the problem being on JB only: I've only had it when flashing JB ROMs. I first noticed it with MIUI, but then AOKP started acting up, and when I finally dared to flash a CM10 unofficial nightly for the first time, it happened too... And then I noticed it doesn't happen always, only sometimes, and other times it just leaves me with a JB ROM that doesn't boot, and in some rare occasions: it works without a hitch. Go figure.
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
SectorNine50 said:
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
Click to expand...
Click to collapse
Is it possible that your hosts file needs modifying when installing the AT&T ROM? If the LG Support tool connects to LG's servers instead of your local http you set up, it will load the official ICS and completely wipe your phone to install that ROM... With my limited amount of knowledge, that's about all I could see if the process removes CWM Recovery.
Also, CWM 6.x is working fine for me, even manually flashed the touch recovery a few minutes ago, backed up my ROM and installed an updated ROM. No problems at all.
SectorNine50 said:
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
Click to expand...
Click to collapse
I don't know if anyone has tried the unbrick method with the new version of cwm but you might try twrp. When a similar version of cwm was in beta there were all sorts of issues. So maybe they haven't been fixed. Also are you installing cwm from GB? ICS has a locked boot loader so that might also be an issue.
http://forum.xda-developers.com/showthread.php?t=1888910
Now I would start with the unbricking guide for a 16th time but follow the directions to install twrp instead of cwm. You might also find you like it better. Good luck.
Sent from my LG-P930 using xda app-developers app
lordcheeto03 said:
Is it possible that your hosts file needs modifying when installing the AT&T ROM? If the LG Support tool connects to LG's servers instead of your local http you set up, it will load the official ICS and completely wipe your phone to install that ROM... With my limited amount of knowledge, that's about all I could see if the process removes CWM Recovery.
Also, CWM 6.x is working fine for me, even manually flashed the touch recovery a few minutes ago, backed up my ROM and installed an updated ROM. No problems at all.
Click to expand...
Click to collapse
I don't believe that the unbricking process would work if the hosts file was wrong, but I checked it again anyway, and it appears to be correct.
The AT&T ROM gets pushed via the abd shell after the unbrick and rooting process. The root appears to work, as the AT&T ROM that I push works fine, it's just not the ROM I want!
Swetnes said:
I don't know if anyone has tried the unbrick method with the new version of cwm but you might try twrp. When a similar version of cwm was in beta there were all sorts of issues. So maybe they haven't been fixed. Also are you installing cwm from GB? ICS has a locked boot loader so that might also be an issue.
http://forum.xda-developers.com/showthread.php?t=1888910
Now I would start with the unbricking guide for a 16th time but follow the directions to install twrp instead of cwm. You might also find you like it better. Good luck.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
After the unbricking process (after I get through all the nonsense on the Korean ROM), the phone is running the GB AT&T ROM, from there I push the CWM recovery.img to the phone using the abd shell. All seems to be working perfectly up until I go to flash the custom ROM! I don't get any errors when I flash the .zip either.
Initially I had installed CWM 6.x.x.x using the ROM Manager application. That's before all this nonsense started, and the phone was on the stock (but rooted) AT&T ICS ROM, so I know that's why I "bricked" my phone the first time.
I'll give TWRP a shot, hopefully that will work.
SectorNine50 said:
I don't believe that the unbricking process would work if the hosts file was wrong, but I checked it again anyway, and it appears to be correct.
The AT&T ROM gets pushed via the abd shell after the unbrick and rooting process. The root appears to work, as the AT&T ROM that I push works fine, it's just not the ROM I want!
After the unbricking process (after I get through all the nonsense on the Korean ROM), the phone is running the GB AT&T ROM, from there I push the CWM recovery.img to the phone using the abd shell. All seems to be working perfectly up until I go to flash the custom ROM! I don't get any errors when I flash the .zip either.
Initially I had installed CWM 6.x.x.x using the ROM Manager application. That's before all this nonsense started, and the phone was on the stock (but rooted) AT&T ICS ROM, so I know that's why I "bricked" my phone the first time.
I'll give TWRP a shot, hopefully that will work.
Click to expand...
Click to collapse
Ok so we know it's not the boot loader issue of ICS after dozens if not hundreds of successful installs using the unbricking guide the only thing left is the new version of cwm. Hopefully twrp will do the trick for you. Has anyone out there successfully completed the unbricking guide with the new version of cwm?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Ok so we know it's not the boot loader issue of ICS after dozens if not hundreds of successful installs using the unbricking guide the only thing left is the new version of cwm. Hopefully twrp will do the trick for you. Has anyone out there successfully completed the unbricking guide with the new version of cwm?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I haven't tried the TWRP recovery a shot yet, since I haven't been home, but I figured it was worth pointing out that the CWM 5.x.x.x (can't remember exact version numbers right now) didn't work for me either. Every time I flashed a ROM, I'd end up with a boot loop on first boot, and then when I'd try to go back into recovery, I'd find that it wouldn't go back in there either.
It was basically acting like when I flashed the ROM that it overwrote the recovery partition, except no one else seems to have this same issue. Yet, if I didn't flash a ROM, I was able to go in and out of CWM recovery as often as I wanted.
Bah.
SectorNine50 said:
I haven't tried the TWRP recovery a shot yet, since I haven't been home, but I figured it was worth pointing out that the CWM 5.x.x.x (can't remember exact version numbers right now) didn't work for me either. Every time I flashed a ROM, I'd end up with a boot loop on first boot, and then when I'd try to go back into recovery, I'd find that it wouldn't go back in there either.
It was basically acting like when I flashed the ROM that it overwrote the recovery partition, except no one else seems to have this same issue. Yet, if I didn't flash a ROM, I was able to go in and out of CWM recovery as often as I wanted.
Bah.
Click to expand...
Click to collapse
Can you clarify exactly what method you are using to flash the ROM? I just can't imagine a scenario where flashing a ROM would overwrite the recovery. What ROM are you flashing?
Also, please confirm what phone you have.
drumist said:
Can you clarify exactly what method you are using to flash the ROM? I just can't imagine a scenario where flashing a ROM would overwrite the recovery. What ROM are you flashing?
Also, please confirm what phone you have.
Click to expand...
Click to collapse
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
SectorNine50 said:
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
Click to expand...
Click to collapse
You are correct, the Nitro is P930. And I'm sure this doesn't need pointing out, but when you download the ROM, make sure it's for P93x and not SU640. Most of the ROMS in the developer section have versions for both models.
Also, when you say you can't access CWM after flashing a ROM, how are you trying to access it? Holding Power+Volume down until the Factory Reset screen pops up? It still shows that screen even with CWM installed, but when you press the power button to perform the factory reset it SHOULD take you into CWM Recovery instead.
SectorNine50 said:
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
Click to expand...
Click to collapse
To access recovery, turn the device completely off. (If you're in a bootloop, pull battery or hold power button for ~20 seconds until screen stays off.) Then when phone is off, press and hold volume down and power buttons at the same time, not releasing until you see text asking if you want to factory reset. Press power button twice to confirm and you'll get to recovery.
Is this the method you're using to try to get to CWM?
My guess as to why you are getting bootloops is that you aren't wiping data first.
Yup, that's how I'm accessing CWM. After the flash, after I press the power button twice, I get something similar to a boot loop. A recovery boot loop, if you will.
Well, I've tried a couple ways now. I've tried using the "factory reset/wipe user data" menu item in CWM, and I've tried going into each partition and wiping them individually before flashing as well.
Just got home, I'll try flashing using the TWRP and let you guys know.
SectorNine50 said:
Yup, that's how I'm accessing CWM. After the flash, after I press the power button twice, I get something similar to a boot loop. A recovery boot loop, if you will.
Well, I've tried a couple ways now. I've tried using the "factory reset/wipe user data" menu item in CWM, and I've tried going into each partition and wiping them individually before flashing as well.
Just got home, I'll try flashing using the TWRP and let you guys know.
Click to expand...
Click to collapse
Good luck. Other possible things to try:
1) Check zip MD5 hash (or just redownload and replace) to make sure it's not corrupted.
2) Reformat entire SD card.
Interesting update:
I decided to give getting back into CWM recovery one more shot before I went through the process of re-unbricking again, and this time it managed to get in (for whatever reason).
So, I did a factory wipe, cleared dalvik cache, flashed the ParanoidAndroid ROM, backed out, did another factory wipe, and tried to reboot into the newly flashed ROM.
No luck. Boot looped, and didn't even get to the ROM animation. Following that, I had trouble getting back into the CWM recovery. Managed to try about 5 times and finally got in, however CWM stated:
Code:
CWM-based Recovery v5.0.2.7
E:Error in /cache/recovery/last_log
(Read-only file system)
So... my phone may have potentially unrooted it's self, somehow... Interestingly, it still shows the file systems as mounted.
So, now I'm doing a full SD card reformat. Figured I'd get that variable out of the way before I go any further.
SectorNine50 said:
Interesting update:
I decided to give getting back into CWM recovery one more shot before I went through the process of re-unbricking again, and this time it managed to get in (for whatever reason).
So, I did a factory wipe, cleared dalvik cache, flashed the ParanoidAndroid ROM, backed out, did another factory wipe, and tried to reboot into the newly flashed ROM.
No luck. Boot looped, and didn't even get to the ROM animation. Following that, I had trouble getting back into the CWM recovery. Managed to try about 5 times and finally got in, however CWM stated:
Code:
CWM-based Recovery v5.0.2.7
E:Error in /cache/recovery/last_log
(Read-only file system)
So... my phone may have potentially unrooted it's self, somehow... Interestingly, it still shows the file systems as mounted.
So, now I'm doing a full SD card reformat. Figured I'd get that variable out of the way before I go any further.
Click to expand...
Click to collapse
You are installing the wrong version of CWM. Never use anything older than 5.8.2.0. This is the one you want: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-p930.img
Anything older than that is known to not work.
Second thing: You seem to have an incorrect understanding of what "root" means. Having "root" simply means you have administrator access to your current ROM. When you install a new ROM, whether you had root access to your old ROM is meaningless frankly.
drumist said:
You are installing the wrong version of CWM. Never use anything older than 5.8.2.0. This is the one you want: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-p930.img
Anything older than that is known to not work.
Second thing: You seem to have an incorrect understanding of what "root" means. Having "root" simply means you have administrator access to your current ROM. When you install a new ROM, whether you had root access to your old ROM is meaningless frankly.
Click to expand...
Click to collapse
Ah, thank you! I must've been viewing an old thread. Now that I look at the version number, it appears that's the version I had been hunting for since the newest one didn't work.
Interesting, I most certainly misunderstood, I was under the impression that "rooting" the device was a filesystem level permission change. Good to know!
It seems like we are getting closer to a solution here. Thanks for your patience!
Well, that appears to have been my problem the whole time! That's kind of embarrassing, considering how much time I sunk into this and how simple the solution was!
Anyway, thank you all very much! I assume that TWRP would have also solved my problems as well. It would seem that both the older and newest versions of CWM have some problems (at least for me!).
SectorNine50 said:
Well, that appears to have been my problem the whole time! That's kind of embarrassing, considering how much time I sunk into this and how simple the solution was!
Anyway, thank you all very much! I assume that TWRP would have also solved my problems as well. It would seem that both the older and newest versions of CWM have some problems (at least for me!).
Click to expand...
Click to collapse
Yeah, the new one (6.0.1.5) just came out. I'll have to test it to see if it works for me.
For what it's worth, I haven't had any issues with 6.0.1.5 yet. The touch version is a must, though.
Malnilion said:
For what it's worth, I haven't had any issues with 6.0.1.5 yet. The touch version is a must, though.
Click to expand...
Click to collapse
Have you had a chance to compare to twrp?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Have you had a chance to compare to twrp?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I really enjoy the integration Rom Manager/CM Updater has with CWM. If twrp is capable of running the install scripts those two use, I might consider trying it out, but I don't really like manually going through the steps to flash a rom every day.
Hi all, hope you are doing well (I also hope that you can help me ).
I just recently got a replacement phone because my other one had a faulty speaker (crackling, etc.). The other one was rooted (via CF-AutoRoot) and had TWRP on it, and I made a complete nandroid backup of it onto my MicroSD card.
I rooted the new phone using CF-AutoRoot via Odin and installed TWRP on it as well (also via Odin). Then I swapped the SD card and SIM card and restored the complete backup to the new phone.
It took a while, but the phone booted up and I had two working clones, the only way to tell which was which was by changing the volume and hearing the crackling on the old one.
So the new phone worked all day (was able to make calls and everything, and the GUI that was customized with Wanam Xposed even looked good), however when I restarted it to put in my backup battery, I didn't have root for some reason. I tried and tried to get it back (reinstalled SuperSU, tried the TWRP method) to no avail.
I re-flashed CF-AutoRoot just to see, and the phone booted up but and for some reason SuperSU was gone (and I didn't have root). When I restarted, I got a boot loop and could not even get back into a recovery.
I got tired of this and wanted a fresh start, so I just flashed the stock ROM via ODIN and did a factory reset. However now if I try to boot, the Samsung logo will flash and just shut down, and I won't be able to get into the recovery no matter what. If I flash a recovery (CWM, TWRP or even stock), the recovery will work until I try to actually try to boot the phone. I've tried taking the battery out for a good 5 minutes and retrying (also tried swapping batteries), I've tried doing complete resets galore from all three recoveries mentioned with no success. Obviously Download mode still works so I know it's not completely bricked, but I am getting a little scared.
Any and all help is extremely appreciated as I would prefer not to have such an expensive paper-weight.
Thanks a bunch!
I would suggest going all the way back stock on stock firmware via Odin. Then re-root, TWRP, and re-download the rom of your choice. Dont restore the backup. Just start fresh.
I Think My S4 Is Insane
SICK MADE DEVELOPMENT
alloycowboy said:
I would suggest going all the way back stock on stock firmware via Odin
Click to expand...
Click to collapse
Thanks for the reply.
And okay, I tried that.
I flashed stock using the T-Mobile ROM I found here: galaxys4root_(dot)_com/galaxy-s4-stock-firmware/
This is the same ROM file I used to completely restore the phone I had to return, and that worked fine.
But it still won't boot up or go into recovery mode (just shows the Samsung logo for a split second before shutting down).
One thing I did do on the other phone was flash a kernel which had set-MUID to off so I could WiFi tether, but I thought flashing the stock ROM would revert that back as well. Do you think that's the reason it messed up so badly? I restored the backup from the other phone with a different kernel? Right after I restored the backup to the new phone and everything was working, I remember checking the kernel info in the About Phone section of the settings, and it was in fact the kernel I'd installed on the other phone.
TLDR: Tried flashing stock ROM to no avail. Download mode still works but can't enter recovery mode or boot.
Are you doing a factory reset after flashing stock firmware?
I Think My S4 Is Insane
SICK MADE DEVELOPMENT
I'd flash a stock rooted ROM. Get that root and recovery back. The konane tar file from the stickies, perhaps.
Sent from my SGH-M919 using xda app-developers app
alloycowboy said:
Are you doing a factory reset after flashing stock firmware?
Click to expand...
Click to collapse
Yeah, as soon as it finished installing I went into stock recovery and did a factory reset.
Karakoram2 said:
I'd flash a stock rooted ROM. Get that root and recovery back. The konane tar file from the stickies, perhaps.
Click to expand...
Click to collapse
Alright, I'll try that.
Is the konane tar an actual ROM? And what do you mean in the stickies?
Sorry, not very familiar with XDA forums.
Samsung GT-I9500 flashes n switches off!
BallisticallySimilar said:
Hi all, hope you are doing well (I also hope that you can help me ).
I just recently got a replacement phone because my other one had a faulty speaker (crackling, etc.). The other one was rooted (via CF-AutoRoot) and had TWRP on it, and I made a complete nandroid backup of it onto my MicroSD card.
I rooted the new phone using CF-AutoRoot via Odin and installed TWRP on it as well (also via Odin). Then I swapped the SD card and SIM card and restored the complete backup to the new phone.
It took a while, but the phone booted up and I had two working clones, the only way to tell which was which was by changing the volume and hearing the crackling on the old one.
So the new phone worked all day (was able to make calls and everything, and the GUI that was customized with Wanam Xposed even looked good), however when I restarted it to put in my backup battery, I didn't have root for some reason. I tried and tried to get it back (reinstalled SuperSU, tried the TWRP method) to no avail.
I re-flashed CF-AutoRoot just to see, and the phone booted up but and for some reason SuperSU was gone (and I didn't have root). When I restarted, I got a boot loop and could not even get back into a recovery.
I got tired of this and wanted a fresh start, so I just flashed the stock ROM via ODIN and did a factory reset. However now if I try to boot, the Samsung logo will flash and just shut down, and I won't be able to get into the recovery no matter what. If I flash a recovery (CWM, TWRP or even stock), the recovery will work until I try to actually try to boot the phone. I've tried taking the battery out for a good 5 minutes and retrying (also tried swapping batteries), I've tried doing complete resets galore from all three recoveries mentioned with no success. Obviously Download mode still works so I know it's not completely bricked, but I am getting a little scared.
Any and all help is extremely appreciated as I would prefer not to have such an expensive paper-weight.
Thanks a bunch!
Click to expand...
Click to collapse
The same thing has happened to me! Did you find any solustion for this?? Please help!! This was my first attempt and i have no idea wats going on!
Here are the stickies for our forum: http://forum.xda-developers.com/showthread.php?t=2419828
Sent from my SGH-M919 using XDA Premium 4 mobile app
What I did to unbrick my T-Mobile S4 (SGH-M919)
killerwolf2121 said:
The same thing has happened to me!
Did you find any solutions for this? Please help if you can; this was my first attempt and I have to idea what's going on.
Click to expand...
Click to collapse
Well, for the first problem, flashing the stock ROM did it for me. I followed this tutorial.
For the second issue of not booting up after displaying the Samsung logo; my battery just simply was too dead and didn't have enough juice to start. You have no idea how stupid I felt.
Let your phone charge from the wall cable for a good while before trying all this again; then see if that works. It did it for me. If it doesn't, I'm not sure what else to try.
After that (if it works), if you still want root, just flash CF-Auto-Root and then a custom recovery if you want (like ClockworkMod Recovery (click the little version link, not the "Download ROMs" button) or TWRP via GooManager) (I use TWRP)
All the best and let me know how it went!
Keep in mind that I did this on an SGH-M919 (T-Mobile S4) running Android 4.2.2, so if you don't have that, I have no idea if any of the above will work for you. Also I'm pretty sure if you do have 4.3, you will ruin your warranty forever due to the Knox restriction they added (if you haven't already).
Android_Monsters said:
Here are the stickies for our forum: http://forum.xda-developers.com/showthread.php?t=2419828
Click to expand...
Click to collapse
Thanks
BallisticallySimilar said:
Well, for the first problem, flashing the stock ROM did it for me. I followed this tutorial.
For the second issue of not booting up after displaying the Samsung logo; my battery just simply was too dead and didn't have enough juice to start. You have no idea how stupid I felt.
Let your phone charge from the wall cable for a good while before trying all this again; then see if that works. It did it for me. If it doesn't, I'm not sure what else to try.
After that (if it works), if you still want root, just flash CF-Auto-Root and then a custom recovery if you want (like ClockworkMod Recovery (click the little version link, not the "Download ROMs" button) or TWRP via GooManager) (I use TWRP)
All the best and let me know how it went!
Keep in mind that I did this on an SGH-M919 (T-Mobile S4) running Android 4.2.2, so if you don't have that, I have no idea if any of the above will work for you. Also I'm pretty sure if you do have 4.3, you will ruin your warranty forever due to the Knox restriction they added (if you haven't already).
Thanks
Click to expand...
Click to collapse
I am on 4.3 and yes, flashing the stock rom worked for me too! relief thanks a ton!
Having trouble unbricking M919 T-Mobile
Hi, I'm trying to unbrick my M919 through Odin. I have all the updated software, but I keep getting a fail message. Any help would be appreciated.
I hope I am posting this in the correct forum.
I am running the Note 4 with a stock rooted Lollipop rom, with a TWRP recovery. Starting yesterday, I have had problems charging the phone. Most of my cables will suddenly not charge the phone at all, or perhaps charge the phone for a couple of minutes and stop. I have found that if I turn the phone off and plug in the charger that came with the phone (the fast charger), it will charge very slowly, but steadily.
I did some reading on this and what could cause it. Since it happened with all my cables suddenly, when they were working fine the day before, I have to assume the issue is the phone itself, not my cables. It could be (and I am hoping it is) some dust in the USB port, so I am going to pick up some dust off and try to clean it that way. But if it's a hardware problem that needs to be addressed, I am a little hesitant to bring the phone into the Sprint store
where I got it because I have tripped the KNOX meter and assume I could have some issues with that. At the very least I assume I will have to return to the stock recovery if I don't want call attention to the issue at Sprint. Anyway, I would be interested in hearing from anyone else who may have had these issues on any suggestions they would have for my on my next moves.
Addendum:
Just realized I should mention that my carrier is Sprint and I am paying for insurance every month as part of my bill. I don't know if that makes any difference as to whether the rooting and Knox would be an issue or not.
=========================
Thanks.
Back in December the consensus was that Sprint didn't care at all about root or Knox trip. And Samsung had a one-time pardon on Knox trip regarding warranty repair.
Recently, a few have posted contrary to this belief. With Sprint warranty, I do believe it is OK to bring it in stock with Knox trip; just don't mention root or trip. Take it somewhere else if they refuse to help you.
That said, have you tried backing up your app data, removing sdcard and wiping everything several times, power down and Odin stock tar and checking charge feature? Worth a try. I'd even suggest trying the NIE stock tar if another tar fails.
Just do the wipes in TWRP and power down prior to Odin in download mode.
samep said:
Back in December the consensus was that Sprint didn't care at all about root or Knox trip. And Samsung had a one-time pardon on Knox trip regarding warranty repair.
Recently, a few have posted contrary to this belief. With Sprint warranty, I do believe it is OK to bring it in stock with Knox trip; just don't mention root or trip. Take it somewhere else if they refuse to help you.
That said, have you tried backing up your app data, removing sdcard and wiping everything several times, power down and Odin stock tar and checking charge feature? Worth a try. I'd even suggest trying the NIE stock tar if another tar fails.
Just do the wipes in TWRP and power down prior to Odin in download mode.
Click to expand...
Click to collapse
Thanks very much for this; very useful. I was going to try what you suggested, the problem I am having now implementing it is that whatever issue is happening with the USB port also seems to be keeping my desktop computer from recognizing the phone is plugged in. I tried going into download mode, connecting the phone to the computer with the original cable, and running Odin, and it does not appear. I can imagine this is going to cause me problems if I want to revert to stock recovery before I bring the phone in, as I assume I cannot use TWRP to replace itself with stock recovery, correct?
Yesterday the phone did charge for a while, all the way up to 60%, right after I wiped dalvik and cache. I was also able to charge it for a while when it was turned off. So I am still trying to sort this out. One additional thing: though I was able to charge for a while when it was turned off, I notice now that if I turn the phone off and plug in the charger, the phone does not show a charging image, but it does throb continuously while it is plugged in. Very odd.
You want stock recovery? Since Odin didn't work, you can try Flashify. Extract files from the BOB7 stock tar using PC, transfer via USB to storage and install the recovery.img using Flashify app from Google Play.
Can you use USB to transfer files?
Edit: you can get the stock kernel the same way but if you flashed a custom kernel, not recommended because the modules get modified. You'd need a system image for that. I don't know if Flashify is up that task out not.
Did you try Samsung KIES? You may run into the same USB issues but worth a try if you haven't.
samep said:
You want stock recovery? Since Odin didn't work, you can try Flashify. Extract files from the BOB7 stock tar using PC, transfer via USB to storage and install the recovery.img using Flashify app from Google Play.
Click to expand...
Click to collapse
So I would just pull the recovery.img file?
samep said:
Can you use USB to transfer files?
Click to expand...
Click to collapse
I'll try, but I'm guessing not, but I can always pull the SD card.
samep said:
Edit: you can get the stock kernel the same way but if you flashed a custom kernel, not recommended because the modules get modified. You'd need a system image for that. I don't know if Flashify is up that task out not.
Click to expand...
Click to collapse
I am using the Lollipop rom I got as an update from Samsung. Only thing I did was CF-Root it, and Flashify TWRP and install a few apps like Titanium Backup and the like. And however the standard method is to install Superuser, can't remember if I installed it via Flashify, Odin, or just sideloaded it as an app at this point. But I was not as flash-crazy with this phone as I have been with some in the past. So I would assume I have a stock kernel still.
samep said:
Did you try Samsung KIES? You may run into the same USB issues but worth a try if you haven't.
Click to expand...
Click to collapse
I could use that to restore to stock? I will look into it.
Right now I have to deal with the issue that my battery is almost totally out because of my inability to charge via USB. I decided to deal with that by picking up the Battery charging station and backup battery from Best Buy on the way home (a useful thing to have anyway), but I am still planning on bringing this phone into Sprint and getting it fixed if I can. I've only had it for since the fall and I am paying a service contract.
Thanks again for your help
Yes, extract the file from stock tar to get the recovery and use Flashify to install the image.
Have you tried a factory reset? Do you have a lollipop nandroid to restore? I may have asked that already? If it's on the external sdcard, factory reset a few times and wipe internal storage and system a few times before restoring nandroid.
You can unroot within the SuperSU application if you take it back to Sprint.
Best wishes for a fix it replacement.
samep said:
Yes, extract the file from stock tar to get the recovery and use Flashify to install the image.
Click to expand...
Click to collapse
Okay,great, will do that.
samep said:
Have you tried a factory reset?
Click to expand...
Click to collapse
Do you mean in TWRP? Or in Backup and reset under settings? Not yet, but I can do it later.
samep said:
Do you have a lollipop nandroid to restore? I may have asked that already? If it's on the external sdcard, factory reset a few times and wipe internal storage and system a few times before restoring nandroid.
Click to expand...
Click to collapse
I did not do a nandroid backup right after I installed TWRP if that's what you mean. I just did one but that would be useless to restore Iwould think.
samep said:
You can unroot within the SuperSU application if you take it back to Sprint.
Click to expand...
Click to collapse
Oh, great, I see that option. So that I would do after I've flashified the stock recovery, right?
samep said:
Best wishes for a fix it replacement.
Click to expand...
Click to collapse
Just want to make sure I have the right order for this stuff.
If I factory reset, will I still be able to run flashify on the recovery and superuser to unroot?
Or do I do the factory reset afterwards?
Once again, thanks very much for your help, I really appreciate it.
maltydog said:
Okay,great, will do that.
Do you mean in TWRP? Or in Backup and reset under settings? Not yet, but I can do it later.
Click to expand...
Click to collapse
Factory reset should be a priority and it shouldn't unroot you. I don't think there's any difference between settings or TWRP factory reset.
maltydog said:
I did not do a nandroid backup right after I installed TWRP if that's what you mean. I just did one but that would be useless to restore Iwould think.
Click to expand...
Click to collapse
right
maltydog said:
Oh, great, I see that option. So that I would do after I've flashified the stock recovery, right?
Click to expand...
Click to collapse
Correct; Flashify needs root access.
maltydog said:
Just want to make sure I have the right order for this stuff.
If I factory reset, will I still be able to run flashify on the recovery and superuser to unroot?
Or do I do the factory reset afterwards?
Once again, thanks very much for your help, I really appreciate it.
Click to expand...
Click to collapse
Yes. Personally I'd do this first. You could use titanium backup to backup apps because factory reset wipes the user apps and data. It's possible that your USB/charging problems are in this partition. Equally possible that it's in root partition or another partition which is where the nandroid or stock tar would be helpful since USB is dysfunctional.
samep said:
Factory reset should be a priority and it shouldn't unroot you. I don't think there's any difference between settings or TWRP factory reset.
right
Correct; Flashify needs root access.
Yes. Personally I'd do this first. You could use titanium backup to backup apps because factory reset wipes the user apps and data. It's possible that your USB/charging problems are in this partition. Equally possible that it's in root partition or another partition which is where the nandroid or stock tar would be helpful since USB is dysfunctional.
Click to expand...
Click to collapse
Okay, right, thanks again. I will run another Titanium Backup before I do all this. Then I will flashify the recovery, then unroot with superuser, then do the factory reset in the settings (since I will not have TWRP anymore). I think that's the correct order. Then I can see after this if there is any change in the USB connection, and if not return to the Sprint store and keep my fingers crossed!
maltydog said:
Okay, right, thanks again. I will run another Titanium Backup before I do all this. Then I will flashify the recovery, then unroot with superuser, then do the factory reset in the settings (since I will not have TWRP anymore). I think that's the correct order. Then I can see after this if there is any change in the USB connection, and if not return to the Sprint store and keep my fingers crossed!
Click to expand...
Click to collapse
An additional question. I have downloaded the BOB7V3Final.zip file. I extracted it,
but I do not see a file named recovery.img. The only files named recovery are install-recovery.sh files,
several of them, and recovery-from-boot.p, and recovery.resource.dat EDIT: I believe that was the wrong file.
I am downloading a stock firmware from another site, and it does contain the recovery.img file.
Did This Work
Hopefully, someone will see this. I am having damn near the same exact issue, my phone has not been charging since a couple days after root. Unfortunately, I do not have a back-up of the stock OS. Seeking help to avoid being phoneless.
Sorry to beat a dead horse, I come from the nexus forums and haven't used a samsung device in a while. My friend has the Note 4 with MM on it. Is flashing TWRP as simple as just flashing it via odin with his phone as is? Does he need to complete any process first, before being able to flash TWRP via odin?
Thanks all!
Sprint Note 4 already updated to PD1? If latest update is desired, update it first.
FYI: An ounce of prevention is worth a pound of cure!
The bootloader is already unlocked but the reactivation lock may have been locked by user. Goto to Settings/Security/Reactivation lock and disable it. You can also verify this while in download mode, the phone's display show reactivation lock disabled before your proceed.
Enable developer options by tapping build number in About device in Settings 7 times. Go into developer tab and enable USB debugging.
Using latest Odin and latest TWRP is recommended. You should only flash only the specified custom recovery for your device or the touch screen will not be accurate.
TWRP can be found in the original development thread.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Use AP slot and make sure the Samsung driver is installed; get that from Samsung support for Note 4. Make sure KIES and SmartSwitch is closed or uninstalled (may not work on rooted phone; manually backup files you wish to keep just in case). Run Odin as administrator; not required for Windows 10.
To flash, press the Odin exe, uncheck the auto reboot option, load the file using the AP slot, power down phone, hold the keys [volume down, menu and power] together until booted in download initial screen, connect the USB, volume up, verify your COM is connected and start. When you see the success, 0 failed, disconnect USB and pull battery, wait at least 30 seconds and replace battery and boot directly into recovery to ensure it sticks. Otherwise, you're back on stock recovery.
If swapping device owner, it's recommended to remove the Google account before factory resetting the device. Consider it as a good practice for all Settings menu selected factory resets. If you trip the factory reset protection circuit, you need to sign in with original Google account & password.
You can use Odin to downgrade to Android Lollipop 5.1 (most recent OK1 build recommended if going back to Lollipop) but you cannot use Odin to downgrade to Android 5.0 Lollipop or KitKat. The bootloader prevents lower security bootloaders from being installed.
Custom ROMs may remove ItsOn but may not remove it from root folder. Unless /carrier/ItsOn folder is deleted, you may suffer continual reboots if factory resetting device at some point. After following and verifying all the above, you may consider factory resetting, including wiping data, internal memory and Android folder in extSdCard to make a clean break with normal un-rooted conditions and Lollipop fragments on phone to prevent random reboots.
Sent from my SM-N910P using Tapatalk
samep said:
Sprint Note 4 already updated to PD1? If latest update is desired, update it first.
FYI: An ounce of prevention is worth a pound of cure!
The bootloader is already unlocked but the reactivation lock may have been locked by user. Goto to Settings/Security/Reactivation lock and disable it. You can also verify this while in download mode, the phone's display show reactivation lock disabled before your proceed.
Enable developer options by tapping build number in About device in Settings 7 times. Go into developer tab and enable USB debugging.
Using latest Odin and latest TWRP is recommended. You should only flash only the specified custom recovery for your device or the touch screen will not be accurate.
TWRP can be found in the original development thread.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Use AP slot and make sure the Samsung driver is installed; get that from Samsung support for Note 4. Make sure KIES and SmartSwitch is closed or uninstalled (may not work on rooted phone; manually backup files you wish to keep just in case). Run Odin as administrator; not required for Windows 10.
To flash, press the Odin exe, uncheck the auto reboot option, load the file using the AP slot, power down phone, hold the keys [volume down, menu and power] together until booted in download initial screen, connect the USB, volume up, verify your COM is connected and start. When you see the success, 0 failed, disconnect USB and pull battery, wait at least 30 seconds and replace battery and boot directly into recovery to ensure it sticks. Otherwise, you're back on stock recovery.
If swapping device owner, it's recommended to remove the Google account before factory resetting the device. Consider it as a good practice for all Settings menu selected factory resets. If you trip the factory reset protection circuit, you need to sign in with original Google account & password.
You can use Odin to downgrade to Android Lollipop 5.1 (most recent OK1 build recommended if going back to Lollipop) but you cannot use Odin to downgrade to Android 5.0 Lollipop or KitKat. The bootloader prevents lower security bootloaders from being installed.
Custom ROMs may remove ItsOn but may not remove it from root folder. Unless /carrier/ItsOn folder is deleted, you may suffer continual reboots if factory resetting device at some point. After following and verifying all the above, you may consider factory resetting, including wiping data, internal memory and Android folder in extSdCard to make a clean break with normal un-rooted conditions and Lollipop fragments on phone to prevent random reboots.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks bud. This was really great!
hate to be a stickler, but im a frickin nub.... after doing this how do i get root access?? pls help im new i just paid 10$ FOR A NOTE 4 , mint condition hahah but for real someone help..
CorporalCactus said:
hate to be a stickler, but im a frickin nub.... after doing this how do i get root access?? pls help im new i just paid 10$ FOR A NOTE 4 , mint condition hahah but for real someone help..
Click to expand...
Click to collapse
To get root after getting on desired update, whether it be current update, downgrading (be careful with downgrading; most likely you're only able to downgrade as low as Android 5.1 but that depends on your current bootloader) or upgrading, you flash TWRP and then you would do one of two things:
1) flash a pre-rooted ROM. Custom ROMs in our forum do this.
2) flash custom kernel and complete root with SuperSU zip. Both are flashed in recovery but both should be flashed before booting. Kernel first, then flash SuperSU zip and boot. You would also need to manually remove ItsOn and Knox.
Given the complexity of it, I'd suggest the custom stock ROM for you. The ROM should match your bootloader. I'd recommend stock, aka touchwiz ROMs. They're mostly stock and have less bugs and workarounds than others like CM.
We still don't have highly customized Marshmallow stockish ROMs but I don't think it will be long before we see them. By the time they're here, maybe you're ready.
Read the OP of the custom ROM. If you don't understand or need clarification, this thread is a good place to ask the question. Install this app to check your bootloader (baseband is relevant too):
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Hint: make sure you're on the the recommended bootloader and baseband first. If you have trouble with TWRP flash sticking, you may not be unchecking auto reboot and pulling battery after successful flash and booting directly into recovery to make it stick properly. You have to wait at least 30 seconds after battery pull and boot directly into recovery.
Sent from my SM-N910P using Tapatalk
samep said:
To get root after getting on desired update, whether it be current update, downgrading (be careful with downgrading; most likely you're only able to downgrade as low as Android 5.1 but that depends on your current bootloader) or upgrading, you flash TWRP and then you would do one of two things:
1) flash a pre-rooted ROM. Custom ROMs in our forum do this.
2) flash custom kernel and complete root with SuperSU zip. Both are flashed in recovery but both should be flashed before booting. Kernel first, then flash SuperSU zip and boot. You would also need to manually remove ItsOn and Knox.
Given the complexity of it, I'd suggest the custom stock ROM for you. The ROM should match your bootloader. I'd recommend stock, aka touchwiz ROMs. They're mostly stock and have less bugs and workarounds than others like CM.
We still don't have highly customized Marshmallow stockish ROMs but I don't think it will be long before we see them. By the time they're here, maybe you're ready.
Read the OP of the custom ROM. If you don't understand or need clarification, this thread is a good place to ask the question. Install this app to check your bootloader (baseband is relevant too):
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Hint: make sure you're on the the recommended bootloader and baseband first. If you have trouble with TWRP flash sticking, you may not be unchecking auto reboot and pulling battery after successful flash and booting directly into recovery to make it stick properly. You have to wait at least 30 seconds after battery pull and boot directly into recovery.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
damn thanks for this info! youre the man! you know ur stuff thats awesome. im confused regarding the kernel.. i just winged it tbh, i installed TWRP via odin. got it to stick, then flashed SUPERSU and got root. I made a full backup via twrp then i flashed a custom CM rom and it works awesome. i didnt do anything regarding kernels. My question now is, what is the easiest way to swap between roms?? Such as stock Rom to this New CM rom i have. Would i just create backups and restore when i want to switch??
CorporalCactus said:
damn thanks for this info! youre the man! you know ur stuff thats awesome. im confused regarding the kernel.. i just winged it tbh, i installed TWRP via odin. got it to stick, then flashed SUPERSU and got root. I made a full backup via twrp then i flashed a custom CM rom and it works awesome. i didnt do anything regarding kernels. My question now is, what is the easiest way to swap between roms?? Such as stock Rom to this New CM rom i have. Would i just create backups and restore when i want to switch??
Click to expand...
Click to collapse
You could make backups and factory reset before restoring. If you have issues restoring stock backups, wipe internal memory also.
You have to take care to read and adhere to changing trends with CM; they may not be compatible with Marshmallow baseband and bootloader yet but may even require a different kernel to run with Marshmallow bootloader and baseband. I'm not current on the latest and lack experience. Search the specific ROM threads for CM known issues, workarounds and trends.
As far as the kernel question, I did omit the fact you could flash SuperSU to patch the stock kernel; you didn't do any wrong there. I've abandoned use of stock kernel since Android 5.1 required an exploit to root. We didn't always have the boot image patch that SuperSU now includes. For some reason, users are randomly losing root with systemless root. If that happens, just flash SuperSU again; same version or higher should be OK.
Sent from my SM-N910P using Tapatalk
samep said:
You could make backups and factory reset before restoring. If you have issues restoring stock backups, wipe internal memory also.
You have to take care to read and adhere to changing trends with CM; they may not be compatible with Marshmallow baseband and bootloader yet but may even require a different kernel to run with Marshmallow bootloader and baseband. I'm not current on the latest and lack experience. Search the specific ROM threads for CM known issues, workarounds and trends.
As far as the kernel question, I did omit the fact you could flash SuperSU to patch the stock kernel; you didn't do any wrong there. I've abandoned use of stock kernel since Android 5.1 required an exploit to root. We didn't always have the boot image patch that SuperSU now includes. For some reason, users are randomly losing root with systemless root. If that happens, just flash SuperSU again; same version or higher should be OK.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
ugh i messed something up and cant find the restore files for the note 4. after flashing that CM rom, a lot of stuff didnt work so i restored a backup i just made. it bootlooped, i did it again and the phone came on, BUT i cannot place or delete and media from the device using a PC.. not sure why its say the device has either stopped responding or has been disconnected
CorporalCactus said:
ugh i messed something up and cant find the restore files for the note 4. after flashing that CM rom, a lot of stuff didnt work so i restored a backup i just made. it bootlooped, i did it again and the phone came on, BUT i cannot place or delete and media from the device using a PC.. not sure why its say the device has either stopped responding or has been disconnected
Click to expand...
Click to collapse
Did you factory reset and wipe internal memory when restoring the backup?
Put your micro sdcard in a card reader and transfer it. If you're trying to transfer while in recovery, that currently doesn't work.
If you're trying to copy your TWRP backup to micro sdcard, the path should be: TWRP/BACKUPS/(your device s/n recognized by TWRP)/(TWRP Backup folder)
Without proper path, TWRP may not see the backup as official. When saving TWRP backups, the TWRP folder as a whole with desired backups should be saved.
If you can't restore the backup, you can flash a ROM that matches bootloader. Like I said before, factory reset and wipe internal memory and flash the ROM.
Sent from my SM-N910P using Tapatalk
CorporalCactus said:
ugh i messed something up and cant find the restore files for the note 4. after flashing that CM rom, a lot of stuff didnt work so i restored a backup i just made. it bootlooped, i did it again and the phone came on, BUT i cannot place or delete and media from the device using a PC.. not sure why its say the device has either stopped responding or has been disconnected
Click to expand...
Click to collapse
At this point I would just recommend flashing a new ROM man.
Sent from my SM-N910P using Tapatalk