I'm having a issue in which I rooted and unlocked using Wug's toolkit. I used this successfully since Thursday that I got my phone without issues. Well today I went into twrp recovery and wiped cache and dalvic cache as I was having issues installing apps (apks) and from store. Now my phone boots but just sits at boot screen without starting up. I am able to boot into recovery but phone still won't boot after restart. I have already waited over 30 mins and have tried multiple times. I called my carrier and they want to send me a replacement, but my concern is how to set it back to stock. Any help would greatly be appreciated.
cbrvnm said:
I'm having a issue in which I rooted and unlocked using Wug's toolkit. I used this successfully since Thursday that I got my phone without issues. Well today I went into twrp recovery and wiped cache and dalvic cache as I was having issues installing apps (apks) and from store. Now my phone boots but just sits at boot screen without starting up. I am able to boot into recovery but phone still won't boot after restart. I have already waited over 30 mins and have tried multiple times. I called my carrier and they want to send me a replacement, but my concern is how to set it back to stock. Any help would greatly be appreciated.
Click to expand...
Click to collapse
wipe dalvik cache??? From what i know, Lollipop uses ART.
These are the options I have in my recovery under advanced wipe
Even though the runtime is ART now, clearing dalvik in TWRP does force a 'rebuild' of apps upon boot, so it does still have a purpose.
The 'rebuild' I'm talking about is the "android is upgrading" screen.
cbrvnm said:
These are the options I have in my recovery under advanced wipe
Click to expand...
Click to collapse
just flash the stock firmware with your recovery. I would recommend reporting this bootloop issue to twrp. Im sure it has someting to do with it.
Flash system.img
Ghettonine said:
just flash the stock firmware with your recovery. I would recommend reporting this bootloop issue to twrp. Im sure it has someting to do with it.
Click to expand...
Click to collapse
When he says "firmware" he means
Code:
fastboot flash system system.img
It won't wipe your data, but it will remove no-force encryption (NFE) and you're going to need to re-root :good:
Had the same problem a few days ago.
@Ghettonine I don't think it's TWRP, more so SuperSU
I was able to use rootkit to flash stock and unroot and it goes through the whole process and states that it was successful and to wait until it boots. The problem is that it never boots and stays in the boot screen. Also I have had it on for 30 mins multiple times and still not working. I boot into recovery but this time I don't have TWRP anymore I just have a android with red triangle with no options to choose. Any other suggestions that could help?
Re-flash stock factory images and stop relying on tool kits to flash stuff. Learn how to use adb and fastboot, or just don't bother messing with root.
Related
Like an idiot I wiped my System inside TWRP. Using TWRP 2.6.0.2
Earlier tonight my phone starting rebooting. I was inside GooManager and tapped reboot to recovery. When I did that, for some reason my phone lost root. Meaning when I went to reboot inside TWRP it stated that it looks as if my phone is not rooted. I rebooted anyway without installing SuperSU through TWRP. I was already rooted. Afterwards, it would boot up fine but kept constantly rebooting only after a minute or two.
I went back into TWRP and clicked through dalvik wipe and cache wipe. Still got reboots. I was planning on flashing CyanogenMod anyways so I thought I'd go on and wipe everything. I went in to advance wipe and check everything. As I swiped the slider to wipe I realized I checked System too, but it was too late.
Now my phone won't boot past the HTC logo with the red text underneath. I can boot into TWRP however so I hope all is not lost. I am currently at work so I have no way to try anything on the phone at the moment but was hoping for some advice on what to try later when I get home.
I'm thinking maybe I'll be able to use the "Mount" tab in TWRP to load a ROM on and flash and everything will be well again. Would I mistaken to think that? If not, I'll purchase an USB OTG cable and use a USB stick but I really need this up an running as quickly as possible.
Also, does anyone think it would be best just to go back to stock at this point (if I can) and start from scratch?
Much thanks for your help and advice,
dgb1891
So, oddly enough I did the same thing, How I managed to recover it so you can adb sideload a rom from TWRP and have access to a "working" phone again was to find your stock recovery.img, then flash it via fastboot, and then from the hboot menu, choose factory reset and let the stock recovery do it's thing, then reflash TWRP (I honestly like CWM doe) and adb sideload a rom (presumably what you were using before). It SHOULD fix your problem and you'll be able to mount files again.
hayame said:
So, oddly enough I did the same thing, How I managed to recover it so you can adb sideload a rom from TWRP and have access to a "working" phone again was to find your stock recovery.img, then flash it via fastboot, and then from the hboot menu, choose factory reset and let the stock recovery do it's thing, then reflash TWRP (I honestly like CWM doe) and adb sideload a rom (presumably what you were using before). It SHOULD fix your problem and you'll be able to mount files again.
Click to expand...
Click to collapse
By stock recovery.img you mean a stock HTC image? - or do you mean a recovery like TWRP or CWM?
dgb1891 said:
By stock recovery.img you mean a stock HTC image? - or do you mean a recovery like TWRP or CWM?
Click to expand...
Click to collapse
Literally stock recovery.img, not TWRP or CWM.
hayame said:
Literally stock recovery.img, not TWRP or CWM.
Click to expand...
Click to collapse
K. Thanks. I have a feeling this is going to be a bit more complicated than I first thought...
I followed what you suggested and got the phone back up and working. Thanks again.
Hi All,
I have the VZW DE and was having trouble deleting files when connecting my phone to Ubuntu (when I tried to delete a file, my phone would reboot). I figured I corrupted some files and had a nandroid backup from a few days ago. So I rebooted into TWRP and did a restore of the backup (system, data, and boot). But now when I reboot, my phone is stuck in a boot loop on the bootloader unlock screen. It will stay on for about 30 seconds, the phone will power down and then back to the bootloader unlock screen . I have no choice but to go back into TWRP.
I tried all that I could, I wiped then restored, same thing. I even had a back up from a few weeks ago but same results. Strange thing is, every time I go back into TWRP and click the Mount button, System mount is always unchecked even when I check it and reboot (same thing happens, stuck on bootloader unlock screen and will have to go back into TWRP)
Any ideas whats happening? I thought the restore would work perfectly but has completely stopped me from getting back on my phone.
Thanks guys!
atomus12 said:
Hi All,
I have the VZW DE and was having trouble deleting files when connecting my phone to Ubuntu (when I tried to delete a file, my phone would reboot). I figured I corrupted some files and had a nandroid backup from a few days ago. So I rebooted into TWRP and did a restore of the backup (system, data, and boot). But now when I reboot, my phone is stuck in a boot loop on the bootloader unlock screen. It will stay on for about 30 seconds, the phone will power down and then back to the bootloader unlock screen . I have no choice but to go back into TWRP.
I tried all that I could, I wiped then restored, same thing. I even had a back up from a few weeks ago but same results. Strange thing is, every time I go back into TWRP and click the Mount button, System mount is always unchecked even when I check it and reboot (same thing happens, stuck on bootloader unlock screen and will have to go back into TWRP)
Any ideas whats happening? I thought the restore would work perfectly but has completely stopped me from getting back on my phone.
Thanks guys!
Click to expand...
Click to collapse
what FW are you on? what twrp version are you using? did you try wiping cache and dalvik before and after restoring your back up?
jayboyyyy said:
what FW are you on? what twrp version are you using? did you try wiping cache and dalvik before and after restoring your back up?
Click to expand...
Click to collapse
Sorry about the delay. Thanks for your response jay!
If by FW you mean firmware, I'm on Verizon's 139.15.1_ghost. I just recently flashed twrp version 2.6.3.1 to prep for 4.4 and it flashed successfully. I wiped cache and dalvik before and after (always like to be on the safe side haha).
I tried a few other methods, like wiping the system and restoring, and wiping system, flashing the flashable zip 139.15.1 and restoring just data from the backup, etc.
I'm thinking about just RSDing my phone with the latest firmware (140.45.5_ghost) and start from scratch. Is that tool available for Linux?
atomus12 said:
Sorry about the delay. Thanks for your response jay!
If by FW you mean firmware, I'm on Verizon's 139.15.1_ghost. I just recently flashed twrp version 2.6.3.1 to prep for 4.4 and it flashed successfully. I wiped cache and dalvik before and after (always like to be on the safe side haha).
I tried a few other methods, like wiping the system and restoring, and wiping system, flashing the flashable zip 139.15.1 and restoring just data from the backup, etc.
I'm thinking about just RSDing my phone with the latest firmware (140.45.5_ghost) and start from scratch. Is that tool available for Linux?
Click to expand...
Click to collapse
thats your problem. you flashed twrp for 4.4 but you weren't on 4.4. I don't believe that twrp is backwards compatible. what you need to do is flash your old twrp back to the recovery. then restore your backup. then flash the stock recovery and system images. then take the ota. then flash the new twrp, then boot phone, say you wnat root. then create another back up of that twrp.
jayboyyyy said:
thats your problem. you flashed twrp for 4.4 but you weren't on 4.4. I don't believe that twrp is backwards compatible. what you need to do is flash your old twrp back to the recovery. then restore your backup. then flash the stock recovery and system images. then take the ota. then flash the new twrp, then boot phone, say you wnat root. then create another back up of that twrp.
Click to expand...
Click to collapse
Never even thought about that! I will try those steps as soon as I get home today!
Thanks jay!!
Straight to the point:
Installed Xposed Lollipop, gave me low storage warnings
Rebooted to see if it would fix that, it built cache again but warning stll there
Boot into recovery, selected "Fix Permissions" in TWRP, wiped dalvik cache and cache
Booted again, goes through boot cycle but then goes straight to a black screen. Can get into bootloader. Wasn't able to go into recovery (spit out a black screen) but I plugged it into the charger and was able to get in.
I've unlocked the bootloader, rooted and that's about it. I'm rocking the Pure Edition. Anything I can do short of Factory Reset? I really don't want to lose my data for no reason.
Edit: I flashed system.img and boot.img from the toolkit in Android Development. That didn't work outside of TWRP detecting root wasn't installed. I did a Factory Reset in TWRP and that fixed things. Oh well.
Did you wiped dalvik and cache after flashing zip? ?
@jcracken: the perils of using Alpha software.
Go back into recovery and reflash xposed. Then reboot. I also used selmodechanger and set it to permissive.
This is not due to xposed. The bootloop was due to TWRP, DO NOT FIX PERMISSIONS FROM TWRP. It will cause a boot loop on lollipop whenever you do it
To uninstall xposed on lollipop go into file manager in twrp and delete xposed.prop in /system partition after mounting and also delete xposed.jar in /system/framework
If you want a toy, get an iPhone. If you want a Smartphone, get an Android
Hi,
I had recently tried to root my Moto G 2014 (running 6.0) so I could install the latest CM13. I followed all the instructions and even came across the red WARNING BOOTLOADER UNLOCKED SCREEN every time I try to reboot the device(status code=3). After installing TWRP 3.0.2.3 and making a backup of current state, I ran into a few bootloops which I managed to fix by flashing it back with a stock as shown on this thread http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682 (I downloaded both the download links and extracted everything to a single folder before following all the commands)
The SIM wasn't receiving any signal thereafter, which I luckily managed to fix with help from another thread.
My problem is that I've tried to install SuperSU more than a couple of times with different versions and it almost always sends my phone into a bootloop. The few times where I was able to boot into system, it kept giving me the error that the necessary binaries weren't installed and I was not able to do as well, due to the bootloop issue. Working RootChecker told me that my device wasn't rooted properly, which I wasn't surprised at.
Although I read somewhere that rooting isn't necessary to flash a custom ROM like CM13, so I decided to negate SuperSU (I did the unroot everything option on SuperSU and factory reset the device, cleared data, cache and dalvik too) and try flashing it directly instead through TWRP. It kept giving me the Error 7 even after I had removed the assert checks.
Can someone tell me what I did wrong and what can I do to go ahead? Also, is my bootloader completely unlocked? I tried checking *#*#7378423#*#* but nothing happened, so I rebooted into bootloader and used the 'fastboot oem device-info' command but it said that the command was invalid or something.
As of right now, the phone is running 6.0 with all the stock apps. The bootloader unlocked warning still shows up every time I reboot the phone though.
Boot into twrp and wipe cache , dalvik cache, system and data and flash cm13 and wipe cache and dalvik cache and reboot you should be good to go if u want root access flash the latest version of supersu or you can for a rom which has preinstalled supersu such as dirty unicorns.
phoenix964 said:
Hi,
I had recently tried to root my Moto G 2014 (running 6.0) so I could install the latest CM13. I followed all the instructions and even came across the red WARNING BOOTLOADER UNLOCKED SCREEN every time I try to reboot the device(status code=3). After installing TWRP 3.0.2.3 and making a backup of current state, I ran into a few bootloops which I managed to fix by flashing it back with a stock as shown on this thread http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682 (I downloaded both the download links and extracted everything to a single folder before following all the commands)
The SIM wasn't receiving any signal thereafter, which I luckily managed to fix with help from another thread.
My problem is that I've tried to install SuperSU more than a couple of times with different versions and it almost always sends my phone into a bootloop. The few times where I was able to boot into system, it kept giving me the error that the necessary binaries weren't installed and I was not able to do as well, due to the bootloop issue. Working RootChecker told me that my device wasn't rooted properly, which I wasn't surprised at.
Although I read somewhere that rooting isn't necessary to flash a custom ROM like CM13, so I decided to negate SuperSU (I did the unroot everything option on SuperSU and factory reset the device, cleared data, cache and dalvik too) and try flashing it directly instead through TWRP. It kept giving me the Error 7 even after I had removed the assert checks.
Can someone tell me what I did wrong and what can I do to go ahead? Also, is my bootloader completely unlocked? I tried checking *#*#7378423#*#* but nothing happened, so I rebooted into bootloader and used the 'fastboot oem device-info' command but it said that the command was invalid or something.
As of right now, the phone is running 6.0 with all the stock apps. The bootloader unlocked warning still shows up every time I reboot the phone though.
Click to expand...
Click to collapse
while @kushal_10 explained most of the things to do, i would like to remind you that CM13 has inbuilt Root. You just have to enable Developer options, then in Developer Options,under Root Access, choose Apps and ADB. Don't flash SuperSu
Hope I helped you.
kushal_10 said:
Boot into twrp and wipe cache , dalvik cache, system and data and flash cm13 and wipe cache and dalvik cache and reboot you should be good to go if u want root access flash the latest version of supersu or you can for a rom which has preinstalled supersu such as dirty unicorns.
Click to expand...
Click to collapse
I read somewhere that wiping the system isn't advisory because in case something goes wrong, there will be no way to restore. Can you confirm this?
Hi,
I was running Oxygen 4.0.0 and a beta build of TWRP 3.0.3 which works with new encryption. I used the android update mechanics to get the 4.0.1 OTA. System rebooted to recovery, recovery threw an error (zip file corrputed) and since then I am not able to boot the system. Whatever I do I land in TWRP recovery.
Things I did so far:
- Tried installing the full 4.0.1 zip. Install worked without errors, device still boots to recovery.
- Tried to get stock recovery, since another post (https://forum.xda-developers.com/oneplus-3t/help/stuck-recovery-mode-t3532524) indicates stock recovery might fix the problem
--> stock recovery is not obtainable anymore. Seems deleted from all the download links I could find. Example is here: https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
- Wipe cache and dalvik cache in the hopes, the instruction to boot to recovery is there somewhere.
I did not do the unbrick tool, since I run linux and didnt want to fiddle with windows yet.
I did make a nandroid backup, so once my system boots again I should be fine.
Any Idea where to either get a mirror of stock recovery or how to fix this problem otherwise?
I had this same problem, and I solved downloading the unbrick tool and extracting the recovery from there. Here is the file
https://drive.google.com/file/d/0BwaafKaXbak3d1RFblFOWVd5eGs/view?usp=sharing
Also locking the bootloader worked for me. Booted into system then unlocked again.
Thanks a lot for the stock recovery. That worked!
Once it booted, installing TWRP and SuperSU again.
mad-murdock said:
Thanks a lot for the stock recovery. That worked!
Once it booted, installing TWRP and SuperSU again.
Click to expand...
Click to collapse
Does your TWRP boot correctly? I flashed it and when I restarted I still had the stock recovery, so I used fastboot boot and it booted, but it is stuck in the loading screen.
Edit: After rebooting and reflashing totally random, it worked.
mariospizza said:
Does your TWRP boot correctly? I flashed it and when I restarted I still had the stock recovery, so I used fastboot boot and it booted, but it is stuck in the loading screen.
Edit: After rebooting and reflashing totally random, it worked.
Click to expand...
Click to collapse
Yeah, worked totally normal as it should.
My educated guess about this whole dilemma is, the system sets a flag to boot to recovery which TWRP doesn't clear and only stock recovery clears. Usually those flags should be in cache partition, but in this case isn't.
Tldr: don't use build in update mechanisms if you modified Rom and recovery.