{
"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"
}
Chenxiaolong's DualBootPatcher
A small but well working alternative for Tasssadar's MultiROM...keep in mind that Dualbootpatcher works without flashing a new Kernel
Tested on tbltexx, tbltemo and should work for all other tblte-variants
Because of the very simple porting all Credits and thanks belong to chenxiaolong
His thread you can find here
Visit https://dbp.noobdev.io for further Instructions.
################################################################################xNNism.com##########
Instructions: [see also the original thread]
Installation:
Android:
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI):
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Dualbooting:
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/show....php?t=2491299
################################################################################xNNism.com##########
Download: https://dbp.noobdev.io/downloads
Source: https://github.com/chenxiaolong/DualBootPatcher​
Hello
Thank you for your work but i run note 7 port on my note edge and can not set the kernel
Anyway to set the kernel on note 7 port?
did you got a error message?
I'll test it later that evening with the same Rom. Thx for reporting.
Related
Hi all, this is my second theme. I hope you all like it!
Credits :-
Thanks to Google for the awesome Android OS
Thanks to Samsung for galaxy 3
Thanks to dhirend_6d for the theming guide
Thanks to vivekchamoli for the theme remix
Thanks to aarrun for the theme remix
ClassicTheme v1 //Download//
{
"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"
}
Frequently Asked Questions (For Noobs)
1) How to install this theme?
First of all, it requires a "deodexed" stock/custom rom and CWM recovery
Download the theme and put the .zip in your sdcard
Boot in CWM recovery and select "Wipe Cache" and "Wipe Dalvik Cache"
Reboot recovery
Select "Install .zip from sdcard" and wait till its done
Reboot & Enjoy
2) Can this theme work in JPU?
Yes, but I haven't really test it yet
3) Is there icon bug?
No, the .zip already contain some .jars and .so for fixing icon bug
4) Can this theme work in other firmwares?
I don't think so.........
Got more questions? Post Reply or PM me!
reserved for later
reserved for lateer
will it run on XXJPU?
-> cause JPU is a little different in framework files
qaysedcftgb said:
will it run on XXJPU?
-> cause JPU is a little different in framework files
Click to expand...
Click to collapse
Yes ofcourse it will run. But there s a point,
"If you're using a rom that already has 9lockmod (such as kyrillos, kyorarom, vivek's rom and etc), delete ALL the .jars and lib in the .zip before installing!!"
So if you already have 9 lockscreenmod enabled JPU in your phone, just delete the lib folder and all the jar files from /system/framework/ from the zip.
so all in one word:
it is enough to install the *framework*.apk files. Settings.apk is not really necessary.
The question comes up, because I am using a stock deodexed XXJPU and halcos 9lock package with extended power menue.
In this package there were only a few lib and jar files.
The package in this thread contains a lot of lib files. So I am a bit unsettled if it is enought to install the two framework apk files.
The aim of the game or better the root cause why this question comes up:
I have seen some strange pattern while moving the slider for unlocking the fone (4lock default). So I have decided to use invisible sliders and gre smybols.
But moving the slider very slow to the side... what do I see?
Looks like the slider description -> "freigeben" means "to release"/"unlock".
Have a look to the attachment for illustrating the words.
It´s just a cosmetic thing. So I would like to try the framework file out of this package and use my own icons for battery and so on...
If its not implemented in the apk files I assume that the *framework*.jar files may also be necessary to get exchanged.
decompiling and recompiling the *frame*.apk ends up in a mess of *.9.png errors, even unmodified, so this way is not usable for me
Thats why I want to try another theme in order to get rid of this small thing.
It runs very good on vivek's 6.0 rom
What if I'm on stock JPQ but have only 5ls and extended power menu? Do I get 9ls with theme or I have to install 9ls alone first?
Because when I first flashed JPQ and tried to install themes with 5 or 9 ls mods I had lots of crashes and new flashes...
hello all, like i said..this will work in ALL froyo base roms! so don't worry about it, just read instruction carefully
Alright, this thread is going to be dedicated to "Nooky" the supertool. What this script will do, is multiple things. Reset to factory firmware (exploit the /factory partition / bootcount.), Root, fix broken recoveries, and with root comes all of the mods for stock that I came up with. This is so then we can have everything in one tool without worrying about certain things. (also, after root, it could also install CWM recovery.)
Instructions:
I suggest that you have some kind of root shell. Either by using the adb hijack app I made found here or by being in recovery.
Extract the zip, and click "Nooky.bat" Ignore all other files, just click "Nooky" not nook and zergy. Nooky. Just needed to clarify. Anyway, then you just go through the menus and choose what you want. Enjoy.
*Note, you need to have an adb shell running as root on some of these options. So you may want to be booted into recovery off sd or something.
Features:
Root (includes nook and zergy script)
Md5sum check for recovery images.
Recovery flashers (root only.)
Reboot menu (Android and Recovery)
Reset nook to factory state (including /system and boot.) {8 failed boots method}
Auto device checker
More to come (maybe)
Download, screenshots, and changelog will be in 2nd post.
Download link:
download the awesomeness here.
Changelog:
Code:
1.0: Initial Release
Screenshots:
{
"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"
}
Thanks, it would be great if that tool has an ablility to resize the system partition of NT,
at the moment, users are only able to access 1GB via usb and repartitioning process is pretty complicated.
since there are CWM recovery img floating around the forum we can just reflash that after we repartition.
Very cool!
psh, seems more like a discussion thread >.> lol, J/k Will post video when made.
when you say install recovery, is this stock or CWM? If it is CWM, might I suggest a restore to stock flash as another option? or the reverse?
Other suggestions- stock image flasher? Stock image checker? check mounting of SD card? is it possible to use this tool to force people to boot from SD card by choosing an option here?
Just thoughts.
seems a good tool!
leegoon84 said:
Thanks, it would be great if that tool has an ablility to resize the system partition of NT,
at the moment, users are only able to access 1GB via usb and repartitioning process is pretty complicated.
since there are CWM recovery img floating around the forum we can just reflash that after we repartition.
Click to expand...
Click to collapse
We should have full use of the storage on the Nook Tablet after the next release of the CM7 ROM that Celtic, Gonce and Indirect are working on, without changing partitions at all.
Repartitioning is kinda dangerous with these things, it's not like repartitioning an SD card or a PC. This tool is for prepping/rooting/factory-resetting a nook tab, among other things. I think it's going to be pretty important as a recovery/prep tool when everyone's flashing ROMs to their NTs.
Mike is right. Also, fixed a small bug.
Sorry i don't understand only one think (i hope), To use this supertool, i have to install adb and usbdriver?
Sorry for the stupid question? but i not sure
i want to buy NT, but first, i want know how to root it?
Thanks
I themed my CM9 Galaxy Nexus notification drawer widgets to match the blue in the rest of ICS instead of the default white. I had an Epic 4G visitor ask about doing this for their phone, then a Photon user too! So I built this Zipthemer file to help y'all out. I don't have a Photon so I couldn't test this out. If you try it let me know if it works, or what doesn't work.
{
"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"
}
download zipthemer here
*How to use Zipthemer*
note: you may need a ROM you have flashed (CM9) in order to configure your edify script (this is the script that tells CWM what to do when you run your update.zip file)
1. Install zipthemer!
2. Open up the menu (on ICS it's the 3 vertical dots) and click on update edify (you will only have to do this once)
3. Updating Edify screen (complete either Option 1 or Option 2)
- option 1: browse to the ROM you have on your phone and click it -- done
- option 2: click on download, then exit out of the screen, click options (3 dots), settings, update script format, select your phone. If your phone isn't present, see option 1.
4. Download the zipthemer file (.zip), and using a file explorer, move it to the "zipthemer" folder on your sd card.
5. open zipthemer again, click the "+theme" button, select the theme you want to apply (you can select more than one, or even only certain parts of one)
6. click "*output" button and pick the name you want for your update file (or accept the default). Leave the "-update.zip" at the end of the file name and "/sdcard/" at the beginning so it will be in your sdcard root directory and easier to find when you go to flash it.
7. click "build it!", it will ask you if you want to create a backup file, I usually do just in case so I don't have to re-flash the entire ROM to undo my changes if I want to.
8. Exit zipthemer, reboot to recovery, flash your new zip file, reboot system, enjoy!
more notes:
a. as always, it's a pretty good idea to run a nandroid anytime you play with your system (this is a do as I say, not as I do kinda statement)
b. A lot of these type of themes where some system files are modified or system apps are modified, it's good to do a wipe dalvik/cache
c. if you update your ROM to a new nightly/RC/stable, re-build the zipthemer file. It's likely that this isn't necessary, but unless you know just what the CM team changed it's probably a good idea.
Can i apply this to my ics fone?
Im on ics 4.0.3/cm9/build 17/sgs I9000
Sent from my GT-I9000 using Tapatalk 2 Beta-4
softpinkishlips said:
Can i apply this to my ics fone?
Im on ics 4.0.3/cm9/build 17/sgs I9000
Sent from my GT-I9000 using Tapatalk 2 Beta-4
Click to expand...
Click to collapse
Maybe, I'll have to download the CM9 ROM for the SGS and look at the files to see. I'll look into it as soon as I can and let you know.
Sent from my Galaxy Nexus using Tapatalk
It was me who asked if you could, very glad you were able to, You Rock!!!
MoPhoACTV Initiative
Basically, there are 3 types of flash method for K900
SDFUSE
OTA Recovery
MFT (Manufacturing Flash Tool)
There is a lot of question, asking about why same version of VIBEROM_V1.0_1411_ST_K900 have so many method of flashing.
There are too many information from the general thread. so I create new thread here for beginner to understand more about flashing.
From my understanding, there are only one version ROM (eg. VIBEROM_V1.0_1411_ST_K900).
But there are a few format for different flashing method.
1) SDFUSE
This format usually flash by create sdfuse folder in internal SD. Normally for update ROM
Copy files system.img.gz, boot.bin, dnx_firmware.bin, etc. (or .inb file which is the one and only one file) into sdfuse folder.
Shutdown and boot up by pressing power + volume up for couple of seconds
select SDUpdate and press power to start.
After done select power off, then power on again. (direct reboot may cause boot loop)
2) OTA Recovery
The format of rom is in ZIP. The zip is signed and there will be checksum (SHA1 and MD5) during flash. so the zip is unable to modified before flashing.
this method normally for update ROM too.
Copy update.zip file into sd card (recommended is at root of SDCard) and shutdown.
Boot up by pressing power + volume up for couple of seconds, then select recovery.
wipe data / Factory reset and wipe cache partition ( optional, which will wipe all data in sdcard)
apply update from internal storage and select update.zip
system will reboot after done.
This does not works for me to upgrade to 4.3 where I am on Qubex Vibe ROM v4.
But there are a lot of K900 user able to flash original Vibe ROM v7 and follow the above method and upgrade successfully.
Refer this http://forum.xda-developers.com/showpost.php?p=51069544&postcount=3142 or
http://forum.xda-developers.com/showpost.php?p=51128922&postcount=3199
if you are using official Vibe Rom v7. There are a easier way to flash.
copy the downloaded OTA zip file into SD Card.
Go to System upgrade, swipe left get menu, and select tools.
Touch Install specified update package and browse for OTA Zip file in sd card.
Touch install Now.
3) MFT
This method require computer with driver and software installed and USB cable for sure.
Refer this http://forum.xda-developers.com/showpost.php?p=51162040&postcount=3245
I got this method successfully when I am on non-official Vibe rom.
Please correct me if I am wrong.
Thanks to Onesjy at lenovo forum.
http://bbs.lenovo.com/forum.php?mod=viewthread&tid=154595&extra=page=1
Edited:
From my experience, the MFT method is always succeed.
Url for latest 1418_DEV MFT : http://forum.xda-developers.com/showpost.php?p=52500023&postcount=3745
MFT
i know how to use it but where can i find Manufacturing Flash Tool 6.0.2??
As far reported to me by QuBeX the ADB mode is not working on that device... I guess for the issue we have with MFT, it is the only solution we can look for also because I haven't forum (and have to open it) a thread where to speak about the recovery of a stock ROM.
About the Method N.3, most of the compatibility issues are related to the OS you are working on.
For the Settings you have to apply what you see below...
{
"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"
}
... about the libraries, instead, download that packages and replaces (if so) the files already present in the 32 / 64bit Windows' system folders: https://drive.google.com/file/d/0B282FXce0kggSHpHSDRROFNZaEU/edit?usp=sharing
You can find the Applications as well the Drivers you need directly starting from that shared folder: https://drive.google.com/file/d/0B282FXce0kggSHpHSDRROFNZaEU/edit?usp=sharing
imei changed to null
i tried to flash viberom using sdfuse method but after flashing imei changed to null how to retore it
help
Many people here don't know how to roll back or update their phones' firmware, and that's why I'm making this guide. I hope that it's easy to understand for everyone.
HOW TO UPGRADE/DOWNGRADE STOCK OFFICIALLY
To do this process you do NOT need an unlocked bootloader, and it will NOT void your warranty. If you have an unlocked bootloader, it will also not lock it.
What you need:
-Your phone model (NOT THE MODEL LISTED ON THE FIRMWARE). Flip the phone and look where the ZTE logo is at, it should say either A2017, A2017U or A2017G.
{
"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"
}
-Stock recovery. If you didn't tamper with the device you'll most likely have this. If you have TWRP, you can use a flashable zip to get the stock recovery back. There are some for the A2017G, don't know about the others. You can find them at the Download Center. I recommend you to use the same recovery that your firmware version should have, for instance if you are on B04 use the one for B04 or maybe B03. But usually you shouldn' have trouble if you use an older one.
-The firmware that you'll install on the phone. You can either download it on a PC or on the phone itself, but you'll probably need to unzip it.
I recommend trying to download ot on the phone first. If it fails to download, the safe bet is using a PC though.
-RAR if you'll download the system on your phone, or an unzipper on your PC if you're gonna do it from there (7zip, winrar)
IF YOU ROLL BACK, ALL OF YOUR DATA (INTERNAL STORAGE INCLUDED) WILL BE WIPED. BACK UP EVERYTHING YOU CONSIDER IMPORTANT!
If you update, this usually does not happen, but always back everything up just in case.
Regardless that you download it via PC or phone, you'll need the system zip. Knowing the HARDWARE MODEL of the phone, download it either from the official ZTE pages, or via unofficial sites. If you download it from unofficial sites though, check that the zip is ~2.3 GB and that, if you open it with RAR or some zip manager, it has an update.zip inside and a PDF. If it has, follow the instructions; if not, just move it to the root of the sd card (/storage/emulated/0/) and go to Settings - Updates, and update. The A2017G has a list of previously unzipped system zips on the Guides section (Download Center by @raystef66, check it out)
If you know how to use an IDM, it can be very good on the phone. Just sayin'
For the A2017: http://www.zte.com.cn/china/sitecor...rt/detail?id=B4C0ACE418834F588FED0C72D6046C78
For the A2017G:
http://www.ztedevice.com/support/detail?id=98CEB24F9FFD433EA99EC424163149A6
For the A2017U: 'Tis a little bit more fuzzy, there's many different carrier ROMs and there's only one zip from the unlocked model page. Either find a package here on XDA or, if you solely want to update to Nougat, go to the official page and download the zip available for your carrier:
https://www.zteusa.com/support_page/
Select 'Smart phones', the carrier, and ZTE Axon 7 (Not 'ZTE Axon' nor 'ZTE Axon 7 Mini'!)
So, process:
a. If you'll use the Phone:
Once you have the system zip, install RAR from the Play store or an apk, and find the Downloads folder, and the zip you downloaded. The screenshots here are just emulating how one of the official files will look, the numbers of the zip are just random and the sizes are not realistic (I just took some files and renamed them ).
Open the zip, find the update.zip inside, select it with the checkmark, and unzip it.
RAR will ask you where to extract this. Just remove everything after /0/, like on the screenshot. Press OK.
Go to System Update on the Settings, and there should appear the zip, with an sd card icon. Press Update and you're done!
b. If you'll use the PC:
1. Download the zip on your PC.
2. Open your zip manager of choice and open the zip. Throw the update.zip on your desktop.
3. Connect your phone, open the internal storage and throw the update.zip inside.
4. Go to Settings, Updates, and the zip should pop up, with an sd-card thumbnail (even though it's not on an SD card, disregard that). Install, and you're done.