• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [OUDHS] Factory Image and Restore

xInterlopeRx

xInterlopeRx

Android Enthusiast
Ha! You came back to this thread thinking it was gonna just be like it was when last you looked. But, thanks to edit functionality, it's completely different. Our cohort cobretti was able to pull the LK2 update and push it to my host. Well, after I checked it out, I made a .tar out of it and re-upped it for your flashing pleasure. I know many of you would like a flashable zip, and I can do that, but it will take some time. The file is nearly a Gb and I have worse internet than Kajikstan. For instruction on how to flash this read the CWM thread, replacing this file with the CWM file. It's all the same. So, thank cobretti when you pass him in the forum halls and live easier knowing the OUDHITSQUAD loves YOU!

Reverb Stock System V LK2

Flashtastic Rooted Stock with custom font M950VPALK2

I'll fix the other file ASAP. Sorry for the delay, things have been kinda tough around here.
 
xInterlopeRx said:
Well, as luck would have it, I have nothing witty to follow that intro with. So, straight to the goodies. This thread is gonna be for those poor unfortunate souls who do something really bad to their phone and are ready to throw the phone into the toilet for a little lube-n-tune. I would really like to offer up a factory image, even a rooted stock image but there aren't any yet. It's up to you, the hero of the Reverb community to rescue your forum buddies with your daring attempt to pull one for us all. If you, SuperUser, can do that much, I will do the rest. Or if anyone wants to learn a bit of the behind the scenes stuff, I am more than willing to teach someone.

Lets get started!

I'll assume SuperUser already has ADB installed and the Samsung drivers. Plug in the device and get set for adb commands. You will need 4GB of free space on your sdcard to fish the file we want. So, that's something to consider.

[HIGH]adb shell
su
dd if=dev/block/mmcblk0p19 of=/data/media/system.img.ext4
exit
adb pull data/media/system.img.ext4 c:\Users\Yourname\Documents[/HIGH]Now, once you have that file I will give you access to a place to upload it. I don't use those fly by night file servers, I pay for hosting so all of us can enjoy easy access and good speeds with no waiting. Email or PM for that cuz it's a secret! Cheers and good luck SuperUser!
Click to expand...

ok, I started this, however your command sends the system.img to the internal space on phone, I stoped it before it was done when I got the low memory notification. Also, I couldn't get adb to work on windows so I did this on my linux mint 13 box. Should I just change the (of=/data/media/system.img.ext4) to say exsdcard? I've had my linux setup for about 1 year but I'm a slow learner, however, I follow instructions pretty well.
 
Has any progress been made on getting a factory image yet? My phone is all kinds of messed up from attempting to install Google Now, so it would be pretty nice to have it.
 
dobbs69 said:
ok, I started this, however your command sends the system.img to the internal space on phone, I stoped it before it was done when I got the low memory notification. Also, I couldn't get adb to work on windows so I did this on my linux mint 13 box. Should I just change the (of=/data/media/system.img.ext4) to say exsdcard? I've had my linux setup for about 1 year but I'm a slow learner, however, I follow instructions pretty well.
Click to expand...

Sorry I didn't reply directly. I forget that the OP must subscribe to each new thread he/she creates. Thanks for trying. In the future I will be sure to say whether or not the code is certain or exemplary.
 
Hey, I really appreciate what you're doing for us, Interloper, especially helping out with the dumb screw up I did. Unfortunately the Stock System image didn't go through to the phone. I have successfully flashed CWM onto my phone using Odin and then flashed back to stock recovery and kernel, and followed the same instructions to flash this system image.

Here's a screenshot of the result from Odin. And it left the phone in download mode with the progress bar not moving.

When I rebooted the phone manually, the phone still didn't boot into Android. But it can still access download and recovery modes.

Thanks again and feel free to ask any questions to help you troubleshoot my problem.
 
MetalLink said:
Hey, I really appreciate what you're doing for us, Interloper, especially helping out with the dumb screw up I did. Unfortunately the Stock System image didn't go through to the phone. I have successfully flashed CWM onto my phone using Odin and then flashed back to stock recovery and kernel, and followed the same instructions to flash this system image.

Here's a screenshot of the result from Odin. And it left the phone in download mode with the progress bar not moving.

When I rebooted the phone manually, the phone still didn't boot into Android. But it can still access download and recovery modes.

Thanks again and feel free to ask any questions to help you troubleshoot my problem.
Click to expand...

Did you make any changes at all to the file? I just checked, and evidently it is named system.img after all. Pulling the link for the time being. Working on it right now.
 
<ID:0/014> Initialzation..
<ID:0/014> Get PIT for mapping..
<ID:0/014> Firmware update start..
<ID:0/014> system.img
<ID:0/014> NAND Write Start!!
<ID:0/014>
<ID:0/014> Complete(Write) operation failed.
<ID:0/014> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
 
It takes 5 hours for me to upload an 800mb file. And, I have other things I do. I'd like to make a flashable zip and upload it, but it all takes time and testing. If the zip needs adjustments to work properly, that's another 5 hours. I'm only saying this so that everyone here understands the position I am in. I don't have a Reverb. If anyone wants to buy me one, I'll take it and test with it, but I'm not trying to do that. What I am trying to do is help you all enjoy your devices and have a bit of fun and adventure. Please be patient. Asking "when blah blah blah" does nothing to help me help you.

READ THE OP (Original Post) IF YOU NEED STABILITY, ROOTING AND FLASHING IS NOT FOR YOU. IF YOU TAKE THE RISK, YOU ASSUME THE RESPONSIBILITY.

Rant over, but will probably be included with every new post I make. That being said, the new image is live.

Flash responsibly!
 
Aww, no dice on this one, same error from Odin. No idea how to help you troubleshoot in this case...
 
Ok, I have a few ideas to maybe figure this out. Since I am on Linux, I can't try Odin, I use a program called Heimdall. It's basically like Odin in that it flashes Samsung devices. I do know however, that there are several versions of each and some devices do better on a unique version. I only have Odin 3.04 which is what you have if you got it from me. Heimdall has a Windows variant that you can try. It has a different interface, and I only use it on the command line anyway, so you will know more about that once you try it. Another way to get the image on the device is the same way we got it off, using dd through adb. This is advance stuff, but if your device can't boot into system (regular android OS) you might think about trying it assuming you can get into recovery and have ADB access to the device. If you want to try it this is what you need to do:

1. Connect the device and make sure you can do 'adb devices' and get a serial number back.

2. Extract the system.img from the .tar container.

3. Put the file on the sdcard (Use adb push c:\path\to\file sdcard or however else you want to)

4. Type:

[HIGH]adb shell
su
dd if=/sdcard/system.img of=/dev/block/mmcblk0p17

adb reboot recovery[/HIGH]

5. Wipe everything

6. Reboot

You should be able to boot to system now. Now, I've been a flashaholic too and sometimes we do some really dumb stuff and we don't disclose it on the forum. If that's you, PM me, so I can try and help you farther. If you only removed some .apks we can fix that a different way. Let me know how it all goes. Cheers and good luck!
 
thankfully i found another way to fix my phone (by using my psuedo stock rom idea that no one bothered to reply to...;)). ....anywccccho, when i try to run this, it asks for msvpc100.dll....and even trying to install V+ 2010/QT takes forever so I gave up....lol
 
petrafan007 said:
thankfully i found another way to fix my phone (by using my psuedo stock rom idea that no one bothered to reply to...;)). ....anywccccho, when i try to run this, it asks for msvpc100.dll....and even trying to install V+ 2010/QT takes forever so I gave up....lol
Click to expand...

A more descriptive title helps. Like "Fix with CWM restore image idea" You're doing great and have been very helpful, thanks!
 
True...well that was when I had come up with the idea so it was a question I had. Too bad I can't edit the title. Maybe I should create a new one...can someone delete the old thread once I copy it over?

xInterlopeRx said:
A more descriptive title helps. Like "Fix with CWM restore image idea" You're doing great and have been very helpful, thanks!
Click to expand...
 
xInterlopeRx said:
Ok, I have a few ideas to maybe figure this out. Since I am on Linux, I can't try Odin, I use a program called Heimdall. It's basically like Odin in that it flashes Samsung devices. I do know however, that there are several versions of each and some devices do better on a unique version. I only have Odin 3.04 which is what you have if you got it from me. Heimdall has a Windows variant that you can try. It has a different interface, and I only use it on the command line anyway, so you will know more about that once you try it. Another way to get the image on the device is the same way we got it off, using dd through adb. This is advance stuff, but if your device can't boot into system (regular android OS) you might think about trying it assuming you can get into recovery and have ADB access to the device. If you want to try it this is what you need to do:

