Hey I recently flashed Nameless ROM onto my i9300, restarted once, and then my phone kept rebooting into recovery. However, TWRP was crewed up for some reason and would keep restarting as soon as the starting 'Teamwin' picture finished (it would restart the animation / picture). I flashed TWRP again but it still happened (and I couldn't boot normally). My TWRP also had the material play theme on it. I eventually fixed this by flashing CWM and re-flashing the ROM (and gapps).
However, I'd would still like to know why TWRP was crashing.
Thx
I am having the same issue, caused by battery malfunction though.
almost bricked device
Oh okay.
Related
I was using my phone and all had been working fine for ages. It was in my pocket for a while and when i took it out to use it I saw that it was on the boot animation of CM11. My phone was already on when I last used it so I had assumed it had crashed. I took the battery out and turned the phone on again but it got stuck on the CM boot animation. The last time I turned on my phone before that was when I flashed a supersu zip file to make my root work as I was having some problems. After flashing the supersu zip and told my CWM recovery to restart the system, it prompted me to "fix root" or something like that, and I clicked yes and it booted normally. That was the last time it booted normally before being stuck as it is now. First thing I did after it got stuck was go into recovery and reflash my current rom ( a CM11 snapshot) I then got faced with a status 7 error and so couldnt flash the rom. So then I flashed multiple other CM11 roms, none of which worked, so I flashed a CM10.2 stable rom which worked. I then got faced with the fix root before reboot thing and so I clicked yes. Still had the stuck booting thingy. I tried many things, flashing kernals roms gapps etc and nothing made a difference. I wiped cache, dalvik cache and no difference. I even wiped the system and tried to flash roms but only the 10.2 one would work, still got a status 7 with the CM11 ones. When I wiped my data however and flashed CM 10.2, it booted. I still couldn't flash the CM11 roms though even after a factory reset. So I have the reason to believe something in the data is wrong, not cache system or anything like that. What could it be? I don't want to have to lose all my data in order to be able to use my phone again, even then, something is still wrong as my phone won't flash CM11 roms anymore. So my questions are;
What things could have caused this?
Can this be a problem from flashing the supersu zip (a root issue)
Is it possible to somehow view or copy the internal data on a computer (since I cant get into the operating system), and this would allow me to get all my pictures contacts music etc anything so I can use my phone by wiping data?
Thanks, sorry this is quite long and probably hard to understand whats going on, but help is appriciated thanks
Don't fix root if you wish to use SuperSU instead builded-in cm superuser. Also try to flash via Odin latest recovery. TWRP should be fine. You can mount partitions from recovery level to download data to your computer. Of course if it still exists. If not, if they are corrupted you need to flash stock ROM and repeat whole cm11 adventure again. If Odin successfully flash the stock then it's a chance your partition layout and user data are untouched.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
I have twrp installed version 2.8.7. I flashed DU rom and everything went well. Went I reboot the device it just stops on the Google logo indefinitely. In this state it also heats up a lot. Help me please
nyasha1935 said:
I have twrp installed version 2.8.7. I flashed DU rom and everything went well. Went I reboot the device it just stops on the Google logo indefinitely. In this state it also heats up a lot. Help me please
Click to expand...
Click to collapse
Your bootloader is unlocked?
yes
nyasha1935 said:
yes
Click to expand...
Click to collapse
Try these commands in bootloader:
Fastboot format userdata
Fastboot format cache
Note that the 1st command will wipe your SDcard.
Strange, my N9 just started doing the same thing. I wonder if it's a hardware problem (like some bad blocks in the flash memory). I've been running AICP without issues for the past 3 months.
I did notice that I can sometimes press the volume up button on the Google screen, and it will then continue on and boot normally.
(Actually, upon further inspection, it appears that just letting my N9 sit at the Google screen for a few minutes, will sometimes get it to boot).
When I have time, I'm gonna try re-flashing the factory image (LMY48I) and see if that helps.
---Update---
Yup, that fixed it. Fastboot flashed all the .img files, and now my N9 starts normally every time.
Gonna go back to a custom ROM when I get a chance. I'll report back if I see this behavior again.
Sent from my Nexus 9
Hi guys,
I was flashing the latest build of DU and my nexus 9 got stuck at google logo. Since then I tried everything possible i.e. factory reset, flashed the latest factory build, tried using the stock kernel along with the factory image, tried flashing paranoid android. Nothing worked. Can anybody help me fix my device? Should I consider it bricked?
Hi.
I have a slight problem with my device. Yesterday, after installing new update via updater my device cant boot the system. It stays on black screen with "MI" then "Powered by android" appears and nothing happens (waited couple of hours, but still nothing). I've tried to wipe cache, dalvik cache and factory reset via recovery - still nothing.
My device was flashed to have TWRP and then supersu - haven't used any other modifications.
Can anyone please help?
Cheers
Same here, TWRP backup also seems gone and cant manually install the update ROM nor the previous stable one.
My problem is solved.
I've flashed miui v.6.7.5 via miFlash and then installed new release through recovery and it works just fine.
Hello guys,
I had a very strange problem with my Xperia Z3V. The phone was rooted and had philz touch installed. OS 5.1.1. The phone was charging and when I found it, it was rebooting itself continuously. So I went to philz touch recovery and tried to clear cache. Rebooted, and the phone passed Sony logo and started to boot the system, but after a while restarted itself. Then I went back to philz touch cleared cache and dalvik an retried. still the same. So I decided to format the system. still no success. But the problem I am facing now is that I am not able to enter recovery anymore. I can only enter system recovery which doesnt help at all. I tried to enter using safe mode but no luck reaching the philz touch recovery. Maybe philz touch has gone for good.
Any suggestion how to bring the phone to life once again?
Thank You all,
Same (sort of).
Two days ago one of mine stopped getting reception completely. After messing around with the SIM I decided something else is wrong.
It also won't cycle through reboot properly. Particularly, it won't shut down and gets very hot.
No new apps or messing with it. Just all of the sudden, on its own.
Now I can't get into Philz recovery to bring it back to a saved backup.
My other one is fine, and the two have identical apps, widgets and layouts.
If you had auto update Apps then you probably updated the su binary and/or the supersu that was included in the root kit published here. Don't update either. Something about the latest Supersu causes this. Just leave reflash the phone using Sony recovery app to stock. Then start all over. Phone will work fine. Don't update Supersu.
Hi,
First I apologise for not having made a back up of my filesystem, I had grown overconfident from previous successful projects ;-/
I have unlocked the phone and installed TWRP recovery. I then used SUPERSU to root the phone under TWRP. After SUPERSU the phone did not boot, it stayed on the WARNING BOOTLOADER UNLOCKED splash for over an hour and did not boot after a reset.
I read through the forums and looked for a kernel to try as I had read that the OS may be damaged, and I wanted to flash a ROM in any case. I read to clean the boot partition before flashing so I did this. The kernel I tried was Squid. This made the phone display "fall through from normal boot mode". So I tried Cyanogen Mod 14, which put the phone on a very rapid bootloop cycle (about every 15 secs), then tried Squid Kernel R22B which put the phone on a long (about 8 minute) bootloop cycle.
Not sure what else I can do. I don't want to give up on the phone as it still mostly works (it has a bootloader, recovery and a file system). I have tried to find a stock ROM to install but proving difficult to track down - links seem to be down)
I apologise if I have got any technical terms wrong. I hope you can help!
Thanks,
Caroline
Caroline300 said:
Hi,
First I apologise for not having made a back up of my filesystem, I had grown overconfident from previous successful projects ;-/
I have unlocked the phone and installed TWRP recovery. I then used SUPERSU to root the phone under TWRP. After SUPERSU the phone did not boot, it stayed on the WARNING BOOTLOADER UNLOCKED splash for over an hour and did not boot after a reset.
I read through the forums and looked for a kernel to try as I had read that the OS may be damaged, and I wanted to flash a ROM in any case. I read to clean the boot partition before flashing so I did this. The kernel I tried was Squid. This made the phone display "fall through from normal boot mode". So I tried Cyanogen Mod 14, which put the phone on a very rapid bootloop cycle (about every 15 secs), then tried Squid Kernel R22B which put the phone on a long (about 8 minute) bootloop cycle.
Not sure what else I can do. I don't want to give up on the phone as it still mostly works (it has a bootloader, recovery and a file system). I have tried to find a stock ROM to install but proving difficult to track down - links seem to be down)
I apologise if I have got any technical terms wrong. I hope you can help!
Thanks,
Caroline
Click to expand...
Click to collapse
Assuming you've the Lineage 14 zip in your internal storage or micro sd,. Enter TWRP, select wipe, advanced wipe, check system data cache and dalvik, swipe to wipe. Now you've clean wiped your phone.
Then go "install", select the Lineage zip and flash it.
Hi DroidFreak32, thank you for your help. The phone is now booting for the first time since it's "adventure".
Hi,
Unfortunately the phone is still in the boot logo screen. It stayed on the Lineage logo for 2 hours. I have powered off and rebooted once more, and it is still in the boot logo screen now (1 hour later). I'll wipe and install again and post an update.
Hi,
I reflashed Lineage, same problem. I did notice that each time I installed a zip file, SUPERSU asked me to install it prior to reboot to root the phone and I have always hit Yes. On the final flash, I powered off the phone when it prompted me to install SUPERSU, and the phone booted normally. Very nice design on the mod, I like the way the apps are displayed alphabetically. Good work Lineage Team!