Hey i got my oneplus one yesterday from oppomart and had to flash cm11s so that worked ok and when i tryed to flash cm11 nightlys it always fails no matter which recovery
Md5s is ok
But the weird thing is the snapshot flashed ok?
Anyone
More information required. What error are you getting?
Sent from a crappy Samsung because my Evita died
Status 7 but is not a bad download is happening every rom
What's the full filename of the ROM zip?
Sent from a crappy Samsung because my Evita died
What do you mean its off the cm website and not even cyanogenmod not works only snapshot i wouldn't mind but on the snapshot rom my home button stops working for some reason
I asked for the filename, not where you got it from, not what's happening. The filename.
Sent from a crappy Samsung because my Evita died
Check this, same problem. http://forum.xda-developers.com/showthread.php?t=2829943 /URL]
Sent from my One using Tapatalk
Related
Hey so when I update my phone from a nightly from August to a nightly in September I keep on getting random force reboots. I managed to flash to the experimental M1 nightly and i'm stable there, but anything past that and I get force reboots (my phone randomly shuts off).
Any help would be greatly appreciated! Thanks!
Are you sure it is due to CM? I have the same issue with the stock Rom rooted.
Well it only happens on any nightly past the experimental M1.
Have you tried a clean flash? Or have you just been doing dirty flashes over and over?
Yeah, I tried a full wipe then install last night.. didn't get a force reboot for about an hour but then after that it went back to "normal" and happened like every five minutes.
Thank God i made my back before I installed cm10 i had and still have the same issue, so i went back to stock+root if anyone know the fix post it thanks
kevin2005 said:
Thank God i made my back before I installed cm10 i had and still have the same issue, so i went back to stock+root if anyone know the fix post it thanks
Click to expand...
Click to collapse
Same here I had tested e different rom and mostly reliable I found was DarthStaker v7. But looks like samsung did something with the new s3 hardware because before my phone replacement my first s3 was smooth as a butter with any rom but now is a pita toget it shorted out with new rom. Stock+root works way better that any rom.
Sent from my SGH-T999 using xda premium
I tried the CM updater, like I have been for the nightlies, except, now I'm stuck and a bootloop and I can't get into recovery. I go from the bootloader and select recovery and it takes me to the same screen that the updater does where it says:
Updating partition details....
Running boot script....
Finished running boot script.
Installing zip file '/sdcard/cmupdater/cm-10-20121110-NIGHTLY-evita.zip
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
This is the screen I get every time I flash nightlies, then I reboot and my phone boots normally, but, now when I do this, it puts me in a bootloop (HTC screen comes up, goes dark, no Cyanogen screen, then reboots to the HTC screen and goes to a dark screen...you get the point)...any thoughts on what I need to do to get my phone to work again?
CM10 Nightlies 20121110
First of all I love CM but Ive been having an issue with it. Ok so I flash the rom everything goes fine as far as that goes but Im having call issue. I can hear the person Im calling but that person cannot hear me. When I put the caller on speaker I cant hear him and that person still cant hear me, then the phone freezes. Im no developer but i have flashed plenty of roms so Im literate to this stuff. Some help or tips would be great as I love CM10 and havent been able to use any CM10 based roms they all do the same. I have an At&t One X unlocked, rooted, unlocked bootloader 1.14...
Rising32 said:
First of all I love CM but Ive been having an issue with it. Ok so I flash the rom everything goes fine as far as that goes but Im having call issue. I can hear the person Im calling but that person cannot hear me. When I put the caller on speaker I cant hear him and that person still cant hear me, then the phone freezes. Im no developer but i have flashed plenty of roms so Im literate to this stuff. Some help or tips would be great as I love CM10 and havent been able to use any CM10 based roms they all do the same. I have an At&t One X unlocked, rooted, unlocked bootloader 1.14...
Click to expand...
Click to collapse
Try flashing the previous boot.img then install the latest nightly. I've seen a few people have problems and that normally fixes it.
If that doesn't fix, re download the latest nightly and flash it. Could be a bad dl
Sent from my HTC One XL cellular device over clocked to 1.9Ghz
I had the same problem just like u. I flashed back to 1109.
Sent from my One X using xda app-developers app
So every time I get a newer version of CM10 do I need to flash the boot.IMG first then flash the ROM or is it OK just to flash the ROM with my existing boot.IMG? I mean does the boot.IMG change? I have been just flashing the zip file without the boot.IMG just keeping the original boot.IMG from one of last months update.
Sent from my One X using xda app-developers app
always flash boot.img with any new build, unless your using a custom kernel
cm10 call issue
Myrder said:
Try flashing the previous boot.img then install the latest nightly. I've seen a few people have problems and that normally fixes it.
If that doesn't fix, re download the latest nightly and flash it. Could be a bad dl
Sent from my HTC One XL cellular device over clocked to 1.9Ghz
Click to expand...
Click to collapse
So ur saying flash the previous nightly's boot image??? Thanks if that's the case then I will try it and report back. I've tried several CM10 based Rome they all have the same issue... Is it just my phone??? Is it something in the CM code that needs to be fixed? I mean one Rom is one thing but every one Ive tried so far lol. That's what I get for loving asp lol.
---------- Post added at 02:49 AM ---------- Previous post was at 01:52 AM ----------
Myrder said:
Try flashing the previous boot.img then install the latest nightly. I've seen a few people have problems and that normally fixes it.
If that doesn't fix, re download the latest nightly and flash it. Could be a bad dl
Sent from my HTC One XL cellular device over clocked to 1.9Ghz
Click to expand...
Click to collapse
Well I tried ur suggestion and nothing... re-downloaded the lates nighty and used previous boot image, nothing. Wiped cache and reflashed the rom and still nothing.
I recently bought my girlfriend a galaxy s II skyrocket. I own one myself. I updated my phone successfully and easily to jellybean through the official CM10. I am well aware of the different methods to install different custom roms to your phone. I received my girlfriend's phone with stock gingerbread. I proceeded to install the stock ice cream sandwich update to the phone through Odin. It was successful. I also installed ClockWorkMod recovery into her phone, the exact same one I had. I continued to attempt to install the same rom that I had on my phone, to my girlfriends phone, CM10. CWM said it was a successful installation after the careful 3x: Factory reset, Cache, Dalvik Cache. Upon rebooting of the phone however, the phone would fail to successfully turn on. It would stay in boot loop mode forever. One time I even left it for an hour and there it was, the boot screen I so dreadfully began to hate. I gave up on CM10, so i began to look for other prospects of a rom. I discovered slim bean. I installed it into my original phone to test it and found it to be of great quality. After I followed the exact same steps I followed to install slim bean to my original phone, to my girlfriends phone, the same result came about; boot loop. After about 20 tries, seriously, I tried to find yet another prospect of a rom. I also discovered another slimmer version of jelly bean for the Skyrocket. Even after the careful following of the steps, I encountered the same result; boot loop. I am beyond frustrated at this point at the fact that I am holding two phones exactly the same, yet when I attempt to install the rom, it only works on one of them. They are both Samsung Galaxy S II Skyrockets model numbers 1727. Both based off of At&t in the United States. One is white while the other one is black. If it makes any bit of a difference the phone I am having trouble with is white. I need help. I've tried everything with no success. I am trying to update this phone to jellybean but it does not seem to accept it, and I have no idea why
Re: [Q] Stuck on boot loop after several different jb roms
TLDR condense give important details that's it
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
TLDR condense give important details that's it
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Sorry, I am not yet familiar with all the terms. It seems like jargon to me at times lol. TLDR Condense?
Re: [Q] Stuck on boot loop after several different jb roms
Nobody knows what version of cwm you're on.
Nobody knows where you're dl'ing cm10 from.
Quit wiping 3x you only need to do it once.
Don't write novels.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
---------- Post added at 03:10 AM ---------- Previous post was at 03:09 AM ----------
Tldr means to long didn't read
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
Nobody knows what version of cwm you're on.
Nobody knows where you're dl'ing cm10 from.
Quit wiping 3x you only need to do it once.
Don't write novels.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
---------- Post added at 03:10 AM ---------- Previous post was at 03:09 AM ----------
Tldr means to long didn't read
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I've tried installing Official CM10.1 (from XDA) with boot loop result. I've tried installing unofficial 4.2.2 slimbean (from XDA) with boot loop result. I've tried installing Skyjellybean 4.1.2 update 11.4 (from XDA) with boot loop result, and finally I've tried installing Superlite CM10 JB 4.1.2 v8.0 (from XDA) with boot loop result as well. I am currently on stock Ice cream sandwich installed through Odin (links and all found from XDA)
Agree with mtdew.
Keep it as short as possible and be specific.
Get CM10 (not CM10.1 as it's still unstable) from http://get.cm/?device=skyrocket .
Also try latest CWM http://forum.xda-developers.com/showthread.php?t=1777970 .
lingowistico said:
Agree with mtdew.
Keep it as short as possible and be specific.
Get CM10 (not CM10.1 as it's still unstable) from http://get.cm/?device=skyrocket .
Also try latest CWM http://forum.xda-developers.com/showthread.php?t=1777970 .
Click to expand...
Click to collapse
I discovered the issue! Even if it was the same recovery as my other phone i used to install these updates successfully, it was the recovery that was broken. I installed a different version the latest "touch" version of Clockworkmod and to my surprise, the update was successful. I am running 4.2.2 unofficial slimbean! Thanks guys, for your help.
s3rgioru3las said:
I discovered the issue! Even if it was the same recovery as my other phone i used to install these updates successfully, it was the recovery that was broken. I installed a different version the latest "touch" version of Clockworkmod and to my surprise, the update was successful. I am running 4.2.2 unofficial slimbean! Thanks guys, for your help.
Click to expand...
Click to collapse
That is good news, i'm glad it worked out for you. Good luck. :good:
Help
s3rgioru3las said:
I discovered the issue! Even if it was the same recovery as my other phone i used to install these updates successfully, it was the recovery that was broken. I installed a different version the latest "touch" version of Clockworkmod and to my surprise, the update was successful. I am running 4.2.2 unofficial slimbean! Thanks guys, for your help.
Click to expand...
Click to collapse
I too Have a Bad Recovery . Every time i try to install ANY jellybean rom i get stuck in boot loop . I Tried different recovery's and different rom's and stock jellybean and no success . But any ics or gingerbread installs normally . I have a epic 4g touch galaxy 2 and it's rooted . Any new idea's what it could be or how to fix it ? I feel i'm the only person with this problem since i cant find anyone else with the same situation . Your the closets to my problem
Cisco408ca said:
I too Have a Bad Recovery . Every time i try to install ANY jellybean rom i get stuck in boot loop . I Tried different recovery's and different rom's and stock jellybean and no success . But any ics or gingerbread installs normally . I have a epic 4g touch galaxy 2 and it's rooted . Any new idea's what it could be or how to fix it ? I feel i'm the only person with this problem since i cant find anyone else with the same situation . Your the closets to my problem
Click to expand...
Click to collapse
Use the latest recovery in your forum
Sent from my HTC One using Tapatalk 4
So I just rooted my phone and flashed cyanogen cm10 for my Blaze. It worked flawlessly for the first 2 days but then suddenly would either freeze for a few seconds and shut off or just plain shut off on me. It happens randomly like it doesn't happen during anything specific. I searched Google and the forums but couldn't find a solution. Please can someone help me out?
Sent from my SAMSUNG-SGH-T769 Cm10 using Tapatalk 2
Daze7 said:
So I just rooted my phone and flashed cyanogen cm10 for my Blaze. It worked flawlessly for the first 2 days but then suddenly would either freeze for a few seconds and shut off or just plain shut off on me. It happens randomly like it doesn't happen during anything specific. I searched Google and the forums but couldn't find a solution. Please can someone help me out?
Sent from my SAMSUNG-SGH-T769 Cm10 using Tapatalk 2
Click to expand...
Click to collapse
Are you running the latest nightly or the 'stable' build? The 'stable' build (note the "") isn't that stable and from the sound of it you are experiencing the screen of death (SoD) that I believe is present in the 'stable' build.
If you flashed the 'stable' build, flash the newest nightly instead. Or better yet, head on over here and also flash this (it's better than CM10 IMO - Just be sure to flash the kernel AFTER the rom). :good:
Daze7 said:
So I just rooted my phone and flashed cyanogen cm10 for my Blaze. It worked flawlessly for the first 2 days but then suddenly would either freeze for a few seconds and shut off or just plain shut off on me. It happens randomly like it doesn't happen during anything specific. I searched Google and the forums but couldn't find a solution. Please can someone help me out?
Sent from my SAMSUNG-SGH-T769 Cm10 using Tapatalk 2
Click to expand...
Click to collapse
Which version of CM10? No reboots here on Provision.. Used CM10 latest nightly as a base.. If you have random reboots then I should too.. Also a logcat would be helpful.
Sent from my Provisioned Galaxy S Blaze
Im on the stable version, but ill try the nightly like the first post suggest or the link you provided
Edit: logcat on the way sorry about that
Sent from my SAMSUNG-SGH-T769 using Tapatalk 2
anactoraaron said:
Are you running the latest nightly or the 'stable' build? The 'stable' build (note the "") isn't that stable and from the sound of it you are experiencing the screen of death (SoD) that I believe is present in the 'stable' build.
If you flashed the 'stable' build, flash the newest nightly instead. Or better yet, head on over here and also flash this (it's better than CM10 IMO - Just be sure to flash the kernel AFTER the rom). :good:
Click to expand...
Click to collapse
Hey, I downloaded the rom and kernel that u suggested. When i plugged in my phone to my laptop to transfer the files to my sd card i noticed that my internal sd and ex sdcard now reads as 'Generic Hierarchical'. Prior to this i did notice that my ex and internal memory were not showing the correct amount of space after rooting but i was so happy with the root that it slipped my mind somehow.
What in the world is generic hierarchical? And how can I get it safely to Fat32 to flash the ParanoidAndroid without messing up my phone?
Daze7 said:
Hey, I downloaded the rom and kernel that u suggested. When i plugged in my phone to my laptop to transfer the files to my sd card i noticed that my internal sd and ex sdcard now reads as 'Generic Hierarchical'. Prior to this i did notice that my ex and internal memory were not showing the correct amount of space after rooting but i was so happy with the root that it slipped my mind somehow.
What in the world is generic hierarchical? And how can I get it safely to Fat32 to flash the ParanoidAndroid without messing up my phone?
Click to expand...
Click to collapse
Go to settings/storage. Press menu. Then USB computer connection. There you can choose. Select USB mass storage. When connected to the computer it will prompt you if you want to move files from computer to your phone.
Sent from my Provisioned Galaxy S Blaze
In the end I just went back to stock and did a clean new root, this time with ParanoidAndroid. I loved the cm10 stable i had but the phone shutting off was t0o much. Thanks for all the help though i really appreciate it. :angel:
I've been trying to install Slimsaber on my phone. I've been able to install AOKP 4.4.2 and Beanstalk 4.4.2 fine, however when I follow the instructions on installing Slimsaber the bootscreen seems to linger forever. I've waited longer than 10 minutes and it still remains with a flashing SlimSaber bootscreen. I've tried the 05142014 nightly.
05132014 nightly worked fine.
14 nightly and after has some troubles, with build script mostly as we did some experiments to it. Anw it woukd be back soon after we solve a more important issue named stealing . Sr for this inconvenience.
Sent from my GT-I9300 using Tapatalk