Related
After testing CM10 for a while (thx codeworx) I now ported my NanoBoot image to CM10.
Changes compared to original CM10 boot:
"insecure" (means: / and /system mounted read-write (easy 'adb push' into /system ...), ro.secure = 0)
support for /system/etc/init.d/ init scripts
(somewhat) easy UMS access
Changes in r10:
Use 179:24 instead of 179:25 as address for UMS (fixes UMS on Windows)
to enable UMS for external SD with this boot.img it is enough to do:
Code:
setprop sys.usb.config mass_storage,adb
to return to MTP:
Code:
setprop sys.usb.config mtp,adb
TIP:
If you use Linux you may use some function like:
Code:
ums () {
if [[ $1 == "+" ]]; then
adb root
sleep 2
adb -s c1607c00051963f shell 'setprop sys.usb.config mass_storage,adb'
else
adb root
sleep 2
adb -s c1607c00051963f shell 'setprop sys.usb.config mtp,adb'
fi
}
'ums +' will enable UMS, 'ums -' will disable UMS on your tablet (not to mention it needs to be connected (...))
replace '-s c1607c00051963f' with '-s <your adb id>' - you get the id via 'adb devices'.
If you only got one adb-enabled device, you could remove '-s c1607c00051963f' from the commands.
If there's more than one device connected adb needs to know which one should receive the commands.
I did not yet have the time to modify framework-res.apk to add UMS to the list of options...
Flash using img/pit with either Odin or Heimdall. Or use zip to flash using CWM.
Images for Odin/Heimdall
PIT:
p3100.pit http://downloads.nanolx.org/P3110/p3100.pit
p3110.pit http://downloads.nanolx.org/P3110/p3110.pit
Stock CM10 Kernel:
NanoBoot-r10-CM10.img http://downloads.nanolx.org/P3110/NanoBoot-r10-CM10.img
Johnsel's CM10OC Kernel:
-No WiFi-
Zips for CWM
Stock CM10 Kernel:
NanoBoot-r10-CM10.zip http://downloads.nanolx.org/P3110/NanoBoot-r10-CM10.zip
Johnsel's CM10OC Kernel:
-No WiFi-
Tried this on my P3113 and it broke my WiFi.
Macadamia Daze said:
Tried this on my P3113 and it broke my WiFi.
Click to expand...
Click to collapse
Here with 3110 it works... if you provide me the original 3113 boot.img, I can re-pack one, that should work.
And it only works with Cyanogen Mod 10. Not on 9 or stock rom.
Setialpha said:
Here with 3110 it works... if you provide me the original 3113 boot.img, I can re-pack one, that should work.
And it only works with Cyanogen Mod 10. Not on 9 or stock rom.
Click to expand...
Click to collapse
I am using CM10, so here's the original boot.img for CM10 on the P3113. You don't need the stock one, do you?
Macadamia Daze said:
I am using CM10, so here's the original boot.img for CM10 on the P3113. You don't need the stock one, do you?
Click to expand...
Click to collapse
try with attached CWM zip.
n00b here.....what does this do??
Sent from my GT-P3113 using Tapatalk 2
F3AR420 said:
n00b here.....what does this do??
Sent from my GT-P3113 using Tapatalk 2
Click to expand...
Click to collapse
Just as first post says. This is a modified boot image for cyanogen mod 10 (no other ROM supported!) for galaxy tab 2 7", which makes / and /system read-write, adds support for init-scripts and adds pretty easy way to access UMS (USB Mass Storage) for external SD-Card.
According to your signature you're using an incompatible rom anyway - so don't use this.
@Macadamia Daze: now also tested with a 3100 I got my hands on: WiFi works. Dunno why it doesn't work with 3113 (I got no clue whether 3113 has some special WiFi stuff or whatever). Either way, please tell me, whether the attached one for 3113 (two posts above) works with WiFi.
Setialpha said:
@Macadamia Daze: now also tested with a 3100 I got my hands on: WiFi works. Dunno why it doesn't work with 3113 (I got no clue whether 3113 has some special WiFi stuff or whatever). Either way, please tell me, whether the attached one for 3113 (two posts above) works with WiFi.
Click to expand...
Click to collapse
Silly me; the problem was an incompatible kernel (Johnsel's). I returned to the default CM10 kernel and reflashed this, so now WiFi works. Still, in Windows it doesn't work properly. While it does create a new removable disk in Computer, it gives the "Please insert a disk into drive" error when I try to open it. Haven't tested in Linux yet, but based on my earlier tests with your previous UMS solution, it probably works.
---------- Post added at 08:12 PM ---------- Previous post was at 07:22 PM ----------
Ooh, I have good news! I used Device Manager to examine the blank drive letter on the computer, and it was recognizing it basically like an SD card reader with no SD card. So, I decided to poke around some of the files referenced in your UMS script from before to check their values. When I tried to open /sys/devices/virtual/android_usb/android0/f_mass_storage/lun/file, I got an error. Thinking it may not be working properly, I created a file on my computer with the contents "/dev/block/vold/179:24" and ADB pushed it to overwrite the broken file. Instantly, my SD card mounted on the PC. I hope this is useful information for you!
Macadamia Daze said:
Silly me; the problem was an incompatible kernel (Johnsel's). I returned to the default CM10 kernel and reflashed this, so now WiFi works. Still, in Windows it doesn't work properly. While it does create a new removable disk in Computer, it gives the "Please insert a disk into drive" error when I try to open it. Haven't tested in Linux yet, but based on my earlier tests with your previous UMS solution, it probably works.
---------- Post added at 08:12 PM ---------- Previous post was at 07:22 PM ----------
Ooh, I have good news! I used Device Manager to examine the blank drive letter on the computer, and it was recognizing it basically like an SD card reader with no SD card. So, I decided to poke around some of the files referenced in your UMS script from before to check their values. When I tried to open /sys/devices/virtual/android_usb/android0/f_mass_storage/lun/file, I got an error. Thinking it may not be working properly, I created a file on my computer with the contents "/dev/block/vold/179:24" and ADB pushed it to overwrite the broken file. Instantly, my SD card mounted on the PC. I hope this is useful information for you!
Click to expand...
Click to collapse
I see... 179:24 is the sdcard itself, 179:25 (what I use) is the first partition on the sdcard... unixoid systems don't care about that, but windows seems too... I'm gonna test with 179:24 on Linux and if it works there (I'd say yes even without testing, I provide an update). Thanks for testing.
r10 is now online - fixes UMS issue on Windows.
I can't get WiFi to work with Johnsel's CM10OC Kernel - so I skiped uploading those image/zip...
You can find me in Freenode #cyanogenmod-dev if you care to sort out what's happening with the wifi on my kernel
Johnsel said:
You can find me in Freenode #cyanogenmod-dev if you care to sort out what's happening with the wifi on my kernel
Click to expand...
Click to collapse
It fails to load something and therefore can't be enabled, don't remember exact log-message right now.
I'll contact you, when I'm hacking around the next time.
This is pretty interesting.
Two things
1-Doesn't CM10 already support init.d scripts?
2-Would it be possible to swap the mountpoints for the "internal" sdcard space and the actual microSD card slot? My current method of re-mounting things right after boot is OK but not very elegant.
DivinityCycle said:
This is pretty interesting.
Two things
1-Doesn't CM10 already support init.d scripts?
2-Would it be possible to swap the mountpoints for the "internal" sdcard space and the actual microSD card slot? My current method of re-mounting things right after boot is OK but not very elegant.
Click to expand...
Click to collapse
1 - atleast not via boot.img - that's why I added it.
2 - I have an older tablet I used before (ARNOVA 7C G2) it worked with this one, so it should work with this one, too. But you should never enable UMS while some app is running... On that other tablet I had to use EXT2 or EXT4 on SD-Card else all that permission stuff didn't work (FAT only has very basic permission rules for files). Also I recommend using second partition of SD-Card for /data. (first gets used as external storage and is managed by vold - at least that is what I did on my other tablet).
I attached init.espresso.rc, so that you can play around with the mount points (re-send me the file after you're done and I can provide you a flashable zip).
Setialpha said:
1 - atleast not via boot.img - that's why I added it.
2 - I have an older tablet I used before (ARNOVA 7C G2) it worked with this one, so it should work with this one, too. But you should never enable UMS while some app is running... On that other tablet I had to use EXT2 or EXT4 on SD-Card else all that permission stuff didn't work (FAT only has very basic permission rules for files). Also I recommend using second partition of SD-Card for /data. (first gets used as external storage and is managed by vold - at least that is what I did on my other tablet).
I attached init.espresso.rc, so that you can play around with the mount points (re-send me the file after you're done and I can provide you a flashable zip).
Click to expand...
Click to collapse
That's the thing I have been wrestling with lately, what's "the best" way to manage this stuff?
It seems like the main thing that needs to be done for legacy purposes is linking the regular /storage/sdcard0/data directory over to /storage/sdcard1/data/.
One idea I had was to format the "internal" sdcard (/storage/sdcard0) with ext4, which would allow symlinks to exist there, then just remove the data directory and replace it with a symlink that points to /storage/sdcard1/data.
From what I've read, ext4 is supposed to be a better, higher performance solution, so I'm kinda curious to try it out.
It would make UMS pretty worthless to Windows guys like me, but I basically do everything via network anyways (SFTP mostly).
Is it possible to control the file systems used on the internal & external sdcards in the init? I didn't look too deeply at it cuz I don't know how to rebuild a boot.img (at least not yet)
Tested this with the current AOKP JB nightly, and it also breaks WiFi. I'm trying now to keep the rom and restore the CM10 NanoBoot backup. Fingers crossed it will be stable.
here simple application that will enabled UMS mode for External sdcard
root needed.
how to use:
safe way on version 2.5 is :
enable UMS Mode when cable usb is unplug
Back to Charge mode when cable usb is unplug
safe way on version 3.0 is :
do it on condition usb plugged
note:
if you plug into player or some device player , and you found that it cannot found the USB drive
in this case just do this
settings -> connectivity -> usb connection type
and do press or repress the "Charge Only"
in version 3.0 you will notice 1 triangle on task bar, its normal , it telling you mass storage is currently unmount
2 icon on task bar is telling you the mass storage successful unmount you can take it out
those of notice are normal if we do unmount the mass storage in android api level.
all the information about how to do it i found on XDA forum.
i do some research also code this app
version 2.1
fix sometime fail to mount back to external_sd folder
version 2.5
fix sometime got to bluescreen on windows
version 3.0
fix bluescreen on windows
using different approach to unmount the external SD card
version 3.2
bring back native method to mount and unmount, its speed up abit when using native method
by check the box to enable native mode
version 3.3
support Jelly Bean
thanks are goes to XDA Members
UMS_mode.apk
UMS_MODEv2.1.apk
UMS_Modev2.5.apk
UMS_ModeV3.0.apk
UMS_ModeV3.2.apk
UMS_ModeV3.3.apk
its working good tnx mate
Thanks for app. It is amazing
Best regards,
It does not mount back SDcard to /mnt/sdcard/external_sd after disconnect, so have to reboot after use it.
MTP is working but external_sd is empty.
your welcome guys,
@m0b :
i think you forget click on "back to charge mode"
bullghost said:
your welcome guys,
@m0b :
i think you forget click on "back to charge mode"
Click to expand...
Click to collapse
No, i try it, but it does not help, only reboot.
m0b said:
No, i try it, but it does not help, only reboot.
Click to expand...
Click to collapse
try the version 2.1,
i fix it
bullghost said:
try the version 2.1,
i fix it
Click to expand...
Click to collapse
now ist fine for me, tnx!
m0b said:
It does not mount back SDcard to /mnt/sdcard/external_sd after disconnect, so have to reboot after use it.
Click to expand...
Click to collapse
With the first version I have access to the card. After disconnecting I have to reboot the phone, so I can regain access to the card.
bullghost said:
try the version 2.1, i fix it
Click to expand...
Click to collapse
Version 2.1 gives reproducible blue screens with Win7 x64 SP1 at the first link when I confirm the superuser, or in further tries, when connect the USB cable.
Only uninstalling the apk helps to solve the problem.
A little off topic:
After UMS_mode.apk does not work for me, here is another way to access both memory cards in the P880 (and any other Android-Device) from Windows OS:
Install Total Commander (Shareware): http://www.ghisler.com
Install Total Commander Plugin "Android ADB" (Freeware): http://www.totalcmd.net/plugring/android_adb.html
Android device driver has to be installed too!
Through links, both SD-Cards appear with 3 differen pathes in the P880 operating system.
The external SD-Card has its mount point in (!) the internal SD-card:
Code:
Internal SD-Card:
\\\ADB\LG-P880\data\media\
\\\ADB\LG-P880\mnt\sdcard\
\\\ADB\LG-P880\sdcard\
2. external SD-Card:
\\\ADB\LG-P880\data\media\external_sd\
\\\ADB\LG-P880\mnt\sdcard\external_sd\
\\\ADB\LG-P880\sdcard\external_sd\
Bud Cord said:
A little off topic:
After UMS_mode.apk does not work for me, here is another way to access both memory cards in the P880 (and any other Android-Device) from Windows OS:
Install Total Commander (Shareware): http://www.ghisler.com
Install Total Commander Plugin "Android ADB" (Freeware): http://www.totalcmd.net/plugring/android_adb.html
Android device driver has to be installed too!
Through links, both SD-Cards appear with 3 differen pathes in the P880 operating system.
The external SD-Card has its mount point in (!) the internal SD-card:
Code:
Internal SD-Card:
\\\ADB\LG-P880\data\media\
\\\ADB\LG-P880\mnt\sdcard\
\\\ADB\LG-P880\sdcard\
2. external SD-Card:
\\\ADB\LG-P880\data\media\external_sd\
\\\ADB\LG-P880\mnt\sdcard\external_sd\
\\\ADB\LG-P880\sdcard\external_sd\
Click to expand...
Click to collapse
thanks bro , here version 2.5 will fix the bluescreen
Thanks a lot! useful for syncing with doubleTwist. can't stand the LG PC Suite its too slow.
Sent from my LG-P880 using xda premium
version 3.0 relase fix bluescreen again,
if you suffer on always media scanning you can turn it off on
setting -> application -> find "Media Storage" -> disable
Wow!
This is the greatest thing created for this phone so far.
MTP is painfully slow, doesn't work with cars/stereos/etc, requires installing drivers everywhere I go, crashes all the time, doesn't allow access with a file path, and somehow caused my sd card to wipe itself three times in two weeks, so this was a major issue for me that was making me regret buying the phone.
Initially after installing this app (v3.0), I had to repeatedly toggle UMS/MTP mode and plug/unplug my phone from the computer several times before it finally started working, but now it's perfect.
If you have a paypal or flattr link, and I'll send something your way. Or put it on the Play Store so I can buy it and update
Thanks!
thanks
ben! said:
This is the greatest thing created for this phone so far.
MTP is painfully slow, doesn't work with cars/stereos/etc, requires installing drivers everywhere I go, crashes all the time, doesn't allow access with a file path, and somehow caused my sd card to wipe itself three times in two weeks, so this was a major issue for me that was making me regret buying the phone.
Initially after installing this app (v3.0), I had to repeatedly toggle UMS/MTP mode and plug/unplug my phone from the computer several times before it finally started working, but now it's perfect.
If you have a paypal or flattr link, and I'll send something your way. Or put it on the Play Store so I can buy it and update
Thanks!
Click to expand...
Click to collapse
thank you , as far as you like it , is enough for me
ben! said:
This is the greatest thing created for this phone so far.
Click to expand...
Click to collapse
I can not confirm unfortunately.
I wanted to give the app still a second chance and have installed 3.0.
Then I restarted the phone, without starting the APP before.
Now it hangs on startup LG boot logo.
Even without the second SD card the same problem.
Any idea without factory reset or flashing KDZ?
My phone is still stuck in boot, but I have an access via adb shell to system.
Unfortunately I have no permission to access "/data"
Could anyone tell me the aplication name of this UMS-Tool under "/data/data" ?
I only found "com.noshufou.android.su" in classes.dex, but don't know wether this is right:
Code:
[email protected]:/data $ run-as com.noshufou.android.su
run-as com.noshufou.android.su
run-as: Package 'com.noshufou.android.su' is unknown
[email protected]:/data $
Ok, I guess it's not quite working perfectly for me now that I've used it a bit more, but I still love it.
1) it's really tricky to get it working initially. I almost always have to toggle it multiple times and sometimes reconnect the usb cable.
2) like someone else mentioned, it never remounts the SD card so I have to restart the phone to get it working again after I'm done.
I have not had any problems on boot like BudCord.
I'm running stock firmware 10f.
Anyone have v3 hosted any where else? I can't download from media fire.. no captcha support..
Tried stock browser, dolphin, and chrome..
Any chance to get it working on mac os x (10.6.8) ?
For the moment it is the only default i found with this phone : the lack of "connections" with Apple's OS :/
PS : I searched on the web and I found a solution for Mac OS X users : Android File Transfer (on the official website).
Sorry I can not the url because I am new on this forum.
Hey Guys
So I thought I found a great deal on craigs list... touch pad for a good price... but it turns out I bought more then I barganed for. To cut to the chase the old owner seems to have a semi installed CM9 installed, but the something messed up and now im the new owner... :crying:
I tried to delete this guys photos in WebOS but he keeps coming back to huant me! IT seems that all the files are locked in read only mode and factory restores wont work
I tried this post
[Guide] Factory condition restoration / Downgrade to webOS 3.0.0
http://forum.xda-developers.com/showthread.php?t=1426244
and
[HOWTO][CM7 ALPHA2.1] FIX - sdcard storage mounts as readonly
http://forum.xda-developers.com/showthread.php?t=1322127
so far with no luck..
When i Tried Doctor os it fails at %12
Any suggestions guys?
PLEASE HELP
I once royally screwed mine by using windows to format it. You could try that...
WebOS doctor and the novaterm will get it going after that...
Just an idea...
Sent from my SAMSUNG-SGH-T989 using xda premium
I tried both WebOS = Failed at 12%
Novaterm =factory reseting and some other stuff
Please help :crying:
-SGA- said:
I once royally screwed mine by using windows to format it. You could try that...
WebOS doctor and the novaterm will get it going after that...
Just an idea...
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Did you try mounting the SD in windows through webos and then right clicking on the drive and click format?
Sent from my aokp_tenderloin using xda premium
I'm able to mount and format but when I reboot that guys photo is back Along with the system files and folders
QUOTE=-SGA-;33722106]Did you try mounting the SD in windows through webos and then right clicking on the drive and click format?
Sent from my aokp_tenderloin using xda premium[/QUOTE]
Update
So I was able to boot into clock work with this thread :
http://forum.xda-developers.com/showthread.php?t=1302433
Comman used : novacom boot mem:// < uImage.ClockworkMod
Once in there I tried all the various options
format sd card / fix permissions / wipe X options
I also tried : CM7: Fixes for SDCARD issues
from : http://rootzwiki.com/topic/13277-cm7-fixes-for-sdcard-issues/page__st__90
but when i load files into the sdcard via mounting through clockwork Im unable to install from zip from SD card... due to the read only nature of this current drive...
My new Lead on this problem is from this thread : http://newbrightidea.com/2011/08/26/hacking-the-touchpad-part-1/
what caught my eye was his statement about mounted read only by default... (see below)
in theory if i follow his steps i may be able to unlock this read only bug and fully install CM9... Stay tuned.
STARTING OPENSSH SERVER
Harder than it sounds! The root filesystem is mounted read-only by default, but you can hack your way around that with:
mount -w -o remount /
Then, add the sshd user and group to /etc/passwd and /etc/group
Setup an ssh key using ssh-keygen and set the “HostKey” property in sshd_config to point to the private key.
If you didn’t remount the root FS as read-write, you need to set UsePrivilegeSeparation to true.
Start sshd like so:
krunktor said:
I'm able to mount and format but when I reboot that guys photo is back Along with the system files and folders
QUOTE=-SGA-;33722106]Did you try mounting the SD in windows through webos and then right clicking on the drive and click format?
Sent from my aokp_tenderloin using xda premium
Click to expand...
Click to collapse
[/QUOTE]
Removed.
emuX said:
Removed.
Click to expand...
Click to collapse
EmuX
are you refering to this post:
http://forum.xda-developers.com/showpost.php?p=24047078&postcount=3
Yes, I was. That's why I removed the post since you'd already found it. Although I didn't do all the steps suggested - just the first few and then ran webos doctor with it all uninitialised.
I just did:
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
mkdosfs -f 1 -s 64 /dev/store/media
Click to expand...
Click to collapse
(Oh, and I've got a 32gb device in case that makes any difference.)
Also, how long did you wait for webos doctor to complete? After using that approach I left mine running for a long time at 8% or 12% (I forget which) and it eventually carried on.
Well as the Title say through my dumb idea of using rm -rf / on my linux laptop I managed to wipe my Linux Laptop HDD together with every partition of my LG G Watch R since I had it connected. It doesn't turn on anymore since bootloader is misssing and is only found as broken usb device in windows and when suing lshw on Linux it loads forever. Any way to maybe low level write the Bootloader or recovery again so that I can create all the partitions and stuff again?
Found something with lshw now but didn't find anything too helpful yet online
Beschreibung: Allgemeines USB-Gerät
Produkt: QHSUSB__BULK
Hersteller: Qualcomm CDMA Technologies MSM
Physische ID: 3
Bus-Informationen: [email protected]:3
Version: 0.00
Fähigkeiten: usb-2.00
Konfiguration: driver=qcserial maxpower=2mA speed=480Mbit/s
Can anyone with a working LG G Watch R please runt his command and send me the file?
dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1M count=200
Did you run him up ?
Maybe that will help You :
http://forum.xda-developers.com/showthread.php?t=2683073
As a tip...
I can share with files in case.
1 find way to load files on him . Worst then it is atm can not be
Also catch that:
http://forum.xda-developers.com/g-watch-r/help/restore-download-mode-t3124633
Hope it will help - GL!
Ping if sth.
gucio1200 said:
Did you run him up ?
Maybe that will help You :
http://forum.xda-developers.com/showthread.php?t=2683073
As a tip...
I can share with files in case.
1 find way to load files on him . Worst then it is atm can not be
Also catch that:
http://forum.xda-developers.com/g-watch-r/help/restore-download-mode-t3124633
Hope it will help - GL!
Ping if sth.
Click to expand...
Click to collapse
Thanks for the answer. I had tried to get my broken watch to be recognized as Mass storage which can somehow be achieved through Qualcomm's diagnostic ports but didn't succeed. Meanwhile I bought a new Motherboard for my Watch so I can finally use it again. All that's left now is to wait for Android Wear 2.0
In the past 3 months or so I noticed that my Mi5 3GB 32GB is not recognized by my PC anymore. I didn't care too much because I hardly connect my phone to PC.
I was running the lastest xiaomi.eu Rom unrooted.
So on Thursday, I deleted my OS by mistake, therefore I do not get past the Mi Logo.
I can boot into TWRP Recovery & Fastboot however, there is not code when using CMD adb/fastboot devices such as 1cwe3f23.
Also, I read about the EOL method aka test point method, to force a connection as Qualcomm driver with no success. Different PCS dont recognize any drivers.
The battery is not an issue because I can easily charge my phone to 100% and it can hold its charge, therefore I do not think it is a battery related issue.
What i did so far :
- used 3 differenct USB C cables and PC -> phone still not recognized
- Installed all lastest driver on Drivers -> phone still not recognized
- tried to use the test points method -> phone still not recognized
- tried Miflash tool -> phone is still not recognized
- tried Mi PC Guide -> didn't work either
Then I read somewhere that I can use a OTG cable with a pen drive
- OTG storage is not recognized in TWRP recovery and cannot be selected. [OTG STORAGE 0MB even if different pen drives are connected]
SO my Main problem is not the phone itself, it is that I cannot get any data onto the internal memory because I can't get past TWRP.
Please help me out since I really struggling with this problem for the past 7 days and I'm desperate now for any kind of help.
Greetings and thanks in advance.
amando1991 said:
SO my Main problem is not the phone itself, it is that I cannot get any data onto the internal memory because I can't get past TWRP.
Click to expand...
Click to collapse
What do you mean by "can't get past TWRP"? Is it that you can't flash any ROM to system?
You have fastboot and TWRP, so things are likely fine. Rather than use Windows, you might have more luck running linux inside VirtualBox (plenty of guides around XDA). If you can sudo fastboot devices in linux, you should be good to go. Otherwise, the error reporting is often richer/simpler in linux.
Hi bro
same as me, 4 days ago...
system, vendor error
flashing stock rom miui9 via twrp
although the error twrap will only provoke usb computer,
if it works usb computer, try flashing by using miflash...
goodluck
Sory bad englis
moo113 said:
What do you mean by "can't get past TWRP"? Is it that you can't flash any ROM to system?
You have fastboot and TWRP, so things are likely fine. Rather than use Windows, you might have more luck running linux inside VirtualBox (plenty of guides around XDA). If you can sudo fastboot devices in linux, you should be good to go. Otherwise, the error reporting is often richer/simpler in linux.
Click to expand...
Click to collapse
I did as you recommended and used Ubuntu. However also there the system didn't recognize the phone when plugged. It may because I am not fully familiar with Ubuntu. I would appreciate if you could point me in the direction of a tutorial.
same as me, 4 days ago...
system, vendor error
flashing stock rom miui9 via twrp
although the error twrap will only provoke usb computer,
if it works usb computer, try flashing by using miflash...
Click to expand...
Click to collapse
could you be more precise please? How did you overcome not having a PC conncetion?
Currently, I am not able to transfer any kind of data to the phone either by PC or OTG. Furthermore, the internal storage is completely empty after wiping everything by mistake.
I have twrp working fine, but without any data on the device, I cannot use it. Also, the device only stays in fastboot for roughly 20 secs before it turns off.
any help is welcomed. Thank you
EDIT : I got Ubuntu to work but its the same process. My phone is not recognized and running the command adb devices gives me
"list of devices" .... thats not! Nothing ! usally there is the code Phones ID but nothing there
amando1991 said:
EDIT : I got Ubuntu to work but its the same process. My phone is not recognized and running the command adb devices gives me
"list of devices" .... thats not! Nothing ! usally there is the code Phones ID but nothing there
Click to expand...
Click to collapse
A number of different issues could be here.
#1 Firstly, ensure you've installed openvm tools and reboot. This should enable things like hardware pass through.
$ apt-get install open-vm-tools open-vm-tools-desktop
$ sudo init 6
Then, follow these instructions for the pass through (may be slightly different, but very similar) https://forum.xda-developers.com/showthread.php?t=570452
#2 Type "adb" and see what version is in use in the first line of output. If it's 1.0.0.32 or older, it might be an issue. Try installing the following packages:
$ sudo apt-get install android-tools-fastboot android-tools-adb
You might need to find a newer version elsewhere, Ubuntu repos are often old. Google around for 1.0.36 or newer. This could solve your issue.
#3 Ensure you have the necessary rules for the Mi 5. There's a few different hardware models. The Arch Wiki can walk you through it better than I can: https://wiki.archlinux.org/index.php/android#Connect_device (ignore the package hyperlinks, they're arch-specific). Only do this if you've properly configured the pass through from #1. Do F"igure out device IDs" and then "Adding udev Rules". Instead of the "udevadm" command run
$ sudo service udev restart
If you're still not detected, no idea.
moo113 said:
A number of different issues could be here.
#1 Firstly, ensure you've installed openvm tools and reboot. This should enable things like hardware pass through.
$ apt-get install open-vm-tools open-vm-tools-desktop
$ sudo init 6
Then, follow these instructions for the pass through (may be slightly different, but very similar) https://forum.xda-developers.com/showthread.php?t=570452
#2 Type "adb" and see what version is in use in the first line of output. If it's 1.0.0.32 or older, it might be an issue. Try installing the following packages:
$ sudo apt-get install android-tools-fastboot android-tools-adb
You might need to find a newer version elsewhere, Ubuntu repos are often old. Google around for 1.0.36 or newer. This could solve your issue.
#3 Ensure you have the necessary rules for the Mi 5. There's a few different hardware models. The Arch Wiki can walk you through it better than I can: https://wiki.archlinux.org/index.php/android#Connect_device (ignore the package hyperlinks, they're arch-specific). Only do this if you've properly configured the pass through from #1. Do F"igure out device IDs" and then "Adding udev Rules". Instead of the "udevadm" command run
$ sudo service udev restart
If you're still not detected, no idea.
Click to expand...
Click to collapse
Thank you again for the help!
Unfortunately, it appears that my device is still not recognized by either Ubuntu or Win10.
I Have taken the necessary steps to install Ubuntu and update the adb drivers (1.0.39) but still no luck so far.
It really pisses me off since I was stupid enough to wipe the internal storage ☹ and not I am not able to transfer any data to the devices again.
Any other out of the box ideas?
amando1991 said:
Thank you again for the help!
Unfortunately, it appears that my device is still not recognized by either Ubuntu or Win10.
I Have taken the necessary steps to install Ubuntu and update the adb drivers (1.0.39) but still no luck so far.
It really pisses me off since I was stupid enough to wipe the internal storage ☹ and not I am not able to transfer any data to the devices again.
Any other out of the box ideas?
Click to expand...
Click to collapse
You configured the USB pass through to your Ubuntu host? Double check you followed #3, and then run sudo fastboot devices. That step is tricky for some.
Reconnect your phone to your Ubuntu host (in fastboot) and run "dmesg -T", see what errors are present. If you have no errors, I would image it's a configuration issue. Other than that I'm out of ideas.
moo113 said:
You configured the USB pass through to your Ubuntu host? Double check you followed #3, and then run sudo fastboot devices. That step is tricky for some.
Reconnect your phone to your Ubuntu host (in fastboot) and run "dmesg -T", see what errors are present. If you have no errors, I would image it's a configuration issue. Other than that I'm out of ideas.
Click to expand...
Click to collapse
OMFG!!! First of all, thank you for support and your patience. I really appreciate it.
HOWEVER, all it was is that the USB PORT was full of dust( literally tons!) which appears to have allowed to charge the phone but seemed to have cloaked up some part of the responsibile for a usb connection to a computer.
Stupid me should have known this because the usb port was kinda wobbly which I had mistaken for degradation using the phone for almost 2 years
MANY THANKS!
moo113 said:
What do you mean by "can't get past TWRP"? Is it that you can't flash any ROM to system?
You have fastboot and TWRP, so things are likely fine. Rather than use Windows, you might have more luck running linux inside VirtualBox (plenty of guides around XDA). If you can sudo fastboot devices in linux, you should be good to go. Otherwise, the error reporting is often richer/simpler in linux.
Click to expand...
Click to collapse
Hey , I was researching about my issue and came up to this. I'd be really glad if you can sort me out with this. I have the same mobile , by mistakenly wiped out the phone including the internal storage , my pc does not detect the device , and whenever i go to fastboot mode to try something like miflash , it goes back to twrp after 15 seconds. Also , i tried several OTG's but none of them get detected on TWRP , and I am stuck on this thing for almost a week now . Please guide me on how to sort this out . i basically just downloaded adb files , miflash , etc from the internet and never reinstalled them. also i used several usb c cables to connect to pc and even then device manager does not detect it . thank you . i would really appreciate your reply.