Hi everyone.
Well it's a well known issue of yuphoria to get stuck on bootloop and you can find many youtube video to fix it too. My yuphoria is now experiencing the same problem. It is stuck in bootloop. Thing that is different in my case is it bootloops on anything. Even if i connect it to a power source or a laptop, it start itself and get stuck in bootloop. I also noticed that it is not recognized by my laptop in adb command prompt so i cant even rely on traditional "boot in recovery method". I tried to put it manually on fastboot mode by pressing down the pwer key along with vol down key. It does reboot in fastboot mode but still is unrecognizable by adb fastboot commands. I flashed bootleggers rom that was based on oreo 8.1 and was my daily driver on this device. Worked quite well too. I also installed twrp recovery but it seems to be absent now as I cant enter in recovery mode in anyway. Please suggest some means to fix this device. Thanks in advance.
Related
I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.
mattlokk said:
I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.
Click to expand...
Click to collapse
Did you set:
Allow oem unlock in dev opt.
Fastboot protocol into BL?
Twrp app & manager need root to work.
Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link
thanks for the help, i'll try and work through this soon.
fpozar said:
Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link
Click to expand...
Click to collapse
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.
mattlokk said:
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.
Click to expand...
Click to collapse
Okay so I'm guessing you have stock ROM.
To flash TWRP you have to enter fastboot mode (vol down + power I believe) and flash the twrp image with fastboot flash recovery twrp.img (rename the shield tablet twrp to just twrp.img and place it into your easy adb and fastboot folder)
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck
fpozar said:
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck
Click to expand...
Click to collapse
Agreed. This is probably what is happening (as described on the TWRP webpage here:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Alternately, immediately rooting (flash SuperSU or Magisk) right after flashing TWRP, will prevent TWRP from being replaced with stock recovery.
Although the inconsistent fastboot connection, and how much trouble you had flashing TWRP initially, is a bit worrisome. Try using a different cable (maybe the one you are using is not connecting well?) try another USB port on the computer, and don't use a USB hub (connect direct to the PC).
Well, like they say: persistence is key. I kept pushing and trying new things until eventually.... I bricked the device. No, not really, it's working great now on LineageOS.
Thanks again to everyone who helped me out :good:. I'm still not sure exactly what caused TWRP to stop working on my device, however following this guide helped me fix it: https://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462
The "flash-all.bat" restored everything to stock (including the recovery mode) and after that I was able to flash the latest TWRP and install Lineage.
Hi There!
I'm exeriencing a wierd problem:
On my rooted Doogee S60, i was able to enter the built in recovery mode (and from there the fastboot mode) with Vol+ and Power.
Since i've installed a twrp recovery.img, pressing Vol+ and Power will launch the TWRP UI (wich i cant use, because my touchscreen is disabled).
Normal boot won't work eighter - i flashed a corrupted system.img file as it looks like (ooops). There is also the message at the Boot Screen saying:
"Orange State - Your device has been unlocked and can't be trusted. Your device will boot in 5 seconds"
... although these 5 seconds won't countdown and the device won't boot.
If i enter the TWRP, i can still access the ADB mode. So i can sideload stuff on the device, even the sd card is shown on pc. But the command
adb reboot fastloader
will reboot the phone, but not load the fastloader/fastboot - as it stucks at boot screen (orange state).
Any other ideas to access fastboot, due to flash the recovery.img again with the original to fix?
... or simple question: did i brick it?
thx in advance
Command
Code:
adb reboot fastloader
doesn't exist.
Look inside here:
How to Reboot Android Device into Fastboot or Recovery Mode via ADB « My Digital Life
If you’re using Android phones, tablets or devices, which is proliferating across all markets, prices and channels nowadays, then you may want to familiar yourself with fastboot or recovery mode, which is useful when you need to troubleshoot your beloved phone from the like of Samsung, HTC...
www.mydigitallife.net
introjoe said:
Hi There!
I'm exeriencing a wierd problem:
On my rooted Doogee S60, i was able to enter the built in recovery mode (and from there the fastboot mode) with Vol+ and Power.
Since i've installed a twrp recovery.img, pressing Vol+ and Power will launch the TWRP UI (wich i cant use, because my touchscreen is disabled).
Normal boot won't work eighter - i flashed a corrupted system.img file as it looks like (ooops). There is also the message at the Boot Screen saying:
"Orange State - Your device has been unlocked and can't be trusted. Your device will boot in 5 seconds"
... although these 5 seconds won't countdown and the device won't boot.
If i enter the TWRP, i can still access the ADB mode. So i can sideload stuff on the device, even the sd card is shown on pc. But the command
adb reboot fastloader
will reboot the phone, but not load the fastloader/fastboot - as it stucks at boot screen (orange state).
Any other ideas to access fastboot, due to flash the recovery.img again with the original to fix?
... or simple question: did i brick it?
thx in advance
Click to expand...
Click to collapse
Hi introjoe,
Are you doing? i have the doogee s60 but i just cant root it :'( can you tell me please how did you do it, or the files you use for it? i allready tried but, when i reset and enter fastboot mode, my pc simply dont recognize it.
I want to upgrade the android system to 9 or 10, thats why im doing all o this.
Thanks in advance.
@doryan666
i wasnt able to root the device in the end unfortunately.
i tried using an unofficial twrp, but i was stuck at the main boot screen
i t seems to need some bootloader-activation-code to enter the bootloader to install a new os.
the command line would look like
adb reboot bootloader "CODE"
the activation code has not been released yet by doogee ... and most probably never will be.
sorry to say but i dont think android upgrad will be possible with this device
Good morning!
While attempting to flash a stock MIUI 10 ROM into my Xiaomi Redmi Note 7, to downgrade back to Android 9.0 due to some app compatilibty issue, I messed up big time and my phone is now stuck in a loop where the screen turns on, nothing shows up, then it restarts, going off for a few seconds and turning on again.
Power Button + Volume UP successfully brings me to the stock recovery 3.0 from xiaomi.
Power Button + Volume DOWN fails to bring me to the fastboot mode.
If I select the Connect with MIAssistant in the recovery the phone will show up as "sideloaded" after using the command adb devices, but the MIPCSuite app does not see it and the command adb restart bootloader also fails to bring up the fastboot mode, it just gets stuck in the loop again.
More context on what went wrong and caused this: I followed an online tutorial to flash a rom using the MIFlash app, so I unlocked the bootloader and tried to flash the rom usin xiaomi's tool. I got a failed to check sparse crc error code and it went downhill from there when I tried to fix things reading multiple threads on the issue. I tried deleting some lines from the flash_all.bat file and tried to flash it again but then the flashing process went seemingly forever so I aborted the operation and now this loop happens. I tried a few more times but with no success.
The first time I tried to use the tool I used the clean all and lock option so I'm not certain if the miflash tool locked the bootloader regardless of the outcome of the flashing attempt.
Is there hope? Can I fix this phone if I only have access to stock recovery and nothing else (although it shows up in adb devices but can't get into fastbootmode) ?
Thanks a lot to anyone who took the time to read and possibly help.
Both ADB and Fastboot are Android-side launched by device's bootloader. If you can't enter Fastboot mode then my guess is there is something is wrong with curently installed Android.
BTW: If you lock device's bootloader then bootloader attempts to load device's Stock ROM.
jwoegerbauer said:
Both ADB and Fastboot are Android-side launched by device's bootloader. If you can't enter Fastboot mode then my guess is there is something is wrong with curently installed Android.
BTW: If you lock device's bootloader then bootloader attempts to load device's Stock ROM.
Click to expand...
Click to collapse
I see.
What can I do to try to fix this issue?
I finally managed to fix it through the Emergency Download Mode (EDL). It requires Xiaomi Authentication which I bypassed using this guide: https://www.droidwin.com/fix-mi-account-authorization-unbrick-xiaomi-edl-mode/
With that setup I flashed a stock rom using the MiFlash tool.
Hello everybody,
I have a LG K520EMW with Android 10 Stock ROM,
According to Treble Check I have a system supporting system-as-root and a system partition A/B
So I downloaded a GSI from the phhusson's Treble Experimentations
But here are my problems :
- the phone won't boot at all on Fastboot mode (tried adb reboot bootloader, adb reboot-bootloader, both from sideload mode and normal mode, tried plugging the phone when it's off holding vol + or Vol - keys, and using QuickBoot, obviously didn't help because the phone is not rooted)
- the phone won't boot either on Recovery mode, it displays "No Command", i've tried all possible key combinations with vol +, vol -, power, camera, nothing happens and it stays on "No Command",
- Can't root with any tool, I tried KingRoot, KingoRoot, mtk-su
The only door open for me right now is sideload, I know I can type "adb sideload rom.zip" but the issue is I haven't unlocked bootloader, so I don't know what happens if I do this...
I've found nothing on the web about this phone, so if anyone have some informations or knows any procedure on another phone which would be applicable on this model, it would be great
Well, some news, i've figured out a dirty vay to access Fastboot mode, very very dirty :
I've tried, just to see what it does, adb sideload lineageOS-18.1-etc.img, and like a rabbit getting out of a hat, a recovery menu appeared and I could access Fastboot,
Now, I still have to find out why when I try fastboot oem unlock or fastboot oem device-id ( LG official procedure )
I have enabled OEM unlock in debugging options of course
On the Fastboot screen, Bootloader version is unknown,
When I try fastboot boot twrp.img, it answers "Download is not allowed on locked devices"
So, if anyone has an idea, I'd be very grateful
Hey everyone,
I tried flashing Paranoid Android Sapphire Alpha 3 on my OnePlus 8. I rolled back to OxygenOS 11, tried to flash the ROM through fastboot and got a partition error. After that I was stuck in Qualcomm CrashDump mode. Some hours later while trying to make the MSM tool work the phone somehow started again and updated to OxygenOS 12, but I had no network coverage, so I tried flashing the stock ROM to see if that could fix it. Now I'm stuck in fastboot mode with no way to get out.
I already tried several volume + power buttons combinations with no avail, tried to use fastboot reboot, fastboot reboot fastboot, but I'm still stuck in fastboot mode, also when trying to navigate through the fastboot menu with the volume keys, it seems like the volume up key is stuck and cycles through the options endlessly so I can't choose to power it off (I'm pretty sure that button wasn't stuck before, so it might have been something that came up with the faulty stock ROM flash).
Does anyone know what I can try? Thank you.
EDIT: It seems like I can power it off while not connected to the PC. But as soon as I plug it it goes to fastboot mode.