yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Johnn78:
When I went to Android 13 then I had ES File Explorer which didn't have access to Android/Data. Then I found ES File Explorer v4.4.0.2.1 which has the ability to have access to Android/Data but it hasn't the ability to write (via copy - paste) to Android/Data. This problem doesn't exist only to ES File Explorer but in all File Managers which I have used like File Manager+, File, MiXplorer, Xplore etc... The MiXplorer which can write to Android/Data not be done via copy - paste but via some trick by splitting screen and drug-drop the file which is some intermediate solution. If it is found some solution which can work the copy - paste to Android/Data then this will work to all File Managers which means that the problem isn't that the ES File Explorer is deprecated. May exist some magisk module or lsposed module which deactivate the SAF (Storage Access Framework) permission in which wasn't enabled in Android 12.
[Google Pixel 6 Pro] Strephon Alkhalikoi:
ES File Explorer, as I said in my previous post, no longer works with current versions of Android. This is because there is no one working on its code. No one to fix bugs when they appear. No one to ensure root functions continue to work. No one to enable proper access to Android/data.

There are file managers out there that are not ES File Explorer, and while you have tried some, you've not tried them all. I tried Root Explorer just now and had no problems copying files to /Android/data in internal storage; no tricks or workarounds needed. So I stand by my statement. Especially as the file manager I now use doesn't have this issue.
[Google Pixel 6 Pro] heikkiap:
As the OP had problem with Foldersync in selecting folders in Android/data, I have not found a solution. I can access data folder using X-plore and I can even copy the path of the desired folder, but in Foldersync, there is no way to paste the path, but you have to select the path step by step, and step to data folder is not allowed in Foldersync.

So, any one having solved the problem? As this is not working in the latest Foldersync version, seems that developers have not yet solved it either.
[Google Pixel 6 Pro] falciatrice10:
Mixplorer will show the content of Data or Obb but can't open it.

The only way is root
[Google Pixel 6 Pro] Coldblackice:
What if you try it in tangent with Shizuku?
[General Questions and Answers] Wind Dancer:
I have Hard SPL and UDK Syrius beta 2.9 on my Touch Diamond. It was working fine for a couple of days then he came out with beta 3 and I was going to flash it and my diamond was not connected to Activesync so I got an error message. I then cleared storage and the device would not go past the splash screen and the radio version etc. on the splash. i have tried to hard reset several time with no luck. I have been searching around this forum for some time and I can not find any info on what to do. I have seen what to do if it won't come out of bootloader and even downloaded mtty.exe. but if activesync doesn't connect what can I do? Does anyone know where I should be looking?

Thanks in advance for any help.
[General Questions and Answers] Wind Dancer:
Sure glad we have a dedicated question and answer section

"This Forum is dedicated to helping you get the answers you need ! Any question related to Pocket PC's, Smartphones, and the Themes and Applications that accompany them, are welcome in this thread. This section is not dedicated to a specific device or specific topic, but to any and all general questions in the Pocket PC and Smartphone world. So feel free to seek the help you need here."

thanks for all the help!!
[General Questions and Answers] Junner2003:
Why don't you post your question in the DIAMOND section?
[General Questions and Answers] DaveShaw:
No need for the smart ass comments :) a *bump* would have sufficed.

Have you tried re-flashing the ROM from the bootloader?

Ta

Dave
[General Questions and Answers] Wind Dancer:
I can't establish an Activesync connection. I don't know of any way to flash without that. I tried once, put phone into bootloader manually and started flash, got error could not connect to device.
[Lenovo P11] IndigoHD:
My device was at the latest original chinese firmware with a locked bootloader.

I unlocked my bootloader and then used the extracted boot.img from ZUI_13.0.346 (like in the guide), after patching with magisk, to root my device.

Now its stuck in bootloop. Can anyone here help me?

I followed this guide: https://xdaforums.com/t/root-lenovo-tb-j716f-c.4350037/post-85955341

