Related
I just got the Note 2 from Newegg (for verizon) and after reading through a lot of the threads on this forum like:
How to Unlock Your Bootloader - Firmware Version VRALJB
and
[Q] Stock restore Fail at sboot.bin
and
Questions about Unlocking or Recovering from a Soft Brick
I guess there's issues with the OTA verizon pushed out and the first guide won't work if you have the OTA. Well long story short, how can I tell for sure if the phone I've received had the latest updates put on it before I got it?
My build says VRALJB, does that mean I'm good and I still have the older version? Would it say VRALL4 if the OTA had been applied?
In a related question, would it be wise to simply update to VRALL4 now, use the new method to jailbreak, and then continue on my merry way? Would this alleviate any worries of the OTA getting applied and breaking my root / possibly bricking my phone??
Thanks for any help for a noob. I tried to do research first!
You do not have the ota..... Use original method!!
Sent from my most awesome phone EVER!!!!
As stated above you are on the original baseband VRAJB so you can use the original root and unlock method. Once you are unlocked, do not take a OTA ever as you may get relocked and who knows if there will be a future unlock method. Most of the custom ROMs block the updates, but just in case don't take it if you ever get the message.
Once you are unlocked you will use TWRP custom recovery (which is the screen that will appear at the end of the unlock process). You can flash the VRALL4 baseband when you flash a ROM if you want to be on the latest baseband (flash ROM first then immediately flash VRALL4, no reboot in between). The download can be found here: http://forum.xda-developers.com/showthread.php?t=2108510
Thanks for the replies.
There's a video on the Adam Outler Jailbreak Guide that actually suggest getting the OTA first and then just doing the CASUAL thing afterwards. Personal preference or is there some advantage?
The video in question is the first one in the thread, it is titled "Jailbreak video for Windows users only!
This video desmonstrates CASUAL used with Odin to flash the Galaxy Note 2 firmware Thanks to DroidModderX" and the timeframe in question is 00:50 to 01:10
Just wondering, thanks!
No real advantage either way (the update to VRALL4 was very minor but did relock the bootloader). If you want to be on the latest update you either need to take it OTA or flash it yourself. I was on VRAJB and unlocked before the update so I only had the original method to work with. I updated to VRALL4 manually by flashing it.
Bottom line, either way will work, just make sure if you take the OTA before doing anything that you use the correct unlock method (the "new" one). The whole thing will take you maybe 10 minutes, its really easy. The video is a great guide.
if HTC allows downgrading the bootloader so I can install a custom rom after I make the mistake of taking an OTA update from ATT. With the S4 this wasn't possible. but since this is my first android phone, I was wondering if it was Samsung trying to keep the device "secure" or ATT forcing these companies to keep their bootloaders locked.
some_douchebag said:
if HTC allows downgrading the bootloader so I can install a custom rom after I make the mistake of taking an OTA update from ATT. With the S4 this wasn't possible. but since this is my first android phone, I was wondering if it was Samsung trying to keep the device "secure" or ATT forcing these companies to keep their bootloaders locked.
Click to expand...
Click to collapse
Once you unlock the boot loader no update can relock it. HTC offers a lot more freedom than samsung, but at the price of no warranty. So if you unlock it and shatter your screen, don't be upset like other people when htc will not warranty it. As long as you have a custom recovery, your phone cannot even physically take an ota update so nothing to worry about either way.
The Magnuson–Moss Warranty Act is in place for us consumers for this reason. The company has to prove that any modification you did, is the cause of the trouble. So if you unlock your bootloader, root, etc, then crack your screen, as the poster above mentioned, the company can not void your warranty since what you did has nothing to do with cracking your screen.
This was huge for me when I modified my car and I found this here on XDA after doing more searching
http://www.xda-developers.com/xda-tv-2/your-warranty-is-not-void-xda-tv/
Oh and yeah,,if you are outside the US, it wont work lol
some_douchebag said:
if HTC allows downgrading the bootloader
Click to expand...
Click to collapse
That depends on what you mean by "allow". You cannot downgrade the bootloader by any "official" means. You will fail version check when you try to install, as you can "normally" only flash a equal or great version number hboot.
But if you are s-off, version check is bypassed, and any hboot version can be flashed.
Similar to a previous response, my advice would be to unlock the bootloader (required if you want to flash custom ROMs anyway) and S-off the phone soon after you get it. Neither of those can be changed by any OTA.
Also, accepting OTA is not recommended on a modded phone, anyway. Whatever came in the update will usually get posted in a stock rooted form in the Development forum, and/or incorporated into custom ROMs, often within days of the OTA rolling out. And OTA will not install on a modded phone (stock recovery needs to be present). OTAs also may plug existing s-off or other exploit; preventing you from doing them if you haven't already (but as mentioned, can't make the phone s-on again). Moral of the story, I strongly recommend against OTA on any modded phone.
Some of these terms/concepts are HTC specific, so may be a bit confusing for you. I would suggest reading up on these forums, if you aren't familiar with s-off, HTC's bootloader unlock process, etc.
Hello. Thanks in advance for your time and advice.
I've got a brand new HTC One M8, AT&T, firmware says 4.4.2 with no available updates.
I want to create an initial backup. I'm a computer technician, and just dabbling in Android, and it's important for me to make a "clone" of my phone before I proceed to wreck things. (This is a replacement phone, the last one had a hardware issue... I swear... I managed to install ViperOne onto it, for a week before the screen faded to white and died.)
I assume I'll need root access to make a proper backup. I also assume I should use Nandroid. I've not used the app before, but I'm sure I can figure it out. As far as root goes, I previously used Hasoon2000's HTC One 2014 (M8) All-In-One Toolkit, which worked well, as far as I could tell. (It's a visual basic program with scripts to download drivers, register at htcdev, get token id, submit it, unlock bootloader, flash recovery, and lots of nice ADB commands. Is this a good option to use? I hear many people use S-Off, but I don't really see a need... ?
So, I assume I'll need a new token ID from HTC, as the previous one I got corresponds to the old, malfunctioning phone.
After it's unlocked, I'd use the toolkit to grant perm root. That would be a great place to be for now. I plan to wait until the 4.4.4 update is pushed, then worry about installing a new rom.
Am I on the right track?
For the AT&T version (and most the major US carrier versions) we are lucky enough to have RUUs. So really, no need to backup the stock configuration. If you like, grab the RUUs and save them to your computer so you have them ready if and when it is needed.
Nandroid isn't a specific app, its just a generic term for a backup made with recovery. The custom recovery is your choice: TWRP, Clockworkmod, Philz.
Just a personal opinion, I would actually strongly recommend against using the toolkit for a couple reasons: most importantly using the toolkit robs you of an important learning opportunity. Doing the steps "manually" is a key way to learning your way around fastboot/adb. Doing the steps manually isn't that hard, and shortcutting the process with the toolkit really doesn't gain you much. Another key issue, is the toolkit introduces an additional point of failure. In fact, I've seen folks have trouble doing some of the steps with the toolkit; where doing the steps "manually" worked without a hitch. And the toolkit hasn't been updated for a long time, and will install an obsolete version of TWRP recovery, which in itself can cause issues.
If you used the toolkit before, you can certainly use it again. This is likely the path of "least" resistance, the the "easy" way to do things. But I wouldn't necessarily call it the "best" way to do it. If you don't already know your way around adb, I would do the steps manually. Since you have a background in computers, you will probably even find the manual process more enjoyable.
Yes, you would need to unlock the bootloader again via HTCDev.com, as the unlock bin code in based on the phone's unique IMEI.
The process would be as simple as unlocking the bootloader using HTCDev.com (very easy, the website is self-explanatory). Use fastboot to install custom recovery. Then to gain root, just flash SU or SuperSU in recovery. If you need a step-by-step guide, there is an excellent one here: http://forum.xda-developers.com/showthread.php?t=2799796
But also be aware that once the 4.4.4 OTA rolls out, you will need to return to stock recovery, and also restore any system files modifed by root, in order to install the OTA.
Thanks, redpoint73
Exactly the answer I was looking for. The guide looks great. Looks like there's a lot of useful information about reverting to stock, too. I guess I'll have a go at it now, as opposed to waiting for the update. Like you say, it's good to know things. Thanks much.
@redpoint73
Now I'm only asking cause I don't know everything. Couldn't those who have S-off just RUU the update once available instead of reverting to complete stock state(no root,no custom recovery, locked Bootlaoder)?
AT&T HTC ONE M8
jball said:
@redpoint73
Now I'm only asking cause I don't know everything. Couldn't those who have S-off just RUU the update once available instead of reverting to complete stock state(no root,no custom recovery, locked Bootlaoder)?
Click to expand...
Click to collapse
Absolutely. In fact S-off is not even required to run an RUU intended for your version (AT&T). If s-on, the added step of relocking the bootloader is all that is needed to run the RUU.
HTC seems to have gotten better about releasing the RUUs promptly. In fact, the previous (ill fated) 4.4.3 update saw the RUU and OTA roll out on the same day. Although this hasn't always been the case. On past devices, the RUUs were not released for weeks (sometimes longer) after the OTA started to roll out. And many folks don't want to wait that long.
Also, relocking the bootloader is not required to OTA, only to RUU.
Im sorry if this has been answered in other threads im simply trying to help a friend out with rooting and possibly unlocking the boot loader? Can someone point me in the rite direction? It would be most appreciated
I would check the Verizon LG G3 forums where there are many instances of your questions having been already thoroughly answered.
What you will find is that you must be on v10b firmware, which you can downgrade to using either the .kdz or the .TOT method, then you can root v10b (only) with StumpRoot, or ioRoot, or PurpleDrake, before the phone updates back to v12b. With SuperSu in survival mode root can be retained through either of the current OTA updates (which provide very little enhancement beyond patching root exploits), so far, and with root you can install a specially modified TWRP recovery which will allow the flashing of unsigned kernels and roms.
There. You are on your own from hete on.
Sent from my VS985 4G using Tapatalk
use flashify to install the bumped version of twrp (get it from the original development section). Worked like a charm. Plenty of bumped roms to grab in the dev section.
gothicasshole said:
Im sorry if this has been answered in other threads im simply trying to help a friend out with rooting and possibly unlocking the boot loader? Can someone point me in the rite direction? It would be most appreciated
Click to expand...
Click to collapse
There is no unlocking of the bootloader. Bumping doesn't unlock the bootloader. However, it fools the phone into allowing the flashing of custom ROMs and kernels without unlocking the bootloader. Basically, the phone "believes" that whatever is being flashed (via TWRP) is acceptable and allows the image to pass the "security check" that is done when flashing. It's the same thing as IF the bootloader were unlocked, but in reality, it isn't unlocked. It's a security exploit, kind of like rooting this phone is a security exploit.
However, a quick OTA patch from Verizon or LG could make either or both no longer work. In fact, some OTAs have fixed the root exploit on some models, so you have to flash back to a previous version to root.
You have to root first, then you can flash TWRP.
As stated, there are plenty of FAQs in the general G3 section that help explain all of this.
OK thanks guys. Um just used to seeing a sticky on root under original android development I have no idea what firm ware he's running ik how restrictive big red can be at&t is no better but that's why when they offered a nexus I went and grabbed it
He's wanting a lollipop rom
gothicasshole said:
He's wanting a lollipop rom
Click to expand...
Click to collapse
Go here which gives a whole list of things, including how to root, how to bump, how to flash, etc:
http://forum.xda-developers.com/lg-g3/help/help-thread-lg-g3-question-t2947298
It's where I went before I got this phone to be sure I could do all the things I wanted to.
Thank you
I'll definitely refer him
So I've been unlocking and rooting/flashing phones since the HTC Universal but i'm stumped. I've downloaded the toolkit to unlock my bootloader, downloaded my .bin file and the toolkit says my bootloader is unlocked but the screen on my phone asking me whether i want to unlock it never comes out...any senior members willing to point me in the right direction? I'm using my AT&T M8 on T-mobile and i haven't had a single update since i bought the M8 so i need to update it ASAP.
Update: So I used the sunshine method to try and finally root my phone. Now I'm in the interesting situation where my boot loader is unlocked, it's s-off, yet there is still the stock recovery and not rooted yet. Quite the last 12 hours trying to get root access. I should be able to root it on the PC now that my boot loader is unlocked.
HTCFAN0923 said:
So I've been unlocking and rooting/flashing phones since the HTC Universal but i'm stumped. I've downloaded the toolkit to unlock my bootloader, downloaded my .bin file and the toolkit says my bootloader is unlocked but the screen on my phone asking me whether i want to unlock it never comes out...
Click to expand...
Click to collapse
The Toolkit hasn't been updated in forever, is very obsolete, and will therefore cause more problems than anything.
Toolkit just does functions that are easy to do yourself "manually" anyway. You don't need the toolkit, and you didn't need to s-off to unlock the bootloader (although it can be handy for other things).
HTCFAN0923 said:
I'm using my AT&T M8 on T-mobile and i haven't had a single update since i bought the M8 so i need to update it ASAP.
Click to expand...
Click to collapse
OTA updates for the AT&T version will only be received when connected to AT&T's network (an AT&T specific annoyance). You could have updated to Lollipop using RUU.
---------- Post added at 11:28 AM ---------- Previous post was at 11:26 AM ----------
HTCFAN0923 said:
Update: So I used the sunshine method to try and finally root my phone. Now I'm in the interesting situation where my boot loader is unlocked, it's s-off, yet there is still the stock recovery and not rooted yet. Quite the last 12 hours trying to get root access. I should be able to root it on the PC now that my boot loader is unlocked.
Click to expand...
Click to collapse
Now that the bootloader is unlocked, just flash TWRP via fastboot. Then flash SuperSU 2.46 using TWRP to obtain root.
But your OP says you want to update. Here it says you want to root. Those are 2 very different things, so its not clear what your actual goal is.
redpoint73 said:
The Toolkit hasn't been updated in forever, is very obsolete, and will therefore cause more problems than anything.
Toolkit just does functions that are easy to do yourself "manually" anyway. You don't need the toolkit, and you didn't need to s-off to unlock the bootloader (although it can be handy for other things).
OTA updates for the AT&T version will only be received when connected to AT&T's network (an AT&T specific annoyance). You could have updated to Lollipop using RUU.
---------- Post added at 11:28 AM ---------- Previous post was at 11:26 AM ----------
Now that the bootloader is unlocked, just flash TWRP via fastboot. Then flash SuperSU 2.46 using TWRP to obtain root.
But your OP says you want to update. Here it says you want to root. Those are 2 very different things, so its not clear what your actual goal is.
Click to expand...
Click to collapse
Thanks for the help and sorry for the confusion.
I'm looking to update my phone AND root just because I've always rooted my phones but just now got a replacement for my old laptop that broke down shortly before I got the M8. I figured since I was on T-Mobile my best bet to update it would be to root it and upload a new ROM anyway. Your suggestion is easy enough so I'll be doing that after work.
My last question is this: On the M7, I was able to use an international M7 ROM as everything apart from the radios was the same. Is that the case with the M8 as well? I typically like having Sense ROM's but hate the bloat carriers put on their RUU's....
thanks again!
HTCFAN0923 said:
I'm looking to update my phone AND root just because I've always rooted my phones but just now got a replacement for my old laptop that broke down shortly before I got the M8. I figured since I was on T-Mobile my best bet to update it would be to root it and upload a new ROM anyway. Your suggestion is easy enough so I'll be doing that after work.
Click to expand...
Click to collapse
In that case, I would suggest updating by RUU first, and then root.
Reason I say that, is that RUU would wipe out root anyway, so no point in having to do it twice.
Whether you unlock the bootloader (via HTCDev.com) before or after RUU is somewhat irrelevant. Especially since you have s-off, so its not required to relock the bootloader to RUU (which is required with s-on).
But one other thing to consider. Since you are using the AT&T version on the T-Mobile US network; the ATT version is actually missing support for the AWS band that T-Mob uses in most areas for HSPA (3G). If you are in an area with good LTE coverage (and I'll assume NYC is) you may have not even noticed this. But if you move into an area where T-Mob doesn't have LTE, you might find that you don't have 3G either, and be pushed down to 2G (EDGE) data speed.
One cool thing about the M8, is the band support is actually software based. So one option would be to change your device's carrier ID (CID) and model ID (MID) which are possible with s-off, then flash the T-Mobile firmware or RUU to "convert" the phone to a T-Mob device including the proper T-Mob band support. After that, you can unlock the bootloader, root, flash a custom ROM.
HTCFAN0923 said:
My last question is this: On the M7, I was able to use an international M7 ROM as everything apart from the radios was the same. Is that the case with the M8 as well? I typically like having Sense ROM's but hate the bloat carriers put on their RUU's....
Click to expand...
Click to collapse
Yes, its a similar situation on the M8. All international ROMs should work on the M8. But note that your firmware (hboot, radio, etc.) needs to be the proper version supported by the ROM. So for instance, if you are still on KitKat (sounds like you are) you will want to update firmware first, otherwise if you flash a Lollipop ROM, you will likely suffer major issues such as broken WiFi and extreme long boot times (10+ min).
redpoint73 said:
In that case, I would suggest updating by RUU first, and then root.
Reason I say that, is that RUU would wipe out root anyway, so no point in having to do it twice.
Whether you unlock the bootloader (via HTCDev.com) before or after RUU is somewhat irrelevant. Especially since you have s-off, so its not required to relock the bootloader to RUU (which is required with s-on).
But one other thing to consider. Since you are using the AT&T version on the T-Mobile US network; the ATT version is actually missing support for the AWS band that T-Mob uses in most areas for HSPA (3G). If you are in an area with good LTE coverage (and I'll assume NYC is) you may have not even noticed this. But if you move into an area where T-Mob doesn't have LTE, you might find that you don't have 3G either, and be pushed down to 2G (EDGE) data speed.
One cool thing about the M8, is the band support is actually software based. So one option would be to change your device's carrier ID (CID) and model ID (MID) which are possible with s-off, then flash the T-Mobile firmware or RUU to "convert" the phone to a T-Mob device including the proper T-Mob band support. After that, you can unlock the bootloader, root, flash a custom ROM.
Yes, its a similar situation on the M8. All international ROMs should work on the M8. But note that your firmware (hboot, radio, etc.) needs to be the proper version supported by the ROM. So for instance, if you are still on KitKat (sounds like you are) you will want to update firmware first, otherwise if you flash a Lollipop ROM, you will likely suffer major issues such as broken WiFi and extreme long boot times (10+ min).
Click to expand...
Click to collapse
Crap....went back to the toolkit to flash twrp and root it and lo and behold, my phone is now stuck in the entering recovery screen....How ****ty is that toolkit that it can't do even do a proper recovery flash right...8 years on XDA and I've never had such a headache from rooting/flashing a device....
HTCFAN0923 said:
Crap....went back to the toolkit to flash twrp and root it and lo and behold, my phone is now stuck in the entering recovery screen....How ****ty is that toolkit that it can't do even do a proper recovery flash right...8 years on XDA and I've never had such a headache from rooting/flashing a device....
Click to expand...
Click to collapse
I gave previous advice to stop using the toolkit, so I don't know why you insist on ignoring that advice.
Older versions of TWRP don't work on newer hboots; and the opposite is true where older hboots don't work with newer TWRP builds. This is the most frequent reason for TWRP not working properly.The toolkit worked fine at the time it was updated. But it hasn't been updated in a very long time, and therefore won't work on many M8 versions now. The issue is more your lack of understanding, and lack of following advice given to you.
Flashing TWRP is just a matter of downloading the proper version, and flashing with a single fastboot command (2 commands, if you want to be thorough and wipe cache before flashing TWRP). You don't need a toolkit for that, and again I advise stopping its use altogether.
Its not clear whether you chose to update before TWRP and root (current device status) and once I know the main version (OS number on bootloader screen) and present hboot number I can probably advice what version TWRP you need to flash.
And you're absolutely right about that. It was my fault for not listening. I was being lazy about it honestly.
I did end up using the lollipop pre rooted RUU and that worked after two atttempts. I think the issue was that the toolkit flashed the recovery without root. Add that to the fact that the toolkit caused the SD card issue to pop up made it a nightmare. Thankfully, I was able to fix it and now I'm running the AT&T lollipop ROM rooted.
You truly are the best and I thank you for the advice and help. Let me know your PayPal so I can send you beer money for the trouble.
HTCFAN0923 said:
I think the issue was that the toolkit flashed the recovery without root.
Click to expand...
Click to collapse
I don't follow. Root isn't needed to install custom recovery; nor does flashing custom recovery automatically root the phone (this has to be done as an additional step, usually by flashing SuperSU in TWRP).
I think the main issue was that the toolkit flashed an old TWRP version that was not compatible with the software/firmware that was on your phone.
HTCFAN0923 said:
You truly are the best and I thank you for the advice and help. Let me know your PayPal so I can send you beer money for the trouble.
Click to expand...
Click to collapse
I appreciate the thought; but your thanks is all I expect in return. I've benefited plenty from XDA from folks that don't ask for any monetary compensation; so I just like to give back to the community by helping how I can.