{
"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"
}
Just wanted to let you guys know how to unroot the AT&T Galaxy Note 3 especially since it looks like you have to do some digging to find the correct files for the SM-N900A Galaxy Note 3.
I have created a step by step guide: Here
All credits go to designgears' thread!
techfanatic9 said:
Just wanted to let you guys know how to unroot the AT&T Galaxy Note 3 especially since it looks like you have to do some digging to find the correct files for the SM-N900A Galaxy Note 3.
I have created a step by step guide: Here
All credits go to designgears' thread!
Click to expand...
Click to collapse
Thanks a lot sir!!
Thank you
Lose regional lock?
supers2k said:
Thank you
Click to expand...
Click to collapse
If you unroot Lose the regional unlock????
can you at least put a warning up, if you are on MJ5 and you try this method you will brick your device?
Thanks.
What if you are on MI1, can you still do the MJ9 one click and upgrade to MJ9 unrooted?
dead link
I have been looking for a way to unroot my n900a and everywhere i have gone the files needed leave me at a dead link...can anyone help with this a mirror or am I missing something here?
If you rooted with Kingo, just unroot using the unroot commend in SU. After a couple of restarts everything will be back to normal. This also works on MJ5..
Sorry, but this doesn't work.
I keep getting a "FAILED" message.
If you are on mj5 and you flash it using Odin with the mj5 stock ROM will the Knox counter trigger?
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Kitkat 4.4 Leak
Could you use this to return a Note 3 to stock that was running the leaked build of kitkat?
Failed
I'm getting a failed message as well. Seems like the OP isn't responding to anyone who was unsuccessful returning back to stock.
Also get the failed message.
many more people are getting it on his website with zero response.
songokussm said:
Also get the failed message.
many more people are getting it on his website with zero response.
Click to expand...
Click to collapse
Yeah. With all the ads on OPs website, OP is just probably here to make some extra revenue from the ads.
i have a friend who works for Samsung mobile and she tried putting on kitkat from her work laptop. The firmware she has comes directly from Samsung but it wouldn't let her because it kept reading that my phone had been rooted. i had used this app ginger unroot to supposedly remove my root but it apparently didn't work. I would like to know if i use this method will that by pass the message?
You won't get anywhere with this method. Read our replies.
Odin Fails
Hi I have my AT&T Note 3 currently rooted but want to put it back to normal. I never changed the ROM and Knox hasn't been tripped. But what I did was uninstall certain apps that were preloaded with out backing them up first. Also my wifi decided to not work anymore and I cant do any updates. So I decided I wanted to reinstall stock firmware. I downloaded the firmware from SamMobile and used Odin 3.09 like it was recommended. But every time I try Odin Fails. I also tried this method as well and Odin fails. I tried mulitple cords, usb ports, and different computers. Here is what the Odin log says
<ID:0/019> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900AUCUBMI9_N900AATTBMI9_N900AUCUBMI9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/019> Odin v.3 engine (ID:19)..
<ID:0/019> File analysis..
<ID:0/019> SetupConnection..
<ID:0/019> Initialzation..
<ID:0/019> Get PIT for mapping..
<ID:0/019> Firmware update start..
<ID:0/019> SingleDownload.
<ID:0/019> sbl1.mbn
<ID:0/019> NAND Write Start!!
<ID:0/019> FAIL! (Auth)
<ID:0/019>
<ID:0/019> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
StormChaser83 said:
Sorry, but this doesn't work.
I keep getting a "FAILED" message.
Click to expand...
Click to collapse
Did you figure out why it was failing and if there is any fix for it?
Unfortunately, I will have to unroot my phone.... work requires me to encrypt my device... which apparently won't encrypt with root. Is this a pretty safe method to unroot?
Related
Hello XDA, this is probably my first thread ever.
I am a complete noob on Android but have some knowledge on technically supporting other platforms.
My father owns a N7000 he bought in Dubai, factory unlocked, which is now running the latest Samsung stock official Gingerbread, unrooted.
We live in Argentina, and he has been able to use the phone for about 15 days with a local carrier without any problem.
Last Friday, the phone stopped working and he can not make or receive calls, send/receive SMS or use mobile network data at all. Wifi works perfectly. IMEI displays just fine.
I have already tried removing and reinserting the SIM card, tried with another SIM card from another carrier, tried going in an out of airplane mode, restored the phone to factory defaults and all other recommended solutions to this problem I found on the forums, except for flashing it.
Should I flash it? I am not looking for a custom ROM nor rooting or anything "unofficial". It is my Dad's phone.
Should I flash another modem suitable for my region?
If I am not wrong I should also be flashing a new bootrom if I were to flash an ICS ROM, right?
I do not completely understand if changing modem, PDA or CSC would possibly brick the device if not carefullly chosen. Can I flash any ICS PDA I randomly choose from the official ROMs thread?
My phone version is as follows:
PDA: N7000JPLA1
PHONE: N7000XXLA4
CSC: N7000OJPLA1
Build Info: Tue Jan 17 00:51:31 KST 2012
I would be more than grateful for any help you could give me.-
If you have been able to use it with no problem for 15 days, and all of a sudden it's not working , unless you did something in between, I do not see any other reason but a hardware problem.
P_
Also sounds like a hardware problem to me. Nonetheless I would try to flash a rom. It's worth a try, if it doesn't help it won't do any harm neither. In the following thread you'll find all stock roms a long with a manual how to flash using pc odin.
http://forum.xda-developers.com/showthread.php?p=20963707
One remark: If you want to be on the safe side flash a Gingerbread rom. If you want to flash an ICS rom don't flash a wipe rom and don't perform a factory reset after you flashed the rom. ICS roms suffer from a bug and can possibly brick your phone.
Sent from my Galaxy Note running ICS
Thanks, I will try to re-flash Gingerbread to the device then. Should I try flashing a different modem or anything or would the best thing be to flash the same version the device has shipped with?
I have just reflashed the phone and nothing has changed
Should I flash another modem maybe?
I will be taking it to a Samsung repair center but unfortunately since I did not buy the phone in my country it is not covered by the warranty :S
mfragola said:
I have just reflashed the phone and nothing has changed
Should I flash another modem maybe?
I will be taking it to a Samsung repair center but unfortunately since I did not buy the phone in my country it is not covered by the warranty :S
Click to expand...
Click to collapse
Yes, you could try another radio modem..try LP5
Sent from my GT-N7000 using xda premium
have you tried the sim in a different phone to see if it is sim or phone related?
Yes, I have tried another working SIM on the Note and exactly the same symptoms. I will search for LP5 then, thanks
You can flash only modem part too.
Here is ROM, which is you have right now installed
http://www.hotfile.com/dl/144991211/85c9920/N7000JPLA1_N7000OJPLA1_XSG.zip.html
Download and extract it.
Download odin
Install kies (driver) to PC
open odin and select phone tab and point to ROM file which you have extracted.
Dont select re partition/bootloader/pit/PDA/CSC
and flash it
If you want to flash full ROM, here it goes like below image( have to select PDA)
look this image
{
"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"
}
So if you want to flash modem only
select Phone tab
If you wish to flash full ROM
select PDA tab
rest of procedure remain same.
This is what I am getting:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000JPLA1_N7000OJPLA1_N7000XXLA4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> cache.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004>
<ID:0/004> Receive Response form LOKE
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
LP5 failed too
(EDIT: When I made the full flash earlier today I used this same ROM file with PDA selected on Odin)
seems connection error
Are you sure you have put your device in download mode? (switch off then vol dwn + Home + power. release power once see logo. then press vol up to continue. you will see downloading now...)
make sure kies is completely closed
No antivirus is running
try different USB port, without any extension cable
Thanks for your prompt replies.
The error appears to happen only when selecting PHONE option on Odin, as I have just tried reflashing full PDA and the process has completed successfully.
I will try flashing the official ROM from my carrier in Argentina I found on the official ROMs thread, and if it doesn't work I will be taking it to Samsung.
Please as a last favour would you please let me know if doing that could lead to something bad?
Hardware failure then? I can't even call 911, it says "Out of service area"...
You can flash any rom.
Does it worked after flashing rom?
Sent from my GT-N7000 using xda premium
No, unfortunately it has not worked. Flashing my local carrier's ROM has changed the installed modem and still no luck. I will be going to Samsung then.
Thanks for all your help, I will let you know if something changes
Likely hardware issue then.
Goodluck
Sent from my GT-N7000 using xda premium
Can't activate due to using cyanogenmod 11 (using cyanogenmod installer). Now, I don't know how to flashback to stock sprint rom. I follow this tutorial and received fail message
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
this is the information of my phone
{
"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"
}
I'm trying to follow this comment but I can't boot into recovery mode.
Please help, I am a yesterday android user, I don't know much
skip this and read the next paragraph. Fix is at bottom.
This is my hard work. It keeps falling down the haystack. I just posted a l720t help thread with this in it too. This method has worked for me on ANY rooted device. Recovery is just an app away. Then you can flash your stock.zip.
http://androidforums.com/sprint-gal...y-way-flash-custom-recovery-rom-720-720t.html
Upon further review of this post in its entirety.. it would seem as though your trying to flash back to stock with odin. Not recovery flashable zips.
If this is the case... A. Be sure to only flash the same android version that you last had on stock.. or newer. (Not 100% sure.. but i believe this 'could' break your device)
And B. Make sure the device is 1. Connected 2. Drivers are installed completely. 3. IS IN "DOWNLOAD MODE" (by holding volume down + home + power. After the warning pops up hit volume up as it should state to continue)
4. Is being read by 'Odin Multi Downloader' (com box should be yellow and or show a com# {ie. com 4 } then and only then proceed) ..
BTW im out of space on my tapatalk app so you might have to long-press the little 'broken image boxes' to view 'em.
Now I already know your problem. You have updated to NAE.. proof here..
Good news is there is an easy enough fix. Flash the right NAE firmware. proof here..
Solution found here bud ... http://forum.xda-developers.com/showthread.php?t=2663619
Daisflaque said:
This is my hard work. It keeps falling down the haystack. I just posted a l720t help thread with this in it too. This method has worked for me on ANY rooted device. Recovery is just an app away. Then you can flash your stock.zip.
Click to expand...
Click to collapse
I'm on cyanogenmod 11 now, I have no idea how to root . Please help me
simaxe said:
I'm on cyanogenmod 11 now, I have no idea how to root . Please help me
Click to expand...
Click to collapse
Cyanogenmod comes rooted buddy. but never mind root. Just follow the link at the bottom of my last post. That will get you back to stock bud.
Daisflaque said:
Cyanogenmod comes rooted buddy. but never mind root. Just follow the link at the bottom of my last post. That will get you back to stock bud.
Click to expand...
Click to collapse
OH GOD, YOU SAVE MY PHONE. Thank you so much man.
All in a few minutes work. anytime buddy. try and use that thanks button tho
Daisflaque said:
All in a few minutes work. anytime buddy. try and use that thanks button tho
Click to expand...
Click to collapse
New errors
Unfortunately, Google Play Services Has Stopped
Please help me, happen repeatedly
Go through the updates in sprint zone. Ie. Update prl, profile and firmware. I try to not update software but thats just me. Afterwards power off. Hold volume up+home+power. Factory reset. Reboot. And all should be well.
---------- Post added at 06:28 PM ---------- Previous post was at 06:10 PM ----------
Please let us know if everything worked.
Daisflaque said:
Go through the updates in sprint zone. Ie. Update prl, profile and firmware. I try to not update software but thats just me. Afterwards power off. Hold volume up+home+power. Factory reset. Reboot. And all should be well.
---------- Post added at 06:28 PM ---------- Previous post was at 06:10 PM ----------
Please let us know if everything worked.
Click to expand...
Click to collapse
Work perfectly, thanks a lot
Of course bud. Hope all is well from now on.
Sent from my SPH-L720 using Xparent Purple Tapatalk 2
Hi I am wondering how do I root sgh-i337 with 5.0.1 it is already updated from Att all I can find is threads that have keep root, any help on this would be great and yes I know this voids warranty I don't care if it does just saying before people start posting saying different thing like that all I want to do is root my phone thanks for any help
killernos said:
Hi I am wondering how do I root sgh-i337 with 5.0.1 it is already updated from Att all I can find is threads that have keep root, any help on this would be great and yes I know this voids warranty I don't care if it does just saying before people start posting saying different thing like that all I want to do is root my phone thanks for any help
Click to expand...
Click to collapse
Flash NB1 and do the keeproot method, otherwise there's no other way.
how do i flash nb1 fron 5.0.1? by odin like any other samsung??
Enviado desde mi SAMSUNG-SGH-I337 mediante Tapatalk
DeadlySin9 said:
Flash NB1 and do the keeproot method, otherwise there's no other way.
Click to expand...
Click to collapse
Will flashing nb1 not downgrade the bootloader?
Root SGH-I337 running Lollipop 5.0.1
Hi All, I'm new here and also a noob. Can I continue this thread or do I need to start a new one? Just like OP, I want to root my AT&T S4, and eventually install custom ROM's. I've tried everything I can find with no success. King Root, KingoRoot, CASUAL, Super Root, OneClick root, Root Genius... I just want my phone my way. Can anyone help with tutorials and such? Thanks in advance
Cliffhanger68 said:
Hi All, I'm new here and also a noob. Can I continue this thread or do I need to start a new one? Just like OP, I want to root my AT&T S4, and eventually install custom ROM's. I've tried everything I can find with no success. King Root, KingoRoot, CASUAL, Super Root, OneClick root, Root Genius... I just want my phone my way. Can anyone help with tutorials and such? Thanks in advance
Click to expand...
Click to collapse
Its impossible (momentarily) to direct root 5.0.1
Only method is downgrading to NB1 - rooting with towelroot - then doing a keeproot update to 5.0.1
Downgrade to NB1 and root using this post HERE (Second post - second part under HOW TO GET TO ANY KITKAT 4.4.2)
To update to 5.0.1 and keep root follow this post HERE.
TheJuli said:
Its impossible (momentarily) to direct root 5.0.1
Only method is downgrading to NB1 - rooting with towelroot - then doing a keeproot update to 5.0.1
Downgrade to NB1 and root using this post HERE (Second post - second part under HOW TO GET TO ANY KITKAT 4.4.2)
To update to 5.0.1 and keep root follow this post HERE.
Click to expand...
Click to collapse
I tried to downgrade to NB1 before using the same guide and file in the link, got several errors, I don't remember what they were. When I rebooted I was still in OC4. I will try again in the next couple of days (Wife's birthday tomorrow) when I have the extra time. I will update post when I find out something. Thanks for the response and the interest in helping!
---------- Post added at 04:42 AM ---------- Previous post was at 03:59 AM ----------
Cliffhanger68 said:
I tried to downgrade to NB1 before using the same guide and file in the link, got several errors, I don't remember what they were. When I rebooted I was still in OC4. I will try again in the next couple of days (Wife's birthday tomorrow) when I have the extra time. I will update post when I find out something. Thanks for the response and the interest in helping!
Click to expand...
Click to collapse
Just tried to Odin v3.09 to NB1... FAIL! Here is the log from Odin. Don't know if you can tell anything from it or not, besides that it failed.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUFNB1_TWRootable_Full_Odin.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
Cliffhanger68 said:
I tried to downgrade to NB1 before using the same guide and file in the link, got several errors, I don't remember what they were. When I rebooted I was still in OC4. I will try again in the next couple of days (Wife's birthday tomorrow) when I have the extra time. I will update post when I find out something. Thanks for the response and the interest in helping!
---------- Post added at 04:42 AM ---------- Previous post was at 03:59 AM ----------
Just tried to Odin v3.09 to NB1... FAIL! Here is the log from Odin. Don't know if you can tell anything from it or not, besides that it failed.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUFNB1_TWRootable_Full_Odin.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
Click to expand...
Click to collapse
Tried it again, it got a few more steps in then failed, then again a few steps more. Then it hung... uh oh! softbricked. None of the "fixes" work. Any more ideas? HELP!!!
---------- Post added at 08:40 AM ---------- Previous post was at 08:34 AM ----------
Cliffhanger68 said:
I tried to downgrade to NB1 before using the same guide and file in the link, got several errors, I don't remember what they were. When I rebooted I was still in OC4. I will try again in the next couple of days (Wife's birthday tomorrow) when I have the extra time. I will update post when I find out something. Thanks for the response and the interest in helping!
---------- Post added at 04:42 AM ---------- Previous post was at 03:59 AM ----------
Just tried to Odin v3.09 to NB1... FAIL! Here is the log from Odin. Don't know if you can tell anything from it or not, besides that it failed.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUFNB1_TWRootable_Full_Odin.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
Click to expand...
Click to collapse
Tried it again, it got a few more steps in then it failed, then again a few steps more, failed. Then it hung... uh oh! softbricked. "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again". None of the "fixes" that I have tried work. Any more ideas? HELP!!!
Cliffhanger68 said:
Tried it again, it got a few more steps in then failed, then again a few steps more. Then it hung... uh oh! softbricked. None of the "fixes" work. Any more ideas? HELP!!!
---------- Post added at 08:40 AM ---------- Previous post was at 08:34 AM ----------
Tried it again, it got a few more steps in then it failed, then again a few steps more, failed. Then it hung... uh oh! softbricked. "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again". None of the "fixes" that I have tried work. Any more ideas? HELP!!!
Click to expand...
Click to collapse
FINALLY!!! got it back up. Running 4.4.2, NB1, rooted.
Cliffhanger68 said:
FINALLY!!! got it back up. Running 4.4.2, NB1, rooted.
Click to expand...
Click to collapse
Im pretty sure the cable you are using is faulty OR the port in which you have connected it is faulty. In this case faulty, does not mean totally broken. Something like kinda loose, not in a particularly good shape. Try using a different port in the PC or a different micro USB cable. Everything you did was fine and how it should have been done. Hardware problem.
TheJuli said:
Im pretty sure the cable you are using is faulty OR the port in which you have connected it is faulty. In this case faulty, does not mean totally broken. Something like kinda loose, not in a particularly good shape. Try using a different port in the PC or a different micro USB cable. Everything you did was fine and how it should have been done. Hardware problem.
Click to expand...
Click to collapse
I think there may be a little truth to that, I used my son's PC (newer hardware) and it got further but still failed several times. I moved it back to mine and used a MoBo USB port and it seemed to do better. I installed the PIT file and finally got it to work after probably 15 to 20 times. Now, I can Odin with no problem, but only the NB1 that is on it now. I tried to update to OC4 and it stuck at the Samsung logo. I re-Odin'd the NB1 which went in with no problem. Now, I'm setting it up, I'm gonna rock 4.4.2 for a while, got scared! . Been going thru Titanium backup and getting it cleaned up a bit. Thanks for all the assistance.
Cliffhanger68 said:
I think there may be a little truth to that, I used my son's PC (newer hardware) and it got further but still failed several times. I moved it back to mine and used a MoBo USB port and it seemed to do better. I installed the PIT file and finally got it to work after probably 15 to 20 times. Now, I can Odin with no problem, but only the NB1 that is on it now. I tried to update to OC4 and it stuck at the Samsung logo. I re-Odin'd the NB1 which went in with no problem. Now, I'm setting it up, I'm gonna rock 4.4.2 for a while, got scared! . Been going thru Titanium backup and getting it cleaned up a bit. Thanks for all the assistance.
Click to expand...
Click to collapse
Glad you got it all sorted out.
There is nothing to be afraid of imo - with these updates files and files, its impossible to hard brick. You simply just hate it when it soft bricks because you have to re do it all again.
BTW - Did you odin the new bootlader after flashing the oc4 update with flashfire? That could be the problem of why it gets stuck to the smasung logo.
TheJuli said:
Im pretty sure the cable you are using is faulty OR the port in which you have connected it is faulty. In this case faulty, does not mean totally broken. Something like kinda loose, not in a particularly good shape. Try using a different port in the PC or a different micro USB cable. Everything you did was fine and how it should have been done. Hardware problem.
Click to expand...
Click to collapse
Just in case anyone is still following this, I ended up going back to stock, letting it update OTA back to Lollipop. Then this week I decided to try again and I was able to direct root my I337, on 5.0.1. OC4, using Kingroot. Then I used w0lfdroid's method to replace Kinguser with Supersu. Worked like a charm. Still rooted after multiple reboots. Then I installed Titanium Backup and took out some of the BS apps and I like my phone a lot better now. Hmmm, what's next? :victory:
Hmmm, maybe I'll try to install a custom recovery... any suggestions on a ROM? Got a lot of reading to do.
{
"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"
}
Sent from my Rooted Galaxy S4 SGH-I337 on 5.0.1 Lollipop.
Cliffhanger68 said:
Hmmm, maybe I'll try to install a custom recovery... any suggestions on a ROM? Got a lot of reading to do.
Sent from my Rooted Galaxy S4 SGH-I337 on 5.0.1 Lollipop.
Click to expand...
Click to collapse
Dropped it week before last. Broke the lcd. Ordered a new one, now back up and running!
Hi,
Long story short....
I bought a brand new S5 from Vodafone December 2014 with the intention to unlock it to use on three, Anyway it took 2 months to unlock it through Vodafone UK. If that wasn't enough...
The phone in question a few weeks ago started acting up where it would occasionally turn itself off then re-boot back up again like nothing happened.... Well now it won't come on at all and if by some miracle you do get it to come on it freezes straight away and it will then usual power down its self and then go into a kinda boot loop where it will load up to the black screen with the Samsung logo then a line across the screen appears for a split second the then it repeats this step continuously unless you remove the battery....
So naturally seen as the device was only 4 months old at the time I contacted Samsung directly (after the farce I had with Vodafone last time round) anyway they sent me a box and a label so off the phone went and a few days later I got an email...... Well I was gobsmacked at the cheek of what they said! Here's a copy/past of the email below.
"Hello *****.
We’re contacting you from the Samsung repair centre.
Thank you for sending your Samsung SM-G900F to us for repair. We have received it successfully and our engineers have carried out a thorough examination.
We have located an issue on your device and this is not covered under the manufacturer’s warranty.
Our engineers have found that your KNOX warranty shows your device has been rooted and are therefore unable to further assess any faults you were experiencing.
Please see attached a picture of the issue.
This is considered too severe for us to proceed, and classes your product as Beyond Economical Repair. (BER)
We are sorry for any inconvenience this causes you *****.
We’ll now return your device back to you unrepaired and it will reach your registered return address within the next 3 working days via our courier, DPD.
Thank you for your time today."
....... Well I didn't know what to make of this email to begin with as I had never rooted this device, I would never do anything to a device that is still under warranty. I pleaded my argument with them and they weren't having any of it. So my 2 options where either pay £174 to have it fixed or have it returned unfixed...so I took the latter option.
Then I took the phone to a Vodafone store after this and they sent it away, Basically a week later I had the same outcome.
So I contacted Trading Standards and 3 weeks later nothing is happening, I'm having to do all the leg work to prove my innocence, I'm not prepared to go to court over something like this........so I'm either going to sell the phone as it is or try with help from you guys to get it fixed hopefully.
(I I know I said long story short, sorry)
Any help or advice would be much appreciated.
Hello, vxlomegavy,
sorry about your plight. but if this is about your warranty... personally, i wouldn't go after samsung for this thing. does your device still go to download moade? if yes, i would recommend downloading a full firmware and flash your device via odin (since they claim your warranty is void). if you dont know how, please search the forums. if still unclear, please post here. i will try my best to help.
Regards, Greatness.
Greatness_GH said:
Hello, vxlomegavy,
sorry about your plight. but if this is about your warranty... personally, i wouldn't go after samsung for this thing. does your device still go to download moade? if yes, i would recommend downloading a full firmware and flash your device via odin (since they claim your warranty is void). if you dont know how, please search the forums. if still unclear, please post here. i will try my best to help.
Regards, Greatness.
Click to expand...
Click to collapse
Hi Greatness,
Thanks for the response....
I would be up to trying to flash the device with guidance, If someone would point me in the direction of all the software i need to download and a quick step by step guide i will give it a shot, At this point i've nothing to lose.
Thanks
By the way i don't mind going back onto KitKat if it makes things simpler.
vxlomegavy said:
By the way i don't mind going back onto KitKat if it makes things simpler.
Click to expand...
Click to collapse
flashing via odin is the same procedure, no matter which android version.... please check ou this tutorial from AndroidXDA
{
"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"
}
Cant seem to open odin... Any ideas?
Greatness_GH said:
flashing via odin is the same procedure, no matter which android version.... please check ou this tutorial from AndroidXDA
Click to expand...
Click to collapse
Just cant open odin for some reason
Managed to get Odin to work and downloaded lolipop etc.. But i've had an error..
Managed to get it to do it eventualy but it hasn't fixed the phone its just the same.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1BOA3_G900FOXA1BOA4_G900FXXU1BOA3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Rooting shouldn't void your warranty any more than putting Linux on a pc that came with windows. I'd push trading standards on this one. I had a rooted htc one x that developed a fault and they repaired it. St the end of the day unless they can prove the actual fault was caused by you they have a legal obligation to fix it. Sssuming your in the uk? Gaining admin rights (which is all rooting is) to an operating sysyem will not cause hardware problems. Tbh though Vodafone supplied the phone so your contract is with them not samsung. Get on the phone to Vodafone on the freephone number and don't put the phone down till you get a new phone. Trust me after 3 to 4 hours they will give it to you. A tip make sure you get the contacts name and number and always go back to the same person after they try shipping you round their office. Persistence pays! Good luck.
ok so i am a typical bloke. i ignored all the warnings however i did read the instructions which makes a change.
Bought a new note 4 and decided to ROOT it as it was the buzz word going round. Rooting all worked fine no problem there however i forgot to check the phone actually worked before i rooted it. Once i finally put in te new sim i discovered that when i make a call i cannot hear the caller. They can hear me fine and if i put the phone on to speaker or bluetooth headset it works no problem.
So i now need to send the phone back but first i must unroot it. I have tried numerous links etc however every firmware file i have downloaded has either stopped at .1GB left of a 1.8GB file or been a scam / virus. Tried SAMMOBILE last night and all i got was 1.7gb downloaed overnight and the file is jargon name is lots of boxes #~}&& etc
Tech spec of the Phone
SM-N910F Android Version 5.0.1 Baseband Version N910FXXU1BOC4 build number N910FXXU1BOC5
Please help i need to restore and send back for an exchange
cheers
Mr Stupid
You do realise that you may have voided your warranty by rooting! It trips the knox counter. Have the SM-N910F, UK. SamMobile, search firmware for 910f, UK, comes up with United Kingdom BTU, which worked for me. Used Odin to reload the firmware.
Sent from my SM-P900 using XDA Free mobile app
technophobe321 said:
ok so i am a typical bloke. i ignored all the warnings however i did read the instructions which makes a change.
Bought a new note 4 and decided to ROOT it as it was the buzz word going round. Rooting all worked fine no problem there however i forgot to check the phone actually worked before i rooted it. Once i finally put in te new sim i discovered that when i make a call i cannot hear the caller. They can hear me fine and if i put the phone on to speaker or bluetooth headset it works no problem.
So i now need to send the phone back but first i must unroot it. I have tried numerous links etc however every firmware file i have downloaded has either stopped at .1GB left of a 1.8GB file or been a scam / virus. Tried SAMMOBILE last night and all i got was 1.7gb downloaed overnight and the file is jargon name is lots of boxes #~}&& etc
Tech spec of the Phone
SM-N910F Android Version 5.0.1 Baseband Version N910FXXU1BOC4 build number N910FXXU1BOC5
Please help i need to restore and send back for an exchange
cheers
Mr Stupid
Click to expand...
Click to collapse
Not a big deal. And you can regain your warranty but there is only one way. To reflash stock rom. Note that it will delete every file on internal storage but after that you will have a phone just like you did when it came out of the box.
So first go and find note 4 official firmware download only from trusted sources.
Then download odin for your phone brand. Search for Odin Multi Installer Note 4.
Collect any other files that you may need.
Lastly go sesrch for how to flash firmware to note 4 with odin.
Thats all
Sent from my LG-D722 using Tapatalk
You could also try purposely hard bricking the phone. I did this by accident once with my old phone and when I brought it in, I was just like, "It stopped turning on! I don't know why "
The ATT guys fiddled with it, checked for water damage, then gave me a new phone.
Not the best solution, but it worked for me, lol.
Sent from my SAMSUNG-SM-N910A using Tapatalk
NemboSix said:
Not a big deal. And you can regain your warranty but there is only one way. To reflash stock rom. Note that it will delete every file on internal storage but after that you will have a phone just like you did when it came out of the box.
So first go and find note 4 official firmware download only from trusted sources.
Then download odin for your phone brand. Search for Odin Multi Installer Note 4.
Collect any other files that you may need.
Lastly go sesrch for how to flash firmware to note 4 with odin.
Thats all
Sent from my LG-D722 using Tapatalk
Click to expand...
Click to collapse
tried all that every forum every link i have tried for note 4 firmware fails. Even the links on this forum dont work for me i get to 1.7gb of 1.8 gb then it fails or what opens up is not the file i am supposed to see but a load of jargon
technophobe321 said:
tried all that every forum every link i have tried for note 4 firmware fails. Even the links on this forum dont work for me i get to 1.7gb of 1.8 gb then it fails or what opens up is not the file i am supposed to see but a load of jargon
Click to expand...
Click to collapse
I will make this as easy as possible to understand. First grab your phone box that you got when you bought Note 4. You should find somewhere in that box your phone variant. You can see several different variants below. Try and search for this kind of numbers somewhere in or on your box.
The image:
{
"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"
}
Poslano z mojega LG-D722 z uporabo Tapatalk
As per starter thread spec is on the original msg
Tech spec of the Phone
SM-N910F Android Version 5.0.1 Baseband Version N910FXXU1BOC4 build number N910FXXU1BOC5
technophobe321 said:
Tech spec of the Phone
SM-N910F Android Version 5.0.1 Baseband Version N910FXXU1BOC4 build number N910FXXU1BOC5
Click to expand...
Click to collapse
Ok. The last thing we need is your newtork operator ( example: Vodafone, Sprint, Verizon...)
Poslano z mojega LG-D722 z uporabo Tapatalk
why, tyo help you I can access remotly with teamviwer or beanywhere to you computer when I am at house. But you need to check Model bewind the battery, and tell me what country\operature you have bought this phone
Mega links works fine for you??? (speedy?)
NemboSix said:
Ok. The last thing we need is your newtork operator ( example: Vodafone, Sprint, Verizon...)
Poslano z mojega LG-D722 z uporabo Tapatalk
Click to expand...
Click to collapse
Install simple Samsung☆Phone Info☆ from Play Store...Post here screenshots from CSC code and some1 will be give u working link from sammobile
technophobe321 said:
Tech spec of the Phone
SM-N910F Android Version 5.0.1 Baseband Version N910FXXU1BOC4 build number N910FXXU1BOC5
Click to expand...
Click to collapse
You can flash stock firmware as said above and unroot phone but remember that your warranty is forever void
thay said:
You can flash stock firmware as said above and unroot phone but remember that your warranty is forever void
Click to expand...
Click to collapse
Where is the op from? Not so in the EU...
EclipseX said:
why, tyo help you I can access remotly with teamviwer or beanywhere to you computer when I am at house. But you need to check Model bewind the battery, and tell me what country\operature you have bought this phone
Mega links works fine for you??? (speedy?)
Click to expand...
Click to collapse
sorry guys been off on a 3 week holiday and couldnt access my account whilst away. Still have the phone obviously and the same issues.
The phone is unlocked to all networks however i can put an EE sim card in the phone if needs be.
Unroot failed
so i finally managed to find a download for my note 4 that wasnt just jargon. Loaded to ODIN hit the start button all looked good and then i get a fail at the end.
no stuck on the downloading screen with a message:
Volume size is too big
ODIN: Invalid ext4.img
This is what is in the ODIN message if this helps you at all :
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910FXXU1BOC5_N910FEUR1BOD2_N910FXXU1BOC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Have reloaded the original root file and phone is now operational again but i need to reload original firmware asap as am sending phone back or i need to brick the phone. please help
still no luck
still cant find a valid file and have now downloaded over 50gb of rubbish. Does anyone have access to the file i require or the phone is just going in the bin...