DEV EDITION Need modem image for G900V DEV EDITION

[longus catus]

I have a developer edition phone, and I think I managed to install a retail modem. For my own reasons, I'd like the dev modem version back. Can someone create an image via cat /dev/block/.../by-name/modem > modem.img and attach it? (find /dev | grep by-name) It doesn't contain any identifying info- that's in modemst1, modemst2, and efs. But you probably know that already. No odin tar necessary, just an image is fine. Or do whatever you want, as long as I can grok it back into the image. Do what makes you happy.

I would appreciate it very much. If someone wants to get fancy and make a whole recovery boot chain (past aboot to boot, or whatever) that would be cool, too. But just a modem works. I'm talking about the files like apnhlos, carrier, boot, dbi? ddr? fota? fsc? fsg? modem pad param persdata persist recovery rpm sbl1 ssd tz. I don't know the actual boot chain and boot order. Maybe someone else does.

If one of these contains identifying information please don't shoot me, I'm not trying to steal your IMEI. But I really really really would appreciate the modem binary, and that doesn't contain personal info.

Please send me a dev edition G900V modem partition image!

 

[jpcalhoun]

I have a developer edition phone, and I think I managed to install a retail modem. For my own reasons, I'd like the dev modem version back. Can someone create an image via cat /dev/block/.../by-name/modem > modem.img and attach it? (find /dev | grep by-name) It doesn't contain any identifying info- that's in modemst1, modemst2, and efs. But you probably know that already. No odin tar necessary, just an image is fine. Or do whatever you want, as long as I can grok it back into the image. Do what makes you happy.

I would appreciate it very much. If someone wants to get fancy and make a whole recovery boot chain (past aboot to boot, or whatever) that would be cool, too. But just a modem works. I'm talking about the files like apnhlos, carrier, boot, dbi? ddr? fota? fsc? fsg? modem pad param persdata persist recovery rpm sbl1 ssd tz. I don't know the actual boot chain and boot order. Maybe someone else does.

If one of these contains identifying information please don't shoot me, I'm not trying to steal your IMEI. But I really really really would appreciate the modem binary, and that doesn't contain personal info.

Please send me a dev edition G900V modem partition image!

I maybe wrong, but I think the Dev modem and the retail modem are the same, unless however there has been an OTA that changed the retail modem. I have a Dev S5 and my modem is G900VOYU1ANCG.

 

[longus catus]

Thanks for your response.

My phone still says "MODE: developer" but I think something's not quite right. Actually at one time it didn't say developer, but I kept calm knowing that it just hurts more if you resist.. So I rooted the image and overwrote the aboot with a backup and now it says developer but it's not all quite right. I think. Uh maybe TWRP should have a "full retard/backup" option, but a recursive script over the "by-name" list works well, too.

I had ordered another dev phone a few days ago, and I think I will take the "partial refund" and get a phone that I know works, and get it right *now*. Then I'll be the one making a recovery tar that nobody will care about, but should anyone else have the misfortune of being me (currently the count is 1), they will find some respite in that tar image. But I can still write and boot assorted kernels, recoveries, and roms. So obviously it is somewhat of a development phone.

I maybe wrong, but I think the Dev modem and the retail modem are the same, unless however there has been an OTA that changed the retail modem. I have a Dev S5 and my modem is G900VOYU1ANCG.

I dunno, you may be right. I made a tar with the order of boot, recovery, modem. Because... anyway, odin says the following:

<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.

When I have a tar in the order of KLTE_USA_VZW.pit, aboot.mbn, spl1.mbn, rpm.mbn, tz.mbn, sdi.mbn, NON-HLOS.mbn, boot.img recovery.img modem.img, I get the following on my phone:

SECURE CHECK FAIL: modem
Invalid percent of drawing download progress bar!
SECURE CHECK FAIL: aboot.

Well I checked the md5sum of that aboot file and the very aboot partition image and they're one and the same, so something is up. I have no idea what I'm doing, but I'm doing it pretty well. It's funny because if I 'cat modem.img > disk' I will end up with the Verizon unauthorized software triangle of doom. So that's one reason I think the dev and retail modems are different. And the maligned bootloader shows its sensitive side, giving an accurate warning of impending doom.

C:\Users\andrew\Downloads\dev>find "G900" modem

---------- MODEM
G900V.00
8░σk |░σk0╚░σk6▒σG900V.003
G900V.05
SM-G900V
G900VVRU1ANCG

Does yours say the same thing?

Or uh... grep -a G900V /path/to/modem/partition | strings ... or you could adb pull the modem partition... I'm sure there are more ways, most of which do not require goat sacrifice (I wish I had known this before).

 

[longus catus]

So I got all the partition images from a totally new untouched developer phone.

