Database Develop

(Help!!) How to unbrick my droid3?

{
"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"
}
First, Sorry for my English
Hmm.. my droid3 doesn't work. When boot up, Motorola logo
block motoblur launcher . so I can't use my droid3. I use rsd lite5.5(with fastboot firmware zip). But nothing happened to my droid3. Motorola Korea After service center said "we don't know what is wrong and have replacement"
Help me guys ..
Sent from my SHW-M250S using XDA App

http://forum.xda-developers.com/showthread.php?t=1336980
Follow instructions.
If link to file doesn't work, use this mirror: http://dl.dropbox.com/u/61707107/Ve...izon+DROID+3+OTA+5.6.890+to+phone_psouza4.zip

DoubleYouPee said:
http://forum.xda-developers.com/showthread.php?t=1336980
Follow instructions.
If link to file doesn't work, use this mirror: http://dl.dropbox.com/u/61707107/Ve...izon+DROID+3+OTA+5.6.890+to+phone_psouza4.zip
Click to expand...
Click to collapse
But my symptom is same...
Sent from my LU2300 using XDA App

HerbK said:
But my symptom is same...
Sent from my LU2300 using XDA App
Click to expand...
Click to collapse
What? please elaborate
edit: you don't have the XT862?

DoubleYouPee said:
What? please elaborate
edit: you don't have the XT862?
Click to expand...
Click to collapse
I have Droid3(xt862 vrw). Now My droid3 doesn't work. I download that file and flash file. Flashing is all right, But Everything is same :[
Sent from my LU2300 using XDA App

That is Notification Bar, I can touch that bar. But Droid3 always showed that screen
Sent from my LU2300 using XDA App

HerbK said:
I have Droid3(xt862 vrw). Now My droid3 doesn't work. I download that file and flash file. Flashing is all right, But Everything is same :[
Sent from my LU2300 using XDA App
Click to expand...
Click to collapse
So you flash with fastboot? Not RSDlite..
It takes 3+min first boot

im actually having the same problem as this guy. but mine was refurbished and im pretty sure its a hardware problem. ik adb rsd and moto-fastboot lol

To be clear...
You downloaded that file above?
Plugged in your phone via USB with a mostly/fully charged battery?
Powered up with M + Power button?
Scrolled with Volume Down to AP Fastboot and pressed Volume Up to select it?
Once it said USB Connected, you ran the CLICK HERE etc. batch file?
This should unbrick you in a few minutes and the initial boot will take a few minutes as well. I know those files work...they're my working DL'd files on my DropBox account.

cant speak for the other guy but for me this is my third refurbished droid 3. i can still acess clockwork and stock recovery. i used moto fast boot and rsd they both said "okay" for each part. "adb reboot-bootloader" aka ap fast boot also went there manually yes battery fully charged made sure. im so puzzled lol

jellman said:
cant speak for the other guy but for me this is my third refurbished droid 3. i can still acess clockwork and stock recovery. i used moto fast boot and rsd they both said "okay" for each part. "adb reboot-bootloader" aka ap fast boot also went there manually yes battery fully charged made sure. im so puzzled lol
Click to expand...
Click to collapse
Try the quick unbricking script. There's 2 other threads just posted in today in this General section that contain all of the needed info.

redsox985 said:
Try the quick unbricking script. There's 2 other threads just posted in today in this General section that contain all of the needed info.
Click to expand...
Click to collapse
...hm. maybe i wasn't clear. the unbricking method isnt new to me and i am not a noob. i have tried both thank you for your suggestion tho. permanent solution? google needs to take over the world and unlock bootloaders i miss the days of the original droid T_T

jellman said:
...hm. maybe i wasn't clear. the unbricking method isnt new to me and i am not a noob. i have tried both thank you for your suggestion tho. permanent solution? google needs to take over the world and unlock bootloaders i miss the days of the original droid T_T
Click to expand...
Click to collapse
OOH! Misunderstood you. When you said you used Moto Fastboot and RSD I assumed that you booted into Fastboot to flash with RSD. Fastboot just allows you to flash, the script and RSD are the two means of unbricking. Gotcha. And I agree. BL's need to be unlocked.

Maybe you guys are on the latest OTA and try to fastboot .890?

