Rom: cm11.0_golden.maclaw installed
My S3 Mini works. But every change is undo after reboot.
I can do every thing - uninstall apps, write files, ... but after Reboot is all lost
The recovery (TWRP) has no effect too.
Wipe runs - but nothing happen.
I decide to flash the complete rom with odin - the same problem.
Odin run - no error - no change. >> I boot and every thing is in the same status.
Please Help.
Related
hey all, so I have my first brick. I thought I knew what to do.
This is what happpened.
1) was running inception 1.2
2) was flashing Continuum 4
3) in CWM I select the zip and go ahead.
4) CWM says:
E: failure at line XX: copy_dir PACKAGE:system SYSTEM: Installation aborted
[the "XX" is a number - was 21 for Inception, 11 for Cognition]
Alright ...
Tried this:
1) restore system
- completed successfully, did not boot
2) restore boot, system and data
- completed successfully, did not boot
3) flash different roms, including Inception 1.2
- fails the same way as above
When I try to boot up, I see the ATT and the Inception's Samsung screen - never get to a boot animation.
Help?
ODIN back to Stock?
Sent from my SAMSUNG-SGH-I897 using XDA App
FIXED:
per further searching:
- problem is with recovery
- flash new kernel in ODIN
- get a new ROM in there.
- Flashed to Cognition, will give me time to stop sweating, and then move to continuum as I had intended.
Cheers.
Yeah ... I tried to fix it in CWM - but went to Odin and it was all good.
Hi,
I'm having a major issue with not being able to flash roms using clockworkmod for some strange reason.
I decided to move from MIUI rom because every time I gave it a chance when new versions came out, it constantly let me down with countless bugs and such. So, I've decided to go back to modified stock ROMs as they seem more reliable.
When I attempted to flash using clockworkmod (that comes with MIUI) it failed to apply the new (non-MIUI) ROM and forced it to go into a bootloop which knackered up going into recovery, so my only other option was to go into download mode and flash a stock ROM (I chose the latest, I9000XXJW4), root it, flash cyanogenmod and try again.
But unfortunately this did not work and now I'm stuck on the stock ROM.
I've taken a video of the exact moment it all goes wrong. Also, below is each step taken of the process.
youtube.com/watch?v=EmZAZ3DeL2U
1) Download Samsung Value Pack (I9000XXJW4) and CF-Root-XX_OXA_JW4-v4.4-CWM3RFS
2) Galaxy S rebooted to download mode
3) Used Odin3 1.85 to apply JW4_JW4_JW4.TAR file to the PDA section. Re-Partition is not checked.
4) Allowed the device to reboot to the home screen.
5) Powered off the device and booted back to download mode
6) Used Odin3 1.85 to apply CF-Root-XX_OXA_JW4-v4.4-CWM3RFS.TAR to the PDA section. Re-Partition is not checked.
7) Allowed the device to reboot to the home screen (The video begins now).
8) Launched the CWM application (with root permissions) and rebooted to Recovery.
9) Wipe data/factory reset selected and confirmed
10) Wipe Dalvik Cache selected and confirmed
11) Format /system selected and confirmed
12) Install zip from SD Card, Choose Zip from sdcard and update-cm-7.1.0-GalaxyS-signed.zip selected and confirmed.
13) Here is an extract from the log that follows before rebooting:
- Finding update package...
- Opening update package...
- Installing update...
- Checking state of BML/MTD...
14) Self-Rebooted
15) Boot-loop
Any help is greatly appreciated!
Thanks,
Andy
when it bootloops it does it cause it just flashed the kernel and its trying to run the stock rom on the cynogen kernel. so pull the battery, put it back in. reboot into recovery and flash the rom again. it should work the second time cause its using the cynogen mods version of cwm recovery. let it boot it will take a while. but that should work.
dont forget to hit thanks!
taz0697 said:
when it bootloops it does it cause it just flashed the kernel and its trying to run the stock rom on the cynogen kernel. so pull the battery, put it back in. reboot into recovery and flash the rom again. it should work the second time cause its using the cynogen mods version of cwm recovery. let it boot it will take a while. but that should work.
dont forget to hit thanks!
Click to expand...
Click to collapse
Genius!
Thank You!
Cannot believe the solution was staring at me the entire time!!
YABLP (Yet Another Boot Loop Problem)
Hi,
I'm having a devil of a time installing CM7 on my GalaxyS I9000. Description of my procedure and problem below.
I've been beating my head against a wall for a week so any help GREATLY appreciated.
-John
Phone: Galaxy S "I9000"
Trying to Flash: CM7.2.0 using CWM Recovery
What I did:
Flash stock ROM w/ODIN v1.85 - OK
Wipe Data/Wipe Cache
Flash ChainFire (CF-Root-XX_OVA_JVU_2.3.6-v4.3-XWM3RFS.tar) w/ODIN v1.85
Wipe Data/Wipe Cache
Phone now rooted OK
Boot to CWM Recovery
Install zip from sdcard
Select update on SDCard (cm-7.2.0-galaxysmtd.zip from CM site)
Flash completes in just a few seconds - much too quick!
Phone reboots automatically
Now stuck in boot loop
Screens in boot loop:
1. GalaxyS/GTI9000/Samsung
2. GalaxyS/Cyanogen(mod)
3. CWM menu scrolls by too quickly to read
Back to 1.
Tried Heimdall but complained about missing XML file
Tried installing "Datafix". Would not install (says not compatible with device)
Tried STFW: many reports of same problem but no solutions seemed relevant & appropriate
Clues:
After CF flash, disk use as follows
/system: used 27.3M, free 9.4M (97%) (seems pretty full)
/data: used 47M, free 1916M (2%) (seems pretty empty)
Me thinks maybe /system is too small/full to accept update?
This is the 3rd I9000 I've flashed. First 2 went Ok but this time it failed although identical files/procedures used (I think).
HELP!
I've seen a similar problem on my I9000 - I think the CWM scroll complains about "can't mount /data".
I'm in a similar position, I can't get anything to flash and boot though : http://forum.xda-developers.com/showthread.php?t=1967982
This happens pretty much every time you flash any kind of CM rom from stock. All you need to do is flash CM7, it will go in to bootloop with various text scrolling through thats too fast to read. You just pull battery while in the bootloop. Then replace battery, three button combo to recovery and flash the same CM7 zip again. This time the install will take a while longer. Afterwards flash gapps and reboot and you should be good to go.
I tried this - but same result, just spins round on the CM boot screen
Where do the wipe data and wipe cache commands fit in to this? Before/after both installs?
I don't normally bother with gapps - just trying to get it loaded. Does that make a difference?
Also, no SIM card in at all during all this...
IT WORKED!
Bless you BandiBp!
I'll be sending my first-born by return mail (please don't tell my wife
Yeah that happens because its flashes a kernel with a new partition system. Dunno why only a few roms warn people about this.
Sent from my GT-I9000 using xda premium
You're welcome mate, yeah the reasons are the new partition changes on different roms. I agree that rom flashers should be warned in advance about this. Would reduce problems A LOT. My general rule is if a Rom installs in under 5 secs, then you should always flash again.
Anyways have fun.
Hello fellas, i really need a help here.
I have a I890L Brasilian with latest updates installed - is the phone of my wife. She was complaining about the slow so i decide check for a CFW or a something. I'm not new on it, i flashed cfw to my smarts since i had a P500, now on Moto G. But the question is:
1º - i rooted the S3 mini follow this thread - How to guide easiest way - and works fine. No problems here.
2º - after it i searched by a CFW and decide by AOKP 4.4.4 (this) but i made a mistake and put the files on sdcard, not external. So when i wipe data/factory i erased it (stupid, i know) and did the follow threads: remove the batery, get the memory card, removed it (to put the files of CFW - aokp4.4_golden.nova.20140805 and [GApps][4.4.2][AROMA]_Aroma_Installer_GApps-v1.5.2 - and while it happens i started the phone. Normally, jsut clean. So enabled the usb debugging, put the memory card back and proceed the 1º step again - in my mind, since imade a factory reset and it stats with the official samsung firmware, was unrooted. The things was normally, works nice and i enter on recovery using the win+adb strategy.
3º - now is the problem. On recovery, i wipe data/factory, wipe cache, installed CFW, root and installed gapps - and now i'm froze on a android logo (it's a bootsplash animation). The question is how i solve it? i don't enable the Three-button combo so i can't back to recovery; but the phone is detected by Odin while on download mode.
Can someone help to solve it and help me to flash a CFW on the proper way?
forget it. i solved flashing oficial firm through odin
Being the complete moron I am, I accidentally flashed Cynogenmod 7.2.0 (Stable version) before installing CWM (v4.0.0.9).
This led to the boot loop. I managed to install CWM with great success, however now I receive error 7 when installing any custom ROM
I have tried:
- Cynogenmod
- TheUltimatum(V4.9)[-The'A'Factor] // With this one, I managed to get the furthest, being able to go into the custom GUI installer, pick the options I wanted, however upon installing I still receive error 7.
- PAC
- Toggling script asserts
- Deleting the phone verification feature in the script, I did this to Cynogenmod, however it did not work. I think trying it again might work but I know that if (for example) it is not the correct ROM I think it is, I'll have a nice paper weight.
- Looked at about 30 different pages claiming to have the Gingerbread 2.3.3 download (I'd be happy to just go back to that at this point, even if it was ugly and slow).
- Used Odin to install a custom ROM, I have Kies which has installed several drivers for the phone. I do not know exactly what it says, but I am able to see the phone in Odin, I am able to choose the ROM and press start, however, once I have pressed start I see it do something for a second, then it gets stuck at SetupConnection.
- Wiping data/factory reset
- Wiping cache partition
- Wiping Dalvik cache (I read in several place this does something..)
I have searched the internet far and wide, XDA has been quite the website with the most help ( Thank you guys ) however they all seem to say the same thing for what I am searching for and that does not seem to work. Or maybe, just maybe, I'm stupid... (Probably the latter)
dideej848 said:
Being the complete moron I am, I accidentally flashed Cynogenmod 7.2.0 (Stable version) before installing CWM (v4.0.0.9).
This led to the boot loop. I managed to install CWM with great success, however now I receive error 7 when installing any custom ROM
I have tried:
- Cynogenmod
- TheUltimatum(V4.9)[-The'A'Factor] // With this one, I managed to get the furthest, being able to go into the custom GUI installer, pick the options I wanted, however upon installing I still receive error 7.
- PAC
- Toggling script asserts
- Deleting the phone verification feature in the script, I did this to Cynogenmod, however it did not work. I think trying it again might work but I know that if (for example) it is not the correct ROM I think it is, I'll have a nice paper weight.
- Looked at about 30 different pages claiming to have the Gingerbread 2.3.3 download (I'd be happy to just go back to that at this point, even if it was ugly and slow).
- Used Odin to install a custom ROM, I have Kies which has installed several drivers for the phone. I do not know exactly what it says, but I am able to see the phone in Odin, I am able to choose the ROM and press start, however, once I have pressed start I see it do something for a second, then it gets stuck at SetupConnection.
- Wiping data/factory reset
- Wiping cache partition
- Wiping Dalvik cache (I read in several place this does something..)
I have searched the internet far and wide, XDA has been quite the website with the most help ( Thank you guys ) however they all seem to say the same thing for what I am searching for and that does not seem to work. Or maybe, just maybe, I'm stupid... (Probably the latter)
Click to expand...
Click to collapse
if you can go in download mode, you can try to install stock ROM (not custom ROM) by odin:
http://live.samsung-updates.com/index.php?device=GT-S5830
daniga74 said:
if you can go in download mode, you can try to install stock ROM (not custom ROM) by odin:
http://live.samsung-updates.com/index.php?device=GT-S5830
Click to expand...
Click to collapse
Try formatting system, cache and data and retry in cwm in advanced settings