Related
I want to install cwm recovery in my canvas a1 for backup my current rom android 4.4.4.
I m going to install lollipop 5.1 I heard about some bug in lollipop so for my safety i want a backup.
I used minimal adb and fastboot for installing cwm.
But when i type the command "fastboot flash recovery recovery.img"
End hit enter
Then it show a error.
"Failed (remote download for partition 'recovery' is not allowed'
What should i do now?
http://forum.xda-developers.com/cro...oolbox-android-one-toolkit-one-click-t3030165
Go to this thread and follow the simple instructions...dnt go through such command prompts..when an easy way is available hit thanks if i helped
MaxySpark said:
I want to install cwm recovery in my canvas a1 for backup my current rom android 4.4.4.
I m going to install lollipop 5.1 I heard about some bug in lollipop so for my safety i want a backup.
I used minimal adb and fastboot for installing cwm.
But when i type the command "fastboot flash recovery recovery.img"
End hit enter
Then it show a error.
"Failed (remote download for partition 'recovery' is not allowed'
What should i do now?
Click to expand...
Click to collapse
Before flashing CWM recovery, you have to unlock the boot loader, using the command:
Code:
fastboot oem unlock
Then press Volume Up in phone to confirm.
Now you can flash.
Note: Unlocking bootloader formats the User data (/data partition), such as apps and other settings. Take a backup using Titanium Backup Tools, then proceed
Your recovery partition is locked.
1. Make yourself a developer (go to Settings -> About Phone -> Tap on Build until developer
2. In Developer options turn on Enable OEM unlock
3. Flash the new recovery, don forget to "fastboot oem unlock"
4. Important: don't allow phone to complete a normal reboot after flash. When rebooting, press Vol Up + Vol Down + Power to enter CWM recovery directly. Otherwise the stock recovery will replace CWM again.
When I type the command "fastboot oem unlock" and press enter, my phone displays a long-ish disclaimer text about the dangers of unlocking the bootloader, ending with the instruction to use Volume Up key to confirm ("YES, unlock...") or the Volume Down key to cancel ("NO, don't unlock..."). Pressing Volume Down works as expected: the line "returning to fastboot in 3secs" is displayed, followed by a return to fastboot. But pressing Volume UP seems to have NO EFFECT at all!! NOthing highlighted, no change in the screen, pressing power afterward does nothing. It is not a hardware problem of the Volume Up button either -- Volume Up/Down keys work in normal apps and in recovery mode just fine.
I was hoping that perhaps it just silently succeeded, but when i next try to flash the CWM recovery img, I still get 'sending recovery' OKAY but 'writing recovery' FAILED??
what do I do to get the volume UP to work while the phone in this mode??
BTW the phone is a Rook 4G phone from EE here in the UK. This is apparently the same as a ZTE Blade 3 A410 phone with carrier branding.
THANKS in advance for any help!
sbpetrack said:
When I type the command "fastboot oem unlock" and press enter, my phone displays a long-ish disclaimer text about the dangers of unlocking the bootloader, ending with the instruction to use Volume Up key to confirm ("YES, unlock...") or the Volume Down key to cancel ("NO, don't unlock..."). Pressing Volume Down works as expected: the line "returning to fastboot in 3secs" is displayed, followed by a return to fastboot. But pressing Volume UP seems to have NO EFFECT at all!! NOthing highlighted, no change in the screen, pressing power afterward does nothing. It is not a hardware problem of the Volume Up button either -- Volume Up/Down keys work in normal apps and in recovery mode just fine.
I was hoping that perhaps it just silently succeeded, but when i next try to flash the CWM recovery img, I still get 'sending recovery' OKAY but 'writing recovery' FAILED??
what do I do to get the volume UP to work while the phone in this mode??
BTW the phone is a Rook 4G phone from EE here in the UK. This is apparently the same as a ZTE Blade 3 A410 phone with carrier branding.
THANKS in advance for any help!
Click to expand...
Click to collapse
Hi, I have exactly the same situation!
No effect on Volume UP. I can't understand...
marc2800 said:
Hi, I have exactly the same situation!
No effect on Volume UP. I can't understand...
Click to expand...
Click to collapse
Absolutely identical experience here with the Alcatel One Touch Pop 3 - 5015x. I was following this tutorial http://forum.xda-developers.com/and...lcatel-one-touch-pop-s3-t3060092/post65430049, had a problem with the OEM, solved it by finding the top post on THIS thread and now I have the exact same issue as you two gentlemen. Any help would be appreciated, cus the phone seems bricked as it is. It's stuck in boot loop and receiving no input.
Thi is NOT the exact same issue as we have: you are stuck in a boot-loop; we have a version of fastboot which seems to have disabled the volumeUp button, thereby making it impossible to confirm our request to unlock the bootloader. e can only press VolumeDown (which cancels our request to unlock the bootloader).
i posted at http://forum.xda-developers.com/showpost.php?p=65462453&postcount=48 a suggestion for how to proceed in your case: just use SP Flash tools to reinstall a stock recovery image, and then use that recovery to install a complete stock ROM.
,BTW, Sir, when you say:
> ...with the Alcatel One Touch Pop 3 - 5015x. I ... had a problem with the OEM, solved it by finding the top post on THIS thread
note that the solution given in the top post of this thread is designed for Android One devices, and your Alcatel One Touch does NOT appear in the list of supported devices for that "fix." can't say it's entirely surprising that you would get into a bootloader problem if you apply top your phone a bootloader unlock solution for some random other platform!! LUck would not likely be with you when doing that.
zeta274 said:
Absolutely identical experience here with the Alcatel One Touch Pop 3 - 5015x. I was following this tutorial http://forum.xda-developers.com/and...lcatel-one-touch-pop-s3-t3060092/post65430049, had a problem with the OEM, solved it by finding the top post on THIS thread and now I have the exact same issue as you two gentlemen. Any help would be appreciated, cus the phone seems bricked as it is. It's stuck in boot loop and receiving no input.
Click to expand...
Click to collapse
I can't understand why volume down is working fine and not volume UP...
zeta274 said:
Absolutely identical experience here with the Alcatel One Touch Pop 3 - 5015x. I was following this tutorial http://forum.xda-developers.com/and...lcatel-one-touch-pop-s3-t3060092/post65430049, had a problem with the OEM, solved it by finding the top post on THIS thread and now I have the exact same issue as you two gentlemen. Any help would be appreciated, cus the phone seems bricked as it is. It's stuck in boot loop and receiving no input.
Click to expand...
Click to collapse
Go in bootloader mode, connect your phone to your computer and tell me what do you get if you tape in your console "fastboot devices"
I want to know the number before fastboot.. mine is strange and maybe not the original
MaxySpark said:
I want to install cwm recovery in my canvas a1 for backup my current rom android 4.4.4.
I m going to install lollipop 5.1 I heard about some bug in lollipop so for my safety i want a backup.
I used minimal adb and fastboot for installing cwm.
But when i type the command "fastboot flash recovery recovery.img"
End hit enter
Then it show a error.
"Failed (remote download for partition 'recovery' is not allowed'
What should i do now?
Click to expand...
Click to collapse
That is also my problem with my phone!
---------- Post added at 05:56 AM ---------- Previous post was at 05:54 AM ----------
GokulNC said:
Before flashing CWM recovery, you have to unlock the boot loader, using the command:
Code:
fastboot oem unlock
Then press Volume Up in phone to confirm.
Now you can flash.
Note: Unlocking bootloader formats the User data (/data partition), such as apps and other settings. Take a backup using Titanium Backup Tools, then proceed
Click to expand...
Click to collapse
Hi, I had done that fastboot oem unlock command and pressed Volume Up but nothing happened and my bootloader still locked could you help? Thanks, my phone is Starmobile UP HD MTK6582 :laugh:
GokulNC said:
Before flashing CWM recovery, you have to unlock the boot loader, using the command:
Code:
fastboot oem unlock
Then press Volume Up in phone to confirm.
Now you can flash.
Note: Unlocking bootloader formats the User data (/data partition), such as apps and other settings. Take a backup using Titanium Backup Tools, then proceed
Click to expand...
Click to collapse
really thanks:angel:
I can't
I have an error installing a ROM, partition x not allowed.
I can't go in recovery mode + I can't open my phone to enable usb debugging.
I don't have root & and I don't have my OEM unlocked.
How can I install my ROM for Asus Zenfone GO ZC500TG? :'( :'(
Anyone, please?!!
ADB devices allowed?
I have the same problem, but i just resolve it now. First, i've connected my phone in normal mode, then i opened cmd and wrote: adb devices, and a popup displayed in my phone to allow adb debug. I allowed and reboot to bootloader and follow all steps to unlock bootloader.
I also have problems, my phone is a polaroid turbo c4 plus and i cand get through the setup, so i can't install cwm and i am searching for methods to recover it, it's pretty hard since theres nothing online about it
For those that, like me, could not get driver recognition on the latest Win 10 x64 no matter what you tried. And ,yes, using every tutorial I could find on this and two "other Forums". Odin failed to see my device (still can't) Cydia impactor allows rebooting into fastboot and D/L but doesn't connect in either alt. mode. Yes, drivers all removed and replaced in varying states (usbdeview, etc.).
But ADB/Fastboot works!
Make sure you have your adb/fastboot drivers installed universally (Check this Fabulous Forum)
Download device-specific TWRP - I used this one for the 4gb version - https://www.dropbox.com/s/b7u3k1mgpppxlyx/recovery.img?dl=0
L.Shift-R. click in the folder you downloaded to (Open Command Window Here) - "adb devices" (to make sure device registers) then - "adb reboot bootloader" gets you into fastboot. - "fastoot boot {your-recovery-name}.img"
I got a fully functional TOUCH CAPABLE TWRP. Which I proceeded to load this - https://www.dropbox.com/s/j1owqv7mjkdpo75/UPDATE-SuperSU-v2.46.zip?dl=0 - and, VOILA! ROOT!!
I had similar issues with my laptop and drivers. Used a friend laptop in the end to "see" the phone and install twrp.
Sent from my S7 using Tapatalk
When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?
vaskovass said:
When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?
Click to expand...
Click to collapse
Hi there, I have the same issue. No success
I found a way, instead of volume up, use the home button this worked for me.. however after I unlocked the OEM and flashed TWRP the phone didn't want to boot anymore. It was stuck on Elephone logo with warning: "Orange State: The phone has been unlocked and can't be trusted. Your device will boot in 5s", however it didn't boot and stayed like that for almost an hour. Had to flash back the stock firmware to boot. Tried 1 more time the procedure to root but again the same. Maybe I do something wrong?
stock fw flash back
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!
dnsgtr said:
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!
Click to expand...
Click to collapse
I read somewhere the is a zip inside the update.zip & is that one that is flash able with twrp.
Have a look
During the main time I managed to flash the 0218 stock rom.
I still got the orange message but the phone finally boot. Then I just called the twrp recovery img via atb. I did nothing only touch the reboot in the twrp screen and since then "Orange status...." again.
May be the twrp recovery img is not the right one...
Bad command "fastoot boot {your-recovery-name}.img"
after OEM alow (informacion phone/compilacion number touch fast 9 times/access/alow oem)
fastboot oem unlock
"fastboot boot {your-recovery-name}.img" for me is fastboot boot recovery.img and all OK
bat still not working (phone not thrust unlocked bootloader cleaning data in 5..4..3..2..1.. and rebot)
I just bricked my phone :crying: :crying:
I wanna get back to the official rom, after trying android P (without make it work).
(the rom is from http://en.miui.com/download-354.html)
But I run the wrong script and take the flash_all_lock.img
And my device is stuck on android 8.1 bootloop (It boot, but i get an animated line loop ...)
Any ideas or tricks before i get it back to warranty ?
Thanks
Unlock bootloader and flash again. You can find a guide to unlock bootloader at the beginning of this guide.
BubuXP said:
Unlock bootloader and flash again. You can find a guide to unlock bootloader at the beginning of this guide.
Click to expand...
Click to collapse
But since I flashed the official rom with data whipe, I'm unable to go to dev option and enter OEM Unlocking .... And Fastboot respond me that my device is locked
Seems like my only option left is to boot into EDL mode ...
But seems fastboot oem edl does not work I don't lnow how to handle the problem
droopeur said:
Seems like my only option left is to boot into EDL mode ...
But seems fastboot oem edl does not work I don't lnow how to handle the problem
Click to expand...
Click to collapse
Have you tried to switch the active slot?
Try if it boots using
fastboot set_active a
or
fastboot set_active b
If not working, can you enter recovery (power on with Volume up button pressed)?
If you can enter recovery, hold down the power button for 3-5 seconds and then press and release the Volume up button, to make commands appear. Then your only hope is to install the OTA update zip from there (copy the OTA in a microSD card, there is a thread where you can find the link to the OTA zip).
In my opinion, "OEM unlocking" in developer options MUST be always keep active, because incidents like this could happen, and because even without modding, an OTA could go wrong resulting in your same situation.
I was in your same situation (OEM unlocking disabled and then I locked bootloader with a custom ROM installed) with a Nexus 5X.
I don't remember well how I fixed it, but I remember entering in Qualcomm download mode (should be the same EDL mode) and loading a file found after many hours of research in strange forums and sites.
BubuXP said:
Have you tried to switch the active slot?
Try if it boots using
fastboot set_active a
or
fastboot set_active b
Click to expand...
Click to collapse
In fact, both work, but my phone still stucked at the bootloader (infinite line animation in both cases).
BubuXP said:
If not working, can you enter recovery (power on with Volume up button pressed)?
If you can enter recovery, hold down the power button for 3-5 seconds and then press and release the Volume up button, to make commands appear. Then your only hope is to install the OTA update zip from there (copy the OTA in a microSD card, there is a thread where you can find the link to the OTA zip).
Click to expand...
Click to collapse
Yes I can enter recovery and I have already tried this, but I always end up with the error:
Code:
E: Unknow volume for path [/sideload/package.zip]
Verifying update package...
Update package verification took 17.3 s (result 0)
Installing update...
E:Error il /sideload/package.zip (Status 1)
Installation aborted
BubuXP said:
In my opinion, "OEM unlocking" in developer options MUST be always keep active, because incidents like this could happen, and because even without modding, an OTA could go wrong resulting in your same situation.
I was in your same situation (OEM unlocking disabled and then I locked bootloader with a custom ROM installed) with a Nexus 5X.
I don't remember well how I fixed it, but I remember entering in Qualcomm download mode (should be the same EDL mode) and loading a file found after many hours of research in strange forums and sites.
Click to expand...
Click to collapse
Yes of course !
But I revert to stock rom with Mi Flash and I click on Flash all and lock, since the telephone should have been "brand new" it should not have any problems but ...
I have to enter EDL mode, but don't know how to do it since modified fastboot executables does not activate it it just reboot the phone...
Deep flash cable may help but not shure if it works, or I may have to disassemble the device to find EDL pins...
after unlock bootloader type fastboot flashing unlock_critical and flash with miflash tool
LUNARIO said:
after unlock bootloader type fastboot flashing unlock_critical and flash with miflash tool
Click to expand...
Click to collapse
But since I can't activate OEM I can't unlock bootloader....
try this http://www.xiaomitool.com/ not sure if it works on our phone but maybe can unlock the bootloader so you can use miflash
Have you sideloaded the zip? I think it's better to copy the OTA zip to microSD than ADB sideload.
droopeur said:
I have to enter EDL mode, but don't know how to do it since modified fastboot executables does not activate it it just reboot the phone...
Deep flash cable may help but not shure if it works, or I may have to disassemble the device to find EDL pins...
Click to expand...
Click to collapse
There should be only two methods for entering EDL:
1- request authorization in en.miui.com forum. Sometimes the admins accept requests to give an account one EDL flash permission (but I don't know if it works with AndroidOne devices).
2- finding the test point in the phone's motherboard.
Hi guys,
i tried to install this twrp but it doesnt work...
so i searched on internet and i found another article, i tried to check the current partition and install in another way
for first:
fastboot getvar current-slot
after i do this
fastboot boot_b recovery.img
and then
fastboot set_active b
so nothing to do....but right now my MI A2 lite not boot.
i try again to check my partition but this time i have no replay.
i have unlocked bootloader but i cant go to recovery and i cant boot!!
someone can help me please?
I HAVE THE SAME PROBLEM
everything you said is completely simillar to mine. Can someone help us? Or did you already fix it? Please help me i need my phone working.
I have same problem fastboot flash but after that, it started to reboot automatically. The phone was automatically turning off and on. I again did a "clean all and lock" via miflash tool but still now, no result!
I can boot into recovery without having any problem. But when I boo to setup country date....etc, it starts its auto rebooting process,
Any help ?
droopeur said:
But since I can't activate OEM I can't unlock bootloader....
Click to expand...
Click to collapse
Same situation here. I am desperate!! Did you solve it?
Isso resolve
steledama said:
Same situation here. I am desperate!! Did you solve it?
Click to expand...
Click to collapse
gadgetsfarm.com/download-mi-a2-lite-fastboot-rom-v9-6-4-download/[/url]
How to unbrick?
Hey guys. I bricked my Mi2 Lite as well. Is there any step by step way to unbrick?
had the same problem, was stuck in the bootloop even after I flashed img with MiFlash! NOTE: MY BOOTLOADER WAS UNLOCKED!!! (LUCKLY I DID NOT TRIED FLASH ALL AND UNLOCK!)
headed to this thread
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
did not work, I get error saying FAILED
but after i used
Code:
fastboot oem edl
I went to MiFlash and used "Clean all" option (again note DON'T use "Clean all and lock"!!!). It took around 5 minutes to flash and my notif. light blinked whole the time. After it say "Success" I was able to normaly boot the phone again
Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.
Hi, where i can find MI A2 Lite Tool Kit? i open my device and i can put in EDL mode., my computer detect my pone in EDL mode, but i can not know do.
I like bypass FRP, can anybody help me
Thanks.
mr_techno said:
Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.
Click to expand...
Click to collapse
Hi all,
I also had same problem and I just resolve it.
My phone was in bootloop mode after stock rom flashing...
You don't need apply "fastboot oem edl" !
Just be sure your device is unlocked.
Download first stock rom (V9.6.4.0.ODLMIFF Firmware for Mi A2 Lite). If you flash last ROM, it don't work.
Flash it with XiaoMiFlash tool (don't forget to enable "Clean All") in bottom of the tool.
After reboot, you can apply OTA updates.
Enjoy !
Hello!
I try to unlock my bootloader with magisk but it does not work.
I have tried this in the picture and in the other is the result.
What did i do wrong?
Best regards
peter
Hello!
Has nobody an idea?
Best regards
peter
To unlock Bootloader:
adb reboot bootloader
The device will now boot into the bootloader and say
Waiting for fastboot command...
Input the following to unlock the bootloader:
fastboot flashing unlock
You will be prompted on the tablet screen with a warning about unlocking the bootloader.
Press the power button to unlock the bootloader.
The device will reboot and say "Bootloader is unlocked and OS verification is OFF. Device will continue booting in 30 seconds." You will also hear an audible beep. You will then see some spinny stuff. This is the userdata being formatted.
When complete, the device will boot back into the bootloader and say
Waiting for fastboot command...
Boot back into Android by inputting:
fastboot reboot
Your Pixel C will be reset.
Hello!
Thanks for your help. But i see on the pc only the information "< waiting for device >! Nothing else happend.
On the pixel is not "warning" or anything else.
Can anyone help.
Best regards
Peter
Do you have Developer options in Settings?
I not then look it up and do what you need to get it.
Then set "USB debugging"
Yes i have done!
best regards
peter
m+a+r+k said:
Do you have Developer options in Settings?
I not then look it up and do what you need to get it.
Then set "USB debugging"
Click to expand...
Click to collapse
I have done developer options done!
But nothing works.
Did anyone have an idea?
Best regards
peter
hello!
I changed the driver!
Now it works
thanks for the help!
best regards
peter
That was about to be my next suggestion
Hello Mark!
Everthing is fine now!
But it is normal that when i start the pixel it need 30sec. bevor it starts and i flash the recovery 3 times but when i start the pixel with "loundness up and power on" there is no recovery menue.
What can i do?
Best regards
peter
11.10.2018 @Mark! Now it works! I found the way for the TWRP. Thanks!
Best regards
peter
There is nothing any one can do about the 30s delay in starting I'm afraid.
I only ever see that when I reflash every month the latest factory image security update so I can live with it.
Flashing TWRP is easy.
Install Custom Recovery:
Input the following:
adb reboot bootloader
The device will now boot into the bootloader and say
Waiting for fastboot command...
With the Pixel C in the Fastboot bootloader and the recovery file in your ADB directory, input the following:
fastboot flash recovery TWRP-3.2.3-0-dragon.img
Immediately reboot to TWRP Recovery by 'Power + Volume down' until screen turns off, keep pressing Volume down to boot into Coreboot Bootloader. Navigate to 'Reboot into Android Recovery' with Volume down and then press Power button to select.
In TWRP when asked for encryption password, type your password.
m+a+r+k said:
There is nothing any one can do about the 30s delay in starting I'm afraid.
I only ever see that when I reflash every month the latest factory image security update so I can live with it.
Flashing TWRP is easy.
Install Custom Recovery:
Input the following:
adb reboot-bootloader
The device will now boot into the bootloader and say
Waiting for fastboot command...
With the Pixel C in the Fastboot bootloader and the recovery file in your ADB directory, input the following:
fastboot flash recovery TWRP-3.2.3-0-dragon.img
Immediately reboot to TWRP Recovery by 'Power + Volume down' until screen turns off, keep pressing Volume down to boot into Coreboot Bootloader. Navigate to 'Reboot into Android Recovery' with Volume down and then press Power button to select.
In TWRP when asked for encryption password, type your password.
Click to expand...
Click to collapse
Hello Mark!
If i do this then i am going to "save mode" not to recovery.
I fund no way.
Best regards
peter
I'm not sure I understand.
Are you saying that when you select Power + Volume Down and then 'Reboot into Android Recovery' it goes into Safe Mode?
Does TWRP appear to install OK when you fastboot flash it?
m+a+r+k said:
I'm not sure I understand.
Are you saying that when you select Power + Volume Down and then 'Reboot into Android Recovery' it goes into Safe Mode?
Does TWRP appear to install OK when you fastboot flash it?
Click to expand...
Click to collapse
Yes it is!!!
Thats weard!
best regards
peter
Never seen or read about that before.
Flash entire factory image and start again?
m+a+r+k said:
Never seen or read about that before.
Flash entire factory image and start again?
Click to expand...
Click to collapse
Hello there @m+a+r+k,
I noticed that your signature indicates that you have a Chrome Pixel C, with Stock Oreo 8.1 rooted. I purchased my Pixel C back in late 2016 and JUST NOW opened the package for the first time ever LOL. What can I say, work has been keeping me extremely busy.
Anyway, as I normally do with my Android devices (Usually before purchasing them), I start looking at how solid is the 'Alternative Dev Community', for things like rooting, custom recovery, custom kernels, custom roms, etc.
After doing some searching and reading, I was beginning to lean towards just rooting and installing the custom recovery but keeping everything stock. Then I saw your signature.
If possible, what advice can you provide me with regarding this tablet and the current 'Alternative Dev' community?
There doesn't appear to be that many choices with Custom ROMs and so forth. Any tips would be greatly appreciated.
Thank you in advance!!
BJ
I'd just root it and install TWRP.
I'm happy with 8.1. Every month I download the new factory image flash system.img, vendor.img and boot.img to update it.
I don't know what your experience of this is, I can put instructions up here if you need them.
I can't believe you had a Pixel C sitting in its box all this time! You were so busy you didn't even have half an hour to unpack it out of curiosity?
m+a+r+k said:
I'd just root it and install TWRP.
I'm happy with 8.1. Every month I download the new factory image flash system.img, vendor.img and boot.img to update it.
I don't know what your experience of this is, I can put instructions up here if you need them.
I can't believe you had a Pixel C sitting in its box all this time! You were so busy you didn't even have half an hour to unpack it out of curiosity?
Click to expand...
Click to collapse
Hey there @m+a+r+k,
Yes, if you could please post some instructions, that would be awesome. That way, I don't end up trying to follow outdated material. Also yes...I've been extremely busy even relocated to another State during this time LOL. I even have the following NAS still sitting in the box for the past year, brand-new and unopened: https://www.qnap.com/en-us/product/tvs-473 . Haha I even have the following Firewall waiting for me for the last 6 months: https://www.netgate.com/solutions/pfsense/sg-3100.html.
I haven't even had the chance to update my XDA signature on here LOL
BJ
Apologies if I'm trying to teach you to suck eggs.
I make no promises, this worked for me. I can't be held responsible for any damage (unlikely) caused when attempting this.
You will need the latest (important) adb and fastboot package. You don't need the rest of the SDK Platform Tools.
https://developer.android.com/studio/releases/platform-tools#download and choose which platform you have. Unpack and copy folder to Program Files (x86) or whatever.
Download latest TWRP from this forum
Download Magisk 17.2 from https://forum.xda-developers.com/apps/magisk
Enable developer mode
Go to Settings > About tablet
Tap on "Build Number" 7 times until it says "You are now a developer"
Enable OEM Unlocking
Go to Settings > Developer options
Enable "OEM Unlocking"
Tap on Enable when a disclaimer pops up
Enable USB Debugging (ADB)
Go to Settings > Developer options
Enable "USB debugging"
Tap on OK when prompted with a disclaimer
If the ADB USB driver has been installed, you will see a popup that says "The computer's RSA key fingerprint is: xx:xx:xx:xx(blah blah)"
Check the box next to "Always allow from this computer"
Tap on OK
Unlock Bootloader
Connect Pixel C to PC with USB power cable.
PC should install drivers (fingers crossed).
Open a Command Prompt window so that it points to the SDK Platform Tools folder.
[Type commands in blue]
Type
adb devices
Do you get a response with a number? If not you don't have a connection and drivers may not be installed or USB Debugging enabled. Windows 7 and 10 recognized Pixel C OK for me.
adb reboot bootloader
The device will now boot into the bootloader and say "Waiting for fastboot command..."
Input the following to unlock the bootloader:
fastboot flashing unlock
You will be prompted on the tablet screen with a warning about unlocking the bootloader.
Press the power button to unlock the bootloader.
The device will reboot and say "Bootloader is unlocked and OS verification is OFF. Device will continue booting in 30 seconds." You will also hear an audible beep. You will then see some spinny stuff. This is the userdata being formatted.
When complete, the device will boot back into the bootloader and say "Waiting for fastboot command..."
Boot back into Android by inputting:
fastboot reboot
Your Pixel C will be reset, so you will need to re-enable USB debugging.
Connect to your wireless network, set up your lock screen password and then skip past everything else in the initial setup, as all of this setup info may be wiped again later on.
Enable "USB Debugging" again.
When you are happy copy the Magisk.zip file to Pixel C Downloads folder.
Install Custom Recovery
Input the following:
adb reboot bootloader
The device will now boot into the bootloader and say "Waiting for fastboot command..."
With the Pixel C in the Fastboot bootloader and the TWRP recovery file in your ADB directory, input the following:
fastboot flash recovery TWRP-3.2.1-0-dragon.img <or whatever the name of the TWRP file>
If OK: THIS IS IMPORTANT If you reboot the device back into Android, it will write over the custom recovery with the stock one. Reboot to TWRP Recovery by holding down "Power button + Volume Down button" until screen turns off, keep pressing Volume Down to boot into Coreboot Bootloader. Navigate to "Reboot into Android Recovery" with Volume Down button and then press Power button to select.
You should now boot into TWRP. You'll be asked for encryption password - it is your lock screen password or if no password has been set use "default_password".
You can now play with settings in TWRP (colour, clock etc).
Make a Nandroid Backup.
Install root
In TWRP select Install menu and select the Magisk zip file. Drag the bar to the right. When finished Wipe Caches.
At main menu Reboot to System and set up your Pixel C.
Install Magisk Manager apk.
Install one of the many free Root Checker apps to check all is OK.
Phew...
I've probably missed something...
Thanks to b1ggjoe and gargamon for being my guinea pigs on this script
m+a+r+k said:
Apologies if I'm trying to teach you to suck eggs.
I make no promises, this worked for me. I can't be held responsible for any damage (unlikely) caused when attempting this.
You will need the latest (important) adb and fasttboot package. You don't need the rest of the SDK Platform Tools.
https://developer.android.com/studio/releases/platform-tools#download and choose which platform you have. Unpack and copy folder to Program Files (x86) or whatever.
Download latest TWRP from this forum
Download Magisk 17.2 from https://forum.xda-developers.com/apps/magisk
Enable developer mode
Go to Settings > About tablet
Tap on "Build Number" 7 times until it says "You are now a developer"
Enable OEM Unlocking
Go to Settings > Developer options
Enable "OEM Unlocking"
Tap on Enable when a disclaimer pops up
Enable USB Debugging (ADB)
Go to Settings > Developer options
Enable "USB debugging"
Tap on OK when prompted with a disclaimer
If the ADB USB driver has been installed, you will see a popup that says "The computer's RSA key fingerprint is: xx:xx:xx:xx(blah blah)"
Check the box next to "Always allow from this computer"
Tap on OK
Unlock Bootloader
Open a Command Prompt window so that it points to the SDK Platform Tools folder. [Type commands in blue]
adb devices
Do you get a response with a number? If not you don't have a connection and drivers may not be installed or USB Debugging enabled. Windows 7 and 10 recognized Pixel C OK for me.
adb reboot bootloader
The device will now boot into the bootloader and say "Waiting for fastboot command..."
Input the following to unlock the bootloader:
fastboot flashing unlock
You will be prompted on the tablet screen with a warning about unlocking the bootloader.
Press the power button to unlock the bootloader.
The device will reboot and say "Bootloader is unlocked and OS verification is OFF. Device will continue booting in 30 seconds." You will also hear an audible beep. You will then see some spinny stuff. This is the userdata being formatted.
When complete, the device will boot back into the bootloader and say "Waiting for fastboot command..."
Boot back into Android by inputting:
fastboot reboot
Your Pixel C will be reset, so you will need to re-enable USB debugging.
Connect to your wireless network, set up your lock screen password and then skip past everything else in the initial setup, as all of this setup info may be wiped again later on. Enable "USB Debugging again.
Install Custom Recovery
Input the following:
adb reboot bootloader
The device will now boot into the bootloader and say "Waiting for fastboot command..."
With the Pixel C in the Fastboot bootloader and the TWRP recovery file in your ADB directory, input the following:
fastboot flash recovery TWRP-3.2.1-0-dragon.img <or whatever the name of the TWRP file>
If OK: THIS IS IMPORTANT If you reboot the device back into Android, it will write over the custom recovery with the stock one. Reboot to TWRP Recovery by holding down "Power button + Volume Down button" until screen turns off, keep pressing Volume Down to boot into Coreboot Bootloader. Navigate to "Reboot into Android Recovery" with Volume Down button and then press Power button to select.
You should now boot into TWRP. You'll be asked for encryption password - it is your lock screen password or if not set "default_password".
You can now play with settings in TWRP and Reboot into System and set up your Pixel C.
At some point when you are happy copy the Magisk.zip file to Downloads folder.
Install root
Reboot into recovery
adb reboot recovery
or Reboot to TWRP Recovery by holding down "Power button + Volume Down button" until screen turns off, keep pressing Volume Down to boot into Coreboot Bootloader. Navigate to "Reboot into Android Recovery" with Volume Down button and then press Power button to select.
In TWRP select Install menu and select the Magisk zip file. Drag the bar to the right. When finished Wipe Caches.
At main menu Reboot to System.
Install Magisk Manager apk.
Phew...
I've probably missed something...
Click to expand...
Click to collapse
Thank you Sir!!!!!!! Ok, I will try this out this evening right after work...can't wait!!
Thanks again,
BJ
I was trying to install the google camera and then relocking the bootloader.
i uninstalled magisk manager and in the adb command prompt terminal i typed fastboot oem lock and my phone displays system has been destroyed.
please help as fast as possible.
fayadfyzer said:
I was trying to install the google camera and then relocking the bootloader.
i uninstalled magisk manager and in the adb command prompt terminal i typed fastboot oem lock and my phone displays system has been destroyed.
please help as fast as possible.
Click to expand...
Click to collapse
Flash stock rom with mi flash but before you have to unlock again bootloader
HTCDevil said:
Flash stock rom with mi flash but before you have to unlock again bootloader
Click to expand...
Click to collapse
I have the same problem, so how can I unlock the bootloader being that it has no system for this ?
ItaloIanetta said:
I have the same problem, so how can I unlock the bootloader being that it has no system for this ?
Click to expand...
Click to collapse
So if you cannot boot to bootloader by pressing power and volume down at startup, you can try to enter recovery by pressing power and volume up. Then if it says no command hold the power button and press volume up one time. Now you should enter recovery. then from here you can try to enter bootloader.
Then flash your image via Miflash
TJ1999 said:
So if you cannot boot to bootloader by pressing power and volume down at startup, you can try to enter recovery by pressing power and volume up. Then if it says no command hold the power button and press volume up one time. Now you should enter recovery. then from here you can try to enter bootloader.
Then flash your image via Miflash
Click to expand...
Click to collapse
the point it is, how can i flash via MiFlash, even they request the bootloader unlocked, when I begin the flash, they show the error, that nothing can do because the bootloader are locked, the program can't do nothing, i open device, initializing the phone on EDL mode, but, when flash system is done, from edl mode, they stuck on boot loop.
---------- Post added 3rd November 2018 at 12:06 AM ---------- Previous post was 2nd November 2018 at 11:49 PM ----------
TJ1999 said:
So if you cannot boot to bootloader by pressing power and volume down at startup, you can try to enter recovery by pressing power and volume up. Then if it says no command hold the power button and press volume up one time. Now you should enter recovery. then from here you can try to enter bootloader.
Then flash your image via Miflash
Click to expand...
Click to collapse
I can enter the fastboot mode, I can enter the recovery mode, but the device does not respond to anything and gets bootloop
Ok, you said you can enter edl mode even the bootloader is locked right?
How did you do this? You said you opened device, did you short the two test points. I have a similar Problem.
Seems like there are other Posts with different problems at the beginning which are now facing the same problem as we do, after some flashing:
https://forum.xda-developers.com/mi-a2-lite/help/mi-a2-lite-suddenly-damaged-t3861467 (my Problem)
https://forum.xda-developers.com/mi-a2-lite/how-to/xiaomi-mi-a2-lite-hard-brick-t3861576
fayadfyzer said:
I was trying to install the google camera and then relocking the bootloader.
i uninstalled magisk manager and in the adb command prompt terminal i typed fastboot oem lock and my phone displays system has been destroyed.
please help as fast as possible.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=78066196&postcount=6
EASY FIX for this problem!...go again into fastboot mode....POWER button + Volume DOWN - in the command prompt on the PC type: fastboot oem unlock
system erases all the data and starts again had the same problem! i installed magisk to enable camera2pi, so today i got the mi mix 3 and i thought hmm lets lock the bootloader mi a2 lite and erase all the data so i can pass it further to my mum and she´ll get fresh updates! unfortunately, when i did fastboot oem lock, it said "system .blablabla..destroyed" ! Now everything workds fine again!
dappolino said:
EASY FIX for this problem!...go again into fastboot mode....POWER button + Volume DOWN - in the command prompt on the PC type: fastboot oem unlock
system erases all the data and starts again had the same problem! i installed magisk to enable camera2pi, so today i got the mi mix 3 and i thought hmm lets lock the bootloader mi a2 lite and erase all the data so i can pass it further to my mum and she´ll get fresh updates! unfortunately, when i did fastboot oem lock, it said "system .blablabla..destroyed" ! Now everything workds fine again!
Click to expand...
Click to collapse
You can also flash stock rom with Miflash tool and choose the option at the right bottom to "clean all and lock" after flashing you've got stock rom and relocked bootloader