UPDATE: First custom rom with Interop Unlock flashed succesfully. Requires hard reset after installing and an unlocked bootloader. See post for proof:
http://forum.xda-developers.com/showpost.php?p=24818275&postcount=242
BIG THANK YOU TO ULTRASHOT!
Without you I couldn't have done it!
NOTICE: Testing full unlock (XIP unlock etc) with ultrashot. Will post new files as soon as I get a working build which doesn't get stucked on boot
Disclaimer:
I AM NOT RESPONSIBLE IF YOU LOOSE DATA, BREAK YOUR PHONE, OR SET YOUR HOUSE ON FIRE. DO THIS AT YOUR OWN RISK. BTW, REQUIRES A HARD RESET SO YOU WILL LOOSE ALL THE DATA IN YOUR PHONE BY FLASHING THIS. IF UNSURE, DON'T DO IT.
PLEASE STOP PM'ING ME FOR HELP, I CAN'T REPLY 20 PMS/HR. Please use the forum, maybe someone can create a discussion topic to help others and leave this for links and development. Thank you very much!
PLEASE STOP SENDING ME PMS ASKING FOR HELP AND USE THE DEDICATED THREAD
THIS THREAD IS FOR DEVELOPMENT ONLY, PLEASE RESPECT THAT AND USE THE Q&A THREAD FOR YOUR QUESTIONS.
LINKS:
Lumia 800: Full Unlock
New firmware: May 16, 2012 (removed foursquare and stuff)
sdb3.rar: Flash it to PARTITION #3. It contains 12070's amss & adsp. Not absolutely required but if you have an older version this should give you better battery life.
http://www.mediafire.com/?kwjladlgvq81rha
OS-NEW:
As always, flash it to PARTITION #9.
Part1: http://www.mediafire.com/?21by2oj7acnhkhw
Part2: http://www.mediafire.com/?wkeduvp9l4199qh
Part3: http://www.mediafire.com/?cnbkms40dy4y06z
Part4: http://www.mediafire.com/?rabunpmnaqclq3o
Complete Mediafire folder access: http://www.mediafire.com/?uo2dqcl34b9cy
___________________
Alternate ROM with Full Unlock + Some apps:
Part1: http://www.mediafire.com/?8gnqm418v32im3e
Part2: http://www.mediafire.com/?bgtg2t5infrnua1
Part3: http://www.mediafire.com/?l0sl5hbr0v9gfi1
Part4: http://www.mediafire.com/?emt2dfswdhn0z0w
Apps preinstalled:
DS Supertool
File Deployer
Metro Theme
WebServer
WinTT
WM Device Center
WP7 Root Tool
___________________
Lumia 710: Interop Unlock (no full unlock yet)
ROM Based on: RM803_059N2L6_1600.3015.8107.12070_010
Mediafire folder access: http://www.mediafire.com/?9z6og65ozgrnr
http://www.mediafire.com/download.php?d3bj3dkfbffbakn
http://www.mediafire.com/download.php?l35zjaebdrsm315
http://www.mediafire.com/download.php?ys5bapu8ubezybo
http://www.mediafire.com/download.php?tnadd4uuoxhatv3
CAUTION: I don't have a 710, so these images AREN'T TESTED. Use at your own risk. Be careful, people are reporting problems with this rom.
Full Unlock Image for Lumia 710 by lucifer3006 -BE CAREFUL, IT HAS BUGS, FOR TESTING PURPOSES ONLY- (thanks ultrashot & lucifer3006): http://www.mediafire.com/?p3318y5l19abb
You have a mirror of all the stuff on mediafire on xdafil.es: http://xdafil.es
Thank you mousey_!
PLEASE DO A FULL BACKUP OF THE NAND BEFORE PLAYING AROUND.
If you are developing fixes for the bootloader 'problem', feel free to grab a copy of the rest of partitions and stuff I posted over this thread here: http://www.mediafire.com/?kknt4lnc3tn7w
INSTRUCTIONS:
Requires an unlocked bootloader (a.k.a. qualcomm development bootloader).
Easy to check: Turn the phone OFF, then press and hold VOLUME UP + POWER until you notice a short vibration. Plug in to the computer. If the phone turns up in disk mode (USB Mass Storage Device), then you have an unlocked bootloader. IF you're in Windows, it will ask if you want to format the disk. SAY NO OR IT WILL EXPLODE (it won't explode but you might break it)
If the device detected by the computer is Nokia DLOAD you have a locked bootloader and you're out of luck, at least for now.
I used 'dd' in Linux, I guess you can do it with Windows version too (http://www.chrysocome.net/dd) but it's more involved to find the appropiate partition:
dd if=./os-new.nb of=/dev/sdX9
Where X is the disk detected by your linux distribution.
After that, you'll need to hard reset the phone. Hold Power button for 10 seconds to exit Qualcomm's disk mode, and press and hold POWER+VOLUMEDOWN+CAMERA until you feel the phone vibrate. After that, RELEASE power button but KEEP HOLDING volume down + camera for five or more seconds. This will trigger the hard reset.
Now time to play with bootloaders and try to get this to work for everyone!
If you like my work and want to donate for a beer (or two), follow this link
Fantastic discovery. I am not a coder. All the best.
Can't reproduce here.
I press both volume buttons and power and I get 'Nokia DLOAD'.
If I stop holding volume buttons, it boots WP7.
The method you've described is how I do dead-mode flash. I don't see why it would show a USB disk.
awesome work mate!! having a look right now!
seems NAND cant be accessed directly form windows PC! strange! need to check more..
im getting usb input on device manager...but no drivers install!
so looks like i need the drivers.
no drivers found...now i need to goto linux.
surya skype me we'll figure this out thats a fantastic discovery mate !have a nice easter ,booom
Ooohh, ****!! I promissed myself to never install Linux... But...
xsacha said:
Can't reproduce here.
I press both volume buttons and power and I get 'Nokia DLOAD'.
If I stop holding volume buttons, it boots WP7.
The method you've described is how I do dead-mode flash. I don't see why it would show a USB disk.
Click to expand...
Click to collapse
The only other thing I did was change usb mode from Zune to Serial on diagnostics app, and tap a bit on the 4 serial ports it shows when in serial mode, but I tried and for me it still works even in zune mode.
Also, what I have is a retail phone, not a development one.. just in case:
OS version: 7.10.7720.68
Firmware rev: 1600.2475.7720.11414
SoC version: 0.74.2.1
Bootloader version: 7.35.0.0
What do you have in your phone?
Sent from my GT-I9100 using XDA
biktor_gj said:
The only other thing I did was change usb mode from Zune to Serial on diagnostics app, and tap a bit on the 4 serial ports it shows when in serial mode, but I tried and for me it still works even in zune mode.
Also, what I have is a retail phone, not a development one.. just in case:
OS version: 7.10.7720.68
Firmware rev: 1600.2475.7720.11414
SoC version: 0.74.2.1
Bootloader version: 7.35.0.0
What do you have in your phone?
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
OS version: 7.10.8107.79
Firmware rev: 1600.2483.8107.11501
SoC version: 0.74.2.1
Bootloader version: 7.35.0.0
I'm in Zune mode. I'll try this serial mode. Edit: Serial is same. I just get 'Nokia USB connectivity' instead (in Windows). Shows nothing on Linux.
Heathcliff74 said:
Ooohh, ****!! I promissed myself to never install Linux... But...
Click to expand...
Click to collapse
Maybe you can look here:
http://www.puppylinux.com/
ok guys so this is only available for 7720.11414 or lower(11412) firmware and since you have 11501 this is not available so downgrade guys and woooow !! we're almost there
Oh no, so this wotn work for 1207 firmware?
Great discovery, works great on my Lumia 710 (tried it with Ubuntu 11.10).
OS version: 7.10.8107.79
Firmware version: 1600.3015.8107.12070
Bootloader version: 7.33.0.0
Okay, I kept digging a little deeper, and this is what I know so far (if you want copies of dumps, files etc, just ask for them )
First of all... Thank you Nokia!
LUMIA 800 FLASH FILE SYSTEM LAYOUT:
Partition Begin End Blocks ID
/dev/sdb1 * 1 1000 500 4d Initial Bootloader - SECBOOT
/dev/sdb2 1001 4000 1500 46 Second stage loader? - OSBL, also looks like it has the download mode and seems to init LCD, enable USB etc.
/dev/sdb3 4001 304000 150000 c W95 FAT32 (LBA) - Writable partition with EMMCBOOT, AMSS etc.
EMMCBoot is responsible for loading Windows Kernel (nk.exe). I got a copy of Samsung Galaxy i9001's emmcboot.mbn, and putted it in there. It tries to start, but seems to crash (expected). But hey! it tries to boot it (it even vibrates for 1/10 of a second), so getting something else (did anyone say...android?)running on this phone should be easier than in lots of other phones... Does anyone have u-boot ports for Qualcomm 8255?
/dev/sdb4 304001 31037579 15366789+ 5 Extended partition which holds the OS
/dev/sdb5 304006 304133 64 ef EFI (FAT-12/16/32) - Linux detects it as an EFI partition, but it's just 64Kb size, and seems to have some markers, not sure yet what it is, but could be anything from IMEI and simlock to an actual efi partiton for WinCE...
EDIT AGAIN: this partition contains phone serial number and product code, and possibly imei and simlock. For sure its not an efi partition
/dev/sdb6 304134 310277 3072 58 3Mb size
/dev/sdb7 393216 399359 3072 4a 3Mb size
/dev/sdb8 399360 405503 3072 4b 3Mb size
These three partitions have similar start and end data on their partitions, no idea what they are, since I haven't been able to see if it's even a file system. All the documentation I see seems to tell Windows Mobile uses exFAT for the filesystem, but can't seem to find its header anywhere on the flash... still looking. It could even be where WinMo stores application installers for first boot on the device (but could be perfectly wrong)
All of them start with the following header (hex):
7D 8D 27 82 D7 40 F8 90 53 22 82 43 6D EC 6F 69 49
/dev/sdb9 524288 31156362 15316037+ 48
This las partition is 15Gb size, and contains all the Operating System and all the data on the phone.
Anyone know about how does Windows Phone manage filesystems on NAND? Some help would be really appreciated...
EDIT: A little bit more... The file system for the 15Gb partition has _wmstore header, still incompatible with some kitchens, but still looking...
Here's part of the header:
_wmstore
!zLH?k
_wmpart_B
_wmpart_S
_wmpart_S
_wmpart_N
_wmpart_U
_wmpart_D
_wmpart_I
_wmpart_P
_wmpart_U
PSBdX
GFCB
SRPX
Once we can mount this thing and inject some files we'll have interop unlock
can we flash a rom through that ?
You can dump and write back whatever you want to the flash, so if anyone finds some application to read wmstore dumps and build them back I can check it...
tl;dr: you can do custom roms and whatever you want with it,but need some app to manage it first
Sent from my GT-I9100 using XDA
this is awesome! +1 for u for this!! i am gonna install ubuntu in next 2 hrs and downgrde my lumia...since im on updated, it doesnt have options fro zune serial modes! :///
crap wer da hell was linux!! hahah
anyways...keep it up..hope to see this baby rock!
Keep it up guys!
It's one of the very few positive signs about lumia windows phone development.
surya467 said:
this is awesome! +1 for u for this!! i am gonna install ubuntu in next 2 hrs and downgrde my lumia...since im on updated, it doesnt have options fro zune serial modes! :///
crap wer da hell was linux!! hahah
anyways...keep it up..hope to see this baby rock!
Click to expand...
Click to collapse
Apparently there's no need to downgrade. beidl said he managed to get it working using 12070 firmware
ombadboy said:
Apparently there's no need to downgrade. beidl said he managed to get it working using 12070 firmware
Click to expand...
Click to collapse
but on lumia 710 man on lumia 800 diagnostic app is updated on those firmware and is lack of serial mode
cdbase said:
but on lumia 710 man on lumia 800 diagnostic app is updated on those firmware and is lack of serial mode
Click to expand...
Click to collapse
It seems it has more to do with firmware version than Serial/Zune menu availability on Diagnostics app. I haven't updated my Lumia, so I can't know for sure. Try powering down the phone and holding vol+, vol- & power. If windows detects a USB disk and tells you it's not formatted, it probably works for you (you can check it by going to Control Panel -> Administrative tools -> Computer Management -> Disk Management)
AGAIN, BE CAREFUL, YOU CAN BRICK YOUR PHONE.
Related
[DFT Freedom ROM] Mondrian mango 7720 V2 version
Updates:
20 Langs in one rom USA_ENG_FRA_ITA_GER_ESN_NLD_DAN_FIN_NOR_SVE_PTB_ PTG_RUS_ELL_HUN_CSY_PLK_JPN_KOR
Replace RUU_Mondrian_S_Cingular_US_4.03.502.00_5.69.09.05a_22.50.50_RELEASE new driver
Replace some of the new HTC XAP (from Titan ROM or Radar ROM or Market )
Open Internet sharing
Fully unlock with IE download XAP , can be immediately downloaded and install it , see picture under
XAP unlimited installation, dozens of XAP than can be installed, I installed more than 30 XAP which download from the market, fixed market XAP update/install issue from DFT Freedom 7720 version.
ROM built-in HTC Deck , Tango, TouchXplorer, Registry Editor, in the pass XAP only can be installed via computer, DFT developed DFTInstall.exe so now all the XAP can be build-into custom ROM , of course need to see will be over the size of 512, this tool is strictly prohibited any theft, unauthorized use exception.
Important Note
1. Before doing anything, make sure you have more than 50% battery!
2. You must have RSPL / HSPL installed on your device, download RSPL / HSPL see this http://www.darkforcesteam.com.cn ... & extra = page% 3D1
3. Supported Operating Systems: Windows XP, Windows Vista, Windows 7.
Disclaimer
This product is free of charge, at your own risk. We do not have any conflict, fault, or damage caused by the process of responsibility. Implied or otherwise, if you agree that any use of the product warranty. Did not find the problem, several different devices simultaneously to test this product, your experience may vary.
Products used for commercial purposes is strictly prohibited, and prohibited xda.cn & wpxap forum and reproduced with the use of intellectual ROM
For the protection of the DFT our official website and XDA - developers.com, it is not allowed within 5 days reproduced in this ROM, the column name well-known owners of this forum the forum three days after the group can reproduced without the application after five days free reproduced, reprinted, be sure to indicate the DFT produced the original post and add links
# Strongly prohibit any use made of the DFT ROM resources,
20 language versions download here
Code:
Password: 11/08/2011 @ DFT
Dark Forces Team Special thanks to TouchXplorer & Registry Editor author Julien Schapman allows us to these two software built into ROM.
Official DFT site (Chinese)
DarkForcesTeam Nov,2011
http://www.youtube.com/watch?v=KyTniK4AXUE&feature=channel_video_title
invalid password
Thanks a lot. I'll test.
@agushaha: have a space before 11/08/2011 @ DFT.
my current OS version is 7.10.7720.68
my device is an at&t surround
can I install this on my device? i have not yet installed hspl / rspl.
i cant open the file....
do you lnow why?????
nacho685 said:
i cant open the file....
do you lnow why?????
Click to expand...
Click to collapse
Chances are that you put the password in incorrectly
Thank's it's work
bmamo said:
my current OS version is 7.10.7720.68
my device is an at&t surround
can I install this on my device? i have not yet installed hspl / rspl.
Click to expand...
Click to collapse
I also would like to try this. Is there a tutorial on how to get this installed??. Got the same OS version.
Thxs
hi guys,
I can't unzip. I have the latest winrar. I tried the password with and without the first space...
space before but no space between then.
perfect!
password is:
" 11/08/[email protected]" (without the ")
thanks
Advanced Config Not Working
Not sure if its a bug but it appears advanced config does not work with this rom.
I miss my custom grey theme already
NVM Reboot fixed it
My attempt at a tutorial
jesusodin said:
I also would like to try this. Is there a tutorial on how to get this installed??. Got the same OS version.
Thxs
Click to expand...
Click to collapse
Here is my attempt at a tutorial
Step 1: take anything important off your phone (Pictures Videos Music Etc) Because installing all this stuff will erase your phone completely
Step 2: Go and read the first post in this thread
http://forum.xda-developers.com/showthread.php?t=1195647
Once you have read it, READ IT AGAIN!, because if you flash that to your phone and its not compatible you will BRICK YOUR PHONE.
Once you are sure that your phone is compatible with the RSPL/HSPL download it and use the included tools to flash it to your phone. You will need to put your phone in bootloader mode to install that. To do this you will turn the phone off completely then press power + the volume down button to get to your boot loader screen it will be red green blue and white.
Connect your phone start the RSPL app and follow the steps to the letter, once this is down download the rom posted in this thread.
Step 3: Flash the rom posted in this thread by using the same steps. Power off the phone, then press power + volume down button when you see the bootloader start the flashing process. You will get a progress bar let it go through until the phone reboots.
Step 4: Enjoy a truly amazing rom on your Surrond, thank you so much DFT.
HTC update?
Got this "update" last night, does anybody know what it does???
Don't update. Your phone will become a brick if you update.
I tested. There are a few minor bugs eg: Errors column waves 3G,misspelled in the About
Model: HTC Mondrian
Carrier: HTC Sunnound T8788
Thank so much.
hello
When you unzip the file gives error unknown format or damaged
regards
rob243 said:
Here is my attempt at a tutorial
Step 1: take anything important off your phone (Pictures Videos Music Etc) Because installing all this stuff will erase your phone completely
Step 2: Go and read the first post in this thread
http://forum.xda-developers.com/showthread.php?t=1195647
Once you have read it, READ IT AGAIN!, because if you flash that to your phone and its not compatible you will BRICK YOUR PHONE.
Once you are sure that your phone is compatible with the RSPL/HSPL download it and use the included tools to flash it to your phone. You will need to put your phone in bootloader mode to install that. To do this you will turn the phone off completely then press power + the volume down button to get to your boot loader screen it will be red green blue and white.
Connect your phone start the RSPL app and follow the steps to the letter, once this is down download the rom posted in this thread.
Step 3: Flash the rom posted in this thread by using the same steps. Power off the phone, then press power + volume down button when you see the bootloader start the flashing process. You will get a progress bar let it go through until the phone reboots.
Step 4: Enjoy a truly amazing rom on your Surrond, thank you so much DFT.
Click to expand...
Click to collapse
that thread says this:
WARNING TO ALL:
Do NOT use RSPL / HSPL with Mozart 4.XX and other RUU ROMS with MANGO.
All WP7F devices affected: MOZART, GOLD, SCHUBERT, MONDRIAN, SPARK!
It will damage your device. Not a joke.
MORE INFORMATION HERE
--------
I have mango. therefore i understand i cannot change the rom am i right?
on the 3 colour screen i get the following:
PD26100 SS-BC (4K)
SPL-4.3.2250.0(128976) MNG
MicroP(LED) 0x09
TOUCH C1(v69)
Am I stuck on Mango?
Downgrade????
this is correct do not use the rspl/hspl if the numbers for the versions do not match
I had originally installed mango using the disconnect trick what I needed to do to install this was use the stock rom for my phone/provider to downgrade first for me it was Telus my provider, I found the rom here to put me back to pre-nodo like the phone was fresh out of the box.
THEN I was able to do the rspl/hspl then the DFT rom.
Also check under your battery for the model ID and verify its compatible with those posted in the RSPL/HSPL thread the model ID on my phone is PD26110 I can confirm with a pre-nodo rom and that model ID the rspl/hspl and the dft rom work perfectly
hello
someone upload the rom to another server and that gives me this error or damaged
regards
Dear friend
here you have a little a quick guide that will give you an unlocked free Lumia 800. This guide is working also for Lumia 710, maybe on all version.
What do you need
NSS Pro 0.48 (last version Today)
The NB file you choose to flash between the custom roms you can find here in XDA ( I suggest to take This One - Unlocked and based on 12070 )
a Lumia 800, the Qualcomm One
Preparing..
First of all you need to check if your Lumia is the Qualcomm One. You can simply understand this: in installation driver, putting the phone in OSBL mode, by pressing the VOL UP for more than 8 seconds, you'll have QUALCOMM CDMA Technologies, your phone is Qualcomm. If you'll get NOKIA DLOAD, your phone is not qualcomm
Second of all, install correct qualcomm drivers, the best way is to follow the Qualcomm Drivers Tutorial, here in XDA
Third of all, check battery, you need minimum 50%
How TO
Open NSS PRO
Go To Flashing - WP 7 Tools
Power on Phone normally
Let Windows Find your phone with correct drivers
On Bottom - Left choose Nokia Connectivity
Click On DETECT
Where Software say "Normal Mode", click on OSBL Mode e give a click on the arrow
Now click on "OS File" and choose the NB file you want to flash
Click on Write OS
All Done - Good Work Boss
n.b.= Italian People can Contact me for italian tutorial
Utenti italiani, contattatemi in caso di problemi
Dengel said:
Dear friend
here you have a little a quick guide that will give you an unlocked free Lumia 800. This guide is working also for Lumia 710, maybe on all version.
What do you need
NSS Pro 0.48 (last version Today)
The NB file you choose to flash between the custom roms you can find here in XDA
a Lumia 800, the Qualcomm One
Preparing..
First of all you need to check if your Lumia is the Qualcomm One. You can simply understand this: in installation driver, putting the phone in OSBL mode, by pressing the VOL UP for more than 8 seconds, you'll have QUALCOMM CDMA Technologies, your phone is Qualcomm. If you'll get NOKIA DLOAD, your phone is not qualcomm
Second of all, install correct qualcomm drivers, the best way is to follow the Qualcomm Drivers Tutorial, here in XDA
Third of all, check battery, you need minimum 50%
How TO
Open NSS PRO
Go To Flashing - WP 7 Tools
Power on Phone normally
Let Windows Find your phone with correct drivers
On Bottom - Left choose Nokia Connectivity
Click On DETECT
Where Software say "Normal Mode", click on OSBL Mode e give a click on the arrow
Now click on "OS File" and choose the NB file you want to flash
Click on Write OS
All Done - Good Work Boss
n.b.= Italian People can Contact me for italian tutorial
Click to expand...
Click to collapse
Nice guide, you should add a line for people with DLOAD bootloaders on how to flash the QC one
Also this line
Italian People can Contact me for italian tutorial
You might want to write that line in Italian
Perhaps it is a good idea to include some links to more 'how to's' in the openings post, e.g. I can't find how to go to the installation drivers. Yep, I'm new to WP
Koen87 said:
Perhaps it is a good idea to include some links to more 'how to's' in the openings post, e.g. I can't find how to go to the installation drivers. Yep, I'm new to WP
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1669498
Thanks for the info.
ps; as usual, it doesn't work on os x?
Here you have a little installer to Force installation of correct drivers for Nokia Lumia Qualcomm Based.
The software will include in OEM driver, the ones for our beatiful phone
Here we go...
Download The package Qualcomm Driver Installer For Nokia Lumia
Unrar it on your desktop
Click on the qcusbtest.cer and install it, choosing Root Authorization, and Trusted Authors ( don't know if is the correct translation, because my OS is in italian )
Then Run the driver Installer with Administrator Right ( right click on the software, Run as Administrator )
All Done
Dengel said:
Preparing..
First of all you need to check if your Lumia is the Qualcomm One. You can simply understand this: in installation driver, putting the phone in OSBL mode, by pressing the VOL UP for more than 8 seconds, you'll have QUALCOMM CDMA Technologies, your phone is Qualcomm. If you'll get NOKIA DLOAD, your phone is not qualcomm
Click to expand...
Click to collapse
As usual, yu will have to make it clear... simply pressing Vol+ for more than 8 secs does nothing... (even after 60 secs)
Once for good, make sure about how doing it really... and correct it in your post...
Might be nice if you could actually include how you downgrade to Qualcomm bootloader on the Lumia 710.
I've followed the instructions on the other post on how to downgrade the bootloader but for some reason it doesn't seem to work.
uploaded sucks =/
What can i do, if i get the NOKIA DLOAD message? Is there any solution out there?
capsob said:
What can i do, if i get the NOKIA DLOAD message? Is there any solution out there?
Click to expand...
Click to collapse
Same here. I also want to know how I can unbrand and unlock without a Qualcomm device. Please assist. thanks!
bootloader is not flashable, till now, on lumia 800.
In lumia 710 is possible, using NSS with special loaders.
help pleasee don't work for me! Cant acces to download mode!
HELP in NSS I don't have nokia connectivity! How to fix?
---------- Post added at 07:17 AM ---------- Previous post was at 07:06 AM ----------
Help pleaseeeeeeeee
Did the drivers install correctly?
Deeco7 said:
Did the drivers install correctly?
Click to expand...
Click to collapse
Now yess but NO DRIVER for qualcomm! I've try really ALL! Nothing win seven 64 bit DON't RECOGNIZE it! Uffffff help pleaseee can't flash custom rom!
first of all i would like to thank you for your useful post,i managed to recover my nokia 800 that was frozen on the nokia screen,now im getting into the menu and all the other functions nicely but it acts up or freezes most of the time when i lock the screen and i try to slide-to-unlock then it hangs,might it be the issue of the custom NB file? please helppp
do i have to fallow same steps for lumia 710?
Sensiz Olmaz GALATASARAY!!
Will this unlock will remove my phone warranty?
Can I flash - Lumia 800 12.070 with apps - Dengel Share.rar - in lumia 710 or I need lumia 710 custom flash ?
Hi,
It's possible to unlock this lumia with this soft?
OS. 7.10.8773.98
SW. 1750.0805.8773.12220
Hardware version: 112.1402.2.3
Bootloader is Qualcomm
Thanks for answer,
Sorry for my english
Sorry,it's not possible,you have to look for hwrev 2.3,a very early firmware 1600.xxxxx and an unbranded phone in most cases.
mioduch_22 said:
Bootloader is Qualcomm
Click to expand...
Click to collapse
With a Qualcomm bootloader you can access the NAND and copy an unlocked ROM to it. So yes, if you have a Qualcomm b/l it is possible.
ChrisKringel said:
With a Qualcomm bootloader you can access the NAND and copy an unlocked ROM to it. So yes, if you have a Qualcomm b/l it is possible.
Click to expand...
Click to collapse
Could You tell me step by step ?
Maybe some files ?
Sorry but I'm really don't know how ro make it .
Thank You.
yes u can unlock with 2.3
flash the qualcomm firmware and den any custom ROM
surya467 said:
yes u can unlock with 2.3
flash the qualcomm firmware and den any custom ROM
Click to expand...
Click to collapse
but how flash it with qualcomm firmware ?
please help !
give some solution
Phone details:
-----------------
NCSD Version: 1.9
SW Version: 1750.0805.8773.12220
HW Version: 112.1402.2.3
IMEI: ***************
Product Code: 059M0C7
Basic Product Code: 059J2N6
Module Code: 0205051
Production SN: 001******
Public ID: 02C446C562A4D648************
WLAN MAC: 14*****************
Battery life: 59%
Number of Nams: 1
Number of Mins: 2
ESN: 00000000
ESN Decoded: 0
PRL Version: 65535
Battery Charge Capacity: 1342mA
Battery Full Capacity: 1374mA
Battery Cycle Count: 65535
Battery Temperature: 358
Battery Voltage: 3970mV
Battery State of Charge: 59%
Battery Average Current: 194mA
Battery Flags: 296
Battery Standby Current: -5mA
Battery MaxLoad Current: -865mA
Battery Health State: 857
Battery Nominal Capacity: 819mA
Battery Remaining Capacity: 787mA
Please tell me how can I make it
please.
lumiaunlock
when you say unlock is it sim unlock or unlock the software for sideloading apps
both require the qualcomm bootloader but your phone needs to have the first version where it comes up as a flash disc, if it doesnt come up as a flash disc you have a locked bootloader regardless if its qualcomm or not.
rob :good:
It's like this,
When I connect lumia 800 to PC with usb (vol up + power) I see removable disk qualcomm msm drvice and question - format disk or cancel, I know better not format it.
My question is how to full unlock my device ( no simunlock but softwere unlock) ?
Phone details:
-----------------
NCSD Version: 1.9
SW Version: 1750.0805.8773.12220
HW Version: 112.1402.2.3
IMEI: ***************
Product Code: 059M0C7
Basic Product Code: 059J2N6
Module Code: 0205051
Production SN: 001******
Public ID: 02C446C562A4D648************
WLAN MAC: 14*****************
Battery life: 59%
Number of Nams: 1
Number of Mins: 2
ESN: 00000000
ESN Decoded: 0
PRL Version: 65535
Battery Charge Capacity: 1342mA
Battery Full Capacity: 1374mA
Battery Cycle Count: 65535
Battery Temperature: 358
Battery Voltage: 3970mV
Battery State of Charge: 59%
Battery Average Current: 194mA
Battery Flags: 296
Battery Standby Current: -5mA
Battery MaxLoad Current: -865mA
Battery Health State: 857
Battery Nominal Capacity: 819mA
Battery Remaining Capacity: 787mA
lumia unlock
right if your seeing the flash disc this is excellent news means you can flash a custom rom,
the way i done it was to install nokia care suite first of all and qualcomm drivers which you can find here, that was what i done to get mss pro to dectect the phone.
http://forum.xda-developers.com/showthread.php?t=1669498
if you want to run a custom rom it will require you to download and boot up ubuntu linux, i used a live cd on my macbook which means i didnt have to install it
or mess my system up.
head over to the dev section and download rainbowmod its a pretty sweet rom i use it on both my lumia 800s.
you can get away with just "dd" the sdb3 parttion in linux then use nss in windows to flash the rom its self. i flashed the sdb3 in linux then used nss in window to flash version 1.3 and 1.4 with no problems
once you have the custom rom installed you can slap your phone into flash mode vol+ and power load up mss 5.0 and remove your sim unlock
http://forum.xda-developers.com/showthread.php?t=1778454
if you need help with the flashing in linux ill give ya some pointers if ya need it
rob:good:
Reflexdarky said:
if you need help with the flashing in linux ill give ya some pointers if ya need it
rob:good:
Click to expand...
Click to collapse
yes please give me instructions on Linux ubuntu, and i have one more question what It is "dd" ?
Thank You my friend
Regards !
lumia flash
okie dd stand for a form of low level copying, it basically copies a file to a disc
right you first need to download ubuntu i used the latest version and burned it to a disc, a good idea would be to download the sdb3 files from the rainbow mod section and slap them on a usb disc it will save faffing about in ubuntu
once ubuntu is booted to the desktop you will need to extract the sbd3 file with archiver double click it and drag it to your desktop.
next put your lumia into flash mode then plug it in to the pc with ubuntu running
it will detect it and mount the sdb3 partition as fat ignore this
right now open a terminal prompt
and type umount /dev/sdb3
thats the partition your going to flash unmounted
now for the flashing part you should have a file called amssadsp.img this is the one you got from the rainbowmod thread and is on your desktop
now in the terminal type the part where (****) drag and drop the file on your desktop in to the terminal and type the rest thats what i done.
dd if=(********) of=/dev/sdb3
once that is done your set to flash the main rom
follow this thread and it will set ya ready for running a custom rom flash with mss pro in windows and its job done
http://forum.xda-developers.com/showthread.php?t=1683449
rob:good:
Reflexdarky said:
okie dd stand for a form of low level copying, it basically copies a file to a disc
right you first need to download ubuntu i used the latest version and burned it to a disc, a good idea would be to download the sdb3 files from the rainbow mod section and slap them on a usb disc it will save faffing about in ubuntu
once ubuntu is booted to the desktop you will need to extract the sbd3 file with archiver double click it and drag it to your desktop.
next put your lumia into flash mode then plug it in to the pc with ubuntu running
it will detect it and mount the sdb3 partition as fat ignore this
right now open a terminal prompt
and type umount /dev/sdb3
thats the partition your going to flash unmounted
now for the flashing part you should have a file called amssadsp.img this is the one you got from the rainbowmod thread and is on your desktop
now in the terminal type the part where (****) drag and drop the file on your desktop in to the terminal and type the rest thats what i done.
dd if=(********) of=/dev/sdb3
once that is done your set to flash the main rom
follow this thread and it will set ya ready for running a custom rom flash with mss pro in windows and its job done
http://forum.xda-developers.com/showthread.php?t=1683449
rob:good:
Click to expand...
Click to collapse
Everything iy's done !!!
THANK YOU MY FRIEND !!!
I am new in case of Windows Phone flashing and all ...
Basically i want custom windows phone 7.8 on my phone (like this one - http://forum.xda-developers.com/show...0352&nocache=1 ) and i don't know the procedure to do the same. I read all the forums on XDA Developers but i seriously got confused about what to actually do with my phone...
I would be really thankful if anybody guides me through all the steps involved in flashing custom ROM by some RSPL/HSPL method ... Also do I need to downgrade anything ??? If yes HOW??/
I have given all the information about my current state of phone
PLEASE HELP !!!! PLEASE HELP!!!!! PLEASE HELP!!!!!!
PHONE INFORMATION :
Name: HTC 7 Mozart T8698
Model: HTC 7 Mozart T8698
Software: Windows Phone 7.5
Total Storage: 7.20 GB
Available Storage: 1.67 GB
OS Version: 7.10.8773.98
Firmware revision number: 2250.21.51205.707
Hardware revision number: 0004
Radio software version: 5.69.09.05a_22.50.50.21U
Radio hardware version: A.102.0.D4
Bootloader version: 5.12.2250.5(139188)
Chip SOC version: 2.2.5.0
MAC address: F8-DB-7F-86-89-79
SIM ID: 89910704910009427355
INFORMATION DISPLAYED when switching on the phone with volume down button :
IN RED _________
PD67100 SS-BC (4K)
SPL-5.12.2250.5(139188) MNG
MicroP(LED) 0*07
TOUCH C1(v69)
IN GREEN_________
SD SANDISK 7580MB
Partition Info-v211v413
IN BLUE______________
IN WHITE_____________
Serial
General INFORMATION:
COUNTRY: INDIA ( So i guess my phone is not SIM locked i think it is called unbranded )
Hi i was new to all this and installed dynamics v2.0 fully unlocked rom the other day and this is how i went about it
download this
http://mediafire.com/?3p9p97ta84bjym2
password - verynuclear
this is a load your phone back to 1.24
to install it i did this
turn phone off hold down volume down and turn phone on you should go to the bootloader screen then plug in your usb cable to the pc,
then on the white line at the bottom on phone screen should say usb instead of serial but maybe it will need to install some drivers cant remember 100%
when it is ready open that file and click the RomUpdateUtility.exe and follow the steps in that then you will have your phone back to 1.24
next you can follow this post here and download the attachment at the bottom named DFT_XSPL_WP7FG1.rar this what u need for this step
http://forum.xda-developers.com/showthread.php?t=1195647
basically this is the install procedure u may need to install active sync (XP) or windows mobile device center (vista and 7) but i did not have to my phone automatically did this
DFT_RSPL_WP7FG1_LAUNCH allows you to load RSPL on the device:
1. Extract ALL files from RAR archive.
2. Run DFT_RSPL_WP7FG1_LAUNCH (with administrative rights to access USB)
3. Mindfully reads information text. Press “Next” button.
4. Reset your device and hold “Volume Down” button during reset to enter OSPL mode.
5. Connect your device to PC via USB cable.
6. Now you may need to install proper USB drivers. They come with Active Sync / Windows Mobile Device Center.
7. Install drivers if required.
8. Make sure device show “USB” at the bottom instead of “Serial”.
9. Press “Next” button in the wizard. It should detect your phone.
10. If you are using WCEUSBHS driver under Windows Vista/7 (for MTTY or MAGLDR TTY for example), you should apply “Windows XP compatible mode” in the properties of EXE file to get connection.
11. After successful connection it should show device codename and allows to choose installed OSPL version.
12. You should look at the screen and select OSPL version in drop down list box. You need do this because it’s not possible to detect installed version via USB.
If your current SPL version doesn't present in the list, you can choose nearest version,
BUT ONLY IF IT HAS SAME FIRST NUMBER!!
Example: You have 4.XX on the device. Do NOT choose 1.XX 2.XX 3.XX.
13. Press “Next”. Wait until comes final page.
14. Read and close window
15. Look at the device – it must reboot to RSPL.
16. If you see RSPLX.Y.Z and “CotullaRSPL” on the screen – the task done! Otherwise, please report in this thread about your problems.
17. Put some feedback in this thread for community and developers.
Installing HSPL
DFT_HSPL_WP7FG1_INSTALL allows you to install HSPL on the device:
1. Launch RSPL on the device like described above.
2. Be sure that you close RSPL wizard window.
3. Run DFT_HSPL_WP7FG1_INSTALL.exe (with administrative rights to access USB)
4. Mindfully reads information text. Press “Next” button.
5. Proper drivers already must be installed in RSPL step.
6. Press “Next” button in the wizard. It should detect your phone.
7. If you are using WCEUSBHS driver under Windows Vista/7 (for MTTY or MAGLDR TTY for example), you should apply “Windows XP compatible mode” in the properties of EXE file to get connection.
8. After successful connection it should show device codename and allows to choose HSPL or OSPL version to install. OSPL means you install stock SPL back.
9. Check device codename, if something wrong turn off computer and run to the nearest forest. Grab some water with yourself.
10. Press “Next”. Wait until comes final page.
11. Device will reboot and start to boot OS.
12. Reset it and enter SPL mode again. Be sure there HSPLX.Y.Z and “CotullaHSPL” appear.
13. Put some feedback in this thread for community and developers.
Now u are ready
you can find what custom rom you want i used dynamics v2.0 which can be found here and its fully unlocked aswell so all i all im pleased with it
http://forum.xda-developers.com/showthread.php?t=1520352
download it and install the same way we installed the 1.24 rom in the begining of this post
i hope this helps i just answered here coz no1 else has and i did the same a few days ago all on my own after much much reading haha
good luck report back
beany2009 said:
Hi i was new to all this and installed dynamics v2.0 fully unlocked rom the other day and this is how i went about it
Click to expand...
Click to collapse
Great guide, dude - this was exactly how I did mine too.:good::good:
Base on his firmware .707 he won't be able to use ansar orange Rom to downgrade his bootloader, has to use the Y cable to downgrade.
are you sure mate from looking at his OS version and firmware he has been updating in zune obviously and looks upto date the same as what i did and worked ok for me
i didnt check my firmware before hand tho just went about it and installed everythign
---------- Post added at 10:33 AM ---------- Previous post was at 10:20 AM ----------
Girthmeister said:
Great guide, dude - this was exactly how I did mine too.:good::good:
Click to expand...
Click to collapse
cheers pal
ah never mind lol i have .401
Mirror broken
beany2009 said:
download this
<LINK>
Click to expand...
Click to collapse
Do you have another mirror? This one has been exceeded its download count because of encryption.
Give me 30 mins ill upload it to zippyshare
---------- Post added at 03:05 PM ---------- Previous post was at 02:22 PM ----------
you can follow the new tutorial here good luck
http://forum.xda-developers.com/showthread.php?t=2200702
Please Help me to install RSPL/HSPL on my htc 7 mozart
I am not able to install Rspl to my phone.
After follow all steps in ( DFT_RSPL_WP7FG1_LAUNCH ) it says successfully change Spl to Rspl but there's all same.
and not change to Rspl.
Please Guide my.
PHONE INFORMATION :
Name: HTC 7 Mozart
Model: HTC 7 Mozart
Software: Windows Phone 7
Total Storage: 7.20 GB
Available Storage: 5.58 GB
OS Version: 7.0.7004.0
Firmware revision number: 2250.09.12210.061
Hardware revision number: 0004
Radio software version: 5.50.09.18_22.24.50.09U
Radio hardware version: A.102.0.D4
Bootloader version:1.22.2250.10(110809)40
Chip SOC version: 2.2.5.0
MAC address: F8-DB-7F-86-89-79
SIM ID: 89910704910009427355
INFORMATION DISPLAYED when switching on the phone with volume down button :
IN RED _________
PD67*** MFG SS-BC (4K)
SPL-1.22.2250.10(110809)
MicroP(LED) 0X07
TOUCH C1(v69)
IN GREEN_________
SD SANDISK 7580MB CLASS0
Partition Info-v211v413
IN BLUE______________
IN WHITE_____________
Serial
yesterday when i tried to update the radio on my dinc4g (including rcdata=radio_data and rpm=radio-powermanagement, but somehow i thought it should be okay to also include boot.img (as this is reversible by TWRP recovery and tz=trusted_zone!!) ... before i compared to similar (but supposedly reversible!! partial firmware updates with their matching firmware downgrades ... all only suggested to remove at least hboot.img and stock-recovery if included) ... there was no new hboot in the new 2014 OTA firmware and stock-recovery (along with the 2ndary bootloaders) i had removed
everything also flashed just fine, no write failed, just all "OK / OKAY" and done, BUT ... after fastboot reboot ... the phone didn't come up anymore and is now STUCK on "QHSUSB_DLOAD" mode => bricked! damn ...
unfortunately the "regular" HTC unbrick tools do not support the Dinc4G ... now i'm hunting for solutions to recover my daily driver >.> already searched xda and elsewhere: tried at least brick-detect from HTC unbrick tools, but they are mainly looking if linux registers the "qhsusb_dload" _and_ adds the partitions of the phone to the running linux ... but mine only registers the serial-usb terminal from qhsusb_dload, but _not_ the phones partition(s) >_>
only thing i found is that the qualcomm QPST (oem preprogramming!) tool sees this device (albeit as said in download-mode only) and offers to flash certain things, but i do not have a QPST backup-file for the Dinc4G to compare to and/or use that to revive my phone.
i'm therefore looking for someone with a working (and at best similarly S-OFF'ed dinc4g phone to create such a QPST backup.
any help is highly welcome
further hunting the web and lots of reading here on XDA (for similarly bricked mobiles ... from almost every manufacturer!) ... the easiest (albeit not always working) idea comes down to the following:
getting a direct dump from the eMMC memory of a running/working system in a known good state:
Is anyone willing to dump the partition table/bootloader part from their working Dinc4G with FW 2.17.605.2 (the regular ICS4.0.4 without the most current 2014 OTA) for me?... best would be from an S-OFF device like mine i assume, just to make sure it matches my situation, but S-ON should also work, as it's just for recovery-boot via microSD (if it work's on a Dinc4G)
in a busybox or other terminal as root (aka: su mode)
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1048576 count=256
this will dump the first 128MB of your own eMMC (internal memory) including your current and working partition table and some of the boot partitions
then just zip that "backup.bin" (which should greatly reduce its size!) ... uploaded it somewhere and forward me the link ...
thanks for your help!!! :fingers-crossed:
thanks to j13smiley, who provided me with a eMMC dump from his Dinc4G ... i couldn't get my bricked fireball so far to failsafe-boot from the microSD with the dump he send me:
but I was able to reconstruct the filesystem-structure quite somewhat further than mdmower here http://forum.xda-developers.com/showthread.php?t=2077608&page=7 with the descriptive help from this thread http://forum.xda-developers.com/showthread.php?t=1959445 using the HOXL as a template for partition types on HTC devices
here is what i've come up with so far (analysing the /dev/mmcblk0 dump from j13smiley:
Code:
omitting empty partition (33)
Partition 33 is deleted
Disk /dev/mmcblk0: 15.9 GB, 15931539456 bytes =!size is wrong, due to using a 16GB uSD to dump the backup!=
1 heads, 16 sectors/track, 1944768 cylinders, total 31116288 sectors =!same as above!=
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System QCname
/dev/mmcblk0p1 * 1 256 128 4d QNX4.x SBL1(cfg_data)
/dev/mmcblk0p2 257 768 256 51 OnTrack DM6 Aux1 SBL2
/dev/mmcblk0p3 769 262110 130671 5d Unknown
/dev/mmcblk0p4 262111 15269886 7503888 5 Extended EXT
/dev/mmcblk0p5 262112 262143 16 5a Unknown (CID+IMEI)
/dev/mmcblk0p6 262145 262656 256 73 Unknown
/dev/mmcblk0p7 262658 293812 15577+ 5b Unknown
/dev/mmcblk0p8 293814 294325 256 5c Priam Edisk
/dev/mmcblk0p9 294327 296374 1024 45 Unknown SBL3(qscbl)
/dev/mmcblk0p10 296376 296887 256 47 Unknown RPM(appsbl)
/dev/mmcblk0p11 296889 300984 2048 46 Unknown TZ(oemsbl)
/dev/mmcblk0p12 300986 303033 1024 4c Unknown HBOOT(aboot/fota)
/dev/mmcblk0p13 303035 303098 32 0 Empty
/dev/mmcblk0p14 303100 315387 6144 34 Unknown SPLASH
/dev/mmcblk0p15 315389 317436 1024 36 Unknown
/dev/mmcblk0p16 317438 319485 1024 0 Empty (dsps)
/dev/mmcblk0p17 319487 411646 46080 77 Unknown (radio)
/dev/mmcblk0p18 411648 432127 10240 7a Unknown (adsp/q6)
/dev/mmcblk0p19 432129 442368 5120 0 Empty (wcnss)
/dev/mmcblk0p20 442370 458750 8190+ 74 Unknown (radio_config)
/dev/mmcblk0p21 458752 491519 16384 48 Unknown BOOT(apps)
/dev/mmcblk0p22 491521 524287 16383+ 71 Unknown (recovery)
/dev/mmcblk0p23 524289 526333 1022+ 76 Unknown (misc)
/dev/mmcblk0p24 526335 534526 4096 4a Unknown MODEMST1
/dev/mmcblk0p25 534528 542719 4096 4b Unknown MODEMST2
/dev/mmcblk0p26 542721 583680 20480 19 Unknown (devlog)
/dev/mmcblk0p27 583682 583689 4 0 Empty
/dev/mmcblk0p28 583691 584202 256 23 Unknown (pdata)
/dev/mmcblk0p29 584204 584235 16 0 Empty
/dev/mmcblk0p30 584237 586797 1280+ 0 Empty (local)
/dev/mmcblk0p31 586799 586926 64 0 Empty
/dev/mmcblk0p32 586928 786431 99752 0 Empty =!possibly wrong start/end&blocks!=
/dev/mmcblk0p33 83 EXT4 (system)
/dev/mmcblk0p34 83 EXT4 (cache)
/dev/mmcblk0p35 83 EXT4 (userdata)
/dev/mmcblk0p36 c FAT32(LBA) (fat)
not fully complete yet, but still much further improved over the previous partition layout details
Anything I can do to help?
I have qdload.pl, a MPRG8960.hex and 8960_msimage.mbn from some XDA thread or other (they don't seem to work though). My fireball is functional, rooted but S-ON (I got it early and htcdev still allowed me to unlock the bootloader). It does have the OTA update though.
I'm interested because my wife's fireball is stuck in QDL mode. She's migrated to a Rezound so it's not urgent.
I suspect it got that way because I used DirtyRacun S-OFF, then went to flash the OTA update. I suspect DR modifies hboot or one of the sbl's, and when I flashed the OTA it might have put me back S-ON.
(Got motivated to try to root her phone because even though it wasn't rooted, it kept trying and failing to download the OTA, killing the battery).
The DR website has an RUU.zip that has images of all the sbl's and an hboot, so working images isn't a problem, but getting them on there is.
mutterc said:
I have qdload.pl, a MPRG8960.hex and 8960_msimage.mbn from some XDA thread or other (they don't seem to work though). My fireball is functional, rooted but S-ON (I got it early and htcdev still allowed me to unlock the bootloader). It does have the OTA update though.
Click to expand...
Click to collapse
if you don't mind: plz attach your MPRG8960.hex and 8960_msimage.mbn files here ... so i could compare against those i have.
and well, if you are still S-ON _and_ the OTA-2014 is already applied then you are "out of luck" ... at least for the next couple of weeks or even months. no S-OFF method known for OTA-2014 applied fireballs!
I suspect it got that way because I used DirtyRacun S-OFF, then went to flash the OTA update. I suspect DR modifies hboot or one of the sbl's, and when I flashed the OTA it might have put me back S-ON.
Click to expand...
Click to collapse
afaik: DR "only" uses security holes in the firmware from 2.17.605.2 (from regular ICS4.0.4 RUU) to remove S-ON/write S-OFF flag ... and then add the engineering hboot of fireball (albeit modified) ... in the general section, several users with S-OFF (before the OTA-2014!) applied now the firmware from the OTA-2014 separately and confirmed that S-OFF stayed even after the OTA and since it doesn't include any new hboot, they still have their previous one
likewise, there are different qhsusb_dload modes, depending on WHEN they kicked in... in the sense of which stage fails (attaching your qdload-fireball to a linux system, there are at least 2 distinct possibilities: a) only qdload-mode or b) qdload-mode AND enumerating partitions ... the latter one is fairly easy to cure whereas the former (like mine) is much harder to come by unfortunately >_<
The DR website has an RUU.zip that has images of all the sbl's and an hboot, so working images isn't a problem, but getting them on there is.
Click to expand...
Click to collapse
they have a RUU.zip (for 2.17.605.2) and it has the firmware bit isolated and included, but that _won't help you at all_ with a bricked phone as you need a predefined partition-layout and -structure files _and_ then manage to get your brick to accept and all load those start-up settings at once. the RUU has only the files, but _not_ their structure!
i managed to already recreate most of the partition-structure of a fireball with the help from some other xda-members, but _still_ that wasn't enough for those software-tools i tried!! maybe my MPRG8960.hex isn't correct (193.692byte / md5sum: 2534fd61ebc7c8bdd9fe0dbb90c77fb0) ... i decided to buy another 2nd-hand fireball (hopefully it should still come W/O the OTA-2014 ) ... to create/dump what is on there to resurrect my bricked fireball, yet even that is still unclear if it will work. (need to wait a few more weeks until the other fireball arrives here: intl shipping & customs take quite a while unfortunately)
kimba.
first thanks for your help with the ota foirmare in theother tread. second HOW CAN I HELP YOU.
although I am on cm11 and have the firmware updated I think that is where you want to get to.
i am reasonable good with unix and adb with directions I am sure I can get anything you need off of my phone. let me know.
kimba99 said:
if you don't mind: plz attach your MPRG8960.hex and 8960_msimage.mbn files here ... so i could compare against those i have.
likewise, there are different qhsusb_dload modes, depending on WHEN they kicked in... in the sense of which stage fails (attaching your qdload-fireball to a linux system, there are at least 2 distinct possibilities: a) only qdload-mode or b) qdload-mode AND enumerating partitions ... the latter one is fairly easy to cure whereas the former (like mine) is much harder to come by unfortunately >_<
[/i]
Click to expand...
Click to collapse
Attached as tar.gz, looks like from your size/md5sums that my MPRG8960.hex is the same.
Mine has only one device (qcserial) showing up in lsusb, which means it's not enumerating partitions, right? Which if I'm still S-OFF means one of the SBLs is scrod, right?
mutterc said:
Attached as tar.gz, looks like from your size/md5sums that my MPRG8960.hex is the same.
Mine has only one device (qcserial) showing up in lsusb, which means it's not enumerating partitions, right? Which if I'm still S-OFF means one of the SBLs is scrod, right?
Click to expand...
Click to collapse
don't just check lsusb ... try the output of
Code:
dmesg | tail
BEFORE ... you attach the bricked fireball to your linux system & then right after attaching (about 10sec later or so should be enough) check again with the SAME
Code:
dmesg | tail
if it only attaches a "qualcomm usb-2-serial device on tty*" then you're in bad luck (as me) currently ... but if dmesg shows and lists some new "/dev/sdb1 /dev/sdb2 /dev/sdb3" devices and so on ... you can fairly easy fix it (at least as _now_ we/i had extracted or better said reconstructed the partition-layout and thereby we could flash any borked or unmatching partition directly).
as for S-OFF, that _should_ have nothing to do with the reason for the brick as there are already fellows here with properly updated OTA2014 firmware _working_ with properly retained S-OFF ... and secondly, it doesn't have to be one of your SBL2*'s as it could also be TZ or RPM not matching one another (as far as I understood the SecureBoot3.0-chain) ... so it depends WHICH file you (tried to) flash (and how) that leaded to your brick.
EDIT: as for your attached MSM8960-files ... identical to mine and thereby unfortunately NOT working (afaik) for recovery of a fireball T_T
any improvements on this problem? I'm having the same problem with my phone so please let me know if you find a way to fix this problem....
bought another Dinc4G ... in replacement for my bricked one. in my trail to revive my bricked one (and/or having another Dinc4g at least to use regularly with a ROM of my choice again)
after requested, the seller _confirmed_ that the 2014-OTA has __not__ yet been applied and the phone still runs fine on 2.17.605.2 ... and "guess what" i received yesterday in my mail:
his Dinc4G _WITH_ the 2014-OTA applied & of course it's stock/locked/s-on!!! DAMN IT!!!
kimba99 said:
bought another Dinc4G ... in replacement for my bricked one. in my trail to revive my bricked one (and/or having another Dinc4g at least to use regularly with a ROM of my choice again)
after requested, the seller _confirmed_ that the 2014-OTA has __not__ yet been applied and the phone still runs fine on 2.17.605.2 ... and "guess what" i received yesterday in my mail:
his Dinc4G _WITH_ the 2014-OTA applied & of course it's stock/locked/s-on!!! DAMN IT!!!
Click to expand...
Click to collapse
That sucks. Having this phone unrooted with the 2014 update is a little like being Sandra Bullock in the film Gravity. I sure hope there's someone smarter than me working on root for this thing with the 2014 update.
not many users (or even devs!) left on our Dinc4G .... pretty unfortunate
i mean temp-root still work's (apparently) on the 2014-OTA ... and the hboot didn't change at all (it's still 1.15) ... i assume one needs to find a way to perm-root the new 2.19.605.2 stock-rom first & from there try the same (or at least similar) "s-off" attack to the 1.15-hboot as previously. it's just that the devs of the prev s-off methods don't tell WHERE or HOW they obtained write-permission to set the s-off flag
still: i managed to trigger the "tampered"-flag above my "*locked*"-flag ... *lol*
kimba99 said:
bought another Dinc4G ... in replacement for my bricked one. in my trail to revive my bricked one (and/or having another Dinc4g at least to use regularly with a ROM of my choice again)
after requested, the seller _confirmed_ that the 2014-OTA has __not__ yet been applied and the phone still runs fine on 2.17.605.2 ... and "guess what" i received yesterday in my mail:
his Dinc4G _WITH_ the 2014-OTA applied & of course it's stock/locked/s-on!!! DAMN IT!!!
Click to expand...
Click to collapse
With the news of the new s-off method for the latest OTA, I was wondering if you were able to fix your phone. Looks like the answer is no, buuuut, you now have s-off with the latest OTA! :good: !
junkmail9 said:
With the news of the new s-off method for the latest OTA, I was wondering if you were able to fix your phone. Looks like the answer is no, buuuut, you now have s-off with the latest OTA! :good: !
Click to expand...
Click to collapse
unfortunately not (yet?) ... but at least, i'm near exactly where i was left on the new phone! real incredible that i could restore my nandroid from the borked phone directly to the new one (okay, after i figured out i need to rename the TWRP-backup folder to match ne new ADB-ID of the phone ... only missing a bunch of photos, that i didn't backup prior to the brick.
i'll try again later, but the brick still doesn't accept to be flashed either way by QPST as it says it is missing "its magical token" (whatever that means, but there are several posts about that specific QPST issue with qhsusb_dload bricked phones here on xda)
finally solved ... but that SURE wasn't for the faint hearted => poor fireball had to strip completely (disassambled) ... JTAG pins are ___under___ the IMEI-battery sticker even (so that had to be removed as well) ... before the "solder party" could begin.
and then thanks to _huzein_ from "gsm-europe" (who provided the RIFF-box and soldering for some smaller money) ... and the famous _legija_ ... the developer of the RIFF-box himself! (who guided us and reflashed my brick via a remote RIFF-session) ... flashing a bricked "HTC fireball" via JTAG for the very FIRST time!! we used the dump from jsmiley13 (so thanks to him again for providing me with the dump) ... after that we needed to reflash the ENG-HBOOT (via RIFF JTAG interface again) though as it had the 1.15.1111 but showed S-OFF _locked_ ?!
now it's back alive ... after 2hrs of remote debugging, remote-flashing etc ... hopefully now, legija can implement a NEW ressurrector.dll for fireball (for the 1ST TIME) and add it as a by now newly supported device on his RIFF-box!
attached below is a small "photo-story" ... for those who are interested *lol* ... and NO it's not an optical illusion, the panels definitely appear to have some slightly different color-hue (esp the green looks not the same)
kimba99 said:
finally solved ... but that SURE wasn't for the faint hearted => poor fireball had to strip completely (disassambled) ... JTAG pins are ___under___ the IMEI-battery sticker even (so that had to be removed as well) ... before the "solder party" could begin.
and then thanks to _huzein_ from "gsm-europe" (who provided the RIFF-box and soldering for some smaller money) ... and the famous _legija_ ... the developer of the RIFF-box himself! (who guided us and reflashed my brick via a remote RIFF-session) ... flashing a bricked "HTC fireball" via JTAG for the very FIRST time!! we used the dump from jsmiley13 (so thanks to him again for providing me with the dump) ... after that we needed to reflash the ENG-HBOOT (via RIFF JTAG interface again) though as it had the 1.15.1111 but showed S-OFF _locked_ ?!
now it's back alive ... after 2hrs of remote debugging, remote-flashing etc ... hopefully now, legija can implement a NEW ressurrector.dll for fireball (for the 1ST TIME) and add it as a by now newly supported device on his RIFF-box!
attached below is a small "photo-story" ... for those who are interested *lol* ... and NO it's not an optical illusion, the panels definitely appear to have some slightly different color-hue (esp the green looks not the same)
Click to expand...
Click to collapse
Looks like I am also having the same issue. Did an exchange remote wipe and came back to my phone completely bricked, Q Download mode. I am guessing the only way is to JTAG the device? Is there any other possibilities? I have qpst, and hpst etc. What is the hex and mbn image used for?
freemenot said:
Looks like I am also having the same issue. Did an exchange remote wipe and came back to my phone completely bricked, Q Download mode. I am guessing the only way is to JTAG the device? Is there any other possibilities? I have qpst, and hpst etc. What is the hex and mbn image used for?
Click to expand...
Click to collapse
depends on HOW your fireball was bricked ... but plain QPST or similar won't help as our CPU, the MSM8960, is toooo new and the unsigned usb-loader (like QPST) won't work ... at least if it's a firmware brick!!! (as legija explained to me)
only JTAG'ing via RIFF-box would help here, _but_ official support from RIFF is _NOT yet_ given (today using my brick was his trail run for "fireball") ... it should be implemented within the next days or a few weeks maybe.
Congrats on getting it back alive!
That is some impressive major surgery. Wow!
impressive!!!
great info!
i wonder how many brave souls will ever try this. a new phone for $200 might be the easier route for most people.