Hello everyone, first off, I read these two posts in their entirety:
http://forum.xda-developers.com/showthread.php?t=1009969
and
http://forum.xda-developers.com/announcement.php?f=943
I apologize if this might not be the best forum to post in, but as I just signed up I didn't have enough posts to post in the first thread like other people.
So I kinda have a good understanding of what I need to do with my phone, but need someone to recommend the best thing for me to do to change my firmware to 6.05.6 or 6.05.9, so allow me to share my rooting experience:
First off, I am running Windows 7 64-bit and I have never rooted a phone before and my Thunderbolt was my first droid device that I got 5 days ago on April 2nd, but I have plenty experience with flashing firmware for other devices such as routers, DVD drives etc. Initially I was not going to bother rooting my phone because of how complicated it looked, but then I found the one-click method and was becoming increasingly annoyed by not being able to get rid of the bloatware such as the Blockbuster app, Bitbop, Lets Golf 2, Rockband, Peep, and a couple others, so I decided to give the one-click method a shot.
Initially I had an issue with the ADB driver as Windows failed to install it successfully, after many agonizing minutes and a couple forums later, I installed HTC Sync and that fixed the issue, so now my batch file was working thus far. My second problem was the hbooteng.nb0 file. I had extracted the files from the exploits.zip correctly to the platform-tools folder, but my mistake was that instead of using the RUU filed and renaming it for the first flash, I initially flashed it with the one that was already name PG05IMG, so basically I thought I had done it correctly until I ran into the hbooteng.nb0 issue and realized I had flashed with the wrong file, leaving my phone basically unchanged and unrooted, but working perfectly fine.
Sooo I started over, this time knowing for sure I was using the correct files, and the process went pretty smoothly and the oneclick method told me my phone was rooted and to install the SU and ROM Manager so I did. Also did the clockworkmod thing as well.
But here is where my current problem is: My firmware is the 605.10 version and I would like it to either be back at the stock 605.6 or the newer 605.9. My phone works modestly well with the 605.10 so far EXCEPT it isn't correctly detecting my location. I live in Indiana, but the clock keeps setting itself to Rio de Janeiro. Also if I try to use Google Earth and do "find my location" with the GPS enabled, it takes me to Rio de Janeiro!
So here is my question: Which method of getting to the 605.6 or 605.9 firmware is the safest for me to use? And will using the one-click batch file to flash to either of those firmwares be safe since in the beginning it says that method does not work unless it is already at 605.6 or 605.9? Or should I attempt to do the option of factory resetting my phone through the SDcard settings, and what will I lose, and will I be back at 605.6, OR am I somehow supposed to use the ROM Manager app to flash to 605.6 or 605.9?
Many thanks in advance!
Ok so I ended up using ROM Manager and flashed to the 1.12.605.06 and it worked successfully but now my phone is no longer rooted since the ShootMe app doesn't work.
Related
So this was sort of a 3 part process that I need to detail to see if anyone has any clues on how to help. I tried to search the forums but had no luck coming across anything. Basically here is what I did, as I'm using a Mac I took a back door route.
1. Rooted phone using UnRevoked3. This worked fine I was using it for a day or two but then wanted to install Cyanogenmod so I could use Froyo. I wasn't able to install and it appeared the consensus was that the way unrEVOked works does not allow the proper access to install cyanogenmod. According to theunlockr.com/2010/07/20/how-to-root-the-htc-evo-4g-unrevoked-method/ it appeared that after installing unrevoked one still needed to unlock the NAND as seen here theunlockr.com/2010/07/20/how-to-unlock-nand-on-the-htc-evo-4g/
2. As this process did not work on Mac I scoured the forums and found this process forum.xda-developers.com/showthread.php?t=705113 and went through all the steps. Everything worked fine until the end when I installed the Radio an then the ROM (this was backwards from their instructions, ROM then radio which may have cause the problem). Regardless I ran Radio update, but then didn't reboot and installed Cyanogenmod update linked to from here forum.xda-developers.com/showthread.php?t=729367&highlight=brick
3. Everything appeared to work fine. After installing Cyanogenmod it asked if I wanted to reboot. I said yes, it said updating radio then rebooted. This may have been where I made the true mistake. It gave me a thing with an exclamation point after rebooting. At this point I waited for a little while then tried restarting, I took the battery out and tried to press a button. After this it wouldn't turn on. Am I totally screwed? My guess is that I probably am and feel like a total moron... Please let me know if there is anything worth doing...
Thanks,
Greg
also http portions were left out of links due to the fact that xda won't let me post links as a new member
When I first got my S2 I rooted it to remove some bloatware like orange backup and maps. I was looking to also remove the orange startup and shutdown logos but never found how to do this. Now I want to undo all I've done (not much really) and put it all back the way it was.
Having searched the webs I find all the results about flashing using Odin to a new custom ROM, but I'm sure this is what I want to do.
I am sure I made a backup of the original files but I can't find them anywhere on my computer. However, I have managed to find some files I must have originally used to root/flash.
Odin
S2Root 1.4.3
GT-I9100_XXKG3_insecure
GT-I9100_XXKG3_original
I have rebuilt my computer since I originally rooted my handset, so when I needed the drivers and installed Samsung Kies it told me I had an update to ICS. I've completed this but Sky Go is still saying my device is rooted and will not work. I've downloaded and tried superoneclick (latest version) but this crashes every time. Opening S2Root, which I'm assuming I used originally, and trying to Unroot it tells me my device is not rooted and aborts the operation.
How can I fix this now?
Thanks in advance
Boxa786 said:
When I first got my S2 I rooted it to remove some bloatware like orange backup and maps. I was looking to also remove the orange startup and shutdown logos but never found how to do this. Now I want to undo all I've done (not much really) and put it all back the way it was.
Having searched the webs I find all the results about flashing using Odin to a new custom ROM, but I'm sure this is what I want to do.
I am sure I made a backup of the original files but I can't find them anywhere on my computer. However, I have managed to find some files I must have originally used to root/flash.
Odin
S2Root 1.4.3
GT-I9100_XXKG3_insecure
GT-I9100_XXKG3_original
I have rebuilt my computer since I originally rooted my handset, so when I needed the drivers and installed Samsung Kies it told me I had an update to ICS. I've completed this but Sky Go is still saying my device is rooted and will not work. I've downloaded and tried superoneclick (latest version) but this crashes every time. Opening S2Root, which I'm assuming I used originally, and trying to Unroot it tells me my device is not rooted and aborts the operation.
How can I fix this now?
Thanks in advance
Click to expand...
Click to collapse
You in the right thread?
Sent from my SPH-L710 using xda premium
Hey guys,
First off, I've searched far and wide for any help with my problem but it is such a peculiar situation that I have yet to find someone with a similar situation. I expect if I want to ever use my M8 again, I'll need to send it to HTC and pay a few hundred bucks to fix it. But maybe someone here will have an idea that I've missed.
Shortly after getting my M8, I unlocked my device, rooted it and installed a few roms. Everything was fine save for one major thing: no matter which PC I used (and I used MANY - 3 different windows destops, a windows desktop at the office and my Macbook Pro) the device was never able to mount and make the storage accessible. I knew at that point something at some point had gone wrong. I've long preferred to use a wireless file transfer app to send stuff to and from my phone so I wouldn't have to break out all my cables so I figured it wouldn't be a big deal. I'd make it work.
A few days ago, I decided to try a different rom than what I'd been using for months (HD Revolution - great rom!) and downloaded everything required. I booted to TWRP, wiped the usual stuff and flashed my rom. When I rebooted, I was continually met with a crash as soon as the phone started and was never able to get into the OS. No big deal - this has happened before with other devices, so I didn't sweat it. I simply powered down the phone and tried to get back to recovery. Here's where the problem really kicked in : when attempting to boot to recovery, my phone will bring up the Hboot screen but instantly try to select the first option, thus not allowing me to scroll down to "Recovery". No matter what I do, it brings up the white Hboot screen, automatically selects the first option, gives me some error (I'm at work so I don't have the device in front of me) and tries to boot to the OS. That takes us back to the automatic crash.
Now, I know usually the solution would involve USB and ADB, but like I mentioned at the start of my sad tale, connecting my phone to PC's results either in nothing (Mac) or a "the device has failed" message in Windows. I've tried removing all the phone drivers, reinstalling and using a few toolkit methods - the phone is just never ever detected.
So, that's it. I'm pretty much resigned to sending my phone in and the HTC folks quoted me about $200. I do have a functional phone at the moment so it isn't the worst situation in the world, but if I could fix this I'd be able to using it as my main device again or sell it for a good chunk of change - I just bought it in June.
Sorry for the long read!
As far as the storage issue, never seen that happen before so I'm not sure. When you plug it in to the computer does the phone ask if you want to connect it as a storage device etc?
The bootloader is a very peculiar problem. It almost sounds like you have an img file that its trying to read as soon as you boot into boot loader.
Try to install HTC sync. And make sure the computer has an internet connection when you plug it in via usb.
Try to flash stock recovery fw buddy
Maybe thats problem RUU
Cek mike blg to find all stock recovery fw
After that install custom recovery again
This sounds a little familiar.
In my experience I've found some firmware versions and ROMs very choppy.
I once had a problem with storage too, couldn't send anything over to my phone.
Fortunately I could access recovery, so used ADB sideload and installed another ROM. And went to another firmware and never looked back.
The last 401.6 firmware gave me all sorts of issue.
If you can access fastboot I'd also recommend new firmware 401.7 is working flawlessly for me with ARHD 21.
Sent from my HTC One_M8 using XDA Free mobile app
I would try putting one of the bootable ruus on your SD card so when it goes to your hboot, it'll read the RUU and install it
Awesome, some interesting suggestions here. Would I be able to somehow update the firmware via an SD card without any input from a computer? I managed to get into Recovery last night somehow (maybe letting the battery totally drain and charging it for a while did something) but plugging in my phone when in recovery still won't mount the storage or be recognized by ADB. Would I somehow be able update my firmware from recovery without the need of ADB'ing from my desktop? I've been looking at ROM threads and stuff and noticed that almost every rom requires new firmware or WiFI/radios other stuff won't work....
I'm at work right now so I'll definitely research this in depth when I get home, but if you guys could guide me in the right direction, I'd really appreciate it and maybe buy ya' a beer.
Xavierc123 said:
Awesome, some interesting suggestions here. Would I be able to somehow update the firmware via an SD card without any input from a computer? I managed to get into Recovery last night somehow (maybe letting the battery totally drain and charging it for a while did something) but plugging in my phone when in recovery still won't mount the storage or be recognized by ADB. Would I somehow be able update my firmware from recovery without the need of ADB'ing from my desktop? I've been looking at ROM threads and stuff and noticed that almost every rom requires new firmware or WiFI/radios other stuff won't work....
I'm at work right now so I'll definitely research this in depth when I get home, but if you guys could guide me in the right direction, I'd really appreciate it and maybe buy ya' a beer.
Click to expand...
Click to collapse
Download a rom that can use the 2.xx firmware. Look around and you should be able to find the roms. There's still plenty out there. Here's a little suggestion, reflash TWRP (or other recovery) through fastboot than grab a SD card and place the rom into the SD card and install the rom using through the use of a SD card. Just remember to do a full wipe before that
After tinkering with my Androids over the years, (Infuse, Captivate, G2, and now G3) I have finally decided to become a member of the forum that I primarily use as a source of information and links to downloads. I'd like to first say thank you to all those that have unknowingly help me over the years with my roots. Great place you've got here.
Now the fun part, after two days of ownership, I have experienced the first issue was not able to resolve on my own, what appears to be a hard brick. I downloaded Flashify after my initial root, installed TWRP Manager, ran the patch for writing to the SDcard, and installed TWRP Recovery from AutoRec. All appeared to go well and it said the instal was successful. I followed the instructions I found online that had great results for my particular model and version 5.0.1. Well, when I went to boot into recovery to make my initial backup, the phone shut down and would not come back up. No response at all. It wont power up by any method, tried letting the capacitors drain, still no go. After tinkering with it for a few hours (I've owned this phone for a total of 2 days now), I finally came to the conclusion that it would need JTAG and the original boot image flashed over the one that I mucked up.
Any ideas on where I made my mistake? I'm near 100% certain I downloaded the proper files for my phone model.
Also forgot to mention, I have not changed anything else on the phone. Only installed apps and root browsers I planned on using. So stock kernel, stock ROM, nothing until I started getting ready to make myself a save point, ironic really!
jamguitarist said:
After tinkering with my Androids over the years, (Infuse, Captivate, G2, and now G3) I have finally decided to become a member of the forum that I primarily use as a source of information and links to downloads. I'd like to first say thank you to all those that have unknowingly help me over the years with my roots. Great place you've got here.
Now the fun part, after two days of ownership, I have experienced the first issue was not able to resolve on my own, what appears to be a hard brick. I downloaded Flashify after my initial root, installed TWRP Manager, ran the patch for writing to the SDcard, and installed TWRP Recovery from AutoRec. All appeared to go well and it said the instal was successful. I followed the instructions I found online that had great results for my particular model and version 5.0.1. Well, when I went to boot into recovery to make my initial backup, the phone shut down and would not come back up. No response at all. It wont power up by any method, tried letting the capacitors drain, still no go. After tinkering with it for a few hours (I've owned this phone for a total of 2 days now), I finally came to the conclusion that it would need JTAG and the original boot image flashed over the one that I mucked up.
Any ideas on where I made my mistake? I'm near 100% certain I downloaded the proper files for my phone model.
Also forgot to mention, I have not changed anything else on the phone. Only installed apps and root browsers I planned on using. So stock kernel, stock ROM, nothing until I started getting ready to make myself a save point, ironic really!
Click to expand...
Click to collapse
Post the guide that you followed
You would have to kick your phone into Qualcomm USB Loader 9008 in order to fix it
http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-all-variants/
Hello,
I'm in a bit of a pickle. Bought my sister a brand new Nexus 5x about 3-4 months ago, first thing I did was install Pure Nexus (6.0.1) on it (prerooted) and unlocked bootloader, don't know why I did it but I thought it'd be nice for her to use foreign country appstores/other things. Anyways long story short, I installed Nexus tool root kit (latest version 2.1.9) to return the device to stock and relock the bootloader.
First thing I did was do a full backup (around 600mb, she didn't install much stuff).
Backed up other things - SMS/Phone/Contacts/Media (70mb.. weird), also copied and pasted all media to computer as I didn't trust the small file size here.
Next, I did a flash and unroot with stock firmware, selecting the latest firmware 7.0 (bullhead MTC20k) and this wiped the phone. After that finished, enabled debugging and etc and reconnected. At this point I used the toolkit to relock the device and it was wiped once again. Now, the phone was running the latest firmware and was locked and back to stock.
After rushing through the initial setup, (wifi, account etc.) I got back to home screen, went to developer options to re-enable USB Debugging and got the phone's fingerprint access thing approved. Then I went to open the toolkit to run the restoration. Following prompts and accepting to restore (no password set/required), I saw pretty much all the app names pop up and being restored. However after it completes, the computer's log says check device. Looking at the device I see no apps added or anything. I've run this step a few times but it appears no applications are being restored.
I would greatly appreciate some advice on what to do next, as I'm at a loss here. Thank you!
Hey guys,
Reporting back, I have downgraded the firmware to the latest Marshmellow version 6.0.1 MTC20K, and tried the whole process again. I'm glad to say that the restoration now worked and all the apps can be seen (including the ones requiring root, which now, no longer work).
It appears upgrading to a completely new version prevented the apps from showing.
Anyways, glad the ordeals over, once photos and contacts restored I can present the phone back to my dear sister.
Thanks!