yashsingh1/xdaforums huggingface dataset:
[Huawei Mate 10  Guides, News, & Discussion] Samael2328:
OREO BETA

Good evening from Panama, I managed to login to the Oreo Beta but it tells me that there are no projects available ...
[Huawei Mate 10  Guides, News, & Discussion] m.heikal:
Unfortunately yes I'm from Egypt :D
[Huawei Mate 10  Guides, News, & Discussion] m.heikal:
i don't know if there is a project for oreo beta testing in panama or not. Maybe there isn't a project in that time or there is a project but it's full.
[Huawei Mate 10  Guides, News, & Discussion] Karim.h.Nassar:
The same as me, but I didn't get the update,
[Huawei Mate 10  Guides, News, & Discussion] santo80s:
huawei nova 2i dont have double tap to wake?
[Huawei Mate 10  Guides, News, & Discussion] king:
[MENTION=5309476]m.heikal[/MENTION] did u check if it brings treble support??
[Huawei Mate 10  Guides, News, & Discussion] santo80s:
Dear [MENTION=5309476]m.heikal[/MENTION] qould you share the rom?
[Huawei Mate 10  Guides, News, & Discussion] GamooSachar:
Yes It does :)
[Huawei Mate 10  Guides, News, & Discussion] king:
Awesome!

Thats the best part of Oreo update;)
[Huawei Mate 10  Guides, News, & Discussion] m.heikal:
go to settings and try to find update manual. i didn't get any notification about update.

By the way I had unlocked my boot loader before joining beta testing project but i re-locked it again before joining project and i haven't had a problem in getting and installing oreo update.
[Huawei Mate 10  Guides, News, & Discussion] m.heikal:
Unfortunately no it doesn't.
[Huawei Mate 10  Guides, News, & Discussion] m.heikal:
yes it does.
[Huawei Mate 10  Guides, News, & Discussion] m.heikal:
the update files seems to be deleted after update i couldn't find it in whole of my phone.

Do you know how to extract the ROM from the phone without using Non-stock recovery?

Is there any way using adb shell?
[Huawei Mate 10  Guides, News, & Discussion] santo80s:
Dear [MENTION=5309476]m.heikal[/MENTION] you can backup using trwp
[Huawei Mate 10  Guides, News, & Discussion] m.heikal:
No i can't because this is a testing version and unlocking bootloader can roll back the official version of EMUI 5.0 as what huawei said in update agreement besides i don't want to erase my personal data.
[Huawei Mate 10  Guides, News, & Discussion] Samael2328:
I have the Huawei RNE-L21C185142

I'm from Pakistan and I live in Panama, my grandparents sent me the team in December and it has the update RNE-L21C185142 and I managed to register in the beta of huawei ... more in says there are no projects ....
[Asus ZenFone 3 Zoom Questions & Answers] mollonado:
Hi guys,

I got the ASUS Zenfone 3 Zoom and started playing with it. Unfortunately I managed to soft brick it and somehow I can't go back to stock. Here are all the things I did. I would be happy to get any ideas what to try next:

1. unlocked the bootloader - using asus's official unlock tool

2. flashed twrp recovery - twrp-3.2.1-0-Z01H-20180304.img, using:

adb reboot bootloader

fastboot flash recovery twrp.img

3. updated asus's firmware to the latest official one:

copying UL-Z01H-WW-71.60.139.30.zip onto internal memory

android detects the update and applying it using android

4. Enabling lock pattern at boot (from android settings). Correct pattern required even when booting into recovery

5. Installing supersu via twrp:

adb reboot recovery

installing supersu

wiping caches (the cache partition cannot be wiped)

6. SuperSu working (tested via android)

7. Reading about Magisk. Trying to install magisk via twrp. Magisk's installer complained that the system is not vanilla (due to SuperSu modifications). Have to uninstall SuperSu to return to previous state.

8. Tried uninstalling SuperSu from the program itself (in android). The uninstaller got stuck. The phone become unresponsive and had to reboot.

9. Found a script packaged as an executable zip (to be installed via twrp) that will uninstall SuperSu and return system to pristine state (SuperSu makes a backup of the files it changes before installation) - UPDATE-unSU-signed.zip. Uninstallation worked.

10. Magisk installation still complained about the bootloader. Then things started to go wrong. I unpacked the latest firware UL-Z01H-WW-71.60.139.30.zip, took out boot.img and tried to flash just the bootloader

fastboot flash boot boot.img

