yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] jashsu:
How is this going to help OTA RC30 users, who fail on the update-script?
[G1 Android Development] tonym001:
Yeah, you're not going to be able to downgrade that way without access to google's signing key.

It looks like the bootloader has been dumped, and that it's using the standard HTC password, so there should (hopefully) be a solution to those users on rc30/rc8 that don't have root access soon.
[G1 Android Development] jazzmanmonty:
ok i'm no linux hacking expert, have been more of a windows and wm person when it pertains to pda phones in the past, but i think it should come down to a simple key generator of some sort or overwriting some existing key. I'm sure since we are all here talking about how to hack the g1, we have all (never) downloaded pirated software with keygens or using some product key we obtained from the web. The problem is this, we need some sort of supervisor key to get root on RC30. Well with all the people that visit this site, i'm sure someone has access to this key, and with all the talented software tweakers on here, i'm sure someone can write a quick prog to install the key on the g1....am i on the right path on this one, or because of my cluelessness w/linux platform i'm totally sounding like i'm shroomin?
[G1 Android Development] Gary13579:
No. Yes, people in Google have access to this key. But they'd not only get fired for releasing it, they'd face multiple lawsuits.

And the key isn't something that's installed onto the phone, it's used to "encrypt" update.zip's so that the phone will accept it.
[G1 Android Development] N3xt2N0N3:
Just a thought...

Ok what if we use a recovery.img from a previous RC

Save it on a SD card

Use Android File Manager, its in the Market.

Go to under SD Card

Locate the recovery.img you put on there.

Copy it

Then Go under My Phone

Then system

Paste the edited recovery.img

And try to run the recovery

I wonder if it would work
[G1 Android Development] xile6:
Correct me if I'm wrong but I don't believe the file manger has the promission to write the img to the needed folder
[G1 Android Development] card13:
It would be nice. And work if RC30 didn't lockout the entire /system dir. It's all read only, so if you find someway to unlock it in an official RC30 then by all means please let us know. Also that trick only works on RC29 or lower.

And xile6, your right I tried it right after the program came out, I've tried all the file managers, and the adb push method, it's all locked to read only. Android File Manager, and Glance both show them as lock, specifically the recovery.img file. With no root we're for lack of a better way to put it, screwed.
[G1 Android Development] speoples20:
Possible way to get RC29 on G1

