Database Info

Tell me I've not bricked my Xoom!!!

I've just tried to root my wifi only Xoom using the 1 click method, but didn't see there was a tab for wifi only & a 3G tab. I went through the options using the 3G options.
Now my Xoom's stuck at the red Motorola screen & won't go any further.
Are there any threads to reverse my balls up?? I've had a look but can't see anything
Please tell me I've not bricked it?!?

tell me why you posted this in the wrong section

I could tell you that it's not bricked...but then I might be lying.

Moved to Q&A. This is not development.

You will need to adb and flash recovery then flash the rom again.
Sent from my PC36100 using Tapatalk

PaulG1488 said:
tell me why you posted this in the wrong section
Click to expand...
Click to collapse
Sorry, I didn't realise I'd put it in the wrong place.
Do you know if I've stuffed my Xoom?
thanks

alex2792 said:
You will need to adb and flash recovery then flash the rom again.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Do you know how I do this. I can't get adb working??

So the Xoom isn't recognizes when you type adb devices?
Sent from my PC36100 using Tapatalk

alex2792 said:
So the Xoom isn't recognizes when you type adb devices?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
It's ok alex, I've managed to get the stock boot & system images on it again. Just updating to 3.1 again now.

clemo71 said:
It's ok alex, I've managed to get the stock boot & system images on it again. Just updating to 3.1 again now.
Click to expand...
Click to collapse
how do you solved ? ive the same problem on my xoom...

davidebeatrice said:
how do you solved ? ive the same problem on my xoom...
Click to expand...
Click to collapse
clemo71 said:
It's ok alex, I've managed to get the stock boot & system images on it again. Just updating to 3.1 again now.
Click to expand...
Click to collapse
Please let us poor souls know how you did it!!! I am stuck with the same problem - the screen freezes with the Motorola logo and the tablet wouldn't boot up!

For those still having issues, try going into fastboot and flashing the stock images.
You can access fastboot by restarting your xoom (power and vol up) and then once the red M comes up, tap the volume down key around a second later. You have a decent window of opportunity to press the key. This should take you to the bootloader. Once in there, use the volume down key to enter fastboot.
From fastboot you can either flash a custom recovery then from the recover install the BRD 3.1 rooted update, or you can just use the fastboot flash command to flash each partition back to stock.
Good luck.

willverduzco said:
For those still having issues, try going into fastboot and flashing the stock images.
You can access fastboot by restarting your xoom (power and vol up) and then once the red M comes up, tap the volume down key around a second later. You have a decent window of opportunity to press the key. This should take you to the bootloader. Once in there, use the volume down key to enter fastboot.
From fastboot you can either flash a custom recovery then from the recover install the BRD 3.1 rooted update, or you can just use the fastboot flash command to flash each partition back to stock.
Good luck.
Click to expand...
Click to collapse
Thanks . I have now installed custom recovery (ClockworkMod 3.0.2.8) but where do I get the rooted or stock ROM from? I suppose it has to be in a *.zip format.

[Q] Bricked?

Dear, xda members
I have a problem because my Nexus S i9023 is bricked.
I flashed a bad ROM, I use it Clickie.
Now you think, but is not that stupid?
yes it is! Now my question, how can i fix this?
The Nexus S does not boot anymore, not even recovery, the screen just stays black
Still have questions? just ask.
greetz
bart

bartjuhhbartyow said:
Dear, xda members
I have a problem because my Nexus S i9023 is bricked.
I flashed a bad ROM, I use it Clickie.
Now you think, but is not that stupid?
yes it is! Now my question, how can i fix this?
The Nexus S does not boot anymore, not even recovery, the screen just stays black
Still have questions? just ask.
greetz
bart
Click to expand...
Click to collapse
Will your phone boot into bootloader mode? Take the battery out and put it back in and hold power and volume up at the same time..

