Related
I feel I've made a terrible (and stupid) mistake. I decided to unroot my phone from cyanogen roms. I read a how to guide that I guess was outdated because now I have android 1.0 firmware. The guidw was [how to] unroot by tubaking182 (absolutely zero offense to him, not his fault, I'm stupid, etc etc.) So I now have stock version 1.0. There's no check for system updates under about phone in settings so I can't do that. There are file manager apps that I could use to rename the necessary updates into update.zip, but there's no apps available like download crutch so I can download them. I also can't enter recovery. It gives me a triangle with an exclamation inside next to a image of a phone and that's it and I have no idea how to install an update without recovery mode. As I'm sure you've noticed by now, I'm the epitome of newb and feel free to laugh at my failure. I just really need someone to help me and would be eternally grateful. In all likelihood, I'll need step by step instructions on what to do. I know this is a lot to ask and I've really done nothing to earn this help... I really just need assistance. Thank you to anyone who helps me in advance
Not to be an asshole and say "Shoulda Coulda Woulda" but you really should have done your research before embarking on bricking your phone.
ItsAndroidsWorld had many videos on You Tube. Look for ones on how to root, then how to install the death spl, then look for the ones with Super D or FastTest .. as it seems as though they are probably the best roms for everyday use at this point.
I've found that using these videos via You Tube is the easiest way to go.
Good Luck.
^^^ ABOVE POST stolen from another similar thread.
psyko-m1 said:
Not to be an asshole and say "Shoulda Coulda Woulda" but you really should have done your research before embarking on bricking your phone.
Click to expand...
Click to collapse
he didn't brick his phone, don't scare him
To OP: The same happened to me when I was a n00b at this ****.
Dude, google is your friend.
Calm down.
tsk tsk tsk.....Im gonig to say this....WRONG SECTION
but I will be nice as well. just find the updates on google from 1.0 to 1.5 and oh yeah to get back into recovery from the triangle withthe !...alt L...but if you somehow brick ya phone youe fault not mine next time do ya research before you mess with ya phone
Technically speaking he is in a DEFCON 2 "Brick" situation.
Sorry.
psyko-m1 said:
Technically speaking he is in a DEFCON 2 "Brick" situation.
Sorry.
Click to expand...
Click to collapse
Well he's in the wet cement
SeEsAw12 said:
Well he's in the wet cement
Click to expand...
Click to collapse
Or...
You are late for work and have a flat...
click on this http://theunlockr.com/category/howto/android_how_tos/htc-mytouch-3g-magic/:cool:
remove the cool http://theunlockr.com/category/howto/android_how_tos/htc-mytouch-3g-magic/
this website should help you get back on track and you just need to download the nbh file to get it back to cupcake
BUT 0MGAWWZZZ N00BZORZ DO3S 1.0 HAVE A DA SENSE RAOM???
in all seriousness, there's nothing actually wrong with your phone. You completely unrooted it. By following the aforementioned instructions, it'll be easy to reroot and update. What I DO find weird is why you're not getting 1.5 OTA...
although i hate when people post in the wrong section - im in a good mood this morning
http://zenthought.org/content/project/flashrec
not sure if it works in 1.0 - it should as it uses a rather old bug to do so
Easy as pie...just follow the guide in my sig.
=)
To those who say I bricked it, I know that's not the case it still works so I obviously didn't brick it... not that fail thankfully.
To thenameismax, AHA! I did not know about alt+l retrieving text so thank you thank you thank you. I just need to get the necessary updates and copy them to sd card root, rename update.zip/install one at a time... I think lol
Thanks again to all who helped and sorry about the wrong section. When I was rooting, it was in development. I assumed that unrooting would be too and therefore problems with that... further fail.
afiellerddr said:
To those who say I bricked it, I know that's not the case it still works so I obviously didn't brick it... not that fail thankfully.
To thenameismax, AHA! I did not know about alt+l retrieving text so thank you thank you thank you. I just need to get the necessary updates and copy them to sd card root, rename update.zip/install one at a time... I think lol
Thanks again to all who helped and sorry about the wrong section. When I was rooting, it was in development. I assumed that unrooting would be too and therefore problems with that... further fail.
Click to expand...
Click to collapse
yeah man no problem. good luck.
Don't do anything. In a day or two you get an OTA update.
You can force the update like people have mentioned, but as long as you can hold off for a day or two you dont need to.
BTW, at some point you will see the E or 3G icon downloading like crazy and you dont know why. It is downloading the update. Stay away from task killers and in my experience it is good to be around wifi.
Just relax.
Sent Move Request
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
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.
Just bought a brand new N6 and its not downloading any ota's, still on 5.0. The build is LNX07M which is a developer build and apparently will not download any ota's. Has anyone heard of this? Did a quick Google search and there is hardly anything about this build.
I have no access to a computer, am I stuck on this build and 5.0?
csdaytona said:
Just bought a brand new N6 and its not downloading any ota's, still on 5.0. The build is LNX07M which is a developer build and apparently will not download any ota's. Has anyone heard of this? Did a quick Google search and there is hardly anything about this build.
I have no access to a computer, am I stuck on this build and 5.0?
Click to expand...
Click to collapse
no access at all?
simms22 said:
no access at all?
Click to expand...
Click to collapse
Not at the moment. What will I need to do?
This is my first nexus device and the last phone I rooted/flashed was the G1 way back in the day.
I was excited to get my phone today so this kind of sucks....
csdaytona said:
Not at the moment. What will I need to do?
This is my first nexus device and the last phone I rooted/flashed was the G1 way back in the day.
I was excited to get my phone today so this kind of sucks....
Click to expand...
Click to collapse
ohh.. that sucks. i remember my g1
i have a way that will probably work out fine, but this way is highly looked down upon on xda. would you be willing to try? btw, im one of those that would look down on this way, unless in certain situations..
simms22 said:
ohh.. that sucks. i remember my g1
i have a way that will probably work out fine, but this way is highly looked down upon on xda. would you be willing to try? btw, im one of those that would look down on this way, unless in certain situations..
Click to expand...
Click to collapse
OK what is it and why is it frowned upon?
csdaytona said:
OK what is it and why is it frowned upon?
Click to expand...
Click to collapse
because its not "proper", and normally isnt used properly. but ill explaine to you the proper way. you can try an app called kingsroot. you csnt get it at the play store, youll have to search google for it. after you install it, then run it, youll have root. but, youre not done yet. you will want to download the latest twrp recovery for the nexus 6 with your phone and keep it there. then you will unstall flashify from the play store. you will now use flashify to flash the twrp recovery. now, last thing, to get your bootloader unlocked. you will install any bootloader unlock apps, like boot unlocker or similar(that might delete everything from your phone), then youre done. ive never tried this on a nexus, but have on other devices, just so you know.
simms22 said:
because its not "proper", and normally isnt used properly. but ill explaine to you the proper way. you can try an app called kingsroot. you csnt get it at the play store, youll have to search google for it. after you install it, then run it, youll have root. but, youre not done yet. you will want to download the latest twrp recovery for the nexus 6 with your phone and keep it there. then you will unstall flashify from the play store. you will now use flashify to flash the twrp recovery. now, last thing, to get your bootloader unlocked. you will install any bootloader unlock apps, like boot unlocker or similar(that might delete everything from your phone), then youre done. ive never tried this on a nexus, but have on other devices, just so you know.
Click to expand...
Click to collapse
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Btw, thanks for helping me out.
csdaytona said:
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Btw, thanks for helping me out.
Click to expand...
Click to collapse
If you can get to a computer, download this: https://dl.google.com/dl/android/aosp/shamu-mra58k-factory-5b07088c.tgz
It's the Marshmallow (6.0) factory image for the Nexus 6. Run the batch file inside and it'll flash your phone. Note that this WILL wipe it.
Here's the actual Google-supplied information on it: https://developers.google.com/android/nexus/images?hl=en
|Jason8| said:
If you can get to a computer, download this: https://dl.google.com/dl/android/aosp/shamu-mra58k-factory-5b07088c.tgz
It's the Marshmallow (6.0) factory image for the Nexus 6. Run the batch file inside and it'll flash your phone. Note that this WILL wipe it.
Here's the actual Google-supplied information on it: https://developers.google.com/android/nexus/images?hl=en
Click to expand...
Click to collapse
First time doing this, but it's OK to jump straight to 6.0?
csdaytona said:
First time doing this, but it's OK to jump straight to 6.0?
Click to expand...
Click to collapse
It'll be fine. It's the complete system image, so it doesn't matter what you're on currently. Note that you will have to install all sorts of extra crap to get the Android SDK installed and working and the proper drivers, but it's not that hard, just gigs of downloads when everything is all said and done.
Like I said, it WILL wipe your phone completely.
csdaytona said:
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Btw, thanks for helping me out.
Click to expand...
Click to collapse
if you can get to a computer..
you can unlock your bootloader with "fastboot oem unlock"
then fastboot flash twrp recovery
then flash a custom kernel wiyh the latest supersu in your new recovery.
and then boot up with root, an unlocked bootloader, and a custom recovery
|Jason8| said:
It'll be fine. It's the complete system image, so it doesn't matter what you're on currently. Note that you will have to install all sorts of extra crap to get the Android SDK installed and working and the proper drivers, but it's not that hard, just gigs of downloads when everything is all said and done.
Like I said, it WILL wipe your phone completely.
Click to expand...
Click to collapse
Not worried about wiping the phone, I've literally only had it for a few hours and nothing is loaded on it.
Would be possible to just install an ota to get me on the right upgrade path? I'm just trying to do the quickest and easiest method possible.
csdaytona said:
Not worried about wiping the phone, I've literally only had it for a few hours and nothing is loaded on it.
Would be possible to just install an ota to get me on the right upgrade path? I'm just trying to do the quickest and easiest method possible.
Click to expand...
Click to collapse
If it's not grabbing an OTA, not sure what else you can do, short of downloading all the OTAs and flashing via recovery. But no guarantee that'll work as you're on a development build... There probably isn't an OTA to go from your development build to a release build.
csdaytona said:
I have no access to a computer, am I stuck on this build and 5.0?
Click to expand...
Click to collapse
simms22 said:
no access at all?
Click to expand...
Click to collapse
csdaytona said:
Not at the moment.
Click to expand...
Click to collapse
csdaytona said:
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Click to expand...
Click to collapse
Dude, come on... I know this is the Q&A section, and were supposed to be nicer here... But this lazyness is bull****.
You act like using a computer is impossible, then as soon as it takes some work.... You can get at one the next day?
Stop expecting to be spoon fed and at least try to learn something fist. There are a TON of write ups on how to do this. You spend how much money on a phone, and now you don't care to educate yourself on it?
Instead of expecting other to do all the work for you, read through the stickied index thread in the general section
http://forum.xda-developers.com/nexus-6/general/nexus-6-index-thread-t3229412
It has a newbie guide that literally holds your hand through the whole process. Post 2 has info on "how to flash factory images", use method 2 as method 1 in that thread will not work with the MM factory image.
Nice people have already spend a lot of time and effort documenting these things for you, as they are common questions. People like Simms and the other posters in this thread answer questions and offer support for free out of the kindness of their heart... Don't create extra work for them by ignoring all the effort already put out by other members, expecting it all to be regurgitated to you.
|Jason8| said:
If it's not grabbing an OTA, not sure what else you can do, short of downloading all the OTAs and flashing via recovery. But no guarantee that'll work as you're on a development build... There probably isn't an OTA to go from your development build to a release build.
Click to expand...
Click to collapse
Fastboot, as described in the threads mentioned above, will completely overwrite the pertinent partitions, regardless of what was there... dev build or not. No need to flash and apply countless incremental updates. Google provides not only full system images, but the information to use them on their web page...
|Jason8| said:
If it's not grabbing an OTA, not sure what else you can do, short of downloading all the OTAs and flashing via recovery. But no guarantee that'll work as you're on a development build... There probably isn't an OTA to go from your development build to a release build.
Click to expand...
Click to collapse
Gotcha. I'll try to flash 6.0 tomorrow. Wish me luck.
Thanks for the help!
scryan said:
Fastboot, as described in the threads mentioned above, will completely overwrite the pertinent partitions, regardless of what was there... dev build or not. No need to flash and apply countless incremental updates. Google provides not only full system images, but the information to use them on their web page...
Click to expand...
Click to collapse
I linked him to that already. No need to be a **** about it. He was looking for an easy way to do it now, when he doesn't have a computer. **** got crazy, so he asked if it would be easier with a computer, which the answer is yes.
Wouldn't you be excited as **** if you had a new phone? Wouldn't you want to get it up and running as quickly as possible? Well... now he's gotta wait until he has a computer. Obviously installing an OTA and doing the incremental updates would be easier, which is what he was looking for. Since that's not an option, we laid out other ways to go about doing it. So he's getting to a computer tomorrow.
---------- Post added at 09:51 PM ---------- Previous post was at 09:50 PM ----------
csdaytona said:
Gotcha. I'll try to flash 6.0 tomorrow. Wish me luck.
Thanks for the help!
Click to expand...
Click to collapse
No problem man. I wish you luck!
If you do plan on modding it/rooting it/romming it in the future, DEFINITELY unlock your bootloader before you set up the phone or that'll wipe it, too.
|Jason8| said:
Wouldn't you be excited as **** if you had a new phone? Wouldn't you want to get it up and running as quickly as possible? Well... now he's gotta wait until he has a computer. Obviously installing an OTA and doing the incremental updates would be easier, which is what he was looking for. Since that's not an option, we laid out other ways to go about doing it. So he's getting to a computer tomorrow.
Click to expand...
Click to collapse
You act like I was born with a nexus 6... It was a new phone to me too. I was so excited I read as much as I could on it, thanking the people who were so gracious to spend their personal time writing guides so I could understand the process well enough to be comfortable with my phone and help others here.
scryan said:
Dude, come on... I know this is the Q&A section, and were supposed to be nicer here... But this lazyness is bull****.
You act like using a computer is impossible, then as soon as it takes some work.... You can get at one the next day?
Stop expecting to be spoon fed and at least try to learn something fist. There are a TON of write ups on how to do this. You spend how much money on a phone, and now you don't care to educate yourself on it?
Instead of expecting other to do all the work for you, read through the stickied index thread in the general section
http://forum.xda-developers.com/nexus-6/general/nexus-6-index-thread-t3229412
It has a newbie guide that literally holds your hand through the whole process. Post 2 has info on "how to flash factory images", use method 2 as method 1 in that thread will not work with the MM factory image.
Nice people have already spend a lot of time and effort documenting these things for you, as they are common questions. People like Simms and the other posters in this thread answer questions and offer support for free out of the kindness of their heart... Don't create extra work for them by ignoring all the effort already put out by other members, expecting it all to be regurgitated to you.
Fastboot, as described in the threads mentioned above, will completely overwrite the pertinent partitions, regardless of what was there... dev build or not. No need to flash and apply countless incremental updates. Google provides not only full system images, but the information to use them on their web page...
Click to expand...
Click to collapse
i have absolutely no computer nor laptop access, so i completely understand(understood) his side as well.
scryan said:
You act like I was born with a nexus 6... It was a new phone to me too. I was so excited I read as much as I could on it, thanking the people who were so gracious to spend their personal time writing guides so I could understand the process well enough to be comfortable with my phone and help others here.
Click to expand...
Click to collapse
He googled his build number and didn't get many hits on it. So he's asking if there's a way to get it up and running tonight without a computer. Seems valid to me. You jump into the thread offering no help at all and start talking **** about the guy. That's the exact opposite of what you're saying you strive to do. I don't get it.
simms22 said:
i have absolutely no computer nor laptop access, so i completely understand(understood) his side as well.
Click to expand...
Click to collapse
At that point its a legitamate question. This is a very different situation that is not well covered here, and requires a unique solution not many would come up with.
But "I absolutely have no computer nor laptop access" is pretty different then "I can access one TOMORROW. Sheesh, having something 1 day away is pretty far from it not being a possibility.
And I think you would agree it would be a significantly better idea to wait that day then to proceed with the method you gave (not that it was bad of you to give it... but you tried to differentiate and he held out to avoid being told to do it the hard way)
|Jason8| said:
He googled his build number and didn't get many hits on it. So he's asking if there's a way to get it up and running tonight without a computer. Seems valid to me. You jump into the thread offering no help at all and start talking **** about the guy. That's the exact opposite of what you're saying you strive to do. I don't get it.
Click to expand...
Click to collapse
We are told time and time again that their are no bad questions. Truth is there are more bad questions then good ones.
Him asking about a build that provides few google hits is very legitimate.
Him asking about doing it without a computer because he doesn't have one is legitimate.
It only becomes an issue when he doesn't get the answer he wants, and all of a sudden he does have computer access.
And given that he is going to proceed in a computer... It becomes nothing more then "How do I update my phone?", which is VERY well documented.
I not only gave him the link to the information he needed, AND even corrected the information pointing out that the flashall script fails and that he would need to use the second method listed in the instructions I linked him to (since I know he will likely have limited time to fail and figure out whats wrong)
"That's the exact opposite of what you're saying you strive to do. I don't get it."
Then let me explain.
Would you skip your homework, ignore your textbook, then show up to class asking your teacher to explain it again? We are here to help... but how or why should I care more about it then he does? With no attempt made to learn, how much should I care to teach him?
Its a pretty big **** you to all those who have spend countless hours documenting this stuff to help new people to ignore their work and tell someone to do it again.
Hi everyone,
Please forgive any n00b questions.
I got started with rooting / custom ROMs on a Nexus 4, and I didn't realize at the time that this made things really easy and I didn't need to learn very much about how everything worked. Fast forward to last week -- I decided, at long last, that I was tired of using stock MM on my T-Mo G4 / H811. How hard could it be? Probably not much different from playing on my old Nexus 4 right? Lol, maybe not.
So now 72 hours later, my phone is hard bricked and will not enter download mode. and I need some assistance, if anyone would be so kind.
I will try to recount what I did:
To start with, I was using a Mac, so I used Homebrew to install Android platform tools / ADB.
I decided I wanted to try out LineageOS so I went ahead and followed their very clear steps (on LOS wiki) to unlock the bootloader install TWRP. However, TWRP doesn't seem to have an official build for the G4(!) so I had to look up and use one of the betas from this post. Is this where I went off the rails already? [Of course, very stupidly I also failed to make a complete backup of anything before going on ahead. Rookie mistake.]
After unlocking bootloader and flashing my TWRP beta, I was able to boot into TWRP just fine. I followed the normal prescribed steps of doing a Wipe (normal TWRP defaults -- system, cache, etc.?) before flashing the latest LOS nightly (14.1-something) and also the nano-x64 variety of gapps. I rebooted and got stuck with the LOS boot animation. I let this go for 55 minutes, so I am pretty sure it was an actual bootloop, not just the 1st-time-startup and optimization going on.
I rebooted into TWRP and decided to try a different ROM to see if that was the issue. So I wiped again, flashed another ROM (I believe it was a flavor of AOKP 14.1.x), flashed gapps again, and gave it another try. Again got stuck with an endless bootloop (45 minutes).
Since this is my daily driver, I decided to go back to stock. Found this thread, downloaded the MM-debloated zip, pushed to phone, and again Wiped + Flashed. This time, when I hit reboot, my phone was immediately hard-bricked. No startup screen, no nothing. That was quite unexpected. Also, the first time I had ever HARD bricked a device that I was playing with. Yikes!
Since then, I got a hold of a PC, and have been trying to revive the device by flashing an image to the microSD and booting into Download mode, in the form of this thread or this one.
I did get this to work briefly yesterday, or at least I got to Download Mode / Firmware Update screen, and then attempted to run LGUP with the KDZ file. However I ran into an error at about 9%, and couldn't continue -- and then I had to give back my loaner PC for the day. I also noticed that the LG Mobile Support tool was recognizing my phone NOT as an H811 but as something like HX230 or ... whatever it was, it was definitely wrong. Which is worrisome.
Today I'm giving it another try but my phone will not enter Download Mode at all, nor respond in any other way. I'm curious if this is a battery issue? So I am simply charging it for the time being. I also re-formatted the microSD and re-flashed the single .img just to be safe, but still can't get a response out of the phone. On my PC's device manager it is showing up as the common Qualcomm 9008 that a lot of people seem to have seen. No recognition from LG Mobile Support tool, nor from LGUP.
So ... what now?
It's possible that once my battery gets some charge again, maybe I'll be able to enter DL mode. Let's hope so.
However, I am also totally in the dark about which software version I should be using. 20i? 20p? I have no idea what these refer to, and I did not make any prior notes to capture the state that my phone was in before this all began. So IF I get to DL mode I will definitely need further instruction on the CORRECT KDZ FILE to be flashing. Else I will just compound my problems.
ANY tips or suggestions will be appreciated! Thanks so much.
Should have verified being on 20o firmware
Upon further reading, quite obvious, at the top of this thread, I definitely should have followed the Prerequisite steps. I did NOT verify that I was on 20o firmware. "OR RISK BRICKING YOUR DEVICE" is right.
So I bricked my device, in exactly the way I was warned not to do, it seems.
Still, what's the next step? Any thoughts?
freeradical426 said:
Upon further reading, quite obvious, at the top of this thread, I definitely should have followed the Prerequisite steps. I did NOT verify that I was on 20o firmware. "OR RISK BRICKING YOUR DEVICE" is right.
So I bricked my device, in exactly the way I was warned not to do, it seems.
Still, what's the next step? Any thoughts?
Click to expand...
Click to collapse
try search for a fix if not may be @steadfasterX knows how to help you.
Re: searching for unbrick solutions
raptorddd said:
try search for a fix if not may be @steadfasterX knows how to help you.
Click to expand...
Click to collapse
Thanks, I have been looking around for solutions, but can't seem to find anything aside from the unbrick-guides that I've already listed / already attempted.
Will hope for help from @steadfasterX ! Or some other knowledgeable / benevolent party.
freeradical426 said:
Thanks, I have been looking around for solutions, but can't seem to find anything aside from the unbrick-guides that I've already listed / already attempted.
Will hope for help from @steadfasterX ! Or some other knowledgeable / benevolent party.
Click to expand...
Click to collapse
Ok what was the last KDZ file you flashed which had worked? 20o?
As you have hard bricked your device you can try the sdcard method again if it works flash 20o again (of it it was 20o).
If you flash a lower version you will hard brick again.
If the sdcard doesn't work anymore for you you can try to flash with QFIL but beware to use the right one. If you use the wrong one it will convert your device and believe me that's not what you want. I can share the good ones but unfortunately maybe on next week first.
Otherwise search on your own for 9008 unbrick but check the md5sum of the programmer!! Compare it with the Evil one mentioned in my ARB list here: http://tinyurl.com/antirollg4 and DO NOT USE THE EVIL one..
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Ok what was the last KDZ file you flashed which had worked? 20o?
As you have hard bricked your device you can try the sdcard method again if it works flash 20o again (of it it was 20o).
If you flash a lower version you will hard brick again.
If the sdcard doesn't work anymore for you you can try to flash with QFIL but beware to use the right one. If you use the wrong one it will convert your device and believe me that's not what you want. I can share the good ones but unfortunately maybe on next week first.
Otherwise search on your own for 9008 unbrick but check the md5sum of the programmer!! Compare it with the Evil one mentioned in my ARB list here: http://tinyurl.com/antirollg4 and DO NOT USE THE EVIL one..
Click to expand...
Click to collapse
Thanks very much for the guidance! The post that you linked to REALLY helps. Until now I really was not sure what 10n, 20i, 20o, etc. referred to, aside from just various software versions. Having a definition for anti-rollback and further links to explain, really helps! This gives me more information and I might be able to self-resolve from here. I will give it a shot.
As for your question ... unfortunately there was NO instance where I flashed a working KDZ file, and I didn't know (due to my past experience with my Nexus) that I needed to check the STOCK software version of my phone before beginning to play with ROMs. In other words, I have no idea if I was on 20i, 20o, 20p, etc. From what I understand, this makes things a lot more difficult
Having looked at the linked thread just a little bit, it appears that using a 20o KDZ is the best bet -- because I bricked my device using a 20i ROM so I expect it was due to violating the anti-rollback restriction.
I will look into it more closely and come back if I hit another brick wall. Thanks so much!
If anyone cares, here are the ending results of all this ...
#1 Be wary of anti-rollback restrictions before you flash anything to your G4. You WILL brick your phone!
I tried multiple rounds and multiple variations of all the MicroSD card methods that I could find. I could NOT succeed in unbricking my phone.
#2 Luckily ... I was able to convince LG that I was still technically under warranty!
Because I had the stock bootloop issue in May 2017, LG did an in-warranty repair for me, and replaced the motherboard. So last week, I simply told them "my phone is AGAIN unable to charge and will not power on, just like in May". Since it had only been 5-6 months since the first issue, they agreed to replace the motherboard again.
Moral of the story: you can definitely unbrick your phone by having LG replace the mobo XD XD
From here, I think I will just totally avoid doing any rooting or custom ROMs on my totally-stock G4 coming today in the mail. I will cross my fingers and hope we get OEM Nougat in the USA sometime in the next couple of months.
Thanks again for the help everyone!