EDIT: A piece of information missing from that guide was that the "boot.img" absolutely needs to be the same version as the tablet itself. I used the one provided by following the guide and thats why i got a bootloop.

i reflashed ZUI13 via Qfil, installed TWRP recovery and dumped my own boot.img that way. After patching that with Magisk everything worked perfectly.
[One (M9) Q&A, Help & Troubleshooting] Ichbinkeinroboter:
I have the same problem as described several times in this (HTC M9 Boot mode errors - Failed to boot to recovery mode) thread. Thanks for this, it helped me and I was able to finally get the device working. However, this version of aicp (aicp_himaul_p-14.0-UNOFFICIAL-20181030.zip) is out of date and incompletely developed - as quasi unusable. Because I can only install a twrp-3.0.0-0-hima.img, I cannot install more recent versions.

I'm surprised because I've already been able to flash an HTC One m9 without any problems ?!

How can it be that the m9, which is younger than the m8, cannot use a newer TWRP ?

Is there an alternative to TWRP

Is there a functional way to fix the problem ?

Do you know another way to install a current aicp or lineage ?

Or is there another ROM that I don't know about ?

I can not express it better without guidance ...

I appreciate any help ...
[One (M9) Q&A, Help & Troubleshooting] Ichbinkeinroboter:
Hello all,

I am already despairing and hope to find help here.

I want to make a firmware update of my htc m9, but can not cope with the variety and the resulting error possibilities.

Here is the info about the device:

Unlocked

htc_himauhl PVT S-on

LK-1.0.0.0000

Radio-01.04_U11440601_71.02.50709G_F

OPenDSP-v29.2.6-00492-M8994_0702

OS-2.10.111.6

Oct. 14 2015, 15:43:14

fastboot getvar all:

(bootloader) kernel: lk

(bootloader) product: htc_himauhl

(bootloader) version: 1.0

(bootloader) imei: 357226062546916

(bootloader) version-main: 2.10.111.6

(bootloader) boot-mode: download