bartjuhhbartyow said:
Dear, xda members
I have a problem because my Nexus S i9023 is bricked.
I flashed a bad ROM, I use it Clickie.
Now you think, but is not that stupid?
yes it is! Now my question, how can i fix this?
The Nexus S does not boot anymore, not even recovery, the screen just stays black
Still have questions? just ask.
greetz
bart
Click to expand...
Click to collapse
scott8281 said:
Will your phone boot into bootloader mode? Take the battery out and put it back in and hold power and volume up at the same time..
Click to expand...
Click to collapse
No, the screen stays black.

power button + volume up , if you are able to get into BOOTLOADER , then your phone is still alive...

qtwrk said:
power button + volume up , if you are able to get into BOOTLOADER , then your phone is still alive...
Click to expand...
Click to collapse
i did not work

bartjuhhbartyow said:
i did not work
Click to expand...
Click to collapse
Your best hope is to find the right stock firmware flashable through ODIN and flash it that way, as long as your phone can get into download mode. open ODIN and connect the phone with your phone off and press and let go of power while holding in volume up and down at the same time till you see download mode
---------- Post added at 09:30 AM ---------- Previous post was at 09:17 AM ----------
bartjuhhbartyow said:
i did not work
Click to expand...
Click to collapse
heres the link to the Odin files and firmware for your i9023...
http://forum.xda-developers.com/showthread.php?t=1009432

scott8281 said:
Your best hope is to find the right stock firmware flashable through ODIN and flash it that way, as long as your phone can get into download mode. open ODIN and connect the phone with your phone off and press and let go of power while holding in volume up and down at the same time till you see download mode
---------- Post added at 09:30 AM ---------- Previous post was at 09:17 AM ----------
heres the link to the Odin files and firmware for your i9023...
http://forum.xda-developers.com/showthread.php?t=1009432
Click to expand...
Click to collapse
let me try.

My bad, correction on download mode...take out battery, then put battery back in, hold both volume up and down at same time then plug in usb cable, no power button presses

Download mode only works for me if i first plug in the usb data cable. So plug in the acble, remove battery, put it back in and immediately press volume up+ volume down + power buttons.
Some people couldn't get the phone running after flashing the wrong rom.

mike.b93 said:
Download mode only works for me if i first plug in the usb data cable. So plug in the acble, remove battery, put it back in and immediately press volume up+ volume down + power buttons.
Some people couldn't get the phone running after flashing the wrong rom.
Click to expand...
Click to collapse
Neither does, any idea?

download mode and Odin doesn't work?
then looks like there's nothing we can do about it...

qtwrk said:
download mode and Odin doesn't work?
then looks like there's nothing we can do about it...
Click to expand...
Click to collapse
i can't get in Download mode.

bartjuhhbartyow said:
i can't get in Download mode.
Click to expand...
Click to collapse
Unfortunately i don't have any other ideas, as far as i know, ODIN is the only thing that can save it in that state. the only other thing i can think of is maybe the screen is just not working but the phone is on. if thats the case and you can find some stock system images you might be able to use fastboot to return it to stock. do you have the Android SDK and ADB installed on you computer? if so connect your device and opened a command prompt and type- adb devices & you should see a serial number pop up, it’s the serial number of your phone. This means you are all set. If you do NOT see a serial number, then you need to reinstall the drivers. But if the SDK and the drivers are installed and you still don't see your device listed then its probably bricked beyond repair.
If you do see your device listed you can flash it via fastboot by places the stock signed system images into your SDK tools folder and opening a command prompt to the tools folder and typing the following commands....
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
adb reboot

scott8281 said:
Unfortunately i don't have any other ideas, as far as i know, ODIN is the only thing that can save it in that state. the only other thing i can think of is maybe the screen is just not working but the phone is on. if thats the case and you can find some stock system images you might be able to use fastboot to return it to stock. do you have the Android SDK and ADB installed on you computer? if so connect your device and opened a command prompt and type- adb devices & you should see a serial number pop up, it’s the serial number of your phone. This means you are all set. If you do NOT see a serial number, then you need to reinstall the drivers. But if the SDK and the drivers are installed and you still don't see your device listed then its probably bricked beyond repair.
If you do see your device listed you can flash it via fastboot by places the stock signed system images into your SDK tools folder and opening a command prompt to the tools folder and typing the following commands....
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
adb reboot
Click to expand...
Click to collapse
My pc did't not adb device found...

