Develop Bugs

[GUIDE] Unlocking (& Re-locking) the Motorola Xoom for flashing

The following will VOID your warranty but will easily unlock the Xoom for fast software flashes using a custom recovery and will allow flashing root files or manipulated system files on to your current software installation.
This will ERASE your Xoom.
1) Get the Motorola USB drivers MOTODEV > Documentation & Tools > USB Drivers (you need to sign up on their but maybe you can google this and find it as well)
2) Get the Android SDK Android SDK | Android Developers (you only really need the fastboot executable file for your host OS)
2.5) - I will soon put together a windows pack for usb drivers & fastboot so you don't have to download all this stuff just to do one task.
3) Power off your Xoom
4) Press and hold the volume down button while pressing the power button
Even after the Xoom turns back on keep it pressed down and you'll see some starting fastboot protocol text on the top left of the screen.
5) Open a command window in your sdk\tools folder (not platform tools and depending on when you get the SDK you may need to copy over some DLL files)
6) type:
fastboot oem unlock
Click to expand...
Click to collapse
7) read the warning on your Xoom's screen, hit volume up if you wish.
You're now free to put whatever data you want on your tablet. Cheers.
-- To RE-LOCK your Xoom, boot in to fastboot, and on your computer (from the tools folder):
fastboot oem lock
Click to expand...
Click to collapse
Read this warning:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You actually have to read the warning and understand it - If you have modified your Xoom's software outside of the user space you won't be able to successfully re-lock your device. You'll have to restore it back to 100% factory, which you can do here: http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard (The Verizon Wireless stock software).

This wouldn't negate the free LTE upgrade would it?

I'm not sure. I'd say you should re-lock the boot loader and restore any custom stuff to factory before you send it back in though.

I'm curious, what are the hardware ids in the usb driver when the xoom is in fastboot? Is the usb driver that is active while it's in fastboot called something like single adb device?
Thanks!
Sent from my MB860 using XDA App

How do you relock it?
Sent from my HTC Vision using Tapatalk

Wow, that has to be the easiest unlock I have ever seen. Does this mean we will not have to install something like Amon's RA Recovery to flash ROMs whenever people get a chance to make them?
Also, if we issue a fastbook oem lock (or whatever the proper command is), can we then send it in for repairs? in other words, is there some history on the device that says I unlocked it?

youareme7 said:
I'm curious, what are the hardware ids in the usb driver when the xoom is in fastboot? Is the usb driver that is active while it's in fastboot called something like single adb device?
Thanks!
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Windows first found it as fastboot, then I got the moto driver from their dev site and I didn't look what it was called after that. I think a Moto composite device or something, I'm pretty sure it installed 3 drivers. I will double check when I'm back home.
djunio said:
How do you relock it?
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
I'm not sure but I would say "fastboot oem lock" should probably work. - What I am really curious about is if fastboot oem unlcok writes something to the tablet somewhere that lets Moto/VZW know it was unlocked.
padanfain said:
Wow, that has to be the easiest unlock I have ever seen. Does this mean we will not have to install something like Amon's RA Recovery to flash ROMs whenever people get a chance to make them?
Also, if we issue a fastbook oem lock (or whatever the proper command is), can we then send it in for repairs? in other words, is there some history on the device that says I unlocked it?
Click to expand...
Click to collapse
We'll still need a custom recovery to make life easier, but after you unlock it you can push any files/images to wherever you want.
The unlock screen makes you agree to the fact you're voiding your warranty. I'm not sure if re-locking it will be enough and I'd venture to speculate that there should be a difference between a hardware fail and software fail for warranty work. I guess we'll see.

thefredelement said:
This will ERASE your Xoom.
Click to expand...
Click to collapse
What does this mean? Does unlocking the device wipe everything, or just wipe data/cache? Is system effected just by executing this, or are you referring to the flash process?

mikejs78 said:
What does this mean? Does unlocking the device wipe everything, or just wipe data/cache? Is system effected just by executing this, or are you referring to the flash process?
Click to expand...
Click to collapse
It's a factory reset.

i know this was the same unlock for Nexus One, but will this give us root? has anyone attempted to install SuperUser.apk and su?

koush has just tried this and did not unlock bootloader. was this done on a consumer device or developer's device?

