I can't flash Android M:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can't find any boot.sig and recovery.sig, only find .img files with the M package. Any advice will be greatly appreciated.
Manually flash each IMG as opposed to using the flash-all.bat (others have had this same issue)
EddyOS said:
Manually flash each IMG as opposed to using the flash-all.bat (others have had this same issue)
Click to expand...
Click to collapse
Yes That's exactly I was doing. I flash it one by one still get can't find .sig file....
pyth0ner said:
Yes That's exactly I was doing. I flash it one by one still get can't find .sig file....
Click to expand...
Click to collapse
No, what I'm saying is DON'T use the flash-all.bat script as that's causing the issue. You have to extract the ZIP file and manually flash each IMG file one at a time, e.g.
fastboot flash bootloader bootloader.img
fastboot-reboot bootloader
fastboot flash radio radio.img
fastboot-reboot bootloader
fastboot flash system system.img
fastboot-reboot bootloader
fastboot flash recovery recovery.img
fastboot-reboot bootloader
fastboot flash boot boot.img
fastboot-reboot bootloader
etc, etc, etc.
Maybe you shouldn't be flashing a developer preview if you don't know what you're doing?
Sent from my Nexus 5 using Tapatalk
Ben36 said:
Maybe you shouldn't be flashing a developer preview if you don't know what you're doing?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Well said well said
Sent from my Nexus 5 using XDA Free mobile app
It happens to me some times regardless of the android version, if I use the computer front ports. It's always better to use the ones directly on the motherboard.
the *.sig thing always appear but I also recommend you to avoid the .bat file and do it manually.
Issues with Image
Hi folks, I know what i'm doing, so I flashed the images and it all worked...BUT some major things are missing. I cant drop down the notification drawer (nor do I get any notifications) Also, nothing Google syncs. I tried manually syncing/logging out and logging back in and nothing seems to work, so 1) Suggestions? 2) Is there a dedicated forum for this? I cant seem to find anything online. I also tried flashing it again and to no avail.
Help me XDA, you're my only hope to not going mad on my phone.
Do a clean flash. You didn't if the notification drop down doesnt work
Sent from my Nexus 5 using Tapatalk
Related
i know you have to flash the boot.img to get roms working, but how about the default rom, do i have to flash the top one in adb?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i like cm10, but wanna go back to stock for a change
For_itembine said:
i know you have to flash the boot.img to get roms working, but how about the default rom, do i have to flash the top one in adb?
i like cm10, but wanna go back to stock for a change
Click to expand...
Click to collapse
this is a nand backup done from a custom recovery, restore it in recovery...
SOLVED
i flashed boot.emmc.win
i was just unsure if i could flash it or not (because it was emmc win and not .img)
thanks
(i was getting bootloops trying to restore the default/stock rom, so this is all i needed to do - for others viewing this with similar problem)
For_itembine said:
SOLVED
i flashed boot.emmc.win
i was just unsure if i could flash it or not (because it was emmc win and not .img)
thanks
(i was getting bootloops trying to restore the default/stock rom, so this is all i needed to do - for others viewing this with similar problem)
Click to expand...
Click to collapse
confused ?! are you not trying to restore the whole backup cuz flashing the boot.img is not gonna restore your backup but just the kernel really.
For_itembine said:
SOLVED
i flashed boot.emmc.win
i was just unsure if i could flash it or not (because it was emmc win and not .img)
thanks
(i was getting bootloops trying to restore the default/stock rom, so this is all i needed to do - for others viewing this with similar problem)
Click to expand...
Click to collapse
So first you flash the first one in fast boot then the whole backup through recovery, right??
Sent from my One X using xda app-developers app
thinkhope said:
So first you flash the first one in fast boot then the whole backup through recovery, right??
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
you should be able to "restore" the whole nand backup from recovery.
U need to flash boot.img from the rom in fastboot not the nandroid boot backup that wont work and ur phone wont boot.
Well i downloaded the new developer preview for m
and tried to flash the usual way
Then i encountred this error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
tried running cmd in admin mode too, no effect.
The method i used is as follows
I extract the zip in the folder to get access to the images inside and then flashed them manually.
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system sysytem.img (did not work)
fastboot flash userdata userdata.img
Click to expand...
Click to collapse
Running Fastboot and adb v 1.4 from here
http://forum.xda-developers.com/showthread.php?t=2588979
Kindy someone assist thank you
Your image doesn't show
Sent from my Android M Nexus 5 yo!
Try to reboot to your bootloader, and then flash system.img.
Schoat333 said:
Try to reboot to your bootloader, and then flash system.img.
Click to expand...
Click to collapse
i try this and still get the error
Schoat333 said:
Try to reboot to your bootloader, and then flash system.img.
Click to expand...
Click to collapse
I tired that.
I actually even tried restarting the bootloader after flashing every component.
Seems this fastboot has some issues with android m.
Can anyone who has flashed it provide some input.
Sent from my A0001 using XDA Free mobile app
I had the same problem. Not just with android M, other Google OEM Roms. I was only able to get it to work by doing it on my Mac. I would think that Linux would have no problem either.
I had no issues flashing M through fastboot - even used flash-all.sh.
I couldn't get M to boot until I individually erased each part using fastboot, and then individually flashed each part, extracted from Google's zip, also using fastboot.
lnchbx said:
I had the same problem. Not just with android M, other Google OEM Roms. I was only able to get it to work by doing it on my Mac. I would think that Linux would have no problem either.
Click to expand...
Click to collapse
I can't get it to work on my Mac! I keep getting the data length too large error when trying to flash system.mg. Everywhere I've looked has said update the sdk, but I'm on the latest version.
theChief_ said:
I can't get it to work on my Mac! I keep getting the data length too large error when trying to flash system.mg. Everywhere I've looked has said update the sdk, but I'm on the latest version.
Click to expand...
Click to collapse
You need to pass the '-s' argument to fastboot to be able to flash system.
Redownload the file could be corrupt. Only other thing try using mfastboot(google it)
Hi,
I never saw this problem
My phone is unlocked (since a year more or less) and I can't install TWRP nor CWM. I tried many tutorials such as all the root methods listed on XDA for this smartphone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any idea would be really appreciated!
Thanks
There might be a problem with your drivers. You can try uninstalling and reinstalling them. Also, try using fastboot commands manually
Sent from my Mate
unlock again
Thank you. I'd like not to have to relock it as it's already done and rooted. Could you please tell me what drivers to install? I tested many of them (https://i.imgur.com/wBgsezr.png) but it seems I don't have the right ones then.
I'm using Win7 64bits.
Thanks again!
Use adbdriveinstaler and when it's install you can push recovery to add folder and try this command
cd C:/adb
Fastboot flash recovery recovery.img
Change name your twrp or cwm to recovery
Send frome globe
Okay. Here we go
ADB driver installed (https://i.imgur.com/PWrZoHH.png)
Went to flash and... still not allowed.
And in fastboot/rescue mode on my phone it's written PHONE Unlocked.
WTF
BTW, is there any other way to upgrade the phone? Cause every time I go to the software update in the menu i'm told it's up-to-date, but it's not... Android 4.4.2 & EMUI 3.0.
I read about a "local update" but can't find out how to update from the SDcard, I only have OTA.
Bud64 said:
Okay. Here we go
ADB driver installed (https://i.imgur.com/PWrZoHH.png)
Went to flash and... still not allowed.
And in fastboot/rescue mode on my phone it's written PHONE Unlocked.
WTF
BTW, is there any other way to upgrade the phone? Cause every time I go to the software update in the menu i'm told it's up-to-date, but it's not... Android 4.4.2 & EMUI 3.0.
I read about a "local update" but can't find out how to update from the SDcard, I only have OTA.
Click to expand...
Click to collapse
In your screen you have locked bootloader. Unlock againg
Send frome globe
Okay, I sent an email to Huawei, I'll get back in a few days.
Hello, Before we get started this is a quick TLDR guide and you do this at your own risk, If you DM me and your phone doesn't work I will laugh myself to sleep. (This shoulden't do that unless your stupid!).
If you have issues such as sensors not working like Auto Rotate, Proximity, Auto Brightness, Etc (Use a sensor testing app to confirm) [Make sure your 100% sure it's not due to damage].
Then you need to flash the persist.img, Some how or at least in my experience its become corrupted, normally you would just flash via fastboot the stock files and you should be good to go but Xiaomi doesn't let you flash these because you should not ever have too. The last option was to use EDL but that seems complicated for a issue with some sensors.
Now thanks to a few guides on XDA (Can't find the right one or I would link it here) and some other Xiaomi user posts the quickest way is just to use a recovery to flash the img, now I've tried coping the backup persist partition (PersistBak) and it did not help me nor did using recovery to dd the image to the persist partition, but flashing via OrangeFox did the trick,
Messing with the persist partition is not recomended and may break stuff as its never ment to be tampered with so if you can't use pay anymore Don't blame me!
You do so at your own risk!
1. So Grab your firmware IE latest from your chosen region
2. Grab the extracted persist.img and load your recovery
3. Then select persist img and select it from storage (SD Card)
4. Make sure you pick flash to persist (On OrangeFox it was Persist_IMAGE for me)
5. Flash it and reboot
6. Check your sensors and they should be working!
Now you don't have to spend hours looking online your welcome!
Please thank the individuals that found this and not me I'm just a risk taker and have money to replace it if I Break it.
UnfixableExploit said:
Can't find the right one or I would link it here)
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
XDA Search in This forum
https://forum.xda-developers.com/t/problem-proximity-sensor-vayu.4366935/post-86002353
UnfixableExploit said:
some other Xiaomi user posts the quickest way is just to use a recovery to flash the img, now I've tried coping the backup persist partition (PersistBak) and it did not help me nor did using recovery to dd the image to the persist partition, but flashing via OrangeFox did the trick,
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/problem-proximity-sensor-vayu.4366935/post-86137755
I believe I used the one from the Xiaomi Mi 8, I didn't know we had a vayu guide...
And when I looked for one online quoting XDA it never showed up.
i tried to flash stock rom RMX1971EX_11_OTA_0110 flash system.img, boot.img, vendor.img, vbmeta.img and still keep going back to fastboot, usually its work. Now just stuck in fastboot or stuck in realme logo, no recovery, system, nothing. help how do i fix this?
Have you fixed the problem? I have had the same problem. I had installed in my phone Android 11 and I was trying to flash RMX1971EX_11_OTA_0110. Rihht now nothing works. Just realme logo and after that reboot again and again.
Have you fixed the problem? I have had the same problem.
hoczzx112 said:
Have you fixed the problem? I have had the same problem.
Click to expand...
Click to collapse
yes. Use this:
RMX1971EX_11_F.03 - Google Drive
drive.google.com
softrobot said:
yes. Use this:
RMX1971EX_11_F.03 - Google Drive
drive.google.com
Click to expand...
Click to collapse
thank you so much but it is not working for me. do you have file realme Q zip or ozip F.03? please help me
hoczzx112 said:
thank you so much but it is not working for me. do you have file realme Q zip or ozip F.03? please help me
Click to expand...
Click to collapse
Did you flash all the img files? I did that and It worked. I didnt use any other files.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i don't know.huhuhuhuh
softrobot said:
yes. Use this:
RMX1971EX_11_F.03 - Google Drive
drive.google.com
Click to expand...
Click to collapse
Thanks bro its working but cant turn on my wifi after that
tamaaw said:
i tried to flash stock rom RMX1971EX_11_OTA_0110 flash system.img, boot.img, vendor.img, vbmeta.img and still keep going back to fastboot, usually its work. Now just stuck in fastboot or stuck in realme logo, no recovery, system, nothing. help how do i fix this?
Click to expand...
Click to collapse
did you fix it yet? i have the same problem here