yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] 00p513:
Wow, a new ROM for grouper in 2021! Keep up the good work guys!
[Nexus 7 Android Development] V'Pier:
I've been digging through XDA looking for a rom to install on my ancient Grouper (2 of them actually), I'm hoping this will do the trick, I'll try it on one first then the other.

Not sure what other Grouper roms out there are noteworthy in Aug 2021, obviously one important detail is it being able to run smoothly rather than backwards cuz of too much bloat.
[Nexus 7 Android Development] bartman350:
What version of TWRP is recommended? I used the one that was already installed: 3.1.1-0

and it does not boot DOS. Did anybody have success running this ROM?

edit: tried with TWRP 3.6.0_9-0 also without success. After using divest recovery it comes up. So what about "This is one of the few devices supported by DivestOS that recommends the use of TWRP" ?
[Nexus 7 Android Development] SkewedZeppelin:
If you accidentally relock with TWRP it is slightly less likely to brick.

Relocking with DivestOS recovery is broken on grouper and will render device irreversibly bricked.

If you are sure to never attempt to lock grouper, then DivestOS recovery *is* recommended.

I can't really test anymore for grouper as mine managed to die a slow death, I suspect the NAND wore out.

But it did boot the November build just fine.
[Nexus 7 Android Development] michnixweiss:
Old thread, but hoping for help.

I tried flashing DivestOS - comming from Los with TWRP without success. So I wanted to use the DivestOS recovery. After flashing (shown successful) I ran into bootloop only showing:

Failed to mount /cache (invalid argument)

Can't mount /cache/recovery/last_local

Found no key combination to get into recovery nor fastboot again.

Any hints?
[Nexus 7 Android Development] SkewedZeppelin:
It doesn't sound like you flashed it?

And TWRP is STRONGLY recommended for this device.

If you accidentally lock grouper with AOSP/Lineage/Divest recovery this device will perma brick.
[Nexus 7 Android Development] michnixweiss:
Thanks for the reply.

The device was and is unlocked - I got the open lock symbol at the bottom at startup.

But then there is a laying down android shortly displayed and the errors like described are shown.

I read, that fastboot is a low level function and should work even recovery is damaged.

Is there another way to get this mode started? Any hardware hints, buttons or so? I also read something about unplugging the batterie to get some Mode startet, but only for Stock. Whats the fourth button for (when opening the backcover there are four buttons, but the cover only uses three - vol + / - / pwr)?
[Nexus 7 Android Development] SkewedZeppelin:
I never figured out the fourth button.

My grouper's nand died recently and I don't remember the keys either.

I do know grouper still works on the latest update, was confirmed by someone in the chat recently.
[Nexus 7 Android Development] michnixweiss:
@SkewedZeppelin does the grouper support edl mode? If yes do you know how to enter it?
[Nexus 7 Android Development] SkewedZeppelin:
EDL is Qualcomm specific. Grouper is a NVIDIA Tegra device.

It has a distinct recovery mode and is only functional if you first dumped the necessary keys.

AndroidRoot.Mobi - Tegra3 Guide: nvflash NEXUS 7 (and Transformer Jellybeans)

It is highly unlikely you bricked it by simply flashing the recovery.

Only if you attempted to lock it or flashed the recovery immediately after unlock without reboot would it be bricked.

To be clear, if you unlocked and immediately flashed the recovery without a reboot in between, it is destroyed.

That is not a DivestOS issue, but a fatal flaw in the bootloader's handling of the unlock state.
[Nexus 7 Android Development] michnixweiss:
THX, i'll try nvflash.

But that's what I did - but not trough fastboot, I flashed it from TWRP.

Unlock the device is years ago. I flashed several roms with and without gapps, got microG working and now wanted to test DivestOS with BitGapps.

I also don't think its an DivestOS issue. Maybe something went wrong while flashing or download (I never check hash, but also never had any problems... till now).
[Nexus 7 Android Development] michnixweiss:
... so I tried

- How to unbrick Nexus 7 without blob.bin

