Related
..::Team Viper Official Sites::..
Team Vipers Official Site
Team Vipers Official Wiki
Team Vipers Official Ticket System
--------------------------------------------------------------------------------------------------------------
Rodderik's 1.2GHz Overclocked Kernel
Genocide_1.2GHzOC_EB13_Kernel_v0.2a.zip
Genocide_1.2GHzOC_EB13_Kernel_v0.2a.zip Mirror
Give Rodderik a thanks and buy him a beer, He paved the way for the Kernels with the first OC!!
--------------------------------------------------------------------------------------------------------------
..::Thanks::..
Thanks to ACS for the DK28 leak. Thanks to mysteryemotionz for some of the images.
--------------------------------------------------------------------------------------------------------------
..::Changelogs::..
ViperROM [TRiNiTY v2.0] EXT4-RFS DK28 Dual 4.0.4
Added New Theme
Added ViperWheelWidget - Custom Viper Widget
Added ViperPad - Custom Viper App Pad (Based of the Palm's SwipePad App)
Removed A Few Scripts Causing Issues
Returned The Artificial Intelligence Sounds
Added TTS Back Into The ROM
Google Nav Works Again
New Boot Animation
Governor Killer Baked In
AOSP Lockscreen Added
Added New App Icons
Moved Data/Tweaks To System/Bin/Tweaks
Optimized More For Speed & Battery
Changed Browser Start Page - Team Vipers Official Site
Added Wallpaper, Wifi Tether, And Launcher Pro To SDCard (VIPERaddons)
Modified Hosts File
Modified Build.prop
Modified Android.policy.jar
Modified MMS.apk
Themed Dialer
Modified SettingsProvider.apk To Always Allow 3rd Party Apps Install
Added ViperComm Widget
Modified A Lot Of Images
New Sounds
ViperROM [FRoZeN] EXT4-RFS DK28 Dual 4.0.3
New Theme
New Shutdown Animation
New Transition Animations
Removed Some Scripts
Added Data/Tweaks
Governor Killer Baked In
Added A Few New Scripts
Modified For Speed
Modified For Battery Life
New Boot Animation
Custom Sounds - By Team Viper
--------------------------------------------------------------------------------------------------------------
..::ROM Downloads::..
ViperROM [TRiNiTY v2.0] EXT4-RFS Dual DK28 4.0.4
ViperROM [FRoZeN] EXT4-RFS DK28 Dual 4.0.3
--------------------------------------------------------------------------------------------------------------
..::Videos::..
ViperROM 4.0.4 Benchmark Scores
ViperROM 4.0.4 Features
--------------------------------------------------------------------------------------------------------------
..::Screenshots::..
COMING SOON!
SDCARD Partitioning Tutorial.
I know that with EXT4, partitioning the sdcard can be a hassle. Here's a little workaround to help you get it partitioned the easiest way I know without having to mount systems and such in Terminal Emulator. This way makes you flash 2 seperate recoveries, but I would rather do this than the other methods which could take upwards of a half hour or even longer. I've seen people that were working on it for a couple hours. Without further adieu:
NOTE: If you are running RFS, just follow step 1. and you'll be done. If you are running EXT4, skip right to step 2. and follow from there.
1. If you are running RFS, then you do not need to follow any other steps. In the green CWM2.5.5 recovery, just go to "advanced" in recovery and choose the Partition option. It's going to give you two questions for sizes that you want. The first size is going to be the ext size. For this it will give you a few options, but I don't recommend choosing anything below 512. You will see all the options when they pop up, just choose what you feel most comfortable with. The next thing it's going to tell you to select is the swap size. I again don't recommend choosing anything below 128 for this option. You will again see a list of options, so choose what you feel most comfortable with.
2. If you are running EXT4, then follow these steps and you'll be up and running with your new partition very soon. First thing you need to do is gather all the tools you're going to need. Here are the list of tools you will need:
A. One Click Root & Recovery 2.5.5
B. One Click Root & Recovery 3.0.0.6
Quite the long list huh? lol ...I told you it's gonna be simple lol.
Download both of these files (if you don't have one or the other already) and extract them to an easy to find location on your computer somewhere.
3. Ok, you're going to do this just the same as you would if you were rooting your phone from a stock state. And to answer your question that's running through your head right now, No, this will not return you to RFS. You will still be on EXT4 the entire time, so there's not real need to backup your sdcard or worry about having to sit through the backup&restore again. Once again, to be very clear... Even though you are flashing cwm2.5.5 recovery, you will REMAIN EXT4. So let's continue. Make sure USB Debugging is on and plug your phone into your computer. Do NOT mount the sdcard, just have the phone plugged in. Open the One Click Root & Recovery 2.5.5, and run the program. When it's finished, your phone will reboot. Do NOT unplug it until the script is complete. The script will say "Operation Complete. Hit any button to continue" or something along those lines. Just hit a button and the script will automatically close. You can now reboot into recovery and you will see the 2.5.5 recovery with the green letters. If you don't have the green letters, then you didn't run the right One Click, and you should start over using the correct one lol . For those that successfully flashed the 2.5.5 recovery, move on to step 4.
4. If you have the green letters, then we'll continue, if not, repeat step 3. with the correct one click lol. Now that you have the green letters, revert to step 1. When you're finished following the same instructions from step 1, move on to step 5. If you have any issues with anything from step 1. (which you shouldn't, but if you do) click here to go to Mibbit's irc chat website. Along the top left side you will see 2 tabs labeled "Home" and "Connect". Make sure you are on the tab that says "Home". When on the tab labeled "Home", you will see the box in the middle of the page. Right beside the letters "IRC:" is a dropdown box. You're going to click on the dropdown arrow and select "EFNET". Next, you're going to enter your nickname, and finally, beside "channel:" type "#viper" and select "Go". That will bring you to Team Vipers chat where one of us will be able to help you.
5. Now that you are partitioned, it's time to restore the EXT4 recovery. If you do not restore the EXT4 recovery, you will not be able to flash any new ROM's or Kernels, so you MUST restore the correct recovery. To do so, you simply do the same steps. Make sure USB Debugging is turned on and plug your phone in. You do NOT need to mount. Now you simply run the 3.0.0.6 One Click Root & Recovery. Let it run through it's process and it will reboot itself. Do NOT exit out of the command prompt until it says "finished, press any key to continue". Once your phone reboots, you can then reboot into recovery and you will see that you have the orange letters again. When you see the orange letters, you now have a partitioned sdcard and you are back on the correct recovery.
**ONCE THE KERNEL IS RELEASED (Which should be within the next 24 hours as long as my testers don't see any issues) THEN MOVE ON TO STEP 6.**
6. Now that you're partitioned, the only thing left to do is flash the kernel. Connect your phone to your computer and copy the Kernel to your sdcard if you have not done so already. To flash it, just choose "Install zip from sdcard" followed by "Choose zip from sdcard" and simply navigate to where you stored it on your sdcard. That's all. It's quite quick and painless and you should be able to do it all within 10-15 minutes.
VIPERrom Store where everything is FREE!
**Cleaned up post 13 January**
**If you want mods and addons download viperstore from the market**
NOTE: stuff is still being ported to the new edify scripting required for clockworkmod 3.0.0.5 so if something doesn't work submit a ticket from our website and we will get it ported over as soon as we can. For now you can access the store's contents that have been converted here.
VIPERchat in your browser chat.efnet.org (enter your nickname and #viper for the channel name)
VIPERchat Downloadable Version VIPERchat.zip (3.38 MB)
Voice Apps were removed in 3.0.3 to save space but if you want them Voice Apps **UPDATED FOR NEW CLOCKWORK**
Stock Sprint Apps (install .apk like normal):
SprintDK28_Navigation.apk (5.6 MB)
SprintDK28_Nascar(updated).apk (385 KB)
SprintDK28_NFLMobile(updated).apk (510 KB)
SprintDK28_SprintTV.apk (879 KB)
SprintDK28_SprintTVWidget.apk (84 KB)
SprintDK28_SprintZone.apk (367 KB)
First to post on this thread besides u
But yea ill look into the link for you right now
if i find it ill give to u
Edit: Here is the link http://forum.xda-developers.com/showthread.php?t=724171
not sure if that will help will look for some more
Reserved.. always wanted to say that.
Nice and clean separate thread me like...
Do i sense a 3.0.1 update to be sweet! or is the current 3.0 this version?
Hi BT. Thanks for the great ROM. I am using 3.0 right now. What is the difference between 3.0 and 3.0.1? Thanks. Keep up the great work! And one quick question. When I try to install lagfix, everythiing works besides the last step, installing viperspeed. It says I cant install it because I dont have enough room. but I have 185MB free. any ideas?
Link? I hope it's not there or else I'll feel more jerky than usual. Oh and super-thanks for those file names on the battery mods, so important... I have a mess of files like GREENBATMODTHISTHAT with no versions or anything and I guess I didn't realize that I needed to keep mods organized by ROM.
azichek said:
Hi BT. Thanks for the great ROM. I am using 3.0 right now. What is the difference between 3.0 and 3.0.1? Thanks. Keep up the great work!
Click to expand...
Click to collapse
3.0.1 is just a new name for it so if we make updates there's less confusion... It's still the same as 3.0, but hopefully this will eliminate some questions in the thread lol.
3.0.1 = 3.0 ...No new updates yet.
BUT!!!
Rodderik did make the battery mods!, check them out!
azichek said:
Hi BT. Thanks for the great ROM. I am using 3.0 right now. What is the difference between 3.0 and 3.0.1? Thanks. Keep up the great work!
Click to expand...
Click to collapse
I think 3.0.1 is just the updated version of 3.0.
3.0.1 does have the aosp lock screen the 4g is fixed
and couple other things... At least that i think lol
Hope that helps
Added A2SD (Download Terminal Emulator, And type "start a2sd" followed by "launch a2sd" and it will back everything up on your sdcard)
Click to expand...
Click to collapse
Can you please clarify this for me, because I tried earlier and it gave an error when trying to install the terminal. Also I have used linux before but never used a terminal on a phone before lol...can you write down a few steps for us newbies
Again Thank you for your work and to your team
Hey BT there is a app called WidgerLocker Lockscreen which lets you put any widget/app i believe on you lock screen that might be helpful i think..
Just installed it and brought back the aosp lock screen might wanna check it out... Send me a pm of ur email so i can send u the apk cause its a paid app
Another quick question BT, what are the other options for in the lagfix? Are they for future upgrades or not necessary at all?
Hey BT I just want to thank you for all your hard work and your great rom. I hope this hasn't been answered but is it necessary to remove my original root before flashing any of your roms? I have flashed most all of them and I have not deleted it. I'm not having any problems with 3.0. Thank you....
hemi dart said:
Hey BT I just want to thank you for all your hard work and your great rom. I hope this hasn't been answered but is it necessary to remove my original root before flashing any of your roms? I have flashed most all of them and I have not deleted it. I'm not having any problems with 3.0. Thank you....
Click to expand...
Click to collapse
nope you don't have to...just wipe 3x, wipe cache 2x, and wipe dalvik cache ONCE and flash the rom then you are good to go (assuming you are using the correct modem and if not then flash it first with odin)
DAVenom said:
Hey BT there is a app called WidgerLocker Lockscreen which lets you put any widget/app i believe on you lock screen that might be helpful i think..
Just installed it and brought back the aosp lock screen might wanna check it out... Send me a pm of ur email so i can send u the apk cause its a paid app
Click to expand...
Click to collapse
Widget locker is good, I installed it and then moved it to system apps. Works perfectly
Sent from my frozen epic4g
neuton said:
Another quick question BT, what are the other options for in the lagfix? Are they for future upgrades or not necessary at all?
Click to expand...
Click to collapse
2.2 is for the vibrant, minfree is setting the phones task killer settings (I recommend doing this), restoring the boot animation gives you a new boot animation, you can set a schedule if you want, and of course all the uninstall options
Sent from my VIPERrom [TRiNiTY] DK28 3.0
BThomas22x said:
3.0.1 is just a new name for it so if we make updates there's less confusion... It's still the same as 3.0, but hopefully this will eliminate some questions in the thread lol.
3.0.1 = 3.0 ...No new updates yet.
BUT!!!
Rodderik did make the battery mods!, check them out!
Click to expand...
Click to collapse
Haha thanks for clearing that up. I also sent you a pm about a weird lag fix problem i'm having. Thanks BT. The ROM is great.
Rodderik said:
nope you don't have to...just wipe 3x, wipe cache 2x, and wipe dalvik cache ONCE and flash the rom then you are good to go (assuming you are using the correct modem and if not then flash it first with odin)
Click to expand...
Click to collapse
I have the correct modem and 3.0 is working great. I have tried most of the other roms and yours have been the best by far. I thank you guys for that.
When I restore data from cockwork it broke lagfix. Anywork around?
Sent from my SPH-D700 using XDA App
Bt, awsome work, wish I had you for a neighbor. Question, scince going to 3.0 my usb tether stopped working, is it not supported in 3.0 ?
maxdamage2122 said:
Since "official" nightlys have not been compiling for the g-tablet, I have been compoiling them myself on my personal computer. I'll compile the source every so often and upload it here https://www.dropbox.com/s/w3vhon1u5a2orsk/smb_a1002/kang?v=l. The time stamp in the file name (MMDDYYYY-HHMM) is the time that the repo sync was done.
In the meantime I'm setting up an old computer that I have as a buildbot to automatically compile every night for us. I'll let you guys know when I have it up and running.
Click to expand...
Click to collapse
I thought it might be nice to get a thread going for discussion on the CM7 port for harmony for our gtablet device. There are nightly builds which are starting to incorporate some great things such as video acceleration and the new google release of 2.3.4 could be around the corner. In fact some 2.3.4 code made it into nightly#60.
I am in no way associated with CM7. If someone from CM7 or someone in some way associated with CM7 wants to run this thread or create a similar one please do so.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Rule #1 of CyanogenMod: Don't ask about release dates.
CM7 Harmony Stable Releases
http://mirror.teamdouche.net/?device=harmony&type=stable
CM7 Harmony Nightly Releases
http://mirror.teamdouche.net/?device=harmony&type=nightly
Changelog
http://cm-nightlies.appspot.com/?device=harmony
Tablet Tweaks II (original TT is already incorporated)
http://forum.xda-developers.com/showthread.php?t=1002000
For firsties...
How-To Guide:
(slightly edited from Wiki http://wiki.cyanogenmod.com/index.php?title=Viewsonic_G_Tablet:_Full_Update_Guide)
Before you do anything — Make a backup
Don't forget to back up your data. If you have synced the device with a Google account, then the contacts, calendar, Gmail & select other Google-related data will not be lost and will come back after the next sync. However, you should backup anything you want to keep that is not stored on the SD card:
Bookmarks,
Applications; use Titanium Backup or the Astro File Manager, for example,
Any application data not on the SD card.
It would also be a good idea to backup everything stored on the SD card in the rare case the SD card must be formatted to resolve any major problems.
Backup for Root Users is a free application that can assist with backing up your data.
Installing ClockworkMod Recovery
For this guide, it is not necessary to root the Viewsonic G Tablet in order to flash CyanogenMod. You can simply install ClockworkMod Recovery & continue on.
Warning: Installing ClockworkMod Recovery on the Viewsonic G Tablet will void the warranty.
Download the ClockworkMod package: Download
Unzip the ClockworkMod package & copy the recovery folder & the update.zip to the root of the internal memory (NOT in any folders & NOT to the removable SD card).
Power off the Viewsonic G Tablet and reboot holding the Volume Up button and the Power button until the device is in the stock recovery.
While in the stock recovery, use the Volume buttons to navigate to the apply update.zip & press the Home button to select it.
Once the it the update.zip is applied the Viewsonic G Tablet will have ClockworkMod Recovery. Please continue to the next section.
Flashing CyanogenMod
*******************
adampdx said:
...according to this tweet we're not supposed to flash between the stable releases and the nightlies. ....
Click to expand...
Click to collapse
*******************
jerdog said:
Echoing the above -
DO NOT USE ROM MANAGER ON THE VIEWSONIC GTABLET!!!!! IT WILL BORK YOUR DEVICE 99% OF THE TIME. MAGIC VALUE MISMATCH AND OTHER ASSORTED ERRORS.
We've been dealing with these issues for months now - don't discount because you think you know better because you've used it on XYZ phone.
IT CAUSES ISSUES ON THE GTABLET. PLEASE EDIT YOUR OP TO REFLECT THIS. THERE ARE POSTS ALL OVER HERE DETAILING THIS. PLEASE ALSO POST A LINK TO BEKIT's CWM .8 - THAT IS THE ONE THAT WAS MODIFIED TO WORK WITH THE GTABLET GIVEN THE MULTIPLE QUALITY CONTROL ISSUES ASSOCIATED WITH THE PARTITIONS AND WHAT NOT.
Click to expand...
Click to collapse
Place the CyanogenMod update.zip file on the root of the SD card.
Optional: Place the Google Apps .zip on the root of the SD card also.
Boot into the ClockworkMod Recovery.
Once the device boots into the ClockworkMod Recovery, use the side volume buttons to move around, and either the power button or the trackball to select.
Select the option to Wipe data/factory reset.
Then select the option to Wipe cache partition.
Select Install zip from sdcard.
Select Choose zip from sdcard.
Select the CyanogenMod update.zip.
Optional: Install the Google Apps by performing steps 7 - 9 again and choosing the Google Apps update.zip.
Once the installation has finished, select +++++Go Back+++++ to get back to the main menu, and select the Reboot system now option. The Viewsonic G Tablet should now boot into CyanogenMod.
Having issues with finding your Internal Storage?
Check your fstab. CM has a different paradigm. See below from maxdamage2122
maxdamage2122 said:
This is a flashable zip file that I have created to backup the vold.fstab file and replace it with one that mounts the internal storage as /sdcard.
http://goo.gl/DS8u9
Click to expand...
Click to collapse
Edit: Thanks and props to the CM team and all involved. No thanks to me, I am just a copy/past whore.
Edit: Removed RomManager Method (thanks badfrog and jerdog)
Edit: Added reference to fstab mod. Thanks maxdamages 2122
Do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
Great job Oozura. Make sure Mad-Murdoch links this thread in his post in the nook forum. I had volunteered to do the same but he didn't get back to me. I'm a long time CM nightlies user on Droid, and now on GTab as well. I'll post as much as I can here.
And that bad frog is right. Use bekit's 0.8 GTab recovery and forget about Rom Manager. You'll just end up having to nvflash...
Thanks!
MC
thebadfrog said:
Do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
Click to expand...
Click to collapse
Are you sure about this? If so I dont mind editing that part of the CM instructions.
Echoing the above -
DO NOT USE ROM MANAGER ON THE VIEWSONIC GTABLET!!!!! IT WILL BORK YOUR DEVICE 99% OF THE TIME. MAGIC VALUE MISMATCH AND OTHER ASSORTED ERRORS.
We've been dealing with these issues for months now - don't discount because you think you know better because you've used it on XYZ phone.
IT CAUSES ISSUES ON THE GTABLET. PLEASE EDIT YOUR OP TO REFLECT THIS. THERE ARE POSTS ALL OVER HERE DETAILING THIS. PLEASE ALSO POST A LINK TO BEKIT's CWM .8 - THAT IS THE ONE THAT WAS MODIFIED TO WORK WITH THE GTABLET GIVEN THE MULTIPLE QUALITY CONTROL ISSUES ASSOCIATED WITH THE PARTITIONS AND WHAT NOT.
Search for the endless threads on hard bricked and soft bricked tabs from using rom manager on the gtab. And before all you fanbois jump in and tell me you had no problems understand this....there are at least 2 different partitioning setups on the Gtab from the factory. Sometimes you can't even boot after flashing Gingerbread roms without nvflash.
MicroChip said:
Great job Oozura. Make sure Mad-Murdoch links this thread in his post in the nook forum. I had volunteered to do the same but he didn't get back to me. I'm a long time CM nightlies user on Droid, and now on GTab as well. I'll post as much as I can here.
Thanks!
MC
Click to expand...
Click to collapse
Been a long time droid, dInc user. I had sent you a PM about half way through the OP but decided what the heck. I hope this helps keeps discussion in one place for our gtab and CM7 (soon to be 7.1)
Oozura said:
Are you sure about this? If so I dont mind editing that part of the CM instructions.
Click to expand...
Click to collapse
Yes, I'm sure he is sure about this. Do NOT use Rom Manager to install any of the roms or to update CWM. Only use bekit 0.8 recovery.
I don't even install Rom Manager on my Gtab.
thebadfrog said:
Search for the endless threads on hard bricked and soft bricked tabs from using rom manager on the gtab. And before all you fanbois jump in and tell me you had no problems understand this....there are at least 2 different partitioning setups on the Gtab from the factory. Sometimes you can't even boot after flashing Gingerbread roms without nvflash.
Click to expand...
Click to collapse
Sounds good to me. I will take it out. As long as the other method works then no need to make anyone cry over a bricked tab.
+10000 I learned this the hard way on day one.
Sent from my CM7 GTablet
Oozura said:
Sounds good to me. I will take it out. As long as the other method works then no need to make anyone cry over a bricked tab.
Click to expand...
Click to collapse
Please - don't just take it out - add a warning about it. And provide the link to the known working CWM (Bekit .8).
RomManager method removed
OP Edited. Thanks.
jerdog said:
Please - don't just take it out - add a warning about it. And provide the link to the known working CWM (Bekit .8).
Click to expand...
Click to collapse
I quoted your post. Link was already there to correct version in the clockwork mod package. thanks.
Thank you. There is something flakey about these devices and they don'y like Rom Manager
So who is using the latest nightly? I'm running 60 and seems stable. I occasionally get a stall on browser apps after a long sleep. But can't find any other issues.
Sent from my ADR6300 using Tapatalk
Oozura said:
So who is using the latest nightly? I'm running 60 and seems stable. I occasionally get a stall on browser apps after a long sleep. But can't find any other issues.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
I am. No issues to report, camera is still grainy. Video playback is still great.
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
Hardware Decoding?
So I installed AOSP the other day (the one in the Dev forum) because it was claiming hardware acceleration. It loaded up and was super laggy, but also didn't play the same video files that Vegan 5 played. I loaded up CM7 today and found the same thing. It's not nearly as laggy as the AOSP build, but still does not play video. I get volume, but no sound. Am I mistaken is thinking that we in fact have hardware acceleration now?
adampdx said:
So I installed AOSP the other day (the one in the Dev forum) because it was claiming hardware acceleration. It loaded up and was super laggy, but also didn't play the same video files that Vegan 5 played. I loaded up CM7 today and found the same thing. It's not nearly as laggy as the AOSP build, but still does not play video. I get volume, but no sound. Am I mistaken is thinking that we in fact have hardware acceleration now?
Click to expand...
Click to collapse
Progress is being made but we aren't there yet. Did you try mobo player? Engage software decoding and you'll be good to go.
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
I've been using RockPlayer and havent had any issues. Most notably for me though was YouTube HD videos now play with no lag.
I think Irs421 is right. Its progress but not complete hardware acceleration until Nvidia releases GB drivers I would guess.
I figured as much. Progress, even slow progress, is good. I'm liking CM7 so far any how.
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.2.0 compared to 2.2.0.0):
Mostly bugfixes:
Significantly improved sd-ext handling (ext partitions on sdcards)
Changes to kinetic scrolling in file selectors
Fixed a problem with using periods in backup names
Fixed problems in XML layouts with mounting system and USB storage
Fixed a problem with unmounting a partition before formatting during restore
Add Jelly Bean decrypt support
Updated 320x480 theme to match others (thanks to Llewelyn)
Improve "symlinking" of /data/media to either /sdcard or /emmc
Added sanitizing of device IDs for invalid characters (thanks to bigbiff)
Fixed free space calculation when switching backup devices on /data/media devices
Fixed a problem with using OpenRecoveryScript to create a backup without providing a backup name
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!
NOTE: If you're coming from another build of TWRP, you may need to go into settings and tap reset defaults to reset the storage paths so that you can see your zip files.
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.
thank you for this, ill test asap
if anyone wants a flashable zip, lemme know. i already have it done
edit: works good. only thing is i was flashing a rom (attempting to anyway) and somehow my zip got corrupted and unreadable. never had that happen before. any thoughts? (it was fine when i put it on my sd card, was flashing a 2nd time, so zip had worked previously and all other files on my sd are fine)
Going to flash this now and give it a try. Hopefully it works out good.
whoshotjr2006 said:
if anyone wants a flashable zip, lemme know. i already have it done
Click to expand...
Click to collapse
Throw it up brother!
thanks, always wanted a touch recovery and this one is great, if i could make a recovery touch it would be like this one again thanks
I flashed this a week or two ago and been working awesome! I love it.
i have been using cw recovery all time and always wanted to have a touch screen recovery and this one is sick, my only thing i have found is when i go to restore a backup it cannot find it,(one from cwm recovert). is it that it just cant restore those or did i miss something? no big deal to me ,just wanted to put it out there.
again thanks for this
they are in different folders on the SDCARD, im not even sure they are compatible.
ok cool im trying to do differant things and ill update you either way
would you know off hand where twrp folder would be? im looking if i get it before a reply ill post it
i got it twrp folder
alsp cani get the twrp 2220 in a zip format?
will this recovery work with firerats? on heroc?
dankdank11 said:
will this recovery work with firerats? on heroc?
Click to expand...
Click to collapse
Yes, Firerats has nothing to do with the recovery. Firerats just resizes your data/system/cache portion of the system really so you can install more apps.
I am using it and love it and works awesome on my Hero. :good:
thanks im trying it now, love the use of touch
I am going to leave the automated GooManager install for the Hero on version 2.2.2.0 due to the age of the device and the problems with recovery API 3 and older zips. TWRP 2.3.0.0 does work fine on the HeroC but I'm willing to bet that most zips are using old update binaries that will not install on the new version. If anyone wants to try, you're welcome to download and flash the newer versions manually:
http://techerrata.com/browse/twrp2/heroc
I was going to give 2.3.0.0 a try but like you stated, and someone in IRC said, that most of the zips online for the old Hero are prob all older so going to stick with 2.2.0.0 I think. Thanks for the update though.
Does TWRP require any particular hboot version, or will it function with any of them? I know you need to be on Android 2.3 in order to install TWRP, but I'm wondering... does it also mean that if you flash back to a stock ROM that TWRP won't work properly?
EDIT: My question was obviously stated with some knowledge missing. Recovery is obviously not dependent upon the ROM, as the ROM is loaded after the recovery program is done! But... I'm curious to know, if I made a nandroid backup with TWRP 2.2.2.0, will TWRP2 be able to restore it?
* DELETE *
There has been a small oversight with the GooManager route of distribution and the original post for this particular phone. You must have a PC or have a phone that can flash .zips or has a 2.3 or up ROM installed so it can run GooManager, even though this phones last OTA was Android 2.1, so it probably should have a .zip posted instead.
For example, I have a stock but rooted HTC Hero from Sprint as my backup with the latest OTA. So I can't use this method of install for this recovery without flashing a different recovery first, and then either flashing it as a .zip or upgrading my ROM to a 2.2 or 2.3 based ROM. In reality, I think most will just stick with whatever recovery must be flashed first in this situation as I will, even though I wanted TWRP. That said I think most of the users that use this will just want a .zip.
But there is no .zip posted for the guys that can flash it. This also makes it an overly cumbersome option if the handset is in stock state. As I said, I probably won't bother re-flashing, I kind of like sticking to one recovery on a phone and prefer to do minimal NAND writes.
DizturbedOne said:
There has been a small oversight with the GooManager route of distribution and the original post for this particular phone. You must have a PC or have a phone that can flash .zips or has a 2.3 or up ROM installed so it can run GooManager, even though this phones last OTA was Android 2.1, so it probably should have a .zip posted instead.
That said I think most of the users that use this will just want a .zip.
But there is no .zip posted for the guys that can flash it. This also makes it an overly cumbersome option if the handset is in stock state. As I said, I probably won't bother re-flashing, I kind of like sticking to one recovery on a phone and prefer to do minimal NAND writes.
Click to expand...
Click to collapse
As stated a couple of posts before you:
Dees_Troy said:
I am going to leave the automated GooManager install for the Hero on version 2.2.2.0 due to the age of the device and the problems with recovery API 3 and older zips. TWRP 2.3.0.0 does work fine on the HeroC but I'm willing to bet that most zips are using old update binaries that will not install on the new version. If anyone wants to try, you're welcome to download and flash the newer versions manually:
http://techerrata.com/browse/twrp2/heroc
Click to expand...
Click to collapse
Sent from my SCH-I535 using xda app-developers app
Hippie459MN said:
Yes, Firerats has nothing to do with the recovery. Firerats just resizes your data/system/cache portion of the system really so you can install more apps.
I am using it and love it and works awesome on my Hero. :good:
Click to expand...
Click to collapse
That's good to know. I think I'll give it a shot.
The reason for this User Thread is so that we can keep the development thread clean. Post in the development thread only if you have something useful to contribute such as a logcat, or any dev-related comments. Post any suggestions, bug reports, questions or comments about the rom in this thread,
What's working and what's not?
Working:
Camera - Yes, this means Camcorder also works! 1080P Video shooting and playback work great.
Bluetooth
WiFi
Audio
SD Card Storage
Battery Meter
And of course Hardware Acceleration!
Not Working:
RIL (Mobile Network) - This means no calls, no SMS, no Data, no anything related to the functions of your SIM Card! T-Mobile WiFi Calling also doesn't work.
Information On Dual Booting Roms
Since we currently have an issue with the network radio on our CM10 roms, most people will not be able to use this rom as a daily driver, and would prefer to stay on a fully functioning GB rom. This dual booting method lets us have the best of both worlds! You can have a buttery smooth and fast CM10 rom for enjoying all of Android Jellybean 4.2.1 goodies and a fully function Gingerbread rom when ever you need to make a call and such. For now, this is the best we can do. It's simple and very fast to switch between roms. What else could you ask for? ;D
Installation Instructions Including Dual Booting
DISCLAIMER
I (WE) AM NOT RESPONSIBLE of any damages to your device related to the use of this ROM or the dualboot toolkit. You do this at your own risk. Even though this has been tested and works well, using NVFLASH may brick your device if done incorrectly.
This ROM comes in two flavours: The dualboot toolkit or the Original flashable ROM
Dualboot ROM Instructions
WARNING! NVFLASH will format EVERYTHING, including internalSD. Make sure you backup your important files on your externalSD card
PART 1 - Resizing system partition
1) Unzip the dualboot toolkit and unzip NVFLASH_Resizer-G2X.zip.
2) Power off your phone and remove the battery. Keep vol. up and vol. down held and plug the phone via USB to a WINDOWS computer.
3) Windows should add an "APX driver". Go to control panel -> Device manager and right click on it -> Update driver -> search in system. Then, browse to the drivers folder inside the NVFLASH package and choose nvidiausb.inf. Approve any error messages (Windows 8 users read my FAQ). Install the Nvidia Fastboot driver.
4) Unplug your phone and hold down vol.up and vol.down. Replug it again and double click on flash.bat inside the NVFLASH folder. KEEP BOTH BUTTONS HELD DOWN DURING THE WHOLE PROCESS!.
5) When NVFLASH is done, unplug the phone and put back the battery. Reboot into recovery with power + vol. down. Plug it back and go to mounts and storage -> mount USB storage. If your PC asks to format the internal SD card, select yes.
PART 2 - Installing ROMS
1) Download the desired "call/SMS" ROM and extract boot.img from it's flashable zip. Rename it to boot1.img. Extract Step3_bootimg.zip from the dualboot toolkit and copy-paste boot1.img into system/boot, replacing the file that is already there. Repack Step3_bootimg.zip.
2) Copy-paste your desired ROM into the 0dualboot folder and send it to your device SDcard with everything it contains (your device should already be in the "mount USB storage" menu).
3) From the recovery, flash Step1_enabler.zip. When the screen goes black, hold power + vol. down to get back into recovery.
4) Flash your desired ROM, then Step2_ROM1.zip. Reboot to the OS.
5) You should have a Systemchanger app. Open it, click on "Switching" and give root permissions. When the screen goes black (again...), hold power + vol. down to get into recovery.
6) Flash ROM2.zip and Step3_Bootimg.zip and reboot in the OS
And there you go! To switch from one OS to another, just open the systemchanger app and click on "switching"!
Credits to bihariel for the original method. See the original thread here.
Original flashable zip ROM instructions
1) Boot into recovery with power + vol. down
2) Wipe data/cache, then mounts and storage -> format system
3) Flash this ROM
4) Advanced -> Wipe dalvik cache and fix permissions
5) Reboot and enjoy!
Special trick : In settings, go to About phone and click 6 times on Build number. This will pop up the developer and performances options. In performances options, CPU settings, change the governor from INTERACTIVE to SMARTASSV2.
Downloads
ROM with DUALBOOT Toolkit ***BETA***
DOWNLOAD HERE!
Original flashable ZIP (For single boot)
DOWNLOAD HERE!
Credits
See Mazout360s original thread here for the full list!
Thanks to bihariel for the original method for the Optimus 2X which I adapted for the P999. Great job!
Special thanks to Core Memory for helping me start this project[/CENTER][/QUOTE]
*All Information On this User Thread is from Mazout360s Thread in the Dev forums. Credits go to him for the Instructions/Downloads/Etc.
Quick template for now.. I'll update it as soon as I can.
Mazout Kernel on Stock 2.3.4
I flashed Mazout360's GB kernel over kwes' rooted 2.3.4/March 2012 basebannd. Was running pretty smooth, but had some problems
> Bluetooth icon at top of screen did not turn off "connected" status when I turned off my headset (BlueAnt q2.1)
> Had a few freezes. Installed SetCPU to keep max speed at 1015MHz but still some stops. Some out of nowhere, some in the middlle of doing stuff
> Finally started shutting down often. Tried to get a terminal emulator from the Market, but Market started crashing, even after several reboots. Could not get a kmsg to send.
Reinstalled my nandroid. No time at the moment to play more, need my phone reliable for some days to come. Hope lots of people try this kernel out and that I get more time with it. Nice to have new Dev activity for the G2x.
Quick question, i was wondering if it matters what zip tool we are using? Can i use 7zip for this, or should i use winzip?
Sent from my Mazout driven Reborn Hellbird.
grantusmantus said:
Quick question, i was wondering if it matters what zip tool we are using? Can i use 7zip for this, or should i use winzip?
Sent from my Mazout driven Reborn Hellbird.
Click to expand...
Click to collapse
Shouldn't matter, but I always use Winrar.
Micro SD card not detected
I was following along the steps and everything was going well until step 5 in part 1. when i rebooted my phone into recovery and pulged it into the PC nothing happened even though i followed exactly what the steps say, then i continued on and everything was going well until the end, where i found out that i couldn't get the data that I backed up to my Micro SD card because the phone doesn't see it.
Please help, I'm a noob around here.
I appreciate all the great work
did this project die?
reeshmd23 said:
did this project die?
Click to expand...
Click to collapse
No it didn't. My build computer broke and I need to setup a new HDD with my build environment. I'll make a new version as soon as possible.
hello,
I have dualboot now with hellfire2.4.2 and cm10 mazout's. So one is cm 7 and the other one is cm 10, I want to flash kernel but how? If I flash cm7 kernel will it block the cm10 rom or vice-versa?
guys I have just realized that I do not have dualboot after that steps
5) You should have a Systemchanger app. Open it, click on "Switching" and give root permissions. When the screen goes black (again...), hold power + vol. down to get into recovery.
6) Flash ROM2.zip and Step3_Bootimg.zip and reboot in the OS
I had systemchanger app and clicked on switching after that I flashed mazout's rom then when I open app drawer in cm10 rom, I noticed that I do not have systemchanger app anymore nor camera app.?? what should I do? If I do all steps all over again sould it be working ?
0b095 said:
hello,
I have dualboot now with hellfire2.4.2 and cm10 mazout's. So one is cm 7 and the other one is cm 10, I want to flash kernel but how? If I flash cm7 kernel will it block the cm10 rom or vice-versa?
guys I have just realized that I do not have dualboot after that steps
5) You should have a Systemchanger app. Open it, click on "Switching" and give root permissions. When the screen goes black (again...), hold power + vol. down to get into recovery.
6) Flash ROM2.zip and Step3_Bootimg.zip and reboot in the OS
I had systemchanger app and clicked on switching after that I flashed mazout's rom then when I open app drawer in cm10 rom, I noticed that I do not have systemchanger app anymore nor camera app.?? what should I do? If I do all steps all over again sould it be working ?
Click to expand...
Click to collapse
If you flash another ROM, you have to flash the corresponding stepX....zip file right after before rebooting, else you won't have the dualboot app.
Since android 4.2.2 just got out, I'll wait until it gets stable and make my upcoming build out of it For now, my phone battery doesn't work very well so I can't really test anything until I get a new one.
Hey. I got everything to work and am dualbooting nicely. My problem is kernel. I flashed a recent CM7 with this and everything went fine. Then I went to install the most recent CM7 kernel from Maz (the OC) and that works until I switch to Rom2 and back. Then the wifi gets an error and wont do anything. The kernel wont stick. Did I miss something?
Also, last night went to bed with my phone charging and when I woke up my phone was burning hot. Had Max OC at 1100.
Thanks! Works great having a taste of 4.2.1 and a phone!
Sent from my LG-P999 using xda app-developers app
Mazout360 said:
If you flash another ROM, you have to flash the corresponding stepX....zip file right after before rebooting, else you won't have the dualboot app.
Since android 4.2.2 just got out, I'll wait until it gets stable and make my upcoming build out of it For now, my phone battery doesn't work very well so I can't really test anything until I get a new one.
Click to expand...
Click to collapse
thank you, I see the problem now, and two question more; do I have to redo PART 1 - Resizing system partition everytime when I install different rom combinations or reinstall same roms and does that Resizing system partition harmful/useless or slows down the phone IF I only use 1 ROM?
I'm considering the dual boot, but want to know if it's possible to go back to single boot if/[hopefully] when radio is fixed. I suppose it'll be a matter of using original nvflash and format to have only one partition?
*edit1* Ok, now I'm getting my toes wet with this. fastboot.bin...what am I doing with this? The instructions say "install NVidia fast boot." Ok, but how? Or, has it already been installed with APX? I'm confused.
*edit2* ok I have dual boot! Wow this is interesting. Been running it through different combinations of reboots through system changer, and it seems when I update gb to the latest mazkrnl it won't stick after switching to jb and back again.
Do I need to use the boot.img from the kernel and repack it into step3?
Sent from my LG-P999
Oh shoots. Somewhere along the line I managed to break the wifi
MAC address comes up as unavailable in jb, just says error whenever I try to turn it on in gb. I'm thinking start the process over?
Sent from my LG-P999
adamiscool said:
Oh shoots. Somewhere along the line I managed to break the wifi
MAC address comes up as unavailable in jb, just says error whenever I try to turn it on in gb. I'm thinking start the process over?
Sent from my LG-P999
Click to expand...
Click to collapse
You need to flash a kernel. I am having the same problem, but flashing a kernel after switching back to GB fixes everything.
Edit: fyi I use maz's latest kernel 0205OC
Sent from my LG-P999 using xda app-developers app
Freakthis08 said:
You need to flash a kernel. I am having the same problem, but flashing a kernel after switching back to GB fixes everything
Click to expand...
Click to collapse
So, you mean that after using system switcher app, do power+vol up and flash kernel? Because any time I've tried that it only works on the first instance when i boot into gb. Once i go to jb and back again, the kernel goes back to stock. I'll try again though. Maybe fix permissions too!
Sent from my LG-P999 using xda app-developers app
adamiscool said:
So, you mean that after using system switcher app, do power+vol up and flash kernel? Because any time I've tried that it only works on the first instance when i boot into gb. Once i go to jb and back again, the kernel goes back to stock. I'll try again though. Maybe fix permissions too!
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
When you system switch back to GB, reboot back into recovery and flash a kernel. I wouldn't say it goes back to stock because if it did there wouldn't be a wifi error like that. But for some reason JB works fine nothing wrong I have seen yet, though I just noticed I don't have a camera/gallery.
After switching back and forth so much I just flash the kernel and don't do anything else because nothing has seemingly changed if I wipe anything or fix anything.
If Maz has answer for this I would be much appreciated or anyone else for that matter.
Sent from my LG-P999 using xda app-developers app
Edit: figured it out. A new boot1.img does need to get made with the new kernel already installed.
I created a new boot.img per the instructions on the original dual boot for p990 thread with maz kernel. Then I repacked step3_bootimg. Reflashed rom2 and the step3, then voila! So, you have to redo a couple steps if you want to update one rom's kernel.
Pic no longer related.
guys im having some trouble, when i go to the systemchanger app and grant permission instead of the screen going blank it gets stuck on a screen with two lg logos.
i think i havent installed the fastboot drivers correctly. i assumed it gets installed when i run flash.bat, but it may need to be installed seperately. if it needs to be installed how do i do it cause its just a .bin file and i have no idea what to do with it
---------- Post added at 10:20 PM ---------- Previous post was at 10:15 PM ----------
adamiscool said:
I'm considering the dual boot, but want to know if it's possible to go back to single boot if/[hopefully] when radio is fixed. I suppose it'll be a matter of using original nvflash and format to have only one partition?
*edit1* Ok, now I'm getting my toes wet with this. fastboot.bin...what am I doing with this? The instructions say "install NVidia fast boot." Ok, but how? Or, has it already been installed with APX? I'm confused.
*edit2* ok I have dual boot! Wow this is interesting. Been running it through different combinations of reboots through system changer, and it seems when I update gb to the latest mazkrnl it won't stick after switching to jb and back again.
Do I need to use the boot.img from the kernel and repack it into step3?
Sent from my LG-P999
Click to expand...
Click to collapse
hey, i have the same question, did u install the fastboot.bin separately or does it get installed with the flash.bat???
Hi there.
As most of you already know, starting some time ago, CM team has decided to include a script check for firmware/hboot that will allow to flash a CM based ROM only on newer firmware/hboots (2.13.0000, 2.15.0000, 2.15.4444). This is valid for all 3.4 kernel based ROMs (CM 10.2, PACman, PA, Odyssey and so on). This check was introduced because some were reporting problems by flashing such ROMs on lower hboots and it was assumed that you MUST have the latest firmware in order to flash and run them.
This leaves few options for those having lower hboots: either upgrade to latest firmware OR not flashing the ROMs at all.
What if, someone has a lower hboot/firmware and IS able to run those ROMs without issues? The previous assumption that having lower hboot will make the ROM not working/booting is wrong...at least for me and I don't think I'm unique. I'm sure that there are more users having lower hboots that could run the latest ROMs without having to upgrade their firmwares. I'm on 1.06.0000 hboot S-On and I'm happy with it. I didn't had any single ROM flashed on my device that didn't run. I don't like the idea of being forced to upgrade (going through a procedure that for some proved to be difficult or bricked their phones) without needing to
Well there is still hope....
DISCLAIMER
PLEASE BE AWARE THAT I DO NOT RECOMMEND TO TRY THIS IF YOU DON'T KNOW WHAT YOU'RE DOING. EVEN IF FOR SOME USERS THE 3.4 KERNEL BASED ROMS WILL WORK ON LOWER HBOOT/FIRMWARE, CM DIDN'T PUT THAT CHECK THERE FOR NOTHING. I SHOULD NOT BE HELD RESPONSIBLE IF YOU FLASH SUCH ROM AND IT WON'T WORK. ALSO DO NOT REPORT ANY BUGS IN CASE YOU FLASH A ROM THIS WAY
Now, what people maybe thought already (but some don't know how to do it) is that you need to get rid of that script check in order to flash such ROM. Following the steps below anyone can get rid of the check and enjoy the newest ROMs without upgrading their firmware, presuming such a ROM will run on their firmware/device
Prerequisites:
In order to do this properly anyone will need two tools
- PPCGeeks Android Signer application (or similar) - DOWNLOAD
- Notepad ++ (or similar) - DOWNLOAD
Download and install both from links above then you're ready to go...
Steps to change the script & flash ROM:
1. Download the ROM of your choice and save it on your PC
2. Create a folder with a distinctive name (say CM 10.2) and extract the ROMs ZIP there
3. Look for the file "updater-script" located in \META-INF\com\google\android folder where you have previously extracted the ROM
4. Open the file using Notepad++
5. You will usually find the check for firmware at the beginning of the file and it'll look like something like below:
assert(getprop("ro.bootloader") == "2.15.4444" ||
getprop("ro.bootloader") == "2.15.0000" ||
getprop("ro.bootloader") == "2.13.0000");
That means that, only the users having hboot 2.15.4444, 2.15.0000 and 2.13.0000 will be able to flash that ROM, anyone else will be receiving an error and ROM won't flash
6. Delete those lines with Notepad++ then save the file
7. ZIP the whole ROM again and give the ZIP a name
8. Sign the ZIP with Android Signer then copy the signed ZIP on your phone's sdcard
9. Flash the ROM
This should do it and you'll be able to flash such ROM.
There is an alternative method of extracting the file from the ZIP, deleting the lines then putting it back in the ZIP...this will skip the unzipping and signing steps but depending on how you'll do it it could also give you script errors when flashing (Status 7 or Status 6 errors). Steps to be followed for this "quick" method are:
1. Extract the updater-script from the ZIP and save it on your PC
2. Edit it with Notepad++ like I've described above
3. Open the ZIP with WinRAR and navigate to the place where updater-script is (\META-INF\com\google\android) and delete it from the ZIP
4. Using drag&drop, take the modified updater-script and drop it onto the opened WinRAR window in the location where it should be. There will be a popup windows to confirm adding the file to the ZIP, just press OK.
5. Close the ZIP and flash it
Well many of you might already know and do this one way or another but there might also be some users that don't know how to do it and either ask for help in various ROM Development threads or just quit flashing the ROM
So this is for all those that would like to try the new 3.4 kernel based ROMs and don't know how to do it. It won't guarantee that such ROM WILL WORK on their devices, it just allows flashing it even if they don't meet the firmware requirements. If after flashing, the ROM won't boot or it'll boot loop, there's almost sure need for a firmware upgrade in order to run it.
Thanks rapier. This helps me tons.
I guess the only annoying part about it is that we have to delete those lines each time there's an update/nightly that comes out. But for the time being this will suffice until I have the luxury to upgrade my firmware.
Sent from my HTC One S using xda app-developers app
I too am on Hboot 1.06 and S-on and have never had problems with other ROMs. Being away from the community for several months i'm a bit bewildered by all the risky processes I have to carry out to get my phone to accept the new 3.4 kernel.
So I will give your method a try right away!
Many thanks
RichardW1992 said:
I too am on Hboot 1.06 ...
So I will give your method a try right away!
Click to expand...
Click to collapse
Have you had any success? I am very curious.
Thanks
Patrick
This looks interesting and looks much less complicated than the whole upgrade process.
I'm on HBOOT 1.13 and S-ON; I tried to flash CM 10.2 just for fun but I got the error message (script related).
I read that those who had no problem running the latest Trickdroid and Viper can use this ROM without upgrading their firmware. TD and Viper are the 2 latest ROMS I've been using.
I'm gonna try this this weekend or next week lol - although I prefer the features of Sense ROMS.
androidsigner doesnt work
after dragging the modified zip, it get "Unable to locate file"
---------- Post added at 09:54 PM ---------- Previous post was at 09:11 PM ----------
Ok so on a forum I've found that workaround - no extraction-rezipping-signing.
This is known about theme'd files, you cannot sign them even with command line. They must be opened with 7zip as not to break the signature and edited that way, then close and flash.
Click to expand...
Click to collapse
I did that, so I guess I dont need to re-sign the file
I'll flash another day, Im really tired
By the way, question : I deleted the 2.15 verification lines in the script updater, which moved the next line "mount .... etc" up to Line 2 (Notepad++)
Should leave it as it is, or move it to Line 1?
Thanks
salutcemoi said:
androidsigner doesnt work
after dragging the modified zip, it get "Unable to locate file"
...
Click to expand...
Click to collapse
This error is because AndroidSigner uses the Java JRE and it cannot find in on the path variable. Install latest Java JRE from official site and it'll work.
salutcemoi said:
...
Ok so on a forum I've found that workaround - no extraction-rezipping-signing.
I did that, so I guess I dont need to re-sign the file
...
Click to expand...
Click to collapse
You can extract the file, modify it with Notepad++ (or equivalent) and add it back to the zip using an archiving program (I use WinRar). No need for signing in this case
salutcemoi said:
...By the way, question : I deleted the 2.15 verification lines in the script updater, which moved the next line "mount .... etc" up to Line 2 (Notepad++)
Should leave it as it is, or move it to Line 1?
...
Click to expand...
Click to collapse
After deleting the check lines, the next line in the script should be on line 1 (no blank line at the beginning of the script)
Rapier said:
This error is because AndroidSigner uses the Java JRE and it cannot find in on the path variable. Install latest Java JRE from official site and it'll work.
You can extract the file, modify it with Notepad++ (or equivalent) and add it back to the zip using an archiving program (I use WinRar). No need for signing in this case
After deleting the check lines, the next line in the script should be on line 1 (no blank line at the beginning of the script)
Click to expand...
Click to collapse
thank you !
Much appreciated :good:
I did all the zipping/unzipping through my phone with the help of es file explorer. I got cm 10.2 sept 05 nightly to work but the only thing that's being funky is my wifi. I can turn on the Wifi and it scans all the available network just fine but after placing the password to my designated internet, it doesn't connect.
I'm not sure if it's this method of flashing roms or the way I performed my zip that's causing the issue.
Sent from my HTC One S using xda app-developers app
cougzzz said:
I did all the zipping/unzipping through my phone with the help of es file explorer. I got cm 10.2 sept 05 nightly to work but the only thing that's being funky is my wifi. I can turn on the Wifi and it scans all the available network just fine but after placing the password to my designated internet, it doesn't connect.
I'm not sure if it's this method of flashing roms or the way I performed my zip that's causing the issue.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Shouldn't be affected by the script change. This change only allows you to flash the ROM, nothing else. You can try a WiFi fix or reflash kernel for this kind of issue. I had CM10.2 running well on my phone and didn't have any problems with WiFi. Same for Odyssey ROM which is also Android 4.3 with same kernel as I know
hi
i've tried this metod to install cm10.2 over cm 10.1 on hboot 1.13 htc one s.
After flash rom+gapps and flash boot.img via fastboot i'm on htc logo bootloop
any suggestion?
Tnx in advice
I also had exactly the same issue with CM...could not fix it even after flashing kernels....gave up and went to AOKP ..now Wi-Fi works, still no 4g..but that wasn't working with CM either
Sent from my HTC One S using xda app-developers app
okaiuz said:
hi
i've tried this metod to install cm10.2 over cm 10.1 on hboot 1.13 htc one s.
After flash rom+gapps and flash boot.img via fastboot i'm on htc logo bootloop
any suggestion?
Tnx in advice
Click to expand...
Click to collapse
Same here
I'm also hboot 1.13
Sent from my HTC One S using xda app-developers app
I've read it in the forum for either AOKP or CM that lower HBOOT like 1.13 is going to cause bootloops....I was hoping that using this method, in the OP thread, I'd be able to upgrade to newer ROM...but I wasn't able to (bootloops)
Sent from my HTC One S using xda app-developers app
Bootloops mean you need to upgrade your firmware. This method is only for the rare few with lower hboots and newer firmware.
el_smurfo said:
Bootloops mean you need to upgrade your firmware. This method is only for the rare few with lower hboots and newer firmware.
Click to expand...
Click to collapse
Yup
I rooted my phone and flashed custom roms before the official JB firmware update.
Sent from my HTC One S using xda app-developers app