Anyone knows why flashing logo.img does not apply in MIUI 13 Android 12 Xiaomi.eu stable and others MIUI 13?
I tried every possible way. The funny thing is after flashing the image if I extract it from the phone an put it in the Logo Manager application it show the one that I flashed but on my phone when is booting it shows the stock one no matter what. This happens only on this Rom on stock Rom MIUI 11 everything work correctly.
I just wanna know if there is a fix or am I doing something wrong.
I could really use some clarifying because I am going nuts. Thank you in advance.
nokio85 said:
Anyone knows why flashing logo.img does not apply in MIUI 13 Android 12 Xiaomi.eu stable and others MIUI 13?
I tried every possible way. The funny thing is after flashing the image if I extract it from the phone an put it in the Logo Manager application it show the one that I flashed but on my phone when is booting it shows the stock one no matter what. This happens only on this Rom on stock Rom MIUI 11 everything work correctly.
I just wanna know if there is a fix or am I doing something wrong.
I could really use some clarifying because I am going nuts. Thank you in advance.
Click to expand...
Click to collapse
Which method to flash twrp or cmd?
cmd=.\fastboot flash logo logo.img
NOSS8 said:
Which method to flash twrp or cmd?
cmd=.\fastboot flash logo logo.img
Click to expand...
Click to collapse
I was using TWRP but mainly ADB or cmd how u call it, the thing is it does flash it where it supposed to be just that the phone always loads the stock one don't even know how it's possible if it's replaced by the one I flashed.
I was using TWRP but mainly ADB or cmd how u call it, the thing is it does flash it where it supposed to be just that the phone always loads the stock one don't even know how it's possible if it's replaced by the one I flashed.
nokio85 said:
I was using TWRP but mainly ADB or cmd how u call it, the thing is it does flash it where it supposed to be just that the phone always loads the stock one don't even know how it's possible if it's replaced by the one I flashed.
Click to expand...
Click to collapse
For this type of rom twrp is not recommended.
It's not an ADB command but Fastboot.
The phone must be in fastboot mode.
If the logo.img is called Logo the command is:
.\fastboot flash logo Logo.img
NOSS8 said:
For this type of rom twrp is not recommended.
It's not an ADB command but Fastboot.
The phone must be in fastboot mode.
If the logo.img is called Logo the command is:
.\fastboot flash logo Logo.img
Click to expand...
Click to collapse
Sorry my mistake that what i was using fastboot flash logo logo.img and it works my dude it flashes the file cause if i extract it from phone after flasing i load it in Logo Manager and it's the one i flashed it's just that when phone is booting it's showing the STOCK logo not the one that it's flashed. You understand what i am saying?
nokio85 said:
Sorry my mistake that what i was using fastboot flash logo logo.img and it works my dude it flashes the file cause if i extract it from phone after flasing i load it in Logo Manager and it's the one i flashed it's just that when phone is booting it's showing the STOCK logo not the one that it's flashed. You understand what i am saying?
Click to expand...
Click to collapse
I had understood from the beginning but I wanted to make sure that you used the correct command.
Could be a problem with 13 roms.
ask here:https://xiaomi.eu/community/
Logo.img for miui 13 =28884 ko
NOSS8 said:
I had understood from the beginning but I wanted to make sure that you used the correct command.
Could be a problem with 13 roms.
ask here:https://xiaomi.eu/community/
Logo.img for miui 13 =28884 ko
Click to expand...
Click to collapse
Hmmm so does the size matter?
But the logo is there is flashed....makes no sense.
Anyway thank you very much for your time my friend i will continue my research it's really annoying this is. xD
nokio85 said:
Hmmm so does the size matter?
But the logo is there is flashed....makes no sense.
Anyway thank you very much for your time my friend i will continue my research it's really annoying this is. xD
Click to expand...
Click to collapse
It always indicates that the flash is correct but at the start nothing changes.
On miui 12 I made some logo that was either smaller or bigger than the original and it worked. (+or- a few ko).
BTW
Have you tried removing security on the lock screen rebooting and flashing the logo.
NOSS8 said:
It always indicates that the flash is correct but at the start nothing changes.
On miui 12 I made some logo that was either smaller or bigger than the original and it worked. (+or- a few ko).
BTW
Have you tried removing security on the lock screen rebooting and flashing the logo.
Click to expand...
Click to collapse
I know on MiUI 12.5 i had succes with every logo i flashed
It's not only showing that the flash was a success i can see it was
So i do it like this:
fastboot flash logo logo.img
after flash i do
$# dd if=/dev/block/bootdevices/by-name/logo of=/sdcard/logo.img
to extract the logo from the phone
after i check it in Logo Manager and what do you know it's the one that i flashed.
But when booting it's not using it.
Related
Help me please, i've flashed a rom of X9076 on my X9077 chinese, now my display is black, i feel vibration, i hear sounds of boot and i can go in fastboot but i don't see anyting on display, i tryed to flash successfully a recovery but i can use cause i don't see anything...anyone can link me a rom for X9077 to flash in fastboot please?????is the only thing i can try i mean!
hermanndj said:
Help me please, i've flashed a rom of X9076 on my X9077 chinese, now my display is black, i feel vibration, i hear sounds of boot and i can go in fastboot but i don't see anyting on display, i tryed to flash successfully a recovery but i can use cause i don't see anything...anyone can link me a rom for X9077 to flash in fastboot please?????is the only thing i can try i mean!
Click to expand...
Click to collapse
It's amazing that people don't even bother to read, let alone search. This thread even has the words "blank screen" in the title..
http://forum.xda-developers.com/find-7/help/help-blank-screen-recovery-start-phone-t2801032
tropical cactus said:
It's amazing that people don't even bother to read, let alone search. This thread even has the words "blank screen" in the title..
http://forum.xda-developers.com/find-7/help/help-blank-screen-recovery-start-phone-t2801032
Click to expand...
Click to collapse
i read! but i don't fetch a X9077 rom to flash the blob partitions to my phone using fastboot (aboot, modem, etc...)!!
That should fix any low-level-driver issues you might be having (screen, digitizer, sensors, etc). i can view any rewcovery, i installed it succesflly but i don't see
hermanndj said:
i read! but i don't fetch a X9077 rom to flash the blob partitions to my phone using fastboot (aboot, modem, etc...)!!
That should fix any low-level-driver issues you might be having (screen, digitizer, sensors, etc). i can view any rewcovery, i installed it succesflly but i don't see
Click to expand...
Click to collapse
Which recovery did you use sir? Is it TWRP or CWM?
FareedYusoff said:
Which recovery did you use sir? Is it TWRP or CWM?
Click to expand...
Click to collapse
i try twrp and the original stock...but i can't see anything cause display is black..i think the only solution is flash via fastboot a stock rom ( if i'll find it)
hermanndj said:
i try twrp and the original stock...but i can't see anything cause display is black..i think the only solution is flash via fastboot a stock rom ( if i'll find it)
Click to expand...
Click to collapse
Can't say if you will be able to flash it with fatsboot, but this is the stock rom for your model :
https://www.dropbox.com/s/b12yq35jyout4ed/FIND7_12_OTA_010_all_svn7963.zip
Flash stock recovery on it through fastboot and then stock ROM (v1.2.1i or so). I'll update this post once I find the links again to the ROM and the Recovery.
Edit:
Recovery: http://ge.tt/2EQ5h2m1/v/0?c
ROM: http://mirror.lucky.li/android/oppo/x90x6/firmware/
Taken from: http://www.oppoforums.com/threads/stock-recovery-for-find-7-7a.17397/#post-220682
Don't forget to wipe data of course before flashing this on.
mathieudevos said:
Flash stock recovery on it through fastboot and then stock ROM (v1.2.1i or so). I'll update this post once I find the links again to the ROM and the Recovery.
Edit:
Recovery: http://ge.tt/2EQ5h2m1/v/0?c
ROM: http://mirror.lucky.li/android/oppo/x90x6/firmware/
Taken from: http://www.oppoforums.com/threads/stock-recovery-for-find-7-7a.17397/#post-220682
Don't forget to wipe data of course before flashing this on.
Click to expand...
Click to collapse
Thanks guy butwhen i flash the recovery i can't do anything cause i can see the command on screen ( is black..)
hermanndj said:
Thanks guy butwhen i flash the recovery i can't do anything cause i can see the command on screen ( is black..)
Click to expand...
Click to collapse
Even after you flash the recovery in fastboot and after that reboot the phone with: "fastboot reboot". At that time keep pressing volume down and you should arrive in your recovery with visuals...
Same issue
Hi, all!
I'm experiencing the very same issue on x9076 (intl) right after attempting flashing 2.0.0i in stock 1.2 recovery.
Everything is working, but I see nothing but black screen. Neither image, nor splash, not even "fastboot" word.
All the operations in fastboot work ok though.
What could I attempt to fix it? Or at least how could I make some diagnostics?
same issue here...i put my find 7 in the freezer...then the display come out again...try it out. but make sure wrap your phone with a plastic bag first... black screen again everytime i restart my hp. have to put it in the freezer again.
Turn off your hp first before putting it inside the freezer. once the hp become at least less than 10°c you can try to turn on you hp.
Hi
Can anyone help with this ?
I am stuck on a Linux logo on my screen
I am unable to go into recovery or Bootloader mode
However if I Fastboot, it recognize the device
I tried flashing the recovery image and It Flashed successfully; Yet I cannot boot into Recovery
I tried Flashing the the Bootloader and the same
Funny thing is all Fastboot commands seem to work, like rebooting the Bootloader, but it goes straight to the Linux logo
see picture attached
Thank you.
Voyebanm said:
Hi
Can anyone help with this ?
I am stuck on a Linux logo on my screen
I am unable to go into recovery or Bootloader mode
However if I Fastboot, it recognize the device
I tried flashing the recovery image and It Flashed successfully; Yet I cannot boot into Recovery
I tried Flashing the the Bootloader and the same
Funny thing is all Fastboot commands seem to work, like rebooting the Bootloader, but it goes straight to the Linux logo
see picture attached
Thank you.
Click to expand...
Click to collapse
Did you erase the system? If not try to flash for fastboot just boot.img, maybe help you, if don't reboot flash the entire rom image
I was testing volte.zip. I already tried flashing the boot file, still nothing. I tried flashing miui global fastboot with miflash still no luck. It sees the device but flashed for 5s and then said successful.
did u check "clean all" and try edl mode (just a reminder,it happened to me many times,i was impatient/panicked forgot to check "clean all")
Voyebanm said:
I was testing volte.zip. I already tried flashing the boot file, still nothing. I tried flashing miui global fastboot with miflash still no luck. It sees the device but flashed for 5s and then said successful.
Click to expand...
Click to collapse
I have never seen this linux logo before on Mi Max and I can assure you I am on top of everything happening around it...
I think you did something hmmm... excuse me but stupid... That volte.zip is for kenzo and it flashes all partitions that you are not supposed to flash with anything but hydrogen specific images... Your only option is EDL mode flashing and I am not even sure if it is going to work.
Good luck...
nijel8 said:
I have never seen this linux logo before on Mi Max and I can assure you I am on top of everything happening around it...
I think you did something hmmm... excuse me but stupid... That volte.zip is for kenzo and it flashes all partitions that you are not supposed to flash with anything but hydrogen specific images... Your only option is EDL mode flashing and I am not even sure if it is going to work.
Good luck...
Click to expand...
Click to collapse
No Luck so far.
Voyebanm said:
No Luck so far.
Click to expand...
Click to collapse
That seem be a similar case at inverse (Hydrogen on Helium) but maybe help you: http://forum.xda-developers.com/showpost.php?p=68205960&postcount=24
SubwayChamp said:
That seem be a similar case at inverse (Hydrogen on Helium) but maybe help you: http://forum.xda-developers.com/showpost.php?p=68205960&postcount=24
Click to expand...
Click to collapse
I will give that a try. Thanks
http://en.miui.com/a-234.html
Install MiFlash from Xiaomi, download fastboot image and unpack it.
http://xiaomitips.com/guide/how-to-put-mi-max-into-edl-mode/
Boot to EDL mode with hard keys method, screen stays black, but Qualcomm QH USB device shows up in Device Manager/Ports. MiFlash fastboot image.
If you have 8 or newer Windows, you have to boot it driver signature verification disabled before MiFlash install:
http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
SubwayChamp said:
That seem be a similar case at inverse (Hydrogen on Helium) but maybe help you: http://forum.xda-developers.com/showpost.php?p=68205960&postcount=24
Click to expand...
Click to collapse
Thank you all for the suggestions, but this helped me to fix the problem and it was easy to perform
PS: I spoke too fast now my SIM card is not detected, in both slots
Voyebanm said:
Thank you all for the suggestions, but this helped me to fix the problem and it was easy to perform
PS: I spoke too fast now my SIM card is not detected, in both slots
Click to expand...
Click to collapse
What did you do to understand, maybe wrong firmware, maybe just a problem of modem partition, if you are using DualBootPatcher try with a CM based rom like primary, other possibility is to flash just NON-HLOS.bin of corrrect rom in fastboot mode, maybe wrong file in Update Firmware folder (in zip rom), go with a file explorer to /data/nvram if it`s generated for the new rom, take a backup first and delete after, reboot device (if this is the case) and check again your sim.
SubwayChamp said:
What did you do to understand, maybe wrong firmware, maybe just a problem of modem partition, if you are using DualBootPatcher try with a CM based rom like primary, other possibility is to flash just NON-HLOS.bin of corrrect rom in fastboot mode, maybe wrong file in Update Firmware folder (in zip rom), go with a file explorer to /data/nvram if it`s generated for the new rom, take a backup first and delete after, reboot device (if this is the case) and check again your sim.
Click to expand...
Click to collapse
Thank you though, I was able to resolved it by flashing the EFS backup that I had.
Problem SOLVED !!!
Thanks again for your Help.
I got a bricking when I tried flashing MIUI EU ROM over CM on a locked bootloader. Is there a way to flash the latest firmware files without also flashing a new boot image which could brick the phone? I had to do an EDL flash using MiFlash last time, I don't want to go through the hassle again.
Hi guys, I searched around the forum before posting this so I apologize but I recently installed a new rom and possibly a wrong kernel with it. Afterwards, if I try to turn it on, it just shows the logo and then turns right off. I can't even go into recovery since it does the same. The only thing I can do is boot it into fastboot but I'm not sure where to go from here. I tried using a guide with no success.
Any words of wisdom?
reflash your recovery via fastboot, then boot into recovery and do a clean install
fastboot flash [recovery].img
I tried reflashing recovery but all it does is show the old rom logo that was used and then shuts down.
Hi,
Read carefully and try this guide:
forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
which rom did you flash? You need the correct twrp file for your bootloader.
That's the first place I tried. Anytime I hook-up my phone to the PC it shows up as OnePlus Android bootloader interface under Android phone and I can't seem to update the drivers..
matze19999 said:
which rom did you flash? You need the correct twrp file for your bootloader.
Click to expand...
Click to collapse
I used the Freedom Rom 2.0
Arken2121 said:
I used the Freedom Rom 2.0
Click to expand...
Click to collapse
you need this twrp file:
https://forum.xda-developers.com/devdb/project/dl/?id=21835
matze19999 said:
you need this twrp file:
https://forum.xda-developers.com/devdb/project/dl/?id=21835
Click to expand...
Click to collapse
Thank you so much, I guess I installed the wrong TWRP and I can FINALLY get into recovery. Thank you so much.
Hi all,
*I've unlocked bootloader
* Have tried fastboot boot TWRP.img, as well as tried flashing TWRP RC1 via the Skipsoft toolkit.
Every way I've tried the phone just sits at the TWRP boot screen and doesn't allow me to go any further..
Any help here would be truly appreciated!
Cheers,
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
You're braver than me. I haven't had my Pixel XL long but this is the first phone I've ever owned where I am afraid to try and install a custom recovery and ROM. With the dual partitions and what I hear about TWRP still being buggy it just seems like Google didn't want people to run anything but pure Android on the Pixels.
dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....
mikefnz said:
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....
Click to expand...
Click to collapse
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.
mac796 said:
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.
Click to expand...
Click to collapse
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?
XtraArrow said:
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?
Click to expand...
Click to collapse
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!
mazubo said:
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!
Click to expand...
Click to collapse
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.
XtraArrow said:
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.
Click to expand...
Click to collapse
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..
mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1 zip
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again
mazubo said:
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..
Click to expand...
Click to collapse
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??
mac796 said:
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again
Click to expand...
Click to collapse
Hmm, maybe this is where I've gone wrong.. I thought the need to create a security pin/pattern was only if coming from a previously rooted state, or from a custom ROM. I will try this as well and report back.. thanks!
XtraArrow said:
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??
Click to expand...
Click to collapse
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..
mazubo said:
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..
Click to expand...
Click to collapse
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.
XtraArrow said:
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.
Click to expand...
Click to collapse
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!
mazubo said:
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!
Click to expand...
Click to collapse
I'm no expert but it's seems like a decent suggestion. Let us know how it goes.
@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!
Just wait. It will take little longer
Sent from my Pixel XL using Tapatalk
freddy0872 said:
@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!
Click to expand...
Click to collapse
Yes, I have tried fastboot to flash the TWRP img, as well as skipsofts toolkit. I guess I've been using the term "flash" for fastboot, as I haven't been able to use twrp yet.. I understand that you need to flash the TWRP img via pc and then flash the TWRP zip, then SuperSU or magisk, whatever your poison may be !
I was buy this phone a few days ago with ubl already. I think that was great because i don't need to unlock the bootloader by myself. Since this my first xiaomi phone, unlocking the bootloader may gave me headache. But when i tried to flash twrp, i face a problem that adb said "FAILED (remote: Requested download size is more than max allowed)". At the same time, in fastboot screen shown "press anykey to shutdown". Is somebody here know what must i do? I was spend at least six days looking for solution on internet.. but, still no luck. Hope someone here will help. Any suggestions will so appreciated.
-Sorry for my bad English
Additional info:
On me, isn't driver or port or my windows 10 problem like some people saying since i can run any fastboot commands (flashing twrp too) with another xiaomi phone.
Check this thread
https://forum.xda-developers.com/re...uide-fix-locking-bootloader-fake-ubl-t3833631
deathbearer said:
Check this thread
https://forum.xda-developers.com/re...uide-fix-locking-bootloader-fake-ubl-t3833631
Click to expand...
Click to collapse
Sorry for late replying.. Actually, i though fake UBL is not the problem since my device can bind mi account. I do research for 2 weeks and find nothing can solved this problem
Kratos-mgc said:
Sorry for late replying.. Actually, i though fake UBL is not the problem since my device can bind mi account. I do research for 2 weeks and find nothing can solved this problem
Click to expand...
Click to collapse
Get this zip : https://files.orangefox.website/OrangeFox-Stable/whyred/
Extract it.. find recovery.img and put it in your fastboot folder, run 'fastboot boot recovery.img'.. now, after going to recovery the device will show up as storage in Windows, and put the orange fox zip in internel memory and flash it with booted recovery....
DKWxda said:
Get this zip : https://files.orangefox.website/OrangeFox-Stable/whyred/
Extract it.. find recovery.img and put it in your fastboot folder, run 'fastboot boot recovery.img'.. now, after going to recovery the device will show up as storage in Windows, and put the orange fox zip in internel memory and flash it with booted recovery....
Click to expand...
Click to collapse
Thanks.. Downloading file right now. I thought i've done that before with older version of OrangeFox without luck. Have try with Official TWRP and RedWolf too with same result. But, will try with latest version like you said :highfive:
Kratos-mgc said:
Thanks.. Downloading file right now. I thought i've done that before with older version of OrangeFox without luck. Have try with Official TWRP and RedWolf too with same result. But, will try with latest version like you said :highfive:
Click to expand...
Click to collapse
Np .. post here what happened..
DKWxda said:
Np .. post here what happened..
Click to expand...
Click to collapse
Sure
DKWxda said:
Np .. post here what happened..
Click to expand...
Click to collapse
Same as before.. fail either. What should i gonna do now?
Actually, my phone already had twrp installed with custom rom too after 2 weeks use time. I can't find solution for my problem so i do unusually step (or you can say frustrating step). Do test point things and flash rom like usual. But, before i replace stock recovery with twrp and rename it like stock one. After that, just start flashing and when it finish, boot to recovery directly and flash magisk plus no verity. Then i got twrp and root.. But, still can't flash anything from fastboot, even flashing with miflash. Just curious what exactly the problem is. I know can repeat the same step just in case i got problem to boot and somehow can't boot to twrp too. But, you know.. that takes lot of time to do
I don't know if ur problem is solved by now, i think you should flash latest dev firmware, that might be the key, have you ever done that after the problem? You should use twrp to do that tho.. and pls take note, every firmware is not supported by everry recovery, but i trust orange fox, and don't try to downgrade firmware too, check always if the cutom rom support the firmware you gonna flash and also check ARB value...
Edit: what does this mean
replace stock recovery with twrp and rename it like stock one