- tegra30_debrick

but my Nexus is not recognize as ADB, fastboot nor APX device.

So I think the expense from now on is bigger than it's value.

Thanks for the support.
[Samsung Galaxy S21 Ultra] fa1rid:
Can I flash SM-G9980 (Taiwan BRI) with SM-G998B firmware (any region/csc) or it must be from same model?

Also my model in the network mode doesn't show:

2G Only

3G Only

etc...

it shows only:

3G/2G (auto connect)

4G/3G/2G (auto connect)

etc...

In other words I would like to force network mode to 2G only which I saw available only in the SM-G998B

Thanks!
[Samsung Galaxy S21 Ultra] mishufac:
No. One is Snapdragon G9980 and other is Exynos G998B
[Samsung Galaxy S21 Ultra] mpore14:
No.
[Samsung Galaxy S21 Ultra] H4T3M4CH1N3:
Mine has the ability to select 2G only. I suggest you try changing CSC to TGY.

View attachment 5326985
[Samsung Galaxy S21 Ultra] fa1rid:
Yours is TGY (Hong Kong)?
[Samsung Galaxy S21 Ultra] Riyal:
Mine is also TGY and it has 2G Only.
[Samsung Galaxy S21 Ultra] fa1rid:
Oh that's interesting guys. I will change my CSC to TGY then. I can do that by flashing the TGY firmware using Odin right?

Does using the HOME_CSC changes the CSC or I need to wipe all the data?

And after that OTA will work fine?

Thanks!
[Samsung Galaxy S21 Ultra] fa1rid:
So can I use Odin to flash a new firmware to change the CSC? I want to change from (Taiwan BRI) to (TGY Hong Kong). Please advise, do I need to wipe all data on phone?
[Samsung Galaxy S21 Ultra] H4T3M4CH1N3:
I told ya on the other thread that I did change it. What part are you not understanding?

You'll need to flash HOME_CSC if you want to prevent wiping data on your phone.
[Samsung Galaxy S21 Ultra] fa1rid:
I tried to flash the TGY using the HOME_CSC and Odin showed pass and then device rebooted, but nothing changed. It's still showing BRI.
[Samsung Galaxy S21 Ultra] SoIomon:
just try but make a backup first
[Samsung Galaxy S21 Ultra] fa1rid:
try what? Anyone has an exact method he followed and succeeded? Just please confirm the exact steps you did. Thank!
[Samsung Galaxy S21 Ultra] SoIomon:
try flashing the firmware if it fails then go to recovery mode using TWRP. before flashing, back it up using TWRP
[Samsung Galaxy S21 Ultra] fa1rid:
Sorry it's not clear, can you please explain?
[Samsung Galaxy S21 Ultra] SoIomon:
you first need to backup your device using Team Win Recovery Project (TWRP). View attachment 5336977

after backing it up, go to install and try flashing the firmware.
[Samsung Galaxy S21 Ultra] fa1rid:
This app requires root and doesn't do the job. There no s21 on the list of devices even.
[Samsung Galaxy S21 Ultra] fa1rid:
Is there anybody here who can help?
[Samsung Galaxy S21 Ultra] mpore14:
I tried flashing the Home_CSC with May firmware and it didn't change it. I discovered I'm also on BRI firmware. I haven't tried it but you can try to flash the whole TGY (Hong Kong Firmware) using odin.

Edit:Beware that this will perform a factory reset on the device
[Samsung Galaxy S21 Ultra] rayw_xda:
You can use my app Samsung Band Selection to force those options. Click on "more network settings", "advanced", and then "preferred network type"
[Samsung Galaxy S21 Ultra] fa1rid:
This was helpful and working. Thanks!
[HTC Cavalier] cruzzmz:
1stly i would like to give a big huge thanks for

everyone who hv helped me in reviving back my cava

esp to jockyw2001 (God bless)

So for anyone else who was stuck at 1st splash screen like i did (the dopod screen). Here is the deal

Note: Tis only work with the Hard SPL

HOW TO

-----------------------------------------------

