Ouya Bricked ? - Ouya Q&A, Help & Troubleshooting

Hello !
Here's my prob :
I installed CWM Recovery on my OUYA, and then i wanted to flash a ROM via recovery.
Unfortunately, i've done a full wipe while in recovery, and restarted the console.
Now it's turning on, with the power button on, black screen, and identifyed as an MTP USB device.
I tried the alt + Sysreq + i trick, but it doen't seems to work here ...
Any chance to get it back to life in other way ?

Keep trying alt + sysreq + i trick my takes about 50 times before the light on the ouya flashes then i have to hit the home key some times to see anything

imerrn said:
Keep trying alt + sysreq + i trick my takes about 50 times before the light on the ouya flashes then i have to hit the home key some times to see anything
Click to expand...
Click to collapse
What timing of button's hitting have you used ?
The light of the OUYA is flashing when in recovery mode ?

ElMeteK said:
What timing of button's hitting have you used ?
The light of the OUYA is flashing when in recovery mode ?
Click to expand...
Click to collapse
Try these timings. I had the same issue and these worked for me. The keyboard trick is currently your only hope.

I keep pressing alt + sysreq + i keys at the same time takes me about 30 times to get to recovery the light will flash one time then i know im in recovery some times iget the ouya smile with a ! mark some time a black screen then i press home button to get to recovery push the home button again it goes away i have done about three ouya.

Problem solved.
My ouya doesn't loved my Microsoft Keyboard...
I used a generic on, and it works directly
Ouya saved
Another advice : if it doesn't work, try another keyboard !

Ouya Bricked Need Help Reward For The Fixer
Here is my Issue I installed The CWM and flashed over a few ROMS but really wanted to try out the CM10. I had all my files backed up but some how they were all deleted and when I turn on my machine I get the Cyanogen boot loop and I can do the keyboard trick print screen/ Alt / I but there is no files to recover and I have no way to load any ROM directly to my internal nand flash unless there is something I am missing.
I am so upset I with thy would have put a sd card slot on this thing. Can anyone help me to try to recover putting any stock ROM back on my machine or is there a way to get my PC to read my device to load the ROM to my internal HD?
Please any help and instructions would be greatly appreciated.
I need some serious help here. Thanks to anyone who can get me back up and running again I will even send the person who has the solution one of my devices that run XBMC like a champ. Here is my site for anyone who is up for the challenge. www.xbmcandroidtv.com the EXOON Q2 Plus is the device I will send to the person who solves my dilemma.
I have tried the keyboard trick but all I get it to do is load into CWM and there is nothing to load. Am I doing something wrong?
Thanks in advance and eager to get my OUYA back up and running.

labossiere said:
Here is my Issue I installed The CWM and flashed over a few ROMS but really wanted to try out the CM10. I had all my files backed up but some how they were all deleted and when I turn on my machine I get the Cyanogen boot loop and I can do the keyboard trick print screen/ Alt / I but there is no files to recover and I have no way to load any ROM directly to my internal nand flash unless there is something I am missing.
I am so upset I with thy would have put a sd card slot on this thing. Can anyone help me to try to recover putting any stock ROM back on my machine or is there a way to get my PC to read my device to load the ROM to my internal HD?
Please any help and instructions would be greatly appreciated.
I need some serious help here. Thanks to anyone who can get me back up and running again I will even send the person who has the solution one of my devices that run XBMC like a champ. Here is my site for anyone who is up for the challenge. www.xbmcandroidtv.com the EXOON Q2 Plus is the device I will send to the person who solves my dilemma.
I have tried the keyboard trick but all I get it to do is load into CWM and there is nothing to load. Am I doing something wrong?
Thanks in advance and eager to get my OUYA back up and running.
Click to expand...
Click to collapse
You have to fastboot the "boot.img" supplied with CM10. I had the same issue so pm me if you need help.:good:

Never, ever ever ever ever ever wipe the boot.img, if you want to be safe, never replace it either, you can always 'fastboot boot boot.img" it.
Sent from my SAMSUNG-SGH-I317 using xda premium

at what point does your Ouya connect back to your pc so you can do a fastboot command? do you have to be in CWM?

glitchhawk said:
at what point does your Ouya connect back to your pc so you can do a fastboot command? do you have to be in CWM?
Click to expand...
Click to collapse
You can do it from CWM, but you don't have to be there. Depends on what you've done to your system. If you flashed CM10 and now it's detected as an MTP device your best bet is to reboot into recovery and 'adb reboot bootloader' then use fastboot commands. That's what worked for me.

BUS DR1V3R said:
You can do it from CWM, but you don't have to be there. Depends on what you've done to your system. If you flashed CM10 and now it's detected as an MTP device your best bet is to reboot into recovery and 'adb reboot bootloader' then use fastboot commands. That's what worked for me.
Click to expand...
Click to collapse
ok, cuz im basically in the same boat as everyone else. i flashed CM10 and now its hanging at the CM boot screen. so i guess its time to sit there and tap keys for hours lol.

