{
"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"
}
MultiROM is a one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
WARNING
It is dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
IMPORTANT
I'm not responsible for anything, you do all this on your own risk.
Once you have flashed and set up MultiROM, don't flash another boot.img using fastboot or normally. Always go to TheMultiROM Menu (3 bars in the top right corner) to flash ROMs/kernels or other mods.
If you want to uninstall MultiROM, just flash the MultiROM uninstaller.
I am not certainly sure about the compatibility with stock Roms, I still need to test this yet.
Your device must not be encrypted.
When booting another ROM, you'll notice that in some cases, you can enter the recovery of the boot.img of the ROM. Please don't use it, flash everything using MultiROM TWRP.
DOWNLOAD
you can find the MultiROM recovery and MultiROM flashable zip here: MultiROM files
INSTALLATION
Make sure you are on a Rom compatible with a kernel that can run MultiROM and flash it or use the non-kexec workaround. (See important Notices)
Reboot into MultiROM TWRP and flash the MultiROM installer
That's it. You can now go to TheMultiROM Menu (3 bars in the top right corner) to start flashing other ROMs.
Adding ROMs
Go to recovery, select TheMultiROM Menu (3 bars in the top right corner) -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to TheMultiROM Menu (3 bars in the top right corner) in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to TheMultiROM Menu (3 bars in the top right corner) -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
SOURCEs
MultiROM - https://github.com/XperiaMultiROM/multirom/ (branch master)
Modified TWRP - https://github.com/multirom-htc/Team-Win-Recovery-Project (branch android-6.0)
Kernel w/ kexec-hardboot patch - https://github.com/Myself5/kernel// (branch aosp/LA.BF64.1.2.2_rb4.7)
FAQs can be found here.
CREDITs
Myself5
Tasssadar
Olivier
nkk71
Garcia98
Thunder07
skin1980
Envious_Data
[NUT]
Panic Brothers
You might want to consider a Donation to Tasssadar, who is the Mastermind behind MultiROM
As well as a Donation to nkk71, who wrote the kexec-workaround and helped a lot
Thanks a lot to those who have donated! The 2 really deserve it!
Mesa is first.
Sent from my E6653 using Tapatalk
Issue in TWRP
MTP don't work
killedbyghost58 said:
Issue in TWRP
MTP don't work
Click to expand...
Click to collapse
That's not a twrp issue, but a kernel issue.
We'll be releasing a stock kernel that doesn't cause this problem.
oshmoun said:
That's not a twrp issue, but a kernel issue.
We'll be releasing a stock kernel that doesn't cause this problem.
Click to expand...
Click to collapse
Will Androplus kernel v31 work?
killedbyghost58 said:
Will Androplus kernel v31 work?
Click to expand...
Click to collapse
yes multirom should work on Androplus V31, since it has kexec support. I didn't test personally though so I can't guarantee it
can't find the MultiROM uninstaller? is it enough to just flash another recovery or kernel?
shafiq01 said:
can't find the MultiROM uninstaller? is it enough to just flash another recovery or kernel?
Click to expand...
Click to collapse
yes you can simply flash another boot.img and multirom will be uninstalled. To replace multirom recovery then simply flash another recovery.img
Hi, thanks for this port.
Is it possible to use stock ROM (32.1.A.1.185) as primary ROM?
Thibault1171 said:
Hi, thanks for this port.
Is it possible to use stock ROM (32.1.A.1.185) as primary ROM?
Click to expand...
Click to collapse
it should work, I did run such a setup for a while
oshmoun said:
it should work, I did run such a setup for a while
Click to expand...
Click to collapse
Okay thanks
my Z5C does't boot to recovery
EDIT: apparantly it is the recovery that doesn't work
EDIT #2: ok with the OM5Z kernel
farfetch said:
my Z5C does't boot to recovery
EDIT: apparantly it is the recovery that doesn't work
EDIT #2: ok with the OM5Z kernel
Click to expand...
Click to collapse
Its because of the different methods used to boot to the recovery, as described in the OM5Z OP. The recovery we build for MultiROM is only working with init_sony, not the init.sh bootrec scripts like it was used before/like it is used on other kernels. This is to provide compatibility with AOSP custom ROMs and hopefully all stock kernel devs will switch to our method sooner or later too.
Sent from my E6653 using Tapatalk
Myself5 said:
Its because of the different methods used to boot to the recovery, as described in the OM5Z OP. The recovery we build for MultiROM is only working with init_sony, not the init.sh bootrec scripts like it was used before/like it is used on other kernels. This is to provide compatibility with AOSP custom ROMs and hopefully all stock kernel devs will switch to our method sooner or later too.
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
But there is only a problem...Could be that my stock ROM doesn't boot on your kernel?
Sent from my E5823 using XDA-Developers mobile app
farfetch said:
But there is only a problem...Could be that my stock ROM doesn't boot on your kernel?
Sent from my E5823 using XDA-Developers mobile app
Click to expand...
Click to collapse
Kernel is updated to .224, but you're still running .163
Why don't you update to the latest version? Is it not available for your region/provider?
oshmoun said:
Kernel is updated to .224, but you're still running .163
Why don't you update to the latest version? Is it not available for your region/provider?
Click to expand...
Click to collapse
This is AndroKernel, with yours my rom won't boot
Sent from my E5823 using XDA-Developers mobile app
farfetch said:
This is AndroKernel, with yours my rom won't boot
Sent from my E5823 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thats what he just said. Ours is not working with your rom, cause your rom is outdated. Update to 32.1.A.1.224, then you can use our kernel.
Sent from my E6653 using Tapatalk
Myself5 said:
Thats what he just said. Ours is not working with your rom, cause your rom is outdated. Update to 32.1.A.1.224, then you can use our kernel.
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
How would you upgrade? I have stock ROM with DRM restored, root and Xposed
Thanks
Sent from my E5823 using XDA-Developers mobile app
No way to get it working.
Flashed last stock fw, flashed your kernel, flashed your twrp, flashed multirom zip. Stock rom doesn't start anymore, my phone freeze at android logo.
I can't nether installa X-Power 3.0...It's stuck at extracting system
I won't buy an Xperia anymore...Only Nexus or Lenovo with stock Android
farfetch said:
No way to get it working.
Flashed last stock fw, flashed your kernel, flashed your twrp, flashed multirom zip. Stock rom doesn't start anymore, my phone freeze at android logo.
I can't nether installa X-Power 3.0...It's stuck at extracting system
I won't buy an Xperia anymore...Only Nexus or Lenovo with stock Android
Click to expand...
Click to collapse
sorry that happened to you
did you check if that latest fw you flashed is really .224? I can't think of much else being the problem.
Related
I'll start by saing that all credits go to :good: pershoot :good: So be sure to thank him !!
INFO
http://droidbasement.com/db-blog/
This is Android 4.2.2 (Jelly Bean) + CM10.1 for the Samsung Galaxy Tab 10.1v
{
"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 / NIGHTLIES ARE NOW AVAILABLE !!
http://get.cm/?device=p3
INSTALLATION INSTRUCTIONS
/!\ Before doing anything make sure your bootloader is unlocked and you have a rooted device!
1. Backup your apps+data using Titanium Backup.
2. Go to http://get.cm/?device=p3
3. Download 'recovery.tar.md5' to your PC if you don't have it yet. It's Clockworkmod 6.0.1.0 (latest version). If it's not available on the above location, it's also attached to this post.
4. Download 'cm-10.1.......zip' and put it in internal storage.
5. Download the latest 'gapps-jb-*-signed.zip' from http://goo.im/gapps and put it in internal storage. gapps-minimal-jb-20121212-signed.zip has been confirmed to work fine.
6. a. Flash recovery.tar.md5 on your device using ODIN3 (go into downloading mode, wait for USB connected on screen, then select the file using PDA and click Start)
6. b. You can also use fastboot (for some reason I prefer this method). Just extract the recovery.img from 'recovery.tar.md5' and then flash it using fastboot ("fastboot flash recovery recovery.img" (permanent on device) and/or "fastboot boot recovery.img" (just boot it from pc))
7. Once in recovery: clean cache & clean dalvik cache. (I did a full wipe to be sure I don't report bugs to pershoot which are linked to data problems).
8. Flash the ROM.
9. Flash gapps.
10. Reboot
11. Enjoy your ROM :fingers-crossed:
12. Put back all your apps (using batch Titanium Backup) but don't restore system apps.
13. You're done!
If you need to flash the P4 modem:
1. Get ODIN 1.85
2. Get the Samsung drivers "SAMSUNG_USB_Driver_for_Mobile_Phones_v1_3_2300_0" (google it)
3. Install the driver for Tab
4. Download the modem image from pershoot's p3 repository
5. Boot into bootloader (press power and hold volume-up and volume-down at the same time, then select Downloading).
6. Start ODIN (you should see the first block become yellow on the screen => means your device is connected)
7. Select PDA and browse to the modem file
8. Flash it
9. You're done. Make sure you got the correct RIL by flashing the latest image.
Video made by SjPedro22
WORKING
• bluetooth
• browser
• back camera (8MP)
• gps
• install/move apps on sd card
• mobile data 3g/2g
• rotation
• sound (notifications, calls, ringtones, alarm, music)
• superuser
• MTP
• video playback
• vibration
• wifi
• youtube
• front camera
BUGS
• none! If you find one, please post them in this thread!
Great new cm10 topic thanx ori
Sent from my GT-P7100 using XDA Premium HD app
Gapps ishue
Pershoot, our "Galaxy" king!! Thank you!!
Is there anyone with problems with Gapps?
made a video for this at: http://www.youtube.com/watch?v=eUBM3Ci3J0Y&feature=youtu.be all credits went to pershoot of course!
SjPedro22 said:
made a video for this at: http://www.youtube.com/watch?v=eUBM3Ci3J0Y&feature=youtu.be all credits went to pershoot of course!
Click to expand...
Click to collapse
Nice, I have added it to the OP if I have your permission
no problem mate!
Overscorp said:
Pershoot, our "Galaxy" king!! Thank you!!
Is there anyone with problems with Gapps?
Click to expand...
Click to collapse
I got no issue with Gapps. Are you sure you used the one with date 20120717? It has to be have that date! More recent version doesn't work yet. pershoot is looking into it.
ORiZorrie said:
I got no issue with Gapps. Are you sure you used the one with date 20120717? It has to be have that date! More recent version doesn't work yet. pershoot is looking into it.
Click to expand...
Click to collapse
i got no issues either. i've flashed 20120726, and untill now, no problems at all.
Thanks for the post, is much more usefull like this man
Overscorp said:
i got no ishues either. i've flashed 20120726, and untill now, no problems at all.
Thanks for the post, is much more usefull like this man
Click to expand...
Click to collapse
Well, be carefull because pershoot posted this yesterday:
If you use gapps, do not use 0726 from goo.im. If this is installed, after powering down, journal on /data goes awry and android will not be able to boot thereafter. This condition ocurred when USB was plugged in/ADB debugging on + WiFi on. The only way to boot if this occurred was to format data via the stock recovery (i.e. wipe/data factory). 0717 works fine in this regard.
Click to expand...
Click to collapse
ORiZorrie said:
Well, be carefull because pershoot posted this yesterday:
Click to expand...
Click to collapse
how do i uninstall this pack then? now you put myself affraid lool
EDIT: however, i had already turn off the tab at least 3 times and nothing had happened
Sorry for the dumb question, but does anyone have the links to this?
Sent from my Galaxy Nexus using xda premium
Member688 said:
Sorry for the dumb question, but does anyone have the links to this?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
here you have mate, link to gapps
http://goo.im/gapps
just it the thanks button
Overscorp said:
how do i uninstall this pack then? now you put myself affraid lool
EDIT: however, i had already turn off the tab at least 3 times and nothing had happened
Click to expand...
Click to collapse
I think you're safe then. There's no need to panic and change it now
Overscorp said:
here you have mate, link to gapps
http://goo.im/gapps
just it the thanks button
Click to expand...
Click to collapse
Cheers! But I was more hoping for a link to the CM10 build. Couldn't find it in op, or on droid basement when I last checked.
Sent from my Galaxy Nexus using xda premium
Checked again and its all there.
ROM and recovery:http://droidbasement.com/galaxy/roms/cm10/p3/
Gapps:http://goo.im/gapps/gapps-jb-20120717-signed.zip
Opps, sorry and game on!
Sent from my Galaxy Nexus using xda premium
I used the 'old' recovery (the one for CM9) to flash CM10 and I had no problems.
boot in recovery
clear cache / dalvik cache
factory reset
flash cm10
flash gapps 1707
reboot and enjoy
Google Now is not working but the camera is. Restore apps with titanium is also working. Very nice work.
Wijnand85 said:
I used the 'old' recovery (the one for CM9) to flash CM10 and I had no problems.
boot in recovery
clear cache / dalvik cache
factory reset
flash cm10
flash gapps 1707
reboot and enjoy
Google Now is not working but the camera is. Restore apps with titanium is also working. Very nice work.
Click to expand...
Click to collapse
are they the same recovery, just with name difference? Or is there any difference?
sorry for the noob question
---------- Post added at 11:46 AM ---------- Previous post was at 11:24 AM ----------
sorry if i'm putting any pressure, it's not my intencion, at all! But, Pershoot, is there any final build for CM10 in the "oven"?
Anyway, i'm already very satisfied with this build!!
Thanks For The ROM
Many thanks for the ROM Pershoot and many thanks for the guide ORiZorrie.
Followed the guide and loaded the ROM on no problems.
However now the Tab wont boot, been stuck for about 20 minutes.
Anyone have any ideas?
xandurr said:
Many thanks for the ROM Pershoot and many thanks for the guide ORiZorrie.
Followed the guide and loaded the ROM on no problems.
However now the Tab wont boot, been stuck for about 20 minutes.
Anyone have any ideas?
Click to expand...
Click to collapse
wich Gapps pack you used? it could be because of the last pack installation, it's not ready yet, and could be the reason of your boot issue. you should install the 20120717 pack, for more stability
Fixed it
Overscorp said:
wich Gapps pack you used? it could be because of the last pack installation, it not ready yet. you should install the 20120717 pack, for more stability
Click to expand...
Click to collapse
Nah i used the exact right files, but for whatever reason was stuck with this boot logo.
HOWEVER:
I was able to resolve the issue myself, just took some fiddling as i didnt have my PC set up for android tinkering after a recent reformat.
once i got the SDK installed, the below is how i fixed it in case anyone else hits this same problem.
1. Boot tablet into Fastboot mode
2. Open Command Prompt (Windows)
3. Run the following commands
a) fastboot -w
b) fastboot reboot
4. voila!! fixed and boots through boot animation in approx 30 seconds.
Not sure why clearing userdata and cache from fastboot resolved it as i cleared cache and davlik cache while in CWM but for whatever reason in worked perfectly.
Thanks
Hello for all!
Have a good time in my thread!This is an instruction (or method) about how to get a rooted, deodexed, recovery, superusermod firmware (build number 199) for SXTX (UB)Attention!
Use this method only for Unlocked Bootloaders!!!
This "Method" i've been tested on my SXTX, and its working, please dont try it on SXTX "LB" or on Sony Xperia T.
I'm not responsible of sploit devices etc. Everything what you do, you doing only on your own risk!!!
Follow the instruction carefully and everything gonna be allright
Big thanks and all respect for those who make it possible:
DooMLoRD - stock SXTX kernel with dual recovery
vlad-96 (4pda.ru) - for deodexer
DavidMKD - superusermod guide
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2458144Some screens
Im installed another systemUI/Home and themes... they are not included into this method!!! Look for, deodex, root, superusermod...they are
{
"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"
}
Requirements:
Unlocked Bootloader
Installed Flashtool
Installed fastboot drivers
Installation process (UB):
Copy first
The firmware to Flashtool/firmwares folder.
The kernel.elf (dualrecovery) to Flashtool/firmwares folder (or somewhere else where you easily find)
The SuperSU to your device's sdcard
The deodexer zip to your device's sdcard
Getting stock official 199 firmware + root + dualrecovery
Power off your device. Start Flastool on your PC, flash device-> flashmode, select the "firmware" and press Flash. When the guide window pop-ups on your powered off device hold Vol- (down) and connect to PC (green led will appear). Wait until it finished. Disconnect. Don't power on your device!!!
On your powered off device hold Vol+ (up) and connect to PC (blue led will appear), then start Flashtool, flash device-> fastboot mode, select the "select kernel" (DooML0RD) and press Flash. Wait until it done. Close, disconnect. Now you have a kernel with dual recovery!!!
Turn on your device, when the violet led will appear press Vol+(up) (CWM). Go to install.zip, sdcard0 and flash UPDATE-SuperSU-v1.93.zip, reboot. Now you rooted!!!
Deodexing (includes patched services.jar aka "Superusermod")
Enter CWM, then to advanced menu and wipe dalvik cache.
Go to Install.zip and choose the "SXTX_199_Deodexer+superusermod".
Flash it.
Go to advanced menu and wipe dalvik cache!
Reboot and Enjoy!
Downloads:
Firmware: [email protected]
Kernel: SXTX_199_dualrec_kernel.rar or use link from androidfilsharing.com
SuperSU: UPDATE-SuperSU-v1.93.zip or use link from androidfilesharing.com
Deodexer: SXTX_199_Deodexer+superusermod
Additional downloads:
Deodexer (without patched services.jar aka "Superusermod"): i will upload soon
Modded services.jar for SXTX 199 users: Services_superusermod_SXTX_build_199
Some information:
Enter to recovery:
Vol up (+) - CWM
Vol down (-) - TWRP
This deodexer file is not a whole, full deodexed 199 firmware. It is just a deodexer.zip for 199 firmware which deodexing the system/app and system/framework folders, so dont try to flash it if you are not on firmware 199, otherwise you will get bootloop.
Warning!!!If you install Hexared, Robocop (maybe others too), then applying it will work only until you reboot the phone... if you reboot you will get bootloop! - im searching the solution to solve it!
But for example the UniQue theme (which also require superusermod) working perfectly even after reboot with no problems.
XDA:DevDB Information
[STOCK][JB 4.3][9.2.A.1.199][UB]SXTX Root + CWM+ Deodex+Superusermod [14.03], a ROM for the Sony Xperia T
Contributors
Midleo
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Stable Release Date: 2014-03-14
Created 2014-03-14
Last Updated 2014-03-14
thanks, this CWM kernel is touch version or normal ?
There is two recoveries, CWM, TWRP. The CWM one is simple vol+, vol-, power button and you can use swipes (i never used). The TWRP is full touch!
Sent from my LT29i using XDA Premium 4 mobile app
Midleo said:
There is two recoveries, CWM, TWRP. The CWM one is simple vol+, vol-, power button and you can use swipes (i never used). The TWRP is full touch!
Sent from my LT29i using XDA Premium 4 mobile app
Click to expand...
Click to collapse
you mean CWM with touch function ? can swipe up down left right ? not PhilZ Touch CWM right ? i like PhilZ Touch CWM than TWRP is full touch and CWM with touch
Dumb Question
If you don't mind me asking, what's the difference between SuperSU and modded services jar?
Is one for root and the other one for apk install permissions? Is that it or do they do the same thing?
devilmaycry2020 said:
you mean CWM with touch function ? can swipe up down left right ? not PhilZ Touch CWM right ? i like PhilZ Touch CWM than TWRP is full touch and CWM with touch
Click to expand...
Click to collapse
Yes simple CWM 6.0.4.5 with touch function... but its your decission...you can navigate with both (touch, buttons). It is not PhilZ touch recovery!!!
Vol+ will enter you to CWM
Vol- to TWRP (full touch)
kaleys said:
If you don't mind me asking, what's the difference between SuperSU and modded services jar?
Is one for root and the other one for apk install permissions? Is that it or do they do the same thing?
Click to expand...
Click to collapse
Im not sure for 100%, but i know that SuperSU is just giving you possibility to action with system (delete, copy, replace, cut, rename, changing permissions of system files etc.)...so its getting you full enter to system folder and others... but SuperSU dont changing the interior of apks, jar etc. on it own... it just giving you the permission for it... for ex. if you have SuperSU you can edit build.prop...
Superusermod is "disables the nasty signature verification for all apps. After applying this mod you can install apps with different signature like Xperia Z1 or newer Sony apps" -> read first strokes
Midleo said:
Yes simple CWM 6.0.4.5 with touch function... but its your decission...you can navigate with both (touch, buttons). It is not PhilZ touch recovery!!!
Vol+ will enter you to CWM
Vol- to TWRP (full touch)
Click to expand...
Click to collapse
thanks. can you make kernel with PhilZ touch recovery only ?
Midleo said:
Im not sure for 100%, but i know that SuperSU is just giving you possibility to action with system (delete, copy, replace, cut, rename, changing permissions of system files etc.)
Click to expand...
Click to collapse
Ohh alright thanks for that, was informative. Gonna upgrade with your method soon.
Thanks Again!
devilmaycry2020 said:
thanks. can you make kernel with PhilZ touch recovery only ?
Click to expand...
Click to collapse
You can do it on your own!
If im right you can do like this!
Flashing firmware, kernel and SuperSU from my method! Then start flashtool and flash the firmware again but on "exlcude menu point" check all except kernel!!!! This will receive you a stock 199 firmware with root but without recovery, cause you flashed back the stock 199 kernel from firmware....
Now when you have root you can use this instruction to get PhilZ touck kernel: http://forum.xda-developers.com/showthread.php?t=2657190
:good: :laugh:
Midleo said:
You can do it on your own!
If im right you can do like this!
Flashing firmware, kernel and SuperSU from my method! Then start flashtool and flash the firmware again but on "exlcude menu point" check all except kernel!!!! This will receive you a stock 199 firmware with root but without recovery, cause you flashed back the stock 199 kernel from firmware....
Now when you have root you can use this instruction to get PhilZ touck kernel: http://forum.xda-developers.com/showthread.php?t=2657190
:good: :laugh:
Click to expand...
Click to collapse
thanks for the info, but do i need UL first ? i think in your guide no need UL, is it right ?
devilmaycry2020 said:
thanks for the info, but do i need UL first ? i think in your guide no need UL, is it right ?
Click to expand...
Click to collapse
Iin case PhilZ Unlocked bootloader is not necessary! It possible on LB!
Midleo said:
Iin case PhilZ Unlocked bootloader is not necessary! It possible on LB!
Click to expand...
Click to collapse
yeah, i knew PhilZ CWM can do on LB. but in the step flash CWM kernel built-in i must unlock BL first ?
devilmaycry2020 said:
yeah, i knew PhilZ CWM can do on LB. but in the step flash CWM kernel built-in i must unlock BL first ?
Click to expand...
Click to collapse
ahhh.....yeah...you right!!! :good: Yes you need! so dont try it on LB, otherwise youll get problem
Midleo said:
ahhh.....yeah...you right!!! :good: Yes you need! so dont try it on LB, otherwise youll get problem
Click to expand...
Click to collapse
here is my step to make 4.3 root, cwm
1. backup TA then unlock UL in 4.1.2
2. flash stock 199 (do not reboot)
3. flash CWM kernel (do not reboot)
4. flash supersu (do not reboot)
5. flash stock kernel (do not reboot) , you lost CWM
6. flash philZ CWM touch
7. relock BL
8. done.
Right ?
devilmaycry2020 said:
here is my step to make 4.3 root, cwm
1. backup TA then unlock UL in 4.1.2
2. flash stock 199 (do not reboot)
3. flash CWM kernel (do not reboot)
4. flash supersu (do not reboot)
5. flash stock kernel (do not reboot) , you lost CWM
6. flash philZ CWM touch
7. relock BL
8. done.
Right ?
Click to expand...
Click to collapse
You right till step 5!
On step 5 after you flashing stock kernel it doesnt matter you reboot or not...you lost recovery!!! no more recovery...
6. You need to boot up (set up) your phone! then install flashgordon app, then on flashgordon app select PhilZ.zip and flah it
7. About step 7 i nver tried it....so im not sure 100% but i think it should work!!!
devilmaycry2020 said:
here is my step to make 4.3 root, cwm
1. backup TA then unlock UL in 4.1.2
2. flash stock 199 (do not reboot)
3. flash CWM kernel (do not reboot)
4. flash supersu (do not reboot)
5. flash stock kernel (do not reboot) , you lost CWM
6. flash philZ CWM touch
7. relock BL
8. done.
Right ?
Click to expand...
Click to collapse
I don't know why you keep it so complicated. Myself and others have already posted plenty of times this exact scenario.
In your case, you're almost right, except you need to flash Philz recovery and then flash stock kernel. If you do it this way, you don't need to install Flashgordon. I'll put it simple:
1. backup TA then unlock BL in 4.1.2
2. flash stock 199 / ZIP or FTF
3. flash CWM kernel / ZIP or Sin/Elf Kernel
4. Reboot into recovery, and flash Philz Recovery
5. Go into fastboot, flash stock kernel, you have not lost recovery
6. Boot into recovery, flash SuperSu (if you want).
7. done.
Midleo said:
7. About step 7 i nver tried it....so im not sure 100% but i think it should work!!!
Click to expand...
Click to collapse
About this, I don't know either, I haven't tried relocking BL on 4.3 with root and recovery, but I don't see why it wouldn't work either.
Antiga Prime said:
I don't know why you keep it so complicated. Myself and others have already posted plenty of times this exact scenario.
In your case, you're almost right, except you need to flash Philz recovery and then flash stock kernel. If you do it this way, you don't need to install Flashgordon. I'll put it simple:
1. backup TA then unlock BL in 4.1.2
2. flash stock 199 / ZIP or FTF
3. flash CWM kernel / ZIP or Sin/Elf Kernel
4. Reboot into recovery, and flash Philz Recovery
5. Go into fastboot, flash stock kernel, you have not lost recovery
6. Boot into recovery, flash SuperSu (if you want).
7. done.
About this, I don't know either, I haven't tried relocking BL on 4.3 with root and recovery, but I don't see why it wouldn't work either.
Click to expand...
Click to collapse
Many thanks. Good job,
in step 4 ; i flash deodexed rom first then philz touch, because after step 6 if i want to deodex rom , i flash rom zip then root gone.
I did it, locked BL + rooted + PhilZ touch, TA restored OK
devilmaycry2020 said:
Many thanks. Good job,
in step 4 ; i flash deodexed rom first then philz touch, because after step 6 if i want to deodex rom , i flash rom zip then root gone.
I did it, locked BL + rooted + PhilZ touch, TA restored OK
Click to expand...
Click to collapse
Great. If you had planned to flash a ROM zip, you could have done that straight from 4.1.2 recovery and not flash 4.3 FTF, but whatever, as long as it works for you.
Antiga Prime said:
Great. If you had planned to flash a ROM zip, you could have done that straight from 4.1.2 recovery and not flash 4.3 FTF, but whatever, as long as it works for you.
Click to expand...
Click to collapse
Big problem mate. i've got auto reboot while copy or delete file in system. please help. cause i lock BL to gain BE working.
Hey guys, I'm new here..idk if this is the right category but here we go: I tried to upgrade the software from the phone and after reboot just went in recovery mode and I found out I have no android. After that I copied stable cm 10.1 gapps on my sd card then I tried to install the zips, everything seemed ok..I restarted the phone and it went straight to recovery mode. I did the same thing with the android 4.4.2 MoKee and happend the same thing. What should i do?
kanaal said:
Hey guys, I'm new here..idk if this is the right category but here we go: I tried to upgrade the software from the phone and after reboot just went in recovery mode and I found out I have no android. After that I copied stable cm 10.1 gapps on my sd card then I tried to install the zips, everything seemed ok..I restarted the phone and it went straight to recovery mode. I did the same thing with the android 4.4.2 MoKee and happend the same thing. What should i do?
Click to expand...
Click to collapse
Try installing Symbian , just kidding.
Did you unlock the bootloader of the phone while you were on stock rom?
fuathan said:
yeah guys I ask anything ?
Click to expand...
Click to collapse
Apparently you do.
Coolneng said:
Try installing Symbian , just kidding.
Did you unlock the bootloader of the phone while you were on stock rom?
Click to expand...
Click to collapse
Yes, I unlocked the bootloader
kanaal said:
Hey guys, I'm new here..idk if this is the right category but here we go: I tried to upgrade the software from the phone and after reboot just went in recovery mode and I found out I have no android. After that I copied stable cm 10.1 gapps on my sd card then I tried to install the zips, everything seemed ok..I restarted the phone and it went straight to recovery mode. I did the same thing with the android 4.4.2 MoKee and happend the same thing. What should i do?
Click to expand...
Click to collapse
Can you little better describe how did you upgrade the software. Recovery, rom etc. Did you start at stock ICS or JB?
LGaljo said:
Can you little better describe how did you upgrade the software. Recovery, rom etc. Did you start at stock ICS or JB?
Click to expand...
Click to collapse
I had stock JB and I had this program in menu "Software update" and it was an 19-25 mb update..I downloaded and I installed the update then the phone rebooted and it went in cwm recovery. If I install a custom rom everything seems ok, after reboot it enter straight to recovery and I don't know why.
kanaal said:
I had stock JB and I had this program in menu "Software update" and it was an 19-25 mb update..I downloaded and I installed the update then the phone rebooted and it went in cwm recovery. If I install a custom rom everything seems ok, after reboot it enter straight to recovery and I don't know why.
Click to expand...
Click to collapse
If you set up working stock JB follow this:
*prepare custom ROM, kernel and Gapps then copy to SD
*if you want CWM download this: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.5-p880.img, then copy *.img file to a folder where adb is installed and rename it to recovery.img
*boot to fastboot mode (adb reboot oem-unlock)
*install recovery in fastboot mode (fastboot flash recovery recovery.img)
*power off, then boot to recovery
*flash ROM, Gapps and kernel
LGaljo said:
If you set up working stock JB follow this:
*prepare custom ROM, kernel and Gapps then copy to SD
*if you want CWM download this: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.5-p880.img, then copy *.img file to a folder where adb is installed and rename it to recovery.img
*boot to fastboot mode (adb reboot oem-unlock)
*install recovery in fastboot mode (fastboot flash recovery recovery.img)
*power off, then boot to recovery
*flash ROM, Gapps and kernel
Click to expand...
Click to collapse
Ok, I will try this but can you suggest me a good custom ROM and kernel? I never installed a kernel before and i don't know what to look for
kanaal said:
Ok, I will try this but can you suggest me a good custom ROM and kernel? I never installed a kernel before and i don't know what to look for
Click to expand...
Click to collapse
You don't really need different kernel, for first start I suggest you official CM11 nightly
Hit thanks if it helps
LGaljo said:
You don't really need different kernel, for first start I suggest you official CM11 nightly
Hit thanks if it helps
Click to expand...
Click to collapse
While I try to install the cwm I get this error http://i.imgur.com/d9nPSeI.jpg I installed with my cwm 6.0.4.4 the CM11 gapps and this kernel http://forum.xda-developers.com/showthread.php?t=2241474 all of these installed with no problems, after that i reboot and the cwm recovery appears w/o pressing the volume button.
kanaal said:
While I try to install the cwm I get this error
{
"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"
}
I installed with my cwm 6.0.4.4 the CM11 gapps and this kernel http://forum.xda-developers.com/showthread.php?t=2241474 all of these installed with no problems, after that i reboot and the cwm recovery appears w/o pressing the volume button.
Click to expand...
Click to collapse
I recommend you not to use this kernel, it is deprecated. Try without flashing different kernel first. Which CWM did you download? From link I gave?
EDIT: Have you done formats of /system, /data, /cache ?
You bugged out your device. OTA doesnt work properly with custom recovery installed. Reflash kdz to fix the issue,but try grabbing everything you need from via adb from recovery first as you may have to do hard reset from stock recovery which will format your internal sd (in case you dont know how to flash custom recovery via fastboot)
LGaljo said:
I recommend you not to use this kernel, it is deprecated. Try without flashing different kernel first. Which CWM did you download? From link I gave?
EDIT: Have you done formats of /system, /data, /cache ?
Click to expand...
Click to collapse
Yes, from the link you gave me and I did formated the /system, /data and /cache
Flying_Bear said:
You bugged out your device. OTA doesnt work properly with custom recovery installed. Reflash kdz to fix the issue,but try grabbing everything you need from via adb from recovery first as you may have to do hard reset from stock recovery which will format your internal sd (in case you dont know how to flash custom recovery via fastboot)
Click to expand...
Click to collapse
What kdz is? Sorry, but i'm new in this thing.
kanaal said:
Yes, from the link you gave me and I did formated the /system, /data and /cache
What kdz is? Sorry, but i'm new in this thing.
Click to expand...
Click to collapse
You can reflash or put phone to stock state with using lgmobile support tool. Just put phone in S/W mode (volume down and USB cable plug in) and in dropdown menu select update recovery
LGaljo said:
You can reflash or put phone to stock state with using lgmobile support tool. Just put phone in S/W mode (volume down and USB cable plug in) and in dropdown menu select update recovery
Click to expand...
Click to collapse
Ok, so i was following this tutorial http://forum.xda-developers.com/showthread.php?t=2069723 and on LG Mobile Support when I press install usb driver I can't find LGP880, why? maybe something is missing from pc like drivers or something like that?
EDIT: I did it, my phone works fine thank you very much! one more thing..can i install CM11 w/o problems now? i mean while i'm on 4.1.2
kanaal said:
Ok, so i was following this tutorial http://forum.xda-developers.com/showthread.php?t=2069723 and on LG Mobile Support when I press install usb driver I can't find LGP880, why? maybe something is missing from pc like drivers or something like that?
EDIT: I did it, my phone works fine thank you very much! one more thing..can i install CM11 w/o problems now? i mean while i'm on 4.1.2
Click to expand...
Click to collapse
yes, you can. the bug you encountered only happens when you use OTA with modified stock firmware.
good luck :good:
Flying_Bear said:
yes, you can. the bug you encountered only happens when you use OTA with modified stock firmware.
good luck :good:
Click to expand...
Click to collapse
Ok, I got it. Thank you! One more thing, I swear it! When I try to root my phone (I follow this guide http://forum.xda-developers.com/showthread.php?t=1818502 ), the SystemBackupTest doesn't work, I googled the problem and I found nothing.
kanaal said:
Ok, I got it. Thank you! One more thing, I swear it! When I try to root my phone (I follow this guide http://forum.xda-developers.com/showthread.php?t=1818502 ), the SystemBackupTest doesn't work, I googled the problem and I found nothing.
Click to expand...
Click to collapse
you are using deprecated method. that's method for ics. search for a way to root jellybean 20a.
Hi all,
i would like to ask how to install a custom rom onto my samsung galaxy s3 mini. I know there are many guides but i am a complete starter, i just made a switch from apple and i have no idea what they mean, even the clearest one.. I just want to update these devices to lollipop since they are still on 4.1.2 jelly bean. Omnirom or cyanogen or others, i dont mind, i just want an updated device. Step by step instructions on everything would be perfect thank you!! By the way, i dont have windows, only mac.
this would help me a lot in the future.
thanks
Leonardo Yip said:
Hi all,
i would like to ask how to install a custom rom onto my samsung galaxy s3 mini. I know there are many guides but i am a complete starter, i just made a switch from apple and i have no idea what they mean, even the clearest one.. I just want to update these devices to lollipop since they are still on 4.1.2 jelly bean. Omnirom or cyanogen or others, i dont mind, i just want an updated device. Step by step instructions on everything would be perfect thank you!! By the way, i dont have windows, only mac.
this would help me a lot in the future.
thanks
Click to expand...
Click to collapse
Hi, at first I suggest to you to choose between two roms: The Omnirom and the CM. Your choice depend only about what you want from your phone. The Omni one is pretty nice and it looks like more a stock rom. The CM is very customisable in a lot of stuff. If you are not very expert, I suggest to you the CM, because it's more easy to install. But decide at first what you need from your phone!
Stefano Cappelletti said:
Hi, at first I suggest to you to choose between two roms: The Omnirom and the CM. Your choice depend only about what you want from your phone. The Omni one is pretty nice and it looks like more a stock rom. The CM is very customisable in a lot of stuff. If you are not very expert, I suggest to you the CM, because it's more easy to install. But decide at first what you need from your phone!
Click to expand...
Click to collapse
I’ll choose Cyanogen then. Thanks for the reply.
What you need to flash is:
- the original firmware
- Odin
- USB drivers
- CM (Odin version)
- gApps (Google Apps)
You can find the original firmware on sammobile.com, and you can find other sottware on novafusion.pl in the section . When you have everything we can start!
Stefano Cappelletti said:
What you need to flash is:
- the original firmware
- Odin
- USB drivers
- CM (Odin version)
- gApps (Google Apps)
You can find the original firmware on sammobile.com, and you can find other sottware on novafusion.pl in the section . When you have everything we can start!
Click to expand...
Click to collapse
Is it ok if i get odin for mac? Because i'm a mac user. I'm not sure if this is official
techbeasts . com/2015/04/13/download-odin-jdoin3-mac/
I added two spaces between on the left and write of the dot because I'm not allowed to post links, idk why. Just remove the other two spaces thanks.
Two more things, I can't find the USB drivers or original firmware on novafusion. And please be patient as it will take a while to download these things. My internet has a whopping 200 kilobytes per second, yeah it's slower than a snail...
It seems that Odin for Mac doesn't exist, the software that you can find is only similar but not the original Odin. Maybe they are good software as well but I don't want to risk to brick the phone for a not fully compatible software... Don't worry: we do everything also without Odin, is just a little bit longer but it works.
At first reboot your phone in recovery mode (menu button, volume up, power botton than wait) and do the wipe of cache and than reboot it and wait.
When the Phone is ready go here and download the SuperSu (to root the device) https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
and copy the zip file in your phone, than, reboot again the device in recovery mode and select "instal ZIP" (or something like that, I don't remember exactly honesty and choose the zip that you downloaded. Reboot the phone and now if everything worked you should find an app called "SuperSU" in your drawer. After you got the root access, we can go to the next step
Oh i actually already rooted it with KingRoot, is it bad?
Leonardo Yip said:
Oh i actually already rooted it with KingRoot, is it bad?
Click to expand...
Click to collapse
KingoRoot is also fine.
Regarding "Odin on Mac":
jOdin uses "Heimdall" which works fine with S3 Mini - so unless they messed up the UI completely (giving wrong commands to Heimdall) the tool works fine, too.
KingRoot is should be fine at the same. You just need the root access to flash the device from the recovery. I sugget to you to install the TWRP recvery if you don't have it yet. You can download it and flash it from the recovery (you have root access now) or you can download an app on Google Play store like rom manager or TWRP manager and install the recovery from the app. Then we can go to the next step
KaffeeKiffer thanks but i'll stick with Stefano's method . Ok i got TWRP, but i still can't find the USB drivers or the original firmware (it's not on SamMobile). And for cyanogen mod 12.1, do i now get the normal version, like not the odin one?
Yes, you have to download not the Odin version but the other one "recovery version". At the same you have to download and flash the TWRP recovery first (always "recovery version" of the download). It should be the same also if you flash the CM with other recovery but I read online that flashing CM via recovery, by the TWRP recovery is better.
1) Download and flash TWRP recovery
2) Wipe cache and clean everything
3) Download and flash
Now the next step will be installing gApps
MAJOR PROBLEM!!! PLEASE HELP NOW. It failed to install the zip, and when i try to reboot it, it goes automatically to twrp.. please see attached picture, please please help. it says E: Error executing updater binary in zip
{
"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"
}
http://postimg.org/image/j4invhd0v/
Leonardo Yip said:
MAJOR PROBLEM!!! PLEASE HELP NOW. It failed to install the zip, and when i try to reboot it, it goes automatically to twrp.. please see attached picture, please please help. it says E: Error executing updater binary in zip
http://postimg.org/image/j4invhd0v/
Click to expand...
Click to collapse
sei italiano?
KaffeeKiffer said:
KingoRoot is also fine.
Regarding "Odin on Mac":
jOdin uses "Heimdall" which works fine with S3 Mini - so unless they messed up the UI completely (giving wrong commands to Heimdall) the tool works fine, too.
Click to expand...
Click to collapse
I'll jump in long enough to point out that Heimdall/Odin is not functional under current Mac environments. SInce Mobile Odin is effectively obsolete for current devices/ROMs, Mac users often rely on fastboot and similar tools instead for what can't be accomplished via a good custom recovery such as TWRP.
Leonardo Yip said:
Hi all,
i would like to ask how to install a custom rom onto my samsung galaxy s3 mini. I know there are many guides but i am a complete starter, i just made a switch from apple and i have no idea what they mean, even the clearest one.. I just want to update these devices to lollipop since they are still on 4.1.2 jelly bean. Omnirom or cyanogen or others, i dont mind, i just want an updated device. Step by step instructions on everything would be perfect thank you!! By the way, i dont have windows, only mac.
this would help me a lot in the future.
thanks
Click to expand...
Click to collapse
install odin on windows pc: http://depositfiles.com/files/m2n77b1vc
install samsung drivers on windows pc: http://developer.samsung.com/technical-doc/view.do?v=T000000117#none
get cyanogenmod 12.1: http://novafusion.pl/
get the odin version
when mobile powered off, hold volume down, home and power button. You get the downloadmode option on your screen, let go all buttons and press volume up button.
Now connect the phone to your pc with the usb cable and let odin find it.
Load the tar file in the downloaded zip file as pda and flash it.
If you want clockwork mod, install this as tar, also in pda flash option: https://www.androidfilehost.com/?fid=95887005526789241
If your samsung doesn't work but you can still get into download mode, view next page: http://forum.xda-developers.com/showthread.php?t=2122548
and install a fail safe firmware according to your type of phone.
Leonardo Yip said:
MAJOR PROBLEM!!! PLEASE HELP NOW. It failed to install the zip, and when i try to reboot it, it goes automatically to twrp.. please see attached picture, please please help. it says E: Error executing updater binary in zip
http://postimg.org/image/j4invhd0v/
Click to expand...
Click to collapse
I don't have 12.1 running, but isn't TRWP 2.6.3 a bit low? I hope somebody with experience in that regard can help you.
But on Novafusion's site (which I assume you're flashing), the current version is 2.8.
Androidandy's version also worked great for me.
Mike B. said:
I'll jump in long enough to point out that Heimdall/Odin is not functional under current Mac environments. SInce Mobile Odin is effectively obsolete for current devices/ROMs, Mac users often rely on fastboot and similar tools instead for what can't be accomplished via a good custom recovery such as TWRP.
Click to expand...
Click to collapse
Thanks for the info - I tested it some time ago and have a windows PC, so no need to run it ever after.
I was just relying on my past experience.
What i don't understand is why the flashing went wrong, I did everything right, at least I think. Wipe everything and flash the rom, why didn't it work?
Hi friends i was searching for multi rom mod for our zuk z1 for past few days.....
Successfully i find this... And felt a bit happy about it.
Download link:- https://www.androidfilehost.com/?fid=24533103863143606
Please help me friends , how to flash it....
Thanks.??
This version wont work. Yes it will boot into the multirom recovery but you wont be able to flash any roms. Sadly BitO BSessiOn quit the work for the Zuk Z1 and sold his device. And i have no time to di this and i don't know how all the stuff for this works.
Thanks
OrdenKrieger said:
This version wont work. Yes it will boot into the multirom recovery but you wont be able to flash any roms. Sadly BitO BSessiOn quit the work for the Zuk Z1 and sold his device. And i have no time to di this and i don't know how all the stuff for this works.
Click to expand...
Click to collapse
Thanks a lot for responding......
I think this will work only if the kernal has kexec patch....
Can't it be enabled by @acuicultor
jai krishna said:
Thanks a lot for responding......
I think this will work only if the kernal has kexec patch....
Can't it be enabled by @acuicultor
Click to expand...
Click to collapse
I know but the multirom recovery itself isnt working. That with the kernel is another thing.
OrdenKrieger said:
I know but the multirom recovery itself isnt working. That with the kernel is another thing.
Click to expand...
Click to collapse
Ohh kk
Thanks
TWRP + MultriROM NO-KEXEC version (blind build, testing)
This is a "blind" build... I've been working for a days in a version of TWRP-MROM for other devices and a friend has acquired a Z1 so I've decide to build... so... don't expect to work... (I can't test it, sorry), but if somebody is interested in retake and develop this, I can share current code status and try to help, if I can (and I know).
TWRP-MROM:
https://www.androidfilehost.com/?fid=385035244224402398
MultiROM:
https://www.androidfilehost.com/?fid=529152257862685511
If TWRP works... try to select no-kexec workaround in Multirom Settings after flashing any rom as secondary (as sugestion initially try a cm-13 like rom) and inject bootsector.
If it still works... you should get MultiROM and select internal or secondary... cross fingers....
Thanks bro
---------- Post added at 03:32 PM ---------- Previous post was at 03:29 PM ----------
Ill test it can u continue development of multi rom??????
Firstly, I'm sorry I'm a complete noob here when it comes to MultiRom stuff but still thought of giving it a shot.
I flashed the modified recovery via Rashr... Successfully booted into it.... The recovery appeared to be working just fine except for one thing....
I think it couldn't mount internal storage or any kind of storage since mounting options were absent and on clicking install it showed various partitions except sdcard.
Also on selecting Select Storage, it shows no partitions.
Please let me know if I did something wrong or if I should do something else.
Thanks!
I think maybe Select Storage doesn't work because no SD Card and no USB OTG... Only internal storage (/system and /data partitions... Right? )
Can you make a full backup of all partitions..? How many do appear...?
BitOBSessiOn said:
Can you make a full backup of all partitions..? How many do appear...?
Click to expand...
Click to collapse
Thanks for your response, will try right away and report back!
Here are my findings...
No partitions available to select while creating a backup
Even while wiping only Dalvik Cache shows up
Please check the pictures attached
TWRP + MultriROM NO-KEXEC (test build 002)
New blind builds:
TWRP-MROM:
https://www.androidfilehost.com/?fid=529152257862685732
MultiROM
https://www.androidfilehost.com/?fid=385035244224402625
BitOBSessiOn said:
New blind builds
Click to expand...
Click to collapse
Thank you so much the new TWRP appears to be working just fine. I'll attach a few screenshots. (Kindly ignore the theme :silly: )
Can you please give me a few directions what my next steps should be?
I'm on NucleaRom Nougat 7.1
Flashed your TWRP
Should I flash the zip file now?
And what should be done after that?
Would have experimented but wanted to do it the right way.
Thank you so much for your awesome work!
Please, flash Multirom.zip, inject boot sector (to be able to boot multirom) and reboot. You should see, at least, multirom menu to select rom (by default Internal), and boot internal.
If this works, go back to twrp, select multirom options (upper right icon) and try to flash a secondary room. In multirom settings activate no-kexec work around.
Reboot and you should be able to select the new secondary in multirom menu. Select and try to boot on it...
Thx and good luck...
Thank you so much for the directions.
I flashed the MultiROM zip and rebooted but no MultiROM option appears.
As I stated above, I'm on NucleaRom Nougat and after bootlogo followed by Radioactive Reborn Kernel logo, I get black screen for about 6-7 seconds and after that my NucleaRom boots up normally.
I even tried booting into TWRP normally from the ROM but I don't see any MultiROM options there. (Shouldn't be an issue with theme since I switched back to stock theme to confirm)
Although I think in the previous TWRP, this option was present.
But I think it's an achievement in itself getting so far since I wasn't expecting the ROM to boot up after flashing the zip. Lol
But again, thanks a ton.
If you'd like me to experiment with some other ROM, I'll give it a try.
sahu.prashant said:
Thank you so much for the directions.
I flashed the MultiROM zip and rebooted but no MultiROM option appears.
As I stated above, I'm on NucleaRom Nougat and after bootlogo followed by Radioactive Reborn Kernel logo, I get black screen for about 6-7 seconds and after that my NucleaRom boots up normally.
I even tried booting into TWRP normally from the ROM but I don't see any MultiROM options there. (Shouldn't be an issue with theme since I switched back to stock theme to confirm)
Although I think in the previous TWRP, this option was present.
But I think it's an achievement in itself getting so far since I wasn't expecting the ROM to boot up after flashing the zip. Lol
But again, thanks a ton.
If you'd like me to experiment with some other ROM, I'll give it a try.
Click to expand...
Click to collapse
Have you selected option to "inject bootsector" after installing multirom.zip ...?
BitOBSessiOn said:
Have you selected option to "inject bootsector" after installing multirom.zip ...?
Click to expand...
Click to collapse
Looks like I missed that part but I think didn't see that option anywhere. But please allow me to take a look again.
---------- Post added at 04:04 PM ---------- Previous post was at 03:55 PM ----------
Now this is hilarious....
Repeatedly flashed the latest MultiROM TWRP and MultiROM option appeared again! (Could be an issue with Rashr)
However I flashed the zip again and inject MultiROM was checked by default so I let it be.
Then I went into the MultiROM option and injected bootsector and rebooted but no MultiROM options unfortunately.
Sorry for the confusion but this behavior of disappearance and appearance of MultiROM options in TWRP was rather unexpected.
sahu.prashant said:
Looks like I missed that part but I think didn't see that option anywhere. But please allow me to take a look again.
---------- Post added at 04:04 PM ---------- Previous post was at 03:55 PM ----------
Now this is hilarious....
Repeatedly flashed the latest MultiROM TWRP and MultiROM option appeared again! (Could be an issue with Rashr)
However I flashed the zip again and inject MultiROM was checked by default so I let it be.
Then I went into the MultiROM option and injected bootsector and rebooted but no MultiROM options unfortunately.
Sorry for the confusion but this behavior of disappearance and appearance of MultiROM options in TWRP was rather unexpected.
Click to expand...
Click to collapse
Ummmhhh.. at this point... if no MultiROM menu I'm afraid it's going to be so hard to fix... Sorry.
BitOBSessiOn said:
Ummmhhh.. at this point... if no MultiROM menu I'm afraid it's going to be so hard to fix... Sorry.
Click to expand...
Click to collapse
No worries, I'm just very thankful to you for getting us this far.
TWRP + MultriROM NO-KEXEC (Test build 005.... getting closer )
Well, Thx to @acuicultor who has tested some newer test builds, we've determined that MultiROM seems to WORK, but there is a graphical glitch in MultiROM (black screen) which should be (maybe) fixed in this build... (he can't test it atm...):
MultiROM:
https://www.androidfilehost.com/?fid=385035244224402835
TWRP-MROM:
https://www.androidfilehost.com/?fid=529152257862685912
If I'm right, with this build you should be able to flash a secondary ROM, set no-kexec option in settings for MultiROM from TWRP, inject boot and see MultiROM menu to select secondary.
If you DON'T see MultiROM menu, a workaround is select secondary as default rom in TWRP settings for MultiROM and it should boot... (don't forget to select no-kexec option )
Good luck.
PS: Still a bug that prevents it from flashing IMG files, like recovery images, from TWRP...