First of all, I would like to say hello, since I'm new on this forum!
So, to begin with, my problem is the following: I'm trying to install the CyanogenMod on my vodafone 858 smart. I followed the instructions on this forum:
-rooted my phone
-installed ROM Manager + Clockwork recovery
-in ROM Manager I selected Install ROM from SD card -> checked to make a backup, to wipe data and cache and to wipe dalvik cache
-phone rebooted into recovery mode -> could't see anything but the small hourglass
-waited for more then an hour, nothing changed, hourglass was still there
-took out battery, reinserted it, started phone and everything worked properly, but I still have 2.2 version of Android
-I tried to install CyanogenMod again, this time switching off my phone, and rebooting into recovery mode manually
-after rebooting into recovery mode, a message appeared, saying it is unpacking 1/2 (the process bar not moving anything not even after an hour) and below it states that the 'update has failed'
Could anyone please help me with this issue, I'd really like to upgrade my phone, but I can't seem to manage.
ps.: sorry if this has been asked, I couldn't find a similar thread.
Thank you!
HELP! My phone stuck on boot screen (or boot loop) can someone upload their backup of vodafone 858 phone (or system.img) file???
PLZ HELP My phone dont work...
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
Hello everybody.
I have a huge problem and basicly it is my fault. Yesterday i repartitioned my microSD card and created swap partition. Just to see if it works. I used swapper 2 to activate this. After this operation phone was working as usual (it was official nightly build of CM 10.2 from 19.09.2013). But...when i rebooted, the phone was stuck on Samsung logo (So yes, even CM bootloader didn't start working). It was 1 A.M. so i was nearly sick with this, but fortunatelly CWM and Odin mode were working. So did battery recharge. Odin and battery still works.
I have tried cache wipe, full wipe, installing another CM version (10.1.3 - via CWM), installing official samsung firmware ( I9300XXEMG4 - i checked in odin only Auto Reboot and F. Reset Time) - whcich resulted in removal of CWM. But it is always stuck on samsung logo, so system itself is not booting. Filesystem is more or less OK, because i launched astro file manager from CWM and was able to copy most of my data.
I tried to do adb logcat when it is trying to boot. Windows recognizes device as "Samsung Mobile MTP Device" after ~20 seconds from turning on, but it can't load drivers for it.
Please help. I am really grateful for any answer.
------------------------------------------------------------------------------
Solved. It turned out that /efs was somehow wiped.
Hi, I soft- bricked my phone (recovery mode loads, boot logo loads, phone won't start)
I have MT6572 phone, I can write down specs if needed.
I rooted it, and it was working OK, but then I tried to change status bar images (battery logo etc.) with ROM Toolbox Pro and the phone just shutted down and won't properly start.
I haven't got a backup of my stock ROM, but I downloaded the one that was for my phone model, and I tried to apply it by entering recovery mode, selecting 'apply update from sdcard', and selecting the ZIP file with the ROM, but it just said 'installation canceled' in a few seconds.
Does anyone know how to help me?
Hello xda,
Basically, I am stuck on booting screen. All I see is that blue cyanogen boy. Dammit. I feel so miserable now. I tried everything to solve this problem, yet without any progress. I think I know where the problem is, I forgot to wipe the data and cache before I began installing the Cyanogenmod.
Stuff I tried (the goal was to wipe all the data):
1. Can't get into recovery mode
2. Can get into download mode, yet odin doesn't recognize the device or something
3. Tried to wipe all the data with adb, using adb shell --wipe_data, it says /sbin/sh: --wipe_data: not found
Can anybody please help me? If you need some more details, let me know down in the comments
Hi guys, I really need your help.
I'm new at this rooting stuffs and I tried to root my Oppo Neo 5.
I tried so many softwares like OneClickRoot, FramaRoot, and Kingroot but none seemed to work.
So I resorted to an app called oppo tools
It worked at first but I got really annoyed when my status bar suddenly colored to red when my phone discharges to 15% so I unrooted my phone and rooted back again. I really thought that was going to fix my problem but that's where the bootloop issue started.
I tried to flash some custom recovery zip but it failed since I only have a stock recovery.
But the thing is, I found a guide that says to rename the clockworkrecovery img to PG86IMG.zip.
So I did tried that and as soon as I flashed the zip from my stock recovery, my phone hanged.
I long-pressed the power button to restart and boot into recovery mode but nothing seems to happen.
I'll try to explain a bit more on how it looks when I boot my device.
When it boots normally (I mean not pressing the volume to enter recovery mode) it will only show the logo but when I try to go into recovery mode it will show the logo with a little text on the lower left portion "Recovery Mode"
Before I flashed the PG86IMG.zip, recovery mode was still working and the charging screen when off is working too.
but after I flashed the zip, every time I try to recovery mode the logo shows up with the little text but RECOVERY MODE isn't working. When I charge my phone it automatically boots up and shows the logo and text like it's trying to go recovery mode (I'm just trying to charge? It's going to recovery mode)
I tried using "adb devices" on cmd but it's not detecting any devices.
I'm really out of ideas guys, I know not all people use this model but what would be your suggestion?
A suggestion on how to fix this would really be appreciated :good:
I'm sorry I'm really new at this, please correct me if I did something wrong starting this thread. :angel:
@DeepBricked please confirm your problem, Boot-loop and can enter into recovery.
Salman Al-Badgail said:
@DeepBricked please confirm your problem, Boot-loop and can enter into recovery.
Click to expand...
Click to collapse
Oh, I'm sorry, I didn't notice.
Lately I can't access the recovery mode but now
I'm currently on Boot-loop and I can enter into recovery.
The ColorOS recovery mode only have limited function that I can mess around.
It only has the apply update, wipe data and cache, reboot, power off and system file verification.
As always I already did wipe the data and cache but nothing happens. Still boot-loop.
What should I do?
DeepBricked said:
Oh, I'm sorry, I didn't notice.
Lately I can't access the recovery mode but now
I'm currently on Boot-loop and I can enter into recovery.
The ColorOS recovery mode only have limited function that I can mess around.
It only has the apply update, wipe data and cache, reboot, power off and system file verification.
As always I already did wipe the data and cache but nothing happens. Still boot-loop.
What should I do?
Click to expand...
Click to collapse
You made a soft brick, not to worry flash it with correct stock firmware, if the phone is in warranty than ask them to do flash, this will take approx 10-30min. If it isn't in warranty than you should try it own or else pay some amount and the rest they will do.
Salman.
how about bootloop, cant enter recovery, reboot continiously when turn on even going to recovery, only fastboot isnt rebooting automaticaly but pc days drivers not succesfuly installed, and when off it qont detect by pc because of rebooting auto,
where can i find a rom for my oppo neo 5
pls help me pls