One Woot! user got theirs today, and it's 3389. I am going to assume that they are probably all 3389, then - most likely all imaged the same.
What a relief! I will update my mod posts, accordingly. Btw, 3389 isn't even the latest "official" firmware, you are one revision behind. 3389 came out in December, I believe.
Did they get an OTA, or was that out of the box, and no OTA after that?
Jim
The firmware upgrades are not OTA correct?
Sent from my PC36100 using XDA App
3389 OOTB. This one user just ran the updater and it wants to update them to 3588 (which is expected).
3389 was a late December update, btw - that was the one they released just before Christmas.
itsernst said:
The firmware upgrades are not OTA correct?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
The stock updates are all OTA - they don't supply offline updates.
roebeet said:
3389 OOTB. This one user just ran the updater and it wants to update them to 3588 (which is expected).
3389 was a late December update, btw - that was the one they released just before Christmas.
The stock updates are all OTA - they don't supply offline updates.
Click to expand...
Click to collapse
Yep this is the exact version my tablet came in ootb almost 2 weeks ago!!! Ota up to 3588
So what is the call to action, do the OTA update? Then proceed with rooting?
vegeetz said:
So what is the call to action, do the OTA update? Then proceed with rooting?
Click to expand...
Click to collapse
Advice here.
vegeetz said:
So what is the call to action, do the OTA update? Then proceed with rooting?
Click to expand...
Click to collapse
If it were me, I would do the following:
- Charge if fully first. It will take at least an hour to do that, but it's recommended. This thing gets very wonky when the battery is low.
- Do a data wipe. User data corruption is basically the first thing any modder will ask you to correct, if you have problems. And the early builds definitely required them. The problem here is that, if you have Flash and the Kindle apps installed, they will be deleted, so keep that in mind.
I'm assuming that you won't care, given that you are here and you want the Market, anyway.
- Update it to 3588, via OTA. I would recommend it, as it gives you the most stable baseline. 3588 has been out since January and it's a solid stock ROM. It also preps you for their "1.2" path, if Viewsonic releases it.
- Pick a modded ROM. The fun begins.
Optional but recommended: Install and learn adb and nvflash. There are a few guides floating around here on those. adb is essentially a remote shell (like a "telnet") and you can do some interesting things with it. It's not enabled on the device by default, but most modded ROMS will enable it on the device, for you. nvflash is a low level format mode and it's basically your backout plan in case you mod the device and mess it up, badly (a "soft brick").
Roebeet,
As you can see from my sig, I'm still on stock 3452. Never got an OTA notification.
If 3588 is a transitional version, that means if I'm stuck on 3452, then I won't be able to upgrade past 3588, ever?
So, seeing that I'm not getting any OTA notifications, do you think that I should download and flash to 3588 manually now?
If so, I have CWM .8 installed as recovery right now, so I should be able to use that CWM to flash the 3588 update.zip, right?
Final question: If I do that, will that wipe out all my apps, etc.?
Thanks,
Jim
P.s. Does the 3588 flash wipe out CWM?
3452 was one one of those leaked UAT's that was never released (If I recall correctly - remember, some of these leaked to users via OTA - we could never figure out their release process, exactly).
If you never got an OTA update to 3588, I would recommend forcing yourself to 3588 to get a solid baseline. Basically, you'd take the 3588 in the stock ROM post (http://forum.xda-developers.com/showthread.php?t=842000), rename it to "update.zip" and create a recovery\command file as mentioned there (or take one from the 1.0.0 homebrew zip).
roebeet said:
3452 was one one of those leaked UAT's that was never released (If I recall correctly - remember, some of these leaked to users via OTA - we could never figure out their release process, exactly).
If you never got an OTA update to 3588, I would recommend forcing yourself to 3588 to get a solid baseline. Basically, you'd take the 3588 in the stock ROM post (http://forum.xda-developers.com/showthread.php?t=842000), rename it to "update.zip" and create a recovery\command file as mentioned there (or take one from the 1.0.0 homebrew zip).
Click to expand...
Click to collapse
I don't think the update.zip/recovery folder method would work for me, since as mentioned I have CWM .8 installed?
Also per earlier questions, does 3588 wipe out CWM?
Jim
jimcpl said:
I don't think the update.zip/recovery folder method would work for me, since as mentioned I have CWM .8 installed?
Also per earlier questions, does 3588 wipe out CWM?
Jim
Click to expand...
Click to collapse
Yes, it should wipe out cwm. You can use clockworkmod between 3452 and 3588, as they are both "1.1" firmwares. Just be careful with anything newer than 3588 as we just don't know what it will look like yet.
roebeet said:
Yes, it should wipe out cwm. You can use clockworkmod between 3452 and 3588, as they are both "1.1" firmwares. Just be careful with anything newer than 3588 as we just don't know what it will look like yet.
Click to expand...
Click to collapse
Thanks. That's what I thought. I have the 3588 update.zip from back in January, so I'll give that a shot, using CWM.
Jim
Related
all ROM info can be found HERE
Reserved
Just holding a parking spot...
Reserved II
I am the jerk who takes two spots with his/her car...
What keyboard does this have? And does the D2 multitouch keyboard still work?
ok, let me get this straight. will i be able to SBF with the 2.2 SBF file that was leaked about 2 weeks ago?
Can I flash this over Fission 1.2.1?
Sent from my DROID2 using XDA App
firestrife23 said:
Can I flash this over Fission 1.2.1?
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Yes, though it's still recommended that you wipe system
With rom manager or sbf? Thanks
Sent from my DROID2 using XDA App
dec11ad said:
ok, let me get this straight. will i be able to SBF with the 2.2 SBF file that was leaked about 2 weeks ago?
Click to expand...
Click to collapse
That all depends. Have you gotten the OTA yet? If you are still on baseband 01.09.05P and Version 2.2.20 from verizon then yes, you can SBF. If you have gotten the OTA and are on baseband 01.09.07P and 2.30.20 from verizon, then no, you have to wait for the new SBF. The OTA changed both the mbmloader and the bootloader and you will end up with a brick of you sbf with the 2.2.20 file after the OTA
ok, i have the BP_C_01.09.07P baseband, can i still SBF? or does it only break the ability to SBF after installing Fission 2.0?
i currently have fission 1.2.1 ROM.
dec11ad said:
ok, i have the BP_C_01.09.07P baseband, can i still SBF? or does it only break the ability to SBF after installing Fission 2.0?
i currently have fission 1.2.1 ROM.
Click to expand...
Click to collapse
you cannot SBF on that baseband
Sorry for asking:
- I'd never done an OTA upgrade, my baseband BP_C_01.09.05P
- I'd rooted my D2 with easier1-2-3 by darkonion
- Now i'm on fission 1.2.1
So, what should i do to install Fission 2.0?
Thanks in advance
a_sty2007 said:
Sorry for asking:
- I'd never done an OTA upgrade, my baseband BP_C_01.09.05P
- I'd rooted my D2 with easier1-2-3 by darkonion
- Now i'm on fission 1.2.1
So, what should i do to install Fission 2.0?
Thanks in advance
Click to expand...
Click to collapse
I was in your situation, what i've done so far is SFB'ed my DROID2 to stock and i'm currently waiting for the OTA to popup on my device and then after that installs im going to reroot with the same method you used and install fission 2.0 like i did before.
droid2andyou said:
I was in your situation, what i've done so far is SFB'ed my DROID2 to stock and i'm currently waiting for the OTA to popup on my device and then after that installs im going to reroot with the same method you used and install fission 2.0 like i did before.
Click to expand...
Click to collapse
SBF your phone before installing this.
droid2andyou said:
I was in your situation, what i've done so far is SFB'ed my DROID2 to stock and i'm currently waiting for the OTA to popup on my device and then after that installs im going to reroot with the same method you used and install fission 2.0 like i did before.
Click to expand...
Click to collapse
The instruction said that:
"If you have the latest OTA update then I suggest you do not install this ROM in the case something goes wrong you will be stuck with a brick."
So why are you waiting for the OTA and install it?
a_sty2007 said:
The instruction said that:
"If you have the latest OTA update then I suggest you do not install this ROM in the case something goes wrong you will be stuck with a brick."
So why are you waiting for the OTA and install it?
Click to expand...
Click to collapse
because nothing went wrong when i installed Fission 1.2, i want the new baseband and kernel.
droid2andyou said:
because nothing went wrong when i installed Fission 1.2, i want the new baseband and kernel.
Click to expand...
Click to collapse
So, can i SBF'ed my D2, and flashing Fission 2.0 without waiting for OTA update? (Cause maybe need a time to wait for OTA popup)
So can anybody clarify the "do i need to sbf" question?
Yes, I def read the instructions which say you should, but I have still never had to sbf my d2, and I'm just wondering what am I risking, or possible to have problems with if I don't SBF?
Just seems reeeeallly above and beyond as wiping data sucks enough already.
Anyway, thanks for the continued releases, I can't remember the last time I had the same build of a rom on my phone for more than 48 hours lol.
a_sty2007 said:
So, can i SBF'ed my D2, and flashing Fission 2.0 without waiting for OTA update? (Cause maybe need a time to wait for OTA popup)
Click to expand...
Click to collapse
angdroid said 2.0 would work with or without the new update (kernel / baseband), however if you do get the OTA update you cannot SBF if you get stuck until it is released over @ mydroidworld. As long as you have the older baseband and kernal you can SBF your D2
one. said:
So can anybody clarify the "do i need to sbf" question?
Yes, I def read the instructions which say you should, but I have still never had to sbf my d2, and I'm just wondering what am I risking, or possible to have problems with if I don't SBF?
Just seems reeeeallly above and beyond as wiping data sucks enough already.
Anyway, thanks for the continued releases, I can't remember the last time I had the same build of a rom on my phone for more than 48 hours lol.
Click to expand...
Click to collapse
As with anything, it is not required. We will not offer support for the ROM however, unless the steps listed in the first post were taken. There are many user caused issues simply because the phone has been modified and we do not know to what point it has. The steps listed for the install restore the phone to factory settings, thus giving us a starting point. This also will allow us to isolate bugs and help to eliminate user error.
I've a rooted G2X that's still running 2.2. Just over an hour ago I got a "T-Mobile Update Service." notification. Surprisingly there's no talk of a fresh OTA here so I'm not really sure what's going on. Not that an OTA would work for me since I'm rooted, but I guess it's going to keep bugging me until I do something about it.
2.3.3 was all the rage about a month or so ago.
Sent from my LG-P999 using xda premium
Well, sure, but all news says that T-mobile stopped doing OTAs some time ago (started late July, stopped August 10). So why on earth is my phone just getting it now? I even do a manual check every so often and never got it. I didn't do anything special today that I can recall.
you should update it. you dont have nothing to lose. ifd your still rooted it will unroot but then you can flash nvflash recovery and go back to any rooted roms you want
epithumia said:
I've a rooted G2X that's still running 2.2. Just over an hour ago I got a "T-Mobile Update Service." notification. Surprisingly there's no talk of a fresh OTA here so I'm not really sure what's going on. Not that an OTA would work for me since I'm rooted, but I guess it's going to keep bugging me until I do something about it.
Click to expand...
Click to collapse
No idea why you're just getting it now, but its the same one thats been out for a while now.
hmichaelkim said:
No idea why you're just getting it now, but its the same one thats been out for a while now.
Click to expand...
Click to collapse
T-Mobile removed the 2.3.3 update from their servers long ago. If you are getting something else it is new most likely. You can do an OTA if you are rooted as long as you have not modified any system files other than adding su and superuser.apk to get root..
epithumia said:
I've a rooted G2X that's still running 2.2. Just over an hour ago I got a "T-Mobile Update Service." notification. Surprisingly there's no talk of a fresh OTA here so I'm not really sure what's going on. Not that an OTA would work for me since I'm rooted, but I guess it's going to keep bugging me until I do something about it.
Click to expand...
Click to collapse
So what was the update?
Sent from my HTC Desire using XDA App
What happens?
Sent from my LG-P999 using XDA Premium App
Well, I let it update but of course it just booted into CWM instead of doing anything. I'm guessing I'd have to flash back to stock in order to apply any OTA. If someone tells me what to search for I can run logcat and see what it downloaded, but I didn't see anything obvious when I looked (and there's a lot of stuff in there).
I'm on froyo to and rooted but no clockwork mod recovery. I tried to check for an update and it said some kind of error i dont remember.
epithumia said:
Well, I let it update but of course it just booted into CWM instead of doing anything. I'm guessing I'd have to flash back to stock in order to apply any OTA. If someone tells me what to search for I can run logcat and see what it downloaded, but I didn't see anything obvious when I looked (and there's a lot of stuff in there).
Click to expand...
Click to collapse
Check in the /cache directory for the zip file for tthe update. If you can, before you install it can you save a copy of the zip to a separate area on your sdcard and thn upload it to a file sharing site so others can download it? Once you install it, it gets deleted from the /cache directory but if you save it elsewhere those copies will be saved.
epithumia said:
Well, I let it update but of course it just booted into CWM instead of doing anything. I'm guessing I'd have to flash back to stock in order to apply any OTA. If someone tells me what to search for I can run logcat and see what it downloaded, but I didn't see anything obvious when I looked (and there's a lot of stuff in there).
Click to expand...
Click to collapse
Yes, you need to be on stock recovery and your phone's system partition must be stock. LG stores some OTAs very differently than other vendors.
Do a backup of your phone first to preserve the OTA image. It might be in the cache but it might be elsewhere. If you wouldn't mind giving me a link to the system and cache images I can try to find the OTA and see what it is for.
I just got the 2.3.3 ota update about 2 weeks ago which i thought was real late also. I used to check for the update and i would always get an error too. i was rooted in stock froyo for tmobiles g2x (LG P999DW). I didnt have to re-root the phone and last night i just flashed clockworkmod recovery and flashed the 1.55ghz overclocking kernel on to the 2.3.3 that i got from the ota update.
Lenin809 said:
I just got the 2.3.3 ota update about 2 weeks ago which i thought was real late also. I used to check for the update and i would always get an error too. i was rooted in stock froyo for tmobiles g2x (LG P999DW). I didnt have to re-root the phone and last night i just flashed clockworkmod recovery and flashed the 1.55ghz overclocking kernel on to the 2.3.3 that i got from the ota update.
Click to expand...
Click to collapse
Did you flash roms and then restore an old backup? That backup could have had the OTA on it and you did not notice it before. T-Mobile pulled the OTA months ago (was available less than two weeks). Doesn't seem likely it was pushed to you recently.
Hi I had a question. If I got root and installed revolver would it still be possible to upgrade to ICS when it comes out? I have heard alot of issues of people not being able to do OTAS after this. Also is it possible to remove revolver and got back to stock?
Thanks
After rooting you cannot install any OTA's, but if you run revolver you will most likely see an update to ICS considering the owner keeps it updated. He releases new firmware updates to his ROM the same day they are released from Asus.
If you root though know what you are doing, and yes you would be able to flash back to stock.
ThEiiNoCeNT said:
After rooting you cannot install any OTA's, but if you run revolver you will most likely see an update to ICS considering the owner keeps it updated. He releases new firmware updates to his ROM the same day they are released from Asus.
If you root though know what you are doing, and yes you would be able to flash back to stock.
Click to expand...
Click to collapse
I see. I've done a bit of rooting with the archos 101 and i'm pretty good with computers. You said you can't do OTAs but asus puts the files on their website don't they? Couldn't you just dl it there and update?
you can download it but you get an error when trying to install I believe. I've just updated through the roms that were released. These guys are right on it, and they're good!
Yes, you could.....but it won't work, and will automatically fail mid-way through. If the update detects any software tampering and doesn't appear to be a stock unrooted build it will fail. Like I said though, ROM developers are good at updates, they put them out daily and we are sure to see a ROM of ICS before it is even out officially for our tabs.
Sent from my Transformer TF101 using xda premium
Without nvflash how can we revert to stock? I'm on a tf101g b80. Sry if i post it there.
Hi there,
I read almost every thread about no updates available and still don't found answer...
My tab was rooted and CWM installed.
because this is B60, I used NVflash to flash totally stock 8.6.5.13 from here:
http://www.tabletroms.com/forums/tr...stock-3-2-recovery-roms-unbricking-tools.html
after that, I tried to use "system firmware update" but "There is no update available" message appears,
so I decided to update it manually, put 8.6.5.21 zip on sdcard and now have 8.6.5.21 android,
but still "There is no update available"...
I also tried to root this 8.6.5.21 put CWM again, used SuperWipe Full script, and again installed 8.6.5.13 with NVFlash, still same situation.
I also tried tricks with clear cache/data of CMClient and DMClient,
I can push ICS via NVflash but last version i found is .24, i tried this also, but can't get update to .27 and noticed battery draining during night,
my plan is come back to totally stock where OTA will work and give this tab to my wife.
Anybody can help me ?
_Pablo_ said:
Hi there,
I read almost every thread about no updates available and still don't found answer...
My tab was rooted and CWM installed.
because this is B60, I used NVflash to flash totally stock 8.6.5.13 from here:
http://www.tabletroms.com/forums/tr...stock-3-2-recovery-roms-unbricking-tools.html
after that, I tried to use "system firmware update" but "There is no update available" message appears,
so I decided to update it manually, put 8.6.5.21 zip on sdcard and now have 8.6.5.21 android,
but still "There is no update available"...
I also tried to root this 8.6.5.21 put CWM again, used SuperWipe Full script, and again installed 8.6.5.13 with NVFlash, still same situation.
I also tried tricks with clear cache/data of CMClient and DMClient,
I can push ICS via NVflash but last version i found is .24, i tried this also, but can't get update to .27 and noticed battery draining during night,
my plan is come back to totally stock where OTA will work and give this tab to my wife.
Anybody can help me ?
Click to expand...
Click to collapse
Use BRK's tool and download the latest firmware from Asus. This tool works great and will even get you rooted after nvflashing 9.2.1.27 for you.
sidneyk said:
Use BRK's tool and download the latest firmware from Asus. This tool works great and will even get you rooted after nvflashing 9.2.1.27 for you.
Click to expand...
Click to collapse
BRK tools is great "Everything in one place" tool.
I can use it to install ICS .27 from Asus web site, and this is great,
but I don't know if in the future OTA will come...
I tried to install 8.6.5.21 using this tool, and after that still had message "There is no update avaiable"
as I wrote, want to be 100% sure, future OTA will come.
_Pablo_ said:
BRK tools is great "Everything in one place" tool.
I can use it to install ICS .27 from Asus web site, and this is great,
but I don't know if in the future OTA will come...
I tried to install 8.6.5.21 using this tool, and after that still had message "There is no update avaiable"
as I wrote, want to be 100% sure, future OTA will come.
Click to expand...
Click to collapse
My understanding is that FOTAs will be allowed if you nvflash a stock firmware with this tool, so long as it's not rooted and you keep the stock recovery. All has to be stock and the proper SKU, i.e. US, WW, CN, etc. and it should work the same as if it came from the factory that way.
I have a rooted, deodexed stock(ish) rom and I still get updates, but of course they won't flash. I don't think ASUS is constantly pushing old updates since the only ones who haven't upgraded yet are either rooted or haven't used their tablet. The updates are incremental, so you need the current stock rom to update with the lastest OTA. The full roms can be downloaded from the ASUS site.
If you want to get updates straight from ASUS, then flash the latest rom and keep it stock. Otherwise, you'll just get useless updates that won't flash. You need a stock system and a stock recovery to flash the ASUS OTAs. No voodoo, no overclocking kernel, no CIFS/SAMBA, no XBMC, no nothing, no fun.
gee one said:
I have a rooted, deodexed stock(ish) rom and I still get updates, but of course they won't flash.
Click to expand...
Click to collapse
Exactly! Rooted rom or changed recovery don't stop to receive FOTA notifications, but will give an error if you try to install.
gee one said:
I don't think ASUS is constantly pushing old updates since the only ones who haven't upgraded yet are either rooted or haven't used their tablet. The updates are incremental, so you need the current stock rom to update with the lastest OTA. The full roms can be downloaded from the ASUS site.
Click to expand...
Click to collapse
Something is strange here, and probably only Asus knows how it works.
I had rooted room, and my tab downloaded first update to ICS version, but of course I didn't install it. Now I tried to come bace to fully stock, tried 8.6.5.13, 8.6.5.21, and 9.2.1.24 and never received FOTA notification anymore.
Maybe my serial number is banned on Asus side ??? Who knows...
I spend a lot of time reading and some people had this problem, some not, nobody don't know the reason.
gee one said:
If you want to get updates straight from ASUS, then flash the latest rom and keep it stock. Otherwise, you'll just get useless updates that won't flash. You need a stock system and a stock recovery to flash the ASUS OTAs. No voodoo, no overclocking kernel, no CIFS/SAMBA, no XBMC, no nothing, no fun.
Click to expand...
Click to collapse
I tried to come back to fully stock in order to give this tab to my wife, but if tab don't receive FOTA anymore, and I'll have to update it by hand every time using SD card it makes no sense to install stock firmware. Now I'm looking for most stable ROM and will install it. For now the winner is newest ARHD, but I still reading about diffrent roms.
To be clear, I think that ASUS only pushes out updates for the latest ROM. If you are on .24 or older, you probably won't get an update since .27 is the latest. This is just my theory. The updates are incremental, which means that you have to apply the .27 update on top of the .24 rom. It will fail if you try to flash it over an older rom, even if it is bone stock.
In your situation, I would recommend a custom ROM.
Gee one is right... once you root stock update won't install and yes its a incremental update and you can't install .27 over .21 it has to be in order (.21->.24->.27)... also you need a unrooted ROM to download and apply updates from Asus otherwise update will fail and u risk soft bricking ur tablet... I did that once coz I was having problems with 1st ICS versions....
If don't like/can't get to work then root it and install either android revolution HD or revolver ICS.. both are stock based ICS ROMs...
Sent from my Transformer TF101 using xda app-developers app
Hmm...
Updates are incremental, this is true.
but... When i bought my tf, and come back to home, FOTAs coming few times and after one hour about I had nevest version.
Now, after NVFLASHing .24 I don't receive FOTA update since two days...
Somewhere I red, NVFLASH don't clean everything, maybe this is reason.
I would like to try, but i have no idea how to TOTALLY clean my tab,
I looked into SuperWupeFull script and it clean mmcblk0p1, p2 and p7.
Any idea about TOTAL clean ?
really dangerous way should be to execute dd if=/dev/zero of=/dev/block/mmcblk0
but i don't know if it is good idea ))
this could break apx mode.
_Pablo_ said:
really dangerous way should be to execute dd if=/dev/zero of=/dev/block/mmcblk0
but i don't know if it is good idea ))
this could break apx mode.
Click to expand...
Click to collapse
Why don't u try downloading older version of Asus and do incremental update.. say first version of ICS for transformer...
Sent from my Transformer TF101 using xda app-developers app
I tried versions, ICS .21, .24 and HC .13, .21.
Every time, same message:
"No updates available for your device"
Asus might not be pushing any updates. I bet they stop as soon as they post the latest rom on their website.
If you use nvflash to reflash your TF, it will format every partition, but you have to use the --create flag. If you just download the system or recovery, it won't touch the other partitions.
I am doing an incremental update of my tablet and I need to know what the chronological order of the updates where. My tablst came with 9.4.5.26 and I see references to .16, ,18, .30 etc. Which ones do I need before I can do the 10.4.4.20 update. I'm not sure but I believe I should do the .30 next. If so can I use the WW.30 update because the thread I am using to do this only offers it and not a US.30. Still new and do not know the difference, if there is one.
lartomar2002 said:
I am doing an incremental update of my tablet and I need to know what the chronological order of the updates where. My tablst came with 9.4.5.26 and I see references to .16, ,18, .30 etc. Which ones do I need before I can do the 10.4.4.20 update. I'm not sure but I believe I should do the .30 next. If so can I use the WW.30 update because the thread I am using to do this only offers it and not a US.30. Still new and do not know the difference, if there is one.
Click to expand...
Click to collapse
The order is .30, .16, .18, then .20. Incremental is nessessary to retain root. If you unlocked, you could flash the full version .20 and done.
buhohitr said:
The order is .30, .16, .18, then .20. Incremental is nessessary to retain root. If you unlocked, you could flash the full version .20 and done.
Click to expand...
Click to collapse
Thank you, how about using the ww.30 update is that okay? There is not a link to a US .30 update. Do not want to unlock at this time I unlocked my first TF700 and rooted it but when I tried to setup NVflash I ended up bricking it. Thankfully I was still with in the 30 day Amazon return period so they sent me a new one. I am now out of the return period with this one and if I brick it now all I will have is a $479.00 door stop. Not only that but I will have to put up with my wife's outrage.
lartomar2002 said:
Thank you, how about using the ww.30 update is that okay? There is not a link to a US .30 update.
Click to expand...
Click to collapse
OTA updates must be done on the same SKU - if you start with an US firmware, you must continue with US dlkpkgs.
lartomar2002 said:
Thank you, how about using the ww.30 update is that okay? There is not a link to a US .30 update. Do not want to unlock at this time I unlocked my first TF700 and rooted it but when I tried to setup NVflash I ended up bricking it. Thankfully I was still with in the 30 day Amazon return period so they sent me a new one. I am now out of the return period with this one and if I brick it now all I will have is a $479.00 door stop. Not only that but I will have to put up with my wife's outrage.
Click to expand...
Click to collapse
Haha, but if you unlock, you wife will be a lot happier!! Actually, unlock is very safe and even less risk than rooting. Either it works or just fails. With the poor performance of the tf700, it's a huge different if you unlock and install Cleanrom. Anyway, you don't do .30 incremental update and no, you can't use WW instead of US. Since there is no US file, you should do a Full version update then do root and then do incremental from there on. Here is link for full .30.
http://forum.xda-developers.com/showthread.php?t=1734005
buhohitr said:
Haha, but if you unlock, you wife will be a lot happier!! Actually, unlock is very safe and even less risk than rooting. Either it works or just fails. With the poor performance of the tf700, it's a huge different if you unlock and install Cleanrom. Anyway, you don't do .30 incremental update and no, you can't use WW instead of US. Since there is no US file, you should do a Full version update then do root and then do incremental from there on. Here is link for full .30.
http://forum.xda-developers.com/showthread.php?t=1734005
Click to expand...
Click to collapse
I am rooted using Debug's (?) tool. can I just go ahead and unlock while rooted, will I need to use the OTA Root Keeper?
I forgot to add the cost of the dock into that price so it would be a $600 door stop. Even more rage, OUCH!
Also, in the thread I am using for the incremental updates say's I have to use a "dlpkg" file is that different from the regular firmware?
lartomar2002 said:
I am doing an incremental update of my tablet and I need to know what the chronological order of the updates where. My tablst came with 9.4.5.26 and I see references to .16, ,18, .30 etc. Which ones do I need before I can do the 10.4.4.20 update. I'm not sure but I believe I should do the .30 next. If so can I use the WW.30 update because the thread I am using to do this only offers it and not a US.30. Still new and do not know the difference, if there is one.
Click to expand...
Click to collapse
My tablet came with US 4.xx.xx.20 JB and flashed US 9.xx.xx.30 ICS by renaming zip file and copy to root of sd. Did this so I can root ICS. After I downgraded I was prompted with OTA to JB 4.xx.xx.20. I rooted first of course and installed OTA rootkeeper and after the OTA finished I restored root via OTA rootkeeper and didnt have any issue with jumping straight to JB .20. Although I hated JB on the tf700 as it caused so much lag so I flashed back to ICS .30 which is the only version that will work via micro sd card method.
I'm wondering why the need for incremental upgrade?
lartomar2002 said:
I am rooted using Debug's (?) tool. can I just go ahead and unlock while rooted, will I need to use the OTA Root Keeper?
I forgot to add the cost of the dock into that price so it would be a $600 door stop. Even more rage, OUCH!
Also, in the thread I am using for the incremental updates say's I have to use a "dlpkg" file is that different from the regular firmware?
Click to expand...
Click to collapse
Yes, it's the best way while you already rooted, then unlock. Once you unlocked, it's very simple to do the rest. Just install custom recovery (TWRP) using Goomanager app from the market, then use this to flash prerooted rom like Cleanrom/kernel etc...
The most common mistake ppl bricked their devices was flashing the wrong recovery or using wrong tool to flash recovery. Other wise is pretty much brick proof.
dlpkg file is incremental update, it will not wipe your stuff (same as OTA update) and you could preserve root with Rootkeeper. Firmware download from Asus site is a full rom upgrade, which will wipe everything before upgrade, included root, apps etc...
Rooting is not really help with tf700 performance issue. I recommend you should unlock then life is beautiful after that.....
---------- Post added at 10:18 PM ---------- Previous post was at 10:12 PM ----------
aznmode said:
My tablet came with US 4.xx.xx.20 JB and flashed US 9.xx.xx.30 ICS by renaming zip file and copy to root of sd. Did this so I can root ICS. After I downgraded I was prompted with OTA to JB 4.xx.xx.20. I rooted first of course and installed OTA rootkeeper and after the OTA finished I restored root via OTA rootkeeper and didnt have any issue with jumping straight to JB .20. Although I hated JB on the tf700 as it caused so much lag so I flashed back to ICS .30 which is the only version that will work via micro sd card method.
I'm wondering why the need for incremental upgrade?
Click to expand...
Click to collapse
In your case, you already have everything installed (JB 20), like JB boot loader, drivers, firmware etc.. So when you downgrade, most of the stuff remain in your tablet (JB bootloader remain intact etc..). People that never upgrade before and they only at .30, the right way is to upgrade one version at a time, this ensure you don't miss anything.
Good to know. Thanks
Sent from my SGH-T999 using Tapatalk 2