Related
Hi All. During a upgrading phase I don' know what appened but:
- The device start only in recovery mode
- I don't able to go in fastbbot mode, both pressing keys on startup of device or by fastbbot command line
- the command "fastboot devices" give me any device attached, or other fastboot cmmand < waiting for device>
- command adb devices give me:
C:\Temp\android-sdk-windows\tools>adb devices
List of devices attached
HT936NG00644 recovery
- I am able to push .zip on Dream (adb push ...) and install it by ALT+S on Dream
- On the Dream I reach this error:
- E:Can't read MISC: (No space left on device)
- E:Can't open /cache/recovery/command
- any other adb command by command line, give me the follow error:
C:\Temp\android-sdk-windows\tools>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
HELPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP, Its 4 days I didn't able to solve.
Can anyone help me ?
Thanks
Pippapeppa
pippapeppa said:
Hi All. During a upgrading phase I don' know what appened but:
- The device start only in recovery mode
- I don't able to go in fastbbot mode, both pressing keys on startup of device or by fastbbot command line
- the command "fastboot devices" give me any device attached, or other fastboot cmmand < waiting for device>
- command adb devices give me:
C:\Temp\android-sdk-windows\tools>adb devices
List of devices attached
HT936NG00644 recovery
- I am able to push .zip on Dream (adb push ...) and install it by ALT+S on Dream
- On the Dream I reach this error:
- E:Can't read MISC: (No space left on device)
- E:Can't open /cache/recovery/command
- any other adb command by command line, give me the follow error:
C:\Temp\android-sdk-windows\tools>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
HELPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP, Its 4 days I didn't able to solve.
Can anyone help me ?
Thanks
Pippapeppa
Click to expand...
Click to collapse
What buttons are you holding while you bootup?
Hi JAguirre1231,
Thanks for the response.
I Hold Back+Power or Camera+Power. In any way I boot the Dream always go in Recovery Mode.
Thanks again for Your Help.
Pippapeppa
Try to reflash radio and SPL but be careful. I can't give you warranty that you will not broke your phone completely. You have damaged data in ROM (radio & SPL) and I think that reflashing it should help you but also can damage it completly (but I think that it shouldn't happen). The risks increase fact - you must flash radio & spl from recovery but this method is strongly discouraged because of risks to broke phone (read topics about dangerSPL and why you shouldn't use recovery to flash it).
http://forum.xda-developers.com/showthread.php?t=831139
Hi Gerdal,
Whitch version of Radios and SPL have I to reflash.
Which procedure can I follow ?
Thanks again, there are to many information and I understand that if we can chach procedure, sequence and version we can total brick the phone.
Regards
Pippapeppa
Radio - http://forum.xda-developers.com/showthread.php?t=640535
SPL - in attachments
Flash RADIO, reboot, wait - phone will reboot automatically to recovery, flash SPL, reboot and again wait before phone automatically rebot to recovery. If everything goes correct you can reboot and try to boot in fastboot.
Hi Gerdal,
I just done the two updated without errors.
I didn't resolve The dream start only in recovery mode .
I am desperate
I don't understand this thing, if I run by PC with Dream connected by USB the command:
C:\Temp\android-sdk-windows\tools>adb devices
I obtain:
List of devices attached
HT936NG00644 recovery
The devices is visisible and accesible by PC,
If I run:
C:\Temp\android-sdk-windows\tools>fastboot devices
Nothing is the response, I presume that the tool fastboot don't see the Dream.
Any Hel is appriacied
Regards Pippapeppa
fastboot devices will see phone only if phone is running in fastboot mode. Are you sure you pressing camera+power when you powering on phone? Can you try to flash any ROM in recovery, reboot (do not press any buttons) and try to boot to android? Maybe camera button is broken?
Actually I'm trying to find possibility to flash entire ROM (everything what is in nbh file) through recovery. This should repair everything. Maybe someone know what to do this and will write how to do that?
Hi
Gerdal said:
fastboot devices will see phone only if phone is running in fastboot mode. Are you sure you pressing camera+power when you powering on phone? "Can you try to flash any ROM in recovery", reboot (do not press any buttons) and try to boot to android? Maybe camera button is broken?
Click to expand...
Click to collapse
I haven't find any botton to switch off the Dream, the only way is reboot (HOME+BACK or PHONE+POWER+MENU). So immediatly after I press HOME+bACK I press CAMERA+POWER. Should be that the mapping of the keys are not correct ?
How can perform "Can you try to flash any ROM in recovery", I understood that this operation should be only in fastmode. If I can do it and You can tell me how should be a good way.
Thanks again
Pippapeppa
Which recovery are you using? Have you flashed once a custom recovery for example AmonRa Recovery or ClockWork recovery? If you have one of them you can flash any zip that contains ROM for example cyanogenmod. If you flash this and reboot, the phone should boot into this system. If not we need to find answer why it don't do that.
You are pressing rights buttons when you try to boot in fastboot so I don't understand why it don't works...
Sorry Gerdal I am a beginner on this space.
I explane you the context because I am very frustrated.
The device is of my collegues and I am test it for potential purchase. I have attempted to upgrade it to appreciate al the functionalities and I have done the trouble !
So I don't know which recovery I am using I know that the Dream has been rooted.
If You can be kind to explain me the major step to execute and the reference to the persion of files I will be grateful ... forever.
Thanks again
Pippapeppa
Hi Gerdal,
I have flashed with ionr1-signed.zip, the ROM installed before the Hang.
I have attempt to install and run this (http://forum.xda-developers.com/showpost.php?p=9221440&postcount=39), but without result. seems the internal partition are all broke / unconfigured and any script on this partitation are unavailable.
Always the same behavior
Thanks for any help
Sorry but I can't help you. I don't understand why these ways don't work for you.
Hello every body and sorry for my poor English !
I have root my phone some month ago by changing my recovery with flashrec 1.0
all work done, I can be root on my phone by press "su".
But there is an update now and I want my old recovery partition.
So I use flashrec and type "restore backup" but it tell me failed !
I restart the phone and try it again : and in 0,01 second flashrec tell me success and when I restart my phone in recovery mode I have a block screen with triangle next to phone icon and I can't do nothing else than remove the battery !
So I try to do :
Code:
adb shell reboot bootloader
fastboot boot recovery-backup-htc-hero.img
But it answered : "FAILED (remote: not allow)"
I try :
Code:
adb shell flash_image recovery /sdcard/recovery-backup-htc-hero.img
But it answered : "mtd: read error at 0x00000000 (Out of memory)"
or nothing happens.
I have try :
Code:
fastboot erase recovery
But it answered : "FAILED (remote: not allow)"
Any idea for recover my recovery ?
Thanks or your answers.
i guess you are using unlocked SPL It might be causing problems
Greetings,
See the following :
http://forum.xda-developers.com/showpost.php?p=9143548&postcount=7
This is another way to root the phone and get amon ra on.
maheshpatel said:
i guess you are using unlocked SPL It might be causing problems
Click to expand...
Click to collapse
I'm not sure I have understand :
Code:
unlocked SPL
What I must do ?
Steven_belfast said:
Greetings,
See the following :
http://forum.xda-developers.com/showpost.php?p=9143548&postcount=7
This is another way to root the phone and get amon ra on.
Click to expand...
Click to collapse
The link is for root a phone ?!? no?
I just want to recover my recovery !
For flash my old recovery I do all it say in your URL apart the format of SD card, do you think it is important?
Moreover memory on my phone is 56m do you think it can be the problem ?
Can I saw my recovery partition on the file system?
Thanks at both of you for your rapid answered, I hope you will answered me again !
Is your phone is rooted ?
Code:
"mtd: read error at 0x00000000 (Out of memory)"
It needs rooted phone to run it ..
i 'd suggest root your phone -)
&
try this :-
Power on your hero while holding down the volume down button.
then:
Code:
fastboot erase recovery
fastboot flash recovery - & filename of recovery in the pc
try flashing old Recovery of Amon_ra first . if it works than try latest one ..
If nothing comes on your way. than i would suggest use stock RUU & than try flashing Amon_Ra & See you can flash it from boot loader or not ?
maheshpatel said:
Is your phone is rooted ?
Code:
"mtd: read error at 0x00000000 (Out of memory)"
It needs rooted phone to run it ..
i 'd suggest root your phone -)
&
try this :-
Power on your hero while holding down the volume down button.
then:
Code:
fastboot erase recovery
fastboot flash recovery - & filename of recovery in the pc
try flashing old Recovery of Amon_ra first . if it works than try latest one ..
If nothing comes on your way. than i would suggest use stock RUU & than try flashing Amon_Ra & See you can flash it from boot loader or not ?
Click to expand...
Click to collapse
Yes my phone is rooted : When the phone is on, I can become root by typing "su" and then an application ask me if I allow to become root.
So I have "Power on my hero while holding down the volume down button" and I see a green check list during a second and after I see in blue HBOOT.
So I have try to do on my computer "fastboot erase recovery" but my prompt say me
Code:
C:\Windows\System32>fastboot erase recovery
erasing 'recovery'...
and it never do anythinks !
So if I press back on the Hero I can see :
Code:
C:\Windows\System32>fastboot erase recovery
erasing 'recovery'... FAILED (status read failed (Too many links))
finished. total time: 78.280s
An idea?
I'm totally out of ideas...
you are not using the standard data cable that comes with the htc hero? status read failed (Too many links)) error comes when you are not using standard data cable that comes with the htc hero..
Make sure your adb tools working correctly..
maheshpatel said:
I'm totally out of ideas...
you are not using the standard data cable that comes with the htc hero? status read failed (Too many links)) error comes when you are not using standard data cable that comes with the htc hero..
Make sure your adb tools working correctly..
Click to expand...
Click to collapse
This is the standard cable but a little broken.
I will search a bit more.
If you or someone find an other idea !
Thanks !
your cable is causing problem . find a good cable and do it
I had problems with the original cable. So what's happening when you shutdown and press menu/power. Blocked triangle?
And it was all yellow...
spikey68 said:
I had problems with the original cable. So what's happening when you shutdown and press menu/power. Blocked triangle?
And it was all yellow...
Click to expand...
Click to collapse
Yes this is my problem a yellow blocked triangle when boot on recovery mode...
Do You have a solution?
Hello, I received my Zuk Z1 with Zui rom two days ago and managed to install Cyanogen Os with threads here.
My problem is that OTA updates are downloaded but do not apply. Phone restarts to cm recovery and nothing happens. Any idea?
Glops4 said:
Hello, I received my Zuk Z1 with Zui rom two days ago and managed to install Cyanogen Os with threads here.
My problem is that OTA updates are downloaded but do not apply. Phone restarts to cm recovery and nothing happens. Any idea?
Click to expand...
Click to collapse
Hi, Factory data reset, after that update OTA again!
Thanks for your help. I did a factory reset, still nothing. Also from recovery, then rebooted, and the OTA failed. Then I found out that kingroot was still there! Unrooted from the app, rebooted and it disappeared.
But OTA is still not working. I went in developper option and saw that bootloader is locked. impossible to unlock it. Even with fastboot commands. I am stuck with this preliminary version for now. How to unlock the bootloader now?
Glops4 said:
Thanks for your help. I did a factory reset, still nothing. Also from recovery, then rebooted, and the OTA failed. Then I found out that kingroot was still there! Unrooted from the app, rebooted and it disappeared.
But OTA is still not working. I went in developper option and saw that bootloader is locked. impossible to unlock it. Even with fastboot commands. I am stuck with this preliminary version for now. How to unlock the bootloader now?
Click to expand...
Click to collapse
Hi Glops, click my Google+ profile link in my signature and message me on Hangouts. I will be happy to help out
Ota is working again. I had to re-convert the z1 to cyanogen with the convert rom, cm recovery and adb.
Please DO NOT root your z1 with KINGROOT!!
It will mess up your system and your bootloader.
Glops4 said:
Ota is working again. I had to re-convert the z1 to cyanogen with the convert rom, cm recovery and adb.
Please DO NOT root your z1 with KINGROOT!!
It will mess up your system and your bootloader.
Click to expand...
Click to collapse
Hi, I did same think as you. Rooted my phone with KingRoot and now OTA updates not working. Can you please write a "How-to" to recover my Zuk? I would be very thankfull.
You have to follow this tutorial here and you will get back the OTA updates.
Thank you, i will try it. I'm just trying download all necessary files, but stumbled upon driver downloads. Whole site is in chinese and cannot download anything. If you have those drivers, can you please upload them somewhere? Thx.
And one thing, since i have the international version, which have original CM OS installed (not ZUI), doesnt it mess something on phone?
Cyanogen preview
In my device it show cyanogen preview 12.1 yoga4pap1cg,
Any one guide me how to remove the same
How should bootloader screen looks like on ZUK?
When i restart to Bootloader (adb reboot bootloader or directly from phone) all i can see is logo "ZUK" in the middle and "Powered by Android" in the bottom. And I think this is the problem, since fastboot devices not showing anything. Also fastboot -i 0x2b4c oem get-device-info get stuck on three dots and nothing happens.
In this mode i can see the my phone in device manager as ShenQi Composite ADB Interface.
Yes bootloader screen looks just like yours. If you can boot to bootloader, then you do not need more drivers.
This is how I proceeded, with Cyanogen Os installed and wanting to get rid of Kingroot (for each one having the same problem):
You don't need ShenQi drivers if you proceed this way and you can uninstall them to just auto install Android ADB Interface.
- Enable usb debugging in developpers option
- 1st get the Rsa authorisation. For that download Kingroot for windows, install and run in your computer. Attach device and press blue button. accept "always accept this device" in your phone and close Kingroot
- Detach the phone
- Shut down the phone
- Press volume down and power button, you will open a menu
- attach device to the computer
- open a terminal in windows
- check the exact adress you see, for example C:\Users\Glops4>
- Open Windows Explorer in your computer
- Copy the following files to the same directory you see in terminal: z1.cyanogen.convert.signed.zip , z1.recovery.testkeys.img (you have to rename extension to .img by yourself)
- In terminal, type : "adb devices"
- You should see your device listed
- then type "adb reboot bootloader"
- Zuk screen will remain
- Do not write "fastboot -i 0x2b4c oem get-device-info"
- Skip checking if bootloader is unlocked
- write "fastboot -i 0x2b4c boot z1.recovery.testkeys.img"
- Go back to your phone, you should be in CM Recovery
- "Wipe data/factory reset"
- "Apply update"
- "Apply from ADB"
- Back to terminal on the computer
- "adb sideload z1.cyanogen.convert.signed.zip"
- Wait to completion (very long)
- Do all the updates
- Root?????
____________
(Remix of Modaco tutorial)
Glops4 said:
Yes bootloader screen looks just like yours. If you can boot to bootloader, then you do not need more drivers.
This is how I proceeded, with Cyanogen Os installed and wanting to get rid of Kingroot (for each one having the same problem):
You don't need ShenQi drivers if you proceed this way and you can uninstall them to just auto install Android ADB Interface.
- Enable usb debugging in developpers option
- 1st get the Rsa authorisation. For that download Kingroot for windows, install and run in your computer. Attach device and press blue button. accept "always accept this device" in your phone and close Kingroot
- Detach the phone
- Shut down the phone
- Press volume down and power button, you will open a menu
- attach device to the computer
- open a terminal in windows
- check the exact adress you see, for example C:\Users\Glops4>
- Open Windows Explorer in your computer
- Copy the following files to the same directory you see in terminal: z1.cyanogen.convert.signed.zip , z1.recovery.testkeys.img (you have to rename extension to .img by yourself)
- In terminal, type : "adb devices"
- You should see your device listed
- Adb reboot bootloader
- Zuk screen will remain
- Do not write "fastboot -i 0x2b4c oem get-device-info"
- Skip checking if bootloader is unlocked
- write "fastboot -i 0x2b4c boot z1.recovery.testkeys.img"
- Go back to your phone, you should be in CM Recovery
- "Wipe data/factory reset"
- "Apply update"
- "Apply from ADB"
- Back to terminal on the computer
- "adb sideload z1.cyanogen.convert.signed.zip"
- Wait to completion (very long)
- Do all the updates
- Root?????
____________
(Remix of Modaco tutorial)
Click to expand...
Click to collapse
HI, just to clarify some thinks:
- Press volume down and power button, you will open a menu - this way i boot into EDL menu, right? With the test board, etc...
- Copy the following files... - I have those files named exactly as you mentioned. So which extensions should i change to img? I have ...testkeys.img and ...signed.zip
- fastboot -i 0x2b4c boot z1.recovery.testkeys.img - i once tried this (but booted to bootloader from CM, not from EDL) and its failed to load the file (something about not signed?)
And which exact drivers should I use? Can you please post a link?
- Press volume down and power button, you will open a menu - this way i boot into EDL menu, right? With the test board, etc...
Click to expand...
Click to collapse
Right
- Copy the following files... - I have those files named exactly as you mentioned. So which extensions should i change to img? I have ...testkeys.img and ...signed.zip
Click to expand...
Click to collapse
Those are ok, do not change anything
- fastboot -i 0x2b4c boot z1.recovery.testkeys.img - i once tried this (but booted to bootloader from CM, not from EDL) and its failed to load the file (something about not signed?)
And which exact drivers should I use? Can you please post a link?
Click to expand...
Click to collapse
I think your drivers are ok, please try as I said and you should be fine
Glops4 said:
Right
Those are ok, do not change anything
I think your drivers are ok, please try as I said and you should be fine
Click to expand...
Click to collapse
End up with error:
Code:
C:\android-sdk-windows\platform-tools>Adb reboot bootloader
C:\android-sdk-windows\platform-tools>fastboot -i 0x2b4c boot z1.recovery.testkeys.img
downloading 'boot.img'...
OKAY [ 0.374s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.390s
Any idea?
Need to flash again CM, cuz with Kingroot/Root you can't update over OTA. I hope CyanogenMod will release soon.
Gesendet von meinem Z1 mit Tapatalk
vr43x3m said:
End up with error:
Code:
C:\android-sdk-windows\platform-tools>Adb reboot bootloader
C:\android-sdk-windows\platform-tools>fastboot -i 0x2b4c boot z1.recovery.testkeys.img
downloading 'boot.img'...
OKAY [ 0.374s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.390s
Any idea?
Click to expand...
Click to collapse
Finally got it. Apparently the option to unlock bootloader in phone do nothing. I must used "fastboot -i 0x2b4c oem unlock-go". So its finally uploading the image. Thank for all your informations.
vr43x3m said:
Finally got it. Apparently the option to unlock bootloader in phone do nothing. I must used "fastboot -i 0x2b4c oem unlock-go". So its finally uploading the image. Thank for all your informations.
Click to expand...
Click to collapse
This is the same with the Yu Yunique and Wileyfox Swift phone, which also run CyanogenOS, can someone explain why its unlock-go and not just unlock as for other phones?
othe01 said:
This is the same with the Yu Yunique and Wileyfox Swift phone, which also run CyanogenOS, can someone explain why its unlock-go and not just unlock as for other phones?
Click to expand...
Click to collapse
To answer my own question, if we look in the android kernel sources (aboot.c) we find:
Code:
void cmd_oem_unlock(const char *arg, void *data, unsigned sz)
{
if(!is_allow_unlock) {
fastboot_fail("oem unlock is not allowed");
return;
}
display_fbcon_message("Oem Unlock requested");
fastboot_fail("Need wipe userdata. Do 'fastboot oem unlock-go'");
}
void cmd_oem_unlock_go(const char *arg, void *data, unsigned sz)
{
if(!device.is_unlocked || device.is_verified)
{
if(!is_allow_unlock) {
fastboot_fail("oem unlock is not allowed");
return;
}
device.is_unlocked = 1;
device.is_verified = 0;
write_device_info(&device);
struct recovery_message msg;
snprintf(msg.recovery, sizeof(msg.recovery), "recovery\n--wipe_data");
write_misc(0, &msg, sizeof(msg));
fastboot_okay("");
reboot_device(RECOVERY_MODE);
}
fastboot_okay("");
}
The difference between "oem unlock" and "oem unlock-go" seems to be that the unlock-go one also wipes out the userdata; No idea why it is needed tho.
vr43x3m said:
Finally got it. Apparently the option to unlock bootloader in phone do nothing. I must used "fastboot -i 0x2b4c oem unlock-go". So its finally uploading the image. Thank for all your informations.
Click to expand...
Click to collapse
Good job mate, thanks for the info.
Hello i have the same problem. Im not techy guy i dont know to do it. Anyone who can help me? Please
Hello!
At its OPO I changed the display the frame and battery. Installation went without any problems. Unfortunately, after launching the phone started only Cyanogen Recovery. Display and touch functions entirely without any problems. So I wanted to re-install CM13, but the phone does not run fastboot. You can not run from Cyanogen Recovery or VOL + POWER-UP. The phone always starts to Cyanogen Recovery. I tried this yet through ADB, phone are detected as recovery (so drivers are probably fine), but when you try to fastboot command ends "Device waiting." Thank you in advance for your help and answers.
Hi, maybe you are in the wrong section so ask moderator to move your thread to Q-A & Troubleshooting
I changed the display of my OPO 3 times and I never had this issue.
- your fastboot is corrupted or something like that.
- Cyanogen recovery su***
- you don't do the manipulation correctly
Here's a small list of things to try :
#1 Firstly First :
- Boot your phone to the OS => Settings => Developer options.
- untick "Update Cyanogen recovery", tick "Advanced reboot"
- long press on the power button, the boot menu will appear and then, press reboot => reboot to bootloader.
- look if the phone boot in fastboot mode
2# Secondly Second :
- do the #1 Firstly First steps but select "Reboot to recovery" and flash TWRP 2.8.7.0.3.ZIP https://www.androidfilehost.com/?w=files&flid=30332
- install Cyanogen OS 13 signed flashable zip (link in #3)
#3 Thirdly Third
- if the first & the second method didn't worked, download the signed flashable zip you want here :
http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
- And TRY to install it via Cyanogen Recovery.
Tell me if one of these methods worked for you
natheux said:
Hi, maybe you are in the wrong section so ask moderator to move your thread to Q-A & Troubleshooting
I changed the display of my OPO 3 times and I never had this issue.
- your fastboot is corrupted or something like that.
- Cyanogen recovery su***
- you don't do the manipulation correctly
Here's a small list of things to try :
#1 Firstly First :
- Boot your phone to the OS => Settings => Developer options.
- untick "Update Cyanogen recovery", tick "Advanced reboot"
- long press on the power button, the boot menu will appear and then, press reboot => reboot to bootloader.
- look if the phone boot in fastboot mode
2# Secondly Second :
- do the #1 Firstly First steps but select "Reboot to recovery" and flash TWRP 2.8.7.0.3.ZIP https://www.androidfilehost.com/?w=files&flid=30332
- install Cyanogen OS 13 signed flashable zip (link in #3)
#3 Thirdly Third
- if the first & the second method didn't worked, download the signed flashable zip you want here :
http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
- And TRY to install it via Cyanogen Recovery.
Tell me if one of these methods worked for you
Click to expand...
Click to collapse
Thank you very much for trying to help. I appreciate it
# 1 I can not - not letting android
# 2 Can not
The only thing that can be run Recovery is SIDELOAD through which the phone to a PC continuous. Unfortunately, no bootloader command does not work and end up on the "waiting for device".
I also tried to install ColorOs, but the report is plenty FAILED and the phone starts only ColorOS Recovery.
I do not know what to do: - ((((
What if the fastboot damaged?
antikipr said:
Thank you very much for trying to help. I appreciate it
# 1 I can not - not letting android
# 2 Can not
The only thing that can be run Recovery is SIDELOAD through which the phone to a PC continuous. Unfortunately, no bootloader command does not work and end up on the "waiting for device".
I also tried to install ColorOs, but the report is plenty FAILED and the phone starts only ColorOS Recovery.
I do not know what to do: - ((((
What if the fastboot damaged?
Click to expand...
Click to collapse
I'm trying yep, you're welcome
Okay hum.. have you looked at this thread : https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
It's the ultimate guide, the step 5 is the last solution when a device is bricked. I suggest you to check the step 1 in a first way, the step 2 in a second way, etc..
Tell me if it's helpful or not..
PS : are you a Windows or Linux user ?
Some steps too understand. When I try to install ColorOS through Msm8974 Download Tool in 1.7 is the result:
8974_msimage.mbn: OK
dynamic_nvbk.bin: OK
emmc_appsboot.mbn: OK
gpt_backup0.bin: OK
gpt_backup0_64G.bin: OK
gpt_main0.bin: OK
gpt_main0_64G.bin: OK
userdata.img: FAILED
userdata_64G.img: FAILED
rawprogram0.xml: OK
rawprogram0_64G.xml: OK
NON-HLOS.bin: OK
MPRG8974.mbn: OK
rpm.mbn: OK
sbl1.mbn: OK
sdi.mbn: OK
static_nvbk.bin: OK
tz.mbn: OK
boot.img: FAILED
cache.img: OK
persist.img: FAILED
recovery.img: FAILED
system.img: FAILED
Then the phone starts only ColorOs Recovery.
I use Windows 10.
I do not know what to do: - ((((
I am attempting to put lineageos on my new Mi A1, following the installation guide here https://wiki.lineageos.org/devices/tissot/install
I have previously installed lineage on my old Moto G LTE and a Samsung Galaxy S4 and have not run into issues.
I have unlocked the bootloader and all that but I can't get twrp to boot.
I boot into fastboot with
Code:
adb reboot bootloader
that works fine, then I
Code:
fastboot boot twrp-3.2.2-0-tissot.img
This seems to have no effect, other than my phone 'disconnecting' from the PC.
I get the following terminal output
Code:
./fastboot boot .\twrp-3.2.2-0-tissot.img
Downloading 'boot.img' OKAY [ 0.682s]
booting OKAY [ 0.623s]
Finished. Total time: 1.336s
However nothing happens on the phone, it still just has the fastboot logo on it.
At this point if I manually reboot (long-press power) it will reboot into stock rom.
If I manually reboot into recovery (long-press power+volume up) it will reboot into stock recovery
I have ensured my sytem tools are up to date, and tried the previous version of twrp, and there is no change.
I WAS able to get twrp to boot using the "Mi A1 Tool" i found here https://forum.xda-developers.com/mi-a1/how-to/tool-xiaomi-mi-a1-tool-drivers-unlock-t3742857
However I was not able to install lineage due to an error.
I did not copy the exact output but it was something along the lines of
error 7, kInstallDeviceOpenError
After this attempt, I reflashed the stock rom using Xiaomi tools, and am back to the beginning.
The phone is fully up-to-date with stock updates, Android 8.1, July security update.
Once again went through the bootloader unlocking, and everything, but have arrived at the same result.
Anyone have any ideas?
any help would be greatly appreciated!
Thanks!
Hey, could you try this TWRP made for Oreo? https://www.androidfilehost.com/?fid=818070582850498337 (thread: https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472)
I've also had some issues booting TWRP, but running
Code:
fastboot oem unlock
was enough to boot it successfully (
Code:
fastboot boot recovery-3.2.1-2-oreo.img
)
Thank you!
dgadelha said:
Hey, could you try this TWRP made for Oreo? https://www.androidfilehost.com/?fid=818070582850498337 (thread: https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472)
I've also had some issues booting TWRP, but running
Code:
fastboot oem unlock
was enough to boot it successfully (
Code:
fastboot boot recovery-3.2.1-2-oreo.img
)
Click to expand...
Click to collapse
This recovery image worked great, AND installed lineage, thank you very much.
However, I am now unable to get gapps working.
I was pointed to this changelog here https://lineageos.org/Changelog-19/ by a user in the lineage subreddit.
I rebooted from twrp into the lineage recovery, chose Apply Update -> Apply from ADB
On my PC I run
Code:
./adb sideload .\MindTheGapps-8.1.0-arm64-20180610_024023
.zip
and after a pause I get the output
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: No error
and sometimes I get
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: Connection reset by peer
What happens on the phone has been a little different each time I have attempted this.
It either pops up on screen that it is unable to verify the file, install anyway?, doing so doesn't work.
OR it is hung up on a progress bar screen, with the following log output, or a slight variation of it
Code:
Stopping adbd...
Now send the package you want to apply to the device with "adb sideload <filename>"...
Finding update package...
Opening update package...
Verifying update package...
E: Signature verification failed
E:error: 21 Restarting dbd... Installation aborted.
After many attempts of this, reflashing lineage, and trying again, it did miraculously start doing the transfer at one point. It got to 47% then failed again.
Can't you just install from recovery?
https://forum.xda-developers.com/mi-a1/development/rom-lineageos-15-1-t3757938
pidermin said:
This recovery image worked great, AND installed lineage, thank you very much.
However, I am now unable to get gapps working.
I was pointed to this changelog here https://lineageos.org/Changelog-19/ by a user in the lineage subreddit.
I rebooted from twrp into the lineage recovery, chose Apply Update -> Apply from ADB
On my PC I run
Code:
./adb sideload .\MindTheGapps-8.1.0-arm64-20180610_024023
.zip
and after a pause I get the output
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: No error
and sometimes I get
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: Connection reset by peer
What happens on the phone has been a little different each time I have attempted this.
It either pops up on screen that it is unable to verify the file, install anyway?, doing so doesn't work.
OR it is hung up on a progress bar screen, with the following log output, or a slight variation of it
Code:
Stopping adbd...
Now send the package you want to apply to the device with "adb sideload <filename>"...
Finding update package...
Opening update package...
Verifying update package...
E: Signature verification failed
E:error: 21 Restarting dbd... Installation aborted.
After many attempts of this, reflashing lineage, and trying again, it did miraculously start doing the transfer at one point. It got to 47% then failed again.
Click to expand...
Click to collapse
Hey,
Install GApps also at TWRP. Signature verification is failing most probably because the Lineage Recovery should be accepting only Lineage-signed ZIP files.
You can install TWRP in your current boot image (so you don't need to boot TWRP everytime through fastboot) with this ZIP: https://www.androidfilehost.com/?fid=746010030569959456 (yet, you need to boot to TWRP through fastboot so you can flash it, but no need to boot it manually after installing it). Notice that after every system update you may need to install TWRP again (same for Magisk), as boot images get replaced.
Also, if sideload fails, you can just do a
Code:
adb push filename.zip /sdcard/
then install the ZIP directly from the "Install" section on TWRP.
Thanks!
Thanks a lot!
I found and was able to follow this guide
https://forum.xda-developers.com/mi-a1/how-to/lineageos-gapps-magisk-twrp-dolbyatmos-t3762939
instead of the one on the lineageOS website, and I am up and running.
Thank you very much for your time!
Can't boot to recovery or fastboot
I'm totally not getting the problem, i am having network issues on my Mi A1 on both Oreo and pie. So I decided to install a custom ROM but I can't boot my device to fastboot or recovery, it simply reboots . I tried the hard keys as well as through the PC using command prompt it just reboots normally. Any suggestions on what should I do Please?
Azan Qazi said:
I'm totally not getting the problem, i am having network issues on my Mi A1 on both Oreo and and pie. So I decided to install a custom ROM but I can't boot my device to fastboot or recovery, it simply reboots . I tried the hard keys as well as through the PC using command prompt. Any suggestions on what should I do.
Click to expand...
Click to collapse
Have you tried doing reboot in the OS and choosing Recovery option?
Azan Qazi said:
I'm totally not getting the problem, i am having network issues on my Mi A1 on both Oreo and pie. So I decided to install a custom ROM but I can't boot my device to fastboot or recovery, it simply reboots . I tried the hard keys as well as through the PC using command prompt it just reboots normally. Any suggestions on what should I do Please?
Click to expand...
Click to collapse
TrueMS said:
Have you tried doing reboot in the OS and choosing Recovery option?
Click to expand...
Click to collapse
yes sir I did tried several times. But as I said above it simply reboots the system.