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.
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.
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...
Latest Ufirm QE2 Nougat Firmware For The S7 Edge Only
This well give you a Customizable NonRooted Rom that uses stock boot.img not the eng boot image so there is no lag and it will pass safetynet checks and samsung pay will work
Give this guy @umaro some thanks he worked on this until it became reality even when I gave up
Files To Download
Odin.zip
ADB_Root_G935U_QE2Files.zip
Mega Mirror Link
UFIRM_G935_Odin_Firmware.zip
Mega Mirror Link
FlashFire_Flashable_G935UFirmware.zip
Mega Mirror Link
UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_QE2_V3.zip
These first 2 step must be done first unless you are on my previous version of this rom or my carrier specific rom that do not have root or if your unsure just do this first
This Will Wipe Your Phone
1. Unzip UFIRM_G935_Odin_Firmware.zip and flash all files in odin
2. Go through setup ignore invalid sim message and skip adding accounts
3. Goto Step 3 Below
If you are on one of my previous version of this rom or my carrier specific rom
1. Unzip UFIRM_G935_Odin_Firmware.zip
2. Use odin to flash BL and CP
3. Unzip ADB_Root_G935U_QE2Files.zip
4. Flash EngBoot image with odin
5. Root Phone. Im not going to have half a page about rooting there is an entire rooting thread here. The Eng Boot.img can be found in the UFIRM_QD2_Modified_Nougat_Firmware Folder
6. Unzip FlashFire_Flashable_G935UFirmware.zip
7. Copy AP_FlashFire_Only_G935U_QE2_Firmware.tar.md5 to internal storage of your phone
8. Copy UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_QE2_V3.zip to internal storage of your phone
9. Open FlashFire and click Add Zip and choose UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_QE2_V3.zip make sure to check mount system
10. Now in FlashFire click Add Firmware and choose AP_FlashFire_Only_G935U_QE2_Firmware.tar.md5 select all the partitions
11. Make sure Inject SuperSu is not selected
12. Click Add Wipe and choose Wipe Dalvik Cache and Cache and choose Format Cache Also select wipe SuperSU image. Make sure wipe is at end of flash sequence. The sequence should be AP file first then Zip second and Wipe cache last
13. Now Choose Flash
14. Phone will take Up to 20 minutes to boot
15. Reflashing Zip Will Require Flashing The AP File In FlashFire At The Same Time
16. Do not use Package Disabler Pro if you Choose NoNaMe mods in Aroma
MODS- (NoNaMeRomControl)
3minitbattery
Speed meter
Status bar mods
Center clock
Wifi/signal bar mods
Color change icon mod
Custom backgrounds
Notification drop-down
Incallui background
Gif in notification drop-down
Change/remove carrier names
And much more...
THANKS AND CREDITS
@jds3118 for testing and providing files and bootlooping his phone countless times for me
Gharrington for his awesome 3minitbattery mod...
NoNaMe rom development team for their incredible mods and rom control app...
@malbert16442 for his black themes
Xda for all the great guides to accomplish this...
Kernel source
RomControl Source
I recommend everyone put the Flashfire AP zip and Rom Zip on your internal storage as the AP file is so large that it may not be read properly do too limitations of some SD Cards. When you select AP file in Firmware there should be 4 partitions that are selected. If not then you have a bad download or need to have AP file on internal storage
You are a big @jrkruse and I love what you build I will install it in a couple of hours I will return thanks
Sent from my SM-G935T using XDA-Developers Legacy app
Can there will be a stock android custom rom?
---------- Post added at 08:23 AM ---------- Previous post was at 08:22 AM ----------
Thanks for your work ?
Hey man! Awesome that you've got a ufirm rom thread here too.. now I don't have to go to the verizon forums
umaro said:
Hey man! Awesome that you've got a ufirm rom thread here too.. now I don't have to go to the verizon forums
Click to expand...
Click to collapse
I just updated all the OP's of the Ufirms I forgot to give you a shoutout for your work. Thanks again I am sure Tmobile and ATT people will agree. Even gave the Flat Tmobile and ATT some new roms to play with
Gohar___Nadeem said:
Can there will be a stock android custom rom?
---------- Post added at 08:23 AM ---------- Previous post was at 08:22 AM ----------
Thanks for your work
Click to expand...
Click to collapse
Not sure what your asking. But yes there is a custom stock tmobile rom as well
Sorry for my bad english....
I'm asking that!
Like lineage Os ,resurrection remix any of that kind rom will be available for t-mobile in future?
Gohar___Nadeem said:
Sorry for my bad english....
I'm asking that!
Like lineage Os ,resurrection remix any of that kind rom will be available for t-mobile in future?
Click to expand...
Click to collapse
Probably not
I've tried to install twice so far. Both times I make it as far as Aroma installer getting to "Wiping Data" then phone reboots to Splash screen and just sits. Doesn't make it to boot animation. Tried rebooting, then booting to recovery and wiping cache, then tried factory reset, but nothing helped.
Are there any things I should avoid in Aroma options?
radoo7701 said:
I've tried to install twice so far. Both times I make it as far as Aroma installer getting to "Wiping Data" then phone reboots to Splash screen and just sits. Doesn't make it to boot animation. Tried rebooting, then booting to recovery and wiping cache, then tried factory reset, but nothing helped.
Are there any things I should avoid in Aroma options?
Click to expand...
Click to collapse
Did you flash the Verizon Odin files first. Then root. The flashfire AP and Rom zip
jrkruse said:
Did you flash the Verizon Odin files first. Then root. The flashfire AP and Rom zip
Click to expand...
Click to collapse
Yup, I did everything exactly as listed. Since there was no directions for Aroma, I was wondering if I was picking a wrong option there. I choose full wipe, TMo stock kernel, modded ui, but it always fails at Wipe when it starts to install.
radoo7701 said:
Yup, I did everything exactly as listed. Since there was no directions for Aroma, I was wondering if I was picking a wrong option there. I choose full wipe, TMo stock kernel, modded ui, but it always fails at Wipe when it starts to install.
Click to expand...
Click to collapse
So you never get through aroma installer?
jrkruse said:
So you never get through aroma installer?
Click to expand...
Click to collapse
I get thru the options, then hit install. Installer starts at Wipe, the my phone just reboots to Splash screen the nothing. 3rd try I picked No Wipe and still same thing.
Downloading TMobile version to try that one tomorrow.
radoo7701 said:
I get thru the options, then hit install. Installer starts at Wipe, the my phone just reboots to Splash screen the nothing. 3rd try I picked No Wipe and still same thing.
Downloading TMobile version to try that one tomorrow.
Click to expand...
Click to collapse
Are you choosing to mount system when you choose the rom zip with flashfire
jrkruse said:
Are you choosing to mount system when you choose the rom zip with flashfire
Click to expand...
Click to collapse
Yup. To the best of my knowledge I've followed every step exactly. It may be possible I have a bad download. My internet has been acting up. I'll try again later after I talk with my service provider tomorrow. Thanks
radoo7701 said:
Yup. To the best of my knowledge I've followed every step exactly. It may be possible I have a bad download. My internet has been acting up. I'll try again later after I talk with my service provider tomorrow. Thanks
Click to expand...
Click to collapse
Could you tell me each mod you chose so I can see if I can recreate the problem. Also is te AP and zip on your phone storage or sdcard
Edit:Also ceck the md5 of your download
jrkruse said:
Could you tell me each mod you chose so I can see if I can recreate the problem. Also is te AP and zip on your phone storage or sdcard
Click to expand...
Click to collapse
I picked full wipe, TMo stock kernel, modded ui, NoName boot animation. Most of the S8 apps and custom debloat. I tried the dual speaker mod the first 2 times but not the 3rd.
Both files are on my sdcard.
radoo7701 said:
I picked full wipe, TMo stock kernel, modded ui, NoName boot animation. Most of the S8 apps and custom debloat. I tried the dual speaker mod the first 2 times but not the 3rd.
Both files are on my sdcard.
Click to expand...
Click to collapse
Do you remember what you chose in custom debloat. I just want to run your same config and try. I would check that md5 use and md5 checker program then check it against Android file host generated md5 for file. If its bad there is no need in doing all this
jrkruse said:
Do you remember what you chose in custom debloat. I just want to run your same config and try. I would check that md5 use and md5 checker program then check it against Android file host generated md5 for file. If its bad there is no need in doing all this
Click to expand...
Click to collapse
I don't remember exactly. One of the times I just chose the minimal debloat option (70 apps, I think)
Anyway, I'll have to try again tomorrow after work.
MODIFIED INSTALL PROCEDURE TO AVOID FORCE CLOSES !
Made a SL!M rom of the chinese A2017 V2.0 B13 MiFavor 5.0 version ( with its new Camera app, VoLTE,...)
I debloated most of the unnecessary apps and added some new ones. It’s nothing too fancy but worth looking into. It was a bit harder to make SuperSU working ok. So follow the steps carefully when flashing !
It’s fully functional and tested. Smooth, no bugs (report when there is)
Hope you’ll E N J O Y !!!
Based on :
A2017 V2.0 B13 MiFavor 5.0
INSTALL : ( TWRP ) IN FOLLOWING ORDER
When you're on another ROM and you want a clean install just follow this procedure :
For replacing SuperSU with Magisk : in ROM zip replace in ROOTZIP folder the SuperSU.zip with the Magisk zip. Use 7-zip. Just drag&drop..easy !
IMPORTANT : rename to magisk.zip to the same name as in rootzip folder: "SuperSU.zip". So remark capitals !
That should do the trick. Just reflash the procedure and Magisk is there.
MAGISK zip : https://androidfilehost.com/?fid=889964283620765995
You also can try out other modem (for G model they're all in DownloadCenter) for testing out better battery life, signal and so on.[/B][/SIZE][/COLOR] thnx for testing @joaste
NEW METHOD TO AVOID FORCE CLOSES (AS ON AROMA MF5.0)
0. In case you want to reflash your own apps backup your personal apps with f.e. TB, ZipMe... (or whatever)
00. running TWRP 3.1.1.0
1. Make a full backup of your current device in TWRP ! (use it to RESTORE if necessary) DON’T FORGET !
2. Wipe cache / dalvik / data / system
3. Install BUT DO NOT BOOT : A2017 V2.0 B13 MiFavor 5.0 SL!M : https://androidfilehost.com/?fid=817906626617946091
4. CHOOSE : 4a or 4b
4a. Install : bootstack B13 FIX 2 when coming from another rom : https://androidfilehost.com/?fid=745849072291693516
GOTO (5)
4b. Install : bootstack Universal B15 “adapted 3.1.1.0” when already on a MiFavor 5.0 rom
https://androidfilehost.com/?fid=673791459329066038
GOTO (5)
5. Install : MODEM (G) : https://androidfilehost.com/?fid=962021903579492190
( flash modem for A2017U model : https://androidfilehost.com/?fid=817550096634745612 )
( flash modem for A2017 model : https://androidfilehost.com/?fid=457095661767137840 )
6. REBOOT :
6a When you were already on a MiFavor rom ( and of course did 4b ), you’ll normaly have a clean (double) boot
6b When you came from another rom ( and did 4a ), your phone will power off (3 red led). Don’t reboot ! Hold power+vol+ to enter back into twrp. Just flash B15 adapted (4b) with TWRP3.1.1.0 and reboot. No need to flash TWRP3.1.1.0 again. You’ll have a clean boot too.
7. IMPORTANT ! Follow steps !
7a. setup WIFI/data
7b. go into SuperSU and check if all ok
7c. tap ADAWAY and give permissions
7d. tap addless youtube app. You’ll be asked to log in and update google services ! Do so and wait.
7e. tap google playstore, settings/disable autoupdates
7f. open settings/app and go to google services ( even if you’re on the latest 11.9.51 (440-177350961) or 11.7.46 (440-175121617)) Uninstall update ! Reboot, go into youtube app again and update services AGAIN ! YEP !
7g. try an app like google maps(enable gps and get a fix), hangouts or chrome and you’ll normaly see that force closes should be gone !
Everything is working as far as i can see...
INFO :
Stripped off :
....enough
Zte clock replaced by Google Clock
Zte calendar replaced by Google Calendar
ZTe File mananger replaced by ES File Explorer (imo a very good ROOT file manager)
….......
Baked into :
AdAway
ES
Google Calender
Google Clock
YouTube Adfree Black Themed (dont update !)
Minor Modifications :
Boot :
• Init.d enabled
• Dm-verity disabled
Zip aligned apk’s
Build.prop tweaks : (remove them in system/build.prop if not needed)
• Improved performance
• Faster boot
• Phone rings immediately
• Wifi scan interval 180sec
• Better call voice quality
• Better network signal
Added sounds LOS
Hope you'll E N J O Y !!!
Contributors :
me, myself and I
Credits :
@amarullz
@SuperR.
@Unjustified Dev
@Ayush Singh
@ZaneZam (iYTB Thnx !)
@Chainfire
@topjohnwu
@jcadduono
ROM OS Version : 7.1.1 Nougat Mifavor 5.0 (chinese)
Source : ZTE stock-rom A2017UV2.0.0B13 / original ZTE upload/reuploaded : https://androidfilehost.com/?fid=889764386195932870
Kernel : stock
Version Information :
Status : Stable
Created : 2017-11-12
some more pics
You did it [emoji4] [emoji106]
Send from here
Sunn76 said:
You did it [emoji4] [emoji106]
Send from here
Click to expand...
Click to collapse
Were you able to install it? I wasn't.
After all the steps and final reboot, I just got the red led that blinks 2 or 3 times then just a black screen.
Will try again tomorrow.
joaste said:
Were you able to install it? I wasn't.
After all the steps and final reboot, I just got the red led that blinks 2 or 3 times then just a black screen.
Will try again tomorrow.
Click to expand...
Click to collapse
Same thing on my side as well. It was tried with b32 bootstack and b25 modem as well on A2017U. It will not boot on mine either.
First of all, would like to thank you for this!
I'm on Stock v.2.0.0B13 7.1.1 now. Never think of flash any rom until I see this one. But I don't know how to install TWRP on stock rom. Could someone please help (links on how to install TWRP)?
Can I still use android pay with this rom? tks
noeybou said:
First of all, would like to thank you for this!
I'm on Stock v.2.0.0B13 7.1.1 now. Never think of flash any rom until I see this one. But I don't know how to install TWRP on stock rom. Could someone please help (links on how to install TWRP)?
Can I still use android pay with this rom? tks
Click to expand...
Click to collapse
Use the twrp app. Load it from the play store.
BaamAlex said:
Use the twrp app. Load it from the play store.
Click to expand...
Click to collapse
You finished installing the Rom already?
Send from here
Sunn76 said:
You finished installing the Rom already?
Send from here
Click to expand...
Click to collapse
Yeah its running fine. You have to follow steps like I described AND in that order. It'd cost me a day to figure out why it wasn't working with B15 bootstack from djkuz, nor was it working with own bootstacks. Just the universal BL was working with modem flash afterwards. Also very important : you'll have to flash 3.1.1.0 BEFORE BOOTING ! (with INSTALL/IMAGE) . I too had those blinking lights and more of this .
So, put all the downloaded files on your extSD before you begin and dont miss a step in that order. I did the test multiple times So, if it works after i was on N-B08 slim³, it'll work on your device too. Keep trying and remember, always backup.
All pictures are from running rom.
Btw : overnight : 1% battery drop :cyclops: / rom is fluent and smooth / double tap to wake works better then on G roms / clarity over phone call imo is a bit less then on G rom / VoLTE / new camera / ...
picture : my working screen from this morning...
joaste said:
Were you able to install it? I wasn't.
After all the steps and final reboot, I just got the red led that blinks 2 or 3 times then just a black screen.
Will try again tomorrow.
Click to expand...
Click to collapse
Hi joaste,
I had that too. Perhaps you missed a step ? Do follow all procedure in that order. Even the 3.1.10 to flash in TWRP before boot !
HTML:
raystef66 said:
Hi joaste,
I had that too. Perhaps you missed a step ? Do follow all procedure in that order. Even the 3.1.10 to flash in TWRP before boot !
Click to expand...
Click to collapse
Thanks for the follow-up! I think I did it correctly (but it was quite late ), but I'm backing-up right now again and will try to reflash everything.
PS: When I restored the backup I made last night before trying to flash, I was unable to get past the PIN code asked before booting (i.e. I first got the SIM card code request, then I get the lockscreen, then I would get a PIN code request - normally the one associated with my fingerprint - that is the one that upon entering it, nothing would happen). Any ideas?
---------- Post added at 08:43 AM ---------- Previous post was at 08:38 AM ----------
joaste said:
HTML:
Thanks for the follow-up! I think I did it correctly (but it was quite late ), but I'm backing-up right now again and will try to reflash everything.
PS: When I restored the backup I made last night before trying to flash, I was unable to get past the PIN code asked before booting (i.e. I first got the SIM card code request, then I get the lockscreen, then I would get a PIN code request - normally the one associated with my fingerprint - that is the one that upon entering it, nothing would happen). Any ideas?
Click to expand...
Click to collapse
Well just did it all again and now I just get a black screen after the "your device is unlocked" screen. Is this normal or should I be getting the ZTE boot animation?
EDIT: If I hold the power button, I get the ZTE logo, then black screen and red LED blinks 2/3 times, like before.
EDIT2: am re-downloading the ROM now. Maybe there was an issue with it...
joaste said:
HTML:
Thanks for the follow-up! I think I did it correctly (but it was quite late ), but I'm backing-up right now again and will try to reflash everything.
PS: When I restored the backup I made last night before trying to flash, I was unable to get past the PIN code asked before booting (i.e. I first got the SIM card code request, then I get the lockscreen, then I would get a PIN code request - normally the one associated with my fingerprint - that is the one that upon entering it, nothing would happen). Any ideas?
---------- Post added at 08:43 AM ---------- Previous post was at 08:38 AM ----------
Well just did it all again and now I just get a black screen after the "your device is unlocked" screen. Is this normal or should I be getting the ZTE boot animation?
EDIT: If I hold the power button, I get the ZTE logo, then black screen and red LED blinks 2/3 times, like before.
Click to expand...
Click to collapse
Very, very strange....
Is all mounted in TWRP? Also system ? Try to check all and try again.
raystef66 said:
Very, very strange....
Is all mounted in TWRP? Also system ? Try to check all and try again.
Click to expand...
Click to collapse
Yes, everything is mounted.
Just tried it again with a fresh download of all files. Still the same reaction. Black screen
Same Problem with my German users, no success flashing so far
https://www.android-hilfe.de/index.php?posts/10757632
Send from here
joaste said:
Yes, everything is mounted.
Just tried it again with a fresh download of all files. Still the same reaction. Black screen [/QUOTE]
I think i got it
I went back to stock and i experienced now that same issue again with the blinking lights. Strange enough it has all to do with in which state the phone is. To make a long story short try this :
1. upload file from B15 fix from djkuz ( i will upload it in a minute) : https://androidfilehost.com/?fid=673791459329060915
2. Do the same procedure again BUT with the bootstack from B15 djkuz
3. dont forget modem and 3.110 and reboot
4. as all is good you'll see that is powers off after the red lights. Power for 4 secs and you'll boot up untill tiles. But it stays there.
5. Then : go back into TWRP and repeat the all the procedure BUT with universal BL
6. if all ok it boots twice and all ok
Can you perform these steps to test joaste ? Thnx ! ( others have to wait till this is sorted out )
Click to expand...
Click to collapse
Sunn76 said:
Same Problem with my German users, no success flashing so far
https://www.android-hilfe.de/index.php?posts/10757632
Send from here
Click to expand...
Click to collapse
Let them wait too if all sorted out. Main thing is that SU didn;t work with B15 djkuz and univeral bl does.
But lets wait for the test of my friend joaste
Anyways it runs with me so there is something in procedure that has to be fixed.
btw : i see kenet is uploading a universal bl B13 - that might make things easier , who knows
raystef66 said:
joaste said:
Yes, everything is mounted.
Just tried it again with a fresh download of all files. Still the same reaction. Black screen [/QUOTE]
I think i got it
I went back to stock and i experienced now that same issue again with the blinking lights. Strange enough it has all to do with in which state the phone is. To make a long story short try this :
1. upload file from B15 fix from djkuz ( i will upload it in a minute) : https://androidfilehost.com/?fid=673791459329060915
2. Do the same procedure again BUT with the bootstack from B15 djkuz
3. dont forget modem and 3.110 and reboot
4. as all is good you'll see that is powers off after the red lights. Power for 4 secs and you'll boot up untill tiles. But it stays there.
5. Then : go back into TWRP and repeat the all the procedure BUT with universal BL
6. if all ok it boots twice and all ok
Can you perform these steps to test joaste ? Thnx ! ( others have to wait till this is sorted out )
Click to expand...
Click to collapse
Success! Many thanks!!!
Click to expand...
Click to collapse
joaste said:
raystef66 said:
Success! Many thanks!!!
Click to expand...
Click to collapse
THANK YOU FOR TESTING !
It's running ok now ?
Click to expand...
Click to collapse
raystef66 said:
joaste said:
THANK YOU FOR TESTING !
It's running ok now ?
Click to expand...
Click to collapse
I'm updating apps as I write this.
Now you just need to make an Aroma version
I'll update this thread with any comments/questions as they come.
Thanks again (Dank U / Merci) for the time taken!
Click to expand...
Click to collapse
Sunn76 said:
Same Problem with my German users, no success flashing so far
https://www.android-hilfe.de/index.php?posts/10757632
Send from here
Click to expand...
Click to collapse
ALL OK NOW
@joaste did the test
Seems to need a DOUBLE routine flash with first B15 and a new flash with universal bl
UPDATED OP !