1. Download mtty

2. Take out ur microSD

3. Disable USB conn on ActiveSync

(Right click on ActiveSync icon on pc --> Conn setting --> uncheck "Allow USB conn")

4. Enter bootloader (3 color screen)

(Press Camera + Voice Rec + Power)

5. Run mtty

6. Type : CMD>task 32

(if it return "Level=0" u r set to go)

7. CMD>info 8

(give info on how many bad blocks)

8. CMD>task 32

9.CMD>task 2a

(let it run ... it will check & repair bad blocks)

10.CMD>task 28

(output:

Storage format start

Write Nand Success

dwBlockToWrite = 13

Storage start block: 509

Storage Total block: 515

Total Bad Block in CE: 0

NeedToEraseBlockStart: 522

NeedToEraseBlockEnd: 1024

Storage format success)

11. Flash back modded shipped rom (OS only) HERE

12.Keep ur finger crossed

Hopefully tis will help

More info on mtty commands
[HTC Cavalier] cruzzmz:
mod can u make this thread sticky

thanks
[HTC Cavalier] oldsap:
wow this will make us feel a lot safer when flashing ROMs. Thank you.
[HTC Cavalier] cruzzmz:
hope so :D since it took me a while to revive back my cava .... thx to a certain person though ;)
[HTC Cavalier] ibeqa:
Good to hear that your device did not break (otherwise you would had an expensive brick :) )

Cheers
[HTC Cavalier] cruzzmz:
yup ... a very expensive paper weight ;)
[HTC Cavalier] tiger75:
upgrade ROM error code HELP PLS

Hi,

Can someone help me pls. I have SE Xpeia X1 and it is with WM 6.1

I went to SE web site where they offerd me to download an aplication in order to update my software and till here all ok I followed the instructios etc. the phone went to that color mode etc. and the update started but gues what it stucked at 10% and a message came up on my PC (the updates is on PC aplication and it requieres an USB conection btween PC and the phone) and the message says "update unsucsesful turn off yr phone and try again....."

ok I did it and I did it .....and .... more than 20 times and now X1 cant start WM6.1 and it is dead. So pls can someone give me an advice what I can do do get back to life my X1 pls.
[HTC Cavalier] tiger75:
It recovered him self next day????!!!!!!!!!

HI all,Just to inform you that the next day the update was installed 100%. Somehow the X1 did not stuck and the update pass. So I have alive X1 again.

the case is closed

nice day to all
[Nexus 5 Android Development] forse_qualcuno:
I'm trying to use this but both camera and wifi hotspot do not seem to work. Can I help somehow?

Hammerhead: camera and hotspot do not work. · Issue #140 · Divested-Mobile/DivestOS-Build

Phone boots fine, tho. Bootloader relocking works as well. I haven't tried calling, incoming SMS do work. I'd like to use this phone again, but I can't without camera and hotspot. I did run a logca...

github.com
[Nexus 5 Android Development] fw190:
Hi

@SkewedZeppelin Just did a clean install. I can't remove apps the regular way (tap, hold, swipe to the uninstall field at the top). I have to go into apps section in the settings and there click uninstall.
[Nexus 5 Android Development] SkewedZeppelin:
This is an old bug in the launcher, it happens at random sometimes. Just force stop Trebuchet.
[Nexus 5 Android Development] balakarpo:
Hi guys.

I have device LG Nexus 5x bullhead and tried to install Divest on it.

(I installed custom ROMs several times, I am not new to this process)

All went smooth, but when I was setting up the phone, on the step to set the screen lock pin/pattern - it just crashed.

After this I had difficulties to boot it even into fastboot menu and when I did - I tried to flash the genuine (Google) ROM on it (I did it several times and it is working ROM), but during the flashing, in the terminal it showed a list of archives missing.

Now the phones goes to Google logo and then to black screen.

Well, I do not know if there is any workaround or not.

Please advice.

