Database Develop

boot looping when I update with Viperboy 1.1.0

I am rooted on a Sprint One and had stock HTC. Then downloaded the Viperrom 1.0.4 and had no trouble get it on, did not loose any of my settings or folders. Now when I download and try to run the viper 1.1.0 zip, it does the install and starts up shows my walpaper and icons appropriately, then crashes and constant reboots to the same point. Able to get on to recovery and reinstall the back up i had made with no rpoblems.
What do I need to do? If I wipe, what do i wipe? Have TWRP.
Will I loose all my settings and data?
Please help

Under advanced wipe select the first 4(dalvik,cache,system,data).
Then reflash the Rom.
You will lose settings.

Thanks, will try that in the morning.
Is there anyway we can save settings and restore them after upgrades?

aviatordoc said:
Thanks, will try that in the morning.
Is there anyway we can save settings and restore them after upgrades?
Click to expand...
Click to collapse
Htcs built in backup through dropbox works very well. It restores apps, settings, homescreens. About the only two things it doesnt restore are accounts, autorotate and lockscreen password
Sent from my HTCONE using xda app-developers app

youkosnake said:
Htcs built in backup through dropbox works very well. It restores apps, settings, homescreens. About the only two things it doesnt restore are accounts, autorotate and lockscreen password
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
yes but i also disables google backup

I fond HTCs better than googles. The only thing I manually use google sync for is contacts. And thats just force of habit.
Sent from my HTCONE using xda app-developers app

youkosnake said:
I fond HTCs better than googles. The only thing I manually use google sync for is contacts. And thats just force of habit.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
good to know, thanks

aviatordoc said:
I am rooted on a Sprint One and had stock HTC. Then downloaded the Viperrom 1.0.4 and had no trouble get it on, did not loose any of my settings or folders. Now when I download and try to run the viper 1.1.0 zip, it does the install and starts up shows my walpaper and icons appropriately, then crashes and constant reboots to the same point. Able to get on to recovery and reinstall the back up i had made with no rpoblems.
What do I need to do? If I wipe, what do i wipe? Have TWRP.
Will I loose all my settings and data?
Please help
Click to expand...
Click to collapse
Need to wipe before installing. In TWRP, hit Wipe>Swipe to wipe
gmentals said:
Under advanced wipe select the first 4(dalvik,cache,system,data).
Then reflash the Rom.
You will lose settings.
Click to expand...
Click to collapse
Do NOT do this. It will wipe everything including your internal SD card
Sent from my HTCONE using Tapatalk 2

I did the same thing as you. Mine got caught in a bootloop, I couldn't get the damn thing to force restart either. The bottom home & back key just kept flashing no matter how long I held it. I had to wait forever for the battery to die. I think something might be wrong with the restart fail safe HTC built in. So I relocked it, flashed back to stock, go to sprint store of course it reboots perfect every time. The people at the store are morons I hate going there. The guy says to me you just hold it down and the restart menu will come up. I'm like if the phone is frozen that doesn't work. None the less I don't expect them to replace something that is working. So I re-unlocked, cleared everything and installed latest build fresh works great haven't had any issue. I didn't back up either so I had to re set everything up which takes forever. I'm not a fan of restoring backups anyway as it can cause issues. I will be doing a nandroid next time and be more careful with dirty flashing. I always dirty flashed on MeanBean on my LTE without issues and Mike made it very clear when dirty update was not advised. In my opinion they shouldn't release a major update that will bootloop a phone over goo manger. It's still my fault but I didn't think twice about it when I tried to update viper. It still pisses me off that I have to fight with it to get the phone to reboot, the entire point of a fail safe is incase something goes wrong. It's the first time I have ever bootlooped a phone.

Do NOT do this. It will wipe everything including your internal SD card
Sent from my HTCONE using Tapatalk 2[/QUOTE]
I do this everytime I flash a new Rom and it doesn't wipe my internal SD...

Thanks all, I am just where I was. so many opinions and would like to have a concensus.

