Develop Bugs

[Resolved] Recovery installed but no root access

I used AlphaRevx to achieve S-OFF and when it asked if I wanted the CWM recovery, I said yes. It installed the recovery properly. I have SU. However, if I try to run Titanium, it says that there is no root access. I have rebooted several times. I tried to flash CM7 and it was stuck in a bootloop. Downloaded from the mirror and it booted up fine. I tried playing around with ROM Manager while I was booted into CM7 and it told me there was no recovery image on the root of the SD card.
Hopefully it's just something simple that I'm overlooking. Any suggestions?
Another thing I though was weird is that I couldn't sync to Gmail while booted into CM7.

To gain root access on the stock rom, you first have to flash thisthrought recovery.

I actually did flash that as well. Still had the same results.
Should I have removed the SU file that was already installed on the sd card and then flashed the patch?

Hmm weird, maybe try flashing one of these 2 roms
this
or
this
Both are based off the stock froyo rom, debloated and rooted.

I'll probably give that a try in a little bit. I suspect that it will not work as I didn't even have root access with CM7 installed.

Maybe before you flash clear all the data at least 2 times, do a factory reset, and clear the dalvik cache. If nothing works try the manual way to flash CWM and reflash it.

I only wiped data/cache once before I flashed each time. I'll try wiping more than once next time.
Do you think I could have flashed a corrupt file for SU?

brocksdad said:
I only wiped data/cache once before I flashed each time. I'll try wiping more than once next time.
Do you think I could have flashed a corrupt file for SU?
Click to expand...
Click to collapse
Make sure you wipe /data, /cache, /system before you flash any rom. If you do this it removes the chances for errors to occur. if you flashed CM7 over the original /system, you might have corrupted the su file.

I don't think that I did, but it is possible. I'll first start by removing the SU file that is on there now and then flashing the patch that you posted up. I'll update after I do that.
I have to wait though, my battery is dead.
Thanks for your help!

No problem. If you didn't format the /system before you flashed CM7, you flashed over the original /system, sometimes it makes no difference, sometimes it messes stuff up. Kinda hit or miss.

Yah normally doing a Factory wipe then a wipe data/cache/dalvik should get her done try rerunning alpharev utility and see what you get

Update: I removed the su-2.3.6.1-ef-signed.zip from the SD card and then flashed the patch. Still having the same issues. I tried to run AlphaRevX again and it came back saying something like "You already have S-OFF with AlphaRev. What do you think you're doing?"
Any other suggestions?

First of all i s-offed and cwmed with alpharev.
Then in cwm i wiped phone + cache + dalvik .
Then flashed this http://forum.xda-developers.com/showthread.php?t=1138274
Then after phone boots and so on i restart in cwm again and flashed this
http://forum.xda-developers.com/showthread.php?t=1160745
After all i got SU in programs and got root for all my apps.
Try this )

The whole point of this is to have Titanium backup installed so I backup all my apps before I flash a ROM.

brocksdad said:
The whole point of this is to have Titanium backup installed so I backup all my apps before I flash a ROM.
Click to expand...
Click to collapse
Hey brocksdad,
Why not give this a shot as this is what I had to do:
-Alpharevx s-off which you've done
-flashed CWM via fastboot adb which seems like you've done: http://forum.xda-developers.com/showthread.php?t=1134520
-flash this patch which will install superuser, busybox, and rooter kernal in the correct places /system/xbin: http://forum.xda-developers.com/showthread.php?t=1134520
-reboot and you should be good to go.
I think you were having the same issues I was in that the SU app would not update the binaries for me, so I had to install the manual patch I found in the development forum.
Let me know if this works for you....

If I wanted to manually put the CWM recovery in there do I just flash OVER what I already have or do I need to remove the recovery that is already installed? If I have to remove it, how do I go about doing that?