Writing the other phone's aboot to my aboot partition doesn't seem to do anything abnormal except "Mode: Developer" is gone. And is back when I flash my original copy.


I created a tar called modem.tar with the phone's own modem.bin as its only contents. This is what I see on the screen when I try to flash it:

ODIN MODE
PRODUCT NAME: SM-G900V
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
REACTIVATION LOCK(kk): OFF
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, A1, A1, P1
MODE: Developer
UDC START
SECURE CHECK FAIL : modem

Which is weird, because that's the modem already installed, through dd/cat to the partition.

I created a tar that had the same file order as G900VVRU1ANCG_G900VVZW1ANCG_G900VVRU1ANCG_HOME.tar.md5, which is aboot, sbl1, rpm, tz, sdi, NON-HLOS, boot, recovery, system, cache, and modem. With just up to but not including system. And failed on flashing the phone's own aboot. Maybe because there's trailing garbage from trying to flash the whole partition image instead of just the signed portion of the file. So how do I know how large the actual file to flash should be...

The modem image says it's G900VOYU1ANGC, which is different than can be seen in the above tar file.

It would be nice to know if the trailing garbage is why the file doesn't flash through odin-only the unprotected (as dev edition) recovery boot and system are ok with it. And how to get rid of the garbage. In the file, that is.

 

[c89memcpy]

Hey longus catus, did you ever manage to create a restoration image for other SM-G900V dev edition users? I have one as well, flashed TWRP via ODIN, went to make a backup, but I didn't double check that the backup sync'd to my SD card and installed CM11 only to find that my backup of stock was gone. I can get 4G data, but I cannot make or receive calls. I am not sure of what could have happened. After a lot of digging I managed to find a system.img and boot.img from stock ANCG, however, I still cannot make or receive calls (or use <= 3G data).

I am really hoping that my EFS did not get corrupted somehow. My IMEI is still valid, so I do not think that is the case, probably just filling myself with unwanted dread. Anyway, if you managed to create a good recovery tar it might go a long way toward my debugging. I am not far from declaring this a very expensive PDA.

 

[unruly1]

Hey longus catus, did you ever manage to create a restoration image for other SM-G900V dev edition users? I have one as well, flashed TWRP via ODIN, went to make a backup, but I didn't double check that the backup sync'd to my SD card and installed CM11 only to find that my backup of stock was gone. I can get 4G data, but I cannot make or receive calls. I am not sure of what could have happened. .

I am in almost the exact same boat. The only difference for me is that I used Philz (instead of TWRP) because of the fact that I wanted to verify I could restore my backup and after 3 times of the backup disappearing with TWRP, I flashed Philz, then backed p, then verified the backup restored. That is when I flashed Cyanogenmod and had "no service" so I restored my backup and assumed I was up and running until a day or two later when I got voicemail notifications. I am not able to make or receive calls but everything else seems to work. Any ideas? How can I get a "stock" S5 dev edition tar that I can restore?

---------- Post added at 09:47 AM ---------- Previous post was at 09:00 AM ----------

I am in almost the exact same boat. The only difference for me is that I used Philz (instead of TWRP) because of the fact that I wanted to verify I could restore my backup and after 3 times of the backup disappearing with TWRP, I flashed Philz, then backed p, then verified the backup restored. That is when I flashed Cyanogenmod and had "no service" so I restored my backup and assumed I was up and running until a day or two later when I got voicemail notifications. I am not able to make or receive calls but everything else seems to work. Any ideas? How can I get a "stock" S5 dev edition tar that I can restore?

well in a very strange turn of events... This is what I did to fix my issue....

1. powered off my phone
2. removed micro SD card
3. removed SIM card
4. powered on phone
5. waited 5 minutes
6. powered off my phone
7. installed SIM card
8. installed micro SD card
9. powered on phone
10. placed a call from my work phone to GS5 Dev Edition and GS5 rang.
11. placed a call from GS5 Dev Edition to work phone and work phone rang.

I really hope this helps someone else.

 

[c89memcpy]

Wow I really hope that works. I will try it when I get off work tonight.

 

[c89memcpy]

It did not work... Were you running the stock firmware?

 

[c89memcpy]

I flashed to stock and it worked. Thank you so much. I am now running albinoman887's cm12 build successfully (with the exception of NFC).

 

[Sedinsamsung]

Question

I maybe wrong, but I think the Dev modem and the retail modem are the same, unless however there has been an OTA that changed the retail modem. I have a Dev S5 and my modem is G900VOYU1ANCG.

If you change modem of g900v to g900t, will 4g lte work, I have problem with my Verizon G900V it shows only e, no lte ot 4g :crying: So if I change modem to t-mobil's modem will it work?

Thanks