Database Develop

Can not load device. deleted some system font, after restart it holds on white screen

Can see just HTC that's it.
Can i recover it?
Please help...

Hey came across this on under the "latest" tab, I don't have the same device as you, so my advice could be way off base. but if you can get into recovery mode then you're fine, just do a data wipe/factory reset in recovery mode. If that doesn't work, flash a new rom. This is assuming you have root and a custom recovery.
Sent from my SGH-I777 using XDA App

How can i flash a new rom? where can i get it? I can not get to recovery mode

I'm afraid you may be out of luck. Unless someone more familiar with your device has better advice. Knowing what I know about android, it appears you've "hard bricked" your phone, and there may not be a possibility of recovery.
Sent from my SGH-I777 using XDA App

Windows can see device as android 1.0 but it can not install any driver.
Is it possible to installsome driver?
There is no HTC service center in my country to flash my device...
please help.

here is a link to stock roms
http://forum.xda-developers.com/showthread.php?t=1317895
Sent from my HTC_Amaze_4G using xda premium

I can interract with my device from fastboot.
do you have any idea how can i recover my phone?

I can interract with my device from fastboot.
do you have any idea how can i recover my phone?

giorgit28 said:
I can interract with my device from fastboot.
do you have any idea how can i recover my phone?
Click to expand...
Click to collapse
Did you unlock the bootloader at the HTCdev website? If so you need to relock it in fastboot (type fastboot oem lock ... I think its that, someone correct me if I'm wrong) and install one of the stock roms from the link a couple of posts up.
DO NOT try to install a stock rom with the bootloader unlocked!!!!!
If you didn't unlock the bootloader, thats where the problem is, install a stock rom and then go to HTCdev.com to unlock the bootloader, once that is done you can then root and install capys rom

Vertigo:
Yep, i reloked phone from
fastboot with command
fastboot oem relock
Then i have installed official ROM (exe)
And thats it.
It was so easy... I have spent about 10-12 hour with my pc and phone to made that solution....
I AM HAPPY!!!!!!!!!!!!!!!!

giorgit28 said:
Vertigo:
Yep, i reloked phone from
fastboot with command
fastboot oem relock
Then i have installed official ROM (exe)
And thats it.
It was so easy... I have spent about 10-12 hour with my pc and phone to made that solution....
I AM HAPPY!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
I'm glad you've managed to sort it
If you wanna instal capys rom follow shingers5 method to the letter here... http://forum.xda-developers.com/showthread.php?t=1366238

[vertigo] said:
I'm glad you've managed to sort it
If you wanna instal capys rom follow shingers5 method to the letter here... http://forum.xda-developers.com/showthread.php?t=1366238
Click to expand...
Click to collapse
Thanks Man
I have installed that custom rom.
Nice one.

good to see us all getting involved here. was about to post but see that we have some great folks in here

shingers5 said:
good to see us all getting involved here. was about to post but see that we have some great folks in here
Click to expand...
Click to collapse
Well you've been a big help to a lot of us here, just glad I could help

Umm, just in case
In such situation you don't need to wipe everything and flash a new rom...
just push original font back to the fonts folder via adb and that's it...

Adiost said:
Umm, just in case
In such situation you don't need to wipe everything and flash a new rom...
just push original font back to the fonts folder via adb and that's it...
Click to expand...
Click to collapse
In fastboot mode you can not use adb. Because there is no any launched OS to use adb commands.

Can anyone help me too? I need the RUU for my Sensation XL with HTC__038 (India)

I have this Sensation XL long time ago and i lost all the box , doccument, now i want to flash back to ship rom but i dont know what version of ship rom should i need and what religion my phone are . Anyone can help ?

justbenice said:
I have this Sensation XL long time ago and i lost all the box , doccument, now i want to flash back to ship rom but i dont know what version of ship rom should i need and what religion my phone are . Anyone can help ?
Click to expand...
Click to collapse
Any in the runnymede official rom thread should work. Some people have not been able to use them sucessfully but on a whole majority have been ok
Sent from my GT-I9100 using xda premium

justbenice said:
I have this Sensation XL long time ago and i lost all the box , doccument, now i want to flash back to ship rom but i dont know what version of ship rom should i need and what religion my phone are . Anyone can help ?
Click to expand...
Click to collapse
Hi,
Try the following:
1. Download adb tools. (www.filesonic.com/file/1774628264)
2. On your pc click on your local disk C: Drive (or D: drive for some) (WINDOWS users: Start > My computer > Local Disk (C)
3. Create a new folder called "adb" and extract the files from adb.zip into it. Make sure it doesn't create another folder in the adb folder when extracting
4. open command prompt (or terminal for linux) and type "cd" "followed by the path to your adb folder" (windows users can type "cd C:\adb")
5. Don't forget to enable the "usb debugging" when you connect it by the USB.
6. Enter in the command prompt screen the following:
adb devices
adb reboot-bootloader
fastboot getvar cid
7. If your mobile is from Europe, it will give you: HTC__001.
8. You can search the net for other codes and accordingly, download the suitable RUU file. If you are unlucky like me, your mobile will show "HTC__038" .
Good luck.
---------- Post added at 07:28 AM ---------- Previous post was at 07:24 AM ----------
shingers5 said:
Any in the runnymede official rom thread should work. Some people have not been able to use them sucessfully but on a whole majority have been ok
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thank you for the reply but I tried, Eurpoe, wwe, Asia, Thailand softwares but I couldn't. As lomg as the mobile is still S-On, you can only istall the RUU of the mobile region.
Thanks.

How to get your BELL ATRIX HD onto At&t Jellybean (4.1.1) - Unlocked bootloader ONLY!

How to get your BELL ATRIX HD onto At&t Jellybean (4.1.1) - Unlocked bootloader ONLY!
I would like to start saying that I’m not responsible for whatever happens to your phone. Thanks to MATTLGROFF who figure out this way of flashing this jellybean leak on my phone.
Having that said THIS IS ONLY FOR BELL ATRIX HD USERS THAT HAVE THEIR BOOTLOADER UNLOCKED. Please read thru and ask any questions before attempting
OK here we go:
1. I assume you’re in stock BELL ICS ROM (77.55.18.MB886.BellMobility.en.CA) … it doesn’t matter if you’re rooted or not. Make sure you have the motorola drivers installed.
2. Enable debugging mode on your phone (settings>development options> enable USB debugging)
3. MAKE SURE YOU HAVE AN UNLOCKED BOOTLOADER. To do this open command prompt and type “adb reboot-bootloader” and check....
a. It should say: "Device is UNLOCKED. Status Code:1"
4. Now double check you’re unlocked.
5. Make sure you have a charged battery (more than 60%) and boot into fastboot. (if you're not already here)
6. Now download the stock ICS zip for At&t.
a. Unzip it
b. Make sure you have the fastboot files in the same folder/path as your fxz files.
c. Flash the boot.img from the at&t zip.
i. Hold the shift key down and right click on the unzipped folder. Now in the dropdown menu click “open command prompt here”
ii. Now type “fastboot flash boot boot.img”
d. Flash the system.img
i. "Fastboot flash system system.img”
ii. you should be in Stock att ICS rom now.
7. Now download the file for the stock at&t Jellybean zip. ( you will be able to go back to ICS --I have gone back to stock 4.0.4 Bell ROM-- bc you’re only flashing boot and system images)
8. Now start back at step 6 but with the jelly bean leak ---- Or you can try just going to settings and checking for updates! (haven't tried this yet - don't know if it will flash something we don't want it to UPDATE: I guess it doesn't work)
9. You should be on AT&T Jellybean now - and you probably(thanks soulja) lost root...
Fastboot link: https://www.dropbox.com/s/rhlcajoerowtpiw/fastboots.zip
Stock ICS link: http://forum.xda-developers.com/showthread.php?t=1853522
Stock JB link: https://www.dropbox.com/s/65ro5ddf5mhdc9f/7.7.1Q-144_MB886_MR1-22_SIGNED_CFC.xml.zip

reserved. IF you have any questions please ask!

gabo_e30 said:
3. MAKE SURE YOU HAVE AN UNLOCKED BOOTLOADER. To do this open command prompt and type “adb reboot-bootloader” and check....
a. It should say: "Device is UNLOCKED. Status Code:1"
4. Now double check you’re unlocked.
5. Make sure you have a charged battery (more than 60%) and boot into fastboot. (if you're not already here)
Click to expand...
Click to collapse
You might want to just clarify that "adb reboot-bootloader" puts the device into fastboot. Took me a few minutes to figure that out.
gabo_e30 said:
9. You should be on Jellybean now - and you prolly lost root...
Click to expand...
Click to collapse
...probably! not "prolly"!
OK, so I think I followed the directions properly, it appears SafeStrap is gone, and I now get new boot animations, a "thumping" Motorola logo and then an AT&T Rethink Possible. But it seems to be stuck after it plays that, with the AT&T logo and "Rethink Possible" message. Help!
UPDATE: After much flailing about, I got it into Recovery mode (could only get there by adb reboot recovery, the vol up/down + pwr only gets me a white texted menu which included "factory" but didn't do anything".) Will see if this works.
UPDATE 2: YES! After the factory reset, I let it boot up again. I was about to give up and try going back to ICS, but then it went past the Rethink Possible logo to a configure phone screen.
UPDATE 3: What... OK so it thinks it's an AT&T phone now, that's OK. It also shows it connected to 4G which it never has (always E, H or H++) But it's still on 4.0.4 ICS even though I did load the JB rom. But I just checked updates and it's got 4.1.1!!
UPDATE 4: Update (98.4.20.en.US) downloaded. Hitting install now...
UPDATE 5: CRAP. After reboot "The software update failed!" I might try reflashing the file from 7.7.1Q-144_MB886_MR1-22_SIGNED_CFC
UPDATE 6: No joy. :/ Any tried flashing Blur_Version.77.12.22.MB886.ATT.en.US.zip? After the above procedure, is my phone now "really" an AT&T phone?
UPDATE 7: I followed the thread about fixing failed update http://forum.xda-developers.com/showthread.php?t=2050416, and then got the OTA update. THIS TIME IT WORKS!!! I did lose root though. Oh well. I tried motofail2go again, but I couldn't get the "bug report" vibrate to happen.

noob problem with adb
3. MAKE SURE YOU HAVE AN UNLOCKED BOOTLOADER. To do this open command prompt and type “adb reboot-bootloader” and check....
a. It should say: "Device is UNLOCKED. Status Code:1"
sorry where in PC or in motorola atrix ? need i another app ? thanks in advance
i just unlocked root with Motofail2Go

w0hnzimmer said:
3. MAKE SURE YOU HAVE AN UNLOCKED BOOTLOADER. To do this open command prompt and type “adb reboot-bootloader” and check....
a. It should say: "Device is UNLOCKED. Status Code:1"
sorry where in PC or in motorola atrix ? need i another app ? thanks in advance
Click to expand...
Click to collapse
First step is actually to get Motorola drivers installed on your PC, as well as adb tools. Sorry I don't have a link handy. Then from PC do the "adb reboot-bootloader".

Can this be done with at&t and why not ?
Seems like you can go jb > ics easily.

souljaboy said:
Can this be done with at&t and why not ?
Seems like you can go jb > ics easily.
Click to expand...
Click to collapse
Step #4 and the title to the thread.
Sent from my MB886 using xda premium

capran said:
First step is actually to get Motorola drivers installed on your PC, as well as adb tools. Sorry I don't have a link handy. Then from PC do the "adb reboot-bootloader".
Click to expand...
Click to collapse
thanks, now i got "Device is LOCKED. Status Code: 0"
any chance to unlock ?
regards

w0hnzimmer said:
thanks, now i got "Device is LOCKED. Status Code: 0"
any chance to unlock ?
regards
Click to expand...
Click to collapse
The title of this threads says "Unlocked bootloader ONLY!" You haven't unlocked it yet. Please go read up on how to do that first.
1. Root. http://forum.xda-developers.com/showthread.php?t=1940594
2. Can't seem to find the bootloader bit...

ATGAdmin said:
Step #4 and the title to the thread.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
i know...
what unlocked changes is, you can replace the kernel... but the RSDLite can replace it too, i dont quite get it.

capran said:
You might want to just clarify that "adb reboot-bootloader" puts the device into fastboot. Took me a few minutes to figure that out.
...probably! not "prolly"!
OK, so I think I followed the directions properly, it appears SafeStrap is gone, and I now get new boot animations, a "thumping" Motorola logo and then an AT&T Rethink Possible. But it seems to be stuck after it plays that, with the AT&T logo and "Rethink Possible" message. Help!
Click to expand...
Click to collapse
YOu need to do a factory reset! Sorry forgot to include that in the steps! My Bad!
UPDATE: After much flailing about, I got it into Recovery mode (could only get there by adb reboot recovery, the vol up/down + pwr only gets me a white texted menu which included "factory" but didn't do anything".) Will see if this works.
UPDATE 2: YES! After the factory reset, I let it boot up again. I was about to give up and try going back to ICS, but then it went past the Rethink Possible logo to a configure phone screen.
Click to expand...
Click to collapse
YESSS!!! you figured it out!
UPDATE 3: What... OK so it thinks it's an AT&T phone now, that's OK. It also shows it connected to 4G which it never has (always E, H or H++) But it's still on 4.0.4 ICS even though I did load the JB rom. But I just checked updates and it's got 4.1.1!!
Click to expand...
Click to collapse
Yeah 4G is the same as H+, that's just how At&t symbolizes it
UPDATE 4: Update (98.4.20.en.US) downloaded. Hitting install now...
UPDATE 5: CRAP. After reboot "The software update failed!" I might try reflashing the file from 7.7.1Q-144_MB886_MR1-22_SIGNED_CFC
Click to expand...
Click to collapse
I guess it won't work huh?... we were lucky if it did!
UPDATE 6: No joy. :/ Any tried flashing Blur_Version.77.12.22.MB886.ATT.en.US.zip? After the above procedure, is my phone now "really" an AT&T phone?
Click to expand...
Click to collapse
No it's not really an at&t phone... you can flash back the Bell 4.0.4 ROM (I just did it). Remember it will ONLY WORK IF YOU HAVE AN UNLOCKED BOOTLOADER!
UPDATE 7: I followed the thread about fixing failed update http://forum.xda-developers.com/showthread.php?t=2050416, and then got the OTA update. THIS TIME IT WORKS!!! I did lose root though. Oh well. I tried motofail2go again, but I couldn't get the "bug report" vibrate to happen.
Click to expand...
Click to collapse
Cool you found a solution...(?) But it should work with the above Jellybean file. Gonna try it out again myself!

w0hnzimmer said:
3. MAKE SURE YOU HAVE AN UNLOCKED BOOTLOADER. To do this open command prompt and type “adb reboot-bootloader” and check....
a. It should say: "Device is UNLOCKED. Status Code:1"
sorry where in PC or in motorola atrix ? need i another app ? thanks in advance
i just unlocked root with Motofail2Go
Click to expand...
Click to collapse
Ok. SO install the moto drivers first (just google them -Motocast)
Now the fastboot files and put them in the same folder or path of the system and boot.img
Now connect your phone and make sure its in debugging mode
Open command prompt (cmd) in the folder you have the files you want to install. (do this by holding shift and right click on that folder)
Now type adb reboot bootloader IN CMD. You phone should reboot into fastboot! :victory:

capran said:
The title of this threads says "Unlocked bootloader ONLY!" You haven't unlocked it yet. Please go read up on how to do that first.
1. Root. http://forum.xda-developers.com/showthread.php?t=1940594
2. Can't seem to find the bootloader bit...
Click to expand...
Click to collapse
Capran you can't install it following this procedure. It won't work or you will brick.
This si only for unlocked bootloader Atrix HDs. There's only a few of them out there (they all seem to be BELL models, but not all Bell models) I think its the ones that shipped with system version: 77.55.17.MB886.BellMobility.en.CA. TheBootloader version is 10.96 i believe... and the locked one is 10.97 I think...

souljaboy said:
i know...
what unlocked changes is, you can replace the kernel... but the RSDLite can replace it too, i dont quite get it.
Click to expand...
Click to collapse
From what I understand is that RSDlite changes it but after and Only with kernels and files that r signed (by Moto)

gabo_e30 said:
Capran you can't install it following this procedure. It won't work or you will brick.
This si only for unlocked bootloader Atrix HDs. There's only a few of them out there (they all seem to be BELL models, but not all Bell models) I think its the ones that shipped with system version: 77.55.17.MB886.BellMobility.en.CA. TheBootloader version is 10.96 i believe... and the locked one is 10.97 I think...
Click to expand...
Click to collapse
How about the 77.55.18.MB886.BellMobility.en.CA can we flash it to our unlocked Atrix hd? I saw that there's an update to JB 4.1.2. on this version. Thanks
Sent from my MB886 using xda premium

I have an unlocked Bell Atrix HD. It was running 77.55.17 and I tried this method of flashing the AT&T software using fastboot and it didn't work. I could flash the boot.img, but when I went to flash the system.img.ext4 it would tell me that I had exceeded the download buffer. So at this point I had flashed the boot.img already and the phone wouldn't boot. I actually couldn't get any system.img files to flash from fastboot, even the Bell one, always the same exceeded the download buffer error. So I downloaded RSD lite and flashed the 77.55.18 Bell firmware to it via RSD lite and I was back in business again. At this point I just said to heck with it with fastboot and then flashed the stock ICS AT&T firmware via RSD lite only having used the modified XML file that is suggested to use. This worked perfectly fine as well. I was then able to root with motofail and use voodoo to backup my root. Then I just let it do the JB update OTA and that worked perfectly fine as well and then restored my root through voodoo and verified I still had root. Everything looks fine. The funny thing is I'm selling this phone, I have a Galaxy Note II now, but I was worried if I sold it with the Bell firmware nobody would want it since it was still ICS. Should be a bonus to someone that its unlocked, and rooted already hopefully.

ryuben2k said:
How about the 77.55.18.MB886.BellMobility.en.CA can we flash it to our unlocked Atrix hd? I saw that there's an update to JB 4.1.2. on this version. Thanks
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
I used RSDlite (the latest one) to flash the 77.55.18 version on my phone.. now its the one im currently running. SO yeah you can flash it! ( i still don't have an update though) Link for teh FXZ file is in the OP (same place where the ICS at&t ROM is)

BHUGHESVA said:
I have an unlocked Bell Atrix HD. It was running 77.55.17 and I tried this method of flashing the AT&T software using fastboot and it didn't work. I could flash the boot.img, but when I went to flash the system.img.ext4 it would tell me that I had exceeded the download buffer. So at this point I had flashed the boot.img already and the phone wouldn't boot. I actually couldn't get any system.img files to flash from fastboot, even the Bell one, always the same exceeded the download buffer error. So I downloaded RSD lite and flashed the 77.55.18 Bell firmware to it via RSD lite and I was back in business again. At this point I just said to heck with it with fastboot and then flashed the stock ICS AT&T firmware via RSD lite only having used the modified XML file that is suggested to use. This worked perfectly fine as well. I was then able to root with motofail and use voodoo to backup my root. Then I just let it do the JB update OTA and that worked perfectly fine as well and then restored my root through voodoo and verified I still had root. Everything looks fine. The funny thing is I'm selling this phone, I have a Galaxy Note II now, but I was worried if I sold it with the Bell firmware nobody would want it since it was still ICS. Should be a bonus to someone that its unlocked, and rooted already hopefully.
Click to expand...
Click to collapse
Glad you worked it out! The first time I did it was from the 77.55.17 version, then I updated to at&t ICS the to JEllybean and now back to Bell ICS (77.55.18) Not sure what happened, but still glad you worked it out!
That's the great thing about the forums we can all work together in solving issues!

gabo_e30 said:
Glad you worked it out! The first time I did it was from the 77.55.17 version, then I updated to at&t ICS the to JEllybean and now back to Bell ICS (77.55.18) Not sure what happened, but still glad you worked it out!
That's the great thing about the forums we can all work together in solving issues!
Click to expand...
Click to collapse
Indeed, so glad I didn't brick it, lol. Maybe it was something wrong with the fastboot executables I used, I used the same ones I had downloaded a couple weeks ago to flash the HTC One V's that I got my kids for Christmas and not the ones linked to in the original post. It worked fine for for the One V's, not for the Atrix HD for some reason. Oh well, I just like tinkering with this stuff.

gabo_e30 said:
I used RSDlite (the latest one) to flash the 77.55.18 version on my phone.. now its the one im currently running. SO yeah you can flash it! ( i still don't have an update though) Link for teh FXZ file is in the OP (same place where the ICS at&t ROM is)
Click to expand...
Click to collapse
Thanks. Here's the link that i saw from motorola that there's an update for 77.55.18. and if someone from here can prove that they already upgrade to 4.1.2.
Thanks
https://motorola-global-en-usa.custhelp.com/app/answers/detail/a_id/92147
Sent from my MB886 using xda premium

error: device not found

Hi right now Im trying to unlock my bootloader and im on the EUR-XXX one But when I try adb reboot oem-unlock
I just get error:device not found

fatality911 said:
Hi right now Im trying to unlock my bootloader and im on the EUR-XXX one But when I try adb reboot oem-unlock
I just get error:device not found
Click to expand...
Click to collapse
Have you installed the adb drivers?

noppoer2 said:
Have you installed the adb drivers?
Click to expand...
Click to collapse
I dunno Where do I find them?

Download the file in http://forum.xda-developers.com/showthread.php?t=2180688
Then put the adb.exe file in your windows directory.
Enable USB debugging on phone.
You should be able to get it working from there.

boonkeng said:
Download the file in http://forum.xda-developers.com/showthread.php?t=2180688
Then put the adb.exe file in your windows directory.
Enable USB debugging on phone.
You should be able to get it working from there.
Click to expand...
Click to collapse
Noob question but where is windows directory?

fatality911 said:
Noob question but where is windows directory?
Click to expand...
Click to collapse
c:/windows

boonkeng said:
c:/windows
Click to expand...
Click to collapse
Kk thanks

fatality911 said:
Hi right now Im trying to unlock my bootloader and im on the EUR-XXX one But when I try adb reboot oem-unlock
I just get error:device not found
Click to expand...
Click to collapse
Use ALL in One tool for unlock
HERE
If you have root permission, put usb cable and enable debugging
Tool make it for you.
Select first 1 option for install adb driver then select 2 option,

Don't connect your device in USB 3.0... (for now isn't compatible)
Use USB 2.0.. and all have to run very nice!!!

manos20082 said:
Don't connect your device in USB 3.0... (for now isn't compatible)
Use USB 2.0.. and all have to run very nice!!!
Click to expand...
Click to collapse
I rooted and unlocked from a 3.0 port
Sent from my LG-P880 using xda app-developers app

alekthefirst said:
I rooted and unlocked from a 3.0 port
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
I don't kwon about you, but i had this isue before!!!
maybe this is the reason, but i don't know...
anyway... :angel:

[Q] Possibly soft bricked my device

I unlocked my bootloader and everything was fine. Then I installed CM10.1.2 and it loads to the initial Welcome screen (where you select country) but the touch doesn't work at all. The volume and power button works but I can't tap anything.
Also no softbutton shows.
I also tried flashing CM10.1.0 and the latest FXP rom.
If anyone helps solve this it would be so appreciated.

Sounds like you flashed the wrong version for your phone.
Which phone do you have and which cm dud you flash
Sent from my LT30p using xda premium

gregbradley said:
Sounds like you flashed the wrong version for your phone.
Which phone do you have and which cm dud you flash
Sent from my LT30p using xda premium
Click to expand...
Click to collapse
I have an Xperia T and I flashed CM Mint.

ok, try flashing a stock ftf in flashtool to see if touch screen comes back.
If that works redownload the cm mint .zip and try flashing it again.
Let me know how you get on

gregbradley said:
ok, try flashing a stock ftf in flashtool to see if touch screen comes back.
If that works redownload the cm mint .zip and try flashing it again.
Let me know how you get on
Click to expand...
Click to collapse
Okay trying to find an appropriate stock ftf, or does it not really matter?
Like if I had a central european unbranded one or something on my UK Orange phone?

foxyfennec said:
Okay trying to find an appropriate stock ftf, or does it not really matter?
Like if I had a central european unbranded one or something on my UK Orange phone?
Click to expand...
Click to collapse
doesn't matter, just make sure its fir the right phone model or use one of mine from the all in one thread (Its Vodafone, but that does not matter)

gregbradley said:
doesn't matter, just make sure its fir the right phone model or use one of mine from the all in one thread (Its Vodafone, but that does not matter)
Click to expand...
Click to collapse
I flashed yours onto my phone and it loads up but the same problem happens The touchscreen still doesn't work.
I saw this earlier before heading to work: http://forum.xda-developers.com/showpost.php?p=39920703&postcount=11
But when I adb shell I don't get a [email protected] I have some garbled text. Basic commands like ls work. su is not found though, neither is the rmi4_fwloader command found. But then adb devices showed it in "recovery" mode not "device". Though on this computer adb devices shows nothing but fastboot does. Did flashing the stock rom relock it?
Thanks

foxyfennec said:
I flashed yours onto my phone and it loads up but the same problem happens The touchscreen still doesn't work.
I saw this earlier before heading to work: http://forum.xda-developers.com/showpost.php?p=39920703&postcount=11
But when I adb shell I don't get a [email protected] I have some garbled text. Basic commands like ls work. su is not found though, neither is the rmi4_fwloader command found. But then adb devices showed it in "recovery" mode not "device". Though on this computer adb devices shows nothing but fastboot does. Did flashing the stock rom relock it?
Thanks
Click to expand...
Click to collapse
That postwas my next piece of advice to you...
ok, have you unlocked your bootloader? Have you rooted the new firmware? Use bin4ry or doomlords rooting method to root the firware and try again.
also, you can use a USBOTG cable and a mouse to control the phone instead of the touchscreen

gregbradley said:
That postwas my next piece of advice to you...
ok, have you unlocked your bootloader? Have you rooted the new firmware? Use bin4ry or doomlords rooting method to root the firware and try again.
also, you can use a USBOTG cable and a mouse to control the phone instead of the touchscreen
Click to expand...
Click to collapse
The bootloader was still unlocked after putting your firmware on.
Is there a way of enabling usb debug mode outside of the phone? I'm guessing that's what's needed to get adb shell to work.
Woohoo! Progress! Still broken, but progress!!!!
I installed PdaNet and it made adb drivers work. Then I did adb shell from recovery.
This part is important:
The path is messed up on my phone so if anyone has trouble with that method for similar reasons would have to do the same:
Code:
/sbin/su
/system/bin/rmi4_fwloader -b /system/etc/firmware/touch_module_id_0x32.img -d /sys/bus/rmi4/devices/sensor00 -r -f
(echo $PATH is /sbin/ but for some reason su doesn't work without /sbin/. if /sbin/su doesn't work what I actually did was cd /sbin then su)
(It is important to run /system/bin/rmi4_fwloader because it simply can't find rmi4_fwloader, even if you cd /system/bin/)
Now my touch works! I just have no software buttons
Any idea how to get my.. nevermind, after going through the startup bit they just appeared.
Thank you you are a genius!

No problem, Glad its sorted for you now.

[Q] wifi not working

when you go into settings the wifi is grayed out. I tried a hard reset and same problem exist. My other tablets all work fine. Any Suggestions?

kapebretoner said:
when you go into settings the wifi is grayed out. I tried a hard reset and same problem exist. My other tablets all work fine. Any Suggestions?
Click to expand...
Click to collapse
Custom rom or stock? Name and Version? Kernel? bootloader version? Much more info required ......

wifi greyed out
sbdags said:
Custom rom or stock? Name and Version? Kernel? bootloader version? Much more info requires
stock rom
android version 4.3
Click to expand...
Click to collapse

kapebretoner said:
sbdags said:
Custom rom or stock? Name and Version? Kernel? bootloader version? Much more info requires
stock rom
android version 4.3
Click to expand...
Click to collapse
If a factory reset doesn't fix it and you haven't unlocked and customised it then it looks like a hardware failure to me.
Can you enable usb debugging in settings / developer settings and try and capture a logcat and dmesg. That will tell us for sure.
Zip them up and post them please.
Run these from a pc (you will need to install adb if you don't have it) whilst connect to the tablet via a command line prompt.
Code:
adb logcat -v time > logcat.txt
adb dmesg > dmesg.txt
Click to expand...
Click to collapse

this is what I get when enter the first command listed.
the process cannot access the file because it is being used by another process.

kapebretoner said:
this is what I get when enter the first command listed.
the process cannot access the file because it is being used by another process.
Click to expand...
Click to collapse
What do you get with the command
Code:
adb devices
Copy the entire contents of the cmd window and post it please.