(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F

(bootloader) version-bootloader: 1.0.0.0000

(bootloader) mid: 0PJA10000

(bootloader) cid: T-MOB101

all:

Finished. Total time: 0.006s

The device is unlocked and there is a TWRP on it (Vers. twrp-3.0.0-0-hima.img) It is not possible to install a more recent TWRP. Probably because the firmware is too old.

Is there someone here who can kindly support me and help me ?

It would be very important to me not to destroy the device, which is why I no longer dare without help.
[One (M9) Q&A, Help & Troubleshooting] platinumthis:
Download twrp.img and flash over twrp recovery. Select IMG and flash the new twrpXXX.img
[One (M9) Q&A, Help & Troubleshooting] platinumthis:
Download twrp.img and flas over twrp recovery. Select IMG and flash the new twrpXXX
[Redmi Note 10 Pro] ImHorizon:
Hello, is there any ROM that has the ability to remove the Google Searchbar that appears at the bottom of the screen? I really like Pixel Launcher but I don't use it and I want to remove it, I've tried PixelOS and it doesn't appear to have the option to remove the searchbar.
[Redmi Note 10 Pro] cocopipou:
I don't know if there is any Rom allowing that.

Personnaly I'm using Nova Launcher Prime (from the playstore) which contains the feature You want to have.
[Redmi Note 10 Pro] nale988:
You can also use Lawnchair launcher (www.lawnchair.app), it's a fork from the Pixel Launcher, but you can customize this detail. And a lot more.
[Redmi Note 10 Pro] ImHorizon:
I've tried this and looks cool, but I can't use gestures (swipe up to return home, swipe from side to go back), I think I'm looking for a ROM that uses Pixel Launcher and has the searchbar disabled, or just for another launcher similar to it, I've saw that ArrowOS uses Quickstep, and is really like Pixel Launcher without the bar, but it lacks a lot of customization, I think I'll stick to MIUI for now
[Redmi Note 10 Pro] nale988:
If I recall right, the Quickstep is a Magisk module for allowing the launcher to access the running apps. You should install it along with the Lawnchair.

Not sure about the gestures, I am using them (with PixelOS) and I have no issues, even advanced stuff (long back, swipe down for one-handed mode etc).

I did not try to use it with MUIU due to issues with the ROM itself.
[Redmi Note 10 Pro] ImHorizon:
I guess I'll give PixelOS a try once again, install Lawnchair and see how it goes, thanks
[Redmi Note 10 Pro] nale988:
I've also tried Pixel Experience and no issues.
[Xiaomi 12X] mtx4:
I'm new to xiaomi world, I just received this minor update today, but there are few bugs and lags, I want to revert back.

Both Roms are stock Stable Global EEA.

I don't know how to dowgrade, because recovery zip and update app not work, unable to downgrade.

Can you show me a complete guide to flash that firmware? I need unlocked bootloader?

Anything in particular I have to know?
[Xiaomi 12X] NOSS8:
1/Unlock the bootloader

https://c.mi.com/thread-1857937-1-1.html

https://en.miui.com/unlock/index.html

then after 168 hours:oops:

Use this tool(Read carefully)

https://xdaforums.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
[Xiaomi 12X] maRRRco89:
Thank you so much.

This new firmware is a bit laggy.
[Xiaomi 12X] NOSS8:
Use Xiaomi Eu ROM better than stock

https://xiaomi.eu/community/
[Nothing Phone 1] King_lilrowrow:
OrangeFox Recovery

ℹ️ Information

Status: Experimental

Version: 12.1

Release Date: 2022-08-23

Source Code:

View Source on GitHub!

​

⬇️Download:

Latest Version Download

📲 Installation on Nothing Phone 1:

- Download the latest OrangeFox build from above

fastboot flash boot <path-to-orangefox-img>

📚 Documentation (FAQ):

OrangeFox Wiki

📒 Source changelog:

Commit History on GitHub

V 0.1-EXP KNOWN ISSUES:

- Does not boot on global devices (EEA ONLY)

- Does not boot on devices updated to stock 1.1.3 FW

V 0.2 -EXP KNOWN ISSUES:

- None reported!
[Nothing Phone 1] King_lilrowrow:
(UPDATE 30/08/22)

- V 0.2-EXP RELEASED

- ADDED TWRP CRYPTO MODULE

- BOOTING SHOULD BE FIXED NOW ON BOTH EEA&GLOBAL VARIANTS

- CAN INSTALL ON ANY VERSION OF NOTHING OS (AS LONG AS ANDROID12 BASED)

- TOUCH INPUT IN RECOVERY SHOULD BE FIXED
[Nothing Phone 1] Sib64:
Nice to see the first recovery (even in development) for the NP1.

Well done (y)
[Nothing Phone 1] AntoXik72:
Fantastic! Thanks for your hard work! Any SpacewarEEA planned?
[Nothing Phone 1] King_lilrowrow:
Reserved

Both global and EU already supported
[Nothing Phone 1] AntoXik72:
Stuck on Nothing logo then for me
[Nothing Phone 1] King_lilrowrow:
What version of NothingOS was you on before flashing? (Recovery is built with 1.1.2 kernel)
[Nothing Phone 1] sh4tteredd:
good job man! good to see first recovery!
[Nothing Phone 1] AntoXik72:
I'm not even sure to have one at the moment... Stuck on fastboot, can't flash any partition that's linked to super partition (system, product, vendor,...) I will try again with what can be flashed of the 1.1.2 update and tell you back
[Nothing Phone 1] King_lilrowrow:
Remember spacewar doesn't have a "super" partition
[Nothing Phone 1] HofaTheRipper:
are you sure?View attachment 5694379View attachment 5694383
[Nothing Phone 1] AntoXik72:
Tried with what I can flash from payload.bin (everything except system, product, vendor, system_ext and odm), stuck on nothing logo again..
[Nothing Phone 1] King_lilrowrow:
Very sure, device is using vA/B, if the partition is there it isn't mounted/used.

Device is also using the newer (Android 12) RAMDISK_IN_VENDOR_BOOT, recovery also needs modules loaded into vendor_boot now to work correctly
[Nothing Phone 1] King_lilrowrow:
Some imgs can only be flashed in fastboot while others in fastbootd.

If your struggling to find which ones, use the nothing phone one tools found on XDA to reflash all partitions
[Nothing Phone 1] HofaTheRipper:
ok 🤷‍♂️...
[Nothing Phone 1] pankspoo:
If you are flshing some partaioms using fastbootD mode then it has super partations
[Nothing Phone 1] AntoXik72:
I already tried everything on the forum, including fastbootd, the tool from sh4tteredd, even tried things like fastboot create logical partition, fastboot erase, nothing is working at the moment
[Nothing Phone 1] ayed78:
change slot and flash
[Nothing Phone 1] vinayak.s19:
I can confirm that it has a 6 gig super partition.
[Nothing Phone 1] AntoXik72:
Already tried, same result
[Nothing Phone 1] HofaTheRipper:
Stuck on nothing Logo if i try to boot it (SpacewarEEA 1.1.3)
[Nothing Phone 1] King_lilrowrow:
I'll get a version built with 1.1.3 prebuilt kernel added and uploaded hopefully by the the end of the day, I'll update the post to let people know the current one only supports 1.1.2
[Nothing Phone 1] hahagu:
Welp, super partition is fxxed for me now too 😅

not EEA, so don't even have something to restore to.
[Nothing Phone 1] sh4tteredd:
try to use my tool, maybe you're still able to flash. https://github.com/sh4tteredd/nothing-phone-1-tools
[Nothing Phone 1] hahagu:
Yeah, no luck.

Gives me an error about not enough to resize or something on b

Will try to come up with a log.
[Nothing Phone 1] sh4tteredd:
also try to wipe from recovery
[Nothing Phone 1] hahagu:
Will do :)
[Nothing Phone 1] hahagu:
nothing phone(1) fastboot flash by @sh4ttereddDON'T flash a nothingOS versio - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com

