Develop Bugs

Back to stock, OTA update help

I rooted my Mytouch slide this afternoon and loaded another ROM which I decided I didn't like. So, I went back to stock, but its an earlier version than what I had before I rooted. There's are updates on this forum for the most recent OTA update. However, I get a signature error when I goto load it.
I boot into recovery by going holding Vol Down + power, the phone then reads the files on my SDCARD. After that, I go down and select "Recovery" and I goto the screen with the Red Triangle.
I then hit Vol up + Power and load the next screen, I select "Apply Update: update.zip" or whatever it says and I always get a signature error, I have tried the file form 3 different sources with the same result, surely someone has experienced this and can help me. Im using Simple Mobile so I dont think that I will get the OTA request so I need to find a way to get this OTA loaded unless there is a nandroid backup with these updates already in it.
Please help me, Ive read every possible thread on this site without any results.

Firstly you doin it wrong did you flash the eng build? if you are no longer rooted
http://forum.xda-developers.com/showthread.php?t=746577 IT WILL break root but put you back at stcok which is waht you want. ]
TO ROOT SAID UPDATE
http://forum.xda-developers.com/showthread.php?t=754669
FOLLOW THE DIRECTIONS CAREFULLY
ALSO READ THESE AND MEMORIZE THEM
http://forum.xda-developers.com/showthread.php?t=730965
http://forum.xda-developers.com/showthread.php?t=701241

I went back and went through the root process again, I can tell by the prompt that im rooted. I just cant get the updates applied to update my mytouch slide to the newest radio and system update. I get signature errors on both files. Surely someone on here has had a similar issue.
Any ideas?????

what is it that you want? are you using clockwork? and getting errors whn trying to get in to clockwork? if you havent flashed the ENG build you have to push ota.zip and update.zip EVERY TIME you try and get into clockwork

encrypti0n said:
what is it that you want? are you using clockwork? and getting errors whn trying to get in to clockwork? if you havent flashed the ENG build you have to push ota.zip and update.zip EVERY TIME you try and get into clockwork
Click to expand...
Click to collapse
Im running the stock Tmobile Rom version 1.18.531.1.
I want to update the phone to 1.35.531 and make the sure the radio is updated to 7.09.35.10. Both the newest versions of stock.
I have downloaded the ~25MB update from here but I get a signature error everytime I try and run the update. To run it, Im booting with Vol Down + Power, then to "Recovery" and when the screen comes up with the Red Triangle, (Vol Up + Power). Then I select "Update.zip" but it fails on the signature verification.
Thats exactly what Im doing, am I missing something?

reroot your phone

ratchetrizzo said:
reroot your phone
Click to expand...
Click to collapse
Ummm, I did that, I went through the whole process again unless Im missing something. Would someone be willing to help me by chat, Ill be on MSN under the email [email protected] I'd really like to get this fixed, if someone could help Id be really greatful. Thanks.

A little update
Ok,
I have a little update and Im hoping someone can put me on the right track from here. I flashed the stock ROM located at http://forum.xda-developers.com/showthread.php?t=713507
My version is now up to 1.26.531.1 and my radio is still at 7.08.35.04S
When I put the full ~25MB update to 1.35.531 on my sdcard as update.zip I go into Recovery and select the update.zip. Now I get past the signature but it errors out with the following error:
"E:Error in /sdcard/update.zip (status 7) and the installation aborts. Ive seen other people with similar errors but haven't seen a resolution. Any ideas?

Before you can apple the update file that is like 27mb you have to apply this FIRST http://db.androidspin.com/androidspin_developer_display.asp?developerid=63#280
Im in the same situation your in. The problem is that I cant find any mirros and AndroidSpin is down...

hypersonicx said:
Im in the same situation your in. The problem is that I cant find any mirros and AndroidSpin is down...
Click to expand...
Click to collapse
AndroidSpin works fine for me.

nbetcher said:
AndroidSpin works fine for me.
Click to expand...
Click to collapse
Do downloads work from there site? The site works but all download links take me to a error page.

[Q] Problem after the new update GN

