Formated my SD Card now I am stuck! - Ouya Q&A, Help & Troubleshooting

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:

Related

stuck after wiping

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

Bricked ZL550 - Any ideas?

I bricked my U.S. market ZL550 Zenfone 2. My bad, I spent the last two weeks desperately trying everything I could think of to get Link2SD to mount an Ext2 or 4 partition on my SDXC card, and I wasn't at all surprised when it hung on the Asus logo while booting on Saturday.
Anyway, I can't get it to boot normally again. Using fastboot, I flashed recovery, boot and droidboot from the latest Asus ROM, Z008-WW-2.18.40.7, but when I try to flash the system image zip, I get a bunch of errors and a "fail" message on the phone.
I tried sideloading the image with adb but adb won't connect to the phone in recovery mode. Also tried copying the image zip to the SD Card but that wouldn't load, it would only look for MOFD_SDUPDATE.ZIP.
I can return it, I'm not exactly thrilled with it anyway. Anyone have any ideas of what I might try before sending it back?
Thanks! Carl
ConnCarl said:
I bricked my U.S. market ZL551 Zenfone 2. My bad, I spent the last two weeks desperately trying everything I could think of to get Link2SD to mount an Ext2 or 4 partition on my SDXC card, and I wasn't at all surprised when it hung on the Asus logo while booting on Saturday.
Anyway, I can't get it to boot normally again. Using fastboot, I flashed recovery, boot and droidboot from the latest Asus ROM, Z008-WW-2.18.40.7, but when I try to flash the system image zip, I get a bunch of errors and a "fail" message on the phone.
I tried sideloading the image with adb but adb won't connect to the phone in recovery mode. Also tried copying the image zip to the SD Card but that wouldn't load, it would only look for MOFD_SDUPDATE.ZIP.
I can return it, I'm not exactly thrilled with it anyway. Anyone have any ideas of what I might try before sending it back?
Thanks! Carl
Click to expand...
Click to collapse
I'm surprised!! Why do you need link2sd??? with 32 GB Internal, I have 118 Apps installed along with movies and music. Still I have space( I have not used SD Card).
Anyways,
From what you mentioned, you seem to have a ZE551ML. And you Installed Z008-WW-2.18.40.7. It should be Z00A and not Z008. Please download the correct firmware and try out.:good:
Thumb-rule,
ZE550ML = Z008
ZE551ML = Z00A
I guess thats what you did Wrong
Thanks for pointing that out! It's actually a 16GB 550.
I'd go and connect it to pc on fastboot and wipe everything via command. Ex. Fastboot erase system, data, cache. Then flash a stock Rom from Asus via adb sideload
ConnCarl said:
Thanks for pointing that out! It's actually a 16GB 550.
Click to expand...
Click to collapse
for MOFD_SDUPDATE.zip to work, you need to place it on the external sd card and reboot into recovery. It will automatically start to install.
Placing it on the Internal card wont help.
---------- Post added at 08:58 AM ---------- Previous post was at 08:57 AM ----------
lordpipa said:
I'd go and connect it to pc on fastboot and wipe everything via command. Ex. Fastboot erase system, data, cache. Then flash a stock Rom from Asus via adb sideload
Click to expand...
Click to collapse
I wouldnt recommend that.
He is unable to use adb properly. And if he messes up something, he might even lose his warranty
lordpipa said:
I'd go and connect it to pc on fastboot and wipe everything via command. Ex. Fastboot erase system, data, cache. Then flash a stock Rom from Asus via adb sideload
Click to expand...
Click to collapse
Tried all that. Many times.
ConnCarl said:
Tried all that. Many times.
Click to expand...
Click to collapse
When i restored from stock via ADB, I was going from a preroot, bricked, because I updated and was getting the little error bot.. After i sideload the image, i still had to factory reset. I'm just guessing, but you did try and do the factory reset after fastboot/ADB.
godgib said:
When i restored from stock via ADB, I was going from a preroot, bricked, because I updated and was getting the little error bot.. After i sideload the image, i still had to factory reset. I'm just guessing, but you did try and do the factory reset after fastboot/ADB.
Click to expand...
Click to collapse
I can't sideload the image, because I can't connect with ADB.
ConnCarl said:
I can't sideload the image, because I can't connect with ADB.
Click to expand...
Click to collapse
but you can get into recovery, it's just when you click on "ADB update" your computer doesn't see the phone, that's my understanding...
Right, correct. I can get into recovery, and fastboot works, but not ADB.
ConnCarl said:
Right, correct. I can get into recovery, and fastboot works, but not ADB.
Click to expand...
Click to collapse
It sounds like you still in fastboot and not recovery. This is what recovery looks like and then you put in it "Apply update ADB sideload."
{
"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"
}
Yep, that is exactly what it looks like. But when I try to sideload, it times out. ADB won't see the phone.
ConnCarl said:
Yep, that is exactly what it looks like. But when I try to sideload, it times out. ADB won't see the phone.
Click to expand...
Click to collapse
I'm pretty sure if it timse out using ADB sideload then it should also timeout when you type ADB deviecs, but try it you should see your serial number sideload.... If you don't then
1. Make sure you have ADB 1.42 with intel drives 1.9
2. Use the stock cable.
3. In device manager make sure there's no unknown Android devices.
4. if ADB still doesn't work then try and flash via fast boot a new boot.img and recovery.img.
5. If you do get to the point where you can sideload...
6. Downloaded the ASUS firmware with WW not CN.
7. Also make sure the firmware package doesn't have ext .zip.zip, because of unknown file ext in windows.
Not sure if this works but you can give it a try.
Have you boot it with Temp CWM?
Delete all cache, including those of under advanced section
install zip file should work to install your full rom. since you stated you cant adb to detect.
Thanks everyone for all the suggestions!
I was just sort of reviewing godgib's screen grab when it slowly dawned on me that at least part of the solution had been staring me in the face all along.
It had never occurred to me that adb might not be able to connect even though fastboot could. Then when I read "you need adb 1.0.32 or newer to sideload to this device", it started to make sense. I upgraded adb and connected but still couldn't sideload. After reviewing godgib's methodical list, I realized it was a driver problem. Once I squared that away, sideload went without a hitch.
Interesting side note...I don't know what build I had originally, but it had to be at least a month old or so. I figured I might as well get the latest release, so I went with Z008_WW_2.18.40.7, and I updated boot/droidboot/recovery while I was at it. The funny thing was that when it booted, it was set for 250 dpi and everything was tiny.
Luckily, since adb was finally working (thanks again godgib) I was able to send "adb shell wm density 480" to put it back to normal.
Thanks again, everyone!
Carl
Glad you got it working...
Sent from my ASUS_Z00AD using XDA Free mobile app
godgib said:
Glad you got it working...
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse
Appreciate that.
Of course now auto-rotate is borked. I'll have to either wait for a patch or downgrade.
Did you ever figure out the sdcard problem? I just got the same card and want to do the same thing. But the phone wont see the second partition at all.
i have similar problem too

