Ouya Bricked. Need HELP!! - Ouya Q&A, Help & Troubleshooting

So I managed to Brick my Ouya pretty bad I think.
I installed a version of Xposed Framework onto my Ouya and then rebooted it. After rebooting my Ouya it became stuck and would not boot. It is stuck on the screen with the little Ouya symbol.
I have tried the ALT + Prt sc + I and deleted all user files and cache partition.
The big problem I am having is I cannot connect my Ouya onto my computer in order to Flash the Original framework via ADB.
The Ouya drivers will not install on my computer.
So at this point I am not sure what to do. If anyone has any ideas that can help please let me know.
I'm not a developer, but can follow directions
Thanks.

Go here
http://forum.xda-developers.com/showthread.php?t=2385485
Download the zip file and install the driver it has in it.
If you're running windows 8 or 8.1 you have to disable driver signature enforcement or something like that.
Once you get the driver installed boot back into recovery and sideload the latest firmware from here
http://forum.xda-developers.com/showthread.php?t=2266629
Sent from my Nexus 5 using XDA Premium 4 mobile app

Thanks
TwitchyEye said:
Go here
http://forum.xda-developers.com/showthread.php?t=2385485
Download the zip file and install the driver it has in it.
If you're running windows 8 or 8.1 you have to disable driver signature enforcement or something like that.
Once you get the driver installed boot back into recovery and sideload the latest firmware from here
http://forum.xda-developers.com/showthread.php?t=2266629
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That did it! Thank you very much. Once I installed the drivers I was able to send the zip package.

Related

[Q] Nexus Help?

I was going ahead and about to flash my ROM (after doing so successfully at an earlier time), but after formatting everything, there was no sd card to format. I rebooted but now I'm stuck at bootscreen showing Google and the lock at the bottom. Can't get out of this. Anyone care to help?
Thanks.
I was able to get it into Fastboot mode but it isn't recognized by my computer....
Install google usb drivers
bk201doesntexist said:
Install google usb drivers
Click to expand...
Click to collapse
His phone isn't coming up in Device Manager. Wouldn't that not allow the drivers to install properly?
Try installing PDAnet - it's the most reliable way to get the right drivers.
Sent from my GT-P7500 using XDA App
What exactly did you format? And from where? Do you have a custom recovery installed? Can't you get into that?

!!tried everything can not factory restore!!!

ok have a gnex had it rooted rommed etc etc Ihave tried every single thing to revert this sum bich to stock for resale and nothing works any help??
PS used both pc and mac, odin, wugfresh, gnex toolkit etc etc
what exactly does not work? any error?
did u tried fasboot to restore the original google stock images?
for an example i just tried the toolkit again and wugfresh it sees my phone says all drivers are installed then i start everything it gets to bootloader mode and then just hangs there saying waiting for device?
AndreaCristiano said:
for an example i just tried the toolkit again and wugfresh it sees my phone says all drivers are installed then i start everything it gets to bootloader mode and then just hangs there saying waiting for device?
Click to expand...
Click to collapse
Try uninstalling the drivers and re install them. Are u in debug bode also?
Sent from my Galaxy Nexus using xda premium
Esteway.619 said:
Try uninstalling the drivers and re install them. Are u in debug bode also?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yea in debug did the uninstall reinstall of drivers
Did you restart the pc after installing the drivers?
Which drivers did you install and what OS is your pc running?
If you open the device manager on your pc and connect the phone in fastboot mode what exactly does it say in the Android tab (name of driver installed)?
Mark.
AndreaCristiano said:
Yea in debug did the uninstall reinstall of drivers
Click to expand...
Click to collapse
You have a driver issue.
Uninstall all GN device drivers.
Get the drivers from here.
Follow these steps to install the drivers.
Follow this to get back to stock.
efrant said:
You have a driver issue.
Uninstall all GN device drivers.
Get the drivers from here.
Follow these steps to install the drivers.
Follow this to get back to stock.
Click to expand...
Click to collapse
I will def give this a shot thanks

Waiting for device no matter what