Hi,
I searched the forum but I couldn't find a similar problem, so Please I need some help.
Last week I got the new update 4.1.2 on my Galaxy Nexus gsm, so I went and installed it.
During installation when the device turned off and it was unpacking the update or even a little bit before that, I got a message which I really don't remember very much and didn't understand but i think it was from rom manager asking something maybe about flashing or something similar.
I remember as well, that it said that the action cannot be undone! and since I didn't understand very well what it was asking me, i chose something which seemed to me the safest at the time.
Which means, if it asked me to install something, I chose not to since it can't be undone.
I know I'm not giving as much information as i should but this is what happened.
After the installation was finished, I downloaded root checker to find if i had lost my root or not and it took awfully long time for the app to tell me that my device is rooted.
So, everything was okay and apps which needed root access were getting it from superuser app.
Today I decided to backup my rom so I opened rom manager premium and I was not able to backup the rom or even restart in recovery mode, so i uninstalled it and reinstalled it and I was getting always error that it was not granted superuser access.
So, i figured out that the problem is specifically with the rom manager because other app which needs root access were always getting it, so I went to titanium backup and rebooted through the app into recovery mode and it did but all i got is that black screen with the android icon in the middle having a red triangle on top. I had to take the battery off to restart the phone.
I tried again to reboot into recovery mode using the power and the volume button but I was unable to.
So, I'm asking whats the problem?
Am I still rooted? and how can i fix this problem?
I was thinking of using the nexus kit but I can't reboot in recovery mode at all so I guess it won't be much of a help.
I'm very sorry for the LONG question.
Thanks Guys

clouds73 said:
Hi,
I searched the forum but I couldn't find a similar problem, so Please I need some help.
Last week I got the new update 4.1.2 on my Galaxy Nexus gsm, so I went and installed it.
During installation when the device turned off and it was unpacking the update or even a little bit before that, I got a message which I really don't remember very much and didn't understand but i think it was from rom manager asking something maybe about flashing or something similar.
I remember as well, that it said that the action cannot be undone! and since I didn't understand very well what it was asking me, i chose something which seemed to me the safest at the time.
Which means, if it asked me to install something, I chose not to since it can't be undone.
I know I'm not giving as much information as i should but this is what happened.
After the installation was finished, I downloaded root checker to find if i had lost my root or not and it took awfully long time for the app to tell me that my device is rooted.
So, everything was okay and apps which needed root access were getting it from superuser app.
Today I decided to backup my rom so I opened rom manager premium and I was not able to backup the rom or even restart in recovery mode, so i uninstalled it and reinstalled it and I was getting always error that it was not granted superuser access.
So, i figured out that the problem is specifically with the rom manager because other app which needs root access were always getting it, so I went to titanium backup and rebooted through the app into recovery mode and it did but all i got is that black screen with the android icon in the middle having a red triangle on top. I had to take the battery off to restart the phone.
I tried again to reboot into recovery mode using the power and the volume button but I was unable to.
So, I'm asking whats the problem?
Am I still rooted? and how can i fix this problem?
I was thinking of using the nexus kit but I can't reboot in recovery mode at all so I guess it won't be much of a help.
I'm very sorry for the LONG question.
Thanks Guys
Click to expand...
Click to collapse
Try to flash recovery through fastboot from PC

polimeno said:
Try to flash recovery through fastboot from PC
Click to expand...
Click to collapse
Thanks for the answer.
Flashing recovery using what exactly? Gnexus Kit?

clouds73 said:
Thanks for the answer.
Flashing recovery using what exactly? Gnexus Kit?
Click to expand...
Click to collapse
Yeah, Galaxy nexus toolkit will work fine. You can also download the recovery (it is a .img file) and flash it manually through fastboot (fastboot flash recovery recoveryname.img)

Unable to Access Device Storage