BUS DR1V3R said:
You can do it from CWM, but you don't have to be there. Depends on what you've done to your system. If you flashed CM10 and now it's detected as an MTP device your best bet is to reboot into recovery and 'adb reboot bootloader' then use fastboot commands. That's what worked for me.
Click to expand...
Click to collapse
in stock recovery am i suppose to go into sideload sub menu? my pc doesn't detect the ouya in the main recovery menu

glitchhawk said:
in stock recovery am i suppose to go into sideload sub menu? my pc doesn't detect the ouya in the main recovery menu
Click to expand...
Click to collapse
How does the Ouya show up in device manager? Is there an exclamation point beside it?
If the drivers are fine then try mounting /data in recovery.

BUS DR1V3R said:
How does the Ouya show up in device manager? Is there an exclamation point beside it?
If the drivers are fine then try mounting /data in recovery.
Click to expand...
Click to collapse
sorry, how do i mount it? the only options i have in stock recovery is
Reboot system now
Apply update from ADB (if i go into this menu i have the driver installed on pc and it comes up adb composite device)
wipe data/factory reset
wipe cache partition

glitchhawk said:
sorry, how do i mount it? the only options i have in stock recovery is
Reboot system now
Apply update from ADB (if i go into this menu i have the driver installed on pc and it comes up adb composite device)
wipe data/factory reset
wipe cache partition
Click to expand...
Click to collapse
Ah, stock recovery.... You could go into Apply Update From ADB. Then type "adb reboot bootloader" then you can type "fastboot boot boot.img" to boot successfully into CM10.
You can put the boot.img for CM10 in the same folder as fastboot.exe to make things easier.

BUS DR1V3R said:
Ah, stock recovery.... You could go into Apply Update From ADB. Then type "adb reboot bootloader" then you can type "fastboot boot boot.img" to boot successfully into CM10.
You can put the boot.img for CM10 in the same folder as fastboot.exe to make things easier.
Click to expand...
Click to collapse
well this is lame.. it keeps telling me Error: Closed

glitchhawk said:
well this is lame.. it keeps telling me Error: Closed
Click to expand...
Click to collapse
What keeps telling you that? What are you doing? I need more information.

BUS DR1V3R said:
What keeps telling you that? What are you doing? I need more information.
Click to expand...
Click to collapse
I put the Ouya on sideload from adb.
Then i open adb on my pc, check to make sure it finds the Ouya and then i try to adb reboot bootloader. and that error comes up. if i try to load an .img file from the same place it just says <waiting for device> and doesn't ever move.

glitchhawk said:
I put the Ouya on sideload from adb.
Then i open adb on my pc, check to make sure it finds the Ouya and then i try to adb reboot bootloader. and that error comes up. if i try to load an .img file from the same place it just says <waiting for device> and doesn't ever move.
Click to expand...
Click to collapse
If it says <waiting for device> then its probably a driver issue with fastboot. When you reboot into the bootloader go into device manager and check the driver again. I also had this issue.

Related

I think ive bricked my phone?

