Galaxy Note 3 Verizon Developer Edition is COMING SOON according to samsung

[keynith]

My DE's EFS got corrupted while using EFS Professional. I clicked on "NV Backup" in EFS Pro, my phone immediately rebooted into boot-loops. After about two weeks of trying to fix i decided to send it in to Samsung to get DE firmware re-flashed.

I talked to a Samsung CSR and told him that it was a developer device, (nobody knows about these) told him: It had been rooted, knox was tripped, IMEI missing, firmware corrupt, out of warranty repair, I want to pay for the re-flash. All I want is original DE firmware flashed, I expect to pay for re-flash. He wrote down my requests in the ticket, and noted "out of warranty repair" on ticket.

So after 8 days in Texas I find out that the repair facilities policy is "any phone received that has been rooted is automatically deemed "BER" (beyond economical repair)". That's great to know!
I did flash back to stock before shipping. So just knox was tripped, and recovery error "E:failed to mount /efs (Invalid argument)".

Does anyone know of a Samsung technical services, or contact that can flash the firmware back to original DE, and write IMEI?



2. Product Information
Model Number : SM-N900VMKEVZW
Serial Number : 99000436583147*
Product Symptoms : Operation System Issue/Platform / Software/Operating System Issue
Warranty : Out of Warranty


SAMSUNG REPAIR CENTER,RSI
2901 SUMMIT AVE SUITE 100
Plano TX

*03/12/2014//20:28:52//0001773863//Telephone//ASC*
3/12/2014 7:28 PM-Sylvia Hernandez: The unit is shipped.
*03/12/2014//20:11:50//0001773863//Telephone//ASC*
3/12/2014 7:10 PM-PBA Inspection: The unit has left the technician. SOLUTION: BER
*03/12/2014//20:10:49//0001773863//Telephone//ASC*
DEVICE ROOTED
*03/11/2014//12:06:34//0001773863//Telephone//ASC*
3/11/2014 11:06 AM-Selene Herrera: The unit has been received. Pack Condition: Fair Packaging (Box & Cushion)
03/06/14 Received Signed for by JESUS
03/04/14 Shipped

Nah your screwed. Same thing happened to me a while back. Sent it over to @oneandroidnut for him to tinker with. Just bought a regular note 3 because sammy hasnt gotten the dev editions in stock.

The only way to fix it is to get the stock images, which samsung probably wont put up because then people could potentially unlock the retail version note 3

---------- Post added at 09:03 PM ---------- Previous post was at 09:01 PM ----------

Can you do a battery pull, boot into download mode, and use Odin to install the factory DE tar?

Sent from my SM-N900V using Tapatalk

There is no stock img for the dev and the tars will not work so he's done for.

 

[radionerd]

Nah your screwed. Same thing happened to me a while back. Sent it over to @oneandroidnut for him to tinker with. Just bought a regular note 3 because sammy hasnt gotten the dev editions in stock.

The only way to fix it is to get the stock images, which samsung probably wont put up because then people could potentially unlock the retail version note 3

---------- Post added at 09:03 PM ---------- Previous post was at 09:01 PM ----------



There is no stock img for the dev and the tars will not work so he's done for.

Thanks for sharing your similar experience. When mine comes back I will continue to look at the block mounts folders with comparison of a good DE. Maybe someone knows the location where the IMEI could be edited back in, if it even resides in the mounts

 

[keynith]

Thanks for sharing your similar experience. When mine comes back I will continue to look at the block mounts folders with comparison of a good DE. Maybe someone knows the location where the IMEI could be edited back in, if it even resides in the mounts

Yeah mine just boots up and goes into reboot mode. It sucks

Sent from my SCH-I535 using Tapatalk

 

[cam1pbell]

Delete Post... Thanks

Sent From My SM-N900V Developer Addition

 

[DavidFlory]

Nah your screwed. Same thing happened to me a while back. Sent it over to @oneandroidnut for him to tinker with. Just bought a regular note 3 because sammy hasnt gotten the dev editions in stock.

The only way to fix it is to get the stock images, which samsung probably wont put up because then people could potentially unlock the retail version note 3

---------- Post added at 09:03 PM ---------- Previous post was at 09:01 PM ----------



There is no stock img for the dev and the tars will not work so he's done for.

I understand that there is no "factory" image for a SM-N900V DE. I meant the MJE stock tar from az-bikers ROOT thread using Odin. Why won't that work? Just curious.

Sent from my SM-N900V using Tapatalk

 

[keynith]

I understand that there is no "factory" image for a SM-N900V DE. I meant the MJE stock tar from az-bikers ROOT thread using Odin. Why won't that work? Just curious.

Sent from my SM-N900V using Tapatalk

Idk didn't work on mine

Sent from my SCH-I535 using Tapatalk

 

[droidstyle]

Idk didn't work on mine

Sent from my SCH-I535 using Tapatalk

That is because you fubard yours tinkering around with NV backup...the restore file beans made will work fine for most bootloop situations. Play with fire long enough and eventually you will get burned.

Did you ever try sending to mobile tech and see if Jtag would bring it back?

And Samsung is a bunch of D-Bags!! Sorry to hear about your troubles.

 

[keynith]

That is because you fubard yours tinkering around with NV backup...the restore file beans made will work fine for most bootloop situations. Play with fire long enough and eventually you will get burned.

Yeah i know. But this guy all also messed up his doing the same thing so I'm just telling him there isn't much hope. Which sucks.

Sent from my SCH-I535 using Tapatalk

---------- Post added at 07:37 AM ---------- Previous post was at 07:24 AM ----------

That is because you fubard yours tinkering around with NV backup...the restore file beans made will work fine for most bootloop situations. Play with fire long enough and eventually you will get burned.

