Hi!
I'm moving my first steps into Android modding: I've succesfully installed Cyanogenmod on my Xperia U and then started to play with my Xperia S. That's what I did on the S:
- unlocked bootloader (with Sony official procedure)
- copied ROMs into phone
- flashed TWRP 2.8.0.1 using flashtool (fastboot mode)
- started phone in recovery, wiped, installed ROM/Gapps, reboot.
All seems to work fine: the phone boots correctly, system configuration and all, except that when I reboot it, on the next start it stucks on boot on Sony logo.
The phone is recognized by flashtool and I can still enter recovery, so I can't say it's bricked, but it doesn't start the OS!
I've tried different ROMs, Android 4.4.4. and 5.0.2, but the result is the same: all working fine until the phone is rebooted, then stuck. Sometimes it happens just after installing the ROM, other times later, after installing other apps (it always happens if I try to recovery app backups with Titanium backup, for example).
Can it be a TWRP problem?
Any ideas or help will be high apreciated! :fingers-crossed:
ZeligPC said:
Hi!
I'm moving my first steps into Android modding: I've succesfully installed Cyanogenmod on my Xperia U and then started to play with my Xperia S. That's what I did on the S:
- unlocked bootloader (with Sony official procedure)
- copied ROMs into phone
- flashed TWRP 2.8.0.1 using flashtool (bootloader mode)
- started phone in recovery, wiped, installed ROM/Gapps, reboot.
All seems to work fine: the phone boots correctly, system configuration and all, except that when I reboot it, on the next start it stucks on boot on Sony logo.
The phone is recognized by flashtool and I can still enter recovery, so I can't say it's bricked, but it doesn't start the OS!
I've tried different ROMs, Android 4.4.4. and 5.0.2, but the result is the same: all working fine until the phone is rebooted, then stuck. Sometimes it happens just after installing the ROM, other times later, after installing other apps (it always happens if I try to recovery app backups with Titanium backup, for example).
Can it be a TWRP problem?
Any ideas or help will be high apreciated! :fingers-crossed:
Click to expand...
Click to collapse
After flashing ROM, the phone will seem to be stuck at Boot Animation for 10-15 minutes. It is not stuck and normal. Let it boot, it will come to home screen eventually. During second boot, it will seem to be stuck at Sony logo, but this is too normal. It will take approx 10 minutes here too.
Mirhawk said:
After flashing ROM, the phone will seem to be stuck at Boot Animation for 10-15 minutes. It is not stuck and normal. Let it boot, it will come to home screen eventually. During second boot, it will seem to be stuck at Sony logo, but this is too normal. It will take approx 10 minutes here too.
Click to expand...
Click to collapse
Wow. Thank you Mirhawk! I knew about long boot animation at first boot, but never heard about the second (or later) one "stuck" at Sony logo! Waited 10 minutes and then the phone wake up! :good:
Thank you again.
Related
Hello,
I have a great problem with my Motorola. I installed battery icon mod without reading for which phone it's made and used it. Now I can't use my phone, because it's stopping at this logo before system. I had Cyanogenmod 7 (last nightly before RC), but when I destroyed it by this application first thing I did was wipe. After it nothing has changed, so I tried again and I flashed it with normal 2.2 Nordic but - as I "predicted" - nothing has changed again, but this time system was stopping at Android logo, not Cyanogenmod logo. I tried to flash again - nothing. The device can be charged (there appears this battery).
What should I do?
zielonek430 said:
Hello,
I have a great problem with my Motorola. I installed battery icon mod without reading for which phone it's made and used it. Now I can't use my phone, because it's stopping at this logo before system. I had Cyanogenmod 7 (last nightly before RC), but when I destroyed it by this application first thing I did was wipe. After it nothing has changed, so I tried again and I flashed it with normal 2.2 Nordic but - as I "predicted" - nothing has changed again, but this time system was stopping at Android logo, not Cyanogenmod logo. I tried to flash again - nothing. The device can be charged (there appears this battery).
What should I do?
Click to expand...
Click to collapse
Go into the stock recovery and wipe data. Then re-flash the sbf.
I did it already, but I forgot, that I can do wipe after flashing the device I thought about it and did it - everything is working. Sorry for useless thread.
Regards.
I wanted to ask at the same time. What if i can't enter stock recovery. My phone's rooted , slightly overclocked , and i can't download any apps , i can't do factory reset , and even when i'm trying to enter it , the android pic would appear with that "danger - triangle". What should be done?
sLvW said:
I wanted to ask at the same time. What if i can't enter stock recovery. My phone's rooted , slightly overclocked , and i can't download any apps , i can't do factory reset , and even when i'm trying to enter it , the android pic would appear with that "danger - triangle". What should be done?
Click to expand...
Click to collapse
The triangle IS the stock recovery! when you see the triangle with the little android dude, hit both up and down volume at the same time. This will bring up a menu that will allow you to do a factory wipe.
And another question. I've installed custom recovery , and it said that install was succsesful , but when I apply recovery boot , it just reboots my phone , or lefts screen blacked out, at which case i have to turn on my phone by removing and applying battery.
sLvW said:
And another question. I've installed custom recovery , and it said that install was succsesful , but when I apply recovery boot , it just reboots my phone , or lefts screen blacked out, at which case i have to turn on my phone by removing and applying battery.
Click to expand...
Click to collapse
Not sure I understand the questions, but I'll take a stab at it anyway:
Since we have a locked bl, the custom recovery does not overwrite the stock recovery.
As far as I know, the only way to get in to custom recovery, is to push the vol down when the blue light goes on during the boot cycle.
sLvW said:
And another question. I've installed custom recovery , and it said that install was succsesful , but when I apply recovery boot , it just reboots my phone , or lefts screen blacked out, at which case i have to turn on my phone by removing and applying battery.
Click to expand...
Click to collapse
If it was a first reboot after installing Custom Recovery than USB Debbug should be off...
I was trying to install AuroraPlay 1.1, everything was going fine, i unlocked my bootloader, installed doomkernel, booted it up and it was fine until then. Then i followed the next installation steps (factory reset, format system, and flashed the rom, did it all on Clockwork mod) and now the Xperia logo keeps looping. I can't enter recovery, the phone doesn't vibrate like it did before on the doomkernel screen and no matter what i press it just goes to the logo again
I'm pretty new to all this so i suppose i just made a common stupid mistake. Flashtool seems to still recognize my phone when i connect it in flash mode, but not for long, it disconnects itself and reconnects again but not in flash mode. Can i save my phone?
After removing the battery many times, and trying again and again, it booted into AuroraPlay
Everything looked normal, so i turned it off and on again to see if it was fixed, but it's looping again, and i still can't acess recovery
I can't think of anything i did differently when it booted successfully
Start from begining again:
-flash stock firmware and see does it boot up
-reflash doom kernel again, if you can enter fastboot mode (hold search when pluging in usb)
-boot rom again, to see if stock rom can boot up with doomlord kernel
-if you can, reset to recovery(keep pressing back button), format data and system and install Aurora again
If you manage to boot to (any) rom, check your sd card for errors, if any...
Around half an hour after my last post, i left my xperia looping for like 10 minutes to see if anything changed, then took out the battery and booted it up again
this time i managed to go into recovery, but didnt want to flash everything again so i just applied the doomkernel v14 wifi fix that i couldnt apply before
it then booted into the rom normally and i've been using it since without a problem
kinda afraid to reboot though
Hello to all
I have Samsung Galaxy Nexus 4.2.1 stock and unlocked.
It worked perfectly to two years! From yesterday i have problem with it! My GN won't boot anymore, I can see just google and X (nexus) logo after that GN restart itself! This is repeated without stopping until I put out battery.
I have tried to clear cache, wipe data/factory reset in Recovery Mode but problem has continued!
I have unlocked bootloader and update to android 4.3 stock (non rooted) through ADB (google SDK), updated successfully but when phone has reboot problem has continued, GN restart non-stop!
In Fastboot mode/Recovery Mode phone it never restarted! I have left in this mode with hours to try if restarted but no It works without any problems in this mode! It restart only when phone boot up!
Can this problem to be hardware failure or not?!
Can anyone help me? What can i do to boot my GN again?
I hope in your your support
visar.r said:
Hello to all
I have Samsung Galaxy Nexus 4.2.1 stock and unlocked.
It worked perfectly to two years! From yesterday i have problem with it! My GN won't boot anymore, I can see just google and X (nexus) logo after that GN restart itself! This is repeated without stopping until I put out battery.
I have tried to clear cache, wipe data/factory reset in Recovery Mode but problem has continued!
I have unlocked bootloader and update to android 4.3 stock (non rooted) through ADB (google SDK), updated successfully but when phone has reboot problem has continued, GN restart non-stop!
In Fastboot mode/Recovery Mode phone it never restarted! I have left in this mode with hours to try if restarted but no It works without any problems in this mode! It restart only when phone boot up!
Can this problem to be hardware failure or not?!
Can anyone help me? What can i do to boot my GN again?
I hope in your your support
Click to expand...
Click to collapse
Don't panic, this problem is called bootloop and it's normal. Just download factory images from here and flash them by using this awesome guide by efrant!!
Also bookmark this link for future reference.
http://forum.xda-developers.com/showthread.php?t=1812959
started having the same problem yesterday after 6 months of stability on a custom 4.3 rom.
oem lock then unlock to format, nothing, tried various methods of flashing back to stock via ADB with mixed results, normally more boot looping with it occasionally booting into a rom for ~5 seconds. so SOMETHING is working.
I tried Efrant's method about an hour ago, but its been sitting at the google logo since, I'm at a lost, I'm no stranger to boot loops when installing borked roms but this is the strangest problem I have ever had with an android device.
should I just chock it up to hardware failure?
Mostly yours USERDATA partition is corrupted.
Use FASTBOOT to reflash the USERDATA IMG and it should do the trick.
Sent from my Galaxy Nexus using xda app-developers app
did a total stock reflash again, got to the setup screen before it rebooted after ~15 seconds, bootlooping again. flashed the userdata img with a few different ones.
I'm trying to read my logcat but when I run the ADB command in clockwork It finds nothing.
I've done all steps by this awesome guide by efrant! But same problem here
I've tried to install 4.2.2 stock, 4.3 stock, all comands works but in the end when i press fastboot reboot my nexus it's in bootloop again restart restart and restart
Any other solutions :crying::crying::crying:
I've waited about 30 minutes after restarting non-stop, my GN boot to system i saw home screen of android but after 5 sec restarted again :crying:
I'm getting into my system once every 10 or so reboots. managed to turn off wifi in case that was the problem but still boot looping. I'm inclined to think it might be hardware related as I started having trouble in the middle of a text after several months of rom stability.
Hello,
My Xperia z1 compact is not able to boot to recovery anymore. I have installed cm11 nightly build from 9th mai 2014. Yesterday i tried to update with cm-updater, but after it successfully downloaded the rom, my z1 compact just rebooted but did not enter recovery. So no update was performed. After that I tried to enter recovery-mode manually, first with SleepandWake -> Restart -> Recovery and after that from PowerOff with "PowerOn and VolumeUp". My Phone always boots the normal system. Also the LED-light is missing. Normally it lights purple and orange while booting Recovery, but since yesterday it stays off while booting.
Howerver, booting into bootloader is still possible. The blue light is on while in bootloader.
I bought it a while ago in February, I think and it is running CM11 since the first Day and I do my updates twice a week.
Does anyone know about that problem? How could this happen? And what can I do to update my Smartphone?
Any hint is appreciated.
Thanks
Kind Regards
1003
Reflash the kernel with fastboot.
[solved] issue
zxz0O0 said:
Reflash the kernel with fastboot.
Click to expand...
Click to collapse
Hello,
that solved my problem. But I am very curious how this could happen.
Thanks anyway!
Kind Regards
1003
Hi,
same problem here but other rom.
My Z1C ist rooted and on 4.4.2 (14.3.A.0.757) Stock. (Something with generic DE).
Sorry, i am not so familiar with this.
Now I can't enter the recovery menu anymore. On booting the phone a red led flashes (instead of a green one while rooting process).
When a app tries to "boot to recovery", the phone normally boots android.
I have tried the install.bat in Z1C-lockeddualrecovery2.7.123-BETA.installer.zip and choose option 1 "rooted with SuperSU".
Scripts runs through but when phone reboots, only android starts.
Could i try to flash the kernel new or would i loose my root?
If your bootloader is locked you need to start again from the beginning of the guide. The above solution is only for unlocked bootloader.
Hi,
When i use my 5x for a hour or so, then try to reboot it, it stucks at the google logo. When i restarted with the physical button, its usually starts, but not always. There was a time when i couldn't make it work for at least 30minute, then i waited a hour and it started finally.
Every time when i stucked at google logo, i'm able to get to twrp. Tried with stock rom, locked bootloader, stock recovery too, but its same. When i use it for a long time and its get hot, its stucks at google logo when restarting.
But it never restarted automatically. I can use it for 10hours if i want, just if i restart it, its stucks.
Is it because faulty motherboard or what do you think?
Because it dont stuck forever, and i can access recovery mode.
That's probably some random issue, the BLOD happens like this:
You do your stuff on the N5X,
everything freezes for several seconds,
phone restarts itself and doesn't get past google logo,
can't access recovery, however you can access bootloader, which is very laggy,
starting up again is nearly impossible, you can hold the button for an hour and the phone won't even get to the google logo.
ZLevente said:
Hi,
When i use my 5x for a hour or so, then try to reboot it, it stucks at the google logo. When i restarted with the physical button, its usually starts, but not always. There was a time when i couldn't make it work for at least 30minute, then i waited a hour and it started finally.
Every time when i stucked at google logo, i'm able to get to twrp. Tried with stock rom, locked bootloader, stock recovery too, but its same. When i use it for a long time and its get hot, its stucks at google logo when restarting.
But it never restarted automatically. I can use it for 10hours if i want, just if i restart it, its stucks.
Is it because faulty motherboard or what do you think?
Because it dont stuck forever, and i can access recovery mode.
Click to expand...
Click to collapse
I had the same issue when I flashed the newest bootloader version (bhz31b). Issue resolved when I reverted to bhz31a.
Wakamatsu said:
I had the same issue when I flashed the newest bootloader version (bhz31b). Issue resolved when I reverted to bhz31a.
Click to expand...
Click to collapse
Thanks, i'll try bhz31a thanks
(I'll write in some days if it worked or not)
Wakamatsu said:
I had the same issue when I flashed the newest bootloader version (bhz31b). Issue resolved when I reverted to bhz31a.
Click to expand...
Click to collapse
Which bootloader is bhz31a? I tried the bootloop fixes, none worked. Only have access to bootloader, no recovery.
edit: i see bullhead-opm1.171019.011-factory-3be6fd1 has the bhz31a bootloader. I tried this, with no luck on my end. Even with the 4core modified recovery/boot. I must have one of the unfixable BLOD.
I tried that bootloader too, same
My phone can boot, just sometimes it's stucks at google logo, but i can access recovery every time, even if it's stucked at google logo.
Usually every 2. reboot stucks.