Database Info

Kernel/ota questions

I've successfully recovered my tablet using this method. I was trying to update my TF using the batch script method and somehow managed to flash an outdated kernel. I know this because Asus tech support told me that was the reason my TF wasn't receiving the ota to 3.2. However, Asus tech support also told me that I could flash a new kernel by downloading the source code onto my tablet, then the TF would automatically recognize the [.rar] file and install my new kernel; which didn't work out as you might imagine.
I am now on official 3.1 8.4.4.11.and my kernel is v 2.6.36.3-00011-g3eb19ex And I can't get the OTA update. At one time I had official 3.2 [after previously flashing stock 3.1] but decided to try to root when I found out Netflix wasn't officially supported like the EEE pad site says it does.
Every time I try the batch script method, I end up stuck on the eee pad logo screen. Adb is working as well as apx drivers. Ultimate goal here is stock 3.2 rooted with netflix, but at this point I'd settle for stock official 3.2.
Any ideas? Tia

You may get help if you post your QUESTIONS in the correct forum.
This is the development forum....not Q&A.
Sent from my Jailbroken iPhone 4 using Tapatalk.

Thanks for the input. I just felt that that based on the content of the question, it would be better suited here.

you could try the zip file from the thread titled [OTA]Stock 3.2 zip file
And +1 on wrong section. This is not related to developing a new ROM or features for the Eee Pad.

I'm trying to avoid flashing CWM, that's where I end up bricking it.

jdmnash said:
I'm trying to avoid flashing CWM, that's where I end up bricking it.
Click to expand...
Click to collapse
I would suggest you to try Nvflash. it is the easiest way to root that tf.

I think the relationship between nvflash and the TF is complicated.
There are a few bootloaders out there, including the one used by custom roms, as well as the 4 stock ones.
My theory is that the kernel images in the boot and recovery images have to match the bootloader that is on the TF.
Throw in the fact that the bootloader is only written using the nvflash --create command or during the OTA update, and we have TFs with all kinds of different bootloaders going around that won't match what people are flashing. I think this is why CWM breaks whenever there is a stock OTA that rewrites the bootloader. I think most people brick trying to go back to stock from a custom rom. Going from stock to custom usually isn't a problem because the compatible bootloader is flashed in the rooting process.
Is this the first time we've seen an completely unlocked bootloader on Android?
sent from my cyanogen(mod) vision

jdmnash said:
Thanks for the input. I just felt that that based on the content of the question, it would be better suited here.
Click to expand...
Click to collapse
No. Android Development is for "DEVELOPMENT" does this thread have any kind of release? No.
That's why there's a sticky thread that says,
[REF] SEARCH BEFORE POSTING!! All Questions Go In The Q&A FORUM!!
Originally Posted By: mskip
Click to expand...
Click to collapse

ok folks i get it. I'm sorry. Is there anything I can do right now about accidently posting this in the wrong forum? Please forgive me. Mods feel free to move the thread or ban me or both. Whatever the normal punishment is.

Use the NVFlash unroot method here:
http://tabletroms.com/forums/showthread.php?1071-Asus-Transformer-NVFlash-Stock-3.1-Recovery-Roms
That will get it back to stock everything with 8.4.4.5. Then, you can manually install 8.4.4.11 with the download on the Asus website. After that it will recognize the OTA update to 8.6.5.6. Once you've done all that, use the Batch Script for a quick root, and you're done. I did this today. As long as you follow all the steps, it's a breeze.

I don't think it will recognize the OTA update to 8656. Roach's update will work, but not the stock update.
sent from my cyanogen(mod) vision

It will recognize it, because if you follow all the steps I listed, you're completely stock until you run the batch script to root 3.2. I did this myself on my transformer today.

My OP is not very clear, but that is exactly the steps I've followed to get to where I am today. I've given it 2 days to detect the new update and i've got nothing. I'm currently sitting on stock 8.4.4.11 waiting for the OTA.

kingwp1 said:
It will recognize it, because if you follow all the steps I listed, you're completely stock until you run the batch script to root 3.2. I did this myself on my transformer today.
Click to expand...
Click to collapse
How did you root before and what were you running before you went back to stock 8445?
sent from my cyanogen(mod) vision

stock 3.2. I was trying to get rooted 3.2 to get netflix

jdmnash said:
stock 3.2. I was trying to get rooted 3.2 to get netflix
Click to expand...
Click to collapse
Did you ever make a backup with CWM when you had 3.2?

