sorry guys for my english , im new to this forums, i dont know if this has been posted already but i looked it up in the whole forum and i didnt found nothing about this problem,
my problem is the following :
i have a tmobile g1, and i"ve been trying to root it but i 've been having problem flashing a recovery image.
i have followed every tutorial in this forum and tmobile forum ,but the results are the same , i downgraded my g1 to rc29 with the dream,nbh file ,then i put the recovery.img on the root of my sdcard and the hardspl.zip
everything goes well , i type telnetd ,and i downloaded telnet from the market, so when im typing
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system this part goes well i get the pound prompt the i type
# cd sdcard,,, and i type " ls " to see if the file are on the sdcard. ok everything is in the right place
# flash_image recovery recovery.img " then when im typing this , i get the error
mtd:erase failure at 0x001c0000 (I/O) error
mtd: skipping write block
then i rebooted the phone to see if everything went well , im pressing home+power i get the rainbow screen .. i "ve been having this problem since 2009 , any help with this .................... also i have tried to erase the partition with this command
cat /dev/zero > /dev/mtd/mtd2
but nothing seems to be working .. thanks
i hope someone can help me thanks and sorry if this have been post it
dethsector said:
sorry guys for my english , im new to this forums, i dont know if this has been posted already but i looked it up in the whole forum and i didnt found nothing about this problem,
my problem is the following :
i have a tmobile g1, and i"ve been trying to root it but i 've been having problem flashing a recovery image.
i have followed every tutorial in this forum and tmobile forum ,but the results are the same , i downgraded my g1 to rc29 with the dream,nbh file ,then i put the recovery.img on the root of my sdcard and the hardspl.zip
everything goes well , i type telnetd ,and i downloaded telnet from the market, so when im typing
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system this part goes well i get the pound prompt the i type
# cd sdcard,,, and i type " ls " to see if the file are on the sdcard. ok everything is in the right place
# flash_image recovery recovery.img " then when im typing this , i get the error
mtd:erase failure at 0x001c0000 (I/O) error
mtd: skipping write block
then i rebooted the phone to see if everything went well , im pressing home+power i get the rainbow screen .. i "ve been having this problem since 2009 , any help with this .................... also i have tried to erase the partition with this command
cat /dev/zero > /dev/mtd/mtd2
but nothing seems to be working .. thanks
i hope someone can help me thanks and sorry if this have been post it
Click to expand...
Click to collapse
ok man, first off you have to be on android 1.5 not 1.0 according to every guide and me haha, when on rc29 you have to downlad this file called signed-kila-ota-148830.de6a94ca just google it and download it, put it on sdcard and rename it to update turn phone off and go into recovery pressing home and power together, press alt+L when you see the triangle with the sign and then alt+s to update to 1.5 wait and boot, setup.... then use this apk i uploaded, install it with linda or any file manager from your phone, download amonra recovery v1.6.2 from the forum (http://forum.xda-developers.com/showthread.php?p=4647751#post4647751) and put it on your sdcard then go to the app flashrecovery open it and press backup recovery image or whatever it says at the bottom of the screen then you type this sdcard/recovery-RA-dream-v1.6.2.img and then press flash custom recovery image and you are pretty much done, power off and power on pressing home key and check if is there.... hope i helped
etu_aty said:
ok man, first off you have to be on android 1.5 not 1.0 according to every guide and me haha, when on rc29 you have to downlad this file called signed-kila-ota-148830.de6a94ca just google it and download it, put it on sdcard and rename it to update turn phone off and go into recovery pressing home and power together, press alt+L when you see the triangle with the sign and then alt+s to update to 1.5 wait and boot, setup.... then use this apk i uploaded, install it with linda or any file manager from your phone, download amonra recovery v1.6.2 from the forum (http://forum.xda-developers.com/showthread.php?p=4647751#post4647751) and put it on your sdcard then go to the app flashrecovery open it and press backup recovery image or whatever it says at the bottom of the screen then you type this sdcard/recovery-RA-dream-v1.6.2.img and then press flash custom recovery image and you are pretty much done, power off and power on pressing home key and check if is there.... hope i helped
Click to expand...
Click to collapse
You, apparently, don't know what you're talking about.
1) The first rootable exploit was found when firmware version was 1.0. You do NOT need to update to root.
2) The root exploit present in 1.5 was already present already in 1.0, so the same rooting procedure should work fine in 1.0 as it does in 1.5.
@OP: By the sounds of it, it would appear that your NAND may be SHOT... which means that you're going to have to approach this using a different avenue. Specifically, you're going to need to set up your cache and misc partitions for an SPL update from a running system. You have root, so that should be possible. You may need to modify and/or pull some files from a recovery system in order to accomplish this... if you can get the SPL updated to 1.33.2003, then you will have fastboot capability, which makes the recovery partition redundant -- you will be able to boot an external recovery and bypass the whole problem.
i "ve followed all instruction , but i cant put the device into fastboot because the defaulth bootloader the one with the rainbow does not support fastboot , fastboot is only for engineering spl ,
dethsector said:
i "ve followed all instruction , but i cant put the device into fastboot because the defaulth bootloader the one with the rainbow does not support fastboot , fastboot is only for engineering spl ,
Click to expand...
Click to collapse
then... sorry man i got nothing
i dont know men but there should be a way to fix this , this happenned way back when cupcake was released , i didnt want to wait for tmobile to roll out the update , then i just did it manually , after that the problem with the mdt:erase failure started , i hope wrote haykuro about this , but he didnt answer .
dethsector said:
i dont know men but there should be a way to fix this , this happenned way back when cupcake was released , i didnt want to wait for tmobile to roll out the update , then i just did it manually , after that the problem with the mdt:erase failure started , i hope wrote haykuro about this , but he didnt answer .
Click to expand...
Click to collapse
haykuro doesn't know ANYTHING. He is a kid with no experience, who accidentally stumbled onto something unreliable, and talked a thousand people into bricking their phones.
I've already given you your options on this. You have the choice of following my suggestion and developing something to fix your problem, or you can completely give up. Those are your options.
dethsector said:
sorry guys for my english , im new to this forums, i dont know if this has been posted already but i looked it up in the whole forum and i didnt found nothing about this problem,
my problem is the following :
i have a tmobile g1, and i"ve been trying to root it but i 've been having problem flashing a recovery image.
i have followed every tutorial in this forum and tmobile forum ,but the results are the same , i downgraded my g1 to rc29 with the dream,nbh file ,then i put the recovery.img on the root of my sdcard and the hardspl.zip
everything goes well , i type telnetd ,and i downloaded telnet from the market, so when im typing
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system this part goes well i get the pound prompt the i type
# cd sdcard,,, and i type " ls " to see if the file are on the sdcard. ok everything is in the right place
# flash_image recovery recovery.img " then when im typing this , i get the error
mtd:erase failure at 0x001c0000 (I/O) error
mtd: skipping write block
then i rebooted the phone to see if everything went well , im pressing home+power i get the rainbow screen .. i "ve been having this problem since 2009 , any help with this .................... also i have tried to erase the partition with this command
cat /dev/zero > /dev/mtd/mtd2
but nothing seems to be working .. thanks
i hope someone can help me thanks and sorry if this have been post it
Click to expand...
Click to collapse
Shouldn't this be in the general Q&A section, and not the development section?
allright men, so how im gonna update the spl to 1.33.2003 without gettin into fastboot mode , thats the only way to do that right ? when i downgraded the g1 into 1.0 , i turn it off , then i press home+back and it went into recovery , so i press alt L then alt S , it say something about verifying update , reading update , then it says E:cannot read (5 files) , that means im not rooted it so i cant use any update.zip , then i tried updating to cupcake and it worked so while im in 1.5 i turn the phone off and turn it back on pressing home+back , and it went directly to the rainbow screeen
that means after i update the phone to cupcake , i couldnt even put the phone into recovery mode cuz it went into the rainbow screen thats weird right , cuz it doesnt matter what firmware you onto , the phone it suppose to go into recovery mode no matter what , thats why im finding weird too
dethsector said:
allright men, so how im gonna update the spl to 1.33.2003 without gettin into fastboot mode , thats the only way to do that right ? when i downgraded the g1 into 1.0 , i turn it off , then i press home+back and it went into recovery , so i press alt L then alt S , it say something about verifying update , reading update , then it says E:cannot read (5 files) , that means im not rooted it so i cant use any update.zip , then i tried updating to cupcake and it worked so while im in 1.5 i turn the phone off and turn it back on pressing home+back , and it went directly to the rainbow screeen
that means after i update the phone to cupcake , i couldnt even put the phone into recovery mode cuz it went into the rainbow screen thats weird right , cuz it doesnt matter what firmware you onto , the phone it suppose to go into recovery mode no matter what , thats why im finding weird too
Click to expand...
Click to collapse
Don't hold home and back. Just hold home when you turn it on.
Related
I would like to give thanks to JesusFreke who helped me to understand this process !!!! Please show him some love and make good gestures for his work….. Also to all the other people and sites who made this possible including Koush !!! I take no credit for this just posting it to help people like me, who dont know to much about this.
First…. You need to install a google android usb driver so you can use the adb program. (It lets you push and pull files to/from the phone, and you can open up a shell with it to).
Download the driver file (http://dl.google.com/android/android_usb_windows.zip) and
unzip it to the desktop.
On ur G1… Go menu > Settings > Applications > Development then enable the
USB debugging button.
Then connect your Android device via USB. When the Found New Hardware Wizard
appears, you'll be asked if you'd like Windows Update to search for software,
select No, not this time and click Next. Select Install from a list or specified location
and click Next. Select Search for the best driver in these locations. Browse and
select the unzipped file (android usb windows.zip). Click Finish.
Second…. Setting up the SDK
Go to http://code.google.com/android/download_list.html and download the
SDK
Unzip the file to the desktop and rename the folder to sdk
Open your command prompt (Windows Key and R)
Type “cmd” (Without the quotations)
Then "cd desktop"
Then “cd sdk”
Next “cd tools”
Now type “adb devices
After that it should say some thing like… List of devices attached HT845GZ21370
Device. If u see this abd sees your device.
Third…. Writing JesusFreke’s Recovery image
Download the zip file from this thread... http://forum.xda-developers.com/showthread.php?t=443041)
Unzip the files to the SDK tools folder
Now, in the command window, type
"adb push recovery_testkeys.img /data/local/recovery.img"
(This will copy the recovery image files to the phone)
Fourth…. Get Root working on ur G1
Download the Android Telnet Client from the Market or get it here…
http://www.koushikdutta.com/2008/11/android-telnet-client.html
Turn on your phone's WiFi. This gives your phone an IP you can reach it at.
Restart your phone
Once restarted type telnetd at the home screen and press enter – Yes….. it will
start up a Contact search, do not worry about this, just type “telnetd” and press
enter (the enter button on the keypad).
Now press connect to localhost……. (You now have root!)
Now put in this command….
“mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system”
Then “cd /system”
Then “cat /data/local/recovery.img > recovery.img”
Finally “flash_image recovery recovery.img” (Your Recovery Image is now writen)
*To make sure your Recovery Image was written…. Reboot your phone in Recovery
mode and press Alt+L. At the top it should say "using test keys" If so its written. Go
ahead and Reboot your phone by pressing the Home and Back buttons.*
Fifth…Apply JesusFreke’s modified RC30/RC8/ADP1
Go here http://forum.xda-developers.com/showthread.php?t=475381 and Download the ZIP
Now once the ZIP is downloaded rename it to “UPDATE”
Put it on the storage card
Last but not least Power off your G1 and Power it on by pressing the home key and power key
Press Alt+L (to turn on text)
Press Alt+S (to update)
And Bam you have yourself a modded RC30 G1 !!!!!!!!
ANOTHER Step by Step How-To get Modify RC30
Per user- "brandenk"
I think you need root to make the changes which is why you need to downgrade from RC30 to RC29 to take advantage of the root bug.
To downgrade using this NBH file: http://android-dls.com/wiki/index.php?title=Root_For_RC30
To gain root access: http://android-dls.com/wiki/index.php?title=Rooting_Android
To flash the recovery and install modified rc30: http://android-dls.com/wiki/index.php?title=Keeping_Root
Engineering bootloader for G1: http://forum.xda-developers.com/showthread.php?t=455860
Follow those steps, for #2 you dont need to do the beatbox mod and for step #3 use JKv1.3 instead of 1.2, then I added a step, flashing the Engineering Bootloader. Once you do those steps you will be good to go, I did this for the first time ever last night following those directions and it worked for me, and thats with my changes to the process. It took me reading through the directions like 50 times before I tried it but I went slowly and carefully and it went flawlessly.
Complete instructions for RC30 -> JFv1.3
Per "JesusFreke"
"I saw someone post this over on saurik's G1-hackers mailing list, and thought it would be useful to some of you.
It gives complete step-by-step instructions (all 23 of them ) for going from RC30 to JFv1.3.
http://www.webnetta.com/2009/01/02/t...rc30-to-jfv13/
__________________
"Whether You Think You Can or Can't, You're Right"
--Henry Ford
T-Mobile G1 - modified RC30 with root access !!!
Thanks for the step by step instructions. Been looking for something like this!
would i get brick if i unlock it with a code for ATT?
step three link should be the following:
http://forum.xda-developers.com/showthread.php?t=443041
thanks for the walk through
also the link for the modded RC30 is:
http://rapidshare.com/files/162035634/update-RC30-fullupdate-modified-testkeys-v1.1.zip
I did this last night and upgraded to RC30 but the problem is right before I started the original RC30 was downloaded and it was asking me to update my phone but I declined. So now after everything is done, is there a way I could tell if I have the modded RC30 or the original RC30?
will this work even if your phone has already been updated to the stock rc30?
i dont think so. because they patched it
johnny13oi said:
I did this last night and upgraded to RC30 but the problem is right before I started the original RC30 was downloaded and it was asking me to update my phone but I declined. So now after everything is done, is there a way I could tell if I have the modded RC30 or the original RC30?
Click to expand...
Click to collapse
yup "open a command prompt however you like (telnet, adb, terminal emulator app, etc.) and type "getprop ro.secure". If it says 0, then you're running the modified boot image. Otherwise, if it says 1, you're still running the."-JesusFreke
Still at risk??
A bit of a noob here... but check my thinking:
True/False:
1. Flashing the new recovery image will prevent any further OTA updates from being loaded unless they are signed with the test keys.
2. If 1 is true, then Google/Tmobile can still push a forced update to us if they sign it with test-keys?
If both above are true, maybe we need to look at disabling OTA updates altogether?
anyone want to make a how-to for ubuntu/*nix users?
I just tried all this (havent flashed mod rc30) and rebooted into recovery mode and I see:
Android system recovery utility
"Using Test Keys"
E:Can't open /cache/recovery/command
Is this correct? Is it supposed to say "E:Can't open /cache/recovery/command"? When I do "getprop ro.secure" I get 1. I'm afraid to try the flash like this. Im going to leave my phone off until I can figure this out...dont want a forced rc30 or a brick.
Can anyone help me??
xavier6303 said:
I just tried all this (havent flashed mod rc30) and rebooted into recovery mode and I see:
Android system recovery utility
"Using Test Keys"
E:Can't open /cache/recovery/command
Is this correct? When I do "getprop ro.secure" I get 1. I'm afraid to try the flash like this. Im going to leave my phone off until I can figure this out...dont want a forced rc30 or a brick.
Can anyone help me??
Click to expand...
Click to collapse
yes that looks right. you still get a 1 because you still need to do STEP 5. that is flashing with the modified RC30. Looks like you are set up to go. GL
it will always say that E:Can't open /cache/recovery/command i believe. just ignore it.
mack said:
yes that looks right. you still get a 1 because you still need to do STEP 5. that is flashing with the modified RC30. Looks like you are set up to go. GL
it will always say that E:Can't open /cache/recovery/command i believe. just ignore it.
Click to expand...
Click to collapse
ahh...thank you so much for the reply!
UPDATE: performed the update to rc30 and I now get a 0 for getprop ro.secure
Thanks, I just updated to the mod RC30 with a breeze. Anyways, to make sure, how do I confirm that I'm on the modded RC30?
xavier6303 said:
ahh...thank you so much for the reply!
UPDATE: performed the update to rc30 and I now get a 0 for getprop ro.secure
Click to expand...
Click to collapse
congrats...you now have modded RC30
donutman said:
Thanks, I just updated to the mod RC30 with a breeze. Anyways, to make sure, how do I confirm that I'm on the modded RC30?
Click to expand...
Click to collapse
A quote for a quote
"open a command prompt however you like (telnet, adb, terminal emulator app, etc.) and type "getprop ro.secure". If it says 0, then you're running the modified boot image. Otherwise, if it says 1, you're still running the."-JesusFreke
What are the modified recovery image and modified RC30 update? What it the difference? Why the original onces do not work?
Guys, I'm RETARDED. PLEASE HELP ME.
I was going to update to JesusFreke's RC30v1.3, but when booted up pressing HOME + END, I saw that for some reason, I didn't have the recovery image that uses the test keys while i did have the modded boot image (getprop ro.secure returned 0)
I tried following the guide here since I still had root from the adb shell, but when I tried to do it, I got stuck. When I tried to do the following line,
Code:
cat /data/local/recovery.img > recovery.img
I got this:
Code:
write: No space left on device
No problem, I thought. I'll just wipe the phone and then try it again!
It didn't work.
I then started experimenting with different things, even though I know I shouldn't have... and then I accidentally deleted my recovery.img file. ****.
As you may have surmised from the title of the post, I have root access from within the OS and from ADB and I also have the ADP1 bootloader on my phone. When I try going to the recovery menu, it just takes me to the bootloader (with the skateboarding 'droids). Also, I have installed manup's Bluestar 5 theme. I don't know since when my recovery image had reverted, but I know it was some time after I installed the ADP1 bootloader.
I've tried to do the stuff in the post mentioned above again, but it still gives me the damn
Code:
write: No space left on device
... I think it's mocking me.
The REALLY ironic part was that the first thing that I was going to do when I installed v1.3 was make a NANDroid backup.
Guys, PLEASE help me with this if you can. I know I was a retarded noob, but I'll learn from my mistakes. In the meantime, I can at least USE the phone... just with JF's RC30v1.2 and without Stericson's new theme (which I was gonna apply after backing up from NANDroid after installing RC30v1.3)
Thanks for your time,
~Ankush
The reason you are having write errors is JF has pushed the storage of /system partition to the limit. But flash_image can take any source location. Just put recovery.img in /data and then run
flash_image recovery /data/recovery.img
I saw that for some reason, I didn't have the recovery image that uses the test keys while i did have the modded boot image (getprop ro.secure returned 0)
Click to expand...
Click to collapse
This is a documented bug in v1.2. The new v1.3 recovery has a very distinct background image so there's no more ambiguity.
When I try that, I can boot into the Recovery menu, but when I try to apply the v1.3 update.zip, it fails at the "verifying update package" step and says:
Code:
E:Corrupt file:
data/recovery.img
E:Verification failed.
Installation aborted.
I redownloaded the recovery.img file and tried it again several times, but it didn't work either...
Thanks for the reply though.
~Ankush
P.S: HAPPY NEW YEAR! (at least in EST)
After you have done flash_image, rm recovery.img from /data. Also you might want to check your MD5 of update.zip
Yeah. I ended up downloading the 1.3 update again and then unzipping the recovery.img from that and applying it.
I saw the weird background along with the NANDroid 2.1 option so I applied the update.zip of the redownloaded JFv1.3 update.
I think that the main problem was the md5...
Oh well, it's all dandy now!
Thanks a BUNCH jashsu, have a happy new year!
I can get root access. I have RC29. I am trying to install the custom firmware.
This is where i am having the problems:
Install JF's ROM
Download JF's RC30 v1.41 ROM for US users or JF's RC8 v1.41 ROM for UK users or JF's ADP1.1 v1.41 ROM if you have an ADP1 to /sdcard and rename it to update.zip (when you are done it should be "/sdcard/update.zip").
Download the modified recovery and unzip it. Place the file "recovery_testkeys.img" in /sdcard
In the terminal you opened earlier (with root access) Enter the following commands in to flash the modified recovery
mount -o remount,rw /dev/block/mtdblock3 /system
cd /system
cat /sdcard/recovery_testkeys.img > recovery.img
flash_image recovery recovery.img
Reboot your phone (completely, do not enter recovery yet or your neighbors dog might die)
Once fully rebooted, power off your phone (hold power and select "Power Off"), and hold down home while you turn the power back on.
When you enter the recovery console (which should say "using test keys" if your modified recovery was flashed correctly) hit "alt+L" and then "alt+S" on your keyboard. This will flash the update.zip file that you downloaded and placed there. If you have any problems with this step you missed something above.
I type in all that stuff in telnet and reboot.
Then when I hold the home button and power on I dont see the "using test keys" I see a White triangle with an (!) in it. and a phone. My phones working fine I just cant seem to get the custom JF rom to install.
Please help me out. Thanks in advace.
is anyone havin this problem?
open your keyboard and push "Alt" + "L" when you see the triangle. You should see a menu, then push "Alt" + "S".
wow, it was that easy... i feel like an idiot. sorry for the trouble...
Hello everyone,
I have succesfully rooted my Sprint Hero, I am even using a cache app that you have to be rooted to use so I KNOW I am rooted. The only problem is NO MATTER WHAT I try I can not successfully flash the recovery img. It shows as flashing ok but when I go to boot in recovery it either flashes the HTC sign real quick then dies or stays on the HTC screen and doesnt do anything. Ive literally been trying this for 2 days now! Ive rerooted 10 times, Ive tried as many different recovery imgs for CDMA that I could find and I STILL get the same result. I even switched sd cards!! Could there be a problem with my phone thats not allowing it to work? Someone please help this is driving me nuts! Im ready to return the phone and get a new one just to try it,LOL!!PPlease help??
What images have you tried?
Just ones Ive found around the internet. Most of them were recovery-RA-heroc-v1.2.3.img
How are you trying to install it?
Flashrec?
flash_image?
Anyone??? Please?????Im about to return it and try again Id hate to find out it was something simple cuz this Hero has been perfect except for this problem, which is pretty useless to have it rooted if I cant flash, And I wont be able to update if sprint has an update also correct??
packetlss said:
How are you trying to install it?
Flashrec?
flash_image?
Click to expand...
Click to collapse
I follow f directions online that I go into cmd and get to the root and type" flash_image recovery /sdcard/recovery-RA-heroc-v1.2.3.img, when I hit enter all that happens is it shows exactly what I typed AGAIN then just #
So it will look like this:
#flash_image recovery /sdcard/recovery-RA-heroc-v1.2.3.img
flash_image recovery /sdcard/recovery-RA-heroc-v1.2.3.img
#
Then when I type reboot recovery it just reboots and shuts off, so Ill pull the battery and try the hardware method power volume down and it does THE SAME thing or it will just stay stuck on the HTC screen.
Do it like that.
then then use the:
"reboot recovery" command on the # prompt. See if that helps.
packetlss said:
Do it like that.
then then use the:
"reboot recovery" command on the # prompt. See if that helps.
Click to expand...
Click to collapse
Ya I did that, same thing happened. ):
One last try.
Redownload the the image from this post: http://forum.xda-developers.com/showthread.php?t=581521
Download md5sum.exe from this site: http://www.etree.org/md5com.html
Save it in them in same folder as you have the adb command in.
Then from the command line run:
md5sum recovery-RA-heroc-v1.2.3.img
It should output something like this:
0bdcea0f2c734035ba960d76aba0fa6a *recovery-RA-heroc-v1.2.3.img (Don't forget to copy it to the sdcard again )
Bolded text is the checksum of the file, it should match perfectly or your image is damaged.
If the checksum is the same, try flashing it again.
ahh i see clearer now.....
yes as suggested in the last thread you posted in... do a sprint RUU and try agian... this will put you at a known good baseline.... follow steps exactly...
as a added measure to cancel the option of bad sd card, get an external micro sd card reader and format it in windows as fat32
johnsongrantr said:
ahh i see clearer now.....
yes as suggested in the last thread you posted in... do a sprint RUU and try agian... this will put you at a known good baseline.... follow steps exactly...
as a added measure to cancel the option of bad sd card, get an external micro sd card reader and format it in windows as fat32
Click to expand...
Click to collapse
I actually already formatted to fat32,lol. How do I flash RUU??? To start over?
packetlss said:
One last try.
Redownload the the image from this post: http://forum.xda-developers.com/showthread.php?t=581521
Download md5sum.exe from this site: http://www.etree.org/md5com.html
Save it in them in same folder as you have the adb command in.
Then from the command line run:
md5sum recovery-RA-heroc-v1.2.3.img
It should output something like this:
0bdcea0f2c734035ba960d76aba0fa6a *recovery-RA-heroc-v1.2.3.img (Don't forget to copy it to the sdcard again )
Bolded text is the checksum of the file, it should match perfectly or your image is damaged.
If the checksum is the same, try flashing it again.
Click to expand...
Click to collapse
Where do I input that? Once I get in root?
I did adb shell
$su
#md5sum recovery-RA-heroc-v1.2.3.img
it says md5sum not found
No, md5sum in run before you do the adb shell command (it's a normal PC program).
aaron130 said:
Where do I input that? Once I get in root?
I did adb shell
$su
#md5sum recovery-RA-heroc-v1.2.3.img
it says md5sum not found
Click to expand...
Click to collapse
windows command line not adb shell.... make sure you are in the directory in which you downloaded md5sum
obdcea0f2c734035ba960d76aba0fa6a *recovery-RA-heroc-v1.2.3.img
thats what happened Good??
That is the correct checksum.
Try and flash that one.
Nope Same DAM thing it gets stuck at htc or htc then quits and shuts off
I'm out of ideas then. Could be that it's broken, unless someone else has the same problem. (Haven't seen any of that though).
packetlss said:
I'm out of ideas then. Could be that it's broken, unless someone else has the same problem. (Haven't seen any of that though).
Click to expand...
Click to collapse
Thx Im flashing the RUU now. Thx for your help though I appreciate it alot!!
Do it at your risk!
Hi,everybody.
I had successfully ported CWM recovery&Bootmenu 2ndinit for spice,which allows us to use custom rom.
Now,you have two ways to use CWM recovery.One is entering CWM recovery through bootmenu,the another way is entering CWM recovery through stock recovery(Fake flash update zip).
Method 1:Through bootmenu
First of all,you need to root your spice.And then install bootmenu.
Download the bootmenu.tar file(attached).And push it into /sdcard/
Turn on usb debugging on your phone. And use the following commands in adb:
Code:
C:/> adb shell
$ su
# mount -o remount,rw /dev/block/mtdblock1 /system
# mkdir /system/bootmenu
# cd /system/bootmenu
# busybox tar -xf /sdcard/bootmenu.tar
# rm /system/bin/charge_only_mode
# busybox ln -s /system/bootmenu/binary/bootmenu /system/bin/charge_only_mode
# sync
# mount -o remount,ro /dev/block/mtdblock1 /system
# exit
The bootmenu will be installed.
Restart your device once.
Using Boot Menu:
Turn your phone off.
Press the Power Button.
After 1-10 seconds, the red led on your phone will light up for just 3 seconds (Still while the Motorola logo is being displayed).
Exactly when the led lights up, press the volume down button.
You will see the BootMenu, use the Volume Button to navigate up and down, and the power button to select an item.
Then you can select enter CWM recovery.(Someone say CWM's backup&restore cannot work,you can use method 2 for it)
Method 2:Through stock recovery(Fake flash zip)
I found that we can use CWM recovery with stock recovery leak(Fake flash update zip,like OpenRecovery),but this leak is only existed in SESGC_U3_10.10.0_RT firmware.
I have dumped this recovery(Attached file:recovery.img).And flash it by fastboot.It works well with SESLA_U3_01.72.0 firmware.
And then to flash a fake update.zip(Attached file:update.zip) from the root of your sdcard,you will enter CWM recovery!
By the way,if you want to port CM7 for spice,you need to use 2ndinit for your froyo/gingerbread,because it has locked bootloader.
I have compiled CM7 for it,and it can boot up but stuck in white screen after CM bootanimation.If you want to continue my work,you can checkout my github.
Thanks to:
CyanogenMod
koush
...
sorry for my poor English.
With the first method i can't make a nandroid backup, i'll try it with the second!
Nand backup question
GentryLamp said:
Do it at your risk!
Hi,everybody.
I had successfully ported CWM recovery&Bootmenu 2ndinit for spice,which allows us to use custom rom.
Now,you have two ways to use CWM recovery.One is entering CWM recovery through bootmenu,the another way is entering CWM recovery through stock recovery(Fake flash update zip).
Method 1:Through bootmenu
First of all,you need to root your spice.And then install bootmenu.
Download the bootmenu.tar file(attached).And push it into /sdcard/
Turn on usb debugging on your phone. And use the following commands in adb:
Code:
C:/> adb shell
$ su
# mount -o remount,rw /dev/block/mtdblock1 /system
# mkdir /system/bootmenu
# cd /system/bootmenu
# busybox tar -xf /sdcard/bootmenu.tar
# rm /system/bin/charge_only_mode
# busybox ln -s /system/bootmenu/binary/bootmenu /system/bin/charge_only_mode
# sync
# mount -o remount,ro /dev/block/mtdblock1 /system
# exit
The bootmenu will be installed.
Restart your device once.
Using Boot Menu:
Turn your phone off.
Press the Power Button.
After 1-10 seconds, the red led on your phone will light up for just 3 seconds (Still while the Motorola logo is being displayed).
Exactly when the led lights up, press the volume down button.
You will see the BootMenu, use the Volume Button to navigate up and down, and the power button to select an item.
Then you can select enter CWM recovery.(Someone say CWM's backup&restore cannot work,you can use method 2 for it)
Method 2:Through stock recovery(Fake flash zip)
I found that we can use CWM recovery with stock recovery leak(Fake flash update zip,like OpenRecovery),but this leak is only existed in SESGC_U3_10.10.0_RT firmware.
I have dumped this recovery(Attached file:recovery.img).And flash it by fastboot.It works well with SESLA_U3_01.72.0 firmware.
And then to flash a fake update.zip(Attached file:update.zip) from the root of your sdcard,you will enter CWM recovery!
By the way,if you want to port CM7 for spice,you need to use 2ndinit for your froyo/gingerbread,because it has locked bootloader.
I have compiled CM7 for it,and it can boot up but stuck in white screen after CM bootanimation.If you want to continue my work,you can checkout my github(["github . com/gentrylamp").
Thanks to:
CyanogenMod
koush
...
sorry for my poor English.
Click to expand...
Click to collapse
Hello!
Mr GentryLamp, congratulations done, I do not see many people who understand Android programming interested in XT300, you're the man!
I performed all the procedures above, installed bootmenu (but renamed the "charge_only_mode" as "charge_only_mode.bin" the backup purposes), I installed the old recovery with flash_image (command "flash_image recovery path_of_recovery _.img") and put the update.zip on the root of SD.
I can not perform with nand backup recovery from bootmenu (advance notice, and obviously non-functional), and the second way does not work (the leakage update.zip).
When trying to nand backup the nand, the device is the screen backuping ("SD memory free... Backup system...") For about an hour, and then the screen goes white, and end.
You know how I could accomplish this nand backup? You got on your device? Do you know any script that I can use for it?
If you need more information, or something that I test on my device, I place myself at your disposal.
Sorry my english too, Google Translate help much Brazilians.
Hug.
Regisboliver said:
Hello!
Mr GentryLamp, congratulations done, I do not see many people who understand Android programming interested in XT300, you're the man!
I performed all the procedures above, installed bootmenu (but renamed the "charge_only_mode" as "charge_only_mode.bin" the backup purposes), I installed the old recovery with flash_image (command "flash_image recovery path_of_recovery _.img") and put the update.zip on the root of SD.
I can not perform with nand backup recovery from bootmenu (advance notice, and obviously non-functional), and the second way does not work (the leakage update.zip).
When trying to nand backup the nand, the device is the screen backuping ("SD memory free... Backup system...") For about an hour, and then the screen goes white, and end.
You know how I could accomplish this nand backup? You got on your device? Do you know any script that I can use for it?
If you need more information, or something that I test on my device, I place myself at your disposal.
Sorry my english too, Google Translate help much Brazilians.
Hug.
Click to expand...
Click to collapse
I haven't confirmed whether NAND backup will work in bootmenu,but it works well in fake update.zip way.
If your firmware version is SESLA_U3_01.72.0,you need to boot the phone into fastboot mode(bule screen,pressing Vol-up&Vol-down while the phone boots up),and using fastboot to flash recovery.img.
BTW:Some firmware(such as SESGC_U3_10.10.0_RT) do not allow fastboot.You can see some warnings in fastboot bule screen.
More questions...sorry
GentryLamp said:
I haven't confirmed whether NAND backup will work in bootmenu,but it works well in fake update.zip way.
If your firmware version is SESLA_U3_01.72.0,you need to boot the phone into fastboot mode(bule screen,pressing Vol-up&Vol-down while the phone boots up),and using fastboot to flash recovery.img.
BTW:Some firmware(such as SESGC_U3_10.10.0_RT) do not allow fastboot.You can see some warnings in fastboot bule screen.
Click to expand...
Click to collapse
Thanks for reply man o/
My firmware is SESLA_U3_01.72.0, nand backup really not work on first method, and in the second method, also not .
I followed a guide like this: [ht tp:// forum . xda-developers . com/showthread.php?t=918275]. I believe the command is flash_image the same effectiveness as the fastboot, because I could run the CWM_recovery from the update.zip (you said that this gap is only SESGC_U3_10.10.0_RT recovery firmware, and I do not use - no clue of what it is, just know mine, and Chinese MONSTER).
But I saw now that you've lost your XT300 and therefore believe that there is no possibility to test or you do something for it. But anyway, I am grateful and even my disposal device testing, if desired.
Taking advantage ... would be able to put an 'if' that is, the low volume was not pressed, he continued with the 'charge_only_mode', so that the battery could be charged with the device off? I would also like to know if you know if it is possible to make a nand backup from a script, with the connected device, and if you have some kind of script ...
Excuse me for asking so many questions to you is that I know someone who knows and is as interested as you.
Thank you!
Hug.
i had the same problem with NAND backup using method 2
Regisboliver said:
the low volume was not pressed, he continued with the 'charge_only_mode', so that the battery could be charged with the device off?.
Click to expand...
Click to collapse
The phone will not enter charge only mode when you install bootmenu.
In method 2,NAND Backup&Restore works well when I use spice,I'm sorry that it doesn't work with some phone.
GentryLamp said:
The phone will not enter charge only mode when you install bootmenu.
In method 2,NAND Backup&Restore works well when I use spice,I'm sorry that it doesn't work with some phone.
Click to expand...
Click to collapse
I understand that only with bootmenu the device not charge without boot but, my question was would like to know if one can apply this procedure to boot: power button pressed > magenta led light and Motorola logo > {(before bootanimation and bootinstructions) volume down button pressed while red led light? "yes? -> bootmenu" | "no? -> execute the real charge_only_mode binary", execute charge_only_mode.bkp for example, in my case, since renamed the original charge_only_mode for subsequent restoration of boot } > boot. Understand my question? :s
But if there is, I made two scripts, one for installation and uninstallation of another bootmenu (if someone wants I can post), but if you do not give to run the above algorithm, I use the update.zip CWM_recovery the same, so I can recharge my device is switched off, while I find I try to do a custom for 2ndinit.
Mr GentryLamp, you said above, in the opening thread, it has ported a CM7 for XT300 and it crashed after the Motorola logo. I some time ago, I replaced the file libGLES_android.so (in the folder / system / lib / egl), trying to enable the GPU, I fear there is not even in the chipset of XT300 and while on the Motorola logo, the screen was white, blinking. You keep intact the lib folder? Forgive me if I did wrong or very noob question, because I have no expertise in ROM switches, ports, CM, etc...
Regarding the nand backup, searched about it here, to see if I can find at least one script for it, because then I can become more peaceful to test changes more dangerous, not bothering with RDS, SBF ...
Thanks again bro!
Is there a way to port to other Motorola devices? I have a DROID x that I need to try this on because it is stuck in safe mode. How did you port this to flash in stock recovery?
Sent from my DROID4 using Tapatalk 2
Great job, but I think this work is not useful because we don't have a custom Rom for this phone and the stock Rom sucks, I have this xt300 from my carrier iusacell Mexico, and is so slow and to f**king buggy, if is thera a chance to have a good froyo or gingerbread stable Rom will be perfect this phone have some potential but is too capable by the Motorola software
I hope we can some time get a good Rom for this great and cheap phone