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...
Related
Hey, I bring to you the first Clockworkmod Recovery or commonly known as CWM for your N5100 and N5110. Giving your device the ability to flash your favourite custom ROMs, Kernels, Mods. *Now known as Advanced CWM or aCWM. Thankyou to 'xperiacle' and 'GSLEON3' for giving me the stock recoveries and kernels for N5100/10, so I could start off with my work.
Works perfectly now. OP will only be updated with stable releases, everything else will be floating around the thread.
I have provided the stock recovery if you encounter any issues, you can always flash back.
Featues:
Most things you would expect from stock CWM
EFS backup / restore
Removed option to: report error / show log / testkeys
More to come...
Downloads:
Use this if you are having problems with your SDCard. (Mount / Backup / Restore)
N5100 / N5110
Stable Release #1: ODIN | ZIP
Stock Recovery: http://d-h.st/tHx
N5120
Stable Release #1: ODIN
Stock Recovery: http://d-h.st/51H
Changelog:
Code:
[I][U]Stable Release #1[/U][/I]
Added reboot menu (rom, download, recovery)
Advanced CWM = aCWM
Code:
[I][U]Experimental #6[/U][/I]
Working EFS backup / restore under 'advanced' tab
Removed keytest / report error / show log options
Custom recovery, no more to be called 'stock' CWM, more device specific features to be added
N5120 support
Fix permissions now directed to /sdcard/.android_secure
Cleaned up some code for flashing zips
[I][U]Experimental #5[/U][/I]
[COLOR="Red"]REMOVED DUE TO ISSUES[/COLOR]
Touch recovery (reimplemented)
Universal for 5100 / 5110
Fixed up some mount lengths
Fixed up init.rc
[I][U]Experimental #4[/U][/I]
Display issues fixed
[I][U]Experimental #3[/U][/I]
Built again with fresh tree - n5110
(info: skipped for n5100)
[I][U]Experimental #2[/U][/I]
Touch Input excluded (temp)
kernel built from source with dancing cwm patch
[I][U]Experimental #1[/U][/I]
Public release
emwno said:
Hey, I bring to you, Clockworkmod Recovery or commonly known as CWM for your n5100. Giving your device the ability to flash your favourite custom ROMs, Kernels, Mods in the future. Thankyou to 'xperiacle' for giving me the stock recovery and boot.img. Flash with Odin
This has not been tested by me and is still experimental. I hold no responsibility for any
problems caused. YOU! Are trying this at your own risk. Don't blame me that I wasted your $$$.
Put a scare in you didn't I?
I have provided the stock recovery if you encounter any issues, you can always flash back.
Downloads:
CWM Recovery: http://d-h.st/rDv
Stock Recovery: http://d-h.st/tHx
Changelog:
Code:
[I][U]Release #1[/U][/I]
Public release
Click to expand...
Click to collapse
Thanks now we need one for the N5110.
rfb813 said:
Thanks now we need one for the N5110.
Click to expand...
Click to collapse
Just need to check if this works properly. If yes, then n5110 is up next
emwno said:
Just need to check if this works properly. If yes, then n5110 is up next
Click to expand...
Click to collapse
Thanks!
Thanks man, that was fast work
Sent from my GT-N5110 using Tapatalk HD
Southrice said:
Thanks man, that was fast work
Sent from my GT-N5110 using Tapatalk HD
Click to expand...
Click to collapse
Nothing to be credited for, until the device boots to CWM
How do you flash this custom recovery with ODIN?, what version?, thanks
I flash the file 2 times and it said pass but when reboot to recovery is stock so I don't know what went wrong
Speedy Gonzalez said:
I flash the file 2 times and it said pass but when reboot to recovery is stock so I don't know what went wrong
Click to expand...
Click to collapse
How did you flash, Odin?
brosenz said:
How did you flash, Odin?
Click to expand...
Click to collapse
I added the zip to the pda area and flash Odin v3.07
I installed the image with ADB.
put the recovery image on the sdcard mount or ext sdcard mount
ADB to the note 8.0
su to root
go to your image directory
dd if=xxx.img of=/dev/block/mmcblk0p6
switch back to the note and reboot directly to recovery (i used goomanager)
it does boot the first time - but it is jittery and in landscape mode.
after the first system boot- the device wipes it and goes back to stock recovery.
I have seen this with other stock android devices- sometimes there
is a script that gets triggered on boot to remove any custom recoveries.
I did clear the recovery check from CWM - but it was hard to see because of the
landscape mode and the screen jumping around.
It looks like the full backup is working- now I wonder what ROM will be close enough
to the 8.0 to try flashing.
Speedy Gonzalez said:
I added the zip to the pda area and flash Odin v3.07
Click to expand...
Click to collapse
Any idea why it didn't flash with Odin?
@xbill9
Code:
adb pull /tmp/recovery.log
for fixes
Speedy Gonzalez said:
I flash the file 2 times and it said pass but when reboot to recovery is stock so I don't know what went wrong
Click to expand...
Click to collapse
Found this Q&A in the Note 10.1 rooting guide in RootGalaxyNote.com:
Q: I don’t see ClockworkMod Recovery when I enter recovery, I see stock Android recovery.
A: With newer software updates, you may be encountering this error because it will overwrite ClockworkMod Recovery upon reboot. To get around this, simply boot into ClockworkMod Recovery right after flashing in ODIN. You can set auto-reboot off in ODIN then when done, just hold down Power and Volume Down straight to bootloader menu.
This may have been the problem.
To get it to stop resetting to stock recovery every time you reboot, under /system, there is a file named "recovery-from-boot.p". Rename it to .bak or whatever. That file is typically the culprit for custom recoveries not 'sticking'.
Also, we don't have a factory image yet, do we? I'm hesitant to mess too much with this stuff until we have a way to Odin ourselves out of a softbrick.
---------- Post added at 11:45 PM ---------- Previous post was at 11:42 PM ----------
Also, to the OP, thanks for doing this. I'm pretty familiar with adb if you'd like to do TWRP. Would love to have it instead of CWM!
rfb813 said:
Q: I don’t see ClockworkMod Recovery when I enter recovery, I see stock Android recovery.
A: With newer software updates, you may be encountering this error because it will overwrite ClockworkMod Recovery upon reboot. To get around this, simply boot into ClockworkMod Recovery right after flashing in ODIN. You can set auto-reboot off in ODIN then when done, just hold down Power and Volume Down straight to bootloader menu.
Click to expand...
Click to collapse
Those having issues, try that ^^^
jntdroid said:
To get it to stop resetting to stock recovery every time you reboot, under /system, there is a file named "recovery-from-boot.p". Rename it to .bak or whatever. That file is typically the culprit for custom recoveries not 'sticking'.
Also, to the OP, thanks for doing this. I'm pretty familiar with adb if you'd like to do TWRP. Would love to have it instead of CWM!
Click to expand...
Click to collapse
Yeah, But i'd like to keep, just incase something goes insanely wrong. The stock recovery.img is provided, you can always flash back it something goes wrong. And i am readying up TWRP, may need you to pull some logs if it doesnt boot
jntdroid said:
To get it to stop resetting to stock recovery every time you reboot, under /system, there is a file named "recovery-from-boot.p". Rename it to .bak or whatever. That file is typically the culprit for custom recoveries not 'sticking'.
Also, we don't have a factory image yet, do we? I'm hesitant to mess too much with this stuff until we have a way to Odin ourselves out of a softbrick.
---------- Post added at 11:45 PM ---------- Previous post was at 11:42 PM ----------
Also, to the OP, thanks for doing this. I'm pretty familiar with adb if you'd like to do TWRP. Would love to have it instead of CWM!
Click to expand...
Click to collapse
http://samsung-updates.com/device/?id=GT-N5100
http://samsung-updates.com/device/?id=GT-N5110
I will be releasing a full Note 8.0 Toolkit today or tomorrow with support to rename the stock recovery restore files so that custom recovery isnt overwritten after flashing. If anyone wants to help test please email me at [email protected]
Mark.
Attached is a tar of recovery.log pulled with ADB while booted to CWM.
The display goes to landscape on boot - and the fonts seem extra large.
When the vol up/down navigates the screen jumps and you can't see the
highlighted option.
It is usable with trial and error if you know the order of the CWM menus and
use the vol up/down and power to navigate.
emwno said:
@xbill9
Code:
adb pull /tmp/recovery.log
for fixes
Click to expand...
Click to collapse
Only thing I can judge by that are the missing mount types for the recovery.fstab. Ill fix that now. But someone, try keeping the device physically portrait and see if cwm works properly then, if not then physically landscape.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
P.S try using touch input, its a touch recovery, or so I built it
^thats why fonts are large
^thats why there are no indicators
I tried changing orientation before boot - it always goes to landscape.
I attached 2 images - one is the display after the first CWM boot.
The second is after pressing Vol Up to navigate to the 2nd menu option.
I have seen jumpy CWM presentation like this on some smaller screens like the
Sony Xperia 2011/2012 phones.
emwno said:
Only thing I can judge by that are the missing mount types for the recovery.fstab. Ill fix that now. But someone, try keeping the device physically portrait and see if cwm works properly then, if not then physically landscape.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
P.S try using touch input, its a touch recovery, or so I built it
^thats why fonts are large
^thats why there are no indicators
Click to expand...
Click to collapse
These are pure AOSP builds by dhacker29, all credit goes to him.
Please note these are hot off the press and may have bugs. Users have reported trouble with flashing, etc, but when you manage to get it to run the ROM runs smoothly.
Still, AOSP is bare-bones and will need device specific modifications that custom ROMs provide. Consider it a stable-ish alpha build, but not a dependable daily driver.
Please ensure you do your backups. Nobody is responsible if your phone bursts into flames.
All files you need are here:
Prerequisites: KitKat requires TWRP 2.6.3.0 which can be found here
xt925 ROM
xt926 ROM
GAPPS
By default AOSP has no root access, however Chainfire's root will work just fine. Just flash and install SuperSU.
Have fun with KitKat!
Changelog
20131108 Fix sd-mount, update blobs with 4.4 MotoX leak
Known Issues:
Ext-SD not activated
As with other AOSP builds, Google Keyboard is not working. Make sure to use AOSP keyboard.
Does not work with 16GB internal storage https://twitter.com/dhacker29/status/398946262172446720 (Try different versions of TWRP to address this)
Front camera may not work - will crash camera app. Go to app info and clear data to run it again
Video playback problems for some
Some HDMI problems when plugged in
I'm pretty happy on CM 10.2, but I may have to flash this just to see what 4.4 is all about...
Thanks for sharing! :good:
Thanks for sharing.
From a comment on twitter, it looks like the external SD card doesn't work. Just an FYI for those who are flashing.
Sent from my XT926 using Tapatalk
Just tried to flash the ROM using CWM... obviously didnt work lol.
Flashed TWRP 2.6.3.0, then flashed the ROM
Setting up device now.
Ill post after a day or so of usage to let everyone know how its going.
TXKSSnapper said:
From a comment on twitter, it looks like the external SD card doesn't work. Just an FYI for those who are flashing.
Sent from my XT926 using Tapatalk
Click to expand...
Click to collapse
You got right.
Another FYI. TWRP 2.6.3.0 in the first post does not work on the XT925.
madmonkey57 said:
Another FYI. TWRP 2.6.3.0 in the first post does not work on the XT925.
Click to expand...
Click to collapse
Worked fine for me, it's how I flashed it in the first place. How did it fail on your end?
dabanhfreak said:
Worked fine for me, it's how I flashed it in the first place. How did it fail on your end?
Click to expand...
Click to collapse
do you mind editing the OP to include a list of known issues?
Thanks!
koftheworld said:
do you mind editing the OP to include a list of known issues?
Thanks!
Click to expand...
Click to collapse
Yet to run into any tbh (besides ex-SD of course), will give it about 24hours and see what folks pick up.
koftheworld said:
do you mind editing the OP to include a list of known issues?
Click to expand...
Click to collapse
Got stuck on the M Logo. But now, I'm wondering if it's not the infamous "Stuck on the M Logo" bug more than the recovery not working on the XT925. I'll try again.
madmonkey57 said:
Another FYI. TWRP 2.6.3.0 in the first post does not work on the XT925.
Click to expand...
Click to collapse
I just fastboot TWRP 2.6.3 now and it´s working flawlessly on XT925. I´m using it to do a backup right now before trying the wonderful Dhacker piece of work.
flight666 said:
I just fastboot TWRP 2.6.3 now and it´s working flawlessly on XT925. I´m using it to do a backup right now before trying the wonderful Dhacker piece of work.
Click to expand...
Click to collapse
Using Flashify. It flashes OK, but I can't get to the recovery... Hanging on the M logo. Damn it.
Can the atrix HD flash this??
Sent from my MB886 using xda app-developers app
Flashing TWRP 2.6.3.0 using Flashify --> Can't boot to the recovery, stuck on the M Logo
Flashing TWRP 2.6.3.0 using fastboot/USB cable --> Can't boot to the recovery, stuck on the M Logo
Flashing OUDhs CWM Touch Req0very v1.0.3.4 using fastboot/USB cable --> boot to the recovery OK
As it works for some other XT925s out there, something is wrong with mine...
---------- Post added at 03:37 PM ---------- Previous post was at 03:32 PM ----------
madmonkey57 said:
Flashing TWRP 2.6.3.0 using Flashify --> Can't boot to the recovery, stuck on the M Logo
Flashing TWRP 2.6.3.0 using fastboot/USB cable --> Can't boot to the recovery, stuck on the M Logo
Flashing OUDhs CWM Touch Req0very v1.0.3.4 using fastboot/USB cable --> boot to the recovery OK
As it works for some other XT925s out there, something is wrong with mine...
Click to expand...
Click to collapse
Got it:
My twrp file was 8370KB whereas the actual file size is 8400KB... The first download failed and it missed the last 30KB...
I confirm TWRP 2.6.3.0 running on my device as well.
madmonkey57 said:
Flashing TWRP 2.6.3.0 using Flashify --> Can't boot to the recovery, stuck on the M Logo
Flashing TWRP 2.6.3.0 using fastboot/USB cable --> Can't boot to the recovery, stuck on the M Logo
Flashing OUDhs CWM Touch Req0very v1.0.3.4 using fastboot/USB cable --> boot to the recovery OK
As it works for some other XT925s out there, something is wrong with mine...
---------- Post added at 03:37 PM ---------- Previous post was at 03:32 PM ----------
Got it:
My twrp file was 8370KB whereas the actual file size is 8400KB... The first download failed and it missed the last 30KB...
I confirm TWRP 2.6.3.0 running on my device as well.
Click to expand...
Click to collapse
Good to see
I'm noticing that there's a bug in the AOSP launcher, I can't seem to add a new home screen.
I installed the Nexus 5 Launcher as well, same result.
No such problems on Nexus 7 when installed Google Launcher.
EDIT: nvm, it seems that installing Google Launcher messes with the AOSP launcher... didn't make sense to me either. Oh well, no N5 experience
Uh, no, not that either. I think it was a custom Wallpaper.
you've to drag an app to make a new screen on the new kk launcher ?
pls correct me if i'm wrong..
madmonkey57 said:
Got it:
My twrp file was 8370KB whereas the actual file size is 8400KB... The first download failed and it missed the last 30KB...
I confirm TWRP 2.6.3.0 running on my device as well.
Click to expand...
Click to collapse
Great!
Now its me... having error on updater binary flashing the 4.4 ! lol
flight666 said:
Great!
Now its me... having error on updater binary flashing the 4.4 ! lol
Click to expand...
Click to collapse
Downloads are slow and tend to fail before the end... We'd better be careful! I am currently re-downloading all files needed.
Hello peeps...
This is Pure Stock Image 4.4.3 from deodexed it and Converted to F2FS..
Lets first understand,
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
What is All-F2FS?
We used F2FS only for /data. It was simply because we have only to flash a compatible Kernel and Format /data partition. With All-F2FS we use F2FS for all partitions and we need a compatible ROM
Instructions :
Download compatible ROM
Download FormatPartitions.zip
Download "special" TWRP for All-F2FS: openrecovery-twrp-2.7.0.0-mako-All-F2FS.img
(This is different for that of simply F2FS)
Copy FormatPartitions.zip and ROM on Phone
Flash "special" TWRP with Fastboot
Flash FormatPartitions.zip with new Recovery
Reboot Recovery
Flash ROM with new Recovery
(Flash GApps with new Recovery)
Go to Wipe Menu and press Format Data (The Big BUTTON!) (You will LOSE all your Data! Music, Movies etc!!)
Reboot
Note : If you already on F2FS directly flash the zip and then Supersu from below link
Tested it..
All working fine..
Need to flash Supersu to retain root..
Downlaods
Link : Flashable Zip Folder - All Files
or
Flashable Zip - ROM
Mirror Link :
http://goo.gl/oQL9uD
Supersu : http://download.chainfire.eu/446/SuperSU/UPDATE-SuperSU-v1.99r3.zip
Wifi Fix : Wifi Fix
F2FS 4.4.3 Kernel : d-h.st/t34
Credits :
@is0l4ted - creating the F2FS version
@My Nexus 4 whatsapp group members..
@Rohit02(Me)
@CallMeAldy : Wifi Fix
Changelogs :
2014/06/03 : Initial Release
2014/06/04 : Fixed bootoop for some users. Fix zip included in the new link. (Old link removed)
Rohit02 said:
Hello peeps...
This is Pure Stock Image 4.4.3 from deodexed it and Converted to F2FS..
@My Nexus 4 whatsapp group members..
Click to expand...
Click to collapse
There's a Nexus 4 WhatsApp group?
Sent from my Nexus 4 using XDA Free mobile app
Rohit02 said:
Hello peeps...
This is Pure Stock Image 4.4.3 from deodexed it and Converted to F2FS..
Tested it..
All working fine..
Need to flash Supersu to retain root
Click to expand...
Click to collapse
I'm on stock with root, recovery and Xposed. Can I just flash the zip and root again without lose anything?
is there a big difference in speed with F2FS? any problems??
thx
Gr8 work @is0l4ted and @Rohit02 and all the Whatsapp Group members !! Really short on time but if possible will try flashing it tomm evening !!
ronakchavan said:
There's a Nexus 4 WhatsApp group?
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Hmm yes an amazing group
ttheodorou said:
is there a big difference in speed with F2FS? any problems??
thx
Click to expand...
Click to collapse
Many threads out there about f2fs its advantages and disadvantages !! Its faster in opening apps and boot times and improved io performance especially on dalvik !!
NABENDU1 said:
Many threads out there about f2fs its advantages and disadvantages !! Its faster in opening apps and boot times and improved io performance especially on dalvik !!
Click to expand...
Click to collapse
so in short it is a good upgrade for the phone. i think i will try it at some point
ok I flashed without wipe and now it's in bootloop. Uff I don't want to wipe everything
CWM ?
Is it compatible with TWRP only or can I flash it via CWM ?
Sorry Bro
gajira said:
ok I flashed without wipe and now it's in bootloop. Uff I don't want to wipe everything
Click to expand...
Click to collapse
Sorry Bro for the inconvenience.. here is the fix for your problem hope you didn't wiped again!!!
Hit Me to fix bootloop!! or Me!!
---------- Post added at 02:09 AM ---------- Previous post was at 02:03 AM ----------
spfc_jcp88 said:
Is it compatible with TWRP only or can I flash it via CWM ?
Click to expand...
Click to collapse
Only TWRP F2FS Version. To confirm that the back button on TWRP should be red in color.
is0l4ted said:
Sorry Bro for the inconvenience.. here is the fix for your problem hope you didn't wiped again!!!
Hit Me to fix bootloop!! or Me!!
---------- Post added at 02:09 AM ---------- Previous post was at 02:03 AM ----------
Only TWRP F2FS Version. To confirm that the back button on TWRP should be red in color.
Click to expand...
Click to collapse
thanks, I had a nandroid backup
Maybe that's the problem, I need a F2FS TWRP.
OP updated..
Enjoy
Can't seem to get my wifi working :/ Installer says it should be activated to view networks, but i cant activate it. If i skip the first install screen where you need to log into your google account etc, and then try to activate wifi in the settings menu nothing happens when i flip the switch :/
Did a clean install multiple times, but it just keeps on not working any fixes for this?
mumaster20 said:
Can't seem to get my wifi working :/ Installer says it should be activated to view networks, but i cant activate it. If i skip the first install screen where you need to log into your google account etc, and then try to activate wifi in the settings menu nothing happens when i flip the switch :/
Did a clean install multiple times, but it just keeps on not working any fixes for this?
Click to expand...
Click to collapse
Same here. Cannot activate wi-fi.
Can I have to install the new radio?
sychim said:
Same here. Cannot activate wi-fi.
Click to expand...
Click to collapse
flash new modem and baseband. If you change to the new android version google provides new binaries. If you haven't then maybe you're wifi won't work. Look in general section for modem baseband flashable.zip
or here:
http://forum.xda-developers.com/nexus-4/general/ref-mako-modem-collection-t2087227
carepack said:
flash new modem and baseband. If you change to the new android version google provides new binaries. If you haven't then maybe you're wifi won't work. Look in general section for modem baseband flashable.zip
or here:
http://forum.xda-developers.com/nexus-4/general/ref-mako-modem-collection-t2087227
Click to expand...
Click to collapse
Already got the new .02 baseband installed :/
To install this "special" recovery, which one of these commands is right?
Code:
fastboot flash boot filename.img
OR
Code:
fastboot flash recovery filename.img
Many thanks before...
omegahanggara said:
To install this "special" recovery, which one of these commands is right?
Code:
fastboot flash boot filename.img
OR
Code:
fastboot flash recovery filename.img
Many thanks before...
Click to expand...
Click to collapse
fastboot flash recovery filename.img
is the right way...
carepack said:
fastboot flash recovery filename.img
is the right way...
Click to expand...
Click to collapse
You're my hero.... :highfive:
omegahanggara said:
You're my hero.... :highfive:
Click to expand...
Click to collapse
no problem man
Hi many People have Net Hunter installing problems!! here its in NOOB:cyclops:friendly Instructions
1: Root ur device and install TWRP latest. {MULTIROM MANAGER HIGHLY RECOMMENDED}
2: Install CynogenMod 13 snapshot latest as secondary OS not primary{Daily Driver} coz nightly's dnt work
3:install Open Gapps 6.0
4: After installing both of them just fill startup information like Gmail etc.
5:Reboot into TWRP and install Kali Linux Net Hunter 3.0{Marshmallow} Nexus 5
6: Select the files u need and then reboot(On the last stage it will be saying Finding Chroot it may take a while) Yes it Takes 20min. let it stay or just start clicking on the bottom right side it will go back to twrp there will be no button while clicking.
7: Reboot Ur device and then start cm13(Net Hunter)
8: Open ur net hunter app and update it 1st then download chroot package {Full chroot package highly recommended to download}
9: After everything finishes reboot ur device!
10: VOILA Net hunter runnung smooth has butter and HAPPY HACKING
{CM 13} https://download.cyanogenmod.org/get/jenkins/158655/cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NM-hammerhead.zip
{Net Hunter} https://images.offensive-security.com/nethunter-release/nethunter-hammerhead-marshmallow-3.0.zip
{GAPPS} http://opengapps.org/
(USE 6.0 GAPPS)
hii man
i do all u sad but in installation my device have problem and the proces stoped in 40 & 70% heelp meee
yup didnt work for me either, stuck at 90% checking for chroot and over 30mins passed. tapping bottom right a bunch of times didnt bring me back to twrp either
Sword_of_a_1000_truths said:
yup didnt work for me either, stuck at 90% checking for chroot and over 30mins passed. tapping bottom right a bunch of times didnt bring me back to twrp either
Click to expand...
Click to collapse
yup it happens many times reboot ur phone while pressing power button and see it cm13 boots up
and use cm 13 has secondary rom not as daily driver and flash net hunter zip over cm13
hi an other thing i finally could do that but cellular data is not working properly hav e u any suggestions?
puoria said:
hi an other thing i finally could do that but cellular data is not working properly hav e u any suggestions?
Click to expand...
Click to collapse
umm.. not working! what is happening actually!
pranavmali said:
umm.. not working! what is happening actually!
Click to expand...
Click to collapse
LTE is shown in notification bar but this (!) not gone and data not working
puoria said:
LTE is shown in notification bar but this (!) not gone and data not working
Click to expand...
Click to collapse
try to change networks from Mobile Networks in {Setting>more>Mobile Networks}.. change it form LTE to 2g or 3g restart ur phone and change it back to LTE!.. if this dosent work then the problem would be ur network carrier.. or ur data pack! Coz i dnt hv a network problem on LTE at all
pranavmali said:
try to change networks from Mobile Networks in {Setting>more>Mobile Networks}.. change it form LTE to 2g or 3g restart ur phone and change it back to LTE!.. if this dosent work then the problem would be ur network carrier.. or ur data pack! Coz i dnt hv a network problem on LTE at all
Click to expand...
Click to collapse
my other ROM haven't this problem and I do all of u said but nothing changed I guess I should install ROM again maybe that work
---------- Post added at 08:43 AM ---------- Previous post was at 08:43 AM ----------
pranavmali said:
try to change networks from Mobile Networks in {Setting>more>Mobile Networks}.. change it form LTE to 2g or 3g restart ur phone and change it back to LTE!.. if this dosent work then the problem would be ur network carrier.. or ur data pack! Coz i dnt hv a network problem on LTE at all
Click to expand...
Click to collapse
my other ROM haven't this problem and I do all of u said but nothing changed I guess I should install ROM again maybe that work
thanks man ur best:good::good::good:
puoria said:
my other ROM haven't this problem and I do all of u said but nothing changed I guess I should install ROM again maybe that work
---------- Post added at 08:43 AM ---------- Previous post was at 08:43 AM ----------
my other ROM haven't this problem and I do all of u said but nothing changed I guess I should install ROM again maybe that work
thanks man ur best:good::good::good:
Click to expand...
Click to collapse
Or u can install other rom and use that as a daily driver! Coz even the devs do not recommend this rom as Daily Driver! Use this rom to hack or wht even u do in Kali Linux! Possibilities are Endless!
Dude I am runing reseruction remix, and I want to install net hunter. Plzz tell in detail. As per me I will flash cm13 snapshot and open gapps, then do we have to directly flash nethunter or is there any other way. The problem is how to make it secondary. Plzz help
defaulter11s said:
Dude I am runing reseruction remix, and I want to install net hunter. Plzz tell in detail. As per me I will flash cm13 snapshot and open gapps, then do we have to directly flash nethunter or is there any other way. The problem is how to make it secondary. Plzz help
Click to expand...
Click to collapse
if ur on RR install multirom manager and install its recovery! with its kernel! then reboot into recovery and navigate into add rom go forward install cm13 and then install its gapps then reboot! set ur cm13 and flash net hunter over cm13 ( navigate to manage roms in recovery click on cm13 then then there will be an option called flash zip Flash net hunter and check what you want then reboot!! Read the thread Carefully
pranavmali said:
if ur on RR install multirom manager and install its recovery! with its kernel! then reboot into recovery and navigate into add rom go forward install cm13 and then install its gapps then reboot! set ur cm13 and flash net hunter over cm13 ( navigate to manage roms in recovery click on cm13 then then there will be an option called flash zip Flash net hunter and check what you want then reboot!! Read the thread Carefully
Click to expand...
Click to collapse
Can you explain in detail plzz, I still dont understand, I need a step to step guide, because we are 5 people here with Nexus 5 all waiting for flashing nethunter, currently we all have twrp latest and Resurrection Remix Running.
Plzz send a step to step guide cause we don't know about multirom manager and its recovery and all the stuff, we are just aware about flashing roms and recoveries and other flashable zip, so please help us.
defaulter11s said:
Can you explain in detail plzz, I still dont understand, I need a step to step guide, because we are 5 people here with Nexus 5 all waiting for flashing nethunter, currently we all have twrp latest and Resurrection Remix Running.
Plzz send a step to step guide cause we don't know about multirom manager and its recovery and all the stuff, we are just aware about flashing roms and recoveries and other flashable zip, so please help us.
Click to expand...
Click to collapse
1st Install Multirom manager from play store
2: Open it it will see if your kernel has Kernel-exe patch if yes it will only its modified twrp or it will install modified kernel and twrp let it do its thing!
3 after Everything is done by Multirom reboot into recovery!
4: Go to Multirom Manager in recovery
5 select add rom and then select your zip files 1st flash Cm13 then go back dont reboot just press the back button. Then refresh.. it will show you cm13 select it.
6 there will a option called flash zip when you select cm13 select that option and flash open gapps! Then reboot and set your device up!
7: read yhe thread! If you dont knw kali linux do some research and then flash the net hunter the same way as we flashed open gapps on cm 13
pranavmali said:
1st Install Multirom manager from play store
2: Open it it will see if your kernel has Kernel-exe patch if yes it will only its modified twrp or it will install modified kernel and twrp let it do its thing!
3 after Everything is done by Multirom reboot into recovery!
4: Go to Multirom Manager in recovery
5 select add rom and then select your zip files 1st flash Cm13 then go back dont reboot just press the back button. Then refresh.. it will show you cm13 select it.
6 there will a option called flash zip when you select cm13 select that option and flash open gapps! Then reboot and set your device up!
7: read yhe thread! If you dont knw kali linux do some research and then flash the net hunter the same way as we flashed open gapps on cm 13
Click to expand...
Click to collapse
Thank you so much bro, but it wont brick my phone right
defaulter11s said:
Thank you so much bro, but it wont brick my phone right
Click to expand...
Click to collapse
Nope ! your RR rom will be perfect! if anything goes wrong you can just delete Cm13 from recovery and start over!
pranavmali said:
Nope ! your RR rom will be perfect! if anything goes wrong you can just delete Cm13 from recovery and start over!
Click to expand...
Click to collapse
Thank you so much, you are the best.
Could you please elaborate the last point about how to setup kali nethunter. I did the multirom thing, now plzz explain the flashing process
. I know I am disturbing you sorry for that
defaulter11s said:
Could you please elaborate the last point about how to setup kali nethunter. I did the multirom thing, now plzz explain the flashing process
. I know I am disturbing you sorry for that
Click to expand...
Click to collapse
Install Cm13 as secondary rom from multirom manager recovery!
install gapps over cm13 {Navigate to Multi Rom manager in recovery! select Cm13 then there will a option called Flash zip select that option and then select your gapps zip them flash it and reboot! then set your device up!
install the net hunter zip the same way we flashed the Gapps zip!
Net Hunter has AROMA fzip so choose your options carefully everyone needs are different so dont ask Me which options to choose! the interface is very simple!
pranavmali said:
Install Cm13 as secondary rom from multirom manager recovery!
install gapps over cm13 {Navigate to Multi Rom manager in recovery! select Cm13 then there will a option called Flash zip select that option and then select your gapps zip them flash it and reboot! then set your device up!
install the net hunter zip the same way we flashed the Gapps zip!
Net Hunter has AROMA fzip so choose your options carefully everyone needs are different so dont ask Me which options to choose! the interface is very simple!
Click to expand...
Click to collapse
I already did that you are telling now, but after installing cm13 snapshot and setting up and then installing net hunter cm13 what I get is a black screen and buttons, statusbar. I am sending screenshot.
AOKP Nougat for Axon 7 has arrived!
* You can dirty flash from the official AOKP M builds.
* FP reader seems broken on first boot, but seems to work after a reboot.
* Sources at https://github.com/AOKP/device_zte_axon7
This ROM requires the N boot stack. Get the link from the Lineage 14.1 thread.
Official download link: http://xfer.aokp.co/?developer=AOKP&folder=axon7
Reserved.
Omg yessss
---------- Post added at 06:50 PM ---------- Previous post was at 06:50 PM ----------
Going to flash right now thank you so much
Hmm, FP reader started working. Not sure why, maybe a reboot fixed it.
Ugh... On 14.1 now. Looks like I'll nandroid back up and give this bad boy a spin. Thanks!
Can't download. Will check back.
is the bootstack flashed before or after flashing the ROM?
also the site is down alt. link?
gecko702 said:
is the bootstack flashed before or after flashing the ROM?
also the site is down alt. link?
Click to expand...
Click to collapse
Flash the boot stack first, the ROM should assert on the boot stack version.
If basket build stays down, I'll mirror the file.
Does this ROM have the same sound issues as Lineage? (only left channel, distortion at high volumes)
---------- Post added at 09:15 PM ---------- Previous post was at 09:06 PM ----------
And also if you're saying that udev can't release his sources until next week when the N update is out, does that mean that it will be actually be out next week?
site is still down
Would someone mirror this!!!!
Sent from my ZTE A2017U using XDA Forums
Download is working
So I flashed this from lineage 14.1. Booted fine after a full wipe (would not boot on dirty flash).
Restored lineage backup and my decrypt password worked, but the pin on first boot would not accept (wrong pin).
Rebooted to twrp (3.0.4), put in password, said it decrypted fine
Tried full wipe and it failed to mount data, said decrypt unsuccessful.
Tried a data format, unsuccessful
Tried another restore, unsuccessful
rebooted a couple times and suddenly I could wipe data.
Reboot and now I when I put in my password I get password correct, but data is corrupt.
Still working to resolve. b29 is downloading and I will attempt to flash that next.
Just a warning...
Download is working for me, just slow (saying 36 minutes left and been going for a 5 minutes now). I can't mirror it though, plus I'm leaving in about 5 minutes for a gig (in a band). So not much help other than saying it works for me?
Mirror for test build: http://code.nwwn.com/files/android/roms/aokp_axon7_nougat_UNOFFICIAL_2017-02-02.zip
@lafester
lafester said:
Restored lineage backup and my decrypt password worked, but the pin on first boot would not accept (wrong pin).
Click to expand...
Click to collapse
If for whatever reason you run again into this "wrong pin " or pattern after restoring a backup just to the following:
1. Boot to TWRP
2. Use the File Manager of TWRP
3. navigate to and delete.
* Data > System > Locksetting.db
Then just boot normal again and you're Good to go.
DrakenFX said:
@lafester
If for whatever reason you run again into this "wrong pin " or pattern after restoring a backup just to the following:
1. Boot to TWRP
2. Use the File Manager of TWRP
3. navigate to and delete.
* Data > System > Locksetting.db
Then just boot normal again and you're Good to go.
Click to expand...
Click to collapse
Yeah I should have tried that once I had access to internal data. I should still have my backup and will try that next if it is still an issue.
Flashing b29 did get me back for the moment.
edit - flashed backup, encountered 'wrong pin' again. reboot to twrp and delete locksetting.db and all is well.
tempted to just stop using all these passwords for awhile until this is sorted.
Flashed from lineage 14.1. Everything went fine. Downloaded XDA app to post screenshot to this thread. App crashed when attempted attachments. Restored backup but had to reformat data partition to ext4. So lost screenshot. Would have moved to extSD card if I would have thought of it. Anyway, pretty good build. Thanks for the work @tdm
Really like seeing some movement in the Dev community on this phone.
Some issues I've noticed so far on the test build:
* Soft restart during or after using split screen.
* Photos won't start.
* Screen shot won't save.
tdm said:
Some issues I've noticed so far on the test build:
* Soft restart during or after using split screen.
* Photos won't start.
* Screen shot won't save.
Click to expand...
Click to collapse
also the package manager keeps crashing for me so i cant open most of the apps. but the screenshots seem to work for me
edit: package manager crashes on every new app start BUT you can fix this by manually giving app the permissions they ask for
tdm said:
Some issues I've noticed so far on the test build:
* Soft restart during or after using split screen.
* Photos won't start.
* Screen shot won't save.
Click to expand...
Click to collapse
I was also able to get a screen shot using power + vol down. It saved to gallery.