Related
My wife's Nexus 7 is on the 4.13 bootloader. I've tried to change it before to no avail. I tried to use Wug's kit to flash the latest 4.4.2(coming from the 66Y build) but I got the error on the bootloader flash. So everything got wiped but the bootloader and left an empty device. All attempts to flash after that failed to get past the first line(erasing boot), I guess 'cause it was already erased? I flashed the individual img' s(boot, system, etc) and got the Nexus to boot up into kit Kat 4.4.2, but there is this little glitch in between the "google" splash screen and the boot animation where I can see recovery flash for a split second. I want to flash the proper bootloader and redo the process clean, but for the life of me I can't get the bootloader to take. I flash in Wug's, the same way I flashed the other img's, but fastboot screen still shows 4.13. Adb shows connected but says "offline" next to device, which is making the adb reboot command fail(unless I'm done now something else wrong there). Can anyone help? My wife is not pleased.
Sent from my SCH-I535 using Tapatalk
Your wife is displeased because of a momentary flash of the screen while booting? **
Or maybe she's displeased with the idea of you fooling with her tablet and that's the only straw to grasp at?
You need to say exactly what the error is, not "an error occurred". You can cut-n-paste right here into your posts.
Also, you should verify the checksum (e.g. MD5) of the bootloader image file you are attempting to flash to make sure you are really using a valid bootloader file.
(In particular, the one shipped in the KOT49H = 4.4.2 factory image is corrupted)
Note [WARNING][URGENT] N7 grouper (2012 WiFi) bootloader .img files from Google
Honestly, I would avoid flashing your bootloader unless it was absolutely, positively necessary. It's the riskiest flashing operation that you could possibly perform on your tablet. Unless I missed something, you didn't really indicate anything else was particularly wrong with the tablet.
good luck
** I think I saw a bug report about fleeting screen flashes in KitKat 4.4.2 (you see an "old" screen briefly appear when you are on your way to doing something else; they are quite noticeable because they are "out of sequence"). For instance I've seen my settings screen appear momentarily when I am moving between two running apps. I think I saw this reported as a KitKat bug - not something due to the bootloader.
.
Well, bootloader now says 4.23, but I still get the invalid state error when flashing the latest kit kat img. Is there a way to force request an OTA? The 4.4.2 OTA failed because I was on a custom rom/recovery, but now it seems to say I am up-to-date even if I downgrade. Is there a way to clear the memory or get the OTA to attempt?
How do you flash? Using a toolkit? Fastboot? ADB? On what operating system? What is the error message and at what step does occur?
It's a bit difficult to give suggestions how to solve a problem when one has only little information.
If you have a 4.23 bootloader installed, flashing boot.img and system.img is sufficient to get a running system, I.e.
Fastboot flash boot boot.img
Fastboot flash system system.img
While boot.img and system.img are extracted from the factory image, but without having detailed information ...
Sent from my Nexus 7 using xda app-developers app
I tried to update using Wug's NTK in fastboot. I got an "invalid state" error when it was flashing bootloader during 4.4.2 return to stock process, and that part fails. I've read this problem has to do with the current bootloader. So I flashed back to the V build and everything flashes fine in NTK. But I get the error again trying to flash stock and unroot to 4.4.2. So I flashed just the boot and system img files in NRK and it's running 4.4.2 now, but I can't flash it in Wug's the normal way. I've read others have solved this error but I haven't been able to.
Sent from my SCH-I535 using Tapatalk
jackdubl said:
I tried to update using Wug's NTK in fastboot. I got an "invalid state" error when it was flashing bootloader during 4.4.2 return to stock process, and that part fails. I've read this problem has to do with the current bootloader. So I flashed back to the V build and everything flashes fine in NTK. But I get the error again trying to flash stock and unroot to 4.4.2. So I flashed just the boot and system img files in NRK and it's running 4.4.2 now, but I can't flash it in Wug's the normal way. I've read others have solved this error but I haven't been able to.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
It may be that the file is corrupt, but it could also mean that your usb port is faulty. Try plugging it in on a different usb port.
First suggestion: try to avoid any toolkit
Second suggestion: get familiar with fastboot
Third suggestion: try to use a decent OS, i.e. Linux / OS X
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
First suggestion: try to avoid any toolkit
Second suggestion: get familiar with fastboot
Third suggestion: try to use a decent OS, i.e. Linux / OS X
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I thought I mentioned that I couldn't get adb to reboot into the bootloader because device said "offline" so I couldn't run in fastboot. The toolkit lets you flash in fastboot without using adb so that's how I flashed the system and boot. I'll just leave it the way it is. Seems to run fine and no slow charging issue.
Sent from my SCH-I535 using Tapatalk
Excuse me, but adb and fastboot are two completely different things ...
Btw. You can boot your device into bootloader (fastboot) mode by pressing vol-down + power while booting it.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Excuse me, but adb and fastboot are two completely different things ...
Btw. You can boot your device into bootloader (fastboot) mode by pressing vol-down + power while booting it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I know that part. But how do you enter the commands after that?
Sent from my SCH-I535 using Tapatalk
Hi all,
Sorry if this is covered elsewhere but I cannot find it.
I successfully installed the May 2016 updates and now I am trying to get root back. I followed the usual steps for installing TWRP
Code:
adb reboot-bootloader
fastboot flash recovery .\recovery\twrp-3.0.2-0-clark.img
fastboot reboot
No errors seen...
Now if I try to reboot into recovery I get the "No command" page. If I then follow the power button and volume up keypress sequence, I am taken to the original recovery and not TWRP.
Any clues what I am doing wrong? I tried this several times today and no joy (yet all the other updates, I have had no problem getting TWRP and root installed).
Thanks.
user7743 said:
Hi all,
Sorry if this is covered elsewhere but I cannot find it.
I successfully installed the May 2016 updates and now I am trying to get root back. I followed the usual steps for installing TWRP
No errors seen...
Now if I try to reboot into recovery I get the "No command" page. If I then follow the power button and volume up keypress sequence, I am taken to the original recovery and not TWRP.
Any clues what I am doing wrong? I tried this several times today and no joy (yet all the other updates, I have had no problem getting TWRP and root installed).
Thanks.
Click to expand...
Click to collapse
You have to immediately boot into TWRP after flashing or the system will overwrite it with the stock recovery.
Sent from my XT1575 using XDA Labs
Thanks for that. Exactly the hint I needed.
Question
Would you mind telling me what steps you took to get the May update? It's so small that I'm reluctant to do anything major to get it and I'm debating on whether to just flash the stock recovery to give that a try, or whether I'm going to have to flash the unrooted image I've saved using TWRP, then flash stock recovery, then get the OTA. Seems like a lot of work for a tiny update.
user7743 said:
Hi all,
Sorry if this is covered elsewhere but I cannot find it.
I successfully installed the May 2016 updates and now I am trying to get root back. I followed the usual steps for installing TWRP
Code:
adb reboot-bootloader
fastboot flash recovery .\recovery\twrp-3.0.2-0-clark.img
fastboot reboot
No errors seen...
Now if I try to reboot into recovery I get the "No command" page. If I then follow the power button and volume up keypress sequence, I am taken to the original recovery and not TWRP.
Any clues what I am doing wrong? I tried this several times today and no joy (yet all the other updates, I have had no problem getting TWRP and root installed).
Thanks.
Click to expand...
Click to collapse
Marnina said:
Would you mind telling me what steps you took to get the May update? It's so small that I'm reluctant to do anything major to get it and I'm debating on whether to just flash the stock recovery to give that a try, or whether I'm going to have to flash the unrooted image I've saved using TWRP, then flash stock recovery, then get the OTA. Seems like a lot of work for a tiny update.
No errors seen...
Now if I try to reboot into recovery I get the "No command" page. If I then follow the power button and volume up keypress sequence, I am taken to the original recovery and not TWRP.
Any clues what I am doing wrong? I tried this several times today and no joy (yet all the other updates, I have had no problem getting TWRP and root installed).
Thanks.
Click to expand...
Click to collapse
If you have modified the system in any form, such as using Xposed, then OTA will fail. If the system image is stock that has never been rooted, in theory you should have no issues with stock recovery installed. The OTA is the May security update. Whether you feel it is necessary or not is up to you.
I can't get any further than unlocked bootloader I get no command after trying to get straight into twrp after flash and always goes to factory recovery if that will even boot is there a secret way to boot into recovery directly after twrp flash cause I've been trying for days and days what is going on is there a way to root without twrp first please help it's the main reason I bought this damn thing
Sent from my XT1575 using XDA-Developers mobile app
Sherrillface said:
I can't get any further than unlocked bootloader I get no command after trying to get straight into twrp after flash and always goes to factory recovery if that will even boot is there a secret way to boot into recovery directly after twrp flash cause I've been trying for days and days what is going on is there a way to root without twrp first please help it's the main reason I bought this damn thing
Sent from my XT1575 using XDA-Developers mobile app
Click to expand...
Click to collapse
Don't run the last command:
fastboot reboot
Select to reboot into recovery from the menu. If you're getting No command, you may need to flash the stock recovery then reboot the recovery. You should have the menu back. Flash TWRP and reboot into recovery to start TWRP.
HTH
Ooms
Sherrillface said:
I can't get any further than unlocked bootloader I get no command after trying to get straight into twrp after flash and always goes to factory recovery if that will even boot is there a secret way to boot into recovery directly after twrp flash cause I've been trying for days and days what is going on is there a way to root without twrp first please help it's the main reason I bought this damn thing
Click to expand...
Click to collapse
1. Periods, dude. Where are they?
2. Flash TWRP again.
3. In TWRP, mount /system (Advanced > Mount > system), and delete:
/system/etc/install-recovery.cfg
/system/etc/recovery-resource.dat
/system/recovery-from-boot.p
Click to expand...
Click to collapse
or add the .bak extension to the filenames.
/system/etc/install-recovery.cfg.bak
/system/etc/recovery-resource.dat.bak
/system/recovery-from-boot.p.bak
Click to expand...
Click to collapse
4. Reboot straight back into TWRP (Reboot > Recovery) to make sure TWRP sticks.
Can't get into twrp at all tried fastboot reboot and tried recovery mode directly after flash that's the whole issue just says no command upon trying to enter twrp directly after twrp.img flash.
Sent from my XT1575 using XDA-Developers mobile app
---------- Post added at 06:09 AM ---------- Previous post was at 06:08 AM ----------
Says flash successful but I don't think it truly is
Sent from my XT1575 using XDA-Developers mobile app
Sherrillface said:
Can't get into twrp at all tried fastboot reboot and tried recovery mode directly after flash that's the whole issue just says no command upon trying to enter twrp directly after twrp.img flash.
Sent from my XT1575 using XDA-Developers mobile app
---------- Post added at 06:09 AM ---------- Previous post was at 06:08 AM ----------
Says flash successful but I don't think it truly is
Sent from my XT1575 using XDA-Developers mobile app
Click to expand...
Click to collapse
Sounds like it's not flashing... what is your bootloader state? Try to start it with fastboot boot recovery.img command.
acejavelin said:
Sounds like it's not flashing... what is your bootloader state? Try to start it with fastboot boot recovery.img command.
Click to expand...
Click to collapse
Got it a while ago wrong windroid version.
Sherrillface said:
Got it a while ago wrong windroid version.
Click to expand...
Click to collapse
Umm... OK... No offense to @Rapscallion16 but why are you using a generic toolkit on the Moto X??? It has been mentioned many times that using one click tools and other toolkits is not safe with this and most newer Moto devices, doing it manually is pretty simple.
Anyway, glad you got it working. Enjoy...
Hello,
I tried to root my Zenfone 2 ZE500KL but i didn't see that the method don't work with Android 6. Now, when I start my phone i have the message "ERROR: Can't load invalid boot image" with the ASUS Logo.
I tried a lot of things using ADB, like go to the recovery mode for format, installing from the ROM again from my SD. But the message stay...
I need your help now, car I don't find anything... Thanks !
CzeroXCI said:
Hello,
I tried to root my Zenfone 2 ZE500KL but i didn't see that the method don't work with Android 6. Now, when I start my phone i have the message "ERROR: Can't load invalid boot image" with the ASUS Logo.
I tried a lot of things using ADB, like go to the recovery mode for format, installing from the ROM again from my SD. But the message stay...
I need your help now, car I don't find anything... Thanks !
Click to expand...
Click to collapse
Download this boot.img for Marshmallow v.13.10.7.1
https://drive.google.com/file/d/0B7F3ZXr565GkV2N3WjBoeEZXUUU/view?usp=drivesdk
The command from fasboot mode:
fastboot flash boot boot.img
Muminek111 said:
Download this boot.img for Marshmallow v.13.10.7.1
https://drive.google.com/file/d/0B7F3ZXr565GkV2N3WjBoeEZXUUU/view?usp=drivesdk
The command from fasboot mode:
fastboot flash boot boot.img
Click to expand...
Click to collapse
My phone version is 13.10.10.34 can I flash this boot image????
Sharashchandra said:
My phone version is 13.10.10.34 can I flash this boot image????
Click to expand...
Click to collapse
You need to boot.img from stock rom v 13.10.10.34.
Stock rom you can download from Asus website and then extract boot.img from this stock rom.
Sharashchandra said:
My phone version is 13.10.10.34 can I flash this boot image????
Click to expand...
Click to collapse
Plz help I used twrp v2.8.7.7seven max then
Its booted and showing in modified partition.ileave it as it is and I just backup the system but after backup when I press reboot system it will just freezed .then manually I switched on its showing "ERROR: Can't load invali boot image" two phones are under same condition plz help me its my friends phone.
Help me as fast as possible
---------- Post added at 01:13 PM ---------- Previous post was at 01:11 PM ----------
Muminek111 said:
You need to boot.img from stock rom v 13.10.10.34.
Stock rom you can download from Asus website and then extract boot.img from this stock rom.
Click to expand...
Click to collapse
Plz help I used twrp v2.8.7.7seven max then
Its booted and showing in modified partition.ileave it as it is and I just backup the system but after backup when I press reboot system it will just freezed .then manually I switched on its showing "ERROR: Can't load invali boot image" two phones are under same condition plz help me its my friends phone.
Help me as fast as possible
Sharashchandra said:
Plz help I used twrp v2.8.7.7seven max then
Its booted and showing in modified partition.ileave it as it is and I just backup the system but after backup when I press reboot system it will just freezed .then manually I switched on its showing "ERROR: Can't load invali boot image" two phones are under same condition plz help me its my friends phone.
Help me as fast as possible
---------- Post added at 01:13 PM ---------- Previous post was at 01:11 PM ----------
Plz help I used twrp v2.8.7.7seven max then
Its booted and showing in modified partition.ileave it as it is and I just backup the system but after backup when I press reboot system it will just freezed .then manually I switched on its showing "ERROR: Can't load invali boot image" two phones are under same condition plz help me its my friends phone.
Help me as fast as possible
Click to expand...
Click to collapse
I don't understand what your problem.
For Marshmallow use this TWRP.
https://drive.google.com/file/d/0B7F3ZXr565GkY28yUjhfRkd5MUk/view?usp=drivesdk
Another possibility how to fix your phone is flash stock rom from stock recovery. It's the easiest way.
Muminek111 said:
I don't understand what your problem.
For Marshmallow use this TWRP.
https://drive.google.com/file/d/0B7F3ZXr565GkY28yUjhfRkd5MUk/view?usp=drivesdk
Another possibility how to fix your phone is flash stock rom from stock recovery. It's the easiest way.
Click to expand...
Click to collapse
After flashing also the same problem persists
Thankyou
Sharashchandra said:
After flashing also the same problem persists
Thankyou
Click to expand...
Click to collapse
Do you tried to flash Asus stock rom v.13.10.10.34(1.4gb) from Asus stock recovery v.13.10.10 34. I don't mean flash from TWRP.
Hello M having ASUS ZenFone 2 laser ze550kl model with marshmallow version.. I tried to unlock boot loader but m unable to do so.. Please help me..
just flash this zip https://yadi.sk/d/0NFnYyTG36XzWv using TWRP recovery(in menu "install").
just flash this..
it works perfectly fine
make sure you use the latest TWRP for your device.
Hey bro you can watch this video and follow the steps then your phone will definitely right back.....
https://youtu.be/_Ca10N-XQJk
I have also this problem .
But i can't enter in the recovery menu , it doesn't work.
P.S. sorry for my english
Muminek111 said:
Do you tried to flash Asus stock rom v.13.10.10.34(1.4gb) from Asus stock recovery v.13.10.10 34. I don't mean flash from TWRP.
Click to expand...
Click to collapse
Well, i can feel some doubt in your post...but h*ll yeah! I'm currently facing the same problem; where flashing stock rom, downloaded from their site, using their stock recovery, adb, and adb sideload....
the rom flashes successfully, but still boots with the same error...To be frank, i'm fed up...and almost about giving up on this phone...
-i believe i'll give it another shot this very night, trying different methods...funny ones though; if and when they work, i will definitely update my post again... my phone version is Z00ED, in case anybody cares to know -
UPDATE:
=======
Aaaaaanyway, I downloaded 2 kinds of stock roms from the Asus official site;
1. UL-ASUS_Z00E-WW-13.1010.1612.53-user (the latest:- M) and...
2. UL-ASUS_Z00E-WW-12.8.5.222-user (and older version:- actually, the pre-installed version)
after flashing the first one over and over again; after and before wiping my phone and cache over and over again, NOTHING HAPPENED; no change!!! still kept throwing back the error message.
So I decided to flash the second one, and for a split second, I was happy cos the error had disappear...only for me to wait for eternity and in vain for the phone to boot (that is, even if it could). suddenly, I realized what had happen....the phone couldn't boot pass the ASUS logo, neither could it load recovery again (as it used to). It only boots into ADB, but of course, that will require USB DEBUG MODE to be ON to be able for the phone to be detected through ADB (which is far from possible due to the numerous wipes I performed).
CURRENT SITUATION: I can't ADB, I can't get into recovery, and I'm stacked with the logo at boot......when the phone is completely turned off and placed on charge, the battery shows an empty battery with the loading (status) sign (but it charges, even without the OS being able to display the process).
Don't know whether anyone is facing same, or I can start a new thread with this? and I need help before taking it to a 3rd party repairs (since we don't hv Asus customer care in our country yet).
Will be glad to find help.
PS: The computer still detects the phone as an ADB Android device, and to me, that's a beacon of hope.
abodan09 said:
Well, i can feel some doubt in your post...but h*ll yeah! I'm currently facing the same problem; where flashing stock rom, downloaded from their site, using their stock recovery, adb, and adb sideload....
the rom flashes successfully, but still boots with the same error...To be frank, i'm fed up...and almost about giving up on this phone...
-i believe i'll give it another shot this very night, trying different methods...funny ones though; if and when they work, i will definitely update my post again... my phone version is Z00ED, in case anybody cares to know -
Click to expand...
Click to collapse
This problem will resolve to open the bootloader.
Muminek111 said:
This problem will resolve to open the bootloader.
Click to expand...
Click to collapse
I don't think I got that...do u mind explaining further??? thank you!
abodan09 said:
I don't think I got that...do u mind explaining further??? thank you!
Click to expand...
Click to collapse
You can not flash the older version stock rom from stock recovery.
Flash latest stock rom.
Download this twrp: https://drive.google.com/file/d/0B7F3ZXr565GkY28yUjhfRkd5MUk/view?usp=drivesdk
Download this ulock bootloader: https://drive.google.com/file/d/0B7F3ZXr565GkMWNwUkZJa1BUVUU/view?usp=drivesdk
Download this supersu: https://drive.google.com/file/d/0B7F3ZXr565GkOTcxb2VPbmQzT2M/view?usp=drivesdk
Restart to fasboot mode.
Command: fastboot boot twrp.img
From twrp flash first zip ulock bootloder then flash zip supersu.
Reboot.
---------- Post added at 08:39 PM ---------- Previous post was at 08:15 PM ----------
Android 6
Must be first opened bootloader then can modified boot image.
Same ERROR,you just need to flash the unlock bootloader file
UnlockBL.zip
Click to expand...
Click to collapse
https://goo.gl/nVq9e7
i have installed new firmware on my zenfone laser 2 (ze500kl),but when restarts it says error cant load invalid boot image...then i fastbooted boot.img..but when i restarts the phone it again shows the errror...
pls help me..
christin7 said:
i have installed new firmware on my zenfone laser 2 (ze500kl),but when restarts it says error cant load invalid boot image...then i fastbooted boot.img..but when i restarts the phone it again shows the errror...
pls help me..
Click to expand...
Click to collapse
Test:
Try to flash boot.img of your firmware version from fastboot mode but use command: fastboot boot boot.img. Reboot system. Then let me know.
So my VS995 (Verizon LG V20) is stuck in a fastboot loop. I can't do anything outside of fastboot. I got to after step 3 in the Dirty Santa root method and could not get the phone to boot into TWRP recovery. I kept getting an ADB device offline error and could not get ADB to see my device to initiate the "ADB reboot recovery command".
In a stupid and drunk state I did a "fastboot erase system" and thats what locked me into the fastboot loop.
Any help is appreciated as my V20 is now unusable :crying:.
I guess I would need a stock boot image, and stock recovery to get back to where I started. If anyone could point me in the right direction and help me get my phone back (and possibly rooted), I would be more than happy to donate via PayPal .
P.S. The LGUP software used in the how to restore v20 thread linked-> ( https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903) does not recognize the model of device giving the error ("you have to select a known model, please")
Kevin_xail said:
So my VS995 (Verizon LG V20) is stuck in a fastboot loop. I can't do anything outside of fastboot. I got to after step 3 in the Dirty Santa root method and could not get the phone to boot into TWRP recovery. I kept getting an ADB device offline error and could not get ADB to see my device to initiate the "ADB reboot recovery command".
In a stupid and drunk state I did a "fastboot erase system" and thats what locked me into the fastboot loop.
Any help is appreciated as my V20 is now unusable :crying:.
I guess I would need a stock boot image, and stock recovery to get back to where I started. If anyone could point me in the right direction and help me get my phone back (and possibly rooted), I would be more than happy to donate via PayPal .
P.S. The LGUP software used in the how to restore v20 thread linked-> ( https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903) does not recognize the model of device giving the error ("you have to select a known model, please")
Click to expand...
Click to collapse
Use this thread https://forum.xda-developers.com/v20/development/vs995-kdz-t3527538
If you have verizon VS995
Follow the procedure in the thread https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903
download these
VS99512A_06_1114_ARB00.kdz
lg-firmwares.com/download-file/?fileId=4889
https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
LGUP_Store_Frame_Ver_1_14_3_3.msi http://downloads.codefi.re/autoprime/LG/LG_G5/LGUP
LGMobileDriver_WHQL_Ver_4.1.1.exe http://downloads.codefi.re/autoprime/LG/LG_G5/LGMobileDriver_WHQL_Ver_4.1.1.exe
I was able to flash the appropriate stock .kdz file (THANKS dwertz!) but my phone immediately boots right back into FastBoot Mode
Do I need a stock Boot.img file?
I can communicated with the device through the PC's terminal using fastboot. Are there any fastboot commands I could try to boot into the stock firmware I just flashed? Are there any partitions I need to erase or format?
Any help is appreciated!
Kevin_xail said:
I was able to flash the appropriate stock .kdz file (THANKS dwertz!) but my phone immediately boots right back into FastBoot Mode
Do I need a stock Boot.img file?
I can communicated with the device through the PC's terminal using fastboot. Are there any fastboot commands I could try to boot into the stock firmware I just flashed? Are there any partitions I need to erase or format?
Any help is appreciated!
Click to expand...
Click to collapse
to my understanding, the kdz file contains the stock boot.img and stock system.img, everything to bring the device completely back to stock .
In fastboot to boot to the system the command is "fastboot reboot"
dwertz said:
to my understanding, the kdz file contains the stock boot.img and stock system.img, everything to bring the device completely back to stock .
In fastboot to boot to the system the command is "fastboot reboot"
Click to expand...
Click to collapse
After flashing the stock .kdz firmware for the VS995 fastboot is no longer working and giving me the error FAILED (remote: unknown command).
My phone can not get past FastBoot! :crying: I think I really bricked this thing now. My bootloader is locked, fastboot commands don't work at all.
The only thing that does work is download mode (holding volume up and plugging phone in) and I am able to flash the vs995 firmware from the lg website but i STILL can't boot into anything but fastboot.
Does anyone have any suggestions as to what I can try to fix this thing. I think i'm doomed. I may try to flash the stock us996 firmware because at this point it seems like it wont get any worse.
Any help would be appreciated!
Kevin_xail said:
After flashing the stock .kdz firmware for the VS995 fastboot is no longer working and giving me the error FAILED (remote: unknown command).
My phone can not get past FastBoot! :crying: I think I really bricked this thing now. My bootloader is locked, fastboot commands don't work at all.
The only thing that does work is download mode (holding volume up and plugging phone in) and I am able to flash the vs995 firmware from the lg website but i STILL can't boot into anything but fastboot.
Does anyone have any suggestions as to what I can try to fix this thing. I think i'm doomed. I may try to flash the stock us996 firmware because at this point it seems like it wont get any worse.
Any help would be appreciated!
Click to expand...
Click to collapse
did you ever get any help? I would go directly to the dirty santa thread and make your issue known. I'm not sure how much help I could give you but if no one else is willing to help I can try.
Kevin_xail said:
After flashing the stock .kdz firmware for the VS995 fastboot is no longer working and giving me the error FAILED (remote: unknown command).
My phone can not get past FastBoot! :crying: I think I really bricked this thing now. My bootloader is locked, fastboot commands don't work at all.
The only thing that does work is download mode (holding volume up and plugging phone in) and I am able to flash the vs995 firmware from the lg website but i STILL can't boot into anything but fastboot.
Does anyone have any suggestions as to what I can try to fix this thing. I think i'm doomed. I may try to flash the stock us996 firmware because at this point it seems like it wont get any worse.
Any help would be appreciated!
Click to expand...
Click to collapse
Did you flash the kdz using Uppercut?
imucarmen - I can't post in the dirty santa thread because I am a new member to XDA (been coming here for years just never made an account )
bond32 - Yes I was able to flash the .kdz using Uppercut+LGUP but my problem is not fixed. My phone still boots right to FastBoot Mode in the "Locked State" to where I can't issue any commands or alter any partitions.
This makes no sense to me if LGUP is able to 100% flash the stock firmware, WHY CAN'T I GET OUT OF FASTBOOT! Lol
Does anyone have any ideas as to what I could try to unbrick this thing?
I know it's a different issue from the one that I had, but the LG Support Tool method that KedarWolf posted might help solve this issue too.
https://forum.xda-developers.com/showpost.php?p=70337463&postcount=5
Splinter 77 - Thank you for the suggestion. I have been trying to get this tool to work for a couple hours and everytime it hangs on the Downloading Firmware section. No matter what I try I can't get it to download the firmware....
Does anyone have some ideas I can try? I'm up for anything at this point!
Kevin_xail said:
Does anyone have some ideas I can try? I'm up for anything at this point!
Click to expand...
Click to collapse
Did you try pulling the battery, put the battery back in.
Hold the volume down and power button at same time. When the lg logo shows up let go of the power button but continue to hold the volume down and press the power button again. It will bring you to a screen tgat has 2 questions. Answer yes to both of them. Then reboot. I believe that resets the way the phone boots almost like resetting a cmos
Sent from my VS995 using XDA-Developers Legacy app
im in the same boat now... ugh
---------- Post added at 06:01 PM ---------- Previous post was at 05:56 PM ----------
ahh i got it man! @Kevin_xail
i dont know if this will help seince u relocked, but do the factory reset dance
hold the vol down and power and put in battery as soon as its on click the power button and re hold it. it will get to recovery, it took me hours but its there.
I had tried that a few times after reading about it but I'll try now for an extended period of time and see if I can activate it. I'll report back with what happens, thanks for the tip dwertz and Team DevDigitel
Well I got in to the recovery menu and reset to factory settings and wipe cache (the only two options) but I still am booting right into FastBoot and can't escape!
I even flashed the stock .kdz again after the factory reset and wiping cache and I'm still stuck in FastBoot
Any other suggestions to try?
Kevin_xail said:
Well I got in to the recovery menu and reset to factory settings and wipe cache (the only two options) but I still am booting right into FastBoot and can't escape!
I even flashed the stock .kdz again after the factory reset and wiping cache and I'm still stuck in FastBoot
Any other suggestions to try?
Click to expand...
Click to collapse
When you have a unlocked boot loader and you do a factory reset, I believe it wipes the OS from the phone giving you no OS. If you can get back to recovery, flash this rom https://forum.xda-developers.com/v20/development/vs995-vzw-nrd90m-modded-notsostock-rom-t3525864
That will at least get you booted so you can flash the kdz.
I can't get into any kind of recovery to flash a rom though
Kevin_xail said:
I can't get into any kind of recovery to flash a rom though
Click to expand...
Click to collapse
How long ago did you get the phone?
Bricked with locked Bootloader on fastboot
Splinter77 said:
I know it's a different issue from the one that I had, but the LG Support Tool method that KedarWolf posted might help solve this issue too.
https://forum.xda-developers.com/showpost.php?p=70337463&postcount=5
Click to expand...
Click to collapse
I was bout ready to give up, got it working with newest lg up and stock flash file from lg support website, I haven't seen a whole lot (any) solved posts so I thought I would share. At least got it working again, rooted is another story.
Kevin_xail said:
Well I got in to the recovery menu and reset to factory settings and wipe cache (the only two options) but I still am booting right into FastBoot and can't escape!
I even flashed the stock .kdz again after the factory reset and wiping cache and I'm still stuck in FastBoot
Any other suggestions to try?
Click to expand...
Click to collapse
Same problem here, did you ever fix it?
Hello,
I've installed a twrp recovery file on my oneplus 6t recently, and for some reason after trying to boot up the OS this frozen "bootloader is unlocked" screen appears. It won't go away! The screen turns black for a second after holding down the volume up+power button, but then goes back to the "bootloader is unlocked" screen again. Draining the battery doesn't help either.
Any ideas on how to fix this?
You probably have to MSMTool it but you could try activating your other partition.
Code:
fastboot --set-active=a
Or
Code:
fastboot --set-active=b
You didn't give much info on what happened exactly. We dig the technical details on here!
Wrapped with delicious Fajita [emoji896]
FiWe20 said:
Hello,
I've installed a twrp recovery file on my oneplus 6t recently, and for some reason after trying to boot up the OS this frozen "bootloader is unlocked" screen appears. It won't go away! The screen turns black for a second after holding down the volume up+power button, but then goes back to the "bootloader is unlocked" screen again. Draining the battery doesn't help either.
Any ideas on how to fix this?
Click to expand...
Click to collapse
Is your phone the T-Mobile or International version?
If International, have a look at this thread and see if the issue you are facing is similar to mine. The solution posted by Mannan Qamar further down the thread is what solved the issue for me, and I've detailed the solution step by step in the latest post in that thread.
Timmmmaaahh said:
You probably have to MSMTool it but you could try activating your other partition.
Code:
fastboot --set-active=a
Or
Code:
fastboot --set-active=b
You didn't give much info on what happened exactly. We dig the technical details on here!
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
Thanks for replying!
For some reason after days of desperately trying to fix it, the 6t it suddenly booted into fastboot after being battery-drained. I am not experienced in rooting at all but I think this stuck "bootloader is unlocked" issue happened when I installed the twrp file via the "flash boot_a" instead of the "flash recovery".
FAILED (remote: '(recovery_a) No such partition')
comes up when using the normal "flash recovery".
So the flashing is the main problem I guess. Is there any other way to install twrp?
FiWe20 said:
Thanks for replying!
For some reason after days of desperately trying to fix it, the 6t it suddenly booted into fastboot after being battery-drained. I am not experienced in rooting at all but I think this stuck "bootloader is unlocked" issue happened when I installed the twrp file via the "flash boot_a" instead of the "flash recovery".
FAILED (remote: '(recovery_a) No such partition')
comes up when using the normal "flash recovery".
So the flashing is the main problem I guess. Is there any other way to install twrp?
Click to expand...
Click to collapse
You need to boot TWRP first as there is no recovery partition to flash to (hence the error). From there, you can flash a TWRP installer as explained in the TWRP thread. If you're not knowledgeable or have doubts about the topic then I strongly recommend in reading thoroughly before taking any actions.
Alternatively, you can flash from within Magisk Manager when you get the boot image right as explained in my previous post here. That can be a bumpy ride though! You've been warned
Just note that, with Android 10 (if that is your goal), the safest option is having root without TWRP recovery. If you're sticking with Android Pie, just ignore these last two paragraphs.
Timmmmaaahh said:
You need to boot TWRP first as there is no recovery partition to flash to (hence the error). From there, you can flash a TWRP installer as explained in the TWRP thread. If you're not knowledgeable or have doubts about the topic then I strongly recommend in reading thoroughly before taking any actions.
Alternatively, you can flash from within Magisk Manager when you get the boot image right as explained in my previous post here. That can be a bumpy ride though! You've been warned
Just note that, with Android 10 (if that is your goal), the safest option is having root without TWRP recovery. If you're sticking with Android Pie, just ignore these last two paragraphs.
Click to expand...
Click to collapse
I tried "fastboot boot twrp.img" before but then the next issue comes up...
Sending 'boot.img' (31136 KB) OKAY [ 0.667s]
Booting FAILED (remote: 'unknown command')
FiWe20 said:
I tried "fastboot boot twrp.img" before but then the next issue comes up...
Sending 'boot.img' (31136 KB) OKAY [ 0.667s]
Booting FAILED (remote: 'unknown command')
Click to expand...
Click to collapse
Are you on Android 10? Because in that case this is expected behaviour or in sweet dev terms: by design. OOS Android 10 Beta 1 doesn't allow TWRP for some reason. You can only get it by fastboot flashing a patched boot image or via a Magisk flash. You also need some luck because in both cases it can fail miserably. On top of that, you need some old keymaster to be able to access any files. It's all a true joyride for now, lol...
---------- Post added at 02:18 PM ---------- Previous post was at 02:14 PM ----------
Wait, "fastboot boot twrp.img" gives you "Sending 'boot.img'"? That can't be. Enlighten us on version numbers first please.
Timmmmaaahh said:
Are you on Android 10? Because in that case this is expected behaviour or in sweet dev terms: by design. OOS Android 10 Beta 1 doesn't allow TWRP for some reason. You can only get it by fastboot flashing a patched boot image or via a Magisk flash. You also need some luck because in both cases it can fail miserably. On top of that, you need some old keymaster to be able to access any files. It's all a true joyride for now, lol...
---------- Post added at 02:18 PM ---------- Previous post was at 02:14 PM ----------
Wait, "fastboot boot twrp.img" gives you "Sending 'boot.img'"? That can't be. Enlighten us on version numbers first please.
Click to expand...
Click to collapse
Its interesting because I managed to get TWRP working the first time and if I remember correctly it was via the "flash boot_a" command. And yes it was through the Open Beta version of Android 10. I think this whole "bootloader is unlocked" problem was caused after rebooting from twrp.
How do you fastboot flash a patched boot image if flashing a normal boot image cause errors? I really appreciate you taking your time on this.
---------
Fastboot version 29.0.4-587166
FiWe20 said:
Its interesting because I managed to get TWRP working the first time and if I remember correctly it was via the "flash boot_a" command. And yes it was through the Open Beta version of Android 10. I think this whole "bootloader is unlocked" problem was caused after rebooting from twrp.
How do you fastboot flash a patched boot image if flashing a normal boot image cause errors? I really appreciate you taking your time on this.
Click to expand...
Click to collapse
There could be many reasons; Android works in mysterious ways. The "bootloader is unlocked" screen shows the minute you.. well, unlock your bootloader (fastboot oem unlock)
The fact that it freezes is simply because it finds something to boot but it fails to do so, which could be either an OS or a recovery. I've been there as well but forcing a restart with power+volume buttons did fix it for me (different situation of course, it was months ago).
Trust me, experiencing these annoying situations is the best way to learn more about your device. Before you know it you'll be playing around with fastboot, adb, recoveries, ROMs, kernels and mods like a pro.
Timmmmaaahh said:
There could be many reasons; Android works in mysterious ways. The "bootloader is unlocked" screen shows the minute you.. well, unlock your bootloader (fastboot oem unlock)
The fact that it freezes is simply because it finds something to boot but it fails to do so, which could be either an OS or a recovery. I've been there as well but forcing a restart with power+volume buttons did fix it for me (different situation of course, it was months ago).
Trust me, experiencing these annoying situations is the best way to learn more about your device. Before you know it you'll be playing around with fastboot, adb, recoveries, ROMs, kernels and mods like a pro.
Click to expand...
Click to collapse
Booting OS doesn't work(-> "freeze screen"), recovery mode doesn't work(-> also freeze) and installing new recovery files won't work either because it's in the beta version of android 10. So my 6t is completely broken unless twrp releases an open beta android 10 version of their recovery file?
FiWe20 said:
Booting OS doesn't work(-> "freeze screen"), recovery mode doesn't work(-> also freeze) and installing new recovery files won't work either because it's in the beta version of android 10. So my 6t is completely broken unless twrp releases an open beta android 10 version of their recovery file?
Click to expand...
Click to collapse
Great. What did you do this time? lol. I thought you had it working. Not to worry, you can always resort to the MSMtool (found here). But before you do, there's a few 'softer' methods you can try. I advise reading the first post of this thread.
One piece of advice: if at all possible, try avoiding locking the bootloader again. It serves no purpose and can only create more problems. I have to admit that I haven't used MSMtool myself (been quite lucky so far) but I'm guessing it locks the bootloader in its automated process. If there's a switch to prevent that, use it! If not, ah well...
Timmmmaaahh said:
Great. What did you do this time? lol. I thought you had it working. Not to worry, you can always resort to the MSMtool (found here). But before you do, there's a few 'softer' methods you can try. I advise reading the first post of this thread.
One piece of advice: if at all possible, try avoiding locking the bootloader again. It serves no purpose and can only create more problems. I have to admit that I haven't used MSMtool myself (been quite lucky so far) but I'm guessing it locks the bootloader in its automated process. If there's a switch to prevent that, use it! If not, ah well...
Click to expand...
Click to collapse
Nah. It locks the Bootloader. Meaning if something went wrong you can't do anything. Happened to one guy here but I guess that was cause he erased persist. Another thing about MSM is that it only flashes One Slot.
Mannan Qamar said:
Nah. It locks the Bootloader. Meaning if something went wrong you can't do anything. Happened to one guy here but I guess that was cause he erased persist. Another thing about MSM is that it only flashes One Slot.
Click to expand...
Click to collapse
That's why I referred to the 'softer' methods, sometimes just switching partition slots can solve all your problems.
FiWe20 said:
Booting OS doesn't work(-> "freeze screen"), recovery mode doesn't work(-> also freeze) and installing new recovery files won't work either because it's in the beta version of android 10. So my 6t is completely broken unless twrp releases an open beta android 10 version of their recovery file?
Click to expand...
Click to collapse
MSM tool and stop suffering
FiWe20 said:
Booting OS doesn't work(-> "freeze screen"), recovery mode doesn't work(-> also freeze) and installing new recovery files won't work either because it's in the beta version of android 10. So my 6t is completely broken unless twrp releases an open beta android 10 version of their recovery file?
Click to expand...
Click to collapse
Msm tool dude