Hello Everybody,
I habe a really big Problem with my GNex.
Today I Copied some Files over to my PC. For this I used for the first time "USB Mass Storage". Because I haven't seen some Files wich i can see under my Phone.
It worked really good. I unplugged my phone and to my things. Some minutes later i Heared the "Pling" from superuser. Then my phone was really slowly and need a bunch of time only to open the Launcher. So i deactivated Superuser. Deinstalled USB Mass Storage and MyMobiler.
After this i rebooted my Phone 2 times and the lag on my screen was gone. But now i'm unable to Access the Device under Android booted as MTP.
Even after reinstalling USB Mass Storage i'm unable to Access the Device via MTP or Mass Storage. My Windows PC and Android don't says anything. My Device is only Loading.
So i Unlocked my Bootloader with "BootUnlocker" and updated my System with offical Google Update 4.2 "fastboot update image-yakju-jop40d.zip" .
But i cann't access my Device now. Only fastboot is working.
So i'm unable to backup all my data and do an Factory Reset.
Have anyone out there an Suggestion how i can fix this Problem.
My Device:
Galaxy Nexus
Stock: 4.2
BL: Unlocked
Root: No Root (But with BL unlocked should this be the smallest problem.
Best regards and Thanks
Chris
P.s Sorrry for the really bad English
P.s.s Fastboot is working ... so it don't seems like an HW error

The nexus doesn't have use mass storage
Sent from my Galaxy Nexus using Tapatalk 2

This point i know, thats why i used the App.
But how can i aceess my Phone with MTP?
It's not even reconigzed under Windows ... and Android also don't set an Logo which tells that USB is Connected.

Chris302 said:
This point i know, thats why i used the App.
But how can i aceess my Phone with MTP?
It's not even reconigzed under Windows ... and Android also don't set an Logo which tells that USB is Connected.
Click to expand...
Click to collapse
have you tried a different usb chord?

simms22 said:
have you tried a different usb chord?
Click to expand...
Click to collapse
Yes i tried another USB-Cord.
Same thing -> Phone is Charging but not resposing over ADB.
And also i can't see it in the Explorer.
Same thing at my GF PC (Win Vista)

are you trying to use adb in the bootloader? if so, that will never work. ever.

Zepius said:
are you trying to use adb in the bootloader? if so, that will never work. ever.
Click to expand...
Click to collapse
No i'm using Fastboot when i was in BL to confirm that i have no HW error.
I try to ADB when i booted my Phone.
Or to access the My Device via Explorer

Have you tried removing and re-installing the drivers from your PC?
Have you checked the Android SDK to see if there is a 4.2 specific version of adb?

danger-rat said:
Have you tried removing and re-installing the drivers from your PC?
Have you checked the Android SDK to see if there is a 4.2 specific version of adb?
Click to expand...
Click to collapse
I Don't think hat There is my Problem, because under Windows i can Not even See my device it is not even recognized.
I can test driver uninstalling but i can not see my device under the device manager
:/ it seems like my android is f****ed up because root is also not working :/

When you update to a stock image you over write your/system partition (which is where you enabled root access) - that is most likely how you lost root access.
Also, since you updated your device, it is possible that your PC no longer sees it as the same device, which is why I suggested removing and reinstalling the driver...

danger-rat said:
When you update to a stock image you over write your/system partition (which is where you enabled root access) - that is most likely how you lost root access.
Also, since you updated your device, it is possible that your PC no longer sees it as the same device, which is why I suggested removing and reinstalling the driver...
Click to expand...
Click to collapse
I want to clear some things.
Don't think i want to shame you, i really thankfull for your help . Also it is the Best forum for Android Development and everything around it wo i have ever seen.
I was always on Stock. I updated the Offical 4.2 to 4.2 with an Stock image, it is now working again, i think the Update cleaned the Things up. Only Thing (shame me) i have forgotten to check after update is under-> settings -> storage -> Menu -> USB-Connection -> and check there "MTP".
So now my Device says connecting as "MTP" and my PC also recognize it again.
Before that my Device don't even say connecting as MTP.
I know that i will loose root when i update my Device -> but with my unlocked BL I just Booted to CWM and flashed Superuser.
Maybe (i hope) you are willing to help me again.
I am unable to update my SU binary and also i dont see a Message from Superuser, where i can allow Root access.
Even if i set under Settings -> Security -> Automated Answer -> "Allow"
I don't see the Message where i can say "allow" to Root access. I cannot even install SuperSU.
Have you any idea why it seems like i cannot access Root. For me it's seems like my app's don't recognize root.
When i Start SuperSu he says "Su-binary" must be updated" and next step is "Installation failed".
Have you any Idea where this came from?
But the good thing is at this point i'm abel again to access my Device via Explorer Thank you really really much for your Help You can't belive how glad i'm not to do a Factory reset and loose all my data.
Thank oyu for your great help
Chris
P.s. Root is working from Shell

Please read forum rules before posting
Questions and issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

Okay i will read the Rules again.
Thank you for moving the Thread.
I hope in the right section someone can tell my why my Root isn't working ?
P.s. or should i make a new thread for that problem ?

Chris302 said:
Okay i will read the Rules again.
Thank you for moving the Thread.
I hope in the right section someone can tell my why my Root isn't working ?
P.s. or should i make a new thread for that problem ?
Click to expand...
Click to collapse
Use SuperSu instead of Superuser.
Sent from my i9250

bk201doesntexist said:
Use SuperSu instead of Superuser.
Sent from my i9250
Click to expand...
Click to collapse
Sorry for the long delay.
I had no time to check this thread. And also my Email Notification hasen't worked.
So I hope you still look at this and can also suggest something.
I tried SuperSU but supersu says.
He need to install the Binaries.
After roundabout 15 seconds i get an Error message which says: "Installation failed".
My Super user tells me that the Binary is outdated.
And i get this Error Message in SuperSU even when i say "Answer every Permission Request with Allow".
I Even tried to remount the System as RW and the say update. But Both of them Seems to fail to install the Binary.
I flashed Superuser Through Temp Booted CWM.
Is their another Zip that i can try ?! or have i done something wrong while Flashing ?
Or can i theoretically flash SuperSU through CWM and then get Root Access?
Thank you for your help
Chris

Chris302 said:
Or can i theoretically flash SuperSU through CWM and then get Root Access?
Thank you for your help
Chris
Click to expand...
Click to collapse
Correct; you will be rooted again. Just boot a custom recovery and flash.
Sent from my i9250

bk201doesntexist said:
Correct; you will be rooted again. Just boot a custom recovery and flash.
Sent from my i9250
Click to expand...
Click to collapse
Hello
And again a dumb question.
Could you please provide me a download link for a zip. Which is working under 4.2 ?
I have seen zip's around for Superuser but not for SuperSU.
An i only Mention that maybe Superuser have a Problem with 4.2 but i cannot Prove it.
Thanks again
Chris :]
Sent from my ASUS Transformer Pad TF300T using xda app-developers