socomdark said:
koush has just tried this and did not unlock bootloader. was this done on a consumer device or developer's device?
Click to expand...
Click to collapse
A consumer device.
Is he using the right moto dev drivers and fastboot from the 3.0 sdk?

socomdark said:
koush has just tried this and did not unlock bootloader. was this done on a consumer device or developer's device?
Click to expand...
Click to collapse
I just saw his tweet, he was trying to boot a kernel from fastboot it looks like.

thefredelement said:
I just saw his tweet, he was trying to boot a kernel from fastboot it looks like.
Click to expand...
Click to collapse
yea but it looks like he has got clockwork mod on there.

If we void the warranty what happens to the return policy? store.motorola.com 's return policy to be specific

confused
Am i supposed to hold down the volume key the whole time while I'm clicking the fastboot command. I'm a little confused if anyone help understand

You just hold down the volume down key and power button until the white fastboot protocol text appears.

cant get it
thefredelement said:
You just hold down the volume down key and power button until the white fastboot protocol text appears.
Click to expand...
Click to collapse
ok done that but when it will not open in command prompt http://media.xda-developers.com/images/smilies/mad.gif. i think i will jus give up cause something not right.. The command prompt jus pops up and immediately goes away...but thanks for the help i jus wait for the thunderbolt and root it....lol big ups to all whom do and to KOUSH!!!! that brotha is awesome

No big deal here, you have to open the command prompt properly.
If you're on windows7, then browse to the folder in windows explorer, right click on the folder and select open command window here
In windowsXP go to start, run, type in cmd and then cd to the directory where the file is located.

I just purchased a Xoom, has anyone tried to issue the fastboot OEM lock command to see if it will indeed relock the device?

[BOOT] FIREFIREFIRE 1.2 - bootloader with recovery selection

This is a replacement bootloader so you can get into recovery with just the one power button. It's very simple to use, just turn on the Fire, and when the logo pops up press the power button.
FIREFIREFIRE also makes fastboot easy. For a few seconds on every boot, fastboot is enabled; no idme bootmode or special cable needed. The USB ID is changed to one that's supported by even the oldest fastboots. Unlike the stock, you do not need to use the "-i 0x1949" on every run of fastboot.
Now FIREFIREFIRE can fix your partition tables. "fastboot oem format" will overwrite the partition table with the stock table. You can use this to revert to factory partitioning if you have been messing with parted or the like, or can be used with the USB boot kit (Rekindle) to manually rebuild a totally bricked Fire. Running this command on 1.0 or earlier will fail.
Release notes:
1.2 - MD5: a8c8d702606de8ab7e73b898de50b4b6 u-boot.bin
Merge in 6.2->6.2.1 changes: low battery charge safety shutdown, official offsets for NVRAM params
The power LED now tells you more stuff: dim slightly while in fastboot / ready to detect recovery button press, bright green again when the boot of standard OS starts, more orangey orange when recovery starts
Fix Amazon's broken LED code
1.1 - MD5: 7a4f1a2ff60b13a3534df318f99d813c u-boot.bin
Fixed the built-in partitioning to match the partition map on a stock KF
Removed USB PID version. Realized this would screw up Windows. VIDID will always be 18d1:0100 from now on
1.0
Fastboot USB VID switched to Google's VID. Once this is installed you don't need to use "-i 0x1949" on every fastboot command
USB PID reflects the version. 0x0100 is version 1.0, 0x0402 is 4.2, etc
0.9
New logo with "press power button for recovery" message at the bottom
Delays ~10 seconds if no button pressed, but pushing the button immediately goes into recovery
During the delay, you can connect with fastboot. Works under Linux, but the delay may be too short for Windows
Howto flash
The TWRP installer flashes FFF 1.0 when it's run. For most purposes this is ok, but because TWRP has been orphaned, I can't recommend it as a way to get the latest. By the time you read this, KFU should support flashing FFF, and for Windows users is by far the easiest way.
Howto flash by hand
Get into fastboot mode somehow. Having and older FFF from the TWRP installer is a good start. Currently KFU or fbmode is the easiest
flash with "fastboot -i 0x1949 flash bootloader u-boot.bin" (take out "-i 0x1949" if FFF is already installed)
disable fastboot: "fastboot -i 0x1949 oem idme bootmode 4000"
reboot: "fastboot -i 0x1949 reboot"
Howto backup EVERYTHING (on Linux):
(not relevant in this post anymore, but good reference)
This will back up all partitions and the hidden NVRAM data. If you ever have to restore from scratch, you can get fastboot to write a new partition table and then fastboot in these backups
Need >8GB local free, and adb installed and able to get a shell.
Make a new directory to store the dump files and cd into it.
Make sure that your KF is running adb as root. As of 6.2.1 this requires running BurritoRoot, then "adb root" on your PC after it completes.
Then run in a terminal:
Code:
for F in `seq 1 12`; do adb pull /dev/block/mmcblk0p$F; done
adb shell idme ? > nvram.txt
On a brand new KF, this backup will bzip2 down to ~300MB. Once you start writing to the flash, this will go up even if you delete files due to nonempty free blocks.
github is now up at https://github.com/pokey9000/kf_u-boot

