So a friend of mine has an LG D415, which apparently is the same as the Optimus L90. He asked me to install a ROM for him (CM 11) which requires an unlocked bootloader. He already had root (through "KingRoot") and I managed to successfully install TWRP custom recovery.
I then followed this post's instructions on how to unlock the bootloader, that's where everything went wrong.
The phone can still boot into android and recovery without any problems, but I keep getting this error when issuing commands through fastboot "failed (remote: unknown command)"
I have a backup copy of laf.img, but I'm not sure how exactly to flash it with fastboot down for the count.
I have that phone and found the bootloader was already unlocked, thus causing that failure message. Try just installing the ROM.
---------- Post added at 02:08 PM ---------- Previous post was at 02:06 PM ----------
Also, if you find that it doesn't recognize the sim card, make sure you flash the KitKat bootstack.
sandworm said:
I have that phone and found the bootloader was already unlocked, thus causing that failure message. Try just installing the ROM.
---------- Post added at 02:08 PM ---------- Previous post was at 02:06 PM ----------
Also, if you find that it doesn't recognize the sim card, make sure you flash the KitKat bootstack.
Click to expand...
Click to collapse
if is allready unlocked why rommanager cant install twrp?
Don't use rom manager. Flash TWRP manually using fastboot or use flashify.
Help
"Forgive me maybe I ask for help in the wrong place"
Hello!
I have a D415 T-MOBILE
According to this procedure I act
.According to the restart guide
And again the wire stays in "LG"
Thanks.........
Related
Hi,
I hvae HTC ONE after trying to install custom rom and they didn't work (status 7) but now I can't load the system it automatically boot into recovery mode, also I can't factory rest in fastboot menu. plz help
Thread moved.
You have to download a custom rom like Viper or ARHD. Notice that you have to get the right recovery to flash diffrent roms. When using ARHD you have to use TRWP 2.6.3.3 recovery!
So make sure you are using the right recovery.
Some custom roms need to flash the boot.img via command prompt / terminal
Boachti said:
You have to download a custom rom like Viper or ARHD. Notice that you have to get the right recovery to flash diffrent roms. When using ARHD you have to use TRWP 2.6.3.3 recovery!
So make sure you are using the right recovery.
Some custom roms need to flash the boot.img via command prompt / terminal
Click to expand...
Click to collapse
Thank you for your replay, Now I lost root on my recovery I can't do anything it says unable plz help
Please be more precise
Your bootloader is still unlocked?
You aren't able to acces into recovery or what ?
What rom do you currently have installed ?
And which recivery have you now installed ?
---------- Post added at 10:06 AM ---------- Previous post was at 09:57 AM ----------
http://www.joe0.com/2013/10/07/htc-one-how-to-re-root-after-4-3-ota-update/
This can help you
Boachti said:
Please be more precise
Your bootloader is still unlocked?
You aren't able to acces into recovery or what ?
What rom do you currently have installed ?
And which recivery have you now installed ?
---------- Post added at 10:06 AM ---------- Previous post was at 09:57 AM ----------
http://www.joe0.com/2013/10/07/htc-one-how-to-re-root-after-4-3-ota-update/
This can help you
Click to expand...
Click to collapse
I unlocked bootloader and Installed HD Revolution HD but after finishing the rom it says:
You lose Root, do you want to fix?
1. No
2. Yes fix
and I accidentally clicked No,
now I can't do anything in recovery because I don't have root permission and I can not load into normal system because it will restart into recovery.
Ok so it always reboot into recovery
---------- Post added at 10:35 AM ---------- Previous post was at 10:28 AM ----------
Flash your custom recovery again
Download the latest twrp recovery
http://techerrata.com/browse/twrp2/m7
This should fix it
---------- Post added at 10:43 AM ---------- Previous post was at 10:35 AM ----------
If you get asked again than chose this time yes ^^
Boachti said:
Ok so it always reboot into recovery
---------- Post added at 10:35 AM ---------- Previous post was at 10:28 AM ----------
Flash your custom recovery again
Download the latest twrp recovery
http://techerrata.com/browse/twrp2/m7
This should fix it
---------- Post added at 10:43 AM ---------- Previous post was at 10:35 AM ----------
If you get asked again than chose this time yes ^^
Click to expand...
Click to collapse
yes, now I did rebootRUU and it change to
relocked security warning tampered
what should i do?
Unlock the bootloadee again with a new unlock.bin
So you have to redo the process at http://www.htcdev.com/bootloader/
You have to use the new unlock.bin that you will receive from htcdev
Boachti said:
Unlock the bootloadee again with a new unlock.bin
So you have to redo the process at http://www.htcdev.com/bootloader/
You have to use the new unlock.bin that you will receive from htcdev
Click to expand...
Click to collapse
... no need to get unlock code again. the old one will also work fine ...
Devilish_Angel said:
... no need to get unlock code again. the old one will also work fine ...
Click to expand...
Click to collapse
No I had the situation where it didn't work
Boachti said:
No I had the situation where it didn't work
Click to expand...
Click to collapse
... well i doubt that. but its the strange world. isnt it ? ...
Devilish_Angel said:
... well i doubt that. but its the strange world. isnt it ? ...
Click to expand...
Click to collapse
Anyway it doeasn't matter ^^
Unlocked my phone and everything was fine. Then tried installing the 5.1 update and something got messed up there...
My phone is stuck on the "Google logo unlocked icon screen" and will not boot.
I've tried the factory reset, installing a stock image via Flash-All, clearing cache, etc. Nothing fixes it.
Any ideas here?
leesfer said:
Unlocked my phone and everything was fine. Then tried installing the 5.1 update and something got messed up there...
My phone is stuck on the "Google logo unlocked icon screen" and will not boot.
I've tried the factory reset, installing a stock image via Flash-All, clearing cache, etc. Nothing fixes it.
Any ideas here?
Click to expand...
Click to collapse
Try flashing stock image the old fashioned way, and do check that your bootloader and radio version match with the android version you're using
Yasharkhan said:
Try flashing stock image the old fashioned way, and do check that your bootloader and radio version match with the android version you're using
Click to expand...
Click to collapse
If I do a flash-all using the stock LRX22C then it should include the correct bootloader and radio, right?
leesfer said:
If I do a flash-all using the stock LRX22C then it should include the correct bootloader and radio, right?
Click to expand...
Click to collapse
No, do not downgrade your bootloader.
---------- Post added at 07:45 PM ---------- Previous post was at 07:44 PM ----------
And do not relock your bootloader.
---------- Post added at 07:47 PM ---------- Previous post was at 07:45 PM ----------
From fastboot:
fastboot format cache
fastboot format userdata
Okay, I've reinstalled stock 5.1 step-by-step via fastboot rather than flash-all and everything seems to be working okay now.
I see now that flash-all was giving some missing file errors that I missed
Hello guys,
this is my first thread and I have a serious problem:
First, I unlock the bootloader and flash TWRP on it. It seems working, because every time it's booting there comes a message, that I can't trust this device, cause it's unlocked.
The problem is, when i go in fastboot mode, it says "FRP locked") and in the dev-options I can't change the setting (oem unlock). Now when its connected with PC (fastboot Mode), and I try everytime to flash Data there is this error: "FAILED (remote: Command not allowed)"
So...I format all data with TWRP (no OS anymore). Now I know there is no custom ROM for this device out. I was totally fckd up.
I download the update.zip (Stock Rom update) from another Thread and unpack boot.img, recovery.img and system.img from update.app (cause I don't know how to flash it otherwise).
I tried to flash every 3 img. data with TWRP - only the boot.img and recovery.img was installed. Now my device is Bricked because of Im stupid.
So I can only try to flash data with holding vol+ and vol- and power. I also tried eRecovery, but everytime, I tells me that there was a problem by downloading the package.
The fastboot mode is useless, cause there is this bug (read above).
Can you tell me, is there a method to flash update.zip, or another way, or is this device totally broken?
Thanks!!:crying:
Which firmware you had before brick?
MobileTechArena said:
Which firmware you had before brick?
Click to expand...
Click to collapse
I think it was the EMUI 5.0.1 Version (newest) with Android 7.0
70X1C said:
I think it was the EMUI 5.0.1 Version (newest) with Android 7.0
Click to expand...
Click to collapse
PRA-LX1?
MobileTechArena said:
PRA-LX1?
Click to expand...
Click to collapse
Exacly
70X1C said:
Exacly
Click to expand...
Click to collapse
Download here rescue system file, restore that in TWRP. Then flash stock.boot.img via fastboot flash boot boot.stock.img command , then you can update to B110 OTA.
---------- Post added at 04:18 PM ---------- Previous post was at 04:15 PM ----------
To make TWRP to find rescue files, first backup recovery or something in TWRP, then TWRP will make new folder with backup files that you can raplace with files from rescue system.
MobileTechArena said:
Download here rescue system file, restore that in TWRP. Then flash stock.boot.img via fastboot flash boot boot.stock.img command , then you can update to B110 OTA.
---------- Post added at 04:18 PM ---------- Previous post was at 04:15 PM ----------
To make TWRP to find rescue files, first backup recovery or something in TWRP, then TWRP will make new folder with backup files that you can raplace with files from rescue system.
Click to expand...
Click to collapse
The problem is, that I flash the stock recovery on the device (I have no TWRP anymore)
And there is this problem with fastboot..(read above)
70X1C said:
The problem is, that I flash the stock recovery on the device (I have no TWRP anymore)
And there is this problem with fastboot..(read above)
Click to expand...
Click to collapse
Then try to put UPDATE.APP into dload and do Force update.
70X1C said:
The problem is, that I flash the stock recovery on the device (I have no TWRP anymore)
And there is this problem with fastboot..(read above)
Click to expand...
Click to collapse
Is you FRP locked? Try to unlock bootloader again, fastboot oem unlock "your unlock code". Then try to flash TWRP again. Don't bother with Dload and forced update as that doesn't work.
MobileTechArena said:
Is you FRP locked? Try to unlock bootloader again, fastboot oem unlock "your unlock code". Then try to flash TWRP again. Don't bother with Dload and forced update as that doesn't work.
Click to expand...
Click to collapse
I have no idea of the cause, but dload never worked for me too.
This only works if you can boot to Android and Developer Options menu opens for you (if they don't you'll end up with bricked device).
Boot into the Fastboot mode and relock your device (Command: "fastboot oem relock (unlock code)" ).
Then you'll be able to unlock the OEM Lock from the Developer Options menu. (And after it you can go back to Fastboot and unlock the bootloader again to reinstall the TWRP).
You still need help?
MobileTechArena said:
Download here rescue system file, restore that in TWRP. Then flash stock.boot.img via fastboot flash boot boot.stock.img command , then you can update to B110 OTA.
---------- Post added at 04:18 PM ---------- Previous post was at 04:15 PM ----------
To make TWRP to find rescue files, first backup recovery or something in TWRP, then TWRP will make new folder with backup files that you can raplace with files from rescue system.
Click to expand...
Click to collapse
Where exactly is the rescue system file? I can't seem to find it
theholycutu said:
Where exactly is the rescue system file? I can't seem to find it
Click to expand...
Click to collapse
Looks like they removed it from that site. If i find it somewhere i will share it.
.
MobileTechArena said:
Looks like they removed it from that site. If i find it somewhere i will share it.
.
Click to expand...
Click to collapse
Thanks a lot
theholycutu said:
Where exactly is the rescue system file? I can't seem to find it
Click to expand...
Click to collapse
https://mega.nz/#!k0MzQL5T!yHj-2n9DuGvb-ZdsemOgw4k3vQTMy7CJXIGFAhJlplo
Sorry I have seen the thread just before.
Please let me know when you downloaded it. I'll take it out again.
ChinHon said:
https://mega.nz/#!k0MzQL5T!yHj-2n9DuGvb-ZdsemOgw4k3vQTMy7CJXIGFAhJlplo
Sorry I have seen the thread just before.
Please let me know when you downloaded it. I'll take it out again.
Click to expand...
Click to collapse
I downloaded it thanks a lot
:good:
please help me. i also have a bricked p8 lite 2017. but i can boot into. TWRP,fastboot,system upgrade
---------- Post added at 10:15 PM ---------- Previous post was at 10:08 PM ----------
man i also have a bricked p8 lite 2017, did you solve your problem? help me please
EXE bahotin said:
please help me. i also have a bricked p8 lite 2017. but i can boot into. TWRP,fastboot,system upgrade
---------- Post added at 10:15 PM ---------- Previous post was at 10:08 PM ----------
man i also have a bricked p8 lite 2017, did you solve your problem? help me please
Click to expand...
Click to collapse
I get ERROR: 255 and I have tried a lot of options and still haven't got to any solutions.. still attempting to solve it, too
I have the single sim version, i unlock the bootloader and install trwp, after i boot to trwp and allow sistem read, i canot boot any more the phone enters in a bootloop, i need some help, to get it back, and install trwp and get it working.
riper2510 said:
I have the single sim version, i unlock the bootloader and install trwp, after i boot to trwp and allow sistem read, i canot boot any more the phone enters in a bootloop, i need some help, to get it back, and install trwp and get it working.
Click to expand...
Click to collapse
After unlocking bootloader, you need to flash patched kernel of your phone version, else it will be bootlooped. First find out the DRM fixed patched kernel of the version you have, then flash it using fastboot commands with a computer. It just take a couple of minutes only. Patched ketnel is available for most of the versions in this page only. search for it.
---------- Post added at 10:08 AM ---------- Previous post was at 10:06 AM ----------
[email protected] said:
After unlocking bootloader, you need to flash patched kernel of your phone version, else it will be bootlooped. First find out the DRM fixed patched kernel of the version you have, then flash it using fastboot commands with a computer. It just take a couple of minutes only. Patched ketnel is available for most of the versions in this page only. search for it.
Click to expand...
Click to collapse
Check this thread for more information & help: Link
[email protected] said:
After unlocking bootloader, you need to flash patched kernel of your phone version, else it will be bootlooped. First find out the DRM fixed patched kernel of the version you have, then flash it using fastboot commands with a computer. It just take a couple of minutes only. Patched ketnel is available for most of the versions in this page only. search for it.
---------- Post added at 10:08 AM ---------- Previous post was at 10:06 AM ----------
Check this thread for more information & help: Link
Click to expand...
Click to collapse
Thanks i done it yesterday what i do?
flash stock flashtool with all wipe selection.
rebuild the kernel with drm off and patched.
test the kernel
flash the kernel with fastboot
flash trwp with fastboot
form there flash the lastest version of supersu
and voila that is
[email protected] said:
After unlocking bootloader, you need to flash patched kernel of your phone version, else it will be bootlooped. First find out the DRM fixed patched kernel of the version you have, then flash it using fastboot commands with a computer. It just take a couple of minutes only. Patched ketnel is available for most of the versions in this page only. search for it.
---------- Post added at 10:08 AM ---------- Previous post was at 10:06 AM ----------
Check this thread for more information & help: Link
Click to expand...
Click to collapse
Do you know if i can install ota ?
I am new and I don't have much experience in custom rom, recovery, kernel etc. and I think I was wrong in some procedure.
I have a problem with my Moto E5 XT1944-3, I wanted to install the TWRP by following these steps:
https://forum.xda-developers.com/moto-e5/development/recovery-twrp-3-2-3-x-moto-e5-plus-t3912189
(I have the bootloader unlocked)
The inconvenience came when I restarted in recovery mode and the touch did not work (only in recovery mode), which led me to flash again twrp-x.x.x.x.img but still the same. What I ventured on the Internet to find solutions and simplifying, I ended up flashing the recovery img as follows: fastboot flash boot twrp-x.x.x.x.img (I guess the problems started there)
*The E5 did not turn on with the logo and did not start the OS, I tried to use the Lenovo tool to restore the E5 and it says that it is not compatible (maybe because of the unlocked bootloader) although it allowed you the option to search for it within the "compatible" smartphones . I tried from the fastboot tool to try to revive the E5 but it does not start the system. Nor does he let me use: fastboot erase system / data / recovery; to try to make a clean installation.
* The last thing I try is to reinstall the TWRP and try to use the USB-OTG with the mause, but, although it has electricity, the mause does not appear and if the screen is turned off and then on again it remains blank forcing me to a forced restart.
* Oh and download an AOSPEXTENDED ROM and install the img with fastboot and it didn't load the logo but the boot animation but it was just a loop
* Any idea what to do?
* I think that if the recovery worked correctly, I could solve this.
Greetings from Argentina using the google translator :dedos cruzados:
Did you flash the correct recovery? Your phone is the Moto E5 Nora variant
---------- Post added at 07:08 PM ---------- Previous post was at 07:04 PM ----------
And the command is like this:. fastboot flash recovery xxxxxc.bin
---------- Post added at 07:10 PM ---------- Previous post was at 07:08 PM ----------
Dont use fastboot flash boot or you will overwrite the bootloader
loco72 said:
Dont use fastboot flash boot or you will overwrite the bootloader
Click to expand...
Click to collapse
And fastboot flash bootloader... did you forgot? And remember, NEVER EVER use fastboot erase bootloader, as it will brick your device.