oasad92 said:
Yeah SuperSU should do the trick
Click to expand...
Click to collapse
Thank you for the Reply.
But how i have written 2 post ago. SuperSU also did not work.
He keeps saying "Installation Failed" thats why i asked for an Flashable Version which is working under 4.2.

I recently reverted back to stock 4.2.1 (just to try it)
My Win7 computer was unable to see my phone when connected in MTP mode. Nothing showed in the computer at all, However when I selected PTP I could acess the DCIM folder.
In the end I couldn't be F**Ked with it so I pushed a custom rom to data/media/ and every thing was normal again.
I spoke to a friend who had the same issue I had, and he just enabled debugging (which a custom rom has enabled by default) to solve the issue.

Chris302 said:
Hello
And again a dumb question.
Could you please provide me a download link for a zip. Which is working under 4.2 ?
I have seen zip's around for Superuser but not for SuperSU.
An i only Mention that maybe Superuser have a Problem with 4.2 but i cannot Prove it.
Thanks again
Chris :]
Sent from my ASUS Transformer Pad TF300T using xda app-developers
Click to expand...
Click to collapse
oasad92 said:
Yeah SuperSU should do the trick
Click to expand...
Click to collapse
I have not tried Superuser again since Chainfire released Supersu and all those issues rose with JB.
Chris302 said:
Thank you for the Reply.
But how i have written 2 post ago. SuperSU also did not work.
He keeps saying "Installation Failed" thats why i asked for an Flashable Version which is working under 4.2.
Click to expand...
Click to collapse
http://www.google.co.uk/search?q=xd...&sugexp=chrome,mod=0&sourceid=chrome&ie=UTF-8
would take you to:
http://forum.xda-developers.com/showthread.php?t=1538053
flash that
p.s: on the supersu thread says you need to be rooted... for us, of course, it's not quite true, rather we need unlocked bootloader and custom recovery.

[Q&A] [RECOVERY] CWM Recovery 6.0.5.1.2

Q&A for [RECOVERY] CWM Recovery 6.0.5.1.2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

Full backup of one AFTV and restore on another
It's great to see that modstore was able to clone an AFTV.
I dont understand what modstore is saying here:
modstore said:
I'm not sure if anyone has tried backing up one Fire TV and restoring to another, but I just tried it, and all seems good.
Doing the restore though, changed the registered account to that of the backup. So I'm not sure if it would have been registered properly, probably not. But I changed it to the account I wanted it registered too, and all seems good now.
Click to expand...
Click to collapse
Changed what registered account? Does this mean that the new AFTV was setup to have the same amazon account as the backed up AFTV before the restore took place on the new AFTV?
I really want to be able to clone. It sounds like its possible, I just want to avoid the trial and error if possible. I'm sure others are interested in the procedure too.

eville84 said:
It's great to see that modstore was able to clone an AFTV.
I dont understand what modstore is saying here:
Changed what registered account? Does this mean that the new AFTV was setup to have the same amazon account as the backed up AFTV before the restore took place on the new AFTV?
I really want to be able to clone. It sounds like its possible, I just want to avoid the trial and error if possible. I'm sure others are interested in the procedure too.
Click to expand...
Click to collapse
Yes, from what he said that the registration info went over with the backup. If you want to clone machines, then this will work.
he didn't want to clone machines, so he had to put in the correct register info on the machine he put the backup on.

nyder said:
Yes, from what he said that the registration info went over with the backup. If you want to clone machines, then this will work.
he didn't want to clone machines, so he had to put in the correct register info on the machine he put the backup on.
Click to expand...
Click to collapse
There might be a way to make it trigger the initial Registration page after doing a restore of a clone. I'll add it to my list and maybe come up with a special update.zip that will make it happen.

So if you have a FTV set up with xbmc etc you can make a direct copy of it into a stock FTV, thus cloning it as said above?

I've looked around and can't seem to find what to do. I've used adb before but have never ran into this issue yet seems so silly.
When I type "su" in adb shell i get this error "system/bin/sh: su: not found"
I've googled and all I can find is reinstalling the superuser on the phone... I'm trying to unlock the boot loader

hellot1M said:
I've looked around and can't seem to find what to do. I've used adb before but have never ran into this issue yet seems so silly.
When I type "su" in adb shell i get this error "system/bin/sh: su: not found"
I've googled and all I can find is reinstalling the superuser on the phone... I'm trying to unlock the boot loader
Click to expand...
Click to collapse
You need root first. What fw are you on? If it's a rootable version, do that first and then follow the guides for updating here.

Yea figured it out. I'm on 1.3.0 this sucks. I'm trying to sell my amazon box to get a nexus player. Amazon has no idea how to run a home media center.

Thanks!

Bricked mine. Cant boot into recovery anymore using keyboard. Any tips ?
Sent from my SM-N910V using Tapatalk

patt2k said:
Bricked mine. Cant boot into recovery anymore using keyboard. Any tips ?
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
What guide, and which step of said guide, were you running through that you bricked it?
Sent from my TARDIS

0p3nsrc said:
What guide, and which step of said guide, were you running through that you bricked it?
Sent from my TARDIS
Click to expand...
Click to collapse
Guide from AFTVNEWS.
I got recovery to work everything was fine I could reboot from recovery back to recovery again (CWM) but after I did factory reset in CWM it gets stuck on amazon logo.
The reason I did factory reset was because of Error.7 in CWM I had that few times when flashing different roms on different phones/tablets
sometimes getting older cwm or simply factory reset would help.
So now it gets stuck on Amazon logo the keyboard trick to get back into CWM does not work anymore.
Anything else I can try before I call up amazon hoping they replace it ?

I can honestly say if you followed rbox's custom recovery install guide, used his recovery image, and made sure the md5 matched, you shouldn't have had any problems.
Out of curiosity, do you have an external hard drive plugged in?
Sent from my TARDIS

0p3nsrc said:
I can honestly say if you followed rbox's custom recovery install guide, used his recovery image, and made sure the md5 matched, you shouldn't have had any problems.
Out of curiosity, do you have an external hard drive plugged in?
Sent from my TARDIS
Click to expand...
Click to collapse
Yea I did follow instructions correctly. And no I do not only had the usb keyboard plugged in so I could get into recovery.
Almost every device I rooted w/ custom recovery gave me Error 7 tablets phone etc.. I seem to have bad luck with that error lol.
Since I was on the very last step.. flashing rom -> getting error 7 grr