Thanks
[Nexus 5 Android Development] SkewedZeppelin:
That sounds less like a DivestOS issue and more like user-error or the dreaded Nexus 5X bootloop issue: https://en.wikipedia.org/wiki/LG_smartphone_bootloop_issues#Nexus_5X

I test DivestOS on bullhead each monthly update before release (without issue).
[Nexus 5 Android Development] balakarpo:
Thanks for replying so soon.

I installed two ROMs before (LineagOS 17.1 and 19.1 Unofficial version) on this device without problem. The unique problem was that I was unable to encrypt the phone on those and that was the main reason to try DivestOS.

I understand it can be the hardware problem (maybe mine), but is there any workaround? Thanks
[Nexus 5 Android Development] Deleted member 5096246:
Hello, first of all thank you for creating this awesome rom. Im using it for some extended period of time on my backup devices which is Nexus 5 and it works great, it feels so secure and also having latest security patch is awesome. Keep doing the great job! Rom is awesome, recommended for everyone!
[Nexus 5 Android Development] Deleted member 5096246:
I managed to install DivestOS 18.1 even on my Nexus 4, works as it should for now. (Been a nexus fan before so i got these 2 nexuses :-D) Is there a chance that you make it for my main phone which is Xiaomi Mi 10t pro, please? At least one build and thats it :-)
[Nexus 5 Android Development] SkewedZeppelin:
Any device I add I have to perpetually maintain.

apollon is already in the queue to be eventually added maybe someday: https://github.com/Divested-Mobile/DivestOS-Build/issues/68
[Nexus 5 Android Development] aaronjasper49:
Thank you so much for this
[Nexus 5 Android Development] arnoldwu:
Hello, good day! I was trying to fix my nexus 5 Wi-Fi problem, so I was flashing a few ROMs to see if it get fixed. I tried this one then... No success. Now I'm trying to go back to a stock image, but I'm having trouble to get my phone recognized by the computer. Do I get this problem because the phone is encrypted? Can I decrypt my phone? Can't use trwp eider, because of the encryption.
[Nexus 5 Android Development] SkewedZeppelin:
TWRP should work fine?

DivestOS makes no changes that would lock you to DivestOS or prevent you from switching.

Maybe try a different cable, and a USB 2.0 port.

Also Wi-Fi works fine on my hammerhead, if it doesn't work on multiple systems maybe you have a hardware issue or corrupted persist partition.
[Nexus 5 Android Development] c0mr@d3:
Big fan of your OS, i know you do not support SU or Magisk or microG, but could you atleast let us multiboot with your awesome OS? please kindly add the Kexec-Hardboot patch to your kernel so we could be able to boot into a googled OS, or Ubuntu Touch.

thanks in advanced and looking forward to this patch added.

Kexec-hardboot patch
[Nexus 5 Android Development] SkewedZeppelin:
No, kexec is explicitly disabled for security reasons: https://github.com/Divested-Mobile/DivestOS-Build/blob/master/Scripts/Common/Functions.sh#L1048

If you want such changes the way to get them is by compiling your own builds: https://divestos.org/pages/build

Ubuntu Touch for this device is also blatantly insecure missing years of basic security patches: https://github.com/ubports/android_kernel_lge_hammerhead/commits/ubp-5.1
[Nexus 5 Android Development] c0mr@d3:
please do elaborate on the security reasons, all kali nethunter kernels have Kexec-hardboot enabled, i run the latest version and would love to see the exploits for it. Please enlighten me.
[Nexus 5 Android Development] SkewedZeppelin:
There are no direct exploits for it, it is just attack surface reduction.
[Nexus 5 Android Development] c0mr@d3:
maybe possibly supply an optional flashable zip for this minor reduction. giving the user the option to enable this to run nethunter kernel, currently i run it systemless, but i have to use an external wifi adapter, honestly is not very stealthy. I believe there are various benefits to having hardboot, that is just one. (having internal wifi support for nethunter)

P.S. maybe it could be added as a developer option in your OS?
[Nexus 5 Android Development] SkewedZeppelin:
no.

That would require compiling every kernel twice.
[Nexus 5 Android Development] c0mr@d3:
to recompile your kernel do i simply remove "optionsNo+=("KEXEC" "KEXEC_FILE");" and add it to the "optionsYes+=(" section ?
[Nexus 5 Android Development] SkewedZeppelin:
Yes, but you need the full workspace setup first.

You can just use `mka bootimage` to only compile the kernel.
[Nexus 5 Android Development] c0mr@d3:
would EFIDroid also require a recompile of the kernel?

im trying to find a balance to use your OS and be able to test other OS with out wiping or having to purchase other devices, that adds to more junk... in multirom i am also able to install OS to an OTG for testing, this makes your OS a prime candidate for a removable stealth setup.

Update: nevermind EFIdroid does not support encryption
[Nexus 5 Android Development] c0mr@d3:
one more question sir, i have tried all your location suggested apps and none of them give a lock to the GPS. I've tried all the GPS settings checked the physical devices connections, and even reverted back to Stock to verify the hardware works, all works with google services.

Is your OS not built to have working location?
[Nexus 5 Android Development] SkewedZeppelin:
Location does work. Please test using this app and wait up to 12.5 minutes: https://f-droid.org/en/packages/com.android.gpstest.osmdroid

Ensure it has accurate time, clear line of sky, having it not in airplane mode can help too, and wifi or cell so it can download the almanac also helps.

I tested my hammerhead working GPS on this latest build before release.
[Nexus 5 Android Development] SkewedZeppelin:
DivestOS doesn't support UnifiedNlp, such location providers won't do anything.
[Nexus 5 Android Development] c0mr@d3:
i have tried the GPS test app, it did not work for me. i will attempt it again and wait for a non cloudy day.

Do you suggest inserting a SIM card form a carrier? that's is the only thing i don't do because the device then is highly trackable and cell tower network is easy to compromise due to it have no encryption (huge attack surface, ex. SimJackin, IMEI Spoofing, Etc...)
[Nexus 5 Android Development] SkewedZeppelin:
a SIM shouldn't be necessary, and the device connects to towers regardless of SIM inserted for emergency calling support.

also 3g and 4g *do* have encryption. 4g is even e2ee to the tower itself.
[Nexus 5 Android Development] c0mr@d3:
ok maybe i should enable data in my phone dialpad provisioning settings, yes i was aware of it communicating with towers is why i disable via dialpad *#*#

i will re-enable and restest.
[Nexus 5 Android Development] c0mr@d3:
sorry what i meant was once your are in the cell tower network, there's no authentication, you see all device info that are connected to it, you could even see the make and model of the vehicles connected to it.

in the US there are legal interception requirements there for end to end does was not implemented.
[Nexus 5 Android Development] SkewedZeppelin:
there is client authentication, that is what the SIM card is for

and they can derive make/model from your IMEI alone, no backdoor or anything

any traffic that is encrypted from your phone like https or encrypted dns cannot be inspected by them

