I flashed my stock rom android 10 back to PIE using fastboot, all went ok and phone rebooted back to the 'Lets Go' OS screen. However the touch screen has stopped working. Anyways out of this problem?
On Win 10 with the correct drivers (as flash and connected sucessfully) its saying USB not recongised. I can get to fastboot and recovery but feels like I'm stuck with no way out....
So turns out this touch screen problem is a known issue. So I fastboot flashed Pie from April 2019 and problem solved.
https://www.reddit.com/r/essential/comments/b87425/april_download_links/
The laptop USB issue was solved by flashing the firmware on the laptop to latest version. Side issue, red herring fault in all this.
Thanks for sharing the information.
Sent from my PH-1 using Tapatalk
Related
I upgraded to official 2.3.4 GB (i think it was a Chinese ROM because i downloaded it from the huawei website) and i did not like it because my phone did not get Data or Wifi Or Bluetooth so i i downgraded my phone to 2.2.2 back to the original firmware it had but when i was installing it my phone said Successfully Installed and then it turned of but then nothing happened black screen, next day i change it it turn on the touch keys turn on and LED turn red but screen is black
anyone know how to fix this
I am also having this type of problem. I rooted installed CWM and flashed a custom rom now i have the blue screen issue. Can't find the files I need to repair this anywhere. All the treads have broken links.
r0y123 i am following this guide to correct my problem http://forum.xda-developers.com/showthread.php?t=1589205 I will let you know if it works out.
EDIT: worked perfect I can now boot and reroot.
thanks for the help
my phone wont turn on ,the LED and touch keys turn on for a while only when i connect it to the pc or wall charger. ohh also my computer recognized my u8800-51 as a HID-Compatible device------------- anyone know why?
i cant access pink/purple screen or blue screen not even recovery.
PLEASE I NEED HELP!!!!:crying:
I installed ubuntu
can I use ubuntu to see my phone stuff? sorry i couldnt explain my self
It would be worth a try. I have and increadble and the first time i rooted and and tried to run a rom on it. I got the same kinda thing yor getting. It was a screen driver problem. That might be something to think about. My previous post worked like a charm. Try it your phone is already dead. Just pretend it is at the right screen it wont work if it doesnt find your device.
Nope It did not recognize my phone only when I'm on windows my PC recognize it as a HID-Compatible device but when I go to my Device Manager and uninstall the driver it recognize it as a ""Quantomm something something MSM"" but then windows installs it again and I'm trying to install as something else, ANYONE GOT ANY TIPS?
Sent from my MB300 using xda app-developers app
Mine was being reconized as a Qualcomm ........ but it still worked. See if this is helpfull. http://www.addictivetips.com/window...tomatic-driver-installation-in-windows-vista/
r0y123 Did you ever get your phone working? I have the same issue.
I got a serious problem with the N4 of a friend.
First thing to know: his display was broken and he got it repaired. Afterwards, his phone was running fine. Then, he got the Android 4.3 OTA. He accepted the update, but since then in keeps bootlooping (I won't go past the Nexus-X). As far as I know, everything was stock!
Here are the things I tried:
- first I checked the recovery. Indeed it was the stock one, so nothing to do here.
- I wanted to wipe or flash the stock rom using fastboot but i wasn't able to get a connection. First I thought of driver issues, but my N4 works fine (adb & fastboot) on the same computer.
- Establishing a connection failed on two other computers too (my N4 worked)
- Even the device manager in Windows 7 dosen't even recognize anything when plugging in the usb cable (normally you see the ADB whatever device listed in the device manager)
- Right now I tried to get a connection using Ubuntu. Again, no usb device was recognized when plugging in the cable.
So right now, I'm a bit lost. It seems, that the usb port is broken since I can not establish a connection. And without that, I won't be able to wipe or flash anything using fastboot.
Does anyone have an idea what could have gone wrong? I'm still able to boot into the bootloader and see the information:
Bootloader version: MakoZ20i
Radio: .84
HW Version 11
16GB version
According to these information, it seems that the 4.3 Update finished at least the bootloader and radio. But it won't boot into the rom. Could the download mode be of any help?
I appreciate any help.
Thanks.
Since you are in the bootloader scroll up to recovery and select it.
Now you will see a android opened up with "No command." written below the android.
Press volume up and power until it unlocks the recovery and try to wipe the data and cache partition followed by dalvik cache.
Sent from my Nexus 4 using Tapatalk 4
Thanks for your idea, but it turned out to be hardware problem!
I took the device to the lab and had a look at the usb connector. The contact in the middle was teared of the carrier and was stuck to the back and thus no data connection could be established! I was able to to bend it back (more ore less) to its initial position and now its working. Though I'm wondering how long it will last until its pushed back again.
Fact is, that i was able to connect via fastboot. I tried to flash 4.3 again but it still didn't boot. Its back to 4.2.2 and its working now.
Again - thanks for your idea.
Thread can be closed!
I think I may have bricked my phone. I had it rooted and had official beta update installed on my phone. I tried to flash the Pixel Experience rom from the rom's here on the forum. Decided that I didn't like it as much as the stock rom. Flashed the stock rom and magisk back onto the phone. rebooted the phone and the phone got stuck on the intial screen, so I restarted the phone. Now the phone won't boot at all. When I plug the phone into my computer the computer acts like it connects and it is showing in the device manager, but the MSMdownload tool says Waiting for device even if I run the tool as an admin. Any help would be appreciated. Thank you.
Try using another cable or port. This happened to me the first time I had a major scare! Fingers crossed for ya
Fixed
I let it charge over night and was able to get it to fastboot. Got the recovery tool to work. It's all good now.
Hi,
I'm not sure I'm posting in the right section but, I had a really bad experience upgrading to android 10. Really sluggish and slow... so I tried to downgrade to android 9 by using Lenovo's Rescue and Smart Assistant.
What I did, is to find the stock ROM for my model, and replace the files downloaded by the Rescue Assistant (which downloaded the latest firmware). The process went through, but now the device wont power on.
When I plug in the USB, windows makes a sound, the charging light comes on, but The rescue Assistant nor SP flash tool is able to flash the latest firmware.
Is it bricked for good?
Model : TB-XF606F
Hardware number : 60
Maybe your computer doesn't recognize your tablet. Did you ever try using sp flash tool with your tablet before? You can try reinstall or install a driver for your table if you haven't done it yet.
Well the tablet is recognized as the "mtk vcom..." in device manager. I guess it is the driver that the lenovo rescue app installed.
I have never used sp flash tool with my tablet, just the lenovo rescue.
I tried on 2 different pc and it is the same thing. I think the problem is that I can't turn off the tablet properly, even though, all I can see is a black screen.
I will try to drain the battery by keeping the power button pressed with some scotch tape. I don't know what I can do else.
Edit: I tried a few other times with flash tool using different setting for the connection (with battery and full speed) and nothnig happened. But now windows says it does not recognize my tablet.
did the same thing exactly. . bricked lenovo m10 fhd plus x600v after i flashed a downgrade version. dont try to downgrade this thing. i had already flashed it with 3 or 4 versions the same way , but when i chose to flash the oldest version available with the model , this tab got completly unresponsive , no feedback when try to boot into recovery, fastboot, or system . neither does it gets recognised in windows or anything - device manager dowsnt recognise this usb device ( in device manager properties comments it reads- USB\DEVICE_DESCRIPTOR_FAILURE). if you find a way to reflash the device please let us know. good luck .
Bricked mine after being completely running smoothly on Lineage, then was messing around trying to get gapps installed and jacked up the partitions. TWRP said no OS. Kept messing around and mistakenly locked the bootloader again with apparently an unverified boot partition. . I couldn't get SP Flash tool to work ever either. Pretty sure it's a door stop now.
may throw my nexus in the bin...
was already having trouble with trying to connect to windows using usb but kept reconnecting
connected to mint successfully and flashed with twrp
however any twrp flo were giving mounting errors and rebooting, i did try few other versions but was having same issue
so i tried 2.8, now my nexus boots to recovery mode
twrp logo sits still for 5 seconds and then screen flashes black and then shows the logo again, looping
(it surely is still having mounting problems)
adb devices show nothing neither does fastboot
anyway never experienced a device with various problems
like sensors stopping out of nowhere and also taking ages to fully charge
Did it run fine on the original firmware?
V0latyle said:
Did it run fine on the original firmware?
Click to expand...
Click to collapse
stock factory reset worked normally
ignoring what i stated at the end it was running fine
android 6.0.1 kernel 3. something