I had the fabric format Android (4.2.2) and my friend helped me to upgrade to Cyanogenmod by using TWRP. It didn't work so we kept it in the lastest official 4.2.2 from Samsung. After a pair of days of working perfectly, I woke up and my phone was in the "Samsung" loading screen. I kept it for a couple of minutes and nothing happened, so I pulled out the battery and put it in again, same thing happened. Tried again, then it started normally and worked fine for a few seconds, until it froze, so I repeated the battery thing. Samsung loading screen a pair of times, then it loaded again, froze... And it kept doing that
Then I tried to format it with TWRP, but the OS was deleted too (guess I selected the wrong choice?) and it's not loading anymore.
Today I've been trying to re install the firmware via Odin with a friend, but it keeps failing at the system.img file and the error is not very descriptive...
Related
Hi.....One day my galaxy 5 accidently fell down, though from a small height.....its battery came out. And after i reconnected the battery and started the device.....It started and worked normally...(btw i am using cm 10.1 v0.2)until some time and suddenly got frozen..everything on screen was as it was, i waited for almost half an hour but nothing happened.....no hardkeys worked...nothing....i had to pull out the battery and restart and again same happened.....i reflashed rom....after reflashing same rom (cm 10.1 v0.2) i got booted successfully and phone ran smooth as before but after i installed some apps it once again got frozen...and i tried cm 7 also and same happened.Not only in roms but it also gets stuck in recoery sometimes while restore or backup or flashing zip. One thing i noticed was it gets frozen when many apps start at once....I tried to flash official rom with odin but it went into bootloop and didnt even booted......PLZ helpp me...!! I saw this type of problem happened in S3....which is named Galaxy s3 suddon death syndrome and in that problem what happened was that a block in data partition(int. Memory) gets corrupted and when phone comws to write on that block it gets frozen and we have to pull out battery to start the device...I am trying the solution given there which is Dummy file generator but as soon as i start generating dummy files it gets frozen and after 2 to 3 tries, even the rom does not boot up......So please help me to solve this sudden freeze problem......I am really annoyed as i cat use my mobile....PLZZZ Help...
Hi.
I have a SGS3 i9300. It has CWM Recovery 6.0.4.6 installed, and a CM nightly from a couple of weeks back. The thing is, everything was working ok until a couple of hours ago. I needed to turn the phone off so I did (and I left it charging), and later I unplugged it and when I turned it on, it was stuck in the Samsung i9300 screen.
I tried to do a factory reset but when I try it reboots. I tried flashing a Paranoid Android ROM from 2 months ago that I had in the SD card to see if it worked, and nothing (it shows a 'installation complete' message, though). I try wiping cache, and even though it gets wiped, the problem persists.
What can I do?
Well I managed to go back to stock (the last firmware, 4.3). My idea was then rooting the phone and going back to CM. The thing is, somehow I can't root the phone. I am using CF-Root, as it has worked for me before, but I can't get root access.
Am I doing it wrong?
1. The galaxy hangs during normal work(it had custom ROM but was working fine for years), the display showed messed up image and was unresponsive, had to remove the battery(so it was caused by bug or flash storage error).
2. The galaxy could no longer be booted, it was stuck on Samsung Galaxy S II screen and in bootloop(if the flash storage partitions are bugged, I guess it can't boot the SPL and the device is stuck in the main bootloader, is it located in separate ROM chip or in the storage flash chip?).
3. It couldn't boot to recovery, only to download(odin) mode(again I guess it's part of the bootloader on the separate rom chip).
4. Tried to reflash, had to interrupt the operation because it didn't started at all(no progress on NAND write flash).
5. Tried to repartition with .pid file, again no progress with the operation.
6. After that, the device is completely dead, we tried removing the battery, using the charger and other common stuff but it can't be started anyway.
So can the failed repartition/flash operations bug the ROM bootloader so when you press the power button the CPU can no longer execute any instruction(I guess it's hardwired to some init instructions in the bootloader).
Any information about the internal storage chips or any ideas what to do?
Same problem here
Hi I've got the same problem with my phone since i've updated my cm13 on sgs II phone seemed to be working perfectly but around month later woke up and saw that my phone stuck on samsung logo (Same as your did) what i've done was restart to see is it works or recorvery boot up but nothing seemed to be happening. After some time decided to reinstall OS using odin but phone been comp[letely inresponsible to what i've tried to put on it (always been stuck on Nand write start (tried everything)). I tried to repartition it again but after that same as your phone died without any sensible reason. I "temporary" fixed it by pealing off the motherboard specific conductor. It even boot up but afterr that i runned out of charge died again. I can feel that phone is starting to be warm just like it's working but i still have black screen of death, so is there anybody who might actually help with this thread ?
HeadlessHorse said:
Hi I've got the same problem with my phone since i've updated my cm13 on sgs II phone seemed to be working perfectly but around month later woke up and saw that my phone stuck on samsung logo (Same as your did) what i've done was restart to see is it works or recorvery boot up but nothing seemed to be happening. After some time decided to reinstall OS using odin but phone been comp[letely inresponsible to what i've tried to put on it (always been stuck on Nand write start (tried everything)). I tried to repartition it again but after that same as your phone died without any sensible reason. I "temporary" fixed it by pealing off the motherboard specific conductor. It even boot up but afterr that i runned out of charge died again. I can feel that phone is starting to be warm just like it's working but i still have black screen of death, so is there anybody who might actually help with this thread ?
Click to expand...
Click to collapse
same thing happened to my galaxy grand 2
it was charging i was at 80% when i seen it last time i left it for sometime to complete the charge after 15-20min i piked it and i saw it was blank... after that till now it is dead..
I had the fabric format Android (4.2.2) and my friend helped me to upgrade to Cyanogenmod by using TWRP. It didn't work so we kept it in the lastest official 4.2.2 from Samsung. After a pair of days of working perfectly, I woke up and my phone was in the "Samsung" loading screen. I kept it for a couple of minutes and nothing happened, so I pulled out the battery and put it in again, same thing happened. Tried again, then it started normally and worked fine for a few seconds, until it froze, so I repeated the battery thing. Samsung loading screen a pair of times, then it loaded again, froze... And it kept doing that
Then I tried to format it with TWRP, but the OS was deleted too (guess I selected the wrong choice?) and it's not loading anymore.
Today I've been trying to re install the firmware via Odin with a friend, but it keeps failing at the system.img file and the error is not very descriptive...
Also, sorry for the repost, nobody replied in the last one, so I just copied the message. I hope you can help me, please :/ Is it hard bricked? Should I just forget about it and get another phone? Or is there any way to install another OS?
Recently, I flashed a TWRP and rooted my Tablet (Galaxy Tab A SM-T350). Yesterday, I made the mistake of installing crdroid (https://forum.xda-developers.com/galaxy-tab-a/development/rom-galaxy-tab-8-0-t3912517) and wiping the recommended partitions (In that post). After confirming that the custom ROM worked, I went back into TWRP to install the Google Apps and SuperSU. That's when I screwed up.
After installing those .zips I went back into crdroid, and the "Weather Pro" or something like that, which appeared to be the launcher, kept crashing.
Regretting my choices and wanting to go back to stock, I flashed this ROM with ODIN: https://androidfilehost.com/?w=files&flid=154234
That didn't seem to work, as when it booted into the setup, it would crash and reboot. I thought I had flashed the wrong version of Android on it, and downloaded this ROM: https://www.sammobile.com/firmwares/galaxy-tab-a/SM-T350/XAC/download/T350XXU1CQJ5/194035/
That also didn't seem to work, as the device would do the same thing. Boot to setup and crash. I tried to boot into ASR and wipe it from there, which is what landed me where I am now:
The device booted, went into setup and immediately shut down. The device does not boot at all, and when plugged in, simply shows the circle with the bolt inside, never showing the green circle and the battery percentage.
Quick FYI: I backed up everything with ADB to my PC way before this happened. Don't know if that will help.
What I mean: https://1drv.ms/v/s!AnXXk5PX0LXn3gd4nJiaPXYOKhFv
Anyone know where to begin in terms of resurrecting my tablet?
Thanks in advance
UPDATE: I don't know what happened, but the device is not charging. Still refuses to boot without crashing but I feel like this could help
Update 2: Ok so it turns out I was stupid and the battery was just dead (I thought it was charged after a night-long charging, but I guess not)