Database Users

Trying to root but no luck (Rogers Post-911 Patch)

Hey i'm trying to root my Rogers Dream via this method...
http://wiki.cyanogenmod.com/index.php?title=Rogers_Dream:_Rooting_(Post-911_Patch)
My problem is after completing the whole process I am still not rooted.
I think that nothing happens when i do this part...
chmod 666 /dev/mtd/mtd1
flash_image recovery /data/local/recovery.img
are there suppost to be messages after I type those in?
Basically after the whole process i can't get into recovery, and i do not have su permissions.
Thanks for any insight!

For your link, it says: "There is no text on this page".
Anyways, download RC7 (not RC29), sign in, download telnet from market, then when you have recovery.img on sdcard type in:
su
flash_image recovery /sdcard/recovery.img
and you should be rooted.
OR
follow these directions: http://theunlockr.com/2010/04/26/how-to-root-the-htc-g1dream/
OR download oneclickroot and root it that way to access "su" and flash recovery

Thanks I'll give those a try anyways heres the fixed link
http://wiki.cyanogenmod.com/index.php?title=Rogers_Dream:_Rooting_(Post-911_Patch)

e334 said:
For your link, it says: "There is no text on this page".
Anyways, download RC7 (not RC29), sign in, download telnet from market, then when you have recovery.img on sdcard type in:
su
flash_image recovery /sdcard/recovery.img
and you should be rooted.
OR
follow these directions: http://theunlockr.com/2010/04/26/how-to-root-the-htc-g1dream/
OR download oneclickroot and root it that way to access "su" and flash recovery
Click to expand...
Click to collapse
Ok the unlockr method does not work for me.
The HTC Dream is not on the compatible list for oneclickroot can anyone confirm it working?
Where can I find RC7?

have you tryed this app
http://forum.xda-developers.com/showthread.php?t=747598
just install it with a file manager and run it and you should be rooted after that download rom manager from market and install a custom recovery from there
^__^

I finally managed to get the custom recovery flashed! thanks to the xda guide
http://forum.xda-developers.com/wiki/index.php?title=Rooting_HTC_Branded_EBI1_Dreams
If I managed to flash the recovery, does that mean i have root?
Can someone please explain how to do this part? I just get an error...
run the following two fastboot commands (this will prevent issues flashing your rom)
fastboot erase system -w
fastboot erase boot
Click to expand...
Click to collapse
Will anything happen if I do not do this step?
EDIT: Seems I have root now after the app root, flashed cyanogen waiting for it to boot.

aw man you just destroyed my will live.
I was reading this entire post with intense anticipation and was thoroughly let down when I did not see you post a successful root
Any updates on this?
I just purchased a Rogers Dream to learn about rooting and to play with.
If you did have success with this tutorial could you let me know? http://forum.xda-developers.com/wiki/index.php?title=Rooting_HTC_Branded_EBI1_Dreams
I was considering following this tutorial myself!
Cheers

@bourne-nolonger
I used that method a little while ago with no issues.
The steps are easy to follow and work without issue.

Yes i was successful with XDAs procedure
My will was almost destroyed... i traded my magic for this dream... but now im happy

awsome!
thanks for the feedback guys.
definitely looking forward to finally getting a chance to root my G1.
Will report my results!
Cheers

quick question.
in the wiki under "D - Installing an engineering SPL" step 11 says to
Code:
"powerdown - fastboot oem powerdown"
I was wondering what exactly is meant by this?
I looked at fastboot.exe but none of the command line options seem to have a "powerdown" option. They do however have a reboot/reboot-bootloader, is this what step 11 is referring to?
Sorry I should also ask: Can I follow the wiki that describes how to flash CM5+ to flash CM6.1.0? Is the process the same basically between the two versions of CM?
I want to try 6.1.0 instead of going with 5+
Cheers

bourne-nolonger said:
I was wondering what exactly is meant by this?
I looked at fastboot.exe but none of the command line options seem to have a "powerdown" option. They do however have a reboot/reboot-bootloader, is this what step 11 is referring to?
Click to expand...
Click to collapse
That is because its the oem command and the second option (powerdown) is up to the phone to parse..
Once you run 'fastboot erase system -w' and return to recovery you can install any rom you wish just make sure you have an ebi1 kernel.
You also may wish to check out the 2708+ compatible kernel thread to get some extra ram, warning however if you are a rogers customer you will need to sign the e911 wavier before you can switch to any other radio otherwise they will cut your data service.. if you are with another carrier there is no such requirement.

Thanks for explaining step 11. Not sure I fully understand, but I'll do some additional reading.
I was looking at some of your threads before. I thought the 15mb ram expansion wasn't available for the rogers dream?
This is my first time flashing, could I flash cm first then maybe try yours later?
The g1i have luckily isn't my main phone. I bought it just to get comfortable with rooting and flashing.
Cheers
Sent from my Nexus One using Tapatalk

