CWM 5.0.2.6 Recovery
Stable with all features working.
Features:
Working:
Backup&Restore
Installing ZIP from SD Card
Wipe DATA,CACHE,Dalvik-Cache,Battery Stats
EXT4 support for sd-ext(A2SD) partition
Added support for HOME, MENU,SEARCH & back button for menu navigation.
Volume key bug totally fixed
Enabled USB Mass Storage mount support during recovery.
Enabled ADB support during recovery.
All other functions working in the previous version.
Instructions:
Installation:
Download recovery image and save it in the root of your SD Card
Go to Terminal Emulator and type:
Code:
>su
>flash_image recovery /sdcard/recovery.img
>reboot recovery
Navigation:
UP:Home Button,Volume UP.
DOWN:Menu Button ,Volume DOWN
SELECT:Search Button,Power Key.
BACK:Back Button
Download Link:
HTML:
http://dl.dropbox.com/u/21654931/recovery.img
Credits:
Koush for his source
TJStyle for his kernel
Source:https://github.com/mb-14/android_device_fih_fm6
Note:
If ITE users are facing problems with CWM try this ITE version created by s2k7:
http://www.multiupload.com/0UA3OKWFWC
Nice one ! Thank you !
Thanks a lot, GHome
Sent from my HTC Sensation Z710e using XDA App
Thank manys man.
Volume key navigation is still bugged
LayZeeDK said:
Volume key navigation is still bugged
Click to expand...
Click to collapse
I know its bugged but i provided an alternative for up-down navigation i.e home key and menu key
googlehome said:
I know its bugged but i provided an alternative for up-down navigation i.e home key and menu key
Click to expand...
Click to collapse
Yes, that works
Sent from my HTC Sensation Z710e using XDA App
CWM 3.0.2.8 Recovery works good and stable on Viewsonic ViewPad 7.
Thank you again Googlehome, you're the best.
Not working for me on HWVer 1.06 and Android 2.2.2.
Won't let install me. Not enough memory when flashing.
CWRecovery 2.x works.
astuermer said:
Not working for me on HWVer 1.06 and Android 2.2.2.
Won't let install me. Not enough memory when flashing.
CWRecovery 2.x works.
Click to expand...
Click to collapse
Is your device running low on internal storage and/or available RAM ?
It was a quick & easy install/update for me - did it right after I re-flash one of the custom ROM upon rooting & the Vpad7 running. Followed instructions above & it was done - then, I restore settings, etc.
The newer Recovery is much improved & better, with more options to choose from. It shouldn't take up much, if any memory, to flash & install this at all ....
80 mb ram left...
flashed over cwrecovery 2.x and got errors.
i didn't try restarting the device - instead i reflashed cwrecovery 2.x and got no errors.
I also tried it with ROM Manager.
I manually select N700... and then CW 3.x.x
When trying to install i get an error message that installing went wrong.
If I install it manually via Shell I get many error messages (see posting before). Looks like the partition table is a bit changed since the CW 2.x is smaller than CW 3.x.
astuermer said:
Not working for me on HWVer 1.06 and Android 2.2.2.
Won't let install me. Not enough memory when flashing.
CWRecovery 2.x works.
Click to expand...
Click to collapse
Please provide exact error message.
mtd: read error at 0x00100000 (Out of memory)
...around 100 times
...with different read/re-read/write errors and different adresses (0x...)
Any idea?
astuermer said:
mtd: read error at 0x00100000 (Out of memory)
...around 100 times
...with different read/re-read/write errors and different adresses (0x...)
Any idea?
Click to expand...
Click to collapse
(Re-reading your posts) So, this is while you are trying to flash the downloaded recovery.img file saved to mSD card using Terminal connected to PC, and it even popped up with CWM 2.x ?
Tried using a fully wiped clean & different mSD card (re-formatted on PC with FAT32 or FAT) - I use a spare 2 GB or 4 GB mSD card to try out new Roms to avoid having to "corrupt" or risk losing all the "stuff" on the fast 16GB mSD card.
Have a spare PC or do it on a different one with another OS - Vista, Windows 7, etc. (done mine with XP SP3) & substitute a different mini-usb cable ? It seemed that the data transfer process between the "machines" could be the problem - a bad "connector" ?
Maybe try a fresh copy of your toolkits like fastboot-adB, su & busybox - SDK etc. are in the same directory/folder - and not missing ?
Here's a XDA link to a useful shell tool - Droid Explorer - good for exploring what's on your device - use it with extreme caution as the "Tools" it provided can be used to flash ROM, etc. (NOT tested or proven to work specifically with Vpad7 .... fine to use it to identify & read data, etc.) - http://de.codeplex.com/
Thanks, but I flashed it with "flash_image" and the tool "Shell Commander" directly on the device.
I used this tutorial for Clockwork 2.x...
http://android.modaco.com/topic/324042-clockwork-recovery-for-mi700n700viewpad-7/
And the same way I flashed Clockwork 3.x from the first post here.
The Clockwork Recovery 2.x I am using has 4.591.616 bytes.
Clockwork 3.x has 4.745.216 bytes - so it seems to me it's too big for the recovery partition.
astuermer said:
Thanks, but I flashed it with "flash_image" and the tool "Shell Commander" directly on the device.
I used this tutorial for Clockwork 2.x...
http://android.modaco.com/topic/324042-clockwork-recovery-for-mi700n700viewpad-7/
And the same way I flashed Clockwork 3.x from the first post here.
The Clockwork Recovery 2.x I am using has 4.591.616 bytes.
Clockwork 3.x has 4.745.216 bytes - so it seems to me it's too big for the recovery partition.
Click to expand...
Click to collapse
Those *.img files aren't the right size - I checked mine & also copies of the download that I kept, CWM 3.x is ONLY 4,484 kb or 4.37 MB in size (named: cwrecovery.img)
Similar recovery *.img are somewhere between 4 and 5 MB in size only including the stock recovery.img that I've saved. You might want to re-download using Googlehome's dropbox link on top of this post and tried it.
Then, connect device via usb cable to computer, execute terminal and push it onto device (follow GH's steps) I felt that those steps outline in the MoDaCo site a bit confusing when rooting - of course, that's just me (and, I ended up using GingerBreak to root, but 2nd. time around - the One Click worked too)
Something just doesn't look right from you description ....
That's what I did...
Flashing the same way CWR 2.5.1.2. results in no errors and a flashed recovery.
PS: I already tried downloading from the dropbox link several times, copied it over to my SD. No success when flashing...
PPS: 2 GB free on SD, 54 MB free internal memory and 181+77 MB free RAM.
Maybe you have the wrong flash_image. There are at least two different versions of it here on XDA, and I had trouble with one of them on my VPad. Unfortunately, I don't have my device atm.
Sent from my HTC Sensation Z710e using XDA App
Related
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Dees_Troy said:
[RECOVERY] TeamWin Recovery Project (twrp) 2.0.0RC0 [2011-12-17]
Team Win Recovery Project 2.0, or twrp2 for short, is a custom recovery built with ease of use and customization in mind.
Special thanks to xboarder56 for helping test the port and a couple of other testers that I forget the names of at the moment.
Click to expand...
Click to collapse
NICE, thanks to the both of you! Goin' on tonight fo sho.
Very nice job guys! I just might have to update my signature now.
Is there any future in external sdcard support?
Looks good I guess I'll have to update from the old version, thanks.
Awesome work guys.... this kicks total butt!
Nice! It's come a long way since I used it on my 3D. Alot faster compressed backup, thanks
Sent from my HTC Amaze 4G using xda premium
Has anyone had luck installing this on amaze????
Sent from my HTC Amaze 4G using xda premium
milo356 said:
Has anyone had luck installing this on amaze????
Sent from my HTC Amaze 4G using xda premium
Click to expand...
Click to collapse
I have. I can do it in different ways. flash_image recovery recoveryname.img command from the phone itself if you have the flash_image binary installed or by fastboot flash recovery recoveryname.img with the phone in bootloader mode.
Not complicated at all.
Works great, so much better than using the volume up/down keys and power keys. Two weird things that I want to see if anyone else is having issues with (want to know if it is worth reporting on the github)
1. After accessing recovery I get the "Tell HTC" This phone has just recovered from a abnormal reset message. Didn't get that with clockwork, not sure if it is a bug or not.
2. Cant mount ext SD card. Saw that the EVO 3D had the same issue but they had fixed it. I assume this is a problem with the Amaze since it is the same with clockwork mod?
Sikety said:
Works great, so much better than using the volume up/down keys and power keys. Two weird things that I want to see if anyone else is having issues with (want to know if it is worth reporting on the github)
1. After accessing recovery I get the "Tell HTC" This phone has just recovered from a abnormal reset message. Didn't get that with clockwork, not sure if it is a bug or not.
2. Cant mount ext SD card. Saw that the EVO 3D had the same issue but they had fixed it. I assume this is a problem with the Amaze since it is the same with clockwork mod?
Click to expand...
Click to collapse
Use this one if you want to backup and restore to and from external sdcard.
pardon the question, I've looked all over TeamWin's web site... Is there a way to boot the Amaze into twerp directly?
gregma said:
pardon the question, I've looked all over TeamWin's web site... Is there a way to boot the Amaze into twerp directly?
Click to expand...
Click to collapse
I don't understand your question.
You want to reboot into recovery?
adb reboot recovery
or use the 22 different other ways to reboot into recovery.
Binary100100 said:
I don't understand your question.
You want to reboot into recovery?
adb reboot recovery
or use the 22 different other ways to reboot into recovery.
Click to expand...
Click to collapse
I'm talking about rebooting into recovery when I'm not anywhere near a computer. Such as on my HD2, I would hold the power button down until in MAGLDR, then choose to boot into Recovery. Is there something similar on the Amaze?
Greg
gregma said:
I'm talking about rebooting into recovery when I'm not anywhere near a computer. Such as on my HD2, I would hold the power button down until in MAGLDR, then choose to boot into Recovery. Is there something similar on the Amaze?
Greg
Click to expand...
Click to collapse
Which rom are you using?
There are a couple of roms that have the Advanced Power Menu that has a reboot option. When selected it gives you other options such as recovery and bootloader.
There are also a few apps (do a search for Reboot Recovery) on the Market.
I have always used the option from ROM Manager.
You can also use terminal emulator and use the command "reboot recovery" and that should do it too.
You can also power off the device, hold volume down while pressing power to get to hboot mode then select recovery.
Binary100100 said:
Which rom are you using?
There are a couple of roms that have the Advanced Power Menu that has a reboot option. When selected it gives you other options such as recovery and bootloader.
There are also a few apps (do a search for Reboot Recovery) on the Market.
I have always used the option from ROM Manager.
You can also use terminal emulator and use the command "reboot recovery" and that should do it too.
You can also power off the device, hold volume down while pressing power to get to hboot mode then select recovery.
Click to expand...
Click to collapse
Stock ROM right now, I'm getting things set to start flashing new ROM's. Aha! I did see the "recovery" in hboot. Now once I figure out how I lost the ability to get into hboot by holding the volume down button I'll be good to go!
Greg
---------- Post added at 01:55 PM ---------- Previous post was at 01:22 PM ----------
gregma said:
Stock ROM right now, I'm getting things set to start flashing new ROM's. Aha! I did see the "recovery" in hboot. Now once I figure out how I lost the ability to get into hboot by holding the volume down button I'll be good to go!
Greg
Click to expand...
Click to collapse
I LOVE answering my own darned post.... Didn't realize you had to battery power cycle the device to get it back into hboot. I'm good to go now!
Greg
ok i got it loaded up fine on my phone but i cannot figure out how to flash. i click the install button and it takes me to my directories but i dont see any files in the directories... there is no files listed in the root of either sd card as well. what am i doing wrong?
2sh0rt said:
ok i got it loaded up fine on my phone but i cannot figure out how to flash. i click the install button and it takes me to my directories but i dont see any files in the directories... there is no files listed in the root of either sd card as well. what am i doing wrong?
Click to expand...
Click to collapse
Move the zip file to the other sdcard. Remember that you have two.
Here's a free tip!
Make two empty zip files.
Name one internal.zip
Name the other external.zip
Place the internal.zip in the internal sdcard and the external.zip in the external sdcard.
Reboot into recovery and if you see internal.zip file. Guess what sdcard you're looking at? Same goes for external.
Binary100100 said:
Move the zip file to the other sdcard. Remember that you have two.
Here's a free tip!
Make two empty zip files.
Name one internal.zip
Name the other external.zip
Place the internal.zip in the internal sdcard and the external.zip in the external sdcard.
Reboot into recovery and if you see internal.zip file. Guess what sdcard you're looking at? Same goes for external.
Click to expand...
Click to collapse
Dude, i know this... i came from the vibrant. Im saying that NEITHER card shows ANY files... only directories... no zips on the root of /sdcard or /sdcard/ext-sd... nada, zip, zilch
2sh0rt said:
Dude, i know this... i came from the vibrant. Im saying that NEITHER card shows ANY files... only directories... no zips on the root of /sdcard or /sdcard/ext-sd... nada, zip, zilch
Click to expand...
Click to collapse
I came from the vibrant as well however I wasn't so active there.
I don't understand why you don't see any zip files then. Strange.
Me either... think i'll just try and reload it and see what happens. Thought maybe i was clicking the wrong thing or not clicking something.
---------- Post added at 07:47 PM ---------- Previous post was at 07:43 PM ----------
and its not just that i dont see any zip files. i dont see ANY files at all! every directory i click is empty! even on the system partition! not a single file shows up. only directories and when i click them there is nothing except /.. and /.
Team Win Recovery Project 2.2, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG (for 2.2.0):
- On-screen keyboard in recovery! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
- Name new backups and rename existing backups
- Rename files and folders in the file manager
- Pseudo-terminal emulator
- Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
- Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
- Simplified XML layout support between resolutions
- Added dual storage selection radio buttons to zip install, backup, and restore pages
- Improved zip install compatibility
- Updated update-binary source code
- Numerous small bug fixes and improvements
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
ORIGINAL POST (from May):
This is a work in progress.
TWRP (Team Win Recovery Project) 2.1 by TeamWin is an alternative recovery (instead of ClockworkMod) that is a good companion for Goo Manager. See this video for more info.
This is an experimental, mostly untested build of TWRP2 for entertainment purposes only. USE OR ATTEMPT TO USE ENTIRELY AT YOUR OWN RISK. It is intended for those who are willing to risk any and all damage, loss, and STD infection to their hardware, data, person, and associates resulting from this software. Do not attempt to use unless you understand and accept these risks.
Please note this is using the still-being-developed 3.x kernel.
I am including the raw .imgs which can be fastbooted or used on an SD (rename recovery.img.sdcard to recovery.img and put on SD in place of the existing version). Which I don't recommend doing of course, given the disclaimer above. Remember I don't have an NT so I haven't run this... ever.
Finally, this has not at all been put through any kind of paces. That's for you, assuming all the risks, to do. And report it back here for everyone's benefit.
Thanks to dees_troy, eyeballer and demetris_I & frustro for testing this. I'm busy the next few days, so I'm volunteering demetris_I, who has it running, to answer anyone's questions per his availability
twrp-2.1-nt-2012-05-17E-fullofbugs.tar.gz
History
6/12/12 - updated first post.. No binaries yet.. Can someone make one?
5/17 -
Updated 3.0 kernel to support new 512GB NTs (untested)
Updated twrp codebase to latest
Newer cm9 stuff as well
5/17B&C
Use cmdline from u-boot.bin to determine max ram size.
fix device showing up as "B" to "NookTablet"
5/17D&E
I can't remember. But it's betterer.
Has anyone successfully flashed this yet? And can anyone offer up the steps in a more-in-depth way?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Well... there's always update.zip
I haven't tried it, but I'm guessing if you've installed fastboot to your computer, this should work:
1. boot into cyanoboot and choose Fastboot from the menu.
2. On your computer, navigate to where recovery.img is and enter into the terminal
fastboot flash recovery recovery.img
Or... maybe someone could whip up a quick update-twrp2-nt-2012-5-14.zip maybe?
I guess that someone might as well be me. This is intended for use with an existing cwm recovery. This will flash to emmc...maybe.
update-twrp-2.1-nt-2012-05-14-fullofbugs-emmc.zip
MD5: 337269fa77017150325d398216a6dd3c
Thoroughly and completely untested. I really don't know if it will even install, and if it does, if it will work. See all disclaimers above, plus make up some additional ones yourself.
Edit: See below about a possible issue with possible difficulties accessing the external SD card. Internal /emmc seems to work consistently. Looking into it, but if you want to help debug this, that would be much appreciated. Just knowing what works or doesn't work and log samples (dmesg via adb) would be great.
Will this completely replace CWM as the recovery? Or will it run alongside. Anything else I should be aware if before I try to flash (do it on a fresh rom install, will I be able to restore from a backup if something goes wrong etc etc...)
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
It will replace cwm.
Rom doesnt matter , they reside in different partitions.
Cyanoboot is all you want if anything goes wrong or/and CWM/TWRP from sd card so you can dd the recovery.
SilentStormer said:
Will this completely replace CWM as the recovery? Or will it run alongside. Anything else I should be aware if before I try to flash (do it on a fresh rom install, will I be able to restore from a backup if something goes wrong etc etc...)
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Click to expand...
Click to collapse
Should replace it completely. I say should because if you do this with the update.zip, you will be the first one to try it.
Oh, Mister_Argent is trying it on IRC...
The Zip seems to work! Android boots fine, and it's entirely possible to get into TWRP via Cyanoboot. This might just be me, but the terminal seems to lock up...
Oh hey argent, so the zip works? And is it worth my time to change from CWM to TWRP?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
SilentStormer said:
Oh hey argent, so the zip works? And is it worth my time to change from CWM to TWRP?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Click to expand...
Click to collapse
There may be issues with selecting the external SD card... not sure what the deal is. I believe demetris_I checked this out previously, but you can use the internal (/emmc) one though until this is worked out/confirmed one way or the other.
Note: if anyone is good at verifying/debugging, post any relavent dmesg stuff + what your theory is on the issue
So we can still flash stuff through emmc?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Indirect gave me this command to flash recovery via terminal emulator and it worked out nicely
dd if=/recovery.img of=/dev/block/mmcblk0p3
Click to expand...
Click to collapse
where "/recovery.img" is the file path/file name of the recovery image
Recovery looks nice. I'll do some more playing with it later when I have time.
fattire said:
There may be issues with selecting the external SD card... not sure what the deal is. I believe demetris_I checked this out previously, but you can use the internal (/emmc) one though until this is worked out/confirmed one way or the other.
Note: if anyone is good at verifying/debugging, post any relavent dmesg stuff + what your theory is on the issue
Click to expand...
Click to collapse
No issues with external sd it just take some seconds to mount, is not instant but it will mount.
8gb NT. Successfully flashed internally; will test, log and provide feedback on any issues.
The zip file name is overly long and CWM doesn't like it. Renaming to something shorter solves the issue.
In my experience with other android devices, it is normally recommended you wipe 'dalvik cache' whenever changing / updating kernel. Perhaps this step will avoid some issues for people.
Edit: Flashing gapps update via Goo Manager results in failure of rom to load after Cyanoboot screen. I did not choose to wipe dalvik / cache in Goo Manager. Also unable to access Cyanoboot via N. Screen appears but does not seem to respond and automatically boots emmc (blank screen).
Re-download Gapps and press the buttons combo to access twrp/cwm and reflash (power+N)
What rom and what gapps you are using?
Make sure they are downloaded ok before flashing.
demetris_I said:
Re-download Gapps and press the buttons combo to access twrp/cwm and reflash (power+N)
What rom and what gapps you are using?
Make sure they are downloaded ok before flashing.
Click to expand...
Click to collapse
I could not access twrp as already stated, because Cyanoboot did not respond to button press. I've managed to get access to CWM via sdcard and reflashed another gapps. CM9 still will not load.
Next, I plan to wipe everything and flash CM9 anew.
Edit: Still won't boot. Looks like I have a brick to fix.
Edit2: Flashing CWM internally got everything working again. Cyanoboot would previously go automatically to loading from emmc; there was no delay / opportunity to press N to access the menu. Now the delay occurs and I have access. CM9 also loads.
Edit3: Reflashed TWRP internally again. It's not working on 8gb NT. It doesn't break Cyanoboot or prevent CM9 from loading, but any attempt to load TWRP results in a black screen.
How do you flash twrp?
If you flash the zip can you please try the fastboot way?
fastboot flash recovery twrp.img, thanks
demetris_I said:
How do you flash twrp?
If you flash the zip can you please try the fastboot way?
fastboot flash recovery twrp.img, thanks
Click to expand...
Click to collapse
I flashed the above emmc zip via cwm internal
I have adb working, however fastboot seems to require a separate driver to work in windows. I've searched the forum and have not found a clear answer.
I'm guessing the 3.0 kernel doesn't have support added for the 8gb nts yet. I guess maybe I could look into that...
Sent from my HTC Vision using XDA
So to run this I have to be running the new 3.x kernel? Or can I just flash the zip if I'm on the 2.x Cm9
(16gb Tablet)
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
SilentStormer said:
So to run this I have to be running the new 3.x kernel? Or can I just flash the zip if I'm on the 2.x Cm9
(16gb Tablet)
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Click to expand...
Click to collapse
Recovery is separate from the rom. You'll be fine. I have it running on my 16GB.
Team Win Recovery Project 2.6, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. TeamWin started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of additional features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
HTC Droid Incredible 4G LTE product page on TeamW.in
Older versions can be found here if needed.
Download
Download TWRP 2.6.3.0 Official (Change Log)
MD5: 22c58a87402b4049f8bafa1b07b1a765
Download TWRP 2.6.3.0a Unofficial
MD5: fd9f7b520bec55c980d0ea39616aa271
Includes these commits on top of 2.6.3.0: Never generate empty backup name, Remove unneeded images, check for space after = too, Improvements to Update_Log_File, Fix checking for file_contexts in updater
GooManager Installation:
Automated installation through GooManager will only work if you have the su binary (root access) on your ROM. If you have just performed unlock or S-OFF, you must use the manual installation method for the first recovery installation.
Install the GooManager application from Google Play
Open GooManager, pull up the menu, and select Install OpenRecoveryScript
Confirm the first prompt, then verify the filename in the second prompt (openrecovery-twrp-2.6.3.0-fireball.img) and confirm again
After the recovery has been installed, pull up the menu and choose Reboot Recovery
Manual Installation:
Requirements: you must have fastboot set up: Windows Guide, Mac Guide, Ubuntu Guide
1) Reboot your phone to the bootloader:
Method 1: Disable fast boot under Settings > Power > Fast boot. Shut down the phone. Hold Volume-Down and Power simultaneously until the phone vibrates. Continue holding volume down, but release the power button. When you reach the bootloader, choose the FASTBOOT menu option using the volume keys to move up/down and the power key to select.
Method 2: If you have adb installed, then with your phone fully booted up, type: adb reboot-bootloader
2) Flash the recovery image using fastboot. Open a terminal and navigate to the directory with the downloaded image. Type:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-fireball.img
When the image has finished flashing (usually less than 10 seconds), issue the command
Code:
fastboot reboot-bootloader
3) Use the volume keys to navigate to BOOTLOADER and then select it with the power key. After the phone finishes scanning for PJ____.zip images, choose RECOVERY from the menu. This will start TWRP recovery.
Themes:
TWRP supports themes! Create a folder called theme within the TWRP folder on your internal storage and copy ui.zip into it. You can either search for themes compatible with the 540x960 resolution (check out the EVO 3D forum for instance) or build your own. Known themes listed below:
Holo TWRP Theme by prairiedogn
HTC TWRP Theme by prairiedogn
Blue Dalek Theme by agentc13
Sports Recovery Themes by lnando84
Gray Theme by lnando84
Themes written for earlier versions of TWRP may not have themed elements for new features. Be sure to compare the user interface before and after applying a theme to make sure everything shows up. You can check the log for errors as well (the middle button on the bottom of the TWRP interface), it will say something like: "unable to load button image" if resources are missing.
Additional Information:
The boot image comes from RUU 2.17.605.2
This build includes HTC Dumlock in case it is needed. S-OFF users can safely ignore it. HTCDev Unlock users (who are still S-ON) can try it out if experiencing trouble writing to the /boot partition. It can be found under Advanced in the recovery.
Credits:
Dees_Troy for adding the Inc 4G to TeamWin's officially supported devices for TWRP
con247 for putting in the original effort to build TWRP on the Inc 4G
utkanos and KemoNine for building assistance
TeamWin for TWRP and their great building guide
CyanogenMod for way too many reasons
Release History:
Official 2.6 - In addition to TWRP's official changes, this version also introduces support for AOSP data encryption. Additionally, Aroma installers should not fail anymore.
Official 2.4 - Builds are now maintained by TeamWin: Change Log
Official 2.3.3.0 - Identical to Build 1.2
Build 1.2 - Mount internal and external SD to computer via USB
Beta 1.1 - HTC Dumlock included
Beta 1.0 - Initial Release
Known issues / Workarounds / To Do
The charging status LED currently does not turn on when the phone is charging. This is really a non-issue since there is a charge level and charging indicator within the recovery.
If the phone is powered off while plugged into USB, it will temporarily reboot into recovery then shut down 20-30sec later.
Source
The device tree is at github.com/cyanogenmod/android_device_htc_fireball.
great, glad to see this coming
Do you think this could get goo manager support? Thanks for all that you do.
Sent from my DROID RAZR using Tapatalk 2
Awesome! Thanks updating now
jamminjon82 said:
Do you think this could get goo manager support? Thanks for all that you do.
Click to expand...
Click to collapse
I need successful user reports for all the features. Once I get confirmation that everything works as expected, I'll submit my device tree to TWRP and ask for official builds. Goo manager support would follow from there.
I updated the build to version 1.1. For those who are S-OFF, there's no difference from 1.0. For those who are S-ON and using HTCDev Unlock (from team fireballas), there's now HTC Dumlock included. I'm still not sure if it is even needed...
im running a backup now. i'll try wiping and restoring too
---------- Post added at 02:18 PM ---------- Previous post was at 01:37 PM ----------
Backup, wipe, and restore all work as well as backup compression and backup rename. Under wipe I didn't know about internal and android secure are those required for a full wipe?
Linch89 said:
im running a backup now. i'll try wiping and restoring too
---------- Post added at 02:18 PM ---------- Previous post was at 01:37 PM ----------
Backup, wipe, and restore all work as well as backup compression and backup rename. Under wipe I didn't know about internal and android secure are those required for a full wipe?
Click to expand...
Click to collapse
Relevant posts about androidsecure:
http://forum.xda-developers.com/showthread.php?t=1934739
http://forum.xda-developers.com/showpost.php?p=27172605&postcount=218
Internal wipe clears out your internal sdcard's media partition (pictures, music)... probably don't want to do that.
Good look glad I didn't. Well as far as I can tell this is recovery is a win pun intended
im trying to mount my phone to my computer while in recovery and its not working v2.3.3.0 idk if its my computers usb its certainly not my phones micro usb the thing is brand new
The ability to mount the phone's sdcards on the computer while in TWRP was unknown to me. I'm working on the issue. The attached recovery is a first stab at a fix, let me know if it works (my faith is low though since the devices didn't mount in ubuntu for me).
MD5: 6fa24210afa860c38fef3f2a7d4360d1
Edit: the attached recovery did not fix the issue. I'll try to look into this sometime this week (research presentations and job interviews over the next few weeks so time is very scarce right now).
Linch89 said:
im trying to mount my phone to my computer while in recovery and its not working v2.3.3.0 idk if its my computers usb its certainly not my phones micro usb the thing is brand new
Click to expand...
Click to collapse
Mine isn't mounting either, internal nor external card, but I can get it to work through ADB, (work around for the time being)
Interesting side note though, (and this may be expected by some, it was new to me) while in TWRP recovery and running shell though ADB it was listing my actual external SD card as "sdcard" and actual internal SD as "internal_sdcard". I have used CWM on another device and I don't remember it changing the file structure while in recovery. Also I had shell root upon issuing the adb shell command. This is my first device using TWRP, it was just different.
Edit: Never Mind, I am running TWRP v2.2.0, this may not have any validity with the OP's version, sorry.
Edit my Edit: OK I just flashed v2.3.3.0 and same goes, I can get in through ADB and I have shell root once in shell. However, the file system looks like it should with "sdcard" and internal and "external-sd" as external. All else seems normal.
DavDoc said:
Mine isn't mounting either, internal nor external card, but I can get it to work through ADB, (work around for the time being)
Click to expand...
Click to collapse
I worked on the sd card mounting issue last night, but still have not figured it out. I will try to get some assistance from the TWRP folks if I find time tonight. Just to make sure, the feature worked when you used TWRP 2.2 by con247?
In fact, I may be misinterpreting how the feature works. Is the computer supposed to auto-mount your SD card when plugged in via USB, or do you have to activate the feature from within TWRP somewhere?
DavDoc said:
Interesting side note though, (and this may be expected by some, it was new to me) while in TWRP recovery and running shell though ADB it was listing my actual external SD card as "sdcard" and actual internal SD as "internal_sdcard". I have used CWM on another device and I don't remember it changing the file structure while in recovery. Also I had shell root upon issuing the adb shell command. This is my first device using TWRP, it was just different.
Click to expand...
Click to collapse
I just tested and this is what I see:
Code:
drwxrwxrwx 11 root root 16384 Jan 1 1970 external_sd
drwxrwxrwx 11 root root 32768 Jan 1 1970 sdcard
EDIT: Both in TWRP and in 'adb shell' the locations are correct.
It doesn't auto mount upon connecting usb, I didn't try mounting it though, through TWRP settings. From what I can tell, both versions work the same, they just have different names for the file structure, and only for the external and internal sdcards - didn't really investigate any other files.
Edit: To answer your first question, no it didn't work in either version. Don't know who's v2.2.0 it is, but it is the recovery that was added into the supercid.auto script.
mdmower said:
I worked on the sd card mounting issue last night, but still have not figured it out. I will try to get some assistance from the TWRP folks if I find time tonight. Just to make sure, the feature worked when you used TWRP 2.2 by con247?
In fact, I may be misinterpreting how the feature works. Is the computer supposed to auto-mount your SD card when plugged in via USB, or do you have to activate the feature from within TWRP somewhere?
I just tested and this is what I see:
Code:
drwxrwxrwx 11 root root 16384 Jan 1 1970 external_sd
drwxrwxrwx 11 root root 32768 Jan 1 1970 sdcard
EDIT: Both in TWRP and in 'adb shell' the locations are correct.
Click to expand...
Click to collapse
i think they mean usb mounting is gone it is suposed to be under mount option
jose51197 said:
i think they mean usb mounting is gone it is suposed to be under mount option
Click to expand...
Click to collapse
Right, so if I just understood this a couple of days ago I could have had a fix pretty quick. I naively thought the phone was supposed to auto-mount to the computer, which would make no sense because the drives would then be inaccessible to TWRP's routines. Anyways, build 1.2 enables the feature and both internal and external SD cards can be accessed.
mdmower said:
Right, so if I just understood this a couple of days ago I could have had a fix pretty quick. I naively thought the phone was supposed to auto-mount to the computer, which would make no sense because the drives would then be inaccessible to TWRP's routines. Anyways, build 1.2 enables the feature and both internal and external SD cards can be accessed.
Click to expand...
Click to collapse
Its back thanks I wish I can thank you twice and don't want to complain but only thing missing is the backup android.secure option under backup
Sent from my ADR6410LVW using xda app-developers app
jose51197 said:
Its back thanks I wish I can thank you twice and don't want to complain but only thing missing is the backup android.secure option under backup
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
Does your .android_secure folder actually have anything in it? Mine is empty on Viper 2.1.1. I just moved an app to SD and the folder is still empty. The reason I ask is because the and-sec folder is correctly mounted and linked to /sdcard/.android_secure when in TWRP.
I've never seen anything in android secure ever on any phone
Linch89 said:
I've never seen anything in android secure ever on any phone
Click to expand...
Click to collapse
On my OG DInc running AOSP that folder would indeed store sdcard apps... strange its different now....
I moved all apps my apps to sd card and I checked android_secure under sdcard and sdcard2 in root explorer and nothings in there. I can't delete the folder though so it must be of some importance
I am currently on 4.1.2 10-20121209-UNOFFICAL-acclaim ROM
I want to move to CM 11.
My current recovery is CWM - Recovery v6.0.1.9
ON all CM 11 page , it says to update my recovery to new one through fastboot.
I am not sure how to do this on nook tablet. Can anyone help me ?
Also does repartitioning of 16Gb needs to done with each rom install or once done , it stays the same through out ?
naveen_reloaded said:
I am currently on 4.1.2 10-20121209-UNOFFICAL-acclaim ROM
I want to move to CM 11.
My current recovery is CWM - Recovery v6.0.1.9
ON all CM 11 page , it says to update my recovery to new one through fastboot.
I am not sure how to do this on nook tablet. Can anyone help me ?
Also does repartitioning of 16Gb needs to done with each rom install or once done , it stays the same through out ?
Click to expand...
Click to collapse
Hi, repartitioning doesnt need to be done with a new rom install.
IF THIS IS A CLEAN INSTALL
you dont HAVE to install it through flashing a new recovery using fastboot
you just need a working newer CWM , or a working TWRP that you can boot
if you can boot to an older Clockwordmod recovery in any form, you can flash a newer version of CWM to the internal by using a zip file , this user has a couple of the newest ones hosted here:
newbtrigger69 said:
https://www.mediafire.com/folder/3j4kxa3bwkrs1/CLOCKWORKMODS <--------------------------------------------- my compilation of a few important CWM versions in case u dont like twrp (like me).
Click to expand...
Click to collapse
after you flash the new recovery, remove the SDcard, power completely down,
press and hold the "N" NOOK button, and hold the power button for just a second or 2 after you see the tablet boot, and you should be prompted for the new recovery that you just flashed.
---
the newer recoveries have an option on the boot menu to start fastboot. So, if you really wanted to follow the instructions to the letter, get or make a working sd card of a newer CWM recovery, boot to it, then as long as your adb/utilities folder on your PC has fastboot in it, you can fastboot the recovery-0.2.img as is in the cm11 thread.
I found I never had to use fastboot before this cm11 install , so I didnt even have the fastboot on my pc side and had to hunt it down.
my first several installs of CM11 were done using an older boot sdcard that had TWRP recovery on it and it works fine.
----
it will probably be a lot easier it you have a working tablet, to have the copied the zips for cm11 and the gapps you want to install to the tablets
internal memory first, before flashing the new recovery internally
---------- (I completely forgot this other possibility, I'm always just doing clean installs)
IF YOU WANT CM to automatically upgrade though the CM updater process on a running CM10
then , yes you need the newer recovery, and it probably is best if it is the recovery-0.2.img the developer posted in the CM11 thread.
I've never tried it so I dont know how well it migrates your "stuff" from CM10 to CM11
theres a lot of changes to the way storage is mounted in CM11 , and the CM updating process is an important thing they are trying to make as seamless as possible.
If theres stuff on the tablet you really need, I'd save it first before doing any kind of major upgrade like this.
Thanks. I might do a clean install itself. I dont have much stuff.
Actually i am moving to CM 11 in hope that it would be faster. Currently i cant rad the PDF on thios tablet. The scrolling is very stuttery.. gives me headache. If that too doesnt solve that issue , i might simply sell this one and get some nexus tablet.
I just need a tablet to read my study books.
naveen_reloaded said:
Thanks. I might do a clean install itself. I dont have much stuff.
Actually i am moving to CM 11 in hope that it would be faster. Currently i cant rad the PDF on thios tablet. The scrolling is very stuttery.. gives me headache. If that too doesnt solve that issue , i might simply sell this one and get some nexus tablet.
I just need a tablet to read my study books.
Click to expand...
Click to collapse
the latest nightlies of CM11 on a 16GB tablet (has 1GB RAM) are fantastic. best thing ever, especially if you replace the kernel with one that user:demetris has supplied.
I havent run the CM11 on an 8GB (512MB RAM) tablet yet, but it really is a good package.
Its kinda like when Windows 7 came out, its what should have been released instead of XP or Windows 98, its really, really good.
Just tell me .. is flashing recovery via fastboot is same for all devices or for nook tablet its different. Also i need a SD card to do this ?
Can you help me how to flash recovery via fastboot for our nook tablet ?
naveen_reloaded said:
Just tell me .. is flashing recovery via fastboot is same for all devices or for nook tablet its different. Also i need a SD card to do this ?
Can you help me how to flash recovery via fastboot for our nook tablet ?
Click to expand...
Click to collapse
hmmm...
Ive seen fastboot on other devices, Kindle Fires, which I think have a motherboard thats a close match to the NOOK tablet.
on the Kindle, you can force fastboot by using a special cable.
if you need fastboot on the NOOK, the recovery program that you execute at boot has to have the option to start fastboot.
you can boot a recovery that has that option from an internal recovery (CWM newer versions have it, I dont remember about older versions)
or you can boot from an SD card you make that boots a CWM recovery
in any scenario, for fastboot to work, you need a working ADB setup and the fastboot program on your PC
------
you can completely install CM11 without replacing the internal recovery partition of your NOOK which is what that fastboot instruction is trying to get you to do.
the special internal recovery, as I understand it, is only for compatability with the automated CM updating process.
you can boot from an SD card that has CWM 6.0.4.x , or TWRP , and as long as the CM 11 nightly is on the SDcard too, or in the NOOK internal memory, you can flash it.
I am more confused
can you take me step by step or link me to a relevant thread ?
I am sorry if i am taking your time ..
naveen_reloaded said:
I am more confused
can you take me step by step or link me to a relevant thread ?
I am sorry if i am taking your time ..
Click to expand...
Click to collapse
--------- assuming you want to update your NOOK's INTERNAL software, and not run CM11 from an SDcard
I apologize had wrong file linked first post
this zip file should be flashable through your current CWM (6MB)
http://www.mediafire.com/download/0f5fjkjvxp1hga0/flashable_CWM_6.0.4.5(2).zip
http://forum.xda-developers.com/showpost.php?p=48855275&postcount=2
it should update your internal recovery to cwm 6.0.4.5
then you should be able to flash the CM11 nightly and gapps without error
--------------------------
a different (I think slightly more dangerous) way to load the newer recovey to your internal was posted here:
http://forum.xda-developers.com/showpost.php?p=48317620&postcount=15
get the newest recovery image file -
File: http://goo.im/devs/chrmhoffmann/cm-11.0/acclaim/recovery-0.2.img
md5sum: e2a87c433171b3d97d852d27aea1ff49
-------
You can install it from a terminal emulator, if you want to.
1. Download the cwm-recovery.img file referenced in the first post of the thread.
2. Copy this file to the internal memory of your Nook Tablet. Rename this file to cwm.img.
3. On your Nook Tablet, launch Android Terminal Emulator (ATE).
4. In ATE, type in 'su' [ENTER]. Grant it access when prompted.
5. In ATE, type in 'cd /emmc' [ENTER]. This will change your file system current directory to /emmc, which corresponds to the internal storage drive.
6. In ATE, type in 'ls' [ENTER]. This will list the contents of the /emmc directory. You should see the cwm.img file you copied over and renamed earlier (step 2).
7. In ATE, type in 'dd if=/emmc/cwm.img of=/dev/block/mmcblk0p3' [ENTER]. This will write the contents of the cwm.img file to partition 3 of device mmcblk0 (internal memory).
You should now be able to reboot and use cwm. CAREFUL, as you could brick your device if you get step 7 wrong.
nvm
@mikeataol
It worked perfectly. Just flashed it and it udpated to lastest CWM.
Installed CM 11 and got GApps and installed them too. Now downloading some PDF apps to see if they work smoothly and no stuttering is there.
In CM 11 , there is no option for "reboot to recovery" , why so ? I had to use cnyaboot option to enter into recovery.
naveen_reloaded said:
@mikeataol
It worked perfectly. Just flashed it and it udpated to lastest CWM.
Installed CM 11 and got GApps and installed them too. Now downloading some PDF apps to see if they work smoothly and no stuttering is there.
In CM 11 , there is no option for "reboot to recovery" , why so ? I had to use cnyaboot option to enter into recovery.
Click to expand...
Click to collapse
Great!
re: reboot recovery
you have to unlock developer options first by going into
Settings/ About Tablet / Build Number
and tapping the "build number" field 7 times.
then you see a new settings group "developer options",
and in there is advanced reboot and other things.
---------- Post added at 04:24 AM ---------- Previous post was at 04:21 AM ----------
are you on an 8GB / 512 MB ram, or a 16GB 1GB RAM Nook tablet?
Lol , just found that reboot to recovery , came here to say i found , you already replied.
Installing bexus kernel.
Thanks a lot for your help.
One thing though. The scroll stuttering issue is there . Its as if the screen refresh rate or frames per second is not upto the mark , scrolling is very stuttering.
Is there any way to increase or solve this issue ? Please
this is killing the whole tablet and the purpose i want to use this tablet .. ie to read books.
I use 16Gb/1GB tablet
ok ran into issue
After flashing gapps and installing kernel , i am stuck with andoid.phone stopped working error as soon as the tablet boots.
What is the gapps to be used for CM 11 on tablet and is bexus interfering with the gapps ?
how to enable multi touch ?
Also i think there is a serious problem with the screen/display. There is considerable lag and its not smooth scrolling. Its very stuttery...
naveen_reloaded said:
how to enable multi touch ?
Also i think there is a serious problem with the screen/display. There is considerable lag and its not smooth scrolling. Its very stuttery...
Click to expand...
Click to collapse
I would not enable the multi touch, thats just asking for even more trouble.
I think you should consider a total re wipe , and start over
on a 16GB Nook Tablet, the nightly just by itself should run fine
i just downloaded and opened a 71mb pdf file with no issues whatsoever
opens in Adobe reader just fine, scrolling and zooming and searching is perfectly acceptable, nothing I would describe as a stutter
----
if you HAD enabled the multi touch while you were on CM10, I'd consider reflashing the stock LCD firmware before you put CM11 back on it
yeah flashed thrice and i have witheld flashing bexus kernel for time being.
Stutter in the way , the refresh rate is not upto the mark
To best see this issue , dont swipe a text/pdf fast , do it slowly then you will see the jerkiness and also a lag between your swiping and actual screen change.
LCD firmware ? where to get it ?
naveen_reloaded said:
yeah flashed thrice and i have witheld flashing bexus kernel for time being.
Stutter in the way , the refresh rate is not upto the mark
To best see this issue , dont swipe a text/pdf fast , do it slowly then you will see the jerkiness and also a lag between your swiping and actual screen change.
LCD firmware ? where to get it ?
Click to expand...
Click to collapse
to me, seeing a white page while adobe pdf loads the next buffer of pages several pagesahead is normal
I dont see anything abnormal while swiping slowly
re: LCD firmware
if you were on CM10, and fashed the 10 point LCD firmware, then I think you would need to rebuild the unit back to CM10, and reflash the stock LCD firmware.
I dont know how to explain , but look carefully when scrolling (slowly) , you will see tests stuttering as its been scrolled .
I am on CM 11 , do you want me to go to CM 10 ? and flash that firmware?
https://play.google.com/store/apps/details?id=com.aatt.fpsm&hl=en
Used this app and saw that fps varies and it varies like from 7 - 50 during reading pdf.
On slow scrolling of pdf , it only shows 11 or so fps , which is why i think shows the stuttering effect
Used the same app on my GS3 to see the difference and it holds its FPS at 60+ and not dropping below 50.
I think if i can make this tablet to render everything at 30+ fps i might not feel this stuttering effect.
Which PDF reader are you using?
I don't have any stuttering issue on the Mantano Reader.
Hi
I own a 100% stock Samsung Galaxy S2 (GT-i9100).
The device is not rooted or modified and is currently running standard Samsung firmware.
Baseband I9100XXMS2
Kernel 3.0.31-1211311
Build numberJZ054K.I9100XWLSW
Android 4.1.2
Whilst I am not a power user I am tired of running out of system memory and having to move apps to the SD card. I am also tired of not being able to load certain apps due to the old Android version. I do want to connect to my car via Bluetooth (audio and internet etc).
It's time for a new operating system ... hence my visit to this web site. I have tried reading the guides but most use a lot of jargon and talk of multiple ROM options. I am a little lost and need some plain English instruction to follow since this is my first step into the ROM flashing world.
Which version should I install? Where do I download it from? What tools do I need for my PC? How do I do the flash?
Anyone out there who can help a complete novice?
Thanks in advance
Jacbjacb said:
Hi
I own a 100% stock Samsung Galaxy S2 (GT-i9100).
The device is not rooted or modified and is currently running standard Samsung firmware.
Baseband I9100XXMS2
Kernel 3.0.31-1211311
Build numberJZ054K.I9100XWLSW
Android 4.1.2
Whilst I am not a power user I am tired of running out of system memory and having to move apps to the SD card. I am also tired of not being able to load certain apps due to the old Android version. I do want to connect to my car via Bluetooth (audio and internet etc).
It's time for a new operating system ... hence my visit to this web site. I have tried reading the guides but most use a lot of jargon and talk of multiple ROM options. I am a little lost and need some plain English instruction to follow since this is my first step into the ROM flashing world.
Which version should I install? Where do I download it from? What tools do I need for my PC? How do I do the flash?
Anyone out there who can help a complete novice?
Thanks in advance
Click to expand...
Click to collapse
Mate, take it easy, i see you are a good English speaker, it should be very easy for you to understand the guides, for me it was hard and i bricked my phone multiple times, I'm not saying that I'm a geek or an android expert or something like that, but i know enough about my phone and i know what it's capable of and what it isn't, you should start easy step by step, and try following a video guide from YouTube like searching in google "i9100 root and custom recovery" and start reading some articles about it, believe me no one would just give you instructions on a silver plate, even if someone did, you will remain a noob who knows nothing about flashing and you won't be able to change your new rom or go back to stock rom..you should dig for it, there are guides that provide you with instructions and information about what you do..all you have to do is do a couple of google searches..
Anyway, all i can do to you is give you a link to this guide
Hope you understand the message
Regards Migo
Well I spent the entire afternoon and evening yesterday reading all I could about the flashing of the this Samsung Galaxy S2 GT-i9100. I then started to collect the files I think I will need:
Heimdall Suite: Inc' zadig.exe 2.0.0147, heimdall-frontend.exe 1.4.0, heimdall.exe
Lineage 14.1 Rom: cm-14.1-20161225-UNOFFICIAL-i9100.zip
Minimal_adb_fastboot_v1.4.2_setup.exe: Inc' adb.exe. cmd-here.exe, fastboot.exe etc
Odin3 v1.85.exe
open_gapps-arm-7.1-nano-20170225.zip
PIT Files: I9100_2GB-STOCK.pit (in case of problems) and I91001GB_6GB.pit
SAMSUNG USB Driver for Mobile Phones 1.5.27.0.exe
TWRP: twrp-3.0.2-1-i9100.img, recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100.zip,
On the phone I activated USB Debugging
I installed the USB drivers and the PC can see the phone
I ran Odin and the phone is seen
I tried to install TWRP using the instructions found here: https://twrp.me/devices/samsunggalaxys2i9100.html .... It didn't work!
I copied recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100.zip to the SD card, entered recovery mode and tried to apply the update from external storage. All seem to go well but then I got E:Error in tmp/sideload/package.zip (Status 7) ..... at the Top of the page it said Android System recovery (3e) ... I take it that is the system recovery currently installed on the phone. I found twrp-3.0.2-0-i9100.zip and tried that .... but got the same System 7 error!
So I have got nowhere really!
I know I have to repartition the drive using the PIT file
I know I have to load a custom recovery file using the TWRP
I then have to load the new ROM
But I don't know the order in which to do the operations .... TWRP first or PIT?
I don't seem to be alone in my fog ... see https://forum.xda-developers.com/ga...twrp-galaxy-s2-i9100-tried-t3539940?nocache=1
I have now realized that the various guides relate to the version of ROM they wish to install .... I am planning to use a Lineage 14.1 Rom. It seems that I can load it using TWRP or Odin.
I think the first step is to load TWRP ....... But I cant seem to be able to do that ..... Can Anyone help me install TWRP if that if the first priority?
Well I spent the entire afternoon and evening yesterday reading all I could about the flashing of the this Samsung Galaxy S2 GT-i9100. I then started to collect the files I think I will need:
Heimdall Suite: Inc' zadig.exe 2.0.0147, heimdall-frontend.exe 1.4.0, heimdall.exe
Lineage 14.1 Rom: cm-14.1-20161225-UNOFFICIAL-i9100.zip
Minimal_adb_fastboot_v1.4.2_setup.exe: Inc' adb.exe. cmd-here.exe, fastboot.exe etc
Odin3 v1.85.exe
open_gapps-arm-7.1-nano-20170225.zip
PIT Files: I9100_2GB-STOCK.pit (in case of problems) and I91001GB_6GB.pit
SAMSUNG USB Driver for Mobile Phones 1.5.27.0.exe
TWRP: twrp-3.0.2-1-i9100.img, recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100.zip,
On the phone I activated USB Debugging
I installed the USB drivers and the PC can see the phone
I ran Odin and the phone is seen
I tried to install TWRP using the instructions found here: https://twrp.me/devices/samsunggalaxys2i9100.html .... It didn't work!
I copied recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100.zip to the SD card, entered recovery mode and tried to apply the update from external storage. All seem to go well but then I got E:Error in tmp/sideload/package.zip (Status 7) ..... at the Top of the page it said Android System recovery (3e) ... I take it that is the system recovery currently installed on the phone. I found twrp-3.0.2-0-i9100.zip and tried that .... but got the same System 7 error!
So I have got nowhere really!
I know I have to repartition the drive using the PIT file
I know I have to load a custom recovery file - TWRP
I then have to load the new ROM
But I don't know the order in which to do the operations .... TWRP first or PIT?
I don't seem to be alone in my fog ... see https://forum.xda-developers.com/ga...twrp-galaxy-s2-i9100-tried-t3539940?nocache=1
I have now realized that the various guide relate to the version of ROM you wish to install .... I am planning to use a Lineage 14.1 Rom. It seems that I can load it using TWRP or Odin.
I think the first step is to load TWRP ....... But I cant seem to be able to do that ..... Can Anyone help?
Jacbjacb said:
I have now realized that the various guide relate to the version of ROM you wish to install .... I am planning to use a Lineage 14.1 Rom. It seems that I can load it using TWRP or Odin.
I think the first step is to load TWRP ....... But I cant seem to be able to do that ..... Can Anyone help?
Click to expand...
Click to collapse
The TWRP you are trying to install requires a kernel that supports isorec, so you must have that kernel first.
To have isorec support:
Note: -the rom and the isorec recovery and nogut rom and gapps -in short: all files- should be put in external sdcard because the internal sdcard will be wiped in the procedure.
1-you should install latest kernel-Lanchon-TRIM-IsoRec, you can easily flash it using a
Kitkat compatible recovery, flash the recovery using Odin along with a pit that has 1GB system or more,
1.5GB PIT Files by the.gangster or 1GB PIT Files by ELgmal 1GB is enough
2-after that, reboot to recovery:
• wipe data
• wipe cache
• navigate to "mount" and format system and format internal sdcard using (default)
• go back and navigate to "advanced" and wipe Dalvik cache.
• then go back and choose "install zip from sdcard1 (external sdcard)"
• and navigate to your kernel-Lanchon-TRIM-IsoRec and flash it.
• install arnab isorec recovery twrp zip by the gangster
• reboot your recovery, you will find the TWRP installed, now wipe system and data and cache and dalvik and install your nogut rom and the correct gapps.
that's it
Alternative Method
DON'T use odin to flash pit, just use it to flash the kitkat compatible recovery.
• flash Kitkat Compatible recovery with odin.
• in recovery flash kernel-Lanchon-TRIM-IsoRec and then flash twrp 3 isorec.
• and reboot recovery, then in TWRP 3 flash lanchon repit tool.
Lanchon repit tool is a simple flashable zip that can be edited to split the partition in desired way, read more about it in the official thread
This method was recommended by @TriboDoP
All credits goes to our great Developers.
MigoMujahid said:
The TWRP you are trying to install requires a kernel that supports isorec, so you must have that kernel first.
To have isorec support:
Note: -the rom and the isorec recovery and nogut rom and gapps -in short: all files- should be put in external sdcard because the internal sdcard will be wiped in the procedure-
1-you should install latest CM11, you can easily flash it using a
Kitkat compatible recovery, flash the recovery using Odin along with a pit that has 1GB system or more,
1.5GB PIT Files by the.gangster or 1GB PIT Files by ELgmal 1GB is enough
2-after that, reboot to recovery:
• wipe data
• wipe cache
• navigate to "mount" and format system and internal sdcard
• go back and navigate to "advanced" and wipe Dalvik cache.
• then go back and choose "install zip from sdcard1 (external sdcard)"
• and navigate to your cm11 rom and install the rom
• install arnab isorec recovery twrp zip by the gangster
• reboot your recovery, you will find the TWRP installed, now wipe system and data and cache and dalvik and install your nogut rom and the correct gapps.
that's it
Alternative Method
• flash Kitkat Compatible recovery with odin.
• in recovery flash cm11 with twrp 3 isorec.
• and reboot recovery, then in TWRP 3 flash lanchon repit tool.
Lanchon repit tool is a simple flashable zip that can be edited to split the partition in desired way, read more about it in the official thread
This method was recommended by @TriboDoP
All credits goes to our great Developers.
Click to expand...
Click to collapse
WOW IT WORKED! THANK YOU THANK YOU THANK YOU!
I used the following files:
SAMSUNG_USB_Driver_for_Mobile_Phones v1.5.51.0.exe
Lineage-11-20170115-UNOFFICIAL-i9100.zip … (CM11)
CWM-KitKatCompatible-i9100.tar
Odin3 v3.07
PIT Files: I91001GB_6GB.pit
Lineage 14.1 Rom: cm-14.1-20161225-UNOFFICIAL-i9100.zip
TWRP: twrp-3.0.2-1-i9100.img, recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100.zip
open_gapps-arm-7.1-nano-20170225.zip
All went well following the upgrade of SAMSUNG USB Driver for Mobile Phones 1.5.27.0.exe to SAMSUNG_USB_Driver_for_Mobile_Phones v1.5.51.0.exe. Odin 3 v3.07 had communication problems in download mode with the earlier drivers.
I followed your instructions to the letter (printed and ticked as I progressed) and only had one issue when it came to formatting the internal sdcard ….. I didn’t know what format so I selected “default” which worked.
I used a PIT file I had rather than your files simply because I didn’t know which one of your files to choose … too many options! I didn't fully appreciate the difference between them?
What can I say but Thank You …. This must be the simplest and BEST GUIDE out there for somebody going from a stock 4.1.2 to 7.1.1
One last question ..... how do I read my SD card (external) now that I have flashed my phone with 7.1.1?
Windows can see the SD card but wont let me read the contents. I have read https://www.reddit.com/r/Android/comments/3nnkaa/cant_access_android_device_internal_storage_from/ and put the phone into MTP for the USB.
Jacbjacb said:
One last question ..... how do I read my SD card (external) now that I have flashed my phone with 7.1.1?
Windows can see the SD card but wont let me read the contents. I have read https://www.reddit.com/r/Android/comments/3nnkaa/cant_access_android_device_internal_storage_from/ and put the phone into MTP for the USB.
Click to expand...
Click to collapse
It should work, I'm using AICP 12.1 (7.1.1) build 7 Feb, and it's working when i set it to MTP, but sometimes i have to change the cable, try changing the cable or use another USB port.
I installed AICP because official LineageOS 14.1 is buggy these days.
Thanks for the tip i forgot when formatting internal sdcard using default, i edited the guide and added it to my signature so every one can easily find it.
There are good talks about other nogut roms like crDroid and xenonHD, i would try them, but it would take time and i only have one s2 and it's my daily driver, so i couldn't, but many people recommended them.
I'm happy that i was able to help you, and thank you for telling me that my guide was easy, i was afraid that it might be complicated or something
Regards Migo
---------- Post added at 10:28 PM ---------- Previous post was at 10:22 PM ----------
Jacbjacb said:
One last question ..... how do I read my SD card (external) now that I have flashed my phone with 7.1.1?
Windows can see the SD card but wont let me read the contents. I have read https://www.reddit.com/r/Android/comments/3nnkaa/cant_access_android_device_internal_storage_from/ and put the phone into MTP for the USB.
Click to expand...
Click to collapse
Oh, you meant the external sdcard, have you mount it after the first boot, you must have got some notification about it.
If you didn't, navigate to storage in settings and choose the external sdcard and you will be asked to mount it as a "portable storage" or an "internal storage", choose "portable storage".
Jacbjacb said:
One last question ..... how do I read my SD card (external) now that I have flashed my phone with 7.1.1?
Windows can see the SD card but wont let me read the contents. I have read https://www.reddit.com/r/Android/comments/3nnkaa/cant_access_android_device_internal_storage_from/ and put the phone into MTP for the USB.
Click to expand...
Click to collapse
You can use recovery to transfer between computer and phone.(in case the rom fails to do that)