but yes, the tower itself isn't authenticated and it is possible for an attacker to spoof a tower
[Nexus 5 Android Development] c0mr@d3:
be a pal and post a boot.img with hardboot enabled. im having a time trying to compile your kernel. just for the stable 15 version
[Nexus 5 Android Development] c0mr@d3:
tested three N5 with your most recent OS and also tested your Oldest one (downloaded them before you (divestos.sny.sh) was taken down. then i also tried with a modified gps.conf file that i verified working on a normal OS, still no lock. would like to at least get hardboot or a working gps lock on your OS.

I would love to have your OS as a daily driver.
[Nexus 5 Android Development] c0mr@d3:
Tested DOS 15.1-20230508 with all radios, no GPS. doesn't even detect a single sat.
[Nexus 5 Android Development] c0mr@d3:
fixed the GPS by injecting UAR, Dalvik, cache, from a working rom, then i had to edit two files "apns-conf.xml" and "gps.conf" entirely for my side of the planet. I also went the extra mile to tighten up the browser security. (screen shots).

now all i have left to do is tackle your kernel so i could dual boot and get pass safetynet.

over all im loving the setup with systemless spoofing modules for IMEI, serial, device ID, etc, but more importantly i was able to get Kali nethunter running with internal wifi monitor mode, and injection.

thanks
[Nexus 5 Android Development] c0mr@d3:
where is Mulls bookmark file located? don't really want to use a third party app also don't want to give away my bookmark info to mozilla sync service.

P.S. what's up with the mozilla telemetry tracker in Mull browser?
[Nexus 5 Android Development] SkewedZeppelin:
Mull does not support bookmark import/export as Firefox doesn't either: https://github.com/mozilla-mobile/fenix/issues/417

Mull does not have any functional trackers, they're either stubbed out or entirely disabled.
[Nexus 5 Android Development] c0mr@d3:
nevermind i got it, importing bookmarks CSV file into "moz_place" table that's in ".../files/places.sqlite"
[Nexus 5 Android Development] crimss:
Hi, i wanted to try divestOS in my hammerhead (previously with lineageOS) and followed the specific steps for that model.

I tried divested-18.1-20230809-dos-hammerhead.zip. I have a problem after sideload the zip.

Sideload stops at 47%, which i undestand is the spected behavior.

In the phone side im getting:

E1001: Failed to update system image

E:Error in /sideload/package.zip (status 1)

W:failed to read uncrypt status: No such file or directory

in the logs i also see before

/cache/recovery/last_command doesnt exists.

BLKDISCARD ioctl failed: Invalid argument

failed to execute command [erase 6,....]
[Nexus 5 Android Development] crimss:
Im answering this to save some time to SkewedZeppelin who point me to the solution via XMPP

Looks like i was wrong, sideload shouldn´t stop at 47%, after the fix it went to 94%.

In the news (https://divestos.rg/pages/news.html) there is a note specific for hammerhead on 18.1:

I went and downloaded twrp (twrp-3.7.0_9-HH.R.17.img), ran

fastboot flash recovery twrp-3.7.0_9-HH.R.17.img

, followed the steps to resize the partitions (-m parameter) and restarted the steps for hammerhead and im up and running.

Thanks again SkewedZeppelin for your quick support and for this great project.
[Nexus 5 Android Development] LegendOcta:
I do acknowledge this is unsupported but is there a way to disable encryption?

I plan to use this phone only at home for lightweight usage and encryption is pointless for me.
[Nexus 5 Android Development] SkewedZeppelin:
You'd have to edit the fstab after installing each update and replace forceencrypt with encryptable.

But just because it doesn't leave your home doesn't mean it is useless.

eg. What happens when it breaks and you need to throw it out? No need to make it trivial for whatever is on it to be easily accessible.

Encryption also provides a much better guarantee that a wipe will make any past data largely unrecoverable.
[Nexus 5 Android Development] LegendOcta:
Thanks. I don't even have a lockscreen so..
[Nexus 5 Android Development] LegendOcta:
Trying to install on another hammerhead I noticed 15.1 and 16.0 is gone for hammerhead and only 18.1 is available, are they discontinued now? 15.1 was much more responsive compared to later versions IMO, and also used less ram.
[Nexus 5 Android Development] SkewedZeppelin:
yes, I dropped support for them as older branches are less secure: https://divestos.org/pages/patch_levels#branchPatchLevels

and have less features: https://divestos.org/pages/technical_details
[Nexus 5 Android Development] c0mr@d3:
yes 15.1 is in fact way more responsive
[Nexus 5 Android Development] c0mr@d3:
please post the final 15.1 here. thanks in advance, will test 18.1 soon.
[Nexus 5 Android Development] SkewedZeppelin:
i don't store or host old builds.
[Nexus 5 Android Development] c0mr@d3:
what's the last 15.1? i have 0718.
[Nexus 5 Android Development] SkewedZeppelin:
That is indeed the last one.

But please note it is not secure, take for example the recently patched CVE-2023-4863, a critical zero-day allowing code-execution by simply viewing a malicious WebP image: https://divestos.org/pages/news#2023-09.2