Did you ever try sending to mobile tech and see if Jtag would bring it back?

And Samsung is a bunch of D-Bags!! Sorry to hear about your troubles.

Nah i didn't send it to them. I may try doing that later on though once i get it back.

Sent from my SCH-I535 using Tapatalk

 

[LillieBennett]

My DE's EFS got corrupted while using EFS Professional. I clicked on "NV Backup" in EFS Pro, my phone immediately rebooted into boot-loops. After about two weeks of trying to fix i decided to send it in to Samsung to get DE firmware re-flashed.

I talked to a Samsung CSR and told him that it was a developer device, (nobody knows about these) told him: It had been rooted, knox was tripped, IMEI missing, firmware corrupt, out of warranty repair, I want to pay for the re-flash. All I want is original DE firmware flashed, I expect to pay for re-flash. He wrote down my requests in the ticket, and noted "out of warranty repair" on ticket.

So after 8 days in Texas I find out that the repair facilities policy is "any phone received that has been rooted is automatically deemed "BER" (beyond economical repair)". That's great to know!
I did flash back to stock before shipping. So just knox was tripped, and recovery error "E:failed to mount /efs (Invalid argument)".

Does anyone know of a Samsung technical services, or contact that can flash the firmware back to original DE, and write IMEI?



2. Product Information
Model Number : SM-N900VMKEVZW
Serial Number : 99000436583147*
Product Symptoms : Operation System Issue/Platform / Software/Operating System Issue
Warranty : Out of Warranty


SAMSUNG REPAIR CENTER,RSI
2901 SUMMIT AVE SUITE 100
Plano TX

*03/12/2014//20:28:52//0001773863//Telephone//ASC*
3/12/2014 7:28 PM-Sylvia Hernandez: The unit is shipped.
*03/12/2014//20:11:50//0001773863//Telephone//ASC*
3/12/2014 7:10 PM-PBA Inspection: The unit has left the technician. SOLUTION: BER
*03/12/2014//20:10:49//0001773863//Telephone//ASC*
DEVICE ROOTED
*03/11/2014//12:06:34//0001773863//Telephone//ASC*
3/11/2014 11:06 AM-Selene Herrera: The unit has been received. Pack Condition: Fair Packaging (Box & Cushion)
03/06/14 Received Signed for by JESUS
03/04/14 Shipped

That sucks more now, Samsung's refusal to support is near absolute!

SM-N900V DE

 

[keynith]

That sucks more now, Samsung's refusal to support is near absolute!

SM-N900V DE

I know all they literally have to do is re-flash it. So easy. Yet they wont which is frustrating.

 

[jmichaels1982]

I know all they literally have to do is re-flash it. So easy. Yet they wont which is frustrating.

Got the same response today after I got a hold of executive relation suppport. Recorded the whole conversation..she pretty much said we have no way of re-flashing the phone ! She said she has a situation like this and no one has figured out what to do. She also said no one will Call me back because no one knows what to do. That's the end of my journey.

 

[keynith]

Got the same response today after I got a hold of executive relation suppport. Recorded the whole conversation..she pretty much said we have no way of re-flashing the phone ! She said she has a situation like this and no one has figured out what to do. She also said no one will Call me back because no one knows what to do. That's the end of my journey.

Honestly, If you get over the whole DE thing and just want your note 3 back, you could try flashing the retail stock images. I thought about that today, and since I just got a new note 3 (retail version) I was thinking of trying it down the line, knowing it would lock the bootloader, just so I could have one to sell and move on.

 

[jmichaels1982]

That was my original problem

Honestly, If you get over the whole DE thing and just want your note 3 back, you could try flashing the retail stock images. I thought about that today, and since I just got a new note 3 (retail version) I was thinking of trying it down the line, knowing it would lock the bootloader, just so I could have one to sell and move on.

I used Kies on my DE, and it locked it up. Thats why i wanted a re-flash. The phone is just behaving like retail edition.

 

[DavidFlory]

You have locked your bootloader. AFAIK that is permanent. KIES does that.

Sent from my SM-N900V using Tapatalk

 

[LillieBennett]

Got the same response today after I got a hold of executive relation suppport. Recorded the whole conversation..she pretty much said we have no way of re-flashing the phone ! She said she has a situation like this and no one has figured out what to do. She also said no one will Call me back because no one knows what to do. That's the end of my journey.

She is not talking to the division who prepares the DE. What happened with the "flashed a T-Mobile rom" story. It sounded like you found a way through. Did you ever go back to kies to see if it recognized you as T-Mobile? Thanks for this pioneer work, your pain is helping the rest of us.

SM-N900V DE

 

[abe_cedar]

That sucks more now, Samsung's refusal to support is near absolute!

SM-N900V DE

+1

 

[varunkrt]

Question

How to identify developer edition and retail edition phone?

 

[cam1pbell]

How to identify developer edition and retail edition phone?

Under the battery it should say. Developer Device. Plus the box also says Developer Device.

Sent From My SM-N900V Developer Addition

 

[DavidFlory]

Under the battery it should say. Developer Device. Plus the box also says Developer Device.

Sent From My SM-N900V Developer Addition

However, if KIES has been run on the phone then the bootloader may have been relocked and that makes it almost retail.

Sent from my SM-N900V using Tapatalk

 

[oneandroidnut]

Nah your screwed. Same thing happened to me a while back. Sent it over to @oneandroidnut for him to tinker with. Just bought a regular note 3 because sammy hasnt gotten the dev editions in stock.

The only way to fix it is to get the stock images, which samsung probably wont put up because then people could potentially unlock the retail version note 3

---------- Post added at 09:03 PM ---------- Previous post was at 09:01 PM ----------



There is no stock img for the dev and the tars will not work so he's done for.

yes nothing you can do unless we ever get stock dev files