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

Root [OUDHS] Reverb Stock with Root

I tried flashing the "rever-stock-system-LK2-2.tar" file in download mode using Odin 3.07 and got the following error:

<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> system.img
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!

I also tried using the "reverb-stock-rooted-signed.zip" file and flashing from sdcard in recovery mode and got an error message saying:

E:Signature Verification failed

Any idea what I am doing wrong. Others seem to have had success with this. Not sure what i am doing wrong. I must have missed a step somewhere.

Reverb was OTA upgraded to JB 4.1.2. I am trying to get it back to ICS 4.0.4.

I have flashed CWM Test 8. But am still unable to find a image either .tar package to download via Odin, or .zip package to load in recovery mode that restores the phone to ICS.

Any help is greatly appreciated.

Thanks,
Rash
 
rashmia said:
I tried flashing the "rever-stock-system-LK2-2.tar" file in download mode using Odin 3.07 and got the following error:

<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> system.img
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!

I also tried using the "reverb-stock-rooted-signed.zip" file and flashing from sdcard in recovery mode and got an error message saying:

E:Signature Verification failed

Any idea what I am doing wrong. Others seem to have had success with this. Not sure what i am doing wrong. I must have missed a step somewhere.

Reverb was OTA upgraded to JB 4.1.2. I am trying to get it back to ICS 4.0.4.

I have flashed CWM Test 8. But am still unable to find a image either .tar package to download via Odin, or .zip package to load in recovery mode that restores the phone to ICS.

Any help is greatly appreciated.

Thanks,
Rash
Click to expand...

Have you tried the method in the following link:

http://androidforums.com/reverb-all-things-root/733495-out-box-rom.html#post5927479
 
Extract the .tar and tell me if the file inside is called system.img.ext4. If not, there is one problem. If you have the means, ie LINUX, or maybe 7zip, you can fix it there. rename the file to system.img.ext4, tar again, md5sum again then try the flash. I'll check it out myself so the hosted file is correct in the future. I though hitesh used it successfully so I did not verify before uploading. If you cannot do those things, let me know. I'll tell you once I'm done fixing it and you can re-download.

EDIT: I was able to ssh into our server and modify our image. It is now called reverb_stock_LK2.tar. Download that file and flash it. Caveat one: there is no boot.img. I need to add that to revert to ISC now that I'm thinking about it.... check back in a couple minutes. if that flash fails. Sorry for the poor files. I spent $50 on a dev device and it bricked. I have had very little help in that regard and I am not even a VMU customer. Without a device, I cannot test these files locally and must embarrass myself with posts like these....
 
I don't know what you have to be embarrassed about. Considering that you don't even have the device we use, I'd say what you've been able to do is quite impressive!
 
xInterlopeRx said:
Read my response above, then ignore most of it selectively: Then, use this file to fix yer stuff: http://www.oudhitsquad.com/android/Samsung/SPH-M950/stock/reverb_system_boot_LK2.tar

Met me know how it goes.
Click to expand...
The image seem to get closer. I get the following message in Odin:

<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> system.img.ext4
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!

When I try to boot the phone, I get the first SAMSUNG splash screen (with the caution triangle), then i get the Virgin Mobile splash screen, then a second SAMSUNG splash screen. But, it seems to freeze at that point.

I noticed the boot image has just a .img extension, does it also require .ext4 extension to load properly on the phone?

Thanks again for all your help.
 
No, we get the filenames from the PIT/GPT which is how I determined the system.img needed to be changed. Chances are it's not booting because I packed in a JB kernel. I don't have a lot of files for this device, so if you can link me to an ICS kernel I can fix it. Also, be sure to wipe partitions using recovery. I don't have a lot of time to be looking for the files.
 
I am not sure what i did wrong. But, it appears to be a brick now. Will not respond to any power up sequence. No normal boot, or recover, or download mode. The screen remains dark for all key sequences. The battery was fully charged before I started, so i don't think that is the issue.

I have been thinking about just getting a new phone, I guess it time.

Thanks for your help anyway.
 
Man, I feel that! I have a brick on my desk too. Files removed for the safety of the entire world. Links to kernels are now dead. For anyone following this thread, I (we) need a good ICS kernel. Message me if you are on ICS and can pull the boot.img.
 
rashmia said:
I am not sure what i did wrong. But, it appears to be a brick now. Will not respond to any power up sequence. No normal boot, or recover, or download mode. The screen remains dark for all key sequences. The battery was fully charged before I started, so i don't think that is the issue.

I have been thinking about just getting a new phone, I guess it time.

Thanks for your help anyway.
Click to expand...

give adb a try...
 
xInterlopeRx said:
Man, I feel that! I have a brick on my desk too. Files removed for the safety of the entire world. Links to kernels are now dead. For anyone following this thread, I (we) need a good ICS kernel. Message me if you are on ICS and can pull the boot.img.
Click to expand...

You can find the ICS boot.img in the following stock ROM by Martinez

http://androidforums.com/reverb-all-things-root/663688-rom-4-0-4-stock-rom-plus.html

I am not sure which ICS revision was that ROM though. If you want the latest ICS revision, I can just build the stock kernel for you from the MB3 Samsung source code and put in the ICS boot.img.
 
The problem is not the kernel itself What I had wrong was the command line instruction. I ended up using your kernel to get it mrg666. Any chance one of you more skilled guys can get me the bootable recovery image I need to try and restore my device from emmc boot?
 
xInterlopeRx said:
The problem is not the kernel itself What I had wrong was the command line instruction. I ended up using your kernel to get it mrg666. Any chance one of you more skilled guys can get me the bootable recovery image I need to try and restore my device from emmc boot?
Click to expand...

Can't you use the cwm-test8 you had built? It works with ICS. You can try the latest JB recovery too. The recovery images are in either tar or zip files. Sorry if I am missing something and repeating the obvious.

Recovery and boot images are the same thing, just the filename of the image file and ramdisk.gz inside are different. So a bootable recovery image can be created with the same procedure like an ordinary boot image is created. It becomes a recovery image if the image file renamed recovery.img, ramdisk.gz for recovery included, and flashed on the recovery partition.
 
What you are missing: I bricked my device ages ago and kinda abandoned support for it. Subsequently, I clean out my files. Since I'm working on the Victory port for cm-10.2 my head just isn't in the game here. But thanks. I got what I needed but I killed my only tester... Now, if someone could follow the thread I posted and pull the partitions I need to try the emmc boot fix, me and the tester might be able to fix our phones. It works on a lot of 8960 devices but is untested on 7xXX devices and is dependent on aboot.
 
So is this stock rom 100% working now? I intend to sell this device and just looking to flash it to a stock rooted rom. This device isn't that great of quality and it's kind of sickening that Samsung would put the Galaxy name on it. The only Galaxy thats worse is the Prevail. I regret buying it. Loving my GS3. I have KitKat flashed and it handles it nicely.
 
Is this the noshhh4u super user rom cause as far as I know theres a lot of shhing in my neighborhood. And isn't that copyright infringement of chainfires super user app
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom