Related
Prior to 6.2.1 I had my Kindle Fire rooted with super one click. It seems like the Kindle Fire utility is the method of choice today. I would like to know if there is anything special I need to do to remove superoneclick and/or drivers before installing KFU. I'm trying to be a bit cautious here since the frequency of bricking seems to have gone up.
I was lucky that the 6.2.1 upgrade did not mess up my android market or google install – I had already upgraded to the latest version prior to the install. I would like to regain root, but I'm willing to go slow since my KF is currently rock solid and I don't really have any pressing need.
Thanks
Bruce
I didnt have any issues switching from one-click to KFU. it ran fine with the drivers i installed to use one-click. I did have one issue after installing the 6.2.1 udate and FFFm I had to reinstall the KF drivers after I updated (my windows box no longer recognized it and it got stuck in the wrong boot mode which was easy to fix from command line once it was recognized again).
Kekule
As far as I know SuperOneClick never installed anything on your Fire. It sounds like you are using a stock un-rooted 6.2.1 so you'd just proceed as any normal 6.2.1 user would. I, myself, rooted back in 6.2 with SuperOneClick and have been ever since because I installed TWRP and used the pre-rooted 6.2.1 image. I'm kind of curious if there's anything I need to know as well, though. I'd rather err on the side of caution as well.
Buffet_of_Lies said:
As far as I know SuperOneClick never installed anything on your Fire.
Click to expand...
Click to collapse
nothing more that SU, but you do have to get ADB running which requires having the android SDK usb driver to connect to the fire instead of whatever gets installed by default.
Great.. just thought I would check before I just plowed ahead as if it was a brand new 6.2.1 KF. I'm not sure when I'll get to it, but it's nice to know that I don't need to do anything unusual. I may just wait a bit to give KFU some time to mature.
btrvalik said:
I may just wait a bit to give KFU some time to mature.
Click to expand...
Click to collapse
I don't think KFU is going to change much now. Its been at 0.9.1 for some time how. I see the links to the original article are backup so the links should be good too.
Kekule said:
I didnt have any issues switching from one-click to KFU. it ran fine with the drivers i installed to use one-click.
Click to expand...
Click to collapse
Same here.
I am beyond frustrated... just as title says... I consider myself to be smart with computers but this damn computer will not recognize this tablet... could it have to do w/ the rom i have installed? I have downloaded the drivers from acer directly 3 times and uninstalled/installed SEVERAL times... rebooted the cpu several times...
seems as if no matter what i do i cant get it to be seen by the computer... any ideas?
Powell730 said:
I am beyond frustrated... just as title says... I consider myself to be smart with computers but this damn computer will not recognize this tablet... could it have to do w/ the rom i have installed? I have downloaded the drivers from acer directly 3 times and uninstalled/installed SEVERAL times... rebooted the cpu several times...
seems as if no matter what i do i cant get it to be seen by the computer... any ideas?
Click to expand...
Click to collapse
Not an issue with the rom. Shouldn't be anyhow. I might suspect the following;
1. Your USB cable?
2. When you installed drivers, "right" mouse click and select "run as administrator".
3. If your Acer drivers still won't install, Through Device Manager Install them manually. Don't let it search the PC.
4. If that doesn't work, get the Google USB Drivers from here;
http://developer.android.com/sdk/win-usb.html
Extract to your PC. Again, install manually from Device manager (if you get a compatibility warning, ignore it)
thank you for the response.. i got so frustrated that i just installed the stock un rooted full package from the dev section of 3.1.. then updated to 3.2 and 3.2.1 and then for some reason my tablet wouldnt update after that... just kept telling me my system was up to date.. BS!!! i just downloaded the update from the same thread and decrypted and then manually installed... still confused as to why my tablet was telling me i was up to take when i was only on 3.2.1... anyway.. ill look into rooting stock ics tomorrow.. thanks again... oh and btw my computer recognized the tablet after i was no longer rooted and running stock.
Powell730 said:
thank you for the response.. i got so frustrated that i just installed the stock un rooted full package from the dev section of 3.1.. then updated to 3.2 and 3.2.1 and then for some reason my tablet wouldnt update after that... just kept telling me my system was up to date.. BS!!! i just downloaded the update from the same thread and decrypted and then manually installed... still confused as to why my tablet was telling me i was up to take when i was only on 3.2.1... anyway.. ill look into rooting stock ics tomorrow.. thanks again... oh and btw my computer recognized the tablet after i was no longer rooted and running stock.
Click to expand...
Click to collapse
Stranger things have happened. Believe me Technically, a rom "can" be guilty of USB issues, but the ICS releases out right now don't have these issues. Usually you find these on initial Beta releases.
You have to be a little careful when going back to stock. Acer put a stop to the ICS updates for awhile after they found the update process was bricking tablets. And, not all regions got updates before they stopped the program after a couple of days.
I would guess it tells you you;re up to date, as there is no ICS for it yet till they resume the program. Just a guess.
As far as I know, for the 500, they were supposed to resume ICS updates on the 27th May. Last I heard anyhow.
That's because it's Windows 7, lol.
MikeyCriggz said:
That's because it's Windows 7, lol.
Click to expand...
Click to collapse
And????
Actually, I have less issues on windows7. Yeah, you sometimes have to use "run as administrator". So I am not sure what your point is. Technically.
@MD i didnt know they stopped the release ? Win 7 doesnt cause these issues , sorry , for those of you wanting to do more with your android stick with Win 7 , its alot easier than running it through Linux! I use both!
I finally did it. Didn't have to unlock, rollback the firmware, ADB, or anything too drastic. So happy.
I used this method here.
http://forum.xda-developers.com/showthread.php?t=1706588
*My biggest hurdle was getting the drivers installed before using that method. Then I figured out if you use the Asus Pad PC Suite it installs the drivers. Can download it here if you're as incompetent as me (Under Utilities). Exit out Asus Sync in your system tray before attempting the method above. And I'm probably not the guy to ask for any help if you got problems or questions.
http://usa.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
I installed OTA RootKeeper afterwards.
Thanks XDA. Thanks sparkym3.
I think you should give yourself more credit.
GJ
thanks man!
-Bang
supersoulfly said:
*My biggest hurdle was getting the drivers installed before using that method. Then I figured out if you use the Asus Pad PC Suite it installs the drivers.
Click to expand...
Click to collapse
This works indeed, but you must stop ASUS sync if it's running. If you don't, the version of ADB packaged with ASUS Sync is different from the one in the zip file and you'll get a whole lot of lines with "adb server is out of date, daemon started successfully" which mess with the script.
Once I stopped the Sync thing from systray and verified in task manager, the script ran like a charm.
So, another TF300 with .29 WW rooted, thanks to the people involved in making this possible
all this confused me way too much but luckily for me i had help (well i say help he did it all via teamviewer lol) from thing o doom he is a star
I used this method too on my 29.WW,thx guys
just confirming, even thought the method is in the transformer prime section, it works for the TF300T?
Thank you
jakelikescake123 said:
just confirming, even thought the method is in the transformer prime section, it works for the TF300T?
Thank you
Click to expand...
Click to collapse
Ummmm.....I think I confirmed it, in the first post.
supersoulfly said:
Ummmm.....I think I confirmed it, in the first post.
Click to expand...
Click to collapse
im the idiot
thanks
No problems getting the drivers install but rooting fails because it appears that adb cannot see the device.
lightiv said:
No problems getting the drivers install but rooting fails because it appears that adb cannot see the device.
Click to expand...
Click to collapse
May not be the issue, but it's happened to me several times rooting & ROMing phones - plug the cable into a rear USB port that's on the motherboard. The USB ports on the front of the case don't always work for some reason. The front of my case has 6 ports and I can only get reliable phone connections on 2 of them. Down right squirrely!
ID10T Error on My Part
Turn out to be an ID10T error on my part. I had DroidExplorer running from when I rooted my cellphone. I finally ran across a post that made reference to it and killed the process. It took all of 30 seconds to root once I killed the process.
So, my neighbor bought an Acer A500 a few months back. He ended up not liking it so I bought it off of him. My tablet and I got really close and I fell in love. I started neglecting my girlfriend and all that. We had a beautiful relationship; my tablet and me. But, a couple days ago I was playing N.O.V.A 3 and it froze. I thought nothing of it and just powered it down. To my dismay, it froze at the Acer screen. I restarted it again and got the same thing. My life was over. My heart felt like it was ripped from my chest... I shed a manly tear.
I've tried vol- and power, vol+ and power, the reset button, D/Ling several different update.zip files and copying them to my SD. I've spent the last couple days reading and trying everything. All I get is the Droid guy with the blue thing swirling in his chest and then him laying on the ground with a red triangle and an exclamation point.
I'm told it's most likely not a hardware issue as things things are almost bullet-proof. But, I am pretty good at breaking things
Am I screwed or does someone have a miracle they can share. My gaming life depends on it.
-Dennis.
DennisPimps said:
So, my neighbor bought an Acer A500 a few months back. He ended up not liking it so I bought it off of him. My tablet and I got really close and I fell in love. I started neglecting my girlfriend and all that. We had a beautiful relationship; my tablet and me. But, a couple days ago I was playing N.O.V.A 3 and it froze. I thought nothing of it and just powered it down. To my dismay, it froze at the Acer screen. I restarted it again and got the same thing. My life was over. My heart felt like it was ripped from my chest... I shed a manly tear.
I've tried vol- and power, vol+ and power, the reset button, D/Ling several different update.zip files and copying them to my SD. I've spent the last couple days reading and trying everything. All I get is the Droid guy with the blue thing swirling in his chest and then him laying on the ground with a red triangle and an exclamation point.
I'm told it's most likely not a hardware issue as things things are almost bullet-proof. But, I am pretty good at breaking things
Am I screwed or does someone have a miracle they can share. My gaming life depends on it.
-Dennis.
Click to expand...
Click to collapse
Do you know what you were running on this thing? Was it stock Honeycomb, scock ICS, or was it running a custom ROM? (If so which one?)
Was it ever hooked up to your PC? (This would help with retrieving CPUID, if it was.) Do you know your CPUID? (Or SBK?)
You should at the least know the answers to these questions before you attempt any type of repair, as it is almost certainly salvageable, but you will almost certainly need your CPUID.
Danny2 said:
Do you know what you were running on this thing? Was it stock Honeycomb, scock ICS, or was it running a custom ROM? (If so which one?)
Was it ever hooked up to your PC? (This would help with retrieving CPUID, if it was.) Do you know your CPUID? (Or SBK?)
You should at the least know the answers to these questions before you attempt any type of repair, as it is almost certainly salvageable, but you will almost certainly need your CPUID.
Click to expand...
Click to collapse
I was running 4.0.1 ICS. I do have my cpuid and SBK. I tried flashing a new rom using blackthund3rs flash tool but it got to about 25% and stopped. I keep losing sync with my PCs, though.
DennisPimps said:
I was running 4.0.1 ICS. I do have my cpuid and SBK. I tried flashing a new rom using blackthund3rs flash tool but it got to about 25% and stopped. I keep losing sync with my PCs, though.
Click to expand...
Click to collapse
So, do you want to go back to stock, or to a custom ROM? If you wanna go stock, the easiest way would be load a 3.01 EUU, & upgrade on the play market to 4.03. That will prove it isn't a hardware issue. Alternatively, you could root, load a recovery, a bootloader, & flash a new ROM.
Danny2 said:
So, do you want to go back to stock, or to a custom ROM? If you wanna go stock, the easiest way would be load a 3.01 EUU, & upgrade on the play market to 4.03. That will prove it isn't a hardware issue. Alternatively, you could root, load a recovery, a bootloader, & flash a new ROM.
Click to expand...
Click to collapse
To be honest, I really don't care as long as I can getting it working again. But I would rather root it.
I think I can get it to work but neither one of my computers will recognize it. It shows up in APX and says something about recovery driver mode when I plug it into the laptop with Vista automatically downloads a driver and installs it again. I've tried turning off automatic driver install but that doesn't work for some reason. The one with XP Pro just shows up APX device but the APX Flash Tool by blackthund3r says it can't find it. I've downloaded the Acer Iconia 500 drivers and installed them but that doesn't work either. I'm at a loss.
Any tips would be great. I think I have a better chance using my laptop with XP, though. I also need to let you know that I truly do appreciate you trying to help. If you're ever in Columbus Ohio, let me know and I'll buy you a beer. lol
DennisPimps said:
To be honest, I really don't care as long as I can getting it working again. But I would rather root it.
I think I can get it to work but neither one of my computers will recognize it. It shows up in APX and says something about recovery driver mode when I plug it into the laptop with Vista automatically downloads a driver and installs it again. I've tried turning off automatic driver install but that doesn't work for some reason. The one with XP Pro just shows up APX device but the APX Flash Tool by blackthund3r says it can't find it. I've downloaded the Acer Iconia 500 drivers and installed them but that doesn't work either. I'm at a loss.
Any tips would be great. I think I have a better chance using my laptop with XP, though. I also need to let you know that I truly do appreciate you trying to help. If you're ever in Columbus Ohio, let me know and I'll buy you a beer. lol
Click to expand...
Click to collapse
Sorry,I thought I responded to this yesterday, but just now noticed I didn't.
Fire it up in APX mode, and install the 3.01 EUU from the development section, (Stock ROM listing) then simply follow the upgrade path to 4.03, then root. If you drivers are installed correctly, everything will work fine, if not, nothing will happen. If it does start to load the stock ROM, then fails with a write error after it attempts to write the bootsector, you may need to run Badsector, or babsector, depending where you look. Search the recent posts on this, you will find lots of stuff.
Danny2 said:
Sorry,I thought I responded to this yesterday, but just now noticed I didn't.
Fire it up in APX mode, and install the 3.01 EUU from the development section, (Stock ROM listing) then simply follow the upgrade path to 4.03, then root. If you drivers are installed correctly, everything will work fine, if not, nothing will happen. If it does start to load the stock ROM, then fails with a write error after it attempts to write the bootsector, you may need to run Badsector, or babsector, depending where you look. Search the recent posts on this, you will find lots of stuff.
Click to expand...
Click to collapse
How would I go about installing the EUU? I have nvflash and blackthund3r's flashing tools. But I can't seem to get my PC and tablet to connect. When I plug it into my PC without being in APX mode, it just says MTP Device. When I plug it in while in APX mode it does say something about Picasso Recovery Driver.
If you could explain things to me like I'm aN idiot, I'd really appreciate it.
Thanks,
Dennis
DennisPimps said:
How would I go about installing the EUU? I have nvflash and blackthund3r's flashing tools. But I can't seem to get my PC and tablet to connect. When I plug it into my PC without being in APX mode, it just says MTP Device. When I plug it in while in APX mode it does say something about Picasso Recovery Driver.
If you could explain things to me like I'm aN idiot, I'd really appreciate it.
Thanks,
Dennis
Click to expand...
Click to collapse
Sorry for late response, I watched for reply from yourself, but you didn't answer for 10 days, I lost track. Still need help?
Danny2 said:
Sorry for late response, I watched for reply from yourself, but you didn't answer for 10 days, I lost track. Still need help?
Click to expand...
Click to collapse
Yea, it's still bricked. I did finally get the flash tool to recognize it but it kept hanging up. I also tried Timmy Dean's EUU tool and that hangs up too. I did a little more research and found that I may have a faulty emmc. I ran babsector and got 'fatal error code 9 cannot format partition BCT.' I found a thread here that discusses how to write around the bad sectors using Linux. I'm going to give that a go... I've always wanted to learn Linux. Hey, I can't screw it up anymore than it already is, right? Again, thanks for your time and effort in trying to help.
Cheers,
Dennis
Hey, before you try that, try different USB cables and ports (if u haven't already)
I had a similar problem with my phone not maintaining stable USB link to PC... after 4 days I tried a diff USB cable and boom, snap, working.
Just a thought.....
Sent from my A500 using xda app-developers app
ericpeacock79 said:
Hey, before you try that, try different USB cables and ports (if u haven't already)
I had a similar problem with my phone not maintaining stable USB link to PC... after 4 days I tried a diff USB cable and boom, snap, working.
Just a thought.....
Sent from my A500 using xda app-developers app
Click to expand...
Click to collapse
I'll give that a go, m8.
Thanks!
-Dennis
DennisPimps said:
I'll give that a go, m8.
Thanks!
-Dennis
Click to expand...
Click to collapse
Just wondering if you ever figured out the errors you were getting during flashing? Currently having the same issues when using babsector.
First off. I'm pretty much a layman at this. Anyone that can solve my issues, I'll gladly pay via PayPal or whatever...
Two months ago, I bought a used LG G2 . It was rooted and running Lollipop.
Sadly, I was a PokemonGo junkie, so when the M'F'ng Niantic a**holes put a block on rooted phones, I attempted the Magisk workaround and ended up bricking my device.
Fortunately I found a solution via You Tube and was able to restore to the factory KitKat / AT&T.
THE CURRENT problem is that yesterday I re-rooted the device, installed TWRP, but did something wrong to where it will not fully reboot and I'm stuck in TWRP. I've watched and read about 20 "fix it" instructionals, which rely on using a PC. I'm using a laptop running XP and every time I have downloaded, installed, and tried to update the damn LG USB driver, it won't f*ing update. I'm going mad and ready to jump off a bridge.
Supposedly, this is the place to go. for answers, so ...CAN ANYONE HELP?!! Again, I'm a layman. I need VERY simple, step by step solutions, that account for ANYTHING that might go wrong, since so far, it always does.
Thank you, if you read this.
Ok Can you access to twrp ?
(Sorry for my english i'm french)
If you are in the TWRP, just download some other kk rom, transfer it to your phone and install, one question, what TWRP is it ? 2.8.7.0. ?
Kornelije23 said:
If you are in the TWRP, just download some other kk rom, transfer it to your phone and install, one question, what TWRP is it ? 2.8.7.0. ?
Click to expand...
Click to collapse
Agreed. Also, if there's no communication between PC and device, you may need an OTG to flash from.
Sent from my Nexus 6 using XDA-Developers mobile app
R2MIR2MI said:
Ok Can you access to twrp ?
(Sorry for my english i'm french)
Click to expand...
Click to collapse
Thanks for the reply. Yes, I can access TWRP. I just don't know what to do with it.
Dork6243 said:
Agreed. Also, if there's no communication between PC and device, you may need an OTG to flash from.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
It's TWRP 2.7.0. I kind of know in theory what needs to be done, but I don't know how to do it. I thought I backed everything up using Titanium and TWRP, but maybe the KK ROM is gone? I dunno... I was actually hoping to install Lollipop
What model do you have?
If it is d802, then there is an easy-to-flash rom here: http://forum.xda-developers.com/lg-g2/development-d802/rom-pure-stock-lg-google-apps-t3477635/page1
To transfer it to the phone, you can use OTG as Dork said: put the rom on a usb-stick and connect it to the phone with an OTG cable. Most versions of twrp support OTG.
Another way is to get linux for your PC. You're really better off with linux than XP, but you can also just boot with a live-cd. In linux, USB generally just works, though sometimes you have to be root because ordinary users may not have permission.
Thanks for the replies, but being very new at all this, I don't know how to do any of the things suggested. I ended up finding a you tube video which walked me through downloading lg flash tool and some .dll file, and on my work computer with windows 7, I was able to install the usb drivers & change the port number which allowed LG flash to work. The crappy XP didn't have that option on the device manager menu and wouldn't install the drivers.
Anyway, I got it restored to ATT stock KitKat. I wanted Lollipop and Magisk, so I tried installing TWRP with AutoRec, then got stuck in TWRP and bricked again. So I did the whole lg flash to KitKat process again. Now Im sick of messing with it and bricking my phone. I cant find any super simple step by step tutorial that makes sense to a layman like me, or that doesn't leave out steps, or provide expired links, or account for anything that could go wrong. I had hoped this was the place to come, but no luck so far. I know its time consuming for someone to make up a truly easy to follow guide for an older device, using layman terms that my grandma could follow, and I work 2 jobs and dont have hours to try to thoroughly learn OS programming, so I guess Ill just leave well enough alone and live with KitKat and without the ability to mask my root.
davizzyus said:
Thanks for the replies, but being very new at all this, I don't know how to do any of the things suggested.
Click to expand...
Click to collapse
Do what everybody here has done: read. And when you say "I can access TWRP. I just don't know what to do with it." you havn't even read the basics.
Just read the provided solutions properly. The Knowledge will grow. Here's a list of methods:
http://forum.xda-developers.com/showpost.php?p=63327417&postcount=4
Jan Philipp said:
Do what everybody here has done: read. And when you say "I can access TWRP. I just don't know what to do with it." you havn't even read the basics.
Just read the provided solutions properly. The Knowledge will grow. Here's a list of methods:
http://forum.xda-developers.com/showpost.php?p=63327417&postcount=4
Click to expand...
Click to collapse
I have tried reading a lot of different threads. As I said before, I don't understand the "tech talk" for lack of a better word. When I'm reading "bootload" this, and " sideboot" that, and kernels, and loki, and CM, and mods, and .kdz and ATD,....I don't know what all that means, & there's no OS dictionary to translate. I can't seem to find any threads that explain it for newcomers trying to learn.
Im an accountant. I can prepare corporate tax returns with my eyes closed, but cell phone programming is Greek to me.