Related
Nothing to see here.
Original Post Gone. Formatted and tweaked original instructions. Original post by Croak can be found quoted at the bottom of page 8. Please read entire post before asking any questions. All credit goes to Da_G.
This is ONLY for the SGH-i957 and SGH-i957M (Bell).
WARNING: THIS WILL TRIP YOUR FLASH COUNTER [aka VOID WARRANTY]
NEXT WARNING: USE OF ODIN CAN DAMAGE YOUR DEVICE IF USED INCORRECTLY. WE ARE NOT RESPONSIBLE FOR ANY DAMAGE DUE TO FOLLOWING THESE INSTRUCTIONS. PROCEED WITH CAUTION.
Steps:
1. Download and Install the Samsung Drivers for your device. Install Kies, or the latest mobile drivers.
http://forum.xda-developers.com/showthread.php?t=961956
2. Download Da_G's overclock kernel.
http://www.ponack.net/TPC/dagnarf/sgh-i957-oc-kernel-dag-1944mhz.tar
3. Download Odin 1.85
http://www.multiupload.com/0EMX1J7RZJ
3. Open Odin 1.85 as administrator
4. Place the OC kernel .tar file in the PDA slot. (Make sure you do not have any boxes in the options panel checked besides the ones that were checked when opening the program - should only be auto reboot and f.reset time)
5. Place the tablet in download mode. Hold vol up + vol down and hold power until the device powers on into download mode. Hit volume up to proceed after the warning screen
6. Plug the tablet into the computer on a main usb slot and it will be detected by Odin in one of the ID:COM slots (will appear as yellow)
7. Hit Start - the OC kernel should will be flashed to the tablet. Tablet will restart.
8. Go into market and download NoFrills
9. Set Max. Clock Freq. to 1.728, 1.782, 1.836, 1.89, or 1.944 GHz. Set your min clock speed to 192 MHz if desired. If you run into problems, set your I/O scheduler to noop instead of cfq. DO NOT CLICK 'APPLY ON BOOT' UNLESS YOU HAVE THOUROUGHLY TESTED THE STABILITY OF THE DEVICE AT THE SET GHz!!!
If you are unhappy for any reason and wish to go back to stock kernel - you can flash the stock kernel back using steps 3-7 above with the below file.
http://ponack.net/TPC/dagnarf/stock-kernel-odin-image-for-sgh-i957.tar
If you are still experiencing instability at any speed above 1.566 GHz, there are certain .so files (libhardware_legacy.so, librpc.so, and libtalk_jni.so) which limit speeds and can override the OC sometimes. Da_G modified these files which can be pushed to the device through adb commands. I won't explain how to get ADB working, it can be found on XDA elsewhere.
Link to .so files
http://www.ponack.net/TPC/dagnarf/moddedfiles-i957.zip
ADB Commands (do the following once for each file in the .zip):
adb remount
adb push filename.so /system/lib/
adb shell
chmod 644 /system/lib/filename.so
Click to expand...
Click to collapse
Edit by Da_G: Here is a link to the requisite source, always up to date! https://github.com/dagnarf/i957kernel
_________________________________________________________
Credits:
Huge thanks to Da_G for doing ALL of the work on the OC kernel without owning the device. And also for hosting the files. Please Donate to him.
Croak for being the first to test!
Nothing to see here either.
Hi. edited the first post with a link to the requisite kernel source at the bottom, don't want to violate GPL now do we! Source is up-to-date with the current v4 release!
After flashing the kernel 4G would not work, so I turned on wifi and had a device reset.
Next reboot, wifi was on, i turned it off to enable 4g and device reset.
third reboot everything acted fine.
quandrant crashes right after score readout.
@ 1836 - setcpu crashed when setting an OC voltage. reboot. cpu spy caused device reset after OC. reboot.
@1784 - device crash during quadrant
@1728 - device crash during quadrant
@1836 - linpack crash.
Is this still on?
yea that may have been the issue. ill try that.
Croak/Da_G,
So tonight I was messing around with the OC settings using Antutu and all lower freqs. seemed to work fine so I pushed the envelope to 1944 mhz. and my Tab most certainly did not like that setting. It now will boot into the Home screen but immediately freezes and reboots. I can't even turn it off as it freezes when I try to power off. So if I reflash D's kernel will that wipe the CPU Master settings or do I have to go as far as Odin the stock rom we got last week??? Obviously we need to stay below the 1944 setting......hehehehe!
P.S. I also added D's lib files. I renamed the Legacy file as .bak and left it in the folder so i can restore that one I suppose if need be.
Edit: I fixed it by flashing the stock kernel again. Gonna try the OC again tomorrow as it did seem to be snappier with that running. Just have to stay away from over-OCing the darn thing. Had to try just out of curiosity now i know.
Going down the memory hole.
I guess you definitely have to push those lib files for this to work
Sent from my SAMSUNG-SGH-I727 using xda premium
When you use ADB to push the files where do you put the files that you want to push to the device? Do I have to change to that directory or do I have to copy the files to the directory where ADB is loaded from? I tried using ADB to push them but couldn't get it to go? So I ended up using Droid Explorer to copy them to the device then I set permissions using Root Explorer.
Whooooooosh.
There is a graphical program called qtadb which may work well
Sent from my SAMSUNG-SGH-I727 using xda premium
I am a little confused here.
So after following the root method, which flashes the Da_G root kernel, can the device be manually overclocked with setcpu type apps?
Is the OC kernel just to make it active at boot time?
Or is the OC firmware required to do any kind of OCing period?
You mention your "daily use" is the 1.8 ish, so is there an OC kernel at that speed available?
Hopefully this makes some kind of sense...
When you root the first time you have a modified kernel. You can't overclock. Flash the oc kernel in order to do that.
Sent from my SAMSUNG-SGH-I727 using xda premium
So the "1944MHZ" in the kernel name is just the maximum speed the kernel will allow correct?
modestone said:
So the "1944MHZ" in the kernel name is just the maximum speed the kernel will allow correct?
Click to expand...
Click to collapse
Yes just use setcpu do customize the speed
Sent from my SAMSUNG-SGH-I727 using xda premium
orlandoxpolice said:
Yes just use setcpu do customize the speed
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Right on, so whats the consensus on pushing those files over in ADB, pretty much required for this to really work?
Revisionism is fun.
Croak said:
Yes. When Da_G gets some time, he said he was going to package it all up into one automagic file, but for now you'll need to push the lib files manually.
Click to expand...
Click to collapse
Right-o, think I will probably wait it out, only had the damn thing 16 hours, may as well get familiar with its stock limitations first
Welcome
I wrote this post to help people get their Archos g9 tablet running custom roms. If you have any improvement ideas, please post them so I can make this better source of information.
List of content:
Post 1
What is recovery
What is SDE and how to install it
-Also SDE for 4.0.25
List of most commonly used roms
How to install custom roms
How to install offical rom
How to multiboot android 4.0 based roms
Installing 3G stick and Huawei modems support.
Post 2
Change symlinks/binds.
Installing ADB
Installing SuperCharger
Installing Chainfire3D
But why?
FAQ
Useful links
What is recoveryYou can boot to recovery menu by holding volume- while booting your device. From recovery meny you can calibrate your touchscreen, wipe data and do this kind of stuff. Installing SDE creates new entry to recovery menu, called Special Developers Edition. There you can remove android kernel, flash new, export hdd and data. In recovery move up and down with volume + and -. Select by pressing power button
What is SDE and how to install itSDE is shortened word from Special Developers Edition. After SDE is installed, your tablet is able to boot to official rom, recovery, and SDE rom. Most of the roms advice you to use "Remove android kernel" from SDE before you install kernel. When you remove your android kernel from there and install kernel from custom rom, your archos boots directly to custom rom. If you don't delete it, your device boots to official, but keeping volume - while booting gives you change to boot to SDE.
There are 3 guides how to install SDE. Official SDE watermarks your device for archos (there is no watermark on screen ), so they can detect you have installed SDE in some point. It stays even if you remove SDE. Official way is more safe. Also, it removes "only" software warranty. If your devices powerbutton, Usb-port or etc brokes, you can still send it to warranty. Link to official SDE install guide. Big thanks for Shano56.
Then there is unofficial, a bit more dangerous method. It doesn't watermark your device, but is more complicated. Guide tells that it's outdated, but it worked for me. I used official 4.0.4 version while installing. Link to the guide. Big thanks to Shano56.
4.0.25 Guide, by surdu_petru
surdu_petru said:
Hi !
I uninstalled SDE by mistake yesterday !
...so, you can enable (install) unofficially SDE following this path ( work 100% on firmware 4.0.25 ) :
On your tablet :
check on Settings-> Developer options -> USB debugging on !
connect USB cable ( PC to tablet )
On your PC :
> adb push 1 /data/local
> adb push 2 /data/local
> adb shell
$ chmod 0755 /data/local/*
$ ./data/local/1
$ exit
> adb reboot
> adb shell
$ ./data/local/2
$ exit
> adb reboot
> adb push zimage /data/local/tmp
> adb push initrd.cpio.lzma /data/local/tmp
> adb push abcbox /data/local/tmp
> adb shell chmod 755 /data/local/tmp/abcbox
> adb shell /data/local/tmp/abcbox kd_flasher -k /data/local/tmp/zimage -i /data/local/tmp/initrd.cpio.lzma
( now you have installed unofficially SDE ! )
Flash Root version or other Custom Rom :
> adb reboot
> adb shell rm /data/local.prop
> adb push archos.ext4(.update) /mnt/storage
Go to SDE -> ( check "Reboot" on power off menu , and after a while press & keep volume down until you see SDE menu !)
Go to Recovery System -> Developer Edition Menu -> Remove Android Kernel -> I Undestand -> OK -> Developer Edition Menu -> Flash Kernel & Initramfs -> copy here zImage and initramfs.cpio.lzo appropriate archos.ext4(.update) -> OK -> wait to boot !
Now you have Rot version installed !
Here you will find the necessary files : Enable_SDE.zip
Click to expand...
Click to collapse
List of most commonly used romsThese roms are most commonly used. Most of them are still being developed. I also included link to rooted official honeycomb, because some people have better touchscreen responsibility with it.
ParanoidAndroid 3
Cyanogenmod 10, 4.2 mockup
Cyanogenmod 10
AOKP ROM
[email protected]
Clean_Slim&Fast(Based on official 4.0.25!)
Ubuntu. This requires special kernel, which is compatible with official android 4.0.4Overclockable stock rom
Early CM9
Stock ICS rom with root & busybox
Stock honeycomb with root. (FYI, kernel requires renaming while installing)
How to install custom romsCustom roms have different installing methods, but basic idea is same. You move image file with specified name to specified location.
When coming from stock rom or whengoing to stock rom:
CyanogenMod 10, AOKP, CyanogenMod 9
surdu_petru said:
Installation : Now should be work on all devices Gen9 !!!
...connect USB cable to PC and ( you need to use a Rom with root access ) :
> adb shell
# stop
# rm -rf data/*
# mkdir data/local
# mkdir data/media
# exit
> adb push archos.ext4 /mnt/storage ( need to wait about ~150 seconds ) !
> at the same time do : adb reboot & press and keep volume down ; in SDE -> DEM-> Remove Android Kernel ( if exist ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.gz -> OK -> wait to reboot !
Click to expand...
Click to collapse
[email protected], Ubuntu, Root 4.0.7 Clean_Slim&Fast
surdu_petru said:
Install :
- copy archos.ext4.update(archos.ext4 in case of Clean_Slim&Fast) in /mnt/storage/ , you can use this command > adb push archos.ext4.update(remove .update if Clean_Slim&Fast) /mnt/storage/
- go to SDE -> Developer Edition Menu -> ( Remove Android Kernel if available ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.lzo -> OK! -> wait to reboot .....
- after everything was installed - please reboot your device !
Click to expand...
Click to collapse
Honeycomb
Install like Cyanogenmod and AOKP and others, but rename initramfs.cpio.gz to initramfs.cpio.lzo
How to install official romDownload official 4.0.7 rom from here.
Now boot to recovery (hold volume- while booting) and choose update firmware.
Now there should be noew drive in your pc. Drop the downloaded firmware_archos_it4.aos to there and press ok in recovery. Keep usb plugged in while installing. It should take around 30 seconds to 2 minutes. Now choose ok again. your tablet should now reboot to stock rom.
4.0.24 Official is owrking on some devices, but because it won't work on all, i won't cover it here(yet)
How to multiboot android 4.0 based romsInstall modified initfram from this topic. Use the zimage from the rom you want to multiboot. AFAIK you can multiboot with following combos:
[email protected], Ubuntu (download newer kernel from later pages.), Root 4.0.7
and
AOKP, CyanogenMod 9.
You cant use [email protected] and AOKP because they do not use same kind of data. That means that after you have run first rom, the second will bootloop. That is also why it requires wiping data when changing from stock to aokp and vise versa.
Detailed:
Download dmenu-0.3a.zip, and extract initframfs to desktop. Then download [email protected] and stock 4.0.7 rooted. Extract Image files and zimage from either one of the roms. Now just instal like described in earlier section, while using initframfs from multiboot and kernel from other rom.
Installing 3G stick and Huawei modems support.
Trevd made a package to add 3G stick and extra Huawei modems work for AOKP and generally all ICS ROMs. This guy is awesome because he also made some Huawei modems work.
trevd said:
Hi surdu_petru and AOKP fans.
Great work as always, It's not a rom i'll ever use but It's the first time I've loaded an AOKP Rom, I like notification layout, I'll be having that away for my own personal rom Anyway I was more just passing through and noticed 3G was not working yet. As seen as though that seems to be my speciality and preoccupation/addiction for the last 9 months I thought I do something to remedy that situation for you.
Here's an hotfile link to download the update [ 3g-archos-aopk.7z ] this should contain everything you need to get the Archos 3G Dongle, just for ****s and giggles as a extra bonus i've also included the huawei support file as well :good:
Installation:
From a command prompt / bash terminal
Code:
7z x 3g-archos-aopk.7z
adb push 3g /
adb shell reboot_into sde
extracting the 3g-archos-aopk.7z will give youu a 3g directory in you current directory, we then push the contents of the 3g directory to the root direcotry on the device. This operation is recursive.
Have Fun!
What follows is a detailed explanation of what files and modifications are required to add 3G support.
Archos 3G Stick
The changes / additions to add this functionality breaks down like this ; The following required binary's were on the device already:
** /lib/modules/hso.ko is insmod'd by the device specific init file /etc/init/init..rc
Code:
/lib/modules/hso.ko[B]**[/B]
/usr/bin/usb_modeswitch
/system/lib/libtcl-ril.so
/system/bin/rild
/system/bin/pppd
/system/xbin/chat
/etc/ppp/init_pppd_datakey
/etc/ppp/ip-up-datakey
/etc/ppp/ip-down-datakey
/etc/ppp/peers/datakey
/etc/chatscripts/datakey_start
/etc/chatscripts/datakey_stop
/etc/usb_modeswitch/1bbb_f000
The following required services were already defined in the device specific init.rc's located in /etc/init/init..rc ,
*** switch_ms_3g defined by /etc/init/init.archos.rc
Code:
service service switch_ms_to_3g[B]***[/B]
service pppd_secrets
service pppd_datakey
service ril-daemon
So what's missing? you may ask as this pretty much is everything that is needed by the Archos 3G Stick.
Standard Archos Roms use the UsbKeyManager.apk system service to start the switch_ms_to_3g and ril-daemon service's. I replace that with my own ueventd handling native service and add an additional to configuration file keep everything clean
Code:
/system/bin/hotplugd
/init.dongle.rc
I've added the following line to the top of the /init.rc
Code:
import init.dongle.rc
All that is left to do now is enable mobile networks on the rom. I used apktool to decompile the /system/framework/framework-res.apk and change the following values
res/values/bools.xml
Code:
true
true
res/values/arrays.xml
Code:
wifi,1,1,1,-1,true
mobile,0,0,0,-1,true
mobile_mms,2,0,2,60000,true
mobile_supl,3,0,2,60000,true
mobile_hipri,5,0,3,60000,true
mobile_fota,10,0,2,60000,true
mobile_ims,11,0,2,60000,true
mobile_cbs,12,0,2,60000,true
wifi_p2p,13,1,0,-1,true
"1,1"
"0,1"
"7,1"
"9,1"
res/values/strings.xml
Code:
ppp1
Huawei Support
The extend this functionality further I added the following files
Code:
/etc/ppp/init_pppd_gprs
/etc/ppp/ip-up-gprs
/etc/ppp/ip-down-gprs
/etc/ppp/peers/gprs
/etc/chatscripts/gprs_start
/etc/chatscripts/gprs_stop
/etc/usb_modeswitch/ [ numerous configurations files ]
/lib/modules/usb_wwan.ko
/lib/modules/option.ko
/system/lib/libhuaweigeneric-ril.so
We also need to chmod 6755 /system/bin/pppd but that is handled/checked in the /init.dongle.rc so there is no need to do that manually
Click to expand...
Click to collapse
Change symlinks/bindsTrevd wrote guide to let people know how to change binds. That way you can move large folders, like Gameloft games and navigator files to ExternalSD, saving InternalSD space.
trevd said:
If you after freeing up space, it is still possible with a bit of hacking voodoo . There are 2 ways I know of in fact.
METHOD 1 - SDCARD SERVICE
you can point the /storage ( /mnt/storage in reality ) to any directory you like. I've currently got mine pointing to an multi partitioned external 32gb sdcard. :0 all you need to do is change the sdcard service in the /etc/init/init.A101S.rc,
Currently it mounts /data/media to /mnt/storage, if you have an external sdcard card handy, try this as a quick and dirty test
From a terminal emulator or adb shell run the following commands
Code:
stop sdcard ;
sdcard /mnt/sdcard 1000 1015 &
ls /storage
You will now see that the external sdcard can be access through /storage. to kill the test run
Code:
pkill -9 sdcard
start sdcard
Everything should be back to normal. As I mentioned to make a more permanent change edit the following line in the /etc/init/init.A101S.rc
Code:
service sdcard /system/bin/sdcard /data/media 1000 1015
METHOD 2 - MOUNT BIND
The other, perhaps more straight forward method uses the bind argument on the mount to command to "mount an already visible filesystem elsewhere" .
In the example I'll bind the external sdcard to a directory in the internal storage
use the terminal emulator or adb once again to execute the following commands
Code:
mkdir /storage/sdcard
mount --bind /mnt/sdcard /storage/sdcard
To make this more parmanent, I would probably create a wrapper shell script for the sdcard service to make sure it all gets started together, that's just my preference, As we say in trade ( or maybe it's a saying i've just made up :silly: ) ; "there's more than one way to mount a file system!"
In Summary: I would go with method 2 as this effectively achieves the desired effect off "symlinking" an external directory in the /storage
Cheers
Click to expand...
Click to collapse
Installing ADBADB comes from word android development bridge, and it allows you to debug, move files and get shell access to your tablet.
Archos said:
First make sure you are running the latest ARCHOS firmware. Connecting by this method will give you user shell privileges. Learn more to know how to use ADB on Windows, Mac or Linux operating system:
Go to the Android SDK page and download the latest SDK for your operating system.
For Windows users only: Install the Archos ADB USB Driver for Windows. The driver is available at the ARCHOS support ftp (ftp://support.archos.com). Instructions how to install the driver are available at USB Driver for Windows site on Android Developers.
Add Archos vendor ID (0x0e79) to adb_usb.ini in .android folder in your home directory:
Windows: echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini"
Macos: echo "0x0e79" >> ~/.android/adb_usb.ini
Linux: echo "0x0e79" >> ~/.android/adb_usb.ini
For Linux users only: You need to add a udev rule if ADB only works as root:
Create a file /etc/udev/rules.d/51-android.rules that contains the following lines:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="e79/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="e79", MODE="0666"
Make the rule known to udev with the following command:
udevadm control --reload-rules (or udevcontrol reload_rules on older systems)
Click to expand...
Click to collapse
Running adb from anywhere
steviewevie said:
We need to update your Path variable. This lets you run adb on your PC from a command window no matter which directory you are in (which makes things a lot easier). If you don't setup your Path, then every time you want to run adb, you will either have to type the whole long pathname where you put adb, or cd to where you've put adb and run it from there (which could be inconvenient if you are transferring files to/from your phone).
On your PC, right-click on "My Computer" and select "Properties". (on Vista, click on "Change Settings"). Go to the "Advanced" tab, then select "Environment Variables". Find the "Path" variable in the list of variables that it shows (you might need to scroll), and then double-click on that entry to edit it. Add the full path of the "tools" and "platform-tools" folders of the SDK to your path. e.g. if the SDK has been installed in "c:\Program Files\android-sdk-windows", then add to your Path "c:\Program Files\android-sdk-windows\tools;c:\Program Files\android-sdk-windows\platform-tools" (Please Note - don't put any spaces between the semi-colon and pathname, otherwise it won't work !)
Click to expand...
Click to collapse
sources:Archos, steviewevie
Installing SuperchargerSupercharger is a multiscript which makes the tablet work much better. Its created by Zeppelinrox, and its official topic is here. We are using also script manager in this guide. That way we can make MinFrees and OOM apply.
In this guide we'll use Apex launcher which is moved to /system/app for our default launcher.
We are also using adb to configure and run Supercharger.
Because stock launcher is odexed and i am not writing how to deodex, we are not using it.
First make sure apex is your default launcher. This can be tested by pressing home button in homescreen.
If it show mini previews of your homescreens, apex is your default launcher.
Now lets begin:
go to here and download newest file. At
the time of writing, it is Update 9_RC11_test6. Move it to your adb folder.
Then open commandline. This can be opened with windowskey + R and writing cmd. Navigate
to adb folder using cd command. I have made adb to run from anywhere, so i just navigate to the downloaded file.
Now use command "adb push v6* /mnt/sdcard" then use command "adb shell". Now you should have
shell access to your tablet. Now do following
su
cd /mnt/sdcard
sh V6* /remember capital V)
Supercharger script should open now. After presentation, script should print after telling your busybox version
"com.anddoes.launcher is the home launcher!" Now continue install. Supercharger will tell you everything you need to know.
So just follow the instructions. After choosing kernel tweak, you get bunch of permission denieds.
We can't help them, so lets just continue.I recommend on using all the tweaks that you can,
but it is your choise do you want to use or not. After all the selections are selected and your in
driver panel, choose number 32. It'll reboot your tablet and wipe dalvik. When the tablet has booted, lets run supercharger script again.
So write these again:
su
cd /mnt/sdcard
sh V6_Super*
After getting to drivers panel, you notice that minfrees are not in effect, and neither is OOM Grouping Fix BUT if they are, you can ignore this step..
Install script manager from market and open it. Give it root permissions and navigate to /system/etc/init.d
press SS99SuperCharger to open its settings. Now press the Su button and then Boot button.
Now press save, and then click it's name which appers to right. Then press back button and reboot.
Now Minfrees should work, and OOM too.
Now you can run 22 if you want to try it. Supercharger is now fully working.
Installing Chainfire3D
Chainfire said:
Chainfire3D is an intermediary OpenGL driver. What does that mean? It means that Chainfire3D sits between your apps and the graphics drivers, and can intercept and/or change commands between the two. It has some built-in functions, and can be further extended with plugins to provide extra functionality.
Click to expand...
Click to collapse
It is very useful for running gameloft games and other games too. I recommend buying it. There are some plugin for it, but i'm not going to tell you about it now.Play store link.
After downloading it, open it and choose "Chainfire3D Driver" and from there "install". Then confirm it and tablet should reboot. Now reopen it and choose "Default opengl setting". From there you can tweak 3D performance if some games lag. Also, if you install plugin, there you can apply them. I personally use "reduce texture quality".
But why?
This section is to point few reason why to follow these guides. Lets begin:
SDE
Well, you should install this if you want to customize your tablet. If your happy with your tablet running stock, you don't need this, or any other guides.
Custom roms/kernels
Custom roms allow you to use root, they make your tablet faster and add extra functionality. This "functionality" includes: Overclock, run init.d scripts, enable both cores with all governors, root and themes. The benefits are not limited to these, but I could name this quickly. If you wan't to try something which is close to stock, but still has root and some custom functionalities, i would recommend deodexed 4.0.7, or [email protected]
Install official roms
These roms do not require SDE, but will not include root or anything fun . Updating your official rom has many benefits. They include fixes and boost your tablets performance.
Multiboot
Multibooting allows you to have 2 or more roms, which you can choose which to boot on startup. I would recommend this if you want to test functions with root, but still have "backup plan" if testing rom renders unbootable.
3G support
Basicly this allowes some extra huawei 3G sticks to work. There is no list of working stick, you just have to try and hope.
Change symlinks/binds
These allow you to "move" eg. gameloft games to external sd, and allow you to acces your externalsd via internalsd folder.. That way your gamedata does not eat the valuable internalsd space.
ADB
You need this to transfer rom to your tablet. It is also required when you sent logcat reports to help remove bugs.
SuperCharger
This makes your tablet work more fluid. I personally install supercharger to all my android devices. It removes need for task killer, and makes the device work better. Everyone has different results, and it costs only time to install, so i would recommend installing it.
Chainfire3D
This tool allows you to play games made for other GPUs and it can tweak application graphics. You can make the game look worse, but run better or adjust the grphics for a bit higher, so the game looks nicer.
FAQ[/CENTER]
These questions and answers are collected from various sources.
surdu_petru said:
How to activate second core for all govenors in surdu_petrus roms?
To activate the second core, you need the following steps :
- copy /system/S1tweak in /system/etc/init.d/ or ( > adb shell ; # cp /system/S1tweak /system/etc/init.d ; # exit )
- open No-frills CPU Control :
- choose the desired Governor ( but not hotplug ) !
- choose the desired frequency , but not overclocked ! ( when the device will boot - will open with the selected frequency , so please choose max. frequency = your max. stock frequency )
- check "Apply on boot"
- check "Applay"
- check allow if superuser asked permission
- reboot your device !
- Now , both core will be used in any selected Governor ( other than hotplug ! ).
Click to expand...
Click to collapse
What modems does Trevds mod support?
trevd said:
The theoretical list of supportted devices come from those devices supportted by usb_wwan and option kernelp drivers.
Click to expand...
Click to collapse
Shano56 said:
Can I just drag the .zip file to the RAMDISK that appears when I flash zImage and initramfs?
No! Archos recovery cannot read ZIP files. You must first EXTRACT, then copy the contents of the extracted folder. NOT the folder itself. This means you will have two files on the RAMDISK, and no additional folders. If you don't know what a RAMDISK is, try Google or Wikipedia. If you get stuck in a boot loop because you forgot to extract archos.update.ext4 or drive.zip, you must follow the instructions below.
Help! I am stuck in a bootloop! Archos splash screen appears and keeps rebooting. I messed up when I was rooting, and now android will not boot! I accidentally formatted my device, and now I cannot boot into android.
This is a simple mistake and in 99% of cases it is easy to fix. Follow these steps:
Step 1: Download official Archos G9 firmware for ALL G9 tablets (aos file) HERE
Step 2: Boot into recovery turning your device off and then holding volume down + power at the same time
Step 3: Choose "Update Firmware"
Step 4: Connect USB cable to computer and tablet
Step 5: A removable device should appear (RAMDISK), copy the file you just download straight to that drive
Step 6: Press the power button once the file is done copying. DO NOT UNPLUG your device until it has finished updating and has booted back into android.
If you did not format your tablet or delete any personal media, your files should be uneffected.
Will I lose SDE menu if I update my tablet with official AOS or OTA update
As of the latest update (4.0.6) no official update from Archos has removed SDE menu. You should be fine, and your SDE menu should remain untouched.
Click to expand...
Click to collapse
[/quote]
Useful linksSome link i consider useful are here:
G9 101 16GB 1.5GHz Teardown! (Lots of Images)
XBMC for android
Want faster GPS? Follow this guide
3th just i remember something to add. Comment and give me some feedback. It helps me to make this topic useful for beginners, and for those who seek info.
I meant to edit first post... well, this works as 4th reserved then.
Hi there!
You have been busy! Thanks for kind words, Just an heads up really, you might want to update your post as I deleted the usb-modem-binary-redist github repo yesterday as it was a bit too clever for it's own good and I think a bit of abuse/misuse of the concept branching! Just because you can, doesn't always mean you should LOL, with that in mind I'd probably advise against linking to my github repos as they don't stay static for very long. I generally leave the hotfile links up "forever" so link away with them.
The Information and files included in the new AOKP post about 3G Dongles should be good across all ICS roms. Finally allow me to throw out this mini guide I wrote a while back which explains an "app-free" method of freeing up space, I noticed there been a bit of discussion about it, Using an app just seem like overkill, but that's just me I suppose.
Anyway good work. :good:
trevd said:
Hi there!
You have been busy! Thanks for kind words, Just an heads up really, you might want to update your post as I deleted the usb-modem-binary-redist github repo yesterday as it was a bit too clever for it's own good and I think a bit of abuse/misuse of the concept branching! Just because you can, doesn't always mean you should LOL, with that in mind I'd probably advise against linking to my github repos as they don't stay static for very long. I generally leave the hotfile links up "forever" so link away with them.
The Information and files included in the new AOKP post about 3G Dongles should be good across all ICS roms. Finally allow me to throw out this mini guide I wrote a while back which explains an "app-free" method of freeing up space, I noticed there been a bit of discussion about it, Using an app just seem like overkill, but that's just me I suppose.
Anyway good work. :good:
Click to expand...
Click to collapse
Thanks for the feedback.
I removed the part which had github link, and modified the AOKP section to tell it works with all ICS ROMs.
I'll included your mini guide. I might even have some use for it myself...
Sent from my GT-I9100 using xda app-developers app
help me for multi boot ubuntu ics bleuv03
hello I want to know is it possible to bleuv03 ics and multi boot with ubuntu and it is possible that what zImage and iniframts I should use.
desoler for my english I'm french and I go through a translator thank you.
muti642 said:
hello I want to know is it possible to bleuv03 ics and multi boot with ubuntu and it is possible that what zImage and iniframts I should use.
desoler for my english I'm french and I go through a translator thank you.
Click to expand...
Click to collapse
Download zimage, initfram and Ubuntu image from
http://forum.xda-developers.com/showthread.php?p=26000199
There is a high chance that touchscreen will not work if you have 101 G9 model in Ubuntu. You can still use USB OTG devices like mouse normally.
Sent from my GT-I9100 using xda app-developers app
julle131 said:
Download zimage, initfram and Ubuntu image from
http://forum.xda-developers.com/showthread.php?p=26000199
There is a high chance that touchscreen will not work if you have 101 G9 model in Ubuntu. You can still use USB OTG devices like mouse normally.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
thank you for answered. j've already managed to install ubuntu and I had no problem touch by cons I Can not get a dual boot ubuntu and bleuv03 ics. I shall therefore understands the multi boot flash I then I put two images but in the memory of the tablet and then I flash the kernel you gave me quote above and I should be able to boot on 2 rom and bleuv03 ubuntu?
muti642 said:
thank you for answered. j've already managed to install ubuntu and I had no problem touch by cons I Can not get a dual boot ubuntu and bleuv03 ics. I shall therefore understands the multi boot flash I then I put two images but in the memory of the tablet and then I flash the kernel you gave me quote above and I should be able to boot on 2 rom and bleuv03 ubuntu?
Click to expand...
Click to collapse
Download the this kernel https://docs.google.com/file/d/0BxgjsI4pMALheHZoVUdIYnVTN28/edit
It can dualboot [email protected] v03. If the ubuntu does not boot after flashing it, download this ubuntu image:
https://docs.google.com/file/d/0BxgjsI4pMALhVl9kek9SSFpKb2M/edit
THX
julle131 said:
Download the this kernel https://docs.google.com/file/d/0BxgjsI4pMALheHZoVUdIYnVTN28/edit
It can dualboot [email protected] v03. If the ubuntu does not boot after flashing it, download this ubuntu image:
https://docs.google.com/file/d/0BxgjsI4pMALhVl9kek9SSFpKb2M/edit
Click to expand...
Click to collapse
Thank you thanks you it works well, I do not use the right kernel or the good image of ubuntu. ps: the touchscreen does not work but using the OTG is perfect.
thank you again julie :good:
sorry for ignorance but for root i need to have adb sdk for do this steps??
"- copy archos.ext4.update to /mnt/storage/ , you can use this command > adb push archos.ext4.update /mnt/storage/
- go to SDE -> Developer Edition Menu ->( Remove Android Kernel if available ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.lzo -> OK! -> wait to reboot .....
- the first boot may be longer ! "
If my archos is untoot how i use this comand? with adb sdk ?!
solrakk6 said:
sorry for ignorance but for root i need to have adb sdk for do this steps??
"- copy archos.ext4.update to /mnt/storage/ , you can use this command > adb push archos.ext4.update /mnt/storage/
- go to SDE -> Developer Edition Menu ->( Remove Android Kernel if available ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.lzo -> OK! -> wait to reboot .....
- the first boot may be longer ! "
If my archos is untoot how i use this comand? with adb sdk ?!
Click to expand...
Click to collapse
Yes, you must use adb. I assume your "untoot" means unrooted. You use cd command to navigate to your adb folder and from there to platform-tools. Also drop archos.ext4.update to there. Then use the adb command to move the file. Moving file to that location does not require root.
Sent from my GT-I9100 using xda app-developers app
Archos G9 101 HD
Hi Surdu,
I tried to update after SDE install and then accidentally dont know what happened have lost android on my tablet G9 101 HD. I cant see my hd on pc and is not booting but only can see the rom image which appears on boot without animation. How can I transfer the update archos.ext4 into Internal Storage without seeing the drive on PC win 7. I have made mistake in steps may be.
Please help.
hondacity said:
Hi Surdu,
I tried to update after SDE install and then accidentally dont know what happened have lost android on my tablet G9 101 HD. I cant see my hd on pc and is not booting but only can see the rom image which appears on boot without animation. How can I transfer the update archos.ext4 into Internal Storage without seeing the drive on PC win 7. I have made mistake in steps may be.
Please help.
Click to expand...
Click to collapse
Go to the recovery menu, choose update firmware. When it prompts you to connect tablet to pc, cobbect it, but to different usb port than last time. That should cause the pc to reinstall usb drivers for the tablet.
Sent from my GT-I9100 using xda app-developers app
Archos G9 101 HD
julle131 said:
Go to the recovery menu, choose update firmware. When it prompts you to connect tablet to pc, cobbect it, but to different usb port than last time. That should cause the pc to reinstall usb drivers for the tablet.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks, for so fast reply Dear...
I did the same as you advised and a drive with name ending with "REC" with a capacity of 299 MB appeared. I tried to copy the Surdu's Deoedex update but it has more weight in MBS about 390. So it could not. I tried original Archos ROM with weight of 186 MB and it copied. Started update but returned with an error "Update failed: (221)".....
Please advise.
Note: I also tried in SDE menu to export data drive and got a drive 1.48 GB which I formated from win 7 and succeded in copying Stock and Surdu's ROMs one by one but always failed to get android and it always say failed update. Still get unanimated Archos logo on startup with no further bootup.
hondacity said:
Thanks, for so fast reply Dear...
I did the same as you advised and a drive with name ending with "REC" with a capacity of 299 MB appeared. I tried to copy the Surdu's Deoedex update but it has more weight in MBS about 390. So it could not. I tried original Archos ROM with weight of 186 MB and it copied. Started update but returned with an error "Update failed: (221)".....
Please advise.
Note: I also tried in SDE menu to export data drive and got a drive 1.48 GB which I formated from win 7 and succeded in copying Stock and Surdu's ROMs one by one but always failed to get android and it always say failed update. Still get unanimated Archos logo on startup with no further bootup.
Click to expand...
Click to collapse
Okay... So you have sde installed? Good. First, let's get the official firmware working. Download the latest official ROM from archos:
http://update.archos.com/9/gen9/gen9_4.0.26/firmware_archos_it4.aos
Drop this to the 300mb partition called REC. Then press power and let it install.
Now follow the install guide o. The ROM you want to install
Sent from my GT-I9100 using xda app-developers app
Archos G9 101 HD
julle131 said:
Okay... So you have sde installed? Good. First, let's get the official firmware working. Download the latest official ROM from archos:
Drop this to the 300mb partition called REC. Then press power and let it install.
Now follow the install guide o. The ROM you want to install
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks Julle..But Now I understand that official ROM is not installing because of unofficial kernel flash I have already installed and had flushed original one. I think if I get original kernel then I can arrive to original Android ICS which you have mentioned. Please advise if you have any address of original kernel for "firmware_archos_it4.aos".
THANKS and Best Regards...
Further to my above thread...I found the stock kernel and flashed it but still after installing kernel and then original firmware, its giving same error of update failed (221).
Please advise if any remedy you prefer.
Regards...
Hi Julle,
Sorry too many threads from me but very much annoyed but sure thanks Dear for your kind help.
On export of HDD from "Repair system" menu...>>>> A drive appeared in PC but not opening as it says " Insert disk into drive". I think it is the problem which is preventing from installing the AOS file to run Android.
Please advise.
Regards,
hondacity said:
Thanks Julle..But Now I understand that official ROM is not installing because of unofficial kernel flash I have already installed and had flushed original one. I think if I get original kernel then I can arrive to original Android ICS which you have mentioned. Please advise if you have any address of original kernel for "firmware_archos_it4.aos".
THANKS and Best Regards...
Further to my above thread...I found the stock kernel and flashed it but still after installing kernel and then original firmware, its giving same error of update failed (221).
Please advise if any remedy you prefer.
Regards...
Hi Julle,
Sorry too many threads from me but very much annoyed but sure thanks Dear for your kind help.
On export of HDD from "Repair system" menu...>>>> A drive appeared in PC but not opening as it says " Insert disk into drive". I think it is the problem which is preventing from installing the AOS file to run Android.
Please advise.
Regards,
Click to expand...
Click to collapse
To install the update I linked, you shouldn't need any kernel changes. Removing kernel from SDE removes the official kernel, but that does not prevent installing official update. Also installing custom kernel will not prevent installing official rom.
I just do not understand why you get the 221 error as most of the people get it when that have incorrect file there or already have newer stock ROM installed. It is possible that your windows format broke it, because windows formats it to wrong format. You should never format any other than sdcards in windows. You could try the format system in recovery and choosing reformat device. After that install the official update I linked.
Sent from my GT-I9100 using xda app-developers app
Archos G9 101 HD
julle131 said:
To install the update I linked, you shouldn't need any kernel changes. Removing kernel from SDE removes the official kernel, but that does not prevent installing official update. Also installing custom kernel will not prevent installing official rom.
I just do not understand why you get the 221 error as most of the people get it when that have incorrect file there or already have newer stock ROM installed. It is possible that your windows format broke it, because windows formats it to wrong format. You should never format any other than sdcards in windows. You could try the format system in recovery and choosing reformat device. After that install the official update I linked.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks again Dear,
I applied same as you say but ending on same 221 error. Any thoughts please.
Best regards.:crying:
Tweeks:
Camera Tweek (You need busybox installed for this), or you can unpack the zip and apply the patch manually/setting the permission corectly.
It will improve the overall video recording quality, by increasing the size limit cap of the video (old setting 600 Kb vs new 1200 Kb)
Custom Firmwares
Reserved
Recovery
CWM WITH ACCESS AT THE SYS_BOOT PARTITION ======>>>>> Bigger chance in bricking your device if you sleep while you flash something.
CWM NON TOUCH / NO ACCESS TO SYS_BOOT
Way to flash:
Version 1)
- enable usb debugging
- install adb drivers
- use the command adb reboot bootloader
- use the command fastboot flash recovery recovery.img
Version 2)
- shut down the phone
- press the volume key minus and power key
- use the command fastboot flash recovery recovery.img
Do not forget to unpack the zip files.
Please have in mind that with the no_sys CWM, you cannot restore the phone to stock using an official update.
Unbricking
Copied from here
Here's a small tutorial for people who bricked their phone while formatting the sys_boot partition in CWM Recovery. When you format that partition, nothing works except a screen shows up saying "RESET FOR ENTRY QPST DOWNLOAD". This screen is also known as the Qualcomm Diagnostic Mode.
Requirements:
A linux distribution (Ubuntu)
sys_boot.img (https://docs.google.com/file/d/0BxJJu-wXKdltTE90SGtEMmFQZHM/edit)
Follow the steps to restore the sys_boot partition:
1. Connect your phone to a pc using the cable
2. Install the drivers if necessary:
https://dl.dropboxusercontent.com/u/17562266/USB Modem Driver.rar
3. Open your terminal
4. Type "lsblk" (without the quotes).
You should see a list, showing every connected disk and partition. Look for a partition with a size around 50M. This is the partition we need, so remember the corresponding name under the 'NAME' column. It can be "sdc", "sdd" or "sde" followed by a number.
5. Cd to the directory you placed sys_boot.img in
cd [filename]
6. Type "sudo dd if=/dev/NAME of=sys_boot.img bs=512
Replace NAME with the name you got from lsblk, and press enter.
The output should look something like this:
3959420000 bytes (3866621 KB) copied, [ time spent], [KB/s]
7. Remove the cable from your device, do a battery pull and try to boot your device
Normally, it should boot correctly. If you formatted the /system partition too, you have to get into recovery mode by holding the upper volume button while booting, until a red screen appears.
If you have any questions, or if this doesn't work for you – let me know in the comments.
Thanks a lot to Adonis K. and globula_neagra for the sys_boot image and pointing me in the right direction.
Credits to DieterHolvoet from arctablet for putting it together.
THX! Much appreciated!
I own this device since today and you Sir made me very happy with your cwm and ability to root.
---------- Post added at 08:19 PM ---------- Previous post was at 07:42 PM ----------
I can confirm. Touchversion of CWM does not work.
File for non-touch CWM seems the same as touch btw. Could you please fix the link? Thx!
Yes, the touch version doesn't work.
The no-touch no-sys version works fine.
Here is the link for the no-touch/no-sys version (taken from the arctablet forums): http://globula.arctablet.com/ARCHOS_50_PLAT/CWM_A50_Plat_NoTouch_No_SYS.img.zip
globula must have misstyped it
IN CWM I cannot mount the sdcard. So I can't install any Zip-Files this way
Nash123 said:
IN CWM I cannot mount the sdcard. So I can't install any Zip-Files this way
Click to expand...
Click to collapse
I will fix these issues tomorrow.
Thank you!
GEN 11 ?
cajl said:
GEN 11 ?
Click to expand...
Click to collapse
Yes the Archos 50/53 Platinum and Archos 80 Xenon are Generation 11
NO !
it will be announced at IFA and I would see in Berlin
cajl said:
NO !
it will be announced at IFA and I would see in Berlin
Click to expand...
Click to collapse
I could try to convince you that they are Gen11, but you will have to trust me, the update page does not lie.
OK Archos 53 also ...
Anyone know if it's possible to partition the internal memory and internal sdcard together? I'm getting really low in internal space intended for app installations (180mb left, getting insufficient space errors)
Updated the third post with a new touch cwm, test version, i don`t have a platinum to test it.
Adonis, i don`t think is possible, tough you can use directory binder
I need some help with some file from the Archos 50 Platinum, I want to test if the phone function works on Archos 80 Xenon (it should in theory as this is not the first tablet made by Archos/Arnova that has a crippled phone function, my 7C G3 is capable if doing/receiving phone calls)
Hmmm, i see. In my previous phone the developers found a way to repartition the device and play around with them so we could balance the phone and internal memory to our advantage. Could really use the /storage/sdcard1 as part of my /data and /system partitions.
http://i.imgur.com/MJkdLS9.png
Never heard of directory binding, is it like symlinking?
I will test touch version in a few mins, gotta watch something first.
edit: Nope, touch still not working. Same results as the previous one.
Adonis K. said:
Hmmm, i see. In my previous phone the developers found a way to repartition the device and play around with them so we could balance the phone and internal memory to our advantage. Could really use the /storage/sdcard1 as part of my /data and /system partitions.
http://i.imgur.com/MJkdLS9.png
Never heard of directory binding, is it like symlinking?
I will test touch version in a few mins, gotta watch something first.
edit: Nope, touch still not working. Same results as the previous one.
Click to expand...
Click to collapse
Then it will be no touch for the moment, tough is strange, on the Archos 80 Xenon is working fine.
Not having the phone is a big impediment for me to test things, and I have the Xenon only till 28`th, so this is my main platform for testing for now (identical spec with the 50 Plat, even the partition layout is identical , that`s why i believe that the phone function should work)
I will do another try with the touch version from the Xenon in the next days, maybe with will work with that one.
Yes, the directory binding is the same as simlinking
Does anyone know a fix for the incompatability with older routers? (Non Wifi-N support).
Sorry for the OT btw.
Edit: Second question. How do I revert back to stock firmware or stock mode [without root and CWM-recovery]? I used the non_sys-version.
Edit2: Tomorrow I will flash original firmware. Hopefully the alterations will be gone.
Nash123 said:
Does anyone know a fix for the incompatability with older routers? (Non Wifi-N support).
Sorry for the OT btw.
Edit: Second question. How do I revert back to stock firmware or stock mode [without root and CWM-recovery]? I used the non_sys-version.
Edit2: Tomorrow I will flash original firmware. Hopefully the alterations will be gone.
Click to expand...
Click to collapse
I think you will need the sys_boot recovery for that, or the stock one, the non_sys boot will not allow you to flash stock firmware.
Hi,
Lenovo Vibe K4 Note which was recently released in India got many OTA updates from Lenovo. This updates are available for users as soon as they connect their device to the internet. This update mainly includes bug fixes and software improvements.
Using ADB logcat, I captured the URL for downloading the update and updating the phone manually.
OTA 1 : This upgrades the phone from build number A7010a48_S143_151218_ROW to A7010a48_S147_160113_ROW.
Update Size : 283MB
URL : http://phonedl.ota.lenovomm.com/dls...OW_TO_A7010a48_S147_160113_ROW_WC542E0B8B.zip
Mirror : https://docs.google.com/uc?id=0BzJd5Ca5OlI3ZDZIR1E4Y05GdjA&export=download
Checksums :
MD5: 5e4d969c82426f2a5483dd5d58b573b3
SHA-1: 94dcfc29538984f6ef867191195d6e7fae86b69c
OTA 2: This upgrades the phone from build number A7010a48_S147_160113_ROW to A7010a48_S148_160201_ROW.
Update Size : 40MB
URL : http://phonedl.ota.lenovomm.com/dls...OW_TO_A7010a48_S148_160201_ROW_WC2A54CCF5.zip
Mirror : https://userscloud.com/qqsvk3nyv8t4
Thanks to @gursewak.10
OTA 3: This upgrades the phone from build number A7010a48_S148_160201_ROW to A7010a48_S150_160219_ROW.
Update Size : 38MB
URL : http://phonedl.ota.lenovomm.com/dls...OW_TO_A7010a48_S150_160219_ROW_WCBBBB28A6.zip
Mirror : https://userscloud.com/mnxxf6s4pmnu
Thanks to @gursewak.10
OTA 4 : This upgrades the phone from build number A7010a48_S150_160219_ROW to A7010a48_S152_160302_ROW.
Update Size : 34MB
URL : http://phonedl.ota.lenovomm.com/dls...OW_TO_A7010a48_S152_160302_ROW_WC5A28FDD3.zip
Mirror : https://userscloud.com/kdz3habbdrzf
Thanks to @gursewak.10
MARSHMALLOW UPDATE!!!
OTA 5 :This upgrades the phone from build number A7010a48_S152_160302_ROW to A7010a48_S214_160527_ROW.
Update Size : 1.62GB
URL : http://phonedl.ota.lenovomm.com/dls...OW_TO_A7010a48_S214_160527_ROW_WC04B2A0E0.zip
FULL ROM
This is a standalone ROM for this device. The version is S232.
URL : https://drive.google.com/file/d/0B0oTcPwt3IIDYWgxZlQ4NnFoNjg/edit
Installation Instructions :
1. Rename the downloaded zip file to "update.zip" using a file manager and place it in the root directory of the internal storage.
2. Power off your device.
3. Access the recovery by holding down the power key until the device vibrates and then pressing and holding the Volume Down and Volume Up buttons until the recovery screen appears.
4. Tap on "Install upgrade pack".
5. Tap on "Yes" when asked to "Install update.zip from internal or external sdcard".
This will start your installation and takes 8-15 minutes based on the number of apps installed.
Cheers,
abhish3k
Here is the link for 2nd 40mb update for the same
http://phonedl.ota.lenovomm.com/dls...OW_TO_A7010a48_S148_160201_ROW_WC2A54CCF5.zip
Or
Get the file here
https://userscloud.com/qqsvk3nyv8t4
Here is the next 38mb update link
http://phonedl.ota.lenovomm.com/dls...OW_TO_A7010a48_S150_160219_ROW_WCBBBB28A6.zip
Or you can easily download via any browser here
https://userscloud.com/mnxxf6s4pmnu
I'm using this stock rom s147, but unfortunately not able to update using this OTA
Sent from my Lenovo A7010a48 using XDA Premium 4 mobile app
You have to update your phone in sequences how the updates came.
Ist- 283mb
2nd-40mb
3rd-38mb
4th-34mb
You can't skip any previous update before installing newer update.
Hey, guys, can I install this on the brazilian version? Thanks.
abhish3k9 said:
Hi,
Lenovo Vibe K4 Note recently released in India, got an OTA update from Lenovo. This update is available for users as soon as they connect their device to the internet. This update mainly includes bug fixes and software improvements.
Using ADB logcat, I captured the URL for downloading the update and updating the phone manually.
OTA 1 : This upgrades the phone from build number A7010a48_S143_151218_ROW to A7010a48_S147_160113_ROW.
URL : http://phonedl.ota.lenovomm.com/dls...OW_TO_A7010a48_S147_160113_ROW_WC542E0B8B.zip
Mirror : https://docs.google.com/uc?id=0BzJd5Ca5OlI3ZDZIR1E4Y05GdjA&export=download
Checksums :
MD5: 5e4d969c82426f2a5483dd5d58b573b3
SHA-1: 94dcfc29538984f6ef867191195d6e7fae86b69c
OTA 2: This upgrades the phone from build number A7010a48_S147_160113_ROW to A7010a48_S148_160201_ROW.
URL : http://phonedl.ota.lenovomm.com/dls...OW_TO_A7010a48_S148_160201_ROW_WC2A54CCF5.zip
Mirror : https://userscloud.com/qqsvk3nyv8t4
Thanks to @gursewak.10
OTA 3: This upgrades the phone from build number A7010a48_S148_160201_ROW to A7010a48_S150_160219_ROW.
URL : http://phonedl.ota.lenovomm.com/dls...OW_TO_A7010a48_S150_160219_ROW_WCBBBB28A6.zip
Mirror : https://userscloud.com/mnxxf6s4pmnu
Thanks to @gursewak.10
Installation Instructions :
1. Rename the downloaded zip file to "update.zip" using a file manager and place it in the root directory of the internal storage.
2. Power off your device.
3. Access the recovery by holding down the power key until the device vibrates and then pressing and holding the Volume Down and Volume Up buttons until the recovery screen appears.
4. Tap on "Install upgrade pack".
5. Tap on "Yes" when asked to "Install update.zip from internal or external sdcard".
This will start your installation and takes 10-20 minutes based on the number of apps installed.
Cheers,
abhish3k
Click to expand...
Click to collapse
I had rooted my K4 and foolishly uninstalled "Cloud" and "step counter" as I did not like them. Now my phone throws FC randomly and annoys.
Would you know how to fix this? Thanks in advance.
new 33 mb update
Please provide a mirror link to download the new 33MB update.
Ankitchoudhary said:
Please provide a mirror link to download the new 33MB update.
Click to expand...
Click to collapse
Yes, of course...
Check the forums in the evening
Provide more info
marcopolo said:
I had rooted my K4 and foolishly uninstalled "Cloud" and "step counter" as I did not like them. Now my phone throws FC randomly and annoys.
Would you know how to fix this? Thanks in advance.
Click to expand...
Click to collapse
Well, it depends.... Which app is FCing ?
abhish3k9 said:
Hi,
Lenovo Vibe K4 Note which was recently released in India got many OTA updates from Lenovo. This updates are available for users as soon as they connect their device to the internet. This update mainly includes bug fixes and software improvements.
Using ADB logcat, I captured the URL for downloading the update and updating the phone manually.
OTA 1 : This upgrades the phone from build number A7010a48_S143_151218_ROW to A7010a48_S147_160113_ROW.
URL : http://phonedl.ota.lenovomm.com/dls...OW_TO_A7010a48_S147_160113_ROW_WC542E0B8B.zip
Mirror : https://docs.google.com/uc?id=0BzJd5Ca5OlI3ZDZIR1E4Y05GdjA&export=download
Checksums :
MD5: 5e4d969c82426f2a5483dd5d58b573b3
SHA-1: 94dcfc29538984f6ef867191195d6e7fae86b69c
OTA 2: This upgrades the phone from build number A7010a48_S147_160113_ROW to A7010a48_S148_160201_ROW.
URL : http://phonedl.ota.lenovomm.com/dls...OW_TO_A7010a48_S148_160201_ROW_WC2A54CCF5.zip
Mirror : https://userscloud.com/qqsvk3nyv8t4
Thanks to @gursewak.10
OTA 3: This upgrades the phone from build number A7010a48_S148_160201_ROW to A7010a48_S150_160219_ROW.
URL : http://phonedl.ota.lenovomm.com/dls...OW_TO_A7010a48_S150_160219_ROW_WCBBBB28A6.zip
Mirror : https://userscloud.com/mnxxf6s4pmnu
Thanks to @gursewak.10
Installation Instructions :
1. Rename the downloaded zip file to "update.zip" using a file manager and place it in the root directory of the internal storage.
2. Power off your device.
3. Access the recovery by holding down the power key until the device vibrates and then pressing and holding the Volume Down and Volume Up buttons until the recovery screen appears.
4. Tap on "Install upgrade pack".
5. Tap on "Yes" when asked to "Install update.zip from internal or external sdcard".
This will start your installation and takes 10-20 minutes based on the number of apps installed.
Cheers,
abhish3k
Click to expand...
Click to collapse
Hello Abhishek..
Dear i m not able to install Update.zip ..
it says Install Fails..
i have rooted my device with KingRoot & now unroot it..
Please guide..
Well here is the next 33mb update
https://userscloud.com/kdz3habbdrzf
update failed
I am unable to update this time with 33Mb update. It shows update failed. I had not rooted my device or done anything wrong with it. Then why its not getting this update?
abhish3k9 said:
Well, it depends.... Which app is FCing ?
Click to expand...
Click to collapse
Like I mentioned, "Cloud" and "step counter".
Follow this link
glassyrajat said:
Hello Abhishek..
Dear i m not able to install Update.zip ..
it says Install Fails..
i have rooted my device with KingRoot & now unroot it..
Please guide..
Click to expand...
Click to collapse
This guide for Lenovo K3 Note also applies for K4 Note. I hope this helps you out.
Cheers,
abhish3k
When i update 2nd one 40 mb file the error came & file software can not update please help me
douglastabajara said:
Hey, guys, can I install this on the brazilian version? Thanks.
Click to expand...
Click to collapse
Check in settings>>about phone>>device info
If it shows ROW in build. Number i.e. Rest of World then you can install.
I think there are two lenovo k4 software versions only- 1)Chinese 2)ROW -Rest of World
---------- Post added at 10:15 PM ---------- Previous post was at 10:07 PM ----------
Friend if you are not able to install any of the updates here are some. Notes which may help you-
-The file should be renamed to update.zip. -all small letters sometime error comes due to it.
-phone should not be rooted
-unrooting also doesn't work. Rare chance of updating success in this case. Try installing stock rom again.
-try downloading with no pause during download as sometimes a file gets corrupted in zip file causing update failure.
***meanwhile check here for other k4 help
http://forum.xda-developers.com/android/general/lenovo-vibe-k4-note-t3341182
Well friends good news official marshmallow update has started rolling out.
Heres the link
http://phonedl.ota.lenovomm.com/dls...OW_TO_A7010a48_S202_160316_ROW_WCB5490CE7.zip
Mirror https://userscloud.com/c13b2auv6tjw
gursewak.10 said:
Well friends good news official marshmallow update has started rolling out.
Heres the link
Click to expand...
Click to collapse
please share the steps on how to flash the update zip without recovery, I've rooted with kingroot and I've still two OTA's which has to be updated.
Thanks
kiran2508 said:
please share the steps on how to flash the update zip without recovery, I've rooted with kingroot and I've still two OTA's which has to be updated.
Thanks
Click to expand...
Click to collapse
Then you can't
Because for every new update its compulsory that you should already have previous update installed.
You should flash stock rom first via sp flash tool and then install all updates according to serial wise.
Hi,
Goal is to upgrade my M2, I believe it has a modem because it is able to receive SMS, 4G network, etc...
One thing is missing, calling functionality, dialer stuff ... is this hardware or firmware (or driver not installed)?
Can somebody please confirm or know how these things work?
So I want to upgrade because, I just want to be up to date, new android!
No updates are available if I try the official via EMUI Update way... online at Huawei nothing is available either (they refer to EMUI). It says most current version.
But then I read people from other European countries do have updates installed, 'same' model ... WTF?!?
Version / model : M2-A01L / 2GB
* Everything is still factory.
* EMUI : 3.1
* Android : 5.1.1
* Custom version : CUSTC100D002
* Bootloader version : V100R001C00B000_FASTBOOT
* Kernel version : M2-A01LV100R001C100B006_BOOT
* AP : M2-A01LV100R001C100B006_SYSTEM
* CP Version / baseband : 21.600.20.00.010(balong)
* Cust Version : Cversion:C100 DVersion002
So first things first reading different posts and tutorials about updating:
* https://forum.xda-developers.com/mediapad-m2/how-to/guide-official-updates-m2-tablet-root-t3589363
* https://forum.xda-developers.com/me...om-official-manual-updates-m2-tablet-t3595211
Im already stuck at the official steps:
1 - On tablet created folder : InternalStorage/HwOUC placed M2-A01LV100R001C100B007.zip and rename in update.zip
2 - Turn off , Reboot device (not connected to laptop) , should automatically install update above. Nothing happens.
So lets try bootloader maybe I can choose to update from folder or something. Nope, just 3 options, (reboot:wipe cache:factory)
Strange... Im wondering
1 - If they disabled something so updating is not possible at all?
2 - Other possibility in the forum, update.app in dload... people mention the process got stuck on 2%. Can you get back to original, it just fails or do you need to do a factory reset to get a working tablet again?
3 - What steps to take to make sure you can always... yes, always get back to your factory firmware when updating.
4 - Then I was reading about simply download to a full firmware (not an update)
HUAWEI_MediaPad+M2+10.0_M2-A01L_Firmware_Android+5.1.1_EMUI+3.1_V100R001C100B010CUSTC100D001_Germany_Spain_Belgium.zip
Not Netherlands... Im not 100% confident this is the way to go. Last part of the filename D001_German... mine is D002, so, aaargh
I hope you can guide me and help me updating. I dont know much about this, is it really chipset, hardware or just software (compilation) stuff...
jesperrekuh said:
Hi,
Im already stuck at the official steps:
1 - On tablet created folder : InternalStorage/HwOUC placed M2-A01LV100R001C100B007.zip and rename in update.zip
2 - Turn off , Reboot device (not connected to laptop) , should automatically install update above. Nothing happens.
So lets try bootloader maybe I can choose to update from folder or something. Nope, just 3 options, (reboot:wipe cache:factory)
Click to expand...
Click to collapse
Making progress ... step:
0 - Back to factory settings, yes wipe that thing and let's see... then:
1 -
a - Unpacked M2-A01LV100R001C100B007.zip placed in internal storage/dload. Settings > Update > menu > local update. Package found, rebooting, installing, SUCCESS, rebooting again.
b - Open Settings > About Tablet > look at buildnr... A01LV100R001C100B006 didn't change, huh. repeated steps above...
Lets's see what happens if go to OTA-M2-A01LV100R001C100B010.zip, same steps... and after updating process. nothing changed, still the same ... A01LV100R001C100B006 ...
So somehow the manual local update looks into dload folder > changes the boot procedure to update > then looks into a factory prepped setting > updates to its original and no version change.
Edit:
Placed file 007 in internal storage > dload , powered off , then I did :
Vol + UP and Vol - Down and PowerOn buttons, waited until I got the installing EMUI screen.
Nope, nothing changed.
YESSSSS , SUCCESS :good: read!!! (and above)
- Tablet (bought in the Netherlands) - Huawei M2 10" - A01L :
* Custom version : CUSTC100D002
* Bootloader version : V100R001C00B000_FASTBOOT
* Kernel version : M2-A01LV100R001C100B006_BOOT
* AP : M2-A01LV100R001C100B006_SYSTEM
This is what I did :
- Factory reset, tried to update B006 -> B007 -> B010, nothing seemed to be changed although it said success ...
- Not rooted, no TWRP, not Developer or Manufacturer mode... just basic.
Then downloaded rom in this topic :
https://forum.xda-developers.com/mediapad-m2/development/rom-m2-a01l-lte-premium-stock-t3624094
Huawei 10 - M2 A01L - B010 LTE file
- sdcard in tablet (not internal storage)
- create folder dload
- unzip file (above) and place the contents of the extracted file and its subfolder dload into this.
- the folder contained file UPDATE.APP and hw folder. Total size 3.3GB.
- Power down
- Unplug all cables
- Check if you have sufficient power >50%
- VolUp + and VolDown - and PowerOn, wait until EMUI Install screen, takes around 15-20seconds.
- Install starts until finished, 15minutes. Slow progress.
- Looks like it hangs on 99% but wait for success
Et voila, from B006 -> B010 and yes, including dialer... made a phonecall...
Next is rooting...
As I was saying... ROOTING, success again.. what ... a .... day !!!
My Steps :
0. Did above... don't forget
1. Follow these steps and pay 4 credits : Steps to Unlock, Recovery and Root
- Manufacturer mode to get the unlock code, back to hiSuite mode
- Command line tools for windows : ADB and fastboot
- Follow the exact procedure , step 18.
2. Troubles finding the files you need:
- TWRP for Android 5.1.1 More information can be found link here
- SuperSu
Enabling call on M2-801L
jesperrekuh said:
As I was saying... ROOTING, success again.. what ... a .... day !!!
My Steps :
0. Did above... don't forget
1. Follow these steps and pay 4 credits : Steps to Unlock, Recovery and Root
- Manufacturer mode to get the unlock code, back to hiSuite mode
- Command line tools for windows : ADB and fastboot
- Follow the exact procedure , step 18.
2. Troubles finding the files you need:
- TWRP for Android 5.1.1 More information can be found link here
- SuperSu
Click to expand...
Click to collapse
I read your post with interest. I was trying to do exactly the same thing i.e. enable the calling features on my M2-801L.
Eventually got my tablet fully working and your post helped a lot!!
So thanks for posting the info.