[Q] Galaxy GTI5500M - Boot loop problems abound - General Questions and Answers

Hey there,
So before I came here I searched far and wide for a solution to my problem. Somehow, in the dead of night I accidentily formatted my SD card while wiping the phone at the same time. As such, I have have no recovery to fall back on. I resigned to installing a ROM from scratch as I can't figure out where else to go from here. So I installed CWM through Odin> Wipe data/reset>Wipe cache> Mount USB> Copied update-cm-9-20120608-MADTEAM-galaxy5-signed.zip>Installed Gapps> Wipe cache> Reboot> Endless boot loop of doom.
I've tried several roms including CleanROM and a couple others, some wouldn't install but everyone that did install correctly would cause the same boot loop.
So is my phone junked or what? I can't even seem to find the manual code for recovery/reboot on the GTI5500M, the only info I can find is how to power it up in downloading mode.
Am I missing something? Just about pulling my hair out at this point.
Greene

Related

[Resolved] [q] formatted samsung epic 4g touch need help restoring please

Hello
Today I was upgrading to the latest starburst rom...this was not the first time I upgraded roms and i did the exact same thing I had done in the past which included wiping data wiping cache wiping dalvik and then flashing....
when i did this and restarted my phone it wouldnt load past the boot screen...after the boot animation the phone stayed black...i repeated steps 1-3 again hoping i just did something wrong...but still nothing
i went back to look at the directions and i say that the developer said to format the system under mounts and storage...in bolded font...i thought maybe thats why it wasnt working so i did just what he said...
now when i load my phone it doesnt load at all and when i open cwm i get a string if e: errors basically saying that it cannot find the drive
if anybody has any advice on how to recover from this I would be extremely greatful
Im having the same problem cant figure out how to fix it.

Boot frozen on first boot screen... Can't read ext.sd

Ok so I have been trying to install blackbean 8 for my tf300 running 4.2.1 using twrp 2.5. I could never get it past the first boot screen. I have read everywhere for days and tried everything. I wipe data, system, cache, and dalvik cache everytime to no avail. It does the same thing everytime even with cm 10.1. I finally read something about formatting data and i thought i would give it a try (which I am now so badly regretting) because i have a nandroid backup on my microsd. So I tried it and it did the same thing! So i tried to restore the backup from my external sd but nothing shows up!!! It recognizes it and tells me how much space I have left but there are no files on it.... The part that confuses me is I plug the microsd onto my computer and all the files are on it! Am I bricked? I have no idea what to do right now so any help would be greatly appretiated!
EDIT: Ok so i got it to recognize my micro sd by trying a different one but it says i have nothing in my recovery file. Why would that be?
EDIT2 So i got cm 10.1 sideloaded using adb but it still wont boot! Am i missing something? I would really like to understand.

[Q] Decryption Unsuccessful Error - Cannot boot

I have a Samsung Galaxy tab 2 GT-P5110 which I had successfully installed CM12 onto. I decided to set up work email which insisted that I encrypt the device. I believe that the process completed successfully.
At that point I decided that I would like to flash the device with CM12.1. Restarted the process (Factory reset, Wipe Cache, Wipe dalvik cache) and flash the new CM12.1 zip file from external SD card.
I cannot now get to the recovery mode and the device doesn't always boot into anything recogniseable. The screen goes black and blacker! I have manaed to get to the CM logo and then a screen asking me for the PIN for the encryption. The next screen tells me that the PIN is right but the data is corrupt. It gives me the option to "RESET TABLET" but that really doesn't do anything and won't let me in to the recovery menu.
I can get into the Download mode and connect Heimdall up to it.
Is there anything that anyone can point me at that will help me to unbrick it?
I hope I've passed on enough information to help. It seems to me I need to somehow re-format the internal SD but I can't get to any menu that will allow me to do that.
Any thoughts anyone?
Ta
Fixed It
I seem to have fixed it. I flashed the CWM Recovery rather than the recovery that I had been trying to use and I got control of the device back. Not sure why that made a difference but this time the Android Robot came on screen with the 3D polygon rotating inside it and it seems to be running correctly now and updated to Android 5.1 ... Magic!

SD card fried?