Sup everyone
ive completly done a **** up whist trying to flash my phone with android hd rom.
ive actually put the wrong zip on to the phone and now has wiped my phone and wont boot up.
i can access recovery mode but the phone will not boot up. it gets stuck on google.
if i try to mount usb storage i get a error :
Unable to open ums lunfile (no such file or directory)
Is there a way around this PLS?
jeezy85 said:
Sup everyone
ive completly done a **** up whist trying to flash my phone with android hd rom.
ive actually put the wrong zip on to the phone and now has wiped my phone and wont boot up.
i can access recovery mode but the phone will not boot up. it gets stuck on google.
if i try to mount usb storage i get a error :
Unable to open ums lunfile (no such file or directory)
Is there a way around this PLS?
Click to expand...
Click to collapse
How this post belongs in dev area???
Go to android hd rom and ask your question or post it in Q&A!!!!
Come on
how do i delete this thread?
jeezy85 said:
how do i delete this thread?
Click to expand...
Click to collapse
Mods going to move it or if you ask they are going to delete it.Please read forum rules before posting
Flash stock images in fast boot. You can't mount USB storage on this phone anyways.
Sent from my Galaxy Nexus using xda premium
happen to me too....
I flashed an Pauls update instead of core and messed my phone up.
flash stock image then use ADB and push the rom to the sd/update.zip - then flash.
That should fix it.
You're phone is not bricked. Reflash the factory images using fastboot. http://groups.google.com/group/andr...hread/2dde45a058a737b9/43c3a418144fc6c5?pli=1
thanks for the replies really appreciate it
just to clarify
is fastboot mode recovery mode?
jeezy85 said:
thanks for the replies really appreciate it
just to clarify
is fastboot mode recovery mode?
Click to expand...
Click to collapse
Hold the Volume Up Key + Volume Down Key and then press the Power button.
jeezy85 said:
thanks for the replies really appreciate it
just to clarify
is fastboot mode recovery mode?
Click to expand...
Click to collapse
fastboot is fastboot recovery is recovery
Yeah, what Stea1thmode said
fastboot is a bit more lower level [i think] than recovery
pulling my hair out lol
im completly lost
ive downloaded the stock image... just dont know how to flash it
First of all naughty naughty please do not post questions in the development forum. I moved it over to Q&A
Ok now thats over with follow *THIS* guide to get fastboot drivers set up on your pc. Some users spend hours trying to figure it out (myself included the first time) and that guide is detailed. Install the pdanet program on your comp to get the needed drivers then boot your phone into fastboot mode and connect to your pc via usb cable. If it doesnt install the automatically then you can do it manually via the Device Manager.
Once the drivers are installed open up a command prompt and goto the folder you put the fastboot.exe file in. Type fastboot devices and it should return a number which means your phone is recognised.
Next goto *THIS* thread and follow the instructions to fastboot the Stock images back to your device and restore your phone.
Once everything is back and working READ every instruction thoroughly before doing anything in future Luckily this phone is next to impossible to brick
Mark.
thank you so much for pointing me in the right direction...
things seem to be getting worse..
im having trouble installing drivers.. (windows 7)
it keeps failing :S
jeezy85 said:
thank you so much for pointing me in the right direction...
things seem to be getting worse..
im having trouble installing drivers.. (windows 7)
it keeps failing :S
Click to expand...
Click to collapse
I have windows 7 too so it will work its just a pain to get them on.
Did you install the pdanet drivers to your pc? Did you update the drivers in the Device Manager? Please list your exact procedure you followed and where you are getting stuck.
Mark.
ok my phone gets stuck on the google sign...
if plug in my phone the comp detects it.. it starts installing the drivers Samsung mobile MTP Drivers.. then all of a sudden it says failed....i also installed Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe
still no luck
i tried installing the pdanet program but it doesnt detect the phone as it doesnt boot up?
jeezy85 said:
ok my phone gets stuck on the google sign...
if plug in my phone the comp detects it.. it starts installing the drivers Samsung mobile MTP Drivers.. then all of a sudden it says failed....i also installed Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe
still no luck
i tried installing the pdanet program but it doesnt detect the phone as it doesnt boot up?
Click to expand...
Click to collapse
Why are you trying to boot up the phone if you know it doesnt boot?
You need to do everything through the fastboot screen. Hold Volume Up and Volume Down buttons while pressing the power button until the big green Android icon appears and it will say fastboot on the screen.
Have your Device Manager open (from settings on your pc) so that you can dee the item pop up in the list that you need to update the driver for.
PdaNet drivers are the best ones that work for fastboot.
Mark.
when i go into fastboot mode.. then go to device manager the only thing i can see with a explanation mark is android 1.0.....
theres no samsung device or nothing
jeezy85 said:
when i go into fastboot mode.. then go to device manager the only thing i can see with a explanation mark is android 1.0.....
theres no samsung device or nothing
Click to expand...
Click to collapse
Yes thats the item you need to update the driver for.
Make sure you have installed the samsung drivers (and maybe pdanet drivers if you want to be safe) on your pc first. Then double click on the Android 1.0 item and then select Driver, Update Driver. Click Browse My Computer and then Let me pick from a list.
It should give you a few options. If you see it then select Android Adb Device but if not try one odf the samsung adb interface drivers.
Mark.
mskip i LOVE YOU!!!
starting to get somewhere got the drivers installed...
ok i typed this command in cmd where the stock img is
fastboot-windows flash all flash-all.sh
i get this
sending 'all'<0 KB>....OKAY
writing 'all'.....FAILED <remote : Unkown Partition>
Any ideas?
try just flashing the image zip.
Code:
fastboot -w update image-yakju-itl41f.zip

[Q] NOOB bricked acer a100 help!

