Trying to root verizon note 8 - Samsung Galaxy Note 8 Questions and Answers

I am trying to root a verizon note 8. I can get safestrap installed, I can get a factory android installed, but when i try to load a rom into a rom slot it wont boot. it just shows a black screen after the safestrap options. not sure what i am doing wrong.
Are there any roms for specifically the verizon note 8? Or any pre rooted versions i can install through odin? I think Ive tried everything.
Should also say im new to all of this so i need things explained very clearly and easy instructions lol.

Rom slots do not work. What firmware are you on? What bootloader? Need more info not just it doesnt work.[emoji106]
Sent from my SM-N975U using Tapatalk

Not really sure about any of that. I followed these directions https://www.the***********.com/root-galaxy-note-8-snapdragon-n950u/
It boots but its just the stock android. I need to get root somehow. If this wont work ill move on to another phone.

You can't be past bootloader 3. If build number starts with U4 or S4 you cannot root. There is EDL for bootloader 6 but if you have no idea how to even root then there is no way you should mess around with that method. There is no root past revision 3 bootloader.
Sent from my SM-N960U using Tapatalk
---------- Post added at 11:24 PM ---------- Previous post was at 11:15 PM ----------
Do you know what build you are on? That is a good place to start. That is why I asked and you said you have no idea about any of that. Not trying to be a jerk but it will save you a lot of searching and frustration if you knew these basic things before trying to root. Know your build number..bootloader version. Just trying to offer friendly advice as alot of peeps here will have wanted you to know these basic things before they offer up help. If you know these things then I and others can point you in the right direction. Good luck.
Sent from my SM-N960U using Tapatalk

butchieboy said:
You can't be past bootloader 3. If build number starts with U4 or S4 you cannot root. There is EDL for bootloader 6 but if you have no idea how to even root then there is no way you should mess around with that method. There is no root past revision 3 bootloader.
Sent from my SM-N960U using Tapatalk
---------- Post added at 11:24 PM ---------- Previous post was at 11:15 PM ----------
Do you know what build you are on? That is a good place to start. That is why I asked and you said you have no idea about any of that. Not trying to be a jerk but it will save you a lot of searching and frustration if you knew these basic things before trying to root. Know your build number..bootloader version. Just trying to offer friendly advice as alot of peeps here will have wanted you to know these basic things before they offer up help. If you know these things then I and others can point you in the right direction. Good luck.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Im pretty sure im on bootloader 6. I did the EDL stuff, im good with computers, only ever rooted one phone. Like i said i can get safestrap on there but when i have safestrap going it will not load into android. it just black screens.
I followed these directions https://www. the custom droid .com/root-galaxy-note-8-snapdragon-n950u/
But the final product doesnt have the safestrap app installed. I have to load it through odin and then nothing works except safestrap. Like I said, Not really sure what im doing but its a spare phone so im tinkering.
Thanks for the help.

terky69 said:
Im pretty sure im on bootloader 6. I did the EDL stuff, im good with computers, only ever rooted one phone. Like i said i can get safestrap on there but when i have safestrap going it will not load into android. it just black screens.
I followed these directions https://www. the custom droid .com/root-galaxy-note-8-snapdragon-n950u/
But the final product doesnt have the safestrap app installed. I have to load it through odin and then nothing works except safestrap. Like I said, Not really sure what im doing but its a spare phone so im tinkering.
Thanks for the help.
Click to expand...
Click to collapse
Well you're trying to load Android from safe strap and like @butchieboy77 said the rom slots don't work on safe strap yet. Since all you said you were doing is "tinkering" because it's a spare phone we don't have any idea what it is that you're trying to do or what you're asking for? I mean if the rom slots don't work then what else can we do to assist you?

The goal is to get it rooted. But it seems that's not possible right now.

can't not root the latest firmware now??

Got it rooted now. Thanks for the help.

Related

HTC One Bricked?

