Related
My dell was totally dead (Bricked) and I sent it to one of my friends to JTAG. After Resurrection with Riff Box, it came to live but it does not recognize the sim card (shows no sim card). In addition to that it shows TAG Number 000000. Please help.
what rom is currently installed? you could try reinstalling with 351/latest to make sure all the firmware files are in sync.
Have you tried doing a read on a good streak to make sure the data loaded though jtag was good?
(I dont have any actual exprience jatagging, i assume you can do reads though it just like you can do writes)
TheManii said:
what rom is currently installed? you could try reinstalling with 351/latest to make sure all the firmware files are in sync.
Have you tried doing a read on a good streak to make sure the data loaded though jtag was good?
(I dont have any actual exprience jatagging, i assume you can do reads though it just like you can do writes)
Click to expand...
Click to collapse
I do not have any information about JTAG. My friend has done the JTAG. I will try to forward your post him.
iT iS Me said:
My dell was totally dead (Bricked) and I sent it to one of my friends to JTAG. After Resurrection with Riff Box, it came to live but it does not recognize the sim card (shows no sim card). In addition to that it shows TAG Number 000000. Please help.
Click to expand...
Click to collapse
I have the same problem after my Riff JTAG around 3-4 days back. I have the unlock Code but it's not prompting me to input one. My Service Tag Number has also gone 000000.
(I am not sure if Streak Unlocker will be able to unlock my phone and therefore not paid $29 yet though the test shows it can. But then Test was showing it can unlock by phone even when it was already unlocked.)
I guess JTAG has somehow re-written the BIOS and not sure what to do next. I have tried Stock ROMs but still not getting the prompt to put unlock code. I am considering to get the JTAG done again and get everything written properly or try Streak Unlocker after paying $29.
There must be a way to put the unlock Code in Engineering mode or by keying in some number like *#123UNLOCK321#* or find & write the code manually. If streak unlocker can do it there must be way to do it manually too.
Well the streak has to store some special data somewhere, stuff like the service tag among them.
If you can get your hands on a couple of working, stock streaks, you might want to consider trying to dump that data and seeing what's shared among all streaks what what is unique. Very least it might give you a clue on why yours isnt working/displays no service tag
TheManii said:
Well the streak has to store some special data somewhere, stuff like the service tag among them.
If you can get your hands on a couple of working, stock streaks, you might want to consider trying to dump that data and seeing what's shared among all streaks what what is unique. Very least it might give you a clue on why yours isnt working/displays no service tag
Click to expand...
Click to collapse
If some one has a better or rather a more practical idea..Please help. Getting couple of Streaks is almost impossible here (India) and further getting them on Stock ROM will be equally impossible at most of the places (how many ppl you find around.... having a streak?)
I have the unlock code.......Just need a way to enter it....I am not getting this prompt on any ROM I have tried QDL, Stock O2, Stock AT&T. Stock Hong Kong (354) ...and have hit the wall
nirajkrm said:
If some one has a better or rather a more practical idea..Please help. Getting couple of Streaks is almost impossible here (India) and further getting them on Stock ROM will be equally impossible at most of the places (how many ppl you find around.... having a streak?)
I have the unlock code.......Just need a way to enter it....I am not getting this prompt on any ROM I have tried QDL, Stock O2, Stock AT&T. Stock Hong Kong (354) ...and have hit the wall
Click to expand...
Click to collapse
I am really SAD for you. my mobile still with my friend and so far I do not know what is the status (I am just waiting ). Have you done a full backup before it got bricked. If so, try full restore (This what I asked my friend to do).
Same Problem!!
I had the same problem with my DS. It shows a message Default NV selected #3 while loading in fastboot mode. so i guess something went wrong while setting the default NV to 3??.
Valid SIM card is no longer detected and gives notification saying No SIM Card.
It was a factory unlocked phone and was bricked last month by the command fastboot -w.
since this command erased the user data from somewhere inside the phone(either Internal SD card or the ROM), there should be some ways to re-write those data to those locations.
If any one is familiar to develop some kinda application that can write to those locations then pleaseeeeeeeeee try this out for us.. we can root the device if needed..
If anyone with same problem has got any solutions then please do share with me too..
my email address is : [email protected]
Thanks in advance
JTAGging the Streak is the only way to revive a Streak that has been hit with a fastboot -w. And as you have seen from the rest of the thread it's very likely the Streak will never be able to make calls again after recovery. There are multiple other users in the forum dealing with bricked Streaks, and out of all of them, I believe only one was able to restore phone capability.
Changing MicroSD cards and/or ROMs won't help because the affected area is in the Streak's BIOS (for lack of a better term). The service tag and SIM card low-level interface firmware are stored in the BIOS.
There gotta be a way out of it!!
Hi eveyone!
Now i ended up to a dell streak tablet(was phone) after i did the "fastboot -w" .
The guys from dell mailed me yesterday that they can recover it but would cost me 179.9 pounds(Which i bought for 200 pounds). Is that fair?? to charge 179 for repairing a phone that can be bought at 200?? So i decided not to send to the dell store for repair.
Since i am not an expert I am not sure about this ,But i think there is a way out of this problem, I mean if "fastboot -w" command erases the data from "god knows which location" then there can be a command like "fastboot -wr location data_to_be_copied" which simply copies some thing that is missing due to fastboot -wr command??
Is there anyone who can Reverse Engineer the fastboot and figure out from where the data was deleted and what was deleted and the way to restore those data there???
Thanks in advance to those who would analyze the fastboot and its data flow and try to help coz there are lot of people waiting for this..
We have 8 nand partitions (/dev/block/mtdblock0-7)
One is for kernel boot image, other might contain system, bb, firstboot and other stuff.
Maybe the answer is there?
Fastboot -w/erase likely corrupts the partition table on the innerSD,
seeing as it was prob due to dell never updating their fastboot loader to take it into account. (The Venue doesnt have this issue as it doesnt have an innerSD).
You can fix it by either restoring it to a known good image (there's a thread on the main subforum) or by manually repartitioning your innerSD.
You will need to disassemble your S5 to do it (regardless of who does it) and a pc with a SD/microSD port then just reimage it, it's not very difficult besides the disassembling part.
The firmwares are on the nand, but we cant read to it, and the only way to (safely) write to it is the stock rec.
Dear XDA community,
everyday i'm reading new questions from users, how they have to unlock their Lumia 800 and how they can flash custom roms onto it...
So i decided to make this how-to-thread.
I'll keep this post updated as an overview:
post 2: Bootloader unlock DLOAD Lumia 800 to Qualcomm
post 3: Backup and flash your L800 with Ubuntu, flash in Windows using dewe's Lumia Downloader 0.5
post 4: How-To use USB-Video-Out
So please, guys, read this thread, and if you don't understand, feel free to ask. :good:
Bootloader unlock DLOAD Lumia 800 to Qualcomm
If you want to flash a custom rom, you need to have a Lumia 800 with qualcomm bootloader.
But it's a difficult way to make your DLOAD Lumia 800 to Qualcomm:
You need two main things:
1. You need ATF flasher box
2. You need good soldering skills or the special atf cables from gpg industries
Here's a tutorial to SIM-Unlock a Lumia 800: How-To SIM-Unlock your Lumia 800 - gsmhosting.com
This is almost the same procedure for "bootloader-unlocking" your Lumia 800.
You just do not need to click SP-Unlock, you need to click "boot repair" (and select qualcomm, of course).
Here's the thread of the special cables: No more soldering for lumia 610,710,800,900 easiest osbl swap ever
These cables do not require you to solder your device. You only need to open up your phone and connect it to the cable and your ATF Box.
So, if you don't want, or can't buy such a box, check for a local phone repair shop in your town/city. If they have ATF, i'm sure they can do this for you for a small amount.
Hope this helps.
Flash your custom rom using dewe's Lumia Downloader 0.5
Dewe's Nokia Lumia Downloader 0.5
I attached the Nokia Lumia Downloader 0.5 for flashing your Lumia 800 easily in Windows.
Thx to dewe for his great work!
This requires your Lumia 800 to have the qualcomm bootloader!!
First: make a backup of ALL 9 partitions of the phone!
This might really save your ass Id did save mine more than once :good:
1. Install Ubuntu to your computer, or use Ubuntu-Live-CD
2. put phone into "Qualcomm Mode" by pressing VOL UP + POWER and connect it to your pc
3. check with
Code:
sudo fdisk -l
how your phone appears in ubuntu
4. backup your partitions using this:
Code:
sudo dd if=/dev/sd[B]X[/B]1 of=/media/Data/backup1.bin
sudo dd if=/dev/sd[B]X[/B]2 of=/media/Data/backup2.bin
sudo dd if=/dev/sd[B]X[/B]3 of=/media/Data/backup3.bin
up to
sudo dd if=/dev/sd[B]X[/B]9 of=/media/Data/backup9.bin
where the X is your special letter, mostly it's b, c, or d.
if = your input file
of = your output file
And this might take up to 2 hours.
Restoring your backups is the exact opposit.
second: you can now flash your Lumia 800.
because you're already in Ubuntu, you can flash it using:
Code:
sudo dd if=/path/to/your/os-new.nb of=/dev/sd[B]X[/B]9
You MUST flash the os-new.nb file to partition 9!!!
Or you can use attached Nokia Lumia Downloader on Windows.
1. Connect your phone in "qualcomm mode"
2. open the Tool with admin rights in Windows
3. Klick "download" and select os-new.nb file
NOTICE: when you connect the phone in "qualcomm mode" in windows, you'll get a message of formatting the drive. DO NOT DO THAT!!!! CLICK CANCEL! If you format, your phone's broken.
How-To use USB-Video-Out
How to use USB Video Out:
As it seems to be a little "difficult" to use the usb video out package, here's what you have to do (this is a copy out of the readme file of the package):
You can download the needed files here:
USB-Video-Out.rar
Mirror @4shared
Enabling USB video out on the phone (ON THE PHONE)
- From Start Menu swipe over to the application list and run "USB Video Out"
- Answer Yes to enable USB Video out. This is a toggle.
- When the phone boots up it is in Zune Mode which enables it to sync data with Zune Client software on the PC. You will need to toggle this to Video mode using the above steps to get video out.
- Note: Toggling between Zune mode and Video mode requires the phone to reboot each time.
Setting up driver on the desktop (one time)
- Make sure Zune is not running.
- Your Phone must be flashed with a ROM that has video out bits on it, they must be enabled, and the phone must be on and plugged into your PC to continue. When the phone boots up the default setting is OFF for the video output.
- Start -> Right click on Computer, select Manage
- In "Computer Management" click on the Device Manager
- Under "Other Devices"
- Within the list of drivers Right Click on WM7VIDSTREAM driver, select "Update Driver Software..."
- Choose Browse and point Windows to appropriate driver folder.
- Approve the Unsigned Driver installation.
Starting application
- Launch VidStream.exe.
- This application does support disconnect & reconnecting of the phone's USB cable.
- If a previous instance of VidStream.exe was running with the device connected, you will need to simply unplug and replug the phone's USB cable.
- Press ESC to exit the PC Client application.
Re-enabling MTPz USB sync (Zune Mode)
- Open "USB Video Out"
- Answer Yes to enable MTPz
- The device will reboot to make the changes effective.
Click to expand...
Click to collapse
Oh, I was about to write that I'm flashing my phone on Windows but then I saw this method below the Ubuntu.
Isn't it better to put the windows method above the ubuntu? I think more ppl use Windows and possibly won't se the windows method as me
Paviano said:
Oh, I was about to write that I'm flashing my phone on Windows but then I saw this method below the Ubuntu.
Isn't it better to put the windows method above the ubuntu? I think more ppl use Windows and possibly won't se the windows method as me
Click to expand...
Click to collapse
Hi, thx for reply, i wrote it this way, because i wanted to point out, that it is really recommended to make a backup.
If i put the windows flashing above, most people will stop reading, and don't make a backup
I think this way, more people read the backup story, so it's their choice if they don't make one
Zune
Hey thanks for this tutorial. I just had one quick question.
After I do this can I still sync with Zune? Because I would like my data such as songs and apps back. Is this still possible?
if i got for it, it will cost me about 12000 Pakistani rupee for ATF, and about 4000 Pakistani rupee for cable............total 16000, and i can buys with this + sale price of my cell = samsung s#........my GOD....where i am
Good bye to lumia 800....wanna get rid off
bowi1612 said:
Hey thanks for this tutorial. I just had one quick question.
After I do this can I still sync with Zune? Because I would like my data such as songs and apps back. Is this still possible?
Click to expand...
Click to collapse
Hi there,
sorry for late reply.
I you mean with "doing this" unlocking your bootloader, syncing data does not really have anything to do with your bootloader.
Generally, if you make your DLOAD to Qualcomm, your personal files are still on your phone, as bootloader changing does not overwrite any personal files (partition 9 of the phone).
It matters more, which rom you install, if syncing content with zune is still possible or not.
If you flash a custom rom, your data is whiped, as you overwrite your OS partition with the custom rom. But after that, with my roms for example, you can sync your songs etc. back to your Lumia.
I don't think this might work with apps, you have to install them again via marketplace.
Is it possible to use your ROMs on N9?
Is it possible to use your ROMs on Nokia N9? If yes how?
with regards
hrbani said:
Is it possible to use your ROMs on Nokia N9? If yes how?
with regards
Click to expand...
Click to collapse
Is this a serious question??
mate... N9 is a totally different phone, this will NOT work!
Thanks. I'm amateur and know noting about ROM port and others, I asked that question because I want win phone on my N9 .
with regards
Bootloader unlock DLOAD to Qualcomm L800
If I do Bootloader unlock DLOAD to Qualcomm L800 using ATF NITRO ...
do this make any changes on my ROM..?
will this make my phone data wiped...?
and do i need any kind of flash files for this
saddam.khan999 said:
If I do Bootloader unlock DLOAD to Qualcomm L800 using ATF NITRO ...
do this make any changes on my ROM..?
will this make my phone data wiped...?
and do i need any kind of flash files for this
Click to expand...
Click to collapse
Hi there,
no, this only overwrites your bootloader, which is on a different partition as the phone operating system.
so this will not wipe your phone data.
just flashing a custom rom will wipe your data.
Remove Funkyrom
I am just wondering. If I ever want to go back to the Original Windows Phone OS, can I just restore to factory settings on my windows phone? Or do I need to do some other stuff, I can't find an answer anywhere.
bowi1612 said:
I am just wondering. If I ever want to go back to the Original Windows Phone OS, can I just restore to factory settings on my windows phone? Or do I need to do some other stuff, I can't find an answer anywhere.
Click to expand...
Click to collapse
Hi there,
if you've made a backup, you can restore this and reset your phone afterwards.
That's the best solution in my opinion, because you're back on the original rom, but you're still on the qualcomm bootloader, so you can reflash a custom rom whenever you want
Of course you can restore DLOAD and flash the original ROM with ATF, too. But then you have to do the soldering stuff again, if you want to use a custom rom in the future.
thanks for your support
What about the method from cyclone box?
Do you think there will be a method soon for changing bootloader without opening the phone and buying a box? The problem is I don't want to pay for cyclone box.
Celteek said:
What about the method from cyclone box?
Do you think there will be a method soon for changing bootloader without opening the phone and buying a box? The problem is I don't want to pay for cyclone box.
Click to expand...
Click to collapse
No. I think there'll never be an option.
Afaik, this is only possible with ATF, not with cyclone.
lordmaxey said:
No. I think there'll never be an option.
Afaik, this is only possible with ATF, not with cyclone.
Click to expand...
Click to collapse
It is said on their website that it is possible to patch bootloader without opening the phone. (sorry I can't post links yet, but it is easy to find on google by typing "cyclone box lumia 800 no tp" ). Unfortunately we need a cyclone box . My question is : will there be a method with which we don't need a cyclone box?
I was trying to unlock with gc pro key with sprint unlock to work with gsm carriers and it didnt work for me. So i tried a different formula which i flashed a firmware "ZV3" on Z3X Box and i was running on ZV5. Now the phone doesnt turn on and when connected to computer the usb driver says "Qualcomm Usb USB QDLoader 9008. Any solutions will be highly appreciated and would save me on having to buy a customer a new phone.
First lesson.. don't downgrade any lg latest phones, 2nd dont use boxes too flash it, use lgup so you can get warning of laf downgrade. 3rd search medusa or z3x jtag if they support jtag, or if you smart enough too find pinoits on board for jtag.
xplict310 said:
I was trying to unlock with gc pro key with sprint unlock to work with gsm carriers and it didnt work for me. So i tried a different formula which i flashed a firmware "ZV3" on Z3X Box and i was running on ZV5. Now the phone doesnt turn on and when connected to computer the usb driver says "Qualcomm Usb USB QDLoader 9008. Any solutions will be highly appreciated and would save me on having to buy a customer a new phone.
Click to expand...
Click to collapse
i also bricked my ls775 any one have system dump can write in sdcard may be get download mode thanks
ls775 rom dump.
gdeepp said:
i also bricked my ls775 any one have system dump can write in sdcard may be get download mode thanks
Click to expand...
Click to collapse
dear sr. i have zv5 and zv7 rom dumps of this phone, thing is that partitions are not the same in both versions, so you need to know which one you had on your device, if you know to flash this with sd card i'll provide both software versions for free, as long as you are willing to share the "flashing with sd" tutorial, if it actually works of course. by the way, both versions were dumped with z3x.
ls775 rom dump
hcom said:
dear sr. i have zv5 and zv7 rom dumps of this phone, thing is that partitions are not the same in both versions, so you need to know which one you had on your device, if you know to flash this with sd card i'll provide both software versions for free, as long as you are willing to share the "flashing with sd" tutorial, if it actually works of course. by the way, both versions were dumped with z3x.
Click to expand...
Click to collapse
bro i was bricked on ZV5 so u only upload it on google drive or mega.....also if u have any knowledge about Sd card flash also share it thanks
ls775 qdloader 9008
Well guys, i have one piece in the same condition, I have z3x but there is no support for this model, no firmwares no jtag files or even pinout, if any of you find the way to flash the emmc back in to the phone please let me know. i can offer you the extracted files for version zv8 and zva, if someone needs them to test or whatever i am willing to share.
have a nice day
lo solucione amigos
Hi, @ante0 , @Pretoriano80 and everyone else!
Been lurking on these forums ever since mate 10 Pro was released, but due to being one of the folks to downgrade from emui 9 to brick I had to take my phone to service for board swapping as I wasn't in a situation to do the testpoint fix myself.
Now, I'm looking to get the bootloader unlock code again and to my surprise even the 3rd party sites are down.
There's a guy at minstryofsolutions that offers bootloader unlock code using testpoint but he asks for 40$ + access to pc for 2 hours + refuses to describe in any way what he's doing to the device and why will the device end up rebranded + new imei and with it new bootloader code ( Obviously device in that condition can't be taken into a Huawei service center) .
So, upon searching and trying to find if anyone had found a way to unlock using testpoint I stumbled upon this : https://forum.xda-developers.com/mediapad-m5/how-to/downgrade-unbrick-huawei-device-methods-t3915693
Op and several others seem successful with downgrading their devices and using dc unlocker to get the code once the security patch is no more.
Op even mentions that for kirin 970 it's probably the same process but I haven't seen anyone sharing their experience doing the same on 979 devices.
Couple users are having issues as well and while op was quite helpful he and several others that were helping out seem to have been gone missing. There's a guy helping out with issues regarding this process but it seems rather finicky when even after doing all this and flashing with dload certain parts like lte modem remain present on a WiFi only tablet.
Does anyone have passes for easy firmware or dc unlocker firmware database? Is anyone willing to give these a try and see if the process will work on our devices or if it will ask for verification of some kind for images being flashed?
It looks quite promising, so if anyone has a bricked device ( Maybe someone that was refused at the Huawei repair center during the wave of downgrades ) would you be willing to give it a try?
I've got no tools, no passes and no other device to use while playing with this.
Obviously, I'm not asking for you guys to go out of your way and brick the device so I can know whether this is a viable option or not lol.
Just thought about sharing and seeing if anyone more knowledgeable has anythiny they'd like to add to this as a tip or personal experience trying this method.
This might be what we are looking for when it comes to unlocking device / downgrading to lower versions.
Hopefully the post I linked helps someone, in case anyone has experience with this please share as well!
Anyways thanks in advance!
Rstment ^m^ said:
Hi, @ante0 , @Pretoriano80 and everyone else!
Been lurking on these forums ever since mate 10 Pro was released, but due to being one of the folks to downgrade from emui 9 to brick I had to take my phone to service for board swapping as I wasn't in a situation to do the testpoint fix myself.
Now, I'm looking to get the bootloader unlock code again and to my surprise even the 3rd party sites are down.
There's a guy at minstryofsolutions that offers bootloader unlock code using testpoint but he asks for 40$ + access to pc for 2 hours + refuses to describe in any way what he's doing to the device and why will the device end up rebranded + new imei and with it new bootloader code ( Obviously device in that condition can't be taken into a Huawei service center) .
So, upon searching and trying to find if anyone had found a way to unlock using testpoint I stumbled upon this : https://forum.xda-developers.com/mediapad-m5/how-to/downgrade-unbrick-huawei-device-methods-t3915693
Op and several others seem successful with downgrading their devices and using dc unlocker to get the code once the security patch is no more.
Op even mentions that for kirin 970 it's probably the same process but I haven't seen anyone sharing their experience doing the same on 979 devices.
Couple users are having issues as well and while op was quite helpful he and several others that were helping out seem to have been gone missing. There's a guy helping out with issues regarding this process but it seems rather finicky when even after doing all this and flashing with dload certain parts like lte modem remain present on a WiFi only tablet.
Does anyone have passes for easy firmware or dc unlocker firmware database? Is anyone willing to give these a try and see if the process will work on our devices or if it will ask for verification of some kind for images being flashed?
It looks quite promising, so if anyone has a bricked device ( Maybe someone that was refused at the Huawei repair center during the wave of downgrades ) would you be willing to give it a try?
I've got no tools, no passes and no other device to use while playing with this.
Obviously, I'm not asking for you guys to go out of your way and brick the device so I can know whether this is a viable option or not lol.
Just thought about sharing and seeing if anyone more knowledgeable has anythiny they'd like to add to this as a tip or personal experience trying this method.
This might be what we are looking for when it comes to unlocking device / downgrading to lower versions.
Hopefully the post I linked helps someone, in case anyone has experience with this please share as well!
Anyways thanks in advance!
Click to expand...
Click to collapse
You can as I've done it.
Use testpoint (this will void warranty as you have to remove back of the phone) and flash bootloader files from DC Phoenix, there are several Kirin970 to choose from but only one should work. DC will tell you when phone is in fastboot mode after flashing.
Then I used IDT (Image Download Tool) to flash board firmware. Boot to board firmware and used HCU to repair imeis and all that. Then used HCU to get an unlock code. After this flash dload firmware back to Oreo (needs to be a new dload because of updated bootloader).
HCU fix guide for BLA:
1)Flash oeminfo (own backup) from fastboot OR dump existing oeminfo using adb pull (adb pull /dev/block/bootdevice/by-name/oeminfo) then flash it from fastboot.
2)Backup modemnvm_system, modemnvm_factory and modemnvm_backup using adb pull from a command prompt (/dev/block/bootdevice/by-name/modemnvm_system and so on)
3)Flash backed up modemnvm_system, modemnvm_factory and modemnvm_backup from fastboot
3)Modify and brand with HCU in the CDMA tab (check everything but those that erase/flash empty board) (remember to fill vendor and cust)
4)Unlock sim 'Direct SIM Unlock'
5)Read Bootloader code if you ever used HCU to get code before or if you need unlock code
6)Download and flash Oreo service firmware from androidhost.ru using a OTG cable and a memory stick. Pick the latest Oreo one you find for your cust
If you fail to do any of the steps above you will end up with no IMEIs or 'No Network' and/or Sim lock
So you'd need: DC/HCU pass and unencrypted board firmware (gem-flash and easy-firmware has them but they're paid.).
I have not tested using DCs own board firmware.
ante0 said:
You can as I've done it.
Use testpoint (this will void warranty as you have to remove back of the phone) and flash bootloader files from DC Phoenix, there are several Kirin970 to choose from but only one should work. DC will tell you when phone is in fastboot mode after flashing.
Then I used IDT (Image Download Tool) to flash board firmware. Boot to board firmware and used HCU to repair imeis and all that. Then used HCU to get an unlock code. After this flash dload firmware back to Oreo (needs to be a new dload because of updated bootloader).
HCU fix guide for BLA:
1)Flash oeminfo (own backup) from fastboot OR dump existing oeminfo using adb pull (adb pull /dev/block/bootdevice/by-name/oeminfo) then flash it from fastboot.
2)Backup modemnvm_system, modemnvm_factory and modemnvm_backup using adb pull from a command prompt (/dev/block/bootdevice/by-name/modemnvm_system and so on)
3)Flash backed up modemnvm_system, modemnvm_factory and modemnvm_backup from fastboot
3)Modify and brand with HCU in the CDMA tab (check everything but those that erase/flash empty board) (remember to fill vendor and cust)
4)Unlock sim 'Direct SIM Unlock'
5)Read Bootloader code if you ever used HCU to get code before or if you need unlock code
6)Download and flash Oreo service firmware from androidhost.ru using a OTG cable and a memory stick. Pick the latest Oreo one you find for your cust
If you fail to do any of the steps above you will end up with no IMEIs or 'No Network' and/or Sim lock
So you'd need: DC/HCU pass and unencrypted board firmware (gem-flash and easy-firmware has them but they're paid.).
I have not tested using DCs own board firmware.
Click to expand...
Click to collapse
Thanks a lot!
Will any of this process leave bootloader unlocked / relocked along the way?
I'm experiencing screen burn in due to outdated firmware and was gonna get the code, apply new adhesive I buy online and have them replace the device's screen + seal it properly in the process so the water resistance remains - kinda essential to hide any signs of tampering like bootloader unlock '-' ( 2nd burn in on Oreo firmware now, both happened within few months of the device running old firmw )
Thanks for the guide as well!
I'm not completely sure how to do the whole process yet but I'll try getting all the software I can right now and try figuring it out.
One question tho, do you have any screenshots you can share of which firmware will work out of those several that you mentioned and is there any possibility of brick by flashing wrong xload, etc.?
I'm on 8.0.0.156 c432 and was gonna drop to 142 or 143 - will have to check which one is the latest without security patch.
Glad to know this is a possibility! Will order the tools required for this and when / if I'm successful I'll create seperate thread under guides as there prolly are peps still trying to unlock.
Rstment ^m^ said:
Thanks a lot!
Will any of this process leave bootloader unlocked / relocked along the way?
I'm experiencing screen burn in due to outdated firmware and was gonna get the code, apply new adhesive I buy online and have them replace the device's screen + seal it properly in the process so the water resistance remains - kinda essential to hide any signs of tampering like bootloader unlock '-' ( 2nd burn in on Oreo firmware now, both happened within few months of the device running old firmw )
Thanks for the guide as well!
I'm not completely sure how to do the whole process yet but I'll try getting all the software I can right now and try figuring it out.
One question tho, do you have any screenshots you can share of which firmware will work out of those several that you mentioned and is there any possibility of brick by flashing wrong xload, etc.?
I'm on 8.0.0.156 c432 and was gonna drop to 142 or 143 - will have to check which one is the latest without security patch.
Glad to know this is a possibility! Will order the tools required for this and when / if I'm successful I'll create seperate thread under guides as there prolly are peps still trying to unlock.
Click to expand...
Click to collapse
I doubt that the burn-in is because of the old firmware, probably the oled panel it's getting old.
You should do the other way around, first send it to Huawei for a display replacement and then get the unlock code.
The procedure it's not really easy and the water resistant part it's the last of your problem, first you must make sure that you don't break the glass back cover when you open it up. xD
Probably Huawei's repair center won't even bother to replace the display only, but they will replace almost everything, so you would endup with a locked bootloader again.
Pretoriano80 said:
I doubt that the burn-in is because of the old firmware, probably the oled panel it's getting old.
You should do the other way around, first send it to Huawei for a display replacement and then get the unlock code.
The procedure it's not really easy and the water resistant part it's the last of your problem, first you must make sure that you don't break the glass back cover when you open it up. xD
Probably Huawei's repair center won't even bother to replace the display only, but they will replace almost everything, so you would endup with a locked bootloader again.
Click to expand...
Click to collapse
The display literally burned in couple months after I boguht the device and and we still had the emui 8 only. Replaced it and switched to the 9 the same month. All was good for a year or so untill they replaced motherboard. Now the same thing all over again, few months have passed - literally 2/3 months and the screen burned in again at the same spot - navigation bar.
The opening part doesn't look that complicated, was thinking of buying a heating plate, heat phone to 120°C and go back and forward cutting adhesive then heating the phone again. Should be fast and efficient this way.
The finicky part that I'm worried about has to do with bricking the device or shorting the motherboard in some way '-' Maybe service also uses some repair stickers that aren't present on any of the guides and will get dmged when I open the device - after all, I took the device for repairs under warranty at least 5+ times by now
Last time for the replacement they indeed replace almost everything - display, battery, back cover, new frame - essentially a new device w same motherboard.
Pretoriano80 said:
I doubt that the burn-in is because of the old firmware, probably the oled panel it's getting old.
You should do the other way around, first send it to Huawei for a display replacement and then get the unlock code.
The procedure it's not really easy and the water resistant part it's the last of your problem, first you must make sure that you don't break the glass back cover when you open it up. xD
Probably Huawei's repair center won't even bother to replace the display only, but they will replace almost everything, so you would endup with a locked bootloader again.
Click to expand...
Click to collapse
Rstment ^m^ said:
The display literally burned in couple months after I boguht the device and and we still had the emui 8 only. Replaced it and switched to the 9 the same month. All was good for a year or so untill they replaced motherboard. Now the same thing all over again, few months have passed - literally 2/3 months and the screen burned in again at the same spot - navigation bar.
The opening part doesn't look that complicated, was thinking of buying a heating plate, heat phone to 120°C and go back and forward cutting adhesive then heating the phone again. Should be fast and efficient this way.
The finicky part that I'm worried about has to do with bricking the device or shorting the motherboard in some way '-' Maybe service also uses some repair stickers that aren't present on any of the guides and will get dmged when I open the device - after all, I took the device for repairs under warranty at least 5+ times by now
Last time for the replacement they indeed replace almost everything - display, battery, back cover, new frame - essentially a new device w same motherboard.
Click to expand...
Click to collapse
Also, if they do replace stuff the code you get through DC will not work.
It works by modifying some strings in the oeminfo partition, so if they were to wipe and reflash everything your code would be lost.
If they replace motherboard you will need a new unlock code.
There is a sticker on one of the screws you need to remove, so they will know you did open it anyway.
Bricking is no problem as you can unbrick using testpoint. Shorting shouldn't be a problem. I tried all the visible points and only 1 or 2 actually send current back so USB devices in computer restarted xD But none of them shorted my phone.
ante0 said:
Also, if they do replace stuff the code you get through DC will not work.
It works by modifying some strings in the oeminfo partition, so if they were to wipe and reflash everything your code would be lost.
If they replace motherboard you will need a new unlock code.
There is a sticker on one of the screws you need to remove, so they will know you did open it anyway.
Bricking is no problem as you can unbrick using testpoint. Shorting shouldn't be a problem. I tried all the visible points and only 1 or 2 actually send current back so USB devices in computer restarted xD But none of them shorted my phone.
Click to expand...
Click to collapse
I see on pictures online that there are some points exposed with the shield on. Will take a look at picture you posted earlier for testpoint location to determine if indeed you can access it without removing the shield - hence not touching the stickers you mentioned - ty!
Wdym by losing dc unlocker code tho?
Does it not read the bootloader code of the device - meaning after they wipe / flash their stuff I can use the same code again to unlock via fastboot?
Or can it not read the code and just modifies the nvme files or whatev inside the partition to allow for a custom bootloader code?
Thanks for all the info! Will go look now for the picture then decide whether I'll open before or afterwards depending on the position of test point.
Rstment ^m^ said:
I see on pictures online that there are some points exposed with the shield on. Will take a look at picture you posted earlier for testpoint location to determine if indeed you can access it without removing the shield - hence not touching the stickers you mentioned - ty!
Wdym by losing dc unlocker code tho?
Does it not read the bootloader code of the device - meaning after they wipe / flash their stuff I can use the same code again to unlock via fastboot?
Or can it not read the code and just modifies the nvme files or whatev inside the partition to allow for a custom bootloader code?
Thanks for all the info! Will go look now for the picture then decide whether I'll open before or afterwards depending on the position of test point.
Click to expand...
Click to collapse
When you use HCU to get code it writes stuff to oeminfo, replacing 2 strings with "DC-UNLOC". So that's used in calculation of code. If you flash back stock, unmodified, oeminfo after using HCU you won't be able to use the code it generated.
Testpoint is located under the shield, so it's not possible to get to it without removing the shield. I have my phone with shield on infront of me. And I can't remember which screw had the sticker on it. If it's on one of the corners I guess you could try to bend it up to get to testpoint.
I just can't understand why the won't release the bootloader unlock at this point? The phone is now 'outdated' and old.... where is the harm?
ante0 said:
When you use HCU to get code it writes stuff to oeminfo, replacing 2 strings with "DC-UNLOC". So that's used in calculation of code. If you flash back stock, unmodified, oeminfo after using HCU you won't be able to use the code it generated.
Testpoint is located under the shield, so it's not possible to get to it without removing the shield. I have my phone with shield on infront of me. And I can't remember which screw had the sticker on it. If it's on one of the corners I guess you could try to bend it up to get to testpoint.
Click to expand...
Click to collapse
Thanks but I'm still having hard of a time following ?
After you use hcu it modifies the oeminfo to get strings it needs for calculations - You get the code aftwerards and your oeminfo is modified, right?
What I don't get is how flashing stock makes code unusable tho?
Is it not original bootloader code we'd get if Huawei site was still up? That code should be usable even after all modifications were reflashed with stock, no?
Or is it a custom code that depends on modified oeminfo to work?
Rstment ^m^ said:
Thanks but I'm still having hard of a time following ?
After you use hcu it modifies the oeminfo to get strings it needs for calculations - You get the code aftwerards and your oeminfo is modified, right?
What I don't get is how flashing stock makes code unusable tho?
Is it not original bootloader code we'd get if Huawei site was still up? That code should be usable even after all modifications were reflashed with stock, no?
Or is it a custom code that depends on modified oeminfo to work?
Click to expand...
Click to collapse
It's a custom code. If you use HCU to generate a code it invalidates your stock code. If you flash back stock oeminfo you can use the code Huawei gave you but not the HCU code (until you use HCU again to generate code).
Iirc on Kirin960 (and probably below it) you can use both HCU and stock code, so it uses another way of generating it I guess
Has anyone tried this approach for a MATE 10? or would you recommend it?
FUHuawei said:
Has anyone tried this approach for a MATE 10? or would you recommend it?
Click to expand...
Click to collapse
What method are you talking about?
If through testpoint, then yes!
Everything works perfectly
geogsm_1 said:
What method are you talking about?
If through testpoint, then yes!
Everything works perfectly
Click to expand...
Click to collapse
Yes, of course, I meant through test point. Do you know of any good step by step guide on how to do it? I want to try it and post here my results, if everything goes well I hope everyone ditches huawei software.
Also, I have searched around for options regarding ROMs, does anyone recommend anything in particular?
FUHuawei said:
Yes, of course, I meant through test point. Do you know of any good step by step guide on how to do it? I want to try it and post here my results, if everything goes well I hope everyone ditches huawei software.
Also, I have searched around for options regarding ROMs, does anyone recommend anything in particular?
Click to expand...
Click to collapse
Yes, I know the method) and have long written instructions on another forum with the permission of my teacher.
Decision made
On Huawei Mate 10 / Mate 10 Pro /, you can get the bootloader unlock code using a testpoint. But you need to have a programmer such as MRT / SIGMA / HDE / HCu-Client
Please upload this tool if you have it so i can fix my phone .. at this point t-mobile, metro pcs and god knows what they all were able not only to fix their phone but install the unlocked rom without the bloatware .. Honestly i don't get why OP refuses to release this .. or maybe they have but its not posted here ..
So if you bought your phone from oneplus.com and have the unbricking tool .. please upload it or tell me how you managed to fix your phone
Contact OnePlus support, and request a remote session to repair your phone.
If they set one up, they'll send you a link to download the MSMDownload Tools ahead of time.
So far everyone with unlocked version has been told to mail their phone in, rather than doing the remote session. Once someone gets the remote session, they'll be able to upload the MSMDownload Tools.
edale1 said:
Contact OnePlus support, and request a remote session to repair your phone.
If they set one up, they'll send you a link to download the MSMDownload Tools ahead of time.
So far everyone with unlocked version has been told to mail their phone in, rather than doing the remote session. Once someone gets the remote session, they'll be able to upload the MSMDownload Tools.
Click to expand...
Click to collapse
already went thru that and instead of sending my phone in chose to wait for the tool.. looks like i made a huge mistake and now is too late to send it in ... but thanks for suggesting
Also waiting for an ops for the unlocked variant - I have a theory that converts between variants without unlocking BL, but without the ops it can't be verified.
I believe One Plus is not releasing their MSM tool specifically because it could be used to convert variants to unlocked / retail. They have refused multiple board members, myself included, to utilize the tool to remotely fix broken devices.
Dimitrimem, check the unbrick thread for my instructions on how to fix phones using fastboot and a super.img or fastbootd and the OTA.
Un-bricking my Nord N200
Don't ask me why, but I tried to upload a GSI using fastboot to my N200. And that didn't work. So I then read online about other people getting the same error I had, and their fix was deleting the "product" partition and erasing the system...
forum.xda-developers.com
oCAPTCHA said:
I believe One Plus is not releasing their MSM tool specifically because it could be used to convert variants to unlocked / retail. They have refused multiple board members, myself included, to utilize the tool to remotely fix broken devices.
Dimitrimem, check the unbrick thread for my instructions on how to fix phones using fastboot and a super.img or fastbootd and the OTA.
Un-bricking my Nord N200
Don't ask me why, but I tried to upload a GSI using fastboot to my N200. And that didn't work. So I then read online about other people getting the same error I had, and their fix was deleting the "product" partition and erasing the system...
forum.xda-developers.com
Click to expand...
Click to collapse
Bootloader is locked so fastboot is not an option ..
Do you have the unlock code bin file?
If so do the following, because booting in fastboot itself will give you an error saying you cannot unlock the bootloader, you most boot into recovery, fastboot is not recovery it's considered the master recovery Incase if the Android recovery fails or you flashed the wrong file to the wrong partition.
Winnower Amber said:
Do you have the unlock code bin file?
Click to expand...
Click to collapse
I don't
You'll need to give that information. Check the box, your serial number should be on it.
Does Android recovery work?
Winnower Amber said:
You'll need to give that information. Check the box, your serial number should be on it.
Click to expand...
Click to collapse
I threw the box away .. let me see if I can find it in my mail with oneplus
Winnower Amber said:
You'll need to give that information. Check the box, your serial number should be on it.
Click to expand...
Click to collapse
The only thing I have from my mail with oneplus is the IMEI number from the form they made me fill in for the remote session only that later on they told me they don't have the files(msm) for my phone
If IMEI and serial number are the same let me know and I'll post thst here
The most you could do is get the unlock code bin. Then wait 7 days for a reply, flash your device with the TMobile msm, and then follow the TMobile to oem, that should do it.
If you need to reach me for stuff like this, I am available on discord via the xda,
Winnower Amber said:
Does Android recovery work?
Click to expand...
Click to collapse
From the screen itself. No it boots back to the error .. but I was able to get into recovery by pressing volume up and down
Winnower Amber said:
The most you could do is get the unlock code bin. Then wait 7 days for a reply, flash your device with the TMobile msm, and then follow the TMobile to oem, that should do it.
Click to expand...
Click to collapse
I have the fully paid variant.. so I don't need the unlock code... That's t-mobile.. my bootloader is locked or OEM is locked
Your phone comes preloaded with an emergency boot chip called Qualcomm download mode. Use the TMobile msm tool to flash your device back to factory, then you can essentially do what you need. To get back to oem.
I keep forgetting to quote reply I hate this lol.
Winnower Amber said:
Your phone comes preloaded with an emergency boot chip called Qualcomm download mode. Use the TMobile msm tool to flash your device back to factory, then you can essentially do what you need. To get back to oem.
Click to expand...
Click to collapse
My phone does not work with the MSM tool for TMobile... already tried that ( others already tried it so I'm not alone)