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?
Related
This concerns my galaxy note n7000. I had a rooted checkrom v4 working on my note. I tried to install criskelorom v2 and got bootloops. I then tried to go back to stock via odin and flashed stock N7000 KL3 ROM which i had earlier used, I had to go to stock because after bootloop even recovery was not working. now after flashing stock i am getting a strange problem of the phone getting stuck at the welcome to gt-n7000 screen . "touch the android to begin" . nothing is happening after touching the android on the screen although i can change the language etc and even the pull down notification is also working but the phone is stuck at the initial stage. I have a nandroid backup of my initial checkrom in my internal sd card but cannot restore it before installing a rom with root and cwm. Kindly help . Thanks.
I'm having the exact problem. I'm hoping we can create a soft brick sticky thread. I walked away from my phone last night because I was getting frustrated.
My attempts to flash stock ROM via Odin resulted in the "not responding" message in windows. I can get to both CWM and download mode, however any ROM flashed via CWM results in the behavior described by the OP. fortunately I have access to another Samsung phone, so I can double check driver installation (although it worked for flashing previously).
I'm continuing a search through the forums to find some alternate methods for unbricking. Hope someone has an idea.
Thanks!
It seems that the stock roms i was trying to flash were nonwipe ones so i flashed xxla3 which is a wipe rom and was able to boot . I then flashed the earlier kl3 rom over this rom because kl3 is rootable. I then rooted and installed cwm booted into recovery and restored my earlier nandroid backup. I think the situation arises because the nonwipe rom was unable to clear the cache , user data etc
Thank you for the information. I had exactly the same problem. What did you use to root KL3 ?
Just wipe both cash and user data, and reboot.
reboot to recovery mode -> mount and storage -> format system, format cache, format data.
and do a factory reset and wipe cache.
problem should be solved cause that's what i did
Flo1389 said:
Just wipe both cash and user data, and reboot.
Click to expand...
Click to collapse
Thanks
liewkingyan said:
reboot to recovery mode -> mount and storage -> format system, format cache, format data.
And do a factory reset and wipe cache.
Problem should be solved cause that's what i did
Click to expand...
Click to collapse
daaamnnn!!! I'm scared to dead because of this!! Thanks dude!!!, no more **** ass ics
I had an issue like this once or twice.
http://www.youtube.com/watch?v=L5XjF6sPef4
This skips the that screen. then I cleared some things like google framework and it all was peachy
But its not wroking for me
Hi, im having problem with my o2x. Frirst phone started to behave strangely and every application has stop working. Error was
"uids on the system are inconsistent you need to wipe your data partition or your device will be unstable"
and then every time i restarted the phone it was the same error again so i decided to reinstall rom. Than error was gone but other problem appeared, now after 3 min of use phone get frozen and than i reinstall rom again and phone get frozen agan.
Please if someone can tell me what is the problem and how can i fix them.
You have mentioned reinstalling (reflashing?) the ROM but you haven't mentioned a factory reset so I have to ask... Have you tried a factory reset?
Should i do factory reset on rooted phone? if yes how can i do that. I read somewhere that factory reset should not be done on rooted phones. is that true?
In CWM, You always have to Wipe your Data,Cache,Dalvik Cache,Battery stats.
Optional : Format System.
For a rom to function well, else it will get all kind of problems, like you have.
Of course if you install a update for a ROM, you only have to wipe the cache/Dalvik Cache.
Remember to make a Backup of your apps with Titanium Backup.
I didnt wipe Dalvik Cache and Battery stats. I'll give it a try. What does Format System do?
The factory reset basically resets your phone to as it came from the factory. It erases all your settings and apps, and is recommended that you do that when you change from a stock ROM to a custom ROM.
Having root has nothing to do with it.
Me personally I like backing up my apps and doing a factory reset each time I change/update my ROM. This way I make sure I always have a clean system each time. Of course this might not be convenient if you like flashing a new ROM twice a week
Wipeing Dalvik Cache, Battery stats and factory reset didnt do the trick. I flashed cyanogenmode nightly now and its ok for now. Could it be problem with the rom?
"Factory reset" (/data wipe) doesn't wipe system apps. If you had on your old ROM some "broken" system app, you most likely still have it. First thing i would do is full device wipe (/data and /system partition wipe). If you dont know how to do this here is the script and how-to. Be aware of that this script can brick your phone (ofc then you can fix it with smartflash) is you won't follow instructions.
After that wipe and ofc flashing clean ROM (btw. which is it?), it still isn't working, it's most likely ROM's fault. It could be Baseband<->RIL problem eaither but i've never saw RIL problem which has influence of system stability.
Are you flashing back to stock or a custom ROM?
If you are flashing to a custom ROM, you need do all the wipe-steps and then do BacktoEXT3 before flashing the custom ROM,
http://forum.xda-developers.com/showthread.php?t=1021549
Hi guys. I'm quite a noob, but have a good experience on flashing without be bricked (CM9, CM10, Crash, Paranoid...), but I have a problem.
I will explain to you step-by-step what I've done with my Note, so I wish some of you could help me.
1) I was running JB Crash ROM with PhilZ kernel.
2) Some apps got Force Close too often, so I went on Rom Manager and, after a look into the "Fix permissions" description ("It will fix some force closes" or something like that), I decided to give it a try and I tapped on it.
3) After that, my homescreen became unusable, because "TouchWiz Home" got EVERY TIME force closed without reason. Everything else worked fine, so I deciced to boot into CWM recovery to restore a nandroid backup of the same ROM.
4) Instead of tapping "restore", I tapped "backup" (my fault) and it started without possibility of get back. I got something like 200 Mb of free space, so in every case it will never have had success. My Note stucked at this point, so I decided to reboot manually (vol up+home+power) into recovery. Finally I tried to "restore" but I get this message: "ERROR WHILE RESTORING /SYSTEM".
5) I tried to reboot my Note, but it stucks at "Samsung Galaxy Note GT-N7000" screen without going on.
The good news is that it can go without problems into recovery and into download mode. What can I do? Flashing from CWM, for example, CM9 can fix this?
Please help me thanks!
1. Boot into CWM
2. Wipe data, dalvik and cache
3. Format system
4. Reflash your ROM
Don't use rom manager it's not compatible ....
friedje said:
1. Boot into CWM
2. Wipe data, dalvik and cache
3. Format system
4. Reflash your ROM
Don't use rom manager it's not compatible ....
Click to expand...
Click to collapse
After formatting /system, can I try to restore my nandroid backup? Or I have to necessary reflash my ROM? In that case, it's the same thing make it via CWM or via ODIN PC? I'm still on PhilZ recovery, which is safe I guess!
Anyway, thanks for your help
Via CWM or Odin, depends if you have your rom in the zip or the md5.tar format.
I would reflash to be clean. It's a bit more work in restoring your apps and data
afterwards, but at least you don't restore any messed up files.
if you can still access CMW and Download Mode then you probably are not brick... try fresh install through pc odin.. safe method no need to worry about bricking by fullwiping on unsafe kernel or raising triagle or binary counter whatsoever.. if you wanna play safe then PC ODIN and after that you can root your rom
Thank you guys, now I'm on stock ICS flashed via PC Odin and everything works fine I knew I was 99% not-bricked (still recovery and download mode avaiable), but I was a little scared too.
Thank you again!
glad you solved it.. :good:
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.
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