Root [Sprint] My bootloop problem

[dustwun77]

I started a new thread for my continuing adventures and to keep the other thread on topic, sort of. lol

ovrrdrive asked if it felt good that I had gone ahead and rooted, I answered in the affirmative, and things progressed from there!

Yes indeed!

One note, that Quickboot app that I have used forever. I had it take me to the bootloader.
I could not get out of it without pulling the battery. That was a pain in this otterbox. The plastic shell does not want to come apart!
Saw something somewhere that on some phone without a custom recovery when they used that app to go to the stock recovery, it just went ahead and did a factory reset. Lol.
It works fine to just reboot and shut down though, which I like. 1 button shutdown save wear and tear on hardware button.

Edit: I am going to break out some of the non 1 click root stuff, starting here and moving it to the My Bootloop thread.

 

[ovrrdrive]

I used wanam xposed to geta 4 in 1 reboot menu. It worked great.

I was playing around benchmarking my phone yesterday and at any overclock other than 2.34 it went into a hard lock and I had to do a battery pull to get it back. I had to take the otterbox off 3 times. I finally just gave up. What a pain in the ass!

 

[dustwun77]

Phone is definitely locked in to the otterbox, no doubt!

I've seen that Exposed thing referred to but haven't really tracked down what it was to try to take advantage of it yet.

Until I do actually put a custom recovery on it, I might be in the same boat if I used it Wanam to go to recovery. Not too eager to find out.

I never was big into using adb, though I do have the mini SDK tool set up on my pc. I ought to give it a shot and see what it takes for me to get it to work with this phone.

I have never used that Odin tool, either.

Edit: When I went to use adb, my old tool said a device was there but that it was offline. It showed my HTC right off the bat. A little research found the claim that I should update the mini sdk. Fortunately, I remembered that Early had us update the links to that and sure enough, using the link I found here, http://androidforums.com/faqs/443072-adb-guide.html I got the new tool and it works correctly!

 

[ovrrdrive]

Phone is definitely locked in to the otterbox, no doubt!

I've seen that Exposed thing referred to but haven't really tracked down what it was to try to take advantage of it yet.

Until I do actually put a custom recovery on it, I might be in the same boat if I used it Wanam to go to recovery. Not too eager to find out.

I never was big into using adb, though I do have the mini SDK tool set up on my pc. I ought to give it a shot and see what it takes for me to get it to work with this phone.

I have never used that Odin tool, either.

Edit: When I went to use adb, my old tool said a device was there but that it was offline. It showed my HTC right off the bat. A little research found the claim that I should update the mini sdk. Fortunately, I remembered that Early had us update the links to that and sure enough, using the link I found here, http://androidforums.com/faqs/443072-adb-guide.html I got the new tool and it works correctly!

Wanam gives you a lot of options that are typically baked into custom roms that you can apply to the stock rom. This way there isn't as big of a need to go full custom. For people that want to do simple things like get a 4 in 1 menu or a custom battery gauge it's perfect for that. There is a lengthy thread on xda for it, but essentially it's in the market for free. You install it and it downloads the xposed framework on the first run and then you open it up and start poking. Everything I have tried to do on the N3 has worked. Of course the deeper you poke the more you risk something getting screwed up. Without a custom recovery and a backup you'll be forced to use odin to flash the phone back to stock, which is also painless I might add. Painless that is as long as it works. lol

I'm also new to everything samsung and thus far it has been easy for me to adapt. I've been using the odin version that came with cf root as I figure if it is good enough for him its good enough for me. You just plug the phone in and hit start and it does its thing. I had to odin back to stock to get the MJ4 update and then reroot. It went off without a hitch.

 

[dustwun77]

Wow, boot loop city. My phone does NOT like the exposed framework, Wanam combination! Was making me want that Nandroid even more.

Need to try that script I posted earlier. supposed to be able to back up the system with it too.

Quickboot does the same thing to my phone. It will eventually settle down but starts and restarts a number of times before it settles in.

