yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] xman73:
Encountered Issues

First off, thanks [MENTION=5653319]JT1510365[/MENTION] for PE 10! It has brought new life to my Nexus 7 (2013). Kudos to you and the PE team! :good:

These are the issues I've encountered after flashing the "Latest 4/15 320 Stock dpi build for Flo" using TWRP 3.3.1:

Selecting install TWRP app after flash, causes system to hang on boot at the "G" screen (unchecking it before flashing makes it boot successfully)

PIN lock after booting won't take your PIN until either several tries or after turning the screen off/on over 3 times (could be because the OS is still loading??)

Tried to remove NOVA launcher in TWRP Recovery, mounting System, use File Manager and looked under System but didn't see it in there

That's all I've noticed...so far.

Working:

Netflix build 4.8.5

Microsoft Edge

Magisk 20.4 passes SafetyNet Check (ctsprofile & basicIntegrity), you need to enable "hide" in the settings, it's off by default

Thanks again! :D
[Nexus 7 (2013) Android Development] willows:
Hi i try this rom and i find everytime the screen lock and unlock the device rotate to portrait mode even before i lock the screen i make my device to landscape mode.
[Nexus 7 (2013) Android Development] albaniax:
[MENTION=5653319]JT1510365[/MENTION], can you edit the first post to add the note to NOT let TWRP install the TWRP System-App when flashing the rom?

Because otherwise it bootloops and you have to reflash.

Took me some time to find the post where another user writes the solution

//

I get "Limited WLAN Connection" after Magisk Install - but despite this, internet starts working after a few minutes or a restart once.
[Nexus 7 (2013) Android Development] willows:
Hi, i have some problem with this rom I cannot send and receive any apk file using bluetooth. And I try send file using WiFi direct from my mobile device is error too. Can someone help? And this rom location (gps) still problem, I cannot find change to high accuracy using this rom. Need help how to fix it
[Nexus 7 (2013) Android Development] jhford:
[MENTION=5653319]JT1510365[/MENTION]. Is this still the case? I'm running your 9 version.
[Nexus 7 (2013) Android Development] Behemoth_kat:
The same question here about deb release timeplan: my little daughter’s nexus is on your flo Q release, works like a charm, but my son’s nexus 7 is a deb and currently on LineageOS 17.1 - I’m very unhappy with it
[Nexus 7 (2013) Android Development] JT1510365:
Hey everyone i am sorry about not updating ya'll at the moment there will be no more updates for this rom and my other roms since i am too busy with personal life and my job but i hope to get a new build up soon i just don't know when that will be. I apologize in advance my personal life is just taking away my dev time. Please be patient and understand that my life is more important than our devices. Take care and stay safe:)
[Nexus 7 (2013) Android Development] Behemoth_kat:
Sure, personal things are most important!

thanks for update, stay safe!
[Nexus 7 (2013) Android Development] JT1510365:
just use newest twrp version which is twrp 3.4.X.X from twrp website you don't need to use UA Twrp and you wont see that twrp system app dialog

or use the previous one from twrp 3.4.X.X so it would be twrp 3.3.X.X

the x's are there in replace of the numbers because i dont know the other numbers
[Nexus 7 (2013) Android Development] Smolson:
Error 7

Hi I could not flash anything because of Error 7 message. Even if I flash repartition zip.

I try to use different versions of twrp

What I do wrong?

Please help

Thanks
[Nexus 7 (2013) Android Development] JT1510365:
try wiping and formatting all your partitions a couple times including internal storage and data and make sure you resize system in twrp. Your data partitition is not mounting correctly or at all
[Nexus 7 (2013) Android Development] Smolson:
Hi, after data wipe my Nexus cannot connect to USB OTG even in twrp, and it cant connect to pc via USB. Do anyone of you any solution?
[Nexus 7 (2013) Android Development] kpeters59:
On 2 different units, using the 480 ROM, I keep getting a Play Services Error.

When I look at details, it's about:

This App won't work properly unless you allow Google Play Services request to access the following:

.SMS

to continue, Open Settings, then Permissions and allow all.

It just never works.

I also ran in to the 'Wait a Second' issue doing a Restore of My Cloud Backup that never does anything. Had to skip it.

Thanks,

-KP
[Nexus 7 (2013) Android Development] dave457:
5Ghz router seems to have disappeared. It was fine during setup and then I used 5Ghz to update all the apps on Google Play. Worked fine.