I managed to successfully root and flash CM6 onto my G1.
I see why people were complaining about performance issues.
Its a little sluggish, but usable (mind you are I am not using this as my daily phone)
thanks to XDA for a beginners guide to rooting this phone!

sorry bout this guys but im just curious.. i thought rc7 was for europe only... i honestly am confused now lol i know for me its rc29 im in america and you are in canada is the device really that different even though its such a short distance..? i apologize if its a stupid question...

[REF] [NS4G] Stock ROMs | How To Root/Unroot | OTA Files & Images

Why another post for stock files? Well for a few reasons, mainly the lack of quality found amongst the files in similar threads on the web. When I got my Nexus S 4G I took a look around the web, downloaded the stock roms that were floating around and noticed they were very flawed. The update scripts used in them were poorly done, seem to be the result of copy and pasting many update scripts together. The boot.imgs were also flawed, some of them even 8mbs in size, the stock boot.img is 2.8mb. After running them through one of my scripts, I also noticed many apps were not even zipaligned. Needless to say I did not flash these files. I took it upon myself to remake all these files. Stock files are essential to a development phone and can save many people in a sticky situation. Also, I have noticed that the official stock software images have not been released yet, so I went ahead and uploaded those for you all as well. These images include radio, boot, recovery, system, userdata, and bootloader. Please note, this post is not intended to bash anyone's work. I am simply trying to provide much needed files to the community. If you have any questions feel free to ask. Also, I may forget to keep this post updated so please check the downloads page on my website as it will always be maintained.
http://www.peteralfonso.com/p/downloads.html
Downloads: (Most can also be found in ROM Manager)
GRJ06D Stock Rooted ROM (Odexed)
GRJ22 Stock Rooted ROM (Odexed) (DeOdexed)
GRJ90 Stock Rooted ROM (Odexed) (DeOdexed)
GWK74 Stock Rooted ROM (Odexed) (DeOdexed)
GRJ22 Software Images
GRJ22 from GRJ06D OTA
GRJ90 from GRJ22 OTA
GWK74 from GRJ90 OTA
D720SPRKD8 Radio
D720SPRKE5 Radio
D720SPRKE1 Radio
Tethering Fix For Android 2.3.5 ROMs
How To: Root Nexus S 4G
1. Download GWK74 Stock Rooted ROM from above
2. Download CWM Recovery
3. Open a terminal and use the following commands:
Code:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo4g.img
4. Navigate to "recovery" in the bootloader and select it
5. Navigate to "mounts and storage" > "mount USB storage"
6. Place the GWK74 Stock Rooted ROM on your sdcard
7. Navigate to "Unmount" > "+++++Go Back+++++"
8. Navigate to "install zip from sdcard" > "choose zip from sdcard" > choose "GWK74ODEXED.zip" > choose "Yes – Install GWK74ODEXED.zip"
9. Navigate to "reboot system now" and enjoy.
How To: Return Nexus S 4G To Stock
1. Download the GRJ22 Images from above
2. Open a terminal and use the following commands:
Code:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock

Pete did you get a Nexus S 4G? Thought you were on Verizon?
Any ROM development plans?
Sent from my GT-P7510 using XDA Premium App

oxeneers said:
Pete did you get a Nexus S 4G? Thought you were on Verizon?
Any ROM development plans?
Sent from my GT-P7510 using XDA Premium App
Click to expand...
Click to collapse
My work provided me with the Nexus S 4G. I still use my OG Droid and will continue to develop for it. I have successfully built an entire AOSP ROM for the Nexus S 4G and am running it now, not sure what I will release for this device though seeing as how it is for work. Time will tell...right now I am really busy though.

Yea, I know the stuff I posted is crap I am not a dev and say that in the threads on several occasions. I am very, very glad you posted this, I will post a HUGE link in my thread to this also. Look forward to the awesomeness you will bring to this phone

mikeyinid said:
Yea, I know the stuff I posted is crap I am not a dev and say that in the threads on several occasions. I am very, very glad you posted this, I will post a HUGE link in my thread to this also. Look forward to the awesomeness you will bring to this phone
Click to expand...
Click to collapse
Really hope I didn't offend anyone, that was not my intentions. Having said that the only way to learn is to try to put things together yourself, compare them to others, etc. I was there not long ago. Keep it up and soon you will know more than you imagined.

You plan on making a ROM for the NS4G? You also mentioned that the ROM's that were out there were not zipaligned. Is the stock version posted above zipaligned?

dalvarez7 said:
You plan on making a ROM for the NS4G? You also mentioned that the ROM's that were out there were not zipaligned. Is the stock version posted above zipaligned?
Click to expand...
Click to collapse
Not sure what my plans are as of now to be honest. You can guarantee anything I release will be zipaligned.