I have installed and reinstalled the usb drivers like 4 times with reboots in between. I was about to root, but after root i cant do anything. The main thing i want to do is flash a custom rom. I have the gnex tool kit, it says waiting for device (option 6), and the most recent drivers are from that toolkit. I tried command pront, Fastboot reboot-bootloader, it says waiting for device. I tried adb flash recovery recovery.img it says waiting for device. I tried 2 different cables and all my usb ports on my computer.
Im at a loss. I can still transfer files from my computer to my device. My computer detects it just none of these commands... god i wish i had an sd card slot... lol
Edit:
I also tried putting it inot fastboot mode by pressing the power and wolume up / down keys. It goes to the screen and says start. All commands still say waiting for device.
I feel like this is a driver issue but idk why.... i have tried all drivers...........
i have a samsung galaxy nexus l515 verizon cdma.
Thanks!
Do u have USB debugging on?
Sent from my Galaxy Nexus using xda premium
Esteway.619 said:
Do u have USB debugging on?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yeah usb debugging is enabled. :crying:
Unplug your phone from computer install the drivers from Samsung's website. (Google USB drivers for galaxy nexus i515) reboot computer and try again. Maybe u should install android SDK with adb and do it manually instead of using a toolkit. Those cause problems.
Sent from my Galaxy Nexus using xda premium
Its a driver problem, for sure. OP, stop being lazy please, learn from this here, and after that, like Zepius says, put your big boys pants on and do it like this
Sent from my Nexus 10 using xda app-developers app
Ohhh the universal naked drivers. I never even thought of that. Actually i did. I have installed them same issue. I have fallowed the instructions in your first link prior to starting this thread. I appreciate the help but your attempt to call me lazy is wrong. Still unable to flash cwm or anything from the computer however i was able to flash cwrm touch today after buying the rom manager premium. Still doesnt explain why i cannot do it from my computer. Mind you i attempted this on my laptop (slackerware) and i did still have issues.
I think it is somthing with the port on my phone ror maybe somthing else. Regardless, im not lazy for i do know where google is and how to abuse all of her abilities. I know where the forum search button is also.
Drivers i have tried.
Naked nexus drivers
Windows native drivers
Slackerware mobile drivers
Samsung drivers
And what ever the gnex tool kit installs. No matter what i get waiting for device...
Sent from my GT-N8013 using xda app-developers app
5imp7y said:
I have installed and reinstalled the usb drivers like 4 times with reboots in between. I was about to root, but after root i cant do anything. The main thing i want to do is flash a custom rom. I have the gnex tool kit, it says waiting for device (option 6), and the most recent drivers are from that toolkit. I tried command pront, Fastboot reboot-bootloader, it says waiting for device. I tried adb flash recovery recovery.img it says waiting for device. I tried 2 different cables and all my usb ports on my computer.
Im at a loss. I can still transfer files from my computer to my device. My computer detects it just none of these commands... god i wish i had an sd card slot... lol
Edit:
I also tried putting it inot fastboot mode by pressing the power and wolume up / down keys. It goes to the screen and says start. All commands still say waiting for device.
I feel like this is a driver issue but idk why.... i have tried all drivers...........
i have a samsung galaxy nexus l515 verizon cdma.
Thanks!
Click to expand...
Click to collapse
Are you confusing adb with fastboot, or was "adb flash recovery recovery.img" a typo? Anyway, forget the toolkit. Get adb/fastboot binaries from the 101 & FAQ, and try:
1) booted into Android: adb devices
This should list your device with a number. If the list is empty, adb cannot interface with your gnex.
2) booted into the bootloader: fastboot devices
This should also list your device with a number. If the list is empty, fastboot cannot interface with your gnex.
Note that the adb and the fastboot interface are different. If you installed drivers and got adb running, this does not automatically make fastboot working. Boot into fastboot, connect and use device manager to scout for unknown devices. Update using naked driver if necessary.
5imp7y said:
im not lazy
And what ever the gnex tool kit installs. No matter what i get waiting for device...
Click to expand...
Click to collapse
you are lazy. you're relying on a toolkit.
please root your phone the manual way, or at least try fastboot alone so we actually know what the problem is.
Thanks yeah that was a typo. I have the adroid bianarys. Adb and fastboot. I was typing. Fastboot reboot bootloader to try and get gnex tools to see the device. No luck.
Sent from my GT-N8013 using XDA Premium HD app
I did root without the tool kit...? I was trying all possabilities to flash cwrm touch before i created a thread. I realize there was a typo in the op. I AM rooted but i had no recovery. Sorry for the confusion.
I rooted manually no problems. Problems arose post root. This can be marked as solved for buying the app fixed my issue. With recovery i can flash roms on the device. No need for a computer anymore. Thanks to those who didnt attack me and make me cry. To those who did well... thanks anyways....
Sent from my GT-N8013 using XDA Premium HD app
5imp7y said:
I did root without the tool kit...? I was trying all possabilities to flash cwrm touch before i created a thread. I realize there was a typo in the op. I AM rooted but i had no recovery. Sorry for the confusion.
I rooted manually no problems. Problems arose post root. This can be marked as solved for buying the app fixed my issue. With recovery i can flash roms on the device. No need for a computer anymore. Thanks to those who didnt attack me and make me cry. To those who did well... thanks anyways....
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
If you know how to root manually, then surely you must know how to boot or flash a custom recovery like twrp or cwm with fastboot.
Sent from my Nexus
Fastboot flash recovery "your recovery img here". Still said waiting for device....
Edit:
so many typos my bad it is hard to type on my phone or tablet with fat fingers.
Seriously though, to the 2 people taking time out of their day to be jerks, grow up im done with this thread.
Sent from my GT-N8013 using XDA Premium HD app
5imp7y said:
Fastboot flash recover your recovery img here. Still said waiting for device....
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
Again, driver issue. 'fastboot devices' should return your devices serial number. that command is the tell-tell sign that communication between fastboot host (PC/Mac) and client (device) see and recognise each other.
And please try to be flawless on the transcription of the exact commands used, to exclude the possibility of typos.
Sent from my Nexus
bk201doesntexist said:
Again, driver issue. 'fastboot devices' should return your devices serial number. that command is the tell-tell sign that communication between fastboot host and client see each other.
And please try to be flawless on the transcription of the exact commands used, to exclude the possibility of typos.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
BUT! in the gnex tool kit my serial number is displayed...?
5imp7y said:
BUT! in the gnex tool kit my serial number is displayed...?
Click to expand...
Click to collapse
Then it maybe not be a driver problem: you need to update platform-tools through android-sdk, which has fastboot/adb binaries. 4.2.2 requires it.
Sent from my Nexus
Let's try and be as friendly as possible when trying to help someone.
Thanks bk201doesntexist for trying to help.
bk201doesntexist said:
Then it maybe not be a driver problem: you need to update platform-tools through android-sdk, which has fastboot/adb binaries. 4.2.2 requires it.
Sent from my Nexus
Click to expand...
Click to collapse
if not a driver issue, it must be this.
install PDAnet on your device .. follow procedure of installation carefully ( should be installed on both pc and phone ) and when it was installed .when u enter your bootloader your phone will be recognize by your pc and wait for device will gone .
the method tested by me and took me one month two years ago to find .. on my g nexus first try to unlock .
PDAnet isntall drivers and everything you need to use adB commands ... if it helped give me thanks and let me know by pm .
PDA links
http://junefabrics.com/android/downloadold.php
1. Open device manager on your PC.
2. Right click on Android 1.0 with the yellow ! mark on it.
3. Choose update driver.
4. Choose browse my computer.
5. Choose Let me pick from a list.
6. Scroll down and find the Samsung driver with newest date. Should be the driver you downloaded above. (Possibly dated 11/25/2011 ).
7. It will give you a warning about installing the driver, just click yes.
driver: http://www.samsung.com/us/support/owners/product/GT-I9250TSGGEN#