brocksdad said:
If I wanted to manually put the CWM recovery in there do I just flash OVER what I already have or do I need to remove the recovery that is already installed? If I have to remove it, how do I go about doing that?
Click to expand...
Click to collapse
You would just reflash over the recovery. I'm hoping you used the recovery that was posted for us and not the one with Rom Manager as that is an older recovery that hasn't been updated for Inc2 support yet.
In any case, it wouldn't hurt to go and do the process over again. You should have fastboot.exe in the same folder as your adb and might as well have the CWM flash .img in that same folder as well to make things easier. once you do that you can flash the SU patch in recovery and you should be good to go.
Update: By the way if you need adb, you can just download the files from the "Temp Root" post in development and download fastboot.exe by searching in google.

I used the recovery that the AlphaRev tool gave me.
I'll give that a try and see how it goes.
Thanks!

brocksdad said:
I used the recovery that the AlphaRev tool gave me.
I'll give that a try and see how it goes.
Thanks!
Click to expand...
Click to collapse
Okay then you should be fine. Go ahead and flash that SU zip in recovery mode. Once you reboot, open up superuser and go to settings. Check the SU binary and make sure it says v2.3.2-efgh (eclair, froyo, gb, honeycomb).
If it does then you should be good to go. Also make sure when there are md5 sums provided by the uploads that you check those to make sure they match so that you don't try flashing corrupted downloads. There's a free app in the market for checking the md5 sums right on your phone, it's called AFV (Android File Verifier)

I just looked at the SU information. It says v2.3.6.3. Underneath it says SU binary voutdated. I tried to update and it comes back with an error saying that su-2.3.1-bin-signed.zip has been placed on the sd card. Please reboot into recovery mode and flash it to update the SU binary.

SUPERUSER problem...

Sorry to post this as my first thread here, but I'm running into a problem that I can't seem to get past. Trying to root an unlocked T-Mo T989. I followed the instructions in the developer's thread on how to do it, and I got the CWM installed properly and did a NANDROID backup. The problem I'm having is with any user of the SU binary and SUPERUSER.APK. I first tried to install the Superuser-3.0.7-efgh-signed.zip, but got an error that it was a bad zip, installation aborted. It's given me that error regardless of which downloaded version of that file I used, and I've D/L'd it from several different sites. So, I tried the instructions to use the deodexed ROM from this site. I re-CWM'd the phone, and tried to load SGH-T989-Deodexed-Root-Busybox-Superuser-by-teshxx-bubby323.zip from my SD card and I got the same error- bad zip, installation aborted. Can't be that many bad zips out there, and more to the point, I can unzip these files fine manually and see the data, so it's obviously something I'm doing.
Interestingly, SuperUser did get installed on the phone, but I don't seem to have SU rights to anything except that which I've installed. I'm trying to remove all the bloatware, but don't have rights to it.
I've had to rebuild all my personal data because bubby323's instructions here had me clean the partitions. I don't want to do that again except for when the phone is properly rooted, so I'm hoping that someone here will be kind enough to tell me how I'm screwing it up. Thanks,
..Joe

this not a rooting question, so don't hijack an unrelated topic for your troubles
the problem you are having is installing SU
just boot into CWR which you already have insalled, then use CWR to Flash the SU zip file
or if that is too complicated use then use the superoneclick method which will also install SU for you the easy way

Umm, sorry, but did you read the post? I did boot into CWR, and tried to install the SU zip, and that's where I get the error that it's a bad zip, installation aborted. Same thing for the one-click version by bubby. That's why I posted it in that thread: I did not try to hijack anything. That was the rooting and SU thread, hence the reason I posted it there.
For all I know it's a problem with CWR.
Geez, talk about jumping allover someone asking for help...
..Joe

AllGamer said:
or if that is too complicated use then use the superoneclick method which will also install SU for you the easy way
Click to expand...
Click to collapse
Agreed.
Use superoneclick if you can't install superuser via cwm. may be best to uninstall superuser if its on your phone but not working.
Sent from my SGH-T989 using XDA App

Actually this is quite an easy fix....
In CWM, run the install again. Hell, run it a couple times, until it says successful. I've done this on 5 sgsii's so far, and 3 of them had this problem. My best guess is it isn't mounting the partitions correctly, (which I am unable to verify. The installer script it right, and even if i mount the system partition manually before install it still failed.)
So, easy answer:
Boot to cwm.
Run the installer for su
if it fails, run it again without rebooting
if it fails, once again run it.....
eventually it will work, then reboot, and your rooted. (I'd also suggest after this is done to go into the superuser program settings, scroll to the bottom and update the su binary as well, but this isn't really required.)
Good luck.

