Related
I am fairly new to rooting, but thanks to this great website and all your inputs I have learned so much over the past month.
I first rooted my G1 using the 1-click method which was great, but now my earpiece has blown I will be receiving a new handset next week. So I learned how to properly downgrade and install stock firmware for my old handset.
When I receive my new handset, I decided to take the plunge and root the traditional way for 2 reasons.. 1- to learn a different way and 2- its possible the security hole may be patched by then rendering the 1-click useless.
Anyway, after reading all the varying posts on how to downgrade/root/flash custom rom I am still left with a little confusion so hopefully someone can clear this up for me.
When actually rooting, I have seen methods to type various things in the telnet window, and another method to just rerun the .apk and select "protect root". What is the difference between these two methods? Do they both accomplish the same task of making a permanent root? One method actually said to download the JFreke rom to fix permissions to root, bo no other method mentioned that. Is that even necessary?
Also, I know that with Cyanogen Roms I do not really need to flash to "hard spl" if I decide to stay with cm roms, and cm recovery also allows the use of nandroid backup as well. The only other argument I have seen is that a hard spl would potentially allow someone to "unbrick" a bricked phone, but from everything I have read, most people have bricked trying to flash the hard spl.
If I am going to stay with cm roms, is there any real benefit to a hard spl other than increasing the brick chance? If I do upgrade the spl, am I correct that it would be done last, after a potential radio update (assuming my replacement handset does not come with the latest radio)?
Sorry for all the questions, and thanks in advance for your help.
This is the best guide I found.
I have done 4 phones using this method with only 2 minor differences.
1) I format the sd card using a microsd card reader instead of the phone.
2) when it says What To Do Now That You Have Root don't download any of the builds listed there, just download the latest cyan stable rom.
This is the guide hehe forgot to link
http://forum.xda-developers.com/showthread.php?t=442480
Oh and don't worry about swap or apps2sd partitions until after you root and verify that the rom is working with no problems, this will limit the number of variables in case you have troubles.
Thanks for the input.
So do you install hard spl according to that guide or do you skip that and just install the cm rom?
I love the auto apps2sd of cm roms. My phone is currently back on stock cupcake and I miss having all my apps on my 500mb ext 3 partition!
yea you need HardSPL. and use the recovery linked in the guide. Install cyan's recovery later.
This to me is the easiest step by step visual rooting process have done 3 G1 with full success. The newest G1 I had would not let me do the 1 click rooting method.
http://www.youtube.com/watch?v=xOo2V9qCauc&feature=related
maybeoneday said:
This to me is the easiest step by step visual rooting process have done 3 G1 with full success. The newest G1 I had would not let me do the 1 click rooting method.
http://www.youtube.com/watch?v=xOo2V9qCauc&feature=related
Click to expand...
Click to collapse
Yeah I figured the new handset would most likely be patched. What was the result when you tried the 1-click. Would the new phone just not let you install the 1-click apk?
One thing I might add is you can't brick your phone by flashing Hardspl. It's the "danger" spl that has the potential of bricking your phone. Just follow the traditional guide that fingerlickin provided and your good to go.
Thanks for the help!
Anytime.......
Nope sure wouldn't just kept telling me install aborted. I don't no why. It could be some kind of patch. But I went to old faithfull step by step you tube install. Its really a nice video. You can pause the video and root your phone right along with guy doing the video. he also gives you links on the side bar to all files needed in the rooting process.
oh I'm sorry, I actually have one more question.
After flashing the HardSPl, would there ever be a reason to revert back to the original g1 spl? For instance if I had to send a phone back to t-mo, would they know that I am using the hardspl if all I did was reload the dreaimg.rbh rc-29 downgrade, or does that also reflash the spl back to the original?
Yes you would want to unroot phone before sending it to Tmobile, they do not warrenty a rooted phone
Unrooting
http://forum.xda-developers.com/showthread.php?t=491350
dcorrea said:
oh I'm sorry, I actually have one more question.
After flashing the HardSPl, would there ever be a reason to revert back to the original g1 spl? For instance if I had to send a phone back to t-mo, would they know that I am using the hardspl if all I did was reload the dreaimg.rbh rc-29 downgrade, or does that also reflash the spl back to the original?
Click to expand...
Click to collapse
You shouldn't ever have to go back. T-mo would prolly never check it. Many people have sent there phones in with root access and different things installed. But if you do get paranoid and ever have to do it, just flash RC29 and it will put everything back to stock.
maybeoneday said:
Yes you would want to unroot phone before sending it to Tmobile, they do not warrenty a rooted phone
Unrooting
http://forum.xda-developers.com/showthread.php?t=491350
Click to expand...
Click to collapse
I turned my phone in with root access and custom splash screen and they didn't say anything. You don't want to make it known that you have done anything to it, but they won't check. When they are sent in they just hook it up with jtag and reflash everything.
supremeteam256 said:
You shouldn't ever have to go back. T-mo would prolly never check it. Many people have sent there phones in with root access and different things installed. But if you do get paranoid and ever have to do it, just flash RC29 and it will put everything back to stock.
Click to expand...
Click to collapse
Ok thanks that is what I figured. I actually just unrooted my phone yesterday from cyanogens rom, but I never flashed the SPL (did the 1-click thing originally), but now that I am going to do the original method I wanted to be sure.
I can't wait for my replacement phone to get here next week, because using the stock cupcake rom sux!
Anyway, thanks to everyone who gave their input and helped me learn even more about the process! You all rock!
supremeteam256 said:
I turned my phone in with root access and custom splash screen and they didn't say anything. You don't want to make it known that you have done anything to it, but they won't check. When they are sent in they just hook it up with jtag and reflash everything.
Click to expand...
Click to collapse
Really, thats music to my ears. I have often thought it would be a pain if something broke on the phone and I had to try to unroot it before I sent it in. uhhhh like a bricked phone
I work in an electronics repair company and I agree with supremeteam256 about sending your phone in rooted. Our techs don't check for tampering, they just plug it in and use the programs my department writes to test and reflash the devices. Of course our devices are much more complicated but the same NON-Communication between customer service and technicians still exist.
I think the biggest reason for this is because the techs just aren't interested in explaining the technical details to a customer service rep because all they ever get is "huh? wtf is a bootloader?"
Disclaimer:
I'm not claiming that HTC or TMobile will not check or notice that you have rooted your phone. Just illustrating that the repair techs don't want to talk to customer service anymore than you do and would rather just fix the phone and move on to the next one.
Fingerlickin said:
I work in an electronics repair company and I agree with supremeteam256 about sending your phone in rooted. Our techs don't check for tampering, they just plug it in and use the programs my department writes to test and reflash the devices. Of course our devices are much more complicated but the same NON-Communication between customer service and technicians still exist.
I think the biggest reason for this is because the techs just aren't interested in explaining the technical details to a customer service rep because all they ever get is "huh? wtf is a bootloader?"
Click to expand...
Click to collapse
Nice breakdown.
I'll be rooting tomorrow. Any thing I sure make sure not to do? Any certain apps not to try or stuff that's really successful?
Don't Brick it.
Check the firmware that you have .... if it is 1.4.0 or newer, you need to make sure the root method applies.
I don't have a NC, but want to get one over the Holidays. I was reading this information on NookDevs.com
cal3thousand said:
Check the firmware that you have .... if it is 1.4.0 or newer, you need to make sure the root method applies.
I don't have a NC, but want to get one over the Holidays. I was reading this information on NookDevs.com
Click to expand...
Click to collapse
1.4.0?! I think that's for the Nook, not the NC. NC is only 1.0.0 with MAYBE 1.0.1, but that's not confirmed yet.
I followed the Windows 7 guide on the wiki, I think it's the best "complete" guide available and has more information as well as being updated than some of the other posts. Ultimately, you're going to be doing a lot of reading as I don't think there is a definitive guide on what to do post-root. Such as enable superuser, and how to install apps (adb install (appname.apk)
Sirchuk said:
1.4.0?! I think that's for the Nook, not the NC. NC is only 1.0.0 with MAYBE 1.0.1, but that's not confirmed yet.
I followed the Windows 7 guide on the wiki, I think it's the best "complete" guide available and has more information as well as being updated than some of the other posts. Ultimately, you're going to be doing a lot of reading as I don't think there is a definitive guide on what to do post-root. Such as enable superuser, and how to install apps (adb install (appname.apk)
Click to expand...
Click to collapse
Thanks for clarifying that...
So the phantom supposed root ruining update is 1.0.1
Does that affect new device root opportunities? I'm trying to get all my gifts in B&N giftcards and want to make sure its not all in vain.
cal3thousand said:
Thanks for clarifying that...
So the phantom supposed root ruining update is 1.0.1
Does that affect new device root opportunities? I'm trying to get all my gifts in B&N giftcards and want to make sure its not all in vain.
Click to expand...
Click to collapse
There's only been one report of it so far, so no one's sure about details. 1.0.1 was the reported updated version though.
Yeah we really have no idea, and even if 1.0.1 is real and does unroot, we don't know if it's possible to re-root using a different method.
Honestly, nobody can tell you one way or the other. Risk it, and hope the next release gets rooted (as most usually are) or get something more generic, like bestbuy certificates and buy it from there instead.
That way, if it is made un-rootable, you can still get something besides books.
Sirchuk said:
That way, if it is made un-rootable, you can still get something besides books.
Click to expand...
Click to collapse
As far as I can tell, the worst that BN can do is make the stock firmware really unpleasant to root. We should always be able to boot into our own custom fw from SD.
Sirchuk said:
Yeah we really have no idea, and even if 1.0.1 is real and does unroot, we don't know if it's possible to re-root using a different method.
Click to expand...
Click to collapse
It will be trivial to re-root an "upgraded" device. Trivial != legal though.
Trivial == taking a dd image from a rooted 1.0.0 device and applying it to a device that has 1.0.0+ (B&N's attempt to stop rooting).
In less that 10 mins, I can take the nooter image that folks are using to root 1.0.0 devices and turn it into a "flash back to 1.0.0 + rooted" image. It's going to go from 40M to ~5G though since I would need to have a dd image of an already rooted device included.
It's as simple as overwriting the partitions that hold the OS with an image that has root enabled.
The problem here is that there are portions of the image that are NOT GPL but are proprietary B&N software. That makes this very doable but also very illegal which is why the original rooters didn't just distribute an image that would turn your phone into a completely rooted device with all kinds of nifty apps installed, tuned and tweaked for you. Its all about not going to jail ya know!
Had OD and loved having it rooted. (My sister's bf helped me. I'm more or less a newb) Had to upgrade to Bionic and while I love it am missing root.
I've been searching online and between info about root and the upcoming ICS update I am getting confused.
Should I root now and wait for ICS? Or wait for ICS then root?
It seems pretty likely that there will be ICS based ROMs available long before Motorola gets around to releasing an official OTA update.
kimeee said:
(My sister's bf helped me. I'm more or less a newb)
Click to expand...
Click to collapse
You need not be rooted at all. If you don't know exactly what you're doing, you should NOT be rooted because you WILL brick your phone.
If you really want to be rooted, you need to do some research and get more familiar with it, what it's for, how it works, and what it can do to your phone.
You probably want to be pretty familiar with ADB too.
I am running the most current unreleased patch 5.7.893 and have not really read what I am really going to gain my rooting. If someone can tell me what I would get that would be worth rooting I will root. but running stock OTA roms specially the 5.7 has fixed most of what was wrong with the phone. I would if I was you just patch per instructions on here rootzwiki.com/topic/8562-easily-upgrade-to-57893-keep-root-and-webtop/ to get the fixes unless someone says there is something well risking rooting
ichigo007 said:
I am running the most current unreleased patch 5.7.893 and have not really read what I am really going to gain my rooting. If someone can tell me what I would get that would be worth rooting I will root. but running stock OTA roms specially the 5.7 has fixed most of what was wrong with the phone. I would if I was you just patch per instructions on here rootzwiki.com/topic/8562-easily-upgrade-to-57893-keep-root-and-webtop/ to get the fixes unless someone says there is something well risking rooting
Click to expand...
Click to collapse
If you are happy with what you have on your phone now, you shouldn't root.
Better to not take the chances.
Oh and...it takes a lot of manual coding to root for you now because the 893 kernel blocks all One-Click-Root programs from working. You have to do it all manually now, and you have to go back to 886 before you can root again anyway.
Tivo7 said:
If you are happy with what you have on your phone now, you shouldn't root.
Better to not take the chances.
Oh and...it takes a lot of manual coding to root for you now because the 893 kernel blocks all One-Click-Root programs from working. You have to do it all manually now, and you have to go back to 886 before you can root again anyway.
Click to expand...
Click to collapse
Yea I understand about going back. I had to go back just to get the webtop working in 5.7.893. I did the incremental one and lost webtop. used the R3l3AS3DRoot_Windows_V2.1 to go back to the 886 then used the single file update to 5.7 and everything works great. I would probably root if I could get free wifi hotspot so I could use my XOOM thru my phone cause I don't want to pay the hotspot or extra for more 4G bandwidth for my XOOM since my phone is unlimited
I didn't brick my last phone. Rooted all by myself. BF just pointed the way.
kimeee said:
I didn't brick my last phone. Rooted all by myself. BF just pointed the way.
Click to expand...
Click to collapse
Even if you did do it by yourself, if you don't know where to go from there, I wouldnt do it.
Its fun seeing the ROMs that are put out but unless that tutor is available I wouldnt do it. Bricking your phone isnt cool.
Rooting really isn't that big a deal once you have some idea what you are doing.
I have had 3 rooted phones and have rooted/jailbroke/hacked just about every other electronic device in my entire house at one point or another.
Do your research, and make sure you follow the instructions. Of course it also helps if you are familiar with ADB and a command shell so you know what the commands you are running actually do too.
Oh, and wait for ICS? C'mon you know XDA will have that at least 2-3 months before it get's an OTA update. [this is fact] <-- don't hold me to that.
Terror_1 said:
Oh, and wait for ICS? C'mon you know XDA will have that at least 2-3 months before it get's an OTA update. [this is fact] <-- don't hold me to that.
Click to expand...
Click to collapse
Exactly. Motorola will have to start all over with Blur, that is gonna take forever. Rooting a phone with a decent developer community will always mean you have access to the new toys well before the OTA updates.
At the OP, You should have also ran the 43V3R root when you did R3L3AS3DRoot. I'm not an expert on android software and rooting but when I had my X2 I did some minimal research and haven't ran into any problems. When I got my Bionic I rooted it within the first 20 min of getting it. The tools that Dhacker put out (R3L3AS3DRoot, etc.) are amazing and rather easy for someone who is less experienced. They also make it nearly impossible to brick your phone as you can just run it again to get back to stock. Not to say you should just rush into things with reckless abandon.
If you do some research and read EVERYTHING that a developer provides as a guide to flashing their ROM, mod, hack, etc. you'll most likely be ok. Just do everything in small steps. As to your question about ICS though, do like I said. I know it's a pain but backup all your apps and run the R3L3AS3DRoot again, but then also run 43V3R root and intall Cheesecake. All of these can be done with the same tool. Then flash the 5.7.893 update and bam, you have the latest version and your still rooted. You may have to reinstall Super User from the market though.
As far as how useful having a rooted phone is, it all depends on what you will actually take advantage of. One of the simplest things is to just flash a custom ROM and enjoy the changes the developer has made. Liberty is top notch and I would reccomend it to a "newb". Personally I am quite satisfied with stock and would rather customize everything to my own personal satisfaction. If you go that route there are still great things out there. I'm using the V8 Supercharger script and ROM toolbox. TBH I'm not really sure what I'm doing with scripts but there was a good guide for the V8S one and I would highly suggest ROM toolbox. You can use it to install custom fonts, boot animations, download and install custom ROMs (though I think it only supports liberty (haven't tested it)) freeze or uninstall bloatware apps. Basically it's about 10 or so apps in one and it's very user friendly.
Wow this is getting way longer than I planned so here's the:
TL;DR
Do research til you feel comfortable. Read EVERYTHING any developer gives you as a guide. Don't rush into things. And looks at all your options. Rooting gives you access to a few neat tools and hacks to get everything you can out of your phone. Just keep R3L3AS3DRoot handy and you have a very low chance of completely bricking your phone. Also as a disclaimer, I'm not responsible if you completely wreck your phone.
Edit: Adding some links to helpful reads.
FAQs, highly recommend.
List of all ROMs and most tools, etc.
UOT Kitchen, very user friendly way to theme your phone. PM me if you want to use this because there are certain things you must do and things you cannot do.
Hope I have helped a bit.
R3L3AS3DRoot and 43V3R Root were easier than expected.
I say go for root that update is a few months away anyways just make sure you know what you're doing.
Sent from my DROID BIONIC using XDA App
I'd like to flash my Vivid with the new Rum Float ROM and from what I gather; now that a RUU is available it should be fairly easy. I.bought the phone last Thursday and haven't had a chance to grab a SD card. I just want to make sure that I fully understand the process involved. I've read a number of posts here at XDA and elsewhere but I still have a few questions to make sure my knowledge is solid and I don't end up with an HTC paperweight! A) Will the Android market will have a record of what I have already dl'd so I can dl it again? B) Is using the RUU executable fairly simple? Should I do the BL UL before I restore?(I would like root, so I'm assuming that this is one of the first steps!) C) Is it a simple follow the instructions sort of thing with the RUU? D) Will "frigid's" "supertool" method to get root work in this instance or do I need to use CWM? E) I'm using an AT&T Vivid could somebody give me a simple step by step(not in detail, but if you could that would be great!) Such as "1- Do BL UL, 2- Run supertool for root, 3 - Run RUU, etc, etc, etc
Also there appears to be a sense and a NONSense version of the ROM, are they both included in the RUU exe file? And for the NONSense version will there be any difference in stability, performance, you acceleration, etc?
Thanks for any info in advanced!
-MeeGz-
MeeGz said:
I'd like to flash my Vivid with the new Rum Float ROM and from what I gather; now that a RUU is available it should be fairly easy. I.bought the phone last Thursday and haven't had a chance to grab a SD card. I just want to make sure that I fully understand the process involved. I've read a number of posts here at XDA and elsewhere but I still have a few questions to make sure my knowledge is solid and I don't end up with an HTC paperweight! A) Will the Android market will have a record of what I have already dl'd so I can dl it again? B) Is using the RUU executable fairly simple? Should I do the BL UL before I restore?(I would like root, so I'm assuming that this is one of the first steps!) C) Is it a simple follow the instructions sort of thing with the RUU? D) Will "frigid's" "supertool" method to get root work in this instance or do I need to use CWM? E) I'm using an AT&T Vivid could somebody give me a simple step by step(not in detail, but if you could that would be great!) Such as "1- Do BL UL, 2- Run supertool for root, 3 - Run RUU, etc, etc, etc
Also there appears to be a sense and a NONSense version of the ROM, are they both included in the RUU exe file? And for the NONSense version will there be any difference in stability, performance, you acceleration, etc?
Thanks for any info in advanced!
-MeeGz-
Click to expand...
Click to collapse
The RUU DOES NOT CONTAIN MY ROM. It is an official tool used by HTC for upgrading and returning to stock.
Android market will keep tabs on purchased apps. It will not keep track of free apps.
You need an sdcard to keep safe.
The RUU is easy to run. Its just an exe. Follow the on-screen prompts.
I don't know what you are trying to restore but it would appear you have your terminology and methods all mixed up.
RUU will get you a stock ics. And it will wipe your apps and settings. It will act like a phone you just pulled out of the box with ics.
In order to run rum float (or any aftermarket rom) you need to unlock your bootloader. Rooting has nothing to do with it. Unlock bl then flash recovery on then flash rom and kernel.
Your steps as you perceive them are slightly off. I don't recommend you do anything to your phone right now.
After you complete the RUU you'd have to go to htc.dev and unlock your bootloader. After you can fastboot flash a recovery and CWM with root. After that's complete you can flash a rom of your choice. I'd get familiar with using fastboot commands in ADB (command prompt). I guess you can use the supertool to root but it isn't necessary really a matter of preference. Check out the superguide. Maybe PG or someone can update it with specific steps if you are using the RUU but the process is the same. It starts with the unlocking the bootloader. Definitely pick up an SD card!
Thanks for the quick replies and the clarification. I think I get it now, I would do the following to get to a rooted custom ICS Rom: Unlock the boot loader, root and run titanium backup to save my apps(using an ad card), run the RUU and get to stock HTC ics, copy ROM to sd card, re-root, download and run CWM, root again and restore apps with titanium backup, enjoy!
The only things that may be a bit off in that process is running the RUU as I don't need that to just flash a custom ROM, assuming said ROM includes the ICS kernel. If did have to use the RUU would I have to re-root to run cwm? Also the actual ROM itself is installed from HBoot, correct?
Sorry if these sound like dumb questions, I'm just new at this. I really appreciate the replies. I'm sure I will pick this up fairly quickly as I have years of linux & OS X command line experience and am well versed with c. It's just kind of information overload on this board as there is such a wealth and variety of info here!
Thanks again,
-MeeGz-
So you can run the ruu.exe even if you are rooted, unlocked bootloader, on att stock? Or do you have have to relock bootloader to proceed with the ruu?
Sent from my HTC PH39100 using XDA
RUU is for stock roms IIRC. If you are rooted and already unlocked I'd use the original method PG and Thecubed created.
back on my computer for a little better explanation.
the RUU or the methods that thecubed and i have laid out will get you the necessary HBOOT/RADIO/etc that you will need to flash a custom ICS rom
either method will get you the same thing....an updated HBOOT and ICS
if you run the bootloader unlock tool from htcdev, YOU WILL LOSE ALL YOUR SETTINGS! it will wipe the device like its brand new......do NOT include this in your dreams of getting backups prior to flashing a custom rom....
please just read through the posts and understand what is going on.
in order for ICS to happen on your vivid you need the new HBOOT, Radio, and various other components that the RUU/PH39IMG contain
there are 3 different roads you can follow to get there, the EASIEST being just run the RUU (WHICH WILL ALSO WIPE SETTINGS!), afterwards, reboot to bootloader, unlock bootloader, reboot to fastboot, fastboot flash the boot.img and the recovery.img of your choice on (limited on boot.img's at the moment, better use the one from the rom), reboot to recovery and flash the rom
the other methods imply you understand somewhat how the process works.
relock bootloader (if unlocked), run PH39IMG install, unlock bootloader, fastboot flash recovery and boot.img, reboot to recovery and flash rom.....
if you wrap your head around HOW it works, its all really simple....so the first step is understanding HOW it works, not blindly following some tutorial or walkthrough.
please try to LEARN and UNDERSTAND what it is you are doing....
PS. you have involved ROOTING too many times in your post...... the rom is already ROOTED, you dont have to ROOT to unlock, flash rom or anything....ROOTING is only applicable INSIDE the booted OPERATING SYSTEM, and has nothing to do with recovery/bootloader
i feel i need to apologize to the board here.
frustrations were not directed at the OP of this thread, just in general....
i have been inundated with PM's and seeing the same barrage of questions for the last few days on the forum....
i can understand everyone's excitement...hell i was excited to get this too.
but you all need to read, and try to take it all in before attempting anything. sometimes those of us that understand whats going on, dont explain in a whole lot of detail, because we take the knowledge for granted, and assume if you are on this site, you are here to learn. it is frustrating to see the same questions pop up on nearly an hourly basis...
all i ask is that you take forth the effort to learn how these tools of ours work and understand that a lot of us working on things like this rely on you guys to assist each other in the process. that leaves us more time to deal with what we need to deal with and try and fix and squash bugs/processes/etc.
in return i apologize if i seem on edge the last couple of days...its because i am. if you can imagine one question multiplied by a hundred.....and having people freaking out about them 'bricking'.....after being warned its possible, but unlikely. i think most of these 'bricks' are salvageable and just require someone that understands how they work.
sorry to seem like an ass, but mainly its because i am an ass, and i have a hard time being nice most of the time.
Thanks pirateghost. I understand how to do the other methods but wanted to use something less complicated with less risk for user error. I read and read everything that is posted on the forums. I try not to ask a question unless I am not understanding what has been posted. Thanks for your patience and understanding.
Sent from my HTC PH39100 using XDA
PG, so im pretty sure i "bricked" it lol. im not upset as it was entirely my fault, just wondering if there is any way to get this mother to turn on? i know that when i plug it into the computer it recognizes it but not as anything i have seen lol..if i can find the correct drivers can this be reversed?
Thanks
Thanks to PG for everything and the instructions. I thought I had bricked my phone, but theCube was able to help me on IRC, which is where I suggest anybody go for real-time assistance.
This could off all been avoided with step by step Detail instruction. Why? Well example , I don't follow this forum at all never had an HTC phone but my wife's phone the vivid. All my phone has been Nexus and the galaxy line from Samsung, things over there are a bit different. All I did was flash the ph.img and then after not seen the device reboot I wipe/factory reset and all when to hell from there. Couldn't unlock the bootloader or reboot the phone. How could this happen? Assuming that people should know the basic is wrong. I'm not in any way blaming anyone I did this own my on risk but at the same time I'm super mad had to buy a new phone. As developer you should eliminate all threats and post a details instructions step by step with do's and don't before posting firmwares.
Sent from my Galaxy Nexus using xda premium
Dxtra said:
As developer you should eliminate all threats and post a details instructions step by step with do's and don't before posting firmwares
Click to expand...
Click to collapse
As a user, you should understand the risks/benefits of the things you download. The devs are under no obligation to keep you from bricking your phone, and to be fair, most everything is covered in the Superguide and the various ROM threads. Even if someone were to post a file called NOT_A_VIRUS.EXE and you downloaded it and it wiped your computer when you ran it, the responsibility is squarely on your shoulders.
As far as I remember, there is no dev/user contract and they're not getting paid for any of this.
Dxtra said:
As developer you should eliminate all threats and post a details instructions step by step with do's and don't before posting firmwares.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
oh?
am i being paid to do a job here?
i gave instructions based on how *I* got it to work and duplicated the procedure several times. so its MY responsibility to try and find a way to brick my phone for you?
an RUU cant brick your phone.....however, being a retard can.
this is the type of attitude i would expect my boss to have, if i screwed up a project....but alas, i am here out of my own free will.....
if this is how you feel, then you should get the F off this site.
formicae said:
As a user, you should understand the risks/benefits of the things you download. The devs are under no obligation to keep you from bricking your phone, and to be fair, most everything is covered in the Superguide and the various ROM threads. Even if someone were to post a file called NOT_A_VIRUS.EXE and you downloaded it and it wiped your computer when you ran it, the responsibility is squarely on your shoulders.
As far as I remember, there is no dev/user contract and they're not getting paid for any of this.
Click to expand...
Click to collapse
I totally 100% agree with you. If you HAVE taken the time to read and are still a bit confused, ask! For me I'm not even a week into this platform and I WILL NOT do anything that I don't entirely understand. The problem with android, if you could even call it a problem, is that there is such a huge variety of handsets and a big variety methods for doing this, that, and the other thing. It basically results in a non-linear process to get from point A to point B. It's imperative to understand the basic proceedures. If you were here since the G1, great, you've been able to.follow things from the start. I've used iOS for years, and I still love it btw.(only jailbroken of course!) I'll probably buy an iPad 3! The software is integrated with the hardware amazingly well, battery life is phenomenal, and ONCE JAILBROKEN, iOS is an excellent platform. Sure the "spec numbers" may not be as high but it boils down to.performance. That has always been great for me, obviously battery life is exceptional on apple devices as well. I'm hoping with a rooted ICS Rom there won't be cpu-time hogging processes and ill be able to adjust other things accordingly to get somewhat better battery life. I really wish each OEM would take the time to optimize the SW that they're using to the HW that they're selling. B/C from what I've seen the "Nexus" devices generally perform extremely well, even.against higher spec'd devices. So far I'm loving Android and my Vivid. I love the freedom that I get even on a non-rooted device! It's an excellent platform. Flexible, dynamic, and personal. Customization is there from the get-go. There are a million different things that one could do, even while staying un-rooted. The only reason that I've waited so long to get on board with android is ibwas waiting for it to grow and mature, if I could have a device that tri-booted Android, iOS, and WebOS I'd be a very happy person. I love using multiple platforms.
PG - I'm sorry if I bothered you, thanks for the great info though!
I think knowledge-wise I'm at a point where I'm not going to brick my phone. Wish me luck!
Pirateghost said:
oh?
am i being paid to do a job here?
i gave instructions based on how *I* got it to work and duplicated the procedure several times. so its MY responsibility to try and find a way to brick my phone for you?
an RUU cant brick your phone.....however, being a retard can.
this is the type of attitude i would expect my boss to have, if i screwed up a project....but alas, i am here out of my own free will.....
if this is how you feel, then you should get the F off this site.
Click to expand...
Click to collapse
Seriously if that is how you feel do get the f*ck off this site please. The devs in all mobile hacking communities are unpaid and do it for fun. You sir are a prime example of WHY THEY LEAVE!!! IF YOU DON'T KNOW AND HAVE READ, ASK, DON'T BE A ****!!!
Dxtra said:
This could off all been avoided with step by step Detail instruction. Why? Well example , I don't follow this forum at all never had an HTC phone but my wife's phone the vivid. All my phone has been Nexus and the galaxy line from Samsung, things over there are a bit different. All I did was flash the ph.img and then after not seen the device reboot I wipe/factory reset and all when to hell from there. Couldn't unlock the bootloader or reboot the phone. How could this happen? Assuming that people should know the basic is wrong. I'm not in any way blaming anyone I did this own my on risk but at the same time I'm super mad had to buy a new phone. As developer you should eliminate all threats and post a details instructions step by step with do's and don't before posting firmwares.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
REALLY? You want the UNNPAID DEV'S TO REMOVE ALL THREATS?!?!?! FROM WHAT IS BASICALLY OSS AND A FIRMWARE THAT SOMEBODY DL'D? REALLY? These guys take a FW and cook it into a ROM for FREE and just b/c you didn't take the time to understand it you're gonna put it on them? WTF?!?!?!?
i'll make him a deal. next time we get a hold of something like this, i will let him figure out how to get it on his phone....i don't have to share how...
Dxtra said:
This could off all been avoided with step by step Detail instruction. Why? Well example , I don't follow this forum at all never had an HTC phone but my wife's phone the vivid. All my phone has been Nexus and the galaxy line from Samsung, things over there are a bit different. All I did was flash the ph.img and then after not seen the device reboot I wipe/factory reset and all when to hell from there. Couldn't unlock the bootloader or reboot the phone. How could this happen? Assuming that people should know the basic is wrong. I'm not in any way blaming anyone I did this own my on risk but at the same time I'm super mad had to buy a new phone. As developer you should eliminate all threats and post a details instructions step by step with do's and don't before posting firmwares.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You know, its users like you that get Devs frustrated and not want to share the work that they have accomplished. XDA is a site for Devs, its not a WalMart that people can stop by and expect to be spoonfed and be on their merry way. Pirateghost is a very talented Dev who wanted to share something with this community, and instead of saying "thank you" you decide to look a the glass as half empty instead of half full and EXPECT MORE from him?
Reading your post, it tells me that you dont frequent the HTC forums at all, and instead of reading up, you just decided to flash. Just because it didnt go as smoothly as you thought it would is NO REASON to tell a Dev that they needed to do more. That part lays on you.
Next time you decide to tell a Dev that "they need to do more" I think you need to do more reading so it prevents you from having to buy a new phone. If it dosent make sense to you or you dont think theres enough documentation/step-by-step instructions YOU HAVE THE POWER TO SAY NO AND NOT FLASH IT.
Uh, there's a reason every single solitary dev puts a disclaimer on their ROM threads. Their work, if directions are not followed to the letter can turn your device into a +/- 200$ paperweight. I've been lurking around these forums for a hot minute, rarely post ( not an ounce of dev skill being the main reason), and really, when's the last time a dev didn't post at least semi detailed instructions to go along with his/her OP.
@pirateghost- bought a vivid literally 12 hours ago, got home, saw your thread, FOLLOWED THE DIRECTIONS CAREFULLY, and now have ICS on my device. Just wanted to say thanks.
And now for the most epic noob question of all time. Wth is RUU? I'm very familiar with flashing roms, cam, tibu, etc from my days on the sgsII SR forums. So most if not all HTC terminology is new to me.
Sent from my HTC PH39100 using xda premium
I just received my Nexus 6 that I bought from Best Buy yesterday and have got it activated today.
I really want to root and try flashing my first rom. I have been reading thread after thread trying to learn and understand what it takes to root a Nexus 6, flash a rom, and what the proper way to do it is. Spent at least 5 hours reading threads and I have been so confused as to what to do.
First, I have read that you should do the ADB way to unlock, root, flash etc. (Nexus 6 all in one Beginners Guide) because using a toolkit will make flashing roms more trouble than its worth.
Next, I have read repeatedly that the method used when the Nexus 6 first came out is still a valid and perfectly fine way to unlock, root, flash, etc , but then I have found in another thread that in order to root it you will need to flash a custom kernal of some sort so i'm unsure what I need to do.
The Nexus 6 All-in-One Beginners Guide seems pretty straightforward and easy, however this is my first time flashing anything and rooting a Nexus device so i'm unsure what I should trust.
Thanks in advance for anyone willing to help give this newbie some advice.
Any help is appreciated, I am just frustrated with trying to find a current method of unlocking, rooting, flashing, etc because nearly every thread I have read is dated back to when the device first came out and I usually am able to learn visually very easily but many videos for the N6 on youtube are from when the N6 came out, dating back 6-9 months ago.
So again, any help would be greatly appreciated because I am getting a bit frustrated with sorting out all the information and learning what I can trust so I don't damage my phone beyond repair.
Thank you again for reading and giving advice if you choose to and I apologize if this sounded like a rant. I just really need some help understanding what to do. Thank you.
If anyone is able to clear up my confusion on the issues I brought up, thank you.
1. Use Wugs to unlock and root
(Sure knowing how to adb is important, but just do that)
2. Wugs will install a custom recovery - you flash roms in said recovery.
3. Apps I recommend you get after obtaining root:
(Some paid, some free)
SuperSU Pro (paid)
Buaybox Pro (paid)
Root Explorer (paid)
Titanium Backup (paid/free)
Then you'll have a pretty good start at supporting the devs, while having a good file/folder control app, and a way to protect yourself against data loss - with a simple way of reverting back to a previous build should you dislike a rom.
Keep reading. You're off to a gold start but I learn more and more every day. Never underestimate the value of reading everything prior to flashing/modifying it just might save you a headache when your phone inevitably bootloops for a silly reason.
iRub1Out said:
1. Use Wugs to unlock and root
(Sure knowing how to adb is important, but just do that)
2. Wugs will install a custom recovery - you flash roms in said recovery.
3. Apps I recommend you get after obtaining root:
(Some paid, some free)
SuperSU Pro (paid)
Buaybox Pro (paid)
Root Explorer (paid)
Titanium Backup (paid/free)
Then you'll have a pretty good start at supporting the devs, while having a good file/folder control app, and a way to protect yourself against data loss - with a simple way of reverting back to a previous build should you dislike a rom.
Keep reading. You're off to a gold start but I learn more and more every day. Never underestimate the value of reading everything prior to flashing/modifying it just might save you a headache when your phone inevitably bootloops for a silly reason.
Click to expand...
Click to collapse
Thank you for your advice. May I ask the difference of doing it with a Toolkit rather than the ADB way ? It just seems that one is easier than the other.
May I ask the pros and cons of doing it the Toolkit way and the ADB way ?
Iandrew124 said:
Thank you for your advice. May I ask the difference of doing it with a Toolkit rather than the ADB way ? It just seems that one is easier than the other.
May I ask the pros and cons of doing it the Toolkit way and the ADB way ?
Click to expand...
Click to collapse
The adb way teaches you how to do it at the base level - this method would allow you to pull files/folders without the phone booting, or flash individual partitions without having to flash a whole image - there's a LOT of reasons to know and understand adb, and you eventually should, as it could save your phone when all else fails.... It has its benefits, but for simplicity's sake - for now - just use Wugs.
Using toolkits in effect gives you a crutch. With this crutch you then are forced to depend on this crutch for future needs. What happens when you get a update or different phone that Wugs doesn't work with or do what you need to do? THATS where adb understanding would come in handy.
I NEVER recommend people use toolkits exclusively as this can and WILL eventually lead to major issues that the user is now at step 1 of the learning process all over again - or - are forced to wait for toolkits to be made to do something as simple as obtain root. That's annoying.
In this case, I hope you will make yourself more familiar with adb when you can, use it, try it out, understand what it does and what it's for - but just to get you up and running you can use the kit, just don't expect it to be that easy every time because, I promise you, it won't be and at some point adb will be the only option you have. You don't want to have to be in a panic situation when that knowledge could have saved you.
That's just how I like to help people learn this stuff. Start off slow just so they can do what they want to do - but heavily stress the importance of HOW that toolkit works - because its doing what you need to learn how to do - it just does it all for you.
Don't rely on that crutch - it won't always be there.
Iandrew124 said:
. . .
May I ask the pros and cons of doing it the Toolkit way and the ADB way ?
Click to expand...
Click to collapse
Manual flashing has the advantage that you controls the 'speed of the process. Because you have to enter commands one by one.
Toolkits use scripts instead of commands. And you have a choice from many options.
You won't be fast enough to stop when using a wrong option/script.
The post of irub1out is a good method.
After point 1. wait a day and go on with reading and posting.
adb is not used in the rooting process. fastboot is used to unlock the bootloader and then flash a custom recovery.
It's a really simple process after installing fastboot.
1. fastboot oem unlock
2. fastboot flash recovery recovery.img
3. Put SuperSU flashable zip on sdcard
4. Boot into recovery and flash that zip
There really shouldn't be any need to use a toolkit and if you do it manually, you KNOW your computer is configured properly so if you need it for recovery purposes later and something is not working, you know it's not the computer that is the issue.
Use the toolkit for other things once you've done the unlock and flash manually by all means. But NEVER use the toolkit first. This is a recipe for disaster.
Although the previous posts stress the importance of learning manually, they kind of miss part of the point as to why and I bet 90% of our experienced users here will agree with me...NO SHORTCUTS FIRST TIME.
If you need more info on fastboot, there's an adb and fastboot thread in general > sticky roll-up thread.
I concur with @danarama. We spend half our time in this forum trying to fix mistakes made with toolkit.
really, if the user doesnt have the proper knowledge to make the simple choices given in the toolkit, they are not going to choose the right files to do it manually.
so it makes no difference really, other than the person gaining the knowledge to understand exactly what they are doing, which i agree with,
but regardless of what any user might claim, the toolkit doesnt make mistakes. it executes the same commands you would use manually via a script based on your choices.
there is no margin of error other than the users input.
j
bweN diorD said:
really, if the user doesnt have the proper knowledge to make the simple choices given in the toolkit, they are not going to choose the right files to do it manually.
so it makes no difference really, other than the person gaining the knowledge to understand exactly what they are doing, which i agree with,
but regardless of what any user might claim, the toolkit doesnt make mistakes. it executes the same commands you would use manually via a script based on your choices.
there is no margin of error other than the users input.
Click to expand...
Click to collapse
first off, toolkits DO occasionally make mistakes, it has been proven, so dont argue with that. sure, its not always, but it happens. secondly, the user choosing files.. ok, if you do it the right way, there are only two files you need. and the user doesnt have a choice to pick them. they are the twrp recovery, and supersu. the user has to go find them, not pick out of a list. and witj my time on the n6 since last November, not one person picked the wrong files to root their phones. again, its because they arent given a choice.
bweN diorD said:
it makes no difference really, other than the person gaining the knowledge to understand exactly what they are doing
Click to expand...
Click to collapse
...and to ensure fastboot is Working, as I mentioned in my post. So it does make a difference.
a person gaining knowledge to understand what they are doing is by far the most important thing that can happen. thats something thatll never happen with a root toolkit.
Iv'e had several good flashes and some bad using the exact same files and same options during testing and playing. Worst button/option to even be available to noobs is the lock after flash or even a relock button at all. Remove that option and you are pretty much safe from hard brick. Then only have to come back and ask us to walk through fastboot when the flash goes belly up. Need an audit on how many times we have seen this exact scenario.
prdog1 said:
Iv'e had several good flashes and some bad using the exact same files and same options during testing and playing. Worst button/option to even be available to noobs is the lock after flash or even a relock button at all. Remove that option and you are pretty much safe from hard brick. Then only have to come back and ask us to walk through fastboot when the flash goes belly up. Need an audit on how many times we have seen this exact scenario.
Click to expand...
Click to collapse
That's another good point.. When 5.1 came out and locking the bootloader after flash, if it didn't boot, it would be a brick.. Toolkits would do this after a flash and brick phones.. You have to wait until the toolkit is updated before using it safely.
simms22 said:
j
first off, toolkits DO occasionally make mistakes, it has been proven, so dont argue with that. sure, its not always, but it happens. secondly, the user choosing files.. ok, if you do it the right way, there are only two files you need. and the user doesnt have a choice to pick them. they are the twrp recovery, and supersu. the user has to go find them, not pick out of a list. and witj my time on the n6 since last November, not one person picked the wrong files to root their phones. again, its because they arent given a choice.
Click to expand...
Click to collapse
i sir, will argue with whatever i wish.
in the year i maintained a toolkit for the last moto i had, 20k+ downloads, not one user accused the toolkit of flashing something it wasnt supposed to. the code is fairly simple, one option points to a command and file (simply put), etc. etc.
is it possible some one in a million error happened, doubtful but ok.
my comment was more directed at the previous poster who said something about spending 1/2 his time helping users with toolkit problems.
thats very unlikely, unless the toolkit coding is done very poorly.
---------- Post added at 12:27 PM ---------- Previous post was at 12:25 PM ----------
danarama said:
...and to ensure fastboot is Working, as I mentioned in my post. So it does make a difference.
Click to expand...
Click to collapse
how about you quote the rest of my sentence next time, where i agreed with your logic on that.
unless your intentionally trying to start an argument? cause thats what it looks like.
bweN diorD said:
how about you quote the rest of my sentence next time, where i agreed with your logic on that.
Click to expand...
Click to collapse
Because the rest of your sentence was nothing to do with what I wanted to say and you didn't agree with my logic at all. In fact your sentence (even complete) suggests that what I had said wouldn't even factor in to anything.
bweN diorD said:
unless your intentionally trying to start an argument? cause thats what it looks like.
Click to expand...
Click to collapse
I'm 35 years old. I've got better things to do than try to create arguments in Internet forums. I was expanding on your sentence on something you missed. Kick yourself for the omission, not me for pointing it out.
Don't be so bloody confrontational. You're coming off as a petulant child, as does everyone who starts a sentence "how about" without trying to understand what they're talking about first.
bweN diorD said:
i sir, will argue with whatever i wish.
in the year i maintained a toolkit for the last moto i had, 20k+ downloads, not one user accused the toolkit of flashing something it wasnt supposed to. the code is fairly simple, one option points to a command and file (simply put), etc. etc.
is it possible some one in a million error happened, doubtful but ok.
my comment was more directed at the previous poster who said something about spending 1/2 his time helping users with toolkit problems.
thats very unlikely, unless the toolkit coding is done very poorly.
Click to expand...
Click to collapse
if i can get someone that will make a toolkit that does what it does, and goes through every step explaining the process of what its doing and how to do it manually, id be a happy man. seriously.
danarama said:
Because the rest of your sentence was nothing to do with what I wanted to say and you didn't agree with my logic at all. In fact your sentence (even complete) suggests that what I had said wouldn't even factor in to anything.
I'm 35 years old. I've got better things to do than try to create arguments in Internet forums. I was expanding on your sentence on something you missed. Kick yourself for the omission, not me for pointing it out.
Don't be so bloody confrontational. You're coming off as a petulant child, as does everyone who starts a sentence "how about" without trying to understand what they're talking about first.
Click to expand...
Click to collapse
funny, it looks like i am agreeing with the manual logic...
other than the person gaining the knowledge to understand exactly what they are doing, which i agree with,
Click to expand...
Click to collapse
simms22 said:
if i can get someone that will make a toolkit that does what it does, and goes through every step explaining the process of what its doing and how to do it manually, id be a happy man. seriously.
Click to expand...
Click to collapse
I honestly considered making that in the past.
---------- Post added at 05:44 PM ---------- Previous post was at 05:37 PM ----------
bweN diorD said:
funny, it looks like i am agreeing with the manual logic...
Click to expand...
Click to collapse
That's not what we're talking about. I never said you didn't agree with the "manual logic"
Please re-read my post. I think you've misunderstood what I said. Let me know if you'd like me to explain what were talking about afterwards if you still dont understand
Tbh, not using toolkits comes down to this:
Its the easiest ****ing thing ever to do with out one. If you need one, you have a major gap in your understanding... And you need to fix that first. Well you don't "need" to unfortunately, but acquiring root access is taking over being the admin for your device. If you are choosing to do that, you should probably understand the basic tools.
I am in approximately the same position as the OP with a brand new Nexus 6 and I have a question. Should I take any OTA updates that are available before starting the unlock bootloader and rooting process?