Here's a log of what happens :)
[Nothing Phone 1] hahagu:
And this unfortunately achieved nothing ;(
[Nothing Phone 1] sh4tteredd:
try to reboot into fastbootd from fastboot using

fastboot reboot fastboot

and then write

fastboot wipe-super

.

After that try to flash with my script
[Nothing Phone 1] hahagu:
fastboot wipe-super

returns:

fastboot: error: ANDROID_PRODUCT_OUT not set
[Nothing Phone 1] sh4tteredd:
lol I forgot that you need the empty image, if it's possible I'll send it asap
[Nothing Phone 1] hahagu:
Thanks :)
[Nothing Phone 1] hahagu:
maybe flashing EEA, and overwriting it with Global would work?
[Nothing Phone 1] sh4tteredd:
can't do that much, the easiest thing that you can do is

imo it shouldn't make any problem, just try to not boot into system like

fastboot reboot fastboot
fastboot flash super super.img
fastboot reboot bootloader

and run my script
[Nothing Phone 1] hahagu:
Well, that's not any better..

nothing phone(1) fastboot flash by @sh4ttereddDON'T flash a nothingOS versio - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com
[Nothing Phone 1] sh4tteredd:
wipe from recovery

re flash the super backup using:

fastboot reboot fastboot
fastboot flash super super.img
fastboot reboot bootloader

flash using my script

wipe from recovery

return into fastboot and write

fastboot --set-active=a
fastboot reboot
[Nothing Phone 1] hahagu:
Okay, that'll do the job!

Will have to test if it works all right :)

Thanks for the help!
[Nothing Phone 1] King_lilrowrow:
(UPDATE 30/08/22)

Sorry for the delay in new builds! But they should be a bit more frequent from now on. Here's today's build available now.

- V 0.2-EXP RELEASED

- ADDED TWRP CRYPTO MODULE

- BOOTING SHOULD BE FIXED NOW ON BOTH EEA&GLOBAL VARIANTS

- CAN INSTALL ON ANY VERSION OF NOTHING OS (AS LONG AS ANDROID12 BASED)