Ok so I recently rooted my HTC One and I think I might've bricked my phone. I tried out the Renovate ROM (I think it was the latest version) and it didn't work somehow, and my phone was stuck in boot, so I went into recovery, and factory reset but I accidently checked the button for system and then my OS was deleted. To fix that, I adb pushed Insert Coin ROM and flashed that, but when I booted my phone, it started up fine, but then after 10 seconds or so, the phone would just freeze and then reboot. I went back into recovery adb pushed the stock Sprint HTC One ROM and flashed that and the same thing is happening, but this time, when the phone turns on, it just shows a black screen with the notification bar at the top, and I can't use it in any way. It also freezes and reboots after like 10 second.
TL: DR
My Sprint HTC One keeps on freezing then rebooting after ten seconds, no matter what ROM I try.
Thanks in advance.
Yea....you understand you cant install gsm htc one roms. Thats what you did. Go download a ruu and run it while your in bootloader as i see adb is working for you
Sent from my HTCONE using xda premium
---------- Post added at 12:09 PM ---------- Previous post was at 11:57 AM ----------
Also no ur not bricked. A hard brick means the phone cant even power on. Its a brick. Unusable.
Sent from my HTCONE using xda premium
HTC_M7 said:
Yea....you understand you cant install gsm htc one roms. Thats what you did. Go download a ruu and run it while your in bootloader as i see adb is working for you
Sent from my HTCONE using xda premium
---------- Post added at 12:09 PM ---------- Previous post was at 11:57 AM ----------
Also no ur not bricked. A hard brick means the phone cant even power on. Its a brick. Unusable.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
I believe I have done the same thing as I am very new to this. Is there a link or something to find this ruu? and doesn't it need to be a certain one?
Like my phone is a Sprint HTC One. I am stuck in a boot loop and no matter what ROM I try it just keeps rebooting? Please any help would be greatly appreciated!
Check this thread for the RUU and instructions
http://forum.xda-developers.com/showthread.php?t=2250904
Khilbron said:
Check this thread for the RUU and instructions
http://forum.xda-developers.com/showthread.php?t=2250904
Click to expand...
Click to collapse
YESSSS!!!!!! Thank you it worked after following video instructions. Thanks again. You wouldnt know to unlock bootloader again with fast boot would you? Or would I need to follow Dev instructions again?
---------- Post added at 01:42 PM ---------- Previous post was at 01:28 PM ----------
Also what is a gsm htc one rom and how is it different sorry but like i said I am very new to this less than a week so any info I am sucking up like a sponge! Thanks again for your help!
Knixson said:
YESSSS!!!!!! Thank you it worked after following video instructions. Thanks again. You wouldnt know to unlock bootloader again with fast boot would you? Or would I need to follow Dev instructions again?
---------- Post added at 01:42 PM ---------- Previous post was at 01:28 PM ----------
Also what is a gsm htc one rom and how is it different sorry but like i said I am very new to this less than a week so any info I am sucking up like a sponge! Thanks again for your help!
Click to expand...
Click to collapse
fastboot flash unlocktoken Unlock_code.bin
GSM is the AT&T, T-mobile & international models....Sprint & Verizon are CDMA
O.M.J said:
fastboot flash unlocktoken Unlock_code.bin
GSM is the AT&T, T-mobile & international models....Sprint & Verizon are CDMA
Click to expand...
Click to collapse
Thank you! would I also need to install the open recovery twrp to gain root access as well?
Knixson said:
YESSSS!!!!!! Thank you it worked after following video instructions. Thanks again. You wouldnt know to unlock bootloader again with fast boot would you? Or would I need to follow Dev instructions again?
---------- Post added at 01:42 PM ---------- Previous post was at 01:28 PM ----------
Also what is a gsm htc one rom and how is it different sorry but like i said I am very new to this less than a week so any info I am sucking up like a sponge! Thanks again for your help!
Click to expand...
Click to collapse
You need to follow the dev instructions. If I were you though, I wouldn't do anything more until you understand some of the risks involved. A phone is a really, really inconvenient thing to have incapacitated when you're learning how to flash. For one, your device wasn't bricked (completely nonresponsive to input); for another, dev instructions are going to tell you to use fastboot (or a toolkit that runs fastboot for you).
Before you start again, you should learn how to use fastboot at the very least, and if you can, adb install/sideload (although it seems you tried that based on the OP). fastboot is often the only thing working if a flash goes awry.
A ROM is a ROM, no matter what device it's for. GSM/CDMA are separate network technologies that power your phone. In the U.S., Sprint and Verizon are the major CDMA carriers, while AT&T, T-Mobile, and essentially the rest of the world use GSM. The easiest way to tell the difference between the two is to remember if you needed a SIM card to activate the phone or not.
However, GSM and CDMA devices are set up differently on the software (and hardware, in terms of radios) side, and if you flash a ROM built for a GSM phone onto a CDMA equivalent, you'll probably break the device. For all intents and purposes, you should consider GSM phones to be wholly distinct devices. Also make sure you're only flashing ROMs built for Sprint, as there are often differences between Sprint and Verizon phones as well.
Knixson said:
Thank you! would I also need to install the open recovery twrp to gain root access as well?
Click to expand...
Click to collapse
yep...unlock, flash recovery, flash ROM
Rirere said:
You need to follow the dev instructions. If I were you though, I wouldn't do anything more until you understand some of the risks involved. A phone is a really, really inconvenient thing to have incapacitated when you're learning how to flash. For one, your device wasn't bricked (completely nonresponsive to input); for another, dev instructions are going to tell you to use fastboot (or a toolkit that runs fastboot for you).
Before you start again, you should learn how to use fastboot at the very least, and if you can, adb install/sideload (although it seems you tried that based on the OP). fastboot is often the only thing working if a flash goes awry.
A ROM is a ROM, no matter what device it's for. GSM/CDMA are separate network technologies that power your phone. In the U.S., Sprint and Verizon are the major CDMA carriers, while AT&T, T-Mobile, and essentially the rest of the world use GSM. The easiest way to tell the difference between the two is to remember if you needed a SIM card to activate the phone or not.
However, GSM and CDMA devices are set up differently on the software (and hardware, in terms of radios) side, and if you flash a ROM built for a GSM phone onto a CDMA equivalent, you'll probably break the device. For all intents and purposes, you should consider GSM phones to be wholly distinct devices. Also make sure you're only flashing ROMs built for Sprint, as there are often differences between Sprint and Verizon phones as well.
Click to expand...
Click to collapse
Thank you for all your information I really do appreciate it. I believe I understand fastboot alot better than when I started. I am starting to understand what I did wrong. I just have a few questions and I think I will be fine to just flash ROMs which is all I really want to do.
1. does it matter if s is off or not?
2. when I do flash a ROM should I flash just the IMG file or the whole ZIP?
I am sorry if this is inconvenient for you or other memebers I do apologize just trying to learn about this flashing ROMS
Knixson said:
Thank you for all your information I really do appreciate it. I believe I understand fastboot alot better than when I started. I am starting to understand what I did wrong. I just have a few questions and I think I will be fine to just flash ROMs which is all I really want to do.
1. does it matter if s is off or not?
2. when I do flash a ROM should I flash just the IMG file or the whole ZIP?
I am sorry if this is inconvenient for you or other memebers I do apologize just trying to learn about this flashing ROMS
Click to expand...
Click to collapse
1) If all you are doing is flashing Roms right now you don't need to s-off.
2) You flash the zip.
and I will second the notion that you should do a lot of reading before you do too much. This is an easy process to screw up if you don't know what you are doing and taking your phone out of commission can be a real pain in the ass.
Good Luck!
Knixson said:
Thank you for all your information I really do appreciate it. I believe I understand fastboot alot better than when I started. I am starting to understand what I did wrong. I just have a few questions and I think I will be fine to just flash ROMs which is all I really want to do.
1. does it matter if s is off or not?
2. when I do flash a ROM should I flash just the IMG file or the whole ZIP?
I am sorry if this is inconvenient for you or other memebers I do apologize just trying to learn about this flashing ROMS
Click to expand...
Click to collapse
We all have to start somewhere. There are some good guides in the forums if you search though that will be a lot more comprehensive than the answers we can give in each individual thread.
1. S-OFF matters if you want to make changes to /system during runtime. For example, if you used a root tool like Titanium Backup to move an app into /system with S-ON, the phone would crash because it detected a security violation (improper programic access to a secured location). S-OFF disables that check. You can still flash ROMs with S-ON though since the protection isn't active to the same extent in recovery, although I think it will block writing to the radio. Don't monkey with it more than you have to though, because it's easy to really screw yourself over with the wrong combination of software (unsigned boot software and S-ON will really brick your phone).
2. Read the thread. Almost all ROMs though are distributed in a flashable .zip, meaning you copy it over to the phone's storage and install through recovery (or use sideload). You shouldn't have to use the .imgs ever, although it's a good trick to know (use fastboot flash <> <>.img) in case something goes wrong. I had to do this recently when my fubared my /system but didn't feel like reflashing the whole ROM, so I extracted system.img from the ROM I used and just pushed that to device.
Rirere said:
We all have to start somewhere. There are some good guides in the forums if you search though that will be a lot more comprehensive than the answers we can give in each individual thread.
1. S-OFF matters if you want to make changes to /system during runtime. For example, if you used a root tool like Titanium Backup to move an app into /system with S-ON, the phone would crash because it detected a security violation (improper programic access to a secured location). S-OFF disables that check. You can still flash ROMs with S-ON though since the protection isn't active to the same extent in recovery, although I think it will block writing to the radio. Don't monkey with it more than you have to though, because it's easy to really screw yourself over with the wrong combination of software (unsigned boot software and S-ON will really brick your phone).
2. Read the thread. Almost all ROMs though are distributed in a flashable .zip, meaning you copy it over to the phone's storage and install through recovery (or use sideload). You shouldn't have to use the .imgs ever, although it's a good trick to know (use fastboot flash <> <>.img) in case something goes wrong. I had to do this recently when my fubared my /system but didn't feel like reflashing the whole ROM, so I extracted system.img from the ROM I used and just pushed that to device.
Click to expand...
Click to collapse
Thank you everyone has been very helpful I am so glad I found this forum I really do appreciate all the info that has been shared with me!
So I will leave with one final question then back to studying, Do you know any really good beginner tutorials or anything to start at?
Thanks again people I have learned a lot just in this conversation
Knixson said:
Thank you everyone has been very helpful I am so glad I found this forum I really do appreciate all the info that has been shared with me!
So I will leave with one final question then back to studying, Do you know any really good beginner tutorials or anything to start at?
Thanks again people I have learned a lot just in this conversation
Click to expand...
Click to collapse
There was a really good one in one of the threads in the development section, but I can't for the life of me remember what ROM had it posted. I'll take another look for it later, but in the meantime I would try reading on XDA's wiki.
Oh I just remembered one more question. I have Viper ROM currently but if I wanted to ad a different one should I wipe the Viper first and install new one or would it install right over top of the Viper? Thanks any help is appreciated. You have been the best!!!
Knixson said:
Oh I just remembered one more question. I have Viper ROM currently but if I wanted to ad a different one should I wipe the Viper first and install new one or would it install right over top of the Viper? Thanks any help is appreciated. You have been the best!!!
Click to expand...
Click to collapse
You can flash over it (which is often called a dirty flash) but you are much better off wiping first. I usually use This tool. Just put it on your sd card and flash it before you flash your new ROM.
I believe this thread will help any and all Sprint HTC One owners if they are having bootloop problems and also answers to frequently asked questions lmao!! Thanks again everyone you ALL have been VERY HELPFUL!!!!
Knixson said:
I believe this thread will help any and all Sprint HTC One owners if they are having bootloop problems and also answers to frequently asked questions lmao!! Thanks again everyone you ALL have been VERY HELPFUL!!!!
Click to expand...
Click to collapse
also do a nandroid before flashing, so you have a fall back
Htc One Stuck In Cwm And Cant Flash A Rom
SO i Rooted my Htc one and now im stuck in Cwm and i cant flash a rom or anything i have tried to sideload a Ruu file onto my phone but that didnt work
SO i tried using the Rom Update Utility and that didnt work either
Im lost and stuck with a Htc One That doesnt work at all i have tried multiple methods but nothing seems to work please help me if you can im 100% new to this whole thing....
jake012 said:
SO i Rooted my Htc one and now im stuck in Cwm and i cant flash a rom or anything i have tried to sideload a Ruu file onto my phone but that didnt work
SO i tried using the Rom Update Utility and that didnt work either
Im lost and stuck with a Htc One That doesnt work at all i have tried multiple methods but nothing seems to work please help me if you can im 100% new to this whole thing....
Click to expand...
Click to collapse
Check PM

To Root or not to Root

Quick question for my good folks here. I just purchased my Note 3 over the weekend via AT&T Next. I love the phone so far as I'm coming over from a fully rooted, modded, OG Note 1 that finally gave up the ghost. I understand the terms of the AT&T Next to be that I can switch to a new phone yearly. The catch is I have to trade in this Note 3, clean, undamaged, and unlocked I presume. I'm very familiar with rooting and flashing on the OG Note but I'm completely lost and overwhelmed with the stark contrast of this Note.
For one, I've read about a locked bootloader that I've never had to worry about before add well as something called Knox which is also new to me. I would love to Root the phone but I do not want to defeat the purpose of upgrading through AT&T Next if it's denied because of the rooting and or custom recovery. Can someone please give me a little advice as to what I should do?
I suppose my question is, if I root is there a way around unrooting and returning to factory without tripping the counters? I understand the warranty is void by rooting but I'm not to worried about that. I would like to be able to use my upgrade after 12 months and return the phone in factory condition.
I'm sure I repeated myself here several times but although I love root access, I don't want to risk being denied when I'm finished playing with this one. Sorry for thelong post. Any guidance would be appreciated. Thanks!
I have a note 3 and I had to wait for the root and to be honest it is worth it as for the custom recovery that's not an option because of the locked bootloader and custom roms are out also so if you do root there is really no benefit except to unlock the ? spot
Sent from my SAMSUNG-SM-N900 using XDA Premium 4 mobile app
dcscorpio76 said:
Quick question for my good folks here. I just purchased my Note 3 over the weekend via AT&T Next. I love the phone so far as I'm coming over from a fully rooted, modded, OG Note 1 that finally gave up the ghost. I understand the terms of the AT&T Next to be that I can switch to a new phone yearly. The catch is I have to trade in this Note 3, clean, undamaged, and unlocked I presume. I'm very familiar with rooting and flashing on the OG Note but I'm completely lost and overwhelmed with the stark contrast of this Note.
For one, I've read about a locked bootloader that I've never had to worry about before add well as something called Knox which is also new to me. I would love to Root the phone but I do not want to defeat the purpose of upgrading through AT&T Next if it's denied because of the rooting and or custom recovery. Can someone please give me a little advice as to what I should do?
I suppose my question is, if I root is there a way around unrooting and returning to factory without tripping the counters? I understand the warranty is void by rooting but I'm not to worried about that. I would like to be able to use my upgrade after 12 months and return the phone in factory condition.
I'm sure I repeated myself here several times but although I love root access, I don't want to risk being denied when I'm finished playing with this one. Sorry for thelong post. Any guidance would be appreciated. Thanks!
Click to expand...
Click to collapse
Depends what are you going to do with the root? I don't see too many benefits of the rooting At&T Note3 and even Xposed doesn't offer too much for TWZ and the modules has only a few working options. And btw the warranty isn't void by rooting. Wrong flashing does sometimes.
arlenesboyfriend said:
I have a note 3 and I had to wait for the root and to be honest it is worth it as for the custom recovery that's not an option because of the locked bootloader and custom roms are out also so if you do root there is really no benefit except to unlock the ? spot
Sent from my SAMSUNG-SM-N900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What makes you think there are no custom roms safestrap allows us to use any custom rom on the att forum you just have to use kk if you are on official 4.4.2 with jb you can use both as long as you Odin the proper kernel and bootloader
---------- Post added at 06:42 PM ---------- Previous post was at 06:41 PM ----------
As for the op you can go back to close to official with Carl's rom in the development section close enough where att wouldn't notice
---------- Post added at 06:42 PM ---------- Previous post was at 06:42 PM ----------
His is called urdroid
Thanks for the responses so far. I was just going to ask about safestrap as I came across that during my reading. What is the deal with that recovery on the Note? I used it on a DROID Maxx HD I had for work but that was a while ago. Keep in mind, my Note came preloaded with KK 4.4.2 out of the box. I'm on NC2 with the latest kernel 722276. Is there anything specific I need to do to obtain root like a preferable methods over the other and is safestrap the only way to go in terms of recovery? No CWM or TWRP? Lastly, if I don't do safestrap, I'll just be rooted with superuser access but no way to flash roms? Just trying to make sure I'm understanding the difference and the benefits.
jerrycoffman45 said:
What makes you think there are no custom roms safestrap allows us to use any custom rom on the att forum you just have to use kk if you are on official 4.4.2 with jb you can use both as long as you Odin the proper kernel and bootloader
---------- Post added at 06:42 PM ---------- Previous post was at 06:41 PM ----------
As for the op you can go back to close to official with Carl's rom in the development section close enough where att wouldn't notice
---------- Post added at 06:42 PM ---------- Previous post was at 06:42 PM ----------
His is called urdroid
Click to expand...
Click to collapse
every rom I've tried to flash has failed
Sent from my SAMSUNG-SM-N900 using XDA Premium 4 mobile app
arlenesboyfriend said:
every rom I've tried to flash has failed
Sent from my SAMSUNG-SM-N900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Then you are doing something wrong
---------- Post added at 03:33 AM ---------- Previous post was at 03:31 AM ----------
dcscorpio76 said:
Thanks for the responses so far. I was just going to ask about safestrap as I came across that during my reading. What is the deal with that recovery on the Note? I used it on a DROID Maxx HD I had for work but that was a while ago. Keep in mind, my Note came preloaded with KK 4.4.2 out of the box. I'm on NC2 with the latest kernel 722276. Is there anything specific I need to do to obtain root like a preferable methods over the other and is safestrap the only way to go in terms of recovery? No CWM or TWRP? Lastly, if I don't do safestrap, I'll just be rooted with superuser access but no way to flash roms? Just trying to make sure I'm understanding the difference and the benefits.
Click to expand...
Click to collapse
Towelroot.com is your only method to root and yes safestrap is the only way to flash custom roms
---------- Post added at 03:35 AM ---------- Previous post was at 03:33 AM ----------
You need to install busybox after rooting then install safestrap 3.75 then you can flash custom roms
I'm to help a co worker root his note 3 using towel root. Everything went well but busy box won't install says something about super user needs too give permission. So I go in to superuser and the binaries need updating so I do so and no dice get a error that knox is installed picked the option to remove but it didn't so I'm back to square one. After rooting with towel root I verified root with root checker and it says we had root but when I dl safestrap 3.75 and choose to install recovery at the top it says the phone is not rooted. I followed the steps like it said. I also went and I uninstalled everything I had previously install busybox superuser and safestrap I went and started from step one and now after I dl towel root and install I can't confirm root with root checker whereas earlier today it did verify root
I finally braved up and rooted my Note 3 via towelroot. I then installed supersu, busybox, and lastly SS 3.75. All installed perfectly without a hitch. However, I know notice an unlocked lock with the text CUSTOM below. Anybody know what that is or what it means?
dcscorpio76 said:
I finally braved up and rooted my Note 3 via towelroot. I then installed supersu, busybox, and lastly SS 3.75. All installed perfectly without a hitch. However, I know notice an unlocked lock with the text CUSTOM below. Anybody know what that is or what it means?
Click to expand...
Click to collapse
It means you gave at&t and samsung the finger.
Sent from my SM-N900A using XDA Premium 4 mobile app
Lol... fair enough @posersk8r
I've had that at times too. Idk what it means but after flashing a ROM(depending on the ROM) or restoring to stock it goes away. I think it just means a certain file was edited. Like I said, I've gotten it too and Knox still isn't tripped.
I wouldn't worry too much.
Sent from my SM-N900A using XDA Free mobile app
It means you are rooted
jerrycoffman45 said:
It means you are rooted
Click to expand...
Click to collapse
This pretty much it. Some roms modded something sysscope im not sure so system would think it's official and the unlocked padlock wont show up on boot.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

[Q] Finger print issue and now extreme lag

OK guys, if any one can actually help me with this... I will be eternally grateful, as my return time frame is up.
Stupidly I flashed a rom that clearly said before wiping anything to remove the finger print settings... Of course I forgot and flashed anyways. Regardless the flash failed, so obviously i recovered a nandroid. But thats is where the problem escalated. After recovery I noticed that i was getting an error on the finger print set up. OK, whatever I Odin flashed back to stock (sammobile of course) after the device was back to stock... LAG... not just a little lag... ridiculous lag. Since this has been the case I have Odin flashed repeatedly trying to resolve, with very little luck.
I have disabled in dev settings the Animation scale, to no avail...
PLEASE GOD SOMEONE GIVE ME SOME GOOD NEWS ON THIS. I early hardware upgraded this from rogers and paid out the ass for it, and of course have lost my ability to return the device as it was working flawlessly before I unleashed my stupidity on it...
*bangs head on desk*
celkin said:
OK guys, if any one can actually help me with this... I will be eternally grateful, as my return time frame is up.
Stupidly I flashed a rom that clearly said before wiping anything to remove the finger print settings... Of course I forgot and flashed anyways. Regardless the flash failed, so obviously i recovered a nandroid. But thats is where the problem escalated. After recovery I noticed that i was getting an error on the finger print set up. OK, whatever I Odin flashed back to stock (sammobile of course) after the device was back to stock... LAG... not just a little lag... ridiculous lag. Since this has been the case I have Odin flashed repeatedly trying to resolve, with very little luck.
I have disabled in dev settings the Animation scale, to no avail...
PLEASE GOD SOMEONE GIVE ME SOME GOOD NEWS ON THIS. I early hardware upgraded this from rogers and paid out the ass for it, and of course have lost my ability to return the device as it was working flawlessly before I unleashed my stupidity on it...
*bangs head on desk*
Click to expand...
Click to collapse
I forgot to wipe my fingerprint settings my first time, too. Not a big deal. Totally fixable.
First things first.
Have you done a factory reset?
Yeah, I'd start with a factory reset, as well.
Rogers is the Canadian version correct?
How many stock versions of the firmware do you guys have?
We have 2 in America. Anj and ank.
If you guys have more than one which are you flashing?
The lag is the stuff you did after you messed up the finger printer scanner trying to fix it.
Does your private mode work?
If not have you tried the private mode fix?
Factory reset has been attempted repeatedly, to no avail...
Privacy mode does work actually.
Rogers has 2 firmwares on sammobile, i have odin flashed both. But lag is still persisting.
Its literally every other word i type. Driving me MENTAL LOL
Sent from my SM-N910W8 using Tapatalk 4
You guys are awesome for the assistance btw. This is the first time in 4 Samsung devices ive done something that im SERIOUSLY concerned was going to be... Unfixable.
I could care less about the finger print scanner, the lag is... Bad.
Sent from my SM-N910W8 using Tapatalk 4
Are you using team win recovery or clockwork mod.
And, what if anything have you wiped through recovery?
Which rom did you flash?
Attempted flashing ib4stids rapture rom.
At the moment im stock unrooted, was using twrp, his instructions advised to factory reset, then advanced wipe data, system, cache, dalvic... I think that was it without looking at the page.
Sent from my SM-N910W8 using Tapatalk 4
I'd re root. And then try firekat.
Making sure of course you didn't leave old fingerprint files.
Then try out the fp scanner and check for lag and report back.
Im experiencing the same exact thing, tried to go stock rom and factory reset three times. I even redownlaoded everything and did it all over again. Tried firekat, dynamic rom, and even cm12 runs a little sluggish. I'm getting a replacement phone at least
So does this lag come from not wiping your fingerprint from your STOCK rom before you flashed a new rom?
Weird thing is, on my other note 4 I never experienced this. I'm pretty sure I forgot to delete fingerprints and then I flashed firekat and no lag.
Thanks guys, MERRY XMAS, if you guys are into that. I have a few thoughts atm, but am away from my pc till tonight. I am determined to get this resolved, and will be checking back and updating on progress as it happens.
Thank you all for the assistance, definitely renewing my faith is Xda.
Sent from my SM-N910W8 using Tapatalk 4
Maybe we're talking defective units.
I think btort may have the right idea by getting a replacement.
My scanner works and if there's lag I'm too full of Christmas cheer to see it.
This is my current set up:
I'll tell you how I got that set up and try to describe what I did when I forgot to clear the finger print scanners memory before I flashed.
---------- Post added at 08:17 PM ---------- Previous post was at 08:09 PM ----------
I mean I soft bricked before and everything and there were no problems like this.
ok
1
When I do a start over flash at the moment I flash anj.
I don't know what tmobile put into ank and until I do its not going on my phone.
(The canadian fellow would flash the earlier version of the rogers stock rom).
Using Odin 3.04. (I'm just not as happy with the later versions of Odin).
2
I flash chainfire.
3
Then the team win recovery.
4
I flash firekat before the phone tries to update.
5
I do the sd card fix with the team win recovery.
6
I do the private mode fix with the team win recovery.
7
I update my modem to ank with the modem trick.
(Canadian users do not have the modem.bin files to do this at this time and should leave their modems alone). I'll try to rip them. It doesn't matter anyway. The 2 modems available are the same anyway.
8
My root apps come back automatically.
Adfree, cachemate, titanium, etc
9
I freeze the bloat.
---------- Post added at 08:20 PM ---------- Previous post was at 08:17 PM ----------
I love firekat btw and all the other roms, of course.
But I'm recommending it because it's the longest running rom. Known to work on the Canadian version of the note 4 and he's been fixing lag / and it's similar enough to stock to fix errant flashing.
And from the set up described you could flash any TouchWiz based rom.
That's about right.
Throwing a factory reset in the mix can help as well. I'm coming back from stock Odin flashes with the same background and ring tones and settings etc.
---------- Post added at 08:50 PM ---------- Previous post was at 08:49 PM ----------
I wanted to run this by you guys. If i were to intentionally mess up the phone. IE pull the cable mid odin flash. then repair via kies... would that fix this issue?
Thoughts? Concerns? Input? Obviously I am going to wait for input from people before i do something this drastic. But I think it might resolve?
I wish it was a defective issue. The devise was used to 2-3 weeks before I decided to flash a rom, causing this... The phone was flawless until i messed it up.
Android_Monsters said:
Maybe we're talking defective units.
I think btort may have the right idea by getting a replacement.
My scanner works and if there's lag I'm too full of Christmas cheer to see it.
This is my current set up:
Click to expand...
Click to collapse
I will definatly give that a go. I am willing to attempt anything. Thank you for the input. I think this thread might assist some others as well. As inevitably this is going to happen to others...
Android_Monsters said:
I'll tell you how I got that set up and try to describe what I did when I forgot to clear the finger print scanners memory before I flashed.
---------- Post added at 08:17 PM ---------- Previous post was at 08:09 PM ----------
I mean I soft bricked before and everything and there were no problems like this.
ok
1
When I do a start over flash at the moment I flash anj.
I don't know what tmobile put into ank and until I do its not going on my phone.
(The canadian fellow would flash the earlier version of the rogers stock rom).
Using Odin 3.04. (I'm just not as happy with the later versions of Odin).
2
I flash chainfire.
3
Then the team win recovery.
4
I flash firekat before the phone tries to update.
5
I do the sd card fix with the team win recovery.
6
I do the private mode fix with the team win recovery.
7
I update my modem to ank with the modem trick.
(Canadian users do not have the modem.bin files to do this at this time and should leave their modems alone). I'll try to rip them. It doesn't matter anyway. The 2 modems available are the same anyway.
8
My root apps come back automatically.
Adfree, cachemate, titanium, etc
9
I freeze the bloat.
---------- Post added at 08:20 PM ---------- Previous post was at 08:17 PM ----------
I love firekat btw and all the other roms, of course.
But I'm recommending it because it's the longest running rom. Known to work on the Canadian version of the note 4 and he's been fixing lag / and it's similar enough to stock to fix errant flashing.
And from the set up described you could flash any TouchWiz based rom.
Click to expand...
Click to collapse
Good luck. I'll help in any way I can.
Karakoram2 said:
Good luck. I'll help in any way I can.
Click to expand...
Click to collapse
Maybe you guys should try this. http://forum.xda-developers.com/showpost.php?p=56276338&postcount=5
someone said it worked for them
10 words
Rapture was the ROM i flashed that got me in this mess lol. I should not say that, firstly, i got myself in this mess. Second, iB4stid is a dope developer, been using his builds for years now.
If flashing this will help i gladly will. But i have a feeling im going to have to send this phone for manufacturer repair :-/
Sent from my SM-N910W8 using Tapatalk 4

I really messed my new phone up.

Just got a new Verizon Nexus 6. Never rooted or messed with android in my life. I installed Android M on it (with hours of frustration) and then was following a guide to root it while being on Android M. Somehow I deleted EVERYTHING on the phone, it says the phone is corrupt and wont start when I try to turn it on. (I have Team Win Recovery Project v2.8.7.1) How can I fix this ASAP? Have no idea how. I just need a working phone. Please help thanks!
If you can boot into TWRP just download a ROM and push it to the device and flash it. If you can get into bootloader you can flash a factory image to fix.
If you've never rooted, let alone even used Android, why the hell are you installing a dev preview onto your device? Guess you found out the hard way. Just saying....
Sent from my Nexus 6 using Tapatalk
Highway 55 said:
If you can boot into TWRP just download a ROM and push it to the device and flash it. If you can get into bootloader you can flash a factory image to fix.
If you've never rooted, let alone even used Android, why the hell are you installing a dev preview onto your device? Guess you found out the hard way. Just saying....
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah I agree. I need some one with skype to walk me though it. I literally followed step by step guides on youtube without knowing what I was doing, it was my fault.
Did you ever figure it out. I have no problem walking you through it. Just shoot me a pm and we can go from there.
Nick
I hope everything turns out okay and you get your phone working again. I would Skype with you but I'm on dad duty with my kids tonight. Good luck!
Sent from my Nexus 6 using Tapatalk
Jaimbi said:
Just got a new Verizon Nexus 6. Never rooted or messed with android in my life. I installed Android M on it (with hours of frustration) and then was following a guide to root it while being on Android M. Somehow I deleted EVERYTHING on the phone, it says the phone is corrupt and wont start when I try to turn it on. (I have Team Win Recovery Project v2.8.7.1) How can I fix this ASAP? Have no idea how. I just need a working phone. Please help thanks!
Click to expand...
Click to collapse
That was your mistake. If never messed with Android worst thing you could do is jump right on a Beta build.
---------- Post added at 08:14 PM ---------- Previous post was at 08:08 PM ----------
Easy to fix if unlocked and have TWRP. Recommend going to stable build first and work your way up. At least will have a working phone. Make a backup up stable build and then play all you want. Could have made backup of stock before even flashed M and would have been golden.
What did you do when you got the corrupt message? I'm asking because many people get this message but if you ignore it, it should boot up anyway.
slosrtnick said:
Did you ever figure it out. I have no problem walking you through it. Just shoot me a pm and we can go from there.
Nick
Click to expand...
Click to collapse
yeah I got it! i watched a video on re-flashing M? I think? It works now, I'm still not sure how to back up my stuff properly but I have a working phone! Thanks for the reply!
Jaimbi said:
Just got a new Verizon Nexus 6. Never rooted or messed with android in my life. I installed Android M on it (with hours of frustration) and then was following a guide to root it while being on Android M. Somehow I deleted EVERYTHING on the phone, it says the phone is corrupt and wont start when I try to turn it on. (I have Team Win Recovery Project v2.8.7.1) How can I fix this ASAP? Have no idea how. I just need a working phone. Please help thanks!
Click to expand...
Click to collapse
It sounds like all you need to do is: when you get to that "phone is corrupt" screen, press volume down and then the power button to continue.

[GUIDE] Downgrade Firmware SM-G900A Lolipop

Prerequisites:
Odin 3.11.1- http://forum.xda-developers.com/showthread.php?t=2711451
5.1.1- http://forum.xda-developers.com/showpost.php?p=53454972&postcount=1 (Use first link for OI5)
Kies- http://www.samsung.com/in/support/usefulsoftware/KIES/ (To backup data. Use Kies 3)
Samsung USB Driver- http://developer.samsung.com/technical-doc/view.do?v=T000000117
NOTICE: Do not use this guide to downgrade from OC4 and above to NCE, you will brick your device. Only use this guide to downgrade to compatible firmware's for example: PA3 to OI5, PA2 to PA1, etc..Do not attempt to downgrade back to OC4 as ATT blew a qfuse. You can only downgrade to OF2 and above. This may brick your device and I am not liable. This does not trip the KNOX flag. This will wipe all data so do keep a backup.
Download the firmware you want for example OI5 from the link above. Extract the file to a directory. Then launch Odin and go into the extracted file. Select CP,CSC, and AP(PDA on Odin 3.9 and below). Do not select the BL slot. I repeat do not select the BL slot, only use AP,CP, and CSC. Also in the options tab select only Auto Restart and F. Reset Time. Turn off your phone and hold power button, home button, and volume down button. Then once it says flashing a custom firmware may..., press the volume up button. Then plug in your phone and you should see blue, if you see yellow install the USB drivers. Once you have plugged it in and the correct files are selected, press Start. This process will take about 5-10 minutes depending on the speed of the USB. Do not unplug the cable while in this process. Once it says PASS at the top, the phone will boot into recovery mode and apply the update. Once the phone has applied the update, it will reboot and be stuck at the AT&T logo. Do not panic, this just means that it is working on the operating system. This will take about 5-6 minutes. Once this is done proceed to setup the phone as usual going through the entire setup. Once the setup, is finished you can then restore your data using Kies if you had a backup. You have now successfully downgraded your phone. This process could be used to root our devices because we are exposing security holes that have been patched.
I just want to go from PA3 to.... whichever one will allow root access. Warranty possibly needed. I need to make sure this will work because.. otherwise.. my sister's phone could blow a fuse (****ing boot loaders..) and go dead.. if i can get around the warranty flag then that would be awesome. Sorry.. just not sure how to handle it; can't find people who are reliable and say it can actually downgrade without bricking.
pr3dicament said:
I just want to go from PA3 to.... whichever one will allow root access. Warranty possibly needed. I need to make sure this will work because.. otherwise.. my sister's phone could blow a fuse (****ing boot loaders..) and go dead.. if i can get around the warranty flag then that would be awesome. Sorry.. just not sure how to handle it; can't find people who are reliable and say it can actually downgrade without bricking.
Click to expand...
Click to collapse
Your best option would be to downgrade to OI5, which the link is provided in the OP. Downgrade, and then try rooting with Kingroot. The vulnerability which works is CVE 2015-1805. Otherwise if Kingroot doesn't work for you you could try iovyroot, but that needs an absolute kernel address. Try searching on Github for CVE 2015-1805 . Sorry can't post links, I am a new user.
NavSad said:
Your best option would be to downgrade to OI5, which the link is provided in the OP. Downgrade, and then try rooting with Kingroot. The vulnerability which works is CVE 2015-1805. Otherwise if Kingroot doesn't work for you you could try iovyroot, but that needs an absolute kernel address. Try searching on Github for CVE 2015-1805 . Sorry can't post links, I am a new user.
Click to expand...
Click to collapse
Kingroot/KingOroot was what I was about to try. I'll grab OI5, maybe just the kernel, hopefully? .. I just hate removing it, and not with SuperSUme .. never worked for me. When it comes to Kingroot, I just would rather remove it manually, I guess.. plus SuperSUme didn't work on my tablet when I tried to use it heh. There's a post somewhere with instructions but all you do is just keep a daemon running while you uninstall and then install the other, while partially keeping root before it gets the binary and updates from SuperSU.
Will post results when I can. I dont want to downgrade the entire thing if i can quickly avoid it.
NavSad said:
Your best option would be to downgrade to OI5, which the link is provided in the OP. Downgrade, and then try rooting with Kingroot. The vulnerability which works is CVE 2015-1805. Otherwise if Kingroot doesn't work for you you could try iovyroot, but that needs an absolute kernel address. Try searching on Github for CVE 2015-1805 . Sorry can't post links, I am a new user.
Click to expand...
Click to collapse
http://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597
^ You can say it; even a post on here has it. It looks very promising. I downloaded OI5 but didn't get a chance to flash, will tonight or tomorrow.
The following could not find a known exploit for the specific OS.. Failed with the following: Kingoroot, Kingroot, and vRoot (aka iRoot) .. then I checked here to give updates .. and upon re-reading your post.. I noticed you also put iovyroot, made from an exploit based on CVE-2015-1805, as the post says. It looks EXACTLY like saferoot lol.. I can deal with temporary root, I'll take care of the rest to make sure it stays.. I'll be giving more updates. Thank you for pointing me in the right direction.. I made sure all of my ADB drivers are installed correctly, as well as enabling USB debugging and doing a few things in ADB to make sure they are working and they are. RSA now saved.
My sister's phone still on PA3.. I'm glad she listened. If it doesn't work, then it doesn't work. I'm sure many others will appreciate this as well.
pr3dicament said:
http://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597
^ You can say it; even a post on here has it. It looks very promising. I downloaded OI5 but didn't get a chance to flash, will tonight or tomorrow.
The following could not find a known exploit for the specific OS.. Failed with the following: Kingoroot, Kingroot, and vRoot (aka iRoot) .. then I checked here to give updates .. and upon re-reading your post.. I noticed you also put iovyroot, made from an exploit based on CVE-2015-1805, as the post says. It looks EXACTLY like saferoot lol.. I can deal with temporary root, I'll take care of the rest to make sure it stays.. I'll be giving more updates. Thank you for pointing me in the right direction.. I made sure all of my ADB drivers are installed correctly, as well as enabling USB debugging and doing a few things in ADB to make sure they are working and they are. RSA now saved.
My sister's phone still on PA3.. I'm glad she listened. If it doesn't work, then it doesn't work. I'm sure many others will appreciate this as well.
Click to expand...
Click to collapse
Did you make any progress on this? I just rolled back to OI5. Now I need to figure out how to get the correct address and compile that code.
So, I just got this 900a AT&T phone and it already has 5.1.1 installed, which already hasent the mega locked down bootloader, correct? Everywhere else I've looked for a root method has said you CAN'T downgrade. I don't know much about downgrading or what version I can downgrade to. Can I get a bit of help or explanation?
joshua_nope said:
So, I just got this 900a AT&T phone and it already has 5.1.1 installed, which already hasent the mega locked down bootloader, correct? Everywhere else I've looked for a root method has said you CAN'T downgrade. I don't know much about downgrading or what version I can downgrade to. Can I get a bit of help or explanation?
Click to expand...
Click to collapse
You can't downgrade back to 4.4.2 once you are above 5.0 . This method explained in the OP is to only downgrade back to OI5, and possibly OC4. Not NCE.
Do I go by baseband or build number?
because my baseband is OC4 but my build is OF3.
darrel12 said:
Do I go by baseband or build number?
because my baseband is OC4 but my build is OF3.
Click to expand...
Click to collapse
Go by build number. For you it would be upgrading not downgrading.
Greek2me said:
Did you make any progress on this? I just rolled back to OI5. Now I need to figure out how to get the correct address and compile that code.
Click to expand...
Click to collapse
Ugh it was forced through to PA4.... unbelievable. I don't know if I can roll back to OI5 with PA4. She always wants her phone back right away.. I'm sorry about the lack of time in between responses, but I have to back up her crap anyway one way or another if I'm rolling back. I wanted to try and just roll back the kernel and then give kingroot and shot. An RCA Tablet that I got about 8 months ago for $35 at Walmart wasn't able to be rooted for the longest time since it came with LP 5.0.1.. I finally was able to root that.
I think I'm the first to do it. Voyager Pro. I use FlashFire with recovery for it.. sorry, off topic.. but that exploit was very useful in that instant.
I will see what I can do to roll back.. my life is literally a mess. I don't want a bunch of people saying poor pr3dicament or some stupid ****. Oral cancer, early. Cutting it out... and then (more) awful pain after that. Second recurrence. Didn't spread. Procedure tomorrow. I'll just grab her phone and say I am fixing a bug for security or something to make sure she shuts the **** up about it. No guarantees. If I can roll back from PA3 or PA4 to OI5.. not sure if another went through.. I think it did. .. but if I can roll back to OI5 with no problems or even just the kernel to root it... even temporary root.. full root.. I have a few current binaries that it'll work with.
I temporarily rooted the RCA and now it's fully rooted with the binary I use in place... I am probably going to just write a script to make it easier if it works. Again, my apologies for the length between responses.
pr3dicament said:
Ugh it was forced through to PA4.... unbelievable. I don't know if I can roll back to OI5 with PA4. She always wants her phone back right away.. I'm sorry about the lack of time in between responses, but I have to back up her crap anyway one way or another if I'm rolling back. I wanted to try and just roll back the kernel and then give kingroot and shot. An RCA Tablet that I got about 8 months ago for $35 at Walmart wasn't able to be rooted for the longest time since it came with LP 5.0.1.. I finally was able to root that.
I think I'm the first to do it. Voyager Pro. I use FlashFire with recovery for it.. sorry, off topic.. but that exploit was very useful in that instant.
I will see what I can do to roll back.. my life is literally a mess. I don't want a bunch of people saying poor pr3dicament or some stupid ****. Oral cancer, early. Cutting it out... and then (more) awful pain after that. Second recurrence. Didn't spread. Procedure tomorrow. I'll just grab her phone and say I am fixing a bug for security or something to make sure she shuts the **** up about it. No guarantees. If I can roll back from PA3 or PA4 to OI5.. not sure if another went through.. I think it did. .. but if I can roll back to OI5 with no problems or even just the kernel to root it... even temporary root.. full root.. I have a few current binaries that it'll work with.
I temporarily rooted the RCA and now it's fully rooted with the binary I use in place... I am probably going to just write a script to make it easier if it works. Again, my apologies for the length between responses.
Click to expand...
Click to collapse
Well, all I can say is that if you're successful, then you'll be a hero.
Good luck.
Yes, I rolled back from PA4 to OI5 using this guide.
I can do the root if only I can figure out how to extract the kernel from the stock OI5. Any ideas?
Greek2me said:
Yes, I rolled back from PA4 to OI5 using this guide.
I can do the root if only I can figure out how to extract the kernel from the stock OI5. Any ideas?
Click to expand...
Click to collapse
Just PM'D zxz00 for help on this issue. He's developer of iovyroot.
pr3dicament said:
Ugh it was forced through to PA4.... unbelievable. I don't know if I can roll back to OI5 with PA4. She always wants her phone back right away.. I'm sorry about the lack of time in between responses, but I have to back up her crap anyway one way or another if I'm rolling back. I wanted to try and just roll back the kernel and then give kingroot and shot. An RCA Tablet that I got about 8 months ago for $35 at Walmart wasn't able to be rooted for the longest time since it came with LP 5.0.1.. I finally was able to root that.
I think I'm the first to do it. Voyager Pro. I use FlashFire with recovery for it.. sorry, off topic.. but that exploit was very useful in that instant.
I will see what I can do to roll back.. my life is literally a mess. I don't want a bunch of people saying poor pr3dicament or some stupid ****. Oral cancer, early. Cutting it out... and then (more) awful pain after that. Second recurrence. Didn't spread. Procedure tomorrow. I'll just grab her phone and say I am fixing a bug for security or something to make sure she shuts the **** up about it. No guarantees. If I can roll back from PA3 or PA4 to OI5.. not sure if another went through.. I think it did. .. but if I can roll back to OI5 with no problems or even just the kernel to root it... even temporary root.. full root.. I have a few current binaries that it'll work with.
I temporarily rooted the RCA and now it's fully rooted with the binary I use in place... I am probably going to just write a script to make it easier if it works. Again, my apologies for the length between responses.
Click to expand...
Click to collapse
You can use Package Disable Pro to block OTA updates without root.
Greek2me said:
Yes, I rolled back from PA4 to OI5 using this guide.
I can do the root if only I can figure out how to extract the kernel from the stock OI5. Any ideas?
Click to expand...
Click to collapse
Yeah... the kernel is all we need... after that, we can get in.. almost positive on that. Please remember that this isn't even my phone I'm talking about. My sister is a little stupid and just acts like she can't let me have it for a few minutes.. I will take your vouch and go for the kernel only.
I might be looking to do this very shortly, but here's how it was done with Odin.. not sure if it'll give the same result nowadays. It should.. it's an extraction. I didn't look through the entire process, I've been very busy, but from what I remember.. you download a stock rom and use 7zip or WinRAR and extract boot.img and convert to .tar for ODIN, place it in PDA/AP (Depends on version of Odin)
If this does NOT work, please do NOT be surprised and do NOT claim responsibility for the above. That is just what I remember doing not too long ago for S4 debugging. I know this is an S5.. so.. grab the OI5 zip/tar and extract it, then find boot.img and convert it to .tar. If you screw your phone up.. it's not my fault. That's all I can do at the moment.. Her phone is on her right now, so.. just trying to help. If this is incorrect or wrong, my apologies. There's some youtube video where it kind of shows you if you don't understand... the guy is hard to understand so turn up your volume:
https://www.youtube.com/watch?v=-3j7lyI_DuU
---------- Post added at 05:31 PM ---------- Previous post was at 05:21 PM ----------
NavSad said:
You can use Package Disable Pro to block OTA updates without root.
Click to expand...
Click to collapse
I completely forgot about that..
God I feel like an idiot now. Thank you for that. When she comes home I'll disable something for her so that she will come to me with the phone with her problem Again--thank you for reminding me, and the rest of the community, about this app. I was always just keeping cache full to the point where it couldn't force it but dumb little sister thought disabling automatic updates on the Play Store was the same thing as not letting AT&T force it.
lol.. either way, I'll just try to remotely install it via her google account.
---------- Post added at 05:37 PM ---------- Previous post was at 05:31 PM ----------
NavSad said:
Just PM'D zxz00 for help on this issue. He's developer of iovyroot.
Click to expand...
Click to collapse
Yeah... I thought maybe converting boot.img to boot.tar etc would work or something.. usually people mean boot when they say kernel, and kernel when they mean boot. There's many levels of booting, and that's why I just posted that youtube video in there. I did that a long time ago but this was before sbl1, 2, 3 (etc) ... so really i dont have an idea. I do know that you can roll back though.
If you get no response, I'll try asking. I hope I was correct.. I do not want to be seen as illiterate..
eh forget it lol if you get a response from him that is similar to mine than that'd be great. I actually want you to confirm that with him or any other developers before moving forward with a simple kernel downgrade because that could potentially cause trouble.
NavSad said:
Just PM'D zxz00 for help on this issue. He's developer of iovyroot.
Click to expand...
Click to collapse
Got a reply from him, going to copy and paste it.
"For 32bit you can use kallsyms and for 64bit see here https://github.com/dosomder/iovyroot/issues/1"- Reply from zxz00
NavSad said:
Got a reply from him, going to copy and paste it.
"For 32bit you can use kallsyms and for 64bit see here https://github.com/dosomder/iovyroot/issues/1"- Reply from zxz00
Click to expand...
Click to collapse
Yeah I've requested a pull from it before.. I got nothin'.. you could call me a halfassed developer but nothing like most of these guys.
I'll take another look.. I'll try another pull.
---------- Post added at 06:06 PM ---------- Previous post was at 05:59 PM ----------
pr3dicament said:
Yeah I've requested a pull from it before.. I got nothin'.. you could call me a halfassed developer but nothing like most of these guys.
I'll take another look.. I'll try another pull.
Click to expand...
Click to collapse
Oh wait a minute. Now I see why he pointed you to 1. You're looking for an *ASBOLUTE* kernel address..
Can't pull now.. ****. It's all closed. Either that or my brain had a mass that I do not know about. Alright well that exploit is already passed along.. we just need to roll back to OI5 or bust. That's basically the short answer.
---------- Post added at 06:09 PM ---------- Previous post was at 06:06 PM ----------
NavSad said:
Got a reply from him, going to copy and paste it.
"For 32bit you can use kallsyms and for 64bit see here https://github.com/dosomder/iovyroot/issues/1"- Reply from zxz00
Click to expand...
Click to collapse
For the record.. When I used iovyroot via adb the other night, before PA4... It wasn't happy that it was "64 bit" but I can't believe I missed that.. it was right in front of me and I just did not see it. I am so so pissed. She had to take the phone anyway, I didn't get a chance to enable ADB over TCP/IP... @#)%*@%$ God. I was one line away. One.. ****ing.. line.
I'll just go get broken S5 for a few bucks and replace the motherboard.
pr3dicament said:
Yeah I've requested a pull from it before.. I got nothin'.. you could call me a halfassed developer but nothing like most of these guys.
I'll take another look.. I'll try another pull.
---------- Post added at 06:06 PM ---------- Previous post was at 05:59 PM ----------
Oh wait a minute. Now I see why he pointed you to 1. You're looking for an *ASBOLUTE* kernel address..
Can't pull now.. ****. It's all closed. Either that or my brain had a mass that I do not know about. Alright well that exploit is already passed along.. we just need to roll back to OI5 or bust. That's basically the short answer.
---------- Post added at 06:09 PM ---------- Previous post was at 06:06 PM ----------
For the record.. When I used iovyroot via adb the other night, before PA4... It wasn't happy that it was "64 bit" but I can't believe I missed that.. it was right in front of me and I just did not see it. I am so so pissed..
Click to expand...
Click to collapse
I compiled for 32 bit using ndk but it won't work without absolute kernel adress.
NavSad said:
I compiled for 32 bit using ndk but it won't work without absolute kernel adress.
Click to expand...
Click to collapse
Hm. Did you try a rollback yet or kernel rollback? anything like that?

Categories

Resources