[At first, I have a Huawei p9 Lite] I recently was stuck in reboot mode, my phone would not boot up anymore and just keep rebooting so I went into twrp and did a factory reset without having a backup because I did not have any important files on my mobile. I then still could not boot up so I accidently wiped the whole cache and deleted my OS, so now my phone won't even boot anymore and it's stuck in the "Your device has been unlocked and can't be trusted" screen. How do I make my phone work again? I don't know anything about how to download stuff on my phone when I only have twrp left so I can install it with twrp and then boot again.
EDIT adb push doesn't work either and I can't wipe because it always gives me a red error line in twrp "Failed to mount '/cache' (opperation not supported on transport endpoint)
cxybah said:
[At first, I have a Huawei p9 Lite] I recently was stuck in reboot mode, my phone would not boot up anymore and just keep rebooting so I went into twrp and did a factory reset without having a backup because I did not have any important files on my mobile. I then still could not boot up so I accidently wiped the whole cache and deleted my OS, so now my phone won't even boot anymore and it's stuck in the "Your device has been unlocked and can't be trusted" screen. How do I make my phone work again? I don't know anything about how to download stuff on my phone when I only have twrp left so I can install it with twrp and then boot again.
Click to expand...
Click to collapse
OK so, whenever I try to adb sideload a rom from my pc to my mobile and I go to adb sideload in twrp and swipe it disconnects from my pc and I hear a de de de sounds
That device has an sdcard slot, so just move your desired rom over to that and flash it.
Also, may I ask what rom you had? Lineage os is available for your device (not sure, but if someone compiled twrp, sources are available which means that you can compile it for your device)
Related
Your Android device is stuck on bootloader screen? When you boot after rooting or installing a custom ROM on your device, you only see the big, dull logo of your manufacturer? Don't panic as this is normal and understandable. During the root or installation process, an error occured and ruined:silly: your entire operating system. When you install ROMs, you have to delete the current operating system, and if an error occur, it will terminate any installation done on your device, which leaves your device with came-with-box software components:crying:, which in this case the bootloader. It got stuck on the bootloader screen because your device has no available system to boot into. So the solution is simple:
Case #1. In case you've installed a recovery and have backed up your system, boot into recovery and restore it.
Case #2. If you haven't installed recovery, search through the internet for recovery installation tutorial for your device, make sure to search by the model e.g.GT-P5200 not the name e.g.Samsung Galaxy Tab 3. Boot into recovery and wipe everything exists on your hard disk. Transfer the ROM you want to install from your PC to the device turned on and with the recovery booting in, so the PC can access the device, or else it will be in accesible even if plugged in via USB cable. After that install the ROM you transfered to your device, and now it will boot.
Sorry that I couldn't be more informative, this is how far i can go, but if you have any questions, just quote my post, and I'll be in response.
See ya later!:fingers-crossed:
Hello, XDA-Members,
long story short, I tried to flash CM-13 on my Honor 5X(KIW-L21 B340). Well, that didn't work and the phone always booted into TWRP. So I flashed FlymeOS because I couldn't flash the stock rom anymore(No matter why.).
It worked perfectly, and I were able to use my phone. After restarting my phone it booted back into TWRP, tried to wipe and all that stuff and even re-flashed Flyme OS, but still booted into TWRP. I was so UPSET that I deciced to flash the original RECOVERY.img for my Honor 5X. Well and from there I made it worse.
Windows and Linux don't recognize my phone. Windows just shows an empty E:\ drive. Reinstalled Google USB drivers, reinstalled driver etc. Didn't work. Now, when I start my phone it boots into the honor 5x recovery. I got these options available:
- Reboot system now
- Wipe data/factory reset
- Wipe cache partition
So, well. I can't install a rom anymore. As well when trying to connect my phone to ADB it won't work either. ADB doesn't recognize my phone. I made a big bull****, tbh. Installed HI-Care as well, but it doesn't get recognized either. I can also boot into Huawei eRecovery, connect to my wifi because it says it can download the stock rom. Guess what, it always said failed so I'm not able to do this either.
I'm really stuck. Anybody got an idea? Thanks in advance!
dunios said:
Hello, XDA-Members,
long story short, I tried to flash CM-13 on my Honor 5X(KIW-L21 B340). Well, that didn't work and the phone always booted into TWRP. So I flashed FlymeOS because I couldn't flash the stock rom anymore(No matter why.).
It worked perfectly, and I were able to use my phone. After restarting my phone it booted back into TWRP, tried to wipe and all that stuff and even re-flashed Flyme OS, but still booted into TWRP. I was so UPSET that I deciced to flash the original RECOVERY.img for my Honor 5X. Well and from there I made it worse.
Windows and Linux don't recognize my phone. Windows just shows an empty E:\ drive. Reinstalled Google USB drivers, reinstalled driver etc. Didn't work. Now, when I start my phone it boots into the honor 5x recovery. I got these options available:
- Reboot system now
- Wipe data/factory reset
- Wipe cache partition
So, well. I can't install a rom anymore. As well when trying to connect my phone to ADB it won't work either. ADB doesn't recognize my phone. I made a big bull****, tbh. Installed HI-Care as well, but it doesn't get recognized either. I can also boot into Huawei eRecovery, connect to my wifi because it says it can download the stock rom. Guess what, it always said failed so I'm not able to do this either.
I'm really stuck. Anybody got an idea? Thanks in advance!
Click to expand...
Click to collapse
Shut down the phone
plug the phone into your windows PC
hold volume down + power to enter the bootloader
from windows open the command prompt - type fastboot devices hit enter (your phone serial number will display)
type fastboot flash recovery TWRP.img (be sure to use this TWRP and it's named TWRP.img and in the same folder as fastboot)
after the file is flashed successfully hold power + volume up + volume down
after 5 seconds let go of power and continue to hold the volume buttons until TWRP boots
From TWRP you can now copy the CM13.zip and Gapps.zip to your phone and wipe/factory reset - then install them one by one
be sure their are no errors .. if you see errors choose reboot recovery and try the flash again until it succeeds.
first boot of cm13 will take some time, be patient
Thanks,
I recovered my phone. Awesome!
My system crashed when I was typing in Whatsapp and since then the phone is trying to reboot but is stuck eternally in the boot screen with the Mi and Android logo. I only had 100 MB free space, so maybe the system cannot boot because of that?
- The newest version of Mi PC Suite cannot connect and an older MiPhoneAssistant version is only able to flash the ROM.
- I tried to clear caches with fastboot but it says "device is locked. Cannot erase". Also flashing TWRP is not possible.
- When trying to start adb shell in bootloader mode it only says "error: closed".
- It is possible to start adb shell when the phone is stuck in the boot screen, but without root permission I cannot access the data folder
So I really tried a lot, but as this whole topic is new to me, maybe someone has another idea? I once already successfully recovered encrypted files from an old Windows partition and I didn't imagine that this would be so difficult on a phone. I only need my notes from the MIUI Notes app, (almost) all the other stuff was backuped.
Is your phone bootloader is locked?
Jaga1234 said:
Is your phone bootloader is locked?
Click to expand...
Click to collapse
Yes, otherwise I would have flashed another one
So finally I had to use the testpoint method (https://www.youtube.com/watch?v=AE4JhUbZ_LQ) to flash a new ROM, but all data ist lost .
sector001 said:
So finally I had to use the testpoint method (
) to flash a new ROM, but all data ist lost .
Click to expand...
Click to collapse
I tried with qfil tool it was successful but still stuck at milogo , when i am trying with miflash there is some error always
I accidentally deleted my android os.
I tried to install one using a rom and twrp but it doesent work, so i tried using fastboot and adb tools but didnt work either.
I cannot access my stock recovery to apply an update beacuse of twrp.
Is my phone dead or is there any way to make my phone work again?
It doesent boot, just goes to an unlocked bootloader screen "Device will boot in 5 seconds" just freezes on that screen. I can go to twrp but when i try to install a rom it doesent work "error 7"
Its a Moto G5 XT1670 it has an unlocked bootloader, no root
Hi , this should help you to fix error 7.
https://forum.xda-developers.com/showthread.php?t=2522762
Hi folks,
I've got a new A52 5G and wanted it to root. TWRP couldn't be used, because each and every possible solution failed. I even got stuck at boot with a message that the recovery couldn't get startet, even if I just restarted the phone without pressing the keys and without plugged USB cable.
Even flashing the original firmware was not possible. Then I tried to lock the bootloader again and flashing of the firmware was going on with odin. Puh... Then I used the Magisk method without TWRP to change die boot.img with magisk and load it in Odin. Success! I had now root on the phone. Yesterday I read about uninstall Magisk and install it afterwards on the B partition for updating the firmware over OTA. But accidentally I pressed the button below "uninstall" and it performed imediately. Now my phone is dead again... With unlocked Bootloader it is stuck in a bootload and I can start the Samsung recovery mode to wipe the cache for example. I wiped the phone completely, but it is still stucked in a bootloop.
Then I tried my first method: Just lock the Bootloader again (in the download mode) and then flash the new firmware with odin. But Odin either crashes or is giving me instantly the message "failed".
When I'm trying to start the phone (it happened also after locking the bootloader) i'm getting the download screen and the message with a big red !
"partition boot
Reason boot: Hash of data does not match digest in descriptor. [2nd] (3)
Calculated Hash of (boot) : 23B8CFD554, (VEMETA) : D23E59ACD6
CUSTOM boot
VBMETA A526BXXU1AUCA, 38851814R"
Now I unlocked the bootloader again, to access the recovery mode so I can turn it off. Otherwise its stuck in the damn bootloop. Can't flash and wipe doesn't help either.
Please help me somehow -.-
why did you u
Insomnium_D said:
Hi folks,
I've got a new A52 5G and wanted it to root. TWRP couldn't be used, because each and every possible solution failed. I even got stuck at boot with a message that the recovery couldn't get startet, even if I just restarted the phone without pressing the keys and without plugged USB cable.
Even flashing the original firmware was not possible. Then I tried to lock the bootloader again and flashing of the firmware was going on with odin. Puh... Then I used the Magisk method without TWRP to change die boot.img with magisk and load it in Odin. Success! I had now root on the phone. Yesterday I read about uninstall Magisk and install it afterwards on the B partition for updating the firmware over OTA. But accidentally I pressed the button below "uninstall" and it performed imediately. Now my phone is dead again... With unlocked Bootloader it is stuck in a bootload and I can start the Samsung recovery mode to wipe the cache for example. I wiped the phone completely, but it is still stucked in a bootloop.
Then I tried my first method: Just lock the Bootloader again (in the download mode) and then flash the new firmware with odin. But Odin either crashes or is giving me instantly the message "failed".
When I'm trying to start the phone (it happened also after locking the bootloader) i'm getting the download screen and the message with a big red !
"partition boot
Reason boot: Hash of data does not match digest in descriptor. [2nd] (3)
Calculated Hash of (boot) : 23B8CFD554, (VEMETA) : D23E59ACD6
CUSTOM boot
VBMETA A526BXXU1AUCA, 38851814R"
Now I unlocked the bootloader again, to access the recovery mode so I can turn it off. Otherwise its stuck in the damn bootloop. Can't flash and wipe doesn't help either.
Please help me somehow -.-
Click to expand...
Click to collapse
why did you OTA update the rooted phone
it is clearly written that your phone might brick.
what happened to you is your boot.img file is replaced with the newer version try replacing with the boot.img file of previous version.
I didn't, because I get (as always, this is not my first rooted phone) the message, that the system has been changed. OTA is not working and I read that uninstall magisk, update the phone and BEFORE reboot install magisk again on partition B. But I accidentaly pressed the second option in magisk, complete uninstall or how its name is. Didn't expected, that its start instantly without a "Caution" message.
Uninstalling Magisk should not bring my phone into a bootloop anyway, even if I wipe the cache. Or am I wrong?
raja0408 said:
what happened to you is your boot.img file is replaced with the newer version try replacing with the boot.img file of previous version.
Click to expand...
Click to collapse
That is the problem how do I do that, when everything with odin stops imediately or odin crashes.
Does Odin give you any error messages? Are you patching all of the files for the firmware AP BL CP & CSC? Are you making sure to use the non home CSC? Have you tried using Samsung Smart Switch to recover your phone?
Smart Switch didn't recognize the phone. The only error on Odin was "succeed 0 / failed 1).
It worked with Windows 10 notebook and the USB C Port. However it didn't worked on Win 7 and regular USB Ports. Very strange. Well, but now I have the original firmware and again lots of bloatware. TWRP doesn't work, impossible to boot with it. How can I root the A52 with Magisk that way, to deactivate it - if needed - for firmware updates? The phone doesn't has A/B partition.
Same happened to me.
So, I have an A52 Indian version and want to flash the Canadian firmware. I downloaded different versions of the Canadian firmware and used Odin to flash. I followed the instructions on downloading the files, loading them into Odin,hit Start and it kept failing. It was giving an error message regarding a repartitioning error. Could this be due to having to tick "OEM Unlocking" in developer options which I hadn't done?
Hey, is your phone still stuck ?
SHAREit​