I want to downgrade a tf101 from ICS to HC because it have extremely many random reboots. Is it possible to flash a stock ROM of HC?
And is there any?
Sent from my LG-P990 using XDA
They are out there. For compatibility, I would suggest also flashing the kernel/boot.img and maybe even the bootloader. You might get bootloops otherwise, but it's just a theory.
I thought ASUS has the stock roms on their site, but you have to mod them for use on CWM or mod CWM to flash them. They are bone stock so unless you mod them, you will lose root and recovery.
edit: the stock roms generally won't flash through cwm because the mounts aren't all there. Rogue might work, but it's just a guess. You also might be able to mount the staging partition through adb and flash the stock roms.
This ROM is HC 3.2.1 and have a kernel (this is just an example), can I just flash this?
http://forum.xda-developers.com/showthread.php?t=1251044
And the bootloader for HC, is it download-able? Flashable?
Asus might have the full roms on their ftp site. There are HC roms on their download site for the tf101, but not all countries. The OTAs will have the bootloaders in them usually.
I'm weary about flashing different kernels and bootloaders. I suspect that they cause bootloops, but it's just a theory. It might be wrong.
gee one said:
Asus might have the full roms on their ftp site. There are HC roms on their download site for the tf101, but not all countries. The OTAs will have the bootloaders in them usually.
I'm weary about flashing different kernels and bootloaders. I suspect that they cause bootloops, but it's just a theory. It might be wrong.
Click to expand...
Click to collapse
Its a US version.. I'll check..
Edit: On the download section (asus.com) there isn't a HC download for US version....
Related
I just rooted (New Method) my TF version 8.2.3.9 and was wondering if there is a way to get 8.2.3.13 update installed manually without flashing a custom rom? Also is there a way to fix the rear camera without loading a custom rom as well?
Any help is greatly appreciated. TIA
Why, do you just like a challenge? in order to root.. you need to modify the system partition, adding su.. so you're running a custom rom anyways..
Prime 1.3 is just like stock... except it has a tweaks that are beneficial.. There really isn't anything truly custom that people can do with honeycomb until the source is released. which may or may not remain Google's dirty little secret.
You can use 'dd' to rewrite boot and system partitions. You just need to find a .13 blob, split it using blob tools and rewrite the partitions from recovery/adb. In worst case you will rewrite bootloader or recovery and brick your device. The hard part is to find the blob as I think the update was incremental.
Sent from my Transformer TF101 using Tapatalk
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_US_epad_user_82313.zip
Here is the blob (copy-pasted from another thread).
Sent from my Transformer TF101 using Tapatalk
thaddyusmaximus said:
I just rooted (New Method) my TF version 8.2.3.9 and was wondering if there is a way to get 8.2.3.13 update installed manually without flashing a custom rom?
Click to expand...
Click to collapse
I did the same, as I want to stay on stock too. To keep root extract the blob mentioned above with the blobunpack tool mentioned somewhere here. Then dd blob.APP to /dev/block/mmcblk0p1 and after that install the ZIP mentioned on
http://android.modaco.com/content/a...pr-how-to-root-your-asus-eee-pad-transformer/
to get the root binary/app back.
This way you have a clean rooted ASUS stock .13 . I couldn't resist to install an overclocked kernel though afterwards
Blades said:
Why, do you just like a challenge? in order to root.. you need to modify the system partition, adding su.. so you're running a custom rom anyways..
Prime 1.3 is just like stock... except it has a tweaks that are beneficial.. There really isn't anything truly custom that people can do with honeycomb until the source is released. which may or may not remain Google's dirty little secret.
Click to expand...
Click to collapse
Not the challenge really but laziness to reinstall all my games and apps. I installed about 50 games/apps with about 4 games that is larger than 200mbs.
[Q]. What happens to the paid apps when I flash a custom rom? Can I redownload them later for free from Android Market? Is there a limit on how many times I can download them?
I've installed prime rom on my tablet,but now I need to go back to the original hc 3.2.1
what can I do?
Try this. It worked for me.
http://forum.xda-developers.com/showthread.php?t=1154947
but now i've hc 3.2.1 not 3.1 >_< and i've an EUR version,not US
I think you have a few options:
- find a flashable zip that installs the stock firmware
- make a flashable zip yourself to install the stock firmware
- use nvflash if you have a low enough serial number
- flash the stock firmware using the staging partition
- there might be a way to use asus-backup, but I haven't tinkered with that.
The first two options usually require the command line and blob tools, although some of the rom cooking tools might work. You could probably mod one of the asus stock roms to flash via recovery.
The nvflash option requires the blob tools and nvflash.
The staging partition option can be done via terminal, but can also screw things up quickly. You'll also lose recovery unless you use the blob tools.
You'll have to mod the stock firmware to be pre-rooted if you want to keep root, which will require slightly more advanced android-fu.
All of these options would start with the EU/WW asus stock firmware. You'll just be modding it to install to your liking. My choice would be a DIY flashable zip or the staging partition, but that is just me.
Do you want to keep root or recovery or just go bone stock? Does nvflash work?
so many questions lol. But that just means alot go look up first. This sounds cool. Thank you.
Why go with nv flash? I only ask because ive always used cwm. But iguess i was rooted too.
Lets say i wanted to go stock on the rom but rooted? With CWM, superuser, maybe an oc kernel.
Or just stick with Prime!
Thanks.
I'm not sure there are any clear advantages to nvflash- it's easier to load the stock firmware with nvflash, but you can also load custom roms/recoveries too, but they have to be converted for nvflash. nvflash isn't available to all TFs because of the SBK issue. We only know the SBK for the low serial numbers, which allows us to use nvflash.
Any of the first four methods can be used to flash a rooted stock rom with oc kernel and cwm. I don't know anything about asus-backup.
This is a full rom for stock(ish) 9.2.1.17 and includes the following:
9.2.1.17 US bootloader and kernel/boot.img
modded recovery based on Roach's 3.2.0.1
Superuser
su binary
busybox
adb enabled, ro.secure=0 (if you previously disabled adb, it will remain disabled, unless you wipe data)
The updater script will also clear cache and dalvik cache.
Plus, if you flash now, it will also fix the cwm recovery bootloops by writing zeros to the first 80 bytes of /misc (/dev/block/mmcblk0p3)
I was lazy and the progress bar in recovery does not udpate- it is a full rom so it does take a while to flash.
This is pretty close to a rooted stock experience. It isn't for everyone, but I think some will find it useful. I thought this would help out people who get in in a pickle by flashing various roms and ending up with unbootable systems, or people who tried a few other roms and want to return to a more stock experience. I think a custom recovery is safer with a rooted rom so that flashing via recovery is still available. This should still receive OTA updates, but they will probably fail to flash because the build.prop file is different (ro.secure=0 and adb). This rom will flash in situations where doaist's CWM friendly updates will not. As a matter of fact, this rom will probably flash on any version of cwm/custom recovery that can read it.
The recovery is modded- it is based on Roach's 3.2.0.1 and only sees the external sd card. I used Roach's ramdisk, but used the the inits, fstab, and ueventd files from the stock recovery. This recovery will seem identical, but you can look at the default.prop to see the difference. In future versions, I might change the version number in case there is any confusion.
NOTE and WARNINGS:
This is for the TF101 US only. The fingerprint checks are removed from the updater-script so it is up to you to know what you are flashing. (Don't flash this on your phone! and if you do, don't say a word and act like your phone is still working.)
This will overwrite your recovery. You can flash it back to something else after a reboot.
This will overwrite your bootloader/EBT. This might have unintended consequences so flash at your own risk. The stock OTA updates the bootloader, so this is why I included it here.
Flash at your own risk. I am not responsible for any damages or consequences.
ALL WARRANTIES REGARDING MERCHANTABILITY OR FITNESS OF PURPOSE, EXPRESSED OR IMPLIED, ARE DISCLAIMED.
Please thank Kuromera for hosting the files on a speedy server and check out the other files hosted there. See his thread here - http://forum.xda-developers.com/showthread.php?t=1549055
Download from here!
US version
ics_92117_stock_EBT_SOS.zip
MD5(ics_92117_stock_EBT_SOS.zip)= 201eae30cbeb00687d5cc69c14469027
WW version
ics_92117_WW_stock_EBT_SOS.zip
MD5(ics_92117_WW_stock_EBT_SOS.zip)= 1c8b1aea6d27643f70891b363ff5fa36
http://www.xdafileserver.nl/index.p...+(TF101)/ROMS/Stock+Roms+by+gee+one/With+Root
Alright, gonna try flash this from Revolution 3.0.1, gotta get back to .17, .11 is so unstable for me, random reboots and shutdowns, and I woke up this morning to a flat battery - from 100% before I went to bed...
Will report back inna bit!
+++
All good, thanks (and thanked)!
Flashed over Revolver 3.11, it automatically optimized the apps on first boot, so far so good.
The weather widget won't update my location, but I've had trouble with that on a lot of the stock firmwares. Could also be from the flash over revolver.
Anyways, thanks for the good work.
I'm very interested in a WW version of your update!!
Anything Ican do to help, just tell me, and I will try. But i might need a little guidingalong the way
Sent from my Transformer TF101 using xda premium
edit: OK, WW version should work now
ics_92117_WW_stock_EBT_SOS.zip
MD5(ics_92117_WW_stock_EBT_SOS.zip)= 1c8b1aea6d27643f70891b363ff5fa36
Having difficulties downloading.
I keep getting "download unsuccessful" If I download straight to the tab.
If I download on my PC the MD5 changes every time. File is listed as 300MB but shows up as 193MB???
Can anyone post a mediafire link?? Or anything.
Are you trying to download the US version?
The WW version is uploading now and will probably complete in about half an hour.
Yeah, my upload is slow.... So be sure to thank Kuromera for hosting the files http://forum.xda-developers.com/showthread.php?t=1549055
If anyone is having problems downloading, I uploaded to Box:
I've shared a folder with you through Box.
To access this folder, visit the following link: https://www.box.com/shared/a479f50d578d27a355f9
Due to my account limitations, I had to upload it as a multi-part zip (6 50mb sections, and a tiny trailing 7th section)
Hope that helps!
Sent from my Transformer TF101 using xda premium
OK, WW version is uploaded. Sorry for the confusion.
Quick question...do we nvFlash this or rename it/reboot as if it were a legitimate stock rom?
gVibeR said:
Quick question...do we nvFlash this or rename it/reboot as if it were a legitimate stock rom?
Click to expand...
Click to collapse
This flashes through clockworkmod or any other custom recovery. I think there is a recovery installer.apk in the dev section, or there are nvflash versions of some of the custom recoveries.
gee one said:
Are you trying to download the US version?
The WW version is uploading now and will probably complete in about half an hour.
Yeah, my upload is slow.... So be sure to thank Kuromera for hosting the files http://forum.xda-developers.com/showthread.php?t=1549055
Click to expand...
Click to collapse
Happens with both the US & WW versions. I watched the download stop at approx 190MB. Don't know what's causing it. I guess I'm the only one.
I';ll check the server hold on
Mmm cant see anything strange, the ww file and us file have both be downloaded succesfully allready but i'll keep watch. The server should support download managers btw.
gee one said:
This is a full rom for stock(ish) 9.2.1.17 and includes the following:
NOTE and WARNINGS:
This is for the TF101 US only. The fingerprint checks are removed from the updater-script so it is up to you to know what you are flashing. (Don't flash this on your phone! and if you do, don't say a word and act like your phone is still working.)
This will overwrite your recovery. You can flash it back to something else after a reboot.
This will overwrite your bootloader/EBT. This might have unintended consequences so flash at your own risk. The stock OTA updates the bootloader, so this is why I included it here.
=====================
The WW version make the same, overwrite the bootloader and recovery?
Thanks
Click to expand...
Click to collapse
Yes, they both update the bootloader and recovery. The recovery is based on Roach's 3.2.0.1. You can flash a different recovery after a reboot if you want to change it.
The stock recovery is too limiting with a rooted rom- it's practically useless actually since it won't always restore if changes have been made.
Updating bootloader really means what in practical terms? I am intending to flash this but this bootloader stuff makes me wonder...
Sent from my GT-I9100 using Tapatalk
So far all fine.
Sound finally on the normal volume.
Reboots not seen yet. (too early to tell)
Only problem i had was busy box and super user but fixed it in the end.
WW version.
Cheers!
gee one said:
Yes, they both update the bootloader and recovery. The recovery is based on Roach's 3.2.0.1. You can flash a different recovery after a reboot if you want to change it.
The stock recovery is too limiting with a rooted rom- it's practically useless actually since it won't always restore if changes have been made.
Click to expand...
Click to collapse
Thanks.
About recovery I understand is ease to flash a newest.
And about bootloader, what change? I can continue to flash custom roms and new kernels?
Obrigado
No one can please post an NVFlashable rom of the WW version??
I only need the system and the boot part, as using a dual boot system i can only update via nvflash
PLEASEEEEE!!
AllanJacques said:
Updating bootloader really means what in practical terms? I am intending to flash this but this bootloader stuff makes me wonder...
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
ValenteL said:
Thanks.
About recovery I understand is ease to flash a newest.
And about bootloader, what change? I can continue to flash custom roms and new kernels?
Obrigado
Click to expand...
Click to collapse
The bootloader gets updated with the OTA so I left it in to stay with the rooted stock experience. The bootloader I included is the one asus includes with their update. I'm not sure if other roms will be expecting older bootloaders. I think most nvflash versions use the oldest bootloader still, and I don't know if this will cause any issues. I don't foresee issues with other roms and kernels, although I did notice I had to wipe data completely to get some of the aosp roms to boot.
As I said, this is directed to someone who wants root and a more stock rom. You can edit system to debloat (and reinstall if you take too much out )
sent from my cyanogen(mod) vision
ok so I was an original GS III owner (I preordered, used the original root66, waited for the unlocked bootloader, etc.)
I just rx'ed a 2nd replacement because the power button fell off my first replacement (my 1st gsIII had a faulty modem).
This one came preloaded with the 2nd OTA (VRALHE)
I was wondering the correct method to go about setting it up...
1.) odin the original root66 VRALF and continue in the same way I did with my original one (dd a TWRP and the insecure bootloader)?
2.) I could follow the directions in section 1 here: http://forum.xda-developers.com/showthread.php?t=1762709
and odin a pre-rooted VRBLJ1. It then says I can just go ahead and add a custom recovery (it mentions the EZ app but I'd rather just dd. then do the insecure aboot the same way)
3.) I could follow the directions here: http://forum.xda-developers.com/showthread.php?t=1974114
it mentions ODINing the VRBLJ1 leak and then ODINing a custom recovery but the recoveries INCLUDE "VRBLJ1 Bootchain." Why?
according to Invisiblek (http://rootzwiki.com/topic/29256-ro...-unlock-sch-i535-d2vzwverizon-galaxy-s-iii/):
What the locked bootloader prevents us from doing is flashing, via odin, a custom recovery or kernel. What we can do however, is revert to an older (semi-insecure) bootchain which we have acquired, flash our custom recovery, and then continue on from our freshly flashed custom recovery by flashing an unlocked bootloader and anything else we want.
Kernels from the newer OTA's prevent us from doing this process. We'll need to flash a kernel too...
Click to expand...
Click to collapse
he mentions flashing the VRALEC and then later (after flashing the VRALF2 kernel and a custom recovery) the VRALF2 bootchain. His explanation makes sense, but the other threads say to use the VRBLJ1 bootchain. why all the conflicting info?
Also, as I wrote this I used the rootDebugFS thing on my freshly rx'ed VRALHE. i then dd'ed a recovery and the insecure aboot. Everything is working fine. So what's all the fuss about? and will I encounter problems if I try to odin anything, like invisiblek said?
Thanks
preusstang said:
ok so I was an original GS III owner (I preordered, used the original root66, waited for the unlocked bootloader, etc.)
I just rx'ed a 2nd replacement because the power button fell off my first replacement (my 1st gsIII had a faulty modem).
This one came preloaded with the 2nd OTA (VRALHE)
I was wondering the correct method to go about setting it up...
1.) odin the original root66 VRALF and continue in the same way I did with my original one (dd a TWRP and the insecure bootloader)?
2.) I could follow the directions in section 1 here: http://forum.xda-developers.com/showthread.php?t=1762709
and odin a pre-rooted VRBLJ1. It then says I can just go ahead and add a custom recovery (it mentions the EZ app but I'd rather just dd. then do the insecure aboot the same way)
3.) I could follow the directions here: http://forum.xda-developers.com/showthread.php?t=1974114
it mentions ODINing the VRBLJ1 leak and then ODINing a custom recovery but the recoveries INCLUDE "VRBLJ1 Bootchain." Why?
according to Invisiblek (http://rootzwiki.com/topic/29256-ro...-unlock-sch-i535-d2vzwverizon-galaxy-s-iii/):
he mentions flashing the VRALEC and then later (after flashing the VRALF2 kernel and a custom recovery) the VRALF2 bootchain. His explanation makes sense, but the other threads say to use the VRBLJ1 bootchain. why all the conflicting info?
Also, as I wrote this I used the rootDebugFS thing on my freshly rx'ed VRALHE. i then dd'ed a recovery and the insecure aboot. Everything is working fine. So what's all the fuss about? and will I encounter problems if I try to odin anything, like invisiblek said?
Thanks
Click to expand...
Click to collapse
I'm assuming since VRBLJ1 is the newest JB leak then it uses the newer boot chain. The only reason you would need that boot chain to unlock the bootloader is if you used Odin to flash the newest VZW JB leak onto your phone. Then you would need it to unlock the VRBLJ1 JB leak. If you are are any of the ICS stock ROMs and want to unlock you can use the old way of doing it. The post you are reading from invisiblek is old, it was when we were on the VRALFW stock ROM.
Now I have no clue why you would want to use Odin to flash the newest JB leak when you can do it by downloading the version of the ROM made to be flashed with TWRP or CWM. I would love to have a dev or someone knowledgeable about these things to chime in and tell us if there is any benefit to using Odin to update to the newest JB leak or if there is no difference between having the JB leak or one of the OTA's on your phone before you flash a ROM.
Sent from one of the many Anthropomorphic Personalities on the Disc
shangrila500 said:
I'm assuming since VRBLJ1 is the newest JB leak then it uses the newer boot chain. The only reason you would need that boot chain to unlock the bootloader is if you used Odin to flash the newest VZW JB leak onto your phone. Then you would need it to unlock the VRBLJ1 JB leak. If you are are any of the ICS stock ROMs and want to unlock you can use the old way of doing it. The post you are reading from invisiblek is old, it was when we were on the VRALFW stock ROM.
Now I have no clue why you would want to use Odin to flash the newest JB leak when you can do it by downloading the version of the ROM made to be flashed with TWRP or CWM. I would love to have a dev or someone knowledgeable about these things to chime in and tell us if there is any benefit to using Odin to update to the newest JB leak or if there is no difference between having the JB leak or one of the OTA's on your phone before you flash a ROM.
Sent from one of the many Anthropomorphic Personalities on the Disc
Click to expand...
Click to collapse
Its just another way of basically doing the same thing. If your already rooted and have cwm recovery, then flashing a J1 rom via cwm or twrp recovery is by far the easiest method. Now if your stock and unrooted, it would be easier to odin root66 J1 , then unlock and get cwm recovery via the ez unlock/recovery apps. This is why I have 2 different methods in my guide...I also chose to not flash bootchains unless its a last resort because they can perma brick a device if something goes wrong. Also I like to use methods that dont trip the flash counter, makes for one less thing to do if the device ever needs to be returned.
droidstyle said:
Its just another way of basically doing the same thing. If your already rooted and have cwm recovery, then flashing a J1 rom via cwm or twrp recovery is by far the easiest method. Now if your stock and unrooted, it would be easier to odin root66 J1 , then unlock and get cwm recovery via the ez unlock/recovery apps. This is why I have 2 different methods in my guide...I also chose to not flash bootchains unless its a last resort because they can perma brick a device if something goes wrong. Also I like to use methods that dont trip the flash counter, makes for one less thing to do if the device ever needs to be returned.
Click to expand...
Click to collapse
Gotcha, that's been bothering me for a few days. I remember when I was flashing on my RAZR that the stock OTA was the base for everything and if you didn't have the latest OTA some of the ROMs wouldn't run on your phone until you updated and some of the older ROMs wouldn't work until they had been updated to work on the newest OTA or leak. The ROMs were just overlays and usually only added a little bit of added performance or functionality.
Would updating to the latest OTA via Odin add any benefits like it did on the RAZR ? I know the RAZR wasn't unlocked and we weren't flashing ROMs like we do on the GS3 but.....
Sent from one of the many Anthropomorphic Personalities on the Disc
no not on samsung devices...you can go from f2 to the latest with no issues.
droidstyle said:
no not on samsung devices...you can go from f2 to the latest with no issues.
Click to expand...
Click to collapse
No I get that, I was meaning are there any positive side effects from using the newest JB leak as your base ROM before flashing a new one. Like flashing the new JB leak via Odin, then unlocking and flashing a new ROM on top of it. Will there be any benefits like there were on the RAZR or when we flash in custom recoveries does it completely do away with the stock ROM that was on the system partition and replace it with whatever we flash? I know on the RAZR you would use the ROM you were on as a base you flash whatever else you wanted and there were benefits to having a certain OTA as your base before you flashed. I don't think I'm doing a very good job of phrasing my question, I apologize for that. Its just a hard question to put into words.
Sent from one of the many Anthropomorphic Personalities on the Disc
shangrila500 said:
No I get that, I was meaning are there any positive side effects from using the newest JB leak as your base ROM before flashing a new one. Like flashing the new JB leak via Odin, then unlocking and flashing a new ROM on top of it. Will there be any benefits like there were on the RAZR or when we flash in custom recoveries does it completely do away with the stock ROM that was on the system partition and replace it with whatever we flash? I know on the RAZR you would use the ROM you were on as a base you flash whatever else you wanted and there were benefits to having a certain OTA as your base before you flashed. I don't think I'm doing a very good job of phrasing my question, I apologize for that. Its just a hard question to put into words.
Sent from one of the many Anthropomorphic Personalities on the Disc
Click to expand...
Click to collapse
no not on samsung devices...the reason you needed to do that on the moto device is because of the locked bootloader. meaning you couldnt replace the kernel, so you had to ota to the latest, then root , recovery, and flash rom. since our device is fully unlocked, we dont have to worry about this. most if not all roms for d2vzw are packaged with a kernel. so it does not matter what current base your on, flashing a rom will overwrite it.
droidstyle said:
no not on samsung devices...the reason you needed to do that on the moto device is because of the locked bootloader. meaning you couldnt replace the kernel, so you had to ota to the latest, then root , recovery, and flash rom. since our device is fully unlocked, we dont have to worry about this. most if not all roms for d2vzw are packaged with a kernel. so it does not matter what current base your on, flashing a rom will overwrite it.
Click to expand...
Click to collapse
That's what I thought. I was just wanting a little clarification on that. Thanks man!!!
Sent from one of the many Anthropomorphic Personalities of the Disc
I've got the ICS bootloader and wanted to flash the new bootloader and get cm10 back on my device.
Couldn't I just flash the blob for 4.1 to do this? I see the 'how to' that talks about moving files here and there, but shouldn't I be able to use the tool to install the latest stock/ota blob to do the same thing?
beepea206 said:
I've got the ICS bootloader and wanted to flash the new bootloader and get cm10 back on my device.
Couldn't I just flash the blob for 4.1 to do this? I see the 'how to' that talks about moving files here and there, but shouldn't I be able to use the tool to install the latest stock/ota blob to do the same thing?
Click to expand...
Click to collapse
If you're still on ICS, I would recommend you first to back up your bootloader using nvflash (search the development forum). Updating to JB will also re-write the bootloader and there isn't a known way to revert that change, meaning that once you flash JB you can't go back to ICS. Although I never had to go back to ICS cause JB is pretty stable, I did it anyway just to be on the safe side.
Once you do that (or if you already did) you are better off running asus update to JB. As far as I know, in order to flash JB roms you need a JB recovery image, which you can't install if you're on ICS.
Yea, that was kinda what I was looking to find out... Can't we just use the Asus update and blobs to go to jb and, if we wanted, back to ics?
Since it wipes the device, can't we just use the Asus updater and tool rather than the overly complicated method described in another post?
It's been a while since I've had to flash a blob, but I think it was the Viper tool I used... Seems like we could just get the ICS and jb blobs and use that tool to flash which ever we wanted. But someone please correct me if I'm wrong.