I received my G1 yesterday. But I wanna know if I can root it. And how.
n8gk said:
I received my G1 yesterday. But I wanna know if I can root it. And how.
Click to expand...
Click to collapse
Try to flash it with the US RC29 or the UK firmware. But I don't think this will work as the SPL will block it.
AFAIK there's no way to get root at the non US/UK/Dev G1 at this time.
Michael
try update using rc30 update.zip file. I think you will install SPL for US region and you can flash back to RC29
Does it work? Because i wanted to buy the German G1 but if I can't root it, I will buy the UK Version.
@n8gk
work root with the US SPL ??
have you try this ??
If you flash a US or UK firmware on a german G1,....
will the Keyboard work correct ? the Layout for Z and Y are different.
Where can I get the RC30 update.zip file
Ther german has also a build 123099.
I didn't try to update, because I don't wanna loose the ability to go back to the original.
Waiting that a original one is out first. (because of language and keyboard)
Not Allowed
I tried to downgrade with rc29 firmware, but it isnt possible...
Checking...
Loading...
Not Allowed...
And then stuck in the bootloader...
I also got my G1 last week and it also has the 123099 Build.(I live in Austria) If there is any way how i can help to root this build (upload it?), let me know.
If i flash an UK or US firmware on my phone (suppose some genius finds a way how to do it) wouldn't it render the "Disable Data-Roaming" function useless, when i travel to one of these countries? And even deactivate the data connection in my home country?
In Austria tmo offers a roaming block on their side so i do not have to use this function on the phone, but i am just curious...
Maybe one of the more experienced users in here could tell us about the chances of rooting such a device.
Are there any or did Google / T-Mobile finally fix the backdoor completely?
Greetings,
Becksman
In device info the build description is:
kila_eu-user 1.1 TMI-RC4 123099
ota-rel-keys,release-keys
And build id:
TMI-RC4
The backdoor has been fixed for some time now... But as long as you were able to revert to an older image you can re-root your device, but we are not able to do this because we would need to use an image with another CID and that is not allowed with the original SPL. But the only way to change SPL is when you have your device rooted...
Correct me if im wrong plz..
So that means bad news for the European G1 owners?
seems so. and because the developers here already got a us-hacked version, they not seem to be interested in hacking this 1.1 firmware the one or other way.
are the european developers to stupid/busy to do it? or are they so clever to get a us one?
in the european firmware 1.1-version the manufacturer has alredy fixed the lame telnetd-root bug and the bootloader. and this is, on what the us-g1-hacks are based on.
i have the hope that some day a local root exploit will apear, which exploits the kernel or another vital component of the g1 to get root without telnetd.
maybe such a kernel exploit will be discovered in the standard linux kernel which can be portet to android; or some great reversing/hacking-debugging-genious-mastermind finds an android exploit all by himself.
android is so new, there MUST be bugs to exploit locally.
Iam a highlevlel-programmer, iam not able to find such local root vulnerabillities.
way to open EU G1
one guy from Czech republic did it
http://forum.xda-developers.com/showthread.php?p=3361823#post3361823
First of all, congratulations to Paul for hooking us up with the Desire root.
I'm a new android user and I'm most of all interested in learning the inner workings of the platform (more than just having root), so I'm starting this thread to discuss Paul's recently published root method, so we can better understand it so that we can build on it.
As I see it, Paul has found a "Test RUU" that downgrades the phone to a Test ROM version of version 1.15.405.3. This version has the the recovery ROM set so it listens to ADB and allows for root access via ADB when booting the recovery partition.
He then pushes a few files with the objective of triggering a modified update (unsigned) that contain all the interesting bits, such as Superuser APK, and other modifications. This update is probably a modified and unsigned version of OTA update 1.15.405.4.
So I figure that the impossibility of rooting phones with the 0.80 bootloader is that it is not possible to downgrade the bootloader via RUU from 0.80 to 0.75 (which is the version in the Test ROM that Paul has found).
Is this it? can anyone else add some comments to improve on this vision? Paul?
Regards,
LG
Hi Guys,
I have an unlocked One Mini which apparently works in all European countries. At the moment its on 4.3 but I found an OTA file online named "OTA_M4_UL_K44_SENSE55_MR_HTC_Europe_3.10.401.4-2.12.401.1_release_351632.zip" which apparently is the update to 4.4.2
As best I can, I have cross referenced the phones build.prop with the updater script in the OTA and the relevant versions / model id seem to match. I also found instructions online about how to apply it. A couple of questions:
Could someone more knowledgable than me please confirm which items I need to match up in both files, so I dont make a mistake?
How do I access the recovery menu itself once recovery starts?
I need to leave it stock for warranty purposes, and I underfstand applying the OTA wont void warranty. Am I correct?
Thanks in advance
No one have any ideas on this?
To answer my own question, I spoke to HTC yesterday, it is the correct update for my phone and installs fine
Hi, I am wondering if there is a way to resign/regenerate hashes for a modified OTA file to try and force the system to downgrade when bootloader is verizon-locked.
So basically
1.) Modify version numbers to be newer than the current ones on the system to pass the first check.
2.) Generate a new hash for the file and sign it with that
3.) Device is fooled.
Has anyone ever tried any kind of file modification/spoofing for Pixel 2 VZW?
This comes up every time a new update breaks a root/unlock method. This kind of solution comes up often but never happens. I wouldn't count on it ever happening in the future.
I want to edit the hosts file of a moto edge (2021), however I also want it to continue to get OTA updates. So some (potentially dumb) questions:
Can you get OTA updates on an unlocked bootloader for motorola?
Can you get updates after rooting then unrooting the phone?
Will the hosts file changes made while rooted remain after unrooting?
Thank you for your time and help, much appreciated!
Hello, I have seen your publication and I want to give you an answer based on my experience with my Motorola phones, I am just going to try the custom rom that is available for this phone.
but I can clarify certain doubts
Regarding the updates, they continue to be received even if your device is unlocked, that is the answer to your first question,
second, once the phone is updated you can lose the root since in the updates they lose the modifications to some files like the boot.img.
and in the same way it depends on the update but if you can modify the host file.
But I am still going to recommend that you do not update the phone when you have it rooted, since in some update some changes are reverted and it may remain in the bootloop
I hope my answer helps you and I repeat this answer is based on experience with motorola phones