So like a lot of the people out there I updated to the normal RC30.:( I didn't mean to update it but that stupid box popped up and I pressed update without thinking.

So the other day I had an idea. I called T-mobile tech support and told them my volume control was "broken". After trouble shooting and telling the I did a hard reset(which I didn't actually do) they placed an order for a replacement G1. I was hoping that the replacement phone would have the older RC29 update.

So my G1 arrived today and I transfered my SIM and battery over to the new phone. Logged into my new G1. Went straight to my settings and there it was, the glorious holy grail, RC29!:D

Since all the apps are free and syncing my contacts and info is super easy its not hard to change to a new phone. Just need to redo my invisisheild. So if you really want to get the RC29 and hack it with the modded RC30 I would suggest doing a warranty exchange.
[G1 Android Development] Disconn3ct:
factory units are rc30 now, so the chances of this working get more and more slim by the day.
[G1 Android Development] speoples20:
Yeah I was hopping that I could get one before they start coming with RCv30. So hurry up if people want to try this. Only $10 for shipping.
[G1 Android Development] dirr:
That's pretty funny that you just made something up and consequently got a rooted phone.
[G1 Android Development] dwang:
Thats what I did too to get rc29. I returned my rc30 version for another one.

Of course the new one has some issues with the face buttons being really flat and mushy, but I'll live with it. I got mine at costco so I can return it anytime within 3 months, I'm waiting for rc30 to get cracked and maybe I'll exchange it with another one with better face buttons.
[G1 Android Development] carlozt03:
Idea to downgrade RC30

Hello! Long time reader...rare poster...but I had an idea I haven't seen put out here yet to downgrade to RC29 and get root back. Would it somehow be possible to spoof the build on the G1 so that the signed RC29 would take? It looks like the update-script sees to verify what version the phone is and then moves forward appropriately. Spoofing the phone to be, say, RC19 would maybe make the RC29 take? Maybe I'm retarded? Haha. Thanks!
[G1 Android Development] mrdelayer:
That was the premise of a lot of the early PSP downgrade hacks and may very well be a viable solution.
[G1 Android Development] jashsu:
This idea is a non-starter. Inside every update.zip is a META-INF folder which contains among things a list of cryptographically signed hashes of all the files in the update. If you remove the assertions from update-script, it will no longer match the signed hash. The signature is made with a T-Mo/HTC private key.
[G1 Android Development] carlozt03:
I meant spoof the actual version in the G1 itself not the files in the update.zip. That way when the RC29 install is attempted, it sees that the version on the G1 is RC19 or 28 not the RC30 that is actually installed.
[G1 Android Development] bunny0007:
Are you sure of checking af the meta files?

I have not checked it but, in the source code from recovery is there some files excluded from the check.
[G1 Android Development] jashsu:
Can't modify the fingerprint at runtime.
[G1 Android Development] JesusFreke:
I'll have to agree with jashsu here. The fingerprint that it checks is set in the /default.prop file in the recovery image. The only way to change the fingerprint is to change that file, and to change that file, you have to re-flash the recovery image, which requires root access (or a dev bootloader). I also took a brief look through the code in init that is responsible for keeping track of these properties. It seems pretty secure.. I didn't see any potential buffer overflows, or otherwise any way to get around the restriction where you can't change a "ro." property once it has been set.
[G1 Android Development] debro012:
Why not Flash signed RC29 to RC30 to get root back?

Is this possible... I was downloading a RC29 official update file and I was going to re-flash my RC30... Am i mistaken or is the problem that we were having is that without root access it would not take a unsigned image? or is the problem something else?
[G1 Android Development] richbayliss:
The theory is solid, but I belive the phone will check and say that 30->29 is a downgrade and therefore not possible.
[G1 Android Development] afbcamaro:
The official's RC29's update script looks that it is indeed an update and also checks signatures. We can defeat the update script to not check for <RC29 but as soon as we do that we lose the signature :-( Endless loop!!
[G1 Android Development] debro012:
Tried and this method does not work...Failure at Line1
[G1 Android Development] jashsu:
Here are the first four lines from RC29 update-script (location update.zip\META-INF\com\google\android\update-script

assert getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC29/115247:user/ota-rel-keys,release-keys" || getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC28/114235:user/ota-rel-keys,release-keys" || getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC19/109652:user/ota-rel-keys,release-keys" || getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC29/115247:user/ota-rel-keys,test-keys" || getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC28/114235:user/ota-rel-keys,test-keys" || getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC19/109652:user/ota-rel-keys,test-keys"
assert compatible_with("0.2") == "true"
assert getprop("ro.product.device") == "dream" || getprop("ro.build.product") == "dream"
assert getprop("ro.bootloader") == "0.95.0000"

An assertion simply ends the script if the logical statement following it is false. The assertion on the first line checks the fingerprint of the installed Android and makes sure it is one of the authorized fingerprints. In this case, only OTA Androids of equal or lower RC## are permitted to use the update.

An interesting note is that htc/TMo could theoretically push out an OTA update to all G1s without specifying the origin fingerprint by simply removing the first line assertion. (Lines 3 and 4 would ensure that the update is not run on non-G1 Androids).
[G1 Android Development] debro012:
Ok juys i have been playing with the update folder and this is what i have come across...

I downloaded at Stock rc29 and rc30 update

Kepping in mind i have ota rc30 on my g1

I was not able to flash rc29 using update.zip(error at line1)

However i was able to reflash rc30 update.zip

I decided to extract both updates and inserted the the recovery.img and build.prop found in the system folder of the rc29 into the system folder of the rc30 and created my own zip file named update, of course, and attempted to flash... my results were:

that it made it all the way through flash til it got to system/recovery.img-wrong digest... now i dont know too much about programing but maybe these findings will spark a programmer into another direction with hacking rc30... Im not giving up on this issue until there is a soulution and i vowe to keep krying any file, software exploit i come in contact with... i will keep switching around files in this hybrid update.zip folder just to see what happens, but i have to go for now but ill be back this evening...
[G1 Android Development] jashsu:
This approach is destined for failure as all files in any given update.zip are SHA1-hashed and then signed with a private key. If you attempt to mix and match files from different updates, the foreign files will not match the hash entries in the MANIFEST.MF and CERT.SF.
[G1 Android Development] debro012:
^^^so is there any 1 file that is dfferent from the rc29 and rc30 update that would allow this method to succed if that one file could be altered or is the whole thing just a domino effect no matter what you alter?
[G1 Android Development] jashsu:
Android basically just uses Java's security model. It's been proven for over a decade. You can read the details about jar (same as zip or apk) verification here:

http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/jarsigner.html#Verifying
[G1 Android Development] bhang:
havent you been following along?

to the guy who just wanted to use the official RC29 to overwrite an RC30, you have really missed a bunch of stuff in this area start reading at the first sticky and read all of them at very least.

to the guy who is frankenstining update.zips good try but you gotta have the htc keyset to sign your baby, like the lightining that brought Doc frank's creation to life, but your right it just may spark somebody somewhere, but good encryption is a *****, remember this when you have stuff that you dont want anybody to see on your harddrive, I dont think there is a brain scan available to figure out if you can recall your encryption key or not.

they even search the contents of harddrives in laptops at airports, in the name of security, lock up "my computer" before departing on your next flight...

It will happen those ota RC30's will be broken and even tho Im making fun, any testing could lead to the solution, no matter how misguided, I mean imagine if they left a root shell open all the time and fed all keyboard input to it? ITs a bit far fetched but It could happen...

bhang
[G1 Android Development] d474rpr:
Where can I get the rc29 and rc30 update files? :eek:
[G1 Android Development] Mikey:
would help if you tell us what RC number is installed on your phone, first.
[G1 Android Development] JesusFreke:
Why do you need the RC#?

The update files can be found here: http://android-dls.com/wiki/index.php?title=OTA_Updates
[G1 Android Development] jdwme:
well thanks to an idea in this thread I contacted tmobile to get a warranty replacement stating my track ball was messing up (it really has messed up) and they sent me another device, this was friday night. Paid for express shipping and got the phone today with rc-29. I just updated to the modified rc30

Of course I got a phone with a dead pixel on the screen, one red dot, wonder if I can swap screens before I send the old one back?
[G1 Android Development] robpet2:
wow... this is making me wanna send mine back and get a replacement g1 and hope for rc29
[G1 Android Development] neva dinova:
maybe someone should ask jockw2001 he did the franken kaiser project
[G1 Android Development] genejockey:
I'm not sure if that question is rhetorical or not, but I will say that the HTC Dream service manual is pretty informative on how to disassemble your phone, starting on page 18. The LCD looks pretty deep into the device. First you have split the LCM from the main chassis, then you dig into the LCM. Note that there is double sided tape needed on page 44.
[G1 Android Development] Mikey:
My experience in these forums, with certain people, WANT something but not knowing what they have causing them to be UNABLE to have it.
[G1 Android Development] andyandrwew:
Watch out.

watch out JF the build numbers are a huge deal now(the finger-print errors)
[Nokia Lumia 920] jndmn:
Does somebody can help me with finding the HEX loaders for unlocking the bootloader on Lumia 920?
[Nokia Lumia 920] lizijun:
tell me your rm,i have a lot of hex files for 920
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] Astridxx:
AwakenOS for Lenovo P2a42 [kuntao]

#include <std_disclaimer.h>
/*
* Your warranty is void. Or...Valid? Probably?
*
* Project Awaken and its maintainers are not responsible for bricked devices,
* dead SD cards, data loss, thermonuclear war, or economic crisis caused by
* Awaken OS. YOU are choosing to make these modifications, and if you
* point your finger at me for messing up your device, I will laugh at you.
*/

Born different, now awaken.

Awaken OS brings consistent, fluent and smooth experience with all your must-have customizations, for you, for the community, for everyone.

- Project Awaken Team -

Saikiran [Founder & Lead Developer]

Ninad Patil [Lead Developer]

Mukul [Developer]

Hugwalk [Lead Designer]

Jagadish [Designer]

Glitch [Designer]

Find us on Telegram! @AwakenOSNews

Display

Ambient edge lighthing

Fonts, Icon shape & Icon pack customizations

Force full screen app & hide app from launcher

Kdragon Monet

Monet customizations

Gestures

Advance reboot menu

Double tap to sleep and wake

Navbar customizations

Playback control

Three finger screenshot

Toggle torch when screen off

Volume button wake and cursor control

Lockscreen

Charging info

Media art & blur

Pulse visualizer

Notification

Headsup Customizations

Saner Headsup

Pixel Features

Columbus (Quick Tap)

Game Dashboard

Smartspace

Quick Settings

Brightness slider customizations

Internet speed meter

Quick QS pull down

Security

Applock

Disable qs pulldown on secure lockscreen

Face unlock

Hide power menu on lockscreen

Scramble pin layout and quick unlock

Secure qs tiles on lockscreen

Sounds

Custom ringtone vibration pattern

Cycle through ringer modes

Increasing ring volume

In-call vibration

Link ring and notification volumes

Per app volume

Ringtone focus mode

Smart pause

Statusbar

Battery styles

Clock customizations

Combined signal & 4G instead of LTE toggle

Mic, Camera & Location indicator toggle

Small mobile type icon

You tell

First Time Install / Clean Flash

1. Download the proper flashable ZIP for your device

2. Reboot to Recovery

3. Wipe Cache / Data / System / Vendor

4. Flash ROM

5. Flash Gapps (optional)

6. Flash Magisk (optional)

7. Reboot to System and #beAwakened

Update / Dirty Flash

1. Download the proper flashable ZIP for your device

2. Reboot to Recovery

3. Flash ROM

4. Wipe Cache

5. Reboot to System and #beAwakened

Download Here / Official Announcement / Official Community

Kernel Source / Source Code
​

XDA:DevDB Information

[ROM][12.1][UNOFFICIAL] AwakenOS 2.10 for Lenovo P2

Contributors

Astridxx ,XiaoAk ,Sohit5s

ROM OS Version: 12.x Sv2

ROM Firmware Required: Latest Stock

ROM Kernel: Linux 3.18.x

Version Information

Status: Stable

Created: 2022-05-10

Last Updated: 2022-09-21
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] Astridxx:
Changelog :

21/09/2022
• EOL build
• Enabled unlimited google photos backup
• Enabled home button wakeup
• Fixed system update issue
• Bump zram 1GB to 1.5GB

16/08/2022
• Awaken version now 2.10
• Merged August security patch
• Fixed fm radio

10/07/2022
• Awaken version now 2.9
• Merged july security patch
• Compilied kernel with 12.0.7 clang

17/06/2022
• Awaken version now 2.8
• Merged june security patch
• Updated GPS config for S
• Switch to default DRM HAL
• Improve scrolling responsiveness
• Fixed VPN settings screen
• Fixed Gradually increase volume in alarm clock
• Removed location indicator when wifi is enabled
• Removed carrier video call support ( not working with our old ims blobs)

14/05/2022
• Fixed bt call
• Enabled ANT+ support
• Enabled seamless AOD transition

10/05/2022
• initial build
• Merged may security patch
• Compilied kernel with 12.0.5 clang
• Switched to selinux enforcing
• Switched to audio hal v5
• Switched to health hal 2.1
• Switched to lazy drm hal
• Switched to lazy wifi hal
• Switched to grapheneos camera
• Fixed safetynet
• Fixed manual network selection
• Updated f2fs/ext4 mount flags
• Disabled fp gestures vibration
• Silence cam and fp excessive logs
• Add several Android Go optimization
• Readd various USB compositions
• Set wfd max resolution to 1080p 30fps
• Limit screen recorder to 60fps
• Apply aggressive write caching for old phone
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] amdyss:
Smooth instalation. So far so good.
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] mahmutpekkara:
Great work, much appreciated!
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] hoticx:
I would like to thank our friends who worked hard and offered the users ANDROID 12 experience for the Lenovo P2 produced in 2017. I've been using it for three days and it's great.
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] amdyss:
After couple od days I'd say its better than crdroid.