It won't wipe internal unless you specifically check it in advanced. Never wipe internal, but davlic, cache, data and system are fine and constitutes a full wipe..you should always wipe that way when trying different roms or going to a new base. Or use a superwipe script to make things easier.
Sent from my HTCONE using xda premium
---------- Post added at 12:28 PM ---------- Previous post was at 12:27 PM ----------
http://forum.xda-developers.com/showthread.php?t=2237021
[TOOL]smw6180 Superwipe
Sent from my HTCONE using xda premium

Mrlakadaddy is absolutely correct.
Consensus achieved
Sent from my EVO using xda premium

OK here it goes. Went to advanced, wiped all except internal. will see how it goes.

scottspa74 said:
Mrlakadaddy is absolutely correct.
Consensus achieved
Sent from my EVO using xda premium
Click to expand...
Click to collapse
What's up Scott did you get a One?
Sent from my HTCONE using Tapatalk 2

All went well and am on the new base. Only, I lost all my settings and it is such a pain to recreate all the screens, shortcuts, sign ons and accounts...
Thanks to all.

same problem
ive had the same problem, i actually had to use the ruu to get back to stock, unlocked it again s-off rooted and no matter what i do everytime i install any custom rom it goes into bootloop. ive tried every rom on here i cant even get viperrom to fully boot up. looking thru all the forums nobody has a clear answer as to why this is happening.

im stuck in boot loop after the viper rom and i just got it yesterday .. i dont know what to do at this point . when it does boot it ask me for the wifi login and fails says poor connection when its right next to me

Boot Loop
I'm also stuck in boot loop. I've done research and tried all kinds of stuff with no luck. This is what I get...
Phone boots
I get the notification bar and a black screen
Can't do anything with that.
After about a minute, it reboots.
Can anyone help with this? I have the 1.31 version. Clearing cache/data/delvik does nothing for me.
Can someone help me get it back to stock, or at least usable?
Thanks in advance.

erickr5 said:
ive had the same problem, i actually had to use the ruu to get back to stock, unlocked it again s-off rooted and no matter what i do everytime i install any custom rom it goes into bootloop. ive tried every rom on here i cant even get viperrom to fully boot up. looking thru all the forums nobody has a clear answer as to why this is happening.
Click to expand...
Click to collapse
Are you wiping before you flash a new rom?
matt406regal said:
im stuck in boot loop after the viper rom and i just got it yesterday .. i dont know what to do at this point . when it does boot it ask me for the wifi login and fails says poor connection when its right next to me
Click to expand...
Click to collapse
Same question are you wiping before flashing a new rom?
huebenthal said:
I'm also stuck in boot loop. I've done research and tried all kinds of stuff with no luck. This is what I get...
Phone boots
I get the notification bar and a black screen
Can't do anything with that.
After about a minute, it reboots.
Can anyone help with this? I have the 1.31 version. Clearing cache/data/delvik does nothing for me.
Can someone help me get it back to stock, or at least usable?
Thanks in advance.
Click to expand...
Click to collapse
RUU following this guide. http://forum.xda-developers.com/showthread.php?t=2390821
All of you should really start your own topic so people see it and help you.

[Q] Help with unroot and removing "Custom" and unlocked padlock

I purchased the AT&T version of the Galaxy Note 3 a little less than a week ago and, to be honest, I'm not really keen on it. There are a number of reasons, but what it boils down to is that I just don't think I like it all that much. I've already sold my Galaxy Note 2, so I'll have to figure out what I'm going to do about a cell phone, but that's something beyond the scope of this particular posting. What I need help with is how to unroot this device. I used the Root De La Vega procedure very shortly after it came out and it worked like a charm. I noted that when the phone boots up, there is the word "Custom" and an unlocked padlock. How do I get this AT&T model of the Galaxy Note 3 back to the condition, more or less, of when I bought it about a week ago so that I won't have any issues getting the refund processed? I've heard some people requesting help with unrooting and they've been told to use the unroot in SuperUser. Will this get rid of the "Custom" wording on boot-up AND the unlocked padlock? If not, is there a way to get this back to the way it was or am I just out of luck since I only have about another week to return this device. Obviously, if I'm stuck, I'm stuck and I'll find a way to live with it. Who knows...I might actually get to liking it down the road when some of the quirks have been worked out. However, if there's a way to sort all of this out in a timely manner where there's no muss or fuss, that would be the ideal solution. Any help would be greatly appreciated.

