Related
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
It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is no longer available - seek out the LineageOS rom instead
I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.
Swift 2 Plus and SuperSU
FelixPiers said:
I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.
Click to expand...
Click to collapse
Yes initially the only version of SuperSU I could find was v2.46, which kept failing.
Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.
thejackle123 said:
Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.
Click to expand...
Click to collapse
Is it too hard to google your question?
Works on most devices:
1) Turn off device
2) Hold VOLUME UP button
3) Connect device to PC via usb-cable
I installed SuperSU, before that I installed TWRP. Now I am unable to install the latest update "cm-marmite-a1478a0ee9-to-7aa1c797975e-signed"
When I download this update and perform the actual install, it gives an error. Restarting the phone via TWRP recovery gives the same error. I am getting "Error 7"
So no I want to revert back, to get rid off SuperSU and TWRP to install all updates and then later root the device with TWRP and SuperSU. How do I get the original state of the phone back?
Or do you have any advice how to get the latest update installed?
Thx.
SMessy said:
It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is here
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll
Rom location
RayfG said:
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll
Click to expand...
Click to collapse
Just to confirm the stock room is still at this location as at 2nd march 2017
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
"Just to confirm the stock ROM is still at this location as at 2nd march 2017 :"
Link above does not work now, however below one does.
https://androidfilehost.com/?w=files&flid=126553
Hmmm. I'm going to try again. Before I got fastboot in red and Dvice Status: Locked. But I'll try again, see where I get.
Image of issue: https://ibb.co/jfLPye
edit: Updating to the latest Oreo update (8.1 I think)
---------- Post added at 08:34 AM ---------- Previous post was at 08:14 AM ----------
ohhhhhhh, I had to turn the phone off while connected, already running "adb & fastboot" (not just adb) then (phone connected in USB debugging mode) turn off the phone and hold volume up (no need to hole the power key as connected and I got the option to unlock with a warning that I may void the warranty. Then my phone encrypted/re-encrypted itself (I think it was already encrypted).
Now to flash TWRP (3.2 I think) and flash a custom ROM (Lineage 15.1 / 8.1 Oreo) Not sure if I should root or not. And if I do, should I root before installing 8.1?
got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)
Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?
bl91 said:
Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?
Click to expand...
Click to collapse
your device isn't picked up by fastboot ...first of all install the very latest version of adb ...using the usual Ubuntu story
sudo apt-get install adb
sudo apt-get upgrade
sudo apt-get update
sudo reboot
then switch on your device
go to /settings/about/buildnumber
click until developer settings are enabled
go to developer settings
toggle oem unlock to on
toggle adb to on
WITHOUT SWITCHING OFF
connect device to pc/laptop with original orange wileyfox cable
now your Ubuntu machine
must install drivers and Mount the phone so it should appear as a mounted volume on desktop
now open a terminal
now run the following :
sudo adb
sudo adb devices
now look on your phone and pull down the notification shadse ..make sure you have adb connected and file transfer mode ..if not change from charge to file transfer ...
there should be a pop up window on phone screen asking for permission for adb ..select allways allow and give pernission / authorization ..
now in terminal run adb devices and it should return some value as connected device
run:
adb reboot bootloader
phone will reboot to bootloader
run:
fastboot oem unlock
*use volume up to select yes
**beware will erase DATA ...
***if it doesn't work and adb and fastboot doesn't detect your device it is a driver problem but i haven't used Ubuntu in ages so can't remember steps to update your drivers other than updating the whole adb package
****some ubuntu instructions might be a little off as I've explained previously it's been a while
*****your waiting for device means
-adb service didn't start
+try "sudo adb"
-adb drivers out of date
+try sudo apt-get update
-adb on device not toggled to on
+toggle adb in dev settings
*adb authorization not given **should still see unauthorized device
-bad usb cable
+try another usb cable
-bad usb port
+try a different usb port
_____for clarity double check Ubuntu adb instructions and commands but this should put you on the right track____
---------- Post added at 08:30 AM ---------- Previous post was at 08:19 AM ----------
reggiexp said:
got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)
Click to expand...
Click to collapse
don't reboot immediately ..stock recovery will be flashed back over twrp
*i assume you know how to get to fastboot
adb reboot bootloader
fastboot oem unlock
*volume up for yes
fastboot flash recovery recovery.img
*make sure you have a copy of twrp called recovery.img in adb folder
when it says sending...
then is says writing ...
then it says done
DON'T REBOOT
UNPLUG USB
***MANUALLY BOOT TO BOOTLOADER USING VOLUME UP AND POWER
**** IN BOOTLOADER SELECT "RECOVERY"
you should then just wait on wileyfox first time it takes a minute or two don't know why then
it should boot to twrp
***you can take stock boot.img and patch it with magisk
-use: fastboot flash boot boot.img
-then you will have magisk and rooted
-using twrp apk or something like root rasher or flasher ..give apk root permission
-download twrp ..flash with apk from inside system ..after flashing select yes to reboot directly to recovery
Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now
bl91 said:
Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now
Click to expand...
Click to collapse
okay no problem
*i know everybody likes lineage and its usually more stable and the base for many custom roms
however just my 2cents worth ...i tried all the roms for our device ..but the by far the best for me was following the tutorial on how to make our device treble compatible ..
Then ...after 3-4 months of trying different treble GSI's i have stopped on Viper Official Pie 64bit A-only treble system.img ... at least give it a try after trying out lineageOs ..
you might thank me .
I can't get my device to show up usb debugging is on, Advanced Reboot', 'OEM Unlocking' etc. I've been trying for hours and hours. It shows up to transfer files if I want that mode so my PC is recognising it, but it doesn't seem to have drivers for adb. I've tried installing google usb drivers and also this: https://afterthoughtsoftware.com/posts/using-adb-with-wileyfox-swift
sorry if I haven't explained clearly, I'm just so sleepy from going around in circles. :|
I've rooted phones before and never had this issue. please can anybody help?
edit: have fixed I think! did two things at once so not sure which. I revoked usb devices so that my computer would have to ask permission again to connect (or something like this) and also clicked a thing on my PC to allow it to update what I think said driver icons automatically, which I wouldn't have thought would help, but it seemed to find the adb driver this time. I'd probably make more sense if it weren't 1am. :|
When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.
My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
RavZ75 said:
When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.
Click to expand...
Click to collapse
bubba_66 said:
My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
Click to expand...
Click to collapse
Doesn't seem that many who have this lock on their bootloaders, the only ones I could find here who had locked bootloaders the same way as I had are in the LineageOS 14.1 thread.
So at least I am not alone with that but sure makes me wonder how it is so for some while others not.
After unlock bootloader Everytime reboot always like this https://ibb.co/NSZR818
DWYOR
After a long time of googling I got a solution for yu5510a full access.
You need
Adb + fastboot
Twrp 2.8.7.0 tomato
SuperSU.zip
Coolpad drivers
Cyanogen ROM V1 from firmwarefile.com
Any Custom Rom, I am using aosp extended.
Gapps
Memory card
Install all drivers , adb & fastboot.
First flash Cyanogen ROM using YGDP tool
Use version 3.98 in other versions I got problems.
After ROM installation enable developer option.
Enable android debugging, fast reboot and check update cyanogen recovery
Now connect phone with PC
Goto adb folder
Copy twrp.img in adb folder
Shift + Right click select open command window here
Type adb devices
Device should be shown if not showing try to install adb drivers
Now after that
Type Command adb reboot-bootloader
Device will be rebooted in bootloader
Type command fastboot -i 0x1ebf oem device-info to verify device in fastboot mode and your bootloader is unlocked or not.
If bootloader showing unlocked then follow next process if not then unlock it
Type command fastboot -i 0x1ebf oem unlock
Boot loader unlocked now.
Remove data cable and remove battery from phone for 30 secs and reinsert again.
Press volume + key and hold
Attach phone with PC ( it shows fastboot mode)
After that type command
fastboot -i 0x1ebf flash recovery twrp.img
When done remove data cable & battery
After 30 secs reinsert battery
Press Volume + , Volume - & Power key
When yu logo appears release power key and keep pressing both volume keys
You will be goto twrp
Now wipe everything also format data/don't delete mmc
Restart twrp to recovery
Your internal and external storage are mounted.
Install any custom ROM for yureka/yureka plus
Flash gapps ( not required in miui & quarkos)
Flash SuperSU.zip
Reboot
It takes 10-15 minutes for first boot .
Done
Flash Latest NON-HLOS.bin before flashing any volte ROM.
Flash through fastboot
File link
https://drive.google.com/file/d/0B8Vodzmhc0GlXzdtOUFjb29EOFU/view
Extract .zip
Copy NON-HLOS.bin in adb folder
Open command prompt here
Connect phone into fastboot mode
Type command
fastboot -i 0x1ebf flash modem NON-HLOS.bin
Wait till process done.
Disconnect phone
Remove battery and insert again
Goto twrp recovery.
Install any volte enabled ROM.
Enjoy.:good:
OEM unlock command not found
hi,
I am trying to root my yu yureka plus( YU5510A white color) running android 5.1.1 , build number is 5.1.111.P0.160314.YU5510A , i am able to connect the phone to my PC running adb,
"adb devices" lists the phone , "adb reboot bootloader" puts the phone in fastboot ( screeen doesnt show fastboot instead it shows do not disconnect usb cable and non secure phone). When i run the command fastboot -i 0x1ebf oem unlock , im getting the error as command not found. same error im getting when i run the command fastboot -i 0x1ebf oem device-info
what could be the reason.
Any help in this regard is appreciated.
nischait said:
DWYOR
After a long time of googling I got a solution for yu5510a full access.
You need
Adb + fastboot
Twrp 2.8.7.0 tomato
SuperSU.zip
Coolpad drivers
Cyanogen ROM V1 from firmwarefile.com
Any Custom Rom, I am using aosp extended.
Gapps
Memory card
Install all drivers , adb & fastboot.
First flash Cyanogen ROM using YGDP tool
Use version 3.98 in other versions I got problems.
After ROM installation enable developer option.
Enable android debugging, fast reboot and check update cyanogen recovery
Now connect phone with PC
Goto adb folder
Copy twrp.img in adb folder
Shift + Right click select open command window here
Type adb devices
Device should be shown if not showing try to install adb drivers
Now after that
Type Command adb reboot-bootloader
Device will be rebooted in bootloader
Type command fastboot -i 0x1ebf oem device-info to verify device in fastboot mode and your bootloader is unlocked or not.
If bootloader showing unlocked then follow next process if not then unlock it
Type command fastboot -i 0x1ebf oem unlock
Boot loader unlocked now.
Remove data cable and remove battery from phone for 30 secs and reinsert again.
Press volume + key and hold
Attach phone with PC ( it shows fastboot mode)
After that type command
fastboot -i 0x1ebf flash recovery twrp.img
When done remove data cable & battery
After 30 secs reinsert battery
Press Volume + , Volume - & Power key
When yu logo appears release power key and keep pressing both volume keys
You will be goto twrp
Now wipe everything also format data/don't delete mmc
Restart twrp to recovery
Your internal and external storage are mounted.
Install any custom ROM for yureka/yureka plus
Flash gapps ( not required in miui & quarkos)
Flash SuperSU.zip
Reboot
It takes 10-15 minutes for first boot .
Done
Click to expand...
Click to collapse
nithin1664 said:
hi,
I am trying to root my yu yureka plus( YU5510A white color) running android 5.1.1 , build number is 5.1.111.P0.160314.YU5510A , i am able to connect the phone to my PC running adb,
"adb devices" lists the phone , "adb reboot bootloader" puts the phone in fastboot ( screeen doesnt show fastboot instead it shows do not disconnect usb cable and non secure phone). When i run the command fastboot -i 0x1ebf oem unlock , im getting the error as command not found. same error im getting when i run the command fastboot -i 0x1ebf oem device-info
what could be the reason.
Any help in this regard is appreciated.
Click to expand...
Click to collapse
Try without using 0x1ebf and report.
nischait said:
Try without using 0x1ebf and report.
Click to expand...
Click to collapse
I tried without -i 0x1ebf also but it does not show in fastboot. With -i 0x1ebf it shows "xyznumbers fastboot" . The problem now is , I flashed through YGDP tool and now it shows aboot failed image, and does not boot at all.
Why doe my phone show non secure phone ?
Please help.
Yogesh1969 said:
I tried without -i 0x1ebf also but it does not show in fastboot. With -i 0x1ebf it shows "xyznumbers fastboot" . The problem now is , I flashed through YGDP tool and now it shows aboot failed image, and does not boot at all.
Why doe my phone show non secure phone ?
Please help.
Click to expand...
Click to collapse
Download cyanogen ROM and flash it with ygdp
1st ever rom uploaded in AFH.
Your device should be boot up.
Then try with command prompt.
May be new device having different device ID.
nischait said:
Try without using 0x1ebf and report.
Click to expand...
Click to collapse
Hi...
I too face the same problem, I tried fastboot adb and YU yureka drivers reinstalling and connected device to PC it gets charger when connection in on, when connected in fastboot mode on device it shows fastboot but when check in PC for device info, it dosen't show any connected device. I followed many tutorials for this to install TWRP but its impossible to install without establishing a proper connection. I also tried to install TWRP without PC, for this i need to root my device and flash TWRP img, so I started trying root I had used kingroot, kingoroot, towelroot and some more but failed to root, I am still trying to install TWRP can anyone help me in either of the process to install TWRP.
nischait said:
Download cyanogen ROM and flash it with ygdp
1st ever rom uploaded in AFH.
Your device should be boot up.
Then try with command prompt.
May be new device having different device ID.
Click to expand...
Click to collapse
I couldnt find the ygdp version of Cynogen, any way I found a way from youtube which solved my problems.
Link : https://www.youtube.com/watch?v=2Gpz65r2pNM
---------- Post added at 05:21 PM ---------- Previous post was at 05:18 PM ----------
vijaykumarbabu079 said:
Hi...
I too face the same problem, I tried fastboot adb and YU yureka drivers reinstalling and connected device to PC it gets charger when connection in on, when connected in fastboot mode on device it shows fastboot but when check in PC for device info, it dosen't show any connected device. I followed many tutorials for this to install TWRP but its impossible to install without establishing a proper connection. I also tried to install TWRP without PC, for this i need to root my device and flash TWRP img, so I started trying root I had used kingroot, kingoroot, towelroot and some more but failed to root, I am still trying to install TWRP can anyone help me in either of the process to install TWRP.
Click to expand...
Click to collapse
For drivers problem install pdanet. And you can refer to the youtube video link (above post) if you want for all needs.
vijaykumarbabu079 said:
Hi...
I too face the same problem, I tried fastboot adb and YU yureka drivers reinstalling and connected device to PC it gets charger when connection in on, when connected in fastboot mode on device it shows fastboot but when check in PC for device info, it dosen't show any connected device. I followed many tutorials for this to install TWRP but its impossible to install without establishing a proper connection. I also tried to install TWRP without PC, for this i need to root my device and flash TWRP img, so I started trying root I had used kingroot, kingoroot, towelroot and some more but failed to root, I am still trying to install TWRP can anyone help me in either of the process to install TWRP.
Click to expand...
Click to collapse
Getting your device connected is a very important stage, whether it is system,recovery or fastboot. From what I read , you can connsct through fasatboot, since you flashed cyanogen. Just flash TWRP 3.2.1 or so which is the latest, through fastboot:
fastboot flash recovery twrp.3.2.1 .img ( Remember the spaces, the name twrp.xxx.img should be same as you downloaded. If flash is successful, you can see twrp when you boot to recovery. Then flash supersu file and/or whichever rom you want.
Sorry for late answers.
I was lil busy and sorry for wrong address also.
You could get it from firmwarefile.com
I can't post link here but select yu yureka plus variant and download oldest CBP
Weird: I was just using it normally, it switched off and now it stays stuck on the Google logo; when entering recovery mode, I get TWRP"s splash screen and it stays there, so I cannot even recover.
Suggestions please??
Note 1: I'm pretty bad with this kind of stuff, need step-by-step instructions.
Note 2: rom is AOSP 7.1.2 but I guess is irrelevant, as even TWRP does not load.
Thanks in advance!!
Can you fastboot boot the TWRP recovery?
Hmmm dont know exactly what that means sorry; I mean I havent tried connecting it to the laptop and using thr ADB toolkit, but I can reset via Power+VolDown to the bootloader menu (? the android layind down and giving the option to StartSystem/ SwitchOff/ Restart/ RecoveryMode), and choosing RecoveyMode it tries to launch TWRP (it even shows the logo) but stays there on the splashscreen, doesn't quite manage to give me the TWRP menus
Someone?
AndDiSa said:
Can you fastboot boot the TWRP recovery?
Click to expand...
Click to collapse
let's see... I set in recovery mode, connect to the PC (does not recognise it), and with "fastboot boot twrp.img" it just sends/writes the file, the tab shows the Google logo with open lock, and then tries to launch Twrp, but as before, it just get stuck in the splashscreen "TeamWin Recovery Project 3.3.1.0" , so just the same.
Command "fastboot flash boot twrp.img" the same
Command "fastboot flash recovery twrp.img" the same
Command "adb devices" returns the list empty
Command "adb reboot recovery" returns "error: no devices / emulators found"
Command "fastboot oem unlock" returns "(bootloader) bootloader is already unlocked"
I tried running a tool called FirstAid (https://forum.xda-developers.com/devdb/project/dl/?id=16684) but does nothing for me
I'm lost, please help
Video and photos of the issue (device, not adb)
video: https://photos.app.goo.gl/GrFrmQhbyQeHVFZN7
Well, looking at your video it seems that there is no bootable ROM installed and also the recovery (for what ever reason) has some issues to start.
The fact, that you are able to boot into bootloader shows that at least it's not completely bricked ... but there's still the chance that the flash memory has some issues.
I would connect the device via usb with a PC and try to do a
fastboot boot <twrp-3.3.1-grouper.img>
to whether in that case the recovery is booting.
If this is successful, the next step would be re-flashing the recovery into the recovery partition and booing into recovery mode from the bootloader.
If this is successful, too, wiping and flashing a new ROM would be the last step.
I unlocked the bootloader, the FRP too.
Now I need to flash the TWRP image with the command "fastboot flash recoery_ramdisk twrp.img" because it is a partition A only.
Those are the steps I take:
1) connect USB the device
2) enable USB debugging
3) adb reboot bootloader
4) the phone boots with the fastboot screen
(it says PHONE unlocked, FRP unlocked)
5) I put the command: "fastboot flash recoery_ramdisk twrp.img" (I have twrp.img in the same folder as the adb)
6) the console gives me <waiting for the device>
I red around a lot, and in a lot of threads even here on XDA it says it's adriver issues, so I isntalled Universal ADB driver, then 15 seconds adb drivers, the n tried to downlowad the Hi Suite but it doesn't even start (I have Win 10)
Additional info:
The boot loader is unlocked, also in the settings (I used potatoNV method)
I have EMUI 5.0.3
Android version 7
Number model PRA-LX1
What to do guys?
cocclina said:
I unlocked the bootloader, the FRP too.
Now I need to flash the TWRP image with the command "fastboot flash recoery_ramdisk twrp.img" because it is a partition A only.
Those are the steps I take:
1) connect USB the device
2) enable USB debugging
3) adb reboot bootloader
4) the phone boots with the fastboot screen
(it says PHONE unlocked, FRP unlocked)
5) I put the command: "fastboot flash recoery_ramdisk twrp.img" (I have twrp.img in the same folder as the adb)
6) the console gives me <waiting for the device>
I red around a lot, and in a lot of threads even here on XDA it says it's adriver issues, so I isntalled Universal ADB driver, then 15 seconds adb drivers, the n tried to downlowad the Hi Suite but it doesn't even start (I have Win 10)
Additional info:
The boot loader is unlocked, also in the settings (I used potatoNV method)
I have EMUI 5.0.3
Android version 7
Number model PRA-LX1
What to do guys?
Click to expand...
Click to collapse
Hi There.
change you rcovery image file name to "twrp.img" and move them to c:/ partition.
then enter the command bellow : fastboot flash recovery c:/twrp.img
NOTICE : Of course, I installed twrp custom recovery on my huawei p8 gra-ul00 phone and im very regretted.
And you're doing this at your own risk.
Regards,