So, I was installing ADB and such with android toolkit, It rebooted my phone into FASTBOOT in order to check the status of bootloader. Got the info I needed, then the phone rebooted, I went to download depixel8 and get ready to unlock and start the root shenanigans...and boom. The phone installs the NMF26U update without me even telling it to/letting it. Am I completely screwed on here as far as now being able to root and unlock my phone?
SomeFknGuy said:
So, I was installing ADB and such with android toolkit, It rebooted my phone into FASTBOOT in order to check the status of bootloader. Got the info I needed, then the phone rebooted, I went to download depixel8 and get ready to unlock and start the root shenanigans...and boom. The phone installs the NMF26U update without me even telling it to/letting it. Am I completely screwed on here as far as now being able to root and unlock my phone?
Click to expand...
Click to collapse
The toolkit updated your phone, or your phone took an ota? The toolkit should not have been able to update if you weren't already unlocked. Unless there's something I'm missing here..
k.s.deviate said:
The toolkit updated your phone, or your phone took an ota? The toolkit should not have been able to update if you weren't already unlocked. Unless there's something I'm missing here..
Click to expand...
Click to collapse
The OTA update notification was there, but I've been avoiding and ignoring it. When ADB/Toolkit rebooted my phone to check the status of the bootloader all was good, the second my phone rebooted from all that the notification bar showed that it was finishing the update. Went into the settings window to check the build version and it is now showing 7.1.1 and NMF26U. I'm without a solid hotspot work around now since foxfi is dead and I'm too lazy to pull my phone case constantly to remove and replace the sim heh. Just wondering what toolkit triggered to allow and instigate the update install
SomeFknGuy said:
The OTA update notification was there, but I've been avoiding and ignoring it. When ADB/Toolkit rebooted my phone to check the status of the bootloader all was good, the second my phone rebooted from all that the notification bar showed that it was finishing the update. Went into the settings window to check the build version and it is now showing 7.1.1 and NMF26U. I'm without a solid hotspot work around now since foxfi is dead and I'm too lazy to pull my phone case constantly to remove and replace the sim heh. Just wondering what toolkit triggered to allow and instigate the update install
Click to expand...
Click to collapse
I'm pretty sure the ota automatically downloads, when the toolkit rebooted the device it finished the install. If your device is Verizon then yes I think you're boned.
k.s.deviate said:
I'm pretty sure the ota automatically downloads, when the toolkit rebooted the device it finished the install. If your device is Verizon then yes I think you're boned.
Click to expand...
Click to collapse
oy... i was afraid of that... maybe someone can find a work around to at least get my hot spot working...
Is there no way to change the boot slot? Old system is still on the now not active bootslot.
So my question is there a way to change the bootslot without twrp.
mikaole said:
Is there no way to change the boot slot? Old system is still on the now not active bootslot.
So my question is there a way to change the bootslot without twrp.
Click to expand...
Click to collapse
There is. "fastboot --set-active=_a" (or _b). Here is a list of all known fastboot commands. https://forum.xda-developers.com/pixel-xl/how-to/pixel-xl-fastboot-commands-t3490080
mikaole said:
Is there no way to change the boot slot? Old system is still on the now not active bootslot.
So my question is there a way to change the bootslot without twrp.
Click to expand...
Click to collapse
Isn't the old system partition updated in the background then after the update is complete? Even if it isn't, the radio and bootloader are still updated.
Sent from my Pixel XL
imnuts said:
Isn't the old system partition updated in the background then after the update is complete? Even if it isn't, the radio and bootloader are still updated.
Sent from my Pixel XL
Click to expand...
Click to collapse
Nope, they aren't updated until a new update comes. Also there are two slots for radio and bootloader just like everything else so in theory if he could use fastboot he could switch boot slots.
Sent from my Pixel XL using Tapatalk
superchilpil said:
Nope, they aren't updated until a new update comes. Also there are two slots for radio and bootloader just like everything else so in theory if he could use fastboot he could switch boot slots.
Click to expand...
Click to collapse
Unfortunately this won't help. If he installed the update his bootloader is now locked and there is no way to unlock it.
aholeinthewor1d said:
Unfortunately this won't help. If he installed the update his bootloader is now locked and there is no way to unlock it.
Click to expand...
Click to collapse
I sry to say..but I completely agree. If your on 7.1.1 and still locked your stuck locked.
SomeFknGuy said:
oy... i was afraid of that... maybe someone can find a work around to at least get my hot spot working...
Click to expand...
Click to collapse
Pop the sim card, push it back in, wait 4 seconds, turn on hotspot.
No there is a way past this it happened to me, @jcase knows the command you need to get by this.
mwalt201 said:
Pop the sim card, push it back in, wait 4 seconds, turn on hotspot.
Click to expand...
Click to collapse
actually been doing just this. just a little bit of a pain to do with the cover that I'm running. worth it though, until verizon figures out a fix for that :|
Related
Anyone know what this is for?
Jrocker23 said:
Anyone know what this is for?
Click to expand...
Click to collapse
Hm. 612 megs. That could be....well let's see.
Sent from my Nexus 6 using Tapatalk
Installed and currently on the Android is upgrading/Optimizing apps screen...... Hopefully won't take too much longer.
software repair patch for 5.1 as told by vzw customer service. what it is repairing i dont know
3.10.605.7 / Base: 2.12.C1144073
Nothing different.... Seems just like a security patch.
http://www.verizonwireless.com/support/htc-one-m9-update/
SnoStorm said:
Nothing different.... Seems just like a security patch.
http://www.verizonwireless.com/support/htc-one-m9-update/
Click to expand...
Click to collapse
One can only wonder what the heck verizon does to their software such that it requires a 612meg security patch huh?
Anyhow.. Time to use that nandroid i posed in the dev section to accept the OTA.. -or- I will post an updated one later this evening.
Probably 600mb of updated NFL bloatware included and the rest just the security update.
Any word yet on whether this is really just a 612Meg security patch?
jtommyj said:
Any word yet on whether this is really just a 612Meg security patch?
Click to expand...
Click to collapse
yup, nothing special
Anyone know if letting this thing run and update will break root? I'm stock, rooted. Don't want to lose that and not be able to get it back myself.
baune7 said:
Anyone know if letting this thing run and update will break root? I'm stock, rooted. Don't want to lose that and not be able to get it back myself.
Click to expand...
Click to collapse
are you SOFF? if so, you will be fine
Yes.. I'm s-off and unlocked. So after it updates, will it still be rooted? Or would I havery to re-root it? I'm just worried because my cable Internet isn't working for a few days and I need my wifi tether. Thanks
Ran into an issue with this update. It failed to install on 11/3 with a error code 409, but when I try to download it again by selecting "Check for new system updates" it says I have the latest update. I've rebooted a number of times and it shows up every time. From what little information I can find online, I have to reset my phone to factory then attempt to update again. I want to avoid this so here I am.
I'm on my phone so I can't properly upload the screenshots. I posted Google Drive links for now
https://drive.google.com/file/d/0B__V8WYcxeW8dkVxOXktZXZHcVU/view?usp=sharing
https://drive.google.com/file/d/0B__V8WYcxeW8YWdsU1kyMmZOcFk/view?usp=sharing
gumbyx84 said:
Ran into an issue with this update. It failed to install on 11/3 with a error code 409, but when I try to download it again by selecting "Check for new system updates" it says I have the latest update. I've rebooted a number of times and it shows up every time. From what little information I can find online, I have to reset my phone to factory then attempt to update again. I want to avoid this so here I am.
I'm on my phone so I can't properly upload the screenshots. I posted Google Drive links for now
https://drive.google.com/file/d/0B__V8WYcxeW8YWdsU1kyMmZOcFk/view?usp=docslist_api
https://drive.google.com/file/d/0B__V8WYcxeW8dkVxOXktZXZHcVU/view?usp=docslist_api
Click to expand...
Click to collapse
Flash the custom firmware zip and restore the nandroid I posted of the update. Then wipe data for the app htcdm. Flash supersu.zip and you're done.
Sent from my Nexus 6 using Tapatalk
dottat said:
Flash the custom firmware zip and restore the nandroid I posted of the update. Then wipe data for the app htcdm. Flash supersu.zip and you're done.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I'm not rooted.
Update: I decided to just to a factory reset. Thankfully it worked and I am at the latest firmware.
So I've tried letting this update run a couple times. Downloading for the third time as I write this. When it tries to install, it just reboots into TWRP recovery and does nothing. Then I restart the phone and basically start the process all over again. Any guidance on how to get this squared away?? I met one of the members here with a card who S-offed, unlocked, rooted, my phone which I'm thankful for. Just want to be stock rooted is all. Don't really do much with custom roms on this phone. Thanks.
baune7 said:
So I've tried letting this update run a couple times. Downloading for the third time as I write this. When it tries to install, it just reboots into TWRP recovery and does nothing. Then I restart the phone and basically start the process all over again. Any guidance on how to get this squared away?? I met one of the members here with a card who S-offed, unlocked, rooted, my phone which I'm thankful for. Just want to be stock rooted is all. Don't really do much with custom roms on this phone. Thanks.
Click to expand...
Click to collapse
I'm pretty sure you need stock recovery to take an OTA.
SigLover21 said:
I'm pretty sure you need stock recovery to take an OTA.
Click to expand...
Click to collapse
Ok.. Thanks.. I'll have to check into that
Hey guys,
so i got my 5x a few days ago and set up root etc. A few laters i wanted to listen to music and realized that my jack is not working ( cant put my earphones all the way in, no contact).
So i wanted to send it back and get another one, Using the awesome nexus 5x toolkit i went back to stock and locked the bootloader, but now everytime it boots up i get that ugly message that my device is corrupt and i dont want to have any troubles because of it. any help? (flashed the mhc19j, it came with an older version).
Thanks!
levibuko said:
Hey guys,
so i got my 5x a few days ago and set up root etc. A few laters i wanted to listen to music and realized that my jack is not working ( cant put my earphones all the way in, no contact).
So i wanted to send it back and get another one, Using the awesome nexus 5x toolkit i went back to stock and locked the bootloader, but now everytime it boots up i get that ugly message that my device is corrupt and i dont want to have any troubles because of it. any help? (flashed the mhc19j, it came with an older version).
Thanks!
Click to expand...
Click to collapse
Just fixed my 5x yesterday! Rooted it etc right out of the box and, presto, that warning. I'm having trouble with the link though. Here goes...
Or not. There's a thread with a flashable zip in here. I just Googled "corruption bootloader warning" sans the quotes and there it was.
Hinesight 20/20 said:
Just fixed my 5x yesterday! Rooted it etc right out of the box and, presto, that warning. I'm having trouble with the link though. Here goes...
Or not. There's a thread with a flashable zip in here. I just Googled "corruption bootloader warning" sans the quotes and there it was.
Click to expand...
Click to collapse
so there is no official way to dismiss the warning? only replacing it with the tool?
levibuko said:
so there is no official way to dismiss the warning? only replacing it with the tool?
Click to expand...
Click to collapse
nope. That warning will appear on devices with an unlocked bootloader. The only way around it is to re-lock the bootloader or cover it up with a bootloader skin like the material design one available on this site
levibuko said:
so there is no official way to dismiss the warning? only replacing it with the tool?
Click to expand...
Click to collapse
No. In fact someone put up a bounty to get ride of it.
Hinesight 20/20 said:
Just fixed my 5x yesterday! Rooted it etc right out of the box and, presto, that warning. I'm having trouble with the link though. Here goes...
Or not. There's a thread with a flashable zip in here. I just Googled "corruption bootloader warning" sans the quotes and there it was.
Click to expand...
Click to collapse
clcdev said:
nope. That warning will appear on devices with an unlocked bootloader. The only way around it is to re-lock the bootloader or cover it up with a bootloader skin like the material design one available on this site
Click to expand...
Click to collapse
Well. i didt lock my bootloader and it is till there.
i am not talking about ""Your device software can't be checked for corruption. Please lock the bootloader." (Orange)"
but about this one:" Your device is corrupt. It can't be trusted and may not work properly." (Red)"
levibuko said:
Well. i didt lock my bootloader and it is till there.
i am not talking about ""Your device software can't be checked for corruption. Please lock the bootloader." (Orange)"
but about this one:" Your device is corrupt. It can't be trusted and may not work properly." (Red)"
Click to expand...
Click to collapse
Ah. Sorry, I misunderstood the error you were getting. I believe that second one is due to a mismatch between the particular rom you are running and the vendor version. If you flashed back to stock using the latest stock images, I'm not sure why you are getting it as the vendor version should match (unless something else went wrong during the flash).
I unlocked the bootloader on my Pixel 2 XL and rooted, while being on security patch May 2018, I'm wanting to update to July 2018's security patch but don't want to risk locking the bootloader.
It's a Verizon phone.
Anyone know if I can go about it and how exactly? Really nervous and don't really like my device without being rooted.
Any help is appreciated
ryanispd said:
I unlocked the bootloader on my Pixel 2 XL and rooted, while being on security patch May 2018, I'm wanting to update to July 2018's security patch but don't want to risk locking the bootloader.
Anyone know if I can go about it and how exactly? Really nervous and don't really like my device without being rooted.
Any help is appreciated
Click to expand...
Click to collapse
You won't lock the bootloader unless you manually enter the commands in fastboot.
You can update to July by either: fastbooting the factory image with the -w removed to preserve data. Flashing the OTA.zip in twrp. Or side load the OTA :good:
Badger50 said:
You won't lock the bootloader unless you manually enter the commands in fastboot.
You can update to July by either: fastbooting the factory image with the -w removed to preserve data. Flashing the OTA.zip in twrp. Or side load the OTA :good:
Click to expand...
Click to collapse
My device is a Verizon phone, I was in luck when getting the phone for it being on an older security update just really worried that I will lock it if I try to update it.
Are you 100% sure this won't do so?
Is this guide fine to follow: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535
or do I need to leave anything out while doing it? I thought I'd need to leave the bootloader-taimen-tmz12g-.img out or something to prevent it.
Apologizes if I sound dumb, I'm new to all this and only recently moved from Samsung to Pixel so I appreciate the help.
ryanispd said:
My device is a Verizon phone, I was in luck when getting the phone for it being on an older security update just really worried that I will lock it if I try to update it.
Are you 100% sure this won't do so?
Is this guide fine to follow: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535
or do I need to leave anything out while doing it? I thought I'd need to leave the bootloader-taimen-tmz12g-.img out or something to prevent it.
Apologizes if I sound dumb, I'm new to all this and only recently moved from Samsung to Pixel so I appreciate the help.
Click to expand...
Click to collapse
You made no mention that it was a Verizon phone in your post. Therefore, I'm not sure now. Have you run the IMEI checker to see if it's truly a Verizon phone.
Sorry, my bad, you did mention it.
Badger50 said:
You made no mention that it was a Verizon phone in your post. Therefore, I'm not sure now. Have you run the IMEI checker to see if it's truly a Verizon phone.
Sorry, my bad, you did mention it.
Click to expand...
Click to collapse
I've read that the only way to lock the bootloader once its unlocked is to manually do so via the commands, this should be the same regardless of if being Verizon I would assume but not sure and don't want to go through with updating without knowing.
What's a good IMEI checker to check which network, imei.info doesn't seem to show
ryanispd said:
I've read that the only way to lock the bootloader once its unlocked is to manually do so via the commands, this should be the same regardless of if being Verizon I would assume but not sure and don't want to go through with updating without knowing.
What's a good IMEI checker to check which network, imei.info doesn't seem to show
Click to expand...
Click to collapse
This is the only one I know of.
http://www.imeipro.info/check_lg.html
Badger50 said:
This is the only one I know of.
http://www.imeipro.info/check_lg.html
Click to expand...
Click to collapse
I checked via verizon's imei checker (https://www.verizonwireless.com/prospect/bring-your-own-device#/checkDevice)
looks like it isn't actually a verizon model, I'm in luck I guess.
ryanispd said:
My device is a Verizon phone, I was in luck when getting the phone for it being on an older security update just really worried that I will lock it if I try to update it.
Are you 100% sure this won't do so?
Is this guide fine to follow: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535
or do I need to leave anything out while doing it? I thought I'd need to leave the bootloader-taimen-tmz12g-.img out or something to prevent it.
Apologizes if I sound dumb, I'm new to all this and only recently moved from Samsung to Pixel so I appreciate the help.
Click to expand...
Click to collapse
It will not relock. I am 100 percent sure. There are several reasons it wont. One is that relock will wipe your data, can you imagine the lawsuits if Google and Verizon send an update that they knew would wipe your data.
The second reason is that it is technologically impossible. You are thinking of when a VZ update breaks root o other phones. This phone is way different. It won't happen.
Relax, update.
You will lose root when you update. Easy enough to restore though.
ryanispd said:
I unlocked the bootloader on my Pixel 2 XL and rooted, while being on security patch May 2018, I'm wanting to update to July 2018's security patch but don't want to risk locking the bootloader.
It's a Verizon phone.
Anyone know if I can go about it and how exactly? Really nervous and don't really like my device without being rooted.
Any help is appreciated
Click to expand...
Click to collapse
I also have a Verizon phone that randomly let me unlock the bootloader. I was running DU and just flashed the OTA in TWRP. Booted right up. No issues with it relocking the bootloader or any other nonsense.
Guys I need your help and I’m desperate to someone get me to the right dirrection.
I just got a pixel 2 xl, I unlock the bootloader and root with twrp. I try to install a lineage os rom with the gaps and it looks like everything when the well. I erase the cache and free I reboot it went back to the bootloader screen. From that point I have been spending all day trying to get back to factory or at least trying to install any other rom with out any luck. It someone can help me out I will be more than happy to send a Starbucks card or something. I just got the phone,
I forgot to mention that when I try to use the and side load it says something about the e drive, like if there es no drive on my phone
rectangularspace said:
Guys I need your help and I’m desperate to someone get me to the right dirrection.
I just got a pixel 2 xl, I unlock the bootloader and root with twrp. I try to install a lineage os rom with the gaps and it looks like everything when the well. I erase the cache and free I reboot it went back to the bootloader screen. From that point I have been spending all day trying to get back to factory or at least trying to install any other rom with out any luck. It someone can help me out I will be more than happy to send a Starbucks card or something. I just got the phone,
Click to expand...
Click to collapse
Do you know and understand how you use fastboot or the Deuces script to flash factory images to return you to stock OS?
Well not really. But I follow many instrucciones from differents post and nothing
rectangularspace said:
Well not really. But I follow many instrucciones from differents post and nothing
Click to expand...
Click to collapse
Read over this thread. Then let us know if you need help. https://forum.xda-developers.com/pi...de-reference-8x-oreo-to-t3826330/post77530335
Also, if you have twrp installed, you can flash the OTA zip that corresponds to your current OS version :good:
I do have twrp installed the problem is that I don’t have the zip on the phone to install the ota file.
Try with deceus Script (Just search for it) and select repair bootloop. It will download the factory Image and flash it on a and b partition then your phone will boot again. But your data will be lost :/
Ok., I will let you guys know thank you
Also, I forgot to mention that it looks like that I don’t have a OS installed ( twrp is telling me that every time i try to get out to the get out of the twrp menu. At this point i haven’t don’t anything mention in this post because I’m resetting my computer nd I’m installing right now the android sdk software.
You don't have to install the full Android SDK software for the job you're trying to do. You can download the latest Fastboot commands and ADB through Google, or even XDA(somewhere).
I've installed adb to my Windows commands, so once in recovery, when I need a file, I just "adb push file.zip /sdcard/".
No worries though. You'll be back up and running. ?
Edit: Also, if you still have data on your phone, you can check using the file explorer on TWRP. If you do, you can adb pull anything you want to keep.
@rectangularspace Link to the standalone platform tools HERE. This is all you need.
Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?
rectangularspace said:
Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?
Click to expand...
Click to collapse
Yes, but going down from 9 to 8 will cause/require a data wipe.
rectangularspace said:
Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?
Click to expand...
Click to collapse
Why did you decide to install Oreo?? There will be no further security or functionality updates for 8.1. The next monthly update to Pie should be the first Monday of next month (October 1st) if you don't get a OTA nag before then.
I have the update available to install on my settings. But what I'm looking for is to start over on rooting my pixel 2 xl. But after last experience I'm a little conservative when it comes to mess with the phone. I'm reading right now the post where it says to do the critical unlock for the phone but I don't know witch bootloader version I have. Can you guys help me out
I have tmz10n version on my bootloader. It means that I need to do the critical unlock? By the way I did already unlock my bootloader and i Haven lock it again. And I think at some point when I was having trouble with my phone to put it back to run I did also the critical unlock process.
rectangularspace said:
I have tmz10n version on my bootloader. It means that I need to do the critical unlock? By the way I did already unlock my bootloader and i Haven lock it again. And I think at some point when I was having trouble with my phone to put it back to run I did also the critical unlock process.
Click to expand...
Click to collapse
You only need to do the unlock process one time, BUT there are two separate unlock commands which include unlock_critical. If in doubt you can use fastboot device-info or getvar to check the current status. Make sure you are using the latest version of the platform tools I linked to above. One word of caution... don't EVER re-lock your bootloader or you WILL run into problems. Even if you are returning the phone to Google for RMA you do not need to re-lock it.
My bad, after unlock my bootloader I haven't look back again. So it is unlock right now. Thank you for advised. For what I read the only way to unlock it it will be by running the command fastboot right? If I upgrade to pie using the upgrade available in my settings right now, it will not lock the bootloader right?
rectangularspace said:
My bad, after unlock my bootloader I haven't look back again. So it is unlock right now. Thank you for advised. For what I read the only way to unlock it it will be by running the command fastboot right? If I upgrade to pie using the upgrade available in my settings right now, it will not lock the bootloader right?
Click to expand...
Click to collapse
I meant the only way to lock the bootloader will be thru a fastboot command.
rectangularspace said:
I meant the only way to lock the bootloader will be thru a fastboot command.
Click to expand...
Click to collapse
Yes, once you have successfully unlocked the phone in fastboot using the two separate commands, you will never have to do it again, AND flashing anything will not re-lock the bootloader. Please read over Nathan's GUIDE HERE to confirm you have done this correctly (and completely). Once this is done you can flash OTA's , full Google images, custom roms, etc. Lastly, if you are properly unlocked you cannot brick your phone. No matter how bad it gets, you will always have a path to restore the phone to it's original state. Don't hesitate to take the OTA being offered on your phone. It will take you to 9.0 without losing data or locking anything. :good:
Just wondering when the new security update will be out as I feel the last one is making my battery drain quite a lot. Tried all the normal routine stuff and still nothing specially after two factory resets. Here is hoping that with the new software it will be fixed
Hey Goku80, judging solely by past-trends, it should most certainly be out today.
It's live guys! https://dl.google.com/dl/android/aosp/crosshatch-pq3a.190801.002-factory-15db810d.zip
Flashed August full image from google website and touchscreen doesn't work. Can't even use pin to access phone. Anyone else?
BoboBrazil said:
Flashed August full image from google website and touchscreen doesn't work. Can't even use pin to access phone. Anyone else?
Click to expand...
Click to collapse
Could I flash it without root? Sorry it has been a long while since I did something like this. I remember on the OnePlus you could flash manually
ota is not here yet
Goku80 said:
Could I flash it without root? Sorry it has been a long while since I did something like this. I remember on the OnePlus you could flash manually
Click to expand...
Click to collapse
The OTA can be flashed using stock recovery. No wipe.
spotmark said:
The OTA can be flashed using stock recovery. No wipe.
Click to expand...
Click to collapse
True but means I need to use ADB which I don't have a pc
Goku80 said:
True but means I need to use ADB which I don't have a pc
Click to expand...
Click to collapse
You can flash it as long as your BL is unlocked. It has nothing to do with root. You still need to use the flash-all batch file though, so a computer is still necessary.