KennyXL said:
I purchased the AT&T version of the Galaxy Note 3 a little less than a week ago and, to be honest, I'm not really keen on it. There are a number of reasons, but what it boils down to is that I just don't think I like it all that much. I've already sold my Galaxy Note 2, so I'll have to figure out what I'm going to do about a cell phone, but that's something beyond the scope of this particular posting. What I need help with is how to unroot this device. I used the Root De La Vega procedure very shortly after it came out and it worked like a charm. I noted that when the phone boots up, there is the word "Custom" and an unlocked padlock. How do I get this AT&T model of the Galaxy Note 3 back to the condition, more or less, of when I bought it about a week ago so that I won't have any issues getting the refund processed? I've heard some people requesting help with unrooting and they've been told to use the unroot in SuperUser. Will this get rid of the "Custom" wording on boot-up AND the unlocked padlock? If not, is there a way to get this back to the way it was or am I just out of luck since I only have about another week to return this device. Obviously, if I'm stuck, I'm stuck and I'll find a way to live with it. Who knows...I might actually get to liking it down the road when some of the quirks have been worked out. However, if there's a way to sort all of this out in a timely manner where there's no muss or fuss, that would be the ideal solution. Any help would be greatly appreciated.
Click to expand...
Click to collapse
I'm not super familiar with the unrooting process, but try to unroot using SuperSU and reboot a couple of times to see if it goes away. If that doesn't work then flash the original firmware with odin and that should do it. Pretty easy to do from what I understand.

agent929 said:
I'm not super familiar with the unrooting process, but try to unroot using SuperSU and reboot a couple of times to see if it goes away. If that doesn't work then flash the original firmware with odin and that should do it. Pretty easy to do from what I understand.
Click to expand...
Click to collapse
Perhaps this is showing my ignorance, but since the AT&T Galaxy Note 3 has a locked bootloader (which, as of yet, has not been unlocked), would that prevent Odin from flashing a new image? If I don't need an unlocked bootloader to flash with Odin, do you know where I might find the original image that came with my phone from AT&T in a format that Odin can flash? I haven't tried the SuperSU yet since I want all my options readily available so that if one fails, I can move on to the next one.

KennyXL said:
Perhaps this is showing my ignorance, but since the AT&T Galaxy Note 3 has a locked bootloader (which, as of yet, has not been unlocked), would that prevent Odin from flashing a new image? If I don't need an unlocked bootloader to flash with Odin, do you know where I might find the original image that came with my phone from AT&T in a format that Odin can flash? I haven't tried the SuperSU yet since I want all my options readily available so that if one fails, I can move on to the next one.
Click to expand...
Click to collapse
To my understanding you can flash anything with Odin on a locked bootloader phone that is "signed". If you give me a few minutes I'll help you look for the original odin file to flash.

agent929 said:
I'm not super familiar with the unrooting process, but try to unroot using SuperSU and reboot a couple of times to see if it goes away. If that doesn't work then flash the original firmware with odin and that should do it. Pretty easy to do from what I understand.
Click to expand...
Click to collapse
agent929 said:
To my understanding you can flash anything with Odin on a locked bootloader phone that is "signed". If you give me a few minutes I'll help you look for the original odin file to flash.
Click to expand...
Click to collapse
I really appreciate your help. Every time I've used Odin in the past has involved a phone with a non-locked bootloader (as far as I know) so this is new territory for me.

KennyXL said:
I really appreciate your help. Every time I've used Odin in the past has involved a phone with a non-locked bootloader (as far as I know) so this is new territory for me.
Click to expand...
Click to collapse
Not a problem. I've been looking for that odin file with no luck. I would PM designgears and ask him if he can provide a link for it because you couldn't find it.

