Related
I've had the tablets for a few weeks and would like to root it. It has android 4.2.2 but doesn't have an option to connect to pc as it doesn't have a micro usb port on the tablet. The charging port is proprietary and uses a AC adapter style cord similar to a laptop one so it doesnt have a usb end. Am I just SOL?
UPDATE: see post #8 by groumfi
UPDATE 2: thanks to member Taiz for the info. You can now root using an app found at www.towelroot.com No cable required
I returned mine a long time ago but this is good news regardless
Sent from my HP SlateBook 10 x2 PC using Tapatalk 4
Anyway to root HP slatebook x2?
aznmode said:
I've had the tablets for a few weeks and would like to root it. It has android 4.2.2 but doesn't have an option to connect to pc as it doesn't have a micro usb port on the tablet. The charging port is proprietary and uses a AC adapter style cord similar to a laptop one so it doesnt have a usb end. Am I just SOL?
Sent from my HP SlateBook 10 x2 PC using Tapatalk 4
Click to expand...
Click to collapse
Hello,
Apparently these two pages present two procedures for root any android by the sole procedure that allows currently Slatebook: recovery> apply update from zip (only root, no kernel or rom change):
Someone has tested or can test?:
http://forum.xda-developers.com/showthread.php?t=2358996
http://forum.xda-developers.com/showthread.php?t=1746794
Greetings
Daifex said:
Hello,
Someone has tested or can test?:
Greetings
Click to expand...
Click to collapse
Thanks for that, mate. Looks like that someone has tried this but it doesn't work.
Alternatively it has been suggested that root access can be gained from the updated file from HP: http://h10025.www1.hp.com/ewfrf/wc/...dlc=en&lc=en&os=4153&product=5400087&sw_lang= but unfortunately I'm not a developer nor technically inclined so I wouldn't know how to extract it. However the file is available from the above link if someone know how to grab and tinker with it.
GrievousMcG said:
Thanks for that, mate. Looks like that someone has tried this but it doesn't work.
Alternatively it has been suggested that root access can be gained from the updated file from HP: http://h10025.www1.hp.com/ewfrf/wc/...dlc=en&lc=en&os=4153&product=5400087&sw_lang= but unfortunately I'm not a developer nor technically inclined so I wouldn't know how to extract it. However the file is available from the above link if someone know how to grab and tinker with it.
Click to expand...
Click to collapse
a few of us are anxiosly waiting for this great tablet to get root access. I think the only way to motivate senior xda developers to buy this tablet would be if Hp drop off the price to $299.
gdfrisco said:
a few of us are anxiosly waiting for this great tablet to get root access. I think the only way to motivate senior xda developers to buy this tablet would be if Hp drop off the price to $299.
Click to expand...
Click to collapse
hoho....how much we must wait that? One year? two?
we just need to get HP signature to sign update.zip file...
some informations
Here is the detail or the official OS that we got with the slatebook 10 x2 :
Android version 4.3
3.4.57-g61ce4c9
[email protected] #1
Wed Dec 11 00:41:15 CST 2013
Build number
4.3-17r20-03-23
Many of us can not connect dirrectly the device to a PC. So it will be better to root it with usb flash drive or a SD Card but an apk like Framaroot would the best. I'm posting this to help anyone trying to make this for all slatebook users. There is still hope people!
Hp still don't give us the ability to purchase a usb wire. The. French clients service said that no wire is available. There is still hope to find other devices with the same kind of proprietary port but the next problem will be to find a device with the same kernel.
Envoyé de mon C5303 en utilisant Tapatalk
How to unlock and root HP SlateBook x2
Hi there,
We finally achieve root on this SlateBook x2. Full story here: http://forum.xda-developers.com/showthread.php?t=2402681&page=59
Sum-up
Buy the HP proprietary cable
Unlock bootloader
Boot CWM recovery I built for the SlateBook x2
Push SuperSU thru sideload
Detailed steps
You need to buy the Micro-USB dedicated cable, HP spare part number 728141-001
You can find it at http://www.eetgroup.com/. Frenchies can order it here: http://fr.eetgroup.com/i/728141-001-HP-MICRO-USB-TO-USB-CABLE. The guys are located at St Ouen (93) and it is possible to pick-up the cable at their office to save shipping costs. Even w/o shipping costs I had to pay 57,30 € which is quite expensive for such a cable.
Anyway, once you have the $$$ cable, proceed as follow to root the device:
You'll need adb installed and working onto to your computer. This could be done by installing the full Android SDK or a light version from here: http://forum.xda-developers.com/showthread.php?p=42407269
Normally, the package should install the naked USB drivers. If this not the case have a look at http://forum.xda-developers.com/showthread.php?t=2386956 and download and install the naked USB drivers
Into your home directory (ie: C:\Users\<username> for Windows or /home/<username> for Linux) you should find a .android directory. Check the adb_usb.ini file within this directory and ensure that content is 0x03F0
Then, enable USB debugging into the Developper options of Android parameters
Once done, connect to the PC with the dedicated cable, wait for a moment for adb drivers to install
Once installed, check that adb can detect the tablet with by entering: adb devices
If it is detected, reboot in bootloader mode: adb reboot bootloader
Once in bootloader, unplug / plug again the tablet and wait for adb drivers to install. Then unlock the bootloader: fastboot -i 0x03F0 oem unlock. WARNING: this will reset your tablet to factory default and loose all your data
Once bootloader is unlocked, reboot your tablet and perform the initial android setup
Tun USB debugging on again and connect the tablet
Reboot to bootloader: adb reboot bootloader
Boot downloaded recovery: fastboot -i 0x03F0 boot recovery_maya-0.1.img
Wait a couple of seconds for CWM to start on the tablet
On the tablet, select Install zip and then Install zip from sideload
Once sideload is ready, install UPDATE-SuperSU-v1.94.zip: adb sideload UPDATE-SuperSU-v1.94.zip
Wait for install to finish, reboot and enjoy
Notice
For those running Ubuntu flavor Linux, no need to download any drivers (assuming you've installed android-tools-adb and android-tools-fastboot packages). Just add 0x03F0 to your ~/.android/adb_usb.ini file so that adb will detect the tablet.
I have updated my device to 4.3 to ensure this is working properly. For those who still have 4.2.2, this method will also work as developper Chainfire has implemented 4.3 and olders in SuperSU zip
I did the build of CWM by my own and it is not 100% fully functional (still have issue mounting internal storage). But it is usable enough to install SuperSU zip thru sideload
DO NOT FLASH this version of CWM. I've not tested flashing and it might brick your device
Edit 23-Aug-14 : I flashed it thru Flashify and it boots. I also installed Quick Boot (Reboot) to easily reboot to recovery. Only issue is that it does not mount internal storage, but with external SD, I was able to perform a Nandroid backup-restore operations
Quick question please ref your post
I have received the cable you mentioned (HP 728141-001) and although it connects, the LED on the cable does not illuminate. Does yours light up? Cheers.
groumfi said:
Hi there,
We finally achieve root on this SlateBook x2. Full story here: http://forum.xda-developers.com/showthread.php?t=2402681&page=59
Sum-up
Buy the HP proprietary cable
Unlock bootloader
Boot CWM recovery I built for the SlateBook x2
Push SuperSU thru sideload
Detailed steps
You need to buy the Micro-USB dedicated cable, HP spare part number 728141-001
You can find it at http://www.eetgroup.com/. Frenchies can order it here: http://fr.eetgroup.com/i/728141-001-HP-MICRO-USB-TO-USB-CABLE. The guys are located at St Ouen (93) and it is possible to pick-up the cable at their office to save shipping costs. Even w/o shipping costs I had to pay 57,30 € which is quite expensive for such a cable.
Anyway, once you have the $$$ cable, proceed as follow to root the device:
You'll need adb installed and working onto to your computer. This could be done by installing the full Android SDK or a light version from here: http://forum.xda-developers.com/showthread.php?p=42407269
Normally, the package should install the naked USB drivers. If this not the case have a look at http://forum.xda-developers.com/showthread.php?t=2386956 and download and install the naked USB drivers
Into your home directory (ie: C:\Users\<username> for Windows or /home/<username> for Linux) you should find a .android directory. Check the adb_usb.ini file within this directory and ensure that content is 0x03F0
Then, enable USB debugging into the Developper options of Android parameters
Once done, connect to the PC with the dedicated cable, wait for a moment for adb drivers to install
Once installed, check that adb can detect the tablet with by entering: adb devices
If it is detected, reboot in bootloader mode: adb reboot bootloader
Once in bootloader, unplug / plug again the tablet and wait for adb drivers to install. Then unlock the bootloader: fastboot -i 0x03F0 oem unlock. WARNING: this will reset your tablet to factory default and loose all your data
Once bootloader is unlocked, reboot your tablet and perform the initial android setup
Tun USB debugging on again and connect the tablet
Reboot to bootloader: adb reboot bootloader
Boot downloaded recovery: fastboot -i 0x03F0 boot recovery_maya-0.1.img
Wait a couple of seconds for CWM to start on the tablet
On the tablet, select Install zip and then Install zip from sideload
Once sideload is ready, install UPDATE-SuperSU-v1.94.zip: adb sideload UPDATE-SuperSU-v1.94.zip
Wait for install to finish, reboot and enjoy
Notice
For those running Ubuntu flavor Linux, no need to download any drivers (assuming you've installed android-tools-adb and android-tools-fastboot packages). Just add 0x03F0 to your ~/.android/adb_usb.ini file so that adb will detect the tablet.
I have updated my device to 4.3 to ensure this is working properly. For those who still have 4.2.2, this method will also work as developper Chainfire has implemented 4.3 and olders in SuperSU zip
I did the build of CWM by my own and it is not 100% fully functional (still have issue mounting internal storage). But it is usable enough to install SuperSU zip thru sideload
DO NOT FLASH this version of CWM. I've not tested flashing and it might brick your device
Click to expand...
Click to collapse
ericritou said:
I have received the cable you mentioned (HP 728141-001) and although it connects, the LED on the cable does not illuminate. Does yours light up? Cheers.
Click to expand...
Click to collapse
No, no lights
Finally received the cable too! Not going to root it now (but thanks for the procedure!).. I really just wanted an ADB connection.
Some notes:
1. You have to connect the cable to the tablet itself not the base (stupid but took me some time to figure this out as I never use it without the base).
2. I can't get the driver to work on Win7 (device not recognized even though I can see the files), but it works on Ubuntu.
3. You do have to edit the usb_adb.ini and *then* connect the cable, normally you should have an authorization on tablet. Don't do "android update adb" as it wipes the ini file.
4. The light does not seem to ever light up, actually I don't even think it's a light, maybe it's just something to show which side goes up...
Jerem
Well thankx for setting up the guide. Since I'm EU spain I'll try to get a hold on one of those usb cables. Really want root for fps meter and TinyCore I think it's called. It would compliment my gaming on the device very well.
Maybe a stupid questions......
When using this expensive USB cable can you charge the tablet also with it or is it only for USB communication?
B3rt said:
Maybe a stupid questions......
When using this expensive USB cable can you charge the tablet also with it or is it only for USB communication?
Click to expand...
Click to collapse
Definitely not a stupid one. You can NOT charge the tablet, it is only working as a data USB cable
groumfi said:
Definitely not a stupid one. You can NOT charge the tablet, it is only working as a data USB cable
Click to expand...
Click to collapse
No charging yet, but HP is working on a 99$ cable that will do the charge of the tablet too :laugh:
Does someone know if some custom roms developpers are interested with the Slatebook ?
It's a pity at this time because we can not clearly see the end of the tunnel... Not rooted mine because I just don't want to miss the 32Go internal...
Popol640001 said:
Not rooted mine because I just don't want to miss the 32Go internal...
Click to expand...
Click to collapse
Do you mean due to the factory reset done when unlocking bootloader ?
groumfi said:
Do you mean due to the factory reset done when unlocking bootloader ?
Click to expand...
Click to collapse
No my friend, I don't have important data on the internal 32 gigs, so no problem for me that the factory reset delete all the datas.
I mean that I don't want to "lost" this internal memory which is usefull for install applications (because this internal memory isn't well recognized no ? or I don't have well understood...).
Popol640001 said:
No my friend, I don't have important data on the internal 32 gigs, so no problem for me that the factory reset delete all the datas.
I mean that I don't want to "lost" this internal memory which is usefull for install applications (because this internal memory isn't well recognized no ? or I don't have well understood...).
Click to expand...
Click to collapse
Ah, okay, I see what you see.
No risk to loose the internal memory: it is still there once the tablet is rooted.
Issue I was mentioning about "no way to see internal memory in CWM" meant that when you boot CWM (the recovery), it does not see the internal storage. That the reason why, you have to sideload the SuperSU to flash it.
Then, once rebooted (and rooted), internal storage is visible as usual from Android
I would like to fix it into CWM so that we would them have a 100% usable and flashable CWM. Very useful then for flashing other zip that you should copy to internal storage and/or perform nandroid backups to internal storage.
So, you can safely root your device with the method (just be prepared to have the device reset to factory default due to unlocking bootloader)
Cheers
Just found it on Google
Sent from my SM-N900T using XDA Free mobile app
Problem with adb_usb.ini
groumfi said:
Hi there,
We finally achieve root on this SlateBook x2. Full story here: http://forum.xda-developers.com/showthread.php?t=2402681&page=59
Sum-up
Buy the HP proprietary cable
Unlock bootloader
Boot CWM recovery I built for the SlateBook x2
Push SuperSU thru sideload
Detailed steps
You need to buy the Micro-USB dedicated cable, HP spare part number 728141-001
You can find it at http://www.eetgroup.com/. Frenchies can order it here: http://fr.eetgroup.com/i/728141-001-HP-MICRO-USB-TO-USB-CABLE. The guys are located at St Ouen (93) and it is possible to pick-up the cable at their office to save shipping costs. Even w/o shipping costs I had to pay 57,30 € which is quite expensive for such a cable.
Anyway, once you have the $$$ cable, proceed as follow to root the device:
You'll need adb installed and working onto to your computer. This could be done by installing the full Android SDK or a light version from here: http://forum.xda-developers.com/showthread.php?p=42407269
Normally, the package should install the naked USB drivers. If this not the case have a look at http://forum.xda-developers.com/showthread.php?t=2386956 and download and install the naked USB drivers
Into your home directory (ie: C:\Users\<username> for Windows or /home/<username> for Linux) you should find a .android directory. Check the adb_usb.ini file within this directory and ensure that content is 0x03F0
Then, enable USB debugging into the Developper options of Android parameters
Once done, connect to the PC with the dedicated cable, wait for a moment for adb drivers to install
Once installed, check that adb can detect the tablet with by entering: adb devices
If it is detected, reboot in bootloader mode: adb reboot bootloader
Once in bootloader, unplug / plug again the tablet and wait for adb drivers to install. Then unlock the bootloader: fastboot -i 0x03F0 oem unlock. WARNING: this will reset your tablet to factory default and loose all your data
Once bootloader is unlocked, reboot your tablet and perform the initial android setup
Tun USB debugging on again and connect the tablet
Reboot to bootloader: adb reboot bootloader
Boot downloaded recovery: fastboot -i 0x03F0 boot recovery_maya-0.1.img
Wait a couple of seconds for CWM to start on the tablet
On the tablet, select Install zip and then Install zip from sideload
Once sideload is ready, install UPDATE-SuperSU-v1.94.zip: adb sideload UPDATE-SuperSU-v1.94.zip
Wait for install to finish, reboot and enjoy
Notice
For those running Ubuntu flavor Linux, no need to download any drivers (assuming you've installed android-tools-adb and android-tools-fastboot packages). Just add 0x03F0 to your ~/.android/adb_usb.ini file so that adb will detect the tablet.
I have updated my device to 4.3 to ensure this is working properly. For those who still have 4.2.2, this method will also work as developper Chainfire has implemented 4.3 and olders in SuperSU zip
I did the build of CWM by my own and it is not 100% fully functional (still have issue mounting internal storage). But it is usable enough to install SuperSU zip thru sideload
DO NOT FLASH this version of CWM. I've not tested flashing and it might brick your device
Click to expand...
Click to collapse
Hello,
Thanks for your work. I'm running on windows 8.1 and can't find adb_usb.ini ... I've only two files adbkey (1 File type and 1 Publisher type).
I've trying to install the minimal_adb_fastboot program on two differents pc but I obtain the same results...
I've a macbook pro but I don't know if it's possible to use it to unlock and root my HP slatebook x2 and how to proceed.
Thanks for your help
Hey everyone. Long time lurker, first time poster, and always grateful.
Okay, so I took a good look at some related threads. They all seem to have been resolved by using tools specific to their particular device. I have not had luck following their lines. So, here's what's up with me:
Asus Transformer Tf700 US edition
Had Cyanogen Mod. Wanted to sell my tablet, so I decided to wipe and go back to factory. Unfortunately, while fooling around in TWRP, I managed to putz it up and wipe the system and data. So no more OS, and apparently no more super user (whoops), although I may be wrong about that.
I can reboot the device into TWRP, but I can't mount the microsd card. When I plug my microsd card into my device, I just get an error that says cannot mount external sd card. So, since that isn't working, I've tried to sideload via adb.
I have the SDK but can't run ADB sideload because ADB on my computer does not recognize my device. I have tried to install updated drivers, though the drivers that I did find, when I point windows to the folder with them, it doesn't see a driver. SO maybe I'm doing that wrong.
I'm completely at my wit's end here. Can someone give me a little help?
Thanks everyone for your help in advance.
Specifics please????
CM, TWRP, Windows, drivers: What version?
You may want to try this, it installs the drivers for you: http://forum.xda-developers.com/showthread.php?t=2588979
berndblb said:
Specifics please????
CM, TWRP, Windows, drivers: What version?
You may want to try this, it installs the drivers for you: http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Hey there, thanks so much for replying!
I'm using TWRP v2.6.0.0.
Windows 7 x64 SP1
The CM version that I had, I actually don't recall now. I had flashed it back to stock though, before this, by using TWRP recovery. I noticed after that that I had not flashed my saved files properly. That's when I pooched it, hah.
I removed the existing USB drivers via device manager, restarted, used the installer that you linked to, restarted, and plugged in my device. It said installing drivers, and then failed to install drivers. ADB does not recognize a connected device. Merp.
I still haven't had any luck. Does anyone have any ideas?
You have to get the Windows drivers working to get ADB and fastboot access to your tablet and that can be tricky. Any chance you can get your hands on a Linux machine?
If the ADB tool I linked to didn't work (and I don't understand why - I used it on Win7 32 bit without a hitch) try to install the Google Universal Naked Drivers (google the term and should find them easily).
Actually - do you have the Asus device drivers installed? What happens if you connect the USB cable? Does Windows recognize the device at all? If not try to download Asus Sync, install it and try again. Once Windows recognizes the tablet as a MTP device, run the adb tool again and then try "adb devices" when you are booted into Android and "fastboot devices" when the tablet is in fastboot mode.
http://forum.xda-developers.com/showthread.php?t=2646279
berndblb said:
You have to get the Windows drivers working to get ADB and fastboot access to your tablet and that can be tricky. Any chance you can get your hands on a Linux machine?
If the ADB tool I linked to didn't work (and I don't understand why - I used it on Win7 32 bit without a hitch) try to install the Google Universal Naked Drivers (google the term and should find them easily).
Actually - do you have the Asus device drivers installed? What happens if you connect the USB cable? Does Windows recognize the device at all? If not try to download Asus Sync, install it and try again. Once Windows recognizes the tablet as a MTP device, run the adb tool again and then try "adb devices" when you are booted into Android and "fastboot devices" when the tablet is in fastboot mode.
Click to expand...
Click to collapse
Hey, thanks for the reply. When I plug in the device, it tries to install drivers and almost immediately fails. It then shows in the device manager as shown in the attached file. When I right click, select update driver, and point it to the folder with the google naked drivers (or the asus drivers), it says that "Windows cannot find drivers for this device." This seems strange to me. It has no idea what the transformer is when it is plugged in. Is there a different manual method of installing drivers, or cuing windows to recognize that these are the correct drivers?
I had Asus Sync installed, and that didn't seem to do anything for me. Windows would not do anything differently than it had already done. Grrr. This hurts.
sbdags said:
http://forum.xda-developers.com/show....php?t=2646279
Click to expand...
Click to collapse
This method looks promising, but it requires one to go into Android and turn on USB debugging mode. Problem is: I have no OS to log in to in order to do so
Whoops, forgot screen shot
Jeez - this is frustrating. I'm running out of ideas how to get Windows to work...
You are running Windows with administrator rights - yes?
Consider installing Linux as a dual boot on your Windows machine. I did that just to get rid of these ADB/fastboot driver problems....
berndblb said:
Jeez - this is frustrating. I'm running out of ideas how to get Windows to work...
You are running Windows with administrator rights - yes?
Consider installing Linux as a dual boot on your Windows machine. I did that just to get rid of these ADB/fastboot driver problems....
Click to expand...
Click to collapse
I'm running shy on space on my OS SSD, but would it potentially work running off of a boot disk? I have Fedora lying around here somewhere. Would the process be especially different? I have so very little experience working in Linux.
Also, I wonder if this is important. When I tell TWRP to reboot the machine, it informs me that super user isn't installed, and offers to root my device for me, but when I select that option, the screen just goes blank and it appears to hang, and I have to reboot it with the volume and power keys.
hardshank said:
I'm running shy on space on my OS SSD, but would it potentially work running off of a boot disk? I have Fedora lying around here somewhere. Would the process be especially different? I have so very little experience working in Linux.
Also, I wonder if this is important. When I tell TWRP to reboot the machine, it informs me that super user isn't installed, and offers to root my device for me, but when I select that option, the screen just goes blank and it appears to hang, and I have to reboot it with the volume and power keys.
Click to expand...
Click to collapse
I have no idea if you can run adb or fastboot if you boot Linux off a boot disc - but what the heck? Why not try it at this point?
I do not understand your driver problems at all. I helped someone today with a lot of the same problems: The tablet only booted into recovery, TWRP would not mount the microSD, didn't see any files on the internal... The ADB tool I linked to earlier allowed him to adb reboot to the bootloader - the rest was a breeze... Something in your Windows setup is just effed up... Sorry - wish I had that magic wand...
berndblb said:
I have no idea if you can run adb or fastboot if you boot Linux off a boot disc - but what the heck? Why not try it at this point?
Click to expand...
Click to collapse
Sure, if you have compatible adb and fastboot binaries it should work. Linux doesn't care where it was booted from.
_that said:
Sure, if you have compatible adb and fastboot binaries it should work. Linux doesn't care where it was booted from.
Click to expand...
Click to collapse
I had to install the adb and fastboot binaries on my distro. You can't do that on Linux running off a disc - can you? You would have to find a distro that comes with them?
berndblb said:
I had to install the adb and fastboot binaries on my distro. You can't do that on Linux running off a disc - can you? You would have to find a distro that comes with them?
Click to expand...
Click to collapse
On some live distros you can install additional software to a ramdisk. For adb and fastboot, any live distro with 32 bit libraries should have the required libs so that you can just copy/download the binaries and run them.
So here is an interesting development: I am now able to see my micro SD card when it is plugged into my device. Why? I haven't the foggiest. However, I still can't see any of its contents. Curious....
hardshank said:
So here is an interesting development: I am now able to see my micro SD card when it is plugged into my device. Why? I haven't the foggiest. However, I still can't see any of its contents. Curious....
Click to expand...
Click to collapse
Okay. I can't believe this worked, but I'm back in action. Here's how it went down:
- I tried doing a Linux USB drive, but was having difficulties getting it to boot, and my knowledge of Linux is so limited, I basically gave up hope.
- Today, I picked up my tablet (which has remained plugged in for power all of this time), and rebooted it. At the opening screen, which allows me to choose to go into TWRP, boot into (I think) Linux, or wipe data, I had never selected Wipe Data. Why? Because accidentally wiping the wrong partition is what got me in this mess to begin with.
- SO then I think, what the hell. It seems to have actually done something (though I don't know what), so I grab my micro SD with stock Android loaded on it, and pop it in. Voilà! It is recognized (as above).
- For some reason, no contents of card are visible
- Restarted device: card contents visible!
- Selected "Install" in TWRP menu, and selected my stock ROM
So. This has been a weird month. Thank you to EVERYONE who helped out on this. I'll be sure to hit the Thanks buttons!
hardshank said:
Okay. I can't believe this worked, but I'm back in action. Here's how it went down:
- I tried doing a Linux USB drive, but was having difficulties getting it to boot, and my knowledge of Linux is so limited, I basically gave up hope.
- Today, I picked up my tablet (which has remained plugged in for power all of this time), and rebooted it. At the opening screen, which allows me to choose to go into TWRP, boot into (I think) Linux, or wipe data, I had never selected Wipe Data. Why? Because accidentally wiping the wrong partition is what got me in this mess to begin with.
- SO then I think, what the hell. It seems to have actually done something (though I don't know what), so I grab my micro SD with stock Android loaded on it, and pop it in. Voilà! It is recognized (as above).
- For some reason, no contents of card are visible
- Restarted device: card contents visible!
- Selected "Install" in TWRP menu, and selected my stock ROM
So. This has been a weird month. Thank you to EVERYONE who helped out on this. I'll be sure to hit the Thanks buttons!
Click to expand...
Click to collapse
Glad you got it working!
Out of curiosity: Was your tablet booted or completely off until you picked it up today? Did you reboot into the bootloader or did it do that by itself?
Sent from my ASUS Transformer Pad TF700T using Tapatalk
EDIT: solution here
Hi all,
My HTC OX+ died, and I bought a Motorola Moto G (Falcon) to see me through to the end of my contract. Aside from the price, the big draw was CM support.
I've unlocked by bootloader and installed TWRP without trouble (when I was screwing with my HOX+, I read that CWM doesn't support sideloading. Since - correct me if I'm wrong - the 'cleanest' way to install a ROM is to format the SDcard completely, then install the ROM, sideloading support is vital).
I've tested and confirmed root access (initially, I thought not having the SU binary installed was an issue, although I did have TWRP installed fine). However, I'm stuck with adb - in recovery, adb does not recognise what I do. I've tried installing, uninstalling and reinstalling drivers from various sources (first the ones offered my Motorola during the unlocking process, then the ones from Windows Update, and last but not least ones from here: http://d-h.st/5j0 - following advice of a thread I found on here). I've tried doing this both automatically and manually using Device Manager.
Usually, precisely because of these problems, I hate using Windoze for this kind of thing. However, I don't have a Linux distro open to me atm - other than in VirtualBox, in which case adb still doesn't pick up the phone (presumably because its reliant on the host Windows drivers). I'm tearing my hair out trying to get it fixed.
Not that they can be conclusively relied upon, but as confirmation it is a drivers issue (despite Device Manager finding no problem), when the phone is connected in recovery (TWRP), Windows plays an odd sound - three tones instead of the usual two.
Any help would be appreciated. My Windows is Windows 7 Ultimate x64. Also, I've no problems at all when the stock OS is booted - or at least 'adb devices' detects the device and displays it correctly.
Thanks!
CWM does work with sideloading (that's the way i installed CM the first time ) [make sure to use the one linked in CM11 thread!]
if i understand correctly:
fastboot works fine (since you could unlock the BL)
adb works when the device is booted
adb fails when in recovery
make sure you are using the latest adb :
Code:
[email protected] ~ $ adb version
Android Debug Bridge version 1.0.31
if your version is lower than 1.0.31, then update it (in that case your adb is outdated regarding the 4.4 bootloader) ==> update your Android SDK manager or your adb binary
matmutant said:
CWM does work with sideloading (that's the way i installed CM the first time ) [make sure to use the one linked in CM11 thread!]
if i understand correctly:
fastboot works fine (since you could unlock the BL)
adb works when the device is booted
adb fails when in recovery
make sure you are using the latest adb :
Code:
[email protected] ~ $ adb version
Android Debug Bridge version 1.0.31
if your version is lower than 1.0.31, then update it (in that case your adb is outdated regarding the 4.4 bootloader) ==> update your Android SDK manager or your adb binary
Click to expand...
Click to collapse
Do you think CWM is preferred to TWRP? If sideloading is supported, it's not like you spend much time in recovery anyway, so if you think it'll help, flashing CWM is definitely something I can do...
AFAIK...
- have only used fastboot briefly to install recovery, but this went without a hitch.
- ADB does indeed work when the stock OS is booted
- As above. Fails in recovery, I suspect because of a driver issue (weird Windows sound when connected, no Autoplay popup etc). You can kind of understand this...writing a driver for the device in recovery is hardly a key issue for the devs (though I confess, why it can interact with the same hardware with one set of programs loaded (i.e. stock OS) and not another (i.e. TWRP) I've no idea)
Just issued the command, and (as expected since I downloaded the bundle only yesterday from Google) I am running 1.0.31.
ArminasAnarchy said:
Do you think CWM is preferred to TWRP? If sideloading is supported, it's not like you spend much time in recovery anyway, so if you think it'll help, flashing CWM is definitely something I can do...
AFAIK...
- have only used fastboot briefly to install recovery, but this went without a hitch.
- ADB does indeed work when the stock OS is booted
- As above. Fails in recovery, I suspect because of a driver issue (weird Windows sound when connected, no Autoplay popup etc). You can kind of understand this...writing a driver for the device in recovery is hardly a key issue for the devs (though I confess, why it can interact with the same hardware with one set of programs loaded (i.e. stock OS) and not another (i.e. TWRP) I've no idea)
Just issued the command, and (as expected since I downloaded the bundle only yesterday from Google) I am running 1.0.31.
Click to expand...
Click to collapse
In fact i never tried TWRP : i have always been happy with CWM so i didn't feel the need to change (so you can give a try but i don't think it would change anything)
Try to run ADB as administrator it may help (i think you can open cmd as admin with windows but don't remember how :-\)
I don't know how USB drivers work : there's a long time i didn't use Windows
matmutant said:
In fact i never tried TWRP : i have always been happy with CWM so i didn't feel the need to change (so you can give a try but i don't think it would change anything)
Try to run ADB as administrator it may help (i think you can open cmd as admin with windows but don't remember how :-\)
I don't know how USB drivers work : there's a long time i didn't use Windows
Click to expand...
Click to collapse
I think I can figure this out - I'll double check it was running as admin, and try flashing CWM.
As with flashing ROMs, do I need to wipe anything first? Or can I just use the same command I used for flashing TWRP in the firs place?
If it's still not working, (re) installing Linux seems an idea to try (I assume you're not on OSX?). What distro do you use and/or do you know others have had no problems with? (Usually if I was installing Linux, I'd take Ubuntu's minimal iso and stick as little as possible on top of it - since the drivers are likely to be something cut out of that though, installing a 'normal'/'full' .iso seems sensible)
Cheers for your help, man
ArminasAnarchy said:
I think I can figure this out - I'll double check it was running as admin, and try flashing CWM.
As with flashing ROMs, do I need to wipe anything first? Or can I just use the same command I used for flashing TWRP in the firs place?
If it's still not working, (re) installing Linux seems an idea to try (I assume you're not on OSX?). What distro do you use and/or do you know others have had no problems with? (Usually if I was installing Linux, I'd take Ubuntu's minimal iso and stick as little as possible on top of it - since the drivers are likely to be something cut out of that though, installing a 'normal'/'full' .iso seems sensible)
Cheers for your help, man
Click to expand...
Click to collapse
The latest TWRP has in its wipe menu a setting to wipe to install a new rom I use this and with the Gapps & rom Zips on the phone choose install from sd card.
You only need fastboot to flash recovery or stock roms.
Adb is not needed at all but can still be used if you prefer!
ArminasAnarchy said:
I think I can figure this out - I'll double check it was running as admin, and try flashing CWM.
As with flashing ROMs, do I need to wipe anything first? Or can I just use the same command I used for flashing TWRP in the firs place?
If it's still not working, (re) installing Linux seems an idea to try (I assume you're not on OSX?). What distro do you use and/or do you know others have had no problems with? (Usually if I was installing Linux, I'd take Ubuntu's minimal iso and stick as little as possible on top of it - since the drivers are likely to be something cut out of that though, installing a 'normal'/'full' .iso seems sensible)
Cheers for your help, man
Click to expand...
Click to collapse
To install CWM :same as for TWRP, no wipe required
________
Linux :
I'm using Mint (Cinnamon and Xfce) since a while [ubuntu based distro] and Manjaro since a few days [Arch based]
If you want yo install linux without touching your HDD you can do the following :
Burn an iso (Xubuntu could be nice)
Take a blank 16GB USB key and unplug your HDD to void issues
Boot on live CD
Install linux to that USB device
And now each time you want linux : just force boot your computer to USB (no grub / no modifications on HDD)
To use ADB you'll need the Android SDK Manager (to stay up-to-date) and set up your udev rules following this
matmutant said:
To install CWM :same as for TWRP, no wipe required
________
Linux :
I'm using Mint (Cinnamon and Xfce) since a while [ubuntu based distro] and Manjaro since a few days [Arch based]
If you want yo install linux without touching your HDD you can do the following :
Burn an iso (Xubuntu could be nice)
Take a blank 16GB USB key and unplug your HDD to void issues
Boot on live CD
Install linux to that USB device
And now each time you want linux : just force boot your computer to USB (no grub / no modifications on HDD)
To use ADB you'll need the Android SDK Manager (to stay up-to-date) and set up your udev rules following this
Click to expand...
Click to collapse
Is the android-tools-abd and android-tools-fastboot package in the Ubuntu repos not maintained to be the latest? I've no idea about Arch package names, but again, it'd surprise me if they didn't maintain their repo with the latest package (especially since they pride themselves on being on the bleeding edge).
ArminasAnarchy said:
Is the android-tools-abd and android-tools-fastboot package in the Ubuntu repos not maintained to be the latest? I've no idea about Arch package names, but again, it'd surprise me if they didn't maintain their repo with the latest package (especially since they pride themselves on being on the bleeding edge).
Click to expand...
Click to collapse
It is up-to-date on arch/Manjaro (I don't remember the package name either)
On Ubuntu it wasn't when I needed (February), so I installed SDK package :-/
matmutant said:
It is up-to-date on arch/Manjaro (I don't remember the package name either)
On Ubuntu it wasn't when I needed (February), so I installed SDK package :-/
Click to expand...
Click to collapse
Right, well...we'll see how it goes. It might be the repo package does the job.
I've installed CWM and can conclusively confirm I prefer TWRP (the interface is hardly touch-friendly and even though I'm using the touch build, it's easier to use the volume rocker in case of accidental presses) but little else. Windows seems completely ****ed up - when CWM is booted, it plays the disconnect sound, when the cable is unplugged and plugged back in it goes back to playing the 'unknown' tone. Currently torrenting Xubuntu - going to see if a live install has any more luck.
Full solution
matmutant said:
It is up-to-date on arch/Manjaro (I don't remember the package name either)
On Ubuntu it wasn't when I needed (February), so I installed SDK package :-/
Click to expand...
Click to collapse
Right, I'm running TWRP with CM11. There are a couple of issues bothering me, but that's another thread...
Solution:
- From stock, booted into recovery, then replaced TWRP with CWM. Rebooted into CWM.
- Tested sideload from CWM. Still non-functional. Made sure cmd.exe was running with administator privileges, still no difference. Time for _buntu!
- Installed Xubuntu. Connected to wifi, downloaded
Code:
android-tools-adb
and
Code:
android-tools-fastboot
. Plugged in phone. Checked
Code:
adb version
(it is the latest, 14.04 was released in April after you checked in Feb, and the new release must have updated the package...seems strange no one backported it though).
- Sideloaded and did a dirty flash of CM11 (didn't want to wipe without first confirming I could flash and everything was functional). Issues (as expected) such as slow loading but able to boot up.
- Decide it's time to push my luck and flash TWRP - this goes without a hitch.
- Test sideload. Still working, so perform full wipe and factory reset. Then sideload CM11 + GApps.
- Reboot into CM11. Still some issues so flashed the CM11 kernel using fastboot (not sure if TWRP does this automatically, but since the boot up improved a bit, I'd guess not).
- Now have a fully functional phone, albeit some of the changes from CM10.x to CM11 have disorientated me a bit...
Thanks for your help man. As with a lot of things this turned out to be a dopey Windoze issue than a problem with the phone or adb etc!
TWRP
TWRP has sideload ability.
Boot into recovery and got to the "Advanced" button then the "ADB Sideload" button is at the bottom. I am on TWRP v2.7.0.0 and I used it the other day so I know for sure it works.
ArminasAnarchy said:
Right, I'm running TWRP with CM11. There are a couple of issues bothering me, but that's another thread...
Solution:
- From stock, booted into recovery, then replaced TWRP with CWM. Rebooted into CWM.
- Tested sideload from CWM. Still non-functional. Made sure cmd.exe was running with administator privileges, still no difference. Time for _buntu!
- Installed Xubuntu. Connected to wifi, downloaded
Code:
android-tools-adb
and
Code:
android-tools-fastboot
. Plugged in phone. Checked
Code:
adb version
(it is the latest, 14.04 was released in April after you checked in Feb, and the new release must have updated the package...seems strange no one backported it though).
- Sideloaded and did a dirty flash of CM11 (didn't want to wipe without first confirming I could flash and everything was functional). Issues (as expected) such as slow loading but able to boot up.
- Decide it's time to push my luck and flash TWRP - this goes without a hitch.
- Test sideload. Still working, so perform full wipe and factory reset. Then sideload CM11 + GApps.
- Reboot into CM11. Still some issues so flashed the CM11 kernel using fastboot (not sure if TWRP does this automatically, but since the boot up improved a bit, I'd guess not).
- Now have a fully functional phone, albeit some of the changes from CM10.x to CM11 have disorientated me a bit...
Thanks for your help man. As with a lot of things this turned out to be a dopey Windoze issue than a problem with the phone or adb etc!
Click to expand...
Click to collapse
I'm happy it worked fine finally !
And thank you for providing the way you did it, that could help some other people having similar issue.
highspeedfelon said:
TWRP has sideload ability.
Boot into recovery and got to the "Advanced" button then the "ADB Sideload" button is at the bottom. I am on TWRP v2.7.0.0 and I used it the other day so I know for sure it works.
Click to expand...
Click to collapse
I think you mis-read somewhere. I know TWRP has sideload, I used it on my HOX+. It was CWM I was unsure of...
matmutant said:
I'm happy it worked fine finally !
And thank you for providing the way you did it, that could help some other people having similar issue.
Click to expand...
Click to collapse
That was the idea, yeah .
I love the way the moral of the story is "Don't expect Windows to do the job properly. EVER. (Or at least not without several hours of screwing with it first)."
ArminasAnarchy said:
I love the way the moral of the story is "Don't expect Windows to do the job properly. EVER. (Or at least not without several hours of screwing with it first)."
Click to expand...
Click to collapse
And during that time i succeeded to break both my Mint and Manjaro installs (user-related fails) and bring them back to life XD
I have LineageOS 16.0
I used MutiROM before, uninstalled it, but MultiROM Recovery is still installed.
Today I downloaded update for LineageOS but I got "Updater process ended with ERROR: 7"
Now I can't boot to OS because it boots straight to recovery.
The solution is to flash normal recovery and flash LineageOS zip.
But I can't transfer Recovery.img to my OnePlus One.
While I'm in Recovery, ADB is not working and there's no option to enable it.
And while I'm in Fastboot, PC can't see any fastboot devices.
It's not the PC's fault because it can recognize my Xiaomi Redmi Note 7 in both ADB and Fastboot mode.
So basically I need a way to transfer Recovery.img from PC to OnePlus One.
I can access only TWRP and Fastboot.
I can't do anything over USB cable.
OnePlus One doesn't have microSD card slot so I can't do it that way.
And I tried plugging in USB OTG drive and it phone can't recognize it. It won't even send the power to OTG drive.
eldin90 said:
And I tried plugging in USB OTG drive and it phone can't recognize it. It won't even send the power to OTG drive.
Click to expand...
Click to collapse
Use a low current flash drive, e.g. Transcend JetFlash 380 32 GB USB 2.0 OTG [200mA].
ze7zez said:
Use a low current flash drive, e.g. Transcend JetFlash 380 32 GB USB 2.0 OTG [200mA].
Click to expand...
Click to collapse
I don't think that'll work.
Phone doesn't give power to USB devices at all.
I tried plugging in multiple devices that used to work before (2 different USB thumb drives, both directly via micro USB port and via micro USB to USB 2.0 adapter, tried plugging in another phone, mouse, gamepad, micro USB to Ethernet adapter)
All those stuff used to work before while phone was on. But now they don't get power at all.
I don't know could it be because of Recovery?
I haven't tried plugging in OTG devices while in Recovery before.
eldin90 said:
While I'm in Recovery, ADB is not working and there's no option to enable it.
And while I'm in Fastboot, PC can't see any fastboot devices.
Click to expand...
Click to collapse
After entering:
Code:
adb devices
what you see in recovery mode?
---edit---
Use the USB 2.0 port on your PC.
ze7zez said:
After entering:
Code:
adb devices
what you see in recovery mode?
---edit---
Use the USB 2.0 port on your PC.
Click to expand...
Click to collapse
I don't see anything when I enter adb devices.
When I use any other phone I can see it after entering adb devices. But when I use OnePlus One I can't see anything.
And I only have USB 2.0 ports on my PC.
eldin90 said:
I have LineageOS 16.0
I used MutiROM before, uninstalled it, but MultiROM Recovery is still installed.
Today I downloaded update for LineageOS but I got "Updater process ended with ERROR: 7"
Click to expand...
Click to collapse
Are you sure you have an unmounted system partition before installing the ROM?
This message is the result of a mismatch between the build.prop entry from ROM and the TWRP installer script.
ze7zez said:
Are you sure you have an unmounted system partition before installing the ROM?
This message is the result of a mismatch between the build.prop entry from ROM and the TWRP installer script.
Click to expand...
Click to collapse
System partition is unmounted.
MultiROM TWRP gives me that error only when flashing some ROMs.
And it gives it to those ROMs always, no matter what I do.
Problem is that I only have LineageOS 16.0 zip on the phone and I don't have any other recoveries besides that MultiROM recovery.
Is there any way to boot the OS?
It worked fine before I tried to update it and it looks like all system files are still there.
I guess that failed update shouldn't had deleted any system files because it failed before it started doing anything.
I don't know what's making phone boot directly into recovery.
It won't even try to boot OS.
It goes straight into recovery every time.
eldin90 said:
System partition is unmounted.
MultiROM TWRP gives me that error only when flashing some ROMs.
And it gives it to those ROMs always, no matter what I do.
Problem is that I only have LineageOS 16.0 zip on the phone and I don't have any other recoveries besides that MultiROM recovery.
Is there any way to boot the OS?
It worked fine before I tried to update it and it looks like all system files are still there.
I guess that failed update shouldn't had deleted any system files because it failed before it started doing anything.
I don't know what's making phone boot directly into recovery.
It won't even try to boot OS.
It goes straight into recovery every time.
Click to expand...
Click to collapse
There should always be an original ROM for installation and several recovery versions in the phone's memory.
Now you have the use of restoring rom.
Clear the cache. First, try to recover only the Boot, and if that doesn't help, the entire backup.
You also have a powerful tool in TWRP in the form of a terminal and busybox commands, so act.
ze7zez said:
There should always be an original ROM for installation and several recovery versions in the phone's memory.
Now you have the use of restoring rom.
Clear the cache. First, try to recover only the Boot, and if that doesn't help, the entire backup.
You also have a powerful tool in TWRP in the form of a terminal and busybox commands, so act.
Click to expand...
Click to collapse
I tried wiping Cache and Dalvik / ART Cache
Still boots directly to recovery.
I don't have any backups or recovery installations on phone's memory.
I only have backup from 2 months ago that contains only boot and cache.
I restored it but it still boots directly to recovery.
What terminal commands should I use to fix this?
eldin90 said:
I tried wiping Cache and Dalvik / ART Cache
Still boots directly to recovery.
I don't have any backups or recovery installations on phone's memory.
I only have backup from 2 months ago that contains only boot and cache.
I restored it but it still boots directly to recovery.
What terminal commands should I use to fix this?
Click to expand...
Click to collapse
Since you don't maintain software hygiene, it's probably no better with hardware.
Clean the USB socket without damaging the connection. Clean the Vol- key in several ways.
Check if Odin can see the connection.
I have nothing more to add.
ze7zez said:
Since you don't maintain software hygiene, it's probably no better with hardware.
Clean the USB socket without damaging the connection. Clean the Vol- key in several ways.
Check if Odin can see the connection.
I have nothing more to add.
Click to expand...
Click to collapse
I work at coal coke industry and this happened about a month ago.
While I was charging the phone, coke dust inside the phone started burning and melted charger and USB socket together.
Guy from repair shop opened the phone and replaced USB socket with another one.
Is it possible that he didn't connected it correctly to the motherboard?
Or USB socket that he put wasn't exactly the same as the one that was originally there?
After he fixed it, we only tested can it charge the phone.
I haven't tried connecting phone to PC since then.
Anyways, is it possible to do something with terminal?
There has to be a file or something that's telling the phone to boot straight into recovery, right?
Can I remove or modify that file if it exists so phone boots into OS instead of recovery?
Vol- button isn't the problem.
It worked fine until I tried to update the OS.
And I can boot to Fastboot by holding Power and Vol+ buttons.
eldin90 said:
I work at coal coke industry and this happened about a month ago.
While I was charging the phone, coke dust inside the phone started burning and melted charger and USB socket together.
Guy from repair shop opened the phone and replaced USB socket with another one.
Is it possible that he didn't connected it correctly to the motherboard?
Or USB socket that he put wasn't exactly the same as the one that was originally there?
After he fixed it, we only tested can it charge the phone.
I haven't tried connecting phone to PC since then.
Anyways, is it possible to do something with terminal?
There has to be a file or something that's telling the phone to boot straight into recovery, right?
Can I remove or modify that file if it exists so phone boots into OS instead of recovery?
Vol- button isn't the problem.
It worked fine until I tried to update the OS.
And I can boot to Fastboot by holding Power and Vol+ buttons.
Click to expand...
Click to collapse
Using md5sum check the phone ROM.zip of your Lineage you tried to install. Then check the ROM.zip checksum on the server and compare the checksums. You will learn about the quality of the file.
If someone undertook to replace the usb socket, it is obvious that you should check not only the charging lines, but also the data transmission line.
From that I would repair the OPO.
ze7zez said:
Using md5sum check the phone ROM.zip of your Lineage you tried to install. Then check the ROM.zip checksum on the server and compare the checksums. You will learn about the quality of the file.
If someone undertook to replace the usb socket, it is obvious that you should check not only the charging lines, but also the data transmission line.
From that I would repair the OPO.
Click to expand...
Click to collapse
I did sha256 checksum and it's exactly the same as on the server
https://mirrorbits.lineageos.org/fu...16.0-20191118-nightly-bacon-signed.zip?sha256
Mount System partition
Code:
mount /system
and show:
Code:
grep twrp /tmp/recovery.log
Code:
ls -l /data/media/
Code:
ls -l /data/media/0/
Code:
grep lineage /system/build.prop
Code:
cd /
find . -name recovery*
find . -name *.zip
find . -name *.img
It's not everything. When you're finished we'll go on.
ze7zez said:
Mount System partition
Code:
mount /system
Click to expand...
Click to collapse
I did that
ze7zez said:
and show:
Code:
grep twrp /tmp/recovery.log
Click to expand...
Click to collapse
imageupload
ze7zez said:
Code:
ls -l /data/media/0/
Click to expand...
Click to collapse
This one only shows files and folders from internal memory. Nothing important there
ze7zez said:
Code:
ls -l /data/media/
Code:
grep lineage /system/build.prop
Click to expand...
Click to collapse
ze7zez said:
Code:
cd /
find . -name recovery*
find . -name *.zip
find . -name *.img
It's not everything. When you're finished we'll go on.
Click to expand...
Click to collapse
1. Change /sdcard/recovery.log to a unique name.
2. Make Advanced -> Copy Log (Include Kernel Log)
3. Change /sdcard/recovery.log to a unique name.
4. Make a full backup ROM if you haven't already done so.
5. Wipe -> Advanced Wipe: Dalvik, System, Data, Cache
6. Install lineage without "Reboot after installation is complete".
7. Show messages from the installation terminal.
8. Make Advanced -> Copy Log (Include Kernel Log)
9. Change /sdcard/recovery.log to a unique name.
10. Reboot -> System
??
I did all steps.
After wiping everything and trying to install LineageOS zip I get this (same as before)
When I tried to reboot, TWRP warned me that there are no OS installed. Phone still boots straight to recovery.
eldin90 said:
I did all steps.
After wiping everything and trying to install LineageOS zip I get this (same as before)
When I tried to reboot, TWRP warned me that there are no OS installed. Phone still boots straight to recovery.
Click to expand...
Click to collapse
You have twrp installed for Oneplus 3 (E3004) and you want to upload a ROM for Oneplus One.
ze7zez said:
You have twrp installed for Oneplus 3 (E3004) and you want to upload a ROM for Oneplus One.
Click to expand...
Click to collapse
I have installed TWRP that I downloaded from here
https://forum.xda-developers.com/oneplus-one/development/mod-multirom-v26-t2835738/amp
It's says it's for OnePlus One.
And I used to flash Ubuntu Touch and some older Resurrection Remix and CyanogenMod ROMs with it.
eldin90 said:
I have installed TWRP that I downloaded from here
https://forum.xda-developers.com/oneplus-one/development/mod-multirom-v26-t2835738/amp
Click to expand...
Click to collapse
This is impossible because your TWRP is release 3.1.1-0, which was created after 2017-05-17, which is much later than TWRP from the page you provided.
Show:
Code:
grep fingerprint /sdcard/recovery.log
As a joke, I ran "rm -rf /" in Terminal Emulator with superuser rights, after a few seconds the app crashed and the phone froze and I had to press the power button for 15s to cut the power. The biggest suprise was that partitions like /system and even /sdcard were not completely erased, as I booted right back into Lineage OS, however the phone was really sluggish and I experienced a lot of ARNs and micro stutters. Everytime I would try to use my phone I'll only get a maximum 10 seconds of SoT followed by an instant shutdown.
Now trying to install a new rom works 1/2 times. When it fails I get an error such as "couldn't mount /firmware" in the TWRP log, and when it succeeds and boots into the first time setup, the same story as above happens again (ARNs and shutdowns).
Somehow I must've deleted more than just the user writeable partitions, as the file system is all over the place and it's not functioning correctly anymore. The phone isn't recognized by ADB even in Fastboot and Recovery mode, and I reinstalled the Universal ADB Drivers from ClockworkMod for Windows.
Idk if this phone will ever see the light of day again although I daily drove it 4 years and it served me like a champ.
Right now I'm questioning if there is any possible solution or if I have to resort to manually pumping electrons into the NAND Flash =)
To mention:
-My phone is the Xiaomi Redmi 4 Prime (codename markw);
-I had an unofficial build of Lineage OS 18.1;
-I can still boot into Fastboot mode and TWRP Recovery;
-I can still transfer files between my phone and my pc using a micro sd card;
-You can get as technical as you want.
Everyone's opinion will be well perceived and every little bit of help will be much appreciated!!
Side remark:
You've to use Xiaomi Android USB Driver.
jwoegerbauer said:
Side remark:
You've to use Xiaomi Android USB Driver.
Click to expand...
Click to collapse
I have also tried using the MiFlashTool which came bundled with Xiaomi Adb drivers, but no success.