HELP: I accidentally wiped OS off my phone in TWRP

I'm a newbie with this.. I got my Nexus 5x a few weeks ago. With the instruction of someone else i unlocked the boot loader and rooted my phone. then i had an issue with boot looping after some customization on my phone. so i attempted to wipe all that stuff off my phone is TWRP and i accidentally checked system. Now what do i do? Now i don't really know what a rom is or adb side loader or something like that.. i need some simple and clear instructions to get my phone working again. preferably without having to root all over again (that was exhausting and quite difficult, lots of trial and error).. but if it won't be rooted anymore, it's better than nothing. Please help!!
starlitserenity said:
I'm a newbie with this.. I got my Nexus 5x a few weeks ago. With the instruction of someone else i unlocked the boot loader and rooted my phone. then i had an issue with boot looping after some customization on my phone. so i attempted to wipe all that stuff off my phone is TWRP and i accidentally checked system. Now what do i do? Now i don't really know what a rom is or adb side loader or something like that.. i need some simple and clear instructions to get my phone working again. preferably without having to root all over again (that was exhausting and quite difficult, lots of trial and error).. but if it won't be rooted anymore, it's better than nothing. Please help!!
Click to expand...
Click to collapse
just copy some rom , twrp can access mtp
Apayah said:
just copy some rom , twrp can access mtp
Click to expand...
Click to collapse
again , i dont know what a rom is or where to find one and i have no idea what mtp is.
starlitserenity said:
again , i dont know what a rom is or where to find one and i have no idea what mtp is.
Click to expand...
Click to collapse
when you in twrp , just plug it into your pc
starlitserenity said:
I'm a newbie with this.. I got my Nexus 5x a few weeks ago. With the instruction of someone else i unlocked the boot loader and rooted my phone. then i had an issue with boot looping after some customization on my phone. so i attempted to wipe all that stuff off my phone is TWRP and i accidentally checked system. Now what do i do? Now i don't really know what a rom is or adb side loader or something like that.. i need some simple and clear instructions to get my phone working again. preferably without having to root all over again (that was exhausting and quite difficult, lots of trial and error).. but if it won't be rooted anymore, it's better than nothing. Please help!!
Click to expand...
Click to collapse
Heinsbergs guide here describes how to return to stock
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Scroll down to "10. How To Flash The Factory Images (And Return To Stock)"
Darke5tShad0w said:
Heinsbergs guide here describes how to return to stock
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Scroll down to "10. How To Flash The Factory Images (And Return To Stock)"
Click to expand...
Click to collapse
again, i cant do that . my OS is completely wiped. i went to #10 - the instructions cant be followed, i cant get onto my phone except into twrp.
Apayah said:
when you in twrp , just plug it into your pc
Click to expand...
Click to collapse
when i connect my phone to my computer and am in twrp, then what?
starlitserenity said:
again, i cant do that . my OS is completely wiped. i went to #10 - the instructions cant be followed, i cant get onto my phone except into twrp.
Click to expand...
Click to collapse
You only removed system you should still be able to get into bootloader.
Turn phone off, hold the volume down button then power button.
Should go to a screen with a android man laying down and it saying fastboot mode in red.
Darke5tShad0w said:
You only removed system you should still be able to get into bootloader.
Turn phone off, hold the volume down button then power button.
Should go to a screen with a android man laying down and it saying fastboot mode in red.
Click to expand...
Click to collapse
then what? the instructions are too complicated for me :S and i dont understand most of the terms
starlitserenity said:
then what? the instructions are too complicated for me :S and i dont understand most of the terms
Click to expand...
Click to collapse
You are now in fastboot mode and bootloader is still unlocked?
Download and install this http://www.wugfresh.com/nrt/
Wait for it to load the try auto detect on the window that pops up, if that doesn't work select "nexus 5x" and then on the next one choose the one ending with "mhc19q" click next/continue.
then on the next window click download and update all dependances.
What for it to do its thing then on the next window click on "flash stock + unroot", click ok,
{
"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"
}
then ok. It will download the latest factory image and do its thing. What happens after this you will need to describe to me as I have not used this toolkit.
@starlitserenity, I can help you get an OS back onto your phone. It's very simple even though you may be a NOOB. It's OK. As long as you have access to a PC and Internet you are OK because you can still access TWRP. Here is a list of steps:
1) go to forum.xda-developers.com/nexus-5x/development
2) scroll down to the ROM labeled
"Pure Nexus"
3)In the first post (Original Post), scroll down and click on "Downloads & Changelog" You will be redirected to AFH (Android File Host) to download the ROM/OS
4)Scroll down just a little and you will see a Green Box with files/ROMs. Click on the newest one labeled
pure_Nexus_bullhead-6.0.1-20160407.
After you click on the ROM file, a new screen will appear with a Green Box that says "Begin Download".
5) Click on " Begin Download"
Once you click the "Begin Download" box, you will see below another Green Box that says "primary download". Click on the " Primary Download " box to begin downloading your new ROM/OS.
6) Go back to the Pure Nexus original post/first post and click on the link labeled "Highly Suggested Gapps"
You will be redirected to Android File Host again to download your Gapps(GoogleApps). Scroll down just a little to the Green Box again and select
PureNexus_Dynamic_Gapps_6.x.x_4-7-16.zip and click on the link.
7) A new screen will appear with a Green Box that says "Begin Download"
Click on the "Begin Download" box and just below another Green Box will appear that says "primary download".
Click on the " primary download " and this will download you Gapps.
8) Once both of your files have finished downloading onto your PC, boot your 5x into TWRP and connect it to your PC and let the drivers install so your Nexus is recognized by your PC.
9) Now that your 5x is recognized by your PC while booted into TWRP, you will need to move the 2 downloaded files from your PC's download folder to the internal storage of your 5x.
10) Now that you have moved both downloaded files to your Nexus 5x internal storage you will need to reboot your recovery. Select the home button in TWRP, select reboot, then select reboot recovery to reboot TWRP. This will all TWRP to recognize the two new files that were moved to your Nexus internal storage.
11) Unplug your Nexus from your PC. On your device, go to the TWRP home screen and select wipe, then swipe to factory reset. Now you are ready to install your new ROM and Gapps
12) Now that you have wiped the 5z again, select the TWRP home button. Next, select "Install". Navigate to your SD card/internal storage to locate the two files we moved to your Nexus from your PC. Select the file that says
pure_nexus_bullhead-6.0.1-20160407
Once selected you will be directed to a new TWRP screen and you will see a box to click on that says " Add More Zips" Click this box and navigate to the SD card/internal storage and select the 2nd file that says PureNexus_Dynamic_GApps_6.x.x_4-7-16.zip. Once you have selected the file you will be directed to another TWRP screen with a swipe button to install the ROM file and the Gapps file. Swipe the button to begin the installation.
13) Once the installation is complete, you will see a box that says wipe cache/dalvik. Select this box, wipe cache/dalvik, then select reboot system.
14) Once your device boots you will proceed to the setup wizard just like when your Nexus 5x was new out of the box. Go through the setup wizard to setup your device and once completed, reboot, and you will be back to normal with a pretty sweet custom ROM called Pure Nexus.
Sent from my Nexus 6 using XDA-Developers mobile app
-__-
Use power+volume button. You will get thishttp://www.androidcentral.com/sites/androidcentral.com/files/styles/large_wm_brw/public/article_images/2014/11/nexus-manual-update-01.jpg?itok=wEfVvztj.
Then flash nexus factory images. and go stock. You can skip flashing recovery or you can flash recovery again. You will lose root access. you have to flash supersu again
Update? We're you able to install a new ROM and get your 5x back up and running?
Sent from my Nexus 6 using XDA-Developers mobile app

