Related
Hi, i have Atrix 4G on CM7 now. One day, I tried to pick a picture, but it didn't work. Just black screen, and in 2 minutes "Force close". Then, i download some other camera software, such as Camera 360, Go Photo, FX Camera... Still nothing. So i tried to reinstall CM7 at first, then i put back my stock kernel, i restored my backup from CWM Recovery, I put back stock AT&T Rom, i even reinstall Recovery. Nothing helped. Is it some possible way to find out that it is Hardware problem for sure, or any other solution?
THX a lot.
Try doing a complete wipe via fastboot before flashing a ROM if you are not already doing this:
reboot to recovery
wipe dalvik
wipe cache
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
CaelanT said:
Try doing a complete wipe via fastboot before flashing a ROM if you are not already doing this:
reboot to recovery
wipe dalvik
wipe cache
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
Click to expand...
Click to collapse
I did that...
EDIT: It is probably hardware problem, front camera works. I just want to be sure, that its really as i think... S*** But i still will be glad for any help..
EDIT2: Now, when i start the camera app, it says Camera error: Cannot conect to camera.
Anybody???
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Fastboot flash the images. Then reroot.
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
TenderloinShadow said:
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=56921581&postcount=33
That post left out flashing recovery. The download should have 6 files. I flashed recovery at the end (but I don't think it matters how you flash the files, I could be wrong though).
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
di11igaf said:
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
Click to expand...
Click to collapse
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
ericplatham said:
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
Click to expand...
Click to collapse
You're right, now that I think about it, I believe I had to do that as well last time I flashed a factory image.
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
GatorsUF said:
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
Click to expand...
Click to collapse
maybe I'll write up a guide, but download the factory image, extract it. In there is a zip file, extract it too. Then Google 15 second adb install xda. That'll set up fastboot on your pc. Then boot into the bootloader and in a command window opened in the folder where the bootloader image is located run the commands:
fastboot flash bootloader bootloader.img. Note, use the full name of the bootloader.img
fastboot reboot-bootloader
fastboot -w
Open the folder where the boot, system, cache, system, and vendor images are located. Open a command window in that folder and run the commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Then you're done
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Then you're done
Click to expand...
Click to collapse
He will still have to reroot and flash custom recovery... but you got 95% of the process :laugh:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
rank78 said:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
Click to expand...
Click to collapse
Since its a small update you could probably get by just flashing the system and boot images. But I haven't tried it
Sent from my Nexus 5 using XDA Free mobile app
I'd flash everything as described to be safe, I just prefer simply flashing a zip and moving on.
Will updating thru adb wipe my device?
GatorsUF said:
Will updating thru adb wipe my device?
Click to expand...
Click to collapse
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, I have actually flashed a few times thru fastboot in the past so I'm not totally lost on the idea. I've always used tibu in the past, will Google restore my data too?
TenderloinShadow said:
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Click to expand...
Click to collapse
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
fhem said:
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
Click to expand...
Click to collapse
Why erase recovery twice?
Just dont flash stock recovery
fhem said:
STEP #1
fastboot flash bootloader {bootloader.img}
Click to expand...
Click to collapse
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Double_U said:
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Click to expand...
Click to collapse
Hi, Double_U...
Are you sure you've typed the EXACT command..?
Code:
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
Reboot the bootloader, enter fastboot, and try again.
Rgrds,
Ged.
Hi everybody i need your help,
I got an honor 9 STF-L09. I got bricked and I want to install the stock firmware because my phone doesnt on again. I have Twrp installed and unlocked bootloader but when i try to boot into system it says "Func NO: 10 (boot image)".
I tried to flash firmware from thi guide https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892 but nothing to do.
I tried to flash using twrp but the ionstallation fail everytime.
Is there someone that can help me with a stock firmware or even other firmwares that makes my H9 on againg.
Please help me I'am DESPERATE
Did you take a look here ?
http://droidvendor.com/download-8-0-0-360-c432-official-oreo-for-honor-9-stf-l09/
sorry, I'm not expert on this topic, it's the only help i can give you
What rom did you have before? EMUI 8 or 5.1?
JBolho said:
What rom did you have before? EMUI 8 or 5.1?
Click to expand...
Click to collapse
I had emui 8
leocap33 said:
I had emui 8
Click to expand...
Click to collapse
I will provide you with the files that (hopefully) will bring your device back to life. Just need to upload the first, i'll update this post with the link and instructions, hang on a second.
JBolho said:
I will provide you with the files that (hopefully) will bring your device back to life. Just need to upload the first, i'll update this post with the link and instructions, hang on a second.
Click to expand...
Click to collapse
thank you man
leocap33 said:
thank you man
Click to expand...
Click to collapse
In the link you will find Stock EMUI 8 Ramdisk, Recovery and System, as well as TWRP and a Kernel that fixes the possibility of losing the capacitive buttons. Download them into a folder on the root of your PC (for example C:\Temp)
https://www.dropbox.com/sh/88l72rypm6u1u94/AADtPyvsIFhyBl1mcJ5raTBZa?dl=0
I don't know what caused your boot to disappear, mine disappeared when i tried to unroot it from within SuperSU app (Big Mistake), but let's not be drastic just yet. You need Fastboot and ADB on your PC, turn off your phone, hold Volume - and connect the USB cable from the PC to the device. You should enter Fastboot mode. I hope your device is FRP unlocked as well.
Open a command line and input "fastboot devices" to make sure your device is connected
First let's try restoring Ramdisk, TWRP and Kernel:
Run "fastboot flash ramdisk STF-L09_ramdisk.img", then "fastboot flash recovery_ramdisk stf_twrp_oreo.img" and finally "fastboot flash kernel B360_fix_kernel.img"
After that just run "fastboot reboot" and see if it boots or not... This should take care of your problem, if not, let's go drastic:
Turn off the device and plug it in fastboot mode again onto your PC.
On the command line run "fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img" (this will flash stock recovery), and "fastboot flash system SYSTEM.img" (this will flash your system partition, in small bathes at a time, fresh.)
After that, just "fastboot reboot" and it should boot to your system (and without a factory reset!) If it bootloops for some reason, turn off the device, boot into stock recovery and wipe cache (or do a full factory reset, but that should not be necessary i think...)
Hope all this helps!
JBolho said:
In the link you will find Stock EMUI 8 Ramdisk, Recovery and System, as well as TWRP and a Kernel that fixes the possibility of losing the capacitive buttons. Download them into a folder on the root of your PC (for example C:\Temp)
https://www.dropbox.com/sh/88l72rypm6u1u94/AADtPyvsIFhyBl1mcJ5raTBZa?dl=0
I don't know what caused your boot to disappear, mine disappeared when i tried to unroot it from within SuperSU app (Big Mistake), but let's not be drastic just yet. You need Fastboot and ADB on your PC, turn off your phone, hold Volume - and connect the USB cable from the PC to the device. You should enter Fastboot mode. I hope your device is FRP unlocked as well.
Open a command line and input "fastboot devices" to make sure your device is connected
First let's try restoring Ramdisk, TWRP and Kernel:
Run "fastboot flash ramdisk STF-L09_ramdisk.img", then "fastboot flash recovery_ramdisk stf_twrp_oreo.img" and finally "fastboot flash kernel B360_fix_kernel.img"
After that just run "fastboot reboot" and see if it boots or not... This should take care of your problem, if not, let's go drastic:
Turn off the device and plug it in fastboot mode again onto your PC.
On the command line run "fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img" (this will flash stock recovery), and "fastboot flash system SYSTEM.img" (this will flash your system partition, in small bathes at a time, fresh.)
After that, just "fastboot reboot" and it should boot to your system (and without a factory reset!) If it bootloops for some reason, turn off the device, boot into stock recovery and wipe cache (or do a full factory reset, but that should not be necessary i think...)
Hope all this helps!
Click to expand...
Click to collapse
thank you a lot, u give me hope. When I return home I'll try everything
JBolho said:
In the link you will find Stock EMUI 8 Ramdisk, Recovery and System, as well as TWRP and a Kernel that fixes the possibility of losing the capacitive buttons. Download them into a folder on the root of your PC (for example C:\Temp)
https://www.dropbox.com/sh/88l72rypm6u1u94/AADtPyvsIFhyBl1mcJ5raTBZa?dl=0
I don't know what caused your boot to disappear, mine disappeared when i tried to unroot it from within SuperSU app (Big Mistake), but let's not be drastic just yet. You need Fastboot and ADB on your PC, turn off your phone, hold Volume - and connect the USB cable from the PC to the device. You should enter Fastboot mode. I hope your device is FRP unlocked as well.
Open a command line and input "fastboot devices" to make sure your device is connected
First let's try restoring Ramdisk, TWRP and Kernel:
Run "fastboot flash ramdisk STF-L09_ramdisk.img", then "fastboot flash recovery_ramdisk stf_twrp_oreo.img" and finally "fastboot flash kernel B360_fix_kernel.img"
After that just run "fastboot reboot" and see if it boots or not... This should take care of your problem, if not, let's go drastic:
Turn off the device and plug it in fastboot mode again onto your PC.
On the command line run "fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img" (this will flash stock recovery), and "fastboot flash system SYSTEM.img" (this will flash your system partition, in small bathes at a time, fresh.)
After that, just "fastboot reboot" and it should boot to your system (and without a factory reset!) If it bootloops for some reason, turn off the device, boot into stock recovery and wipe cache (or do a full factory reset, but that should not be necessary i think...)
Hope all this helps!
Click to expand...
Click to collapse
Hi sir I tried, everything flashes ok but when I reboot it continue bootloops until it enter into erecovery. I tried to wipe data but when I press the button to wipe cache after it displays a red '!' into the circle and the same for the wiping data.
sorry for my English, how can I solve ..? FRP was written "FRP unlock"
leocap33 said:
Hi sir I tried, everything flashes ok but when I reboot it continue bootloops until it enter into erecovery. I tried to wipe data but when I press the button to wipe cache after it displays a red '!' into the circle and the same for the wiping data.
sorry for my English, how can I solve ..? FRP was written "FRP unlock"
Click to expand...
Click to collapse
Everything flashes ok, no errors? What did you flash? Everything?
eRecovery is to rescue the device, that won't work with Oreo (at least not for me). The stock recovery you enter it by keeping the Vol + pressed and power up the device (just as TWRP), you can enter it? And it gives error when wiping the cache?
JBolho said:
Everything flashes ok, no errors? What did you flash? Everything?
eRecovery is to rescue the device, that won't work with Oreo (at least not for me). The stock recovery you enter it by keeping the Vol + pressed and power up the device (just as TWRP), you can enter it? And it gives error when wiping the cache?
Click to expand...
Click to collapse
yes it gives me an error while I wipe cache or factory data. I enter normally into recovery with vol+.
leocap33 said:
yes it gives me an error while I wipe cache or factory data. I enter normally into recovery with vol+.
Click to expand...
Click to collapse
What ROM exactly were you using? OldDroid's B360? Or some other?
I were using the stock emui8 I don't know the build number because I can't get it. My region is italy
leocap33 said:
I were using the stock emui8 I don't know the build number because I can't get it. My region is italy
Click to expand...
Click to collapse
The only explanation i see is that the EMUI8 you were using has something different from the one in OldDroid's thread... On mine i did exactly what i told you, those files are the ones i used on mine as well.
Right now you have everything stock right? Can you try to flash one of the Treble Roms? Either AOSP or RR-O?
You just have to download them (they're a system.img file) and run the "fastboot flash system system.img" command, go to recovery and factory reset. Your device should boot.
If everything fails, the only hope i see if to go to OldDroid's thread - https://forum.xda-developers.com/honor-9/how-to/stf-l09c432-how-to-install-oreo-h9-t3707729 and download the files, and follow the instructions on the OP to rollback to Nougat.
sonneper said:
Did you take a look here ?
http://droidvendor.com/download-8-0-0-360-c432-official-oreo-for-honor-9-stf-l09/
sorry, I'm not expert on this topic, it's the only help i can give you
Click to expand...
Click to collapse
I think the link you probided is a fake bull$hiting guide :
1) it states european C432 but provided two of the three files of a russian C10 firmware.
2) almost sure. the file provided won't flash the dload way as stated in guide.
leocap33 said:
Hi everybody I got an honor 9 STF-L09, my region is italy. I got bricked and I want to install the stock firmware because my phone doesnt on again. I have Twrp installed and unlocked bootloader but when i try to boot into system it says "Func NO: 10 (boot image)".
I tried to flash firmware from thi guide https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892 but nothing to do.
I tried to flash using twrp but the ionstallation fail everytime.
Is there someone that can help me with a stock firmware or even other firmwares that makes my H9 on againg.
Please help me I'am DESPERATE
Click to expand...
Click to collapse
OK, so you were on oreo, and now the nougat's service repair dload firmware are not working.
I'll start by asking:
-how do you get bricked, what did you do just before ?
Try this tool for honor 9:
https://forum.xda-developers.com/newreply.php?do=newreply&p=75084955
(xda link to russian tool)
https://forum.xda-developers.com/newreply.php?do=newreply&p=75661658
(xda link to english translated scripts)
http://4pda.ru/forum/index.php?showtopic=833645&st=2400#entry69940847
(pda link to russian tool)
Same here, I just have access to eRecovery and fastboot mode
I was on the last version (oreo) and I wanted root my phone so I have unlock bootloader and install twrp but after twrp install in the wipe my internal stockage was empty and when I wanted install supersu I have some error like failed to mount: data, failed to mount: cache, ect..
but I still had access to my phone
Except that I had to go through the eRecovery every time so I tried to look at the side of my errors mount and I tried unbrick with the software Huawei Multi Tool and images of a rom stock publish on the forum except that I had even more access to my phone but I no longer have the errors mount.. With Huawei Multi Tool I have try the recovery option but nothing, now I don't know what make
Hi everyone I tried all the tools given into this thread but no success, it seems like a big lost challenge
Tell us more..
so you were on oreo or nougat before brick ?
and now the nougat's service repair dload firmware are not working ?
how do you get bricked, what did you do just before ?
Yeah never see a sht like that, I guess we have to send our phones to a huawei repair center..
Ok you were on oreo emui8.
Hello
I 'm using Lenovo Tab 2 a7-10f
I tried to flash TWRP recovery throught fastboot.
But i didnt succeed before, so this time, i tried to enter command to open TWRP without need to install it.
___________
I entered fastboot mode via command
adb reboot bootloader
and yes, i did unlocked bootloader
___
then i used this command to put recovery in my tablet just to open that recovery
fastboot -c "lge.kcal=0|0|0|x" boot c:\twrp.img
______
i found this solution on this site
https://android.stackexchange.com/questions/86936/how-to-flash-root-zip-in-fastboot/102597
_______
And now, it is in bootloop, until i click both volume up and down , then it enters TWRP
_______
Tried to go in TWRP , Reboot > Power Off
And it shows logo and dont proccedd more, just stuck there and spining
Until i press both volume up and down, so it opens me TWRP recovery
________
Also tried to go into Reboot > System
But still same issue, not booting up at all
___
If i click Reboot > Recovery
Then it boots me back in TWRP
______
I tried already SPFlash tool before, but it doesnt detect my tablet, even if i have all drivers, and google drivers, and USB debbuging, i'm using this tablet for android app development, so it have all drivers.
_______
I managed to get my data from tablet.
I dont know what to do next.
Should i make some command from computer to boot system, using ADB, i know to use ADB, just i stucked in this weird bootloop.
_____
I'm thinking that i should flash stock ROM from TWRP while it is still alive.
Should i do that, i dont want to lose my data, i have many programs.
I dont care if i lose TWRP recovery, i dont need it after this experience right now???
What should i do
If you flash stock can you resume control and appreciate with repatching of recovery
([emoji813]9/[emoji725]/9[emoji813])
PoochyX said:
If you flash stock can you resume control and appreciate with repatching of recovery
([emoji813]9/[emoji725]/9[emoji813])
Click to expand...
Click to collapse
O, oh man, i just got shocked !!! By all this.
I understood that my problem is in boot,
because this command
fastboot -c "lge.kcal=0|0|0|x" boot c:\twrp.img
tells android that when i press power button, to boot into whatewer it is pointed to.
So this command tells android to boot recovery instead of normal system.
So i just reverted it in bootloader (fastboot) mode, by pushing command
fastboot flash boot c:\boot.img
So it booted up again ) , and also important, without losing any precious data. ))
______
It is true when people say that if everything fails in android, there is always a bootloader that you cant destroy.
And also here are commands for other partitions, in this way you can flash whole system without root or anything, for anybody who face this problem which is very hard to break without ADB, because i think even if i flash stock ROM it will boot recovery because somewhere deep inside, it is written from that bootloader,
Again, never joke with bootloader, if it dont support, it dont support and over, i dont want TWRP anymore.
Dont get in this trouble, mybe nobody will be able to fix it if he dont know how it happened.
______
Commands
_______
adb reboot bootloader (to go into bootloader)
fastboot flash boot boot.img (this is i used)
fastboot flash system system.img (this is ROM, like kitkat, or lolipop)
fastboot flash userdata userdata.img (this can be optional, it means full reset)
fastboot flash recovery recovery.img ( if on twrp , dont flash this thing if not cause problems)
indestructible master said:
O, oh man, i just got shocked !!! By all this.
I understood that my problem is in boot,
because this command
fastboot -c "lge.kcal=0|0|0|x" boot c:\twrp.img
tells android that when i press power button, to boot into whatewer it is pointed to.
So this command tells android to boot recovery instead of normal system.
So i just reverted it in bootloader (fastboot) mode, by pushing command
fastboot flash boot c:\boot.img
So it booted up again ) , and also important, without losing any precious data. ))
______
It is true when people say that if everything fails in android, there is always a bootloader that you cant destroy.
And also here are commands for other partitions, in this way you can flash whole system without root or anything, for anybody who face this problem which is very hard to break without ADB, because i think even if i flash stock ROM it will boot recovery because somewhere deep inside, it is written from that bootloader,
Again, never joke with bootloader, if it dont support, it dont support and over, i dont want TWRP anymore.
Dont get in this trouble, mybe nobody will be able to fix it if he dont know how it happened.
______
Commands
_______
adb reboot bootloader (to go into bootloader)
fastboot flash boot boot.img (this is i used)
fastboot flash system system.img (this is ROM, like kitkat, or lolipop)
fastboot flash userdata userdata.img (this can be optional, it means full reset)
fastboot flash recovery recovery.img ( if on twrp , dont flash this thing if not cause problems)
Click to expand...
Click to collapse
You good now...
([emoji813]9/[emoji725]/9[emoji813])
m
I can't install any rom, ADB sideload fails with this error:
Unable to mount storage.
Devices on super may not mount until rebooting recovery.
To flash additional zips, please reboot recovery to switch to the updated slot.
I already tried to switch the slots many times.
I also tried to format data, but it tells me:
E: unable to check merge status
Updating partition details...
...done
Unable to mount storage
I can access the recovery and the factory-reset android, but i can't do anything more.
I think the problem is relative to encryption but I can't even format data, so I don't know how to escape this...
Now I can't even access the rom, I can only access TWRP and fastboot. The problem is that format data does not work, with the same error:
E: unable to check merge status
I tried repairing and changing filesystem, now I don't really know what to do...
just install rom using fast boot tool and
format data after that
muneeb rizwan said:
just install rom using fast boot tool and
format data after that
Click to expand...
Click to collapse
I have never used fastboot tool. I'm on linux. Is this the program i must install?
And also, do I need a fastboot rom?
[Tool] Flash Custom ROMs through Fastboot [mojito / sunny]
Are you struggling to install custom roms on this device? Lots of recovery errors? Can't boot to any rom? Don't worry. Fastboot is a good way to avoid such nonsense... Install any custom rom & miui recovery rom through fastboot Steps: 1...
forum.xda-developers.com
USE THIS TOOL AND YOU DONT NEED FASTBOOT ROM
Ok, i installed CrDroid with fastboot tool, then format data and then re-flashed the rom with adb, but the phone starts just on the CrDroid recovery (slot b) or on fastboot (slot a)...
What is the correct process to install a ROM? This A/B thing gets me mad
Now I managed to install an old MIUI fastboot rom from this link with XiaomiADBFastbootTools (a kind of mi flash tool for linux) and this rom now it is working, so I think I had some problems with the fastboot tool you suggested. But I don't really know what was the problem, the installation process seemed to work, It restarted to recovery, I rebooted to system but then it kept returning to recovery or to fastboot without entering in the system...
Switching slots directly in recovery is not functional. Just look after switching what the active slot is and you will see that it has not changed. Do the slot switching with the fastboot command from the PC.
fastboot --set-active=a
fastboot --set-active=b
StaryMuz said:
Switching slots directly in recovery is not functional. Just look after switching what the active slot is and you will see that it has not changed. Do the slot switching with the fastboot command from the PC.
fastboot --set-active=a
fastboot --set-active=b
Click to expand...
Click to collapse
yes, I was using these commands to switch slots. but when it is necessary to switch slots in the flashing process? I mean, what is the correct order? format - flash rom with adb - reboot to fastboot - switch slot - reboot to system...is this correct?
Slot swapping may not be required. Do it only when it is requested or when the boot crashes into recovery.
StaryMuz said:
Slot swapping may not be required. Do it only when it is requested or when the boot crashes into recovery.
Click to expand...
Click to collapse
OK, so is this the correct order?
Format - flash rom with adb - reboot to system
Now I have a problem with fastboot...I don't know why but it can't boot any recovery...
"fastboot boot recovery.img" remains stuck at:
Sending 'boot.img' (131072 KB)
Click to expand...
Click to collapse
and nothing happens! I tried with TWRP and OrangeFox.
I also tried to change slot but it fails:
fastboot --set-active=a
Setting current slot to 'a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
The command 'Fastboot reboot' gives me a black screen with a white message: 'any key to shutdown', then the phone reboots to system...
What is the full designation of your phone?
StaryMuz said:
What is the full designation of your phone?
Click to expand...
Click to collapse
what is the designation?
Xiaomi Redmi Note .....
All of it, exactly.
StaryMuz said:
Xiaomi Redmi Note .....
All of it, exactly.
Click to expand...
Click to collapse
Redmi Note 10 64GB/4GB, I think the codename is sunny because I have the global/european version. Do you need more?
I think the best step is to upload the original Miui using MiFlash with the "clear all" setting.
Use this version of MiFlash.
You can get the right Miui here.
Before using MiFlash, I recommend loading the boot.img included in the downloaded Miui into your phone in fastboot mode.
Use the command:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Then use MiFlash and don't play Miui. Wait until the phone starts itself, then you can disconnect it.
If anything is not clear, ask questions.
StaryMuz said:
I think the best step is to upload the original Miui using MiFlash with the "clear all" setting.
Use this version of MiFlash.
You can get the right Miui here.
Before using MiFlash, I recommend loading the boot.img included in the downloaded Miui into your phone in fastboot mode.
Use the command:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Then use MiFlash and don't play Miui. Wait until the phone starts itself, then you can disconnect it.
If anything is not clear, ask questions.
Click to expand...
Click to collapse
Actually I'm already in a original MIUI and it is working. My pc is on linux so I can't use MiFlash but I used XiaomiADBFastbootTools (a kind of MiFlash tool for linux). Can I start from here or I have to install the MIUI version you linked?
The only thing is that I didn't specifically load the boot.img
Unfortunately I don't know the Linux version of MiFlash. They may not work equivalently. It needs to properly clean all the partitions of the phone and load all the files supplied in the ROM.
I recommend to use the Miui listed by me.