Related
I was on RC19 with root. And I have the certs renamed to avoid the RC30 update.
In order to download a few apps from market, I renamed the certs back, and I renamed the updater.apk.
But it still goes to download the RC30 and reboot the phone. While it is booting, I took the battery out.
Now every time I power on, it still goes to the boot screen with a progress bar showing the update progress. So I keep the phone off now.
Is there still chance for me to go back to RC19 or update to a modified RC30 with root?
blues said:
I was on RC19 with root. And I have the certs renamed to avoid the RC30 update.
In order to download a few apps from market, I renamed the certs back, and I renamed the updater.apk.
But it still goes to download the RC30 and reboot the phone. While it is booting, I took the battery out.
Now every time I power on, it still goes to the boot screen with a progress bar showing the update progress. So I keep the phone off now.
Is there still chance for me to go back to RC19 or update to a modified RC30 with root?
Click to expand...
Click to collapse
Hey blues, give me an IM. I'll be darned if I let another phone be updated to RC30 when it can still be prevented
First, you didnt read about renaming the certs. You could have renamed the OTA certs and left the others which would have let you use the market fine. People need to be more careful with this crap and read better. Not to be a jerk, but these are expensive phones to be messing with like this and not paying attention. I would hate to see a bunch of new G1 users bricking their devices because they tried removing a battery during an update.
Darkrift said:
First, you didnt read about renaming the certs. You could have renamed the OTA certs and left the others which would have let you use the market fine. People need to be more careful with this crap and read better. Not to be a jerk, but these are expensive phones to be messing with like this and not paying attention. I would hate to see a bunch of new G1 users bricking their devices because they tried removing a battery during an update.
Click to expand...
Click to collapse
(registered just to post this, LONG time lurker)
Also, root is locked off for this reason. So people DON'T **** up their phones, and HTC/T-Mobile ends up paying out the ass because of something YOU screwed up.
At the OP, try this: Take the sdcard out, put the RC28 or 29 on the card (as update.zip), then throw it back in. Even without changing the keys to test keys, or being able to rename the certs, this would allow you to update and keep root access. Then you could install the modded RC30.
Wow. I can feel the love tonight guys . Take it easy, geez. lol. So he made a mistake and almost ended up with RC30 installed. That's a far cry from bricking your phone.
Heck, even I screwed up and accidentally installed RC30 on my first phone
JesusFreke said:
Wow. I can feel the love tonight guys . Take it easy, geez. lol. So he made a mistake and almost ended up with RC30 installed. That's a far cry from bricking your phone.
Heck, even I screwed up and accidentally installed RC30 on my first phone
Click to expand...
Click to collapse
No, but not reading correctly/renaming the wrong files could very very easily brick your phone. I'm not bashing him for almost upgrading, as that isn't really his fault (the updater is annoying as ****).
If T-Mobile has to replace thousands of bricked phones, do you really think Google would think twice about unlocking root?
I am back to RC19 now.
Here is what happened:
1. While the phone is booting, I removed the battery to stop the rc30 update.
2. I put rc29 as update.zip on the sdcard, and boot the phone.
3. While the rc30 update progress bar was moving on, I press alt+L
4. I saw the rc30 update is failed. It said some file under /cache is not correct.
5. And I saw the menu. then I press alt+S. It said unable to mount the sdcard. So the sdcard update failed either.
6. then I pressed the home+return, the phone boots. then I am back to rc19!
Not sure what happened!
Gary13579 said:
No, but not reading correctly/renaming the wrong files could very very easily brick your phone. I'm not bashing him for almost upgrading, as that isn't really his fault (the updater is annoying as ****).
If T-Mobile has to replace thousands of bricked phones, do you really think Google would think twice about unlocking root?
Click to expand...
Click to collapse
I challenge you to actually brick a G1 just be deleting or renaming files.
They're more resilient than you think. Granted, it's fairly easy to make it so your phone won't boot up into normal mode. But as long as you have a viable recovery partition, you can just reflash and be good to go.
The only way to brick a phone I can think of offhand, just by simple file manipulation, would be to overwrite /system/recovery.img with some random file, and then make some other change so that it wouldn't boot in normal mode.
JesusFreke said:
I challenge you to actually brick a G1 just be deleting or renaming files.
They're more resilient than you think. Granted, it's fairly easy to make it so your phone won't boot up into normal mode. But as long as you have a viable recovery partition, you can just reflash and be good to go.
The only way to brick a phone I can think of offhand, just by simple file manipulation, would be to overwrite /system/recovery.img with some random file, and then make some other change so that it wouldn't boot in normal mode.
Click to expand...
Click to collapse
I'm not actually going to try it, but if the phone doesn't boot, it is essentially a brick.
How would you go about recovering a phone that won't boot? With the official keys. Would the recovery screen allow you to reflash an official update, say bricked modded RC30 to official RC30, since the build versions are the same? I'd assume no.
The only way I could see recovering a bricked phone is if the updater allowed you to install versions <= the current version. Or if there is some kind of "is everything okay" check on important files to insure that the phone would boot, and if there isn't, allow an install that's = the current build.
Even so, the phones would still be bricked and would probably require customer service/return, which would cost T-Mobile quite a bit. Even if all they have to do is reflash it, time is money.
He means it won't boot into the normal screen but you could still boot into the recovery partition and wipe the phone clean.
And I believe you can install updates from the same version... I installed the RC29 update twice with no errors.
Gary13579 said:
How would you go about recovering a phone that won't boot? With the official keys. Would the recovery screen allow you to reflash an official update, say bricked modded RC30 to official RC30, since the build versions are the same? I'd assume no.
Click to expand...
Click to collapse
If you have the "official" recovery image, using t-mobile's proprietary keys, then you can always re-apply the same update that the recovery image is from. All of the official updates do a version check, which is performed against the version string that's stored on the recovery partition - in /default.prop, on the recovery initramfs image, and *not* against the version stored on the system partition - /system/build.prop. And all of the full updates so far allow you to reflash the same version you are on.
For example, in the full, official RC30 update, here are all of the version strings that it checks for. Your version must match one of these in order for the update to apply
"tmobile/kila/dream/trout:1.0/TC4-RC30/116143:user/ota-rel-keys,release-keys"
"tmobile/kila/dream/trout:1.0/TC4-RC29/115247:user/ota-rel-keys,release-keys"
"tmobile/kila/dream/trout:1.0/TC4-RC28/114235:user/ota-rel-keys,release-keys"
"tmobile/kila/dream/trout:1.0/TC4-RC19/109652:user/ota-rel-keys,release-keys"
"tmobile/kila/dream/trout:1.0/TC4-RC30/116143:user/ota-rel-keys,test-keys"
"tmobile/kila/dream/trout:1.0/TC4-RC29/115247:user/ota-rel-keys,test-keys"
"tmobile/kila/dream/trout:1.0/TC4-RC28/114235:user/ota-rel-keys,test-keys"
"tmobile/kila/dream/trout:1.0/TC4-RC19/109652:user/ota-rel-keys,test-keys"
Notice the first one, which is the same version as what the update applies onto the phone.
So assuming that you have a full update for the same version you are running, then the only way you could brick the phone is to hose both your recovery and boot (or system) partitions at the same time. If you just hose the recovery partition, you can boot up into normal mode and reflash a new recovery image. Or if you hose your boot or system partition, you can boot into recovery mode and re-apply the update, which will wipe the boot and system partitions and load a known-good version.
And if you have the modified recovery image, you can craft your own updates of course, and apply any version you feel like applying - modified or not.
Ahh, yes. It is a bit stronger than I thought, and I feel a bit more comfortable working with it .
But still. If someones phone doesn't boot, they will probably take it back to T-Mobile, not wait days for someone to post how you can restore it.
I doubt it. If they're doing something that could brick the phone, they (almost certainly) have root access, and they should realize that t-mobile will give them a new phone that probably won't be rootable (more and more likely as the existing RC28 units are sold off)
I dunno. I was in the Playstation Portable scene for years (was an admin at one of the largest sites at the time), people are pretty stupid.
Gary13579 said:
I dunno. I was in the Playstation Portable scene for years (was an admin at one of the largest sites at the time), people are pretty stupid.
Click to expand...
Click to collapse
Yeah, I guess I can't really argue against that
My opinion on this situation is one that it helps us overall
If a unit is bricked either due to a bad flash or poor understanding of why you need access such as root, then having fall backs such as JF is suggestions helps the community.
It helps build a strong collection of tools to recover units that are self damaged or accidentally damaged and allows an increase of people trying to do different things with the unit who wouldn’t necessarily try due to the risk of killing the devices.
Check out Olipro who actually enjoys the challenge of finding work arounds but detests the attention that it can generate (in terms of xda forums being on the top of google, and the potential more uneducated users ask simple questions repeatedly) Until JF stops with the helping im assuming he’s enjoying the android game too!
I know people don’t like long posts and you have probably skipped to this end part... But I would personally say that imo 90% of G1 users doesn’t actually need ROOT access anyway.
Imp
Okay, ill take this from the top.
Well i found out Cyan had a new rom available and i figured ill take the time to update to the newest rom i was on 4.1.1.1.1.1.1 (Whatever) and i first downloaded 4.2.3.1 and tried to flash it not knowing you have to download a recovery image so i had downloaded and flashed the recovery image on top of the 4.2.3.1 then when that was finished the phone said formatting radio or something then it rebooted then went back to the recovery screen next thing i see is the phone giving a message formatting cache and it didnt do anything for about 20 min i rebooted the phone and now im back at stock firmware without root.....
Do i go ahead and Root my phone again or do i have to do something else.
Any advice is much appreciated!
gamecheif said:
Okay, ill take this from the top.
Well i found out Cyan had a new rom available and i figured ill take the time to update to the newest rom i was on 4.1.1.1.1.1.1 (Whatever) and i first downloaded 4.2.3.1 and tried to flash it not knowing you have to download a recovery image so i had downloaded and flashed the recovery image on top of the 4.2.3.1 then when that was finished the phone said formatting radio or something then it rebooted then went back to the recovery screen next thing i see is the phone giving a message formatting cache and it didnt do anything for about 20 min i rebooted the phone and now im back at stock firmware without root.....
Do i go ahead and Root my phone again or do i have to do something else.
Any advice is much appreciated!
Click to expand...
Click to collapse
My advice... post this in the correct forum (which is Q&A).
gamecheif said:
Okay, ill take this from the top.
Well i found out Cyan had a new rom available and i figured ill take the time to update to the newest rom i was on 4.1.1.1.1.1.1 (Whatever) and i first downloaded 4.2.3.1 and tried to flash it not knowing you have to download a recovery image so i had downloaded and flashed the recovery image on top of the 4.2.3.1 then when that was finished the phone said formatting radio or something then it rebooted then went back to the recovery screen next thing i see is the phone giving a message formatting cache and it didnt do anything for about 20 min i rebooted the phone and now im back at stock firmware without root.....
Do i go ahead and Root my phone again or do i have to do something else.
Any advice is much appreciated!
Click to expand...
Click to collapse
Yeah that's why you must always read before flashing. You should reroot you phone to be safe. What bootloader and recovery system do you have now? Next time download the recovery image from htc and then flash ur image from cyanogen. ... and oh yeah POST in Dream Q&A next time. This forum is already cluttered as is already.
gamecheif said:
Okay, ill take this from the top.
Well i found out Cyan had a new rom available and i figured ill take the time to update to the newest rom i was on 4.1.1.1.1.1.1 (Whatever) and i first downloaded 4.2.3.1 and tried to flash it not knowing you have to download a recovery image so i had downloaded and flashed the recovery image on top of the 4.2.3.1 then when that was finished the phone said formatting radio or something then it rebooted then went back to the recovery screen next thing i see is the phone giving a message formatting cache and it didnt do anything for about 20 min i rebooted the phone and now im back at stock firmware without root.....
Do i go ahead and Root my phone again or do i have to do something else.
Any advice is much appreciated!
Click to expand...
Click to collapse
I am beyond fed up with people like you.
You are not contributing to Android development.
You are not helping anyone.
You're simply selfish, lazy, stupid, and a waste of time.
Sorry if that sounds extreme, but it's not that hard to read forum rules.
Did I read that correctly in that you flashed 4.2.3.1 over your 4.1.9xx w/e CM build and then flashed the HTC image afterwards? Ya that was incorrect. You did the process in reverse. Just read Cyanogen's first post in his thread (read it slowly just to make sure). It clearly states what to do.
gamecheif said:
Okay, ill take this from the top.
Well i found out Cyan had a new rom available and i figured ill take the time to update to the newest rom i was on 4.1.1.1.1.1.1 (Whatever) and i first downloaded 4.2.3.1 and tried to flash it not knowing you have to download a recovery image so i had downloaded and flashed the recovery image on top of the 4.2.3.1 then when that was finished the phone said formatting radio or something then it rebooted then went back to the recovery screen next thing i see is the phone giving a message formatting cache and it didnt do anything for about 20 min i rebooted the phone and now im back at stock firmware without root.....
Do i go ahead and Root my phone again or do i have to do something else.
Any advice is much appreciated!
Click to expand...
Click to collapse
Seems to me like someone didn't read the directions correctly on how to flash the ROM. You deserve it, but it's not the end of the world. I'm surprised this thread has not been moved or locked yet, but then again, Mods have enough trouble sifting through stuff like this as it already is. Oh what to do, what to do.
Start asking your questions in the right sub-forum (Q&A) (Theme) or even in (General), or simply search.......This isn't a developmental subject, Thank you.
Final result will be a ban for you up too 3 days.
If you persist on posting in wrong forums.
Thread Trashed!!
Update your PRI with No Factory Reset
First and foremost we would like to say thanks to Sprint/HTC for releasing this "PRI Fix" in the form of an OTA PRI 1.40 update push. If nothing more it serves us as peace of mind that we remain on the same page with them in our endevors to explore and possibly aid in the future development of this awesome Android Platform.
Update 08/30/2010 Please see post #3 for another possible upgrade method: STEP by STEP instructions to update to PRI 1.40_003 as posted by thisizaremix
Update 08/28/2010 There seems to be a few people getting the update with a battery pull as posted by chummer360 here is his posted response:
NAN BACK UP
##786#
WIPE
REBOOT
WHEN IT START THE HANDS FREE ACTIVATION (I CANCLED IT, THE SCREEN WILL STAY DARK, I PULLED THE BATTERY)
REBOOT INTO RECOVERY AND RESTORE AND REBOOT
IT WILL GO THROUGH THE UPDATE PROCESS AGAIN, LET IT DO ITS THING
CHECK THE PRI
Note: Some are letting the battery stay out for up to 30 mins which I am assuming basically confirms that the phone and server connection goes through a complete reset.
UPDATE 08/21/2010: There appears to be a much greater success rate when using the RA Recovery vs the Clockwork Recovery. You can get the latest RA Recovery here: http://forum.xda-developers.com/showthread.php?t=705026
Also there is an easier way to get your MSL now. Search for "MSL Reader" in the market.
After reading and re-reading this thread several times one would have to conclude that there is no clear cut method of recieving the PRI 1.40 update that is a universal factor of success. The only consistant variable is that there is inconsistant ways of achieving it...
As of now there are only two common denominators consistant in obtaining the update:
The ##786# master reset and the other as proposed by TheMike1 The ##3282# reset.
--------------------------
##786# Maters Reset:
1: Do a NAND Backup 1st...
2: Dial ##786#
3: Hit Menu
4: Press Reset
5: Enter your MSL 6 digit number
6: Phone will reboot into recovery mode
7: Wipe Cache/Dalvik x2
8: Reboot
The phone will go through handsfree activation and update the PRI to 1.40
If it did not just repeat the process until it does.
--------------------------
TheMike1: Why not cut to the chase and do a ##3282#?
This will allow you to Start the Hands Free Activation Process and update your PRI without forcing you to do a Factory Reset.
Steps:
1. Dial ##3282#
2. Enter Edit Mode
3. Enter your MSL
4. Select Data Profile
5. Menu
6. Restore
7. Let Phone Reboot, and Wait and the Hands Free Activation will Start.
8. Repeat until you have 1.40 PRI.
Both of these methods seem to work sporadically, so if it does not succeed the first time keep trying. Some people report success after 10+ attempts. At lease doing it with ##3282# does not require you to Wipe Your Data and is quicker/easier to repeat.
--------------------------
If you need you MSL call sprint and get it or try this link:http://forum.xda-developers.com/showthread.php?t=697487
--------------------------
If you are having problems with a specific ROM try flashing to a Custom Stock OTA ROM such as one of these:
Android 2.1 ('start over') Stock ROM
Netarchy Rooted 2.2 Stock ROM
SteelH Rooted 2.2 Stock ROM
--------------------------
I can't stress this enough: There is no magical method that will work for all users. Some of the factors are just out of our control such as the server's actual ability to push the update...either from overall traffic load or it is just not available in your area yet. The bottom line is that some will get it quick and some have been trying since it came out with all kinds of software variables...yet have not gotten it.
Just what this PRI update is actually doing for us still remains somewhat a mystery. Some claim dramatic increase in data transfer some don't. Me personally I have only seen maybe a brief increase in my overall ping...not much else. Once again a big Thanks to Sprint/HTC...
Seems interesting.... I'll have to try it.
STEP by STEP instructions to update to PRI 1.40_003
As posted by thisizaremix
After trying almost every way imaginable to update my PRI for a month, I finally seen a post of what someone did and I did what they did and got the update in one try.
I will attempt to give the best instructions I can on how to update the PRI on your EVO since I know so many people have been trying for so long now.
Step 1
Boot into Recovery and Nandbackup your Evo.
Step 2
Follow this link and follow the posters instructions for installing recovery RA-evo-v1.8.0.
forum.xda-developers.com/showthread.php?t=705026
Step 3
Follow this link and grab the zip for "HTC OTA Froyo 2.2, *FINAL*, build 3.36.651.6 (Rooted) Odexed" and put it on your SD card.
forum.xda-developers.com/showthread.php?t=743352
Step 4
Follow this link and grab the zip for "Fresh Evo 3.1.0.2" and put it on your SD card.
forum.xda-developers.com/showthread.php?t=743079
Step 5
Boot into Recovery and flash the zip file from step 3. (HTC OTA Froyo 2.2, *FINAL*, build 3.36.651.6 (Rooted) Odexed)
Step 6
Reboot system and when your Evo comes up and is finished loading, enter the dialer and put in ##786#. After it loads, choose MENU, then RESET, then enter your MSL number and accept the prompts to reset your Evo. Your Evo will power off and will start up in Recovery after it wipes the system. While in Recovery, follow the next step.
Step 7
Choose the menu for "Wipe"
Choose Wipe Cache and acknowledge it
Choose Wipe Delvik and acknowledge
Choose Wipe Cache again and acknowledge
Choose Wipe Delvik again and acknowledge
Step 8
Flash the "Fresh Evo 3.1.0.2" zip file from Step 4 and reboot system when it's complete.
Step 9
Wait 10 seconds after you see the "unlock screen" menu and then unlock it and let it contact the network and do it's thing.
When this is completed, you can check your settings and see if you have PRI 1.40_003 installed. Now you can boot back into Recovery and NandRestore your system that you backed up in Step 1.
I am confident that it will work for you if you follow the instructions exactly as it worked for me on the first try after trying to get this update for almost a month...
GOOD LUCK!
SteelH said:
This method is useless for anyone with a rooted phone.
Click to expand...
Click to collapse
Quite possibly the contrary now that unrevoked forever is out... I'm still watching that development...
This was just posted on the bounty thread by Zikronix
I JUST DID DAMAGE CONTROL ##786# master reset once
cleared dalvik, system reset wipes, etc
Rebooted hands free activation, I GOT THE NEW PRI
was running the current PRL and 134 before that
rebooted still have my ra, and I still have eng hboot
and I still have root
no unrevoked....none of that ****
Sent from my HTC EVO using Tapatalk
1st try now...
Code
What's the code i'll try it on non rooted
##786# but you need your MSL to do reset...believe me it works. They are now pushing the updated PRI to 1.40...
Worked for me. I had 1.34, rooted with toast, running stock rooted froyo.
Wishing, and hoping, and waiting.....
Assuming that this does indeed work for some, would doing this break root? Or could I just do this, get the updated PRI while reseting in the process, still have full root and nandroid back to my old setup?
SteelH said:
This method is useless for anyone with a rooted phone.
Click to expand...
Click to collapse
No it isnt... I am Fully ROOTED via Toast Method and it worked for me here is how
No Need for any Files
Do a NAND Backup 1st...
Dial ##786#
Hit Menu
Press Reset
Enter MSL (if you dont have it call sprint and ask for it they just gave it to me I told them I was having issues)
Phone will reboot into recovery mode (can not confirm that this will work for clockwork mod)
Wipe everything 2x
Reboot
The phone will go through handsfree activation then when its done just hit skip on the phone setup and go to menu settings about phone software to see if it updated
If it did not just repeat the process until it does. It took me 3x but others have reported it worked on the 1st and some say it worked on the 10th.
I'm fully rooted (toast's method) and now have the 1.40 PRI.
Doward said:
I'm fully rooted (toast's method) and now have the 1.40 PRI.
Click to expand...
Click to collapse
So if I do this, it'll reset my phone, go through the activation process (and maybe update my PRI too). Afterwards I'd still have root and could then nandroid back into my old setup but now with the update PRI?
Award Tour said:
So if I do this, it'll reset my phone, go through the activation process (and maybe update my PRI too). Afterwards I'd still have root and could then nandroid back into my old setup but now with the update PRI?
Click to expand...
Click to collapse
Correct... may take you a few times for it to update... have seen in the other thread it took someone 12 times.. It took me 3
jdawg0024 said:
Correct... may take you a few times for it to update... have seen in the other thread it took someone 12 times.. It took me 3
Click to expand...
Click to collapse
Thanks. And yeah, it has to be a server thing on HTC's end. When I first got my EVO it took a bunch of tries before everything updated correctly on my first initial activation.
And I apologize for the fact that this post was actually for non-rooters stuck on PRI 1.34....the other post by goonzy is for rooted users needing the upgrade. Either way it appears that both are achieving the update to some degree based on maybe the sprint server status and the actual push.
After saying all this and now that I am running PRI 1.40, I don;t see a real big difference in data transfer. My ping rate may be a bit better though...
Not sure what happen but I reset mine now the phone wont boot.
zone23 said:
Not sure what happen but I reset mine now the phone wont boot.
Click to expand...
Click to collapse
Take the battery out and replace try again?
Will the method work on fresh Rom
Okay so, I love my Infuse but getting really tired of not being able to download anything off the play store. Just tired of it's rather less than great performance right now as well. It's is running 2.3.6 GB and want to get this thing up to ICS if possible. Just something running 4.0 so I can use my phone for what I need too. It is not rooted, no cyanogenMod, NOTHING. As the title says, I'm a full on noob here and I apologize if all this is covered in other threads, however I have just gotten to the point where I have found myself even more lost than where I started on what I needed to do/get. If someone can, I will literally need this spelled out to me (no pun intended), in order of the steps I need to take with everything. I'm getting tired of confusing myself even more from all the different stuff I have seen all over the place and I know without some serious guidance, I will just brick my phone. Thanks for any help! :laugh:
I understand this community can be a bit unorganized and confusing so I'll give you my process for rooting and installing custom firmware (there are other ways, but this works for my AT&T Infuse 4G SGH-i997).
First of all, no one uses ICS on the Infuse. There is a ROM, but it's underdeveloped because JB came out so quick. You will need to flash it to get to higher operating systems, but it is by no means a daily driver. Even JB is a little buggy compared to KitKat on the Infuse these days.
The first thing you want to do is root your phone and get a custom recovery.
There are more than a few options for rooting, but I prefer using ODIN (as I understand it, this is the tool Samsung uses to restore soft bricked phones). So this is a good thing to know how to do, in case you ever do soft brick your phone, you'll know exactly what to do.
Read the ODIN instructions in full as I will only briefly explain.
You're going to have to install Samsung drivers.
You'll be using UCLB3_Unbrick_root_1.1.zip. If you used UCLB3_Unbrick_1.1.zip it would just get you back to stock GB with no root added.
To put your phone into download mode, first turn off your phone. Plug a usb cable into your computer. Then with the phone off, hold down both volume buttons and plug the usb cable into your phone. A warning will come up and you push volume up to accept, realizing that you can easily soft brick your phone if you loose power or unplug during a download.
Once downloading is done, the phone will reboot and you'll be disappointed to see that nothing has changed. Except one small thing, you are now rooted and you should have an application called SuperUser that will allow you to do nifty and also dangerous things.
Now follow this step in the ODIN instructions to add the custom recovery (CWM = Clock Work Mod):
The version with root works exactly like the above version, but adds root. To add CWM recovery to the rooted version, download a custom Gingerbread kernel from HERE or HERE and flash the zImage using SGS Kernel Flasher (found in the Play Store) on the phone. If you go this route for root and CWM, your Custom Binary Download counter will not show any custom binary activity.
Click to expand...
Click to collapse
If you follow the link in the second "HERE," you'll get the kernel I prefer since it was most recently updated. Scroll down the downloads section and grab "2013.04.30-CWM-Synthesis-1.2Ghz.zip." (1.2Ghz is stock for our processor, anything higher will be overclocked which I don't recommend).
Extract that and grab the zImage file in the update folder. You're going to copy this to your phone in a second.
But first you need SGS Kernal Flasher, you can get it off the playstore, but I despise having to log in to an OS I'm going to write over in less than a minute so I download the APK from here. Hopefully you know how to install APKs from your SD card and that you'll have to check install from unknown sources.
Now flash the zImage using SGS Kernel Flasher. Your phone will reboot and hang on the Samsung logo and a creepy voice is going to tell you about how she's partitioning your phone and installing Voodoo lag fix. This is normal. Eventually your phone will reboot back into GB and you'll be ready to flash any ROM of your choice by rebooting into recovery.
You reboot into recovery by holding the volume up and volume down button while powering on the phone. This is different than download mode and will take you do a new screen that you control with the volume keys.
You'll be using this to put new software on your phone.
Now you can bassically follow the instructions for getting to CyanogenMod 11 (Kit Kat) from GB.
The first bullet is what I just explained in detail.
Note that I didn't include the links in these instructions, just follow the link above to get to the original post.
Obtain CWM, this can be done using Jscotts Odin back to stock (Follow instructions and use SGS kernal flasher to obtain CWM)
Run Qksters IMEI backup script here
Make certain you are on ICS, this can be done by flashing Entropy's CM9
It is recommended now that you remove your SD Card
CWM: Wipe Cache / Factory Reset
Install ROM: Scroll down for downloads sectoion
... The package will start to install..
... Phone will reboot into the install screen again...
... Continue to install [Automatically] If not manually flash again
... Phone will reboot again and be at the recovery screen...
Install Gapps: Here - Working swipe!
CWM: Wipe Cache Partition
CWM: Advanced/Wipe Dalvik Cache
Reboot
Click to expand...
Click to collapse
To be clear, when you flash a ROM, it won't be like flashing the zImage (that was just to get custom recovery). To flash the CM9 ROM or Qksters IMEI backup script for example, you leave the rom in the .zip file and simply put it on your SD card. Once in the recovery screen, you select "Install Update from ZIP" and navigate to the particular ROM you wish to install.
Also after updating to a higher version of Android, your phone will sometimes hang on the install screen for a long time. If it does for more than five minutes, it's safe to pull the battery and try flashing again (and sometimes necessary).
After flashing Entropy's CM9, you will be on ICS, you can use if you want but I don't advise it. You should continue with the instructions and update to KitKat after getting to ICS. I recommend Scott's CM11 (what I linked you to) or Scott's BeanStalk (find it in the Android Development Section).
Lately I've been using CyanFox and I have to say, it's the most stable ROM I've used in a while.
If you have any questions about this, feel free to ask.
Best of luck and happy flashing,
~bokonon9
Thank you muchness!
Thank you very much for helping me in this mess! I greatly appreciate it. I love my Infuse and do not want to get rid of it quite yet so hopefully this will help! Once I get a new usb cord I will get on this. My toddler decided to get a hold of it and it has to set a certain way now and can't be moved. This, is no bueno! Anyways, THANKS AGAIN!!! :laugh:
Goodluck! :laugh: :good:
I'm new in the android world and I'm using a nexus 7 and an infuse to make experiments just to learn.
bokonon9, thank you! You're guide has been precious to me.
Unfortunately I only succeeded installing ICS, infact I get till here:
After flashing Entropy's CM9, you will be on ICS, you can use if you want but I don't advise it. You should continue with the instructions and update to KitKat after getting to ICS. I recommend Scott's CM11 (what I linked you to) or Scott's BeanStalk (find it in the Android Development Section).
Click to expand...
Click to collapse
I tried to install CM11 and even CM10 at least half a dozen times each, following step by step the instructions that I've found on the thread but all the times I have the same issue:
after the zip rom update and the reboot, the bootloader keeps launching the CWM recovery. I see the logo, the progress bar and then I land in recovery
I don't get any kind of error (and I don't know where to look for to get more information than what's shown on the screen) and I'm just stuck in the recovery and I have to start from scratch every time using Odin all the way down.
I'm not interested in Gapps so, at the beginning I tried without installing them but then I tried also using the appropriate gapps as indicated in the procedure. Either way I didn't get any solution to my problem.
Do you have an idea? Is there a way for me to provide more information or debug?
Thank you!
wwr said:
I'm new in the android world and I'm using a nexus 7 and an infuse to make experiments just to learn.
bokonon9, thank you! You're guide has been precious to me.
Unfortunately I only succeeded installing ICS, infact I get till here:
I tried to install CM11 and even CM10 at least half a dozen times each, following step by step the instructions that I've found on the thread but all the times I have the same issue:
after the zip rom update and the reboot, the bootloader keeps launching the CWM recovery. I see the logo, the progress bar and then I land in recovery
I don't get any kind of error (and I don't know where to look for to get more information than what's shown on the screen) and I'm just stuck in the recovery and I have to start from scratch every time using Odin all the way down.
I'm not interested in Gapps so, at the beginning I tried without installing them but then I tried also using the appropriate gapps as indicated in the procedure. Either way I didn't get any solution to my problem.
Do you have an idea? Is there a way for me to provide more information or debug?
Thank you!
Click to expand...
Click to collapse
i would say go back to stock gb with odin and basically start over but with ics i always let it reboot to get a "feel" for it then i reboot to recovery and wipe basically everything then flash the next level of android which should be cm 10 then i let that boot then repeat that to get to kitkat 4.4.3 CarbonRom....sometimes you have to flash the same rom twice to get it to flash tho
I already tried all that and I can't figure out a way out ... I'm really banging my head against the wall
wwr said:
I already tried all that and I can't figure out a way out ... I'm really banging my head against the wall
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2091900&page=370
read the last post on that page by scmfxt
So, I did a stupid thing this morning. I spent the last, probably, five hours backing up all of my apps and data from my TF300, and once that was all done, I wiped the data on my tablet. "What makes that stupid?" What makes that stupid is, it was a miracle that I ever actually managed to root this thing in the first place, and now, I don't know a) if it's still rooted (I doubt it), and b) if I'm even mentally capable of rooting it again (I doubt it).
So, here's my situation, and if someone could just dumb down the steps for me and point me in the right direction, that's all I need. I got my tablet, I don't know, probably early 2012. I can tell you that the tablet is on ICS 4.0.3, and the build number is 9.4.3.29-20120511. It's also unlocked, I don't know if that needed to be mentioned. Now, things are better since I wiped the data on this mother, but ICS, on this tablet in particular, is slow as balls, and I'm done with it, I want KitKat. But I am so far beyond lost after what I did that if I try to work my own way out of it, I'm going to brick this thing.
I wiped the data because I was trying to do something involving the Fastboot menu or something like that. Whenever I selected the USB icon and hit up on the volume strip, the tablet just locks cold. I figured whatever caused that, would probably go away with a data wipe. It didn't. So now my data's gone, my apps are gone, my tablet's not rooted anymore, I have no idea how to get to KitKat, I can't sleep at night, it burns when I pee... let's focus on the tablet stuff for now, I'm signed up to some forums for the other stuff.
I know most of the people that read this topic will be inclined to say, "You're an idiot, read this, this, and this, and take care of it yourself." I know I'm Androidiot, and I'm humbly asking for help. Again, I'm just petrified of following the wrong topic and ruining the whole thing, so if someone could tell me how I'd go about upgrading my tablet from stock ICS to KitKat, I'd appreciate the hell out of it.
Just a little bump, not too big... no love for Tim?
Normally, you need to install the latest stock ROM from ASUS in order to recover a functional device & by the way upgrade your bootloader.
Things done, you can proceed to install recovery and kitkat.
Better explanations here : http://forum.xda-developers.com/showpost.php?p=53738192&postcount=2
zlazaar said:
Normally, you need to install the latest stock ROM from ASUS in order to recover a functional device & by the way upgrade your bootloader.
Things done, you can proceed to install recovery and kitkat.
Better explanations here : http://forum.xda-developers.com/showpost.php?p=53738192&postcount=2
Click to expand...
Click to collapse
Thank you, Zlazaar!
Well, it seems that after my device was wiped, it still didn't remove CWM as a bootloader or whatever, I don't know what I'm saying. When I hold down the power and volume down buttons, I could wait like ten seconds for fastboot, or I could tap vol up to enter the "RCK" menu. I don't know what that means. But I go into it, and I'm at the CWM menu, I think it was 5.5.0.4. You probably know better than me if I need to do anything further than that with CWM, but I should be good on that, right?
I'm almost going to go to the sites that you mentioned to download files and get more information on how to use it all. I appreciate your help, because without it, I'm sitting on an unrooted stock ROM with only most of my apps, because oh yeah, like 70 apps forgot to transfer with that backup I did... so, whoopee.
Thank you again, buddy!
The goal is kitkat, right ?
So, in order to get it you need 2 important things :
1- The latest bootloader, yours can't handle kitkat.
2- a custom recovery supporting kitkat, i.e i'm using TWRP 2.7.1.0 (link in my signature), your CWM is outdated.
The only way i know to update the bootloader is to flash Stock ROM via fastboot as described in tutorial.
I got some really stupid questions... apparently it's been entirely too long since I've messed with any of this.
What's a bootloader? I know mine's unlocked, but I didn't know there were versions of it. Is it the blob file I got from Asus?
And I have my tablet hooked up to my PC, it's on the fastboot menu wait for input from USB. When I go to the command prompt, I've tried to push TWRP to the device, but when I start a command with "adb push," it just tells me that it doesn't know what to do with that command. Same thing happened with fastboot, but then I realize I didn't have fastboot installed, so I tried to install it and it complained about a missing dll file on my computer, and I think I'm about ready to give up. lol
Here is the driver : Universal Naked Driver
After install, you can use fastboot and complet other steps.
Tim 13 said:
I got some really stupid questions... apparently it's been entirely too long since I've messed with any of this.
What's a bootloader? I know mine's unlocked, but I didn't know there were versions of it. Is it the blob file I got from Asus?
And I have my tablet hooked up to my PC, it's on the fastboot menu wait for input from USB. When I go to the command prompt, I've tried to push TWRP to the device, but when I start a command with "adb push," it just tells me that it doesn't know what to do with that command. Same thing happened with fastboot, but then I realize I didn't have fastboot installed, so I tried to install it and it complained about a missing dll file on my computer, and I think I'm about ready to give up. lol
Click to expand...
Click to collapse
Ok Tim so the GOAL IS: 4.4 KITKAT CORRECT?
This is the process overview. This is a review.
Step 1 Upgrade the bootloader. Why? Inorder to flash a 4.4 rom you need a Jelly Bean 4.2 bootloader. How? Do as zlazarr suggests by flashing the lastest stock version V10.6.1.27.5 on your tf300t. Flashing the latest stock rom will update your bootloader. And here's another helpful guide.
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/ Remember that the SKU has to match!
Step 2 Follow this guide.
http://www.transformerforums.com/fo...nstall-roms-tf300-jelly-bean-kitkat-roms.html
It guides you on how to unlock your bootloader which you already have and it shows you how to install twrp. After installing twrp MAKE A BACKUP!
NOTE: If using the command method on the link fails repetitively use the app rashr to install the twrp version in the link
Step 3 Upgrade twrp to vr 2.7.0.0 or higher. Refer to step 2 link on the post about 4.4 kitkat.
Step 4 Install a 4.4 kk rom. I recomend the lastest snapshot of Cyanogen Mod 11. The download is on their wiki.
And then your done! Don't give up! The hardest part I find is using the command prompt! Look for work arounds. AND SEARCH FOR METHODS!
Goodluck
b..c said:
Ok Tim so the GOAL IS: 4.4 KITKAT CORRECT?
This is the process overview. This is a review.
Step 1 Upgrade the bootloader. Why? Inorder to flash a 4.4 rom you need a Jelly Bean 4.2 bootloader. How? Do as zlazarr suggests by flashing the lastest stock version V10.6.1.27.5 on your tf300t. Flashing the latest stock rom will update your bootloader. And here's another helpful guide.
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/ Remember that the SKU has to match!
Step 2 Follow this guide.
http://www.transformerforums.com/fo...nstall-roms-tf300-jelly-bean-kitkat-roms.html
It guides you on how to unlock your bootloader which you already have and it shows you how to install twrp. After installing twrp MAKE A BACKUP!
NOTE: If using the command method on the link fails repetitively use the app rashr to install the twrp version in the link
Step 3 Upgrade twrp to vr 2.7.0.0 or higher. Refer to step 2 link on the post about 4.4 kitkat.
Step 4 Install a 4.4 kk rom. I recomend the lastest snapshot of Cyanogen Mod 11. The download is on their wiki.
And then your done! Don't give up! The hardest part I find is using the command prompt! Look for work arounds. AND SEARCH FOR METHODS!
Goodluck
Click to expand...
Click to collapse
Okay, so I've started work on this finally, but I think I might be having some trouble. I flashed the latest stock ROM onto my baby and restarted the tab like the article said, but now it's taking a very long time to load. I don't know if it's supposed to be taking this long, considering I'm pretty sure it wiped the data on it (flashing a ROM wipes data, doesn't it?), so I'd assume that removing the weight of those apps would make startup lightning quick.
I have the ASUS logo and the spinny circle. And it's just spinning and spinning and spinning and spinning. Is this a problem?
I'm going to let it spin spin spin spin spin for like five more minutes, and then I might go cry for a while.
EDIT: I cried too soon, it loaded for a long time then came to a menu that says "Android is upgrading..." and it's optimizing the apps, or apptimizing, that were apparently NOT wiped when I flashed a new ROM. lol, so I'm back on track. So far, so good. Thank you for the detailed guide, I appreciate it!
Further edit: And I'm also done rooting and flashing to KK 4.4. Thank you for dumbass-proofing the process for me, it is incredibly highly appreciated. I didn't kill my tablet!
Tim 13 said:
Okay, so I've started work on this finally, but I think I might be having some trouble. I flashed the latest stock ROM onto my baby and restarted the tab like the article said, but now it's taking a very long time to load. I don't know if it's supposed to be taking this long, considering I'm pretty sure it wiped the data on it (flashing a ROM wipes data, doesn't it?), so I'd assume that removing the weight of those apps would make startup lightning quick.
I have the ASUS logo and the spinny circle. And it's just spinning and spinning and spinning and spinning. Is this a problem?
I'm going to let it spin spin spin spin spin for like five more minutes, and then I might go cry for a while.
EDIT: I cried too soon, it loaded for a long time then came to a menu that says "Android is upgrading..." and it's optimizing the apps, or apptimizing, that were apparently NOT wiped when I flashed a new ROM. lol, so I'm back on track. So far, so good. Thank you for the detailed guide, I appreciate it!
Further edit: And I'm also done rooting and flashing to KK 4.4. Thank you for dumbass-proofing the process for me, it is incredibly highly appreciated. I didn't kill my tablet!
Click to expand...
Click to collapse
Hi Tim13,
I'm glad to hear that everything went well and my guide helped you!:good: And to answer your question flashing doesn't wipe your data. You have to manually wipe it. And lol:laugh::good: that you didn't kill your tab. I hope you find your tab faster and useful again!
It's just as slow and useless as it was. But honestly, the flashing process was fun, and I learned from it. Plus, TWRP and Cyanogen mod are awesome, and now I know that. lol
Great to see you up and running @Tim 13 :good:
Can you add SOLVED to the thread title
Thx Josh
No, I'm not gonna do that.
I'm just kidding. You're all right, darling. :good:
Edit: Actually, not being a douche, I can't figure out how to edit the thread title. I went to edit the first post and I can't change the title of the post... I'm gonna look around for how to do it a bit more but after that I'm gonna go to bed.
DOUBLE EDIT: Got it, as you can see. Thanks to all that helped out!