My phone was rooted and I did a factory reset to send it to have the screen repaired. I lost root and I get the message "com.android.phone not responding" all the time if I restart the phone but it works fine. Someone told me to use Odin to wipe the phone and get rid of that message. After I do that, what tool should I use to root on 4.2.2?
Need MORE info. What was the Original firmware/ what firmware do you have right now? You said 4.2.2 but which one? MDB? MDL? or MF3?
MDB and MDL you can do a lot note with and use motochopper + Loki bootloader bypass. MF3 patched the exploit and can only use safestrap recovery.
Read some of the threads once you find which firmware you have and/or on right now. If your stock, then beware it will AUTO UPDATE you without your consent. So find out what you have and need to do quickly.
RockRatt said:
Need MORE info. What was the Original firmware/ what firmware do you have right now? You said 4.2.2 but which one? MDB? MDL? or MF3?
MDB and MDL you can do a lot note with and use motochopper + Loki bootloader bypass. MF3 patched the exploit and can only use safestrap recovery.
Read some of the threads once you find which firmware you have and/or on right now. If your stock, then beware it will AUTO UPDATE you without your consent. So find out what you have and need to do quickly.
Click to expand...
Click to collapse
Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looks like it's MDL?. So I guess motochopper then. Mine cannot auto update fortunately. It fails every time. I've had it like that for a while but now I really want to root it again. I think it's because of that error I get on start-up that the update fails.
SRCP said:
Thanks.
Looks like it's MDL?. So I guess motochopper then. Mine cannot auto update fortunately. It fails every time. I've had it like that for a while but now I really want to root it again. I think it's because of that error I get on start-up that the update fails.
Click to expand...
Click to collapse
I had a similar situation, and the AT&T updates would fail at ~28%, even though I never approved the updates (my guess is that after I've said no more than 3 time, they did it anyways?). At that point I was stuck, and to make things worse, the WiFi was working only in my house, but no data over the ATT network, just voice. Even reflashing with ODIN didn't resolved the problem.
Had to bite the bullet and get the phone replaced by the warranty. I hope this doesn't happen to anyone else,
SRCP said:
Thanks.
Looks like it's MDL?. So I guess motochopper then. Mine cannot auto update fortunately. It fails every time. I've had it like that for a while but now I really want to root it again. I think it's because of that error I get on start-up that the update fails.
Click to expand...
Click to collapse
Since it is MDL firmware just use Motochopper + Loki and you will have a custom recovery (TWRP or CWM YOUR CHOICE). Then flash ANY custom ROM on your phone. You can have the best of BOTH worlds. You can flash a updated firmware ROM like ShoStock for the Touchwiz based Roms or a AOSP based ROMs. NO need to update firmware from ATT. In fact you lose what you can do with your phone if you do.
If you REALLY want to update to ATT newest firmware you can download the STOCK MDL firmware from samfirmware. Flash it which will make your phone PURE STOCK firmware and recovery. Then you will be able to update from ATT. The reason it fails is because you are rooted and probably custom recovery already?
Thanks. Well, I had it rooted but it seems like I lost root when I did something, I don't remember but I think it's when I factory reset it to send it to be repaired. It still says custom when I turn restart it but I am not rooted. I'm not very knowledgeable at this, I just follow guides step by step. I used an old method to root, it was an automated tool, can't remember the name. Anyway, in my current custom, non-rooted state, sgould I do something first before using motochopper?
SRCP said:
Thanks. Well, I had it rooted but it seems like I lost root when I did something, I don't remember but I think it's when I factory reset it to send it to be repaired. It still says custom when I turn restart it but I am not rooted. I'm not very knowledgeable at this, I just follow guides step by step. I used an old method to root, it was an automated tool, can't remember the name. Anyway, in my current custom, non-rooted state, sgould I do something first before using motochopper?
Click to expand...
Click to collapse
If you got it repaired does it have the same firmware version on it? Got to menu, settings, more, about device and look for the last three characters of your baseband. What are they?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If you got it repaired does it have the same firmware version on it? Got to menu, settings, more, about device and look for the last three characters of your baseband. What are they?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, that pic is recent. I got it repaired months ago.
Related
I created a spot on my website for the stock Odin Tar's that I use for the P600.
I posted the US / XAR Region Stock Odin. I also posted the ML1 Asian base I used as well.
As I gather newer ones I will put them up and updated this thread.
Although this guide is written for the p600 it would, in theory work on any P60x device so long as you have the proper Odin files!
Note: This will not "untrip knox"!!!!!!!!
Here is the download page on my site:
MOD EDIT: Link removed as domain has expired. Thread closed until new links can be installed
Enjoy!
Currently Hosted:
P600UEUBMK1_P600XARBMK1_XAR (Shipped US ROM / XAR Region)
P600ZTUBML1_P600ZZTBML1_BRI (Asian Based ROM / BRI Region)
Other Odin Tar resources: Sammobile. Must be a member but they have tons of them.
How to Return to stock
This mini guide assumes the following...
You were able to root and or install a custom recovery or ROM therefore the drivers are installed on your PC for the tablet. So here we go...
Download Odin from the links in the OP
Extract the the .md5 file from the zip file you downloaded above.
Boot tablet into "Download" mode. You can do this by holding Power and Volume - (down) when the device is shut off. I note on this device it can be a little trickier so you may have to try a couple times. You should now see this on your tablet
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Connect Tablet to PC using known good USB Cable
Start Odin and Press the "AP" button to load the tar.md5 file. This may take a minute as it is also calculating the MD5 to ensure you have a good file. A bad file means bad issues and it wont let you flash it (good fail safe).
Once Odin sees the Tar and loads it completely AND Odin sees the tablet press the Start button to begin. Can takes about 5 to 10 minutes so be patient. Do NOT check or uncheck mark ANY other Options in Odin unless you know what you are doing!
Once it complete you will have a factory image on your tablet. Yay!
But we are not done. You may also want to, at this point, reboot to recovery and do a full data wipe. This method of Odin leaves the SD card and user data intact. To get into recovery hold Power and Volume + until you see the stock Android recovery. Select format Data, reboot. Boom, your tablet is like brand new!
Guided added!
I am not the best technical writer so if you need help understanding what I am saying dont hesitate to ask!
Bumped so people can find this...
Mods moved it so no one looking will actually see it...
scrosler said:
Bumped so people can find this...
Mods moved it so no one looking will actually see it...
Click to expand...
Click to collapse
I'm glad you bumped it. I still haven't tried to install any custom ROM in this tablet, but this post will sure come in handy soon!
Vexelius said:
I'm glad you bumped it. I still haven't tried to install any custom ROM in this tablet, but this post will sure come in handy soon!
Click to expand...
Click to collapse
Indeed!
What happens if I failed to root (according to TWRP) and am stuck in the Samsung splash screen? I was obviously able to install TWRP so hopefully that is enough for Odin to get me back to stock
Will this work?
kaneelias said:
What happens if I failed to root (according to TWRP) and am stuck in the Samsung splash screen? I was obviously able to install TWRP so hopefully that is enough for Odin to get me back to stock
Will this work?
Click to expand...
Click to collapse
If you can see samsung screen you can odin back to stock.
The directions I posted should hold true about getting to Odin / Download Mode
Thanks for this guide, I agree, it should definitely be in the development section.
Hello
So will I get the OTA updates after this? How do I untrip knox?
thanks
Thanks for this Scott and a great ROM!!!!
Sent from my SAMSUNG-SGH-I317 using Tapatalk
tahrang said:
Hello
So will I get the OTA updates after this? How do I untrip knox?
thanks
Click to expand...
Click to collapse
Yes, this is returning you to stock like when you turned it on for the very first time.
No one knows how to untrip knox.
Is it Knox that blocks the ota updates, or is it the rooting itself?
starfall42 said:
Is it Knox that blocks the ota updates, or is it the rooting itself?
Click to expand...
Click to collapse
Not sure. Never tried to Ota with KNOX.
Maybe ask in the Q/A forums.
Just to be safe, and If I do this the tablet will be as if it was completely new, right? I'm going to exchange it for another one and I want to be sure it's as new. Are there any flash counters or stuff like that I should be worried about?
Sent from my Nexus 5
So when a system update comes out we could use these directions to flash the stock rom with out loosing data, apps, settings, etc? Then be able to get the stock OTA?
Coming from the Nexus world, This is a bit different. Google seems to have no interest in the 10 inch sector though, so here we are.
Never have we had a tablet so heavily defended with so many issues. 6 tablets and this one stands out.
Via my Note 3
Tripping out?
scrosler said:
Note: This will not "untrip knox"!!!!!!!!
Click to expand...
Click to collapse
I think I understand what you are saying, but I'm new to Android, and would appreciate a sanity check::cyclops:
1. Knox "trips" (i.e. opens a fusible link in the hardware) if you root the tab and (or?) boot with a non-factory ROM. Once it trips, it cannot ever be "untripped", even if you return to a factory ROM image. (Hence the emphatic statement in the quote.)
2. Question: If a tablet is currently, and has always been, unrooted and stock, will using Odin and these instructions with a factory ROM trip knox? For example, to upgrade to the factory KitKat image
3. Follow-up question: If I flash KitKat as above, can I return to the original release by following your guide, again without tripping knox?
Thanks for the guide and software, and for your help.
iTelegraph said:
I think I understand what you are saying, but I'm new to Android, and would appreciate a sanity check::cyclops:
1. Knox "trips" (i.e. opens a fusible link in the hardware) if you root the tab and (or?) boot with a non-factory ROM. Once it trips, it cannot ever be "untripped", even if you return to a factory ROM image. (Hence the emphatic statement in the quote.)
2. Question: If a tablet is currently, and has always been, unrooted and stock, will using Odin and these instructions with a factory ROM trip knox? For example, to upgrade to the factory KitKat image
3. Follow-up question: If I flash KitKat as above, can I return to the original release by following your guide, again without tripping knox?
Thanks for the guide and software, and for your help.
Click to expand...
Click to collapse
1. As far as anyone knows, Knox cannot be untripped.
2. If you Odin a FACTORY IMAGE it WILL NOT trip Knox. Only custom roms/rooting trips AFAIK.
3. I'm not 100% sure as I haven't tried, but I think I've seen discussions where the bootloader wasn't changed so you could go back. Again, I'm not 100% sure. Maybe we could get clarification from someone who tried.
Sent from my SM-P600 using Tapatalk
So I flashed 4.4.2 successfully and it was booting and everything was working. Now I'm trying to get back to 4.3 but I am unable to do so.
In ODIN, I selected only the 4.3 AP file -
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It just keeps trying to boot for a very long time. What am i doing wrong?
bleuwave said:
So I flashed 4.4.2 successfully and it was booting and everything was working. Now I'm trying to get back to 4.3 but I am unable to do so.
In ODIN, I selected only the 4.3 AP file -
It just keeps trying to boot for a very long time. What am i doing wrong?
Click to expand...
Click to collapse
The 4.4.2 bootloader would stop you from downgrading, in other words, you 'CANNOT' go back to 4.3. You have to use 4.4.2 mate.
stanley08 said:
The 4.4.2 bootloader would stop you from downgrading, in other words, you 'CANNOT' go back to 4.3. You have to use 4.4.2 mate.
Click to expand...
Click to collapse
I have the Canadian version! which allows downgrading...
Can anyone help...i see many people have been successful with downgrading the Canadian version on the forums...
bleuwave said:
I have the Canadian version! which allows downgrading...
Can anyone help...i see many people have been successful with downgrading the Canadian version on the forums...
Click to expand...
Click to collapse
Okay, I know normally, 4.4.2 bootloader stops you from downgrading to 4.3. Maybe those people didn't flash the 4.4.2 bootloader. Anyway!
Then maybe you need a factory reset. Do in stock recovery (It will delete all files in internal sd).
Better still, maybe flash custom recovery then Wipe there and not lose files in Internal SD. Cheers!
bleuwave said:
I have the Canadian version! which allows downgrading...
Can anyone help...i see many people have been successful with downgrading the Canadian version on the forums...
Click to expand...
Click to collapse
Are you running a custom rom right now? If you are, follow the steps below;
- if you flashed a custom rom ( x-note, omega, etc...) after flashing stock firmware, you have to flash back to stock KK same way when you upgrade
- flash your original 4.3 firmware, for example in my case I have MJ4 before flashing then I have to flash MJ4 back because MJ1 will fail.
- if after flashing of original 4.3 firmware and it's getting stuck at the samsung flash screen, take battery out and put it back in, boot to recovery ( press vol up + power + home button at the same time till recovery appears then let go ) and do factory reset then reboot and it should boot up all the way to setup
edit: I haven't seen your last post below the picture, in this case just reboot to recovery and factory reset and it'll boot up all the way to setup.
stanley08 said:
Okay, I know normally, 4.4.2 bootloader stops you from downgrading to 4.3. Maybe those people didn't flash the 4.4.2 bootloader. Anyway!
Then maybe you need a factory reset. Do in stock recovery (It will delete all files in internal sd).
Better still, maybe flash custom recovery then Wipe there and not lose files in Internal SD. Cheers!
Click to expand...
Click to collapse
Thanks! that is what worked...i just saw your post now....
thanks for responding. appreciate how kind people go out of your way to help noobs like us
hey_joe said:
Are you running a custom rom right now? If you are, follow the steps below;
- if you flashed a custom rom ( x-note, omega, etc...) after flashing stock firmware, you have to flash back to stock KK same way when you upgrade
- flash your original 4.3 firmware, for example in my case I have MJ4 before flashing then I have to flash MJ4 back because MJ1 will fail.
- if after flashing of original 4.3 firmware and it's getting stuck at the samsung flash screen, take battery out and put it back in, boot to recovery ( press vol up + power + home button at the same time till recovery appears then let go ) and do factory reset then reboot and it should boot up all the way to setup
edit: I haven't seen your last post below the picture, in this case just reboot to recovery and factory reset and it'll boot up all the way to setup.
Click to expand...
Click to collapse
yeah it was the factory reset that did it after flashing via odin....thanks a bunch for browsing this q/a threads and helping us noobs out! Feels great when someone responds with kind help when all you want to do is bash your head against a wall lol
bleuwave said:
Thanks! that is what worked...i just saw your post now....
thanks for responding. appreciate how kind people go out of your way to help noobs like us
yeah it was the factory reset that did it after flashing via odin....thanks a bunch for browsing this q/a threads and helping us noobs out! Feels great when someone responds with kind help when all you want to do is bash your head against a wall lol
Click to expand...
Click to collapse
Lucky Users of Canadian version. It seems no other version can revert from 4.4 to 4.3 OR 4.3 to 4.2.
Hi guys,
I'm having trouble getting into CWM recovery. When I try to boot into if from Rom Manager it gives me an error that says, "System software not authorized by verizon wireless". After filling my pants I figured out how to get past that and boot up my phone, but I don't know what to do from here. Any thoughts?
I'm running stock 4.4.2 Rooted
Thanks!
Retail devices can only use safestrap. Developer editions can use custom recoveries. Sounds like youre on a retail device.
waxcatharsis said:
Hi guys,
I'm having trouble getting into CWM recovery. When I try to boot into if from Rom Manager it gives me an error that says, "System software not authorized by verizon wireless". After filling my pants I figured out how to get past that and boot up my phone, but I don't know what to do from here. Any thoughts?
I'm running stock 4.4.2 Rooted
Thanks!
Click to expand...
Click to collapse
bmwh0r3 said:
Retail devices can only use safestrap. Developer editions can use custom recoveries. Sounds like youre on a retail device.
Click to expand...
Click to collapse
Like my buddy @bmwh0r3 stated, sounds like you're on a Retail device.
Check out this thread by @az_biker that walks you through all the things you need to know.
Shaggy Kobain said:
Like my buddy @bmwh0r3 stated, sounds like you're on a Retail device.
Check out this thread by @az_biker that walks you through all the things you need to know.
Click to expand...
Click to collapse
Yes I have a retail version rooted using the towelroot method. So I can just install Safestrap and move on from there?
waxcatharsis said:
Yes I have a retail version rooted using the towelroot method. So I can just install Safestrap and move on from there?
Click to expand...
Click to collapse
Correct. Make sure you grab SafeStrap 3.75B04 and you will be good to go :good:
Shaggy Kobain said:
Correct. Make sure you grab SafeStrap 3.75B04 and you will be good to go :good:
Click to expand...
Click to collapse
Great, I'll try that! Thanks guys!
Success! Only thing is I still need to do the workaround to boot up my phone(hold down home, volume down and power). Once I do that I'm able to boot into recovery or system. Do I need to remove CWM through some further process or is something else causing that?
I would start over. Odin the stock tar and pit files. Root again and follow the instructions in the safestrap thread. Be re device you can only use the touchwiz roms
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bmwh0r3 said:
I would start over. Odin the stock tar and pit files. Root again and follow the instructions in the safestrap thread. Be re device you can only use the touchwiz roms
Click to expand...
Click to collapse
I was afraid of that...
bmwh0r3 said:
I would start over. Odin the stock tar and pit files. Root again and follow the instructions in the safestrap thread. Be re device you can only use the touchwiz roms
Click to expand...
Click to collapse
100% agree. Nothing like taking the chance that all is ok, just to get everything set up, issues show their ugly heads, and you end up starting from scratch anyway.
At this point, you're basically at square one, just do it right and save a ton of headaches down the road
az_biker said:
100% agree. Nothing like taking the chance that all is ok, just to get everything set up, issues show their ugly heads, and you end up starting from scratch anyway.
At this point, you're basically at square one, just do it right and save a ton of headaches down the road
Click to expand...
Click to collapse
As I mentioned earlier, I used the towelroot method to get root originally. Can you point me towards a thread that has the most current method to gain root on the Note 3?
waxcatharsis said:
As I mentioned earlier, I used the towelroot method to get root originally. Can you point me towards a thread that has the most current method to gain root on the Note 3?
Click to expand...
Click to collapse
If you're on NC4, towelroot is the most current.
thegamerdarkseid said:
If you're on NC4, towelroot is the most current.
Click to expand...
Click to collapse
Great, so to be clear you recommend unrooting and rooting again?
waxcatharsis said:
Great, so to be clear you recommend unrooting and rooting again?
Click to expand...
Click to collapse
Are you already rooted? Explain fully, are you still trying to use clockwork mod or have you gotten rid of that and trying safestrap?
thegamerdarkseid said:
Are you already rooted? Explain fully, are you still trying to use clockwork mod or have you gotten rid of that and trying safestrap?
Click to expand...
Click to collapse
I have root and safestrap now. I didn't remove CWM I just installed safestrap. It works fine but I am getting an error message that says "system software not authorized" on boot that I have to bypass by pressing volume down, home and power at the same time. It's really a minor inconvenience so I'm not too worried about it but if there's a simple fix I'd like to do that.
waxcatharsis said:
I have root and safestrap now. I didn't remove CWM I just installed safestrap. It works fine but I am getting an error message that says "system software not authorized" on boot that I have to bypass by pressing volume down, home and power at the same time. It's really a minor inconvenience so I'm not too worried about it but if there's a simple fix I'd like to do that.
Click to expand...
Click to collapse
You really may not want to but it'll be best to start over as there's no telling what kind of problems having clockwork mod on a phone with a locked bootloader might bring down the line. Things may seem okay now with a minor inconvenience but you just never know.
thegamerdarkseid said:
You really may not want to but it'll be best to start over as there's no telling what kind of problems having clockwork mod on a phone with a locked bootloader might bring down the line. Things may seem okay now with a minor inconvenience but you just never know.
Click to expand...
Click to collapse
Alright. I can wipe my phone from safestrap but do you know if that will get rid of CWM also?
waxcatharsis said:
Alright. I can wipe my phone from safestrap but do you know if that will get rid of CWM also?
Click to expand...
Click to collapse
You SHOULD be able to perform a FACTORY RESET / WIPE from Android download, that will return your phone to OEM, unrooted (should remove CWM) and all your peronal files.
Then start the process from scratch, the NC4 Root link in my sig has links to the files you need to get back up and running.
This will give you peace of mind that no 'unknowns' are hanging around waiting to surface...
az_biker said:
You SHOULD be able to perform a FACTORY RESET / WIPE from Android download, that will return your phone to OEM, unrooted (should remove CWM) and all your peronal files.
Then start the process from scratch, the NC4 Root link in my sig has links to the files you need to get back up and running.
This will give you peace of mind that no 'unknowns' are hanging around waiting to surface...
Click to expand...
Click to collapse
Thanks Biker, I was at a function last night and couldn't get back to him.
Hey Y'all,
So I've been trying to root my 5.0.1 S4, but could not do it for the life of me. I figured since the CF Auto Root file was made for 4.4.2, I would try flashing back to that with Odin. After getting the correct build for my device, I've been trying to get it to flash, but it got to system, and then stalled forever. I let it run overnight, and it hadn't progressed, so I tried restarting. Now, it fails in a matter of seconds, but I keep seeing progress on the phone's blue bar.
[Q] AM I wasting my time trying to flash an old build? If so, should I just use a custom rom so I get my root? And if so, which one should I use (I'm new to this phone mod stuff.)
Thanks in advance!
F13Bubba said:
Hey Y'all,
So I've been trying to root my 5.0.1 S4, but could not do it for the life of me. I figured since the CF Auto Root file was made for 4.4.2, I would try flashing back to that with Odin. After getting the correct build for my device, I've been trying to get it to flash, but it got to system, and then stalled forever. I let it run overnight, and it hadn't progressed, so I tried restarting. Now, it fails in a matter of seconds, but I keep seeing progress on the phone's blue bar.
[Q] AM I wasting my time trying to flash an old build? If so, should I just use a custom rom so I get my root? And if so, which one should I use (I'm new to this phone mod stuff.)
Thanks in advance!
Click to expand...
Click to collapse
Yes, stop before you brick your device. CF Auto Root works for Lollipop. Or Odin TWRP and flash SuperSU zip. Or just flash a rooted ROM. Read the OPs and decide which one sounds like the best fit for you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bilgerryan said:
Yes, stop before you brick your device. CF Auto Root works for Lollipop. Or Odin TWRP and flash SuperSU zip. Or just flash a rooted ROM. Read the OPs and decide which one sounds like the best fit for you.
Click to expand...
Click to collapse
KK, thanks. I could not get CF to root my device, trying 3 different versions of Odin. I'll go the custom rom route, methinks.
F13Bubba said:
KK, thanks. I could not get CF to root my device, trying 3 different versions of Odin. I'll go the custom rom route, methinks.
Click to expand...
Click to collapse
Uncheck Auto Reboot and F Reset (everything) when using Odin. And wait a minute after it says PASS before unplugging. Also try different ports and cables.
I can only find .img files for TWRP, I haven't yet been able to find any .tar files. Any tips on where to get a recovery file to use with Odin?
Yeah, definitely cannot restart my phone at the point, it's referring me to Kies to recover. Kies won't connect, either 3.0 or 2.6. So At this point I guess I'm hoping flashing a custom ROM will work...otherwise, is my phone bricked?
F13Bubba said:
I can only find .img files for TWRP, I haven't yet been able to find any .tar files. Any tips on where to get a recovery file to use with Odin?
Yeah, definitely cannot restart my phone at the point, it's referring me to Kies to recover. Kies won't connect, either 3.0 or 2.6. So At this point I guess I'm hoping flashing a custom ROM will work...otherwise, is my phone bricked?
Click to expand...
Click to collapse
TWRP can flash images now.
Flash this build of TWRP first. (It's a .tar for Odin)
https://dl.twrp.me/jfltespr/twrp-2.8.4.0-jfltespr.tar
Copy this build to your device somewhere. (You might as well go ahead and copy a ROM you want to install on your device also.)
https://dl.twrp.me/jfltespr/twrp-2.8.7.0-jfltespr.img
Boot into TWRP and go to install. Select images button at the bottom right and select the build you copied to your device. You will now be running the current version of TWRP.
WOOOOOO!
After a ton of troubleshooting and grief, I finally got 5.0.1 back on, and working. I also discovered that my front usb port was not working correctly. I guess I'll try to root it now!
Aaaaaand, it seems to have worked flawlessly. Thanks for all the help guys!
January 1 Security update. Everything else seems to have stayed the same.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Another update! Cool.
These security updates are coming very frequently. I would be careful updating if you value an unlocked bootloader. I wouldn't bet that Samsung wouldn't pull a fast one and lock it down even at this stage of the N4's life span. So be careful just incase.
Could anyone installed this update, confirms that the bootloader still unlocked, plz?
Sent from my SM-N910P using Tapatalk
tx_dbs_tx said:
These security updates are coming very frequently. I would be careful updating if you value an unlocked bootloader. I wouldn't bet that Samsung wouldn't pull a fast one and lock it down even at this stage of the N4's life span. So be careful just incase.
Click to expand...
Click to collapse
I agree. I never update until i have an Odin file!
aaron74 said:
I agree. I never update until i have an Odin file!
Click to expand...
Click to collapse
When you get the full tar file which files you remove from the tar before flashing to make sure that your bootloader still the old unlocked one?
anees02 said:
When you get the full tar file which files you remove from the tar before flashing to make sure that your bootloader still the old unlocked one?
Click to expand...
Click to collapse
I dont remove anything. But just use the name to verify the bootloader is same version. I cant verify this but I read somewhere that as long as the version number doesnt change, then its backwards flashable. Heres an example of what I mean.
Heres current firmware on sammobile N910PVPS4DPK1
and following so on like these N910PVPS4DPJ1, N910PVPU4DPH4, etc.
After the PVP is the bootloader version # as "S4" and "U4". Now what I read is as long as that # is same, that determines what firmware you can use.
So if you go back to firmware that we cant go back to like N910PVPU3BOF5. You can see its a 3. This is why we can only go back to N910PVPU4COG5
So in other words, as long as that stays a "4" , we should be able to downgrade to any firmware that is a "4".
As I already stated, I dont know this first hand, but have read it somewhere here!!
Hope this was helpful!!
aaron74 said:
I dont remove anything. But just use the name to verify the bootloader is same version. I cant verify this but I read somewhere that as long as the version number doesnt change, then its backwards flashable. Heres an example of what I mean.
Heres current firmware on sammobile N910PVPS4DPK1
and following so on like these N910PVPS4DPJ1, N910PVPU4DPH4, etc.
After the PVP is the bootloader version # as "S4" and "U4". Now what I read is as long as that # is same, that determines what firmware you can use.
So if you go back to firmware that we cant go back to like N910PVPU3BOF5. You can see its a 3. This is why we can only go back to N910PVPU4COG5
So in other words, as long as that stays a "4" , we should be able to downgrade to any firmware that is a "4".
As I already stated, I dont know this first hand, but have read it somewhere here!!
Hope this was helpful!!
Click to expand...
Click to collapse
Thank you very much.
I knew something new today because of you... Thanks again.
When I see to the latest OTA QA1 there are two things T4 and S4 what does that mean?
Maybe different CSC versions?
anees02 said:
Thank you very much.
I knew something new today because of you... Thanks again.
When I see to the latest OTA QA1 there are two things T4 and S4 what does that mean?
Maybe different CSC versions?
Click to expand...
Click to collapse
On all firmwares. The middle listing is the csc version, and its always got a different numbering than the others.
There's 3 version numbers here. 1st is the PDA (which is the actual rom firmware) 2nd is CSC (which is region) 3rd is the PHONE (which is the modem)
So this one is still #4 so it should be alright to still downgrade.
Now the last 3 digits just rep the date. Q=2017 A=January 1= 1st revision.
https://forum.xda-developers.com/showthread.php?t=1356325
wow. learning new things. thank guys.
just a little too late, after taking the update myself.
Has anyone been able to twrp/root? or odin backwards is the only way right now?
linhnd2000 said:
wow. learning new things. thank guys.
just a little too late, after taking the update myself.
Has anyone been able to twrp/root? or odin backwards is the only way right now?
Click to expand...
Click to collapse
You can Odin back as far as OG5 which is Android Lollipop 5.1
You can Odin TWRP on any of those updates. But Odin the desired update first if that's your goal.
What gets overlooked with TWRP flash is that you should boot directly into recovery after flashing. If you boot system first, immediately after TWRP flash, stock recovery gets restored.
That pattern and timing is tricky so it's recommended to uncheck auto reboot in Odin options when flashing TWRP. Once you get the success, 0 failed in Odin status, pull the USB cable and battery and wait at least 30 seconds (some suggest waiting at least a minute while discharging power circuit by holding power button down *Don't go Beastmode on that power button*). Reinstall battery and pattern boot into recovery (Vol+, Power and Home simultaneously until phone vibrates).
If you're rooting stock with stock kernel, you need systemless superuser. Flash SuperSU zip by Chainfire in recovery.
If flashing a custom ROM, you only need TWRP. No pre-root required for that.
Sent from my SM-N920P using Tapatalk
samep said:
You can Odin back as far as OG5 which is Android Lollipop 5.1
You can Odin TWRP on any of those updates. But Odin the desired update first if that's your goal.
What gets overlooked with TWRP flash is that you should boot directly into recovery after flashing. If you boot system first, immediately after TWRP flash, stock recovery gets restored.
That pattern and timing is tricky so it's recommended to uncheck auto reboot in Odin options when flashing TWRP. Once you get the success, 0 failed in Odin status, pull the USB cable and battery and wait at least 30 seconds (some suggest waiting at least a minute while discharging power circuit by holding power button down *Don't go Beastmode on that power button*). Reinstall battery and pattern boot into recovery (Vol+, Power and Home simultaneously until phone vibrates).
If you're rooting stock with stock kernel, you need systemless superuser. Flash SuperSU zip by Chainfire in recovery.
If flashing a custom ROM, you only need TWRP. No pre-root required for that.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
works perfectly. thanks. I went back to PK1 so I can use the debloated rom.