Related
Hey everyone, I started this guide myself after coming to the conclusion that there wasn't any real clear or even good guide to flashing a recovery after having to use the HTCDEV tool to unlock your bootloader. If you had to use the HTCDEV tool method it is becasue your bootloader is version 1.50 and the revolutionary method will not work for you at this point in time.
This is my own guide I wrote and is soley my own work despite what some insecure noobs think on these forums. I'm not claiming to have discovered this method first, I'm just sharing my knowledge in a neat little guide to just be of any help to those who need it!
Please visit here if you havent used the HTCDEV Tool yet to unlock your bootloader. [http://htcdev.com/bootloader/]
After using the HTCDEV tool you will need
a recovery and Superuser permissions to have root access. The only recovery I was able to flash and get working correctly using this method was the exact version of cwm that you can download from this guide. I was not able to get TWRP or any other recovery to work this way...
**make sure you have ADB set up on your computer (download AndoridSDK and open up SDK Manager and install the add on packages)**
Step 1: Download the cwm zip from this post and place the .img file in your
androidsdk/tools folder. Then download the su zip folder and place this on the root of your SD card
Step 3: Reboot the phone into bootloader (Vol down + Power), then select fastboot usb next.
Step 4: open up your command prompt and enter these lines of command
Code:
CD C:\AndroidSDK\tools
(your's might look different)
Code:
fastboot flash recovery c:\androidsdk\tools\cwm-4.0.1.4-shooter(1).img
**you should now see that it will flash the recovery in your command promt window**
Step 5: When its done flashing the recovery go ahead and boot into recovery and flash the su zip file so you will have root permissions!!
You should be done after this you can flash roms or reboot normally.
Nevermind.
Couple things wrong/could be done better with this post, no offense, just things you'll want to correct or add.
~ You're going to want to explain how to get ADB going, because as of the past few versions, it's very convoluted to get.
~ You can't directly reboot into Fastboot (at least, not without being fully rooted already). The phone must be fully turned off, and before you even do that, you need to turn off the "fast boot" option in the Android power settings completely off. That "fast boot" option is completely unrelated to Fastboot mode but if you leave "fast boot" checked on, the phone doesn't fully power off when you press and hold power.
~ As far as formatting goes, you'll want to wrap the command prompt lines in code tags which are these: [.code].[./code] (no periods). That way, it looks like this:
Code:
cd C:\AndroidSDK\tools
The same goes with the fastboot command, because otherwise it's confusing as to what the entered code really should be.
~ You've packaged the recovery as a RAR, when in reality, you don't actually need to package it up as anything, you can directly upload the img. Also, for the sake of convenience, because not everyone has the same ADB path (and by extension, not everyone will be able to copy and paste the command you put up) you can rename the image to just "recovery.img" because when you're tying the fastboot recovery flash command out, it's irritating to type out the full name of the recovery.
The HTC unlock method does not give you S-Off. You'll still be S-On, but you're able to install a recovery then flash the SU zip. Its important to note that the newest version of cwm that I was able to get working was 4.0.1.4. I was not able to get any version of TWR working. You are also unable to flash custom boot.img's, making kernel modification impossible.
Thanks for the input! I will revise the guide just wanted something quick for people out there that were thinking that they could not have any recovery after using the htc dev tool, and thus not being able to flash any custom roms.
I never got TWRP flashed either, or any other version of cwm except the one I posted on the thread...but its better than no recovery and it gives you the ability to obtain root access so you can also use rooted apps.
I have now used both revolutionary and the HTCDEV tool multiple times, the HTCDEV tool being a bigger pain in the rear than I had figured but it was only because no other recovery would install except for cwm via fastboot adb.
As for custom kernels, maybe using a rom with a baked in kernel would be a good option since it would flash together with the rom.
Also, It would not let me attatch the file as a .img file there were errors so I had to zip them in order to attatch them in my thread.
Unknown_Hero said:
Thanks for the input! I will revise the guide just wanted something quick for people out there that were thinking that they could not have any recovery after using the htc dev tool, and thus not being able to flash any custom roms.
I never got TWRP flashed either, or any other version of cwm except the one I posted on the thread...but its better than no recovery and it gives you the ability to obtain root access so you can also use rooted apps.
I have now used both revolutionary and the HTCDEV tool multiple times, the HTCDEV tool being a bigger pain in the rear than I had figured but it was only because no other recovery would install except for cwm via fastboot adb.
As for custom kernels, maybe using a rom with a baked in kernel would be a good option since it would flash together with the rom.
Click to expand...
Click to collapse
...why did you use the HTC Dev tool after Revolutionary? Do you realize what you've done by doing that?
I hope what you meant was that you had the 2.3.4 stock update and tried to use Revolutionary, found out it didn't work, and then tried the HTC Dev tool, because running the HTC Unlock after successfully using the Revolutionary tool is not the best idea on the planet.
The downside to using HTC's Unlock (for those who think 'oh, i have root and recovery, i'm ok) is that you can't use custom kernels or updated Radio stacks.
Baked in kernel won't matter, the boot partition (as far as I can tell) is still locked.
So you just troll chat rooms and kang people's work and claim it as your own eh? Way to kang this entire writeup. You didn't figure this out.
Sent from my rooted, Dark Horse INFECTED Synergy bolt running Ziggys latest.
First off I didnt use both rooting methods...I used revolutionary on my own evo and had to use the devtool on a friends....I'm not that stupid I know the difference between the two. The reason I started this post was because when I was having difficulties when flashing a recovery on my freinds phone after using the dev tool I couldn't find any help or thread on getting this to work. Maybe I didn't look hard enough but the only help I got was off android forums and there was a real vague description on getting the recovery to flash...I was trying to help not troll...nor did I calim this was MY discovery at all in my thread lol.
Unknown_Hero said:
First off I didnt use both rooting methods...I used revolutionary on my own evo and had to use the devtool on a friends....I'm not that stupid I know the difference between the two. The reason I started this post was because when I was having difficulties when flashing a recovery on my freinds phone after using the dev tool I couldn't find any help or thread on getting this to work. Maybe I didn't look hard enough but the only help I got was off android forums and there was a real vague description on getting the recovery to flash...I was trying to help not troll...nor did I calim this was MY discovery at all in my thread lol.
Click to expand...
Click to collapse
That's ok, I assumed that you didn't run both on your phone, I just wanted to make sure. I think the guy above me might be going overboard though.
Unknown_Hero said:
First off I didnt use both rooting methods...I used revolutionary on my own evo and had to use the devtool on a friends....I'm not that stupid I know the difference between the two. The reason I started this post was because when I was having difficulties when flashing a recovery on my freinds phone after using the dev tool I couldn't find any help or thread on getting this to work. Maybe I didn't look hard enough but the only help I got was off android forums and there was a real vague description on getting the recovery to flash...I was trying to help not troll...nor did I calim this was MY discovery at all in my thread lol.
Click to expand...
Click to collapse
Liar. You copied everything out of the Synergy chat room after someone else did it and there are chat logs to prove you kanged it.
Sent from my rooted, Dark Horse INFECTED Synergy bolt running Ziggys latest.
Thank you I appreciate constructive criticism I know you were just trying to help and my post was pretty noob I don't know why McLabia is trippen though...oh well not worried about it I have much to learn and you got to start somewhere!
McLabia said:
Liar. You copied everything out of the Synergy chat room after someone else did it and there are chat logs to prove you kanged it.
Sent from my rooted, Dark Horse INFECTED Synergy bolt running Ziggys latest.
Click to expand...
Click to collapse
Your joking right???? I have never even used synergy chat room bro...I created this noob post myself and im being 100 percent honest you need to chill and be a little respectful. I'm for sure not a liar and did not "Kank" this post from anyone dude why would I need to steal info about flashing a recovery??? Wow, some people have their pants on way too tight lol.
Unknown_Hero said:
Thank you I appreciate constructive criticism I know you were just trying to help and my post was pretty noob I don't know why McLabia is trippen though...oh well not worried about it I have much to learn and you got to start somewhere!
Click to expand...
Click to collapse
Im not tripping. I'm pointing out the fact that you straight trolled the chat and the posted this like it was yours. You did nothing. Someone else did. Straight up thief.
Sent from my rooted, Dark Horse INFECTED Synergy bolt running Ziggys latest.
McLabia said:
Im not tripping. I'm pointing out the fact that you straight trolled the chat and the posted this like it was yours. You did nothing. Someone else did. Straight up thief.
Sent from my rooted, Dark Horse INFECTED Synergy bolt running Ziggys latest.
Click to expand...
Click to collapse
Your outta your mind homie I didn't steal this from anyone and i definetely wasn't in a chat room go ahead and show me some proof then lets see it, prove that im a liar and a theif your going to look like such an idiot when you prove yourself wrong lol...man I thought this was a joke but this guy is too serious
Unknown_Hero said:
Your outta your mind homie I didn't steal this from anyone and i definetely wasn't in a chat room go ahead and show me some proof then lets see it, prove that im a liar and a theif your going to look like such an idiot when you prove yourself wrong lol...man I thought this was a joke but this guy is too serious
Click to expand...
Click to collapse
Incoming by the person that Actually figured this out and putting another kanger on blast.
Sent from my rooted, Dark Horse INFECTED Synergy bolt running Ziggys latest.
was asked pics be removed
This doesn't even prove anything!!! Its not even close to what i posted LOL. Buddy you need to get a life man I wasn't in the chatroom and what I posted is completely different...what your saying then is that everyone has kanged something at one point in time...just because a topic was brought up and there's a post about elsewhere means it's stolen?? I hope you get all your issues figured out in your sad life bro I'm going to continue mine content on the fact that I'm not a kanger lol you say I have alot of respect for the devs and users on XDA and would never steal some ones work for the sole purpose of stealing the spotlight from them...I don't care about that I don't even have that kind of time in my day troll chatrooms to "kang" peoples work. You sound like a 16 year old emo girl get a grip...I came up with this on my own and I'm proud of it!
Sent from my PG86100 using XDA Premium App
Unknown_Hero said:
This doesn't even prove anything!!! Buddy you need to get a life man I wasn't in the chatroom and what I posted is completely different...what your saying then is that everyone has kanged something at one point in time...just because a topic was brought up and there's a post about elsewhere means it's stolen?? I hope you get all your issues figured out in your sad life bro I'm going to continue mine content on the fact that I'm not a kanger lol you say
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
Lol. Busted and still denying it. Sad. I hope your phone bricks.
Sent from my rooted, Dark Horse INFECTED Synergy bolt running Ziggys latest.
Lol busted from two screenshots that show absolutely nothing to prove...
my phone won't brick because I know how to dev on it, and I don't need chatrooms to do it
looks like your Busted for being a Nub
Unknown_Hero said:
Lol busted from two screenshots that show absolutely nothing to prove...
my phone won't brick because I know how to dev on it, and I don't need chatrooms to do it
looks like your Busted for being a Nub
Click to expand...
Click to collapse
LOL. Two screenshots that show the time that it was done compared to your post. Give it up thief. Youre a terrible liar and a straight up kanger.
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 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
hi everyone.. I recently upgraded my phone to the LG G2, and in doing so I have kept my Droid DNA for the purpose of getting into rooting, and customizing. I have always been fascinated with smart phones , and operating systems, and would like to get to know how to dig into them. I know stock systems very well, and optimize every phone I get up to the stock allowance. Now I want to lift my limitations, and this is the perfect phone to do it with. so if yu could please kindly give me some advice on where to start,. I have been lurking these forums for quite some time, and I find it overwhelming, since I don't know a good starting point. I will continue reading/learning before I tap into this OS, but I just need to know basics, then I will begin to understand the framework..if I have this in the wrong section, im sorry, ill find it if you move it. if you can help , thanks in advance.
findinghomer said:
hi everyone.. I recently upgraded my phone to the LG G2, and in doing so I have kept my Droid DNA for the purpose of getting into rooting, and customizing. I have always been fascinated with smart phones , and operating systems, and would like to get to know how to dig into them. I know stock systems very well, and optimize every phone I get up to the stock allowance. Now I want to lift my limitations, and this is the perfect phone to do it with. so if yu could please kindly give me some advice on where to start,. I have been lurking these forums for quite some time, and I find it overwhelming, since I don't know a good starting point. I will continue reading/learning before I tap into this OS, but I just need to know basics, then I will begin to understand the framework..if I have this in the wrong section, im sorry, ill find it if you move it. if you can help , thanks in advance.
Click to expand...
Click to collapse
I suppose unlocking and S-off should be your starting point, if I understand the question correctly.
If your DNA is on the latest firmware 3.x.x then Rumrunner will get this done for you.
Then install a custom Recovery, ClockWorkMod (CWM) or TeamWinRecoveryProject (TWRP).
Back up your OE Rom by making Nandroid (done in recovery).
After that you can flash whatever ROM you choose.
I have 2 DNAs, on one I have ViperDNA 2.5.0 and on the other CyanogenMod 11.0 nightly.
Above all, have fun :good:
Thanks, Yes... that does answer my question. And I am on firmware 3. Android 4.2.2. Is there any specific advice you can give me to avoid any fatal errors?
btw. what lead me to create a this thread, was that I heard I need rumrunner , so I went to the website, DL the file. after extracting the file for my device, and executing soju.exe, when it ask if im aware of the implications or whatever "type yes or no" when I type yes, It just keeps asking me over and over lol. so I got no where. so I did some digging and found tons of different threads ,, some of which say use this file.... or that tool kit, or this program.... or that method, some that seem to no longer works etc. so it just confused me on what I need to do with my particular phone. 4.2.2 firmware 3 sense 5.0
findinghomer said:
btw. what lead me to create a this thread, was that I heard I need rumrunner , so I went to the website, DL the file. after extracting the file for my device, and executing soju.exe, when it ask if im aware of the implications or whatever "type yes or no" when I type yes, It just keeps asking me over and over lol. so I got no where. so I did some digging and found tons of different threads ,, some of which say use this file.... or that tool kit, or this program.... or that method, some that seem to no longer works etc. so it just confused me on what I need to do with my particular phone. 4.2.2 firmware 3 sense 5.0
Click to expand...
Click to collapse
This http://forum.xda-developers.com/showthread.php?t=2559232 should be all you need for unlock and S-off.
This http://forum.xda-developers.com/showthread.php?t=1994662 is the Recovery I use, TWRP.
When using Rumrunner you must follow the instructions EXACTLY.
Make sure your drivers are working properly.
Make sure your device is recognized by ADB and Fastboot.
Rumrunner assumes you have studied, and are familiar with ADB and Fastboot commands.
If not read this http://forum.xda-developers.com/showthread.php?t=879701
Make sure your firewall and any anti virus are disabled.
Enjoy :fingers-crossed:
Make sure you use a capital y when typing yes, everything needs to be exact.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
Make sure you use a capital y when typing yes, everything needs to be exact.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yip that was it. figured out adb/fastboot commands out too. So I am finally getting a start. I really appreciate it guys. thanks
.'
'Eg
Wanting to do the same thing
So I am also trying to do this same thing, on same firmware and sense versions, but when rumrunner gets to the very first step were it reboots into the bootloader, it never gets past the waiting for fastboot stage. My phone just sits at the bootloader menu and the countdown runs out. I am not sure what I am doing wrong. Any help is appreciated.
Mr.Schneider said:
So I am also trying to do this same thing, on same firmware and sense versions, but when rumrunner gets to the very first step were it reboots into the bootloader, it never gets past the waiting for fastboot stage. My phone just sits at the bootloader menu and the countdown runs out. I am not sure what I am doing wrong. Any help is appreciated.
Click to expand...
Click to collapse
Sounds like either your ADB or Fastboot are not working properly.
Fix them and you should be fine.
Mr.Schneider said:
So I am also trying to do this same thing, on same firmware and sense versions, but when rumrunner gets to the very first step were it reboots into the bootloader, it never gets past the waiting for fastboot stage. My phone just sits at the bootloader menu and the countdown runs out. I am not sure what I am doing wrong. Any help is appreciated.
Click to expand...
Click to collapse
What os are you running? Like sdamark said it sounds like your drivers aren't installed properly.
Sent from my Droid DNA using Tapatalk
I have Windows 8.1 on the computer I'm trying this on. I just read that might cause some problems. I'm going to try it on my Windows 7 laptop in a little bit and see if that helps
Sent from my HTC DROID DNA
Mr.Schneider said:
I have Windows 8.1 on the computer I'm trying this on. I just read that might cause some problems. I'm going to try it on my Windows 7 laptop in a little bit and see if that helps
Sent from my HTC DROID DNA
Click to expand...
Click to collapse
Windows 8.1 does not get along with the dna. It's best to use Windows 7
Sent from my HTC Droid DNA using XDA Premium 4 mobile app
Jaggar345 said:
Windows 8.1 does not get along with the dna. It's best to use Windows 7
Sent from my HTC Droid DNA using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's not entirely true. You have to disable driver signature enforcement in Windows 8.x then install the ADB driver. Microsoft doesn't want anyone unknowingly installing drivers by accident. They make it so that you know what you are doing and doing it on purpose.
http://youtu.be/NM1MN8QZhnk?t=29s
Got it!
I did all the same things on my Windows 7 laptop and it worked perfectly the first time. It really was Windows 8.1 that was the problem. I'll be sure to follow that link and make sure all the rest of my drivers work in the future. Thanks.
Guess the title says it all. All the guides I keep finding are for lollipop. All I want to do is return this phone to 100% stock. Can someone please help me? I don't want to mess it up.
darthyobert said:
Guess the title says it all. All the guides I keep finding are for lollipop. All I want to do is return this phone to 100% stock. Can someone please help me? I don't want to mess it up.
Click to expand...
Click to collapse
1. Download kdz file from here: https://docs.google.com/uc?id=0B3R77elw9JjNSmVsVjhjbWdLcEU&export=download
2. Download lgup from here: https://drive.google.com/file/d/0BzRiXiP57hD7bnpaVkJJUUFLQnc/view?pref=2&pli=1 and install both file in it. After that Copy the "common" folder in the zip file to "C:\Program Files (x86)\LG Electronics\LGUP\model"
3. Download and install LG Bridge for drivers. http://www.lg.com/us/support/product-help/CT10000026-1438110404543-preinstall-app
4. Turn off your phone, hold volume up button while plug your microusb cable, It will set your v10 to download mode.
5. Run lgup executive file, chose upgrade, in bin file select the kdz downloaded from step 1, then CLOSE lg up.
6. Reopen lgup again, chose refurbid, the kdz file still linked in bin
7. Press start and wait. When it finished, u're on stock MM v20e.
Perfect! Thank you. Do I need to relock the bootloader after that or will lgup do it for me?
I used lg bridge and clicked recovery button on bottom right then locked bootloader. Worked like a champ for me
Sent from my LG-H901 using Tapatalk
sjrl79 said:
I used lg bridge and clicked recovery button on bottom right then locked bootloader. Worked like a champ for me
Click to expand...
Click to collapse
Lg bridge returned you to stock or you just used it to lock your bootloader?
Yeah took me to stock and stock recovery, but u have to adb oem lock bootloader
Sent from my LG-H901 using Tapatalk
darthyobert said:
Guess the title says it all. All the guides I keep finding are for lollipop. All I want to do is return this phone to 100% stock. Can someone please help me? I don't want to mess it up.
Click to expand...
Click to collapse
Hello darthyobert,
http://forum.xda-developers.com/tmobile-lg-v10/general/step-step-guide-rooting-lg-v10-using-t3382631
http://forum.xda-developers.com/tmobile-lg-v10/general/root-android-6-0-h901-t3382819
Two very good threads on the subject. A quick search would've lead you to those two threads.
sjrl79 said:
Yeah took me to stock and stock recovery, but u have to adb oem lock bootloader
Click to expand...
Click to collapse
Cool thanks
jun19inf said:
Hello darthyobert,
http://forum.xda-developers.com/tmobile-lg-v10/general/step-step-guide-rooting-lg-v10-using-t3382631
http://forum.xda-developers.com/tmobile-lg-v10/general/root-android-6-0-h901-t3382819
Two very good threads on the subject. A quick search would've lead you to those two threads.
Click to expand...
Click to collapse
Thanks but I didn't ask how to root. I already did that. I want to undo it. And I was just looking for the simplest way. Trust me, I've read every thread in the world on the v10. Theses other guys helped me out. It's all good now. Have a nice day...and there's no such thing as a QUICK search on the subject. I've been searching for 3 days ish and just got tired of it. So I asked
Yeah I was on MM rooted and had to return my V10. I searched too, I finally decided to take a chance and use lg bridge and it worked. But no write up on how to.
Sent from my LG-H901 using Tapatalk
So what's the verdict to go completely back to stock? Use LGUP or Bridge or both?
Sent from my VK815 using XDA-Developers mobile app
darthyobert said:
Thanks but I didn't ask how to root. I already did that. I want to undo it. And I was just looking for the simplest way. Trust me, I've read every thread in the world on the v10. Theses other guys helped me out. It's all good now. Have a nice day...and there's no such thing as a QUICK search on the subject. I've been searching for 3 days ish and just got tired of it. So I asked
Click to expand...
Click to collapse
Nobody reads anything anymore. The thread that was linked literally has a pdf in it called "how to unroot"
When these unroot methods are applied, do they get rid of the "your device software cant be checked for corruption" prompt on bootup?
I think only relocking the bootloader removes that message.
Sent from my pretty nifty brand new LG V10
I ask because I'd like to trade in this phone for the V20. I just don't want to embark on all this effort and still have a phone with "root evidence" making it un-tradeable.
watdafux said:
I ask because I'd like to trade in this phone for the V20. I just don't want to embark on all this effort and still have a phone with "root evidence" making it un-tradeable.
Click to expand...
Click to collapse
flash the phone with root stock and then while in fastboot mode run the following command: fastboot oem lock
That will lock the bootloader and get rid of the annoying message.