you can also use the Fix Permission option in CWR
i know i came across that problem before, and it was able to install after i Fixed the permissions

Well, obviously I'm still doing something wrong. I restored the phone to stock using the CWN Recovery of the NANDROID backup I did when first attempting this. I then started over:
Up and down held down while inserting the USB cable.
From ODIN I select the CMW tar in the PDA, and that installs and reboots the phone.
Shut down phone and re-start with up and down keys depressed, USB cable out
Select Install zip from SD card
Select the Superuser-3.0.7-efgh-signed.zip (or the deodex, doesn't matter)
down 7 times to select
then I get this error:
Selecting SU Superuser-3.0.7-efgh-signed.zip...
Finding update package...
Opening update package...
E:can't open /sdcard/Superuser-3.0.7-efgh-signed.zip
(bad)
Installation aborted.
I get that no matter how many times I've tried to install it, and even after fixing permission, and even if I try to install it off the internal USB storage.
Any one have any ideas?
Thanks,
..Joe

Correction...
It doesn't like the SD card. I installed the deodex file from the internal USB storage, and this time, it finally took! Thanks to everyone for all the help.
..Joe

hi i have the exact same problem. Can you please explain what is a deodex file and how you installed it? thanks

i got the same error when rooting, however upon rebooting and going into my apps superuser had installed and was working even after receiving the error

sorry but i'm a bit confused here..my apps? what's the exact path to that?
I basically get that error, leaving me without root privilages, the only thing accomblished is the s-off. But without root access, i cant do anything.
Also, after that, my phone's reception is gone...

kostistheo said:
sorry but i'm a bit confused here..my apps? what's the exact path to that?
I basically get that error, leaving me without root privilages, the only thing accomblished is the s-off. But without root access, i cant do anything.
Also, after that, my phone's reception is gone...
Click to expand...
Click to collapse
the exact path to apps would be phone reboots, then upon reboot pay close attention here... upon reboot i click my app drawer, BAMMM theres my apps.. now i cycle thru until i get to the S section and look for super user...lol
---------- Post added at 03:01 AM ---------- Previous post was at 02:59 AM ----------
do this ... GOOGLE "HOW TO ROOT THE T989" there will be youtube video with the step by step hands on walk thru...watch it

thanks for the unnecessary sarcastic american comment...

thanks for the seemingly racist comment, ignorance must be a way of life for some.

kostistheo said:
sorry but i'm a bit confused here..my apps? what's the exact path to that?
I basically get that error, leaving me without root privilages, the only thing accomblished is the s-off. But without root access, i cant do anything.
Also, after that, my phone's reception is gone...
Click to expand...
Click to collapse
S-off? Our phone doesnt come with a locked boot loader... We arent using an htc device. never had s-on to begin with lol.
Sent from my SGH-T989 using XDA App

joegerardi said:
Sorry to post this as my first thread here, but I'm running into a problem that I can't seem to get past. Trying to root an unlocked T-Mo T989. I followed the instructions in the developer's thread on how to do it, and I got the CWM installed properly and did a NANDROID backup. The problem I'm having is with any user of the SU binary and SUPERUSER.APK. I first tried to install the Superuser-3.0.7-efgh-signed.zip, but got an error that it was a bad zip, installation aborted. It's given me that error regardless of which downloaded version of that file I used, and I've D/L'd it from several different sites. So, I tried the instructions to use the deodexed ROM from this site. I re-CWM'd the phone, and tried to load SGH-T989-Deodexed-Root-Busybox-Superuser-by-teshxx-bubby323.zip from my SD card and I got the same error- bad zip, installation aborted. Can't be that many bad zips out there, and more to the point, I can unzip these files fine manually and see the data, so it's obviously something I'm doing.
Interestingly, SuperUser did get installed on the phone, but I don't seem to have SU rights to anything except that which I've installed. I'm trying to remove all the bloatware, but don't have rights to it.
I've had to rebuild all my personal data because bubby323's instructions here had me clean the partitions. I don't want to do that again except for when the phone is properly rooted, so I'm hoping that someone here will be kind enough to tell me how I'm screwing it up. Thanks,
..Joe
Click to expand...
Click to collapse
I had this problem too, just do this:
Before attempting to install the SU zip again, wipe Dalvik cache
(under "advanced" in CWM recovery)
Then install the SU zip
Works everytime..

i tried what you post but still not rooted, I got super user but its still not roote
ingenious247 said:
I had this problem too, just do this:
Before attempting to install the SU zip again, wipe Dalvik cache
(under "advanced" in CWM recovery)
Then install the SU zip
Works everytime..
Click to expand...
Click to collapse
I tried that but my phone still not rooted, I've tried various methods and it still doesn't work I got the superuser app but still not root

Odd Kindle / Jelly Bean / Gapps issue

Recently put Jelly Bean on my Kindle - JB flashed, using TWRP, fine and runs great. Gapps will NOT flash, no matter which I use; it fails using TWRP each time, even after clearing cache and even redoing the whole install process.
I figured I would just sideload the Google Play store and any others I needed, but Google Play will not open once installed; it pops open for a split second then closes. I read that installing Talk and signing in would fix this, but after sideloading Talk it does the same thing.
So it seems no Google apps will sideload properly and I also am unable to flash any gapps.zip's.
Any idea? Did I miss something obvious?

Depends...are you using the CM10 gapps?
Also, what version of TWRP are you using?

Yes, CM10 (tried others too) and TWRP 2.

sleep_debt said:
Yes, CM10 (tried others too) and TWRP 2.
Click to expand...
Click to collapse
2.0? 2.1? 2.2?
Also, are you checking the md5s? It's a longshot but worth looking into.

Which version of gapps are you using?

TWRP 2.2 is what I'm using.
Not sure the gapps versions, but ive tried about 5 different ones. All from July and August.
What would I be checking in the md5's exactly?

sleep_debt said:
TWRP 2.2 is what I'm using.
Not sure the gapps versions, but ive tried about 5 different ones. All from July and August.
What would I be checking in the md5's exactly?
Click to expand...
Click to collapse
Make sure it's this version.
http://goo.im/gapps/gapps-jb-20120726-signed.zip
Sent from my Nexus 7 using Tapatalk 2

TWRP 2.2 is still quite new and it is yet unknown of all the bugs that may come with it. Have you tried an earlier version?

Did you find a solution to your problem yet?
sleep_debt said:
Recently put Jelly Bean on my Kindle - JB flashed, using TWRP, fine and runs great. Gapps will NOT flash, no matter which I use; it fails using TWRP each time, even after clearing cache and even redoing the whole install process.
I figured I would just sideload the Google Play store and any others I needed, but Google Play will not open once installed; it pops open for a split second then closes. I read that installing Talk and signing in would fix this, but after sideloading Talk it does the same thing.
So it seems no Google apps will sideload properly and I also am unable to flash any gapps.zip's.
Any idea? Did I miss something obvious?
Click to expand...
Click to collapse
Hi sleep_debt, I was wondering if you have found a solution to this problem yet. I am also having a problem getting access to Google Play. I've tried loading multiple versions of GoogleServicesFramework.apk and Vending.apk, etc. I am able to get them to install, but when I open the "Market" icon it prompts me to create an account and sign in, but it is never able to make the connection. I am also confused by references to the "Google Play" store. I don't have anything called "Google Play" I only have an icon called "Market". So, I think I'm missing something, but I don't know what.
Val

vmallder
vmallder said:
Hi sleep_debt, I was wondering if you have found a solution to this problem yet. I am also having a problem getting access to Google Play. I've tried loading multiple versions of GoogleServicesFramework.apk and Vending.apk, etc. I am able to get them to install, but when I open the "Market" icon it prompts me to create an account and sign in, but it is never able to make the connection. I am also confused by references to the "Google Play" store. I don't have anything called "Google Play" I only have an icon called "Market". So, I think I'm missing something, but I don't know what.
Val
Click to expand...
Click to collapse
Which ROM did you use? The two ROMs I have tried both had an accompanying gapps zip file. I'm using TWP installed by KFU 0.9.6. I installed cm-10 from sgt7-linaro and jdaycane 1.7.2. I flashed the gapps ROM at the same time using TWRP and had no issues.

vmallder said:
Hi sleep_debt, I was wondering if you have found a solution to this problem yet. I am also having a problem getting access to Google Play. I've tried loading multiple versions of GoogleServicesFramework.apk and Vending.apk, etc. I am able to get them to install, but when I open the "Market" icon it prompts me to create an account and sign in, but it is never able to make the connection. I am also confused by references to the "Google Play" store. I don't have anything called "Google Play" I only have an icon called "Market". So, I think I'm missing something, but I don't know what.
Val
Click to expand...
Click to collapse
nmaiorana said:
Which ROM did you use? The two ROMs I have tried both had an accompanying gapps zip file. I'm using TWP installed by KFU 0.9.6. I installed cm-10 from sgt7-linaro and jdaycane 1.7.2. I flashed the gapps ROM at the same time using TWRP and had no issues.
Click to expand...
Click to collapse
Not sure what this issue is, still - have tried every gapps & TWRP version I could find, but TWRP also throws an error when trying to flash gapps.
Also, sideloading the gapps just doesnt work, either, making me think the actual OS flash might be damaged? Been busy lately but plan on just flashing another OS and seeing if that clears it up.
If anyone has any other tips, it would be much appreciated!

Update:
Spent the weekend trying to re-root, flash Jellybean/Gapps to no avail. Same results (when Jelly bean is installed, Gapps will not flash using TWRP 2.2.2). I then wiped everything, leaving only TWRP. Cleared all caches, etc and tried to re-flash Jellybean; now NOTHING will flash successfully and there is no OS anymore, just TWRP.
How can I get an OS back on if TWRP isnt cooperating?

What errors do you get when trying to flash gapps or ROMs?

sleep_debt said:
Update:
Spent the weekend trying to re-root, flash Jellybean/Gapps to no avail. Same results (when Jelly bean is installed, Gapps will not flash using TWRP 2.2.2). I then wiped everything, leaving only TWRP. Cleared all caches, etc and tried to re-flash Jellybean; now NOTHING will flash successfully and there is no OS anymore, just TWRP.
How can I get an OS back on if TWRP isnt cooperating?
Click to expand...
Click to collapse
i would try adb installing twrp 2.2.2.1 and then flashing a rom, i read that the update fixed some issues that your probably having.

callmeshulah said:
i would try adb installing twrp 2.2.2.1 and then flashing a rom, i read that the update fixed some issues that your probably having.
Click to expand...
Click to collapse
That's the version of TWRP I'm using; the error I'm getting when flashing anything is:
* Verifying filesystems...
* Verifying partition sizes...
Error flashing zip 'whateverthefileis.zip'

TWRP errors
I agree with nmaiorana, cm-10 from linaro is not throwing errors like you seem to be running into. Latest version I am using is: 10-20120831-2228. the gapps v that works with this rom is: gapps-jb20120726. In TWRP after clearing cache and dalvik cache, goto to Install, click on the ROM you want to install, then go back to install and click on the gapps file, then slide the button to the right. You can install multiple flash files this way in TWRP. See if that works.
[email protected]@dog

If you've tried reinstalling every version of TWRP and you have tried installing different ROMs and they all return the exact error you posted, try this:
fastboot oem format
...and then reinstall TWRP. If that doesn't work, fastboot may not be working to correctly flash information to the recovery partition. If that's the case you may need to replace your bootloader, but not with fastboot. TWRP probably wouldn't work either and you don't want to open the case to do the shorting trick unless you have to.
My suggestion would be to use adb to install TWRP and see if that makes a difference. If that works and you can flash ROMs normally, replace your bootloader right away.
At least that's what I would try.

Pull the recovery log and see if it gives you more details on what's causing the flash to fail...
Attempt to install the gapps package. After it fails, run the following adb command
Code:
adb pull /cache/recovery/last_log recovery_log.txt
You'll find the recovery_log.txt file in your current working directory. Copy and paste the contents of the log file into pastebin.com and share the URL here.

soupmagnet said:
If you've tried reinstalling every version of TWRP and you have tried installing different ROMs and they all return the exact error you posted, try this:
fastboot oem format
...and then reinstall TWRP. If that doesn't work, fastboot may not be working to correctly flash information to the recovery partition. If that's the case you may need to replace your bootloader, but not with fastboot. TWRP probably wouldn't work either and you don't want to open the case to do the shorting trick unless you have to.
My suggestion would be to use adb to install TWRP and see if that makes a difference. If that works and you can flash ROMs normally, replace your bootloader right away.
At least that's what I would try.
Click to expand...
Click to collapse
kinfauns said:
Pull the recovery log and see if it gives you more details on what's causing the flash to fail...
Attempt to install the gapps package. After it fails, run the following adb command
Code:
adb pull /cache/recovery/last_log recovery_log.txt
You'll find the recovery_log.txt file in your current working directory. Copy and paste the contents of the log file into pastebin.com and share the URL here.
Click to expand...
Click to collapse
will try these in the next few days and see if anything works.
btw, ive tried every recent rom/gapps with no luck, so it doesnt seem to be a version-issue.

[Q] Link2SD Uninstall

Out of curiosity I installed link2sd and my device status immediately changed to modified. I uninstalled link2sd but still it is modified. Usually whenever I installed any root application status used to change to modified and when I uninstall it used to change back to normal. But with link2sd it is still modified. Can somebody tell me how to completely remove link2sd so that I get the status back to normal? somehow I am not getting courage to use triangle away

It's not related to triangle away.
Flashing a stock rom helps
Sent From Samsung's Galaxy Note II Using Internet

raj_k_r said:
Out of curiosity I installed link2sd and my device status immediately changed to modified. I uninstalled link2sd but still it is modified. Usually whenever I installed any root application status used to change to modified and when I uninstall it used to change back to normal. But with link2sd it is still modified. Can somebody tell me how to completely remove link2sd so that I get the status back to normal? somehow I am not getting courage to use triangle away
Click to expand...
Click to collapse
Or you could try a Factory Data Reset. That may clear it. It worked for me after rooting with CF Autoroot.

Thank You, I will try tonight and update you
One more question, Kies has detected a new firmware but it says if device is rooted, update might fail. Is it so? Can I update without removing root?
and these are the files added/modified by link2sd
debuggerd from system/bin and
install-recovery.sh and install-recovery.sh.ori from system/etc
I am not sure what to do with these. Can anybody suggest. I want to keep flashing through ODIN as the last option and factory resetting wont remove these files. I believe samsung does not use install-recovery.sh. Can I just delete these files in that case?

norm2002 said:
Or you could try a Factory Data Reset. That may clear it. It worked for me after rooting with CF Autoroot.
Click to expand...
Click to collapse
Still it says modified after Factory resetting

Deleting them will get you a modified status.
Rename them to default.
They restore the default recovery if it had been changed on boot.
You need to remove root.
And have both stock recovery and kernel.
I have 0 counter and official binary and status in download mode.
But settings show device status modified.
Go to supersu and select full unroot.
It will reboot and you will get default status.
Also disable any app that uses root.
Like disabling and restoring and mods.
Last resort is to do factory res reset and then flash stock rom.
Sent from my GT-N7100 using xda app-developers app

UtkarshGupta said:
Deleting them will get you a modified status.
Rename them to default.
They restore the default recovery if it had been changed on boot.
You need to remove root.
And have both stock recovery and kernel.
I have 0 counter and official binary and status in download mode.
But settings show device status modified.
Go to supersu and select full unroot.
It will reboot and you will get default status.
Also disable any app that uses root.
Like disabling and restoring and mods.
Last resort is to do factory res reset and then flash stock rom.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Thank you but can you check and let me know whether you also have these files? If you have, can you share them here? I dont mind experimenting but I would like to flash stock ROM only when Samsung releases 4.2. Till then I can keep on experimenting with.

raj_k_r said:
Thank you but can you check and let me know whether you also have these files? If you have, can you share them here? I dont mind experimenting but I would like to flash stock ROM only when Samsung releases 4.2. Till then I can keep on experimenting with.
Click to expand...
Click to collapse
I've got the same problem now. Didn't know about JB ROM's not supporting app2sd, and followed a forum's advise to use Link2SD instead. Ended up with Link2SD not working (standard mount of Link2SD very likely already used by the OS itself), and tried to get rid of the scripts it installs in the system.
But no got. Since there is no documentation and no real uninstaller, you end up with messed up scripts in your system folders.
The system modified status won't go away anymore.
I could correct the scripts Link2SD modifies myself (I'm used to do such things in Linux), but I'd need to know, what exactly has changed...
Is there anyone who could help?

moving to rbox custom rom from stock rooted

I am on rooted 51.1.1.0_user_511070220 (last rootable version), with the dcp amazon update disabled.
I would like to do a clean move to the unlocked bootloader, clockworkmod, latest rbox custom rom, and then finally playstore.
I have the following questions, and would like to get it clarified before I start the procedure.
1. In order to unlock the bootloader and then install clockworkmod I follow this:
http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/
2. I want to do a clean install. So, which things I have to wipe in clockworkmod?
3. After wipe, I install the rom using:
http://www.aftvnews.com/how-to-install-a-custom-rom-image-on-the-amazon-fire-tv/
My question is - in step 2, if I wipe everything, how do I get the rom image on to the fire tv. Or, do you recommend that a wipe is NOT necessary?
Also, in this case, do I have to do the disable dcp amazon update again?
4. Also, where can I find the latest playstore apks? I am thinking of going with this:
http://forum.xda-developers.com/fire-tv/help/help-install-google-playstore-t2933189
Thanks.

OK since no one replied I did NOT wipe.
Downgraded, unlocked boot loader, installed cwm, installed custom ROM. Works great. Thank you rbox.
My SuperSU now cannot be started. I can't uninstall/reinstall it either via apk. I read that few others have this problem as well.
Once I get that fixed, next is play store.
Thanks.

deepasadish said:
OK since no one replied I did NOT wipe.
Downgraded, unlocked boot loader, installed cwm, installed custom ROM. Works great. Thank you rbox.
My SuperSU now cannot be started. I can't uninstall/reinstall it either via apk. I read that few others have this problem as well.
Once I get that fixed, next is play store.
Thanks.
Click to expand...
Click to collapse
No one replied most likely because all your questions have been answered in the various threads about them.
And yes, currently the SuperUser can't be opened, but seems to work just fine. Do you need to go into it's settings? It shouldn't be holding you back from installing or doing anything.

nyder said:
No one replied most likely because all your questions have been answered in the various threads about them.
And yes, currently the SuperUser can't be opened, but seems to work just fine. Do you need to go into it's settings? It shouldn't be holding you back from installing or doing anything.
Click to expand...
Click to collapse
Sorry I have read almost every post and can't find info about the wipe. Anyways I will do that later as it is not important right now.
Regarding SuperSU, yes I can't open it. I only have the force stop, clear cache, clear data options for it. Obviously I can't uninstall and reinstall it either. I downloaded the SuperSU zip, but decided against flashing it in cwm.
Having said that, I do think I have root. When I type su in adb I do get root and see the message root granted on the screen. However it is not asking me whether to give su permission or not.
edit - i did clear data for supersu and then if I type su in adb, then i get the popup. so, i guess it was just remembering previous settings and granted automatically. i still can't open supersu though. thanks.

Here's the thread: http://forum.xda-developers.com/fire-tv/help/supersu-t2926119.
You can download a different version of su. (Direct download link is in the thread.) This is not the chainfire version. This version will open, allow you to set defaults, etc. Be aware that the screen is very low contrast and hard to read. You need to look carefully.
BTW, both versions seem to coexist peacefully.