stuck after wiping - Desire HD Q&A, Help & Troubleshooting

i used ext4 recovery to go to screen to flash a rom and it freeezed after I wiped partition except sd card ( i'm presuming my sd card is still ok)
so i tried to connect my phone to adb on my computer but was unable to flash the rom via fastboot. Is it possible to do so or what am i supposed to do ? am i supposed to place the ROM zip file in the android platform tools folder or push it to my SD card ( I am not too sure what command to input too ) ?

whateheck said:
i used ext4 recovery to go to screen to flash a rom and it freeezed after I wiped partition except sd card ( i'm presuming my sd card is still ok)
so i tried to connect my phone to adb on my computer but was unable to flash the rom via fastboot. Is it possible to do so or what am i supposed to do ? am i supposed to place the ROM zip file in the android platform tools folder or push it to my SD card ( I am not too sure what command to input too ) ?
Click to expand...
Click to collapse
boot in recovery again and reflash the rom. ADB only works with booted phones and custom roms are not possible to be flashed from fastboot anyway but RUU's are.

Sorry I forgot to add that my volume is spoilt so that's why I was trying to use the adb. Is there anyway I can try to flash anything or I have to try the ruu (where can I get it and place it in and the command to type too) ?thanks

i used a card reader and checked my SD card and there's a clockworkmod folder with the files .android_secure.vfat (357,525 KB RAR) ,cache.ext4 ( 5KB RAR) , data.ext4 ( 489,783 RAR) , system.ext4 ( 424,852 KB RAR) , boot.img ( 4,096 KB IMG file) , fsinfo (1 KB file), nandroid.md5 (1 KB MD5 file) , recovery.img ( 8,701KB IMG file ) . anything i can do with them too ? I pulled my batt out as I was afraid it might run down quickly with the boot menu on all day too - not sure if I can get back to it later

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I used 4ext touch recovery to wipe all partitions except sd card and it freezed. when i power on , it only shows HTC logo on the bright white screen , and I was able to get to the image above via adb on my PC , not too sure if I am able to do anything next ? my volume knocker is spoilt so I cannot do use that to operate using just the phone itself. anyone has an idea ? thanks

whateheck said:
So I used 4ext touch recovery to wipe all partitions except sd card and it freezed. when i power on , it only shows HTC logo on the bright white screen , and I was able to get to the image above via adb on my PC , not too sure if I am able to do anything next ? my volume knocker is spoilt so I cannot do use that to operate using just the phone itself. anyone has an idea ? thanks
Click to expand...
Click to collapse
Try adb reboot recovery

hdorius said:
Try adb reboot recovery
Click to expand...
Click to collapse
So I just need to type this line ? What should i be expecting after that? Just trying to get an idea,thanks!

whateheck said:
So I just need to type this line ? What should i be expecting after that? Just trying to get an idea,thanks!
Click to expand...
Click to collapse
Connect your phone to your computer, make sure ADB and the drivers are installed, and type it from the computer command line. There are several ADB guides online; Ace Think Tank thread in General forums has one linked.

yup, comp suddenly said found new hardware and asked for drivers , so i assumed it meant it wanted the android 1.0 and got the android-usb-driver and included in the path folder for it to search to install.
after I got to the boot menu, i keyed adb reboot recovery but it says no device found now - have I done anything wrong ?

whateheck said:
yup, comp suddenly said found new hardware and asked for drivers , so i assumed it meant it wanted the android 1.0 and got the android-usb-driver and included in the path folder for it to search to install.
after I got to the boot menu, i keyed adb reboot recovery but it says no device found now - have I done anything wrong ?
Click to expand...
Click to collapse
You need to install drivers with the device unplugged. Install them, then plug the phone and let the PC finish the process. Once it says that the device is ready to be used, you go ahead.
If you are going to install them again, uninstall what it is already in your pc from control panel and then do the above. :good:

oh,,,, I thought it suddenly needed something when plugged and prompted to install some drivers so I did ....
erm, I'm not sure where the driver is now - the only possible options i have under my control panel is 'Add hardware' or 'add/remove program' , I suppose ? windows xp

whateheck said:
oh,,,, I thought it suddenly needed something when plugged and prompted to install some drivers so I did ....
erm, I'm not sure where the driver is now - the only possible options i have under my control panel is 'Add hardware' or 'add/remove program' , I suppose ? windows xp
Click to expand...
Click to collapse
Do you mind if I give a look over teamviewer?

really big thanks to glevitan for able to run my phone again I really appreciate it
but getting back the screen freezing/ ghosting issue I have earlier so not too sure if it's the spoilt volume knocker an issue or digitizer

Related

[HOWTO] If you flashed the original RUU_Hero_HTC_WWE_2.73.* and got the new hboot

You will have noticed you can't 'fastboot boot' the recovery image again for rooting or using the new recovery image.
However:
You can use flashrec to flash the patched recovery, from where you can do all the usual stuff (and even put the old hboot back on if you want!)
Notice:
flashrec is using an exploit that isn't patched yet in the current kernel used by HTC, however if/when HTC patches this, flashrec will stop working.
So for now it's ok but a next version might have patched this, so keep this in mind !
Thanks for the original headsup by Magnus and Modaco, adapted from here
Quick Howto:
1. On your phone, goto Settings, Applications, and make sure Unknown source is checked ON.
2. On your phone, goto Settings, SD card and phone storage, and click Unmount SD card.
3. Then click Format SD card (it should automatically remount after this).
4. Plug the phone into the compuer via USB, then pull down the notification bar and click on the SD card notification. Then click mount.
5. Download this APK and recovery image and save it to your computer:
flashrec-20090815.apk
Cyanogen’s / Modaco Hero Recovery Image
Update: updated flashrec here
6. Extract the cm-hero-recovery.img out of the MoDaCoPatchedRecovery-1.0.zip and put it somewhere on your computer.
7. Save both the cm-hero-recovery.img and the flashrec-20090815.apk to your computer, then copy them both to your SD card
(do NOT put them inside any folders on the SD card, just put them in the root of the SD card itself).
8. Unplug the phone from the computer once they are downloaded to the SD card.
9. Goto the Market and download Linda File Manager or any file manager program if you do not already have one.
10. Open the file manager and goto SDCard and then find the flashrec-20090815.apk file and click on it.
If asked, tell it to use Package Installer to open it. It should automatically install the apk.
11. Open the FlashRec program and click on Backup Recovery Image and wait for it to finish.
12. Once done, click on the empty text box in the FlashRec program and type:
sdcard/cm-hero-recovery.img
Then click on the Flash Custom Recovery Image button and wait for it to finish.
13. Turn off the phone and turn it on into Recovery mode by holding down Home and Power to turn it on
(keep holding until the recovery screen comes up has a bunch of text on a black background).
As long as that screen comes up, you have done it correctly and can now go and load other ROM/hboot/whatever.
Excellent, worked perfectly! Thanks!
I flashed the new official update from HTC, but i do got a nandroid from before when my phone was rooted, do you know if restoring that will make any changes to the hboot? And will i get root again? Or is this method that you posted over, the only way so far?
Root
I did all this with the orginal 2.73 update and booted in to the recovery mode (worked fine..) but i still dont hav root
I tried the other method from theunlockr.com to but still no root..
I followed this excellent tutorial, then I just ran the root tutorial again. Worked flawlessly.
Worked fine - thx m8
Is it possible to make this without a sd card?
Because my phone doesn't detect my sd card. Now i have the problem that i can't do anything on my phone because i can't get into recovery mode...
Anyone who knowes a solution???
Thanks in advance.
works perfectly, many thanks !
I get this "downloading 'boot.img'... FAILED (remote: not allow)" when i type "fastboot boot cm-hero-recovery.img" any one know what is wrong ?
you have uploaded the recovery image by that apk, be sure to boot your phone holding POWER+HOME NOT power+back, then you can continue to root your phone, hope i could help you
Ok, But what to do when i boot up with power+home ?
then you have to root your phone again like it is described in
http://forum.xda-developers.com/showpost.php?p=4257045&postcount=38
i would recommend you to make a backup with nandroid (just select it and push the track ball) and then continiue with
6 ROOTING - MODIFYING THE CODE TO GET ROOT ACCESSS
Ofcourse! stupid me so easy.. Thank you
after i update the rom to the new one 2.73
i can't root my hero
i get this error msg "FAILED (remote: not allow)"
i need to install fonts and i can't
anyone can help me
Wait, I gotta format the SD card?
Why would this be needed? Isnt it enough to just do the rest???
walter_yaron said:
after i update the rom to the new one 2.73
i can't root my hero
i get this error msg "FAILED (remote: not allow)"
i need to install fonts and i can't
anyone can help me
Click to expand...
Click to collapse
excuse me,... but did you read and fully understand the first article from this thread?!
kingkeld said:
Wait, I gotta format the SD card?
Why would this be needed? Isnt it enough to just do the rest???
Click to expand...
Click to collapse
i also thought of that, i think it does not matter but i have a lot of 2gb micro sdhc cards so i just followed as described
I'd like to update with RUU, but failed with this error. Kindly advice
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Geochelone said:
I'd like to update with RUU, but failed with this error. Kindly advice
Click to expand...
Click to collapse
do you have a branded phone?
When I followed the instructions, everything worked, until I have to restart with Home button pressed.
I see the HERO word on my screen, but nothing else happens.
Has someone some suggestions?
I followed the instructions already twice.
-------------------------------------------------------------
SOLVED:
In the first page there is a link to flashrec-20090815.apk. That did not work for me.
I used http://code.google.com/p/flashrec/ to download the file.
Thank you for your interest in reading my post.

HTC Stock Rom Recovery Android 2.3.3 & 2.3.5

Hey guys,
for all those who want to have the orginal stock rom back here's a
recovery by me. It's Android 2.3.3 and 2.3.5. Flashable through cwm 5.
Android 2.3.3 Version: here
Android 2.3.5 Version: here
OC Kernel (806 MHz): here <= ONLY 2.3.5
You will find the downloads if you click "To Downloads" and then choose the one you want
Click the banner if you want to support me !
For me it works very stable and smoothly. If it doesn't boot and redirects you to the recovery: wipe data, cache and dalvik again and retry.
Questions please here in this thread and NOT per pn!
Best regards,
Maxi_king_223
http://lectrasxt16.ohost.de/
Not working for me "E:invalid command argument" tried several times with wiping all but just boots into recovery.
Ok,
First time i got the same problem.
try to flash an other rom with cwm and then wipe data, cache and dalvik.
after this flash the stock rom agian.
If this fails too, post the cmd-output please.
ps. Which version did you used?
oK, tried again and got the same, put a memory card in the phone and booted the phone up and it worked. Many thanks, .
well it just seems to be stuck at the waiting for device dialog for almost an hour now with the 2.3.3 version...........followed all the steps to the letter and am running a wildfire s gsm model with a sim card........waiting for some help.........dling the 2.3.5 now.....will try if it helps....................
and now the 2.3.5 also doesnt seem to work at all........it also gets stuck at the waiting for device dialog......any help????????????
pandollar said:
oK, tried again and got the same, put a memory card in the phone and booted the phone up and it worked. Many thanks, .
Click to expand...
Click to collapse
that's new to me with the memory card. well, thanks for your feedback
kill3rlook5 said:
well it just seems to be stuck at the waiting for device dialog for almost an hour now with the 2.3.3 version...........followed all the steps to the letter and am running a wildfire s gsm model with a sim card........waiting for some help.........dling the 2.3.5 now.....will try if it helps....................
and now the 2.3.5 also doesnt seem to work at all........it also gets stuck at the waiting for device dialog......any help????????????
Click to expand...
Click to collapse
did you install HTC sync with the htc drivers for your phone ?
when not --> try it http://dl4.htc.com/managed-assets/support/software/htc-sync/setup_3.0.5617.exe
Maxi_king_223 said:
that's new to me with the memory card. well, thanks for your feedback
Click to expand...
Click to collapse
Me to, but as long as it worked I'm happy, cheers
For info I used the 2.3.5 rom
Maxi_king_223 said:
did you install HTC sync with the htc drivers for your phone ?
when not --> try it http://dl4.htc.com/managed-assets/support/software/htc-sync/setup_3.0.5617.exe
Click to expand...
Click to collapse
thank u very much maxi for your reply.......but i have HTC sync installed on my system and i already have the htc drivers installed.......newasy for simplicity and for removing the doubts if any i reinstalled sync and then i tried to run the batch file provided by you......i evn tried flashing my phone from the command line but still everytime the console gets stuck at waiting for phone......aint able to understand it...........hope i get some help.......
kill3rlook5 said:
thank u very much maxi for your reply.......but i have HTC sync installed on my system and i already have the htc drivers installed.......newasy for simplicity and for removing the doubts if any i reinstalled sync and then i tried to run the batch file provided by you......i evn tried flashing my phone from the command line but still everytime the console gets stuck at waiting for phone......aint able to understand it...........hope i get some help.......
Click to expand...
Click to collapse
hmm.
could you please do the fowwowing ?
1. open command window in the directory of the recovery tool.
2. run "fastboot devices" and check if your device is listed.
3. if not, get the newtest fastboot .exe from here --> android sdk
it should be in xxx\android-sdk-windows\platform-tools. also copy adb.exe and AdbWinApi.dll and AdbWinApiUsb.dll into the recovery folder.
4. try again and run "fastboot devices".
5. if your device is listed : start flashing.
Maxi_king_223 said:
hmm.
could you please do the fowwowing ?
1. open command window in the directory of the recovery tool.
2. run "fastboot devices" and check if your device is listed.
3. if not, get the newtest fastboot .exe from here --> android sdk
it should be in xxx\android-sdk-windows\platform-tools. also copy adb.exe and AdbWinApi.dll and AdbWinApiUsb.dll into the recovery folder.
4. try again and run "fastboot devices".
5. if your device is listed : start flashing.
Click to expand...
Click to collapse
maxi man....u know wat u are the man........i downloaded the sdk and then i dint find anything in the platform tools.....i ran the sdk manager and installed the platform tools......i got all the updated files that i needed and then all i did was copied the same files u asked me to copy to the directory i had created from ur rom..........and then the flashing went on smoothly without any hiccups.....then followed ur steps.....powered down and restarted the phone....and lo......i got a bootloop....then remembered that i hadnt wiped the caches....and data.....wiped them and then redid the whole thing.....the thing booted and i get stock rom back.........wifi is giving me some problem....but i will let u know
BTW I sincerely clicked the thanks button ROFL
My wildfire s is back......and I am loving it....thanks to u maxi
Sent from my HTC Wildfire S A510e using xda premium
Well i see alot of people get problems, i would say that you will need to install an adb driver onto your computer to fix part of the problem and to make sure you have a memory card inserted with at least 15mb of free space inside of it.
CLICK THANKS IF THIS HELPED YOU
NOT HARD TO CLICK THANKS
It worked perfectly on mine, thanx a lot!!!
I'm glad i helped you
EDIT: Ah nearly i forgot: here's my email:Maxi_king_223 [at] live [dot] de
Please write only when you really do not get an answer from me here
I have a very important question here , previously i "played" with the /dev stuff , mostly the misc partition , and now i am having a partial usb brick , mostly caused by a malfunctioned misc partition , so will this fix anything ?? BTW , I tried flashing the ORIGINAL RUU from htc and nothing changed .... so will this work for me ?
seaskyways said:
I have a very important question here , previously i "played" with the /dev stuff , mostly the misc partition , and now i am having a partial usb brick , mostly caused by a malfunctioned misc partition , so will this fix anything ?? BTW , I tried flashing the ORIGINAL RUU from htc and nothing changed .... so will this work for me ?
Click to expand...
Click to collapse
did you change the partition? maybe i'm not sure.
Maxi_king_223 said:
Hey guys,
for all those who want to have the orginal stock rom back here's a
recovery by me. It's Android 2.3.3 and 2.3.5.
Make sure you wiped your data your cache and your dalvik before flashing with this tool !!
After flashing just power off your phone from fastboot menu.
Do not reboot! Just power off and power on again!
Android 2.3.3 Version: here
Android 2.3.5 Version: here
Tutorial:
1.Remove and reinsert the battery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2.Press Volume Down and Power to start the device into Bootloader mode.
3.Use the Volume buttons to select up or down. Highlight Fastboot and press the Power button.
4. Connect the device to the computer via a usb cable.
5. Unzip the archive onto your desktop and run flash_stock_rom.bat.
6. Press "j" and confirm your choice with enter.
7. Ignore the fails and wait until the message "Stock Rom geflasht." appears.
8. Unplug your phone from usb.
9. Highlight "Power off" with volume- and volume- and press the power button.
10. Power on your phone and enjoy the orginal Stock rom!
For me it works very stable and smoothly. If it doesn't boot and redirects you to the recovery: wipe data, cache and dalvik again and retry.
Questions please here in this thread and NOT per pn!
Best regards,
Maxi_king_223
Click to expand...
Click to collapse
Hi
May I edit the .bat file and translate the tool to english?
deanokidd95 said:
Hi
May I edit the .bat file and translate the tool to english?
Click to expand...
Click to collapse
if you want to do so
please post the translated file here after finishing.
regards
maxi
I`m getting a E:invalid command argument error every time, already tried with or withoit sd card, and flashing a rom with cwm recovery, using a 2.3.5 version. Help please!

WTF!!!!!!!

I recently sold my Wildfire S, and because of that I wanted to wipe the phone out. So, I went to install a ROM, the same m1 mix I have been using for months, and I tried to install it again.
> Stays at HTC white screen and will forever if I let it.
> Tried installing another ROM to see if it was just corrupt. No go.
> I can get to the HBoot screen and move around but I can't get past HTC screen after installation is complete!!!
> Tried installing CWM again to see if it was an issue there, but now I get a "Install Fail" message because the ID is incorrect (I assume it has to do with the golf card)
I just want the damn thing to boot and work, I don't even care if it goes back to stock, I just need it to work. What are my options here? Any help would be great. An important factor I should mention is that I am on a Mac, and only have access to a Mac.
Thanks!
I have an evo so I'm not sure how things work on your phone but have you tried an ruu? It should help
Sent from my PC36100 using xda premium
Are you wiping data/factory reset, cache and dalvik? You need to do this in cwm
Yes, I always wipe both system and cache, as well as dalvik.
I will try a RUU, see where that gets me. Thanks. And if anyone else has suggestions please let me know!
I think you can only run an ruu under windows.
I could be wrong though.
I can't just have the ZIP on my SD Card and install it from there?
You can but I think it will give you the same issue.
Try it though, its worth a shot
I just want the easiest way to get this back to functioning. I don't need any of the data on the phone or the SD card. I just wanted it to work. Period.
Easiest and safest is ruu
Do you not know anyone that will let you run it on their windows machine?
It would take 10 mins topps and is almost guaranteed to get you back up and running.
By the way are you a GSM or cdma user?
Edit: is that rom overclocked by default? The reason I ask is a lot of people have been having issues like you when installing Rom's that are pre overclocked.
Check if there's a default clock speed kernel on his op
GSM Virgin Mobile Canada.
nootered said:
GSM Virgin Mobile Canada.
Click to expand...
Click to collapse
Also your bootloader must be locked in order for the ruu to work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am unlocked currently. I have been running it just fine with the m1xd ROM, all the stats are in my sig.
I just want this facking thing to function!!!!!!!!!!!! :O
nootered said:
I recently sold my Wildfire S, and because of that I wanted to wipe the phone out. So, I went to install a ROM, the same m1 mix I have been using for months, and I tried to install it again.
> Stays at HTC white screen and will forever if I let it.
> Tried installing another ROM to see if it was just corrupt. No go.
> I can get to the HBoot screen and move around but I can't get past HTC screen after installation is complete!!!
> Tried installing CWM again to see if it was an issue there, but now I get a "Install Fail" message because the ID is incorrect (I assume it has to do with the golf card)
I just want the damn thing to boot and work, I don't even care if it goes back to stock, I just need it to work. What are my options here? Any help would be great. An important factor I should mention is that I am on a Mac, and only have access to a Mac.
Thanks!
Click to expand...
Click to collapse
Hello ,
this will return your phone to stock state (means that you will no longer have CWM recovery and you will have to install it again after this. If unlocked with XTC Clip YOU WILL STAY S-OFF ,I didn`t tried it with device unlocked via HTC Dev)
STEP BY STEP instructions what you should do :
1. go to http://forum.xda-developers.com/showthread.php?t=1432474
2. download http://www.mediafire.com/?ksa9k8dmxexdkdo
3. follow the instructions from 1
4. click thanks button
credits to Gig11gs & Ping192
P.S. I`m not responsible if you do any damage to your device.
if you have a backup or something then flash it through hboot
or if you have a extracted zip file from an ruu (rom.zip file in c:/temp when you run the installer) then extract it to desktop and flash it through hboot(if the file name of system is system.yaffs2.img then change it to system.img , you require only two files boot.img and system.img so no need to extract everything just extract these two)
the codes for both are
(locate the adb files first.)
in my case i have copied fastboot file from tools folder of sdk on desktop and also adb and adbbin.dll on desktop.. if you also copy these files on desktop then run the following exact commands when you are on bootloader the fastboot option will be highligted press power buton to select it .. when you in fastboot menu connect phone to pc and then write these command in dos prompt (go to start menu , run then write cmd and press enter you will have a dos prompt open)
Code:
cd desktop
fastboot flash boot boot.img
fastboot flash system system.img
when done go to recovery and now do all format data , clear chache and dalvik chace your phone will be un rooted total stock
It worked for me.. credits to EOgan
Or you can go to this tutorial that will downgrade everything even hboot and radio at http://forum.xda-developers.com/showthread.php?t=1540952 and remember o thank me
Just a thought but have you wiped everything before flashing the ROM? I've had a weird experience once with pretty much the same issue (stuck on splash screen). Wiping everything (system, data, cache, boot AND SD Card) seemed to have resolved the issue. If you're using an already partitioned card, I'd recommend powering off after CWM flashing, unmounting the SD and then turning it on.
This should work actually (don't see a reason not to). Also, if you've modified the ROM.zip file in any way after downloading it, I'd advise flashing one which is freshly downloaded rather (would eliminate any user tweaks causing the issue).
PS. I've attached a flashable superwipe script which you can run before flashing the ROM. Let me know how it worked out for you.

Formated my SD Card now I am stuck!

So heres the deal, I formated my SD card, so now, there is nothing on the ouya... I still have recovery, but I don't see the big exclamation point and the ouya lettering, wich I trully belive that my litle box is bricked.
My ouya doesn't appear in device manager, nor does it work with adb...
My question is, is there a way to install OTA and/or Custom Roms via OTG?
Thank you. and please help me!
New developments...
My device manager detects an unknown device, however, when I try to install the drivers it won't let me, says that the device could harm my PC.
Il_Padrino said:
So heres the deal, I formated my SD card, so now, there is nothing on the ouya... I still have recovery, but I don't see the big exclamation point and the ouya lettering, wich I trully belive that my litle box is bricked.
My ouya doesn't appear in device manager, nor does it work with adb...
My question is, is there a way to install OTA and/or Custom Roms via OTG?
Thank you. and please help me!
Click to expand...
Click to collapse
Hi,
In al my desperation i also formatted my SD. When the Ouya booted i had nothing more than a black screen.
I rebooted into recovery .. sideloaded the latest OTA and this worked for me (after that i installed the stock plus rom)
But my point of view is "when the device is still being detected by a computer, its possible to recover )
Greetz
I did the same, to be clear: i did wipe data and dalvik to flash a ROM and when y tried to flash i got an error. I dont know how but i missclicked on a keyboard test and dont know how to get out so i had to reboot. The result is a black screen and the device detected as MTP device...
Im trying to get on recovery with the keyboard but it dsnt works :/
tupie said:
I did the same, to be clear: i did wipe data and dalvik to flash a ROM and when y tried to flash i got an error. I dont know how but i missclicked on a keyboard test and dont know how to get out so i had to reboot. The result is a black screen and the device detected as MTP device...
Im trying to get on recovery with the keyboard but it dsnt works :/
Click to expand...
Click to collapse
lel, everytime ill visit a thread to help somebody, their problem seems to be directly releated to the one i had a few days ago.
try to list the device via adb, if it doesnt show up, click this link and scroll down to my second post, it seems recovery, fastboot, and normal operation have 3 different hardware id's.
OPTIONAL
ArdDarvis also pointed out that you can add the id instead of replacing it, just seperate them with a comma like this:
Code:
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010, USB\VID_18D1&PID_D001
report back and let us know if it worked.
iAmSmokey said:
lel, everytime ill visit a thread to help somebody, their problem seems to be directly releated to the one i had a few days ago.
try to list the device via adb, if it doesnt show up, click this link and scroll down to my second post, it seems recovery, fastboot, and normal operation have 3 different hardware id's.
OPTIONAL
ArdDarvis also pointed out that you can add the id instead of replacing it, just seperate them with a comma like this:
Code:
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010, USB\VID_18D1&PID_D001
report back and let us know if it worked.
Click to expand...
Click to collapse
Tnx for the help but my problem wasnt like your. I just wiped my data partition. I finally fixed it using the alt+i+imprscrn keys to get on CWM and restoring from backup.
Tnx a lot anyway dude
I went ahed and installed the drivers anyway, and I got a "google device" and not OUYA, my box isn't detected when I try to sideload OTA!
my device manager shows this...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I need help, please...
That may still work like that. My OUYA is detected by Windows 7 home premium 64bit very similarly and I was able to access it using the one click test version.
Go ahead and try to get on to recovery
Sent from my SCH-I535 using Tapatalk 4 Beta
Il_Padrino have you tried reinstalling the driver? also the image is a little small :S
iAmSmokey said:
Il_Padrino have you tried reinstalling the driver? also the image is a little small :S
Click to expand...
Click to collapse
I did. says it's a generic google device, doesn't recognizes being an ouya...
Il_Padrino said:
I did. says it's a generic google device, doesn't recognizes being an ouya...
Click to expand...
Click to collapse
It shouldn't matter. You just need to connect via adb, have you tried to list adb devices from the command prompt?
As I said, that is how my computer lists it and I was able to root it using the test version of the tool kit.
Sent from my SCH-I535 using Tapatalk 4 Beta
TadeoNYC said:
It shouldn't matter. You just need to connect via adb, have you tried to list adb devices from the command prompt?
As I said, that is how my computer lists it and I was able to root it using the test version of the tool kit.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
my device is listed and connect, however, when I try to sideload the OTA it gives me it shows E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
I tried installing CWM again, and even pushing the boot.img into ouya, but when I go and change the drivers from adb to bootloader the ouya restarts and the alt+prt sc+I method doesn't work...
Just came to realize that all the directories in my memory are gone I tought that it was like the phones, that if you formated the SD Card it would be rebuilt with the standard directories,
Is there any way to create directories trough adb?
Can anyone send me a backup of their system?
or
Do I have a brick?
Il_Padrino said:
my device is listed and connect, however, when I try to sideload the OTA it gives me it shows E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
I tried installing CWM again, and even pushing the boot.img into ouya, but when I go and change the drivers from adb to bootloader the ouya restarts and the alt+prt sc+I method doesn't work...
Just came to realize that all the directories in my memory are gone I tought that it was like the phones, that if you formated the SD Card it would be rebuilt with the standard directories,
Is there any way to create directories trough adb?
Can anyone send me a backup of their system?
or
Do I have a brick?
Click to expand...
Click to collapse
nothing is bricked as long as you still have a recovery installed.
either CWM or Stock, download this: http://devs-ouya-tv-prod.s3.amazonaws.com/ota/RC-OUYA-1.0.356-r1_ota.zip
1.) Then bring your Ouya into recovery, turn it on and hold alt+prt sc+I several times until the Ouya Logo and a exclamation mark shows up, then press HOME.
2.) Do a factory reset
3.) navigate to apply update from ADB, plug your Ouya into USB and use "ADB sideload RC-OUYA-1.0.356-r1_ota.zip"
4.) after a reboot your Ouya should work again.
If you had CWM and applying the OTA update bricked your Ouya, repeat these steps with the Stock recovery, if it didn't flash the stock recovery, try looking for the stock recovery that you can flash with CWM.
This was the case for me, flashing the OTA update with CWM bricked it, but it was fine after I flashed with stock.
My drama is over...
I come to accept it. My OUYA is 100% bricked has I lost recovery from my litle box...
It was fun, but now is over.
:crying:

Instaled wrong ROM, how reinstal? P6-C00

I have Huawei P6-C00. It is Dualsim, china version. I tried instal CyanogenMod 10.1 for p6-u0. Now I can start my phone. When it starts I see:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried instal it by Recovery but I have only this options:
When I conected my phone to computer by USB:
I have clear ROM for my version but I can't instal it. How I can do this? Please help me.
aknorts said:
I have Huawei P6-C00. It is Dualsim, china version. I tried instal CyanogenMod 10.1 for p6-u0. Now I can start my phone. When it starts I see:
I tried instal it by Recovery but I have only this options:
When I conected my phone to computer by USB:
I have clear ROM for my version but I can't instal it. How I can do this? Please help me.
Click to expand...
Click to collapse
dissconnet it from the usb port and if you have the update.app in the dload folder in your SD card, the update should work
It is Dualsim model, It has not SDcard. In place SD slot is second simcard.
Any other solution this issue?
From here
http://dl-uk.huaweinews.com/index.php?dir=Roms/Ascend-P6/
I have oryginalny ROM for this phone, but I don't idea how I can instal it.
Do You have access to external memory via USB?
So, can You use it as mass storage?
If yes, then create a folder on the internal storage vith the name DLOAD and put the official ROM (the file called UPDATE.APP) in it.
Power off your P6.
Hold both vol up and vol down. Turn it on and hold all the three keys (power on, vol up, vol down). When You see Huawei logo, release the Power key, but still hold the vol buttons, untill You see that the update starts.
This is how I could go back to stock ROM from MIUI..
1. No I has not access to external memory via USB. When I tried connect it. I have communicat: http://oi42.tinypic.com/102kz04.jpg
2. No I cant use it as mass storage.
3. When I hold all three keys I see: http://oi44.tinypic.com/jv0xug.jpg
If you can't help I will go to servis with Jtag, but how they open this phone? They can open phone?
aknorts said:
1. No I has not access to external memory via USB. When I tried connect it. I have communicat: http://oi42.tinypic.com/102kz04.jpg
2. No I cant use it as mass storage.
3. When I hold all three keys I see: http://oi44.tinypic.com/jv0xug.jpg
If you can't help I will go to servis with Jtag, but how they open this phone? They can open phone?
Click to expand...
Click to collapse
ur problem isn't that big, u just need to put the firmware file on your internal storage, u might try to flash TWRP via fastboot and u can access your internal storage from it with usb
7OOKA said:
ur problem isn't that big, u just need to put the firmware file on your internal storage, u might try to flash TWRP via fastboot and u can access your internal storage from it with usb
Click to expand...
Click to collapse
adb does not work in stock recovery I think...
edit: oops, my bad. He should be able to do it in the download mode
Thanks for answers.
I am noob, how do it?
aknorts said:
Thanks for answers.
I am noob, how do it?
Click to expand...
Click to collapse
first follow this amazing guide : http://techglen.com/2013/10/01/abd-and-fastboot-guide/
then continue with TWRP guide
Hey, thanks for your help. I do exacly what is in turtorial. But where can I take the recovery_original_flashable.img? It is in ROM? Where?
aknorts said:
Hey, thanks for your help. I do exacly what is in turtorial. But where can I take the recovery_original_flashable.img? It is in ROM? Where?
Click to expand...
Click to collapse
that if you will flash stock recovery, but i guess u will flash TWRP, so after finishing the 1st guide go straight to TWRP thread and download it from there
Good luck
Ok, thx. I did this. But all time I has comunicat: "wait for device" and nothing happend.
aknorts said:
Ok, thx. I did this. But all time I has comunicat: "wait for device" and nothing happend.
Click to expand...
Click to collapse
i will assume that u followed the fastboot guide to the letter and everything went fine, open driver tools and uninstall the drivers and reinstall it, then connect the device to the pc and hold power and vol - buttons till the device reboots then release the power button and keep holding vol - for few seconds (2 or 3) then your pc should recognize ur device as an "adb interface" then u can flash the recovery straight (fastboot flash recovery recovery.img)
if that won't work then u did something wrong in setting fastboot
I tried in two PC and I did step by step. Really I don't know what is wrong.
Probably will not work, but try this one: http://forum.xda-developers.com/showthread.php?t=2618253

Resources