Hello,
this ROM is designed for the Acer Iconia Smart. Acer's latest flagship Androphone.
All credits goes to Vache for making this great ROM !
Here is the changelog from Vache :
Code:
T1
Based on Acer_S300_1.000.19_EMEA-GEN1
Rooted
Busybox, nano, bash...
Unsecure boot (adb remount)
semiTransparent notif
Transparent dock background
removed pagination bubble on the homescreens
Stock Lockscreen
Disable Debug USB icon
Smoother Launcher transitions
Disable camera sound
disable some useless Acer services
Removed many apps
Added TerminalEmulator
Updated all apps
SD speed tweak
Lowmemkiller tweak
Zipalign at boot for new apps
Using Google DNS
Removed craps on homescreen (widgets)
Added SpeechSynthetizer
Network tweaks
Ice Cream Sandwich bootanimation
Added compatibility swith in Settings app
Disable some animations
Disable bubble tooltip at first start
Added GoLauncher & LauncherPro (edited to fit the screen)
Added EStrong File Exploer and Task Manager
T2
Fix Phone.apk FC when calling
Fix /data mount during flash
...
T3
Fix WiFi error
AOSP Dialer
T4
Fix HotReboot when installing app that can be move to SD
ICS Market v3.2
T5
Fix typo in the update script
Back to stock Music (for notification widget)
Removed nemoPlayer
Updated SU binary and app
Updated Terminal Emulator
Updatd Youtube
ICS UI sounds
ICS Theme
T6
Removed GooglePlus 2.0 (make the contact FC when FB sync is active)
Fix Google Account disappear after some reboots
T7
Added TabooTools for Iconia Smart
Easy change Acer/Stock Contact/Lockscreen/Notifications
Updated SU binary
Fix TalkBack Keyboard FC
T8
Fix SU binary
Fix Acer Contact file name
T9
Modded hosts file for ads filter
Updated VoiceSearch
More ICS theme for framework and apps
T10
Fixed GPS and Batterie icons
Fixed ICS progress bar
Optimized automatic LCD backlight values
Added 1% batterie step in the framework
Added QuickSettings for stock notif
Fix notif switching from TabooTools
Even more ICS theme
T11
Fix Fast Dormancy
Custom kernel with OC/UV (up to 1.9Ghz)
Requirements :
- Acer Iconia Smart... obviously
- Acer drivers available HERE
- CWM recovery files for Iconia Smart. HERE
I) First Step
Update to latest Acer revision available HERE
WARNING this update will erase all your data
II) Install the custom Recovery
Plug your Iconia Smart to your PC.
Unpack the zip file containing the recovery.
Execute install_recovery.cmd and just follow the steps.
III) Preparing
Copy the ROM ( Smartoonay-1.0.zip) to your sdcard (this has to be an external sdcard, not the phone memory).
IV) Almost there
Switch off the phone and boot to recovery by pressing [vol+] + [focus] + [power]. Keep pressing the buttons until you're in the recovery (yellow text on black screen)
(You get "focus" by half pressing the camera button).
V) WIPE !
Once in the recovery choose "wipe data/factory reset" and validate (pressing camera button).
Also "wipe cache partition"
And then in "Advanced" choose "Wipe Dalvik Cache"
VI) Installing the ROM !
Go back to home menu of the recovery, choose "install zip from sd card" then "choose zip from sdcard". Find the file Smartoonay-1.0.zip (you just copied it on your sdcard) and validate to launch the installation.
Once done just reboot the phone and you're good to go !
You have just convinced me to buy this phone. I was torn between this and the Note, it's refreshing to see some Development on this.
Thankyou very much, your instructions are excellent BTW!
FYI, for me it worked once (after reset) and then went into a bootloop after installing this rom. Never got into fixing it as Vache did not respond anymore... you haven't had that issue?
Regards,
Nika.
Hi,
It bootloops on the bootanimation ? It can happen and usually it works if you remove the battery for 5min.
Can you describe where it stopped working and what you did just before it bootlooped ?
I haven't tried removing the batt, it just bootlooped after my first softreset in the morning. I did try several times, tried resetting all caches, and then reverted back to 1.000.19 eventually and gave up...
I may try again soon... too much work right now
Regards,
Nika.
Going to give it a go this evening.
Really excited to try it out.
So how did it go ?
In my case it keeps displaying the Acer / Android logo... it does not boot (just Android logo)...
Thank´s for me works well
Well...I have tried like 10 times, still nothing.
I started by installing cwm & making a backup (good step to add to your steps in the OP). Then I started install of smartoonay:
1. install 1.000.19
2. boot 1.000.19 once (& configure next, next, finish)
3. install new cwm
4. factory defaults from cwm
5. clear cache from cwm
6. clear dalvic cache from cwm
7. install smartoonay from cwm
Boot wail stop at the acer/android screen (with the 3 green androids).
I have tried fact/def from vol+/- and from cwm. I have tried clearing caches before and after smartoonay. I've downloaded smartoonay rom from vache several 3 times to make sure it's not a faulty rom... nothing...
Restored the backup: everything fine again...but still no smartoonay
Regards,
Nika.
Sorry to read that it doesn't work for you. Have you tried with the .24 official update? It did work for several people.
If it still doesn't work you might have to wait for a next release from vache that will take the smart to a new level ;-)
paugustin said:
Sorry to read that it doesn't work for you. Have you tried with the .24 official update? It did work for several people.
If it still doesn't work you might have to wait for a next release from vache that will take the smart to a new level ;-)
Click to expand...
Click to collapse
Downloading now:
http://global-download.acer.com/GDF... SMART (S300)&OS=a06&LC=nl&BC=Acer&SC=EMEA_18
Regards,
Nika.
Nope... for whatever reason it doesn't work for me.
1. Install .24 version (link see above)
2. Install cwm (4.0.0.8 version from S300-recovery.img 14/07/2011)
3. factory defaults from cwm
4. clear cache from cwm
5. clear dalvic cache from cwm
6. install smartoonay from cwm
Still only see my little Android friends
That's disapointing. Keep yourhopes up as Vache is working on a whole new ROM for the Iconia Smart. It's time consuming but it's going forward and it should be worth the wait
For the current ROM I think we tried everything (removing the battery and all) already and it might be an issue with you model.
paugustin said:
That's disapointing. Keep yourhopes up as Vache is working on a whole new ROM for the Iconia Smart. It's time consuming but it's going forward and it should be worth the wait
For the current ROM I think we tried everything (removing the battery and all) already and it might be an issue with you model.
Click to expand...
Click to collapse
I really hope he's able to give us something that'll work on all devices! I love Vache's work and was really disappointed when the only custom ROM we have didn't boot.
FloatingFatMan said:
I really hope he's able to give us something that'll work on all devices! I love Vache's work and was really disappointed when the only custom ROM we have didn't boot.
Click to expand...
Click to collapse
It doesn't work on yours either? Did you try it? Remember my device has a defect (touchscreen top is defective), so possibly it works on yours... (and I really did everything I can think of, including formatting system, etc., manually)...
My S300 also stuck in booting screen (Acer logo with 3 android idol) after flash the Smartoonay ROM...
I forgot backup my ROM before flashing it, does any one can help me how can flash back the official ROM without backup?
nikagl said:
It doesn't work on yours either? Did you try it? Remember my device has a defect (touchscreen top is defective), so possibly it works on yours... (and I really did everything I can think of, including formatting system, etc., manually)...
Click to expand...
Click to collapse
I actually had it before general release. Alas, my device just hangs until I take out the battery. Shame really, the root & cwm part worked great.
edmundtsang said:
My S300 also stuck in booting screen (Acer logo with 3 android idol) after flash the Smartoonay ROM...
I forgot backup my ROM before flashing it, does any one can help me how can flash back the official ROM without backup?
Click to expand...
Click to collapse
Hi edmund,
Just download the official ROM from somewhere (OS_Acer_1.000.24.EMEA.GEN1_A23G_S300), see above post. Or find yourself another ROM (I also used EUUs_Acer_S300_1.000.19_EMEA-GEN1_01.05.00 in the past, just google for it).
Connect your device with USB and install it using the setup.exe in the download.
In my case the installer crashed btw, because I have the android sdk installed which has a newer (incompatible) version of adb. Just make sure the PATH variable does not contain the ADB.EXE (use "for %I in (adb.exe) do echo %~dp$PATH:I" to figure that out).
Good luck!
Regards,
Nika.
Dear all,
I have been trying to get this ROM going but still no success.
I have compared the two boot images, and they are almost the same. It looks like it should be possible to run the Smartoonay rom with the stock boot image. That gives the highest success as well, because when I try to use the default Smartoonay rom it will get stuck at the first Android page (so it never shows the ICS boot animation). I also tried using the Smartoonay boot image with the stock ROM, but it then also gets stuck at the Android screen (see above image)
When I use the stock boot image, it finally displays the ICS boot animation, but it will get stuck in a bootloop. Usually caused by not clearing cache and such, but no solution in my case.
When I look at recovery.log, I do see one thing that I've never seen before:
Code:
Formatting /system...
[COLOR=Red][B]mtd: not erasing bad block at 0x08e00000[/B][/COLOR]
Done.
I wonder whether this one bad block may be the cause?
Anyone any other suggestions? Or maybe some instructions (a kitchen???) on how to make a new ROM like Smartoonay did? Any new Smartoonay ROMs to look forward to?
Regards,
Nika.
---------- Post added at 10:22 AM ---------- Previous post was at 10:16 AM ----------
FloatingFatMan said:
I actually had it before general release. Alas, my device just hangs until I take out the battery. Shame really, the root & cwm part worked great.
Click to expand...
Click to collapse
By the way... I fixed my screen by getting a new Touch Screen Digitizer for Acer S300 Iconia Smart Device is difficult to take apart (first take off top cover where the power button is in, which is a flat plastic, then take the screw out, then take the entire top cover off, remove two screws, open battery department cover, remove battery & screws, and then you can use a soft plastic pull tool to take the screen out...)
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 ?
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
So here we go I can say finally I managed to produce firs custom rom for our beloved HTC One S C2 (I called it this way cause that is how on gsmarena.net is presented). If we ever get a sub forum this is how I suggest it is called. It is not very special rom, but it is a start. cause I don't like bloatware on my phone, I've tried to remove as many unnecessary stuff as I could remember, and I could miss.
Since this is my very first rom I've build with kitchen (for public use at least), don't be to harsh on me. I will try to improve it, and remove even more sens components, cause I just prefer stock experience.
You will need android sdk on you computer (you may know it as adb shell)
REQUIREMENTS
Unlocked Bootloader and Root access
TWRP Recovery
INSTALLATION
1. Download the ROM, extract only boot.img where you have android-sdk installed installed in folder platform-tools
2. Make a backup of your apps with Titanium backup or other similar app (so that you can restore them after flashing my rom)
3. Boot into Recovery (with GooManager, or restart phone and hold volume down, when in fastboot choose recovery with volume down and press power button)
4. Make a BACKUP in recovery!
5. WIPE! Do a factory reset and System wipe
6. "install zip from sdcard"
7. "choose zip from sdcard"
8. Flash the ROM
9. Go back to the main menu of recovery, choos reboot, and then reboot to bootloader.
10. Flash kernel with Command prompt (go into direcotry where you have extracted boot.img) and run:
(step by step guide)
Short version:
Code:
fastboot flash boot boot.img
fastboot erase cache
fastboot reboot
11. Wait until android boots up, it will take a few mintues (5-10), because it is deodexed, but only first boot takes longer after that it is normal.
What is working:
Since this is sense based rom all the functionality should work (calling, texting, mobile data, GPS, wifi, bluetooth, camera, etc)
POSSIBLE PROBLEMS:
- There might be some reports of some services stop executing, this is nothing to worry about, it would just be something that I have removed cause it is only sens based and drains battery, but it should impact with phone experience.
- Due to all HTC widgets removal, not all the lockscreen options are functional (like people).
FUTURE:
I hope I'll have time and the will to make this rom to look and feel almost as an AOSP based (that is with statusbar, lockscreen, dialer, settings, etc). But I am still learning so don't expect to much. If there is themer among you or modder, I would really apperaciate some help with this stuff. Together we can make this something ! I would also need some mirror if this rom will become popular.
WARRINING:
This rom is for HTC One S with S3 processor only!!!
Flashing any kind of custom rom voids your warranty, and it could brick your phone. I am not responsible if this happens to you. So you flash this software completely at your own risk!
That being said here is the download link.
BackToBasics_v1
BackToBasics_v2:
(you have to downloade both rar files in sam folder and then extract from .part1, it will extract flashable .zip)
PART 1
PART 2
BackToBasics_V3
If you are coming from lower version of this rom, just make backup, wipe cache, flash rom and you are good to go. No need to factory reset (data wipe) or system wipe in this case
THANKS TO:
- dsixda for his amazing rom kitchen
- torxx for his update-binary and updater-script
- Chainfire for SuperSU
- PaulOBrien for his superboot, which provide us root
- Tesla Coil software for Nova Launcher
- Estrogen Inc. for File explorer
- everyone else that makes this community so good!
If I forgot somebody important please forgive me and let me know, I will immediately add him or her.
[ROM][S3] BackToBasics_v2 (based on RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.110)
About rom:
v3:
- HTC Lockscreen widgets enabled (People, Weather, FriendStream, etc)
- HTC Locksreen shortcuts re-enabled with application Lockscreen Shortcut (thanks to itandy)
- Added missing Gallery
- Updated SuperSU an Su binary
- Updated ES File Manager
- Added GooManager for easy rom flashing and backing up
v2:
- root access now works
- WIFI problem solved
- Camera problem solved
- added Busybox free application
- removed boot sound (it really annoys me)
v1:
- Based on RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.110
- All originally included languages are in there
- Deodexed
- Zipaligned
- Rooted with SuperSU
- Added busybox run parts
- Removed Rosie launcher and replaced with Nova Launcher (free version)
- Included ES File Explorer
- Insecure boot.img (stock kernel) -> adb shell root enabled
- A lot of build.prop tweaks
- Added /data/app/ functionality
- /etc/init.d script support
- custom bootanimation support (but for now I've kept original boot animation)
- 95 removed apps (all sens widgets and other stuff)!
Congratulations for the first S3 rom :]
EDIT: I noticed that you didn't claim two posts. So if you need to expand the content to this post just send me a PM and I will add it to this post erasing my content.
thx!!!
downloading
haha that's very good
hohoho
very nice to see an s3 rom get here!
Qzem, you should include some screenshot in first post.
oww .. what i should say ??? CONGRATZ TO OUR S3 DEVICE !! :laugh:
Thanks for the share.. works great.
I having a super hard time connecting my wifi ... stuck at obtaining IP address all the time !!
Down not working from dropbox
Sent from my HTC One S using xda premium
Alright , I found a solution for wifi obtaining IP address problem .
This is just a temp way to do it .
go to ur specific wifi , long press it . Click show show advance option . and choose static IP . Key in the data .
It connect successful . qzem , try to find what is the problem for cant obtaining ip automatically . It would be quite suffer when wanna use public wifi
waint for a link to download
Problem at my devices :
1) Can't save picture after took picture using camera app .
2) superusers got problem , can't get permission for the apps .
3 ) wifi cant get ip address automatically . ( have to manual set up static ip )
I will get to debugging and trying to fixing problems on monday,cause I am on camping for weekend with my buddies .
Sent from my HTC One S using xda app-developers app
Any chance its possible to remove the 3 button menu and remap menu to long hold home?
Sent from my HTC One S using xda premium
onlinechi said:
Any chance its possible to remove the 3 button menu and remap menu to long hold home?
Click to expand...
Click to collapse
Is this mode available for One S? This would be first thing I would like to change for sure :good:
There is some info HERE
Try this WIFI fix and report if it works. I am gonna test soon. And if it does I will include it in next version.
banesi said:
Is this mode available for One S? This would be first thing I would like to change for sure :good:
There is some info HERE
Click to expand...
Click to collapse
I can include this, but I will read a little more, to see if it is worth it.
EDIT: Good news I've solved WIFI and root problems. Will upload new build tommorow, cause I most probably I won't have enaught time today.
New version is up!
I suggest you to change thread caption to v2, and to move up changelog for v2.
STOCK ANDROID 6.0 MARSHMALLOW ROM
FOR THE LENOVO TAB 3 8"/TB3-850F
TWRP FLASHABLE ZIP
FORCE ENCRYPTION & DM-VERITY DISABLED
DISCLAIMER: Your warranty will be voided by installing this ROM, unlocking your bootloader, or flashing a custom recovery. You hereby assume sole responsibility for any positive or negative consequences incurred by flashing this ROM. As always, flashing your Android device or otherwise altering its file system & partitions involves an inherent risk. I am not responsible for any devices which are bricked or otherwise rendered inoperable as a result of flashing this ROM. However, in such scenarios,
I will provide all support feasibly possible. Follow the simple instructions carefully and you should experience no adverse affects.
Lenovo's open source code for this ROM encompasses both the 850F & 850M variants of this tablet. Therefore, this ROM should be completely compatible with the TB3-850M as well.
NOTES:
This Stock Android 6.0 ROM is virtually unmodified. However, it should be noted that dm-verity (device mapping) and force encryption have been disabled via patched boot image. This is the most current stock OS for the Lenovo Tab 3 8"; therefore, no OTAs will need to be installed subsequent to flashing this ROM. In order to ensure that force encryption gets disabled, it is imperative that the /userdata (Data) partition is formatted in TWRP prior to Installation. Please carefully follow the below instructions.
For those members who want a pure stock experience, but also want root access of the stock OS, I'm currently compiling a deodexed & zipaligned version of this ROM, fully rooted with Magisk 14.0 & BusyBox binaries pre-installed.
SPECIFICATIONS:
Android Version: 6.0 Marshmallow
Build No: TB3-850F_S100031_171010_ROW
Kernel Version: 3.18.19
SDK Version: 23
Software Version: TB3-850F_160412
Build ID: MRA58K
Android Security Patch Level: 9/05/2017
Runtime Version: ART 2.1.0
Hardware Version: LenovoPad TB3-850F
Board Platform: MediaTek MT6735M
CPU: 64-Bit, Quad-Core Cortex A-53 - 1.0GHz
GPU: Mali T720 - 450MHz
RAM: 1GB
OS Build Date: 10/10/2017
Source Code: http://pcsupport.lenovo.com/us/en/products/tablets/a-series/tab3-8/downloads/ds112711
REQUIREMENTS:
1. Unlocked bootloader;
2. TWRP recovery;
This is a pure stock, unmodified, TWRP flashable Android 6.0 Marshmallow ROM for the Lenovo Tab 3 8". This ROM was compiled from the most recent stock /boot and /system images. However, as noted previously, the boot image has been unpacked, patched, and repacked in order to disable dm-verity and force encryption. Because raw firmware images were used in compiling this ROM, the file size is in excess of 1GB (approximately 1.35GB).
INSTRUCTIONS:
1. Download the ROM from the link provided and save it to your external micro SD card. Do not save to internal storage, as your /data partition will need to be formatted prior to installation;
2. Boot your tablet into TWRP recovery;
3. Wipe /system, /data, /cache & /Dalvik-ART cache. Also, select "Wipe", then "Format Data." This step is crucial to ensure disabling of force encryption. Please note that once installed, you may go to SETTINGS>>SECURITY and opt to encrypt the userdata on the tablet;
4. Select INSTALL, navigate to the location in which you saved the ROM zip file, and initiate installation. Flashing will complete in approximately 3 - 4 minutes;
5. Reboot system.
You should now have unmodified stock Android 6.0 installed on your Tab 3, as well as disabled dm-verity and disabled force encryption.
DOWNLOAD LINKS:
Stock Android 6.0 ROM --
TB3-850F_S100031_171010_ROW: https://drive.google.com/file/d/1iMf0Ns_XWGpYlNmXCvUsW_1DfaRMeIuO/view?usp=drivesdk
Stock Recovery Image: https://drive.google.com/file/d/1D6A7b080luzsSf0xLJSCqPBNeQLSWo94/view?usp=drivesdk
Unpatched Stock Boot Image: https://drive.google.com/file/d/1azgIrPbfJHBzZF9R4IUMxIGNga6vjipD/view?usp=drivesdk
Lenovo File Manager (APK): https://forum.xda-developers.com/android/general/app-lenovo-file-manager-lenovo-tab-3-8-t3706161
Lenovo Tab 3 8" User Guide --
TB3-850F & TB3-850M (English)(PDF): https://drive.google.com/file/d/18gCTfuZecJnlB0ddBIN02YPaDpuvmzov/view?usp=drivesdk
Older Build(s):
TB3-850F_S100030_161209_ROW: https://drive.google.com/file/d/0B1Sfod4HWfk2aTNtVmJHZGpWZEE/view?usp=drivesdk
BUGS: Please report any and all bugs, no matter how seemingly trivial or insignificant. For those members with the knowledge, please submit a proper bug report. If you are not sure how, simply provide as many facts & details as possible. If you are having problems with apps, please specify as to whether the app is from Google Play. Also, please DO NOT submit bug reports unless you are utilizing this ROM in its present form -- unmodified, pure stock. Custom kernels, mods & tweaks (e.g. Xposed framework) & any deviations from pure stock will make it futile to analyze bug reports. Instead, provide with detail the precise nature of the problem. If reporting a bug, please specify if you are rooted (systemless or system-mode) and/or have BusyBox binaries installed. Submit screenshots of bugs if possible.
Brilliant! Will download now and report back later. Thank you.
My custom ROM for this tablet should be coming out of the Android Kitchen later this evening. I've dubbed it Ethereal OS v1.1 [Android 6.0.1]. Extremely lightweight yet moderately feature packed.
MotoJunkie01 said:
My custom ROM for this tablet should be coming out of the Android Kitchen later this evening. I've dubbed it Ethereal OS v1.1 [Android 6.0.1]. Extremely lightweight yet moderately feature packed.
Click to expand...
Click to collapse
Nice!
After flashing the stock zip TWRP says unknown error. It booted up fine to where you login to your gmail and "bluetooth sharing has stopped working" pops up. Bluetooth can not be turned on within settings. I can not double swipe down to get to the notifications and the "Home" and "Recents" buttons do not seem to work although they both vibrate when pressed.
I will flash stock with SPFT and try your stock rom again.
stonedpsycho said:
Nice!
After flashing the stock zip TWRP says unknown error. It booted up fine to where you login to your gmail and "bluetooth sharing has stopped working" pops up. Bluetooth can not be turned on within settings. I can not double swipe down to get to the notifications and the "Home" and "Recents" buttons do not seem to work although they both vibrate when pressed.
I will flash stock with SPFT and try your stock rom again.
Click to expand...
Click to collapse
I got the same error with Bluetooth Share force closing two times at the setup screen. Probably a corruption issue during archiving the ROM. I'll do an md5 and archive the ROM again.
Seemed to work, however the loading images and screen is still lenovo. Also they lenovo apps are still there.
rongallant said:
Seemed to work, however the loading images and screen is still lenovo. Also they lenovo apps are still there.
Click to expand...
Click to collapse
This is not a custom ROM. This is pure stock. The Lenovo boot logo, boot animation & apps are supposed to be there. Like the title implies this an "Unmodified" stock ROM.
MotoJunkie01 said:
This is not a custom ROM. This is pure stock. The Lenovo boot logo, boot animation & apps are supposed to be there. Like the title implies this an "Unmodified" stock ROM.
Click to expand...
Click to collapse
My bad, understood.
On another note, I am finding it very buggy. The home and overview buttons do not work. They show you clicked it along with the haptic feedback, but nothing happens. The back button works and is the only way I know to get back to the home screen.
Also the tool panel you pull from the top stops working after a little while until I reboot. Then works for a little while.
The Play store downloads barely work. They show pending and nothing happens. I force quite, cleared the cache, disabled, reverted to the stock app and it works for a little bit. Then the other Play Store app comes back. Anyways, I am not complaining. I appreciate the work you put into this. It's awesome we get to do it at all. Just giving my feedback. P.S. It's a new TB3-850F.
rongallant said:
My bad, understood.
On another note, I am finding it very buggy. The home and overview buttons do not work. They show you clicked it along with the haptic feedback, but nothing happens. The back button works and is the only way I know to get back to the home screen.
Also the tool panel you pull from the top stops working after a little while until I reboot. Then works for a little while.
The Play store downloads barely work. They show pending and nothing happens. I force quite, cleared the cache, disabled, reverted to the stock app and it works for a little bit. Then the other Play Store app comes back. Anyways, I am not complaining. I appreciate the work you put into this. It's awesome we get to do it at all. Just giving my feedback. P.S. It's a new TB3-850F.
Click to expand...
Click to collapse
Yes. Very buggy indeed. I have determined that the bugs are due to corruption during the unpacking of the system image. I'm repacking the ROM now to alleviate the bugs. Thanks for your input...
I've managed to fix the major bugs reported upon initial install of the ROM -- Recents & Home Buttons, Quick Pulldown Menu, Google Framework bugs, New App Shortcut bugs, etc. Simply corruption during packing (archiving) the ROM zip. I will try my best to get a new build posted sometime today.
MotoJunkie01 said:
I've managed to fix the major bugs reported upon initial install of the ROM -- Recents & Home Buttons, Quick Pulldown Menu, Google Framework bugs, New App Shortcut bugs, etc. Simply corruption during packing (archiving) the ROM zip. I will try my best to get a new build posted sometime today.
Click to expand...
Click to collapse
Dear MotoJunkie
İs it possible to upload stock Fm Radio Aplication(offline radio) of Tab3 8? İn my Turkish model, theres no Fm radio aplication. I need it to use tablet in my car.
Thanks
MotoJunkie01 said:
I've managed to fix the major bugs reported upon initial install of the ROM -- Recents & Home Buttons, Quick Pulldown Menu, Google Framework bugs, New App Shortcut bugs, etc. Simply corruption during packing (archiving) the ROM zip. I will try my best to get a new build posted sometime today.
Click to expand...
Click to collapse
Did you get around to uploading it? I am unable to use the OTA update file. Says its missing 'android-info.txt'
Also, anyone care to point me to a way to get back to stock/unrooted?? Nooooo, I didn't backup my ROM first. That would have made way to much sense.
I've been out of commission, unfortunately, due to impending health issues once again. I know that hospital food sucks, that the pretty nurses don't typically put out easy, and that the hospital WiFi restrictions can easily be bypassed with a proxy server address. Lol. And that's all I've learned in the past ten days. Anyway, hope to be back in my daily routine in the next day or so and finishing some stuff up for this device.
Hi, is this thread alive? I'm interested in solution because i have about 60 tablets and need a solution to clone form one source tablet (config, apps, wlan, users, etc.) to other 59. I have tried adb backup --twrp and it went ok, but when i tried restore it gave errors with system partition and now i can only recover tablet with factory ROM from this thread (but it is buggy and cannot put it int to production like this). Is it possible to create system rom from other working tablet? Iwill be very pleased If You can write step by step, how to create zipped rom from working device so i can then upload it to share with others.
spiker_80 said:
Hi, is this thread alive? I'm interested in solution because i have about 60 tablets and need a solution to clone form one source tablet (config, apps, wlan, users, etc.) to other 59. I have tried adb backup --twrp and it went ok, but when i tried restore it gave errors with system partition and now i can only recover tablet with factory ROM from this thread (but it is buggy and cannot put it int to production like this). Is it possible to create system rom from other working tablet? Iwill be very pleased If You can write step by step, how to create zipped rom from working device so i can then upload it to share with others.
Click to expand...
Click to collapse
The thread is alive and I'm currently ironing out the errors on the posted ROM. The errors are due to a couple of permissions which are omitted on my updater-script file. I'll be posting an updated and hopefully error free release this week. Thanks for your interest and sorry for the delay in development. I've had a number of health issues of late and I'm now recovering.
Problem after wiping /system
Hi,
I´m new right here. I bought a new TB3-850F and wanted to flash the Original Stock Rom. After opening the Bootloader and booting into twrp like this way https://forum.xda-developers.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786 I wiped the /data /System /dalvic and /Cache. After that I rebooted the system.
But it only shows after starting the Lenovo-Logo. No more booting. Because of this I can´t start the fastboot modus with Minimal ADB and Fastboot.
Is there some idea how I can boot into fastboot?
Many thanks for your help,
sailor1977
sailor1977 said:
Hi,
I´m new right here. I bought a new TB3-850F and wanted to flash the Original Stock Rom. After opening the Bootloader and booting into twrp like this way https://forum.xda-developers.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786 I wiped the /data /System /dalvic and /Cache. After that I rebooted the system.
But it only shows after starting the Lenovo-Logo. No more booting. Because of this I can´t start the fastboot modus with Minimal ADB and Fastboot.
Is there some idea how I can boot into fastboot?
Many thanks for your help,
sailor1977
Click to expand...
Click to collapse
I´ve got a solution: After powering down, press power, wait 1 sec then hold both vol up & down also (all 3 Buttons) until vibrates. After starting in recovery Modus hold power button und press once the vol up.
With help of: https://forum.xda-developers.com/android/help/lenovo-tab3-8-2016-custom-recovery-t3483454 post #66
Ok. I've debugged the Stock 6.0 ROM in the OP. Fixed the Bluetooth force close issue at startup and the bugs involving the hardware buttons and the pull down menu. I'm traveling for work at the moment. Soon as I'm back home Monday I'll post the fixed build in the OP.
MotoJunkie01 said:
Ok. I've debugged the Stock 6.0 ROM in the OP. Fixed the Bluetooth force close issue at startup and the bugs involving the hardware buttons and the pull down menu. I'm traveling for work at the moment. Soon as I'm back home Monday I'll post the fixed build in the OP.
Click to expand...
Click to collapse
Cheers buddy. Good stuff ??
@Hemphiz, I hope all is well my friend. Something I wanted to get your input on. It seems that a few members have been experiencing boot loops and other problems after following the TWRP & Root thread I revised. I'm sort of at a brick wall in terms of figuring out what's going on. I'm thinking that maybe there are regional variants that are incompatible with the TWRP we use. Or, it could be one of those situations where instructions are not being closely followed. What are your thoughts? Thanks.