Sounds to me like either one or both of you didn't erase userspace in stock recovery. I had this very same problem. The rsdlite method will not allow you to boot until the old junk is gone from /data and /cache. Try turning on the d3 from power off while holding the "m" key, then selecting down arrow to "Recovery", then hit "ok". Once in stock recovery, select erase user data and cache. Do it several times, then select reboot, and you will be good to go, assuming you flashed the correct xml/zip package successfully.
Sent from my DROID3 using xda premium

[Fastboot] Droid Razr M Xt907 Ice Cream Sandwich

DROID RAZR M XT907 Ice Cream Sandwich software update availability​
The following table is for reference only.
Country|Carrier Name|Android|System version
US|Verizon|4.0.4|Blur_Version.77.111.10.XT907.Verizon.en.US
BUILT PROPERTIES
build.id=7.7.1Q-144_SMQ_S136-10
build.version.release=4.0.4
build.date=Mon Aug 27 06:18:07 CDT 2012
Blur_Version.77.111.10.XT907.Verizon.en.US
Click to expand...
Click to collapse
Click to expand...
Click to collapse
1. 7.7.1Q-144_SMQ_S136-10 - Verizon
Source: http://www.droidevelopers.com/showt...e-Cream-Sandwich-software-update-amp-download

mine tried to update today, it wouldn't go through. Also when I try to reboot into recovery I'm having issues there, just doesn't want to do it... anyone know why?

Are you pressing all physical buttons then scroll with v down select with v up then press both v buttons at red android screen then select file from SD and apply
https://www.youtube.com/watch?v=6efI1iGAgsU&feature=youtube_gdata_player
Video link to most of process from my YouTube
Sent from my XT907 using xda app-developers app

I missed the step about both v keys at the M, I'm getting it to work now, except I can't find the file. I know its there, can go look at it in the file explorer, but can't find it in recovery.

Did you move it to your SD card it goes to your internal first not external which is where it has to be also did you rename to update.zip?
Sent from my XT907 using xda app-developers app

I apologize if this is something obvious, but when I try and run this through rsdlite (5.7 and 5.9) on my retail M running the JB leak, it immediately fails and says "Failed flashing process. Unknown fastboot command. (getvar)".
{
"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"
}

Got it, didn't know it wasn't downloaded to my external memory. Its all good now, thanks!

Got it to work by removing the getvar line in the xml (per mattlgroff, no way I would've tried that myself) - works perfectly from the JB leak, thanks again for this!

Just to be clear, is the the stock ROM that came with the RAZR M? That way people could try out the JB leak, and then use this to revert back. Since there isn't a way to install CWM and do a backup.

FAUguy said:
Just to be clear, is the the stock ROM that came with the RAZR M? That way people could try out the JB leak, and then use this to revert back. Since there isn't a way to install CWM and do a backup.
Click to expand...
Click to collapse
Correct, on the current leak anyway. Obviously if you have to do this your data will be wiped as well.

jntdroid said:
Correct, on the current leak anyway. Obviously if you have to do this your data will be wiped as well.
Click to expand...
Click to collapse
But the only way you could get it to work was by removing the getvar line in the XML?

FAUguy said:
But the only way you could get it to work was by removing the getvar line in the XML?
Click to expand...
Click to collapse
That's the only way mine would work - rsdlite wouldn't go past that.

Use RSD Lite 6.1.4

When using RSD Light, does the phone have to be in normal "power on" mode, or in a special "download" mode for RSD to install the files?

FAUguy said:
When using RSD Light, does the phone have to be in normal "power on" mode, or in a special "download" mode for RSD to install the files?
Click to expand...
Click to collapse
AP Fastboot - from powered off, hold down volume-up AND volume-down, then while holding those, press and hold the power button until you see a menu pop-up that's simply white text on a black background. Once that comes up, use volume-down to move down to AP Fastboot, and volume-up to select it. Then plug it into your computer, fire up rsdlite (6.1.4! ), open the file linked in the OP, and go!
Sent from my XT907 using Tapatalk 2

Ok, thanks.
I've posted the files and instruction here:
http://www.phonearena.com/news/How-to-restore-your-Motorola-DROID-RAZR-M-back-to-stock_id35580
If anything needs editing, let me know.

FAUguy said:
Ok, thanks.
I've posted the files and instruction here:
http://www.phonearena.com/news/How-to-restore-your-Motorola-DROID-RAZR-M-back-to-stock_id35580
If anything needs editing, let me know.
Click to expand...
Click to collapse
Credits Firmware Team?
Enviado desde mi HTC Sensation XE with Beats Audio Z715e usando Tapatalk 2

help im stuck
ok so i messed with the build.prop and cant get the original one in through adb, i tried flashingjust system img thru fastboot but the file is too big just error after error with cmd prompt...
so i downloaded stock firmware per phonearena link, and i have rsdlite 6.1.4 installed as well as all the latest drivers, it fails on step 1 "gpt_main0.bin" so i removed that line from xml and tried again, it got further but failed at fsg.mbn
i dont know what to do, i figure if all i need is a good build.prop i should have rsd flash just the system.img but that doesnt work either...
i don't know what to do? any suggestions, or ideas?
---------- Post added at 08:11 PM ---------- Previous post was at 07:30 PM ----------
ok i solved it, nevermind

tadgerloks said:
ok so i messed with the build.prop and cant get the original one in through adb, i tried flashingjust system img thru fastboot but the file is too big just error after error with cmd prompt...
so i downloaded stock firmware per phonearena link, and i have rsdlite 6.1.4 installed as well as all the latest drivers, it fails on step 1 "gpt_main0.bin" so i removed that line from xml and tried again, it got further but failed at fsg.mbn
i dont know what to do, i figure if all i need is a good build.prop i should have rsd flash just the system.img but that doesnt work either...
i don't know what to do? any suggestions, or ideas?
---------- Post added at 08:11 PM ---------- Previous post was at 07:30 PM ----------
ok i solved it, nevermind
Click to expand...
Click to collapse
PLEASE post what you did to fix this issue as it may creep up again for someone else. These posts I run into every so often on google asking a problem and then all I see is "fixed it" no solutions posted. =) thanks!