I don't need that!

 

[ovrrdrive]

You might just be experiencing the same thing a bunch of us are. When i restart my phone it always starts up at least twice. Sometimes 3 times before it settles in. I saw a thread of people complaining the same thing that weren't rooted so it looks like it might just be another bug. I restart my phone every morning and like I said, always at least two boots.

 

[dustwun77]

I had not heard of that cool little bug.

I may have had it earlier and not noticed because I usually start it up and leave it without watching it. Let me check.

Yep. I still have the problem even with out all of that stuff on the phone.

 

[ovrrdrive]

I had not heard of that cool little bug.

I may have had it earlier and not noticed because I usually start it up and leave it without watching it. Let me check.

Yep. I still have the problem even with out all of that stuff on the phone.

I hate to bring it up, but I wonder if using wanam xposed caused this bug...

If it did I guess I owe you a beer for suggesting you use it.

I'll try to dig into it deeper later tonight. The thread I saw where it was mentioned only had one other guy in it with the problem so it may not be that wide spread. At least it's just weird behavior and nothing that is a deal breaker. Mine usually just boots twice when i restart it.

 

[dustwun77]

I hate to bring it up, but I wonder if using wanam xposed caused this bug...

If it did I guess I owe you a beer for suggesting you use it.

I'll try to dig into it deeper later tonight. The thread I saw where it was mentioned only had one other guy in it with the problem so it may not be that wide spread. At least it's just weird behavior and nothing that is a deal breaker. Mine usually just boots twice when i restart it.

I read on XDA something about installing the Exposed Framework might cause bootloops, I think. I went into it eyes open.

I'll take the beer anyway though.

Like I said, I may have already had the problem and not even noticed it the way I start the phone at leave it to do it's thing without watching it.

No biggie. I went ahead and reinstalled Exposed and Wanam and have been running with them all day. Didn't make that many mods though.

Still have that Mj4 stock code I can use Odin with if I take the notion.

 

[dustwun77]

I have been a busy boy!

Seeing that my boot loops were not caused by Exposed or Wanam, I went ahead and put them back on the phone.

Quickboot quit working for me as far as one click shut off, reboot, etc, so I tried the 4 in 1 in Wanam that you suggested. It did not work for me either and bootloops were even worse.

Ok, I was not going for that. I loaded Goomanager just to see if TWRP recovery was listed for my phone, it was. I told it to install it. It said it did but it did not reboot. Using the 4 in 1, I tried to get to the recovery I thought I had installed. No joy.

Decided to try out this ODIN thing to get TWRP on the phone. I had the one for rooting with
chainfire's method.

I downloaded the appropriate TWRP and went for it. That was fun.

I finally figured out I was supposed to click in the PDA box and select the TWRP file and that I was supposed to have the phone in download mode, Volume down, Home and Power pressed, before Odin would work. Did I mention that I am a really smart guy, lol ?

Once I did it correctly, it worked fine and fast! Seeing TWRP on my pretty new phone was quite a joy as well!

First thing I did was make a nand. It is a lot faster to make the nand to internal memory than to the sd card, I have subsequently discovered.

Today I went through a bunch of stuff and managed to get the bootloops to quit. Not sure what did it. I got rid of the 4 in 1, kept all my other mods in wanam and the Exposed framework. Got rid of quickboot, seeing as how it isn't working. Made another nand.

Now, I stand on the edge of the unknown, getting ready to flash me my first note 3 rom, after I read up on it a bit, anyway.

Just thought i would share, hopefully somebody gets something from all that.

 

[dustwun77]

I installed freeza's stock rooted mj4 rom and now my Quick boot app works again.

I don't know why I waited so long. Rooted is the way to be!

 

[ovrrdrive]

Were there any other benefits to flashing the freeza rom?

