All In One Toolkit By hasoon2000:
Go here and Try this tookit first, its extremely simple and Hasoon has made a lot of effort making this. This will take care of a lot of your rooting needs outlined below.
Click to expand...
Click to collapse
Basic Knowledge:
I have been getting questions regarding unlocking and rooting a lot and I keep refering people to Binary's page he has made and spend a lot of time making. In Order to root you need to the the following in THIS order:
1. Unlock bootloader (For mac and linux go to this thread its for the rezound, but is exactly the same for the amaze. For pc go here)
2. Put Custom recovery on your phone (for mac, pc and linux look below on post #2)
3. Root your phone, Either with a custom rom (in the development section), or by flashing/installing su-2.3.6.3-efgh-signed.zip, via custom recovery that you just installed in step 2. In order to learn how to flash su-2.3.6.3-efgh-signed.zip go here. For extreme newbies look at the bottom of the post here to show you easy way to get into your recovery and flash/install su-2.3.6.3-efgh-signed.zip, via taking out back battery.
All this found in thread [HOW TO] ROOT HTC RUBY / AMAZE 4G in the first sticky post in General Section, in much more detail.
NOTE: ONE CLICK ROOT TOOL DOES NOT NOT UNLOCK YOUR PHONE NOR DOES IT PUT CUSTOM RECOVERY, IT ONLY ROOTS. YOU MUST FOLLOW BASIC KNOWLEDGE ABOVE
Click to expand...
Click to collapse
Troubleshooting:
1.Common Problems: You can find more common problem questions answered here
2.Custom Recovery Problems: If have problems with step 3 (Custom Recovery) in [HOW TO] ROOT HTC RUBY / AMAZE 4G, or from the post below, go to this page.
3.WiFi and Bluetooth Problems: This is due to your kernel. I have seen multiple threads about this. Here are the ways to resolve this:
Whenever you download a rom there's a boot.img file in there. always extract the boot.img file and use xobarders kernel flasher to flash your kernel before you install your custom rom. If you are running a stock rom, download All in One Toolkit by Hasoon. Alternatively you can use the one and only custom kernel we have right now Faux's Custom kernel.
4.Touchscreen and Multitouch issues (Gaming Etc): It seems like installing a third party lockscreen widget such as Widgetlocker, Go locker, or Flyscreen, tends to interfere with the multitouch of the HTC amaze. Disable these widgets and restart your phone. Then use this program from the market to get 4 solid points touch points, If you are not getting it, uninstall the lockscreen widget altogether, and restart until you are constantly getting four touchpoints.
Click to expand...
Click to collapse
Rules and General Knowledge:
Over time we get many many questions in the General Section about things that can easily be found. I assure you if you read these in this order, you will learn a lot, and have almost no questions left.
1. Read the FAQ section: Here
2. Please Read the Bible in the development section, This is very helpful: Here
3. Look in the development section for what you need before asking for roms, stock roms, how to root, or how to unlock. (The development section is only three pages, I urge you to go through it if you want to learn how to do things and are unfamiliar with things: Here
4. Use the search feature before asking a question.
Click to expand...
Click to collapse
Camera Quality:
There have been many debates among people about camera quality, this is a guide that provides good information on camera and why the amaze has the best camera on the market
1. Aperture 101: http://inluminent.com/2005/12/14/digital-photography-101-aperture/
2. Lens size/focal length (wide viewing angle): http://www.paragon-press.com/lens/lenchart.htm
Some comparisons:
HTC Amaze: F/2.2, backside illuminated sensor, Excellent camera software, Close to zero shutterlag. 28 mm lens, very wide viewing angle (get more real estate in one picture)
Iphone 4S: F/2.4, backside illuminated sensor, Above Average camera software, Close to zero shutterlag 35 mm lens, wide viewing angle
Galaxy S II: F/2.65, NO backside illuminated sensor, Above Average camera software, Normal shutter lag, I think 28 mm lens (seems to be more like 30 or 35), very wide viwing angle.
Galaxy nexus: F/2.75, NO backside illuminated sensor, Basic ICS camera software, Zero shutterlag, 35 mm lens, wide viewing angle
The Amaze has the widest viewing angle, as it has a 28 mm lens, the lower the number the more real estate you get, look at number 2 (lens size) above. Look at how much wider of a field you get with galaxy s II and amaze 4g. Amaze has the lowest f/stop (aperture), f/2.2, meaning more light gets to the sensor. However lower f stop comes at a price, I prefer a f/2.4 on the iphone 4s but with a wide viewing angle of 28mm, no phone on the market has that right now. The higher your f-stop, the easier it will be to focus on larger subjects and objects and to keep more of the frame in focus, at the cost of a darker image. The lower f-stops will give you a blurrier background and possibly create some darkness around the corners of the frame, but a brighter overall image
compare images a when it shows you the distance: http://www.phonearena.com/reviews/i...axy-S-II-vs-Amaze-4G-camera-comparison_id2883
For Those who want to really learn how to take Great pictures with any camera here's a really good complete guide: http://www.camera.canon.com.my/archive/photography/art.htm
Click to expand...
Click to collapse
I made this thread to help you and I have spend time editing it and linking important threads that are all collections from this amaze forum. I am in no way responsible if you manage to mess up your phone computer etc. With that said these events are very unlikely to occur. I assure you by reading this thread, 99 percent of your questions will be answered and you will go from a noob to a semi pro! Unlocking and Rooting require knowledge that can be found by reading this thread; there are only a few people to answer hundreds of questions in this forum, so it will be faster for you to read this than to ask questions
Click to expand...
Click to collapse
If I have helped you please don't forget to click thanks
If you Loved this Post you can always rate it up on top right where the stars are
EASY CUSTOM RECOVERY NOOB PROOF FOR MAC, PC AND LINUX
Click to expand...
Click to collapse
1. Go to Settings > Applications > Development > Make sure USB Debugging is checked
2A. For PC. Unzip and Run Flash.bat
2B. For Mac and Linux Unzip and Run Flash.sh
Thanks to Binary: this is a modified version of a script Binary made for windows. This one is a one i modified; will work on Mac, Linux and Windows.
Although There have been no problems, please use at your own risk
Click to expand...
Click to collapse
If I have helped you please don't forget to click thanks
Haha. I know what you mean. It is pretty annoying, but people never read. When they say I think I bricked my phone, we should ask them "Did you read before you started". Some people just never listen or want to search.
seansk said:
I can't believe I just got this http://forum.xda-developers.com/showthread.php?t=1426676 5 minutes after I posted this thread... binary something needs to be done...3 threads started in the past two hours...asking dev stuff...can you sticky this...and start closing threads if the next person asks how to get a rom.
Click to expand...
Click to collapse
I'll sticky it under the condition that you keep this orderly and under control. As the OP you'll have to keep this thread on topic and friendly at all times.
I might suggest losing the CAPS in post #1. People want a friendly atmosphere to learn in and get their questions answered. By having all CAPS it loses that effect almost immediately. Lose the CAPS and I'll stick it.
hasoon2000 said:
Haha. I know what you mean. It is pretty annoying, but people never read. When they say I think I bricked my phone, we should ask them "Did you read before you started". Some people just never listen or want to search.
Click to expand...
Click to collapse
Sadly, there is nothing I can do about the members that don't want to use the search feature. I can't make them read either. That's what school is supposed to be for.
Binary100100 said:
Sadly, there is nothing I can do about the members that don't want to use the search feature. I can't make them read either. That's what school is supposed to be for.
Click to expand...
Click to collapse
Done. Edited. I hope you approve
seansk said:
Done. Edited. I hope you approve
Click to expand...
Click to collapse
Approved and stuck.
Thanks!
Binary100100 said:
Approved and stuck.
Thanks!
Click to expand...
Click to collapse
Now Lets hope we don't have to put another read this "read this" thread lolol....
seansk said:
Now Lets hope we don't have to put another read this "read this" thread lolol....
Click to expand...
Click to collapse
I say we have someone make a video since some people seem to be incapable of reading and following instructions. I'm sure if SassyBoB made a video it would attract a bit of attention.
Link my thread in. I made a FAQs page. Atleast it would help!
http://forum.xda-developers.com/showthread.php?t=1426959
hasoon2000 said:
Link my thread in. I made a FAQs page. Atleast it would help!
http://forum.xda-developers.com/showthread.php?t=1426959
Click to expand...
Click to collapse
Now make them read it.
seansk said:
I can't believe I just got this http://forum.xda-developers.com/show....php?t=1426676 5 minutes after I posted this thread... binary something needs to be done...3 threads started in the past two hours...asking dev stuff...can you sticky this...and start closing threads if the next person asks how to get a rom.
Click to expand...
Click to collapse
I've read somewhere there are 3.7 million Android devices activated on Christmas day alone. Assumed that 1% of those new device is the Amaze and that'll give us 37,000 new Amaze owner with assuming/estimately/approx. 10% wanted to root their phone ... that equal to 3,700 newbies and at least 1/2 of them will head to this forum
I wouldn't be suprise if my Mom log-in here and ask is rooting will allow her newly Amaze steamed her rices for her though.
So, get ready and be a little gentle if you could lads.
Binary said:
I say we have someone make a video since some people seem to be incapable of reading and following instructions. I'm sure if SassyBoB made a video it would attract a bit of attention.
Click to expand...
Click to collapse
LOL
antiquezip said:
I've read somewhere there are 3.7 million Android devices activated on Christmas day alone. Assumed that 1% of those new device is the Amaze and that'll give us 37,000 new Amaze owner with assuming/estimately/approx. 10% wanted to root their phone ... that equal to 3,700 newbies and at least 1/2 of them will head to this forum
I wouldn't be suprise if my Mom log-in here and ask is rooting will allow her newly Amaze steamed her rices for her though.
So, get ready and be a little gentle if you could lads.
LOL
Click to expand...
Click to collapse
I believe if you are unable to unlock and root your phone, you better not do (actually not be allowed to do) it in the first place and first spend some time learning before doing it...people just want to root for the heck of it without understanding anything and they probably will have 2000 more questions after rooting and trying to customize and flash roms.
Do you know how much I had to read before I decided to unlock and root my nexus one the first time!!! I wanted to know what it meant what I could do etc. I screwed my phone up 2 times and tried different things to fix it and was able to...that's how you learn. with all the guides provided here people should have no problem learning SO SO much... This way they can get better use of their phone...learn how to flash themes, learn what hboot, fastboot, kernel, etc all that stuff does.
Please folks I urge you to read read read...It's not like your reading a boring textbook, its cool stuff that'll make you be able to use your phone much more effectively and to your liking.
I say binary should take out the noobproof recovery zip file and let people learn how to do it in fastboot and adb, thats how i learned, but then that'll create a massive load of questions i guess. learning a little bit of dos in the process its always usefull.
seansk said:
I believe if you are unable to unlock and root your phone, you better not do (actually not be allowed to do) it in the first place and first spend some time learning before doing it...people just want to root for the heck of it without understanding anything and they probably will have 2000 more questions after rooting and trying to customize and flash roms.
Do you know how much I had to read before I decided to unlock and root my nexus one the first time!!! I wanted to know what it meant what I could do etc. I screwed my phone up 2 times and tried different things to fix it and was able to...that's how you learn. with all the guides provided here people should have no problem learning SO SO much... This way they can get better use of their phone...learn how to flash themes, learn what hboot, fastboot, kernel, etc all that stuff does.
Please folks I urge you to read read read...It's not like your reading a boring textbook, its cool stuff that'll make you be able to use your phone much more effectively and to your liking.
I say binary should take out the noobproof recovery zip file and let people learn how to do it in fastboot and adb, thats how i learned, but then that'll create a massive load of questions i guess. learning a little bit of dos in the process its always usefull.
Click to expand...
Click to collapse
We're still getting the questions and I'm still getting the private messages but not as much now. I agree with you that the people that can't root the device because they can't follow the instructions should not be allowed to do so. Here's a simple reason why. When I used to develop ports and themes (couple roms back in the G1/MT3G days) I always had to include a disclaimer that WAS the link. In other words I would say download by clicking the disclaimer below which would waive their rights to blame me should something go wrong. Why did I do that? Because people couldn't read or follow instructions which caused a quite a bit of grief for me. Funny thing was that when I began using that method people were asking me "Where can I download?" and that would prove to me that they did not read the disclaimer or the instructions for that matter. I have also learned that you have to put words in color, different sizes, use underlines and even in bold to get their attention. In fact, I'll be willing to wager that that last sentence was the first to get your attention. Which proves my point. Developers need to make things stand out without making it look tacky.
Here's an example of one of my themes with what I was talking about:
http://forum.xda-developers.com/showthread.php?p=8899943
You must add pictures, underlines, changelogs that are easy to find, read and understand. Then you need to add the disclaimer. That way you don't need to worry about getting people pissed off at you for messing up their device.
Binary100100 said:
We're still getting the questions and I'm still getting the private messages but not as much now. I agree with you that the people that can't root the device because they can't follow the instructions should not be allowed to do so. Here's a simple reason why. When I used to develop ports and themes (couple roms back in the G1/MT3G days) I always had to include a disclaimer that WAS the link. In other words I would say download by clicking the disclaimer below which would waive their rights to blame me should something go wrong. Why did I do that? Because people couldn't read or follow instructions which caused a quite a bit of grief for me. Funny thing was that when I began using that method people were asking me "Where can I download?" and that would prove to me that they did not read the disclaimer or the instructions for that matter. I have also learned that you have to put words in color, different sizes, use underlines and even in bold to get their attention. In fact, I'll be willing to wager that that last sentence was the first to get your attention. Which proves my point. Developers need to make things stand out without making it look tacky.
Here's an example of one of my themes with what I was talking about:
http://forum.xda-developers.com/showthread.php?p=8899943
You must add pictures, underlines, changelogs that are easy to find, read and understand. Then you need to add the disclaimer. That way you don't need to worry about getting people pissed off at you for messing up their device.
Click to expand...
Click to collapse
well I made some changes look much less tacky...It'll be a work in progress!!!
Binary I modified your script to work with linux and mac. I need someone to test it. I think it should work, I posted it in the second post of this thread.
seansk said:
Hope this helps
Click to expand...
Click to collapse
Would have saved me a few minutes the other day if this was posted, but I just opened the .bat files in textedit and ran them in terminal(with whatever tweaks to the commands needed). Glad it is here for future osx/linux people though.
I never did figure out why, but a few different versions of fastboot didn't work for me- one of these had a version that worked for me, the others didn't, can't remember which worked.. RecoveryInstallerForNoobs, EasyKernelFlasher, Xboarder56-All-in-One-Tool. Or maybe it was fastboot-mac that I think I found on the htcdev site..
Either way, definitely cool to see more mac/linux friendliness in the forums I don't touch my pc if at all possible..
Silentbtdeadly said:
Would have saved me a few minutes the other day if this was posted, but I just opened the .bat files in textedit and ran them in terminal(with whatever tweaks to the commands needed). Glad it is here for future osx/linux people though.
I never did figure out why, but a few different versions of fastboot didn't work for me- one of these had a version that worked for me, the others didn't, can't remember which worked.. RecoveryInstallerForNoobs, EasyKernelFlasher, Xboarder56-All-in-One-Tool. Or maybe it was fastboot-mac that I think I found on the htcdev site..
Either way, definitely cool to see more mac/linux friendliness in the forums I don't touch my pc if at all possible..
Click to expand...
Click to collapse
did you use RecoveryInstallerForNoobs version 2.0?? I just made it!
seansk said:
did you use RecoveryInstallerForNoobs version 2.0?? I just made it!
Click to expand...
Click to collapse
I don't know about 2.0, I downloaded it and some other files 2 nights ago when I got my amaze. Like I said, there were a few versions of fastboot that I tried that didn't work.. still the entire process of unlocking bootloader, flashing recovery, and flashing a rom took less than 30 minutes once I figured out that the fastboot file was the issue. It probably helps that I thought I'd have this phone a month ago, so already researched everything I would need to know.
Binary tell me if you need me to change anything, or how the posts look. Feel free to change them. After seeing what you have done before, you have a better design sense than I do I guess
Related
I wanted to contribute something to the development but I'm a dumby when it comes to code. For a living I coordinate techs and developers with end users, basically I'm a tech-speak translator. I've notice that around these parts there are a ton of questions that could be easier resolved by following some guidelines. So this guide isn't about how to root or rom specifically, it's tips to avoid common mistakes and make it easier to provide you with help if something does go wrong. Think of it like when you call your cable help line and they ask you "is it plugged in" if you checked to make sure it was plugged in before you called you'll get to a solution a lot quicker.
I ask that any devs who can add to this do because knowing what us regular users can do to make your job (unpaid job that is) easier benefits us all.
Back up
This is super important but a lot of us are in such a rush to play with the goodies that we skip it. Always always keep a current back up of your sd card on your pc/mac. You can create a folder called "mytouchbak" or whatever you want and just copy and paste all the files over there.
Also nandroid backup. You should keep at least 2 nandroid backups. If you're just now rooting make a nandroid back up before you do anything. Then once you have a good stable rom running make another nandroid back up. This way you can either return to a default build, or to your working rom build.
These things are important because usually if you screw something up it's usually quicker and easier to just start from the beginning rather than have someone try to figure out what tiny step out of the many involved you may have done wrong, then figure out how to fix it.
Try twice
This relates to "back up." If something seems broken start from the beginning and try it again. Most likely you missed a step, forgot a symbol in something you typed, or sometimes something just didn't quite go right. By rooting you are doing things that weren't meant to be done and sometimes some numbers just got crossed somewhere. Before you proclaim that things are broken just try it again. You would be suprised by the number of times things work the second time through.
Read the whole thread
We have all done it. You follow the instructions perfectly and something doesn't work so you run to the forum and immediately write a post saying "help, i can't get it to work" on page 80 of a thread when several other people experienced the same problem, already asked the question and a solution was posted on page 20. I know it's sometimes a pain to skim 80 pages of posts but those 80 pages are probably caused by other people not reading the thread before posting. A good tip for this is if there is something specific that isn't working like wi-fi tether, just open the search toolbar in your browser, type "tether" and then go to each page hitting search. That way you don't have to read every post but if anyone has mentioned anything about tethering it will point you right to it and you only have to read those posts.
Have a computer ready
This is one that most of us already do but the one time you forget things always go bad. Don't ever rely on remembering the instructions you read on your phones browser when working on rooting and romming. If you have a computer in front of you you can read the forums and follow the instructions word for word which gives you a better chance of success.
Read everything first
Before you start read everything from start to finish at least once. Sometimes devs skip steps that they assume we know and then mention them later. It's because a lot of things seem like something everyone should know, but we don't. In the same vein if you can find multiple tutorials read them all first. This will give you several view points on doing the same thing and will in general make the whole process make more sense to you and clue you in on things one tutorial may have skipped past.
The other benefit is sometimes a step is listed, and then right after it it will say something like "and don't do that until you do this." such as with our current rooting loop method. If you read all the steps first before starting you won't be caught off guard by things like this.
Asking for help
When you get stuck, you can't find any answers AFTER READING AND SEARCHING THE FORUM for your issue then definitely ask away. How you ask relates to how easily it is for someone to help you.
Avoid making general statements when possible, detail is a must. Instead of saying "I rooted, then did A2SD, then restarted" give the steps you took to root and A2SD by either referencing the method such as "I rooted as per the steps laid out in (link to instructions or name of method) or lay out the exact steps line for line as to what you did. If you assume you rooted right and what went wrong was you missed a step in the rooting process how is anyone supposed to tell you what step you missed.
Also format it to be easy to read. Development trains your mind to be very organized and structured. Basically don't format your post like this guide I'm writing, in large blocks of paragraph text. Instead put each command on a new line for instance:
"I did this
adb shell
adb push update.zip /sd
reboot into recovery....."
this makes it a lot easier to provide you with help.
Slow down, Find a good time
Don't rush through the process. That's how steps are missed, commands are mistyped and phones get bricked. I've done roots at 2am and couldn't for the life of me get it to work, I put it away and tried again in the morning and things went great. So don't mess with rooting and romming when you're exhausted, in a hurry, high, in the midst of an argument with your girlfriend, or any sort of other distractions.
That's all I have for now, I hope it helps. If anyone has anything to add please do.
great guide, most of us probably follow these general rules without really thinking about it and sometimes that is overlooked when a new guy comes in to try to do something.
tubaking182 said:
great guide, most of us probably follow these general rules without really thinking about it and sometimes that is overlooked when a new guy comes in to try to do something.
Click to expand...
Click to collapse
Thank you. I notice that happen a lot in my job where someone with no experience in the particular tech get's lost because the things we take for granted as common knowledge really aren't for someone new to the idea. Especially with the android devices becoming insanely popular theres a huge influx of new users looking at the goodies that come with root. install a custom rom or two and everything above becomes second nature.
skullkandy said:
Slow down, Find a good time
Don't rush through the process. That's how steps are missed, commands are mistyped and phones get bricked. I've done roots at 2am and couldn't for the life of me get it to work, I put it away and tried again in the morning and things went great. So don't mess with rooting and romming when you're exhausted, in a hurry, high, in the midst of an argument with your girlfriend, or any sort of other distractions.
Click to expand...
Click to collapse
So that's why I was having problems.
this tut is NOW IN SLIDE BIBLE! just send people there any chance you get with noobs, and we'll let them search
Aweome idea for a post! Thanks!
Sent from my T-Mobile myTouch 3G Slide using XDA App
Thanks for all the positive feedback guys. And especially thank you for getting this posted into the slide bible. I hope this cuts down on some of the repeat questions and makes it easier for some of the new folks to not be so overwhelmed when rooting for the first time.
@Bigshow281 : I have screwed up several rootings by being a little bit too foggy to be messing with something that requires precise typing and following instructions correctly.
I am fairly new to rooting so far I have explored app removal, have created full back ups, performed a restore, have flashed a few zips including the new 4.2 camera. Now I want to move on particularly with a view to increasing speed/smoothness etc for which I know that I will need to flash a ROM and or kernel. It is not the how that bothers me so much - lots of good advice here I have TWRP installed, have ODIN both desktop and mobile ODIN, but WHICH to try. I am currently on JB 4.1.2 stock rooted with an i9300. Through different apps I can find lots of compatible ROMS listed but almost no information about which ones are considered good and why. Clearly I want to start with one that is better, or at least as good as, my current stock but none of the listed ROMS say anything much about their features. There is a little sparse information about Kernels but not much for a person starting out to flash their first ROM. I have searched on here for any kind of comparison table, but if there is one I am either searching in the wrong forums or not wording the search well.
So I wondered if people could share their favorite ROM/Kernel and a little about what it can do or point me to a reliable online comparison.- obviously one with 4.2 would be good but even a 4.1.2 improvement would be helpful
no. read the rules
Give MiUI a go over on miui android.
Sent from my GT-I9300 using Tapatalk 2
gbswales said:
searching in the wrong forums or not wording the search well.
So I wondered if people could share their favorite ROM/Kernel and a little about what it can do or point me to a reliable online comparison.- obviously one with 4.2 would be good but even a 4.1.2 improvement would be helpful
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1935514
Please start by reading the faqs and guides first .
jje
Here is The Best ROM ever!! Must try!
Sent from my GT-I9305 using xda app-developers app
Thank you but I am puzzled
Glebun said:
no. read the rules
Click to expand...
Click to collapse
I glance through forum rules in the same way that I read terms and conditions and instruction manuals - that is that I scan them for anything that may be important and refer to them occasionally if I find I am doing something wrong. I would strongly suspect that many people do not even do this much. So having encountered a problem of apparently doing something wrong I took the trouble (once I had found them) to read fully through the rules here http://forum.xda-developers.com/announcement.php?a=81 . In all honesty I cant see how my post contravenes any rule in that, as a newbie, I am just asking for opinions and sources for what I need. I could have just googled but the last time I did that I nearly bricked my tablet, and was told that this was the place to come for help and advice. I did follow the rule to search the forums first but that didn't turn up anything useful
My instinct was to post this in the developer forum but, since this clearly states it is for experienced user/developer discussion only, I didn't.
I don't understand why it would be so wrong to have feature lists and experience comments for what is developed here. I did find some very good descriptions from Omega and for that reason will probably try one of these first but it would be nice to know how others stack up and whether, for example, there are any other 4.2 ROMs out there.
I do thank you for taking the time to read my request.
Clive
Two posts prior to yours is a link to the thread concerning why best Rom threads aren't allowed
i recommend playing with stock roms first before trying custom roms. get to know your phone first.
flash
root
debloat
apply mods
etc
etc.
I have found that now - though not in main rules!
slaphead20 said:
Two posts prior to yours is a link to the thread concerning why best Rom threads aren't allowed
Click to expand...
Click to collapse
I have to say I don't understand why, despite the explanation, because the nature of a forum is that members can answer the posts that they want to and ignore those they feel are irrelevant. I think by comparison what I really mean is a feature list - after all the main for rooting a phone (other than "because I can") is, I would think, because (a) you want more control (b) you want to get rid of bloatware (c) because you want features that your current ROM doesn't have but which could be available (d) because you want to overclock the processor - within sensible limits, or not - All of these in my experience amount to wanting a "cooler smarter device"
I do appreciate that this is a developers forum and I will in future try and pay more attention to rules here. Would it be wrong to ask if any of the experienced developers here know where else to go for some guidance about what newly issued ROMs contain, not necessarily rating them but just saying what is different to stock. I have in mind the sort of information posted by Omega in the forums here
http://forum.xda-developers.com/showthread.php?t=1663656 If each ROM creator had something similar and they were collated together in a sticky forum it would be really useful - It would be something I would be quite happy to subscribe to with a fee, with the income returned to the developers who contribute. It would be so useful to people like myself who do not have hours of time and (at least until I have gained more confidence) the nerve to keep switching ROMS
Each ROM has a changelog for each release
Just read it
thanks for that good advice
I have been reading more and can see that I can probably flash most of the things I want to my stock ROM
I actually prefer this because I do like Touch Wiz over all the other launchers I have tried
My only concern is that so far I haven't been able update a stock ROM without going through the rooting process again and re-making all the mods - should I look for stock roms that have been rooted - each time I re-root with ODIN I am back with CWM recovery rather than TWRP - I haven't read the benefits of one over the other but I know that on my phone I can't read the CWM commands on recovery screen so prefer TWRP
I am sure that people must have found ways to update to new stock versions without losing root so will keep on searching - time is the biggest enemy as I have been four hours on here already today!
Clive
gbswales said:
I have to say I don't understand why, despite the explanation, because the nature of a forum is that members can answer the posts that they want to and ignore those they feel are irrelevant.
Before the thread is locked .
But this is a developers forum not a fix your phone or make it cool forum .
Users are expected to either have a basic knowledge and if not to bother to read the FAQS and Guides .
I think by comparison what I really mean is a feature list
All listed for each rom in the thread .
-
http://forum.xda-developers.com/showthread.php?t=1663656 If each ROM creator had something similar and they were collated together in a sticky forum it would be really useful -
That has been done in the past but as we still get multiple what's best rom posts it was dropped .
Its not nerve that is required its a matter of starting where all the experinced users and devs start by reading the basics .
jje
Click to expand...
Click to collapse
cynical but at least funny
djembey said:
Here is The Best ROM ever!! Must try!
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
As it gave me a laugh I have given you thanks though posted a comment on you tube too
time is the enemy
JJEgan said:
gbswales said:
I have to say I don't understand why, despite the explanation, because the nature of a forum is that members can answer the posts that they want to and ignore those they feel are irrelevant.
Before the thread is locked .
But this is a developers forum not a fix your phone or make it cool forum .
Users are expected to either have a basic knowledge and if not to bother to read the FAQS and Guides .
I think by comparison what I really mean is a feature list
All listed for each rom in the thread .
-
http://forum.xda-developers.com/showthread.php?t=1663656 If each ROM creator had something similar and they were collated together in a sticky forum it would be really useful -
That has been done in the past but as we still get multiple what's best rom posts it was dropped .
Its not nerve that is required its a matter of starting where all the experinced users and devs start by reading the basics .
jje
Click to expand...
Click to collapse
Believe me I read about 20 posts before even rooting and spent three days building up the confidence to do it - even so my heat was in my mouth until it rebooted successfully. I think, as suggested by someone else , I will for now stick to modifying the things I want to change by flashing zips using Mobile Odin (I thought that was an app well worth paying for - really easy to use - I also like TWRP - I just hate the idea of having to re-do the root and most of these mods when stock 4.2 gets released. I have now found a few more detailed descriptions by going into the forum marked for developers only Omega's are particularly good. All these shop window type posts gathered into one place is all I think would really be needed - I just find it very difficult to search the forums because when I started searching on things like "ROM comparison" and "ROM features" I didn't see the post that has been pointed out since about why you don't do this. My foray into this has taken over four hours rather than 5-10 minutes
Click to expand...
Click to collapse
gbswales said:
JJEgan said:
Believe me I read about 20 posts before even rooting and spent three days building up the confidence to do it - even so my heat was in my mouth until it rebooted successfully. I think, as suggested by someone else , I will for now stick to modifying the things I want to change by flashing zips using Mobile Odin (I thought that was an app well worth paying for - really easy to use - I also like TWRP - I just hate the idea of having to re-do the root and most of these mods when stock 4.2 gets released. I have now found a few more detailed descriptions by going into the forum marked for developers only Omega's are particularly good. All these shop window type posts gathered into one place is all I think would really be needed - I just find it very difficult to search the forums because when I started searching on things like "ROM comparison" and "ROM features" I didn't see the post that has been pointed out since about why you don't do this. My foray into this has taken over four hours rather than 5-10 minutes
Click to expand...
Click to collapse
We all go through this, but you will get more confident.
The main thing to remember is if things go wrong, don't panic, walk away, put the kettle on, have a think about what might have gone wrong, reread instructions, check, check, check!
What you musn't do is randomly trying different things in a panic
Click to expand...
Click to collapse
slaphead20 said:
gbswales said:
We all go through this, but you will get more confident.
The main thing to remember is if things go wrong, don't panic, walk away, put the kettle on, have a think about what might have gone wrong, reread instructions, check, check, check!
What you musn't do is randomly trying different things in a panic
Click to expand...
Click to collapse
And to add a prelude to slappy's post...BACKUP! BACKUP! BACKUP! before doing anything to your phone every single time. So many arses have been saved because of this.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Please read this: http://forum.xda-developers.com/showthread.php?t=1935514
Before anyone flames me for creating this thread and then closing it, I just want to let staff know that I did indeed read the sticky threads.
All the instructions for how to root a C6806 on this site seem a bit complex with many steps and quite risky if you are not a Linux and Android phone geek who knows exactly what they are doing. It seems way too easy to make a mistake and permanently brick a phone or lose Dram keys or simply not be able to completely unroot for warranty's sake.
I used to work in the IT field over a decade ago with some training in Network Technology before I got married and I find these instructions too risky for an expensive phone that is too vital for personal and business needs to take a moderate to strong risk of damaging the phone beyond warranty. I can only imagine how someone with little to no Linux or Android experience would fare trying to follow all these steps.
I was hoping that someone could develop a program or app that could do this a lot easier. Not necessarily one click root easy as ideal as that might be but at least simplifying enough so the less than geekworthy can root this phone. Not making rooting feasible for the general public does only encourages future phone makers to keep phones locked and unrooted.
I would really like to use the 64GB SD Card for apps and I would like to use Avast Security for rooted users but there is no way I can trust myself through all the steps of flash software download, system backup, boot unlock, system version rollback, pre-flash procedures, flash, post-flash inspection and probably a few other things I missed.
Unfortunately it's a bit more complex than that.. Unless you unlock your bootloader or have root you won't be able to run the app that you want to unlock the bootloader and/or root with.
Good news is you are wrong re "easy to hardbrick" - flashing stock firmware always an option to recover the device.
At the end of the day to get the benefits of what you call "risky" you will have to take a few "risks"
Sent from my C6833 using Tapatalk
As buzzy said, there really is no risk in hard bricking the zu unless you really are inept. The steps are easy once you understand them:
1. Downgrade to 532 ftf (read my sticky)
2. Root with Bin4ry's or [NUT]'s tool (see my or lordmanhattan's threads)
3. Back up TA (see lord's thread)
4. Flash latest FTF
5. Unlock BL and flash a rootable kernel
The problem with a 'tool' is you never know what they have donr or not and how to recover.
Sent from CarbonROM on my Z-Ultra
It's already very easy to root the Ultra if you're either on .681 or .757 (latest firmware). All you have to do is to flash a kernel and then SuperSU. 2 minutes.
The real issue is what we have to do BEFORE rooting. The TA backup is a pain in the ass, and if Sony would've dropped the whole DRM thing, all we'd have to do would be to unlock the bootloader and flash a kernel.
It's not possible to make a "one click" solution that includes TA backup, so there really isn't any better way of doing it today. It's very easy once you've backed up the TA partition, and you'll only ever do it once per device.
Sent from my C6833 using Tapatalk
blueether said:
As buzzy said, there really is no risk in hard bricking the zu unless you really are inept. The steps are easy once you understand them:
1. Downgrade to 532 ftf (read my sticky)
2. Root with Bin4ry's or [NUT]'s tool (see my or lordmanhattan's threads)
3. Back up TA (see lord's thread)
4. Flash latest FTF
5. Unlock BL and flash a rootable kernel
The problem with a 'tool' is you never know what they have donr or not and how to recover.
Sent from CarbonROM on my Z-Ultra
Click to expand...
Click to collapse
Is that the order to do them in? Each step seems to be its own sticky thread.
LordManhattan said:
It's already very easy to root the Ultra if you're either on .681 or .757 (latest firmware). All you have to do is to flash a kernel and then SuperSU. 2 minutes.
The real issue is what we have to do BEFORE rooting. The TA backup is a pain in the ass, and if Sony would've dropped the whole DRM thing, all we'd have to do would be to unlock the bootloader and flash a kernel.
It's not possible to make a "one click" solution that includes TA backup, so there really isn't any better way of doing it today. It's very easy once you've backed up the TA partition, and you'll only ever do it once per device.
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
Impossible? Why? Unless I read the thread wrong awhile back, it appears that the TA backup thread had a link to a program just for TA backup. It just didn't have everything else that is relatively easy. Why can't a one click root program be built as an extension of that program?
Are the DRM keys the same or unique for every device of a specific model? My husband and I each bought a C6806 directly from Sony's Play Store the very first day they went on sale.
Do I need to flash a kernel or even unlock the bootloader if I'd like to keep the stock OS?
polargirl said:
Is that the order to do them in? Each step seems to be its own sticky thread.
Click to expand...
Click to collapse
Why would I post them out of order?
There is really only one sticky thread that is needed, Lordmanhattan's one. The one I wrote (for the first step) is also covered in LordManhattan's guide, just that if you read my thread you wont temporarily lose your imei no.
polargirl said:
Impossible? Why? Unless I read the thread wrong awhile back, it appears that the TA backup thread had a link to a program just for TA backup. It just didn't have everything else that is relatively easy. Why can't a one click root program be built as an extension of that program?
Are the DRM keys the same or unique for every device of a specific model? My husband and I each bought a C6806 directly from Sony's Play Store the very first day they went on sale.
Do I need to flash a kernel or even unlock the bootloader if I'd like to keep the stock OS?
Click to expand...
Click to collapse
No it's not impossible, but remember that all the dev work is done for free, in our spare time, and more often than not to itch a scratch the "we" have.
Yes the DRM keys are unique to each device
No you dont need to unlock the bootloader if you only want root, but it will make life alot easier in the longrun as you will then be able to flash a kernel that has recovery and is simple to install root on. As our phones get more secure you will have to run a custom kernel and recovery to have root
blueether said:
Why would I post them out of order?
There is really only one sticky thread that is needed, Lordmanhattan's one. The one I wrote (for the first step) is also covered in LordManhattan's guide, just that if you read my thread you wont temporarily lose your imei no.
No it's not impossible, but remember that all the dev work is done for free, in our spare time, and more often than not to itch a scratch the "we" have.
Yes the DRM keys are unique to each device
No you dont need to unlock the bootloader if you only want root, but it will make life alot easier in the longrun as you will then be able to flash a kernel that has recovery and is simple to install root on. As our phones get more secure you will have to run a custom kernel and recovery to have root
Click to expand...
Click to collapse
Please link me to that Lordmaahattan thread as he probably has quite a few.
I am quite happy and grateful that there are people like you guys who do this stuff even if it is just to "scratch the itch" and say "we have". I just wish some people would take the battle against the smartphone tyrants to a higher level as all. I have no right asking you guys to take it to a higher level but who else is more able and willing to do it? The need to render locking smartphones futile is a just and noble war.
Is there an Android equivalent to ghosting in Windows that copies everything on the phones' memory right down to the DRM keys or an other mirroring method? I'd feel a lot more comfortable making a clone image than just partial backups.
How can I tell if a TA backup is completely successful before I flash? I guess the Lordmanhattan thread should have info on how to relock and unroot?
polargirl said:
Please link me to that Lordmaahattan thread as he probably has quite a few.
I am quite happy and grateful that there are people like you guys who do this stuff even if it is just to "scratch the itch" and say "we have". I just wish some people would take the battle against the smartphone tyrants to a higher level as all. I have no right asking you guys to take it to a higher level but who else is more able and willing to do it? The need to render locking smartphones futile is a just and noble war.
Is there an Android equivalent to ghosting in Windows that copies everything on the phones' memory right down to the DRM keys or an other mirroring method? I'd feel a lot more comfortable making a clone image than just partial backups.
How can I tell if a TA backup is completely successful before I flash? I guess the Lordmanhattan thread should have info on how to relock and unroot?
Click to expand...
Click to collapse
The definitive thread is this one http://forum.xda-developers.com/showthread.php?t=2569904, quite complex to read, but simple when you understand it. The problem is that it caters for all, ie locked and unlocked, 4.2 to 4.4 etc
This thread http://forum.xda-developers.com/showthread.php?t=2593918 is how to first downgrade and keep the imei number, not strictly needed but might stop you from panicking when it vanishes.
I quite like the way sony do it, allowing you to unlock the bootloader from their dev site, although it does mean the loss of DRM keys.
You can back up the whole phone with dd (often called disk destroyer for how dangerous it can be), but you may need root first - never done it and I would not recommend doing it.
The TA partition is the only one that is really important to back up, and going back to 'factory' is as easy as using the same app to write the backup back then flashing a FTF
blueether said:
I quite like the way sony do it, allowing you to unlock the bootloader from their dev site, although it does mean the loss of DRM keys.
You can back up the whole phone with dd (often called disk destroyer for how dangerous it can be), but you may need root first - never done it and I would not recommend doing it.
The TA partition is the only one that is really important to back up, and going back to 'factory' is as easy as using the same app to write the backup back then flashing a FTF
Click to expand...
Click to collapse
I can't say I agree. Although Sony has been generous with the unlocking process, I find myself wondering why it was necessary to lock it in the first place. Polargirl isn't off mark, I spent half a day in frustration (and losing my DRM keys) before I managed to unlock and root. Once I did of course it was sweet, but the path there was a bit perplexing (a myriad of threads here) and quite scary (what if I brick it because I misread one of the 9 different threads?).
That being said, I came from Note II which was a cakewalk - I might be a bit spoiled :cyclops:
Edit: Not to mention, my very first post here was because a rooting thread was obsolete so I, on LordManhattan's advice got in touch with the mods to have said thread un-stickied. This forum is in fact a bit of a mess.
polargirl said:
Is that the order to do them in? Each step seems to be its own sticky thread.
Impossible? Why? Unless I read the thread wrong awhile back, it appears that the TA backup thread had a link to a program just for TA backup. It just didn't have everything else that is relatively easy. Why can't a one click root program be built as an extension of that program?
Are the DRM keys the same or unique for every device of a specific model? My husband and I each bought a C6806 directly from Sony's Play Store the very first day they went on sale.
Do I need to flash a kernel or even unlock the bootloader if I'd like to keep the stock OS?
Click to expand...
Click to collapse
Well okay then. Make a one-click solution that downgrades your device to a firmware that has the exploit that Bin4ry's root tool can root, then get a tool to backup the TA partition, while automatically granting it root access, and then unlock the bootloader without you having to enter your IMEI and unlock key, oh... and then update to the latest firmware and also automatically flash Jackie's kernel, boot into recovery, automatically flash SuperSU and reboot.
Not only would it potentially take several hours for the tool to finish, but it will never ever happen. Ever.
Sent from my C6833 using Tapatalk
Chima2 said:
I can't say I agree. Although Sony has been generous with the unlocking process, I find myself wondering why it was necessary to lock it in the first place. Polargirl isn't off mark, I spent half a day in frustration (and losing my DRM keys) before I managed to unlock and root. Once I did of course it was sweet, but the path there was a bit perplexing (a myriad of threads here) and quite scary (what if I brick it because I misread one of the 9 different threads?).
That being said, I came from Note II which was a cakewalk - I might be a bit spoiled :cyclops:
Edit: Not to mention, my very first post here was because a rooting thread was obsolete so I, on LordManhattan's advice got in touch with the mods to have said thread un-stickied. This forum is in fact a bit of a mess.
Click to expand...
Click to collapse
Thank you for posting that you agree with me and for also seeing the problem: The instructions are indeed complex and chaotically spread out over nine different threads making it easy to miss a step.
LordManhattan said:
Well okay then. Make a one-click solution that downgrades your device to a firmware that has the exploit that Bin4ry's root tool can root, then get a tool to backup the TA partition, while automatically granting it root access, and then unlock the bootloader without you having to enter your IMEI and unlock key, oh... and then update to the latest firmware and also automatically flash Jackie's kernel, boot into recovery, automatically flash SuperSU and reboot.
Not only would it potentially take several hours for the tool to finish, but it will never ever happen. Ever.
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
It doesn't have to be all (one click root) or nothing. Even partial simplification would help. Anything better than the several different steps over nine different threads that Chima2 was referring to would help. 3 or even 4 steps in one thread is better than the "solution" currently available.
polargirl said:
Thank you for posting that you agree with me and for also seeing the problem: The instructions are indeed complex and chaotically spread out over nine different threads making it easy to miss a step.
It doesn't have to be all (one click root) or nothing. Even partial simplification would help. Anything better than the several different steps over nine different threads that Chima2 was referring to would help. 3 or even 4 steps in one thread is better than the "solution" currently available.
Click to expand...
Click to collapse
Buy a ZTE if you want hard
Why should I or Lordmanhattan (or anyone) rewrite what has already been written. I, at least, have written the steps out more times than I care to remember. The process is not that hard, and the steps are well documented in well written english
blueether said:
Buy a ZTE if you want hard
Why should I or Lordmanhattan (or anyone) rewrite what has already been written. I, at least, have written the steps out more times than I care to remember. The process is not that hard, and the steps are well documented in well written english
Click to expand...
Click to collapse
Why? Because they aren't well written. They appear scattered and chaotic to everyone who isn't familiar with this site. Chima2 and I were just trying to give feedback is all. If more people just browsing for rooting solutions were to signup and post, they would probably agree as well. They just aren't here to give you even more feedback.
polargirl said:
Why? Because they aren't well written. They appear scattered and chaotic to everyone who isn't familiar with this site. Chima2 and I were just trying to give feedback is all. If more people just browsing for rooting solutions were to signup and post, they would probably agree as well. They just aren't here to give you even more feedback.
Click to expand...
Click to collapse
It took me about a week of reading in my spare time to get my bearings and feel confident that I could start to modify my phone. That is a small amount of effort to put forth for a device that I plan to have for at least the next year. Yes it was a little confusing but I managed and am certainly not gifted when it comes to intelligence. I feel that any average person that sets their mind to it can succeed, and any specific questions will generally be answered if possible.
adfurgerson said:
It took me about a week of reading in my spare time to get my bearings and feel confident that I could start to modify my phone. That is a small amount of effort to put forth for a device that I plan to have for at least the next year. Yes it was a little confusing but I managed and am certainly not gifted when it comes to intelligence. I feel that any average person that sets their mind to it can succeed, and any specific questions will generally be answered if possible.
Click to expand...
Click to collapse
Enough said! It might be worth it to you but probably not to most people.
polargirl said:
Enough said! It might be worth it to you but probably not to most people.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=2031989&postcount=45
polargirl said:
Enough said! It might be worth it to you but probably not to most people.
Click to expand...
Click to collapse
If a week of reading is to much for some then that is good, they shouldn't root their phones.
When people have really 'simple' ways of doing things they tend to skip steps and blame people for it. When something seems hard and daunting they read carefully and completely before starting, then read step by step as they go.
Could the 9 stickies be updated to 1 thread with all information? Why yes they could, and if it is important to you that it be done the best solution would be to write the new thread yourself. It would be a great way to give back to the community. If you notice something you find wrong, and its in your power to fix it, then do so.
Sent from my C6806_GPe using Tapatalk
_Dennis_ said:
If a week of reading is to much for some then that is good, they shouldn't root their phones.
When people have really 'simple' ways of doing things they tend to skip steps and blame people for it. When something seems hard and daunting they read carefully and completely before starting, then read step by step as they go.
Could the 9 stickies be updated to 1 thread with all information? Why yes they could, and if it is important to you that it be done the best solution would be to write the new thread yourself. It would be a great way to give back to the community. If you notice something you find wrong, and its in your power to fix it, then do so.
Sent from my C6806_GPe using Tapatalk
Click to expand...
Click to collapse
That is quite the cynical statement you posted and apparently contrary to even the spirit of this site let alone development and hacking in general. A better good for society is rending the need to root futile should be the goal and easily within reach of this site's members.
Another newbie, zxc1251, has indeed did just that and I have been helping that member with instruction simplification.
http://forum.xda-developers.com/showthread.php?t=2769782
The only problem with that is newbies tend to be quite limited in their tech knowledge thus limited in their usefulness when it comes to simplifying instructions for the tech ignorant and semi-ignorant public but I guess some relatively tech ignorant people need to start this if a revolution against unrooted, jailed or otherwise restricted access phones is to happen.
I am trying my best with the knowledge and tools that I have to get this going.
polargirl said:
That is quite the cynical statement you posted and apparently contrary to even the spirit of this site let alone development and hacking in general. A better good for society is rending the need to root futile should be the goal and easily within reach of this site's members.
Another newbie, zxc1251, has indeed did just that and I have been helping that member with instruction simplification.
http://forum.xda-developers.com/showthread.php?t=2769782
The only problem with that is newbies tend to be quite limited in their tech knowledge thus limited in their usefulness when it comes to simplifying instructions for the tech ignorant and semi-ignorant public but I guess some relatively tech ignorant people need to start this if a revolution against unrooted, jailed or otherwise restricted access phones is to happen.
I am trying my best with the knowledge and tools that I have to get this going.
Click to expand...
Click to collapse
The reason I had the 'do it yourself' attitude is all the information to make a new thread is there, just needed presentation, something tech geeks aren't well known for.
There should always be a need to root. Average use case for a phone, having security is important since you store a lot of sensitive information. If phones came rooted or came so rooting was extremely easy imagine how many people would loose their bank account info or their contact info to the not so nice side of the Internet.
Edit:
Let me use this analogy. If you wanted to change the transmission in you car would you
A) search the internet for 15 minutes and the open your hood and start disconnecting things or
B) Spend at least a few hours looking at the specifics for your car (if you've change a few transmissions before) or as long as it takes for you to feel comfortable you won't destroy your car?
If you wanted Linux on your laptop would to research the drivers, installation procedures, and distros first or just download the first one and hope you know how to install it?
All I'm saying in researching is not a bad thing, if more people did it, less would brick their phones.
Sent from my C6806_GPe using Tapatalk
_Dennis_ said:
The reason I had the 'do it yourself' attitude is all the information to make a new thread is there, just needed presentation, something tech geeks aren't well known for.
There should always be a need to root. Average use case for a phone, having security is important since you store a lot of sensitive information. If phones came rooted or came so rooting was extremely easy imagine how many people would loose their bank account info or their contact info to the not so nice side of the Internet.
Edit:
Let me use this analogy. If you wanted to change the transmission in you car would you
A) search the internet for 15 minutes and the open your hood and start disconnecting things or
B) Spend at least a few hours looking at the specifics for your car (if you've change a few transmissions before) or as long as it takes for you to feel comfortable you won't destroy your car?
If you wanted Linux on your laptop would to research the drivers, installation procedures, and distros first or just download the first one and hope you know how to install it?
All I'm saying in researching is not a bad thing, if more people did it, less would brick their phones.
Sent from my C6806_GPe using Tapatalk
Click to expand...
Click to collapse
PCs that ship with Windows serve the tech ignorant public just fine without restricting access for a common user. Developers is a whole different story when it comes to Windows but that is going off-topic.
I realize most geeks aren't comfortable with marketing and presentation issues with people like Erica Griffen (aka: Angel of Tech) being a huge exception. I don't have anywhere near her level of tech knowledge or even most members on this site but I am willing to help or even take over if needed. I just can't be of much help shortening process or making it more comfortable for the public but at least I haven't been totally useless.
Any help in shortening process or partially automating things wherever and whenever geeks can feel comfortable enough is not only appreciated by me but will be by the public as well.
Sooo, Ill start off by saying that I've unlocked, hacked, rooted, jailbroke pretty much every phone since it became available over the years. Im a careless tinkerer and have always stumbled across well written how to's to do everything I've need in forums like this and have great luck.
Well awhile ago, shortly after I got my AT&T M8, I decided to try and turn it into Google Play Edition. Somewhere along the way while in the process of doing S-OFF, something went wrong. I kept getting errors and couldn't get anything to flash. So I gave up and got the LG G3 and put the M8 aside for a bit. Well now I want to use it again, and along the way of "tinkering", I've managed to wipe TWRP, relocked the bootloader, have no OS and still S-OFF. I can boot into recovery or boot to the HTC screen so its not completely gone yet from what Ive researched.
Would anyone be willing to help me out in getting this thing back to stock Sense or point me in the right direction? I want it completely stock, without root or custom recovery. I'd rather a good step by step, if someone would be willing. I can't seem to piece together all of the information i need to do this myself. Thanks!
Have you tried this. http://forum.xda-developers.com/showthread.php?p=55094112
StupidN00b said:
Im a careless tinkerer and have always stumbled across well written how to's to do everything I've need in forums like this and have great luck.
Click to expand...
Click to collapse
Just RUU as suggested in the previous response.
I suggest leaving your phones stock, unless you are willing to put in the time to read, research, and obtain some real knowledge.
Step-by-step guides and toolkits are dangerous things. As you see, they just get you into trouble without giving you the knowledge or tools to get out of that jam.
I'm surprised you've modded as many phones as you say, and haven't gotten any real knowledge to this point. Either you are very humble; or your story is a testament to the fact that such step-by-step guides shouldn't be posted in the first place.
redpoint73 said:
Just RUU as suggested in the previous response.
I suggest leaving your phones stock, unless you are willing to put in the time to read, research, and obtain some real knowledge.
Step-by-step guides and toolkits are dangerous things. As you see, they just get you into trouble without giving you the knowledge or tools to get out of that jam.
I'm surprised you've modded as many phones as you say, and haven't gotten any real knowledge to this point. Either you are very humble; or your story is a testament to the fact that such step-by-step guides shouldn't be posted in the first place.
Click to expand...
Click to collapse
Thank you for your response but unfortunately I find it extremely arrogant and asinine. The fact is that I have put in a lot of time and knowledge to understand what I am doing. I may not have a conventional degree in coding as you might but I am able to successfully mod my phones by browsing forums like this where you can find an abundance of knowledge, especially step-by-step guides, as you are so against. If you are so against step by step guides then maybe you can be the voice about banning them from this forum. Do you see how I am a new member? I am one of the few that actually search the forums instead of posting another thread asking the same questions. Ive used tools and information from this site for a very long time without having to post one single thing until a few days ago. And this is the response I get? I was even humble enough in my screen name to call myself stupid because, with this specific issue, I knew it had to be something stupid that i was missing. You shouldn't tell people that step by step guides are dangerous things. All it takes is some balls and some command lines and you can accomplish many things. Have I messed up my phones and others before? Yes, but i had never run into a situation I haven't been able to get myself out of. To me, tinkering around, as a hobby, is fun. Like now, as I watch Sunday NFL Countdown, I am about to dust off my Nexus 5 and flash Lollipop on it. Guess what I am going to use? A STEP BY STEP GUIDE!!!! If I mess it up, then Im sure I wouldn't be the first to do so and Im sure Ill find a solution on great forums like this. Besides, my rooted/unlocked OnePlus One is my main phone. I wanted to play around with the M8 again to see if I would miss the smaller screen but I don't. So, thank you for just repeating the first response then proceeding to insult me because you think i don't have the skills needed to mod my devices. I will continue to do so however I please, just as many others will. Either contribute to threads or ignore them. No need for the insults. You've also insulted many other members who have posted tools and step by step guides on this specific site.
nuwayman said:
Have you tried this. http://forum.xda-developers.com/showthread.php?p=55094112
Click to expand...
Click to collapse
I actually did RUU but it ended up that I had a corrupt RUU file. I redownloaded it and put it on the MicroSD card and it worked like a charm. Thank you for your quick response.
StupidN00b said:
Thank you for your response but unfortunately I find it extremely arrogant and asinine.
So, thank you for just repeating the first response then proceeding to insult me
Click to expand...
Click to collapse
Quite frankly, incorrect on both points. You don't understand what an insult is, and there is nothing insulting in my post. If you read my post carefully, you will see there is no actual personal attack or insults.
redpoint73 said:
Just RUU as suggested in the previous response.
Click to expand...
Click to collapse
Contrary to what you suggest, backing up the previous suggestion is added value; as it adds credibility and consensus to the previous solution.
redpoint73 said:
I suggest leaving your phones stock, unless you are willing to put in the time to read, research, and obtain some real knowledge.
Click to expand...
Click to collapse
Its just a suggestion, and note that its conditional. Therefore, if you meet the latter part of the statement, the first part doesn't apply to you.
redpoint73 said:
Step-by-step guides and toolkits are dangerous things. As you see, they just get you into trouble without giving you the knowledge or tools to get out of that jam.
Click to expand...
Click to collapse
I stand by this statement. I've seen dozens dozens of instances where such tools just arm people with enough "knowledge" to get them into trouble, and don't equip them with any tools to get them out. Its then left to folks like me to even start to get these folks on the right track.
I'll step back a bit from my statement that these tools "shouldn't be posted in the first place". I'll agree that step-by-step guides and toolkits might be useful if combined with the proper research, learning and understanding. But in and of themselves, they can easily lead newcomers astray.
redpoint73 said:
I'm surprised you've modded as many phones as you say, and haven't gotten any real knowledge to this point. Either you are very humble; or your story is a testament to the fact that such step-by-step guides shouldn't be posted in the first place.
Click to expand...
Click to collapse
I already gave you the benefit of the doubt here, but you chose to react defensively and in my opinion, unreasonably.
In any case, as far as your knowledge and background, we can only go by what you've stated; and you clearly stated yourself as a "careless tinkerer" and "stumbled" upon solutions. Now in your later post you say "I have put in a lot of time and knowledge to understand what I am doing". So if you provide conflicting information as to your background, nobody can be blamed for making an incorrect assumption regarding your knowledge.
This will be a launching pad for tips and recommendations for members negotiating long threads and reading pertinent information. I read many posts with members stating that the thread is just too long to read. Then using that as an excuse for not reading at all. Please add your ideas and methods for reading.
The first thing I do when looking at a new thread is read the OP. I always check dates and also the date of the latest iteration of the ROM, kernel, etc. after reading what the author wrote about their thread I'll jump to the end of the thread and read backwards to the date of the latest release. This gets me up to date with the latest build and any issues.
Then I'll decide if I want to flash this on my very expensive device.
Like I said...
Please add on your tips!
Thanks!
RayMcGrath said:
This will be a launching pad for tips and recommendations for members negotiating long threads and reading pertinent information. Please add your ideas and methods for reading.
The first thing I do when looking at a new thread is read the OP. I always check dates and also the date of the latest iteration of the ROM, kernel, etc. after reading what the author wrote about their thread I'll jump to the end of the thread and read backwards to the date of the latest release. This gets me up to date with the latest build and any issues.
Then I'll decide if I want to flash this on my very expensive device.
Like I said...
Please add on your tips!
Thanks!
Click to expand...
Click to collapse
Hi...
The way you use to read a thread pretty much summarize the way I do it myself. I go a step further by searching within the said thread with some key words such as:
Problem, issue, brick, bricked, bootloop, etc...
I may sound paranoid, but I often browse the forum late at night and I could miss an important post due to being tired.
Cheers...
Great idea Ray. Teach by teaching, not by beating a person over the head lol
I go to the OP also and if I am interested in flashing, go back a month or two and read posts to see if things are stable or not. I also follow a bunch of Roms that I don't intent to flash or, have flashed before - just to see what kind of problems have arisen and how they were dealt with. It's a great way to pass a ride on the train or other idle time. I do think that there are many from around the world here and language might be a factor effecting their ability to read and/or search. Either way, I love this XDA, a valued tool! Too bad I came along so late in the game.
Bobbaloo said:
Great idea Ray. Teach by teaching, not by beating a person over the head lol
I go to the OP also and if I am interested in flashing, go back a month or two and read posts to see if things are stable or not. I also follow a bunch of Roms that I don't intent to flash or, have flashed before - just to see what kind of problems have arisen and how they were dealt with. It's a great way to pass a ride on the train or other idle time. I do think that there are many from around the world here and language might be a factor effecting their ability to read and/or search. Either way, I love this XDA, a valued tool! Too bad I came along so late in the game.
Click to expand...
Click to collapse
Great to have you. You're a big help to many folk.
5.1 said:
Hi...
The way you use to read a thread pretty much summarize the way I do it myself. I go a step further by searching within the said thread with some key words such as:
Problem, issue, brick, bricked, bootloop, etc...
I may sound paranoid, but I often browse the forum late at night and I could miss an important post due to being tired.
Cheers...
Click to expand...
Click to collapse
You're right!
Performing a search can be an art form. Using the just right keyword to be successful takes some practice. It is so important to try many paths and exhaust all possibilities before posting your question in the threads. And then phrasing your question with all your information is important as well.
RayMcGrath said:
You're right!
Performing a search can be an art form. Using the just right keyword to be successful takes some practice. It is so important to try many paths and exhaust all possibilities before posting your question in the threads. And then phrasing your question with all your information is important as well.
Click to expand...
Click to collapse
Well, since my first modded android phone in 2008, i have never felt the need of asking anything. Most likely because all issues I encountered were already covered. Either by developers or people answering issues reported by previous users having the same problems. And maybe because I like to get things done by myself. (Which I achieve 1% of the time ).
I check XDA almost every day since. I must say that the "reading thing" may sound challenging for some people. You'll ask me why?
What follows is about novice users for the most part who don't know about/how to use the search function. Try reading a thread where 100 users come each and every day writing the same thing about the same problem over and over. And over again...
Trying to find the relevant posts in-between all this mess is sometimes quite discouraging.
I'm lucky to have affinity with English and of course it's a lot easier to read and find infos when I need them. Google translate became really nice with time. Yet i find myself using it, since English is not my native language and I learned it the hard way. Sometimes it's sad to see people not using such a powerful tool.
People, please use the search function! Take some time to read. If you don't get it, use an online translator. :good:
PS: Hopefully I didn't derail too much from the OP with this post... I'll delete it if needed.
5.1 said:
Well, since my first modded android phone in 2008, i have never felt the need of asking anything. Most likely because all issues I encountered were already covered. Either by developers or people answering issues reported by previous users having the same problems. And maybe because I like to get things done by myself. (Which I achieve 1% of the time ).
I check XDA almost every day since. I must say that the "reading thing" may sound challenging for some people. You'll ask me why?
What follows is about novice users for the most part who don't know about/how to use the search function. Try reading a thread where 100 users come each and every day writing the same thing about the same problem over and over. And over again...
Trying to find the relevant posts in-between all this mess is sometimes quite discouraging.
I'm lucky to have affinity with English and of course it's a lot easier to read and find infos when I need them. Google translate became really nice with time. Yet i find myself using it, since English is not my native language and I learned it the hard way. Sometimes it's sad to see people not using such a powerful tool.
People, please use the search function! Take some time to read. If you don't get it, use an online translator. :good:
PS: Hopefully I didn't derail too much from the OP with this post... I'll delete it if needed.
Click to expand...
Click to collapse
From the beginning, searching for the answer - did someone else have the same situation and fix it(?) - THIS always seemed easier and more gratifying than waiting for someone to answer me on a thread
Actually, I was flashing macks ROM, then CM on my note 2 and I didn't even KNOW XDA existed. I was so grateful when I found it. Especially when I got this phone. With Google ai, now it seems so much easier to do a quick search on the web
Bobbaloo said:
From the beginning, searching for the answer - did someone else have the same situation and fix it(?) - THIS always seemed easier and more gratifying than waiting for someone to answer me on a thread
Click to expand...
Click to collapse
Yeah I know how you feel! At least for me having no real technical knowledge, I'm always glad to find the solutions by myself. Since it's around and just needs a search it's even faster than waiting for an answer. Also, since I only need to search when my phone is broken, I simply can't wait for someone to answer. Imagine no one replied during two days...
Bobbaloo said:
Actually, I was flashing macks ROM, then CM on my note 2 and I didn't even KNOW XDA existed. I was so grateful when I found it. Especially when I got this phone. With Google ai, now it seems so much easier to do a quick search on the web
Click to expand...
Click to collapse
This is the first place I found when I started to flash my HTC vision back in 2008. I started reading guides and development and was like: WTF these guys are cracking bootloader, carrier unlocking, etc... And all can be found so easily... :good: