How brick-proof/-prone is the Ouya - Ouya Q&A, Help & Troubleshooting

I'm interested in trying some of the in-development projects (cwm, Rome, etc.) but I don't want to brick my device. Are there fastboot files yet?
Sent from my NookColor using Tapatalk HD

well, not fastboot files like you're thinking of. We have a CWM recovery.img that can be booted from fastboot mode, but more likely if you flash something wrong, you'll just plug in a usb keyboard and press alt+sys req+i a bunch of times and get to whatever recovery you have flashed. I "soft-bricked" mine about nine times flashing my own amateur builds of CM10 (because I'm stupid and decided the Ouya would be a good platform for my first effort at building from source...) but once I use the key combination to boot into recovery I just reflash the stock Ouya OTA from Rayman's thread, or restore my Nandroid backup and I'm up and running.
Honestly I have been doing all kinds of stupid stuff to this thing, and I've always been able to get back. Just don't do anything REALLY stupid like pulling the power while you're in the middle of flashing the recovery and you should be fine.

Related

[Q] My incredibly stupid CWM question

So I just rooted my phone thanks to Ash and Mills, but now I have an incredibly stupid question to ask about cwm...
what button combo do I have to press in order to access it on the phones start up?
I tried searching the forums, but maybe I missed an obvious post. Don't be too harsh on me!
I am in the same boat, I have gone in to fastboot and with the android SDK used the adb shell and reboot recover and will not boot to CWM. I know that i am rooted as I am able to remove apps that are stock from verizon.
The kernels which have embedded CWM are not fully functional on the R800x. There is a CWM recovery image which you can use with the command :
Code:
fastboot boot recovery.img
You mustn't flash it as you'd flash a normal kernel, as it will brick your phone (it's not a kernel, it's just the recovery!). Until you get a kernel with embedded recovery which works as it ought to,, you can use that for CWM.
I thought Doom's kernel had it embedded and therefore there would be a way to boot into it... obviously I was wrong though haha.
Thanks for the reply!
xanderharris86 said:
I thought Doom's kernel had it embedded and therefore there would be a way to boot into it... obviously I was wrong though haha.
Thanks for the reply!
Click to expand...
Click to collapse
doomlords kernel does, if you are using doomlords kernel, power the device off, when off press the power button to turn on, then keep tapping back till the device boots into recovery..... but like Logseman becareful AND DO NOT FLASH BINARYS RECOVERY.IMG
xanderharris86 said:
So I just rooted my phone thanks to Ash and Mills, but now I have an incredibly stupid question to ask about cwm...
what button combo do I have to press in order to access it on the phones start up?
I tried searching the forums, but maybe I missed an obvious post. Don't be too harsh on me!
Click to expand...
Click to collapse
Search these forums for what is called recoveryPLAY.img and you need to fastboot flash that.
The command prompt should be fastboot flash boot recoveryPLAY.img
NO! That is wrong! If he flashes recoveryPLAY.img, he'll brick the phone! Come on, Binary says it himself!!!
http://forum.xda-developers.com/showthread.php?t=1130639
Bin4ry said:
Please DO NOT FLASH! This recovery is designed to work just as recovery, if you flash it to your device it will NOT boot system anymore!
Click to expand...
Click to collapse
Flash recoveryPLAY.img and you will corrupt /boot end up with bad blocks and brick your phone, you've been warned by both of us!
Sent from my R800i using Tapatalk
Never wanna flash CWM. Always ALWAYS boot it. Binary said himself that ur f*cked if you flash it lol.
You aren't f***ed if you flash it, but the only thing then, that will start is the recovery menu !
Already tried it out, it's just because it's an entire "only recovery kernel".

[Q] CWM Online Builder

Has anybody managed to get a working CWM Touch built using the CWM Recovery Builder? I've tried a few times but can't seem to get anything working.
I was thinking that it was something to do with recovery.fstab, but so far, it just seems like the regular stock recovery *SIGH* Guess I'll keep at it later during the week.
masr1979 said:
Has anybody managed to get a working CWM Touch built using the CWM Recovery Builder? I've tried a few times but can't seem to get anything working.
I was thinking that it was something to do with recovery.fstab, but so far, it just seems like the regular stock recovery *SIGH* Guess I'll keep at it later during the week.
Click to expand...
Click to collapse
Well, what happens when you try it? Does it boot into recovery or fail before that point? Or does it work but just no touch? And last...twrp works fine and has touch.
I'll give it a shot tomorrow sometime and see what's up, though zeronull would probably be the guy to contact about a100 recoveries.
Tapatalked from my Galaxy S II.
I'm more of a fan of CWM than TWRP, though I've been using the later for quite a few months. Mostly though it's that itch to mess around with stuff
As far as what was happening, it booted into recovery and after a few secs would show the android with the red warning sign (I'm assuming since it couldn't find the update.zip in the sdcard).
I had considered asking zeronull, yourself, or waydownsouth for some advice, but I figure you guys are doing plenty as it is. As I said, it's not a necessity or anything.
I'll keep at it, when I have some time.
masr1979 said:
I'm more of a fan of CWM than TWRP, though I've been using the later for quite a few months. Mostly though it's that itch to mess around with stuff
As far as what was happening, it booted into recovery and after a few secs would show the android with the red warning sign (I'm assuming since it couldn't find the update.zip in the sdcard).
I had considered asking zeronull, yourself, or waydownsouth for some advice, but I figure you guys are doing plenty as it is. As I said, it's not a necessity or anything.
I'll keep at it, when I have some time.
Click to expand...
Click to collapse
Well zeronull or WDS would be the ones to ask about this kind of stuff, its beyond me really I'm just a script guy. Although are you flashing the recovery to test, or booting recovery off the PC over USB? While you can do it, I recall cwm corrupting sometimes. Not sure if these devices are prone to it or not. Like I said if I get some time I'll mess around and see what I can see.
My most time consuming project hit a wall until I can get ahold of a bricked a100, so I have a little extra time atm.
Tapatalked from my Galaxy S II.
Edit: So I made a working CWM Touch Recovery. At least, it works like it flashes ok, boots fine, and touch works. Didn't test it past that. I even wound up flashing it over boot, so I could only boot into recovery. That was fun. So, if anyone asks, you can flash recovery to boot, and you will always boot into recovery. Win.
I managed to build a CWM Touch Recovery from the CWM 5.5.0.4 Recovery. I was able to wipe, flash.
Flash this only if you already have a working Recovery such as the CWM 5.5.0.4 or TWRP Recovery (meaning you already have ICS firmware installed).
Please test this with caution since I haven't tested all functions.
Download links
CWM Touch Recovery
CWM 5.5.0.4 - if you want to restore to CWM 5.5.0.4
Big thanks to Koush for the Online Recovery Builder
[email protected] said:
I managed to build a CWM Touch Recovery from the CWM 5.5.0.4 Recovery. I was able to wipe, flash.
Flash this only if you already have a working Recovery such as the CWM 5.5.0.4 or TWRP Recovery (meaning you already have ICS firmware installed).
Please test this with caution since I haven't tested all functions.
Download links
CWM Touch Recovery
CWM 5.5.0.4 - if you want to restore to CWM 5.5.0.4
Big thanks to Koush for the Online Recovery Builder
Click to expand...
Click to collapse
Nice. I did it earlier lol I was gonna put it up but xda has been all screwed up most of the day so I can't even reply to posts. I sent him a pm with a link a few hours ago.
For those wondering you can flash it with fast boot.
adb reboot bootloader
once at bootloader
fastboot flash recovery recovery.img
fastboot reboot
This assumes recovery.img is where adb and fast boot are run from otherwise add the folder where it is.
Tapatalked from my Galaxy S II.
pio_masaki said:
...So, if anyone asks, you can flash recovery to boot, and you will always boot into recovery. Win.
Click to expand...
Click to collapse
LOL! there you go, you learn something new everyday
Thanks to both of you for your time.

Don't use TWRP 2.6.3.0 on T989/T989D

First, never use GooManager to flash TWRP, to soft brick your phone is very likely, if soft bricked your phone, you need to use odin to flash TWRP.
Second, don't use TWRP 2.6.3.0 on our T989/T989D, I have found the following problems:
1: in recovery mode - after advanced wipe is done, the "return" button (right bottom corner) it's not sensitive, you need to press a few times to get back to previous screen
2: after flash new ROM, it usually takes at least 30 seconds to reboot the device, you may think your device is powered off, but it is not, just take too long.
3: No usb mount button in mount screen, not sure why, so you cannot mount your phone in recovery mode, you have to use adb to push file.
4: after you flash the ROM successfully, the newly flashed ROM may enter "bootloop" mode, it happened to me many times, same ROM, I have to flash at least 4-5 times to by pass the bootloop.
5: if you are lucky, and your newly flashed ROM booted, you may experience various problems, e.g. reboot, hangs, lag.... etc. Happened to me.
So, you better stick with TWRP 2.6.1.0, however 2.6.1.0 is prefect, it cannot wipe /preload, but at least, it doesn't have the above problems.
brisk5181 said:
First, never use GooManager to flash TWRP, to soft brick your phone is very likely, if soft bricked your phone, you need to use odin to flash TWRP.
Second, don't use TWRP 2.6.3.0 on our T989/T989D, I have found the following problems:
1: in recovery mode - after advanced wipe is done, the "return" button (right bottom corner) it's not sensitive, you need to press a few times to get back to previous screen
2: after flash new ROM, it usually takes at least 30 seconds to reboot the device, you may think your device is powered off, but it is not, just take too long.
3: No usb mount button in mount screen, not sure why, so you cannot mount your phone in recovery mode, you have to use adb to push file.
4: after you flash the ROM successfully, the newly flashed ROM may enter "bootloop" mode, it happened to me many times, same ROM, I have to flash at least 4-5 times to by pass the bootloop.
5: if you are lucky, and your newly flashed ROM booted, you may experience various problems, e.g. reboot, hangs, lag.... etc. Happened to me.
So, you better stick with TWRP 2.6.1.0, however 2.6.1.0 is prefect, it cannot wipe /preload, but at least, it doesn't have the above problems.
Click to expand...
Click to collapse
You can wipe preload in 2.6.1.0 by going to settings and ticking use rm -rf instead of formatting.
The no USB mount is the worst problem for me. I wonder if @Dees_Troy can shed some light on that.
I wonder if there are such issues then why there are more than 1800 hits on 2.6.3? And also if it has issue then why TWRP released it without properly checking it? Im oberserving TWRP is doing this from a long time and infact i have to search on internet to check if latest version is perfect or not
brisk5181 said:
First, never use GooManager to flash TWRP, to soft brick your phone is very likely, if soft bricked your phone, you need to use odin to flash TWRP.
Second, don't use TWRP 2.6.3.0 on our T989/T989D, I have found the following problems:
1: in recovery mode - after advanced wipe is done, the "return" button (right bottom corner) it's not sensitive, you need to press a few times to get back to previous screen
2: after flash new ROM, it usually takes at least 30 seconds to reboot the device, you may think your device is powered off, but it is not, just take too long.
3: No usb mount button in mount screen, not sure why, so you cannot mount your phone in recovery mode, you have to use adb to push file.
4: after you flash the ROM successfully, the newly flashed ROM may enter "bootloop" mode, it happened to me many times, same ROM, I have to flash at least 4-5 times to by pass the bootloop.
5: if you are lucky, and your newly flashed ROM booted, you may experience various problems, e.g. reboot, hangs, lag.... etc. Happened to me.
So, you better stick with TWRP 2.6.1.0, however 2.6.1.0 is prefect, it cannot wipe /preload, but at least, it doesn't have the above problems.
Click to expand...
Click to collapse
When you re-flashed several times for the new ROM, did you do a wipe everytime? or did you just re install??
HQuser said:
I wonder if there are such issues then why there are more than 1800 hits on 2.6.3? And also if it has issue then why TWRP released it without properly checking it? Im oberserving TWRP is doing this from a long time and infact i have to search on internet to check if latest version is perfect or not
Click to expand...
Click to collapse
There's plenty of documented issues with it....maybe for some devices its fine, but not all devices seem to be created equal.
Why is twrp doing nothing about it....probably because our aging device is under their radar, or they just aren't concerned with a few people with issues. Again....it may be flawless on every other device, so they aren't concerned with our old phone.
That's my guess.
Battery problems? No matter the rom or android version.... >>>> http://forum.xda-developers.com/showthread.php?t=2461864
I have had these same problems, but thy only started when I flashed 4.3. That is slim bean and paranoid android. It will boot after the flash, bit any attempt to reboot after that is met with a boot loop.
Thing is, I don't remember which version of TWRP I am using, and I would like to avoid rebooting since I don't want to reflash just yet. Is there a way to check on the version without a reboot? I know a reflash is inevitable if I want to install another version of TWRP.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Johndoe9990 said:
I have had these same problems, but thy only started when I flashed 4.3. That is slim bean and paranoid android. It will boot after the flash, bit any attempt to reboot after that is met with a boot loop.
Thing is, I don't remember which version of TWRP I am using, and I would like to avoid rebooting since I don't want to reflash just yet. Is there a way to check on the version without a reboot? I know a reflash is inevitable if I want to install another version of TWRP.
Click to expand...
Click to collapse
I can confirm that TWRP 2.6.1.0 causes no bootloop after flashing a ROM.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Where do I find a ODIN flashable file of the 2.6.1.0? I'm new to the Samsung side of things. I have looked all over and all I find at Goo and TWRP sites as .img and .tar files. I know .img files have to use dd to use now is the .tar files can be used with Odin? If so please let me know don't want to brick my new / used S2.
michaelcrossland said:
Where do I find a ODIN flashable file of the 2.6.1.0? I'm new to the Samsung side of things. I have looked all over and all I find at Goo and TWRP sites as .img and .tar files. I know .img files have to use dd to use now is the .tar files can be used with Odin? If so please let me know don't want to brick my new / used S2.
Click to expand...
Click to collapse
Yes, the tar files are for Odin.

Cant boot into recovery

Hey guys, new to the forum and am looking for some guidance here. I've had my LGOG going great with CM11 and one day I put it on the charger when the battery got down to 1%. The next morning I grabbed my phone and it was off and refused to turn on. I was able to get it on by holding volume up + power and plugging it into a charger or PC but only when it was plugged in. I replaced the battery already to rule that part out. So now i've followed this guide and everything went fine,I flashed Teenybin SBLunlockhttp://forum.xda-developers.com/showthread.php?t=2230106. Only thing is for some reason i cannot boot into recovery mode, fastboot and download mode work fine but when i choose recovery from fastboot the phone shows a google logo and a small lock on the bottom of the screen and then turns off and show's the charging icon. I've been at it for hours and cannot get into recovery to flash a new rom.
My question for yall is am I wasting my time with this? I'm still not convinced that this is not a hardware failure since nothing on the phone works unless plugged into power. Any thoughts would help a ton otherwise i'll have to just cough up the cash for a new one. Thanks in advance guys.
Nex
nextelhalo said:
Hey guys, new to the forum and am looking for some guidance here. I've had my LGOG going great with CM11 and one day I put it on the charger when the battery got down to 1%. The next morning I grabbed my phone and it was off and refused to turn on. I was able to get it on by holding volume up + power and plugging it into a charger or PC but only when it was plugged in. I replaced the battery already to rule that part out. So now i've followed this guide and everything went fine,I flashed Teenybin SBLunlockhttp://forum.xda-developers.com/showthread.php?t=2230106. Only thing is for some reason i cannot boot into recovery mode, fastboot and download mode work fine but when i choose recovery from fastboot the phone shows a google logo and a small lock on the bottom of the screen and then turns off and show's the charging icon. I've been at it for hours and cannot get into recovery to flash a new rom.
My question for yall is am I wasting my time with this? I'm still not convinced that this is not a hardware failure since nothing on the phone works unless plugged into power. Any thoughts would help a ton otherwise i'll have to just cough up the cash for a new one. Thanks in advance guys.
Nex
Click to expand...
Click to collapse
Your battery was probably fine so I would keep it around. That just seems to happen sometimes.
The recovery that teenybins installs is not CM11 compatable. So you need to install a KK recovery, or ADB sideload a Stockish ROM.
For ADB sideload to install a Stockish Rom go here. http://forum.xda-developers.com/showthread.php?p=36270473
To install a recovery through fastboot, DL it from here. http://downloads.codefi.re/shelnutt2/freegee/LG-LS970/ These are for KK
And to install it using fastboot.
fastboot erase recovery
fastboot flash recovery recovery.img
You may need to do a factory reset to get it to boot.
---------- Post added at 06:06 AM ---------- Previous post was at 05:56 AM ----------
Forgot to tell ya, just pull the recovery image from the zip and use it with fastboot.
engine95 said:
Your battery was probably fine so I would keep it around. That just seems to happen sometimes.
The recovery that teenybins installs is not CM11 compatable. So you need to install a KK recovery, or ADB sideload a Stockish ROM.
For ADB sideload to install a Stockish Rom go here. http://forum.xda-developers.com/showthread.php?p=36270473
To install a recovery through fastboot, DL it from here. http://downloads.codefi.re/shelnutt2/freegee/LG-LS970/ These are for KK
And to install it using fastboot.
fastboot erase recovery
fastboot flash recovery recovery.img
You may need to do a factory reset to get it to boot.
---------- Post added at 06:06 AM ---------- Previous post was at 05:56 AM ----------
Forgot to tell ya, just pull the recovery image from the zip and use it with fastboot.
Click to expand...
Click to collapse
Thanks for the reply, this helped me get along with ADB and SDK but i'm still not clear on it. I've got the recovery image needed and ADB running but not sure how to flash the recovery image to the phone. I tried following the guide in the link you provided but it wants you to get into recovery mode on the phone and enable ADB mode but I cant get into my recovery on the phone. Problem. Again though thanks for you help, much appreciated. This learning process brings me back to my days of modding the old Xbox.
So just thinking about your last post, did you recommend installing a stock rom first and then try to install the new recovery image? I am able to put the phone into download mode and i've used LGNPST to push a full stock ZVB rom to it, seemed to work but I didnt know if that was the right way to go and flashed the Teenybin SBL unlock again.
nextelhalo said:
Thanks for the reply, this helped me get along with ADB and SDK but i'm still not clear on it. I've got the recovery image needed and ADB running but not sure how to flash the recovery image to the phone. I tried following the guide in the link you provided but it wants you to get into recovery mode on the phone and enable ADB mode but I cant get into my recovery on the phone. Problem. Again though thanks for you help, much appreciated. This learning process brings me back to my days of modding the old Xbox.
So just thinking about your last post, did you recommend installing a stock rom first and then try to install the new recovery image? I am able to put the phone into download mode and i've used LGNPST to push a full stock ZVB rom to it, seemed to work but I didnt know if that was the right way to go and flashed the Teenybin SBL unlock again.
Click to expand...
Click to collapse
You said you had fastboot. So you can use fastboot to load the kk recovery using those commands. If unsure just google it. Lots of info on fastboot.
As for sideload that was just to get a stock ROM on your SD.
If you lgnpst zvb then your phone should boot up and needs to update to zvc before you do anything else.
But if you flashed teenybins then you should have recovery and be able to flash the kk recovery. Power+ vol up gets recovery. Dn twice on vol button, then power gets you to recovery.
Check the FAQ and root guide. All this info is in there if it's confusing.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
You said you had fastboot. So you can use fastboot to load the kk recovery using those commands. If unsure just google it. Lots of info on fastboot.
As for sideload that was just to get a stock ROM on your SD.
If you lgnpst zvb then your phone should boot up and needs to update to zvc before you do anything else.
But if you flashed teenybins then you should have recovery and be able to flash the kk recovery. Power+ vol up gets recovery. Dn twice on vol button, then power gets you to recovery.
Check the FAQ and root guide. All this info is in there if it's confusing.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I got ya, so I'm making sense of it all after a bit and I have more info if it helps. I've been able to get ZVB on there (via LGNPST) and i'll update to ZV9 just in case yet no matter what i do i cannot get recovery to boot. I get into fastboot and choose Recovery ( locked and unlocked) but when i hit the power button to choose recovery I get nothing, it shuts down. I'll keep at it and give a progress report if I make any.
UPDATE: Ok so I can only access (on phone) Fastboot when i flash one of the Teenybin files. The stock ZV9 and ZVB just show me the LG logo and go back to the battery icon. So, I flashed teenybin SBL unlock again got the phone into fastboot. I opened a terminal on my PC with ADB running and my phone in Fastboot connected to my PC (LG Drivers installed). When i choose adb sideload recovery.img and it says "device not found". Still working on it but havent gotten past this yet.
Im still wondering if there is hardware failure since I flashed ZVB and the phone still will not boot up period unless it's connected to PC/charger.
Do this then. Grab the zvc bin from the root guide. That is the most current and it has the right modem. Zvb and zv9 have the wrong modem.
Also it sounds like you have stock recovery. Which you will if your using zv? bins.
Then after using zvc bin, use teeny bin. That'll get you to twrp recovery. In twrp flash the kk recovery and you should be good to go.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
Do this then. Grab the zvc bin from the root guide. That is the most current and it has the right modem. Zvb and zv9 have the wrong modem.
Also it sounds like you have stock recovery. Which you will if your using zv? bins.
Then after using zvc bin, use teeny bin. That'll get you to twrp recovery. In twrp flash the kk recovery and you should be good to go.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Gave it a shot, flashed ZVC and then after that did Teenybin SBL unlock and same thing. I get it into fastboot, choose recovery and then the phone show's a google logo with alittle lock on the bottom and then goes to black screen then to charging icon. :silly: I'll keep at it.
Update, a friend gave me some help and I was able to flash the recovery image you linked to me via ADB but still no change in the phone. On teenybin in fastboot, select recovery and still get the same google logo and small lock, then goes to power screen.
Haha, seems you've been down this road before. Found this while searching around, I'm giong to try the steps in the last two post's of the thread. Thanks for the help Engine.
http://forum.xda-developers.com/showthread.php?t=2535874&page=3
UPDATE: unfortunately no change, left the phone on the charger for a few hours but still stuck with no usable recovery mode and phone only responds while plugged in. Think i'll chalk this up to some type of hardware failure.
Will your phone even boot to the stock ROM? If it does, try installing Quickboot from the PlayStore. See if that'll get you into recovery.
I can't remember if it's in the root guide or the FAQ, but I posted another option for a battery issue like yours. Try it and see if it'll do more.
There's some commands that'll wipe through adb. I'll see if I can find them.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Wont boot into stock Rom yet, man i wish i was that far along and i'd be done probably. Thanks for looking at it for me.
nextelhalo said:
Wont boot into stock Rom yet, man i wish i was that far along and i'd be done probably. Thanks for looking at it for me.
Click to expand...
Click to collapse
There's something we're missing here, so lets start at the beginning
LGNPST ZVC again. This SHOULD get you going.
Now you will have stock recovery. To enter stock recovery, press vol down+power The LG logo will come on, then the capacitive lights. Immediately let go when the capacitive lights turn on. It takes a few seconds to work. And maybe a few tries to get it.
IF that all happens, then in stock recovery, do a Factory reset. IT WILL WIPE YOUR SD/INTERNAL STORAGE!!
Now your phone should boot up to stock ROM.
If that doesn't work, go to ADB and issue these:
adb shell
"dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/cache"
adb shell
"dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/userdata"
These will zero out /cache and /data
Reboot your phone and it should boot up
If not, you may need to LGNPST ZVC one more time and you should be good to go
If no dice again, you might need to try a battery pull, which you should know seeing as how you replaced the battery.
That's about all I got....you could also try getting on the irc and see if someone there has more idea's
Good luck! :fingers-crossed:
Edit: I forgot to tell you that in Stock recovery, use the capacitive menu key to select. The Power button doesn't do it in Stock recovery. Menu is the bottom right of the display and I don't think it's lit, but I'm not sure.
Thank you sir, i'll give this a shot tonight when i get back home. I'll keep my fingers crossed but i've located another LGOG on Craigslist for 80$, might not be able to pass up that deal.
Update: still no go, I agree there is something missing here. When i flash ZVC all goes like it should but the phone still just flatout wont do anything unless on external power. I went ahead and did a battery pull but no change. It's like we're doing everything correctly here but it wont let us past fastboot or download mode. Either it's software or this thing may have fried. I'm going to bring it to a friend here in town and see what he can do, he's a guru in this department but I wanted to figure this out on my own. If we get this back up and running I will for sure update this thread, hopefully it can help some folks out there. Thanks again for the help Engine, I wont give up until i know exactly what happened and i'll pass it along.

Does anyone have a Nandroid Backup I could Use for the Z00AD?

Hey all, little embarrassing coming here for this, but I'm in a little bit of a jam. I'm new to flashing custom ROMs, and I was trying to flash my first today, and managed to screw everything up in the process. I can boot into Clockwork mod via my PC, and I can still do everything I need to from there, but I was stupid, and didn't make a Nandroid backup before doing so. So I was wondering if anyone here could lend me theirs that I could slap onto an SD card, and recover my phone with. Any help would be appreciated.
EDIT: Just so we're clear, this isn't an attempt to get personal information. I will take any backups you have, with or without an unlocked bootloader, with or without rooting, with or without custom ROM, anything. Heck, I'd prefer to have it as close to stock as possible, so I can do everything myself. I just need a bit of a bailout here.
Shameful self-bump. I could still really use some help here.
fastboot flash stock recovery
adb side load latest firmware in stock recovery
enjoy
timbernot said:
fastboot flash stock recovery
adb side load latest firmware in stock recovery
enjoy
Click to expand...
Click to collapse
That's a little hard to do when the device isn't recognized by my PC, and I can't get it to boot into any recovery that isn't Clockwork mod via my PC.
Misinko said:
That's a little hard to do when the device isn't recognized by my PC, and I can't get it to boot into any recovery that isn't Clockwork mod via my PC.
Click to expand...
Click to collapse
how do you boot into Clockwork Mod via your pc when the device isn't recognized by your pc?
tabletalker7 said:
how do you boot into Clockwork Mod via your pc when the device isn't recognized by your pc?
Click to expand...
Click to collapse
EDIT: Nevermind, seems I ADB recognizes the device with CWM running. Now I gotta see where to go from there.
Now I've encountered problem number 2: I didn't allow USB debugging for the computer I'm using (USB debugging is ticked in the settings [or at least I think it is], but it's not authorized for my PC). So here's the question: Can I authorize it through Minimal ADB and Fastboot?
Triple post, but it's with a question. I'm nearly positive that this whole ordeal is going on because I tried to boot into recovery mode with the TWRP app when no recovery was available. So now the question is, is there any way I can stop the phone from trying to boot into recovery so I can install a proper one?
Turn it off, then press volume up + power when vibrates, release power while holding volume up, then release volume up as well, it should boot into bootloader where you can fastboot a new recovery.
fastmix said:
Turn it off, then press volume up + power when vibrates, release power while holding volume up, then release volume up as well, it should boot into bootloader where you can fastboot a new recovery.
Click to expand...
Click to collapse
Tried that. Doesn't work. Like I said, it keeps booting into the psudo-recovery mode thing. I can't even boot into the bootloader from there.
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
that will help you - besides if you are silly enough to think anyone will just give you something like a backup, come on man, I am dumb but even I am not that dumb
Have u tried to boot into Fastboot from your Cm recovery? If not, there is a way to make the stock firmware flushable by twrp or cm recovery. I don't feel like typing the whole process but if u look around the forum for a sec u should find it pretty easily. Once u do that, everything will be factory again.
Sent from my Z00D using XDA-Developers mobile app
jflow36 said:
Have u tried to boot into Fastboot from your Cm recovery? If not, there is a way to make the stock firmware flushable by twrp or cm recovery. I don't feel like typing the whole process but if u look around the forum for a sec u should find it pretty easily. Once u do that, everything will be factory again.
Click to expand...
Click to collapse
I have tried booting from CWM, but TWRP overrides it still. I'll look into flashing stock firmware through CWM though.

Categories

Resources