no it was stock 3.2 firmware/recovery
I'm making progress. I'm now on rooted 8.4.4.11... still trying to get to 3.2

[Q] How Do I Downgrade from ICS to Honeycomb?

Can anyone tell me how to downgrade back to Honeycomb or point me to the enigmatically-named forum post?
I'm running stock 4.0.3, kernel 2.6.39.4.
Please don't hang me if this is already on here somewhere. I did search, but all I found was version numbers and frankly, a lot of stuff I didn't understand.
From the Moderator: Doing a proper search will yield the right results. To find in a search you need to take your original query and then rearrange the word order sometimes to find. oka1
I recently did the OTA update to ICS. Since then I have had power drain, random reboot, and problems connecting to Wi-Fi.
Any help would be greatly appreciated.

Being you're on stock ROM, the only way is if your tf is nvflash compatible.
Serial # B60 or previous (some B70)

B50
My serial starts with B50, so I guess I'm at least in a good starting place.

Loremonger said:
My serial starts with B50, so I guess I'm at least in a good starting place.
Click to expand...
Click to collapse
Yes the B50 certainly is NVFlash compatible.
Here are a lot of NVFlash ROM, I don't see the latest HC (.21) ROM but try searching here or Google.
http://www.tabletroms.com/forums/tr...stock-3-2-recovery-roms-unbricking-tools.html
or it might update itself in stage up to .21 (not 100% sure on this)

Thank you, baseballfanz, that at least gives me a starting point.
From the Moderator: Doing a proper search will yield the right results. To find in a search you need to take your original query and then rearrange the word order sometimes to find. oka1
Click to expand...
Click to collapse
Well, at least I didn't post in the developer's forum. Anyway, it doesn't matter how much you manipulate the search, it won't yield results that aren't on this forum.

What abt 101G S\N B90 running ICS 9.2.2.3 ? How to downgrade to HC ?
Note: Don't have root and can't root

hearts king101 said:
What abt 101G S\N B90 running ICS 9.2.2.3 ? How to downgrade to HC ?
Note: Don't have root and can't root
Click to expand...
Click to collapse
Sorry, dude. But from what I found out today, it looks like anything above B70 is "in the works." Something should be out soon, but for now, it looks like you're stuck. I would check this post regularly to see if an update is available for later models.