So will this still work with 6.2? I'm confused. Anyway, this is awesome! Just what we needed
Sent from my ADR6400L using Tapatalk

Yeah, a boring video of the "factory cable" method since the nvram boot mode is broke would be useful But awesome that it works.

I can't remember what the device was doing before the update but now if I try adb commands for recovery, bootloader, and fastboot, it looks like there is some response. I don't actually get in to recovery but it looks like maybe the device is rebooting in to fastboot. I don't have a ton of experience with this but just figured it was worth mentioning.

SikYou said:
So will this still work with 6.2? I'm confused. Anyway, this is awesome! Just what we needed
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
I just need to debug it. For some reason even the u-boot that comes with the 6.2 source drop doesn't respect the new NVRAM layout. This is just a proof of concept since TWRP is still AWOL, so don't worry. I plan to make the button handling a little more robust, including a way to select recovery or fastboot with just the button so you can ditch the Fire ROM altogether.

SikYou said:
I can't remember what the device was doing before the update but now if I try adb commands for recovery, bootloader, and fastboot, it looks like there is some response. I don't actually get in to recovery but it looks like maybe the device is rebooting in to fastboot. I don't have a ton of experience with this but just figured it was worth mentioning.
Click to expand...
Click to collapse
I noticed that too. I tried building the u-boot from the 6.2 source drop and it doesn't detect when I set the bootmode either, but the one in the update .bin does.

pokey9000 said:
I just need to debug it. For some reason even the u-boot that comes with the 6.2 source drop doesn't respect the new NVRAM layout. This is just a proof of concept since TWRP is still AWOL, so don't worry. I plan to make the button handling a little more robust, including a way to select recovery or fastboot with just the button so you can ditch the Fire ROM altogether.
Click to expand...
Click to collapse
Sounds great, looking forward to seeing the finished product.
Sent from my Kindle Fire using Tapatalk

Xeddicus said:
Yeah, a boring video of the "factory cable" method since the nvram boot mode is broke would be useful But awesome that it works.
Click to expand...
Click to collapse
There you go.

BTW, have you been in touch with agrabren from TWRP? He is the one kinda spearheading the KF TWRP project and I think one of the issues was not having a reliable method for booting to recovery; if that is the case you have obviously done a lot of work towards solving that problem.
Sent from my Kindle Fire using Tapatalk

This is awesome!
Not trying to nitpick, but is there a way to add on-screen options or no?

death2all110 said:
This is awesome!
Not trying to nitpick, but is there a way to add on-screen options or no?
Click to expand...
Click to collapse
Maybe at some point. I'm just trying to get something that works for now. With one button there isn't much benefit imho other than a message that says "press button now for recovery"

pokey9000 said:
Maybe at some point. I'm just trying to get something that works for now. With one button there isn't much benefit imho other than a message that says "press button now for recovery"
Click to expand...
Click to collapse
Well fine then! I see how it is. Just shoot everyone down... jk
Great work man!
But that is what I was thinking, It can either normal boot and get shown a brief message like "Press Power Button again to boot in.to recovery." And if you hit the button again it boots recovery.

