Hi,
I unlocked my Note 8 Pro, flashing twrp-3.7.0_9-0-begonia.img with Fastboot successfully , but by reboot no twrp-startscreen/menu starts. Instead on loop of Redmi-Logo with unlocked-Symbol for 5 seconds, than reboot. several keykombinations (volume-Up+OnOff-key) does not start twrp... what is wrong? (I tried several older twrp-versions.)
I read https://forum.xda-developers.com/t/guide-info-psa-redmi-note-8-pro-megathread-cfw.4056527 and used follwing commands:
fastboot flash preloader preloader_begonia.bin
fastboot flash lk lk.img
fastboot flash lk2 lk.img
now my phone is absolutely bricked. only blacksreen. fastboot does not start, fastboot-command does not find any device.
edu.mc said:
I read https://forum.xda-developers.com/t/guide-info-psa-redmi-note-8-pro-megathread-cfw.4056527 and used follwing commands:
fastboot flash preloader preloader_begonia.bin
fastboot flash lk lk.img
fastboot flash lk2 lk.img
now my phone is absolutely bricked. only blacksreen. fastboot does not start, fastboot-command does not find any device.
Click to expand...
Click to collapse
It brick because you did something stupid. Follow this to recover your phone:
edu.mc said:
Hi,
I unlocked my Note 8 Pro, flashing twrp-3.7.0_9-0-begonia.img with Fastboot successfully , but by reboot no twrp-startscreen/menu starts. Instead on loop of Redmi-Logo with unlocked-Symbol for 5 seconds, than reboot. several keykombinations (volume-Up+OnOff-key) does not start twrp... what is wrong? (I tried several older twrp-versions.)
Click to expand...
Click to collapse
And _9 is Android 9. So you need to downgrade to Miui Android 9 to use that "Official" one. Or use unofficial twrp for Miui 12.0.x or Miui 12.5.x
-
Related
So,recently i switched from cm14.1 back to cm13 and when i did that, i forgot to downgrade the bootloader,so after i flashed the rom I went to the bootloader and made the downgrade,Successfully booted into cm13,but when i tried going to recovery to flash xposed,i found out there's bootloop ( stuck on asus logo ) ! Everytime i try to boot into bootloader or recovery! nothing works!
Saumitraa said:
So,recently i switched from cm14.1 back to cm13 and when i did that, i forgot to downgrade the bootloader,so after i flashed the rom I went to the bootloader and made the downgrade,Successfully booted into cm13,but when i tried going to recovery to flash xposed,i found out there's bootloop ( stuck on asus logo ) ! Everytime i try to boot into bootloader or recovery! nothing works!
Click to expand...
Click to collapse
if no boot loader you have to use unbrick threads.
If you had a flashed back a stock recovery and boot.img if on rooted mm bl with giovix modder tool , you could've downgraded via sd card and stock recovery ..in my link below
There were 2 different cm 13s , one with mm bl and one based on 5.
.
Unbricked
So i unbricked the phone! Everything was success! xfstk worked then i got the 4 color screen and after that the bootloader!
Extracted the .raw file and then flashed using commands, but when the phone tries to reboot, it gets stuck on the ASUS logo! waited half an hour for that! Service center people say that its a motherboard problem! Any advice ?
Saumitraa said:
So i unbricked the phone! Everything was success! xfstk worked then i got the 4 color screen and after that the bootloader!
Extracted the .raw file and then flashed using commands, but when the phone tries to reboot, it gets stuck on the ASUS logo! waited half an hour for that! Service center people say that its a motherboard problem! Any advice ?
Click to expand...
Click to collapse
did you get any error in any command. if you got bootloader it must work
flash xfstk again and and run these commands after extracting raw.. tell me if any of the command fails or give error
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot
No errors
I flashed everything again, no errors whatsoever! The phone just wont boot! Stuck on Asus logo for an hour , then switched off the phone
Saumitraa said:
I flashed everything again, no errors whatsoever! The phone just wont boot! Stuck on Asus logo for an hour , then switched off the phone
Click to expand...
Click to collapse
Which build number raw file you use ?
Saumitraa said:
I flashed everything again, no errors whatsoever! The phone just wont boot! Stuck on Asus logo for an hour , then switched off the phone
Click to expand...
Click to collapse
send me log of cmd when you run commands
timbernot said:
Which build number raw file you use ?
Click to expand...
Click to collapse
This one : WW_ZE551ML_2.20.40.194_20160713
Hi
I was trying to install Lineage OS on my device, but I failed, now the phone does not have TWRP anymore, and when I power up, it goes into fast boot only.
I have done quite a lot of work to save my phone, and the last thing that I did was download the stock fastboot rom and run flash_all.bat from it.
(I can not get the Miflash tool working on my PC because when I startup the program, it asks me to download 5 drivers, but it failed to download and throw me an error)
luckyvictor said:
Hi
I was trying to install Lineage OS on my device, but I failed, now the phone does not have TWRP anymore, and when I power up, it goes into fast boot only.
I have done quite a lot of work to save my phone, and the last thing that I did was download the stock fastboot rom and run flash_all.bat from it.
(I can not get the Miflash tool working on my PC because when I startup the program, it asks me to download 5 drivers, but it failed to download and throw me an error)
Click to expand...
Click to collapse
First of all - if your phone boots to fastboot, there seems to be a problem with your bootloader or kernel.
To fix that, you need to reflash aboot.img and boot.img via fastboot.
Boot.img depends on the version, you want to install. Copy both files into your fastboot folder and
Code:
fastboot flash boot_a boot.img
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash aboot_a aboot.img
Code:
fastboot flash aboot_b aboot.img
Now your phone shouldn´t stuck @ fastboot anymore.
Ok, to save your data, you could try to boot twrp:
Code:
fastboot boot twrp.img
If you´re lucky, it can decrypt your data - then you can backup data and internal storage...
If it´s not able to decrypt, you need to install twrp.
To install a fastboot rom without miflash look here
I suggest you to install caf-kernel via twrp. Sometimes your phone boots up with it - magic
Voodoojonny said:
First of all - if your phone boots to fastboot, there seems to be a problem with your bootloader or kernel.
To fix that, you need to reflash aboot.img and boot.img via fastboot.
Boot.img depends on the version, you want to install. Copy both files into your fastboot folder and
Code:
fastboot flash boot_a boot.img
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash aboot_a aboot.img
Code:
fastboot flash aboot_b aboot.img
Now your phone shouldn´t stuck @ fastboot anymore.
Ok, to save your data, you could try to boot twrp:
Code:
fastboot boot twrp.img
If you´re lucky, it can decrypt your data - then you can backup data and internal storage...
If it´s not able to decrypt, you need to install twrp.
To install a fastboot rom without miflash look here
I suggest you to install caf-kernel via twrp. Sometimes your phone boots up with it - magic
Click to expand...
Click to collapse
Thanks, will give it a try.
Just for my knowledge, what are these boot_a and boot_b please? they relate to the two sim slot in this device?
luckyvictor said:
Thanks, will give it a try.
Just for my knowledge, what are these boot_a and boot_b please? they relate to the two sim slot in this device?
Click to expand...
Click to collapse
Boot.img from fastboot rom... To be flashed in partition boot_a and boot_b. Our device is a AB-device. That means all partitions are doubled (except of data). If your system breaks, you can switch to the other slot by "fastboot set_active a" or b if you are on a.... Btw perhaps that fixes your phone too! Boot twrp and you can see which slot is active (under reboot)
Hi everyone,
I bought a Motorola G6 play model XT1922-3 type 374B and wanted root acces on this device.
So I started by succesfully unlocking my bootloader using the following tutorial.
After this a started tried to root the device using this tutorial.
This tutorial doesn't link to boot images anymore so I was able to find the moto-g6-play-jeter-patched-twrp.img somewhere else.
I did the following things:
- reboot to bootloader [Succesfull]
- fastboot boot moto-g6-play-jeter-patched-twrp.img [Unsuccesfull]
The device did boot the twrp image but I was unable to interact with it in any way. I couldn't swipe or press buttons.
I made a short video to show this.
I wanted to retry the whole thing so I did reboot to bootloader but then I accidently entered the following command:
fastboot flash boot moto-g6-play-jeter-patched-twrp.img picture of command prompt
After this I wasn't able to normally boot my device. When I try to do so the screen goes black and says n/a in the left corner.
Please does anyone know how I could either be able to boot my normal stock rom again or to have a rooted rom?
Kind regards Sven Onderbeke
Hi Sven,
This isn't going to be the most advanced reply, as I'm not very experienced with this stuff either, but it seems you have accidentally flashed your twrp image to 'boot', wherever that is, which is why the phone isn't able to boot to system.
Can you still boot into bootloader and recovery (twrp)?
If so, then I'd suggest using fastboot to flash a sock or custom ROM. I'm not sure exactly which one though, you have basically the same model as me and that seems to use the JETER ROMS a list of which are over here (can't post links yet, so you will just have to search on mirrors . lolnet . com /firmware/moto/jeter/official/ or remove the spaces
I seem to have somehow lost the partitions on mine, but will start a new thread question about that.
Sven Onderbeke said:
Hi everyone,
I bought a Motorola G6 play model XT1922-3 type 374B and wanted root acces on this device.
So I started by succesfully unlocking my bootloader using the following tutorial.
After this a started tried to root the device using this tutorial.
This tutorial doesn't link to boot images anymore so I was able to find the moto-g6-play-jeter-patched-twrp.img somewhere else.
I did the following things:
- reboot to bootloader [Succesfull]
- fastboot boot moto-g6-play-jeter-patched-twrp.img [Unsuccesfull]
The device did boot the twrp image but I was unable to interact with it in any way. I couldn't swipe or press buttons.
I made a short video to show this.
I wanted to retry the whole thing so I did reboot to bootloader but then I accidently entered the following command:
fastboot flash boot moto-g6-play-jeter-patched-twrp.imgpicture of command prompt
After this I wasn't able to normally boot my device. When I try to do so the screen goes black and says n/a in the left corner.
Please does anyone know how I could either be able to boot my normal stock rom again or to have a rooted rom?
Kind regards Sven Onderbeke
Click to expand...
Click to collapse
Just flash a stock boot.img to boot. Then just flash TWRP to recovery. In TWRP, format data. Type yes. Then reboot recovery. Then Use TWRP to flash magisk. Done.
Hi again Sven,
I just wanted to let you know that I just downloaded the following RETAIL ROM
ALJETER_RETAIL_9.0_PPPS29.55-35-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
and used the following fastboot commands, one at a time.
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
Which rebooted into bootloader so pressed "start" and all booted fine now. It looks like we have the same device, so hopefully that will work for you too.
Hello, my first post on RN8PRO Section, but I am on this forum since I bought this device five months ago. Rough times!
But now we have some custom ROMs, and I want to test some on this beast. Bootloader already unlocked. Now I have some files here (linux):
- twrp.img (AgentFabulous)
- lk.img
- preload.img
- vendor.img (begonian, 871MB)
What I need to be sure, is the correct order of flashing everything. Do I:
Code:
fastboot flash recovery twrp.img
fastboot flash preloader preloader_begonia.bin
fastboot flash lk lk.img
fastboot flash lk2 lk.img
fastboot flash vendor vendor.img
fastboot reboot
Press volume UP + power until Recovery, then flash ROM???
Is this all? Am I forgetting something?
P.S: SP Flash Tools and Global Stock Android 9 ROM already download, just in case
Thanks in advance
Preloader should be the first just in case and then lk, and to enter to fastboot or recovery vol up + pwr, and then choose one
Hi, I was on 11.0.11 and after flashing 11.0.12 from TWRP
miui_GINKGOGlobal_V11.0.12.0.PCOMIXM_912960e1fc_9.0.zip
I can't flash TWRP
twrp-3.4.0-1-ginkgo.img
in fastboot mode even though there isn't an error
Code:
fastboot flash recovery twrp-3.4.0-1-ginkgo.img
Sending 'recovery' (65536 KB) OKAY [ 1.564s]
Writing 'recovery' OKAY [ 0.277s]
Finished. Total time: 1.868s
if I try to boot into recovery TWRP isn't there, it's on stock recovery. My bootloader is unlocked if it isn't obvious.
If I do
fastboot reboot recovery
after flashing TWRP, it doesn't boot into TWRP but instead into normal phone mode, not recovery.
If I do
fastboot reboot recovery
after flashing TWRP and then keep pressing the recovery key combo (PWR+VOLUP) it doesn't boot any recovery, it just keeps rebooting
-
Hacker?pcs said:
Hi, I was on 11.0.11 and after flashing 11.0.12 from TWRP
miui_GINKGOGlobal_V11.0.12.0.PCOMIXM_912960e1fc_9.0.zip
I can't flash TWRP
twrp-3.4.0-1-ginkgo.img
in fastboot mode even though there isn't an error
Code:
fastboot flash recovery twrp-3.4.0-1-ginkgo.img
Sending 'recovery' (65536 KB) OKAY [ 1.564s]
Writing 'recovery' OKAY [ 0.277s]
Finished. Total time: 1.868s
if I try to boot into recovery TWRP isn't there, it's on stock recovery. My bootloader is unlocked if it isn't obvious.
If I do
fastboot reboot recovery
after flashing TWRP, it doesn't boot into TWRP but instead into normal phone mode, not recovery.
If I do
fastboot reboot recovery
after flashing TWRP and then keep pressing the recovery key combo (PWR+VOLUP) it doesn't boot any recovery, it just keeps rebooting
Click to expand...
Click to collapse
Download twrp fastboot mode.
Download TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150-fastboot.zip - Redmi Note 8
Download TWRP TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150-fastboot.zip - Redmi Note 8 - in MiFirm ✅ - Xiaomi MIUI Firmware - ROM - TWRP download free and max speed - The biggest Xiaomi Mi download
mifirm.net
J. Harry Potter said:
Download twrp fastboot mode.
Download TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150-fastboot.zip - Redmi Note 8
Download TWRP TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150-fastboot.zip - Redmi Note 8 - in MiFirm ✅ - Xiaomi MIUI Firmware - ROM - TWRP download free and max speed - The biggest Xiaomi Mi download
mifirm.net
Click to expand...
Click to collapse
Doesn't work,
fastboot boot recovery-TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150.img
bring me to a different screen, the one that says "Redmi by Xiaomi" instead of the one with the little thing with the communist hat tinkering with Android but it's fastboot again, no TWRP.
Flashing it to recovery is the same as the official, rebooting to normal phone mode and if I do adb reboot recovery it gets me to stock recovery, not TWRP
Hacker?pcs said:
Doesn't work,
fastboot boot recovery-TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150.img
bring me to a different screen, the one that says "Redmi by Xiaomi" instead of the one with the little thing with the communist hat tinkering with Android but it's fastboot again, no TWRP.
Flashing it to recovery is the same as the official, rebooting to normal phone mode and if I do adb reboot recovery it gets me to stock recovery, not TWRP
Click to expand...
Click to collapse
Then ig.......try after reseting your device or clean flash latest miui with mi flash tool.(your bootloader needs to be unlocked)
Hacker?pcs said:
Doesn't work,
fastboot boot recovery-TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150.img
bring me to a different screen, the one that says "Redmi by Xiaomi" instead of the one with the little thing with the communist hat tinkering with Android but it's fastboot again, no TWRP.
Flashing it to recovery is the same as the official, rebooting to normal phone mode and if I do adb reboot recovery it gets me to stock recovery, not TWRP
Click to expand...
Click to collapse
By the way this is a different method. this should have worked. what did you do ?
J. Harry Potter said:
Then ig.......try after reseting your device or clean flash latest miui with mi flash tool.(your bootloader needs to be unlocked)
Click to expand...
Click to collapse
My bootloader is unlocked, I'm with Magisk since I bought the device, I usually to update download the recovery rom
Miui Updates
Redmi Note 8 Global Stable V11.0.12.0 OTA Apply for V11.0.11.0 https://bigota.d.miui.com/V11.0.12.0.PCOMIXM/miui-blockota-ginkgo_global-V11.0.11.0.PCOMIXM-V11.0.12.0.PCOMIXM-a0ac2f3c57-9.0.zip Recovery ROM...
t.me
and flash it then flash Magisk then TWRP to recovery, sometimes I forget though TWRP and then flash it from fastboot. I forgot it now but now it doesn't flash via fastboot for some reason
J. Harry Potter said:
By the way this is a different method. this should have worked. what did you do ?
Click to expand...
Click to collapse
As I've said, it acts like the official TWRP, it either reboots to fastboot or to normal phone mode.
Hacker?pcs said:
My bootloader is unlocked, I'm with Magisk since I bough the device, I usually to update download the recovery rom
Miui Updates
Redmi Note 8 Global Stable V11.0.12.0 OTA Apply for V11.0.11.0 https://bigota.d.miui.com/V11.0.12.0.PCOMIXM/miui-blockota-ginkgo_global-V11.0.11.0.PCOMIXM-V11.0.12.0.PCOMIXM-a0ac2f3c57-9.0.zip Recovery ROM...
t.me
and flash it then flash Magisk then TWRP to recovery, sometimes I forget though TWRP and then flash it from fastboot. I forgot it now but now it doesn't flash via fastboot for some reason
As I've said, it acts like the official TWRP, it either reboots to fastboot or to normal phone mode.
Click to expand...
Click to collapse
i don't know how you flashed that twrp. Just open EN_Recovery-twrp-oneclick-EN then press enter. and then boot your phone to fastboot mode and connect to pc. then in pc type 2 and then i hope it will work
J. Harry Potter said:
i don't know how you flashed that twrp. Just open EN_Recovery-twrp-oneclick-EN then press enter. and then boot your phone to fastboot mode and connect to pc. then in pc type 2 and then i hope it will work
Click to expand...
Click to collapse
I've flashed it with the fastboot I have from Android SDK, didn't run the script. I've checked it out and saw that it flashes the misc.bin file too, I've tried flashing it but now I'm stuck on fastboot... ffs
I've downloaded the official Fastboot rom
ginkgo_global_images_V11.0.12.0.PCOMIXM_20201119.0000.00_9.0_global_37804edbcb.tgz
but I can't flash its misc.bin, it says Volume full...
fastboot continue
says "system has been destroyed"
I really don't want to wipe data and start fresh with Mi Flash tool ffs
Hacker?pcs said:
I've flashed it with the fastboot I have from Android SDK, didn't run the script. I've checked it out and saw that it flashes the misc.bin file too, I've tried flashing it but now I'm stuck on fastboot... ffs
I've downloaded the official Fastboot rom
ginkgo_global_images_V11.0.12.0.PCOMIXM_20201119.0000.00_9.0_global_37804edbcb.tgz
but I can't flash its misc.bin, it says Volume full...
never heard of volume full problem. place the fastboot rom in desktop menu. and install necessary drivers that need to flash via mi flash tool
Click to expand...
Click to collapse
J. Harry Potter said:
never heard of volume full problem. place the fastboot rom in desktop menu. and install necessary drivers that need to flash via mi flash tool
Click to expand...
Click to collapse
Well the misc.bin from your link is 8KB, the misc.img from fastboot rom tgz is 8MB
It sucks because mi flash tool erases data...
EDIT
THANK GOD,
fastboot erase misc
fixes the destroyed problem and lets me boot.
I figured it out from the bat script in the tgz fastboot rom, it doesn't flash the contained 4MB misc.img, it just has "fastboot %* erase misc" near the end
Problem that I can't flash TWRP again so I can't root :/
Hacker?pcs said:
Well the misc.bin from your link is 8KB, the misc.img from fastboot rom tgz is 8MB
It sucks because mi flash tool erases data...
EDIT
THANK GOD,
fastboot erase misc
fixes the destroyed problem and lets me boot.
I figured it out from the bat script in the tgz fastboot rom, it doesn't flash it, it just has "fastboot %* erase misc" near the end
Problem that I can't flash TWRP again so I can't root :/
Click to expand...
Click to collapse
so now you can boot.
if you have a pc just store your data in pc and then flash miui. then ig it will clear all the bugs u r facing and then you can try to flash twrp
J. Harry Potter said:
so now you can boot.
if you have a pc just store your data in pc and then flash miui. then ig it will clear all the bugs u r facing and then you can try to flash twrp
Click to expand...
Click to collapse
Yeah seems to the only way, something blocks the custom TWRP recovery and a clean slate may be the only way
Hacker?pcs said:
Yeah seems to the only way, something blocks the custom TWRP recovery and a clean slate may be the only way
Click to expand...
Click to collapse
don't forget to flash VBMETA after so the custom recovery (twrp or orangefox) persist