Database Users

how to root a uk version g1 build crc37 ???

hi ive been looking round how to root my g1 and had no conformation if the UK version g1 are different to root than the US.
can some give me some clarification on how to root them.
thanks in advance

i am a us g1 users so i might be incorrect but i believe that you need to use rc9 or a gold card. if it is rc9, the rest of the method is the same just a different .nbh

porkky said:
hi ive been looking round how to root my g1
Click to expand...
Click to collapse
No, you didn't.
http://forum.xda-developers.com/showthread.php?t=442480

Afirejar said:
No, you didn't.
http://forum.xda-developers.com/showthread.php?t=442480
Click to expand...
Click to collapse
Hey I’m having some trouble getting to grips with rooting too; there is quite a lot of information (some of it contradictory or at least inconsistent) for someone new like myself to take in. I consider myself pretty tech savvy but my G1 is uninsured and I’m frankly terrified of bricking it as I’ve got a year left on my contract to pay.
Anyway my point being...the guide your pointing to is specifically tailored to US models as are most guides on the net it’s very hard to find anything definitive about rooting the UK models with regard to SPL and Radio, etc. Also, given that this stuff moves soo quickly (which is an amazing testament to the hard work that all the devs and everyone else involved puts in, thank you!) it’s hard to catch up on everything and understand what exactly to do.

One click root works fine on crc37 uk phones ive rooted a couple now just follow the usual instructions, there's little danger of anything getting bricked if you arent touching radio which you dont need to do to load CM using the one click root app
http://www.ryebrye.com/blog/2009/08/16/android-rooting-in-1-click-in-progress/

seaweeduk said:
One click root works fine on crc37 uk phones ive rooted a couple now just follow the usual instructions, there's little danger of anything getting bricked if you arent touching radio which you dont need to do to load CM using the one click root app
http://www.ryebrye.com/blog/2009/08/16/android-rooting-in-1-click-in-progress/
Click to expand...
Click to collapse
I'm a little confused with all this too.
I've been to that blog and that seems simple enough.
It should work on this right? -
firmware - 1.5
kernel - 2.6.27 [email protected] #1
Build Number - CRC 1
Now, this means by phone is rooted, (Basically giving me sys admin rather than root user?)
Which in turn means I can install custom ROM images? Is there anything else this allows me to do?
And is all this permement? Or will it go back to the original ROM on the hardware when I hard reboot?
Sorry for all the questions, I got my phone today .

That's an original and most up to date UK version, so no you're not rooted. Easiest way is the one-click root, just install, put rom on SD card, run prog, reboot, flash (Read full instructions though).
Having root enables you to have full access, so you can do whatever you like from terminal and applications which require special permissions to run can, some cool stuff can only be done with root.

AdamPI said:
That's an original and most up to date UK version, so no you're not rooted. Easiest way is the one-click root, just install, put rom on SD card, run prog, reboot, flash (Read full instructions though).
Having root enables you to have full access, so you can do whatever you like from terminal and applications which require special permissions to run can, some cool stuff can only be done with root.
Click to expand...
Click to collapse
Thanks for the quick reply and I'm not trying to Hijack the thread, (But the OP will probably want to know this too), once I've rooted and installed the new ROM from the boot menu loader thing, how do I go about formatting my SD card to ex2?
I'm looking at this guide - http://forum.xda-developers.com/showthread.php?t=535232
But in this thread - http://forum.xda-developers.com/showthread.php?t=537204 CM himself says not to install APPS2SD. Can you do the format from inside that ROM or does it do it automatically for you?

Yeah cyanogen roms already contain their own method of app2sd, so trying to use another method on top just screws things up.
All you need to do is partition the card, then when you reboot it will see the partition, move your current stuff over and be good to go.
Follow this guide for partitioning from recovery console: http://forum.xda-developers.com/showthread.php?t=534714

Root for nexus one

Cyanogen tweeted it Some time back.....Nexus One is Now Rooted
http://android.modaco.com/content/g...82/30-12-1-1-superboot-rooting-the-nexus-one/
Isn't this great News..????
Starting the year with An Android which is already rooted.......
Wait for Jan 5th.....