death2all110 said:
Well fine then! I see how it is. Just shoot everyone down... jk
Great work man!
But that is what I was thinking, It can either normal boot and get shown a brief message like "Press Power Button again to boot in.to recovery." And if you hit the button again it boots recovery.
Click to expand...
Click to collapse
Thanks
Right now it goes into recovery if you just hold the power button down when turning it on instead of just hitting it quick. I could add a delay and just throw some text at the bottom of the boot logo. Hmm... now that I think about it, how about this:
-Boots up, shows a splash screen with the logo and some text like "hold down power for recovery"
-Listens for fastboot for up to 5 seconds, enough to run fastboot on the commandline real quick
-If it doesn't get a fastboot connection in 5 seconds, it checks the state of the power button
-If the power button is pressed, boot recovery, or else boot normal
Also if anyone has any better logos than what I've got now... Requirements are that most of the screen area must be a single color like the current logo, or the logo won't compress well enough, and must be 600x1024.

pokey9000 said:
Thanks
Right now it goes into recovery if you just hold the power button down when turning it on instead of just hitting it quick. I could add a delay and just throw some text at the bottom of the boot logo. Hmm... now that I think about it, how about this:
-Boots up, shows a splash screen with the logo and some text like "hold down power for recovery"
-Listens for fastboot for up to 5 seconds, enough to run fastboot on the commandline real quick
-If it doesn't get a fastboot connection in 5 seconds, it checks the state of the power button
-If the power button is pressed, boot recovery, or else boot normal
Also if anyone has any better logos than what I've got now... Requirements are that most of the screen area must be a single color like the current logo, or the logo won't compress well enough, and must be 600x1024.
Click to expand...
Click to collapse
I'd be willing to create a cool boot-logo, how would just a flame in the background and some text saying "FireFireFire Bootloader" on top of it?

I dunno if it's just me but once I read the title FIREFIREFIRE I pictured Beavis and Butthead. One day..

MrJandD said:
I'd be willing to create a cool boot-logo, how would just a flame in the background and some text saying "FireFireFire Bootloader" on top of it?
Click to expand...
Click to collapse
I was actually thinking of something getting away from the name of the bootloader since in the scheme of the user experience it's pretty insignificant. Andy with some flames in the background maybe, or a Nook Tablet on fire (yes, i'm that bitter and petty)

Thelgow said:
I dunno if it's just me but once I read the title FIREFIREFIRE I pictured Beavis and Butthead. One day..
Click to expand...
Click to collapse
That's exactly what was going on at 1am... I needed to make a splash screen (Amazon doesn't include the stock one in the source, trademark and all that) and I typed the first thing that popped into my head into the editor.

pokey9000 said:
I was actually thinking of something getting away from the name of the bootloader since in the scheme of the user experience it's pretty insignificant. Andy with some flames in the background maybe, or a Nook Tablet on fire (yes, i'm that bitter and petty)
Click to expand...
Click to collapse
Hard to make a nook tab one color
How about the text FireBoot?
Im open to idea's.

First Edition.
How about this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

MrJandD said:
Hard to make a nook tab one color
How about the text FireBoot?
Im open to idea's.
Click to expand...
Click to collapse
It doesn't have to be one color. The image has to be mostly background and the background must be a solid color. It all has to do with RLE compression, like GIF or faxes where black text on a white page compresses down really small. There's only about 8-10k to spare for the boot splash, so we can't just put up a full screen photo of something or smooth gradients.

Question Bricked OP9pro

Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...

danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
What did you do to try to patch it? Why are you in adb? Does fastboot work?

craznazn said:
What did you do to try to patch it? Why are you in adb? Does fastboot work?
Click to expand...
Click to collapse
Patched the boot.img using magisk and then flashed it. After patching, it totally cant boot and can only boot to bootloader.
tried alot of version of MSMtool and it will always fail with param preload error...
Then tried manually recover via extracting the payload using python then using adbtools to wipe and flash but it will also fail because some img files are unable to flash over to the phone...
Any other solutions?

U not able to flash boot the stock boot.img?

i am able to flash the stock boot.img to the phone but some critical img files will come out with
FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed

You need to be in fastbootd,
Code:
fastboot reboot fastboot

craznazn said:
You need to be in fastbootd,
Code:
fastboot reboot fastbootd
Click to expand...
Click to collapse
Nope not working too...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

danjcxie said:
Nope not working too...
View attachment 5281163
Click to expand...
Click to collapse
Sorry, fastboot reboot fastboot (without the d)

