Help!!! My phone is messed up badly - AT&T HTC One (M8)

To make it short, my phone is all messed up. Whatever I try to flash I get errors and can't get it back to stock. I don't know what else to do. Totally frustrated. AT&T HTC One M8. I've been trying to RUU the phone but I keep messing it up even further
I really need help.
I use a mac and have windows 8.1 via VM Ware.
Does anyone know where I can get help in Miami?
Thanks.

EDIT: crap, I edited (deleted) my previous post when I meant to post an additional response.
Basically my previous post suggested that the OP stop cross-posting, as he has now started 2 threads for basically the same issue, in addition to similar posts on a few other existing threads. Jumping around makes it very confusing to try to help. Sticking to 1 thread also allows a more chronological/sequential troubleshooting process.
Also, if you want proper help don't "make it short". Make it long, give as much detail as possible. In particular the following ingo is needed: S-on or s-off, what recovery and version, what ROMs did you try to flash.
One suggestion would be to try wiping cache, and re-installing recovery, using the latest version. It might be as simple as a faulty recovery installation.
Also, Win8.1 does not work at all with the RUU. HTC drivers do not play well with 8.1 even with a "real" Win8.1 machine. I can only imagine that using VMWare would cause even more issues. If you want to run the RUU, you will need Win8 or lower (preferably Win7 or even XP) and probably a "real" Win PC is best.
_______________________________________________________________
And this was intended as my subsequent post:
So the OP clicked "thanks" for my post, but did not respond. Did you try anything that I suggested? Any change in status? You didn't bother providing any of the info I requested.
I really feel you are going about this the wrong way.
Stick to one thread. Provide the info requested, and allow us to walk you through the troubleshooting process.

Related

Question on Rooting and Unlocked Phones

Hey guys, long time browser, first time poster. I just recently purchased a Telus Hero and I want to root it to be able to go to 2.1. The thing is, I don't know if I should update the radio or not. The phone is unlocked and I need the phone unlocked to be able to use it. If I update the radio, will my phone stay unlocked? Also, any guides for rooting a Telus Hero on Windows 7 x64?
Welcome to the forums pal.
OK,... 1st of all,... updating the radio will have NO effect on the network lock.
It is not always necessary to update the radio, but it is recommended to have the latest one. However, if it does cause adverse effects, you can always return back to a previous one.
Use BTDAGs guide linked in my signature, it is not Telus specific but you should be fine.
BTDAG has also done a guide on sorting drivers for 64bit systems so you may have to use both guides in conjunction with one another,...
Let me just say though,... I struggled with Win7 x64,... ended up using an old XP machine in the end.
Here you go,...
[Guide] How to Setup Correct Hero Drivers (for x86 & x64 users)
ddotpatel said:
Let me just say though,... I struggled with Win7 x64,... ended up using an old XP machine in the end.
Click to expand...
Click to collapse
I know many people have said they've had problems with Win 7 x64. However, I just (finally) rooted my Hero (It's a Telus Hero, but I'm using it on AT&T, so it's unlocked) the other day and installed a 2.1 ROM with no issues on it, so sometimes you can get lucky.
PS - I have a quick question while we're on the topic of the radio. In going through the whole goldcard/downgrade process, I installed the IU version of the radio. So far, I haven't noticed any problems. Is there any noticeable change in the OU version of the radio for the North American Hero, specifically on AT&T (if anybody can answer that). Is it worth updating, or since I don't seem to be having any issues, should I stick with IU?
Oh great. While I do have access to a Windows XP machine, I prefer 64-bit. Oh well. What problems did you have anyway?
Thanks for that guide, though. You always hope for that nice first-time experience on a forum and when you get it, it feels great. I just got it.
bjg222 said:
PS - I have a quick question while we're on the topic of the radio. In going through the whole goldcard/downgrade process, I installed the IU version of the radio. So far, I haven't noticed any problems. Is there any noticeable change in the OU version of the radio for the North American Hero, specifically on AT&T (if anybody can answer that). Is it worth updating, or since I don't seem to be having any issues, should I stick with IU?
Click to expand...
Click to collapse
As far as I know it is recomended to always have the latest radio,... But if you do think the change has decreased signal strengths then it is simple to roll back again.
arcblade851 said:
Oh great. While I do have access to a Windows XP machine, I prefer 64-bit. Oh well. What problems did you have anyway?
Click to expand...
Click to collapse
I think it was the downgrade bit that kept freezing and it just didn't want to do anything,... But I'm not too sure to be honest, t'was a little while back now. ...I was later told that updating my drivers may have helped,... So you could have a bash to see if it works.
BTDAG has also done a guide on setting up drivers,... should be on pg1, 2 or 3 of the Development section.
Wouldn't you know it, the downgrade process won't go past the bootloader. Time to move onto XP. Thanks!
Whoo! Finally flashed it to a pre-rooted vanilla 2.1 ROM. Any suggestions on what I should flash to now? And what about Nandroid?
Iv just finished setting mine up again. Villain10.2. Working beautifully.
You could do a nandroid backup now but your on a clean slate, no need.
Thanks for the advice. One more thing, though. Does Nandroid run in the recovery menu, and is the backup stored in the phone's memory?

