Database Develop

[Q] How to update my phone's firmware?

Hi there guys. As you probably noticed,i'm new here,so pardon me if my question sounds noobish at the time,but I promise I'll learn from you guys! Thanks!
So,the question's simple. How do I update my phone's firmware? Don't wanna brick or possibly damage my phone here,as I just bought a couple of days ago. So,is there any risk to update the phone's firmware? Thanks bros!

Have you use search features before asking this question?
http://forum.xda-developers.com/showthread.php?t=1111771

Yeah,saw that already,but it seems to convoluted for me. I need a one-to-one kinda reply. Honestly,I didn't understand anything that was written on that page. So,could please someone clarify it in a more simple,noobish,way?
Thanks bro!

pdf guides are included in the kit. just follow them

either you can use KDZ or R&D for the official
or flash any custom ROM with CWM
(the tutor is already out there)
and the risk ? bootloop or brick maybe

Thanks bros! And another thing,what are custom ROMs? I keep hearing about it like Cyanogen? What's the upside for using it?

Laier94 said:
Thanks bros! And another thing,what are custom ROMs? I keep hearing about it like Cyanogen? What's the upside for using it?
Click to expand...
Click to collapse
Custom roms in simple terms are unofficial versions of the o/s modified or "cooked" by people who want to add or remove certain features or performance tweaks. The upside is you can find a ROM that suits your usage and aesthetic preferences. For more info read through some ROM threads and compare their features.
However there is always a chance something could go wrong even if you know what you are doing. So my advice would be to read and re read the instructions from rooting to flashing radios to flashing roms and look up the termanology until you think you understand and then read it all again. There are some good guides around that can givevyou the basics.
Otherwise you can wait until your carrier releases a official update.
Sent from my HTC EVO 3D X515m using xda premium

Thanks for clarifying bros!
And another thing,I just saw this vid at Youtube.
It's called "How To Install CyanogenMod 7 On Your Android Device"
I can't post the link here because im still new,haha!
Is it really that easy to install Cyanogenmod on your phone? But your phone have to be rooted first,right?
I saw the list with the firmware from various countries,but not mine,Malaysia. How do I solve this? I'm still suck with V10-a,which i think is the oldest firmware for OB.
Also,what are these baseband,kernel and build number thingies? Anything important? Thanks! Really starting to get interested in these things!

I think the following is related to malayians so you have to use an indonesian firmware :
http://csmg.lgmobile.com:9002/csmg/b2c/client/tool_mode_country_check.jsp?model=LGP970&country=MY
- you can flash firmwares anytime whatever the situation
- to flash a ROM (cyanogen, nova...) you need the custom recovery mod called ClockworkMod alias CWM (available on the market via ROM Manager app, or my kit)
- and for CWM, root access is needed
once phone is rooted and CWM installed, phone potential is extended to the infinite. you can then install a lot of useful apps of more and customize your phone.
I think the general goal of all of that, is to optimize and extend possibilities as far as possible and then you'll be able to say that you "truly own" your phone

Thanks for clearing that up bro. BTW,would you recommend me using Gingerbreak to root my phone? Since i'm using an older firmware,it should be ok,right?

no problem, blackjack should do it too. do as your feeling

Ilko said:
no problem, blackjack should do it too. do as your feeling
Click to expand...
Click to collapse
Thanks bro! Anyway,anything else I should know and do before I root my phone? Like should I do a factory reset,battery level 100% or something?

2 steps : root, flash recovery.
know that you'll have to use an app to boot into recovery (ROM manager, anreboot, ezboot...) take a look at my thread for more infos

Ilko said:
2 steps : root, flash recovery.
know that you'll have to use an app to boot into recovery (ROM manager, anreboot, ezboot...) take a look at my thread for more infos
Click to expand...
Click to collapse
Great! Cool bro,thanks! And sorry for the stupid question,but what are KDZs?

firmware files are in .kdz format

Ilko said:
firmware files are in .kdz format
Click to expand...
Click to collapse
Ouh,wow,did that felt stupid,haha. So what you're saying is,after rooting my phone,I should get to installing ClockWorkMod Recovery,am I right? And the only way to install it is using the computer,connect it with the phone,and execute the UPK that you have provided in your download link. After that,I use the app,EzBoot,to boot into recovery mode,is this correct?
After that,what will I do in the recovery mode? Thankies again!

all right. as I said earlier, the recovery mode extends phone potential in an easy way. many ROMs and mods must be did via recovery. in fact, CWM helps you flashing files, roms, doing backups/restorations and more. jump the step and see by yourself.
don't forget to backup before anything

Ilko said:
all right. as I said earlier, the recovery mode extends phone potential in an easy way. many ROMs and mods must be did via recovery. in fact, CWM helps you flashing files, roms, doing backups/restorations and more. jump the step and see by yourself.
don't forget to backup before anything
Click to expand...
Click to collapse
By backing up,you mean backing up contacts and internal memory stuffs,right?
All right! Will root my phone as soon as my charge hits 100%! Using gingerbreak! Is the root reverse-able? I mean,can I unroot my phone once I root it?