@danjcxie
To be honest, I would download the rom and boot with the recovery image instead, I'll upload the image collection...
Will post a link here once it's up.
Actually, just noticed there isn't a recovery image, so boot to the default boot.img using fastboot, then see if the storage shows on your computer, copy the latest default rom over to the main storage folder then then go into Settings > System > System Updates and use the cog to do a local update using the rom zip.
That should re-install everything back to default, you might get lucky and still have all your data
My collection is for the Europe build FYI:
OP9P_Image_Collection_BA_11.2.3.3.zip | by djsubterrain for OnePlus 9 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
MD5 : 00227014483b4913a2624fac6f492434
So you would reboot the phone into fastboot mode by holding vol up during boot
Once you are in fastboot mode connect the phone to your computer
Test that the computer can see it properly using fastboot devices
You should see a number returned, if so then your computer is recognising the phone, if you don't then try installing the latest drivers from here
If fastboot can see the device properly then copy the default boot.img to the same folder as your fastboot.exe and type the following :
fastboot boot boot.img
You should see a message saying it's transferring it to the phone, then it should boot the phone using it, it's slower than a normal boot but, if everything else on the phone is ok, then you should see it booted and it should accept your lock method
Once you get into the phone using that boot.img, try connecting the phone to your computer and see if it's recognised, if it is then copy over the latest stock rom to your main storage folder, then go to Settings > System > System Updates and use the cog to do a local update using the rom zip
I'm guessing it should let you because it will see a difference between your boot image and the one from the rom.

MSM tool for LE2125 - 11.2.2.2.LE15AA
User Type of Others for login MSM Tool for LE2125 - 11.2.2.2.LE15AA Drivers Mirrors: (provided by @djsubterrain) MSM Tool : https://sourceforge.net/projects/djsubterrain/files/OnePlus 9 Pro/OP9P_MSM_Tool.zip/download MD5 ...
forum.xda-developers.com

New problem... After i did fastboot reboot fastboot, it shows low battery whole day and is unable to charge totally... it has been charging the whole day now and totally cant turn on at all.
it keeps showing the lightning sign in the centre of the circle keeps blinking and dies off

danjcxie said:
New problem... After i did fastboot reboot fastboot, it shows low battery whole day and is unable to charge totally... it has been charging the whole day now and totally cant turn on at all.
it keeps showing the lightning sign in the centre of the circle keeps blinking and dies off
View attachment 5281971
Click to expand...
Click to collapse
Turn it off and try charging it
Also "fastboot reboot fastboot" isn't a valid command, there is an adb command "adb reboot bootloader" but that can only be run from within your rom from when you are in recovery with the phone connected
See here :
Fastboot Commands: A Beginner’s Guide
With this guide of ours, you'll be able to learn all the fastboot commands and their syntax. We've also posted some hidden commands which you never knew.
android.tutorials.how
#To reboot your device
fastboot reboot
#To reboot your device to fastboot mode
fastboot reboot-bootloader
Click to expand...
Click to collapse

djsubterrain said:
Turn it off and try charging it
Click to expand...
Click to collapse
Yup tried. Everytime you just plug in the charging cable, it will just auto boot up and show the charging sign

danjcxie said:
Yup tried. Everytime you just plug in the charging cable, it will just auto boot up and show the charging sign
Click to expand...
Click to collapse
Yeah that symbol isn't what I get, I get a blue lightning sign with the percentage underneath. Are you running OxygenOS or ColorOS?
I think it might be time for you to contact OnePlus support

djsubterrain said:
Turn it off and try charging it
Also "fastboot reboot fastboot" isn't a valid command, there is an adb command "adb reboot bootloader" but that can only be run from within your rom from when you are in recovery with the phone connected
See here :
Fastboot Commands: A Beginner’s Guide
With this guide of ours, you'll be able to learn all the fastboot commands and their syntax. We've also posted some hidden commands which you never knew.
android.tutorials.how
Click to expand...
Click to collapse
Wtf are you talking about. fastboot reboot fastboot is literally the only way to get into fastbootd if you can't get to recovery or boot normally.
Regarding battery, that I'm not sure, hopefully someone can help