I deleted the bad build.prop from the system, and The recovery-from-boot.p file or something similar in name, they're the only 2 files in /system that aren't folders, after I rebooted into AP Fast boot and through cmd.exe on win7 and typed in "fastboot -w"
Then "fastboot reboot"
Back too fastboot mode, start RSDLite 6.1.4 w/admin privileges, extracted firmware manually, edited XML too remove any line wit "var" or "OEM" in them, as well as the line with "gpt-main0.bin" I pointed RSD too the XML and it flashed flawlessly
Now I'm back on JB Leak and rooted

[Q] Having problems flashing my Droid 4

I ran into a problem on my stock rom that I thought I could fix by restoring a backup of my phone using safe strap 3.11. I'm not sure what I did wrong, but after the restore my phone would boot though the Motorola Duel Core screen, then the safe strap screen where you can press menu of search to go into recovery or t skip. Then the "droid" sound plays, but there is no boot animation (black back lit screen). I tried restoring two more times with the same result.
I then tried to flash the 4.0.4 fastboot file from sbf.droid-developers.org/cdma_maserati/list.php using RSD Lite 5.6, but it kept failing on the first step.
I'm still able to boot into recovery mode and I'm able to boot into the Cyanogen Mod 10.1 I have installed on one of my rom slots.
What can I do to fix my stock rom?

you verified md5 check sum
phone was in ap fastboot?
Sent from my XT894 using xda premium

sd_shadow said:
you verified md5 check sum
phone was in ap fastboot?
Sent from my XT894 using xda premium
Click to expand...
Click to collapse
Yes and yes.

you install moto drivers manually before flashing?
Motorola_End_User_Driver_Installation_5.9.0_ Dev-H
after flash failed, did you check Device Manager for an unknown device or device without a driver?
---------- Post added at 05:03 PM ---------- Previous post was at 04:58 PM ----------
may look like this if missing driver
{
"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"
}
---------- Post added at 05:04 PM ---------- Previous post was at 05:03 PM ----------
note the yellow triangle with ! in it.

Yes, and there were no unknown devices.
I tried flashing it again and this time it got to step 5 before failing.
"Failed flashing process. Failed flashing process. 5/17 reboot-bootloader -> Phone returned FAIL; phone connected"

did you try wiping cache or data?
using Stock moto usb data cable?
maybe try RSD Lite 5.7
or different pc

sd_shadow said:
did you try wiping cache or data?
using Stock moto usb data cable?
maybe try RSD Lite 5.7
or different pc
Click to expand...
Click to collapse
I am using the stock moto cable and RSD Lite 5.7. I don't have another pc to use.

if you want to restore my stock nandroid made in safe strap 3.11
I uploaded to http://d-h.st/piz 429.61 MB
It's only has been rooted, with safe strap 3.11 installed
no accounts, no apps added or removed, I never really have used stock
system version 6.16.217.XT894.Verizon.en.US
android version 4.0.4

I can restore that using safe strap, right?
Also, do you have any advise for making backups, like program and settings? I think there might have been something wrong with the backup I made with safe strap because I don't get why it would load to a black screen just from restoring a backup, but I'm not sure what went wrong.
Could my problem flashing have something to do with my SDK? I used to have a Droid 2 and had to flash it several times from this computer and all I've updated since then has been the fastboot file, RSD Lite, and the moto drivers.

yes restore with safestrap
your nandroid may have got corrupted, not sure why
flashing problem seems like a driver issue, have you tried
MOTOROLA DEVICE MANAGER
how much ram does your pc have? 1gb or more?
also could try Droid 4 Utility ICS Only
downloads here jsnweitzel

99% Finished
After using your backup with safe strap and restoring my apps and data with titanium, almost everything is back to normal. I did run into a small problem with system updates under Settings > About Phone. When I check for updates it says "Check for update is not available at this time. Try again later."
Do you know what would cause that or how I can fix it?

phone is active on verizon network?
if you have removed/froze any stock apks, update may fail
just checked update works, over wifi for me, at least it said
Your device is up to date!
No updates is necessary at this
time.
Click to expand...
Click to collapse
if trying over LTE, may want to dial *228
if an update does get pushed a you can not update over the air
someone will post the update.zip, that can be flashed in stock android recovery
thanks for letting know, stock nandroid backup, worked for you,
I thought it should, but who knows what the reason, the xml recovery file didn't work

My phone is active. I unfroze my frozen apps. I dialed *228. I tried on LTE and wifi. I still get the same error message, but I'm not too concerned about it. Thank you very much for unbricking my phone.

did you see there's a soak test update?
is your phone registered @ the moto site?
---------- Post added at 11:20 PM ---------- Previous post was at 11:11 PM ----------
just curious, if that's why, you checked for an update
---------- Post added at 11:47 PM ---------- Previous post was at 11:20 PM ----------
sometimes unfreezing stock apps, still is not enough, if you want to update ota
you may have restore my nandroid

The main reason I want the system updates to work is just for the sake of completeness, not anything specific. I'll keep playing around with different backups to try to get it working.

[RESOLVED]Did I just brick my phone? Any help at all is appreciated

So in preparation for the kitkat update, I did the following steps:
unrooted within superuser app
flash stock recovery
flash stock boot.img
flash stock system.img
Once I rebooted I downloaded the OTA and tried to install. Now, after that, I wasnt really sure what happened on the phone, as I passed the time by watching a youtube video on my computer. However, I looked back down, and it was inside the bootloader, giving a partition failure of some sort. And when I tried to flash anything, it gave a remote failure error. It won't boot into anything, and it says the device is locked. Can't do mfastboot oem get_unlock_data either, literally nothing but fastboot reboot works
do i have a $650 paper weight on my hands?
{
"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"
}
Fixed it! See the post at the very bottom of this page for the solution!

i would use RSD lite to get back to the latest 4.2.2

mj0528 said:
i would use RSD lite to get back to the latest 4.2.2
Click to expand...
Click to collapse
it won't boot at all

Well fastboot starts at least. If you try to reload stock firmware (4.2.2) using rsdlite(not fastboot from a command line) which error do you get?

Steve-x said:
Well fastboot starts at least. If you try to reload stock firmware (4.2.2) using rsdlite(not fastboot from a command line) which error do you get?
Click to expand...
Click to collapse
My device isn't showing up under rsdlite 6.1.4 at all

Sadly then I'm leaning towards it being a pretty looking brick. I've had many flash failures while experimenting with my XT1058s but I have never tried any custom recoveries so they were always recoverable with fastboot and rsdlite.
Hopefully someone else has some suggestions for you to try.

I flashed system.img, recovery.img, and boot.img from the original sbf file. not from the first OTA. and then the phone seems to have locked itself

alex94kumar said:
I flashed system.img, recovery.img, and boot.img from the original sbf file. not from the first OTA. and then the phone seems to have locked itself
Click to expand...
Click to collapse
Had you taken the first OTA already? If you had done that, you should have flashed these files from the new SBF file....
So, when you are in fastboot mode, your device is no longer getting recognized from fasboot command line? What does fastboot devices show?