I tried using the simple root and clockwork mod method and now my a100 keeps cycling thru bootloaderversion 0.03.06-ics-ics (unlock mode) with green acer logo. If I reboot holding power+down sd update command recovery
update_package=sd card update.zip
booting recovery kernal image
then it starts cycling again.
Please can someone help!
same
Same thing here (or at least very similar). Hoping there's a simple solution like the "Odin back to stock" I can do on my SGS phone.
are you sure that the bootloader say "unlock mode"?
If so, then try this.
try this
Install the USB drivers on your PC if you haven't done it already. ( http://global-download.acer.com/GDF...A TAB&Step3=A100&OS=a08&LC=en&BC=Acer&SC=PA_6 )
install android SDK. ( http://developer.android.com/sdk/index.html )
copy the update.zip file to your SD card root.
download TWRP recovery ( http://forum.xda-developers.com/showthread.php?t=1608152 ) and place it in the platform-tools dir where the SDK was installed ( ex. C:\Program Files\Android\android-sdk\platform-tools )
Once all that is done follow these steps
1) boot the tablet to fastboot mode
2) run command prompt on PC (cmd.exe)
3) cd to the platorm-tools dir
4) type the following lines one at a time.
adb.exe
fastboot erase recovery
fastboot flash recovery NAMEOFRECOVERY.img (ex. recovery-A100ICS-TWRP.img)
5) hold the vol down button on the tablet
6) type fastboot reboot.
The tablet should now reboot to the recovery program. Goto settings and mount the external SD card, then flash the update.zip by going to install.
Hope this helps
[email protected] said:
I tried using the simple root and clockwork mod method and now my a100 keeps cycling thru bootloaderversion 0.03.06-ics-ics (unlock mode) with green acer logo. If I reboot holding power+down sd update command recovery
update_package=sd card update.zip
booting recovery kernal image
then it starts cycling again.
Please can someone help!
Click to expand...
Click to collapse
Did you rename/delete /etc/install-recovery.sh ?
I think you're not. Try to make hard reset, then boot normaly rename/delete this file and after that flash recovery again, it should work.
All it's explained here.
Thank you
TheBlackshinobi said:
are you sure that the bootloader say "unlock mode"?
If so, then try this.
try this
Install the USB drivers on your PC if you haven't done it already. ( http://global-download.acer.com/GDF...A TAB&Step3=A100&OS=a08&LC=en&BC=Acer&SC=PA_6 )
install android SDK. ( http://developer.android.com/sdk/index.html )
copy the update.zip file to your SD card root.
download TWRP recovery ( http://forum.xda-developers.com/showthread.php?t=1608152 ) and place it in the platform-tools dir where the SDK was installed ( ex. C:\Program Files\Android\android-sdk\platform-tools )
Once all that is done follow these steps
1) boot the tablet to fastboot mode
2) run command prompt on PC (cmd.exe)
3) cd to the platorm-tools dir
4) type the following lines one at a time.
adb.exe
fastboot erase recovery
fastboot flash recovery NAMEOFRECOVERY.img (ex. recovery-A100ICS-TWRP.img)
5) hold the vol down button on the tablet
6) type fastboot reboot.
The tablet should now reboot to the recovery program. Goto settings and mount the external SD card, then flash the update.zip by going to install.
Hope this helps
Click to expand...
Click to collapse
I'm going to try this, one question though. My computer does not read the tablet anymore even though I have the drivers installed will it still work? Yes I'm a serious noob, but I'm trying...and thank you for your help it is much appreciated.
cpu doesnt read tablet anymore
[email protected] said:
I'm going to try this, one question though. My computer does not read the tablet anymore even though I have the drivers installed will it still work? Yes I'm a serious noob, but I'm trying...and thank you for your help it is much appreciated.
Click to expand...
Click to collapse
Okay, I downloaded everything but my computer doesnt recognize my a100 anymore, only if I put the tablet into fastboot then it see's it. My tablet just keeps on rebooting itself repeatedly unless I go into fastboot. Please tell me I dont have a paperweight.
were getting close
Blackshinobi or anyone that can help,
I'm getting close. I make it to: "fast boot flash recovey" cmd prompt
I get two different errors depending hoew I type the cmd prompt:
1. "fastboot flash recovery recovery-A100ICS-TWRP.img"
error (can not load recovery-A100ICS-TWRP.img)
2. "fastboot flash recovery-A100ICS-TWRP.img"
error ( cannort determine image file name for 'recovery-A100ICS-TWRP.img)
I was a little confuse on proper cmd line prompt, but I'm thinking #2 is the correct way.
Thanks so much for your help!
pfisher101 said:
Blackshinobi or anyone that can help,
I'm getting close. I make it to: "fast boot flash recovey" cmd prompt
I get two different errors depending hoew I type the cmd prompt:
1. "fastboot flash recovery recovery-A100ICS-TWRP.img"
error (can not load recovery-A100ICS-TWRP.img)
2. "fastboot flash recovery-A100ICS-TWRP.img"
error ( cannort determine image file name for 'recovery-A100ICS-TWRP.img)
I was a little confuse on proper cmd line prompt, but I'm thinking #2 is the correct way.
Thanks so much for your help!
Click to expand...
Click to collapse
That's awesome news!!!
Number 1 is the correct command.
Just making sure you are actually in fastboot (bootloader) mode. On the command-promt type "fastboot devices", if you see the result below, then you're good
? fastboot (yes that's a question mark)
Now be sure you are in the directory with the recovery image and issue number 1 command (fastboot flash recovery whatever-recovery.img). If you get some errors, be sure to check the MD5 hash of the recovery image cuz it could be a corrupted download.
Of course, you can't flash the custom recovery if you still have a locked bootloader.
you guys rock..even closer
Thank-you everyone ..I am soooo close. I did get the recovery image to load (I accidently had it in android-sdk and not platform-tools...oooops my bad). Now I can reboot to recovery and install the update.zip off my external sd card. However after I install the update.zip and reboot, I still get stuck on the acer screen (bootloader version 0.03.06-ICS (Unlock Mode) at top with acer logo in green at bottom.
Which update.zip am I suppose to be using? Currently I am trying to install one of the stock ROMS from the developer section of this forum. Am I suppose to be using a specific one?
Thanks again, I know I'm close. My tablet has been brick'd for weeks and I'm dedicated to getting it back now that I have time.
pfisher101 said:
Thank-you everyone ..I am soooo close. I did get the recovery image to load (I accidently had it in android-sdk and not platform-tools...oooops my bad). Now I can reboot to recovery and install the update.zip off my external sd card. However after I install the update.zip and reboot, I still get stuck on the acer screen (bootloader version 0.03.06-ICS (Unlock Mode) at top with acer logo in green at bottom.
Which update.zip am I suppose to be using? Currently I am trying to install one of the stock ROMS from the developer section of this forum. Am I suppose to be using a specific one?
Thanks again, I know I'm close. My tablet has been brick'd for weeks and I'm dedicated to getting it back now that I have time.
Click to expand...
Click to collapse
Congrats resurrecting your tab! Gotta be a great relief!
How about Flexreaper ROM? It will require full wipe before flashing: in recovery wipe/factory reset, wipe system, wipe cache, wipe dalvik cache, flash Flexreaper ROM zip file. This is basic guide, follow detailed instructions on this ROM thread (link is in my sig).
Sent from my A100 using xda premium
not quite recovered yet. I still get the hang on Acer screen. anyone know why? I will try flexreaper
I'm BACK
Thanks to all. I'm back up. flexreaper did work.. I hope the guy who actually started this thread is as lucky.
Not so lucky
I'm still stuck my pc doesnt read my acer a100 still....any helps out there?
[email protected] said:
I'm still stuck my pc doesnt read my acer a100 still....any helps out there?
Click to expand...
Click to collapse
Power down the unit. Set screen lock in the up position. Hold volume down and power. When powered on keep holding the vol down button. Then toggle the screen lock to down.
That should do a factory reset.
Then put a stock rom in the root of SD Card. Volume up then power until let the tablet recover.
This worked for me.
did u install the drivers from an earlier post? Also when you power up you your tablet you need to boot into fastboot mode? You're certain you have done both of these things?
I am unable to connect to, my pc doesnt recognize my acer anymore...unless by sd card you mean external card? Thank you for trying to help. I'm a serious noob but trying hard.
i'm in a similar situation. i accidentally deleted the build.prop file and rebooted. now it only displays a black screen after the acer logo drops out. my boot loader is locked but i cant install the mtp usb drivers to fix anything. think i have a paperweight now.
mechpilot_z said:
i'm in a similar situation. i accidentally deleted the build.prop file and rebooted. now it only displays a black screen after the acer logo drops out. my boot loader is locked but i cant install the mtp usb drivers to fix anything. think i have a paperweight now.
Click to expand...
Click to collapse
that's easily fixed, install this through stock recovery, http://forum.xda-developers.com/showthread.php?t=1611696
eww245 said:
that's easily fixed, install this through stock recovery, http://forum.xda-developers.com/showthread.php?t=1611696
Click to expand...
Click to collapse
tried. i had no alternative recovery on it. i could not get the sd card mounted to push the zip to it. both adb and fast boot wont see my tablet. every attempt at unlocking fast boot wouldn't work. I tried to check in device manager to see if it was connected, the driver was working but it had an error message "Device can not start (Code 10)"
My pc only sees my tablet when I boot it into fastboot mode and sees it as an adb interface...Is there anything I can do from there?

Erased EVERYTHING

I accidently erased everything from the KF2, all I have on it now is the recovery.
How can I get a rom back on the device?
When I plugged it in the computer under Device Manager it says Portable Devices >> F:/
When I go to my computer to try to enter f:/ its inaccessible.
How can I fix this?
Thanks!
Same issue here. Understood the instruction to wipe everything before installing ROM to mean "System" and "Internal Storage" as well. Now the downloaded ROM and "gapps" zip files are gone...
Found something called "ADB Sideload" in TWRP, could that help?
Like the OP, would appreciate some help. Kindle is a brick for now...
chipsndukes
Back Up & Running
First You need a Fastboot Cable.
Run The Recovery Tool. (Options 1 then 2)
When its completed unplug the Fastboot Cable and press and hold the power button until the KF2 turns off.
Turn it back on and you are all set to Root it!
Rooting
[ONE-CLICK] Automated Freedom-Boot and TWRP installer
OK, thanks LEGEND94, that helped !
Only difference to above: did not use a Fastboot cable to get into fastboot mode, rather fmkilo's technique here: http://forum.xda-developers.com/showthread.php?t=2117224
Held off button to shut down and restarted without having to do anything else, did not have to type any command to get out of fastboot mode.
Am restarting root and ROM flashing, hopefully will work this time.
Thanks again,
chipsndukes
chipsndukes said:
OK, thanks LEGEND94, that helped !
Only difference to above: did not use a Fastboot cable to get into fastboot mode, rather fmkilo's technique here: http://forum.xda-developers.com/showthread.php?t=2117224
Held off button to shut down and restarted without having to do anything else, did not have to type any command to get out of fastboot mode.
Am restarting root and ROM flashing, hopefully will work this time.
Thanks again,
chipsndukes
Click to expand...
Click to collapse
even though legend was OP, his method was a bit overkill, but totally fine.
Once you have recovery, or even the bootloader, you should NEVER need to restore. From the bootloader you can get into fastboot now, and from fastboot you can get the recovery.
As for putting files on, I'm not sure. I could look it up but you both got your issues solved. If someone coming here does need the help, PM me and I can look it up, but from what i remember on other android devices, usually the recovery somewhere has an option to mount USB like a storage device (probably bad wording there) but basically just like when you "turn on usb storage" in the android OS.
I am ASSUMING TWRP has something similar, and if I'm wrong, I'm sure you can always ADB to push the files onto the device from your PC in fastboot mode.
iytrix said:
even though legend was OP, his method was a bit overkill, but totally fine.
Once you have recovery, or even the bootloader, you should NEVER need to restore. From the bootloader you can get into fastboot now, and from fastboot you can get the recovery.
As for putting files on, I'm not sure. I could look it up but you both got your issues solved. If someone coming here does need the help, PM me and I can look it up, but from what i remember on other android devices, usually the recovery somewhere has an option to mount USB like a storage device (probably bad wording there) but basically just like when you "turn on usb storage" in the android OS.
I am ASSUMING TWRP has something similar, and if I'm wrong, I'm sure you can always ADB to push the files onto the device from your PC in fastboot mode.
Click to expand...
Click to collapse
Unfortunately usb Mount doesn't work in the kf2 twrp. I would love the option.
You CAN adb sideload from twrp though.
--
Sent from my Kindle Fire 2, CM 10.1
What I did above is the easiest way, the sideload didn't even work!
chipsndukes said:
Held off button to shut down and restarted without having to do anything else, did not have to type any command to get out of fastboot mode.
Click to expand...
Click to collapse
One change to the above statement. I did have to get out of fastboot mode, but it was confusing how because the terminal emulator was now gone.
I did this instead via a command window with the Fire plugged into the computer. I sent the "fastboot -i0x1949 oem idme bootmode 1" command while in the root directory for the KF2_SRT_10.2.3 restore package, there is a fastboot.exe file there.
Hope that helps.
chipsndukes

[Q] Stuck on Slimbean Boot Logo

Hello i am having problem with my samsung galaxy nexus I9250
i just factory reset the Slimbean Rom and now got stuck on Slimbean boot logo
i cant even go to the recovery mode, i cant even enter to the download mode,
but on the Slimbean boot logo when i attached the USB on my computer the Galaxy Nexus was detected and i can access the internal storage
but my phone is still stuck on Slimbean Logo
NEED HELP!
THANKS!
a small reward will be sent to anyone that can help me fix this out :good:
You tried accessing recovery by pressing vol up+vol down+power, then scrolling down to recovery with volume key and press power?
ntybrav infpire
t1.8matt said:
You tried accessing recovery by pressing vol up+vol down+power, then scrolling down to recovery with volume key and press power?
Click to expand...
Click to collapse
yes i tried that but slimbean wont let me
What happens when you press the button combo? Does it do anything at all like go to fastboot mode or it just tries to boot the ROM?
t1.8matt said:
What happens when you press the button combo? Does it do anything at all like go to fastboot mode or it just tries to boot the ROM?
Click to expand...
Click to collapse
no luck, its just proceeding to the ROM, i cant enter fastboot or flashboot or download mode even if i combine any keys
Weird, I don't know how you would lose fast boot. I'm not sure if this will work but can you plug into your computer and boot the phone up and try to use adb to boot into fast boot. I think its adb reboot-fastboot or adb reboot fastboot. Or try adb reboot-recovery or adb reboot recovery. I can never remember if you need the hyphen in adb.
t1.8matt said:
Weird, I don't know how you would lose fast boot. I'm not sure if this will work but can you plug into your computer and boot the phone up and try to use adb to boot into fast boot. I think its adb reboot-fastboot or adb reboot fastboot. Or try adb reboot-recovery or adb reboot recovery. I can never remember if you need the hyphen in adb.
Click to expand...
Click to collapse
maybe i guess it was bricked im stuck on the Slimbean logo like forever, sorry but what tool can i use to enter the adb fastboot ? noob here thanks for the response anyway
Follow Step A and Step C #1-2 from here to get adb and fast boot setup on your computer. http://forum.xda-developers.com/showthread.php?t=1626895 After you get it setup, you go into the platform tools folder which you will download as part of Step C and right click and click command prompt, then enter those commands I gave you. How did you root and install a recovery the first time?
t1.8matt said:
Follow Step A and Step C #1-2 from here to get adb and fast boot setup on your computer. http://forum.xda-developers.com/showthread.php?t=1626895 After you get it setup, you go into the platform tools folder which you will download as part of Step C and right click and click command prompt, then enter those commands I gave you. How did you root and install a recovery the first time?
Click to expand...
Click to collapse
Here's what just happened
my brother gave me this phone,
it has a slimbean rom which is my first time seeing that rom
i just go to settings
and click the factory reset
when the phone boots up i can only access the settings no other thing after that
i managed to get into the recovery mode of that rom on the settings
and install the rom again which is still on the sd card
then after the installation is completed when it boots up its now stuck on boot screen
and im screwed
i tried the universal naked driver but no luck device is still not recognized
I see. You're not supposed to use factory reset from the settings. You should only be doing that from recovery. I'm really not sure what else to do, my knowledge is limited on this. Hopefully someone else with more experience can chime in. I'm sorry I'm not able to help you on this. You tried using the platform tools to open a command prompt?
t1.8matt said:
I see. You're not supposed to use factory reset from the settings. You should only be doing that from recovery. I'm really not sure what else to do, my knowledge is limited on this. Hopefully someone else with more experience can chime in. I'm sorry I'm not able to help you on this. You tried using the platform tools to open a command prompt?
Click to expand...
Click to collapse
yep maybe thats my last luck hope it works, you think usb jig might work on this ? well thank you so much for your time and for trying to help me may god bless you always
No, theres no reason to use a USB jig. It's driver issues or something else simple, I'm just not site what. Not trying to get on you but it helps to know what your doing before you mess with things. If someone else is able to help you figure it out, do a lot of research in the general stickies before you do anything else. I hope you are able to get it going again and sorry I couldn't help you further.

Soft bricked OPO3, Fastboot with no recovery

Hi guys,
Rooted Oneplus 3 is soft bricked. Please help me!!! :crying:
:crying:Quick desription: Fastboot formatted it. My PC detects it.
Tried to Fastboot flash latest TWRP ("twrp-3.0.2-0-oneplus3.img") via CMD Prompt.
After that I get a message saying that the processed was "finished" (within 0.802s!).
Now I reboot+volume down and bootloop continues. Phone starts, I see the normal warnings I used to get after rooting it. Then I see the Oneplus logo for a fraction of a second and then it boots again and the process repeats itself.
I think it may be worth mentioning that the reason all this happened is an encryption problem that occurred while I was flashing a rom update with TWRP: After the flashing finished, got an error saying "unable to mount storage". Wiped cache+dalvik and then restarted. Got a black screen that did not display any signs of life after several minutes. Then turned it off and on by long press on the power button. Then I got an error saying that the encyption process was disrupted and that I have to wipe my phone (strange given that I did not select any encryption button in TWRP). Anyhow, then I fastboot formatted the phone and that's it.
Thank so much for anyone who can help!!!
fastboot flash recovery recovery.img (I recommend blu_spark's TWRP) reboot to recovery, if it doesn't work, try:
fastboot boot recovery recovery.img
See if you boot to recovery and then try flashing a custom ROM.
Hi Fobos, thanks for responding quickly.
I tried using fastboot boot command (with twrp-3.0.2-0-oneplus3.img). No luck with that.
Also, didn't find a downloadable blu_spark *.img version for twrp recovery. would you be so kind to add a link?
Thank you.
Now I think it's hard bricked ( Help!!!
Phone just stopped responding. Mostly doesn't respond. Occasionaly turns on for a nano second, flashes the +1 logo and turns off. Most of the time it doesnt even do that any more when I press (long / short press) the power button!
Somebody help, please!!
ppppp44 said:
Phone just stopped responding. Mostly doesn't respond. Occasionaly turns on for a nano second, flashes the +1 logo and turns off. Most of the time it doesnt even do that any more when I press (long / short press) the power button!
Somebody help, please!!
Click to expand...
Click to collapse
Keep calm and breath in. I was in the same situation.
Take a breath.
So, you have 2 ways depending on what you want. You can either go back to full stock with a flashing tool or you can install a custom recovery and then installing a custom rom (or stock one). I suggest the flashing tool.
Just follow the steps here: https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306 and if you have any question come back here and ask them.
Good luck.
Recoveryhttps://forum.xda-developers.com/devdb/project/dl/?id=24575
First format recovery by using command
fastboot format recovery
then flash recovery using
fastboot flash recovery "recovery.img"
Kayembe said:
Keep calm and breath in. I was in the same situation.
Take a breath.
So, you have 2 ways depending on what you want. You can either go back to full stock with a flashing tool or you can install a custom recovery and then installing a custom rom (or stock one). I suggest the flashing tool.
Just follow the steps here: https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306 and if you have any question come back here and ask them.
Good luck.
Click to expand...
Click to collapse
Hey Keyembe, thanks for the reply...
Tried to follow the instructions you posted. Did everything to allow unsigned drivers to be installed. Disabled it on from the advanced boot settings, and - when that didn't work, also running on test mode. Neither options work:
In the device manager I right click the android device (currently in fastboot mode), which is installed with Google drivers. I try to update the driver software to the unsigned driver and I get an error saying it's not compatible with my system (Win10 Pro) and that I should make sure it is compatible with an x64 based system.
What now?
Tx
Hey! Thanks for the reply...
anup807 said:
Recoveryhttps://forum.xda-developers.com/devdb/project/dl/?id=24575
First format recovery by using command
fastboot format recovery
then flash recovery using
fastboot flash recovery "recovery.img"
Click to expand...
Click to collapse
Hi Anup!
Thanks for the link to the Blu_Spark version of TWRP.
On CMD Prompt, tried to format recovery, console stopped responding. "Fastboot format recovery"...Just stops responding
Also tried "Fastboot delete recovery". I get a message saying "deleting recovery..." then also stops responding. Nothing happens from there.
I tried to use the OPO3 Root Toolkit. It does detect the fastboot device, but when I try to flash or boot or do anything else other than detection, it is unable to find the device. Says operation failed.
What now? :crying:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Machiel187 said:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Check your cable (try another one), even reinstall your adb drivers on your machine (if Windows).
Let the device charge for 30 minutes at least then retry (charge with new cable too).
ppppp44 said:
Hey Keyembe, thanks for the reply...
Tried to follow the instructions you posted. Did everything to allow unsigned drivers to be installed. Disabled it on from the advanced boot settings, and - when that didn't work, also running on test mode. Neither options work:
In the device manager I right click the android device (currently in fastboot mode), which is installed with Google drivers. I try to update the driver software to the unsigned driver and I get an error saying it's not compatible with my system (Win10 Pro) and that I should make sure it is compatible with an x64 based system.
What now?
Tx
Hey! Thanks for the reply...
Click to expand...
Click to collapse
Firstly, plug your phone on your computer in recovery mode or fastboot mode.
When you go in cmd and you type "adb devices" do you get anything?
If that works and you still can access recovery, you can install stock rom available on the OnePlus site. Here's a link : http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.3/
Boot into recovery, then install from adb.
Machiel187 said:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Thanks mate, followed the instructions on this post. I never get the device to be detected as Qualcomm. All I get is "Android Phone". I did install the Qualcomm drivers despite the warning I got for installing unsigned drivers. Installation went OK. When I go to the device manager again I still identifies the device as android phone. Also when I click "Have Disk" and select the qualcomm drivers I get an error saying they are incompatible with the device or with an x64 based system (regardless of them being signed or not).
Any ideas?
thanks again..
Kayembe said:
Firstly, plug your phone on your computer in recovery mode or fastboot mode.
When you go in cmd and you type "adb devices" do you get anything?
If that works and you still can access recovery, you can install stock rom available on the OnePlus site. Here's a link : http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.3/
Boot into recovery, then install from adb.
Click to expand...
Click to collapse
Hey Kayembe,
I only get to fastboot mode. No Adb device detected. No recovery mode available.
ppppp44 said:
Thanks mate, followed the instructions on this post. I never get the device to be detected as Qualcomm. All I get is "Android Phone". I did install the Qualcomm drivers despite the warning I got for installing unsigned drivers. Installation went OK. When I go to the device manager again I still identifies the device as android phone. Also when I click "Have Disk" and select the qualcomm drivers I get an error saying they are incompatible with the device or with an x64 based system (regardless of them being signed or not).
Any ideas?
thanks again..
Click to expand...
Click to collapse
Strange. Are you sure you turned off Driver Signature Enforcement?
When you hold the power button 10 seconds and plug the phone in, it should not be on. The screen should stay black. (looks like its off)
So make sure it's not trying to boot, because then it probably shows up as Android Phonee again.
Machiel187 said:
Strange. Are you sure you turned off Driver Signature Enforcement?
When you hold the power button 10 seconds and plug the phone in, it should not be on. The screen should stay black. (looks like its off)
So make sure it's not trying to boot, because then it probably shows up as Android Phonee again.
Click to expand...
Click to collapse
That's exactly what happens but when it's not in fastboot mode [ either after 10 seconds power button press or after i see the +1 logo (black screen)] - phone is not detected by my pc.
Yeah I'm sure about the driver signature enforcement. It's definitely off.
What am I doing wrong?
Thanks
ppppp44 said:
That's exactly what happens but when it's not in fastboot mode [ either after 10 seconds power button press or after i see the +1 logo (black screen)] - phone is not detected by my pc.
Yeah I'm sure about the driver signature enforcement. It's definitely off.
What am I doing wrong?
Thanks
Click to expand...
Click to collapse
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Puddi_Puddin said:
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Click to expand...
Click to collapse
ok I somehow managed to flash Blu_Spark Twrp and got it to work.
Within TWRP, flashed OnePlus3Oxygen_16_OTA_051_all_1704112009_2521.zip
and also SuperSU.zip, and no_verity.zip.
Getting some errors.
Device still doesn't boot.
Attaching the log TXT here.
I am desperate... please help.,..
Puddi_Puddin said:
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Click to expand...
Click to collapse
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
ppppp44 said:
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
Click to expand...
Click to collapse
try "default_password" for the password
ppppp44 said:
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
Click to expand...
Click to collapse
Go to Fastboot type 'fastboot erase userdata' (you have to reflash OOS tho.. Make sure you are on the latest TWRP. I'm not a fan of Bluspark but his TWRP is currently more up 2 date.

Categories

Resources