agent929 said:
Not a problem. I've been looking for that odin file with no luck. I would PM designgears and ask him if he can provide a link for it because you couldn't find it.
Click to expand...
Click to collapse
Thanks. I'll give that a try.

Use the same file that u used to root. The one with the one click. After it pass, you're back to stock. i just did it yesterday.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

If you looked at the root thread you'd see directions to unroot right there.
Sent from my SAMSUNG-SM-N900A using xda app-developers app

panday74 said:
Use the same file that u used to root. The one with the one click. After it pass, you're back to stock. i just did it yesterday.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Zach Alt said:
If you looked at the root thread you'd see directions to unroot right there.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
What they said
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4

panday74 said:
Use the same file that u used to root. The one with the one click. After it pass, you're back to stock. i just did it yesterday.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried the SuperSU full unroot method - didn't remove the padlock, flashed the one click - didn't remove it, and just flashed the second (for funsies) and that didn't help (probably shouldn't have expected it to).
I'm returning my note and can't get rid of the lock. Will PM Designgears I guess

Did you restart it a few times? Also a factory reset?
Sent from my SAMSUNG-SM-N900A using Tapatalk 5

seanu13 said:
I tried the SuperSU full unroot method - didn't remove the padlock, flashed the one click - didn't remove it, and just flashed the second (for funsies) and that didn't help (probably shouldn't have expected it to).
I'm returning my note and can't get rid of the lock. Will PM Designgears I guess
Click to expand...
Click to collapse
I was kinda wondering how to remove the padlock also. I have read that some people that haven't even rooted have the padlock on boot up also??? I read somewhere about triangle away working, have you tried that?

agent929 said:
Did you restart it a few times? Also a factory reset?
Sent from my SAMSUNG-SM-N900A using Tapatalk 5
Click to expand...
Click to collapse
yes to both (restarted 5 times). since i was already so far into the root process, I added the files to the sdcards that are in the root steps, and the lock went away. Then I finished rooting.
went back and did one click again and still had the lock after rebooting 5 times. Thought about how it went away after adding the files so I skipped through the phone setup, enabled USB debugging again and added a dummy file to the sd card (a .csv I had on my desktop) and then removed it. Rebooted, and the lock was gone.

I'd use the padlock hack in Wanum and hide the root apps via Nova Launcher just to stick it to ATT and return it rooted.
Sent from my SAMSUNG-SM-N900A using xda premium

Omg, just reflash the stock rom from the package. Says so in the instructions.
READ!
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

Jammol said:
Omg, just reflash the stock rom from the package. Says so in the instructions.
READ!
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you READ, you will see he already did that.

agent929 said:
If you READ, you will see he already did that.
Click to expand...
Click to collapse
The last post that was here when I posted was yours. That's why I posted for him to Read the instructions.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

Ok well here's what I did and the padlock is gone.
Factory reset on the phone
Phone rebooted and I removed the super su app using the setting in the su app.
Then flashed the one click 9 tar
phone reboots on its own after flashing, icon was still there
rebooted the phone twice and the padlock was gone
Not sure if I just got lucky or what lol

Jammol said:
The last post that was here when I posted was yours. That's why I posted for him to Read the instructions.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Got ya..tapatalk has been mean to me too lol
---------- Post added at 10:26 AM ---------- Previous post was at 10:25 AM ----------
Quickvic30 said:
Ok well here's what I did and the padlock is gone.
Factory reset on the phone
Phone rebooted and I removed the super su app using the setting in the su app.
Then flashed the one click 9 tar
phone reboots on its own after flashing, icon was still there
rebooted the phone twice and the padlock was gone
Not sure if I just got lucky or what lol
Click to expand...
Click to collapse
I know you have to reboot a few times to set the status somehow, iB4STiD explained it in one of his post before.

Has anyone else gotten this while rooting?

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

[Q] Help Re-Rooting after OTA Update

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.

[Q] Can't get rid of "Custom" boot screen.

