Hi
(pleas) can someone explain
how to migrate from Safestrap 1.8x to Safestrap 2.01.....
What's the difference between 2.00 and 2.01? Battery thing? I missed it
To go from 1.8x, you'll need to be in a non-safe system ROM with the stock GB kernel (I have MavROM installed). While in non-safe system ROM, disable safe system, remove recovery, and uninstall 1.8x Safestrap, and then install 2.01 Safestrap. Then install recovery and then if needed enable safe system. It depends on how you have your phone set up. I dual boot so I have MavROM as non-safe system, and have safe system for whatever else. PLEASE CORRECT ME IF I'M WRONG.
DoubleYouPee said:
What's the difference between 2.00 and 2.01? Battery thing? I missed it
Click to expand...
Click to collapse
This was Hash's explanation:
Hashcode said:
You bring up a good point.
I made a very important change in Safestrap, that I may need to undo.
Many users were experiencing low battery and then unable to get to charge mode. And this was causing a sort of "stuck" behavior.
I made this latest Safestrap bypass the 2nd rom if booted while plugged into ac power. This should allow for charge mode under any circumstance.
The downside is that if you reboot while plugged in, your going to bypass the 2nd rom. I'll come up with a better option for the future which avoids the confusion.
Sent from my XT894 using Tapatalk 2
Click to expand...
Click to collapse
So if some users were plugged into AC while booting, they might not be able to enter charge mode. So if a user say got into a bootloop, or some such issue, their battery would drain. My guess is that it was just to get faster boot times.
So did he undo it and that's 2.01 or what?
DoubleYouPee said:
So did he undo it and that's 2.01 or what?
Click to expand...
Click to collapse
not yet
ovelayer said:
not yet
Click to expand...
Click to collapse
So whats changed?
pm2gonzales said:
To go from 1.8x, you'll need to be in a non-safe system ROM with the stock GB kernel (I have MavROM installed). While in non-safe system ROM, disable safe system, remove recovery, and uninstall 1.8x Safestrap, and then install 2.01 Safestrap. Then install recovery and then if needed enable safe system. It depends on how you have your phone set up. I dual boot so I have MavROM as non-safe system, and have safe system for whatever else. PLEASE CORRECT ME IF I'M WRONG.
So if some users were plugged into AC while booting, they might not be able to enter charge mode. So if a user say got into a bootloop, or some such issue, their battery would drain. My guess is that it was just to get faster boot times.
Click to expand...
Click to collapse
I dont understand your first response. You toggle to the safe system to install the 2.0 safestrap, so it shouldnt matter what rom you have installed on the non safe system. I would like more detail on the correct way to upgrade from 1.8 to 2.0.
As far as the 2.01 battery upgrade, you got it wrong i believe. When I read hash's response, it sounds to me like he made version 2.01 ALWAYS boot the SAFE system rom (stock rom/kernel) when the phone is plugged into a charger. I'm guessing that while people are playing around with kexec that it has charging issues and if the phone goes dead, there is no way to get it to charge again. So to avoid being "stuck", you just plug it in and it boots the stock rom/kernel and starts charging. This would avoid you needing to access recovery manually and switch modes.
insanespain said:
I dont understand your first response. You toggle to the safe system to install the 2.0 safestrap, so it shouldnt matter what rom you have installed on the non safe system. I would like more detail on the correct way to upgrade from 1.8 to 2.0.
As far as the 2.01 battery upgrade, you got it wrong i believe. When I read hash's response, it sounds to me like he made version 2.01 ALWAYS boot the SAFE system rom (stock rom/kernel) when the phone is plugged into a charger. I'm guessing that while people are playing around with kexec that it has charging issues and if the phone goes dead, there is no way to get it to charge again. So to avoid being "stuck", you just plug it in and it boots the stock rom/kernel and starts charging. This would avoid you needing to access recovery manually and switch modes.
Click to expand...
Click to collapse
Safe mode is your non stock rom. Non safe is the stock. And yes his directions are correct. Boot to non safe(stock), uninstall old recovery and apk, then install new one.
When I did it I did not even remove the recovery, just installed the new apk and when I launched it, it said I had an old recovery, just installed the new right over it.
Edit: you are correct in saying it doesn't matter which rom you have installed in non safe, but since safestrap doesn't allow flashing the non safe side, most ppl leave it stock, since it's much more work to flash something onto it.
Sent from my XT860 using xda premium
I just upgraded to 2.01 from my safe system (non-stock) without issue. It doesn't seem to matter where you install from
Sent from my DROID3 using xda app-developers app
insanespain said:
I dont understand your first response. You toggle to the safe system to install the 2.0 safestrap, so it shouldnt matter what rom you have installed on the non safe system. I would like more detail on the correct way to upgrade from 1.8 to 2.0.
As far as the 2.01 battery upgrade, you got it wrong i believe. When I read hash's response, it sounds to me like he made version 2.01 ALWAYS boot the SAFE system rom (stock rom/kernel) when the phone is plugged into a charger. I'm guessing that while people are playing around with kexec that it has charging issues and if the phone goes dead, there is no way to get it to charge again. So to avoid being "stuck", you just plug it in and it boots the stock rom/kernel and starts charging. This would avoid you needing to access recovery manually and switch modes.
Click to expand...
Click to collapse
2.00 always boots safe system, no matter if ac is plugged in or not. No charge only mode.
2.01 boots non-safe kernel if ac is plugged in. But there is a problem. If the phone is switched off and you plug in ac, then it will go into charge only mode - like it should. If ac is plugged in and you try to do a normal boot or reboot it loads the non-safe-kernel, too, but gets stuck into bootloop. So normal boot of safe-system is only possible without ac. Thats the bug he will work on for safestrap 2.02.
tobby88 said:
2.00 always boots safe system, no matter if ac is plugged in or not. No charge only mode.
2.01 boots non-safe kernel if ac is plugged in. But there is a problem. If the phone is switched off and you plug in ac, then it will go into charge only mode - like it should. If ac is plugged in and you try to do a normal boot or reboot it loads the non-safe-kernel, too, but gets stuck into bootloop. So normal boot of safe-system is only possible without ac. Thats the bug he will work on for safestrap 2.02.
Click to expand...
Click to collapse
Thanks for the clarification on that. I will probably install 2.01 tonight.
Sent from my XT862 using Tapatalk 2
Related
Hi All,
Please help. While I'm charging my SGS with the phone turned off, there isn't any batter charging animation (before I rooted my phone, the animation was there). The battery picture is stuck at 0% all the time. However, when I turn on the phone, the charging indication is there along with how many percent have been completed (definitely, more than 0% as indicated when the phone turned off).
How to fix this problem? Thanks in advance for the help.
If it'll help, I'm running stock FW DXJF4 rooted.
Cheers
I noticed yesterday that I'm seeing something similar.
I've also noticed that if I try going into Clockwork Recovery via ROM Manager it no longer starts up directly, but instead eventually goes into the standard Recovery Manager and I have to start Clockwork Recovery manually via the update.zip file.
I'm using the JG5 based MCR r3 ROM so I may try reinstalling later.
Mimocan's market fix causes this
Thanks for that info, I'll have a play when I reinstall the OS later.
android53 said:
Mimocan's market fix causes this
Click to expand...
Click to collapse
So, I assume that this is normal? And yes, I'm using Mimocan's market fix (as well as lag/stall fix). Thanks for the help.
Its because you move the system files onto the ext4 partition, a partition that only gets mounted at boot.
The market fix is optional, personally i don't use it
get to keep my battery meter that way
I downloaded an older version of P3Droid's toolbox and tried enabling a different battery indicator. Suddenly, everything on the phone was FC'ing. I restarted but the phone won't get past the boot logo. I have RSD Lite installed and I downloaded the .890 SBF (because I updated), and went into AP Fastboot, but the battery is too low to flash it. I may be wrong in assuming the battery won't charge when my phone is stuck like this, but idk. Is there any other way to fix it?
Oh, and I had Koush's bootstrapper installed
Edit: It seems now there's a tweaked version of Koush's bootstrapper, by Hashcode, that allows booting into CWR by selecting BP-Tools. That would've prevented me from having to flash an SBF,
then rooting, then restoring a nandroid.
plug the phone in and try. if it wont charge you can try to let the battery die and take it to verizon and just say it stopped taking charges. if they throw in a new battery and boot it up and see your are boot looped they might get suspicious but maybe there will be enough juice to use rsdlite? idk
MyDrodonWall said:
plug the phone in and try. if it wont charge you can try to let the battery die and take it to verizon and just say it stopped taking charges. if they throw in a new battery and boot it up and see your are boot looped they might get suspicious but maybe there will be enough juice to use rsdlite? idk
Click to expand...
Click to collapse
The light next to the usb port on the phone lights up. Is that an indication that it's charging?
That usually means that it is charging
I goofed up my D3 into a similar situation playing with metamorphs. Using recovery I did a factory reset then used voice command to access the market and install a launcher to correct my mistakes (assuming your launcher is currently confused). Its a bit messy but it got me in. I wasn't going to run the risk of Verizon denying my exchange.
Sent from my DROID3 using XDA App
If I could access ClockworkMod, this wouldn't be an issue. I'd just restore one of my backups. I can't get into it though
Help! I'm a newbie at this forum , but I just a droid 3 today , and while trying to get into recovery mode , I got stuck in a continueious boot loop. D:
I Installed the rom manager , got an ics rom , installed clockwork mod etc , then went to reboot into recovery , but it would just do a normal reboot,. I then found a safestrap .apk , which was I guess a modified version of HashCodes. But when I went to reboot , it just got stuck in a boot loop. Any Ideas? I'm trying Hashcodes SBH flash or whatever to reset it to factory settings , but unfortunatly its a 500mb download. So thats gonna be an hour. Any suggestions?
Was Clockworkmod uninstalled/removed before you added Safestrap?
Sent from my DROID3 using XDA
Boot with X+Power, then both volume keys, and wipe data from withing Android Recovery. I'm not a fan of ROM Manager on the D3, it only seems to cause headaches in terms of ROM flashing.
Okay , I'll try that in a second. As SOON as I got finished with the download , the phone died. ( left it in the fastboot mode thinking it was charging...apparently not...D: ) So I will post results in about 20mins. Also , is there any other way to install roms without it?
I've done alot of ROM flashing to windows devices and just older things...and I always liked the simple installers without any problems etc. Anything like that on the Droid 3?
And no , it was installed. Haha , but with the strap , I don't think it installed completely? It kept force closing the installer right before it got to 100% ( I thought it got to 100% ). I didn't know if that was normal , or what. I couldn't open the app after that...
Now , I;m having a different issue. The phone died , and I've had it on the charger for a good 20-30mins , and it won't even go into the bootloop now. It will turn on with a battery with a question mark in it , but it won't do anything else. Help? Haha
You're moving too fast lol
Once you get your battery charged, it'll probably be best to start with a fresh SBF flash (an SBF that is appropriate for your phone, of course).
Then root with one of the many tools mentioned in the development forum
Then install the safestrap app, then run it, and hit the install button. It will say in the safestrap app if the safestrap recovery has been installed (the first line in the app window, I believe)
If safestrap doesn't say that it installed (in that first line), you may have to separately install Busybox installer (its free in the android market). Then you can try to hit the install button in safestrap again.
With safestrap installed, you can restart phone.. you should see the safestrap splashscreen on bootup - hit Menu to go into safestrap recovery.
In safestrap recovery, it will be in non-safe mode (your phone's current stock rom).
Use the volup/voldown button to navigate, and power button to select.
Go to the safe menu, and hit toggle safe zone (or whatever its called)
It will move the necessary stuff and get you into the safe zone. Once that's done, there will be no rom on it yet, so you can then install a custom rom from zip.
Hope this helps
DreadCode said:
Now , I;m having a different issue. The phone died , and I've had it on the charger for a good 20-30mins , and it won't even go into the bootloop now. It will turn on with a battery with a question mark in it , but it won't do anything else. Help? Haha
Click to expand...
Click to collapse
The phone does not charge when it hasn't booted. You're gonna have to buy or jerry-rig a usb battery charger. You can take any old USB cable, strip the wires, and tape the black wire to the (-) terminal on the battery, and tape the red wire to the (+) terminal on the battery. Charge the battery for a maximum of 3 hours.
Sent from my DROID3 using XDA
Thank you Chatoic* I did that last night after I realized the battery didn't charge. Then flashed a new SBH etc. Rooting worked fine , and now I get to the menu just fine on bootup. But now I'm having another issue. I go to Rom Manager , and try to install my AOKP ICS from the SD card , but when It reboots and goes to the menu etc , I don't know what to do to install it. It makes a backup I think? But doesn't install the ROM. Sooo any Ideas? Am I missing a file or something on the sd card? And it says Error partitioning the SD card with a backup etc...
IMO, ROM Manager only causes way more headaches than it fixes, at least on the D3. I would recommend a folder simply called AAAZips (This is what I use, it keeps it at the top for less/no scrolling in Boot/SafeStrap) on your external SD card. Then install either SafeStrap or BootStrap, as you prefer, and reboot into recovery this way to backup/flash/wipe/etc.
Moral of this, IMO, ditch ROM Manager.
redsox985 said:
IMO, ROM Manager only causes way more headaches than it fixes, at least on the D3. I would recommend a folder simply called AAAZips (This is what I use, it keeps it at the top for less/no scrolling in Boot/SafeStrap) on your external SD card. Then install either SafeStrap or BootStrap, as you prefer, and reboot into recovery this way to backup/flash/wipe/etc.
Moral of this, IMO, ditch ROM Manager.
Click to expand...
Click to collapse
Lol. Mine is called Aisthefirstletter
Sent from my XT860 using xda premium
Then I just boot into recovery and do what to install the .zip?
And what do I put in the AAAzip folder?
Nevermind I think I got it working. WAY better then rom manager.....
I'm glad it's working. It may not be as nicely polished as ROM Manager, but flashing through CWM/SS from SD card seems to work better.
DreadCode said:
Help! I'm a newbie at this forum , but I just a droid 3 today , and while trying to get into recovery mode , I got stuck in a continueious boot loop. D:
I Installed the rom manager , got an ics rom , installed clockwork mod etc , then went to reboot into recovery , but it would just do a normal reboot,. I then found a safestrap .apk , which was I guess a modified version of HashCodes. But when I went to reboot , it just got stuck in a boot loop. Any Ideas? I'm trying Hashcodes SBH flash or whatever to reset it to factory settings , but unfortunatly its a 500mb download. So thats gonna be an hour. Any suggestions?
Click to expand...
Click to collapse
I'm noticing that the modded safestrap kicks me out of safe mode when flashing and then causes me to bootloop, maybe because of a problem w/the flash related to kicking me out of safe mode or something. Try hashcodes safestrap apk from his blog site and see if you have any more luck with that.
Hey all, hopefully someone can help me out. Ill post the full story and the tl;dr version at the end.
So, my Xperia TL (LT30at) has been rooted for over a year and a half. Since i rooted it it never charged when turned off. I did research and couldnt figure out why, so i left it and have lived with it for the last year and a half. However, i just updated my phone to JB 4.3 by Dark Lord (Ultimate Pure XT ROM) so the model number is actually Xperia T (LT30) Anyways, the phone dies a lot quicker than before so the other day it died and because it wont charge when it is off i usually wrap a rubber band over the power button so itll charge enough to turn on and then charge by itself after that. However, it would only charge enough this time to boot, but then turn right back off. I did this for well over a day and got sick of it not working so i tried messing with things. In the process, I was in recovery (it was philz cwm or something like that, by the way im quite a noob when it comes to all of this, hence why im having problems) and i flashed the xposed disabler zip, thinking it would get rid of cwm because i didnt know what I was doing. It did end up getting the phone to turn on, and its charging great. However, the system UI crashes, and the "unfortunately the system UI has stopped working" pops up repeatedly so you cannot physically do anything on the phone. I tried going back into recovery to flash my backup to fix everything, but it was downgraded back to an older version of cwm, the version i origonally had on it before the 4.3 update. its like 6.0.3 or something, by david marcos or something. Anyway, itll go into recover but a bunch of error messages come up, like unknown volume path, no etc/recover.fstab, stuff like this. There is no way to flash any recoveries because it basically says it cannot find the paths. It will not backup, restore, wipe anything, flash from sideload, nothing. Ive tried all i can think of. Basically cwm comes on but i cant use it for anything. Instead i tried reinstalling cwm to try to fix it, but when i do it says "system cannot find path specified" so it wont download.
tl;dr version, cwm wont work at all after flashing xposed-disabler.zip. i cannot flash any recoveries or install anything through the usb. What do i need to do to fix this? because the system ui keeps crashing my phone is basically useless. thanks for dealing with a numskull..thanks in advance.
You can flash a stock rom with kernel using flash tool and then flash recovery and restore your backup.
Sent from my Xperia T using cm12
arniks8 said:
You can flash a stock rom with kernel using flash tool and then flash recovery and restore your backup.
Sent from my Xperia T using cm12
Click to expand...
Click to collapse
why i didn't think of that, i dont know.
This worked as far as getting the phone to boot and whatnot, however the phone died and because it doesnt charge when it is off, i cant turn it on. it will boot and itll get all the way to the home screen but it immediately shuts back down, even though it is plugged in. Is there any way to fix this charging bug? i did some research and found it is linked to cwm, however now that i flashed the stock rom i no longer have cwm on the phone, so why does it still not charge when off? Thanks for the help by the way..
Rooted, Bootloader unlocked, TWRP installed, Xposed Running. 5.0 - I did not yet update or press update ever, If I have ever accidentally allowed it to begin downloading I kill the download by deleting the file using SDMaid.
I got home, had problems with other devices, phone was on about 40% at this point. I remember hearing the phone reboot, I noticed it went into TWRP, which was strange, I restarted system > powered up > lockscreen > restart to twrp with no interaction. Phone is now getting low 21%ish. Fix permissions - because used to be the all out fix on my other devices.
Same thing again > straight into twrp.
I notice that some scripts have been ran in the twrp console. Something along the lines of Victara_en_US.zip Some red scripts I assume saying failed to update.
I assume the phone is now too low to power up.
It shows no sign of charging since leaving the last twrp reboot.
Green light in top speaker shows when attempting to power up with usb charger plugged in > nothing else happens.
With charger unplugged from phone I see my modified logo screen and the moto planet spinning before phone turns off completely. This process now repeats.
Anyone have any idea what the hell is wrong with my phone?
EDIT UPDATE:
Managed to get into the fastboot menu:
Battery Low (RED)
Device is UNLOCKED status code 3 (YELLOW)
Software status modified (YELLOW)
As normal aside from Battery...
THE-M1GHTY-BUKO said:
EDIT UPDATE:
Managed to get into the fastboot menu:
Battery Low (RED)
Device is UNLOCKED status code 3 (YELLOW)
Software status modified (YELLOW)
As normal aside from Battery...
Click to expand...
Click to collapse
Get your phone into TWRP and connect it to your charger and let it charge to at least 70% Use Advanced Wipe in TWRP, select Cache and wipe that. Then see if your phone will start normally. Somehow you have downloaded the update file and it is trying to run automatically. Since your phone is modified, the update fails (and nothing is updated or changed.) The update file is in /cache so wiping that should correct the problem. You should go ahead and update to the Stagefright patched version of your ROM so you aren't having to deny the factory update all the time.
mikeoswego said:
Get your phone into TWRP and connect it to your charger and let it charge to at least 70% Use Advanced Wipe in TWRP, select Cache and wipe that. Then see if your phone will start normally. Somehow you have downloaded the update file and it is trying to run automatically. Since your phone is modified, the update fails (and nothing is updated or changed.) The update file is in /cache so wiping that should correct the problem. You should go ahead and update to the Stagefright patched version of your ROM so you aren't having to deny the factory update all the time.
Click to expand...
Click to collapse
Attempting this now....
Phone still boots to a black screen. I don't understand why it would download the update let alone attempt to install it, I religiously deny the update. Also why would it have booted up normally then forced itself into TWRP? :S
What can I next? I dont mind wiping using fastboot as I managed to take all my files off the phone via twrp.
This happened to me a couple times but wiping the cache AND the dalvik cache fixed it. If it still doesn't work, I hope you have a backup because you are going to have to wipe the system and data next. Sometimes these updates like to link themselves to all the phone's partitions, and in that case you should wipe everything and restore your full system and data backup in recovery.
TyNote3Krill said:
This happened to me a couple times but wiping the cache AND the dalvik cache fixed it. If it still doesn't work, I hope you have a backup because you are going to have to wipe the system and data next. Sometimes these updates like to link themselves to all the phone's partitions, and in that case you should wipe everything and restore your full system and data backup in recovery.
Click to expand...
Click to collapse
I wiped both the first time I tried it :-/
I don't have a system backup as a far as I am aware, need to check main pc for something like that. I had a lot of trouble with no signal after changing my phone to x1095 so I could root it etc. Just hope I don't have the same trouble again. Can i reinstall the system through twrp? Or do I need to flash via fastboot?
Whats my best option, system files wise, for fixing this?
THE-M1GHTY-BUKO said:
I wiped both the first time I tried it :-/
I don't have a system backup as a far as I am aware, need to check main pc for something like that. I had a lot of trouble with no signal after changing my phone to x1095 so I could root it etc. Just hope I don't have the same trouble again. Can i reinstall the system through twrp? Or do I need to flash via fastboot?
Whats my best option, system files wise, for fixing this?
Click to expand...
Click to collapse
If you dont have a backup, at this point, I don't see any other options besides formatting your data or flashing the stock firmware. Of course, don't just take my word for it, but in the future just make sure you have a working backup available.
TyNote3Krill said:
If you dont have a backup, at this point, I don't see any other options besides formatting your data or flashing the stock firmware. Of course, don't just take my word for it, but in the future just make sure you have a working backup available.
Click to expand...
Click to collapse
Am I able to flash anything other than the stock 5.0? Last I checked I had converted whatever I had to the x1095. I remember everything being easier on other phones...
Yes, you can, just make sure you have the right file for the job. They are usually about 2 gigs, and they take forever to flash. Note that once you flash the file, your phone will be as if you just bought it from the store, but it always will boot if you have the corresponding build.
THE-M1GHTY-BUKO said:
Attempting this now....
Phone still boots to a black screen. I don't understand why it would download the update let alone attempt to install it, I religiously deny the update. Also why would it have booted up normally then forced itself into TWRP? :S
What can I next? I dont mind wiping using fastboot as I managed to take all my files off the phone via twrp.
Click to expand...
Click to collapse
In TWRP, make a backup now even though it may not be useful depending on what the problem is. Then, use advanced wipe in TWRP and wipe data. If the phone will boot now, something got corrupted in data and you'll just need to set your phone up again. If the problem continues, you'll have to flash your system image. How to do this varies with the model of your phone; some models have TWRP images, others need to use fastboot files. After you flash the new system image, you can either just continue to clean setup the phone, or you can try to restore only data from the backup you made previously.
TyNote3Krill said:
Yes, you can, just make sure you have the right file for the job. They are usually about 2 gigs, and they take forever to flash. Note that once you flash the file, your phone will be as if you just bought it from the store, but it always will boot if you have the corresponding build.
Click to expand...
Click to collapse
Does that include 5.1 roms? I can never seem to find x1095 5.1 roms, or anything for that matter, they are all titled with every other version.
mikeoswego said:
In TWRP, make a backup now even though it may not be useful depending on what the problem is. Then, use advanced wipe in TWRP and wipe data. If the phone will boot now, something got corrupted in data and you'll just need to set your phone up again. If the problem continues, you'll have to flash your system image. How to do this varies with the model of your phone; some models have TWRP images, others need to use fastboot files. After you flash the new system image, you can either just continue to clean setup the phone, or you can try to restore only data from the backup you made previously.
Click to expand...
Click to collapse
I tried wiping data to no avail.
Im trying to download stock 5.0 for now but the download is taking decades for some reason. Do you, or anyone else, recommend any roms which I can easily flash without having to worry about modem files?
THE-M1GHTY-BUKO said:
Does that include 5.1 roms? I can never seem to find x1095 5.1 roms, or anything for that matter, they are all titled with every other version.
Click to expand...
Click to collapse
Hopefully this could provide more information for your situation?
http://forum.xda-developers.com/moto-x-2014/development/rom-xt1095-flashable-stock-rom-t3185945
Thank you for your help, as well as anyone else who helped me. I now have a running phone on 5.1.
How do I gain root from here? My superuser app updated and now tells me I have no binary, despite telling me to flash something only 5 minutes prior.
Sent from my XT1095 using XDA Free mobile app
So you don't have root? I would suggest rooting using towelroot. Go online and search "towelroot" click on the first result, click on the lambda to download the apk, and install it. You can then open the app, and press "make it ra1n" to root your device without any reboot needed.
I had root prior to wiping and installing the 5.1 update that was linked to me. Towelroot gives me the phone not supported message.
Sent from my XT1095 using XDA Free mobile app
Towel root does not work in 5.1.
To root just flash TWRP. Start TWRP. When you exit TWRP it will ask you if you want to root it. Simple.
Sent from my XT1095 using Tapatalk
I'm still in the "phone not responding" phase.. how did you manage to get in the bootloader from there? Tnx!
I found a chainfire autoroot IMG that rooted my phone. Found xposed too. I'm back at a fully working phone now, thank you to all who helped me.
Gotta say, the battery life on 5.1 is a hell of a lot better.
Sent from my XT1095 using XDA Free mobile app
As in you can't get it to fastboot?
I left it to charge for a while, then took about 5 minutes attempting the power button volume button combo to restart and get it into fastboot.
I believe that it's something like:
Power + vol down until the phone screen flashes/green light goes off
Then
Still holding the power and volume down
Hold the vol up too
Then release the power still holding the vol up and down.
That's what worked for me. It's literally the most awkward phone I've had go button combos.
I think vol up from powered off works too.
If you mess up just hold the power and vol down again.
Sent from my XT1095 using XDA Free mobile app