Hi there,
a few days ago I flashed my LG Optimus Black with Zeus Rom v6.22n (previously I had v3 installed, but I did a wipe and first installed v6n before updating to v6.22n). Up till today everything went fine, but since this morning the phone gets really hot and then randomly reboots (at least 4 times now!). Also, wifi seems to have stopped working (just doesn't even attempt to connect and I can't tell it to because the settings won't open).
Is there anything I can do, or will I have to reflash?
I did not change anything serious with the Zeus Tweaker (only injected Titanium Backup and restored LG E-Mail and Gallery).
I use Go Launcher Ex and Widget Locker.
Hoping for help,
Silberwoelfin
Both Zeus 6.22n and 6.22o runs stable and without any problem.
The people who experiment "strange" things can elimate this doing a fresh reflash, not forgetting doing de necesery wipes (factory, dalvik, system). Dalvik wipe is made by the flashed zip, but it isn't a great effort to do this manually.
The order to flash is first: 6.20n and second: 6.22n
or first 6.20o and second 6.22o
You jumped from 6n to 6.22n and this can't work!.(See Huexxx instructions in his first post, in his thread about Zeus)
Regards!
Sorry, I didn't remember correctly. After looking it up in my download-folder, I did flash v6.2n not v6n. And afterwards the v6.22n.
And, as I said above, I did do wipes. Although, I do not know which of the ones you mentioned, since I let the RomManager do it for me (both 'wipe data and cache' and 'wipe dalvik cache'). That should be enough though, shouldn't it?
Alas, I don't see why we should do a factory reset, because afterwards we would have to reinstall RomManager in order to install the rom. So the factory reset would be tainted again, wouldn't it?
Silberwoelfin said:
Sorry, I didn't remember correctly. After looking it up in my download-folder, I did flash v6.2n not v6n. And afterwards the v6.22n.
And, as I said above, I did do wipes. Although, I do not know which of the ones you mentioned, since I let the RomManager do it for me (both 'wipe data and cache' and 'wipe dalvik cache'). That should be enough though, shouldn't it?
Alas, I don't see why we should do a factory reset, because afterwards we would have to reinstall RomManager in order to install the rom. So the factory reset would be tainted again, wouldn't it?
Click to expand...
Click to collapse
Wipe data is factory reset and you don't lose recovery. In zeus you don't have to install rom manager because it has the g-recovery.
Sent from my LG-P970 using Tapatalk 2
Follow Huexxx's instructions:
- Need to use CWM recovery
- Copy v6.2 and v6.22 to sdcard root
- Reboot in recovery
- Do a nandroid backup of your phone, I'm not responsible of your data losing
- Do a wipe data/factory reset. If you come from same base you can try to flash it wipping only /cache.
- Flash the ROM v6.2 with option: Install zip from SDCARD.
- Flash the update v6.22.
- Reboot and wait...
THE SAME BASE means v6.x, due Huexxx has totaly rebuild this version from scratch. So don't use Rommanager to flash, use recovery "install zip from SD" after the whipes. And sure, you are right the 'wipe data and cache' (=factory reset) and 'wipe dalvik cache' are normaly enough. But you went into a problem with it and RomManager, so to go safety do the wipes factory, dalvik and format system partition, mentioned in my post before in recovery mode. I think that this isn't a big thing.
Hope this will solve your problem.
Regards.
I got this problem too. This morning, my phone just got so hot and then power off. I'm using Zeous v6
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)
Well, i am stuck at bootlooping after flashing CM7.1 onto my friend's device, we've tried many times flashing it with different ways, but it seems to get stuck everytime at the bootscreen, i know the initial boot can take up to something like half an hour but after 2,5 hours we gave up, downgraded to 2.3.4 again using odin, and tried again on a different way (different recovery)
this is how we flashed it:
-made sure we had 2.3.4
-wiped data and cache with CWM 4.0.0.idk (the odin package for this CWM was included in the thread)
-installed CM7, everything went smooth
-rebooted, and then it got stuck
I really want to get this to work for him, any help from you guys?
is it because i wiped after flashing ?
Well the process should be like this :
1. Wipe data - Wipe cache - Wipe Dalvik-cache - Wipe Battery stats
2. Flash ROM
3. Wipe data - Wipe cache - Wipe Dalvik-cache - Wipe Battery stats
So twice?
He's not here right now with the device, but i want to gather enough info for tomorrow to retry
`leon said:
So twice?
He's not here right now with the device, but i want to gather enough info for tomorrow to retry
Click to expand...
Click to collapse
Yeah, it is safe to wipe before and after flashing.
And you're sure you did wipe dalvik-cache right ?
errrrmm, i don't remember, i think i did tho, i will, as again, retry tomorrow with also wiping dalvik
Well, as for me, when something went wrong, i flashed my device back to stock froyo first.
Then flash GB, Flash CWM, clear data and cache, flash the rom, clear data and cache again.
Reboot.
That's it
Sent from my GT-S5570 using xda premium
K, he's not here, i will give it a try now, fingers crossed :x
i know though what went wrong before
`leon said:
K, he's not here, i will give it a try now, fingers crossed :x
i know though what went wrong before
Click to expand...
Click to collapse
Always explain what went wrong, if someone with the same issues is reading the thread they'll know what not to do then.
So, what went wrong before?
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
I have the GT-i9000M
I did not put Cyanogen 9 on myself, the phone was given to me with it on it. I wanted to upgrade to cyanogen 10 so I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=1778526 .
"- Upgrading from CM7/CM9?
Do a Nandroid Backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon"
Did my nandroid backup obviously, wiped everything, then I went to "install zip from sdcard" picked "cm-10-20120726-UNOFFICIAL-galaxysmtd.zip" then my phone went into a reboot loop of just failing. So I went back into recover with 3 button combo and wiped everything again and restored from my nandroid backup, then when I booted back up I had no lockscreen and my phone and camera apps were gone.
What did I do wrong and how do I get those back and/or upgrade to cyanogen 10 properly?
Keep in mind this is my first time doing anything like this to my android, I was given it with cyanogen 9 on it.
Edit: Now when I try restoring from my nandroid backup and reboot all I see the is the cyanogen (mod) 9 animation boot screen forever, it never boots.
fastfreddy101 said:
Edit: Now when I try restoring from my nandroid backup and reboot all I see the is the cyanogen (mod) 9 animation boot screen forever, it never boots.
Click to expand...
Click to collapse
First i9000M is not same as I9000 http://forum.xda-developers.com/showthread.php?t=886158
so you need to check for compatibility problems
This procedure is for i9000
1. Using CWM, make sure to wipe data/factory reset, then wipe cache, and then go into advanced, and wipe the Dalvik cache too.
2. From there, flash the ROM
3. Afterwards, repeat the wipe step (step #1).
4. Continuing on, go into advanced and fix permissions.
5. Finally, reboot the device.
Thanks for the reply!
I finally got it by wiping everything and the dalvik cache, and reinstalling the zip from the SD card, got everything working now.
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?