Hey,
I'm quite new with all this stuff and I just got into some problem. I wiped everything in recovery mode using twrp, cache and internal memory etc (dont ask me why). Anyway, my phone seem to be stuck on a booting loop since I can't enter recovery because twrp fail to load up correctly. You can see where it gets stuck in the image I attached.
Someone know what's wrong and if it's possible to fix somehow?
Thanks :fingers-crossed:
Okay, it seems like I managed to fix it myself. I used adb and fastboot to install everything as stock.
https://developers.google.com/android/images
However I'm not sure about the USB debugging part, how do I enable that if there is no os installed? Do I even need it enabled when I use fastboot?
Related
Hi all,
So, I done effed up. I've been running Elegancia with no problems for a while now, and decided off the cuff to try something new. Long story short, I didn't read properly and ended up flashing an International ROM to my phone by accident. No problem, I think, I'll just ADB sideload Elegancia again.
I boot into TWRP recovery and then find that my computer no longer recognizes my phone. So, I hit restore on TWRP, and restore a backup that I'd made beforehand. After everything finishes restoring, I discover to my dismay that the backup did not include my OS.
Now, when I power up my phone, I can boot only into bootloader. When I try to boot into recovery, the phone is stuck on the TeamWin logo and doesn't move. If I turn on the phone without booting into bootloader, I'm stuck on HTC's logo. My primary goal right now is just
In conclusion, I have no idea what to do with the following problems:
1. When booting into bootloader, my computer no longer recognizes my device, so I have trouble flashing TWRP. Basically, my computer searches for an HTC MTP driver, and then fails to find one/install one. When I try to update the driver manually by downloading a MTP driver and then installing via Device Manager, Windows tells me I'm already using the most up-to-date version.
2. When booting into bootloader and then going to Recovery, my phone will boot into teamwin's logo ... and then not move from there.
I'm aware that I've screwed up pretty bad-- I've done my best to read stuff that's relevant, though. I'd love more help, please! Thanks in advance. Lots of invisible cookies coming your way.
[EDIT: It turns out TWRP was just taking a really, really, really long time to load. That said, my problem now is this:
- When going to Advanced -> ADB Sideload, my computer does not recognize my device when using adb devices.
How can I make sure that this actually works? Thanks again!]
[EDIT #2: Okay, um, I don't know why, but for some reason my computer now lists my device after going into sideload from TWRP. Maybe something to do with a reboot of my computer. If that's true, I feel really stupid. Will update if sideload doesn't work ... I think the cosmic gods are laughing at me. I guess all I had to do was post in xda-developers so that I could publicly embarrass myself before I fix my phone.]
[EDIT #3: Everything works and I'm dumb.]
I had NOS Google Play ROM on my phone, but now it won't boot up and I forgot to set a backup file. Now I am stuck in TWRP since I can't boot up the phone. Also, I deleted the ROM file from my phone. Yes call me stupid all you want but I seriously need this fixed.
So what happens is, I boot the phone, goes to the boot screen, and shows it is booting, but it never does boot. It's in some kind of an infinite loop.
On top of that, I can't transfer files in TWRP!!
Does anyone know how to fix this? I know there is a fix to this, but I can't seem to get any to work or most just don't make any sense.
If you have boot loader unlocked (most likely) try fastboot flashing boot.img in fastboot mode
Sent from my DNA
hddr3 said:
I had NOS Google Play ROM on my phone, but now it won't boot up and I forgot to set a backup file. Now I am stuck in TWRP since I can't boot up the phone. Also, I deleted the ROM file from my phone. Yes call me stupid all you want but I seriously need this fixed.
So what happens is, I boot the phone, goes to the boot screen, and shows it is booting, but it never does boot. It's in some kind of an infinite loop.
On top of that, I can't transfer files in TWRP!!
Does anyone know how to fix this? I know there is a fix to this, but I can't seem to get any to work or most just don't make any sense.
Click to expand...
Click to collapse
USB OTG Cable, thumbdrive, rom image on thumbdrive, install from external SD.
Boot into recovery and connect the device to your pc and open a terminal and type in adb devices to make sure the pc recognizes your phone and it should. The just adb push a different Rom to the sdcard wait for that to finish and flash. Or if you can get adb sideload to work you can do that too.
You can use adb push/pull in recovery without mounting anything or at least it works for me...
Sent from my dlx using XDA Premium HD app
I'm new to rooting and all of this type of thing, i figured I would first start with my HTC Flyer. I successfully unlocked the bootloader, and installed SuperUser, upon installing greenify and i tried to install the Xposed Framework, and my device now is stuck in a boot loop.
When enter the bootloader and do a factory reset or try to enter factory it completely freezes, and when i try to connect it to my PC via fastboot the PC says that the USB device that is connected cannot be recognized and fastboot will not work. Did i completely fry this device? Also if you have time I couldnt figure out a proper way to flash a custom rom so if anyone has a guide for that I would appreciate a link to that as well.
Thank you so much!!
So, I have quite a problem, and having a country-native device isn't really helping.
I have a Cherry Mobile J2s in 6.0 with bootloader access allowed.
I seemed to have failed in rooting my phone by doing 'fastboot recovery twrp-3.2.1-0-cherry.img' it seemed to have been added properly but it said something like 'recovery' partition successfully made. I'm not sure if that's something wrong but I placed it in just in case. Because of this, my phone showed the Encryption Unsuccessful.
Here's the bad part. It doesn't seem to be able to reset itself. It just stays on the opening screen that says Flare J2s. It doesn't seem to open up the reset screen which I see from other tutorials. I believe it's because I failed to install the recovery img correctly, most especially since I had nothing like a boot img to use. I have tried opening recovery mode but to no avail. I seem to not have a way with connecting my phone to my pc so I can't use adb to fix itself.
Does anyone know how to fix this problem? Thanks in advance. ^^
Pink Panther Bumps
Bu-bump. Bu-bump.
Bu-buh, bu-buh, bu-buh, bu-buh-
Bu-buuuuuump. Bu-bu-bu-bump.
thatguy396 said:
So, I have quite a problem, and having a country-native device isn't really helping.
I have a Cherry Mobile J2s in 6.0 with bootloader access allowed.
I seemed to have failed in rooting my phone by doing 'fastboot recovery twrp-3.2.1-0-cherry.img' it seemed to have been added properly but it said something like 'recovery' partition successfully made. I'm not sure if that's something wrong but I placed it in just in case. Because of this, my phone showed the Encryption Unsuccessful.
Here's the bad part. It doesn't seem to be able to reset itself. It just stays on the opening screen that says Flare J2s. It doesn't seem to open up the reset screen which I see from other tutorials. I believe it's because I failed to install the recovery img correctly, most especially since I had nothing like a boot img to use. I have tried opening recovery mode but to no avail. I seem to not have a way with connecting my phone to my pc so I can't use adb to fix itself.
Does anyone know how to fix this problem? Thanks in advance. ^^
Click to expand...
Click to collapse
The proper command should have been fastboot flash recovery twrp-3.2.1-0-cherry.img . I am not to familiar with the device you are using, but can you put it in download mode? If that's an option, try to reflash the same firmware you are using to recover your phone.
Bump
Bump.
I think first you need to unlock bootloader before flashing that custom recovery .
Similar problem and Fix you can find here:
https://forum.xda-developers.com/showthread.php?t=2453849
Good Luck .
Hi there! I'm hoping someone on XDA Developers can help me sort out a root gone-wrong.
I did my best to follow the guide on XDA. I have an Umidigi A9 Pro with 6gb ram. I was successfully able to get the android tools on PC and was able to unlock the bootloader. I went to the Umidigi website to get the ROM. I think I *might* have grabbed the wrong one. Once I got this zip from the Umidigi website, I unzipped the folder and copied the boot.img that was in that root folder to the device. I then went into Magisk and patched the img. I then copied the patched img to my PC then use the commands on the XDA guide to flash the image to the device, the flash was successful (I think). However the device is now stuck in a boot loop. The device displays the Umidigi OEM logo and the android logo; underneath it says in small text:
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
after 5 seconds the screen goes black and then comes back with the same screen. This happens continuously. I have tried holding the volume down, the power button, and several combinations of volume up, down, and power. Holding all buttons down makes the screen stay black, however while plugged into the PC the PC still makes the device connected and disconnected sounds off and on. Whenever I release the buttons, it goes right back to the loop. Windows PC plays the device connected and disconnected sound on and off. The command prompt is not able to affect the device. When I run "adb devices" it doesn't display the phone so it doesn't seem that windows is detecting the device.
ROM: https://community.umidigi.com/forum.php?mod=viewthread&tid=22236&extra=page=1
https://www.umidigi.com/page-Download.html
I'm hoping for some help on this one
Thank you!
It should be obvious that when being in a bootloop ADB cannot function: On Android side the ADB daemon gets started and after seconds closed, and this over and over again.
In the simplest explanation, a bootloop describes when your phone is stuck in a loop of rebooting. The term "bootloop" is just a more common way of saying "reboot loop."
Curious if you ever managed to get this figured out? I'm in essentially the same situation, though I was not attempting to flash a ROM. I successfully managed to get TWRP 3.5.2 installed and then I was trying to get Magisk installed.
My phone data was wiped, which honestly I didn't care about, however I must have done something wrong with the Magisk installation as now I have the rebooting issue.
I'm able to use ADB and have been trying to push a ROM to the sdcard folder of the internal storage. ADB says the file has successfully completed, but nothing is on the phone. I fixed the issue of the storage showing up as 0MB by changing from EX4 to EX2 and then changed it back to 4.
Really unsure of how to flash a ROM if I can't get the file to pushed to the phones internal memory though.
Zeidwinder said:
Curious if you ever managed to get this figured out? I'm in essentially the same situation, though I was not attempting to flash a ROM. I successfully managed to get TWRP 3.5.2 installed and then I was trying to get Magisk installed.
My phone data was wiped, which honestly I didn't care about, however I must have done something wrong with the Magisk installation as now I have the rebooting issue.
I'm able to use ADB and have been trying to push a ROM to the sdcard folder of the internal storage. ADB says the file has successfully completed, but nothing is on the phone. I fixed the issue of the storage showing up as 0MB by changing from EX4 to EX2 and then changed it back to 4.
Really unsure of how to flash a ROM if I can't get the file to pushed to the phones internal memory though.
Click to expand...
Click to collapse
I honestly haven't messed with it since. It was a very cheap extra android phone I had laying around. Once it got messed up I pretty much just put it in a drawer and said "maybe another day"