Boot loop error, really stuck here.

Ok so my phone was going really slow on the PAC rom v22 so i decided i wanted to give the Trinity kernel a try, placed it on sd booted into cwm and installed it, from there on i am completely stuck in bootloop.
So i have trawled forums and alike to come up with an answer to this, most saying just enter recovery mode. My phone wont let me!
I am quite a noob when it comes to this although i have successfully done the process of putting custom roms on my device 3 times before but have never not been able to get into recovery mode. The only thing i can still do is enter CWM, i have tried installing Trinity a few times - same outcome, i tried installing the pac rom again, this bought back an error
Code:
Assert failed: getprop(" ro.product.device") == "LT26i || get prop("ro.build.Product") == "LT26i" getprop ("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi" E: error in /sdcard/*filename* (Status 7) installation aborted
i have tried the sony restore but not being able to enter recovery has kinda hindered this a useless tool for me right now.
I'd very much appreciate you time and help. Thanks
Flash stock rom via flashtool
Sent from my LT26i using xda app-developers app
electrash said:
Flash stock rom via flashtool
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
And how do i do this? i cant get into recovery and i can't get into the phone to put it on the SD? when i load flash tool it just tells me device is disconnected. if i enable sideload in CWM flash tool tells me...
16/014/2013 16:14:08 - ERROR - Drivers need to be installed for connected device.
16/014/2013 16:14:08 - ERROR - You can find them in the drivers folder of Flashtool.
but i have installed all the drivers, or atleast i thought i had, all the Xperia S drivers that came with the tool are installed, also flas and fast tools
Other than the Xperia s divers install the fastboot and flash mode divers too from the flashtool package.
Sent from my LT26i using xda premium
isht97 said:
Other than the Xperia s divers install the fastboot and flash mode divers too from the flashtool package.
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
Unfortunately, i have tried this (with a successful install) :-/
I should perhaps mention however when stuck in the bootloop towards the end the pc picks the phone up but in device manager its recognized as an Xperia S but its still unknown device with yellow triangle after installing the flash drivers.
http://androxyde.github.io/
Download, instal, in driver folder instal "gordon gate" (drivers) just to be sure, download STOCK rom and put it in "firmware folder" and other then that, follow on screen steps on flashtool, tutorial is on that site too.
you even have stock rom on that site
http://androxyde.github.io/LT26i_6.2.B.0.211_Customized_MEA.ftf.torrent
So you can get in to CWM. Did u try Factory reset & installing a Pre rooted / stock which is in zip format ?
i suggest you do a clean install of stock. Then repeat what ever you did before, and this time little more carefully.
electrash said:
http://androxyde.github.io/
Download, instal, in driver folder instal "gordon gate" (drivers) just to be sure, download STOCK rom and put it in "firmware folder" and other then that, follow on screen steps on flashtool, tutorial is on that site too.
you even have stock rom on that site
http://androxyde.github.io/LT26i_6.2.B.0.211_Customized_MEA.ftf.torrent
Click to expand...
Click to collapse
I appreciate your trying to help, thanks, but i cant get the PC to recognize the phone only when in CWM in ADB Sideboot,
Captain Droid said:
So you can get in to CWM. Did u try Factory reset & installing a Pre rooted / stock which is in zip format ?
i suggest you do a clean install of stock. Then repeat what ever you did before, and this time little more carefully.
Click to expand...
Click to collapse
Unfortunately i don't have a Stock zip on the phone only the PAC rom which fails to install with the error in top post, i have indeed tried a factory reset and tried reinstalling the PAC rom, with the same error.
I have a Stock rom on my pc, i just cant send it to the phone to install it :-/
There is some command to send frimware to the phone via adb.
But i never used it, try to search adb commands on google.
Sent from my LT26i using xda app-developers app
If you have cwm, then fron advance option mount usb storage
Sent from my GT-I9082 using Tapatalk 4 Beta
---------- Post added at 01:07 AM ---------- Previous post was at 01:06 AM ----------
If you have cwm, then fron advance option mount usb storage and send stock rom to your device
Sent from my GT-I9082 using Tapatalk 4 Beta
Sent from my GT-I9082 using Tapatalk 4 Beta
Razor! said:
If you have cwm, then fron advance option mount usb storage
Sent from my GT-I9082 using Tapatalk 4 Beta
Unfortunately when i do this, windows doesnt detect a device in the usb at all...
I'm really at a loose end now, i have set-up the ADB stuff, and well it doesn't even detect my phone... probably part to do with apparently having no drivers...
I have installed all the Xperia S drivers available with flash tool and also from the sony site, they install (with flash tool method) but i still get my Xperia device in device manager with the yellow triangle. It appears under other devices and actualy says its an Xperia S but there are no drivers there for it, been trying to do this all day now
Click to expand...
Click to collapse
Doondoons said:
Razor! said:
If you have cwm, then fron advance option mount usb storage
Sent from my GT-I9082 using Tapatalk 4 Beta
Unfortunately when i do this, windows doesnt detect a device in the usb at all...
I'm really at a loose end now, i have set-up the ADB stuff, and well it doesn't even detect my phone... probably part to do with apparently having no drivers...
I have installed all the Xperia S drivers available with flash tool and also from the sony site, they install (with flash tool method) but i still get my Xperia device in device manager with the yellow triangle. It appears under other devices and actualy says its an Xperia S but there are no drivers there for it, been trying to do this all day now
Click to expand...
Click to collapse
Try asking doomlord he might help you ..
Sent from my GT-I9082 using Tapatalk 2
Click to expand...
Click to collapse
Ok, so i'm getting somewhere, miraculously the drivers seem to have installed so i can now access ADB... where to go from here.
Currently i have nozomi_PAC_JB_4.2.2-v23.0.0-v2_Themed.zip downloaded and LT26i_6.2.B.0.200_WORLD.ftf (which apparently is the stock rom)
Doondoons said:
Ok, so i'm getting somewhere, miraculously the drivers seem to have installed so i can now access ADB... where to go from here.
Currently i have nozomi_PAC_JB_4.2.2-v23.0.0-v2_Themed.zip downloaded and LT26i_6.2.B.0.200_WORLD.ftf (which apparently is the stock rom)
Click to expand...
Click to collapse
In flashtool select the flashmode option, choose the firmware> plug in phone to pc in flashmode, flashtool should do the rest, phone should boot up properly after successful flashing.
Just an update, i have now tried to sideload the PAC rom and LT26i_DooMLoRD_leak-JB-197, both return the original error i showed in my first post.
And i still cant get into the flashmode (hold back button) so flash tool seems to be out of the question right now :-/
Thanks for all your suggestions guys, i have finally gotten back into the phone, i was able to install the DoomKernal Which then allowed me to reinstall PAC and now i'm all back up and running again

