I know im rehashing allot of stuff already said and I apologize for that. But dev information can be overwhelming when you come late to the game like im doing now, just trying to sort this out in my head before my Fire arrives tomorrow. Not new to android, rooted and romed plenty of Android phones including a G2 so I know my way around the basics like adb and the like. I've just never seen so much talk about bricking as im seeing around these fire forums.
From everything im reading it seems pretty straight forward, you use KFU to root (should you perm root or temp at this point or does it matter?), flash FFF, then flash TWRP, and then just flash whatever rom you want, right? Is there something im missing, do kindles just randomly brick while doing this or do you have to do something wrong? Also, it sounds like the way FFF works as long as you have that flashed and you don't dink around with bootloader it should be impossible to brick no? And assuming this is true why doesn't everyone just flash FFF and be done with it, are there any drawbacks to running it?
Guess im just trying to figure out if these things are brick machines or are there just allot of new android folks around this device that aren't following the steps properly? I suppose I better make a factory cable just in case lol
Thanks for reading, any help you can give a Fire newb would be appreciated!
FinalJenemba said:
I know im rehashing allot of stuff already said and I apologize for that. But dev information can be overwhelming when you come late to the game like im doing now, just trying to sort this out in my head before my Fire arrives tomorrow. Not new to android, rooted and romed plenty of Android phones including a G2 so I know my way around the basics like adb and the like. I've just never seen so much talk about bricking as im seeing around these fire forums.
From everything im reading it seems pretty straight forward, you use KFU to root (should you perm root or temp at this point or does it matter?), flash FFF, then flash TWRP, and then just flash whatever rom you want, right? Is there something im missing, do kindles just randomly brick while doing this or do you have to do something wrong? Also, it sounds like the way FFF works as long as you have that flashed and you don't dink around with bootloader it should be impossible to brick no? And assuming this is true why doesn't everyone just flash FFF and be done with it, are there any drawbacks to running it?
Guess im just trying to figure out if these things are brick machines or are there just allot of new android folks around this device that aren't following the steps properly? I suppose I better make a factory cable just in case lol
Thanks for reading, any help you can give a Fire newb would be appreciated!
Click to expand...
Click to collapse
No, they are actually pretty difficult to brick. A lot of the "brick" threads here are usually one of two things.
1) Users who can't get their devices to boot normally because they don't know how to change the bootmode.
2) KFU stops mid-way through some process and they are not familiar with the tools to reverse or finish the process.
By the sound of your post, you are ahead of the game and KFU will probably get in the way of where you want to go. You don't even have to root the KF if you are just going to flash a ROM. I suggest you skim this thread...
http://forum.xda-developers.com/showthread.php?t=1552547
Post #2 will get your drivers installed and the bottom of post #3 has step-by-step directions on how to get your device ready to flash a ROM. I think that's all you're going to need.
EDIT: I forgot to answer your FFF question. Yes, if you have an intact FFF bootloader, you should always have a solid base from which to rebuild your system. You could basically wipe everything else out... as long as you have FFF, you can recover without having to do anything drastic. The only drawback I can think of is that it takes a little while longer to boot because it pauses for about 4 seconds while it temporarily gives you access to fastboot mode. IMHO, this is actually a huge plus because it means you can always get access to fastboot mode without a factory cable, so it's definitely worth the tradeoff.
Like said already, they aren't easy to brick.
What is a pain in the ass is getting the computer to recognize it correctly sometimes.
Sent from my Amazon Kindle Fire using Tapatalk 2
No, they are not very easy to brick. Most of the "bricks" are not permanent and quite easy to fix if you have some ideas of what is wrong and the methods of fixing it.
To actually brick it permanently so that there is no way to fix it without proper hardware tools is very hard and I believe that is very uncommon if you follow instructions and do everything with care.
Here's my very own anecdote of a false-brick panick:
It was my first day with a shining brand new kindle. I read on xda that KFU was the easiest way to get into the world of custom roms. So I downloaded it, followed the steps exactly and ended up with a kindle which won't boot. I was lost. I didn't know what went wrong, as is usually the case with such scenarios.
After a few hours of head-screatching and crash-coursing through these threads, I finally figured out the problem. KFU attempted to flash TWRP which was not properly downloaded. I think my internet connection must have dopped. But KFU thought the download was done and proceeded to flash anyway and long story short, I lost a precious few hours of my life but did gain heaps of experience in the process.
Lucky for me, FFF had been flashed earlier and I was able to recover my lovely kindle.
Moral: xda rocks! (may not be obvious from the story, but it's true)
Sent from my Amazon Kindle Fire using XDA
I've managed to permanently brick my device once but that was out of sheer stupidity and messing with partitions I didn't have any business messing with.
I'm not sure if it's failure to pay attention or some people don't want to take the time to learn what they are doing before doing it, but it simply amazes me how many people can't grasp the basics of how the Kindle Fire/Android works, even with one of the most comprehensive and easy to understand beginners guide I've seen.
As long as you understand that when adb/fastboot doesn't connect it's a driver issue, and you have a good understanding of the different bootmodes, with a little research you can fix 99.99999999% of the problems you'll encounter on the Kindle Fire.
Most of the problems you'll see are from Windows users (imagine that) because of Windows' lack of a good system for dealing with device drivers. And most of the rest are from just plain ignorance, refusal to learn, and trying to take the easy way out.
If you have problem, chances are 250 other people have had the same problem and a simple search will usually get you the answer you need. And while XDA's search function has a lot to be desired, Google's search function works quite well and should definitely be put to use. You'll be amazed by what you'll find just by putting "site:forum.xda-developers.com kindle fire" in front of your search criteria.
Thanks guys, you pretty much confirmed what I was thinking.
And thanks kinfauns, I did read your guide but totally missed post 3, that's pretty much all the info I need. I would much rather use ADB when the steps are that easy. I remember when the devs first got s-off on the G2 and the ADB/Terminal emulator steps and this looks allot more straightforward lol.
Just wanted to update to say that I got my Fire and got it rom'd. Nothing to it, kinfauns guide made it incredibly easy. If you can read you can root a Fire
Thanks again kinfauns!
FinalJenemba said:
If you can read you can root a Fire
Click to expand...
Click to collapse
Such a simple concept, yet it alludes so many.
ha
Not gonna lie, it is kinda funny to watch so many people freak out...but I guess I was there once too.
ive rooted 5 kindles now.
3 of my own, as i had to return 2 because of a ghosting issues apparently from a bad batch that got out. Note to self (and by proxy, others), buy your kindle from Amazon instead of a 3rd party store. At least Amazon has great customer server.
was very easy, never had a single issue. Even returning them back to stock.
Related
Hi guys,
Im new to the Android scene, and thats because of the N1 got my nexus on order and should arrive shorty in the following week. Been reading the threads here over the last week or so, but alot of things aren't quite clear to me. Especially because im a Android noobie (previous WinMo )
Anyways reading about the Unlocking bootloader and Rooting the device seems pretty straight forward. I understand the consequences of each part and thus appears to be pretty easily done.
The things that i am unclear about are the addon packs and the things it comes bundled with?
- What are the current benefits from flashing these "addon" packs?
- They aren't ROM's just kind of expansion packs right? so no lost data after?
- Wtf is adb? lol i keep seeing it but no idea what it is, thus confusing for noobies like me.
- In cyanogens thread here it says backup using Nandroid, and when i find Nandroid in google i get this. But it says for G1? will it still work fine?
Thankyou for any answers as I believe you will help me to NOT mess up my new phone. I'm sure alot of other people would be thankful for your answers.
Thankyou again!
Hello,
First off welcome to Android, second, get the fire suit on for the "wrong forum" flames.
What are the current benefits from flashing these "addon" packs?
Not a *ton* but there is Tether and other goodies that you can start using.
- They aren't ROM's just kind of expansion packs right? so no lost data after?
Yes to 1st, and there will be lost data when you unlock the bootloader.. if you unocked the bootloader, and then used the phone for a week or so, THEN flashed this addon pack, then no data loss.- Wtf is adb? lol i keep seeing it but no idea what it is, thus confusing for noobies like me.
Android Debug Bridge... its used for debugging. lol....- In cyanogens thread here it says backup using Nandroid, and when i find Nandroid in google i get this. But it says for G1? will it still work fine?
No, the Nandroid backup will be an option AFTER you unlock the BL and install Amon_RA's Recovery image..
Good luck man!!
thanks for the reply.
I'm trying to gather as much as i can before i get the phone in my hands. Maybe because i want to start right away when i get hold of the phone lol You have enlightened me on many points.
I was just wondering also,
I've read about apps such as Nexus Torch and SetCPU which require rooting. Are these apps aquired simply after I unlock + root from the market place? because i read about reinstall su and similar.
Sorry for the noobiness, as i've mentioned im a android beginner and not too familiar with the terms used.
I just want to install some cool apps and convert those iphone users......(my gf )
No they're not required. Rooting is really only for the hardcore phone nerd (which is probably why you're on this site!) I personally am holding off on rooting my N1 until it's fully understood on if it can be re-locked etc. If this is your first Android phone I would recommend doing some reading around on the G1 forum and understand the full capabilities of rooting your device and some neat apps.
**edit
mis-read what you said. Those apps can be obtained from the "Makin Bacon" add on somewhere on this forum. Cyanogen posted it up.
SystmDcln said:
No they're not required. Rooting is really only for the hardcore phone nerd (which is probably why you're on this site!) I personally am holding off on rooting my N1 until it's fully understood on if it can be re-locked etc. If this is your first Android phone I would recommend doing some reading around on the G1 forum and understand the full capabilities of rooting your device and some neat apps.
**edit
mis-read what you said. Those apps can be obtained from the "Makin Bacon" add on somewhere on this forum. Cyanogen posted it up.
Click to expand...
Click to collapse
I'm doing the same thing as this guy. I'm super hardcore about customization so I have no doubt that I'll root my phone eventually but not quite yet. Things are still a bit too new and right now there really aren't that many reasons to root (outside of tethering support IMO). If you can live without tethering for a month, then you should wait to root.
welcome
addon packs do a few things to your phone. the biggest things, i think, are the busybox and the dropbear installations, and the tethering apps. some modders also like to "optimize" android too. whether or not it actually works, i can't personally tell, but i take their word for it.
busybox will allow you to run some common linux commands on your android (with a terminal app i guess...) http://en.wikipedia.org/wiki/BusyBox
dropbear is an ssh server so that you can access the command line (and push files to your android) from your computer
tethering means share your cell connection with a computer to give your computer internet. i've used it in many airports, and it's sweet.
like the other dude said, the initial root will require a data wipe, but not the addons. i'm not sure if it's true for EVERY rom (i think it is) but when you first install a whole rom a wipe is required, but when upgrading to a newer version of the same rom no wipe is required. if you like to keep your sms and mms's then it's good to have some of these linux tools so you can move and replace the sms and mms databases manually.
adb is android debugging bridge. it's a part of the android sdk (software development kit) that google gives out for free and is meant to develop apps. with it you can plug your phone into your comp via USB and run all sorts of commands on it from your computer. droidexplorer is basically a GUI for the adb commands, so with ADB you can do all that droidexplorer can do. http://de.codeplex.com/
nandroid is kind of like "system restore" for android. you need to root the phone, then flash Amon_RA's recovery thingy (in one of the threads). once you're in recovery, you can create a nandroid backup (kind of like an image of your current android phone) that you can restore later. then restoring it is as simple as going back into recovery and clicking "restore".
m00moo said:
Hi guys,
Im new to the Android scene, and thats because of the N1 got my nexus on order and should arrive shorty in the following week. Been reading the threads here over the last week or so, but alot of things aren't quite clear to me. Especially because im a Android noobie (previous WinMo )
Anyways reading about the Unlocking bootloader and Rooting the device seems pretty straight forward. I understand the consequences of each part and thus appears to be pretty easily done.
The things that i am unclear about are the addon packs and the things it comes bundled with?
- What are the current benefits from flashing these "addon" packs?
- They aren't ROM's just kind of expansion packs right? so no lost data after?
- Wtf is adb? lol i keep seeing it but no idea what it is, thus confusing for noobies like me.
- In cyanogens thread here it says backup using Nandroid, and when i find Nandroid in google i get this. But it says for G1? will it still work fine?
Thankyou for any answers as I believe you will help me to NOT mess up my new phone. I'm sure alot of other people would be thankful for your answers.
Thankyou again!
Click to expand...
Click to collapse
wow thanks vmuch for the kind replies!
i feel like i understand the previous things i've read around in the forum alot more now!
So the question to root or not root, rooting the device would prob be the option for me as:
1) dont really want to do a wipe after a week or two
2) want cool apps such as SetCUP/Nexus Torch
One thing im wondering is whats this about paid apps and rooted devices in the market? After rooting some people cannot see paid apps or something?
Once again thankyou for the kind kind replies and i hope some other noobies like me are learning
If I buy an app (I'm thinking of the Exchange Calendar sync app) and then end up rooting and installing another ROM (say the EU ROM if it has multitouch) will I be able to get my purchased apps working again - or do you have to rebuy them?
If you buy an app it'll always show as purchased on the marketplace so you can redownload it - all the ones I bought on my G1 were still available when I setup the N1 for example.
m00moo said:
wow thanks vmuch for the kind replies!
i feel like i understand the previous things i've read around in the forum alot more now!
So the question to root or not root, rooting the device would prob be the option for me as:
1) dont really want to do a wipe after a week or two
2) want cool apps such as SetCUP/Nexus Torch
One thing im wondering is whats this about paid apps and rooted devices in the market? After rooting some people cannot see paid apps or something?
Once again thankyou for the kind kind replies and i hope some other noobies like me are learning
Click to expand...
Click to collapse
Wait to root. Right now it's still too unknown on the "ins and outs" of this phone. When I first started rooting on my G1 and MyTouch I wiped a lot while learning things about it. Research while you wait. An OTA is supposed to come out to fix some bugs, and nobody has released any ROMs anyways. And on paid apps, Google Checkout keeps a record of what you purchase, no matter how many times you wipe Market will always have them listed in the "Downloads" Tab as "Purchased" to re-download at no charge.
m00moo said:
wow thanks vmuch for the kind replies!
i feel like i understand the previous things i've read around in the forum alot more now!
So the question to root or not root, rooting the device would prob be the option for me as:
1) dont really want to do a wipe after a week or two
2) want cool apps such as SetCUP/Nexus Torch
One thing im wondering is whats this about paid apps and rooted devices in the market? After rooting some people cannot see paid apps or something?
Once again thankyou for the kind kind replies and i hope some other noobies like me are learning
Click to expand...
Click to collapse
that happened to me. i think it has to do with the fact that i rooted and turned on my phone before i even put my simcard in. i opened the market and couldn't see "top paid apps" (though i could still search for apps and paid ones would show up). after i turned it off, then put my sim card in and turned it back on, no dice, still no top paid apps.
i reflashed nexusone-superboot-1.1.img with my sim card in this time (can't remember if i wiped. i think it required a wipe) and i turned it on with my sim and voila. paid apps. so it's definitely fixable if you run into that problem.
thanks again for the replies
Im pretty up for rooting upon recieving my handset which should be by wednesday the latest (no engraving), as i ordered on friday 8th. But being the first time im quite scared to do so lol especially on a brand new phone.
But as SystmDcIn said theres too much we don't know as of yet and slowly things are becoming more and more developed as we speak.
The main issue for me is using the phone 2 weeks in and then wiping it clean hopefully somebody will make some cool ROMS soon which include the "addons and goodies" so the process is made way more simple.
Thanks again guys! Well appreciated!
I would also agree with waiting to root. I dont see the benefits of SetCPU for the N1, cuz its already at 1ghz, if it was underclocked i would understand.
Orangeandblue302 said:
I would also agree with waiting to root. I dont see the benefits of SetCPU for the N1, cuz its already at 1ghz, if it was underclocked i would understand.
Click to expand...
Click to collapse
I use SetCPU to underclock the device in sleep mode.
I also underclock when I am not going to be using it for long periods.
Saves battery life.
true true, didnt think of it like that. most people want to overclock, i shouldnt assume. you know what happens when you assume lol.
It is a bit of a travesty to do it to this device. Its like putting a Beetle engine in a Porsche.
I can't always be near a charger, and until I can get a bigger battery that will give me more than seven hours, this is the solution.
this being my first android device i have spent hours on end on theses boards and on wiki's learning as much as i can about the phone and the platform... many of these basic questions that he asked i also had not 24 hours ago haha...
that being said, i think a lot of people are moving over to android so what if a thread got started that would answer basic questions that typically ever new user is going to have? ive yet to find a straight forward answer for half of the crap i have tried to find out and having it all in 1 place would be quite beneficial for people switching over... this could be moderated highly to keep it clean and in order?
a nice, straightforward, helpful community would be a nice touch to overtake some iphone shares
I see that you're from Hong Kong also- has your device shipped yet? I ordered mine on the 8th as well and it still shows not yet shipped. Was just wondering whether that's normal as most people state that the device shipped a day after ordering.
yamanote said:
I see that you're from Hong Kong also- has your device shipped yet? I ordered mine on the 8th as well and it still shows not yet shipped. Was just wondering whether that's normal as most people state that the device shipped a day after ordering.
Click to expand...
Click to collapse
Sorry I am not really from Hong Kong lol I'm in fact from UK and Chinese. My Phone will be arriving early next week so whilst waiting, I am trying to learn as much as possible in case i damage my phone being a noob. lol
I agree with JHaste, i think due to the N1 and the upcoming HTC andoird devices. Alot of people will be moving over to Android in the coming 2-3 months. The questions i asked will be asked over and over and some kind of wiki,faq or android bible will be great. If anybody had the time and knowledge of basic rooting, unlocking and flashing could do such a thing it will be greatly appreciated
m00moo said:
thanks again for the replies
Im pretty up for rooting upon recieving my handset which should be by wednesday the latest (no engraving), as i ordered on friday 8th. But being the first time im quite scared to do so lol especially on a brand new phone.
But as SystmDcIn said theres too much we don't know as of yet and slowly things are becoming more and more developed as we speak.
The main issue for me is using the phone 2 weeks in and then wiping it clean hopefully somebody will make some cool ROMS soon which include the "addons and goodies" so the process is made way more simple.
Thanks again guys! Well appreciated!
Click to expand...
Click to collapse
i think cyanogen's mod includes a backup app (titanium backup or somethin)...you'd be able to save all your data before you wiped it clean (but then you'd need the same backup app to restore it)
this may seem like a silly question, but i have to return my incredible bec they are sending me a replacement, dead pixel, so before i try to root i would like to have it unrooted before i send it back...
so how do you unroot it?
thanx all
At the risk of starting a flamewar (and none of this is directly aimed at the OP):
A lot people need to chill on this. This root method is not ready for prime time yet (that's why they made the disclaimer that it's only really for power users).
As an average user, there is almost nothing gained by having root at this point (other than removing city id and MAYBE gaining tethering). I mean seriously, people who don't even know how to install the android sdk on their computers have no business attempting this.
The main reason most people want root is for custom roms and there aren't any yet.
To answer your question, yes, you can easily undo it with a factory wipe/flash, but again, what's the point in trying it when you have nothing to do with the privileges?
Use one of the RUU post in this forum pre ota or the ota one.
m1k3- said:
To answer your question, yes, you can easily undo it with a factory wipe
Click to expand...
Click to collapse
thank you!
m1k3- said:
To answer your question, yes, you can easily undo it with a factory wipe/flash, but again, what's the point in trying it when you have nothing to do with the privileges?
Click to expand...
Click to collapse
BOOO!
I've been seeing this kind of presumptuous junk pop up again in the Inc thread around the root issue, just like it used to around root season in late '08 for the G1. The one lesson I learned was this:
STOP TELLING PEOPLE THEY'RE NOT SMART/GOOD/CRAFTY ENOUGH TO ROOT!
And if you haven't checked recently, there are a ton of root-only apps on the market. Maybe he just likes #-signs better than $-signs. Whatever his reasons are, just let people be. This forum wouldn't exist if it weren't for natural curiosity.
really though at this point it's kinda based on the SD card you have an timing. to unroot though you just download and run the RUU on the forums here.
rynosaur said:
BOOO!
I've been seeing this kind of presumptuous junk pop up again in the Inc thread around the root issue, just like it used to around root season in late '08 for the G1. The one lesson I learned was this:
STOP TELLING PEOPLE THEY'RE NOT SMART/GOOD/CRAFTY ENOUGH TO ROOT!
And if you haven't checked recently, there are a ton of root-only apps on the market. Maybe he just likes #-signs better than $-signs. Whatever his reasons are, just let people be. This forum wouldn't exist if it weren't for natural curiosity.
Click to expand...
Click to collapse
Dude,
Aside from the fact that they can break stuff (up to and including bricking their phone - yes I realize this process resulting in a brick is unlikely, but it's still possible), there's also another good reason... security. A lot of these people aren't 'linux guys' and don't even really understand what exactly 'root' even means. I bet $20 that if you had everyone in this forum in a room and walked around with a clipboard asking people 'What is UID 0?' maybe 20-30% of people would know the answer. That means that up to 80% of them probably don't quite understand all of the things inside this can of worms they're trying to open.
My comments weren't intended to be presumptuous, or to look down on people, or to thumb my nose at them, etc. I'm only pointing out that for average (or probably even most) users, there aren't really any everyday reasons to go through this.... especially if you don't know what you're doing. All risk, no reward. And that's exactly why the developers of the method are advising these types of users to wait for something that's more suitable for mass consumption.
Ya I love my phone the way it is, all I wanted to do is wifi tether haha. I rooted just fine and im no expert at all. It took about 20 minutes.
Thank you! To the answer on how to quickly unroot. I appreciate it...
drieves1 said:
Use one of the RUU post in this forum pre ota or the ota one.
Click to expand...
Click to collapse
Is there a way to unroot without wiping the phone?
Since when did wiping the phone remove root?
If you RUU the phone to unroot it is wiped and will need to re-do all the settings. I dont want to have to do that.
for us noobs. it is damn near impossible to root this phone. i look all over the internet and i look up every possible related error nobody has an answer to/ adn thats the superoneclick method and it's "memory issue" ...it is impossible all. so we enjoy our slow phones in the meantime because some of us cant downgrade and go back to 1.6 because there is no data coverage. thank you all.
Um..... HUH???? Ilove these posts.
I was the first to root the fender Mytouch. Look around for my guide in the forum if you dont believe me. It took myself and Cursordroid 3 days of Gchat back and forth, files back and forth till we figured out exactly what needed to be done.
In the end, It was a gold card, a rom for a different phone, and ENG bootloader on long enough to flash a recovery... then everything back to stock. Now with all these Universal roots, zroot etc everyone thinks its always supposed to be just that easy.
I nearly broke 2 phones trying to get it rooted int he first place for people... Just because there isnt anything yet, stop your *****ing and have patience.
Better yet... everyone wants it rooted out of the box for eclair/froyo... but then an actual OYA update comes out for the newest version of Froyo.... and nothing but whining.....
ok so ur saying there is no other method?
No he's saying he's aggravated your complaining about SuperOneClick when it used to almost take an act of god to get your phone rooted, which is the other guide in my signature (being the harder way).
and do you know how many pages you have in 3 days as composed to the other thread in months?
Yeah, which just means that the new method isn't as reliable as the old, that's about it. What he's saying is that you didn't pour hours upon hours trying to get your phone rooted, so don't complain. I'm not flaming, just pointing out his point, which I tend to agree with. I had already rooted my phone by the time I made even my first post on here, and that was after about 16 hours spent researching and double-checking and trial and error. Now people are getting rooted in less than 15 minutes without having to do much outside read a post from the forum.
As for your problem with not having data coverage and SuperOneClick not working, you'd be better off rooting using the old method anyways. And yes, SuperOneClick has issues, but at least it works for 2.2.1 whereas the other two more popular programs (Universal Androot and z4root) died off with 1.6.
Man I agree with crypsmoker and donjuan about you people have no idea how much effort we put into rooting our phones. I learned adb installed development tools and researched countless hours before ever attempting the actual rooting. I am glad it was so hard then. Not saying I don't think less tech savvy people shouldn't have full control of their own phones. Sometimes it takes time to fully understand what it is you are doing and I hope it brings great satisfaction to all who succeed.
Sent from my T-Mobile myTouch 3G using Tapatalk
Impossible to root for newbs?
Well... there's a solution to that. Just don't be a newb.
Am I a newb? I can think of over a dozen just on the top of my head that aren't newbs. Yet we try to help those that are. And what do we get for our efforts? Posts like this. Here's a suggestion for any whiners, you can either NOT root your phone OR develop an easier alternative. Complaining about the process isn't going to get anyone anywhere. It's only going to frustrate the hell out of those that put in hundreds of hours to even make it possible for the non-newbs! Just reading this thread really pissed me off because it makes me realize what I've been wasting my time on. Helping newbs that can't root the phone because it's "impossible." And if you think that it really is impossible then try starting off with a brand new linux based operating system on an alien device. That was the G1. That was some work! It involved telnet, mounting the system as rw, dowloading and PUSHING files over with adb, etc. That was just to GET root. So now we have a 1-click method that doesn't always work on all devices and your pissed? Whatever. Anyone that isn't persistant enough to get root either doesn't want it bad enough or your just too damn lazy to accomplish it. All of the information is available and there are HUNDREDS if not THOUSANDS of people that have accomplished what you can't. So by that very definition there are probably more non-newbs than there are newbs like yourself! Yet you come in here and get all pissed off because you can't get root. Okay... so how is that everyone elses fault? We understand that your upset but don't start pissing all over those that worked hard to get us where we are now! I hate getting pissed on by ungreatful, newbs with a bad attitude! In fact... anyone that has that kind of attitude I will refuse to help them. Why? Because they will never be greatful and they will never learn anything for themselves. That is why I don't spoonfeed and don't support spoonfeeding. Just saying that you've "read all over the internet" for your solution is naive. There is so much information out there that you wouldn't get to read it all by your 90th birthday! Information that was put out there like people like those that you just spat on with your pointless thread!
So with that in mind...
THREAD CLOSED
I am returning my bricked kindle fire today to pick up a new one. I bricked it trying to sideload Go Launcher EX. I would like to know what steps I can take to avoid the same fate for this new one. What can I install to be able to rescue it if something like this happens again?
Suggestions:
Don't make changes that you don't know how to undo.
Read the entire thread for a mod to see what problems or issues others had before trying
Don't be the first to try a new mod
Have your systems setup and tools available to revert the changes back to stock to get out of problems
I have not really seen anyone with a "Brick" yet that could not be overcome by some method that was not a hardware problem. Most of the people who have sent back their devices didn't/couldn't try the methods to correct their device.
A lot of people simply jumped in because they saw there was a mod you could do before doing any research on what the mod is, how it will effect their device.
Most didn't bother reading the entire process BEFORE attempting the mod to see what issues others ran into so they knew what to expect.
There is a reason why most platforms not just phones/tablets come with root protection turned off.
/\ What he said.
I don't want to be a **** but it is people like you that make people who root their device look bad to the general public and make equipment manufacturers try to make it harder for us.
If you are not willing to read some of the "recover from problems rooting" or "unbrick" threads before you return it then tell us what you did and what the device is doing and someone will try to help before you go and return a device which is probably fine and can be sorted out with a few minutes of effort.
If you are not willing to make any effort to follow instructions and fix any problems that occur then you should not attempt to root your device in the first place.
Like everyone else has said if you don't know how to recover your device you probably should mess with it.
I don't own a Kindle Fire but my buddy does, he couldn't wait for me to help him this weekend to root it, so he decided to try himself....guess what he soft bricked it. I just spent the better part of the morning reading, reading, reading, searching, reading....you get the idea. I was able to recover his device , root it, install TWRP recovery and CM7 for him.
You should always try to recover your device, spend some time to read, search and learn. Taking it back to the retailer and playing dumb is not the way to fix things. Since you soft bricked just trying to put an app on your kindle (fairly basic skill level) and you eff that up you probably should leave the new one alone. And I mean all of this in a nice and polite way.
you mean..if you don't know..you shouldN'T mess....
Sent from my HTC Vision using xda premium
wait...how do u brick a whole tablet trying to install a launcher? that's like me bricking my car by spraying windex on the windows. ??? Is it really bricked? describe.
Sent from my HTC Vision using xda premium
cochran.191 said:
How to avoid a brick
Click to expand...
Click to collapse
Duck!
Sent from my Nexus S using XDA App
GBH2 said:
/\ What he said.
I don't want to be a **** but it is people like you that make people who root their device look bad to the general public and make equipment manufacturers try to make it harder for us.
If you are not willing to read some of the "recover from problems rooting" or "unbrick" threads before you return it then tell us what you did and what the device is doing and someone will try to help before you go and return a device which is probably fine and can be sorted out with a few minutes of effort.
If you are not willing to make any effort to follow instructions and fix any problems that occur then you should not attempt to root your device in the first place.
Click to expand...
Click to collapse
I cannot agree with you anymore than I do, this is true with almost any device on the market. From gaming consoles to cell phones. People choose to rush in to a mod but once its messed up they just wanna get another one and possibly/probably do the same to the next device. So preach it brother, I'm behind you.
Sent from my DROID X2 using XDA App
hggadm3 said:
I cannot agree with you anymore than I do, this is true with almost any device on the market. From gaming consoles to cell phones. People choose to rush in to a mod but once its messed up they just wanna get another one and possibly/probably do the same to the next device. So preach it brother, I'm behind you.
Click to expand...
Click to collapse
Well said. If you make a brick, at least post in the thread you were following so at least the dev can figure out if it can be avoided.
androidcues said:
wait...how do u brick a whole tablet trying to install a launcher? that's like me bricking my car by spraying windex on the windows. ??? Is it really bricked? describe.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
He probably didn't brick it(or even come close to bricking it), but had no idea what he was doing so he panicked. I think some, if not most of us have been guilty of that at some point(I remember freaking out when I thought I bricked my iPod trying to install iPod Linux six years ago; fortunately it was extremely difficult to softbrick an iPod and I fixed it in about 3 minutes).
My advice: RTFM. Look at the known issues that people are having and their fixes so you know what to do when you have an issue. I don't think it will be possible for you to root a device and tinker without ever running into any problems. I highly doubt you'll get a brick though
Wow, rough crowd in here. Not saying you're comments are off the mark, but the new year is right around the corner -- let's resolve to be a little nicer to each other!
Sent from my HTC EVO View 4G
I wasn't trying to be an ass I was trying too find out what was going on because sometimes it doesn't add up...and dont like using smiley faces and doing the old "lol".
he who errs...helps best by being verbose about his misfortune just as if he achieved success of the task. round and round we go.
Sent from my HTC Vision using xda premium
One message and he signed up today gtfo and don't even install go launcher from the Amazon market idiot troll ... he never even tried to fix it he never responded to what it was doing .... stupid kid stay out of XDA
Sent from my SPH-D710 using xda premium
How do you brick a device side loading an app?
bdpyo said:
Duck!
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
LOL best post all day.
Sent from my Kindle Fire using Tapatalk
Let me explain what happened. I was trying to sideload Go Launcher EX. When I loaded it up the first time it froze, I restarted, and got the "shimmering" Kindle Fire logo at boot and nothing else. I read pretty much every forum post and website i could find on bricked fires or how to unbrick them. I went through installing the Java Developers Kit, the Android SDK, KFU, and all that. I was able to temp root it after getting it updated with the latest drivers. But still couldn't get anywhere with it so I then decided to just go ahead and install TWRP. I tried to install that through KFU 0.9.1. One website said to boot into fastboot first and go from there. When I tried to do that something happened, I'm not sure what, but it restarted and came up with the solid kindle fire logo. I tried accessing through the command prompt with adb but it was stuck in read-only mode. I tried everything i could find to get it back into read/write mode but to be honest after about 2 days of that I just decided it was better to return it for a new one and get a fresh start. I may be a noob when it comes to Android devices but I am not new to voiding my warranty. I'm just looking for a way to be sure that I don't have this same problem again if something were to happen when I mess around with my fire for fun.
the first one was'nt bricked - for shure
all the information you need is here - the search function is your friend !
you will be stuck in wrong bootmode at some point
to change bootmode manually:
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot reboot
to change system from read to read/write:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
good luck with your second try !
I tried changing it in adb. All I got was the permission denied answer every time. I also couldn't get into su because my root was lost when I tried to restart into fastboot. I tried it all. I just go tired of it so now I'm trying to start over fresh and avoid my mistakes from the past.
as a last resort the use of a factory cable is allways possible
perhaps it's a good idea to buy/build one just in case you need it
instructions to build and use are also here - just search for factory cable
good luck again !
I had thought about using a factory cable but to be honest I didn't have enough worth saving off of that device to justify buying one or spending the time making one. I think this time I'm going to go a little slower and read a little more about things before I try them. I would still like to know what I could do to help prevent/recover more quickly if something happens again.
Can anyone please help me? Today I got my 6P and decided to try and root it. Now it wont get out of the boot animation and ADB devices no longer lists my phone. Is there a chat room or walk through for fixing this? I'm in a pretty large amount of mental agony over this. I just want stock back and will never fiddle again. Promise.
Hawkison said:
Can anyone please help me? Today I got my 6P and decided to try and root it. Now it wont get out of the boot animation and ADB devices no longer lists my phone. Is there a chat room or walk through for fixing this? I'm in a pretty large amount of mental agony over this. I just want stock back and will never fiddle again. Promise.
Click to expand...
Click to collapse
How did you root it? If you follow my guide you'll have no problems.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
You'll need to start from scratch though so follow the directions in section 9 first, that'll take your phone back to stock.
I used the Nexus Root Toolkit I found because I figured I'm a novice, this will do it for me. Hah! Nope. Also tried to restore it that way. No go, surprising no one at this point.
Ok. So i had the wrong file, because again, I'm a moron and it has been proven. Looks like things are going back to stock ok now. <3 :crying: so happy
Hawkison said:
I used the Nexus Root Toolkit I found because I figured I'm a novice, this will do it for me. Hah! Nope. Also tried to restore it that way. No go, surprising no one at this point.
Click to expand...
Click to collapse
Hawkison said:
Ok. So i had the wrong file, because again, I'm a moron and it has been proven. Looks like things are going back to stock ok now. <3 :crying: so happy
Click to expand...
Click to collapse
A word of advice: don't use toolkits. While they may seem helpful for a novice like yourself, they'll keep you at a novice level because they allow you to do things to your device without actually knowing what's going on. This prevents you from doing any learning and advancing. Take the time to learn how to use fastboot and you'll see it isn't as daunting as you may think, plus you'll get great satisfaction from doing these things yourself. Have a look at my guide, and if you have any questions myself and others are there to help.