Related
cant get windows to find USB driver for cwm/trwp... missing drivers or something tried most common dl links, vmware to isolate. i337m latest trwp openrecovery-twrp-2.6.3.1-jfltecan/GalaxyS4-CWM-6.0.4.4-Canada. ive also tried forcefully installing from the latest samsung/adb cab/exe and windows wont recognize the manual install either.
used these so far
http://forum.xda-developers.com/showpost.php?p=11498043&postcount=1&nocache=1&z=8984906396242748
neither after extracting files can manual install the required drivers, not sure what the ****ing hell is wrong. its not a windows thing its a matter of the infs are lacking the hwids or im just installing the wrong things here.
win 7 x64.
Hello everyone on the XDA community.
This is my first post here ..!
To begin excuse my very bad English, I used a translator to do this. Second, moderators apologies if it is not the right place, I ask a little patience and if you need to edit or move the topic, are in every right to do so.
Thanks in advance.
WARNING: This method has been tested by me, but do not hold me responsible for lost data on their devices or if they suffer irreparable damage. The method should be used with caution, following the steps explained below and must possess knowledge of the use of the tools used. USE AT YOUR OWN RISK.
Tools to be used:
BLU Phone Drivers
Universal ADB Drivers
SP Flash Tools v5.1436.00.000
Studio C D536U V08 5.0 Generic Stock Rom
Kingo Root
Easy Magic TWRP Installer for MediaTek
The first step and most important is: BACKUP, support all device data if possible make a backup of the complete ROM Stock, since in case of a "sudden death" can use this to revive the device. In the XDA Developers forums are methods to do this kind of support.
Steps that I have followed for an update ROM Stock, rooting and subsequent installation of custom recovery:
If you have any drivers installed for your BLU device uninstall them before seeing step 2.
Install the device driver for BLU
ADB drivers installed Universal
Enable USB debugging on development options
Download and install the ROM Stock mentioned above using the following::
Open SP Flash Tool.
Click scatter-loading then select the scatter file inside the ROM you downloaded (must be unzipped of course).
Change "Download" to "Firmware upgrade" (under scatter-loading file).
Click in "Download" button.
Take battery out of your phone and insert it again. make sure your phone does not turn on (If phone has an internal battery then just make sure the phone is off).
Plug in your phone to your PC.
The green check mark means you're good to go.
After installing the new ROM Stock, or if you were already using that version of the ROM Stock must install the Kingo Root, then connect your device and the program will recognize it immediately. The whole process is very simple and takes very little time, stay tuned to the screen of your device for confirmations.
Already having installed and running ROM Stock and rooting and undamaged device, run the program TWRP Setup, this will create the MTK-TWRP folder on your desktop, in it we find the TWRP.exe program which execute and follow the steps described in THIS POST.
And with that we have our rooting device with a new version of ROM Stock and custom recovery.
FINAL NOTE: In my case after installing the new version of ROM Stock did a search for update from the device, and found a new version: BLU_D536U_V10_GENERIC. The downloaded and installed before proceeding with the routing and the installation of custom recovery.
I hope you can use this guide and is very useful for everyone.
Best regards.
New Link Added 16/04/2015https://mega.co.nz/#F!TplRURRI!LyAuAlNIBND_AOgu3bx6tQ
Thanks for the guide, but the rom Studio C D536U V08 5.0 Generic Stock Rom in the mega link, is not available, can you upload?
tttony said:
Thanks for the guide, but the rom Studio C D536U V08 5.0 Generic Stock Rom in the mega link, is not available, can you upload?
Click to expand...
Click to collapse
Hi.
The following directory on the website of Mega contains all the Stock ROM for BLU devices, look inside the folder named "STUDIO SERIES" the "STUDIO 5 C - D536" folder, there you can download the ROM Stock V8 Generic.
https://mega.co.nz/#F!TplRURRI!LyAuAlNIBND_AOgu3bx6tQ
BLU Phone Drivers [link broken]
SP Flash Tools v5.1436.00.000 [link broken]
I have a bricked BLU Studio 5.0 C D536L. Can I flash this rom and files?
I don't know if D536U and D536L are the same devices (maybe L and U only a local id).
I just got this phone from Walmart, even though I didn't use your method to root, as my rom is newer than the rom you provide, mine rom is BLU_D536U_V11_GENERIC seemed pointless to downgrade, I did download your Studio C D536U V08 5.0 Generic Stock Rom as it contained a file I needed to manually root my device.
I use Linux not windows, so the splash tool doesn't help, none the less I was able to root without any problems, using the one file from Studio C D536U V08 5.0 Generic Stock Rom.
Thanks
Vampirefo
Need a pointer or two.
vampirefo said:
I just got this phone from Walmart, even though I didn't use your method to root, as my rom is newer than the rom you provide, mine rom is BLU_D536U_V11_GENERIC seemed pointless to downgrade, I did download your Studio C D536U V08 5.0 Generic Stock Rom as it contained a file I needed to manually root my device.
I use Linux not windows, so the splash tool doesn't help, none the less I was able to root without any problems, using the one file from Studio C D536U V08 5.0 Generic Stock Rom.
Thanks
Vampirefo
Click to expand...
Click to collapse
Hello. I have the same phone and conundrum. Sure would appreciate any pointers you could throw my way about successfully rooting this critter. It's a BLU Studio 5.0 Ce D536 Unlocked Dual SIM 5.0 Phone Android KitKat CellPhone.
There was a sale on ebay selling this new for 68.00 so I bit the bullet and bought it. Sure would appreciate it. I use both Linux and windows so I can relate. Any pointers would be great,Thanks!
rwilcher said:
Hello. I have the same phone and conundrum. Sure would appreciate any pointers you could throw my way about successfully rooting this critter. It's a BLU Studio 5.0 Ce D536 Unlocked Dual SIM 5.0 Phone Android KitKat CellPhone.
There was a sale on ebay selling this new for 68.00 so I bit the bullet and bought it. Sure would appreciate it. I use both Linux and windows so I can relate. Any pointers would be great,Thanks!
Click to expand...
Click to collapse
Your device is different than mine, I don't know anything about your phone.
Sent from my BLU STUDIO 5.0 C using Tapatalk
rwilcher said:
Hello. I have the same phone and conundrum. Sure would appreciate any pointers you could throw my way about successfully rooting this critter. It's a BLU Studio 5.0 Ce D536 Unlocked Dual SIM 5.0 Phone Android KitKat CellPhone.
There was a sale on ebay selling this new for 68.00 so I bit the bullet and bought it. Sure would appreciate it. I use both Linux and windows so I can relate. Any pointers would be great,Thanks!
Click to expand...
Click to collapse
Post 3 seems to have files for your phone, should be able to use those files to root your device.
I had to build a custom recovery for my device, I built Carliv 3.3 recovery and TWRP 2.6.8.0 for my device.
Sent from my BLU STUDIO 5.0 C using Tapatalk
Root BLU Studio 5.0 C success
vampirefo said:
Post 3 seems to have files for your phone, should be able to use those files to root your device.
I had to build a custom recovery for my device, I built Carliv 3.3 recovery and TWRP 2.6.8.0 for my device.
Sent from my BLU STUDIO 5.0 C using Tapatalk
Click to expand...
Click to collapse
Thanks for that. Worked but was scary. Had to change shorts afterwards
Brick/Loop in Recovery.
Hey alakentu, thanks for this great thread. I have a problem at the moment: My, Studio BLU Studio 5.0 C (D536U), boots into the recovery and that is all. If I select Factory Mode it gets stuck on the BLU boot animation. I need to flash a new ROM through the original recovery and I need help with this. Can somebody help me ?
I'll give it a try
I have a 5.0C that has one SIM disabled. The SIM was filled with a platic blank that was glued down. I plan on backing up the custom Digicel ROM (D526 I think) and try to load the D536U stock ROM. I assume that if the hardware isn't customized, the stock ROM will have the code that enables and controls the two SIMS. :fingers-crossed:
I rooted and updated my previously locked phone to the V11 generic ROM. The generic ROM:
1. enabled the SIM that was blocked from the OEM.
2. unlocked both SIM slots.
The upgrade was well worth the trouble that I had with properly loading the USB drivers on my Windows 8 PC.
Same exact quandary here as @blackvitriol. My d536u (Studio 5.0 C) sticks at the Blu splash screen. Is there an RUU mode of sorts with this device? If so, how do I access it without being able to fully boot this device?
Sent from my HTC6535LVW using XDA Free mobile app
jmvaught said:
Same exact quandary here as @blackvitriol. Sticks at the Blu splash screen. Is there an RUU mode of sorts with this device? If so, how do I access it without being able to fully boot this device?
Sent from my HTC6535LVW using XDA Free mobile app
Click to expand...
Click to collapse
SOLVED!! (Not that this is an active thread or anything)
So, in ALL of my research I didn't find one single instruction to fix the bootloop, corrupted ROM issue I had. Many claimed to be able to fix this issue, but all fell short because of ONE SINGLE error in the command line. I know, that's all it takes, BUT it may be difficult to figure out (as it was for me). This is all assuming you have your drivers installed and at the very least Minimal ADB/Fastboot functioning.
1. download the factory image (zip, rar, whatever) and UNPACK it somewhere you can easily find in Windows.
2. place the boot.img and system.img files in the same folder as adb.exe and fastboot.exe
3. put your device in Fastboot by doing the following:
a. press and hold Vol Up AND Power until you see the LCD flicker dark (you'll know it when it happens about 3 seconds into holding. Nothing else will happen yet. Nothing will appear on your LCD.)
b. press Vol Up twice and then Vol Down
*you should see three lines pop up in white text on your screen and it should show Fastboot beneath that. If not, pop that battery out and start over. It may take practice to get it right.
4. open a command window in your adb/fastboot folder.
5. Type the following:
fastboot devices
(your device should show up after you hit enter)<---don't type this
fastboot flash boot boot.img
(you should get some action on your device showing it flashed OK as well as in your command window)<---or this
fastboot flash /system system.img
(you should see it working on your device's LCD counting up from 0% to 100%)<---or this
fastboot reboot
(now wait and watch your device come back to life)<---or this
So what's different here from the other instructions out there? You're flashing the system partition by typing "/system system.img" instead of "system system.img"
Any questions, feel free to ask. Have a good one and good luck.
If I've helped you in any way and you want to help support my kids' college fund, please consider buying me a cup of coffee.
jmvaught said:
Same exact quandary here as @blackvitriol. My d536u (Studio 5.0 C) sticks at the Blu splash screen. Is there an RUU mode of sorts with this device? If so, how do I access it without being able to fully boot this device?
Sent from my HTC6535LVW using XDA Free mobile app
Click to expand...
Click to collapse
i threw away that phone and bought a LG Tribute. Best decision ever. Also, thanks for teaching me this new word: quandary
jmvaught said:
SOLVED!! (Not that this is an active thread or anything)
So, in ALL of my research I didn't find one single instruction to fix the bootloop, corrupted ROM issue I had. Many claimed to be able to fix this issue, but all fell short because of ONE SINGLE error in the command line. I know, that's all it takes, BUT it may be difficult to figure out (as it was for me). This is all assuming you have your drivers installed and at the very least Minimal ADB/Fastboot functioning.
1. download the factory image (zip, rar, whatever) and UNPACK it somewhere you can easily find in Windows.
2. place the boot.img and system.img files in the same folder as adb.exe and fastboot.exe
3. put your device in Fastboot by doing the following:
a. press and hold Vol Up AND Power until you see the LCD flicker dark (you'll know it when it happens about 3 seconds into holding. Nothing else will happen yet. Nothing will appear on your LCD.)
b. press Vol Up twice and then Vol Down
*you should see three lines pop up in white text on your screen and it should show Fastboot beneath that. If not, pop that battery out and start over. It may take practice to get it right.
4. open a command window in your adb/fastboot folder.
5. Type the following:
fastboot devices
(your device should show up after you hit enter)<---don't type this
fastboot flash boot boot.img
(you should get some action on your device showing it flashed OK as well as in your command window)<---or this
fastboot flash /system system.img
(you should see it working on your device's LCD counting up from 0% to 100%)<---or this
fastboot reboot
(now wait and watch your device come back to life)<---or this
So what's different here from the other instructions out there? You're flashing the system partition by typing "/system system.img" instead of "system system.img"
Any questions, feel free to ask. Have a good one and good luck.
If I've helped you in any way and you want to help support my kids' college fund, please consider buying me a cup of coffee.
Click to expand...
Click to collapse
Question/Comment...& Thank you.. However I am attempting to sideload adb style ROM from my BLU 5.5 to another's BLU 5.0 C D536u. Any non USB, PC Solutions? Last night we attempted to back up my system to an SD but failed. Pls I've spent hours researching I've installed the Necessary apps (from what I've read), pls help. Thanks again tho for posting this very useful info
Ivy.Crystal said:
Question/Comment...& Thank you.. However I am attempting to sideload adb style ROM from my BLU 5.5 to another's BLU 5.0 C D536u. Any non USB, PC Solutions? Last night we attempted to back up my system to an SD but failed. Pls I've spent hours researching I've installed the Necessary apps (from what I've read), pls help. Thanks again tho for posting this very useful info
Click to expand...
Click to collapse
Why are you trying to put 5.5 rom on 5.0?
Sent from my Venue 8 3830 using Tapatalk
I'm trying to find the 5.0 stock ROM to download it to my SD so the other person can put it in that way.
Or if u can just help me figure out how to get the 5.0C out of bootloop using my phone? Pls
Sent from my BLU STUDIO 5.5 C using Tapatalk
Anyone install the new update? My phone shows v14 is available, date 9/9/2015.
Sent from my BLU STUDIO 5.0 C using Tapatalk
Hi XDA Community!
I can find information to about almost single topic, but the big problem is, i dont know where exactly to start with and the correct order of all of these steps.
What i wanna do is, like on a pc, format the whole phone, delete everything and set up a custom rom and root the phone.
My first step was trying to root it because i dont know if the root is related to the OS or to the phone kernel.....
I tried the CF-Autoroot procedure from XDA-Forum http://forum.xda-developers.com/showthread.php?t=2219803 but i experience the same issue as many other users. When i click start the process starts, but gets stuck immediately when it comes to the imaging step. Then i get no response from my phone or Odin anymore, the bar wont process for hours.
I tried different USB ports, same result. But i can exchange data from phone OS to pc via USB without problems !
So im kind of thrown back now and i dont know what to do or where to start. Can anyone help me ?
5 Years ago i cooked a rom for my Sony Xperia X1 and put it on my phone without any problems lol, and now with Samsung i get only problems.....
If you want to put a custom ROM on it you only need to flash a custom recovery.
This can be done, also, with Odin.
The only other steps are with ADB or root.
TWRP have install instructions (for all methods) on their site.
One important thing is that you also have to take your device model into consideration. Some models (AT&T & Verizon) have locked bootloaders, which make the whole process of rooting and flashing a pain in the butt.
GDReaper said:
If you want to put a custom ROM on it you only need to flash a custom recovery.
This can be done, also, with Odin.
The only other steps are with ADB or root.
TWRP have install instructions (for all methods) on their site.
One important thing is that you also have to take your device model into consideration. Some models (AT&T & Verizon) have locked bootloaders, which make the whole process of rooting and flashing a pain in the butt.
Click to expand...
Click to collapse
My phone is NOT locked. But my question was the correct ORDER of these things to do. Please read my question carefully. What I do first and what comes next ? I also want to root my phone for full acess
C128D said:
My phone is NOT locked. But my question was the correct ORDER of these things to do. Please read my question carefully. What I do first and what comes next ? I also want to root my phone for full acess
Click to expand...
Click to collapse
I read it and I told you.
If you want to put a custom ROM on it, you have to flash a custom recovery First!
Recovery and root are two independent things. The only reason to root first would be if you want to backup your apps and data of your current ROM.
Custom ROMs are pre-rooted
Otherwise flash a custom recovery, put the ROM zip on your microSD card, boot into recovery, wipe the phone, flash the ROM.
And don't forget about gapps.
Since you said you've already flashed ROMs before, this shouldn't be anything different from what you did before.
Well, it was a lot easier on my Sony, even cooking the rom was a first time success. Here im struggling really hard since i feel im running around in circles, not able to proceed...
First of all some details to my phone:
Android 5.0.1
API Level 21
Bootloader I9505XXUHOJ2
Build ID LRX22C.I9505XXUHOJ2
Java VM ART 2.1.0
OpenGL ES 3.0
Kernel armv7l
Kernel V 3.4.0-5978264 (I9505XXUHOJ2)
Root No
Thing is, every source tells me that I need TWRP or a different custom loader to flash the ROM. But i cannot install it since my phone isnt rooted and the ODIN root-method fails for me, since the process stops right in the beginning at the recovery.img, like its hung up. I tried everything from different USB ports to disabling windows firewall and enabling USBdebugging in the developer settings of my phone... Still same result, no sucess....
Is there any way to do this via Kies ? What should I do ?
C128D said:
Well, it was a lot easier on my Sony, even cooking the rom was a first time success. Here im struggling really hard since i feel im running around in circles, not able to proceed...
First of all some details to my phone:
Android 5.0.1
API Level 21
Bootloader I9505XXUHOJ2
Build ID LRX22C.I9505XXUHOJ2
Java VM ART 2.1.0
OpenGL ES 3.0
Kernel armv7l
Kernel V 3.4.0-5978264 (I9505XXUHOJ2)
Root No
Thing is, every source tells me that I need TWRP or a different custom loader to flash the ROM. But i cannot install it since my phone isnt rooted and the ODIN root-method fails for me, since the process stops right in the beginning at the recovery.img, like its hung up. I tried everything from different USB ports to disabling windows firewall and enabling USBdebugging in the developer settings of my phone... Still same result, no sucess....
Is there any way to do this via Kies ? What should I do ?
Click to expand...
Click to collapse
There are 3 methods to flash TWRP:
1) Root and Flashify
2) Odin
3) ADB
Since rooting with Odin doesn't work, maybe you should try flashing recovery with Odin.
Have you tried a different version of Odin or a different Windows version?
So im thinking of purchasing one of these when the come out here and i was wondering about an android to windows os hack. Will there be one in the immediate future and will dual booting be an option?
The hardware is exactly the same.
There must be a way to dual boot, hopefully others on this forum can figure out how to do this if Lenovo doesn't facilitate dual boot themselves
Best
I believe there's a different BIOS for Win vs Android. Could have sworn I saw the Windows BIOS posted on the Lenovo support site prior to the Oct 17 launch. It seems gone now though, unless I'm missing something or went to the wrong link? Unlikely you can install Win without a different BIOS.
There is some clear hardware differences with the Android and Windows tablets. Specifically, 2 different physical layouts for the halo keyboard, where the windows one has defined left and right mouse click buttons. There doesn't seem to be any way of accessing the BIOS on the Android tablet, and it does have the usual Android power + volume up, power + volume down recovery options, so it looks like it boot directly to the boot loader.
The Bios is still there ... but how would you flash it?
http://support.lenovo.com/de/de/products/Tablets/Yoga-Series/YOGA-Book/downloads/DS119182
ok so there is also android open source code available in their site, any chance of making a custom rom?
I wonder if we could flash the Chuwi 12 roms onto this given that Chuwi12 has dual boot already?
This is reallly really stupid to me, why not provide dual boot in the first place? I would not mind shelling out $100 more for a dual boot version. Now if I want the windows version I will need to spend another $550 to get another OS with the same device. I will end up having 2 same devices, but that is so anti-mobile really. Do I have to carry 2 hardware devices so i can have 2 OSes at the same time?
Lenovo get some grip please and provide a dual OS version.
win 10 driver
Today, the windos 10 drivers are online..
The drivers you get with levono support with input of the serial number
It must now be possible to build a dual system
Tastertur chipset audio and more .
igelelf said:
Today, the windos 10 drivers are online..
The drivers you get with levono support with input of the serial number
It must now be possible to build a dual system
Tastertur chipset audio and more .
Click to expand...
Click to collapse
Could you post the link for the windows 10 drivers? also any idea on how to unlock the bootloader?
Hi,
earthCallingAngela did unlock the bootlader. .
My background knowledge about booting is very low. But I think there are huge differences between Android and Windows. I think If a system can boot via PC-Bios or Android-Boot-Loader is "on the chip". If this is correct you would need a Android-Boot-Loader that does boot into a windows ... IMO this is no "easy to do". May be the guys who did create Remix OS found a way to do that ...?
Can we use Chuwi 12's disk image somehow? It comes with dual boot.
hajkan said:
Can we use Chuwi 12's disk image somehow? It comes with dual boot.
Click to expand...
Click to collapse
Are the two the same hardware? My understanding is that unless the hardware is very similar, you can't use other ROMs without a *TON* of work.
so i was able to install android x86 6.0 on my yoga book, unfortunately i managed to do it over my windows install so now i just need to reinstall windows lol.....
---------- Post added at 06:35 PM ---------- Previous post was at 05:54 PM ----------
decided to install 7.0 over my 6.0 install i just made and messed everything up. now im back to just trying to get gparted to run so i can reformat and start over.
bisharat said:
Could you post the link for the windows 10 drivers? also any idea on how to unlock the bootloader?
Click to expand...
Click to collapse
http://support.lenovo.com/kr/en/pro... and Software|Drivers and Software&beta=false
you can download yogabook win10(64bit) driver here.
edited--
you should change operating system dropdown menu from android to windows10
Hi & Happy New Year
Now it's possible to get root with android version
I have a YogaBook with Windows version ; Someone can make a backup Android version?
Maybe it's possible to create a dual boot with the windows version I cross the fingers :fingers-crossed:
Where and how?
ThomasHardy said:
Hi & Happy New Year
Now it's possible to get root with android version
Click to expand...
Click to collapse
someone can said me, where i found an android image? (original yoga book, of course) i try to install Remix OS and Android-x86 6.0-r1 released from Android-x86.org but, its can't run. graphics issues and reboot.
i install in a MicroSD and boot it booting yogabook hold volume up + power boton and select boot menu, but it fail on boot.
i have yoga book windows. any idea?
thanks
sorry for my english..
I'm exploring this as well.
Since the BIOS and drivers available (just tested with my serial#), it does seem like it would be relatively easy to dual-boot, provided you can get past the loader issue.
I've done many dual-boot setups, just not since the Win7 days, with the Win8 and forward it's gotten quite a bit trickier, the loader does a bunch of "extra" stuff, boot timing and such, to protect itself.
I've also never done an Android/Windows dual-boot, mostly just Win/Win or Win/Unix.
I think you'd have to figure out how to bootstrap these, so the custom loader can take over, and load from there, but this is a bit beyond my Android capabilities.
Has anyone even tried this? I assume the power/volume keys must work, to get at the loader?
Hi there !
I've just unlocked my Yoga Book's android bootloader and made a backup. I'm trying to install Windows 10 and replace Android with it. The problem is that I don't know how to boot the device from the USB drive.
Does anyone know how to do that ? Even if rooting is required ?
P.S. : I can't google it as all results link to "how to boot a PC from android device", which is the reverse...
Totjoss said:
Hi there !
I've just unlocked my Yoga Book's android bootloader and made a backup. I'm trying to install Windows 10 and replace Android with it. The problem is that I don't know how to boot the device from the USB drive.
Does anyone know how to do that ? Even if rooting is required ?
P.S. : I can't google it as all results link to "how to boot a PC from android device", which is the reverse...
Click to expand...
Click to collapse
simple...you can't do that! it's not possible to boot usb from android bootloader or recovery.
First, I'm not a newb, but I'm at my wits end so I'm swallowing my pride and posting this here.
I recently wiped my hard drive and reinstalled Windows 10. Prior to that Windows could see my v20, I could transfer files and ADB worked fine.
I installed command line tools to install ADB/drivers and tried both LG mobile 4.20 drivers and even tried the Intel drivers. Along the way I dusted off usbdeview to clear out the drivers and start over so likely further screwed things up.
I was able to eventually get ADB functional but no matter what I did the device wouldn't show up as a portable device under My PC.
I've finally said screw it and am currently reinstalling windows 10 from scratch for a fresh start.
So, looking for input as to the best way to proceed on fresh Windows install. Is best way to install adb/adb drivers by installing command line tools rather than full android studio? Does it matter what order I install LG drivers/ADB?
I'm running the notsostock 5.5 dirtysanta rooted on a verizon v20.
Thanks.
I haven't been able to get it to show as a portable device since flashing the NotSoStock rom. I'm on Windows 7, it was visible just fine prior to flashing and I haven't done anything to the computer in the meantime.
I've been assuming it was something goofy in the rom rather than windows drivers... It just hasn't been a big enough deal for me to monkey with, I don't often need that, and adb still works fine so I just push/pull stuff if I need to move anything...
ZachJohnson said:
I haven't been able to get it to show as a portable device since flashing the NotSoStock rom. I'm on Windows 7, it was visible just fine prior to flashing and I haven't done anything to the computer in the meantime.
I've been assuming it was something goofy in the rom rather than windows drivers... It just hasn't been a big enough deal for me to monkey with, I don't often need that, and adb still works fine so I just push/pull stuff if I need to move anything...
Click to expand...
Click to collapse
I came to the same conclusion about 4 hours ago. It was the NotSoStock rom that broke it. I wiped my v20 and installed the WETA rom and everything works perfectly. The dialer lock issue I had with that rom is gone. The hotspot issue is gone, etc. I've only been on it for a few hours, but it's definitely better than what I was on before.