yo guys, i have a little trouble with twrp, it is flashing in slot b and dont boot, or flashing in slot a and dont boot the system, tried 3 other twrp & ofox, maybe you'll know whats wrong?
sewerfract said:
yo guys, i have a little trouble with twrp, it is flashing in slot b and dont boot, or flashing in slot a and dont boot the system, tried 3 other twrp & ofox, maybe you'll know whats wrong?
Click to expand...
Click to collapse
Last version
https://dl.akr-developers.com/?dir=skkk/TWRP/A12/v6.0_A12
Installation
Phone in fastboot mode
Cmd:
fastboot boot twrp.img
Power shell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
NOSS8 said:
fastboot boot twrp.img
Click to expand...
Click to collapse
if fastboot boot would work i would not writing here
sewerfract said:
if fastboot boot would work i would not writing here
Click to expand...
Click to collapse
You have not specified it.
So you have installed a TWRP with fastboot and now the Fastboot mode no longer works?
And specify what phone you have.
NOSS8 said:
You have not specified it.
So you have installed a TWRP with fastboot and now the Fastboot mode no longer works?
And specify what phone you have.
Click to expand...
Click to collapse
fastboot still working, no problems with it. twrp just didnt flash with fastboot boot twrp.img, i can send vids how it looks.
poco f3 alioth global
sewerfract said:
fastboot still working, no problems with it. twrp just didnt flash with fastboot boot twrp.img, i can send vids how it looks.
poco f3 alioth global
Click to expand...
Click to collapse
With this one?
https://dl.akr-developers.com/?file=skkk/TWRP/A12/v6.0_A12/[BOOT]3.6.2_12-RedmiK40-POCOF3-Mi11X_v6.0_A12-alioth-skkk_b3647986.zip
NOSS8 said:
With this one?
https://dl.akr-developers.com/?file=skkk/TWRP/A12/v6.0_A12/[BOOT]3.6.2_12-RedmiK40-POCOF3-Mi11X_v6.0_A12-alioth-skkk_b3647986.zip
Click to expand...
Click to collapse
yeah, that first twrp i ever tried to flash
sewerfract said:
yeah, that first twrp i ever tried to flash
Click to expand...
Click to collapse
the bootloader is unlocked?
If so post a screenshot of the fastboot command.
NOSS8 said:
the bootloader is unlocked?
If so post a screenshot of the fastboot command.
Click to expand...
Click to collapse
of course unlocked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sewerfract said:
yo guys, i have a little trouble with twrp, it is flashing in slot b and dont boot, or flashing in slot a and dont boot the system, tried 3 other twrp & ofox, maybe you'll know whats wrong?
Click to expand...
Click to collapse
You need to provide full details of what you are doing. Are you flashing a ROM? Did you format the data partition after flashing the ROM? etc. etc.
sewerfract said:
of course unlocked.
Click to expand...
Click to collapse
try with power shell
DarthJabba9 said:
You need to provide full details of what you are doing. Are you flashing a ROM? Did you format the data partition after flashing the ROM? etc. etc.
Click to expand...
Click to collapse
Okay. I flash stock fastboot miui 13.0.5, next i want flash a twrp with "fastboot boot twrp.img" command, but as i wrote above, it didn't flash, my phone just turned off and after turning it on it start miui, "fastboot reboot recovery" command sent me in stock miui recovery. Today I tried flash twrp with "fastboot flash boot_a twrp.img" command, it flashed, but after i do this system stop booting, worked only twrp and fastboot mode. I also tried "fastboot flash boot_b" command but like "fastboot boot" it didn't flash twrp
Download Platform tool
command is
NOSS8 said:
Download Platform tool
command is
View attachment 5728813
Click to expand...
Click to collapse
i try it tomorrow, thanks
sewerfract said:
Okay. I flash stock fastboot miui 13.0.5, next i want flash a twrp with "fastboot boot twrp.img" command, but as i wrote above, it didn't flash, my phone just turned off and after turning it on it start miui, "fastboot reboot recovery" command sent me in stock miui recovery. Today I tried flash twrp with "fastboot flash boot_a twrp.img" command, it flashed, but after i do this system stop booting, worked only twrp and fastboot mode. I also tried "fastboot flash boot_b" command but like "fastboot boot" it didn't flash twrp
Click to expand...
Click to collapse
Try this:
Code:
fastboot devices
fastboot flash boot twrp.img
fastboot reboot recovery
sewerfract said:
i try it tomorrow, thanks
Click to expand...
Click to collapse
You are using ADB.exe instead of Fastboot.exe.
NOSS8 said:
You are using ADB.exe instead of Fastboot.exe.
Click to expand...
Click to collapse
always using it
sewerfract said:
always using it
Click to expand...
Click to collapse
It is a Fastboot command,that s all.
Related
Hello, how can i boot in recovery without hardware buttons they are broken? and another thing i dont have any rom instaled, the phone i s-off with 4ext touch recovery. please help. THX:crying:
turn on the phone (u should just get stuck at white htc splash screen) then plug in to pc and open command window and type
adb devices
if ur device shows up then type
adb reboot recovery
it doesn¨t work when i turn on the phone i get to fastboot or hboot...?
capone5 said:
it doesn¨t work when i turn on the phone i get to fastboot or hboot...?
Click to expand...
Click to collapse
oh rite, thats a balls. Dont think theres any other way. Try taking the phone apart and cleaning the buttons. ul be surprised at the dust there. Hopefully that will work. If it dont then the only other way is to flash an ruu via bootloader. What does ur phone say in bootloader?
capone5 said:
it doesn¨t work when i turn on the phone i get to fastboot or hboot...?
Click to expand...
Click to collapse
Did you try running the adb commands that jmcclue listed above while in hboot?
Maybe try running fastboot commands such as "fastboot devices" to see if its recognized.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try "fastboot devices"
capone5 said:
http://img40.imageshack.us/img40/3765/desireintrouble.jpg[/IMG ]i have install adb and when start the process i cant find device as you can see from the picture...i get in fastboot and hboot menu but i cant navigate any futher, is there a way to flash rom threw windows beyond recovery? because i do a full wipe and i dont have any rom instaled on my precious desire :(...[/QUOTE]
Hi Capone5,
One way to do it, is by downloading a recovery img ([url]http://forum.xda-developers.com/showthread.php?t=1791371[/url] or [url]http://forum.xda-developers.com/showthread.php?t=1474327[/url]) unzip and put it in the fasboot folder, plug phone in fastboot mode and type 'fastboot boot [filename].img'
Hope this helps
Click to expand...
Click to collapse
here are the pictures...when i turn on the phone it immediately go on this screen http://img708.imageshack.us/img708/9121/img20130602212615.jpg and when i try fastboot devices in cmd
capone5 said:
here are the pictures...when i turn on the phone it immediately go on this screen http://img708.imageshack.us/img708/9121/img20130602212615.jpg and when i try fastboot devices in cmd
Click to expand...
Click to collapse
You dont do "adb fastboot devices". You do "fastboot devices"
adb only works when phone is booted or stuck at boot animation, thats why i said try turning on phone then try adb while it bootloops r stuck at splash screen but his phone boots straight into bootloader. Also there is no command for fastboot to reboot recovery. Personally i would take phone apart and clean buttons, worth a shot.
@ op what boes it say in ur bootloader ?
jmcclue said:
adb only works when phone is booted or stuck at boot animation, thats why i said try turning on phone then try adb while it bootloops r stuck at splash screen but his phone boots straight into bootloader. Also there is no command for fastboot to reboot recovery. Personally i would take phone apart and clean buttons, worth a shot.
@ op what boes it say in ur bootloader ?
Click to expand...
Click to collapse
Would fastboot work without selecting it in hboot? If fastboot is able to detect the phone, then he can use "fastboot boot recovery.img" to boot into a touch based recovery like 4ext (without actually flashing it).
Heres his bootloader:
this i get when just trying fastboot devices
jmcclue said:
adb only works when phone is booted or stuck at boot animation, thats why i said try turning on phone then try adb while it bootloops r stuck at splash screen but his phone boots straight into bootloader. Also there is no command for fastboot to reboot recovery. Personally i would take phone apart and clean buttons, worth a shot.
@ op what boes it say in ur bootloader ?
Click to expand...
Click to collapse
the buttons of volume are broken and i try everything to just press - and nothing hapened...how can i load a new recovery threw fastboot?
Check your android-sdk/platform-tools/ directory to make sure the fastboot.exe is there.
If its not there, redownload the sdk and setup adb/fastboot using this guide. Also make sure you install these fastboot drivers
Then try "fastboot devices" again and hope that the phone shows up. If it does you can boot a recovery by doing this:
-Download the 4ext recovery img from here
-Extract the zip and put the recovery img in your android-sdk/platform-tools/ directory
-Run "fastboot boot recovery.img"
If its not showing up in fastboot im not really sure that you have any options, other than to do what jmcclue suggested.
capone5 said:
this i get when just trying fastboot devices
Click to expand...
Click to collapse
have u got the fastboot drivers installed on ur computer?
follow this guide to install them. u cant use fastboot unless u do.
ADB & Fastboot
chromium96 said:
Check your android-sdk/platform-tools/ directory to make sure the fastboot.exe is there.
If its not there, redownload the sdk and setup adb/fastboot using this guide. Also make sure you install these fastboot drivers
Then try "fastboot devices" again and hope that the phone shows up. If it does you can boot a recovery by doing this:
-Download the 4ext recovery img from here
-Extract the zip and put the recovery img in your android-sdk/platform-tools/ directory
-Run "fastboot boot recovery.img"
If its not showing up in fastboot im not really sure that you have any options, other than to do what jmcclue suggested.
Click to expand...
Click to collapse
i just put recovery.img in android sdk/tools folder then ran the command fastboot boot recovery.img
and guess what? im in recovery. Nice 1 chromium, it works
heres a pic
jmcclue said:
i just put recovery.img in android sdk/tools folder then ran the command fastboot boot recovery.img
and guess what? im in recovery. Nice 1 chromium, it works
Click to expand...
Click to collapse
Yep it works. Im trying to compile TWRP for the desire, so i use that command to temporarily test it rather than actually flashing it.
chromium96 said:
Yep it works. Im trying to compile TWRP for the desire, so i use that command to temporarily test it rather than actually flashing it.
Click to expand...
Click to collapse
its handy to know coz im pretty sure hardly anyone knows that and i bet u cant find it on the old interweb lol
Hi all !
TWRP Recovery 2.8.6.0 for MATE7twrp 2.8.7.0 for 4.4 https://basketbuild.com/devs/asyan4ik/hwmt7_l09_4.4[/SIZE]
screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Install
connect phone to pc (enable usb debugging ) , unpack archive and run Flash_twrp_recovery.bat
Testing now.
UPDATE:
Backup and restore works. Mine is black/yellow.
yep don't work with lollicrap beta rom... damm, no TWRP, no CWM... no root...
tozneno said:
yep don't work with lollicrap beta rom... damm, no TWRP, no CWM... no root...
Click to expand...
Click to collapse
if you want I'll describe the way how to get to the root on 5.1 ...
i compile cwm \ twrp recovery for 5.1 . work - no gui
acbka said:
if you want I'll describe the way how to get to the root on 5.1 ...
i compile cwm \ twrp recovery for 5.1 . work - no gui
Click to expand...
Click to collapse
ahhhh why not, i could take a look. because i've just need a custom recovery for install super su zip. once it's down i come back to stock recovery for keeping OTA ok with the root.
acbka said:
if you want I'll describe the way how to get to the root on 5.1 ...
i compile cwm \ twrp recovery for 5.1 . work - no gui
Click to expand...
Click to collapse
for what version ? mt7-tl10 ?? i want cwm or twrp .. can you help ?
tozneno said:
ahhhh why not, i could take a look. because i've just need a custom recovery for install super su zip. once it's down i come back to stock recovery for keeping OTA ok with the root.
Click to expand...
Click to collapse
try it :
1. Download and unpack this archive https://yadi.sk/d/ByBdaMIshJuxF
2. Run from unpacked folder terminal
3. Write terminal
Code:
adb reboot bootloader
fastboot flash recovery nogui.img
fastboot reboot
after loading
important after command adb reboot recovery - the screen will be black
Code:
adb reboot recovery
adb push UPDATE-SuperSU-v2.46.zip /su.zip
adb shell /sbin/recovery --update_package=/su.zip
back to stock recovery
Code:
adb reboot bootloader
fastboot flash recovery recovery_lollipop.img
View attachment 3366008
Works on tl10 and tl9?
Sent from my HUAWEI MT7-TL10 using Tapatalk
paulopais said:
Works on tl10 and tl9?
Sent from my HUAWEI MT7-TL10 using Tapatalk
Click to expand...
Click to collapse
I think it's working on tl10 , try
Can i save my stock recovery ?
Sent from my HUAWEI MT7-TL10 using Tapatalk
acbka said:
I think it's working on tl10 , try
Click to expand...
Click to collapse
Does it work on tl09 also?
acbka said:
try it :
1. Download and unpack this archive https://yadi.sk/d/vij50mf9hHzyW
2. Run from unpacked folder terminal
3. Write terminal
Code:
adb reboot bootloader
fastboot flash recovery nogui.img
fastboot reboot
after loading
important after command adb reboot recovery - the screen will be black
Code:
adb reboot recovery
adb push UPDATE-SuperSU-v2.46.zip /su.zip
adb shell /sbin/recovery --update_package=/su.zip
back to stock recovery
Code:
adb reboot bootloader
fastboot flash recovery recovery_lollipop.img
View attachment 3366008
Click to expand...
Click to collapse
thx you so mutch :good: i've dld it for now but i'll get a try after work, i'll keep in touch for feedback.
Thanks... every time more people is coming here to bring great news about development...
---------- Post added at 08:08 AM ---------- Previous post was at 07:55 AM ----------
Ok.... I was able to flash this recovery using flashify... I download your package and extract the recovery image and works... HAM7 lt_09 stock 137sp04 rooted Rom and locked bootloader...
@acbka
it's very funny because i could flash your no gui recovery, it seems to work because a could going under it with push vol up + power (the adb commande ligne for it don't work...) but after that all other adb commande don't work, the commande return "device not found"...
fastboot flash recovery nogui.img give me a error
FAILED -(remote: command not allowed)
http://i.imgur.com/9FOny1O.jpg - why say phone unlocked ?
anyone ?
I have Cwm recovery.... And KangVip Rom... Can i flash with flashify the twrp image? Or have to flash first stock recovery and after twrp image?
paulopais said:
fastboot flash recovery nogui.img give me a error
FAILED -(remote: command not allowed)
http://i.imgur.com/9FOny1O.jpg - why say phone unlocked ?
anyone ?
Click to expand...
Click to collapse
On my HAM 7 says unlock... but is not true.. when I rooted it shows as unlock and if you type
Fastboot oem get-bootinfo it says unlocked but not able to flash nothing... I did a test reflashing a stock firmware whitout root and typing the command and show as locked...
djzero86 said:
On my HAM 7 says unlock... but is not true.. when I rooted it shows as unlock and if you type
Fastboot oem get-bootinfo it says unlocked but not able to flash nothing... I did a test reflashing a stock firmware whitout root and typing the command and show as locked...
Click to expand...
Click to collapse
Unlock bootloader , can be done with 5.1 ?
I have made full backup without problems.
Sent from my HUAWEI MT7-TL10 using Tapatalk
paulopais said:
Unlock bootloader , can be done with 5.1 ?
I have made full backup without problems.
Sent from my HUAWEI MT7-TL10 using Tapatalk
Click to expand...
Click to collapse
Really I can't tell you since I am on 137 Rom .. and locked bootloader:crying:
acbka said:
try it :
1. Download and unpack this archive https://yadi.sk/d/vij50mf9hHzyW
2. Run from unpacked folder terminal
3. Write terminal
Code:
adb reboot bootloader
fastboot flash recovery nogui.img
fastboot reboot
after loading
important after command adb reboot recovery - the screen will be black
Code:
adb reboot recovery
adb push UPDATE-SuperSU-v2.46.zip /su.zip
adb shell /sbin/recovery --update_package=/su.zip
back to stock recovery
Code:
adb reboot bootloader
fastboot flash recovery recovery_lollipop.img
View attachment 3366008
Click to expand...
Click to collapse
Thanks Sir, finally got my MT7 TL-10 rooted
Good day,
sorry for going direct to the point but, i'm having trouble with my ze551ml, as it was not yet available in my country a few months back, i bought it online, and it seems the original firmware was CN, and it was just converted to WW before it was shipped to me, as i bought it via CC, i didn't return it to the online store. now the problem is that, i want to update the software but it always fails, even if i did manual update.
Device info:
-device is rooted(it was rooted already when i got it
Build number:
LRX21V.WW-ASUS_Z00A-2.13.40.13_20150401_8390_user
044030427_201501060109
0010000500001
Kernel Version:
[email protected] #1
Wed Apr 1 00:31:25 CST 2015
Baseband Version
1509_5.0.18.00_0320,1509_7.0.10.0_0320
CPU-Z
also wondering, this was supposed to be a 64 bit phone right? but in the cpu-z it says
Processor: Intel(R) Atom(TM) CPU Z3560 1.83GHz
Cores: 4
Architecture: x86
CPUID: 6.5a.0
Codename: Moorfield
Process: 22 nm
P.S: is it possible to update if i flash the latest firmware?
BTW: Are these info safe to share?? Thanks
Yeah it's OK to share, you fail to update in recovery right? but you get the ota notification right? To me it looks like your build version is too old and it fails to update since newer updates require newer recoveries. Does ADB sideload fails too?
sorry can't understand much
ota doesn't see new updates, haven't tried adb, current computer has no android sdk installed, hopefully answered everything? but will install it now, also will finish latest stock rom in a minute
BTW: i'm willing to lose all data just to fix this problem
dwynez03 said:
ota doesn't see new updates, haven't tried adb, current computer has no android sdk installed, hopefully answered everything? but will install it now, also will finish latest stock rom in a minute
BTW: i'm willing to lose all data just to fix this problem
Click to expand...
Click to collapse
You have to try with adb, go in the recovery and you should see the adb sideload option, press it and connect to the PC, now download this http://forum.xda-developers.com/zen...l-windroid-universal-android-toolkit-t3206907 and go to command section and the sideload file. Now choose the lastest update available on asus site http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.168-user.zip (here is a direct link), now your update should start it will take a long time so don't unplug the usb!!
ElmirBuljubasic said:
You have to try with adb, go in the recovery and you should see the adb sideload option, press it and connect to the PC, now download this http://forum.xda-developers.com/zen...l-windroid-universal-android-toolkit-t3206907 and go to command section and the sideload file. Now choose the lastest update available on asus site http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.168-user.zip (here is a direct link), now your update should start it will take a long time so don't unplug the usb!!
Click to expand...
Click to collapse
ok, will try this, i'll get back to you, thanks
dwynez03 said:
ok, will try this, i'll get back to you, thanks
Click to expand...
Click to collapse
help, always rebooting into fastboot mode, how do i disable this? it won't enter twrp/recovery...
dwynez03 said:
help, always rebooting into fastboot mode, how do i disable this? it won't enter twrp/recovery...
Click to expand...
Click to collapse
You can't boot the system? Or the phone reboots in fastboot and you cant enter in recovery?
ElmirBuljubasic said:
You can't boot the system? Or the phone reboots in fastboot and you cant enter in recovery?
Click to expand...
Click to collapse
the phone reboots into fastboot and can't enter recovery, i tried reboot to recovery option in fastboot but it just boots again to fastboot..
dwynez03 said:
the phone reboots into fastboot and can't enter recovery, i tried reboot to recovery option in fastboot but it just boots again to fastboot..
Click to expand...
Click to collapse
You softbricked it, but that's OK, can you follow this guide please http://www.asus-zenfone.com/2015/12/how-to-re-lock-bootloader-asus-zenfone-2.html and after point 18 use the file you downloaded from asus site
ElmirBuljubasic said:
You softbricked it, but that's OK, can you follow this guide please http://www.asus-zenfone.com/2015/12/how-to-re-lock-bootloader-asus-zenfone-2.html and after point 18 use the file you downloaded from asus site
Click to expand...
Click to collapse
btw, when i try normal boot it boots properly into the system, i can use it normally, is that still softbricked? thanks
when i try to reboot to recovery it always returns to this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
when i select recovery mode it reboots the the same fastboot mode image,
this doesn't show up
dwynez03 said:
btw, when i try normal boot it boots properly into the system, i can use it normally, is that still softbricked? thanks
Click to expand...
Click to collapse
Ahh then it's not, some people can't boot in the system and only in the fastboot, i want you to flash a recovery and let's see if works, http://www.mediafire.com/folder/setyy42t2cymy#3puweqngpjspc download all this files and put them in your adb folder(if you have any if not download this folder(https://drive.google.com/file/d/0B8Zi6Xs3FmZlSkl5NUFFNmZxOE0/view?usp=sharing i know it's for root but it will do just fine)) and after you have booted in bootloader type this commands
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
1 at time and then try to go into recovery
ElmirBuljubasic said:
Ahh then it's not, some people can't boot in the system and only in the fastboot, i want you to flash a recovery and let's see if works, http://www.mediafire.com/folder/setyy42t2cymy#3puweqngpjspc download all this files and put them in your adb folder(if you have any if not download this folder(https://drive.google.com/file/d/0B8Zi6Xs3FmZlSkl5NUFFNmZxOE0/view?usp=sharing i know it's for root but it will do just fine)) and after you have booted in bootloader type this commands
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
1 at time and then try to go into recovery
Click to expand...
Click to collapse
i think it got bricked, now all it shows up is usb symbol....
dwynez03 said:
i think it got bricked, now all it shows up is usb symbol....
Click to expand...
Click to collapse
That error is a bi***, follow this to fix all your problems http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
haha, ok, it's not bricked, just jumped to conclusion., here's what happened, i can boot normally, but when i try to boot into fasboot or recovery it shows up the usb symbol....
dwynez03 said:
haha, ok, it's not bricked, just jumped to conclusion., here's what happened, i can boot normally, but when i try to boot into fasboot or recovery it shows up the usb symbol....
Click to expand...
Click to collapse
Here is what i think, the guy who sold your phone have put the wrong recovery in your phone, by flashing the files i give you(in my good will i thought the recovery was the same as firmware version) you bricked the bootloader, to fix this you must perform the guide i give you (http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256), so i suggest you to do is backup all your internal storage to PC, backup everything you might need and do that operation when you have time, then you can update OTA
ElmirBuljubasic said:
Ahh then it's not, some people can't boot in the system and only in the fastboot, i want you to flash a recovery and let's see if works, http://www.mediafire.com/folder/setyy42t2cymy#3puweqngpjspc download all this files and put them in your adb folder(if you have any if not download this folder(https://drive.google.com/file/d/0B8Zi6Xs3FmZlSkl5NUFFNmZxOE0/view?usp=sharing i know it's for root but it will do just fine)) and after you have booted in bootloader type this commands
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
1 at time and then try to go into recovery
Click to expand...
Click to collapse
hmmm, i think i made a mistake here, i entered this commands in fastboot mode...
ElmirBuljubasic said:
Here is what i think, the guy who sold your phone have put the wrong recovery in your phone, by flashing the files i give you(in my good will i thought the recovery was the same as firmware version) you bricked the bootloader, to fix this you must perform the guide i give you (http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256), so i suggest you to do is backup all your internal storage to PC, backup everything you might need and do that operation when you have time, then you can update OTA
Click to expand...
Click to collapse
thanks, will try again tomorrow, i'm ready if it means losing all data... thanks again,, i'll update you tomorrow or later, when i get back online.
dwynez03 said:
thanks, will try again tomorrow, i'm ready if it means losing all data... thanks again,, i'll update you tomorrow or later, when i get back online.
Click to expand...
Click to collapse
Sure! This is part of everyone experience when modding the phone
dwynez03 said:
thanks, will try again tomorrow, i'm ready if it means losing all data... thanks again,, i'll update you tomorrow or later, when i get back online.
Click to expand...
Click to collapse
hi, followed this one, and now, i can't seem to boot normally now, haha, i think it is softbricked now, but everytimer i try to flash any image, it's alwast flash failed..
PS C:\adb> fastboot --set-active b
C:\adb\fastboot.exe: unknown option -- set-active
That's the error I'm getting in fastboot. Any ideas?
localceleb said:
PS C:\adb> fastboot --set-active b
C:\adb\fastboot.exe: unknown option -- set-active
That's the error I'm getting in fastboot. Any ideas?
Click to expand...
Click to collapse
Try...fastboot --set-active=b
Badger50 said:
Try...fastboot --set-active=b
Click to expand...
Click to collapse
Same result.
localceleb said:
Same result.
Click to expand...
Click to collapse
Have you updated your platform-tools, tried a different cable, and you are in fastboot mode?
Badger50 said:
Try...fastboot --set-active=b
Click to expand...
Click to collapse
Badger50 said:
Have you updated your platform-tools, tried a different cable, and you are in fastboot mode?
Click to expand...
Click to collapse
Yes to all of those.
So, phone was fine this morning. Booted to twrp to make a backup so i could play with something different. Made the backup and rebooted, but it wouldn't boot the OS. It kept kicking me back to twrp, but twrp wouldnt fully load. Froze on the splash screen. So I rebooted to bootloader and tried to fastboot boot twrp and the same thing was happening with the splash screen. So went back to bootloader to try and swtch slots and here we are now. I've tried different cables and know that i'm up to date.
localceleb said:
Yes to all of those.
So, phone was fine this morning. Booted to twrp to make a backup so i could play with something different. Made the backup and rebooted, but it wouldn't boot the OS. It kept kicking me back to twrp, but twrp wouldnt fully load. Froze on the splash screen. So I rebooted to bootloader and tried to fastboot boot twrp and the same thing was happening with the splash screen. So went back to bootloader to try and swtch slots and here we are now. I've tried different cables and know that i'm up to date.
Click to expand...
Click to collapse
That doesn't sound good. You may have to fastboot the factory image again without the -w to get back up and running.
Badger50 said:
That doesn't sound good. You may have to fastboot the factory image again without the -w to get back up and running.
Click to expand...
Click to collapse
That was my thought, but wanted to avoid that if possible. I'm not sure why the slot command isnt working.
localceleb said:
That was my thought, but wanted to avoid that if possible. I'm not sure why the slot command isnt working.
Click to expand...
Click to collapse
Couldn't tell you my friend as to the why it happened. Dang ghosts in the machine!
What about fastboot --set-active=_b ?
rickysidhu_ said:
What about fastboot --set-active=_b ?
Click to expand...
Click to collapse
same result
localceleb said:
Any ideas?
Click to expand...
Click to collapse
fastboot set_active b, according to an OG pixel thread that I found.
You probably don't have the lastest platform tools. I had a similar problem cuz I was using platform tools from like 2 years ago. Do "fastboot --version" without quotes to see what version you're running. I'm using 28.0.1 without problems.
If you need, download the latest from here and see if that helps.
I suggest you try using Deuce's script...
He designed it so it flashes all the images on BOTH the A and B slots; it might set you back right to the correct slots. Also, he gives the option of not wiping your data (iteration of -w or not)
Good luck and hope this helps...
amartolos said:
You probably don't have the lastest platform tools. I had a similar problem cuz I was using platform tools from like 2 years ago. Do "fastboot --version" without quotes to see what version you're running. I'm using 28.0.1 without problems.
If you need, download the latest from here and see if that helps.
Click to expand...
Click to collapse
I had the same problem, I changed the platform tools, some cmd command would work then not, worked great m10,u11 & u11+ . It was the usb drivers which was giving me the problems.
Are you using PowerShell or windows terminal. I noticed this issue using those terminals...if you are using windows 10 , then navigate to the folder and then click on the address bar and type cmd..you will be redirected to the terminal..or you can always use cd {folder path}
techydawg said:
Are you using PowerShell or windows terminal. I noticed this issue using those terminals...if you are using windows 10 , then navigate to the folder and then click on the address bar and type cmd..you will be redirected to the terminal..or you can always use cd {folder path}
Click to expand...
Click to collapse
This was my problem. Thanks!
techydawg said:
Are you using PowerShell or windows terminal. I noticed this issue using those terminals...if you are using windows 10 , then navigate to the folder and then click on the address bar and type cmd..you will be redirected to the terminal..or you can always use cd {folder path}
Click to expand...
Click to collapse
I learnt today through trying to trouble shoot bad notes on unlocking the G7 bootloader that you can type CMD in powershell then you have proper working command promt withing powershell
the benefit of this is when using commands like
Code:
fastboot flash *******.img (here is where you can drag and drop file name)
You just need to make sure after the last character in the flash syntax you leave a space before you drag and drop the file into PowerShell
Hope this makes sense
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Madaz2 said:
you can type CMD in powershell then you have proper working command promt withing powershell
Click to expand...
Click to collapse
I've been doing this for several years now. I'm pretty sure in my older posts on the 2XL forum I've mentioned it. Too bad I didn't see this thread until today
localceleb said:
PS C:\adb> fastboot --set-active b
C:\adb\fastboot.exe: unknown option -- set-active
That's the error I'm getting in fastboot. Any ideas?
Click to expand...
Click to collapse
yes Its happed with me. reason: i forgot to allow pop up of USB Debbuging authorization, then i flashed magisk boot img on fastboot mode... then stucked into recovery ... for god sake i had back up apps on my Google account... but data was deleted...
Hi everyone!
I bought a MI 9 SE for my dad, it was a Chinese version with an unlocked bootloader and global rom installed.
After trying to use Google Pay, I figured it needs a locked bootloader. So I locked it using "fastboot oem lock".
After that, the phone is bricked
I didn't have an account bound to it, so can't use the official unlock.
Can access fastboot and recovery.
Tried flashing using recovery, sideloading.
It refuses to install a chinese rom, only a global one can be installed.
Obviously, I get the "This MIUI version can't be installed on this device".
I know there's the EDL path, but that requires an authorized account
Is there any other way around this?
Is there a way to force install a chinese rom over the global rom?
I would really appreciate any help or advice. I've spent a few days reading the forums, tried a lot of utilities but with zero luck.
Did you try the original chinese ROM, the first release? The same with global?
elpaablo said:
Did you try the original chinese ROM, the first release? The same with global?
Click to expand...
Click to collapse
I have tried the last few MIUI versions, but didn't try the original release versions. That's a good point! Will try today, and get back with the results :good:
If you locked the bootloader on a non-official ROM, you could have messed the AVB (Android Verified Boot) partition.
Disabling vbmeta could be helpful.
Download vbmeta.img from https://drive.google.com/open?id=1-Np8xHPfVlJwUJLURntIklmkCyVqU5jH and place it in the same folder of your fastboot tools.
Open a cmd window (don't use Windows Power Shell) and type command
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If you get the command executed properly, then type
fastboot reboot
and pray if device will restart on old ROM, set a MiAccount and unlock bootloader again using MiFlash, then flash any Official ROM and relock bootloader, if needed.
You can also get GPay working on unlocked bootloader, using Magisk, in case.
Flounderist said:
If you locked the bootloader on a non-official ROM, you could have messed the AVB (Android Verified Boot) partition.
Disabling vbmeta could be helpful.
Download vbmeta.img from and place it in the same folder of your fastboot tools.
Open a cmd window (don't use Windows Power Shell) and type command
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If you get the command executed properly, then type
fastboot reboot
and pray if device will restart on old ROM, set a MiAccount and unlock bootloader again using MiFlash, then flash any Official ROM and relock bootloader, if needed.
You can also get GPay working on unlocked bootloader, using Magisk, in case.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It didn't work, says 'Flashing is not allowed in Lock State'
elpaablo said:
Did you try the original chinese ROM, the first release? The same with global?
Click to expand...
Click to collapse
The same error both times, seems it refuses to install older versions of MIUI
savandriy said:
The same error both times, seems it refuses to install older versions of MIUI
Click to expand...
Click to collapse
Oh, you don't use miflash tools?
savandriy said:
It didn't work, says 'Flashing is not allowed in Lock State'
Click to expand...
Click to collapse
Try with
fastboot format userdata
and
fastboot reboot
If you use telegram, join the conversation here @GrusFamily
Reboot in fastboot ans use Flashtool
Flash any ron in fastboot format from here https://mirom.ezbox.idv.tw/en/phone/grus/
With flashtool, all partition will be format and phone is like out of the box
Flounderist said:
If you use telegram, join the conversation here @GrusFamily
Click to expand...
Click to collapse
What the hell, I have a family? What's this about?
Grus said:
What the hell, I have a family? What's this about?
Click to expand...
Click to collapse
Hahaha sorry mate. It's the link of a telegram group and it matched with your nickname.
Grus is the device name for Mi 9 SE :laugh:
That's so incredibly strange. Guess I'll have to check that phone out.
Flounderist said:
Try with
fastboot format userdata
and
fastboot reboot
If you use telegram, join the conversation here @GrusFamily
Click to expand...
Click to collapse
Sadly, it just hangs forever on the "Sending 'userdata' (4400 KB)" part ...
pikouchou said:
Reboot in fastboot ans use Flashtool
Flash any ron in fastboot format from here https://mirom.ezbox.idv.tw/en/phone/grus/
With flashtool, all partition will be format and phone is like out of the box
Click to expand...
Click to collapse
Can you please link to the Flashtool or a tutorial? Do you mean XiaomiADB?
savandriy said:
Can you please link to the Flashtool or a tutorial? Do you mean XiaomiADB?
Click to expand...
Click to collapse
Here is the link:
https://www.xiaomiflash.com/download/
You need to download a fastboot ROM and to unzip it TWICE to get the flashable files.
Then launch flashtool while device is connected in fastboot mode.
Locate files using flashtool interface and try to flash it.
If you won't succeed, EDL flash is your last resort.
https://mirom.ezbox.idv.tw/en/phone/grus/roms-cn-stable/
Try the first chinese version (10.2.3).
Flounderist said:
Here is the link:
https://www.xiaomiflash.com/download/
You need to download a fastboot ROM and to unzip it TWICE to get the flashable files.
Then launch flashtool while device is connected in fastboot mode.
Locate files using flashtool interface and try to flash it.
If you won't succeed, EDL flash is your last resort.
Click to expand...
Click to collapse
It says there's a device mismatch, but this is the Chinese MIUI 10.2.3 for MI 9 SE
I guess EDL it is then
Try global too. I would try all Chinese and global versions, just to be sure. Because, you know, edl isn't free.
savandriy said:
It says there's a device mismatch, but this is the Chinese MIUI 10.2.3 for MI 9 SE
I guess EDL it is then
Click to expand...
Click to collapse
If you get device mismatch error you should:
- check if your device is actually a Mi9 SE
- check if you downloaded a fastboot ROM for Mi 9SE
- check if you are using the latest MIUI driver and MiFlash.
Probably your device had a fake-MIUI ROM installed with some messed device fingerprint, hence MiFlash does not recognize it as Grus.
If you are 100% sure your device is a Mi 9SE, and you downloaded the correct ROM (I would recommend latest China Stable), you can try editing the flash-all.bat file.
Here is a tutorial (you probably will need to translate it): https://www.miui.it/forum/index.php...lazione-delle-rom-fastboot-con-miflash.15301/
Good luck!
You can flash him only with testpoint and auth account