bartjuhhbartyow said:
My pc did't not adb device found...
Click to expand...
Click to collapse
thats not a good sign, I'm sure they are people on here that have much more knowledge than myself but unfortunately I'm all out of ideas...best of luck my friend

looks pretty bad. Lets hope someone has a solution. If not you will have to send the device back for repair...

scott8281 said:
thats not a good sign, I'm sure they are people on here that have much more knowledge than myself but unfortunately I'm all out of ideas...best of luck my friend
Click to expand...
Click to collapse
mike.b93 said:
looks pretty bad. Lets hope someone has a solution. If not you will have to send the device back for repair...
Click to expand...
Click to collapse
I send him back, Comes good!
thank's for help al.

Your phones bootloader has been corrupted, you'll gonna need this device to restore it.
http://forum.xda-developers.com/showthread.php?t=1350134

asus HELP

HELP
my asus transformer tablet TF700T not start me and when I turn on fatboots goes straight to recovery mode and flash the recovery and not fully started and when I enter apx mode the screen goes black and the pc but nothing happens reconose urgent help is a very good tablet and do not want to lose

We will need quite a bit more information to be able to help.
What rom are your running?
What recovery?
What bootloader?
What did you do when this happened?
Did you use "Wipe Data" from the bootloader menu?
When the tablet is booted to recovery, do you have ADB access?
Sent from my K00C using Tapatalk

berndblb said:
We will need quite a bit more information to be able to help.
What rom are your running?
What recovery?
What bootloader?
What did you do when this happened?
Did you use "Wipe Data" from the bootloader menu?
When the tablet is booted to recovery, do you have ADB access?
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
hello not that bootloader used is the fastboot mode was upgraded by that updates the tablet occupying official firmware us sku and if ise a wipe data from fastboot and when I turned on me is in recovery and enpiesa to flash if I could mean and how to fix it and what I learned is that the adb is used from the fatboot of which I can not enter because it goes straight to recovery and flash not even fully into the

I guess you are using a translator for these posts?
Could you please try to seperate sentences?
It is very hard to read and understand what you are trying to say.
We need your bootloader version number. For example: 10.6.1.14.10 would be the latest. What do you have installed?
We also need the recovery version number. For example: TWRP 2.6.1 would be one possibility.
It sounds as if you installed an incompatible recovery and then used "Wipe Data" from the bootloader which is not a good idea.....
You are in a "forced reboot to recovery loop".
You do not need access to the bootloader for ADB to work in recovery. Try searching web pages in your language to get ADB drivers installed on your PC.
Sent from my K00C using Tapatalk
---------- Post added at 09:21 PM ---------- Previous post was at 09:15 PM ----------
Actually reading your post again it sounds as if you are on stock firmware.
Did you install a custom recovery?
If not, reboot the tablet. It will start the recovery.
Connect the tablet to a power source and leave it like that overnight.
It could be that the recovery is still trying to finish the "Wipe Data" command and you keep interrupting it.
Leave it alone for 6 hours.
Sent from my K00C using Tapatalk

berndblb said:
I guess you are using a translator for these posts?
Could you please try to seperate sentences?
It is very hard to read and understand what you are trying to say.
We need your bootloader version number. For example: 10.6.1.14.10 would be the latest. What do you have installed?
We also need the recovery version number. For example: TWRP 2.6.1 would be one possibility.
It sounds as if you installed an incompatible recovery and then used "Wipe Data" from the bootloader which is not a good idea.....
You are in a "forced reboot to recovery loop".
You do not need access to the bootloader for ADB to work in recovery. Try searching web pages in your language to get ADB drivers installed on your PC.
Sent from my K00C using Tapatalk
---------- Post added at 09:21 PM ---------- Previous post was at 09:15 PM ----------
Actually reading your post again it sounds as if you are on stock firmware.
Did you install a custom recovery?
If not, reboot the tablet. It will start the recovery.
Connect the tablet to a power source and leave it like that overnight.
It could be that the recovery is still trying to finish the "Wipe Data" command and you keep interrupting it.
Leave it alone for 6 hours.
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
firmware version is 10.6.1.14.10 and TWRP recovery is 2.7.0.0 and donot like making procedure adb if I could provide a link to the procedure by a thank ....... adb serious look at what step was I did the update and then did a wipe data and when you start the blinking recovey

