Originally Posted by herach

Yeah, really. Tell me about it. Just like this guy (the2dcour). He hasn’t been seen since last December in this thread. http://forum.xda-developers.com/show....php?t=1216143. They come in open a thread, put some couple of posts saying (oh, I fixed this, I did this, I did that) then attach couple of files that don’t even work for us and then leave us hanging here. I even sent this guy (the2dcour) an email asking him to help us out and his work will be rewarded, but no answer.

To be fair, the2dcour did in fact unlock 2.3.4. He may have tried 2.3.5 but we need a leak from Motorola for the same to be done for this version. Be nice since pretty much all of these people are doing this in their spare time and for free. The 2.3.5 unlock will come in time, hopefully.

Originally Posted by cwill0303

To be fair, the2dcour did in fact unlock 2.3.4. He may have tried 2.3.5 but we need a leak from Motorola for the same to be done for this version. Be nice since pretty much all of these people are doing this in their spare time and for free. The 2.3.5 unlock will come in time, hopefully.

Yes. I understand that. I'm not trying to be mean or anything but at least say something. Tell us what is going on or just say (you know what I've moved on to a different project, I don't do this any more) don’t just abandon the thread. Then, we'll think of something else not just leave us hanging here and waiting. I don't even think a newer version will help. I've had some Sprint engineering 2.3.5 SBF and tried that and it didn't work. So I guess we are locked for good unless someone comes up with an unlock. I just wish I had the knowledge to do this. Till then we just have to sit and wait.

I hear ya. If i knew anything about any of it, I would be working on it endlessly, lol

Originally Posted by herach

Yes. I understand that. I'm not trying to be mean or anything but at least say something. Tell us what is going on or just say (you know what I've moved on to a different project, I don't do this any more) don’t just abandon the thread. Then, we'll think of something else not just leave us hanging here and waiting. I don't even think a newer version will help. I've had some Sprint engineering 2.3.5 SBF and tried that and it didn't work. So I guess we are locked for good unless someone comes up with an unlock. I just wish I had the knowledge to do this. Till then we just have to sit and wait.

ENG SBFs do not work on retail photons. We need an unlocked retail SBF.

Originally Posted by Lightsword1942

ENG SBFs do not work on retail photons. We need an unlocked retail SBF.

The way that I see it, it looks like there is no Unlocked retail SBF. I'll see if I can go to Sprint store tonight and see if they can fix it or exchange it either warranty or Insurance. Either way, I need to get this fixed. I'm paying $100.00 a month and I can't even use it. I know it was my mistake but I need to fix it.

Originally Posted by Lightsword1942

From the 2.3.5 rom can you run this over an adb shell and post the output?
"cat /sys/firmware/fuse/ReservedOdm"
I have been compiling the output from phones in various states in order to determine what each value means in relation to what you can flash.
so far i have this

10000000000030001000100004000-photon tried to flash photon 2.3.5 eng? currently unlocked but can't flash normal SBF
10000000000010001000100004000-standard unlocked photon
10000000000010001000100000000-standard locked photon
10000000000010001000100004000-standard unlocked electrify
30000000000030003000100004000-electrify stuck on 2.3.5 no additional info
1000000000003000100004000-electrify stuck on 2.3.5 unlocked bootloader previously installed

I havent seen my code posted yet. here you go

# cat /sys/firmware/fuse/ReservedOdm
cat /sys/firmware/fuse/ReservedOdm
20000000000020003000100000000
#
tried flashing boot unable to boot 2. about to flash 2.3.5 sbf to revive my phone

will post ReservedOdm after i flash that


it let me RSD 2.3.5 sbf file.

after flashing got this

# cat /sys/firmware/fuse/ReservedOdm
cat /sys/firmware/fuse/ReservedOdm
20000000000030003000100000000
#

Hey guys. I went to the Sprint store. They wouldn't exchange it. So, I came back home and flashed a CG9.smg and corrupted the boot loader. Now, it is stuck on Boot logo. I called the CS and I told them that it is stuck on the boot loader, so they went through some trouble shooting and it didn't work and they said they will ship me another device. I am waiting for it. I will receive it in the next couple of days. hopefully they won't find out what I did. We'll see. By the way, I am in Vegas and all drunk so wish me luck guys. Hopefully I will go home with crap load of money. Riiiigggghhhhtttt.

Hope

---

Any hope for us reckless 2.3.5 pudding flashers?

Originally Posted by firtermish

Any hope for us reckless 2.3.5 pudding flashers?

Most likely not until moto puts out an update but give me your ReservedODM output if you can, might be helpful. Run the following from adb shell or terminal.

adb shell
su
cat /sys/firmware/fuse/ReservedOdm

# cat /sys/firmware/fuse/ReservedOdm
cat /sys/firmware/fuse/ReservedOdm
30000000000030003000100000000
#

Hope it helps.


Photon flashed 2.3.5 electrify pudding from other thread. Never unlocked, but rooted. Any other info I'd be happy to give