craznazn said:
OP
Wtf are you talking about. fastboot reboot fastboot is literally the only way to get into fastbootd if you can't get to recovery or boot normally.
Regarding battery, that I'm not sure, hopefully someone can help
Click to expand...
Click to collapse
OK, firstly, who the hell do you think you're talking to?
Secondly, did you look at the link I posted?

djsubterrain said:
OK, firstly, who the hell do you think you're talking to?
Secondly, did you look at the link I posted?
Click to expand...
Click to collapse
Who the hell are you? Why the hell are you linking "tutorials.how"?
fastboot/fastboot.cpp - platform/system/core - Git at Google
android.googlesource.com
Lines 2178, source tells you to reboot fastbootd by reboot fastboot.
Show me it's not a valid command, go on

craznazn said:
Who the hell are you? Why the hell are you linking "tutorials.how"?
fastboot/fastboot.cpp - platform/system/core - Git at Google
android.googlesource.com
Lines 2178, source tells you to reboot fastbootd by reboot fastboot.
Show me it's not a valid command, go on
Click to expand...
Click to collapse
Go ahead and help the guy solve his problem.
Just remember it's fastboot, not fastbootd.
Now, how do you block people on here again?

danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
use the MSM Tool with the latest drivers
QDLoader HS-USB Driver_64bit_Setup
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com

danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
This just worked for me minutes ago
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
i downloaded Indian Variant LE2121 while my phone is LE2120 ant it worked

VS986 in trouble /solved

Good day everyone!
I have LG G4 VS986 UsU /e/. I took apart and looked at the motherboard - VS986. But my camera hasn't worked for a long time. I tried all the firmwares for USU'd vs986, and the camera did not work on one of them. So I decided to try installing the stock firmware (maybe the camera will work on it).
In general, I started the firmware process, according to this instruction:
[UNLOCK][UNOFFICIAL][G4] Unlock ANY* LG G4 device with UsU
Spoiler: FAQ 28)b)
1. extract with SALT system + boot + modem partition of the stock ROM kdz of your choice (I took this one: VS9862BA_00_0525_ARB02.kdz)
2. flash them in fastboot:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash modem modem.img
3. boot TWRP (if you do not get into TWRP at the first try it gets overwritten. if that happens you must re-flash TWRP in fastboot) - here i am stuck!
4. flash the baseband package of your model
5. factory reset in TWRP (obviously all your data will be lost - so backup before)
6. if you encounter issues FORMAT data in TWRP (obviously all your data will be lost - so backup before)
But got stuck at point 3. The phone cannot boot into TWRP and FASTBOOT, but it can into DOWNLOAD MODE. Does anyone have any options on what to do next and how to fix it?

xDev91 said:
Good day everyone!
I have LG G4 VS986 UsU /e/. I took apart and looked at the motherboard - VS986. But my camera hasn't worked for a long time. I tried all the firmwares for USU'd vs986, and the camera did not work on one of them. So I decided to try installing the stock firmware (maybe the camera will work on it).
In general, I started the firmware process, according to this instruction:
[UNLOCK][UNOFFICIAL][G4] Unlock ANY* LG G4 device with UsU
Spoiler: FAQ 28)b)
1. extract with SALT system + boot + modem partition of the stock ROM kdz of your choice (I took this one: VS9862BA_00_0525_ARB02.kdz)
2. flash them in fastboot:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash modem modem.img
3. boot TWRP (if you do not get into TWRP at the first try it gets overwritten. if that happens you must re-flash TWRP in fastboot) - here i am stuck!
4. flash the baseband package of your model
5. factory reset in TWRP (obviously all your data will be lost - so backup before)
6. if you encounter issues FORMAT data in TWRP (obviously all your data will be lost - so backup before)
But got stuck at point 3. The phone cannot boot into TWRP and FASTBOOT, but it can into DOWNLOAD MODE. Does anyone have any options on what to do next and how to fix it?
Click to expand...
Click to collapse
Fastboot must work. Do you have followed the guide briefly?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When booting into android you can use adb to reboot into fastboot with: adb reboot bootloader
...but the above procedure has to work in any case