Ok, I got the first part and your bootloader/recovery combination is fine.
Could you try different words to explain what you meant by this:
israelmena59 said:
adb serious look at what step was I did the update and then did a wipe data and when you start the blinking recovey
Click to expand...
Click to collapse

berndblb said:
Ok, I got the first part and your bootloader/recovery combination is fine.
Could you try different words to explain what you meant by this:
Click to expand...
Click to collapse
what happened is that when I did a wipe data update from fatboot
I did the upgrade and then wipe data from fastboot .....go into recovery and is blinking and then fail the recovery

israelmena59 said:
what happened is that when I did a wipe data update from fatboot
I did the upgrade and then wipe data from fastboot .....go into recovery and is blinking and then fail the recovery
Click to expand...
Click to collapse
I don't understand. What do you mean by "blinking recovery and then fail the recovery"??
Do you see an Android falling on his back with an open belly and exclamation mark?
That wold be the stock recovery, but you said you had TWRP 2.7 installed????
Sent from my K00C using Tapatalk

https://www.youtube.com/watch?v=UsDtdK8FsBY&feature=youtu.be
berndblb said:
I don't understand. What do you mean by "blinking recovery and then fail the recovery"??
Do you see an Android falling on his back with an open belly and exclamation mark?
That wold be the stock recovery, but you said you had TWRP 2.7 installed????
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
I send you a video so you can see what happens when you turn
https://www.youtube.com/watch?v=UsDtdK8FsBY&feature=youtu.be

israelmena59 said:
https://www.youtube.com/watch?v=UsDtdK8FsBY&feature=youtu.be
I send you a video so you can see what happens when you turn
https://www.youtube.com/watch?v=UsDtdK8FsBY&feature=youtu.be
Click to expand...
Click to collapse
I send you a video so you can see what happens when you turn
https://www.youtube.com/watch?v=UsDtdK8FsBY&feature=youtu.be

Yes, I think you have a forced reboot to recovery issue.
It's not clear from that video at which point you let go of the buttons, but I think you don't press them long enough.
We have to see if you can get into fastboot.
Keep holding Power and Volume Down past the first Asus screen and until you see a screen with 3 icons: RCK, Android and Wipe Data.
Confirm if you can get to that screen.
Sent from my K00C using Tapatalk

berndblb said:
Yes, I think you have a forced reboot to recovery issue.
It's not clear from that video at which point you let go of the buttons, but I think you don't press them long enough.
We have to see if you can get into fastboot.
Keep holding Power and Volume Down past the first Asus screen and until you see a screen with 3 icons: RCK, Android and Wipe Data.
Confirm if you can get to that screen.
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
I can not get to fastboot

israelmena59 said:
I can not get to fastboot
Click to expand...
Click to collapse
Connect your tablet via original USB cable to your PC.
Open Device Manager if you are on Windows.
Boot the tablet and let it loop on the TWRP logo.
Does it get recognized in Device Manager in any way? Any change in the list of connected devices?
If not, I'm afraid this is a brick.
Sorry

berndblb said:
Connect your tablet via original USB cable to your PC.
Open Device Manager if you are on Windows.
Boot the tablet and let it loop on the TWRP logo.
Does it get recognized in Device Manager in any way? Any change in the list of connected devices?
If not, I'm afraid this is a brick.
Sorry
Click to expand...
Click to collapse
appears a driver called "transformer"

israelmena59 said:
appears a driver called "transformer"
Click to expand...
Click to collapse
Ahhhh - a shimmer of hope! That is good news.
Does the driver show a yellow triangle with ! in it?
If not - even better.
Do you have ADB and/or fastboot installed on your PC?
Sent from my K00C using Tapatalk

