Related
hello,
my honor 7 hard bricked after flashing the wbt rom 5.0
i can't access to fastboot,and recovery mode but one think, adb can read the device but when i do a command i have no answer
can anyone help please?
What does fastboot devices says?
Can you boot into Recovery, eRecovery or fastboot?
Does HiSuite recognizes the phone?
zinko_pt said:
What does fastboot devices says?
Can you boot into Recovery, eRecovery or fastboot?
Does HiSuite recognizes the phone?
Click to expand...
Click to collapse
fastboot doesn't recognize my device.
my phone cant wake up i tried all buttons combinations
Hisuite recognize my phone but he has to be in fastboot mode to unbrick it
Then I'm sorry but I can't help you. Probably someone else can.
Lessons I've learned:
Don't be the first to test and be the Guinea pig.
Don't put a lot of faith on 3rd party ROMs whose equipments have a small community of developers.
Someone can help me ?
Do you remember what you have done in order to brick it?
Its not easy These days to actually brick a phone. Was it the first Rom you flashed?
Sent from my PLK-L01 using XDA Free mobile app
simo255 said:
Someone can help me ?
Click to expand...
Click to collapse
Does the phone charge at all?
Does it light any led, screen, anything?
One thing I've done in another device was to complete discharge, still try to turn it on for dozens of times, just to make sure, then wait for 48h and plug it in to power to see if charging screen goes on.
zinko_pt said:
Does the phone charge at all?
Does it light any led, screen, anything?
One thing I've done in another device was to complete discharge, still try to turn it on for dozens of times, just to make sure, then wait for 48h and plug it in to power to see if charging screen goes on.
Click to expand...
Click to collapse
Yes, the phone is charged
No, anything
i tried to turn it on many times and no result :/
i think that the bootloader is death,so there is a method to install the bootloader on phones via adb ?
Have you tried to turn it on with volume down and with USB cabel connected to PC ? This should start bootloader, you couldn´t damage bootloader area by installing custom wbt rom as it is separated memory. If you will be successful on bootloader, then flash via fastboot commands latest b371. system, boot, recovery and optionally cust.
Ing.King said:
Have you tried to turn it on with volume down and with USB cabel connected to PC ? This should start bootloader, you couldn´t damage bootloader area by installing custom wbt rom as it is separated memory. If you will be successful on bootloader, then flash via fastboot commands latest b371. system, boot, recovery and optionally cust.
Click to expand...
Click to collapse
Hello,
i can't access to bootloader but adb detect my phonr when he's connected to PC
Bad2hold said:
Do you remember what you have done in order to brick it?
Its not easy These days to actually brick a phone. Was it the first Rom you flashed?
Sent from my PLK-L01 using XDA Free mobile app
Click to expand...
Click to collapse
the first rom i've flashed is digirom v4.2
Up
Hi,
I can try to help you but i need more information:
Current version of Honor 7 ? (PLK-L01, PLK-TL01H, etc.).
Android version before flash ?
Did you unlock bootloader successfully ?
Did you install TWRP successfully?
Which rom did you try to use to flash your honor 7?
From which country are you?
Thanks,
If ADB detects, it means you can do fastboot commands.
And most probably you have a corrupted boot.img.
Have you tried to fastboot flash boot boot.img from the oficial rom but the same version as the last to be know working rom in your H7?
sebastien_be said:
Hi,
I can try to help you but i need more information:
Current version of Honor 7 ? (PLK-L01, PLK-TL01H, etc.).
Android version before flash ?
Did you unlock bootloader successfully ?
Did you install TWRP successfully?
Which rom did you try to use to flash your honor 7?
From which country are you?
Thanks,
Click to expand...
Click to collapse
Hello,
i have the plk-l0a version
yes i unlocked bootloader with the y300 method
yes i installed twrp succesfully
i flashed the wbt rom 5.0
i'm from Morocco
thanks
zinko_pt said:
If ADB detects, it means you can do fastboot commands.
And most probably you have a corrupted boot.img.
Have you tried to fastboot flash boot boot.img from the oficial rom but the same version as the last to be know working rom in your H7?
Click to expand...
Click to collapse
Yes i tried they tell me 'waiting for device'
up
simo255 said:
Yes i tried they tell me 'waiting for device'
Click to expand...
Click to collapse
Okay first thing, I think you are connected via adb and not in fastboot mode, so no fastboot command will work in adb mode.
If you are able to get into adb mode, try to fire this command:
Code:
adb reboot bootloader
If this takes you to bootloader mode, then flash all the *.img files from the version you were previously on ex. B330 or B370.
Then after doing that put dload folder with UPDATE.APP of the version you were on before.
Tell me if this works for you.
DigiGoon said:
Okay first thing, I think you are connected via adb and not in fastboot mode, so no fastboot command will work in adb mode.
If you are able to get into adb mode, try to fire this command:
Code:
adb reboot bootloader
If this takes you to bootloader mode, then flash all the *.img files from the version you were previously on ex. B330 or B370.
Then after doing that put dload folder with UPDATE.APP of the version you were on before.
Tell me if this works for you.
Click to expand...
Click to collapse
Hello, thanks for replying
my phone doesn't boot at all , i have to change the motherboard of my phone
simo255 said:
Hello, thanks for replying
my phone doesn't boot at all , i have to change the motherboard of my phone
Click to expand...
Click to collapse
Oh sorry to hear that, but you said that your computer detects your phone, doesn't it?
hello, I have made a twrp port for the console jxd s192 with tegra k1, and I have used the twrp of the nvidia shield tablet, same soc, same resolution.
but I'd like to know if I can be bricked by installing a bad recovery port (it's the first time I make one)
and the original recovery jxd s192, occupies 7.36mb and the twrp port occupies 12.6mb
I have not found a way to see the size of my recovery partition, and I am afraid that the recovery will be bigger than the partition and it will come out, is this possible?
I hope for your help, thanks in advance
Danny.69 said:
hello, I have made a twrp port for the console jxd s192 with tegra k1, and I have used the twrp of the nvidia shield tablet, same soc, same resolution.
but I'd like to know if I can be bricked by installing a bad recovery port (it's the first time I make one)
and the original recovery jxd s192, occupies 7.36mb and the twrp port occupies 12.6mb
I have not found a way to see the size of my recovery partition, and I am afraid that the recovery will be bigger than the partition and it will come out, is this possible?
I hope for your help, thanks in advance
Click to expand...
Click to collapse
No, it is not possible for TWRP.img to exceed the recovery partition size allotted in the device.
At most, probably, you will not be able to boot to recovery partition.
There is no chance of hard brick.
Boot into Recovery
Danny.69 said:
hello, I have made a twrp port for the console jxd s192 with tegra k1, and I have used the twrp of the nvidia shield tablet, same soc, same resolution.
but I'd like to know if I can be bricked by installing a bad recovery port (it's the first time I make one)
and the original recovery jxd s192, occupies 7.36mb and the twrp port occupies 12.6mb
I have not found a way to see the size of my recovery partition, and I am afraid that the recovery will be bigger than the partition and it will come out, is this possible?
I hope for your help, thanks in advance
Click to expand...
Click to collapse
Hi there,
Well if you're scared of bricking your device why don't you try to boot into recovery using adb interface, so in that way, the device won't get bricked.
Hope this works
Augustoandro said:
No, it is not possible for TWRP.img to exceed the recovery partition size allotted in the device.
At most, probably, you will not be able to boot to recovery partition.
There is no chance of hard brick.
Click to expand...
Click to collapse
thanks for the answer, if there is no possibility of hard brick, I remain calmer.
KIBS2173 said:
Hi there,
Well if you're scared of bricking your device why don't you try to boot into recovery using adb interface, so in that way, the device won't get bricked.
Hope this works
Click to expand...
Click to collapse
No, I understand very well what you want to say.
just reboot the device in recovery, from adb?
"adb reboot recovery"?
And so now, can not you bricking?
Hi there,
Well you have to put the twrp file into the adb installation folder or use cd /
Then you have to type adb reboot fastboot.
And then fastboot boot recovery recovery.img
If it doesn't work please let me know and no it won't brick as its not installing on the phone
If that command didn't work
Try
ADB BOOT RECOVERY RECOVERY.IMG
OR
ADB FASTBOOT RECOVERY RECOVERY.IMG
TRY VARIOUS VERSIONS OF THAT BECAUSE WELL I FORGOT THE COMMAND TO BE HONEST
Danny.69 said:
thanks for the answer, if there is no possibility of hard brick, I remain calmer.
No, I understand very well what you want to say.
just reboot the device in recovery, from adb?
"adb reboot recovery"?
And so now, can not you bricking?
Click to expand...
Click to collapse
At least hit thanks, bro
KIBS2173 said:
Hi there,
Well you have to put the twrp file into the adb installation folder or use cd /
Then you have to type adb reboot fastboot.
And then fastboot boot recovery recovery.img
If it doesn't work please let me know and no it won't brick as its not installing on the phone
If that command didn't work
Try
ADB BOOT RECOVERY RECOVERY.IMG
OR
ADB FASTBOOT RECOVERY RECOVERY.IMG
TRY VARIOUS VERSIONS OF THAT BECAUSE WELL I FORGOT THE COMMAND TO BE HONEST
Click to expand...
Click to collapse
I can not go into fastboot.
with the "adb reboot fastboot" command, it restarts, the splash logo comes out, it is restarted, and starts in android
but if comrade Augustoandro says that there is no possibility of hard brick, I can flash the twrp.
do you also think that there is no possibility of brick?
I tried flashing the twrp port and it does not work ....
I tried to make another port cwm, and it does not work either ....
Could someone help me make a twrp port that works?
Augustoandro said:
At least hit thanks, bro
Click to expand...
Click to collapse
Qualcuno riesce a fare una rom x jxd s192 nvidia?
Hello everyone and sorry for my English I am French! I ask for your help because I have a little problem.
I tried to root my xiaomi redmi note 3 pro premium smartphone that I bought in China 2 years ago.
I unlocked the bootloader and then I installed adb on my PC, no worries.
Then I downloaded the TWRP from my smartphone (I took kenzo, I do not know if it's the one I had to take).
I unzipped the folder and renamed the image recovery.img that I copied to the adb folder.
Then I launched the command "fastboot flash recovery recovery.img" then "fastboot boot recovery.img"
and then I restarted the smartphone by clicking on system (in TWRP) and since my phone remains locked to the Mi logo.
I have access to Fastboot and my smartphone is always recognized when I run the "fastboot devices" command.
And then I retried the manipulation and at the end I rebooted in recovery (in TWRP)
but it did not change anything.
Is there a way to get back to normal by keeping all the data on my smartphone? Or can I recover my data in another way?
Thank you in advance for your help !
First Why would you flash & then boot twrp? why dont just only flash and boot to recovery by Power + VOL UP to boot into recovery
and second What did you do when you're on twrp? You did not give us any details about that
Peak.Krittin said:
First Why would you flash & then boot twrp? why dont just only flash and boot to recovery by Power + VOL UP to boot into recovery
and second What did you do when you're on twrp? You did not give us any details about that
Click to expand...
Click to collapse
I just wanted to root my smartphone (have administrator rights)
So I entered TWRP and it asked me for a password that I did not have so I clicked cancel then reboot then on system
(by searching on google I understood that this password would come from the diagram of unlocking of the screen or the sensor of impression and that without this password the data of the smartphone could not be decrypted)
Except that restarting the smartphone is blocked on the Mi logo.
I did not do anything else. (I wanted to download and installed SuperSU after reboot, but I did not do it).
Then I went back to TWRP because I can go back (but I can not see the data of the smartphone without the password that it asks me when I arrive in TWRP) and I made a wipe cache (in TWRP) but it has not changed anything.
just use xiaomi.eu if it present for ur device
Peak.Krittin said:
just use xiaomi.eu if it present for ur device
Click to expand...
Click to collapse
use xiaomi.eu ?
https://youtu.be/YI2CtIIPVaI
check this vid for reference, and I recommend Magisk too over superSU.
You're right
Peak.Krittin said:
You're right
Click to expand...
Click to collapse
Thank you very much the video solved my problem
jo2607 said:
Thank you very much the video solved my problem
Click to expand...
Click to collapse
I have to put the subject in "resolved"?
Hi All,
I've been crawling the web the past few days to find a solution to my problem and unfortunately I didn't...
I have a Asus Zenfone 3 Max ZC520TL MT6737M, I never did a custom OS installation before and didn't know anything about how phone works except the Linux kernel
After 2 or 3 weeks playing with custom rom and recovery, softbrick, fastboot and adb I finally successfully intalled a custom OS, I wanted lineageOS but only found an Himax image working properly (with bluetooth., etc) for my phone and TWRP as custom recovery.
I setted my parameters for all my applications and after inserting my SIM card the network was not working, I tried a factory reset from the phone and then I got stuck in twrp however the way I booted, I tried flashing the os again, the recovery again wiping/formatting data, I was still stuck in TWRP
Then I executed :
fastboot format:ext4 cache
fastboot format:ext4 boot
And now I can't boot nor in twrp nor in fastboot, I can't access the bootloader using power and volume up, and my phone bootloop
Is there a way to get to fastboot to reinstall the recovery and then from here the os or is my phone hardbricked with no future, ready for trash?
Thank you
rominail said:
then I executed :
fastboot format:ext4 boot
Click to expand...
Click to collapse
You completely destroyed phone's boot-loader, what is comparable to a computer's BIOS.
What do you expect? IMO phone is case for the e-waste.
rominail said:
Hi All,
I've been crawling the web the past few days to find a solution to my problem and unfortunately I didn't...
I have a Asus Zenfone 3 Max ZC520TL MT6737M, I never did a custom OS installation before and didn't know anything about how phone works except the Linux kernel
After 2 or 3 weeks playing with custom rom and recovery, softbrick, fastboot and adb I finally successfully intalled a custom OS, I wanted lineageOS but only found an Himax image working properly (with bluetooth., etc) for my phone and TWRP as custom recovery.
I setted my parameters for all my applications and after inserting my SIM card the network was not working, I tried a factory reset from the phone and then I got stuck in twrp however the way I booted, I tried flashing the os again, the recovery again wiping/formatting data, I was still stuck in TWRP
Then I executed :
fastboot format:ext4 cache
fastboot format:ext4 boot
And now I can't boot nor in twrp nor in fastboot, I can't access the bootloader using power and volume up, and my phone bootloop
Is there a way to get to fastboot to reinstall the recovery and then from here the os or is my phone hardbricked with no future, ready for trash?
Thank you
Click to expand...
Click to collapse
You NEVER format your boot partition as ext4 it's a raw boot.img which holds the kernel and ramdisk. You should really do research and follow instructions alittle better than that.. unfortunately I don't think your device can be saved and if you flashed aboot or sbl1/2/3 then your SOL
Thanks
Thank you for your answers!
I don't know why I did that (sometimes I have crazy bad ideas), I didn't see that on internet
rominail said:
Thank you for your answers!
I don't know why I did that (sometimes I have crazy bad ideas), I didn't see that on internet
Click to expand...
Click to collapse
That's okay! Please so make sure you do some research if your new to the custom OS scene.. it's always good to learn new things
maybe you can flash again like from the factory by using the default flashing and ROM tools.
BryanHafidz said:
maybe you can flash again like from the factory by using the default flashing and ROM tools.
Click to expand...
Click to collapse
If your in a Qualcomm chipset and you have an EDL programmer that works for your device I have custom tools in my cloud storage to create an EDL firmware if you don't ready have one. If your on MTK then there is Sugar MTK or SP flash tool that can work. If your an another one you may be out of luck as it seems nobody has been able to restore those chipsets
EDIT: I do have a whole zip file of programmers and one that I use for my LG Zone 2 (msm8x10.mbn)
TheExploitedOne said:
You NEVER format your boot partition as ext4 it's a raw boot.img which holds the kernel and ramdisk. You should really do research and follow instructions alittle better than that.. unfortunately I don't think your device can be saved and if you flashed aboot or sbl1/2/3 then your SOL
Click to expand...
Click to collapse
we have the same problem but I didn't do like you.
I entered these commands
*fastboot flash recovery boot.img (I'm stupid lol)
*fastboot flash boot boot.img
*fastboot reboot*
mahirab23 said:
we have the same problem but I didn't do like you.
I entered these commands
*fastboot flash recovery boot.img (I'm stupid lol)
*fastboot flash boot boot.img
*fastboot reboot*
Click to expand...
Click to collapse
What seems to be going on after the flash?
TheExploitedOne said:
What seems to be going on after the flash?
Click to expand...
Click to collapse
the biggest problem is i have reset the phone and i am stuck with this message: "to start android enter your password". I entered the correct password but another message appears with a reset phone option.
Since the recovery.img file is no longer in the system, the phone keeps making this loop.
mahirab23 said:
the biggest problem is i have reset the phone and i am stuck with this message: "to start android enter your password". I entered the correct password but another message appears with a reset phone option.
Since the recovery.img file is no longer in the system, the phone keeps making this loop.
Click to expand...
Click to collapse
If you can get into fastboot run the following:
fastboot erase recovery
fastboot erase userdata
fastboot format:ext4 userdata
Then reflash your recovery
TheExploitedOne said:
If you can get into fastboot run the following:
fastboot erase recovery
fastboot erase userdata
fastboot format:ext4 userdata
Then reflash your recovery
Click to expand...
Click to collapse
I can't get into fastboot.
another solution?????
mahirab23 said:
I can't get into fastboot.
another solution?????
Click to expand...
Click to collapse
Can you access EDL mode?
TheExploitedOne said:
Can you access EDL mode?
Click to expand...
Click to collapse
thank you for your attention and suggestions.
I haven't tried this method yet.
I'm not good with EDL mode
Can SP tools and MiracleBox help me?
mahirab23 said:
thank you for your attention and suggestions.
I haven't tried this method yet.
I'm not good with EDL mode
Can SP tools and MiracleBox help me?
Click to expand...
Click to collapse
MiracleBox and QPST yes
TheExploitedOne said:
MiracleBox and QPST yes
Click to expand...
Click to collapse
good !!!: o: o
can you develop the method with Miracle Box and QPST ? please!!!
mahirab23 said:
good !!!: o: o
can you develop the method with Miracle Box and QPST ? please!!!
Click to expand...
Click to collapse
I have the tools needed in my cloud I can make into a zip file. You'll need to also do some research on your part but I can also write a readme file too so you have a basic understanding. Just give me a few to get the link
EDIT:
Here you go this has all you'll need for flashing your device in EDL as well as create the firmware if needed
https://mega.nz/file/rc8CVIiB#qnM3_ZzrvCJtp_M7Y9ZftZqDtGgWeN0tqFrLlT30pws
TheExploitedOne said:
MiracleBox and QPST yes
Click to expand...
Click to collapse
thank you
I finally managed to reset the phone thanks to SoftwareDownload
thank you really. you are really kind and available:bien::bien::bien:
mahirab23 said:
thank you
I finally managed to reset the phone thanks to SoftwareDownload
thank you really. you are really kind and available:bien::bien::bien:
Click to expand...
Click to collapse
Absolutely good sir! I'm glad that I can help
TheExploitedOne said:
If your in a Qualcomm chipset and you have an EDL programmer that works for your device I have custom tools in my cloud storage to create an EDL firmware if you don't ready have one. If your on MTK then there is Sugar MTK or SP flash tool that can work. If your an another one you may be out of luck as it seems nobody has been able to restore those chipsets
EDIT: I do have a whole zip file of programmers and one that I use for my LG Zone 2 (msm8x10.mbn)
Click to expand...
Click to collapse
Thank you for your help, unfortunately it's a mediatek
hi all,
i have a rooted vivo air lte with supersu.
i wanted to install magisk with the manager 8.0.3 (the boot.img from stock rom i extracted to downloads folder) by choosing direct install.
now the phone hangs on the bootlogo.
i can boot into recovery and choose "apply update from adb"
i installed fastboot and adb on the pc.
in the terminal command "adb devices" i see "devicenr sideload".
when i enter fastboot devices, there is no device shown.
im not sure if i have unlocked the bootloader when i rooted the phone a year ago..
so what do i have to do now to get it booting again?
thanks for the help!
schlunk said:
in the terminal command "adb devices" i see "devicenr sideload".
Click to expand...
Click to collapse
Device is configured to get booted in "Sideload" mode what is a variant of ADB mode.
Try this
Code:
adb devices
adb reboot
to return to "Normal" mode.
no, this is what i have chosen in the recovery, otherwise i dont get any device listed in the terminal..
@schlunk
Once being in the Android Recovery Mode and you select option Reboot system the Android device simply gets restarted: the actually configured ADB mode herewith doesn't get changed / reset.
when i enter "adb reboot" in the terminal its "error closed"..
is ther e something i can sideload then to solve this, when the phone is waiting for the package to sideload?
thanks for helping!
schlunk said:
when i enter "adb reboot" in the terminal its "error closed"..
is ther e something i can sideload then to solve this, when the phone is waiting for the package to sideload?
thanks for helping!
Click to expand...
Click to collapse
QFIL is the answer.
this is a flasher like odin?
so can i just flash the boot.img, that magisk wrote back to the stock one?
and like i said im not sure if the bootloader is unlocked, does it play a role in this?
schlunk said:
this is a flasher like odin?
so can i just flash the boot.img, that magisk wrote back to the stock one?
and like i said im not sure if the bootloader is unlocked, does it play a role in this?
Click to expand...
Click to collapse
https://firmwarefile.com/blu-vivo-air-lte-v0010uu
https://www.youtube.com/watch?v=MdknZvaTwl4
thats exactly the file i downloaded to extract the boot.img and see what happend
i dont want to flash the complete stock firmware again with the risk that my phone is bricked after that.
there must be some easier solution for this??
cant i just flash what magisk messed up?
schlunk said:
there must be some easier solution for this??
cant i just flash what magisk messed up?
Click to expand...
Click to collapse
Nope, I don't think there is.
Depends if that boot is same that was in your device. See the video
and the thread too: https://forum.hovatek.com/thread-31476.html
The boot should be the same, the firmware is exactly the same like in the phone regarding the label.
So with this linked method, flashing a single partition means, the boot.img can be flashed solo, without the need of flashing the whole firmware?
And when that doesnt work, i still could flash the whole firmware then as last resort?
That what I would do... Good luck!