BuglessPete said:
Not sure what my plans are as of now to be honest. You can guarantee anything I release will be zipaligned.
Click to expand...
Click to collapse
I for one would be very grateful if you made us a ROM for the NS4G.

well thanks for this, you are correct on many points except one.. the stock images were released but most people had to work to get them

You are my HERO! Thx man

Looks like the GRJ06D file did not upload right, I will drive to the library tomorrow and reupload. I live in the country where there is no internet lol.

Sweet! Can you post a deodexed rom for the GRJ22? I would love to start changing some of the stock apks for the ones in CM7

obsanity said:
Sweet! Can you post a deodexed rom for the GRJ22? I would love to start changing some of the stock apks for the ones in CM7
Click to expand...
Click to collapse
Sure, once I get some free time I can deodex them.

Im having issues flashing the recovery... Im somewhat new to flashing via adb got it all except recovery. Bootloader is unlocked but when tring via adb I just get error cannot load.. Any suggestions? Thx kindly

Thanks were off to a great start

tandxcstar1 said:
Im having issues flashing the recovery... Im somewhat new to flashing via adb got it all except recovery. Bootloader is unlocked but when tring via adb I just get error cannot load.. Any suggestions? Thx kindly
Click to expand...
Click to collapse
Please disregard this... I figured it out after some trial and error. Was able to flash recovery. One more question... Does this receovery stick or no? I know when I had my epic and had quickboot it would not allow to boot into recovery. thx again for your hard work on this. After reading the 100+ methods of rooting I was pleased to see this. Thx again

edit: nevermind

BuglessPete said:
Why another post for stock files? Well for a few reasons, mainly the lack of quality found amongst the files in similar threads on the web. When I got my Nexus S 4G I took a look around the web, downloaded the stock roms that were floating around and noticed they were very flawed. The update scripts used in them were poorly done, seem to be the result of copy and pasting many update scripts together. The boot.imgs were also flawed, some of them even 8mbs in size, the stock boot.img is 2.8mb. After running them through one of my scripts, I also noticed many apps were not even zipaligned. Needless to say I did not flash these files. I took it upon myself to remake all these files. Stock files are essential to a development phone and can save many people in a sticky situation. Also, I have noticed that the official stock software images have not been released yet, so I went ahead and uploaded those for you all as well. These images include radio, boot, recovery, system, userdata, and bootloader.
Downloads:
GRJ06D Stock Rooted ROM
GRJ22 Stock Rooted ROM
GRJ22 Software Images
GRJ22 from GRJ06D OTA
Please note, this post is not intended to bash anyone's work. I am simply trying to provide much needed files to the community. If you have any questions feel free to ask. Also, I may forget to keep this post updated so please check the downloads page on my website as it will always be maintained.
http://www.peteralfonso.com/p/downloads.html
Please follow me on Twitter for updates.
To return your device to stock, download the GRJ22 Images and use the following commands:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
One more thing, I also noticed that these rooting guides can be made alot simpler. Simply do the following:
1. Download GRJ22 Stock Rooted ROM from above
2. Download CWM Recovery
3. Use the following commands
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
4. Navigate to "recovery" in the bootloader and select it
5. In recovery select "install zip from sdcard" > "choose zip from sdcard" > choose "GRJ22ODEXED.zip" > choose "Yes – Install GRJ22ODEXED.zip"
6. Reboot and thats it.
Click to expand...
Click to collapse
Thank you very much for this.

mikeyinid said:
Yea, I know the stuff I posted is crap I am not a dev and say that in the threads on several occasions. I am very, very glad you posted this, I will post a HUGE link in my thread to this also. Look forward to the awesomeness you will bring to this phone
Click to expand...
Click to collapse
Hey Mike, you did mention that, but my friend, a pioneer you were! I too appreciate all your time and effort and look forward to many wonderful ROMs from you in the future. Thank you for getting us started with our NS4G's!!!!!

Thanks, and your welcome. Guess everyone starts somewhere. Glad I could help in some way...
a2k said:
Hey Mike, you did mention that, but my friend, a pioneer you were! I too appreciate all your time and effort and look forward to many wonderful ROMs from you in the future. Thank you for getting us started with our NS4G's!!!!!
Click to expand...
Click to collapse
Sent from my Nexus S 4G using XDA App

Why Do All These Xoom Rooting Methods Require a Modified Boot/Kernel Image?

I'll start by saying here that I fully understand that what I'm saying may not apply to the international (non-GED) Xoom devices.
Maybe someone can shed some light on this. Why is it that every rooting method I see here seems to involve flashing some ZIP file that has a modified kernel or boot image? Seems pointless considering that, as with any other Google Experience Device, you can simply unlock your bootloader, flash Clockwork, and then flash the official Superuser.zip from androidsu.com and you're done. There's no unsecuring of the boot image, or anything. It just installs Superuser.apk, the su binary and changes the permissions on the binary.
Am I missing something here? Is there some advantage I'm not thinking of to using a custom boot image to obtain root on a Xoom?

