Alright, Here's the scenario : My phone was working fine, I tried installing the DoCoMo SystemUI here and the All-in-One add-on, Installed normally, cleared cache & dalvik, rebooted, the boot animation plays for a few seconds, it freezes and then the phone restarts. I tried clearing data, then re-installed the JB rom, then i cleared System, Data, Cache, .android_secure and even SD Card (basically everything except ext. SD) then installed CM10.1 from recovery and still the same thing, Bootlooped at boot animation.
And the phone won't charge offline normally, it charges for a while (like 10 seconds) then it starts itself and get into the bootloop.
As formatting everything and installing again didn't help, I don't think FlashTool will, but I'm downloading the 9.1.A.1.140 FTF now and I'll try it tomorrow (slow internet).
Is it possible that the phone is hard-bricked and can't be rescued? If not what else can I do to bring it back to life?
If it was hard bricked it would not boot at all, it would be totally unresponsive (Just like a brick)
Were you on cm10 before?
If so you you cant install those stock based add ons, you should be able to restore your backup. What happens when you do that? (You did make a backup didnt you? Always backup just in case it f**** up!)
If you were not on cm10 before then you need to have an unlocked bootloader to flash cm10, make sure you have unlocked.
gregbradley said:
If it was hard bricked it would not boot at all, it would be totally unresponsive (Just like a brick)
Were you on cm10 before?
If so you you cant install those stock based add ons, you should be able to restore your backup. What happens when you do that? (You did make a backup didnt you? Always backup just in case it f**** up!)
If you were not on cm10 before then you need to have an unlocked bootloader to flash cm10, make sure you have unlocked.
Click to expand...
Click to collapse
I don't have a backup, but would it matter because it only backs up data, system, cache, and .android_secure and I formatted all of them and did a clean install of both official JB and then CM10.1, Same thing for both. That's why I'm scared, I did a clean install but it still bootloops. (OFC my BL is unlocked)
AliAlsuhail said:
I don't have a backup, but would it matter because it only backs up data, system, cache, and .android_secure and I formatted all of them and did a clean install of both official JB and then CM10.1, Same thing for both. That's why I'm scared, I did a clean install but it still bootloops. (OFC my BL is unlocked)
Click to expand...
Click to collapse
a backup backups everything.
You have yet to tell me which rom you were on, informtion like that will help me help you. Please answer all my questions
which kernel is currently installed on your phone?
YES! FlashTool has fixed it!
And I was on stock rom and DooMKernel at the moment of installation.
Related
Hello!
Today, i decided to install cyanogemmod on my 2x. So i downloaded ROM manager and downloaded cyanogenmod. everything went fine until i was going to boot for the first time. I got into a bootloop. so i tried taking out the battery and all that stuff but it still would't work. So i tried to recover the phone. I recovered it to a month old backup (I could not find the one i made in ROM manager before i installed cyanogenmod) The recovery went fine. But, when i rebooted it got into a loop on the lg logo! (the one without the loading bar) it would just load the lg logo, be there for like 10sec, then it would do the same. I tried recovering one more time, but it didn't work. The same thing happend. What should i do? :S Should i wipe data/factory reset?
EDIT: My phone was on android 2.3.4 before i download cyanogenmod.
BTW before i installed cyanogenmod, i forgot to clear cache and data. I was in a hurry so i did't notice the screen popping up, I automatically pressed "ok" without selecting anything.
Thanks for the help
- Kashif
Different partitions... Look for something called backtoext3 in the dev section (or somewhere else) The problem is that when you flash a custom rom like CM you convert your filesystem to EXT4, while stock is EXT3.
So basically what you have to do is:
1) Reboot into recovery
2) Wipe everything
3) Flash Backtoext3 zip
4) Restore Nandroid.
This should work. this will take you back to stock.
So i have to restart the phone, Choose wipe data/factory reset, then flash backtoext3 (how do i do it? lol) then restore nandroid (the backup i just tried to restore twice?)
kashi169 said:
So i have to restart the phone, Choose wipe data/factory reset, then flash backtoext3 (how do i do it? lol) then restore nandroid (the backup i just tried to restore twice?)
Click to expand...
Click to collapse
Yes
Flashing backtoext3 is just flashing the zip file you put on the sd card. (and then install zip from SD ) an then restore your nandroid stock backup and you're back on stock.
But you said you wanted to try CM right? In that case, wipe everything (factory reset/data + cache + dalvik) and then flash the CM7 rom and you have CM! Don't worry about backtoext3, your partitions are already on EXT4, because of your prior CM flash.
Ohh! Thanks Can you send the files for cm (2.3.4)? I've found some, but im not sure if my phone is compitable with them :S im really afraid to mess something up again
My. Signature. (CM7 temasek's KANG = the best CM7 at the moment )
I did everything and i got into a bootloop at the skating andriod screen again
OK, restored my phone back... Now it wont connect to the network and the battery has a question mark inside it. It also says the battery level is 999% heelp
Nvm, got my phone back to normal still dont understand why cm wont work...
You need cwm5 to flash cm.
I have a G2x, which is basically the same phone. But anyway, I would recommend nvflashing CWM and not getting it from ROM Manager.
CWM 5.0.2.0 will do just fine, but it is indeed old...
Anyway, are you sure you waited long enough on the CM boot screen? The first boot might take a couple of minutes. (4 or 5)
Hey,
I have been using CM10 Paranoid Android since it came out on the Note, I am on 2.51 version.
Yesterday my SD Card wouldn't mount so I rebooted the phone, after the reboot it got stuck on the animation (Jelly Bean Android). So I rebooted it again and this time it booted, but every application was 'Not Responding' I couldn't even get to the lock screen.
Ever since then I can't boot it up it stays on the Jelly Bean Man animation. Keep in mind I didn't install any apps, I didn't update the Rom since it came out ( a few months ), it just randomly stopped working.
I am wondering what to do.
Thank you.
Start with cleaning cache and dalvik cache in your recovery.
ThaiDai said:
Start with cleaning cache and dalvik cache in your recovery.
Click to expand...
Click to collapse
Did that, still no success.
mikus123 said:
Did that, still no success.
Click to expand...
Click to collapse
If you have a backup of your Rom (made in recovery) and/or backups of your Apps (made with Titanium Backup):
Factory reset and reinstall this Rom or install another (JB stock) Rom.
If you do not have backups:
Factory reset and reinstall this Rom or install another (JB stock) Rom.
And be sorry, that you didn't make backups.
ThaiDai said:
If you have a backup of your Rom (made in recovery) and/or backups of your Apps (made with Titanium Backup):
Factory reset and reinstall this Rom or install another (JB stock) Rom.
If you do not have backups:
Factory reset and reinstall this Rom or install another (JB stock) Rom.
And be sorry, that you didn't make backups.
Click to expand...
Click to collapse
Do you have any idea what happened? It was so spontaneous. I have a back up of the ROM, however it was before I installed APPS, and TB didn't work on my phone so I could never back them up.
So factory reset is the only way?
mikus123 said:
Do you have any idea what happened? It was so spontaneous. I have a back up of the ROM, however it was before I installed APPS, and TB didn't work on my phone so I could never back them up.
So factory reset is the only way?
Click to expand...
Click to collapse
If TB never worked there was already something wrong with your configuration.
No, I don't have an idea what could be wrong - only hoping that it isn't a hardware problem.
Yes, that's why I would install a stock JB rom with PC Odin first: if this succeeds you'll have working configuration again - if if fails we can analyze the errors in PC Odin.
Hello xda community,
First I have to say I'm french so sorry for my english
I really need your help. I've bought that phone TWO days ago and it already doesn't work. Lemme explain:
- I used DooMLoRD method to Root and install CWM (C5303 model with locked bootloader).
- I installed Xperia Pureness. Wiped System, Cache, Dalvik... It worked fine.
- But i after a few hours Home button didnt work eek so I decided to reflash the rom to reload the System UI. As I used to do with my HTC Sensation, i only wiped dalvik cache and cache for the 2nd flash (ERROR). I realised after have rebooted that i should have had wiped System too.
- It didnt boot since this 2nd flash.
- I've been trying to repair it for this ENTIRE day, nothing happens (pressed red button 5 secs, 10 secs, also tried to reflashed stock .254 ftf with FlashTool...), still can't access Home...
Can you devs find a solution? I really need to repair my phone, bought it 2 day ago :crying:
PS: it doesn't matter if i loose data on my phone
Reflash ROM and dont wipe cache and dalvik If that does not work you need to restrore the backup you made, or you can restore it with my easy restore guide i just made
mrjraider said:
Reflash ROM and dont wipe cache and dalvik If that does not work you need to restrore the backup you made, or you can restore it with my easy restore guide i just made
Click to expand...
Click to collapse
Thanks for the quick reply.
I'm always on bootloop, so can't even access CWM, is it still possible to flash a ROM, or access CWM? I've tried something like 10 times to reinstall stock ROM with FlashTool, still stuck at bootscreen.
I didnt think about making a backup
NaStolgiiK said:
Thanks for the quick reply.
I'm always on bootloop, so can't even access CWM, is it still possible to flash a ROM, or access CWM? I've tried something like 10 times to reinstall stock ROM with FlashTool, still stuck at bootscreen.
I didnt think about making a backup
Click to expand...
Click to collapse
If you follow this guide i made: http://forum.xda-developers.com/showthread.php?t=2476938
You will recover your device with an official Sony tool
After that you can try it again. Since im not into flashing custom ROMS at the moment i cant help you futher with it ( just being honest )
It was long... BUT IT WORKED !!
Thanks a lot !!!!
It was long... BUT IT WORKED !!
Thanks a lot !!!!
i recently flashed the eXistenZ Ultra 2, and im sure i did everything fine, after flashing the rom in recovery and flashing suprsu and wifi fix, i powered off the phone, and powered on but sony logo has apeared until now , and welcoming`s sounding 999..times. i cant turn it off, or i should say i cant do anything.
please help,
After flashing ROM and the fixes you should flash the 12.1.A.0.266 Firmware with FlashTool!
If problem still persists:
http://xda-university.com/as-a-user/how-to-recover-from-a-bootloop
Take a look at this site A recovery would be quite useful, but I think the kernel of eXistenZ ROM has one. If not, you'll find one in the development section. Otherwise, use the ADB as solution.
Good luck
Thanx for the post!
I used force shut down and then flash the 254 rom, and did all those things, and the problem occured again.
does the recovery software have to be the touch recovery? I use CWM v6 that enables with volume +.
and i use SuperSU fix.zip rather than superUser.zip and generally i flash rom, supersu fix.zip and wifi fix.zip. i flashed those three, before first booting, do i have to boot first before flashing wifi fix.zip?
eefathi said:
Thanx for the post!
I used force shut down and then flash the 254 rom, and did all those things, and the problem occured again.
does the recovery software have to be the touch recovery? I use CWM v6 that enables with volume +.
and i use SuperSU fix.zip rather than superUser.zip and generally i flash rom, supersu fix.zip and wifi fix.zip. i flashed those three, before first booting, do i have to boot first before flashing wifi fix.zip?
Click to expand...
Click to collapse
I think you need to flash 12.1.A.0.266 instead of 12.0.A.2.254 after flashing ROM. You could also wipe data, cache and dalvik cache, reflash eXistenZ ROM and SuperSU fix (or SuperUser but SuperSU should be ok), shut down the phone with the option in recovery and then flash the 12.1.A.0.266 with FlashTool.
It doesn't matter which recovery you take. Use the one you like best. I'm not quite sure, but to go sure, please flash the wifi fiz.zip after first boot up!
Schokonuss said:
I think you need to flash 12.1.A.0.266 instead of 12.0.A.2.254 after flashing ROM. You could also wipe data, cache and dalvik cache, reflash eXistenZ ROM and SuperSU fix (or SuperUser but SuperSU should be ok), shut down the phone with the option in recovery and then flash the 12.1.A.0.266 with FlashTool.
It doesn't matter which recovery you take. Use the one you like best. I'm not quite sure, but to go sure, please flash the wifi fiz.zip after first boot up!
Click to expand...
Click to collapse
thanx again,
i flashed the 266 kernel before the first boot, and the rom runs correctly,
but ive got some new problems:
1. performance, when i click on performance, it closes unexpectedly and says it has stopped.
2. i used go backup for backing up from data in 4.1, but in this rom i restored my apps,the apps installed correctly but goBackup says the data restoring successfully finished , but the data didnt restored, by the way at the time i backed up from my apps&data, i swapped memories with that linux code that this forum did.
eefathi said:
thanx again,
i flashed the 266 kernel before the first boot, and the rom runs correctly,
but ive got some new problems:
1. performance, when i click on performance, it closes unexpectedly and says it has stopped.
2. i used go backup for backing up from data in 4.1, but in this rom i restored my apps,the apps installed correctly but goBackup says the data restoring successfully finished , but the data didnt restored, by the way at the time i backed up from my apps&data, i swapped memories with that linux code that this forum did.
Click to expand...
Click to collapse
You're welcome
1. Do you have SuperSU installed? On AOKP ROM I'm running it asked for superuser permission for ROM Control (the control center implemented in the settings of the ROM). Maybe it'll ask you if SuperSU is installed. Otherwise, because it is after the first boot it needs to rebuild cache and so on.. If problem persists after reboot, just use an other clock speed controler (No-frills CPU, SetCPU..)
2. If you did that at the same time, maybe Go Backup didn't really backup your data. Try again, if it doesn't work and if you have a nandroid backup (backup from recovery) you can go into recovery, then to advanced restore and restore data. Otherwise your data is unfortunately gone I think :/
PS: I prefer Titanium Backup
I have Xperia Z3c 5.1.1 rooted with locked bootloader. It is on wifi only. Yesterday I've turned wifi on and suddenly have got device off. I tried to reboot. I see the Xperia logo and bluish Xperia start screen with waving elements. However, the home screen and apps are not appeared, have just black screen. The battery is fully charged (green led). I tried several times reboot today as well with the same result. I believe the phone is soft bricked.
The phone is rooted with NDR Utils and TeamWin Recovery (TWRP). I also have Titanium backup.
After reading this forum I found several ways to unbrick the phone:
1. Soft reset (Power + VolUP) up to 1 vibration.
2. Hard reset (Power + VolUP) up to 3 vibrations.
3.Use flashtool (flashmode) and flash ftf file. Should I flash Kernel as well?
4. Use phone System recovery (Power + VolDown).
Which method I should try first? Can I save root and my current Lollipop firmware or I should go and start from the scratch with rooting and flashing 5.1 again?
Thank you for your suggestions.
Try soft reset and hard reset. This don't break your phone but it is worth a try. If this will not work do NAND backup (full backup of phone) in recovery. Now you can try clear cache in TWRP (wipe -> advanced wipe -> check cache -> swipe to wipe). If this don't work try clear dalvik/art cache.
If this metods didn't work flash same rom (if rom was't pre-rooted root after flash). If system starts you can restore NAND backup without system partition and cache.
If system don't start after restore backup the last chance is clear rom flash.
I don't know where the problem is but in my place I would do that
Thank you krzysiek546 for your help.
I have tried soft and hard reset, both unsuccesful. I made backup and wiped cache and dalvik from within TWRP. The phone after apps optimization has started the system (there was black screen but I was able to see home and Back buttons, which were non-functional, i.e non-responsive.) The screen became black again after a few secs and did not return to the life then.
I think I'm going to flash the Rom. My question is there is any chance to get brick again in case I will restore from the TWRP backup (if there was a virus or something?). May be I should wipe data, cache and dalvik and only then made a backup?
Also, when you saying "a clear rom flash" as a last chance do you mean factory reset?
Thank you.
Don't wipe data before backup. This is like doing backup after format system. It doesn't make sense.
Have you tried this metod with flash with nand backup and flash same rom (zip from twrp or ftf from flashtool) and restoring data without system partition (it's important)? In this i mean something corrupted system files. In this metod you can save your data. You just reinstall system and restore data from nand backup.
When I sayed "a clear rom flash" i mean wiping all data in recovery and flash rom from flashtool or twrp without restoring anything. You can do it first. I think now it's beter because you can check did that fixed your problem and if this "clear rom flash" repair your problem you can restore data from backup.
As to your question. Yes you can get brick from restoring data from twrp but in my opinion this virus or something must have root permissions to do this.
After installing the newest supersu, I also get this bootloop. Is there a chance to undo this without wiping data?
Edit: ok, after hard reset, flashing SU, cleaning caches etc. (which all did not help) I reflashed the ROM, now it works again. Pheeew.
firox said:
After installing the newest supersu, I also get this bootloop. Is there a chance to undo this without wiping data?
Click to expand...
Click to collapse
Try to install SuperSU v2.81 - author apologized for inconvenience caused regarding 2.80 update. I got this bootloop too and solved it by installing SuperSU v2.81.
MATPOC said:
Try to install SuperSU v2.81 - author apologized for inconvenience caused regarding 2.80 update. I got this bootloop too and solved it by installing SuperSU v2.81.
Click to expand...
Click to collapse
When I had that error, it was still V2.80 and no update round the corner.
Thank you for the link. Worked great for me. Installed per TWRP.
Well, in my case I didn't updated SuperSU, just have turned on wifi. I think the problem may be in Wallpaper app I have installed previously. It changes wallpaper every day, but I noticed sometimes the background of my home screen where all apps are became black.
Anyway, only "clear rom flash" with wiping cache, dalvik and data helped me. I then installed pre-rooted Lollipop ROM I made before and restored all custom apps from the Titanium backup. BTW, don't try to restore system apps from the Titanium, I've got the error with Xperia keyboard and have to make a restore whole system from TWRP.
Thank you krzysiek546 very much for your help.
MATPOC said:
Try to install SuperSU v2.81 - author apologized for inconvenience caused regarding 2.80 update. I got this bootloop too and solved it by installing SuperSU v2.81.
Click to expand...
Click to collapse
I also got bootloop after installing latest SuperSU from Google Play.
How can I install 2.81 (or 2.79) when phone is in bootloop?