11. Upon reboot the phone got stuck at the ASUS logo. Reboot into recovery and into fastboot still works (soft brick). Still shows unlock pattern at boot.

12. I tried flashing the original firmware using TWRP (install a zip). However the installation threw some errors. Unsuccessful.

13. I've tried flashing the system.img from the original firware using fastboot but still it's stuck at the ASUS logo at boot.

fastboot flash system system.img

Here I am stuck. I've read that TWRP cannot install properly the ASUS official firmware but if you flash the original recovery, it can probably flash it properly. Another thing that I think might explain why I cannot get out of the soft brick is that I've enabled the lock pattern at boot, which effectively encrypted some parts of the phone and I have a strong feeling this interferes with the boot process. I will look for a script/installable zip (via twrp) that can remove the lock.

I really need ideas/suggestions before I make something that will turn my phone into a hard brick. Thanks.
[Asus ZenFone 3 Zoom Questions & Answers] +)KEV1N(+:
What you need to do is flash stock MM recovery from bootloader using "fastboot flash recovery recovery.img"

Since it came with MM preloaded you'll have to install the ROM using stock recovery via adb. It'll take a while, but after that you should upgrade to the latest MM update.

After that, update to any Nougat patch update you wish to receive, because I still haven't figured out yet how to apply them all with [MENTION=1813976]shakalaca[/MENTION]'s recovery images.

Once you're done, you can install twrp again and flash magisk.

Good luck and hope this helped you ;)
[Asus ZenFone 3 Zoom Questions & Answers] mollonado:
Thanks

Thanks,

I tried to find a stock recovery images but unsuccessful. Can you tell me where to get it from?
[Asus ZenFone 3 Zoom Questions & Answers] +)KEV1N(+:
Here's a link to Shakalaca's recovery images.

In the Old folder you'll find MM stock recoveries.

https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w!I89QgZpK

Flash 11.40.86.75 recovery

Boot into recovery

Flash 11.40.86.75 stock rom via adb (it'll take a while)

Once it's done, boot into Android.

Download your respective region's latest MM rom.

Send it to your micro sd.

Install it once Android detects the update file.

(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)

Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)

So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.

After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.

All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.

If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.

This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.

Good luck ;)
[Asus ZenFone 3 Zoom Questions & Answers] mollonado:
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
[Asus ZenFone 3 Zoom Questions & Answers] mollonado:
Sorry I misread your comment. I'm updating to the latest ROM and installing TWRP. Thanks for the help.
[Asus ZenFone 3 Zoom Questions & Answers] +)KEV1N(+:
Glad to help!

---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------

It came preloaded with Nougat? Interesting.
[Asus ZenFone 3 Zoom Questions & Answers] mollonado:
Hi I managed to flash stock ROM - 71.60.139.30, but after that I can't flash twrp - twrp-3.2.1-0-Z01H-20180304.img. I tried with:

adb reboot bootloader

fastboot flash recovery twrp.img

but when I try to boot into recovery with:

adb reboot recovery

it goes into the stock recovery. Is there something I missed? Do I need to downgrade to flash TWRP?
[Asus ZenFone 3 Zoom Questions & Answers] +)KEV1N(+:
Quick question: which of these warnings do you get when you boot?

https://www.androidauthority.com/go...rrupted-and-modified-android-software-629180/

Also, did you try power cycling to get it to boot?

And since the version number made such a large jump, I believe they must have changed something internally with the latest update and that it's probably going to be one of the last Nougat updates before Oreo (which was delayed until June).

I still need to update to that version to check it out, but I might reset soon since I was waiting for Oreo to reset.
[Asus ZenFone 3 Zoom Questions & Answers] mollonado:
I have the Orange warning. It looks a bit different but the wording is the same. Yes, i tried powercycling and still I boot into the stock recovery. What can I do now? Is it possible to downgrade? I am not sure if I boot into stock recovery if it will let me flash an older stock ROM.
[Asus ZenFone 3 Zoom Questions & Answers] mollonado:
I read here - https://android.gadgethacks.com/how-to/twrp-101-install-best-custom-recovery-for-android-0179547/

that once you flash twrp Android upon next reboot might overwrite it with the stock recovery. Is that possible?
[Asus ZenFone 3 Zoom Questions & Answers] +)KEV1N(+:
So, how did you flash TWRP exactly? Using that guide? Or flashed through bootloader?

And to answer your question: yes, it happens sometimes.
[Asus ZenFone 3 Zoom Questions & Answers] mollonado:
Hi, I managed to get around it by directly booting into TWRP from fastboot. Yes, apparently unless I flash some TWRP files to the system partition upon next reboot, the recovery will return to stock. Anyway, I managed to install Magisk and Exposed framework and have been poking with those two for the last couple of days.

The youtube vanced app is great, but I found something that worries me. I can't login to facebook/twitter. I checked and the reason is I can't connect to the facebook.com or twitter.com https sites (even over chrome). I think either:

- I've installed some module which is messing with that

- my rooted phone is hacked

I've installed a module that is meant as ad blocker, that updates the hosts file. However I removed all modules and the problem remains. I really don't wanna start all over again just to check. And even if I reflash and it works, I will not know what caused it and how to fix it myself next time. Do you have any ideas on how to figure out what the problem is?

Regards,
[Asus ZenFone 3 Zoom Questions & Answers] +)KEV1N(+:
First off, my apologies for this late reply (Been superbusy with school and internship assignments)

Secondly, and that is why I only use magisk. Because once you mess with the host file, depending on what module you install, it can range from tripping safetynet to bootlooping.

So quick question, is it still in this state right now since 9 days ago?

Greetings,

Kevin
[Asus ZenFone 3 Zoom Questions & Answers] rinampa:
I made a mistake and could not install recovery stock, I followed what you wrote in the beginning install MM recovery and so I did a hard reset and I was able to install the most current recovery stock and installed ROM Oreo, Thanks. Sorry, I'm on google translator.
[Xiaomi Redmi Note 4 Questions & Answers] billouetaudrey:
Hi,

I have 5 app, I like to convert to system app.

So I use an app, who convert it to /system/priv-app

I want to create a twrp zip file with these app ( apk ). Is it possible ?

This is my updater-script, but I have error, maybe it can help :) ( provide to titanium backup )

