I have tracked down the last "stable" cm build for the TF101(CM9) and combined it with the necessary gapps through a TWRP backup. It is untouched, and ready to be restored.
You need to unzip the file and place the contained folder inside your TWRP backup folder. Hope this helps someone.
FLASH AT YOUR OWN RISK (as always) :b
https://goo.gl/cxduLx
This one includes/flashes backup of recovery partion TWRP 2.3.2.3:
https://goo.gl/KtVXdw
Current kernel is 2.6.39.4_CyanogenMod_DHD-g74007d5 pinky-ghost.
IF you still out there you got a mirror?
Silverobot ...Were you able to find a working link for the recovery file?
Related
I know that Acer pulled today's update, but will it be possible to switch when it is released again?
Leaked 3.1 to official 3.1
Yes it is, just a little confusing though. You have to know which region your tablet is from http://secure3.tx.acer.com/FindSystem/FindSystem.aspx?title=Information About Your System. And then go about flashing a couple of ROMs to get you ready for the update. Instructions here:
http://forum.xda-developers.com/showthread.php?t=1155664
I am a total noob and wasted my whole day yesterday trying to figure this out. In the end texonex helped me out. Starting with the leaked 3.1 update here's what I did (courtesy texonex):
1. Root the device (http://forum.xda-developers.com/showthread.php?t=1138228). Download Acer Recovery Installer from the market, and from there install the clockwork recovery image. Choose no for a backup of the current recovery.
2. Download the backup file for 1.104.02 here, thanks to camelot1972
dl.dropbox.com/u/34113636/2011-06-24.12.20.13.zip, I guess you could also use the file from here: http://forum.xda-developers.com/showthread.php?t=1113878. This is for the US version.
If your tablet is from another region you would have to find the appropriate "default" version number in the how-to (what firmware is right for my country).
3. Extract the contents from the zip file and put them in the backup folder for clockwork mod on your SD card (take your SD card out of the tablet and connect directly for all the steps), if you do not see the backup folder, I suppose you can make one,e.g. [micro sd]\clockworkmod\backup\2011-06-25.22.14.07. I guess this exact string will still show up in clockwork recovery. I made a backup of the leaked 3.1 and that gave me the folder, and I just replaced the files. The date part is obvious in the name however I wouldn't venture a guess what are the other digits in the folder name.
If you downloaded the file from [OTA] Full Package and Update page, you'll need first to decrypt the file using the decrypter and then extract the contents of the decrypted file. One of the extracted files is update.zip which goes on to the SD card no subfolder in this case.
4. Restore the firmware using CMW using full restore for the US version, or update from the sd card zip if using a full package zip file.
At this point I think you need to save the recovery image for the non-US versions. Follow the instructions in the how-to or just use acer recovery installer to flash the clockword recovery again and this time choose yes to backup the current image.
5. Download 1.104.02 to 1.141.07 update and flash it with CMW.
Or the appropriate latest update file from your region(highest version number).
6. Flash recovery image to 1.141.07, this is option 4 in Acer recovery installer.
For non-us versions restore the recovery image, unroot and restore factory defaults.
7. I stopped here and now am waiting for the OTA. According to the how-to, you roll back to the full defualt package by using the standard ACER recovery (Power + -Vol) after copying the zip file on to the SD card, delete the zip file copied before.
8. Go to settings and trigger update manually. OTA will prompt you the new 3.1 update. I suppose you do not need to unroot.
You can also install the stock ROM from here:
http://forum.xda-developers.com/showthread.php?t=1159443
Thanks to Bec07 (how-to), vache (stock roms) and sc2k (un-rooting) for their contributions or I would have been totally lost in trying to downgrade my tablet from the leaked 3.1. Hope this is helpful, and goes smoothly because if it does not I wouldn't have clue how to fix it.
Sorry for this off-topic post, but you said that acer pulled the update: And I still have it (haven't updated and cant anyway). Is this not right?
What I meant was its not being pushed to more users for now.
Since I had to RUU my phone to stock sense today I had to create a flashable zip file since im on a Mac (unfortuately).
Anyways here is a link to the zip.
Instructions:
1) Backup everything (TI backup and nandroid backups via CWM).
2) Copy backups from SDcard of phone to your computer
3) Copy PG016IMG.zip to sdcard of your phone
4) Run adb reboot fastboot from adndroid sdk platform tools folder
5) Reboot recovery
6) Fastboot recovery will find the PG016IMG.zip and ask if you want to flash, say yes. It will check the file and start flashing.
7) You will see TP being bypassed twice, then the 3rd TP being flashed.
Once it complete the phone will reboot and you will be on stock HTC Sense Android 2.2.
Enjoy.
http://www.multiupload.com/1G88PQX30Q
md5: 27095270aa8e0708a1e774ac01ec6dd6
You are aware that we already have this, right? One "zip" RUU-Back to stock-2.3 zip removed completely
crump84 said:
You are aware that we already have this, right? One "zip" RUU-Back to stock-2.3 zip removed completely
Click to expand...
Click to collapse
edit: nevermind, I am now. Wish I had seen that before I had to go through compiling unshield and running unruu. It wasn't on the wiki. Oh well. thanks!
Hi,
I don't know if this is the correct section to get this question answered, but I'll try:
I have a new tablet, which is not really known at the moment. I managed to root it and next step would be to port Clockworkmod Recovery to it. Since I only found guides where I always have to repo sync the entire CyanogenMod github (which is 19GB+ as I heard), I searched for an alternative where I could save some traffic
I found a clockworkmod recovery from another tablet and wondered if it was just possible to unpack it, modify the recovery.fstab and repack it again.
Is this possible or do I have to modify more than the recovery.fstab? If yes, could you point me to the right direction?
Regards
dump your stock recovery
unpack the stock recovery and save the vold.fstab somewhere.
upload the stock recovery here
http://builder.clockworkmod.com/
get the output and flash`it
if the key`s are not working, unpack the new cwm, and the old recovery, and put the keys from the old recovery.
if you get some mount points erros, you will have to upload also the saved vold.fstab on the clockwork site when you cook the image.
if this does not offer you a good result, you will need to find a similar device (processor, resolution) that has allready a cwm, and try it
the recovery file is ramdisk/sbin/recovery
Hi,
thanks for showing me a way. Unfortunately builder.clockworkmod.com says it didn't find Android magic. This makes sense, as the image is a uImage with lzma compressed data inside. It seems koush's builder handles only "plain" recoveries...
Bad luck
I guess I'll try your second advice and search for a CWM for a similar device, unpack it, replace the fstab file and repack it again.
Thanks again!
hello I have made the porting on http://jenkins.cyanogenmod.com/job/recovery/lastBuild/console
I end up having a zip archive, how can I make my tablet to read that. I have installed cwm recovery and it is rooted. Let me know how can install it and replace my recovery with this.
BTW I have the original stock firmware of my tablet.
let me know thanks
I'm trying to return to stock without usb, but the links from this post don't work http://forum.xda-developers.com/showpost.php?p=34749844&postcount=2
I need a flashable .zip of the stock rom & recovery so that I can turn my phone in for RMA
studjuice said:
I need a flashable .zip of the stock rom & recovery so that I can turn my phone in for RMA
Click to expand...
Click to collapse
Right now there is no flashable image of the stock OS. Google pulled it from their site. But if you can't use USB, you can still use a computer to unzip the image into partitions, then use terminal and `flash_image` to flash each partition. (When I tried using flash_image, it didn't work, so be cautious. If you're rooted you can also use `dd` to flash images, but a typo could brick your phone so don't.)
I bet the easiest thing for you to do is to create individual flashable images for each partition, then boot into CWM and flash each (recovery last, obviously). But I don't know how. In any case, you'll need to wait until Google puts a new mako image on their site: https://developers.google.com/android/nexus/images
---------- Post added at 07:30 AM ---------- Previous post was at 06:56 AM ----------
Actually, depending on how desperate you are, I (or anybody else) could help you. I have a stock recovery installed right now (JOP40D) and I could pull the image with "dd". That won't be a flashable .zip, but you should be able to flash it from within the ROM. I could also get you a copy of my /system partition--there's nothing personal or private in there
If you have a .img, you could pack it into a flashable .zip and download it via dropbox.
Unless you have no access at all to a computer. In that case, you'll just need to wait for Google to release the next version of the image.
fenstre said:
Right now there is no flashable image of the stock OS. Google pulled it from their site. But if you can't use USB, you can still use a computer to unzip the image into partitions, then use terminal and `flash_image` to flash each partition. (When I tried using flash_image, it didn't work, so be cautious. If you're rooted you can also use `dd` to flash images, but a typo could brick your phone so don't.)
I bet the easiest thing for you to do is to create individual flashable images for each partition, then boot into CWM and flash each (recovery last, obviously). But I don't know how. In any case, you'll need to wait until Google puts a new mako image on their site: https://developers.google.com/android/nexus/images
---------- Post added at 07:30 AM ---------- Previous post was at 06:56 AM ----------
Actually, depending on how desperate you are, I (or anybody else) could help you. I have a stock recovery installed right now (JOP40D) and I could pull the image with "dd". That won't be a flashable .zip, but you should be able to flash it from within the ROM. I could also get you a copy of my /system partition--there's nothing personal or private in there
If you have a .img, you could pack it into a flashable .zip and download it via dropbox.
Unless you have no access at all to a computer. In that case, you'll just need to wait for Google to release the next version of the image.
Click to expand...
Click to collapse
I would love some help on packing into a flashable .zip. I found the images here, http://www.randomphantasmagoria.com/firmware/nexus-4/occam/ but I can't do anything with them without fastboot.
I found one guide for creating the flashable zip here: http://forum.xda-developers.com/showthread.php?t=1721680
And a better one here: http://forum.xda-developers.com/showthread.php?t=1949367
In principle, I think you could use your phone to do these, but it would be hard. The hardest step would be extracting individual files from .img files, and I don't know whether you can do that with your phone--it depends on the kernel and the "mount" utility--you would need to mount the .img files as a filesystem and extract from them. Obviously you should avoid flashing /data to ensure that you can keep /sdcard and your CWM backup. And flashing stock recovery should be your last step. In fact, don't flash your stock recovery. Flash the Nexus image version C, then reboot and let the image automatically reflash the recovery. This is safest. But if this step messes up, you will absolutely need to use a computer to fix it.
Actually, there's a far easier way. Somebody could create a CWM backup for you--a backup of version JOP40C. You download it to /data/media/clockworkmod/backups, then use CWM to recover it (use advanced options to recovery ONLY the /system partition (maybe others?), then clear the cache and dalvik cache). Then you OTA upgrade to JOP40D. This will involve downloading a flashable .zip (here). The key is that this will remove root and CWM when you next reboot! If it doesn't remove root, I think you can probably do that yourself.
The thing you can't do without a computer: lock your bootloader. Is using somebody else's computer really out of the question? I think "adb" and "fastboot" work without the rest of the Android SDK, so you could just download them and get to a computer just for the very final step of re-locking the bootloader.
I documented the process I went through to get it back to stock here for future reference:
http://forum.xda-developers.com/showpost.php?p=37064957&postcount=10
You can lock your bootloader without a computer using the BootUnlocker app
Android N Preview 2 npc91k (flashable & image with no encryption and dm verification)
This thread is for the second Android N Preview.
For Android N Preview 3 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-3-beta-npd35k-t3381845
For Android N Preview 4 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-4-beta-npd56n-t3399473
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **** The following are instruction for installing Android N Preview 2 image released by Google on 4/13/2016. After the installation you will have TWRP recovery 3.0.2-0 with the data partition erased and unencrypted if you use method 2, which means you will have ~ 3GB more space and ~ 10 seconds faster boot speed **Always backup your data before flashing something a total stranger gives you!
Method 1: Flash update through TWRP recovery (keeps your data and current recovery)
1- You need to have TWRP installed on your phone.
2- Download this flashable zip..
3- Copy to the phone internal storage and flash via recovery.
4- Reboot. Your data should still be intact and your OS is upgraded to N Preview 2. If your internal storage is unencrypted before flashing it remains unencrypted.
For some people this didn't work. It seems to be the case when you have been encrypted by your previous Android N installation, in which case TWRP seems to have difficulty reading the file, and that seemingly Preview 2 doesn't play nice with TWRP. It works best when you are unencrypted and your recovery is 3.0.2-0. Thanks to @gammaxgoblin, @blitzerking1, @Michael in ATL, @HueyT, and @PhillyFlyer for debugging and hints.
Method 2: Flash update using a computer (wipes everything, unencrypts data, and upgrades TWRP)
1- ALL of your data including the internal storage will be lost so make a backup. (If you know what you are doing and you are coming from unencrypted Marshmallow you can modify the instructions to not lose data but I won't help you with that).
2- Download this file. Note that it is NOT a flashable zip.
3- Unzip into a folder of your choice on your PC.
4- Open a command window (cmd) and cd to this directory. then run the following:
Code:
flash-all
5- Wait until prompted, then press key to reboot the phone.
6- Your data is wiped and your OS is upgraded to N with unencrypted internal storage. Your TWRP is also upgraded to 3.0.2-0.
Technical details: this is a repacking of the Google image with a modified Kernel and removed userdata and recovery images. Everything else is stock.
Problem downloading from Mega on a mobile browser? Change the page setting to "Request desktop site".
About root and other issues
To obtain root after installing this update you should flash SuperSU 2.71 (or higher) in recovery. Get it from here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133. Despite the fact that SuperSU 2.71 is supposedly re-written for Android N, there are still some apps that seem to have a problem obtaining root. The commonest complaint on this thread so far has been about Adaway. If you want to block Ads just manually do what Adaway does. Download a hosts file from any ad block list server such as http://winhelp2002.mvps.org/hosts.htm, copy the files on your sdcard, boot the phone into recovery, and using the TWRP file manager replace the file /system/etc/hosts with this file and set its permissions to 644 (rw-r--r--).
wouldnt flash first go. redl now
no flash again
gammaxgoblin said:
wouldnt flash first go. redl now
no flash again
Click to expand...
Click to collapse
Same happened to me. It would not flash, same error
gammaxgoblin said:
wouldnt flash first go. redl now
no flash again
Click to expand...
Click to collapse
Can you open the zip that you downloaded and see if you can see the file that it is complaining about? What version of twrp are you using?
najoor said:
Can you open the zip that you downloaded and see if you can see the file that it is complaining about? What version of twrp are you using?
Click to expand...
Click to collapse
Same error for me as well. I can extract the zip and view the file it is talking about. I also tried on TWRP 3.0.1-0 and TWRP 3.0.2-0
Everything is working perfect for me with the new zip. I have a unencrypted phone and used 3.0.2 TWRP.
najoor said:
Can you open the zip that you downloaded and see if you can see the file that it is complaining about? What version of twrp are you using?
Click to expand...
Click to collapse
i tried 3.0.1 and 3.0.2 and i can also see the file
Method 2 works great
Method two works I used it myself
Shall I flash preview 2 directly from marshmallow?
Seems like TWRP is having a lot of troubles with each version of N Preview's encryption. I have same problem with both N6 and N6P, as do others in that forum too....:/
i have latest twrp, download a ota update from ofiicial site in zip file and flash it over in twrp. boot normally and works fine. only flash supersu 2.71 and it's unencrypted at all.
ps. TB not works for me ind N prew2 so i flash perv1, restore from TB and flash prew2 over it.
marius987 said:
i have latest twrp, download a ota update from ofiicial site in zip file and flash it over in twrp. boot normally and works fine. only flash supersu 2.71 and it's unencrypted at all.
ps. TB not works for me ind N prew2 so i flash perv1, restore from TB and flash prew2 over it.
Click to expand...
Click to collapse
Sorry for the stupid question. What do you mean for TB?
cerico76 said:
Sorry for the stupid question. What do you mean for TB?
Click to expand...
Click to collapse
I'm going to assume it stands for Titanium Backup.
Waiting for fixed method #1
outkastz said:
I'm going to assume it stands for Titanium Backup.
Click to expand...
Click to collapse
Ah,yes! Thanx!
Can someone please provide a link to the desktop website for the flashable zip?
Just to help with the installation of method 2, holding shift and right clicking a blank space in your unzipped folder, you can click open command window here. That will save you having to CD all the way to it.
Sent from my Nexus 6 using XDA-Developers mobile app
I did method 1. It upgraded fine. All my data remained. It killed root (expected this) and my TWRP. I was unencrypted before attempting.
I went and downloaded the latest TWRP and flashed via fastboot. Then downloaded latest SuperSU from http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 and flashed it via my newly installed TWRP. Root confirmed and all is well.
Good to go Thanks!
I've got an "Invalid boot image" issue :
Any tought ?
outpox said:
I've got an "Invalid boot image" issue :
Any tought ?
Click to expand...
Click to collapse
You may have to flash a previous stable release of marshmallow or lollipop from Google first and then try this because something seems to be corrupted in your system.