Blankflash available in the attachments.
1. Connect your hard bricked phone
2. Wait till the white LED turns on
3. Run blank-flash.bat (on Windows) or blank-flash.sh (on Linux, Mac and other *NIX OS)
4. Wait for the process to finish
5. Install new firmware from here
u r the best!!!!!
This is total nonsense. There is no explanation about what this "blank flash" does and from the script you can guess that only the yellow pre-boot warning gets replaced by another picture. I previously asked what this tool exactly does and there was no reply!
Completely dubious/untrustworthy behaviour.
Crossposting:
[ROM][UNOFFICIAL][10] Lineage 17.1 for Motorola One [DISCONTINUED]
/* * Your warranty is... still valid? * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features...
forum.xda-developers.com
seven.seas said:
This is total nonsense. There is no explanation about what this "blank flash" does and from the script you can guess that only the yellow pre-boot warning gets replaced by another picture. I previously asked what this tool exactly does and there was no reply!
Completely dubious/untrustworthy behaviour.
Crossposting:
[ROM][UNOFFICIAL][10] Lineage 17.1 for Motorola One [DISCONTINUED]
/* * Your warranty is... still valid? * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for pointing this out. My One 5G Ace is stuck in a bootloop. I can only boot into fastboot and I was going to dig into this option posted here a bit to see if it could help.
fosgate3 said:
Thanks for pointing this out. My One 5G Ace is stuck in a bootloop. I can only boot into fastboot and I was going to dig into this option posted here a bit to see if it could help.
Click to expand...
Click to collapse
Yes I think using this blank flash would not help you. There even is no description what it should do.
Hella late reply. Blank flash is when you hard bricked your device, when the device doesn't turn on anymore and only the white LED at the top is blinking.
This shouldn't be flashed if you can still turn on your device.
Need some help. I got a hard bricked motorola one macro that is not responding to any buttons pressed, it is not recognized as USB com port although all needed drivers are installed.
So I tried this instruction. While plugged in, the white LED is permanently on. Starting blank-flash.bat opens cmd window with the message < waiting for device >. Pressing any button and combinations doesn't do anything.
I tried another instruction from this XDA article. Running blank-flash.bat gives the same result. It is always the same: < waiting for device >...
Does somebody has any suggestions what to do?
MacroMarco said:
Need some help. I got a hard bricked motorola one macro that is not responding to any buttons pressed, it is not recognized as USB com port although all needed drivers are installed.
So I tried this instruction. While plugged in, the white LED is permanently on. Starting blank-flash.bat opens cmd window with the message < waiting for device >. Pressing any button and combinations doesn't do anything.
I tried another instruction from this XDA article. Running blank-flash.bat gives the same result. It is always the same: < waiting for device >...
Does somebody has any suggestions what to do?
Click to expand...
Click to collapse
in the video explains the Blank Flash
Related
I went stock DI01 by Odin, and tried re-rooting by Superoneclick 1.7, but it doesn't respond at "Waiting for device". it freezes.
I tried the other way from terminal, and it keeps on saying that the device isn't connected.
******************************************************************************
* *
* Dirrk's EZ Root v0.2 (Sebastien Krahmers Exploit) *
* *
******************************************************************************
*
* Testing if your device is connected
*
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
*
* If you are NOT connected please follow these directions
* Install the correct drivers
* Turn On Debugging
* Check usb port, cable and phone
* Then rerun this application
*
Press any key to continue . . .
*
* Pushing the files to your phone
* rage.bin, busybox, Superuser.apk, su, com.sh
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
* Restarting your phone to ensure the exploit will work
* When your phone comes back on please unlock it if it is locked and then
* wait
error: device not found
I can access the SD card, but rooters are not working when I turn on usb debugging.
I have Samsung driver installed, android sdk installed, and tried turning on and off while connected to computer. still no root.
how can I get it working?
With the number of pre-rooted roms we have why even root? After odin restore boot but don't sign in and power down. Pull battery/Flash CWM_recovery.tar/ insert battery 3 finger salute to recovery flash desired (rooted) rom. Depending upon what package you used you might have to flash a current modem in odin. Continue to restore set up.
good day.
One Click doesn't work anymore. I did this yesterday, after going back to stock and doing an OTA update, works wonderfully and it's really easy, very low possibility of bricking your phone and having to go through the hassle of fixing that. Go to this thread and follow along. http://forum.xda-developers.com/showthread.php?t=913470 I recommend using the Clockwork Packages from here though they are the most recent and everything seems to be fixed on them. http://forum.xda-developers.com/showthread.php?t=1017817 Easiest way I have ever seen to root a phone.
Hello people! The truth did not know where to put this but if it's wrong because there is no problem and relocated!
I have a x900 LeTV I bought several months ago! Two weeks ago you installed a beta version of android 6.0.1. and I was working fine few days and one night, suddenly he went out and caught no more! Hard has a brick because no load, does not light, does not enter or fasboot recovey mode, any PC with any version of Windows recognizes it and have been for days following guidelines to resuscitate through QPST.2.7.429.msi without but although follow the steps one by one PC with Windows 7 simply does not recognize me! I am in despair and can not think of anything else! Some genius of the community could help me? There is a guide for x800 that is very similar to x900, yet still do not achieve much !!!
Same
Same issue, did u manage to fix it?
Hello dear all,
after a long time of rush*around different solutions I finally figure it out how to hard brick Indian le max x900
(note hard brick means ur phone is completely dead no charging,no restart, *no fastboot etc....becoz of may be wrong rom flashing)
1. Install qualcom driver and latest qpst 2.7*(link:*https://androiddatahost.com/np4wq)(qualcomm driver present in qfil file for x800 link in step4)
2. Installed qpst*will be present at c:/program files(x86)/qualcomm/qpst/bin....inside it find qfil flashing*application...open it
3. connect ur dead indian le max to computer and see if qualcomm usb driver can detect it(u may notice qfil flashing appln will also show some com no connected)....if u r unsuccessful just press both volume key/or power key and both vol key at a time for around 1 min when phone is connected to pc.*(in any case u failed no big issue try to install it manually by searching in google, well I have used win10 and it simply worked for me)
4. Download the qfil file for x800 and extract it somewhere, it also have qualcomm driver inside it so once extracted install that driver too (link:*https://mega.nz/#!G0ozxZwb!vowHBNjQGC1AtVOx2ThrWpYt6yHEnAACFvq90XDF4n0)....actually i tried qfil for x900,x1, line brush tutorials etc but none of those worked for me and x800 aks le 1 pro have the same processor so it can make x900 alive....sahara error all the time...*( a big thx to*UNBRICK X800 X900*Started by*mxmax)
5. if all done correctly u can see ur dead indian lemax*phone connected to qualcomm mode with some com no, that u can notice in qfil flashing appln.
6.in the flashing appln select Flat Build,
* * * * * * * * * * * * * * * * * * * * *in browse select ur extracted qfil x800 folder (path\qfil x800\x1_na_dvt1_fastboot\prog_emmc_firehose_8994_lite.mbn,
* * * * * * * * * * * * * * * * * * * * *in load xml select rawprogram_unsparse (present inside folder x1_na_dvt1_fastboot)....after that patch0 that automatically comes,
* * * * * * * * * * * * * * * * * * * * than finally click on download....u can see process started and once completed exit it.
7. So now ur phone have qfil of x800 flashed, try to boot it by pressing power button for 1 min.....u can see blue led blinked and ur phone start to boot (if not means ur phone's battery is very less simply connect it with charger by pressing power button u can see phone starts to show orange led flashing after some time....ie it start charging)
8. once it start in step 7 the phone show chinese letv logo...but it doesn't boot becoz it is for x800 not x900....phone simply tries to boot again and again...so once the phone start to reboot by itself simply press power button and vol down key at a time....u can see small penguin that means ur phone is in fastboot mode.
9. its time now to install twrp 3.0 to ur x900 connected to pc in fastboot mode(link:*https://www.androidfilehost.com/?fid=24533103863139522)...simply install twrp from link extract it open the twrp installer appln ....and install it by pressing backspace key that u find during instrution)....great thing about twrp recovery is it can charge ur phone too while connected to power source.
10.So after step 9 ur phone should be in twrp 3.0 recovery mode....u can see internal storage of it shows in pc of around 10 gb not 52 gb.....so inside twrp\wipe\format data...type yes, and advanced wipe select all and wipe......once done u have 52 gb avail in internal storage that u can see in ur pc too.
11. put indian version any rom inside ur internal storage and flash it...once done ur phone will successfully rebooted links for roms are below...simply download any as per ur choice
* * * * *https://drive.google.com/file/d/0B6m-wM0vYiL8U0U4cUhUM2NlMGc/view*(this is stock 12s rom)
* * * **https://www.androidfilehost.com/?fid=24533103863139959* (this is also stable 12s rom made bu cuoco with extra settings and dolby presinstalled)
* * * **http://evolutionletvx900.blogspot.in/* *(this will give u link for 12s and 13s rom which have nova and google launcher preinstalled)
* * flash any rom and if any any file after flashed make big vibrate ur phone with blue led on...don't panic...simply press power button for long time it will reboot ur phone
A big thx to memerbers of leeco.re for proving international support for leeco becoz it had gone from India, and I request u to make support for Indian x900 also since we cant able to install eui 5.8 based roms....tried to install several roms by deleting lines for check in update-script...even though it installed make it brick/dea again...so plz help for android 6*
Hi, I'm a x900 user
I have the same issue than some of you guys, my phone is detected in Qualcomm mode in QFIL, I have to charge the phone like an hour or two, I can tell its chargin because It has the blue led on, when it has no charge the led is blinking red and after sometime it becomes blue.
Put the phone in Qualcomm mode, download finish succesfully, pressed Vol Up + Power, my phone starts but with blue led and black screen, although its detected as a hard drive (LeTV), it'srecognized as an adb device (serial number ----- recovery). I ran the command "x1_na_fastboot" in command prompt inside folder CEXCNFN590......zip., I got rebooting in fast mode device, but it stops in "awaiting devices".
Thats were I'm stuck. Got any ideas?
2 Rahulraj2012
Thanks bro it is work exactly as you say !!! X900 Unbriked for now ;-)
When the phone is in fastboot mode I connect it to pc then the fastboot mode is turning the phone to on and by that I can't abhle to do the further commands
Nithish_rana said:
When the phone is in fastboot mode I connect it to pc then the fastboot mode is turning the phone to on and by that I can't abhle to do the further commands
Click to expand...
Click to collapse
What model is it?
Can you enable adb debugging?
Realme 3 pro
Nithish_rana said:
Realme 3 pro
Click to expand...
Click to collapse
Have you looked at this thread?
[Guide][How-to] Unlock Bootloader, Install TWRP, GSI and Magisk
DISCLAIMER * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. * YOU are choosing to make these modifications, and if * you point the finger at me for messing up...
forum.xda-developers.com
or the other threads in
Realme 3 Pro Guides, News, & Discussion
Use this forum to find the best how-to guides for the Realme 3 Pro and discover the latest news. General discussion also goes here.
forum.xda-developers.com
Hi!
I tried to update my Mi Pad 4 Wifi to latest twrp 3.5.2.9 but I ended with a half-brick...
I cannot access TWRP anymore (no way to access it with power+volume up). Power menu (I am using arrowos) or adb reboot recovery, they just show me a brief twrp loader image than goes black and I need to power cycle.
Worse even, I can launch fastboot, fastboot devices responds but I cannot boot/flash, or whatever from fastboot.
I suspect I had somehow hosed some boot/persistent or other device partition.
I tried to reboot to EDL but it's not responding ...
System is working but I fell I am in an unsafe position....
Any clue on how to restore fastboot twrp funcionality or I lost my Mi Pad?
not sure if your issue but I needed to goto to fastbook devices, fastboot flash default boot.img. I couldn't get TWRP to work natively as boot - I needed to use Fastboot boot boot.img to temporarily boot into TWRP. This was over a year ago however so definitely not 3.5.2.9
p.s. somehow I managed to get 3.3.1 working - this is what is on my MiPad currently
p.p.s. if your fastboot comes onscreen but jumping straight to black screen with "press any key to shutdown" as soon as you plug in the USB then try this. I needed to
[Guide] Fix "press any key to shutdown" when unlock bootloader or run fastboot cmd
[Guide] Fix "press any key to shutdown" when unlock bootloader or run fastboot cmd For some Windows 10 users (like me), it seems impossible to unlock the bootloader of their Xiaomi devices. Because every time they run MiFlashUnlock and connect...
forum.xda-developers.com
I've also now just installed this. I flashed from TWRP and it worked
[RECOVERY][UNOFFICIAL] Pitch Black Recovery Project [v3.x.x][2021/03/30]
/* *Disclaimer * * Your warranty is now void. * * We're not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features...
forum.xda-developers.com
Last message - promise. Seems that it worked for me initially because I used 3.3.1.
Long-standing and known issues with later versions and suggested fix here >
PSA - The Latest TWRP Release (3.5.0_9-0) is Bugged
Already opened an issue on GitHub but looks like the dev got a long backlog. If anyone has a fix I'd really appreciate it. I experienced the following when updating TWRP to 3.5.0_90: - long loading time: takes ~20s to finish initialization -...
forum.xda-developers.com
Hi,
After a "misswipe"in TWRP I ended up deleting part of my partition table.
Then, I removed TWRP in an attempt to fix it by flashing the stock ROM and this relocked my bootloader for some reason : fastboot flashing unlock just fails. I'm trying to shut down my device to access the COM port right now and use SP Flash Tool, but I can't power if off...
Any ideas on either how to access the COM port or how to unlock the bootloader and restore the original partition table ?
(I'm using SP Flash Tool v5.21 and the MediaTek VCOM Drivers)
In still using phone boot image corrupt and locked bootloader sitting with dead phone and laughing
[STOCK][FULL-ROM] OxygenOS_11.3_A.20 EU DN2103 | Unbrick guide
/* * Your warranty is... still valid! * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. * Please do some research yourself before asking or use anything on this...
forum.xda-developers.com
Read all This Thread I done you can also