I haven't seen enough of a reason yet to do that but then again I'm not really having any other problems either. I did flash the freeza beast mode kernal for grins and haven't had any issues with it either. I am still on 1.7 though as I saw in 1.8 they had some rebooting problems while plugged into the charger and I reboot every morning while plugged in so I figured I better wait. Now I see they're past that issue but the one I'm using is working so good I haven't felt the urge to mess with it. It's neat to show people you can spin your processor up faster than their home computers. Mine isn't stable enough to bench at anything over 2.34 but I have played games at 2.5 and it is stable enough to do that. The heat comes up quickly when overclocked though so I don't mess with it much. It's just nice knowing I can if I want.

The problem with twrp and goomanager is well documented in the twrp thread at xda. I think the maker is actually not allowing it for now for some reason. I just used odin and followed the same directions I did to do the CF Root and it went right on.

It's such a relief once you get it installed and get a few nands. I was afraid to do anything before I flashed twrp. Now I have restored backups 5 miles out in the gulf while I was fishing. lol

 

[dustwun77]

I definitely agree about the relief of having the nands. I had read that about goo, but since I saw it in there, I thought it was a go.

The main thing for me with his 'stock rooted' rom, was that it put my system back in order. Made my apps work right again and totally rid me of the bootloop on start issue. It would finally start up, but watching it reboot 5 or 6 times first was rough.

I didn't see any other advantage to it though.

I didn't stay on it too long though. Got it all set up and nanded and now I am running his custom 'wizless' rom.

[ROM|MJ4] Galaxy Note fre3 1.38 w/ BeastMode Kernel

Haven't had any issues with it. I already use Nova Prime for my launcher. Had to download a few google apps i use. I haven't overclocked it yet. I wonder how stable my phone would be?

Had to get that comment about fishing in there, huh? Lucky guy!

 

[ovrrdrive]

Did you check your CPU bin?

For those who want to see what CPU BIN you have (the higher the better) run this command, from adb or terminal: cat /sys/kernel/debug/acpuclk/pvs_bin

Post your results and I will try my best to reply to them with information on your particular CPU. The results will be a single number ranging 0-6.

Mine is a 3. I suspected as much because it was a launch phone. Supposedly the higher the better. I couldn't get the command above to work for me in terminal but if you have that problem you can navigate there manually in root explorer and read the file like I did.

Believe it or not people are still fishing down here. The inshore fish I target are hard to find this time of year but I'm thinking about taking up bass fishing. They're supposed to be biting pretty good right now. We pay for this weather in the middle of the summer but it makes up for it in the winter.

 

[dustwun77]

Enjoy. I'm just messing with you. Jealous, is what it is.

Terminal emulator and navigating there both gave me a 1.

a 1? Are you sure 1 isn't best? lol

a 1....

 

[dustwun77]

Not over clocked at all

 

[ovrrdrive]

I went to run antutu last night to show you what you were missing by running the stock kernal and I couldn't even get through a run at the stock clock speeds without crashing. It crashed so hard the 4th time that it went into safe mode and a few of my widgets got blown up.

And yes I had to take the stupid otterbox defender off again to reset it. lol

I might play around with it a little more this weekend. I updated the beastmode kernal to the middle one yesterday before I ran antutu. Maybe I need to try the lowest modified one and see if it will at least get through a benchmark.

 

[dustwun77]

wow.

It seems like this rom comes with a custom kernel. At least by looking at the name of it, 3.4.0-BeastMode+ I put my old paid version of setcpu on it but I just left it running with the settings that the kernel came with.

That is one tight case! I slipped the phone into a different one when I was flashing stuff.

I wonder what is up with your phone?

 

[ovrrdrive]

I think it's probably just time for a full wipe and to start over. I've been playing deerhunter 2014 on my phone and to earn money I've been installing a bunch of crap and uninstalling it. I bet it's all just a little confused now. It's stable as can be in day to day stuff though. It's weird.

I did see one other person complain about antutu crashing and someone told him to clear the data and delete the hidden folder on his sd card that it makes. He said it worked... Next time I feel like taking the case off the phone I'll give it another shot.