Develop Bugs

[Release] New firmware: JRDNEM_U3_3.4.2_131-003_DEBLUR

Can't post in Dev theme, but you must know:
h**p://depositfiles.com/files/2qilmot3n
h**p://www.multiupload.com/2PA2X9N2BO
Is a signed SBF, from guy, who leak for as TMO firmware =)
Code:
Filename: JRDNEM_U3_3.4.2_131-003_DEBLUR_SIGN_SIGNED_USAJRDNEMARAB1B8ORAPL035.0R_USAJRDNFRYOORAPL_P006_A002_M0
01_HWp3_Service1FF.sbf
Creation Date: 02/01/2011 08:53:04
File size: 378288514
RAM DL Version: v0x001000
Bootloader Version: -------------
Platform: 4G OMAP
HAB Type: Signed Production
Get from Russian forums =D
New info: firmware for Orange
Other link: h**p://www.multiupload.com/2PA2X9N2BO
Sry for my Eng. I'm on emotions xD

Is this Central Europe version ? At 2.1 only CE doesn't contain Motoblur.

The filename has USA in it twice, does that mean is a US version?

Oh my god its a deblured froyo
Sent from my MB525 using XDA App

I'm can't answer you both.
All Defy firmware start like "USA..." (like сountry of origin) and end "RTGB" - mean Retail Great Britan, "RTCEE" - Retail Central Europe, i guess.
This firmware ends by "RAPL", i guess it's Poland firmware (?)
Many Europien languges are included © The guy from whom it was leaked

iHedG said:
Can't post in Dev theme, but you must know:
h**p://depositfiles.com/files/2qilmot3n
Is a signed SBF, from guy, who leak for as TMO firmware =)
Code:
Filename: JRDNEM_U3_3.4.2_131-003_DEBLUR_SIGN_SIGNED_USAJRDNEMARAB1B8ORAPL035.0R_USAJRDNFRYOORAPL_P006_A002_M0
01_HWp3_Service1FF.sbf
Creation Date: 02/01/2011 08:53:04
File size: 378288514
RAM DL Version: v0x001000
Bootloader Version: -------------
Platform: 4G OMAP
HAB Type: Signed Production
Get from Russian forums =D
Sry for my Eng. I'm on emotions xD
Click to expand...
Click to collapse
Ok i have posted this in the Development section with all credits to you. Thank you for keeping an eye on this. Let us know if more are to come

Does it have a call recorder built-in?

If anyone flashes this can they post a nandroid backup please.

http://forum.xda-developers.com/showthread.php?t=940238
Talk turns to something there ^__^

There's a thread already in the Dev section on this: http://forum.xda-developers.com/showthread.php?t=940238

[REF]Gathered knowledge of VP roms

