Database Users

Fastboot> Recovery dosen't find *.img file on SD card

Hi Guys!
I am trying to root my nexus, unlocked it, installed the right usb drivers, I can see the phone and everything looks right.
Downloaded Superboot for ERE27 with himem enabled and ran this. no problem.
I put the img file on the SD card and when I boot the phone in Fastboot / Recovery it does not find and img files on the SD card.
I tried 2 different cards and also different img files.
When I do this I get first the message no images found than I see the droid with a triangle and a ! in it. - Have to pull the battery.
Ideas anyone?
Thanks

What are you trying to do?
1) you had to unlock the bootloader which enables you to install a new recovery image (which is needed to allow you to install new roms)
2) you had to apply the recovery image Amon RA via a command prompt and a batch file if you use Windows. The phone's USB connection needs to be in development mode and once the batch file executes and successfully finishes you need to reboot the phone.
3) you restart the phone into bootloader mode, use the volume rocker to select the recovery console. If you end up with an andriod and exclamation symbol the Amon RA recovery file was not installed.
4) the new recovery console allows you to clean the SD card. Install roms from the SD card and some other commands. The Roms for the Andriod are in ZIP format and do not need to be unziped. In other words all you need to copy to the SD card is the full ZIP file (approx 75MB) and install that directly from the recovery console.
If your android stays in the booting sequence which is shown as the X with flying little pixels, it's most likely because you did not wipe the device clean first. That item is in the recovery console as well.
Hope this helps. I am just as new to this as you are.

You didn't unzip them did you?

You're trying to root with superboot. Great, but the recovery is not capable of flashing .img files, only .zip updates and roms and such. .img files have to be flashed using fastboot, not recovery, and are flashed from the connected computer.
If you read the superboot instructions from wherever you got the file, you'll see that you have to put the .img in the same directory ON YOUR COMPUTER as fastboot, connect via USB, boot the phone into fastboot, then enter the appropriate command line on the computer to flash the file.
If you've done that, then you are officially DONE with the rooting process.
Also, make damn sure that the superboot version matches the software version on your phone. They're both ERE27, right?
I'm not sure what anosis's post is talking about, but that looks more like the process for installing a custom rom (ie cyanogenmod), than rooting.
To root your phone, you DO NOT need Amon-RA's recovery. You only need that if you want to install custom roms, etc. It wont hurt to have it, as it includes many more functions than the stock recovery, but just to root, you don't need it.
Summary:
If you flashed the superboot.img from your computer via fastboot, your phone is rooted. Done.
You don't need to do anything in the recovery at all for rooting. Only for installing update.zips and custom rom.zips.

Hey, So I have been scouring the forums trying to find some answers about this and you seem to be the closet to my situation. Here is what I did:
So I was running a CM9 Aplha, reverted back to stock 2.3.6 [1ada25375426.signed-soju-ota-189904.1ada2537]) so that I could then apply ICS update [VQ8PQk_V]) which I sucessfully did. This was about a month ago and it was all going well.
Then yesterday I wanted to upgrade to 4.0.4 [hR7QFEtn] so I did and superuser wasn't working properly but then I reinstalled it and got it to work. However I got to the point where everything was working fine EXCEPT for the Google Play store kept on force closing. I spent hours trying last night and could not find a solution.
I tried restoring the previous ICS update that I had and it worked, and then I tried updating again. Also side: My clockwork was on the fritz lately so I was using Zedowmaxs force into clockwork recovery image [fastboot boot recovery3101.img] to force it in sometimes.
Anyway bottom line here is where my REAL ISSUE begins. I decided just to wipe everything and start anew. I factory reset/ wiped properly [cache partition and davliche cache] and then locked my bootloader again. Then tried rebooting. Got stuck on Google screen. Then I unlocked my bootloader again. Tried again, same issue.
So, here is where I am at. Cannot get into recovery from fastboot, takes me back to fastboot. AND, everything is wiped because I locked/unlocked my bootloader. All I can do is adb commands.
I don't know what to do from here and there is a lot of things going on. If you could help that would be great!? What I am going to try next is to flash some recovery on, but I don't know which one/ try to mount a file to my sd card from adb commands.

