Related
I'm trying to root my G1, and despite the fact that every guide in existence gives different steps, I've managed to confirm I HAVE root now but I need to load the HardSPL so I can load roms to the phone... right.
Except when I do HOME+POWER I get the red/green/blue/white boot loader screen and it says Serial0. I don't get the recovery image. Camera button is not stuck, it works fine.
Anybody know why it won't let me to the recovery screen?
EDIT:
Solution: Turns out recovery image itself was corrupt. Downloaded cyanogen's recovery 1.4 and all was well again.
I'm surprised that after reading for hours you didn't post this in Q&A...
Plug in phone.
Do the power home thing.
Press the back key.
Smack forehead with phone repeatedly.
TheDudeOfLife said:
I'm surprised that after reading for hours you didn't post this in Q&A...
Plug in phone.
Do the power home thing.
Press the back key.
Smack forehead with phone repeatedly.
Click to expand...
Click to collapse
Lol after reading this I couldn't stop laughing
Oh COME ON!!!
Talk about rude - you take the time to reply but you don't contribute... wtf.
I have been at this for FOUR HOURS!!!!!!!!!! I have searched every thread I can find for a solution, I haven't been spending hours looking at exactly how I should avoid offending someone! I gotta say, I never got this kind of rudeness in the Vogue forum, maybe switching to an android device has put me in with a new 'class' of users?
Now as far as the problem - the problem is that HOME+POWER does NOT bring up the recovery screen - THAT is the problem! It brings up the boot loader screen instead.
what step r u on ur using this right http://forum.xda-developers.com/showthread.php?t=442480
Sounds to me like the recovery image was not installed in telnet, without it you would not be able to get into recovery cause there is not one to get into, read your steps on rooting and if if you have to redownload a recovery image, that is what happened to me on my second phone that I rooted
gridlock32404 said:
Sounds to me like the recovery image was not installed in telnet, without it you would not be able to get into recovery cause there is not one to get into, read your steps on rooting and if if you have to redownload a recovery image, that is what happened to me on my second phone that I rooted
Click to expand...
Click to collapse
This is what I'm beginng to think, that the downloaded recovery image has errors or something. I think I'll try redownloading it.
Most likely is, it happens every once in awhile and yes you will get some people on this forum that are quite rude and make fun of you without helping, a lot will also sit there and play mod, but you have to just bare with it. There are a lot of great people that will help you out and all the devs do a really great job so the android platform was a great choice in my opinion
well unfortunately, I downloaded the recovery image again, put the sdcard back in the PC, copied it over again, ran through the root process on the device again.... and still can't get the recovery ROM...
did not expect this much of a problem, I had no issues unlocking my Touch VOGUE (similar process) and I run through going to recovery ROM all day long with people at my job, when all the n00bs forget their gmail passwords.
Solved!
After downloading recovery.img 3 times from the thread here: http://forum.xda-developers.com/showthread.php?t=442480, I finally gave up and downloaded cm-recovery-1.4.img instead, renamed it recovery.img, and now I can access the recovery rom.
yay!
kudos to those that helped out! If you ever get me on the line at t-mobile pda tech support just say "xda developers" and I'll make sure to do my best to help out a bud!
That's great to hear buddy, seems like just a bad image, you will really like the g1 a lot now that it is rooted
lotherius said:
Oh COME ON!!!
Talk about rude - you take the time to reply but you don't contribute... wtf.
I have been at this for FOUR HOURS!!!!!!!!!! I have searched every thread I can find for a solution, I haven't been spending hours looking at exactly how I should avoid offending someone! I gotta say, I never got this kind of rudeness in the Vogue forum, maybe switching to an android device has put me in with a new 'class' of users?
Now as far as the problem - the problem is that HOME+POWER does NOT bring up the recovery screen - THAT is the problem! It brings up the boot loader screen instead.
Click to expand...
Click to collapse
TheDudeOfLife has contributed more to this forum and to making your device run like it does more than you ever will. He is one of the main developers here and has a large following using his ROM, it would be hard for him to contribute more than he already has.
Also, he did give you advice, he advised you to try hitting the back button to see if it would do anything, and if as suspected that it did help, he was only pointing out how dumb you would feel if that was all it took.
Just saying... anyways, congrats on fixing your phone. Next time post in the correct forum (I think its been moved anyways), and could you add [SOLVED] to the title of your thread so other might find it easier if they have the same problem.
Well it was resolved which is the main thing, was just a bad image before flashing which can happen.
TheDudeOfLife has contributed a fair bit to Android as well which his ROMs and whatnot and pressing Back does enable FASTBOOT at that stage.
No main harm done eh? ^_^ As h.nocturna suggested, if you could add a "[SOLVED]" tag to the thread title that would be great.
And you should feel privilaged that the dude came here and tried to help.
supremeteam256 said:
And you should feel privilaged that the dude came here and tried to help.
Click to expand...
Click to collapse
Are you serious? He got mocked by the guy and he should feel privileged because the guy is a ROM developer?!
h.nocturna said:
TheDudeOfLife has contributed more to this forum and to making your device run like it does more than you ever will. He is one of the main developers here and has a large following using his ROM, it would be hard for him to contribute more than he already has.
Click to expand...
Click to collapse
Again, the original poster wasn't bashing 'the dude', just stating the obvious fact that mocking people and not contributing makes him look like an ass.
I know this post was very off topic, I was just so shocked that people bow down to ROM developers like they can do no wrong.
AdrianK said:
Are you serious? He got mocked by the guy and he should feel privileged because the guy is a ROM developer?!
Again, the original poster wasn't bashing 'the dude', just stating the obvious fact that mocking people and not contributing makes him look like an ass.
I know this post was very off topic, I was just so shocked that people bow down to ROM developers like they can do no wrong.
Click to expand...
Click to collapse
I was pointing out that he said that the Dude didn't contribute when indeed he gave him instructions on how to solve his problem (contribution #1) and he also contributes by developing ROMs that help everyone (contribution #2). So next time, read what I said and why I said it instead of just taking the quote out of context. And I don't think he was mocking, again, read why I don't think he was.
Wow, when did everyone become such sensitive nannies?
To be honest I thought I was answering his question with a joke and the answer. I didn't read (reading is fundemental) it and realize his recovery was bad. Glad you guys were able to work this out.
TheDudeOfLife said:
Wow, when did everyone become such sensitive nannies?
To be honest I thought I was answering his question with a joke and the answer. I didn't read (reading is fundemental) it and realize his recovery was bad. Glad you guys were able to work this out.
Click to expand...
Click to collapse
I do appreciate any and all help. I apologize for my own rash reactions. hours of fighting with something that should have been straightforward can do that to you! No idea why the image was bad twice, but once I switched to the other recovery image it was all good. I will add [SOLVED] to the title as suggested.
TheDudeOfLife said:
Wow, when did everyone become such sensitive nannies?
To be honest I thought I was answering his question with a joke and the answer. I didn't read (reading is fundemental) it and realize his recovery was bad. Glad you guys were able to work this out.
Click to expand...
Click to collapse
Thank God. I was beginning to think that I misjudged what you wrote and you didn't mean it as a joke. ~sigh~ reading comprehension ftw!
To make all the crybabies happy heres a disclaimer:
Doing this will not mess up your phone. Doing things after this could mess up your phone. Make nandroid backups before making changes to your phone. If you are inexperienced, don't do anything else besides editing/deleting system files on your phone. Flashing other recoveries and other such things could be risky, but removing files from system should have no adverse effects other then maybe causing a bootloop which could be fixed my restoring your system folder. I don't know why people got upset about this, but if you have any brain at all you could of figured this out yourself.
Click to expand...
Click to collapse
You can unlock your nand temporarily and its easy to do.
All you need is the unrevoked tool.
First understand what it is doing. It unlocks your nand to write your recovery image. Normally we cant do this. So look they made this tool to hide what its actually doing, but if you think about it you realize hey if I unplug my USB cable before it flashes recovery and reboots to recovery, I will still have an unlocked nand.
So simple steps.
1. Plug in phone to your PC
2. Run unrevoked tool
3. Let it reboot to bootloader
4. When in bootloader your screen will flash back to the white HTC Incredible screen, at this point unplug your USB and close unrevoked tool(make sure you do it before your phone completely boots and while the unrevoked program still says Waiting for reboot.)
5. Once you get past the bootanimation your phone is unlocked so you can write to /system/
To test, run the app Ad free and update the hosts file, it should say it was successful. If your phone is rebooted it is no longer unlocked.
How many times have you used this trick?
Lets say 20. Well what if on the 21st try, your phone was bricked?
I'm not saying that'll happen, but clearly you didn't write the program, so you have no idea.
I wouldn't suggest anyone try this until unrevoked release a fully tested NAND unlock. There are very few reasons to have NAND unlocked at this time.
I would do this, bit i trist pmf on this one.
Sent from my Incredible using XDA App
pardonmyfreedom said:
How many times have you used this trick?
Lets say 20. Well what if on the 21st try, your phone was bricked?
I'm not saying that'll happen, but clearly you didn't write the program, so you have no idea.
I wouldn't suggest anyone try this until unrevoked release a fully tested NAND unlock. There are very few reasons to have NAND unlocked at this time.
Click to expand...
Click to collapse
There's really nothing to worry about, once your phone is rebooted after hboot and your phone is booting, the program isnt interacting with the phone notice it says waiting for reboot, so really there isnt anything to worry about.
I have done this many times. This is supposed to be an open development community and hiding stuff or making up BS about bricking phones to scare people from trying stuff is really dumb. You root your phone, you are already taking risks doing it in the first place.
TNS201 said:
There's really nothing to worry about the program once your phone is rebooted after hboot, the program isnt interacting with the phone notice it says waiting for reboot, so really there isnt anything to worry about.
I have done this many times.
Click to expand...
Click to collapse
I have to say, it does make sense, but i dont feel like having an expensive brick, so i will wait until proven that i wont brick my phone. I do not like knocking devs and their ideas, so i will try this when i get a chance
Sent from my Incredible using XDA App
I'll give it a shot if another member confirms it working
jdkoreclipse said:
I have to say, it does make sense, but i dont feel like having an expensive brick, so i will wait until proven that i wont brick my phone
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Most people have already ran unrevoked several times to update the their phone's recovery.
SO HOW THE HELL is this any different. Get it through your head and realize that all you are doing is unplugging your phone before it is even going to flash recovery again. The recovery isnt flashed until you boot back into the OS. So pulling the USB before this when the program still says Waiting for Reboot will cause no issue.
What you do to your phone afterwards might cause issues, but people should make nandroid backups before they ever do anything anyways.
TNS201 said:
Most people have already ran unrevoked several times to update the their phone's recovery.
SO HOW THE HELL is this any different. Get it through your head and realize that all you are doing is unplugging your phone before it is even going to flash recovery again. The recovery isnt flashed until you boot back into the OS. So pulling the USB before this when the program still says Waiting for Reboot will cause no issue.
What you do to your phone afterwards might cause issues, but people should make nandroid backups before they ever do anything anyways.
Click to expand...
Click to collapse
I like this idea, and i want to try it, but i dont want to be first. I domt like knocking devs and their ideas, but i dont want to be tje community ginuea pig. I hope ot works, and it makes lots of sense but most of us dont know EXACTLY what unrevoked3 does. I can honestly say, i know it unlocks nand temp, bit i cant say what hardware of software parts it targets. For all i knoe, it could short circuit my phone because the process didnt initualize correctly. No offense to you at all. I think this is a GREAT find, and is very good for the community.
Sent from my Incredible using XDA App
That makes sense(pardon the pun!), TNS201.
jdkoreclipse said:
I like this idea, and i want to try it, but i dont want to be first. I domt like knocking devs and their ideas, but i dont want to be tje community ginuea pig. I hope ot works, and it makes lots of sense but most of us dont know EXACTLY what unrevoked3 does. I can honestly say, i know it unlocks nand temp, bit i cant say what hardware of software parts it targets. For all i knoe, it could short circuit my phone because the process didnt initualize correctly. No offense to you at all. I think this is a GREAT find, and is very good for the community.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Well a few weeks back someone posted some file with a list of commands that temporary unlocks the nand and basically this is what unrevoked is doing along with flashing a new recovery and rooting the phone. Basically its a made program so it can hide what its doing so you the person doing it, doesn't know what their program is doing and also to make it easier for people that are inexperienced with rooting and doing other tasks such as using adb. It basically simplifies the process for the enduser to not have to fuss with adb and any other program or entering commands, etc.
TNS201 said:
There's really nothing to worry about, once your phone is rebooted after hboot and your phone is booting, the program isnt interacting with the phone notice it says waiting for reboot, so really there isnt anything to worry about.
I have done this many times. This is supposed to be an open development community and hiding stuff or making up BS about bricking phones to scare people from trying stuff is really dumb. You root your phone, you are already taking risks doing it in the first place.
Click to expand...
Click to collapse
Where would we be without Unrevoked? They don't hide stuff, they protect stuff. They're protecting exploits from being closed by HTC and phones from being bricked. What it is, is that people are greedy fux and use the phrase OPEN SOURCE/DEVELOPMENT as an excuse to post their (unrevoked's) long hard work all over the forums cause "hey now my adblock works". Its really pathetic! Unrevoked thinks of the big picture, like people being able to root their phones in the future while these other people posting their work are just actually HURTING the community! Now you're gonna post some schlep way to get NAND unlock for one boot, using their tool and then talk **** about their methods. THERE WOULD BE NO DEVELOPMENT SECTION UNDER HTC DROID INCREDIBLE IF IT WASN'T FOR UNREVOKED! Here on XDA or any other site. It would be sad if Unrevoked decided not to release the REAL FULL NAND UNLOCK/UNLOCKED BOOTLOADER cause people keep posting stolen work or schlep methods of using their tools for the non-intended purposes!
Has anyone tried this yet?
Sent from my Incredible using XDA App
SoCalMiles said:
Where would we be without Unrevoked? They don't hide stuff, they protect stuff. They're protecting exploits from being closed by HTC and phones from being bricked. What it is, is that people are greedy fux and use the phrase OPEN SOURCE/DEVELOPMENT as an excuse to post their (unrevoked's) long hard work all over the forums cause "hey now my adblock works". Its really pathetic! Unrevoked thinks of the big picture, like people being able to root their phones in the future while these other people posting their work are just actually HURTING the community! Now you're gonna post some schlep way to get NAND unlock for one boot, using their tool and then talk **** about their methods. THERE WOULD BE NO DEVELOPMENT SECTION UNDER HTC DROID INCREDIBLE IF IT WASN'T FOR UNREVOKED! Here on XDA or any other site. It would be sad if Unrevoked decided not to release the REAL FULL NAND UNLOCK/UNLOCKED BOOTLOADER cause people keep posting stolen work or schlep methods of using their tools for the non-intended purposes!
Click to expand...
Click to collapse
Umm,
If a person such as myself can figure this out.
If a person like you and myself and others all have access to unrevoked program.
This means HTC has access to these programs as well.
HTC hires people who have college degrees and know how to program and know much more about the phones then us.
I'm sure they already have disassembled their program and know what they are doing and knew what it was doing before they did so.
I want to try other things like Metamorph and make themes.
pardonmyfreedom said:
How many times have you used this trick?
Lets say 20. Well what if on the 21st try, your phone was bricked?
I'm not saying that'll happen, but clearly you didn't write the program, so you have no idea.
I wouldn't suggest anyone try this until unrevoked release a fully tested NAND unlock. There are very few reasons to have NAND unlocked at this time.
Click to expand...
Click to collapse
I will assume that they could have given us NAND unlock already. But they haven't. They must have a good reason for holding out. I for one would like to be able to use my Root Explorer instead of getting out my laptop and using that frigging command line interface. I'm not a Linux person. I was raised on the Windows GUI. My previous 2 phones ran Windows Mobile. This is my first Android. I don't like the command line interface. It may be handy for techies and developers, but not for me... So gimmie NAND unlock! I'll take my chances.
Lexus One said:
I will assume that they could have given us NAND unlock already. But they haven't. They must have a good reason for holding out. I for one would like to be able to use my Root Explorer instead of getting out my laptop and using that frigging command line interface. I'm not a Linux person. I was raised on the Windows GUI. My previous 2 phones ran Windows Mobile. This is my first Android. I don't like the command line interface. It may be handy for techies and developers, but not for me... So gimmie NAND unlock! I'll take my chances.
Click to expand...
Click to collapse
So lexus one, ur gonna try it? If so please report back. I would love to try it, but im a little uneasy about it.
And as for the op, this is a schlep method. There is a really good reason unrevoked didnt release the unlocked bootloader. I still lile your idea, but imma go with pmf and SOCALMiles on this one until ot is proven that it works
Sent from my Incredible using XDA App
SoCalMiles said:
Where would we be without Unrevoked? They don't hide stuff, they protect stuff. They're protecting exploits from being closed by HTC and phones from being bricked. What it is, is that people are greedy fux and use the phrase OPEN SOURCE/DEVELOPMENT as an excuse to post their (unrevoked's) long hard work all over the forums cause "hey now my adblock works". Its really pathetic! Unrevoked thinks of the big picture, like people being able to root their phones in the future while these other people posting their work are just actually HURTING the community! Now you're gonna post some schlep way to get NAND unlock for one boot, using their tool and then talk **** about their methods. THERE WOULD BE NO DEVELOPMENT SECTION UNDER HTC DROID INCREDIBLE IF IT WASN'T FOR UNREVOKED! Here on XDA or any other site. It would be sad if Unrevoked decided not to release the REAL FULL NAND UNLOCK/UNLOCKED BOOTLOADER cause people keep posting stolen work or schlep methods of using their tools for the non-intended purposes!
Click to expand...
Click to collapse
As much as I want the nand unlock I have to agree this thread should be closed. Unrevoked has done to much for us.
jdkoreclipse said:
So lexus one, ur gonna try it? If so please report back. I would love to try it, but im a little uneasy about it.
And as for the op, this is a schlep method. There is a really good reason unrevoked didnt release the unlocked bootloader. I still lile your idea, but imma go with pmf and SOCALMiles on this one until ot is proven that it works
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
I'm not gonna try it! You try it! Hey, let's get Mikey!
cheifkeiff said:
As much as I want the nand unlock I have to agree this thread should be closed. Unrevoked has done to much for us.
Click to expand...
Click to collapse
+1. I dont like to knock our valuable devs, but this is a schlep method that is a mockery of sorts of unrevoked. This was a good find, just not the rght thing to do to support unrevoked.
Ps. Sorry if im clogging the thread, i jabe a lot to say on the subject.
Sent from my Incredible using XDA App
i tried it, installed adfree and it worked.
jdkoreclipse said:
+1. I dont like to knock our valuable devs, but this is a schlep method that is a mockery of sorts of unrevoked. This was a good find, just not the rght thing to do to support unrevoked.
Ps. Sorry if im clogging the thread, i jabe a lot to say on the subject.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
+2 UnRevoked your doing a hell of a job, 90% of us understand why the nand unlock has not been released, I want nand but i'm not willing to try what the op has suggested. Perhaps if I were building themes I might use this method for a faster testing procedure. Yet I dont belive it should have been posted here seems alot of new poeple lurking might unplug at the incorrect moment and create issues that would spur a whole bunch of "help me!!" threads.
What UnRevoked is doing is no different than me or anyone else running company server patches in a sandbox for a few weeks before I pushed it to all the servers. Test test test test THEN release!
No doubt HTC has already seen and disected their code. Do you think your the first to figure out how UnRevoked managed to flash the custom recovery? Why has no one else posted this? hmm..
Dont kill me with flames I'm just sayin.
Just my .02 cents
I have tried Universal Androot、z4root...but faild...
Read my signature.
Manual method...
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA App
I'm not sure why people find it so hard to say 'SuperOneClick' in reply to such an easy question. It's the only one-click method still working for the N1!
As always do your research and read the wiki, but you'll want to find and learn about SuperOneClick for rooting and possibly Rom Manager, if you decide to start using custom ROMs.
If you find yourself at the stage where you are using a custom recovery do yourself a favour and do a Nandroid backup. (learn about that too if you haven't already).
Because:
1) SuperOneClick is not the only option - there is also manual method and the bootloader method.
2) You don't know what tomorrow brings. Wiki will be updated, these threads won't be. Pointing to Wiki will keep the people using updated info. This is what Wiki is for.
3) Personally, I think people asking such question should be banned for a day or two, until they learn to read before asking. It's the most basic question with answers just about anywhere, and it still pops 3 times a week.
Also, the part which people often struggle with, is the setting up the sdk.
Superoneclick and manual methods both require sdk to be set up.
Most of the instructions in the wiki are outdated in this respect (it points to threads, which don't get updated), which is why I wrote the guide in the link, and is also the reason why I pointed to it...
Sent from my Nexus One using XDA App
danger-rat said:
Superoneclick and manual methods both require sdk to be set up...Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
SOC needs nothing to be set-up. Just stick it on your pc and run it.
Advising people to root by unlocking bootloader/manual method is like telling someone to use a sledgehammer to crack a walnut. Sure it'll work but it'll be messy, possibly do collateral damage, and could be done safer/faster/easier with another tool!
The OP was clearly looking for a 1-click method, which is understandable as MOST people do prefer to take the path of least resistance.
DirkGently1 said:
SOC needs nothing to be set-up. Just stick it on your pc and run it.
Click to expand...
Click to collapse
Try it, and enjoy the results. Return to tell us the story of how you waited hours for it to connect to your phone, until your patience ran out.
Advising people to use bootloader or manual methods has a great benefit - it teaches people things about the system that they need to know when going root, and a side benefit of preventing some of the idiocy going on around. Most idiotic threads on XDA came from people that either rooted or attempted to root, while clearly not understanding a thing about the system they're dealing with.
Touche
Sent from my Nexus One using XDA App
danger-rat said:
Manual method...
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Cheers! I previously used one-click but am holding onto that guide should I ever need to do it manually
Jack_R1 said:
Try it, and enjoy the results. Return to tell us the story of how you waited hours for it to connect to your phone, until your patience ran out.
Advising people to use bootloader or manual methods has a great benefit - it teaches people things about the system that they need to know when going root, and a side benefit of preventing some of the idiocy going on around. Most idiotic threads on XDA came from people that either rooted or attempted to root, while clearly not understanding a thing about the system they're dealing with.
Click to expand...
Click to collapse
Takes under 2 minutes for me
I'm all for people doing their research, and i always advise people to do just that, including mentioning the wiki...but...
...just look at the SOC thread and the 1.3M + page views
People like 1-click methods!
SOLVED！
SuperOneClick~
many thx~
DirkGently1 said:
Takes under 2 minutes for me
I'm all for people doing their research, and i always advise people to do just that, including mentioning the wiki...but...
...just look at the SOC thread and the 1.3M + page views
People like 1-click methods!
Click to expand...
Click to collapse
You don't seem to understand. The 1-click method STILL requires Nexus drivers from the SDK to be installed - and if you don't have them installed, it won't work!
People that fail with 1-click methods, usually fail because of that. And that's what danger-rat was trying to explain.
Jack_R1 said:
You don't seem to understand. The 1-click method STILL requires Nexus drivers from the SDK to be installed - and if you don't have them installed, it won't work!
People that fail with 1-click methods, usually fail because of that. And that's what danger-rat was trying to explain.
Click to expand...
Click to collapse
Does that vary with operating system? I didn't need to install any sdk drivers on my Win7 install for SOC to work.
Come to think of it i've never had to manually install drivers on Win7 as it has always picked up on everything i've plugged into it. God bless MS
I believe Win7 will automatically install the correct drivers, yes.
Sent from my Nexus One using XDA App
Phew, thought I was losing my marbles there for a minute!
Take a chill pill
Jack_R1 said:
3) Personally, I think people asking such question should be banned for a day or two, until they learn to read before asking. It's the most basic question with answers just about anywhere, and it still pops 3 times a week.
Click to expand...
Click to collapse
You may feel right about this, but no one asked. There are better times, places, and ways to say this without risking looking like a pompous asshole. If you really want to make a difference, try sending the OP a private message so he will understand, or leave a courteous note in your post. I'm pretty sure most people aren't trying to stir up trouble when they post.
Jack_R1 said:
Advising people to use bootloader or manual methods has a great benefit - it teaches people things about the system that they need to know when going root, and a side benefit of preventing some of the idiocy going on around. Most idiotic threads on XDA came from people that either rooted or attempted to root, while clearly not understanding a thing about the system they're dealing with.
Click to expand...
Click to collapse
I'm not really sure about what causes you to impose what other people's goals on this site are. Everyone is here for various reasons, and they aren't necessarily yours.
You are seemingly acting part of bigger problems encompassing the smaller ones that irk you.
Ahhhh, the old "give the man a fish..." vs "teach him how to fish..." debate...
Sent from my Nexus One using XDA App
Hi. How I posted before un SuperOneClick but i cantar enter ti latest AR recovery menu (previously installed) because e3 default recovery os there. I dont want to lost my warranty. thanks!
Sent from my Nexus One using Tapatalk
kubanito09 said:
Hi. How I posted before un SuperOneClick but i cantar enter ti latest AR recovery menu (previously installed) because e3 default recovery os there. I dont want to lost my warranty. thanks!
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
THIS thread may be of some use to you if you haven't seen it before. The wiki is also full of helpful information.
Let us know if you have any furthur questions.
Should i Rom
Sent from my SAMSUNG-SGH-I897 using XDA App
Um...that depends. Do you want to?
If you're comfortable with flashing then I would, if not then probably no.
Sent from 234 Elm Street
should you rom?
if you have to ask....
NO.
you should read.
then decide for yourself.
and know what you are doing before you are the 4th person in 24 hours to PERMANENTLY brick thier phone.
rom? no.... not yet at least...
read yes.
TRusselo said:
should you rom?
if you have to ask....
NO.
you should read.
then decide for yourself.
and know what you are doing before you are the 4th person in 24 hours to PERMANENTLY brick thier phone.
rom? no.... not yet at least...
read yes.
Click to expand...
Click to collapse
I absolutely agree with this answer. If you are thinking of flashing a ROM, what is the reason you are thinking about doing it? If you decide to go for it, then absolutely make sure you know completely what you are doing by reading as much as you can. Research first will save grief and frustration later. Let's just say I learned that the hard way. The only time I had any issues was when I didn't follow this advice.
Good luck with whichever way you decide to go.
TRusselo said:
should you rom?
if you have to ask....
NO.
you should read.
then decide for yourself.
and know what you are doing before you are the 4th person in 24 hours to PERMANENTLY brick thier phone.
rom? no.... not yet at least...
read yes.
Click to expand...
Click to collapse
^^^THIS^^^
Damn 4 ppl in a day...wow
Sent from my GT-I9000 using XDA Premium App
Just take time to read and understand the while process before you start flashing. DO NOT try and figure out stuff as you go, as that is how stupid mistakes are made and you mess up your phone.
Check to make sure the 3 button combo for recovery and download modes are working, and just know and follow the steps laid out in the many tutorials you can find here on xda. If you can follow directions at all, your phone will soon be doing sweet ****, and you will probably become addicted to flashing and trying new things.
I am not all that knowledgeable about how stuff works, so I never try and modify stuff that hasn't been tried and tested by somebody else, and I've never run into any serious problems. I've flashed too many roms to remember, and never screwed up my phone beyond a simple fix, all thanks to a little careful reading.
Once you flash your first rom successfully, the process is simple and fun. Just make sure and read the thread for each rom you want to try carefully so that you know of all possible issues, and you shouldn't have any problems.
Sent from my 2.3.3 Cappy running Mosaic I with Talon 1.5 using XDA Premium App
Make sure you know all the worst things that can happen. Not to scare you from doing it. On the contrary, once you know what's the worst, and you know how to fix it or prevent it, you're good to go.
Like everyone here says (because it's true) READ everything. Read the WHOLE OPs and multiple pages of everything. If someone had problem with something, they probably already mentioned it somewhere in the 23482 pages (it sucks, but you rather spend some time reading than have a dead phone).
At first everything will be uncertain (first time watching the bar go across the download mode screen when flashing from Odin) and sometimes you'll feel like you've bricked your phone. Just read the threads about ACTUAL bricked phones to know what NOT to do.
Actually, what I suggest is to find a rom that you like, but more importantly has REALLY thorough documentation about how to install. Once you do it a couple of times it'll be smooth sailing from there, and you'll be able to work with any kind of rom easily (terminology and stuff becomes more familiar too).
glhf
I got an rma phone and i am not sure if i should rom
mwiz123 said:
I got an rma phone and i am not sure if i should rom
Click to expand...
Click to collapse
So you ask the same question in a different format. Tell us that you at least read some of the replies above. Right?
Talk to people that have rommed (if that's a word. If not, then Copyright bdgiese90 2011). If they know your phone well and can help if you have questions beyond what is answered in OP's, then you can make a choice from that too. But seriously. Do your reading first. Installing a ROM isn't something other people decide for you.
And one more thing. Don't ask the same question again with different wording. Read what all of these intelligent people are posting to you. Believe it or not, they ARE helpful
Sent from my robot vacuum smartphone using black magic and goat blood
You sound ambivalent and unsure. Bad combination. Step away from the phone before you hurt it.
I messed up big and accidentally deleted my os. I can get into TWRP, but I don't know what to do from here.
noohel said:
I messed up big and accidentally deleted my os. I can get into TWRP, but I don't know what to do from here.
Click to expand...
Click to collapse
move the rom, gapps, and supersu over from a computer to your phone, then flash it in twrp. put your phone into recovery, then move them into your phone.
I'm a noob to this stuff so is there any thread with a tutorial or video explaining on how I can do this?
noohel said:
I'm a noob to this stuff so is there any thread with a tutorial or video explaining on how I can do this?
Click to expand...
Click to collapse
I don't think so, as this is the very basic thing that you should learn before you ever flash anything or before you root your device.
there are several ways you can transfer files, adb push is one, or you can just transfer them over using an option in twrp.
If you can't even drag and drop a file to your phone you shouldn't be flashing roms,this is pretty simplistic and basic... I try to help people but this gets really old everyday its the same thing over and over,sorry for my rant or sounding like a total d*#k!
holeindalip said:
If you can't even drag and drop a file to your phone you shouldn't be flashing roms,this is pretty simplistic and basic... I try to help people but this gets really old everyday its the same thing over and over,sorry for my rant or sounding like a total d*#k!
Click to expand...
Click to collapse
ok, really old.. you have 500+ posts, it cant be that old to you. i have 32400+ posts, and im still willing to help everyone. you were a newb once as well, and im sure someone helped you somewhere. i know i was a newb once. oh, and im sure that youre not a dxxk! youre probably a nice guy as well
Ive been on here since 2010,I just don't post every time somebody needs something,I let others chip in. Bit you have to admit how many times do you login and see the same thing day after day.
1. He bought the phone with cm13 on it already and is a noob and doesn't know how or
2 he installed cm13 on his own but accidentally deleted the os which means he's done it before but automatically forgot how to do it again
Again sorry to op I'm being mean tonight!
holeindalip said:
Ive been on here since 2010,I just don't post every time somebody needs something,I let others chip in. Bit you have to admit how many times do you login and see the same thing day after day.
1. He bought the phone with cm13 on it already and is a noob and doesn't know how or
2 he installed cm13 on his own but accidentally deleted the os which means he's done it before but automatically forgot how to do it again
Again sorry to op I'm being mean tonight!
Click to expand...
Click to collapse
i actually used to agree with you completely, in 2013 i was fed up with the same questions over and over and over again. then something happened to me that let me see past being fed up. i guess something like seeing the light. ive been nothing but very nice with newbies since. i do see people asking questions over and over again, that should know what they are doing. it those people ill get on, and wont be nice sometime
Anyways to answer your question do as Simms said
1.boot to twrp
2. Plug device to pc
3. After downloading rom,gapps,and SuperSU drag and drop from pc to your nexus 6
4. In twrp click install and install rom,gapps,and SuperSU
5. reboot and if twrp asks to install super user select no
6. Profit!!!
I'll be blunt here.
I have no patience for people looking for a handout. If a noob comes to this forum, does their research beforehand, and then encounters a problem, I'm more than willing to help them out. They at least are trying to learn how to do things on their own.
I place great value on self-reliance, and will reward the self-reliant with as much help as I can provide, within the limits of my experience. The OP on the other hand is on their own. Unlike the self-reliant person, the OP didn't bother to do their homework before attempting to mess around with their device, and on encountering a problem that could have been solved with a simple search, hit XDA Developers for help after the fact.
An increasing number of noobs aren't even bothering to read and understand what they are doing, because they are under the illusion that rooting is somehow cool or will grant them instant street cred. Rooting, as anyone with half a brain knows, is serious business. One wrong step and your shiny new device could become a shiny new paperweight. So, if the OP is unwilling to help themselves through simple research, how will giving the answer to them teach them anything?
Strephon Alkhalikoi said:
I'll be blunt here.
I have no patience for people looking for a handout. If a noob comes to this forum, does their research beforehand, and then encounters a problem, I'm more than willing to help them out. They at least are trying to learn how to do things on their own.
I place great value on self-reliance, and will reward the self-reliant with as much help as I can provide, within the limits of my experience. The OP on the other hand is on their own. Unlike the self-reliant person, the OP didn't bother to do their homework before attempting to mess around with their device, and on encountering a problem that could have been solved with a simple search, hit XDA Developers for help after the fact.
An increasing number of noobs aren't even bothering to read and understand what they are doing, because they are under the illusion that rooting is somehow cool or will grant them instant street cred. Rooting, as anyone with half a brain knows, is serious business. One wrong step and your shiny new device could become a shiny new paperweight. So, if the OP is unwilling to help themselves through simple research, how will giving the answer to them teach them anything?
Click to expand...
Click to collapse
100% agree, thumbs up. I have said this before on here but I think an admin. Deleted it, I don't think anybody reads anything anymore they just want somebody to do it for them