So I thought it'd be a good idea for me to present my steps and procedures for the N4 CONVERSION on these forums before executing them, seeing as how this process can be dangerous.
- Root my phone through this method, obviously.
http://forum.xda-developers.com/showthread.php?t=2006946
- Then the conversion process.
http://forum.xda-developers.com/showthread.php?t=2099784
Now is where my questions come in. From here, there are many threads that pertains to what you can do. But thing is, I've no idea which and in which order.
Do I flash recovery after conversion or before (after root)?
Okay, so I found this topic:
http://forum.xda-developers.com/showthread.php?t=2117576
And this topic:
http://forum.xda-developers.com/showthread.php?t=2130639
Do they both contain all the fixes prevalent in the conversion? Meaning do I need to only flash one? Or both?
Also found this topic about the 8 GB issue. Do I do that immediately after conversion?
http://forum.xda-developers.com/showthread.php?t=2160124
I
PATRICKismyHERO said:
So I thought it'd be a good idea for me to present my steps and procedures for the N4 CONVERSION on these forums before executing them, seeing as how this process can be dangerous.
- Root my phone through this method, obviously.
http://forum.xda-developers.com/showthread.php?t=2006946
- Then the conversion process.
http://forum.xda-developers.com/showthread.php?t=2099784
Now is where my questions come in. From here, there are many threads that pertains to what you can do. But thing is, I've no idea which and in which order.
Do I flash recovery after conversion or before (after root)?
Okay, so I found this topic:
http://forum.xda-developers.com/showthread.php?t=2117576
And this topic:
http://forum.xda-developers.com/showthread.php?t=2130639
Do they both contain all the fixes prevalent in the conversion? Meaning do I need to only flash one? Or both?
Also found this topic about the 8 GB issue. Do I do that immediately after conversion?
http://forum.xda-developers.com/showthread.php?t=2160124
Click to expand...
Click to collapse
Sent from my Optimus G using Tapatalk 2
Honestly if I were you I wouldn't do the conversion it really has no benefit over the few roms available to us on stock firmware/partitions. It's only a matter of time before more roms make it to the scene.
If you are determined to do so then hop on irc and grab the automated LGNPST install it (as administrator) and get the N4 tot and flash it with LGNPST (no need to root or unlock before hand) once completed go into bootloader and fastboot oem lock, fastboot oem unlock, and fastboot -w install the recovery of your choice, do the 8gb to 16gb fix, flash the rom of your choice, then do the fixes for said rom.
However, I will say that rootbox has been running exceptionally well for me and doesn't require a single fix to function properly. All you have to do in this case is (if you aren't already on stock Jellybean) LGNPST the appropriate TEENYBIN, then boot into recovery and flash the rom of choice from our forums. I hope I've been of some help
Thanks for your input! After further trials, I can't even get past the LGNPST part. Every time I enter download mode and plug into my computer, my computer just crashes. And my phone remains in download mode.
Sent from my LG-E970 using xda app-developers app
If your computer crashes loading lgnpst I wouldn't try to use it then, that's a fast way to hard brick your phone
Sent from my LG-E970 using Tapatalk 2
Just use freegee in the app store then. As long as you took the 4.1.2 ota then used freegee, you're good to flash any of the roms. With the 4.1.2 update your tz/rpm partitions are updated. If you need any help jump on the irc channel and many of us are willing to help.
BE SURE TO ROOT FIRST - use the fiddy method. works for all variants
Initially, I did want to try some of the ROMs here before trying the conversion out. But my problem also comes from the fact that I never received the OTA update. I read somewhere that if you're on 10o you can't receive it, and the only way is to push the update through LGNPST 11c. Thing is, I stayed up late last night trying to get LGNPST to work, and it simply doesn't. I'm thinking it's probably because I'm on Windows 8...
PATRICKismyHERO said:
Initially, I did want to try some of the ROMs here before trying the conversion out. But my problem also comes from the fact that I never received the OTA update. I read somewhere that if you're on 10o you can't receive it, and the only way is to push the update through LGNPST 11c. Thing is, I stayed up late last night trying to get LGNPST to work, and it simply doesn't. I'm thinking it's probably because I'm on Windows 8...
Click to expand...
Click to collapse
I'm on windows 8 and I have no issues with lgnpst, but that being said if you can't get lgnpst working you won't be doing the conversion either as it's required
Sent from my LG-E970 using Tapatalk 2
PATRICKismyHERO said:
Initially, I did want to try some of the ROMs here before trying the conversion out. But my problem also comes from the fact that I never received the OTA update. I read somewhere that if you're on 10o you can't receive it, and the only way is to push the update through LGNPST 11c. Thing is, I stayed up late last night trying to get LGNPST to work, and it simply doesn't. I'm thinking it's probably because I'm on Windows 8...
Click to expand...
Click to collapse
Have you looked at THIS? It may help.
Its not necessarily windows 8. If you have USB 3.0 ports and Windows 8, that's the problem.
Sent from my Optimus G using xda premium
g33k3r said:
Its not necessarily windows 8. If you have USB 3.0 ports and Windows 8, that's the problem.
Sent from my Optimus G using xda premium
Click to expand...
Click to collapse
I have usb 3 ports on my machine, I just don't use them.
PATRICKismyHERO said:
Initially, I did want to try some of the ROMs here before trying the conversion out. But my problem also comes from the fact that I never received the OTA update. I read somewhere that if you're on 10o you can't receive it, and the only way is to push the update through LGNPST 11c. Thing is, I stayed up late last night trying to get LGNPST to work, and it simply doesn't. I'm thinking it's probably because I'm on Windows 8...
Click to expand...
Click to collapse
There's success stories that if you call AT&T and ask them nicely to push through the 11c and JB OTA, they will.
Like everyone else is saying, it'd be worth trying to get LGNPST figured out and flashing any of the available roms. I was able to find it and figure it out by just searching threads/thread titles. I flashed the following Korean Stock Rom JBV1 -> 11c -> LGNPST to 20J -> AOKP 4.2.2
Good luck
PATRICKismyHERO said:
Initially, I did want to try some of the ROMs here before trying the conversion out. But my problem also comes from the fact that I never received the OTA update. I read somewhere that if you're on 10o you can't receive it, and the only way is to push the update through LGNPST 11c. Thing is, I stayed up late last night trying to get LGNPST to work, and it simply doesn't. I'm thinking it's probably because I'm on Windows 8...
Click to expand...
Click to collapse
Have you tried calling AT&T support and asking them to look into why you haven't received the OTA? I've read a few posts from folks who were able to get a tech to push the update.
Good luck with getting your LGNPST sorted out...it's handy to have.
Sent from my Optimus G using xda premium
Related
How do you root the Thunderbolt after the 7/8/11 OTA?
Rooting using the old method doesn't work anymore?
flooritnfly said:
How do you root the Thunderbolt after the 7/8/11 OTA?
Click to expand...
Click to collapse
you would use the same process as before.
lostnuke said:
you would use the same process as before.
Click to expand...
Click to collapse
Yeah, use the same method. After your rooted, flash the rooted OTA stock Rom (google it) and also flash the its radio. That's what I did.
Sent from my rooted stock OTA MR2 Thunderbolt
So.... I can use this (http://forum.androidcentral.com/thu...unroot-windows-updated-5-20-w-mr1-update.html) like I did before then just flash the new radio that was released on 7/8 ?
Well now after 7/8, you have to flash while standing on your head. Yeah, its crazy like that.
bthomp21 said:
Well now after 7/8, you have to flash while standing on your head. Yeah, its crazy like that.
Click to expand...
Click to collapse
That is too funny.
I am unable to install the 7/8 Combo Radio package after installing DasBAMF Stripped 1.8.6
Constantly says "Installation Aborted."
Anyone else with this experience? I thought that I had read that this combo worked.
Got this sorted. I was using an MR1 package, not MR2, apparently. Using a different packaging of the OTA update flashed in via HBOOT.
BoulderGeek said:
I am unable to install the 7/8 Combo Radio package after installing DasBAMF Stripped 1.8.6
Constantly says "Installation Aborted."
Anyone else with this experience? I thought that I had read that this combo worked.
Click to expand...
Click to collapse
Your flashing it through the bootloader right? You can't use clockwork to flash it.
Sent from my rooted stock OTA MR2 Thunderbolt
Thunderbolt/Android Noob
OK .. I have this HTC Thunderbolt .. I want to root it .. I have read the forums up and down ... I saw the link above to AndroidCentral that shows how to root it, and one over in the Thunderbolt Development forum that says MR1 Perma Root ...
I would like to know the best route for me to go with minimal risk of bricking. I have flashed my wife's LG Ally a couple of times .. was easy enough, just ran an exe
All of the ones I have found for the thunderbolt seem to be a lot more complex. Is there a OneClick method I can run that will include the new radio (so i can get the latest fixes)?
If not, I am willing to go the ADB route (I have the Android SDK installed) but I dont know how to update the radio.
Thanks, and sorry to ask a question that seems to have already been answered, I am only asking b/c I did not understand your answers above ..
Use adb to root. Radio is done through hboot. Power off phone. Then hold vol key down and power on. Will bring you to hboot. Make sure radio is at root of SD card and is named properly. There is a sticky in the DEV section that will walk you through it.
courtesy of my rooted bolt
I just used the XDA development one. The key point is to read it carefully several times and be sure you understand each step. Ask questions beforehand if you are not sure about something. And be sure to follow each step exactly. Typos are the biggest risk, so go slow and read what you've typed on each line before hitting enter.
The radio file needs to be renamed to PG051IMG.zip and placed on the root of the SD card. Then power off and boot into bootloader. It'll load automatically after you hit +volume to confirm "yes ".
I had several flashes that resulted in the Exclamation Point warning triangle. Pulling the battery and USB cable and reinstalling power got me back to a running build.
It took me a while to do every step. I wanted to skip steps, not realizing that you needed the downgrade and RUU flashes to get S-OFF and unlock.
Once that was all done, I went to DasBAMF Stripped and found the OTA radio in this thread http://forum.xda-developers.com/showthread.php?t=1160346.
So far, so good. Calibrating battery now and trying to personalize and optimize to my best ability.
Ok so from what I gather there are no issues that would prevent any of the previous methods from working post 7/8 update? That includes the one click app thats been floating around for a few months right?
I've been holding off root for months, but my patience has finally run out, time to do what I should have done from the beginning.
EDIT
on second thought, I think I'll just do it the good old fashioned way
I did the 7/8 update, and was fine with it. I just wanted to get the Verizon bloatware off. I had problems installing the stock debloated ROMs, so i ran with BAMF to test, and since it worked, I kept it. My rooting came after the recent OTA.
The once-click and .bat methods didn't work so well for me, so I followed the full instructions in a CMD window (I can't call that POS in DOS a shell).
Most of my time was installing a correct Java JDK (had to use x86 instead of x64) and getting ADB dialled in.
KO'B said:
Ok so from what I gather there are no issues that would prevent any of the previous methods from working post 7/8 update? That includes the one click app thats been floating around for a few months right?
I've been holding off root for months, but my patience has finally run out, time to do what I should have done from the beginning.
EDIT
on second thought, I think I'll just do it the good old fashioned way
Click to expand...
Click to collapse
I had the same thinking and wanted it the quick and easy way. Doing the research and taking the time (and beers ) to do it manually was very informative and satisfying when i got done. It was said already but ive been able to apply any feature that an official OTA would give long before its normally released to verizon customers. I love my Tbolt and wouldnt have it any other way.
BryanB32 said:
I had the same thinking and wanted it the quick and easy way. Doing the research and taking the time (and beers ) to do it manually was very informative and satisfying when i got done. It was said already but ive been able to apply any feature that an official OTA would give long before its normally released to verizon customers. I love my Tbolt and wouldnt have it any other way.
Click to expand...
Click to collapse
Doing things the long way has never really scared me, but some of the horror stories I kept hearing a month or two back about instability of GB roms had me a bit hesitant to go for it.
It does appear to be a bit more involved than what I am accustomed to, but I have used ADB before, I was just trying not to this time.
Can someone give me a bit of advice actually.
I'm on the end of Step 4 found in the Developement section, and when I hit Bootloader, it brings up a second menu not mentioned in the posts, what do i do from here?
Nevermind once again, screwed up the name of the zip file
I used the auto root method 3 times so far and worked great. I did the full last update and lost root so I had to redo it load Rom and just added the radio file in hboot.
try auto root its fast and simple just follow the commands on the screen!
Hiya folks, bit of a problem. I never bothered to root or unlock my DNA (it's been getting the job done nicely with a few non-root customizations, and I have other gadgets to tinker away with). This morning I accepted the OTA update from Verizon, and now it's bricked - stuck on the HTC splash screen.
I did a soft reset, cleared the cache partition, and performed a hard reset - no dice. Called Verizon and HTC, no help - I can pretty much do a repair/replacement if I'm still under warranty. I'd really rather avoid going down that path, as I think I'm barely over the warranty (though I can hopefully get them to honor it if I'm within 30 days).
Is there any way I can still flash this back to an older stock, having never unlocked it? I can only get the thing into fastboot mode, and all of the instructions I've found are for when the phone's been bricked after rooting. adb can't seem to talk to it at all, probably because it's in fastboot. Is it safe to attempt using an RUU or some sort of image to flash it using the fastboot utility?
Since it's already bricked, I went ahead and made a go at it using an older RUU, but it quick before even trying, claiming I needed the correct version of the utility. It's possible I did it wrong, though.
Any help would be much obliged! This is what I get for not rooting/learning how to do this stuff earlier...
EDIT: Before this newest update, my phone had the most up-to-date stock ROM. It was fully charged when it performed the OTA.
jaawerth said:
Hiya folks, bit of a problem. I never bothered to root or unlock my DNA (it's been getting the job done nicely with a few non-root customizations, and I have other gadgets to tinker away with). This morning I accepted the OTA update from Verizon, and now it's bricked - stuck on the HTC splash screen.
I did a soft reset, cleared the cache partition, and performed a hard reset - no dice. Called Verizon and HTC, no help - I can pretty much do a repair/replacement if I'm still under warranty. I'd really rather avoid going down that path, as I think I'm barely over the warranty (though I can hopefully get them to honor it if I'm within 30 days).
Is there any way I can still flash this back to an older stock, having never unlocked it? I can only get the thing into fastboot mode, and all of the instructions I've found are for when the phone's been bricked after rooting. adb can't seem to talk to it at all, probably because it's in fastboot. Is it safe to attempt using an RUU or some sort of image to flash it using the fastboot utility?
Since it's already bricked, I went ahead and made a go at it using an older RUU, but it quick before even trying, claiming I needed the correct version of the utility. It's possible I did it wrong, though.
Any help would be much obliged! This is what I get for not rooting/learning how to do this stuff earlier...
EDIT: Before this newest update, my phone had the most up-to-date stock ROM. It was fully charged when it performed the OTA.
Click to expand...
Click to collapse
Exact same thing happened to me last evening...except I'm rooted with S-off.
grimmkt said:
Exact same thing happened to me last evening...except I'm rooted with S-off.
Click to expand...
Click to collapse
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
ryclegman said:
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
Click to expand...
Click to collapse
Aha! Much obliged. I searched for the right RUU and couldn't find it, and completely missed that thread - I was using the wrong search terms. Downloading now - I'll update tonight once I know if it works. Then I'm modifying the crap out of this thing!
jaawerth said:
Aha! Much obliged. I searched for the right RUU and couldn't find it, and completely missed that thread - I was using the wrong search terms. Downloading now - I'll update tonight once I know if it works. Then I'm modifying the crap out of this thing!
Click to expand...
Click to collapse
Sounds good! let us know!:good:
ryclegman said:
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
Click to expand...
Click to collapse
I can't get the phone to connect in fastboot. I keep getting a "driver failed to load" type error when I plug in the USB...the device is never visible.
Worked like a charm! The download took awhile, but once I had it downloaded it was easy.
For others searching for this issue:
Once you have the RUU, just install Android Development tools (specifically fastboot) and enter
>fastboot oem rebootRUU
>fastboot flash install IMAGEFILE.ZIP
Terminal/command prompt on the computer side told me it was finished but the phone was stuck at the very end of the progress bar. I waited a while few minutes, and when it didn't move I risked doing a
>fastboot reboot
and we were good to go.
Arise, thread!
So! My phone never bricked again, but a few weeks after I performed the RUU with the image linked earlier in this thread, I started to see the problem that early DNA's started to have with it randomly giving a "no SIM card" error. I'd had this issue when I first got the DNA, but at the time I just went through the normal phone replacement process to resolve it. Imagine my surprise when it came back after flashing! It's now reached the point where I will lose calls because of it, and will often have to reboot/toggle airplane mode to get data back, so I finally got annoyed enough to post.
Presumably this problem is because the image I flashed from is the original DNA image with the drivers that cause that SIM issue. So my question is: if I s-off, root, and install a custom ROM, will that take care of it? Or is this particular issue so deep on the driver level that I need to find a more recent RUU?
I also have not yet tried a new SIM - because of the timing of the problem, I'm slow to believe that it's related to the SIM card, but I suppose it isn't impossible.
jaawerth said:
Arise, thread!
So! My phone never bricked again, but a few weeks after I performed the RUU with the image linked earlier in this thread, I started to see the problem that early DNA's started to have with it randomly giving a "no SIM card" error. I'd had this issue when I first got the DNA, but at the time I just went through the normal phone replacement process to resolve it. Imagine my surprise when it came back after flashing! It's now reached the point where I will lose calls because of it, and will often have to reboot/toggle airplane mode to get data back, so I finally got annoyed enough to post.
Presumably this problem is because the image I flashed from is the original DNA image with the drivers that cause that SIM issue. So my question is: if I s-off, root, and install a custom ROM, will that take care of it? Or is this particular issue so deep on the driver level that I need to find a more recent RUU?
I also have not yet tried a new SIM - because of the timing of the problem, I'm slow to believe that it's related to the SIM card, but I suppose it isn't impossible.
Click to expand...
Click to collapse
The only way I have seen this permanently resolved is to get a new Sim tray from HTC. I got one and my brother did too and I never get Sim card errors like I used to. Just go to their website contact their support and ask for one and they send it out for free no questions asked.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
The only way I have seen this permanently resolved is to get a new Sim tray from HTC. I got one and my brother did too and I never get Sim card errors like I used to. Just go to their website contact their support and ask for one and they send it out for free no questions asked.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, may as well give it a try. What's odd is that this problem hadn't happened at all with this sim tray until after I flashed, which really makes it sound like a software issue. Still, worth a shot!
jaawerth said:
Thanks, may as well give it a try. What's odd is that this problem hadn't happened at all with this sim tray until after I flashed, which really makes it sound like a software issue. Still, worth a shot!
Click to expand...
Click to collapse
It's a known hardware issue in the DNA. When they give you a new Sim tray it's thicker and it holds the Sim card in place better resulting with no more errors.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
A while back when I first got my Verizon Note 2, I used Adam Outler's Casual method to root my phone to Stock. I don't mind stock and root mostly for the Tethering.
About a week back the OTA notice hit my phone. I have declined the notice/update twice giving myself time to look for the root update. I found this thread by Beans: http://forum.xda-developers.com/showthread.php?t=2518704 ........ It seems right but this thread by AdamOutler says not to use ODIN: http://forum.xda-developers.com/showthread.php?t=2045563
So I am a little confused. I just want the update but don't want to mess up and not have my tethering ever again.... or brick the phone.
As a newbie, it's a scary task. Someone please help point me in the right direction. I just want the 4.3 Stock. If there is a thread for my situation I couldn't find it. I search "casual TWRP 4.3 OTA" and other similar variations.
I can still get to the TWRP 2.5.0.0. I have also downloaded the ODIN and started it... looks simple, but there are no instructions.
Someone please help me...
Thanks
MrNewbie said:
A while back when I first got my Verizon Note 2, I used Adam Outler's Casual method to root my phone to Stock. I don't mind stock and root mostly for the Tethering.
About a week back the OTA notice hit my phone. I have declined the notice/update twice giving myself time to look for the root update. I found this thread by Beans: http://forum.xda-developers.com/showthread.php?t=2518704 ........ It seems right but this thread by AdamOutler says not to use ODIN: http://forum.xda-developers.com/showthread.php?t=2045563
So I am a little confused. I just want the update but don't want to mess up and not have my tethering ever again.... or brick the phone.
As a newbie, it's a scary task. Someone please help point me in the right direction. I just want the 4.3 Stock. If there is a thread for my situation I couldn't find it. I search "casual TWRP 4.3 OTA" and other similar variations.
I can still get to the TWRP 2.5.0.0. I have also downloaded the ODIN and started it... looks simple, but there are no instructions.
Someone please help me...
Thanks
Click to expand...
Click to collapse
Welp, couple things...
#1 - The link you posted above is the from the Note 3. You want this one http://forum.xda-developers.com/showthread.php?t=2578458
#2, The ROM gets flashed via CWM or TRWP like normal, it's only the radio update that gets flashed via ODIN. That shouldn't affect your current unlock/root status.
#3 - If it is only ROOT you are after, the 4.3 OTA is Rootable, just not unlockable. So if by chance you accidentally take the OTA you should still be able to ROOT and install your Tethering app. You just won't be able to unlock the bootloader and install a custom recovery/rom.
Jiggabitties said:
Welp, couple things...
#3 - If it is only ROOT you are after, the 4.3 OTA is Rootable, just not unlockable. So if by chance you accidentally take the OTA you should still be able to ROOT and install your Tethering app. You just won't be able to unlock the bootloader and install a custom recovery/rom.
Click to expand...
Click to collapse
So if you are OTA'd to MJ9, how do you unlock?
SteveHebe said:
So if you are OTA'd to MJ9, how do you unlock?
Click to expand...
Click to collapse
You cannot. Best bet is to not take the other and unlock your bootloader. If you take it you will probably be locked for a very long time.
Sent from my SCH-I605 using Tapatalk 2
michigan66 said:
You cannot. Best bet is to not take the other and unlock your bootloader. If you take it you will probably be locked for a very long time.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
SteveHebe said:
So if you are OTA'd to MJ9, how do you unlock?
Click to expand...
Click to collapse
Correct, you cannot currently UNLOCK the OTA MJ9 boot loader. But you can ROOT. Which will allow you to tether.
Sent from my SCH-I605 using xda app-developers app
MrNewbie said:
A while back when I first got my Verizon Note 2, I used Adam Outler's Casual method to root my phone to Stock. I don't mind stock and root mostly for the Tethering.
About a week back the OTA notice hit my phone. I have declined the notice/update twice giving myself time to look for the root update. I found this thread by Beans: http://forum.xda-developers.com/showthread.php?t=2518704 ........ It seems right but this thread by AdamOutler says not to use ODIN: http://forum.xda-developers.com/showthread.php?t=2045563
So I am a little confused. I just want the update but don't want to mess up and not have my tethering ever again.... or brick the phone.
As a newbie, it's a scary task. Someone please help point me in the right direction. I just want the 4.3 Stock. If there is a thread for my situation I couldn't find it. I search "casual TWRP 4.3 OTA" and other similar variations.
I can still get to the TWRP 2.5.0.0. I have also downloaded the ODIN and started it... looks simple, but there are no instructions.
Someone please help me...
Thanks
Click to expand...
Click to collapse
I would think long and hard about taking the OTA...although root is available, you may want an unlocked bootloader at some point, and there is no guarantee that is coming to the official 4.3. My guess is that it will not simply because this phone is 18 months old and the skilled developers that put in the time to do things like unlock bootloaders move on to newer devices.
If you managed to use Casual in the past, Odin won't be a problem for you. Below are the steps:
Odin takes about 5 minutes total...its really easy.
Download Odin (it's just a simple windows program). - http://forum.xda-developers.com/atta...3&d=1304094576
Make sure you have the latest samsung drivers - http://www.mediafire.com/?hzlnda0l5t8qyes
Download and extract the firmware from the first post in this thread - http://forum.xda-developers.com/showthread.php?t=2578458
Save whatever 4.3 ROM you choose to your external SD card.
Power down the phone and boot back into download mode (volume down, power and home at the same time).
Open Odin, plug in phone...Odin should recognize the phone and you will see the com port noted in yellow.
Check the PDA box and put the firmware file (unzipped) in the PDA slot. Click start and 30 seconds later you are done. Phone will reboot into recovery at this point.
Then you can flash any of the 4.3 ROMs (including stock) in TWRP (I use 2.5.0.0 too). I have tried them all and Sophisticated 3.0 has worked the best for me...I will be trying beans 23 as soon as it is done.
tfly212 said:
I would think long and hard about taking the OTA...although root is available, you may want an unlocked bootloader at some point, and there is no guarantee that is coming to the official 4.3. My guess is that it will not simply because this phone is 18 months old and the skilled developers that put in the time to do things like unlock bootloaders move on to newer devices.
If you managed to use Casual in the past, Odin won't be a problem for you. Below are the steps:
Odin takes about 5 minutes total...its really easy.
Download Odin (it's just a simple windows program). - http://forum.xda-developers.com/atta...3&d=1304094576
Make sure you have the latest samsung drivers - http://www.mediafire.com/?hzlnda0l5t8qyes
Download and extract the firmware from the first post in this thread - http://forum.xda-developers.com/showthread.php?t=2578458
Save whatever 4.3 ROM you choose to your external SD card.
Power down the phone and boot back into download mode (volume down, power and home at the same time).
Open Odin, plug in phone...Odin should recognize the phone and you will see the com port noted in yellow.
Check the PDA box and put the firmware file (unzipped) in the PDA slot. Click start and 30 seconds later you are done. Phone will reboot into recovery at this point.
Then you can flash any of the 4.3 ROMs (including stock) in TWRP (I use 2.5.0.0 too). I have tried them all and Sophisticated 3.0 has worked the best for me...I will be trying beans 23 as soon as it is done.
Click to expand...
Click to collapse
Thank you so much. Updated and everything seem to work just fine, but after some use it started rebooting. I am going to put on Sophisticated as you suggested. Hopefully, it will be more stable then the stock ROM.
And I can't get the WIFI Tethering to work. Which Tethering app are you using? I have unlimited data... and need to make sure Verizon isn't charging me for no reason.
MrNewbie said:
Thank you so much. Updated and everything seem to work just fine, but after some use it started rebooting. I am going to put on Sophisticated as you suggested. Hopefully, it will be more stable then the stock ROM.
And I can't get the WIFI Tethering to work. Which Tethering app are you using? I have unlimited data... and need to make sure Verizon isn't charging me for no reason.
Click to expand...
Click to collapse
I had some reboots on the stock rom too...but once I went to the other roms (I tried Nephilium, Sophisticated and N3bula, but had the best results with Sophisticated) and I haven't had one reboot.
As for the wifi tethering, on stock you need to flash the file below (some of the newer roms, including Sophisticated have it baked in).
http://forum.xda-developers.com/showpost.php?p=48315091&postcount=245
IS anybody getting close to an unlock/root post VRUEMJ9 VZWi605 Note 2.
the reason I ask is I unrooted back to stock 4.1.1 and then picked up the VZW OTA 4.3 and now can't use Casual or any other method, I can root but not unlock bootloader. well anybody have any Ideas? thank you.
david515 said:
the reason I ask is I unrooted back to stock 4.1.1 and then picked up the VZW OTA 4.3 and now can't use Casual or any other method, I can root but not unlock bootloader. well anybody have any Ideas? thank you.
Click to expand...
Click to collapse
The reason you ask what? You didn't ask anything. And as it's been stated a million times, no unlock method avaliable and unlikely there will be one.
Sent from my SCH-I605 using xda app-developers app
akellar said:
The reason you ask what? You didn't ask anything. And as it's been stated a million times, no unlock method avaliable and unlikely there will be one.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Eh, he is one of those that puts the question in his title instead of the body of the reply. But as @akellar said, there is nothing available.
Thanks so much for all the help. I got everything working right based on the instructions from this thread. I initially had an issue with the "Wifi Tether" because I was using a 3rd party app. Instead the correct app is the "Mobile Hotspot" app. It might be named differently for other carriers, but for Verizon it is "Mobile Hotspot".
Again thank you for all the replies.
Thank you for Sophisticated v3.
Thank you Adam Outler for the original Casual root.
And Thank you runandhide05 for the "Mobile Hotspot" hack!
:good::fingers-crossed: LOL
Hi All,
I have been trying to get the FW update with extreme save mode for almost a week now.
I check for software updates daily and I get the NO UPDATE found message.
Called At&t and tech support is as useful as my 3 years old kid.
Does anyone have the same problem? Solutions?
Thanks
Unlock bootloader, install Android Revolution thats been updated with latest release and you are good to go. No reason to wait till they let it work for yea when you can do it yourself.
JayRolla said:
Unlock bootloader, install Android Revolution thats been updated with latest release and you are good to go. No reason to wait till they let it work for yea when you can do it yourself.
Click to expand...
Click to collapse
Thanks for the advice, but others are getting the update OTA, without root or downloading Android Rev.
Some M8 owners may see a delay in getting the OTA, as it rolls out sequentially, by some means (I've seen AT&T suggest its by IMEI number). A minority of folks will never get it, just by some random fluke or other (as happens on any OTA).
If you don't want to wait, the RUU is already posted. You can download to a PC, and run it with your phone connected. But it will wipe user data.
http://forum.xda-developers.com/showthread.php?t=2757462
redpoint73 said:
Some M8 owners may see a delay in getting the OTA, as it rolls out sequentially, by some means (I've seen AT&T suggest its by IMEI number). A minority of folks will never get it, just by some random fluke or other (as happens on any OTA).
If you don't want to wait, the RUU is already posted. You can download to a PC, and run it with your phone connected. But it will wipe user data.
http://forum.xda-developers.com/showthread.php?t=2757462
Click to expand...
Click to collapse
Thanks for the tip, I tried that and it wouldn't work. Do I need root or s-off?
Also, has everyone that attempted to download things manually received the update?
I would really appreciate the responses
sassij said:
Thanks for the tip, I tried that and it wouldn't work. Do I need root or s-off?
Also, has everyone that attempted to download things manually received the update?
I would really appreciate the responses
Click to expand...
Click to collapse
How did it not work? As long as you are completely stock with cid cws__001 it should work.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
sassij said:
Hi All,
I have been trying to get the FW update with extreme save mode for almost a week now.
I check for software updates daily and I get the NO UPDATE found message.
Called At&t and tech support is as useful as my 3 years old kid.
Does anyone have the same problem? Solutions?
Thanks
Click to expand...
Click to collapse
download ota package from here http://www.androidfilehost.com/?fid=23487008491963146
put it on your micro sd card
boot to recovery "vol up and power 10 sec, vol down and power until boot loader comes up and navigate to recovery"
once in recovery its either vol up and power or vol down and power for a few seconds for advanced options
choose install update from external sd.
sassij said:
Thanks for the tip, I tried that and it wouldn't work. Do I need root or s-off?
Click to expand...
Click to collapse
No, the phone does not need to be modded to run the RUU. Its a "official" update/recovery tool provided by HTC. If you phone is stock, it should work, as the above response also indicated.
If it "wouldn't work" it would be more helpful to give details, if you want proper help. Not just say it didn't work. What step did it fail at , any error message, etc. Also, the current state of your phone (root, unlocked bootloader, etc.), as we can only assume based on your comment about root, etc.
RUU failing on a stock device is usually a USB connectivity issue on the part of your computer (not a problem on the phone's side). Install or re-install the HTC drives, try a different USB port, or a different computer (if available). If on Windows 8.1, that version is a known issue and will not work with the HTC drivers. You can also try re-downloading the RUU to make sure it wasn't damaged/corrupted during download.
From what i have figured out with trial and error, if you are rooted and try to take the OTA and receive the 0x1111002 error, you can use the .tot file and flash back to stock and then it will allow you to take the OTA.. I flashed back to stock 3 times using the .kdz file and each time trying to update it would receive the dreaded error. Also you can downgrade back to 10b using the .tot file after taking the latest OTA.
The kdz files do not take you back to stock 'new'. They are kdz files for a version that was never released, so yea the update is going to see the wrong version and fail. Tot for pure stock.
Thanks for the info. Id seen several people tell others that were getting the error to use the kdz file so just thought would pass on a solution for others that had the same issue.
Yea, the difference between the two method seems be missed by many people, I didn't know until a couple of days ago. Someone said something that made me ask specifically.
TonikJDK said:
Yea, the difference between the two method seems be missed by many people, I didn't know until a couple of days ago. Someone said something that made me ask specifically.
Click to expand...
Click to collapse
So what is the difference between the two then?
Sent from my Nexus 7 using Tapatalk
GillRigged said:
So what is the difference between the two then?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Second post in this thread.
A lot of people were having a real hard time using the .tot file to return to v10b from v11c, for a variety of reasons, so Autoprime and AnnoyingDuck made the purchase and distribution of a v10b pre-release .kdz version happen, bless them both. They did not know the kdz they bought was a step pre-release at first, but that did not matter since they never intended the .kdz to provide a path back onto OTA's. The goal was just to get folks back to a rootable stock, from which they could flash things like the v11c modem image, if they wanted to.
Flashing back via the v10b .tot method always was possible, and returns you to OTA-capable stock. Its just that the .kdz is easier for most folks, if all you want is to return to a rootable version.