Background info:
All Dell android devices use 'pkgs' as their method of doing rom updates.
The VP uses FFUs as it's a WP7 device, I believe that pkgs (which are unique to dell devices) are functionally very similar to FFUs (which are used by all WP7 devices(?) )
I am the master maintainer of Dell device pkgs and have the largest collection outside Dell itself. I am in the process of researching VP FFUs in the hopes of being able to mirror and provide guides on restoring back to stock roms.
Unfortunately the biggest difference is that FFUs appear to be internal-use only, as in they're ment for servicing tools used only by dell(?).
PKGs are intended for consumer use, and the OTA ones are available on dell's update-site: mobileupdate.dell.com
If this is true, then FFUs are much less common, and from what I've seen the only FFU available is for 104 (See Dell Venue Pro # Official Roms - XDA wiki for more information, and Dell Venue # Official Roms -XDA wiki for a comparison)
updatewp7.exe is similar to fastboot on android, it allows you to directly upload images to the device's respective partitions(?)
Also: the words 'rom' 'firmware' 'drivers' will be used interchangably here, they all mean the same thing.
Information:
The updates available to you are the same as on dell android OTAs, it depends on your currently installed rom.
Currently the track is:
00 EU/US (unlocked) devices get updates first
31/33 (at&t and tmobile USA respectively) get updates afterwards, which is consistant with the way dell manages their ota updates.
Bar the fact that Dell is contractually obligated to release them in a 'timely' manner, 31/33 devices are usually last to get them as they're carrier branded devices.
When the VP was released the primary region was 33 though so it was by default the target region.
As the VP is available unlocked the 00 region has taken over as the one to recieve them first.
Externally (visible to all users though system:about) there are two major version numbers:
OS version: which is the installed version of WP7
Firmware version: which is the part we're interested in
Internally, it's somewhat different (checkable though EM:phone information)
SW version:
OS version from before
Actual oem version
current lock status (?)
SW build date & time:
Example:
My current rom is OS 7720/FW 219, which would look like:
Externally:
OS version: 7.10.7720.68
Firmware version: 2250.1800.7720.219
Internally:
2250.1800.7720.219
GLEOS2A421933_s
TMO-US
Build date: 20110822 18:33:15
Translated: WP7 7720
Firmware version: 219
Hardware version: 2A4
Region: 33 (TMO-US)
Build date: Aug 22, 2011
General rom update process:
When an update is available, zune downloads the following files:
If available, a delta from <your installed version> to <the current version>
VP driver cab
The first set is an oversimplication, but essentially it is a dozen cabs that comprise the full update.
These are not device specific and are the same for all devices that are eligible to update(?)
The last file is device and carrier specific. These are what sets each individial device and carrier apart from eachother.
What I need from you:
Internal version numbers from EM app
Charastics of your device
Relative age (launch, near launch, very recent, etc)
Side of preinstalled sd card
Original lock condition and current lock condition
How to find internal version numbers:
Turn on device and open up dialer
Dial "##634#" (without the quotation marks)
Select "Phone Information"
Finished
What I hope to come out of this:
More complete list of VP roms (firmware)
Information on the hardware submodel numbers
Possibly a guide for flashing the VP
Currently confirmed submodels and regions:
Submodels:
1A4
2A4
Regions:
00EU - Unlocked EU Retail
00US- Unlocked US Retail
31 - At&t
33 - T-Mobile (USA)
Current OS version:
00EU - 8107
00US - 8107
31 - (?)
33 - 7720

my dvp too has the same specs as you have mentioned
2250.1800.7720.219
GLEOS2A421933_s
TMO-US
Build date: 20110822 18:33:15
Further hardware build is 2.1.2.0.0
EM is 1.12
Still have not got the 8107 update nor the 7740 update. Force updates too dont work. Seems all users with this specific model are not getting the new updates.

Yea, yours looks pretty much identical to mine. Is yours an 8gb one?

TheManii said:
Yea, yours looks pretty much identical to mine. Is yours an 8gb one?
Click to expand...
Click to collapse
Yes 8GB.
Also one thing I have noted is that I m not facing the disappearing keyboard issue most users are complaining. not sure if i m missing anything in terms of understanding the problem. but the keyboard both software one and the hardware one work fine without any issue

my dvp too has the same specs as you have mentioned
2250.1800.7720.219
GLEOS2A421933_s
TMO-US
Build date: 20110822 18:33:15
Further hardware build is 2.1.2.0.0
EM is 1.12
Still have not got the 8107 update nor the 7740 update. Force updates too dont work. Seems all users with this specific model are not getting the new updates.
my phone 16gb

Once I get a couple version numbers from non tmo branded devices I can draw a conclusion.
But my current thinking is that 219-33 ones that came with it preinstalled are intentionally not being given updates (or the converse, they forgot to add 219-33 to the update whitelist)
On the S5 and V, several pre-installed roms have no upgrade paths and must be manually upgraded for this very reason. These specific roms are ONLY available pre-installed and other devices of the same grouping can update because they have a common rom.
Example:
An S5 with 347 preinstalled cannot OTA to 351, but an S5 with 318 can OTA to 351. 347 can be easily manually upgraded to 351.
All 3 mentioned roms are intended for generic/retail S5's which is now the majority of the remaining S5's available.

