]Hey everybody,
i wanted to switch from cm9 to cm10. after i managed to return to stock rom and recovery and successfully updated to stock ics, still with root available, i cannot connect my tpt to my pc, which is necessary to install adb drivers to further load the new cwm.
i've been trying and reading posts for several hours now, but there is just no way the tpt gets recognized in win7. i always get the message:
'unknown device'. device has been stopped. code 43.'
Click to expand...
Click to collapse
so far i've tried everything i could find in several posts out there, and yes, sync with pc is enabled as well as usb debugging.
i tried to install android_winsub.inf (both from lenovo adb driver package and the android sdk) and edited it as suggested in some other posts, but still no luck.
i also did a reset and tried it with two other pcs - still no luck.
any ideas?
danjac said:
]Hey everybody,
i wanted to switch from cm9 to cm10. after i managed to return to stock rom and recovery and successfully updated to stock ics, still with root available, i cannot connect my tpt to my pc, which is necessary to install adb drivers to further load the new cwm.
i've been trying and reading posts for several hours now, but there is just no way the tpt gets recognized in win7. i always get the message:
so far i've tried everything i could find in several posts out there, and yes, sync with pc is enabled as well as usb debugging.
i tried to install android_winsub.inf (both from lenovo adb driver package and the android sdk) and edited it as suggested in some other posts, but still no luck.
i also did a reset and tried it with two other pcs - still no luck.
any ideas?
Click to expand...
Click to collapse
Hi, are you sure that you heve correct USB IDs added to adb driver (android_winsub.inf)? I found out that it changes when I installed different CWM and CM version. I had similar problem recently.
HaliG1 said:
Hi, are you sure that you heve correct USB IDs added to adb driver (android_winsub.inf)? I found out that it changes when I installed different CWM and CM version. I had similar problem recently.
Click to expand...
Click to collapse
well, i read about it. it was said that one should just open the 'details tab' (device manager...) and read out the id when plugged in. unfortunately, i get nothing there. so the problem must be somewhere else.
but nevertheless, thank you for your hint/idea.
I have seen this issue before when i have not used the stock USB cable supplied by Lenovo.
dcshoecomp said:
I have seen this issue before when i have not used the stock USB cable supplied by Lenovo.
Click to expand...
Click to collapse
I tried several cables, ports and pcs... nothing worked. By now I believe it's my loose mini-usb-port, it's probably still ok for charging the tablet but not for data transfer - it is the only explanation i can think of so far. So sooner or later I might need the dock.
Nevertheless, I managed to install the new cwm and cm10 by using the terminal emulator. So there is no urgent need to get that working again.
Have you tried a wireless ADB app?
This worked for me when ADB via USB cable quit working after flashing a new ROM.
Sent from my LG-VM670 using Tapatalk 2
I went to flash cyanogenmod 10.1.
backed up rom via clockwork.
wiped data, flashed new rom.
flashed gapps.
I think i flashed the wrong gapps
upon boot I get "setup wizard has stopped" as well as one regarding gapps.
this prevents me from using the rom. I can access the calender and clock that is all. not the settings or reboot menu.
I can access the built in storage via windows, shows up as a nexus 7.
Ok, not a big deal, I will boot into recovery via the bootloader.
That no longer works. Sits at a google screen forever
Ok, I will use fastboot via the bootloader....
That no longer works. As soon as a usb cable touches the nexus either power or pc it freezes the bootloader requires a reboot.
windows rejects the usb and states is malfunctioned and unrecognised (though it works fine in the rom)
fastboot doesn't see the device.
I've tried:
three usb cables.
windows safe mode.
different ports
uninstall/install drivers.
nexus tool kit (doesnt recognise device)
wiggling the cable as suggested
anybody got an idea how I can either get the bootloader not to freeze when using a usb cable or how to boot into some kind of recovery (which was there!!!!!)
please? :fingers-crossed:
Something seems a little off here.
Was it a gapps package for some other device? Hard to see why flashing something to /system would produce the result you got, as the (gapps) edify script would at most specify a mount of "system", not a /dev/block/ device name.
Does adb work (with the ROM booted)? If so, can you get a root shell or install .apks?
The fact that the ROM boots suggests that the bootloader is working correctly enough to load and execute the LNX (boot) image. That means that in principle you could flash (using the "dd" command) a recovery image to the boot partition from a root-privileged command line (either an adb session or a terminal emulator). Performing a regular (power button) restart would boot you into a recovery session.
Obviously, this hinges on you getting a command line somehow with your reduced-functionality ROM limping along as it is. It's not obvious to me how you will make that happen though.
I am not at all confident that this will fix the bootloader <--> USB issue without somehow reflashing the bootloader without using fastboot!. The only way this has been observed for the N7 has been with the OTA process and a stock recovery - the OTA puts an image (**note - important!** this OTA bootloader image is slightly different from the bootloader image in the factory/fastboot ROMs) into the USP partition and some magic occurs on the next boot.
Well, anyway there's some ideas. Would you mind identifying the "wrong" gapps that you used? For the life of me I can't see how it caused the symptoms you are observing...
good luck
Hi. Many thanks.
Ok.....
Gapps. I downloaded the appropriate package via the link on the Rom page. However, I flashed a jellybean package I'd downloaded for my one x. I may be naive in thinking that Gapps is Gapps no?
I deduced it was that having googled the setup wizard problem and seeing that others had had it.
Bootloader.
Again. Ive googled around and can see many have the freezing bootloader with usb issue. Some say its the cable. Some say its the pc. But it does it with the charger as well. Again this is an issue for some. not sure what to do! Works fine until the cable goes in.
Recovery.
Again I know its an issue booting recovery from bootloader. I've read you need the usb in to a pc to make it happen. Obviously that's a no go for me
Adb.
Never really used it. Used fastboot many times. I assumed you need to be able to access the developer options and activate debugging etc within the Rom to allow it to work? I can not do that. Its around 10% funtional. I can place a reminder on the calender but that's about it! No way to system settings.
Sorry if thats teaching you to suck eggs. You obviously know your stuff, just wanted to make it clear.
Ta.
Sent from my HTC One X+ using xda app-developers app
olly2097 said:
Recovery.
Again I know its an issue booting recovery from bootloader. I've read you need the usb in to a pc to make it happen. Obviously that's a no go for me
Click to expand...
Click to collapse
A normally functioning tablet does NOT require you to be plugged in to a PC in order to boot the recovery from the bootloader menu. Maybe you are saying something else here, but I trust you've tried starting the recovery without anything plugged in at all.
Unless you can get the recovery working, the only hope you have is somehow levering up what you have available to gain a privileged thread of execution. Obviously that's going to be pretty challenging.
good luck - you're going to need it.
PS: could you provide a URL to the *wrong* One X gapps download? I think the gapps bundle ships with system libraries - I want to peek at those libs to see if there are any hardcoded block device paths that might explain the queerness you observed. (I can't imagine why this would be the case, but...)
bftb0 said:
A normally functioning tablet does NOT require you to be plugged in to a PC in order to boot the recovery from the bootloader menu. Maybe you are saying something else here, but I trust you've tried starting the recovery without anything plugged in at all.
Unless you can get the recovery working, the only hope you have is somehow levering up what you have available to gain a privileged thread of execution. Obviously that's going to be pretty challenging.
good luck - you're going to need it.
PS: could you provide a URL to the *wrong* One X gapps download? I think the gapps bundle ships with system libraries - I want to peek at those libs to see if there are any hardcoded block device paths that might explain the queerness you observed. (I can't imagine why this would be the case, but...)
Click to expand...
Click to collapse
yeah, tried both ways.
The gapps I downloaded was a while ago. I've deleted it. was for 4.1.1
anyway. I....
Booted to bootloader, selected recovery, pressed power and rammed in the usb cable at the same time.
recovery
now running rom fine after flashing TW recovery via toolkit and mounting to pc.
I cant explain it. it took forever. but thank you
I have checked at least hundred threads now, but my problem seems unique! (First time this happened to me )
When I connect my N7 (WiFi, 32 GB) to my laptop (Win 8.1), it says "USB device not recognized - The last USB device you connected to this computer malfunctioned, and Windows does not recognize it." In Device Manager, it is like the image attached, no other recognition for the device. Upon selecting Properties, It says "Code 43" in status, also says "A request for the device descriptor failed". That happened with 2 computers; I used 2 cables (both worked previously). So it means N7's USB port is somehow malfunctioning. But it gets charged as well as ever!!
This started after I tried an OTA update of 4.4 earlier (the download had not completed, but a prior small update (1-3 MB) was installed).
Now, I have Android SDK (latest version) and installed those google USB driver and platform-tools. I have NRT 1.7.9 (which worked for me previously). But I cant get my N7 to answer to ADB requests. [highlight]Upon connecting USB, it says "Charging (USB)" but no option regarding PTP or MTP appears.[/highlight] I have developer tools installed. I followed the instructions given in NRT about ADB installation to the letter but still no progress. I have tried a factory reset too.
BTW, I dont have a custom recovery flashed. It vanished along with the precious root privilage.
Now the N7 is in Android 4.3 (JWR66Y), bootloader is unlocked, SuperSU is Installed (but do not work due to having no root access and I cant even Uninstall it for the same reasons!!!). Now the OTA update also do not work mysteriously (it downloaded the 4.4.2 update and went on to install it, but as the bar started filling, it only said "error" and stopped!!! no explanations whatsoever!!!!). I will be very happy any of the followings:
[highlight]1. root without computer (wireless ADB is also welcome),
2. working OTA, or anyhow the 4.4.2 update
3. working ADB connection with my laptop.[/highlight]
Any help will be very helpful... Thank you in advance...
If you can not communicate via USB hardware, then using fastboot is not an option (obviously). And so therefore the lock state of your bootloader is quite irrelevant, too.
Even if you were to get adb over tcp (WiFi) working, that doesn't get you much, as an adb login shell on a stock ROM is just an unprivileged user; it's not much different from using a terminal emulator app (from a privilege escalation point of view).
The only other thing left is an exploit (privilege escalation) method that runs under the stock ROM. Something similar to that Motochopper exploit from some time ago. I suppose that particular hole was plugged; whether or not a new exploit exists, I can't tell you.
You could always just send the tablet back for repair. Seems like not having a working USB port is pretty crippling to someone who wants to root, flash ROMs, copy backups off the tablet, etc.
Thank you for the replying...
Actually I lack warranty as I bought this from eBay weeks before it was officially available in India. Therefore I kept that repair thing as a last resort. I am now trying it through Linux. And being a noob there, its going too slow. However I have got the ADB working and detecting the device, so its not a port issue (I dont know why the hell windows was so adamant on that point!)... But I am yet to figure out how to flash the image... thank you for the tip over wi-fi, i was actually hoping to wait for it...
Aaron061992 said:
Thank you for the replying...
Actually I lack warranty as I bought this from eBay weeks before it was officially available in India. Therefore I kept that repair thing as a last resort. I am now trying it through Linux. And being a noob there, its going too slow. However I have got the ADB working and detecting the device, so its not a port issue (I dont know why the hell windows was so adamant on that point!)... But I am yet to figure out how to flash the image... thank you for the tip over wi-fi, i was actually hoping to wait for it...
Click to expand...
Click to collapse
Well that is very different than having a broken USB port.
You probably noticed in your search that this forum is littered with thousands of reports from users complaining about their Windows drivers. It gets pretty old, frankly. (No drivers are needed at all for Linux or Mac OS/X).
Here is a suggestion that I made in another thread just a few days ago about using fastboot under Linux - in your case, you will be on your way after installing a recovery, e.g.
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-grouper.img
I even attached the most recent version of the (Android SDK Linux) fastboot to that post.
Note that you don't even need a dual-boot PC or PC with a semi-permanent Linux install; you can do the whole thing with one of those "Live CD" boots and a USB stick.
good luck
Hello,
I have leeco le pro 3 x722 and problem happened that I have tried to flash to another ROM from AOSP to DOT, so I have made backup and tried to flash after wipe I realised I have wiped everything and now don't have any ROM inside phone, I have connected phone to pc but it does not show in device manager and nothing happens it only charges. I have TWRP recovery and I can only explore in it. Did I bricked my phone already? How can I recover it? did TWRP wipes backups too ? Also in TWRP it shows Internal Storage (0 MB seems wiped) and U(USB Storage)(0MB). Tried to connect with differend cables - same situation still no reaction only charging. On Backup Tab it shows that I have System Image 4gb, System 1,4gb, Boot 64mb
Updated//
Fixed partition now it shows internal size.
1.Changed data partition from ext4 -> fat > and change it again to same it succesfully recovered but after reboot it gone again.
2.Tried on diferent pc to connect phone - still no MTP.
Updated// 2018-08-24
Cutted file /system/priv-app/Setup-Wizard/setup-wizard.apk to another folder successfully booted ROM, now trying to download another ROM.
After download and reboot in TWRP internal storage shows 0 and cant access to ROM.zip, after change trick data wipes and after boot it show again clear phone. PC still don't see and cant turn on developers options.
kiamikadze said:
Hello,
I have leeco le pro 3 x722 and problem happened that I have tried to flash to another ROM from AOSP to DOT, so I have made backup and tried to flash after wipe I realised I have wiped everything and now don't have any ROM inside phone, I have connected phone to pc but it does not show in device manager and nothing happens it only charges. I have TWRP recovery and I can only explore in it. Did I bricked my phone already? How can I recover it? did TWRP wipes backups too ? Also in TWRP it shows Internal Storage (0 MB seems wiped) and U(USB Storage)(0MB). Tried to connect with differend cables - same situation still no reaction only charging. On Backup Tab it shows that I have System Image 4gb, System 1,4gb, Boot 64mb
Updated//
Fixed partition now it shows internal size.
1.Changed data partition from ext4 -> fat > and change it again to same it succesfully recovered but after reboot it gone again.
2.Tried on diferent pc to connect phone - still no MTP.
Click to expand...
Click to collapse
Part 1
The fact that you can use Twrp is great news! and its okay the phone is fine as long as TWRP is installed and the bootloader is unlocked. its no big deal not having an OS. As long as you have Twrp you are fine.
You are not bricked.
But, you need to be extremely careful with anything that you do regarding the Elite X722, if you brick it we do not have a qfil file to fix it and you will have no solution.
I do not have a X722, I have the X727 and I generally do not like giving advice on the X722 because of its volatility and there is no option to save bricks.
Here is the main link for the X722, only use roms that are compatible with the X722.
https://forum.xda-developers.com/le...elite-model-x722-guides-development--and-mods
You need to choose a reliable rom, gapps and Magisk.
I would highly recommend AICP
AICP is an excellent rom that works extremely well on the X722,
Everything that you need is with the original post page.
Get AICP here: https://forum.xda-developers.com/le...mods/rom-aicp-13-1-pro3-aka-zl0-x722-t3730711
You already have Twrp installed, follow the steps below for the installation of Rom, Gapps, Magisk
First, you can of course use ADB but you would be better off buying an OTG adapter and a USB 3.0 USB Flash drive. I recommend at least 32GB. Absolutely, the OTG adapter is the best method, because you will have all of your files available for quick installation and you can make numerous nandroid backups of your favorite rom installations. So If you get bored with one Rom, you can quickly restore another Rom in 5 to 10 minutes.
If you do not have an OTG adapter and drive
First place your rom, Gapps, and Magisk within storage ( aka: sd card) using your desktop and follow steps below.
Boot into TWRP recovery
1. Go to "Wipe" and then to "Advanced Wipe".
2. Mark "Dalvik / ART Cache", "System", "Data" and "Cache".
3. "Swipe to Wipe" and proceed back the main menu, by clicking home button.
4. Go to "Install".
5. Select the ROM zip file and then press "Add more Zips" and select the Gapps zip file, and then the Magisk file.
6. "Swipe to confirm Flash" and wait for some time.
7. After the flashing is finished, just reboot to recovery, clicking checkboxes for TWRP, Reboot to Recovery first, then reboot to system.
Finished!
Edit: Since the PC does not see the phone, additional steps to come in few minutes.
---------- Post added August 24th, 2018 at 12:04 AM ---------- Previous post was August 23rd, 2018 at 11:57 PM ----------
[/COLOR]
kiamikadze said:
Hello,
I have leeco le pro 3 x722 and problem happened that I have tried to flash to another ROM from AOSP to DOT, so I have made backup and tried to flash after wipe I realised I have wiped everything and now don't have any ROM inside phone, I have connected phone to pc but it does not show in device manager and nothing happens it only charges. I have TWRP recovery and I can only explore in it. Did I bricked my phone already? How can I recover it? did TWRP wipes backups too ? Also in TWRP it shows Internal Storage (0 MB seems wiped) and U(USB Storage)(0MB). Tried to connect with differend cables - same situation still no reaction only charging. On Backup Tab it shows that I have System Image 4gb, System 1,4gb, Boot 64mb
Updated//
Fixed partition now it shows internal size.
1.Changed data partition from ext4 -> fat > and change it again to same it succesfully recovered but after reboot it gone again.
2.Tried on diferent pc to connect phone - still no MTP.
Click to expand...
Click to collapse
Part2 : Stay at ext4, use nothing else, there is virtually no benefit in using F2FS, the speed increase is in the milliseconds.
If these steps below do not work, try another computer or another cable. Or better yet just be patient and get the OTG adapter and USB drive before doing anything else.
[B ]If you can use ADB [/B]
You can save your self alot of time by looking up how to give ADB system wide privileges: this will allow you to flash files without tying the directory path.
However, there is a faster way: @mauronofrio created a tool called: "TOOL ALL IN ONE"" and its great!
https://forum.xda-developers.com/and...ctory-t3358711
Its an excellent tool for keeping your drivers and adb up to date. Plus it will give ADB system wide privileges.
Mauronofrio's tool can also unencrypt your stoarge
After install the All in One Tool
Make sure to check for the AIT program for updates, to the tool itself and to ADB.
Next, click button to allow ADB privileges system wide.
Get more information here:*https://toolaio.tk**
XDA page for Le pro 3 : https://forum.xda-developers.com/le-...1#post71627491
* The all is one tool is excellent and you can use it to install everything you want.
* You can use it to unlock the bootloader.
* Remove Encryption
* Install TWRP,
* Install your Rom, Gapps and Magisk etc.
* The tool will also update your existing installation of ADB, Android Drivers, and provide system wide ADB privileges.
Again , if you do not use an OTG drive. Just use ADB for flashing your files, the steps are same as with any other phone.
---------- Post added at 12:13 AM ---------- Previous post was at 12:04 AM ----------
Post 3,
I just reread your post and only now seeing the partition size issue. The size issue will be resolved after formatting your storage, this is a strange issue, but is fixable. At this point you need to be extremely careful, if you lose you your boot, and recovery you are in trouble. FYI the boot and recovery are on different partitions., formatting storage does not affect them.
Specifically what did you flash?
No doubt, you flashed something not for the X722?
Question
Were you previously using a custom Rom?
Do not try flashing alternate firmwares,
There are several firmwares out there that will brick your phone, Go to you forum that I linked above for the safe versions. @D1stRU3T0R has a X722, perhaps he can chime in here and help provide some further advice on helping you out.
I am thinking that if you can use the All in One tool to flash the X722 stock Rom, you can have a fresh start. @D1stRU3T0R, if you are ssing this mention, care to comment? Thanks
Post 3,
I just reread your post and only now seeing the partition size issue. The size issue will be resolved after formatting your storage, this is a strange issue, but is fixable. At this point you need to be extremely careful, if you lose you your boot, and recovery you are in trouble. FYI the boot and recovery are on different partitions., formatting storage does not affect them.
Specifically what did you flash?
No doubt, you flashed something not for the X722?
Question
Were you previously using a custom Rom?
Do not try flashing alternate firmwares,
There are several firmwares out there that will brick your phone, Go to you forum that I linked above for the safe versions. @D1stRU3T0R has a X722, perhaps he can chime in here and help provide some further advice on helping you out.
I am thinking that if you can use the All in One tool to flash the X722 stock Rom, you can have a fresh start. @D1stRU3T0R, if you are ssing this mention, care to comment? Thanks
Click to expand...
Click to collapse
I think my last hope is otg, or usb drive to android phone because after many tries still can't connect phone to pc no new devices in device manager, phone only charging, tried now with 3 different pc and 3 different cables. Tried to install this ROM: https://forum.xda-developers.com/le-pro3/development/rom-dotos-2-3-1-t3809068 last ROM was paranoid and working well, but I have bored and wanted 8.1 Android, so..
kiamikadze said:
Hello,
I have leeco le pro 3 x722 and problem happened that I have tried to flash to another ROM from AOSP to DOT, so I have made backup and tried to flash after wipe I realised I have wiped everything and now don't have any ROM inside phone, I have connected phone to pc but it does not show in device manager and nothing happens it only charges. I have TWRP recovery and I can only explore in it. Did I bricked my phone already? How can I recover it? did TWRP wipes backups too ? Also in TWRP it shows Internal Storage (0 MB seems wiped) and U(USB Storage)(0MB). Tried to connect with differend cables - same situation still no reaction only charging. On Backup Tab it shows that I have System Image 4gb, System 1,4gb, Boot 64mb
Updated//
Fixed partition now it shows internal size.
1.Changed data partition from ext4 -> fat > and change it again to same it succesfully recovered but after reboot it gone again.
2.Tried on diferent pc to connect phone - still no MTP.
Updated// 2018-08-24
Cutted file /system/priv-app/Setup-Wizard/setup-wizard.apk to another folder successfully booted ROM, now trying to download another ROM.
After download and reboot in TWRP internal storage shows 0 and cant access to ROM.zip, after change trick data wipes and after boot it show again clear phone. PC still don't see and cant turn on developers options.
Click to expand...
Click to collapse
@tsongming thanks.
So, first of all, you try to say that you made a backup but you wiped everything so now our phone is empty, and you can't connect it to PC nor use sdcard(logic) and OTG doesn't see your USB?
So, listen here, i had this problem too xd.
First, what format is your usb stick? If I remember well, NTFS is working (assuming you have pretty nes TWRP). Try to format the stick to NTFS, or try with another one. Your only option now is to find a compatible USB stick and to make it work with OTG, than you csn flash any rom you want.
When you get the USB working, install newest twrp, 0.3.2.1-3 or smth like this, than Genesys 26S, as a base stock rom, than AICP and blackscreen OC kernel, or whatever rom you want.
My wife has a 722 too. Mtp is never working on my PC. So i habe to usw ADB for file transfer. Just type "adb devices" if there is shown your device its working (must be in twrp at least and connectet via cable) then just type "ADB push " path to file" /sdcard" and it will copy the file to the phone.
I would first update twrp then modem.ZIP for x722 and then Rom gapps and magisk if u want.
oiseau1201 said:
My wife has a 722 too. Mtp is never working on my PC. So i habe to usw ADB for file transfer. Just type "adb devices" if there is shown your device its working (must be in twrp at least and connectet via cable) then just type "ADB push " path to file" /sdcard" and it will copy the file to the phone.
I would first update twrp then modem.ZIP for x722 and then Rom gapps and magisk if u want.
Click to expand...
Click to collapse
As @D1stRU3T0R mentioned you will not need the PC once you have the PTG adapter and the USB 3.0 drive.
Make sure its USB 3.0 otherwise it may take a while before your phone will recognise the flash drive. I bought my OTG adapter and a 32GB usb 3.0 flash drive for $14 at Walmart for both!
tsongming said:
As @D1stRU3T0R mentioned you will not need the PC once you have the PTG adapter and the USB 3.0 drive.
Make sure its USB 3.0 otherwise it may take a while before your phone will recognise the flash drive. I bought my OTG adapter and a 32GB usb 3.0 flash drive for $14 at Walmart for both!
Click to expand...
Click to collapse
I have 2 usb 2.0 and they both work (with some cheap old otg cable), so OP can try whatever stick he wants.
And i guess you mean OTG not PTG
D1stRU3T0R said:
I have 2 usb 2.0 and they both work (with some cheap old otg cable), so OP can try whatever stick he wants.
And i guess you mean OTG not PTG
Click to expand...
Click to collapse
Ha, Ha. Yes OTG, its my stupid autocorrect, on this awesome chroma keyboard. Keyboard is great, with its amoled theme, the autocorrect, not so good.
Yes, I used to use large 2.0 drives too. But, once they become about 80 percent full, I would need to wait 20-30 seconds, sometimes longer for them to show up in recovery. To make matters worse, sometimes I would need to reboot to recovery for them to appear at all. On the the other hand the much, much better USB 3.0 reliably always show ups and instantly.
To go on, the transfer rate difference plays a significant factor when creating or restoring a large full nandroid backup. For example, The transfer rate of USB 2.0 is a mere 60 Mbps while transfer rate of USB 3.0 is 640Mbps. Yes, this speed difference is in fact a huge time factor when restoring a 11GB full recovery!
Respectfully use whatever you want, but I am not going to ever recommend anything less than USB 3.0 Its funny, for a person whose always wanting the maximum overclocking speed, and absolute full use of the battery. I am frankly very surprised you would use anything less than USB 3.0..... Lol. its okay, just winding you up, I guess that I have much less patience than you. Ha ha
FYI, USB 3.0 drives are nearly the same price as the USB 2.0 drives.
I paid $2.00 for my OTG adapter and $11 dollars for by USB 3.0 drive. Better yet, I went back a week later and Walmart had a package with two USB 3.0 drives on sale for only $20!
Sent from my LEX727 using XDA Labs
first of all what version is your twrp,because newer roms need newer twrp
i did the same mistake on my x722 and managed to install new rom using adb sideload from twrp,pc and a data cable,just look into it how to install rom from pc using adb sideload or if the otg arrived is easyer to install from a flash drive with otg
So, first of all, you try to say that you made a backup but you wiped everything so now our phone is empty, and you can't connect it to PC nor use sdcard(logic) and OTG doesn't see your USB?
So, listen here, i had this problem too xd.
First, what format is your usb stick? If I remember well, NTFS is working (assuming you have pretty nes TWRP). Try to format the stick to NTFS, or try with another one. Your only option now is to find a compatible USB stick and to make it work with OTG, than you csn flash any rom you want.
When you get the USB working, install newest twrp, 0.3.2.1-3 or smth like this, than Genesys 26S, as a base stock rom, than AICP and blackscreen OC kernel, or whatever rom you want.
Click to expand...
Click to collapse
After many tries it didn't help I have tried with NTFS, FAT32 still same didn't recognized otg storage, uploaded ROM to flashdrive when in TWRP checked storage of usb drive, cant even choose mount usb drive, or just take data from usb in Leeco. I don't know what to do I think I should recycle it ..
I have installed many ROMS and unbricked many phones but this one is "Die Hard" don't know what to do more when cant connect via usb/otg. Many thanks for help, I think for now is impossible to reflash any rom, still not wiped system data so I can boot my phone without setup wizard and he runs.
Just to be certain, Bootloader was unlocked, OEM unlocking was checked. ( I rooted the PH1 before and it was simple enough last year but idk what's happing now)
I was on Feb update, wanted to go and apply the patched boot so I can at least apply root. Followed this guide post #7.
https://forum.xda-developers.com/es...ndroid-10-unsupported-unknown-format-t4072429
But when i try to fastboot flash boot <filename>. I get this error "FAILED (remote: Error flashing partition.)"
So I searched some more and discovered this.
https://forum.xda-developers.com/essential-phone/help/flash-twrp-error-flashing-partition-t3834804
And I get the same exact issue in this thread with " FAILED (remote: Flash Write Failure)".
Basically anything to do with wiping fails, and it seems everything wipes first then writes. SO I think i wiped everything I was going to subsequently write but the phone never allowed writing.
Im at a lost in a current bootloader boot loop. Fastboot still recognises the device but further research has me seeing eeprom corrupt chip preventing writing..
Anyone got this fixed? Sorry for the original terrible post... I was a bit in disarray...
Rewrote the OP with more info after i composed myself.
I had a similar issue some time back and writes to either slot would result in failure. Some smaller images would write sometimes. I thought the hardware failed...
But then I read somewhere that bad USB cables can cause issues so although I had used the same 6 ft cable to write many many times, I switched to a short length high quality cable and boom everything was back to normal. No issues since then for 6 months now.
Try it if you have not done so already.
hammer7t said:
I had a similar issue some time back and writes to either slot would result in failure. Some smaller images would write sometimes. I thought the hardware failed...
But then I read somewhere that bad USB cables can cause issues so although I had used the same 6 ft cable to write many many times, I switched to a short length high quality cable and boom everything was back to normal. No issues since then for 6 months now.
Try it if you have not done so already.
Click to expand...
Click to collapse
im cofused as hell. 100% dumbfounded. I had an old rusty usb cable i threw over my wall. I literally went for it and plug it in an old laptop and it worked. Its currently accepting all flashes no errors at all....
wtf. And I tried 3 different brand USB cables as well. Type A to C. and the original C to C. I even used the same cable and same laptop I used to root the device last year but it have errors. I am legit confused. How can the cable work one time and then legit refuse the other. It was eeven a cable recommended on here(or reddit) a long time ago to use WITH flashing and roms etc.
Edit: Phone fully recovered.