[GUIDE]Complete Guide to Obtain S-OFF, Flash Recovery, and Install ROOT for the EVO3D

Hello everyone,
I wanted to take some time today to make a very clear and concise guide on how to complete the root process for the EVO3D. I understand that there is at least one other floating around at this point. If you don't have a firm grasp of how all of this works though, you may run into problems or have questions. I commissioned my guide to try and add clarity to the process and to also teach our communities newest members some of the ins and outs of modding our phones. The guide is far too large to post in a thread, therefore I've created a PDF of it and am offering it for download.
Feel free to mirror my guide and provide me with the link so that I can add it below.
Below is a Preface and Contents of the Guide. Feel free to ask questions or address any concerns you may have as I will be revising the guide.
The Complete Guide to Obtain S-OFF, Flash Recovery, and Install ROOT for the EVO3D
Authored by: sidepart of the
XDA-Developers Forum
Revision 1.1 - Published July 30, 2011​
Preface
Prior to reading this document, please be aware that as a disclaimer, I am not responsible for anything that goes wrong in this guide. Some people will run into issues that others do not. This is especially true with the differing versions of the Android-SDK. Some advanced users are using an older version which uses different commands than are offered by the latest Android-SDK. I encourage you to ask questions and keep an open mind. Try to understand the commands that are given here, and how you might have to be flexible in changing them to work for your situation. If at any time you are not comfortable with this process I highly recommend seeking out assistance from a more knowledgeable friend.
What this Guide Assumes
I assume that you will be downloading the latest version of the Android SDK which at the time of this document’s creation is R12. I also assume that you are using Windows 7, but this translates very easily into Windows Vista or XP.
Disclaimer
I am not responsible for any problems or fatal errors that may or may not occur through the process of performing the instructions of this guide. If at any time you are not comfortable with this process I highly recommend seeking out assistance from a more knowledgeable friend.
Contents of this Guide
What is S-OFF, Recovery and Root?
It’s not Just “ROOT”. Getting Past Outdated Nomenclature.
When I Say, “Do this”, Perform the Following Steps
Going to HBOOT
Booting into Recovery
Enabling USB Debugging
Install the Android-SDK
Obtaining S-OFF Status
Obtaining “unrevoked & AlphaRev’s: Revolutionary S-OFF & Recovery Tool”
Common Questions
Running “unrevoked & AlphaRev’s: Revolutionary S-OFF & Recovery Tool”
Common Questions
Flashing a Recovery Program
Flashing the TeamWin Recovery Project Recovery Program
Flashing or Installing the Superuser Management Program (Root)
Conclusion
Acknowledgements
Click Here to Download
Changelog
Revision 1.1 - July 30, 2011
Fixed some glaring grammatical and spelling errors.
Added a Common Questions section under item 4b.
Added a common question to 4b,i. It instructs users on how to paste their Beta key-code into the Revolutionary EXE program.
Fixed some formatting.
Used your guide and had no problems thank you!
Have not used it yet but this is very helpful... will be rooting my wifes e3d tonight... wasn't going to do it off of the other thread... I had no idea what it was talking about. Thanks for taking the time to put this together
Sent from my SPH-D700 using XDA App
Kind of hilarious to see my access.log right now. Lots of people looking at the guide interspersed with a few people discovering my site's index.html.
Used your guide and almost worked flawlessly The only problem I had was flashing the TeamWin recovery with the following command: ..\tools\fastboot.exe flash recovery recovery-twrp-shooter-1.0.0.img
The img that I downloaded through the site was like 1.0.1, but the error was on my end. Otherwise awesome guide!
So much info!!! love it.. nice
Sent from my PG86100 using www.psvitahacks.co app
bryangene said:
Used your guide and almost worked flawlessly The only problem I had was flashing the TeamWin recovery with the following command: ..\tools\fastboot.exe flash recovery recovery-twrp-shooter-1.0.0.img
The img that I downloaded through the site was like 1.0.1, but the error was on my end. Otherwise awesome guide!
Click to expand...
Click to collapse
I think they may have updated since I first published. I might see if I can emphasize that you're supposed to use the downloaded filename in the command.
Excellent guide!
Sent from my PG86100 using XDA Premium App
Lovely guide! for those who get
E:Error in /tmp/sideload/package.zip
(status 0)
just reflash su >_>
zander145 said:
Lovely guide! for those who get
E:Error in /tmp/sideload/package.zip
(status 0)
just reflash su >_>
Click to expand...
Click to collapse
I actually tried to load the zip from http://goo-inside.me/superuser and it wouldn't work. Retried it quite a few times and got the same error. I found an unsigned version of it in clark44's guide and that one worked just fine. Not sure what the problem was, hence my recommendation to grab superuser from the market and follow it's instructions instead. Seems to be working out well.
I think I might add something about this to the guide if too many people are running into the problem.
Any problems with not being able to send/recieve calls/texts with this? Haven't really messed around too much with the girlfriend's phone b/c she's terrified of not being able to get calls and what not..
I know this is a beta setup for now, so i'm assuming it'll turn into a simple one click type of thing when it gets to that point..?
Edit: I went through all this on my phone and had no problems really except having to call Sprint ..
Followed the guide as instructed...revolution wont recognize my device...it just hangs on waiting for device. I double checked to ensure usb debugging was enabled but it just hangs there.. Again i did follow the guide from step 1 and this is where im at...any suggestions?
SBERG117 said:
Followed the guide as instructed...revolution wont recognize my device...it just hangs on waiting for device. I double checked to ensure usb debugging was enabled but it just hangs there.. Again i did follow the guide from step 1 and this is where im at...any suggestions?
Click to expand...
Click to collapse
I would take a look at the documentation for the Revolution EXE, it could shed some more light on the situation that you're experiencing. Off hand though, I do have some recommendations.
Do you have HTC sync installed? I was reading around and found that this was causing an issue with the revolution program. Try removing that first.
If that's not the case and this still isn't working, there could be a driver conflict with some previously installed android drivers on your system. To clear that up, I would recommend grabbing the latest HTC drivers mentioned in the Revolution documentation. This is the most recent link that I've found: http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
The process may require you to manually remove the old drivers and manually install the new ones. If you're not certain of how to do this, it's beyond the help of my guide. I would encourage you to look up the process online or ask a friend to show you.
Hope this helps!
Neogenx said:
Any problems with not being able to send/recieve calls/texts with this? Haven't really messed around too much with the girlfriend's phone b/c she's terrified of not being able to get calls and what not..
I know this is a beta setup for now, so i'm assuming it'll turn into a simple one click type of thing when it gets to that point..?
Edit: I went through all this on my phone and had no problems really except having to call Sprint ..
Click to expand...
Click to collapse
The only related issue that I've come across is the "Error 16" when provisioning the phone after s-off. As you found, this usually fixed with a call to Sprint. I'll never say, "never" though. Be aware that making modifications to the phone always carries with it an inherent risk, however small or unlikely. The risk of course is part of what makes it fun, but girlfriends (mine) seem to seldom understand this.
If the root method is ever released, there is potential for it to become more of a one-click procedure, but I don't think there's a guarantee of course.
Thanks for the guide!
I'm stuck though!
The Revolutionary Command Window says:
"Waiting for fastboot..."
And my phone rebooted into the HBOOT screen but it shows: S-ON
What should I do?
Is this in your guide?
1. Install drivers: http://www.multiupload.com/2OFYWZFCCR
2. Put phone in full boot, usb debugging on , charge only.
3. Uninstall HTC Sync if installed.
4. Profit.
sidepart said:
I would take a look at the documentation for the Revolution EXE, it could shed some more light on the situation that you're experiencing. Off hand though, I do have some recommendations.
Do you have HTC sync installed? I was reading around and found that this was causing an issue with the revolution program. Try removing that first.
If that's not the case and this still isn't working, there could be a driver conflict with some previously installed android drivers on your system. To clear that up, I would recommend grabbing the latest HTC drivers mentioned in the Revolution documentation. This is the most recent link that I've found: http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
The process may require you to manually remove the old drivers and manually install the new ones. If you're not certain of how to do this, it's beyond the help of my guide. I would encourage you to look up the process online or ask a friend to show you.
Hope this helps!
Click to expand...
Click to collapse
Updating the driver worked..im good to go now.. thnx..