berndblb said:
Ahhhh - a shimmer of hope! That is good news.
Does the driver show a yellow triangle with ! in it?
If not - even better.
Do you have ADB and/or fastboot installed on your PC?
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
if it appears with a yellow triangle
as I install adb or fastboot on pc

israelmena59 said:
if it appears with a yellow triangle
as I install adb or fastboot on pc
Click to expand...
Click to collapse
Sorry, I don't understand. Is that a yes or no on having adb/fastboot installed?

berndblb said:
Sorry, I don't understand. Is that a yes or no on having adb/fastboot installed?
Click to expand...
Click to collapse
no no I have installed adb / fastboot on pc
as I install adb or fastboot
but first let's focus on the problem and I can fix it

israelmena59 said:
no no I have installed adb / fastboot on pc
as I install adb or fastboot
but first let's focus on the problem and I can fix it
Click to expand...
Click to collapse
Don't understand your last sentence.
But if you have adb, open a command prompt from the folder where you're adb.exe is and issue this command:
Code:
adb devices
If that returns a string of numbers and letters, you have an adb connection to the tablet.
If it returns nothing you'll have to get the correct drivers.
But try this first and we'll see...

berndblb said:
Don't understand your last sentence.
But if you have adb, open a command prompt from the folder where you're adb.exe is and issue this command:
Code:
adb devices
If that returns a string of numbers and letters, you have an adb connection to the tablet.
If it returns nothing you'll have to get the correct drivers.
But try this first and we'll see...
Click to expand...
Click to collapse
a link to download adb

Bricked?

Hey everyone, so I usually know how to solve these situations, but this is different. I was trying to flash a rom so wiped everything from recovery and then realized that there is nothing on the sd card. I tried booting the phone but it is stuck at the google logo. Here is the problem: I am not able to get into bootloader/recovery mode and cant boot into the software. Does this mean the device is hard bricked?
Thannk You

ok so i am in recover/bootloader. when i am in twrp i can adb reboot to bootloader, but when i try to push a file it says device not found

No, it means u wiped everything and now need to sideload a new ROM, u will need a PC in order to do it, in twrp there is an advances section, in there is the adb sideload option, download the ROM and gapps to PC, and if u use windows use one of the toolkits to sideload the ROM u wanna flash, if Linux, use the terminal and type
adb sideload "name of ROM here".zip
Let it do its thing and ur all set, or u could just use the PC to dl the files then use a USB to transfers the ROM to the phone and flash it
PS, didn't see u can't get into recovery, have u tried long pressing power and volume, or whatever ur devices button combo is for recover?
Sent from my XT1526 using Tapatalk
---------- Post added at 12:37 PM ---------- Previous post was at 12:35 PM ----------
nabil alami said:
Hey everyone, so I usually know how to solve these situations, but this is different. I was trying to flash a rom so wiped everything from recovery and then realized that there is nothing on the sd card. I tried booting the phone but it is stuck at the google logo. Here is the problem: I am not able to get into bootloader/recovery mode and cant boot into the software. Does this mean the device is hard bricked?
Thannk You
Click to expand...
Click to collapse
Try holding down power, when it starts to reboot, switch to vol- and hold that till it boots to twrp, at worse u may need to use a PC and adb to boot to fastboot mode
Sent from my XT1526 using Tapatalk

Cant he just fastboot Marshmallow stock rom put the files back in and fastboot TWRP. Ive done that plenty of times and I hate it. I know you can sideboot a rom but havent for the life of me figured it out. But Bricked!!! Nope you havent, your good bro.

nabil alami said:
ok so i am in recover/bootloader. when i am in twrp i can adb reboot to bootloader, but when i try to push a file it says device not found
Click to expand...
Click to collapse
What kind of PC are u using, u dont have USB fastboot drivers working, that's ur problem, the PC can't see it in fastboot mode
Sent from my XT1526 using Tapatalk

