Related
Hi!
I've been using Androwook 2.0 for a while and love it. However, I'd like to try 2.1 and the BAKED ROMs. Based on feedback on the forum, I want to use the Team Win recovery (TWRP) as opposed to my currently installed Clockwork Recovery.
Problem is, I can't work out how to replace CWR with TWRP. I've downloaded GooManager and instructed it to install the TW recovery. It says it's done so but when I reboot to recovery it takes me back to CW.
So, question is: how can I replace Clockwork Recovery with TWRP on a TF201?
Many thanks in advance for your thoughts!
Regards,
mroshaw
mroshaw said:
Hi!
I've been using Androwook 2.0 for a while and love it. However, I'd like to try 2.1 and the BAKED ROMs. Based on feedback on the forum, I want to use the Team Win recovery (TWRP) as opposed to my currently installed Clockwork Recovery.
Problem is, I can't work out how to replace CWR with TWRP. I've downloaded GooManager and instructed it to install the TW recovery. It says it's done so but when I reboot to recovery it takes me back to CW.
So, question is: how can I replace Clockwork Recovery with TWRP on a TF201?
Many thanks in advance for your thoughts!
Regards,
mroshaw
Click to expand...
Click to collapse
you could use fastboot method: http://www.teamw.in/project/twrp2/93
also it is recommended to use AndroidRoot bootloader: http://forum.xda-developers.com/showthread.php?t=1774352
Thank you for the reply. I'm not that comfortable with that level of tweaking and I had really hoped that Goo Manager would sort me out. Is it a known issue that Goo Manager cannot install TWRP if another recovery is present?
If so, I'll give the fastboot method a go at the weekend.
You really shouldn't be flashing anything if you don't know what its actually doing on your device.
Danny80y said:
You really shouldn't be flashing anything if you don't know what its actually doing on your device.
Click to expand...
Click to collapse
I think most of us are unaware of exactly what is going on behind the scenes when you tell an app to update the recovery. The fact that he is searching for alternative methods to GooManager since it doesn't work seems rather valid. I flashed twrp via the fastboot method. I did not use the AndroidRoot bootloader.
Danny80y said:
You really shouldn't be flashing anything if you don't know what its actually doing on your device.
Click to expand...
Click to collapse
Yeah, not a particularly helpful response to be honest. If you don't know the answer to the question, probably best not to post a reply.
emptyshell said:
The fact that he is searching for alternative methods to GooManager since it doesn't work seems rather valid
Click to expand...
Click to collapse
Indeedy - thanks for that.
The Androwook flashing process felt really safe and gave a lot of less techy Prime users access to a ROM that transformed (excuse the pun) the TF201 into a usable device. I don't think a lack of a full understanding of the inner workings of the technology or process should stop people from using it or from asking questions. Otherwise, what's the point of the forum?
If anyone is able to answer the question as to why Goo Manager will not install TWRP on top of an existing CW recovery, I'd greatly appreciate it. :good:
emptyshell said:
I think most of us are unaware of exactly what is going on behind the scenes when you tell an app to update the recovery. The fact that he is searching for alternative methods to GooManager since it doesn't work seems rather valid. I flashed twrp via the fastboot method. I did not use the AndroidRoot bootloader.
Click to expand...
Click to collapse
I had problem with GooManager too, so I flashed TWRP manually via fastboot.
Be aware her if you want to use twrp backup/restore you'll probably need modified bootloader as stated above. Twrp uses .img backup format, not blob, and modified bootloader can handle them correctly, which is not the case of original one.
You could have a non functional restore process for /boot. One solution could be to reflash the ROM after the restore in that case, so if you don't want to modify the bootloader always keep the zip of the ROM that you backup.
Thanks all.
I'll go the manual route then, I think. Be as well to go the whole hog and do the modified boot loader too, by the sounds of things.
Thank you for your useful responses and input - much appreciated.
Couple of things to be aware of, firstly, fastboot method for installing twrp not too hard, read the instructions a couple times before you proceed. If you do run into problems, go back to the forum and ask, don't try to "fix" it with a method that hasn't been proven. Secondly, when you install twrp, you can forget you cwm backups, they are now worthless. That being said, make a back up in twrp at your earliest convinence.
Third, read the instructions, most are pretty clear but if you don't understand something ask before you start you can save yourself a lot of trouble.
Hey, first post here but I've been reading some threads since 2011.
I have a Samsung Galaxy S4 (I have experience with custom roms and such with the Droid Charge, also Samsung. See a pattern?).
I rooted it a while back, but recently have been experiencing quite a bit of instability so I wanted to try a custom rom (Hyperdrive is the one that I'm looking at but that's kinda irrelevant to this post).
The problem for me is that every guide expects me to be rooted with the custom recovery. I am rooted, and I did have CWM installed to perform the root, but now for some reason recovery boots into stock and I haven't been able to load any custom recoveries. I tried the CWM Rom Manager app to get CWM back, but it didn't seem to work (touch or normal). I have also tried Goo Manager to get TWRP and that was a complete bust.
I noticed one or two other methods involving safe-strap but I cannot for the life of me get safe-strap working on my phone and I've followed a couple guides several times without success.
I need someone to point me in the right direction to get a custom recovery back on my phone. I'm assuming something got screwed up somewhere along the line, so I'm not confident in these other methods but I'm trying to find a guide using Odin. Part of the problem seems to be that the Verizon phones aren't too common so all the guides and downloads are for a different model.
Please help, I'd prefer an Odin method but I'm open to suggestions.
cdroid93 said:
Hey, first post here but I've been reading some threads since 2011.
I have a Samsung Galaxy S4 (I have experience with custom roms and such with the Droid Charge, also Samsung. See a pattern?).
I rooted it a while back, but recently have been experiencing quite a bit of instability so I wanted to try a custom rom (Hyperdrive is the one that I'm looking at but that's kinda irrelevant to this post).
The problem for me is that every guide expects me to be rooted with the custom recovery. I am rooted, and I did have CWM installed to perform the root, but now for some reason recovery boots into stock and I haven't been able to load any custom recoveries. I tried the CWM Rom Manager app to get CWM back, but it didn't seem to work (touch or normal). I have also tried Goo Manager to get TWRP and that was a complete bust.
I noticed one or two other methods involving safe-strap but I cannot for the life of me get safe-strap working on my phone and I've followed a couple guides several times without success.
I need someone to point me in the right direction to get a custom recovery back on my phone. I'm assuming something got screwed up somewhere along the line, so I'm not confident in these other methods but I'm trying to find a guide using Odin. Part of the problem seems to be that the Verizon phones aren't too common so all the guides and downloads are for a different model.
Please help, I'd prefer an Odin method but I'm open to suggestions.
Click to expand...
Click to collapse
If you are on NC5 then Safestrap is your only option. You are going to brick your phone if you just keep throwing recoveries at your phone until one sticks. If you are on MDK then your bootloader is unlocked and you can do what you want. Read the threads, that's what they're there for.
Jesus loves you!
Phone version
liljoe727 said:
If you are on NC5 then Safestrap is your only option. You are going to brick your phone if you just keep throwing recoveries at your phone until one sticks. If you are on MDK then your bootloader is unlocked and you can do what you want. Read the threads, that's what they're there for.
Jesus loves you!
Click to expand...
Click to collapse
I'm actually on ME7. I haven't updated in a very long while because I wanted to root and then stop tinkering. That's not an option for me anymore for the stability reasons. I had over a year of rock solid performance though so it was a good run.
I was searching threads on this forum and others. This one seems to be more reliable than others (and a whole lot friendlier), but I still can't find what I'm looking for.
Maybe you can help me out by pointing out one of the threads that has what I need?
Thanks much.
cdroid93 said:
I'm actually on ME7. I haven't updated in a very long while because I wanted to root and then stop tinkering. That's not an option for me anymore for the stability reasons. I had over a year of rock solid performance though so it was a good run.
I was searching threads on this forum and others. This one seems to be more reliable than others (and a whole lot friendlier), but I still can't find what I'm looking for.
Maybe you can help me out by pointing out one of the threads that has what I need?
Thanks much.
Click to expand...
Click to collapse
MDK, as I understand it, is the only bootloader that has been unlocked thus far. If you are still on ME7 and it's locked anyway, you may be better off just taking the update.
Jesus loves you!
liljoe727 said:
MDK, as I understand it, is the only bootloader that has been unlocked thus far. If you are still on ME7 and it's locked anyway, you may be better off just taking the update.
Jesus loves you!
Click to expand...
Click to collapse
Okay, well obviously I've messed up my phone somehow, I don't think it's possible for me to just go to system settings and update. How do I go about this if that doesn't work?
cdroid93 said:
Okay, well obviously I've messed up my phone somehow, I don't think it's possible for me to just go to system settings and update. How do I go about this if that doesn't work?
Click to expand...
Click to collapse
Well you can update via Samsung Keis, or if you know how to use ODIN you can flash the latest NC5 through ODIN. You'll find everything you'll need from here.
Forgot to say that after you upgrade you can root through towelroot which you can by searching this forum or Google it.
After you install busybox you should be able to install Safestrap, but if you can't, you need to download and install an app calle SElinuxmodechanger and set SElinux to permissive. Then you will be able to install Safestrap. Once you have SS you can only install ROMs on the Stock slot. non of the other slots work.
skeezer308 said:
Well you can update via Samsung Keis, or if you know how to use ODIN you can flash the latest NC5 through ODIN. You'll find everything you'll need from here.
Forgot to say that after you upgrade you can root through towelroot which you can by searching this forum or Google it.
After you install busybox you should be able to install Safestrap, but if you can't, you need to download and install an app calle SElinuxmodechanger and set SElinux to permissive. Then you will be able to install Safestrap. Once you have SS you can only install ROMs on the Stock slot. non of the other slots work.
Click to expand...
Click to collapse
Okay, for starters thank you. This is almost exactly what I needed. I've just got one more issue;
I cannot discern from what I've found on the forums or elsewhere what safestrap is safe for my phone now that I'm on NC5?
Thanks again for this, was a big help.
cdroid93 said:
Okay, for starters thank you. This is almost exactly what I needed. I've just got one more issue;
I cannot discern from what I've found on the forums or elsewhere what safestrap is safe for my phone now that I'm on NC5?
Thanks again for this, was a big help.
Click to expand...
Click to collapse
3.72
Jesus loves you!
Also keep in mind that you can only install TW ROMs or GPE ROMs that are SS friendly. If you try to install Cyanogen or other AOSP ROMs that require custom kernels you run the chance of bricking your phone
Hi all,
Just want to help a bit with the CM12S. Flash the attached zip if you want root in apps and ADB.
I grabbed a debuggable boot.img from the official CM servers here:
Code:
http://builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS0YL-bacon/2263178b74/cm-12.0-YNG1TAS0YL-bacon-boot-debuggable.img
EDIT: New OTA [YNG1TAS17L]:
Code:
http://builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS17L-bacon/e816218e8a/cm-12.0-YNG1TAS17L-bacon-boot-debuggable.img
Then, I simply put them in a flashable zip format together with su binary from the latest CM12 nightly. I have tested it on my own phone and so far, there is no issue.
I have only tested it using TWRP, flash on your own risk.
Credits to @julian_klode:
https://forums.oneplus.net/threads/flashable-zip-enable-integrated-superuser.75511/
Note: I initially wasn't aware about the source of the base zip file that I used to pack the necessary files until julian_klode mentioned it in the Q&A thread.
There is no difference between this one and his, just the fact that I update mine manually. So, I think you should follow his thread instead.
Or just flash the SuperSu zip via recovery.
Sent from my A0001
Outstriped! I was thinking to make Debug kernel, but they released it sooner
Thank you so much. Puzzle and Dragons doesn't like Supersu, but works perfect with CM's superuser.
works fine here, thanks!
Vivek_Neel said:
Or just flash the SuperSu zip via recovery.
Sent from my A0001
Click to expand...
Click to collapse
Some people, like me, prefer CM's own root. Integration with Privacy Guard is pretty nifty, you know?
thank you , works perfectly!
inscythe said:
Some people, like me, prefer CM's own root. Integration with Privacy Guard is pretty nifty, you know?
Click to expand...
Click to collapse
thx:good:
Works great please keep this updated with each OTA if possible!
Vivek_Neel said:
Or just flash the SuperSu zip via recovery.
Sent from my A0001
Click to expand...
Click to collapse
That did not work for me
droidextra said:
That did not work for me
Click to expand...
Click to collapse
sorry for my noob question. but i actually flashed supersu. that wont affect anything. i am asking this cause yesterday i had to factory reset my device 4 times as it got stuck at cyanogen boot animation. It would boot fine couple of times and then get stuck.
srgudhka said:
sorry for my noob question. but i actually flashed supersu. that wont affect anything. i am asking this cause yesterday i had to factory reset my device 4 times as it got stuck at cyanogen boot animation. It would boot fine couple of times and then get stuck.
Click to expand...
Click to collapse
I have never tried SuperSU in my OPO Lollipop since I found out about the built-in root support, so I can't say what's wrong with it. Bootloops may be caused by stuck up boot process, which may be caused by kernel.
If I'm not wrong, I remember last time when Lollipop launched that SuperSU need to patch the kernel in a certain way for it to run properly. My solution also works with a different kernel, albeit it is provided officially by Cyanogen.
If you really want SuperSU for some reason, you can try flashing SuperSU and then flash the boot.img from the link above (or extract it from my zip). Latest TWRP will do it just fine.
inscythe said:
I have never tried SuperSU in my OPO Lollipop since I found out about the built-in root support, so I can't say what's wrong with it. Bootloops may be caused by stuck up boot process, which may be caused by kernel.
If I'm not wrong, I remember last time when Lollipop launched that SuperSU need to patch the kernel in a certain way for it to run properly. My solution also works with a different kernel, albeit it is provided officially by Cyanogen.
If you really want SuperSU for some reason, you can try flashing SuperSU and then flash the boot.img from the link above (or extract it from my zip). Latest TWRP will do it just fine.
Click to expand...
Click to collapse
SuperSU plus CM root don't play well together. Take a look through Caulk's stock 5.0.2 thread and you'll see several people having problems - manifested by flashing SuperSU and then trying to open Developer Options. It FCs. Just use the built-in CM root or disable CM root before you flash SuperSU.
All good here! I went into the Supersu settings and did a FULL UNINSTALL OF ROOT. Once that was done, I went into TWRP and flashed CM zip provided by OP... Bam. Done and no problems. Thank you, OP!
Wisiwyg said:
SuperSU plus CM root don't play well together. Take a look through Caulk's stock 5.0.2 thread and you'll see several people having problems - manifested by flashing SuperSU and then trying to open Developer Options. It FCs. Just use the built-in CM root or disable CM root before you flash SuperSU.
Click to expand...
Click to collapse
I perhaps wasn't very clear about my above suggestion.
What I meant is that, there is an official insecure boot.img (the kernel) which I linked above and included in my zip package. I'm not telling him to install both SuperSU and the built-in root.
SuperSU has some features that is not present in the built-in root though, like logging or tapjacking protection. Privacy Guard is pretty nifty, but I still miss the old interface of SuperSU.
inscythe said:
Hi all,
Just want to help a bit with the CM12S. Flash the attached zip if you want root in apps and ADB.
I grabbed a debuggable boot.img from the official CM servers here:
Code:
http://builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS0YL-bacon/2263178b74/cm-12.0-YNG1TAS0YL-bacon-boot-debuggable.img
Then, I simply put them in a flashable zip format together with su binary from the latest CM12 nightly. I have tested it on my own phone and so far, there is no issue.
I have only tested it using TWRP, flash on your own risk.
Click to expand...
Click to collapse
Is there any way to make this work with franco kernel r41? Thanks...
ten_tickles said:
Is there any way to make this work with franco kernel r41? Thanks...
Click to expand...
Click to collapse
I think it's the issue with Franco's own kernel... Even the nightly CM12 users with the built-in root enabled also had the root access disabled.
SuperSU works in this case because it relies on an init.d su-enabling service.
Just wait for Franco to fix it, since the CM11S versions works well with the built-in root. I am also a FK paid user, so this is a bad situation for me as well...
If you could update this asap to the YNG1TAS17L build that would be awesome thanks a lot for your hard work! Edit: nvm was able to make my own.
Link_of_Hyrule said:
If you could update this asap to the YNG1TAS17L build that would be awesome thanks a lot for your hard work! Edit: nvm was able to make my own.
Click to expand...
Click to collapse
Care to share it? I presume that the version in the OP won't work with the new v5.02 OTA?
I uploaded it here sorry it's not a better host but I'm on my phone ATM lol. http://uploadmirrors.com/download/R8ADOYOG/icial-12.0-signed-YNG1TAS17L-bacon-superuser.zip All I did was get the ota URL from here and changed the ending to cm-12.0-YNG1TAS17L-bacon-boot-debuggable.img I guess the system automatically makes the debug images when the ota rolls out. So I imagine the same thing would work for next ota. You just rename it to boot.img and replace the one in the zip from this thread and rename the zip and flash.
Link_of_Hyrule said:
If you could update this asap to the YNG1TAS17L build that would be awesome thanks a lot for your hard work! Edit: nvm was able to make my own.
Click to expand...
Click to collapse
Not that hard to make, right? But super practical to keep this if you often jumping ROMs.
SimonTS said:
Care to share it? I presume that the version in the OP won't work with the new v5.02 OTA?
Click to expand...
Click to collapse
Sorry, was doing overtime at work. I've updated the OP too.
Just updated from 4.3 to 5.1 so I can get CarbonROM, and can't seem to find how to root it now. Kingo worked fine when it was on 4.3 if I'm not mistaken (I've rooted 6 devices since then, so I may be misremembering, haha). Now, it's no longer supported. KingRoot and Towelroot have also failed. I've been googling and trying to find the answer, but all I'm getting are the above methods, for 4.3. If I've completely overlooked something and am asking a dumb question here, then please forgive me. I'd appreciate at least a web link in the right direction if that's the case, or if this is a valid question then I'd love if I could get a bit of a walkthrough with this. Currently, I'm running the stock ROM, unlocked bootloader, stock recovery... which was needed because I had to update
zombunny said:
Just updated from 4.3 to 5.1 so I can get CarbonROM, and can't seem to find how to root it now. Kingo worked fine when it was on 4.3 if I'm not mistaken (I've rooted 6 devices since then, so I may be misremembering, haha). Now, it's no longer supported. KingRoot and Towelroot have also failed. I've been googling and trying to find the answer, but all I'm getting are the above methods, for 4.3. If I've completely overlooked something and am asking a dumb question here, then please forgive me. I'd appreciate at least a web link in the right direction if that's the case, or if this is a valid question then I'd love if I could get a bit of a walkthrough with this. Currently, I'm running the stock ROM, unlocked bootloader, stock recovery... which was needed because I had to update
Click to expand...
Click to collapse
Carbon is already rooted. Enablee in developer options in settings. Just flash twrp and install carbon.
Moody66 said:
Carbon is already rooted. Enablee in developer options in settings. Just flash twrp and install carbon.
Click to expand...
Click to collapse
ah, nice!! thanks dude, I'm new to the custom ROM scene and didn't know that was even a possibility. I really appreciate the help!
And to benefit others who searched and reached this thread, beside build in root in CM, for all ROM, you can always install SuperSu.zip in twrp to gain root. The detail is in the INDEX page root section.
http://forum.xda-developers.com/showthread.php?p=61682514
xordos said:
And to benefit others who searched and reached this thread, beside build in root in CM, for all ROM, you can always install SuperSu.zip in twrp to gain root. The detail is in the INDEX page root section.
http://forum.xda-developers.com/showthread.php?p=61682514
Click to expand...
Click to collapse
Good idea.
Rooting 5.1 ham2
Download the mt2 l03 twrp image to your pc's adb folder on your hard drive
open command prompt from inside the adb folder. I believe its 'shift' and 'right click' mouse
then connect your device and run the fastboot twrp commands
twrp will root your ham 2
this all presumes that you've unlocked your bootloader
This post by @ArkAngel06 should be able to help it has Pretty much everything you need to install TWRP. It can be found at http://forum.xda-developers.com/showpost.php?p=61802299&postcount=2 . Just look for the link titled TWRP for Mate2. I would suggest downloading the newest version of TWRP that's compatible with the Carbon, Cyanogen and PAC if you wanted to install them later on, Just rename the file twrp like the one in the folder and replace the one in the folder with the one that you downloaded. The new TWRP can be found at http://android.cmphys.com/twrp-mt2/ . Then just follow the instructions in the folder to install TWRP and SuperSU .
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.