Hi all, new here. I would appreciate any responses/ideas.
I have an Samsung Galaxy Rush. Here's what happened:
After playing Netflix for a while the sdcard would get full, so I would go into root and delete the cache(as instructed by someone else). One night I fell asleep, woke up the next morning, and decided to just wipe the entire sdcard. Booting into recovery I did just that. Plugged to compuer, ran Odin, pushed the stock tar.. all went well, but then the phone would not boot up. It will only go into recovery.
So I tried this again, except I wiped everything. Cache, dalvik cache, everything(i'm noob, pls don't hate ). Same result.
I should mention that in recovery, I can mount cache, mount this, mount that, but mounting the sdcard won't happen. It just blinks the screen.
I'm thinking either the sdcard is fried. Or it's one of these things I'm not familiar with (boot loop? soft brick?)
Thanks for taking the time to read.

Wokeup to my phone stuck in a bootloop... [SOLVED]

UPDATE: I have finally managed to get my phone working again! Am now currently re-downloading all my apps and transferring all my files back to my phone, running AOSPExtended (https://forum.xda-developers.com/oneplus-one/development/rom-aospextended-rom-t3732194) with OpenGApps. I'll write the steps I took to figure this mess out at the end of this post for anyone who might encounter the same problem in the future. :good:
So last night I left my phone charging overnight from 54% as I was downloading a couple of files (my internet is 1Mbps or 125KB/s). I've done this a couple of times before with no problems what so ever. But this morning I woke up and my phone was in a boot loop. I've tried everything I can think of and everything I could find on these forums, but to no luck. I am at my wits end and I have no clue what to do except to do a full factory reset, which I'd rather not do as its been a while since my last backup and I would lose a lot of precious files...
My Phone: OnePlus One 64GB Sandstone Black, purchased in August 2014.
ROM: cm-13.0-ZNH5Y-20161105-STABLE-Sultan-bacon
Recovery: TWRP+3.0.3-2-TugaPower
Firmware: bacon_firmware_update_2016_1-25_.4.0.1.c7-00011
The boot loop itself is odd, I'll describe them separately here.
-I can boot into fastboot, but not while the USB is plugged into my PC. I have to boot into fastboot, followed by plugging it into my PC. If I try to boot into fastboot while it is plugged in, the screen goes completely black and goes back into the bootloop. However, the phone shows up in Device Manager during the black screen.
- I can boot into Recovery, but the phone automatically reboots and goes back into the bootloop after a few minutes. One thing I have noticed is that if I let it reboot by itself, all the settings reset (including the confirmation to allow modifying of files when you first boot into recovery). But if I manually reboot back into recovery, the settings remain the same; atleast until it reboots automatically again.
Here, I'll list the things that I have tried to no avail:
1. Following this post - https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/, when I try to wipe Dalvik cache and cache from recovery, the phone goes right back into the bootloop
2. I tried flashing a newer version of TWRP (3.2.1-0 and 3.2.1-K2). After flashing I try to boot into recovery but the TWRP loading screen displays, and then goes right back into the bootloop. It wont even let me into the main menu.
3. I tried flashing a ROM through fastboot (via this post, https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/). The phone still remains in a bootloop.
HOWEVER, if I flash my previous recovery (TWRP+3.0.3-2-TugaPower replacing the stock cyanogen recovery from this method), my phone manages to get past the 1+ screen, and goes through my custom power on screen, and reaches the "Android is starting... Optimizing app 1 of 67." But it never gets past app 1, freezes, and then reboots. So now it's stuck in this "extended" bootloop thing.
What I want to know: is there anyway to fix my phone, or will I have to lose all my data and do a full factory reset through the ColorOS method? If anyone has any experience with this or knows a way to help, please don't hesitate!
Thank you in advance.
WHAT WORKED FOR ME:
After following the steps in this post (https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/) my phone was booting up, but was kicked back into a boot loop after freezing at the "Android is starting.. Optimizing app 1 of 67" screen. However, the recovery was now the default CyanogenMod recovery. I then re-flashed my previous recovery (TWRP+3.0.3-2-TugaPower) from fast boot, and it was now stable (no more auto-reboots). From there I made a backup off all my files onto my PC before proceeding. After that, I did what this post said (https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/) and wiped Cache + Dalvik cache. This allowed me to boot all the way past the "Android is starting" screen. However, the phone was still rendered unusable as there were non-stop notifications saying various apps had stopped working. I then booted back into recovery, downloaded and pushed a new ROM and GApps package on to my phone, wiped system, data, cache, dalvik cache, and installed the ROM and GApps pacakge, clearing the cache one more time before rebooting. Everything is working beautifully so far and I could not be happier! I hope this helps anyone else who encounters this problem, Cheers!

Categories

Resources