Hello,
i have used TWRP for saving all my data on the sd-card. And today i have restored the data without any problems.
A the end of this action TWRP asked something i don't remember what, it was two check box, and i have said yes.
And now my phone is blocked,
i can't boot on android (boot loop on first screen with unlock) , and when i try to access to TWRP i have only the fisrt page with the logo TEAWIN and nothing else .
If i reflashed TWRP it's the same things.
Thank's
Related
I have the Canadian Wifi version (5110). I was running rooted stock, with CWM.
So, here's the situation that I'm in: The device was encrypted. After a bad restore from titanium my note would get stuck on the samsung animation (after asking for the encryption password). I went into recovery and formatted /data. After reboot, it kept asking me for the encrypted memory password (and not accepting the correct one). I then formatted all the other options that were in there (/preload, /system, /sdext etc). It still doesn't start after reboot. Shows the Name of the unit and just stays there, no samsung animation. I can power off and get into recovery again. I can flash other roms (I tried CivZ-FlexBeam) and once again I get to the point where it asks for the memory password (which it accepts) but doesn't go any further.
Edit: Solved it by flashing stock recovery and doing a factory reset from there.. thanks to civato here: http://forum.xda-developers.com/showthread.php?t=2333191
Long story short installed substratum and it was working fine, had a navbar theme already running and installed another one. Few hours later rebooted phone and when it booted back up systemui crashed and it went into bootlooping into that over and over again. Now it bootloops a few times and goes into a recovery menu that only gives me the options to try rebooting again or a factory data reset.
The phone boots into bootloader/fastboot just fine and I can get into recovery but the only options I have are 'try again' and 'factory data reset' I know that FDR is basically my only option and so be it. BUT IF POSSIBLE I want to try and backup the internal data or at least as much of it as possible.
So, is it possible to backup any internal data with only having access to bootloader/fastboot.
I've spent over an hour searching to this answer but either I was searching wrong or simply was not able to find the answer. Pixel XL is 100% stock. Never modded, never rooted, stock recovery, stock latest official Oreo from OTA update.
So again. Absolutely no access to the OS. Only access bootloader/fastboot and a form of the recovery menu and I would like to somehow backup the internal data. I don't care about apps or any app data, specifically just the user data if at all possible. If not well then I'm screwed and that's that.
Hello,
Happened to me also something like this. The phone rebooted and the only option were those presented to you also. But, I pressed the "Try again". If this still doesn't work, when the device is rebooting, and the white screen appears, try and hold on to the power button until the moving dots appear.
Also, this didn't wipe anything on my device.
Hope this is useful to you.
moraritza1 said:
Hello,
Happened to me also something like this. The phone rebooted and the only option were those presented to you also. But, I pressed the "Try again". If this still doesn't work, when the device is rebooting, and the white screen appears, try and hold on to the power button until the moving dots appear.
Also, this didn't wipe anything on my device.
Hope this is useful to you.
Click to expand...
Click to collapse
Does nothing. Just reboots back into recovery. I've tried Try Again probably 100 times and nothing ever changes. Even safe mode does not work. The SystemUI is completely dead.
I'm 90% sure there is no way to fix the phone other than factory data reset and I'm fine with that. I just want to know if I can backup anything from bootloader/fastboot before I do that.
Have you tried using ADB to boot ( not flash ) a custom recovery, and from there to backup the phone, and after if it's possible, to use the USB-OTG to copy that backup to an USB memory stick?
Looking at the Substratum FAQ in the app it says that if you experience a bootloop you should be able to flash /storage/emulated/0/substratum/SubstratumRescue.zip in recovery and it should fix the boot loop.
matt0720 said:
Looking at the Substratum FAQ in the app it says that if you experience a bootloop you should be able to flash /storage/emulated/0/substratum/SubstratumRescue.zip in recovery and it should fix the boot loop.
Click to expand...
Click to collapse
As Matt already mentioned, there's a rescue zip file which comes by default with substratum. It's purpose is to remove all overlays which you've currently installed.
In case you don't have a custom recovery installed you can simply boot into twrp via adb (without having flash the recovery)
Android-xp said:
As Matt already mentioned, there's a rescue zip file which comes by default with substratum. It's purpose is to remove all overlays which you've currently installed.
In case you don't have a custom recovery installed you can simply boot into twrp via adb (without having flash the recovery)
Click to expand...
Click to collapse
What if you're bootloader locked? Is there a way to recover from a bad overlay?
You could try to flash the factory image if you've unlocked the BL, just remove the -w from the flash all script
bobby janow said:
What if you're bootloader locked? Is there a way to recover from a bad overlay?
Click to expand...
Click to collapse
If you have checked the option to potentially allow unlocking your bootloader in dev-settings you can use fastboot to unlock your bootloader and boot into the bootable recovery image
I tried to update to the latest update to the Razer Phone and was able to install it successfully, but when I went to install Magisk on the new update, it caused the Wifi to stop working. For that reason, I tried to restore my old TWRP backup I made prior to updating which everything was working before updating. I wiped cache, dalvik, data and system and restored my old backup. Now when I try to boot, it gets stuck at the Razer logo and doesn't get past that. I also tried wiping data and restoring the system image only to no avail and it didn't do anything.
Have you tried booting to TWRP and booting The other [email protected]
How long did you wait on the Razer logo.. When I reset my phone after relocking it.. It took 10+min for first boot. I was scared it wasn't gonna work but I just left it alone and it eventually booted itself up
mikeandjaimie said:
How long did you wait on the Razer logo.. When I reset my phone after relocking it.. It took 10+min for first boot. I was scared it wasn't gonna work but I just left it alone and it eventually booted itself up
Click to expand...
Click to collapse
Thanks. I'll try that and see if it works. But I let it sit for 5 or so minutes.
Edit: I'll go ahead and add it was stuck at the Razer logo. It never got to the actual boot animation.
Edit 2: I let it sit for 20+ minutes and it wouldn't boot or get past the Razer logo.
RUNNERX said:
Have you tried booting to TWRP and booting The other [email protected]
Click to expand...
Click to collapse
Yes I've tried switching slots and it didn't work.
Any luck with the stuck at logo screen? I followed instructions from Razer and fkashall and now it won't boot to recovery download or system . It just hangs at the logo screen for better part of 2 hours now so it's not a waiting game .. any luck in fixing yours?
hi there, same here after flashing google pixel experience on razer phone1. seems to be a general problem for many users. Any hints?
Best regards
Michael
I have the same problem, but I wasn't updating or installed any new app. I was just ordering food from an app and then all of a sudden my phone restared and got stuck in a bootloop.
I reflashed the stock rom, over and over, slot a or slot b, hoping that would fix it somehow... it's just stuck there now. I could go into download mode and recovery mode. but, it's only until there.
now it's bootloop until it gets into download mode...
ThatGuy94 said:
I tried to update to the latest update to the Razer Phone and was able to install it successfully, but when I went to install Magisk on the new update, it caused the Wifi to stop working. For that reason, I tried to restore my old TWRP backup I made prior to updating which everything was working before updating. I wiped cache, dalvik, data and system and restored my old backup. Now when I try to boot, it gets stuck at the Razer logo and doesn't get past that. I also tried wiping data and restoring the system image only to no avail and it didn't do anything.
Click to expand...
Click to collapse
I could fix it. After flashing (even Android Pi) you have to do a factory reset.
IMPORTANT: THE FACTORY RESET IN TWRP DOES NOT WORK. So you have to flash the boot-sector in your system partition with the stock boot.img and reset to STOCK RECOVERY by typing "fastboot reboot" and pressing the vol-up button. Once in stock recovery, do a factory reset and return to bootloader. Now you can flash the boot.partition with twrp boot.img, install in recovery the stock boot.img, install the twrp-installer.zip and reboot to system. The bootlogo will not stuck anymore.
I hope, I could help you. Do not forget to backup before trying.
Best regards
Mellus
sry for my bad english
Well, I will be straightforward... I'm probably pretty much f**ked.
I have a Xiaomi Redmi 5A which was never tampered with, ever. It had Android Oreo 8.1, MUIU 10, never rooted, never unlocked. It was my wife's. She bought a new phone and now I wanted to use this Redmi 5A.
So I intended to flash a custom ROM on it. I did my research and picked Ancient OS for the custom ROM (https://forum.xda-developers.com/t/rom-10-0-0_r39-official-ancientrom-civilization.4113993/).
I started all the work. First, unlock bootloader. I used MIFlash unlock provided by Xiaomi itself. Followed all the steps and unlocked the bootloader. After this it was time to flash a custom recovery. I chose TWRP. Tried to use their own TWRP riva image (twrp-3.5.0_9-0-riva.img) but it didn't worked. Whenever I flashed, after rebooting, the stock recovery would overwrite TWRP. This was supposedly because this version of TWRP was based on Nougat and my phone was on Oreo, so I searched a bit more and found a guy who has modified TWRP to work with Oreo. I flash his version and flashed lazyflasher afterwards et voilà! The TWRP installed correctly and was no long overwritten by stock recovery.
After this I made a FULL backup of the stock ROM using TWRP (System, Cust Vendor, Data, Boot, Bootloader, EFS, Persist, Logo) and stored the backup on my computer.
Then I proceed to flash the Ancient OS ROM. First I went to wipe on TWRP > format data > yes. After this I went to wipe again > advanced and selected to wipe Dalvik, Data, System, Cust Vendor, Cache. And finally then, to install and flash the ROM. Things were a bit weird here because when I tried to flash TWRP threw Error 7 which is related to a script protection to determine if the ROM is compatible to your phone. The thing is... the ROM was compatible. I checked the "updater-script" inside the ROM file the code lines to check for the device were correct, it displayed riva as the model, which is my phone. One of the solutions to Error 7 was to eliminate these lines from the script, which I did and so I was able to flash the ROM. Everything went well and reboot to system.
System boot up, splash screen, main screen. All were good. Device timed-out and the screen locked. After the screen lock the only thing appearing were bizarre vertical red lines. Phone was still responsive, but screen was not being rendered properly. Forced reboot, splash screen... and main screen again, all normal. Tested to lock to notice the screen error again, and there it was: red lines just after I locked. Rebooted once again... only this time I went stuck on bootloop (on logo). Decided to boot to recovery to restore things, but, for my astonishment TWRP didn't started. The TWRP logo appeared as if it was loading, but nothing happened and if I leave it like this for some minutes, it just reboots to recovery once again but without TWRP being able to initialize and keept stuck on this reboot to recovery loop.
I don't have the slightest idea how can the recovery be affected by a ROM flash, seriously... I never saw this. It is a completely different partition. Worst of all, everything on TWRP was working before flashing the Ancient OS ROM.
I have no idead what to do. Can't enter system, can't access TWRP and can't use fastboot (most likely because USB debugging was disabled after OS was flashed). If some one can shed some light... it would be truly appreciated.
Auto-reply... Solved this issue flashing the original Stock ROM (I mean the Stock ROM that came with the phone back in 2017; before ANY updates.) with the own Xiaomi Mi Flash.
Be advised: This Xiaomi tool only works with devices that have unlocked bootloader.
/EDIT:
Alright, the thread can be closed. I somehow managed it.
In case someone faces the same issue, I used twrp to dd the sdf files back on the phone which stopped the reboots. After that, just wiped and formatted everything again and reinstalled the ROM.
Hello guys,
I hope you can help me with this issue since I've tried everything I know to fix this problem.
The plan:
Unlocking bootloader, installing TWRP and xiaomi.eu ROM on a new device.
Changing its IMEI with QPTS/QFIL afterwards.
What happened:
Unlocked successfully. Installed TWRP, xiaomi.eu ROM and Magisk.
After pulling the QCN backup and editing the file I pushed it back to the phone what seemed to work.
After rebooting, I noticed that the phone rebooted 5 seconds after showing me the "Enter PIN" screen.
Booted up again and the same thing happened.
I booted into TWRP, wiped and formatted "data", installed the ROM again. The phone started up normally and there was no reboot.
I went back to TWRP and flashed Magisk, the phone crashed again and everytime I boot it up, it immediately reboots after some seconds. Installing Magisk somehow triggers the phone to reboot on its own.
I thought to start over, flashed everything from stock using Mi Flash Tool and the newest China Rom.
After starting up the phone, the issue still exists. This time with this rom there is no difference between installing Magisk or not, the phone always reboots after showing up the miui welcome/setup screen.
Current situation:
The phone boots up Android, reboots after some seconds and goes into fastboot automatically. After the fastboot timeout it again reboots automatically, goes into the OS and crashes again and on and on.
No matter what I do, I can't keep the phone from rebooting.
And since I can't flash Magisk, I have no root.
This means that I can not use root to put the phone into diag mode to restore the original qcn file.
I have backups of the EFS partition and also sdf7/8/9/10 files. I just don't know how to restore them given the current situation.
Thank you very much in advance for your support!
Cheers