[Q] "Error: Device not found" in adb.

Hello friends,
I'm trying to install cyanogenmod and no matter what I do I consistently get the device not found error when I try to use "adb push cm-10.2.0-RC1-endeavoru.zip \sdcard\"
I know that in the cyanogenmod install guide it says it's probable that it's a driver issue. I've looked around for a good 2 hours trying to find what it might be, so I've tried reinstalling htc sync, I've tried uninstalling htc sync and using koush's universal adb driver, but nothing seems to work.
When using "adb devices" it doesn't give me the error, it just gives me "List of devices attached" which is empty. (I'm not sure if this is what it is supposed to do though)
Attached img of what I've been doing.
USB debugging is on. It's been automatically turned on whenever I connect it to my PC since I updated to 4.2.2 anyway.
I have no idea where to go from here. Any help would be appreciated.
Aireon said:
Hello friends,
I'm trying to install cyanogenmod and no matter what I do I consistently get the device not found error when I try to use "adb push cm-10.2.0-RC1-endeavoru.zip \sdcard\"
I know that in the cyanogenmod install guide it says it's probable that it's a driver issue. I've looked around for a good 2 hours trying to find what it might be, so I've tried reinstalling htc sync, I've tried uninstalling htc sync and using koush's universal adb driver, but nothing seems to work.
When using "adb devices" it doesn't give me the error, it just gives me "List of devices attached" which is empty. (I'm not sure if this is what it is supposed to do though)
Attached img of what I've been doing.
USB debugging is on. It's been automatically turned on whenever I connect it to my PC since I updated to 4.2.2 anyway.
I have no idea where to go from here. Any help would be appreciated.
Click to expand...
Click to collapse
mount the sdcard inside the recovery and copy the rom
Mr Hofs said:
mount the sdcard inside the recovery and copy the rom
Click to expand...
Click to collapse
Sorry, I'm completely new to this. Do you mean normal recovery from bootloader or a custom recovery that I should of done but completely skipped due to my ignorance? (I also haven't unlocked bootloader so I'm assuming that's a misstep as well?)
Because all I get when I do the normal recovery is a picture of a phone with a red triangle and "!" combo.
Thanks
Yeah to install a custom rom it's mandatory to unlock the bootloader and install a custom recovery. And what i can tell from your post it that you really are a novice on things. Some tips ?
1: never start without a full battery
2: learn fastboot + commands
3: always make a stock rom nandroid backup before starting flashing !
Read up in this forum. Under the stickys there are some nifty guides. If you have questions after that just ask here.
Mr Hofs said:
Yeah to install a custom rom it's mandatory to unlock the bootloader and install a custom recovery. And what i can tell from your post it that you really are a novice on things. Some tips ?
1: never start without a full battery
2: learn fastboot + commands
3: always make a stock rom nandroid backup before starting flashing !
Read up in this forum. Under the stickys there are some nifty guides. If you have questions after that just ask here.
Click to expand...
Click to collapse
Thanks for the tips!
After a while of toiling to try and unlock the boot loader manually and getting stuck at the load error for Unlock_code.bin, I found Hasoon2000's tool, so he is my god for now.
My query that I have is, Do I need a custom recovery like ClockWorkMod to create a nandroid back up? Because all I get when I try to go into recovery from the bootloader is this (img attached, not mine because I don't have another camera in the house but luckily I managed to find one on google img.)
I can't find anything saying that I do need a custom recovery, but then again it's not working when I try without one, so I'm not too sure where to go from here.
Thanks again
Please read carefully what i write, i know exactly what to do !
You need a custom recovery !
Sorry to be back again so soon but I'm stuck again, haha.
When I try to flash cwm I get "error: cannot load 'recovery.img'". When I try to use Hasoon2000's tool kit to do it for me it doesn't work either as it just says device not found and in the second command window it says that it can't load it's .img file either.
The recovery.img is in the same location as fastboot. My phone is in Fastboot in bootloader.
I'm typing "r:\Android\adt\sdk\platform-tools\fastboot flash recovery recovery.img". Trying to auto complete recovery.img using tab does nothing (if that might indicate some sort of problem).
The only thing I can think of is that the MTP drivers never install properly but I read on this forum that it shouldn't affect fastboot.
If you are on windows you must select camera as usb option
Sent from my GT-I8190 using xda app-developers app
---------- Post added at 02:25 AM ---------- Previous post was at 02:22 AM ----------
I mean windows 8
Sent from my GT-I8190 using xda app-developers app
robindebruin said:
If you are on windows you must select camera as usb option
Sent from my GT-I8190 using xda app-developers app
---------- Post added at 02:25 AM ---------- Previous post was at 02:22 AM ----------
I mean windows 8
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Ah, I probably should of said it earlier, sorry. I'm using windows 7.
And did you install java jdk and driver
Sent from my GT-I8190 using xda app-developers app
robindebruin said:
And did you install java jdk and driver
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
If javaj jdk is just normal java then yes. In programs and features it's called Java 7 Update 45?
Do you mean the phone drivers on my PC?
Edit: Noticed jdk was the dev kit. Downloaded and installed. Will try again.
Edit2: Still not working, same errors.
Jre is normal java jdk is the development kit
and yes that drivers
Sent from my GT-I8190 using xda app-developers app
robindebruin said:
Jre is normal java jdk is the development kit
and yes that drivers
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
I just updated the phone drivers (without HTC sync) from http://forum.xda-developers.com/showthread.php?t=2376761 to 4.2.0.001 from the 4.0 version I had that HTC sync had installed previously for some reason.
Shows up in fastboot devices now. Still doesn't show up in adb devices. Still getting the can't load recovery.img error.
Would it be worth it to try doing it on another computer?
Yes and plz post results
Sent from my GT-I8190 using xda app-developers app
robindebruin said:
Yes and plz post results
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Ok so I still couldn't do it manually on the other computer. Got the same errors as with the first. I tried flashing with Hasoon2000's tool again and noticed that it was trying to flash CWM.img while the recovery for it was actually called recovery.img. Renamed it to CWM.img and it flashed perfectly.
I assume it would of done the same on the original PC I tried it on.
No idea why it wouldn't work when I tried it manually, but yolo. Hasoon2000 is love. Hasoon2000 is life.
Holy hell Hasoon2000 has saved me again.
I flashed the kernal by accident and it got stuck in boot. So i just sideloaded the rom in H2K's tool and everything turned up Milhouse.
Yay congrats
Sent from my GT-I8190 using xda app-developers app
And if it says can not load recovery that means it's named differently or that it's not placed in the same dir of the fastboot files. A common error is that people hide filename extensions in windows. Then rename the recovery to recovery.img.img and then it won't be found by fastboot
Mr Hofs said:
And if it says can not load recovery that means it's named differently or that it's not placed in the same dir of the fastboot files. A common error is that people hide filename extensions in windows. Then rename the recovery to recovery.img.img and then it won't be found by fastboot
Click to expand...
Click to collapse
Hmmm, I'm not sure what it would of been as a tried flashing recovery.img.img as well. But everything worked out well in the end .
Thank you both the help.
Glad to hear that it worked
Sent from my GT-I8190 using xda app-developers app

Categories

Resources