Daboxk said:
Hey, So I have been scouring the forums trying to find some answers about this and you seem to be the closet to my situation. Here is what I did:
So I was running a CM9 Aplha, reverted back to stock 2.3.6 [1ada25375426.signed-soju-ota-189904.1ada2537]) so that I could then apply ICS update [VQ8PQk_V]) which I sucessfully did. This was about a month ago and it was all going well.
Then yesterday I wanted to upgrade to 4.0.4 [hR7QFEtn] so I did and superuser wasn't working properly but then I reinstalled it and got it to work. However I got to the point where everything was working fine EXCEPT for the Google Play store kept on force closing. I spent hours trying last night and could not find a solution.
I tried restoring the previous ICS update that I had and it worked, and then I tried updating again. Also side: My clockwork was on the fritz lately so I was using Zedowmaxs force into clockwork recovery image [fastboot boot recovery3101.img] to force it in sometimes.
Anyway bottom line here is where my REAL ISSUE begins. I decided just to wipe everything and start anew. I factory reset/ wiped properly [cache partition and davliche cache] and then locked my bootloader again. Then tried rebooting. Got stuck on Google screen. Then I unlocked my bootloader again. Tried again, same issue.
So, here is where I am at. Cannot get into recovery from fastboot, takes me back to fastboot. AND, everything is wiped because I locked/unlocked my bootloader. All I can do is adb commands.
I don't know what to do from here and there is a lot of things going on. If you could help that would be great!? What I am going to try next is to flash some recovery on, but I don't know which one/ try to mount a file to my sd card from adb commands.
Click to expand...
Click to collapse
It looks like the time when you were locking-unlocking the bootloader, you messed up the recovery. Since your phone can get into bootloader menu, I think you can get out of this issue.
Here is what I would do.
1. Unlock the bootloader.
2. flash clockworkmod recovery using fastboot USB.
3. Download recovery-RA-passion-v2.2.1.img, put it in C:\fastboot\
4. Shut down your phone. Then start your Nexus One in Fastboot mode by holding down the Trackball and press the Power button.
5. Connect your phone to your computer. Open a Command Prompt (Start -> All Programs -> Accessories -> Command Prompt), and run the following commands:
cd C:\fastboot
fastboot devices
fastboot flash recovery recovery-RA-passion-v2.2.1.img
now see if you can get into recovery. If you can, just flash a custom rom using install zip from sd card option in the recovery

I didn't read all the replies but fastboot reads from your PC's disk not the sdcard, unless you are running it through shell or something?

[Q] fastboot - no boot or img file

hey guys i'm having some trouble. i just got the nexus (it's my first smartphone, ever) and i've tried to hit the ground running. here's what i've done to the phone so far.
i got all the drivers running on my win7 machine and also installed the android SDK folder onto C: as was described in this thread: http://forum.xda-developers.com/showthread.php?t=878786
i then unlocked the bootloader using the above guide as well. when I power on the phone using UP+POWER it says UNLOCKED.
I then proceeded to follow this guide: http://forum.xda-developers.com/showthread.php?t=875875
i used ADB to flash the clockwork crespo recovery. i then used fastboot to install Superuser.
at that point i had an unlocked bootloader, clockword recovery image and superuser permissions.
i then saw that the 2.3.1 update had been released. i wanted to learn how to tackle that so i started reading up. i noticed that people were using ROM Manager and Titanium. I got titanium and installed the BusyBox addon and it allowed me to do a full Batch Backup of all my programs, etc. i've got the 50MB or so backup folder on my PC now.
anyway, i then messed with Rom Manager. I installed the 3.0.0.0 ClockworkMod Recovery and everything went smoothly. now this is where my troubles begin.
when i go to Download ROM all i get is a Free Stuff area.
when i go to Check for ROM Updates it tells me my device isnt set up for OTA updates.
those are just minor issues.
this is the big and scary issue i have:
when i click on reboot to recovery, it takes me to the same screen that i go to when i power on with VOLUME UP+POWER. it doesnt take me to the recovery screen that i see in various youtube videos. instead, i'm at the main screen where it says UNLOCKED and i have 4 choices (reboot bootloader, recovery, reboot, power off). and on the very top in RED letters it says fastboot - no boot or img file. <-- this is the part that makes me nervous. If i manually power down the phone and boot to fastboot and click recovery, it just goes back to this same screen and says fastboot - no boot or img file. when i first rooted the phone, clicking recovery actually took me to a different screen where i was able to load up superuser.zip and install it.
did i accidetnally delete something that i wasnt supposed to? did installing ROM manager mess something up? i typically dont do anything until i confirm that i am supposed to. i think the problem is that i dont yet know how one thing i do on the phone affects another. i'm guessing when i used rom manager to update the CWmod it changed some folders/files? i dunno!
otherwise, the phone works fine and there are no glitches or hiccups or crashes. So if someone can please take a moment to just explain to me what i did wrong or what i failed to do i'd really, really appreciate it.

