Hello everyone, first of all I want to apologize for my bad English, I'm Argentine.
I'm in a serious problem that I've been trying to solve for a year now. First of all, my cell phone is a Samsung Galaxy Ace 4 Neo, which I tried to install an unofficial rom based on CM13.
This is where everything began. When I flashed the rom, I accidentally disconnected the USB cable, causing my phone to completely crash. Determined to recover it, I had already installed the TWRP. When I proceed to want to format everything, the /system, /data and /cache partitions gave an error when being partitioned. So I stayed for 2 weeks until I visited a forum (which by the way, I do not remember what it is) that said that changing the ext4 format to exfat would allow you to format well. SERIOUS MISTAKE IS MINE WHEN TRUSTING IN THAT FORUM. By doing this I not only screwed up the phone already, but it did not even turn on. As a last resort, I used Odin to nand erase and reflash the stock rom. Surprisingly, there were no errors when reflashing, but when the phone is turned on, it remains in the boot screen. Investigating Odin's options, I realized that I can not use the re-partition option, since I get the error "Can't open the specified file. (Line: 1831)". I do not know what else to do with this phone, so my last hope is you. Please I need help!!!
Related
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.
Hey everyone, I'm using a GT-P5100 (3G + Wifi) O2 UK rooted tablet and for the last month it has been broken. It started rebooting itself randomly every now and then, and then suddenly it wouldn't even boot up for 15 seconds before it would restart itself again.
I am able to get into safe mode and I can get into the boot options, but when I factory reset it does nothing, I've tried from the boot menu, from safe-mode options and even from the dial up code.
I tried to connect my tablet to my PC as a media device and format it but that didn't work either; I can't connect it as a disk then format it that way because they took out 'mass storage mode' on this firmware.
I then tried to flash a stock ROM in Odin but every time I tried it would fail until I used Odin.v1.3, but guess what, it rebooted itself and my entire tablet is still exactly the same.
(the option was on AP ram in v1.3 not AP nand I don't know if that makes a difference.)
If anyone can point me in the right direction I would appreciate it so much. I have been trying for weeks to fix this and I just don't know what to do anymore, I tried on another forum but nobody answered me.
Everyone else gets replies and I get zilch; amazing. I don't know what it is that is preventing my tablet from wiping itself but it refuses to clear the current data no matter what way I try (ROM, factory reset, computer format). If someone could just tell me what that is and what I have to do about it that would be grand.
You mention "rooted " but you don't mention what current rom or past roms that you may have flashed, you could have some sort of rom cluster [email protected]$k going on in your tab but NO one else will ever be able to help because of lack of INFO or history.
Pp.
I standard rooted it from Odin. This is my first ROM I am trying to flash. I just need to know what would prevent a tablet from rebooting itself properly. Factory reset, format and flash is not working so I must assume that rebooting is the issue here.
If you are running stock rooted rom and having issues like this the only way out is reflashing the stock firmware complete (not just a rom) and see if that fixes it before you try any other roms.
If you can get into download mode thats the fix.
Pp.
To flash it completely do I need more than an MD5 file? (I also have the partition file for my model). Another question, if the tablet is having issues with the reboot after a flash, will updating from a microSD with a zip help? Thanks for the advice.
Hi,
I've got a very odd problem:
My Nexus 5 is rooted, I flashed it many times before, the bootloader is unlocked. This morning, it crashed, and couldn't restart. No panic, I launch recovery mode and go for a wipe data / factory reset.
Two hours passed, and nothing happened, it's stuck at formatting /data.
Still no panic! Let's flash that bad boy. I used flashboot to erase all partitions, everything went fine, then flashed each one of them one by one, until system and userdata...
These two give me a "flash write failure". I think it's probably because these two are the largest, and my flash memory would be corrupted or not working at all.
My warranty is dead since one week (yay). What should I do? Maybe it's not a hardware problem and then I'm in luck? :3
EDIT: Locking back the bootloader is ineffective after rebooting the device. According to another post, this means that my eMMC chip is dead. But then why can I still write on boot, cache, bootloader and recovery?
The EMMC doesn't get "fried" per say - it's just that some sectors of it become damage beyond the capabilities of its firmware to bypass. When this happens , the firmware locks/errors out when try to write .
Edit : In your case it seems like the vital parts of it are still working - there might be a way to repartition around the damaged portions , but I'm afraid I have no idea how.
I previously posted in the local Galaxy S3 i747M section with the same problem, but now the issue is worse than before.
Here's my previous thread:
http://forum.xda-developers.com/galaxy-s3-att/help/boot-loop-plugged-to-ac-twrp-wipe-data-t3070064
A note that I'm no stranger to flashing and the inner workings of Android architecture (ROMs and general hardware), . But for the sake of this issue, please feel free to treat me like a noob if you think it would help elaborate any procedures I should follow or troubleshooting steps I should take, or just throw ideas at me like the software dev that I am and expect me to figure it out on my own.
Some background:
Recently (around beginning of April), my phone began to exhibit strange behaviour - reboots when reading/writing from internal memory (not uSD card), unable to wipe /data partition in TWRP or CWM. I would also get bootloops when I was plugged into direct AC charging (no problems if plugged into a computer for charging, though).
When in TWRP, CWM, and Philz, I would not be able to wipe the /data partition or anything in it. Installing anything to /system also caused a crash (though wiping it didn't cause any issues). Doing a factory reset wipe would also cause the recovery to "crash" - the recovery would freeze up and the phone would reboot. I could not restore a NANdroid, I could not install a new custom ROM. In TWRP, if I opened up a terminal window and manually tried to repair the /data and /system partitions with the e2fsck command, it would still freeze up and crash.
At that point, I downloaded the stock 4.4 firmware image (I think it was NF2?) from Sam Mobile and flashed it via Download Mode + Odin. Booted it up and ran the phone stock for probably a week. Then, I carefully used Odin to flash a freshly downloaded (and MD5 verified) TWRP 2.8.6.0 TAR image and SuperSU. Flashed both via Odin just fine. From there, I mounted the microSD card - I didn't want to touch the internal memory for now - and copied over a fresh downloaded copy of a CM12 based ROM (also MD5 verf'd) to it. From there, still in TWRP, I successfully flashed a 4.4.x TouchWiz-based ROM.
Take note that at this point, doing anything to attempt to wipe /data still leads to crashing the recovery. Nothing I have done has resolved this issue. I left that issue alone, just happy to have a working phone.
That above procedure seemed to work. I could then use the phone for about 2 weeks. Then my phone started crashing again, same as before: only when I was doing something that was reading/writing the internal memory. E.g. music, podcasts, etc.
I followed the same procedure with Odin + stock firmware > reboot > Odin + TWRP + SuperSU > flash custom ROM. Worked fine again for 2 more weeks.
Here I am 1 month later, same problem as the last 2 times. This time, however, after flashing the custom ROM, it does not boot up now. My phone is at home because I cannot use it. Last night, upon trying to boot up S3rx and PAC 5.1, I literally let it sit at the boot animation for 1 hour, each, and neither got past the boot animation. I'm familiar with ROMs sometimes taking say 10 minutes upon very first boot on a clean flash, but I gave up after about 1 hour (in fact, 1.5 hours for PAC 5.1, which was my second attempt last night). It's to the point where I'm certain if I left my phone plugged into the AC, it would still be at the boot animation over 12 hours later.
I know of the NAND memory corruption issue that S3's had previously, and I did flash the stock firmware that came out at the time (I think it was an Lxx based bootloader+firmware). But that was years ago, end of 2012 if memory serves me correct.
Thoughts on what I am facing? What I should try and do next? Where to go from here? If this is a hardware issue that is beyond fixing with flashing things in fastboot/ADB/Odin, then I'll face defeat and look for a new phone. But if I can hang on to this phone for just a little bit longer...
Thanks!
Hi there
Please note the following sticky from the top of the Assist section,
> General discussion > XDA Assist > The Purpose of XDA Assist [Please Read]
As a senior member on XDA, I am quite confident that you know where your device section is (you already asked something there) and where to ask for help.
Thanks for understanding
Good luck
Hi,
First I want to say that although I am not a total newbie, I can be considered as a newbie. I have windows 7 32 bit. I am starting from the beginning.
Until about 1.5 years ago, I was used to connect my phone to Kies and do a "firmware upgrade and initialisation" after feeling that it is time to do so in order to speed up the phone back. Does it speed up the phone back? I'm not sure, but as a guy that still formats his pc from time to time maybe it's a habit.
But about 1.5 years ago when Kies told me that my phone is not supported any more I couldn't do that. Then I made some search and found out cm.
I first installed cwm 6.0.4.3 to my phone by heimdall 1.4.0 then installed cm 10.2.0 and gapps-jb-20130813. I thought it would be good and my phone would be faster since I wouldn't have the unnecessary att apps. It also supported Turkish whereas the stock only supports English and Spanish.
I actually liked it at first except for some parts. Then a few months later the phone switched its language to English itself and started to behave abnormally, so I switched back to latest att stock rom by using odin3-v1.85.
Then about 3 months ago my phone got some water inside when I was under the rain with my phone in my pocket and my pocket not being sealed enough. The phone at first said please insert sim card when it was actually inserted, then I noticed it got wet. I immediately turned it off and removed the battery. Then opened it up and let it dry for a few days.
The phone got back to normal except for a single issue. When I charge the battery the screen behaves abnormally. The abnormality increases with time during the charging, I thought it is related with the phone getting warmer during charging. After the phone turns the screen off after timeout, It does not always turn it on after I press the power button. It starts at first by turning on after a few trials up to not being able to turn on during the charging process. When I unplug the charging cable, I can turn the screen on after a few trials. The phone gets back to nearly normal after 10-15 minutes. Although the screen does not turn on it still responds, for example I can answer a call. And sometimes the screen turns on with being upside down and flickering but responding as if its not upside down.
I hope I could describe the problem well. So this may be a hardware or hopefully a software problem. So I decided to first go back to factory settings. The problem with the screen continued. Then I installed the stock rom by odin. The problem continued but I noticed that the two applications I installed after resetting to factory settings remained in the phone. odin either not installs the rom or installs it by copying files, not formatting the system partition. I thought maybe formatting and reinstalling stock would solve the problem with the screen.
I made some research and noticed that I could actually increase the system partition, which is awesome since I always encounter filled memory problem when I try to install an app so I uninstall some apps to install the new ones. If I manage to repartition the system drive, it also has to format it.
Then I installed the stock rom using the pit file someone uploaded (6GB system partition), I did it but got an error from cwm upon first boot saying something like "unable to mount F", when I ignored the error the phone seemed to turn on but got stuck with att sign. When I pull the battery and turn it back on the phone got stuck at the same place without an error from cwm. Then I installed the stock rom with the original pit file, now the phone turns on but I still have previous apps. I repeated thes a few times (6gb pit file, original pit file) but nothing changed.
Then cm came to my mind, it would format the system drive. I repeated the same procedure I did 1.5 years ago. The phone turned on. I noticed that the internal sd drive had the previous folders,so I wiped the sd drive with cm. Everything was fine but the problem with the screen continued which stated that the it was a hardware problem. There was no reason to stay with cm so I installed the stock rom.
The phone asked a password from me since it had encrypted folders ???. I didn't provide a password, I think it did not recognise the sd drive wiped by cm.
I couldn't install cwm 6.0.4.3 with heimdall, it gave an error at the end. I decided to install a recovery with odin so I installed twrp 2.8.7.0.
I installed cm with 6gb pit, with original pit, installed stock rom with 6gb pit, with original pit with random order and how many times I don't remember that I brought the phone to a state that it won't boot. It turned on with odin mode though. Even the twrp did not recognise the drives. So I wiped all with ext4 format.
Now I have cm with 6 gb system but I want to go back to stock rom. cm drains up my battery. I also noticed that I really got used to the stock rom. I would appreciate it if I have 6 gb system like now. But if I have to reduce it back to 2 gb I don't care.
Can someone please help me?
Sorry for the long post, I wanted to state the problem as good as possible.
Not getting even a single reply probably means I am facing a really extraordinary problem.
I'll try to reformat the partitions. Maybe the OS thinks the unrecognised partition as encrypted. I previously made them both FAT.
Can someone please tell me what should be the filesystems of the system and the internal sd? Are they the same or different?
bloodcurdler said:
Not getting even a single reply probably means I am facing a really extraordinary problem.
I'll try to reformat the partitions. Maybe the OS thinks the unrecognised partition as encrypted. I previously made them both FAT.
Can someone please tell me what should be the filesystems of the system and the internal sd? Are they the same or different?
Click to expand...
Click to collapse
I could be wrong but Ext4 is the most common filesystem so try that