No. Before when I first bought my xoom I just rooted it, no custom kernel or rom. Now I've used both and benefits alot. As for example some games people complain laggs, with custom kernel ya can over clock and fix some of this. Then custom roms allow ya to use features not enabled by Google on default. For example the wifi xoom can not connect ad-hoc networks like mobile hotspots. Roms include this unless you wanna do it the hard way. Another nifty feature is the USB OTG to attach hard drives which Google allows ya to do like mice and keyboards but not external drives.

oldblue910 said:
Seems pointless considering that, as with any other Google Experience Device, you can simply unlock your bootloader, flash Clockwork, and then flash the official Superuser.zip from androidsu.com and you're done. There's no unsecuring of the boot image, or anything. It just installs Superuser.apk, the su binary and changes the permissions on the binary.
Am I missing something here? Is there some advantage I'm not thinking of to using a custom boot image to obtain root on a Xoom?
Click to expand...
Click to collapse
I think you ARE missing something. The process you outlined with other GED devices is identical to the Motorola XOOM root process as well.
1. You use "fastboot oem unlock" to unlock the bootloader. (This only unlocks the bootloader so you can flash custom ones, recoveries, etc. but does NOT modify the current bootloader in any way.)
2. Flash clockwork with fastboot as well.
3. Install the Universal XOOM rooting ZIP through clockwork.
4. Done.
How is this any different?
The Universal XOOM root ZIP can be found @ http://forum.xda-developers.com/showthread.php?t=1242241 and does NOT contain any sort of modified Kernel or Boot image.
I don't know where you got your information from.

Sure it does. Take a look at the zip file (all those files in the kernel folder). Plus once it's done, stock recovery no longer auto flashes because something was changed in the boot image and the checksums don't match anymore.
Sent from my Xoom using Tapatalk

Well, I stand corrected! Yeah, I don't know why it modifies the boot image either then. I'd have just thought flashing clockwork and installing the binary should be fine.
I guess you need to talk to solarnz or one of the other more experienced XOOM devs...

sodaboy581 said:
Well, I stand corrected! Yeah, I don't know why it modifies the boot image either then. I'd have just thought flashing clockwork and installing the binary should be fine.
I guess you need to talk to solarnz or one of the other more experienced XOOM devs...
Click to expand...
Click to collapse
And that's the thing...flashing just the binaries DOES work fine, at least on my Xoom. I wonder if it has something to do with the international non-GED Xooms...
Sent from my Xoom using Tapatalk

You do need a modified initramfs to root properly.
an insecure boot.img is the most useful part of being rooted.
And with one of those you don't even need clockworkmod.
flash it with fastboot / reboot / adb remount and then just push su and superuser set suid on su (10 seconds total - far less hassle than messing with clockworkmod).

I am a little surprised no one figured out how to root before unlocking. Would sure be handy to do a titanium backup before unlocking ( which wipes everything !! ) That said, it is just a minor inconvenience. Copy some stuff to the PC and I am good to go.

oldblue910 said:
I'll start by saying here that I fully understand that what I'm saying may not apply to the international (non-GED) Xoom devices.
Maybe someone can shed some light on this. Why is it that every rooting method I see here seems to involve flashing some ZIP file that has a modified kernel or boot image? Seems pointless considering that, as with any other Google Experience Device, you can simply unlock your bootloader, flash Clockwork, and then flash the official Superuser.zip from androidsu.com and you're done. There's no unsecuring of the boot image, or anything. It just installs Superuser.apk, the su binary and changes the permissions on the binary.
Am I missing something here? Is there some advantage I'm not thinking of to using a custom boot image to obtain root on a Xoom?
Click to expand...
Click to collapse
You don't _need_ to flash an insecure kernel image; there's multiple paths to root. If you don't have a version of CWM for the device, then running the system insecure may be the only way to do it. Running the system in insecure mode does give you the ability to run adb as root amongst other things, however (so you can do things like adb remount).

Yeah I can see needing the insecure image in the case of not having ClockworkMod or if you need those extra commands in ADB. I was more just curious if running an insecure image was somehow a better practice than just flashing the androidsu.com zip. I guess it's 6 of one or a half dozen of the other in the end.
Thanks for the explanation!
Sent from my Xoom using Tapatalk

unrandomsam said:
an insecure boot.img is the most useful part of being rooted.
Click to expand...
Click to collapse
I suppose that depends on what you use root for, really. For instance, the ability to run adb as root means nothing to me really. I can count the number of times I've used adb on one hand. I more use root so I can take screenshots without hooking up to USB, and I also like having root access to the filesystem.
Plus, it seems that the insecure image is the reason why everyone says not to accept OTAs if you're running a rooted stock ROM. I've read horror stories of people accepting OTAs on a rooted stock ROM and ending up with bootloops and all kinds of other craptastic stuff. If you root with the boot image secure, you can accept OTAs and just re-root when it's done flashing.
Different strokes for different folks, right?
Sent from my Xoom using Tapatalk

