Hi all,
I tried to install cm-11 for my us player 5. It kept failing with a recursive error message. I then read that my version of CWM (v 3.0.x) was too old. I tried using odin to install yp-g70-kernel-r14-cwm.tar (converted from zip using a tool) which has a newer version of CWM. It does connect to the phone but when I click start I get the following messages:
<ID:0/006> at the beginning of each line.
File Analusis
setup connection
initialization
get pit for mapping
firmware update start
meta-inf
nand write start
(blank line)
complete(write) ooperation failed
all threads complete (sucees 0/failed 1)
now the galaxy player is stuck / bricked?
And in the screen have a new icon. a phone on the left/a dotted line with a yellow exclamation mark connecting to a computer on the right.
this icon also shows when i try download mode (vol down and plug computer). computer does beep to indicate connection.
if i try to turn it off, the screen goes blank for a couple of seconds and then this image comes back.
if i try to reboot into recovery mode it just keeps cycling that image on and off....grrr
i
Now i cannot turn it off
any suggestions and help would be grateful.
Thanks!
Terry
I tried using R4 tar and it downloaded to the player. now the player simply says samsung on the display
download mode now works with the "do not turn of target" msg
Now I am able to install R9
now I have cwn 5.
I tried to instal cm11 and I get an error <this is a "herring">
I tried to install my previous cm 10.1...
I wipe everything, etc...
I get assert failed on getprop("ro_product.device") = "YP-G70" || a whole bunch more....
How can I set that or clear that?
Thanks!
terry
Hi all,
Finally got the bugger working. on CM11 (kk4.4). I did alot of trial and error...so it's difficult to know exactly which steps worked.
I copied the yp_g70-kernal_r14-cwm.zip to the device and installed it.
I copied the KKernel_R2.1_USA.zip to the device and installed it.
I copied the cm-11-20140113-iunofficial-venturi.zip and installed it... and turned off assertions
then i was able to boot it up but the 3 buttons on the bottom got stuck lit and did not work (usa version).
I copied and installed the cm11-uskernel_dec24.zip and installed it.. which fixes the buttons
Thanks for listening
Terry
Related
Hi all,
I think I broke my Galaxy S (I9000). I hope you can help me somehow. Here is the history of things I already did/tried
- my phone was working and had cyanogenmod 9.1 installed
- I wanted to give my phone a little speedup and wiped the cache and dalvik cache partition (did this before and it worked before)
- after this, phone was in a boot loop (even the battery loading animation rebooted over and over)
- the download mode still worked, but no recovery menu appeared!
- as given on cyanogenmod homepage in the install guide I flashed ClockworkMod Recovery using heimdall
- after that, recovery worked again
- I copied the cm9.1 zipfile on my phone to flash it, wiped the whole phone (factory reset), but flashing fails at some asserts (even though I disabled asserts) that seem to check that the target device really is a Galaxy S (I9000) (unfortunatly, I do not have a screenshot and cannot provide one now)
- I also had a ClockworkMod backup I tried to recover, but it fails at restoring /system (unfortunatly, I do not have a screenshot and cannot provide one now)
- so I thought, maybe I can use a regular firmware and flash it with Odin3 (1.87) to make things working at least a little
- started odin, selected firmware and started, but Odin3 got hung at some early point, so I closed Odin after ~10 minutes (see screenshot odin.jpg)
- when I now start my phone, only two symbols appear which kind of signal a problem with a connection to a (PC-)host which I have never seen before (see screenshot startscreen.jpg)
I tried a lot, but now I am out of ideas. Can you help?
Robert
missing attachments
Missed the attachments. Here they are.
Robert
Turn off phone, remove usb cable from pc if it's connected, remove battery, wait around 10 seconds, while battery is still not in the phone press the button combination for download mode. While u still holding the button combination for download mode, force reinsert the battery. Now phone should go into download mode automatically. Connect cable to pc and phone and flash stock Rom via Odin. Good luck
Worked! Great! Phone is back in download mode. Unfortunatly my work pc does not detect the Samsung composite device so I have to wait until I am back home. I hope Odin is working then. As given, it did not when I last tried.
Can you tell me what kind of mode this is, when those two symbols appear?
Robert
It's not any mode, it just an indication that earlier download mode flashing via Odin failed or interrupted by user.
U probably need to kill Kies process via Windows task manager before flashing with Odin because it's known to interrupt Odin, make it hung at setup connection.
Hi,
brought my phone into download mode again and this time odin flashed succesful. However, Kies was never installed on this computer so I have no idea why it worked now.
After flashing the phone rebooted, but stated several errors. They are similar to those which appear on reflashing with the cm91 zip via recovery mode ( "unable to mount ... (file exists)" ). I have made a screenshot and attached it. You have an idea how to help?
I have tried both the 512 and the 803 pit file, same results.
Thanks,
Robert
Tried to re reboot after those errors, but the S-Animation of the stock rom during boot never ended.
Robert
I took another stock firmware, JVI, which contains also a CSC and PDA image. Flashing worked, phone booted, Works!
I will see how to come back to my cm91, but a great step forward .
Thanks,
Robert
Made it back to cm91 . Thank you for your support.
Here are the steps ...
- applied I9000XWJVI.zip with 512 pit and repartition (2.3.3 based german stock firmware)
- applied I9000XWJW6_I9000DBTJW2_DBT (2.3.6 based german stock firmware)
- applied cf-root-xx_oxa_jw4-v4.4-cwm3rfs.zip as this clockworkmod recovery is able to disable verifications before appling a zip
- applied cm91 zipfile
- restored my backup
Robert
Hi guys,
little bit of background on the phone, had it since new close to 2 years away (2 year contract and im 7weeks from an upgrade) the phone is on orange (well EE now)
Basically when I turn my phone on it is stuck in a force close loop, with loads of different messages appearing, such as;
(process com.sec.android.provider.logsprovider)
calenders, messaging etc etc
So I have tried going into the boot mode, by pressing volume up, home screen and the power button.
Then when I try to reboot it comes up with the error messages;
e:error in /data/log/recovery_log.txt (read-only file system)
(read-only file system)
e:copy_kernel_file :: Can't Open /data/log/recovery_kernel_log.txt
Rebooting...
It then just continues onto the normal home screen, then when I enter my swipe code it comes up with the force close loop again.
Any solutions to this problem, Or will I have to factory restore, or is completly broken? Im not due an upgrade for about 7weeks either
Would rather not have to factory restore if possible as I have some files on there I dont want to loose, but if its unhelpable so be it
Thanks in advance guys!
Cheeky little bump, Anyone know a fix to this?
Have similar problem...
I believe a factory reset will fix it...sorry to hear you losing files though..
I have a similar problem. I should probably make a new thread for this though...
Background: Samsung Galaxy SII 1900 bought October 2011. Yesterday flashed a stock ROM for the phone and everything was working perfectly. This is probably not related but have been trying to install a working version of Android Keyboard which has gesture typing working for other languages than English, German, Spanish and French and so some hours before this happened I tried to flash a zip with that but it turned up "e: signature verification failed" so I pretty much gave it up and the phone was still working. Then I decided to install another recovery mode on the phone cause that should allow me to install without verification. So I downloaded the one for SGS2 at clockworkmod com rommanager and put it in on the SD card. Then I shut down the phone and this is the weird part: First I accidentally pressed the power button first so I realised the phone was gonna boot normall so I pressed the power button again to force shut it down. I pressed for quite a long time and then it just restarted and I'm at a boot loop where it says Samsung Galaxy S II with white text on black background.... Then suddenly after removing the battery and trying start several times it booted normally. So I just continued where I left off going to make a backup in Titanium Backup before flashing CWM and suddenly the phone just restarted and I got into the boot loop again. I am able to enter Download mode and Recovery mode but the phone no longer starts. Been trying like 30 times to restart it... Now when I entered Recovery mode just now I got the error message
"E:Error in /data/recovery_kernel_log.txt(Read-only file system)" in red letters... and that's where I'm at now.
Here's a sitty picture of it from my HP Chromebook webcam ******* (Google Drive) Edit: Not allowed to post links in first 10 posts
Hello,
Some threads with similar issues are already around, but I didn't find one with the same problem as me.
What I was doing when the issue happened:
I was trying to install cyanogenmod from the isntaller method (apk isntalled on the phone, application running on windows that installs it automatically). At certain point, it rebooted the device and the cyanogenmod logo was on the screen. After a while, the program gave an error "'We couldn't talk to your phone' - Samsung devices ONLY", which is described in their wiki. So the pc lost connection to the phone.
What I did:
1 - Since I had installed the clockwork recovery and tested it before, I thought "hey, no problem. I'll hust recover this S*it". So I disconnected the SIII from the PC and tried to enter recovery mode pressing "volume ip + home + power". While I have these pressed, the phone in in an infinite loop on the initial screen showing the brand and model. When I release them, it goes straight to the cyanogenmod blue creepy robot just there staring.
2 - Since that didn't work out since I now don't have a recovery mode and I don't have any functioning rom either, I found several tutorials for using Odin and reflashing and or repartitioning. PROBLEM: Odin seems to recognize the phone (com port), I click on the option and... FAIL!
2.1 - What I have tried: Different Odin versions (1.83 and 3.09), stock drivers from Kies, Zadig drivers.
So. There you go. I pretty much exhausted everything I could get from my head and interpret from google. So, No recovery, no ROM, fail at odin.
Any ideas?
Thanks in advance.
Remove kies from the pc reinstall drivers and flash a cwm recovery. From there flash a custom rom in recovery from ext sd. Odin 3.04 is good. I would keep trying to get into recovery though. Do you have that red mark in the corner on Sammy splash screen?
Okay, so this is my story. I had cm11 m8. Everything was fine until, two days ago, he turned off. I tried powering on but nothing - bootloop. I entered cwm to make backup and reinstall it. When I tried, it showed error: can't backup /data or something like that. But that is the point where it would stop. Then I tried flashing CWM through Odin but that failed. It started processing zImage, wrote NAND write start and after some time it reported error: Complete(Write) Operation failed. All threads completed (succeed 0 / failed 1). I disconnected my phone and pressed the power button to try and go to CWM and reinstall ROM. But this time, CWM was gone. So I was stuck with only download mod available. I tried again in Odin, this time to flash stock rom but again, the same error appeared. I tried several times but nothing. But Samsung logo was lost and "firmware upgrade encountered an issue.." screen appeared. I tried to intall Kies but it won't start. At startup it displays an fatal error. Tried flashing the .pit file again, same error poped up. Then I tried downloading GB rom with .csc, .pit, kernel and rom files to flash them all together. But, once again, it showed the same error. But I got the Samsung logo screen back, only this time without roor.
Please, but please can someone help me with this?
I have a Samsung galaxy prevail LTE (sm-g30p) that isn't finishing its boot. It goes into recovery and into the Odin thing but It won't fully boot up, it just stays stuck on the SAMSUNG thing. I have no idea how this happened, I just took it out of my pocket and it was like that. I think maybe I pressed something while it was in my pocket. (I was watching a video file using the default video player and the screen doesn't turn off when you press off it just ignores all touches unless you tap the lock icon at the top.)
I don't think my phone is rooted, I don't remember if I successfully rooted it or not. My computer won't recognize it when it is plugged in. It gives me the "can't recognize USB" error. I've tried using ODIN and ADB but they can't detect it. I've also tried flashing TWRP and a debrick image from a MicroSD but it won't work. I even used win32 disk imager. Every time I try to update from external storage it gives me this error:
Applied the CSC-code: XAS
did not match sized '/system/csc/common/system/csc/others.xml' (No such file or directory)
What should I do?
I could just factory reset it but I wanna get my files off of it first
TWRP I used: https://forum.xda-developers.com/galaxy-core-prime/development/twrp-2-8-7-0-sm-g360p-t3462592
Image I used: https://forum.xda-developers.com/general/help/samsung-sm-g360p-recovery-brick-t3248692