Related
Well, I really did it this time. In my efforts of messing with the M Preview build and trying to eliminate the "verification failed" startup message I made the mistake of locking the bootloader. Now the phone will not boot into Android or into Recovery. I'm stuck in Bootloader and it won't let me "fastboot OEM unlock" the device because in order to do this you need to boot into Android and tick the box to allow OEM unlocking (which I also unticked before getting into this mess, like an idiot).
EDIT: Got it resolved!
In order to get into Recovery I had to use the following commands in the bootloader:
fastboot format cache
fastboot format userdata
After doing this I was able to boot into recovery. However, recovery showed 0MB available storage and wouldn't mount /data, which prevented me from installing anything. It also wouldn't allow me to copy anything to the SD card using Android File Transfer or ADB sideloading.
To solve this I went into "Wipe" while in recovery and did a full format (the one that requires you to type "yes" before proceeding"
After doing this and booting back into recovery, I had full storage space back and recovery was able to mount /data. At this point I just copy/pasted the 5.1.1 ROM onto the sdcard with Android File Transfer. Once installed, I flashed the ROM and it booted right up.
I then skipped through the setup to get to settings and in developer settings I ticked the box to allow OEM unlocking. After doing that, I booted back into the bootloader and used the fastboot command "fastboot oem unlock" to unlock the bootloader again.
Once that was done I was able to use fastboot commands to flash the M preview all over again.
Hopefully you don't find yourself in this mess, but if you do, I'm hoping the above solution works for you.
sn0warmy said:
Well, I really did it this time. In my efforts of messing the the M Preview build and trying to eliminate the verification failed startup message I really locked up the phone. I locked the bootloader and now the phone will not boot into either recovery or the ROM. It won't let me "fastboot OEM unlock" the device either because it requires me to go into settings and check the allow OEM unlock. However, since I can't boot into the ROM, I cannot do that.
I'm really stuck here. Any ideas?
Click to expand...
Click to collapse
Hope you can RMA it
akellar said:
Hope you can RMA it
Click to expand...
Click to collapse
Well.... s**t.
sn0warmy said:
Well.... s**t.
Click to expand...
Click to collapse
Is TWRP installed?
WAIT!!
I did the following:
- fastboot format cache
- fastboot format userdata
And the phone now boots into TWRP. It won't boot fully but it will boot into recovery. I'm trying to sideload a ROM now but I can't access the storage.
Edit: enabled ADB sideload so I can ADB push a ROM to the SD card to flash. Does anyone know the exact root folder name for the sd card to pusht he ROM to? Is it /data/media/?
I did something similar this past weekend while trying to do the 5.1.1 upgrade with the OTA files before the Factory images were available.
Try and use the WugFresh tool to wipe the cache and such, and try some of the other obvious settings in the tool.
It was late and I'm not 100% sure what I did but I do remember reflashing the LRX22C from the factory image using the tool. Everything I did was from the tool minus the 5.1 OTA that came through once I was able to get back into the device. From there I was able to unlock the bootloader again.
I was worried myself that I might have to send the phone back but I just kept trying, don't give up just yet. I've been told many times it's almost impossible to brick an android device now a days.
Good luck!
sn0warmy said:
WAIT!!
I did the following:
- fastboot format cache
- fastboot format userdata
And the phone now boots into TWRP. It won't boot fully but it will boot into recovery. I'm trying to sideload a ROM now but I can't access the storage.
Edit: enabled ADB sideload so I can ADB push a ROM to the SD card to flash. Does anyone know the exact root folder name for the sd card to pusht he ROM to? Is it /data/media/?
Click to expand...
Click to collapse
Enable MTP in TWRP then drag n drop.
rootSU said:
Enable MTP in TWRP then drag n drop.
Click to expand...
Click to collapse
Can't access device storage.
However, I was able to ADB push the ROM to the SDcard. But when I try and install the ROM it gives me a bunch of errors saying "unable to mount '/data'" and "unable to mount storage"
Ideas?
sn0warmy said:
Can't access device storage.
However, I was able to ADB push the ROM to the SDcard. But when I try and install the ROM it gives me a bunch of errors saying "unable to mount '/data'" and "unable to mount storage"
Ideas?
Click to expand...
Click to collapse
Assuming you tried ticking data in twrp mounts...
In twrp, try and format data again. If that fails, try to format it as another file system such as f2fs before formatting it back to ext4
rootSU said:
Assuming you tried ticking data in twrp mounts...
In twrp, try and format data again. If that fails, try to format it as another file system such as f2fs before formatting it back to ext4
Click to expand...
Click to collapse
Success!
TWRP was also reporting 0mb available storage. I went into Wipe and performed a full format. Booted back into recovery and storage was showingt he full amount again. I was then able to plug the phone in and enable MTP and drag/drop the 5.1.1 ROM onto the SD card. Just flashed it and it booted right up!
I'm going to update the OP with all this info just in case someone else runs into the issue and needs help.
Thanks for your help!
sn0warmy said:
Well, I really did it this time. In my efforts of messing with the M Preview build and trying to eliminate the "verification failed" startup message I made the mistake of locking the bootloader. Now the phone will not boot into Android or into Recovery. I'm stuck in Bootloader and it won't let me "fastboot OEM unlock" the device because in order to do this you need to boot into Android and tick the box to allow OEM unlocking (which I also unticked before getting into this mess, like an idiot).
Click to expand...
Click to collapse
Hi,
I faced the same condition like you experienced, with some differences:
- the phone stuck in "Google" logo
- stock recovery is accessible from bootloader
- I am unable to mount sdcard or install rom from sd card, but could conduct adb sideload
However, am stuck with verifying update package showing :
E: footer is wrong
E: signature verification failed
any ideas what to do next?
================ edited- add below info on how I got stuck
So my N6 was still on 5.0 (has not been updated to 5.1). I decided to try the M preview. I downloaded the preview, and began the process as follows:
1. reboot into bootloader
2. fastboot oem unlock
3. flash-all (success on loading the bootloader and radio, but error on updating the image)
4. hence i followed to flash individually:
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
5. and comes the stupid thing ! --> fastboot oem lock (really really regret why I did this)
6. and then once reboot, it stuck in Google logo forever
However, I am still able to access:
- bootloader (fastboot recognize the device, but wouldn't allow me to fastboot oem unlock)
- able to go to stock recovery, and as mentioned above:
I am unable to mount sdcard or install rom from sd card, but could conduct adb sideload
However, am stuck with verifying update package showing :
E: footer is wrong
E: signature verification failed
I tried to adb sideload the M preview image and 5.1 LMY47I but both showing the above error....
hope you can shed some light on this...
Please does anyone have a solution to this? please help me
Iambenqazy said:
Please does anyone have a solution to this? please help me
Click to expand...
Click to collapse
A solution to what? Keep in mind your problem may be different from the OP's issue, so if you want people to help you it's necessary to provide plenty of information, such as what you were trying to do, how you tried to do it, and any other information that you believe may be useful.
Strephon Alkhalikoi said:
A solution to what? Keep in mind your problem may be different from the OP's issue, so if you want people to help you it's necessary to provide plenty of information, such as what you were trying to do, how you tried to do it, and any other information that you believe may be useful.
Click to expand...
Click to collapse
.
OK What i was trying to do was to flash a stock recovery, i start it by running the flash-it all.bat file in the factory image zip, it changed the user interface of the bootloader after first reboot and and had an error for "archive: recovery.sig not found" (something like). the phone status shows Software Version: Modified and fastboot oem unlock dont give the confirmation.
and
now my phone wont even boot to the bootloader, everything turned black. please hellp!!!!:crying::crying:
If you can't even get into the bootloader (volume down and power) you may have to have the device serviced. Do you get a response when you type "adb devices"?
Iambenqazy said:
.
now my phone wont even boot to the bootloader, everything turned black. please hellp!!!!:crying::crying:
Click to expand...
Click to collapse
Maybe it just crashed at a black screen? Does a very long press of the power button (over 10 secs) cause it to react?
Or maybe the battery is empty? Try connecting the power supply for some time.
i did that but no response.
Iambenqazy said:
i did that but no response.
Click to expand...
Click to collapse
The very dead battery is a real possibility. The thing is, using the charger that came with the phone isn't going to help. If you think the battery being dead is a possibility, you would need to plug the phone into a USB port on a PC, that is a very slow charge. Leave it on there overnight then unplug and replug. If the led at the top of the screen lights or the battery icon shows on the screen, you have hope. At this point using the original charger should get the battery going again. In this case, plan on replacing the battery.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Hey xda community,
last night i run into a tricky situation.
First, I explain what I did
I bought me the P9 EVA-L09 via Telekom Germany.
cause i don't want the Telekom **** on my device i decide to TWRP, Root, and flash P9 stock Rom on it.
Unlocking and install TWRP with the SRK Tool works fine. Install the Root was a bit more tricky, because windows lost the correct ADB connection when i go into TWRP Sideload Mode. Because that does not work, i decide to flash the P9 Stock ROM without Root to come forward.
While flashing, (i don''t now anymore which method i choose to flash) an error appers, and the flash process canceled.
The Device don't boot anymore. After a loot of googeling and testing, i've found out that the problem was the encryption of the /Data Partition.
TWRP was unable to mount it, same for the /cust and one more.
After reading about other Methods to get the Phone work again i try this Method i've found on xda.
http://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818
Unfortunately the "press all buttons on the phone" Method don't work.
I also tried out the Huawei Update Extractor to flash single image files to the partitons of the phone. I used the dload file form the previous Method
http://forum.xda-developers.com/showthread.php?t=2433454
http://www.modaco.com/forums/topic/372688-re-partition-stock-partition-tool/ (using the answer on the bottom)
Download from xda huawei update extractor and extract img files from the update.
Turn off the phone, then press vol- and power key, you are in fastboot mode.
Then, flash img files from extracted rom with:
Fastboot flash system SYSTEM.IMG
fastboot flash boot BOOT.IMG
And do the same with the others...
When you finish, fastboot reboot
Click to expand...
Click to collapse
But that don't work. fastboot already replies with "Remote Command not allowed"
i changed the Method a bit. I've put the BOOT.IMG and RECOVERY.IMG an an SD card and flash it via the Install IMG Funktion of TWRP.
That workes very well and expect the /data partition every partition was mountable again.
Then i used the "Fastboot flash system SYSTEM.IMG" again, and tada it works without errors.
The device is booting again to Android, but it reports that the /Data Partition Decryption failed and i have to enter the Recovery Mode and do a factory reset to unlock the partition. If i reboot for get rid of this error the phone does not boot into the Recovery, it boot to the eRecovery which is useless for that because it only provide the eRecovery function instead of also a normal factory reset (how dump is this )
Now the state is, phone boots normal, reports the /Data is not decryptable, reboot to eRecovery, shutdown or reboot. It does really nothing else.
I can't get into the Fastboot/Download Mode, it ignores the Key Combination Volume down + Power. If i press this it starts normal.
I also can't get into the recovery / TWRP Mode, it ignores the Key Combination Volume Up + Power. If i press this is starts normal.
I've also noticed that the Phone is not conecting to the ADB on my computer, only the virtual CDROM from wich the HiSuite is installable connects.
I've also noticed that the eRecovery is not able to starts WIFI on the phone. It errors with "Starting WIFI failed!"
I also tryed out another time the dload function. This changed nothing. Phone boots still normal and run into the Decryption problem.
And i tried out to boot into fastboot or recovery after a cold reset, battery empty
Now it's on you. Has anybody an idea how i can solve one of the above problems. I think when one is solved the others will disappear via flashing new TWRP or so
Try connecting your phone to usb and then holding power+volume down until it boots to fastboot mode.
Huawei phone won't boot into recovery if system and twrp don't match but it should boot to fastboot allways.
What is the last rom you had on your phone while it was working?
Ogameplayer said:
Hey xda community,
last night i run into a tricky situation.
First, I explain what I did
I bought me the P9 EVA-L09 via Telekom Germany.
cause i don't want the Telekom **** on my device i decide to TWRP, Root, and flash P9 stock Rom on it.
Unlocking and install TWRP with the SRK Tool works fine. Install the Root was a bit more tricky, because windows lost the correct ADB connection when i go into TWRP Sideload Mode. Because that does not work, i decide to flash the P9 Stock ROM without Root to come forward.
While flashing, (i don''t now anymore which method i choose to flash) an error appers, and the flash process canceled.
The Device don't boot anymore. After a loot of googeling and testing, i've found out that the problem was the encryption of the /Data Partition.
TWRP was unable to mount it, same for the /cust and one more.
After reading about other Methods to get the Phone work again i try this Method i've found on xda.
http://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818
Unfortunately the "press all buttons on the phone" Method don't work.
I also tried out the Huawei Update Extractor to flash single image files to the partitons of the phone. I used the dload file form the previous Method
http://forum.xda-developers.com/showthread.php?t=2433454
http://www.modaco.com/forums/topic/372688-re-partition-stock-partition-tool/ (using the answer on the bottom)
Download from xda huawei update extractor and extract img files from the update.
Turn off the phone, then press vol- and power key, you are in fastboot mode.
Then, flash img files from extracted rom with:
Fastboot flash system SYSTEM.IMG
fastboot flash boot BOOT.IMG
And do the same with the others...
When you finish, fastboot reboot
But that don't work. fastboot already replies with "Remote Command not allowed"
i changed the Method a bit. I've put the BOOT.IMG and RECOVERY.IMG an an SD card and flash it via the Install IMG Funktion of TWRP.
That workes very well and expect the /data partition every partition was mountable again.
Then i used the "Fastboot flash system SYSTEM.IMG" again, and tada it works without errors.
The device is booting again to Android, but it reports that the /Data Partition Decryption failed and i have to enter the Recovery Mode and do a factory reset to unlock the partition. If i reboot for get rid of this error the phone does not boot into the Recovery, it boot to the eRecovery which is useless for that because it only provide the eRecovery function instead of also a normal factory reset (how dump is this )
Now the state is, phone boots normal, reports the /Data is not decryptable, reboot to eRecovery, shutdown or reboot. It does really nothing else.
I can't get into the Fastboot/Download Mode, it ignores the Key Combination Volume down + Power. If i press this it starts normal.
I also can't get into the recovery / TWRP Mode, it ignores the Key Combination Volume Up + Power. If i press this is starts normal.
I've also noticed that the Phone is not conecting to the ADB on my computer, only the virtual CDROM from wich the HiSuite is installable connects.
I've also noticed that the eRecovery is not able to starts WIFI on the phone. It errors with "Starting WIFI failed!"
I also tryed out another time the dload function. This changed nothing. Phone boots still normal and run into the Decryption problem.
And i tried out to boot into fastboot or recovery after a cold reset, battery empty
Now it's on you. Has anybody an idea how i can solve one of the above problems. I think when one is solved the others will disappear via flashing new TWRP or so
Click to expand...
Click to collapse
Try this.
http://forum.xda-developers.com/p9/how-to/tools-huawei-p9-firmware-updater-t3432457/page1
Sent from my HUAWEI VIE-L29 using XDA Labs
I see two possibilites for this behavior:
1) The phone only pretents to reboot but makes a kind of warm start (never running the code to branch to recovery/boot) -> if the phone seems powered off and you attach usb cable, do you see standard battery laoding animation (that's what it should be) or black screen / boot logo?
2) You flashed a wrong boot.img and/or recovery.img or flashing got screwed up
If you have wrong images, fastboot should still work as edint3000 said.
For the unlikely case (1) with non removable battery you have to wait until battery is drained before you can boot into fastboot after connecting USB cable. Edit: oops just saw you did that.
I had another phone that at some point decided to go only in fastboot with volume down and no power button, when powered up with USB power. But I had never such an issue with a Huawei phone. However, playing around a bit costs nothing (but time).
I see no reason why fast boot should not work. How did you find out, that everything is fine after flahing with TWRP and before flashing system with fastboot?
Did you do anything else than flashing the system.img with fastboot?
Chilli
Same problem here...Phone not boot/not enter fastboot mode/not enter recovery mode...just stuck "your device booting now" screen...any solution?
Hello Mossyhand
you should search for the recovery Method with an "dload" ROM. This are kind of special Roms wich are able to "selfflash" onto the phone.
You have to put the right file onto your SD Card and then you have to press some keys when i remember right.
Sadly i've forgot, when i solved my problem, to reply how i did that exactly ._.
But if you do search in the dload method you will figure a way out i guess
If you don't find an right file, i can upload you my file, i have it still on my computer
had the same problem
go into the erecovery, it will tell you the data partition has been damaged. u can wipe it from there. go into trwp again, install rom and stuff. voila, works
cheers
Hello everyone, I have the problem, that my 3T boots to recovery every time I boot. The system is no more booting. What I did was, "updating" in the CM about/update menu (from unofficial cm14.1 13.12. to 14.12. ).
So maybe an open recovery script was created and booted to bootloader. Update failed but I did it manually.
From now on the phone does just only boot twrp recovery (or is it a boot loop ?). I tried to restore a backup and install the oxygen os via zip and wiped all partitions (except internal storage) but nothing helps. Does anyone know this and can give me advice ? Thank a lot in advance.
Edit:
For the OnePlus One if found an error report which look a little bit my error:
The problem is suspected to stem from the "persist" partition getting corrupted during the reboot, even though CyanogenMod doesn't use this particular location. The damaged area doesn't get fixed like other partitions because a filesystem integrity check isn't ran. It's left corrupted, and even though the area isn't needed for the OS to run, the OnePlus One boot loops anyway.
Click to expand...
Click to collapse
But the partition layout on the 3T seems to be different, I can see only partitions like sda etc ...
same here
Called the 1+ support and they sent me the same file like in this post http://forum.xda-developers.com/oneplus-3t/help/unbrick-unbrick-tutorial-oneplus-3t-t3515306 They offered me a telephone support slot in 2 days, but I tried myself, now the default system is booting again. If you need assistance write I can guide you as best as i can.
Good luck to you.
sniperle said:
Called the 1+ support and they sent me the same file like in this post http://forum.xda-developers.com/oneplus-3t/help/unbrick-unbrick-tutorial-oneplus-3t-t3515306 They offered me a telephone support slot in 2 days, but I tried myself, now the default system is booting again. If you need assistance write I can guide you as best as i can.
Good luck to you.
Click to expand...
Click to collapse
Thank you!
Enviado do meu ONEPLUS A3003 através de Tapatalk
Thnaks so much
sniperle said:
Called the 1+ support and they sent me the same file like in this post http://forum.xda-developers.com/oneplus-3t/help/unbrick-unbrick-tutorial-oneplus-3t-t3515306 They offered me a telephone support slot in 2 days, but I tried myself, now the default system is booting again. If you need assistance write I can guide you as best as i can.
Good luck to you.
Click to expand...
Click to collapse
:good:
I follow your recommendation thanks for your assistance I fixed my OP3T,
What a mess ... after all this I wanted to install my CM backups again, but TWRP refused to boot. I had only a black screen with a white LED when going to recovery. But now after some hours I have a solution to this. You need to update Oxygen OS before going on !!
Make a full system update or flash this update via TWRP: http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_3.5.3/
After this TWRP is booting as expected.
Now I'll enjoy a beer or two or ....
Good luck to all others. If anybody needs assistance ... contact me.
never had a issue
Please help!!!! I tried flashing the update for the latest OTA, I had the full zip. I have unlocked bootloader, twrp, phh supersu, magisk and xposed. I did a nandroid backup and then clicked Wipe- Dalvik and Cache. I then flashed the zip. For 20 mins the boot logo was spinning around, so I rebooted into twrp to see what was going on. Now I can't reboot and it shows no data, it says my device is encrypted and I can't see any files. What can I do??
Was your internal storage encrypted before ?
TWRP doesn't show your internal storage and didn't ask for a password ?
fix bootloop
Boot into your recovery [Vol+ and Power]
Connect your phone to your PC
Execute the following fastboot command on your PC (More informations on fastboot)
Code:
fastboot continue
Your phone will start right away. :good:
I solved the problem
OK what i did was when the phone was starting and vibrating I push the power bottom and volume down bottom at the same time ,then i connected the phone to the PC,from the panel in the phone there are 3 categories to erase everything on the phone I did it all(1,2,3) and then I put the phone in ADB mode from the control panel in the phone,After that I flash via fastboot the original .zip from one plus for the version 4.0.3 (1.4 GB) ,when it finished I restarted and the phone started normal again,I hope this help someone alse,I was so desesperated:silly:.
RE
TOMASITO95 said:
OK what i did was when the phone was starting and vibrating I push the power bottom and volume down bottom at the same time ,then i connected the phone to the PC,from the panel in the phone there are 3 categories to erase everything on the phone I did it all(1,2,3) and then I put the phone in ADB mode from the control panel in the phone,After that I flash via fastboot the original .zip from one plus for the version 4.0.3 (1.4 GB) ,when it finished I restarted and the phone started normal again,I hope this help someone alse,I was so desesperated:silly:.
Click to expand...
Click to collapse
how ? can you please teach me ( my op3t didn`t go to system is says " md5 checksum failed , recovery failed , boot failed , system failed , boot_aging failed , dsp failed , modem failed please help me (
Change USB port
Try a different USB port. I flashed it through a 2.0 USB port instead of the 3.0 and no checksum error!
Hi All, I need fastboot!
Perhaps someone can help with my brick? I've unlocked the bootloader, installed TWRP and had lineageOS 18.1 installed once. The screen was dim so I tried to flash DotOS. And got a "failed to mount /tmp/com.android.resolv.apex to loop device /dev/block/loop16" error so I tried to reinstall stock 57 ROM.
I did "fastboot flash recovery boot.img" with the decrypted boot.img hoping to get colourOS recovery.
The phone is now bootlooping trying to get into recovery mode. It won't power off or respond to button presses except vol up + vol down seems to delay the reboot on a blank screen.
I was hoping to get to fastboot mode to flash TWRP. Can anyone help? Should I surrender and accept the bricking?
you can get back to stock by install the stock rom, vendor, and kernel with adb drivers and commands.
or
if your mobile is MIUI you can just use the software to revert back to stock rom remember it re-locks the bootloader and again you need to unlock
The phone is currently boot looping.
I can't even turn it off.
It displays RealME/Android logo, then small "> RECOVERY MODE" text at bottom, then "Orange State" text. Repeat..
It has no response to a usb cable - no usb messages in dmesg. So it is not detected by adb or fastboot.
When the battery finally goes flat, my only hope is that I can get fastboot to flash TWRP into the recovery partition. I am not confident of this :-(
frolyx said:
The phone is currently boot looping.
I can't even turn it off.
It displays RealME/Android logo, then small "> RECOVERY MODE" text at bottom, then "Orange State" text. Repeat..
It has no response to a usb cable - no usb messages in dmesg. So it is not detected by adb or fastboot.
When the battery finally goes flat, my only hope is that I can get fastboot to flash TWRP into the recovery partition. I am not confident of this :-(
Click to expand...
Click to collapse
did you ever get this solved and fixed? i have accidently done the same thing.
hey guys follow this youtube
managed to unbrick my phone
smiley.raver said:
did you ever get this solved and fixed? i have accidently done the same thing.
Click to expand...
Click to collapse
Not yet, but I will try the youtube method above..
This recovered the Phone!
But, win10 reported the MCT extractor contained a worm (the python script under linux didn't work). I'm not sure I can trust this phone 100% from now on LOL!
the bypass just deactivates mtk hardware verificaton as normally they have a special dongle they use with the software download
I havent had any issues
I will upload thw bypass i use which doesnt havw any virus
Hi everyone!
Since yesterday i am having problems with my phone, first it briked after a normal update, thanks god i unlocked the fastboot before, i installed a custom OS but didn't liked it, so i wiped both partition (and i think i ****ed up there)
So now i can still enter fastboot mode, but everytime i try to send fastboot boot judypn_TWRP_bootable-metadata.img (that yesterday worked) not it's not working anymore, it just boots normally and remain stuck in bootloop
On my microsd i put the img of twrp with metadata HavocOS and twrp zip too, yesterday i could install and enter in recovery mode them without any problem, today the boot img is sent but the phone "ignores" it.
PS. I can enter fastboot mode without problem, download mode isn't working
Thanks to anyone who can help!
Sporalinux said:
Hi everyone!
Since yesterday i am having problems with my phone, first it briked after a normal update, thanks god i unlocked the fastboot before, i installed a custom OS but didn't liked it, so i wiped both partition (and i think i ****ed up there)
So now i can still enter fastboot mode, but everytime i try to send fastboot boot judypn_TWRP_bootable-metadata.img (that yesterday worked) not it's not working anymore, it just boots normally and remain stuck in bootloop
On my microsd i put the img of twrp with metadata HavocOS and twrp zip too, yesterday i could install and enter in recovery mode them without any problem, today the boot img is sent but the phone "ignores" it.
PS. I can enter fastboot mode without problem, download mode isn't working
Thanks to anyone who can help!
Click to expand...
Click to collapse
So first, the forum you posted this in is called 'Roms, Kernels, recoveries and other development'... so which 'development' is this? a Rom? a Kernel? a Recovery?
None of the above right? So what you have is a 'question', and it should be in 'Questions and Answers'. Sorry if that offends, but if someone wants to find something in these forums, then posts need to be in the appropriate places...
First thing I'd do would be to get the phone's download mode (lgup) working again and flash a stock kdz. That way you can basically 'start over' (and hopefully have better results with your endeavors).
try this initially: Follow this link and read the 'notes' file. Hopefully that will give you lgup, if it doesn't then it's a more involved process to use edl and flash, basically, a whole image.
cheers