Hey guys,
I've tried to flash DarkSide preFinal on my Atrix, now the phone is stuck on "Unlocked, Dual Core"-Screen.
Here's what I did:
Downloaded latest DarkSide and saved it to internal SD
Factory Reset via Recovery Console
Wipe Data
Wipe Cache
Wipe Dalvik Cache
Flashed the zip file
the process seemed to go through just fine, now when I'm trying to boot the phone it is stuck at the "Dual Core"-screen
Any ideas on how to solve this? I tried to factory-reset and wipe several times, still stuck
Any help is appreciated!
1. Do you have an unlocked bootloader?
2. Are you using a CWM-based recovery?
If you have answered yes to both 1 and 2 then:
3. Have you tried flashing the zip from the external SD?
4. Did you try to flash anything else after flashing the ROM while still in the same recovery session?
(If you answered "Yes" to #4 then re-flash the rom by itself and boot at least once before flashing anything else)
EDIT: Ignore question #1, I just realized you mentioned "Unlocked" on the boot logo.
rbf101 said:
Hey guys,
I've tried to flash DarkSide preFinal on my Atrix, now the phone is stuck on "Unlocked, Dual Core"-Screen.
Here's what I did:
Downloaded latest DarkSide and saved it to internal SD
Factory Reset via Recovery Console
Wipe Data
Wipe Cache
Wipe Dalvik Cache
Flashed the zip file
the process seemed to go through just fine, now when I'm trying to boot the phone it is stuck at the "Dual Core"-screen
Any ideas on how to solve this? I tried to factory-reset and wipe several times, still stuck
Any help is appreciated!
Click to expand...
Click to collapse
Thanks for the quick reply.
I reflashed with Wet Dream from the external SD (newer is always better, right? ).
Everything is working now
Seems like being a great ROM.
rbf101 said:
Hey guys,
I've tried to flash DarkSide preFinal on my Atrix, now the phone is stuck on "Unlocked, Dual Core"-Screen.
Here's what I did:
Downloaded latest DarkSide and saved it to internal SD
Factory Reset via Recovery Console
Wipe Data
Wipe Cache
Wipe Dalvik Cache
Flashed the zip file
the process seemed to go through just fine, now when I'm trying to boot the phone it is stuck at the "Dual Core"-screen
Any ideas on how to solve this? I tried to factory-reset and wipe several times, still stuck
Any help is appreciated!
Click to expand...
Click to collapse
how long did you let it sit at the loading screen?
Usually when I have boot loops, I let it sit on the loading screen for awhile(2-4 minutes). If it still doesnt boot, then I do a battery pull, and then usually after that it boots.
And if it doesn't boot just reboot into recovery mode, wipe cache, data and dalvik and reinstall the ROM again.
Sent From Rob's RP-Hybrid Atrix.
When installing any new rom, it can take a while to build up the dalvik cache again. I've had it take up to 10 min before. Best to just walk away and come back and check on it.
Related
Guys, I desperately need help. I followed this guide to install CM7.1 nightly into my Defy and at the end I got the CM7 logo loop. Based on the guide, I took out the battery and put it back and now it's stuck at the small "Google" logo. I took out the battery again and went to the system recovery to wipe cache/factory reset. I got bunch of "mount" cache errors (command, log). I then went to the custom recovery and did the wipe cache again, this time beside "mount" cache error, there were some "open" cache errors. I did the wipe one more time and all of these errors gone. Booted it up again, and it still stuck at the "Google" screen so I went into the custom recovery trying to wipe dalvik cache as the guide said. I selected that option but nothing happened. No question asked to confirm the wipe and all it did was a short blink screen and the screen stayed the same.
Any helps would be highly appreciated !!!
That sounds a bit tricky to me, but first things first.
The first boot after installing CM7 can take a while (some minutes) since all the dalvik cache and other things has to be built. Taking out the battery during that is somewhat risky I think. After the first boot, the system starts pretty fast.
The best guess for you (at least that is what I would try) is:
go to recovery, clear dalvik cache and cache. If you have not installed CM7 before, i would also recommend to clear data as well (ok you lose you data but I hope that you were not doing it without a backup).
Then I would reflash cm7 and try again.
since you had the cm7 boot scree, I believe you have no kernel problem...
by the way, do you know what version your initial rom was?
I think it`s better to flash it from scratch:
1) Flash your previous rom with RSD
2) Root + cwm recovery
3) Cyan
(and if I were you - I would do wipe from stock recovery after 1st step and wipe from custom recovery after 3 step)
Yes, as Iddqd2 suggested just flash stock froyo using RSD Lite and then go all over for CM7 method of installation.
Hi guys,
I was running on CM10 11.18. However, wanted to switch back to CM7.2. Phone is now unable to boot up.
This is what I did.
1. Wiped Cache and data in stock recovery.
2. Wiped Cache, dalvik, data in custom recovery.
3. Installed CM7.2 and gapps
When I tried booting it up, the phone was on bootloops.
Then I picked my SEA sbf and flashed it using RDS Lite. However, problem persists. . Can anybody guide me through. I am without a phone now. Help!
You'll have to convert data to ext3.
Install cm10, in boot menu select tools then filesystem tools then convert to ext3
Sent from my MB526 using xda premium
rashsalmn said:
Hi guys,
I was running on CM10 11.18. However, wanted to switch back to CM7.2. Phone is now unable to boot up.
This is what I did.
1. Wiped Cache and data in stock recovery.
2. Wiped Cache, dalvik, data in custom recovery.
3. Installed CM7.2 and gapps
When I tried booting it up, the phone was on bootloops.
Then I picked my SEA sbf and flashed it using RDS Lite. However, problem persists. . Can anybody guide me through. I am without a phone now. Help!
Click to expand...
Click to collapse
Have you tried to wipe data in stock recovery again? (volume down + power on)
If bootloops persist try to flash your sbf again, after flashing go to stock recovery immediately and wipe data again.
I Flashed JellyTime ROM available here. I updated the Gapps too. The whole installation went smooth. Tab started with JT logo and then went blank. I waited for like 10 minutes and nothing happened. I tried twice but same result. So I went back to ICS4.0.3 stock.
Can some tell me if there is a newer JT ROM or am i doing someting wrong? I wiped cache and dalvik before flash.
PLEASE HELP:crying:
PuruTiger said:
I Flashed JellyTime ROM available here. I updated the Gapps too. The whole installation went smooth. Tab started with JT logo and then went blank. I waited for like 10 minutes and nothing happened. I tried twice but same result. So I went back to ICS4.0.3 stock.
Can some tell me if there is a newer JT ROM or am i doing someting wrong? I wiped cache and dalvik before flash.
PLEASE HELP:crying:
Click to expand...
Click to collapse
You have the V8 unlocked bootloader installed, correct? If not, you'll need to have it installed first.
If so, and a recent CWM installed,
sequence should be;
a. Wipe data/factory reset
b. Wipe Cache
c. Wipe Dalvik
d. Format /system
e. Install JT
Moscow Desire said:
You have the V8 unlocked bootloader installed, correct? If not, you'll need to have it installed first.
If so, and a recent CWM installed,
sequence should be;
a. Wipe data/factory reset
b. Wipe Cache
c. Wipe Dalvik
d. Format /system
e. Install JT
Click to expand...
Click to collapse
Great!! Thanks a lot!
Only step I had missed was format /system. I thought factory reset did just that, apparently I was wrong!
Thanks again. Loving my JB on A-501.
Just one issue, Google now voice search doesn't work.
And I noticed there is a phone app. So can I make a call??
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:
Hi,
I have G935F, installed TWRP 3.0.0.0 and rooted, WITHOUT wiping. System boots correctly, but I cannot do factory reset or wipe with TWRP, because I got some messages like "Cannot mount Data" and "Failed crypto loader". I understand that it has to do with encryption. Can someone please enlight me, and give me tips about the issue?
Thank you
Polemos82 said:
Hi,
I have G935F, installed TWRP 3.0.0.0 and rooted, WITHOUT wiping. System boots correctly, but I cannot do factory reset or wipe with TWRP, because I got some messages like "Cannot mount Data" and "Failed crypto loader". I understand that it has to do with encryption. Can someone please enlight me, and give me tips about the issue?
Thank you
Click to expand...
Click to collapse
You have to download dm-verity and force encryption disabler from here , put it to SD card, reboot into TWRP, FORMAT DATA (not wipe) and flash that file (dm-verity and force encryption disabler). All your data will be erased.
No way to unencrypt without loosing you data for the moment(
"All your data will be erased" means that after boot I'll find a clean system installation (as factory reset)?
I hope not to be posing stupid questions, I'm completely new to this world
Thank you very much
Yes just as a factory reset
Sent from my SM-G935W8 using Tapatalk
Ok, thank you all!!! ???
s it very important to wipe data?
Can I first flash the twrp ,second back up the rom by TWRP recovery
and then after factory reset ,I restore thw rom by twrp??
IS IT possible?
AGU PENG said:
Can I first flash the twrp ,second back up the rom by TWRP recovery
and then after factory reset ,I restore thw rom by twrp??
IS IT possible?
Click to expand...
Click to collapse
No, you cannot perform a backup, because your data is encrypted by default and the only way to disable it is to format your data.
I have a unique problem. I have a HTC Desire 612 from Verizon and I decided to revive it to playe PoGo. But it was stuck in a boot loop and I couldn't get any custom ROM.
Finally a gentle soul here gave me the stock rom and I flashed it vide TWRP and played PoGo for weeks. Then yesterday the phone bro led and when it came up it was stuck in a boot loop.
So I decided to flash the stock ROM again. But before that I tried to factory reset. I could go to TWRP, select wipe data, enter yes and the wiping was successful, then clear dalvic and cache and system beforehand finally I flashed the stock ROM.
Surprise surprise is NOTHING happens. The phone boots without the apps telling me they are installing. Then I get back the exact same data in my phone including my selected wallpaper and apps. Before I can do anything the phone restarts.
Point is wiping and restoring the stock ROM does NOTHING to the phone yet the processes are successful. Can somebody help?
vooks said:
I have a unique problem. I have a HTC Desire 612 from Verizon and I decided to revive it to playe PoGo. But it was stuck in a boot loop and I couldn't get any custom ROM.
Finally a gentle soul here gave me the stock rom and I flashed it vide TWRP and played PoGo for weeks. Then yesterday the phone bro led and when it came up it was stuck in a boot loop.
So I decided to flash the stock ROM again. But before that I tried to factory reset. I could go to TWRP, select wipe data, enter yes and the wiping was successful, then clear dalvic and cache and system beforehand finally I flashed the stock ROM.
Surprise surprise is NOTHING happens. The phone boots without the apps telling me they are installing. Then I get back the exact same data in my phone including my selected wallpaper and apps. Before I can do anything the phone restarts.
Point is wiping and restoring the stock ROM does NOTHING to the phone yet the processes are successful. Can somebody help?
Click to expand...
Click to collapse
HTC?? Wrong thread.
B3311 said:
HTC?? Wrong thread.
Click to expand...
Click to collapse
It really is about TWRP failing to wipe