I recommend starting from scratch by flashing a stock MM ROM, then TWRP, and then a custom ROM.

soupysoup said:
No, it means u wiped everything and now need to sideload a new ROM, u will need a PC in order to do it, in twrp there is an advances section, in there is the adb sideload option, download the ROM and gapps to PC, and if u use windows use one of the toolkits to sideload the ROM u wanna flash, if Linux, use the terminal and type
adb sideload "name of ROM here".zip
Let it do its thing and ur all set, or u could just use the PC to dl the files then use a USB to transfers the ROM to the phone and flash it
PS, didn't see u can't get into recovery, have u tried long pressing power and volume, or whatever ur devices button combo is for recover?
Sent from my XT1526 using Tapatalk
---------- Post added at 12:37 PM ---------- Previous post was at 12:35 PM ----------
Try holding down power, when it starts to reboot, switch to vol- and hold that till it boots to twrp, at worse u may need to use a PC and adb to boot to fastboot mode
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
when i try to sideload it says error deivce not found but when i want to flash anything it works probably will try flashing stock marshmallow

nabil alami said:
when i try to sideload it says error deivce not found but when i want to flash anything it works probably will try flashing stock marshmallow
Click to expand...
Click to collapse
That's what I would do at this point, what kind of PC are u using, it could be as simple as defining USB access, which I can help u with if your using Linux or Ubuntu
Sent from my XT1526 using Tapatalk

soupysoup said:
That's what I would do at this point, what kind of PC are u using, it could be as simple as defining USB access, which I can help u with if your using Linux or Ubuntu
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
update: flashed stock 6.0 going to try again to flash the ROM. flashbacks came back haha havent done this in almost a year.

marcusva79 said:
Cant he just fastboot Marshmallow stock rom put the files back in and fastboot TWRP. Ive done that plenty of times and I hate it. I know you can sideboot a rom but havent for the life of me figured it out. But Bricked!!! Nope you havent, your good bro.
Click to expand...
Click to collapse
oh ya I know I did it a ton of times too, but I wasnt able to get into bootloader mode. currently all is well and am flashing the rom

Stuck on a loop

So after trying to root my device I successfully unlocked my device and installed twrp and magisk through twrp but after trying to reboot into the system, it doesn't. Every time i try to reboot into the system, it just goes into a loading "G" and boots right back into recovery or twrp.

adrianherndez304 said:
So after trying to root my device I successfully unlocked my device and installed twrp and magisk through twrp but after trying to reboot into the system, it doesn't. Every time i try to reboot into the system, it just goes into a loading "G" and boots right back into recovery or twrp.
Click to expand...
Click to collapse
Flash the stock boot.img to both slots. That should get you running again. Then I'd boot twrp then install magisk. I wouldn't try to flash twrp but if you do make sure you flash that before magisk. Then reboot to twrp and flash magisk.
Sent from my [device_name] using XDA-Developers Legacy app

I'm literally in the same situation. Bootloader unlocked but only able to boot to TWRP. Tried running the "flash-all" from the Google stock image but it doesn't run. Now i'm lost and my new phone is not at its best.

Tarush13 said:
I'm literally in the same situation. Bootloader unlocked but only able to boot to TWRP. Tried running the "flash-all" from the Google stock image but it doesn't run. Now i'm lost and my new phone is not at its best.
Click to expand...
Click to collapse
Make sure you've updated your sdk platform tools.
Sent from my [device_name] using XDA-Developers Legacy app

Just re-downloaded from Google, still doesn't run. Also, not getting "no valid slot to boot" when I flash the boot.img file
---------- Post added at 09:59 PM ---------- Previous post was at 09:38 PM ----------
update: got the flash-all file to work, but now the touchscreen does not work when I am trying to set it up. There is no twrp and I cannot do anything except boot to fastboot or stare at the setup screen