you don't have a recovery partition. Either flash one over manually using fastboot, or boot up and try to use ROM Manager to flash CWR.

when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?

kramer987 said:
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
Click to expand...
Click to collapse
yes, just follow the examples in http://forum.xda-developers.com/showthread.php?t=875875

kramer987 said:
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
Click to expand...
Click to collapse
Yes, 'cept it will be "fastboot flash recoveryrecovery-clockwork-3.0.0.0-crespo.img" without the quotes now.
But does it say that you're missing a boot.img or recovery.img?
Also, the "not set up for OTA" thing isn't for official OTAs. Some developers have made their custom ROMs capable of being updated that way.

unremarked said:
Yes, 'cept it will be "fastboot flash recoveryrecovery-clockwork-3.0.0.0-crespo.img" without the quotes now.
But does it say that you're missing a boot.img or recovery.img?
Also, the "not set up for OTA" thing isn't for official OTAs. Some developers have made their custom ROMs capable of being updated that way.
Click to expand...
Click to collapse
thank you luxferro and unremarked. i did it and it works perfectly. i am now able to access clockworkmod recovery 3.0.0.0. next step is backup my existing ROM and also to figure out how to put the OTA 2.3.1 on and restore all my data
oh and unremarked: it basically said no boot or img file and thats it after i would click on recovery or reboot to recovery trhough rom manager. it was just in red at the top. but now it takes me to the ClockworkMod Recovery

status 7 error when updating roms? Bricked? **NOW Fixed!*

So it seems I have messed up my phone decently bad
decided to go back and reload everything from scratch but unfortunately flashed back a CWM version thats 3.0.1 and when I try to flash my old recovery (ICS CM9) it gives me error 7
I am guessing thats because I have to install 5.0 CWM can anyone explain to me how to do this?
Thank you so much all!
Yan
More Info:
Ok so heres the deal.
I was originally running CM9 from Nexus MV ICS rom with a Franco Kernel.
All was well and phone was rock solid for weeks since he released with everything working.
as the update came out I was told I should revert back to 2.3.6 and wait for the OTA update that way I could have the true OEM ICS. It is pretty much 90% of why I originally Rooted and unlocked my phone.
I used this link.
http://forum.xda-developers.com/showthread.php?t=1063664
and downloaded
Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
That I flashed using CWM
Phone rebooted fine but had no SuperUser file and seemed like it no longer was rooted so though if I go back and re-root it should be fine.
Went to.
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
and went straight to instruction 5) Open up a command prompt by typing “cmd” under Start->Search Programs and files.
Then type “cd \nexussrootnew” to browse into the directory in Windows. For Linux and Mac, should be similar to “cd /nexussrootnew“.
Then type “fastboot oem unlock“.
Thats when I went back to CWM 3.1.0.1 and tried to install any rom or backup and it just seems to give me Status 7 error.
I hate that I cant figure this out alone but I am a little lost.

Here's a link: http://forum.xda-developers.com/showthread.php?t=1382624
Use the search next time, it took less than 10 seconds for me to find the page.

063_XOBX said:
Here's a link: http://forum.xda-developers.com/showthread.php?t=1382624
Use the search next time, it took less than 10 seconds for me to find the page.
Click to expand...
Click to collapse
Actually I tried this originally
http://forum.xda-developers.com/showthread.php?t=1248760
Still get Status 7!
Sorry I usually search before just forgot to write that in!

Download CWM 5.0.2.0 and rename the .img to recovery.img
(i'll assume you have phone drivers and everything working, and fastboot)
Put the recovery.img into the same directory as your fastboot.exe
Boot into your bootmanager (vol up+power)
Plug phone into PC
Open up CMD prompt and change to the directory where you have fastboot.exe
(cd c:\android\tools) for example
type in:
> fastboot flash recovery recovery.img
reboot to recovery

seriosbrad said:
Download CWM 5.0.2.0 and rename the .img to recovery.img
(i'll assume you have phone drivers and everything working, and fastboot)
Put the recovery.img into the same directory as your fastboot.exe
Boot into your bootmanager (vol up+power)
Plug phone into PC
Open up CMD prompt and change to the directory where you have fastboot.exe
(cd c:\android\tools) for example
type in:
> fastboot flash recovery recovery.img
reboot to recovery
Click to expand...
Click to collapse
I tried that and unfortunately it gives me an error when I try it
says
"Error: cannot load recovery.img"
Used the download from this link!
http://forum.xda-developers.com/showthread.php?t=988686&highlight=recovery
Looks like someone else is having the same issue as me.
http://forum.xda-developers.com/showthread.php?t=996914&page=4

Try to just boot the newer cwm recovery with fastboot
Fastboot boot recovery recovery name.img

albundy2010 said:
Try to just boot the newer cwm recovery with fastboot
Fastboot boot recovery recovery name.img
Click to expand...
Click to collapse
Same error as earlier....
Can Not load
Darn this is frustrating!

sspikey said:
Same error as earlier....
Can Not load
Darn this is frustrating!
Click to expand...
Click to collapse
SWEET just got this phone to boot up again! No network right now for some reason but wifi works!
Here is what I used.
http://forum.xda-developers.com/showthread.php?t=884093
Where should I go from here? Ideas? I am guessing I have to install super user Zip through the current 3.0XX CWM right?
MORE PROGRESS!!!!!
Got CWM 5.0.2.0 loaded on to it by flashing the IMG through CMD
Worked after what I did earlier!
Progressing forward!!!!
Final cherry on top of the cake!!!
works perfectly again accepted my nandroid backup and shes running at 100%
ah feels good!

please help me i am also having the same problem i tried everything nothing seemed to work out and please check my thread ( http://forum.xda-developers.com/showthread.php?t=1533346 ) thnx.

I bricked my Nexus S. Please help.

I tried looking around the forums to see if someone has had this problem before. Couldn't find something similar.
I had stock 4.0.3 installed and I saw today that 4.0.4 was being pushed out. Since 4.0.3 wasn't a stock build I tried to downgrade to 2.3.6 in order to keep everything stock. I rooted the phone, installed the ROM Manager and flashed 2.3.6 through Clockworkmod Recovery. Everything went smoothly but when I powered on the phone force quit messages kept popping up and I can't get past the welcome screen. When I go into Fastboot mode and try to go in Recovery mode it just shows the Android symbol and a warning sign. I tried flashing a recovery .zip file I found online through fastboot but couldn't manage to do it (I'm on Mac OSX)
Can someone please help me? I'm completely desperate and wouldn't care about erasing everything (I think I already did, actually).
Thanks in advance.

flash a recovery.img
that multiple fc happened to me when i installed a i9023 rom on my i9020a.
unzip the recovery.zip and flash the .img file through fastboot and make sure you have the right rom for your model

Thank man, but that's what I tried to do. I got confused and wrote that it was a .zip up there. I'm really confused and couldn't flash the .img. Could you walk me through it? or point me to a thread that shows me how to do it?

im not sure how a mac is set up, i can walk you through flashing it on windows through command prompt ...

Please do that. I guess I can try to work it out.
Thanks

http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
memorize that lol it saved me.
you can skip the root part, but it explains how to set up the pc so it'll read the nexus with the correct drivers and whatnot, and what commands to run to flash the recovery. then when youre in the recovery, mount as usb, copy over 2.3.6 (the right one!) and install from zip.

I just tried that. I get this message: "error: cannot load 'twrp-crespo-2.0.0RC0.img'" I don't know what to do!

Can you get into boot loader mode?
Have you tried to use Odin?
http://forum.xda-developers.com/showthread.php?t=947950&highlight=odin
Sent from my Nexus S 4G using XDA Premium App

colettamiguel said:
I just tried that. I get this message: "error: cannot load 'twrp-crespo-2.0.0RC0.img'" I don't know what to do!
Click to expand...
Click to collapse
Did you unlock your bootloader?
Code:
fastboot oem unlock

[Q]LG G2 re-flashing or rooting stock 4.4.2 bad rom

Hi all,
First off I've tried now for a two days to solve this, reading as much as I could find on here and the rest of the internet.
I decided to root my LG D802 running 4.2 and install CWM recovery no problem. Next I flashed a stock 4.4.2 vodaphone img. All went well untill i tried to use the touch screen, which shows that when i press on one point on the screen it selects multiple points basically its unusable and unable to do almost anything with it, however i have managed to turn on ADB and connect to the phone. So now i have a stock recovery and an unusable ROM.
So next up I tried to rooting it since I had ADB shell working ok, using the IOROOT25. This appears to work as when it reboots and installs the kkroot.zip in the recovery it's saying it worked. Now when I reboot and open ADB shell then type SU to get root I can't press ok when superuser pops up to asking me to give it permission, because of the touch screen problem.
If i can get root in ADB then remount the files system then i will be able to DD a new recovery img??
After getting this far and loosing, I then found this: http://forum.xda-developers.com/showthread.php?t=2432476 on flashing to stock, but the program crashes every time it's about to flash, so i tried doing a fresh install of windows 7 and then tried windows 8 however the program still crashes every time and yes I have followed the instructions and tried the manual method and checking the 127.0.0.0. lgblahblah is there
So no I am turning to you guys for help.
phone details;
Model: D802 32GB
Firmware operator: VDF
sw version: D80220a
ro.build.fingerprint: lge/g2_vdf_com/g2:4.4.2/KOT49I.D80220a/D80220a.1392133741:user/release-keys
Recovery: <3e> KOT49I.D80220a test-keys

UPADATE: I have root but getting this error when trying to flash the recovery:
+] loki_flash v2.0
[-] Loki aboot version does not match device.
any ideas?
Ok so i found a different aboot img pushed to the phone and flashed that using dd
Code:
dd if=/data/local/tmp/about.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
this solved the problem above and a allowed me to flash cwm recovery. This then broke the installed rom so it wouldn't boot. now I had a custom recovery i flashed a EUR open 16gb stock zip this all went well and now i have a working phone What i should of done is remove the stock recovery.img from the zip and the line to flash it in the update script so it didn't flash the stock recovery.
This now leaves me with the loki flash problem above when trying to flash a custom recovery i could flash a different aboot.img but i don't want to break the current rom.
Any one else found a way to solve this problem?

need help
need help please!!
i have pretty much the same as your first problem, i installed the vodafone kitkat and the touch went crazy
and the custom recovery was deleted
and the lg support tool doesnt work for me
i dont know what to do.
sorry i forgot to mention that my phone is lg g2 d802 16 GB

Mustafa1 said:
need help please!!
i have pretty much the same as your first problem, i installed the vodafone kitkat and the touch went crazy
and the custom recovery was deleted
and the lg support tool doesnt work for me
i dont know what to do.
sorry i forgot to mention that my phone is lg g2 d802 16 GB
Click to expand...
Click to collapse
Have you tried running IO root to again root on your device? Also do you know much about linux, command line and android tools like ADB? Or do I need to explain the commands step by step?

twon23 said:
Have you tried running IO root to again root on your device? Also do you know much about linux, command line and android tools like ADB? Or do I need to explain the commands step by step?
Click to expand...
Click to collapse
i downloaded ioroot25 and extracted it and ran root.bat
Looking for device...
Make sure drivers are installed. Check Windows Device Manager.
Make sure proper USB Debugging mode is enabled.
Verizon users make sure ethernet mode is selected.
Did you check phone screen for Yes/No prompt?
(select checkbox to always remember then hit yes)
...sometimes you need to unplug the USB cable then re-plug.
Determining device model...
Rebooting into stock recovery...
When recovery loads, select: *apply update from adb* with power button...
then press Enter/Return on your keyboard.
Press any key to continue . . .
(here the phone restarts and LG logo appears with (secure booting error)message in the upper left corner, and when i press any key)
Reboot back into System after flash in recovery finishes.
Press any key to continue . . .
and when pressing any key the cmd closes and the phone stays on with black screen and the back light on
in the pc i get many windows about formating drives (from H to S)
and i dont know anything about linux or command line
would you explain it to me??

Ok so your phone not longer boots, correct? Do you know what build/version plus any other details of the rom you flashed? or even a link so i can have a look at the rom you have installed. Can you get into recovery mode and is it still a stock recovery image? also what is your phone d802? 16gb 32gb?

Mustafa1 said:
i downloaded ioroot25 and extracted it and ran root.bat
Looking for device...
Make sure drivers are installed. Check Windows Device Manager.
Make sure proper USB Debugging mode is enabled.
Verizon users make sure ethernet mode is selected.
Did you check phone screen for Yes/No prompt?
(select checkbox to always remember then hit yes)
...sometimes you need to unplug the USB cable then re-plug.
Determining device model...
Rebooting into stock recovery...
When recovery loads, select: *apply update from adb* with power button...
then press Enter/Return on your keyboard.
Press any key to continue . . .
(here the phone restarts and LG logo appears with (secure booting error)message in the upper left corner, and when i press any key)
Reboot back into System after flash in recovery finishes.
Press any key to continue . . .
and when pressing any key the cmd closes and the phone stays on with black screen and the back light on
in the pc i get many windows about formating drives (from H to S)
and i dont know anything about linux or command line
would you explain it to me??
Click to expand...
Click to collapse
If you're running root.bat as an admin, try executing it without admin privileges. Dunno why, but it seemed to work for me.

Mustafa1 said:
need help please!!
i have pretty much the same as your first problem, i installed the vodafone kitkat and the touch went crazy
and the custom recovery was deleted
and the lg support tool doesnt work for me
i dont know what to do.
sorry i forgot to mention that my phone is lg g2 d802 16 GB
Click to expand...
Click to collapse
Did you try to flash CWM recovery? http://forum.xda-developers.com/showthread.php?t=2582142 This thread has What you need to do .. After then you can nandroid backup after then wipe everything except EFS on twrp after that you can stock_kitkat.zip on the xda forum. Efter that restore data via twrp.
I think that It will be correct without deleting your current rom ...
---------- Post added at 06:18 PM ---------- Previous post was at 06:12 PM ----------
makgun said:
Did you try to flash CWM recovery? http://forum.xda-developers.com/showthread.php?t=2582142 This thread has What you need to do .. After then you can nandroid backup after then wipe everything except EFS on twrp after that you can stock_kitkat.zip on the xda forum. Efter that restore data via twrp.
I think that It will be correct without deleting your current rom ...
Click to expand...
Click to collapse
NOT CWM , it is TWRP
Are you from turkey?

twon23 said:
UPADATE: I have root but getting this error when trying to flash the recovery:
+] loki_flash v2.0
[-] Loki aboot version does not match device.
any ideas?
Ok so i found a different aboot img pushed to the phone and flashed that using dd
Code:
dd if=/data/local/tmp/about.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
this solved the problem above and a allowed me to flash cwm recovery. This then broke the installed rom so it wouldn't boot. now I had a custom recovery i flashed a EUR open 16gb stock zip this all went well and now i have a working phone What i should of done is remove the stock recovery.img from the zip and the line to flash it in the update script so it didn't flash the stock recovery.
This now leaves me with the loki flash problem above when trying to flash a custom recovery i could flash a different aboot.img but i don't want to break the current rom.
Any one else found a way to solve this problem?
Click to expand...
Click to collapse
Hi! I've recently flashed an updated stock ROM and have the same Touchscreen issue as yourself! Can you tell me the steps you have done to fix it? I'm using windows 8.1 to flash etc, and using a stock ROM I can't seem to get it to work again