Fastboot must work. Do you have followed the guide briefly?
Click to expand...
Click to collapse
Yes, I did. I tried to go in this way too, but it didn't work.
When booting into android you can use adb to reboot into fastboot with: adb reboot bootloader
Click to expand...
Click to collapse
That was the point - Android did not boot completely (showed the installation of applications 1-33, and then rebooted and showed the splash screen).
I was able to start Android later:
I typed it, - I held down all three buttons (volume + and -, and the on / off button) - and licked out the menu with the proposal to format the data and answers "yes" and "no". After formatting, Android is fully loaded!
Alas, the camera still doesn't work. And now, when I booted through adb to Fastboot and flashed TWRP, I cannot enter the Recovery menu! Tried to go through the Fastboot command: fastboot reboot recovery; and pressing the buttons doesn't work either. The phone just boots into the system. Are there any ways how to get the Recovery back?

xDev91 said:
Yes, I did. I tried to go in this way too, but it didn't work.
That was the point - Android did not boot completely (showed the installation of applications 1-33, and then rebooted and showed the splash screen).
I was able to start Android later:
I typed it, - I held down all three buttons (volume + and -, and the on / off button) - and licked out the menu with the proposal to format the data and answers "yes" and "no". After formatting, Android is fully loaded!
Alas, the camera still doesn't work. And now, when I booted through adb to Fastboot and flashed TWRP, I cannot enter the Recovery menu! Tried to go through the Fastboot command: fastboot reboot recovery; and pressing the buttons doesn't work either. The phone just boots into the system. Are there any ways how to get the Recovery back?
Click to expand...
Click to collapse
the process to enter fastboot works. 100%. maybe your volume button is not working properly.
yes you have to format data when you flash a new ROM. that is the case always when switching between ROMs - and stock is just another ROM so here you need to do that as well ofc.
fastboot reboot recovery does not work here. you have to use the key combo and if that does not work for recovery as well you likely have an issue with your hardware buttons. after flashing TWRP you have to boot directly into it otherwise it will be overwritten on boot. so adb reboot recovery won't work either. last but not least fastboot boot does not work when UsU'd.
so. first of all fix you volume button. maybe disassemble the back cover and see if you see dust/dirt anywhere near the volume button. try pressing the vol down button harder when trying to get into recovery.
if all that does not help and you cannot fix the button problem you could ofc flash TWRP in fastboot to both: the recovery AND the boot (!) partition. Then you can reboot and it will directly load TWRP. here choose reboot-> recovery to be in the correct slot. last you push the boot image from the stock ROM to the device and in TWRP press install (switch to "img"), select the boot image and choose "boot" as target. now you can reboot and TWRP should be still there. but honestly.. fix your volume button

steadfasterX said:
maybe your volume button is not working properly.
Click to expand...
Click to collapse
You were right. The volume button "-" was not quite functional.
I thank you, steadfasterX, for your support. Thanks for the advice. All the best to you!

Question Can not boot any more

Hello comunity,
I installed TWRP on my Galaxy A72 to install Magisk but now I cant Boot any more. Please help my.
I hope you can help me. Moritz

Did you follow all the steps on the XDA thread?
If yes, it could be possible that you additionally need to flash services disabler

Moritz_pro said:
Hello comunity,
I installed TWRP on my Galaxy A72 to install Magisk but now I cant Boot any more. Please help my.
I hope you can help me. Moritz
Click to expand...
Click to collapse
Probably you flashed TWRP image at "fastboot boot TWRPLOL.img" this happens it . now do this,fastboot flash recovery YourTWRP.img then type fastboot reboot then Get your orginal boot.IMG from your Phone version's firmare folder by 7zip or winrar. then do fastboot flash boot boot.img then type fastboot reboot

hey Idk Who can help me for SPOOF(Change by random TEXT) Any android 5.1 to Android8's BASEBRAND Version and KERNEL Version ? How I can change it ? Phone ROOTED and XPosed module ready(not Virtual xposed) ? Please find it or Create new Xposed APK or SUPERuser(ROOT right) APK for Change BASEBRAND and Kernel Version,You know it writes under settings/about phone,Everything changing exclude these.Please Helpme,or if i can do this manually from which file /system or where ?

ineedstoplaggerwatchers said:
Probably you flashed TWRP image at "fastboot boot TWRPLOL.img" this happens it . now do this,fastboot flash recovery YourTWRP.img then type fastboot reboot then Get your orginal boot.IMG from your Phone version's firmare folder by 7zip or winrar. then do fastboot flash boot boot.img then type fastboot reboot
Click to expand...
Click to collapse
I'm not sure if I am understanding all what you are saying right, so please tell me more detailed so I dont't make it worse.