Thanks

Sorry for my bad english
[Xiaomi Redmi Note 4 Questions & Answers] DarthJabba9:
package_extract_dir("system", "/system");

This will do in one statement all your several "package_extract_file" statements. And, for the permissions, you might want to try "set_perm_recursive"
[Xiaomi Redmi Note 4 Questions & Answers] billouetaudrey:
Can you post the final update-binary file please? Thanks
[Xiaomi Redmi Note 4 Questions & Answers] DarthJabba9:
Two things a) which final update-binary are you talking about? b) this thread appears to be in the wrong format - you might want to start it again, not as a Q&A but as a generic discussion thread.
[Xiaomi Redmi Note 4 Questions & Answers] billouetaudrey:
https://xdaforums.com/showthread.php?t=3772579
[Google Pixel 2 XL Guides, News, & Discussion] Jmaniac55:
In case you have a Verizon version of the Pixel 2 and installed Android P but would like to go back an official build (Like me[Didn't know I had that version, bought it on Ebay])

DOES REQUIRE FACTORY RESET OR IT WILL GO INTO SYSTEM FAILURE SCREEN
[Non-Touchscreen Windows Mobile Other] maxima00se:
Even though some of us shadow/juno users don't have a section up here yet, are there any works in progress for wm6.1? I know they have it for the dash so I am not sure how much different it would be for the shadow/juno.
[Non-Touchscreen Windows Mobile Other] D1P53T:
ya i would seriously love this haha i really want a 6.1 shadow rom with threaded text messaging
[Non-Touchscreen Windows Mobile Other] freyes01:
I would like to see it too
[Non-Touchscreen Windows Mobile Other] maxima00se:
I would love to see a Juno/Shadow section
[Non-Touchscreen Windows Mobile Other] MightyMike:
we've been fighting for an htc s640 forum for a few weeks now, they just ignore us lol, so i doubt you guys are going to get one as well anytime soon heh..

we're also poking around for a wm6.1 rom, no luck :(

dont' worry guys, you're not the only ones!
[Non-Touchscreen Windows Mobile Other] V2A2:
It sure would be nice to have our own section for the JUNO/Shadow, and I find it hard to believe that none of these ROM cookers have not been working on a WM6.1 custom rom for the shadow.

The 3125 has been a staple of the smartphone community for too long, and anyone who has used the shadow can appreciate the larger screen and better camera found in the shadow.

Come on y'all...........it's time for some JUNO/Shadow love
[Non-Touchscreen Windows Mobile Other] freyes01:
I guess we will have to start learning how to "cook" roms.

I'll try to learn something and post it on my website: http://www.freddyreyes.com/forums
[Non-Touchscreen Windows Mobile Other] ND4SPD:
There isn't that much to regular cooking of roms. The problem is porting it from another device(which I have no idea how to do). Here are the things you need to do to mod the rom after you have that very important step figured out:

Extract rom (extracted versions are floating around in this forum somewhere...(Check Calling all T-Mo Shadow users thread)

Dump rom into bin files and then convert to normal files/folders

Add/remove files as needed

Create XIP chain with working Shadow drivers (Don't know how to do that)

Convert fiel back to a bin file and recreate os file (nk.nbh)

I can do all of these steps except creating the new XIP chain. I have no idea where to start with that.
[Non-Touchscreen Windows Mobile Other] ND4SPD:
I just remembered, you also need to make any drivers in the actual rom that don't work universally to work for the shadow.

If someone can teach me some of the things to do to port the rom, I'll try and do it.
[Non-Touchscreen Windows Mobile Other] maxima00se:
I don't understand why they won't make us a new section :(
[Non-Touchscreen Windows Mobile Other] freyes01:
How can I give you the drivers? Do I need to "dump" my Rom and extract the files?

Here is the post that you mentioned: http://xdaforums.com/showthread.php?t=351660
[Non-Touchscreen Windows Mobile Other] ND4SPD:
Well, I've got the shadow dump, but I don't know how to edit any drivers from a different devices wm6.1 to work for the shadow
[Non-Touchscreen Windows Mobile Other] freyes01:
Maybe Kavana (http://xdaforums.com/member.php?u=373268) at the Excalibur forum can give us a hand. He ported 6.1 to the Dash.
[Non-Touchscreen Windows Mobile Other] ND4SPD:
Ok. What device's wm6.1 should we try and port and what build?

I know that there are currently 3 builds of wm6.1, but I don't know if they all have to do with smartphones(maybe only for ppc). Which should we use?
[Non-Touchscreen Windows Mobile Other] freyes01:
There are 2 that could work. The Dash is very similar to the Shadow. It has wi-fi, bluetooth, camera...however the camera is only 1.3 Mp and the other issue could be the "sure type" shadow's keyboard.

Dash (Smartphone)

http://xdaforums.com/showthread.php?t=374890

Tornado (Smartphone)

http://xdaforums.com/showthread.php?t=375670
[Non-Touchscreen Windows Mobile Other] ND4SPD:
The only problem I can see with using the dash is that it's landscape oriented and the shadow is portrait oriented. It doesn't matter to me though..
[Non-Touchscreen Windows Mobile Other] pixelwix:
spl

i would say use the vox. there is a 6.1 build for the vox. and also not rain on this but, even if you make a build how are we going to flash it? spl will be locked i'm guessing and as far as i know nobody has come up with a jump or hard spl yet for the juno
[Non-Touchscreen Windows Mobile Other] ND4SPD:
Does anyone know if Lokiwiz works for the shadow? We could CID unlock it with that, right?
[Non-Touchscreen Windows Mobile Other] freyes01:
I tried that on my old Wizard and it worked not sure about the Shadow....
[Non-Touchscreen Windows Mobile Other] ND4SPD:
EDIT: I thought it CID unlocked my phone. I'll try something else. I downloaded the vox SYS and OEM folders that contain the rom image. (I'll start replacing all the parts tomorrow. Thanks pixelwix for reminding about the cid unlock and the Vox rom suggestion.
[Non-Touchscreen Windows Mobile Other] brandun_6:
Umm I'm trying to go back to the T-Mobile ROM but I can't seem to load the bootloader. I've tried the Camera+Power key method but that didn't work and the Left/Right Soft key+Home and back button+power key then realsing power key after 2 seconds. Any other way?
[Non-Touchscreen Windows Mobile Other] kron2:
you have to have your phone off then tern it on well holding the camera button
[Non-Touchscreen Windows Mobile Other] brandun_6:
Thanks I don't know what I did different but it worked this time.
[Non-Touchscreen Windows Mobile Other] shadowmike:
Its hard to say because we dont have a ROM image with those drivers installed. ND4SPD Said he had a fixed version made with thewse working but never uploaded it.

Thats why Ive been asking him to upload it so we can actually use this rom on our phones instead of using this POS SLOW t-mobile rom.
[Non-Touchscreen Windows Mobile Other] maxima00se:
ND4SPD, do you have your most recent updates in a new rom up?
[Non-Touchscreen Windows Mobile Other] benjaminries:
XIP files

Hey guys,

Not sure if you got a response from Gonzo yet, but based on http://xdaforums.com/archive/index.php/t-341435.html we might assume that the following files are device-specific:

boot.*, cecompr.dll, ceddk.dll, nk.exe

Someone also advised that you could leave the original device

hd.dll and osaxst0.dll

because "they don't do anything" (?)

I'm guessing you can port the rest? I'm not confident to try this stuff just yet, but I'm researching...
[Non-Touchscreen Windows Mobile Other] freyes01:
I'm stuck in the XIP part. Not sure what to do after that.

We will have to wait for ND4SPD....
[Non-Touchscreen Windows Mobile Other] benjaminries:
ah yes. he's our fearless leader.

on a related policy note: rumours about the shadow 2 having concurrent Neo + WM6.1 Slide interface options are even better reason to defer porting Neo to WM6.1 ourselves-we'll have an easier time just porting the official Shadow 2 ROM when it comes out. Plus scroll wheel issues should be taken care of when T-mo releases that ROM.
[Non-Touchscreen Windows Mobile Other] the_pilot:
Just went thru this entire thread and I just wanted to say all of you all's hard work is much appreciated. I can't wait to see the stable version. Also I have been a lurker on the forum for sometime and I don't think I've seen a rom build this quickly. Thank the lord for spring break!
[Non-Touchscreen Windows Mobile Other] shadowmike:
****... if this shadow 2 has 3g. ill be getting it the dat its avalible. so ill get you guys all of what youll need :)
[Non-Touchscreen Windows Mobile Other] maxima00se:
is there an update?
[Non-Touchscreen Windows Mobile Other] benjaminries:
Pretty sure ND4SPD is a high school student, and his classes are likely getting busy. Patience - once the auto-reset issue is dealt with, he'll probably post an update
[Non-Touchscreen Windows Mobile Other] ND4SPD:
I just got back from our robotics competition in Atlanta. Sorry if I forgot to mention it. You're right that I'm a high school student and I've just missed three days of work. I promise you guys that I will upload soon after I catch up on work and I port all the files except the ones benjaminries mentioned above. I had forgotten to load the XIP partition onto the laptop I was using and couldn't work with it at all when I had downtime.

Just wanted to let you guys know....(internet was $10!?! a day so I couldn't update before). Thank you all for your support up until now. It's a real confidence booster!
[Non-Touchscreen Windows Mobile Other] benjaminries:
So according to http://xdaforums.com/showthread.php?t=331094&page=11, most of the files in the OEM folder are either device-specific or not worth porting. And in the non-OEM folder, "hd.dll, kd.dll, osaxt'.dll's" are device specific in that they are matched with nk.exe.

And according to another post, even device.exe is not device-specific! So basically, don't rely too heavily on what I'm finding. Because I don't completely understand it.
[Non-Touchscreen Windows Mobile Other] ND4SPD:
I'm not sure. One post said that when you make the packages, you should port the whole MSXipKernel folder. The problem is that seems to have the files that would seem the most device specific (device.exe, etc.)

I'm not sure where to go at this point...
[Non-Touchscreen Windows Mobile Other] kron2:
nd4spd I still think you are doing a great job I didn't expect to see the rom these far :)
[Non-Touchscreen Windows Mobile Other] the_matrixx:
ND4SPD, I tried the latest ROM you uploaded last night. Great start! Hopefully you, and everyone helping, can get a stable ROM soon.
[Non-Touchscreen Windows Mobile Other] brandun_6:
He uploaded a ROM last night? And ND4SPD again you're great.
[Non-Touchscreen Windows Mobile Other] ND4SPD:
No, I didn't. It's the previous one and I'm guessing he means that he downloaded last night. Anyways, just wanted to say I think I hit jackpot:

Will port these files immediately! :)
[Non-Touchscreen Windows Mobile Other] kron2:
DA_G post on porting the xip looks very promising :D
[Non-Touchscreen Windows Mobile Other] shadowmike:
thats great news nd4spd still waiting patiently :) great job and thanks again for working on this.
[Non-Touchscreen Windows Mobile Other] phatman81:
the FIRST competition?
[Non-Touchscreen Windows Mobile Other] ha85:
where can I go to download the latest rom? does the powercontrol +omap still work? tzones internet hack? opera 8.5? slingbox and google maps!? sorry!
[Non-Touchscreen Windows Mobile Other] maxima00se:
wait until ND4SPD releases his newest version. It will be soon (crosses fingers) :rolleyes: