I've been running the Cyanogen Mod 10.1 nightly's and yesterday my tablet crashed and rebooted but would not go past the boot animation. I tried restarting it many time but it only boots to the animation. I booted into bootloader mode and wipted everything and tried installing an older nightly and the wingray gapps. It still is stuck not booting up only showing the spinning boot animation. Anyone have any ideas on what I can do? Any help would be greatly appreciated
Is there a way to update to a working rom though odin? I can't figure out how to do that.
Guys I installed the latest nightly, except for the keyboard problem, the resolution seems to be wrong: the writing in fact are blurred. is it a known problem?
Patfors613 said:
Is there a way to update to a working rom though odin? I can't figure out how to do that.
Click to expand...
Click to collapse
Yes, you can use odin to flash a rom, but it must be a stock rom, after which you will need to root your device again, install CWM recovery and then flash the nightly again. To use odin, you will need to put the device in download mode connect to the pc after activating odin and when the device is recognised (one of the boxes will light up in yellow) then put the extracted firmware in PDA of odin and click start. If successful, a green PASS will show in odin. Disconnect the device and wait for the device to boot up. You can try ICS 4.0.4 which is commonly available in Samsmobile.
Sent from my GT-P7500 using xda app-developers app
Mine just died too. Went back to stock 4.0.4
Sent from my GT-P7500R using xda app-developers app
For the bootloop, you can try to Wipe Cache/Dalvik.
But honestly, every new update that is pushed out, it's harder for our tabs to manage. So unstable to keep it up-to-date with every version, haha.
Thanks! I'll be going back to stock when I return home from work. Does anyone know where I can get CM 9 or 10 nightlies or stable ROM?
Related
Hi Everyone! just a rookie here in need of a bit of advice.
I'm a Galaxy S II I9100 owner and have my phone rooted and all setup with custom roms and been comfortable with flashing for some time now. My ROM of choice recently was Vanilla Rootbox and have to say the ROM has been fantastic with very few bugs to report. Last night i recieved the OTA update via Goo Manager for Vanilla Rootbox 3.4. I downloaded the full update over wifi and flashed with all wipes no worries. Next step was to flash the latest GAPPS and i figured there would be nothing wrong with flashing the GAPPS zip i had on my sd card that i had downloaded the last time i was notified of a GAPPS update via Goo manager as well. After flashing, wiping everything and rebooting again. My phone then booted up to a series of dialog boxes indicating that many google processes had stopped functioning. apps.google.com etc etc. A similar error has been reported in the Vanilla Rootbox thread by another user but i wasnt able to report this bug their either because my post count is too low to post in a development forum. So after seeing this error i rebooted into recovery to flash my last backup but CWM recovery came back with an error messaging stating it couldnt mount either ext or int sdcard. i did a factory reset which made no difference to the problem whatsoever. I then downloaded ODIN and the latest stock ICS Rom and flashed it via ODIN with no reported errors. My phone now boots through the optus boot animation and is stuck at the Galaxy S 2 screen with the flashing red and yellow animation over the S. If i turn off the phone with the power button, the phone turns off and immediately starts again and gets stuck at the flashing s screen. I've taken the battery sim and ext sd card out and put it all back in only for the problem to persist.
If anyone could help me there's a donation and my thanks in it!
Much appreciated
Nick
tried to re flash another stock ROM?
If so, tried factory reset the phone after the flash?
As long as you can get to DL mode, you are good to keep on flashing till you are up & running.
And then you got this
Remember to update your kies and make sure you close it all up before flashing with odin. If you are in 4.0.4 beware of the brick bug.
gastonw said:
tried to re flash another stock ROM?
If so, tried factory reset the phone after the flash?
As long as you can get to DL mode, you are good to keep on flashing till you are up & running.
And then you got this
Remember to update your kies and make sure you close it all up before flashing with odin. If you are in 4.0.4 beware of the brick bug.
Click to expand...
Click to collapse
Kies has never been installed on this computer but i did use the usb drivers mentioned in the soft brick recovery guide you linked. I used some information from the guide to flash this stock rom but i couldnt flash or wipe the partition because im unsure where to get the .PIT file required? i cant get past the boot animation so no factory reset possible and yes i can still get into download mode!
darkstar117 said:
Kies has never been installed on this computer but i did use the usb drivers mentioned in the soft brick recovery guide you linked. I used some information from the guide to flash this stock rom but i couldnt flash or wipe the partition because im unsure where to get the .PIT file required? i cant get past the boot animation so no factory reset possible and yes i can still get into download mode!
Click to expand...
Click to collapse
wow wow, leave pit files alone for now, they are nasty.
What stock ROM did you flash? 4.0.4 or 4.0.3?
You can factory reset via recovery mode.
Try installing kies anyway, it can't never hurt. Just make sure all applications are closed before you re-flash.
here's jb leak, might help:
http://www.sammobile.com/2012/11/15/i9100xxlsj-%E2%80%93-galaxy-s-ii-android-4-1-2-jelly-bean-test-firmware/
Right so i flashed I9100XWLP8 stock rom (4.0.3). Just then i flashed Siyah Kernel and attempted to use the factory reset function in recovery there, i get a message down the bottom mentioning that it can't mount my internal SD.
darkstar117 said:
Right so i flashed I9100XWLP8 stock rom (4.0.3). Just then i flashed Siyah Kernel and attempted to use the factory reset function in recovery there, i get a message down the bottom mentioning that it can't mount my internal SD.
Click to expand...
Click to collapse
Tell me your:
Model
Firmware
Country
Carrier
Always mention this
try flashing jb leak (ROM, modem & kernel package).
Ok, because I was so happy with cyanogenmod on my galaxy s I decided to try to install it on my SII.
Silly me, I decided to follow the instructions. couldn't get my trusty odin working, even after a couple of reboots and reinstalls of kies. Heimdall turned out to be the 64 bit version so I needed to find the 32 bit version. Long story short, the instructions sucked...
Then, I tried to install the suggested cwm. After a reboot, my phone entered a bootloop. I could enter recovery but trying to flash cm10 gave me "Status 7 blabla".
So, I searched on the web for a stock rom to at least get my s2 working again, found one and flashed it. Market keeps on crashing and it's version 4.0.3.
I tried reflashing cwm, cf-root and time and time again it kept creating a bootloop after which I had to reflash the rom with the broken market to get everything working again.
My questions are:
where did I go wrong in flashing cwm? Is there a different version I should flash? what's up with the extremely bad cyanogenmod instructions? Can someone get the market working again?
can someone guide me step by step through the process?
Why don't you flash it via recovery?
Sent from the little guy
gastonw said:
Why don't you flash it via recovery?
Sent from the little guy
Click to expand...
Click to collapse
because it gives the error "status 7"
I can't install a cwm that doesn't bootloop (I can however enter recovery) and in recovery I can't flash a thing because it throws errors at me
Assuming that you are on stock samsung ICS ROM, flash Siyah kernel from Odin
http://d-h.st/Bcf
After this you will get CWM recovery from which you can flash any i9100 CM version.
Sent from my GT-N7100 using Tapatalk 2
quick follow-up:
I had another laptop laying around that was never poisoned by samsung kies, so I decided to give it a try. installed the usb-drivers and used odin to flash another stock-rom version (that actually worked this time )
Then, I flashed cf-root and upgraded to cyanogenmod without any problem.
Hi forum,
I rooted my S2 a year ago and did happily CM 10.1 updates all the time. Everything just fine.
Then 10.2 came out and I gave that a try. One of the first ones did boot but had several issues (phone app missing, no connection to Play Store, etc). I decided to do updates via CM updater. Now I am stuck with nightly from August 24th. The problem then was that I couldn't access the CWM recovery any more and hence the CM Updater. Thus I tried to flash it again with Odin. So I can boot into Odin mode and Odin recognizes the device. I tried flashing several clockworkmods to no avail. Odin hangs for ever if it comes to the actual writing.
After that the phone did not start any more but stayed in that Firmware update encountered an issue screen. I used heimdall and flashed CWM with that. That looked better and then the phone started (somehow after many attempts) again but still no recovery.
Next I installed the latest Dorimanx Kernel with Odin. So that worked. Now the phone starts reliable again but no matter what I try there is no reccovery.
ROM Manager doesn't even start btw.
What I want now is of course a working recovery. At best CWM. Then back to CM 10.1. But how?
I read a lot here and elsewhere but everything I tried just didn't work.
Thanks for help!
Cheers,
blitz-gordon
you used Odin and Heimdall on same PC?!
ROM manager is bad for s2 and could cause bootloops. Don't use it
i suggest that you flash stock rom with odin. and then you'll have to root ur s2 again
TheMasterOfToast said:
you used Odin and Heimdall on same PC?!
ROM manager is bad for s2 and could cause bootloops. Don't use it
i suggest that you flash stock rom with odin. and then you'll have to root ur s2 again
Click to expand...
Click to collapse
Yep, Ubuntu 12.04 and XP as a VM. I used heimdall on another PC though.
I know that ROM Manager is not choice number one. That was more a test which failed anyway.
Well, I thougth I could get away easier.
Thanx!
For the records.
I de-rooted the device by putting a stock image on it. Then I rooted it again and now it runs the latest CM, woohoo!
If somebody wants details I can provide a short howto.
Cheers,
blitz-gordon
So I'd been having some problems lately with my phone hanging on the Samsung screen on boot. Been running CM11 1/1/2014 nightly most recently. Decided to try using TWRP instead of CWM. That didn't seem to help my issue, so I tried installing CWM again. I used an app called Recovery Tools to download the touch version of CWM. After it said it installed, I tried to boot into recovery and got the error "Unauthorized software found. Please contact Verizon." (paraphrased a little).
Doing some research it looks like that error typically comes up when the bootloader is locked. Now, obviously I had my bootloader unlocked (well, Loki'd) because I was running CM11. Any help fixing this? I'm able to bypass the warning screen on boot if I hold down vol up + power like I'm going into download mode, but then hit vol down to cancel to boot up the phone. Once booted everything is ok, but any reboot just brings that up again. Using ROM manager to flash CWM recovery seems to work ok and it says its installed, but same issue. So does trying to flash TWRP from Goo.
If I were to run this tool that I used to root and loki before (http://forum.xda-developers.com/showthread.php?t=2301720) to install a recovery, would I be able to get everything going again? I think that somehow the recovery I installed wasn't Loki'd, although I picked the right one for my device.
Thank you in advance for any replies.
The fix I found was by pure dumb luck. I ended up trying to flash a recovery with Odin. Odin failed but reboot back into the os. I then used the twrp manager app from the playstore (mainly because goomanager wasn't downloading the recovery at the time) to flash the latest twrp recovery and all was good. Even though Odin failed at flashing the recovery I still think it helped somehow. I haven't thought much about why but I might have to now.
Sent from my SCH-I545 using Tapatalk
You could probably try using ODIN to get back to stock MDK and then Re-Root and install a recovery after.
Edit: And then flash CM11 again.
Sent from my SCH-I545 using Tapatalk
Will this one-click stock ROM work?
http://www.rwilco12.com/downloads.p... S4 (Verizon) (SCH-I545)/Stock ROMs/One-Click
or, which of the files on this page are what I would want? (about 1/3 of the way down for SCH-I545)
http://www.droidviews.com/how-to-install-latest-official-firmware-on-samsung-galaxy-s4-all-models/
I was actually able to reflash TWRP w/ their app from the Play Store. Still get a lot of boot hangs on the Samsung logo though. Seemed to happen less with CWM, but now I'm too scared to try to install a different recovery. I appreciate all your help guys.
Hello everyone,
I own a samsung galaxy s2 gt-i9100 I've been using it for a long time. A few days ago i installed cynogenmod 13 marshmallow on it but faced some severe issues like dialler problems,battery drain,google play services not working. So, i switched it back to my previous rom i.e. cm 12.1 lollipop but my old twrp recovery got replaced by cynogenmod default recovery. Now some people who may have used it know that its very basic and does not has backup,restore, has bugs,does not flashes some zips or files that i wanted so i tried to replace it with twrp/cwm through rashr,flashify,rom manager,etc. But none of it worked, whenever I'd boot after flashing the twrp/cwm recovery it'll go back to the default cynogenmod recovery. Now, me not knowing what im doing stupidly downloaded mobile odin lite app then i downloaded the cwm kernel recovery kitkat compatible and installed via mobile odin lite. After that it got screwed, it won't just startup it'll just start and go into recovery i mean continuously! It was annoying, then i read an article on a forum to download any cm nightly or stable mod and flash it but i did a little bit of tweak of removing the recovery boot img file with twrp to get preinstalled twrp recovery but i gotta admit it was the last mistake possible. Now i sit here, with a bricked phone in my hand which is looping continuously only on the samsung logo. If anyone out there can assist me correctly it'll be a life saver for me. Thanks for reading this and please reply with a solution asap. Please! Im in danger!
can you get into download mode?
if yes you can download a stock firmware and flash but you will have to hope it will work, otherwise you will get stuck on nand write start which means the nand is stuffed/corrupted and then basically only a motherboard replacement will do the job, or you can try using another computer, reinstall usb drivers..
can you get into recovery mode?
if you can, you can flash a rom
The 'nand stuffed' assumption is a last resort, tried everything and nothing works assumption. There is *plenty* to try before assuming that the nand is 'stuffed'......
It sounds like (from your description) that you may have rendered recovery useless and inaccessible.
I've a feeling what you need to do is to go into download mode and Odin flash a firmware.
Even if it doesn't boot, you should have a recovery that you can flash PhilZ recovery from and then use that to flash a custom rom. Initially, I'd stay away from the MM builds and instead flash something KK or LP based as they're less 'volatile' and have a higher degree of stability than the MM roms.
http://i.imgur.com/rVnFwJM.jpg