Related
So, after running MIUI for 3 months, i decided to try something else.
I got Acromion rom, and put it on my SD card.
I were running Jacobsein's kernel.
So, i installed it and rebooted. Waited for 2 hours, and it hasnt progressed.
Tried wiping, reinstalling, and such.
So i went and wanted to put it in fastboot so i could try with another kernel.
But my PC doesnt regonize it anymore.
So, what do i do:/?
THANKS!
Try another USB port on your PC.
Fastboot should not be affected.
iR¡[email protected]!* via Tapatalk
jacobstein or jasonstein?its for miui,doesnt work for other rom than miui..
Sent from my LT18i
Thanks for your help guys!
I just simply can't get fastboot to working.
The blue light is on, but "Fastboot devices" returns nothing..
Does anybody haves another link for the drivers? multiupload is down
install flashtool(latest,got link in sticky),then to driver folder inside flashtool's program file,install it..
Sent from my LT18i
take batery out of phone wait 5 min and try again,
you are sure the fastboot drivers are okay right ?
depulle87 said:
take batery out of phone wait 5 min and try again,
you are sure the fastboot drivers are okay right ?
Click to expand...
Click to collapse
No i'm not 100% sure, thats why i want to reinstall them, but multiupload is down, and that's where all the files are
UPDATE:
I got it working! This video http://www.youtube.com/watch?v=dUsA9HxZjJE&feature=related had the right files! thanks anyway!
rashid.fairus said:
install flashtool(latest,got link in sticky),then to driver folder inside flashtool's program file,install it..
Sent from my LT18i
Click to expand...
Click to collapse
Yes, it shows up as ADB interface in devicemaneger, but fastboot still doesnt work, fastboot devices shows nothing:/
You can download fastboot via android sdk (it's located in platform-tools in android-sdk directory).
In SDK manager install Tools->Android SDK Platform-tools and Extras->Google USB Driver Package.
Replace the android_winusb.inf file located in Extras\Google\usb_driver in android sdk directory with the one provided by SE (http://unlockbootloader.sonyericsson.com/instructions)
If you have a 64 bit OS, this file won't work, use the one I attached to this post :
http://forum.xda-developers.com/showpost.php?p=22361703&postcount=269
Use this inf to install driver
Hi there,
I had rooted Nexus 7 (2013) LTE with 5.0.2 stack version.
The tablet was rooted with Nexus Root Toolkit. I received notification about new (5.1.0) Android version. Tried to upgrade, but received error message during the installation (Error with android symbol and "!"). Tried to upgrade using Nexus Root Toolkit and got the same problem. Tried to do factory default and after that tablet is not coming up. Get stuck with "Google" and unlocked lock over the black screen. Get rebooted a few times and then "No command" over the android symbol. Open fastboot and tried to restore using Nexus Tool Kit but received error message that "Command not found" (please see the pic). Was able to reformat system and boot partition as well as userdata, but still got the same problem during OS installation...
Please advise...
vadim_se said:
Hi there,
Do not PM me for questions. Next time I'd not reply to PM questions.
I had rooted Nexus 7 (2013) LTE with 5.0.2 stack version.
The tablet was rooted with Nexus Root Toolkit. I received notification about new (5.1.0) Android version. Tried to upgrade, but received error message during the installation (Error with android symbol and "!"). Tried to upgrade using Nexus Root Toolkit and got the same problem. Tried to do factory default and after that tablet is not coming up. Get stuck with "Google" and unlocked lock over the black screen. Get rebooted a few times and then "No command" over the android symbol. Open fastboot and tried to restore using Nexus Tool Kit but received error message that "Command not found" (please see the pic). Was able to reformat system and boot partition as well as userdata, but still got the same problem during OS installation...
Please advise...
Click to expand...
Click to collapse
Hello, first download the latest stock ROM from Google nexus images. Make sure you have the right device image. Use winrar to unzip it . you'll again have a file which you'll need again to extract by selecting rar to extract it. (On PC)
Then download platform tools, and paste them in the folder you extracted.
Click on install.bat or something and it'd run fine.
I'll attach platform tools in a bit or update it with a link. Find platform tools below.
forum.xda-developers.com/showthread.php?t=2415668
Quote me next time if you expect a reply
Hnk1 said:
Hello, first download the latest stock ROM from Google nexus images. Make sure you have the right device image. Use winrar to unzip it . you'll again have a file which you'll need again to extract by selecting rar to extract it. (On PC)
Then download platform tools, and paste them in the folder you extracted.
Click on install.bat or something and it'd run fine.
I'll attach platform tools in a bit or update it with a link. Find platform tools below.
forum.xda-developers.com/showthread.php?t=2415668
Quote me next time if you expect a reply
Click to expand...
Click to collapse
Thank you for your answer.
I've unzipped platorm tools and the Android latest release. There is no install.bat or anything like that. When I'm trying to run any of adb commands (adb reboot bootloader, for example) I receive error message that device can't be found. However, Nexus Root Tool is able to reboot device.
Please advise...
vadim_se said:
Thank you for your answer.
I've unzipped platorm tools and the Android latest release. There is no install.bat or anything like that. When I'm trying to run any of adb commands (adb reboot bootloader, for example) I receive error message that device can't be found. However, Nexus Root Tool is able to reboot device.
Please advise...
Click to expand...
Click to collapse
Are you on unlocked boot loader? Do you have all the drivers installed from wugfresh tool kit?
Read this guide but you'll need nexus 7 2013 lte image
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Hnk1 said:
Are you on unlocked boot loader? Do you have all the drivers installed from wugfresh tool kit?
Read this guide but you'll need nexus 7 2013 lte image
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Click to expand...
Click to collapse
Hnk1,
Thank you very much. Sorry for PM. I've manually flashed all partitions using fastboot command and the tablet came back up. It is locked now and I'm not sure if I want to unlock it since the only rooted components I was using were application restart blocker and TB.
vadim_se said:
Hnk1,
Thank you very much. Sorry for PM. I've manually flashed all partitions using fastboot command and the tablet came back up. It is locked now and I'm not sure if I want to unlock it since the only rooted components I was using were application restart blocker and TB.
Click to expand...
Click to collapse
I'm glad everything is working fine. Unlocked boot loader isn't a problem at all. All of my devices are developer unlocked . So it isn't a problem if you like flashing/changing Roms.
Just keep it as you feel comfortable. If you have any other queries /questions, quote me and I be glad to answer your questions.
I have a Chinese max, 32gb. It’s currently on miui 7.5.1.0 stable. When I click check for updates it says no updates available. I’m in china if that makes any difference.
How can I upgrade to a newer software? Can I change to global rom?
I don’t have a windows computer and most guides seems to require windows. Also I don't want a custom rom.
Alternatively, how can I get native update function the to work?
Thanks for help to push mein the right direction.
Screenshot of about phone?
Sent from my Xiaomi MI MAX using XDA Labs
here is the screenshot
nick5000 said:
I have a Chinese max, 32gb. It’s currently on miui 7.5.1.0 stable. When I click check for updates it says no updates available. I’m in china if that makes any difference.
How can I upgrade to a newer software? Can I change to global rom?
I don’t have a windows computer and most guides seems to require windows. Also I don't want a custom rom.
Alternatively, how can I get native update function the to work?
Thanks for help to push mein the right direction.
Click to expand...
Click to collapse
Well, without a pc you have less options, users of miui are on nougat (beta) but in your case must be sure of these things; download (easier) an app from playstore about developer options, open and check at USB debugging, allow, now download a global version from official Miui page for Hydrogen (device name) must be in .zip format and try going to /settings/about device/system update you`ll see four dots upper right and option "select update package", navigate to your downloaded file and try to flash
Thanks. So I downloaded it, went to updater and chose the file, and it says couldn't verify update package.
Tried to download to recovery mode, but then I just get to a screen with the symbol to connect USB cable to computer.
nick5000 said:
Thanks. So I downloaded it, went to updater and chose the file, and it says couldn't verify update package.
Tried to download to recovery mode, but then I just get to a screen with the symbol to connect USB cable to computer.
Click to expand...
Click to collapse
If from this option doesn`t flash your zip either do from mi recovery. Version for China probably is from a phone company if you live there. You need a pc at least to install TWRP (it takes two minutes) and from here you must install last version official beta v8 7.1.19 but you need unlock bootloader
So this is not possible to do with a MAC? what about the terminal commands, can I install a rom from the CLI ?
nick5000 said:
So this is not possible to do with a MAC? what about the terminal commands, can I install a rom from the CLI ?
Click to expand...
Click to collapse
I know this isn't the quickest workaround, but if you're stuck on a Mac you can always bootcamp it for free. Just download Windows 10 (around a 5GB download I think) and install via bootcamp. You don't need a serial to officially install or run WIndows 10 and you can just remove the installation when you're finished.
nick5000 said:
So this is not possible to do with a MAC? what about the terminal commands, can I install a rom from the CLI ?
Click to expand...
Click to collapse
You can use other advance phone (cause this will be busy) like a viewfinder of .img in your computer, with an app from Play Store called DriveDroid, you place some .img in your sdcard and to arrange computer select usb (it`s like a virtual machine) or burn an image in a usb with a linux distro, here is a rescue cd that contain a virtual Windows XP called Hiren`s Boot (500 mb aprox.) but really I don`t know if all that works on a mac.
First read that post, it seems is possible use fastboot on a mac according that: http://htc-one.gadgethacks.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
SubwayChamp said:
You can use other advance phone (cause this will be busy) like a viewfinder of .img in your computer, with an app from Play Store called DriveDroid, you place some .img in your sdcard and to arrange computer select usb (it`s like a virtual machine) or burn an image in a usb with a linux distro, here is a rescue cd that contain a virtual Windows XP called Hiren`s Boot (500 mb aprox.) but really I don`t know if all that works on a mac.
First read that post, it seems is possible use fastboot on a mac according that: http://htc-one.gadgethacks.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
Click to expand...
Click to collapse
I tried using fastboot commands on mac to to update, but didn't work.
I guess I'll have to stick with 7.5.10 until I get a new phone.
However wonder why the OTA update doesn't work.
nick5000 said:
I tried using fastboot commands on mac to to update, but didn't work.
I guess I'll have to stick with 7.5.10 until I get a new phone.
However wonder why the OTA update doesn't work.
Click to expand...
Click to collapse
What did you type in fastboot?, zip version is not for fastboot, must be download correct version, but go for the first step, probably you must
unlock bootloader, request to xiaomi, sometimes you got it in 6 hours, depends, probably device is rooted, for this reason don't update ota. Here you have other thread to apply fastboot with other method https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
tried both the flash all except storage.sh and the flashboot flash system commands. it said device it locked. I applied to unlock bootloader, no reply yet, but does that also require a Windows program to unlock the bootloader?
Device is not rooted, but I installed google play, maybe that's what broke the OTA
nick5000 said:
tried both the flash all except storage.sh and the flashboot flash system commands. it said device it locked. I applied to unlock bootloader, no reply yet, but does that also require a Windows program to unlock the bootloader?
Device is not rooted, but I installed google play, maybe that's what broke the OTA
Click to expand...
Click to collapse
No, Google Play can't do that. In my little corner of the world we say "all the roads lead to Rome", I think you need a pc, There is other shorter way of two steps root first with a pc and then download from Google Play an app called "flashfire" you may flash a zip rom from this app. Also you may use a virtual cd or usb with a linux distro like ubuntu or debian running on your mac to arrange computer like a live cd or usb without install on your mac or if you prefer install it on your mac, there's a world of options just root device and can flash any you want and be the real owner of your phone
Now that I've successfully unlocked my bootloader, I'm having an issue trying to flash the 8.1.0 system image. When I try to execute the flash-all.bat, it acts as if it's flashing the bootloader, and then I get an error message saying it failed. Here's a screenshot. Thanks in advance
Did you extract the zip file that's in the factory image zip? There's another zip in there that has the boot, recovery, etc image files.
Sent from my [device_name] using XDA-Developers Legacy app
I did. I'm wondering if it's an SDK issue...the Android API 27 SDK keeps failing to download via SDK manager because of a mismatched size. I tried downloading it in Android Studio, too, and while it says it's installed there, it says it isn't in SDK manager. Weird. I wish there was a way I could get it to download and install properly.
Google 15 seconds adb xda. That's the easiest way to get Fastboot and adb set up. It don't matter where the image files as it sets it up system wide. But it sounds more like you might have a corrupted file. Try download the factory image again.
Sent from my [device_name] using XDA-Developers Legacy app
Thanks! I tried that, however it still keeps failing I'm at a total loss. I just want to get onto Oreo 8.1 so I can flash the AOSP and root! This really has me baffled. Thanks again for your help
I did also try to redownload the file, and that wasn't the answer, either :/
Are you using Type C to C? I had this issue on my Pixel C and Pixel XL unable to flash a factory img with C to C only when I use A to C
It was indeed the SDK platform! I tried looking for where the API 27 had successfully installed in Android Studio, and found that it was under App Data>SDK. I looked there and voila! There was the downloaded platform. I extracted it and moved it to where the other platforms were located under SDK Tools, and success! I'm flashing the 8.1.0 factory image now
Ok, I spoke too soon The factory image files AREN'T flashing, and I got a data write failure....go figure. When I go to restart my tablet, I get the classic Android with the exclamation point. Here are some pics of what I got:
So I got it working! After a LOT of trial and error, and moving files to the platforms folder and flashing them that way, plus changing which USB port I was using, I was able to manually flash all files! I'm now on 8.1.0!
Hello,
I managed to screw something up, and now my phone is in a bootloop.
I have already posted a question somewhere else on this forum, but I got a suggestion to post it here.
Here is the link to the thread.
https://forum.xda-developers.com/ge...ges-target-t3803741/post76807253#post76807253
Please, I really need to get this phone up and running again.
I'm going to try everything that is suggested.
Thank you very much,
Jan
jan_ruc said:
Hello,
I managed to screw something up, and now my phone is in a bootloop.
I have already posted a question somewhere else on this forum, but I got a suggestion to post it here.
Here is the link to the thread.
https://forum.xda-developers.com/ge...ges-target-t3803741/post76807253#post76807253
Please, I really need to get this phone up and running again.
I'm going to try everything that is suggested.
Thank you very much,
Jan
Click to expand...
Click to collapse
Where are you at right now, and what have you all tried besides the skipsoft?
Badger50 said:
Where are you at right now, and what have you all tried besides the skipsoft?
Click to expand...
Click to collapse
I tried downloading the official(8.1.0) and the latest version of P beta from Google, and ran the flash-all.bat. Running that said that the max reported download size was not reported and failed. As far as I know Android should still be installed, TWRP still works and thats pretty much it.
jan_ruc said:
I tried downloading the official(8.1.0) and the latest version of P beta from Google, and ran the flash-all.bat. Running that said that the max reported download size was not reported and failed. As far as I know Android should still be installed, TWRP still works and thats pretty much it.
Click to expand...
Click to collapse
Try a different USB cable.
ilal2ielli said:
Try a different USB cable.
Click to expand...
Click to collapse
I don't have any other cables. I will ask my friend to lend me his and try that. But what if that doesn't work?
I had this issue on my old tower. Plugging my phone into USB 3.X ports didn't allow it to flash images via fastboot with the same error. I plugged it directly into the case's 2.0 ports and it worked perfectly. My new tower doesn't do that, though. Oh and I had two brand new cables.
So basically try a different port/cable.
Ariac Konrel said:
I had this issue on my old tower. Plugging my phone into USB 3.X ports didn't allow it to flash images via fastboot with the same error. I plugged it directly into the case's 2.0 ports and it worked perfectly. My new tower doesn't do that, though. Oh and I had two brand new cables.
So basically try a different port/cable.
Click to expand...
Click to collapse
Thank you very much.
I will try every port I find on every device I find.
What shoul I do if I find that it works somewhere?
Should I simply run flash-all.bat?
I want to go back to full stock.
It's weird because that cable and that port work very well for data transfer and adb actually works. Fastboot works as well...
Is the problem in that command only?
I had a similar issue. I had to use a different PC to get my phone back to work. Try restarting the pc or a create a different user in Windows and see if that helps. Also there is a very useful script called Deus script on the forums here for bootloops try it.
dabaang_khan said:
I had a similar issue. I had to use a different PC to get my phone back to work. Try restarting the pc or a create a different user in Windows and see if that helps. Also there is a very useful script called Deus script on the forums here for bootloops try it.
Click to expand...
Click to collapse
Do you mean Deuces? I tried it. Should I try it again on a different computer?
jan_ruc said:
Thank you very much.
I will try every port I find on every device I find.
What shoul I do if I find that it works somewhere?
Should I simply run flash-all.bat?
I want to go back to full stock.
It's weird because that cable and that port work very well for data transfer and adb actually works. Fastboot works as well...
Is the problem in that command only?
Click to expand...
Click to collapse
Yeah, the case was the same for me.
Super weird issue.
OH, there's one more thing I can think of. What OS are you running? If it's Windows 10, it could also be that. MS and their automatic updates override Google's driver so I always disabled that. It's weird, but that was another issue I had at some point.
You might see a LeLand driver or something similar for it, I don't remember the exact name. So that's also something to look into if you can.
For full stock run flash-all.bat, this will erase all the phone's data though.
Ran into the same issue few days ago, changing cables and ports didn't help but restarting the computer several times did.
Ariac Konrel said:
Yeah, the case was the same for me.
Super weird issue.
OH, there's one more thing I can think of. What OS are you running? If it's Windows 10, it could also be that. MS and their automatic updates override Google's driver so I always disabled that. It's weird, but that was another issue I had at some point.
You might see a LeLand driver or something similar for it, I don't remember the exact name. So that's also something to look into if you can.
For full stock run flash-all.bat, this will erase all the phone's data though.
Click to expand...
Click to collapse
I do have a laptop that is running Win 7 and my father's laptop that has Vista on it for some reason.
Also I relaized my friend has a Type-C port on his desktop so will probably give that a try, and use the original cable.
I forced a Google backup before I messed it up so I don't really care about the data.
By the way what's the matter with the
"fastboot: error: Device does not support slots"?
Is that anything critical? Or just another weird error because of the cable/port?
Also: I did some digging throu the system files with TWRP and most of the root directories are empty...
jan_ruc said:
I do have a laptop that is running Win 7 and my father's laptop that has Vista on it for some reason.
Also I relaized my friend has a Type-C port on his desktop so will probably give that a try, and use the original cable.
I forced a Google backup before I messed it up so I don't really care about the data.
By the way what's the matter with the
"fastboot: error: Device does not support slots"?
Is that anything critical? Or just another weird error because of the cable/port?
Also: I did some digging throu the system files with TWRP and most of the root directories are empty...
Click to expand...
Click to collapse
See, look at all the advice you got. From what I've read, your USB cables appears to be your #1 issue. Like others have said, get a good USB A to USB C cable, and you'll likely be ok ?
Badger50 said:
See, look at all the advice you got. From what I've read, your USB cables appears to be your #1 issue. Like others have said, get a good USB A to USB C cable, and you'll likely be ok
Click to expand...
Click to collapse
Indeed, thank you! I'm actually kinda stuck installing the newest ADB and drivers right now... Can someone share a link to the latest 8.1 image avadible for this phone and the adb that I need, please? This laptop is currently quite clean and I really don't want to mess around anymore.
Thank you all!
jan_ruc said:
Indeed, thank you! I'm actually kinda stuck installing the newest ADB and drivers right now... Can someone share a link to the latest 8.1 image avadible for this phone and the adb that I need, please? This laptop is currently quite clean and I really don't want to mess around anymore.
Thank you all!
Click to expand...
Click to collapse
Here's the factor image page. Just look for Taimen, June image at the bottom of the section. Use the OPM2 unless your on T-Mobile.
https://developers.google.com/android/images
And this is the SDK/platform-tools that I use that also has the adb interface ?
https://developer.android.com/studio/releases/platform-tools
Badger50 said:
Here's the factor image page. Just look for Taimen, June image at the bottom of the section. Use the OPM2 unless your on T-Mobile.
https://developers.google.com/android/images
And this is the SDK/platform-tools that I use that also has the adb interface
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Thanks! Now I simply extracted the platform-tools in a folder C:\adb.
Downloaded the image, but the phone won't show up when I run adb devices...
On Windows 7... On my desktop it shows up the sec I run it.
Installed Google drivers as well.
Say could I simply "adb push" the image on the phone and flash it from TWRP?
"adb push" works. I just tried and pushed the image on the phone. But it says "invalid zip file format".
Could I extract the zip and push all the images one by one?
jan_ruc said:
Thanks! Now I simply extracted the platform-tools in a folder C:\adb.
Downloaded the image, but the phone won't show up when I run adb devices...
On Windows 7... On my desktop it shows up the sec I run it.
Installed Google drivers as well.
Say could I simply "adb push" the image on the phone and flash it from TWRP?
"adb push" works. I just tried and pushed the image on the phone. But it says "invalid zip file format".
Could I extract the zip and push all the images one by one?
Click to expand...
Click to collapse
You've got to get in the mindset that though adb and SDK/platform-tools are part of each other, they are also different. Adb is mostly used when your device is on, whereas sdk/platform-tools is used as your bootloader interface, where you do your fastboot commands.
After you installed the SDK, there should be a folder within SDK named platform-tools. That's where your extracted files from the factory image go. You don't put the full factory image in there. The pics should give you an idea what I'm taking about. You'll actually open your command prompt on the platform-tools folder so you can execute your fastboot commands.
Badger50 said:
You've got to get in the mindset that though adb and SDK/platform-tools are part of each other, they are also different. Adb is mostly used when your device is on, whereas sdk/platform-tools is used as your bootloader interface, where you do your fastboot commands.
After you installed the SDK, there should be a folder within SDK named platform-tools. That's where your extracted files from the factory image go. You don't put the full factory image in there. The pics should give you an idea what I'm taking about. You'll actually open your command prompt on the platform-tools folder so you can execute your fastboot commands.
Click to expand...
Click to collapse
Now I have installed Android Studio and selected the SDK tools that weren't selected before and installed them.
Still my question remains... Since the USB cable is the problem, could I flash it from TWRP? I don't mind keeping TWRP installed so if I could just reinstall the OS. That would be lovely.
On the other hand. Tell me what to do, and I'll do it.
Another route to go of your struggling with paths is my convoluted method that works for me. Every month I download the latest factory image and the latest platform tools and extract both to the same folder. I also put the TWRP.img file and also dueces script there too. So each month I have a stand alone installation. I have used the dueces script the last two months with good results. (I just like having both slots up to date in case I install a custom Rom). If you choose to go the route with the script there is an additional zip file to extract. At the end, all the loose files are in one directory beside some folders for platform tools. Let us know if you need additional info. Note for June they changed something in the syntax so dueces made a new version of the script. Here are the files in my latest dir.
deuce-flash-all-v4.5.bat
platform-tools-latest-windows.zip
taimen-opm2.171026.006.c1-factory-21236059.zip
Twrp-3.2.1-2-taimen.img
CyberpodS2 said:
Another route to go of your struggling with paths is my convoluted method that works for me. Every month I download the latest factory image and the latest platform tools and extract both to the same folder. I also put the TWRP.img file and also dueces script there too. So each month I have a stand alone installation. I have used the dueces script the last two months with good results. (I just like having both slots up to date in case I install a custom Rom). If you choose to go the route with the script there is an additional zip file to extract. At the end, all the loose files are in one directory beside some folders for platform tools. Let us know if you need additional info. Note for June they changed something in the syntax so dueces made a new version of the script. Here are the files in my latest dir.
deuce-flash-all-v4.5.bat
platform-tools-latest-windows.zip
taimen-opm2.171026.006.c1-factory-21236059.zip
Twrp-3.2.1-2-taimen.img
Click to expand...
Click to collapse
At the moment all I really want is to get this phone working...
I just re-ran the flash-all.bat with the same set of folders as you have and got this:
< waiting for any device >
Sending 'bootloader_a' (36380 KB) OKAY [ 0.937s]
Writing 'bootloader_a' FAILED (remote: Flashing is not allowed for Critical Partitions
)
Finished. Total time: 0.947s
rebooting into bootloader OKAY [ 0.002s]
Finished. Total time: 0.002s
fastboot: error: Failed to identify current slot
rebooting into bootloader OKAY [ 0.002s]
Finished. Total time: 0.003s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: TMZ12g
getvar:version-baseband FAILED (remote: unknown command)
fastboot: error: requirements not met!
Press any key to exit...
So I guess that means criticlal is locked?
I ran fastboot flashing unlock_critical:
fastboot flashing unlock_critical
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.002s
EDIT*: I rebooted the phone in hopes of you know... Any progress. It seems to be stuck on the "G" loading screen.
From this point could I just flash a custum ROM via TWRP?
I just want it to work.