OK. This is for those who are not so great or somewhat new to flashing stuff; if you're already awesome at this you will most likely not find this thread helpful. It took me a long time to find the answers I was looking for so I thought I'd share my results.
My issue: I was trying to update to Android 5.01 (Nexus 6, 5.0, encrypted, rooted)
I got the OTA notification, which after I dismissed it, could not get it back. However, I found out, again after much reading that even if I had caught it, it would not have worked since Lollipop does a system check before it updates and because I was rooted would not have worked. I also tried just capturing the OTA update from droidlife and again, once I got to the sideload phase (either through wugfresh, or just standard minimal adb).
So... searched and searched, I didn't want to lose my user data, since it's tough to get everything just the way I like it. I finally found a solution.
I downloaded Wugfresh (mainly because the application is great in terms of getting the drivers under control, I was able to get it installed and working on two comptuers).
Next, downloaded the minimal adb and fastboot stuff, it's pretty awesome, because after this process you really feel like you're getting a grasp on customizing android.
http://forum.xda-developers.com/showthread.php?t=2317790
Next, download the actual install image from google (nexus 6, 5.01)
http://forum.xda-developers.com/showthread.php?t=2317790
Once you get that file, you'll need a nice zip program like 7zip: You want to go into the file and get 5 files:
radio-shamu-d4.0-9625-02.55.04.img (I renamed it to radio.img)
bootloader-shamu-moto-apq8084-71.05.img (I renamed it to bootloader.img
then in the image-shamu-lrx22c.zip file, retrieve these three files:
recovery.img, system.img and boot.img
Now, take a breath, get a drink and prepare for the next part.
Boot into fastboot mode (power off phone, then once it's off, hold down power and volume DOWN)
Pull up your minimal adb and fastboot:
type:
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Very important next step:
fastboot reboot-bootloader
Next:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
This first boot will take quite a bit but it WILL come up, and optimize all your apps and settings (nothing lost)
Now, because I was in the mood to flash stuff, I rebooted into fastboot mode again (after I downloaded CF-auto root and extracted the files for 5.0)
renamed the cf-autoroot blah blah blah to just root.img
then:
flashboot boot root.img, it ran and rebooted, bam rerooted, none of the my data lost. Hope this helps someone.
Good to hear you've got it sorted. This has been covered on many occasions in other threads though.
Hello I am pretty new to flashing and been looking around to find a way to flash 5.0.1 on my N6 w/o having all my data wiped. Like you i got the OTA update and i attempted to install it even tho i had root and i read on forums that it would fail. After it finished downloading it rebooted my device to shortly fail right after. The OTA update has never popped up since and i been waiting for it to come back up (2 days now) so i can attempt to install it after i unroot.
Thanks for your detailed instructions and for assuring me that you were successful w/o having to lose data. I will flash my N6 as soon as i get home!
Amos91 said:
Good to hear you've got it sorted. This has been covered on many occasions in other threads though.
Click to expand...
Click to collapse
people like you need to go away - i had the same thought, but did i feel so compelled to bash the OP? As far as i'm concerned, there will always be new people around with new nexus devices and what the OP laid out clearly addressed many threads that popped up over the last week regarding 5.0.1. Even though i didn't need the help, thanks OP for sharing.
mb3030 said:
people like you need to go away - i had the same thought, but did i feel so compelled to bash the OP? As far as i'm concerned, there will always be new people around with new nexus devices and what the OP laid out clearly addressed many threads that popped up over the last week regarding 5.0.1. Even though i didn't need the help, thanks OP for sharing.
Click to expand...
Click to collapse
Not sure I can see how I bashed the OP. I could of been considerably more brash than that and meerly said whilst it was good he got it working it has been covered.
Whilst I agree the information is useful there has to be some kind of limit to duplication.
I'm not a robot
firestarter44 said:
Next, download the actual install image from google (nexus 6, 5.01)
http://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
Can someone please verify the url to the image (or direct me to a directory of images)?
I believe it is: https://developers.google.com/android/nexus/images#hammerheadlrx22c but I'm a newbie so I prefer someone who knows verify this.
CodeWarrior4Life said:
Can someone please verify the url to the image (or direct me to a directory of images)?
Click to expand...
Click to collapse
if you go to google, and search for nexus factory img, itll be the very first link https://developers.google.com/android/nexus/images
Instead of using fastboot manually since you installed wug's you could have used it to flash each image and not have to type it all out. It's under the advanced button
xxfwmxx said:
Instead of using fastboot manually since you installed wug's you could have used it to flash each image and not have to type it all out. It's under the advanced button
Click to expand...
Click to collapse
I tried to flash in Wugs and I was able to flash the first two files "fastboot flash bootloader bootloader.img and fastboot flash radio radio.img and fastboot reboot-bootloader . Each time when you flash one, it reboots. When I tried to flash the 3rd file, the fastboot flash recovery recovery.img, it gave me an error saying it cant find my device. I manually typed out tye commands in fastboot and it worked fine.
Also, for folks like me that don't often use the commants, make sure when you unzip your files, if you are using the commands with fastboot, that you put the files in the same directory as Minimal ADB and fastboot. That is my help to everyone! Thanks for the tutorial!!!!
This helped me out a lot!!! Thanks =D
I'd have to agree with mb3030. I searched multiple threads as well as Google to find specific information regarding the Nexus 6 going from 5.0 ==> 5.0.1 (while encrypted) and found no such information until this popped up. While I've been doing this for years now, it's still helpful finding a thread this specific to double check I'm doing things right. I never understood why XDA was so harsh on reposts. I would personally rather have a thousand different threads all saying the same thing from different members as this seems to be the best way to come to a general consensus of the "right" way to do something. It's a typical scientific approach to conduct multiple studies in order to verify information.
Bloody brilliant worked like a charm THANKS!!!!!!!!
So there isn't a stock rooted flashable zip for 5.0.1
Thank you for this awesome guide, worked all well.
will this be the same procedure for 5.1 or will we have to see?
Greetings,
Elmar.
Just wanted to say thanks for this thread! I, too, searched, trying to find this information and never found anything this simple and straightforward. Exactly what I was looking for.
So I've followed the directions and got all the way to flashing the system and it seems to be stuck on "sending sparse system". It already did a "sending sparse system" and followed with "writing system". It sounds like it's trying to send a write the system file in chunks instead of all at once. Am I right? Is it supposed to do this? If I back out now, am I hosed?
aaronmcd1214 said:
So I've followed the directions and got all the way to flashing the system and it seems to be stuck on "sending sparse system". It already did a "sending sparse system" and followed with "writing system". It sounds like it's trying to send a write the system file in chunks instead of all at once. Am I right? Is it supposed to do this? If I back out now, am I hosed?
Click to expand...
Click to collapse
Yes it sends it in chunks. Just let it keep going it will work out fine just takes a bit longer than the other IMG files
The Tig using Tapatalk
the factory image link is not correct
the factory image link is not correct
ncelover said:
the factory image link is not correct
Click to expand...
Click to collapse
The correct link is https://developers.google.com/android/nexus/images
Look for the 5.0.1 image for Nexus 6 "Shamu"
The Tig using Tapatalk
Everything works fine until I boot into fastboot mode and then suddenly it can't see the device anymore. Wugfresh works and can see the device in normal mode, but once I pop it into fastboot mode it can't find it anymore either.
Anyone have any ideas?
Related
Hello today I attempted something that I thought was going to be a quick video tutorial fix. I tried Rooting my HTC one. I followed several guides and read many posts I easily managed to unlock my phone. The problem started when trying to flash the recovery onto my phone, first I tried through commands: fastboot flash recovery and I received the error (FAILED data transfer failure unknown error) I've searched for 7 hours looking for a fix. Since I cant root reverting back to a fresh install is impossible, I cant find a RUU for telus, (I live in canada). I just don't know what to do, when I try to flash anything my bootloader freeze, drivers are up to date, tried restarting computer. Used One_M7_All-In-One_Kit_v1.0 doesn't work. This is a nightmare come save me before I jump off a cliff.
EDIT: What I did from beginning was followed this video "How to Root the HTC One-FlamingArio"to the point where you try and flash the recovery fastboot. That didnt work so after trying to fix that I tried How To Root HTC One & Unlock Bootloader - Easiest & User Friendly- The smoking Android ( super boot a 1 click install) that made my bootloader screen turn to tampered. after that I tried One_M7_All-In-One_Kit_v1.
Note in all in one kit I did erase cache and standard recovery works fine, I've re-installed it may times.
Cant post links yet but I gave video names.
EDIT: when I do the cmd fastboot devices my device shows up when I do adb devices nothing shows up could this be part of the problem?
Thank you all for your help, I re-installed all the programs on my laptop and redid all the steps and it worked. Bye!
Try this in ABD fastboot erase cache then flash the recovery again i hope this helps:fingers-crossed:
What did you do from the beginning? Could you post a step by step traceback of what got you to this point? Let's see if you missed any steps
Tonberry23 said:
Hello today I attempted something that I thought was going to be a quick video tutorial fix. I tried Rooting my HTC one. I followed several guides and read many posts I easily managed to unlock my phone. The problem started when trying to flash the recovery onto my phone, first I tried through commands: fastboot flash recovery and I received the error (FAILED data transfer failure unknown error) I've searched for 7 hours looking for a fix. Since I cant root reverting back to a fresh install is impossible, I cant find a RUU for telus, (I live in canada). I just don't know what to do, when I try to flash anything my bootloader freeze, drivers are up to date, tried restarting computer. Used One_M7_All-In-One_Kit_v1.0 doesn't work. This is a nightmare come save me before I jump off a cliff.
Click to expand...
Click to collapse
Keep an eye on this thread http://forum.xda-developers.com/showthread.php?t=2302870
Many people are looking for the Telus RUU.
Can you still access standard recovery? If so try reverting to factory settings (all data will be lost) and try to boot.
If you can get it to boot you should have more luck in trying to root your device.
I know that I had some issue's trying to get root on my device. But once I got S-off with revone, I was able to install root no problem.
ArmedandDangerous said:
What did you do from the beginning? Could you post a step by step traceback of what got you to this point? Let's see if you missed any steps
Click to expand...
Click to collapse
But I would agree, if you can post the steps you have taken so we know where the bottleneck is.
Hope this helps you out bud
Still need help
Tonberry23 said:
Still need help
Click to expand...
Click to collapse
Nice to see you sorted it
Assuming you have actually flashed a recovery image to your device, you will then need to push a ROM to your sd card so that you can flash it in recovery.
Just do the following:
1. I am guessing you have the HTC drivers installed on your PC.
2. Download the attached adb.zip and unzip it to a folder on your C drive and call the folder whatever you like.
3. Boot your device into recovery and plug it in to a powered USB port on your PC.
4. Navigate to the folder that you just created on your PC and copy your ROM zip into it. rename the ROM zip to 'rom.zip' to make life easy.
5. Inside the folder, press and hold the shift key and right click in a blank part of the window and select 'Open command window here' (screenshot attached).
6. Type 'adb push rom.zip /sdcard' (don't use the quote marks)
7. Press 'enter'
8. Once the zip has finished being pushed to your sdcard, you can reboot into recovery and then flash it as normal.
EDIT: That will teach me not to read to the very end of a post. I'll leave this here for someone else.
Hey everyone, so tonight I got the 4.4 ota on my N7, I am unlocked and rooted but stock everything including recovery.
After updating, my N7 keeps going to stalk recovery and that's it.
I know I can just reflash everything but I have a few very important files. Is there a way to reflash 4.3 without losing data or accessing the data partition while soft bricked so I can recovery my files?
I may be wrong, but can't you reflash your phone as long as you don't replace the userdata.img through fastboot to retain the same information? I could be wrong.
chrisinsocalif said:
I may be wrong, but can't you reflash your phone as long as you don't replace the userdata.img through fastboot to retain the same information? I could be wrong.
Click to expand...
Click to collapse
I'm not sure. I'd like to have this confirmed before I do anything. It's not urgent as the due date on my prgect isn't for another couple of weeks. But thanks. I'll look at that as a last resort.
Is it one file or multiple files you are trying to access? Have you tried to pull them using adb to your pc? I do not know how to do it, but I am sure there is a guide somewhere. Or try a phone backup using fastboot then unpack it on your desktop and get the files you need. Again, I am not good with phones, just throwing out idea's.
chrisinsocalif said:
Is it one file or multiple files you are trying to access? Have you tried to pull them using adb to your pc? I do not know how to do it, but I am sure there is a guide somewhere. Or try a phone backup using fastboot then unpack it on your desktop and get the files you need. Again, I am not good with phones, just throwing out idea's.
Click to expand...
Click to collapse
ADB or Wugs root kit don't see my Nexus 7 as it keeps rebooting to the dead droid and I know I don't have it set for debugging. Guess I'm screwed.
When you say "dead droid", you're referring to fastboot mode, right? (Android icon with a bunch of text below it, starting with "Fastboot Mode" in red.)
If you have fastboot, you can flash TWRP Recovery 2.6.3.0. Download it from Team Win's site (Google it). Then:
fastboot flash recovery openrecovery-twrp-2.6.3.0-grouper.img
fastboot reboot-bootloader
Use the Volume keys to select "Recovery Mode" and hit Power. Once you see the TWRP menu, you should have adb root access automatically. Connect tablet to USB, and use adb pull to download the contents of /sdcard:
adb pull /sdcard /dumphere
Replace "dumphere" with whatever directory you want to dump to. I'm sure there's better guides and explanations for this, but this is the quick version.
I guess you could reflash stock recovery afterwards, but I can't think of a reason why you'd want to. It's not like it's that useful.
As a rule of thumb, you should at least know how to get around a command line, and use adb and fastboot before mucking around with your tablet.
-XCN-
P.S. I could be mistaken, but I don't think internal storage (which is /sdcard, or /data/media) is overwritten when you flash a ROM. Obviously, backup first before trying.
Hello everyone, about five hours ago I was going through the process of rooting my Moto X 2014 Pure (UK). Unfortunately it seems to be stuck in a boot loop. I've crawled through forums but to no avail. Now it's 6:00am and I'm having a slight mental breakdown and would really appreciate some help.
notes:
-The phone stays stuck on the watery 'M' logo that appears after the boot animation.
-Unlocking the bootloader went fine
-had trouble installing the android SDK since I ran out of space on my hard-drive, however the installation log notes that the necessary files were successfully downloaded after I made some space.
-I'm not running TWRP or any equivalent. The only thing I can access is the standard fastboot screen thing.
-I think made two errors with my first attempt at rooting: I forgot to type 'boot' after fastboot and I also hadn't uncompressed the zip folder that the img was contained in (it was CF Root incidentally). The command terminal came back with information alluding to it having done something but the device didn't reboot, so i'm unsure if it did.
-I tried to rectify this by installing different root imgs but the phone still won't boot.
I'm really unsure as to what to do. My guess is that I need to sideload a factory img of some sort. I've sent of for the official img from the Motorola website and am anxiously awaiting a reply but I wondered if anyone knew of any alternatives? All this hassle just so I could run some xposed modules :crying:
SexyEgg said:
Hello everyone, about five hours ago I was going through the process of rooting my Moto X 2014 Pure (UK). Unfortunately it seems to be stuck in a boot loop. I've crawled through forums but to no avail. Now it's 6:00am and I'm having a slight mental breakdown and would really appreciate some help.
notes:
-The phone stays stuck on the watery 'M' logo that appears after the boot animation.
-Unlocking the bootloader went fine
-had trouble installing the android SDK since I ran out of space on my hard-drive, however the installation log notes that the necessary files were successfully downloaded after I made some space.
-I'm not running TWRP or any equivalent. The only thing I can access is the standard fastboot screen thing.
-I think made two errors with my first attempt at rooting: I forgot to type 'boot' after fastboot and I also hadn't uncompressed the zip folder that the img was contained in (it was CF Root incidentally). The command terminal came back with information alluding to it having done something but the device didn't reboot, so i'm unsure if it did.
-I tried to rectify this by installing different root imgs but the phone still won't boot.
I'm really unsure as to what to do. My guess is that I need to sideload a factory img of some sort. I've sent of for the official img from the Motorola website and am anxiously awaiting a reply but I wondered if anyone knew of any alternatives? All this hassle just so I could run some xposed modules :crying:
Click to expand...
Click to collapse
First thing I guess is installing a custom recovery. I recommend TWRP. Try this link to get the zip http://www64.zippyshare.com/v/HPPiFhly/file.html
Unzip the file on your pc.
Take the device to fastboot screen and plug it on pc.
Open the Instalador.bat file and click Enter until it's fully installed.
Then, get back to the fastboot screen and try to open the recovery.
---------- Post added at 01:36 PM ---------- Previous post was at 01:36 PM ----------
Let me know it that works for you.
So I've solved the problem but just figured I'd share the solution; basically don't use the terminal just run the bat file (assuming the img has one). Having rooted all my previous phones I hastily emulated the same process neglecting to notice the extremely convenient bat file included in the folder. Never could get TWRP to flash though. Although I could boot into it using: fastboot boot 'recovery'.img A little tedious but certainly functional. Once I had a working phone again I flashed TWRP using the Flashify App which I was a bit dubious about but it seems to have worked absolutely fine.
So yeah, silly oversight really but at least my phone turns on now; so that's nice. Cheers for the help though fhreire, although I couldn't get that recovery you linked to to work the fact it installed via a bat file is what lead me to find the solution I needed.
I recently formatted everything on my nexus 6 and I mean everything, the OS too. And I can't fix it, there was nothing on the forums or threads about this and how to fix it. Could you please help me?
Boot into the boatloader and flash the fastboot image.
Sent from my DROID Turbo 2
I have Ben an apple guy for 5 years just bought the nexus, I know how to get in to the boot loader but how do I flash the image? I tried downloading the image from the Google developers website but it said it failed ins
talling it!
Big-Blunt said:
I have Ben an apple guy for 5 years just bought the nexus, I know how to get in to the boot loader but how do I flash the image? I tried downloading the image from the Google developers website but it said it failed ins
talling it!
Click to expand...
Click to collapse
you cant use the flash-all, you need to flash each part separately. ynzip the file, then flash each .img file sepately. btw, ive deleted the whole os before. if you already have twrp installed, it wouls be a much easier fix using twrp instead.
How do I unzip the file in the boot loader?
Big-Blunt said:
How do I unzip the file in the boot loader?
Click to expand...
Click to collapse
i dont remember the program i used on my laptop, maybe 7zip.
The file downloaded from Google has a second zip inside. Unzip twice with 7 zip. The system image is inside the embedded zip file.
I assume you have the SDK from Google... Place all image files in the platform tools folder. I rename the images boot, radio, system, etc. to simplify typing the commands when actually flashing the images. DO NOT add the, " .IMG" when renaming.
Then:
Fastboot flash bootloader bootloader.IMG
Fastboot reboot-boitloader
Then same for system, radio, data and cache with out the reboot line.
When all files are flashed then fastboot reboot and enjoy
My brains are exploding rn, idk what or how to do anything, maybe u will think I'm dumb but I don't know what u guys are saying, could anyone post full instructions on how I would do it
The ONLY thing that you need to revive your device is alive bootloader. Every OS has its bootloader, and it determines what to load before system loaded.
I guess you did that foolish things on recovery. Then it won't kill itself of bootloader for sure.
Then there's always a chance. Try to boot into bootloader and switch it to fastboot mode.
Just flash stock rom image provided by google as described above.
You need to do some googling about fastboot and/or look for the beginners guide posted in the forums. You could use wugsfresh toolkit as well. I'm not being a douche not linking them,I'm to stoned
Google anything you don't understand
Sent from my Nexus 6 using Tapatalk
Do you know if your bootloader is unlocked?
You say you're an Apple guy - are you using a Mac? If you have access to a Windows machine I suggest you install Wugfresh's Nexus Root Toolkit and use the "Install & test drivers" button to set up the required drivers to connect your Nexus 6 to the computer. The walkthrough is comprehensive and extraordinarily simple - brilliant piece of programming. There is no Mac version.
Download the factory image (https://developers.google.com/android/nexus/images?hl=en#shamu image MMB29K).
Find the Fastboot/ADB programs on the web (I may have used the Minimal ADB & Fastboot tool, I can't remember exactly) and create a directory containing both programs plus their associated bits and pieces. I recommend making the path as simple as possible - e.g. C:\ADB for ease of navigation ( see below).
(While reading up on this, I came across this, which you may find useful - http://www.android.gs/install-set-up-adb-mac-os-x-linux/).
Unzip everything in the factory image, including the zip inside the zip as Larzzzz82 said, then copy the unzipped *.img files into the ADB Fastboot directory.
Boot your N6 into bootloader.
Open a CMD window and navigate to the ADB directory.
To check that you're connected, type (you don't need caps, this is just to make it clearer) FASTBOOT DEVICES. You should see something like "djdgkdjhgkdfj device" in response; if it's blank you're not connected - go through the driver setup again to see what you've missed.
Once you're successfully connected, you can install your new image following the instructions in this thread:
http://forum.xda-developers.com/google-nexus-5/help/stuck-launching-flashstock-bat-t3244470
I did ask for an expert to run a more experienced eye over them to correct any errors or to remove any pointless reboot commands, but nobody did either, so I guess they're ok. It's what I did and it worked for me. I've just noticed that it includes a line "fastboot flash recovery twrp.img" which you can ignore for the moment - though you may want to do this later when you have a working device.
Come back if you want any clarifications.
Happy new year (and, I hope, device...)
I tried I guess flashing the image through the recovery mode in the mount section but it said it failed,
Big-Blunt said:
I tried I guess flashing the image through the recovery mode in the mount section but it said it failed,
Click to expand...
Click to collapse
No no no you do not flash images through the recovery
Use Wugfresh's Nexus root and toolkit to restore it. Pretty easy.
@wolfen69 - duck and take cover...
I was going to suggest exactly that, since I'm a big fan of Wugfresh's NRT, but recommending it doesn't half bring down the flak... that's why I recommended using it initially at least to get the PC set up properly to connect and then get on with learning how to do it manually.
Personally in this situation using the NRT is exactly what I'd do myself. But now I'm retiring to my bunker for a while.
dahawthorne said:
@wolfen69 - duck and take cover...
I was going to suggest exactly that, since I'm a big fan of Wugfresh's NRT, but recommending it doesn't half bring down the flak... that's why I recommended using it initially at least to get the PC set up properly to connect and then get on with learning how to do it manually.
Personally in this situation using the NRT is exactly what I'd do myself. But now I'm retiring to my bunker for a while.
Click to expand...
Click to collapse
That's OK if people disagree with my recommendation. People are entitled to their opinions.
I tried for hours to do it the manual way and could never get it to work. And I'm a person who is VERY tech savvy. I had a computer repair business and have written advanced linux tutorials. I gave up and started using wugfresh. Has worked great for me. Others are free to do what works for them.
If you dont flash the images through the recovery mode then how do you flash it? I cant flash through command because the phone dosent have usb debugging enabled and its not in developer mode. I tried the nexus root toolkit as well and that didnt work either. Plz i need help!
So how much of my instruction did you follow? What exactly have you tried? Step by step. If you're vague then we can't help you. Error messages?
How did you delete the OS if your phone isn't unlocked?
Sent from my DROID Turbo 2
So i put it in recovery mode and when i tried resetting to factory i accidentally clicked advanced wipe and deleted everything so now its stuck in the boot loop. What i have tried was i downloaded the img file 6.0 shamu from googles site and drag and dropped on internal memory with my pc. Then in recovery mode i went mount and selected the img and it said error.
Hello, XDA forums. I was trying to get Miracast to work on my cousin's Nexus 6 device; doing sone research I found that it was as modifying a value in the build.prop file. Naturally, I was like "Pshh, easy!" (Note that the device was already rooted.)
So I download a build.prop editor and apply the edit, save the file. Superuser request, granted, saved. I noticed that the editor now displayed build.prop as an empty file, but still had the values loaded; okay, whatever.
I rebooted the device to apply the changes. It was stuck at the Google post screen and had not continued to the boot animation.
After waiting a couple minutes I realized there was an issue. Okay, so I would just use the adb interface to replace the build.prop file with the stock file, easy, no issue. Turns out when I rooted the device a while back I never flashed CWM or TWRP, so I had to get into the backup recovery, since attempting to factory reset from the bootloader resulted in the same as a normal boot.
Once I had gotten into the backup recovery I plugged the device in and attempted to update the build.prop file. I couldn't get further than 'adb root', it would result in an error for every command except sideload and USB. I tried for quite a while to resolve that issue.
That wasn't working so I was like "I'll just flash the OS since I have the ability to sideload", so I flashed the stock Nexus 6 ROM and still had the same issue.
Does anybody know of a solution?
@Drasid,
Download the factory image from Google developer site. Extract all the files. Fastboot flash the system, and boot image files from bootloader.
@cam30era,
I can do this with the stock recovery?
I can only secure an adb connection through that; fastboot commands do not work in it.
Drasid said:
@cam30era,
I can do this with the stock recovery?
I can only secure an adb connection through that; fastboot commands do not work in it.
Click to expand...
Click to collapse
No you use fast boot to flash factory images, adb to push a factory ota file
@Holeibdalip, Oh yeah, I was explaining the issue then my friend then realized "Wait, you can't fastboot like that, you fastboot in the bootloader."
It was one of those "Duh" moments.
Drasid said:
@Holeibdalip, Oh yeah, I was explaining the issue then my friend then realized "Wait, you can't fastboot like that, you fastboot in the bootloader."
It was one of those "Duh" moments.
Click to expand...
Click to collapse
And if you reread carefully what I wrote, I said "fastboot flash"....
Drasid said:
@Holeibdalip, Oh yeah, I was explaining the issue then my friend then realized "Wait, you can't fastboot like that, you fastboot in the bootloader."
It was one of those "Duh" moments.
Click to expand...
Click to collapse
Happens to the best of us lol
Alright so I reinstalled Android and it worked. Though on the setup page it said that my cousin couldn't log in and had to wait 24 hours (FRP). So, we waited a day and it persisted. I did some research and found a couple ways to fix it. Using adb I launched the settings app and performed a factory reset in the os. I still got the error afterwards, though I read that would fix it. Then I wiped the partition which is supposed to contain the frp information, that didn't work. I also tried to enable OEM unlocking in the os so I could fastboot OEM unlock and fix it, though the developer options appeared empty. I am unsure what to do next.
Edit: I flashed the system with the google developer image and reinstalled it, I got it to work, thanks for your guys's help.