tejaskary said:
Had you taken the first OTA already? If you had done that, you should have flashed these files from the new SBF file....
So, when you are in fastboot mode, your device is no longer getting recognized?
Click to expand...
Click to collapse
Ah. there's my problem. I flashed the files from the factory moto X.
And the device is recognized in fastboot, I can send it commands, it's just that none of them except fastboot reboot actually work

alex94kumar said:
Ah. there's my problem. I flashed the files from the factory moto X.
And the device is recognized in fastboot, I can send it commands, it's just that none of them except fastboot reboot actually work
Click to expand...
Click to collapse
Can you try these commands and see if anything changes?
fastboot oem fb_mode_clear
fastboot reboot-bootloader
After that can you try any of the fastboot flash commands using the new SBF file?

It worked!!! Oh my god thank you so much! You are a life saver!!

delete

alex94kumar said:
It worked!!! Oh my god thank you so much! You are a life saver!!
Click to expand...
Click to collapse
Glad it worked for you !! Enjoy with 4.4...

[Superseded] Crossflash US Unlocked Pie to your Bootloader Unlocked V40

SUPERSEDED: Go Here​
Prerequisites:
V35 Engineering Bootloader flashed to your device (Stock bootloader will NOT work for this)
USB 2.0 (USB 3.x does not work well with ADB or Fastboot)
The V40 Pie Conversion Tool
Be in fastboot mode before attempting this
Patience
ADB and Fastboot DRIVERS. Platform tools are already included in the archive
Windows. The tool is not designed for Linux.
This will NOT sim unlock your phone[/CENTER]
Note: I'm not responsible for any bricks that come about from using this tool. Once you crossflash, there's NO going back unless you have backups of your partitions, or a KDZ specifically for your device. I'm going to say this again, DO NOT use USB 3.x while attempting this. You will run into errors. You won't see anything for a little bit when it gets to flashing system_a and vendor_a because it has to load those images into ram.
Download the tool: Google Drive
1. Download the archive and unzip the tool.
2. Navigate to the folder you unzipped the tool to.
3. Enter the folder and inside the folder you should find "V40PIECONVERSION.cmd". Ignore the one with the "Stock Boot" at the end. All it does is flash the stock boot image instead of the TWRP that is required to do this.
4. Execute the batch file and follow the instructions. When the batch file is done, Pie will be flashed, but it will not boot due to encryption. We're going to disable that.
5. Boot TWRP by performing a master reset. To perform a master reset: Press and hold Vol- and Power. When you see the "V40 ThinQ" logo release the power button and quickly press back down. Keep holding Vol- and Power until you see a factory reset screen. Finally, follow the prompts (yes) and you should be in TWRP.
TWRP Instructions​
Head over to the wipe menu and format data (to remove encryption).
Next, head over to mount and mount vendor. Mount ONLY vendor.
Now, open a command prompt, navigate to the folder where you extracted the tool, and open a command prompt inside the folder (Type "CMD" in File Explorer's Address Bar)
{
"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"
}
Execute the adb command:
Code:
adb pull /vendor/etc/fstab.judypn
Edit the file (fstab.judypn) in your favorite text editor and on the /data mountpoint change "forceencrypt" to "encryptable".
Save and Close the file and push the file back with the command:
Code:
adb push fstab.judypn /vendor/etc
Now that encryption is disabled, you NEED to flash back the ORIGINAL boot image that's included with the tool. In order to do that, we need to get back into fastboot.
To get back into fastboot, we need to: Make sure USB is still plugged into the phone. Press and hold VOL+ (Or vol up). Power off the phone (Via TWRP reboot menu) while still holding vol+. Keep holding VOL+ until you see download mode flash for a brief second and you should be in fastboot. The fastboot you see now isn't the V35 Engineering Bootloader. It's the stock pie bootloader. Wiping the laf_a partition allows access to fastboot on devices that are locked (Nearly all US Carriers).
Finally, run the commands:
Code:
fastboot flash boot_a boot_a.image
and
Code:
fastboot format userdata
You should run into an "encryption unsuccessful" screen. Just hit reset phone. You may have to reboot once or twice to get to the setup screen.
For those of you that want root, here's a patched Magisk boot image: Google Drive
You can flash it by running the command:
Code:
fastboot flash boot_a magisk_patched.img
Make sure you open a command prompt in the directory you downloaded the image in. If you don't have adb and fastboot in your environment path, just place it in the V40PIEConversion folder and flash it from there.

How do you get the v35 bootloader on stock Att ?

Evilmonstertruck said:
How do you get the v35 bootloader on stock Att ?
Click to expand...
Click to collapse
Contact @vbenkovskyy on Telegram. He is an awesome guy. Of course, it isn't free, but his prices are better.

Confirmed working - thanks Xsavi for an excellent guide!

Would this method work on the T-Mobile variant? Is there a fee [anywhere]?
---------- Post added at 04:16 PM ---------- Previous post was at 04:12 PM ----------
Can someone comment on this?

avaie said:
Would this method work on the T-Mobile variant? Is there a fee [anywhere]?
---------- Post added at 04:16 PM ---------- Previous post was at 04:12 PM ----------
Can someone comment on this?
://youtu.be/nSeqIfQeWi4
Click to expand...
Click to collapse
No T-Mobile is not supported

avaie said:
Would this method work on the T-Mobile variant? Is there a fee [anywhere]?
---------- Post added at 04:16 PM ---------- Previous post was at 04:12 PM ----------
Can someone comment on this?
://youtu.be/nSeqIfQeWi4
Click to expand...
Click to collapse
Ainz is right. You'll end up with a brick if anything.

Confirmed working on my att variant. ? Thanks again for the great guide ?

pp342261 said:
Confirmed working on my att variant. Thanks again for the great guide
Click to expand...
Click to collapse
You are very welcome! Feel free to contact me if you run into any issues.
On the plus side, your b-slot is untouched throughout all of this, so you can use that to re-root or flash backups should something go wrong, or update. Enjoy the pie.

Xsavi said:
You are very welcome! Feel free to contact me if you run into any issues.
On the plus side, your b-slot is untouched throughout all of this, so you can use that to re-root or flash backups should something go wrong, or update. Enjoy the pie.
Click to expand...
Click to collapse
Will this work on the LG V40 International?

rmgibbs1861 said:
Will this work on the LG V40 International?
Click to expand...
Click to collapse
Yes it will.

rmgibbs1861 said:
Will this work on the LG V40 International?
Click to expand...
Click to collapse
One more question, How will further updates be done after cross flashing? Thank you!

rmgibbs1861 said:
One more question, How will further updates be done after cross flashing? Thank you!
Click to expand...
Click to collapse
By flashing System, Vendor, and boot.

Very confusing. Which variants of V40 this is going to work for?

How to get the v35 engineering bootloader on the phone the only method ive heard about is through octoplus jtag?

twoxa said:
Very confusing. Which variants of V40 this is going to work for?
Click to expand...
Click to collapse
Well it worked for all US Carriers except for T-Mobile

had my sprint v40 bootloader unlocked from octoplus and tried this cause i hate sprint SW (activation screen).it flashed everything from batch file fine but when i went to boot into twrp it booted into normal recovery with the rainbow circle "erasing" then rebooted into os but it was all korean and the android version was 8.1. wtf lol? trying it again now, yes im using "V40PIECONVERSION" not the stock one.

jass65 said:
had my sprint v40 bootloader unlocked from octoplus and tried this cause i hate sprint SW (activation screen).it flashed everything from batch file fine but when i went to boot into twrp it booted into normal recovery with the rainbow circle "erasing" then rebooted into os but it was all korean and the android version was 8.1. wtf lol? trying it again now, yes im using "V40PIECONVERSION" not the stock one.
Click to expand...
Click to collapse
Did you check to make sure you are on Slot A and not B? Becuase i remember when i had everything flashed the first time i tried to boot TWRP in Slot A and somehow ended up switching to Slot B

Ainz_Ooal_Gown said:
Did you check to make sure you are on Slot A and not B? Becuase i remember when i had everything flashed the first time i tried to boot TWRP in Slot A and somehow ended up switching to Slot B
Click to expand...
Click to collapse
thats what it ended up being. xSavi helped me out :good:

Hi guys,
I have a Sprint V40 bought off of Taobao that was rooted, sim unlocked, and crossflashed to US Cellular 11d but after I installed Pix3lify trying to get gestures on 8.1 I lost root. I don't seem to be able to get into fastboot, either with Vol- + cable or via adb, but I have an unlocked bootloader and I can get to download mode. Factory reset just reboots. Any tips as to how can I get root back, or upgrade to Pie? Can anybody please explain how to switch from slot a to slot b and vice versa?
Jeff