My Slide just got a Touch Screen Fail message at boot. I am trying to root it so I can try to load a new ROM, to see it it might help.
I can boot phone normally, but I have no touch screen, so I cannot change to USB debug, nor use the phone for anything else.
I need to be able to root it from the Bootloader. Anybody has any suggestion how to remove the S-Off and be able to reflash phone ?
Is there a custom Esprimg file that can help ?
valv507 said:
My Slide just got a Touch Screen Fail message at boot. I am trying to root it so I can try to load a new ROM, to see it it might help.
I can boot phone normally, but I have no touch screen, so I cannot change to USB debug, nor use the phone for anything else.
I need to be able to root it from the Bootloader. Anybody has any suggestion how to remove the S-Off and be able to reflash phone ?
Is there a custom Esprimg file that can help ?
Click to expand...
Click to collapse
Well you CAN actually use the trackpad to navigate without the touchscreen. Bit difficult, but it can be done. What's the message you get exactly? Even a picture would help
Sent from my T-Mobile myTouch 3G Slide
Here's screen picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anybody can share some info ? Thanks
valv507 said:
Anybody can share some info ? Thanks
Click to expand...
Click to collapse
How could you get that if you weren't rooted?
You should take it to T-Mobile and get it replaced.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Afaik, you most likely need the touch screen in order to root. Then again, I am a noob at this stuff. If the touch screen showed as a failure it may be a hardware problem. Other than that you can navigate just fine with the trackpad and select with it or with the keyboard to tick "USB Debugging".
Related
Whenever I try to boot up my Desire Z, it would show me the HTC logo, but shut off promptly. I'd be able to enter the bootloader, but whenever I try entering recovery, I get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is my phone bricked?
I'm not sure what was done previously, as I bought this phone second hand, so I'm wondering if there's anything I can do to rectify the problem.
Sounds like a soft brick, at the worst. You can fix it. Look up loading a rom from bootloader dezire z. Maybe you can put the new update on the sd card. You will lose root though, which you probably have if the got you stuck on that screen.
Sent from my HTC Vision using XDA Premium App
Try looking up about the triangle, also. There might be some buttons you can press etc.
Sent from my HTC Vision using XDA Premium App
At the triangle screen you show, hold down volume for a second or 2 then press and hold power. See if that doesn't take you to the text-based recovery screen (stock is blue text?).
PS - sounds like no rom and/or radio is flashed, that or someone tried to reroot and stockify it but bricked it as you describe. I'm inclined to believe it's been wiped clean. What's the bootloader show for your hboot, radio versions etc?
Ah, I was able to get it into the 3e recovery with the blue text, but unfortunately I can't do anything there.
I think I have another problem now, though. The battery won't charge. If I plug it in, it'll flash an orange and green LED, and from what I've been able to gather online, that means there's something wrong with the battery connection or overheating? It's not the latter, so I'm going to assume there's something wrong with the pins. The warranty sticker has been broken as well, so I think I think I'm SOL.
Thanks for the help anyway, guys!
im currently running cm-7.2.0-RC0-marvel-KANG and im on US Cellular. Everything works except:
wifi and internet
Need some help please
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
help
vansrootedandroid said:
im currently running cm-7.2.0-RC0-marvel-KANG and im on US Cellular. Everything works except:
wifi and internet
Need some help please
Click to expand...
Click to collapse
You [and all cdma variants (like me even)] will have to wait for kernel development as alquez states in his OP of that thread.
or
Restore your nandroid backup of stock (easiest fix).
Regards,
Rob
insink71 said:
You [and all cdma variants (like me even)] will have to wait for kernel development as alquez states in his OP of that thread.
or
Restore your nandroid backup of stock (easiest fix).
Regards,
Rob
Click to expand...
Click to collapse
Hope it comes soon...I forgot to make a backup before i went to cm7....however I do have a second Wildfire S thats rooted but for some reason i cant get into recovery to back up that ROM....it gets stuck on the white HTC screen....any ideas?
ideas
Can you boot to hboot [on second phone]? If not you are either semi-bricked or bricked. Still assuming you cannot get into hboot, go download the htc sync drivers, set up your environment [Google has a guide that walks you through it], then with the phone connected to your computer [and on] type "adb devices" If you get a return that looks like a short serial, it can be fixed... If no devices found... well, it will take someone smarter than me If you can boot to hboot, it can be fixed no problemo... Hit me back with results [via pm] I can't follow every thread I respond to.
Regards,
Rob
PS it sounds like the 2nd phone has had either a bad recovery or wrong boot.img flashed to it w/o knowing more
I recently got a Epic 4G Touch from a friend who was upgrading. After messing around with it, I decided to try get CyanogenMod running on it. To make a long story short, I can no longer get the phone to boot, but I do have access to the AGAT custom recovery. I know I could use OdinExecution, but the phone is no longer recognized by Windows when plugging in USB - probably after flashing the kernel.
My question is what should I do from here? The only other way to get data onto the phone would be microSD, unless I can get USB working (I doubt). I was pretty foolish to go into this without more reading, and for that I apologize.
Ringle said:
I recently got a Epic 4G Touch from a friend who was upgrading. After messing around with it, I decided to try get CyanogenMod running on it. To make a long story short, I can no longer get the phone to boot, but I do have access to the AGAT custom recovery. I know I could use OdinExecution, but the phone is no longer recognized by Windows when plugging in USB - probably after flashing the kernel.
My question is what should I do from here? The only other way to get data onto the phone would be microSD, unless I can get USB working (I doubt). I was pretty foolish to go into this without more reading, and for that I apologize.
Click to expand...
Click to collapse
If you can get into recovery, I would try going here and flashing one of the zips found there.
http://forum.xda-developers.com/showthread.php?p=31961585
If by chance you can get into download mode and if the links are not working you can always use this
http://www.sammobile.com/firmwares/3/?download=12947
BIGSAMDA1ST said:
If you can get into recovery, I would try going here and flashing one of the zips found there.
http://forum.xda-developers.com/showthread.php?p=31961585
If by chance you can get into download mode and if the links are not working you can always use this
http://www.sammobile.com/firmwares/3/?download=12947
Click to expand...
Click to collapse
Thanks for the reply,
I managed to get a custom ROM installed, so at least I'm able to use the phone. Now I need to figure out how to get USB working again. I took a snapshot of the device screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there perhaps a compatible kernel I can try?
Hello experts,
I hard bricked my phone, but with the tool I managed to repair it. But after unbricking it while starting phone, it got stuck in boot logo and screen appear to be broken but its not.
This is how phone look like and everytime it happene same.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https ://drive.google.com/open?id=0B_S-tkD3eHy5Y3h3NnB3Y013Uy1qbTZycnpTWHN3OXlEc05F
What to do in this case? I don't have any idea now.
Please provide any solution.
unnat1993 said:
Hello experts,
I hard bricked my phone, but with the tool I managed to repair it. But after unbricking it while starting phone, it got stuck in boot logo and screen appear to be broken but its not.
This is how phone look like and everytime it happene same.
https ://drive.google.com/open?id=0B_S-tkD3eHy5Y3h3NnB3Y013Uy1qbTZycnpTWHN3OXlEc05F
What to do in this case? I don't have any idea now.
Please provide any solution.
Click to expand...
Click to collapse
It appears to get to the part where it starts to load the OS. In this case try to get into recovery. If you can get into recovery, great! Then just adb sideload the latest ROM from OnePlus.
ZVNexus said:
It appears to get to the part where it starts to load the OS. In this case try to get into recovery. If you can get into recovery, great! Then just adb sideload the latest ROM from OnePlus.
Click to expand...
Click to collapse
Did it, but after sideloading latest ROM from oneplus, it runs perfectly for sometime and again doing same thing.
Un brick by method 2
unnat1993 said:
Did it, but after sideloading latest ROM from oneplus, it runs perfectly for sometime and again doing same thing.
Click to expand...
Click to collapse
This actually sounds like a hardware issue to me, but I have no idea what I am talking about so idk.
drmuruga said:
Un brick by method 2
Click to expand...
Click to collapse
Did it, problem persist. :crying:
I'm not see the video but why you flash twrp and flash any other rom and try ?
Finally, OnePlus has told me that motherboard is not working. So have to change phone.
Phone always greets me with this pixelloided screen.
Its becoming an issue slowly.
Whenever I press the power button i get this screen. It persists for a while and goes off by itself.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
meher777 said:
Phone always greets me with this pixelloided screen.
Its becoming an issue slowly.
Whenever I press the power button i get this screen. It persists for a while and goes off by itself.
Click to expand...
Click to collapse
These are the screen snaps
hemanth.k said:
These are the screen snaps
Click to expand...
Click to collapse
do you have a custom rom?
Mr bubbles said:
do you have a custom rom?
Click to expand...
Click to collapse
No
hemanth.k said:
No
Click to expand...
Click to collapse
odd then that usual happens on custom roms you might need to re flash stock rom then.
Mr bubbles said:
odd then that usual happens on custom roms you might need to re flash stock rom then.
Click to expand...
Click to collapse
How to do that without unlocking BL?
hemanth.k said:
How to do that without unlocking BL?
Click to expand...
Click to collapse
Not that I'm aware of, you might want to try a Factory Data Reset first. After doing the appropriate backups first of course.
If that fails, unlock the BL, flash stock. Once you verify it works lock the BL again. You might have to FDR again to get the Play Store to show Certified if clearing data under Apps doesn't work.
I wish I could still trust my Robin, but I have a battery heating issue that nothing seems to fix. Hence my signature showing my former backup phone as my DD.
Sent from my ZTE B2017G using XDA Labs