I rooted my S3, changed one file, and am now stuck in the startup screen. I've looked on the forums but I'd like to confirm what my recovery options are.
(1) Since I have no backup*, can I recover from a factory recovery for my model and still keep some of my data, apps and customizations?
It's a N American SIII (Rogers Wireless Samsung SGH-I747M). I can boot successfully into both Odin and CWM Recovery (Clockwork 5.5). BusyBox installed.
*I only did one thing:
renamed framework-res.apk to framework-res.apk2 to test permissions. Errors and crash ensued, then I restarted and here I am.
That apk file is part of a fix which is circulating that corrects a bug in the North American models' battery reporting, which requires replacing the apk with a slightly modified version. I thought trying a file rename was a safe small test, prior to backing up. The name "framework" should have tipped me off probably.
(2) Is factory recovery my best option? I would love to get in and just name the file back. But I can't get in.
(3) Was some automatic backup made that I overlooked? Rooting and the learning curve took so many steps I can't remember myself.
(4) Can I just restore the /system directory perhaps? Or some other advanced or custom restore?
Yep, relative noob here. Hope my question is placed correctly and I haven't missed another post with the answers I need, if not pls advise.
CWM Recovery Flash Zip - Not able to find zip on SD
Some progress here...
Since I think the problem is that I renamed framework-res.apk to framework-res.apk2, and since I had a backup of the original, I found and applied the following:
[GUIDE] How to make a cwm recovery flashable zip
Specifically:
Stuck my saved framework-res.apk into the archive in the correct folder (system/framework)
Renamed from sample.zip to update.zip
Copied update.zip to the root of my micro SD (went to buy one since I didn't have a working one)
Since the Guide didn't specify, I assume that flashing requires booting into CWM Recovery (in my case Clockwork 5.5) and using one of the "install zip from sdcard" options there. But it couldn't find the file. Here are my attempt outcomes:
- apply /sdcard/update.zip:
E: Can't open /sdcard/update.zip
(no such file or directory)
Click to expand...
Click to collapse
- choose zip from sdcard:
This just shows me the directory structure inside my phone
So how can I flash from a zip on the (external) SD card? I can't connect via USB except maybe with Odin, so I don't think I can put anything on my device.
No luck
Well, attempted the stock restore from Epic and still have a soft bricked phone.
According to the thread, everyone else is reporting success with Epic's version 4, but it's not working for me. Maybe I'm tired after 48 hours of this and I've missed something or am trying something that cannot work. No idea what's wrong.
I even resigned to losing everything (no backup) and starting over. Didn't think I'd have a permanent brick though.
Here is what everybody is raving about. CWM Recovery on all SGS3 LTE Variants
Will try again, just in case.
Any Luck?
I have done something similar...
I've been trying to find the stock boot from Rogers for the last 5 hours.
I can get into recovery mode and the download screen, but that's as far as I can get.
If you figure it out PLEASE let me know!
same boat
i just bricked my Rogers S3 with apparently a wrong ROM.
can't even get into recovery, totally bricked!
Were you able to find any solution?
Gave up and swapped hardware
I wasn't able to fix it. I was stuck between three useless boot options:
Regular boot - splash screen only and a vibration every few minutes
ODIN - showing that I had flashed the ROM 3 times
CWM - Clockworkmod's custom flash install, replacing the stock one
(Search the forums for the key combinations to get into these.)
I took it back to the store and they kindly replaced it. Glad they didn't know the key combinations. When they told me they needed an hour "to look at it" I thought I'd come back to a finger wag and a flat denial. That was a tough hour.
Make a backup, people; actually, I'm completely sure that a backup is enough. I'm still green at this.
snoops609 said:
I've been trying to find the stock boot from Rogers for the last 5 hours.
Click to expand...
Click to collapse
I understand that the Rogers Galaxy SIII stock recovery isn't out anywhere. If someone is aware of one, please post a link.
Revived my s3! I flashed the att boot img and that has fixed it. Of course my Odin count is up to 25.
And yes I'm sending this from my s3.
If anyone is still in need I still have the files I flashed with. Just shoot me a pm.
Details pls
snoops609 said:
Revived my s3! I flashed the att boot img and that has fixed it. Of course my Odin count is up to 25.
And yes I'm sending this from my s3.
If anyone is still in need I still have the files I flashed with. Just shoot me a pm.
Click to expand...
Click to collapse
Snoops, do you have a Rogers phone? Just trying to understand what you mean by "att boot img". Lol on the Odin count, I got up to 3 and thought I was badass.
Yes, I'd be interested in the files for future use, especially if you're on Rogers and have the LTE version of the Galaxy S3. Model SGH-I747M.
snoops609 said:
Revived my s3! I flashed the att boot img and that has fixed it. Of course my Odin count is up to 25.
And yes I'm sending this from my s3.
If anyone is still in need I still have the files I flashed with. Just shoot me a pm.
Click to expand...
Click to collapse
plese bro help me out...im stuck in the same hole..i just installed some font changer software and m:y phone just rebooted ....
Related
WARNING: DO NOT FLASH ANY OTHER GALAXY S VARIANT'S ODIN FILES. YOU WILL BRICK YOUR PHONE!
WARNING: DO NOT FLASH ANY OTHER GALAXY S VARIANT'S ODIN FILES. YOU WILL BRICK YOUR PHONE!
WARNING: DO NOT FLASH ANY OTHER GALAXY S VARIANT'S ODIN FILES. YOU WILL BRICK YOUR PHONE!
If you have installed voodoo before, please follow the instructions here: http://forum.xda-developers.com/showthread.php?t=804784 before attempting to restore back to stock odin files
ONLY FLASH ONE OF THESE AT A TIME. START WITH THE /SYSTEM ODIN AND WORK YOUR WAY DOWN THE LIST IF NEEDED.
Hey guys, after some reading and bricking one device beyond my repair, i have created a file to restore /system back to stock, with su, superuser and busybox already installed.
THIS SHOULD ONLY BE USED TO RESTORE TO STOCK AFTER A COMPLETE FUBAR! I AM NOT RESPONSIBLE FOR WHAT YOU FLASH TO YOUR PHONE!
You need the samsung drivers for windows for this to work. Those can be found on this thread: http://forum.xda-developers.com/showthread.php?t=779238
This has been tested and verified. I signed with md5 and odin reads the md5 signature as it should.
Steps:
1. Pull battery from device
2. Open odin on desktop
3. Hold volume down button and plug device into computer
-This will place the device into download mode
4. Verify device shows up in odin
5. Click "PDA" button in odin
6. Select "Stock-i500-VZW-System.tar.md5" from where you downloaded it
7. Click "Start"
8. Enjoy your fixed /system partition!
Download:
Odin: http://dl.dropbox.com/u/458252/Odin Files/Odin3 v1.3.exe
Odin Restore file for /system: http://dl.dropbox.com/u/458252/Odin Files/Stock-i500-VZW-System.tar.md5
Odin Restore file for kernel: http://dl.dropbox.com/u/458252/Odin%20Files/Stock-i500-VZW-Kernel.tar.md5
Odin Restore file for recovery: http://dl.dropbox.com/u/458252/Odin Files/Stock-i500-VZW-Recovery.tar.md5
PIT file for use in Odin Restores: http://dl.dropbox.com/u/458252/Odin Files/Stock-i500-VZW-pit.pit
Big thanks to lilinser / dkcldark; koush; humancyborg, namebrandon, geeknik, and many others that were testing and constantly flashing their phones!
And without ludeboy, well, i wouldnt even be able to get into download mode to fix my phone in the first place
Changelog:
9/17/2010- Updated links, fixed md5 errors on files
9/15/2010: Added an odin restore file for the kernel and recovery now that sources are out. This should be used to restore the kernel if you try flashing another one. To those having problems, reboot into recovery (power off device, hold both volume buttons and power until samsung logo, release power button, recovery should boot) and wipe data and cache.
Tried these steps to a T and get "FAIL" in Odin on three separate attempts.
Imagiohio said:
Tried these steps to a T and get "FAIL" in Odin on three separate attempts.
Click to expand...
Click to collapse
what is the message that you get?
MD5 hash value is invalid
Imagiohio said:
MD5 hash value is invalid
Click to expand...
Click to collapse
Edit: BLAH
That did the trick. Thanks very much for the files and the help!
Thanks angel! Was afraid to start experimenting with the Fascinate until an Odin restore was available.
Has any one got this to work, Every time I try odin finishes and passes and then I replace the battery and phone hangs at verizon for a few minutes and then screen goes black and no longer responds. I thought it might be part of the process so i let is sit for 30 min and nothing.
I got this working last night after I screwed up my phone editing the browser.apk file. The whole process took about 2 minutes to complete, however I don't see superuser and it doesn't appear that I have root
pduboise said:
Thanks angel! Was afraid to start experimenting with the Fascinate until an Odin restore was available.
Click to expand...
Click to collapse
Did the same thing with Email.apk on day two with the phone trying to get multiple Exchange accounts like just about every other android device (Thanks TW!!! ). I was able to get it replaced but have been afraid to do anything beyond rooting and adding WiFi Tether until I had a way to un-brick.
Thanks angel!!!
For those that say they don't have root, can you please run 'ls /system/xbin' from adb shell and post your results here?
Sent from my SCH-I500 using XDA App
Thanks so much! Saved my butt, again.
Note to Everyone: Do not attempt to take the Contacts.apk file from another carrier's Galaxy S phone. It will prevent your phone from booting.
Another Note to Everyone: The Fascinate and the Vibrant, for whatever reason, lack the ability to add a unique ringtone to a given contact. The Epic 4G, however, has this option in Edit Contact. Not sure why...
We need to get a mirror up for that. 8k/s... I downloaded it last night at home, and it was a decent speed, but it's dragging here at work.
theicemonkey said:
Thanks so much! Saved my butt, again.
Note to Everyone: Do not attempt to take the Contacts.apk file from another carrier's Galaxy S phone. It will prevent your phone from booting.
Click to expand...
Click to collapse
Add Browser.apk to that list. I'm on device #2, since the ROM wasn't out when I bricked mine.
theicemonkey said:
Note to Everyone: Do not attempt to take the Contacts.apk file from another carrier's Galaxy S phone. It will prevent your phone from booting.
Click to expand...
Click to collapse
I'm new to Odin (coming from the Sprint Hero). With Odin, you'd still be able to recover even if your phone became unbootable such as the situation you describe, right?
Or maybe a better question: given Odin, are there things you could do to your phone that would NOT be recoverable?
The folder had su and budybox in it. I checked. The superuser.apk was not in the app drawer. I rerooted using adb rage.bin and everything is well again
After running the restore phone would boot past the verizon logo but would not respond and had a black screen. It showed up in adb and the softkeys responded to touch. I did adb reboot recovery and wiped data / factory restore and it rebooted like new. This may be a possible fix for someone experiencing similar issues with this. I am not an expert but it worked for me.
disclaimer: if you try this it is at your own risk what fixed my phone may brick yours, you have been warned
avhokie said:
I'm new to Odin (coming from the Sprint Hero). With Odin, you'd still be able to recover even if your phone became unbootable such as the situation you describe, right?
Or maybe a better question: given Odin, are there things you could do to your phone that would NOT be recoverable?
Click to expand...
Click to collapse
I can tell you that without this my phone would have been unrecoverable and I would have had to go back to Verizon. This restores your /system folder (which includes system apps, boot procedure, animations, etc.) back to stock. Therefore, if the problem preventing your phone from booting was due to a problem in the /system folder, this will fix it.
theicemonkey said:
Thanks so much! Saved my butt, again.
Note to Everyone: Do not attempt to take the Contacts.apk file from another carrier's Galaxy S phone. It will prevent your phone from booting.
Another Note to Everyone: The Fascinate and the Vibrant, for whatever reason, lack the ability to add a unique ringtone to a given contact. The Epic 4G, however, has this option in Edit Contact. Not sure why...
Click to expand...
Click to collapse
Hmm, interesting. I just checked this out, and at first, believed you were right (much to my dismay, as I have a distinctive ring on the number for my employer, for when I'm on-call). However, after playing around a bit, I discovered that contacts that are local to the phone can have the option for selecting a ringtone when being edited. So, for any contacts you need a custom ringtone on, do the following:
1. Create a duplicate contact stored on the phone (orange icon)
2. Link the new contact to the other existing contact
3. Edit the linked contact, and choose the Phone tab at the top
4. Scroll down to see the Ringtone option
erasmogjr said:
After running the restore phone would boot past the verizon logo but would not respond and had a black screen. It showed up in adb and the softkeys responded to touch. I did adb reboot recovery and wiped data / factory restore and it rebooted like new. This may be a possible fix for someone experiencing similar issues with this. I am not an expert but it worked for me.
disclaimer: if you try this it is at your own risk what fixed my phone may brick yours, you have been warned
Click to expand...
Click to collapse
this saved my life thanks man
Something went wrong during an ODIN revert to stock, and now when I plug in the phone to the computer or wall it shows the battery charge image for a few seconds, then it says the "Samsung Vibrant" splash and goes straight into recovery mode. I've tried holding down the volume keys, adb doesn't recognize the device. IDK wtf to do. Any help would be so appreciated I'll paypal the person a six pack that can help me fix this.
When it goes into recovery mode it says...
Movi_check Start...!!
checksum confirmation need_checksum[0]
Not need checksum confirmation
Movi_check already executed!!...
Movi_checking done!..
E:Can't mount /dev/block/stl11
(invalid argument)
E:Can't mount /dev/block/stl11
(invalid argument)
did you try holding down volume up/down, and just plugging it into your computer?( so you can get into download mode)
So I just got off the phone with Tech Support, luckily I'm still under warranty and my recovery screen says "Android System Recovery" and not ClockworkMod Recovery. They went through the "Master Reset" and that didn't work, obviously, because I tried that. I also tried every other thread to get into download mode and Odin the original rom/kernel/recovery to no avail. They agreed to send me a new phone free of charge, added on the insurance and shipping is now free. Luckily my girlfriend didn't tell them what really went down haha. "Oh well he rooted his phone and then tried to un-root it and ended up turning it into a paper weight." So now I just sit and wait. Next time I'm not using any other outside write ups to try and reflash a recovery on the vibrant. After I get the OTA (if it ever comes) I'll root it again just to remove the bloatware like I did the first time. But with Clockwork you can't get the OTA, or so it said, so I'll just be patient and wait it out. To anyone else who is stuck in recovery and can't get it into download mode, or flashed the euro version, just call T-Mo tech support and say you downloaded an app and rebooted and voila stuck in recovery. On the downside, I have to wait 5-7 business days (not including weekends or holidays though) for my new one in the mail. So let this be a lesson learned to everyone, read read read and if all else fails, lie.
Its not as easy doing things on the Vibrant as it was with the good old Gangster 1 (G1).
Also, I only tried this because Rom Manager said I still had ClockworkMod Recovery instead of the stock recovery after I did the proper forum.xda-developers.com/showthread.php?t=734475, You don't need to flash the root update as the CSC, I guess there could be a non-root update.zip to use, but There was a guide I followed the first time that only used the PIT and PDA files, which put it back to stock but still had ClockworkMod Recovery on it. If it didn't, Rom Manager was lying to me.
red96turbols said:
So I just got off the phone with Tech Support, luckily I'm still under warranty and my recovery screen says "Android System Recovery" and not ClockworkMod Recovery. They went through the "Master Reset" and that didn't work, obviously, because I tried that. I also tried every other thread to get into download mode and Odin the original rom/kernel/recovery to no avail. They agreed to send me a new phone free of charge, added on the insurance and shipping is now free. Luckily my girlfriend didn't tell them what really went down haha. "Oh well he rooted his phone and then tried to un-root it and ended up turning it into a paper weight." So now I just sit and wait. Next time I'm not using any other outside write ups to try and reflash a recovery on the vibrant. After I get the OTA (if it ever comes) I'll root it again just to remove the bloatware like I did the first time. But with Clockwork you can't get the OTA, or so it said, so I'll just be patient and wait it out. To anyone else who is stuck in recovery and can't get it into download mode, or flashed the euro version, just call T-Mo tech support and say you downloaded an app and rebooted and voila stuck in recovery. On the downside, I have to wait 5-7 business days (not including weekends or holidays though) for my new one in the mail. So let this be a lesson learned to everyone, read read read and if all else fails, lie.
Its not as easy doing things on the Vibrant as it was with the good old Gangster 1 (G1).
Also, I only tried this because Rom Manager said I still had ClockworkMod Recovery instead of the stock recovery after I did the proper forum.xda-developers.com/showthread.php?t=734475, You don't need to flash the root update as the CSC, I guess there could be a non-root update.zip to use, but There was a guide I followed the first time that only used the PIT and PDA files, which put it back to stock but still had ClockworkMod Recovery on it. If it didn't, Rom Manager was lying to me.
Click to expand...
Click to collapse
Rom manager doesnt replace samsungs recovery. There is an update.zip that is placed in your root that allows you to get to clockwork recovery by simply reinstalling packages in samsung recovery. Clockwork recovery may still be flashed, but if you remove or replace that update.zip, the only way otherwise to get to it would be through rom manager. Which obviously isnt an option for you.
Sent from my SGH-T959 using XDA App
wildklymr said:
Rom manager doesnt replace samsungs recovery. There is an update.zip that is placed in your root that allows you to get to clockwork recovery by simply reinstalling packages in samsung recovery. Clockwork recovery may still be flashed, but if you remove or replace that update.zip, the only way otherwise to get to it would be through rom manager. Which obviously isnt an option for you.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Dang. Because when I opened CW it said "Current Recovery: ClockworkMod Recover 4.x.x.x, last version: ClockworkMod Recovery x.x.x." So I guess CW wasn't even on there, so I bricked it for no reason. If I just removed the update.zip it would have just been fine? Because it kept saying "You can't receive the OTA with your current ROM, please contact ROM author." Which is why I decided to reflash to stock un-rooted rom. I had also had a 6 pack and 2 jager bombs so hahaha fsck it. I'm getting a new one and will read when I'm un-ability impaired. Thanks for the note though.... but I also renamed the update.zip to 2.1rootupdate.zip, would that matter to CW or not? Because it kept saying no matter how I reflashed that CWR was still on there...
Did you try to flash 2.2 by any chance? Easy way to fox your problem is just adb reboot. It will boot up your phone past the recovery screen, and then you can use odin to get back to stock.
Sent from my Samsung Vibrant
red96turbols said:
Dang. Because when I opened CW it said "Current Recovery: ClockworkMod Recover 4.x.x.x, last version: ClockworkMod Recovery x.x.x." So I guess CW wasn't even on there, so I bricked it for no reason. If I just removed the update.zip it would have just been fine? Because it kept saying "You can't receive the OTA with your current ROM, please contact ROM author." Which is why I decided to reflash to stock un-rooted rom. I had also had a 6 pack and 2 jager bombs so hahaha fsck it. I'm getting a new one and will read when I'm un-ability impaired. Thanks for the note though.... but I also renamed the update.zip to 2.1rootupdate.zip, would that matter to CW or not? Because it kept saying no matter how I reflashed that CWR was still on there...
Click to expand...
Click to collapse
There is no updated rom available. That function of rom manager is currently unused by vibrant devs. It allows them to make updates to roms and streamline the process, but they simply move on to the next rom. Renaming the update.zip that is used to root to whatever it is is ok for cw recovery, but once you have clockwork recovery flashed since it doesnt replace samsung recovery. When something goes wrong you need its update.zip it puts in root to stay right where it is. By reinstalling packages in samsung recovery is the only way to get to clockwork recovery when you cant load up the phone. If that update.zip is gone or renamed, you're s.o.l.
Sent from my SGH-T959 using XDA App
So if I had kept that update.zip file that CW put on, chances are I could have fixed it? Since I clicked the "Repartition" check box on Odin, would it have even mattered? I used the 512.pit file and the Phone file from the "Unroot" thread by Koush I believe. That worked wonderful, and then I did it a second time and I think something went wrong.
I have a SF running on DI01. It is rooted using Z4. I installed Rom Manager and then flashed latest Clockwork Mod Recovery. When I reboot the phone into recovery, and then select update.zip to get into Clockwork, I am met with the following:
E: failed to verify whole-life signature
E: signature verification failed
Installation aborted
When I originally got this phone this worked fine. The issues started AFTER I did a factory reset. I did the factory reset because I was unsatisfied how the phoen operated after doing a recovery with Titanium Backup and wanted to start fresh again.
I made sure to delete all traces of every file and folder prior, I even used a brand new formatted SD card and I am still getting this problem. I have been through 2 factory resets trying to get the recovery to work.
Anyone with any ideas would be much appreciated. Thanks in advance!
--JD
jfigura said:
I have a SF running on DI01. It is rooted using Z4. I installed Rom Manager and then flashed latest Clockwork Mod Recovery. When I reboot the phone into recovery, and then select update.zip to get into Clockwork, I am met with the following:
E: failed to verify whole-life signature
E: signature verification failed
Installation aborted
When I originally got this phone this worked fine. The issues started AFTER I did a factory reset. I did the factory reset because I was unsatisfied how the phoen operated after doing a recovery with Titanium Backup and wanted to start fresh again.
I made sure to delete all traces of every file and folder prior, I even used a brand new formatted SD card and I am still getting this problem. I have been through 2 factory resets trying to get the recovery to work.
Anyone with any ideas would be much appreciated. Thanks in advance!
--JD
Click to expand...
Click to collapse
You cant flash clockwork recovery from the phone it has to be pushed in odin then you can flash it in rom manager
The thread is in the development section
Do a little searching around and you ll find all the info you need
Yet another reason not to use z4 root as you learn nothing about your phone
And really it aint hard to do things the" right" way
Actually it sounds like you did read.
My best guess is you went wrong when you installed the SD card and have the wrong update.zip on it, but it's just as likely you need to prime CWM again in odin. You'll be fine!
I do agree that the guides should give manual roots, not one clicks. The slow way is pretty quick:
http://forum.xda-developers.com/showthread.php?p=9443125
I don't think rooting was your issue in this case though. I think you may have missed how clockwork installs and works. It is persisting but not permanent.
In brief, you pave the way with the cwm odin flash, then use rom manager to place a current version of CWM recovery on your SD card in the form of update.zip, then 'install' that every time you need to run CWM.
Read post #179, then build a little shrine in the corner of your house for angel12:
http://forum.xda-developers.com/showthread.php?t=788099&page=18
Swyped from my i500.04 (bh &1129) using XDA App
Soba - Once I repushed from Odin it came back. Scratching my head a little but hey it's back. I used Z4 on this phone because I got caught by Verizon when I manually rooted the first model which went bellyup after having it for a week. I wanted to make sure I could quickly get rid of the root if I needed to go back into the store.
To the other responder, sorry for not being specifically "clear".
I've been tinkering with 6 different phones from this one to two Motos and 3 different HTC's. All the methods are beginning to run together sometimes.
I appreciate the assist and I thank you both.
soba49 said:
Actually it sounds like you did read.
My best guess is you went wrong when you installed the SD card and have the wrong update.zip on it, but it's just as likely you need to prime CWM again in odin. You'll be fine!
I do agree that the guides should give manual roots, not one clicks. The slow way is pretty quick:
http://forum.xda-developers.com/showthread.php?p=9443125
I don't think rooting was your issue in this case though. I think you may have missed how clockwork installs and works. It is persisting but not permanent.
In brief, you pave the way with the cwm odin flash, then use rom manager to place a current version of CWM recovery on your SD card in the form of update.zip, then 'install' that every time you need to run CWM.
Read post #179, then build a little shrine in the corner of your house for angel12:
http://forum.xda-developers.com/showthread.php?t=788099&page=18
Swyped from my i500.04 (bh &1129) using XDA App
Click to expand...
Click to collapse
So I'm getting stuck at the same place. I'm new, so could you explain how to pave the way with Odin? I think I understand the concept, but I'm looking for a detailed list of flashing things (such as the update.zip from cwm) in Odin to my phone.
Thank you for any input!
woodaresick said:
So I'm getting stuck at the same place. I'm new, so could you explain how to pave the way with Odin? I think I understand the concept, but I'm looking for a detailed list of flashing things (such as the update.zip from cwm) in Odin to my phone.
Thank you for any input!
Click to expand...
Click to collapse
Here's Update.Zip file for CWM
Direct Link, I uploaded it by myself, couldn't find decent one
http://www.4shared.com/file/ReRrCtwV/update.html
Make Sure to thank me if it works
If it doesn't let me know.
Hello.
My phone is starting to act funny, it has the quite common problem where the touch function on the bottom half of the screen stops working properly.
Since I'm going to send it in, I'd like to return everything to as close to the shipping state as possible. I don't care if I still have Clockworkmod left on it or if I make it unrootable, since I'm going to buy a new phone and sell this one when the contract runs out in a few months anyway.
I've tried searching for the info I need but there are still some things I'm unclear about.
The phone is currently running VillainMod and has ClockWorkMod installed as a bootloader. I was running CM on it until a few days ago, but I tried installing a Sense-based ROM to see if I could get the RUU .exe method to work, but it fails after the phone has rebooted and just says that it cannot update the phone. Any ideas what's causing this? (I used the file RUU_Hero_HTC_WWE_3.32.405.1_R_Radio_63.18.55.06P_6.35.15.11_release_signed.exe)
So since the "official" method failed I found the rom.zip that is unpacked by the RUU program and copied it.
Here is where I'm not sure how to proceed. Should I sign the zip-file (using testsign.jar) and then do "apply update.zip" from ClockWorkMod OR should I extract the boot.img, data.img, recovery.img, system.img and radio.img files from the zip, generate a md5 file (how?) and restore it using the backup feature in Clockwork?
Or is maybe both of these ideas totally of the mark?
Any help is appreciated. Do tell if there is some more info you need.
I personally don't think you should go with that plan. I'm not a big scientist when it comes to phone development since I'm still learning. But I think you should go backwards and check what went wrong.
Edit:
I also think that the new rom might have different requirements from the previous one. Usually that causes a problem if you try to flash a rom without fitting the requirements.
No you need to rename the Rom.zip to heroimg.zip then shut down phone and reboot into hboot mode by using power and vol down
So, I have never rooted or flashed a device before and I kinda dove into rooting mine and hoped to learn along the way.
I rooted my Verizon Galaxy S4 version i545VRUEMK2, I used this method from a guy on YouTube named Andre Hebra, it's his only video so if you want to see what it was you can find it (sorry couldn't post a link, I'm a forum newb) now I'm rooted but half of the superuser app is in Chinese or Japanese and its kind of annoying but I can figure out what is happening.
Now here is where I started having some trouble, I decided to try and flash a ROM to my device. I was trying to flash CyanogenMod 11 (12/26/13) Nightly (have no idea what nightly means) and I ran into a few problems that I hope some of you guys can help me with. I downloaded Clockwork ROM Manager and Installed a Recovery. I moved the .zip file from the Cyanogen website to the SD card in my phone. And also moved phone's files into a folder on my computer as a backup. I put my phone into recovery mode through the CWM app and cleared the cache and wiped the data. Now, I can't manually enter recovery boot by holding the volume up, power and home buttons, the phone boots up, the Recovery Boot message appears for a split second and then the phone turns off and boots up again into Android. I'm also struggling to figure out how to flash the ROM, shouldn't I be able to use this Clockwork app to install it from my SD card? But when I try and do that the .zip file doesn't show up in the directory. Did I do something wrong? A quick run through and tutorial would be helpful.
Device Info:
Model number: SCH-i545
Android Version: 4.3
Baseband Versions: i545VRUEMK2
I'm also having trouble navigating to the guides on this site for rooting and flashing my particular device. So i apologize if there is a guide for all of this somewhere but I couldn't find it.
What ROM
Shagen34 said:
So, I have never rooted or flashed a device before and I kinda dove into rooting mine and hoped to learn along the way.
I rooted my Verizon Galaxy S4 version i545VRUEMK2, I used this method from a guy on YouTube named Andre Hebra, it's his only video so if you want to see what it was you can find it (sorry couldn't post a link, I'm a forum newb) now I'm rooted but half of the superuser app is in Chinese or Japanese and its kind of annoying but I can figure out what is happening.
Now here is where I started having some trouble, I decided to try and flash a ROM to my device. I was trying to flash CyanogenMod 11 (12/26/13) Nightly (have no idea what nightly means) and I ran into a few problems that I hope some of you guys can help me with. I downloaded Clockwork ROM Manager and Installed a Recovery. I moved the .zip file from the Cyanogen website to the SD card in my phone. And also moved phone's files into a folder on my computer as a backup. I put my phone into recovery mode through the CWM app and cleared the cache and wiped the data. Now, I can't manually enter recovery boot by holding the volume up, power and home buttons, the phone boots up, the Recovery Boot message appears for a split second and then the phone turns off and boots up again into Android. I'm also struggling to figure out how to flash the ROM, shouldn't I be able to use this Clockwork app to install it from my SD card? But when I try and do that the .zip file doesn't show up in the directory. Did I do something wrong? A quick run through and tutorial would be helpful.
I'm also having trouble navigating to the guides on this site for rooting and flashing my particular device. So i apologize if there is a guide for all of this somewhere but I couldn't find it.
Click to expand...
Click to collapse
You have to make sure that you get the correct ROM for the device you have as they are many. Always if a new to rooting, write down all information from Setting>about. This is where all the most important information is. This way folks on here can help you out a lot better. It seems that you are stuck in a "Boot loop" it's not a big deal. There are a bunch of Youtube videos about boot loop check it out. I'm not that familiar with the ROM you have. Good Luck!
Shagen34 said:
So, I have never rooted or flashed a device before and I kinda dove into rooting mine and hoped to learn along the way.
I rooted my Verizon Galaxy S4 version i545VRUEMK2, I used this method from a guy on YouTube named Andre Hebra, it's his only video so if you want to see what it was you can find it (sorry couldn't post a link, I'm a forum newb) now I'm rooted but half of the superuser app is in Chinese or Japanese and its kind of annoying but I can figure out what is happening.
Now here is where I started having some trouble, I decided to try and flash a ROM to my device. I was trying to flash CyanogenMod 11 (12/26/13) Nightly (have no idea what nightly means) and I ran into a few problems that I hope some of you guys can help me with. I downloaded Clockwork ROM Manager and Installed a Recovery. I moved the .zip file from the Cyanogen website to the SD card in my phone. And also moved phone's files into a folder on my computer as a backup. I put my phone into recovery mode through the CWM app and cleared the cache and wiped the data. Now, I can't manually enter recovery boot by holding the volume up, power and home buttons, the phone boots up, the Recovery Boot message appears for a split second and then the phone turns off and boots up again into Android. I'm also struggling to figure out how to flash the ROM, shouldn't I be able to use this Clockwork app to install it from my SD card? But when I try and do that the .zip file doesn't show up in the directory. Did I do something wrong? A quick run through and tutorial would be helpful.
Device Info:
Model number: SCH-i545
Android Version: 4.3
Baseband Versions: i545VRUEMK2
I'm also having trouble navigating to the guides on this site for rooting and flashing my particular device. So i apologize if there is a guide for all of this somewhere but I couldn't find it.
Click to expand...
Click to collapse
If you are new to all this, then you need to do alot more reading first of all if you are on MK2 base, you can not load any custom recovery except for safestrap. And with safestrap you CANNOT load any CM or ASOP based ROMS. This situation has been discuss a couple hundred times thru out this forum. You will get to learn about ODin process now as that is your only recourse.
many youtube videos on odin and search function works in XDA