I am trying to get my device back to as close to stock as possible. I have played with Root and Wanam Exposed.
I had a weird issue with force closes and could not figure it out so I wiped the device using the factory reset option. Even after that I have FC's with the health app. (no biggie there). The odd thing is that I still have the "CUSTOM" logo on the boot screen that I cant seem to get rid of.
I did a quick search on a bone stock ROM for NC2 KK but have come up empty.
I am currently looking at the Download Screen "ODIN MODE" and the Current Binary is "Samsung Official" System Status "Official" Knox Lock reads 0x0, so I have not tripped knox either.
Kinda baffled here and I seem to be coming up empty handed on all my searches.
Any one got any ideas?

Hoyt Thompson said:
I am trying to get my device back to as close to stock as possible. I have played with Root and Wanam Exposed.
I had a weird issue with force closes and could not figure it out so I wiped the device using the factory reset option. Even after that I have FC's with the health app. (no biggie there). The odd thing is that I still have the "CUSTOM" logo on the boot screen that I cant seem to get rid of.
I did a quick search on a bone stock ROM for NC2 KK but have come up empty.
I am currently looking at the Download Screen "ODIN MODE" and the Current Binary is "Samsung Official" System Status "Official" Knox Lock reads 0x0, so I have not tripped knox either.
Kinda baffled here and I seem to be coming up empty handed on all my searches.
Any one got any ideas?
Click to expand...
Click to collapse
You're on nc2? Pls post your about device info so we can help out.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

posersk8r said:
You're on nc2? Pls post your about device info so we can help out.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not sure what all you need posted....
It is a 900a AT&T Note 3 running KK 4.4.2 NC2 rom.
Rooted via towel root
Tweaked a bit using Exposed Framework and Wanam.
Also jave the latest Safestrap for making nandroids.
HAVE NOT tried to do a custom ROM yet.
What else would you like?

Hoyt Thompson said:
Not sure what all you need posted....
It is a 900a AT&T Note 3 running KK 4.4.2 NC2 rom.
Rooted via towel root
Tweaked a bit using Exposed Framework and Wanam.
Also jave the latest Safestrap for making nandroids.
HAVE NOT tried to do a custom ROM yet.
What else would you like?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=51572014 just in case you f'ed up this will get you back to official nc2. Check out the thread man. As for now I would uninstall all my root apps, delete them then full unroot with supersu so you wouldnt see that custom boot anymore( takes a couple of reboots)
Sent from my GT-I9300 using XDA Premium 4 mobile app

posersk8r said:
http://forum.xda-developers.com/showthread.php?p=51572014 just in case you f'ed up this will get you back to official nc2. Check out the thread man. As for now I would uninstall all my root apps, delete them then full unroot with supersu so you wouldnt see that custom boot anymore( takes a couple of reboots)
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah I read that but their where a few comments made to to make me think that thos was not for those already on NC2. Maybe I read to much into it?
Thanks for your help.

Hoyt Thompson said:
Yeah I read that but their where a few comments made to to make me think that thos was not for those already on NC2. Maybe I read to much into it?
Thanks for your help.
Click to expand...
Click to collapse
The op warned those who are still on 4.3 that if they used the ver 3 mlg with the nc2 bootloader they cannot go back to jb. But to those of us who already are locked to nc2 we could recover from a bootloop or restore to factory for warranty purposes or just want to go back to stock. Read up on that carefully very very useful if you like to play with your phone.
Sent from my GT-I9300 using XDA Premium 4 mobile app

Hoyt Thompson said:
I am trying to get my device back to as close to stock as possible. I have played with Root and Wanam Exposed.
I had a weird issue with force closes and could not figure it out so I wiped the device using the factory reset option. Even after that I have FC's with the health app. (no biggie there). The odd thing is that I still have the "CUSTOM" logo on the boot screen that I cant seem to get rid of.
I did a quick search on a bone stock ROM for NC2 KK but have come up empty.
I am currently looking at the Download Screen "ODIN MODE" and the Current Binary is "Samsung Official" System Status "Official" Knox Lock reads 0x0, so I have not tripped knox either.
Kinda baffled here and I seem to be coming up empty handed on all my searches.
Any one got any ideas?
Click to expand...
Click to collapse
Visit my thread fixes for everyone and see if it can help you. I got something for you there