Related
Thanks for taking an interest in my problem and trying to help.
Here's what I've figured out. I tried doing Toast's root method for linux and the directions weren't idiot proof because I screwed them up. I've explained how far I've gotten in other threads. If that's relevant just ask and I'll explain exactly what I did.
Anyway my phone does the basics. It allows me to make phone calls, text, and look at the internet on the phone so this isn't an emergency but it I am worse off than I was before I tried to root because I can no longer use easytether.
I had no problem with easytether prior to the root attempt, and it still works when I hook it up with my wifes untampered evo. with my phone but with my wife's evo, I've never messed with that one, I have no trouble connecting with easy tether.
Some of the things I've noticed about the device since the attmept...
-I can't update to 2.2 via the OTA or any other method, my device says no updates are available.
-Simple root wasn't so simple, the phone never shut off and rebooted into boot screen like the red screen said it would in step 1.
How do I reset the device to the way it was the day it was purchased. I've got everything I need backed up. I'm ready to reset just tell me how.
Thanks.
Please?
I know it bothers people here when they think someone didn't research anything first but I really did. The problem was I'm on linux so most of the stuff I researched didn't seem to apply, not to mention I'm quite illiterate in the terminal... but working on it. I'd really like to get this phone back to stock so I can try again.
Can anyone help?
what ROM are you running? base on eclair 2.1 or froyo 2.2..
try this http://shipped-roms.com/index.php?category=android&model=Supersonic
They are the Stock Unmodified ROMs for your EVO 4G the first 3 are Eclair (2.1) and the last 2 are Froyo (2.2)
Just know that if you use any of this you will LOSE Root..
Hope it helps..
I recomend you try 1.47.651.1 first ...
Good Luck
hortstu said:
Thanks for taking an interest in my problem and trying to help.
Here's what I've figured out. I tried doing Toast's root method for linux and the directions weren't idiot proof because I screwed them up. I've explained how far I've gotten in other threads. If that's relevant just ask and I'll explain exactly what I did.
Anyway my phone does the basics. It allows me to make phone calls, text, and look at the internet on the phone so this isn't an emergency but it I am worse off than I was before I tried to root because I can no longer use easytether.
I had no problem with easytether prior to the root attempt, and it still works when I hook it up with my wifes untampered evo. with my phone but with my wife's evo, I've never messed with that one, I have no trouble connecting with easy tether.
Some of the things I've noticed about the device since the attmept...
-I can't update to 2.2 via the OTA or any other method, my device says no updates are available.
-Simple root wasn't so simple, the phone never shut off and rebooted into boot screen like the red screen said it would in step 1.
How do I reset the device to the way it was the day it was purchased. I've got everything I need backed up. I'm ready to reset just tell me how.
Thanks.
Click to expand...
Click to collapse
I bet a friend told you about root without giving you all the details, right? Haha. Ok, back to business. Rooting will make it impossible to receive ota updates. This is not a problem, because devs post rooted ota updates that you can flash manually. As far as I know, root is 100% permanent, but you don't know the goods. First of all, search wireless tether root in market it should have a green wifi icon. Second, try some custom roms and themes. I bet you will cry when you see yourself asking to go back to stock....
jadehawk said:
what ROM are you running? base on eclair 2.1 or froyo 2.2..
try this http://shipped-roms.com/index.php?category=android&model=Supersonic
They are the Stock Unmodified ROMs for your EVO 4G the first 3 are Eclair (2.1) and the last 2 are Froyo (2.2)
Just know that if you use any of this you will LOSE Root..
Hope it helps..
I recomend you try 1.47.651.1 first ...
Good Luck
Click to expand...
Click to collapse
I never got to the point where I could flash a ROM or got root. S was never off.
just in case it makes a difference.
firmware= 2.1-update1
baseband version= 1.39.00.04.26
kernel version= 2.6.29-a2443432
build#= 1.32.651.1 CL171253 test-keys
software#= 1.32.651.1
I think the rest is up to date.
I bet a friend told you about root without giving you all the details, right? Haha.
Click to expand...
Click to collapse
Actually I'm a bit of a forum junkie and as soon as I got this phone I found the android forums and have spent a ton of time there trying to maximize the utility of this device. I've done the opposite.
Ok, back to business. Rooting will make it impossible to receive ota updates. This is not a problem, because devs post rooted ota updates that you can flash manually. As far as I know, root is 100% permanent, but you don't know the goods. First of all, search wireless tether root in market it should have a green wifi icon. Second, try some custom roms and themes. I bet you will cry when you see yourself asking to go back to stock....
Click to expand...
Click to collapse
I only want to go back to stock so I can get rooted! I can't root because I can't get 2.2 so I can't use unrevoked 3.21. I can't use simple because of some problem I had with the toast linux method that seems to be screwing up everything since. I appreciate the input I hope I've explained myself better.
hortstu said:
Please?
I know it bothers people here when they think someone didn't research anything first but I really did. The problem was I'm on linux so most of the stuff I researched didn't seem to apply, not to mention I'm quite illiterate in the terminal... but working on it. I'd really like to get this phone back to stock so I can try again.
Can anyone help?
Click to expand...
Click to collapse
Use this to go back to stock: http://forum.xda-developers.com/showthread.php?t=780141
grouse130 said:
Use this to go back to stock: http://forum.xda-developers.com/showthread.php?t=780141
Click to expand...
Click to collapse
The problem is I don't think I'm rooted.I flashed pc36img.zip and never made it any further. Am I rooted. Do I need to undo this or can I do a hard reset?
grouse130 said:
Use this to go back to stock: http://forum.xda-developers.com/showthread.php?t=780141
Click to expand...
Click to collapse
OK so here's why I think I'm not rooted, when I follow step one of the detailed directions,
Power off the phone and reboot into the recovery by holding VOL DOWN + POWER until it boots to the white screen. Then select RECOVERY.
Click to expand...
Click to collapse
I get a screen with an evo, a red triangle, and a red exclamation point.
Where do I go from here?
Any direction will be immensely appreciated.
To find out if you're rooted, simply try to run an app that requires root access. Try downloading Titanium back up, and as soon as you install it, hit the "Problem?" button on the lower right and install busybox. One of the first lines on the main screen of the app says:
Root access => OK (Busybox 1.16.0 from app)
If it does not say "root access => OK" and you cannot use the app, then you don't have root.
hortstu said:
OK so here's why I think I'm not rooted, when I follow step one of the detailed directions,
I get a screen with an evo, a red triangle, and a red exclamation point.
Where do I go from here?
Any direction will be immensely appreciated.
Click to expand...
Click to collapse
From this screen, if you hold volume up and press the power key, it will take you to the hboot menu.
Have you flashed a recovery img?
Sent from my PC36100 using XDA App
rugedraw said:
From this screen, if you hold volume up and press the power key, it will take you to the hboot menu.
Click to expand...
Click to collapse
OK so I'm at the "hboot" screen.
Code:
Android system recovery <2e>
Use volume...
click power key...
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
Then in yellow, below the device picture, triangle, and exclamation I have
Code:
E: Can't open /cache/recovery/command
Not sure where you're steering me rugedraw but thanks for the help...
hortstu said:
OK so I'm at the "hboot" screen.
Code:
Android system recovery <2e>
Use volume...
click power key...
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
Then in yellow, below the device picture, triangle, and exclamation I have
Code:
E: Can't open /cache/recovery/command
Not sure where you're steering me rugedraw but thanks for the help...
Click to expand...
Click to collapse
To check if you are rooted. Download "Terminal Emulator" on the market. If it starts up and when it is done booting, you get a # prompt, you are rooted. If you get a $ prompt. You are not rooted.
You also do not have a custom recovery installed on your phone (the recovery screen you have is the stock one). Try finishing up the process by doing Toast part II -- http://forum.xda-developers.com/showthread.php?t=701835&highlight=Part-2
To find out if you're rooted, simply try to run an app that requires root access. Try downloading Titanium back up, and as soon as you install it, hit the "Problem?" button on the lower right and install busybox. One of the first lines on the main screen of the app says:
Root access => OK (Busybox 1.16.0 from app)
If it does not say "root access => OK" and you cannot use the app, then you don't have root.
Click to expand...
Click to collapse
Finally went back and checked on the titanium backup download. When I first opened it I got the message that it didn't have root access. So I clicked on "problems?" and installed busy box. Now it says,
Root access v=> OK (BusyBox 1.16.0 from app
Click to expand...
Click to collapse
Plus some other stuff... so I guess I have root but not S-off.
hecklbrg said:
To check if you are rooted. Download "Terminal Emulator" on the market. If it starts up and when it is done booting, you get a # prompt, you are rooted. If you get a $ prompt. You are not rooted.
Click to expand...
Click to collapse
Should I still do this or is the info from titanium backup enough?
You also do not have a custom recovery installed on your phone (the recovery screen you have is the stock one). Try finishing up the process by doing Toast part II -- http://forum.xda-developers.com/showthread.php?t=701835&highlight=Part-2
Click to expand...
Click to collapse
Yes I tried doing that but like I said I'm on a linux computer and had some trouble with the steps. What I'd really like to do is just go back to stock and try rooting with unrevoked 3.21.
My concern is that selecting factory reset from the hboot screen won't take me back there. If it did I could probably get the 2.2 update over the air, I suppose now I have to worry about getting this other update that everyone is talking about at the same time. Can I get 2.2 and avoid the update that came out last night? How.
Will a factory reset get me back to stock? I've already got everything backed up that matters.
Thanks for all the help.
OK...I think this should work for you:
go here and download the file on the page:
WRONG FILE>>>WILL FIND THE CORRECT ONE.
rename it update.zip and put it on the root of your SD card.
Boot into HBOOT then into recovery and go to apply update.zip -- choose the file you put on there.
let it run and you should have the stock non-rooted version of the 1st software release from sprint. from there you can update it as far as you want to root it the method of your choice.
hecklbrg said:
OK...I think this should work for you:
go here and download the file on the page:
WRONG FILE>>>WILL FIND THE CORRECT ONE.
rename it update.zip and put it on the root of your SD card.
Boot into HBOOT then into recovery and go to apply update.zip -- choose the file you put on there.
let it run and you should have the stock non-rooted version of the 1st software release from sprint. from there you can update it as far as you want to root it the method of your choice.
Click to expand...
Click to collapse
Thanks hecklbrg,
I assume since I'm half rooted a factory reset won't get me there?
I'll wait for the link to that file...
if you put this on your card and run it from HBOOT...you will get a rooted version of the latest sprint OTA with a custom recovery and the latest radios.
http://forum.xda-developers.com/showthread.php?t=791019
I'm still looking for a non-rooted version to run...but I would think this would work for you to get you the latest OTA in a rooted form.
Second thing is that I don't think you really screwed up your root process. You have only done part of the process and haven't installed a custom recovery. If this works for you, it will give you a custom recovery and you will have a fully rooted phone.
Hecklberg is right. I don't think you even need to rename it update.zip. If its a
pc36img.zip your hboot will automatically scan for it, find it and run it when you put it on your SD card and open hboot.
Also consider, I rooted my phone without any computer, all done from my Evo, using fastRX8 thread in here about how to root for newbies. It involves putting the files on your SD card, then installing terminal emulator from the market and typing a few commands to install flash_image, then custom recovery. You are root, just don't have flash image, custom recovery, and superuser yet. Basically toast part 2, it can be done with no computer, but same files.
Read real quick Whitslack thread on rooting, and fastrx8 thread, even just the 1st post, and it will make sense to you where you're at and what's left to do. You'll see how close you are.
Once root, and superuser installed, you won't need easy tether, Android wired tether is what I use (doesn't require installing any software on the host pc)
(Actually, if you use the threads I mentioned method, don't use the recovery amonra1.7.0.2, there's a newer one to download, its at 1.8 now, just Chang the recovery file name you type in terminal app accordingly-don't worry, it won't go thru if you do it wrong, but won't 'break' anything)
Hope any of this helps, but yeah, hecklberg is right too, just different methods. One requires no computer.
And yeah, with the devs around here, you don't need any Sprint OTAs, most of the time, they seem to have em available before Sprint releases them. These guys are good.
scottspa74 and hecklbrg,
Thanks for the help. I havent had time to look at this or act on it over the last 24 hours but I will try to get to it tonight and let you know how it works. Sounds like you've gotten me out of the woods.
Thanks again.
I think it is $ if you are rooted and# if you aren't because I know I'm rooted and it shows money signs, unless terminal emulator is messed up,i have nvr used it.
hecklbrg said:
To check if you are rooted. Download "Terminal Emulator" on the market. If it starts up and when it is done booting, you get a # prompt, you are rooted. If you get a $ prompt. You are not rooted.
You also do not have a custom recovery installed on your phone (the recovery screen you have is the stock one). Try finishing up the process by doing Toast part II -- http://forum.xda-developers.com/showthread.php?t=701835&highlight=Part-2
Click to expand...
Click to collapse
Sent from my netarchy_toast, froyo beast of a machine evo!
evohack99 said:
I think it is $ if you are rooted and# if you aren't because I know I'm rooted and it shows money signs, unless terminal emulator is messed up,i have nvr used it.
Sent from my netarchy_toast, froyo beast of a machine evo!
Click to expand...
Click to collapse
Nope you are incorrect my friend.. try typing " su " on the terminal emulator see if you get the "#" ... # ==> Root and $ ===> User(I Think) But I know for sure "#" is root access
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.
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.
Hi all,
I've followed with meticulous care the video and web page over at aftvnews for rooting my aftv2...
Everything went perfectly, up to one point,... Instead of just flashing the sloane-5.0.5-rooted_r4.zip (I also placed a check in the checksum box).... strangely it failed the checksum,.... and I decided to choose to reboot.
After checking the sloane-5.0.5-rooted_r4.zip md5 it was okay.... strangely i don't know why it failed.
But now all my firetf2 does is boot directly to the amazon home page. (I still have adb and usb debugging enabled).
All I had connected to the firetv2 was a usb mouse to enable me to click the relevant items within recovery.
Is there any way I can get back into the first TeamWin boot window so that I can actually flash the sloane-5.0.5-rooted_r4.zip file.
I did have a usb hub connected as well, with a usb keyboard just in case I needed it, but thought that it might be the problem so i just left the mouse connected.
Every single part went through perfectly installing adb and fastboot,... installing the mt6577 usb drivers.
connecting the firetv2 via a to a cable, and also running the install_firetv2_recovery.bat file.
Not one single problem until this last bit.
Could do with a couple of pointers please chaps as i can almost see the finish line.
---------------
hhmmmm I rather stupidly left the ramdisk-recovery.cpio.lzma file off the SD card when I wanted to get back into the boot menu.
This time the checksum passed, and rooted firmware went on without any problems.
about to click "reboot system" in preparation of crapping myself....
Hoping that someone can see the final screen attached and tell me if this is okay..
slackbladder said:
Hi all,
I've followed with meticulous care the video and web page over at aftvnews for rooting my aftv2...
Everything went perfectly, up to one point,... Instead of just flashing the sloane-5.0.5-rooted_r4.zip (I also placed a check in the checksum box).... strangely it failed the checksum,.... and I decided to choose to reboot.
After checking the sloane-5.0.5-rooted_r4.zip md5 it was okay.... strangely i don't know why it failed.
But now all my firetf2 does is boot directly to the amazon home page. (I still have adb and usb debugging enabled).
All I had connected to the firetv2 was a usb mouse to enable me to click the relevant items within recovery.
Is there any way I can get back into the first TeamWin boot window so that I can actually flash the sloane-5.0.5-rooted_r4.zip file.
I did have a usb hub connected as well, with a usb keyboard just in case I needed it, but thought that it might be the problem so i just left the mouse connected.
Every single part went through perfectly installing adb and fastboot,... installing the mt6577 usb drivers.
connecting the firetv2 via a to a cable, and also running the install_firetv2_recovery.bat file.
Not one single problem until this last bit.
Could do with a couple of pointers please chaps as i can almost see the finish line.
---------------
hhmmmm I rather stupidly left the ramdisk-recovery.cpio.lzma file off the SD card when I wanted to get back into the boot menu.
This time the checksum passed, and rooted firmware went on without any problems.
about to click "reboot system" in preparation of crapping myself....
Hoping that someone can see the final screen attached and tell me if this is okay..
Click to expand...
Click to collapse
Are you installing sloane-5.0.5-rooted_r4.zip from recovery?
It looks like it installed OK but even so if you already have recovery installed you still have a way back in.....so no worry.
That's what I was gonna say, seems ok to me?
If it won't boot Into recovery or won't boot follow this guide here -
http://forum.xda-developers.com/fire-tv/development/firetv-2-unbrick-image-t3313349
But if you can access recovery with a keyboard press or via adb just follow the guide on aftvnews but since you have already tried to root don't use the installer just flash the prerooted rom (if needed redownload the zip check the md5 checksums & flash In recovery)
Thanks for the details chaps....
I persevered and following the detailed info from aftvnews I used the cmd and typed su..... after pressing enter i had about 3 seconds before the little box that you have to press on "enable" disappeared... managed it on my third attempt. I don't remember reading that one has to use the firetv remote to click on "Enable". but it worked.
command prompt says [email protected] so it looks to be successful.
also blocked updates as well. now if only i could root my firetv v1's i could get rid of opendns.
but using the calculator over at aftvnews (when I could get on there} states that both my firetv1's are not rootable versions due to the serial numbers.
just one other thing chaps.... to be able to load rbox's twrp,.... is that only possible via an sd card plugged in and using ramdisk-recovery.cpio.lzma and then switching on firetv?
just wondering chaps.... are there any uk people here who can still access aftvnews. I only ask as the site went down last night about 3.30 am gmt.
I've had a mate whose on BT and he has full access another mate on sky tested it for me and its okay.
I can access it if I use Tor Browser but other than that it keeps timing out on me and I'm on vermin..
Another piece I almost got lost at, was where you have to click on the three arrows "Swipe to confirm" well I thought it had gone wrong on the page before that, due to another blue page with arrows on..... no mention of that in the video.
Now after all that,.. I assume I still have to sideload kodi?
slackbladder said:
Thanks for the details chaps....
I persevered and following the detailed info from aftvnews I used the cmd and typed su..... after pressing enter i had about 3 seconds before the little box that you have to press on "enable" disappeared... managed it on my third attempt. I don't remember reading that one has to use the firetv remote to click on "Enable". but it worked.
command prompt says [email protected] so it looks to be successful.
also blocked updates as well. now if only i could root my firetv v1's i could get rid of opendns.
but using the calculator over at aftvnews (when I could get on there} states that both my firetv1's are not rootable versions due to the serial numbers.
just wondering chaps.... are there any uk people here who can still access aftvnews. I only ask as the site went down last night about 3.30 am gmt.
I've had a mate whose on BT and he has full access another mate on sky tested it for me and its okay.
I can access it if I use Tor Browser but other than that it keeps timing out on me and I'm on vermin..
Another piece I almost got lost at, was where you have to click on the three arrows "Swipe to confirm" well I thought it had gone wrong on the page before that, due to another blue page with arrows on..... no mention of that in the video.
Now after all that,.. I assume I still have to sideload kodi?
Click to expand...
Click to collapse
You lost me here but glad you managed to finish the installation.
BTW if your FireTv1 is on OS5 you can rooted with kingroot. You need to provide more info to be able to help you furthermore.
Now youve rooted dont forget to block updates via adb! You need a keyboard to access twrp like I said before, no sd card In the aftv2 doesn't matter, you can still access twrp. Yes you can root the aftv gen 1 using Kingroot (please do not use super sume afterwards people have bricked after using super sume!) Block updates & wait for the recovery & prerooted rom by rbox to be released. Yes of course you need to sideload Kodi if you want to, Kodi is not suppled with any root/recovery or rom. Sideload via your phone/adb/adbfire/ftp or es file explorer.
Sent from my SM-G900F using Tapatalk
Thanks bula1ca,
I Updated one firetv1 the other day to 5.0.5 and then pulled the plug..... I'm hoping that rbox will come up with a working rom that i can use.
for the time being my other firetv1 is using 51.1.6.3. (it seems a lot smoother than 5.0.5). or maybe that's just me.
the firetv2 had two ota updates to get to 5.0.5. I had a little panic, I was expecting another update to block the rooting process.
also I was rather surprised how easy it was to root,... I think if i had to do it again,... instead of the 8 hours it took me, it would be more like 45 minutes now... lol
I must admit that I was constantly checking every little thing I was doing.... writing down notes for reference and trying to look at half a dozen open web pages to see how others had done it.
Going to be a problem for me though if I cannot access aftvnews any more....
---------------------------------
Thanks for the info deanr1977,...
I did try to use a keyboard but the firetv2 just kept on booting all the way to the home screen no matter what i did.
This was before I had actually installed the rom though, so this may well explain why I could get to the twrp recovery menu.
Is there a time limit as to how quickly you have to press a particular set of keys on a keyboard to get the recovery menu to show up?
slackbladder said:
Thanks bula1ca,
I Updated one firetv1 the other day to 5.0.5 and then pulled the plug..... I'm hoping that rbox will come up with a working rom that i can use.
for the time being my other firetv1 is using 51.1.6.3. (it seems a lot smoother than 5.0.5). or maybe that's just me.
the firetv2 had two ota updates to get to 5.0.5. I had a little panic, I was expecting another update to block the rooting process.
also I was rather surprised how easy it was to root,... I think if i had to do it again,... instead of the 8 hours it took me, it would be more like 45 minutes now... lol
I must admit that I was constantly checking every little thing I was doing.... writing down notes for reference and trying to look at half a dozen open web pages to see how others had done it.
Going to be a problem for me though if I cannot access aftvnews any more....
Click to expand...
Click to collapse
Sure it will be back up soon, I'm in the UK & can access it fine so just sure it will only be a matter of time & it will be back up & running at your end?
Sent from my SM-G900F using Tapatalk
deanr1977 may I ask are you a vermin media customer? I'm trying to find out why it's only me.
slackbladder said:
deanr1977 may I ask are you a vermin media customer? I'm trying to find out why it's only me.
Click to expand...
Click to collapse
you mean Virgin Media? yes
You have around 10 or 6 seconds to select boot normal to the left or boot to twrp to the right.
I use a Logitech K400 plus keyboard, works perfectly & also has a touch keypad which comes in very handy to those apps which need a mouse to access.
This one here -
http://www.amazon.co.uk/Logitech-Wireless-Keyboard-QWERTY-Layout/dp/B00XJ3LVPI
No honestly mate.... i really do mean vermin... ever since they took over I've had no end of problems. I'd laugh if I could but it just isn't funny.
I had a look at one of those k400's in a local pcworld.... but they were asking well over the odds. I think I might go down the amazon route. cheers also for the info on the boot timing.
slackbladder said:
No honestly mate.... i really do mean vermin... ever since they took over I've had no end of problems. I'd laugh if I could but it just isn't funny.
I had a look at one of those k400's in a local pcworld.... but they were asking well over the odds. I think I might go down the amazon route. cheers also for the info on the boot timing.
Click to expand...
Click to collapse
I'm not happy with there set top box's or interface, but the Internet been fine for me, very fast almost all the time
I gave up in the and had to call them....
basically done all i could at my end... flushdns,... checked hosts, checked opendns, turned off everything except router and new VM| router (modem only mode) and tried an ipad... nope still no good. all this after a full shut down of everything and two reboots.
tried my phone,.... yep you got it right, full access to aftvnews.
whats even more stupid is that I'm using part of my wifi to access the net due to the poor 3g signal and i can access aftvnews.
Well VM staff said there's nothing wrong with network, nothing wrong at my end, and if i want access to keep using tor browser.
that's not really what i wanted to hear.
but he did mention that my IP address may have been blocked at the other end. although I'm not to sure why.
I also read some info from Elias, owner of aftvnews here... http://www.esaba.com/blog/limitations-of-siteground-vps-cloud-hosting/
seems he's not very happy either.
I've asked a bt customer to check for me,.. all okay. a sky customer... all okay,... and also yourself....
This only ever happened to me once before and that was on a forum many years ago. The owner had to unblock me so I could access the website again.
within two weeks I had been blocked again.
My friend has a fire tv 2 box sloane.
we've tried everything to update including contacting Amazon support for remote assistance and factory resetting multiple times.
We can't use YouTube TV without updating.
I'm good with Android and kkow how to use adb.
Can I force flash the stock firmware to update past 5.2.6.0? If so how?
dovedescent7 said:
My friend has a fire tv 2 box sloane.
we've tried everything to update including contacting Amazon support for remote assistance and factory resetting multiple times.
We can't use YouTube TV without updating.
I'm good with Android and kkow how to use adb.
Can I force flash the stock firmware to update past 5.2.6.0? If so how?
Click to expand...
Click to collapse
I had a box the other week that was on 5.2.7.3 so the issue isn't if it only updates to your current version.
There may be a corrupted ota update apk in your build, have you made sure that ota updates are enabled in >settings>my firetv and tried the adb commands to make sure they are actually enabled?
Sent from my SM-G935F using Tapatalk
I haven't run adb commands on it yet nor any fire device only android phones. I don't physically get the box in my possesion again until this weekend.
That's why I'm asking though...
Can I simply flash firmware in the stock recovery? Like via USB?
Whats the gist of recovering this aftv besides factory reset in settings?
dovedescent7 said:
I haven't run adb commands on it yet nor any fire device only android phones. I don't physically get the box in my possesion again until this weekend.
That's why I'm asking though...
Can I simply flash firmware in the stock recovery? Like via USB?
Whats the gist of recovering this aftv besides factory reset in settings?
Click to expand...
Click to collapse
Sorry to hear the factory reset process didn't work for you, I suspect there may be a problem with the update protocol (either system or the ota apk). Maybe someone can correct me if I'm wrong?
Please Note :This method requires a Linux installation either on a pc or live USB.
To flash firmware to your device you will have to unlock it first as per OP unlock instructions.
Here:
https://forum.xda-developers.com/fire-tv/development/unbrick-fire-tv-stick-2-anti-rollback-t3986303
This will unlock your box bootloader and install TWRP.
After TWRP is installed you can then choose what ever firmware(s) pre rooted you want for the box.
The general unlocking process is quite simple. If your friend is game for it being opened, shorted and unlocked that is.
You will first have to get acquainted with adb and boot your pc from a Linux installation or Linux distro Live USB to complete the amonet script process.
(This is the amazing program that flashes the TWRP custom recovery to your device)
All of this may sound quite daunting and bewildering but this box is easy to unlock.
It is totally upto you but this is the only way I can see for you to gain control over your friends box and upgrade the firmware.
The guys here will be there should you need help at anytime.
Regards
R.
Sent from my SM-G935F using Tapatalk
Bertonumber1 said:
Sorry to hear the factory reset process didn't work for you, I suspect there may be a problem with the update protocol (either system or the ota apk). Maybe someone can correct me if I'm wrong?
Please Note :This method requires a Linux installation either on a pc or live USB.
To flash firmware to your device you will have to unlock it first as per OP unlock instructions.
Here:
https://forum.xda-developers.com/fire-tv/development/unbrick-fire-tv-stick-2-anti-rollback-t3986303
This will unlock your box bootloader and install TWRP.
After TWRP is installed you can then choose what ever firmware(s) pre rooted you want for the box.
The general unlocking process is quite simple. If your friend is game for it being opened, shorted and unlocked that is.
You will first have to get acquainted with adb and boot your pc from a Linux installation or Linux distro Live USB to complete the amonet script process.
(This is the amazing program that flashes the TWRP custom recovery to your device)
All of this may sound quite daunting and bewildering but this box is easy to unlock.
It is totally upto you but this is the only way I can see for you to gain control over your friends box and upgrade the firmware.
The guys here will be there should you need help at anytime.
Regards
R.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Bummer, so the new methods referenced here in below link dont work then ?
AFTVnews is saying that i can root with new method?
Is this fake news? lol
https://www.aftvnews.com/amazon-fire-tv-2-box-running-latest-software-version-has-been-rooted/
.
.
.
.
dovedescent7 said:
Bummer, so the new methods referenced here in below link dont work then ?
AFTVnews is saying that i can root with new method?
Is this fake news? lol
https://www.aftvnews.com/amazon-fire-tv-2-box-running-latest-software-version-has-been-rooted/
.
.
.
.
Click to expand...
Click to collapse
No, it works up to 5.2.6.9
Sus_i said:
No, it works up to 5.2.6.9
Click to expand...
Click to collapse
I dont understand. Are you saying method WILL WORK for 5.2.6.0 or WILL NOT WORK for 5.2.6.0?
I am very familiar with Ubuntu Linux and adb..
dovedescent7 said:
I dont understand. Are you saying method WILL WORK for 5.2.6.0 or WILL NOT WORK for 5.2.6.0?
I am very familiar with Ubuntu Linux and adb..
Click to expand...
Click to collapse
As stated by @Sus_i the diplomatic mediatek exploit will only work upto version 5.2.6.9. Any higher version of fireos then you will have to use the hardware root, twrp method from the thread I posted above.
Good you are familiar with Ubuntu/Linux as the commands for the script will be run through terminal with the downloadable amonet script in the thread.
After you've installed/updated adb+fastboot py serial through command line of your Linux install. You're ready to open up your device, and refer to the dat0 located in the photo of OP
Sent from my SM-G935F using Tapatalk
Bertonumber1 said:
As stated by @Sus_i the diplomatic mediatek exploit will only work upto version 5.2.6.9. Any higher version of fireos then you will have to use the hardware root, twrp method from the thread I posted above.
Good you are familiar with Ubuntu/Linux as the commands for the script will be run through terminal with the downloadable amonet script in the the thread.
After you've installed/updated adb+fastboot py serial through command line of your Linux install. You're ready to open up your device, and refer to the dat0 located in the photo of OP
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Thank you. I get a little confused on version numbers with this thing. Does fire tv sw/fw go up like normal fw? Like does it go 5.2.6.0 then 5.2.6.1 and so on?
I have:
5.2.6.0 so this one can be done with software method?
5.2.7.4 this one has to be done by shorting internal stuff+linux right?
dovedescent7 said:
Thank you. I get a little confused on version numbers with this thing. Does fire tv sw/fw go up like normal fw? Like does it go 5.2.6.0 then 5.2.6.1 and so on?
I have:
5.2.6.0 so this one can be done with software method?
5.2.7.4 this one has to be done by shorting internal stuff+linux right?
Click to expand...
Click to collapse
Yes I had to edit the post there as i got confused myself, I had wrote 5.2.7.0 lol.
So just to clarify 5.2.6.9 and under you can use mediatek software root.
5.2.7.0 and over requires the hardware short method.
Sent from my SM-G935F using Tapatalk
dovedescent7 said:
I dont understand. Are you saying method WILL WORK for 5.2.6.0 or WILL NOT WORK for 5.2.6.0?
Click to expand...
Click to collapse
Lets say, it 'should' work :good:
I don't know if someone tested it on your OS version, because it's much older than the exploit itself.
The most current OS version back then was 5.2.6.8, the mtk root method came up and everybody was happy, finally a new root method for the second gen box
Big A patched it with 5.2.7.0.
Needless to say that most people tested it on 5.2.6.8 and .9.
It may be that the exploit isn't adapted to your OS version, but who knows.
Let us know what happens.
Good luck
Perfect thank you for the clarification.
One last question?
I messed up, I factory reset ftv 2 box using my tvs remote and now cannot set it up because my ftv remote is broken/or this particular ftv2 box doesn't pair with Amazon remotes.
Is it possible to somehow setup fire tv (from setup screen after factory reset) without a fire tv remote?
dovedescent7 said:
Perfect thank you for the clarification.
One last question?
I messed up, I factory reset ftv 2 box using my tvs remote and now cannot set it up because my ftv remote is broken/or this particular ftv2 box doesn't pair with Amazon remotes.
Is it possible to somehow setup fire tv (from setup screen after factory reset) without a fire tv remote?
Click to expand...
Click to collapse
Ok, I see. You could try it this way:
-remove the batteries, then press 30 seconds the home button.
-Put new fresh batterys back in.
-Try to pair the remote again, but keep pressing the home button for at least 30 seconds.Do that again and again...
Could be that it takes some time (and attempts), until the remote connects.
If it won't work and you don't know someone with a remote near to you, take a look for a guide with a usb keyboard or so at www.aftvnews.com or xda forums search.
Sus_i said:
Ok, I see. You could try it this way:
-remove the batteries, then press 30 seconds the home button.
-Put new fresh batterys back in.
-Try to pair the remote again, but keep pressing the home button for at least 30 seconds.Do that again and again...
Could be that it takes some time (and attempts), until the remote connects.
If it won't work and you don't know someone with a remote near to you, take a look for a guide with a usb keyboard or so at www.aftvnews.com or xda forums search.
Click to expand...
Click to collapse
THANKS!
NOW I NEED URGENT HELP
Rooted ftv 2 with short method now stuck at twrp.
Can i simply now install prerooted rom from within TWRP via rom on SD card?
edit
so I rooted aftv 2 box with shorting method then got into twrp. Then flashed prerooted fire tv image but when I rebooted it gets stuck on amazon fire tv splash screen and won't move.
I tried clearing cache 1x in TWRP afterwards, then reboot but still hangs at Amazon boot.
What am I missing?
dovedescent7 said:
edit
so I rooted aftv 2 box with shorting method then got into twrp. Then flashed prerooted fire tv image but when I rebooted it gets stuck on amazon fire tv splash screen and won't move.
I tried clearing cache 1x in TWRP afterwards, then reboot but still hangs at Amazon boot.
What am I missing?
Click to expand...
Click to collapse
Have you flashed this way, first the 5.2.6.7_v2 and then a later 5.2.7.x one? It's mentioned in the prerooted thread.
Wipe cache and dalvik before you reboot.
If it won't boot, you probably need to wipe data and internalsd too. Best is to use the 'format' data tab in TWRPs wipe section.
After that, the box should boot, but you need to log on at the setup, pair the remote and so on...
dovedescent7 said:
I dont understand. Are you saying method WILL WORK for 5.2.6.0 or WILL NOT WORK for 5.2.6.0?
I am very familiar with Ubuntu Linux and adb..
Click to expand...
Click to collapse
I just did this on a used device I purchased that came with 5.2.6.7 and it worked perfectly. Follow the instructions and you'll have no issues and none of that jumper stuff.