Related
when I boot my phone up, instead of the htc and boot animation screen it stays a black screen, Whenever I try to back up my current ROM or Go into recovery mode the screen goes black untill I take out the battery and reboot, what could be causing this problem and how could I fix it? Like I said I can't get into CWM so a wipe is out of the question, and adb isn't an option right now, please help
Sent From My T-Mobile G2 using XDA App
Sent From My T-Mobile G2 using XDA App
Are you able to get into your bootloader/hboot screen (hold the power button and the volume down button)?
Bharakrama said:
Are you able to get into your bootloader/hboot screen (hold the power button and the volume down button)?
Click to expand...
Click to collapse
Nope it does the same thing :?
Sent From My T-Mobile G2 using XDA App
Sent From My T-Mobile G2 using XDA App
You should stop bumping this thread. Nobody is posting in this forum so you don't have to worry about your thread being lost...
Similar thing happened to me, but I could actually get to the HTC screen. What you need to do is set up adb, and get to your bootloader by holding vol. down + power and start fastboot usb. There is no way to fix an issue like this if you can't use/get into your recovery. From there you can try fastboot erase system -w and then fastboot flash recovery [name of recovery] and then fashboot update [CM7.zip]. Clockwork mod recovery can be found here: http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Rooting
i would but now my phone is deciding not to connect via USB, i think its falling apart, maybe time to get a new phone i guess...
Wait, you are able to boot up normally?
If so, use flash_image recovery recovery.img to flash CWM again.
sent from my G2 running CM7 nightly
poormanq45 said:
Wait, you are able to boot up normally?
If so, use flash_image recovery recovery.img to flash CWM again.
sent from my G2 running CM7 nightly
Click to expand...
Click to collapse
how do i install that on my phone?
poormanq45 said:
Wait, you are able to boot up normally?
If so, use flash_image recovery recovery.img to flash CWM again.
sent from my G2 running CM7 nightly
Click to expand...
Click to collapse
And yes, I can boot up but not HTC or boot screen shows up, just a black screen then my phone turns on. I can't go into bootloader or recovery mode.
Sent From My T-Mobile G2 using XDA App
From within your rom you need to download the CWM recovery image and save it on your SDcard. Name it recovery.
Use terminal emulator and type in:
Su
Ls sdcard
Flash_image recovery recovery.img
This will flash the recovery back you your phone
sent from my G2 running CM7 nightly
poormanq45 said:
From within your rom you need to download the CWM recovery image and save it on your SDcard. Name it recovery.
Use terminal emulator and type in:
Su
Ls sdcard
Flash_image recovery recovery.img
This will flash the recovery back you your phone
sent from my G2 running CM7 nightly
Click to expand...
Click to collapse
Thanks man
Sent From My T-Mobile G2 using XDA App
poormanq45 said:
From within your rom you need to download the CWM recovery image and save it on your SDcard. Name it recovery.
Use terminal emulator and type in:
Su
Ls sdcard
Flash_image recovery recovery.img
This will flash the recovery back you your phone
sent from my G2 running CM7 nightly
Click to expand...
Click to collapse
Sent From My T-Mobile G2 using XDA App
poormanq45 said:
From within your rom you need to download the CWM recovery image and save it on your SDcard. Name it recovery.
Use terminal emulator and type in:
Su
Ls sdcard
Flash_image recovery recovery.img
This will flash the recovery back you your phone
sent from my G2 running CM7 nightly
Click to expand...
Click to collapse
I don't understand, I followed your instructions but nothing happens? All it says is flash_image partition or something
Sent From My T-Mobile G2 using XDA App
Assuming you've tried to flash recovery from ROM manager (Choose "Flash ClockworkMod Recovery" within ROM manager), if not - do that.
Otherwise, try this:
Download this: http://download.clockworkmod.com/recoveries/recovery-clockwork-3.0.2.4-vision.img
rename it to "recovery.img" and place it on the root of your SD card.
Use terminal emulator on your phone, and type the following 1 line at a time:
Code:
su
cd /sdcard/
flash_image recovery recovery.img
tun4f1sh said:
Assuming you've tried to flash recovery from ROM manager (Choose "Flash ClockworkMod Recovery" within ROM manager), if not - do that.
Otherwise, try this:
Download this: http://download.clockworkmod.com/recoveries/recovery-clockwork-3.0.2.4-vision.img
rename it to "recovery.img" and place it on the root of your SD card.
Use terminal emulator on your phone, and type the following 1 line at a time:
Code:
su
cd /sdcard/
flash_image recovery recovery.img
Click to expand...
Click to collapse
Yes I've already tried it via rom manager.
When I type in the last line all that happens is after a couple of seconds the # appears underneath the last line
Sent From My T-Mobile G2 using XDA App
rickyiswhite said:
Yes I've already tried it via rom manager.
When I type in the last line all that happens is after a couple of seconds the # appears underneath the last line
Sent From My T-Mobile G2 using XDA App
Click to expand...
Click to collapse
That's a good thing. Now try rebooting into recovery from ROM manager. I'm a bit concerned that you can't get into the bootloader, I smell a bigger issue.
tun4f1sh said:
That's a good thing. Now try rebooting into recovery from ROM manager. I'm a bit concerned that you can't get into the bootloader, I smell a bigger issue.
Click to expand...
Click to collapse
Semi brick soft brick and am I going to be bricked soon?
Sent From My T-Mobile G2 using XDA App
rickyiswhite said:
Semi brick soft brick and am I going to be bricked soon?
Sent From My T-Mobile G2 using XDA App
Click to expand...
Click to collapse
As long as you're able to get into the ROM, you're not bricked, but I would NOT do anything that could possibly wipe /system (until you're able to get into recovery)
tun4f1sh said:
As long as you're able to get into the ROM, you're not bricked, but I would NOT do anything that could possibly wipe /system (until you're able to get into recovery)
Click to expand...
Click to collapse
Sent From My T-Mobile G2 using XDA App
Koushik Dutta's Clockwork Recovery:
Attention: Some people experience problems when flashing through Rom Manager. Flashing again usually fixes the issue. Use method below for best results. If on pure stock, your recovery will be overwritten unless you delete your /system/etc/install-recovery.sh file.
To flash recovery for Nexus S 4G, download recovery 5.0.2.0 or recovery touch 5.8.0.2 and place it into your sdk tools folder. Reboot into bootloader and execute:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo4g.img
or if you prefer the touch version:
Code:
fastboot flash recovery recovery-clockwork-touch-5.8.0.2-crespo4g.img
If you'd like simpler and more organized menus see j_r0dd's mod.
rev 5.0.1.0 Fix android_ secure backup bug.
rev 5.0.2.0 Fix root loss. Correct message when choosing "no" when wiping dalvik.
Officiality
RSVP....
outstanding
Sent from my HP Touchpad using xda premium
Backups on 4.x going tto restore properly on 5.x?
Great work by the way.
Sent from my Nexus S 4G using XDA App
...or just go into the ROM Manager app and click on "Flash Clockworkmod Recovery", your version will update to 5 automatically.
Sent from my Nexus S 4G using xda premium
Also there's a app in the app section that flashes img files quicker than you can blink.
Flash_image by gui
Sent from my HP touchpad using xda premium
jakkz said:
...or just go into the ROM Manager app and click on "Flash Clockworkmod Recovery", your version will update to 5 automatically.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I had some issues doing it through rom manager. It was a no go so I flashed through bootloader.
I haven't checked if old backups are compatible yet. Anyone care to try and post?
Sent from my Nexus S 4G using XDA App
Every time I click on the update from inside ROM Manager, something terrible happens. I used think it was because I clicked on the link for the other Nexus S, but I was super duper careful this time.
If I try to reboot into recovery without being attached to my PC after flashing a new recovery in ROM Manager, I get stuck in fastboot. If I tell it to please boot me into recovery so can add a shiny new object to my Android, it tells me, "No ma'am." And, if im being honest, when I can't flash exciting new thingys on the go, existence begins to seem somewhat more futile. I'm sure you understand.
Might as well ask if there's a way I can fix it before I get home (in TEN HOURS) by fastbooting from a terminal or something. Okay, I'm begging.
p.s. I feel like I didn't get invited to most of Version 3 and all of Version 4.
Sent from my Nexus S 4G using xda premium
I had the same issue after using rom manager to flash 5. I just rebooted and tried flashing again from rom manager and it worked the second time
Sent from my Nexus S 4G using Tapatalk
jdkjgjjd said:
Might as well ask if there's a way I can fix it before I get home (in TEN HOURS) by fastbooting from a terminal or something. Okay, I'm begging.
p.s. I feel like I didn't get invited to most of Version 3 and all of Version 4.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Read the op. There is a reason why I gave instructions to flash through fastboot and not rom manager.
info[]box1 said:
Also there's a app in the app section that flashes img files quicker than you can blink.
Flash_image by gui
Sent from my HP touchpad using xda premium
Click to expand...
Click to collapse
This app worked great for me. Easy as 1,2,3
qbking77 said:
Backups on 4.x going tto restore properly on 5.x?
Great work by the way.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
I can confirm they do work.
Trying to upgrade from 4.0.0.2 to 5.0.0.0, I keep getting stuck on "Waiting for device"..
If on windows...your driver is bad.
Try flash_image gui by Joeykrim
Well here is the thing, I can push/pull things from the device, I can adb shell to the device.. Everytime I try flash the recovery, I get the waiting for device
Well if on Windows, fastboot driver needs to be there along with adb.driver. Two different things
Didnt work through rom manager, had to do it via fastboot. I dig the new color!
so rom manager updated my cwm to this one and when i go to reboot into recovery it goes into bootloader and which i chose recovery nothing happens .... first line says FASTBOOT - NO RECOVERY OR BOOT IMG
For anybody having flashing/ pushing/ just getting the new cwm recovery use the flash_image by GUI app located in the ns4g app section. I can't stress it enough, but it your trying to computer up to speed for Android development I understand.
Sent from my HP Touchpad using xda premium
I updated through ROM Manager and it worked just fine. I believe as long as you are running the latest version of ROM Manager you shouldn't have any issues.
Forget to make a backup before trying to flash a rom?
Need to return your phone to sprint? NOW WITH RADIOS + FACTORY IMAGES!
TWRP NANDROID
Unzip then Place these in your TWRP Folder by using ADB (lookup your standard ADB guide) Then restore the nandroid
CWM NANDROID
Unzip then place in your CWM folder sub folder backups then boot to clockwork mod and restore
Stock Recovery Image
use this while in fastboot mode (hold vol up + down + power while phone is off) then on your computer issue cmd fastboot flash recovery recovery.img (search for how to setup adb)
Need Help Rooting? How To Videos Thanks to QBking77!
Need More Help? Join the IRC channel!
RADIO FIX IN THE FORM OF AN ODIN FACTORY IMAGE!!!
THANK YOU SHABBYPENGUIN!!!!! WE LOVE YOU!
If this helped Donate To Me
This should be stickied too
Can someone post the stock zimage?
Wordlywisewiz said:
Need MoComing Soon:
Radio Fix (if you flashed a verizon radio)
Click to expand...
Click to collapse
I am desperate to have anyone dd the basebands & post them.
poontab said:
I am desperate to have anyone dd the basebands & post them.
Click to expand...
Click to collapse
We are working on them....
They appear to be combined into one radio image but it needs to be one for CD a one for lte
Sent from my Galaxy Nexus using xda premium
Thanks - always nice to have insurance - I think I know the answer but just to be sure - is the TWRP nandroid rooted or will I loose root when I run this?
mocsab said:
Thanks - always nice to have insurance - I think I know the answer but just to be sure - is the TWRP nandroid rooted or will I loose root when I run this?
Click to expand...
Click to collapse
All are unrooted but its easy to re root
Sent from my Galaxy Nexus using xda premium
Wordlywisewiz said:
All are unrooted but its easy to re root
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
WHat would I do - simply reflash the SU zip or would I have to re-push that to the phone ? (I know I sound like a noob here - but still learning the differnces between this phone and my old Epic4g - I recall seeing how sometimes everything on the SD card get's over written - but I wasn't sure if that happened in this case?)
mocsab said:
WHat would I do - simply reflash the SU zip or would I have to re-push that to the phone ? (I know I sound like a noob here - but still learning the differnces between this phone and my old Epic4g - I recall seeing how sometimes everything on the SD card get's over written - but I wasn't sure if that happened in this case?)
Click to expand...
Click to collapse
You sould just have to reflash
Unless you wiped your SD card
Sent from my Galaxy Nexus using xda premium
Update:
No new updates XD
Hows the radios coming along, i just borked mine and restored with the verizon img by mistake
joetemp75 said:
Hows the radios coming along, i just borked mine and restored with the verizon img by mistake
Click to expand...
Click to collapse
We are doing our best
Thanks I know you are and I appreciate all that you're doing.
Sent from my Transformer Prime TF201 using XDA Premium HD app
LTE Fixed.
C:\Galaxy Nexus ToolKit>adb-toolkit.exe shell
~ # ls
ls
boot etc sd-ext
cache init sdcard
data init.rc sys
datadata proc system
default.prop res tmp
dev root ueventd.goldfish.rc
emmc sbin ueventd.rc
~ # cd sdcard
cd sdcard
/data/media # ls
ls
radio.img radio1.img
/data/media # dd if=/sdcard/radio.img of=/dev/block/platform/omap/omap_hsmmc.0/b
y-name/radio
dd if=/sdcard/radio.img of=/dev/block/platform/omap/omap_hsmmc.0/b
y-name/radio
24576+1 records in
24576+1 records out
12583168 bytes (12.0MB) copied, 3.677856 seconds, 3.3MB/s
/data/media # dd if=/sdcard/radio1.img of=/dev/block/mmcblk0p9
dd if=/sdcard/radio1.img of=/dev/block/mmcblk0p9
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 4.613159 seconds, 3.5MB/s
/data/media #
C:\Galaxy Nexus ToolKit>
Click to expand...
Click to collapse
We managed to fix my LTE radio so far, but we're still having trouble finding the right spot to pull the CDMA radio from.
Tilton53 said:
We managed to fix my LTE radio so far, but we're still having trouble finding the right spot to pull the CDMA radio from.
Click to expand...
Click to collapse
That's good
Hopefully when u figure out how to fix the radio and get mms working on aosp then the roms should be up and we will have a recovery radio in case something goes bad
Sent from my SPH-D700 using xda premium
Theoretically we basically have a factory image at this point we just need that cdma radio
Sent from my Galaxy Nexus using xda premium
Tilton53 said:
We managed to fix my LTE radio so far, but we're still having trouble finding the right spot to pull the CDMA radio from.
Click to expand...
Click to collapse
Awesome we will get them... then hopefully we can make some sort of factory restore tool
Restore stock nandroid
Flash stock radios
Flash stock recovery
Then relock boot loader..
Sent from my Galaxy Nexus using xda premium
i think that this download for cwm recovery is wrong or something because everytime i go to flash it after putting it on my internal storage like i would with a custom rom it fails right off the bat.
please help me im lost on what to do now.
jsonger121 said:
i think that this download for cwm recovery is wrong or something because everytime i go to flash it after putting it on my internal storage like i would with a custom rom it fails right off the bat.
please help me im lost on what to do now.
Click to expand...
Click to collapse
Reread the first post. It is not a flashable ROM, it's a backup of the stock ROM. So you'll need to unzip it then place it on your internal storage under CWM/backup (or somewhere similar, not using CWM myself so unsure of the exact folder names) then boot into recovery and select Restore and then restore the backup you downloaded.
Sent from my Galaxy Nexus using Tapatalk 2
@Worldly: You still getting Error 927? I just got that issue and just cleared Market (Play Store) cache and it was fine.
Sent from my Galaxy Nexus using Tapatalk 2
Maybe it is interesting also for others, how to get back ROOT access after flashing JB OTA. I did it with YAKJU.
The steps:
1.) adb reboot bootloader
2.) download recovery-clockwork-5.5.0.2-maguro.img
2.) fastboot boot recovery-clockwork-5.5.0.2-maguro.img
3.) adb kill-server
4.) adb start-server
5.) adb devices
6.) mount the system in CWM
7.) adb shell ls -al /system/bin/su
8.) adb shell chmod 4755 /system/bin/su
9.) adb shell ls -al /system/bin/su
10.) reboot
Dont forget to use fastboot with su or sudo -i in Linux.
Steps 3, 4 and 5 are only to ensure that your ADB works correctly with your device.
Steps 7 and 9 is also only for paranoid users like me
That's it.
Voodoo OTA Rootkeeper?
In another thread, a poster reported that Voodoo OTA Rootkeeper was unable to restore root after flashing JellyBean. I wonder if others have had the same experience? Thanks!
gibosi said:
In another thread, a poster reported that Voodoo OTA Rootkeeper was unable to restore root after flashing JellyBean. I wonder if others have had the same experience? Thanks!
Click to expand...
Click to collapse
I was able to make it work...I hit restore su... then it took like a minute little pop up saying su restore successful ..opened superuser app...went back to ota root keeper...hit restore su again...that's when superuser prompted me to allow superuser access.
Sent from my Galaxy Nexus using xda premium
Based on your experience, I flashed Jellybean this afternoon and Voodoo OTA Rootkeeper restored root. Thanks!
i think i've become lazy these days, i just selected - "root phone" in the nexus tool kit 7.4 after flashing the update to get root back.
i dont even bother typing the fastboot commands to boot CWM recovery in CMD anymore, i just select the option in the toolkit.
gibosi said:
In another thread, a poster reported that Voodoo OTA Rootkeeper was unable to restore root after flashing JellyBean. I wonder if others have had the same experience? Thanks!
Click to expand...
Click to collapse
Placing this here in case it can help anyone else:
I downloaded the Jelly Bean .zip file, placed it in /cache, and used the stock recovery to update. After installation, I had lost root. su was gone from /system/xbin and OTA Rootkeeper was unable to restore root. Neither CWM Touch 5.8.0.2 nor CWM 5.5.0.2 were able to mount /sdcard in order to apply su.zip. However, /system/usr/we-need-root/su-backup was still there with the proper permissions so I was able to restore root manually by using it.
the OP's instructions worked for me. I flashed the OTA with CWM by the way (the stock failed on the package checking because I was rooted) ?
Anyway, I ran Titanium Backup to check the root worked per OP's instructions and it did but it complained that permissions weren't optimal so I let it change them to 6755 instead (which gives super to both the owner and the group).
Works like a charm now so far.... only 5 minutes with it though
I forgot to run root keeper before the 4.1.2 OTA. I presume this is still valid?
Can someone confirm that this wont wipe the device?
Ta
aidanbree said:
I forgot to run root keeper before the 4.1.2 OTA. I presume this is still valid?
Can someone confirm that this wont wipe the device?
Ta
Click to expand...
Click to collapse
Let me make this a little easier, do the first couple of steps then once you are in recovery flash this: http://androidsu.com/superuser/
You are rooted.
Why are you trying to make this so hard?
Boot in to CWM Recovery and flash the zip. Takes about 5 seconds.
Couldn't we just adb push a su apk to system/app and maybe a adb install su?
Sent from my Nexus 7 using Tapatalk 2
BrianDigital said:
Couldn't we just adb push a su apk to system/app and maybe a adb install su?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
You could but I still think my way would be easier, just my opinion though.
Sent from my Galaxy Nexus using Tapatalk 2
miketoasty said:
You could but I still think my way would be easier, just my opinion though.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I see but if you took the 4.1.2ota you were on stock recovery and someone wanting to get ota'the same way would have to revert back to stock recovery once this was done.
Sent from my Nexus 7 using Tapatalk 2
BrianDigital said:
I see but if you took the 4.1.2ota you were on stock recovery and someone wanting to get ota'the same way would have to revert back to stock recovery once this was done.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Good point, I don't regularly use the stock recovery so I wasn't thinking about it.
Sent from my Galaxy Nexus using Tapatalk 2
miketoasty said:
Good point, I don't regularly use the stock recovery so I wasn't thinking about it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I am going to do this today, my girlfriend needs roots for silly things like changing the on screen button. I'll document it and leave it in here.
This way she can have her root and I dont have to be like "I needs to update your phone/tablet" when google pushes something new, and maybe other people might find it useful
I initially rooted with http://downloadandroidrom.com/file/GalaxyS3ATT/rooting/GalaxyS3RootATT.zip that I got from here yesterday but feel like it has been al ittle glitcht.y http://galaxys3root.com/galaxy-s3-root/how-to-root-att-galaxy-s3-sgh-i747/
the newer version is recovery-clockwork-5.8.4.5-d2att sI don't want it to conflict with the old version of CWM or anything it leaves behind. hould I just do it through odin?
the best route would be to flash from rom manager.....and if not, grab the latest from the interwebz and run this from terminal
su
if=/sdcard/ recovery.img of=/dev/block/mmcblk0p18
reboot recovery
hapticxchaos said:
the best route would be to flash from rom manager.....and if not, grab the latest from the interwebz and run this from terminal
su
if=/sdcard/ recovery.img of=/dev/block/mmcblk0p18
reboot recovery
Click to expand...
Click to collapse
Should I use the CWM that I already installed or install the CWM that comes with rom manager (in the drop down menu it only offers galaxy s2...fyi I've always flashed with CWM without ROM manager)?
zetsui said:
I initially rooted with http://downloadandroidrom.com/file/GalaxyS3ATT/rooting/GalaxyS3RootATT.zip that I got from here yesterday but feel like it has been al ittle glitcht.y http://galaxys3root.com/galaxy-s3-root/how-to-root-att-galaxy-s3-sgh-i747/
the newer version is recovery-clockwork-5.8.4.5-d2att sI don't want it to conflict with the old version of CWM or anything it leaves behind. hould I just do it through odin?
Click to expand...
Click to collapse
I just updated CWM through Rom Manager. The latest version is 6.xxxx, and it now reads exSd.
Sent from my SGH-I747 using xda premium
geomax45 said:
I just updated CWM through Rom Manager. The latest version is 6.xxxx, and it now reads exSd.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
what do you mean "through" rom manager. Did you flash an image through it? Could you provide the link for that image?
OR
Rom Mangaer has an install CWM recovery option...but underneath that option I do not see the Galaxy S3 listed...so what phone did people select?
zetsui said:
what do you mean "through" rom manager. Did you flash an image through it? Could you provide the link for that image?
OR
Rom Mangaer has an install CWM recovery option...but underneath that option I do not see the Galaxy S3 listed...so what phone did people select?
Click to expand...
Click to collapse
The first option in RM is to flash a recovery. Upon pressing that you are given a list of phones. Scroll down to the Samsung GS3 and choose it. It will then flash the recovery within RM.
Sent from my SGH-I747 using xda premium
zetsui said:
.but underneath that option I do not see the Galaxy S3 listed...so what phone did people select?
Click to expand...
Click to collapse
zetsui said:
Should I use the CWM that I already installed or install the CWM that comes with rom manager (in the drop down menu it only offers galaxy s2...fyi I've always flashed with CWM without ROM manager)?
Click to expand...
Click to collapse
Sent from my SGH-I747 using xda premium[/QUOTE]
AhAh! I knew i wasn't crazy... I have the same problem with Rom Manager , it won't show the S3 in the Menu. I tried uninstalling, wiping app data, reinstalling, Nothing, Nada, Niet ...... Let me know if you find a solution to this
I've had issues getting ROM manager to recognize me as a gs3 as well that's why I learned the terminal commands lol
hapticxchaos said:
I've had issues getting ROM manager to recognize me as a gs3 as well that's why I learned the terminal commands lol
Click to expand...
Click to collapse
Anyone find an easier way? And how would you do this through terminal commands? What are the commands
zetsui said:
Anyone find an easier way? And how would you do this through terminal commands? What are the commands
Click to expand...
Click to collapse
Terminal is as easy as the rest. I posted the commands up top, I see you didn't read the whole thread ;p ****, terminal is easier BC you can pick any recovery you want. Besides, it makes u feel like a true dev ;p
cool
I do not have any SG3 as an option to flash. How do i fix this?
geomax45 said:
The first option in RM is to flash a recovery. Upon pressing that you are given a list of phones. Scroll down to the Samsung GS3 and choose it. It will then flash the recovery within RM.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
hapticxchaos said:
the best route would be to flash from rom manager.....and if not, grab the latest from the interwebz and run this from terminal
su
if=/sdcard/ recovery.img of=/dev/block/mmcblk0p18
reboot recovery
Click to expand...
Click to collapse
Hey my md5 checksum has a mismatch, but I know the files are fine. is there a terminal command to recompile the md5 for a given image?
Also I noticed the new version of CWM has teh option to backup files as TAR, wouldn't that be better since Odin flashes Tar? If you couldn't get into CWM for some reason you can just flash for Odin?
Forgive me if I'm being newb here had my phone for three days after a motorola bravo