Related
5/12/2011 : Thread marked depreciated due to the recent movement to get the 3.1 Honeycomb update installed. While parts of this tutorial may remain valid, the overall synopsis is not. For those of you that have used this guide I can vouch for the procedure in the thread linked below as a viable option to install the 3.1 update.
Thread to 3.1 Android Update
This tutorial was written for the NooB’s among us (like me) that are new to this stuff and are having a hard time “piecing together” all of the steps. While I am actually a not quite a beginner, NONE of these steps/methods/files have been developed by me. I have simply compiled the procedure in a document that I hope will be useful. With this in mind all the credit belongs to the many individuals that contribute in the XDA Developers forum. I have reviewed many posts by many people and have used all of the information along the way. I have intentionally chosen NOT to mention any specific names for fear that I will leave someone out. If you see anything herein that reminds you of something you posted then it probably is true and you are respectfully THANKED!!!
THIS TUTORIAL WAS CREATED AND TESTED ON THE US WIFI ZOOM. THE PC WAS RUNNING VISTA 32BIT
As a courtesy I will attempt to keep this post up to date with links to revised files. Bear in mind that I performed my upgrade using the original information/links and it was successful. I suggest that since this tutorial is for beginners that you follow the ORIGINAL links to complete the guide. Once you get that far you should have a better understanding of the procedures and be ready to "experiment" by flashing new kernals, recoveries, rom's, etc., using directions found in the corresponding section(s) of the development forum. After-all that is the real reason for most of this stuff anyway. As an example.... there is a 5/3 update below which adds links to newer versions of the Tiamat Kernel and Clockwork Mod. While you could probably just download and use the updated versions of these files in conjunction with this tutorial, I have NOT personally verified this to work. If anyone does try, or if the Dev's want to chime in, please post so that I can update accordingly. Thanks.
5/3/2011 --- UPDATE: Added Links to updated Tiamat Kernel (1.4.1) & Clockwork Mod (3.0.2.8) and added links to discussion threads.
5/11/2011 --- NOTICE: If you are wanting to upgrade to the recently released 3.1 Honeycomb Update than I suggest you re-consider following this guide. The upgrade procedure requires that the device be stock or the update will fail. Furthermore there has not been a Kernel Developed yet that works with 3.1 and some users were complaining about issues with ClockWork Recovery after applying 3.1. See the development section for more information
A) Installing ADB
ADB stands for Android Debug Bridge and simplistically stated will be used to send commands to your XOOM using the keyboard on your PC. In essence your PC will be acting like a terminal. ADB is included in a package known as the Android SDK. The following steps should be taken to insure a successful install of the SDK, therefore giving you access to ADB.1. Install Java JDK : http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u25-download-346242.htmla. Download appropriate Java SE Development Kit (JDK) from link above
b. Double click to Install JDK
c. Accept Setup Defaults2. Install SDK Starter Package: http://developer.android.com/sdk/index.htmla. Download SDK Starter Package from link above. There are versions available for Microsoft Windows, Linux and Mac OS X. In case of Windows, both an installer and a zip file are available but there isn’t any need to use the installer as a formal installation is not required. Download the ZIP file.
b. Once you have downloaded the SDK, simply extract the compressed file to a location on your computer. In our case, we have extracted it to the root of our C drive and that makes [FONT="]C:\android-sdk-windows[/FONT] the installation location of the SDK. From here onwards, we shall be referring to this location as the ‘SDK folder’.3. Download the SDK Platform Tools using the SDK Mamager.a. Browse to the SDK folder and launch SDK Manager.
b. When launching it for the first time, it will present you with a window to choose packages to install. The first option begins with ‘Android SDK Platform-tools’. Make sure it is checked, and uncheck all the other packages for now. You can check/uncheck a package by simply double clicking on the package. Again, the only package you want to install is the Android SDK Platform-Tools.
c. Once the process is done, you will have a ‘platform-tools’ folder inside your SDK folder. That folder will include ADB and all its dependencies.
d. Make a copy of the File “fastboot.exe” which is in the “tools” directory and place it in the “platform-tools” directory.B) Install XOOM USB Driver
Just to be sure your XOOM is recognized by your PC it is recommended that you install the latest USB drivers for your system.1. Install MotoHelper : http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Driversa. Download the Driver with MotoHelper from the Link above
b. Double Click downloaded file and follow on-screen instructions to install.C) Unlock Bootloader
Unlocking the bootloader gives you full control over the device so you can flash new Recovery’s, kernels, ROM’s, ETC. THIS STEP WILL DELETE ALL DATA AND SETTINGS ON YOUR XOOM.1. Put XOOM in Debug modea. On the device, go to home screen, press [FONT="]Apps[/FONT] > >Settings>>Applications>>[FONT="]Development[/FONT], and enable [FONT="]USB Debugging[/FONT].
b. Now connect your XOOM to the PC via USB. New hardware installation should begin and it will start looking for and installing the drivers.
c. A prompt should appear that states the drivers were installed successfully. On my PC the AutoPlay Device Options also appeared. I clicked “Open Device to View Files” and saw the device Storage with 27.8 GB free of 28.7 GB.2. Execute ADB Commandsa. Open a command prompt by navigating to the ‘SDK Folder’, Holding the shift key, right clicking on the “platform-tools” folder and selecting “Open Command Window Here” from the popup menu.
b. In the new command window type: adb reboot bootloader and press enter.
c. Wait for the Dual Core screen with “Starting Fastboot protocol support” in the upper left corner to appear and then type: fastboot oem unlock in the command window and press enter. You should see: “To continue, follow instructions on the device’s display…”.
d. Read the WARNING on you XOOM and either Continue Below or Cancel following the on-screen instructions.
e. If you decided to continue then on the XOOM Push Volume Down Button to change the selection from “Cancel” to “I accept” and then press the Volume Up to select that choice.
f. You will be questioned again so Push Volume Down then Volume Up to confirm you want to UNLOCK your device. You will see “Device Unlock operation in progress…” “Formatting UDA”
g. When the operation completes the device will read”Device unlock operation done – rebooting…” and the device will reboot. The windows new hardware “gong” will sound a couple of times during this procedure. After this step when my XOOM rebooted I also saw an “MTP Device” driver Install dialog box on my PC. Unplug the device, and quickly perform the initial set-up. You can “Skip” any steps that will allow you to (like WiFi setup). Just get back to the home screen and continue below:
h. Verify that USB debugging is still enabled and if not re-enable it as outlined above.
i. Re-connect your XOOM to the PC and close any AutoPlay dialog.D) Install Custom Recovery
A custom recovery allows you to flash files created by community developers such as ROM’s, Radios, Kernels, Themes, ETC. It also allows you to perform special tasks such as system backup’s, partitioning, cache wiping, ETC. As of 4/28/2011 the generally accepted custom recovery for the XOOM is ClockworkMod Recovery v3.0.2.5. Clockwork Discussion Threada. Download Clockwork Mod from here: ClockworkMod 3.0.2.5
3.0.2.8 ClockworkMod
b. Place the File “recovery.img” that you just downloaded in the “platform-tools” directory
c. In the previously open command window (if you closed it then re-open as described above) type: adb reboot bootloader and press enter.
d. The device will reboot into bootloader mode (as described above) and when this completes type: fastboot flash recovery recovery.img
e. Check the screen of your XOOM and see: “Flashing StorMgr partition recovery STATUS: - done!
f. Type: fastboot reboot in the command window and press enter.
g. Your XOOM should now boot with no noticeable changes.
h. In your command window type: adb reboot recovery
i. Your XOOM will reboot and an unfamiliar screen will appear. This is the “recovery” program and at this time you should simply verify that you see a reference to ClockworkMod Recovery in the upper left corner of the XOOM. This indicates that our efforts have been successful.
j. When my device rebooted into recovery I also saw additional Device Drivers install. This took a little while and I waited to do anything until I received the “Device Driver Installed Successfully” dialog.
k. Navigate in ClockworkMod Recovery by using the volume up/down to “move” and the power button to “select”. Look for reboot system, highlight it and hit the power button. Your zoom will reboot normally.
OPTIONAL STEPS
l. At some time later (AFTER YOU ARE ROOTED) to avoid the need to execute ADB commands to enter recovery, I suggest you look for a free application called “Quick Boot”, by Sirius Applications from the market.
m. Once Quick Boot is installed run it and simply select “Recovery” to boot into ClockworkMod. E) Install Custom (Tiamat)Kernel to your XOOM
The Tiamat Kernel we have chosen includes many advantages over the “stock” kernel most notably being support for the SD Card slot which as of this writing has still not been released by Moto. Tiamat Discussion Threada. Download the file “Tiamat_Xoom-v1.4.0.zip” from here: Tiamat Kernel 1.4.0
Tiamat Kernel 1.4.1 A big Thanks to Cam3era who acted as a gunia pig for this....Apparently you are better off flashing the 1.4.0 Kernal first and then flashing the 1.4.1. Details are in the Tiamat Thread
b. Make sure you have an SD Card in your XOOM. Some people are having issues with the system reporting the wrong size of the SD card and it has been suggested that you format your card in another android device prior to using it with your XOOM. Another “trick” was to use a small capacity card. Apparently this may still be a current issue so I recommend you format you card prior to use. I personally had a 1GB Micro SD that I formatted in my Android Phone.
c. Enter Recovery via adb by typing: adb reboot recovery in your terminal window and press enter.
d. Now, using the Volume Up and Volume Down buttons on the XOOM to move the prompt and the power button to execute a selection: i. Go to "mounts and storage"
ii. Select "mount USB storage"
iii. Your SD Card will now be mounted on your computer. Copy the Tiamat kernel zip you downloaded above onto the SD Card.
iv. "Go Back" TWICE then go into "install zip from sdcard" then "choose zip from sdcard"
v. Navigate to the zip file and select it.
vi. Navigate to “Yes – Install Tiamat_Xoom-v1.4.0.zip” and select it. It will now flash and you will see some scrolling text and a progress indicator.
vii. Wait until it says “Install from sdcard complete.
viii. Back out to main menu and reboot.e. After the XOOM reboots (this could take a while) check to insure that USB debug mode is still enabled. If not, re-enable it as described above.F) Root the XOOM and Install Superuser APK
Root access is similar to “administrator” privileges and gives you the power to run specially developed programs that take advantage of these additional rights. An example would be a program called titanium backup which coupled with the “super user” privileges can perform backup duties not available in “non-root” environments. The following file was obtained and discussed here: Link
a. Download the file Root_Xoom.zip from here: http://forum.xda-developers.com/attachment.php?attachmentid=579548&d=1303896724
b. Connect your XOOM to the PC (again be sure Debug mode is enabled) and close any AutoPlay dialog boxes that pop up.
c. In the same command window used previously type: adb reboot recovery
d. Now, using the Volume Up and Volume Down buttons on the XOOM to move the prompt and the power button to execute a selection: i. Go to "mounts and storage"
ii. Select "mount USB storage"
iii. Your SD Card will now be mounted on your computer. Copy the “Root_Xoom.zip” file you downloaded above onto the SD Card.
iv. Go Back" TWICE then go into "install zip from sdcard" then "choose zip from sdcard"
v. Navigate to the “Root_Xoom.zip” file and select it.
vi. Navigate to “Yes – Root_Xoom.zip” and select it. It will now flash and you will see some scrolling text and a progress indicator.
vii. Wait until it says “Install from sdcard complete.
viii. Back out to main menu and reboot.e. After the XOOM re-boots check to see that you have a new App in the Drawer called “Superuser”.G) CLEANUP
As you become more at ease with using Clockwork Recovery you will use it more and more. There are many more features than can be described here and after all, that is beyond the scope of this tutorial. I highly recommend that you seek out more information about this tool so you can put it to good use. One term you will see used a lot is “wiping”. Wiping does exactly that to a specific partition(s) and/or file(s) thereby insuring that a new installation is “clean” and no “remnants” of prior information exist. The upside to this “cleaning” is that there is less chance of corruption from using older (or incompatible) versions of files or data and the downside is that this “data” may contain useful information such as high scores, completed game levels or even previously remembered passwords. You should learn how to back-up this data using Titanium Backup or another backup application and manually reload it after your upgrade is considered “stable”. This allows you to wipe and thereby insure that any “issues” you experience are not related to “remnants”. So, with this all said, I recommend that you now Wipe your User Data and Cache. Again, if you have not backed up, this will erase and reset things that you may not want erased or reset. Proceed with caution!!!!
a. Enter Recovery via quickboot or adb as described above.
b. Using the Volume and Power Buttons as described above navigate to “wipe data/factory reset” and select it.
c. Navigate to “Yes – delete all user data” and select it. Wait until it says “Data wipe complete”.
d. Navigate to “wipe cache partition” and select it.
e. Navigate to “Yes – Wipe Cache” and select it. Wait until it says “Cache wipe complete”.
f. Navigate to “reboot system now” and select it.
g. Set up your rooted, custom recovery, custom Kernel XOOM!! ENJOY
I really appreciate your post. This should be sticky
P/s: you can make this instruction even better if you include some pics that can illustrate the process, some frequently errors and solutions to fix those errors.
Thanks for the kind words!
One step at a time my friend. This was my first attempt at creating a tutorial and I tried to handle the "pictures" with very detailed wording. Embedding screenies into future efforts is on my to do list.
The bottom line regarding this is..... I created the tutorial before I even took my XOOM out of the box and then followed it to see if it worked. While I had some minor issues with the original draft, I believe they have all been taken care of in this final.
I expect that if any issues are encountered, it will involve the SD Card size which seemed to be a common issue for some. I had NO problems with mine.
And, while I'm at it....... I was a little hesitant to include the information on "quick boot". Some members (and I'm taking this off the top of my head right now) had issues using clockwork when it wasn't initiated using the adb reboot recovery command. I seem to recall that there was a difference in this regard between the WiFi and 3G versions. In any case if Clockwork does not seem to be working for you then stick with starting up recovery using adb and NOT Quick Boot. Having Quick Boot available in your app drawer is recommended however in case you ever experience issues mounting the device to your PC.
tritran18518 said:
I really appreciate your post. This should be sticky
P/s: you can make this instruction even better if you include some pics that can illustrate the process, some frequently errors and solutions to fix those errors.
Click to expand...
Click to collapse
Thanks
This is exceptionally well done. A tremendous resource. I hope you will keep it up to date. I will refer to it often. Thank you!
I hope this works.....With this it is time to root. Thank you for a great step by step instructions.
This is an excellent tutorial! Thank you. I may take the plunge now. One request : would you be so kind as to add the steps to return to stock and relock the wifi version?
Sent from my Xoom using Tapatalk
See this tread: Stock Image
I have NOT done this procedure but will follow that thread to see how it turns out.
Someone DID apparently re-lock the device but I don't know if that procedure removes all indications that the device was un-locked in the first place.
cam30era said:
This is an excellent tutorial! Thank you. I may take the plunge now. One request : would you be so kind as to add the steps to return to stock and relock the wifi version?
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Didn't really want to bump my own thread but I was hoping someone would have tried this by now. Anybody?
I didn't put this "guide" in the development section because I didn't actually develop anything. Perhaps I should have?
This is an awesome step by step instruction! Good Work! Thanks a lot!
Land Master said:
Didn't really want to bump my own thread but I was hoping someone would have tried this by now. Anybody?
Click to expand...
Click to collapse
Ran through it yesterday on my father in law's new Xoom, worked great!!!
I was holding out for HTC flyer with pen, or Transformer with keyboard...
But, was impressed and may be going with Xoom now myself.
Thanks so much for the guide, it worked very well and he's happily tethered to adhoc wifi on his droid now, so very thankful as well.
Sent from my SCH-I500 using XDA App
Awesome tutorial! Now I have a place to point new users to when they hijack my thread
bigrushdog said:
Awesome tutorial! Now I have a place to point new users to when they hijack my thread
Click to expand...
Click to collapse
Thanks BRD for everything you do. I added links to the 5/1 files but also a disclaimer. Your thoughts on this would be appreciated.
Feedback
Land Master, I just used your tutorial to root my wifi Xoom. It is very well written and easy to understand and follow. I installed the Tiamat 1.4.1 kernel. Worked fine. Have confirmed that I have Superuser permissions. And "about" shows the Tiamat 1.4.1 kernel.
First a suggestion: Under "Install Custom Kernel" your instruction states "c. Enter Recovery via “Quick Boot” application or thru adb". I tried to use Quick Boot but could not (obviously) because I was not rooted yet. Had to use ADB, which worked fine. You may want to modify the instructions here to remove the Quick Boot option at this point?
Second, I have a request for help. I purchased a Sandisk 16gb micro SD card. Formatted it in my rooted Droid Incredible. Placed it in my Xoom and rebooted. I can not find my external SD Card with Root Explorer. Any suggestions?
cam30era said:
Land Master, I just used your tutorial to root my wifi Xoom. It is very well written and easy to understand and follow. I installed the Tiamat 1.4.1 kernel. Worked fine. Have confirmed that I have Superuser permissions. And "about" shows the Tiamat 1.4.1 kernel.
First a suggestion: Under "Install Custom Kernel" your instruction states "c. Enter Recovery via “Quick Boot” application or thru adb". I tried to use Quick Boot but could not (obviously) because I was not rooted yet. Had to use ADB, which worked fine. You may want to modify the instructions here to remove the Quick Boot option at this point? Corrected This THANKS!
Second, I have a request for help. I purchased a Sandisk 16gb micro SD card. Formatted it in my rooted Droid Incredible. Placed it in my Xoom and rebooted. I can not find my external SD Card with Root Explorer. Any suggestions?
Click to expand...
Click to collapse
Cam30era.....Thanks for your help. Honestly I haven't played with the SD Card in mine but do know that I have an "external" directory that is viewable in Root Explorer under "sdcard". With this said you should check the Tiamat thread because I believe the SD card "stuff" was removed in 1.4.1 because it was sketchy. I personally am still on 1.4.0.
I don't really want to take people away from the "official" (Tiamat) thread because they will all need to "learn" the same way most of us have.... by trial and error. It is my belief that this is what makes all of this fun and worthwhile. With that said however, it is my belief that a "Stable" SD Card fix will not become available until after the official Moto update drops.
My goal here was to get people to a "starting point" thus allowing them to get their feet wet and subsequently give them the tools (Root, Recovery, ETC) to continue the journey into flashing different stuff. This is why I wrote the disclaimer above.... Hoping that people would just stick to what is "known good" and march onward by researching other threads and learning as they go.
Land Master said:
Cam30era.....Thanks for your help. Honestly I haven't played with the SD Card in mine but do know that I have an "external" directory that is viewable in Root Explorer under "sdcard". With this said you should check the Tiamat thread because I believe the SD card "stuff" was removed in 1.4.1 because it was sketchy. I personally am still on 1.4.0.
I don't really want to take people away from the "official" (Tiamat) thread because they will all need to "learn" the same way most of us have.... by trial and error. It is my belief that this is what makes all of this fun and worthwhile. With that said however, it is my belief that a "Stable" SD Card fix will not become available until after the official Moto update drops.
My goal here was to get people to a "starting point" thus allowing them to get their feet wet and subsequently give them the tools (Root, Recovery, ETC) to continue the journey into flashing different stuff. This is why I wrote the disclaimer above.... Hoping that people would just stick to what is "known good" and march onward by researching other threads and learning as they go.
Click to expand...
Click to collapse
I'll try flashing 1.4.0 and then back to 1.4.1 and let you know. Thanks for the suggestions.
OK. I just tried to flash 1.4.0 from CWM. Got following error message:
E:Error in /sdcard/tiamat_xoom-v1.4.0.zip
(status 0)
Installation aborted.
I'm getting help now on the Tiamat thread. I'll keep you posted on how this gets resolved.
Land Master, FYI: I successfully flashed 1.4.0. This did create a fully functional external folder inside sdcard. I then flashed 1.4.1 and it's a go. So you may want to modify your tutorial to indicate that you must flash 1.4.0 first.
A big "thank you" for this excellent tutorial, and for your help. I probably would not have rooted my Xoom without this outstanding aid.
cam30era said:
Land Master, FYI: I successfully flashed 1.4.0. This did create a fully functional external folder inside sdcard. I then flashed 1.4.1 and it's a go. So you may want to modify your tutorial to indicate that you must flash 1.4.0 first.
A big "thank you" for this excellent tutorial, and for your help. I probably would not have rooted my Xoom without this outstanding aid.
Click to expand...
Click to collapse
Very glad you got it sorted. I added your suggestion to the OP.
mbowe said:
It worked very well and he's happily tethered to adhoc wifi on his droid now.
Click to expand...
Click to collapse
Ad-hoc? A stock xoom doesn't support this but a rooted one can now? Didn't realize that had been enabled.
hi,
can i install the kernel and the custom recovery without root ?
i thought i need to have root first....
Alright guys,
This is for everyone that is not using windows or mac.
First of all - congrats! You made the right decision by not using them. Ha-ha!
Also - Thanks to everyone that was involved in getting us the so much needed S-OFF - Developers and Testers.
Now, to get S-Off you need to go to http://revolutionary.io/
Just in case - read everything that is in there, and remember that this is a Beta release, so sh*t can go wrong.
Click on "Download For Linux" . This will download revolutionary-0.3pre7.tgz
Now open Home folder, navigate to Downloads, find the file that you just downloaded, right click, and choose "extract here".
Or if you are using the console - you need to do this:
Navigate to the Downloads folder and
Code:
tar -zxf revolutionary-0.3-pre7.tgz
Now open your terminal, and navigate to the Downloads folder. You can do that by typing
Code:
cd ~/Downloads
Once you are in there - do the following:
Code:
sudo ./revolutionary
or if you are root, just do
Code:
./revolutionary
In general, its not a very good idea to stay logged in constantly as root, so yeah.
Once you downloaded the file - it redirected you to the Generator, where you need to put in your information about the phone.
Once you run revolutionary - you can find all the information needed in there, just put in the information, click on "generate", highlight the code, right click, copy, and then go to the console, right click, paste, and hit enter.
Once you get root and everything else, it will ask you if you want to install CWM. It is important to have that, so please choose "Y".
And now you can sit back and enjoy how this is magic
[EDIT]
If you have any problems with revolutionary finding the device - please make sure that you did add the appropriate udev rules to the file /etc/rules.d/51-android.rules
To make sure that your computer sees the phone - just type
Code:
adb devices
If you see it as "??????????????" - then you do need to follow the next guide to add the udev rules.
For more information on how to do that - please follow THIS GUIDE
For more information on how to use ADB under Ubuntu - please check out THIS GUIDE
Thanks, this worked like a charm! Thank to the devs that brought this to us! I've been eagerly awaiting this, almost took my bro's MT4G just to get my flashing fix!! All I need is an AOSP Rom and I'm golden, lol
I'm getting "waiting for device..."
Is there a certain point when I need to plug in my Sensation? I'm able to mount the phone with no issues in linux, but for some reason revolutionary won't identify it.
Wow, 2 minutes with no hiccups on a UK Vodafone branded Sensation. Just carrying out a quick nandroid. Thanks for the tut, much appreciated.
Thanks, will be using this to S-OFF my Sensation when I get home later today!
Ubuntu ftw
Sent from my HTC Sensation using XDA Premium App
Thareal1 said:
I'm getting "waiting for device..."
Is there a certain point when I need to plug in my Sensation? I'm able to mount the phone with no issues in linux, but for some reason revolutionary won't identify it.
Click to expand...
Click to collapse
Did you add the add appropriate udev rules to the file /etc/rules.d/51-android.rules ?
Or with other words, when you are using adb under ubuntu - when you do adb devices - do you see your device with "?????????????" or do you see it like its really installed with numbers ?
If you havent added the udev rules - you can find more information on how to do it HERE
t0ny0 said:
Alright guys,
This is for everyone that is not using windows or mac.
Click to expand...
Click to collapse
Holy smokes, was this easy!! Between your guide and ikhzter's sticky, I had root in about 10 mins. 15 mins later I had a full TB backup. Outstanding!
marcjw said:
Holy smokes, was this easy!! Between your guide and ikhzter's sticky, I had root in about 10 mins. 15 mins later I had a full TB backup. Outstanding!
Click to expand...
Click to collapse
Glad I could help. Plus the guys that made Revolutionary really did their best to make life easy for us
Hi
I've tried to do that but :
Acquiring root (method 3)...
Sending in Caroline...
Cleaning up...
Rebooting to fastboot...
When life gives you lemons, don't make lemonade. Make life take the lemons back!
Waiting for fastboot...
Rebooting to fastboot (again)...
Rebooting to fastboot (yet again)...
Rebooting to fastboot (Once moar...)
SUCCESS - Life gave us lemons, we didn't make lemonade!
Do you want to download (Internet connection required) and flash ClockworkMod Recovery? [Y/n] y
Downloading recovery for your phone (pyramid)...
^C
Click to expand...
Click to collapse
At this section i've lost my internet connection and nothing happend, then i did ctrl+c and after rebooting i've tried to do it again:
Waiting for device...
Found your device: HTC Sensation Z710e (pyramid-1.17.1011, Android: 2.3.3, ROM version: 1.35.720.1)
Your device is not supported at this time.
Click to expand...
Click to collapse
now i dont have ClockworkMod.
I've installed rom manager to install ClockworkMod, the romManager says that it couldnt find sudo user at /system/(x)bin/su
when im rebooting into recovery mod, it says that device is S-OFF.
to access root i found this on http://revolutionary.io/
Does Revolutionary give me root?
No. You will need to flash this zipfile from recovery.
Click to expand...
Click to collapse
when i tried to flash it, it says that signauture verification failed...
i've read from this page that i must install clockworkMod to disable signature verification but rom manager says "an error occured while attemting to run privileged commands!"
it seems that im in a loop...
pezhman32 said:
Hi
I've tried to do that but :
At this section i've lost my internet connection and nothing happend, then i did ctrl+c and after rebooting i've tried to do it again:
now i dont have ClockworkMod.
I've installed rom manager to install ClockworkMod, the romManager says that it couldnt find sudo user at /system/(x)bin/su
when im rebooting into recovery mod, it says that device is S-OFF.
so where doese my root gone?! what should i do now?!
Click to expand...
Click to collapse
You can find more information here - http://forum.xda-developers.com/showthread.php?t=1192300
Or to be exact - you need this:
ikhzter said:
STEP 2. To INSTALL Clockwork Recovery mod- v4.0.1.4 from Revolutionary. Issue With not charging when Device is completely switched off - DOES CHARGE WHEN HIBERNATING (SWITCHING OFF on stock rom) WITH FASTBOOT ENABLED
YOU MUST READ ABOUT THE CHARGING ISSUE in post 3 below before installing!!!!!
1. Download clockworkmod recovery by Revolutionary for the Sensation HERE:
2. Copy the PG58IMG file into the Root folder of your SD card (The main Folder of your Memory Card)
3. Turn off your phone FUlly and reboot into the Bootloader/HBOOT screen (see post above on how to get to hboot screen)
4. Press Volume up to Accept when it asks" Do you want to start the update"
5. Press Power Off to Reboot back to android after installation is successful (normal screen with homescreen)
6. Delete PG58IMG from your memory card and you can now root using step 3 below or install a custom ROM using CWM (Customs Roms are already rooted)
7. Turn the phone back on. click settings > Power > ensure fastboot is enabled (ticked). This will help you charge incase your battery dies. If you hibernate (or switch off on stock roms) with fastboot enabled your phone will still charge
IF YOUR BATTERY IS LOW, SWITCH OFF WITH FASTBOOT ENABLED TILL YOU CAN CHARGE IT (Press Hibernate (on stock Roms) or power off if you don't have hibernate)
IF YOUR PHONE BATTERY DIES WHILST YOU ARE USING IT. DO NOT POWER IT ON OR PULL THE BATTERY OUT.
Make sure you have had it on charge for at least a few minutes then turn it on as normal and continue charging
Currently with fastboot enabled when your phone dies it will hibernate. allowing you to still charge it. If you plug in your charger then switch on, it will boot back up in a few seconds as fastboot is active and it will resume from where you left off.
Turning off without fastboot means your phone will fully turn off not hibernate and your phone will not charge when turned off.
Step 3. To permanently root your Sensation - (This means you will NOT LOSE ROOT on rebooting) DOES NOT AFFECT WIFI
1. Download the file su-2.3.6.3-ef-signed.zip from here: DOWNLOAD
2. Copy su-2.3.6.3-ef-signed.zip to your SD card root folder (main folder of your memory card)
3. Start clockworkmod recovery (instructions below)
4. BACKUP YOUR ROM USING CWM BEFORE ATTEMPTING ROOT!
5. Navigate to "Backup & Restore" using the Volume Down button and press select (power button to select) then select "Backup"
6. Select "install zip from sdcard" after backing up
7. Then select "Choose zip from sdcard"
8. Then select "su-2.3.6.3-efgh-signed.zip"
9. Then select "Yes - install su-2.3.6.3-efgh-signed.zip" to confirm
10. Then go back
11. Then reboot.
12. You're rooted!
Click to expand...
Click to collapse
t0ny0 said:
Alright guys,
Code:
cd /home/username/Downloads
where "username" is the username that you are using.
Click to expand...
Click to collapse
Not trying to be a troll but a little friendly advice =)
instead of /home/username/ and having them put in their username (which some might not know) use ~/Downloads
"~" replaces "/home/username" =)
nice little write up
jassycliq said:
Not trying to be a troll but a little friendly advice =)
instead of /home/username/ and having them put in their username (which some might not know) use ~/Downloads
"~" replaces "/home/username" =)
nice little write up
Click to expand...
Click to collapse
Always appreciating advises
Changed it, thanks !
Yay delighted been waiting for this for like aaaaaaaages and now I'm happy hahahah Cheers lads fair play to yeas,,
@t0ny0 : that was a complete answer which solved my problem
thx G
pezhman32 said:
@t0ny0 : that was a complete answer which solved my problem
thx G
Click to expand...
Click to collapse
Glad I could help
The following post is just a TESTED collection of tools and procedures that were found over at XDA forum or elsewhere on the Internet.
I do not take any credit for all those nice scripts and manuals - I just put them together for the young community of IdeaPad A2107A owners.
Below you will find methods of getting root and Clockwork Mod Recovery v 6.0.1.5 on IdeaPad A2107A (I own the -H version with dual SIM and ca. 4 GB of internal memory).
All processes were tested by me and are working well but obviously you are responsible for your actions.
My device runs on ICS 4.0.3, compilation A2107A-H_S341 and has a couple of European languages (tablet bought in Poland).
What you need is installed ADB drivers so the PC can "talk" to you tablet. You will find a lot of guides on the net - just make sure Windows device manager shows Android Device - Android ADB Interface or something close to that.
I also advise to enable USB debugging and allow installing applications from unknown sources - all in your tablet's settings.
Once you make sure you have done the above you're good to go.
So let's go!
Download this: http://www.mediafire.com/download.php?5o7dm16d430lwal (un7zip) and read as follows:
1 - Root
The method I chose is for patient people - the device will reboot 3 times during this process.
a) connect your tablet to the PC, open "1 - 4.03root" folder and run "root.bat"
b) just after you run the .bat the device will reboot and in the command prompt you will see "Press any key to continue . . ." - WAIT until the tablet boots up completely. When you see the lockcreen THEN hit a key in the command prompt.
c) the above will happen 2 more times - always WAIT for the tablet to boot completely.
This process will install Superuser and RootExplorer so find those apps and see if the root works.
2 - Backup the whole ROM that is on your device - will be useful with making the CWM recovery.img file.
For this you will need ca. 2GB of memory so I advise at least 4GB sdcard.
I also advise to go to the settings and in the memory tab set the "Default write disk" to "SD storage" - this makes the microSD the primary "sdcard" - makes things easier with backups etc.
ALSO in the settings set the screen to stay on for at least 10 minutes - this is how long it will take to do the full ROM dump - important to keep the script alive.
To avoid any issues turn the flight mode on so no new "data" is received by the device.
Once you're done open "2 - Backup" folder from my 7zip and copy the "gscript" folder to the root of your sdcard. Now install "GScriptLite.apk" and run it (needs root access!).
In the app hit the menu button and pick "Add Script" ->"Need SU?" must be checked -> "Load file" -> select "back_mt6575_a4_v2c.sh" -> save and click the script.
As I said - wait ca 10 minutes for the scrip to finish. Now you will have a nice backup in the SD - look for "backup_v2" folder - copy it to your PC.
3 -Mobileuncle - it's in the Google Play Store but you won't find it with our tablet - supposedly incompatible. Bull*hit!
Open "3 - Mobileuncle" folder, copy the apk to your device and install. We will come back to this later.
4 - How about the CWM? Yes!
Open "4 - CWM 6015" - you will find a PDF there - read the instructions. The subfolder "michfood" contanis all the scripts you need so you don't have to download anything else.
ATTENTION - the "recovery.img" used in this process is YOUR "recovery.img" that you dumped in step 2. So find your backup from step 2 and the original "recovery.img" from your ROM.
ATTENTION - our device is MT6575 so you pick nr 1 in the command prompt.
5 - Once you have the new "recovery.img" with CWM (it is actually smaller than the original file) copy it to the root of your sdcard.
Now open the Mobileuncle Tools you installed in step 3 and hit "Recovery Update".
There, at the very top of the screen you will see your new CWM recovery file - hit it and then confirm the update. It takes a second!
Now you will be asked to boot into recovery mode - go ahead, try it
If the tablet booted in CWM then you are all set!
REMEMBER - to go into the recovery mode while the device is OFF you need to:
1 - hold the power button for ca 3 seconds
2 - let it go and in the same moment press BOTH Vol + and Vol - buttons.
REMEMBER 2 - the CWM 6.0.1.5 makes backups in a bit different way than the old CWM - read here :http://forum.xda-developers.com/showthread.php?t=1846446
It also appears that the key to modding our tablet is the MT6575 processor - a lot of tools just need to support this processor, the device itself is not so important.
All the best.
Mike.
P.S.
A little film how it looks: http://www.youtube.com/watch?v=tM3Sdwf2i4M
------------------------------------------------- UPDATE 1 ---------------------------------------------------------
For those who are running the same compilation as I am (A2107A-H_S341):
- you can download my recovery file from here: http://www.mediafire.com/download.php?um372gh6ayf6t6w
To use it you need to do:
1 - Root
(optional backup with GScriptLite.apk)
2 - flash the recovery file with Mobileuncle
Be careful and make sure you have a backup if you want to try this file with another compilation.
Cheers.
------------------------------------------------- UPDATE 2 ---------------------------------------------------------
Tested (by user: manwithmanypiercings) USB drivers are in this post: http://forum.xda-developers.com/showpost.php?p=34651039&postcount=51
------------------------------------------------- UPDATE 3 ---------------------------------------------------------
I think there is even easier way than the one I originally posted above.
BUT I cannot be sure that it will work with all of you - the reason is that I made so many changes to my A2107A-H that I do not know whether this method works "just because it's universal" or because my tablet was tweaked far enough.
On the other hand when you consider it reasonably it looks like it's quite simple and there is no particular reason why it shouldn't work with a stock A2107A.
So...
What you need:
1 - this package: http://www.mediafire.com/download.php?fbuzi5xjofs7vgf
2 - PC running Windows 7 would be the best (7 gave me no problems at all - takes 1 minute to do it). I made it on Windows 8 as well but there is a lot more fuss to install the proper driver.
What you do:
1 - turn on USB Debugging on your tablet
2 - connect the tablet to your PC (if it's the 1st, some default drivers will install - that's ok)
3 - tap on the notifications area in the "Connect as" change to "MTP" - this is quite important !
4 - from the downloaded package run the "Flash_tool.exe"
- click "Scatter-loading" on the right and find "MT6575_Android_scatter_emmc.txt"
- in the list in the lower part of the window you MUST have the "PRELOADER" (super important) and "RECOVERY" ticked and leading to the correct files. The PRELOADER = "preloader_lenovo75_a2_ics.bin" (in the package) and the RECOVERY is the recovery file of your choice -> there are 3 in the package - pick the one you want. You can flash them over and over so if you don't like one then try the other.
5 - click "Download" above - you will see a prompt saying that not all images were loaded - that is fine - we only want to flash the RECOVERY - so click "Yes"
6 - now the Flash tool is waiting for the tablet - press "reset" on the back - Windows will recognize a new device (and WILL NOT find the driver unless you have done it before) - no worries, you have the correct driver.
7 - open Windows "Device manager" and locate the MT65..... unrecognised device -> update / install driver -> point Windows to "USB VCOM Driver" folder from the package and pick your system. My Windows 7 found the driver on the spot but asked to confirm the install - "insecure" driver - I obviously clicked "install anyway" and so should you.
8 - once the driver is loaded the Flash tool will flash the new recovery file - you will see some colour progress bars in the program - at the end you should see a green circle.
That is it. Unplug the tablet, press reset on the back and you can now enter the recovery mode.
FUN FACT: the "reset" button on the back is not really a reset button, it's more like physical cut off button to temporarily disconnect the battery.
I have the Lenovo A2107A under Vodafone's brand Vodafone Smart Tab II 7
It has Android version 4.0.4 and compilation: A2107A_A404_010_002_120913_VODA
Imanaged to root it and install CWM using this thread. But somehow I was not able to create the CWM modded recovery.img
I used the one provided here and it worked fine.
Thanks for this.
I can't connect tablet to PC
csns said:
The following post is just a TESTED collection of tools and procedures that were found over at XDA forum or elsewhere on the Internet.
I do not take any credit for all those nice scripts and manuals - I just put them together for the young community of IdeaPad A2107A owners.
Below you will find methods of getting root and Clockwork Mod Recovery v 6.0.1.5 on IdeaPad A2107A (I own the -H version with dual SIM and ca. 4 GB of internal memory).
All processes were tested by me and are working well but obviously you are responsible for you actions.
My device runs on ICS 4.0.3, compilation A2107A-H_S341 and has a couple of European languages (tablet bought in Poland).
What you need is installed ADB drivers so the PC can "talk" to you tablet. You will find a lot of guides on the net - just make sure Window device manager shows Android Device - Android ADB Interface or something close to that.
I also advise to enable USB debugging and allow installing applications from unknown sources - all in your tablet's settings.
Once you make sure you have done the above you're good to go.
So let's go!
Download this: http://www.mediafire.com/download.php?5o7dm16d430lwal (un7zip) and read as follows:
1 - Root
The method I chose is for patient people - the device will reboot 3 times during this process.
a) connect your tablet to the PC, open "1 - 4.03root" folder and run "root.bat"
b) just after you run the .bat the device will reboot and in the command prompt you will see "Press any key to continue . . ." - WAIT until the tablet boots up completely. When you see the lockcreen THEN hit a key in the command prompt.
c) the above will happen 2 more times - always WAIT for the tablet to boot completely.
This process will install Superuser and RootExplorer so find those apps and see if the root works.
2 - Backup the whole ROM that is on your device - will be useful with making the CWM recovery.img file.
For this you will need ca. 2GB of memory so I advise at least 4GB sdcard.
I also advise to go to the settings and in the memory tab set the "Default write disk" to "SD storage" - this makes the microSD the primary "sdcard" - makes things easier with backups etc.
ALSO in the settings set the screen to stay on for at least 10 minutes - this is how long it will take to do the full ROM dump - important to keep the script alive.
Once you're done open "2 - Backup" folder from my 7zip and copy the "gscript" folder to the root of your sdcard. Now install "GScriptLite.apk" and run it (needs root access!).
In the app hit the menu button and pick "Add Script" ->"Need SU?" must be checked -> "Load file" -> select "back_mt6575_a4_v2c.sh" -> save and click the script.
As I said - wait ca 10 minutes for the scrip to finish. Now you will have a nice backup in the SD - look for "backup_v2" folder - copy it to your PC.
3 -Mobileuncle - it's in the Google Play Store but you won't find it with our tablet - supposedly incompatible. Bull*hit!
Open "3 - Mobileuncle" folder, copy the apk to your device and install. We will come back to this later.
4 - How about the CWM? Yes!
Open "4 - CWM 6015" - you will find a PDF there - read the instructions. The subfolder "michfood" contanis all the scripts you need so you don't have to download anything else.
ATTENTION - the "recovery.img" used in this process is YOUR "recovery.img" that you dumped in step 2. So find your backup from step 2 and the original "recovery.img" from your ROM.
ATTENTION - our device is MT6575 so you pick nr 1 in the command prompt.
5 - Once you have the new "recovery.img" with CWM (it is actually smaller than the original file) copy it to the root of your sdcard.
Now open the Mobileuncle Tools you installed in step 3 and hit "Recovery Update".
There, at the very top of the screen you will see your new CWM recovery file - hit it and then confirm the update. It takes a second!
Now you will be asked to boot into recovery mode - go ahead, try it
If the tablet booted in CWM then you are all set!
REMEMBER - to go into the recovery mode while the device is OFF you need to:
1 - hold the power button for ca 3 seconds
2 - let it go and in the same moment press BOTH Vol + and Vol - buttons.
REMEMBER 2 - the CWM 6.0.1.5 makes backups in a bit different way than the old CWM - read here :http://forum.xda-developers.com/showthread.php?t=1846446
It also appears that the key to modding our tablet is the MT6575 processor - a lot of tools just need to support this processor, the device itself is not so important.
All the best.
Mike.
P.S.
A little film how it looks: http://www.youtube.com/watch?v=tM3Sdwf2i4M
------------------------------------------------- UPDATE 1 ---------------------------------------------------------
For those who are running the same compilation as I am (A2107A-H_S341):
- you can download my recovery file from here: http://www.mediafire.com/download.php?um372gh6ayf6t6w
To use it you need to do:
1 - Root
(optional backup with GScriptLite.apk)
2 - flash the recovery file with Mobileuncle
Be careful and make sure you have a backup if you want to try this file with another compilation.
Cheers.
Click to expand...
Click to collapse
csns thanks for your guide
Unfortunately I can't connect my tablet to pc in USB debbuging mode. I tried a lot of drivers from net but without success.. Pls let me know the right way to root my tablet.
optical99 said:
csns thanks for your guide
Unfortunately I can't connect my tablet to pc in USB debbuging mode. I tried a lot of drivers from net but without success.. Pls let me know the right way to root my tablet.
Click to expand...
Click to collapse
Hi there,
Try those drivers: http://www.mediafire.com/?vx2hyv7dpwlmeyy
They come from the current Android SDK but I am running a 64 bit system and I'm not sure if those drivers will work with 32 bit systems.
Fingers crossed!
I tried with yor recommend dirvers and with a lot of others and doesn't work. I have to unrecognised denices in Device Manager - A2107A-H and MTP.
I am very upset about Lenovo because their support doesn't exist.
optical99 said:
I tried with yor recommend dirvers and with a lot of others and doesn't work. I have to unrecognised denices in Device Manager - A2107A-H and MTP.
I am very upset about Lenovo because their support doesn't exist.
Click to expand...
Click to collapse
I had to use the PDANET from this link.
http://forum.xda-developers.com/showthread.php?t=1982334&page=6
Should be the first post.
Sent from my Samsung Galaxy Note running JellyBeer using Xparent ICS Blue Tapatalk 2
First of all, a ton of thanx to csns for posting this detailed procedure along with all required scripts and tools...
I have just one question...Which Modified ROM did you install as I see you have unlocked calling feature in the video you posted???
I asked because the MOD ROM by pemergency in the other thread is for the 16 GB and creates some issues in the device...But your's is 4 GB, as is mine...
Thanx in advance
makbro said:
First of all, a ton of thanx to csns for posting this detailed procedure along with all required scripts and tools...
I have just one question...Which Modified ROM did you install as I see you have unlocked calling feature in the video you posted???
I asked because the MOD ROM by pemergency in the other thread is for the 16 GB and creates some issues in the device...But your's is 4 GB, as is mine...
Thanx in advance
Click to expand...
Click to collapse
I'm glad you find my post useful.
As for the calling feature - it's not actually working
You see, to have the calling app (in other words "the phone" app) in the app drawer all you need to do is change one tiny value in framework-res.apk.
This value is telling the system weather the whole device is supposed to handle voice calls or not. I just tricked the system to make the Phone.apk visible but there is a lot more do be done in order to make a real call over the cellular network.
I've just had this tablet for a week and I didn't have much time to dig into this topic. Let's see what the weekend brings
Be patient, I think it's just a matter of time when someone posts a user friendly guide... Or search yourself and share what you find with the community.
Take care.
works fine
manwithmanypiercings
I have gained acces to tabled with PDAnet drivers...thanks a lot
csns
I followed all steps and installed CWM 6015. Very nice tutorial...I thought it's simpliest way...respect for your job
optical99 said:
manwithmanypiercings
I have gained acces to tabled with PDAnet drivers...thanks a lot
csns
I followed all steps and installed CWM 6015. Very nice tutorial...I thought it's simpliest way...respect for your job
Click to expand...
Click to collapse
Glad I could help by showing the link. Glad you got everything else taken care of.
This is an awesome post! Thak you very much.
Need help at step 4
csns said:
The following post is just a TESTED collection of tools and procedures that were found over at XDA forum or elsewhere on the Internet.
I do not take any credit for all those nice scripts and manuals - I just put them together for the young community of IdeaPad A2107A owners.
Below you will find methods of getting root and Clockwork Mod Recovery v 6.0.1.5 on IdeaPad A2107A (I own the -H version with dual SIM and ca. 4 GB of internal memory).
All processes were tested by me and are working well but obviously you are responsible for your actions.
My device runs on ICS 4.0.3, compilation A2107A-H_S341 and has a couple of European languages (tablet bought in Poland).
What you need is installed ADB drivers so the PC can "talk" to you tablet. You will find a lot of guides on the net - just make sure Windows device manager shows Android Device - Android ADB Interface or something close to that.
I also advise to enable USB debugging and allow installing applications from unknown sources - all in your tablet's settings.
Once you make sure you have done the above you're good to go.
So let's go!
Download this: http://www.mediafire.com/download.php?5o7dm16d430lwal (un7zip) and read as follows:
1 - Root
The method I chose is for patient people - the device will reboot 3 times during this process.
a) connect your tablet to the PC, open "1 - 4.03root" folder and run "root.bat"
b) just after you run the .bat the device will reboot and in the command prompt you will see "Press any key to continue . . ." - WAIT until the tablet boots up completely. When you see the lockcreen THEN hit a key in the command prompt.
c) the above will happen 2 more times - always WAIT for the tablet to boot completely.
This process will install Superuser and RootExplorer so find those apps and see if the root works.
2 - Backup the whole ROM that is on your device - will be useful with making the CWM recovery.img file.
For this you will need ca. 2GB of memory so I advise at least 4GB sdcard.
I also advise to go to the settings and in the memory tab set the "Default write disk" to "SD storage" - this makes the microSD the primary "sdcard" - makes things easier with backups etc.
ALSO in the settings set the screen to stay on for at least 10 minutes - this is how long it will take to do the full ROM dump - important to keep the script alive.
To avoid any issues turn the flight mode on so no new "data" is received by the device.
Once you're done open "2 - Backup" folder from my 7zip and copy the "gscript" folder to the root of your sdcard. Now install "GScriptLite.apk" and run it (needs root access!).
In the app hit the menu button and pick "Add Script" ->"Need SU?" must be checked -> "Load file" -> select "back_mt6575_a4_v2c.sh" -> save and click the script.
As I said - wait ca 10 minutes for the scrip to finish. Now you will have a nice backup in the SD - look for "backup_v2" folder - copy it to your PC.
3 -Mobileuncle - it's in the Google Play Store but you won't find it with our tablet - supposedly incompatible. Bull*hit!
Open "3 - Mobileuncle" folder, copy the apk to your device and install. We will come back to this later.
4 - How about the CWM? Yes!
Open "4 - CWM 6015" - you will find a PDF there - read the instructions. The subfolder "michfood" contanis all the scripts you need so you don't have to download anything else.
ATTENTION - the "recovery.img" used in this process is YOUR "recovery.img" that you dumped in step 2. So find your backup from step 2 and the original "recovery.img" from your ROM.
ATTENTION - our device is MT6575 so you pick nr 1 in the command prompt.
5 - Once you have the new "recovery.img" with CWM (it is actually smaller than the original file) copy it to the root of your sdcard.
Now open the Mobileuncle Tools you installed in step 3 and hit "Recovery Update".
There, at the very top of the screen you will see your new CWM recovery file - hit it and then confirm the update. It takes a second!
Now you will be asked to boot into recovery mode - go ahead, try it
If the tablet booted in CWM then you are all set!
REMEMBER - to go into the recovery mode while the device is OFF you need to:
1 - hold the power button for ca 3 seconds
2 - let it go and in the same moment press BOTH Vol + and Vol - buttons.
REMEMBER 2 - the CWM 6.0.1.5 makes backups in a bit different way than the old CWM - read here :http://forum.xda-developers.com/showthread.php?t=1846446
It also appears that the key to modding our tablet is the MT6575 processor - a lot of tools just need to support this processor, the device itself is not so important.
All the best.
Mike.
P.S.
A little film how it looks: http://www.youtube.com/watch?v=tM3Sdwf2i4M
------------------------------------------------- UPDATE 1 ---------------------------------------------------------
For those who are running the same compilation as I am (A2107A-H_S341):
- you can download my recovery file from here: http://www.mediafire.com/download.php?um372gh6ayf6t6w
To use it you need to do:
1 - Root
(optional backup with GScriptLite.apk)
2 - flash the recovery file with Mobileuncle
Be careful and make sure you have a backup if you want to try this file with another compilation.
Cheers.
------------------------------------------------- UPDATE 2 ---------------------------------------------------------
Tested (by user: manwithmanypiercings) USB drivers are in this post: http://forum.xda-developers.com/showpost.php?p=34651039&postcount=51
Click to expand...
Click to collapse
Hi csns,
Sorry to bother you but when I try drag and drop my original "recovery.img" to "cwmr 6015.bat" in the "michfood" folder, I get a warning message "System cannot find the specified file "C:\users\....\recovery.img" "recovery" and the bat script exits...I have tried the following:-
1. Copy the folder and file "michfood" and my original "recovery.img" file in all possible alternate locations of my PC including desktop as shown in the pdf tutorial in "michfood" folder.
2. The permissions for both folders is "Full Control" for all users.
3. Files not hdden or protected.
4. Also turned off my antivirus and firewall.
No luck....Please help !!! Thanx in advance
makbro said:
Hi csns,
Sorry to bother you but when I try drag and drop my original "recovery.img" to "cwmr 6015.bat" in the "michfood" folder, I get a warning message "System cannot find the specified file "C:\users\....\recovery.img" "recovery" and the bat script exits...I have tried the following:-
1. Copy the folder and file "michfood" and my original "recovery.img" file in all possible alternate locations of my PC including desktop as shown in the pdf tutorial in "michfood" folder.
2. The permissions for both folders is "Full Control" for all users.
3. Files not hdden or protected.
4. Also turned off my antivirus and firewall.
No luck....Please help !!! Thanx in advance
Click to expand...
Click to collapse
Well, this happened to me once and I think the reason was that the path was too long - I guess it may have something to do with the fact that the .bat is a simple "program" and can have some problems with handling long paths.. specially with "national" character in them.
Try finding a location as close to the root of the drive as possible, and make sure you have full R/W access. Or try with a pendrive for example.
Since you made a backup of your ROM I think you are quite safe with using the recovery I uploaded - first post -> UPDATE 1.
They seem to fit all 2107A devices. If not I will tell you how to restore the original recovery from your backup.
You can also read UPDATE 3 I just made - your choice.
Thanx
Hello csns,
Thanx to your help, I have also got CWM recovery working on my device.
BTW I saw these two posts on a forum in Russian (I guess)...I used google translate and am pretty sure these two posts that I provide links for below have two modified ROMs with everything working, including phone and radio !!! The only draw back is that once you flash these ROMs you'll get Russian language, which can be changed to English from the language menu
I plan to fo it myself as well tomorrow,would let you know the outcome
http://4pda.ru/forum/index.php?showtopic=286687&st=920 (go down to the post labelled "A2107_Foxtrot_v100")
and
http://4pda.ru/forum/index.php?showtopic=286687&st=440 (go down to the post labelled "Прошивка Tasemart
MOD 1.1")
and of course you can also try the "Angeleas_Final" modified ROM also that I'll upload and provide links to tomorrow
Thanx again for all your help !!!
I also had many trouble getting the cwm bat file to work. It is very picky about its path and arguments on Win7.
I moved the michfood folder to C: and moved my own recovery.img to C:\michfood\recovery.old
cd C:\michfood
cwmr\ 6015.bat recovery.old
That worked - otherwise it wouldnt finish the cpio stuff.
Reworking that horrible script to work on linux would have probably taken less time -_-
Anyway - thanks!
Permissions problems on Windows7
Hi,
I Had the same problem.
makbro said:
Hi csns,
Sorry to bother you but when I try drag and drop my original "recovery.img" to "cwmr 6015.bat" in the "michfood" folder, I get a warning message "System cannot find the specified file "C:\users\....\recovery.img" "recovery" and the bat script exits...I have tried the following:-
1. Copy the folder and file "michfood" and my original "recovery.img" file in all possible alternate locations of my PC including desktop as shown in the pdf tutorial in "michfood" folder.
2. The permissions for both folders is "Full Control" for all users.
Click to expand...
Click to collapse
My solution:
It was required to use a directory not to deep in folder structures, so the best is as short as possible like "C:\michfood".
I had to add "Full Control" permissions for "everyone" to the "michfood"-directory and enable the "replicate permissions to subfolders"-option (I don't know the exact designation because I use it in german ... )
I had to delete an existing "Recovery" folder inside the "michfood"-directory from earlier attempts to create the new file and for this I had to take over the ownership of the "Recovery" folder before I was able to delete it.
The original Recovery.img must be in a different folder than "michfood". This can be on the desktop but for a shorter path it could be in the root directory.
I had success after copying "cwmr 6015.bat" to "go.bat" (it's shorter and does not contain any space in it) and calling it from command line from its directory( C:\>cd C:\michfood ) with: "go C:\Recovery.img" ( I had Recovery.img on C:\ ).
makbro said:
3. Files not hdden or protected.
4. Also turned off my antivirus and firewall.
No luck....Please help !!! Thanx in advance
Click to expand...
Click to collapse
I hope this helps ...
Thanx
Thanx for the suggestions everyone, appreciate it...I got it working in the mean time on a WinXP desktop without any problem
makbro said:
Thanx for the suggestions everyone, appreciate it...I got it working in the mean time on a WinXP desktop without any problem
Click to expand...
Click to collapse
HOW?
Tell me what you did...
Cristian.Ene said:
HOW?
Tell me what you did...
Click to expand...
Click to collapse
I copied the folder as "C:\michfoods" and recovery image file as "C:\recovery.img" and gave the command "cwmr6015 C:\recovery.img"...Before that, I removed the space from the file name "cwmr 6015.bat" and saved it as "cwmr6015.bat".
Hi, i rooted succesfuly my a2107a device and installed backup Gscript ...loading "back_mt6575_a4_v2c.sh and saving it , but when it comes to run...nothing...only the counter saying how many sec's till stop.Any ideeas why?
I need help rooting my blu quattro 4.5 dd440 i install drivers via pdanet i tried many version of binary v30 15 31 etc and i get bootloop and system ui error all the time infinate times. I need phone rooted to unistall pre installed apps like facebook and other crap apps that take up ram. please help me if u can
BLU Quattro 4.5 (440D) GSM Recovery+Root
Hello... I got my BLU Quattro 4.5 (D440) a while back, didn't fuzz with it much right off. The Stock ROM was sluggish at best thought there was even an issue with the Digitizer/screen. But this thread was extremely helpful. I am now running Shendu ROM 4.1.2 one of the suggested ROM's above. I tried the other 2 first and they were mostly in Chineese and I had an especially hard time getting them switched over to English. Either way onward to the point. I have put together a few helpful tips-tricks for my experience with this phone and its phoenix transition to an awesome handset. Thats right now this is my daily driver and I love it! See below hope its helpful.
BLU Quattro 4.5 (440D) GSM Recovery+Root
These steps for this phone only!! Not responsible for any issues.
1. download ROM's, Recovery, & Driver from XDA (this thread)
http://forum.xda-developers.com/show....php?t=2327417
2. Enable USB Debugging! Go into Apps-Settings-DevOptions - Check box for USB Debug
3. Have original USB cord if handy! I tried with a Samsung OEM cable but no luck getting drivers to stick. Use original is best. (If you have one.)
Plug in USB Cord to PC then Phone and see if windows detects drivers. let it. It wont get the ones u need later, but what it does find is for USB storage. (you can move over your ROM's/Gapps to storage, downloads folder is a good spot).
4. Go to... http://junefabrics.com/android/downloadold.php to get pdanet software. Install it and it will give i the right drivers for ADB support. I used 4.01 to match the android version currently on my phone.
5. Extract the Driver provided from XDA. Put it in a folder with the ADB commands. Or you can get it all here... http://downloadandroidrom.com/file/G...usRootNew.zipn <-- I know this isn't for BLU but, if you extract this to a folder, and also add the drivers extracted to it as well this works! I've done it.
6. Extract the English Recovery to the same folder.
7. Turn off your phone. Hold down Vol up and Power button for about 5-9 seconds. Once you see a green screen let go of both. Screen may flicker then go black but the icons at the bottom will stay lit. You are now in APX mode (nvflash) mode. (as stated above in original post)
8. Check your Win 7 PC device manager. For a Phone device with ADB. If you you may need to update driver with the one that came from XDA, but the PDANet software should make it work.
8. Go to the folder and find Recovery.bat file (may have Chinese in file name. Double click and a command prompt window will pop up with a bunch of unknown characters, wait 5 sec then hit enter. The batch file should take of pushing the necessary recovery through ADB to the phone. It will error if it can't.
9. If completes OK. Push power for 7-9 seconds to power off the phone. Hit power like normal to turn it back on. It will boot up like normal (or it should).
10. USB is still connected this whole time and you can open a command prompt window. Navigate to the folder you placed the Recovery into. Something like user/username/desktop/BLU/recovery..etc)
Type ADB devices....it should show you that is is connected to your device. Then type " adb reboot recovery " and the device should reboot, give it some time.
11. Once in recovery. Best to do a backup of the original ROM & system. that way you can get back into recovery if anything goes wrong and wipe out the problem by restoring and starting again.
After you backup === you can get into recovery without the command being typed in or even being connected to your PC.... By holding Vol up + Power till you see the green screen then let go of power but keep holding Vol up till you see the BLU Products boot screen then let go ===
Clockworkmod Recovery should be on your screen.
you can reboot phone now and get back to original with no changes. Or you can venture into the world of loading ROM's (There in your downloads folder if you saved them in Step 3)
ROM 101
BACKUP-BACKUP-BACKUP 1st thing once in Recovery ...can't stress enough how much of trouble you can keep yourself out of by keeping an original backup.
As I stated before the Shendu ROM + Gapps is running smooth and all features I've been trying are working flawlessly!! Thanks to original post for getting me going. Just thought I'd add my 2 Cents.
EDIT 2019: rooting with TWRP from 038 read at the bottom of this post
HOW TO.... Stock, Update, custom recovery and root your s60 !!!!
Disclaimer: if you brick your phone, it's your fault, i have tested this way of rooting my s60 now for a several times and it works 100%
SO READ TWICE, CHECK TWICE, BEFORE YOU CLICK ONCE !!!!! i will not take any responsibility !!!
!!! ONCE AGAIN, READ THE WHOLE GUIDE BEFORE YOU START !!!
OK, now we start:
Thanks to everybody who contributed and made the root possible, here in this thread (Cesarq, OpenMinded, Tuschi, BetonJohn, etc.......) the software in the link further down, is the collected data, freely available in the net and linked in the original Thread several times, i have only bundled one package and wrote this, hopefully usefull guide.
in principle do as follows: (I will only explain once how to sideload or load via recovery, afterwards i will only state what kind and what file)
Prerequisites
- switch phone OFF
- download my collection of the essential s60 files : Here is my collection
EDIT 2019: - grap the 035 update here from the Thread: Thanks to tusch00101
i did not find the 038 update as a single zip file to download. if somebody could provide it ?
(there are ALL files included to flash stock, update to .035, flash twrp recovery and root.)
(this is for Win7 x86, you have to check if it works for other versions yourself, sy..)
- install USB drivers
(for recovery and adb !!! There are two different USB drivers needed)
- install "minimal ADB and fastboot"
- copy the two updates (update032.zip & update033.zip) into the folder, where you have installed "minimal ADB and fastboot" (makes live easier later)
- install QPST (the version of QPST is the one from Androidmtk and should be virusfree.)
(The version of QFIL in my collection is the one without reboot, so you have to reset/reboot your phone manually (resetbutton below hatchdoor on your phone) whenever stated in this guide.)
- format micro SD card in fat32 ! and copy SuperSU.zip onto it. Then insert microSD card into your phone.
- switch phone ON
- enable Developer Options, by going into the settings menu and go to "About Device". tip/touch/tap 7x the -build number- field. A message will appear: "You're now developer" (something like this)
- enable USB-debugging. Go again to settings, then "Developer Options" and enable USB-debugging.(flick the switch)
- connect a WORKING USB cable to your phone (Not to your PC atm !!!)
- dial *#06# to see the iMEI('s) of either one or both simslots. dial #02# to check what firmware version you are on
(just for your info: It looks like the "S" in the firmware version (LTE_X.....) indicates, that SingleSim only is activated, while the "D" stands for DualSim activated. my s60 had an "S"... )
(In my phone the second Sim slot (under the microSD card slot), was blocked with a small piece of, simcard shaped, black plastic. With the help of some tweezers the scrap
plastic was gone easily. Anyway --- BE CAREFULL --- when removing it.)
If you are allready on an LTE_D... Firmware version 033 or above (atm only confirmed up to 035) and you want to root with custom recovery, you only need to follow the last step in this guide ("getting twrp and Root") everybody else, continue reading...
getting twrp (for saving your old firmware only)
- power off phone.
- start minimal adb on your PC
- start QFIL (part of QPST) on your PC
- press VOL+ & VOL- simultanousely and connect phone with PC (it will vibrate once, top right LED starts blinking red, screen stays black) (- DOWNLOAD MODE -)
(just in case: to leave Download mode, disconnect phone from PC, press and hold power button for apprx. 15 seconds)
- as soon as you connect your phone to the PC, QFIL should show the Phone/port in the topline allready
(if not, either try to manually select the port, or you probably still have a problem with the USB drivers or the USB cable !)
- QFIL - tick "Flat Build" (top left)
- QFIL - select Programmer, "browse" to the saved location of "update-twrp-recovery-nobootpatch" and select the "prog_emmc.blablabla...mbn" file and doubleclick
- QFIL - "load XML" ,select rawprogramm, doubleclick, select patch0, doubleclick
- QFIL - click on "download"
- if everything was OK up till now, it should start download - BE PATIENT- and read the status window on QFIL, when it shows "finish download"....
- disconnect phone from PC
- press and hold simultanousely POWER and VOL+ (- RECOVERY MODE -) AND...
- ... use a small tool to push the reset button on the phone under the hatch, while still pressing Power and Vol+ !
- the phone should now be in twrp recovery. If so, do a full backup now to your (allready inserted and fat32 formatted) microSD card!!!
when done
- Power off your phone !
flashing stock 31.02
- enter download mode again (Vol+ & Vol-, connect phone to PC.......)
- this time in QFIL, browse in programmer path to "s60_stockFW_31.02" and select the programmer from there
- load XML's (the ones that belong to Stock31.02)
- start download... this will take a while !!!! BE PATIENT !!!!
- when QFIL status window shows finish download, push the reset button on the phone and let it reboot.
(it is normal, that the phone should restart itself 2, maximum 3 times during the first startup, but sometimes it ends up in a bootloop (Cat Logo, reboot, CAT logo, reboot, etc, etc, .......))
(The bootloop mainly happens, if you clear, in twrp recovery, the whole OS, or if you came from another firmware version (LTE_S... -> LTE_D... i.e., but that's no issue either...).
- if it ends up in a bootloop, no worries, just continue ! Believe me, i did this process now several times !
you are back on stock 31.02 !
- Power off your phone again
Updating to 032
- bring up minimal ADB sideload on your PC (start it, if not allready done in previous step (getting twrp)).
- press and hold POWER and VOL+ button on your phone
- when in stock recovery select (with Volume keys) "adb sideload" and click the Powerbutton
- connect your phone to the PC
- on PC, type into the black ADB Terminal window "adb sideload update032.zip" and hit enter
- if correct USB drivers are installed, phone will start downloading the update now.
- when complete, select clear cache, and clear data then reboot your phone.
(again, same as in the step (flashing stock), if bootloop, no worries, just continue, if it boots up, let it boot up and then..)
you're on 032 now
- Power off the phone again
Updating to 033
- do the same steps as described under "Updating to 032" only difference, type in adb window " adb sideload update033.zip"
EDIT2019: - do the same steps for 035 and 038
(After updating to 038, your phone should boot up normally by now. NO MORE BOOTLOOP !)
getting twrp and Root
- this is the same step as above "getting twrp" only difference, this time, no backup needed and...
- when in twrp-recovery, select "install" browse to your micro SD-card, and...
- install SuperSU.zip from SDcard.
- once more, clear cache and data and reboot.
The phone should boot up now, you should be on FW 033, with custom recovery and root !!!
That's all !!!
Oh, one last thing, whoever is having an s60, where only one simslot is working, this guide unlocks the second Simslot as well !!!
Also the problem, some people had, following the other guides (incorrectly) ! (me included) ! , by not using the right QFIL (the one without reboot), in the old Thread, resulting in a
not working WIFI is no issue anymore
EDIT 2019 !!!
Getting TWRP with stock 038 thanks to: CDMCCDMC for the addition !
https://forum.xda-developers.com/showpost.php?p=77978181&postcount=135
thanks for the awesome guide. works perfectly, but i will say every time I plugged my phone in it recognized it as a new device and had to reinstall drivers.... the first few times i did it i thought QFIL froze so i unplugged to reset, this caused an install failure that could not be rectified. I fixed this by uninstalling and reinstalling the drivers from step one and being more patient.
Dear adtbm,
the firmware updates (both) are extracted... became signature failure.
Please update your very useful package... thx
best regards
yanardag
Please i cant use my phone it hangs in a bootloop i need the update.zip 32 and 33
Yanardag said:
Please i cant use my phone it hangs in a bootloop i need the update.zip 32 and 33
Click to expand...
Click to collapse
Thanks for letting me know !
You can get the files from OpenMinded link here
You only need the two update files.
Untill i have updated my package.
EDIT: Package is updated now !
After flash 32 it is starting and i see the wizzard.
But after flashing 33 and rooting i have no wifi.
İ flashed 31.02 then update 32 and after this i update it ota
To 33 and last to 35 and everything is working root (supersu) (dont use magix)is working with 35 very well. Everything ok (xposed, gravity and so on) thx
Yanardag said:
After flash 32 it is starting and i see the wizzard.
But after flashing 33 and rooting i have no wifi.
İ flashed 31.02 then update 32 and after this i update it ota
To 33 and last to 35 and everything is working root (supersu) (dont use magix)is working with 35 very well. Everything ok (xposed, gravity and so on) thx
Click to expand...
Click to collapse
If you don't have Wifi after going to 033, you didn't followed the part of "getting twrp" correctly.
"...... - if everything was OK up till now, it should start download - BE PATIENT- and read the status window on QFIL, when it shows "finish download"....
- disconnect phone from PC
- press and hold simultanousely POWER and VOL+ (- RECOVERY MODE -) AND...
- ... use a small tool to push the reset button on the phone under the hatch, while still pressing Power and Vol+ !
- the phone should now be in twrp recovery. ....."
If you let the phone reboot after flashing the recovery, it will overwrite the boot and your wifi is gone !
But nice to hear, that everything is OK now. Do you have problems with 035 ? some people report, that they having issues with the display camera on 035 ...
Sorry for this silly question, but i´ve seen that in other models once you install twrp then you can flash super su, why here you have to downgrade to 0.31 first?
Thank you in advance.
javizap said:
Sorry for this silly question, but i´ve seen that in other models once you install twrp then you can flash super su, why here you have to downgrade to 0.31 first?
Thank you in advance.
Click to expand...
Click to collapse
Hi,
not sure, if you have read the complete guide, or if you have read through the 28 pages of the original Thread.
I think, it could be possible, (but i did not tested it) to flash the recovery via QFIL directly and then install SuperSU, without going back to 031. But since there are models of the s60 out, where only one Simslot is available (Please read my guide), to get the second slot activated you have to flash an LTE_D... firmware and, thanks to Cesarq, we (only) have atm his 031 firmware available, which is luckywise an LTE_D. firmware !
Like i mentioned in this guide allready, i did not found out the way how to root the s60 (the credit goes to Cesarq) and i also did not find out, how to update to 033 (this credit goes to OpenMinded), i have only collected the software & tools, bundled it and wrote this guide, with the available information written throughout the 28 pages of the original Thread.
So please feel free and test it and write us your result !
ok, just did my s60 last night, everything seemed to go just as described. i just checked and it seems it took the update and the dual sim activation. it didnt take root tho. i tried root checker and titanium and both say no root access. maybe i did the final step wrong? i tried it again with no success. am i supposed to be loading the nobootpatch recovery in qfil as the last step and then install su? thats how i attempted it. any help would be greatly appreciated. thanks in advance!
adtbm said:
If you don't have Wifi after going to 033, you didn't followed the part of "getting twrp" correctly.
"...... - if everything was OK up till now, it should start download - BE PATIENT- and read the status window on QFIL, when it shows "finish download"....
- disconnect phone from PC
- press and hold simultanousely POWER and VOL+ (- RECOVERY MODE -) AND...
- ... use a small tool to push the reset button on the phone under the hatch, while still pressing Power and Vol+ !
- the phone should now be in twrp recovery. ....."
If you let the phone reboot after flashing the recovery, it will overwrite the boot and your wifi is gone !
But nice to hear, that everything is OK now. Do you have problems with 035 ? some people report, that they having issues with the display camera on 035 ...
Click to expand...
Click to collapse
Nope everything is well. 35 runs without any bugs. For me is importend that xposed is running and that does.
yesca213 said:
am i supposed to be loading the nobootpatch recovery in qfil as the last step and then install su? thats how i attempted it. any help would be greatly appreciated. thanks in advance!
Click to expand...
Click to collapse
I asume, you have SuperSU copied onto your microSC card ?!
When you have finished flashing the nobootpatch recovery (QFIL shows finish download), you have to disconnect the phone from the PC, push Vol+ and Power and Reset (under the hatch) at the same time.
Otherwise Bootloader gets overwritten, your Wifi is gone, no custom recovery and no root.
If you are not using the version of QFIL from my package, you probably have a version that automatically reboots when download is finished and you're screwed !!!
If you did it correctly your phone should boot into twrp custom recovery and you should be able to install SuperSU from SD.
adtbm said:
I asume, you have SuperSU copied onto your microSC card ?!
When you have finished flashing the nobootpatch recovery (QFIL shows finish download), you have to disconnect the phone from the PC, push Vol+ and Power and Reset (under the hatch) at the same time.
Otherwise Bootloader gets overwritten, your Wifi is gone, no custom recovery and no root.
If you are not using the version of QFIL from my package, you probably have a version that automatically reboots when download is finished and you're screwed !!!
If you did it correctly your phone should boot into twrp custom recovery and you should be able to install SuperSU from SD.
Click to expand...
Click to collapse
Yes I did have it copied and installed it. I went back and did it again and hit wipe dalvic cache instead of going back in the recovery menu and wiping cache and data. Up and running 33 rooted, everything seems good so far! Thanks [emoji2]
Sent from my S60 using Tapatalk
adtbm said:
Hi,
not sure, if you have read the complete guide, or if you have read through the 28 pages of the original Thread.
I think, it could be possible, (but i did not tested it) to flash the recovery via QFIL directly and then install SuperSU, without going back to 031. But since there are models of the s60 out, where only one Simslot is available (Please read my guide), to get the second slot activated you have to flash an LTE_D... firmware and, thanks to Cesarq, we (only) have atm his 031 firmware available, which is luckywise an LTE_D. firmware !
Like i mentioned in this guide allready, i did not found out the way how to root the s60 (the credit goes to Cesarq) and i also did not find out, how to update to 033 (this credit goes to OpenMinded), i have only collected the software & tools, bundled it and wrote this guide, with the available information written throughout the 28 pages of the original Thread.
So please feel free and test it and write us your result !
Click to expand...
Click to collapse
I took your advice and rooted without downgrading firmware. My CAT is double SIM from factory and on 0.35 OTA.
I followed your guide but jumped from backup with twrp to install supersu, following all the steps from there.
Until now everything working fine with root.
One more time I can say that people on XDA is the best!
Regards
Dear friends,
How can i uninstall google assistant apk?
When i delete it the phone not restart and ended in a bootloop.
When i deactivate it the same bootloop.
very very good
Hello to this wonderful group. I did the rooting and it worked wonders, I was very disappointed with my Cat s60, for not being able to use the second sim and for the poor quality of the camera. After the root it became dualsim and the camera improved a lot. in addition to everything that means to be root. I am very grateful to ADTBM and to all those who made this possible. thanks thanks. regards
Yanardag said:
Dear friends,
How can i uninstall google assistant apk?
When i delete it the phone not restart and ended in a bootloop.
When i deactivate it the same bootloop.
Click to expand...
Click to collapse
Hi Yanardag,
i have the same problem. Unfortunatley Android IS Google . I really don't know how to disable it. Did you try to freeze it with Titanium ?
That's the only thing i could think of. I am annoyed by that Google stuff as well (especially the google assistant....)
This is one of the reasons, why i had to redo my s60 a several times.
So if anybody here finds a way to disable Google assistant, pleasse let us know !!!
@varonv: Nice to hear and thanks for the feedback !
Hi,
I am on 027 now. No OTA update available. Can I try this guide?
Thanks
freeze it with Titanium
adtbm said:
Hi Yanardag,
i have the same problem. Unfortunatley Android IS Google . I really don't know how to disable it. Did you try to freeze it with Titanium ?
That's the only thing i could think of. I am annoyed by that Google stuff as well (especially the google assistant....)
This is one of the reasons, why i had to redo my s60 a several times.
So if anybody here finds a way to disable Google assistant, pleasse let us know !!!
@varonv: Nice to hear and thanks for the feedback !
Click to expand...
Click to collapse
I froze it with Titanium: no problems whatsoever.
This Guide works on win 10 also. .. But ending in Win 10 Test mode