Related
A co-worker recently got a new capitvate from AT&T, and he asked me to root the phone for him. I kept having issues with the phone saying that the phone didn't have the correct signature on the file. I was able to get root on the phone with the superoneclick root but certain programs that needed root would not work properly. So, the work around was to flash using ODIN to a known good unlocked stock ROM. After, flashing to a good stock ROM where the bootloader was not locked I was then able to root and put custom ROM on the phone.
Hi all,
I'm wanting to flash my HTC one 32gb, UK Three network, with the international software so I can receive updates much quicker rather than waiting for my carrier to approve them as well.
First off will I need S-off for this to work because of the carrier lock? I've only ever had unlocked phones before, when I have rooted them. Also what are the best tools for the job? I am looking for that lastest stock international stock ROM that I can root. I'm fine with command line tools like; fastboot, adb ect. Been off the rooting scene in a while since I had a galaxy nexus, with its unlock boot loader option
Thanks.
http://forum.xda-developers.com/showthread.php?t=2183942
This is your best option for rooting
You can't have s-off yet not done yet
jaythenut said:
http://forum.xda-developers.com/showthread.php?t=2183942
This is your best option for rooting
You can't have s-off yet not done yet
Click to expand...
Click to collapse
Could you please help as i am stuck at fastboot screen and cant mount external sd card so can flash via otg ..i cant even install from sd card as it cant read ..any help thanks
Sent from my HTC One X using xda app-developers app
So how can I unlock the boot loader so I can flash a custom recovery? I do not have the option of going to fastboot and unlocking it like on the nexus. Also mine is a carrier version so i assume I cannot unlock the bootloader from the HTC dev site.
twon23 said:
So how can I unlock the boot loader so I can flash a custom recovery? I do not have the option of going to fastboot and unlocking it like on the nexus. Also mine is a carrier version so i assume I cannot unlock the bootloader from the HTC dev site.
Click to expand...
Click to collapse
Try this one http://forum.xda-developers.com/showthread.php?t=2265618
Thanks guys I've done it! Unlocked it the via the HTC dev site and flashed the clockwork mod recovery, then flashed the latest stock ROM. So now I should not have to wait for my network carrier to deliver the updates. Did it on my macbook using fastboot and adb.
So for future reference for anyone else;
HTC one on carrier Three UK, flashed with latest stock ROM with no problems.
No need for S-off either.
twon23 said:
Thanks guys I've done it! Unlocked it the via the HTC dev site and flashed the clockwork mod recovery, then flashed the latest stock ROM. So now I should not have to wait for my network carrier to deliver the updates. Did it on my macbook using fastboot and adb.
So for future reference for anyone else;
HTC one on carrier Three UK, flashed with latest stock ROM with no problems.
No need for S-off either.
Click to expand...
Click to collapse
That is where you might have troubles. Because the OTA updates will still look at your CID and if your CID doesn't match up (which it won't) because the update is for the CID in the UK region and your CID is for example the Australian region then the update won't install.
said houlterm
twon23 said:
Thanks guys I've done it! Unlocked it the via the HTC dev site and flashed the clockwork mod recovery, then flashed the latest stock ROM. So now I should not have to wait for my network carrier to deliver the updates. Did it on my macbook using fastboot and adb.
So for future reference for anyone else;
HTC one on carrier Three UK, flashed with latest stock ROM with no problems.
No need for S-off either.
Click to expand...
Click to collapse
Hi, can i ask where you got the Stock ROM from? I rooted mine the other day, then decided i wanted to unroot it, and in trying to do so I ended up using the wrong RUU and now the Wifi and Camera dont work. I am an idiot.
So ive decided ill settle for a stock ROM for now until someone comes along with the UK Three RUU.
Thanks in advance
Hello,
I seem to have gotten myself into a bind, and looking ahead to the 4.4 KitKat release, I am not sure how to get myself out of it. I've already done a lot of research and troubleshooting on my own, but can't seem to resolve the problem.
I purchased an HTC One Google Play edition, and decided to root to apply a quick fix with utilizing the Nexus 5 launcher. To that end, I unlocked my bootloader and rooted. I had a Windows 7 partition on my Mac at the time, but it was giving me trouble. Since the root, I became dissatisfied with the performance of the phone, and attempted to restore to factory.
I flashed stock recovery again, and relocked the bootloader. Now the bootloader shows as "relocked" and "tampered." However, in between root and unroot attempts, I upgraded my partition to Windows 8.1. Suddenly, when in fastboot, my HTC One shows up as "USB Device not Recognized," meaning I cannot issue any commands using ADB. If I don't get "waiting for device" I get "device offline," and my device is still rooted.
Whenever I uninstall Super SU, it's right back upon reboot.
I currently have S-ON. I am unable to get S-OFF because my computer doesn't recognize the phone when in fastboot. I tried updating and downloading different HTC Drivers to no avail.
I want to attempt to get my device back to its exact status when I bought the phone. Meaning, I want to have my bootloader as locked, keep S-ON (although I don't mind having S-OFF temporarily), and flash the stock RUU/Recovery. Upon Google Search, this seems easy, but there is not much out there for the GPE. A lot of the guides I have found are for Sense versions. My phone is not a GPE conversion. It is an actual GPE phone purchased on the Play Store.
Phone is functional, but I am concerned when 4.4 comes out, the update will fail or brick.
Sorry if this thread is long. I wanted to be as detailed as possible when asking for help. Thanks again to anyone on XDA who can assist.
mikhailov1 said:
Hello,
I seem to have gotten myself into a bind, and looking ahead to the 4.4 KitKat release, I am not sure how to get myself out of it. I've already done a lot of research and troubleshooting on my own, but can't seem to resolve the problem.
I purchased an HTC One Google Play edition, and decided to root to apply a quick fix with utilizing the Nexus 5 launcher. To that end, I unlocked my bootloader and rooted. I had a Windows 7 partition on my Mac at the time, but it was giving me trouble. Since the root, I became dissatisfied with the performance of the phone, and attempted to restore to factory.
I flashed stock recovery again, and relocked the bootloader. Now the bootloader shows as "relocked" and "tampered." However, in between root and unroot attempts, I upgraded my partition to Windows 8.1. Suddenly, when in fastboot, my HTC One shows up as "USB Device not Recognized," meaning I cannot issue any commands using ADB. If I don't get "waiting for device" I get "device offline," and my device is still rooted.
Whenever I uninstall Super SU, it's right back upon reboot.
I currently have S-ON. I am unable to get S-OFF because my computer doesn't recognize the phone when in fastboot. I tried updating and downloading different HTC Drivers to no avail.
I want to attempt to get my device back to its exact status when I bought the phone. Meaning, I want to have my bootloader as locked, keep S-ON (although I don't mind having S-OFF temporarily), and flash the stock RUU/Recovery. Upon Google Search, this seems easy, but there is not much out there for the GPE. A lot of the guides I have found are for Sense versions. My phone is not a GPE conversion. It is an actual GPE phone purchased on the Play Store.
Phone is functional, but I am concerned when 4.4 comes out, the update will fail or brick.
Sorry if this thread is long. I wanted to be as detailed as possible when asking for help. Thanks again to anyone on XDA who can assist.
Click to expand...
Click to collapse
try this http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
it worked for some users
Thanks. Will try when I get home. I was able to use my Win 7 computer at work to unlock the boot loader again, but I cannot get S Off. I ran rumrunner and it looked like it was working, but then said FATAL: download update. Is there no rumrunner for GPE?
Sent from my HTC One using Tapatalk
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
mikhailov1 said:
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
You got stock rom and stock recovery ryt... lock the bootloader and check for update
Prash8429 said:
You got stock rom and stock recovery ryt... lock the bootloader and check for update
Click to expand...
Click to collapse
Yeah I have stock rom and I removed TWRP and flashed stock recovery. Because I did two factory restores from bootloader, I'm assuming the stock recovery is working properly, but I'm a noob at this stuff so I could be wrong.
Going to relock the bootloader, remove SuperSU, and attempt the update when it hits. Hopefully it will work.
Thanks for your help! Since I'm a new member, how do I add to your thanks meter? Want to make sure you're properly....thanked.
mikhailov1 said:
Yeah I have stock rom and I removed TWRP and flashed stock recovery. Because I did two factory restores from bootloader, I'm assuming the stock recovery is working properly, but I'm a noob at this stuff so I could be wrong.
Going to relock the bootloader, remove SuperSU, and attempt the update when it hits. Hopefully it will work.
Thanks for your help! Since I'm a new member, how do I add to your thanks meter? Want to make sure you're properly....thanked.
Click to expand...
Click to collapse
you can still get OTA with a rooted phone, as long as you have stock recovery and flashed stock ruu.... tip if your having trouble with flashing ruu change the zip file name to something simple like ruu.zip worked for me.:good:
mikhailov1 said:
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Can you tell me if your bootloader was 1.54 or 1.55? I have been unable to get Windows 8.1 to recognize the 1.54 bootloader. It always says "device not recognized" If yours was 1.54.0000 I will try this fix. Thanks.
I am 1.54.
Sent from my Nexus 5 using Tapatalk
Thanks for this, helped me out alot
Sent from my HTC One using XDA Premium 4 mobile app
Hello everyone,
I have an AT&T galaxy note 3 that has an unlocked SIM, I unlocked using a code from cellunlocker.net. I'm using it on MetroPCS. I have the gps issue that others have mentioned on the forums and I wanted to update to Kitkat as I heard it fixes the issue. Only problem is I obviously can't get the OTA update from AT&T. Kies says that my phone has the latest firmware (MJ5). I tried using the ZIP that was posted on the forums (official not beta) but I got the sideload error. I also went into best buy and tried updating it at the Samsung desk and they said they couldn't pick up the phone in "smart". Not sure what that means but they said it has to do with it being unlocked. The phone is not rooted and never has been. Am I missing something? Also, if I do succeed in updating will I loose my SIM unlock? If I do can I use the same code I used previously to unlock it?
Thanks!
yedidi2006 said:
Hello everyone,
I have an AT&T galaxy note 3 that has an unlocked SIM, I unlocked using a code from cellunlocker.net. I'm using it on MetroPCS. I have the gps issue that others have mentioned on the forums and I wanted to update to Kitkat as I heard it fixes the issue. Only problem is I obviously can't get the OTA update from AT&T. Kies says that my phone has the latest firmware (MJ5). I tried using the ZIP that was posted on the forums (official not beta) but I got the sideload error. I also went into best buy and tried updating it at the Samsung desk and they said they couldn't pick up the phone in "smart". Not sure what that means but they said it has to do with it being unlocked. The phone is not rooted and never has been. Am I missing something? Also, if I do succeed in updating will I loose my SIM unlock? If I do can I use the same code I used previously to unlock it?
Thanks!
Click to expand...
Click to collapse
Root it and install a custom kk rom
yedidi2006 said:
Hello everyone,
I have an AT&T galaxy note 3 that has an unlocked SIM, I unlocked using a code from cellunlocker.net. I'm using it on MetroPCS. I have the gps issue that others have mentioned on the forums and I wanted to update to Kitkat as I heard it fixes the issue. Only problem is I obviously can't get the OTA update from AT&T. Kies says that my phone has the latest firmware (MJ5). I tried using the ZIP that was posted on the forums (official not beta) but I got the sideload error. I also went into best buy and tried updating it at the Samsung desk and they said they couldn't pick up the phone in "smart". Not sure what that means but they said it has to do with it being unlocked. The phone is not rooted and never has been. Am I missing something? Also, if I do succeed in updating will I loose my SIM unlock? If I do can I use the same code I used previously to unlock it?
Thanks!
Click to expand...
Click to collapse
You won't lose SIM unlock no matter what route you go.
You have to put an AT&T sim to get the update
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
dungvonguyen said:
You have to put an AT&T sim to get the update
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
no you dont need an AT&T sim, updated mine with an Aio/Cricket sim card in and it worked fine. Try going recovery then installing the NB2 OTA first then again with the NC2 OTA, a quick search should fine you these files on XDA, I did it a month or two ago fine.
---------- Post added at 03:02 AM ---------- Previous post was at 02:55 AM ----------
Here are the NB4 & NC2 OTA files, please note these are not mine, they are from other XDA posts
NB4: https://www.dropbox.com/s/zccryfxycby1iq8/2400258.cfg
NC2: http://www.mediafire.com/download/mb...o2/2400258.zip
I believe install goes as follows:
1. copy file to phone
2. rename to update.zip
3. boot recovery
4. wipe data/factory reset
5. install update file
6. select update.zip
7. restart follow install
8. do steps 1 to 7 again, except copy over the NC2 files
hopefully someone else can confirm this? As I did this a couple months ago and don't wanna mess up the op's phone.
yedidi2006 said:
Hello everyone,
I have an AT&T galaxy note 3 that has an unlocked SIM, I unlocked using a code from cellunlocker.net. I'm using it on MetroPCS. I have the gps issue that others have mentioned on the forums and I wanted to update to Kitkat as I heard it fixes the issue. Only problem is I obviously can't get the OTA update from AT&T. Kies says that my phone has the latest firmware (MJ5). I tried using the ZIP that was posted on the forums (official not beta) but I got the sideload error. I also went into best buy and tried updating it at the Samsung desk and they said they couldn't pick up the phone in "smart". Not sure what that means but they said it has to do with it being unlocked. The phone is not rooted and never has been. Am I missing something? Also, if I do succeed in updating will I loose my SIM unlock? If I do can I use the same code I used previously to unlock it?
Thanks!
Click to expand...
Click to collapse
Same problem with wife's N900A , its on T Mobile and I cannot update it via OTA or Kies.
yedidi2006 said:
Hello everyone,
I have an AT&T galaxy note 3 that has an unlocked SIM, I unlocked using a code from cellunlocker.net. I'm using it on MetroPCS. I have the gps issue that others have mentioned on the forums and I wanted to update to Kitkat as I heard it fixes the issue. Only problem is I obviously can't get the OTA update from AT&T. Kies says that my phone has the latest firmware (MJ5). I tried using the ZIP that was posted on the forums (official not beta) but I got the sideload error. I also went into best buy and tried updating it at the Samsung desk and they said they couldn't pick up the phone in "smart". Not sure what that means but they said it has to do with it being unlocked. The phone is not rooted and never has been. Am I missing something? Also, if I do succeed in updating will I loose my SIM unlock? If I do can I use the same code I used previously to unlock it?
Thanks!
Click to expand...
Click to collapse
Same problem here too, i have it running on metro, tried the ota update and it gives me "software update interrupted" message. Ive benn trying to find a way arround it but i dont know how, let me know if you get it . Thanks
So I finally got my At&t note 3 unlocked and on MetroPCS updated to KitKat!
Here's what I did:
1. I was on MJ5 so I couldn't update straight to KitKat NC2 without first updating to NB4. I tried to install NC2 first and got an error. I found a very useful thread here with links to all the firmware versions http://forum.xda-developers.com/showthread.php?t=2693375 Many thanks to Walter.White!! I downloaded NB4 and installed it using ADB. In ADB you'll need to type "adb sideload xxxxx.xxx" (x is the filename of the update) without the quotes.
2. After successfully installing NB4 I downloaded NC2 and installed it the same way, and voila! Make sure to remane the file to "Update" first. When your in ADB type "adb sideload update.zip" to install the file. Now I'm running KitKat.
Note: My sim remained unlocked just like I had figured so no surprises. Just check your apn setting are correct after upgrading so you'll get good service (LTE, etc..).
Can anyone confirm?
yedidi2006 said:
So I finally got my At&t note 3 unlocked and on MetroPCS updated to KitKat!
Here's what I did:
1. I was on MJ5 so I couldn't update straight to KitKat NC2 without first updating to NB4. I tried to install NC2 first and got an error. I found a very useful thread here with links to all the firmware versions http://forum.xda-developers.com/showthread.php?t=2693375 Many thanks to Walter.White!! I downloaded NB4 and installed it using ADB. In ADB you'll need to type "adb sideload xxxxx.xxx" (x is the filename of the update) without the quotes.
2. After successfully installing NB4 I downloaded NC2 and installed it the same way, and voila! Make sure to remane the file to "Update" first. When your in ADB type "adb sideload update.zip" to install the file. Now I'm running KitKat.
Note: My sim remained unlocked just like I had figured so no surprises. Just check your apn setting are correct after upgrading so you'll get good service (LTE, etc..).
Click to expand...
Click to collapse
Hello. I am using n900a baseband N900AUCUBMI9. Can this method work for me to upgrade to kitkat? Thanks guys
Background info:
Currently running LMY47I on Nexus 6 unlocked and rooted with TWRP recovery on TMO network. When I updated to 5.1, the process of manual install went without a problem. After a little while, LTE reception was really poor. After doing some research, I realized that LMY47M was the specific release for TMO users and updates access to the 700 MHz band which I think might resolve some of my problems.
The plan:
Downgrade to 5.0.1 LRX22C so I can manually update to 5.1 LMY47M.
The problem:
My Nexus 6 isn't recognized as an ABD device once the bootloader is rebooted (but it is when the device is on and normally booted). I've tried to uninstall and reinstall drivers manually as well as with Wug's Root Toolkit. Still no dice.
Any ideas where I'm going wrong?
nccountrymike said:
Background info:
Currently running LMY47I on Nexus 6 unlocked and rooted with TWRP recovery on TMO network. When I updated to 5.1, the process of manual install went without a problem. After a little while, LTE reception was really poor. After doing some research, I realized that LMY47M was the specific release for TMO users and updates access to the 700 MHz band which I think might resolve some of my problems.
The plan:
Downgrade to 5.0.1 LRX22C so I can manually update to 5.1 LMY47M.
The problem:
My Nexus 6 isn't recognized as an ABD device once the bootloader is rebooted (but it is when the device is on and normally booted). I've tried to uninstall and reinstall drivers manually as well as with Wug's Root Toolkit. Still no dice.
Any ideas where I'm going wrong?
Click to expand...
Click to collapse
ADB is not used while in bootloader. You must use fastboot commands.
nccountrymike said:
Background info:
Currently running LMY47I on Nexus 6 unlocked and rooted with TWRP recovery on TMO network. When I updated to 5.1, the process of manual install went without a problem. After a little while, LTE reception was really poor. After doing some research, I realized that LMY47M was the specific release for TMO users and updates access to the 700 MHz band which I think might resolve some of my problems.
The plan:
Downgrade to 5.0.1 LRX22C so I can manually update to 5.1 LMY47M.
The problem:
My Nexus 6 isn't recognized as an ABD device once the bootloader is rebooted (but it is when the device is on and normally booted). I've tried to uninstall and reinstall drivers manually as well as with Wug's Root Toolkit. Still no dice.
Any ideas where I'm going wrong?
Click to expand...
Click to collapse
1) ADB commands are never recognized in fastboot. The correct command is "fastboot devices".
2) When you downgrade, do not downgrade your bootloader. Going from 5.1 bootloader to 5.0 bootloader then back to 5.1 bootloader could potentially lead to a brick.
3) The only files that the OTA looks at are system.img and boot.img, so these are all you need to fastboot flash.
Thanks all! User error confirmed.