Related
This guide will enable you to easily root your phone in 6 steps. I've taken out the mystery and complications.
1) Go to HTC Dev site and manually unlock your bootloader. Select "register" and create your account.
1a) After you are registered select "all other supported models" in the pull down box
1b) Click "begin unlock bootloader". it will ask "are you sure" yes of course you are. acknowledge legal terms. then continue.
1c) Ignore the battery pull instructions as we can't pull the battery. hold down the power key and the volume down key until the bottom buttons stop flashing and your phone shuts off (don't worry if you take a screenshot. It happens all the time). then release ONLY THE POWER BUTTON. Keep holding the volume down key until the bootloader screen shows up.
1d) Follow "step 3" and the rest of the instructions as listed on the HTC site to unlock your bootloader manually.
2) Install android ADB/SDK on your pc. This video shows how to do it nicely:
2a) ****NEW UPDATED 03/05/13*** Alternatively if you DON'T want to install ADB/SDK you can just download the NON-FLASHABLE platform-tools.zip file located in my dropbox folder here.
Just extract this folder to your desktop using WINZIP or whatever archive tool you use and proceed to step 3.
3) Open a command line in your "platform-tools" folder by holding shift+right click anywhere within the folder and selecting the menu option "open a command window here". Then click here to install TWRP using fastboot. Follow the "Download - Fastboot Method:" instructions.
3a) If your phone isn't detected by windows please install the proper USB drivers for your operating system. Go here for 32bit. Go here for 64 bit.
4) Flash SuperSu and Busybox on your device:
4a) Click here and download the latest version of SuperSu. save it to your sdcard.
4b) Go to my dropbox and download Busybox 1.20.2 and save it to your sdcard.
5) Reboot into recovery (via the bootloader selection)
6) Flash the SuperSu zip and the Busybox zip listed in 4a and 4b
That's it!
"So now what?" you may be asking.
You are now free to flash ROMs that support s-on.
Two are my favorites are
(1) Stock with Goodies. (my personal favorite and the one I use today). This is a great ROM for beginners and people who prefer a slimmed down ROM (minus the bloat) and lots of free memory!
(2) Viper4G. This is a ROM for more experienced users and offers TONS of customization.
You can also run apps from Google play that required ROOT access!
If you're feeling slightly adventurous you can flash a custom kernel (which will allow you to overclock your phone). Two of the kernels I use are:
(1) ElementalX by flar2. Click here to take a trip over there. This one is especially important to flash as it seems HTC was up to shenanigans with the latest HBoot (2.09).
If you're unlucky enough to have HBoot 2.09 they have RESTRICTED access to your /system partition. What does this mean to you? It means that if any app writes to your /system partition (ROOTED or not) the phone will "panic" and reboot. Shady behavior if you ask me. The solution? Flash this kernel! it will give you write access so that everything works properly.
(2) The Arc-Reactor kernel! This one is for people that are s-off (see below for an explanation of s-off) only! It's the kernel I currently use and is the fastest kernel out there! Highly recommended if you decide to go s-off!!!
If and when you're feeling more adventurous you can go "s-off" (security off) which removes any security limitations of your phone. It makes flashing ROMs and updating firmware a lot easier. You can find out about s-off by taking a trip over to the DirtyRacun thread here. I will NOT walk you through this process. They will totally help you on their IRC channel. Just read post # 1 in that thread.
There's also a new method of s-off which literally takes 2 minutes. It's called facepalm and is located here But is NOT for the feint of heart, bad typers, nor people that cannot follow instructions! Why? One typo here and your phone is a brick. A paperweight. Useless. Well...you can recover...but that's not the purpose of this thread. If you DO brick your phone PM me. I'll help you out.
I take NO credit for any of this. It's all out there to learn I just put it all together. In one spot. Any questions feel free to PM me.
If I helped you out hit the THANKS button...or buy me a beer! Either way lol!
Tested and works with 3.16.651.3 (even if you took the OTA and have hboot 2.09 and are s-on)
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
lancemoreland said:
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
Click to expand...
Click to collapse
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
rawintellect said:
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
Click to expand...
Click to collapse
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
lancemoreland said:
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
Click to expand...
Click to collapse
Indeed this is a well documented problem but really not what this thread is about. Perhaps you can check out THIS thread where they are discussing this issue at length and hopefully they will come up with a solution for it?
http://forum.xda-developers.com/showthread.php?t=1538053
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
rawintellect said:
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
Click to expand...
Click to collapse
Yes I am participating in that thread. Chainfire is looking for a work around for his specific app, other apps that write to the system partition will no longer work. The point is that with Hboot 2.09 there are limitations and we will not enjoy full root as we have before when we were s-on.
Updated with an alternative superuser program.
SuperSU would ask to update binary and then just reboot. This fixed my problem for being able to access/deny and turn off messages. However it did not uninstall superSU will this cause a conflict having them both?
Edit: Okay I am dumb, I had to uninstall superSU first. Then I reflashed superuser to be able to have root privileges for my apps. When I just reflashed superuser hoping it would get ride of and superuser and keep root it did not.
Thanks it worked!
Help with rooting please.
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
MrSteez said:
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
Click to expand...
Click to collapse
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Updated thread with instructions on manually uninstalling supersu first before installing superuser 3.2
Thank you very much!
rawintellect said:
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Click to expand...
Click to collapse
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
MrSteez said:
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
Click to expand...
Click to collapse
yes. going back to stock is as simple as this:
(1) Boot your phone into the bootloader. make sure fastboot is selected. if you have the drivers installed correctly your phone will read "fastboot usb"
(2) if you followed my instructions on rooting you have ADB/SDK installed. so issue the command to relock your phone. type: fastboot oem lock
(3) run the RUU for 3.15.651.16. Done. Your bootloader will say *relocked* but it will be 100% stock.
Uh oh
I think i messed up. I did not see busy box installed and SuperSU is not updating.
The file listed in step 6 contains busybox. It also contains supersu. You want to flash the superuser file after flashing the file in step 6. It will overlay supersu with superuser 3.2. There is no need to update superuser 3.2 once you flashed it. It is the latest release.
Sent from my EVO using xda app-developers app
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
mobilecj said:
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
Click to expand...
Click to collapse
I replied to your email. But check my first post on the subject of superuser and how to uninstall supersu. if you need to that is. I tested this myself and it did uninstall supersu for me by just flashing superuser 3.2. Some people have reported this doesn't work for them.
okay sorry just got both i am going to try it now.. Its all knew to me it seemed like the information was explaining a dual process and i only had acquired one problem.. will post back in a few!
Hello everyone,
Here is the sad tale:
I recently got my Kindle Fire HDX and immediately started fiddling with it. Got it rooted and installed GApps using KindleFree. I then decided to buy KindleFree Pro to tweak even more. I fiddled around with the custom launcher option and basically bricked the device all within the same day that I got it! I'm not sure what that option changed exactly behind the scenes but I was able to ADB in and noticed that Launcher-release-signed_82046410.apk has a size of 0kb... that can't be right so I figured I'd start there...
First, I'd like for someone to confirm the size of theirs, if it isn't 0kb (which I doubt it will be) then can someone kindly upload that APK so I can load it up and hopefully get this thing working again?
Alternatively, can anyone suggest a way to simply reflash the stock rom via ADB somehow? I never installed safestrap and I don't think it can be installed via ADB. At least not that I've seen.
Thanks!
ok sorry
mkid89 said:
Hello everyone,
Here is the sad tale:
I recently got my Kindle Fire HDX and immediately started fiddling with it. Got it rooted and installed GApps using KindleFree. I then decided to buy KindleFree Pro to tweak even more. I fiddled around with the custom launcher option and basically bricked the device all within the same day that I got it! I'm not sure what that option changed exactly behind the scenes but I was able to ADB in and noticed that Launcher-release-signed_82046410.apk has a size of 0kb... that can't be right so I figured I'd start there...
First, I'd like for someone to confirm the size of theirs, if it isn't 0kb (which I doubt it will be) then can someone kindly upload that APK so I can load it up and hopefully get this thing working again?
Alternatively, can anyone suggest a way to simply reflash the stock rom via ADB somehow? I never installed safestrap and I don't think it can be installed via ADB. At least not that I've seen.
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2786190 and that's why we have safestrap so you don't modify your stock http://www.youtube.com/watch?v=K6fPF5UZsWw
There are a few Devs still working on a way to flash something from fast boot no ETA means no promises seems the only fix for you may be to call Amazon . And maybe someone will chime in with a way to sideload an app I'm not sure. Good luck
I should have listened to the warnings when people said it was easy to brick! I've been modifying devices since the windows mobile days before android and never once have felt this hopeless! Safestrap will be the first thing I do once I get this running again.
The good news is I still have SU root access in ADB without needing a Fastboot cable. I'm thinking everything else but the launcher loads so it is pretty much fully functional but with no gui. It sometimes will even boots to the lock screen but unlocks to a black screen.
I think I should be able to sideload the launcher if someone can get me the apk.
well
mkid89 said:
I should have listened to the warnings when people said it was easy to brick! I've been modifying devices since the windows mobile days before android and never once have felt this hopeless! Safestrap will be the first thing I do once I get this running again.
The good news is I still have SU root access in ADB without needing a Fastboot cable. I'm thinking everything else but the launcher loads so it is pretty much fully functional but with no gui. It sometimes will even boots to the lock screen but unlocks to a black screen.
I think I should be able to sideload the launcher if someone can get me the apk.
Click to expand...
Click to collapse
If your patient somebody savvy enough will come by. and actually I know that I have read that someplace here I couldn't tell you where sorry. And if you're hoping for somebody to drop off the apk for you probably should let them know which firmware you are. Or you could always download the Bin file of your current firmware and exract it. Downloaded to an android rename it .zip and extract
That's a good idea but I don't know where to get the bin file or how to confirm I have the correct one. I had just updated so I believe it was the latest version. I'm thinking it's v13.3.2.1 or maybe v13.3.2.4 it said there were no more updates available so it should be the latest.
It's an 8.9. Don't think I mentioned that.
well
mkid89 said:
That's a good idea but I don't know where to get the bin file or how to confirm I have the correct one. I had just updated so I believe it was the latest version. I'm thinking it's v13.3.2.1 or maybe v13.3.2.4 it said there were no more updates available so it should be the latest.
It's an 8.9. Don't think I mentioned that.
Click to expand...
Click to collapse
8.9 is 14.3.2.4 https://s3.amazonaws.com/kindle-fire-updates/update-kindle-14.3.2.4_user_324002120.bin
Thank you for your help! I actually got it working shortly after my last post but got right into installing safestrap. ?
I'll post a write up tomorrow on what needed to be done in case anyone else has the issue. It's late where I'm at so I need to get some rest before trying to write it all up!
Ok! Now that I have a fresh mind I can document the steps I took to correct this issue.
How did this happen to begin with? I think that when I tried to set a custom launcher as default using KindleFree Pro, the launcher I selected was unable to load properly or something interrupted the process. Either way, it either would only load to the lock screen or just sit on the boot animation. I'm thinking the way that KindleFree works is that it replaces the default launcher apk with a link that points to the launcher you want to replace it with (hence the 0kb size). Either that or something got corrupted during the process of changing the launcher. I'm not sure what KindleFree does behind the scenes so this is all just speculation.
Anyways, on to the good stuff. Once I noticed the launcher was 0kb, thats where I decided to direct my troubleshooting efforts. I posted this thread hoping someone would upload the stock launcher for me to replace it with but jimyv gave me the idea to just grab it from the bin. I ended up finding the bin file here: http://www.amazon.com/gp/help/customer/display.html?nodeId=201357190 before he replied with the direct link. The "Download Software Update" link is a direct link to the .bin file. I changed the extension, opened it up and found the launcher apk per jimyv's suggestion.
Once I had the file, I needed to get it onto the HDX. I more or less followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2588608
Instead of replacing the odex files, I replaced the launcher apk under /system/app/ As soon as it had finished copying over, the device went from the boot splash screen to the lock screen in what can only be described as a magical moment.
Interesting to note: Most people say that if you perform a factory reset from the stock recovery, your hopes of using ADB and having root are gone unless you get a factory/fastboot cable. I actually did perform a factory reset but for some reason was still able to use ADB and did not lose root access. I had used TowelRoot to root the device so I'm wondering if that is a more permanent means of rooting compared to other methods? Either way, I'm glad I didn't lose root. Otherwise I would have needed to wait for a factory cable to be shipped and to root it via ADB.
Fyi that Chinese root method which is posted early on in the rollback thread it will root with ADB only.. And the factory reset thing has not really been consistent throughout each user.. But more or less we have been advising people not to because the chances are greater that you will lose the superuser binaries and you definitely will lose safestrap if installed. What is hard to get through to people is when they are in a boot loop they get in a hurry and start factory resetting and that is not always the best option. Depending on exactly what is going on. Most of the time it is people losing their ADB access and cannot figure out how to uninstall the MTP drivers first then install the ADB drivers..
Good job getting your device back online and thank you very much for the closing write up .
mkid89 said:
Ok! Now that I have a fresh mind I can document the steps I took to correct this issue.
How did this happen to begin with? I think that when I tried to set a custom launcher as default using KindleFree Pro, the launcher I selected was unable to load properly or something interrupted the process. Either way, it either would only load to the lock screen or just sit on the boot animation. I'm thinking the way that KindleFree works is that it replaces the default launcher apk with a link that points to the launcher you want to replace it with (hence the 0kb size). Either that or something got corrupted during the process of changing the launcher. I'm not sure what KindleFree does behind the scenes so this is all just speculation.
Anyways, on to the good stuff. Once I noticed the launcher was 0kb, thats where I decided to direct my troubleshooting efforts. I posted this thread hoping someone would upload the stock launcher for me to replace it with but jimyv gave me the idea to just grab it from the bin. I ended up finding the bin file here: http://www.amazon.com/gp/help/customer/display.html?nodeId=201357190 before he replied with the direct link. The "Download Software Update" link is a direct link to the .bin file. I changed the extension, opened it up and found the launcher apk per jimyv's suggestion.
Once I had the file, I needed to get it onto the HDX. I more or less followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2588608
Instead of replacing the odex files, I replaced the launcher apk under /system/app/ As soon as it had finished copying over, the device went from the boot splash screen to the lock screen in what can only be described as a magical moment.
Interesting to note: Most people say that if you perform a factory reset from the stock recovery, your hopes of using ADB and having root are gone unless you get a factory/fastboot cable. I actually did perform a factory reset but for some reason was still able to use ADB and did not lose root access. I had used TowelRoot to root the device so I'm wondering if that is a more permanent means of rooting compared to other methods? Either way, I'm glad I didn't lose root. Otherwise I would have needed to wait for a factory cable to be shipped and to root it via ADB.
Click to expand...
Click to collapse
could i use this way to fix my fault at this link bro?
http://forum.xda-developers.com/kin...p-kindle-fire-hdx-8-9-doesnt-able-to-t2816663
I took a look. That's a totally different issue than my issue. Mine wasn't getting stuck on the recovery screen. Sorry.
First of all, I apologise if I have posted this in the wrong section. Secondly, please be aware right now that the device in question is the S3 4G VERSION. Very different to the vanilla S3. I have dabled in rooting/flashing and general messing around with android firmwares before so I have a mild understanding but please be patient
Now the problem: Rooting. It shouldn't be hard. Should it? Not with tools like chainfires auto rooting kit these days... Alas, CF's auto root isn't doing it for me. At first I was having dramas with KNOX (congrats on loosing a long time customer there samsung). After i got rid of that with the de-samsungizer kit flashed through CWM it stopped showing the stupid "an application has attempted to gain root access and was blocked" crap. However SuperSu continued to crash, I'm assuming because the root was not properly completed. NO error codes or anything are ever returned from Odin, or CWM, everything looks like its happy but just not rooting. Confirmed with rootchecker.
Now a couple of other things I should mention: CWM keeps getting erased or something aswell? Like I'll turn the phone off to go into recovery mode, and im sitting at the bone stock one again, with the little red exclamation mark over my poor android corpse D:
I even tried disabling auto-reboot in ODIN when flashing CF's auto root, droppping the battery and manually starting recovery mode. I get excited when I see the red pirate-droid executing instructions, all goes well, everything is happy, still no root -_-
EDIT: In download mode, knox still exists and has logged EVERY attempt i've made. so everything is definitely executing just fine...
This is also my first time rooting in the presence of KNOX
I don't know what else to do... Am I missing something? is there a glaringly obvious thread or bit of information I've missed?
Thank you in advance for any help provided.
Ok so I took a break from this for a while cos i got really busy and didn't fancy doing MORE work on my phone when i finally got a spare tic. However, I came back to it today and managed to find a magic combination.
I AM NOT RESPONSIBLE FOR BRICKING YOUR DEVICE, PLEASE FEEL FREE TO CRY IN A PM ABOUT IT THOUGH I COULD DO WITH A LAUGH.
The following is a guide for anyone having issues making the root stick on their GT-i9305 samsung galaxy s3 4G/LTE on android 4.3. DO NOT ATTEMPT THIS ON ANY OTHER OS VERSION, VARIANT OR DEVICE.
I noticed a particularly important piece of information in the following link: How to Fix Android 4.3 Jelly Bean Rooting Problem for Galaxy S3/S4/Note 2/3 - W0lfDroid
A superSu update. So i went there grabbed that package ( SuperSU Download for update package ) and started my grand master plan. If you would like to actually read what hte user said yourself, its in a quote bubble naer the bottom, just before the comments.
now. Using an important piece of information in a thread I cannot, for the life of me, find through my browser history (apologies) I grabbed a copy of pihlz touch which you can find in the following thread: [CWM][PhilZ Touch][GT-I9305] 4.00-b21 Touch … | Samsung Galaxy S III I9300, I9305 | XDA Forums
Now. grab yo-self a copy of busybox's supersu root How to root Galaxy S3 I9305 with SuperSU 1.02 - Samsung Update located on that page. Make a folder on both your phone's internal storage and external, name them both the same thing and something you will remember. For instanceI called mine Root stuff. I only do folders on each of them in case I can't extract from external for whatever reason, its not necessary. Put both the supersu update you downloaded earlier and the one you just downloaded from above, busyboxes root, into both of these folders if you did it my way.
To avoid having to reboot your phone an extra time, make sure you did the above step BEFORE moving on
First up, I flashed philz touch with Odin (ensure you have the latest version, use your PDA checkbox and be sure that auto reboot and F. reset time are checked). Next up, turn your phone off and boot into your magnificent (no seriously, this is amazing. Its like a GUI in todays BIOS's...) new CWM recovery mode. Go into advanced and hit reset permissions or something like that... My phone is downstairs atm and I CBF in going and getting it and rebooting. Note that I am unsure if this is actually an essential part of the process, this is something I did because I worried about the permissions on the phone after my, by KNOX's count, 15 attempted flash operations -_- More like freaking 20 thousand....
Now once you have done that, go back to the main menu and tap install zips. FIRST you select the actual root, supersu1.02 busybox. Next, select the extra zip file option and que the UPDATE supersu-v2.02 after the actual root package. Once you have done this, swipe to install. THESE TWO PACKAGES MUST BE IN ORDER!!!!
Thats all I did. My phone rebooted and I was able to use Root checker to conform the root, allowed access to supersu and no crashing. Finally. THat was way too hard.
Thank you for hosting the website gentlemen/ladies where we can all come and share knowledge.
all credits go to anyone/webpage I linked people to and the brilliant programmers that made the packages. And finally, a HUGE thanks to Google and Linux (from which android is based) for freeing us from the shackles of iOS.
I've followed all the threads I can find here, and I've had no luck. Here's the situation. I had my S4 set up with root and the Stang5litre rom for a very long time. I wanted to put Xposed on it, and I completely forgot that it's not Odin friendly. First, I wanted to put TWRP on there, and that's where I messed up. I used the TWRP Manager app, and it said it was successful. On reboot I got the "Software Update Failed" screen. I can't get into recovery, but I can still get into download mode. Odin fails with everything I try saying either "Fail (Auth)" or that line 2012 could not be read. I found a thread here that looked very promising, but the files are no longer available, and I'm not even 100% sure that this is the best solution for me. I'd be happy with getting stock back, with the goal of later getting root and Xposed back on there. I've never been stumped with this before, but now I finally have to admit I need some help. I'd post an Odin log, but I want to know what I SHOULD be flashing, what settings to use, etc., and I'll send that log when I get it if it fails.
Valkrist said:
I've followed all the threads I can find here, and I've had no luck. Here's the situation. I had my S4 set up with root and the Stang5litre rom for a very long time. I wanted to put Xposed on it, and I completely forgot that it's not Odin friendly. First, I wanted to put TWRP on there, and that's where I messed up. I used the TWRP Manager app, and it said it was successful. On reboot I got the "Software Update Failed" screen. I can't get into recovery, but I can still get into download mode. Odin fails with everything I try saying either "Fail (Auth)" or that line 2012 could not be read. I found a thread here that looked very promising, but the files are no longer available, and I'm not even 100% sure that this is the best solution for me. I'd be happy with getting stock back, with the goal of later getting root and Xposed back on there. I've never been stumped with this before, but now I finally have to admit I need some help. I'd post an Odin log, but I want to know what I SHOULD be flashing, what settings to use, etc., and I'll send that log when I get it if it fails.
Click to expand...
Click to collapse
Why can't you go to Sammobile and download all your system files there, then flash them with Odin and start from square one? Or just use google to look for the required system files. Just put everything back the way you had or want it. I picked up an SGH 1337 AT&T phone and had to reflash everything to it with Odin. Yes, it was ponderous but it taught me a few things and steps which is why I hang out here anyway. Let me know if I can assist.
Valkrist said:
I've followed all the threads I can find here, and I've had no luck. Here's the situation. I had my S4 set up with root and the Stang5litre rom for a very long time. I wanted to put Xposed on it, and I completely forgot that it's not Odin friendly. First, I wanted to put TWRP on there, and that's where I messed up. I used the TWRP Manager app, and it said it was successful. On reboot I got the "Software Update Failed" screen. I can't get into recovery, but I can still get into download mode. Odin fails with everything I try saying either "Fail (Auth)" or that line 2012 could not be read. I found a thread here that looked very promising, but the files are no longer available, and I'm not even 100% sure that this is the best solution for me. I'd be happy with getting stock back, with the goal of later getting root and Xposed back on there. I've never been stumped with this before, but now I finally have to admit I need some help. I'd post an Odin log, but I want to know what I SHOULD be flashing, what settings to use, etc., and I'll send that log when I get it if it fails.
Click to expand...
Click to collapse
whatever android version your using or had, you can only odin back to that version an up. no downgrading. id think thats why your getting an auth failure. as for the twrp, far as i know, you cant have any custom recovery on a locked bootloader. however, you can use flashfire app to flash a required file to get xposed. i have tried it and works perfectly on the i545. you just get the alpha 3 i think apk of xposed and then get the zip of arter and be sure it matches your architecture. in my case it was krait. so i downloaded the krait zip and flashed using flashfire. took ten minutes or so to rebuild the cache. then all xposed worked perfectly. i believe there is a guide somewhere on here explaining it all. just be careful for if you flash the wrong zip, you get force closes in apps and the uninstall zip to correct it didnt work so i had to start over
The only thing that you can do is use odin to restore the stock firmware which you had beforehand.
THIS IS A CLOSED CASE, GO HOME. The answer is Hairybean found in step 2 of here [ROM] [TF201] KatKiss 5.1.1 - v30 [MultiWindow] [Stable] [RRO] Read the rest of this post if you're a sadist or want to know of people in the same pain boat as you.
Part 1: My life's story. Skip to Update if you just want to hear of my current problem.
So approximately 12 hours ago, I decided, "Hey, I want to upgrade my tablet so I can download the newest and coolest apps. Since I need to upgrade to a newer OS (ICS>KK ?) I may as well go through the extra hurdle and download a nice, fast custom ROM because the stock feels like crap for the lightweight that is the TF201."
Now me, not having ever touched an android in my life before this tablet, knew this was going to be a challenge. After doing plenty of research into unlocking, flashing a custom recovery, general custom ROM flashing etiquette, and following this guide ([ROM] [MM 6.0.1] KatshMallow v29 [TF201]), I encountered my first of many hurdles. This being: I was able to boot just fine, but the Wifi was in a perpetual state of "Wifi turning on..." I put a total of a couple or so hours into researching this and easily found others having the same issue, albeit not specifically to the exact ROM and device in question. I also tinkered a bit in these hours, reflashing and rebooting and all that jazz. I eventually settled upon one of three conclusions:
The "/persist" folder had gotten deleted which contains vital wifi/network configuration data
wlan0 was borked on a hardware level and I managed to completely kill an hope of wifi on my device
There was a MAC address somewhere that I needed to manually edit (that WASN'T in the persist file)
Considering the fact that I could not see nor change directory via adb terminal (yes, with su) into a "/persist" folder, and that the hardware-broken devices other users had were most if not all cellphones, I pushed on ahead assuming #1 to be my problem. ("See" includes dropping and installing a file explorer onto the tablet as well.)
With this is mind, the next course of action was to somehow get this "/persist" folder back. It seemed like the best way to do this would be to flash a stock ROM (link in Part 2) or ask the community to give me files without even trying to solve things on my own. So in the spirit of remaining a lurker I chose the former. Flashed fine, booted fine, ran.... okay-ish (the status bar "System UI" would crash every 10 seconds, ROM was a means to an end so I didn't care), but the Wifi WORKED! However, I still didn't find a /persist folder and the tablet didn't show up in windows... "Weird but okay, whatever let's do this." Load up recovery again, wipe everything, see if I can get Katshmallow to load again...
Part 1.5: And here we are. tl;dr I'm a scrub at anything android and after 12+ hours of tom****ery, I'm in a bootloop using Katshmallow v29 (v27 made no difference). The "bootloop" is in the form of the ASUS logo appearing with the usual "UnLocked" message in the top for a minute or two, then a reset, rinse, repeat. I am able to boot into recovery and mess around in TWRP just fine, so my ignorance hasn't completely wrecked me... yet.
The information that I believe is most pertinent to my current issue is:
I unlocked using ASUS' utility for the TF700. It worked no problem and with how compatible things seem to be between the two, I don't think this is an issue (especially considering I've flashed and booted system more-or-less just fine).
The most recent ROM I flashed was this [ROM] TF201 JB JRO03C 10.4.2.15 (US) Stock Deodexed + Mods [Unlocked BL]. I figure that this did something (maybe changed the bootloader?) that Katshmallow does not agree with. If I hadn't already spent the better half of a day working on trying to get things working, maybe I would do more research and figure out the inner workings on my own, but I'm done bashing my head against a brick wall that's only pushing me further back.
I am currently running KANG TWRP 2.8.7.2 for the TF201T (yes, the device I'm specifically running). The problem existed with some TWRP 2.8.x for the TF300 as well.
The bootloader message is "Android card-hu-user bootloader <1.00e> released by "US_epad-10.4.2.15-20120917" A03 ... Oh son of a-
Part 2: So I'm a dumb*** who can't read. Okay, I need to know how to get from my current bootloader (10.4.2.15) to the one Katshmallow requires (10.6.1.27.1). In typing this, I realized that the stock ROM I used to test stuff is why I've been screwed for the past 5 hours (coupled with my ignorance of course). In my quick 2 minutes of research I found this: [GUIDE][13/11]Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked/Locked Devices. I fancy methods 2 and 3, I can do those, but that doesn't change the fact that I know NOTHING about the bootloader and what I need to update it (but apparently I know how to give myself a headache by downgrading it).
Any help will be greatly appreciated. Oh, and if you know of how to solve the Wifi issue or the likely related /persist folder issue in the wall of text above, please I beseech you to tell me.
Disclaimer: My "research" is not at all limited to the links in the post. I've spent 90% (or more) of what's now probably 13-14 hours working on getting this piece of- getting things to just go right. So... tired...
Update: The problem has changed to my second post that I will be pasting here to save people the trouble:
So the problem as it stands now. I'm cannot seem to flash a different custom recovery and whenever I try to flash a ROM I get "E:Error executing updater binary in zip" The line above it, "symlink: some symlinks failed". I give up for now... Maybe I'll try again tonight. I'm running bootloader 10.4.2.15 and TWRP KANG 2.8.7.2 (which seems to require a 14.10 bootloader). In this mess, I don't know what to fix nor how to fix it. The angles I see are fix the custom recovery or fix the error/symlink problem since the bootloader version seems to be dependent on successfully flashing ROMs.
Update2: So I managed to upgrade the bootloader by somewhat forcefully flashing Hairybean. While Katshmallow said "JB 4.2.1 BOOTLOADER VERSION 10.6.1.27.1," I glazed over this because I didn't know the importance of the bootloader and there was no other mention of the bootloader in the post (no mention of Hairybean or a download link or a "More information" link). I still have no one but myself to blame, just bitter that I have to blame myself in the first place.
For the time being, I'm following the somewhat better instruction on found in this thread([ROM] [TF201] KatKiss 5.1.1 - v30 [MultiWindow] [Stable] [RRO]) and will be picking up Katshmallow at the "wipe" step (currently waiting on the /data format). I downloaded the newest version of TWRP for TF201T and it's working just fine (note how that thread also doesn't mention anything aside from "MUST BE ON THE HAIRYBEAN BOOTLOADER ENDING IN 27.1" While that's such an obvious and blatant statement that should have inspired some research, my ignorance blinded me).
Now that I know for a fact that I am running the right TWRP and the right bootloader, I am going to pray that I can at VERY LEAST flash and boot into Katshmallow. Whether or not the Wifi problem persists will be for another thread.
IT BOOTS! YAAASSS. How do I close this embrassment of a thead?
Sorry I can't be of more help but what I CAN say is:
- read instructions thoroughly with any release. Sometimes a modified TWRP or other file is posted that you must use even if you have a newer version. You might also have to bounce around to other posts along the way to install/update all of the necessary files.
- keep a written log of changes you've made with notes on reversing them. Changing the bootloader means you can't go back unless you revert it back first. I can back track everything I've done based on my own notes, much easier to understand than someone else's notes or directions.
Good luck and be patient. Don't make more than one change at a time and get it working or revert back before trying something totally different.
Sent from my LG-H811 using Tapatalk
HorthLithperer said:
Sorry I can't be of more help but what I CAN say is:
- read instructions thoroughly with any release. Sometimes a modified TWRP or other file is posted that you must use even if you have a newer version. You might also have to bounce around to other posts along the way to install/update all of the necessary files.
- keep a written log of changes you've made with notes on reversing them. Changing the bootloader means you can't go back unless you revert it back first. I can back track everything I've done based on my own notes, much easier to understand than someone else's notes or directions.
Good luck and be patient. Don't make more than one change at a time and get it working or revert back before trying something totally different.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Thank you for replying nonetheless. I'll keep the note thing in mind. Regarding the bouncing around to get the files necessary, I've done plenty of that. When installing a new ROM, I made sure to follow the links as they were given and did further research where things weren't clear. My current problem stems from that fact that, 1: I have no point in which to restore back to due to my aforementioned ignorance and oversight of basic Android terminology; and 2: The next step is to revert the bootloader, that of which I have no clue how to do or where to start since my preliminary google search. Even if I had been taking notes, no one mentions how to do this without a backup. And so I'm on a hunt to find this information and for posterity, I'll post my quest here:
Google search: "tf201 bootloader version"
Upgrading from ICS Bootloader > [ROM] [TF201] [JB Bootloader] CyanogenMod 10 Unofficial - JZO54K - Oct 30 2012 - I learned that apparently certain ROMs can overwrite the bootloader, extrapolated from:
4) Needs the new Jelly Bean 10.4.2.15 bootloader [IMPORTANT: Flashing over an incorrect bootloader can permanently brick you device. The Oct 13 2012 build includes the bootloader upgrade and can be flashed over any ROM/bootloader]
Google search: " update tf201 bootloader"
[GUIDE] How to manually update/restore firmware (TF101, TF201, TF300, TF700, TF701) - Post #2 sent me to ASUS official support wherein I downloaded "V10.4.2.18." This is a test in hopes that I can get a ROM running and see if the bootloader changes. I'm not able to use the methods in that thread as I do not have a system nor a microSD, as such I'll flash it the way I have been. Same custom recovery as before. Run the usual wipe (Dalvik, System, Cache, Data, Internal). Drop ASUS ROM onto pad's internal. Attempt flash... Error: "E:Error executing updater binary in zip"
More research, now trying to find out what this error is. Tried this and read a couple pages from here. Settled on reflashing TWRP. While looking up the command again, I came upon here, then went to the first post of that thread here, then from the TWRP link in that post to here (yes, I see the big TF700T at the top, I also see the big MUST BE ON A BOOTLOADER ENDING IN 14.10).
Okay so, I have 10.4.2.15 and am going to have to jump through several hoops to get to the mysterious 10.6.1.27.1. Annnnd It seems as though I have a custom flash that doesn't support my bootloader (which I feel should've been an issue up until now?) I just want to boot into A ROM, so either I find a ROM that supports the bootloader and probably flash a recovery that does as well...
Googled: "10.4.2.15 tf201" Came upon this, tried to flash twrp2.3.1.0 for the tf201 (downloaded straight from their website)... Still in 2.8.7.2 ... Okay, what? FINE! Screw it, redownload the stock ROM that got me into this mess (here) and see if I can even flash that. Wipe all the usual but internal storage because I'm lazy and afaik it doesn't need to be wiped anyway. Error: "E:Error executing updater binary in zip" The line above it, "symlink: some symlinks failed". Popped into here, unmounted the things, reformatted /data to f2fs (this may just be a Marshmallow thing though... it was ext_4 before I reformatted) Same error... Kill me.
So the problem as it stands now. I'm cannot seem to flash a different custom recovery and whenever I try to flash a ROM I get "E:Error executing updater binary in zip" The line above it, "symlink: some symlinks failed". I give up for now... Maybe I'll try again tonight. I'm running bootloader 10.4.2.15 and TWRP KANG 2.8.7.2 (which seems to require a 14.10 bootloader). In this mess, I don't know what to fix nor how to fix it. The angles I see are fix the custom recovery or fix the error/symlink problem since the bootloader version seems to be dependent on successfully flashing ROMs.
I'm sure there's someone out that that can point to me the correct tree in this forest using their superior knowledge of the subject. Having grown up with computers, even a new error message is something to work with. But when you can't even get results (success nor detailed failure), then it becomes downright no fun.