Would be nice if he posted how its done so the droid eris could get rooted

thats indeed a very good news..we are also eagerly waiting for things to get started..lets see what they have it on 5th, they have called a press conference..

This is all going to start moving very fast after the 5th

FireSokar said:
Would be nice if he posted how its done so the droid eris could get rooted
Click to expand...
Click to collapse
I don't think the same rules apply to the Eris (or any non Nexus One phone). The way I understood it, the N1 is already technically rooted, but root access just isn't available to applications. The only way to access root is via ADB, as it's provided for developers, not normal consumers. The "root access" off the Modaco forums is really just circumventing the ADB limit and booting up with the device with superuser access, thus allowing apps to take advantage of it. Hope that makes sense... that's how I understand it at least.

Nexus One has ALWAYS been rooted...
The device is software/hardware unlocked if you buy it from Google (don't know if the one that'll be sold through T-Mobile will be locked).
All they did was add a su binary so that apps can share the phone's root access and a Superuser.apk so that users can allow/disallow permissions for apps.
I repeat, the phone was as rooted from factory as the ADP1/2 are.

If only it was that easy eh Jubeh!
Out of the box it's not 'rooted'... it does have an engineering bootloader, but unless you make something to flash via that bootloader, it's nowhere near rooted. You can't just go and dump those 2 files on the devices and say 'done'!
P

And it's be cause of that Engineering Bootloader that a new .img was able to be flashed.
Stericson suspects that the phone consumers get won't be shipped with the same SPL.

modaco said:
If only it was that easy eh Jubeh!
Out of the box it's not 'rooted'... it does have an engineering bootloader, but unless you make something to flash via that bootloader, it's nowhere near rooted. You can't just go and dump those 2 files on the devices and say 'done'!
P
Click to expand...
Click to collapse
Hmm, I thought the device was gonna ship like the ADP1 where you were allowed to adb root and then adb remount.
The engineering bootloader does make things easier, but wouldn't the bootloader allow you to fastboot boot recovery, then you could toss in the files through a custom recovery and set the permissions?

I downgraded from the Official AT&T 2.2 update back to 2.1