patt2k said:
Yea I did follow instructions correctly. And no I do not only had the usb keyboard plugged in so I could get into recovery.
Almost every device I rooted w/ custom recovery gave me Error 7 tablets phone etc.. I seem to have bad luck with that error lol.
Since I was on the very last step.. flashing rom -> getting error 7 grr
Click to expand...
Click to collapse
I think cwm still has some issues. It works fine for installing rbox's pre-rooted ROMs, but I can't backup my ftv. It always errors out.
Was this the first time you've gone through cwm install? Did you try installing one of his custom ROMs and then got that error? Did you verify that your recovery download went okay? Check the md5 against what's listed on the site.
I know it's a lot of questions, but I'm just trying to delve deeper to see what may have caused your error.
(I'm tech support, so I've always got more questions to ask )
Sent from my TARDIS

0p3nsrc said:
I think cwm still has some issues. It works fine for installing rbox's pre-rooted ROMs, but I can't backup my ftv. It always errors out.
Was this the first time you've gone through cwm install? Did you try installing one of his custom ROMs and then got that error? Did you verify that your recovery download went okay? Check the md5 against what's listed on the site.
I know it's a lot of questions, but I'm just trying to delve deeper to see what may have caused your error.
(I'm tech support, so I've always got more questions to ask )
Sent from my TARDIS
Click to expand...
Click to collapse
Yes sir everything was checked few times. Bunch of times made sure even file size is correct etc...
I did install recovery however at first when I had wrong firmware I installed via ADB SHELL then I Downgraded to unlock bootloader after I downgraded I installed recovery via adbfire I think newest version .17 however it was still the newest firmware of recovery anyway.... and yepp it was stock pre-rooted latest firmware that ends with "0" that did not require the fire tv boot menu.. but now I am thinking if I had the boot menu I could have got into recovery! so AFTVNEWS mis-lead me on this part... the bootmenu would be great on all firmwares actually.

patt2k said:
Yes sir everything was checked few times. Bunch of times made sure even file size is correct etc...
I did install recovery however at first when I had wrong firmware I installed via ADB SHELL then I Downgraded to unlock bootloader after I downgraded I installed recovery via adbfire I think newest version .17 however it was still the newest firmware of recovery anyway.... and yepp it was stock pre-rooted latest firmware that ends with "0" that did not require the fire tv boot menu.. but now I am thinking if I had the boot menu I could have got into recovery! so AFTVNEWS mis-lead me on this part... the bootmenu would be great on all firmwares actually.
Click to expand...
Click to collapse
I'm not sure about adbfire anything. I do all mine through Linux/android terminal/windows command line. The boot menu works on firmware 51.1.4.0. When it's sitting at the logo, have you tried connecting via adb, just to see if it initialized enough to poke around? (not sure if it works that way with ftv, but I'd try, regardless)
Sent from my TARDIS

0p3nsrc said:
I'm not sure about adbfire anything. I do all mine through Linux/android terminal/windows command line. The boot menu works on firmware 51.1.4.0. When it's sitting at the logo, have you tried connecting via adb, just to see if it initialized enough to poke around? (not sure if it works that way with ftv, but I'd try, regardless)
Sent from my TARDIS
Click to expand...
Click to collapse
As far as I saw I could only connect via adb at least when in recovery mode.. otherwise it was a no go... anyways thanks for helping me out. I think there is no rescue in this situation by somehow fixing it. I mean just wanted to have few features like swap storage with a flash drive and have newest FW. But that's ok.
Thanks for your time!

patt2k said:
As far as I saw I could only connect via adb at least when in recovery mode.. otherwise it was a no go... anyways thanks for helping me out. I think there is no rescue in this situation by somehow fixing it. I mean just wanted to have few features like swap storage with a flash drive and have newest FW. But that's ok.
Thanks for your time!
Click to expand...
Click to collapse
Sorry I couldn't be of more help :/ the issue you'll probably see is that unlocking the bootloader voids any warranty with amazon.. So I'm not sure what amazon may or may not do for you.
Sent from my TARDIS

About the possible Lollipop ROM for FireTV,is there a way to get the latest qualcomm Adreno 320 drivers like [email protected] from another device for flashing in proper FTV directories since it is meant for Lollipop?
I am hoping for the fix for Dolphin to be runnable and Reicast to no longer cause reboots,as well as better performance for things like Mupen64Plus AE.

Help --Htc Desire 530 --Deleted OS while in TWRP Recovery

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.