- TOUCH INPUT IN RECOVERY SHOULD BE FIXED

Download:

GitHub Releases

ALL ISSUES REPORT THROUGH MY GITHUB ISSUES PAGE!!!

GitHub Issue Reporting
[Nothing Phone 1] AntoXik72:
No boot on mine after flashing, flashed back stock boot, all is booting fine
[Nothing Phone 1] King_lilrowrow:
Yep someone just reported this to me, already running a new build which should sort it 👍
[Nothing Phone 1] hahagu:
Hey, just a question,

have the builds we are getting been tested before release?
[Nothing Phone 1] King_lilrowrow:
So yeah, some do some don't. I have 2 people that have EEA devices, no testers for Global but apart from a different code name they're the same internally.

That being said I have a active build environment where I'm changing a lot regularly so a build they test I might change one thing and release it and it no longer boots etc etc..

Same happened with today's release. I have the device personally as well but sometimes things pop up between builds and development.

The main thing is testing so nothing totally bad happens, which is always done on every build, this device is getting known by myself and other developers to be a pain to work on as well as using 3rd party software on. For some the timestamp issue prevents going back to stock but can be fixed with flashing an older stock firmwares vendor_boot and boot image.

The other issue is one of the slots failing to allow you to flash to it, which you need to flash a blank super.img to or erase and recreate the partitions with the correct sizes.