I rebooted into recovery and flashed Magisk 20.4 and now 5Ghz router has gone from the WiFi options and the "saved setup" for the router shows "Not in range" when attempting to connect.

2.4GHz is fine

BTW, any chance of a fix for GPS?

UPDATE

======

I wiped everything and started again. 5Ghz works fine during initial setup and subsequent actions but after a re-boot (power off / power on) all 5GHz access points have gone from available networks. Only 2.4 GHz available now.

FURTHER UPDATE

=============

Switching off WiFi and then switching on again will show 5Ghz networks again and you can connect but it won't auto-connect to previously saved 5Ghz network
[Nexus 7 (2013) Android Development] Trevomader:
Anyone had success making Slimport HDMI output to work?
[Nexus 7 (2013) Android Development] writerauiler:
Put my vote in for a deb version when you can.
[Nexus 7 (2013) Android Development] JWSmythe:
Is there anything I can do to help you with the dev version? I'm not trying to rush or anything.

I've been a Linux sysadmin (and related things) since the late 1990s. I won't claim that I can write drivers from scratch, but I can usually figure out how to fix them. I haven't done much dev on Android, but under it all is the same, under the surface. Since it seems they already have everything in Lineage 17.1, I suspect it shouldn't be too hard for me to figure out what to bring over to yours. I'm not really up for building and maintaining the entire ROM, so I figured it'd be easier to just offer my assistance.

Consider the offer available to whenever you get back to doing these.
[Nexus 7 (2013) Android Development] leMorre:
Thanks so much man
[Nexus 7 (2013) Android Development] me98278:
Hi JT ,

I built the ROM as per the sources mentioned by you . I had to increase the system partition to 1.6 GB . I was able to flash successfully on my flo device but I see the following issues :

1. not able to install new apps or update existing apps from play store.. the apps get stuck in downloading status ..

2. only the back button works.. the home or running apps buttons do not work .

3. clicking on the settings icon from the pull down menu does not work.

4. ROM boots directly to the home screen. The setup flow is not triggered at all.

Is this something that you have seen in the past ? Or any ideas about what can be done to fix this ?
[Nexus 7 (2013) Android Development] JT1510365:
Setup wizard does not work on our flo for pe10. You will need to remove it from the rom sources. PM if you need help with that. As for the other issues they should be fixed and not be a problem if you dont include the setup wizard and you will need the provision apk to be in the rom since setup wizard doesnt work. I dont know if pe10 includes that so you will have to look into it but pm me if you need help with anything.
[Nexus 7 (2013) Android Development] me98278:
Thanks for the prompt reply..Sending you a PM .
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] TuxInside18:
Rom based on Android 10, first release in the next days.:highfive: [IMG="AOSP 10"]https://i2.wp.com/mobilanyheter.net/wp-content/uploads/2019/11/androidlogo-980x653-2-1.png?fit=980%2C653&ssl=1[/IMG]

I'm not responsable for brick, nuclear explosions, these are test builds for now, be careful!
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] mohsin.kadiwala:
Nice joke
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] TuxInside18:
Not a joke dude, I'm working for it
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] mohsin.kadiwala:
Sorry bro...
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] player615:
Hope that it will be available soon. keep working
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] TuxInside18:
I'm working hard about it, I fixed some issues, hope to release in this days
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] TuxInside18:
Ok men, I fixed some issues, I will release in the end of the next week
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] mody446:
Wow.... I can't wait to see my old phone running with Android 10 ?

Thanks in advance ,and keep up the good work.
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] TuxInside18:
Thank you! I think Honor 6X can live for anothers years, unfortunately developers aren't much.
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] Demonyus:
news?
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] biosx32:
Is it hard to make ROM such as this?

What knowledge do you need?
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] karas1que:
Any news about rom?
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] Peam269:
I think it's (maybe) Fake

Or he got some non-fixable Errors...

Sadly! Would've Loved to see Android 10 on this legendary Phone.
[Honor 6X ROMs, Kernels, Recoveries, & Other Develo] theimpulson:
THREAD CLOSED: Placeholder threads are not allowed on XDA! PM me when you are ready with valid download links to reopen this thread.
[Miscellaneous Android Development] trkzmn:
OrangeFox Recovery Project

[IMG="1"]https://image.ibb.co/cTMWux/logo.jpg[/IMG]​

Redwolf fork​

/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/

OrangeFox is FREE SOFTWARE​

Supports Treble, Miui, Custom Roms

Download

:

OrangeFox Recovery R10.1_1

INSTALLATION

:

0. Backup your ROM and all your files

1. Download the OrangeFox zip file to your device

2. Reboot to your custom TWRP-based Recovery

3. Install the OrangeFox zip file as a normal zip

4. The device will automatically reboot into OrangeFox recovery after installation (allow this to happen)

5. Enjoy!

Frequently Asked Questions, MIUI OTA, Troubleshooting, and Sundry Information

:

* See https://xdaforums.com/showpost.php?p=76885728&postcount=3

Credits

* TeamWin - for TWRP

* The OrangeFox Team - for your hard work

* ATG and Dadi11 - for Redwolf

* Kirillmaster4 - for graphics

* z31s1g - for TWRP theme

* All our testers - for your patience and help

FEATURES:

* Supports Treble and non-Treble ROMs

* Up-to-date Oreo kernel, built from sources

* Increased compatibility with TWRP

* Updated with latest TWRP commits

* Built-in support for installing init.d functionality

* Built-in support for installing Magisk

* AromaFM [only for some devices]

* Password

* Support for Miui and Custom ROMs

* Better language support

* Optimized versions of community scripts

* Fox theme engine:

- choice of theme (black, dark, etc)

- choice of color scheme

- choice of splash screen

* Alternative lockscreen

* And many more!

Screenshots - see below

Visit to https://orangefox.tech/
[Miscellaneous Android Development] trkzmn:
30.12.2019 (R10.1) Changelog

- Initial stable release

10.01.2020 (R10.1_1) Changelog

- Fixing some stuff
[Miscellaneous Android Development] Ehsan315:
Nice work
[Google Pixel 4 XL Questions & Answers] subarubdub:
I am struggling trying to get the December update installed. Originally, I unlocked my bootloader, applied the November update, rooted the phone and installed the Floral kernel. Everything was working great. Since then I tried to install the latest version of the kernel and almost bricked the phone right away. I was able to get back on the November update, now I have the November update running, version 10.0.0 (QD1A.190821.014.C2, Nov 2019). I have not rooted or installed a custom kernel. I still have an unlocked bootloader. All I want to do now is install the December update, but when I install this version 10.0.0 (QQ1B.191205.011, Dec 2019, EMEA carriers, T-Mobile (US), Google Fi) - I have a "Google Fi" Pixel 4 XL purchased from the google store.. I can get it to load to the setup screen but I completely use touchscreen ability so the phone is useless.. My question is - Which December update is correct for my phone ? I am thinking it could be the next file under that one - 10.0.0 (QQ1B.191205.012.A1, Dec 2019)... But I am hesitant to attempt flashing a file I am unsure of. I have read that the reason I cant use the touchscreen is because the boot.img is different. I pushed the boot.img and pfpt.img (or whatever it is called) from that factory image and still it did not work. At this point I am almost ready to return it to bone stock out of frustration. Please advise how to verify what the correct file is, or the most simple method to get the update running. Thank you !

TL;DR

Would like december update installed - having a hard time figuring out the correct factory image to use or getting it to work correctly
[Google Pixel 4 XL Questions & Answers] ilal2ielli:
The first build would be correct for you on Google Fi. Don't know why you're having touchscreen issues.

Are you trying to maintain root? If so, flash the factory image with the -w flag removed from the flash-all.bat. Also, make sure you disable Magisk modules if you have any installed, before flashing the factory image.

If you want to start fresh, leave the flag alone and just flash the image.

Edit: Didn't see that you aren't even rooted or anything in your wall of text.

Either way, since you're having issues, best to clean flash and start over. Once your running properly, I'd say read everything in the forums to get a grasp of everything before doing anything to modify the phone again.
[Google Pixel 4 XL Questions & Answers] Homeboy76:
https://xdaforums.com/pixel-4-xl/ho...-10-q-root-t3996969/post80774791#post80774791

In the guide above read Prerequisites, and #1, then do #4 to install factory image, then #9 to root/reroot

If you are reading the guide with the XDA app tap the three dots (on the top right) select open in browser.
[Google Pixel 4 XL Questions & Answers] Badger50:
Go by the recommended factory image based on your carrier found here...https://support.google.com/pixelphone/thread/21769134?hl=en

