Well I just rooted and here's the deal, every time I try to install an app from the market either the market force closes and i cant get to install it either my phone kind of restarts it shows the boot animation and then its back to the homescreeen.
Another thing is that market does not autoupdate but when I leave the phone in standby with the wifi on it shows the boot animation again and its back to the homescreen again I believe its the same thing that happens when try to install an app also.
I rooted my phone trough the SmartFlash methond by installing a firmware patched with CMWT.
Do you know what I should do in this situation?
Best regards.
Edit: I noticed this happens also when I try to install any kind of apk.
What I have tried until now: - fix permissions trough CWM (didn't work)
- dalvik wipe (didn't work by it's own, haven't tried it after factory reset as factory reset fixed the problem)
Firmware version: V20N - Germany
Solution: - wipe data/factory reset from CWM
Thank you for the help you gave me
What is your rom version btw?
Sent from derp-mobile
Best will be a factory reset + dalvic wipe from CWM. But make a backup before, so you can restore it
Related
Please Help I installed a custum ROM and now I am stuck in a loop a skull comes up and droid and it continues till the battery is dies. I have tried to factory reset and nothing the only way to turn it off is to remove the battery can someone please Help
If the ROM is what's causing the problem, doing a factory reset won't change anything; it'll stil keep the same ROM in place. What you might want to do is download a more popular ROM, like a CM7 nightly, put it on your microSD card (using another phone or a microSD adapter, of course) and boot into recovery and flash that.
If that doesn't work, I dunno then. I got a bootloop the other day after using ROM Manager to flash a new kernel. Turns out it was the kernel because after a factory reset, it booted up fine. So I just chose another kernel and it's all good now.
You just might have a screwy ROM. Try reflashing it if you can. What was the custom ROM, btw?
Yeah I'd agree with the above; install another ROM and make sure to wipe cache and dalvik and if it still doesn't work wipe data as well. Note that wiping data will wipe pretty-much everything on your phones memory (SMS messages, contacts, accounts etc)
when it is cm7 than you should take an other kernel
Please, if you are experiencing random reboots (that involve the M logo) or prolonged screen freezes, you should revert to an older beta kernel that is free of the DSI errors. To do so, replace the boot.img in the update-cm-7...zip package with this one (from 0.04 version): http://code.google.com/p/cyanogenmod4milestone/downloads/detail?name=bootimg0.04.zip
Click to expand...
Click to collapse
Stole that from another Thread:
_Flash with any rom you have
_Milestone will auto reboot after flash done and loop
_Don't worry about that, remove battery in 5s and re-plugin
_Turn on your milestone: hold X and POWER to access Recovery. Select Wipe and reboot
Do you have a Droid or a Milestone? If you have a Milestone, which country is the device from?
I had a boot loop issue too on my UK Milestone when I tried to install CM6.1.2, version 28.01.2011 0.07-11.01.28. (http://android.doshaska.net/cm6)
This is what I did to fix the problem...
- Flashed UK 2.1 SBF file
- Flashed Vulnerability Recovery
- Rooted the phone
- Installed and booted into OpenRecovery
- Installed 15.01.2011 0.06-11.01.15 version (phone booted fine)
- Rebooted into OpenRecovery > Wiped Dalvik Cache
- Applied 28.01.2011 0.07-11.01.28 version
One more thing, you may need to update and/or change your baseband files.
I hope this helps.
Thx for the help guys I,m back up an running. Greatly appreciated
Sent from my Droid using XDA App
Hi all,
So after I flash a new ROM (MIUI MGv2/RC8vC/MGv1) I always hang at the Galaxy S GT-I9000 screen - the first boot screen.
I am wondering what this means? is it a corrupt file, something wrong with my internal sdcard, ROM not installed properly?
Please help,
Thanks.
some times a wipe from recovery will help and goes back to normal boot
many issues may cause this problem for instance if framework.jar or android.policy.jar or... have some bugs , will happen like that
Hi,
By wipe you mean clearing the formatting system, data, cache, dalvik cache and a factory reset? I ask this because the MIUI roms are not are non-wipe and the instructions recommend you to format those places before install (which I did).
I mean wipe cache partition from recovery. just try it and ley us know if it works
Well I just tried again but it doesn't work because I can't access recovery mode. It hangs at the Galaxy S screen and doesn't move from there so I'm wondering why because if I can't fix the bad install then I can't access the recovery mode and can only flash.
if recovery dont work BUT download mode does,
start the whole process again, flash back to stock froyo with froyo bootloader.
did you come to MIUI from Gingerbread ??
Well i've done the process like 10 times, nearly every single time from froyo (JPU,JS5,Ezbase 2.0) and I also went from 2.1 to 2.2 and then to MIUI. The other times I have tried coming from CM7 as CM7 works.
well i have a similar issue but in my case i just wiped my data thru cwm on darky v8 xxjpy..
now i get boot loops,any idea what should i do??
i know this is not exactly the thread but if i get my answer it'll save me from starting a new one..
When I got bootloops i normally reflashed. If you don't have data it will probably work?
I assume you have data as your on Dark v8 when V9 is out?
i dont understand by have data??
i flashed v9.5 but went back to v 8 few months ago..
today i just wiped/factory reset my phone using cwm and it was succesful but now its bootloops and vibrations..
i never wiped my phone before and only have flashed using cwm,never used odin for flashing roms!!
OH I see, by data i meant personal data that you might want to back up...I'm not to most knowledgeable but I know how to flash roms. I reckon you should try to flash V8 it again if you can enter recovery.
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
As the title says I have the problem that I'm stuck in a bootloop. (LG Logo coming up over and over again)
May initial plan was to root the phone (for ClockworkMod, I used AIO-Toolkit), then do a factory reset and then make a backup of the Stock Sytem before attempting to flash the Custom Rom. So there is no Custom Rom on my Phone at the moment. The rooting worked fine and I was able to start it up. Then I turned it off again and entered the Recovery Menu (PWR + Vol -) and selected the option "wipe data/factory reset". Expecting that this would do a factory reset. Then I started it back up and it was stuck in the bootloop. I do have still access to the Recovery Menu. The ClockworkMod is on version 6.0.1.5. I already tried taking out the battery for a few seconds and starting up again and I also tried wiping the Cache and the Delvik Cache and apply the factory reset again. No change.
My Android is still on version 2.3.4 GB. So still the old bootleader as far as I know.
I hope the information I provided were helpfull.
Thanks in advance. I hope you guys can help me.
P.s.: I'm from Germany so my english is far from perfect. I hope it wasn't too bad ^^
FIXED IT!
Flashed a new 2.3.4 V20Q with SmartFlash.
Before that I had a V20R. I am not 100% sure what the difference is but it looks fine.
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?