I did that yesterday hoping that with a clean stock installation would fix problems (and it's working great until now, but as all we know problems come in a random way with ics).
So, I found on the net an nvflash 8.6.5.13 ww rom (full with bootloader, kernel and recovery).
Backup all your stuff first.
I booted into cwm, complete wipe, including /data/media.
Put tf in apx mode, nvflash complete rom, boot it.
After then I configured wifi and a notification about updates appeared. I did that and my tf was upgraded to 8.6.5.21 ww.
Then you can use that, flash cwm with nvflash, flash any honeycomb rom.
Instead I upgraded it with stock 9.2.1.17 ww rom (using official upgrade notification), because I want to see if it works correctly for me (100% stock without root, 9.2.1.17 is not rootable without flashing over a modified rom or with ota rootkeeper)..
Only time will tell if problems are gone for me on ics...

I am so lost

Just got an Infuse a few days ago. It was running froyo 2.2.1 I believe. It was on AT&T, but I wanted to unlock to use with StraightTalk on AT&T. I did get the unlock code and rooted it. I then upgraded it thru Samsung's site to the 2.3.6 Gingerbread. In the process of this, I managed to lock up my laptop when installing Kies and had all kinds of issues. Needless to say, my persistance paid off after spending several hours reading here. Got it all up and working on ST.
Since today was my day off, I decided I wanted to remove the AT&T bloatware from it so off to googleville again and ended up here. Started reading and then found that when I did the Gingerbread update, my phone was unrooted again. Needless to say, after reading around here all day, I decided I wanted to give ICS a try and have been reading about ParanoidAndroid. I am now on pg 31 of 62 and am getting nowhere fast.
I don't want to ask for spoonfeeding, but I am confused about alot of this coding stuff. I have had some flashing experience years ago in ....well, don't guess I want to mention that, but anyhow, it seemed overwhelming until I got my feet wet in it. I have to say, this GB bootloaders, Aroma, non-Aroma, cm7, cm9, red CWM, and blue CWM has me more confused than a fat kid in a candy shop in some foreign country.
In all honesty, I think I could read here for a week and still not be sure on which way I need to go. As I said, I am interested in ICS (ParanoidAndroid) but don't know if I have the GB bootloaders or not and not sure where to start at. The firmware version os showing 2.3.6, Baseband I997UCLB3, Kernal version 2.6.35.7-I997UCLB3-CL977492, and finally a Build of Gingerbread.UCLB3. Yesterday, I was using SuperOneClick and 010 editor. Now I am reading about Odin, Heimdall, and several other programs that I don't know which to start with.
Could somebody please help out this fat kid in a foreign candy shop? I don't even think I can find a Hershey bar. Thanks.

How did you get to gb?
Kies?
Odin?
Cwm?
Which package did you use?
Sent from my SAMSUNG-SGH-I997

qkster said:
How did you get to gb?
Kies?
Odin?
Cwm?
Which package did you use?
Sent from my SAMSUNG-SGH-I997
Click to expand...
Click to collapse
I used Kies mini. I d/l Kies and the file and followed the instructions at Samsung's own website. samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00045587&fm_seq=46249

Be patient... there are a lot of helpful people here and qkster is among the best.

boatboy63 said:
I used Kies mini. I d/l Kies and the file and followed the instructions at Samsung's own website. samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00045587&fm_seq=46249
Click to expand...
Click to collapse
This method will give you the gb boot loaders.
Your next step is to flash a custom kernel.
Follow my signature links to the heimdall method of kernel flashing.
If you are more comfortable with odin, jscott has made some great packages also.
Once you have flash the kernel, just boot into cwm and go from there. If you wanted paranoid, then flash the ROM in cwm.
If you use a gb kernel, for now, it will be red letter.
If you use heimdall jt ics kernel, you will see blue letter.
I rec the jt kernel as you are planning to go ics
Gl
edit:
this is the ics kernel I was referring to:
http://forum.xda-developers.com/showpost.php?p=25526654&postcount=3
flash in download mode.
boot into cwm -3 fingers technique - flash the ics rom you want - follow the OP instructions

Confused about OTA update

Ok, so I got a message for the OTA update today (ver 67.21.125.en.US). Now, I see all these threads that say don't apply the OTA because you can't flash back. But they seem to be talking about if you are already IN ICS. I am running a custom mod version of the supercharged 2.3.6 rom.
Is this the official ICS update? Should I flash all the way back to stock and then just do the OTA's? Will that process make it so I will not be able to FXZ back?
Or Should I follow the instructions in this thread? --> http://forum.xda-developers.com/showthread.php?t=1779968
The only question I have about the above linked thread is I am not sure if that info is out of date regarding this update I just saw today. If the OTA that came up today is nothing new (and it just took forever for me to see it for whatever reason) and everything in that thread still applies, then I will probably go that route. However if this is a new/different update, then I dont know what to do.

Bump

Look here, it has everything you need to know, to make your own decision.
http://forum.xda-developers.com/showthread.php?t=1882335

extide said:
Bump
Click to expand...
Click to collapse
All of your questions have been answered numerous times in numerous threads over the past week.
I suggest to read - A LOT - then, make the choice whether to go on the official ICS (your phone must be in stock 2.3.6 GB condition), or non-official leak#1 which you linked (which yes, we are still able to downgrade with leak#1 ONLY).
If you are going to go on custom roms in the end, then it really doesn't matter... and in my opinion, I'd prefer to have the option to FXZ if I'm in trouble - so I'm personally sticking with leak#1 as a base firmware - at least until we get an FXZ package for the official at&t 4.0.4 ICS.

Ok, I suppose I should have phrased it better, but my main question/concern was whether I was seeing a newer update than what all those threads were talking about. It seems as though I am not.

[Q] Colorful screen bootloop

Have a t959V SGS4G with Froyo. I rooted it, and unlocked it. I then attempted to flash AntonX's "Basic with a Twist SGS4G KJ6 1.1.3" kernel using the SGS Flash tool. It seems that this Kernel is a Gingerbread Kernel, which I flashed on a Froyo system.
When it rebooted after that flash, the screen became multicolored, almost like static and gibberish, and is not boot looping. It wont get past the initial Galaxy S 4G splash screen. I tried the multiple means of accessing download mode with no success. I did just order a jig, but that wont be here for a few days.
Prior to flashing the new kernel, I did backup the old kernel, so its on the SD card.
Any thoughts on how to recover?
Many thanks!!

Use the guide in the second link of my signature and flash with bootloaders. You do not have GB bootloaders which is the reason for the rainbow screen.

rainbow screen - bootloaders
lumin30 said:
Use the guide in the second link of my signature and flash with bootloaders. You do not have GB bootloaders which is the reason for the rainbow screen.
Click to expand...
Click to collapse
ks for your reply. That guide is impressive. i can see a lot of work was put intot hat. It looks like I would take this option:
2.This guide can be used if you flashed a ROM made for a different model phone (i.e. Vibrant):
----> Follow Directions for Flashing WITH BOOTLOADERS
However, I didnt flash the whole ROM. Just the kernel. So, I have aapparantly a Gingerbread based Kernel with a Froyo Rom. In this case, do I want to go to a FROYO kernel, or go to a Gingerbread (or a JB??) ROM?
I have the ultimate goal of going to a JB ROM. I'm starting to think I cant just flash the JB ROM over the Froyo, or can I? I'll have to peruse the forums a bit to learn more about that.
Finally - I cant seem to access download mode via any of the methods presented. I ordered a jig, so when that arrives, I'll follow the guide and either downgrade the kernel or upgrade the ROM.
This devide seems a bit more complicated to work with than the Nexus S that I was previously toying with.
Thanks for your input and assistance.

What are you doing?! Stahp!
You are still in Froyo? Why not migrate to Gingerbread?
By the way we only have ICS, for now.

socalg said:
ks for your reply. That guide is impressive. i can see a lot of work was put intot hat. It looks like I would take this option:
2.This guide can be used if you flashed a ROM made for a different model phone (i.e. Vibrant):
----> Follow Directions for Flashing WITH BOOTLOADERS
However, I didnt flash the whole ROM. Just the kernel. So, I have aapparantly a Gingerbread based Kernel with a Froyo Rom. In this case, do I want to go to a FROYO kernel, or go to a Gingerbread (or a JB??) ROM?
I have the ultimate goal of going to a JB ROM. I'm starting to think I cant just flash the JB ROM over the Froyo, or can I? I'll have to peruse the forums a bit to learn more about that.
Finally - I cant seem to access download mode via any of the methods presented. I ordered a jig, so when that arrives, I'll follow the guide and either downgrade the kernel or upgrade the ROM.
This devide seems a bit more complicated to work with than the Nexus S that I was previously toying with.
Thanks for your input and assistance.
Click to expand...
Click to collapse
You will need to follow the complete guide including flashing bootloaders if you want to upgrade to GB or ICS. No you cannot flash GB or ICS from Froyo recovery because of the bootloaders. As mentioned above, we do not have JB. If you want to flash back to froyo there is a KD1 One-Click FB put together. Let me know if you want to stay on Froyo for some reason and I will find the link for you.

Rainbow screen - froyo, eyc
lumin30 said:
You will need to follow the complete guide including flashing bootloaders if you want to upgrade to GB or ICS. No you cannot flash GB or ICS from Froyo recovery because of the bootloaders. As mentioned above, we do not have JB. If you want to flash back to froyo there is a KD1 One-Click FB put together. Let me know if you want to stay on Froyo for some reason and I will find the link for you.
Click to expand...
Click to collapse
Many thanks. I dont want to stay on Froyo. I'm helping a friend with this device, and she had never updated from Froyo. I'll take a look at moving into Slim ICS, since theres no JB for this device, unless anybody has any better suggestions.
This whole problem started for me after I realized that to get ROM Manager working on this phone, I had to go to a different Kernel. I didnt realize that the kernel I picked had the wrong boot loaders, and Voila. A rather unattractive rainbow screen. As soon as I can get into download mode, I'll jump on this.
I thank everyone again for their input.

socalg said:
Many thanks. I dont want to stay on Froyo. I'm helping a friend with this device, and she had never updated from Froyo. I'll take a look at moving into Slim ICS, since theres no JB for this device, unless anybody has any better suggestions.
This whole problem started for me after I realized that to get ROM Manager working on this phone, I had to go to a different Kernel. I didnt realize that the kernel I picked had the wrong boot loaders, and Voila. A rather unattractive rainbow screen. As soon as I can get into download mode, I'll jump on this.
I thank everyone again for their input.
Click to expand...
Click to collapse
ROM Manager does not work for this device and can cause issues.