1. Connect the device and make sure you can do 'adb devices' and get a serial number back.

2. Extract the system.img from the .tar container.

3. Put the file on the sdcard (Use adb push c:\path\to\file sdcard or however else you want to)

4. Type:

[HIGH]adb shell
su
dd if=/sdcard/system.img of=/dev/block/mmcblk0p17

adb reboot recovery[/HIGH]

5. Wipe everything

6. Reboot

You should be able to boot to system now. Now, I've been a flashaholic too and sometimes we do some really dumb stuff and we don't disclose it on the forum. If that's you, PM me, so I can try and help you farther. If you only removed some .apks we can fix that a different way. Let me know how it all goes. Cheers and good luck!
Click to expand...

I was looking over this thread and thought I would give it another go. So I downloaded the system tar. in the op and extracted it and put the system img. on my sdcard(not extSdCard) and used the above instructions and it work! However, the system img. is the same as thhttp://androidforums.com/reverb-all-things-root/661661-oudhs-reverb-stock-root.htmlis thread. I'm still looking for a totally stock rom img
 
so i keep getting this error when i try to flash the .tar in odin...
 

Attachments

  • fail.JPG
    fail.JPG
    16.6 KB · Views: 117
bkttk2 said:
Using Odin I have only every pushed recoveries. Is this what you are trying to do? Are you in download mode when using Odin?
Click to expand...

i accidently wiped system...
dont have any roms saved on internal memory...
cant get any roms to internal memory since there is no system to boot to...
recovery has a borked 'install from ext sd card'

so im trying to flash the stock rom with odin...
so im using the factory img in the op (its a .tar file)
yes, im in download mode..
 
davidmargolin said:
i accidently wiped system...
dont have any roms saved on internal memory...
cant get any roms to internal memory since there is no system to boot to...
recovery has a borked 'install from ext sd card'

so im trying to flash the stock rom with odin...
so im using the factory img in the op (its a .tar file)
yes, im in download mode..
Click to expand...
Okay so your basically starting from square one.

Have you tried KIES yet? You may need to fix the recovery, back to stock, and then try to reinstall ROM via Kies. This would be the easiest route.

Lets first take care of your recovery.
Try to return to the stock recovery.
Using the steps from this thread:

http://androidforums.com/reverb-all...t-brick-cwm-recovery-support.html#post5278594

Stock recovery, as well as other files can be obtained from xInterlopeRx file shares located at the following:

waywardpilgrim.net

Grab the stock recovery.

Once the stock is succesfully installed then give KIES a try.

Another option is to use Odin to install a CWM recovery. Recommend the Reverb Clockworkmod Recovery Test 8 from the mod folder. http://waywardpilgrim.net/android/samsung/sph-m950/mod/reverb-cwm-test-8.tar

Then download the rooted stock:
http://waywardpilgrim.net/android/samsung/sph-m950/mod/reverb-stock-rooted-signed.zip

The above should be able to get a workable device. If you are wanting the latest JB release I would suggest trying to use KIES to reset your phone and return to full stock.

Good luck and let us know how you fare.
 
bkttk2 said:
Okay so your basically starting from square one.

Have you tried KIES yet? You may need to fix the recovery, back to stock, and then try to reinstall ROM via Kies. This would be the easiest route.

Lets first take care of your recovery.
Try to return to the stock recovery.
Using the steps from this thread:


Stock recovery, as well as other files can be obtained from xInterlopeRx file shares located at the following:


Grab the stock recovery.

Once the stock is succesfully installed then give KIES a try.

Another option is to use Odin to install a CWM recovery. Recommend the Reverb Clockworkmod Recovery Test 8 from the mod folder.

Then download the rooted stock:


The above should be able to get a workable device. If you are wanting the latest JB release I would suggest trying to use KIES to reset your phone and return to full stock.

Good luck and let us know how you fare.
Click to expand...

I've actually tried what you suggested. That is, bringing the recovery back to stock and trying to use Kies on the stock with root rom (assuming that's the same stock with root rom from interloper's thread). Kies says the device is not supported, unfortunately.
 
You must log in or register to reply here.
Back
Top Bottom