You may have indeed already flashed the correct one, or maybe not, but it appears you have. Also, have you tried switching to your inactive slot, and flashed it again? I would at least try that before anything else to see if you get your touch input back.
[Google Pixel 4 XL Questions & Answers] subarubdub:
Ive been rooting and playing with android phones since my G1. This is suddenly an issue for me haha, I think it was my platform tools or something.. a few things in my android studio needed updating. Now It is working ! thanks for the help everyone.. :silly:
[Touch Diamond, MDA Compact IV ROM Development] nikitich:
Since Diamond is not available in russia yet we are all waiting for a working russian rom. Finally someone has uploaded it, but also said that Hard SPL for WWE Roms will not work with it for some reason. Can please someone test it and see what is the matter with it. May be it is the newer rom and you will get the same HSPL problem with next wwe roms too.

http://rapidshare.com/files/1243845...Diamond_52.26a.25.09_1.00.25.03_Ship.exe.html

Thanks!

This rom is mainly important for me `cause I need a russian dialer. I have tried pretty much everything i know but still have not managed to put russian letters in the dialer.
[Touch Diamond, MDA Compact IV ROM Development] jockyw2001:
HTC apparently introduced a new region protection. Roms from some particular regions (Russian rom and maybe others) apparently won't run on devices imported from another region.

Do me a favor and enter tricolor bootloader. Then connect with MTTY, press return twice until you see the Cmd prompt and then type the command "readregionalid" (w/o quotation marks). Copy & paste the output here.
[Touch Diamond, MDA Compact IV ROM Development] nikitich:
I have not tried to run this new rom yet 'cause do not want to brick a device. Diamond was bought for me in Hong kong.

Now I am on 137.456.2 Signed for Middle East
[Touch Diamond, MDA Compact IV ROM Development] jockyw2001:
To further research the issue I would like to see the reply of the "readregionalid" command of Diamonds sold in different regions.

Thx in advance.
[Touch Diamond, MDA Compact IV ROM Development] iourioul:
I can do it, but...

I have Diamond from NL, and Russian ROM not work too.

But you know europe code, i think...

Cmd>readregionalid

ReadRegionalID: GPIO value:0
[Touch Diamond, MDA Compact IV ROM Development] jockyw2001:
Thanks.

What happens? Does it not run at all, do you get an error message?
[Touch Diamond, MDA Compact IV ROM Development] acipat:
I have flashed with this rom my diamond. And now, it's reboots every time after writing TOUCH DIAMON and version numbers (radio, rom,...)

I have tried to hard reset device - but the same.

And I cann't flash with a new rom because it doesn't sync to my pc.

Is it possible to flash it with a good rom? Or my diamond is broken at all?
[Touch Diamond, MDA Compact IV ROM Development] LlabTooFeR:
Hold power button and volume down and after that press reset.You will enter to Bootloader mode next step connect device to PC and flash other rom like 1.37.707.1 WWE
[Touch Diamond, MDA Compact IV ROM Development] acipat:
Thanks a lot!

May be somebody have started diamond withs this rom?
[Touch Diamond, MDA Compact IV ROM Development] iourioul:
Reboot after splash screen.

Down+Reset -> 1.37.405.1 WWE... :(
[Touch Diamond, MDA Compact IV ROM Development] cmonex:
this isn't a hardspl problem...

the rom has to be patched
[Touch Diamond, MDA Compact IV ROM Development] jockyw2001:
hi there cmonex,

you are right, or what i like better is to sec unlock the device :)
[Touch Diamond, MDA Compact IV ROM Development] mun_rus:
All will b soon :)
[Touch Diamond, MDA Compact IV ROM Development] cmonex:
you are right too :) long term that's better solution..

btw can we talk on MSN?
[Touch Diamond, MDA Compact IV ROM Development] cmonex:
try: http://rapidshare.com/files/124846060/RUU_HTC_RUS.exe

this is patched and worked when I tested it.
[Touch Diamond, MDA Compact IV ROM Development] DmMc:
Sorry, unfortunately it doesn't work.

Flashing was ok, now WM6.1 Russian loading, but GSM module can't be started. No way to switch it on using both Settings an CommManager.

Tried twice, the same results.
[Touch Diamond, MDA Compact IV ROM Development] walshieau:
our apologies, i didnt test that part as i assumed it would work as the phone booted.

back to the drawing board.
[Touch Diamond, MDA Compact IV ROM Development] acipat:
after russian rom, I have flashed 1.37.456.2 - and my phone becomes to restart, after entering pin code. if I didn't enter pin code- device is working (without gsm). But each time it restarts after I'm entering pin.

I have flashed old rom 1.37.405.1 - the same problem.
[Touch Diamond, MDA Compact IV ROM Development] cmonex:
and you reflashed radio and everything?
[Touch Diamond, MDA Compact IV ROM Development] cmonex:
sorry, indeed forgot to check - we are not really familiar with the rom's default language :D

that is very interesting & will look into this today
[Touch Diamond, MDA Compact IV ROM Development] acipat:
I think so. I've runned:

RUU_Diamond_HTC_WWE-ME_1.37.456.2_Radio_Signed_Diamond_52.26a.25.09_1. 00.25.03_Ship

and i hope that it flashed fully (with radio etc.) my device. Should I do something more to reflash radio?

After flashing first time, my diamond works properly. But in a few hours it hangs up, and after reseting I'v got this problem.
[Touch Diamond, MDA Compact IV ROM Development] cmonex:
can you try flashing a rom with 0.93 radio and see if this persists?
[Touch Diamond, MDA Compact IV ROM Development] LlabTooFeR:
After that device don't wake up.And it extremely slow.
[Touch Diamond, MDA Compact IV ROM Development] cmonex:
you mean it will only wake up if you press the reset hole?

very strange things; do you have an MSN address so we can check this out more closely. please send me your contact info in a PM. (ICQ/Yahoo is fine too.)

acipat too, please let me know in a PM if you have MSN
[Touch Diamond, MDA Compact IV ROM Development] acipat:
I've flashed with old radio (0.93) and almost the same problem- it didn't turned off after entering pin, only after I make a call, on a second second it is turned off.

And it is impossible to connect to internet via gprs/edge. With a newer radio it turned off after entering pin.

msn: my_xda_developers_nick @ hotmail.com

PS: football, you have the same problem?
[Touch Diamond, MDA Compact IV ROM Development] abbot33:
Could you please post here a result of flashing? I wonder if Russian firmware can work properly with HTC diamond device.

Thaks in advance!
[Touch Diamond, MDA Compact IV ROM Development] cmonex:
conclusion after talking to both, apparently acipat's case is isolated, hardware may be damaged in his case. Football reports that the russian rom with my patched nk.exe, but otherwise unmodified, will not let you turn the radio on.

you can use the rom to take the russian MUI from it & XIP (except nk.exe, that wasn't tried), and the rest can be based on WWE imgfs, and then radio in such a cooked russian rom works fine.

but I'll want to find out which module causes the problem. in any case, all the protections are OS level, not radio level. nothing very extraordinary :)
[Touch Diamond, MDA Compact IV ROM Development] abbot33:
Thanks for the information!
[Touch Diamond, MDA Compact IV ROM Development] mun_rus:
2ALL

Enjoy :)

Test ROM 1.37.411.1 RUS

http://4pda.ru/forum/index.php?showtopic=83618

Next release will b with some bugfixes :)
[Touch Diamond, MDA Compact IV ROM Development] lordaris:
Any other infor on this..

By the way the site does not seem to work for me..
[Touch Diamond, MDA Compact IV ROM Development] Montoi132:
I am having the same problems with the Russian Diamond. Trying to flash the Russian device to English. I have followed all the steps and have even tried different ROMs. I need the original RUS rom to flash it back and see if this will fix the phone (it wont turn on). I may be misunderstanding the solution here. Other ROMs (non RUS) seem to crash the device on startup during the TouchFlo instruction video. Any help would be appreciated. Thanks in advance.
[Touch Diamond, MDA Compact IV ROM Development] Nosferatos:
Original RUS rom here http://rapidshare.com/files/1243845...Diamond_52.26a.25.09_1.00.25.03_Ship.exe.html
[Touch Diamond, MDA Compact IV ROM Development] aleme:
RUU_Diamond_HTC_RUS_1.37.411.2_Radio_Signed_Diamond_52.26a.25.09_1.00.25.03_Ship

can't use this utility due incorrect identificator of producer

HDa3-DJCP5567-HUEbcF6>-DJCP55670

so, rom or phone has to be hacked before update.

who can help????

I bought HTC Diamond P3700 at Helsinki Vantaa airport's Duty free
[Touch Diamond, MDA Compact IV ROM Development] actinide:
No radio in WWE

Same thing here. Tried to flash a Russian Diamond to WWE ROMs (Elite 2.0, bElite) after patching it with Unsigned-Hard-SPL-Diamond-OliNex, but the cellural module stops working and the system constantly crashes (gwes.exe, device.exe errors). bElite ROM could not even pass the boot screen. I guess there's some type of protection in place on the device.

Any ideas what can be done? I really want to get these ROMs working ((