you don't need 100% battery as long phone is plugged. for now, blackjack doesn't have a reverse process. but gingerbreak, yes, considering the fact you stay on v10a/b. you may try with the new superoneclick. the most radical method is still flashing a firmware (so you'll lose all stuffs)
and yes, backup any saveable thing. although CWM saves all datas, more safety is more safe

Ilko said:
you don't need 100% battery as long phone is plugged. for now, blackjack doesn't have a reverse process. but gingerbreak, yes, considering the fact you stay on v10a/b. you may try with the new superoneclick. the most radical method is still flashing a firmware (so you'll lose all stuffs)
and yes, backup any saveable thing. although CWM saves all datas, more safety is more safe
Click to expand...
Click to collapse
Sorry bro,can't quite understand you here. Flashing firmware? For what? I'm just gonna root my phone right? No need to flash,right?

[Rum Float] First flash ever, a bit nervous

I'd like to flash my Vivid with the new Rum Float ROM and from what I gather; now that a RUU is available it should be fairly easy. I.bought the phone last Thursday and haven't had a chance to grab a SD card. I just want to make sure that I fully understand the process involved. I've read a number of posts here at XDA and elsewhere but I still have a few questions to make sure my knowledge is solid and I don't end up with an HTC paperweight! A) Will the Android market will have a record of what I have already dl'd so I can dl it again? B) Is using the RUU executable fairly simple? Should I do the BL UL before I restore?(I would like root, so I'm assuming that this is one of the first steps!) C) Is it a simple follow the instructions sort of thing with the RUU? D) Will "frigid's" "supertool" method to get root work in this instance or do I need to use CWM? E) I'm using an AT&T Vivid could somebody give me a simple step by step(not in detail, but if you could that would be great!) Such as "1- Do BL UL, 2- Run supertool for root, 3 - Run RUU, etc, etc, etc
Also there appears to be a sense and a NONSense version of the ROM, are they both included in the RUU exe file? And for the NONSense version will there be any difference in stability, performance, you acceleration, etc?
Thanks for any info in advanced!
-MeeGz-

MeeGz said:
I'd like to flash my Vivid with the new Rum Float ROM and from what I gather; now that a RUU is available it should be fairly easy. I.bought the phone last Thursday and haven't had a chance to grab a SD card. I just want to make sure that I fully understand the process involved. I've read a number of posts here at XDA and elsewhere but I still have a few questions to make sure my knowledge is solid and I don't end up with an HTC paperweight! A) Will the Android market will have a record of what I have already dl'd so I can dl it again? B) Is using the RUU executable fairly simple? Should I do the BL UL before I restore?(I would like root, so I'm assuming that this is one of the first steps!) C) Is it a simple follow the instructions sort of thing with the RUU? D) Will "frigid's" "supertool" method to get root work in this instance or do I need to use CWM? E) I'm using an AT&T Vivid could somebody give me a simple step by step(not in detail, but if you could that would be great!) Such as "1- Do BL UL, 2- Run supertool for root, 3 - Run RUU, etc, etc, etc
Also there appears to be a sense and a NONSense version of the ROM, are they both included in the RUU exe file? And for the NONSense version will there be any difference in stability, performance, you acceleration, etc?
Thanks for any info in advanced!
-MeeGz-
Click to expand...
Click to collapse
The RUU DOES NOT CONTAIN MY ROM. It is an official tool used by HTC for upgrading and returning to stock.
Android market will keep tabs on purchased apps. It will not keep track of free apps.
You need an sdcard to keep safe.
The RUU is easy to run. Its just an exe. Follow the on-screen prompts.
I don't know what you are trying to restore but it would appear you have your terminology and methods all mixed up.
RUU will get you a stock ics. And it will wipe your apps and settings. It will act like a phone you just pulled out of the box with ics.
In order to run rum float (or any aftermarket rom) you need to unlock your bootloader. Rooting has nothing to do with it. Unlock bl then flash recovery on then flash rom and kernel.
Your steps as you perceive them are slightly off. I don't recommend you do anything to your phone right now.

After you complete the RUU you'd have to go to htc.dev and unlock your bootloader. After you can fastboot flash a recovery and CWM with root. After that's complete you can flash a rom of your choice. I'd get familiar with using fastboot commands in ADB (command prompt). I guess you can use the supertool to root but it isn't necessary really a matter of preference. Check out the superguide. Maybe PG or someone can update it with specific steps if you are using the RUU but the process is the same. It starts with the unlocking the bootloader. Definitely pick up an SD card!

Thanks for the quick replies and the clarification. I think I get it now, I would do the following to get to a rooted custom ICS Rom: Unlock the boot loader, root and run titanium backup to save my apps(using an ad card), run the RUU and get to stock HTC ics, copy ROM to sd card, re-root, download and run CWM, root again and restore apps with titanium backup, enjoy!
The only things that may be a bit off in that process is running the RUU as I don't need that to just flash a custom ROM, assuming said ROM includes the ICS kernel. If did have to use the RUU would I have to re-root to run cwm? Also the actual ROM itself is installed from HBoot, correct?
Sorry if these sound like dumb questions, I'm just new at this. I really appreciate the replies. I'm sure I will pick this up fairly quickly as I have years of linux & OS X command line experience and am well versed with c. It's just kind of information overload on this board as there is such a wealth and variety of info here!
Thanks again,
-MeeGz-

So you can run the ruu.exe even if you are rooted, unlocked bootloader, on att stock? Or do you have have to relock bootloader to proceed with the ruu?
Sent from my HTC PH39100 using XDA

RUU is for stock roms IIRC. If you are rooted and already unlocked I'd use the original method PG and Thecubed created.

