After I tried to root ze500kl with mod_boot.img by
-fastboot erase userdata
-fastboot erase cache
-fastboot flash boot mod_boot.img
after it reboot can't boot and stuck on bootloader screen, I can reboot and enter recovery mode and user adb and fastboot command boot boot.img (boot.img form firmware UL-ASUS_Z00E-WW-12.8.5.156-user.zip)
-fastboot boot boot.img
so it can pass bootloader and can user normally but if I restart my device it will always stuck on bootloader I must usr fastboot command to pass it again.
anyone can fix this issue for me?
Hi
i have this problem too, have you fixed it in meanwhile?
Related
Guys, i need some help. i was messing with my nexus 7. then i tried to start fresh again by re-installing the stock 4.4.4. It's been a while since i flash Stock roms. So i find this tutorial, Erase boot, erase userdata etc. then when i tried to flash the bootloader, it always fail (unknown error). So im stuck with a OS-less Nexus 7 and no recovery. I can go to Fastboot. My device is recognizable through Fastboot devices. My old Rom was 4.4.4 stock. Please help me guys
Hello @vyrus027,
flash the files inside the factory image manually with these commands, it'll do the trick:
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot format userdata
fastboot reboot
Keelah se'lai,
GethPrime
redmi 2
still have the luck?
no recovery mode, just fastboot
i have tried
- flash twrp ( restart and back to bootloop logo)
- fastboot reboot-edl ( still back to loop)
- flash with miflash
- repartition - https://forum.xda-developers.com/redmi-2/how-to/how-to-erase-partition-table-redmi-2-t3520410
- fastboot flash direct method - https://forum.xda-developers.com/redmi-2/how-to/error-resolved-t3324791
any suggest?
Thank you in advance
1.try miflash and flash rom according to your device... and look at progress (some doesnt flash just shows and finish fast) then try with another version of miflash, flash it it will take few minutes
2.if u r still in bootloop after these all ( i faced so many times dnt wrry )
then flash twrp, fastboot boot twrp...
flash any custom rom
I had the same problem, flash twrp and install a custom rom, it worked for me
Tried this method.Worked for me
1.Download the official fastboot rom from the official miui site
2.Check whether ur device is recognised or not
3.Install minimal adb and fastboot
4.Type these commands
fastboot flash system system.img
enter
fastboot flash boot boot.img
enter
fastboot flash recovery recovery.img
enter
fastboot flash cache cache.img
enter
if u want to remove all userdata then
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot reboot.done!!!
I have same issues, when I unplug the charge the phone restart with bootloop, it is on, off and on and off, i cant go to recovery mode if not i charge, i just can go to fastboot mode if I don't plugged in my charge. And I can't go to bootloader menu's
Hello,
I was playing around with the Mi A1 magisk and i was flashing it. But then i by accident pressed lock bootloader (and confirming because i did not payed attention to what it was saying) and now the phone is BRICKED :crying: Only thing i get is the connect sound when connected to PC, but the phone shows NOTHING , just black and vibrates when i hold power and any other button. (no fastboot or recovery)
I think it is done for :crying: which hurts me to say cuz i got it as gift.
I think it will be expensive to fix in service center..
PLEASE HELP IF YOU CAN AS FAST AS POSSIBLE
Thanks in advance.
Same happened to me. Did you change anything with tools? did you erase partitions? what exactly thing were you doing to brick it? only press the lock cant brickt it. Normally you can just re-unlock it and flash with the stockrom. Just give us more information about the process you were doing
Actually i booted TWRP by mohacm flashed Magisk then i powered off the phone and than it happend. When it locked i turned it on and showed the colorfull bar and Mi logo for split second and turned off every single time. After re-unlocking it was in bootloop so i tried to restore with Mi Flash tool and it showed error at the end (something wrong with partition b flash) So i tried again and it froze so i turned the tool off and it put it the state it is now.
Also the response of the phone happens only when plugged to PC
You've bricked nothing at all, just chill. I suppose you've installed all the drivers for the A1 while installing the Mi Flash if yes then install minimal adb and fastboot tool, paste all the files from the images folder from the firmware file to the directory of the minimal adb and fastboot tool, open cmdhere.exe located in minimal adb and fastboot tool folder, boot you phone into fastboot mode(press and hold volume down and power buttons at the same time till fastboot bot appears), plug the phone to the pc, enter the following commands:
- fastboot devices (You should see your device's serial tex next to fastboot text if you see nothing, install fastboot drivers properly)
- fastboot flash modem_a modem.img
- fastboot flash modem_b modem.img
- fastboot flash sbl1 sbl1.img
- fastboot flash sbl1back sbl1.img
- fastboot flash rpm rpm.img
- fastboot flash rpmbak rpm.img
- fastboot flash tz tz.img
- fastboot flash tzback tz.img
- fastboot flash devcfg devcfg.img
- fastboot flash devcfgback devcfg.img
- fastboot flash dsp adspso.bin
- fastboot flash sec sec.dat
- fastboot flash splash splash.img
- fastboot flash misc misc.img
- fastboot flash aboot emmc_appsboot.mbn
- fastboot flash abootbak emmc_appsboot.mbn
- fastboot flash boot_a boot.img
- fastboot flash boot_b boot.img
- fastboot flash system_a system.img
- fastboot flash system_b system.img
- fastboot flash lksecapp lksecapp.img
- fastboot flash lksecappbak lksecapp.img
- fastboot flash cmnlib cmnlib.img
- fastboot flash cmnlibbak cmnlib.img
- fastboot flash cmnlib64 cmnlib64.img
- fastboot flash cmnlib64bak cmnlib64.img
- fastboot flash keymaster keymaster.img
- fastboot flash keymasterbak keymaster.img
- fastboot flash userdata userdata.img
- fastboot reboot
Done!
But the problem is that i cannot boot into fastboot. The phone doesent respond to any actions. I was writing it on the top of the thread. If could boot into fastboot then i would use Mi tool again.
Also when the phone is connected to the PC and i hold the Power and volume buttons (up or down doesent matter) nothng happens just the PC does the dis and connect sounds
try hold volume and and down and then connect to pc after that hold power button volume +,- in the same time then wait 6sec . check if ur phone detect on devie manager port
The PC CAN detect the phone. The problem is not in PC but in the phone cuz it wont boot or show NOTHING on the screen whatsoever.
The PC recognizes it as Qualcomm HS-USB Diagnostics 900E (COM3)
AND you're dumb enough to not mention that. If so buy a cheap type-c cable that works on your phone, make it a deep flash cable(search on youtube how to make it) and flash the stock rom using it, that's my best bet.
dont get how someone can mess up the bootloader. i think in 10 years of my phonelife the bootloader menu never bugged.
Ok guys,
Thanks to everyone who helped my phone Is Back alive thx to Xiaomi Service center.
I happened to erase boot and recovery before unlocking bootloader, and can only enter fastboot mode now. Any solving method?
Hi all,
This is a long shot, I hope there is someone somewhere that can help with this issue. I know it's a fairly old phone now, but if anyone has any knowledge about android recovery, it would be greatly appreciated!
Version: OxygenOS 3.6.1.
Rooted via Magisk and Bootloader Unlocked years ago.
The problem was unexpected. It was suffering battery drains for the past month, and last night, whilst on charge, I noticed it restarted. And now it's stuck on the OnePlus LOGO Screen. D:
I can only access FASTBOOT and NOT RECOVERY mode.
What I've tried:
MSM RECOVERY TOOL (w/ QCOM drivers)
Installing ABD Interface Drivers to try an ADB Sideload (but can't get to recovery)
Fastboot flashing stock and TWRP recoveries (can't boot into it - error dtb not found).
Fastboot flash_Ox211.cmd *
Spoiler: * flash_Ox211.cmd does the following
Code:
rem adb reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
rem fastboot erase recovery
rem fastboot flash recovery unofficial_twrp_2.8.7.0-bacon.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash sdi sdi.mbn
fastboot flash pmic pmic.mbn
fastboot flash hyp hyp.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oem_stanvbk static_nvbk.bin
rem fastboot flash userdata userdata_64g.img
pause
rem fastboot reboot
None of the above has worked or has fixed recovery mode.
I want to keep my userdata. Is it possible to access that partition, and/or somehow do an 'adb backup'. It might be impossible without the recovery
To keep documenting my findings on extra things that I have done or will do.
Reseating the battery
I have drained the battery and taken the battery connection out the phone for an hour.
UPDATE: After re-plugging, and putting it into charge, the phone bootloops now instead of staying stuck on the OnePlus/Android LOGO continuously. NO CHARGING INDICATOR.
Replacing the battery
If it's a battery issue, then a replacement might work. I have ordered one.
UDPATE: TBD
Fastboot Flashing other recovery img's
dtb not found (or device tree blob) - was an issue when I tried booting into a flashed recovery (stock or TWRP). According to some forum posts, it may be due to flashing the wrong recovery version on the device.
UPDATE:
stock []
twrp-2.8.7.0-oneplus2 [] - no dtb error
twrp-3.0.0-1-oneplus2 []
twrp-3.0.2-1-oneplus2 []
twrp-3.2.1-0-oneplus2 []
...
↑ Doing a fastboot boot <recovery>.img bootloops the phone.
Try asking in the op2family discord server, there are some pretty knowledgeable ppl there. Also you could try asking _undead, he's the one who made lineage 19.1 for op2, see in Original Android Development on this forum.
Huh, it sounds like you're having a similar issue as me. Except I can access recovery but not fastboot... and sideloading isn't working for me.