Related
UNLOCKED BOOTLOADER REQUIRED
Here it is: TWRP 2.6.3.0
I've tested backing up / restore, wiping, and installing an old backup (from ver. 2.6.0.0) and all seem to work. I also included the flag "HAVE_SELINUX := true" so it should be compatible with the newer 4.3 based ROMs (needs tested).
To install:
Download and unzip file ("img" was a few bytes over the 8mb forum limit)
Code:
fastboot flash recovery XT901-XT907-TWRP-2.6.3.0-recovery.img
BUGS: I have had the screen start very dim. Sometimes restarting the recovery would fix it, otherwise go to settings / screen, and set the timeout short so it goes out. Press power to turn on and it is at full brightness.
Enjoy!!
Thanks to:
TeamWin for TWRP.
Hashcode and Dhacker for STS-Dev Team source.
Djrbliss for unlocking the bootloader & providing root in the first place.
and mattlgroff
Thank you! Just tested it briefly and it works great. Glad the recovery is finally fixed to be able to use ADB. Was unable to use any TWRPs from 2.5.0.0+ as ADB was broken in the recovery.
CM 10.2 Build removed due to errors.
jbaumert said:
OP updated with link for TWRP compiled with CM10.2 sources
Click to expand...
Click to collapse
The recovery built with the 10.2 sources seems to have an issue with mounting the internal storage and sdcard, but the 1st one built is running perfect. I made a flashable zip of the 2.6.3.0 recovery for anyone who wants to simply flash it in recovery.
@mic213, Thanks for the sanity check. Any chance you have tried backup / restore of a 4.3 build?
Sent from my XT901 using Tapatalk 4
I was able to backup with it. Still hangs at reboot.
Sent from my XT907 using Tapatalk 4
netizenmt said:
Still hangs at reboot.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Do you mean when you reboot from TWRP? I noticed that on other builds, but didn't think much of it.
Recovery Tools is a free app on Google Play. Simply download the Recovery IMG. file from this post, and then open the Recovery Tools app. Grant it root, and now you can simply flash the img. file from the app without having to go into fastboot or compress the file into a flash able zip. Once recovery is flashed phone will reboot into whichever recovery is the most recently flashed. About as basic and straight forward as can be.
---------- Post added at 09:34 PM ---------- Previous post was at 09:22 PM ----------
The recovery file works great, only bug after about 4 days of use would be the dim menu screen in recovery. Still very readable even when bug pops up. Thanks for the great upload
Thanks. I could never get 4.3 to reboot past the initial boot after install, and now it finally does.
scottocs said:
Thanks. I could never get 4.3 to reboot past the initial boot after install, and now it finally does.
Edit....ehh maybe. Still working on it.
Click to expand...
Click to collapse
just make sure everything is wiped and that you are using 4.3 Gapps, also look up the SuperSU 1.65 update, some people have had trouble keeping root when rebooting into 4.3. Flash 4.3 ROM then GAPPS followed by SuperSU update, I would suggest running 4.3 on TWRP 2.5 or 2,6 first. Once your able to run 4.3 on one of those, then good ahead and try flashing 2.6.3. If anything on your phone is 4.2 and trying to load onto 4.3 it will never make it far past the boot screen.
Edited because I started rambling and couldn't delete.
Long story short, I have been having issues wiping, installing, and recovering.
I was flashing from a 4.3 ROM to another 4.3 ROM and decided it would be a good idea to wipe internal. Messed me up good.
I went back to 4.2 finally fixed booting issue on getting stuck at boot image. (Wasn't even making it to the boot animation.) I'll wipe everything except internal like I did before and go from 4.2 to 4.3. Last time I did this I didn't have issues.
motoroid7 said:
I'm not sure what I did, but some ROMs suggest that you wipe internal memory. I did this but now I have the issue after installing a ROM and booting it up... playing with it, if I then go to reboot the phone at all I just get stuck on my boot image (not the animation.) This happens on regardless of what ROM I've installed.
I also now can't go back to my backups. They fail on restoring. [Most recent backup was made on 2.5.0.0, previous to that 2.3.2.3]
How do I fix my phone? I'm wondering if I need to fxz back to a rooted stock ROM to fix what's going on?
Click to expand...
Click to collapse
This happened to me on TWRP too. When I went to restore, it say that it failed. However, I decided to boot into system anyway. TWRP gave me a warning that no OS was installed but I went ahead and rebooted. It booted into my backed up ROM just fine but it needed to be set up, like I just had flashed it. Basically, the restore process restored everything but my data. I did a barebones set up then booted back into recovery and went to restore the same exact ROM. This time, I got my complete ROM, just as I had saved it. This is kind of a long process, but it's better than having to FXZ or using a utility to go back to stock.
RikRong said:
This happened to me on TWRP too. When I went to restore, it say that it failed. However, I decided to boot into system anyway. TWRP gave me a warning that no OS was installed but I went ahead and rebooted. It booted into my backed up ROM just fine but it needed to be set up, like I just had flashed it. Basically, the restore process restored everything but my data. I did a barebones set up then booted back into recovery and went to restore the same exact ROM. This time, I got my complete ROM, just as I had saved it. This is kind of a long process, but it's better than having to FXZ or using a utility to go back to stock.
Click to expand...
Click to collapse
It's too bad I can't seem to locate the delete button on these posts, I'll go ahead and edit it. I was finally able to flash LiquidSmooth v2.9 (Android 4.2). It finally booted up, I just went back in and flashed gapps. It restarted fine. The real test is going to see if I go to hit a regular reboot and it boots up normally again. If that's the case I'm fixed. I would like to flash back to SlimROM that I had, but it seems that's going to probably be difficult without it messing up again. Not sure what to do if it does again. I won't be wiping internal memory anymore. I didn't have issues going from 4.2 to 4.3 when I didn't do it.
Any idea why I get a funky e:error: unknown media 'datamedia' error all the time in TWRP? I've had that error since like v2.3.x.x
motoroid7 said:
It's too bad I can't seem to locate the delete button on these posts, I'll go ahead and edit it. I was finally able to flash LiquidSmooth v2.9 (Android 4.2). It finally booted up, I just went back in and flashed gapps. It restarted fine. The real test is going to see if I go to hit a regular reboot and it boots up normally again. If that's the case I'm fixed. I would like to flash back to SlimROM that I had, but it seems that's going to probably be difficult without it messing up again. Not sure what to do if it does again. I won't be wiping internal memory anymore. I didn't have issues going from 4.2 to 4.3 when I didn't do it.
Any idea why I get a funky e:error: unknown media 'datamedia' error all the time in TWRP? I've had that error since like v2.3.x.x
Click to expand...
Click to collapse
Not 100% sure, but i believe that when you wiped your internal memory on 4.3 you deleted the ROOT. SuperSU seems to be having issues with
carrying over root on 4.3 to some peoples devices, Ive had to flash SuperSU update 1.65 from recovery otherwise when ROM boots up I get stuck in a cycle of SU Binary update/reboot. Also make sure that in Developer Options in your custom ROM, that Root Access is set to APPS and ADB and the same in SuperSU - APPS/ADB. Now to clarify I may be merging two unrelated issues together. If so, my bad lol.. But from my experience running PaCMan 4.3 since August, and now running TWRPS 2.6.3 since OP , 4.3 ROOT will not revert back to 4.2 unless Recovery is included in the backup. One final suggestion, try flashing the boot.img from 4.2 before flashing your 4.2 restore. I was able to revert back to 4.1 restores when I upgraded to 4.2 but while running 4.2 I deleted the Root Data from Internal Storage, I strongly suggest looking up arrrghhhs Sept. 15th Kernal for XT 926 which runs the same for XT 907. It damn near all the way current with CM 10.2 merges, should make running which ever 4.3 ROM you want much easier. If you want to run a 4.2 Rom , look up arrrghhhs 10.1 kernal version.
Arrrghhhs xt926/907 kernal
Kyles1329 said:
Not 100% sure, but i believe that when you wiped your internal memory on 4.3 you deleted the ROOT. SuperSU seems to be having issues with
carrying over root on 4.3 to some peoples devices, Ive had to flash SuperSU update 1.65 from recovery otherwise when ROM boots up I get stuck in a cycle of SU Binary update/reboot. Also make sure that in Developer Options in your custom ROM, that Root Access is set to APPS and ADB and the same in SuperSU - APPS/ADB. Now to clarify I may be merging two unrelated issues together. If so, my bad lol.. But from my experience running PaCMan 4.3 since August, and now running TWRPS 2.6.3 since OP , 4.3 ROOT will not revert back to 4.2 unless Recovery is included in the backup. One final suggestion, try flashing the boot.img from 4.2 before flashing your 4.2 restore. I was able to revert back to 4.1 restores when I upgraded to 4.2 but while running 4.2 I deleted the Root Data from Internal Storage, I strongly suggest looking up arrrghhhs Sept. 15th Kernal for XT 926 which runs the same for XT 907. It damn near all the way current with CM 10.2 merges, should make running which ever 4.3 ROM you want much easier. If you want to run a 4.2 Rom , look up arrrghhhs 10.1 kernal version.
Arrrghhhs xt926/907 kernal
Click to expand...
Click to collapse
To piggy back on general advice: I found I was having all sorts of problems going from 4.2 to 4.3. What finally did the trick was I wiped Dalvik, System, Cache AND I formatted data. The formatting was what did the trick.
When you wipe in twrp 2.5+ the recovery does not delete data/cache from internal (system) unless user mounts system prior to wipe. Wiping system cache, data, and dalvik cache is a full system wipe. Recommended if switching ROM rather than flashing nightly. This way no files from a AOKP ROM stick around and try to associate with your new CM based ROM.
Sent from my XT907 using Tapatalk 2
Thanks for the advice guys.
I was finally able to successfully getting my phone to work again last night (very early in the AM). It's very strange. I actually had 0 issues going from LiquidSmooth v2.9 to LiquidSmooth v3.0 (4.2 to 4.3). Though it was from the same dev could be part of it. It wasn't until I tried flashing from SlimROM/4.3 to CM10.2 nightly (where I wiped internal memory requiring me to type "yes".) Another thing is strange is even though it was saying I lost root in TWRP, I'm not sure that I ever did, unless TWRP just re-installed it when I reboot recovery automatically... because I finally told it no when asked if I wanted to re-install root? Then I was finally able to get LiquidSmooth v2.9 bootable and stable.
Again, thanks for all the help guys. I just wish I had a little bit understanding what I all did to finally get it to boot up. It was pretty early in the morning... going on 5/6AM. So I was pretty tired doing all of this. I just knew I couldn't let my phone not be up and running by morning.
I did a backup last night, flashed a 4.3 ROM which had reboot issues, and then restored with this version. I had zero issues, unlike when I was trying to restore with the previous version. Thank-you for your work.
It works with the xt902 too. Thanks!
What's the difference between the link in the first post and the one in the fourth? One of the is broken? Which one has been built with the CM10.2 sources?
I'm using a CM10.2 ROM... Which one should I peek?
Thanks!
So I've rooted my Z3c using dual recovery method, and later on flashed the Rectify mod, and everything seemed to be working well until I wanted to flash a file in recovery (I know I had CWM working at one point) but it is not working. I found the little NDR tool in the Rectify mod and tired the various recovery options (previously I would just use up on volume key). Well this is when I started noticing it not working and so I tried the manual volume key approach and still it is not working. I installed busy box and have found that can sometimes cause problems with NDR/Recovery however I attempted to uninstall was going to try different location but that's broken now too... I think.
So anyway, my problem is, if I re-install DualRecovery it still does not go to recovery.
Please help me get to Recovery mode so I can reflash rom.
Thank You
Have you installed a different busybox, most others aren't compatible with XZDR and will cause this kind of issue.
I'll tell you what I did, I downgraded firmware using flashtool, followed the dualboot method to upgrade while re-rooting and confirming recovery along the way (this seems to work) then as soon as I install rectify (making sure to flash dualboot flashable zip file before reboot) I'm no longer able to access recovery, not manually or using NDR. I also didn't intall busybox yet.
Oh boy what now, I'm back to square one.
I'm an idiot, what's the rectify mod? Point me to a download link and I'll see if there's something in it that's causing issues with XZDR.
Edit : I see its rectify rom. Well it most likely includes it's own version of busybox, hence the issue.
Hello Everyone!
I am new, my name is rohan and I have my eyes on the Xposed framework. I wanted to download some cool apps but i realized i needed Xposed framework. I own a Samsung Galaxy S5, Android 5.0, It has an ARM32 chip or something like that and i am a huge fan of Xposed now. So i didn't realize until now...I download TWRP, created a recovery and then i downloaded the .zip file for Xposed's framework to be installed. I was using TWRP and flashed the file via recovery but then my phone was starting, remained on the "samsung" (the blue dots like some fireworks) and never went beyond it. Could i get some help on this? Is this the BootLoop?...
Also, I don't know how to recover my phone too, it was also a rooted phone -- i forgot to do a backup for it...So any chances my phone will work again? Currently i have an S6 Edge - SM-G925F. But no plans to root the big boy yet.
Rohan114757 said:
Hello Everyone!
I am new, my name is rohan and I have my eyes on the Xposed framework. I wanted to download some cool apps but i realized i needed Xposed framework. I own a Samsung Galaxy S5, Android 5.0, It has an ARM32 chip or something like that and i am a huge fan of Xposed now. So i didn't realize until now...I download TWRP, created a recovery and then i downloaded the .zip file for Xposed's framework to be installed. I was using TWRP and flashed the file via recovery but then my phone was starting, remained on the "samsung" (the blue dots like some fireworks) and never went beyond it. Could i get some help on this? Is this the BootLoop?...
Also, I don't know how to recover my phone too, it was also a rooted phone -- i forgot to do a backup for it...So any chances my phone will work again? Currently i have an S6 Edge - SM-G925F. But no plans to root the big boy yet.
Click to expand...
Click to collapse
First of all: facepalm. A backup is mandatory if you flash any file through recovery. Always, no excuses.
Concerning your problem: you are encountering a bootloop... maybe. How long did you wait until you decide to abort the boot process? The first boot after flashing takes some time. If you have waited more than ten minutes, download the uninstaller.zip from the Xposed thread and place it on your SD card. Boot into recovery via key combo (use Google to find out about this). Then flash the uninstaller.zip and wipe cache&dalvik. Reboot and you might have your phone back running.
Another hint: after flashing the Xposed framework, it is recommended to wipe cache&dalvik.
orville87 said:
First of all: facepalm. A backup is mandatory if you flash any file through recovery. Always, no excuses.
Concerning your problem: you are encountering a bootloop... maybe. How long did you wait until you decide to abort the boot process? The first boot after flashing takes some time. If you have waited more than ten minutes, download the uninstaller.zip from the Xposed thread and place it on your SD card. Boot into recovery via key combo (use Google to find out about this). Then flash the uninstaller.zip and wipe cache&dalvik. Reboot and you might have your phone back running.
Another hint: after flashing the Xposed framework, it is recommended to wipe cache&dalvik.
Click to expand...
Click to collapse
Maybe i clearly did not explain it, after the flash success from TWRP 2.8.70 i used the re-boot option and then it got boot-looped from there i suppose. And you recovery mode, the recovery mode is still the odin download recovery mode, i ended up restoring the 4.4.2 firmware for now on my S5.
Plus, the issue is fixed - mod lockdown requested.
Closed at OP's request.
Before MM I was already having issues with my LP install. Lockups, crashes, etc.. I had planned on performing a fresh install of my LP ROM yesterday but was excited to see that MM was released. I was hoping that installing MM over LP would fix the issue that I was experiencing. No dice.
So, is it possible to go into TWRP, perform a factory reset (including erasing Internal Storage) and then booting into Download Mode so I can install MM fresh using Odin? Is there anything that I need to know of or missing before performing this procedure? I can then reinstall TWRP and root afterwards. I just want a fresh install and can't wait two or three days for a Flashable Zip. My system is just too unstable in its current form.
Thanks.
JC
For The Record
This is exactly what I just did. It works perfectly and now my phone is back to operating normally. And with a clean install of 6.0.1 to boot!
Now....time for TWRP and Root........
What is safe to wipe in TWRP? I did an install of MM for the 910T stock rom and unfortunately tried the encryption. I thought it would give me the option to decrypt, but that is not the case.
Wipe
Mister_E105 said:
What is safe to wipe in TWRP? I did an install of MM for the 910T stock rom and unfortunately tried the encryption. I thought it would give me the option to decrypt, but that is not the case.
Click to expand...
Click to collapse
I wiped EVERYTHING in TWRP. Powered off the phone and then booted to Download Mode. From there I pushed out a fresh copy of MM using Odin. It flashes a new stock recovery. After the phone boots up go back into Download Mode and flash TWRP using Odin. Then you can flash Beta SuperSU in TWRP for root.
But.....I wanted to follow up on this post. My Note 4 started experiencing issues last week. I was hoping a fresh OS install would fix things. Unfortunately for me during a power off to go into recovery to flash SuperSU I received the dreaded mmc_read failed error. The phone is nearly two years old and I have never seen the bug on my device. I had thought that I was one of the lucky early purchasers. I was wrong.
The device got worse and worse. To the point that now it rarely boots at all. It just sits at the "Samsung Note 4" screen. I can't even get into TWRP reliably. And the mmc screen is popping up more frequently now as well.
I had no choice but to stop by T-Mobile yesterday and (reluctantly) buy a S7 Edge. I say reluctantly for two reasons. 1. The Note 7 comes out in barely over a month 2. There is no known root for S7 (and Note 7 will probably be the same)
I have 30 days to decide if this phone is for me or not. Not having root is something that I never thought I'd have to live with. Barring some unforeseen circumstance I thought I'd have the Note 4 for a couple more years. And I didn't have the time to look for a used one as I needed a phone immediately.
Fingers crossed they get this thing roooted because it really is a pretty sexy device!
I found that the only way to clear the encryption was to load the stock recovery, it had the power to wipe the partitions and allow a clean install.
This has probably been said 1000 times before, but, I'm an idiot.
Now that we got that out of the way, perhaps you fine folks will help a dummy out?
About a year ago, I followed this guide and was successful in all that it deals with (unlocking bootloader, root, installing custom recovery and flashing custom rom).
My phone started acting a little buggy lately, (probably because I had less than 5 gb of space left? ) so I decided I wanted to just wipe everything and start "fresh".
I went into TWRP, wiped EVERYTHING, (wipe/advanced wipe/checked everything (dalvick,system,data,internal,cache) rebooted into recovery, sideloaded the newest Pure Nexus ROM and GApps zips, flashed both. After flashing new ROM, tried to reboot system, a message appeared saying it appears I do not have supersu installed, would I like to install it now? or something to that effect.
I wiped for"yes", phone turned off, then was stuck on the animation screen (swirling/color dot things) when tying to boot up.
Hold power button down till shut off, then restarted in recovery, wiped EVERYTHING (again), re-flashed the ROM, only this time said "no" to the supersu install screen.
Phone loaded up and is running perfectly.
However, I am no longer rooted???
I wasn't aware wiping everything in TWRP would remove root.
I'm confused because as I already said, I'm a dummy!, but when following the guide, I should root, then install a custom recovery.
My question is, do I only need to concern myself with the one step for rooting with CF-Root
since I already have a recovery installed, or am I going to need to re-install TWRP after rooting and then re-flashing the ROM and GApps?
I'm sure you folks are probably sick and tired of fools like me who just blindly follow along with XDA's [HOW TO] threads without knowing what or why we are doing what we are doing, but I appreciate you all just the same!
Any advice is appreciated!
Thanks in advance.
totallybeachin said:
This has probably been said 1000 times before, but, I'm an idiot.
Now that we got that out of the way, perhaps you fine folks will help a dummy out?
About a year ago, I followed this guide and was successful in all that it deals with (unlocking bootloader, root, installing custom recovery and flashing custom rom).
My phone started acting a little buggy lately, (probably because I had less than 5 gb of space left? ) so I decided I wanted to just wipe everything and start "fresh".
I went into TWRP, wiped EVERYTHING, (wipe/advanced wipe/checked everything (dalvick,system,data,internal,cache) rebooted into recovery, sideloaded the newest Pure Nexus ROM and GApps zips, flashed both. After flashing new ROM, tried to reboot system, a message appeared saying it appears I do not have supersu installed, would I like to install it now? or something to that effect.
I wiped for"yes", phone turned off, then was stuck on the animation screen (swirling/color dot things) when tying to boot up.
Hold power button down till shut off, then restarted in recovery, wiped EVERYTHING (again), re-flashed the ROM, only this time said "no" to the supersu install screen.
Phone loaded up and is running perfectly.
However, I am no longer rooted???
I wasn't aware wiping everything in TWRP would remove root.
I'm confused because as I already said, I'm a dummy!, but when following the guide, I should root, then install a custom recovery.
My question is, do I only need to concern myself with the one step for rooting with CF-Root
since I already have a recovery installed, or am I going to need to re-install TWRP after rooting and then re-flashing the ROM and GApps?
I'm sure you folks are probably sick and tired of fools like me who just blindly follow along with XDA's [HOW TO] threads without knowing what or why we are doing what we are doing, but I appreciate you all just the same!
Any advice is appreciated!
Thanks in advance.
Click to expand...
Click to collapse
Boot back into TWRP and reflash SU
totallybeachin said:
... re-flashed the ROM, only this time said "no" to the supersu install screen......
Click to expand...
Click to collapse
That's correct. No in twrp - is needed when there is already a SU in the flashed rom.
Probably you have not the most recent version of twrp.
In play store there are apps to check if you have root acces.
You can also go to the launcher and start the superSU app
kwdan said:
Boot back into TWRP and reflash SU
Click to expand...
Click to collapse
It always seems to be the most simple thing!
I'm not generally a stupid person, but this stuff can sure make a girl blush!
Thank you.
Worked like a charm.
Falling in love all over again with my Nexus 6.
.....makes note for NEXT TIME I have been eating dummie bears!
As NLBeev said, you are probably using an outdated version of TWRP. It doesn't ask about su any longer.