OX+ need help flashing.

Ok, you know, today I got my phone, I had been waiting forever, I got it and within 2 hours I screwed it up. I have followed and followed many forums and posts on how to fix this, and I am just.. lost. So please i need your help, I am seriously stressing out, and I know I shouldnt, but this is my first android phone. I am shot right now.
I had unlocked the bootloader, and then I tried to root it, then it rebooted and went into bootloop mode or whatever it is.
I still cannot figure out how to use this Hasoons2000's OX+ AIO kit. So I am just leaving it alone.
Ok the PC doesn't recognize it as a storage device, but the fastboot does recognize it, as I have executed a few commands, like reboot or something, just to test that it works.
My phone is ATT but I am in Russia so there is no sending this anywheres. All I want to do is reboot the OS and have it work again, I dont care what mod or stock rom it is, I just really need some direction here.
I know something about RUU, ATT RUU, Fastboot, some other stuff, I have like 5 pages on XDA pulled up and I cant figure this out.
What is the CMW or TWRP or whatever it is called? How do I flash a zip or an img to the phone? I really just want my phone on again.
Yes Ive done stupid noob stuff, but you learn. So please I am kindly asking for any assistance,
No need to stress. Its fairly hard to brick your phone, good way to learn quick also is to screw with it.
Just need the right guide and I think this will help you since u have fastboot access hopefully. Its a pain rebuiling so read everything so u only have to do it once.
Remember these guides are for different phones so don't use the ruu or recovery links, user my links below.
Your phone is:
AT&T(Evitare)
This guide:
http://forum.xda-developers.com/showthread.php?p=30863908
Or this guide:
http://forum.xda-developers.com/showthread.php?p=27301573
This is for another phone so you need to choose an ATT ruu from here for step 1:
Your phone is a HTC One X+ for AT&T(Evitare)*
http://www.androidfiles.org/ruu/?developer=EvitaRE
More info here for custom recoveries etc which is cwm and twrp for deploying roms, backing up your current installed Rom and general tools for fixing or enhancing your phone, displayed prior to your phone booting into android:
http://forum.xda-developers.com/showthread.php?p=37778531
Sent from my HTC One X+ using xda premium
somemadcaaant said:
No need to stress. Its fairly hard to brick your phone, good way to learn quick also is to screw with it.
Just need the right guide and I think this will help you since u have fastboot access hopefully. Its a pain rebuiling so read everything so u only have to do it once.
Remember these guides are for different phones so don't use the ruu or recovery links, user my links below.
Your phone is:
AT&T(Evitare)
This guide:
http://forum.xda-developers.com/showthread.php?p=30863908
Or this guide:
http://forum.xda-developers.com/showthread.php?p=27301573
This is for another phone so you need to choose an ATT ruu from here for step 1:
Your phone is a HTC One X+ for AT&T(Evitare)*
http://www.androidfiles.org/ruu/?developer=EvitaRE
More info here for custom recoveries etc which is cwm and twrp for deploying roms, backing up your current installed Rom and general tools for fixing or enhancing your phone, displayed prior to your phone booting into android:
http://forum.xda-developers.com/showthread.php?p=37778531
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
thank you very much I really appreciate your help. I finally figured out the ruu.exe thing, I didnt know they had to be the same numbers, ex 1.15.xxx.xx or whatever.
You see what happened originally was that I unlocked the bootloader, easy pie, but I tried to root it and that is when it started looping. Maybe I didnt understand something, but I seemed to have messed up right there.
Is there really any reason to root? I mean yeah there is super user, but doesnt bootloader help with that a bit? I know BL is for flashing custom roms and all.
May I ask how to flash a custom rom? I really want all of this ATT stuff off of my phone, I really dislike it.
Yes I know I can search, here, google etc. And maybe I should, but I end up getting so many different results, and here and there, and this and that. It really is just easier to talk to one single person who knows what they are doing. So if you could help me, I would again extend my appreciation.
Also I have the android revolution for ox+, and I dont know if it is.. you know.. THE BEST or not. Dont know what to do.
And yes, you live and learn, took me forever with iphones, then I realized hacking and roms and stuff were completely different from iphone. So new game new story.

