PHP:
I welcome, help with 1650-02, it does not flash, not through rsdlite, and even fasboot .. it just reboots .... it worked fine, but I had to bypass the FRP and I used some kind of program, after which a cyclic reboot appeared
Related
My moto z before using RSD lite flash NPL 25.86-30, then OTA updated to NPL25.86-30.3. It seems that bootloarder is also updated. now I want to re-use RSD lite to flash NPL25.86-30. But RSD has shown an error in flashing GPT.bin, show "FAIL"
Who can help me?:crying:
You can't go back, if the Bootloader got updated.
jump the step of flashing gpt by editing the xml file(delete the line)
Now my device have a very strange question, if I use the battery mod, is unable to shutdown, automatically enter the bootloarder. Do not use the module can shutdown, but the connection charger will automatically enter the bootloarder,can not be charged in the shutdown state.
Sorry,my english is bad.
rakee said:
Now my device have a very strange question, if I use the battery mod, is unable to shutdown, automatically enter the bootloarder. Do not use the module can shutdown, but the connection charger will automatically enter the bootloarder,can not be charged in the shutdown state.
Sorry,my english is bad.
Click to expand...
Click to collapse
start fastboot in the cmd and start the following command
fastboot oem fb_mode_clear
this should solve your bootlader at reboot issue...
treibstoff said:
start fastboot in the cmd and start the following command
fastboot oem fb_mode_clear
this should solve your bootlader at reboot issue...
Click to expand...
Click to collapse
Its work for me,thanks man!:highfive::highfive:
treibstoff said:
start fastboot in the cmd and start the following command
fastboot oem fb_mode_clear
this should solve your bootlader at reboot issue...
Click to expand...
Click to collapse
After the last OTA (july) update has failed, I got an issue very similar, but in my case, everytime I restart or turn off the device, it gets to twrp recovery and I need do restart it on fastboot mode then choose START on side menu to get boot properly. Can you help?
hi, I have a p760 that I use as backup phone.
Today I try to power on it and I had security error, so I don't remember what I did with this phone, and I follow THIS guide.
The problem is that
adb oem-unlock
Click to expand...
Click to collapse
doesn't exist. 'cause
HTML:
adb reboot oem-unlock
is the only one that works.
If I give the command adb reboot oem-unlock the phone gives me a black screen with Secure booting unsuccessful.
I try to go in s/w update mode but kzd crash.
So I think that the only way is to unlock the bl, insta cwm and install a custom rom. but how?
can someone help me?
some people with the same problem?
funny ...
Hi to all,
I have a question about my device.
I hope that I have posted this correctly; if not please accept my apologies.
I have a Letv Le 2 Pro X620. This has the MTK CPU (not snapdragon).
The phone had the stock ROM on it with EUI and it got the updates.
In the last update about a month ago, Google Service stopped working; and I therefore wanted to flash a different ROM on to fix that; as well as to finally get rid of the chinese apps which annoyed me.
SO I downloaded a ROM from XDA https://forum.xda-developers.com/le-2/development/rom-lligera-t3538654 (thanks).
The device was unrooted and had the stock recovery.
I used the basic adb and fastboot command prompt applications. I already enabled developer mode in the phone and had also enabled debugging and unlocking boot loader.
In the adb/fastboot I entered the command to unlock "fastboot oem unlock" and "fastboot oem unlock go". IT would confirm and complete and then I went onto flash the recovery.
HERE IS WHERE THINGS DIDNT GO AS EXPECTED.
And I ended up doing this multiple times (i.e oem unlocking, and flashing recovery)
I tried using TWRP twrp-3.2.1-0-s2; and also downloaded a pack "Le2RootMegaPack" which had Letv-X620-Twrp-3.0.2-0 .
IT would complete successfully; but on reboot I would get an error message like "Orange State. Your phone can not be trusted" (this is not the exact message but close to it).
The message only seemed to come once as if I restarted it would disappear.
When I went back to fastboot it would say locked until i did over the fastboot oem unlock command (in other words I had to unlock everytime).
Also when I go to reboot; something about "Lock" would come in the command prompt statuses just before it rebooted.
It seems like the bootloader kept getting locked again.
So I could not boot into TWRP.
I then tried using the "fastboot boot xx.img" command which after several attempts and variations worked.
I flashed the Letv-X620-Twrp-3.0.2-0 and then "fastbook boot" booted from ANOTHER version of TWRP (as it would not boot using that same TWRP).
Then when the phone was about to restart I held up the volume up button and it booted to TWRP.
(That recovery (which I booted from) was from the ROM LeEco+x620+CM13+Rom+v145+by+Kangburra which I also downloaded from XDA.)
However the touch screen wouldnt work and I had to use a USB mouse (using the adaptors/OTG cable) and was able to control the phone in the TWRP.
I wiped the dalvik and cache and loaded the rom and it completed. then it asked to reboot which i did; and then it just wouldnt start.
The present status is that there is nothing on the Phone. I cannot boot to recovery nor to fastboot.
The only reaction I get from the phone is if I plug in a USB cable (charger). I have it plugged into the PC and the PC sound for when a device is plugged in and the sound for when a device is plugged out plays rapidly within 2-3 seconds (ie it connects/disconnects quickly).
The adb/fastboot commands do NOT work. The computer does not include it in devices etc.
I would therefore be grateful if I can have some assistance. I would like the phone to work again (obviously).
Thank you for your time.
Ok, i'm stuck on the bootloader screen.
I've tried every single thing ik. I've tried to reinstall the stock room but EVERY TIME the mFastBoot returns FAILURE for every process, I can even unlock the bootloader since >fastboot oem get_unlock_data returns "Could not get unlock data!" .
All this thing happened after one update that I've received and downloaded.
What should I do now to fix the fastboot?
Thanks for your time =)
I flashed havoc os had some issues , tried restoring from my backup, got caught in a bootloop so i used lgup to flash a kdz and it worked.but now my enable oem unlock is turned off and it is greyed out. What can i do.
Mohammedbi said:
I flashed havoc os had some issues , tried restoring from my backup, got caught in a bootloop so i used lgup to flash a kdz and it worked.but now my enable oem unlock is turned off and it is greyed out. What can i do.
Click to expand...
Click to collapse
The same thing happens to me, I have not found much info about this, I hope you can help us.
Mohammedbi said:
I flashed havoc os had some issues , tried restoring from my backup, got caught in a bootloop so i used lgup to flash a kdz and it worked.but now my enable oem unlock is turned off and it is greyed out. What can i do.
Click to expand...
Click to collapse
I already found the solution, but it will erase your data.
with the adb commands you must restart the device in boorloader mode:
adb reboot bootloader
Then when I take you to the bootloader screen what you have to write next:
fastboot oem lock
(Remember the phone will be erased)
then to restart the device you have to:
fastboot reboot
And the device will reboot.
what you do is lock it, so that you can then unlock it in a simple way.
(If you do not know what the ADB is, warn man), I hope it helps you and those who enter here too :good:
@l3dson: Be careful before relocking the bootloader: The phone MUST be 100% stock or you will have a brick.
@Mohammedbi: Your bootloader is still unlocked, even after flashing the KDZ. It's just the newly flashed ROM doesn't know it, and you don't need it to.
Just go to fastboot (PowerOff, Vol- while plugging in cable) and flash TWRP. Follow ChazzMatt's root guide for the initial TWRP steps.
Have anyone found the solution for this problem...
vino90m said:
Have anyone found the solution for this problem...
Click to expand...
Click to collapse
What exactly is not working?
ADB doesn't require Enable OEM Unlock to be set. Just plug it in and ADB away - unless drivers or cable or port aren't working.
And your bootloader is still unlocked if it was unlocked before you flashed stock Oreo. You should be able to enter fastboot using the steps described in the post just before yours.
Edit: Of course you have to enable USB debugging in order to use ADB. I'm sure you knew that
l3dson said:
I already found the solution, but it will erase your data.
with the adb commands you must restart the device in boorloader mode:
adb reboot bootloader
Then when I take you to the bootloader screen what you have to write next:
fastboot oem lock
(Remember the phone will be erased)
then to restart the device you have to:
fastboot reboot
And the device will reboot.
what you do is lock it, so that you can then unlock it in a simple way.
(If you do not know what the ADB is, warn man), I hope it helps you and those who enter here too :good:
Click to expand...
Click to collapse
hey i have this same problem and been asking around... but the adb reboot command will not work because it says the phone must be "enabled oem unlock" mode before you can use adb commands... which is greyed out..so back to square one... how to enable it?? any suggestions on this??