Related
Okay so i unlocked my bootloader, that went well (as if thats hard)
and then i used Modacos superboot to root, it rooted (except for some reason the super user application opens to just a black screen). After that i continued to flash the recovery so that i can flash Cyanogen. When i try to flash the recovery i keep on getting the error 'cannot load'. i've tried like 4 different recovery roms. Not sure what im doing wrong
Oh and this has been tried on 2 different computers. One win7 and one XP. both gave the same output
_-..zKiLLA..-_ said:
Okay so i unlocked my bootloader, that went well (as if thats hard)
and then i used Modacos superboot to root, it rooted (except for some reason the super user application opens to just a black screen). After that i continued to flash the recovery so that i can flash Cyanogen. When i try to flash the recovery i keep on getting the error 'cannot load'. i've tried like 4 different recovery roms. Not sure what im doing wrong
Oh and this has been tried on 2 different computers. One win7 and one XP. both gave the same output
Click to expand...
Click to collapse
what commands are you using to flash Amon_RA's recovery image? i also assume you're at the white bootloader screen when trying to flash Amon_RA's recovery image. also, to confirm root access, download the N1 Torch app and if it works, you're rooted.
Yes the screen is white. And i am using "fastboot flash recovery recovery-RA-nexus-v1.7.0-cyan.img"
Cannot load what - fastboot or the ROM .img file? Do you have fastboot-windows.exe in the same directory as the rom image?-(not necessary if fastboot command works for you)
Type fastboot devices to double check your link between pc and phone. If not check usb cable & drivers.
Make sure ur unlock is right before flashing Amon. If you've rooted then you should see an unlocked-lock image (the the google Xscreen) while booting, or the N1 torch app method as mentioned above.
_-..zKiLLA..-_ said:
Yes the screen is white. And i am using "fastboot flash recovery recovery-RA-nexus-v1.7.0-cyan.img"
Click to expand...
Click to collapse
Make sure you got to that white screen by pressing the trackball and not the volume rocker.
I renamed the recovery image to "recovery-RA-nexus-v1.7.0.img"
Code:
fastboot flash recovery recovery-RA-nexus-v1.7.0.img
Make sure you check
Code:
fastboot devices
and get your device number and also make sure you put it in the tools folder of the Android SDK
Make these steps
Boot ur phone into bootloader
1 Rename the img to recovery.img
2 Place the file in ur toolfolder where u have ur fastboot
3 Rightclik on toolfolder+Shift choose open cmd here
4 write fastboot devices to be shure u are connected
5 then write fastboot flash recovery recovery.img
hi,I have the problem too.I try many times but still stuck TRIANGLE WITH !.when I do recovery image
the screen come up "sending 'recovery"3948 kb.....ok
writing' recovery'......ok
sending 'recovery"3948 kb.....ok
writing' recovery'......ok
Click to expand...
Click to collapse
Code:
fastboot reboot
Finally got Amon_Ra's recovery to install
I started with a stock N1 with froyo
had a few stumbles along the way and lots of searching...lots and lots lol
using the how-to on the cyanogen page I went to the letter as ive never used ADB
So I installed the Latest Android SDK to get the ADB and Fastboot.
verified connection with "adb devices" command and so on
when I tried to flash amons the first time I got an error saying it couldn't open the file.
I checked to see if i had Super user with the LED flashlight app and I did not so I downloaded Super boot and it worked like a charm
tried again and got the same cannot open error.
I renamed the recovery image back to the original file name and triple checked everything else which didnt help.
at this point it was late and i was exhausted so my memory is fuzzy
but i had a few more issues and finally I installed the clock work app and installed clockwork recovery i then used that to flash amons because that is what i was familiar with from my G1 days.
I do remember I had to go into fast boot and select clear storage. I think thats what caused my N1 to hang on reboot after the ROM was flashed.
But It may have even been what caused my issues with the recovery image.
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.
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)
Ok so I was going about Trying to flash TWRP it wouldnt go. Tried a few times etc, nothing, so i gave up.
Now when i reboot or turn off and power up, i get a N/A in the top corner for a few seconds but then it boots up fine. But i cannot do a backup & reset, and i cant get into recovery now.
I get a start up failed your devices didnt start up successfully use the software repair assiant on your computer,
bottom says ap fastboot flashmode secure
error: failed to load kernel
fastboot reason: fall-through from recovery boot mode
but i can toggle to Start and it boots fine.
Computer now does not see the phone when i plug it in, it dont make a sound and is not in the device manager, also when i reboot to fastboot, it still isnt seen at all. flashing_unlocked so i can flash. but cant use adb since pc wont reconize phone now, and i cant reset.
So i can use the phone like normal atleast, but cant reset or access recovery. its like it just inst there
any ideas???
Thanks
Ok so the computer don't even ding when ya plug the phone I to it. On any computer I use. Is there a corrupted file that the phone uses when connecting to a computer... ?
Phone works fine.. just recovery is missing.. and with no way use to use adb... Is there any way to get the recovery back on?
Jtaxel said:
Ok so the computer don't even ding when ya plug the phone I to it. On any computer I use. Is there a corrupted file that the phone uses when connecting to a computer... ?
Phone works fine.. just recovery is missing.. and with no way use to use adb... Is there any way to get the recovery back on?
Click to expand...
Click to collapse
It would help to know what model your device is for one thing. Also, what command exactly did you use to flash the recovery? It almost sounds like you flashed the recovery to the wrong place or you did the erase command before trying to flash and borked the recovery partition.
ok,
Moto e4 plus, andrid 7.1.1
I did unlock the boot loader.
Security Patch - July 1 2018
Owens
xt1775
The TWRP on this site from git hub was only a zip file not in .img format, so i went TWRP official site and downloaded the one for the moto e4 plus
Put all files where they supposed to. did the adb,
first typed fastboot flash recovery.img that didnt work nothing at all, then did the right way,
fastboot flash recovery recovery.img, didnt work it was able to boot to recovery from adb, but not flash it.
tried a few times, no go, so after that, wheni reboot my phone, it goes straight to the bootloader screen and and says,
start up failed
your device didnt start up successfully use the software repair assisant on your omputer to repair your device.
ap fastboot mode ( secure)
error failed to load kernel!
fastbootReason: Fa;;-through from recovery boot mode
i can arrow down to start and it will start fine ( boot phone up normally )just goes to the n/a in top left for about 10 seconds then starts up normal. But i can NOW adb into my phone again and its reconized by the computer.
did i flash the wrong twrp?
Thanks
switch tools mode
ap fastboot mode (secure)
flashing_unlocked
gives cou emmc dram all that info also
Jtaxel said:
ok,
Moto e4 plus, andrid 7.1.1
I did unlock the boot loader.
Security Patch - July 1 2018
Owens
xt1775
The TWRP on this site from git hub was only a zip file not in .img format, so i went TWRP official site and downloaded the one for the moto e4 plus
Put all files where they supposed to. did the adb,
first typed fastboot flash recovery.img that didnt work nothing at all, then did the right way,
fastboot flash recovery recovery.img, didnt work it was able to boot to recovery from adb, but not flash it.
tried a few times, no go, so after that, wheni reboot my phone, it goes straight to the bootloader screen and and says,
start up failed
your device didnt start up successfully use the software repair assisant on your omputer to repair your device.
ap fastboot mode ( secure)
error failed to load kernel!
fastbootReason: Fa;;-through from recovery boot mode
i can arrow down to start and it will start fine ( boot phone up normally )just goes to the n/a in top left for about 10 seconds then starts up normal. But i can NOW adb into my phone again and its reconized by the computer.
did i flash the wrong twrp?
Thanks
switch tools mode
ap fastboot mode (secure)
flashing_unlocked
gives cou emmc dram all that info also
Click to expand...
Click to collapse
Try this twrp. It should work fine. Change the name to recovery.img and flash it
https://github.com/TwrpBuilder/andr...s/tag/TWRP-3.2.3-TwrpBuilder-2018-08-21_14-10
Jtaxel said:
The TWRP on this site from git hub was only a zip file not in .img format,
Click to expand...
Click to collapse
You unzip to extract the img file.
ST Dog said:
You unzip to extract the img file.
Click to expand...
Click to collapse
yep downloaded zip, extracted folder, just shows all the files, in a folder, not an image file
Jtaxel said:
yep downloaded zip, extracted folder, just shows all the files, in a folder, not an image file
Click to expand...
Click to collapse
That is the source not the image. Click on the link that ends with .img not .tar and you'll get an img
now if i try to fastboot boot recovery.img it boots to recovery but hangs on the recovery loading twrp screen.
and this error in adb now with any code i send
Jtaxel said:
now if i try to fastboot boot recovery.img it boots to recovery but hangs on the recovery loading twrp screen.
and this error in adb now with any code i send
Click to expand...
Click to collapse
You need to type in fastboot flash not fastboot boot. Boot will only "boot" the recovery but won't flash it onto your phone.
Jason M. said:
You need to type in fastboot flash not fastboot boot. Boot will only "boot" the recovery but won't flash it onto your phone.
Click to expand...
Click to collapse
yep i know, first time i tried this, it would boot when i type boot. BUT when i tried to FLASH it, it wouldnt flash and stay.
Now i cant even boot TWRP, just hangs on the TWRP logo screen. I let it sit for 5 mins, before it ould only take a few seconds.
BUT i am using the one from the offical site, not the one on github thats only a zip file.
unless someone has the img file from github.
BUT STILL like i said i get that error you see in CMD screenshot.
Jtaxel said:
yep i know, first time i tried this, it would boot when i type boot. BUT when i tried to FLASH it, it wouldnt flash and stay.
Now i cant even boot TWRP, just hangs on the TWRP logo screen. I let it sit for 5 mins, before it ould only take a few seconds.
BUT i am using the one from the offical site, not the one on github thats only a zip file.
unless someone has the img file from github.
BUT STILL like i said i get that error you see in CMD screenshot.
Click to expand...
Click to collapse
First of all that error is normal. Second, the img is right there on the page I posted the link to. I even posted a screenshot of me downloading it from there. I don't see any reason why I could download the img and you can't. I give up.
OK, sorry didnt see the link. I downloaded that, i flashed it. IT worked. But now when i reboot it goes straight to recovery. But i reboot to bootloader and start that way, no big deal.
Never seen those errors before, but yea it worked now, must have been the wrong TWRP. Works now. THank you
But whats the default password in TWRP
Jtaxel said:
OK, sorry didnt see the link. I downloaded that, i flashed it. IT worked. But now when i reboot it goes straight to recovery. But i reboot to bootloader and start that way, no big deal.
Never seen those errors before, but yea it worked now, must have been the wrong TWRP. Works now. THank you
But whats the default password in TWRP
Click to expand...
Click to collapse
Np. That's why we have a thanks button though. To fix your booting problem you can try connecting your phone to your PC and booting to the bootloader and run this command with fastboot:
fastboot oem fb_mode_clear
That should do it.
Jason M. said:
Np. That's why we have a thanks button though. To fix your booting problem you can try connecting your phone to your PC and booting to the bootloader and run this command with fastboot:
fastboot oem fb_mode_clear
That should do it.
Click to expand...
Click to collapse
tried a couple times, no go, thats ok tho.
But i cant flash nothing because its asking for a password to mount.
Jtaxel said:
tried a couple times, no go, thats ok tho.
But i cant flash nothing because its asking for a password to mount.
Click to expand...
Click to collapse
Ok, try:
fastboot erase DDR
That should solve your booting problem. I knew it was one or the other. Ignore the twrp asking for password and click on the mount settings and you'll see a little check box that says "mount system read only". Uncheck that box
password fixed, i flashed the no verify and super, and it wiped my phone, is that normal, just wondering ,
yes i made a backup
Jtaxel said:
password fixed, i flashed the no verify and super, and it wiped my phone, is that normal, just wondering ,
yes i made a backup
Click to expand...
Click to collapse
If you flashed the force encrypt noverity zip yes. If you don't want enryption or want it to be optional to encrypt use the one that says opt encrypt. This is all gone over possibly hundreds of times in numerous threads. You should do a little searching and reading.
Jtaxel said:
yep downloaded zip, extracted folder, just shows all the files, in a folder, not an image file
Click to expand...
Click to collapse
My bad. Often a .img file is zipped because .img gets treated as a picture.
And you can also extract .img files from flashable zip releases.
Didn't think you might have grabbed a source code zip.
Hi guys, i need some help pleeease!
I was with the November security patch on my cell phone, I unlock the bootloader and went to use the friend tool (https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585) to activate the camera2api.
But it gave problem and the cell phone did not turn on, it was locked in the screen of android one.
So I downloaded the patched_boot.img from the version I was in and put it via fastboot. did not work.
Now, my phone is in this situation: I tried to use MiFlash (three versison: 2018528, 2017720 and 20151028) and they fail in the middle of the process, accusing "FAILED (command write failed (Unknown error))".
And: when I try to connect the cell phone normally, it shows the unlocked bootloader warning and goes straight to the fastboot, even without my request. This is strange. Perhaps because the system is damaged by the miflash unfinished
Obs: bootloader are unlocked and i can access twrp
If anyone can help me I will be very grateful and happy
What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...
AsItLies said:
What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...
Click to expand...
Click to collapse
Hi.
The tool (her topic link is up there) promised to activate camera2api without root my device (allowing OTAs in the future).
I believe she did a "temporary root" with a "temporary" boot.img just to activate the camera2api, and when it rebooted, it would return to normal boot.img without root. I do not know if I could explain it well.
The current issue is that it seems that the system is currently "destroyed or corrupted". Can not I reinstall the entire system through TWRP? Or something like this
Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work
AsItLies said:
Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work
Click to expand...
Click to collapse
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?
erickxd said:
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?
Click to expand...
Click to collapse
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.
AsItLies said:
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.
Click to expand...
Click to collapse
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:
erickxd said:
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:
Click to expand...
Click to collapse
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.
AsItLies said:
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.
Click to expand...
Click to collapse
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me
erickxd said:
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me
Click to expand...
Click to collapse
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers
AsItLies said:
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers
Click to expand...
Click to collapse
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?
erickxd said:
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?
Click to expand...
Click to collapse
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.
Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861
ckpv5 said:
Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861
Click to expand...
Click to collapse
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:
AsItLies said:
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.
Click to expand...
Click to collapse
I can access twrp when I flash ''fastboot boot twrp.img" in powershell, so until the next reboot I have access to twrp
erickxd said:
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:
Click to expand...
Click to collapse
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.
ckpv5 said:
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.
Click to expand...
Click to collapse
Hmm thanks for the answer!
Even when the operation fails after transfer a couple of archives before the system.img??? (on the Miflash)
If my phone was locked, Miflash could transfer these couple of archives before the operation fails?? Or if bootloader is locked, zero files can be passed by Miflash, and the error is apresented at the beginning of the operation?
Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.
prokaryotic cell said:
Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.
Click to expand...
Click to collapse
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?
erickxd said:
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?
Click to expand...
Click to collapse
Before someone can explain that, why don't you answer the question asked .. in fact at least 3 people was asking/telling ...
"Have you successfully unlocked critical partitions?"
Without the proper answer from you, not easy to help.