Related
This guide will enable you to easily root your phone in 6 steps. I've taken out the mystery and complications.
1) Go to HTC Dev site and manually unlock your bootloader. Select "register" and create your account.
1a) After you are registered select "all other supported models" in the pull down box
1b) Click "begin unlock bootloader". it will ask "are you sure" yes of course you are. acknowledge legal terms. then continue.
1c) Ignore the battery pull instructions as we can't pull the battery. hold down the power key and the volume down key until the bottom buttons stop flashing and your phone shuts off (don't worry if you take a screenshot. It happens all the time). then release ONLY THE POWER BUTTON. Keep holding the volume down key until the bootloader screen shows up.
1d) Follow "step 3" and the rest of the instructions as listed on the HTC site to unlock your bootloader manually.
2) Install android ADB/SDK on your pc. This video shows how to do it nicely:
2a) ****NEW UPDATED 03/05/13*** Alternatively if you DON'T want to install ADB/SDK you can just download the NON-FLASHABLE platform-tools.zip file located in my dropbox folder here.
Just extract this folder to your desktop using WINZIP or whatever archive tool you use and proceed to step 3.
3) Open a command line in your "platform-tools" folder by holding shift+right click anywhere within the folder and selecting the menu option "open a command window here". Then click here to install TWRP using fastboot. Follow the "Download - Fastboot Method:" instructions.
3a) If your phone isn't detected by windows please install the proper USB drivers for your operating system. Go here for 32bit. Go here for 64 bit.
4) Flash SuperSu and Busybox on your device:
4a) Click here and download the latest version of SuperSu. save it to your sdcard.
4b) Go to my dropbox and download Busybox 1.20.2 and save it to your sdcard.
5) Reboot into recovery (via the bootloader selection)
6) Flash the SuperSu zip and the Busybox zip listed in 4a and 4b
That's it!
"So now what?" you may be asking.
You are now free to flash ROMs that support s-on.
Two are my favorites are
(1) Stock with Goodies. (my personal favorite and the one I use today). This is a great ROM for beginners and people who prefer a slimmed down ROM (minus the bloat) and lots of free memory!
(2) Viper4G. This is a ROM for more experienced users and offers TONS of customization.
You can also run apps from Google play that required ROOT access!
If you're feeling slightly adventurous you can flash a custom kernel (which will allow you to overclock your phone). Two of the kernels I use are:
(1) ElementalX by flar2. Click here to take a trip over there. This one is especially important to flash as it seems HTC was up to shenanigans with the latest HBoot (2.09).
If you're unlucky enough to have HBoot 2.09 they have RESTRICTED access to your /system partition. What does this mean to you? It means that if any app writes to your /system partition (ROOTED or not) the phone will "panic" and reboot. Shady behavior if you ask me. The solution? Flash this kernel! it will give you write access so that everything works properly.
(2) The Arc-Reactor kernel! This one is for people that are s-off (see below for an explanation of s-off) only! It's the kernel I currently use and is the fastest kernel out there! Highly recommended if you decide to go s-off!!!
If and when you're feeling more adventurous you can go "s-off" (security off) which removes any security limitations of your phone. It makes flashing ROMs and updating firmware a lot easier. You can find out about s-off by taking a trip over to the DirtyRacun thread here. I will NOT walk you through this process. They will totally help you on their IRC channel. Just read post # 1 in that thread.
There's also a new method of s-off which literally takes 2 minutes. It's called facepalm and is located here But is NOT for the feint of heart, bad typers, nor people that cannot follow instructions! Why? One typo here and your phone is a brick. A paperweight. Useless. Well...you can recover...but that's not the purpose of this thread. If you DO brick your phone PM me. I'll help you out.
I take NO credit for any of this. It's all out there to learn I just put it all together. In one spot. Any questions feel free to PM me.
If I helped you out hit the THANKS button...or buy me a beer! Either way lol!
Tested and works with 3.16.651.3 (even if you took the OTA and have hboot 2.09 and are s-on)
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
lancemoreland said:
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
Click to expand...
Click to collapse
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
rawintellect said:
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
Click to expand...
Click to collapse
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
lancemoreland said:
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
Click to expand...
Click to collapse
Indeed this is a well documented problem but really not what this thread is about. Perhaps you can check out THIS thread where they are discussing this issue at length and hopefully they will come up with a solution for it?
http://forum.xda-developers.com/showthread.php?t=1538053
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
rawintellect said:
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
Click to expand...
Click to collapse
Yes I am participating in that thread. Chainfire is looking for a work around for his specific app, other apps that write to the system partition will no longer work. The point is that with Hboot 2.09 there are limitations and we will not enjoy full root as we have before when we were s-on.
Updated with an alternative superuser program.
SuperSU would ask to update binary and then just reboot. This fixed my problem for being able to access/deny and turn off messages. However it did not uninstall superSU will this cause a conflict having them both?
Edit: Okay I am dumb, I had to uninstall superSU first. Then I reflashed superuser to be able to have root privileges for my apps. When I just reflashed superuser hoping it would get ride of and superuser and keep root it did not.
Thanks it worked!
Help with rooting please.
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
MrSteez said:
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
Click to expand...
Click to collapse
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Updated thread with instructions on manually uninstalling supersu first before installing superuser 3.2
Thank you very much!
rawintellect said:
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Click to expand...
Click to collapse
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
MrSteez said:
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
Click to expand...
Click to collapse
yes. going back to stock is as simple as this:
(1) Boot your phone into the bootloader. make sure fastboot is selected. if you have the drivers installed correctly your phone will read "fastboot usb"
(2) if you followed my instructions on rooting you have ADB/SDK installed. so issue the command to relock your phone. type: fastboot oem lock
(3) run the RUU for 3.15.651.16. Done. Your bootloader will say *relocked* but it will be 100% stock.
Uh oh
I think i messed up. I did not see busy box installed and SuperSU is not updating.
The file listed in step 6 contains busybox. It also contains supersu. You want to flash the superuser file after flashing the file in step 6. It will overlay supersu with superuser 3.2. There is no need to update superuser 3.2 once you flashed it. It is the latest release.
Sent from my EVO using xda app-developers app
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
mobilecj said:
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
Click to expand...
Click to collapse
I replied to your email. But check my first post on the subject of superuser and how to uninstall supersu. if you need to that is. I tested this myself and it did uninstall supersu for me by just flashing superuser 3.2. Some people have reported this doesn't work for them.
okay sorry just got both i am going to try it now.. Its all knew to me it seemed like the information was explaining a dual process and i only had acquired one problem.. will post back in a few!
I have a stock rom evo 4g LTE, rooted, with Android 4.0.3 on it.
I forget the root app I used, some one click thingy, I guess my bootloader is unlocked
because I get a boot menu every time I reboot, on that screen that says **TAMPERED**.
Anyway, I ignored the notification icon in my taskbar for OTA updates, for a very long time.
Since the day I bought it over a year ago.
Finally I decided "eh, screw it, why not." ...I'm sure I'll regret that.
I told it to do the OTA update, and it downloaded (I think??) and rebooted.
The icon went away. Seemed to be a done deal.
But once per day since then, my phone rings, and I see a prompt saying
there's an OTA update, and would I like to install it now?
I think it's the same OTA update being prompted repeatdly,
because the filesize is always the same (~42 megs).
What should I do? I can choose install, reboot, and be fine for the rest of the day,
or choose cancel, reboot, and be fine for the rest of the day.
Doesn't seem to matter. But would be nice to fix it for good.
Well, considering that you are about 4-5 OTAs behind the rest of the community, I would say that the notification is probably correct. HOWEVER, of you are not using the stock recovery, then the OTA did not flash. Yes, the phone rebooted, but that's because it is installed entirely through recovery, and the phone has to reboot to get into recovery mode in the first place.
Now, for the more important question at hand....why exactly are you still using ICS? Furthermore, if you are still using ICS, then why are you rooted? As far as I'm concerned, the OTAs are actually necessary updates for the phone. I'm sure that you will love Jelly Bean if you have never used it before.
And please, for the sake of us all who are cringing at the sight of the first sentence....PLEASE UPDATE your phone! If you have a good reason not to, please share.
Hi, thanks for the reply... Maybe they were all different updates after all.
I haven't been prompted to update again since my post.
Maybe I grabbed the 3 or 4 OTA updates that I needed to catch up on.
I do think I'd like Jelly Bean too, seeing some of the features is what prompted me to finally catch up.
Can you explain this part to me? I'm not familiar with this stuff.
HOWEVER, of you are not using the stock recovery, then the OTA did not flash.
Yes, the phone rebooted, but that's because it is installed entirely through recovery,
and the phone has to reboot to get into recovery mode in the first place.
Click to expand...
Click to collapse
So, there's more than one recovery mode, the stock one, and ...whatever else you can install?
When I see the white screen that says **TAMPERED** (looks basically like this screen)...
should I have chosen Recovery instead of the usual reboot option?
If I no longer see the notification, does that mean the updates worked? My Android version still shows 4.0.3.
why exactly are you still using ICS? Furthermore, if you are still using ICS, then why are you rooted?
Click to expand...
Click to collapse
Well, I had no compelling reason to upgrade. I still don't really, the phone does what I want,
I just saw some of the features in the next version and thought "huh, that sounds pretty cool".
I'm rooted for all the usual reasons... I want to be able to browse, copy, move, rename files (including system files)
without incident... use nandroid for backups... wifi tether (still can't get that to work actually)... install unapproved apps...
tweak the OS, and so on.
Ok, my friend...let me educate you. Instead of giving you the simplest, fastest solution, I will actually try to answer all of your questions, since you did ask.
I do think I'd like Jelly Bean too, seeing some of the features is what prompted me to finally catch up.
Can you explain this part to me? I'm not familiar with this stuff.
Click to expand...
Click to collapse
To give a very superficial explanation of Jelly Bean, it is everything that ICS does, and more. It just does it smoother. It also brings Google Now, which was – and still is – the selling point of Jelly Bean. The Sense launcher got a few changes, too, but you will have to explore those changes on your own (mainly because I don’t remember them off hand, and this post is beginning to become lengthy).
Maybe I grabbed the 3 or 4 OTA updates that I needed to catch up on.
If I no longer see the notification, does that mean the updates worked? My Android version still shows 4.0.3.
Click to expand...
Click to collapse
If the first update didn’t update properly, then the phone is simply downloading and trying to install the same update over and over. When you boot back into Android after a successful update, you will be greeted by a welcome message congratulating you for installing the new version.
If you are rooted, odds are, you are using a custom recovery, such as TWRP or CWM. OTAs are only installed through the stock recovery & a locked bootloader. The stock recovery doesn’t make nandroids, or do anything of the sort. To install the stock recovery, go here:
http://downloadandroidrom.com/file/HTCEvo4GLTE/rooting/Evo4GLTERoot2.zip
Click to expand...
Click to collapse
The stock recovery is located somewhere within the zip file.
So, there's more than one recovery mode, the stock one, and ...whatever else you can install?
When I see the white screen that says **TAMPERED** (looks basically like this screen)...
should I have chosen Recovery instead of the usual reboot option?
Click to expand...
Click to collapse
You can flash install the stock recovery by using fastboot commands from the bootloader (which is the screen that shows the TAMPERED status on the top), or you can use Flash Image GUI. It is a paid app on the Play Store, or you can get it from XDA (the dev let XDA users download it for free…Google it).
Lastly, there are a few things that I suggest that you do. First, obtain S-Off (Google, Google, Google...very simple), so you can install the new firmwares directly, instead of using OTAs. Otherwise, if you accept the OTA, you will lose root, and you will have to root your phone again and again. Installing the firmware, then the new rom is the same as accepting the OTA, then rooting.
Another alternative is to get S-Off, then accept the OTA (after installing the stock recovery). Your bootloader does not need to be locked, and there are recovery zips floating around here that can be installed through the bootloader (therefore, you will not be stuck rooting the phone the hard way, just boot into recovery and flash SuperSU). I highly suggest achieving S-Off.
If you want to jump straight to the latest version (Android 4.3, Sense 5.0) by installing the RUU located somewhere in this forum. I actually suggest that you try Sense 4 with Jelly Bean first, but that is completely up to you. Keep in mind that using the RUU will wipe your internal memory, so back up what needs to be backed up. This doesn’t require you to be rooted, and the state of the bootloader does not matter. It will lock the bootloader, load the stock recovery, and you will lose root. You won’t be able to downgrade without S-Off.
Other Notes:
When using the 4.3 RUU, make sure that Android USB Debugging is enabled.
Bookmarking for later but I wanted to say thanks for the thorough reply!
I can confirm the update never worked, because I never got the confirmation message
and I got prompted again a few hours after I posted.
Are you willing to answer just a few more things?
Based on what I've read, it sounds like this is what I ought to do:
- Back up anything I need to. Just to confirm, updating firmware and flashing a new rom wipes out everything in the phone's internal memory, but not external SDcard? Or both?
Are apps considered "on the cloud" and I can reinstall by just redownloading, without paying again?
Except sideloaded apps? Or will I need to find all those APK files and save them somewhere else?
Is it safe to say they're all in \data\app and \system\app? Or would system\app be unwanted since it's what came with the old phone OS?
- Get my phone into S-OFF status.
- Update firmware (this is a separate process from updating the rom? Where do I get this firmware? Google google google?)
- Install a new ROM (stock or otherwise) which will have these updates built in, so I won't need to regain root.
- Not sure what my bootloader is, maybe TWRP, does it matter? Do the above steps affect it? Should I change it to stock anyway?
- You suggested trying Sense 4 rather than Sense 5 first... any special reason?
Are you willing to answer just a few more things?
Click to expand...
Click to collapse
As always, I'm open for questions. Not to sound egotistic, but I enjoy sharing my opinion.
Based on what I've read, it sounds like this is what I ought to do:
- Back up anything I need to. Just to confirm, updating firmware and flashing a new rom wipes out everything in the phone's internal memory, but not external SDcard? Or both?
Updating to the 4.3 firmware wipes your internal memory, not your sd card (although, that may be a very unfortunate circumstance, so it should be backed up as well). The other firmware updates do not affect your memory.
Are apps considered "on the cloud" and I can reinstall by just redownloading, without paying again?
Technically, yes they are "on the cloud." The fact that you paid is saved somewhere within your main Google account that you downloaded the app with. It is possible to pay for apps with your secondary gmail account, which can be switched within the Play Store app.
Except sideloaded apps? Or will I need to find all those APK files and save them somewhere else?
Use Titanium Backup if you can't find the apks. I do save my apks that I download, and I also upload them to Google Drive, since I have multiple Android devices, and I also have a faulty micro sd card that I am yet to replace. I can lose my data at any given moment, but everything is backed up, so I'm not worried.
Is it safe to say they're all in \data\app and \system\app? Or would system\app be unwanted since it's what came with the old phone OS?
Everything within the /system folder is wiped when you flash new roms. That data is NOT backed up while flashing between roms. Also, since it is from an older Android version, it's best to leave them alone. You may back up the data if you like, but I would refrain from restoring the apks along with the data.
The /data directory may be wiped, depending on the dev who built the rom zip. If they added the superwipe script, then /data will be wiped as well. Most devs do not include this, since many people "dirty flash," which is flashing new roms or updates of the current rom without wiping /data first.
- Get my phone into S-OFF status.
You will save yourself a LOT of headaches in the future. It was my S-Off status that allowed me to reflash my firmware when I lost the function of my data/voice antennas while carelessly flashing a port of a phone on a different carrier. Also, if you feel curious to try AOSP roms, then you do not need to do any extra steps to flash them.
- Update firmware (this is a separate process from updating the rom? Where do I get this firmware? Google google google?)
Yes, the firmware handles manages how the hardware of the phone operates. Updating the rom changes how the software looks and behaves. The kernel is sort of a bridge between the firmware and the software, since it manages the firmware (like battery life, processor speed, antennas, etc.), but the kernel is dependent on the software version. The firmware is not dependent on the software version, just as the software version is not dependent on the firmware version.
The only exception of the firmware/software independence is the 4.3 update, which requires a complete update of the firmware, and the older software cannot run on the new firmware without being modded by a dev.
- Install a new ROM (stock or otherwise) which will have these updates built in, so I won't need to regain root.
- Not sure what my bootloader is, maybe TWRP, does it matter? Do the above steps affect it? Should I change it to stock anyway?
Your bootloader is the white screen that shows the TAMPERED status on the top, and little Androids on skateboards on the bottom. With the exception of the firmware information in the top left corner, this screen does not change...ever.
TWRP is your recovery image, which is accessible through the RECOVERY option in your bootloader, or you can boot directly into it through different apps in Android - Titanium Backup is one of them (yes, that's one of the options, even for the free version).
The only reason to return your recovery to stock is to accept OTAs, and also to bring your phone back to the complete factory settings, just as the day when it was first purchased (for the sake of selling the phone, or returning back to Sprint for service}. Otherwise, don't bother with it. You may want to update your version of TWRP, though. If you update to 4.3, you will have to update it. I'm not going to take the time to get into that right now. I've given you enough homework.
- You suggested trying Sense 4 rather than Sense 5 first... any special reason?
I am a very patient person. To me, exploring Android takes time. I enjoy reading before I test, and testing before I settle (which I'm yet to "settle"). All of that being said, I suggested Sense 4 before Sense 5 because I wanted you to experience the both of them. They are truly two different versions of Sense, which one might not realize, as their version numbers are differentiated by one integer (in other words, 4 to 5). Sense 3 was a small step above Sense 2, and Sense 4 was a bigger step from Sense 3. Sense 5 is a complete overhaul of the Sense UI, save the flip clock.
I just feel that skipping from 4.0 to 4.3 is missing out on a great experience, but that is mainly if you actually want to try out different roms. Until the Sense 5 RUU, I still visiting ICS on occassion, but I usually didn't last more than 3 hours before I jumped back to JB.
Click to expand...
Click to collapse
Whew...you're making me work. But I like it. Anymore questions? Feel free to ask.
OK I've been working on this all afternoon and I'm at an impasse.
You've been a huge help so far and I hope you can guide me through this part.
I want to S-OFF and am following a tutorial: http://www.thefortressofnerditude.com/s-off-your-sprint-htc-evo-4g-lte/
Step 3 says root and install recovery. So I decide I need TWRP.
Already have nandroid and titanium backups both completed.
And I copied the whole SDcard to my computer after.
Annoyingly, TWRP's install page suggests that I need to be in S-OFF.
TWRP says I need S-OFF. S-OFF guide seems to suggest I need TWRP working.
I installed "TWRP Manager". Realize that might not be the same thing as TWRP.
Googled and found it on the TeamWin page.
The page asks first to input my device. I choose Evo 4G LTE (Jewel).
That brings me to this page: http://teamw.in/project/twrp2/98
They suggest I do the android app install method. I follow the first link (Market Link)
and install GooManager, and follow their steps.
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will reboot and install the recovery automatically.
This all goes smoothly, but here's my issue.
It doesn't reboot automatically, or install anything automatically.
I see in the comments a recommendation to reboot into recovery mode.
I choose that in GooManager's menu, and after rebooting I get my bootloader screen with 4 menu options:
Bootloader
Reboot
Reboot Bootloader
Power Down
The only one that sounds sensible to me is bootloader so I pick that.
Now I get some new options:
Fastboot
Recovery
Factory Reset
Clear Storage
Simlock
Image CRC
Show Barcode
So, the only one that makes sense is Recovery. I choose it. The phone reboots.
Now I'm back at the first menu. So I'm in a loop.
Nothing I do in this loop seems to install anything.
So I just rebooted the phone normally and I'm back to my OS.
Where to go from here?
CreeDo said:
OK I've been working on this all afternoon and I'm at an impasse.
You've been a huge help so far and I hope you can guide me through this part.
I want to S-OFF and am following a tutorial: http://www.thefortressofnerditude.com/s-off-your-sprint-htc-evo-4g-lte/
Step 3 says root and install recovery. So I decide I need TWRP.
Already have nandroid and titanium backups both completed.
And I copied the whole SDcard to my computer after.
Annoyingly, TWRP's install page suggests that I need to be in S-OFF.
TWRP says I need S-OFF. S-OFF guide seems to suggest I need TWRP working.
I installed "TWRP Manager". Realize that might not be the same thing as TWRP.
Googled and found it on the TeamWin page.
The page asks first to input my device. I choose Evo 4G LTE (Jewel).
That brings me to this page: http://teamw.in/project/twrp2/98
They suggest I do the android app install method. I follow the first link (Market Link)
and install GooManager, and follow their steps.
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will reboot and install the recovery automatically.
This all goes smoothly, but here's my issue.
It doesn't reboot automatically, or install anything automatically.
I see in the comments a recommendation to reboot into recovery mode.
I choose that in GooManager's menu, and after rebooting I get my bootloader screen with 4 menu options:
Bootloader
Reboot
Reboot Bootloader
Power Down
The only one that sounds sensible to me is bootloader so I pick that.
Now I get some new options:
Fastboot
Recovery
Factory Reset
Clear Storage
Simlock
Image CRC
Show Barcode
So, the only one that makes sense is Recovery. I choose it. The phone reboots.
Now I'm back at the first menu. So I'm in a loop.
Nothing I do in this loop seems to install anything.
So I just rebooted the phone normally and I'm back to my OS.
Where to go from here?
Click to expand...
Click to collapse
Did you unlock your boot loader first? You don't need to be S-off to install a custom recovery. Unlock your bootloader at htcdev.com then install twrp.
Read here for more info:
http://forum.xda-developers.com/showthread.php?t=2420916
Also, I suggest learning how to use fastboot commands. Install twrp using fastboot.
Sent from my EVO using XDA Premium 4 mobile app
OK, so I'm semi-bricked but not panicking yet.
Here's where I'm at.
• Unlocked boot loader successfully
• Installed TWRP using fastboot.
• Followed instructions as closely as I could on moonshine.io to get S-OFF working.
Several times during the process I got "installing device driver software" in my win7 system tray.
Not sure if that's normal. But the drivers seemed to install fine. At first.
But then, during this part of the process:
Moonshining .................(1)
Windows prompted me that it was installing some drivers again, But it failed to install the MTP driver.
After ten tries with the "Moonshining" step, I got "ERROR: don't drink and moonshine!" or something like that.
So, it seems like I need to get this MTP driver going. First I tried solutions on the computer:
• Uninstalled all HTC software, unplugged phone, rebooted,
installed HTC Sync Manager (setup name setup_3.0.52.0_htc.exe), then uninstalled it...
because a tutorial said this would keep the drivers but remove the software. Still no luck on the MTP driver though.
• Found "Mass Storage Device" (my phone) under device manager, removed it, unplugged, rebooted, replugged.
• Plugged cord into back of PC, so I'm using USB 2.0 rather than USB 3.0.
• One suggestion said a certain registry section might have an upperfilter key that shouldn't be there.
But I don't have that upperfilter key so that's not the issue.
Some fixes require getting into my phone (one guy suggests turning off USB debugging)...
but I no longer have a working OS. I can get into my bootloader, I tried Factory Reset.
But after choosing this I go into TWRP and I have no TWRP backups that I can restore.
So my next guess is, I need to get a recovery ZIP (is that basically a ROM?) that TWRP can install.
If that's correct, what ZIP should I get? I was on Android 4.0.3 Sense 4.0, can I download jellybean with Sense 5.0,
and install it via TWRP?
That was my goal all along, but I'm determined to get S-OFF working, so if doing that means my phone gets wiped again,
I guess I just want whatever ROM/recovery/whatever that allows me to change this USB debugging setting,
and try other phone-related fixes to the MTP driver issue.
First of all, flash an ICS rom. I'm assuming that you are still using the same ICS firmware, and you will want to have your phone operational (to enable USB debugging). The link for MeanRom ICS still works. http://old.androidfilehost.com/main/EVO_3D_Developers/mikeyxda/LTEvo/MeanROM-ICS-v65-jewel-ltevo.zip
Ok....since you are on the old HBoot, I think that you need to use the older S-Off methods (LazyPanda or DirtyRacun), if I'm not mistaken. You can not download and flash Sense 5.0 through TWRP as of yet, because you need to be using the new firmware to do so. You may want to pay http://unlimited.io/jewel.htm a visit. Also, to use LazyPanda or DirtyRacun, you need to be using Ubuntu. Another option that you have is to use the regular RUU and update directly to Sense 5.0. You will be stock, unrooted, but you can easily use the latest S-Off method.
Lastly, for your rooting/S-Off needs, you can also use a handy-dandy toolkit from @WindyCityRockr that can handle everything that you need to do. I usually encourage manual labor, but there are some exceptions. http://forum.xda-developers.com/showthread.php?t=2436217
Thanks again for jumping in.
I'm getting somewhere, but still so many difficulties.
Fix one thing, break two more.
I finally have a new working rom, but almost against my will it ended up
being CyanogenMod.
The short version:
- unlocked bootloader, got TWRP going, finally got ADB working (don't think it's the right driver,
but whatever, ADB commands work fine), wiped everything... factory reset, Dalvik, external storage.
- Didn't wipe Internal storage, I wiped only /data/ per some post's recommendation.
- I used ADB PUSH to get a few possible roms onto /sdcard/
PJ75IMG_1.13.651.1.zip (failed with "unable to open zip")
(ROM)_Stock_Rooted_OTA_(3.16.651.3)V2.zip (failed with "unable to execute updater binary in zip")
cm-10.2.0-jewel.zip (cyanogenmod) - success!
So, the phone works. It appears to be at least based on android 4.3... and I'm guessing CM, which updates
frequently, has all those OTA updates bundled into it. Any downsides to CyanogenMod?
I could just proceed from here to reinstall my old apps etc.
I'm still not "S-OFF" which annoys me, but I read a post suggesting it's not really that necessary.
The way they put it is, s-off allows you to access partitions so they can be modded,
but nobody is developing anything interesting for those partitions. Like nobody's doing custom radios and such.
Should I still pursue S-OFF anyway?
If so, is there a way to do it with CyanogenMod?
That awesome app (Windroid Universal Toolkit) doesn't recognize the phone.
Last question, how should I go about restoring everything?
I had titanium and nandroid backups copied to my computer.
Can it restore to such a wildly different version of the OS?
Can I get back not just apps, but stuff like my keyboard preferences, texting history, etc.?
Should I still pursue S-OFF anyway?
Click to expand...
Click to collapse
Yes! Being S-On is a complete pain in the BUTT when switching AOSP roms. Have you tried to flash the rom that I posted, MeanRom ICS? I'm really trying to get you to stay on Sense, because S-Off and other different tools work so much better while using Sense. AOSP is better after S-Off. But that's up to you.
If so, is there a way to do it with CyanogenMod?
Click to expand...
Click to collapse
I am not sure. You can try if you have the time. I suggest making a nandroid of your CM rom, and try to flash a Sense ICS rom, not JB...yet.
That awesome app (Windroid Universal Toolkit) doesn't recognize the phone.
Click to expand...
Click to collapse
CM might be the issue here, as well as it might not.
Last question, how should I go about restoring everything?
I had titanium and nandroid backups copied to my computer.
Can it restore to such a wildly different version of the OS?
Click to expand...
Click to collapse
Yes, TB will still work. There are some apps that might cause the restoration process to freeze, so I suggest killing TB and skipping over the app that froze the process when you return.
Can I get back not just apps, but stuff like my keyboard preferences, texting history, etc.?
Click to expand...
Click to collapse
If your keyboard preferences was not backed up, then no. If you were using the stock Sense keyboard, then that is a no as well. As long as your texting history was backed up, it can be restored. Texts are not like apps...their data is typically stored in XML files which are readable through any version of Android (2.3+).
I'm still soliciting my help if you need it.
I'm for sure going to need it, so thanks very much for the ongoing support!
I got discouraged after all the failures but I'll download Meanrom now.
The thing is... now that Cyanogen mod works, I hesitate to wipe it and try a new one.
Especially since several other roms I tried mysteriously failed to install.
I like that it's jellybean and don't wanna move backwards to ICS.
And I like their goal of cutting out the fluff.
I still want S-OFF, will I end up having to wipe everything again to get it?
Also, I really don't feel confident I have the right drivers for my windows machine.
I can transfer files in USB mode, go into USB debugging, and do the usual ADB commands.
But the phone shows up as a nexus in device manager, but it's definitely evo 4G lte.
I tried installing an executable RUU and it failed after a bit saying it can't detect the device.
And there's that issue where Windroid doesn't detect it.
So I have the feeling that without the right USB drivers, tools like Moonshine will still fail.
I specifically got errors every time when anything tried to install MTP usb drivers. Do I really need them?
You think LazyPanda or DirtyRacun's tools will work even if I never get the MTP thing installed?
CreeDo said:
I'm for sure going to need it, so thanks very much for the ongoing support!
I got discouraged after all the failures but I'll download Meanrom now.
The thing is... now that Cyanogen mod works, I hesitate to wipe it and try a new one.
Especially since several other roms I tried mysteriously failed to install.
I like that it's jellybean and don't wanna move backwards to ICS.
And I like their goal of cutting out the fluff.
I still want S-OFF, will I end up having to wipe everything again to get it?
Also, I really don't feel confident I have the right drivers for my windows machine.
I can transfer files in USB mode, go into USB debugging, and do the usual ADB commands.
But the phone shows up as a nexus in device manager, but it's definitely evo 4G lte.
I tried installing an executable RUU and it failed after a bit saying it can't detect the device.
And there's that issue where Windroid doesn't detect it.
So I have the feeling that without the right USB drivers, tools like Moonshine will still fail.
I specifically got errors every time when anything tried to install MTP usb drivers. Do I really need them?
You think LazyPanda or DirtyRacun's tools will work even if I never get the MTP thing installed?
Click to expand...
Click to collapse
Feel free to try the facepalm S-off method as well. Works on devices with older software and is super easy. Look here:
http://forum.xda-developers.com/showthread.php?t=2163013
Sent from my Nexus 5 using XDA Premium 4 mobile app
Evolution_Freak said:
Feel free to try the facepalm S-off method as well. Works on devices with older software and is super easy. Look here:
http://forum.xda-developers.com/showthread.php?t=2163013
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Cheers, it does look pretty straightforward.
Of course that's what I thought hours ago when I tried moonshine haha.
I'll give it a go.
To be clear, does this method wipe anything?
They don't actually say.
CreeDo said:
Cheers, it does look pretty straightforward.
Of course that's what I thought hours ago when I tried moonshine haha.
I'll give it a go.
To be clear, does this method wipe anything?
They don't actually say.
Click to expand...
Click to collapse
Can't remember if it wipes or not. Best thing to do is make a backup with TWRP and keep the backup on your external SD card. If it wipes you can always restore your backup.
Sent from my HTC device
Thanks for the help so far guys. I am currently really enjoying Cyanogenmod. I suspect it's eating battery more,
but then against I am on the phone for hours redoing everything that got changed/removed.
Does anyone know if there's a simple way (or even a difficult way) to restore my texts?
Because the app is totally different, and the old text app was the one that came
with the stock rom, I cannot restore it in titanium. But if I could extract even the raw text that'd be helpful.
Get back to Sense, or get someone with Sense to restore it for you, and save it using a different app. Or maybe try using SMS Backup & Restore from the Play Store. I'm not sure if it can read the backups saved through Sense, but it's worth a try. You just have to navigate to the location of the old backup.
It looks like I can import an XML in this messaging app so maybe if sense offers an export to XML option, I'll be set.
Sense is sort of an OS on top of the OS, right?
Can sense be loaded without flashing a new rom? or is it too integrated with the OS?
Hi all,
I'm having trouble getting Safestrap to install and work properly on my VerizonSG4. Phone is rooted with stock ROM and still on 4.3 with updates and notifications blocked.(SDM frozen with TB) Other mods include Exposed Framework using 2 modules,Greenify, Busybox, and a couple other root dependent apps that are not likely to be the issue. The problem I'm having is that upon getting Safestrap to install (which took multiple attempts) it will open to the screen where you can choose to install or uninstall recovery and when I hit install it does its thing but shows "State: Not Installed". However, I DO get a little pop up at the bottom of the screen that says" Installation Complete". Safe System says " Not Active" and " Reboot to Recovery" is grayed out so that I can't select it. Manual reboot into recovery brings up stock recovery so I'm not sure what's going on. I've tried everything I can think of to make it work including defrosting SDM, disabling my antivirus, verifying that USB debugging is enabled, etc. So I'm frustrated and could use some insight. I'm obviously missing something or doing something wrong so any help would be greatly appreciated. Oh, and the apk that I downloaded was Safestrap-JFLTEVZW-3.71which is supposed to be the correct on for Verizon MK2.
Thanks in advance
markctco said:
Hi all,
I'm having trouble getting Safestrap to install and work properly on my VerizonSG4. Phone is rooted with stock ROM and still on 4.3 with updates and notifications blocked.(SDM frozen with TB) Other mods include Exposed Framework using 2 modules,Greenify, Busybox, and a couple other root dependent apps that are not likely to be the issue. The problem I'm having is that upon getting Safestrap to install (which took multiple attempts) it will open to the screen where you can choose to install or uninstall recovery and when I hit install it does its thing but shows "State: Not Installed". However, I DO get a little pop up at the bottom of the screen that says" Installation Complete". Safe System says " Not Active" and " Reboot to Recovery" is grayed out so that I can't select it. Manual reboot into recovery brings up stock recovery so I'm not sure what's going on. I've tried everything I can think of to make it work including defrosting SDM, disabling my antivirus, verifying that USB debugging is enabled, etc. So I'm frustrated and could use some insight. I'm obviously missing something or doing something wrong so any help would be greatly appreciated. Oh, and the apk that I downloaded was Safestrap-JFLTEVZW-3.71which is supposed to be the correct on for Verizon MK2.
Thanks in advance
Click to expand...
Click to collapse
After rooting your phone with presumably saferoot did you open up SuperSu and update it's binary?
Sounds like a Superuser problem. Either open up SuperSu and update binary the " normal" way or run saferoot again if that doesn't work and then update binary. Then you should be OK to install SafeStrap.
Sent from my SCH-I545 using Tapatalk
Solved it!
Mistertac said:
After rooting your phone with presumably saferoot did you open up SuperSu and update it's binary?
Sounds like a Superuser problem. Either open up SuperSu and update binary the " normal" way or run saferoot again if that doesn't work and then update binary. Then you should be OK to install SafeStrap.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Thanks for the response, and I actually figured it out last night. But you were on the right track. After trying a download from a different source the apk installed, opened up and showed that I wasn't rooted! Surprised me because the app itself needed super user rights itself so I knew I was rooted. Turns out I needed to have the paid/full version of SuperSU! Bought it and I now have Safestrap. I know I should probably always purchase the full versions of such high tech apps but damn it would have been nice if someone...anyone would have said that. I'm guessing there are other versions of SuperUser that may work differently right out of the box? IDK but I'm up and running and grateful that I didn't brick my phone. Been down that road before and know that it doesn't take much to mess things up.
Anyway, thanks to all that read and maybe this will help someone else
markctco said:
Thanks for the response, and I actually figured it out last night. But you were on the right track. After trying a download from a different source the apk installed, opened up and showed that I wasn't rooted! Surprised me because the app itself needed super user rights itself so I knew I was rooted. Turns out I needed to have the paid/full version of SuperSU! Bought it and I now have Safestrap. I know I should probably always purchase the full versions of such high tech apps but damn it would have been nice if someone...anyone would have said that. I'm guessing there are other versions of SuperUser that may work differently right out of the box? IDK but I'm up and running and grateful that I didn't brick my phone. Been down that road before and know that it doesn't take much to mess things up.
Anyway, thanks to all that read and maybe this will help someone else
Click to expand...
Click to collapse
I'm not sure why you had to get a paid version of su. I had the SU zip and installed it as part of the upgrade/downgrade method
sent by baja kitkat S4
Definitely shouldn't need the paid version but hey good to support Chainfire anyways.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Definitely shouldn't need the paid version but hey good to support Chainfire anyways.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yes, I found that odd also. When I switched to the other apk download it installed but said I did not have root, so I backed out one step and under the apk download that I selected was text in red that said "full version of SuperSu is required to complete this operation." So I paid for the full version, rebooted and everything worked fine from there. At that point the price was worth it, plus I typically use free versions of apps if I can get away with it so by supporting the Dev, as stated, perhaps I made a small deposit in the karma bank
Now I'm just trying to figure out if I need to do a factory reset before installing Hyperdrive. This is not my first ROM install but is under this format, so i want to take every precaution. Any suggestions? Leaning towards doing it except for concern about my phone downloading KitKat before I can reinstall TB and block it. Maybe I just need to be quick fingered. Again, open for suggestions.
Thanks in advance
markctco said:
Yes, I found that odd also. When I switched to the other apk download it installed but said I did not have root, so I backed out one step and under the apk download that I selected was text in red that said "full version of SuperSu is required to complete this operation." So I paid for the full version, rebooted and everything worked fine from there. At that point the price was worth it, plus I typically use free versions of apps if I can get away with it so by supporting the Dev, as stated, perhaps I made a small deposit in the karma bank
Now I'm just trying to figure out if I need to do a factory reset before installing Hyperdrive. This is not my first ROM install but is under this format, so i want to take every precaution. Any suggestions? Leaning towards doing it except for concern about my phone downloading KitKat before I can reinstall TB and block it. Maybe I just need to be quick fingered. Again, open for suggestions.
Thanks in advance
Click to expand...
Click to collapse
You should have plenty of time. I've flashed back to stock so many times and never had that update pop up before I could freeze SDM
I have an MDK phone so I'm not 100% up to speed on what you should do... @decaturbob has done it all and I'm sure would help send you down the right path
Sent from my SCH-I545 using Tapatalk
markctco said:
Yes, I found that odd also. When I switched to the other apk download it installed but said I did not have root, so I backed out one step and under the apk download that I selected was text in red that said "full version of SuperSu is required to complete this operation." So I paid for the full version, rebooted and everything worked fine from there. At that point the price was worth it, plus I typically use free versions of apps if I can get away with it so by supporting the Dev, as stated, perhaps I made a small deposit in the karma bank
Now I'm just trying to figure out if I need to do a factory reset before installing Hyperdrive. This is not my first ROM install but is under this format, so i want to take every precaution. Any suggestions? Leaning towards doing it except for concern about my phone downloading KitKat before I can reinstall TB and block it. Maybe I just need to be quick fingered. Again, open for suggestions.
Thanks in advance
Click to expand...
Click to collapse
the steps listed in surge's method are pretty easy and there is a video. Once you have rooted NC5 deox rom installed, then you can flash another rom right over the top as you would normally do. I installed Bajarom.
- roms go in stock slot
- be sure to flash SU update.zip (a step in safestrap right after you flash hyperdrive)
decaturbob said:
the steps listed in surge's method are pretty easy and there is a video. Once you have rooted NC5 deox rom installed, then you can flash another rom right over the top as you would normally do. I installed Bajarom.
- roms go in stock slot
- be sure to flash SU update.zip (a step in safestrap right after you flash hyperdrive)
Click to expand...
Click to collapse
Ok, thanks, but now I'm hung up again. But first of all let me say that there are numerous methods to be found online and I'm not familiar with surge's method, plus I'm not sure exactly how or when to flash the SU update .zip you mention. With that being said, after getting Safestrap to run I decided to flash a Hyperdrive ROM. Following several a combination of instructions and videos, I settled on Hyperdrive RLS12 as it claims to work with 4.3/MK2. But I've also seen that I need to flash the correct module, in this case JFLTEVZW-MK2-modules.zip file. There are conflicting instructions as to whether to flash both zips together or to flash the ROM and then the module just before rebooting. I've also read that I need to wipe cache etc. before rebooting.
Long story short, no matter what I try, I always get the same results...I see the Verizon Galaxy S4 logo followed by a black screen followed by a new boot audio? followed by over 30 minutes of black screen and a very hot battery. I have wiped rom slots between flashes, tried different ROM slots, just about everything I can think of besides the SU update. So perhaps someone can provide some detail on that step and some clarity on the other steps that vary from source to source.
I'm sure I'm doing something wrong but have gotten to a point where I'm just going to leave it alone for a while and use my stock ROM until I can get some help UGHHH
Thanks in advance
markctco said:
Ok, thanks, but now I'm hung up again. But first of all let me say that there are numerous methods to be found online and I'm not familiar with surge's method, plus I'm not sure exactly how or when to flash the SU update .zip you mention. With that being said, after getting Safestrap to run I decided to flash a Hyperdrive ROM. Following several a combination of instructions and videos, I settled on Hyperdrive RLS12 as it claims to work with 4.3/MK2. But I've also seen that I need to flash the correct module, in this case JFLTEVZW-MK2-modules.zip file. There are conflicting instructions as to whether to flash both zips together or to flash the ROM and then the module just before rebooting. I've also read that I need to wipe cache etc. before rebooting.
Long story short, no matter what I try, I always get the same results...I see the Verizon Galaxy S4 logo followed by a black screen followed by a new boot audio? followed by over 30 minutes of black screen and a very hot battery. I have wiped rom slots between flashes, tried different ROM slots, just about everything I can think of besides the SU update. So perhaps someone can provide some detail on that step and some clarity on the other steps that vary from source to source.
I'm sure I'm doing something wrong but have gotten to a point where I'm just going to leave it alone for a while and use my stock ROM until I can get some help UGHHH
Thanks in advance
Click to expand...
Click to collapse
have you looked at any youtube videos concerning S4 and safestrap?
decaturbob said:
have you looked at any youtube videos concerning S4 and safestrap?
Click to expand...
Click to collapse
Absolutely! But good news, phone is now booting! I tried flashing both zips together and it's working...at least I think it is. Displaying what I think is Google Play Edition boot image, 4 dots, yellow green red and blue zooming in and out. Not sure how long this is supposed to go on but I'm further along than previously. Any suggestions in case I end up in a boot loop or how long to wait to decide?
markctco said:
Absolutely! But good news, phone is now booting! I tried flashing both zips together and it's working...at least I think it is. Displaying what I think is Google Play Edition boot image, 4 dots, yellow green red and blue zooming in and out. Not sure how long this is supposed to go on but I'm further along than previously. Any suggestions in case I end up in a boot loop or how long to wait to decide?
Click to expand...
Click to collapse
Did you check the thread for compatibility of roms with ss?
sent by baja kitkat S4
decaturbob said:
Did you check the thread for compatibility of roms with ss?
sent by baja kitkat S4
Click to expand...
Click to collapse
Yup! As a matter of fact this is the video I watched that shows Hyperdrive RSL12 on the exact same phone as mine with 4.3 MK2 build.I think this is also the one that suggests flashing the module at the end. I've watched so many videos I can't remember which ones say what.
Am I missing something? I've made sure that I have USB debugging checked as well as unknown sources before flashing, I've tried flashing both zips at the same time and individually, even tried again without selecting any music players besides the Samsung one and not picking any audio mods when setting up the rom as per someones post on some blog somewhere. I've changed boot image, keyboards...I'm just about over this ROM. It can clearly be used with 4.3 but just not for me I quess? I've even considered backing up my stock rom and doing a factory reset on my phone and then starting from scratch. I'm just hoping I don't have to update to KitKat, which by the way is what Hyperdrive's website states you have to do, but this video contradicts that. UGHHH AGAIN!
http://www.youtube.com/watch?v=pA8cV3-r3oU
Wow, really? Nothing? No one? I thought this was where all the Android Root and Rom specialist hung out? Am I posting in the wrong thread or something? I cannot be the only one with this problem, can I?
markctco said:
Wow, really? Nothing? No one? I thought this was where all the Android Root and Rom specialist hung out? Am I posting in the wrong thread or something? I cannot be the only one with this problem, can I?
Click to expand...
Click to collapse
Alright since your trying Rls12 this should be easy since that's for Mk2.. Which your on.
Hop into SafeStrap and create a ROM slot. After its created activate that ROM slot. Then for good measure once your on that ROM slot wipe it.. Factory data reset. Then proceed to flash the Hyperdrive zip. Once that's finished don't leave SafeStrap until you'll flash those modules.
Then you can wipe cache and Dalvic again before rebooting.
If that's still not working for you I'm not sure where the problem lies. You're using SafeStrap v3.71 right?? Not version 3.72..
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Alright since your trying Rls12 this should be easy since that's for Mk2.. Which your on.
Hop into SafeStrap and create a ROM slot. After its created activate that ROM slot. Then for good measure once your on that ROM slot wipe it.. Factory data reset. Then proceed to flash the Hyperdrive zip. Once that's finished don't leave SafeStrap until you'll flash those modules.
Then you can wipe cache and Dalvic again before rebooting.
If that's still not working for you I'm not sure where the problem lies. You're using SafeStrap v3.71 right?? Not version 3.72..
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Thanks for responding! And yes I'm using that version of Safestrap and did everything you mentioned as per this video:
http://www.youtube.com/watch?v=l4F5UYDcQ5A
The only thing I can think of comes from something someone else mentioned about updating superuser binaries which made me realize that SuperSu, which is what I have doesn't appear to have that option. I checked the Play Store and there is the original Super User apk that I've used before to root other versions before all this bootloader crap started. I remember updating binaries in that version...I think. It may have been an option in CWM which I've also used. Could that be the issue? SuperSu acts just like Super User, asking for permissions and whatnot, but maybe Safestrap needs the other version. I think I'm going to uninstall or freeze (better idea) SuperSu and install the regular SuperUser. What gets me thought is that they are both developed by Chainfire, so I'm not sure what the difference would be. I do know that something is not right because I'm confident I'm doing everything as instructed.
HOT DAMN! I got it! It was a SuperSu issue, just took me a bit to figure out how to update binaries. It doesn't just have a button for that, had to uninstall and reinstall newest version.
Wow, what a trip that was! And I love the ROM.Gotta go and play now though
Thanks for everyones help and patience!
markctco said:
Hi all,
I'm having trouble getting Safestrap to install and work properly on my VerizonSG4. Phone is rooted with stock ROM and still on 4.3 with updates and notifications blocked.(SDM frozen with TB) Other mods include Exposed Framework using 2 modules,Greenify, Busybox, and a couple other root dependent apps that are not likely to be the issue. The problem I'm having is that upon getting Safestrap to install (which took multiple attempts) it will open to the screen where you can choose to install or uninstall recovery and when I hit install it does its thing but shows "State: Not Installed". However, I DO get a little pop up at the bottom of the screen that says" Installation Complete". Safe System says " Not Active" and " Reboot to Recovery" is grayed out so that I can't select it. Manual reboot into recovery brings up stock recovery so I'm not sure what's going on. I've tried everything I can think of to make it work including defrosting SDM, disabling my antivirus, verifying that USB debugging is enabled, etc. So I'm frustrated and could use some insight. I'm obviously missing something or doing something wrong so any help would be greatly appreciated. Oh, and the apk that I downloaded was Safestrap-JFLTEVZW-3.71which is supposed to be the correct on for Verizon MK2.
Thanks in advance
Click to expand...
Click to collapse
Edited
---------- Post added at 10:01 PM ---------- Previous post was at 09:57 PM ----------
Install Terminal Emulator. Type su and press enter. Then type setenforce 0 with a space after setenforce. Then press enter and reopen SafeStrap and all is well. The reboot recovery button will not be greyed out no more.
James- tech for a site dealing with Android day and night!
Hey guys! Unfortunately I bricked my new HTC Desire 626s while fiddling around with xposed for lollipop after successfully rooting the phone and installing cyanogen recovery. I think if I flash the stock rom on the phone through either adb or cyanogen recovery I can unbrick it, but I have been unsuccessful in finding this file on the internet. Would anyone care to give me a link or upload the stock firmware/rom of this phone? It would really help me out, thank you!
You have to make sure the firmware is the same version or newer than the one currently on the phone as well as which carrier or region the phone is from. Without that, can't provide the correct file to download.
es0tericcha0s said:
You have to make sure the firmware is the same version or newer than the one currently on the phone as well as which carrier or region the phone is from. Without that, can't provide the correct file to download.
Click to expand...
Click to collapse
Umm.. Okay so I guess I'll give you my phone's info? WAIT DOES THIS MEAN YOU CAN PROVIDE A DOWNLOAD!? IM SO EXCITED, UH OK HERE
- HTC Desire 626s
- Metro PCS USA
- Current firmware version : 1.06.1550.7
ANYTHING ELSE?? IF YOU CAN GIVE ME THAT DOWNLOAD LINK, MY MOM WONT KILL ME:crying::crying::crying: (she's really pissed :laugh Thank you btw!
Was just thinking about this...if you soft bricked after attempting to install Xposed, and nothing else, you should be able to get out of it by flashing the xposed uninstaller zip. If that does not work, stay tuned to this thread http://forum.xda-developers.com/desire-626/help/htc-desire-626s-root-recovery-t3169169 as there are some others at the end of the thread in a similar predicament. It does not appear that there is an official RUU yet for the Metro version, only the T-Mobile version, and they are not compatible. Just try the uninstaller zip first because that would be the easiest thing to try and should only take a couple of minutes.
es0tericcha0s said:
Was just thinking about this...if you soft bricked after attempting to install Xposed, and nothing else, you should be able to get out of it by flashing the xposed uninstaller zip. If that does not work, stay tuned to this thread http://forum.xda-developers.com/desire-626/help/htc-desire-626s-root-recovery-t3169169 as there are some others at the end of the thread in a similar predicament. It does not appear that there is an official RUU yet for the Metro version, only the T-Mobile version, and they are not compatible. Just try the uninstaller zip first because that would be the easiest thing to try and should only take a couple of minutes.
Click to expand...
Click to collapse
I tried this before my phone got ****ed and it worked:good:! If you can help me dude that'd be great. After uninstalling or changing some stuff in priv-app on my HTC Desire 626s, when I rebooted, it would just stay in a boot loop with the optimizing app message. Any ideas?
What did you uninstall? I would ask for those apps in that thread and use a flashable zip and install via TWRP. You might also try clearing caches and/or resetting the phone again. It DOES take a long time to optimize the apps after wiping stuff as well, so sometimes it is a matter of being patient.
This is why I ALWAYS recommend to freeze apps vs uninstalling. Uninstalling them does not get you any usable space back, so there is no benefit, but it can cause issues if you do need the apps, as you can see...
es0tericcha0s said:
What did you uninstall? I would ask for those apps in that thread and use a flashable zip and install via TWRP. You might also try clearing caches and/or resetting the phone again. It DOES take a long time to optimize the apps after wiping stuff as well, so sometimes it is a matter of being patient.
This is why I ALWAYS recommend to freeze apps vs uninstalling. Uninstalling them does not get you any usable space back, so there is no benefit, but it can cause issues if you do need the apps, as you can see...
Click to expand...
Click to collapse
I believe I uninstalled the dialer and its service in an attempt to replace them with the stock lollipop ones. How do you install TWRP on this phone? My mom has the same phone and its also rooted but hers actually works so I was thinking since TWRP has a nandroid backup setting, I could simply do a nandroid backup on hers and flash it on to mine to see if it will boot up. What do you think? And for the optimizing apps thing, it would finish optimizing, say starting apps, reboot and then optimize again and repeat. Thanks for the help btw, I really hope we can fix this.
You have to unlock the bootloader @ htcdev.com and use fastboot to install TWRP. And yes, that would work, as long as they are on the same software update. Know that when you unlock the bootloader, it will automatically wipe the phone, so make sure she has everything backed up to Google, the PC, etc.
es0tericcha0s said:
You have to unlock the bootloader @ htcdev.com and use fastboot to install TWRP. And yes, that would work, as long as they are on the same software update. Know that when you unlock the bootloader, it will automatically wipe the phone, so make sure she has everything backed up to Google, the PC, etc.
Click to expand...
Click to collapse
Do you have the TWRP recovery file for me to download?
I'm afraid I'm a bit confused... How did you install Xposed and the Uninstaller without a custom recovery? Upon further searching, there doesn't appear to be a version of TWRP for your phone that I could find. Just figured you already had one. You must be on Kit Kat and not Lollipop?
es0tericcha0s said:
I'm afraid I'm a bit confused... How did you install Xposed and the Uninstaller without a custom recovery? Upon further searching, there doesn't appear to be a version of TWRP for your phone that I could find. Just figured you already had one. You must be on Kit Kat and not Lollipop?
Click to expand...
Click to collapse
I installed Cyanogen recovery before flashing Xposed and the uninstaller. I thought you had the TWRP recovery img for my phone which is why I asked. I believe some developers are working on a Clockworkmod recovery for this phone which is basically the same thing as TWRP recovery, right? Anyways I guess I just have to wait until that comes out, but I was wondering if anyone who somehow got a hold of the stock rom could upload it for us to use. It would be really helpful
ClockWorkMod is the recovery that Cyanogen uses. That is able to perform nandroid backups as well.
You have to unlock the bootloader, then if you messed up your stock rom and you've updated it to something newer than what Samsung gives for a stock recoverable rom, you must first use the tmobile vers, let it fail, and then use metropcs vers.
If you messed up recovery or anything it will all go back to stock after flash.
Next just copy superuser zip file to phone, go to download mode and adb flash cyanogen recovery img. Then reboot to recovery, choose to flash update, and find the superuser. zip and flash it, voila.
https://www.mediafire.com/?8o6qtn7hlsec0zj,yqbbzb7divlcvvc
Kitkat, anyone?
Does anybody have a stock KitKat ROM for this device? I'd like to try to bypass the FRP, but am stuck on what must be either a marshmallow or lollipop ROM.
What carrier do you have?
I can send you a backup of the FRP.img for Marshmallow or for lollipop.
You can dd if= flash it to your device and you should be all good.
I am looking for any older roms for these devices too.
Seems like not too many people save the RUU and then HTC only releases the newest.
I got lollipop and marshmallow that's it.
But like i said we can fix the frp partition.
Issue is fixed
BigCountry907 said:
What carrier do you have?
I can send you a backup of the FRP.img for Marshmallow or for lollipop.
You can dd if= flash it to your device and you should be all good.
I am looking for any older roms for these devices too.
Seems like not too many people save the RUU and then HTC only releases the newest.
I got lollipop and marshmallow that's it.
But like i said we can fix the frp partition.
Click to expand...
Click to collapse
I ended up fixing it using some ADB commands as noted in the "Well, I may have found..." thread. It'll be nice to have this phone out of my life. The day I had to spend with it was two days too many.
Attached is a Magisk installer zip patched to work on Acclaim. I can only test that it does install properly; if someone that has the hardware could verify that it actually works, I'd be very grateful. Please be sure to not have another root zip installed, as it could effect the outcome. Thanks in advance to any takers.
fddm said:
Attached is a Magisk installer zip patched to work on Acclaim. I can only test that it does install properly; if someone that has the hardware could verify that it actually works, I'd be very grateful. Please be sure to not have another root zip installed, as it could effect the outcome. Thanks in advance to any takers.
Click to expand...
Click to collapse
So might this theoretically work on the Unlegacy AOSP ROMs? Do I need to go through first boot and then flash the zip or can I do all the flashing at once?
nmyshkin said:
So might this theoretically work on the Unlegacy AOSP ROMs? Do I need to go through first boot and then flash the zip or can I do all the flashing at once?
Click to expand...
Click to collapse
Yes, it should work and you don't need to go through first boot. I've had the best luck rebooting back into recovery after flashing the rom, then flashing Magisk.
fddm said:
Attached is a Magisk installer zip patched to work on Acclaim. I can only test that it does install properly; if someone that has the hardware could verify that it actually works, I'd be very grateful. Please be sure to not have another root zip installed, as it could effect the outcome. Thanks in advance to any takers.
Click to expand...
Click to collapse
Does this work on 16GB only or does this include 8GB version?
It should work on both, they run the same ROMs, only requirement is Lollipop+.
Edit: I'm making the assumption users know which ROMs accommodate the 512mb models. Obviously, the ROM needs to be functional for Magisk to work.
fddm said:
Yes, it should work and you don't need to go through first boot. I've had the best luck rebooting back into recovery after flashing the rom, then flashing Magisk.
Click to expand...
Click to collapse
OK, no joy here. After waiting for a couple of hours to download a ROM (!) I finally put it all together. The system hangs at the "N" screen, never getting to the Cyanoboot screen. I tried this on an 8 GB tablet because I didn't want to mess majorly with my 16 GB one, but as you say, the result should be the same
BTW, there were no error messages I detected as the Magisk zip installed.
If you can, these three things might help to catch the problem:
TWRP log from after flashing Magisk(advanced->copy log)
A TWRP backup of your boot partition after flashing Magisk
A link to the ROM you tested
fddm said:
If you can, these three things might help to catch the problem:
TWRP log from after flashing Magisk(advanced->copy log)
A TWRP backup of your boot partition after flashing Magisk
A link to the ROM you tested
Click to expand...
Click to collapse
Sure. I've attached the log and boot backup below (I just zipped the boot backup folder). This is the ROM: https://builds.unlegacy-android.org/aosp-7.1/acclaim/ua_acclaim-7.1.2-20180215-0240.zip
Let me know if there's anything else I can do.
nmyshkin said:
Sure. I've attached the log and boot backup below (I just zipped the boot backup folder). This is the ROM: https://builds.unlegacy-android.org/aosp-7.1/acclaim/ua_acclaim-7.1.2-20180215-0240.zip
Let me know if there's anything else I can do.
Click to expand...
Click to collapse
I repacked the fix with the latest to fix a crash I see. The main problem I see is "- Magisk patched image detected", it thinks it's already patched so it skips it. I got this error with while testing on Ovation with an old TWRP3 SD recovery, please try rebooting back into recovery after flashing the rom if you haven't already (basically reloading TWRP between flashing the rom and Magisk, you do have to flash your rom again to restore the boot image).
fddm said:
I repacked the fix with the latest to fix a crash I see. The main problem I see is "- Magisk patched image detected", it thinks it's already patched so it skips it. I got this error with while testing on Ovation with an old TWRP3 SD recovery, please try rebooting back into recovery after flashing the rom if you haven't already (basically reloading TWRP between flashing the rom and Magisk, you do have to flash your rom again to restore the boot image).
Click to expand...
Click to collapse
Same behavior. I've attached the stuff you asked for before. And I did recycle through TWRP each time as you had suggested.
Your right, sorry, after testing again I can reproduce this error. Going to have a closer look, see if I can correct it. Thank you!
Edit: problem found, fix incoming
nmyshkin said:
Same behavior. I've attached the stuff you asked for before. And I did recycle through TWRP each time as you had suggested.
Click to expand...
Click to collapse
Ok, I found and fixed the bug. I was trying to check for acclaim by cmdline header, where it needs to check the name header. Should work now, and it doesn't seem to need the reboot. Thank you again!
fddm said:
Ok, I found and fixed the bug. I was trying to check for acclaim by cmdline header, where it needs to check the name header. Should work now, and it doesn't seem to need the reboot. Thank you again!
Click to expand...
Click to collapse
OK, so I've got boot
But I did have to do the recycle of TWRP. The first time I tried it without and it threw out all kinds of red errors. Yipes!
Anyway, I now have questions as I'm no magiskan I read about Magisk before and even tried it on a similar ROM (to no avail, of course), but there are many things I don't fully understand.
1. It seems to want to update when I start Magisk Manager. Is that a good or bad idea, considering I'm working with a custom patch? Just say "no" or......?
2. I need to install an SU manager, yes? MM seems to indicate that it can't find any. Seems like I recall it was based on the phh su so can I just install the manager app for that? Is that what I need to effect "root" or do I already have it?
OK, scratch that second one. I just installed AdAway and it started up asking for root privleges which I was able to give it. But.....it keeps saying "copy failed" which would indicate to me that it does not have write access to where the hosts file is, so something's not "complete" about the root access?
nmyshkin said:
OK, so I've got boot
But I did have to do the recycle of TWRP. The first time I tried it without and it threw out all kinds of red errors. Yipes!
1. It seems to want to update when I start Magisk Manager. Is that a good or bad idea, considering I'm working with a custom patch? Just say "no" or......?
OK, scratch that second one. I just installed AdAway and it started up asking for root privleges which I was able to give it. But.....it keeps saying "copy failed" which would indicate to me that it does not have write access to where the hosts file is, so something's not "complete" about the root access?
Click to expand...
Click to collapse
Yes!
I'm thinking some partition fail is failing to mount after wiping to give the errors, using rm -f in TWRP settings might avoid it.
Yes you can download and install a Magisk Manager update if it asks, just not Magisk updates yet(has to say 'Manager').
With the root problem, I'd try rebooting or maybe clean installing and using AdAway on the first boot. Or try a Magisk module for it. Basically, just need to experiment to see how it behaves. If nothing helps, a logcat from adb might give an idea of what's going on.
Edit: Are you installing anything extra or taking extra steps apart from installing the ROM, Magisk, and AdAway? I'm trying to see if it is reproducible on Nook HD+ on equivalent firmware, but am having no luck so far.
fddm said:
Yes!
I'm thinking some partition fail is failing to mount after wiping to give the errors, using rm -f in TWRP settings might avoid it.
Yes you can download and install a Magisk Manager update if it asks, just not Magisk updates yet(has to say 'Manager').
With the root problem, I'd try rebooting or maybe clean installing and using AdAway on the first boot. Or try a Magisk module for it. Basically, just need to experiment to see how it behaves. If nothing helps, a logcat from adb might give an idea of what's going on.
Edit: Are you installing anything extra or taking extra steps apart from installing the ROM, Magisk, and AdAway? I'm trying to see if it is reproducible on Nook HD+ on equivalent firmware, but am having no luck so far.
Click to expand...
Click to collapse
Things are looking up I searched the AdAway issue and see there is a newer version that seems to solve the problem for people using Nougat ROMs (including someone running Magisk!). Worked like a charm. ES File Explorer seemed to have root access issues but I went into MM to see what the issue was and managed to manually turn on root access. Seems OK now.
As you say, part of this is getting used to it. I'm not seriously thinking this ROM is going to be good for the 8 GB tablet (for one thing I cannot tolerate the shutdown bug) but it's fun to see what's going on and try out this approach. Who knows? Someday there may be an Unlegacy AOSP 8.1 "mini-me" that will run (and maybe even shut down...) and I'll have the know-how to deal with it.
Thanks for your efforts. Sorry to have been a bit of a pain.
nmyshkin said:
Thanks for your efforts. Sorry to have been a bit of a pain.
Click to expand...
Click to collapse
No, you were perfect. You provided essential information and kept trying when you hit a wall, and we got working Magisk in the end. Couldn't be happier, thank you!