Tarush13 said:
Just re-downloaded from Google, still doesn't run. Also, not getting "no valid slot to boot" when I flash the boot.img file
---------- Post added at 09:59 PM ---------- Previous post was at 09:38 PM ----------
update: got the flash-all file to work, but now the touchscreen does not work when I am trying to set it up. There is no twrp and I cannot do anything except boot to fastboot or stare at the setup screen
Click to expand...
Click to collapse
Are using the commands
fastboot flash boot_a boot.img
And
fastboot flash boot_b boot.img
There are two slots you need to flash the image to.
Sent from my [device_name] using XDA-Developers Legacy app

Hi, I got it to boot, but now I cannot use the touchscreen. Any ways to resolve this?
jd1639 said:
Are using the commands
fastboot flash boot_a boot.img
And
fastboot flash boot_b boot.img
There are two slots you need to flash the image to.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse

Tarush13 said:
Hi, I got it to boot, but now I cannot use the touchscreen. Any ways to resolve this?
Click to expand...
Click to collapse
Is the touch screen issue with twrp or when you boot the device itself? I know some people have had an issue with the touch screen not working in twrp.
Sent from my [device_name] using XDA-Developers Legacy app

Yes, it is when I boot the device. When I try to click on "start" to begin the initial device setup, nothing happens. None of the touch input is being received by the device.
jd1639 said:
Is the touch screen issue with twrp or when you boot the device itself? I know some people have had an issue with the touch screen not working in twrp.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse

Tarush13 said:
Yes, it is when I boot the device. When I try to click on "start" to begin the initial device setup, nothing happens. None of the touch input is being received by the device.
Click to expand...
Click to collapse
I'm not sure why it's doing that. But, if I was faced with that issue I'd first flash the system.img to both slots. And if that didn't work I'd try flashing the vendor.img.
Sent from my [device_name] using XDA-Developers Legacy app

flashed vendor.img and still cant use the touch screen? Touch input is definitely not being recorded. Any other ideas?
jd1639 said:
I'm not sure why it's doing that. But, if I was faced with that issue I'd first flash the system.img to both slots. And if that didn't work I'd try flashing the vendor.img.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
---------- Post added at 11:01 PM ---------- Previous post was at 10:54 PM ----------
Just to clarify, I flashed system to both slots and then vendor. Neither seemed to work.
Tarush13 said:
flashed vendor.img and still cant use the touch screen? Touch input is definitely not being recorded. Any other ideas?
Click to expand...
Click to collapse

Tarush13 said:
flashed vendor.img and still cant use the touch screen? Touch input is definitely not being recorded. Any other ideas?
---------- Post added at 11:01 PM ---------- Previous post was at 10:54 PM ----------
Just to clarify, I flashed system to both slots and then vendor. Neither seemed to work.
Click to expand...
Click to collapse
Have you tried a factory reset on the stock recovery?
Sent from my [device_name] using XDA-Developers Legacy app

I can't get to the stock recovery. When I tried to go there from fastboot, I got a "no command" error. Basically all I can do is go to fastboot mode and either reboot to the start screen where the touch input does not work or power off. I also don't see a recovery file in the source image I downloaded from google.
jd1639 said:
Have you tried a factory reset on the stock recovery?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse

Tarush13 said:
I can't get to the stock recovery. When I tried to go there from fastboot, I got a "no command" error. Basically all I can do is go to fastboot mode and either reboot to the start screen where the touch input does not work or power off. I also don't see a recovery file in the source image I downloaded from google.
Click to expand...
Click to collapse
The boot.img contains the stock recovery as well as the kernel. Flash that.
Sent from my [device_name] using XDA-Developers Legacy app

Tarush13 said:
I can't get to the stock recovery. When I tried to go there from fastboot, I got a "no command" error. Basically all I can do is go to fastboot mode and either reboot to the start screen where the touch input does not work or power off. I also don't see a recovery file in the source image I downloaded from google.
Click to expand...
Click to collapse
The no command thing is normal. When you see that screen, push and hold the power button and then, while still holding the power button, press volume up once. That will get you into recovery.

boot.img flashed, factory reset with stock recovery, still can't use the touch screen. This is beyond anything I've encountered in rooting. No clue why this is happening.