Related
Here is the full working CWM Touch recovery for Xolo Play enjoy!!
Build from http://builder.clockworkmod.com with build ID=f1c98dc9e25bfdf38e6fe7437969d8e5
Things required
1.PC with usb drivers and Android SDK tool installed
2.Rooted phone
Procedure:
1.Enable USB debugging in phone.
2.Assure if drivers are installed properly . If not then use Pdanet to install xolo play drivers or try this.
GET recovery.img FROM THE ATTACHMENTS
3.Then open cmd as administrator
[Note: You must have installed Android SDK tools ]
4..Put the downloaded recovery.img in C:\Users\[USER]\AppData\Local\Android\android-sdk\platform-tools.
5.Attach Phone through USB cable.
6.type
Code:
cd C:\Users\[B][USER][/B]\AppData\Local\Android\android-sdk\platform-tools
7.then type
Code:
adb shell
8.now type
Code:
su
9.then
Code:
reboot bootloader
10.continue
Code:
fastboot flash recovery recovery.img
DONE!!
Credit:
Code:
ankur850 for graphics.c
builder.clockworkmod.com
Google
i have added nvidia boot recovery drivers in my post...
devilex94 said:
Here is the full working CWM Touch recovery for Xolo Play enjoy!!
Build from http://builder.clockworkmod.com with build ID=f1c98dc9e25bfdf38e6fe7437969d8e5
Click to expand...
Click to collapse
The build id is outdated. Do u have a permalink?
Build seems to work. Good job! :good: Could you share with the community how you managed to make it work? Touch inside recovery doesnt work but that can easily be ignored. Testing the recovery further now. Will report back.
Edit: Touch works now. :/
deepaktom said:
The build id is outdated. Do u have a permalink?
Build seems to work. Good job! :good: Could you share with the community how you managed to make it work? Touch inside recovery doesnt work but that can easily be ignored. Testing the recovery further now. Will report back.
Click to expand...
Click to collapse
yes i used builder on builder.clockworkmod.com
Uploaded stock recovery.img then recovery.fstab and finally uploaded graphics.c from ankur850's git ( here if you need http://www.mediafire.com/?2dsls2ccps163y0 )
For me touch is working inside cwm recovery
It's full working for me
http://jenkins.cyanogenmod.org/job/recovery/33680/ <= Link to recovery
Good work bro.. :thumbup:
With the pace the development going on, I am sure that we will get custom rom for xolo t1000 soon
Sent from my XOLO Play
anyway to backup original stock recovery?
emptyragnarok said:
anyway to backup original stock recovery?
Click to expand...
Click to collapse
don't worry it's already available here - http://www.mediafire.com/folder/180y8ueauzbcy/Stock
devilex94 said:
don't worry it's already available here - http://www.mediafire.com/folder/180y8ueauzbcy/Stock
Click to expand...
Click to collapse
@devilex94 I think we just need to follow same above steps except for one thing we need to point to stock recovery if we want to revert back! is it right??
emptyragnarok said:
@devilex94 I think we just need to follow same above steps except for one thing we need to point to stock recovery if we want to revert back! is it right??
Click to expand...
Click to collapse
Yes that's right
Sent from my XOLO Play using Tapatalk 2
For those who see their stock recovery even after flashing-
Follow instructions and flash the recovery in fastboot(till step 10.) hold down the power button till it switches off, now boot to recovery by power button + volume down button and you can access CWM.
Upon exit CWM will provide a fix regarding the phone reverting back to stock recovery, accept and reboot now CWM will stick!
Alternate method
You can also Flash CWM through https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
Just place the recovery.img in the internal memory.
Open the Recovery Tools - Flasher app
Flash the recovery .
Choose Reboot to recovery.
Guys its high time we see a forum for xolo play!
Threads are all over the place! development would pick up the pace if we had a forum.
Head over to the forum request thread and upvote my request!
link- http://forum.xda-developers.com/showpost.php?p=46486866&postcount=11627
richie.slayer said:
Guys its high time we see a forum for xolo play!
Threads are all over the place! development would pick up the pace if we had a forum.
Head over to the forum request thread and upvote my request!
link- http://forum.xda-developers.com/showpost.php?p=46486866&postcount=11627
Click to expand...
Click to collapse
Yup...+1 to that . we desperately need a thread...come on guys ...need help from devs ..! :laugh:
help needed...Trouble mounting sdcard!!
Okayy...installed recovery using recovery flasher tool from playstore.... rebooted to CWM . Now it seems CWM is not recognizing my sdcard ! Tried different sdcard but of no use. Somehow its not detecting my external sdcard ....I cant take a backup,neither can I flash any zip...searched google for possible solutions but none seemed to work for me...
Log shows:
Can't mount backup path.
W:Failed to mount /dev/block/platform/sdhci-tegra.0/by-num/p1 ( no such file or directory)
I:Can't format unknown volume : /external_sd
I:Can't format unknown volume : /emmc
E:Can't mount /sdcard/
Done...
etc
Any help would be appreciated!
Still no reply....??
111kaustav111 said:
Okayy...installed recovery using recovery flasher tool from playstore.... rebooted to CWM . Now it seems CWM is not recognizing my sdcard ! Tried different sdcard but of no use. Somehow its not detecting my external sdcard ....I cant take a backup,neither can I flash any zip...searched google for possible solutions but none seemed to work for me...
Log shows:
Can't mount backup path.
W:Failed to mount /dev/block/platform/sdhci-tegra.0/by-num/p1 ( no such file or directory)
I:Can't format unknown volume : /external_sd
I:Can't format unknown volume : /emmc
E:Can't mount /sdcard/
Done...
etc
Any help would be appreciated!
Click to expand...
Click to collapse
did anybody face this issue?? DeepakTom? any idea where I should be looking at in order to fix this issue??
Reboot the phone and select external sdcard as primary storage in settings>>Storage
its done!
devilex94 said:
Reboot the phone and select external sdcard as primary storage in settings>>Storage
Click to expand...
Click to collapse
Well, I managed to fix this myself! it seems my sdacrd (8 gb transcend) somehow got corrupted. And everytime I tried to open CWM, It was not detected. So I managed to format it on my digicam. Funnily its now showing 4gb total space. Next I tried opening the CWM and this time it worked! backup went smooth, even flashed custom rom.
This is kinda strange that only half of my sdcard is accessible .Somehow the blocks got corrupted !anyway, at least its working!
Can we install this recovery using mobile uncle tool ?
your help will be really appericuated
- Dual booting is the process through which you can switch between any two or more roms without the need of wiping data or making backups before flashing, all you need to do is switch between the roms, meanwhile all the apps you've installed remain intact in their specific rom.
Click to expand...
Click to collapse
Strictly put forth by Developers for Developers! If you are inexperienced with Android Development then proceed forward with extreme caution! As for the experienced, this will be easy for you.
***DISCLAMER***
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. YOU are choosing to make these modifications!
Click to expand...
Click to collapse
As always, do anything at your own risk. The above warning/disclaimer is only there because unfortuantely there will be someone who messes this up. The following guide will be conducted straight from the phone so if you are more comfortable using a computer then you will need to adapt this guide to your prefered surroundings. Please insure you have multiple ways to go about restoring your device in case you failed to follow the instructions or misunderstood something within the instructions - A Nandroid Backup, and/or RUU, and/or a ROM fitted for your specific device which you can apply via adb sideload.
Credit goes to @dreccon for bringing this to my attention with a more clear understanding over at his thread,
[GUIDELINES]Dual-Boot on (theoretically) any Android device. He was very helpful to opening my mind and thus putting up this thread. This thread is initially based around working with K2 Variant devices, but I am also aware that this will work on many other devices too.
The following numbers I will be using for partitioning the SD Card is based on maximum used space from a Stock Rom of my own K2_CL device using 4.1.2 Jelly Bean! These numbers are not to be taken literally, so USE COMMON SENSE, and insure you know the sizes for your System, Data, and Cache Partitions!
To determine the proper sizes of your partitions you can use the apk called, Partition Table, mentioned for requirements below. That APK is literally self explanatory so I will not be going over it. You will use this APK to determine the size of each partition and its current format. Do this and take note of them.
The Secondary Rom should be equal to or greater than the Primary Rom OS.
Requirements:
Device SPECIFIC boot.img and custom recovery.img
A text editor of the sorts - I use Quoda Code Editor
A Class 6 or better SDCard (I am talking about the external)
Partition Table from the Play Store
Working roms for your device
A compression tool (I use ZArchiver from the Play Store)
AParted (SD Card Partition) from the Play Store
Steps:
A. PARTITIONING YOUR SD CARD:
Plug your memory card (SD Card) in to your computer using either a card reader or by plugging your device in via usb, and copy everything from it over to your PC as we are going to partition your SD Card (which means it WILL be wiped out). Be sure to unmount your device from your pc if plugged in via usb or any other known method.
Unmount your SD Card on your device by going to, settings > storage > unmount sdcard,on your phone and then proceed to open up the apk, AParted.
Grant root access when prompted. Decline the "Agreement" because it will just try to install junk. Tap configuration, then tap the drop box under Detected devices. You should see mmcblk0, mmcblk1, and usbdisk. If you don't have both "mmcblk0", & "mmcblk1", then stop here, because either something is wrong on your end or this guide isnt for you. If you do, then select mmcblk1 from the list, tap Save, then OK. Tap TOOLS, you should now see parts 1 through 4. "Part: 1" should say fat32, and say the size in MB of your external SD card. If it does, then tap the checkbox next to "Part: 1", next tap the drop box that says Create, select Delete and tap apply. Once done, all parts should say empty. We're going to create 4 partitions. The first partition is going to be the standard external sd partition that will show up in both roms. Tap Create on the top, tap "+", tap the box with "0MB" in it, set it to the size you want the card to be, keeping in mind, that we need space for the second ROMs' partitions. Repeat these steps for System, Data, and Cache as seen below and once completed you will tap the menu button, and tap Apply changes, when done we are finished with the partition setup.
Partition it as followed:
First Partition-FAT32 (total memory card size - I recommend at least 20mb or more depending upon the actual size of your SD Card as a whole) <----- SD CARD
This is the space you will see as your memory card (external sd) in both of your roms (Primary and Secondary).
Second Partition-EXT4 (1339mb) <------ SYSTEM
This will be the System Partition of your Secondary Rom
Third Partition-EXT4 (1165mb) <----- DATA
This is Data Partition of your Secondary Rom, apps will go here
Fourth Partition-EXT4 (220mb) <----- CACHE
You can reduce it a bit more if you want to.
B. PREPARING SECONDARY ROM'S ZIP:
Get the updater-script of the rom you want to dual boot and open it up using Quoda as mentioned in the requirements or with anything else similar to a text editor which won't disrupt the unix coding of that file when you save it later.
SEARCH FOR-mmcblk0p35 (may vary for different devices, look for "mount("ext4", "EMMC", "/dev/block/mmcblk0p35");" in the updater script in order to know what yours is)
Replace with-mmcblk1p2
Save it and move it back to its location in the rom zip (META-INF\com\google\android).
Note: if there is a data folder in the rom's zip then you also have to replace the data partition block with mmcblk1p3, like: mmcblk0p37-->mmcblk1p3
C. PREPARING SECONDARY ROM'S BOOT.IMG:
Unpack the boot.img of the rom you want to dual boot using the proper unpacking and packing binaries. This can be done using your PC and/or phone. There is also the dsixda Kitchen via Windows using Cygwin and/or Linux. However, my guide will be based on doing this directly from my phone so for those who qualify may use this thread - Unpack, Edit, Repack Boot.img/Recovery.img. Otherwise, you will need to approach this differently.
You will need to go through all files which are feasible to view and read within the ramdisk of your boot.img.
Then find and replace:
Find-[email protected]
Replace with-/dev/block/mmcblk1p2
Find-[email protected]
Replace with-/dev/block/mmcblk1p3
Find-[email protected]
Replace with-/dev/block/mmcblk1p4
Save all the files that have had these changes made to them and then repack the ramdisk with the kernel to your new dualboot.img.
D. PREPARING SECONDARY ROM'S RECOVERY (OPTIONAL IF YOU DON'T WANT TO CHANGE THE SECONDARY ROM AGAIN):
Unpack the recovery.img like you unpacked your boot.img and open '/etc/recovery.fstab'.
Edit from this (May vary with other devices):
Code:
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p20
/cache ext4 [COLOR="darkred"]/dev/block/mmcblk0p36[/COLOR]
/data ext4 [COLOR="darkred"]/dev/block/mmcblk0p37[/COLOR]
/devlog ext4 /dev/block/mmcblk0p25
/misc emmc /dev/block/mmcblk0p22
/int_sd vfat /dev/block/mmcblk0p38
/recovery emmc /dev/block/mmcblk0p21
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 [COLOR="darkred"]/dev/block/mmcblk0p35[/COLOR]
to this
Code:
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p20
/cache ext4 [COLOR="red"]/dev/block/mmcblk1p4[/COLOR]
/data ext4 [COLOR="red"]/dev/block/mmcblk1p3[/COLOR]
/devlog ext4 /dev/block/mmcblk0p25
/misc emmc /dev/block/mmcblk0p22
/int_sd vfat /dev/block/mmcblk0p38
/recovery emmc /dev/block/mmcblk0p21
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 [COLOR="red"]/dev/block/mmcblk1p2[/COLOR]
Save the file and repack the modified ramdisk with the kernel as dualrecovery.img.
E. MAKING THE UPDATE.ZIP FOR YOUR BOOT.IMG:
By now, you should have your edited boot.img (dualboot.img) and your edited updater-script. Just place both of them within the Secondary rom zip and you are now good to go to flash and/or share to others (but you better test it prior to sharing it!).
F. FLASHING/SWITCHING ROMS:
Just reboot to your recovery and flash the Secondary rom and after that flash your dualboot.img, unless you have already added it to the rom zip then you wont be required to flash the dualboot.img unless you are S-On.
To Switch between Roms just reboot to your recovery and flash your Boot for primary rom and DualBoot for secondary rom.
NOTE: you can literally flash just your stock boot.img and your primary stock rom will appear as if nothing ever happened.
Sent from my C525c using Tapatalk
Quick question. While I appreciate the tutorial greatly... wouldnt it be safer to use a recovery like SafeStrap?
What would the benefits be of using thia method over SS?
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF
This is currently built with the K2 variant devices kept in mind. I will not guarantee anyone else who does not own a K2 variant that this will work. If you do not own a K2 variant and this does work, please, comment on this thread to let myself and other viewers know. Please specify your device and Rom. However, if you read my first post and everything you saw is fitting to your device and roms, then it is VERY LIKELY that this WILL work for you - Thanks.
To automatically generate your boot.img and/or rom zip to be 'dual bootable' you must download the DualBoot_v1.0 zip at the end of this post and extract it to the root of your internal sdcard. This will save you the hassle of manually unpacking, editing, and repacking the boot.img and as well as extracting, editing, and pushing back the updater-script originally from your rom zip. This process is really fast at accomplishing its goals while doing all the work for you .
The ZipEditor.sh will use my three binaries to edit your boot.img and while doing so, it will create a temporary repack.sh file to allow it to be properly rebuilt again. It will also create a backup of your original boot.img which will be named boot1.img. The dual boot.img will be named boot2.img.
This script is literally built around my three executable binaries - unmkbootimg, mkbootfs, and mkbootimg.
Of course, in order to use the scripts, you need to have had partitioned your SD card the way I described in the first post.
Initial Setup
First of all download the zip at the end of this post, unzip it and copy the DualBoot folder to the root of your SD card.
Install Script Manager from Play Store
How to use
A. ZipEditor.sh
Download the ROM you want to install and copy the zip into /sdcard/DualBoot/OriginalZIPs
Also download a suitable GAPPS.zip and copy it to the same directory (if this applies to you)
If you need to convert additional zips, the tool is designed to process as many as it finds in this directory
Open Script Manager, browse to /sdcard/DualBoot and tap on ZipEditor.sh
In the next screen, select the first two icons on top (Favorite and SU) and then select, Run.
The tool will give you some info about your device. Check them and if they are not right, then kill the script. If they are correct, press Enter to continue. The Editor will process the zips one by one. Everytime a zip is completed, it will prompt you to press Enter.
When all zips are processed you may reboot to recovery, make a backup of your current ROM and flash them.
When you reboot, your secondary ROM will load.
B. SwitchROM.sh
The name is self-explanatory. This tool can only function if it finds the files boot1.img and boot2.img inside the /sdcard/DualBoot/img folder.
These files will be automatically generated when you convert a ROM zip in the ZipEditor. Alternatively, if you know what you are doing, you can create and put them there yourself.
Tap it in Script Manager and again select the first two icons (Favorite and SU) and Run. It will automatically detect the current ROM, flash the boot.img of the other one and prompt you to reboot. Use your Power-Menu and reboot your device. Your device will now boot to the other ROM.
So, for now, you can automatically convert zips for installation to the external partitions with ZipEditor and you can switch between your two ROMs using SwitchROM. You will notice that your normal recovery cannot backup, restore, factory-reset or wipe your secondary ROM. Therefore, @dreccon is currently working on his next project to upload another script that will function as a full fledged Recovery for the secondary ROM, so stay tuned... Meanwhile, you will be required to edit your custom recovery image manually as described in the first post. This will allow you to flash to your secondary rom. For example, the ability to flash and root your secondary rom if it happens to not be rooted.
Click to expand...
Click to collapse
Credits for the ZipEditor.sh and SwitchROM.sh goes to @dreccon
Credits for the executable binaries goes to @Modding.MyMind - That's me
kevp75 said:
Quick question. While I appreciate the tutorial greatly... wouldnt it be safer to use a recovery like SafeStrap?
What would the benefits be of using thia method over SS?
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF
Click to expand...
Click to collapse
Simple, using your sd card prevents hard bricks and or changes to your actual partitions. This prevents the user from screwing up their device, while also, this prevents malicious roms that have been improperly built to be prevented from destroying the users devices which is really helpful for those who are flashaholics and messing around with nightlies. In addition, when all is said and done, all they need to do is put back their primary Rom boot.img and they will have back their primary (or stock) Rom again as if nothing ever happened.
Buying an sd card are a dime a dozen (cell phones are not)
Sent from my C525c using Tapatalk
Oh... I dont think its a bad idea... but the could be done by creating multipe rom slots with SafeStrap.
I'm really just wondering what the benefit would be chooaing this route over another.
I for one think its a great tutorial and is definately a handy way to do it... not so keen on the sd card usage tho... just due to varying speed issues and googles words on write issues to it...
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF
kevp75 said:
Oh... I dont think its a bad idea... but the could be done by creating multipe rom slots with SafeStrap.
I'm really just wondering what the benefit would be chooaing this route over another.
I for one think its a great tutorial and is definately a handy way to do it... not so keen on the sd card usage tho... just due to varying speed issues and googles words on write issues to it...
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF
Click to expand...
Click to collapse
Aren't any issues. You are formating the sdcard to the same format as your system, data, and cache partitions. That would be ext4. With that said, I have done this on a 2gig sdcard using a deodex Rom and it ran faster and smoother than from the actual device itself. Even the first boot time of the deodex Rom was cut down dramatically.
Sent from my C525c using Tapatalk
NICE. Gotta be a class 10 card and the ext4 filesystem.
I would imagine with a slower card it would slow down... tho.
Very cool and great info.... thanks bud!
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF
kevp75 said:
NICE. Gotta be a class 10 card and the ext4 filesystem.
I would imagine with a slower card it would slow down... tho.
Very cool and great info.... thanks bud!
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF
Click to expand...
Click to collapse
Over time it may slow down some, but that would only be due to its available memory filling up which you can only imagine with a 2gig to have but only so much available space when you format it. Now, if you have like a 16 or 32 gig or something close to it, then you would be set . You could even go as far as using any extra space as a swap for more ram .
Sent from my C525c using Tapatalk
kevp75 said:
Oh... I dont think its a bad idea... but the could be done by creating multipe rom slots with SafeStrap.
Click to expand...
Click to collapse
I also failed to mention, that if you use some general common sense you can use the guidelines provided in this thread, and create additional space on the sdcard for more roms
So, instead of dual booting, you could technically have three, four, or even 5 depending on the sdcard and what your device can handle. Not to mention, it doesn't take up space on your device. It is just a matter of swapping out your sdcard which can be handy.
Sent from my C525c using Tapatalk
awesome... i'm going to bookmark this so when i can get a spare device I can give it a whirl =)
hopefully my daughter gets sick of her cracked glass s3 soon and i'll be able to do this on that HA!
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF
kevp75 said:
awesome... i'm going to bookmark this so when i can get a spare device I can give it a whirl =)
hopefully my daughter gets sick of her cracked glass s3 soon and i'll be able to do this on that HA!
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF
Click to expand...
Click to collapse
Sounds good, and remember to not flash anything to your secondary Rom with your custom recovery. It must be done with your dualrecovery. This is only optional for those who plan to keep their secondary Rom.
Sent from my C525c using Tapatalk
gotcha. Thanks for this.
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF
Nicely written guide. Well done!
One alternative to constantly flashing the boot.img is to flash the secondary one into the recovery partition and then install bootstrap recoveries to both systems. This way, each ROM would have its own recovery and you would switch ROMs by key combination at bootup.
dreccon said:
Nicely written guide. Well done!
One alternative to constantly flashing the boot.img is to flash the secondary one into the recovery partition and then install bootstrap recoveries to both systems. This way, each ROM would have its own recovery and you would switch ROMs by key combination at bootup.
Click to expand...
Click to collapse
Would do this, but as my knowledge goes, we (meaning our K2 variants) currently do not have bootstrap support at this time, but if you know how to help in that matter, please pm me
Sent from my C525c using Tapatalk
Modding.MyMind said:
Would do this, but as my knowledge goes, we (meaning our K2 variants) currently do not have bootstrap support at this time, but if you know how to help in that matter, please pm me
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
I haven't tried it. It's just an idea but I'm sure it works. As for building a bootstrap recovery, no I don't know how it's done. I was hoping you already had one.
Sent from the 3rd dimension!
dreccon said:
I haven't tried it. It's just an idea but I'm sure it works. As for building a bootstrap recovery, no I don't know how it's done. I was hoping you already had one.
Sent from the 3rd dimension!
Click to expand...
Click to collapse
I'm confident it would work. I may need to work on bringing it over to us. Will see if I can find time for that though.
Hey guys, a script is in the mix for automating all of what I described within the OP. It will save you the trouble of editing the boot.img, updater-script, and so forth. Some changes need to be made, but I cannot take credit for this. It all goes to dreccon. He is the one writing it out, and I am testing it to insure its integrity. When it is ready, I will be posting it in the third post giving full detailed instructions on how to set it up and use it.
Edit: However, you will still be responsible for formatting the sdcard yourself.
Sent from my C525c using Tapatalk
Third post has been updated. You can now use the available attachment in the third post to automatically generate your dual Rom/dual boot.img. So for those who read my guide in the first post that are scratching their heads... You don't need to anymore lol. All that is required from you is to format your sdcard.
Sent from my C525c using Tapatalk
Hey guys, I will be reconstructing the instructions for post three. Nothing to be concerned about for any of you reading this. Just to keep in accordance with a simple request out of respect and to hold true with the XDA rules.
-- Happy Hunting!!
Sent from my C525c using Tapatalk
Modding.MyMind said:
This is currently built with the K2 variant devices kept in mind. I will not guarantee anyone else who does not own a K2 variant that this will work. If you do not own a K2 variant and this does work, please, comment on this thread to let myself and other viewers know. Please specify your device and Rom. However, if you read my first post and everything you saw is fitting to your device and roms, then it is VERY LIKELY that this WILL work for you - Thanks.
To automatically generate your boot.img and/or rom zip to be 'dual bootable' you must download the DualBoot_v1.0 zip at the end of this post and extract it to the root of your internal sdcard. This will save you the hassle of manually unpacking, editing, and repacking the boot.img and as well as extracting, editing, and pushing back the updater-script originally from your rom zip. This process is really fast at accomplishing its goals while doing all the work for you .
The ZipEditor.sh will use my three binaries to edit your boot.img and while doing so, it will create a temporary repack.sh file to allow it to be properly rebuilt again. It will also create a backup of your original boot.img which will be named boot1.img. The dual boot.img will be named boot2.img.
This script is literally built around my three executable binaries - unmkbootimg, mkbootfs, and mkbootimg.
Of course, in order to use the scripts, you need to have had partitioned your SD card the way I described in the first post.
Initial Setup
First of all download the zip at the end of this post, unzip it and copy the DualBoot folder to the root of your SD card.
Install Script Manager from Play Store
How to use
A. ZipEditor.sh
Download the ROM you want to install and copy the zip into /sdcard/DualBoot/OriginalZIPs
Also download a suitable GAPPS.zip and copy it to the same directory (if this applies to you)
If you need to convert additional zips, the tool is designed to process as many as it finds in this directory
Open Script Manager, browse to /sdcard/DualBoot and tap on ZipEditor.sh
In the next screen, select the first two icons on top (Favorite and SU) and then select, Run.
The tool will give you some info about your device. Check them and if they are not right, then kill the script. If they are correct, press Enter to continue. The Editor will process the zips one by one. Everytime a zip is completed, it will prompt you to press Enter.
When all zips are processed you may reboot to recovery, make a backup of your current ROM and flash them.
When you reboot, your secondary ROM will load.
B. SwitchROM.sh
The name is self-explanatory. This tool can only function if it finds the files boot1.img and boot2.img inside the /sdcard/DualBoot/img folder.
These files will be automatically generated when you convert a ROM zip in the ZipEditor. Alternatively, if you know what you are doing, you can create and put them there yourself.
Tap it in Script Manager and again select the first two icons (Favorite and SU) and Run. It will automatically detect the current ROM, flash the boot.img of the other one and prompt you to reboot. Use your Power-Menu and reboot your device. Your device will now boot to the other ROM.
Credits for the ZipEditor.sh and SwitchROM.sh goes to @dreccon
Credits for the executable binaries goes to @Modding.MyMind - That's me
Click to expand...
Click to collapse
dang it... now i gotta get me a 64G card
Rockin it from my Rockin Smartly Deadly Venom NE5 S4 (much thanks to: @Venom0642 @ted77usa @rebel1699 @iB4STiD ~ 20GB free cloud https://copy.com?r=vtiraF
Guys,
I have had an device impacted by TWRP 2.7.X build that created the problem of not being able to mount /data and sometimes(/cache & /system) partitions.
I have managed to make it run a ROM by using information from
http://forum.xda-developers.com/showthread.php?t=1869673 & http://forum.xda-developers.com/showthread.php?t=1843062.
the problem is that the mounts are not remaining permanent and my modified boot.img does not boot the devices. So i have to mount the partition manually during the boot process over a shell and then the device boots.
Need help from experts to do a kernel which can mount sdext partition and an updated recovery image which also mounts the sdext partition as /data so that roms can be flashed easily.
I will try and do a writeup of how i made it run.
Resurrecting Pyramid
As mentioned in the earlier thread, my sensation got into trouble with TWRP 2.7 version and i was having trouble mounting /data, /system and /cache partitions.
I eventually got the /cache partition mounted by using mkfs.ext4 utility but could not get other and hence started working on a way to move both /data and /system partitions completly off SD card. Lot of people have already attempted that for other devices, feel free to go and check the threads linked in the post 1. Lets get started:
Assumptions: You have a sensation on which /data and /system partitions are an issue - not getting mounted / formatted etc. /cache is expected to be ok/working.
Requirements:
1) Your phone is booting and can go into recovery. Please get 4EXT recovery installed. You can download an img file from here
2) You have basic adb and fastboot setup on your machine(Win/Linux). Just google them out, if you dont have , there are plenty of tools out there.
3) Download Revelation 1.0.3 from here. you can choose any other ROM but i worked on this and have the boot image patched to look at /system from sd-ext.
4) download the two files attached with this thread.
Steps to recover:
1) Boot your phone in recovery. We will first get the SD Card set up. A Class 10 card is preferred, you will have a good feel on the phone.
2) Using 4EXT partition tool for sd card, create 2 sd ext partition in addition to your sdcard. I suggest first partition(which we will use as /system) to be more than 800 MB and second partition( which we will use as /data) to be more than 1024 MB.
3) Verify using the 'info' option of 4ext recovery that you can see sd-ext, sd-ext2 and sdcard partitions.
4) Extract the ROM you have downloaded using 7z/Winzip /winrar and replace the following files you have downloaded from this thread.
a) updater-script in /META-INF/com/google/android/ folder.
b) boot.img in /KERNEL folder.
5) Zip the file again and copy to your sdcard. Choose install from sdcard from the 4ext recovery menu. Choose default options in AROMA installer.
6) Reboot.
Hope your phone boots. If not, this is how you debug
Android will create a /proc/kmsg file when the kernel boots. So open two terminal(linux) windowds, in one, type this
Code:
adb pull /proc/kmsg
and in the second terminal(make sure the directory is same), type this:
Code:
cat kmsg | less
and then go through the error messages to see what is going wrong. If you can share your kmsg file created, I can try and help you debug.
Good luck !!!!!
Hi,
I followed your instructions but the Aroma installer always stops and the log shows this:
Code:
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : Revelation
ROM Version : 1.0.3
ROM Author : SebastianFM
Device : HTC Sensation/XE/4G
Start at : Fri Jan 2 00:00:31 1970
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
line 44 col 70: syntax error, unexpected BAD
2 parse errors
Installer Error (Status 6)
Jack Daniel's said:
Hi,
I followed your instructions but the Aroma installer always stops and the log shows this:
Code:
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : Revelation
ROM Version : 1.0.3
ROM Author : SebastianFM
Device : HTC Sensation/XE/4G
Start at : Fri Jan 2 00:00:31 1970
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
line 44 col 70: syntax error, unexpected BAD
2 parse errors
Installer Error (Status 6)
Click to expand...
Click to collapse
Pick the files from here and then try...
http://forum.xda-developers.com/htc-sensation/help/bricked-htc-corrupted-partitions-t2804222/page3
rmann said:
Pick the files from here and then try...
http://forum.xda-developers.com/htc-sensation/help/bricked-htc-corrupted-partitions-t2804222/page3
Click to expand...
Click to collapse
I tried that before.
Same result but it shows one error less.
Code:
...
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
1 parse errors
Installer Error (Status 6)
Jack Daniel's said:
I tried that before.
Same result but it shows one error less.
Code:
...
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
1 parse errors
Installer Error (Status 6)
Click to expand...
Click to collapse
Which recovery are you using... I have re-tested the script and it works ok for me.
rmann said:
Which recovery are you using... I have re-tested the script and it works ok for me.
Click to expand...
Click to collapse
I get the same exact error as Jack Daniel's.
I am using as recovery 4EXT Recovery Touch v1.0.0.5 RC5.
antiziclon said:
I get the same exact error as Jack Daniel's.
I am using as recovery 4EXT Recovery Touch v1.0.0.5 RC5.
Click to expand...
Click to collapse
did you try to update the recovery to the latest version?
rzr86 said:
did you try to update the recovery to the latest version?
Click to expand...
Click to collapse
Just tested with v1.0.0.6 RC3 build 8, same error
antiziclon said:
Just tested with v1.0.0.6 RC3 build 8, same error
Click to expand...
Click to collapse
redownload the zip file
after that i am out of ideas
ok, I found out the issue.
The issue is on the encoding of the "updater-script" file.
It needs to be in Unix encoding. If you use Windows (as I do) when unzipping the Zip file or when creating a new file with a text editor, the encoding gets changed and it is not Unix encoding.
To solve it:
- Open the file in Notepad++.
- Go to Edit --> EOL Conversion --> UNIX
It will change the enf of lines to comply with Unix encoding. Then add the file to the Rom zip file and you are ready to go
Enjoy!
Successful Pyramid rescue
I have a sensation with corrupted emmc caused by TWRP, /data cannot be mounted.
I followed your instructions and addition re script encoding and successfully installed Revelation to partitioned sdcard.
Phone boots and works.
That's great, thanks.
I have some questions:
1. Is 512 MB sufficient for swap partition? What would be the optimal size?
2. My sensation is s-on unlocked, and I had to flash boot via fastboot after install, 4ext did not flash it despite smartflash option turned on. Is that normal?
2. Superuser does not seem to work, I have no root. I checked with root validator and I have su binary, superuser and busybox, but no root is given to apps that require it, su binary update fails, and there are no logs left in superuser to check (or I simply don't know where to look).
Thank you.
rmann said:
As mentioned in the earlier thread, my sensation got into trouble with TWRP 2.7 version and i was having trouble mounting /data, /system and /cache partitions.
I eventually got the /cache partition mounted by using mkfs.ext4 utility but could not get other and hence started working on a way to move both /data and /system partitions completly off SD card. Lot of people have already attempted that for other devices, feel free to go and check the threads linked in the post 1. Lets get started:
Assumptions: You have a sensation on which /data and /system partitions are an issue - not getting mounted / formatted etc. /cache is expected to be ok/working.
Requirements:
1) Your phone is booting and can go into recovery. Please get 4EXT recovery installed. You can download an img file from here
2) You have basic adb and fastboot setup on your machine(Win/Linux). Just google them out, if you dont have , there are plenty of tools out there.
3) Download Revelation 1.0.3 from here. you can choose any other ROM but i worked on this and have the boot image patched to look at /system from sd-ext.
4) download the two files attached with this thread.
Steps to recover:
1) Boot your phone in recovery. We will first get the SD Card set up. A Class 10 card is preferred, you will have a good feel on the phone.
2) Using 4EXT partition tool for sd card, create 2 sd ext partition in addition to your sdcard. I suggest first partition(which we will use as /system) to be more than 800 MB and second partition( which we will use as /data) to be more than 1024 MB.
3) Verify using the 'info' option of 4ext recovery that you can see sd-ext, sd-ext2 and sdcard partitions.
4) Extract the ROM you have downloaded using 7z/Winzip /winrar and replace the following files you have downloaded from this thread.
a) updater-script in /META-INF/com/google/android/ folder.
b) boot.img in /KERNEL folder.
5) Zip the file again and copy to your sdcard. Choose install from sdcard from the 4ext recovery menu. Choose default options in AROMA installer.
6) Reboot.
Hope your phone boots. If not, this is how you debug
Android will create a /proc/kmsg file when the kernel boots. So open two terminal(linux) windowds, in one, type this
Code:
adb pull /proc/kmsg
and in the second terminal(make sure the directory is same), type this:
Code:
cat kmsg | less
and then go through the error messages to see what is going wrong. If you can share your kmsg file created, I can try and help you debug.
Good luck !!!!!
Click to expand...
Click to collapse
Ok try to make that in unix
Extreme lag
Hi there,
I followed all the staps, but when the rom was installed, it was very laggy and i experinced a lot of force closes. Is this because the partions are to small or because the sd is to slow EDIT: its a class 4 card?
Greetings,
Danil
Extreme unuseful slow
With my sensation XE i also followed all steps. Revelation 1.0.3 is booting, but not to use at all, it stucks in every step, cant even receive a call, can't go to any menu. Pls someone help me out of here. Do I need a swap partition? Or are the partitions to small? sd-ext has 1024Mib; sd-ext2 1537Mib.
danilandroid said:
Hi there,
I followed all the staps, but when the rom was installed, it was very laggy and i experinced a lot of force closes. Is this because the partions are to small or because the sd is to slow EDIT: its a class 4 card?
Greetings,
Danil
Click to expand...
Click to collapse
Hi Danil, could you solve the problem? I encounter same symptoms. My Phone: Sensation XE; Revelation 1.0.3. Cant use it at all , it boots but gets totally stuck. Have original sd, dont know the class. Greetings dididoner
dididoner said:
Hi Danil, could you solve the problem? I encounter same symptoms. My Phone: Sensation XE; Revelation 1.0.3. Cant use it at all , it boots but gets totally stuck. Have original sd, dont know the class. Greetings dididoner
Click to expand...
Click to collapse
probably you need a sdcard with high speed of w/r but i am not sure
Lag
rzr86 said:
probably you need a sdcard with high speed of w/r but i am not sure
Click to expand...
Click to collapse
I'm going to buy a sd-card class 10 and than I will try the same thing agian. I will report later.
@ rmann Btw thanks for the amazing thread, I was completely stuck and now my phone is alive again kinda.
Danil
danilandroid said:
I'm going to buy a sd-card class 10 and than I will try the same thing agian. I will report later.
@ rmann Btw thanks for the amazing thread, I was completely stuck and now my phone is alive again kinda.
Danil
Click to expand...
Click to collapse
rzr86 said:
probably you need a sdcard with high speed of w/r but i am not sure
Click to expand...
Click to collapse
dididoner said:
Hi Danil, could you solve the problem? I encounter same symptoms. My Phone: Sensation XE; Revelation 1.0.3. Cant use it at all , it boots but gets totally stuck. Have original sd, dont know the class. Greetings dididoner
Click to expand...
Click to collapse
So, I bought a class 10 card, revelation is running now!! At first start it was still very slowly an got stuck allover. But at second start it is running now! Thanks for that perfect thread!!:good:
I wonderd why vipers wont start the same way? When I try to boot it , 4ext recovery is starting rightaway with little delay!
Hi, when I got the same problem with /data, /cache and /system not mounting. I followed the steps from #2 post http://forum.xda-developers.com/showpost.php?p=55157092&postcount=2
and when I try to install from zip it says that the zip isn't meant to be flashed in recovery and it aborts the installation. First I tried renaming the new_boot.img you provided to boot.img but it's the same result.
So here you come. To read and perform this tutorial, you obviously need a first hand experience on flashing a ROM and/or kernels. Otherwise this tutorial and my efforts to get you a device with two OSes running might end up giving you a bricked device. So, if you're hearing the terms "flashing" or 'kernels' for the first time and thinking it's kinda good food, then bro, just go and taste those first.
Something's to remind before we gonna dig deep into this tutorial->
Noone but you will be responsible for what you end up with.
The warranty of your device will be voided after this if it isn't already after rooting. For MI users, the good news is that you can reclaim it by just flashing the fastboot ROM for your device.
Enough lectures. Bro let's get to work.
Things you'll be needing =>
One working Windows PC(because I doesn't know any replacement of bootimg.exe on any other OS. If you know, then let me).
ADB, fastboot and the device drivers (easily found in XDA)
Any custom CWM based recovery installed.(since TWRP is most popular, I will demonstrate using it. You can use any other you want overall process will be the same)
A custom ROM and kernel for your phone(the second os)
A class 10 memory card ( I recommend 32GB for the spaces)
PART 1: MODIFYING THE BOOT
At first, how does your device boots up? What are the partitions called /data and /system? The answer is quite simple. It's your kernel that points out the location from where the OS should be picked up. So for booting into the second OS we need some modifications to it at first.
Search and download bootimg.exe on XDA, I'll post a link later. Create two folders. Name them "Internal OS" and "External OS" respectively. Put the zip file of the OS you're currently using to the first one and the OS you're gonna use on the external storage to the second one. Rename the second OS to originalExternalOS.zip. Extract originalExternalOS.zip. Pick the boot.img file from the root of the extracted folder and move it to a new folder named "boot2". Extract the IMG using bootimg.exe. Navigate to the initrd folder and you will get a file named 'fstab".
Basically it's the file that tells the kernel which partition does the OS resides in.
Open the file in your favourite text editor.
Replace every instance of the first line with the second one:
/dev/block/bootdevice/by-name/system => /dev/block/mmcblk1p2
/dev/block/bootdevice/by-name/userdata => /dev/block/mmcblk1p3
/dev/block/bootdevice/by-name/cache => /dev/block/mmcblk1p4
Save the file without giving any extension to it. Repack it using the same tool. You'll have boot-new.img and boot-old.img. Rename boot-new.img to boot.img and replace the one in the root folder with this. Basically what we're doing here is replacing the old boot.img with the modified one.
For your knowledge, blocks are the partitions of any storage you have on your device. For example, your internal storage is partitioned to near about 30 different blocks each starting with prefix "mmcblk0p". We here just told the kernel to load the OS from the blocks mentioned. We'll be creating these blocks in the external SD card next.
PART 2: PARTITIONING THE SD CARD
Connect your device with the memory card inserted to your PC. If you haven't installed fastboot, ADB, and the drivers, do it now.
READ THE FOLLOWING CAREFULLY
Reboot the device to recovery mode. Type the commands in cmd:
Code:
adb shell
parted
unit MB
print
quit
umount external_sd
Read and store the minimum and maximum capacity of your card. Since different cards will have different capacities I will point it as variable MIN_SIZE and MAX_SIZE. You'll need to calculate and put the values in the commands. Now type the following commands on cmd:
Code:
parted /dev/block/mmcblk1
rm 1
//START_BLOCK = MAX_SIZE - 5000
mkpartfs primary fat32 MIN_SIZE START_BLOCK
//SYS_START = START_BLOCK+1
//SYS_END = SYS_START + 1200
mkpartfs primary ext2 SYS_START SYS_END
//DATA_START = SYS_END+1
//DATA_END = DATA_START + 3500
mkpartfs primary ext2 DATA_START DATA_END
//CACHE_START = DATA_END + 1
mkpartfs primary ext2 CACHE_START MAX_SIZE
//We have partitioned the memory card. Let's format them. Ignore all "Do you wish to continue" question in the next commands as we're already mentioning yes.
mkfs yes 1 fat32
mkfs yes 2 ext2
mkfs yes 3 ext2
mkfs yes 4 ext2
quit
//Now they are almost ready. Just make the newly created blocks readable by the OS.
make_ext4fs /dev/block/mmcblk1p2
make_ext4fs /dev/block/mmcblk1p3
make_ext4fs /dev/block/mmcblk1p4
//Now you get where does the blocks come in the kernel right?
exit
//You've covered up the hardest part. Let's get some coffee.
PART 3: MODIFYING THE NEW OS
You've left the OS extracted in the "External OS" folder right? It's time to do some magic in it. We're gonna tell the OS to be installed in the blocks we created just like the kernel. But wait, where does the OS know before installing where it should get installed? Well, the answer hides in the updater-script in the folder META-INF > com > google > android. Navigate yourself in it. Open the updater-script file in your favourite editor ( I use notepad++ ) and modify it in the same way as the boot.
Replace every instance of the first line with the second one:
/dev/block/bootdevice/by-name/system => /dev/block/mmcblk1p2
/dev/block/bootdevice/by-name/userdata => /dev/block/mmcblk1p3
Leave the /dev/block/bootdevice/by-name/boot as it's the fundamental block and we can't replicate it. Don't think for the /cache partition as we've already done that in the boot.img file. Now navigate to the root of the folder where you extracted the External OS. Select all files, add them to a zip file using WinRAR. Name the file to newOS.zip. Open newOs.zip and originalExternalOS.zip with WinRAR and compare them if you find any change in the folder tree. They must and they should be exactly the same. You're 80% done.
PART 4: MODIFYING THE RECOVERY
We often flash many zips including very popular Xposed and other mods to our OS right? They also look for the /system partition. So what are we gonna do? Modifying each of them? Nah. Let's modify where they get which one the /system is. The recovery. Extract the img of the recovery you're using with the same bootimg.exe. Modify exactly the same things. I.e.
Replace every instance of the first line with the second one:
/dev/block/bootdevice/by-name/system => /dev/block/mmcblk1p2
/dev/block/bootdevice/by-name/userdata => /dev/block/mmcblk1p3
/dev/block/bootdevice/by-name/cache => /dev/block/mmcblk1p4
in the following files : initrd/fstab.qcom
initrd/etc/recovery.fstab
initrd/etc/twrp.fstab(For TWRP only)
Save them. Repack. And you got your recovery-new.img and recovery-old.img. Put recovery-new.img and newOS.zip in the same folder. Now wake up, it's time for some action.
PART 5 : INSTALLING THE OS
Open cmd in the folder where newOS.zip resides. Reboot the device in fastboot mode. Type the following commands:
Code:
adb push newOS.zip external_sd
fastboot flash recovery recovery-new.img
fastboot boot recovery
Now your device should boot up in recovery mode. To check if everything has gone fine mount system using TWRP. Use twrp's built in file manager and navigate to system folder. It's empty? Yup. You've done a great job. Now flash the newOS.zip using TWRP and your device should boot up in the new OS. To cross check again remove the SD card and try to boot. If you're headed towards recovery or bootloop after that then it's a win. Put the SD card back again and watch the new OS to boot.
PART 6: SWITCHING BETWEEN THE TWO
Extract the boot.img from the "Internal OS" zip file and put it together with recovery-old.img. To check if your old system is untouched type the following commands in fastboot mode:
Code:
fastboot flash recovery recovery-old.img
fastboot flash boot boot.img
fastboot boot system
Your device should take you back to the old one. Surprised? Now let's make a switch between the two. There are two methods.
METHOD 1: USING FLASHIFY
Create two folders in your SD card. Put boot.img and recovery-old.img to one and boot-new.img and recovery-new.img to the other. To switch to the external OS, just flash boot-new.img as boot and recovery-new.img using flashify. Ignore reboot now dialog and reboot directly to the system. To go back, first install flashify in the new OS and flash boot.img and recovery-old.img. Easy right?
METHOD 2: USING ZIPS
I'm gonna tell you that tomorrow as I can write no more today.
More to come....
CREDITS:
justzzshadz from MIUI forum for this revolutionary concept. @iamsubhranil for adding TWRP, Flashify support and completely rewriting the tutorial.
Thank u so much for ur efforts... It helps me a lot
I don't understand members on xda ...why they don't give thnaks on thread ..they only see the thread and go away...
Sry 4 my english ..
Thanks again
---------- Post added at 08:07 AM ---------- Previous post was at 07:48 AM ----------
Pls lemme know that if i can use dsixda's kitchen for modifying boot.img (kernal ) ???
Coz i didn't find bootimg.exe tool... If u have then pls give me the link.
Thanks
yes you can use android kitchen
When You Will Continue Writing The Thread Im Really Interested in trying it
Faisal Z Ahmad said:
When You Will Continue Writing The Thread Im Really Interested in trying it
Click to expand...
Click to collapse
I will after a while as I'm having final exams you can still try with flashify bro
sc123001.11 said:
Thank u so much for ur efforts... It helps me a lot
I don't understand members on xda ...why they don't give thnaks on thread ..they only see the thread and go away...
Sry 4 my english ..
Thanks again
---------- Post added at 08:07 AM ---------- Previous post was at 07:48 AM ----------
Pls lemme know that if i can use dsixda's kitchen for modifying boot.img (kernal ) ???
Coz i didn't find bootimg.exe tool... If u have then pls give me the link.
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/redmi-1s/general/guide-unpack-repack-kernel-t2908458
Most comfortable
iamsubhranil said:
I will after a while as I'm having final exams you can still try with flashify bro
Click to expand...
Click to collapse
Yeah I Know I Can Try But i Need To Know Method 2 To Switch ROMS Because Second One Is Faster Using Zips Otherwise Great Post And Guide ,Thank You
Good Luck With Your Exams
Nice tutorial.
Dual boot for Mediatek devices is so easy to me. But I don't have any idea for Other devices like Samsung or Sony.
When I bought some SD Card, I'll try this one.
Keep it up!
Faisal Z Ahmad said:
Yeah I Know I Can Try But i Need To Know Method 2 To Switch ROMS Because Second One Is Faster Using Zips Otherwise Great Post And Guide ,Thank You
Good Luck With Your Exams
Click to expand...
Click to collapse
Thanx a lot
BTW flashify is also very convenient method
1)Just choose boot image from the option
2)Find and select the internal or external boot image to boot
3)Have a normal reboot
jbliz said:
Nice tutorial.
Dual boot for Mediatek devices is so easy to me. But I don't have any idea for Other devices like Samsung or Sony.
When I bought some SD Card, I'll try this one.
Keep it up!
Click to expand...
Click to collapse
This one is universal bro
iamsubhranil said:
This one is universal bro
Click to expand...
Click to collapse
I did not see you make any modification to boot.img.
Sry My bad. I didn't read at the top.
iamsubhranil said:
Thanx a lot
BTW flashify is also very convenient method
1)Just choose boot image from the option
2)Find and select the internal or external boot image to boot
3)Have a normal reboot
Click to expand...
Click to collapse
I am gonna try this anyway, maybe tomorrow
Because i want two ROMS mainly, one for CM cuz i love it, daily drivers and everday usage, second one mainly focused on battery life (when i don't use my device much)
Another Question ,How do I Flash Zips (from recovery) To A Specific ROM?
And I Have CM 12.1 And Im Using M5 Kernel so Where Do the Edit Goes?
Faisal Z Ahmad said:
Another Question ,How do I Flash Zips (from recovery) To A Specific ROM?
And I Have CM 12.1 And Im Using M5 Kernel so Where Do the Edit Goes?
Click to expand...
Click to collapse
The edit goes to the recovery. At the end of the process you'll have two different recovery files for two OSes. Flashing any zips via modified recovery will flash them straight to the new os. Switch between those recoveries as required. Read the TUT carefully.
First off doing this will void your warranty and can brick your device. Following these simple steps should work for you. I will state here and further down, make sure you download all programs needed and both recovery.img and recovery_orig.img. I am in no way resposible for your device being bricked.
**Only thing I have not tested is the external sd card, I make no promises that it works. I only have 1 sd micro card its installed in my main device. So install the recoveries and supersu to your internal sdcard.
This is for assurance wireless, I have seen one or two other n817 devices if the specs are the same, they "should" work with this twrp, but use partition backup and restore by wanam on Play store to get a recovery.img for your device. I do not use this program for system back up, for some reason it does not work properly but its fine for boot,aboot, recovery and other smaller partitions.
This is a ported twrp from kis3 twrp version 3.0.2-0 by KonstaT from here http://konstakang.com/devices/kis3/TWRP/. Also this version of chainfire su SR3-SuperSU-v2.79-SR3-20170114223742 download from here https://download.chainfire.eu/1021/. This twrp recovery has Supersu folder but I still installed the zip from recovery to be sure.
The twrp n817 recovery named: recovery.img along with the original n817 recovery named: recovery_orig.img go here https://github.com/jag9906/n817_twrp
Other programs needed [ROOT]Rashr flash tool, online nandroid backup *root*, SD maid from Play Store. The Rashr flash tool is required, you can use any back up you wish, I prefer SD maid for cleaning up system and removing/freezing programs you can use any you use, this is to remove your temp root after recovery and supersu is installed.
**Again I am stating here the Rashr flash tool is required this will allow you to install the recovery.img with a locked bootloader. This is a must to install this twrp recovery. The twrp app will not work until you have supersu installed. There are other flash tools, but this worked flawless with kingo so its the only one I will support for this guide. If you use another flash tool its on you.
First make a back up prior to installing the twrp recovery. Use the online nandoird back up of all partitions I save them as twrp. If you have external SD card you can do all at once if not do all but data and system then copy to your computer and then back up system folder. Your choice on data, I back up my apk so never data.
Next run Rashr flash tool from Play store the first option is recovery from storage, choose this option then go to your location on sdcard and select recovery.img hit ok it will take about 10 to 15 seconds and ask if you want to reboot into recovery, hit yes and then your device will reboot into recovery. Once loaded swipe and go to install, top left find your SR3-SuperSU-v2.79-SR3-20170114223742.zip file and select that, then swipe to install. Once finished hit reboot and system.
Then run SD Maid or any root tool to uninstall you have. You can now delete/remove Kingo or any root you used prior to installing the recovery and have supersu by chainfire as your root for the device.
You now have a twrp recovery, and chainfire's supersu installed on your n817 device.
thanks to KonstaT and Chainfire for the hard work they have done.
Wow, thanks.
I was able to port KonstaT's CWM for the kis3 to this device and it works almost flawlessly, but when I tried to do the same with TWRP I just got a white screen and had to pull the battery. This boots fine, so I'm interested in taking it apart and seeing what you changed.
External SD card doesn't work on my phone. Since I plan on taking it apart anyway I'll look at the fstab files, if I figure it out I'll be sure to share my changes.
Yeah like I said in post I have no external sdcard so I could not test. With putting in external a few ttimes I was looping. I think I did 6 builds and on my device which is not used. I was able to create boot, system and data backups and flash again amd install supersu from chainfire. I have built a number of kernels but wont boot. I am just going to get working kernel and nethunter it or maybe kexec hardboot for a linux. Also I rhink I used the original recovery kernel, might have gone stock.
Did you do recovery or cm 11. I tried about 5 builds of cm11 furthest i got to was loading applications screen and locking. Did you flash this twrp. With rashr app. Not sure how it will handle it being locked boot. Each of the port guides useless being locked. Days off this week might look into delving into it more. But after 5 months of headaches with exynos kernel and rom might need a break. Tired of these corps releasing broken code to stall people. 3 or 4 from scratch begings with samdung kernel between 2,000 and 6,,000 files edited on each attempt and still borked, with even.trying to back port newer versions of drivers. I have one solid kernel running but just above stock because I removed there fuelgague and charger driver with a Script for deepsleep, might be my best yet before I get a new phone in a few months. Samsung and zte plus any mediatek I'm over them now and swearing off.
I notice the line for the sdcard is commented out in twrp.fstab, I'll try uncommenting that and see what happens, but I remember to get the sdcard working correctly under CWM I had to use vold. The line for CWM was:
/devices/msm_sdcc.2/mmc_host auto auto defaults voldmanaged=sdcard0:auto,noemulatedsd
This seems to work with or without an sd-ext partition (mounting sd-ext normally as /dev/block/mmcblk1p2 works, no need to use vold for that).
jag9906 said:
Did you do recovery or cm 11. I tried about 5 builds of cm11 furthest i got to was loading applications screen and locking. Did you flash this twrp. With rashr app.
Click to expand...
Click to collapse
I did KonstaT's CWM recovery from the kis3. I think the only things I had to change were the kernel (from stock recovery), fstab (based on stock recovery, with some trial and error) and default.prop
Haven't tried flashing CM11 to this phone yet, I have tried building the device/vendor trees to build CM11 from source, but ZTE's kernel source for this device doesn't compile and KnostaT's ZTE msm8610 kernel source doesn't boot, so that's as far as I've managed to get.
I flashed this TWRP with the rashr app, but when I flashed CWM I had no problem using (from a root adb shell) "dd if=/path/to/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
I did need to (once) reboot the device with "adb reboot disemmcwp" when I initially got root before I could mount system rw and install SuperSU.
Yeah that was the issue when.I did stuff with my main phone, I only have one sdcard in main phone so I didn't get around to testung vold. That sould fix the issue. I learned that lesson a few weeks ago with my samsung phone. If it works mind posting that fike so.I can.update this twrp.so people cam atleast have a touch backup with supersu not those roots that auto install garbage apks and have ads.
I found another cm11 I will check later afyer work tomorrow and post link since kis3 is gms this one was cmda for porting rom.
ok can try porting the cm11 unofficial condor, or carbon KK unofficial condor both I think I found through xda, there is an AOPK condor MM nightly if you want to try to up to that or the lineage OS condor 14.1 with a new kernel. can google this cm-11-20140808-UNOFFICIAL-condor to get the link from xda or search here.
I got my sdcard (with sd-ext partition) working with this twrp.fstab:
Code:
# mount point fstype device [device2, parameters]
/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot flags=backup=1;
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery flags=backup=1;
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system flags=backup=1;
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache flags=backup=1;
/data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata flags=backup=1; length=-16384
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="MicroSD";storage;wipeingui;removable
/sd-ext auto /dev/block/mmcblk1p2 flags=wipeingui;removable;backup=1
I'm sure that's not quite right, there are probably some flags I'm missing and definitely some other partitions you'd want to back up. I also have TWRP 3.1.0-0 compiling for this device from source (against LineageOS cm-11.0 tree with precompiled kernel from stock recovery) and booting with internal "emulated" SD and external SD both working, but I need to tweak my BoardConfig.mk a bit more to solve a couple minor issues. If I can get that 100% working I might try to "make bacon" and see what happens, I'm pretty sure the rest of my device tree is right and I've pulled all of the vendor files from the device. I didn't remember to take a backup of my stock ROM when I rooted, but I do have a full backup of my device in its current state.
Sorry to double-post, just an update. Between what I already had, your work here and a conversation with KonstaT about kernels, I have the ZTE N817 kernel and TWRP 3.0.2-0 compiling against LineageOS cm-11.0, newer versions of TWRP may build and run fine against KitKat but the OTA tools need a newer version of Android to build.
local manifests:
https://github.com/stevenh512/local_manifest_zte_n817
device tree:
https://github.com/stevenh512/android_device_zte_n817
kernel tree:
https://github.com/stevenh512/android_kernel_zte_n817
vendor tree:
https://github.com/stevenh512/proprietary_vendor_zte_n817
Just repo init -u https://github.com/LineageOS/android.git -b cm-11.0 and copy the local manifests into .repo/local_manifests before you sync, then:
Code:
. build/envsetup.sh
lunch cm_n817-userdebug
make -j4 recoveryimage
adb push out/target/product/n817/recovery.img /storage/sdcard1/recovery-twrp-new.img
(replace /storage/sdcard1 with /storage/sdcard0 if you have no external SD)
I haven't tried to build the ROM yet, but TWRP works flawlessly, external SD and internal "emulated" (/data/media) SD are both recognized.
Have fun.
jag9906 said:
First off doing this will void your warranty and can brick your device. Following these simple steps should work for you. I will state here and further down, make sure you download all programs needed and both recovery.img and recovery_orig.img. I am in no way resposible for your device being bricked.
**Only thing I have not tested is the external sd card, I make no promises that it works. I only have 1 sd micro card its installed in my main device. So install the recoveries and supersu to your internal sdcard.
This is for assurance wireless, I have seen one or two other n817 devices if the specs are the same, they "should" work with this twrp, but use partition backup and restore by wanam on Play store to get a recovery.img for your device. I do not use this program for system back up, for some reason it does not work properly but its fine for boot,aboot, recovery and other smaller partitions.
This is a ported twrp from kis3 twrp version 3.0.2-0 by KonstaT from here http://konstakang.com/devices/kis3/TWRP/. Also this version of chainfire su SR3-SuperSU-v2.79-SR3-20170114223742 download from here https://download.chainfire.eu/1021/. This twrp recovery has Supersu folder but I still installed the zip from recovery to be sure.
The twrp n817 recovery named: recovery.img along with the original n817 recovery named: recovery_orig.img go here https://github.com/jag9906/n817_twrp
Other programs needed [ROOT]Rashr flash tool, online nandroid backup *root*, SD maid from Play Store. The Rashr flash tool is required, you can use any back up you wish, I prefer SD maid for cleaning up system and removing/freezing programs you can use any you use, this is to remove your temp root after recovery and supersu is installed.
**Again I am stating here the Rashr flash tool is required this will allow you to install the recovery.img with a locked bootloader. This is a must to install this twrp recovery. The twrp app will not work until you have supersu installed. There are other flash tools, but this worked flawless with kingo so its the only one I will support for this guide. If you use another flash tool its on you.
First make a back up prior to installing the twrp recovery. Use the online nandoird back up of all partitions I save them as twrp. If you have external SD card you can do all at once if not do all but data and system then copy to your computer and then back up system folder. Your choice on data, I back up my apk so never data.
Next run Rashr flash tool from Play store the first option is recovery from storage, choose this option then go to your location on sdcard and select recovery.img hit ok it will take about 10 to 15 seconds and ask if you want to reboot into recovery, hit yes and then your device will reboot into recovery. Once loaded swipe and go to install, top left find your SR3-SuperSU-v2.79-SR3-20170114223742.zip file and select that, then swipe to install. Once finished hit reboot and system.
Then run SD Maid or any root tool to uninstall you have. You can now delete/remove Kingo or any root you used prior to installing the recovery and have supersu by chainfire as your root for the device.
You now have a twrp recovery, and chainfire's supersu installed on your n817 device.
thanks to KonstaT and Chainfire for the hard work they have done.
Click to expand...
Click to collapse
Unfortunately Kingo can't root my device and neither can anything else...... Sucks but hey the phone was free. Hopefully something can work in the future *shrugs*
Edit: rebooted "adb reboot disemmcwp" and Kingo worked ._.
Yeah, this phone was pretty difficult before King/Kingo supported it, and with no fastboot I don't think there's any way other than a ZTE signed update to alter the /system partition without rebooting with "adb reboot disemmcwp" first. Before I discovered a post mentioning using that command to disable the write-protection on another ZTE device I was able to get a root prompt with the right SELinux context but I still couldn't write anything to /system. Once I got the write-protection disabled, I didn't even bother with any of the one-click rooting apps. I just got a root shell, mounted /system rw and proceeded to put all of the SuperSU files where they go and set their permissions by hand, rebooted and I was good to go. Of course, once I got a recovery installed I did re-flash SuperSU from an update zip just to make sure it was right.
does anyone have a stock backup, i don't kn0w what i did, but now the standard android recovery tells me there are missing files when i do md5 check and it boot loops right back to recovery, anyone have and recommendations for repair, i can get to stock recovery, i can adb side load updates or choose from cache or sd card, when i pop out the battery and plug in its recognized as:
ZTE WCDMA Technologies MSM
right before boot loop to recovery:
Product: ZTE HSUSB Device Manufacturer: ZTE Incorporated (dmesg)
while in recovery in adb sideload mode
Product: N817 Manufacturer: ZTE (dmesg)
18d1:d001 Google Inc. Nexus 4 (fastboot)(lsusb)
whitout battery black screen:
QSHSUSB_BULK qualcom CDMA technologies MSM
i dont know if im in ftm mode, screen just stays black and shows up as above? when in recovery
stevenh512 said:
I got my sdcard (with sd-ext partition) working with this twrp.fstab:
Code:
# mount point fstype device [device2, parameters]
/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot flags=backup=1;
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery flags=backup=1;
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system flags=backup=1;
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache flags=backup=1;
/data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata flags=backup=1; length=-16384
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="MicroSD";storage;wipeingui;removable
/sd-ext auto /dev/block/mmcblk1p2 flags=wipeingui;removable;backup=1
I'm sure that's not quite right, there are probably some flags I'm missing and definitely some other partitions you'd want to back up. I also have TWRP 3.1.0-0 compiling for this device from source (against LineageOS cm-11.0 tree with precompiled kernel from stock recovery) and booting with internal "emulated" SD and external SD both working, but I need to tweak my BoardConfig.mk a bit more to solve a couple minor issues. If I can get that 100% working I might try to "make bacon" and see what happens, I'm pretty sure the rest of my device tree is right and I've pulled all of the vendor files from the device. I didn't remember to take a backup of my stock ROM when I rooted, but I do have a full backup of my device in its current state.[/Q
Change sdcard to sdcard1
Click to expand...
Click to collapse
morpheous1777 said:
does anyone have a stock backup
Click to expand...
Click to collapse
I also wouldn't mind having a stock backup, unfortunately I didn't remember to take a backup before I started tinkering with my system partition, but thankfully I haven't managed to break anything I couldn't fix.
while in recovery in adb sideload mode
Product: N817 Manufacturer: ZTE (dmesg)
18d1:d001 Google Inc. Nexus 4 (fastboot)(lsusb)
Click to expand...
Click to collapse
While in this mode, are you able to actually use fastboot? I ask for two reasons. First, if you're on a stock recovery, the only way you're going to be able to restore a stock ROM (or install any other ROM) from recovery is if it's signed by ZTE, otherwise you'll need another way (like fastboot). Second, as far as I can tell, there is no fastboot on my phone.
leetree2001 said:
stevenh512 said:
I got my sdcard (with sd-ext partition) working with this twrp.fstab:
Code:
# mount point fstype device [device2, parameters]
/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot flags=backup=1;
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery flags=backup=1;
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system flags=backup=1;
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache flags=backup=1;
/data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata flags=backup=1; length=-16384
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="MicroSD";storage;wipeingui;removable
/sd-ext auto /dev/block/mmcblk1p2 flags=wipeingui;removable;backup=1
I'm sure that's not quite right, there are probably some flags I'm missing and definitely some other partitions you'd want to back up. I also have TWRP 3.1.0-0 compiling for this device from source (against LineageOS cm-11.0 tree with precompiled kernel from stock recovery) and booting with internal "emulated" SD and external SD both working, but I need to tweak my BoardConfig.mk a bit more to solve a couple minor issues. If I can get that 100% working I might try to "make bacon" and see what happens, I'm pretty sure the rest of my device tree is right and I've pulled all of the vendor files from the device. I didn't remember to take a backup of my stock ROM when I rooted, but I do have a full backup of my device in its current state.[/Q
Change sdcard to sdcard1
Click to expand...
Click to collapse
I'd really love this and I'd love it more if I could contribute in some way... this phone is painfully slow on the stock OS.
Click to expand...
Click to collapse
Have nothing to contribute right now.Just want to THANK all you guys for your unselfish work!!!
Sent from my LGLS770 using Tapatalk
Does anyone have the stock rom?? The recovery bricked my assurance n817.Please help
This worked great, thanks
---------- Post added at 10:03 PM ---------- Previous post was at 09:32 PM ----------
It works, but my system is very unstable right now. I have a feeling it's that KingCrap . It doesn't like to be replaced with another SU. That stuff is malware and I never use it unless I"m desperate. I'm going to try to push 3c toolbox to it. It won't stay up long enough to install it from playstore.
Member96 posts Thanks: 16
Does anyone have the stock rom?? The recovery bricked my assurance n817.Please help
I did a full backup of my zte n817. it's in .img format. pm me and I'll send it to my google drive and give you the link. Do you know what partition goes where? I also have that info too !! After 3 bricked phones I have learned somewhat of a lesson
I can't do anything with it now. It won't stay up long enough. I have a nandroid backup but it's on the external sd which this TWRP can't see. There isn't enough space on the internal to copy it to. I'm giving up for now, I"ve spent way too much time on a $20 phone
slacker8135666 said:
Member96 posts Thanks: 16
Does anyone have the stock rom?? The recovery bricked my assurance n817.Please help
I did a full backup of my zte n817. it's in .img format. pm me and I'll send it to my google drive and give you the link. Do you know what partition goes where? I also have that info too !! After 3 bricked phones I have learned somewhat of a lesson
Click to expand...
Click to collapse
Sent from my LGLS770 using Tapatalk