Hi xda folks,
I wanted to update the LOS 14.1 to 17.1 from my girlfriends phone and I want to do a backup before just in case.
But my issue is, that when I try to boot the flashed TWRP (i tried twrp-3.2.1-0 and the newest one from xda 3.2.3-r1) and both seems to freeze at the boot splash.
One one thing is, that an adb connection works without issues. Is there a way to fix it?
The installed android/LOS 14.1 works fine and everything else also seems fine. I also flashed LOS recovery to check if it's an issue with the recovery mode of the phone in general but LOS recovery also works perfectly fine (but cannot create backups etc. so it's useless for my purpose).
I searched the forums and didn't find any clue about my issue.
Thank you in advance
Hi again. I managed to "fix" this.
at first I removed the battery for about 1 minute and then I tried to boot TWRP without the sd card with success. Inserting it afterwards produced some odd behaviour (the display buttons went missing).
Then tried it again with a sd card and it worked aswell. I use a 128GB card from sandisk.
Caution! This still can take a bit ~5-15 mins. I haven't measured the time.
Related
Hello!
I have a problem with my Galaxy Note 3:
On a monthly basis, I do a Online Nandroid Backup to my SD-Card.
After encountering a problem with the PlayStore, I booted into Recovery and recovered to my last "good" backup.
Since starting I had weird problems on my phone and I tracked them down to being a problem with the root access.
I used TowelRoot to gain root access again, but the SuperSU app didn't work. I then upgraded the SuperSU app, by deleting the old and installing the new version from the play store.
(After trying the uninstall function within SuperSU which did exactly nothing)
Since then everything kept working fine, but I encounter serious reboot problems.
With no clear time frame, my Note 3 Screen just freezes for 5 sec, and then the phone reboots. Sometimes I can use the phone 1 hour, sometimes 20 min until it happens again.
I have tried to narrow down the problem over christmas, and have the following points:
When I boot up, I have a SD-Card symbol in the notification bar which shows a sd card with a cog wheel in it. As soon as I enter my password it vanishes. Without the SD Card inserted I haven't encountered a problem, and it runs faster. So I reformated the SD Card in my PC to exfat, then reformated it again in my Note 3 and copied all the Data back (over my PC). After using it for 10 min, it rebooted again. I would really like to use my SD Card. 128 GB can't be the problem because it worked beforehand just fine.
In SuperSU I have set the root access to "allow always without questioning". This didn't change anything. I have fixed the Error from KitKat which blocks write/read access to the SD Card. So no problem there.
The problem still persists. And I have no clue what to do.
Tech Details:
Rooted: Yes (with Towelroot), SuperSU installed/working
Branding: None (International Version)
Micro SD-Card: SanDisk 128 GB
Android: KitKat 4.4.2 (Stock)
Recovery: ClockWork Mod 6.1ish (newest)
XPosed Framework installed
1. Factory reset your phone and flash the latest firmware official for your device.
2. Replace the SDCard for other and make some tests.
Joku1981 said:
1. Factory reset your phone and flash the latest firmware official for your device.
2. Replace the SDCard for other and make some tests.
Click to expand...
Click to collapse
Thanks for your fast answer.
As I mentioned above, the SD Card can't be damaged because it worked beforehand. So I think it is not a hardware issue.
As I have recovered from a working Backup it has something to do with the rights/root access and the SD Card.
Factory Reset is not an option for me, because I spent so much time costumizing this thing that it isn't worth doing it all again.
On the other hand:
I am thinking of Flashing CM 11 and doing a Titanium Backup Restore.
Do you think CM 11 would solve my problem?
A friend gave me a bricked samsung S5, he bought it while he was in China and upon coming home it wouldn't read the sim card so somehow he got to the conclusion that it was a copy and he bricked it.
Now two years forward he gave it to me, and I discovered that it wasn't a copy. I unbricked it but I have been having problems with the screen, when the phone goes to sleep and I try to wake it up only the buttons and the led will turn on, I can hear the phone vibrate and I can contact it via adb.
It also happens when I try to turn on the device, sometimes the screen will turn on sometimes it won't, the same with recovery and download mode.
This is what I have done to the phone until now:
1. Flashed twrp.
2. Flashed several custom roms.
3. Flashed the samsung firmware including the stock recovery (I had to flash each img separately since hidden.img wouldn't flash properly)
However still the problem persist, I have tried several solutions that I have seen online but none works and I am out of ideas.
Same Thing
loomely03 said:
A friend gave me a bricked samsung S5, he bought it while he was in China and upon coming home it wouldn't read the sim card so somehow he got to the conclusion that it was a copy and he bricked it.
Now two years forward he gave it to me, and I discovered that it wasn't a copy. I unbricked it but I have been having problems with the screen, when the phone goes to sleep and I try to wake it up only the buttons and the led will turn on, I can hear the phone vibrate and I can contact it via adb.
It also happens when I try to turn on the device, sometimes the screen will turn on sometimes it won't, the same with recovery and download mode.
This is what I have done to the phone until now:
1. Flashed twrp.
2. Flashed several custom roms.
3. Flashed the samsung firmware including the stock recovery (I had to flash each img separately since hidden.img wouldn't flash properly)
However still the problem persist, I have tried several solutions that I have seen online but none works and I am out of ideas.
Click to expand...
Click to collapse
I hope I am doing this right not on forums much. I am having the same issues. Any solutions
loomely03 said:
A friend gave me a bricked samsung S5, he bought it while he was in China and upon coming home it wouldn't read the sim card so somehow he got to the conclusion that it was a copy and he bricked it.
Now two years forward he gave it to me, and I discovered that it wasn't a copy. I unbricked it but I have been having problems with the screen, when the phone goes to sleep and I try to wake it up only the buttons and the led will turn on, I can hear the phone vibrate and I can contact it via adb.
It also happens when I try to turn on the device, sometimes the screen will turn on sometimes it won't, the same with recovery and download mode.
This is what I have done to the phone until now:
1. Flashed twrp.
2. Flashed several custom roms.
3. Flashed the samsung firmware including the stock recovery (I had to flash each img separately since hidden.img wouldn't flash properly)
However still the problem persist, I have tried several solutions that I have seen online but none works and I am out of ideas.
Click to expand...
Click to collapse
Hi,
You didn't mention a factory reset nor internal memory full wipe. Have you tried these?
JCSIGNGUY said:
I hope I am doing this right not on forums much. I am having the same issues. Any solutions
Click to expand...
Click to collapse
I did a factory reset and wiped the cache later on and it helped a bit but it still constantly turns off.
Same thing
loomely03 said:
I did a factory reset and wiped the cache later on and it helped a bit but it still constantly turns off.
Click to expand...
Click to collapse
I took cm 14 completly off took off GAPPS 7.1 wiped everything reformated micro sd . Went downloaded CYAN13 and GAPPS 6 saved to micr sd card and reinstalled all that . It seems to have worked. I don't know if it was me or I got a buggy CYAN14 probaly me.
JCSIGNGUY said:
I took cm 14 completly off took off GAPPS 7.1 wiped everything reformated micro sd . Went downloaded CYAN13 and GAPPS 6 saved to micr sd card and reinstalled all that . It seems to have worked. I don't know if it was me or I got a buggy CYAN14 probaly me.
Click to expand...
Click to collapse
I will try that, the phone worked fine for like 5 days but now the screen wont turn on, even when I try to access recovery or download mode.
Hi all. had an issue while trying to load up LinageOS last night. Was having trouble with keeping root. Seem to have solved that by using Magisk 11.6 and the SUaddon rather than any superuser version.
Anyhow as part of this i went back to a TWRP backup of which i had 3 different versions (stock and lineage) available being a bit ocd with backups. They all flashed ok, but for ALL of them, when the phone booted it kept telling me had wrong pattern when i tried to unlock. Not good. Thought only way back was to factory reset and do all the app loading and setup again.
After a bit of searching found this thread and this post.
https://forum.xda-developers.com/showpost.php?p=69189392&postcount=65
Worked a treat.
The other methods didn't and i suspect are obsolete.
Anyow, posted for info if anyone else runs into this problem. Success dependent on having working TWRP and being able to boot to that as you need to use the File Manager capability in TWRP.
Seeyahs!
Same thing happened to me last week, when I tried lineage, found the answer on HTC forum,.
So avoid that from happening , before you make a backup, unlock all securities( pin, password, fingerprint) then make a backup, next time you restore your backup, it will boot without any issues.
ta for that. will try.
Hey everyone,
I have been looking around online for several days now, but haven't been able to find a description of the problem I have with my n910f nor a solution.
When I got the phone it was stuck in bootloops and so I though it was soft bricked.
After I installed the custom rom and the latest version of TWRP via Odin, I thought that the problem was fixed, because the phone booted and I was able to start the configuration of Android (where it asks you for language, time zone etc.)
However, the phone turned itself off during this process. So I wiped everything and tried again, the same thing happened.
I then flashed it with Lineage, but it would turn itself off even before the logo appeared.
Then I flashed it with Ressurrection ROM, but again, the phone turns itself off during booting.
I can access download and recovery mode without any problems, I can flash roms and Odin works like a charm. I also used 2 different batteries.
Does anyone has an idea what I could try? Could it be the version of TWRP I am using (3.0.2.0)? Or is it a hardware issue?
Thank you!!
Hi, I have this exact same issue with my N910T and so far haven't found a solution to this. I really love my Note 4 so I'd like to know if this issue can be solved or not. I event went to a supposed repair shop and they couldn't figure out the problem, guess they weren't that good.
Sorry to hear this.
I have found issues that seemed similar, but not quite the same, and people hinted that it could be a worn out motherboard that is causing this top happen. But before I open up the phone (at the potential risk of breaking at least the screen) I would try everything else.
Or is there a way to test whether the motherboard is defective?
Its the plague of overheated, worn out emmc memories, sadly. Once it happen,the only way is a new/used motherboard,prefferably C model.
eMMC failure, snapdragon models are susceptible to this.
Tüddels said:
Hey everyone,
I have been looking around online for several days now, but haven't been able to find a description of the problem I have with my n910f nor a solution.
When I got the phone it was stuck in bootloops and so I though it was soft bricked.
After I installed the custom rom and the latest version of TWRP via Odin, I thought that the problem was fixed, because the phone booted and I was able to start the configuration of Android (where it asks you for language, time zone etc.)
However, the phone turned itself off during this process. So I wiped everything and tried again, the same thing happened.
I then flashed it with Lineage, but it would turn itself off even before the logo appeared.
Then I flashed it with Ressurrection ROM, but again, the phone turns itself off during booting.
I can access download and recovery mode without any problems, I can flash roms and Odin works like a charm. I also used 2 different batteries.
Does anyone has an idea what I could try? Could it be the version of TWRP I am using (3.0.2.0)? Or is it a hardware issue?
Thank you!!
Click to expand...
Click to collapse
I suggest flashing stock rom with Odin after wiping your whole device in TWRP. I've had the same thing about 2 months ago.
Hey,
thank you for your responses. Yes, I read a lot about it being a motherboard problem.
I got it to work now thanks to this post: https://forum.xda-developers.com/note-4/general/downgrade-official-mm-to-kitkat-t3383885
First nothing happened, but after I flashed Modem and the original Bootloader again (after installing the rom) the phone turned on and I was able to use it for a while (20mins maybe). Then suddenly it turned itself off and stayed on the "Samsung Galaxy" screen for a long time.
Apparently a lot of people are using Wakelock and it seems to be working for some of them, but that seems to defy the point somehow.
KirbyFan64 said:
I suggest flashing stock rom with Odin after wiping your whole device in TWRP. I've had the same thing about 2 months ago.
Click to expand...
Click to collapse
Which Stock Rom did you use exactly? Is your phone working fine?
Hello! Long time lurker on here but first time posting. I follow this guide to unlock bootloader and install twrp on the zc553kl. https://forum.xda-developers.com/zenfone-3/how-to/zenfone-3-max-zc553kl-bootloader-unlock-t3691837
It kind of worked, and it did flash twrp. The only problem is that the twrp although launching, didnt seem to have permissions to access storage, probably due to a data encryption problem. all the storages had 0mb sizes and i couldn't do anything.
So naturally i googled my problem and tried a few methods.
Nothing seemed to work, and i ended up doing an advance wipe. That also failed and it said it didnt have access or permission to do it (something along those lines). Next day i decide to try again and now my internal storage seemed to show.
So i ended up formatting it, and while the files seem to be still there, i changed .ext4 to .ext2 and back again, and then it stopped recognizing the stock rom i still had installed. Please note that before all of this, although twrp didnt work properly, the phone still worked fine and booted into android. My problem is now the stock rom is gone, twrp says no OS installed, and i have tried my best to reinstall the stock rom, but that hasn't worked. Any ideas or help would be welcome thanks guys
Nyoxx said:
Hello! Long time lurker on here but first time posting. I follow this guide to unlock bootloader and install twrp on the zc553kl. https://forum.xda-developers.com/zenfone-3/how-to/zenfone-3-max-zc553kl-bootloader-unlock-t3691837
It kind of worked, and it did flash twrp. The only problem is that the twrp although launching, didnt seem to have permissions to access storage, probably due to a data encryption problem. all the storages had 0mb sizes and i couldn't do anything.
So naturally i googled my problem and tried a few methods.
Nothing seemed to work, and i ended up doing an advance wipe. That also failed and it said it didnt have access or permission to do it (something along those lines). Next day i decide to try again and now my internal storage seemed to show.
So i ended up formatting it, and while the files seem to be still there, i changed .ext4 to .ext2 and back again, and then it stopped recognizing the stock rom i still had installed. Please note that before all of this, although twrp didnt work properly, the phone still worked fine and booted into android. My problem is now the stock rom is gone, twrp says no OS installed, and i have tried my best to reinstall the stock rom, but that hasn't worked. Any ideas or help would be welcome thanks guys
Click to expand...
Click to collapse
i downloaded a previous rom version from asus site and that flashed fine.