turn of ur phone by holding power button 15 second then wait and be sure phone will not try reboot,then
Press and hold the Power, Volume Down and Home buttons for seconds;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then the device will be the fastboot mode.
get this file then open it (Try open it by 7zip or winrar then extract it there),then click startCMD then type fastboot commands that i talked about it. but first type "fastboot devices" for be sure if it see your fastboot mode phone....... download this https://dl.twrp.me/a72q/twrp-3.6.2_11-1-a72q.img then rename it recovery(Right click on file then click properties and be sure if it says type of file: img file , so fullfile name must be recovery.img then put it into Adb&FastbootCommnderPrayForMe folder then enter this command "fastboot flash recovery recovery.img" then type fastboot reboot then remove cable quick,try power on ur phone, if it still stuck on boot then Poweroff by holding power button 15 second then 2 second later press power button by Volume Up Button together after 3 second later unpress power then continue holding volume up button,If twrp menu opened,swipe right adn go Wipe menu and ONLY chose Clear Cache , then restart phone . if still stuck then go Adb&FastbootCommnderPrayForMe folder and copy recovery.img file to same place and rename it boot(full file name must be boot.img), then go open command then type "fastboot flash boot boot.img" after enter it,Then type fastboot reboot and enter it. if still do same . then Find ur firmware's actual boot.img from your phone device model's firmare version File(firmware versions around 2GB to 10GB)'s boot.img . u can find it in internet too.Hope all works and i will be happy for u too

when I type Fastboot devices my Phone is not regionized what should I do?

Normally PC does not find your device as MTP device while you Hold POWER+home+volumeDown button(I mean fastboot mode without phone bootup).Coz it Shows device as MTP device after Phone bootedup(online).Maybe you tried install its driver as MTP by chosing manual install ? first download and install real usb driver(Adb&fastboot driver) of your samsung phone. https://developer.samsung.com/android-usb-driver then install it. then replug ur phone. Then go Device Manager of your PC,then replug your usb cable,and if you see New Device found like "unknow device or fastboot" then click them then click Properties on it, then click Update driver then click browse for Driver then click Let me pick from list then UNCHECK(unclick) "Show compatible hardware" then find your SAMSUNG ADB driver(if u cant see then click PORTS maybe it installed under Ports drivers) then click next to update it as Fastboot driver . but You can change your PC language to English for See same words in your Pc menus for I help you better coz im not German . but if already your secreen opens ? then you need go phone Settings / about phone/ Tap your phone Firm version 10 times and enable developer menu then enable USB ADB debug for install adb driver easily.if your phone screen not showing anything on screen . then you must just do fastboot mode by fastboot mode keys for install fastboot(samsung android usb driver or ADB driver another name)

When I am in the recovery mode then I see the MTP Window. When I am in the Download Mode I see the other window. I don't now waht the fastboot mode is.

Moritz_pro said:
When I am in the recovery mode then I see the MTP Window. When I am in the Download Mode I see the other window. I don't now waht the fastboot mode is.
Click to expand...
Click to collapse
Ignore what the other guy said above, fastboot is not a thing on Samsung phones. You can make it work with some patches however, but by default there is no fastboot.

ok can you tell me in detail so what do you think is the problem and wehre can I find these patches

Simon1511 said:
Did you follow all the steps on the XDA thread?
If yes, it could be possible that you additionally need to flash services disabler
Click to expand...
Click to collapse
There should be no issues if properly following the XDA thread's instructions.
Moritz_pro said:
ok can you tell me in detail so what do you think is the problem and wehre can I find these patches
Click to expand...
Click to collapse

Thank you for remaining me this option I forgot about it, but I installed a custom Rom, but I'd like to run again on the original software can I install it again. If not, it doesn't matter, but it would be better.

The Rom won't start, the start sign appears but doesn't finish loading.
[ROM][12.1][ENCRYPTION][EOL] LineageOS 19.1 for A52 4G and A72
LineageOS is a free, community built, aftermarket firmware distribution of Android 12.1/12L, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with...
forum.xda-developers.com