lg l9 p769 - droid 4.0.4 - i'm lost, could use help, linux user

i have been seeing a lot of threads about rooting this phone, but, they all have windows scripts, even the thread that is said to have a runme.sh does not have it in any of the links that i unzipped - only a runme.bat, but yet, people keep mentioning a runme.sh in it... also, i really don't see any one lying out the steps for doing this with linux.
i'm a noob, and dont really know much about this stuff, but i've done this ONCE before with a galxy exhibit, but it was very easy, i just copied a file to the phone (stock rom?), rebooted into recovery, told it to recover from that file, and i was done.
i have no idea how to do it with my new phone, and so i'm wondering:
1: where can i find the files i need to do this with linux - i just want root, nothing special
2: where can i find the steps necessary to do it - in the easiest manner possible?
3: it says i have droid 4.0.4, ICS, but every one who talks about lg l9 p769 says its JB, so, thats a bit odd...
any help is appreciated.
sentientsystem said:
3: it says i have droid 4.0.4, ICS, but every one who talks about lg l9 p769 says its JB, so, thats a bit odd...
Click to expand...
Click to collapse
Your phone is running ICS 4.0, that is the version which it shipped with. Pretty much everyone on here has upgraded to JB either with software update on the phone or they have manually updated with the offline KDZ flash method.
I dont have any experience in linux so I cant help. I hope you can get your phone rooted!
Sent from my LG-P768 using xda app-developers app
i just started to restart my phone into recovery mode to see if i could put cyenogenmod on it without having to root it first, and it's saying "software upgrade ... please wait while upgrading...", so, i guess it's upgrading to JB right now... i'll see shortly.
but even if it does upgrade to JB, i still wouldn't know how to do it on linux. i figured there would just be some files to download, and a sequence of adb commands that i could type into bash, but, i'm kinda lost. i guess i'll wait and see if it upgrades to JB before asking more questions.
thanks.
sentientsystem said:
i just started to restart my phone into recovery mode to see if i could put cyenogenmod on it without having to root it first, and it's saying "software upgrade ... please wait while upgrading...", so, i guess it's upgrading to JB right now... i'll see shortly.
but even if it does upgrade to JB, i still wouldn't know how to do it on linux. i figured there would just be some files to download, and a sequence of adb commands that i could type into bash, but, i'm kinda lost. i guess i'll wait and see if it upgrades to JB before asking more questions.
thanks.
Click to expand...
Click to collapse
You would need wine and then set it up...
Sent From My Xperia Themed P769
well, i tried that "LGpwn" and it didn't work, as well as a fake lg-recovery app. i figured out that i've got a "10g" phone (P769 V10G ICS). i'm not sure what the next step is. some one mentioned downgrading to JB... is there some where you can point me to for that???
i've GOT to get this t-mobile junk off my damned phone... i've even TRIED to install cyenogenmod, but i can't figure out how to get my phone to go into recovery mode (NOT factory rest) - i've tried volup+power+home and volup+power, and neither seem to be working.
Setup a sandbox, windows xp. LG uses windows, no other way to root as of right now for the t-mobile version.
Sent from my LGMS769 using xda app-developers app
yeah, it's starting to look like i'm gonna have to try this with a virtual machine, or, pay some one else to do it, or, go get my money back and downgrade to a samsung galaxy exihibit (not sure if the new model of that phone is just as easy as the exhibit 4g, but, it's screen is about an inch smaller than the lg, and they're all 3 the same price, so i'd rather keep the lg).
just out of curiosity, how do you get this phone to boot into recovery mode? you don't have to root it for that, or have windows, right? you just hit the right keys on the phone, right? i couldn't get it to work, but, maybe i was doing it wrong. and, if you can go into recovery, does it have to be rooted to use a cyenogenmod image, or will it not really know the difference?
thanks again. i'm sure this thread may help other noobs as well.
sentientsystem said:
yeah, it's starting to look like i'm gonna have to try this with a virtual machine, or, pay some one else to do it, or, go get my money back and downgrad to an samsung galaxy exihibit (not sure if the new model of that phone is just as easy as the exhibit 4g, but, it's screen is about an inch smaller than the lg, and they're all 3 the same price, so i'd rather keep the lg).
just out of curiosity, how do you get this phone to boot into recovery mode? you don't have to root it for that, or have windows, right? you just hit the right keys on the phone, right? i couldn't get it to work, but, maybe i was doing it wrong. and, if you can go into recovery, does it have to be rooted to use a cyenogenmod image, or will it not really know the difference?
thanks again. i'm sure this thread may help other noobs as well.
Click to expand...
Click to collapse
Option #1
If you are rooted on stock T-Mobile 10e or 10g ROM and have the CWM installed from this thread:http://forum.xda-developers.com/showthread.php?t=2095825 follow my instructions.
Place one of these CWM ROM images on your SD-Card:
http://forum.xda-developers.com/showthread.php?t=2136204
Place this JB radio firmware from T-Mobile 20d ROM on your SD-Card:
http://forum.xda-developers.com/showthread.php?t=2256350
Power off the device.
After power on the back/menu capacitive buttons will flash repetedly. Press Volume down while the lights are flashing and the phone should go into recovery.
Flash the ROM first.
Flash the radio second.
Reboot.
***Notes***
1.) 20d is the latest T-Mobile, 21b is the latest Wind Mobile. Both work.
2.) 21b is lighter/faster but has no wifi-calling.
3.) 21b will require you to manually enter your APN settings for cellular data and MMS. Be sure to write down your APN settings before flashing this ROM.
4.) Some users say battery life sucks on JB. I notice that 21b is better on battery life than 20d.
Option #2.
In Linux install a Windows VM and follow the standard instructions here:
http://forum.xda-developers.com/showthread.php?t=2173465
Use KVM with a GUI or even easier use VirtualBox.
I'm a die hard linux geek too. I even run linux at work while all of our msp software was written for windows. You are better off just running an old copy of xp inside virtualbox trust me its just easier that way. You can use adb if you like (its the same thing the windows users use in their batch files and just rewrite the bash script, but you will save yourself lots of headaches just using virtualbox. -- my .02
Sent from my LG-P769 using xda premium
i'm not exactly sure what the end result of your instructions are, as i assumed it was to BE rooted, but the first line of your post says "if you are rooted ...", so, i'm guessing you're telling us how to ... unlock the boot loader?
by the way, that reminds me, i still haven't come across any posts on this site that tell noobs:
# what's the unlocked boot loader FOR - why do you need this - what does it do?
# what's the difference between unlocked boot loaders and being rooted?
# do you have to unlock the bootloader to get root access?
all some one like ME needs, is root access, so that i can edit the /etc/hosts file and test mobile compatibility of web apps on the development server before making them live - and to remove t-mobile damned bloat-ware. i hope this helps others who are trying to understand the basic concepts of getting control over the phone they paid money for.
thanks again. now to find a winxp image to load into a virtual machine...
My bad. I should have read through your original question all the way before posting. I see that you are not rooted.
If you are on 10e ROM you can root in Linux:
http://forum.xda-developers.com/showthread.php?t=1990705
It will require rewriting the batch script as a Linux shell script. It is possible but nobody has done it yet.
If you are on 10g you will need Windows. I have also answered your questions below.
sentientsystem said:
i'm not exactly sure what the end result of your instructions are, as i assumed it was to BE rooted, but the first line of your post says "if you are rooted ...", so, i'm guessing you're telling us how to ... unlock the boot loader?
by the way, that reminds me, i still haven't come across any posts on this site that tell noobs:
# what's the unlocked boot loader FOR - why do you need this - what does it do?
It allows you to boot an un-signed kernel. You can boot custom ROMs basically.
# what's the difference between unlocked boot loaders and being rooted?
Root allows you to `su -` to the root user and own the whole system.
# do you have to unlock the bootloader to get root access?
No.
all some one like ME needs, is root access, so that i can edit the /etc/hosts file and test mobile compatibility of web apps on the development server before making them live - and to remove t-mobile damned bloat-ware. i hope this helps others who are trying to understand the basic concepts of getting control over the phone they paid money for.
thanks again. now to find a winxp image to load into a virtual machine...
Click to expand...
Click to collapse
yeah, the one t-mobile is selling now is a v10g - so, it's time to play with virtual machine, and hope that usb-access is passed through from ubuntu to the VM.
thanks for answering the other questions. i think this essentially sets things straight.
peace! \m/ (>_<) \m/
sentientsystem said:
yeah, the one t-mobile is selling now is a v10g - so, it's time to play with virtual machine, and hope that usb-access is passed through from ubuntu to the VM.
thanks for answering the other questions. i think this essentially sets things straight.
peace! \m/ (>_<) \m/
Click to expand...
Click to collapse
Welcome!
I know that a long time ago when I ran VirtualBox in Ubuntu there was something I had to do to allow USB access to the VM.
Here are the current instructions directly from Ubuntu:
https://help.ubuntu.com/community/VirtualBox/USB
Good luck.
hey, i've got 1 more quick question: is there a way to simply load a pre-rooted ROM onto it, like i did with my samsung? where you put it onto the device, the go into recovery mode and choose the pre-rooted ROM? i haven't seen any mention of that, so i'm not sure if that's an option...
also, how the hell do you make this boot into recovery mode? i still haven't been able to get it to do that?
thanks \m/ (>_<) \m/
sentientsystem said:
hey, i've got 1 more quick question: is there a way to simply load a pre-rooted ROM onto it, like i did with my samsung? where you put it onto the device, the go into recovery mode and choose the pre-rooted ROM? i haven't seen any mention of that, so i'm not sure if that's an option...
also, how the hell do you make this boot into recovery mode? i still haven't been able to get it to do that?
thanks \m/ (>_<) \m/
Click to expand...
Click to collapse
Yes you can flash a pre-rooted image. They are available. Use the search?
I posted instructions on the first page showing how to boot recovery.
that's great news - that's all i really needed - i didn't see them before, at least, not conspicuously, but i'll search around again.
and, i must have some how missed your instructions, i'll look again.
thanks!
kevev said:
I posted instructions on the first page showing how to boot recovery.
Click to expand...
Click to collapse
those steps assume i have CWM installed, and i don't. i looked at installing CWM, and it doesn't have an official recovery app for the p769, and when i went to look at that thread you linked to, it says you must be rooted already. this is the aggravating part of us ignorant people dealing with people who know many things: it appears to us that you have to do some thing that requires that it is already done before you can do it. it doesn't make any sense - just a bunch of circualar requirements, with no beginning.
so, let me ask this a different way: how do i reboot into recovery mode, on a STOCK LG P769 v10g? the lights do not flash, and i'm assuming that is a CWM feature - but CWM is not installed - this is COMPLETELY STOCK - fresh out of the box. so, what do you press, when turning it on, to make it go into recovery mode, so that you can recover from a pre-rooted rom (which i am still looking for)?
i just want to "recover" to a pre-rooted rom, that's it, so that i can delete bloatware and edit the /etc/hosts file (for web app testing). this thread says you cant do this for LG phones http://forum.xda-developers.com/showthread.php?t=2174767 - i got the same result the last guy got . trying to borrow a windows computer now...
also, does any one know if it is safe to put a jelly bean rom onto a device that was using ice cream sandwich? is there a difference between the versions that would brick the device? is it not recommended, or is it highly recommended?
thanks again. sorry for all the confusion.
you know, as a side note: it may help more noobs understand this stuff if there was a sort of simplified glossary, perhaps as an official site thread, for the orientation of noobs, that would give an outline of the basic concepts, AND their order of operation. exmaple: "rooting is when you... bootloader unlocking is when you... CWM is for people who want to... you MUST do A before you can do B and then you can optionally do C if so desired...". that would help them understand where to START, then, where to GO next.
well, borrowed a windows computer and i got it rooted, but, i found out a few things about this exact model: it has no "boot to recovery" option, by default - it's locked down pretty good. you can not use any of the other root methods on this model, and you can not do it from linux (f*ck me).
so, that long-winded fake-software-update-while-switched-out-a-hex-edited-binary-file is the ONLY way for this exact model, it seems...
but, at least i can confirm that this exact model CAN be rooted at all
now to remove alllllllll the bloatware... and look into this CWM more and learn more about what is actually IS and WHY so many people install/use/flash it...
hey, does any one know if cyenogenmod ever got themselve's an "app/marketplace"??? that was one of the draw-backs to installing it, last i checked.
thanks @everyone for your help.
sentientsystem said:
those steps assume i have CWM installed, and i don't. i looked at installing CWM, and it doesn't have an official recovery app for the p769, and when i went to look at that thread you linked to, it says you must be rooted already. this is the aggravating part of us ignorant people dealing with people who know many things: it appears to us that you have to do some thing that requires that it is already done before you can do it. it doesn't make any sense - just a bunch of circualar requirements, with no beginning.
so, let me ask this a different way: how do i reboot into recovery mode, on a STOCK LG P769 v10g? the lights do not flash, and i'm assuming that is a CWM feature - but CWM is not installed - this is COMPLETELY STOCK - fresh out of the box. so, what do you press, when turning it on, to make it go into recovery mode, so that you can recover from a pre-rooted rom (which i am still looking for)?
i just want to "recover" to a pre-rooted rom, that's it, so that i can delete bloatware and edit the /etc/hosts file (for web app testing). this thread says you cant do this for LG phones http://forum.xda-developers.com/showthread.php?t=2174767 - i got the same result the last guy got . trying to borrow a windows computer now...
also, does any one know if it is safe to put a jelly bean rom onto a device that was using ice cream sandwich? is there a difference between the versions that would brick the device? is it not recommended, or is it highly recommended?
thanks again. sorry for all the confusion.
you know, as a side note: it may help more noobs understand this stuff if there was a sort of simplified glossary, perhaps as an official site thread, for the orientation of noobs, that would give an outline of the basic concepts, AND their order of operation. exmaple: "rooting is when you... bootloader unlocking is when you... CWM is for people who want to... you MUST do A before you can do B and then you can optionally do C if so desired...". that would help them understand where to START, then, where to GO next.
Click to expand...
Click to collapse
I've decided to help you out This page will give you some more info on the P769 and several kdz (roms) for the P769
The fastest way to root is to flash the V21B kdz (this is the Jelly Bean version for Canada) using this guide, http://forum.xda-developers.com/showthread.php?p=36351786
The reason why you want this rom is because it has a vulnerability that is easy to exploit with Jcase apk
Once your followed everything (and rooted), install Super Su and Busybox
Next install artas182x second init CWM (in case you can't find it on his page, the link is here )
Note: you will see blinking led lights when you see the LG logo (booting up) appear after a couple of seconds. To enter the CWM press the vol (-) when the lights start flashing.
After you installed Artas182x CWM you can recover from someones clockworkmod backup.
following info from Cmahendra's thread
Note: only restore CWM backups from P769 versions or MS769!!!!
Or check out the V10B (MetroPCS "JellyBean") CWM backup
Now the only 2 reasons to unlock the bootloader are:
1. Install a safer and better CWM
The reason why is because Artas182x CWM is a second init (bootstrap), so if you mess around with a busybox apk and something goes wrong or you remove a file that is required (for CWM), it will stop operating. You will have to reflash the kdz or fix what you changed to get it working again.) I've had this problem several times while messing around with different busybox apps and etc.
2. Custom roms
(which you stated you are not looking for) not worth talking about right now.
Answer to questions
The only pre rooted roms are clockworkmod backups, lol
The default recovery is useless to us (unless you feel like solving the problem)
Flashing back and forth (ice to jelly) comes with risk, the program used on Windows to flash is buggy at times. The best way (in my opinion) is to flash only when really required and mostly restore from clockwormod backups. The device is actually hard to hard brick, but it will require at lot more knowledge to get your device running again.
---------- Post added at 07:23 PM ---------- Previous post was at 07:16 PM ----------
sentientsystem said:
well, borrowed a windows computer and i got it rooted, but, i found out a few things about this exact model: it has no "boot to recovery" option, by default - it's locked down pretty good. you can not use any of the other root methods on this model, and you can not do it from linux (f*ck me).
so, that long-winded fake-software-update-while-switched-out-a-hex-edited-binary-file is the ONLY way for this exact model, it seems...
but, at least i can confirm that this exact model CAN be rooted at all
now to remove alllllllll the bloatware... and look into this CWM more and learn more about what is actually IS and WHY so many people install/use/flash it...
hey, does any one know if cyenogenmod ever got themselve's an "app/marketplace"??? that was one of the draw-backs to installing it, last i checked.
thanks @all for your help.
Click to expand...
Click to collapse
So what version are you on right now
Ice? Jelly?
i'm still on ICS for the moment. still trying to understand what i need to do next. re-reading your post for the 2nd time, and all the threads it references. making sure i don't screw any thing up. thinking about upgrading to JB, and trying this CWM. and looking into this "cyanogenmod" some more, to understand why i never see any one on this site mention it, and what all these "other roms" are about. lmao, like i said, i'm way new to this . it's a lot to take in, even for a web developer .
thanks \m/ (>_<) \m/

Ugh. Can't believe I'm making this thread

I'm on a Kindle Fire HDX 7" that originally ran GGOW's older roms and safestrap.
I am now trying to put CM12 on the unit and have brought it back to factory specs.
I am version 3.2.5 firmware
I have tried to downgrade by placing older version firmwares on the kindle root and running the manual update.....this leads to 'verify failed' error.
I have been reading this site for 2 weeks to find the proper method for downgrading and haven't been able to accomplish it yet.
I am on a Mac, not Windows.
Reaching out to the community in general, I've tried to help myself and not bother anyone, I'm not succeeding.
Thanks for your generosity beforehand.
-John
Follow the instructions in this post: http://forum.xda-developers.com/showthread.php?p=55759790
EncryptedCurse said:
Follow the instructions in this post: http://forum.xda-developers.com/showthread.php?p=55759790
Click to expand...
Click to collapse
.bat file = WINDOWS
But at least we're getting somewhere, thank you!
johnwaters said:
I'm on a Kindle Fire HDX 7" that originally ran GGOW's older roms and safestrap.
I am now trying to put CM12 on the unit and have brought it back to factory specs.
I am version 3.2.5 firmware
I have tried to downgrade by placing older version firmwares on the kindle root and running the manual update.....this leads to 'verify failed' error.
I have been reading this site for 2 weeks to find the proper method for downgrading and haven't been able to accomplish it yet.
I am on a Mac, not Windows.
Reaching out to the community in general, I've tried to help myself and not bother anyone, I'm not succeeding.
Thanks for your generosity beforehand.
-John
Click to expand...
Click to collapse
Hi John, sorry for your troubles. See link provided by EncryptedCurse. Some thoughts:
- make sure you have a valid update-kindle-13.3.1.0_user_310079820.bin. Download it again. Look for a way to verify the MD5 both on your HDX (Hash Droid works) and on your Mac. MD5=0F2BC5278C057E7A6B4823B0F68D0727
- make sure OTA is reenabled following the same process/procedure used to disable (obviously turn off WiFi and remove all profiles)
- look through the batch file using a text editor. You are probably going to have to issue the ADB commands manually. But you're probably beyond that by now ...
- you may want to consider manually upgrading to 3.2.6 (if it takes) and then rolling back. Point of this excercise to to possibly repair any components that may have been altered while bringing it back to factory specs. There's some risk in this approach; need to think/talk through it.
Sorry if none of the above seems very helpful. Not really sure what's going on based on the symptoms. Hopefully someone else chimes in with a better solution.
Davey126 said:
Hi John, sorry for your troubles. See link provided by EncryptedCurse. Some thoughts:
- make sure you have a valid update-kindle-13.3.1.0_user_310079820.bin. Download it again. Look for a way to verify the MD5 both on your HDX (Hash Droid works) and on your Mac. MD5=0F2BC5278C057E7A6B4823B0F68D0727
- make sure OTA is reenabled following the same process/procedure used to disable (obviously turn off WiFi and remove all profiles)
- look through the batch file using a text editor. You are probably going to have to issue the ADB commands manually. But you're probably beyond that by now ...
- you may want to consider manually upgrading to 3.2.6 (if it takes) and then rolling back. Point of this excercise to to possibly repair any components that may have been altered while bringing it back to factory specs. There's some risk in this approach; need to think/talk through it.
Sorry if none of the above seems very helpful. Not really sure what's going on based on the symptoms. Hopefully someone else chimes in with a better solution.
Click to expand...
Click to collapse
Actually I'm just glad anybody responded at this point. I've done this so many times and am not a noob or a layman to the process, I just feel like one right now. I will go over everything you have pointed out with a fine-toothed comb. Again, thanks for your reply and suggestions, they are HIGHLY appreciated.
johnwaters said:
Actually I'm just glad anybody responded at this point. I've done this so many times and am not a noob or a layman to the process, I just feel like one right now. I will go over everything you have pointed out with a fine-toothed comb. Again, thanks for your reply and suggestions, they are HIGHLY appreciated.
Click to expand...
Click to collapse
We have all been there at some point. I appreciate the work done prior to reaching out; so many come begging for help without making an effort to help themselves. As a double check, make sure you are following the rollback procedure for 3.2.5-3.2.6 vs 3.2.4. If you are messing with build.prop directly you got the wrong procedure.
Davey126 said:
We have all been there at some point. I appreciate the work done prior to reaching out; so many come begging for help without making an effort to help themselves. As a double check, make sure you are following the rollback procedure for 3.2.5-3.2.6 vs 3.2.4. If you are messing with build.prop directly you got the wrong procedure.
Click to expand...
Click to collapse
Hi Davey and John,
Not having done this I don't have any real world experience, but could it be that the permissions need to be changed?
see post #36 here
Regards,
Kico
johnwaters said:
.bat file = WINDOWS
But at least we're getting somewhere, thank you!
Click to expand...
Click to collapse
You can always use a virtual machine or Wine.
On a side note, the script itself is adaptable for OS X, as it's really just executing a few ADB commands.
I'm not exactly sure what the Mac equivalent for 7z.exe would be, but all it does is extract a few files from the stock image, which can be done manually.
kico42 said:
... could it be that the permissions need to be changed?
see post #36 here
Click to expand...
Click to collapse
Yes, quite possible. I'm hoping that isn't the case as build.prop should not have been touched. If permissions do turn out to be the problem then it would be best if someone else helps with the solution. I know just enough about Android permissions to be dangerous ... certainly not confident enough to guide another given the disastrous consequences of screwing it up. Also possible permissions on the bin file are farkled ... but that seems very unlikely and easily remedied by deleting & recopying the bin file.
EncryptedCurse said:
You can always use a virtual machine or Wine.
On a side note, the script itself is adaptable for OS X, as it's really just executing a few ADB commands.
I'm not exactly sure what the Mac equivalent for 7z.exe would be, but all it does is extract a few files from the stock image, which can be done manually.
Click to expand...
Click to collapse
In the process of building a Windows VM right now. Again, thank you for all the help. This is the best community.
I make this post at 8PM and upgrade is completed 11pm.
THANK YOU XDA.

Categories

Resources