Edit: BT calling doesnt work for me. Can someone confirm this?

For me, battery lasts one day, with about 6hr of sot. 90%4g+bt on.
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] Cinek1:
What is the battery life?
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] Astridxx:
Good for me

View attachment 5614375
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] educowley:
Hi all work perfectly only radio fm is not in this room and for me cast does'n work.

Thanks for this first release
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] garvit girotra:
When 4.9 kernel for p2 ???
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] educowley:
Hi, for me now that's the best room by the moment, no bugs only the problem with the FM radio, is not, very customizable, very fast, not too much battery consumption, really fast install from twrp recovery... From Sunday whit it and not any problems... Thanks for all developers
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] utwer:
Update https://androidfilehost.com/?fid=14655340768118474195
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] maruthi@0007:
Hi there, can anyone please confirm is the device is certified In playstore, and also what is the status of safety net test. Really willing to try this Rom as daily driver, Thanks in advance 😄👍
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] Astridxx:
View attachment 5617371View attachment 5617373
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] amdyss:
Does BT calling work for you?
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] amdyss:
Dirty flash will work? What's a changelog?
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] educowley:
I don't know I'll try, BT music work perfectly
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] amdyss:
Yeah bt music is all ok, calling for me doesnt work. I wonder if its only me or its overall problem.
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] Astridxx:
New update:

Download rom: Awaken-2.7-kuntao-12L

Download gapps: Flame-gapps-12L

Changelog:

• Fixed bt call
• Enabled ANT+ support
• Enabled seamless AOD transition
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] maruthi@0007:
This is by far the smoothest rom i've used no lags or hanging ... literally feels like 90 hz screen .. iam really happy to find this rom , Thanks to Astridxx . Really appriciate your hardwork here :)(y)
[Redmi 9A Guides, News, & Discussion] VD171:
EVERYBODY SHOULD AVOID

UPDATING REDMI9A AND REDMI10A USING XDA-FORUM OR XIAOMIFIRMWAREUPDATER.COM.

Here is a good place for finding DANDELION ROM (Redmi 9A / 9AT / 9i / 9A Sport / 9i Sport): https://mirom.ezbox.idv.tw/en/phone/dandelion/

For DANDELION_C3L2 ROM (Redmi 10A): https://mirom.ezbox.idv.tw/en/phone/dandelion_c3l2/
[Redmi 9A Guides, News, & Discussion] Applewubs:
Im sorry for the question, but why should i avoid updating with these websites? (i've updated with xiaomifirmwareupdater.com since a long while ago, they're messing the updates of the 9a and 10a?
[Redmi 9A Guides, News, & Discussion] VD171:
Roms for Dandelion and Dandelion_c3l2 are mixed on them.

So, you can easily flash the wrong rom by mistake.

I've tried to flash Redmi 10A rom on the Redmi 9A and it has bricked the system and I lost all userdata of the device.
[Redmi 9A Guides, News, & Discussion] Applewubs:
Damn, they dont update beta on that site you recommended?, i usually flash them on recovery as they upload them, i don't care much about my data since i have a daily backup on my PC and everything on an SD (Because of the bad official roms when 12.5 came out)
[Redmi 9A Guides, News, & Discussion] VD171:
The "beta" version of the website xiaomifirmwareupdater is the ZIP (recovery) version.

And "stable" version is the TGZ (fastboot) version.
[Redmi 9A Guides, News, & Discussion] bhebe011971:
Does anyone have CUSTOM ROM for REDMI 10A Global?
[Redmi 9A Guides, News, & Discussion] Ivan.Adriazola:
I wonder if thats why my device got bricked XD, but I doubt it since other people said that rom worked for them.
[Redmi 9A Guides, News, & Discussion] VD171:
Tell other people to prove that.

I tried and it didn't work.
[Redmi 9A Guides, News, & Discussion] Ivan.Adriazola:
if your device got bricked it can still be fixxed tho, its annoying but it cna definitley be done, I unbricked mine at least.
[Redmi 9A Guides, News, & Discussion] VD171:
Definitely, yes.

The thread is just an alert.
[Android Software/Hacking General [Developers Only]] -VEDMETA-:
​

Hello my friends

I have created a program that opens and closes the bootloader with just one click for beginners :ROFLMAO::ROFLMAO:

You do not need to install ADB, just check your device drivers on your computer and put the device into fastboot mode

Program for Windows 10\7\11 devices

Run the program open or lock and enjoy

password : ( VEDMETA )

{Mod edit: Attached files removed}
[Android Software/Hacking General [Developers Only]] rodken:
Opens the bootloader - as in unlocking?

Is the program device specific?
[Android Software/Hacking General [Developers Only]] -VEDMETA-:
There are two files, one for locking and the other for opening
[Android Software/Hacking General [Developers Only]] Oswald Boelcke:
@-VEDMETA- Thread closed and attachments from OP removed. All attached files were flagged by VirusTotal.

https://www.virustotal.com/gui/file...25d3fcd26306fe60a98124cbba15bc14f5d?nocache=1

https://www.virustotal.com/gui/file...20b4ee9d03cc85bb7aadd188cb988248a4a?nocache=1