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.
Related
Hi guys, I got a SGS2 just over a week ago, on Bell/Virgin network in Canada. Suffered from the battery drain issue due to being stuck with crappy UGKG2 firmware which my provider still hasn't updated.
I decided to update it myself, and did a ton of research. I successfully got Root tonight by flashing CF-Root-SGS2_ZS-OZS_KG2-v4.1-CWM4 kernel with Odin. In case it matters, I did NOT flash back my stock Kernel, so I still had the insecure kernel installed. From there, I backed up my apps with Titanium.
Went into CWM and selected boot into CWM Recovery. I followed the steps on the wiki, including creating a backup file. My only hint of what I might have done wrong was I originally selected to flash update.zip, and that process failed. I then went to the directory in which cyanogenmod is stored on my SD card, and selected that, then it installed ok. I had downloaded update-cm-7.10-GalaxyS2-signed and that's what I put on the phone. I then also installed the Google Apps.
I then hit reboot, and it only goes to the Samsung screen with the yellow triangle and just hangs there for a few minutes. Not knowing what else to do, I popped the battery out. I have since learned that I can turn it on and off, but it never goes past that screen. Wouldn't go into the recovery or download modes, always that screen. Luckily, I saw somewhere to do the 3 button thing WHILE in that screen, and that works. So I can get to recover, and download modes. So, I think I'm ok. I checked, and it does connect to Odin still.
I just want to know EXACTLY what I should do at this point. I don't want to fully brick it. There are actually two recovery files on the phone... not sure why... Or which one to pick. Should I just flash stock firmware back with Odin? One of my main goals is to get off 2.3.3 so I can have more than 8 hours of battery...
Thanks,
Rob
Boot into tecovery, do a full wipe again. (Wipe data/factory reset, wipe cache partition, advanced>wipe dalvik cache).
Now install CM7 zip twice in a row without reboot. It may take a few minutes for reboot since system is rebuilding dalvik cache. Be patient. After you see the home screen, reboot again.
Sometimes, CM won't install properly with CF root recovery. In that case reboot into download mode, flash codeworkx cwm kernel via ODIN.
http://forum.xda-developers.com/showthread.php?t=1118693
Now reboot into recovery and do full wipe and twice-install !
Ok, working now with the flash twice thing. Well that's weird, would be great if it was in the wiki page...
Thanks!
Rob
So last night I rooted my phone using the All in one toolkit. Flashed hyperdrive rom and after getting everything setup I went to bed.
Some apps were kind of freezing this morning so I tried to boot into recovery and it wouldn't let me. It shows the loading recovery at the top then it just boots my phone up. The only way I can get into Recovery atm is by using the all in one toolkit. Anyone had this issue before? I wipe cache, dalvik, and fixed permissions. Still can't boot into recovery without the toolkit.
if you can get into recovery by typing adb reboot recovery in cmd then maybe your finger may be slipping when holing the buttons to boot into recovery.
bmbrad said:
So last night I rooted my phone using the All in one toolkit. Flashed hyperdrive rom and after getting everything setup I went to bed.
Some apps were kind of freezing this morning so I tried to boot into recovery and it wouldn't let me. It shows the loading recovery at the top then it just boots my phone up. The only way I can get into Recovery atm is by using the all in one toolkit. Anyone had this issue before? I wipe cache, dalvik, and fixed permissions. Still can't boot into recovery without the toolkit.
Click to expand...
Click to collapse
Hold power + volume up, right when you feel it vibrate, let go of the power.
Yeah I tried all that. I ended up having to wipe everything and flash my first back up when i rooted my phone.... Thanks for the help thought.
I have the same issue. Stock, rooted, TWRP... I can use adb reboot recovery, but using the hardware buttons doesn't work. Any help is appreciated!
First off I am on mdk and rooted and up until today have been running hd 10.2. I had been having some weird things happen with twrp 2502 so I went into goo and tried to update to the newest version of twrp. it downloaded and went through with everything and I rebooted into recovery. once I got into recovery it was showing I was still on 2502, but it was asking for a password which I had never seen before. I backed out and tried to boot into my rom again and it got stuck on the samsung custom screen. pulled the battery a few times and still kept getting stuck. went back into recovery and tried to restore a known good backup that I had restored before, but it keeps failing. I had rls12 on my phone so I tried installing it dirty since I cant wipe anything due to the whole password thing in twrp which said it was succesful but still gets stuck on the samsung custom screen. it sits there for about 10 seconds and loops. I tried about 10 more times to get my backup restored and it finally finished and booted into the rom. I left it this way for an hour or so and did some stuff with my phone, tried to update twrp again which did the same thing again and still shows 2502. after the reboot I am back to the same problem of not being able to do anything in twrp except restore or dirty flash, I cant get the usb to mount in twrp so I cant try putting another rom on the phone unless I go and buy a micro sd adapter.
I am in the process of downloading a stock mdk rom to try and flash in odin, but is there anything I can try before I go through with this, or is it pretty much my only option.
after some more research I think I figured out what caused all this. I wiped the data partition with the old version of twrp which screwed it up pretty bad. Apparently the older versions of twrp were known to have this problem. I kept trying to restore, but trying to restore kept failing on the data partition. After about 25 attempts of trying to restore just the data partition I was able to get it to work finally, and then I restored the the others and got it to boot back into the rom. like an idiot I rebooted the phone back into recovery after it finished and had the same problem again. another couple hours wasted trying to restore the data partition and it worked again and this time i was able to get twrp to update and then went back to recovery and formated the data partition again and it seems to have fixed the problem. Now to figure out why hd rls 12 wont install.
Hi all,
New to this whole rooting and flashing thing. I'm not as good with computers that one can hold in their hand.
Anyways, I'll try to explain this stew of issues that I have
I'm running CW Recovery (6.0.2.3) in conjunction with SlimBean (dtt 4.2.2). One day, in a far away land, my phone prompted me to update Slim. That was all and dandy because I've flashed roms from zip files before. When I tried to do that, the process was aborted and I was given a slew of error numbers that made my brain hurt.
So, I tried to start fresh and clean, like the cilantro that chipotle puts in our burrito bowls. I tried a factory reset using the CW Recovery mode so I can re-root now that jellybean is 4.3. After I wiped the cache and data/factory reset, I rebooted the phone. My phone still boots into Slim and uses clockwork for recovery mode.
Essentially, how do I de-root my phone or factory reset it to the settings that I had from day 1?
UPDATE: I just tried flashing CW Recovery from 6.0.2.3 --> 6.0.4.7. After flashing it, I rebooted my phone into recovery. Now I'm getting a never-ending boot cycle. The samsung logo pops up along with the little blue text "recovery" at the top, then shuts off and repeats that every 3 seconds or so. Methinks I broke it
Thanks
Flash stock ROM via Odin. Download [URL="http://www.sammobile.com l" ] Sammobile [/URL]
Edit: better url
Why download a flight simulator?
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