On my Samsung galaxy S3, I installed an experimental Cyanogenmod update which was 10.(?). I had previously been running my phone on what I believe was 10.0.1. (But I'm not entirely sure about any of the update numbers because my phone will currently not boot) After I installed the update, I didn't like the results, so I updated back to 10.0.1(?) which was what I had originally.
After it finished updating, it attempted to boot up, but then it just stuck on the Cyanogenmod booting gizmo indefinitely. I've tried removing the battery and booting into CW recovery (Yes, it will boot into recovery mode), but it still only does the same thing. I need to use my phone tonight, so any help would be greatly appreciated!
Related
Hi guys,
Really sorry to ask about this but tearing my hair out!
I have a P6200 UK model. I installed CWM v6.0.1.0 and it worked fine. The intention was to install Galaxy ROM HD (build #06), so I downloaded it, put it on my SD card, and installed from CWM recovery. The install got stuck on "Flashing boot" - so after around 15 mins I reset it.
It went into a boot loop on the initial Samsung logo. Luckily I'd previously re-flashed stock HC with Odin (to cure a dead Wifi problem caused by, I think, an errant install of Busybox) so I did this again, rebooted, and the system came up, text started scrolling up the screen, followed by a red error message (see picture) and a reboot. I was then once again stuck on the initial Samsung Tab 7.0 Plus log. I repeated the process and it didn't even get past the Samsung logo.
So I thought I'd try the newly released ICS Rom (GT-P6200_ATO_P6200XXLQ1_P6200OXALQ1) - this seemed to install OK, then half booted, did some text type installation stuff with the blue Android, then rebooted again, finally getting stuck on the Samsung logo with blue pulsating behind it. It never gets any further than that.
I tried flashing HC back - same result as earlier. I can also reflash CWM and sometimes it works, sometimes it doesn't. It seems I've run out of options.
So - question is - where (if anywhere!) can I go from here?
Help greatly appreciated, many thanks!
have you tried a system wipe in cwm? if not do a system wipe and reflash HC using odin.. same thing happen to me 2 days ago.. I think something is up with HD rom
On my Samsung galaxy S3, I installed an experimental Cyanogenmod update which was 10.(?). I had previously been running my phone on what I believe was 10.0.1. (But I'm not entirely sure about any of the update numbers because my phone will currently not boot) After I installed the update, I didn't like the results, so I updated back to 10.0.1(?) which was what I had originally.
After it finished updating, it attempted to boot up, but then it just stuck on the Cyanogenmod booting gizmo indefinitely. I've tried removing the battery and booting into CW recovery (it will boot into recovery mode), but it still only does the same thing. I need to use my phone tonight, so any help would be greatly appreciated!
cadeunderwood said:
On my Samsung galaxy S3, I installed an experimental Cyanogenmod update which was 10.(?). I had previously been running my phone on what I believe was 10.0.1. (But I'm not entirely sure about any of the update numbers because my phone will currently not boot) After I installed the update, I didn't like the results, so I updated back to 10.0.1(?) which was what I had originally.
After it finished updating, it attempted to boot up, but then it just stuck on the Cyanogenmod booting gizmo indefinitely. I've tried removing the battery and booting into CW recovery (it will boot into recovery mode), but it still only does the same thing. I need to use my phone tonight, so any help would be greatly appreciated!
Click to expand...
Click to collapse
Wipe it then flash a new rom. Confirm the MD5 checks out on it as well.
Hello,
My GF have a Galaxy Note 10.1 (GT-N8000) and in february she updated to N8000UBCML2. Ah, she never used root, CWM, etc, her tablet is totally "official", so she updated her tablet using WiFi but after the update her tablet started to "reboot every X hours" sometimes more or less. I did a wipe and her tablet is now very better but sometimes he just reboot and get in loop.
She asked me to go to the old version, since the old version was working fine. So I tried to enter in Recovery Mode but her tablet just reboot 2~3 seconds after enter in Recovery Mode, I really don't know what to do I can't use Odin.
Someone help plx
Try this video it may help. Go to 1:08 and try that method.
https://www.youtube.com/watch?v=ozLJ1JrxEnM
(backstory) Hi, ive had an Asus TF300T, for about 3 years now, unlocked, rooted it pretty early on... cycled between cyanogenmod and omnirom quite a bit, without really any major issues. Until today, i was running Cyanogenmods latest nightly build (CM11 Nov 5 2014), it worked just as any other nightly does a few bugs here and there, but nothing major and i hadn't done any major flashing or modding to the device. On my home from university, I turned my tablet off. And when i got home i plugged in the charger, and just as always the tablet turned on, showed the stock Asus screen, then changed to the Android boot animation... the animation then suddenly froze, and the device went into a boot loop... continuously... I dont know whats weong with it... tried to do a factory reset, i tried reinstalling the ROM, tried installing omnirom, but that got stuck on the OmniRom animation...
Im running Asus build 10.6.1.27.5
I had TWRP v2.7.0.1 installed but have now no longer works
id really hope there is a solution for this!
Thanks!
Edit: I dont know why, but when i try using fastboot or adb, the device isnt recognized. It doesnt show up on device manager either. I dont know if its the cable cause i bought it new, it says its can sync data, or a faulty charge/sync port....
razr9622 said:
(backstory) the tablet turned on, showed the stock Asus screen, then changed to the Android boot animation... the animation then suddenly froze, and the device went into a boot loop... continuously... I dont know whats weong with it... tried to do a factory reset, i tried reinstalling the ROM, tried installing omnirom, but that got stuck on the OmniRom animation...
Im running Asus build 10.6.1.27.1 (I know that theres a newer version 10.6.1.27.5, but when i try to flash it, the recovery says error and fails)
I have TWRP v2.7.0.1 installed but have now no longer works
id really hope there is a solution for this!
Thanks!
Click to expand...
Click to collapse
^THIS!
I was just to open a similar thread, then i saw your post. I join your request for help!
A month ago i have done a favor to a friend by unlocking his tf300t and installing CM11 on it. A few days ago he comes to me with this problem. I've tried anything but still no success:
- restore a backup done before flashing CM11 --> restore ends correctly but the problem remains
- flash a rom (CM11 and OmniRom) --> flash ends correctly but the problem remains
- flash the stock firmware found on asus website (WW_epad-user-10.6.1.27.5.zip, the SKU is correct for my version) --> the flash process stuck (i had to force restart the tablet after almost 2 hours of "flashing")
Since the boot animation changes according to the rom, i suppose the flashing process works. But the problem remains: after a few seconds the animation freeze and the device restarts, in loop.
Informations on the system:
- build 10.6.1.27.5
- TWRP v2.7.0.1 (working!)
- adb works (i managed to set /data as rw and push the .zip file to flash)
- fastboot should work
Please help! I feel a bit responsible for bricking my friend's device
SOLVED!
Finally!
I had already tried this method, before requesting for help, but the first time didn't worked... I don't know why this evening the tablet decided to collaborate:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
That worked for me! :victory:
Hey guys, so I'm up for a new phone (had this phone for 2 years) and I remember having a friend root + flash me the cyanogenmod on my Samsung Galaxy S3
I decided to root/flash my current phone (Galaxy S5) and i ended up ****ing in on several fronts.
The following is what I did and where I ended up
Rooted phone through Odin - was successful but I got a feeling it was outdated as I got the Seandroid kernal thing in red
Got ROM Manager and flashed recovery to TWRP - successful
Flashed ROM to Cyanogenmod nightly 7/14/16 - used the wrong version so i couldn't use my phone to call
Flashed Rom to the correct version - successful
Installed Gapps zip so i can use the app store and etc - experienced issues as it was always saying the store failed and etc
Now where I am currently
I ended up wiping all the data and etc so I can flash back to the Stock ROM/firmware since I couldn't get the Gapps to work.
I tried to flash the firmware but everytime I flash it and it boots to the stock recovery and says "installing android update" it gets to 1/3rd where it says "Erasing" and boots up to the Sprint Logo where the Blue notif is on and it is stuck.
I'm assuming its soft bricked and on a bootloop and I am trying to see if I can salvage this phone.
I tried flashing different version of the firmware (my brother has the same phone his version is G900PVPS3CPE2) and i tried that and G900PVPU3CPA. Both times its says its successful on odin but upon booting it only gets 30% before it says erasing and returns to get stuck on the boot.
Can I salvage this phone and if so can someone guide me through the proccess (links to proper firmware download/etc)
I do not care if any data/apps is lost (i have important stuff backed up on my gmail), I just want my phone to work.
That being said, my phone is salvageable instead of guiding me to repairing my phone to stock, if they can guide me to set my phone to a custom ROM (cyanogenmod or anything they suggest assuming they can get the googleapps to work on it) can someone please guide me through that.
Thanks again for reading.
Edit: All info in a TLR format incase my wall of text was messy
Phone: Samsung Galaxy S5 SM-G900P (SPR) Android 6.0.1
problem: ****ed up with flashing now phone is stuck in bootloop
What I want: Find a solution to make my phone work, ideally to make it work using a custom rom(any works) that has a working google apps installed.