I'm working on it for about 2 days and do not know what to do anymore.
My phone worked perfectly, except it's rooted the rest is original.
On saturday I tried to convert an user app to system app and brick the operation system. So... sideloaded a stock room downloaded from ASUS suport page and "vuala", the phone was back to normal, them i think, if i install TWRP next time i brick my phone ll be easier ro restore if i had a backup.
Then i perform the procedures in this topic: http://forum.xda-developers.com/zenfone-5/general/recovery-twrp-2-8-6-0-asus-zenfone-5-t3136263
In TWRP i did a backup of my system and it ask me to install root on the device, what i did . After that the system start to freeze and rebbot randomly even without user interaction.
-My first step was factory reset, not work.
-Removed root, and factory reset again. not work
Wipe system and data partition, re-flash by ADB sideload the stock room, steel freezing and rebooting
I've downloaded the original stock rom V3.23.40.60, replaced the fastboot and recovery to original V3.23.40.60, re-flash dnx_fwr_ctp_a500cg.bin and ifwi_ctp_a500cg.bin from original image V3.23.40.60.
-Removed SD card, microSD and reflashed everithig again. still not work.
After all the probelm persists. Someone have any idea what's going on? My knowledge about mobiles is't enough to deal with this probelma alone.
I start thinking about hardware inssue but it's rly weird.
Some questions:
-There are another partitions on the device that can be restored to factory or reseted?
-Change bootloader or recovery can directly influence the operation system?
-Is there a program I can test internal storage of my device and RAM?
Related
This is my 3rd week battling with this issue.
The phone will freeze no matter what i'm doing or which app im using, and I have to do a battery pull or hold down the power button.
The phone freezes on boot screen. I then would boot into recovery to wipe data.
Wipe data/factory reset freezes on wipe data... (The first time i got this issue 3 weeks ago, when wipe data froze i was unable to flash any zip file successfully and restoring backups failed due to miss matched md5 sum). I then flash stock ics using Odin, it was successful but it freezed at boot. I then flash gingerbread XXKL1 using the .pit file and i was able to boot. After that i was able to flash ICS and boot successfully.
However, the freezes occur randomly (1 to 3 times per day) and the process restarts.
Presently when the issue occur this is my temporary fix:
when I get a freeze that makes the phone unresponsive for a long time I reboot.
If the phone freeze at boot I do a wipe data/factory reset and then set up my phone again or I restore a backup
If wipe data freeze I can restore a backup most times and it might also freeze at boot, therefore, at this point I rather flashing a stock ROM via Odin and then restore my backup after i've rooted. I'm now good until the next freeze.
Yesterday, before attempting the wipe data i tried to do a backup to internal sd card and it was unsuccessful, i found i could only do it to the external card so I did. When im not having the issue i can backup to internal card.
Apart from XXKL1, i've tried GB and ICS recovery files k13 & XXLPH respectively with their bootloaders and .pit files taken from this thread:
http://forum.xda-developers.com/showthread.php?t=1457458
I thought of using the solution from this thread: http://forum.xda-developers.com/showthread.php?t=1760107, however, my problem wasn't caused from flashing LQ5, but i'm thinking I might have a faulty data partition that needs replacing since I had to flash the .pit file from KL1 before i was able to boot in any other ROM when I 1st got this problem. I need to confirm this before i give up 2GB and also after reading the thread i'm still not sure on what file to flash and the steps.
A friend of mine soft-bricked his old galaxy s2.
The phone is running a custom android 5.1 or 6.0 (I don't remember) that i flashed for him a few months ago.
He said he just disabled the google app (not sure why he did that) and the phone crashed and is now stuck in a bootloop.
Anyway I'm trying to enable the app back and hopefully fix the phone without having to wipe everything and flash back the system.
Does anyone know how/if it's possible from an adb shell in recovery mode ?
I tried the pm command but it just crash in recovery, probably because android is not running.
Maybe i could make it work with a chroot or something. No idea how to do that on android though.
Thanks for the help.
Hi,
In this situation, it would be best to wipe your phone. Avoiding wipes is not what you want to do as this could cause more problems instead.
You could try wiping system partition and cache partition. Reflash the ROM and gapps and see if that helps. You should still keep all of your apps this way and no personal data is affected.
Otherwise full wipe is the only option left.
gsstudios
Thanks for your help, i tried to wipe only system partition and cache but unfortunately the phone was still stuck in a bootloop. Tried then to manually remove all google apps and their data before reinstalling them but it didn't work either. I gave up and formated the data partition which fixed it as expected.
Hi all,
Sigh. So it looks like I bricked my Samsung Tab E Verizon. I rooted it with King root and when I removed it, it is now in a endless boot loop. I've tried all sorts of things to try and recover it.
I used SkipSoft to set it up to be flashed but odin fails everytime. I was using the new ROMS found on this Forum. I've tried putting it into download mode and manually flash it and that didn't work. I can't Re-Root it as it won't stay on long enough to Root and they always fail. Right now I'm at a loss.
Can anyone help?
Thanks.
Do you have custom recovery or default? if you have default you can hold the home button and vol up button then the power button to get into recovery, once your done with that you can wipe cache and reboot, if that STILL does not work then factory reset your phone and re wipe cache, i know losing data sucks but its better then a brick. (this will work 99% of the time because the default recovery automatically re-installs stock rom)
If you have a custom recovery, then i recommend wiping everything including dalvik cache etc, making sure EVERYTHING is squeakly clean (execpt recovery obviously) , and find the driver for your samsung phone and download it on your computer and install, once you are done with that, put your phone into download mode, find your original STOCK rom for your phone, download it and flash it with odin, from there IF successfull you should have a fresh boot of your stock rom, then you can re-root and go on with your day.
Also make sure once you re-gain root access backup your rom so you will always have a plan b if everything goes bad. i cannot recommend this enough, even if you are an expert with flashing, there is always that small percentage things will go wrong and you should always have that backup ready.
Hi!
Thank you very much for the reply. You know, that was one of the things i tried initially when it happened. When I tried it, it wouldn't go into recovery mode. I then went on the odyssey of hell in trying to recover it.
When I read your post I was thinking; "Yeah I tried that", but then I thought I would give it another shot. I went into Factory Reset, it then actually went into the recovery menu. I deleted the cache and set it to data/factory reset and it's still looping. I get an error saying; "E:failed to mount /preload (no such directory)". I then tried to run update from external storage and it's telling me that it's disabled. I tried to update from ADB and it's disabled. I tried to apply from cache and it says; "APPLY_CACHE is depreciated". It's still looping.
Urghhhhhhhhh.......
Hey all,
I've got a N7105 (Galaxy Note II LTE) running CM12.1 and TWRP which I was planning to change shortly as it's old and the USB port has issues (charges but doesn't pass data; luckily it has a microsd slot). As it happens, the other day I left it discharge fully and turning it back on left it stuck at Samsung logo (not boot animation, the splash screen before it) forever.
I am: not a noob, I've rooted and flashed plenty of devices before.
I tried: removing battery for a while, charging fully, removing microsd and sim, clearing Cache and Dalvik. Nothing works.
I can: get into ODIN mode (but it's useless as USB data is not working); get into TWRP recovery; explore the Data partition in TWRP
I cannot: mount the System partition in TWRP, not even manually. It just does not let me select it, and gives an error whenever it needs to access it (e.g. if I try to backup it is says Error: unable to mount System)
I want: if possible to solve the issue without formatting Data. I had a TB backup but kinda old, so I got a Nandroid of Data and Boot out from TWRP and I suppose I could then recover stuff extracting from Nandroid through TB, but I've never done it and would rather be able to get a fresh TB backup and move on from there.
A few questions I have: any idea on why I am not able to mount System in TWRP? Could it help to reflash Boot or System, and if so how do I go to do that considering what I have is the whole CM rom package? (I remember being able to fastboot flash single partitions on Nexus devices but that's because the stock rom comes packaged in separate images).
Any input would be greatly appreciated!
Lazer Bear said:
Hey all,
I've got a N7105 (Galaxy Note II LTE) running CM12.1 and TWRP which I was planning to change shortly as it's old and the USB port has issues (charges but doesn't pass data; luckily it has a microsd slot). As it happens, the other day I left it discharge fully and turning it back on left it stuck at Samsung logo (not boot animation, the splash screen before it) forever.
I am: not a noob, I've rooted and flashed plenty of devices before.
I tried: removing battery for a while, charging fully, removing microsd and sim, clearing Cache and Dalvik. Nothing works.
I can: get into ODIN mode (but it's useless as USB data is not working); get into TWRP recovery; explore the Data partition in TWRP
I cannot: mount the System partition in TWRP, not even manually. It just does not let me select it, and gives an error whenever it needs to access it (e.g. if I try to backup it is says Error: unable to mount System)
I want: if possible to solve the issue without formatting Data. I had a TB backup but kinda old, so I got a Nandroid of Data and Boot out from TWRP and I suppose I could then recover stuff extracting from Nandroid through TB, but I've never done it and would rather be able to get a fresh TB backup and move on from there.
A few questions I have: any idea on why I am not able to mount System in TWRP? Could it help to reflash Boot or System, and if so how do I go to do that considering what I have is the whole CM rom package? (I remember being able to fastboot flash single partitions on Nexus devices but that's because the stock rom comes packaged in separate images).
Any input would be greatly appreciated!
Click to expand...
Click to collapse
The note 2 has this issue that makes it unable to be recognized by PC, so this isn't your phone problem, the only way to solve it is replacing the usb socket in your phone, anyway i can recommend dirty flashing your rom first, just flash the rom in recovery and wipe cache and Dalvik cache only then reboot.
If that didn't work, I'm afraid you might have to...... clear data ?
MigoMujahid said:
The note 2 has this issue that makes it unable to be recognized by PC, so this isn't your phone problem, the only way to solve it is replacing the usb socket in your phone, anyway i can recommend dirty flashing your rom first, just flash the rom in recovery and wipe cache and Dalvik cache only then reboot.
If that didn't work, I'm afraid you might have to...... clear data
Click to expand...
Click to collapse
Thanks for the input, I was thinking something along those lines but I wasn't totally sure, I always avoided dirty flashing as I heard of people having issues. Happily, it worked! Weirdest think I saw in a while, it gave me a bunch of errors with System partition (unable to mount, unmount, find), then it gave a "proceeding to patch system partition unconditionally", then it completed. The whole thing took less than 20secs so I do not think it even actually flashed the ROM. Now I am just getting some Play Services error, likely need to reinstall gapps, but phone boots just fine!
So, I can't restore my backup due to the error above. When I restore my backup, I get that error and a reboot loops me straight back into TWRP. You can read all that stuff below if you need the backstory.
(I had Lineage OS 18.1 installed and wanted to restore a backup from two weeks ago. So, I booted into TWRP, did a normal factory reset and restored the Backup of Lineage. However, it put out an error regarding something in root (structure needs cleaning). I tried rebooting into system, but it ended in fastboot mode. So I googled it and one thread said you can solve that by formatting system. "System" is backed up anyway, so I thought there was no harm, wiped it and restored the same backup once again. No error this time.
However, when I rebooted into system, the unlock pattern didn't work any more, even though I never changed it and always use the same one. I had to reboot into recovery, and now the TWRP unlock pattern didn't work either. Had to skip it and did another reset.
Now, every time I restore a backup (and those backups contain basically every partition available) it works, but when I reboot into system it just stops at the boot logo, then reboots into recovery. Basically a boot loop plus. Tried a fresh flash, same loop.
Also, all of my pictures and downloaded files are gone, because it's encrypted. I had to wipe data, which led to the whole encryption issue going away, however, I'm still stuck in that loop.
Does anyone know how to solve this cluster****? How do I get it to boot into system?
Edit: Managed to flash LIneage new after wiping data and system and it actually boots, hallelujah, but when I flash the back up I'm still at square one with the same fail and it fails to boot. )