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???
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 ?
This is an extremely simple ROM modification to the standard Advent Vega 1.10 system image that only alters a couple of things. These are as follows:
/system partition size increased from 128mb to 155mb. (The reason for this will be explained below)
su and SuperUser.apk added - You can use root apps as standard now.
ClockworkMod Recovery built-in.
Added Pauls simple recovery reboot app to get into CWM recovery.
That's all! No google apps, nothing else, just these simple changes. This isn't intended to be used as an everyday ROM (although there is no reason why you couldn't).
The main reason for this, is to be used as ROM base for VegaComb (and any other ROM you wish to use). I have been struggling with the Vega's default partition sizes while trying to port Honeycomb, and rather than spending tons of time trying to make stuff way smaller than it was ever intended to be, this seems like the better option.
So, flash this in nVflash recovery mode (exactly the same as the stock 1.10 image) and off you go. Done. No need to do anything else. You can use this base with any ROM, the ONLY downside is that 30mb of storage has been re-allocated from /data to /system, which most people won't even notice.
ALL future versions of VegaComb will require that you use this modded system image as a base (as they will require more than 125mb of /system space). To return your partitions back to the way they were, just re-flash the stock 1.10 image from www.myadventvega.co.uk (this is the ONLY way to restore your partition sizes, restoring from a Nandroid backup will NOT change your partition sizes back). You DON'T have to return to stock when you want to switch from using VegaComb, all other ROMs should work perfectly fine on top of this base, including Corvus5 and CM7.
Also, it's handy to have this in case you brick your Vega as CWM is pre-installed
AS ALWAYS MAKE SURE YOU NANDROID BACKUP BEFORE FLASHING ANYTHING!
Download ModdedStock_1.10 v2 Here!
Woo Hoo, good sign for things to come
Good work, Love the idea of a bigger /system..saves a lot of messing around moving apps to /data. Cheers. Paul
Just can't get this to install :-(
Keeps coming up with unknown device found!!
Ooops, forgot to plug the charger in.........sorry :-(
I use ubuntu will this work through wine or would i be better off trying to borrow a windows MC
Flash without usb cable?
Is there a way to flash this ROM without using the USB cable and recovery mode since my VPAD10s is giving a huge pain with windows 7 and the driver so I can not make it work.
Is there a version to be used with rom manager?
Thanks guys.
You need to use your PC because this ROM changes the partition sizes in the internal memory, and you need a PC program (nvflash) for that purpose.
Damn! thanks Logseman, I will keep on trying to get my tablet recognized over w7 can´t believe it´s so hard to make it work. wish me luck
Hope over to the Modaco Vega forum and search for YAUDIG and AUDI. They'll get the drivers installed for you.
simonta said:
Hope over to the Modaco Vega forum and search for YAUDIG and AUDI. They'll get the drivers installed for you.
Click to expand...
Click to collapse
Thanks simonta, already tried AUDI´s soft but no luck.
I´m starting to think that the issue might be with my pc/w7.
Great stuff!
Rgds
Lok
Hi:
Currently using vegacomb 0.6, i want to nandroid backup, install the new Rom base, then nandroid restore, and then upgrade to vegacomb 0.7 via the upgrade patch, in order not to loose all my settings.
So I would like to do a Nandroid backup, but being Android illiterate, i havent found how to do it in vegacomb 0.7.
Another question is , as I have moved most apps to SD, if there would be any problem regarding the base rom change and nandroid bacup-restore
Thanks for any hint/pointer
Which gapps should I use it for this built?
Zebwen said:
This is an extremely simple ROM modification to the standard Advent Vega 1.10 system image that only alters a couple of things. These are as follows:
/system partition size increased from 128mb to 155mb. (The reason for this will be explained below)
su and SuperUser.apk added - You can use root apps as standard now.
ClockworkMod Recovery built-in.
Added Pauls simple recovery reboot app to get into CWM recovery.
That's all! No google apps, nothing else, just these simple changes. This isn't intended to be used as an everyday ROM (although there is no reason why you couldn't).
The main reason for this, is to be used as ROM base for VegaComb (and any other ROM you wish to use). I have been struggling with the Vega's default partition sizes while trying to port Honeycomb, and rather than spending tons of time trying to make stuff way smaller than it was ever intended to be, this seems like the better option.
So, flash this in nVflash recovery mode (exactly the same as the stock 1.10 image) and off you go. Done. No need to do anything else. You can use this base with any ROM, the ONLY downside is that 30mb of storage has been re-allocated from /data to /system, which most people won't even notice.
ALL future versions of VegaComb will require that you use this modded system image as a base (as they will require more than 125mb of /system space). To return your partitions back to the way they were, just re-flash the stock 1.10 image from www.myadventvega.co.uk (this is the ONLY way to restore your partition sizes, restoring from a Nandroid backup will NOT change your partition sizes back). You DON'T have to return to stock when you want to switch from using VegaComb, all other ROMs should work perfectly fine on top of this base, including Corvus5 and CM7.
Also, it's handy to have this in case you brick your Vega as CWM is pre-installed
AS ALWAYS MAKE SURE YOU NANDROID BACKUP BEFORE FLASHING ANYTHING!
Download ModdedStock_1.10 v2 Here!
Click to expand...
Click to collapse
Thanks. one questions. Which gapps should I use for this built?
Thanks again.
hi, can i flashed this rom using CWM?
No, you can only flash it using a pc.
@all
Can someone please tell me how to use the nvflash, cause i'm clueless. I've searched using google but no luck, even on YouTube. I've downloaded nvflash but I can't work it. It keeps telling me about the drivers, although I installed the drivers. Any help would be great.
Thank you in advance.
jayk32 said:
@all
Can someone please tell me how to use the nvflash, cause i'm clueless. I've searched using google but no luck, even on YouTube. I've downloaded nvflash but I can't work it. It keeps telling me about the drivers, although I installed the drivers. Any help would be great.
Thank you in advance.
Click to expand...
Click to collapse
Hi
Switch off your Vega.
Connect it to the PC with the USB Cable.
Hold the power button on the Vega for 2 secs
Hold the back button while still holding the power button for a further 2 secs.
Release the power button but keep holding the back button for a further 2 secs.
You should now have a black screen and the Vega should be recognized on your PC (check in Control panel under USB for Nvidia Harmony or Shuttle)
The above assumes that you have installed the drivers.
Then open Modded Stock v1 or 2 which you should have already downloaded to the PC and it will install on the Vega (Vega will show NV Flash mopde across the top of the screen)
Once Modded stock is installed go to the apps menu and the recovery app is there. If you have already downloaded and put on your SD Card, the Vegacomb 9n Rom run the recovery and it will put you into CWM.
Wipe data, cache and in advanced the Dalvik cache.
Then select install from SD card and select the Rom and it will install.
If you continue to have problems Google Vegatools 4.1 and download and install
and it can do all the hard work.
Hope this helps
Stransky
Hi guys, sorry to hijack the thread an take it slightly off course but........
Buy flashing this stock modded rom, will it reset my touch screen issues? Read that its a pretty common problem.
I've tried the fix at modaco, and it works.......for a very brief period, then back to just half of my landscape screen being recognized?
I've only had my Vega a week, can any other of you more experianced fellows point me towards a fix? It would be much appreciated.
Sent from my VegaComb using xda premium
Thanks for a awesome rom.One questions,having problems with the sensor.Is there a simple solution to this?i have wiped dalvic cache but didnt help.I want to play games like NFS Shift and ather other games with sensor abilities.
Why not use Custom MTD ?
http://forum.xda-developers.com/showthread.php?t=717874
Hi,
I have been in contact with Bertans through his LEANdroid thread and through private message and we have been working on a bit of a mod for LEANdroid. Basically people want OC/UC and the rest of the goodness from other roms.
It is a mod of LEANdroid 11.10.2 and has a few extra bits over and above that rom. Now has a kernel custom compiled by me from aorth's kernel source.
Includes:
LEANdroidMOD_6
-2.2.2 Thailand rom base, newer and has the mystical .2 instead of .1!
-NOMA kernel from before
-Custom Ubuntu and Jura fonts because they look better than the ugly android ones
-Not compatible with previous 2.2.1 releases (up to LDM 5)
-This is for testing, not sure if it is compelling enough as an upgrade over LDM5 as I am going to include fonts in LDM 5 too.
-Still has old market, but it will auto update, may update it in a future release.
-Has XDA anti malware patch set up in installer.
LEANdroidMOD_5
-Custom kernel based of NOMA source
-Very custom smartass cpu profile setup, seems fast and battery efficient
-24/12/12, now has Ubuntu and Jura fonts and XDA anti malware patch in installer
-Otherwise similar to before
Previous
-Android 2.2.1+ LEANdroid 11.10.2+
-OC/UC 30mhz to 691mhz. Defaults to 30mhz and 600mhz- Fusion Kernel.
-Smartass and interactive governers. Default is ondemand.
-164MB free space.
-Some custom sounds.
-Fusion kernel 122mhz and 600mhz by default.
-Busybox
-NOfrills cpu control installed by default.
-Tweaked memory management
Everything that worked on LEANdroid should still work up to LDM 5 but it has a more spicy kernel and a few more tweaks. Please backup first as I cant be responsible if it doesn't work or you lose stuff. As these builds are just LEANdroid with a different kernel and a tweak or two, you should be able to get away with just flashing it over your existing LEANdroid install and just wipe cache and dalvic cache.
Download:
LEANdroidMOD_6, 2.2.2 base with everything back in /system directory to see if wifi can work for people.
Download: http://www.mediafire.com/?x8avapvmqlr78y6
MD5: 231D186B7A39E4D0588881A441AAE91F
LEANdroidMOD_6, 2.2.2 base
Download: http://min.us/mbomINMMtE
MD5: 377C8B6E01504BCF054126029BA1C223
LEANdroidMOD_5, 2.2.1 LEANdroid base
Download: http://min.us/mC8N9JhJE
MD5: F70D5C4BCB3F5BF0900F80E0B0FCB97C
Original Thread: http://forum.xda-developers.com/showthread.php?t=987736
Install
Install procedure:
-I installed Clockwork Mod recovery from rom manager which is the 3.0.2.4 version.
http://forum.xda-developers.com/showthread.php?p=13264607
http://forum.xda-developers.com/showthread.php?p=12619750
Reboot after install and hold volume up and green call button then push the power button > hold vol up and green call until recovery menu comes up > wipe user data and cache as well as dalvic cache in advanced menu > choose install zip from SD card and select whichever LDM release you are using. Once it is installed, reboot the phone and you should have a shiny new LDM install.
Thanks
-Bertans for rom base and help
-Androcheck for task killer help
-Dsixda for Kitchen
-aorth for kernel source and answering my annoying questions!
-NOMA Kernel Thread: http://forum.xda-developers.com/showthread.php?t=1228715
Kernel:
Source: https://github.com/PaulMilbank/kernel_huawei_u8150
Hocaeit Kernel 691mhz: http://min.us/mYEQMfD42
Flashable kernel 691mhz: http://min.us/mQYYzixNJ
Flashable kernel 729mhz: http://min.us/mVebnFefs -have not tested yet.
http://www.mediafire.com/?j7fvexu9h1odq
Cheers,
Paul
Looks Good!
Great job - I'm excited - will try tomorrow. What keyboard and launcher is this running?
I will try it (I am excited about it).
Still dun understand why everyone say about abd driver in install procedure when all is done on phone and phone sdcard.
Is running standard android keyboard and launcher pro just like LEANdroid.
Think the adb part is just to get clockwork mod on there. You can also use rom manager if you want, although that seemed to be playing up last time I installed it. if you play a bit more you can also use fastboot, but I have not tried that yet. Im still running CWM 3 installed ages ago using rom manager.
Any idea how to get extended "Phone options" when i press power button.
Like reboot, etc not just the 3: Silent, Airplane, Power Off ??
Thx.
It is something to do with custom frameworks. Have not explored that much as yet. Trying to get the kernel good and fast for a start and then can look at custom looks for later.
Hangs at Android logo
I had just finished flashing LeanDroid when I noticed your (what I like to call) "LeanDroid on Steroids" (on Steroids due to being overclocked). I had been thinking if I were to right a ROM, this would be it...so...I was jazzed. I spent all day trying things over and over and can't get it installed. It just hangs at the "Android" screen. I had to install something so went back to regular LeanDroid and installed it again with no problems. I did everything you suggested including the wipe and the new CWM to no avail. Did anybody else get it installed?
Oh, ok... interesting. will have to do a wipe and flash and see what is going on at some stage. Have been developing it as I go on my phone, so possibly it works as I have been flashing kernels and such over existing builds.
Has anyone else had this problem?
Does CWM give any errors with installing?
Im guessing you are reasonable experienced with flashing, but how long did you leave it for on the android screen?
is this the android animation screen or the boot splash?
Does the MD5 hash match?
Thanks for helping test this, hopefully can get some more info and testing done to work out what is going on here.
heh, just flashed it from fresh and no dice, boot loop. trying to suss it now.
Going to upload a more basic build which is just leandroid+ kernel. Just tested on fresh install and it boots fine. Link will be updated in the first post.
Paul
Ok, take 2... try the new mod which is in the original post. It is straight LEANdroid+fusion kernel.
CWM gives no errors. Not heavy enough to know the meaning of "MD5 hash match" but also not fresh out of the box; I gave it at least 5 minutes on the "Android" screen (don't know if that's called the animation or boot splash); regular LeanDroid takes almost exactly 2 minutes so I thought 5 should be long enough. Will try the new one now. If doesn't work it will take me a little while to get back to you about it because I'll have to reinstall a working ROM so I can connect and reply. Here goes.
PS: I'm not doing this for fun; I just wanted a fast & lean ROM because I found myself demanding a lot of my little IDEOS and she was getting intolerably slow...am I'm really exhausted from trying to come up to speed on all this over the last few weeks...so...I want to be finished with this now...so...when you do any future updates (in gratitude for my help ) if it's even possible, could you please make sure it catches this LEANdroidMOD_2 so I don't have to do anything else to have your final version? I'd really appreciate it. Here goes. I'll let you know what happens.
OK. It loaded. Took 2 minutes just like plain LeanDroid. I went straight to the app drawer to play with NoFrills but it's not there. I realize you probably "lightened" this one as a troubleshooting tool to get her working. I just installed NoFrills and it does offer the 691MHz of the custom kernel. Sorry for asking you to educate me but:
1. Is it very advantageous to have NoFrills (or any desired apps) built in to the ROM instead of installed separately and if so, why?
2. Should I go 691, 122, ondemand, & deadline or what?
3. Should wait before I start heavily customizing my homescreens with postits, etc. because this prelim version won't be updated?
4. Is there a way to update to a more final version without losing my homepage customizations?
Thanks for the (I say best) ROM and any educating you give.
Hey Paulynator, thanks for your patience. Leandroidmod_2 was a very quick build to get things moving as I had to build something to get my phone working after the first rom didn't boot in testing! Will upload another build with busybox by default and a couple of small mods today. Problem came from data/app, so ditched that and put apps into /system/app.
Questions:
1)Not really, I just like it, others may prefer setcpu or something else instead.
2)You go with what you feel happy and doesnt crash your phone, try 652 and 60 first, then go higher and lower if it is working fine. Just leave apply on boot unchecked in nofrills until everything is working fine. Ondemand and deadline will be fine.
3)Updates should be able to be installed without a wipe.
4)Just install zip in CWM over your install, sorry, I cant promise anything though.
Thanks
Paul
Ok, take 3. everything from 2+busybox and some custom bits. Tested on my phone and it boots fine with a total wipe. Hopefully wont need to do a total wipe, but have not tested flashing over an existing install.
For question #1, I didn't mean NoFrills as opposed to SetCPU or something else; I'm asking if it's very advantageous to have desired apps built in to the ROM instead of installed separately and if so, why?
Paul,
Report on LEANdroidMOD_3 (a.k.a. LeanDroidOnSteroids, c'mon, it rhymes!) (or even "cleaner": SteroidLeanDroid. If I say so myself, awesome title for an awesome ROM...to me.)
Installed over version #2 w/o wipe seems to be ok...to the extent that I started the process of recluttering (restoring) my Ideos as though "she's a keeper", i.e. no more wiping; the records stay intact from now on.
Paul
---------- Post added at 05:55 PM ---------- Previous post was at 05:47 PM ----------
Sorry to hit you with 3 since your last but since we have a "hard"/permanent Home button right below the screen, is the redundant one at the bottom of the app drawer removable from a menu or would I have to mod the rom to remove it?
Paulynator said:
For question #1, I didn't mean NoFrills as opposed to SetCPU or something else; I'm asking if it's very advantageous to have desired apps built in to the ROM instead of installed separately and if so, why?
Click to expand...
Click to collapse
Doesnt matter one way or the other, I just liked it built in. Only possible advantage is that some apps in /system/app wont use space in /data/app, but this is lost the moment you update them as updates seem to install into /data/app. So my Leandroid with nofrills in /system/app still gives 164mb free space in data partition until things get updated.
Good work, thanks for the update that it can be installed over a previous install.
Home button is part of launcher pro. on the home screen, hit menu>preferences>appearance settings>uncheck home button on app drawer.
Paulynator said:
Paul,
Report on LEANdroidMOD_3 (a.k.a. LeanDroidOnSteroids, c'mon, it rhymes!) (or even "cleaner": SteroidLeanDroid. If I say so myself, awesome title for an awesome ROM...to me.)
Installed over version #2 w/o wipe seems to be ok...to the extent that I started the process of recluttering (restoring) my Ideos as though "she's a keeper", i.e. no more wiping; the records stay intact from now on.
Paul
---------- Post added at 05:55 PM ---------- Previous post was at 05:47 PM ----------
Sorry to hit you with 3 since your last but since we have a "hard"/permanent Home button right below the screen, is the redundant one at the bottom of the app drawer removable from a menu or would I have to mod the rom to remove it?
Click to expand...
Click to collapse
Just found a possible glitch. Don't know if it's the ROM so tried the obvious things to no avail. The camera app (any camera app; I tested the problem by downloading and trying others) won't access the gallery. In the stock app, the little preview window (that tapping opens the picture in the main window) won't open the picture. It gives an error message saying "app initialize failed. please download the app from the market". The app isn't in the market so I d/l'd 2 other camera apps and they both did the same. Using Root Explorer to try to open a picture also wouldn't work. Could you please try to access the gallery on a phone you've installed your ROM on and let me know if it works? I'd appreciate it. Thanks.
Works fine on mine. Try go to the market and update Quickpic. It does not like being in /system/app so if you update it, it should work. It was one of the reasons I tried to put it in a data/app from the start, but that caused bigger problems like the rom not booting.
I could also put the stock gallery back in alongside quickpic if needed but it does not have multitouch.
Hola peoples!!! Ok so I just thought I'd create my own thread on this matter. Mustangtim started one in apps and themes (and here is the link to that thread) but since I'm taking over this project it was brought to our attention that this should be in the dev section as its no longer just an app.. I am actually tearing .imgs apart trying to figure out what the deuce.
FIRST OFF THIS IS A WORK IN PROGRESS, WE ARE NOT YET FULLY SUPPORTED. HOWERVER I'M DOING MY BEST TO CHANGE THAT.
Secondly if you want to help get this started please visit the market and grab the app here. Its a $3 dollar app for unlimited amount of roms, based on your SD card storage capacity anyway. And speaking of which you need AT LEAST a class 4 or better SD card to make this run smoothly.
Also feel free to visit the forums at http://forum.init2winitapps.com/
Ok so here it is, Boot Manager Pro. Its been a long time coming for the g2x to dual boot. First off let me say long story short, I currently have a bootable SD Rom, known as ROM1. I have yet to be able to recreate my findings tho. But it works and it doesnt brick at all. However it is a bit laggy on my class 4 SD card. Luckily I've already done my research on this project as there are many threads of such awesome info so I'm just going to be lazy about it and quote the good people of xda versus re-writing it based off of their info.
ChrisDDD said:
So here's a very basic description of how it works... It doesn't partition your SD card, it just creates a folder of its own, and then sub-folders to hold the different roms you install. When you install a rom, it basically creates images of the usual Android partitions - system, data, cache, & boot. These are standard .img files, just like the ones Clockwork creates when you do a backup. After the images are created and wiped (formatted, which you should do initially) it installs your rom into these essentially the same way as Clockwork installs a rom to your phone's actual partitions. I assume it modifies the kernel that comes with each rom to mount the image files on the SD card instead of the phone's partitions.
When you want to boot a rom, it just replaces your current boot image with the modified one and restarts the phone. With the modified boot image, the system, data and cache images on the SD card are mounted to the correct locations and Android starts up none the wiser. The rom will initially run a little slow, because the SD card is slower than the internal memory, but after things get cached it speed up considerably.
When you want to reboot to another rom, or back to the phone's rom, Boot Manager again swaps boot images that mount the desired rom's partitions (in the case of the phone's rom) or files (in the case of an SD card installed rom).
When you first run Boot Manager, it makes a Clockwork flash able backup of your current boot image, which you can flash if a rom hangs or loops on startup. Alternatively, you can also simply boot into recovery and do an advanced restore, choosing just the boot image to restore from a backup. It accomplishes the exact same thing.
It can be a little hit or miss, with some roms just plain refusing to start through Boot Manager, but it does work and when it does, it's pretty amazing given what it's actually doing.
Click to expand...
Click to collapse
So basically upon installing the app you need to setup your phone so that way you can properly install a ROM, follow these steps:
1. Go into the supersu(or superuser app) and then go to settings then disable logging or click none.
2. Then go into the BMP app and press the menu button on your phone, not the app, and go to settings. Once in settings put a check mark in force large boot.img, screen on during install, and then go into variables, leave tegra alone but change the sdcard block to show mmcblk1p1. Then press finish and let the app restart. By the way I didnt change any of the sizes of the .imgs but feel free to do so. But be warned do not decrease the size of the system.img only increase it, if desired.
3.Then after you've done the above you need to setup the phone rom. Click on 'Setup Phone' under phone rom and follow that process to setup your phone rom.
4. Once your phone rom is setup you may begin to install a zip to rom1 or rom2 or whatever slot you want. This is the tricky part. I have done tons of reading and most people say that if your using CWM, which us g2x'ers do, then you will probably have a better chance of getting a bootable rom by restoring from a nandroid backup you did versus installing new.
5. So after you decide which path you will take, nandroid backup or fresh rom install, choose install. If you choose a fresh rom, wipe system, data, and cache right away. If nandroid, then wipe after the install.
6. Now once you have clicked install put your phone down, DONT MESS WITH YOUR PHONE AT ALL! PUT IT DOWN AND WALK AWAY OR SOMETHING! Don’t mess with it, text from it, xda from it, dont even use the screen as a mirror!!!! lol seriously the app is picky and while under the .img creation process you want nothing to mess that up or you will not get it booted. You may however drag down the notifications bar to follow the progress of the install.
7. Once its complete, tap the install complete notification in the notification bar and let the app do its thing to finalize the install and get you back to your rom selection screen. Now if you did a nandroid back up here is where you click 'manage slot' and then factory reset the backup you did. Just do it, dont ask why.
7.1 Also so if you desire to install gapps and/or possibly a different kernel, now would be the time to do so while your here. I have read mixed reviews of doing this process right after the rom installs. However when I set up my rom1, I booted into it first all happily then realized I had no gapps. So I had to reinstall BMP on rom1 then boot back to phone rom and then I installed GB gapps and had no issues booting back into rom1.
8. Once the above steps are done if your feelin lucky go ahead and tap on boot the rom you installed, and if all goes well it will boot up.
9. If it boots up you need to post confirmation here!!! Provided info such as phone rom and the info on the sd rom you used and slot number and such.
Hopefully it will just work for you. I have done all the above steps using HFP 2.1 as my phone rom and only been able to get 1 bootable rom. Being it was for testing I used HFP as my phone rom and as well as my rom1.
So if the above steps dont wortk out for you and your boot lopped or what ever, then turn your phone off and reboot into cwm. You have 2 options to resolve the boot issue you just created. 1, you may go to restore then advanced restore then restore your boot. Or 2. select install a zip and nav to the bootmanager folder then phone rom then flash the update zip there.. then reboot and you should be back at your phone rom.
Here is a basic run down of everything that I have done so far:
When I first started working on this project I wasn’t doing any dev'ing to change any of the stuff in the boot.img. I just changed settings in the app per all the research I did. So when all was said and done I restored HFP 2.1 to ROM1 and it actually booted!! And it works lovely btw.. I can still boot into this rom today. I then decided to pass the word and ways that I created the working rom1, well I nor anyone else I passed the info to was able to get it working. Only one other person was able to confirm that rom1 works but only after I copied all my rom1 info and sent it to him for testing.. and he was able to boot into my created rom1… As I see it, it was a blue moon event that I have yet to repeat. So I thought eff it lets do some dev'in so I unpacked the boot.img from rom1 then compared that to the unpacked boot.img from rom2 that I created in my trial and error experiences. So in doing so I noticed 4 differences; 1, the mount points obviously, 2, in the sbin folder had a ueventd file from the working rom1 was a text file viewable by gedit in ubuntu. In rom2 it was just a non-readable file. 3, in the init.rc file was also missing a chmod command for system, (the command is in rom1 but not rom2) and 4, there was a ueventd.tegra file that was in rom1 that wasn’t in rom2, but everything else is the same. So I decided to plug and play with the differences to see if she boots and no go. I don’t understand why its boot looping because I am using the same rom as phone rom as for rom1 and rom2. So it boot looped. So I had to restore my boot.img many times in cwm.
So then I said eff it lets do some more research, then I noticed in the .zips folder plus the individual rom folder there are .zips that will let you flash via cwm if you get boot loops and 'should' get you booting to your desired sdrom. I then tried that way and no go.. so then I opened up the zip and had a look at the internals.. first there is the moveboot.sh file that the app runs in cwm flash the given boot.img. I then checked out the meta-inf and opened up the updater-script thinking that the app wasn’t actually flashing the boot.img which is why it loops... Well I think im half way right. However the script itself is lil dodgy... first thing I noticed was at the end of the script they have a command to cp the log from /tmp to /sdcard/bootmanager well the command was wrong so it never copied the log. So I fixed that. I also saw that the assert command was pointing to ‘boot’ instead of mmcblk0p5, so I changed that too. Then I decided to do away with the assert command and the moveboot.sh file they have going on to utilize the same functions that the kernel zips use, which is a kernel folder that holds the boot.img and a run_program that dd's the boot.img to 0p5. plus I even updated the update-binary that the file uses. I used the one from the g2x nullifier as I know that one was made for our phone and should have no issues.. plus there was a noticeable difference in the sizes of the provided binary to that replaced binary. So with the updated.zip file I then rebooted into cwm to flash that being that I was using a different command to flash the boot.img as well as the other changed stuff and still it boot looped. So as of now the only thing I don’t think ive done was grab the boot.img from rom1 then change the mount points, only change that, and then use that for rom2 and see if it boots. I don’t think I’ve done that yet. But every dam process I do I get boot loops. So basically I have came to the conclusion that it’s now NOT a boot.img issue being that I have done everything to change the boot.img and to make sure it flashes, which it does indeed and now creates the log too… I think maybe it has issues with the system.img as that’s what comes next in the boot process. But that’s just my hypothesis. I won’t be able to confirm this till I liberate rom1’s boot.img then change the mount points to point to rom2 and then see if it boots.. if it don’t work then that would mean to me that there is an issue with system.img created. But that’s just my hypothesis…
What I don’t understand is why the eff when I didnt hack the app I got a working sd-rom, but when I do change some stuff with it still don’t work!!???!! I guess maybe ill just edit/hack the apk to see what’s up.. This is getting way more complicated than it needs to be, since it worked prior to all my major changes to the script its using for flashing and the boot.img and what not. Anyone have any ideas feel free to add them.
My next steps are to edit rom1 boot.img one last time to change the mount points to point to rom2 and then if that’s a no go then it’s got to be the system.img that’s getting created. By the way this whole process I have only been restoring my nandroid backup for HFP 2.1. I have not attempted to flash new as with thru my research more times than not people would get a bootable rom via restoring versus flashing new.. so if anyone wishes to experience an sd rom let me know, ill send you a link to download my rom1 to get it going. Mind you that its not perfect and you need a class 4 or better sdcard. Everything works but it just takes a bit longer to load things and get things cached as its on the sdcard and not nand. Also if you have any input or are wishing to help pm me I need more heads to get this sorted as I can’t be the only one who knows how to edit scripts and unpack imgs and such. Either way I will continue to do this until I get it right damit!!! Oh and I just ordered a class 10 sdcard to help with this process…
That was copied from the other thread that mustangtim started. Last night when I went home the first thing I did was change the mount points on rom1 to reflect rom2, I changed nada else, then I tried to boot it... it boot looped. So maybe its a permissions issue or the system.img.
So just as a proof of concept and before anyone calls bs on my work/findings Here is the link to my rom1 that boots and is HFP2.1. *Update, 'm just going to
leave it on my DB for now till I find something better I guess. xda wont let me attach the file since its 233MB. Oh well here is the link :
Code:
[URL="http://db.tt/eBZwrOrs"][U][B]Here it is, my Rom1 HFP 2.1[/B][/U][/URL].
I have also attached my updated script file to flash back to rom1, for now.
The boot.img points to rom1 instead of phone rom, ill add to phone rom
as well, just not the now. :) Feel free to flash this via cwm versus
restoring...
Also this is part of the this: the ‘.zips’ folder you need to replace the file in
that folder as well. It’s an update file for rom1 to flash the boot.img.
..
If you’re going to use this you need install a random rom to rom1 then replace those created files in rom1 with these files in the 7z file..
So I am doing this new thread to get the devs or people with know how to help me out with my findings. I have edited the boot.img so much I could pretty much re-write everything in there by now including using magic to create to my own kernel eff!! lol jk but seriously I need people with knowhow to provide confirmation of go or no go. Basically I have people whom have helped out but It seems that I'm the only one who has dug this far into this app(unless i've been misinformed) and I have no one on my level to talk with except the init2winit devs. Which are very helpful btw.
And lastly:
Conap said:
Guys if it's failing to make the boot.img first make sure your using the market version....others have released cracked versions of our app which they broke...if your using the actual market version just send me a pm or email [email protected] and send your log.txt from BootManager folder on sdcard and we'll get it straightened out. Thanks.
Click to expand...
Click to collapse
or post here or PM me, I'm always down to help out.
Also thanks go to the init2win team, Gflam and Conap as they started this app. and as well to Mustangtim as he brought me into the light of BMP.
So you got all that???!!!??? Now lets get this party started and get full support for dual booting. I will not rest until I get this working. Thanks for your time and possible assistance.
Ok so since I have a book above I thought this is a good place for links and such...
So just incase anyone is curious, here is the Official Boot Manager Manual
Here is a nice link for Tips and Tricks while Installing ROM's that so far has good info to help you watch via adb what the BMP is doing in its creation process.
Some FAQs:
When should I set up my phone ROM?
Set up your phone ROM EVERYTIME you install a new ROM to your phone so you can get back to your phone ROM and won't get stuck on your SD ROM.
My SD ROM seems to lag how can I fix this?
SD ROM lagging may be due to a few things which all have easy fixes. First fix is that most of you have class 2 cards which are what usually come with your phones. These have a much lower read/write then cards of a higher class, we recommend a class 6 card or above. Another easy solution is overclocking merely install a better kernel and use CPU Boost (or any other overclock app) to overclock your phone.
Can I nandroid my SD ROM slots?
Yes and no you can't nandroid them in the traditional sense of the word using recovery but this app works as a recovery for your SD ROM slots and you can back up your ROM slots within the app in the Manage Installed ROMs section which works as a nandroid for your slots by fully backing up your slots to your sdcard which can later be restored.
What if I want to change the sizes of my images, how may I determine the individual sizes easily?
Easiest way is to open up terminal emulator in your app drawer. Type 'su', then grant permissions if need be, then type 'df -h' and it will display such information. You may also use adb in the same fashion. Connect via usb, open up command prompt/terminal and get adb connected and then type 'df - h' again and the same info will show. I will say this again just because, do not decrease the size of your system.img ever! Unless you want mad issues!
Here is the changlog link and just for heck of it the info based on that link:
Code:
V3.2.6
Fixed DroidX/Droid2 Install issue
Fixed UI theme issues
Fixed issue with spaces in name of pic when selecting photo for screen shot
V3.2.5
Fix to allow continue of install if no boot.img is found.
V3.2.4
Added support for HTC Rezound
Added support for rom's with multiple boot.img's
Added support for rom's made for multiple phones
AutoDetect sdcard for usb mounting
Fix for installing ICS gapps
Optimized SDRom Install process
Added support for Motorola RAZR
Added install queue
V3.2.3
Fixed issues with rom's not showing when on emmc on Droid Incredible
Fixed issues with not showing correct booted rom in app
More improvements to sms sync(all rom's will need updated app for changes to apply)
Fix issues with loader
Fixed issue with switching to backup server when main server goes down
Fixed 1x1 widget to show unlimited rom slots
Added 2x2 widget that works with unlimited rom slots
V3.2.2
Fixed force close for img's over 1Gb when resizing
Fixed current booted rom displaying correctly on gnex
Fixed issue with wrong busybox downloading on gnex which should fix alot of install/boot issues
V3.2.1
Fix for errors causing installs to fail.
Fix for some of the licensing stuff.
Removed sdbooster prefs from Galaxy Nexus(Since they don't have sdcard).
V3.2
Changed 4 sd slots to infinite slots!
Galaxy Nexus Support
Sms and Call Log synced between ROMs (you choose what ones too also requries updating boot manager in all slots)
License Check extended to a week
ROMs do not need market installed for boot manager to run (requires updating boot manager in all slots)
Hide su toasts (superuser elite only)
Fix for force close when setting screen shot in MIUI rom's
Thunderbolt defaulted to force large boot.img
Fixed unsupported device using a key
Manually setting variables only accepts numbers
V3.1.1
Fix for various force closes in rom installs and Nand restores
V3.1
Added su binary check
User selectable colors for everything
Better navigation (press title for quick action)
Added compatability for new twrp backups
Better compatiblitlity with memory tweak scripts(i.e. supercharger script and liquids default scripts)
Fix for install process being killed by android
Fix for some themes erasing img's
Fix more force closes during install
Force smaller boot.img option in settings(Fix for some phone's who's boot.img won't fit on the phone after BootManager edit's it)
Improved gapps checker
Improved security
Boot Manager now accepts keys pay for by paypal (see http://init2winitapps.com/stories/BootManager.html)
Added Evo 3d GSM Support
Added notifcation sound/vibrate for finished install (turn on in settings)
Improved data check
V3.0.3
Fix some force closes
V3.0.2
Added backup server (Sorry our server dropped out)
Fixed some force closes
2nd init fixes for Liquid's ROMs
V3.0.1
Last minute UI fixes
V3.0
UI Completely redone
Includes screen shot of each slot
Custom Info
Custom Dialogs
Custom Animations
Custom everything!
Bug Fixes
Added Droid 2 Global support
Screen shot with long press of search
V2.2.1
Bug fixes in file browsers
File browsers only show relevent files
Kernel installer fix
Droid 2 bug fix
V2.2
New security (more advanced and requires data only once a day)
Installs no longer require data
Added Italian translation thanks Black-Ice
Droid X support
Droid 2 support
Fixed status bar notifications
Fixed phone rom rebooter if gapps aren't installed
Bug fixes
V2.1
Restore android_secure to sd from nandroids
Added TWRP nandroid support
Added CWM tar nandroid support
Added Spanish translation
Made widgets easier to use
SD Booster added (Change SD read cache for better preformance)
Added current settings to manually set variables.
Added option to keep screen on during install in settings
Fixed usb layout
Updated Security
Bug Fixes
V2.0
Install now runs from the foreground (status bar)
Restore Nandroids to slots also in the foreground
User can cancel installs as they run
4 new themes added including one by apophis9283
Some phones such as tb moved to new install code (Fix for some sense rom's)
V1.3
Added third theme to app (Red Theme)
Added 4x1 widget and new widget styling
Fixed in app messenger
Added support for Htc Evo 3D
Added support for Htc Sensation
Added Support for Htc Incredible 2
Added Support for Htc Incredible S
Added Support for Htc Desire S
Added support for LG Ally
V1.2
Added option to reboot to phone rom to install gapps in license check dialog
Better error checking and error logging
Automatically install's ext2 libs if not present
Moved Set Names to Manage rom's
Fix for add-on's not installing correctly
Better compatiblility for rom's that use data2ext or apps2sd(user must set larger img's in manual variables)
Trash cleaner added to extras
Better Fix for WiFi issues on Droid 1
Added display to show what rom you are booted into
Fix for updater-script not found errors
Added support for Htc NexusOne
Added support for Htc MyTouch4G
More compatiblity for ext4 support
V1.1
Fix WiFi issues on Droid 1
Fix bug in rom installer for setting permissions correctly
Fix bug for cache size not setting correctly in setting variables manually
Fix for decimals entered into partition sizes causing force close
Fix force close in widget
Fix force closes in installer
Added Wipe data/Factory reset to Manage Rom's section
Added code to show what file's are being unzipped in dialog
Added support for rom's that extract files to sdcard so the files actually end up on your sdcard
Added support for Htc Desire (apps2sd and data2sd rom's support is experimental. Please email if you test it and it works/doesn't work)
Added support for Htc Inspire4g
Added support for Htc DesireHD
Added option to use ext4 filesystem if rom's support it-Experimental Won't work with all rom's.
Added log.txt file to sdcard to log errors during install
V1.0
Initial Release
YEZZZ
glad to finally see this here!
jookdakang23 said:
glad to finally see this here!
Click to expand...
Click to collapse
indeed... hopefully it wont be before too long that I get this app fully supported for us!
This app will be extremely useful for G2X owners and makes the G2X more versatile and desirable.
da-pharoah said:
indeed... hopefully it wont be before too long that I get this app fully supported for us!
Click to expand...
Click to collapse
idk how you get it booted. lol i keep getting bootloops
jookdakang23 said:
idk how you get it booted. lol i keep getting bootloops
Click to expand...
Click to collapse
Are you using the files I supplied or the ones that BMP created for you?
Woo hoo good job bud
Sent from my LG-P999 using xda premium
x0xhellx0x said:
Woo hoo good job bud
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
LOL thanks bro.... Go Team Hellfire!!!!
da-pharoah said:
Are you using the files I supplied or the ones that BMP created for you?
Click to expand...
Click to collapse
i remember requesting the files but think you ever sent them
jookdakang23 said:
i remember requesting the files but think you ever sent them
Click to expand...
Click to collapse
no we had a miscommunication due to our avail times and GB's lacking ability to utilize two accounts on gtalk.... I have posted those files in the op however...
First, I want to thank everyone who has helped with us on this app. Second, I know I picked the right man for the job, did you see that OP! All kidding aside, a lot of you know I write for ACS under screen name artifintel. I just had too much on my plate to give this project the attention and direction it needs. The right guy is in charge, he's a stand up person and very knowledgeable with this app. Good luck everyone!
[email protected]
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Rafase282 said:
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Click to expand...
Click to collapse
what rom are using as phone rom? and you installed to rom1?
da-pharoah said:
what rom are using as phone rom? and you installed to rom1?
Click to expand...
Click to collapse
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Rafase282 said:
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Click to expand...
Click to collapse
and no bootloop you say?? well then it may be the stock rom your using... The app is very picky and if you get a bootloop, I feel that those can get booted with tweaks... but stuck on lg screen is just no bueno.. Try a different rom... maybe one that has its partitions at ext3 format just to try it.. I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
hands down, a badass app...
SiL3nTKiLL said:
hands down, a badass app...
Click to expand...
Click to collapse
lol +1 for sure!
da-pharoah said:
I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
Click to expand...
Click to collapse
positive on ext4
Team Win Recovery Project 2.3, 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.3.2.3:
-Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see notes)
-Fixed a bug with deleting a backup with a space in the name
-Added highlights on keyboard key presses
-TF101: Ignore blkid when mounting /data
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
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 acquire a recovery.log - you can do this in two ways - the fastest is "adb pull /tmp/recovery.log" right after you have the issue. Alternatively in the advanced menu there's an option to copy the log to the sdcard. Also 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 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.
We also now back up and restore boot! Yay!
Want to compile yourself?
I'm using this config: https://github.com/ViViDboarder/android_device_asus_tf101
And this kernel: https://github.com/ViViDboarder/android_kernel_TF101
And compiling against CM9 source tree
Further device specific announcements will go here
A few thanks for this specific build:
Roach2010 for helping be me test and find the mystery kernel
RaymanFX for finding a config that worked. Still not sure where he found it yet exactly
And... Dees_Troy and eyeballer for their relentless nagging
first ...
well second lol
So, third ......thanks guys, that's awesome !
thanks, been waiting for this.
great work, i've been waiting forever and finally have this on all my devices and those that I support.
I've been using the other one RaymanFX had built and both are awesome. Only 1 change other than the known issues, would be remove the "Bootloader" button under restart. But just my opinion. Thanks Again.
gdeeble said:
I've been using the other one RaymanFX had built and both are awesome. Only 1 change other than the known issues, would be remove the "Bootloader" button under restart. But just my opinion. Thanks Again.
Click to expand...
Click to collapse
Good note. That's a theme issue then. I can build a new theme zip or something later. Working on releasing the much delayed Nexus One build.
EDIT: I've been informed by Dees_Troy that we have build flags to do just this. So I'm adding them to my configs so the next build should have them removified.
It's worth pointing out that this build of TWRP has a recompiled kernel with boot and recovery exposed. You can finally back up boot and restore it.
GooManager keeps hanging at Looking for recoveries after trying to install OpenRecoveryScript. Unable to retrieve files...
Finally recovery on a touch screen device the way it should be! Thanks guys!
Sent from my SGH-I747 using Tapatalk 2
I thought I would give this a try and went to the TWRP page link as instructed. Followed the instructions to download the open recovery through goo manager, which it did and it rebooted my tablet and all looked good. I then tried to reboot to recovery from Team EOS3 Power menu. The usual TWRP blue curtain was there and when it raised, I saw the text at the bottom that my /data partition was being formatted without formatting /data/media and the tablet rebooted, without ever getting to the TWRP recovery menu and I'm now back at the initial Google setup screen. Guess I should have made a fresh Titanium backup first. A warning would have been nice, or is this a bug?
Strange. But I copped the blob from twrp site as "not recommended" suposedly. Ran the command in terminal cuz I don't Fux with goo manager... Everything worked fine. No issues
~Poisoned Viper4g LTEvOne by TeamVenom, Lionheart Cranked to 1.72Jigawats Deadline: Ca1ned.
MassStash said:
Strange. But I copped the blob from twrp site as "not recommended" suposedly. Ran the command in terminal cuz I don't Fux with goo manager... Everything worked fine. No issues
~Poisoned Viper4g LTEvOne by TeamVenom, Lionheart Cranked to 1.72Jigawats Deadline: Ca1ned.
Click to expand...
Click to collapse
Since it's installed now and it wiped my data without asking, I'm going to clear things out and reflash everything. I will test if it tries to wipe my data again after I reinstall a few apps.
sidneyk said:
Since it's installed now and it wiped my data without asking, I'm going to clear things out and reflash everything. I will test if it tries to wipe my data again after I reinstall a few apps.
Click to expand...
Click to collapse
Weird. It didn't wipe my data. Just installed nicely as per instructions.
running great with no issues I used goo manager app but i flashed it through the flash roms selection on the main menu not the 3-dot menu install open recovery script selection.
sidneyk said:
I thought I would give this a try and went to the TWRP page link as instructed. Followed the instructions to download the open recovery through goo manager, which it did and it rebooted my tablet and all looked good. I then tried to reboot to recovery from Team EOS3 Power menu. The usual TWRP blue curtain was there and when it raised, I saw the text at the bottom that my /data partition was being formatted without formatting /data/media and the tablet rebooted, without ever getting to the TWRP recovery menu and I'm now back at the initial Google setup screen. Guess I should have made a fresh Titanium backup first. A warning would have been nice, or is this a bug?
Click to expand...
Click to collapse
Did you ever try to use goo manager with the old unofficial version?
Sent from my HTC One S using xda premium
ViViDboarder said:
Did you ever try to use goo manager with the old unofficial version?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
No, I was using RaymanFX's TWRP build prior to this and before that Team Rogue Touch and before that Roach's CWM build, all flashed from within recovery. I only did the GooManager thing because that was the recommended method. Subsequent boots to recovery did not reproduce the data wipe and after reflashing my ROM and restoring my apps, I went into recovery without a hitch. It was only after installing this one through GooManager per the instructions. It downloaded, rebooted and flashed and rebooted back to Android (Team EOS3 JB #57). After a few minutes I rebooted to recovery from the Power menu in EOS3 and as soon as the blue curtain raised it was wiping my data partition - /data/media. Of course, I didn't expect that and didn't get any chance to stop it. I know I read somewhere before that open recovery wasn't working on the TF101, but since this was new and it was recommended to use open recovery, I just assumed that meant it was now working. Oh well, all is well now.
never mind i figured it out, open recovery only works with internal for now.(it may be because TWRP-2.2.1.4 is mounting the micro SD as /sdc instead of /storage/sdcard0) I moved the goomanager folder to /data/media updated the download folder location in the goomanager app settings to /data/media/goomanager re-ran flash roms from the goomanager apps made my selections and order to flash and selected wipe Cache and Dalvik and it ran just fine, it rebooted to recovery, flashed all the zips(including my mods) in the proper order and booted back up with no issues.
Running EOS3-N58 at this time.
Dam sweet once i figured it out!
Great job!
Thanks
cbrox said:
never mind i figured it out, open recovery only works with internal for now.(it may be because TWRP-2.2.1.4 is mounting the micro SD as /sdc instead of /storage/sdcard0) I moved the goomanager folder to /data/media updated the download folder location in the goomanager app settings to /data/media/goomanager re-ran flash roms from the goomanager apps made my selections and order to flash and selected wipe Cache and Dalvik and it ran just fine, it rebooted to recovery, flashed all the zips(including my mods) in the proper order and booted back up with no issues.
Running EOS3-N58 at this time.
Dam sweet once i figured it out!
Great job!
Thanks
Click to expand...
Click to collapse
I had already flashed EOS3-N58, but had changed some files experimenting with getting Polaris Office to work and gave up. So, I followed your suggestion and moved a few other files that I normally flash along with the ROM and it worked like a charm. Pretty nifty. I setup the order to flash for EOS3-N58, gapps, Guevor kernel, nVidia codecs, iobusy, and DSP Manager along with the preliminary cache and Dalvik cache wipes and it just worked like you say. Thanks. I hadn't tried that feature yet, mostly because until now I thought it might break something since I had read that open scripting wasn't working yet for TF101 somewhere. I can say now, with this recovery and your change to the download folder, that it is working and working well. You just have to have whatever files you want to flash in that folder (or maybe just somewhere in /data/media) and you're good to go.