I used the info on this page: *android.modaco.com/content/htc-desire-desire-modaco-com/310873/possible-hboot-downgrade/* it didn't downgrade the hboot, but that might be something to work on.
CHANGE STEP 3.4. "change it to 1.15.405.1" don't do that, change the "2.20.502.1" in the misc.img from your aria to 1.25.502.2
Oh and you'll need either a Temp root, or a Shell root for adb

I have done this and can confirm that this works
Thanks mate!

I just noticed the Aria got 2.2 finally, albiet through this silly sync method.... It's my wifes phone, I'm sure she's not going to be happy to have to hard reset it.. wth.
Anyway, so why are you guys going back to 2.1? I am surprised not to see more discussion on 2.2 in this forum, but I don't frequent it much since I don't own the Aria myself.

khaytsus said:
I just noticed the Aria got 2.2 finally, albiet through this silly sync method.... It's my wifes phone, I'm sure she's not going to be happy to have to hard reset it.. wth.
Anyway, so why are you guys going back to 2.1? I am surprised not to see more discussion on 2.2 in this forum, but I don't frequent it much since I don't own the Aria myself.
Click to expand...
Click to collapse
I went back to 2.1 because the 2.2.2 version that AT&T released was extremely slow, and my touchscreen would become unresponsive.

andrewishcool95 said:
I used the info on this page: *android.modaco.com/content/htc-desire-desire-modaco-com/310873/possible-hboot-downgrade/* it didn't downgrade the hboot, but that might be something to work on.
CHANGE STEP 3.4. "change it to 1.15.405.1" don't do that, change the "2.20.502.1" in the misc.img from your aria to 1.25.502.2
Oh and you'll need either a Temp root, or a Shell root for adb
Click to expand...
Click to collapse
How do you get a temp root or shell root with the new HBoot still in-place? If temp root is possible, then can't you install clockworkmod and get permaroot?

Gene Poole said:
How do you get a temp root or shell root with the new HBoot still in-place? If temp root is possible, then can't you install clockworkmod and get permaroot?
Click to expand...
Click to collapse
I got a shell root from super one click root (forum.xda-developers.com/showthread.php?t=803682)
after I downgraded to 2.1 I got z4root to get a temp root.

andrewishcool95 said:
I got a shell root from super one click root (forum.xda-developers.com/showthread.php?t=803682)
after I downgraded to 2.1 I got z4root to get a temp root.
Click to expand...
Click to collapse
I'm also very curious about this.

Sounds like the first steps to rooting and downgrading. I'm curious to see if any developers catch this
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

I've been reading up on this and the skinny is that the HBOOT image controls the S-ON and S-OFF flags of the NAND RAM in the device. Even with a temp root shell, you can't write to a partition with its S-ON flag set. This normally includes all the partitions on the phone except the data partition, so trying to root the device requires some sort of interaction with the HBOOT image to turn off the S-ON flag for the recovery and system partitions to properly root a phone.
In short, if and until someone hacks hboot_liberty_7227_1.02.0000_101104, your phone is unrootable.

Gene Poole said:
I've been reading up on this and the skinny is that the HBOOT image controls the S-ON and S-OFF flags of the NAND RAM in the device. Even with a temp root shell, you can't write to a partition with its S-ON flag set. This normally includes all the partitions on the phone except the data partition, so trying to root the device requires some sort of interaction with the HBOOT image to turn off the S-ON flag for the recovery and system partitions to properly root a phone.
In short, if and until someone hacks hboot_liberty_7227_1.02.0000_101104, your phone is unrootable.
Click to expand...
Click to collapse
Help me out, I may be thinking in the wrong direction, but I've been dealing with my nook which is why I thought of this.
Is there not a way to write an hboot to an sd-card or connect via usb at start to make the aria think that the sd-card or the usb connection is the corrected hboot, thus being able to modify?

FroztIkon said:
Help me out, I may be thinking in the wrong direction, but I've been dealing with my nook which is why I thought of this.
Is there not a way to write an hboot to an sd-card or connect via usb at start to make the aria think that the sd-card or the usb connection is the corrected hboot, thus being able to modify?
Click to expand...
Click to collapse
There may be. When I first got my Aria, the rooting procedure involved an HTC signed update that you fooled the hboot into partially loading, then swapped the sdcard with the root package. It involved some complex timing issues where you had to run adb in a loop and plug/unplug the usb cable at appropriate times.
I've been searching the net for that procedure and I can't seem to find the right search terms, or I'm just not looking in the right places or something, but I know that's how I did my Aria before there was an unrevoked plug-n-root.

I have the procedure u are looking for i think...let me know if this is what u were after because i have an archive of saved documents I have copied from forums in the past...GOOD LUCK!
well apparently i haven't posted enough to put the links up in the post

PM me if you want the process...

xerotix said:
PM me if you want the process...
Click to expand...
Click to collapse
May I have a copy of said process? Currently the only way is to buy a very expensive hardware called XClip. I have managed to get the updated 2.2.2 Stock ROM rooted but not deodex or EXT3 FOR ap2sd trying to play with some files from another source to get hboot s off.

econcep said:
May I have a copy of said process? Currently the only way is to buy a very expensive hardware called XClip. I have managed to get the updated 2.2.2 Stock ROM rooted but not deodex or EXT3 FOR ap2sd trying to play with some files from another source to get hboot s off.
Click to expand...
Click to collapse
That process does not work with the new HBOOT. That's why unrevoked doesn't work. Having root access does not unlock NAND.
Currently, the only way known is via hardware tools.

It works. I managed a work around for 2.2.2 update
Hey everyone I am in the second phase of testing my work around with the new HTC Aria update from ATT. I managed to load the update and keep my phone rooted. I am now in the setup mode with no bootloop.
Running into a couple of issues with the new radio but I believe I know how to fix that as well. Keep you all posted and once all bugs worked out I will post my findings and HOPEFULLY MY ROOTED ROM.ZIP with instructions.
IF AT FIRST YOU DON'T SUCCEED.....TRY TRY TRY and TRY I did and I am 99% there.

econcep said:
Hey everyone I am in the second phase of testing my work around with the new HTC Aria update from ATT. I managed to load the update and keep my phone rooted. I am now in the setup mode with no bootloop.
Running into a couple of issues with the new radio but I believe I know how to fix that as well. Keep you all posted and once all bugs worked out I will post my findings and HOPEFULLY MY ROOTED ROM.ZIP with instructions.
IF AT FIRST YOU DON'T SUCCEED.....TRY TRY TRY and TRY I did and I am 99% there.
Click to expand...
Click to collapse
This might be the wrong thread. Did you manage to get around the HBOOT issue with the 2.2 update? If not, then you've just done the same thing I did the day after this release was out:
http://forum.xda-developers.com/showthread.php?t=970272

Gene Poole said:
This might be the wrong thread. Did you manage to get around the HBOOT issue with the 2.2 update? If not, then you've just done the same thing I did the day after this release was out:
http://forum.xda-developers.com/showthread.php?t=970272
Click to expand...
Click to collapse
You are right this might be the wrong thread. But I managed a work around with the new update 2.2.2 and the HBOOT 1.0X. As soon as I can confirm without a doubt that it works and will be able to repeat the process successfully with my husband's ARIA (unfortunately we love hacking things and tend to buy multiple devices) I will be more than happy to share the results.
Again, my apologies if it's the wrong thread.

econcep said:
You are right this might be the wrong thread. But I managed a work around with the new update 2.2.2 and the HBOOT 1.0X. As soon as I can confirm without a doubt that it works and will be able to repeat the process successfully with my husband's ARIA (unfortunately we love hacking things and tend to buy multiple devices) I will be more than happy to share the results.
Again, my apologies if it's the wrong thread.
Click to expand...
Click to collapse
Perhaps I misread (or we're talking past each other). You do have, in fact, HBOOT 1.02.0000 on your Aria, and managed to write to the system partition?

Yes & No. I'm stuck on couple of things. First the will temporary give me root access but then it locks up saying I don't have busybox. I'm rooted but no s-off. I also noticed when I reboot into recovery I go into CWM 2.5.0.1 but other times it boots into CWM 2.5.0.7. When that happens I loose my unknown source in settings>application. Again, if this is the wrong thread, I really am sorry.
I googled alpharev and some others who have worked on rooting. Found some cached pages from Jan when they were testing to root/s-off the Aria. Basing my work on that and couple of other devices that are similar to the Aria.

[XOOM2/XYBOARD][HOW TO] Motorola Xoom 2/Xyboard Everything Root and more!

XOOM2/Xyboard Everything root and more!
From 26/03/2014, I will no longer be updating this post as I no longer have the device and Motorola won't be upgrading the device further. Please instead of sending me PMs, go to the Q&A board or post your comment on this thread.
Note: This method will not work on Windows 8. Only Windows XP, Vista, 7, Linux and Mac OS X is supported.
Root Method - Honeycomb
1. Download the Windows version here, or the Linux/OSX version here.
2. Your Computer must have Motorola Drivers installed before rooting and connect your device with debugging on to your computer via USB. (Mac Users don't need drivers)
3. Extract the zip file from the download link, and run “run.bat” (on Windows) or “run.sh” from a terminal (on Linux/OSX)
4. Your device should reboot a few times during the process, don't worry.
5. Then you should see a finished message on the Root Method Window. At this point your device is safe to be removed from the computer.
7. As you are running Honeycomb if you are reading this then you should be receiving the ICS OTA soon. So lets backup your root so you can restore everything root after the upgrade (saves time). Download OTA Rootkeeper and backup root.
6. Well Done! You have root. Enjoy root and be safe.
Blog Post: Here
Root Method - Ice Cream Sandwich
1. Connect your Xoom2/Xyboard via USB to your Windows PC. Install Motorola Drivers from here.
2. Under Settings > Developer Options > Hit the "Enable USB Debugging" selection.
3. Download the Root Installer from here. (Says for Droid RAZR but also works on Xyboard and Xoom 2]
4. Unzip the download.
Bootstrap/Safestrap[Custom Recovery]
Waring: DO NOT proceed if you are inexperienced. bootstrap is messy and is only needed once we have ROMs cooking. All questions about the recovery ask in the developer thread.
1. Install the Bootstrap APK file.
2. Allow Superuser Powers.
3. Read the instructions which is displayed on the user interface.
5. You will now see a splashscreen after you reboot (before boot animation), here you can decide if you want to enter recovery or continue with boot.
-Method Under Constuction-
Unroot or temporary unroot
Temp Unroot - If you need to unroot for any reason and come back at any time, then install OTA Rootkeeper and then select the option "temp unroot). This will remove root without restarting and you can restore by a touch of a button.
Full remove of Root - If you want to complety remove root all together, if you need to send in your device for repair or trading your device. Install Ginger Unroot and continue with the onscreen instructions. This application has confirmed to work on the Xoom2/Xyboard.​

Doing it right now

Linux version has a wrong link or not uploaded yet

mdcykkk9 said:
Linux version has a wrong link or not uploaded yet
Click to expand...
Click to collapse
Should be working now.

Thx is working now . i just made a donation to his paypal account. i hope for future support for the tablet .

Thanks, is good news. Now we just need that we have updates to fix bugs, and if it can be ics ...
This is worth a donation to continue the work.

édit : error, sorry, it's ok

Working well ! Thank you.
I rooted my Xoom 2 ME bought in France.
But I cannot update to 3.2.2 ???
My build 1.6.0_218.3-MZ607 ,current version 3.2

Would this work for Xoom 1 wi-fi version ?

ouatitw said:
Would this work for Xoom 1 wi-fi version ?
Click to expand...
Click to collapse
This root method should work on all Motorola Devices running honeycomb or gingerbread. Try it out and see if it does
Sent from my Motorola Xoom 2

I did the US ICS update on My UK Xoom so im on 4.03 at the moment - i believe Motorola added some file which prevents me so far from rooting with the current one click programs ? so would it be safe to try this ?

ouatitw said:
I did the US ICS update on My UK Xoom so im on 4.03 at the moment - i believe Motorola added some file which prevents me so far from rooting with the current one click programs ? so would it be safe to try this ?
Click to expand...
Click to collapse
The method is safe to try but Email Dan if you have any issues when rooting.

Thanks a lot Dan Rosenberg,
Suppose i root my device and if i need to use my warranty at later point of time.
Is there is anyway that i can hide Motorola that i have rooted my device.

luke.arran said:
The method is safe to try but Email Dan if you have any issues when rooting.
Click to expand...
Click to collapse
I wouldn't email Dan, I'd post it here... Dan probably has more than enough things going on than to answer all rooting questions on here...
This root method very well may work on the Xoom with ICS, never hurts to try it. I don't see how you can't root with an existing method though, with the Xoom being fully unlockable and all...

Elysian893 said:
I don't see how you can't root with an existing method though, with the Xoom being fully unlockable and all...
Click to expand...
Click to collapse
the thing is that maybe you can, but you might not want to Unlocking wipes all your data, apps, etc and also permanently sets a variable stating that your warranty is gone.
It might, for example, be desireable to create a backup of all your apps and data using titanium backup, which requires root, before unlocking your xoom.

Does this mean that more knowledgeable folks can create custom ROMs now, or does that still require an unlocked bootloader?

Trackz said:
Does this mean that more knowledgeable folks can create custom ROMs now, or does that still require an unlocked bootloader?
Click to expand...
Click to collapse
No, we need to figure out a bootstrap for custom roms. No custom kernels.
Also, the method to fix adb remount is reset every other boot by the kernel, init.rc rebuilds local.prop on reboot as a failsafe and can't be changed without a custom kernel...

Response to luke.arran
luke.arran said:
This root method should work on all Motorola Devices running honeycomb or gingerbread. Try it out and see if it does
Click to expand...
Click to collapse
Just to let you know this does not work on all Xoom models like you say. Here is my thread with my specs in it. I have tried it three times following the directions to a T and it never gets past;
"[*] Initiating Phase 1...
[*] This may take a few minutes, don't mind the buzzing."
I have now let it run for over an hour each time and it never goes any further and my Xoom is still not rooted. It did not even ever reboot on its own. Does anyone have any suggestions? If not I'll just use some threads 1 & 2, I got from a friend.
Thanks, InfiniteImmortal

llama-power said:
Unlocking wipes all your data, apps, etc
Click to expand...
Click to collapse
Not this method. It is supposed to unlock and root motorola devices in 10 minutes without deleting any files. When I read about this on android police I was very excited as I never rooted because I only needed Superuser for my Xoom (never was interested in ROMs) and could never justify scraping everything just for this.
I tested the files here on a windows 7 machine... if I run from command at step 2. I get su permission denied. If I run the batch file I get "failed backup" loop after the device has been detected
tried the portable one click .exe found in "Motofail: Universal Motorola Android Root Tool (Portable)" works perfect on my bionic
obviously fails to remount as it does not include local.prop from step 5. so it's not working on xoom
This is the most awesome root utility I ever came along. It took something like 6 mins to root my phone without losing any files, if I can get it to run on my Xoom this will be just a dream come true!

Update: This root method does not support the Original Xoom. Confirmed by Dan.

[Q] 1 Click Root for Xoom WIFI?

I have rooted several android phones, but always used a 1-click root. I do not know how to use the SDK, and am very nervous about trying it. Is there a 1-click root for the XOOM out there? I have a WIFI Xoom with jelly bean installed. Any help would really be appreciated!!!!

me too
mpscmedic said:
I have rooted several android phones, but always used a 1-click root. I do not know how to use the SDK, and am very nervous about trying it. Is there a 1-click root for the XOOM out there? I have a WIFI Xoom with jelly bean installed. Any help would really be appreciated!!!!
Click to expand...
Click to collapse
I second this!!

Learn how to use android sdk to execute adb and fastboot, worth learning and will save you loads of time in the future. Furthermore there are loads of tutorials and guides online already.

I second that you learn to adb. If something were to go wrong you'd have no clue what to do since you don't know how to use it.

Yea learning adb and fastboot is really important, but if you really want a one click tool use the one on my signature

I have used the android sdk to help root my Droid, my viewsonic G-tab, and even my eken tablets. And XDA has a *ton* of info. A ton.
But for peeps that have just gotten a xoom (like me) there seems to be a lot of info about rooting pre-JB. And very little about rooting a stock JB tablet.
If there's a good resource for rooting a stock JB MZ604 (wifi only tablet) that you know of, I personally would appreciate a link. 'Cause the google isn't finding it. And neither is XDA forum search.
Thanks
cranky_dan

Hmmm...
http://forum.xda-developers.com/showthread.php?t=1936534
As far as unlocking the boot loader, that is the same across all versions.
Sent from my SAMSUNG-SGH-I747 using xda premium

d3athsd00r, I will allow your hairy eyeball (in good humor) for the apparent *lack* of searching. I thanked you for your post and effort.
However, you have posted a link for an image flash. (I found it too.) And while it will effectively 'root' my device, it just ain't the same.
I guess any interest in actually rooting the xoom post-honeycomb waned after Motorola mentioned 4.1.2 was as far as it went. <sigh>
Thanks!
Dan

cranky_dan said:
d3athsd00r, I will allow your hairy eyeball (in good humor) for the apparent *lack* of searching. I thanked you for your post and effort.
However, you have posted a link for an image flash. (I found it too.) And while it will effectively 'root' my device, it just ain't the same.
I guess any interest in actually rooting the xoom post-honeycomb waned after Motorola mentioned 4.1.2 was as far as it went. <sigh>
Thanks!
Dan
Click to expand...
Click to collapse
Its the stock image with root injected. There are no root methods that allow you to root without unlocking the boot loader first (which wipes your internal storage) and then either flashing a root package with a recovery or doing an image flash. Either way it comes out to the same thing. No one is going to waste time trying to find root exploits without unlocking the boot loader when it literally takes three cmd/terminal commands to root.
Code:
reboot fastboot
fastboot OEM unlock
fastboot flash system system.IMG
Sent from my SAMSUNG-SGH-I747 using xda premium

Thanks for the response.
Of all the android devices I've had and flashed versus rooting, I rather prefer the outcome of rooting: no data loss. But you have convinced me, and I'm pretty darned stubborn.
I'll get to it during my vacations the week after next.
Dan