Bought my Note, it did a update not to long after. Rooted couple weeks later, phone started to freeze few times a week. Tried to remove root, failed to do so. Did a complete phone wipe, phone still rooted, tried to unroot again, no avail. Now the phone tells me to update over wifi, it starts the also fails. Tried to flash with KitKat os using Odin 3.09. It also failed.
I've tried a few different ways of doing these procedures but nothing is working. I just want to start my phone over from scratch so it will hopefully stop freezing and restarting.
Use the restore to MJ5 thread in the general section. Then update.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Thanks, I'll try it. Can you tell me what MJ5 is?
Firemoon380 said:
Thanks, I'll try it. Can you tell me what MJ5 is?
Click to expand...
Click to collapse
MJ5 is the last 3 characters in the software version. Under settings-general-about device you have a build number. The latest build is N900AUCUBNB4. Otherwise known as NB4. The previous build was N900AUCUBMJ5. So you can see it's easier calling it MJ5.
That makes sense, do you know if it will make a difference, my phone is MJ5..
just follow this thread and you just like out of the box if you dont do the last step which it rooting again
http://forum.xda-developers.com/showthread.php?t=2559715
Related
I used Super One Click to root my phone a few months ago, only to remove most of the bloatware that came on the phone. My phone now keeps trying to update to the new software, usually only once every 24 hours, but the past week, a few days it has automatically tried updating several times throughout the day. Very frustrating.
Obviously it won't update being rooted. However, I removed the bloatware, so I don't care that it is rooted anymore. I figure I can unroot it and then get the update to work. However, using Super One Click again, it won't unroot. It gets the error "Device does not have Superuser!" I can then proceed to root it with SOC and have it be successful, and try again and get the same error. Any ideas?
And I guess, will unrooting allow me to successfully update it anyways? Thanks!
The phone should update if it is rooted. It will not update if you have CWM installed. You will also get all that lovely bloatware installed back during the update.
Your best bet is to get the lgpnst and v8 tot and update manually then root that and remove the bloatware again.
Thanks for the help. I'm very new to this, so I don't really know what you're talking about haha. I see some stuff on tot, but what is the lgpnst? If you could link to that and the v8 tot you are talking about and maybe how to use those, that would be great.
joshw2011 said:
Thanks for the help. I'm very new to this, so I don't really know what you're talking about haha. I see some stuff on tot, but what is the lgpnst? If you could link to that and the v8 tot you are talking about and maybe how to use those, that would be great.
Click to expand...
Click to collapse
Look in the development section
Sent from my VS910 4G using xda premium
Hey guys. I ran into some trouble trying to root my note 3 and got this message. Now the phone won't turn on our connect to kies to try to repair it. I have the Samsung drivers installed and I believe I followed the directions closely. Can any of you tell me how to get back to factory settings or all the way through the root process. I'm stuck at this screen for now. Any help would be awesome.
Sent from my Nexus 7 using xda app-developers
Try using the one click oding to get back to the stock firmware. Put the phone in download mode and flash the first step of the root procedure and then stop and make sure your phone will work in stock form first before you try rooting it again.
Quickvic30 said:
Try using the one click oding to get back to the stock firmware. Put the phone in download mode and flash the first step of the root procedure and then stop and make sure your phone will work in stock form first before you try rooting it again.
Click to expand...
Click to collapse
Instead of Pass in a green box, I get Failed in a red box and the progress bar on the phone stops
That's not good, maybe try a new download. Which firmware are you flashing? MI1 or MI9?
That's actually what happened when I tried to root. It would sit forever and fail due to a timeout. What I did is after the failure..I left the phone in dl mode and connected and closed the odin..then relaunched odin and it worked the second time. That's my experience and your mileage may vary..
Same thing!
xavier6303 said:
That's actually what happened when I tried to root. It would sit forever and fail due to a timeout. What I did is after the failure..I left the phone in dl mode and connected and closed the odin..then relaunched odin and it worked the second time. That's my experience and your mileage may vary..
Click to expand...
Click to collapse
The exact same thing happened to me... I tried to install Kies 3 and add the drivers but to no avail. So from there on I just closed everything. Disconnected my note 3, reconnected it, and ran odin once more. It immeadiately passed and rooted my phone.
I have seen that in the past it is the sign of a brick you definitely have to Odin back to stock to fix that
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Yes it happened to me too. I just figured it was my crappy computer so I continued to try and after the 4th try I was able to achieve root status. Like a previous commenter suggested, it's a timed out issue.
Yea. I must have tried a dozen times a dozen different ways and I was stuck. I just said eff it and got a new phone. Debating if I want to try again, but I don't feel like potentially going thru the same heart ache. Really the only reason I care to root this phone is to get rid of those damn bloat ware apps; especially My Magazine.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
alpinesun said:
Instead of Pass in a green box, I get Failed in a red box and the progress bar on the phone stops
Click to expand...
Click to collapse
It was MI9
Sent from my SAMSUNG-SM-N900A using xda app-developers app
alpinesun said:
It was MI9
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Just went thru this on my Note 3 - chances are youre using a vm on a mac arent you?
Make sure you use a dedicated *windows* machine and not a vm (or at lest not a fusion VM) That was my issue, I havent tried parallels. I grabbed a dedicated win 7 machine and it works perfectly.
I was going to return it of that failed, which luckily it didnt.
Cheers
first thing is that im rooted and tried to update the small "pre kitkat" update and all goes good til it gets to 25% then it says update fails and ive searched til i cant go anymore about ways to fix it so my question is that can att force update my phone to kitkat or should i wait til ss is updated for kitkat and if thats the case will i be able to flash in rom slot one and leave the stock slot alone ? im new to all this flashing roms and i dont have a computer so im trying to do everything from my phone any and all suggestions will help.
In on the same boat but I'm not rooted. It goes to 25 and then gets interrupted.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
shane1981 said:
first thing is that im rooted and tried to update the small "pre kitkat" update and all goes good til it gets to 25% then it says update fails and ive searched til i cant go anymore about ways to fix it so my question is that can att force update my phone to kitkat or should i wait til ss is updated for kitkat and if thats the case will i be able to flash in rom slot one and leave the stock slot alone ? im new to all this flashing roms and i dont have a computer so im trying to do everything from my phone any and all suggestions will help.
Click to expand...
Click to collapse
Borrow a friend's pc or go to a library and use Samsung Kies, but you will lose root.
This is most likely because you deleted some the system apps that came with the stock rom..... This is why I never delete them only freeze with titanium backup! This happen to me on Ml9 so I had to restore stock rom reroot put super su in survival mode and then take the update!
Sent from my Note 3 SM-N900A rooted by Designgears
how would i go about doing that?
Sent from my SM-N9005 using xda app-developers app
shane1981 said:
how would i go about doing that?
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Kies is just going to tell you that your firmware is up to date. Either factory reset or you may have to use this http://forum.xda-developers.com/showthread.php?t=2559715 < This is how I had to do it.
So if I am rooted and deleted the AT&T bloat apps, I can't install the KitKit update? What I unroot completely? I know that won't bring back the garbage AT&T apps back, but would I be able to OTA to kitkat then?
MattMJB0188 said:
So if I am rooted and deleted the AT&T bloat apps, I can't install the KitKit update? What I unroot completely? I know that won't bring back the garbage AT&T apps back, but would I be able to OTA to kitkat then?
Click to expand...
Click to collapse
You will not be able to ota unless you do a full restore. You also must have att sim card. At&t is just dirty like that.
B_I_N_G_E said:
You will not be able to ota unless you do a full restore. You also must have att sim card. At&t is just dirty like that.
Click to expand...
Click to collapse
Wow. Anyway, I was rooted, but had Wanam installed and successfully updated to Nb4. I had the fake system status set to official. I was alwasy under the impression if it said Official you could update.
And great, because now we all have to follow a really complicated guide to restore back to MJ5 if we want kitkat.
I was rooted on mj5 no wanam or anything and my phone update to nb4
It didn't even ask.
What you probably did was delete the att update software so now it's not even looking.
Sent from my XT907 using xda app-developers app
I don't think being rooted affects your updating. I have read many people accidentally updating and loosing their root. If you couldn't update with root, people wouldn't freeze at&t update.
ive tried unrooting factory reset andthe only thing i can think of is that ive deleted something . i guess the lesson learned is juat freeze apps instead of deleting them
Sent from my SM-N9005 using xda app-developers app
hey guys i tried searching for answers. but had no success. i have a note 3 that was rooted with kingo. AT&T automatically installed an OTA update and of course it un rooted my phone. i still get the custom boot screen as well as still have safestrap on my device. my question is how do i reroot my device? ive tried kingo again and it fails after rebootong the phone 5 or 6 times. im still running 4.3 build is JSS15J.N900AUCUBNB4
i know a little on some things but im not as technical as most of you. but any help would be greatly appreciated.
Survivor058 said:
hey guys i tried searching for answers. but had no success. i have a note 3 that was rooted with kingo. AT&T automatically installed an OTA update and of course it un rooted my phone. i still get the custom boot screen as well as still have safestrap on my device. my question is how do i reroot my device? ive tried kingo again and it fails after rebootong the phone 5 or 6 times. im still running 4.3 build is JSS15J.N900AUCUBNB4
i know a little on some things but im not as technical as most of you. but any help would be greatly appreciated.
Click to expand...
Click to collapse
What version of Kingo did you try? Use 1.1.5 or 1.1.8. People have had success with that. 1.1.8 worked for me. Just Google around and you will find the download on the net somewhere.
theorioles33 said:
What version of Kingo did you try? Use 1.1.5 or 1.1.8. People have had success with that. 1.1.8 worked for me. Just Google around and you will find the download on the net somewhere.
Click to expand...
Click to collapse
it was 1.2.0 ill try an older version
In case you have trouble finding a copy
https://mega.co.nz/#!AxdHUCCQ!86DzctSWlXK4VfbInPYBgC_4QYAM2wUR8cewrflAyk0
theorioles33 said:
In case you have trouble finding a copy
unfortunately that did not work. the root failed. that was version 1.1.5, last night i tried 1.1.8 failed and tried the latest 1.2.0 with no success. would you recommend something else? i did try theese root methods with the sd card inserted im not sure if that is a no no or not
Click to expand...
Click to collapse
I'm at a loss. I had my SD card in by the way. Maybe someone else will have some ideas.
Sent from my SAMSUNG-SM-N900A using Tapatalk
theorioles33 said:
I'm at a loss. I had my SD card in by the way. Maybe someone else will have some ideas.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
that sucks. factory reset? ill most likely still have the issue but maybe not. isnt there a way to completely wipe the phone from the boot screen? id rather not if i dont have to.
You can try a factory reset and then root. If not there is a thread in the general section to go back to stock. Works great. I used it.
Sent from my SAMSUNG-SM-N900A using Tapatalk
theorioles33 said:
You can try a factory reset and then root. If not there is a thread in the general section to go back to stock. Works great. I used it.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
but arent i technically back to stock? since i dont have root access? this is very confusing to me. if my carrier didnt push that update i wouldnt be in this boat
You are but we can't figure out why you can't root when others in your situation can. There is Kingo thread you can check out. Maybe you can find some answers there.
Sent from my SAMSUNG-SM-N900A using Tapatalk
anyone have any suggestions?? 139 views in less than an hour someone has got to know something lol
Survivor058 said:
anyone have any suggestions?? 139 views in less than an hour someone has got to know something lol
Click to expand...
Click to collapse
Factory Reset after the update to NB4, also go to recovery wipe cache, then try the 1.18, during the rooting process, look your phone screen, you need to click accept something twice,
I don't know how it all works terribly well but you said you still have Safestrap? Can you still install ROMs and can they have root?
Also, for when you eventually do get it working again. I recommend freezing the ATT updater. It can be awful when it eventually FORCES an update.
I got a free app called App Quarantine and froze "AT&T Software Update".
coolmingli said:
Factory Reset after the update to NB4, also go to recovery wipe cache, then try the 1.18, during the rooting process, look your phone screen, you need to click accept something twice,
Click to expand...
Click to collapse
ok yea this is all french to me. you want me to factory reset? im not sure what the NB4 is?. and i thing i know how to wipe the cache.
Gary3 said:
I don't know how it all works terribly well but you said you still have Safestrap? Can you still install ROMs and can they have root?
Also, for when you eventually do get it working again. I recommend freezing the ATT updater. It can be awful when it eventually FORCES an update.
I got a free app called App Quarantine and froze "AT&T Software Update".
Click to expand...
Click to collapse
safestrap is on my phone but it cant be removed and just says that the phone isnt properly rooted. so no i cannot install roms and i will make sure that once i resolve this ill freezr that app
sorry for the delay guys im back at this again. i do very much appreciate all who are trying to offer assistance
ok guys so ive wiped the cache. and have done the factory reset. kingo 1.1.5 and 1.1.8 both have failed...... what is going on here maybe someone can skype with me the steps to completely flash my phone to the day i got it i see the thread but im scared ****less to try it lol
You will just have to follow the restore to MJ5 thread. The instructions are simple and very easy to follow. Go slow and follow them to the T.
What they do not mention however is do not use a 3.0 USB port. Only 2.0 will work.
Just follow that.
It is literally impossible to brick this phone to the point of it being unrecoverable. There is a tutorial to restore from hard bricks without J-Tag.
Sent from my SM-N9005A using XDA Premium 4 mobile app
graydiggy said:
You will just have to follow the restore to MJ5 thread. The instructions are simple and very easy to follow. Go slow and follow them to the T.
What they do not mention however is do not use a 3.0 USB port. Only 2.0 will work.
Just follow that.
It is literally impossible to brick this phone to the point of it being unrecoverable. There is a tutorial to restore from hard bricks without J-Tag.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey graydiggy, I did the restore back to MJ5, but can't seem to get the last step for rooting to work. I tried every way with putting the rdlv on internal...unzipped and zipped. I even tried doing the same on the external sd as well. When I reboot supersu doesn't do anything. Any suggestion on how to get the last step to work?
Thanks in advance for your help.
chrispyutec said:
Hey graydiggy, I did the restore back to MJ5, but can't seem to get the last step for rooting to work. I tried every way with putting the rdlv on internal...unzipped and zipped. I even tried doing the same on the external sd as well. When I reboot supersu doesn't do anything. Any suggestion on how to get the last step to work?
Thanks in advance for your help.
Click to expand...
Click to collapse
It has to be unzipped and on the internal. You have to reboot a few times for it to activate. After the first reboot, let the phone sit for a few minutes and then reboot again. You should be good to go after that.
Sent from my SM-N9005A using XDA Premium 4 mobile app
graydiggy said:
It has to be unzipped and on the internal. You have to reboot a few times for it to activate. After the first reboot, let the phone sit for a few minutes and then reboot again. You should be good to go after that.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wow that did the trick!!! Thanks for holding my hand lol. I hit your thanks and I appreciate your help.
Ok, so here's the breakdown:
I was on KK (KNOXRAID 5.1), and wanted to try a different ROM. I always like starting fresh on things, and accidentally went a little too far. I wiped /data, /system/, /cache...everything. So then I lost everything and was always stuck on "No OS installed!". Then I used the guide here: http://forum.xda-developers.com/showthread.php?t=2559715 to kind of restart myself.
That works ok, and now I'm on a rooted stock MJ5. My next thing was to try to get to KK again, and so I used the other guide here: http://forum.xda-developers.com/showthread.php?t=2712039. I've tried this literally about eight times, and every time I end up stuck on the boot / splash screen after finishing every single time. I really have no idea why, as I've followed the instructions exactly.
I've also tried going from a custom ROM, using different USB ports, etc...no luck.
Would someone mind pointing me in the right direction? I want to be on FireNote.
Some details:
Running Windows 8.1 Pro 64-bit
Using OEM cable
I've attached a screenshot of my "About" screen on my current stock rooted MJ5 setup.
Thank you!!
Here you go follow the link. http://forum.xda-developers.com/showthread.php?t=2627234
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
lildoggs said:
Here you go follow the link. http://forum.xda-developers.com/showthread.php?t=2627234
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm afraid I don't follow? Are you saying that there is a post somewhere in the FireNote thread where the solution is mentioned?
Firenote is based on mj5 so no need to go to kk. Just make a slot in ss then flash it there or if you're a bit of an adventurer flash it on stock slot. Just make a backup first.
posersk8r said:
Firenote is based on mj5 so no need to go to kk. Just make a slot in ss then flash it there or if you're a bit of an adventurer flash it on stock slot. Just make a backup first.
Click to expand...
Click to collapse
Yeah...wish I would have realized that obvious fact early on. Only realized a few hours ago.
Apart from all this though, I just tried it on another computer and everything worked great. Don't know what's going on with my laptop, but the desktop worked great. Problem solved.
Thanks anyway everyone!