Related
Hi guys!
I have just rooted my Motorola Defy and installed CM7 (7.0.2) into it using the instructions provided by CM wiki. I decided to use ClockworkMod and bootmenu, since I'm on Mac OS X.
Well, everything went fine until I tried to open the Market app, which was not working. Searching the web, I found that the solution could be wiping user data and caché through the recovery mode. As I could not figure out how to start the bootmenu (which I learned later), I did it through the stock recovery mode (using power + volume down)... and since that I can't boot my phone anymore!
I have already tried wiping everything again and installing CM7, but I'm still facing this problem.
Please, anyone have any ideas? I'm almost desperate.
gfreh said:
Hi guys!
I have just rooted my Motorola Defy and installed CM7 (7.0.2) into it using the instructions provided by CM wiki. I decided to use ClockworkMod and bootmenu, since I'm on Mac OS X.
Well, everything went fine until I tried to open the Market app, which was not working. Searching the web, I found that the solution could be wiping user data and caché through the recovery mode. As I could not figure out how to start the bootmenu (which I learned later), I did it through the stock recovery mode (using power + volume down)... and since that I can't boot my phone anymore!
I have already tried wiping everything again and installing CM7, but I'm still facing this problem.
Please, anyone have any ideas? I'm almost desperate.
Click to expand...
Click to collapse
So after doing a factory reset from stock recovery, you say you're trying to install CM7...
Are you installing this from CWM recovery?
Did you wipe Dalvik cache?
Are you using an MB525 Defy or an MB526 Defy+, and is the CM7 zip you're flashing a Defy or a Defy+ build?
>
You've probably not wiped Dalvik it seems.
In CWM recovery, go to Advanced and under that select Wipe Dalvik Cache.
Do yhis and a normal cache wipe every time you flash a ROM update. If you flash a totally new rom like CM10, wipe data also.
krushnam said:
So after doing a factory reset from stock recovery, you say you're trying to install CM7...
Are you installing this from CWM recovery?
Did you wipe Dalvik cache?
Are you using an MB525 Defy or an MB526 Defy+, and is the CM7 zip you're flashing a Defy or a Defy+ build?
>
You've probably not wiped Dalvik it seems.
In CWM recovery, go to Advanced and under that select Wipe Dalvik Cache.
Do yhis and a normal cache wipe every time you flash a ROM update. If you flash a totally new rom like CM10, wipe data also.
Click to expand...
Click to collapse
Hi! Thanks for the reply, and sorry for my English.
Actually, I have already installed CM7 and it worked fine, except for the Market app. Trying to solve this, I have done a factory reset from stock recovery and, since that, CM7 is locked to the boot screen.
And yes, I have installed CM7 through CWM recovery, and I'm using a MB525 Defy.
Well, I have just tried wiping Dalvik Cache, but it seem as if nothing happens when I select this.
Ya wiping Dalvik is very fast, but it will make a lot of difference. Every time you update your ROM, wipe both cache and dalvik.
>
If this didn't solve your problem, try wiping market data and uninstalling market updates. They will reinstall on their own.
>
If even that doesn't work, reflash the GAPPS zip.
BTW, shouldn't you be on CM7.2? That's the latest CM7 as far as I know.
CM7.2:
WhiteRabbit 1.8: http://forum.xda-developers.com/showthread.php?t=1510063
Maniac's builds: https://github.com/maniac103/android_device_motorola_jordan-common/downloads
Quarx's builds: http://quarx2k.ru/cm7-nightly-defy/
krushnam said:
Ya wiping Dalvik is very fast, but it will make a lot of difference. Every time you update your ROM, wipe both cache and dalvik.
>
If this didn't solve your problem, try wiping market data and uninstalling market updates. They will reinstall on their own.
>
If even that doesn't work, reflash the GAPPS zip.
BTW, shouldn't you be on CM7.2? That's the latest CM7 as far as I know.
CM7.2:
WhiteRabbit 1.8: http://forum.xda-developers.com/showthread.php?t=1510063
Maniac's builds: https://github.com/maniac103/android_device_motorola_jordan-common/downloads
Quarx's builds: http://quarx2k.ru/cm7-nightly-defy/
Click to expand...
Click to collapse
How can I wipe market data? It is not an option from CWM...
gfreh said:
How can I wipe market data? It is not an option from CWM...
Click to expand...
Click to collapse
You can only wipe data from an app trough the Apps Manager inside CM7 (that means you have to boot up your phone).
Try flashing the newest CM7.2 and the newest GAPPS for CM7.2.
If the problem persists, return your phone to the old .sbf and start all over again.
thiagoelg said:
You can only wipe data from an app trough the Apps Manager inside CM7 (that means you have to boot up your phone).
Try flashing the newest CM7.2 and the newest GAPPS for CM7.2.
If the problem persists, return your phone to the old .sbf and start all over again.
Click to expand...
Click to collapse
Well, I really can't boot my phone. I just can access bootloader and both recovery modes from stock and CWM (bootmenu).
Do you know how can I flash a .sbf on OS X? I know a lot of programs for Windows, and I also have found a script (sbf_flash.sh) that should work on Mac, but it seems that a lot of people are having problems in OS X (including myself).
gfreh said:
Well, I really can't boot my phone. I just can access bootloader and both recovery modes from stock and CWM (bootmenu).
Do you know how can I flash a .sbf on OS X? I know a lot of programs for Windows, and I also have found a script (sbf_flash.sh) that should work on Mac, but it seems that a lot of people are having problems in OS X (including myself).
Click to expand...
Click to collapse
OK. Go to CWM recovery. Wipe data. Wipe cache. Wipe dalvik.
Now install WhiteRabbit 1.8 or Maniac's CM7.2.
Flash the GAPPS packages linked in the respective threads.
Now AGAIN wipe cache and dalvik.
You should boot normally.
>
As long as you can access CWM, there's no need to reflash the SBF.
krushnam said:
OK. Go to CWM recovery. Wipe data. Wipe cache. Wipe dalvik.
Now install WhiteRabbit 1.8 or Maniac's CM7.2.
Flash the GAPPS packages linked in the respective threads.
Now AGAIN wipe cache and dalvik.
You should boot normally.
>
As long as you can access CWM, there's no need to reflash the SBF.
Click to expand...
Click to collapse
Hi,
I have just reflashed a retailer version using RSD on a friend's computer and it is now back to life... now I'm figuring out what is the best path to follow.
Thanks for the help!
Factory resetting from stock recovery messes up custom Rom!! If You are on custom rom, you have to use CWM for doing wipe etc...
Sent from my Defy green lense using xda-developers app
sa3e1 said:
Factory resetting from stock recovery messes up custom Rom!! If You are on custom rom, you have to use CWM for doing wipe etc...
Sent from my Defy green lense using xda-developers app
Click to expand...
Click to collapse
Yeah... I know that. I just wanted to rollback everything and have the phone back. I'm now studying which is the best ROM for me to install again, but meanwhile, I have my phone working.
Hi all !
Since yesterday I'm not able to flash any ROM on my I9505. This is what happened.
Yesterday I was flashing a ROM (PACman) and on that ROM I was getting a lot of FC
so I decided to put my previous ROM back on my phone (FoxHound). After the Aroma install,
my phone reboots and keeps stuck at the splash ''Samsung'' logo screen.
This is driving me crazy. I tried to flash different ROMs with no success..
I couldn't boot my phone up, couldn't access recovery, only download mode.
After I flashed a stock firmware with Odin, I can boot up and use my phone properly.
I only can't flash any other ROMs anymore, cause it will cause my phone to keep stuck
at the ''Samsung'' logo..
Someone got a solution? Or is someone having the same problem?
Bhagwanie said:
Hi all !
Since yesterday I'm not able to flash any ROM on my I9505. This is what happened.
Yesterday I was flashing a ROM (PACman) and on that ROM I was getting a lot of FC
so I decided to put my previous ROM back on my phone (FoxHound). After the Aroma install,
my phone reboots and keeps stuck at the splash ''Samsung'' logo screen.
This is driving me crazy. I tried to flash different ROMs with no success..
I couldn't boot my phone up, couldn't access recovery, only download mode.
After I flashed a stock firmware with Odin, I can boot up and use my phone properly.
I only can't flash any other ROMs anymore, cause it will cause my phone to keep stuck
at the ''Samsung'' logo..
Someone got a solution? Or is someone having the same problem?
Click to expand...
Click to collapse
After flashing a rom Try wipe cache , dalvik reboot should work
if not wrkng then try flashing rom factory reset , wip cache , dalvik reboot
if u are using PHILZ recovery no plm but if u have other recovery have PHILZ that will be a solution
123hiten said:
After flashing a rom Try wipe cache , dalvik reboot should work
if not wrkng then try flashing rom factory reset , wip cache , dalvik reboot
if u are using PHILZ recovery no plm but if u have other recovery have PHILZ that will be a solution
Click to expand...
Click to collapse
Hi 123hiten,
Thank you for your reply.
- I flashed FoxHound ROM, wiped cache and dalvik cache. No success..
- I did a factory reset, wiped dflashed FoxHound ROM again, wiped cache and dalvik cache. No success.
- I flashed PhilZ recovery, did a wipe data/factory reset, flashed FoxHound ROM again, wiped cache and dalvic cache.. and again no succes..
I didn't understand what u meant in your last sentence with ''plm''?
I tried to flash the PACman ROM again, and it worked, but still I'm getting Force Close when someone calls me or if I'm trying to call someone.
I really dont know what to do now..
Bhagwanie said:
Hi 123hiten,
Thank you for your reply.
- I flashed FoxHound ROM, wiped cache and dalvik cache. No success..
- I did a factory reset, wiped dflashed FoxHound ROM again, wiped cache and dalvik cache. No success.
- I flashed PhilZ recovery, did a wipe data/factory reset, flashed FoxHound ROM again, wiped cache and dalvic cache.. and again no succes..
I didn't understand what u meant in your last sentence with ''plm''?
I tried to flash the PACman ROM again, and it worked, but still I'm getting Force Close when someone calls me or if I'm trying to call someone.
I really dont know what to do now..
Click to expand...
Click to collapse
Hi.
"plm" = problem
What firmware does your phone say it has got?
malybru said:
Hi.
"plm" = problem
What firmware does your phone say it has got?
Click to expand...
Click to collapse
I don't know where to see that, but I'm sure it's XXUBMF8.
That's the stock firmware I flashed.
Bhagwanie said:
Hi all !
Since yesterday I'm not able to flash any ROM on my I9505. This is what happened.
Yesterday I was flashing a ROM (PACman) and on that ROM I was getting a lot of FC
so I decided to put my previous ROM back on my phone (FoxHound). After the Aroma install,
my phone reboots and keeps stuck at the splash ''Samsung'' logo screen.
This is driving me crazy. I tried to flash different ROMs with no success..
I couldn't boot my phone up, couldn't access recovery, only download mode.
After I flashed a stock firmware with Odin, I can boot up and use my phone properly.
I only can't flash any other ROMs anymore, cause it will cause my phone to keep stuck
at the ''Samsung'' logo..
Someone got a solution? Or is someone having the same problem?
Click to expand...
Click to collapse
try this method...WIPE FACTORY RESET...WIPE CACHE PARTITION ...advanced > WIPE DAVILIK CACHE and BATTERY STATS...and then go to MOUNT AND STORAGE and FORMAT SYSTEM...and thn try to install the rom hope it will work
Hi there
I seem to have a problem flashing 4.3 roms, actually any rom that isn't stock in general.
Right now I am running syzmel's 20E with 1.3ghz overclock version 3.09.
Back to the problem: this is the steps I take to upgrade to any rom: 1. Download (slimbean, vanir asop) 2. flash v20D (unmodded) 3. Root it using Framaroot 4. Install CWM using L7CWM.zip (extracted, then clicked on flash bootloader, flash recovery, and then booted into recovery) 5. Boot into CWM 6. Click on factory reset and reset 7. Go into mounts and storage and format /system 8. Go to advanced and wipe dalvik cache. 9. Flash either 4.3 version slimbean or Vanir ASOP (tell me which is better) 9. Flash gapps (Slimbean: Slim AIO minimal Gapps, Vanir: 4.3 minimal Gapps which is found in the Vanir ASOP page) 10. Factory reset again 11. Wipe dalvik 12. Reboot
Now as soon as I reboot, either it stays rebooting, or boots once and when you reboot it stays at the boot loading page (slimbean logo, or android logo) (In other words, once you go black, you never go back. Not being racist, just saying once it blacks out it doesn't work no more). So i retry. And then I give up and stick on v20E.
So please suggestions?
Also ignore my signature
AsianFoodRules said:
Also ignore my signature
Click to expand...
Click to collapse
Are you sure it wipes made correctly?
Danm, yes I'm sure.
Why you dont format cache and data & data/media ?
Did you try boot without gapps... Sometimes bad gapps cause a lot of problems
Sent from my LG-E610 using Tapatalk
When you factory reset it clears cache automatically. I'll try without Gapps.
wipe data,wipe cache wipe dalvic cache
AsianFoodRules said:
When you factory reset it clears cache automatically. I'll try without Gapps.
Click to expand...
Click to collapse
How do you factory reset? Factory Reset is NOT only wipe data
raul338 said:
How do you factory reset? Factory Reset is NOT only wipe data
Click to expand...
Click to collapse
Factory reset in CWM clears cache automatically.
....Anyway, I finally fixed it. Turns out I had to wipe EVERYTHING. Including /data and /data media. Thanks anyway guys.
LG Optimus L5 E610 - CWM Bootlooping
Basically I inserted a pre-rooted firware into my lg phone using 20d+root + cwm.kdz, everything was fine including the flashing, I some how got the the CWM recovery and done everything such as wiping cache, etc, but the problem was before and after the wiping, etc, is that everytime i press power button it turn off and on and back on to the CWM recovery screen not home screen with apps, etc.
I am really fustrated, please Help!:crying:
Hello,
actually I'm using a SGS4 I9505 with cm-12-20150304-NIGHTLY-jfltexx and CWM 6.0.5.1.
I've tried to flash several TW Lollipop firmware wich i found in the I9505 forum:
1. Kushan+Touchwiz+Lollipop+Lite+Rom+v.1.2
2. S4_Echoev42_EchoePop2_020315
3. OA7-2.1F
4. XXUHA07-v2.01
Before flashing any oft this firmwares i made a factory reset, wiped both caches and installed the modem Firmware via Odin.
After flashing firmware # 1 and 2 my phone was stuc in a bootloop (only Samsung Galaxy S4 Logo appears).
Flashing firmware #3 and 4 fails and cwm reports error 7.
Flashing cm12 afterwards isn't a problem and runs fine.
I think the wipe fails or doesn't work properly. Is it enougth to select factory reset in cwm and wipe the dalvik cache manualy?
What can I do?
With besteht regard
Mirko (NemesisMF)
What if it is a recovery problem?
Thought about that too.
Should i try twrp or philz?
I switched to Philz Recovery and flashed S4 Echoe Rom v42 without any Problems.
CWM seems to have a problem to falsh TW Lollipop images ower an existing CM12 an the I9505.
You need to do full wipe not just cache.
ranger4740 said:
You need to do full wipe not just cache.
Click to expand...
Click to collapse
As I wrote above I did a factory reset before flashing and wiped the caches with cwm. If that is not enougth it would be nice to explain what else I have to wipe or post a link.
While using philz recovery the factory reset for clean system is enougth and the new System is working fine.
Factory wipe is not full wipe, you need to do a full wipe as in format to install new rom, phillz recovery has this feature can't remember exactly where, I think its under advanced.
Just have a look in the sub menus.
Just to explain it better when you do a full wipe it deletes every part of the existing
Rom including the system, data and cache and some other stuff completely removing the android operating system, so unless the rom you install does a wipe before install parts of the existing system will remain and can cause boot issues. For example as you've already discovered you are trying to install a tw rom over an existing cyanogenmod 12 installation which Will cause it to hang on boot.
NemesisMF said:
As I wrote above I did a factory reset before flashing and wiped the caches with cwm. If that is not enougth it would be nice to explain what else I have to wipe or post a link.
While using philz recovery the factory reset for clean system is enougth and the new System is working fine.
Click to expand...
Click to collapse
Do you mean a factory reset from within Android itself? If so, then that's a complete obsolete step. When before flashing a rom you should perform a factory reset, then they always mean a full wipe from the recovery. You need to do a full wipe from the recovery. That means the /system partition is being wiped. You will see it in the screen during the wipe if it wipes /system.
But it also could have been a problem of CWM. I don't think it is being updated anymore, so better use TWRP or Philz.
Hi,
I have a problem installing 8.1 oreo roms on my phone. I follow standard procedure: wipe dalvik, cache, system, data -> install rom + gapps -> wipe cache. After my phone restarts, it displays rom logo, but doesn't load (even after 15-20 minutes of waiting). All I can do is load in fastboot and restore my backup. I use twrp 3.2.1-0, unofficial 8.1 pico gapps from 2018/01/30.
So far I tried:
-Installing rom and gapps separately.
-Installing rom, rebooting, installing gapps.
-Installing rom + gapps, then wiping data.
-Installing rom + gapps, then not wiping anything.
-Factory reset, then install rom + gapps.
-Installing rom + different gapps versions.
Additional notes:
-At one point I successfully installed NitrogenOS (about a month ago) and it is my current rom and backup. But I can't clean flash it again.
-When I install rom only (without any gapps) it boots up fine without errors or long loading.
Can anyone help?
Same problem I am also facing. Using Pixel experience ROM but now not able to flash cosmic official rom...remaining on bootanimation
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
Flash
Rom
Gapps
Wipe to factory reset
Reboot
Done ! That's the only way it worked for me
metro20 said:
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
Flash
Rom
Gapps
Wipe to factory reset
Reboot
Done ! That's the only way it worked for me
Click to expand...
Click to collapse
Thanks for answer. I tried that method too, but it still didn't work for me. I recently tried clean flash with gapps from https://forum.xda-developers.com/xiaomi-redmi-3s/development/rom-lineageos-15-1-t3718757 and it worked flawlessly. So maybe it's an issue with some gapps packages?
I also have the exact same problem.
Flashing ROM without gapps works perfectly.
adding gapps package, no matter if its pico aroma or mini, it results in stuck on boot animation.
wiping after flashing also did not work.
once made pixel experience boot, using it since...ota update worked without a problem.
any other suggestions?
devito666 said:
I also have the exact same problem.
Flashing ROM without gapps works perfectly.
adding gapps package, no matter if its pico aroma or mini, it results in stuck on boot animation.
wiping after flashing also did not work.
once made pixel experience boot, using it since...ota update worked without a problem.
any other suggestions?
Click to expand...
Click to collapse
Try this nano package https://androidfilehost.com/?fid=889964283620771808. It's the only one that worked for me.
sanchez8096 said:
Try this nano package https://androidfilehost.com/?fid=889964283620771808. It's the only one that worked for me.
Click to expand...
Click to collapse
Thanks for the Link!
But unfortunately still Not booting...tried atomic official and teammexs Rom...
metro20 said:
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
*then tap back, FORMAT DATA and confirm by typing "yes"
Flash
Rom
Gapps
Magisk stable (if preferred if not next >>>)
Magisk beta (always flash after stable)
Busybox flashable zip (if needed)
Mods such as MIUI cam mod
Font package
Wipe to factory reset
Reboot
After 1st boot
Reboot to TWRP
Install Magisk modules ( USN or Viper4android etc)
Reboot system
Done ! That's the only way it worked for me
Click to expand...
Click to collapse
ftfy. But before this ensure that:-
1. Non corrupted ZIPs. Avoid if possible from using mobile data. A slower yet stable WiFi yields better success rate.
2. Currently this unofficial opengapps' builds works better and are more current.
Suo.Eno said:
ftfy. But before this ensure that:-
1. Non corrupted ZIPs. Avoid if possible from using mobile data. A slower yet stable WiFi yields better success rate.
2. Currently this unofficial opengapps' builds works better and are more current.
Click to expand...
Click to collapse
I didn't need to format data on Oreo nos
As mentioned in other threads on this topic, I just wanted to mention here as well that I am also affected by these Oreo boot loops and haven't found a solution yet. I somehow managed to get PixelExperience to install once, but downgraded now to a Nougat build for other reasons (better battery and GCamMod compatibility).
sanchez8096 said:
Thanks for answer. I tried that method too, but it still didn't work for me. I recently tried clean flash with gapps from https://forum.xda-developers.com/xiaomi-redmi-3s/development/rom-lineageos-15-1-t3718757 and it worked flawlessly. So maybe it's an issue with some gapps packages?
Click to expand...
Click to collapse
Use twrp 3.2.1-0 bcoz some Oreo ROMs aren't flash able by 3.1.1
Sunny Za said:
Use twrp 3.2.1-0 bcoz some Oreo ROMs aren't flash able by 3.1.1
Click to expand...
Click to collapse
I am using 3.2.1-0 twrp. Rom itself flashes fine, it's the gapps that create infinite boot.
Exact Same issue Here...
I have same problem too .. can't boot in to any Oreo ROM with Gapps .. really isn't any solution here?
This might not be a proper solution, but here's what I did:
1) Wipe data, cache, dalvik, system
2) Flash rom + gapps(I used NitrogenOS and pico gapps)
3) Wipe data again and restore data from backup(I restored data from previous build of NitrogenOS, so I don't know if restoring from different rom will be ok)
4) Boot into rom, ignore any "stopped working" errors and go to Settings-System-Reset options-Erase all data(Not sure if this will erase internal storage, backup just in case)
After that phone booted up and and did first time installation.
sanchez8096 said:
This might not be a proper solution, but here's what I did:
1) Wipe data, cache, dalvik, system
2) Flash rom + gapps(I used NitrogenOS and pico gapps)
3) Wipe data again and restore data from backup(I restored data from previous build of NitrogenOS, so I don't know if restoring from different rom will be ok)
4) Boot into rom, ignore any "stopped working" errors and go to Settings-System-Reset options-Erase all data(Not sure if this will erase internal storage, backup just in case)
After that phone booted up and and did first time installation.
Click to expand...
Click to collapse
Can someone upload me some backup? Pixel Experience would be a best ! Thanks a lot
Anyone have an idea what the problem might be?
I'm facing the same problem. I have a Redmi 3S (international, 3GB version). Doesn't matter what Oreo ROM I try (clean install), they all get stuck in bootloop on boot animation. It doesn't get far enough in the boot process to do a logcat with ADB, so I'm not able to post it.
I'm using TWRP 3.2.1-0 but have tried Red Wolf recovery as well and it yields the same results... I don't think it's a gapps issue since I've tried booting several ROMS without installing gapps.
I have rebooted several times while it's still in the boot process, remounted system in TWRP, wiped everything, ...
If anyone has an idea to get the logs, fire away. Can't boot so can't install liveboot or something like that.
bump
any solution?
The Problem still occurs...
Flashed PE successfully once, but since i went Back to official Nougat lineage os, No Oreo Roms can be booted with gapps