To conclude, people should be aware this device is VERY easily soft bricked (you can get it back working but you'll need to try a few ways first) and that only people with a GOOD understanding of the underlying fastboot(d) systems, partitions and Android itself should attempt to use custom recoveries or ROMs until we get everything more stable!
[Nothing Phone 1] hahagu:
Kind of hard to do without an empty super.img, but it is doable.

That said, shouldn't the installation be handled by OrangeFox itself, and not have a prebuilt kernel embedded?

And I also believe buildvars are missing from the manifest.
[Nothing Phone 1] King_lilrowrow:
Prebuilt kernel was only being used due to lack of a stable OSS kernel for spacewar and bits missing from the source Nothing provide.
[Nothing Phone 1] ZwoelVi:
Do I understand correctly, this recovery does not yet work with Firmware version 1.1.3?
[Nothing Phone 1] hahagu:
Doesn't even boot, for now.
[Nothing Phone 1] ZwoelVi:
I hope this project will be further developed, miss the function to make a full backup of the whole system like in twrp. I would also like to offer my support As for the translation, or donate some money to keep the motivation going 😄 Of course, it is not self-evident that someone sacrifices their free time to program something like this . It's good that there are people like that @King_lilrowrow 💪🏻Unfortunately I can't code, but I'm sure I can help in other ways
[Nothing Phone 1] King_lilrowrow:
Great progress has been made, working on both lineage 20 (A13 based) as well as OrangeFox and TWRP.

Will share more soon.
[Nothing Phone 1] Pho3nX:
Problem is not always the recovery himself on the recents devices but above all the encryption.

If encryption key is not recognized/decrypted, you can't using properly (mount system/data partitions) or make a backup (even if you can backup/restore partitions, no boot).

On my previous Mi 11 Xiaomi i used adb sideload during 1 year for install Custom/AOSP roms, no proper Custom Recovery available...
[Nothing Phone 1] ZwoelVi:
Back then, I always used twrp mainly to make a full backup of the system. I miss this function
[Nothing Phone 1] riccardorossi64:
ERROR 404 (link download page, not working)

Thanks to post a new link or directly the last OrangeFox file
[Nothing Phone 1] AntoXik72:
Thanks to read the thread.
[Nothing Phone 1] riccardorossi64:
There is TWRP for our Nothing Phone?
[Nothing Phone 1] ZwoelVi:
no I meant on my previous devices
[Nothing Phone 1] realend:
Why is the file not accessible?
[Nothing Phone 1] NightMean:
Any possibility to provide an updates on this? The Github repo is currently down.
[Nothing Phone 1] ZwoelVi:
does the recovery work now? currently use the firmware version 1.1.4
[Nothing Phone 1] vpnsentry:
Can someone send me the stock splash.img from the OS after its installed, I want to see if the encryption and encoding is the same as OnePlus and Oppo, I just created SplishSplash which allows you to insert and modify the boot logos...

Thank you!
[Nothing Phone 1] HofaTheRipper:
splash_backup_2022-12-12_07-37-09.img

drive.google.com
[Nothing Phone 1] JazonX:
Can I get rid of the Boot error message ?

Can you link me to the tool if so?
[Nothing Phone 1] vpnsentry:
Unfortunately no, this is only for the bootloader logos, I have the files to get rid of the boot warning message in the binary and repack I just have no time at the moment to rewrite the firmware.
[Nothing Phone 1] vpnsentry:
Thank you! I will give it a try this evening and let you know if I was successful!
[Nothing Phone 1] vpnsentry:
Yea no love, it got the encoding but the headers are failing, can you send me LOGO_a as an img?
[Nothing Phone 1] HofaTheRipper:
there is no LOGO partition 🤷‍♂️
[Nothing Phone 1] Ofdas23:
@King_lilrowrow

Hey, will this work even when I have a custom rom installed?
[Nothing Phone 1] Pho3nX:
TWRP is ready, just wait a little bit. For sure it will be usefull for the Orangefox dev, i hop have the choice between both recovery soon !
[Nothing Phone 1] vpnsentry:
Hmmm it is the same encoding as Oppo which makes sense since the Nothing1 was designed by the Founder of OnePlus and Oppo manufactures OnePlus....
[Nothing Phone 1] Ofdas23:
Thank you a lot for the help and replies man, you are so so kind, it makes me happy :3
[Nothing Phone 1] Valery621:
Is there a version for 1.1.7?
[Nothing Phone 1] NightMean:
Does anyone have the v0.2 download link? I doubt this is still in development.
[Nothing Phone 1] SzymcioYa:
nope, tried seeing if it was archived. it wasnt
[Nothing Phone 1] invincible64:
deleted
[Nothing Phone 1] Wishmasterflo:
Is there a working TWRP or Orangefox for this phone now? And is there a device tree for that still existing somewhere to look at?

All this new vendor_boot as recovery is really a mess and doing things much more difficult in regards of building a fully working custom recovery for new phones.

I have a Google Pixel 7a now as second phone and tried to build Orangefox for it but never had anyh luck to boot it. It always is stuck at the "Google" logo.

And this phone is using vendor_boot as recovery as well. :cautious:
[Nothing Phone 1] elderwolf123:
Orange fox no, TWRP apparantly but it was never released and there has been nothing new in regards to it
[Nothing Phone 1] NightMean:
Recently I found that some devs started to work on OrangeFox for Phone (1) again. Source it's on Github.

I'm not going to share the flashable img file. It can be found on the internet for those willing to flash something from unknown source :)

GitHub - Maitreya25/OFox-device_nothing_Spacewar

Contribute to Maitreya25/OFox-device_nothing_Spacewar development by creating an account on GitHub.

github.com
[Nothing Phone 1] 续rio:
Mod edit - translated by https://translate.google.com/. Oswald Boelcke, Senior Moderator.

Hello, do you still have the recovery.img of nothing phone1?

*********************

你好，还有nothing phone1的 recovery.img吗？
[Tilt, TyTN II, MDA Vario III General] digitalextremes:
I have an issue with my Kaiser, when I use my finger and hit 1 on the dialpad, 9 gets pressed even through they are not even next to each other. That happens with other keys as well, I just gave 1 and 9 as an example.

I have done reflashing with all kinds of roms, calibrated the screen number of times, but the issue doesn't go away, only goes away if I use a stylus.

Does anyone know precisely which component in the hardware could be defective that I can replace? someone mentioned digitizer or something like that?
[Tilt, TyTN II, MDA Vario III General] pyraxiate:
Scratched my previous post, not the issue.

Try downloading a new dialer. There are tons.