I was wondering if there has been a way for the Verizon Note 2 users to replace their custom recovery with the Android Stock Recovery to receive OTA's? Similar to this http://www.youtube.com/watch?v=2VVyQRdsnaA
Thanks
andrewjt19 said:
I was wondering if there has been a way for the Verizon Note 2 users to replace their custom recovery with the Android Stock Recovery to receive OTA's? Similar to this http://www.youtube.com/watch?v=2VVyQRdsnaA
Thanks
Click to expand...
Click to collapse
Visit this thread http://forum.xda-developers.com/showthread.php?t=2107738. Under the section boldly labeled Here's the bottom line up-front.....flash the stock pit file and the updated bootloader baseline file. Place the pit file in the PIT section of ODIN and the bootloader baseline file in the PDA section and flash them at the same time. This should restore the stock recovery.
Thanks. I'll give it a shot when I need it again. I ended up just restoring the phone entirely.
Sent from my SCH-I605 using xda app-developers app
andrewjt19 said:
Thanks. I'll give it a shot when I need it again. I ended up just restoring the phone entirely.
Click to expand...
Click to collapse
How did you do the restore? Thanks.
universexda said:
How did you do the restore? Thanks.
Click to expand...
Click to collapse
It's simple. check out the guide by imnuts here
http://rootzwiki.com/index.php?/topic/37372-[ODIN][VRALJB]-Restore-to-Stock
[ODIN][VRALJB] Restore to Stock
Sent from my SCH-I605 using xda app-developers app
universexda said:
How did you do the restore? Thanks.
Click to expand...
Click to collapse
i told you how to do the restore...damn i swear some folks around here are hard headed.
droidstyle said:
i told you how to do the restore...damn i swear some folks around here are hard headed.
Click to expand...
Click to collapse
If you think I'm not going to seek out other people's experience and rely only on your word or your guide as gospel you don't what real computer/phone engineering is about and you don't know me.
Elsewhere I asked you if you have an unlocked bootloader and you flashed the alternate restore file which leaves you bootloader unlocked if running the VRALL4 OTA would successfully relock the bootloader or cause a problem. Would you answer that question, give it your best shot, or simply say you don't know, which are all part of a scientific process.
universexda said:
If you think I'm not going to seek out other people's experience and rely only on your word or your guide as gospel you don't what real computer/phone engineering is about and you don't know me.
Elsewhere I asked you a pertinent question that is not covered in your guide. If you're really about understanding and spreading the knowledge and not simply trying to avoid the question and make people think you know it all, then you'll answer the question, give it the best shot you can, or simply say you don't know, which are all part a scientific process.
Click to expand...
Click to collapse
Let me help you out. You can keep asking and you're going to get the same answer or you're gonna get the wrong answer. His guide is not gospel as you put it, but it is the best, most accurate and easiest guide (that's why the mods decided to stickie it).
Also, I've directed countless people to his guide here and the s3 section to unbrick their phones and guess what it works every time. So you can keep your phone in the state it is and keep flooding the forum with the same question and get the answers I mentioned earlier.
Finally what is part of the scientific process? And what's this question you asked? I just read through your posts and I see questions that were answered in his guide which he then answered again for you. By the way you do realize his work is a guide to help new people with their phone. Not a comprehensive faqs thread.
Sent from my SCH-I605 using Tapatalk 2
kintwofan said:
...
Click to expand...
Click to collapse
I edited my response to him and laid out a detailed question I have based upon reading his guide, and many posts here. It pertains to relocking the bootloader. If you, he or someone else can answer it I'd appreciate it.
universexda said:
I edited my response to him and laid out a detailed question I have based upon reading his guide, and many posts here. It pertains to relocking the bootloader. If you, he or someone else can answer it I'd appreciate it.
Click to expand...
Click to collapse
He answered that for you already, but I'll go into more details. The problem is not OTA with unlocked. It's a custom recovery and OTA. The OTA contains a boot loader theat overwrites your unlocked boot loader without a problem. It does not have a recovery so you keep your custom recovery and get a locked boot loader which equals unauthorized message.
The alternate restore gives you a stock recovery back. The only thing it doesn't restore to stock is the boot loader. So restore+OTA=full locked stock
Sent from my SCH-I605 using Tapatalk 2
kintwofan said:
He answered that for you already, but I'll go into more details. The problem is not OTA with unlocked. It's a custom recovery and OTA. The OTA contains a boot loader theat overwrites your unlocked boot loader without a problem. It does not have a recovery so you keep your custom recovery and get a locked boot loader which equals unauthorized message.
The alternate restore gives you a stock recovery back. The only thing it doesn't restore to stock is the boot loader. So restore+OTA=full locked stock
Click to expand...
Click to collapse
Thanks for the answer.
kintwofan said:
He answered that for you already, but I'll go into more details. The problem is not OTA with unlocked. It's a custom recovery and OTA. The OTA contains a boot loader theat overwrites your unlocked boot loader without a problem. It does not have a recovery so you keep your custom recovery and get a locked boot loader which equals unauthorized message.
The alternate restore gives you a stock recovery back. The only thing it doesn't restore to stock is the boot loader. So restore+OTA=full locked stock
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
THIS!!!!!!!
---------- Post added at 10:07 PM ---------- Previous post was at 10:04 PM ----------
universexda said:
If you think I'm not going to seek out other people's experience and rely only on your word or your guide as gospel you don't what real computer/phone engineering is about and you don't know me.
Elsewhere I asked you if you have an unlocked bootloader and you flashed the alternate restore file which leaves you bootloader unlocked if running the VRALL4 OTA would successfully relock the bootloader or cause a problem. If you're really about understanding and spreading the knowledge and not simply trying to avoid the question and make people think you know it all, then you'll answer the question, give it your best shot, or simply say you don't know, which are all part a scientific process. But avoiding a response and crude blustering are bs.
Click to expand...
Click to collapse
i didnt avoid any question...i answered it plain and simple. yea i dont know anything, boy you got me there lmfao.
on a side note i didnt provide a full detailed explanation because kwintofan and myself have answered that question countless times. a bit of resesrch on your end should of easily answered your question. dont get butt hurt its just the internet
droidstyle said:
THIS!!!!!!!
---------- Post added at 10:07 PM ---------- Previous post was at 10:04 PM ----------
i didnt avoid any question...i answered it plain and simple. yea i dont know anything, boy you got me there lmfao.
on a side note i didnt provide a full detailed explanation because kwintofan and myself have answered that question countless times. a bit of resesrch on your end should of easily answered your question. dont get butt hurt its just the internet
Click to expand...
Click to collapse
It's silly to get wound up because people don't just accept your guide and advice right off the bat. If you were really about knowledge and not your ego you wouldn't have a problem with people attempting to verify what you have to say.
Notably, your response to me in your guide thread that "no people had problems with ota when using a custom recovery" conflicts with kintwofan's response that "The problem is not OTA with unlocked. It's a custom recovery and OTA." But above you just endorsed what kintwofan had to say. So despite your vein popping crudeness my question remains unresolved between what the 2 of you say.
universexda said:
Don't get your panties in a bunch because people don't accept your guide and advice at face value. If you were really about knowledge and not your ego you wouldn't have a problem with people attempting to verify what you have to say.
Notably, your response to me in your guide thread that "no people had problems with ota when using a custom recovery" conflicts with kintwofan's response that "The problem is not OTA with unlocked. It's a custom recovery and OTA." But above you just endorsed what kintwofan had to say. So despite your vein popping crudeness my question remains unresolved between what the 2 of you say.
Click to expand...
Click to collapse
Our answers are the same. He said no to having a problem taking the ota and being unlocked then continued to say the problem was a custom recovery. I guess he just forgot the period in there.
And this is getting old. If you were really all about knowledge you would take his answer and research why instead of wanting to be soon fed the information. You would have also just searched for the multiple people that have went to his guides and fixed their phone to verify if they were legit.
Sent from my SCH-I605 using Tapatalk 2
kintwofan said:
Our answers are the same. He said no to having a problem taking the ota and being unlocked then continued to say the problem was a custom recovery. I guess he just forgot the period in there.
And this is getting old. If you were really all about knowledge you would take his answer and research why instead of wanting to be soon fed the information. You would have also just searched for the multiple people that have went to his guides and fixed their phone to verify if they were legit.
Click to expand...
Click to collapse
I don't see where droidstyle says it's recovery that would cause a problem with the OTA and not the bootloader.
Verifying with others is precisely what I've been doing. The thing is that droidstyle has jumped in peevishly to assert that I should just accept what his guide says and not ask anyone else about it at all. Problem is that his guide doesn't explicitly address my question. And secondly it makes sense to verify procedures with others before relying on what could be a hundreds of dollars mistake.
Appreciate both you and him when you address the issue. It's not old to me when there are discrepancies in what's being said. I've researched the issue by reading all relevant threads here since the vrall4 jailbreak and still my question has not been consistently answered. I advise you both to ignore my questions/research on this matter in the future as it appears you've already contributed what you can.
no. People had problems with ota when using a custom recovery.
There I'll add the punctuation from his quote now you can see that we agree. My point was not to keep asking, but to actually research. You know look at what's in the ota and what causes the unauthorized message. Then take that info and formulate a hypothesis and test it. You know the scientific method you like.
Also don't worry I won't answer you're further questions.
Sent from my SCH-I605 using Tapatalk 2
universexda said:
I don't see where droidstyle says it's recovery that would cause a problem with the OTA and not the bootloader.
Verifying with others is precisely what I've been doing. The thing is that droidstyle has jumped in peevishly to assert that I should just accept what his guide says and not ask anyone else about it at all. Problem is that his guide doesn't explicitly address my question. And secondly it makes sense to verify procedures with others before relying on what could be a hundreds of dollars mistake.
Appreciate both you and him when you address the issue. It's not old to me when there are discrepancies in what's being said. I've researched the issue by reading all relevant threads here since the vrall4 jailbreak and still my question has not been consistently answered. I advise you both to ignore my questions/research on this matter in the future as it appears you've already contributed what you can.
Click to expand...
Click to collapse
i did say it was a recovery issue in my thread wher u initially asked...go back and read. then u might want to go back and read thru the guide again and you will see where i answered that question more than once. my guide is stickied for a reason...if you want other opinions thats fine, i could care less. i provided you with all the info necessary, your not going to get some magical answer....ill say it again.
odin stock vraljb(no bootloader version / alternate restore method). this will give you stock recovery back which will allow you to take the L4 OTA. then you will be on stock, locked, and bloated L4.... the bootlader being locked or unlocked will not effect anything OTA related. Having a custom recovery will cause the OTA to fail.
---------- Post added at 11:07 PM ---------- Previous post was at 10:57 PM ----------
universexda said:
It's silly to get wound up because people don't just accept your guide and advice right off the bat. If you were really about knowledge and not your ego you wouldn't have a problem with people attempting to verify what you have to say.
Notably, your response to me in your guide thread that "no people had problems with ota when using a custom recovery" conflicts with kintwofan's response that "The problem is not OTA with unlocked. It's a custom recovery and OTA." But above you just endorsed what kintwofan had to say. So despite your vein popping crudeness my question remains unresolved between what the 2 of you say.
Click to expand...
Click to collapse
you obviously have a problem with comprehension...my panties are not in a bunch or wound up. i could give 2 ****s REALLY! you came into my thread asking my advice, then ignored me. then you proceed to take advice from new users that were not sure themselves. wow your scientific method is really panning out now.
note 2 bootloop
Ok next...i bought a note 2 verizon off someone and i know it was on 4.3.1 nd7 thats all i can remember i rooted kingroot then supersu me ok everything fine until i downloaded twrp app from playstore flashed twrp and what ever i did i went to boot into recovery thats it done deal no stock recovery only have download mode.Keeps saying firmare disrupted and verizon firmware wrong go to store and fix. Ive flashed some stock roms and tried flashing twrp through odin..whenever i do it does pass the flash and reboots right back to original stuck screen its says note 2 real fast then pops up to the bootloop screen any advice would be appretiated..lets help another android user out i need my phone back
ricosf415 said:
Ok next...i bought a note 2 verizon off someone and i know it was on 4.3.1 nd7 thats all i can remember i rooted kingroot then supersu me ok everything fine until i downloaded twrp app from playstore flashed twrp and what ever i did i went to boot into recovery thats it done deal no stock recovery only have download mode.Keeps saying firmare disrupted and verizon firmware wrong go to store and fix. Ive flashed some stock roms and tried flashing twrp through odin..whenever i do it does pass the flash and reboots right back to original stuck screen its says note 2 real fast then pops up to the bootloop screen any advice would be appretiated..lets help another android user out i need my phone back
Click to expand...
Click to collapse
I did the same thing on my Note 2. I currently use the Note 4, but wanted to do some updates to my Note 2 and give it to my son. I just forgot about the locked bootloader, and I downloaded the TWRP app from the Play Store and flashed the 3.0 TWRP. Next boot gave me the "Unauthorized software" message. I've tried flashing stock firmware, and it succeeds, but since the bootloader is locked, I still get the "Unauthorized" message. I would also appreciate any help that can be offered to get the bootloader back to stock. I knew better, it had been a couple years since I messed with my Note 2. Thanks for any help.
Did you all try flashing the 4.4 stock firmware? Should work if you can find the file. I just can't seem to find it
Sent from my SM-N915V using Tapatalk
Related
Hello, i've been using these forums in particular the Samsung Galaxy S2 thread "
[Rom] AOKP(Jellybean 4.1.2) | Task650 & Ktoonsez (11/9)" for awhile now, probably going on a year. Just today i tried updating to the aforementioned update in that thread from 11/9, and while installing the ROM segment, i got an Error, and said installation aborted, tried once more, same thing, upon trying to reboot my phone it is now stuck in an endless reboot loop, which is why i believe it is bricked. I have found sites that tell me to get back to the stock rom, since i believe that is my only option now, but first and foremost id like to know how to manually get into recovery mode.
Other sites have said holding down Home Volume Up and Power simultaneously will do this, i've tried multiple times, hasn't worked, so unless there's something i'm missing there i'd love to know if there is some other way. Also if there is anything i can do besides simply going back to stock ROM which is a long and drawn out process Id love to know.
Thank you for ANY and all answers in advance.
First off, make sure you have the i777. I know you said you've been using Tasks' AOKP rom, but forgive us for not trusting you yet. Too many people are trying to flash roms that aren't built for their model.
Secondly, recovery mode is volume up AND down, while holding the power for the i777. Hold all three until you get into recovery.
Also, what sort of error did you get? If you can get into recovery your phone isn't bricked.
Sent from my i777
4thCrater said:
First off, make sure you have the i777. I know you said you've been using Tasks' AOKP rom, but forgive us for not trusting you yet. Too many people are trying to flash roms that aren't built for their model.
Secondly, recovery mode is volume up AND down, while holding the power for the i777. Hold all three until you get into recovery.
Also, what sort of error did you get? If you can get into recovery your phone isn't bricked.
Sent from my i777
Click to expand...
Click to collapse
I've been flashing form this thread for nearly a year as i mentioned so i definitely have the right model, i'm not sure what type of error it was, all i know it it said something like E:/Error cancellation aborted.
Ok in the midst of posting this i finally got into recovery thank you, and i tried reinstalling again. it says "Installing Update...
Symlink: some symlinks failed
E:Error in /emmc/aokp_JB_I777-ota-eng.task650.ktoonsez-11.9.2012.zip
(Status 7)
Which i know is a common issue in the FAQ. but the only suggestion is to install some other ROM< which i cannot do b/c i cannot get the phone past boot screen, so i believe i'll be using a guide i found on cnet to go back to stock rom.
pisky1 said:
I've been flashing form this thread for nearly a year as i mentioned so i definitely have the right model, i'm not sure what type of error it was, all i know it it said something like E:/Error cancellation aborted.
Ok in the midst of posting this i finally got into recovery thank you, and i tried reinstalling again. it says "Installing Update...
Symlink: some symlinks failed
E:Error in /emmc/aokp_JB_I777-ota-eng.task650.ktoonsez-11.9.2012.zip
(Status 7)
Which i know is a common issue in the FAQ. but the only suggestion is to install some other ROM< which i cannot do b/c i cannot get the phone past boot screen, so i believe i'll be using a guide i found on cnet to go back to stock rom.
Click to expand...
Click to collapse
Don't use stuff from other sites.
Sent from Team Pirate! Using Tapatalk 2
Nick281051 said:
Don't use stuff from other sites.
Sent from Team Pirate! Using Tapatalk 2
Click to expand...
Click to collapse
I have no problem doing that as long as their some guide on this site to go back to stock rom for me. This guide requires me to go to download mode, which i'm assuming is a different button combination than Recovery?
Id like to know that if thats known.
pisky1 said:
I have no problem doing that as long as their some guide on this site to go back to stock rom for me. This guide requires me to go to download mode, which i'm assuming is a different button combination than Recovery?
Id like to know that if thats known.
Click to expand...
Click to collapse
I'm thinking if i can get into download mode, i can follow the steps that the thread i've been following far give you for status 7 errors, and get my back up and running how it was.
Just need to know how lol.
First thing is IF you need to go back to stock find creepycrawly's return to stock thread. I would HIGHLY SUGGEST TO ONLY USE GUIDES FROM THIS FORUM.
Now onto your issue I personally would get a remove able sdcard, download the aokp zip again and double check the md5. My bet is you just got a bad download. Place the new aokp on the external sdcard, reboot back into recovery and choose to install from sdcard (NOT from internal sdcard since you cannot boot up). Then flash the new aokp.
Another thought is did you make a nandroid backup? You should be able to get into recovery and restore from internal sdcard if you made a nandroid. This will get you back to where you were originally. Then redownload the aokp and check that the md5 matches EXACTLY. Then flash the newer aokp. You are not bricked at this point. Follow up here after you try my suggestions and let us know how it went.
Sent from My SGH-I777 Running Spiderman Themed AOKP or Spiderman Themed CM10
pisky1 said:
I'm thinking if i can get into download mode, i can follow the steps that the thread i've been following far give you for status 7 errors, and get my back up and running how it was.
Just need to know how lol.
Click to expand...
Click to collapse
Covered thousands of times in this forum.
Volume up and down plus power gets to recovery
Volume up and down plus plug in USB gets you to download. These should be the first things anyone knows before Modding their phone.
Sent from my Nexus 7 using Tapatalk 2
Pirateghost said:
Covered thousands of times in this forum.
Volume up and down plus power gets to recovery
Volume up and down plus plug in USB gets you to download. These should be the first things anyone knows before Modding their phone.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I was referred to this thread nearly a year ago by a friend, and i've had no issues so far, so i kind of arrogantly didn't look too far into things like that, which now i'm obviously regretful of. I've gotten into Download mode, am i right in assuming that download mode only accesses stuff on the external SD< b/c i cannot access my internal drive when entering it, which would make my previous theory about being able to follow the standard Status 7 recovery tutorial if i could get into download mode, wrong.
Sadly to respond to the other poster, no again, with the same about not knowing how to get into download mode, i never made a nandroid, mainly because almost everything on my phone is disposable, i don't take pictures really at all, and all my numbers/contacts are synced up to GMAIL, i guess i never thought of a situation arising like this where that didn't matter, i simply wanted to use my phone lol.
Back to a previous comment you said that i now realize i answered too hastily, about if i have the I777, when my phone boots up it says I9100, but what's weird, and i said it before i was referred here by a good friend of mine who knows my phone, and is a much more experienced rooter than i am, so i guess i just took their word for it, and as i said i've flashed ROM's on this phone for nearly a year now, and it's been seamless, not a single problem up until this point, so im wondering if the i777 vs i9100 conflict caused anything.
[EDIT:] Disregard the following comments... I don't believe they will help.
---------------------------------
I've got the answer to all of your questions:
Stickies and Search. READ.
I'm absolutely 100% serious and positively right. Your problems are very well known and thus very well documented.
Try searching in Google:
Status 7 error I777 xda
I777 shows i9100 on boot xda
Any other queries followed by "xda"
Clay
Team Pirate
Sent from my PINK GSwagger2
clay101eve said:
[EDIT:] Disregard the following comments... I don't believe they will help.
---------------------------------
I've got the answer to all of your questions:
Stickies and Search. READ.
I'm absolutely 100% serious and positively right. Your problems are very well known and thus very well documented.
Try searching in Google:
Status 7 error I777 xda
I777 shows i9100 on boot xda
Any other queries followed by "xda"
Team Pirate
Sent from my PINK GSwagger2
Click to expand...
Click to collapse
I want to thank everyone on this thread for their patience, and their answers, i actually used a guide from another site because it had gotten really good feedback, the only problem is it does not have the I777 official firmware, but rather the i9100, for the international version of the phone so my back key does not work, i am currently looking for the correct version, on this thread, and across the internet if anyone can find the official firmware let me know, thanks in advance, and again thanks everyone who answered in the past, your patience and answers were greatly appreciated.
pisky1 said:
I want to thank everyone on this thread for their patience, and their answers, i actually used a guide from another site because it had gotten really good feedback, the only problem is it does not have the I777 official firmware, but rather the i9100, for the international version of the phone so my back key does not work, i am currently looking for the correct version, on this thread, and across the internet if anyone can find the official firmware let me know, thanks in advance, and again thanks everyone who answered in the past, your patience and answers were greatly appreciated.
Click to expand...
Click to collapse
Forums have these things called stickies. Within these stickies are tidbits of information .. typically these tidbits are important enough to warrant the sticky status and as such should be read carefully. All the info you seek is contained within these stickies
Sent from my Nexus 7 using Tapatalk 2
Just get into recovery mode and do the three wipes to fix the bootloop. If it doesn't, DOWNLOAD and FLASH others rom from the original development thread and then install the latest aokp from task to prevent the error status 7. otherwise, please edit the build.prop
Sent from my SGH-I777 using xda premium
pisky1 said:
I want to thank everyone on this thread for their patience, and their answers, i actually used a guide from another site because it had gotten really good feedback, the only problem is it does not have the I777 official firmware, but rather the i9100, for the international version of the phone so my back key does not work, i am currently looking for the correct version, on this thread, and across the internet if anyone can find the official firmware let me know, thanks in advance, and again thanks everyone who answered in the past, your patience and answers were greatly appreciated.
Click to expand...
Click to collapse
For one you could have easily found the sticky threads with the i777 stock firmware. Second now that you flashed a i9100 I HOPE it didn't contain the boot loaders for the i9100. But I guess you will find out at some point I'm sure.
Like I said EVERYTHING you need CAN and ONLY should be found HERE on xda developers. Anything else is a crap shoot. Maybe you will get lucky and maybe not.
now that you flashed the i9100 firmware you will have to actually READ FURTHER than you did before to see HOW to fix your button issue. It can be easy if you know what your doing or can be hard if you don't. Good luck. I'm out...
Sent from my SCH-I800 using xda premium
RockRatt said:
For one you could have easily found the sticky threads with the i777 stock firmware. Second now that you flashed a i9100 I HOPE it didn't contain the boot loaders for the i9100. But I guess you will find out at some point I'm sure.
Like I said EVERYTHING you need CAN and ONLY should be found HERE on xda developers. Anything else is a crap shoot. Maybe you will get lucky and maybe not.
now that you flashed the i9100 firmware you will have to actually READ FURTHER than you did before to see HOW to fix your button issue. It can be easy if you know what your doing or can be hard if you don't. Good luck. I'm out...
Sent from my SCH-I800 using xda premium
Click to expand...
Click to collapse
I simply did a factory reset, then install the i777 stock firmware, and i'm up and running, i'm gonna do this for awhile i intend on getting a new phone in the next couple months, at that point i'll go back to rooting. So nothing to worry about, thanks again for everyone's help.
The title says it all. Nothing good can come of flashing with Odin except returning to stock. Stick with CWM or TWRP flashable zip files. If you disregard this message you will end up with a locked device, or even worse, a hard bricked device. Please use Odin as a factory restore tool only. I'm concerned that after unlock using our methods that people will flash the wrong thing and cause problems in the future.
The unlock method we have provided is not a standard Bootloader Unlock. It is an IROM unlock. This means you can quite literally flash anything to your device without any sort of signature checks. It is important that you stay safe and try to stay away from Odin unless absolutely necessary.
Thanks for all the hard work
Sent from my SCH-I605 using xda app-developers app
Excellent words of advice from an ERD who KNOWS what's he's talking about... Please take his advice everyone... It will save you A LOT of pain...
Stickied
Thanks for your hours of work. People WILL screw this up, unfortunately.
Sent from my SCH-I605 using xda app-developers app
thejron said:
Thanks for your hours of work. People WILL screw this up, unfortunately.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Yup! I can already see the threads starting.... It is good to know that we can still use Odin though cause I was under the impression that Odin was a no-go at this point... So flashing the factory image from imnuts would be the best resort to get back to stock if we needed to return a device?
shojus said:
Yup! I can already see the threads starting.... It is good to know that we can still use Odin though cause I was under the impression that Odin was a no-go at this point... So flashing the factory image from imnuts would be the best resort to get back to stock if we needed to return a device?
Click to expand...
Click to collapse
yes...check my guide out! I have step by step instructions that clearly state what and what not to do!!
droidstyle said:
yes...check my guide out! I have step by step instructions that clearly state what and what not to do!!
Click to expand...
Click to collapse
Thanks buddy! I just checked it out and I am very thankful for your guides as it has helped me and MANY others! I have thanked so many people that my limit is up (for the day) but I appreciate your time that you have put forth to helping people! :good:
I know I'm off topic. I'm not an owner of the note 2 but wanted to say awesome signature to the OP. From one vet to another thank you
Sent from my LG-LS970 using xda premium
droidstyle said:
yes...check my guide out! I have step by step instructions that clearly state what and what not to do!!
Click to expand...
Click to collapse
I still have plenty of "Thanks" so Thanks, and I am gonna study this weekend, hopefully by then the other issues folks have been having will at least be identified if not corrected.. then it's freedom for me!!
AdamOutler said:
The title says it all. Nothing good can come of flashing with Odin except returning to stock. Stick with CWM or TWRP flashable zip files. If you disregard this message you will end up with a locked device, or even worse, a hard bricked device. Please use Odin as a factory restore tool only. I'm concerned that after unlock using our methods that people will flash the wrong thing and cause problems in the future.
The unlock method we have provided is not a standard Bootloader Unlock. It is an IROM unlock. This means you can quite literally flash anything to your device without any sort of signature checks. It is important that you stay safe and try to stay away from Odin unless absolutely necessary.
Click to expand...
Click to collapse
Adam- but we ARE ok flashing with Odin so we can retrun to complete stock correct? your not saying that doing that may completely brick are phones are you? just want to be clear. i only use ODIN to go complete stock..
thank you for your work
dvigue said:
Adam- but we ARE ok flashing with Odin so we can retrun to complete stock correct? your not saying that doing that may completely brick are phones are you? just want to be clear. i only use ODIN to go complete stock..
thank you for your work
Click to expand...
Click to collapse
"Please use Odin as a factory restore tool only"
In Androidstyle's guide thread, Adam asked him to point the unlock guide to his unlock thread, but I don't see an unlock thread from Adam, only the Revision3 thread which has no steps to unlock. I see the video Adam made, but my understanding is that the process has changed and the links to download Adam's ROM are dead on the Youtube page. Anyone have the link to Adam's unlock step by step guide?
wmaudio said:
In Androidstyle's guide thread, Adam asked him to point the unlock guide to his unlock thread, but I don't see an unlock thread from Adam, only the Revision3 thread which has no steps to unlock. I see the video Adam made, but my understanding is that the process has changed and the links to download Adam's ROM are dead on the Youtube page. Anyone have the link to Adam's unlock step by step guide?
Click to expand...
Click to collapse
It's in "Verizon Galaxy Note II Android Original Development". Go up one level and you'll see it. There are only two threads there so it shouldn't be too hard to find.
I don't mean to sound mean but if you really can't figure out how to get to his unlock thread do you really think it's a good idea to be unlocking your bootloader? Maybe you should just stick to a rooted image and read up and learn for awhile before jumping in over your head
Sent from my SCH-I605 using xda app-developers app
LordRalh3 said:
I don't mean to sound mean but if you really can't figure out how to get to his unlock thread do you really think it's a good idea to be unlocking your bootloader? Maybe you should just stick to a rooted image and read up and learn for awhile before jumping in over your head
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
To be fair, the distinction between "Android development" and "Original Android development" is new for many of us. I, too, was wondering how to get back to this thread since I tend to browse XDA through bookmarks instead of the site hierarchies. I didn't realize there was an "original Android development" section until after I double checked the name on the thread jumper. It's not that one is technologically illiterate (I got through all this in one fell swoop with no issues and have rooted and unlocked every phone I've owned since the G1), it's just that it's different. Last device I had didn't have a section for original development, so it wasn't immediately obvious to me (though I quickly understood what it was for). so cut him some slack and just kindly point him to the right direction. I know you said you weren't trying to sound mean, but if you really weren't trying to sound mean you could have just helped him out without all of the extra, unnecessary commentary. You know what they say about assumptions, after all.
Just got the Note 2 on verizon and loving it so much I'm going to hold off for a bit before unlocking & rooting. Normally on all my android phones that is done day 1... but this time w/ the dev community just now unlocking it, I think I'm going to wait a few weeks.
In context, imnuts has put out a Recovery flash-able version of CWM. If one tries his CWM but wants to go back to TWRP then currently it seems that one need to ODIN it. To Adam Outler's point it would be safer to have a Recovery flash-able version of TWRP. [?]
AdamOutler said:
The title says it all. Nothing good can come of flashing with Odin except returning to stock. Stick with CWM or TWRP flashable zip files. If you disregard this message you will end up with a locked device, or even worse, a hard bricked device. Please use Odin as a factory restore tool only. I'm concerned that after unlock using our methods that people will flash the wrong thing and cause problems in the future.
The unlock method we have provided is not a standard Bootloader Unlock. It is an IROM unlock. This means you can quite literally flash anything to your device without any sort of signature checks. It is important that you stay safe and try to stay away from Odin unless absolutely necessary.
Click to expand...
Click to collapse
Does the same go for Heimdall aswell then?
trevd said:
Does the same go for Heimdall aswell then?
Click to expand...
Click to collapse
Yes because it does the same job as ODIN but on a different operating system.
Sent from VZW Note 2
Clarkkent434 said:
Yes because it does the same job as ODIN but on a different operating system.
Sent from VZW Note 2
Click to expand...
Click to collapse
That's what I figured , I thought I'd ask the dumb question to explicitly clarify it.
I have a vzw max and i recently reverted everything back to stock and unrooted; or so i believed. The kernel still says 3.4.10 etc. and the phone has no signal nor can it find my location. It keeps rebooting every 30 secs or so and no matter what mode I put the device into, it isn't recognized by my PC. the bootloader is locked and I am S-Off. This all happened after I tried to flash CWM's HTC M7 recovery because the Max isn't listed and I couldn't figure out how to flash TWRP. Help please because this is getting crazy and I can't figure out what to do...
bump
nobody at all eh...
LocBox said:
nobody at all eh...
Click to expand...
Click to collapse
So if you boot to bootloader keeps rebooting there too?
Sent from my Nexus 7 using Tapatalk
dude i feel for you.
why did you put m7 cwm on there. clearly not for this device.
can you still get to bootloader? if you can flash the correct recovery! then find a backup someone has done and restore. or flash the correct boot.img
dude here's the correct recovery
http://forum.xda-developers.com/showthread.php?t=2498749
Well the only problem is my any pc won't even detect that it's connected when I plug it into it. So I can't use any fastboot or adb methods and even when I put the phone into fastboot mode it doesn't connect either. I'm able to put it into bootloader mode and it doesn't reset but still no connection; just charges. I've tried flashing through stock recovery manually and it aborts every attempt I'm assuming because my BL is locked..
No it doesn't
dottat said:
So if you boot to bootloader keeps rebooting there too?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
no it doesnt'
LocBox said:
no it doesnt'
Click to expand...
Click to collapse
Ok. I know how we can fix then. Let me pm you
Sent from my HTC6600LVW using Tapatalk
Thanks
Dottat has helped me and not a moment too soon, I was seconds from printing out the return label for HTC and sending it in for a refurb exchange. smbh. thanks man.:good:
dottat said:
Ok. I know how we can fix then. Let me pm you
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
hey mate, whats the secret sauce
Flashing the zip from bootloader ?
pradeepvizz said:
hey mate, whats the secret sauce
Flashing the zip from bootloader ?
Click to expand...
Click to collapse
I agree, it would be nice for that stuff to be posted on here so we can all see it. And maybe not have to ask for help ourselves.
JBS976 said:
I agree, it would be nice for that stuff to be posted on here so we can all see it. And maybe not have to ask for help ourselves.
Click to expand...
Click to collapse
haha, okay chill mate. i was kidding there.
i am guessing it was full flash of rom / kernel using the zip in the bootloader.
pradeepvizz said:
haha, okay chill mate. i was kidding there.
i am guessing it was full flash of rom / kernel using the zip in the bootloader.
Click to expand...
Click to collapse
That is correct, full flash from bootloader. 0P3PIMG.zip on root of sd. and boom with some pow.
JBS976 said:
I agree, it would be nice for that stuff to be posted on here so we can all see it. And maybe not have to ask for help ourselves.
Click to expand...
Click to collapse
I wasn't trying to hide anything. I typically will walk a user through using the encrypted RUU (my person preference as i know it's intact) to restore their phone as long as it can boot to bootloader. I take it offline because the mods didn't take kindly to the encrypted RUU being posted in the past. I don't have an answer as to why that was case so I just keep that part off the main threads. If its someone in need (like the OP) i have no problem helping one on one.
dottat said:
I wasn't trying to hide anything. I typically will walk a user through using the encrypted RUU (my person preference as i know it's intact) to restore their phone as long as it can boot to bootloader. I take it offline because the mods didn't take kindly to the encrypted RUU being posted in the past. I don't have an answer as to why that was case so I just keep that part off the main threads. If its someone in need (like the OP) i have no problem helping one on one.
Click to expand...
Click to collapse
It's cool, I didn't mean it to sound like anything was being hidden, I just like to read all this stuff and take it in for future reference as I don't want to bother you guys unless I just cannot figure it out on my own. Believe me i really appreciate all you guys do on here as this is an invaluable resource if people take the time to read through things. I was unaware that they didn't want the RUU's on here which really sucks because they are nice to have like I had them for the rezound and it came in real handy at times. Not having them for this device yet has been one of the reasons I have been hesitant to do much else than to S-OFF and root. At this point I guess I am waiting for the OTA Kit Kat update then I will probably dive in.
Bryon
JBS976 said:
It's cool, I didn't mean it to sound like anything was being hidden, I just like to read all this stuff and take it in for future reference as I don't want to bother you guys unless I just cannot figure it out on my own. Believe me i really appreciate all you guys do on here as this is an invaluable resource if people take the time to read through things. I was unaware that they didn't want the RUU's on here which really sucks because they are nice to have like I had them for the rezound and it came in real handy at times. Not having them for this device yet has been one of the reasons I have been hesitant to do much else than to S-OFF and root. At this point I guess I am waiting for the OTA Kit Kat update then I will probably dive in.
Bryon
Click to expand...
Click to collapse
Check your pm shortly. S-off later today ?
Sent from my HTC6600LVW using Tapatalk
I have searched around, and have tried to find a solution, but I cannot seem to figure out a way to fix this issue.
Rooted the phone, then tried to install TWRP via goo manager, with the intention of perhaps putting KitKat on the phone, but the custom recovery installation seemed to fail, and I was able to get the phone to boot back up by;
I ended up booting into download mode (volume down + home +power) and then I got prompted for did I really want to do that, I responded no and the phone booted up.
I found that helpful post here: http://forums.androidcentral.com/sa...ck-after-installing-twrp-via-goo-manager.html
So now I am using the phone, and rebooting the phone works fine. But an OTA update is out, and phone says time to install, and I attempted to do so, but end up back at the same screen before, and have to boot into download mode again to get the phone to start back up.
I am not sure of what happened to the phone to cause this, but something obviously did. Hoping someone can point me in the right direction for at the bare minimum allowing me to install updates on the phone in the future.
Any help would be greatly appreciated.
Sytheii said:
I have searched around, and have tried to find a solution, but I cannot seem to figure out a way to fix this issue.
Rooted the phone, then tried to install TWRP via goo manager, with the intention of perhaps putting KitKat on the phone, but the custom recovery installation seemed to fail, and I was able to get the phone to boot back up by;
I ended up booting into download mode (volume down + home +power) and then I got prompted for did I really want to do that, I responded no and the phone booted up.
I found that helpful post here: http://forums.androidcentral.com/sa...ck-after-installing-twrp-via-goo-manager.html
So now I am using the phone, and rebooting the phone works fine. But an OTA update is out, and phone says time to install, and I attempted to do so, but end up back at the same screen before, and have to boot into download mode again to get the phone to start back up.
I am not sure of what happened to the phone to cause this, but something obviously did. Hoping someone can point me in the right direction for at the bare minimum allowing me to install updates on the phone in the future.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Unless you are a mdk firmware. ..you can't use goo manager. ..or install twrp or CWM ..The ONLY recovery is Safestrap. ..Please read some of the threads here
sent by safestrap enabled bajarom
decaturbob said:
Unless you are a mdk firmware. ..you can't use goo manager. ..or install twrp or CWM ..The ONLY recovery is Safestrap. ..Please read some of the threads here
sent by safestrap enabled bajarom
Click to expand...
Click to collapse
How would I determine if I am a mdk firmware or not?
If I could install "safestrap" recovery, would that enable me to install the OTA updates? or at least manually install them via the recovery?
Just trying to undo whatever i botched...which i am still sort of unclear on...
I appreciate the help, I just am not sure what the next step is...can you point me in the right direction? Can you postulate what might have occurred when my failed install of TWRP happened, and keeping in mind the method of how i got the phone to start back up again, then deduce what to do to make it right?
My apologies and sincerest appreciation.
Sytheii said:
How would I determine if I am a mdk firmware or not?
If I could install "safestrap" recovery, would that enable me to install the OTA updates? or at least manually install them via the recovery?
Just trying to undo whatever i botched...which i am still sort of unclear on...
I appreciate the help, I just am not sure what the next step is...can you point me in the right direction? Can you postulate what might have occurred when my failed install of TWRP happened, and keeping in mind the method of how i got the phone to start back up again, then deduce what to do to make it right?
My apologies and sincerest appreciation.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2606501
take a couple days and read this thread and the links found in this thread. Then spend another couple days reading a multitude of threads in these forums
decaturbob said:
http://forum.xda-developers.com/showthread.php?t=2606501
take a couple days and read this thread and the links found in this thread. Then spend another couple days reading a multitude of threads in these forums
Click to expand...
Click to collapse
Fair enough. I was just hoping that from what I posted, someone would be like...oh you just need to do this, to revert back.
I can understand your stance on wanting to make newcomers sieve and sift through the info in the sea that is XDA for their one nugget, but sometimes asking a simple question, and receiving a simple answer, enriches the Internet's pool of cached available spot on search queries, and makes it easier for others who have botched a process to rectify.
I'll start with the thread you recommend, and see if I can't get there solo.
Thank you.
Sent from my SCH-I545 using Tapatalk
Sytheii said:
Fair enough. I was just hoping that from what I posted, someone would be like...oh you just need to do this, to revert back.
I can understand your stance on wanting to make newcomers sieve and sift through the info in the sea that is XDA for their one nugget, but sometimes asking a simple question, and receiving a simple answer, enriches the Internet's pool of cached available spot on search queries, and makes it easier for others who have botched a process to rectify.
I'll start with the thread you recommend, and see if I can't get there solo.
Thank you.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
The more knowledge you gain on your phone will only help you.
sent by safestrap enabled bajarom
decaturbob said:
The more knowledge you gain on your phone will only help you.
sent by safestrap enabled bajarom
Click to expand...
Click to collapse
True true.
Sent from my SCH-I545 using Tapatalk
I would Odin one of these: http://forum.xda-developers.com/showthread.php?t=2735172
Sent from my SCH-I545 using Tapatalk
First off, thanks so much to anyone who helps me out here, Ive been trying to install the ROM below on my phone for many, MANY hours.
[ROM]KOT49H【4.4.3】AOSP Official Google Edition 【Verizon!】06-13-2014
http://forum.xda-developers.com/showthread.php?t=2643031
I have:
SCH-I545
4.4.2
VRUFNC5
I managed to get it rooted but I can't for the life of me figure out how to get the phone into a non stock recovery. every time I try, it goes into the stock recovery, even if I choose reboot recovery from rom manager. I tried flashing the rom from the stock recovery but that did not work. If someone could please point me in the right direction for a recovery program (loki) that will work with my phone I would really appreciate it.
Im hoping the problem isn't with the root but I havn't had any other issues. I downloaded:
UPDATE-SuperSU-v1.99r4
Im sorry if this is noob stuff but I used to do it all the time with my old DX and now I can barely get it rooted! (took hours) proper recovery is the next step toward a GPE ROM I hope. Thanks, a bunch, nap time
Tron4949 said:
First off, thanks so much to anyone who helps me out here, Ive been trying to install the ROM below on my phone for many, MANY hours.
[ROM]KOT49H【4.4.3】AOSP Official Google Edition 【Verizon!】06-13-2014
http://forum.xda-developers.com/showthread.php?t=2643031
I have:
SCH-I545
4.4.2
VRUFNC5
I managed to get it rooted but I can't for the life of me figure out how to get the phone into a non stock recovery. every time I try, it goes into the stock recovery, even if I choose reboot recovery from rom manager. I tried flashing the rom from the stock recovery but that did not work. If someone could please point me in the right direction for a recovery program (loki) that will work with my phone I would really appreciate it.
Im hoping the problem isn't with the root but I havn't had any other issues. I downloaded:
UPDATE-SuperSU-v1.99r4
Im sorry if this is noob stuff but I used to do it all the time with my old DX and now I can barely get it rooted! (took hours) proper recovery is the next step toward a GPE ROM I hope. Thanks, a bunch, nap time
Click to expand...
Click to collapse
First off - did you read any of the stickies about our phone? Unless you are on the MDK bootloader, you cannot install a custom recovery nor can you install this rom. You must use Safestrap to load any custom TW rom - no AOSP or CM based roms at this time.
zeb carter said:
First off - did you read any of the stickies about our phone? Unless you are on the MDK bootloader, you cannot install a custom recovery nor can you install this rom. You must use Safestrap to load any custom TW rom - no AOSP or CM based roms at this time.
Click to expand...
Click to collapse
Stickies? I'm a long time reader but first time poster because this one did my head in so bad, but I do not know what the stickies are. I'll look for them. So basically your telling me I have to do the whole downgrade method if I want to do this? Or it's just not possible at this time? Thanks for the time.
Tron4949 said:
Stickies? I'm a long time reader but first time poster because this one did my head in so bad, but I do not know what the stickies are. I'll look for them. So basically your telling me I have to do the whole downgrade method if I want to do this? Or it's just not possible at this time? Thanks for the time.
Click to expand...
Click to collapse
It is possible to install this rom, you just have to use Safestrap.
This is how to install:
Note: SafeStrap doesn't work with encryption turned on (disabled by default). If you don't know if you don't have encryption on/your phone isn't a business phone (in which case you shouldn't be doing this!!!) then you most likely don't have encryption on!!
6. Use this app to change your SELinux mode to "Permissive" https://play.google.com/store/apps/details?id=com.mrbimc.selinux, this is required to use SafeStrap
7. Install SafeStrap 3.72 APK from this thread http://forum.xda-developers.com/show....php?t=2448925, NOT 3.71 FROM THE VERIZON THREAD!!! Then click install in the SafeStrap App
8. Install https://play.google.com/store/apps/details?id=eu.chainfire.supersu and update your binaries
Then to enter safestrap while rebooting hit menu key, from there you can flash your rom.
Tron4949 said:
Stickies? I'm a long time reader but first time poster because this one did my head in so bad, but I do not know what the stickies are. I'll look for them. So basically your telling me I have to do the whole downgrade method if I want to do this? Or it's just not possible at this time? Thanks for the time.
Click to expand...
Click to collapse
Stickies are at the top of each forum because they considered to important enough for all to read........
Sent from my SCH-I545 using Tapatalk
wzhigaylo said:
It is possible to install this rom, you just have to use Safestrap.
This is how to install:
Note: SafeStrap doesn't work with encryption turned on (disabled by default). If you don't know if you don't have encryption on/your phone isn't a business phone (in which case you shouldn't be doing this!!!) then you most likely don't have encryption on!!
6. Use this app to change your SELinux mode to "Permissive" https://play.google.com/store/apps/details?id=com.mrbimc.selinux, this is required to use SafeStrap
7. Install SafeStrap 3.72 APK from this thread http://forum.xda-developers.com/show....php?t=2448925, NOT 3.71 FROM THE VERIZON THREAD!!! Then click install in the SafeStrap App
8. Install https://play.google.com/store/apps/details?id=eu.chainfire.supersu and update your binaries
Then to enter safestrap while rebooting hit menu key, from there you can flash your rom.
Click to expand...
Click to collapse
This does not work with safestrap its said over and over in the thread that it will not work. I tried it anyway per what you said and it wont get past the boot animation. You have to have an mdk bootloader and be able to install custom recovery for this to actually work.
techguy2002 said:
This does not work with safestrap its said over and over in the thread that it will not work. I tried it anyway per what you said and it wont get past the boot animation. You have to have an mdk bootloader and be able to install custom recovery for this to actually work.
Click to expand...
Click to collapse
thank you for that, which is why I have not messed with safestrap..its one of the first things in the post. so I guess that brings me back to where I started. Do I need to use the down grade method? If I do will it even work? and can somebody please point me in the direction of a proper (loki) recovery that I can flash and will work with my hardware. Thanks
EDIT -
believe me when I say I wouldn't be asking if I hadn't checked hundreds of threads already.
in case it helps, the end goal here is to get the GPE ROM on my phone. I'm rooted with towel. Ive gone in so many circles at this point I need someone who actually has done it or knows what they are talking about. Thanks!!!
Tron4949 said:
thank you for that, which is why I have not messed with safestrap..its one of the first things in the post. so I guess that brings me back to where I started. Do I need to use the down grade method? If I do will it even work? and can somebody please point me in the direction of a proper (loki) recovery that I can flash and will work with my hardware. Thanks
EDIT -
believe me when I say I wouldn't be asking if I hadn't checked hundreds of threads already.
in case it helps, the end goal here is to get the GPE ROM on my phone. I'm rooted with towel. Ive gone in so many circles at this point I need someone who actually has done it or knows what they are talking about. Thanks!!!
Click to expand...
Click to collapse
You can't do loki...Please do some reading...unless u have a mdk firmware...u can only do safestrap.
Sent from my SCH-I545 using Tapatalk
decaturbob said:
You can't do loki...Please do some reading...unless u have a mdk firmware...u can only do safestrap.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
If I downgrade to MDK firmware (I believe you can with surges method??), then I will be able to do this, correct? (without dealing with safestrap) by "this" I mean of course, finding a different recovery and flashing the GPE ROM.
If you read the top you would know that I spent MANY hours, reading MANY different threads and sites, that is why I am in the help section now. I'm not exaggerating when I say I spent from 11PM last night until 6:30 this morning with only a few breaks. I've flashed and re-flashed a million different files trying to get the results I wanted (bricked several times) and nothing worked, so this is my last resort
Tron4949 said:
If I downgrade to MDK firmware (I believe you can with surges method??), then I will be able to do this, correct? (without dealing with safestrap) by "this" I mean of course, finding a different recovery and flashing the GPE ROM.
If you read the top you would know that I spent MANY hours, reading MANY different threads and sites, that is why I am in the help section now. I'm not exaggerating when I say I spent from 11PM last night until 6:30 this morning with only a few breaks. I've flashed and re-flashed a million different files trying to get the results I wanted and nothing worked, so this is my last resort
Click to expand...
Click to collapse
You can NOT downgrade to mdk....u are confusing it with mk2.
Sent from my SCH-I545 using Tapatalk
decaturbob said:
You can NOT downgrade to mdk....u are confusing it with mk2.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I see. So unless someone has a GPE ROM that works with safestrap, I am out of luck until a downgrade method, or some other alternate recovery mthod is found? I appreciate your time and help!
Tron4949 said:
I see. So unless someone has a GPE ROM that works with safestrap, I am out of luck until a downgrade method, or some other alternate recovery mthod is found? I appreciate your time and help!
Click to expand...
Click to collapse
Yep
Sent from my SCH-I545 using Tapatalk
Understood. The learning curve has been very steep, as the last time I did this stuff there was only one version of each phone, sbf's were still around (don't know if they are or not anymore but it's not what I have to use to unbrick now) etc. Thanks so much for the replies and ill keep my eyes open for solutions as they are developed. I WILL have google play edition on my phone someday, and I thank all the dev's ahead of time for their hard work!