Hi,
I'm new to the custom-ROM topic and to xda-developers (it's my first post ). I'm a developer but have never developped something for mobile devices (only desktop,server,web).
== short version ==
I can boot my phone to system from bootloader but it boots to recovery by default. How can I let it boot to system by default?
== long version ==
I bought two Moto Z devices. (XT1650-03 64GB / update-chanel:retapac) and updated both devices to newest available version (7.1.1 / December 2017) -- no 8.0, I do not know why.
Then I installed LineageOS on the first device with this guide: https://wiki.lineageos.org/devices/griffin/install
Used packages:
twrp-3.2.3-0-griffin.img
lineage-15.1-20180820-nightly-griffin-signed.zip
open_gapps-arm64-8.1-mini-20180826.zip
So far so good, the first device is working just fine.
Then I installed LineageOS on the second device exactly (so I hope) the same way. But the second device is booting by default to recovery mode instead of sytem mode. When I reboot from recovery mode to bootloader or when I boot into bootloader directly (volDown+pwrOn) then I can select "Start" and the device boots to System. When the System is booted all seams OK, but on restart (or on pwrOn after shutdown) it boots to recovery mode and I have to go to bootloader and boot to System from there again.
I found some hints how to solve the problem: https://forum.xda-developers.com/showthread.php?t=2774709&page=8
I tried
Code:
fastboot oem fb_mode_clear
but it did not change anything.
I did not try the commands like
Code:
dd if=... of=...
, because I think, that they are device specific and I didn't find one specific to Moto Z.
I tried to reinstall twrp,lineageos,open_gapps but it also didn't fix the issue.
Any ideas?
Thanks!
motovit said:
I did not try the commands like
Code:
dd if=... of=...
, because I think, that they are device specific and I didn't find one specific to Moto Z.
Click to expand...
Click to collapse
Do not think! Just try it!
In recovery mode I mounted system and started a terminal on the device. There is only one directory in /dev/block/platform/soc it is: 624000.ufshc.
On the first device /dev/block/platform/soc/624000.ufshc/by-name/misc was empty and on the second device, there was something with "wipe" and "recovery".
Thus this command fixed the problem:
Code:
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc
I'm curios what the reason for the issue was, but unfortunately I forgot to note the content really stupid!
Related
After upgrading to CM 12.1 everything was just fine. Got my tablet to charger and left it there for a while. And then i saw that i was looping.
It's trying to enter recovery (TWRM) "or something like" and restarting.
I' sitting on forum for 3 days already. trying to get some information and did lot's of things. Nothing helps.
Can anyone help me with this somehow? I'm almost crying and losing it (not really, but that what i feel inside)
Please. Any help. I think I've read all forum about this thing.
Thank you.
Do you have the real TWRP (i.e. not Safestrap!) & an unlocked bootloader?
don't think so. or better say i'm not sure about it. how can i check?
Edit:
i can run adb and after command "adb devices" it shows serial number and status: recovery.
i can use the command adb reboot-bootloader which puts me in fastboot mode. but then i try adb devices and have nothing there.
also, any command like "fastboot...." gets me to "waiting for device" and nothing more.
I tried two different computers. all ports. all cables that i've found.
Edit 2:
also after command "adb shell" i ca see "~ # ←[6n" and i can put there only reboot command
Well, first of all CM12.1 requires TWRP & an unlocked bootloader, if you don't have those, flashing CM12.1 was a bad idea.
So what happens during boot? Do you see the Safestrap logo and had to either wait 10 seconds or press continue to boot? Can you enter Safestrap there by pressing Recovery? Which Safestrap version is it (if any)?
The real TWRP can be accessed by pressing and holding Volume up, then pressing and holding Power, release both when the grey Kindle Fire logo appears on screen.
As having TWRP is a key requirement here, it's important to figure out what you really have (either Safestrap or TWRP).
And do NOT do a factory reset in amazon's stock recovery with Safestrap installed! Will brick the HDX!
As @Davey126 mentioned here you can check whether the bootloader ist unlocked by opening a fastboot prompt (i.e. DOS box, then change dir to your adb directory), then enter:
fastboot -i 0x1949 oem idme
You will only get a response if unlocked.
If you use Windows and get the waiting for device fastboot issue, try these drivers, could be a pain in the ass to install them in Win8(.1)/Win10 x64 though. And note that you probably need to (re-)install the original Amazon Drivers again to get the HDX noticed in Explorer in order to get files copied it.
Cl4ncy said:
Well, first of all CM12.1 requires TWRP & an unlocked bootloader, if you don't have those, flashing CM12.1 was a bad idea.
So what happens during boot? Do you see the Safestrap logo and had to either wait 10 seconds or press continue to boot? Can you enter Safestrap there by pressing Recovery? Which Safestrap version is it (if any)?
The real TWRP can be accessed by pressing and holding Volume up, then pressing and holding Power, release both when the grey Kindle Fire logo appears on screen.
As having TWRP is a key requirement here, it's important to figure out what you really have (either Safestrap or TWRP).
And do NOT do a factory reset in amazon's stock recovery with Safestrap installed! Will brick the HDX!
As @Davey126 mentioned here you can check whether the bootloader ist unlocked by opening a fastboot prompt (i.e. DOS box, then change dir to your adb directory), then enter:
fastboot -i 0x1949 oem idme
You will only get a response if unlocked.
If you use Windows and get the waiting for device fastboot issue, try these drivers, could be a pain in the ass to install them in Win8(.1)/Win10 x64 though. And note that you probably need to (re-)install the original Amazon Drivers again to get the HDX noticed in Explorer in order to get files copied it.
Click to expand...
Click to collapse
Also verify you have a Kindle HDX ... not HD or generic Fire.
the fastboot command got me still only 1 message "waiting for device"
Tried to install drivers. While looping, in device manager, i can see "Fire devices: Android composite ADB Interface"
and "Portable devices: MTP USB Device"
If i enter fastboot mode, gets me to "Other devices: Unknown device" and i just cant figure out how to install the drivers. Tried to download some stuff. plugged, unplugged.
Edit:
After some work done with drivers, i input adb kill-server and adb devices and get "Serial Number Unauthorized"
So maybe i should change word "work" to "messing" with driver
what do i do from here... is there any live chat for it maybe? or i can call someone?
Well, do you have the real TWRP or Safestrap? Can you enter recovery?
well, only thing i get it's blue screen and "Teamwin" and after like 3-4 second restarts and go on looping same "Teamwin"
oreal crast said:
well, only thing i get it's blue screen and "Teamwin" and after like 3-4 second restarts and go on looping same "Teamwin"
Click to expand...
Click to collapse
Still haven't answered Safestrap or native TWRP query (you should know). Do this:
- long press power until device shuts off
- restart device with power button (only)
- detail the 1st, 2nd and 3rd screens you see
If you do not have native TWRP (with unlocked bootloader) you likely borked your device with the installation of CM 12.1. Generally not repairable.
oreal crast said:
well, only thing i get it's blue screen and "Teamwin" and after like 3-4 second restarts and go on looping same "Teamwin"
Click to expand...
Click to collapse
Ok, that should be the real TWRP, the Safestrap screen looks different.
This could mean you've TWRP installed, but the bootloader is locked. So I'd suggest to unlock the bootloader, you can't screw up anything, and can try this nice tool.
Cl4ncy said:
Ok, that should be the real TWRP, the Safestrap screen looks different.
This could mean you've TWRP installed, but the bootloader is locked. So I'd suggest to unlock the bootloader, you can't screw up anything, and can try this nice tool.
Click to expand...
Click to collapse
To check if your bootloader is unlocked (assumes you previously unlocked and still have the prerequisite software installed on host):
- power down device
- press vol-down + power; release both keys when "[fastboot]" prompt appears
- tether your device
- open a command prompt (assuming Windows)
- issue command: fastboot -i 0x1949 oem idme ?
- you will only get a response if bootloader is unlocked
If the (Windows) host displays "<waiting for device>":
- press <ctrl>-c to break wait
- start device manager (different window)
- located device with explanation mark (likely under "portable devices")
- right click -> update driver software -> browse my computer... -> Let me pick...
- select driver from list (ideally one that contains the words 'fastboot'); might have to try a few
- reissue above command
Bit of a PiTA ... might be easier to simply try the one click unlock tool as there is no additional risk to your device. It will either work or not.
I guess i'll check it only next week. Leaving all this things for the weekend.
I'll keep you updated guys.
Anyway, i really appreciate your help! Thank you so much for helping
same problem
Good evening, I am very interested by the article, in fact, I currently have the same problem and I began to be very sad. all stages cited by oreal Crast are similar to the ones I tested. when I enter the command prompt 'adb devices' I get the number of my tablet and status RECOVERY.
'adb shell' gives me "~ # ← [6n"
I even re installs the uboot, boot.img and TWRP freedom by following the steps in one tech site
but at reboot, by entering the command "fastboot oem recovery 0x1949 -i 'my tablet again has a boot loop on teamwin.
i want to resolve very fast this problem because i need my tablet urgently:crying:
ps: I don't think that I can meet these problems because after having bought my tablet to a friend (the tablet possessed CyanogenMod 11 android 5.0.1 I think) I did a factory reset . it is from this manipulation on my tablet reboot teamwin.
thank you for your helping
stephio said:
Good evening, I am very interested by the article, in fact, I currently have the same problem and I began to be very sad. all stages cited by oreal Crast are similar to the ones I tested. when I enter the command prompt 'adb devices' I get the number of my tablet and status RECOVERY.
'adb shell' gives me "~ # ← [6n"
I even re installs the uboot, boot.img and TWRP freedom by following the steps in one tech site
but at reboot, by entering the command "fastboot oem recovery 0x1949 -i 'my tablet again has a boot loop on teamwin.
i want to resolve very fast this problem because i need my tablet urgently:crying:
ps: I don't think that I can meet these problems because after having bought my tablet to a friend (the tablet possessed CyanogenMod 11 android 5.0.1 I think) I did a factory reset . it is from this manipulation on my tablet reboot teamwin.
thank you for your helping
Click to expand...
Click to collapse
I assume you have an unlocked bootloader and were running 'native' twrp (not Safestrap) when the problem occured. Unfortunately, there is no known 'quick fix' recovery from this failure scenario (boot looping on teamwin spash screen) as you have tried to reinstall twrp without success. Someone very talented with android might be able to unravel the problem. Best guess (and it is only a guess) is the recovery partition became damaged to such an extent it the contents can not be replaced without performing a low level format/reset of your device.
Some curiosities:
- Android 5.0.1 and CM11? (impossible combination)
- TWRP freedom? (not supported on HDX)
Are your certain your device is a HDX and not some other model?
same problem
for android version I listed above, I do not know exactly because I have used my tablet a day without really paying attention to it but I think I saw the android 5.0.1 but regarding cyanogen, I just imagined it based on readings on the web.
for this is my tablet AMAZON KINDLE FIRE with a HD 8.9 and the TWRP I recently flashed, I got through the website wikicyanogenmod in the "on how to install cyanogen hd amazon kindle 8.9.
I can not post a link because I am new to the forum so I can only quote the sites where I could download my data.
* I really count on your help to all.
stephio said:
for android version I listed above, I do not know exactly because I have used my tablet a day without really paying attention to it but I think I saw the android 5.0.1 but regarding cyanogen, I just imagined it based on readings on the web.
for this is my tablet AMAZON KINDLE FIRE with a HD 8.9 and the TWRP I recently flashed, I got through the website wikicyanogenmod in the "on how to install cyanogen hd amazon kindle 8.9.
I can not post a link because I am new to the forum so I can only quote the sites where I could download my data.
* I really count on your help to all.
Click to expand...
Click to collapse
You still haven't made it clear whether you have an HD or HDX model.
You're on the HDX forum, but you're talking about documentation on the CyanogenMod wiki for the HD 8.9.
The problem likely stems from the fact that you flashed a recovery for the wrong device.
same problem
EncryptedCurse said:
You still haven't made it clear whether you have an HD or HDX model.
You're on the HDX forum, but you're talking about documentation on the CyanogenMod wiki for the HD 8.9.
The problem likely stems from the fact that you flashed a recovery for the wrong device.
Click to expand...
Click to collapse
I searched the web and I have definitely amazon kindle fire HD 8.9 because even his appearance differs from the HDX 8.9.
no I do not really think the problem comes from the data flash HD 8.9 (wikicyanogenmod) because I flashed the data after doing a factory reset without actually knowing that this would pose a problem with amazon tablets.
the tablet was working well but I was unable to connect to the wifi. I thought it would be nice to change rom and install a suitable and stable rom for my tablet, but my operation I was surprised because I had never heard of this kind of problems caused by an factory reset
Dear everyone,
I have an ASUS MeMoPad 10 (ME103K) here which I vowed to fix. The user wanted to revert to Factory Defaults, lost power or something like this, and ended up with a bricked device.
I can only start it with power button + volume up, into Fastboot. Secure Boot is enabled.
I have Android SDK and minimal FastBoot installed. Have the Google USB Drivers on my desktop.
I tried flashing SuperBoot (ADB), but ADB simply lists "Waiting for Device". No devices can be listed. It does show up in Windows Device Manager: ASUS Android Bootloader Interface.
I have the following files available:
- SuperBoot r5
- Kernel: l-8064-r1_V12.16.1.12-201508071139-foss.tar
- UL-K01E-WW-12.16.1.12-user
- recovery-original-me103k
There is apparently no recovery.img for this device. The boot.img is in the UL-K01E-WW-12.16.1.12-user file
Power = ASUS logo then goes black
Power + Volume up = Fastboot
Power + Volume down = /
Power + Volume up+down = /
Is this the place I should be looking? I'm honestly not sure if I can catch up with the details: android.stackexchange.com/questions/124344/trying-to-flash-a-system-img-i-took-with-dd-failing
Any help would be much appreciated!
- Al
EDIT:
fastboot devices now detects #serialnumber
Alright, fastboot now detects my device. I installed PDANet which didn't do anything, and then downloaded another adbfastboot package which hit it.
I'm able to start writing boot.img, but that's what it stays at. It's an 8MB file, so it shouldn't take half an hour, I suppose?
I'm not getting any error message either, though.
EDIT: It seems that regardless of what commands I send, they stall and don't get executed. ADB doesn't seem to find any devices, only Fastboot does.
EDIT 2: Tried the same on my laptop. Different ports. Nothing goes further than for example "Writing 'boot' - that's it.
Bump (won't bump until tomorrow late)
B0mp
kab0mp
boink
Bwamp
Recover Asus Me103k (k01e)
1) Stock recovery:
View attachment k01e_stock_recovery.zip
3) Run it without flash:
Code:
fastboot boot k01e_stock_recovery.img
3) In recovery select to install UL-K01E-WW-12.16.1.12-user.zip (early placed on microsd)
4) Also can check boot ability:
Extract boot.img from update firmware zip UL-K01E-WW-12.16.1.12-user
And run it from fastboot:
Code:
fastboot boot boot.img
If Android loaded normaly after it, but after reboot you see FASTBOOT MODE, than execute this commands:
Code:
fastboot oem reset-dev_info
fastboot reboot
Asus MeMo pad ME103K/K01E bootloader unlock
sheinbo said:
Hi,
after all these years I remembered my asus memo... Such a fine displsay but ... . I discovered an unofficial rom for another old device ( samsung gt 5830) and so I'd like to ask you whether you know any possibility to "upgrade" the MeMo or any other way to pitch / patch it. Your reply here let me think that you are very attached to asus memo, maybe you are still interested.
Click to expand...
Click to collapse
Same here, running the device on Lollipop is awfully slow, KitKat is somewhat better though but those are the only two official ROM's which can be found and installed.
Tried to unlock the bootloader to try different ROM's but bootloader is locked, despite all info here on XDA, nothing seems to work and the bootloader remains locked. Unlock APK's also give no result.
Running out of options here, any suggestions will be appreciated.
Hello,
I'm stuck into a similar situation reported here [Q] Volume down not working, how to get into recovery? on my LG G5 H850.
I had MM installed and finally wanted to upgrade to N having heared the good news concerning Xposed's availability.
So I've patched the bootloader and then a 20k Complete Stock ROM through TWRP still installed and fully working at this moment.
Boot back to N. OK
Once the upgrade process have finished I had the surprise to discover that I have all my previous apps and settings where still present but I have dozens of FCs polluting the screen !!
e.g. I cannot access com.android.settings
The phone is almost unusable :crying:
Before the upgrade I made some wipes (cache, system I guess and if I look back into my memory) but I don't remember having made a factory reset ... my bad
I don't have root anymore :good:
I made
Code:
adb reboot bootloader
fastboot flash recovery twrp-3.1.x.x.x.img
but cannot "stick" it coz of my volDown button HS
Code:
adb reboot recovery
finishes to a "No command" screen (maybe because of an un"stick"ed twrp)
Code:
adb reboot bootloader
fastboot boot twrp-3.1.x.x.x.img
but got a "FAILED (remote: unknown command)" response
I still have the Official TWRP app manager installer but cannot install a new one (because of the "su" lack)
Questions :
Is there a way to reinstall "su" binaries in these conditions and without TWRP ?
Is there a way to "live" boot into a recovery ?
What can I do with "fastboot boot <something>" ?
Pleease someone ... one good news :fingers-crossed:
Never had a problem running @phhusson GSI when running Android 8.0 bootloader. After I upgraded to Huawei 9.0, I can no longer load a system image, using the guide, it just bootloops every time.
Followed the official instructions from here:
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
Perform a factory reset on your device.
Reboot to your device’s stock recovery using either a button combination when booting or issuing the following ADB command when booted in Android: adb reboot recovery. Once here, use the volume keys to navigate and the power button to select the factory reset option.
Once your device has been factory reset, reboot to your device’s bootloader using either a button combination when booting or issuing the following ADB command when booted in Android: adb reboot bootloader
With your device connected to your PC, open up a command prompt or terminal window in the same directory where you downloaded your GSI of choice.
Enter the following command: fastboot erase system
Enter a command in the following format: fastboot -u flash system name_of_system.img (NOTE: -u is an invalid option, I think it supposed to be --unbuffered)
Allow the image to flash, it could take a few minutes. Once it has completed, reboot your device either manually via power key or by entering fastboot reboot.
I also tried the comment in the troubleshooting section:
As a last resort, you can try a full format of the data partition (WARNING: THIS WIPES EVERYTHING) by entering fastboot -w from a command prompt/terminal window while in the bootloader. I have had to do this on my Huawei device before it could work.
Nobody?
It seems Huawei have got Android 8 GSI certification, and then flipped a switch to stop it working post release, which is rather naughty.
I guess nobody cares that Huawei took this away from you.
Well, same problem here, but Openkirin ROMS still work as they use their "unopen-sourced" magic to make their ROMS run on EMUI 9 devices and Tablets.
as mentioned here https://forum.xda-developers.com/showpost.php?p=79811581&postcount=45 and here https://forum.xda-developers.com/showpost.php?p=79987022&postcount=48 there are some GSI Builds which boots on mediapad M5 SHT-AL09 with vendor 9.
I didn't test every GSI build, phhusson got me only to erecovery, and i wanted a build with gapps, so these two i can confirm to work.
I don't really trust openkirin. We don't know who they are (Internet forum accounts don't count) , and it's closed source. It could contain literally anything.
I will stick with stock I think.
Chr1stOnABike said:
I don't really trust openkirin. We don't know who they are (Internet forum accounts don't count) , and it's closed source. It could contain literally anything.
I will stick with stock I think.
Click to expand...
Click to collapse
Yes, me either
Hey community,
I have been running Poco F1 with twrp and PixelExperience for the last 2 years. Considering the past record of the OS and my experience with the OS, I decided recently to upgrade to the newer PE12 for Poco F1 (maintained by Lakshay Garg). It went smooth initially and after the last OTA update, the phone started behaving weirdly.
Long story short,
This morning the phone went into an automatic restart and is now stuck in a boot loop. It boots and reaches the "G" logo and reboots. However, the weird part is,
Code:
fastboot flash
and
Code:
fastboot boot
are not available, throwing errors. The device is visible in
Code:
adb devices
and
Code:
fastboot devices
. This problem occurs when the phone is not plugged in. Once plugged in, the phone runs fine and everything just works. TWRP is not accessible, as if it is not there anymore and the only recovery that I can reach is the pixel recovery which has no option to flash any custom recovery (newbie, so not sure if something like this should exists or not).
I've tried various threads here and wasn't able to find any solution. Let me know what commands/outputs you guys might need from the device to help me in this.
Thanks in advance. Hope this gets fixed soon.
tysonX5653 said:
Hey community,
I have been running Poco F1 with twrp and PixelExperience for the last 2 years. Considering the past record of the OS and my experience with the OS, I decided recently to upgrade to the newer PE12 for Poco F1 (maintained by Lakshay Garg). It went smooth initially and after the last OTA update, the phone started behaving weirdly.
Long story short,
This morning the phone went into an automatic restart and is now stuck in a boot loop. It boots and reaches the "G" logo and reboots. However, the weird part is,
Code:
fastboot flash
and
Code:
fastboot boot
are not available, throwing errors. The device is visible in
Code:
adb devices
and
Code:
fastboot devices
. This problem occurs when the phone is not plugged in. Once plugged in, the phone runs fine and everything just works. TWRP is not accessible, as if it is not there anymore and the only recovery that I can reach is the pixel recovery which has no option to flash any custom recovery (newbie, so not sure if something like this should exists or not).
I've tried various threads here and wasn't able to find any solution. Let me know what commands/outputs you guys might need from the device to help me in this.
Thanks in advance. Hope this gets fixed soon.
Click to expand...
Click to collapse
Seems to be a battery problem. How old is it? You may need to replace it.
However make sure you followed the clean install method before you come on a conclusion. Also try to not use any Magisk modules.
Best Clean Install method:
Backup all your data. All your data into Internal Storage will be lost during this process.
Download latest Official TWRP Recovery, Pixel Experience build.
Create one Folder and move all the files you downloaded there.
Reboot to Fastboot Mode
Connect your device to PC and Boot into to TWRP via ADB or Minimal ADB and Fastboot:
Code:
fastboot boot <recovery_filename>.img
Example:
Code:
fastboot boot C:\Users\Retrial\Desktop\twrp-3.6.1_9-0-beryllium.img
Select Wipe > Advanced Wipe -> Select Dalvik / ART Cache, System, Data, Internal Storage, Vendor, Cache and then Swipe to Wipe.
Go back and select Wipe > Format Data > type yes
While you are in TWRP, transfer the Folder with the files you downloaded above.
Flash Pixel Experience ROM.
Flashing the ROM will replace TWRP with PE Recovery so OTA updates can be installed without problems since TWRP currently doesn't support decryption on A12 encypted ROMs - If you need in future to change ROM just fastboot boot to twrp via adb and flash img of twrp to recovery partition.
Done! Reboot to system.
Thanks, turns out that it was a battery problem after all. After battery replacement everything is working just fine. I also installed Awaken OS as Pixel Experience was removing the TWRP recovery each time I flashed it. Now as for my fastboot, initially it was not working; it was showing this error whenever I tried to flash TWRP recovery or any stock recovery:
Sending 'boot.img' (38640 KB) FAILED (Write to device failed (Cannot send after transport endpoint shutdown)) fastboot: error: Command failed
After this, the fastboot mode was diconnected and my phone was showing this Error:
Press any Key to Shut Down
It was resolved by running this bat file (as admin) :
https://bit.ly/31T2LcB
After running this file, there was no error and I was able to flash the twrp Recovery smoothly. So thanks for all the help really appreciate it.
tysonX5653 said:
Thanks, turns out that it was a battery problem after all. After battery replacement everything is working just fine. I also installed Awaken OS as Pixel Experience was removing the TWRP recovery each time I flashed it. Now as for my fastboot, initially it was not working; it was showing this error whenever I tried to flash TWRP recovery or any stock recovery:
Sending 'boot.img' (38640 KB) FAILED (Write to device failed (Cannot send after transport endpoint shutdown)) fastboot: error: Command failed
After this, the fastboot mode was diconnected and my phone was showing this Error:
Press any Key to Shut Down
It was resolved by running this bat file (as admin) :
https://bit.ly/31T2LcB
After running this file, there was no error and I was able to flash the twrp Recovery smoothly. So thanks for all the help really appreciate it.
Click to expand...
Click to collapse
Did you face the problem again?
I am using PE11 since last 2 years but suddenly i started facing the same problem. When plugged in, works fine. When I unplug it, works until screen is on and when I use power button to lock or unlock, phone goes into bootloop. I opend it in twrp where it can work as long as battery lasts, that's why I am not sure if it's a battery problem or something else