mobileweasel said:
I am a little surprised no one figured out how to root before unlocking. Would sure be handy to do a titanium backup before unlocking ( which wipes everything !! ) That said, it is just a minor inconvenience. Copy some stuff to the PC and I am good to go.
Click to expand...
Click to collapse
This.
Most devices have temp root so you're able to run rooted app to fully backup before unlocking it. I've been holding off rooting on my wife's xoom because I don't want to wipe her saved data, but im really itching to mess with it, hehe. I heard with ICS you can do a full backup with adb, I believe you use the " adb backup" method.

The insecure boot image is need for two reasons.
1) without it you would not be able to adb mount the partitions while inside the Android os.
2) every time you boot into Android, a script it's ran to check for stock recovery and overwrite it, insecure boot images disable this (you can also disable by deleting the script files)
Sent from my Nexus S 4G

[RECOVERY][4/27/2012] CWM thor 1.7c for A510

Here's an updated version from my earlier patch of thor's 1.7 recovery for the A510. This one has the proper mapping for the data partition (mmcblk0p10). I set the version number as 1.7b.
To recap:
Thor's 1.7 cwm recovery repacked with A510 stock kernel. itsmagic is disabled. overclocking does not work, since it's a stock kernel.
This is exactly the same as the one I repacked for the A200, but with the A510 stock recovery kernel and edited the kernel string to show when it boots. And also changed the fstab for /data to use mmcblk0p10.
You MUST unlock your bootloader before flashing this.
You can rename it to recovery.img and put it on your microsd card and use Acer Recovery Installer to flash it. Or you can use the following command in a terminal emulator or adb shell.
Code:
dd if=thor_recovery17b_A510.img of=/dev/block/mmcblk0p1
Give it a try and see if it works.
***Link Removed***
Cheers!
WARNING: If you downloaded the link I posted earlier that has MD5 of 1ded94b4b4f0522ca14b7070146d9a49, DO NOT USE IT! Download 1.7b above instead.
Edit: Updated to 1.7c to fix some mounting issues.

You MUST unlock your bootloader before flashing this.
please tell me how unlock A510.
thank you

Updated OP with new image to fix some reported mounting issues. Please give this a try. Also remember, that I do not have this device, so I rely on you guys to let me know what doesn't work. So far, the only feedback i've gotten is from NoThrills (Thanks buddy).

Euclid's Brother said:
Here's an updated version from my earlier patch of thor's 1.7 recovery for the A510. This one has the proper mapping for the data partition (mmcblk0p10). I set the version number as 1.7b.
Click to expand...
Click to collapse
This is awesome! Thank you. Will install now.
Dave Burbank

asdf20003 said:
You MUST unlock your bootloader before flashing this.
please tell me how unlock A510.
thank you
Click to expand...
Click to collapse
You must have the ability to send adb commands to the tablet.
adb reboot-bootloader
fastboot oem unlock
Then follow the on screen instuctions very quickly.
Sent from my SPH-D710 using Tapatalk 2

Euclid's Brother said:
Updated OP with new image to fix some reported mounting issues. Please give this a try. Also remember, that I do not have this device, so I rely on you guys to let me know what doesn't work. So far, the only feedback i've gotten is from NoThrills (Thanks buddy).
Click to expand...
Click to collapse
LOL... And there I was fixing it myself this afternoon I think we both noticed that 1 line that was missing in the fstab

After changing tab to use the named devices like the stock recovery, it seemed like it was having even more trouble, so I reverted back to the original fstab and just changed data to mmcblk0p10.
Is it working okay now?

is only for A510 ? if i try for A501 is can be?

euclid, what has changed with the new recovery kernel, i can't get twrp to boot.i sent a gtalk request.

D3v17 said:
is only for A510 ? if i try for A501 is can be?
Click to expand...
Click to collapse
strictly for the A510. It will not work on anything else! The data partition is in a different place.

ibsk8 said:
euclid, what has changed with the new recovery kernel, i can't get twrp to boot.i sent a gtalk request.
Click to expand...
Click to collapse
Who knows. try repacking it with the stock recovery kernel. You'll also need to update the partition device for Data in recovery.fstab

Euclid's Brother said:
You must have the ability to send adb commands to the tablet.
adb reboot-bootloader
fastboot oem unlock
Then follow the on screen instuctions very quickly.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Brother,
Is the above applicable to A500 OTA ICS 4.0.3 bootloader?
Sent from my A500 using Tapatalk 2

