Related
Hi guys,
I've searched everywhere and can't get a definitive answer on this so here goes -
I'm a noob when it comes to Android, having recently defected from being an Apple Disciple (I got hacked off with iTunes and bored in general with the Daycare Centre which is iOS) and have recently acquired an Acer A700 tablet.
I have installed the JB update OTA and everything is working fine and am chomping at the bit to get it booted, but most of the posts I have read regarding unlocking the bootloader and rooting it relate to ICS.
My questions are -
Does the bootloader process apply regardless of Firmware? (Are there different versions for different Firmwares)
Can anyone point me in the direction of a decent tutorial on how to do this?
What happens regarding a future update? Do I have to revert back to stock and update from there or can i jump from one ROM to another? (I'm assuming that I can't use the OTA updates any more)
Sorry for the long OP and thanks in advance for your answers.
ianrobbie said:
Hi guys,
I've searched everywhere and can't get a definitive answer on this so here goes -
I'm a noob when it comes to Android, having recently defected from being an Apple Disciple (I got hacked off with iTunes and bored in general with the Daycare Centre which is iOS) and have recently acquired an Acer A700 tablet.
I have installed the JB update OTA and everything is working fine and am chomping at the bit to get it booted, but most of the posts I have read regarding unlocking the bootloader and rooting it relate to ICS.
My questions are -
Does the bootloader process apply regardless of Firmware? (Are there different versions for different Firmwares)
Can anyone point me in the direction of a decent tutorial on how to do this?
What happens regarding a future update? Do I have to revert back to stock and update from there or can i jump from one ROM to another? (I'm assuming that I can't use the OTA updates any more)
Sorry for the long OP and thanks in advance for your answers.
Click to expand...
Click to collapse
No problem. Seeing you are on JB, then you have a JB bootloader.
You need to go here http://forum.xda-developers.com/showthread.php?t=1953917
And download Vorbeths easyroot2.0. It's for the 700.
You have to unlock your bootloader first, which shouldn't be an issue for you. Easy instructions for that.
Then download his package to a folder on your PC. (not sure, but you may have to download each file individually) Open a command window (shift & right mouse click) and type in whatever his instructions say. Should be painless.
Make sure USB Debugging is turned on first in your tablet (Settings/Developer Options/USB Debugging), and make sure you have the Acer Drivers installed on your PC.
Then connect, wait 30 seconds, and run his batch file.
You should be ok.
MD
Oh yes, one more thing, once you unlock your bootloader, chances are you will not be able to get OTA. And the only way to re-lock the bootloader is to install a stock rom.
Thanks!
Thanks for the reply. I am now the owner of a fully rooted A700!
Had a few issues during unlocking the bootloader. That thing timeouts quick! Also, didn't realise you had to run the .bat file while the tablet was on the Bootloader USB protocol screen. I thought you had to wait until it booted fully into JB.
Anyway, took the plunge and thanks again for your help.
ianrobbie said:
Thanks for the reply. I am now the owner of a fully rooted A700!
Had a few issues during unlocking the bootloader. That thing timeouts quick! Also, didn't realise you had to run the .bat file while the tablet was on the Bootloader USB protocol screen. I thought you had to wait until it booted fully into JB.
Anyway, took the plunge and thanks again for your help.
Click to expand...
Click to collapse
No problem. I thought I mentioned it timed out in about 5 seconds These days I don't remember much
Yeah, I haven't looked at Vorbeth's script, so I don't know which screen he launches it from. With mine for the 701, you can be when the tab is running normal. No difference in the end result though
Happy Hunting!
MD
One last question - do I have to install Clockwork Recovery for re-flashing the stock images or is it just a case of renaming it update. zip and putting it on an SD Card? Any chance you can point me in the right direction of the most recent/stable build? Is it easy to install?
Thanks again.
Sent from my GT-I9305 using xda app-developers app
ianrobbie said:
One last question - do I have to install Clockwork Recovery for re-flashing the stock images or is it just a case of renaming it update. zip and putting it on an SD Card? Any chance you can point me in the right direction of the most recent/stable build? Is it easy to install?
Thanks again.
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Well, this is a trouble spot.
If you wish to install a custom rom, then you will need to install CWM. The most recent version.
If you want to try your luck at installing a stock rom, my opinion, is to leave the stock recovery inplace. I haven't had luck in installing stock update.zips, as Acer has made them very specific. So I can't be much help to you in that.
However, you can always flash back to CWM or a stock JB recovery pretty easy. Personally, unless you plan on flashing a custom, I would just leave the stock recovery.
MD
Sometimes "leaked" update appear here in the forums. They are unofficial. And you never know if they improve things, or make things worse. So be careful.
Moscow Desire said:
Well, this is a trouble spot.
If you wish to install a custom rom, then you will need to install CWM. The most recent version.
If you want to try your luck at installing a stock rom, my opinion, is to leave the stock recovery inplace. I haven't had luck in installing stock update.zips, as Acer has made them very specific. So I can't be much help to you in that.
However, you can always flash back to CWM or a stock JB recovery pretty easy. Personally, unless you plan on flashing a custom, I would just leave the stock recovery.
MD
Sometimes "leaked" update appear here in the forums. They are unofficial. And you never know if they improve things, or make things worse. So be careful.
Click to expand...
Click to collapse
So, just for future reference, how would I go about re-flashing the stock image? I'm assuming it's saved on the tablet in a separate partition?
I've decided to stick with the stock rooted ROM but would like to know how to re-flash for when Key Lime Pie and future updates are released.
And, seeing as how you haven't steered me wrong so far, I though I'd pick your brains one last time.
Hope you don't mind!
Guys, I have spent hours rooting and unlocking my S3. Reason it has taken so long is either I don't know what I'm doing or there are so many ways to do it, some may be outdated or something. I'll side with the first reason. But, I do have experience in rooting...kept my OG Droid rooted/overclocked/customized. Did the same with my Thunderbolt. Also rooted my S3 a few months ago after the VZW update that crapped out the radio. When they released the fix, I removed root and installed it. Got the urge for some new stuff and here I am...
Here is what I'm doing:
- Using CausalR795b. Seems quick and easy. Definitely provides root, but I'm not sure about unlocking the bootloader. What is the insecure aboot? Says it's ready to install it, but I can't find out what this is?
- Trying to install TWRP recovery. What is the easiest way to do this? The last time I did it with Goomanager, I got the Verizon Unauthorized Software message at boot.
- Trying to install the latest Hyperdrive ROM. Got it installed once and on reboot, got the VZW Unauthorized message again,
- Using ODIN 3.07 to flash a stock ROM after getting the error message.
Can anyone tell me a link with good directions, start to finish? Or, give me some advice? To me, at least, seems like VZW has made customizing the S3 unnecessarily complicated,
Thanks in advance.
Insecure aboot is the unlocked bootloader. Once you install that you will no longer get the VZW Unauthorized message.
First welcome to the community.
second, this is the wrong section.
third, you have to use D2VZW-CASUAL-R634b release to fully unlock bootloader
omair2005 said:
First welcome to the community.
second, this is the wrong section.
third, you have to use D2VZW-CASUAL-R634b release to fully unlock bootloader
Click to expand...
Click to collapse
My bad...I did post in the wrong place. Wasn't even thinking about it. Had just spent so long in this subforum trying to find answers, must have lost my bearing.
I really appreciate your help! The older Causal did everything in one try with no hiccups whatsoever. Why isn't anything posted about this noted in the newer Causal thread? It might be in there somewhere and if I would have seen it, hours would have been saved.
Now rocking the newest Hyperdrive and probably going to try a few more ROM's. Thanks again!
Hello XDA Developers,
Okay so here is my unusual situation...
I have two phones. I have one Verizon (d2vzw) SGS3 that I run CM 11 on with CWM Touch installed on that phone. On my second phone which is also a Verizon (d2vzw) SGS3 i was running stock 4.1.2 ROM which was rooted with CWM recovery manager. The stock SGS3 was the baseband version that supported multi windows.
Okay so today i decided to go ahead and check for an OTA update on my stock (rooted) SGS3. I knew there had been an update available for some time but I never decided to update my phone because i figured with it being rooted and with CWM recovery manager installed there was no way that the OTA update would work...
So like an idiot i went ahead and tried the update. I figured what is the worst that could happen? I figured that at the worst it was just going to tell me that the update failed and i would just be stuck with Android 4.1.2 which isn't the end of the world. I really like the multi windows setup. Moving on...i downloaded the update and I hit the install update button. My phone booted into recovery manager and it installed the update. When the phone rebooted I saw the message "Android is upgrading" and i thought whoa! no way!. After android finished upgrading which i believe was the dalvik rebuilding I saw a message in notifications saying "upgrade installation failed", however when i went into settings it now told me that i was running Android 4.3. So to me it looked like the upgrade took but I think the problem was that when it asked me to flash the stock recovery there was an option in CWM to say no and i choose that to keep CWM recovery manager instead of the stock recovery manager. Maybe i should have let the update install the stock recovery manager...
Now i knew ahead of time that if this update worked I was going to loose root but again I didn't think it was that big of a deal since I could just re-root my phone and I would be on a newer Android version. I looked around for the best rooting option and I wanted to use Chainfire's CF-AutoRoot exploit but I know that if you do not have the bootloader unlocked that there is a chance of bricking your phone. So after some research (which i should have done before i updated my phone!) i saw that there was an exploit out called "saferoot.zip" and that you could root your phone running a windows.bat file or a shell script if you are in Linux. Even though the program is for SGS4 many users on XDA with SGS3 phones reported success with "saferoot". So i tried saferoot 2 times with no luck. Finally on the third attempt (3rd times a charm!) i was able to root my phone and SuperSU was able to "disable KNOX".
So i now had my Verizon SGS3 updated from Android 4.1.2 to Android 4.3 and I had successfully re-rooted my phone. I was feeling good...
Until I wanted to make sure that CWM Recovery Manager was still on my phone. I opened up the app "quickboot" and choose to boot into Recovery Manager this is where the trouble began...
When my phone booted into recovery mode i saw a big Yellow Triangle. Under this very scary yellow triangle it said that "Verizon has detected unauthorized software on this phone. Please turn off the phone and take it into your nearest verizon store". Other something along those lines...
I thought I was in big trouble...
I could not get the phone out of recovery mode. I tried pulling the battery but every time my phone rebooted it just kept going back into recovery mode. The trick to get out recovery mode was to hold down Volume Down + Home for a few seconds then press the power button. This brought me to a new menu and i was able to hit "cancel" on installing a new OS and it rebooted my phone back to its normal state.
So finally here is my questions...
Question 1: I know i need to unlock my bootloader again. After you apply an OTA update it re-locks your bootloader right? Does anyone know of a method of unlocking the bootloader with the Verizon (d2vzw) SGS3 baseband version I535VRUCML1 running on Android 4.3?
Before when my phone was running 4.1.2 I unlocked the bootloader with Odin and the app EZ-UNLOCK but i don't think EZ-UNLOCK is going to work with Android 4.3
Question 2: Is there a way to get rid of that message about Verizon has detected unauthorized software on this phone? Now I know that ChainFire has a Yellow Triangle Away app on the Google Play store and I will happily buy it but I know that in order for it to work you first must have your bootloader unlocked right? If i try to use that app with my bootloader in a locked state i could brick my phone permanently right?
Is there possibly any file or exploit i can flash with either Odin or the app "Flashify" so that I can unlock my bootloader. Has anyone here tried unlocking their bootloader on their SGS3 running 4.3 with the app "EZ-UNLOCK" ?
I am very concerned about damaging my phone which is a company work phone so if i mess it up i will be in deep trouble...
Oh, one last question...
Question 3: Since i got that yellow triangle message about unauthorized software when i tried to boot into recovery mode could it have possible been because CWM recovery was somehow deleted with the OTA update? After i was able to get out of recovery mode I used the app "ROM Manager" to install CWM Recovery Again hoping that I might have a recovery manager... Now ROM Manager says that CWM Touch was installed successfully but I am not sure since I am kind of scared to boot into recovery mode again until I unlock this bootloader.
If my recovery manager is being blocked until I get my bootloader unlocked could i use the app "flashify" if i need to flash any files?
I know my situation might be a bit unusual but I am really going to need some help on this and someones expertise advice.
I hope to hear from someone soon...
XDA Members, have a great New Years and make 2014 count!
I thank you all for your time and assistance.
-droidshadow
After accepting the 4.3 OTA, your bootloader is locked and there is no way to unlock it. My suggestion to you would be to grab the 4.3 ODIN file, reflash to 100% stock, root using saferoot, debloat as wanted, and hope for the best.
Probably not what you wanted to hear, but there is no way to unlock the bootloader once taking the 4.3 OTA. Attempting to do so will brick the phone.
well that stinks...
podspi said:
After accepting the 4.3 OTA, your bootloader is locked and there is no way to unlock it. My suggestion to you would be to grab the 4.3 ODIN file, reflash to 100% stock, root using saferoot, unbloat as wanted, and hope for the best.
Probably not what you wanted to hear, but there is no way to unlock the bootloader once taking the 4.3 OTA. Attempting to do so will brick the phone.
Click to expand...
Click to collapse
The only reason that I even attempted the upgrade is because next week I am going to purchasing the smart watch from the Samsung Galaxy Gear. For that watch (you can make calls from the watch) you need the upgrade to pair my SGS3 with my smartwatch when I get it next week.
Now this OTA update is quite new so that means that there still might be a chance to unlock the bootloader eventually when someone works it out right?
Big question:
Is it still possible to have CWM or TWRP with this 4.3 OTA update?
Thanks for the reply.
-droidshadow
droidshadow said:
The only reason that I even attempted the upgrade is because next week I am going to purchasing the smart watch from the Samsung Galaxy Gear. For that watch (you can make calls from the watch) you need the upgrade to pair my SGS3 with my smartwatch when I get it next week.
Now this OTA update is quite new so that means that there still might be a chance to unlock the bootloader eventually when someone works it out right?
Big question:
Is it still possible to have CWM or TWRP with this 4.3 OTA update?
Thanks for the reply.
-droidshadow
Click to expand...
Click to collapse
To bad you took the ota. There is a twrp flashable rom for stock 4.3. And no you can not have custom recovery.
droidshadow said:
Okay so today i decided to go ahead and check for an OTA update on my stock (rooted) SGS3...
Click to expand...
Click to collapse
There's no need to read any further than that.... Sorry to be another bearer of bad news, but if a phone is rooted and you want it to stay that way, "OTA" should be a term that you never, ever, ever even think about !
The S4 boot loader has been locked down with Knox longer than the S3 has, and no one has cracked it yet. I'd say the chances of this boot loader being cracked wide open are slim to none. If unlocking this boot loader were as simple as using EZ unlock 1.2, it would have been written about all over these and all forums.
Sent from the Shark Tank using XDA Premium 4 mobile app
so what entails for the future of samsung phones?
landshark68 said:
The S4 boot loader has been locked down with Knox longer than the S3 has, and no one has cracked it yet. I'd say the chances of this boot loader being cracked wide open are slim to none. If unlocking this boot loader were as simple as using EZ unlock 1.2, it would have been written about all over these and all forums.
Sent from the Shark Tank using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So what is the going to happen to the future of Samsung Phones? Are we no longer going to be able to put custom ROM's and custom Recovery Managers on Samsung Phones?
Will KitKat + SELinux + Knox no longer allow us to enjoy the true beauty of Android? I think that is major BS.
So what are our options now? Are we going to simply have to choose different phones like future Google Nexus phones? I love Samsung phones and I love having the options of flashing custom roms or reverting back to stock and I really really love CWM recovery or TWRP recovery.
These phones are our property...
I understand that the software and the code is Samsung's or Verizon's yet we should be able to do what we want to our property. Could you imagine if Toyota or Chevy said that after you purchased one of their cars you could never paint it a different color or add custom rims + wheels! That would be ridiculous... It is the same concept here really.
It is really sad that Samsung and Mobile carriers such as Verizon have resorted to this...
-droidshadow
droidshadow said:
So what is the going to happen to the future of Samsung Phones? Are we no longer going to be able to put custom ROM's and custom Recovery Managers on Samsung Phones?
Will KitKat + SELinux + Knox no longer allow us to enjoy the true beauty of Android? I think that is major BS.
So what are our options now? Are we going to simply have to choose different phones like future Google Nexus phones? I love Samsung phones and I love having the options of flashing custom roms or reverting back to stock and I really really love CWM recovery or TWRP recovery.
These phones are our property...
I understand that the software and the code is Samsung's or Verizon's yet we should be able to do what we want to our property. Could you imagine if Toyota or Chevy said that after you purchased one of their cars you could never paint it a different color or add custom rims + wheels! That would be ridiculous... It is the same concept here really.
It is really sad that Samsung and Mobile carriers such as Verizon have resorted to this...
-droidshadow
Click to expand...
Click to collapse
Difference is though, if you were to somehow screw up your car by customizing it you wouldn't try to take it back to the dealership and get a new car under a warranty claim. I would have to think at least part of the reason phone manufacturers and mobile carriers are locking down phones is all the "warranty" claims people are submitting after screwing up while rooting and flashing their phones. Warranty claims are for inherent manufacturer defects, not a hard brick from flashing the wrong software. If more people took responsibility for their mistakes and bought a new phone instead of making the carriers or manufacturers pay for their mistakes, perhaps this wouldn't be happening. I'm not saying absolutely, just perhaps. OK, I'll get off my soapbox now. Happy New Year everyone.
Different animal. You own the hardware, but the providers have the right to control the firmware since it can change how the phone interacts with the network.
Just like the firmware in your cars computer. The manufacturer and the federal government have control over what went in. Modifying it can be done, but it is a violation of EPA emission laws.
Modifying the paint, tires, rims etc is like putting a different case, bling etc on your phone
Your phone needs to have the 4.3 odin tar installed to clean the recovery.
Sent from my SCH-I535 using xda app-developers app
droidshadow said:
So what is the going to happen to the future of Samsung Phones? Are we no longer going to be able to put custom ROM's and custom Recovery Managers on Samsung Phones?
These phones are our property...
It is really sad that Samsung and Mobile carriers such as Verizon have resorted to this...
-droidshadow
Click to expand...
Click to collapse
Its really Verizon, They have had many Moto and HTC phones with locked bootloaders , unless Verizon unlocks it, it won't be cracked.
http://forum.xda-developers.com/showthread.php?t=2586319
Sent from my SCH-I535 using xda app-developers app
DigitalMD said:
Its really Verizon, They have had many Moto and HTC phones with locked bootloaders , unless Verizon unlocks it, it won't be cracked.
Click to expand...
Click to collapse
I know but still i think it should be our choice! While there are millions of us out there that love to customize the software on our phone's by adding new recovery managers or custom rom's we are a small population to the rest of the stock phone using world...
Insurance companies make big bucks by all the people who never file a claim...but i won't get into that.
Many of you have made excellent points and i respect that. I especially liked the comparison of car rims to phone cases i thought that was great!
Hopefully someone will work it out soon or some how an unlocked bootloader will get leaked.
Come one Verizon developers! Leak it! We wont tell!
I was planning on getting the NOTE 3 but i doubt that phone comes with an unlocked bootloader so this d2vzw (sgs3) will most likely be my last samsung phone that I ever buy. I guess i will have to stick with the Nexus phones... I am going to miss micro sdcards!
-droidshadow
droidshadow said:
I know but still i think it should be our choice! While there are millions of us out there that love to customize the software on our phone's by adding new recovery managers or custom rom's we are a small population to the rest of the stock phone using world...
Click to expand...
Click to collapse
Having that debate at this site is kinda silly.... Fact is, "we" will lose the fight against the carriers and/or manufacturers as it stands. The only way to really impact them is to STOP giving them our money, but you know what ? The number of people who "hack" their phones is a tiny percentage in the grand scheme. We'd probably get a "good riddance" response from them anyway.
droidshadow said:
So what is the going to happen to the future of Samsung Phones? Are we no longer going to be able to put custom ROM's and custom Recovery Managers on Samsung Phones?
Click to expand...
Click to collapse
That's correct and.... read on.
So what are our options now? Are we going to simply have to choose different phones like future Google Nexus phones?
Click to expand...
Click to collapse
That could be the only solution. I believe the success that Samsung/Verizon have had with locking down their phones will soon result in ALL phones on ALL carriers being locked down with little or no possibility of rooting or flashing.
I suspect we've seen the end of modifying any phone on any network. I sure hope I'm wrong....
It would be a shame....
xs11e said:
I suspect we've seen the end of modifying any phone on any network. I sure hope I'm wrong....
Click to expand...
Click to collapse
I just rooted and got into CM in the last month. Got rid of all the bloat and installed some neat little apps. And now, just when I get hooked, it's possible that my drug of choice may be going away.
hey there guys, i know this post is a little old, but i just wanted to share my story real quickly with you and to reiterate that messing with the boot loader on an sch-i535 running 4.3 is a HORRIBLE idea.
this is the first phone i have ever tried to root. i successfully rooted the phone, immediately i tried to run cwm recovery. HARDBRICK. i was so proud for all of five minutes that i rooted a phone on my first try. The phone would not power on in ANY mode. i could only get a red light to come on by plugging my phone into my computer with the battery out of the phone. after three days and alot of reading and some help from xda i managed to (amazingly) debrick my phone. I am now very VERY cautious of what i do with my rooted sch-i535 with its HORRIBLE 4.3 crap.
If you are truly hardbricked, im told that jigs (despite what is all over the internet) will not work. (maybe they do but a shop in texas told me a hardbrick will not revive by jig).
JTAG is the most dependable repair.
I revived my phone via debrick image on an sd card.
Bottom line, do everything you can to avoid the situation in the first place.
Never take updates. I unlocked boot loader on 4.3 with ez-unlock app booted into recovery and hard bricked my phone... The fun is over after 4.3...Had to send it to Tampa fl. To get JTAG and it worked.
droidshadow said:
So what is the going to happen to the future of Samsung Phones? Are we no longer going to be able to put custom ROM's and custom Recovery Managers on Samsung Phones?
Click to expand...
Click to collapse
That's correct, given the amount of time the Devs have had to find a way to unlock the bootloader on the S3 and S4 w/o success, I believe it's hopeless.
Worse, I believe Samsung will share their technology and ALL cell phones will eventually have locked boot loaders and be un-rootable, un-flashable and, to me, at least, un-desirable!
I sincerely hope I'm wrong but I believe in a year or two any cellphone will be locked down to whatever software is installed at time of purchase.
xs11e said:
That's correct, given the amount of time the Devs have had to find a way to unlock the bootloader on the S3 and S4 w/o success, I believe it's hopeless.
Worse, I believe Samsung will share their technology and ALL cell phones will eventually have locked boot loaders and be un-rootable, un-flashable and, to me, at least, un-desirable!
I sincerely hope I'm wrong but I believe in a year or two any cellphone will be locked down to whatever software is installed at time of purchase.
Click to expand...
Click to collapse
How's the fun over??? Haha I've seen this same junk many times... I'm running 4.3 rooted. Safestrapped (cwmis garbage) alliance 23 build ROM CSC & build prop tweaks on sch-i535v on straightalk att side. Knox removed manually by me. All bands open except domestic 3g. (Working on it now).
So the funs over? I'm confused.. And how is that? Lol take your time. Research. Learn. Adapt. Achieve. If it can be locked. It can be unlocked. I've yet to run across a phone that I couldn't bring back from the supposed "hard brick" but I did find one I COULDNT brick on purpose. And I threw everything at it. Huwaei m8665 I think it was. I tried for two days to brick that little piece of junk, and not even wrong roots etc could. Lol
An0nYm0u5.bat said:
How's the fun over??? Haha I've seen this same junk many times... I'm running 4.3 rooted. Safestrapped (cwmis garbage) alliance 23 build ROM CSC & build prop tweaks on sch-i535v on straightalk att side. Knox removed manually by me. All bands open except domestic 3g. (Working on it now).
So the funs over? I'm confused.. And how is that? Lol take your time. Research. Learn. Adapt. Achieve. If it can be locked. It can be unlocked. I've yet to run across a phone that I couldn't bring back from the supposed "hard brick" but I did find one I COULDNT brick on purpose. And I threw everything at it. Huwaei m8665 I think it was. I tried for two days to brick that little piece of junk, and not even wrong roots etc could. Lol
Click to expand...
Click to collapse
I agree with you if there is a way to lock it there is a way to unlock it.
is just a matter of time some smart brain will figure it out how to and share LOL
Hi Everyone,
As this if my first post just wanted to say that I'm relatively new to customizing my Verizon HTC One M8 and really tried to search around here as well as other places to find answers but I really just wound up getting confused and bogged up in all the different scenarios and things that worked in this version but don't know etc. so apologies if I'm asking a bunch of newbie questions I after a lot of hours I really just couldn't find an up to date comprehensive guide.
So basically I have a Verizon HTC One M8 running Android 4.4.4. and I want to install a custom ROM most likely the DigitalHigh GPE or Skydragon not sure which but regardless I just read a bunch of different guides and started getting frustrated when they didn't work (like going the HTCDev route to realize that that route isn't supported by Verizon or whatever). Currently I have Sunshine installed and am waiting to verify that I can move forward before paying for it.
My question is after I pay for and run sunshine whats the exact route I take to get to where I want to go? I've searched around and found guides but I don't want to be stuck with outdated information that might not work. Thanks a lot for any help you guys can give.
sturdly said:
Hi Everyone,
As this if my first post just wanted to say that I'm relatively new to customizing my Verizon HTC One M8 and really tried to search around here as well as other places to find answers but I really just wound up getting confused and bogged up in all the different scenarios and things that worked in this version but don't know etc. so apologies if I'm asking a bunch of newbie questions I after a lot of hours I really just couldn't find an up to date comprehensive guide.
So basically I have a Verizon HTC One M8 running Android 4.4.4. and I want to install a custom ROM most likely the DigitalHigh GPE or Skydragon not sure which but regardless I just read a bunch of different guides and started getting frustrated when they didn't work (like going the HTCDev route to realize that that route isn't supported by Verizon or whatever). Currently I have Sunshine installed and am waiting to verify that I can move forward before paying for it.
My question is after I pay for and run sunshine whats the exact route I take to get to where I want to go? I've searched around and found guides but I don't want to be stuck with outdated information that might not work. Thanks a lot for any help you guys can give.
Click to expand...
Click to collapse
Since you are on 4.4.4 you first have to figure out if Sunshine will work on your phone, it's more recommended for users on 4.4.3 but you can still try as some people have had success. If it doesn't work, it will not charge so you don't have to worry. about paying and it not working.
sturdly said:
Hi Everyone,
As this if my first post just wanted to say that I'm relatively new to customizing my Verizon HTC One M8 and really tried to search around here as well as other places to find answers but I really just wound up getting confused and bogged up in all the different scenarios and things that worked in this version but don't know etc. so apologies if I'm asking a bunch of newbie questions I after a lot of hours I really just couldn't find an up to date comprehensive guide.
So basically I have a Verizon HTC One M8 running Android 4.4.4. and I want to install a custom ROM most likely the DigitalHigh GPE or Skydragon not sure which but regardless I just read a bunch of different guides and started getting frustrated when they didn't work (like going the HTCDev route to realize that that route isn't supported by Verizon or whatever). Currently I have Sunshine installed and am waiting to verify that I can move forward before paying for it.
My question is after I pay for and run sunshine whats the exact route I take to get to where I want to go? I've searched around and found guides but I don't want to be stuck with outdated information that might not work. Thanks a lot for any help you guys can give.
Click to expand...
Click to collapse
Hey bud, we'll get you where you need to be. First off, unless it's the 4.4.4 under the Verizon forums, don't flash Skydragon as it is for the GSM version. I would recommend going with DHs, but beware *some* people have issues with data with that ROM. Here's the easiest way to get you where you need to be.
1. Go ahead and get S-off with sunshine. With S-off, you can flash RUUs.
2. Download this RUU and place it on your sd card, or use the executable method, both work flawlessly. Note that this will reset your phone, but you're flashing a ROM anyways. This is rooted. http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-4-s-off-onlynewest-t2914914
3. Confirm root and download flashify from the playstore.
4. Flash the recovery of your choice (most, myself included, prefer TWRP)
Now you are rooted with a custom recovery and good to go. If you flash DHs GPE, you will need to update to the 5.0 firmware first for best results. To do this, just place it (https://www.androidfilehost.com/?fid=95832962473400175) on your sd card and boot into hboot by turning off your device, then hold volume down and the power button until it boots into a white screen with multi-colored text. This is hboot. From there, the device should auto detect the firmware on your sd card and press volume up to flash it. Volume up once more to confirm it. To confirm that you are on the new firmware, go back into hboot and check the opendsp number, it should something other than 46.2.2. Delete the firmware from your sd card so hboot doen't keep prompting you to run it every time you boot into hboot. From here, you should be all good to flash DHs ROM. If there is anything else I can help with or you get stuck at any point, let me know and we'll figure it out.
bjoostema said:
Hey bud, we'll get you where you need to be. First off, unless it's the 4.4.4 under the Verizon forums, don't flash Skydragon as it is for the GSM version. I would recommend going with DHs, but beware *some* people have issues with data with that ROM. Here's the easiest way to get you where you need to be.
1. Go ahead and get S-off with sunshine. With S-off, you can flash RUUs.
2. Download this RUU and place it on your sd card, or use the executable method, both work flawlessly. Note that this will reset your phone, but you're flashing a ROM anyways. This is rooted. http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-4-s-off-onlynewest-t2914914
3. Confirm root and download flashify from the playstore.
4. Flash the recovery of your choice (most, myself included, prefer TWRP)
Now you are rooted with a custom recovery and good to go. If you flash DHs GPE, you will need to update to the 5.0 firmware first for best results. To do this, just place it (https://www.androidfilehost.com/?fid=95832962473400175) on your sd card and boot into hboot by turning off your device, then hold volume down and the power button until it boots into a white screen with multi-colored text. This is hboot. From there, the device should auto detect the firmware on your sd card and press volume up to flash it. Volume up once more to confirm it. To confirm that you are on the new firmware, go back into hboot and check the opendsp number, it should something other than 46.2.2. Delete the firmware from your sd card so hboot doen't keep prompting you to run it every time you boot into hboot. From here, you should be all good to flash DHs ROM. If there is anything else I can help with or you get stuck at any point, let me know and we'll figure it out.
Click to expand...
Click to collapse
Thanks so much for the detailed explanation! I suppose its worth mentioning that my end goal is to run a ROM that's close to stock Android 5. Certainly don't mind resetting my phone, I have my contacts and whatnot backed up and being my first android phone I have tons of crap I don't need on it anyway. That being said, would you recommend DH's ROM or another one for my needs? Also in step 2, to clarify, once I apply the RUU that will root my phone or will I have to do that with a separate method?
Also @The Stig 04 thanks for the heads up, I ran the test they have and it told me it would work with 4.4.4, certainly reassuring that they'll refund if it doesn't work so appreciate that
sturdly said:
Thanks so much for the detailed explanation! I suppose its worth mentioning that my end goal is to run a ROM that's close to stock Android 5. Certainly don't mind resetting my phone, I have my contacts and whatnot backed up and being my first android phone I have tons of crap I don't need on it anyway. That being said, would you recommend DH's ROM or another one for my needs? Also in step 2, to clarify, once I apply the RUU that will root my phone or will I have to do that with a separate method?
Also @The Stig 04 thanks for the heads up, I ran the test they have and it told me it would work with 4.4.4, certainly reassuring that they'll refund if it doesn't work so appreciate that
Click to expand...
Click to collapse
No problem buddy! DHs is GPE, so it'll be the closest to stock android that you can get right now, well Google's take on Android anyways. There are a few AOSP roms running around, but I personally have never had an AOSP ROM run in the past year that wasn't ridden with bugs. Plus DHs ROM has an almost completely working Sense camera, which I personally found as a plus since the quality of the 4 ultra pixels on AOSP is almost painful haha. I think another good rom that is actually Sense based but looks and functions a lot like stock Lollipop is Unsense. So step two where you run the RUU will actually redownload and install the same version of OS you have now but it will come rooted and no other further action will be needed to have root access. I found this to be the easiest way to go about it without having to use ADB to install TWRP and flash SU. It takes a few minutes longer since it has to reinstall the OS but is less steps than the ADB route and far easier to explain. Either one will provide the same result, I just prefer the simplicity of running the RUU
bjoostema said:
No problem buddy! DHs is GPE, so it'll be the closest to stock android that you can get right now, well Google's take on Android anyways. There are a few AOSP roms running around, but I personally have never had an AOSP ROM run in the past year that wasn't ridden with bugs. Plus DHs ROM has an almost completely working Sense camera, which I personally found as a plus since the quality of the 4 ultra pixels on AOSP is almost painful haha. I think another good rom that is actually Sense based but looks and functions a lot like stock Lollipop is Unsense. So step two where you run the RUU will actually redownload and install the same version of OS you have now but it will come rooted and no other further action will be needed to have root access. I found this to be the easiest way to go about it without having to use ADB to install TWRP and flash SU. It takes a few minutes longer since it has to reinstall the OS but is less steps than the ADB route and far easier to explain. Either one will provide the same result, I just prefer the simplicity of running the RUU
Click to expand...
Click to collapse
Right on, I'll probably stick with DH's ROM. Thanks again, I'm about to hunker down and start this process, lol I'm glad I made the switch but am mildly missing the days where I could just click a few buttons and have a Jailbroken iPhone.
sturdly said:
Right on, I'll probably stick with DH's ROM. Thanks again, I'm about to hunker down and start this process, lol I'm glad I made the switch but am mildly missing the days where I could just click a few buttons and have a Jailbroken iPhone.
Click to expand...
Click to collapse
I had an Ipone for about 3 months and never had the guts to modify to because I didn't know how to fix it if I broke it haha. There are a lot of individual steps but the process as a whole should go smoothly. Just follow the threads and you will be fine and if you get snagged on anything or need clarification, just let me know man!
bjoostema said:
I had an Ipone for about 3 months and never had the guts to modify to because I didn't know how to fix it if I broke it haha. There are a lot of individual steps but the process as a whole should go smoothly. Just follow the threads and you will be fine and if you get snagged on anything or need clarification, just let me know man!
Click to expand...
Click to collapse
Hey just wanted to let you know I just finished up and it worked like a charm. Love my new phone! Thanks again!
sturdly said:
Hey just wanted to let you know I just finished up and it worked like a charm. Love my new phone! Thanks again!
Click to expand...
Click to collapse
Awesome man! I'm stoked for you, enjoy and no problem!
Looked through google, looked through threads, can find nothing whatsoever to help.
Have Verizon Samsung Galaxy S III Unlocked running Straight Talk VIA sim card. Everything works.. as a regular old phone with root. (rooted with Kingoroot - basically I googled "root galaxy s3" and followed those steps.. that much works fine, though it is not to be confused with the chinese king root. I tried the trick of swapping out king root for SU and, well.. yeah didnt work.)
Problem is I'm running 4.4.2 (the dreaded locked bootloader) and everything I try when it comes to installing custom recovery either doesn't work, bootloops the phone, or hard bricks it. v_v
so as someone who backs up their backups, (thank you OCD fairy), running around with a phone I can't backup puts me on edge, to say the least.
tried safestrap (says not secured. still says not secured after install. does nothing.)
tried various CWM and TWRP via apk installs (whatever that app is you install then tell it to install cwm) ..wouldn't install
Odin, depending on which version I install (e\ not which version of odin, which version of custom recovery), either gives me errors or hardbricks my device.
SO.. I'm looking for someone who has a Verizon Galaxy S III and who has a custom recovery on it to tell me how the devil they managed that one.
Cheers all!!
Drach0n said:
Looked through google, looked through threads, can find nothing whatsoever to help.
Have Verizon Samsung Galaxy S III Unlocked running Straight Talk VIA sim card. Everything works.. as a regular old phone with root. (rooted with Kingoroot - basically I googled "root galaxy s3" and followed those steps.. that much works fine, though it is not to be confused with the chinese king root. I tried the trick of swapping out king root for SU and, well.. yeah didnt work.)
Problem is I'm running 4.4.2 (the dreaded locked bootloader) and everything I try when it comes to installing custom recovery either doesn't work, bootloops the phone, or hard bricks it. v_v
so as someone who backs up their backups, (thank you OCD fairy), running around with a phone I can't backup puts me on edge, to say the least.
tried safestrap (says not secured. still says not secured after install. does nothing.)
tried various CWM and TWRP via apk installs (whatever that app is you install then tell it to install cwm) ..wouldn't install
Odin, depending on which version I install (e\ not which version of odin, which version of custom recovery), either gives me errors or hardbricks my device.
SO.. I'm looking for someone who has a Verizon Galaxy S III and who has a custom recovery on it to tell me how the devil they managed that one.
Cheers all!!
Click to expand...
Click to collapse
A custom recovery can only be flashed on an unlocked bootloader. Trying to flash a custom recovery on a locked bootloader will result in a brick. The only available recovery on it is safestrap
Sent from my Nexus 5
ShapesBlue said:
A custom recovery can only be flashed on an unlocked bootloader. Trying to flash a custom recovery on a locked bootloader will result in a brick. The only available recovery on it is safestrap
Sent from my Nexus 5
Click to expand...
Click to collapse
..I gathered that. I was basing my attempts off the threads I found where the OP "forgot" to mention which android OS he was using on his (or her) galaxy s3 and then omigawd installed custom recovery on it. Where nobody has yet been able to unlock the 4.3 and 4.4.2 bootloader for the galaxy s3 as yet (to my knowledge; if I'm wrong please correct me) this leaves me with safestrap, the custom recovery that doesn't touch the bootloader during install. I know this as well. Perhaps I should have clarified this, but I thought it was obvious to the folks at xda. *shrugs*
And the part where I said safestrap isn't working for one reason or another is where I was hoping to attract someone who knew how to help instead of someone who only knows how to make generic statements (+1) [e\ ftr, attempting to flash non-safestrap recoveries resulted in an error 4 times out of 5, not a brick.]
that said, I will ask again, if someone has 4.4.2 on their s3 as well as custom recovery, please come post here.
sadly, inb4 more +1ers
When you ask a question that's been asked and answered dozens of times before, you're going to get the same "generic statement" in response, because it's the right answer to your question. Your bootloader can't be unlocked, and therefore you can't install a custom recovery on your phone.
Jacquestrapp said:
When you ask a question that's been asked and answered dozens of times before, you're going to get the same "generic statement" in response, because it's the right answer to your question. Your bootloader can't be unlocked, and therefore you can't install a custom recovery on your phone.
Click to expand...
Click to collapse
*sigh* another illiterate. Try reading before posting yeah? I *know* my bootloader cant be unlocked, and I know that a custom recovery /can/ be installed, or are you saying safestrap doesn't exist? look I'm asking for help here not drivel.
..rerolling..
Q: What did you have for breakfast today?
A1: last week, I had breakfast in Deleware!
A2: Last night's dinner was good!
...
xda: the community where post count means more than relevant answers.
*sigh*
looks like I'm going to have to figure out safestrap on my own. whether there is another method for installation besides via apk, why it failed to install, whether safestrap is the only custom recovery that works by not touching the bootloader, why it hardbricked my phone.. etc
guess I'll post the answers somewhere intelligent like Android Authority.
have fun with your +1s
now go die in a fire. cheers
Drach0n said:
Q: What did you have for breakfast today?
A1: last week, I had breakfast in Deleware!
A2: Last night's dinner was good!
...
xda: the community where post count means more than relevant answers.
*sigh*
looks like I'm going to have to figure out safestrap on my own. whether there is another method for installation besides via apk, why it failed to install, whether safestrap is the only custom recovery that works by not touching the bootloader, why it hardbricked my phone.. etc
guess I'll post the answers somewhere intelligent like Android Authority.
have fun with your +1s
now go die in a fire. cheers
Click to expand...
Click to collapse
Honestly I answered your question. It's hard to talk about safestrap other than what I've learned about it. The other member was right, it gets tiring answering the same questions all the time and once in awhile people don't appreciate the answers they are given.
There are threads for safestrap as well as most of the options here on xda. And feel free to go to another forum, your posting questions in a dying forum for the VZW S3. There's not many people who are really that interested in the locked down version anymore. It's very sporadic as far as people and questions go. But to be rude about it just isn't needed.
It's not about post count at xda it's about helping the community. I've been around here long enough to know this. And if you feel someone isn't helpful there's something called a PM instead of calling them out here on the forums. I grow tired of people not being appreciative of anything when someone takes the time to do there best to explain something to someone else
Sent from my Nexus 5
running 4.4.2
PM sent. I might be able to help with that.