I have the weird problem, that my device seems to have no device name anymore, which causes that when I am trying to install a rom it tells me:
"This package is for device: D5803, D5833, z3c, aries; this device is ."
What I tried to fix it:
Trying several twrp kernels (different versions), did not change anything except that on some versions it said that my device is called "" (as device name only two question marks were shown instead of nothing)
Flashing again the kernel I used before and trying to install the old rom, which caused the same error message
Trying many other kernels, including the 3 latest versions of nailyk, the latest kernel directly from twrp, the kernel included in omnirom zip
I tried to flash again the default sony rom via Emma. Flashing of the default worked and I was able to use it, but as soon as I flashed again a twrp rom my device did put out the error message when I tried to install a rom.
What did I do before that happened:
I tried to flash carbonrom (https://get.carbonrom.org/device-z3c.html) onto the device, the version which was released on the 10th April (seems to have been deleted), the recovery menu did not pop up it just restarted several times (I should mention here, that I was never able to boot into the recovery via keys or adb (just the normal system did boot up when I used the command). I only were able to enter the recovery on other kernel images, when no system was installed and the recovery just popped up). So I tried to flash the recovery of the version which was released on the 5th of April, it did change nothing.
Then I tried installing omnirom (https://forum.xda-developers.com/z3-compact/orig-development/oreo-unofficial-omnirom-t3696536) using the kernel from "https://releases.nailyk.fr/twrp/". I finally was able to boot into the recovery and to install omnirom. It worked perfectly, but I forgot to install the gapps, so I reflashed the kernel (because of the boot into recovery problems I mentioned before, to get back into the recovery). When I tried to install the gapps nano, after I reinstalled omnirom it said, that my architecture was not supported (I downloaded the right one (arm 32bit)). Then I tried to install gapps stock. Same error. I read online that it was a bug of newer twrp, which caused that problems on some systems. So I tried a few versions of nailyks kernel and the version 2017-11-21 installed my gapps and I was able to flash them. At that point I tried to flash carbonrom via nailyks kernel (I was able to install the 5th April version. The 10th April version had an endless installation (actually I think the real installation never did start)) and then using the included kernel from the zip to boot. And it did not boot. So I flashed again nailyks kernel. I think after that the problem happened (I am not absolutely sure if I tried something else before that happened (I am forgetting many things)).
Also I shut mention that I wiped Dalvik / ART Cache, System, Cache, Data Internal Storage two times instead of just Dalvik / ART Cache
About carbonrom, that build was faulty. It's been fixed with the newer one.
Which keys do you press to boot into recovery?
marcogiannetta said:
About carbonrom, that build was faulty. It's been fixed with the newer one.
Which keys do you press to boot into recovery?
Click to expand...
Click to collapse
I tried the volume up as well as the volume down button several times as soon as the notification light turned purple. I even tested the camera button. It never booted into recovery mode. And also when I tried entering the recovery via adb I had no luck. It just rebooted.
00pflaume said:
I tried the volume up as well as the volume down button several times as soon as the notification light turned purple. I even tested the camera button. It never booted into recovery mode. And also when I tried entering the recovery via adb I had no luck. It just rebooted.
Click to expand...
Click to collapse
Try to completely shutdown your phone (press power + volume up until it vibrates three to four times), press power + volume down until it vibrates, then release power button. TWRP screen should appear.
That's the way I've been entering TWRP since I unlocked my boootloader.
marcogiannetta said:
Try to completely shutdown your phone (press power + volume up until it vibrates three to four times), press power + volume down until it vibrates, then release power button. TWRP screen should appear.
That's the way I've been entering TWRP since I unlocked my boootloader.
Click to expand...
Click to collapse
Also with that tip I am unable to boot into recovery. I noticed that the notification light turns from purple to orange, before it restarts (it might just be restarting because no os is installed right now)
00pflaume said:
Also with that tip I am unable to boot into recovery. I noticed that the notification light turns from purple to orange, before it restarts (it might just be restarting because no os is installed right now)
Click to expand...
Click to collapse
That's really weird. How do you flash recovery?
There are two ways:
-fastboot flash recovery recovery.img
-fastboot flash fotakernel recovery.img
I don't remember the one I used, but you could try both.
Related
I installed CM 13 on my Droid Turbo after unlocking the bootloader with Sunshine. Everything was going fine until I tried to flash the Open Google Apps zip and I got into a loop with some of the Gapps crashing and I couldn't do anything. I researched this online and they (can't find where now) said to use TWRP to reset the device. So I went into "wipe" on TWRP and under "advanced wipe" I chose "System", "dalvik / art" and "cache" and rebooted the system. Now I've been stuck on the "WARNING BOOTLOADER UNLOCKED" screen for over an hour.
The other thing I have going against me is the power button does not work in anyway whatsoever (before and after I unlocked the bootloader).
Does anyone have any ideas?
You wiped the system partition, which means you erased your phone's operating system. This is why your phone is having trouble booting said operating system. Re-flash CM13 followed by your gapps (flash them sequentially. Don't boot the phone until both are flashed) and you should be fine.
I just went through this. Here's what worked for me, I'm on mobile and your milage may vary, you'll probably want to double check my work.
Get
Minimal adb and fast boot
Motorola turbo USB drivers
Twrp, cm13 20160517 if using nightly, gapps Pico, and in my case SuperSU
Hold power till off
Power up while holding power down
Google for the proper commands to accomplish the following
Fast boot twrp in place for recovery
Edit, boot into twrp.
Adb push cm13 zip
Adb push gapps Pico zip
Adb push SuperSU zip if needed
Edit,reboot back into recovery
Flash cm13, gapps Pico, SuperSU in that order
Reboot, wait for cm13 to load as long as it takes.
Edit, boot into twrp before adb push.
orangestrontium said:
I installed CM 13 on my Droid Turbo after unlocking the bootloader with Sunshine. Everything was going fine until I tried to flash the Open Google Apps zip and I got into a loop with some of the Gapps crashing and I couldn't do anything. I researched this online and they (can't find where now) said to use TWRP to reset the device. So I went into "wipe" on TWRP and under "advanced wipe" I chose "System", "dalvik / art" and "cache" and rebooted the system. Now I've been stuck on the "WARNING BOOTLOADER UNLOCKED" screen for over an hour.
The other thing I have going against me is the power button does not work in anyway whatsoever (before and after I unlocked the bootloader).
Does anyone have any ideas?
Click to expand...
Click to collapse
Since you have no power button this becomes tricky. You can try using adb but don't know if it will work as your phone sits. The only thing I can think of is let your phone die completely once it is off totally plug it in to charge while holding the down vol. Button this will bring you to bootloader where you can use adb commands to start recovery and go into twrp where you can reflash the system and gapps
Grynch13 said:
Since you have no power button this becomes tricky. You can try using adb but don't know if it will work as your phone sits. The only thing I can think of is let your phone die completely once it is off totally plug it in to charge while holding the down vol. Button this will bring you to bootloader where you can use adb commands to start recovery and go into twrp where you can reflash the system and gapps
Click to expand...
Click to collapse
This worked seamlessly, thanks!
I was in the same situation, and your advice got me to drain the battery and get back into recovery mode, so thanks for that! But, when I connected the USB cable, and tried ADB commands, it doesn't recognize my device (it has always recognized it in the past). Any advice? Thanks so much!
Hello,
I am trying to install a newer TWRP (https://forum.xda-developers.com/showthread.php?t=3557606) for Carbon Mod custom rom. I tried:
- install .img with TWRP in TWRP
- flashify
- official app TWRP from google play
- fastboot commands with "platform-tools"
Everywhere I get a message that everything went fine but in TWRP I still have the old version - 3.0.0.2 :/
I am asking for help because I have been fighting this from two days :/
I have unlocked bootloader, stock prerooted firmware .291 + EliteKernel v3.
Does it matter if I have dualrecovery?
I've got the same issue. I have also got dualrecovery. Did you have any luck? How do you access the dual recovery?
Dual Recovery
haverlok said:
I've got the same issue. I have also got dualrecovery. Did you have any luck? How do you access the dual recovery?
Click to expand...
Click to collapse
If in "dual recovery" you mean two versions of TWRP; I have two versions of TWRP on my Z3C.
My older version 3.1.1-0 is accessed by simply pressing the power button the same as turning on the phone. Release when the phone vibrates. When the green light appears in the top-left corner, I press and hold the down-volume until the light turns pink. It then boots to that TWRP recovery.
If I instead: while "pressing and holding down" the down-volume; then press and hold the power button. When the phone vibrates, I release the power button; then the Sony logo appears, release the volume-down. The phone then boots to the other recovery, which in my case is TWRP 3.2.3-0
.
Hi.
Im having alot of trouble doing custom stuff with my mi 9. At this point i have succesfully flashed aospextended on my mi 9 but i cannot enter twrp. It just "recovery loops" with the mi logo. I have tried flashing it again, just booting to twrp from fastboot but it still won't boot to twrp. I am consistently having issues booting to twrp at a point where i had to flash global stable from fastboot because it never stopped booting to stock recovery, where after i formattet cache and userdata. Thanks in advance.
Deleted
Hi!
Try telling us what you have done so far (in terms of modifications as well). Which recovery did you (try) flashing?
I personally tried skiantibag & maufirinio (I know it's not the proper spelling but you'll find it) + flashing RevolutionOS.
You've probably heard it already: Fastboot -> flash recovery -> does it boot into (after shutting down -> volume up + standby pressed)
If not try (first flashing the recovery) then booting from the .img file via fastboot.
After that wipe everything and flash Revolution OS/xiaomi.eu. Do you still experience the problems then? Short hint at the end: setup a password (code - during the android setup process) since your storage gets encrypted (no matter what - at least for me).
Good night, good luck!
ollioddi said:
Hi.
Im having alot of trouble doing custom stuff with my mi 9. At this point i have succesfully flashed aospextended on my mi 9 but i cannot enter twrp. It just "recovery loops" with the mi logo. I have tried flashing it again, just booting to twrp from fastboot but it still won't boot to twrp. I am consistently having issues booting to twrp at a point where i had to flash global stable from fastboot because it never stopped booting to stock recovery, where after i formattet cache and userdata. Thanks in advance.
Click to expand...
Click to collapse
after flashing twrp, (assuming ur using fastboot cmds to boot to twrp) use buttons to reboot to twrp. Long press power button and volume up together until device reboots, once it vibrates, let go of power but keep holding vol up until twrp boots. Then disconnect phone from pc. Twrp should now stick. Which twrp you using?
reg66 said:
after flashing twrp, (assuming ur using fastboot cmds to boot to twrp) use buttons to reboot to twrp. Long press power button and volume up together until device reboots, once it vibrates, let go of power but keep holding vol up until twrp boots. Then disconnect phone from pc. Twrp should now stick. Which twrp you using?
Click to expand...
Click to collapse
This. Rebooting from command line did not work for me either. Just press power + vol up until screen closes and keep pressing 3 more seconds after mi logo appears.
Moin,
My phone was one day suddenly unable to boot into system nor Recovery, but could still enter fastboot.
Took me a while to figure out that USB Hubs let flash attempts fail too. (you can watch the drama in my older posts)
Now i was able to flash System back into a workable state and it looks like that recovery is also successful flashed.
BUT...i can enter recovery only ONCE per Vol - and Power on Button.
i have NO OTHER WAY to enter Recovery at all. i have no reboot option in system (LOS 18.1).
In fastboot/adb command and after one succsesfull reboot per keys, it always stuck after the Sony logo into a black screen. i then have to restart it into system with Vol+ and Power (one vibration) or shut down with vol+ and power for 6 seconds (three vibration) to get it either into fastboot (Vol+ and USB connect) or system again. then i have to flash it again to get into TWRP once. i tryed the latest twrp version (3.7.0) and one older version (3.3.1) that had once worked until the phone broke.
Any idea what is going wrong here. i have already try to completly wipe everything from the phone and try to fix SEL Linux in twrp. nothing seems to work. Did i miss something?
/€: Now it is again in the full broken state. recovery nor System won't boot anymore and end in a black screen.
/€²: Found the Problem: my lilca zip was polluted with altered files i forgot about.
Hello,
I have flashed twrp over Odin and it works well, flashed custom room too, everything was super fine but after i restart the phone
Got stuck in twrp logo
Can't go to download mode or boot to system either.
Tried to hard restart power + vol - then after restart press power vol - bixby but same issue.
Download mode won't launch neither recovery.
Picture of the problem in the attachment
Please any solution?
first you flashed the wrong version of twrp according to your attachment, in my opinion you have to reflash everything and you can follow this tutorial and I hope it helps you
diznote4 said:
first you flashed the wrong version of twrp according to your attachment, in my opinion you have to reflash everything and you can follow this tutorial and I hope it helps you
Click to expand...
Click to collapse
Sorry but i don't think it'll boot first time or even i could flash custom rom from it if the recovery wasn't compatible.
After the twrp everything was fine, and i got access to twrp recovery and flash custom room without any problems.
First bot was fine, but after 2 consecutive restarts
This issue occurred .
And can't make it to download mode now, so I can't flash stock or anything.
I mean the correct version to flash android 13 it is twrp v 3 7 0 9 0 if not the phone hangs at twrp logo.
now to put back on download mode you have to do this manipulation
1/ connect your phone to your pc with the USB cable then press bixbi and power (between 5 and 7 seconds) and when the phone goes black at this moment don't let go of bixbi and power you have to press the volume button -
I hope it will go.