wcrov said:
Brother,
Is the above applicable to A500 OTA ICS 4.0.3 bootloader?
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
NO
He stated already. JUST for the A510 which is the new Tegra 3 tablet. Replacement for the old 500 series

recovery successfully installed.
and now? what is the next step ;-)
how to help people from there to go further in rom cooking and all that stuff ?
anyway, thanks a lot euclid's brother,

I thought this version of thors recovery was not GPL compliant. If it is not be careful, the angry hordes will decend on this thread and you will get banned. Even mentioning of the name of thor is enough to cause you grief.....oh wait, its recovery, not his rom, so those who have a bone to pick turn a blind eye...carry on.

If this is based on the work of a banned developer then I'm afraid we do not wish for it to be posted here.
I'd suggest taking an alternative recovery to amend.

fastboot for Aussie Razr M 77.176.16.XT905.Telstra.en.AU

Hi all
Just wondering if anyone has a copy of the official Australian Razr M release firmware.
77.176.16.XT905.Telstra.en.AU
Always good to have a fallback system image!
Thanks in advance

wintermute000 said:
Hi all
Just wondering if anyone has a copy of the official Australian Razr M release firmware.
77.176.16.XT905.Telstra.en.AU
Always good to have a fallback system image!
Thanks in advance
Click to expand...
Click to collapse
Hi, I am also looking for the same firmware, managed to root the phone using Motofail2go but unable to use Clockworkmod to backup or load other firmware. Now when I try to Erase the phone I get the AP Fastboot Flash Mode (s) Device is looked Boot Failure. Luckily pressing the power button gets me back to a working phone. I have also unrooted the phone using DoomLord unrooting script but still the same boot up error. I know now the bootloader is locked by Motorola, this is why I need the original Telstra firmware.
I will donate $ 20 by Paypal to anyone that posts a working 77.176.16.XT905.Telstra.en.AU firmware that I can use and fixes the boot issue.

ozsultan said:
Hi, I am also looking for the same firmware, managed to root the phone using Motofail2go but unable to use Clockworkmod to backup or load other firmware. Now when I try to Erase the phone I get the AP Fastboot Flash Mode (s) Device is looked Boot Failure. Luckily pressing the power button gets me back to a working phone. I have also unrooted the phone using DoomLord unrooting script but still the same boot up error. I know now the bootloader is locked by Motorola, this is why I need the original Telstra firmware.
I will donate $ 20 by Paypal to anyone that posts a working 77.176.16.XT905.Telstra.en.AU firmware that I can use and fixes the boot issue.
Click to expand...
Click to collapse
Out of curiosity what CWM did you try to flash?
You do know that you CAN unlock your bootloader right? exact same procedure as Razr I. Yeah the moto website doesn't mention telstra Razr M model blah blah blah it works as confirmed by Ausdroid editor in this thread.
http://forum.xda-developers.com/showthread.php?p=33777574#post33777574

wintermute000 said:
Out of curiosity what CWM did you try to flash?
You do know that you CAN unlock your bootloader right? exact same procedure as Razr I. Yeah the moto website doesn't mention telstra Razr M model blah blah blah it works as confirmed by Ausdroid editor in this thread.
http://forum.xda-developers.com/showthread.php?p=33777574#post33777574
Click to expand...
Click to collapse
Hi I used CWM from Google Play and selected the Motorola Photon Q from CWM, maybe a mistake but no RAZR M was listed.
I registerd on the Motorola site to get the unlock key but there is a quite a process to complete the excersice. Rather just have my stock rom back and forget about rooting for now.

ozsultan said:
Hi I used CWM from Google Play and selected the Motorola Photon Q from CWM, maybe a mistake but no RAZR M was listed.
I registerd on the Motorola site to get the unlock key but there is a quite a process to complete the excersice. Rather just have my stock rom back and forget about rooting for now.
Click to expand...
Click to collapse
I dunno how experienced you are at this so I apologise if I'm getting mixed up here but:
a.) You will NEVER flash ANY RECOVERY aside from stock without unlocking your bootloader, and you don't flash CWM from google play (not even sure what you're referring to!!!). You CAN flash recoveries from rom manager if your bootloader is unlocked and you have root.
b.) The only recovery I've seen around the place confirmed for Razr M (unlocked bootloader) is this one
http://aosp.us/?p=294
If you think the steps in unlocking bootloader is too hard you shouldn't even attempt it. Sorry to say but thats pretty much standard stuff for flashing recoveries etc. !!!! (having drivers installed, using fastboot via command line etc.)

