Hello all. I`ve bricked my Tablet with the Lenovo Rescue Tool ...Now i am trying to unbrick my tablet...I managed to Use sp tool on donwload only and succeded on putting back the rom as the software said...but the tablet does not work...I`m still stuck on fastboot and does not boot in to the Android OS...What can i do next?
blue4scorpio1 said:
Hello all. I`ve bricked my Tablet with the Lenovo Rescue Tool ...Now i am trying to unbrick my tablet...I managed to Use sp tool on donwload only and succeded on putting back the rom as the software said...but the tablet does not work...I`m still stuck on fastboot and does not boot in to the Android OS...What can i do next?
Click to expand...
Click to collapse
I was also soft bricked, and couldnt boot into system, every restart goes to fastboot mode...lenovo rescue doesnt seem to be able to handle soft-bricks of this nature.
See if this fastboot command allows you to boot to system
fastboot set_active a
This assumes that you have correctly flashed all components correctly
Related
Please help, I need proffessional help.
Android Phone: ASUS Zenfone 2 Laser 5.0 (ROOTED)
Android Firmware: 5.0.2 Lollipop
Aim: To enter into Fastboot mode and Recovery Mode without problems
Situation: Recently installed TWRP Recovery in-app and through software, but when I try to enter in Fastboot Mode (HOLD POWER & VOLUMEUP) or even Recovery Mode (HOLD POWER & VOLUMEDOWN), I just end up in a hanged out ASUS Logo. I can't do anything except pulling out the battery myself and putting it back then booting the device through power button to boot it normally. I don't know if it's the problem with the model, or the phone's system itself, or it's just a bug, or a problem when I rooted my device through ADB.
(Note: When I rooted the device, I wasn't even able to see the blue "FASTBOOT MODE" when I tried it, I only saw the ASUS logo as well.)
For anyone who has any idea on what's going on with my device, please reply and help me. I really want to have the benefits of a rooted phone completly and I'm a new root user so I need assistance.
For anyone who has an idea on what I've done or on what should I do, please help me. Someone told me that I flashed the recovery and locked the bootloader, so it got damaged. If so, would Unlocking the Bootloader (from Wiki.CyanogenMod's Site) help my case?
CrimsonShade09 said:
For anyone who has an idea on what I've done or on what should I do, please help me. Someone told me that I flashed the recovery and locked the bootloader, so it got damaged. If so, would Unlocking the Bootloader (from Wiki.CyanogenMod's Site) help my case?
Click to expand...
Click to collapse
Do you can acesse to twrp recovery on your device
Same problem.....waiting for helping, please
mohamedelkholy said:
Do you can acesse to twrp recovery on your device
Click to expand...
Click to collapse
I think I have "access" to TWRP recovery. However, I can only access it through booting it up from ADB. I used the command "adb reboot bootloader" to boot it to fastboot mode, however only the ASUS screen appears but I treated it as the fastboot mode itself. Then I checked if it was really on fastboot mode through "fastboot devices" and it showed my serial number. I can only enter into TWRP using "fastboot boot twrp.img" . I don't know if I already installed it because although I opened it, I can't do it from the phone (POWER+VOLUMEDOWN)
Ok now boot twrp and then flashamodified zip or cm13 and your phone should eork you dhould to have unlockrd bootloader
Hi to all, i'd re-open this 3d for the same problem. After months I'm trying to re-sleep my ZE500KL. It was in "can't load invalid boot image" loop. I tried to force recovery mode and (wrongly) force to update from update.zip the stock fw stored in the uSD.
Since this time I can't enter in recovery mode more but fastboot only. The problem is that, in spite of the USB drivers are installed, fastboot does not recognize any connected device.
I've run Win 10 pro with a zenbook ux333fn laptop and I remembered android 6 on the phone, the last time I saw it alive.
I've tried also to install twrp 3.1, with no positive results.
Anyone can suggest me any solving way?
Thanks to all
...anybody?
Up.....
sh4d3_ said:
Hi to all, i'd re-open this 3d for the same problem. After months I'm trying to re-sleep my ZE500KL. It was in "can't load invalid boot image" loop. I tried to force recovery mode and (wrongly) force to update from update.zip the stock fw stored in the uSD.
Since this time I can't enter in recovery mode more but fastboot only. The problem is that, in spite of the USB drivers are installed, fastboot does not recognize any connected device.
I've run Win 10 pro with a zenbook ux333fn laptop and I remembered android 6 on the phone, the last time I saw it alive.
I've tried also to install twrp 3.1, with no positive results.
Anyone can suggest me any solving way?
Thanks to all
Click to expand...
Click to collapse
Up...
QFIL or AFT can be the solution.
I have a similar problem, a hard bricked Z00ED (ZE500KL) not able to get into fastboot or recovery.
after reading some thread here an there. that are Processor / Chipset specific flash tools that help flash bootloaders and repartition hard bricked device.
For mobiles with MediaTec devices, there is a tool called SP Flash Tool. I wasted a whole day with it. then understood that Z00ED (ZE500KL) has a Qualcomm Processor MSM8916
Therefore we need a Qualcomm Flasher here (QFIL )
But nos I am stuck with getting firmware for ZE500KL that can be used by QFIL tool, It should have a firehouse*.mbr file that is the programmer (dependent on CPU of the phone) and a rawprogram*.hex file that I don't know where to get from.
Thanks... It seems a bit less wild, but in any case no solving, yet
Up! ...anyone?
Up!
Hello all..
I've struggled almost a week to unbrick my yureka AO5510. I can able get into bootloader mode by using sd boot method. Also i can able to get into Qualcomm HS USB QDLOADER 9008 by shorting board pins.
But in but in bootloader mode after flash_all.bat done successfully device remains same. No boot. In 9008 mode Sahara protocol error. Couldn't flash.
Finally Here is the solution and cause..
Cause : Corrupted radio modem in bootloader (or something related to boot)
Solution:
Get into bootloader mode using this method https://www.youtube.com/watch?v=TooHuDpKyzA ...
(If you can't get into bootloader mode using this method then nothing helps, i've tried even flashing my device using JTAG boxes)
As per video instructions even after flash_all.bat done if yureka remains bricked here comes the solution.
Download flash_radio.bat(zipped) from link below. Place it in stock firmware folder and run. After everything done successfully Run fastboot -i 0x1ebf reboot
Voila.. you got your device back
This is my first thread. Forgive me if anything uncompleted.
Shiva
View attachment flash-radio.zip
Someone please revert back with results.. i've spent many hours in this.. i can really help you i believe to bring your bricked device back...
yureka hardbrick
I did use your solution and results are very good.but I have a problem Touch not working properly after locking screen. If u tell me how to format bootloader of yureka and flash a very fresh ROM in it.
himan1995 said:
I did use your solution and results are very good.but I have a problem Touch not working properly after locking screen. If u tell me how to format bootloader of yureka and flash a very fresh ROM in it.
Click to expand...
Click to collapse
You dont have to format whole eMMc bootloader. just flash the rom either using fastboot mode or custom recoveries.
xboxxtech said:
You dont have to format whole eMMc bootloader. just flash the rom either using fastboot mode or custom recoveries.
Click to expand...
Click to collapse
I flash yureka plus ROM in yureka via fastboot and causes of that when I get back to my stock.my mobile touch screen work perfectly until I lock mobile screen.
himan1995 said:
I flash yureka plus ROM in yureka via fastboot and causes of that when I get back to my stock.my mobile touch screen work perfectly until I lock mobile screen.
Click to expand...
Click to collapse
Try [Tool] [OFFICIAL] UN-brick yureka device using Annabathina tool V1.0 avilable in XDA.
xboxxtech said:
Try [Tool] [OFFICIAL] UN-brick yureka device using Annabathina tool V1.0 avilable in XDA.
Click to expand...
Click to collapse
I will try it . thanks for reply. Hope its works for me
Hey guys!
It's been a while since I've used my Mi A1. I turned it back on after a very long time and it was stuck on the android screen as if there was nothing to boot into so I tried booting into my recovery but there was nothing there either. I figured I probably formatted some stuff a while ago but I don't really remember what happened. Anyways, here's what I did next:
I could only boot into fastboot so I ran the command
Code:
fastboot boot path/to/tissot/twrp.img
but that didn't work.
So I flash the img to boot and tried rebooting to recovery but I was stuck on the android logo and again. I then again had to wait for my battery to run out before I could do anything else (I couldn't enter fastboot again. Only works when the phone is off for some reason)
I then erased the system partition using fastboot and tried booting into the recovery again but no luck. Can someone help me?
I know I messed up... big time. Someone save me
EDIT: Some more details
I tried two recoveries. The Pitch Black on XDA and also the standard "twrp-3.3.1-0-tissot.img" but had the same issue of getting stuck at the splash screen for both.
Also, I remember using Android 10 before all this happened.
EDIT 2: I ran the following commands:
Code:
fastboot set_active a
Code:
fastboot flash boot path/to/tissot/twrp.img
And I can now use the button combination to boot into recovery but I still get stuck on the splash screen
Hi,
have you fixed it? I face the same/similar issue, that I stuck at twrp splash screen after booting in twrp with fastboot
Code:
fastboot boot twrp-3.5.2_9-0-tissot.img
I have erased/formatted everything (userdata, cache, boot) and also tried to reflash the original rom with mi flash tool, but without success.
Any ideas?
MBR might be creating problem , try clean install with mi flash tool with official ROM .
@MIN313 Thanks for your response.
I tried to flash the official rom with the flash tool ( see here: https://forum.xda-developers.com/t/mi-a1-flash-sec-error.4139573/#_=_ ) .
xiaomiA1 said:
@MIN313 Thanks for your response.
I tried to flash the official rom with the flash tool ( see here: https://forum.xda-developers.com/t/mi-a1-flash-sec-error.4139573/#_=_ ) .
Click to expand...
Click to collapse
Does MiFlash recognize your phone? If not, try instaling ADB drivers nd disable driver enforcment,
To kick device out of diagnostic mode and into QDLoader you will need either:
1) A "deep flash" cable
2) Take the phone apart and bridge test points
There are guides online for both, you can Google. You can make deep flash cable yourself fairly easily with a spare USB cable. Testpoint location is found easily via Google and can be bridged with tweezers or small flat-head screw driver.
MIN313 said:
Does MiFlash recognize your phone? If not, try instaling ADB drivers nd disable driver enforcment,
To kick device out of diagnostic mode and into QDLoader you will need either:
1) A "deep flash" cable
2) Take the phone apart and bridge test points
There are guides online for both, you can Google. You can make deep flash cable yourself fairly easily with a spare USB cable. Testpoint location is found easily via Google and can be bridged with tweezers or small flat-head screw driver.
Click to expand...
Click to collapse
If Phone Showing Charging Only and Can't Even Transfer Data , Not Detected on Pc then will have to do EDL flash
My phone is recognized by MiFlash when I enter the fastboot mode
It is also shown with
Code:
fastboot devices
and I can boot into TWRP, but it stucks in splash screen of twrp.
Code:
fastboot boot twrp-3.5.2_9-0-tissot.img
I also tried older versions of twrp for tissot.
smilar issue, following attempts:
flashed with MiFlash, with or without EDL
flashed installing image with twrp
flashing after wiping dalwik, data, system and so on
flashed several type of ROM: official from xiaomi, crdroid, pixel, lineage
phone only booting with twrp (if installed) or stuck on mi logo
Greetings everybody,
please I need help.
Some days ago I rooted my lenovo tb-x606f and then I installed twrp recovery but Yesterday I uninstalled some preinstalled apps about games, browser and other little things and after this during rebooting the tablet it go in bootloader mode and now i'm not able to boot the system.
I tried to reflash the firmware with SP flash tool and the guide said to shutdown the lenovo tab during flasihng but nothing suceeded.
So I discovered the TWRP recovery was already working and I tried to format the tablet for cleaning it before a new flash but the twrp was unable to mount vendor and i tried to manually mount it in mount section without success.
So during a research i discovered that I need to proceed in fastboot mode flashing manually recovery.img; system.img; boot.img and userdata.img
I did this but the bootloop persists and TWRP recovery was deleted!
I tried the last command in command prompt adb fastboot in the folder of stock firmware: fastboot flashall but the reply is: fastboot: error: could not read android-info.txt
Thank you in advance and have a good day.
Use lenovo rescue smart assistant. download here
It will recognize the device model automatically and flash the latest firmware for it. 5 mins or so and it should be good as new. Unfortunately you'll have to flash twrp again and reroot.
Thank you,
i updated Lenovo Rescue Smart Assistant finding my tb-x606f that before was not present.
I downloaded the firmware in Lenovo Smart Assistant and via SP Flash Tool I flashed it, formatting data and browsing auth.key ; android scatter.txt; and update.bin (the first file)
$ fastboot set_active a
Hey guys,
I turned on my phone after years and I saw it's stuck on rescue mode with errors number 1 (security verify failed) & 10 (boot image).
I was able to go to eRecovery and Fastboot only.
Wiping data and factory reset through eRecovery didn't fix the problem and also I couldn't flash the whole rom using dload mode.
Then I checked fastboot and found out the bootloader was locked. After doing my research, I unlocked the bootloader using PotatoNV and testpoint. Then I could only flash some images like boot, system, recovery & cust. Not other images. Problem remains. Then I used testpoint mode and I was able to flash most of the images like HIFI etc, but nothing changes yet
I also tried Huawei smartphone multi-download and IDTML but they fails too. tried to use SP Flash Tools but couldn't find compatible rom with it.
Its firmware is C185B572. I can flash this version images using fastboot only. Others go to prim vrl failure.
Also flashed TWRP for using that but can't go to it at all.
I don't know what to do anymore
Any help would be appreciated.
Decterox said:
I also tried Huawei smartphone multi-download and IDTML but they fails too. tried to use SP Flash Tools but couldn't find compatible rom with it.
Click to expand...
Click to collapse
Hello!
I’m having the same issue (I haven’t unlock the bootloader though) as you and sadly don’t have any solution yet.
However, what’s this "Huawei samrtphone multi-download" and "IDTML"?
I do have some (hopefully!) compatible ROM that I’m willing to try with SP Flash Tool.