Sony Xperia Z2, locked bootloader, rooted SuperSU.
I was running MM but wanted to update my phone to latest Firmware .575 Marshmellow. Unfortunately, I made the rookie mistake of not making a backup because I was running low on space. Flashed, wiped cache/dalvik and then It went as far as home screen and then boot looped. I could only get into recovery TWRP.
Did a factory reset, clear cache/dalvik again. Nothing worked. Could only get as far as agreeing to terms screen and then boot loop.
Flashed an older firmware (.232) Lollipop that was pre rooted, same issue (don't know what I expected really)
Recovery is still there, I decided to just turn it off and ask someone because the internet is not giving me answers and I think I did enough damage. Please help!
Maybe too late, but..
What about when you wipe only cache and dalvik cache and flash again 575 zip and after that, flash bootloop fix, then restart phone to system from recovery menu?
Monipeev said:
Maybe too late, but..
What about when you wipe only cache and dalvik cache and flash again 575 zip and after that, flash bootloop fix, then restart phone to system from recovery menu?
Click to expand...
Click to collapse
I haven't tried the bootlop fix bit. I have tried this one though after going back to 570 and it still bootlooped. I'm back to 570 now.
Maybe a more stable flashable version will be revealed soon...one can only wait and see.
Related
As the thread title states...I was on 7.1 and downloaded/updated it to 7.2 Now the phone doesn't boot up and all I get is the Kernel Panic Upload Mode.
Anyway I can fix this? And if so, is there a way of doing it without completely formatting my phone and losing all my apps?
Oh and if it makes any difference I had to install that Siyah Kernel or whatever it was called to get out of the bootloop issue that I had with CM7.1. I'm thinking that that may be causing the problem....? But then again what do I know
wipe cache only.
valentinrascu said:
wipe cache only.
Click to expand...
Click to collapse
How? I've been trying [Power+Volume Up+Home] and it hasn't been doing anything. Can I do it through download mode somehow?
Had this problem when i flashed Lite'ning rom. Had to go into download and flash stock with odin. Took me a few tries to actually get the rom to work. As far as I know, that'd be your only option, seeing as recovery doesn't work for you.
take a deep breath and read, there is a very small chance of bricking your phone just so you know. Flash back original with Odin and start everything again
thanks for the replies...looks like i'm gonna flash the stock firmware back and see what i can do about getting to CM7.2 to work. hopefully flashing stock firmware is enough. I can't imagine how this would completely brick my phone and render it unusable.
As an aside...wtf is the point of this "recovery mode" when the thing doesn't even work half the time?
Anywho...downloading the stock .exe file now from here: http://devsrom4android.blogspot.ca/2011/10/samsung-galaxy-s2-firmwares-bell-canada.html[/url
Ok so I flashed the stock rom and now I'm in Android system recovery: Should I just reboot system now or do I wipe data/factory reset or wipe cache partition??
nubreed000 said:
Ok so I flashed the stock rom and now I'm in Android system recovery: Should I just reboot system now or do I wipe data/factory reset or wipe cache partition??
Click to expand...
Click to collapse
If you flashed stock, you should be fine just rebooting.
Its stuck on the boot screen. I tried just rebooting, then wiping/factory reset, then both wipes...reinstalled stock a few times and nothing worked each time. I'm suck on the Samsung Galaxy SII GT-I9100 screen
:-\...when I go into recovery, I get a ton of red messages/errors
I'm gonna try somethig other than stock firmware see if that helps.
edit Ok so I rooted the phone and it got past the first boot screen and now appears to be stuck on the "animated S" boot screen...progress!!
nubreed000 said:
thanks for the replies...looks like i'm gonna flash the stock firmware back and see what i can do about getting to CM7.2 to work. hopefully flashing stock firmware is enough. I can't imagine how this would completely brick my phone and render it unusable.
As an aside...wtf is the point of this "recovery mode" when the thing doesn't even work half the time?
Anywho...downloading the stock .exe file now from here: http://devsrom4android.blogspot.ca/...msung and their changes to Android framework.
Click to expand...
Click to collapse
Ok everything back to somewhat normal. Stock ROM didn't work but 2.3.6 did, so I'm on that. Now do I wanna go back to CM is the question...
Either way, thanks again for all the replies and helping me out with this. Greatly appreciated!
Hi I have attempted to install experience rom on my xperia U. Firstly i successfully unlocked the boot loader. I then rooted it and installed CWM recovery all still good. I the transferred the ROM image to the phone went into recovery did a wipe data factory reset and wipe cash partition. Also wipe dalvick cache. Selected the ROM and install started, it hung, only way out was battery pull, I went back into recovery same thing happened, finally tried once more and it hung at about 75%. Now phone goes in a loop sony logo to black screen and I cant get into recovery mode. I have searched to see if I can find a way out but not found a way around it yet. I would be very grateful for any help with this.
xs1m0nx said:
Hi I have attempted to install experience rom on my xperia U. Firstly i successfully unlocked the boot loader. I then rooted it and installed CWM recovery all still good. I the transferred the ROM image to the phone went into recovery did a wipe data factory reset and wipe cash partition. Also wipe dalvick cache. Selected the ROM and install started, it hung, only way out was battery pull, I went back into recovery same thing happened, finally tried once more and it hung at about 75%. Now phone goes in a loop sony logo to black screen and I cant get into recovery mode. I have searched to see if I can find a way out but not found a way around it yet. I would be very grateful for any help with this.
Click to expand...
Click to collapse
flash stock ICS Rom ftf with flashtool
Thanks for help
Thanks I managed to flash stock Gingerbread in the end.
In case anyone else has a similar problem here is a handy guide I found. (youtube.com/watch?v=hPPWRXcsz7g)
Where it says connect phone I found you need to connect it in fast boot (hold volume up button as you connect it) when the software is ready to flash un-plug phone then connect in flash mode (hold volume down button as you connect).
xs1m0nx said:
Hi I have attempted to install experience rom on my xperia U. Firstly i successfully unlocked the boot loader. I then rooted it and installed CWM recovery all still good. I the transferred the ROM image to the phone went into recovery did a wipe data factory reset and wipe cash partition. Also wipe dalvick cache. Selected the ROM and install started, it hung, only way out was battery pull, I went back into recovery same thing happened, finally tried once more and it hung at about 75%. Now phone goes in a loop sony logo to black screen and I cant get into recovery mode. I have searched to see if I can find a way out but not found a way around it yet. I would be very grateful for any help with this.
Click to expand...
Click to collapse
Flash stock firmware.
Install fastboot drivers.
Flash SlidingXU in cmd
Try out Zperience or TheBrainsRom following factory data reset, wiping cache and dalvik cache.
Hey guys,
I was just wondering what the general consensus is on which recovery is the most preferred.
I was using TWRP 2.6, but that gave me problems (being stuck on samsung logo everytime my phone rebooted). Reverted back to 2.5.0.2 and it seems to work fine so far. I did try CWM in the past but for some reason my boot loader would get locked and I would have to ODIN back to stock.
So what's your preferred recovery and why?
Thanks.
Exodus885 said:
Hey guys,
I was just wondering what the general consensus is on which recovery is the most preferred.
I was using TWRP 2.6, but that gave me problems (being stuck on samsung logo everytime my phone rebooted). Reverted back to 2.5.0.2 and it seems to work fine so far. I did try CWM in the past but for some reason my boot loader would get locked and I would have to ODIN back to stock.
So what's your preferred recovery and why?
Thanks.
Click to expand...
Click to collapse
I like TWRP. It works well with the new phone and Roms that are coming out plus it is so easy to use. Never liked CWM very much. You did right by reverting to an older version of TWRP I had to do that once.
TWRP... i don't even consider anything else.
Do you guys know why my phone gets stuck on the samsung logo everytime i restart my phone?
Doesn't matter what ROM i use it always happens....
Did you do a factory reset, system wipe, preload wipe, cache wipe, and dalvik wipe? Or try fix permissions from recovery?
If not, go do all of those.
If that doesn't work, something is missing from the system partition that is keeping it from booting. Which means you deleted it. :good:
Dubbsy said:
Did you do a factory reset, system wipe, preload wipe, cache wipe, and dalvik wipe? Or try fix permissions from recovery?
If not, go do all of those.
If that doesn't work, something is missing from the system partition that is keeping it from booting. Which means you deleted it. :good:
Click to expand...
Click to collapse
I did ALL of those, still have the problem.
So.... I just ODIN-ed back to stock and going to root and basically re-do everything -_-
My phone is rooted and i was going to flash xda framework, I have cm13 as my ROM and I used the advanced reset options to go into bootloader. I messed up and now i'm stuck with Cyanogen Mod recovery and can't get past OPX Logo boot screen. I tried to factory reset and wipe cache but nothing changed. Also my options are limited due to only having the cm recovery. I really hope someone has a solution,
Thanks!
carmelizing said:
My phone is rooted and i was going to flash xda framework, I have cm13 as my ROM and I used the advanced reset options to go into bootloader. I messed up and now i'm stuck with Cyanogen Mod recovery and can't get past OPX Logo boot screen. I tried to factory reset and wipe cache but nothing changed. Also my options are limited due to only having the cm recovery. I really hope someone has a solution,
Thanks!
Click to expand...
Click to collapse
Does fastboot still work?
Try this last resort might help. https://forums.oneplus.net/threads/g...plus-x.417648/
FIXED
I fixed the problem by flashing cm13 through the apply updates options under advanced, then flashing gapps all after wiping everything. Thanks anway
Cheers
Hi there
I'm totally happy with this device but had an issue today for no apparent reason.
I was using it normally, I put it in my pocket (80% battery) and when I took it out, it was stuck on MI logo screen. Maybe screen wasn't properly blocked or something. But I find all the situation quite shocking since I normally set manual updates for system, and apps, playstore, etc.
I haven't done any flashing opperation recently since I'm not much into this kind of things nor installed any new app recenlty. However the phone was rooted (previos bootloader unlocking) quite a while ago by using "magisk method keeping stock recovery for OTA".
The phone is permanently on with MI logo on screen. I tried using power off button for a long time to see if I could turn it off but it didn't work.
I have access to Fast Boot and to Stock Recovery (3.0).
Is there any way to enter the system again without losing all data? If not, can I recover data before "flashing" anything or before using "wipe all data" option in recovery mode?
Thank you for any possible answer.
Reinstall twrp and boot into twrp from Command Window and Flash Lazy flasher you'll be booted into Your phone
notoriouslion said:
Reinstall twrp and boot into twrp from Command Window and Flash Lazy flasher you'll be booted into Your phone
Click to expand...
Click to collapse
Thanks a lot mate, with this small guidance and not much idea about this things I flashed lazyflasher, wiped cache and dalvik (couldn't with stock recovery) and reboot into system.
Just out of curiosity, by flashing this lazyflasher have I done permanent changes on the system, or just through the first immediate boot they disappear?
What do you think could cause a bootlop if not an update? May an app installed a while ago causing something like this?
xdaforo said:
Thanks a lot mate, with this small guidance and not much idea about this things I flashed lazyflasher, wiped cache and dalvik (couldn't with stock recovery) and reboot into system.
Just out of curiosity, by flashing this lazyflasher have I done permanent changes on the system, or just through the first immediate boot they disappear?
What do you think could cause a bootlop if not an update? May an app installed a while ago causing something like this?
Click to expand...
Click to collapse
It happens sometimes for Unknown reasons and Lazyflasher will not harm your device and I would suggest you to flash Another Rom
xdaforo said:
Thanks a lot mate, with this small guidance and not much idea about this things I flashed lazyflasher, wiped cache and dalvik (couldn't with stock recovery) and reboot into system.
Just out of curiosity, by flashing this lazyflasher have I done permanent changes on the system, or just through the first immediate boot they disappear?
What do you think could cause a bootlop if not an update? May an app installed a while ago causing something like this?
Click to expand...
Click to collapse
Did you run any root apps ? If /system changes you need Lazyflasher I think. You could alternatively reflash the ROM (without wiping data)