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
Related
I have a strange situation going on with my phone and I could use some advice.
My issues started after loading the "official" IMM76D ROM, the rooted and odexed version. Phone would shut off like it was dead after charging all night. Wont boot back up without a battery pull. It would freeze up while the screen was on forcing a battery pull. Basically unusable for more than 10 minutes.
Here is where I might have messed things up. I tried to wipe the phone completely, including the SD card. Factory Reset multiple times, wiped everything multiple times. I even did a repartition of the SD card thinking it would format it further.
Where I'm at now. The phone still boots into the 4.0.4 ROM and I still have CM recovery. But now no matter what I do, factory reset, format/wipe EVERYTHING including the SD card, use fastboot to load a whole new setup, THE PHONE BOOTS RIGHT BACK INTO THE ROM AND SD CARD STILL HAS EVERYTHING. I dont get it.
I have ODIN 1.87 downloaded but it wont see my phone in download mode. I have all the correct drivers loaded including PDAnet, and my phone is correctly detected as Android ADB Device. Interesting side note: fastboot detects the phone, ADB does not. dont know if that means anything.
Sorry for the long winded post but I have been at this for 4 days now and I really need my phone back! Any ideas??
Maybe flash stock rom or CWM recovery from fastboot would solve the partitions issue. I remember when i had my old HTC magic i would sometimes change the partition layout and to reverse it i would have to reflash my recovery.
But as i said, this is all theory and can work or not.
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.
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.
I installed some dodgy app which required root access to operate (but it didn't even though I allowed it in SuperSu) and this is where my problems started.
First of all, I noticed each and every app I tried to run would immediately crash. That included system apps, such as the Settings app. At that stage I was left with only the launcher working and attempts to uninstall apps would also cause a crash. Even the shutdown menu was broken and the phone hung up so I was forced to reboot it by holding the power button for 10 seconds.
After that, the phone would no longer be able to boot, it was stuck in a boot loop, but recovery still worked (TWRP for that matter) so firstly I wiped the cache partitions (including dalvik cache) but that didn't help, as the phone still wouldn't boot. In this case there was only one thing left for me to try and that was the factory reset capability of TWRP which claimed to not even touch internal storage so I was fine with that and did the wipe.
Thankfully, the phone booted afterwards and it welcomed me with the first startup guide (the language selection dialog was really buggy but that's Huawei's fault) and the phone was seemingly ok, except that the whole internal storage had been wiped out but not only that - the external microsd card was empty as well! Could you believe that? I couldn't. TWRP promised not to touch internal storage and the external memory card wasn't even mentioned but why would it wipe it anyway?
That's for the story behind it, now for the actual problems I'm facing right now:
The stock remote app is gone
The boot animation has changed to a different one (now it's a silver "android" logo instead of the "honor" logo)
Battery usage stats are not available (see: http://i.cubeupload.com/BXCknW.png)
Sound quality from the built-in speaker seems noticeably worse
Hereby, I'm asking you guys to help me out with all of this.
The "remote app missing" problem could be solved by someone sharing their apk file with me, that's probably the simplest one to fix.
As for the boot animation, I have no clue as I don't even know what files are responsible for that.
The same for the battery stats problem, I'm already through a couple of full-charge-to-discharge cycles as well as wiping the cache partition, but the problem remains.
The sound quality probably has to do with the DTS sound enhancer. The config file for that is either "/cust/unicom/cn/xml/dolby_config.xml" or "/cust/unicomelectric/cn/xml/dolby_config.xml" and I'm asking you to upload these files somewhere so I can compare them with mine to see if anything is different.
The device I'm using is the H60-L02 variant running the B532 ROM.
Does the 3 buttons method erase internal storage as well? I've already set up quite some apps and having to do it again wouldn't be the most pleasant surprise. But at least in this case I could make some backups and whatnot...
Also, would it work if I flashed B535 straight away or does the 3 buttons method expect the same version which is already installed, in this case B532?
pudup said:
It will wipe internal storage. You can flash any *full* ROM as long as you're not moving up or down from kitkat-lolipop/marshmallow.
Click to expand...
Click to collapse
Okay, so I decided I'd do the whole thing today. I downloaded the full B535 ROM on my PC, backed up all the stuff I care about from the phone to the PC as well, and also I downloaded the MultiTool.
Though the MultiTool thread says this in bold red:
VirusPlus said:
EMUI 3.1 WARNING! Update over rooted or system modded in EMUI 3.1 gives a BRICK.
You have to restore system and REMOVE root before every update in EMUI 3.1 for now.
Click to expand...
Click to collapse
So I also fired up Titanium Backup in order to defrost all the frozen apps, which went fine, and then I wanted to unroot the phone but I've been unable to do so so far.
To unroot, I launch the SuperSU app, navigate to the "Settings" tab and select "Full unroot". The problem being, it just gets stuck on the screen saying "Uninstalling, please wait...". I don't know how long it usually takes to complete, so far I've waited for maybe 10 minutes and nothing seems to change. Should I care about that? Is that warning about updating rooted/modified EMUI 3.1 resulting in a brick still true?
Can I skip this step and just flash the stock recovery followed by the 3 buttons method?
EDIT:
After some trial and error with the multi tool and different recoveries, I was able to finally unroot. Next, I flashed the stock recovery for B532 and attempted to do the 3 buttons method, but it would say "Install failed. The update package does not exist" (could be because I'm doing the update from a USB flash drive as I don't have an micro sd card big enough to fit the package). So I rebooted the phone into system and used the Updater to perfrom a local update where it would let me pick the USB drive. It completed without errors and then rebooted into some kind of updater (black background and some bluish emui colors) where it also took some time to finish thankfully successfully. I can right now see the phone booting and for what it's worth, the boot animation is once again the good old "honor" logo and not that ugly silvery "android" one
And now it's "Optimizing system...". I really hope it finsishes successfully as it's already a bit late here and I wouldn't like the phone to be unusable tomorrow :laugh:
36% ready...
46% it's kind of fun to watch this, and now 49%
I'd like to thank @pudup once more for helping out, I'm not really that much into flashing recoveries, roms and all that myself. Without your help I would probably be too scared to try doing something on my own :crying:
86%, 89%, 95% and 100%. Aww, what a relief Good old stock lock screen and wallpaper.
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!!!