Related
Hi,
First off, my ouya is bricked, i get tot hte ouya "!" screen, thats it.
So after going from zero knowledge to actually got ADB to work and being able to adb roms to the ouya, im finally stuck.
When i try to install a OTA update rom (.zip file) after ADB over, it stops and says the version number is to low compared to the version on the ouya. does anybody have a room that can be ADB over and after that i can just do a factory reset? Any help is appreciated!
I´ve tried some other stockplus roms etc, but it just starts installing then it says canceled. what am i missing?
Is there any rom out there that can be adb over?!
T
There is some chance of flashing a sbf via PC?
Sent from my MB526 using Tapatalk 2
DiegoxG said:
There is some chance of flashing a sbf via PC?
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
Dont know how to choose location on the ouya, i know how to ADB stuff, (belive me it took 2days of hairpulling to figure that one out).
The problam is that i was in superuser with a fileexplorer i had edit a document and after that i was going to put the "read only" status back on the ouya systemfiles. But accidently unclicked read, so the ouya now just boots in to ouya"!" cause it cant read the system files. Does anyone have a system dump that i can flash? or can i flash a system dump just to get in the system and then do a system update / recovery?
Whould the abominable snowman update work if someone hade the ota rom for that? Since its a lter version than what i got i mean?
hello
i have rooted the device using the "1 CLICK ROOT TOOL" and now i have the dead android bot with error when i enter recovery.
i have tried the "fastboot erase cache" command at fastboot mode but it did not help
is their a way to fix it?
Try pressing Volume + key and Power. Don't hold just press. It might take a few goes to get it right. I had the same problem. That means that the update you have downloaded (saved on your system) fails to install.
hello and thanks
i can enter recovery by pressing the keys. this is not the issue
its just that i want to completely solve the problem
koby058 said:
hello and thanks
i can enter recovery by pressing the keys. this is not the issue
its just that i want to completely solve the problem
Click to expand...
Click to collapse
Awh sorry, I thought you can't get into recovery.
Try sideloading the stock Firmware. Go to official ASUS website and download it from there. It's about 1 GB. On this website you can find instructions on how to do it. http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 Section 3.2)
After that you can download OTA updates and install them using method described here http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835, "Steps to Apply OTA manually".
OTA can be downloaded from there (look at the later posts for newer OTA) http://forum.xda-developers.com/zenfone2/general/ota-links-stock-rom-t3093999
I had a very similar problem few days ago. That solved it. Had a similar problem a few days ago coz I messed up my build.prop
hello
i have already did a "adb siedeload" for the stock rom downloaded from the asus web site but the issue remain.
also i downloaded the latest ota, and "adb sideloaded" them as well. it worked flawlessly .
but the small thing with the recovery is annoying.
i thinking about looking inside tmp directory and delete something called "last update"
what do you say?
koby058 said:
hello
i have already did a "adb siedeload" for the stock rom downloaded from the asus web site but the issue remain.
also i downloaded the latest ota, and "adb sideloaded" them as well. it worked flawlessly .
but the small thing with the recovery is annoying.
i thinking about looking inside tmp directory and delete something called "last update"
what do you say?
Click to expand...
Click to collapse
You're not understanding because the information he gave you is slightly wrong. When you try to enter stock recovery it will ALWAYS say installing update and pop up an error Android bot. It's not about having some update data somewhere that fails to install properly. It will ALWAYS do that. That's normal.
rlaw said:
You're not understanding because the information he gave you is slightly wrong. When you try to enter stock recovery it will ALWAYS say installing update and pop up an error Android bot. It's not about having some update data somewhere that fails to install properly. It will ALWAYS do that. That's normal.
Click to expand...
Click to collapse
Owh, this is embarrassing. I was playing with it a lot and I was kind of sure that if you have a working installed update, which is the same as a zip of an OTA update you have on an SD card it will skip installing the update and go to recovery without an error, but I was very very wrong. I'm very sorry for missleading you, and I've learned something new. Thank you.
NiKiToS-04 said:
Owh, this is embarrassing. I was playing with it a lot and I was kind of sure that if you have a working installed update, which is the same as a zip of an OTA update you have on an SD card it will skip installing the update and go to recovery without an error, but I was very very wrong. I'm very sorry for missleading you, and I've learned something new. Thank you.
Click to expand...
Click to collapse
No worries, I've made the same mistake before. We've all been there, still learning new things about this phone after months of using it!
ok let me tell why i begin asking about it.
when i just got the phone i update all of the ota updates and after that i rooted it with "1 CLICK ROOT TOOL" .
two days ago i receive tha 2.20.40.58 ota . i downloaded and install but the instalation failed .
so i unroot it with "1 CLICK ROOT TOOL" and then i checked for update . but there was no update.
so i assumed the problem is because of the recovery issue.
the qustion is why i cannot install ota automatically ?
koby058 said:
ok let me tell why i begin asking about it.
when i just got the phone i update all of the ota updates and after that i rooted it with "1 CLICK ROOT TOOL" .
two days ago i receive tha 2.20.40.58 ota . i downloaded and install but the instalation failed .
so i unroot it with "1 CLICK ROOT TOOL" and then i checked for update . but there was no update.
so i assumed the problem is because of the recovery issue.
the qustion is why i cannot install ota automatically ?
Click to expand...
Click to collapse
The 2.20.40.58 OTA was bugged and pulled from release. Just flash the full stock 2.20.40.59 firmware available from ASUS site and stop modifying your phone if you want to remain trouble-free with OTA updates. Or if you choose to continue to root and tinker with your phone accept that some things might get broken.
Long story short - Bought an LG D851 off Swappe. It came with CM13. I've been sticking nightlies on it. Currently on 2/14. I tried to put 2/18 and found that TWRP wasn't working - it hangs on TWRP Splace. Then I noticed SuperSU wasn't on the phone. So I installed it. Can't update the binaries. Looks like I don't have root.
Used LG Flash tool and flashed D85120E_00.kdz. Part way through, I get an error that the software cannot communicate with the server and it asks if I want to abort. I let it continue.
The phone reboots, I get the "Android is updating 1/196", etc. After which, it reboots, I get the boot jingle, and then it holds on the T-Mobile screen. I've tried flashing the KDZ a few times with the same result.
So now, I humbly, yet again, ask for help.
The endgoal here, is to have a working ROM with BT and WiFi working. I really don't care what it is at this point. Marshmallow is nice. Lollipop is okay. Whatever. I just need a working phone.
Thanks in advance, as always.
mdphoenix said:
Long story short - Bought an LG D851 off Swappe. It came with CM13. I've been sticking nightlies on it. Currently on 2/14. I tried to put 2/18 and found that TWRP wasn't working - it hangs on TWRP Splace. Then I noticed SuperSU wasn't on the phone. So I installed it. Can't update the binaries. Looks like I don't have root.
Used LG Flash tool and flashed D85120E_00.kdz. Part way through, I get an error that the software cannot communicate with the server and it asks if I want to abort. I let it continue.
The phone reboots, I get the "Android is updating 1/196", etc. After which, it reboots, I get the boot jingle, and then it holds on the T-Mobile screen. I've tried flashing the KDZ a few times with the same result.
So now, I humbly, yet again, ask for help.
The endgoal here, is to have a working ROM with BT and WiFi working. I really don't care what it is at this point. Marshmallow is nice. Lollipop is okay. Whatever. I just need a working phone.
Thanks in advance, as always.
Click to expand...
Click to collapse
Ouch!!! Read my CM13 post...you don't need SuperSU anymore (CM13 has root built in)--I had the same problem a while back--fixed it by flashing the old factory version on the phone & then used Purple Drake to root it & then installed CM13...Was a HARD lesson for me.
Upshot---No SuperSU needed--No BusyBox needed on CM13. If you are used to the old way of doing things--you'll get B0rked big time.
Luck to you!!!!
debianmain1 said:
Ouch!!! Read my CM13 post...you don't need SuperSU anymore (CM13 has root built in)--I had the same problem a while back--fixed it by flashing the old factory version on the phone & then used Purple Drake to root it & then installed CM13...Was a HARD lesson for me.
Upshot---No SuperSU needed--No BusyBox needed on CM13. If you are used to the old way of doing things--you'll get B0rked big time.
Luck to you!!!!
Click to expand...
Click to collapse
I guess trying to push the SuperSU binaries is what effed up TWRP?
I'll check out your CM13 post. But the issue I have is that I can't flash a factory version with LG Flash Utility. I mean, it does, but now it just sits on the Tmobile splash.
Hopefully your post will show me something I missing.
@debianmain1 is this the post you're talking about? http://forum.xda-developers.com/showpost.php?p=65432245&postcount=158
I tried that DD command to no avail last night. I tried everything I could find before reaching out to everyone for help.
mdphoenix said:
I guess trying to push the SuperSU binaries is what effed up TWRP?
I'll check out your CM13 post. But the issue I have is that I can't flash a factory version with LG Flash Utility. I mean, it does, but now it just sits on the Tmobile splash.
Hopefully your post will show me something I missing.
@debianmain1 is this the post you're talking about? http://forum.xda-developers.com/showpost.php?p=65432245&postcount=158
I tried that DD command to no avail last night. I tried everything I could find before reaching out to everyone for help.
Click to expand...
Click to collapse
Yes--the SuperSU binaries B0rked my install real good ( as I understand it--2 different types of SU installed B0rks everything )..... And with CM13, you have to allow ADB & apps to have root. I've been modding phones for years now & CM13 threw me under the bus until I learned what to do... I use to ALWAYS root, install BusyBox & SuperSU---not with CM13
Ya--that won't help you I'd look up fastboot commands & try to flash it that way--sounds like you are stuck in a startup bootloop. I did see some info online about starting the G3 in fastboot--I had a very hard time getting my G3 fixed. Do you have a Linux computer to use? It's easier to work with some of the diag stuff with Linux.
debianmain1 said:
Yes--the SuperSU binaries B0rked my install real good ( as I understand it--2 different types of SU installed B0rks everything )..... And with CM13, you have to allow ADB & apps to have root. I've been modding phones for years now & CM13 threw me under the bus until I learned what to do... I use to ALWAYS root, install BusyBox & SuperSU---not with CM13
Ya--that won't help you I'd look up fastboot commands & try to flash it that way--sounds like you are stuck in a startup bootloop. I did see some info online about starting the G3 in fastboot--I had a very hard time getting my G3 fixed. Do you have a Linux computer to use? It's easier to work with some of the diag stuff with Linux.
Click to expand...
Click to collapse
I can always fire up an Ubuntu flash drive if necessary. I'll get working on Fastboot.
Thanks again!
@debianmain1 Hmmm, Fastboot doesn't seem to be functional. I've got download mode. Can I push something to it that way?
I managed to get somewhere yesterday. I tried flashing D85120e_00.kdz and it failed again. I got the "cannot communicate with server" error, then it rebooted and tried running initial setup and failed.
So I tried flashing D85110C_00.kdz. Much to my surprise, it worked! So I ran through initial setup and got the phone working to make sure all was well. I rebooted and got the Red 2. So now here I am. Guides show that I should be able to put it in download mode and reload factory firmware again. But all I get is the "Download Mode" graphic. It never switches over to the updating mode with the circular arrows. I fear the worst at this point, but I really don't know enough about the LGs to diagnose my own doom just yet.
Someone on Reddit pointed me in the direction of Board Diag. Unfortunately it doesn't appear to work on D851. Running out of options. Looks like it'll end up being an expensive learning experience.
Hello,
First of all, Thanks for this great community. It has been helping me with my S4 for a long time.
Almost a year ago, I bought a fire phone for my younger brother. Today I tried to install the Custom Rom CM11 (which I successfully did), but, among the files in the proper thread, are 2 more files, the Google apps and also, a "flash wipe out". I did this in the end, expecting that just cleaned everything without touching the OS. Huge and novice mistake from miself. After almost 5 hours of looking for a solution, I realized that I don't have an OS and can only enter to "Fire phone recovery mode". I have downloaded almost 5 or 6 stock firmwares that are available to donwload here in XDA. Tried to download the OTA for an unlocked phone from amazon and tried to upload it to the phone via ABD tools. In the end, I always get the same errors: Not-signed and can't install it in the phone.
I'm going to be honest: I'm desperate.
In conlcusion:
1) No OS in a fire phone.
2) No custom TWRP.
3) I just have recovery mode
4) Been trying to install through ADB tools without any success the stock OTA update (the last one, since I had the 4.6.6 version)
Anything that can help will be well received.
Thanks in advance
Hello,
Have you tried ADB sideload when you go into your phone's recovery? And if you did, what did it say when you tried installing it? Try using this to sideload your phone.
Thanks for your answer @mechasnyper but I have tried that out as well
Hey, thanks for the answer. I really appreciate the time for doing it.
Yes, I have tried the ADB Sideload. The phone it's identified through the CMD (I get to see the serial) and then try the ADB Sideload. It doesn't work with bin files. It says unable to load. I tried also with the zip files that are posted here in the forums, being able to load then at 100% but the cell phone says "invalid signature", and for this couldn't install it over the fire phone.
lordofra said:
Hey, thanks for the answer. I really appreciate the time for doing it.
Yes, I have tried the ADB Sideload. The phone it's identified through the CMD (I get to see the serial) and then try the ADB Sideload. It doesn't work with bin files. It says unable to load. I tried also with the zip files that are posted here in the forums, being able to load then at 100% but the cell phone says "invalid signature", and for this couldn't install it over the fire phone.
Click to expand...
Click to collapse
Try sideloading using this file. https://www.androidfilehost.com/?fid=24052804347783512 I found this somewhere else and this is the file I used when I screwed up my ROM installation.
When I get home I'll try using that file that you have posted.
I'll update the results.
lordofra said:
When I get home I'll try using that file that you have posted.
I'll update the results.
Click to expand...
Click to collapse
Success?
Sorry for the delay. Been talking with centurylink because since yesterday I have no Internet service (Answering from the phone). No, no success at all.
lordofra said:
It says unable to load.
Click to expand...
Click to collapse
Your need free RAM on computer bigger than .bin size.
Hey, thanks for the answer.
I'm doing it on my laptop that has 8 Gb of ram. Just in case, I'm going to try it on my brother's laptop that has 16 gb of ram to test this out. But I doubt this will make a difference, since I've tried already many .bin files (all of them are unable to load an their size its 1.2 GB max. Many zip files as well where I have obtained 100% load but the firephone aborts the installation due to signature verification failure.
This is really strange. I have screwed up installing Cyanogenmod onto my phone, yet I was able to revert back to the stock ROM with just the stock recovery. I will have to look more into this. I will post again soon for updates. Have you wiped the data and cache?
EDIT: I am not sure if this will work, but try using this bin file. http://androidhost.org/o120v
@lordofra
Try (with quotes)
adb sideload "full_path_and_name_of_the_bin.bin"
Device:
Htc Desire 530
Marshmallow 6.01
T-Mobile/MetroPCS
Ok long story short I rooted my device correctly and then while in TWRP browsing I deleted my OS....
Now the phone is still rooted, and I can flash/un-flash TWRP, but it has major issues connecting with adb and sometimes fastboot as well. I guess basically what I'm asking is for help to get any compatible OS installed.
Thanks in advance
Good day Owl,
Please refer to my Stock Images thread and flash the stock (.img) file for the T-Mobile variant. If you have any issues with this process just shoot me a PM and we can figure out what else to do.
- AndroidSamurai
AndroidSamurai said:
Good day Owl,
Please refer to my Stock Images thread and flash the stock (.img) file for the T-Mobile variant. If you have any issues with this process just shoot me a PM and we can figure out what else to do.
- AndroidSamurai
Click to expand...
Click to collapse
Right so that's the problem I'm having for instance when i go to simply just drag and drop the stock images to my phone i get a corrupted error. Now if i go to fastboot the stock images it gives me a 35 RU_NOT_SUPPORT error. adb just wont connect. i think im done for.
Have you tried reformatting the "internal SD" partition before attempting to "Enable MTP" from the mount menu?
Also, do you happen to have access to a Micro-SD?
AndroidSamurai said:
Have you tried reformatting the "internal SD" partition before attempting to "Enable MTP" from the mount menu?
Also, do you happen to have access to a Micro-SD?
Click to expand...
Click to collapse
well when i try to transfer any file from the computer (excluding fastboot) i get an error message saying "this **** could be corrupted" blah blah. Yes i have a micro sd.
Help sensei.
ps i feel like i could be possibly unzipping my adb/fastboot files incorrectlu
MR_Owl said:
Help sensei
Click to expand...
Click to collapse
Don't doubt yourself Grasshoppa... Wax On, Wax Off.
Ok, so if I'm getting this right you've already grabbed the "Stock Image" and un-compressed it.
Bc this image is so large and you've already been having corruption issues I'd say your best bet would be moving it to the root of an SD-Card.
So i have now sort-of fixed the adb connection issue and sideloaded the twrp recovery, sunshine apk, and supersu files from your page. where im getting hung up i when i go to flash the roms you have on your "stock" post im getting denied flashing the boot image and system image with the error message: 35 RUU NOT_SUPPORT blah blah haaaaaalp, btw my S is still on and i flashed all three of your files sir haaalp
AndroidSamurai said:
Don't doubt yourself Grasshoppa... Wax On, Wax Off.
Ok, so if I'm getting this right you've already grabbed the "Stock Image" and un-compressed it.
Bc this image is so large and you've already been having corruption issues I'd say your best bet would be moving it to the root of an SD-Card.
Click to expand...
Click to collapse
Hey man, you were helping me yesterday so I figured you could point me in the right direction. I have TWRP installed running well. But I can't seem to install a custom Tom to get root status for some reason... the system keeps denying the request even though I have the boot loader unlocked, Supersu is also installed
Have you tried or attempted to flash an Official RUU yet? Sorry for the delay, I work from 6AM-7PM..
AndroidSamurai said:
Have you tried or attempted to flash an Official RUU yet? Sorry for the delay, I work from 6AM-7PM..
Click to expand...
Click to collapse
You're good ! You were a huge help.
Side note.. I'm now successfully rooted but with what OS I'm not sure. Any insight?
From the screenshot I see you are using the Unlocked/Developer build.
Its great, thank u
Help --Htc Desire 530 Deleted OS while in TWRP
Hi, im am currently having the same problem as you were with my desire 530, Every time i try to start it up it goes straight to TWRP, and i keep getting message "failed to mount '/cache' (invalid argument)'. i did the boot.img and system.img flash and they both said [IMG FLASH COMPLETED]. My S is still set as {S-On}, I dont know how to use CMD to Fastboot and/or ADB anything. I cant enter Recovery mode and/or the phone. Stuck in Download, Bootload, and TWRP. how do i fix it to unlock it?
Need help desire 530
I'm trying to now just get S-Off because my phone wont let me do anything with it on and I got TWRP my phone in Download Mode Say's
htc download mode
*** UNLOCKED ***
htc_a16ul PVT S-ON
LK-1.0.0.0000
RADIO-01.01-U113251211_63.10.60527G
OpenDSP-UNKNOWN
OS-1.01.352.25
JUN 27 2016,10:52:53(765079)
I have been trying for months to unlock it to use for a different company or provider. I read a lot of forms on here and downloaded a lot of the links it would let me and yet I get no where. I don't understand or know what to do and don't really know how to use Command Promt I give up and just start dragging and dropping anything and everything I can an in there, I Just Need Help Please Please Help if you can I work a lot and sometimes 12hr nights and this has taken up a lot of my free and work time.