Related
Alright so last night i was able to unlock my phone and root it no problem on my mac computer (which I regret and wish i did it on windows) but the phone worked great after. But after debating if I should unroot I went ahead and tried unrooting the phone but the phone would not activate, it became stuck in bootloader. Ive tried everything that I could look up online and even called google for help but they said to search online and ask the developers. Ive tried flashing the stock image back on but it wouldnt work, it kept saying ivalid boot image header fastboot reason fall-through from normal boot mode. I dont even think my computer is recognizing the phone anymore so I dont know how I would get back into terminal to flash anything. If anyone can help me I would appreciate it. I have no idea what to do now after trying for a whole day. Thanks all, hope someone can be a savior.
Firstly, if you want help... please please please use paragraphs and lines and not 1 blob of text. It makes it extremely difficult to know your problem.
Secondly, do not ever call Google or Motorola (or any manufacturer) or any carrier for help. What you do on XDA is not their problem, that is why there is a warning when you unlock the bootloader.
Third, if you're able to get into bootloader mode then you can fix your phone by flashing the stock images. You most likely had the wrong environment or it is not set up properly to flash the stock images.
If you don't feel comfortable doing this kind of stuff, stick to using the phone out of the box rather than tinkering with it.
zephiK said:
Firstly, if you want help... please please please use paragraphs and lines and not 1 blob of text. It makes it extremely difficult to know your problem.
Secondly, do not ever call Google or Motorola (or any manufacturer) or any carrier for help. What you do on XDA is not their problem, that is why there is a warning when you unlock the bootloader.
Third, if you're able to get into bootloader mode then you can fix your phone by flashing the stock images. You most likely had the wrong environment or it is not set up properly to flash the stock images.
If you don't feel comfortable doing this kind of stuff, stick to using the phone out of the box rather than tinkering with it.
Click to expand...
Click to collapse
Yea, my bad. I typed it in a hurry on my phone.
Bootloader is the only screen I am able to get into. Whatever option I choose and hit power, all it does is flash the screen and go back to bootloader.
The stock image I download was from the google developers page but it did not work.
Will anything even work if my computer doesn't recognize the phone? If so how would I go about doing it?
I used to this this years ago and never ran into problems, just for some reason when I tried to unroot it messed up.
Is there anyway to possibly delete the terminal so I could start over and re-root it??
Anyways thanks for your response.
Is the device recognized by the fastboot command when connected to either the mac or pc?
zylstrajs said:
Is the device recognized by the fastboot command when connected to either the mac or pc?
Click to expand...
Click to collapse
Not sure to be exact, if I just go into terminal and enter "adb devices" nothing will pop up but if I enter cd then space and drag the android file into it, it wont say my device number anymore it'll say device. I'm wondering if I could somehow delete my terminal and possibly start over?
dnasr87 said:
Not sure to be exact, if I just go into terminal and enter "adb devices" nothing will pop up but if I enter cd then space and drag the android file into it, it wont say my device number anymore it'll say device. I'm wondering if I could somehow delete my terminal and possibly start over?
Click to expand...
Click to collapse
Adb is for android. You want to use the command: fastboot devices
dnasr87 said:
Yea, my bad. I typed it in a hurry on my phone.
Bootloader is the only screen I am able to get into. Whatever option I choose and hit power, all it does is flash the screen and go back to bootloader.
The stock image I download was from the google developers page but it did not work.
Will anything even work if my computer doesn't recognize the phone? If so how would I go about doing it?
I used to this this years ago and never ran into problems, just for some reason when I tried to unroot it messed up.
Is there anyway to possibly delete the terminal so I could start over and re-root it??
Anyways thanks for your response.
Click to expand...
Click to collapse
If you want to start over you'd want to be flashing the stock images https://developers.google.com/android/nexus/images
Have your phone in bootloader mode (vol down + power)
Go into the directory with fastboot and type fastboot devices.
If your environment is set up properly then it should display your device as the output. From there you can flash back to stock.
dnasr87 said:
Not sure to be exact, if I just go into terminal and enter "adb devices" nothing will pop up but if I enter cd then space and drag the android file into it, it wont say my device number anymore it'll say device. I'm wondering if I could somehow delete my terminal and possibly start over?
Click to expand...
Click to collapse
what does it say why you type
>fastboot devices
zylstrajs said:
what does it say why you type
>fastboot devices
Click to expand...
Click to collapse
command not found, but all I did was open terminal and entered fastboot devices. Not sure if I should enter anything before it.
dnasr87 said:
command not found, but all I did was open terminal and entered fastboot devices. Not sure if I should enter anything before it.
Click to expand...
Click to collapse
You have to change directory to the folder that contains fastboot. Do you even have fastboot environment set up? You need that.
Google search on how to set it up before posting back. There are many guides on XDA on how to accomplish this.
Okay, your environment isn't set up ideally. Follow these instructions to install fastboot and adb on your PC.
http://forum.xda-developers.com/showthread.php?t=2317790
---
Once you've done and you get a reply to the following command, you can move on.
>fastboot devices
---
open the google factory image file (using something like 7zip) : shamu-lrx21o-factory-e028f5ea.tgz
There is a folder in the .tgz file. Extract the contents of that folder to the directory listed for your command prompt (where you successfully ran fastboot just before).
> fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
>fastboot flash radio radio-shamu-d4.0-9625-02.55.03a.img
>fastboot reboot-bootloader
---
The device will reboot. Don't close the terminal window. Now, extract the contents of image-shamu-lrx21o.zip to the same folder that you've been working in. The folder that contains the bootloader and radio files you just flashed.
---
>fastboot flash recovery recovery.img
>fastboot flash boot boot.img
>fastboot flash system system.img
Some time will pass, this img may be sent in parts.
>fastboot flash cache cache.img
>fastboot flash userdata userdata.img
>fastboot reboot
zephiK said:
You have to change directory to the folder that contains fastboot. Do you even have fastboot environment set up? You need that.
Google search on how to set it up before posting back. There are many guides on XDA on how to accomplish this.
Click to expand...
Click to collapse
I did when I rooted it then once it crashed I tried to start over but wiped my computer.. I'll re download and try again
zylstrajs said:
Okay, your environment isn't set up ideally. Follow these instructions to install fastboot and adb on your PC.
http://forum.xda-developers.com/showthread.php?t=2317790
---
Once you've done and you get a reply to the following command, you can move on.
>fastboot devices
---
open the google factory image file (using something like 7zip) : shamu-lrx21o-factory-e028f5ea.tgz
There is a folder in the .tgz file. Extract the contents of that folder to the directory listed for your command prompt (where you successfully ran fastboot just before).
> fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
>fastboot flash radio radio-shamu-d4.0-9625-02.55.03a.img
>fastboot reboot-bootloader
---
The device will reboot. Don't close the terminal window. Now, extract the contents of image-shamu-lrx21o.zip to the same folder that you've been working in. The folder that contains the bootloader and radio files you just flashed.
---
>fastboot flash recovery recovery.img
>fastboot flash boot boot.img
>fastboot flash system system.img
Some time will pass, this img may be sent in parts.
>fastboot flash cache cache.img
>fastboot flash userdata userdata.img
>fastboot reboot
Click to expand...
Click to collapse
I did it on my mac, if i try to connect my phone to a pc it wont recognize it because its stuck in bootloader. I have already tried connecting it
Why does this thread make me LoL so much?
This thread is all over the place. Are you using your PC or Mac right now to do this? If it is a PC, what does Device Manager say when you plug your phone in while its in Bootloader mode?
PaisanNYC said:
Why does this thread make me LoL so much?
This thread is all over the place. Are you using your PC or Mac right now to do this? If it is a PC, what does Device Manager say when you plug your phone in while its in Bootloader mode?
Click to expand...
Click to collapse
Im using mac right now. I want to start from scratch, not sure if possible. but nothing really shows when I connect the device. I think I wipe the software off my computer. Would I be able to start doing it all over on a pc even if its stuck on bootloader and computer wont recognize?
dnasr87 said:
Im using mac right now. I want to start from scratch, not sure if possible. but nothing really shows when I connect the device. I think I wipe the software off my computer. Would I be able to start doing it all over on a pc even if its stuck on bootloader and computer wont recognize?
Click to expand...
Click to collapse
Are you in the NYC area? I'd just come over with my laptop and do it for you.
PaisanNYC said:
Are you in the NYC area? I'd just come over with my laptop and do it for you.
Click to expand...
Click to collapse
Dude im in NH but at this point I will ship the phone to anyone who can fix it and I will pay you guys $100
PaisanNYC said:
Are you in the NYC area? I'd just come over with my laptop and do it for you.
Click to expand...
Click to collapse
dnasr87 said:
Dude im in NH but at this point I will ship the phone to anyone who can fix it and I will pay you guys $100
Click to expand...
Click to collapse
not necessary some one can just use hangouts remote desktop to help you i thinks that's what they use on xda assist
Acer ADB
Your PC might not be recognizing because you got the Acer ADB of doom...
Just roll back your driver.
dnasr87 said:
Dude im in NH but at this point I will ship the phone to anyone who can fix it and I will pay you guys $100
Click to expand...
Click to collapse
Don't send it to a stranger on the internet. You never know who is who behind a screen lol
Honestly bro, if i were close to you, I'd just do it for you. I have the stock image, drivers, and adb/fastboot all set up. i'm good at fixing things, horrible at explaining things.
Hi,
My friends Moto G just died and now it is just bootlooping. He asked me to try get contacts through ADB but it is not finding phone.
I installed Motorola Device Manager and it seems that it found phone and successfully used command "get variable", but when I use ADB via CMD it don't even finding phone.
How can I fix this?
Tenderenden said:
Hi,
My friends Moto G just died and now it is just bootlooping. He asked me to try get contacts through ADB but it is not finding phone.
I installed Motorola Device Manager and it seems that it found phone and successfully used command "get variable", but when I use ADB via CMD it don't even finding phone.
How can I fix this?
Click to expand...
Click to collapse
at first learn what ADB is.
at second - fastboot it the proper place to begin with.
PsyClip-R said:
at first learn what ADB is.
at second - fastboot it the proper place to begin with.
Click to expand...
Click to collapse
Well, fastboot don't want to work neither so that answer didn't help at all
Tenderenden said:
How can I fix this?
Click to expand...
Click to collapse
ADB can only be used from a fully booted device (you have to be past the login screen. It's a security measure so no one can mess with your data without approval). You can use fastboot commands though.
Try this
Download Minimal ADB and Fastboot and install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installtion or the desktop shortcut you choose to create and selecting "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
XXXXXXXXXXfastboot
Now do your thing, like flashing stock ROM. Multiple tutorials exist for that.
doppelhelix said:
ADB can only be used from a fully booted device (you have to be past the login screen. It's a security measure so no one can mess with your data without approval). You can use fastboot commands though.
Try this
Download Minimal ADB and Fastboot and install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installtion or the desktop shortcut you choose to create and selecting "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
XXXXXXXXXXfastboot
Now do your thing, like flashing stock ROM. Multiple tutorials exist for that.
Click to expand...
Click to collapse
That is the answer that I needed!
Can I somehow pull data from this phone using fastboot? Because I think that flashing stock ROM will erase any personal data, but I really need to get it.
Tenderenden said:
That is the answer that I needed!
Can I somehow pull data from this phone using fastboot?
Click to expand...
Click to collapse
No. That would defeat the lock screen. Just imagine someone steals your phone and can access your data just by booting into fastboot.
doppelhelix said:
No. That would defeat the lock screen. Just imagine someone steals your phone and can access your data just by booting into fastboot.
Click to expand...
Click to collapse
Okay, I got it. Now, have you got any suggestions how to get contacts and (hopefully) SMS back?
Tenderenden said:
how to get contacts and (hopefully) SMS back?
Click to expand...
Click to collapse
Contacts are synchronised with your Google account (unless you choosed not to). Can't say the same about SMS.
doppelhelix said:
No. That would defeat the lock screen. Just imagine someone steals your phone and can access your data just by booting into fastboot.
Click to expand...
Click to collapse
Loading custom recovery via
fastboot boot TWRP.img should do the job.
than one can can make a full backup, which might be extracted on pc as a regular archive.
PsyClip-R said:
Loading custom recovery via
fastboot boot TWRP.img should do the job.
Click to expand...
Click to collapse
Does this work with locked bootloader? That would be really messed up.
Tenderenden said:
Hi,
My friends Moto G just died and now it is just bootlooping. He asked me to try get contacts through ADB but it is not finding phone.
I installed Motorola Device Manager and it seems that it found phone and successfully used command "get variable", but when I use ADB via CMD it don't even finding phone.
How can I fix this?
Click to expand...
Click to collapse
Is your bootloader locked?
Can you try fastboot oem partition dump userdata (using mfastboot, not Google's fastboot)?
PsyClip-R said:
Loading custom recovery via
fastboot boot TWRP.img should do the job.
than one can can make a full backup, which might be extracted on pc as a regular archive.
Click to expand...
Click to collapse
I will try that. Firstly my friend want to message the seller to get his phone repaired. So I can not touch anything in software until he is done.
doppelhelix said:
Contacts are synchronised with your Google account (unless you choosed not to). Can't say the same about SMS.
Click to expand...
Click to collapse
Unfortunately in this case contacts weren't synchronised.
LuK1337 said:
Is your bootloader locked?
Can you try fastboot oem partition dump userdata (using mfastboot, not Google's fastboot)?
Click to expand...
Click to collapse
Well, it seems that I have to read something more about what you said here firstly xD
And the bootloader is locked.
But I appreciate any new idea that may lead to solving this problem.
Tenderenden said:
I will try that. Firstly my friend want to message the seller to get his phone repaired. So I can not touch anything in software until he is done.
Unfortunately in this case contacts weren't synchronised.
Well, it seems that I have to read something more about what you said here firstly xD
And the bootloader is locked.
But I appreciate any new idea that may lead to solving this problem.
Click to expand...
Click to collapse
fastboot oem partition dump userdata may work with locked BL and it'd be great to know if it does...
LuK1337 said:
fastboot oem partition dump userdata may work with locked BL and it'd be great to know if it does...
Click to expand...
Click to collapse
I will try it as fast as I can. Thanks
I bought a Nexus6 about a month ago. I wasn't planning on rooting it, but I have rooted a number of devices in the past so am reasonably comfortable doing that. I bought the phone from Amazon but I am on T-mobile's network.
After I fired up the phone and used it for a while, I got a message asking me to update to software version 5.1. When I go to the about on my phone, it says it has 5.1.1 but it says the build number is LRX22C which when I looked that up indicates that it is actually running 5.0. I told the phone to update, but it fails every time (android guy with the red exclamation mark over his belly). I did a factory reset and repartition and still the same thing. At this point, I figured I would just root and and force it to 6.0.
After installing drivers, ADB-tools, etc. my computer recognizes the phone. When I connect by a USB cable and the phone is on, it shows under devices. However, when I boot into fastboot mode, my laptop no longer recognizes the Nexus. The fastboot screen shows that the phone is unlocked, and it recognizes that it is getting power from the laptop. However, it says to connect via usb. Running the command prompt and using SDK-Windows, when I type fastboot devices it shows nothing.
Interestingly, I see that Superuser is on the phone and working. I don't think I rooted my phone at any point in the process of trying a lot of different things, although anything is possible. I have been thrashing around a bit trying to get this to get the phone on 6.0 so might have rooted accidentally although I doubt it. My suspicion is that I was given a previously used phone that someone rooted and returned.
Any suggestions/help out there?
When in Fastboot Mode, what does Device Manager show? Does it see the device correctly, or is it showing a yellow triangle w/ exclamation point over the device?
RMarkwald said:
When in Fastboot Mode, what does Device Manager show? Does it see the device correctly, or is it showing a yellow triangle w/ exclamation point over the device?
Click to expand...
Click to collapse
It shows Other Devices > Fastboot Shamu S with the yellow triangle and exclamation point. I have motorolla device manager installed and I thought that had my drivers covered but perhaps not?
These devices do have driver issues. Try downloading the correct drivers and it should fix it, a lot of people have had similar issues.
@LSquared
Download Wugfresh Nexus Root Toolkit. It has a long button on the top right "Install and test drivers" - a really helpful guide in clearing out any old drivers and installing and testing the new ones.
It can also perform many other functions, but after a lot of persuasion(!) in these forums I decided that learning to do everything manually is not only simple but safer, because you know at exactly which point an error occurs. The driver setup part of NRT is a brilliant help in setting your PC up once to get you started.
If you don't have anything valuable on your device yet, install the MMB29S factory image, then TWRP, and from there install SuperSU v2.66, and you're as up to date as you can possibly be.
Spend a few hours doing research and you will be fine. Just stay away from root kits. They only make things worse and lessen the experience of owning a nexus. As well as stops any help you may get in the forums as no one will help those that use the root kits.
Thanks for all the help/suggestions. After a lot of poking around, I realized that I had the right driver hiding in a folder (inside SDK I think) and had to just manually point to them and that got rid of the connection issue. Now I seem to be stuck on flashing the latest stock OS. I have been trying to flash via Minimal ADB and Fastboot but it isn't pushing the image there correctly. I don't want a custom rom, just stock 6.0.
LSquared said:
Thanks for all the help/suggestions. After a lot of poking around, I realized that I had the right driver hiding in a folder (inside SDK I think) and had to just manually point to them and that got rid of the connection issue. Now I seem to be stuck on flashing the latest stock OS. I have been trying to flash via Minimal ADB and Fastboot but it isn't pushing the image there correctly. I don't want a custom rom, just stock 6.0.
Click to expand...
Click to collapse
How are you trying to push the files, I assume Fastboot, are you getting an error? Is your Android SDK up-to-date?
LSquared said:
I have been trying to flash via Minimal ADB and Fastboot but it isn't pushing the image there correctly. I don't want a custom rom, just stock 6.0.
Click to expand...
Click to collapse
Google updated fastboot a little over a year ago to allow flashing the very large system.img files. Minimal ADB & Fastboot does not have this update (I believe). Download the latest Android SDK and you'll be good to go.
cam30era said:
Google updated fastboot a little over a year ago to allow flashing the very large system.img files. Minimal ADB & Fastboot does not have this update (I believe). Download the latest Android SDK and you'll be good to go.
Click to expand...
Click to collapse
I just downloaded Android SDK so it has the latest files (I believe). Android SDK doesn't connect to the phone, it just keeps an updated set of firmwear, right? If I am not using minimal ADB and fastboot to push files from my computer to the phone, what program should I be using? It seemed a lot easier on my older phones that had a micro SD card because I could just drop the new Rom on there and install that from the bootloader.
LSquared said:
If I am not using minimal ADB and fastboot to push files from my computer to the phone, what program should I be using?
Click to expand...
Click to collapse
Use the ADB and fastboot that are included with the Android SDK that you downloaded. They are in the Platform-Tools folder.
cam30era said:
Use the ADB and fastboot that are included with the Android SDK that you downloaded. They are in the Platform-Tools folder.
Click to expand...
Click to collapse
If I click on either of those to run the application, it flashes a box for a split second and then nothing. I guess I am missing a step?
LSquared said:
If I click on either of those to run the application, it flashes a box for a split second and then nothing. I guess I am missing a step?
Click to expand...
Click to collapse
I would suggest reading and following this guide >http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot
cam30era said:
I would suggest reading and following this guide >http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot
Click to expand...
Click to collapse
That guide is great and helped me get the bootloader unlocked and the phone rooted. I downloaded the image file just fine, but when I go to run root-windows.bat I get the message "fastboot is not recognized as an internal or external command." I am guessing I don't have some file in the right location?
LSquared said:
That guide is great and helped me get the bootloader unlocked and the phone rooted. I downloaded the image file just fine, but when I go to run root-windows.bat I get the message "fastboot is not recognized as an internal or external command." I am guessing I don't have some file in the right location?
Click to expand...
Click to collapse
The flash_all scripts don't work. Flash each img file individually, after you've extracted them all from the ,zip.
Yup, flash the .img files individually, the batch command doesn't work.
Here's the guide I always use: How to manually flash img files to your Nexus device
Basically, with phone connected to computer and booted to the bootloader, open Command Prompt window, change directories to where your sdk/platform-tools directory is with your Shamu files, then:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Code:
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
Code:
fastboot flash radio "name of radio"
fastboot reboot-bootloader
NOTE: You'll have to extract the files from the image-shamu-mmb29s.zip file in this case to flash MMB29S.
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
Code:
fastboot reboot
I'm aware, it may be overkill, but I've never had any issues performing all of these steps to get back to 100% stock so if it "isn't broken, don't fix it". Also this will wipe your internal SD area, so any files you want to save you should save them prior to starting this.
Good summary!
RMarkwald said:
Also this will wipe your internal SD area, so any files you want to save you should save them prior to starting this.
Click to expand...
Click to collapse
To avoid wiping your internal user storage, just skip the step that flashes userdata img (and the step at the beginning that erases usedata)
Hello!
I think i've bricked my Mi A2.
I have unlocked bootloader but locked critical partition which i cant unlock cause theres no OS to boot into and check the OEM option. Are there any alternatives before opening the phone for EDL?
xunixbeatsx said:
Hello!
I think i've bricked my Mi A2.
I have unlocked bootloader but locked critical partition which i cant unlock cause theres no OS to boot into and check the OEM option. Are there any alternatives before opening the phone for EDL?
Click to expand...
Click to collapse
if you can at least boot on fastboot and it's working, you can enter on edl mode from fastboot, there is a command to do it
Adairo said:
if you can at least boot on fastboot and it's working, you can enter on edl mode from fastboot, there is a command to do it
Click to expand...
Click to collapse
Yeah already tried that but adb wont work
"no devices / emulators found". I think my computer cant see this devices mode, i also cant mount it when i use Clockwork.
I can use fastboot commands just fine though
xunixbeatsx said:
Yeah already tried that but adb wont work
"no devices / emulators found". I think my computer cant see this devices mode, i also cant mount it when i use Clockwork.
I can use fastboot commands just fine though
Click to expand...
Click to collapse
You should try flashing the ROM normally. Just use the included script
ADB commands works only booted phone with USB dev mode.
Fastboot commands with fastboot mode. So you cant use ADB commands when your phone not booted up.
Daniesz said:
ADB commands works only booted phone with USB dev mode.
Fastboot commands with fastboot mode. So you cant use ADB commands when your phone not booted up.
Click to expand...
Click to collapse
You dont have to boot phone to use ADB, you can adb sideload inside Clockwork (i sideloaded no-verity just fine).
By the way i managed to fix my phone by extracting the firmware and fastboot flash files one by one (2 files couldnt be installed cause they needed critical partition unlocked but it seems they werent anything critical cause phone works fine).
xunixbeatsx said:
Yeah already tried that but adb wont work
"no devices / emulators found". I think my computer cant see this devices mode, i also cant mount it when i use Clockwork.
I can use fastboot commands just fine though
Click to expand...
Click to collapse
Enter to fastboot Is all you need to get into edl mode and attemp to flash stock rom
Adairo said:
Enter to fastboot Is all you need to get into edl mode and attemp to flash stock rom
Click to expand...
Click to collapse
I tried that and was no response from the phone.
I also tried edl from ADB, phone restarted but no edl mode.
xunixbeatsx said:
I tried that and was no response from the phone.
I also tried edl from ADB, phone restarted but no edl mode.
Click to expand...
Click to collapse
I've thé same issue. If you fastboot is "broken" you dont have choice you need to short pin (it's easy)..
xunixbeatsx said:
I tried that and was no response from the phone.
I also tried edl from ADB, phone restarted but no edl mode.
Click to expand...
Click to collapse
Did you try to just run the script with the fastboot commands? If you didn't modify critical partitions it should just work fine. Just ignore the error messages
Benjamin_L said:
Did you try to just run the script with the fastboot commands? If you didn't modify critical partitions it should just work fine. Just ignore the error messages
Click to expand...
Click to collapse
I manually fastboot flash the files which i suppose is the same as with running the script, but i wanted to see which files wont get transfered cause of the locked critical partition. Android installed fine but couldnt install updates (edit: Thats probably because i rooted my device, it seems you cant automatic upgrade if you root) so i enabled OEM, unlocked critical partition, flashed normally with MiFlash tool, everythings like new now.
Now i only need a working Xposed Framework version.
Hi all,
I'm encountering a very annoying issue with my brand new Zenfone 8.
I wanted to install the last LineageOS image, but now my phone seems stuck.
Here are what I did:
- Unlocked the bootloader: success with the ASUS APK after a few tries (error 11000 and 11006 ans eventually worked).
- Rebooted to bootloader
- Entered into recovery
- Used fastboot to flash the vendor partition.
At this point, everything looked OK. But then.... :
- Powered off the phone and restarted to bootloader.
- Tried to enter into recovery to flash the Lineage Recovery
But at this point, I had a ASUS logo stucked on the screen.
I can't do anything with adb or fastboot commands.
I tried the method explained here (https://www.asus.com/Content/Android-13-Beta/) to rollback to stock Android 12, but nothing happened too: I looked at the shell script (I'm on Linux) and I reckon that it stucks on fastboot command (the phone is in the bootloader).
Any idea about what failed? The last command used (vendor partition flash) said "OKAY".
And especially, what can I do now? Any way to reinstall the ASUS recovery?
Thanks in advance guys.
Not quite sure what your status is if you say "can't do anything with adb or fastboot commands". I've flashed Zenfones a couple of times (my household has 3 Zenfone 8's on LineageOS) and I had one that went into ramdump. I recovered from that using fastboot to manually reflash all 19 firmware partitions, in both slots. That got the phone out of ramdump, and I got to continue the upgrade to the new LineageOS. So: if you can boot to the fastboot environment, then that would be a road that might leaed you out. But if you can't even get a response to the command "fastboot devices" then I don't know of a course of action for you.
To use fastboot commands I had to run the phone into bootloader mode, then to "recovery" and eventually "fastboot" (I'm note 100% sure but it's what I remembered).
Without that, I was unable to use any fastboot commands like device or flash.
And now the issue is that I'm not able to go to recovery/fastboot again, because I have just the ASUS logo and nothing else.
It looks like that the stock recovery was dead, but I don't know why - and I don't know how to fix/reset it.
From the bootloader you should be able to flash the raw image again, it should flash everything
Adaoh said:
From the bootloader you should be able to flash the raw image again, it should flash everything
Click to expand...
Click to collapse
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.
semurel said:
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.
Click to expand...
Click to collapse
On Linux and maybe macs too you need to run fastboot commands as Root (sudo fastboot devices) for example. The raw image script should ask you for your Root password for this reason
Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).
semurel said:
Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).
Click to expand...
Click to collapse
Yes, they work from the bootloader, I always run the script from the BL too. Ironically, I had issues running fastboot commands from fastbootd for installing Omnirom, so I did it all in the bootloader and all worked fine.
I am not sure I can help you more at this point, it looks like it maybe got interrupted mid flashing and now something is wrong somewhere. Maybe if you look inside the bash script file you can find the command that it got stuck on and run that manually if you manage to get fastboot command access.
Strange - they have never worked from the bootloader. I tried that before according to the LineageOS wiki. I thought it was a mistake and use the recovery > fastboot to do that. I dont like that - I hope it's not a local version of the Zenfone or something like that.
I'm not at home tonight but yes I'll try to find commands not requiering the fastboot command.
Unfortunately all commands from the script are using fastboot. And as "fastboot devices" sees nothing, I can't do anything.
I've tried from the bootloader screen (with start, recovery, poweroff option) - from the start screen showing unlocked bootloader warning and from the ASUS logo when I try to start the recovery. I've tried the commands/scripts with Linux and Windows: same result.
So :
- I can't use any fastboot commands.
- I don't have the ASUS recovery.
Speaking of the ASUS recovery, I've found screenshots on internet and they don't have a "fastboot" submenu (I'm not sure it's a Zenfone 8). May had I a different version?
I don't like that. If I don't have others option, I guess that the warranty doesn't work because the phone is unlocked?
I eventually found a solution! I've tried with my old OnePlus cable and fastboot commands start working from the bootloader screen.
I have no idea why my other cable was faulty (it can charge the phone and executes commands from the Recovery > Fastboot menu - but not on the BL screen).
Anyway my problem is now fixed.
Thanks all for help and support.