back on my computer for a little better explanation.
the RUU or the methods that thecubed and i have laid out will get you the necessary HBOOT/RADIO/etc that you will need to flash a custom ICS rom
either method will get you the same thing....an updated HBOOT and ICS
if you run the bootloader unlock tool from htcdev, YOU WILL LOSE ALL YOUR SETTINGS! it will wipe the device like its brand new......do NOT include this in your dreams of getting backups prior to flashing a custom rom....
please just read through the posts and understand what is going on.
in order for ICS to happen on your vivid you need the new HBOOT, Radio, and various other components that the RUU/PH39IMG contain
there are 3 different roads you can follow to get there, the EASIEST being just run the RUU (WHICH WILL ALSO WIPE SETTINGS!), afterwards, reboot to bootloader, unlock bootloader, reboot to fastboot, fastboot flash the boot.img and the recovery.img of your choice on (limited on boot.img's at the moment, better use the one from the rom), reboot to recovery and flash the rom
the other methods imply you understand somewhat how the process works.
relock bootloader (if unlocked), run PH39IMG install, unlock bootloader, fastboot flash recovery and boot.img, reboot to recovery and flash rom.....
if you wrap your head around HOW it works, its all really simple....so the first step is understanding HOW it works, not blindly following some tutorial or walkthrough.
please try to LEARN and UNDERSTAND what it is you are doing....
PS. you have involved ROOTING too many times in your post...... the rom is already ROOTED, you dont have to ROOT to unlock, flash rom or anything....ROOTING is only applicable INSIDE the booted OPERATING SYSTEM, and has nothing to do with recovery/bootloader

i feel i need to apologize to the board here.
frustrations were not directed at the OP of this thread, just in general....
i have been inundated with PM's and seeing the same barrage of questions for the last few days on the forum....
i can understand everyone's excitement...hell i was excited to get this too.
but you all need to read, and try to take it all in before attempting anything. sometimes those of us that understand whats going on, dont explain in a whole lot of detail, because we take the knowledge for granted, and assume if you are on this site, you are here to learn. it is frustrating to see the same questions pop up on nearly an hourly basis...
all i ask is that you take forth the effort to learn how these tools of ours work and understand that a lot of us working on things like this rely on you guys to assist each other in the process. that leaves us more time to deal with what we need to deal with and try and fix and squash bugs/processes/etc.
in return i apologize if i seem on edge the last couple of days...its because i am. if you can imagine one question multiplied by a hundred.....and having people freaking out about them 'bricking'.....after being warned its possible, but unlikely. i think most of these 'bricks' are salvageable and just require someone that understands how they work.
sorry to seem like an ass, but mainly its because i am an ass, and i have a hard time being nice most of the time.

Thanks pirateghost. I understand how to do the other methods but wanted to use something less complicated with less risk for user error. I read and read everything that is posted on the forums. I try not to ask a question unless I am not understanding what has been posted. Thanks for your patience and understanding.
Sent from my HTC PH39100 using XDA

PG, so im pretty sure i "bricked" it lol. im not upset as it was entirely my fault, just wondering if there is any way to get this mother to turn on? i know that when i plug it into the computer it recognizes it but not as anything i have seen lol..if i can find the correct drivers can this be reversed?

Thanks
Thanks to PG for everything and the instructions. I thought I had bricked my phone, but theCube was able to help me on IRC, which is where I suggest anybody go for real-time assistance.

This could off all been avoided with step by step Detail instruction. Why? Well example , I don't follow this forum at all never had an HTC phone but my wife's phone the vivid. All my phone has been Nexus and the galaxy line from Samsung, things over there are a bit different. All I did was flash the ph.img and then after not seen the device reboot I wipe/factory reset and all when to hell from there. Couldn't unlock the bootloader or reboot the phone. How could this happen? Assuming that people should know the basic is wrong. I'm not in any way blaming anyone I did this own my on risk but at the same time I'm super mad had to buy a new phone. As developer you should eliminate all threats and post a details instructions step by step with do's and don't before posting firmwares.
Sent from my Galaxy Nexus using xda premium

Dxtra said:
As developer you should eliminate all threats and post a details instructions step by step with do's and don't before posting firmwares
Click to expand...
Click to collapse
As a user, you should understand the risks/benefits of the things you download. The devs are under no obligation to keep you from bricking your phone, and to be fair, most everything is covered in the Superguide and the various ROM threads. Even if someone were to post a file called NOT_A_VIRUS.EXE and you downloaded it and it wiped your computer when you ran it, the responsibility is squarely on your shoulders.
As far as I remember, there is no dev/user contract and they're not getting paid for any of this.

Dxtra said:
As developer you should eliminate all threats and post a details instructions step by step with do's and don't before posting firmwares.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
oh?
am i being paid to do a job here?
i gave instructions based on how *I* got it to work and duplicated the procedure several times. so its MY responsibility to try and find a way to brick my phone for you?
an RUU cant brick your phone.....however, being a retard can.
this is the type of attitude i would expect my boss to have, if i screwed up a project....but alas, i am here out of my own free will.....
if this is how you feel, then you should get the F off this site.

formicae said:
As a user, you should understand the risks/benefits of the things you download. The devs are under no obligation to keep you from bricking your phone, and to be fair, most everything is covered in the Superguide and the various ROM threads. Even if someone were to post a file called NOT_A_VIRUS.EXE and you downloaded it and it wiped your computer when you ran it, the responsibility is squarely on your shoulders.
As far as I remember, there is no dev/user contract and they're not getting paid for any of this.
Click to expand...
Click to collapse
I totally 100% agree with you. If you HAVE taken the time to read and are still a bit confused, ask! For me I'm not even a week into this platform and I WILL NOT do anything that I don't entirely understand. The problem with android, if you could even call it a problem, is that there is such a huge variety of handsets and a big variety methods for doing this, that, and the other thing. It basically results in a non-linear process to get from point A to point B. It's imperative to understand the basic proceedures. If you were here since the G1, great, you've been able to.follow things from the start. I've used iOS for years, and I still love it btw.(only jailbroken of course!) I'll probably buy an iPad 3! The software is integrated with the hardware amazingly well, battery life is phenomenal, and ONCE JAILBROKEN, iOS is an excellent platform. Sure the "spec numbers" may not be as high but it boils down to.performance. That has always been great for me, obviously battery life is exceptional on apple devices as well. I'm hoping with a rooted ICS Rom there won't be cpu-time hogging processes and ill be able to adjust other things accordingly to get somewhat better battery life. I really wish each OEM would take the time to optimize the SW that they're using to the HW that they're selling. B/C from what I've seen the "Nexus" devices generally perform extremely well, even.against higher spec'd devices. So far I'm loving Android and my Vivid. I love the freedom that I get even on a non-rooted device! It's an excellent platform. Flexible, dynamic, and personal. Customization is there from the get-go. There are a million different things that one could do, even while staying un-rooted. The only reason that I've waited so long to get on board with android is ibwas waiting for it to grow and mature, if I could have a device that tri-booted Android, iOS, and WebOS I'd be a very happy person. I love using multiple platforms.
PG - I'm sorry if I bothered you, thanks for the great info though!
I think knowledge-wise I'm at a point where I'm not going to brick my phone. Wish me luck!

Pirateghost said:
oh?
am i being paid to do a job here?
i gave instructions based on how *I* got it to work and duplicated the procedure several times. so its MY responsibility to try and find a way to brick my phone for you?
an RUU cant brick your phone.....however, being a retard can.
this is the type of attitude i would expect my boss to have, if i screwed up a project....but alas, i am here out of my own free will.....
if this is how you feel, then you should get the F off this site.
Click to expand...
Click to collapse
Seriously if that is how you feel do get the f*ck off this site please. The devs in all mobile hacking communities are unpaid and do it for fun. You sir are a prime example of WHY THEY LEAVE!!! IF YOU DON'T KNOW AND HAVE READ, ASK, DON'T BE A ****!!!

Dxtra said:
This could off all been avoided with step by step Detail instruction. Why? Well example , I don't follow this forum at all never had an HTC phone but my wife's phone the vivid. All my phone has been Nexus and the galaxy line from Samsung, things over there are a bit different. All I did was flash the ph.img and then after not seen the device reboot I wipe/factory reset and all when to hell from there. Couldn't unlock the bootloader or reboot the phone. How could this happen? Assuming that people should know the basic is wrong. I'm not in any way blaming anyone I did this own my on risk but at the same time I'm super mad had to buy a new phone. As developer you should eliminate all threats and post a details instructions step by step with do's and don't before posting firmwares.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
REALLY? You want the UNNPAID DEV'S TO REMOVE ALL THREATS?!?!?! FROM WHAT IS BASICALLY OSS AND A FIRMWARE THAT SOMEBODY DL'D? REALLY? These guys take a FW and cook it into a ROM for FREE and just b/c you didn't take the time to understand it you're gonna put it on them? WTF?!?!?!?

i'll make him a deal. next time we get a hold of something like this, i will let him figure out how to get it on his phone....i don't have to share how...

Dxtra said:
This could off all been avoided with step by step Detail instruction. Why? Well example , I don't follow this forum at all never had an HTC phone but my wife's phone the vivid. All my phone has been Nexus and the galaxy line from Samsung, things over there are a bit different. All I did was flash the ph.img and then after not seen the device reboot I wipe/factory reset and all when to hell from there. Couldn't unlock the bootloader or reboot the phone. How could this happen? Assuming that people should know the basic is wrong. I'm not in any way blaming anyone I did this own my on risk but at the same time I'm super mad had to buy a new phone. As developer you should eliminate all threats and post a details instructions step by step with do's and don't before posting firmwares.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You know, its users like you that get Devs frustrated and not want to share the work that they have accomplished. XDA is a site for Devs, its not a WalMart that people can stop by and expect to be spoonfed and be on their merry way. Pirateghost is a very talented Dev who wanted to share something with this community, and instead of saying "thank you" you decide to look a the glass as half empty instead of half full and EXPECT MORE from him?
Reading your post, it tells me that you dont frequent the HTC forums at all, and instead of reading up, you just decided to flash. Just because it didnt go as smoothly as you thought it would is NO REASON to tell a Dev that they needed to do more. That part lays on you.
Next time you decide to tell a Dev that "they need to do more" I think you need to do more reading so it prevents you from having to buy a new phone. If it dosent make sense to you or you dont think theres enough documentation/step-by-step instructions YOU HAVE THE POWER TO SAY NO AND NOT FLASH IT.

Uh, there's a reason every single solitary dev puts a disclaimer on their ROM threads. Their work, if directions are not followed to the letter can turn your device into a +/- 200$ paperweight. I've been lurking around these forums for a hot minute, rarely post ( not an ounce of dev skill being the main reason), and really, when's the last time a dev didn't post at least semi detailed instructions to go along with his/her OP.
@pirateghost- bought a vivid literally 12 hours ago, got home, saw your thread, FOLLOWED THE DIRECTIONS CAREFULLY, and now have ICS on my device. Just wanted to say thanks.
And now for the most epic noob question of all time. Wth is RUU? I'm very familiar with flashing roms, cam, tibu, etc from my days on the sgsII SR forums. So most if not all HTC terminology is new to me.
Sent from my HTC PH39100 using xda premium

LG Phoenix Boot Errors

Hey all, Let me start by apologizing for not posting this in the right place (More than likely). i didnt see any threads for LG p505 Phoenix.
On to buisness, i had an error booting into ClockWorkMod Recovery. My phone is booting incorrectly ever since. ive tried to take the battery out and replace it, but that didnt work. I tried to follow some repair work listed on the forums, but i need further assistance. ive gotten as far as the SDK dev package and attempting to restart the bootloader, but no luck. it keeps saying it cant detect the device. the computer recognizes it as ASUS Android Bootloader Interface. Any help?

Where did you learn how to put CWM on you phone? If it wasn't here, why not try those forums where you did?
Try this
http://forums.androidcentral.com/t-lg-phoenix-thrive/

Well, i got CWM on my phone via the Rom Manager App on the Market. but, after toying around with my phone trying to fix it, it appears that it is stuck on the bootloader, and not CWM. when it DOES "boot up", it only displays lines of code that varies when i plug it into a power source or my PC.

Are you rooted?

yeah i am. couldnt have gotten this far without that step.

FawkesPhone said:
yeah i am. couldnt have gotten this far without that step.
Click to expand...
Click to collapse
Just didn't want you thinking you could flash cwm by installing rom manager.
What exactly is going on. Give lots of details.
* iTouched Epic

Well, good for you. im such a rookie that would be entirely possible. lol. anywho, i asked for help on another forum, who a couple people on have some experience with programing and such, and i pretty much explained everything there is to explain there.
however, the website wont let me post a link to said post, so im going to try to copy/paste because i REALLY dont feel like typing all that out again if i dont have to.

Copy link and put (dot) as the dot .
* iTouched Epic

the story is, i tried to boot my phone (LG phoenix [p505], running CarloROM, standard Kernnel) into ClockWorkMod Recovery Mode, but upon booting up, teh device went to a black screen, save for a couple words, most partial. the readable text says "UDC_Start()". on pluging it into the PC, it displays the following text:
-- suspend --
-- reset --
EP1/out FAIL nfo=40 pg0=74000
-- portchange --
usb_read() transaction failed
-- reset --
-- portchange --
fastboot: oops !
fastboot: Processing commands
i am trying to utilize the only fix ive found, which is to reboot the bootloader via andriod developer debug window. i tell the command prompt to run the "adb reboot bootloader" function but it says it cant find the device.
it also appears on the PC as "ASUS android bootloader interface"
Click to expand...
Click to collapse
here's all the details ive got thus far

Try flashing stock recovery on it. Flash back to complete stock. Did you check to make sure cwm was compatible with your device?
Was the other forum not helpful to you?
* iTouched Epic

boborone said:
Try flashing stock recovery on it. Flash back to complete stock. Did you check to make sure cwm was compatible with your device?
Was the other forum not helpful to you?
* iTouched Epic
Click to expand...
Click to collapse
First, not the other forum isnt helping as it's a small user group and no one's responded yet. second, as previously stated, after posting this thread, ive determined that the phone did NOT boot to CWM. and second, yes, CWM is compatable and has worked in the past. i heard about it from someone that has used it on his p505 and it works perfectly.

There are a lot of devices that only run a modded version of cwm. I have a Samsung intercept that won't run with standard cwm.
* iTouched Epic

people on the android central forum you posted a link to say the phoenix runs just fine with standard CWM

Did you try flashing the touch version of cwm? My epic touch sgsll bricks with that?
* iTouched Epic

i rooted my phone, downloaded ROM Manager, gave it Super user permissions, and flashed Optimus One (Old BaseBand). exactly as instructed.

Where did you learn about doing this? You said you tried asking on another forum. What did they say? Did you try what they said? Have you tried what I said about going stock?
* iTouched Epic

i learned all this from here: http://forums.androidcentral.com/t-lg-phoenix-thrive/138186-how-clock-workrecovery-mod-cwm.html
no one has responded on the other forum as previously stated
i have learned that my device is booting to the bootloader, not CWM, also as previously stated.
thus, flashing a new ROM of any sort is impossible.

FawkesPhone said:
i learned all this from here: http://forums.androidcentral.com/t-lg-phoenix-thrive/138186-how-clock-workrecovery-mod-cwm.html
no one has responded on the other forum as previously stated
i have learned that my device is booting to the bootloader, not CWM, also as previously stated.
thus, flashing a new ROM of any sort is impossible.
Click to expand...
Click to collapse
You never said you didn't get any responses from the other forum. If you posted the question yesterday and gave it a couple hours, no responses, then started flipping out cause your is phone is messed up and so you decided to join for the soul reason of using it as a technical support and post in off topic cause this site doesn't even develop (notice I didn't say support) your phone, I say you need to chill out and go back to other site and get a lil bit more in depth with your question. Cause honestly I would have overlooked your question with how it was written and the little information given. Those guys know about your bootloader. I don't. Not many here do. LG doesn't make flagship devices, hence why they're not here.
I can tell you that if nobody does help you, you need to read up on how to shell into the phone and flash something else like that.
* iTouched Epic

FawkesPhone said:
First, no, the other forum isnt helping as it's a small user group and no one's responded yet.
Click to expand...
Click to collapse
Also, why waste an hour of my time? If you're gonna tell me to eff off, why not do it at the beginning?

FawkesPhone said:
Also, why waste an hour of my time? If you're gonna tell me to eff off, why not do it at the beginning?
Click to expand...
Click to collapse
I didn't tell you to f off, but, in all seriousness, I don't like it when people join this site just to ask a question.
Then you post in the wrong forum about a phone that isn't even developed on here.
Sub-Forums : General discussion
Forum
Last PostStats
About xda-developers.com
Anything to do more with the site than with the phones. Feature requests, announcements, praise, moaning, etc.
General
Anything that involves all of the phones and doesn't fit in any of the other fora.
Paid Software Announcement and Discussion
Are you a developer wanting to promote for-pay software? Feel free to post announcements about your apps here and have the community discuss them.
Questions and Answers
This forum is for all questions, big or small, you might have. Please read the rules in this forum before asking.
Hardware Hacking
For discussion of development boards, hardware interfaces, datasheets, circuit modification and related tools
NFC Hacking
For discussion of Near Field Communication (NFC) hacking and development
Upgrading, Modifying and Unlocking
Some of the more advanced issues, involving multiple phones.
Accessories
For accessories that involves multiple phone-types. Car-kits, headphones, cables, chargers, extra batteries, replacement screens, sources for connectors, etc.
Networking
GPRS or WAP-settings, WiFi, ... This forum is for anything to do with getting your device talking to the rest of the world.
XDA TV
Here's your chance to communicate directly with the stars of XDA TV!
Off-topic
Anything not related to the phones.
^ Just wanted to point that out. ^
And I did try to help you. I don't know LG bootloaders. But I went through seeing if you made some noob mistake that I could help with. Then when that was sorted out, I told you how to help yourself. If you're are going to take someone telling you how to help yourself as telling you to f off, not sure you are going to make it here on XDA. Good luck with that attitude.
---------- Post added at 10:20 AM ---------- Previous post was at 10:16 AM ----------
Did you try to search here on this site?
Searched here on XDA and found this:
http://forum.xda-developers.com/showthread.php?t=1289265&page=3
You see, we don't mind helping people at all, it's the people that won't help themselves that get on people's nerves. Look man, I will help you as much as I can. But you have to be willing to help yourself, too. Finding threads like the one I posted above is what I mean by searching and reading on how to shell into the phone, using adb to fix your problems. You have a jacked up phone, don't get frustrated and mad at the world, calm down, chill out. You can fix it.

[Q] Few questions

Okay so, since I'm sort of new, I wanted to ask a few questions:
1. Is it possible to root xperia x8 with manufacturing date 11w48? At least at 95% chance. I'm a bit scared of the bricking part...
2. If it is possible, what kind of "ROM" (if I understood correctly) should I get?
3. If I get hard bricked/soft bricked what's the chance my phone will be still usable.
That's about it. Please don't rage at me for "OMG USE SEARCH BUTTON" type of thing.
I have tried doing it but no results found. Just threads and posts of people updating their.. ROMs I gues? Correct me if I typed anything wrong there.
But yeah, help would be appreciated. Thanks!

Jetboard said:
Okay so, since I'm sort of new, I wanted to ask a few questions:
1. Is it possible to root xperia x8 with manufacturing date 11w48? At least at 95% chance. I'm a bit scared of the bricking part...
2. If it is possible, what kind of "ROM" (if I understood correctly) should I get?
3. If I get hard bricked/soft bricked what's the chance my phone will be still usable.
That's about it. Please don't rage at me for "OMG USE SEARCH BUTTON" type of thing.
I have tried doing it but no results found. Just threads and posts of people updating their.. ROMs I gues? Correct me if I typed anything wrong there.
But yeah, help would be appreciated. Thanks!
Click to expand...
Click to collapse
1. You can safely root your x8 regardless of when it is manufactured, you will not brick it
2. You have 11w48 so it is very risky to unlock your bootloader, i suggest you flash ROMS that is for stock
3. If you get soft bricked you can flash the stock firmware back using flashtool or SEUS, if it is a hard brick, you need to go to the nearest Service center or use a JTAG
Swyped via Tapatalk 2

Thanks a whole bunch. I thought I cannot root because of my manufacturer date. But what is a flash ROM tho?

Jetboard said:
Thanks a whole bunch. I thought I cannot root because of my manufacturer date. But what is a flash ROM tho?
Click to expand...
Click to collapse
you can root your phone. but you can't unlock bl.
when you root your phone, you cam install cwm recovery. simply dl a rom for stock kernel and go to recovery and install(flash) the rom. remember to check the instructions first.
Just because i don't doesn't mean i can't.

All what I found until today was that if I cannot unlock BL I cannot install CWM recovery.
Maybe it is related to model - mine is Sony Xperia J. Y2012.
There is no fastboot available.
Am I wrong, can I have CWM, nandroid backup etc on stock ROM as only such one I may flash ?

F308 said:
All what I found until today was that if I cannot unlock BL I cannot install CWM recovery.
Maybe it is related to model - mine is Sony Xperia J. Y2012.
There is no fastboot available.
Am I wrong, can I have CWM, nandroid backup etc on stock ROM as only such one I may flash ?
Click to expand...
Click to collapse
this is for x8. not sure how it works on J. but yeah we don't havt fastboot either. but we can install cwm even with a locked bl. again that's for se x8.
edit: my advice is go to your phone's subforum. you'll get your answers there.
Just because i don't doesn't mean i can't.

Thank you. I understand that lot of things is device dependent but thought there are non-breakable rules, like gravity,
and what is possible to do under certain circumstances was one of them.
Need walk through XDA forum once more, maybe there is a hope.

F308 said:
Thank you. I understand that lot of things is device dependent but thought there are non-breakable rules, like gravity,
and what is possible to do under certain circumstances was one of them.
Need walk through XDA forum once more, maybe there is a hope.
Click to expand...
Click to collapse
there probably are a few unbreakable rules, but not being familiar with your device i can't guarantee that it's safe or it would work.
Just because i don't doesn't mean i can't.

Despite lot of reading I still am missing knowledge.
Question is:
What is fastboot ?
I found more than one definition of it and compiled into my own.
1.
Of course fastboot.exe is Windows binary (part of flashtool pack) which does certain type of work.
This is not what we are interested in.
2.
I concluded that:
- fastboot is one of modes into what android device can wake up. Just like linux can boot in different ways or Windows into single mode.
- this feature is encoded into boot.img, it is not separate android application.
- boot.img will work only with related kernel.img. They are like love and marriage (which is like horse and carriage - Bundy's).
- Sony sometimes disables stock boot.img to boot into this mode then without replacing boot .img it is impossible.
More comments ?

Fastboot is protocol used to update the flash filesystem in Android devices from a host over USB. It allows flashing of unsigned partition images.
Just because i don't doesn't mean i can't.

Okay, I got one more last question. Is this guide http://forum.xda-developers.com/showthread.php?t=906195&nocache=1 okay to use for rooting? I'm still trying to find the LATEST safe ones =/ I wonder if this one is okay.
Um, I tried that one it didn't work. It said some stuff are missing, then it exited randomly etc.. Can someone give me a link or a short/long guide which I can use that's latest? I do have some X8 drivers in a .zip file but no idea how to install them. Thanks in advance.

Jetboard said:
Okay, I got one more last question. Is this guide http://forum.xda-developers.com/showthread.php?t=906195&nocache=1 okay to use for rooting? I'm still trying to find the LATEST safe ones =/ I wonder if this one is good.
Click to expand...
Click to collapse
I rooted mine with this
Means its safe
Sent from my X8

Having few issues with the SuperOneClick thing... It sometimes randomly exits, tells me that some stuff are missing etc. Any help? =/

Need help rooting Nexus 6 on 6.0.0

I want to root my Nexus 6 running stock android 6.0.0 but not sure exactly how to do it. Any help would be greatly appreciated. Thanks

dbzturtle said:
I want to root my Nexus 6 running stock android 6.0.0 but not sure exactly how to do it. Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Chainfire just released a new root for mm, http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Sent from my Nexus 6 using Tapatalk

blueyes said:
Chainfire just released a new root for mm, http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It says that it's experimental and will likely have bugs. is there a stable way to root? If not I don't mind waiting until there is.

dbzturtle said:
It says that it's experimental and will likely have bugs. is there a stable way to root? If not I don't mind waiting until there is.
Click to expand...
Click to collapse
Fastboot flash twrp, and then flash 2.52superuser.sip in recovery. Look up wugfresh Nexus root toolkit, it'll explain the process.
Sent from my Nexus 6 using Tapatalk

I rooted my N6 on Android 6.0 with 2.52 weeks ago and it's absolutely fine - I've seen no problems at all. The "experimental" mention is a disclaimer to cover Chainfire in case you have problems - a very sensible warning in my opinion, but in this case you can probably ignore it.
And I agree with blueyes - Nexus Root Toolkit is pretty much idiot-proof as long as you read the instructions and in particular choose the correct ROM.

dahawthorne said:
I rooted my N6 on Android 6.0 with 2.52 weeks ago and it's absolutely fine - I've seen no problems at all. The "experimental" mention is a disclaimer to cover Chainfire in case you have problems - a very sensible warning in my opinion, but in this case you can probably ignore it.
And I agree with blueyes - Nexus Root Toolkit is pretty much idiot-proof as long as you read the instructions and in particular choose the correct ROM.
Click to expand...
Click to collapse
The problem with using toolkits when they are "idiot-proof" is that if you go into the process as an idiot, you leave the process still an idiot, so if something goes wrong with the device at a later date, the user has not got the skills to fix it, which becomes a problem on these forums as rather than telling someone how to fix it, we also have to teach the skills that should already have been learned.
Toolkits are great if you know what they're doing but if you dont, use fastboot the first time to get an understanding of it and also to ensure you know it is working on your computer correctly. It's easier to troubleshoot PC configurations when the device is fully working rather than waiting until it is "broken"

"you leave the process still an idiot"
I'll take that in the spirit I think you meant it...
Sure, point taken, but the problem with telling someone to start learning to use tools they don't understand is that this forum ends up with a flood of "I've bricked my device" posts. I agree that the manual way is useful for resolving problems, and I don't use NRT for everything - I'd say maybe 50% of the time for installing a brand new factory ROM, and the rest of the time using ADB/Fastboot for stuff I (think I) understand.
I just think that if someone has taken the time and trouble to give me the commands typed perfectly in the correct order and proven to work, why would I risk typing them in maybe in the wrong order or accidentally installing an image into the wrong partition? My own stupid fault, sure, but why take the long way round instead of the simple straight proven path?
Just sayin'...

dahawthorne said:
"you leave the process still an idiot"
I'll take that in the spirit I think you meant it...
Sure, point taken, but the problem with telling someone to start learning to use tools they don't understand is that this forum ends up with a flood of "I've bricked my device" posts. I agree that the manual way is useful for resolving problems, and I don't use NRT for everything - I'd say maybe 50% of the time for installing a brand new factory ROM, and the rest of the time using ADB/Fastboot for stuff I (think I) understand.
I just think that if someone has taken the time and trouble to give me the commands typed perfectly in the correct order and proven to work, why would I risk typing them in maybe in the wrong order or accidentally installing an image into the wrong partition? My own stupid fault, sure, but why take the long way round instead of the simple straight proven path?
Just sayin'...
Click to expand...
Click to collapse
It's not really the long way round. Once everything is installed, its as quick if not quicker. And as I said, you need all this installed for ongoing maintenance anyway so may as well do this whilst your device is working.
You can't brick your device by flashing to the wrong partition so there are no floods of posts from people doing things manually at all. .if you flash to the wrong partition,.just flash to the right partition. It's not rocket science either. If you flash a radio, flash it to the radio partition. If you flash system, flash it to the system partition. ...and if you type something wrong, it won't do anything at all.
Fastboot is well documented (by me and others) in the general forum. People should feel free to nude toolkits once they have learned it, but noobs should definitely learn it and use it the first time for the reasons I have already mentioned.
To root is so simple.
1. In fastboot, use
"fastboot oem unlock"
2. In fastboot, flash a custom twrp recovery image
"fastboot flash recovery twrp.img "
3. If marshamallow, flash a custom boot.img to allow it to be rooted
"fastboot flash boot boot.img"
4. Copy SuperSU to sdcard
5. Flash SuperSU zip from recovery
Once these steps have been carried out, you've used fastboot, know how it works and also have proof your computer has working fastboot. That ticks essential boxes.that every root user needs to have ticked. Once they're ticked, use toolkits to your hearts desire.
The worst thing about noobs using toolkits is when we need them to use fastboot when helping with their issues, they don't know what it is and we have to teach them that. We also need to troubleshoot setting it up which can be extremely hard if their device is bricked or in a state of needing repair. 10 minutes learning now can help prevent hours of wasting our time later. Surely it's only being courteous to learn these things ?

Where can I find a custom boot image ? I'm asking because I'm rooted but every time I try to go into recovery it ask me for a password

getmoneygreen said:
Where can I find a custom boot image ? I'm asking because I'm rooted but every time I try to go into recovery it ask me for a password
Click to expand...
Click to collapse
If you're encrypted, recovery will always ask you for a password. If you've set a password in android, you use that..if you have not set a password in android, you use the default twrp password.

I am an Android Noob! My first Android devices were the Nexus Player and the Nexus 6. (I came from iPhones and Apple TV) It did not take me long at all to learn how to use fastboot and adb. I manually flashed my Nexus 6 and Nexus Player to 6.0 before the OTAs were rolling out no problem. I have root on both of my devices.
My point is, if I can learn how to do this in a matter of a day (I have not had my Nexus 6 a full month yet) You can learn how to do it as well. There are tons of guides out there on how to do all of this. Google is your friend. You will feel awesome and have a sense of accomplishment if you take the time to learn this stuff. It is easy to learn, not hard at all! I come from a pretty extensive tech background so I was a step ahead, but anyone can do / learn this stuff.
There are toolkits that can do this stuff for you pretty much. I have not downloaded or used one myself. I don't trust someone else's code with my device. That's just me though. I like to feel in control when I flash stuff.

@danarama
"Surely it's only being courteous to learn these things ?"
I know that it's all too easy to be taken wrong when writing a post, so I'll say up front that I'm serious - thanks for posting those steps. I've watched the NRT run through its steps a number of times and it clearly does a lot more than this, which is why i'm glad that it's doing the typing for me
I have used your steps when flashing various things, I've just never used them for a ROM upgrade - except once when I was trying to recover a broken-radio N5 and was installing Chroma.
One value at least of the NRT for noobs is its help in setting up your PC's drivers - that alone is a good reason to look at it.
Just for interest, what would happen if I flashed recovery into the radio partition? Or the boot partition?
Seriously, thanks for these steps - I appreciate it.

dahawthorne said:
@danarama
"Surely it's only being courteous to learn these things ?"
I know that it's all too easy to be taken wrong when writing a post, so I'll say up front that I'm serious - thanks for posting those steps. I've watched the NRT run through its steps a number of times and it clearly does a lot more than this, which is why i'm glad that it's doing the typing for me
I have used your steps when flashing various things, I've just never used them for a ROM upgrade - except once when I was trying to recover a broken-radio N5 and was installing Chroma.
One value at least of the NRT for noobs is its help in setting up your PC's drivers - that alone is a good reason to look at it.
Just for interest, what would happen if I flashed recovery into the radio partition? Or the boot partition?
Seriously, thanks for these steps - I appreciate it.
Click to expand...
Click to collapse
Radio may boot but won't connect to a network.
Boot is the kernel so it won't boot without it (bootloop)
Both can be fixed by flashing the correct image to the correct partition.
The images in the factory image are appropriately labelled too, so it would be difficult to flash to the wrong partition without realizing it was wrong.. Eg
"fastboot flash radio boot.img" looks wrong when you have radio.img too.

Thanks, danarama. I suppose that's the point I was trying to make at the top - that if you're a bit of a thicko then you could flash to the wrong partition, which a predefined script won't. As long as it's recoverable, no problem, but I remember the pumping heart and breathlessness as I watched my devices on several occasions sitting with the boot animation for 10-15 minutes and thinking "What the hell do I do now?"
I know I'm hijacking this thread (sorry...) but is there anything you can think of that would definitely hard-brick my device if I'm being thick or careless? I've never managed it, and maybe as Android progresses it's becoming harder to hard-brick, but is there ever a time when I need to think "There's no way back from this one"?

danarama said:
If you're encrypted, recovery will always ask you for a password. If you've set a password in android, you use that..if you have not set a password in android, you use the default twrp password.
Click to expand...
Click to collapse
Thank for the heads up really appreciate that. BTW what is the default password for twrp

getmoneygreen said:
Thank for the heads up really appreciate that. BTW what is the default password for twrp
Click to expand...
Click to collapse
Not sure, Im not encrypted. But its documented somewhere by twrp dev. Maybe on their site or in their thread