Question Xiaomi K40 Became A Brick

Hi peeps, my Xiaomi K40 now became a brick because it can't be installed any ROM, I've tried using TWRP and also mi flash tool but nothing helps.
When using TWRP I've tried two methods:
1/ adb sideload
2/ Install from a zip file which is pushed to device using adb push command(because now the device doesn't have any OS)
But in both cases it shown:
Failed to mount '/system_root' (Block device required)
Failed to mount '/system_ext' (Block device required)
Failed to mount '/product' (Block device required)
Failed to mount '/vendor' (Block device required)
Failed to mount '/odm' (Block device required)
Click to expand...
Click to collapse
I've also tried to wipe all data using Advance Wipe option to repair the partition but no hope.
Any one has solution for this case? thanks in advance!
Flash your device in EDL mode.
Please refer to the post below on how to bypass edl mode authentication.
[GUIDE] How to bypass authentication and flash in EDL with NO auth for FREE!​
Thanks to VD171 for his post.
I think your device is having a Snapdragon Chipset. Sorry but you may try to search on google for contact to person who has authorised edl account to flash a Snapdragon based phone.
Learn more about it in this video
reborn2020 said:
Hi peeps, my Xiaomi K40 now became a brick because it can't be installed any ROM, I've tried using TWRP and also mi flash tool but nothing helps.
When using TWRP I've tried two methods:
1/ adb sideload
2/ Install from a zip file which is pushed to device using adb push command(because now the device doesn't have any OS)
But in both cases it shown:
I've also tried to wipe all data using Advance Wipe option to repair the partition but no hope.
Any one has solution for this case? thanks in advance!
Click to expand...
Click to collapse
do you still have your fastboot mode on your phone?
mvikrant97 said:
Learn more about it in this video
Click to expand...
Click to collapse
Mi flash didn't recognized my phone.
khazzey said:
do you still have your fastboot mode on your phone?
Click to expand...
Click to collapse
Yes I do.
no bypass for STUCKDRAGON devices for EDL Mode so sad the phone became literally bricked
reborn2020 said:
Mi flash didn't recognized my phone.
Yes I do.
Click to expand...
Click to collapse
listen to me, first if you are on windows 10 you should disable driver signature enforcement on your pc search it on google after disabling you should restart your pc, next step is to install xiaomi flash tool latest (02262021) version after installing the software open it, at the right upper of the software you will see drivers click it and click install after installing, reboot your phone into fastboot mode using volume down and power button, connect your phone to pc and click refresh on xiaomi flash tool if you're phone is detected please come back here let me know
khazzey said:
listen to me, first if you are on windows 10 you should disable driver signature enforcement on your pc search it on google after disabling you should restart your pc, next step is to install xiaomi flash tool latest (02262021) version after installing the software open it, at the right upper of the software you will see drivers click it and click install after installing, reboot your phone into fastboot mode using volume down and power button, connect your phone to pc and click refresh on xiaomi flash tool if you're phone is detected please come back here let me know
Click to expand...
Click to collapse
I did this before but no hope, I don't know if the problem is I'm using a macbook and run windows 10 via bootcamp, I don't have an actual windows computer.
P.S, I upload the latest status.
{
"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"
}
last week I was in a similar situation like yours just twrp and all partition screwed up.
well what saved me was to put dot os 5.2 on a USB c pen drive and then simply installing it from trwp (choosing USB pen as source) after literally 5-10 minutes phones came back to life.
let me know if it works for you.
also if twrp throws any error during installation just ignore them for me after flash completed phone booted just fine
ale82to said:
last week I was in a similar situation like yours just twrp and all partition screwed up.
well what saved me was to put dot os 5.2 on a USB c pen drive and then simply installing it from trwp (choosing USB pen as source) after literally 5-10 minutes phones came back to life.
let me know if it works for you.
also if twrp throws any error during installation just ignore them for me after flash completed phone booted just fine
Click to expand...
Click to collapse
I put a miui rom in a usb type c then connect into my phone, then boot into TWRP, and in Install option, I didn't see any option likes "USB pen"
reborn2020 said:
I put a miui rom in a usb type c then connect into my phone, then boot into TWRP, and in Install option, I didn't see any option likes "USB pen"
Click to expand...
Click to collapse
I said USB pen to make sure you choose it from TWRP install I think the righ name is external storage or something similar anyway it seems you are doing things the right way I am quite sure u ll bring phone back to life.
I think muiu room is just fine, should it fails try crDroid or dot os (do not try arrow or lineage)
Bruh I have a very simple solution I guess it might help you
Well first update to latest official twrp custom recovey for your device then
Navigate to Wipe
advance Wipe
Select data and choose Repair or Change File System
Press Repair File System to see if this fixes the issue. If not, continue.
Press Change File System, choose Ext2, and swipe to confirm.
now switch back to Ext4 and swipe to confirm.
i hope this might help you BTW then flash your first custom rom using a sd card or usb if succeeded then flash every stuff as usual
Anurag3100 said:
Bruh I have a very simple solution I guess it might help you
Well first update to latest official twrp custom recovey for your device then
Navigate to Wipe
advance Wipe
Select data and choose Repair or Change File System
Press Repair File System to see if this fixes the issue. If not, continue.
Press Change File System, choose Ext2, and swipe to confirm.
now switch back to Ext4 and swipe to confirm.
i hope this might help you BTW then flash your first custom rom using a sd card or usb if succeeded then flash every stuff as usual
Click to expand...
Click to collapse
Thanks, I've tried this before, unfortunately still can't solve my problem. Finally I decided to bring my phone to a technician.
Try fastboot erase userdata in cmd after taking your device to fastboot mode
Kinda check different twrp I think your twrp is having any problems plz flash your twrp once again
I hope this will surely work for you my friend.
reborn2020 said:
Thanks, I've tried this before, unfortunately still can't solve my problem. Finally I decided to bring my phone to a ttechnic
Click to expand...
Click to collapse
Bro try different formats then change to Ext4 well try this twrp https://dl.twrp.me/alioth/twrp-3.6.0_11-0-alioth.img.html umm i hope this will help you out completely.
if you still have your fastboot mode (turn off then hold power + vol. down), you should check your pc driver if adb and fastboot driver installed properly, then try flashing stock rom (dont relock your bootloader), I think what cause the brick is encrypted storage that get accessed by twrp, even if you decrypt it using password, you can still brick the phone by manually mount some partition in twrp
Thank you all of your help, peeps. Finally I solved my problem by the help of a technician. Because only technician has access to Xiaomi internal tools, these are "Hardware-Level" which could help in these cases.
He
reborn2020 said:
Thank you all of your help, peeps. Finally I solved my problem by the help of a technician. Because only technician has access to Xiaomi internal tools, these are "Hardware-Level" which could help in these cases.
Click to expand...
Click to collapse
Hello, glad you solved your issue, but can you please explain briefly how hardware was bricked since you were already able to reach fastboot & twrp? Since it's known that when you can boot to fastboot, it's a softbrick
Alipk52 said:
He
Hello, glad you solved your issue, but can you please explain briefly how hardware was bricked since you were already able to reach fastboot & twrp? Since it's known that when you can boot to fastboot, it's a softbrick
Click to expand...
Click to collapse
I can boot to fastboot but I can't do anything with fastboot becuase I wiped out anything on my phone include "firmware" maybe, I don't know, sorry but this's not my major so I can't explain.

Question Red Warning and UnWorking Lockscreen. HELP

{
"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"
}
Hello, dear owners of this beautiful device.
After an unsuccessful attempt to get root, such a warning appeared, plus the ability to lock the screen disappeared. As a result, I didn't get root either and problems arose)
Could you show the instructions how to fix everything step by step and get root? Thanks)
Hey, so I have the same problem as you. I was installing the patched boot.img file when I rebooted, but there was no magsik app. After I tried to flash the same file again, except I put in some vbmeta file because some website said so, now my phone's files are corrupted. I got into fastboot mode and put through recovery mode, and did a data wipe and one final reboot, but even that did work because it said my phone is corrupt. The last thing I will try is to install TWRP, remove the old data, and install the update to restore the previous ROM files. I'll let you know if anything works. Just try ur methods and let me know if they worked. Sure is an expensive paperweight if it doesn't work...
redmgicUSER8 said:
Hey, so I have the same problem as you. I was installing the patched boot.img file when I rebooted, but there was no magsik app. After I tried to flash the same file again, except I put in some vbmeta file because some website said so, now my phone's files are corrupted. I got into fastboot mode and put through recovery mode, and did a data wipe and one final reboot, but even that did work because it said my phone is corrupt. The last thing I will try is to install TWRP, remove the old data, and install the update to restore the previous ROM files. I'll let you know if anything works. Just try ur methods and let me know if they worked. Sure is an expensive paperweight if it doesn't work...
Click to expand...
Click to collapse
did anything happen?
Stusick said:
Did anything happen?
Click to expand...
Click to collapse
Nothing yet... I'm trying to contact the support team. They can only do so much remotely
i have this error also what should i do?
the phone not boot up
the red warning are stuck
yakir150 said:
i have this error also what should i do?
the phone not boot up
the red warning are stuck
Click to expand...
Click to collapse
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
[email protected] said:
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
Click to expand...
Click to collapse
okay i try it and still no luck the same problem
yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
Download global V3.19 rom from: https://rom.download.nubia.com/Europe&Asia/NX729J/V319/NX729J.zip
Download QPST and QFIL flash tool from: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file. Install the driver (provided in the download) and these two programs.
You could then flash this rom V3.19 using QFIL flash tool. If you can flash this rom successfully your phone will work.
[email protected] said:
Download global V3.19 rom from: https://rom.download.nubia.com/Europe&Asia/NX729J/V319/NX729J.zip
Download QPST and QFIL flash tool from: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file. Install the driver (provided in the download) and these two programs.
You could then flash this rom V3.19 using QFIL flash tool. If you can flash this rom successfully your phone will work.
Click to expand...
Click to collapse
my phone is eu and using 4.18
can i use 3.19?
it's ok?
yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
For QFIL, use Flat Build and in the configuration use ufs. Good luck!
yakir150 said:
my phone is eu and using 4.18
can i use 3.19?
it's ok?
Click to expand...
Click to collapse
Your version V4.18 will be replaced by V3.19. This V3.19 version can be flashed through edl mode. I could not find V4.18 in this format. The two roms are very similar. They are both global roms.
[email protected] said:
Your version V4.18 will be replaced by V3.19. This V3.19 version can be flashed through edl mode. I could not find V4.18 in this format. The two roms are very similar. They are both global roms.
Click to expand...
Click to collapse
okay i will try and let you know
thank you very much
yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
If QFIL does not work, you need to do side load the rom multiple times again then it might work!
turn off the red rm8 notification (Your device is broken. It is unreliable and may not work)
- enter command on PC: adb reboot "dm-verity enforcing"
- on phone for rooted device with termux: reboot "dm-verity enforcing"
izsdeaman said:
turn off the red rm8 notification (Your device is broken. It is unreliable and may not work)
- enter command on PC: adb reboot "dm-verity enforcing"
- on phone for rooted device with termux: reboot "dm-verity enforcing"
Click to expand...
Click to collapse
The command on PC shows "Too many arguments." The Termux one works. Thanks!
[email protected] said:
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
Click to expand...
Click to collapse
Tahnk you very very very much.

Categories

Resources