Related
Hello all, I'm new to this site and I've never rooted a phone. Actually, the Eris is my first smartphone. I've read a lot of forums about rooting the Eris and from what I understand I shouldn't have installed the 2.1 ota update. I bought this phone soon after they were released so maybe I have a 1.47 hboot? I'm unsure how to check this, but if so does this mean I can root using the 1.5 method?
I just bought a class 6 8GB microsd card with the hopes of installing a custom rom, overclocking, and installing apps2sd. Now I'm getting very discouraged because it seems 2.1 can't currently be rooted.
Hopefully a senior user can help me out. Please put your response in lamens terms. I've seen some other forums where junior users are getting bashed for asking stupid questions so I'm putting it out there....please don't bash me for this one.
http://forum.xda-developers.com/showthread.php?t=684049
everything you need and more. To answer your next question. As long as your phone was never updated with leak, the process for root of 1.5 and 2.1 are the same.
happy rooting!
Thanks Spencer! If I root using the method at that page will I be able to flash other roms or will I be stuck with this 2.1 ROM? I'd like to install the evileris rom and (again I'm a newbie) I don't want to end up stuck like the people who installed the leaked 2.1.
you should be able to flash a custom rom to the phone as i believe you have to first load a custom recovery image to it. i could be wrong though just a guess.
SDK Not Working?
HELP!! I just rooted my phone, installed java, installed SDK and I can't get the command prompts to work. I followed the steps exactly (or so I think) and I'm opening sdksetup.exe. When I try to type I get nothing. Am I opening the wrong file or doing something wrong. I've not been able to install the recovery or custom rom to my phone yet, so I'm very vulnerable right now. Any ideas anyone?
Ok, maybe this is my problem...
Before the root, I could go into device manager from my computer and I got a yellow exclamation mark. After the root, I cannot find it. I can click on portable devices and it shows an Android Phone so I'm guessing my computer doesn't recognize it anymore. If that's the case I probably need to update the driver for SDK to work, but I need to find the device for that to work. I have USB debugging on. Any help is appreciated.
If it says android phone with no exclamation point that means it is recognized. Its when there is an exclamation point that means it is not recognized. I probably won't be able to help you further because I'm a rooting noob (I've only rooted my Eris and I had no problems) but I am a computer expert and I would suggest rebooting your computer and then trying it again... unless you already have.
-------------------------------------
Sent via the XDA Tapatalk App
joshw0000 said:
HELP!! I just rooted my phone, installed java, installed SDK and I can't get the command prompts to work. I followed the steps exactly (or so I think) and I'm opening sdksetup.exe. When I try to type I get nothing. Am I opening the wrong file or doing something wrong. I've not been able to install the recovery or custom rom to my phone yet, so I'm very vulnerable right now. Any ideas anyone?
Click to expand...
Click to collapse
What exactly do you mean when you say "I can't get the command prompts to work"?
joshw0000 said:
HELP!! I just rooted my phone, installed java, installed SDK and I can't get the command prompts to work. I followed the steps exactly (or so I think) and I'm opening sdksetup.exe. When I try to type I get nothing. Am I opening the wrong file or doing something wrong. I've not been able to install the recovery or custom rom to my phone yet, so I'm very vulnerable right now. Any ideas anyone?
Click to expand...
Click to collapse
Ok, calm down its not the end of the world, i ran into the same problem. What we need for us to help you, is at what point are you in trying to root your phone. Do you have SDK installed and updated?
I'm following the how to root instructions. I've completed I: Gaining Root and made it to 9. In II: Prerequisites. Java and SDK are both saved and extracted on my c: drive. I downloaded the USB drivers package in #6 of II. USB debugging was enabled and the phone was set to charge only. When I opened device manager on my pc, their was no yellow exclamation like the instructions indicated. I clicked on "Android Phone" and attempted to update the drivers found in SDK but Windows said they were up to date. I moved on to step III. Flashing a Custom Recovery and saved the zip file to my SD (should I save that to my c: drive?). I extracted it to tools in Android SDK and attempted to use the command prompt in SDK. It was unresponsive. It did not recognize my phone. I'm unsure if it does that automatically, if I need to take action, or if I should use the pc command prompt.
I went back to #9 of II and tried to troubleshoot. I tried every way I could think of to get the exclamation mark to show up in device manager so I could update the USB drivers. I hooked up my wife's unrooted Eris and it had the exclamation. I restarted my phone, restarted my computer, reflashed PB00IMG.zip and still had no luck.
Anybody had this probem? Any suggestions?
Okay,
I have been trying (in vein) for the past 4 days to upgrade my AT&T locked streak to 2.2 Froyo. I have tried everything I can think of between instructions from here, Streakdroid, Modaco.... nothing seems to work. Uggg.... Can anyone confirm that the upgrade can actually be done from a Windows & 64bit computer???
I have deleted and downloaded the QDL/drivers/etc probably a hundred times, followed the specific instructions for 64bit machines, and never have I been able to locate the Qualcomm Diagnostic stuff anywhere in my computer. I believe this to be the problem, but can't seem to find a solution to it. Have followed all the tutorials to the letter, umpteen times.
So either my reading comprehension SUCKS, or Windows 7 64bit is the problem. Unfortunately I have no access to any other Windows machine with a lower version...uggg
Please help.
I can CONFIRM this for this is the system I use to QDL, Fastboot and CWR..... There is a video tutoriol on excactly how to do this on Win 7 x64bit. Im not sure what forum it was on but I'll see if I can find it. Trust me on this QDL works perfect on x64 bit its just getting and signing the drivers thats tricky.
Sent from my Dell Streak
AT&T Froyo 2.2 ROM v.318 + Perf Mod
Win 7 x64 bit SUPERUSER Rooted
I have a hard time getting the QDL Tool to work for me. I finally met success when I used another machine running Win 7 32Bit. The drivers loaded and all was then right with the world.
Muscleshop said:
Okay,
I have been trying (in vein) for the past 4 days to upgrade my AT&T locked streak to 2.2 Froyo. I have tried everything I can think of between instructions from here, Streakdroid, Modaco.... nothing seems to work. Uggg.... Can anyone confirm that the upgrade can actually be done from a Windows & 64bit computer???
I have deleted and downloaded the QDL/drivers/etc probably a hundred times, followed the specific instructions for 64bit machines, and never have I been able to locate the Qualcomm Diagnostic stuff anywhere in my computer. I believe this to be the problem, but can't seem to find a solution to it. Have followed all the tutorials to the letter, umpteen times.
So either my reading comprehension SUCKS, or Windows 7 64bit is the problem. Unfortunately I have no access to any other Windows machine with a lower version...uggg
Please help.
Click to expand...
Click to collapse
If Its a Question then can you please post in the Q&A Section
Moving to Q&A
I have also had success running QDL on my Windows 7 64 Bit conputer. I have a White AT&T Locked Streak.... Well not anyomre Just do a search in Q & A, i have answered this question a couple times for others with success. Good Luck!
try following this guide http://forum.xda-developers.com/showthread.php?t=805112 but instead of using the 2.1 package download the 2.2 o2 package from here http://mobileupdate.dell.com/PackageProductionLocations/Streak_319_12792_21.pkg
worked for me using win7 64-bit
Have a look at this post:
http://forum.pocketables.net/showthread.php?t=8715
Or
http://forum.pocketables.net/showthread.php?t=8214
You should be able to find what you are looking for, ask questions there too, it is a great group.
jhotmann said:
try following this guide http://forum.xda-developers.com/showthread.php?t=805112 but instead of using the 2.1 package download the 2.2 o2 package from here http://mobileupdate.dell.com/PackageProductionLocations/Streak_319_12792_21.pkg
worked for me using win7 64-bit
Click to expand...
Click to collapse
Im curious, why would you suggest using the o2 ROM when the OP has a US Streak? This advice is misleading and will have the potential of creating more errors than he is currently having. Given the fact that there is a US version of the 2.2 ROM .
To the OP: I would suggest against using the o2 version. Just my two bits, rather you make an informed decision on how you move forward
jhotmann said:
try following this guide http://forum.xda-developers.com/showthread.php?t=805112 but instead of using the 2.1 package download the 2.2 o2 package from here http://mobileupdate.dell.com/PackageProductionLocations/Streak_319_12792_21.pkg
worked for me using win7 64-bit
Click to expand...
Click to collapse
Just to make sure...
Does the phone need to be unlocked before upgrading? AT&T gave me the code no problem, but haven't had a chance to get a Tmobile SIM card yet to unlock it
I used Windows 7 Home Premium 64bit to update my White 6601 ATT locked Streak to Pre-Release 2.2 Official and then flash StreakMod recovery via fastboot, flash AMS and DSP1 via fastboot, reboot to recovery, Full Wipe (Factory reset / Wipe Data, Wipe Cache, Advanced Wipe Dalvik), Install .ZIP from SD card, install 1.6.0. (well, I installed 1.4.6 first and then flashed 1.6 overtop because that was what was out at the time)
It can be done. No need to use unlock code from AT&T before hand. The Qualcom HS-USB Diagnostics 9002 is located within the ZIP archive you download with the repairtool.zip under \QDLTool3rd_20101022_GAUSB1A130500\Driver\Driver_2.067\Win64\WNET\AMD64
You want "qcser.inf"
Make sure you do all the "Test Mode" stuff for certificate installation FIRST.
Are you following the directions here:
http://streakdroid.com/?page_id=92
nickshertzer said:
I used Windows 7 Home Premium 64bit to update my White 6601 ATT locked Streak to Pre-Release 2.2 Official and then flash StreakMod recovery via fastboot, flash AMS and DSP1 via fastboot, reboot to recovery, Full Wipe (Factory reset / Wipe Data, Wipe Cache, Advanced Wipe Dalvik), Install .ZIP from SD card, install 1.6.0. (well, I installed 1.4.6 first and then flashed 1.6 overtop because that was what was out at the time)
It can be done. No need to use unlock code from AT&T before hand. The Qualcom HS-USB Diagnostics 9002 is located within the ZIP archive you download with the repairtool.zip under \QDLTool3rd_20101022_GAUSB1A130500\Driver\Driver_2.067\Win64\WNET\AMD64
You want "qcser.inf"
Make sure you do all the "Test Mode" stuff for certificate installation FIRST.
Are you following the directions here:
http://streakdroid.com/?page_id=92
Click to expand...
Click to collapse
Yes, followed those directions umpteen times...the driver never downloads as "Qualcomm..." I'm seriously beginning to think it has something to do with this Sony laptop...lol
So many people have done it, I know the directions are correct. There is something about the way this computer is seeing/recognizing/etc that is screwing this process up, has to be. Hopefully I'll get some time on another computer shortly..and try it again
Muscleshop said:
Yes, followed those directions umpteen times...the driver never downloads as "Qualcomm..." I'm seriously beginning to think it has something to do with this Sony laptop...lol
So many people have done it, I know the directions are correct. There is something about the way this computer is seeing/recognizing/etc that is screwing this process up, has to be. Hopefully I'll get some time on another computer shortly..and try it again
Click to expand...
Click to collapse
I struggled over and over with using QDL on Windows 7 64 bit too. I'd pick the correct qualcomm driver but it kept coming up as comm14 or comm15. Up and up each time I tried it.
I'm a mac user by the way using bootcamp. So I jumped over to our imac running xp and was finally able to upgrade.
So I'd suggest finding someone with xp or windows 7 32 bit. Should be a breeze after that. Good luck!
Muscleshop said:
Yes, followed those directions umpteen times...the driver never downloads as "Qualcomm..." I'm seriously beginning to think it has something to do with this Sony laptop...lol
So many people have done it, I know the directions are correct. There is something about the way this computer is seeing/recognizing/etc that is screwing this process up, has to be. Hopefully I'll get some time on another computer shortly..and try it again
Click to expand...
Click to collapse
Does your PC screen say "Test Mode, Windows 7, Build 7600" anywhere on the main screen?
Okay so I bought this HTC Amaze the other day and needless to say, I love it.
The only bad thing about it is that it's on 2.3.4 cause it's the unbranded, Asian version. (My english is even set to bloody Malaysian)
Anywho, I read that there's actually an OTA for it that gives 4.0
YAY But that's for tmobile.
Coming from a Motorola Defy+ to HTC isn't exactly a smooth transition, cause in Motorola they couldn't unlock the bootloader and the original stock files were SBF's which were flashed by RSD lite. Also rooting is much easier, in my opinion.
So, I want to boot ICS on this, but not the original tmobile OTA, more like CM9, if possible? I saw there's a few roms I could use.
I tried doing some work on this phone but got confused.
I unlocked the bootloader, and I'm honestly not sure what to do next. Do I need to do S-OFF? I don't even know what that is, let alone how to do it.
Plus I read that it's only available for Ubuntu users?
.............................
Can someone please guide me in the right direction?
If your bootloader is unlocked and you have a custom recovery you should be able to flash a custom ROM like CM. In order to flash a ROM that is specific to another carrier I believe you have to be s-off and super cid
Okay so I installed 4EXT and rooted the device permanently. I tried doing a CM10.1 rom and gapps...... It loaded, but it wont go past the welcome screen where you select the language.
Gonna try to re-wipe and flash again. If not, I made a backup of 2.3.4.
Make sure you check the md5 sums before installation
Okay this is bad, the md5sums don't match and now I'm stuck at white background with htc logo on it all the time.
I can boot into bootloader then recovery. I can also flash roms but they don't work. I tried multiple, always doing a full format except sd card.
I tried flashing stock kernel, not working.
I tried using hasoon's aio to flash original RUU but device undetected.
IDK What to do
Redownload a ROM and make sure the md5 sums match then flash the ROM it you can restore a nandroid if you made one. If the md5 sums don't match that is why you are having issues. It's good you can boot into recovery.
I managed to get it to work on stock rom again, thanks to another forum thread.
I'm a bit scared to try doing it again, seeing that I have windows 8 and the programs don't work on it.
Maybe when I dual boot either ubuntu or windows7 I'll try it again.
Having a nandroid backup and checking the md5 sums before flashing should prevent most issues from happening. I'm running a dual boot windows 8/Ubuntu PC if that means anything to you
It means everything to me!!!!
Can you explain to me how you did it?
I have to burn the image on a cd still, but I tried to dual boot windows 7 and 8 but 7 couldn't be installed on a gpt partition.
I do have an external hard drive, but that's mainly for backing up my data, so I don't want to use that.
Here's what I was doing, I created a partition of 100gbs using the preloaded software on windows, formatted and put it as a letter and it worked well as a partition on windows 8 itself. But when I booted the windows 7 cd, it wouldn't install on it.
Darin_Ram said:
It means everything to me!!!!
Can you explain to me how you did it?
I have to burn the image on a cd still, but I tried to dual boot windows 7 and 8 but 7 couldn't be installed on a gpt partition.
I do have an external hard drive, but that's mainly for backing up my data, so I don't want to use that.
Here's what I was doing, I created a partition of 100gbs using the preloaded software on windows, formatted and put it as a letter and it worked well as a partition on windows 8 itself. But when I booted the windows 7 cd, it wouldn't install on it.
Click to expand...
Click to collapse
I installed Ubuntu with the windows installer if I remember correctly. It's been awhile since I did it so I don't remember exactly how I did it and I don't remember having any issues doing it. My laptop originally came with Windows 7 and I upgraded it to Windows 8 and installed Ubuntu sometime after upgrading to Windows 8. My older hardware may be the reason why it worked now that I'm looking over this stuff again. I'm pretty sure I downloaded the "Install Ubuntu with the Windows installer" to install it. Hopefully that helps.
kmok said:
I installed Ubuntu with the windows installer if I remember correctly. It's been awhile since I did it so I don't remember exactly how I did it and I don't remember having any issues doing it. My laptop originally came with Windows 7 and I upgraded it to Windows 8 and installed Ubuntu sometime after upgrading to Windows 8. My older hardware may be the reason why it worked now that I'm looking over this stuff again. I'm pretty sure I downloaded the "Install Ubuntu with the Windows installer" to install it. Hopefully that helps.
Click to expand...
Click to collapse
Yeah, having the hardware from win7 would have definitely had something to do with the compatibility of Ubuntu on the laptop.
:/ I'll google the windows installer, if it helps I'll let you know.
Darin_Ram said:
Yeah, having the hardware from win7 would have definitely had something to do with the compatibility of Ubuntu on the laptop.
:/ I'll google the windows installer, if it helps I'll let you know.
Click to expand...
Click to collapse
What exactly are you trying to do? Make your phone s-off? All you need is to boot ubuntu 32bit from a cd to make your phone s-off. Everything else is pretty much done through windows or custom recovery. All of t-mobiles RUUs are .zip files and are flashed through the bootloader and the windows toolkits should be able to flash them otherwise some of the other carrier RUUs are .exe files.
No, Hasoon's aio doesn't work on my operating system, I do not know why.
It works fine on windows 7, but I do not always have access to it.
That's why I wanted to dual boot with Ubuntu. If I could get the drivers and programs to work, I can try booting into Cyanogenmod knowing that if anything happens, I can reboot my phone the way I did last time.
I would try WindyCityRockr's WinDroid program. Hasoon's program wasn't Woking for me either but WinDroid worked for me on Windows 8. If that works you may not need to have Ubuntu installed. Booting Ubuntu from a CD is probably your best option
kmok said:
I would try WindyCityRockr's WinDroid program. Hasoon's program wasn't Woking for me either but WinDroid worked for me on Windows 8. If that works you may not need to have Ubuntu installed. Booting Ubuntu from a CD is probably your best option
Click to expand...
Click to collapse
I'll try it out, I still have to re-root my phone lol so if that works, I'll let you know.
guys, i'm new to the amaze, last night i managed to unlock the bootloader, rooted and even installed 4ext recovery, the issue is that i am on an unbranded amaze with that old GB stock (hate it), i can't find the control bear to get it s-off'ed, anyone has the link for the windows file? i saw the tutorial on youtube, couldn't find the exe to it...
is it safe to do that wire trick? can someone send me the exe file or pm me? i would be very greatful, thanks
jafferkhan said:
guys, i'm new to the amaze, last night i managed to unlock the bootloader, rooted and even installed 4ext recovery, the issue is that i am on an unbranded amaze with that old GB stock (hate it), i can't find the control bear to get it s-off'ed, anyone has the link for the windows file? i saw the tutorial on youtube, couldn't find the exe to it...
is it safe to do that wire trick? can someone send me the exe file or pm me? i would be very greatful, thanks
Click to expand...
Click to collapse
Unlimited.io no longer supports the Windows version.
I wonder however if any info here will help you:
http://forum.xda-developers.com/showthread.php?t=2437057
http://www.youtube.com/watch?v=PELMvlA-lWw
A reminder to be very careful. I make no warranties express or implied, but will admit total success after completing all the pre-requisites and then following the proper procedure through linux. Granted, my timing was off, and it took a great many more than several tries, however on the plus side, I get points for perseverence, and it was truly exciting thinking I could have destroyed my phone at any moment, and somehow, did not. FWIW, I used an older than recommended version of linux (don't remember which) than that specified, but can't recommend anyone else do that.
Good luck.
pbergonzi said:
Unlimited.io no longer supports the Windows version.
I wonder however if any info here will help you:
http://forum.xda-developers.com/showthread.php?t=2437057
http://www.youtube.com/watch?v=PELMvlA-lWw
A reminder to be very careful. I make no warranties express or implied, but will admit total success after completing all the pre-requisites and then following the proper procedure through linux. Granted, my timing was off, and it took a great many more than several tries, however on the plus side, I get points for perseverence, and it was truly exciting thinking I could have destroyed my phone at any moment, and somehow, did not. FWIW, I used an older than recommended version of linux (don't remember which) than that specified, but can't recommend anyone else do that.
Good luck.
Click to expand...
Click to collapse
it doesn't help, it redirects towards the unlimited.io website,still without the windows installer
I see links below the video that download files from 4shared. One for GB, one for ICS.
jafferkhan said:
it doesn't help, it redirects towards the unlimited.io website,still without the windows installer
Click to expand...
Click to collapse
Why you guys take risks of doing those risky things with windows...
So many guys bricked their phones...
And few have working also but who knows..
And Linux is not that hard according to me..
Just get started then... Even you don't Know.then we are here to help you out..
Read the precautions and all...and you will be fine with wire trick also
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
shubham211995 said:
Why you guys take risks of doing those risky things with windows...
Click to expand...
Click to collapse
Good point, shubham211995.
There is a clear notice in the pre-requsites on the unlimited.io website to use Ubuntu 12.04 and newer 32-bit, and that even if one has Windows installed, one can use the LiveCD:
"1. Supported Operating Systems:
We only support Ubuntu 12.04 (and newer) 32bit, you may use a LiveCD if you have the wrong OS installed natively. LiveUSB will NOT work!
Ubuntu 64bit, Ubuntu versions lower than 12.04, other Linux distros, Virtual Machines and Mac's will NOT work - we will not help you if you break your device!"
live cd
you can download a live cd and run it on vm ware if do not want linux on your computer.
If you're still stuck @ravike14 can help you out!
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
As the title states, I have an HDX 7 currently sitting with an older firmware and Safestrap 3.70 (TWRP v2.6.3.1).
I haven't touched anything on it since February 2014. My daughter has been using it primarily, but she finally got her own tablet, so I'm reclaiming this one.
Currently, I frequently get a blue screen followed by the tablet rebooting when attempting to watch YouTube videos via the app. Further, I have to uninstall all updates to Google Play for it function at all.
As I recall I also modified some system file to prevent Amazon OTA updates.
I'd like to get this device caught up in terms of current trends. If someone could direct me to my best options and perhaps a guide, I'd really appreciate it. Much of what I'm seeing is for later firmware versions.
Also, if there is a method to retain root and recover the extra storage used by Safestrap, that would be ideal.
Thanks in advance!
PariahNine said:
As the title states, I have an HDX 7 currently sitting with an older firmware and Safestrap 3.70 (TWRP v2.6.3.1).
I haven't touched anything on it since February 2014. My daughter has been using it primarily, but she finally got her own tablet, so I'm reclaiming this one.
Currently, I frequently get a blue screen followed by the tablet rebooting when attempting to watch YouTube videos via the app. Further, I have to uninstall all updates to Google Play for it function at all.
As I recall I also modified some system file to prevent Amazon OTA updates.
I'd like to get this device caught up in terms of current trends. If someone could direct me to my best options and perhaps a guide, I'd really appreciate it. Much of what I'm seeing is for later firmware versions.
Also, if there is a method to retain root and recover the extra storage used by Safestrap, that would be ideal.
Thanks in advance!
Click to expand...
Click to collapse
Given your firmware level:
- verify device is still rooted (use towelroot if needed)
- flash twrp recovery
- update bootloader to v3.2.3.2
- unlock bootloader (try 1-click method)
- flash rom of choice (Nexus, CM 11/12/13), SlimLP)
Search through the forums for relevant threads. Ask questions along the way. You have some work ahead (hours) but a nice reward at the other end.
Is there anything special I need to do to remove Safestrap? I forgot to mention I deleted all of the other rom backups on the device and moved the rooted rom to the default slot to free up space. Pretty sure I have the original rom backed up on my desktop. Do I need to revert before doing any of the above?
PariahNine said:
Is there anything special I need to do to remove Safestrap? I forgot to mention I deleted all of the other rom backups on the device and moved the rooted rom to the default slot to free up space. Pretty sure I have the original rom backed up on my desktop. Do I need to revert before doing any of the above?
Click to expand...
Click to collapse
Thoughts:
- moving roms between slots (specifically stock) via backup/restore is generally a bad idea in Safestrap; consider yourself lucky if you used this technique
- if the rom in the stock slot (assuming FireOS 13.3.1.0) boots properly then you can safely remove Safestrap v3 via the uninstall option in the apk
- do not wipe anything in Safestrap nor execute a 'factory reset' from the native Kindle recovery menu (bad outcomes)
- keep WiFi off / airplane mode engaged unless you are 100% sure the OTA block is working
- snag a copy of Flashify to install twrp and the 3.2.3 bootloader update
- check MD5 checksums with ES File Explorer or another tool before flashing; especially important for bootloader update!
- backup your existing recovery with Flashify before flashing twrp; leave a copy on the device
- enable USB debugging in Kindle settings (optional but offers additional recovery options should something go wrong)
- flash twrp first and make sure it works (reboot to recovery; have a look around but don't change anything)
- reboot FireOS and then use Flashify to update bootloader. Did I mention you should check MD5?
Post when above tasks are complete or if you have questions. Cover bootloader unlock next. Be aware the above steps carry some risk including permanently bricking the device. Make sure you have a clear understand on what is suppose to happen; double/triple check everything before committing changes. Good luck.
So, I understand everything above other than uninstalling Safestrap via the .apk. Is this accomplished via the original apk I installed Safestrap with, or something separate. Also, will I lose root by uninstalling Safestrap?
Ignore the previous post. I've successfully uninstalled Safestrap and reinstalled TWRP. So far, I've attempted to update the bootloader via both TWRP and Flashify, but it's still showing 13.3.1.0 under the device information\system updates. Could this be due to whatever modification I made a couple years ago to prevent OTA updates?
PariahNine said:
So, I understand everything above other than uninstalling Safestrap via the .apk. Is this accomplished via the original apk I installed Safestrap with, or something separate. Also, will I lose root by uninstalling Safestrap?
Click to expand...
Click to collapse
- use the original apk to remove (uninstall) Safestrap v3 recovery; you do not need to uninstall the apk itself
- uninstalling Safestrap will not impact root
---------- Post added at 10:37 AM ---------- Previous post was at 10:30 AM ----------
PariahNine said:
Ignore the previous post. I've successfully uninstalled Safestrap and reinstalled TWRP. So far, I've attempted to update the bootloader via both TWRP and Flashify, but it's still showing 13.3.1.0 under the device information\system updates. Could this be due to whatever modification I made a couple years ago to prevent OTA updates?
Click to expand...
Click to collapse
The FireOS version number will not change following bootloader update. It is a separate 'component' whose version can not be independently queried or verified. Typically the system (what you see, ie: FireOS) and bootloader are updated together and share the same version identifier. In this instance are only flashing the bookloader update as FireOS will soon be replaced by a different ROM. No need to update it and assume the associated risks.
Ahh, gotcha. Problem I'm having now is getting the bootloader unlocked. I downloaded the 1-click file, ran the batch file, and Virtual Box was installed. Once it finished installing it opened up and showed two instances of 1-click, but then nothing happens in either Virtual Box or the cmd window opened by the batch file. If I double click on either instance of 1-click, the last line says it's loading the kernel, but it stays that indefinitely. I attempted closing out Virtual Box multiple times, reran the batch file, all with the same results, sans the installation of course.
PariahNine said:
Ahh, gotcha. Problem I'm having now is getting the bootloader unlocked. I downloaded the 1-click file, ran the batch file, and Virtual Box was installed. Once it finished installing it opened up and showed two instances of 1-click, but then nothing happens in either Virtual Box or the cmd window opened by the batch file. If I double click on either instance of 1-click, the last line says it's loading the kernel, but it stays that indefinitely. I attempted closing out Virtual Box multiple times, reran the batch file, all with the same results, sans the installation of course.
Click to expand...
Click to collapse
Hum. Best handled by @draxie who developed 1-click. Generally pretty responsive to forum posts. If 1-click doesn't do it can always try the manual approach (a LOT more involved but not risky). Let's see what shakes out.
This is what I'm getting from the batch cmd window:
VirtualBox does not appear to be installed
Downloading 'https://www.virtualbox.org/wiki/Downloads' to 'C:\Users\Pariah\Down
loads\1-Click\1-Click\dwnlds'
Download complete.
Downloading 'http://download.virtualbox.org/virtualbox/5.0.12/VirtualBox-5.0.12-
104815-Win.exe' to 'C:\Users\Pariah\Downloads\1-Click\1-Click\VirtualBox-5.0.12-
104815-Win.exe'
Download complete.
Launching the VirtualBox installer momentarily
Please complete the installation with USB support enabled
Installation complete.
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Virtual machine '1-Click' is created and registered.
UUID: 6b44be97-c931-47a5-8eeb-b780f5783b78
Settings file: 'C:\Users\Pariah\VirtualBox VMs\1-Click\1-Click.vbox'
VBoxHeadless: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -23021 (0xf
fffa613) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume2\Windows\Syste
m32\acaptuser64.dll: None of the 1 path(s) have a trust anchor.: \Device\Harddis
kVolume2\Windows\System32\acaptuser64.dll
VBoxHeadless: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\system32\ac
aptuser64.dll': rcNt=0xc0000190
Oracle VM VirtualBox Headless Interface 5.0.12
(C) 2008-2015 Oracle Corporation
All rights reserved.
Click to expand...
Click to collapse
And the 1-click instance in Virtual Box is showing "Booting the kernel."
Here is the method I used to block OTA updates.
Originally Posted by berndt_toast
Yeah, I agree. Staying rooted is difficult, but doable. I am still on the rootable version (13.3.1.0) and have stayed on it even through the OTA updates that have been released. I have stopped them from auto-applying (and from even being seen as updates) by doing the following:
I renamed otacerts.zip to otacerts.zip.old in /etc/security/
I also renamed com.amazon.dcp.apk to com.amazon.dcp.apk.old in /system/app/
Doing those prevent OTA updates from working and if you check for updates from the device, it says none are found (at least it has worked for me).
Click to expand...
Click to collapse
Do I need to undo this before proceeding with the bootloader update and unlocking?
PariahNine said:
Here is the method I used to block OTA updates.
Do I need to undo this before proceeding with the bootloader update and unlocking?
Click to expand...
Click to collapse
No - tasks ahead have no dependence on Amazon's update engine.
10-4. I attempted to find the manual method for unlocking the bootloader with no success. Not sure if I'm looking in the wrong section of the forum, or just overlooking it.
PariahNine said:
10-4. I attempted to find the manual method for unlocking the bootloader with no success. Not sure if I'm looking in the wrong section of the forum, or just overlooking it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/kin...bootloader-unlock-procedure-software-t3030281
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
You're going to need a Linux.
EncryptedCurse said:
http://forum.xda-developers.com/kin...bootloader-unlock-procedure-software-t3030281
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
You're going to need a Linux.
Click to expand...
Click to collapse
Can be accomplished from Windows but a royal PiTA to get the drivers right. Tough having to hold but you probably want to wait on @draxie unless you are very comfortable with device manager and working around unsigned drivers on Win 8/10.
Davey126 said:
Can be accomplished from Windows but a royal PiTA to get the drivers right. Tough having to hold but you probably want to wait on @draxie unless you are very comfortable with device manager and working around unsigned drivers on Win 8/10.
Click to expand...
Click to collapse
I'm actually running Windows 7 64; not sure if that matters. Perhaps why 1-click isn't working?
I'm trying to get Minimal ADB and Fastboot to work, but while my HDX is being detected while booted into the OS or TWRP, it's not in Fastboot mode for whatever reason. I've cleared out the old ADB drivers and reloaded them after plugging the HDX into a USB while in Fastboot mode, and still nothing. It's not showing up under 'adb devices' or 'adb fasboot'.
PariahNine said:
I'm actually running Windows 7 64; not sure if that matters. Perhaps why 1-click isn't working?
I'm trying to get Minimal ADB and Fastboot to work, but while my HDX is being detected while booted into the OS or TWRP, it's not in Fastboot mode for whatever reason. I've cleared out the old ADB drivers and reloaded them after plugging the HDX into a USB while in Fastboot mode, and still nothing. It's not showing up under 'adb devices' or 'adb fasboot'.
Click to expand...
Click to collapse
Yup - that's the driver issue I referenced. Recommend waiting for response from 1-click developer before diving in. Win 7 x64 not an issue.
Davey126 said:
Can be accomplished from Windows but a royal PiTA to get the drivers right. Tough having to hold but you probably want to wait on @draxie unless you are very comfortable with device manager and working around unsigned drivers on Win 8/10.
Click to expand...
Click to collapse
PariahNine said:
I'm actually running Windows 7 64; not sure if that matters. Perhaps why 1-click isn't working?
I'm trying to get Minimal ADB and Fastboot to work, but while my HDX is being detected while booted into the OS or TWRP, it's not in Fastboot mode for whatever reason. I've cleared out the old ADB drivers and reloaded them after plugging the HDX into a USB while in Fastboot mode, and still nothing. It's not showing up under 'adb devices' or 'adb fasboot'.
Click to expand...
Click to collapse
Davey126 said:
Yup - that's the driver issue I referenced. Recommend waiting for response from 1-click developer before diving in. Win 7 x64 not an issue.
Click to expand...
Click to collapse
If you want to give manual unlocking a try:
- use these drivers; you likely need to reinstall when flipping between adb and fastboot
- detail procedure
- suggest browsing this thread for additional info/tips. Lots of noise but some diamonds in the rough too
- careful not to go down a rabbit hole; some solutions are one offs that worked great for the poster due to their familiarity with a particular too, platform or technique
- unlike almost everything else with HDX you can not harm your device with bootloader unlock attempts. It will either work or not with no adverse consequences either way
There are a few excellent posts by @Cl4ncy, @jerryl and others (possibly one of mine) in different threads; unfortunately I wasn't able to surface them in a quick search. Nature of the HDX forums. A gold mine if information that is a bxxtch to access.
Before diving in you may want to flash CM11 or Nexus v4 which can be done with a locked bootloader. Both are rock solid KitKat based roms that will expose the full capabilities of your device and offer continuity to CM13 once unlocked.
Good luck.
First off, I wanna extend a heartfelt thank you to @Davey126 for basically holding my hand through much of the process, and @EncryptedCurse for offering insight as well; folks like you are the reason I've been apart of this community for several years and always come to first when I'm looking for solutions revolving around Android products.
Secondly, I'd like to share a couple of my experiences as a novice that may have others in the future. For whatever reason, I couldn't get 1-click to work on either of my Windows 7 machines with two totally different installations; one being Windows 7 Professional 64-bit, and the other being Windows Home Premium 32-bit. Ultimately I ended up upgrading my system to Windows 10 and was able to unlock the bootloader without any difficulty at all. With the fresh upgrade to Windows 10, I simply uninstalled VirtualBox and reran the 1-click batch file. One thing that should be noted is that there's no reason to click the box to run VirtualBox at the end of the installation process, and may be something that contributed to my confusion and the confusion of others. Secondly, a window for PuttyTel should open up after VirtualBox is finished installing, and the PuttyTel window is where all of the "magic" takes place. I didn't find any of these distinctions in any of the numerous posts I scoured through, though I may have overlooked them.
Either way, thanks again to the three of you... now I just gotta figure out which ROM I'm gonna slap on this bad boy. Been waiting nearly 2 years for this moment.
PariahNine said:
First off, I wanna extend a heartfelt thank you to @Davey126 for basically holding my hand through much of the process, and @EncryptedCurse for offering insight as well; folks like you are the reason I've been apart of this community for several years and always come to first when I'm looking for solutions revolving around Android products.
Secondly, I'd like to share a couple of my experiences as a novice that may have others in the future. For whatever reason, I couldn't get 1-click to work on either of my Windows 7 machines with two totally different installations; one being Windows 7 Professional 64-bit, and the other being Windows Home Premium 32-bit. Ultimately I ended up upgrading my system to Windows 10 and was able to unlock the bootloader without any difficulty at all. With the fresh upgrade to Windows 10, I simply uninstalled VirtualBox and reran the 1-click batch file. One thing that should be noted is that there's no reason to click the box to run VirtualBox at the end of the installation process, and may be something that contributed to my confusion and the confusion of others. Secondly, a window for PuttyTel should open up after VirtualBox is finished installing, and the PuttyTel window is where all of the "magic" takes place. I didn't find any of these distinctions in any of the numerous posts I scoured through, though I may have overlooked them.
Either way, thanks again to the three of you... now I just gotta figure out which ROM I'm gonna slap on this bad boy. Been waiting nearly 2 years for this moment.
Click to expand...
Click to collapse
Happy to hear you were sucesfull. Thanks also for sharing your experiences and insights. Should be helpful to others as they navigate through the process. Every nugget of new information helps!