Related
So I did a full wipe and then installed Rodriguezstyle FroYo rom (http://forum.xda-developers.com/showthread.php?t=692609). It was fine but I missed too many CM features and NeXTheme.
I did a wipe, reflashed CM5.0.7.1 and then restored my nandroid (+ext). Now I cannot get the device to boot!
I can get into bootloader and thought I should replace the radio as I know the FroYo one is a problem in non-FroYo roms but while it copies ok, when installing it says FAILED (remote:image update error)
Please please help me. Give me steps to do to get back to a clean CM5.0.7.1 and I can sort the rest out!
Fastboot won't let me flash anything! I am unlocked though!
There's no need to post your question in multiple forums.
Someone will answer when they know how to help.
That said, all I can suggest is maybe trying a different radio image? Or maybe see if you can load up one of the 2.1 ROMs and deal with the radio issue once it's up and running?
Sorry, got a bit desperate
I have tried several radios, the problem is that I cannot flash anything for some reason. I cannot even flash Amon_Ra's recovery to try and get a different rom working
So even booting to fastboot (press and hold trackball during power-on) your computer is unable to connect via fastboot? So "fastboot devices" doesn't return anything?
Just booting normally, what happens? Does it get stuck on the Android bootloader screen or what? Any chance of connecting to it via adb?
I haven't broken my stuff hard yet, so I'm kinda guessing here lol. Trying to help though!
I appreciate the help, thanks.
I can get to fastboot and issue fastboot commands (fastboot devices returns the model number (?) as normal). It's just that if I try to fastboot flash recovery I get that "image update error"
I can't get as far as a recovery image to issue adb commands. When I try to boot normally, the phone vibrates once as the X comes up, then several quick vibrations which seem like some kind of error code.
Also, by way of some extra info in case it helps, the following is displayed on my bootloader:
NEXUSONE PVT SHIP S-ON
HBOOT_0.33.0012
MICROP-0b15
TOUCH PANEL-SYNT0103
Radio-4.02.02.14
Dec 17 2009,13:05:23
3Shirts said:
I appreciate the help, thanks.
I can get to fastboot and issue fastboot commands (fastboot devices returns the model number (?) as normal). It's just that if I try to fastboot flash recovery I get that "image update error"
I can't get as far as a recovery image to issue adb commands. When I try to boot normally, the phone vibrates once as the X comes up, then several quick vibrations which seem like some kind of error code.
Also, by way of some extra info in case it helps, the following is displayed on my bootloader:
NEXUSONE PVT SHIP S-ON
HBOOT_0.33.0012
MICROP-0b15
TOUCH PANEL-SYNT0103
Radio-4.02.02.14
Dec 17 2009,13:05:23
Click to expand...
Click to collapse
What is the EXACT command are you typing to flash recovery?
3Shirts said:
I appreciate the help, thanks.
I can get to fastboot and issue fastboot commands (fastboot devices returns the model number (?) as normal). It's just that if I try to fastboot flash recovery I get that "image update error"
Click to expand...
Click to collapse
Have you tried this --> http://forum.xda-developers.com/showthread.php?t=614850
It is a sticky..... Anyways, I would also try the official .zip image (PASSIMG.zip) if you can find a thread on that someplace. That loads through fastboot I believe so check it out.....
Also try "Fastboot boot recovery.img" (recovery.img being c:\PATHTOFILE) and see if it will boot into recovery that way......
martin0285 said:
Have you tried this --> http://forum.xda-developers.com/showthread.php?t=614850
It is a sticky..... Anyways, I would also try the official .zip image (PASSIMG.zip) if you can find a thread on that someplace. That loads through fastboot I believe so check it out.....
Also try "Fastboot boot recovery.img" (recovery.img being c:\PATHTOFILE) and see if it will boot into recovery that way......
Click to expand...
Click to collapse
The command I am typing is: fastboot flash recovery recovery.img <- this being the name of the Amon_Ra recovery image file located in the same folder I am in when issuing the command
I have tried that post's instructions but I get "remote: not allowed" when trying to erase userdata and I was getting "remote: image update error" when trying to do any of the flash commands. I say WAS becasue I have just tried sticking the original PASSIMG on sd card and updating that way and, while it gave me partition update errors on boot and system, it has changed something because now when I do the fastboot flash commands I get a different error: "remote: signature verify fail"
I know the files are not corrupt though as I have checked the md5s
EDIT: I also tried doing a fastboot boot to the recovery image but it loads to the X then I get prompted by windows to install a Qualcomm CDMA driver which it can't find?!!
the first case of semi-brick?
like on the G1
JKshowman said:
the first case of semi-brick?
like on the G1
Click to expand...
Click to collapse
Don't say that
Thread Moved.
3Shirts said:
Don't say that
Click to expand...
Click to collapse
no, its just i had a semi-brick problem on the G1 and i solved it quickly enough by reflashing a recovery, but in this case.........
try to see if other flashboot commands work
3Shirts said:
Don't say that
Click to expand...
Click to collapse
Try downloading the recovery image again. It could be corrupt. Also, I am assuming you unlocked your phone first.
No I have confirmed the MD5s on everything I downloaded including the recovery image. Yeah I've been unlocked and rooted from day one.
Does anyone have an hboot image I can try flashing
Well it looks like i'm f***ed then.
I can't adb and can't boot to any kind of terminal so with only fastboot available, and that not allowing me to flash much, I can't fix this
I guess it's off to HTC, see what hey can/will do and if that fails... no more Nexus One
EDIT: Booked it in with HTC for collection tomorrow afternoon (UK time). I'll update again to provide a definitive answer to the question: What is the price for effing up your Nexus One through your own stupidity
The command I am typing is: fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I realize this, but fastboot BOOT recovery.Img is a different command to just "boot" the image and not "flash" permanently... worth a shot....
martin0285 said:
I realize this, but fastboot BOOT recovery.Img is a different command to just "boot" the image and not "flash" permanently... worth a shot....
Click to expand...
Click to collapse
I have tried that too. It just sits at the X. Doesn't get into recovery
3Shirts said:
I have tried that too. It just sits at the X. Doesn't get into recovery
Click to expand...
Click to collapse
****ty, well good luck with HTC.....
Just to update for anyone interested in the process:
I called HTC on 2nd June and booked collection for the following afternoon.
Picked up by courier (I packed it in original box and jiffy bag with battery but no SD or Sim cards) at 2pm on 3rd June
Received confirmation of arrival with HTC (Milton Keynes as I'm in the UK) at 1.43pm on 4th June
Next step is to wait for a call regarding the repair that can be done and associated cost.
Hello anyone know how to remove unlock bootloader warning logo ? Please Help i will be very gratitude for any info
Just download the firmware for your region and extract the file logo_signed, put the device into fastboot mode (press power + vol -) open a console and run the command fastboot flash ulogo logo_signed and reboot your device Hope this helps
Sent from my XT890 using xda app-developers app
You can do it this way
Only ICS and, if the case, maybe Jelly Beam accesed for Homemade
Does not work on Jelly Beam accessed by OTA or RSD Lite
If you mean the caveat that you unlocked bootloader, use the information to a htcmania forum, and as if you can not make a link to there without censor me,
is simple, get files
1. - Fastboot.exe
2. - logo_signed (must be obtained from the firmware, exploring the zip file)
sorry for my bad English
Donwload files
http://db.tt/tak1LsuU
note: logo_signed file is of the firmware: Brasil.en.BR
Procedure
1. - Put the downloaded files in a folder in the root "C" on your pc, (I call this folder Android for example)
2.- Put the phone in fastboot mode (power button and Vol - squeezing them a few seconds until the screen fastboot mode) and connect with USB the phone to pc
3.- Opening a cmd screen, we stand there, I'm in cmd C:\Android\
4. - cheking with command fastboot devices
5. - Performed the command fastboot flash ulogo logo_signed
6. - Conducted after ending command fastboot reboot and that's it
7.- enjoy
Warning: only share what I see written on a forum and I served, so I do not take responsibility for any damage this may cause to your phone
hello
keeps saying somethink about verication lads!!
Does anynone know how to remove this warning from Jelly Bean?
andy_macleod said:
Does anynone know how to remove this warning from Jelly Bean?
Click to expand...
Click to collapse
My friend, download the attatched file and enter fastboot mode, in CMD prompt write the following:
fastboot flash logo logo-CMAK.bmp
fastboot flash ulogo logo-CMAK.bmp
Cheers.
xpc21 said:
My friend, download the attatched file and enter fastboot mode, in CMD prompt write the following:
fastboot flash logo logo-CMAK.bmp
fastboot flash ulogo logo-CMAK.bmp
Cheers.
Click to expand...
Click to collapse
Thanks for you quickly response.
I use stock JB 4.1, may I do your procedure or it just work with cyanogenmod rom?
andy_macleod said:
Thanks for you quickly response.
I use stock JB 4.1, may I do your procedure or it just work with cyanogenmod rom?
Click to expand...
Click to collapse
Sorry andy!
This method i´ve tried and worked on Omar-AVelar ROM April 09, the newer ones didnt worked.
I dunno if will work on another.
Bounty
andy_macleod said:
Thanks for you quickly response.
I use stock JB 4.1, may I do your procedure or it just work with cyanogenmod rom?
Click to expand...
Click to collapse
I too am interested in removing the unlocked warning on OTA JB. We should set up a bounty
xd69 said:
I too am interested in removing the unlocked warning on OTA JB. We should set up a bounty
Click to expand...
Click to collapse
The biggest problem of Razr i is the intel architecture x86 not common in mobiles.
xpc21 said:
Sorry andy!
This method i´ve tried and worked on Omar-AVelar ROM April 09, the newer ones didnt worked.
I dunno if will work on another.
Click to expand...
Click to collapse
Do you mean that you think we will never be free from this ugly warning? :crying:
marcospbs said:
Do you mean that you think we will never be free from this ugly warning? :crying:
Click to expand...
Click to collapse
I don't think so. Just for while, soon someone will find a way to disable this "ugly" warning.
xpc21 said:
My friend, download the attatched file and enter fastboot mode, in CMD prompt write the following:
fastboot flash logo logo-CMAK.bmp
fastboot flash ulogo logo-CMAK.bmp
Cheers.
Click to expand...
Click to collapse
It doesn't works on Pi-Lama ROM 0.6
I suggest you don't even try to flash it. You'll brick your phone. I'm currently stuck on Fastboot and can't boot properly, but i've a CWM backup and can't access CWM anymore.
If you're stucked, i suggest you to flash Omar-Avelar boot.img found here.
Speeding up the process
andy_macleod said:
I don't think so. Just for while, soon someone will find a way to disable this "ugly" warning.
Click to expand...
Click to collapse
A high enough bounty would make someone dev it alot faster!
xd69 said:
A high enough bounty would make someone dev it alot faster!
Click to expand...
Click to collapse
For sure. Lets find at least 100 users from razr i and all deposit US$1,00 in a specific paypall account and give the bounty for who find a way to disable this boring warning.
andy_macleod said:
For sure. Lets find at least 100 users from razr i and all deposit US$1,00 in a specific paypall account and give the bounty for who find a way to disable this boring warning.
Click to expand...
Click to collapse
Im willing to input $20 to the cause so that this gets done faster!
Any luck on JB?
Well, this is what I tried just now:
- I pulled 'logo_signed' and 'ulogo_signed' from 'CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml.zip' file, which is the one I had flashed before Omar's ROM.
- I then simple renamed them one with the name of the other (logo became ulogo and viceversa) and tried to flash via 'fastboot flash'
- The error I got was 'Invalid OSID for logo : 2' when attempted to flash 'logo_signed' and 'Invalid OSID for ulogo : 0' for 'ulogo_signed'
- Opened both files using XVI32 and found almost the same header up to hex addr 9A, where there was a 02 on logo file and a 00 on ulogo file
- I edited them, changing the 02 for 00 and viceversa, saved them and tried to flash again, I then get:
At phone's screen:
Fastboot command failed
Getvar max-download size
In cmd screen:
writing 'ulogo'...
Invalid image ulogo
Preflash validation failed
writing 'logo'...
Invalid image logo
Preflash validation failed
At least I got rid of the first error, but have no idea on this second one... any guesses?
.
Hi, what is your command line ? Do you use fastboot ? Rsd lite ?
nick7722 said:
...
- I then simple renamed them one with the name of the other (logo became ulogo and viceversa) and tried to flash via 'fastboot flash'
...
Click to expand...
Click to collapse
I was probably not very clear, I tried flashing them via fastboot, that is 'fastboot flash logo logo_signed' and 'fastboot flash ulogo ulogo_signed'
.
OK. This is for those who are not so great or somewhat new to flashing stuff; if you're already awesome at this you will most likely not find this thread helpful. It took me a long time to find the answers I was looking for so I thought I'd share my results.
My issue: I was trying to update to Android 5.01 (Nexus 6, 5.0, encrypted, rooted)
I got the OTA notification, which after I dismissed it, could not get it back. However, I found out, again after much reading that even if I had caught it, it would not have worked since Lollipop does a system check before it updates and because I was rooted would not have worked. I also tried just capturing the OTA update from droidlife and again, once I got to the sideload phase (either through wugfresh, or just standard minimal adb).
So... searched and searched, I didn't want to lose my user data, since it's tough to get everything just the way I like it. I finally found a solution.
I downloaded Wugfresh (mainly because the application is great in terms of getting the drivers under control, I was able to get it installed and working on two comptuers).
Next, downloaded the minimal adb and fastboot stuff, it's pretty awesome, because after this process you really feel like you're getting a grasp on customizing android.
http://forum.xda-developers.com/showthread.php?t=2317790
Next, download the actual install image from google (nexus 6, 5.01)
http://forum.xda-developers.com/showthread.php?t=2317790
Once you get that file, you'll need a nice zip program like 7zip: You want to go into the file and get 5 files:
radio-shamu-d4.0-9625-02.55.04.img (I renamed it to radio.img)
bootloader-shamu-moto-apq8084-71.05.img (I renamed it to bootloader.img
then in the image-shamu-lrx22c.zip file, retrieve these three files:
recovery.img, system.img and boot.img
Now, take a breath, get a drink and prepare for the next part.
Boot into fastboot mode (power off phone, then once it's off, hold down power and volume DOWN)
Pull up your minimal adb and fastboot:
type:
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Very important next step:
fastboot reboot-bootloader
Next:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
This first boot will take quite a bit but it WILL come up, and optimize all your apps and settings (nothing lost)
Now, because I was in the mood to flash stuff, I rebooted into fastboot mode again (after I downloaded CF-auto root and extracted the files for 5.0)
renamed the cf-autoroot blah blah blah to just root.img
then:
flashboot boot root.img, it ran and rebooted, bam rerooted, none of the my data lost. Hope this helps someone.
Good to hear you've got it sorted. This has been covered on many occasions in other threads though.
Hello I am pretty new to flashing and been looking around to find a way to flash 5.0.1 on my N6 w/o having all my data wiped. Like you i got the OTA update and i attempted to install it even tho i had root and i read on forums that it would fail. After it finished downloading it rebooted my device to shortly fail right after. The OTA update has never popped up since and i been waiting for it to come back up (2 days now) so i can attempt to install it after i unroot.
Thanks for your detailed instructions and for assuring me that you were successful w/o having to lose data. I will flash my N6 as soon as i get home!
Amos91 said:
Good to hear you've got it sorted. This has been covered on many occasions in other threads though.
Click to expand...
Click to collapse
people like you need to go away - i had the same thought, but did i feel so compelled to bash the OP? As far as i'm concerned, there will always be new people around with new nexus devices and what the OP laid out clearly addressed many threads that popped up over the last week regarding 5.0.1. Even though i didn't need the help, thanks OP for sharing.
mb3030 said:
people like you need to go away - i had the same thought, but did i feel so compelled to bash the OP? As far as i'm concerned, there will always be new people around with new nexus devices and what the OP laid out clearly addressed many threads that popped up over the last week regarding 5.0.1. Even though i didn't need the help, thanks OP for sharing.
Click to expand...
Click to collapse
Not sure I can see how I bashed the OP. I could of been considerably more brash than that and meerly said whilst it was good he got it working it has been covered.
Whilst I agree the information is useful there has to be some kind of limit to duplication.
I'm not a robot
firestarter44 said:
Next, download the actual install image from google (nexus 6, 5.01)
http://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
Can someone please verify the url to the image (or direct me to a directory of images)?
I believe it is: https://developers.google.com/android/nexus/images#hammerheadlrx22c but I'm a newbie so I prefer someone who knows verify this.
CodeWarrior4Life said:
Can someone please verify the url to the image (or direct me to a directory of images)?
Click to expand...
Click to collapse
if you go to google, and search for nexus factory img, itll be the very first link https://developers.google.com/android/nexus/images
Instead of using fastboot manually since you installed wug's you could have used it to flash each image and not have to type it all out. It's under the advanced button
xxfwmxx said:
Instead of using fastboot manually since you installed wug's you could have used it to flash each image and not have to type it all out. It's under the advanced button
Click to expand...
Click to collapse
I tried to flash in Wugs and I was able to flash the first two files "fastboot flash bootloader bootloader.img and fastboot flash radio radio.img and fastboot reboot-bootloader . Each time when you flash one, it reboots. When I tried to flash the 3rd file, the fastboot flash recovery recovery.img, it gave me an error saying it cant find my device. I manually typed out tye commands in fastboot and it worked fine.
Also, for folks like me that don't often use the commants, make sure when you unzip your files, if you are using the commands with fastboot, that you put the files in the same directory as Minimal ADB and fastboot. That is my help to everyone! Thanks for the tutorial!!!!
This helped me out a lot!!! Thanks =D
I'd have to agree with mb3030. I searched multiple threads as well as Google to find specific information regarding the Nexus 6 going from 5.0 ==> 5.0.1 (while encrypted) and found no such information until this popped up. While I've been doing this for years now, it's still helpful finding a thread this specific to double check I'm doing things right. I never understood why XDA was so harsh on reposts. I would personally rather have a thousand different threads all saying the same thing from different members as this seems to be the best way to come to a general consensus of the "right" way to do something. It's a typical scientific approach to conduct multiple studies in order to verify information.
Bloody brilliant worked like a charm THANKS!!!!!!!!
So there isn't a stock rooted flashable zip for 5.0.1
Thank you for this awesome guide, worked all well.
will this be the same procedure for 5.1 or will we have to see?
Greetings,
Elmar.
Just wanted to say thanks for this thread! I, too, searched, trying to find this information and never found anything this simple and straightforward. Exactly what I was looking for.
So I've followed the directions and got all the way to flashing the system and it seems to be stuck on "sending sparse system". It already did a "sending sparse system" and followed with "writing system". It sounds like it's trying to send a write the system file in chunks instead of all at once. Am I right? Is it supposed to do this? If I back out now, am I hosed?
aaronmcd1214 said:
So I've followed the directions and got all the way to flashing the system and it seems to be stuck on "sending sparse system". It already did a "sending sparse system" and followed with "writing system". It sounds like it's trying to send a write the system file in chunks instead of all at once. Am I right? Is it supposed to do this? If I back out now, am I hosed?
Click to expand...
Click to collapse
Yes it sends it in chunks. Just let it keep going it will work out fine just takes a bit longer than the other IMG files
The Tig using Tapatalk
the factory image link is not correct
the factory image link is not correct
ncelover said:
the factory image link is not correct
Click to expand...
Click to collapse
The correct link is https://developers.google.com/android/nexus/images
Look for the 5.0.1 image for Nexus 6 "Shamu"
The Tig using Tapatalk
Everything works fine until I boot into fastboot mode and then suddenly it can't see the device anymore. Wugfresh works and can see the device in normal mode, but once I pop it into fastboot mode it can't find it anymore either.
Anyone have any ideas?
I have a rooted sprint moto x that was running cm 12.1 and I used a toolkit to try and restore it to stock and ended up deleting the os and twrp recovery. I managed to flash the recovery back onto the phone using adb commands, however my PC doesn't recognize my moto as a USB storage device so I am unable to move the rom zip file to the phone. I tried flashing in fastboot and also adb push to push the file to the phone however nothing works..... If anyone could help me I'd greatly appreciate it
Shadowblade19 said:
I have a rooted sprint moto x that was running cm 12.1 and I used a toolkit to try and restore it to stock and ended up deleting the os and twrp recovery. I managed to flash the recovery back onto the phone using adb commands, however my PC doesn't recognize my moto as a USB storage device so I am unable to move the rom zip file to the phone. I tried flashing in fastboot and also adb push to push the file to the phone however nothing works..... If anyone could help me I'd greatly appreciate it
Click to expand...
Click to collapse
When you get into bootloader mode, are you using fastboot or mfastboot to flash system? If your system image is a single file instead of sparse chunks, you need to use mfastboot.
JulesJam said:
When you get into bootloader mode, are you using fastboot or mfastboot to flash system? If your system image is a single file instead of sparse chunks, you need to use mfastboot.
Click to expand...
Click to collapse
At first I used fastboot to flash the entire zip but it would say download size too large. Then I tried using mfastboot to flash the boot.img separately but that just gives me an error message.
Shadowblade19 said:
At first I used fastboot to flash the entire zip but it would say download size too large. Then I tried using mfastboot to flash the boot.img separately but that just gives me an error message.
Click to expand...
Click to collapse
what is the error message?
JulesJam said:
what is the error message?
Click to expand...
Click to collapse
I can't really check right now I'm at the beach... I'm using fastboot on a windows 8 tablet not a full fledged PC would that make any difference?
Shadowblade19 said:
I can't really check right now I'm at the beach... I'm using fastboot on a windows 8 tablet not a full fledged PC would that make any difference?
Click to expand...
Click to collapse
It is impossible for anyone to know what is wrong with your device if you can't tell us what the error message is. Post back when you know.
JulesJam said:
It is impossible for anyone to know what is wrong with your device if you can't tell us what the error message is. Post back when you know.
Click to expand...
Click to collapse
okay it keeps saying remote failure on the command prompt and it says "downgraded security version, update gpt_main version failed, preflash validation failed for gpt" on the bootloader
UPDATE": so after some time I was sorta able to get the mfastboot to work my moto x booted up normally and seemed to be running stock 4.2.2 however i get the message "the process com.android.phone has stopped" constantly to the point where the phone is unusable
Shadowblade19 said:
okay it keeps saying remote failure on the command prompt and it says "downgraded security version, update gpt_main version failed, preflash validation failed for gpt" on the bootloader
UPDATE": so after some time I was sorta able to get the mfastboot to work my moto x booted up normally and seemed to be running stock 4.2.2 however i get the message "the process com.android.phone has stopped" constantly to the point where the phone is unusable
Click to expand...
Click to collapse
UPDATE2- so after reflashing the files I stopped receiving the message and I am able to make and receive calls and texts. However, the phone will constantly power off after a minute of use... this seems to be the only problem so far.
Shadowblade19 said:
UPDATE2- so after reflashing the files I stopped receiving the message and I am able to make and receive calls and texts. However, the phone will constantly power off after a minute of use... this seems to be the only problem so far.
Click to expand...
Click to collapse
Aha I think I finally got it ! so i forgot to flash the stock recovery over my twrp so when i went to upgrade to 4.4.4 it would keep powering the phone off to install the update but load up twrp intead. A quick flash of the custom recovery and everything seems to be working fine. Thanks for all your help JulesJam I was seriously worried I bricked my phone beyond repair.
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.