***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY***
CLEAR/DELETE DALVIK-CACHE FOLDER FROM "/data/dalvik-cache" IN ROOT EXPLORER OR TWRP AFTER INSTALLING BOOT IMAGE TO ALLOW SYSTEM TO ADJUST
##FLASH THE LATEST SUPERSU ZIP BELOW##
P.S. I NOTICE IT IS NO LONGER SYSTEM-LESS MODE. SO WE CAN TRIM THE SUPERSU SYSTEM-LESS CONTENT FROM THE RAMDISK.
Tweaked the contents of the boot image to allow for faster boot and better runtime performance. I use it as my daily driver. App performance is snappier. Only for the Boost Desire 626s. Unzip and flash with Flashify, TWRP, or your choice of image flasher. I also added some optimization scripts to supplement the boot image. Run them with Smanager, Root Explorer or in the terminal. Also here is a zip 601626SPIEFIX.zip that when flashed in TWRP recovery will allow the system to run non-pie executables and it works great. You'll be able to run custom binaries without any issue or error. All zips in this thread are the latest.
If you have ISSUES WITH DATA SPEEDS in certain areas, especially if you tether, GO INTO THE DIALER and DIAL *#*#4636#*#* then ACCESS PHONE INFORMATION and SELECT CDMA auto (PRL) UNDER SET PREFERRED NETWORK TYPE. LTE seems to be problematic in certain areas with speeds dropping to 150kbps and with this solution you'll be getting about 600 to 700kbps so at least it'll be a gain until you get into an area with better LTE coverage. In a good coverage area, I get download speeds of up to 5 to 7 mbps with LTE on, but in bad areas, CDMA works better. If you want to tether with a wireless third party solution make sure to run in a terminal window or adb shell as root : pm disable com.htc.tetheringguard
DOWNLOAD BOOT IMAGE: http://forum.xda-developers.com/attachment.php?attachmentid=3917986&d=1477604429
DOWNLOAD SUPERSU BETA: https://download.chainfire.eu/1009/SuperSU/SR2-SuperSU-v2.78-SR2-20161029143931.zip?retrieve_file=1
DOWNLOAD SCRIPTS: http://forum.xda-developers.com/attachment.php?attachmentid=3863279&d=1472880351
DOWNLOAD PIE FIX: http://forum.xda-developers.com/attachment.php?attachmentid=3844539&d=1471383163
DOWNLOAD BOOT IMAGE TOOL : http://forum.xda-developers.com/attachment.php?attachmentid=3917995&d=1477605263
DOWNLOAD HTC DRIVERS AND MINIMAL ADB + FASTBOOT: http://forum.xda-developers.com/attachment.php?attachmentid=3868562&d=1473328405
ANDBLOCKDEV.sh from scripts zip will speed up file input and output speeds, its contents have been incorporated into the boot image so the scripts files are for your own archival.
The zip DESIRE626SIMGTOOL.zip contains the android image kitchen and the 6.0.1 Boost Desire 626S boot image contents already extracted into two folders split_img and ramdisk with recent modifications. Enjoy!
http://www.vysor.io/ is a great tool to control your android device from a computer within chrome. You should try it out.
I provided a zip named HTCDrivers.zip containing the installation for both fastboot and adb drivers for the Boost Desire 626S, and minimal adb and fastboot. This will help you connect your device up with Vysor.
COPY the FILES; fastboot.exe, adb.exe, AdbWinUsbApi.dll and AdbWinApi.dll FROM - C:\Program Files (x86)\Minimal ADB and Fastboot - TO - C:\Windows\System32 - AND - C:\Windows\SysWOW64
Once you have installed the drivers for HTC devices,
and copied the minimal adb and fastboot files specified above to both system folders, you should be able to run adb commands without a problem by just opening a command prompt as administrator,
and RUNNING the command:
adb devices
- to start the adb server. This will allow connection with Vysor.
##########
For those who prefer nightbreed813's 6.0.1 slim rom version, I uploaded 601VPNDIALOGSFIX.zip to fix the issue with authorizing VPN clients, but first YOU HAVE TO CREATE /system/priv-app/VpnDialogs in Root Explorer or any other root filesystem browser, then reboot to TWRP recovery and flash the zip.
DOWNLOAD VPNFIX : http://forum.xda-developers.com/attachment.php?attachmentid=3860930&d=1472669879
##########
Also, you can get your MSL/SPC security code easily.........
Use the info in this thread to get your MSL/SPC security code so you can write new values to NV entries in the modem. Some values are locked but you can change the BC config for both LTE and CDMA so that would at least be helpful.
INFO HERE: http://forum.xda-developers.com/spri...k-sim-t3314755
##########
Android settings can be changed in the terminal for three namespaces; system, global and secure.
In the terminal run:
settings list system
settings list global
settings list secure
For each namespace all associated settings and their values will be listed. To change a setting type:
settings put system setting_name_here value_here
settings put global setting_name_here value_here
settings put secure setting_name_here value_here
##########
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Look now has working VPN......
***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY***
anthonykb said:
Tweaked the contents of the boot image to allow for faster boot and better runtime performance. I use it as my daily driver. App performance is snappier. Only for the Boost Desire 626s. Unzip and flash with Flashify, TWRP, or your choice of image flasher. I also added some optimization scripts to supplement the boot image. Run them with Smanager, Root Explorer or in the terminal. Also here is a zip 601626SPIEFIX.zip that when flashed in TWRP recovery will allow the system to run non-pie executables and it works great. You'll be able to run custom binaries without any issue or error. All zips in this thread are the latest.
Click to expand...
Click to collapse
Will this run on the Metro Variant?
As far as I know no but you can try in case it might.
Enter these commands in a new terminal window:
cd /dev/block/platform/soc.0/7824900.sdhci/by-name
dd if=boot of=/sdcard/backup.img
The backup boot image can be flashed from the sdcard in TWRP recovery if the device fails to boot into the system after flashing the boot image contained in the zip in the attachments.
Is there anyway you would be able to make one for the metro Variant if i upload my boot image?
MetroPCS Boot Image
GotHeart said:
Is there anyway you would be able to make one for the metro Variant if i upload my boot image?
Click to expand...
Click to collapse
Did you try unzipping the boot image and flashing it already? I don't think it could work that way. I would do it if I had the metro version myself.
anthonykb said:
Did you try unzipping the boot image and flashing it already? I don't think it could work that way. I would do it if I had the metro version myself.
Click to expand...
Click to collapse
Thats what im saying.if i upload my metro boot image would you be able to optimize it like you did before with the boost Variant?
GotHeart said:
Thats what im saying.if i upload my metro boot image would you be able to optimize it like you did before with the boost Variant?
Click to expand...
Click to collapse
I meant so you tried the boost version and it wouldn't boot?
anthonykb said:
I meant so you tried the boost version and it wouldn't boot?
Click to expand...
Click to collapse
No i havent tried it yet
GotHeart said:
No i havent tried it yet
Click to expand...
Click to collapse
Backup your kernel boot image to your sdcard and flash the boost version just to make sure.
cd /dev/block/platform/soc.0/7824900.sdhci/by-name
dd if=boot of=/sdcard/backup.img
Then unzip the 601bootimg.zip file with Zarchiver in the Play Store and flash the extracted boot image.
anthonykb said:
Backup your kernel boot image to your sdcard and flash the boost version just to make sure.
Click to expand...
Click to collapse
Okay ill do it now and let you know
The phone booted but it corrupted my sdcard,so i lost everything i had on there.
GotHeart said:
The phone booted but it corrupted my sdcard,so i lost everything i had on there.
Click to expand...
Click to collapse
Flash back the backed up boot image in TWRP and see if the sdcard mounts right. The mount point contained in the boost boot image is probably wrong for the the sdcard/emmc in the metropcs phone.
I did but my sdcard got corrupted so i was forced to format it.
GotHeart said:
I did but my sdcard got corrupted so i was forced to format it.
Click to expand...
Click to collapse
I'm so sorry the process turned out to be a dud for you I have the boost model myself. Hope you can recover your files with one of those forensic data recovery tools.
anthonykb said:
I'm so sorry the process turned out to be a dud for you I have the boost model myself. Hope you can recover your files with one of those forensic data recovery tools.
Click to expand...
Click to collapse
Its nothing important lol.any chance you can share what you did or how?
Use the Android Image Kitchen by osm0sis
GotHeart said:
Its nothing important lol.any chance you can share what you did or how?
Click to expand...
Click to collapse
Use the tool at the link below to unpack the image, make your modifications, and repack the image contents (The ramdisk and split_img folders.) It's available for Windows, Linux and Android. It's a simple process expect for knowing what you'd need to do to the image.
http://forum.xda-developers.com/showthread.php?t=2073775
anthonykb said:
Use the tool at the link below to unpack the image, make your modifications, and repack the image contents (The ramdisk and split_img folders.) It's available for Windows, Linux and Android. It's a simple process expect for knowing what you'd need to do to the image.
http://forum.xda-developers.com/showthread.php?t=2073775
Click to expand...
Click to collapse
My mistake i was in a hurry when i typed that last reply.
Im aware of how to unpack/repack boot images and i appreciate the link,but i was wondering what modifications that were made.if youd prefer not to share,i can upload my boot image if youd like to make the modifications yourself.im just trying to make this compatible with the metro version.
The same modifications done for the Boost Desire 626S might not work well for the MetroPCS version so upload the image you backed up yesterday as an attachment in a reply post and I'll work on it.
Thanks a ton!
MetroPCS Boot Image
GotHeart said:
Thanks a ton!
Click to expand...
Click to collapse
Run busybox top in the terminal on your phone and post some screenshots so I can see what might need to be done. We want to see what processes would be the culprit behind bogging down precious processor time and reducing the snappiness of the device in reacting to realtime input and handling current requests.
Related
Hello,
i have been reading guides all the day and no-one had a solutions to my problems so i would like to write my own to help out others who are encountering my same issues.
----------------------------------------------------------------------------------------
This guide is for Windows and explains everything you need to update your Nexus 7 (2013) Wifi (flo) from 4.3 JSS15R to 4.4 KRT16O
----------------------------------------------------------------------------------------
1) disconnect table from USB cables if it is connected to the pc
2) go http://developer.android.com/sdk/index.html and download the SDK
3) unzip the SDK in C\
4) go in C:\adt-bundle-windows and start the SDK Manager
let is load and scan for all possible updates.. when it has finished click on Deselect All then choose only these to packages:
Tools --> Android SDK Platform Tools
Extra --> Google USB Driver
if the Android SDK Platform tools are updated then you will only have 1 package to download else you will see Install 2 Packages, click it, then select Accept Licence and click Install.. wait it to finish and then close
5) let's now download the factory image
Nexus 7 2013 only WIFI (flo) "razor" is here: https://developers.google.com/android/nexus/images#razorkrt16o and download the first link of the page (4.4 (KRT16O) Link)
Nexus 7 2013 MOBILE/LTE (deb) "razorg" is here: https://developers.google.com/android/nexus/images#razorgkrt16o and download the first link of the page (4.4 (KRT16O) Link)
for some reason the MD5 checksum and SHA1 for the flo version dont match but i read people have been able to install this image anyway (i installed the OTA so i did'nt try this install)
unzip the downloaded file and you should get a .tar file.. unzip it again and you should get a bunch of files.. i got the following ones:
1)bootloader-flo-flo-03.14.img
2)flash-all.bat
3)flash-all.sh
4)flash-base.sh
5)image-razor-krt16o.zip
place all these files in C:\adt-bundle-windows\sdk\platform-tools\
6) now let's install the drivers correctly and flash the update
First thing, keep the Nexus 7 not connected to the USB cable. Then switch it on and go into Settings --> Storage click on the Options and choose USB computer connection and make sure to have the CAMERA (PTP) selected.
Now go into developer options and select Stay Awake and USB Debugging
Go back to the home screen and connect the tablet to the PC.. let the PC try to install it by himself.
Now press WINDOWS+R and run devmgmt.msc
If you see a device called Nexus 7 with a yellow sign then right click on it and choose Update software driver.
Then select the second option (find a driver on the computer), then select the second option (choose manually a driver from a list), now click first option (show all the devices), then click Driver disk button, then browse to C:\adt-bundle-windows\sdk\extras\google\usb_driver\ and choose android_winusb.inf and do ok.
The box should fill with a device called Android Composite ADB Interface, choose that and do next
To check if you have done right do:
WINDOWS+R and run cmd
in cmd do cd.. until you get into C:\
then do cd adt-(tab) to autocompile and enter
then do cd sdk enter
cd platform-tools enter
adb.exe devices enter
the daemon should start and you should get a list of devices attached showing you a code made of numbers and letters.. this is your nexus 7.
if cmd says the device is unauthorized then look at your tablet and allow the computer to operate
let's now install the driver also in fastboot so to do this always in cmd type
adb.exe reboot-bootloader
the tablet will reboot into the bootloader and you will see an android with the open tummy
now inside the command prompt window run the following commands:
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
fastboot -w update image-razor-krt16o.zip
if everything has gone right you should have updated using the factory image and the tablet should reboot by now...
else continue reading:
if you had any issues we can then try to update through OTA which means you will need to download another package
the nexus 7 ONLY WIFI OTA: http://android.clients.google.com/p....signed-razor-KRT16O-from-JSS15R.3a3951e8.zip
not sure if the nexus 7 LTE OTA url has been released or not because i can't find it.. if anyone has the link and can point it out to me i would be glad to add it here
download it and place it always in
C:\adt-bundle-windows\sdk\platform-tools\
rename it to something easier and redo
adb.exe sideload ota_zipfilename (enter)
everything should go fine now, so it will reboot.. configure the tablet again if it is the case
7) changing recovery
download latest recovery from here http://techerrata.com/browse/twrp2/flo
place the download img into C:\adt-bundle-windows\sdk\platform-tools\
then reboot to bootloader using adb or simply switch the table on keep vol down down
in cmd type
fastboot.exe flash recovery recoveryimagefile
8) rooting the tablet
btw sideloading the zip for rooting requires a custom recovery such as TWRP so step 7 must be achieved in order to root this way
download the latest superSU from here http://download.chainfire.eu/supersu
go into recovery mode passing by the bootloader
do another adb sideload passing this time the zip for supersu
everything done hopefully
hope this helps others which had issues with drivers and had issues with the original factory image 4.4 (KRT16O) giving the E: signature verification failed
Great guide!
The package for the link https://developers.google.com/android/nexus/images#razorkrt16o fails verification for me as well and does not install once its side loaded. So it's probably beneficial to just point to the other link.:good:
haet said:
Great guide!
The package for the link https://developers.google.com/android/nexus/images#razorkrt16o fails verification for me as well and does not install once its side loaded. So it's probably beneficial to just point to the other link.:good:
Click to expand...
Click to collapse
The factory image isn't meant to be side loaded. It needs to be installed using fastboot/bootloader.
If I understand this correctly, it fails because ADB sideload is intended for zips and not image files.
If you use the flash_all.bat (or whatever it is, slips my mind at the moment) it will flash a complete factory image.
The zip on the other hand is intended for sideloading and should update the OS no problem.
cincibluer6 said:
If I understand this correctly, it fails because ADB sideload is intended for zips and not image files.
If you use the flash_all.bat (or whatever it is, slips my mind at the moment) it will flash a complete factory image.
The zip on the other hand is intended for sideloading and should update the OS no problem.
Click to expand...
Click to collapse
Gotcha.
There is quite a size difference between the the zip and the tgz format. Is this only because of compression format? Or is it more beneficial to flash one over the other?
cincibluer6 said:
If I understand this correctly, it fails because ADB sideload is intended for zips and not image files.
If you use the flash_all.bat (or whatever it is, slips my mind at the moment) it will flash a complete factory image.
The zip on the other hand is intended for sideloading and should update the OS no problem.
Click to expand...
Click to collapse
There are zips and then there are ZIPS
It isn't the type of archive that is critical but the contents of the zip. Zip is just a generic archive format and can store anything.
The OTA zips include specific content. In particular they are
signed by google
include an install script to handle patching, replacing files, and setting up permissions
include an install utility to run the script
include individual patch files
include whole files if the patches would be too large
have a specific directory structure where everything is supposed to be located
The factory images are also delivered in an archive. They are first archived in a tar format, which just collects a bunch of files and doesn't compress. Then they are gzip'd which is a Gnu archiver which performs a similar job to zip, but uses a different format and algorithm. Within the original tar archive there is also a zip archive. That zip contains images of the kernel, recovery, rom, user and data partitions, but it doesn't include the aforementioned items that make a zip into an OTA-style zip.
The factory images are NOT meant to be flashed in recovery. Recovery will be expecting the stuff above that OTA-style zips have. If you try to flash the factory image, the first point of failure is the signature verification fails, because it isn't signed (and even if it were signed, it wouldn't be signed in the way recovery is expecting)
So what is the difference between flashing via Recovery and the OTA-style zip vs running flash-all and the factory image?
The OTA-style flash will go and examine each file it needs to patch to make sure it is stock JSS15R. It must do this because it doesn't have the complete KRT16O file, only a patch (difference between the JSS15R and KRT16O versions of the file) that only makes sense if applied to the original JSS15R file. Even if there is a one space difference in the file, the patch would fail.
Since the OTA-style patches files (in general) it will leave files you have added in place. In particular the files installed to keep root are left in place and so are apps, sounds, images, etc. you added to the ROM (/system) partition. So you ask why do you lose root? You don't lose the root files that were installed, they are neutered because at the end of the OTA-style install, it resets the permissions in all the directories to what they are supposed to be. This drops the special permissions you gave the root files to do their job. Also the OTA-style patch does not directly overwrite your recovery. Upon first boot, there is a script that runs which builds the new recovery using the installed kernel. This is why if you immediately (prior to reboot) run the SuperSU install script after the installation of the OTA-style update.zip, you can restore root and keep your recovery. The SuperSU install script replaces the script that builds the new recovery, with its own file. It also reinstalls and sets the permissions on the root files. So in effect, you have root and have prevented stock recovery from being installed over your custom recovery.
The Recovery that you use to run the OTA-style update.zip is just special program that boots up on the linux kernel and accepts certain actions. The source code for Recovery along with the kernel is published. People can easily replace Recovery with their own custom program and that is why you have custom recoveries.
The factory images on the other hand install through the bootloader. This is a low-level program similar to BIOS on PCs. It has more limited functions and the code is proprietary. It is harder to do custom bootloaders because the source code isn't published.
The bootloader has a more limited set of functionality and you communicate with bootloader using a different program called fastboot.
The bootloader expects the files you give it to be .img files or you can give it a zip archive full of .img files. These are not patches of files like the OTA. These are complete images to replace the existing partitions. It is like a Norton Ghost image (factory image style) of your entire hard drive vs an incremental backup (OTA-style) of just the files that changed.
Given they are full images, they will overwrite the partitions completely so anything you had on them before is wiped out and overwritten.
Also full images are always larger than OTA patch-style updates because they contain everything rather than just the changed file patches.
By default they use the -w option in the fastboot install instructions, which will wipe your user data as well, but you can remove the -w option and keep your user data, though there are always a small percentage of upgrades where it won't work to keep your user data (same with the OTA).
Anyway that is just a brief summary. There are many more details and nuances I didn't list.
^^ I won't go ahead and quote you but thanks for the full on summary. I knew what .tgz was and all that (using Linux for a few years now) but I'm new to most of the Android like stuff.
Thanks for clarifying and explaining it so well.
Just gave the sideload of SuperSU a shot and was given two errors:
failed to verify whole-file signature
signature verification failed
haet said:
Just gave the sideload of SuperSU a shot and was given two errors:
failed to verify whole-file signature
signature verification failed
Click to expand...
Click to collapse
You cannot sideload the SuperSU update.zip using stock recovery because it isn't signed by Asus/Google.
It is signed, but using a generic cert.
You need to use custom recovery like TWRP or CWM to install it. You can use their menu system to choose the file or if they have sideload, you can sideload using custom recovery.
sfhub said:
You cannot sideload the SuperSU update.zip using stock recovery because it isn't signed by Asus/Google.
It is signed, but using a generic cert.
You need to use custom recovery like TWRP or CWM to install it. You can use their menu system to choose the file or if they have sideload, you can sideload using custom recovery.
Click to expand...
Click to collapse
Makes sense. Thanks for the help!
Windows 2008 server usb drivers?
This guide was great, and everything worked fine until I reboot into recovery and choose to adb sideload an image. Then, the device doesn't get recognized, and the google drivers don't work. So, I can't see the device with the ADB interface driver.
Does any have experience with this? Am I out of luck? I couldn't find anyone talking about drivers for windows server 2008 anywhere -- but usually win7 drivers work fine -- just not here.
I don't have another windows installation anywhere, so if there isn't an answer, I will just have to wait for OTA
** UPDATE **
I found some universal drivers from Koushik Dutta: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Those drivers worked! Then I used the OTA download (your second option), sideloaded it, and got the update. Now running KitKat, so thanks a bunch! hopefully someone else will find this driver option useful.
I'll give those universal drivers a go. Hell, I've tried everything else on the Internet with complete failure. One last try before I give up.
Sent from my SM-P600 using XDA Premium HD app
jbwray said:
This guide was great, and everything worked fine until I reboot into recovery and choose to adb sideload an image. Then, the device doesn't get recognized, and the google drivers don't work. So, I can't see the device with the ADB interface driver.
Does any have experience with this? Am I out of luck? I couldn't find anyone talking about drivers for windows server 2008 anywhere -- but usually win7 drivers work fine -- just not here.
I don't have another windows installation anywhere, so if there isn't an answer, I will just have to wait for OTA
** UPDATE **
I found some universal drivers from Koushik Dutta: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Those drivers worked! Then I used the OTA download (your second option), sideloaded it, and got the update. Now running KitKat, so thanks a bunch! hopefully someone else will find this driver option useful.
Click to expand...
Click to collapse
You sir are a genius (and the driver author). I had the exact problem and looked everywhere. I am low tech, too. So following these two guides;
http://phandroid.com/2013/11/13/how-to-install-kitkat-nexus-7/
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
I am now on 4.4. And everything is intact. Thank you!
I also ran into Google USB driver problems after the Nexus dropped into recovery mode. So I gave up trying to use Windows 8 and switched over to using Ubuntu workstation. Getting ADB to run on Ubuntu is very easy and so flashing the Kit Kat OTA file was a breeze.
On Ubuntu there's no need to install the full SDK just to get ADB and Fastboot; the process is outlined here: http://forum.xda-developers.com/showthread.php?t=1860108. From there it's just simple command line entries from a terminal i.e. "adb devices."
I was disappointed to see Google has kept the black top and bottom bars for tablets. I usually run Teslacoil's launcher and installed their beta launcher with transparent bars a welcome relief.
doorunrun said:
I also ran into Google USB driver problems after the Nexus dropped into recovery mode. So I gave up trying to use Windows 8 and switched over to using Ubuntu workstation. Getting ADB to run on Ubuntu is very easy and so flashing the Kit Kat OTA file was a breeze.
On Ubuntu there's no need to install the full SDK just to get ADB and Fastboot; the process is outlined here: http://forum.xda-developers.com/showthread.php?t=1860108. From there it's just simple command line entries from a terminal i.e. "adb devices."
I was disappointed to see Google has kept the black top and bottom bars for tablets. I usually run Teslacoil's launcher and installed their beta launcher with transparent bars a welcome relief.
Click to expand...
Click to collapse
If you install the latest Google search apk and GEL from the nexus 5, you will have transparent nav bar.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 7 using Tapatalk 4
Hi. This will wipe the device right? We should have a backup before proceeding?
ganstar said:
You sir are a genius (and the driver author). I had the exact problem and looked everywhere. I am low tech, too. So following these two guides;
http://phandroid.com/2013/11/13/how-to-install-kitkat-nexus-7/
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
I am now on 4.4. And everything is intact. Thank you!
Click to expand...
Click to collapse
You should also know that Google has drivers as well located at http://developer.android.com/sdk/win-usb.html, which is what you would have downloaded right after you installed the SDK package.
For those who can't get their devices recognised even after doing everything correctly. Just boot the tablet and change from MTP to PTP. Worked for me.
Sent from my Nexus 7 (2013)
I was on PTP. still didn't work
BreakShadow said:
For those who can't get their devices recognised even after doing everything correctly. Just boot the tablet and change from MTP to PTP. Worked for me.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
I was on PTP. Still didn't work until I found those drivers. The drivers from Google were what I was using, but they didn't support the device in fastboot mode for the version of windows I was using. (2008 server R2)
haet said:
You should also know that Google has drivers as well located at http://developer.android.com/sdk/win-usb.html, which is what you would have downloaded right after you installed the SDK package.
Click to expand...
Click to collapse
I had those, they didn't work for me, as others have noted as well.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For anyone interested, below are the steps for getting your device dual-booting with CyanogenMod 10.2.
Why?
I don't want to erase native firmware and want to give a try to CyanogenMod
I want to have both native and CM, because I like native Samsung S-Pen apps, but want to have more fresh Android too
I like experimenting - it's cool!
The Idea
Our Android device has 2 boot partitions - for normal boot, and to boot into recovery. If I want to boot CyanogenMod, I need to place its boot image instead one of those boot partitions. E.g. if I want to have both native firmware and cyanogen - then obviously I need to replace recovery partition. However I can do the backup of recovery and restore it later if needed.
But, I also need to place cyanogen system and data partitions somewhere. Putting it on the external sdcard makes CM working really slow, repartitioning internal memory might be good idea, but it is not so easy and is not necessary for experimenting. Thus I've created 2 image files and put it to native data partition (mmcblk0p12) to media folder, e.g. into internal sdcard, then changed cyanogen boot image to mount those image files on boot as system and data partitions.
Prerequisites:
Rooted Samsung Galaxy Note 10.1 2012 Edition
2GB of free disk space at internal sdcard
Recovery partition backup, because we are going to replace it with CyanogenMod boot image
Clear understanding of what you are doing, because you potentially can break your device
Downloads:
CM 10.2 boot image
CM 10.2 data partition image
CM 10.2 system partition image
Steps
This manual suggests that you are going to do the recovery backup to external sdcard and has native firmware which means that recovery partition is mmcblk0p6, data partition is mmcblk0p12 and internal sdcard is /mnt/sdcard folder (otherwise you need to change the commands appropriately and might need to fix cyanogen boot image too).
Download 3 files by the links above and upload to internal sdcard of your device. Connect to your device via ADB and run ADB shell, or type the next commands in terminal emulator:
Code:
# become root
su -
# go to external sdcard to create recovery backup
cd /mnt/extSdCard
dd if=/dev/block/mmcblk0p6 of=./recovery.img
# go to internal sdcard folder
cd /mnt/sdcard
# unpack partition images - each is 1Gb of disk space
gunzip ./system.img.gz
gunzip ./data.img.gz
# write CM boot image to recovery partition
dd if=./cyanogen.img of=/dev/block/mmcblk0p6
# finish
exit
exit
Now you can reboot your device into recovery mode and see CyanogenMod booting.
Restoring native recovery:
If you got tired from CyanogenMod and/or would like to take back your recovery, please use the backup you've done before. Lets say it is placed on your external sdcard, then connect to your device via ADB and run ADB shell, or type the next commands in terminal emulator:
Code:
# become root
su -
# go to the folder with recovery backup
cd /mnt/extSdCard
# write recovery image over recovery partition
dd if=./recovery.img of=/dev/block/mmcblk0p6
Please let me know If I missed anything in my steps.
P.S. What I've changed in Cyanogen boot.img to make it using img files instead of partitions in form of patch: View attachment cyanogen_boot_img.patch. It is also necessary to create /host folder in initrd folder tree.
wow!!
it's really hard to be done xD
i thought it will be as easy as it was on my old Galaxy S2
all what i needed to do is to restart the phone and press home to boot to second Rom
i hope it's going to be easier soon
and thank you for you efforts toward our device Development
MoNsTeRmUk said:
wow!!
it's really hard to be done xD
Click to expand...
Click to collapse
Well, it is not as hard as it probably seems Download 3 files and overwrite recovery partition.
Probably I need to compose something like zip file for CWM or TWRP when I have free time... But if would be really nice if someone get it working too following current steps
X-Stranger said:
Well, it is not as hard as it probably seems Download 3 files and overwrite recovery partition.
Probably I need to compose something like zip file for CWM or TWRP when I have free time... But if would be really nice if someone get it working too following current steps
Click to expand...
Click to collapse
I really Appreciate your work here brother And as it seems our device is not getting much of the attention unlike other devices
And what i meant by hard is it's possible to be done without any mistakes , but i take sometime to do so and you need a computer every time you want to change the Rom so it's not a solution for every time use .
I wish you good luck and Thank you for your support
MoNsTeRmUk said:
I really Appreciate your work here brother And as it seems our device is not getting much of the attention unlike other devices
And what i meant by hard is it's possible to be done without any mistakes , but i take sometime to do so and you need a computer every time you want to change the Rom so it's not a solution for every time use .
I wish you good luck and Thank you for your support
Click to expand...
Click to collapse
Thanks for kind words Actually you don't need to have the computer to change ROM, you can type commands from terminal emulator directly from Android. I'm also thinking about creating small Android app which can be installed to each ROM and will be able to switch boot partition within one click.
Thanks for this superb work. Can't download last file ?
Please if can make someone flashable zip it would be great I am a noob but I want try this thanks again
Sent from my GT-N8000 using Tapatalk HD
other roms
Can I do this this with another rom
maro_X said:
Can I do this this with another rom
Click to expand...
Click to collapse
It is possible, but your another rom must be specially modified for this.
What rom are you talking about exactly?
Multi-boot solution
I've tired of writing images to boot partition every time I want to switch between native firmware and Cyanogen, so decided to compose a little program that I was talking before. So let me introduce you N8xx Boot Manager!
The idea:
You put your boot images files to some folder on your sdcard, lets say to /mnt/extSdCard/images/boot
And recovery boot images to /mnt/extSdCard/images/recovery
Now you run Boot Manager and select what you want to boot as normal boot or as recovery
As soon as you selected it, the application asks you if you would like to write this image to the appropriate partition (boot or recovery)
After successful writing it will ask you for booting from that partition, e.g. propose to reboot into your another rom or recovery
For sure all the settings like path where to keep images and boot/recovery partition names can be fixed appropriately to your device at the Settings tab
For sure the application requires root permissions, e.g. your device must be rooted. You can also check this from Settings tab
The application file: View attachment bootmanager-1.0.apk - feel free to install it to your device and use posting me bug reports
P.S. The only thing I've forgotten - the button to create native boot image file backup You still need to do it manually, sorry Hopefully in next release, if there be people interested in N8xx Boot Manager
P.P.S. Generally this program can be used for any device - just put correct images and correct boot partition names
P.P.P.S. Why N8xx and not N8xxx or N80xx? Because I've missed one symbol when typed application name in Android Studio and was too lazy to change that later :laugh:
N80xx Boot Manager
Updated version of N80xx Boot Manager: View attachment bootmanager-1.1.apk
Changelog:
Fixed application name
Fixed images path detection when no settings were changes
Added "Backup boot partiton" and "Backup recovery partition" buttons
Thus, now to install CM 10.2 as dual boot you don't need to go to ADB or terminal - just upload 3 img files to your device proper locations, installl boot manager apk, create stock boot/recovery partitions backup, then select what you want to boot and boot to that rom!
P.S. Going to update first post of this thread with steps based on Boot Manager, just would be nice if someone confirm that it works.
swamimahesh said:
Can't download last file
Click to expand...
Click to collapse
Re-uploaded.
I love u man
Finally alittle love for our device :crying:
Do I have to reinstall apps when booting to cm?
edit: I dont really understand the first step when you extract data and system.img. Can you explain more clearly the procedure?
edit2: did anyone do this dualboot successfully?
data.img.gz
Hi,
Thanks for this post !
The unpack data.img.gz don't work for me, an error occurs (with several softwares).
The md5 is ok.
Could you repost this file ?
TY.
:angel:
I can not use the n80xx boot manager app. It was failed to back up recovery or boot img. And it can not detect backup folders also. I am using revolution hd9 on n8000
Sent from my GT-N8000 using Tapatalk
netj said:
Hi,
Thanks for this post !
The unpack data.img.gz don't work for me, an error occurs (with several softwares).
The md5 is ok.
Could you repost this file ?
TY.
:angel:
Click to expand...
Click to collapse
Looks like file hosting has disk issues thus my files become broken. System.img re-uploaded already. Now please try that View attachment data.img.gz and let me know if it works for you.
muop_92 said:
I can not use the n80xx boot manager app. It was failed to back up recovery or boot img. And it can not detect backup folders also. I am using revolution hd9 on n8000
Sent from my GT-N8000 using Tapatalk
Click to expand...
Click to collapse
I'm using the same Revolution HD 9.0 by mike1986 and it works for me. The backup might fail if backup folder is not available. By default it is trying to use external sdcard for backups, it is looking for /mnt/extSdCard/images/boot and /mnt/extSdCard/images/recovery paths for the purpose. Please create those folders if you don't have it, or change boot manager settings according to your thought where the backups should be. The boot and recovery folders should exist anyway, e.g. it is up to you to create them.
X-Stranger said:
I'm using the same Revolution HD 9.0 by mike1986 and it works for me. The backup might fail if backup folder is not available. By default it is trying to use external sdcard for backups, it is looking for /mnt/extSdCard/images/boot and /mnt/extSdCard/images/recovery paths for the purpose. Please create those folders if you don't have it, or change boot manager settings according to your thought where the backups should be. The boot and recovery folders should exist anyway, e.g. it is up to you to create them.
Click to expand...
Click to collapse
Where is /mnt ? I saw in my device only /storage/extSdCard
Sent from my GT-I8160 using Tapatalk 2
muop_92 said:
Where is /mnt ? I saw in my device only /storage/extSdCard
Click to expand...
Click to collapse
It's the same. External sdcard is available on both these paths as far as I know. You can change it otherwise in application settings tab.
Ok !
X-Stranger said:
Looks like file hosting has disk issues thus my files become broken. System.img re-uploaded already. Now please try that View attachment 2519204 and let me know if it works for you.
Click to expand...
Click to collapse
Hi,
It's Ok !
Thanks !
I have just modify the paths :
dd if=/dev/mmcblk0p6 of=./recovery.img --> dd if=/dev/block/mmcblk0p6 of=./recovery.img
dd if=./cyanogen.img of=/dev/mmcblk0p6 --> dd if=./cyanogen.img of=/dev/block/mmcblk0p6
:good:
Droid Turbo System Image Tutorial
So I've noticed there isn't yet a guide on how to modify a system image for the Turbo and thought I would write one up. Note that anything you do here can very easily brick your phone, and I'm not responsible for anything that breaks, bricks, catches on fire, causes Skynet to become sentient, or eats your cat.
Here's what you need:
A rooted system image (can be found here)
A linux distro, either running natively or in VirtualBox (Ubuntu is a good choice)
IF YOU'RE USING LINUX NATIVELY:
Put the system image somewhere on an ext4 file system you have access to, such as in your home directory (/home/user)
Make sure loop device support is installed (this will vary by distro but should be installed by default on Ubuntu)
Make sure the loop kernel module is loaded:
Code:
lsmod | grep loop
As long as the command returns text, you're good.
If it is not, load it:
Code:
sudo modprobe loop
Make a mountpoint:
Code:
sudo mkdir /mnt/turbo
And finally, mount the image:
Code:
sudo mount -t ext4 -o loop /path/to/turbo/image /mnt/turbo
And the image will be accessible at /mnt/turbo/. Note that you'll need root permissions to access the files. To open the file manager as root under Ubuntu:
Code:
sudo nautilus
Navigate to /mnt/turbo to access the image and modify whatever you feel like.
IF YOU'RE USING VIRTUALBOX:
Please note that I'm writing these instructions under Linux. YMMV.
You'll have to convert the turbo's system image to something VirtualBox can recognize. To do this:
Code:
VBoxManage.exe convertdd turbo_system.img turbo_system.vdi
Load VirtualBox, but don't start your virtual machine yet.
Right click on your VM and open Settings.
Navigate to Storage and select Add Hard Disk.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Select your Turbo's system image in vdi format.
Click OK and close the settings window.
Start the VM.
Once you're all logged in, you can open your file manager and see if the image is already visible in the sidebar for mounting. If so, just click to mount and you're all good, although as above you'll have to be root in order to modify it. To open the file manager as root under Ubuntu:
Code:
sudo nautilus
If the image is not in the sidebar of your file manager, you'll have to mount the image manually. Use blkid to find a list of devices attached to the virtual system; the one we want is of type ext4, and *should* be the last device in the list. You can double check by finding the size of the device:
Code:
sudo blockdev --getsize64 /dev/sdX
where X is the letter of the device. This should return 3 GB or so.
Make a mountpoint:
Code:
sudo mkdir /mnt/turbo
Mount the image:
Code:
sudo mount -t ext4 /dev/sdX1 /mnt/turbo
where X is the letter of the device.
Open your file manager as root and navigate to /mnt/turbo. Under Ubuntu this would be:
Code:
sudo nautilus
Shut down your VM when you're done playing around.
Once you're done modifying the image, you need to convert it back to a raw .img format.
Code:
VBoxManage.exe clonehd turbo_system.vdi turbo_system.img --format raw
And that's it! Try not to break anything too badly. Make sure you unmount the image and/or stop your VM before flashing! This is the first guide I've written, so let me know if there's any questions you have or any improvements I can make.
First off, thanks for putting this tutorial together. I am running Windows 7 and I have downloaded all of the files that are needed to set up my virtual machine as well as the /system image that you linked to. I have, as far as I can tell, successfully added the Ubuntu image but I am stuck at adding the /system image as a HDD. I click the "Add Hard Disk" button followed by "Choose existing disk" then browse to the path that my image is in. With the default settings I can't see the .7z archive that I downloaded or the .img file that I extracted from it using WinRar. Next I tried changing the file type drop down to "All files" which allowed me to see both file types. I tried selecting both of them (at different times) and both files produce the following error when I click "Open":
Failed to open the hard disk file C:\Users\Chris & Kymber\Droid Turbo\Shared VM\xt1254.system.Blur.21.44.12.quark_verizon.rooted.ext4.img\xt1254.system.21.44.12.quark_verizon.rooted.ext4.img.
Could not get the storage format of the medium 'C:\Users\Chris & Kymber\Droid Turbo\Shared VM\xt1254.system.Blur.21.44.12.quark_verizon.rooted.ext4.img\xt1254.system.21.44.12.quark_verizon.rooted.ext4.img' (VERR_NOT_SUPPORTED).
Click to expand...
Click to collapse
I get the same error message whether I attempt to add it as an IDE or SATA drive. Am I doing something wrong or missing a step here?
Ok, I think I may have figured it out. I used the VBoxManage.exe convertdd command to convert the .img file to a .vdi file that VirtualBox can handle. I now have the drive mounted in my VM and using the command "sudo nautilus" (gksudo said it was not installed, I'm guessing this varies between different copies of Linux?) I was able to achieve root access to the drive so that I can modify it. When I'm done, can I simply use the VBoxManage.exe convertdd command from windows to convert the file back from .vdi to .img?
If you are changing things and flash an unbootable system image can you just flash a good image to recover? I would assume so since your reflashing the entire system partition.
thecaptain0220 said:
If you are changing things and flash an unbootable system image can you just flash a good image to recover? I would assume so since your reflashing the entire system partition.
Click to expand...
Click to collapse
Yep, basically flash the image that is in the mofo guide and you're back in action.
Good Idea!
Thanks for this primer on the subject! Would it be possible to please throw us some links on how to install Xposed framework, updated SuperSU Pro, wifi tethering, or remove bloatware? With any luck we can start altering the stock Moto images we have in the Dev section.
BEDickey said:
Thanks for this primer on the subject! Would it be possible to please throw us some links on how to install Xposed framework, updated SuperSU Pro, wifi tethering, or remove bloatware? With any luck we can start altering the stock Moto images we have in the Dev section.
Click to expand...
Click to collapse
You wouldn't want to alter those imaged, as they are not pre-rooted (unless you feel like doing that part yourself). It would be best to modify the image that comes with mofo as a starting point.
brennam7 said:
You wouldn't want to alter those imaged, as they are not pre-rooted (unless you feel like doing that part yourself). It would be best to modify the image that comes with mofo as a starting point.
Click to expand...
Click to collapse
I'm not saying we can't. I'm completely new to this,just trying to wrap my brain around it and participate.
I mounted the image in Linux and removed a few files to test it out. Then I unmounted the image. It seems like the modified image is the same size. Does the image retain its size? Is there a way to compact the image? I am going to try flashing it now and see if my changes are there.
thecaptain0220 said:
I mounted the image in Linux and removed a few files to test it out. Then I unmounted the image. It seems like the modified image is the same size. Does the image retain its size? Is there a way to compact the image? I am going to try flashing it now and see if my changes are there.
Click to expand...
Click to collapse
Yes, the image will retain its size.
BEDickey said:
Thanks for this primer on the subject! Would it be possible to please throw us some links on how to install Xposed framework, updated SuperSU Pro, wifi tethering, or remove bloatware? With any luck we can start altering the stock Moto images we have in the Dev section.
Click to expand...
Click to collapse
I'll look into this later today
cstone1991 said:
Ok, I think I may have figured it out. I used the VBoxManage.exe convertdd command to convert the .img file to a .vdi file that VirtualBox can handle. I now have the drive mounted in my VM and using the command "sudo nautilus" (gksudo said it was not installed, I'm guessing this varies between different copies of Linux?) I was able to achieve root access to the drive so that I can modify it. When I'm done, can I simply use the VBoxManage.exe convertdd command from windows to convert the file back from .vdi to .img?
Click to expand...
Click to collapse
Yes this should work, I'll update the OP to include this information, sorry
Edit: this doesn't work, I'll be working on a solution today, hang tight everyone
Ekkoria said:
[*]Navigate to Storage and select Add Hard Disk.
[*]Select your Turbo's system image.
Click to expand...
Click to collapse
So virtualbox doesnt let you mount an img as a harddrive. I used
VBoxManage.exe convertdd system.img system.vdi
I was able to then add the system.vdi as a harddrive, booted up ubuntu and finished following guide/making changes. (putting in my own hosts file.. 5mb addition)
After shutting down guest, I did the reverse of the above command to get back to an img...
Its 600megs short of the original img, so obviously something isnt right. Mofo says its not a valid ext4 so I did something wrong.
I really just want the modified hosts file working, adaway and adfree modify the hosts at first, and after a while it gets corrupt/reverts, I imagine because it was modified after the phone boots.
Ugh.
ntxct said:
So virtualbox doesnt let you mount an img as a harddrive. I used
VBoxManage.exe convertdd system.img system.vdi
I was able to then add the system.vdi as a harddrive, booted up ubuntu and finished following guide/making changes. (putting in my own hosts file.. 5mb addition)
After shutting down guest, I did the reverse of the above command to get back to an img...
Its 600megs short of the original img, so obviously something isnt right. Mofo says its not a valid ext4 so I did something wrong.
I really just want the modified hosts file working, adaway and adfree modify the hosts at first, and after a while it gets corrupt/reverts, I imagine because it was modified after the phone boots.
Ugh.
Click to expand...
Click to collapse
Odd. Virtualbox may have compressed the image. See if you can turn that off. I'll work on it myself later today, see if I can get it working
http://forum.xda-developers.com/nexus-4/general/diy-manually-installing-xposed-t2369618
Found this guide to install xposed manually will try it out soon
ntxct said:
So virtualbox doesnt let you mount an img as a harddrive. I used
VBoxManage.exe convertdd system.img system.vdi
I was able to then add the system.vdi as a harddrive, booted up ubuntu and finished following guide/making changes. (putting in my own hosts file.. 5mb addition)
After shutting down guest, I did the reverse of the above command to get back to an img...
Its 600megs short of the original img, so obviously something isnt right. Mofo says its not a valid ext4 so I did something wrong.
I really just want the modified hosts file working, adaway and adfree modify the hosts at first, and after a while it gets corrupt/reverts, I imagine because it was modified after the phone boots.
Ugh.
Click to expand...
Click to collapse
Try the following:
Code:
VBoxManage.exe clonehd path/to/turbo.vdi turbo.img --format raw
Ekkoria said:
Try the following:
Code:
VBoxManage.exe clonehd path/to/turbo.vdi turbo.img --format raw
Click to expand...
Click to collapse
Hey! Same size as original now. Thanks, Ill keep moving forward
UPDATE:
Flashed completed, booted normally. Verified the edited hosts file was there, it was. Everything seems to be working how I was hoping! Oddly the system did create (or I did along the way) a second hosts file in the etc folder, "hosts~" which is a default hosts file. However the system doesnt seem to use it, just the edited one so its no big deal but maybe its a permission issue?
ntxct said:
Hey! Same size as original now. Thanks, Ill keep moving forward
UPDATE:
Flashed completed, booted normally. Verified the edited hosts file was there, it was. Everything seems to be working how I was hoping! Oddly the system did create (or I did along the way) a second hosts file in the etc folder, "hosts~" which is a default hosts file. However the system doesnt seem to use it, just the edited one so its no big deal but maybe its a permission issue?
Click to expand...
Click to collapse
Not sure about the hosts deal, but hey, if it works right?
OP updated to include the new information.
Ekkoria said:
Not sure about the hosts deal, but hey, if it works right?
OP updated to include the new information.
Click to expand...
Click to collapse
So i got this going finally. Removed a bunch of bloat, shot the lollipop boot animation in there, as well as some xposed parts. Compiling it back to system.img now, but its sitting at 0% for quite some time. Not sure if thats normal?
EDIT: oh dear christ it just went to 10%. This is going to take some time
EDIT 2: And now it sits at the boot animation but never boots. Not sure why, as i didn't really make any major changes. time to pick this think apart.
hi, have you installed xposed successfully and does it function correctly?
123421342 said:
http://forum.xda-developers.com/nexus-4/general/diy-manually-installing-xposed-t2369618
Found this guide to install xposed manually will try it out soon
Click to expand...
Click to collapse
Haven't seen this mentioned, but might have missed it: can we symlink /system/etc/hosts to /data/data/hosts (before flashing) to maintain write access to the hosts file?
Guide: Getting Xposed RunningThis morning, I finally managed to get Xposed up and running on my Turbo. So I thought I'd write up a guide as to how!
What you'll need:
A paid copy of Mofo (obviously)
Either a modified system image containing Xposed already, or if you like, you can modify one yourself as described in this tutorial. I've already created a modified system image to include Xposed as well as Wifi Tethering and a modified hosts file for ad blocking.
The Xposed Installer apk
Xposed Installer needs to be installed on your phone
Terminal Emulator and ES File Explorer from the play store need to be installed on your phone
A rooted image flashed to your phone
Before flashing anything, this is what you need to do:
On your computer, find your de.robv.android.xposed.installer_v33_36570c.apk and rename it to be a .zip file.
Open this .zip file and extract /assets/XposedBridge.jar and, if you're modifying your own system image, extract /assets/arm/app_process_xposed_sdk16 as well.
Put XposedBridge.jar somewhere on your phone, I like to use the Downloads folder so I don't lose track of it later.
In ES File Explorer, navigate to /data (NOT SDCARD/DATA)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make sure it doesn't say sdcard > data!
Create a folder called "xposed"
Long press the folder, select properties, and set permissions to 755
Set the owner of the folder to root and the group to shell
Move XposedBridge.jar into the xposed folder we just created.
Make the permissions of XposedBridge.jar 644
As before, make the owner root and the group shell.
Open the Xposed Installer app on your phone.
Open terminal emulator and type
Code:
ps | grep xposed
This will return a pattern like the following. Make a note of the first seven characters, as shown (the first is a lowercase u)
Return to /data/xposed
Create two new files: modules.list and modules.whitelist
Make the permissions on both files 644 as above
Set the owner to the seven characters we noted down earlier and the group to shell on both files
If you're flashing a pre-compiled image with Xposed, you're done here! Go ahead and flash, and enjoy!
If you're modifying your own system image, you've got some more work to do. Take app_process_xposed_sdk16 from the Xposed apk and rename it to app_process.
In your turbo system image, navigate to /bin/ and replace app_process with the one from Xposed Framework. Make sure its permissions are set to 755:
Code:
sudo chmod 755 /path/to/img/bin/app_process
Linux does not allow setting the group of a file to a nonexistent group, so on your pc you'll have to make a shell group:
Code:
sudo groupadd shell
Change the group of app_process to shell:
Code:
sudo chgrp shell /path/to/img/bin/app_process
You're ready to flash!
NOTE: If XposedBridge.jar reports problems, try setting installation mode in the Xposed installer app to recovery (flash manually) and hitting install, then reboot.
You're done! Xposed should show up as installed! Don't use any modules that require system write access, such as replacing system icons, but most modules (ie GravityBox) work fine without it.
Ekkoria said:
This morning, I finally managed to get Xposed up and running on my Turbo. So I thought I'd write up a guide as to how!
Click to expand...
Click to collapse
Gahhh I was working all day on getting Xposed baked in
Thanks for the write up! I'm finding modifying the image file and flashing it to be just as addictive if not more than flashing someones prebuilt roms on other devices. I never got into compiling android so this feels like a way to tinker on my own without jumping into the deep end of code.
ntxct said:
Gahhh I was working all day on getting Xposed baked in
Thanks for the write up! I'm finding modifying the image file and flashing it to be just as addictive if not more than flashing someones prebuilt roms on other devices. I never got into compiling android so this feels like a way to tinker on my own without jumping into the deep end of code.
Click to expand...
Click to collapse
Same here! When I finally opened Xposed Installer and saw it read the framework as installed, I've almost never been so excited about something Android.
i dont need it but its a great guide, easy, short and with pictures!
Does the phone need to be flashed with a rooted image, like that in the tutorial of how to modify system images? I can't write to /data, presumably because I don't have the rooted image flashed yet. Also my /data directory is empty.
I have a copy of mofo, and copies of the rooted system image and your already compiled system image. Is there something I am missing? Thank you in advance.
Thanks so much man, about to flash. Will let you know how it goes.
Ah damn, I actually just did a bit different process of installing Xposed on a image for myself, (which involved baking it into the rom that didn't have it) totally got it working and I've rebooted 3 times so far and everything sticks. Loving having battery percentage now! I can write a quick tutorial writing xposed files into a fresh rooted image via Virtualbox and such... Took me a few hours
It did not work for xposedbridge.jar
aven1357 said:
Does the phone need to be flashed with a rooted image, like that in the tutorial of how to modify system images? I can't write to /data, presumably because I don't have the rooted image flashed yet. Also my /data directory is empty.
I have a copy of mofo, and copies of the rooted system image and your already compiled system image. Is there something I am missing? Thank you in advance.
Click to expand...
Click to collapse
Yes, you will need to be rooted first to perform these actions. Apologies for not originally including this. OP updated
savagebunny said:
Ah damn, I actually just did a bit different process of installing Xposed on a image for myself, (which involved baking it into the rom that didn't have it) totally got it working and I've rebooted 3 times so far and everything sticks. Loving having battery percentage now! I can write a quick tutorial writing xposed files into a fresh rooted image via Virtualbox and such... Took me a few hours
Click to expand...
Click to collapse
Yes please do so. I'd be very interested.
Sent from my XT1254 using XDA Free mobile app
I am having trouble with es file explr it tells me the operation failed when trying to do anything I have root and I enabled root for ES it seemed to work on root browser fine (I reset my device and just installed es so far)
edit checked and the root enhancement options are greyed out?
After following directions for all files and then subsequent flashing of your pre-built image xposed installer still reports framework problem. I've gone back and double checked the user:group and perm masks and everything looks good. Any ideas what else I should check?
I am having same problem as u smokie
smokie75 said:
After following directions for all files and then subsequent flashing of your pre-built image xposed installer still reports framework problem. I've gone back and double checked the user:group and perm masks and everything looks good. Any ideas what else I should check?
Click to expand...
Click to collapse
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Ekkoria said:
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Click to expand...
Click to collapse
Thanks! That worked!
Thanks for this , works great , now we just need one with busybox preinstalled
Stuck at this point any help?[/ATTACH]
Ekkoria said:
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Click to expand...
Click to collapse
so will doing this enable gravitybox to work on the turbo?
hmltnjrmy7 said:
Stuck at this point any help?[/ATTACH]
Click to expand...
Click to collapse
You should be able to foloow the instruction you quoted from that point. You should go back and check your permissions, ownership and group for the 4 files. first
Do the change in install mode to manual. Hit install and go to recovery
recovery should give you the dead droid an then reboot
Also don't worry if the group "shell" shows up as something else in app_proces
rayjr13 said:
You should be able to foloow the instruction you quoted from that point. You should go back and check your permissions, ownership and group for the 4 files. first
Do the change in install mode to manual. Hit install and go to recovery
recovery should give you the dead droid an then reboot
Also don't worry if the group "shell" shows up as something else in app_proces
Click to expand...
Click to collapse
Lol the dead droid freaked me out at first, but I'm so happy xposed finally works!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Fastboot Enhance
What it can do?
- Show fastboot vars
- Switch between fastbootd & bootloader
- Switch between A & B slot
- Flash Payload.bin in fastbootd
- Flash images
- Erase partitions
- Delete logical partitions
- Create logical partitions
- Resize logical partitions
- Unpack Payload.bin
- Extract specific image from Payload.bin
- Show Payload vars
- Show dynamic partition metadata
And above all, it has friendly GUI
Download
Releases · libxzr/FastbootEnhance
A user-friendly Fastboot ToolBox & Payload Dumper for Windows - libxzr/FastbootEnhance
github.com
By using this, you can freely switch between different versions of HydrogenOS & OxygenOS & Custom ROMs.
It is mostly tested on 8T but should work fine on any device shipped with dynamic partitions.
Notes for fastboot visualization
- You need to pre-install related fastboot usb drivers to make sure the device can be recognize by the software.
- Only in fastbootd or bootloader mode can the software recognize your device.
reserved2
I wonder if this would work with kb2007 TMO to go to ColorOS? I will download a check it out, thanks for the contribution!
xzr467706992 said:
Fastboot Enhance
Click to expand...
Click to collapse
Dev
xzr467706992thanks for making this tool! I created (modified) a non-working OTA incremental update Linux program to install 11.0.9.9.KB05AA on my rooted Op8T (not available as a full update yet) and this program notified me that the -cow files, when I clicked on install from payload.bin, had to be deleted as they were temp files and taking up space in super - now I'm running an unreleased build (full update) on my Op8T!!! I have no idea where you found documentation on these temp -cow files, but it was the missing part of all my work!!! Without those logical files present, there was enough room in Super to install the fully updated Super components (odm, product, system, system_ext, and product)! And I have to say, your program is awesome!!! Intuitive interface, high functionality, and makes things just easier to see and do.
mslezak said:
Dev
xzr467706992thanks for making this tool! I created (modified) a non-working OTA incremental update Linux program to install 11.0.9.9.KB05AA on my rooted Op8T (not available as a full update yet) and this program notified me that the -cow files, when I clicked on install from payload.bin, had to be deleted as they were temp files and taking up space in super - now I'm running an unreleased build (full update) on my Op8T!!! I have no idea where you found documentation on these temp -cow files, but it was the missing part of all my work!!! Without those logical files present, there was enough room in Super to install the fully updated Super components (odm, product, system, system_ext, and product)! And I have to say, your program is awesome!!! Intuitive interface, high functionality, and makes things just easier to see and do.
Click to expand...
Click to collapse
Disregard I just found your thread
Great job
mslezak said:
Dev
xzr467706992thanks for making this tool! I created (modified) a non-working OTA incremental update Linux program to install 11.0.9.9.KB05AA on my rooted Op8T (not available as a full update yet) and this program notified me that the -cow files, when I clicked on install from payload.bin, had to be deleted as they were temp files and taking up space in super - now I'm running an unreleased build (full update) on my Op8T!!! I have no idea where you found documentation on these temp -cow files, but it was the missing part of all my work!!! Without those logical files present, there was enough room in Super to install the fully updated Super components (odm, product, system, system_ext, and product)! And I have to say, your program is awesome!!! Intuitive interface, high functionality, and makes things just easier to see and do.
Click to expand...
Click to collapse
Google has mentioned the copy-on-write(COW) device here
Virtual A/B Overview | Android Open Source Project
source.android.com
For virtual a/b, the COW devices are created during the process of update. When there's enough spaces in super, they'll be created there, otherwise they'll be created in /data/gsi/ota.
xzr467706992 said:
Google has mentioned the copy-on-write(COW) device here
Virtual A/B Overview | Android Open Source Project
source.android.com
For virtual a/b, the COW devices are created during the process of update. When there's enough spaces in super, they'll be created there, otherwise they'll be created in /data/gsi/ota.
Click to expand...
Click to collapse
Yes I found it there for "virtual A/B" just an hour or two ago actually. They don't explain it too well, however.
Please don't mind I have few doubts about how to use this.
1. Suppose I have installed a custom rom and now I want to go back to Oxygen OS, can I do it by flashing the payload.bin using this fastboot enhance tool? If yes, what exact steps I have to go through?
2. If I flash the payload bin using this tool, will my all partitions will be recreated automatically as it was in a fresh stock condition when I used this 8T for first time even if the custom rom did any mess up with size or anything else? Also will it cleanup inactive slot too?
Amsal1 said:
Please don't mind I have few doubts about how to use this.
1. Suppose I have installed a custom rom and now I want to go back to Oxygen OS, can I do it by flashing the payload.bin using this fastboot enhance tool? If yes, what exact steps I have to go through?
2. If I flash the payload bin using this tool, will my all partitions will be recreated automatically as it was in a fresh stock condition when I used this 8T for first time even if the custom rom did any mess up with size or anything else? Also will it cleanup inactive slot too?
Click to expand...
Click to collapse
Yes, you can switch between custom ROMs and OOS using this tool.
This tool will only flash partitions listed in payload.bin, that means other partitions will remain unchanged.
Logical partitions will be automatically resized during flashing.
This tool will not create snapshot & switch slot when flashing, which is different from a normal update or sideload. That means the current slot will be flashed with new images in payload.
Note that on 8T, only the current slot you are using is bootable because of virtual ab, DO NOT SWITCH SLOT.
xzr467706992 said:
Yes, you can switch between custom ROMs and OOS using this tool.
This tool will only flash partitions listed in payload.bin, that means other partitions will remain unchanged.
Logical partitions will be automatically resized during flashing.
This tool will not create snapshot & switch slot when flashing, which is different from a normal update or sideload. That means the current slot will be flashed with new images in payload.
Note that on 8T, only the current slot you are using is bootable because of virtual ab, DO NOT SWITCH SLOT.
Click to expand...
Click to collapse
Thanks for your clarification
So the exact steps to flash any rom(OOS, Custom Rom) would be:
1. Boot to fastbootd mode
2. Load the payload.bin in Fastboot enhance v1.8
3. Click the flash payload.bin
4. Reboot to recovery and wipe
5. Reboot to system
right?
Amsal1 said:
Thanks for your clarification
So the exact steps to flash any rom(OOS, Custom Rom) would be:
1. Boot to fastbootd/bootloader mode
2. Load the payload.bin in Fastboot enhance v1.8
3. Click the flash payload.bin
4. Reboot to system
right?
Click to expand...
Click to collapse
Yes but you need to reboot to fastbootd for logical partitions (also theres hint in software)
Btw remember to enter recovery and wipe data after flashing
xzr467706992 said:
Yes but you need to reboot to fastbootd for logical partitions (also theres hint in software)
Btw remember to enter recovery and wipe data after flashing
Click to expand...
Click to collapse
reboot to fastbootd for logical partitions? I didn't got this.
Sure I will wipe from recovery after flashing the rom!
Amsal1 said:
reboot to fastbootd for logical partitions? I didn't got this.
Sure I will wipe from recovery after flashing the rom!
Click to expand...
Click to collapse
That means: flash payload in fastbootd because we have logical partitions.
xzr467706992 said:
That means: flash payload in fastbootd because we have logical partitions.
Click to expand...
Click to collapse
How can I enter fastbootd mode bro ? Thank you
hieu76pro said:
How can I enter fastbootd mode bro ? Thank you
Click to expand...
Click to collapse
If you are in system
adb reboot fadtboot
If you are in bootloader
Press the "reboot to fastbootd" button in software
xzr467706992 said:
If you are in system
adb reboot fadtboot
If you are in bootloader
Press the "reboot to fastbootd" button in software
Click to expand...
Click to collapse
Thanks bro
I am getting this while trying to flash evo x rom payload.bin:
These are the two cow partitions I found:
Is it safe to delete these two partitions?
Amsal1 said:
I am getting this while trying to flash evo x rom payload.bin:
View attachment 5383121
These are the two cow partitions I found:
View attachment 5383123
Is it safe to delete these two partitions?
Click to expand...
Click to collapse
Yes if system update status is none