Database Develop

[Q] Zeus Rom v6.22n Random Reboots

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

Trying to upgrade from cyanogen 9 to cyanogen 10 now missing phone and camera apps.

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.

[Q] Problems installing stock rom, possible bootloop?

Hey XDA
Been trying to go back to stock ROM (http://forum.xda-developers.com/showthread.php?t=2224752 odexed version) where I followed this guide http://forum.xda-developers.com/showthread.php?t=2265618 using Method 1 under "Going back to stock" section. What I did was
1. Make backup of the ROM before I trying to go back to stock ROM
2. Format Data and wipe dalvik and normal cache several times so I was pretty certain of having a clean phone
3. Used sidepush to transfer ROM from PC to HTC One in recovery mode (FYI, using TWRP recovery)
4. Installed the ROM (While installing I noticed it said that first boot would take some time, but not how much or some sort of estimate)
5. Wiped dalvik and normal cache
6. Rebooted to system
Now it is just stuck on the standard HTC "quietly brilliant" startup logo and has been for 20+ minutes and still nothing happens. What have I done wrong and what can I do to fix this?

[Q] Razr i - no possibility to flash custom rom or stock - bricked?

Hallo together,
I seem to have done something wrong while trying to flash the rom "RazRi_JB_X-2014-Jul-16".
Here is what i did:
- Unlocked to bootloader using official Motorola homepage
- Flashed CWM (non-touch) recovery using "Recovery Flasher by LeBobo v1.7", USB-Debugging was on
- Rebooted into bootloader and flashed "RAZRiRoot2" to prevent Stock-ROM from overwriting the recovery
- Tried to install the Custom ROM using CWM, but it fails to wipe cache (stuck on line "Formatting /cache")
Because it didn't work, i tried to reset everything as it was before to be able to try again - flashed stock-recovery using the Recovery Flasher by LeBobo, booted into bootloader and selected "Factory". The cell is now just showing the "Warning bootloader unlocked" warning and nothing else happens.
When i try to select the recovery in the bootloader menu, an image of a Android laying on its back with an opened hatch and a red warning symbol showing a "!" appears and nothing else happens.
I seem to have bricked my device, because i cant't really do anything now - is there any solution?
I read through different topics but could not find a real solution to this particular problem...
Thank you so much in advance for your help!

It's not bricked
At the moment u enter stock recovery with that android and red warning sy,bol, u need to press bot volume up + downp. Than it will enter stock recovery mode.
Those are the following things u can do to get custom rom,
1. Flash another recovery, cwm touch, cwm non-touch, twrp. They all work a little different.
2. Flash the custom rom and wipe everything, The wip can take some time. sometimes it will be seconds, sometimes it will take a couple of minutes. Every recovery behaves different, and every flash/wipe too.
3. enjoy
If u really want to go back to stock, flash your stock JB firmware by RSD-Lite.

Thank you very much for your answer. I restored the stock rom using RSD Lite and did a clean install of TWRP.
Then I did a Factory Reset and started to install the custom ROM.
The TWRP is now stuck at "Flashing File 1 of 1 /external_sd/RazRi_JB_X-2014-Jul-16.zip".
Is it normal that it takes more than five minutes or is something going wrong here? Is there something i forgot?

StarGeneral said:
Thank you very much for your answer. I restored the stock rom using RSD Lite and did a clean install of TWRP.
Then I did a Factory Reset and started to install the custom ROM.
The TWRP is now stuck at "Flashing File 1 of 1 /external_sd/RazRi_JB_X-2014-Jul-16.zip".
Is it normal that it takes more than five minutes or is something going wrong here? Is there something i forgot?
Click to expand...
Click to collapse
5 minutes is a bit too much. But that's the problem with this device. Every device behaves different and we haven't found out a solution too it.
At the moment i can't do much for you. I can only say try to wipe the partitions mannualy. Wipe system, data and cache. and mount system. And then try to install it. Maybe if that doesnt do the trick try again another recovery.
This from KTR-ROM
Code:
- Enter in TWRP or CWM
- Wipes required: data, system, cache y dalvik
*In CWM mount system must format before (Mount and storage -> Mount system)

Thanks again - that was it.
For some reason, TWRP did not automatically wipe the system-partition. It had to be mounted + wiped manually.
Not the custom ROM is up and running well. Installation took 35 minutes for some reason though...
Thank you so much for your help!

StarGeneral said:
Thanks again - that was it.
For some reason, TWRP did not automatically wipe the system-partition. It had to be mounted + wiped manually.
Not the custom ROM is up and running well. Installation took 35 minutes for some reason though...
Thank you so much for your help!
Click to expand...
Click to collapse
nice, glad that it worked

Soft brick on rooted Xperia Z3c locked bootloader?

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?