Mine Europe Factory unlocked 8Gb with Mango update installed. Buyed new early summer 2011.
From EM:
SW version
2250.1800.7720.219
GLEOS2A421900EU_S
000-88
HW version
2.1.2.0.0
SW build date & time
20110822 17:12:49
From Settings/About:
OS version 7.10.8107.79
Firmware revision number: 2250.1800.7720.219
Hardware revision number: 112.576.2.0

Partition Layout FFU file - example:
information table --> HashTable.blob
amss.mbn
appsboot.mbn
apps.mbn
dbl.mbn
dsp1.mbn
fsbl.mbn
osbl.mbn
+
OS Section
-->User Part etc...
-->BLDR
-->SLDR
-->NK
-->IMGFS
-->Users Sector etc....

Igoran said:
Mine Europe Factory unlocked 8Gb with Mango update installed. Buyed new early summer 2011.
From EM:
SW version
2250.1800.7720.219
GLEOS2A421900EU_S
000-88
HW version
2.1.2.0.0
SW build date & time
20110822 17:12:49
From Settings/About:
OS version 7.10.8107.79
Firmware revision number: 2250.1800.7720.219
Hardware revision number: 112.576.2.0
Click to expand...
Click to collapse
Ah finally an AWS user that isnt tmo (hardware wise it's an AWS model still) Like I thought EU would be 00 or something, I'll update the OP.
00EU is a funny way to do it, then again the way they did it on the S7 isnt any better
They could have done 00 = Unlocked EU, 30 = Unlocked US
Perhaps 219-00xx is given updates and 219-33 isnt. So far that fits the pattern
Nokser said:
Partition Layout FFU file - example:
information table --> HashTable.blob
amss.mbn
appsboot.mbn
apps.mbn
dbl.mbn
dsp1.mbn
fsbl.mbn
osbl.mbn
+
OS Section
-->User Part etc...
-->BLDR
-->SLDR
-->NK
-->IMGFS
-->Users Sector etc....
Click to expand...
Click to collapse
Is there a DT.img? Besides that and the android-specific boot/recovery/system.imgs it's virtually identical to the contents of a pkg (which makes sense, they fulfill the same role)
Edit: Managed to extract the NK and imgfs parts, havnt figured out how to extract the others

Igoran said:
Mine Europe Factory unlocked 8Gb with Mango update installed. Buyed new early summer 2011.
From EM:
SW version
2250.1800.7720.219
GLEOS2A421900EU_S
000-88
HW version
2.1.2.0.0
SW build date & time
20110822 17:12:49
From Settings/About:
OS version 7.10.8107.79
Firmware revision number: 2250.1800.7720.219
Hardware revision number: 112.576.2.0
Click to expand...
Click to collapse
Mine is the same as above.

Can anyone get and upload ffu file of 219.33?
http://mobileupdate.dell.com/?version=GLEOS2A421933 -doesnt work.
multiupload.com with VenuePro_flash_GLEOS2A_US_TMO_SIGNED_SWV0105_LP003 0_RV001_RETAIL.zip doesnt work either.

It doesnt work with the VP as dell doesnt host them themselves (because it runs WP7), it's all done though windowsupdate.com
The FFU's, even though they are similar to PKGs are not intended for general release. It would be closer to QDL tool as those are not ment for general release, but have the capability of restoring a bricked device.

What do you mean- Flashing of VenuePro_flash_GLEOS2A...ffu via zune updatewp.exe will lead to brick?
QDL tool, as we seen on service manual. I bet update rom is stored on sd-card too. Yes another questions who can get this tool and how to read unknown formatted sd-card?
I need any PDA retail or TM ffu for this device to try to flash and modify if it works..

heineken78 said:
What do you mean- Flashing of VenuePro_flash_GLEOS2A...ffu via zune updatewp.exe will lead to brick?
QDL tool, as we seen on service manual. I bet update rom is stored on sd-card too. Yes another questions who can get this tool and how to read unknown formatted sd-card?
I need any PDA retail or TM ffu for this device to try to flash and modify if it works..
Click to expand...
Click to collapse
Not sure what you're talking about,
but with regards to the sdcard, WP7 devices 'lock' them so they're difficult to reformat for use as a normal sd card.

Updated op with more info, will eventually move it all over to the wiki once there's enough to warrent it's own page/section on a page
Still missing info from a at&t VP, and any other carrier ones that i'm unaware of

Can I install roms of Venue Pro to my Dell Venue, which runs android

mikecore said:
Can I install roms of Venue Pro to my Dell Venue, which runs android
Click to expand...
Click to collapse
If the files get rewritten to the specs of it yes. Otherwise that would just cause it to either brick or bootloop.

Problems updating to 4.0 and changing CSC

I need help updating to android 4.0. I have been going trough pages and reading, but there is simply too much stuff that i cant understand. Here is the situation: I can't update to android 4.0 through kies. What i need to do?
Model number: GT.i9100
Android version: 2.3.4
Baseband version: I9100XXKG1
Kernel version: 2.6.35.7-i9100XXKG1-CL349526 [email protected] #2
Build number: Gingerbread.XXKG1
I have rooted my phone earlier, installed custom ROM, and then installed android 2.3.4 stock firmware. Information above tells everything about my SGS2. I can't find android 4.0 firmware download links, or instructions how to even do it. I have odin, and before i rooted my phone i took this information up what my phone used to be
baseband 19100xxki4
kernel i9100xwki8
To be hones, i don't know what those even mean. I only know that now they are different, and because my CSC is wrong i cant update with kies. I installed application called CSC select and it says my CSC is KOR. I also read that it needed to be NEE(nordic countries), to be able to update with kies. How ever CSC select application doesn't have a NEE available...
I am pretty clueless what i needed to do now, would really apperciate if someone could give me some advice. I dont need my android 4.0 to be rooted.

In the same boat
Riikka said:
Model number: GT.i9100
Android version: 2.3.4
Baseband version: I9100XXKG1
Kernel version: 2.6.35.7-i9100XXKG1-CL349526 [email protected] #2
Build number: Gingerbread.XXKG1
Click to expand...
Click to collapse
Hi, I am much in the same position as you. I am still trying to figure out my options, and will post back if I get anywhere. In the meantime, can you please post CSC etc details of your phone? You can get this by opening the dialer, and dialling
Code:
*#1234#
This is what I get; can you confirm if you have the same thing?
Code:
PDA : I9100XXKG1
PHONE : I9100XXKG1
CSC : I9100[B]O[/B]XAKG1
Build Info: Tue Jul 5 23:11:24 KST 2011
(Note that the bold letter in CSC is an uppercase letter "o", NOT numeral "0").
Do you have any idea if your phone is region-locked, region-free, unlocked, factory unlocked etc? Bought in India?
Cheers,

prshah said:
Hi, I am much in the same position as you. I am still trying to figure out my options, and will post back if I get anywhere. In the meantime, can you please post CSC etc details of your phone? You can get this by opening the dialer, and dialling
Code:
*#1234#
This is what I get; can you confirm if you have the same thing?
Code:
PDA : I9100XXKG1
PHONE : I9100XXKG1
CSC : I9100[B]O[/B]XAKG1
Build Info: Tue Jul 5 23:11:24 KST 2011
(Note that the bold letter in CSC is an uppercase letter "o", NOT numeral "0").
Do you have any idea if your phone is region-locked, region-free, unlocked, factory unlocked etc? Bought in India?
Cheers,
Click to expand...
Click to collapse
I have to same problem
I order my phone on ebay from china made in Korea

[Q] n7100 N7100XXUEMK9 no IMEI odin FAIL KNOX activated

Hi everyone,
I am tried to recuperate a Samsung note 2 GT-N7100 without efs backup and baseband, imei and network lost. KNOX is activated.
Following to "Originally Posted by dr.ketan View Post N7100XXUEMJ5 How to Root + Remove New Bootloader + KNOX Free" from "dr.ketan" I really hope that I can do it. But in the first steep I´m blocked, because when I try to flash "PDA: N7100XXUEMJ5" in the first second appears "FAIL" and the phone said "that is not compatible with this version".
To download the original rom from sammovile like dr-ketan said linking to "http://forum.xda-developers.com/showthread.php?t=2499794" of "Faryaab" and I cant find:
Model: GT-N7100
Country: Open Europe
Version: Android 4.3
Changelist: 2138564
Build date: Wed, 20 Nov 2013 19:16:05 +0000
Product Code: OXX
PDA: N7100XXUEMK9
CSC: N7100OXXEMK4
MODEM: N7100XXUEMJ9
Download: Mod Edit on links.
or
Model: GT-N7100
Country: Open Asia
Version: Android 4.3
Changelist: 1903221
Build date: Wed, 16 Oct 2013 23:49:26 +0000
Product Code: OLB
PDA: N7100XXUEMJ5
CSC: N7100OLBEMJ4
MODEM: N7100XXUEMJ5
Download:Mod Edit on links.
So I download from external webs but am not sure if it doesn’t work or is my phone´s problem.
I explain exactly all my probes that i did before this post, an actually I am really feel that I´m loose this battle, so please if anybody has an idea it´ll be great!
I beging with no IMEI, so the phone can´t take network to use it. Always that become dead the only way to recuperate it is flash via odin:
Model: GT-N7100
Model name: Galaxy Note II
Country: Spain
Version: Android 4.3
Changelist: 2138564
Build date: Wed, 20 Nov 2013 10:22:31 +0000
Product Code: PHE
PDA: N7100XXUEMK9
After that I can swicth on, but steel without IMEI and network; and of course KNOX activated.
Ok, let´s go to explain what I did before in case this can give aut some information:
1.- To recuperate the IMEI with ARIZA-Path
http://forum.xda-developers.com/galaxy-s3/help/solved-siii-network-problem-update-sn-t1918601
I obtain root access to install busy-box and ariza-patch with KNOX activated. The patch was apply correctly, but it wasn’t recuperate the IMEI
2.- To recuperate the modem or base band using different files
Here I used many post from XDA testing different modems, patch and baseband according of my PDA file in every moment. But still no work, sometimes become in CWM mode "signature fail", other via odin "PASS"; but the conclusion in every case is the same, "phone unknown, no baseband, no IMEI..."
Here I have other question, when u flash the modem, for example "XXDME4 / DXDMF1 / DDMG1" do you have to put only the correct one (DXDMF1 in my case) or all of it. I did both, just to try.
http://forum.xda-developers.com/showthread.php?t=1584250 to read and http://forum.xda-developers.com/showthread.php?t=2044937 to download modems
http://forum.xda-developers.com/showthread.php?t=2468119
3.- To recuperate the IMEI via flash Philz after that in CWM using this post http://forum.xda-developers.com/showthread.php?t=2536418
The same situation
4.- To complete flash and recovery with http://forum.xda-developers.com/showthread.php?t=2154890
I did the same operation in other S-4 and works, but here my problem is:
- The complete pack of 5 files to flash it via odin, I only found for android 4.1.2
- If I try to downgrade with KNOX active, become "FAIL"
- If I try to flash a version of android 4.3 without KNOX, appears one more time the same "FAIL"
Posible solution for that ¿¡?
- Find out a complete flash files for android 4.3 (PDA, MODEM or baseband, BOOTLOADER, CSS and in case Pit file)
- Downgrade to 4.1.2 and install OXA pack that I have it
- Restore it for SAT http://forum.xda-developers.com/showthread.php?t=2618261 with flash counter in 0
- Use KIES to restore it (I hate this possible solution) external link obviously in http://www.droidviews.com/firmware-upgrade-encountered-an-issue-solution/
Hopefully u posts it in correct place and someone can help me.
Regards to moderates people and every person who post looking for helps to others.

To Downgrade you N7100 and remove KNOX you need
1. OLD JTAG microSD card
2. Open the phone
3. Short Resistor
4. Power up the phone
5. Wait for success message
6. Assembly back
7. Flash to ANY old SW and Knox will not showed in Download Mode
Many phones checked like that

Full unroot of sm-t805 from marshmallow 6

Hi
I need advice on how to unrooted and fully restore my device to as much as factory out-of-the box state as possible.
Background: I have not been using my Tab for a while and before that I was using Iron rom 2.2.
I went straight to marshmallow 6.0 and it worked perfectly, except for camera issues, SD card issues etc. Really fast compared to previous ROM I was using.
Right now my device has not got any PDA or CSC values? according to Phone info and SamMobile device info.
*#1234# generates: connection problem or invalid MMI Code
*#06# does produce IMEI and LTE connection has been working correctly but somewhat buggy when roaming.
I think i might have missed a step or two and i should have updated to a recent bootloader before updating to marshmallow, my bootloader is from the wrong region but It matched the device and operator (austria/telenor/vodafone) by the time I flashed it for the first time (early days of smt805)
so far i have:
1. Downloaded Proper Nordic Region NEE (Sweden) region firmware from samfirm software, also downloaded the binary version just in case. It says you are suppose to make use of AP, BL, CP, CSC on newer devices? What box should i Tick?
2. Everything is backed up including EFS
3. read many threads about this topic but I am still a little bit uncertain for this particular device/scenario
device info
Code:
GENERAL INFO
Manufacturer: samsung
Brand: samsung
Phone Model: SM-T805
Device Type: chagalllte
Product Name: aosp_chagalllte
Country of Origin: MADE IN VIETNAM
Manufacturing Date: 2015.3.18
Knox Warranty Void: 0x1
Colour: White
Internal Storage:
CSC INFO
Product Code: SM-T805NZWANEE
Original CSC Code: NEE
Firmware's CSC Code:
Active CSC Code: NEE
Available CSC Codes:
CSC Country:
CSC Country ISO:
Mobile Operator: Telenor SE / 24008
FIRMWARE INFO
Bootloader Version: T805XXU1BOCC
PDA Version:
CSC Version:
Baseband Version: T805XXU1BOC1
Latest Firmware: T805XXU1BPC4/T805NEE1BPC1/T805XXU1BPC1
Kernel Version: 3.4.106-g2baa1c5-dirty [email protected] #1 32-bit
Java Virtual Machine: ART 2.1.0
OS INFO
Root Existence: Yes
Android Version: 6.0.1
Build Number: aosp_chagalllte-userdebug 6.0.1 MXC89K eng.ubuntu.20160712.204335 test-keys (eng.ubuntu.20160712.204335)
Build Fingerprint: samsung/aosp_chagalllte/chagalllte:6.0.1/MXC89K/ubuntu07122044:userdebug/test-keys
Build Description: aosp_chagalllte-userdebug 6.0.1 MXC89K eng.ubuntu.20160712.204335 test-keys
Build Date: Di 12. Jul 20:44:31 CEST 2016
Changelist:
HARDWARE INFO
Hardware: universal5420
Board: universal5420 [32-bit]
Platform: exynos5
Chip:
GPU: ARM Mali-T628
Modem Board: XMM7160
Hardware Revision: MP 0.700
Total RAM: 2.71 GB
Screen: 10.54 inches, 2560 × 1600 pixels, 286 ppi, 320 dpi
Camera:
Rear: 8MP / SONY_IMX134_FIMC_IS
Front: 2.1MP / SLSI_S5K6B2YX_FIMC_IS
Battery: Li-ion 7900 mAh, Health: Good

Everything looks correct.
Please be aware that while running AOSP MM you won't be able to readout PDA and CSC Version

If you have stock modified rom and want to up date bootloader some were id xda there is a post about just updating bootloader this will give you little to no errors with csc codes etc, etc......