wintermute000 said:
I dunno how experienced you are at this so I apologise if I'm getting mixed up here but:
a.) You will NEVER flash ANY RECOVERY aside from stock without unlocking your bootloader, and you don't flash CWM from google play (not even sure what you're referring to!!!). You CAN flash recoveries from rom manager if your bootloader is unlocked and you have root.
b.) The only recovery I've seen around the place confirmed for Razr M (unlocked bootloader) is this one
If you think the steps in unlocking bootloader is too hard you shouldn't even attempt it. Sorry to say but thats pretty much standard stuff for flashing recoveries etc. !!!! (having drivers installed, using fastboot via command line etc.)
Click to expand...
Click to collapse
Hi Thanks for your help and comments, I have rooted my old HTC Desire using Unrevoked in the past and flashed a Cyanogen mod and a LeeDroid mod without any problems so I thought I would try the RAZR M. Maybe the boot loader was different or not locked. I was able to go into recovery mode and select the cooked zipped roms from the SD card. I can not find any roms for the Aussie RAZR M either, I guess that is what you are looking for and concerned about updating the the JB from for the Verizon version as the radio may be different.
Anyway, the Motorola UI is not so bad and I especially like to start page with the circles. Hopefully JB update will come OTA soon. I hope that the JB update will return my phone to stock and the Bootloader error does not come up anymore. All is fine for now but if I have to wipe my phone and start again I can not do it. Have you ended up using your Motorola unlock code to unlock the boot loader ?
I am not completely a newbie

ozsultan said:
Hi Thanks for your help and comments, I have rooted my old HTC Desire using Unrevoked in the past and flashed a Cyanogen mod and a LeeDroid mod without any problems so I thought I would try the RAZR M. Maybe the boot loader was different or not locked. I was able to go into recovery mode and select the cooked zipped roms from the SD card. I can not find any roms for the Aussie RAZR M either, I guess that is what you are looking for and concerned about updating the the JB from for the Verizon version as the radio may be different.
Anyway, the Motorola UI is not so bad and I especially like to start page with the circles. Hopefully JB update will come OTA soon. I hope that the JB update will return my phone to stock and the Bootloader error does not come up anymore. All is fine for now but if I have to wipe my phone and start again I can not do it. Have you ended up using your Motorola unlock code to unlock the boot loader ?
I am not completely a newbie
Click to expand...
Click to collapse
No waiting for
- backup stock image for obvious reason!
- something to actually flash to appear!
BTW check this thread http://forum.xda-developers.com/showthread.php?p=33789915#post33789915 the comments from apacheo who has confirmed unlock and recovery install (TWRP though not CWM)

wintermute000 said:
No waiting for
- backup stock image for obvious reason!
- something to actually flash to appear!
BTW check this thread http://forum.xda-developers.com/showthread.php?p=33789915#post33789915 the comments from apacheo who has confirmed unlock and recovery install (TWRP though not CWM)
Click to expand...
Click to collapse
Thanks. did you mean now waiting, I guess u could mean either as apacheo has something available ? Looks like apacheo might be getting my $20 via paypal. So with the recommendation from apachio do I still have to unlock the booter. If yes, can this only be done via the Motorola site unlock code?
Will the stock Telstra image from apacheo fix my boot failure issue ? Will I need to have a rooted RAZR M and loader (TWRP) to load the file?
Thanks appreciate your help.

You shouldn't need to unblock bootloader to push the stock image. If its stock you should be able to flash it.
The whole point of unlocking is to be able to push NON OFFICIAL stuff however not having seen that image I can't confirm. e.g. Maybe because he extracted it himself its not signed like an official moto image so you may need to unlock.
If he has extracted a fastboot image it will INCLUDE stock recovery and you flash it via fastboot command line utility. Thats better than a ROM you have to flash with a recovery because it lets you roll back even if you screw your recovery.
All in all, ask him yourself, I'm only speculating based on first principles
BTW android manufacturers have gotten a lot more anal since desire, and yeah back then a lot of stuff was unlocked, now pretty much only Sammy ships unlocked bootloaders. I'd say that back then you could probably unlock the bootloader pretty easily so you don't remember jumping through hoops.

ozsultan said:
Thanks. did you mean now waiting, I guess u could mean either as apacheo has something available ? Looks like apacheo might be getting my $20 via paypal. So with the recommendation from apachio do I still have to unlock the booter. If yes, can this only be done via the Motorola site unlock code?
Will the stock Telstra image from apacheo fix my boot failure issue ? Will I need to have a rooted RAZR M and loader (TWRP) to load the file?
Thanks appreciate your help.
Click to expand...
Click to collapse
The stock recovery img is probably not going to fix your device.. sounds like you probably need the boot image, but how'd you manage to corrupt that?

apacheo said:
The stock recovery img is probably not going to fix your device.. sounds like you probably need the boot image, but how'd you manage to corrupt that?
Click to expand...
Click to collapse
Hi Apacheo, thanks for the reply, my procedure was as per my first post yesterday. Using Clockworkmod Rom Manger app I picked the Motorola Photon Q for Flash Alternate Recovery as this was the only close Motorola phone to the Razr M. (MY BAD) Maybe that was the problem. I tried to back up the existing rom using Clockworkmod but again got the AP Fastboot Flashmode error.
How do I get the boot image and load that? Meanwhile I have unrooted the phone and can use it. Just can't do a factory data reset and start with a new slate if I have to. Just hangs on the AP Fastboot Flashmode (S) black and white Device is locked screen.
Thanks, I was hoping to lose that $20 to u.

Flashing the stock recovery using fastboot is probably the best start.
I'll upload the recovery image and post the URL here. Wait a moment.
Sent from my XT905 using xda app-developers app
---------- Post added at 08:01 PM ---------- Previous post was at 07:56 PM ----------
Here's the stock recovery image:
http://db.tt/A5veTD0u
Sent from my XT905 using xda app-developers app

apacheo said:
Flashing the stock recovery using fastboot is probably the best start.
I'll upload the recovery image and post the URL here. Wait a moment.
Sent from my XT905 using xda app-developers app
---------- Post added at 08:01 PM ---------- Previous post was at 07:56 PM ----------
Here's the stock recovery image:
http://db.tt/A5veTD0u
Sent from my XT905 using xda app-developers app
Click to expand...
Click to collapse
Thanks Apacheo, I assume I can use RSD Lite 5.4.6.4, how to open the 10 MB RAW file ? I know RAW as a picture file from a camera. Does the 10 MB file contain the whole Telstra ROM ?

ozsultan said:
Thanks Apacheo, I assume I can use RSD Lite 5.4.6.4, how to open the 10 MB RAW file ? I know RAW as a picture file from a camera. Does the 10 MB file contain the whole Telstra ROM ?
Click to expand...
Click to collapse
No idea about RSDLite, you use Fastboot to flash that, and it's a raw dump of the Recovery partition. Flash it like this:
fastboot flash recovery recovery-file.raw
The extension is irrelevant, you could equally rename it .img (which is the standard for fastboot files) but it won't make any difference. It's not the whole Telstra ROM, just the recovery partition. The whole ROM would be something like 600 mb, and as I've modified my system partition (i.e. rooted it) you may not want that, and with only 3G internet, I couldn't upload it anyway

apacheo said:
No idea about RSDLite, you use Fastboot to flash that, and it's a raw dump of the Recovery partition. Flash it like this:
fastboot flash recovery recovery-file.raw
The extension is irrelevant, you could equally rename it .img (which is the standard for fastboot files) but it won't make any difference. It's not the whole Telstra ROM, just the recovery partition. The whole ROM would be something like 600 mb, and as I've modified my system partition (i.e. rooted it) you may not want that, and with only 3G internet, I couldn't upload it anyway
Click to expand...
Click to collapse
Hi apache, thanks again, HELP.
OK, I press vol up and vol down and press the power key at the same time. I get the menu boot load selection, availlable boot modes if I pick recovery or AP fastboot I still get back to the AP Fastboot Flashmode (s) screen Device is locked Status Code:0
I assume I get into recovery mode and use your raw file from my SD card to update the recovery partition. What am I doing wrong?

incorrect, you flash via fastboot command line in.... fastboot mode (not recovery mode)

Hey,
I'm hoping to help you guys out. First I have a couple of questions.
1) is your device bootloader unlocked?
2) are you rooted?
If so I have methods to create a backup XML file for you.

jimmydafish said:
Hey,
I'm hoping to help you guys out. First I have a couple of questions.
1) is your device bootloader unlocked?
2) are you rooted?
If so I have methods to create a backup XML file for you.
Click to expand...
Click to collapse
If you have methods to recover an Australian modem IMG (instead of the Verizon-based one) then I'm all ears.. because until I find an AU modem, my phone is now completely unusable.. whoops :/

apacheo said:
If you have methods to recover an Australian modem IMG (instead of the Verizon-based one) then I'm all ears.. because until I find an AU modem, my phone is now completely unusable.. whoops :/
Click to expand...
Click to collapse
We can work on this, do you have access to another AU M? Plus this may be easier via gtalk or email.

jimmydafish said:
We can work on this, do you have access to another AU M? Plus this may be easier via gtalk or email.
Click to expand...
Click to collapse
If I had another, I'd just root it and dd the modem image off and flash it on the broken one.. sadly I don't
I managed to screw it up by flashing the VZW ICS stock, so I could get the JB update on.. I deliberately didn't flash the modem from the VZW ICS stock, and I modified the JB update so it wouldn't apply any changes to the modem... but seemingly, I missed a couple of lines (checking the updater-script, I missed a couple that messed with the modem) so it's completely wrecked. Says the SIM is invalid, and won't detect or connect to any UMTS or GSM carriers here.
If someone else with a rooted Aussie RAZR M is able to step up to assist, it'd be great.
I'll also PM you my details jdf.