use only with L78032
Z5_Pro_GT_TOOL
Unlocked and TWRP installed, but...
Everything worked great (didn't use your batch file, pulled the files and flashed manually) but now the system just sits at the Lenovo logo after the "unlocked device" warning and never boots. I can see the filesystem from within TWRP but nothing works to get it to boot, and this is only a secondary phone so I didn't try to do a backup before flashing anything...
You wouldn't happen to have a flashable stock firmware for this thing, would you? It's a long shot to ask, I know, but now I basically have a brick with TWRP installed lol. I have the 8.1 Qualcomm firmware in a QPST zip file, but the QFIL tool never works and I have no idea how to build firmware using the files inside the zip.
Any advice?
Thanks either way, at least I was able to unlock and flash TWRP. :good:
noobly_dangers said:
Everything worked great (didn't use your batch file, pulled the files and flashed manually) but now the system just sits at the Lenovo logo after the "unlocked device" warning and never boots. I can see the filesystem from within TWRP but nothing works to get it to boot, and this is only a secondary phone so I didn't try to do a backup before flashing anything...
You wouldn't happen to have a flashable stock firmware for this thing, would you? It's a long shot to ask, I know, but now I basically have a brick with TWRP installed lol. I have the 8.1 Qualcomm firmware in a QPST zip file, but the QFIL tool never works and I have no idea how to build firmware using the files inside the zip.
Any advice?
Thanks either way, at least I was able to unlock and flash TWRP. :good:
Click to expand...
Click to collapse
flash magisk to patch boot file
a601943 said:
flash magisk to patch boot file
Click to expand...
Click to collapse
Unfortunately I can't boot into the phone itself, so patching the boot image won't work with Magisk since you have to use the Magisk Manager app to patch (unless there's some way to do it from recovery or fastboot of which I'm not aware).
Z5_Pro_GT_TOOL link goes 404 not found.
a601943 said:
flash magisk to patch boot file
Click to expand...
Click to collapse
noobly_dangers said:
Everything worked great (didn't use your batch file, pulled the files and flashed manually) but now the system just sits at the Lenovo logo after the "unlocked device" warning and never boots. I can see the filesystem from within TWRP but nothing works to get it to boot, and this is only a secondary phone so I didn't try to do a backup before flashing anything...
You wouldn't happen to have a flashable stock firmware for this thing, would you? It's a long shot to ask, I know, but now I basically have a brick with TWRP installed lol. I have the 8.1 Qualcomm firmware in a QPST zip file, but the QFIL tool never works and I have no idea how to build firmware using the files inside the zip.
Any advice?
Thanks either way, at least I was able to unlock and flash TWRP. :good:
Click to expand...
Click to collapse
I guess you were from ZUI ? It has been warned that you are likely to have bootloop after unlocking bootloader. Try this :
- "format data" using twrp
- boot into system
If that doesn't work, flash custom firmware or GSI. Flash through qfil will be your last resort.
Having the same issues here? I would like to fix the phone where can I get an official phone rom ?
Eu consegui resolver apenas pelo qfil, restaurei a stock ROM, com isso o aparelho iniciou novamente.
Supertitan said:
Having the same issues here? I would like to fix the phone where can I get an official phone rom ?
Click to expand...
Click to collapse
No you tube você consegue uma stock ROM, faça com a versão 10.5 da zui
Related
I accidentally flashed a custom rom after i thought I'd unlocked my bootloader, the bootloader was not unlocked and now I'm in a error loop, Help? or advice? I'm very new to this stuff
If you can get to bootloader, from off hold power and up volume key until ASUS logo appears, you can try to use fastboot to install an image file, get it from the pre-rooted roms thread in original android developement.
Hopefully this will fix. If you want to try a stock rom from ASUS then you still need to go to this mode, go to recovery and, if youget a n android with error underneath, hold the same buttons as above. This will allow you to either flash using ADB or you can put the downloaded zip folder on your fat32 formatted sd card, named MOFD-SDUPDATE.zip, and do a recovery stock flash by picking the update file.
Good luck...
Still no success.
My problems started when I couldn't flash xposed framework onto my rooted zenfone 2 (ze551ml). I tried different versions for intel devices from one of the links i got here. Then i tried to do it via magisk installation. I was using twrp 2.8.7.0 to flash the roms. After attempting to install magisk v7, my device couldn't boot. Have tried installing stock rom from the asus website via abd sideload and by flashing it after renaming it mofd_sdupdate.zip. The processes seeem to work fine and "complete" or "finished" messages pop up. But when i try to reboot it stops at bootloader screen or just goes directly to twrp.
Can someone help.
Veza said:
My problems started when I couldn't flash xposed framework onto my rooted zenfone 2 (ze551ml). I tried different versions for intel devices from one of the links i got here. Then i tried to do it via magisk installation. I was using twrp 2.8.7.0 to flash the roms. After attempting to install magisk v7, my device couldn't boot. Have tried installing stock rom from the asus website via abd sideload and by flashing it after renaming it mofd_sdupdate.zip. The processes seeem to work fine and "complete" or "finished" messages pop up. But when i try to reboot it stops at bootloader screen or just goes directly to twrp.
Can someone help.
Click to expand...
Click to collapse
1. Magisk on stock ROMs may require some modifications in order to work or booting correctly.
2. You may want to flash RAW firmware...
Sent from my ASUS_Z00A using XDA Labs
krasCGQ said:
1. Magisk on stock ROMs may require some modifications in order to work or booting correctly.
2. You may want to flash RAW firmware...
Click to expand...
Click to collapse
Thanks, I was able to flash the RAW firmware and now my phone works again. Had to install Intel soc drivers xfstk downloader and Asus flash tool. Quite a tideous process but worth it at the end.
Veza said:
Thanks, I was able to flash the RAW firmware and now my phone works again. Had to install Intel soc drivers xfstk downloader and Asus flash tool. Quite a tideous process but worth it at the end.
Click to expand...
Click to collapse
Glad to know. Enjoy your 'back-to-life' phone! :good:
Sent from my ASUS_Z00A using XDA Labs
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, I manually updated my honor 7x (BND AL10 INDIAN) to EMUI 8 following the other post in this forum and after that I went on to flash TWRP recovery again from another post "complete_twrp_ramdisk.img" so that I could take full Nand backups and what not. But Here's the problem, When I try to flash the stock recovery back "BND_RECOVERY_NOcheck" which I flashed during upgrading to EMUI 8, it says "size of image is large than target device"
I tried this using boot fastboot command "fastboot flash recovery_ramdisk recovery.img" and also using the TWRP. It doesn't work either way. So I'm basically stuck with TWRP. The reason I want stock recovery is because
1. I can install OTA UPDATES on EMUI 8 (I actually got one)
2. I may want to just be on complete stock like locked bootloader, sock recovery etc...
Could any one help?? Maybe I need the right stock recovery file ?
BTW It's my first post ever so please go easy if I did any mistakes.
Could you share your twrp? Thanks!
Thetpcguy said:
Hi, I manually updated my honor 7x (BND AL10 INDIAN) to EMUI 8 following the other post in this forum and after that I went on to flash TWRP recovery again from another post "complete_twrp_ramdisk.img" so that I could take full Nand backups and what not. But Here's the problem, When I try to flash the stock recovery back "BND_RECOVERY_NOcheck" which I flashed during upgrading to EMUI 8, it says "size of image is large than target device"
I tried this using boot fastboot command "fastboot flash recovery_ramdisk recovery.img" and also using the TWRP. It doesn't work either way. So I'm basically stuck with TWRP. The reason I want stock recovery is because
1. I can install OTA UPDATES on EMUI 8 (I actually got one)
2. I may want to just be on complete stock like locked bootloader, sock recovery etc...
Could any one help?? Maybe I need the right stock recovery file ?
BTW It's my first post ever so please go easy if I did any mistakes.
Click to expand...
Click to collapse
"BND_RECOVERY_NOcheck" is nouget stock recovery.
Oreo update replaces all the partitions, including the recovery that you flashed in order to install the update.
The stock recovery can be extracted from "update.app" , the one inside the oreo "updateL22.zip"
holds said:
Could you share your twrp? Thanks!
Click to expand...
Click to collapse
It's here https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500
mrmazak said:
"BND_RECOVERY_NOcheck" is nouget stock recovery.
Oreo update replaces all the partitions, including the recovery that you flashed in order to install the update.
The stock recovery can be extracted from "update.app" , the one inside the oreo "updateL22.zip"
Click to expand...
Click to collapse
Hi, I'm downloading that UPDATEL22.ZIP right now and Can I extract this with any unzip/unrar program? What will be the name of that recovery? is it going to be "recovery"? The thing is I've never extracted anything from a ROM so I have not idea.
Thetpcguy said:
Hi, I'm downloading that UPDATEL22.ZIP right now and Can I extract this with any unzip/unrar program? What will be the name of that recovery? is it going to be "recovery"? The thing is I've never extracted anything from a ROM so I have not idea.
Click to expand...
Click to collapse
you should already have the update.zip.
use same one you "manualy" installed.
winrar did not work for me but 7-zip did.
there is also rom extractor built into "multi-tool" and stand alone extractor around here some where.
I found it here
the name is just like the twrp you flashed and just like the partition that you flashed. (recovery_ramdisk.img)
Thetpcguy said:
Hi, I'm downloading that UPDATEL22.ZIP right now and Can I extract this with any unzip/unrar program? What will be the name of that recovery? is it going to be "recovery"? The thing is I've never extracted anything from a ROM so I have not idea.
Click to expand...
Click to collapse
Hi, so I figured Huawei update extractor app is the way to do it but I have a Mac and there doesn't seem to be a Mac version? is there a way to do it on android or Mac?
mrmazak said:
you should already have the update.zip.
use same one you "manualy" installed.
winrar did not work for me but 7-zip did.
there is also rom extractor built into "multi-tool" and stand alone extractor around here some where.
I found it here
the name is just like the twrp you flashed and just like the partition that you flashed. (recovery_ramdisk.img)
Click to expand...
Click to collapse
Hi, Thanks for all your replies. After doing a bit of search, I managed to get it extracted on my android using zarchiver app and I copied the recovery_ramdisk.img from that BNDL22.ZIP and when I tried flashing it using the fastboot command "fastboot flash recovery_ramdisk recovery.img" It went ok and It got installed but when I tried to boot into recovery, I got this screen "ERROR MODE" ATTENTION ETC.. I don't know where I'm going wrong?
Thetpcguy said:
Hi, Thanks for all your replies. After doing a bit of search, I managed to get it extracted on my android using zarchiver app and I copied the recovery_ramdisk.img from that BNDL22.ZIP and when I tried flashing it using the fastboot command "fastboot flash recovery_ramdisk recovery.img" It went ok and It got installed but when I tried to boot into recovery, I got this screen "ERROR MODE" ATTENTION ETC.. I don't know where I'm going wrong?
Click to expand...
Click to collapse
I dont know.
The new way to boot to recovery was written in other thread as "hold both volume buttons & power button"
not sure if it was a problem with extraction or not, but attached is the recovery I extracted. do not have it installed. I dont even have oreo installed., I'm still pulling files together and reading the update-scripts and trying to convince myself if it is worth trying it.
https://www.androidfilehost.com/?w=files&flid=262391
I have now jumped on board and did oreo conversion on L24, then flashed RR. I went and installed the oreo recovery, then back to this stock recovery. It worked fine for me.
mrmazak said:
I dont know.
The new way to boot to recovery was written in other thread as "hold both volume buttons & power button"
not sure if it was a problem with extraction or not, but attached is the recovery I extracted. do not have it installed. I dont even have oreo installed., I'm still pulling files together and reading the update-scripts and trying to convince myself if it is worth trying it.
https://www.androidfilehost.com/?w=files&flid=262391
I have now jumped on board and did oreo conversion on L24, then flashed RR. I went and installed the oreo recovery, then back to this stock recovery. It worked fine for me.
Click to expand...
Click to collapse
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Thetpcguy said:
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Click to expand...
Click to collapse
i am wipeiing my data it always show faild plss help my device is dead
Thetpcguy said:
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Click to expand...
Click to collapse
Which perticular file should i flash for stock recovery please. There are 4-5 files. Pl help. I am on RR and want to flash system.img to go back to oreo beta. But i think i do not have stock recovery as i had tried to flash twrp. Pl help
Thetpcguy said:
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Click to expand...
Click to collapse
Hey bro thefe are too many files there will it flash through fastboot or twrp and how to flash one by one pls help me
Hello all,
thanks for all the info in this thread.
I bricked my Honox 7x (BND-LC21) by trying to go Oreo.
The installation went halfway through, but now I can't complete (missing info howto flash bootloader / kernel) and I also can't go back as the partition layout has already changed to oreo style.
Steps done so far:
- unlocked boot loader
- installed twrp
- extract system image and recovery image from oreo update zip
getting the phone in fastboot mode i can successfully run
fastboot flash recovery_ramdisk recovery_ramdisk.img (i can also flash old recoveries this way, but none of them will successfully boot into recovery mode)
fastboot flash system system.img
either way, the system will not boot afterwards.
how do I manually flash bootloader / kernel on the oreo partition layout?
erecovery and hisuite won't recover my phone either...
Any hints appreciated
Aibiman
mrmazak said:
I dont know.
The new way to boot to recovery was written in other thread as "hold both volume buttons & power button"
not sure if it was a problem with extraction or not, but attached is the recovery I extracted. do not have it installed. I dont even have oreo installed., I'm still pulling files together and reading the update-scripts and trying to convince myself if it is worth trying it.
https://www.androidfilehost.com/?w=files&flid=262391
I have now jumped on board and did oreo conversion on L24, then flashed RR. I went and installed the oreo recovery, then back to this stock recovery. It worked fine for me.
Click to expand...
Click to collapse
Can I flash just the stock recovery to my phone and if so is it the recover_ramdis.img, or do I need to flash them all. I'm on mostly stock bnd-l24. Unlocked bootloader TWRP and magisk for root. There's a new update and i wanted to flash stock recovery so I could update.
kingd421 said:
Can I flash just the stock recovery to my phone and if so is it the recover_ramdis.img, or do I need to flash them all. I'm on mostly stock bnd-l24. Unlocked bootloader TWRP and magisk for root. There's a new update and i wanted to flash stock recovery so I could update.
Click to expand...
Click to collapse
Yes that is the recovery.
But if you have root, update not going to work
mrmazak said:
Yes that is the recovery.
But if you have root, update not going to work
Click to expand...
Click to collapse
Will uninstalling magisk fix that or does the boot image have to be reflashed. Thank you for the quick response
kingd421 said:
Will uninstalling magisk fix that or does the boot image have to be reflashed. Thank you for the quick response
Click to expand...
Click to collapse
From magisk manager app should be a restore images option
mrmazak said:
From magisk manager app should be a restore images option
Click to expand...
Click to collapse
Sounds good. I appreciate it.
aibiman said:
Hello all,
thanks for all the info in this thread.
I bricked my Honox 7x (BND-LC21) by trying to go Oreo.
The installation went halfway through, but now I can't complete (missing info howto flash bootloader / kernel) and I also can't go back as the partition layout has already changed to oreo style.
Steps done so far:
- unlocked boot loader
- installed twrp
- extract system image and recovery image from oreo update zip
getting the phone in fastboot mode i can successfully run
fastboot flash recovery_ramdisk recovery_ramdisk.img (i can also flash old recoveries this way, but none of them will successfully boot into recovery mode)
fastboot flash system system.img
either way, the system will not boot afterwards.
how do I manually flash bootloader / kernel on the oreo partition layout?
erecovery and hisuite won't recover my phone either...
Any hints appreciated
Aibiman
Click to expand...
Click to collapse
can you in to TWRP?
I was on nougat on my L21_hw_eu before i tried to upgrade manualy to oreo. i tried the twrp and terminal method and my phone started upgading. It failed at 72% saying "update verification failed". I lost my stock rom and bricked my phone.
Then i manualy flashed different Update.app images and was able to unbrick my phone .
I tried lineage OS and stock oreo.
Problems are:
1: I cant factory reset my phone using stock recovery it fails at 24%
2: FingerPrint Sensor won't work except for gestures (in Stock oreo. works in LineageOs)
3: Themes dont work
4: Flash light don't work
4: CAMERA is not responding. in both roms
in lineageOs everything works perfectly except Camera.
Please provide me details for what am i doing wrong..
iu.khan53 said:
I was on nougat on my L21_hw_eu before i tried to upgrade manualy to oreo. i tried the twrp and terminal method and my phone started upgading. It failed at 72% saying "update verification failed". I lost my stock rom and bricked my phone.
Then i manualy flashed different Update.app images and was able to unbrick my phone .
I tried lineage OS and stock oreo.
Problems are:
1: I cant factory reset my phone using stock recovery it fails at 24%
2: FingerPrint Sensor won't work except for gestures (in Stock oreo. works in LineageOs)
3: Themes dont work
4: Flash light don't work
4: CAMERA is not responding. in both roms
in lineageOs everything works perfectly except Camera.
Please provide me details for what am i doing wrong..
Click to expand...
Click to collapse
If you only have extracted images flashed from update.app, then you do not have the full rom installed.
You should run either hurupdater of HWOTA again to get full emui8 installed.
mrmazak said:
If you only have extracted images flashed from update.app, then you do not have the full rom installed.
You should run either hurupdater of HWOTA again to get full emui8 installed.
Click to expand...
Click to collapse
I suspected that too...
Now my TWRP hangs at initial screen. i m using p20lite.img twrp
other TWRP works but they dont have adb enabled
is there a way i could flash through fastboot?
iu.khan53 said:
I suspected that too...
Now my TWRP hangs at initial screen. i m using p20lite.img twrp
other TWRP works but they dont have adb enabled
is there a way i could flash through fastboot?
Click to expand...
Click to collapse
no,
dont adb though.
mrmazak said:
no,
dont adb though.
Click to expand...
Click to collapse
HuRUpdater keeps loading on initial screen and
HWota Fails after installing no check recovery.
screenshot attached..
iu.khan53 said:
HuRUpdater keeps loading on initial screen and
HWota Fails after installing no check recovery.
screenshot attached..
Click to expand...
Click to collapse
Is that v3.1 . I pulled that version because of error 2 messages.
Check the guide and download again. File name should be. ...
NVM, I just put the download link here.
https://www.androidfilehost.com/?fid=746163614322268008
mrmazak said:
Is that v3.1 . I pulled that version because of error 2 messages.
Check the guide and download again. File name should be. ...
NVM, I just put the download link here.
https://www.androidfilehost.com/?fid=746163614322268008
Click to expand...
Click to collapse
Hwota was successful with the newer version but after rebooting update failed at 0%
iu.khan53 said:
Hwota was successful with the newer version but after rebooting update failed at 0%
Click to expand...
Click to collapse
Please screenshot the twrp screen before reboot.
mrmazak said:
Please screenshot the twrp screen before reboot.
Click to expand...
Click to collapse
i flashed different images from UPDATE.APP manually through fastboot and twrp.. I was succesfull and fingerprint was working but camera was still not working so i stupidity flashed DTS.IMG, ODM.img, and ERECOVERY_KERNEL.img through twrp and when i rebooted. there was completely black screen and nothing was working. fastboot only recognizes device and i m able to send commands . i wanted to flash other dts,odm and ERECOVERY_KERNEL.img through fastboot but it says "remote command not allowed". there is absolutely no life in phone. i think it is hard bricked. is there a way to get device back?? or else i m completely F****D.
iu.khan53 said:
i flashed different images from UPDATE.APP manually through fastboot and twrp.. I was succesfull and fingerprint was working but camera was still not working so i stupidity flashed DTS.IMG, ODM.img, and ERECOVERY_KERNEL.img through twrp and when i rebooted. there was completely black screen and nothing was working. fastboot only recognizes device and i m able to send commands . i wanted to flash other dts,odm and ERECOVERY_KERNEL.img through fastboot but it says "remote command not allowed". there is absolutely no life in phone. i think it is hard bricked. is there a way to get device back?? or else i m completely F****D.
Click to expand...
Click to collapse
You are well past anything I. Have dealt with.
mrmazak said:
You are well past anything I. Have dealt with.
Click to expand...
Click to collapse
well i will try to repair it with sigma device. I heard it can flash anything on to device through fastboot. I will try that otherwise i have to give it to huawei service centre and pray they accept to repair it.
iu.khan53 said:
well i will try to repair it with sigma device. I heard it can flash anything on to device through fastboot. I will try that otherwise i have to give it to huawei service centre and pray they accept to repair it.
Click to expand...
Click to collapse
can not explain it, but I have seen that camra not working problem, and the blank black screenfixed by flashing the vendor partiton. The bad part about that is, i do not think it flashes with fastboot.
mrmazak said:
can not explain it, but I have seen that camra not working problem, and the blank black screenfixed by flashing the vendor partiton. The bad part about that is, i do not think it flashes with fastboot.
Click to expand...
Click to collapse
i took the phone to local repair shop they flashed naugat on it and were unsuccesfull(naugat cant be flashed on oreo) but i am again at fastboot with situation similar to this thread.
https://forum.xda-developers.com/mate-9/help/please-help-bootloop-error-func-14-1-t3724685
iu.khan53 said:
i took the phone to local repair shop they flashed naugat on it and were unsuccesfull(naugat cant be flashed on oreo) but i am again at fastboot with situation similar to this thread.
https://forum.xda-developers.com/mate-9/help/please-help-bootloop-error-func-14-1-t3724685
Click to expand...
Click to collapse
As far as I know (which is not that far). You need three images to be correct for recovery to load on oreo based device.
1. recovery_ramdisk.img
2. kernel.img
3. recovery_vbmeta
try to flash those in fastboot first. and see if they complete without error.
then if they do flash, try to boot into recovery. (try with stock first-- can try TWRP after if this works)
mrmazak said:
As far as I know (which is not that far). You need three images to be correct for recovery to load on oreo based device.
1. recovery_ramdisk.img
2. kernel.img
3. recovery_vbmeta
try to flash those in fastboot first. and see if they complete without error.
then if they do flash, try to boot into recovery. (try with stock first-- can try TWRP after if this works)
Click to expand...
Click to collapse
i cant flash ramdisk images. ithink i m on naugat now because i am able to flash succesfully recovery.img and boot.img in recovery and boot partitions. but cant flash ramdisk and kernel.
and what is iom3 image. error do i need to flash something for that?
and also hifi image error when upgrading through dload method
iu.khan53 said:
i cant flash ramdisk images. ithink i m on naugat now because i am able to flash succesfully recovery.img and boot.img in recovery and boot partitions. but cant flash ramdisk and kernel.
and what is iom3 image. error do i need to flash something for that?
and also hifi image error when upgrading through dload method
Click to expand...
Click to collapse
oh, well let me get together some nougat suggestions
mrmazak said:
oh, well let me get together some nougat suggestions
Click to expand...
Click to collapse
i have sent phone to the service center. waiting for their response now. They told me if they were unable to repair the phone then i will get a new one. lets hope for the best.
iu.khan53 said:
i have sent phone to the service center. waiting for their response now. They told me if they were unable to repair the phone then i will get a new one. lets hope for the best.
Click to expand...
Click to collapse
That sounds good
mrmazak said:
That sounds good
Click to expand...
Click to collapse
Received call today they were unable to repair it. They said they will get me a new one as soon as new stock arrives.
mrmazak said:
That sounds good
Click to expand...
Click to collapse
Recieved new phone today. Works like a charm. but again stuck on naugat. i will wait for official upgrade this time
Edit:
Got upgrade to oreo today. Love the new UI.
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
try to flash stock boot.img and recovery.img
sonn3 said:
try to flash stock boot.img and recovery.img
Click to expand...
Click to collapse
Same issue. So how would we go about flashing properly?
Search for recovery.img and boot.img in stock rom and flash in fastboot mode.
mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
Did you select close avb 2.0 in twrp and factory reset?
mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
We would need further details on which device (region) which MIUI version (number, android, region) you were on when you attempted to install Magisk. Of course we assume here you had unlocked your bootloader first, otherwise any attempt to flash anything will result in bootloop.
Many have successfully rooted on Android 9 regardless of MIUI version.
Complication often comes with Chineses devices from what I read, Global not so much so if you are on Global device consider yourself lucky
Easiest root is probably to flash LR team TWRP If you can still access fastboot mode (voloume - + power) version 09.24 or 11.04 if you are on Android 9 or version 12.10 if you are on Android 10. Note that you probably have more chances of success being on Android 9.
And use the root feature from WITHIN that TWRP to install root on your device.
You have a complete guide of the steps to reproduce here:
Guide
I have tested on Android 9, EEA device, EEA rom MIUI 11.0.2.0 and it works without an issue if you follow the guide provided above.
If you still want to manually flash Magisk from any other recovery, make sure to use version 19.04 which seems to have the higher odds of success (update afterward from Manager).
Also as mentioned by @wang1chung do not forget to close avb 2.0.
Myself I also had RM Force encrypt option used (just in case) even if not mentionned in the thread.
But unlike what was suggested in those threads I did not wipe data.
That said since I do not want to have TWRP to stick for now, I actually want it to automatically be replaced by stock recovery all went fine for me, and Magisk is there.
And when I need TWRP for something I just flash it again and do my stuff.
Hope this helps.
Good luck!
Same problem here. Luckly fastboot was still working (vol down + power after Redmi logo gets off). Then, I've downloaded stock ROM, and tryied manually execute fastboot commands, without success. Then, I've found a .bat file inside the root folder of the stock ROM .tar.gz archive, then executed the .bat file. Phone is working back. So, whats the catch about install Magisk? Any tips?
allxdadev said:
Same problem here. Luckly fastboot was still working (vol down + power after Redmi logo gets off). Then, I've downloaded stock ROM, and tryied manually execute fastboot commands, without success. Then, I've found a .bat file inside the root folder of the stock ROM .tar.gz archive, then executed the .bat file. Phone is working back. So, whats the catch about install Magisk? Any tips?
Click to expand...
Click to collapse
Personally I used the hassle-free method pressing the button to root directly from within the LR-TWRP (09.24, or 11.04 on Android 9 MIUI), swiped, then pressed that other provided button to close AVB 2.0, swiped and it worked on first attempt.
Of course TWRP got replaced on first reboot by system recovery, but I dont care as I do not want it to stick on my device. I just flash it again when I need it.
Magisk stayed, updated it from Manager (well manager updated first to that new ugly theme.... yurk!), then Magisk updated, no problem.
Note that I am on EU Phone running EEA MIUI 11.0.2.0. You might get a different outcome with other devices/roms.
Side note, LR-TWRP 09.24 installs Magisk 19.04 which has been reported numerous time to work on most Android 9 MIUI regional versions. LR-TWRP 11.04 howevers installs Magisk 20.0 fyi.
Hope this helps,
Regards,
regarding the thread title, i had the same problem. right when i was about to retart everything all over from 0, i was glad i was able to just go into twrp and just unroot. rebooted and it started as if nothing hsppended. now i jjust gotta find which module made me bootloop.
try this n give us the result