I have an old Samsung 5670 and decided to flash cyanogen 11. I successfully installed clockwork 6.0.4.5-beni and then i flashed cm-11-20140116-NIGHTLY-beni, wipe data, wiped cache and dalvik and everything worked just fine. And then, dissaster came: i tried to install gapps and since then (i got a message that flashing was successful) and since then, everytime i turn on my phone i can only enter into the os but the only thing i see is battery status and time on the upper right corner and the rest of the screen is black. I can swipe from the top (i can see the date and time and a "emergency calls only" message).
I tried wipe data/factory reset from recovery, wiped cache and dalvik, i even re-flashed cm 11 and i am still having the same issue. I tried to flash a different rom (miui 2.4.20) but im getting an "installation aborted" message. Even tried to flash the stock rom with odin but though i have installed the usb drivers odin can not "see" my device.
And yes, i was stupid enough not to take a nandroid backup
So now what? Is there a way to fix this?
Related
I was following a guide to root and flash a ROM for my LG Optimus V. I got to the step where I wipe data/factory reset, cache, and dalvik-cache, but I decided to continue the guide later and powered off my phone and ended up in fastboot. I got out of fastboot by installing the zip files for BACKside ROM from the recovery menu, so now my phone works but a few things are off like I can't receive calls, getting server errors on google play, and getting an error that com.phone.android stopped working. I'm not sure what to do next to resolve those issues.
Edit: I realized that before installing BACKside, I didn't wipe caches or format anything since I had done them before my phone went into fastboot. Does this make a difference and means I need to re-install BACKside (by wiping caches, formatting, and then flashing)?
flowerTea said:
I was following a guide to root and flash a ROM for my LG Optimus V. I got to the step where I wipe data/factory reset, cache, and dalvik-cache, but I decided to continue the guide later and powered off my phone and ended up in fastboot. I got out of fastboot by installing the zip files for BACKside ROM from the recovery menu, so now my phone works but a few things are off like I can't receive calls, getting server errors on google play, and getting an error that com.phone.android stopped working. I'm not sure what to do next to resolve those issues.
Edit: I realized that before installing BACKside, I didn't wipe caches or format anything since I had done them before my phone went into fastboot. Does this make a difference and means I need to re-install BACKside (by wiping caches, formatting, and then flashing)?
Click to expand...
Click to collapse
1)maybe the rom and ur baseband don't match
2) maybe bcoz u didn't wipe so ders problem
3) or the rom itself has prob
so do a full wipe including formatting system.
My P5100 had CM10 nightly on it and was running fine until I upgraded to the latest version of CM10 after wiping the cache & Dalvik cache. After the upgrade I couldn't get Google Play to run even after wiping its data and fixing permissions so I tried to do a CWM restore. Unfortunately there was a fault restoring the Data partition and now my tablet is stuck at the animated bootscreen. If I long-press the power button it powers off but immediately restarts. There is no way to start in in recovery or flash mode. I've plugged it into my PC and the Samsung Android ADB interface is showing but the other references to the tablet all have a yellow triangle in Device Manager. I'm hoping some clever person can help me rescue the tablet with ADB. Thanks!
dwl99 said:
My P5100 had CM10 nightly on it and was running fine until I upgraded to the latest version of CM10 after wiping the cache & Dalvik cache. After the upgrade I couldn't get Google Play to run even after wiping its data and fixing permissions so I tried to do a CWM restore. Unfortunately there was a fault restoring the Data partition and now my tablet is stuck at the animated bootscreen. If I long-press the power button it powers off but immediately restarts. There is no way to start in in recovery or flash mode. I've plugged it into my PC and the Samsung Android ADB interface is showing but the other references to the tablet all have a yellow triangle in Device Manager. I'm hoping some clever person can help me rescue the tablet with ADB. Thanks!
Click to expand...
Click to collapse
IF CWM is not working use Odin to flash CWM again then use CWM to flash CM10,
You may need to do a factory reset (full wipe) from CWM.
If all else fails use Odin to flash stock JB ROM
DigitalMD said:
IF CWM is not working use Odin to flash CWM again then use CWM to flash CM10,
You may need to do a factory reset (full wipe) from CWM.
If all else fails use Odin to flash stock JB ROM
Click to expand...
Click to collapse
Thanks but Odin cannot see the tablet to re-flash the recovery.
Downlods mode
Then flash new firmware
sembre said:
Downlods mode
Then flash new firmware
Click to expand...
Click to collapse
That's the problem - I cannot access download mode
UPDATE - it just started in download mode! I can manage from here!!
Just for the record you can install adb on the pc and run the command 'adb reboot recovery'. This will force the tablet to reboot in recovery mode.
Sent from my GT-I9300 using xda app-developers app
Jeez, this has taken up most of the day to fix. I came across many problems I have not previously experienced:
1. When the tablet was stuck at the boot animation and I tried to turn it off by long-pressing the power button it immediately restarted. The only way I could get it to turn off was by long-pressing the power button whilst it was connected to my PC.
2. Flashing the stock ROM with Odin appeared to complete successfully but it would never fully boot, it always got stuck at the black & white Samsung screen. Same problems turning it off as above.
3. Flashing CWM with Odin caused the tablet to reboot into the stock ROM which would not load, in the end I had to untick the "reboot" button in Odin, power it off then manually restart with the Vol- & power buttons.
4. The only way I could get a bootable ROM was by flashing CM10 with CWM. I tried to restore 2 previous CWM backups but on each occasion there was an error restoring the Data partition and I got stuck at the scenario at (1). The backups were made to the external SD card with CWM Touch - is the Touch version unreliable?
I would be really interested if anyone could shed any light on any of this stuff!
For how long did you let it install during the first reboot? It happened to me too, and it took about 10 minutes, maybe even more...
Also, did you try in the "Mount and storage" cwm menu the options "format system", "format data", "format cache" and "format preload" options, prior to re-flashing a ROM? I have read somewhere that for a clean install it's better to do this, as it really clears everything that could mess up the system between two different bases ROMs (like CM and stock).
What I do everytime is using in CWM these 4 "format" options, plus "wipe" system, cache and dalvik, then immediately after this I flash with cwm the new "zip" copied on the card. Then the first reboot is much longer than usual, as at this stage it installs the files, rebuild the dalvik cache etc.
Good luck
dwl99 said:
2. Flashing the stock ROM with Odin appeared to complete successfully but it would never fully boot, it always got stuck at the black & white Samsung screen. Same problems turning it off as above.
Click to expand...
Click to collapse
I think I gave it a good 20 mins to boot. When I got up this morning there was an error message saying that there was no room to install any more apps even though I had very few installed. Settings -> Storage would not calculate the space available so I figured that the partitions had become corrupted. I did the step by step format you described and reflashed & it all seems to be OK now.
Hey there guys! Thanks in advance for taking the time if you're reading this... thing is I got totally hooked up on Android since 8 days ago, haven't slept much, I learnt a HUGE LOT in these past days... specially here at XDA... well, what brings me here is the following, learnt to root, to upgrade and do some minor tweaking... and now I find myself addicted to this old Samsung Fascinate I just got, it was an odissey to activate on my local carrier, had to learn to program it myself and all the stuff... well, thing is that Stock rom was kinda like missing something, so I adventured to the unknown... I'm going for KitKat... but I'm stuck at CM10, could flash CM10.1, but the only ROM could be flashed on my phone is missing it's WiFi, and can't find a fix... so... will a lovely soul help me a bit with just a word of wisdom on where to next? below I paste the list of things I've done so far so you guys have any ideas and that way I don't make you guess more than the needed... a zillion thanks in advance!!
1. Started at stock CI500_VZW_EH03_GB_CM.tar.md5 withit's atlas.pit
2. odin'd cwm-recovery-ALL.tar (CwM voodoo lagfix recovery v.2.5.1)
3. flashed root su-2.3.6.1.x succesfully
4. odin'd cwm4_fixed_for_cm7-ODIN (for cm7) and rebooted in recovery again
5. wiped the big 3 (data wipe, cache + dalvik)
6. flashed update-cm-7.2.0-Fascinate-signed.zip succesfully (waited for reboot 5 mins aprox) (no data for my Fassy on CM7)
7. wiped the big 3 again (twice, now CwM is v.5.0.2.8)
8. flashed teamhacksung-ota-eng.BUILD2.zip succesfully
9. automatically back into recovery which turned into v5.5.0.4, now for flashing cm_fascinatemtd-mtd-eng.BUILD14.zip succesfully (not after wiping data, cache and dalvik 2 times each)
10. prompted the msg: installation from zip complete, rebooted and waited for the CM9 to fully boot
11. reboot into recovery again to flash cm-10-20120721-UNOFFICIAL-fascinatemtd.zip after double wipe for the 3 to-wipe elements
12. phone rebooted to CwM recovery v6.0.1.0 and continued flashing CM10, once succesfully booted... back into recovery
13. wiped ONCE only cache and dalvik
14. got error: This ROM uses incompatible partition layout, your /data will be wiped upon installation, run this update.zip again to confirm install", looked for the same ROM and tried to reflash, came to recovery automatically where it reads down below: "CWM based Recovery v6.0.3.3., warning no file_context"
15. rebooted to recovery again, again tried to flash the same CM10.1 file, after a couple of minutes it read: Install from sdcard complete
16. wiped cache and dalvik and after that booted CM10.1, realized I couldn't go to recovery mode... tried and odin'd the CwM4 that came with CM7
17. could enter recovery mode with the the button way, installed gapps-jb-20130812-signed.zip and kernel-Devil_4.2.2_fassy_07-17.zip
18.... started all over, couldn't get past from that point, any of the few ROMS I try for the Fassy give some kind of error (on the third, fourth even fifth attempt of flashing), am I missing something? ohh! btw... can't get TWMP to run properly on my phone... I think that limits me a little more, also, can't get to find the latest CwM v.6.0.6.4 for the Fascinate (if anyone would be so kind with a little direction on the topic, it'd be hugely appreciated!
thanks a zillion in advance to whoever stops by and gives a little help
The Wifi on my phone wasn't turning on, even after factory reset, so I reflashed stock ROM via Odin (v3.07)
I got stuck in a bootloop, and after factory reset via the stock recovery + wipe of cache partition, it was still stuck.
I then re-flashed the stock ROM. Still stuck.
Tried using Kies 3, with the firmware upgrade and installation tab. Said something about not supporting my phone when I was prompted to plug it in. (SM-G355H; Samsung Galaxy Core II Duos)
I then found an unofficial version of CWM v6 for my phone (there's no official support), and quickly flashed that (via Odin 3.09; which is what I use from this point on), forgetting that my phone was no longer rooted. I wiped davlik cache and data. Still stuck. Then I rooted my phone. Stuck.
Then I reflashed stock ROM (this time, I downloaded from another website) (to test my luck, I tried seeing if simply a factory reset and cache wipe would work. It did not) rooted my phone, and flashed CWM. Wiped davlik cache. Still stuck.
By the way, when I wipe davlik cache it says:
Warning: no file_contexts
E:unknown volume for path [/sd-ext]
Davlik Cache wiped.
Any ideas on what to do now? I can't send it to a manufacturer / repair store where I live. I'm thinking maybe I should untick Auto Reboot and/or F. Reset Time when flashing, use an earlier version of Odin or the ROM itself, or maybe there is something I can do with ADB? I'm not very familiar with it, but I'm more than willing to learn. I just need some direction...
Update: Flashed with Auto Reboot unticked. Still in bootloop.
Flashed with same ROM, different country. Still in bootloop.
Alright, I fixed it by using Kies, via firmware upgrade and installation. You have to ignore where it says that your device is not supported, and just leave it to download. If you get stuck on the setup screen like I did, try cache wipe + factory reset. If it doesn't work flash an earlier version of the firmware. You might be using the wrong region (It's not always your country), use Kies to check. When it tells you what pda/ modem / csc it wants to update the region will be in parentheses ( eg ACR). Use all of them possible
After searching through countless threads on this site, I've had no avail in resetting my Rogers Samsung Galaxy S6 running XtreStoLite 2.2.
A little while ago, I thought it would be a good idea to encrypt my phone with a custom ROM installed. I knew I had recovery and download mode, so I thought It'd be no biggie. Left the phone on overnight encrypting, came back 24 hours later and knew that it hung somewhere. Booted it up and this screen came up: Reset it and restored from TWRP backup, the same screen right here came up: http ://i.imgur.com/J37aZaq .png (sorry XDA will not let me post links, remove spaces) after this, I tried pressing the "reset device" button without success. It just rebooted the phone. Tried to restore from a different backup, no avail, then I tried to flash my custom ROM again through TWRP, no avail. I download ODIN and flashed stock Samsung firmware onto it and it still gave me this screen when I was done. Tried going into TWRP and factory resetting (where it wipes all partitions) and nothing happened. Currently, I'm trying to flash my Samsung Galaxy S6 with the stock firmware through ODIN with the "re-parition" box checked.
It seems there's a hardware flag of some sort stopping this from working. I mean, my file system is brand new, reset to factory defaults, I even checked with ADB and everything has been formatted. Checked with TWRP file manager and everything is good. But I can't get past the "Encryption Failed" screen.
Help me! Thanks.
fix
did you fix this?
Hi, i am encountering the same problem with my G920F.
I have the XtreStoLite_Deo_Mod_v.2.3 and also TWRP installed
I started encrypting but it got stuck so i rebooted my phone and got the same message (Encryption failed, please do a factory reset). So i did the reset but the same screen appeared. I also tried restoring from a back-up from TWRP but the same screen was still there. So i decided to do a full wipe and restore the phone with a twrp back up witch was on my laptop. But when i am in TWRP i can not copy files to (or from) my phone. So it is not possible to get the backup on my phone. I am able to get in to download mode and connect the phone with odin.
My questions are :
- what was the solution to the problem?
- What causes the copying error? And what is the solution? So i can put the backup on my phone and try to restore it this way.
- What are my option with odin? Can i use the TWRP files in odin?
Thanks a lot in advance
Jules
Solved the issue. After a full wipe i installed a stock firmware with odin. It still displayed encryption failed after reboot. But after the factory reset the notification was gone.
I have fixed this
Best solution is on a stock rom to reset. If rooted with recovery -format and wipe all data, reset, let sit at boot for a while, go into recovery and install new rom from USB-OTG, or odin from download mode.