Question bricked nord 2 (dn2103) download not completed! - OnePlus Nord 2 5G

i just got this after updating my system and now it bootloops and getting this error everytime. is there any way to fix this?

What u done did you restored partition backup?

yes

Anyone has a tool or a stock rom to unbrick nord 2? No fastboot no twrp, please

venezolano69 said:
Anyone has a tool or a stock rom to unbrick nord 2? No fastboot no twrp, please
Click to expand...
Click to collapse
Use mtkclient with your proper backup

REDOTHELLO said:
Use mtkclient with your proper backup
Click to expand...
Click to collapse
I dont have backup and my phone goes only in EDL

Download backup from govix drive
Change extension boot.img to boot.bin then flash boot.bin with mtkclient after that you can access to fastboot mode

i tried to go in download mode and flash tool recognizes the phone but mrk client dont.
with mtk client im getting the same error all the time
[14:07:13]: Status: Waiting for PreLoader VCOM, please connect mobile
[14:07:14]: Status: Handshake failed, retrying...
[14:07:14]: Status: Handshake failed, retrying...
[14:07:15]: Status: Handshake failed, retrying...
[14:07:15]: Status: Handshake failed, retrying...
[14:07:15]: Status: Handshake failed, retrying...
[14:07:16]: Status: Handshake failed, retrying...
[14:07:16]: Status: Handshake failed, retrying...
[14:07:16]: Status: Handshake failed, retrying...
[14:07:17]: Status: Handshake failed, retrying...
[14:07:17]: Status: Handshake failed, retrying...
[14:07:17]: Please disconnect, start mtkclient and reconnect.

and also in cmd getting this:
DeviceClass
DeviceClass - [LIB]: ←[31mCouldn't get device configuration.←[0m
DeviceClass
DeviceClass - [LIB]: ←[31mCouldn't get device configuration.←[0m

i tried to flash the rom with flash tool but i get this error

Untzo said:
i tried to go in download mode and flash tool recognizes the phone but mrk client dont.
with mtk client im getting the same error all the time
[14:07:13]: Status: Waiting for PreLoader VCOM, please connect mobile
[14:07:14]: Status: Handshake failed, retrying...
[14:07:14]: Status: Handshake failed, retrying...
[14:07:15]: Status: Handshake failed, retrying...
[14:07:15]: Status: Handshake failed, retrying...
[14:07:15]: Status: Handshake failed, retrying...
[14:07:16]: Status: Handshake failed, retrying...
[14:07:16]: Status: Handshake failed, retrying...
[14:07:16]: Status: Handshake failed, retrying...
[14:07:17]: Status: Handshake failed, retrying...
[14:07:17]: Status: Handshake failed, retrying...
[14:07:17]: Please disconnect, start mtkclient and reconnect.
Click to expand...
Click to collapse
oof man, im sorry, i also had that problem, i just sent it to service center, they did the testpoint thing in the motherboard, if you want you can try, but i dont know the full proccess im sorry, the repair cost me 43 euros

Untzo said:
i just got this after updating my system and now it bootloops and getting this error everytime. is there any way to fix this?
Click to expand...
Click to collapse
You need a small file.called oneplus custom.bin .write that file will be ok.

Untzo said:
i just got this after updating my system and now it bootloops and getting this error everytime. is there any way to fix this?
Click to expand...
Click to collapse
Was the update done via OTA? Was the phone rooted or OS modified before installing the update?

Related

Trying to use Casual with rooted 4.1.2 on SCH-1605(note 2)

Im a noob and have been trying to use casual to unlock my bootloader. I have a rooted version of 4.1.2 flashed through odin on my SH-1605. Ive tried it twice now and it hasn't worked. This is what i am getting from casual. I had to shorten it quite a bit but i think i got the main error.
This is a tool which will root, unlock, and install a custom recovery on a Verizon Galaxy Note 2.
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Uploading PIT
PIT upload successful
Uploading BOOTLOADER
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: BOOTLOADER upload failed!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
[Heimdall Error Report] Detected:
Heimdall uncontinuable error; Script halted
[/Heimdall Error Report]
done
Script Complete
Any help would be appreciated!

Lenovo S60-a Sahara Error Through Qfil

i Have Lenovo S60-a when i upgrade it to 5.0 then it cause some problem
it load nothing i tried all combinition of button then i tried it through test point and it work it load Qualcomm HS-USB QDLoader 9008 and connected to my pc now when i try to flash it through QFil it give me error
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
And some time it give
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:System.Exception: Failed to send Firehose NOP to the phone.
at QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()
at QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)
Download Fail:FireHose Fail FireHose Fail
Finish Download

really sick of 50%can not verify error for unlock bootloader

hi all so I read through many many posts i am 100% clear on the procedures of unlocking bootloader so i got permission from unlocking already log in to i.mi.com already double checked both phone and the unlock tool is same mi account but i am still getting 50% stuck error, checked driver is udpated, anyone has any actual solution to this? I see many people unlock it with zero problem am i missing anything?
Had this problem for weeks.
Only thing that actually worked is to flash the developer rom, try, it will complete.
Then flash back to the stable rom, pain in the arse I know, but save your time and try it.
en.miui.com/download-299.html
Make sure that you are on the developer ROM .
And it took me 2-3 days more to unlock my phone after getting confirmation from Xiaomi. Wait for 2-3 days so that their server gets updated.
edhahaha said:
hi all so I read through many many posts i am 100% clear on the procedures of unlocking bootloader so i got permission from unlocking already log in to i.mi.com already double checked both phone and the unlock tool is same mi account but i am still getting 50% stuck error, checked driver is udpated, anyone has any actual solution to this? I see many people unlock it with zero problem am i missing anything?
Click to expand...
Click to collapse
What ROM do you have?
i was at chinese stable, i flashed to latest developer chinese, 6.10.20 , doesn't work, then tried 6.10.13, samething, and i waited 2-3 days already.
edhahaha said:
i was at chinese stable, i flashed to latest developer chinese, 6.10.20 , doesn't work, then tried 6.10.13, samething, and i waited 2-3 days already.
Click to expand...
Click to collapse
Did you tried with developer global ?
If don't work, try with developer global MIUI7 . Worked for me.
You must be signed into the MIUI account on your device that you are using on the unlock application also.
Here are the steps i followed
1. I was on global stable ROM, flashed global developer ROM
2. login with Mi Account Id, not email or mobile number on phone as well as the unlock tool
3. Now I'm able to unlock the bootloader
4. Install Stable rom again if needed, I flashed it and my bootloader remained unlocked
The thing is,
Maybe you can try to check the lock status as well,
Mine showing 50% error several times,
But when i do "fastboot oem device-info"
It said that the BL was unlocked already,
I dont know how, but it seems the unlock was actually went through even when it show error
You have to be on a developer ROM, chinese or global doesn't matter.
If you're currently on chinese stable, you can switch to chinese developer. But if you're on Global stable, you can only switch to Global developer.
Hello. I had the same problem and I assume you have checked every single guide out there as well. I got around it when I changed my computer and unlock using the new computer. Maybe you can try doing the same thing and use your friend's laptop to unlock BL. To make sure there's no computer issue make sure to install ADB and Fastboot driver and check if your computer can detect your device in Fastboot mode (there has to be a guide out there, try google). Cheers
Hi, I run into the same issue on win 10 and also installed the android sdk to get the drivers.
Device Mi5 Pro
Latest chinese dev 6.10.20 (MIUI8)
I can find the device with fastboot, however "fastboot getvars" fail all the times with the same error:
Code:
fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
Thus the mi unlocker tool runs into the same issues:
Code:
DEBUG <11:15:16.127,T:5796> : Initializing native downloader...
INFO <11:15:16.127,T:5796> : init resource C:\Users\ose\Downloads\MiFlashUnlock_1.1.0317.1_en\res\ language:en region:
ERROR <11:15:17.003,T:2000> : product: return:getvar:product FAILED (command write failed (Unknown error))
ERROR <11:15:17.648,T:2000> : soc-id: return:getvar:soc-id FAILED (command write failed (Unknown error))
ERROR <11:15:18.294,T:2000> : soc_id: return:getvar:soc_id FAILED (command write failed (Unknown error))
ERROR <11:15:18.993,T:2000> : board_version: return:getvar:board_version FAILED (command write failed (Unknown error))
ERROR <11:15:18.993,T:2000> : Can't identify device in fastboot mode.(num=0)
INFO <11:15:34.057,T:4264> : to login by name:XXX pwd:XXX sid:XXX verify:EMPTY sec_token:EMPTY
INFO <11:15:34.090,T:4264> : LoginStep1
DEBUG <11:15:37.791,T:4264> : OnAccountLoggedIn
DEBUG <11:15:43.173,T:4264> : OnNewServiceCookies
DEBUG <11:15:43.173,T:4264> : Login success and get user detail
INFO <11:15:49.223,T:2032> : status result: {
"applyStatus" : 2,
"code" : 0,
"description" : null,
"shouldApply" : true,
"uid" : 1554152998
}
DEBUG <11:15:49.223,T:2032> : unlock status: 2
DEBUG <11:15:49.223,T:2032> : should apply:true
INFO <11:15:53.357,T:5796> : connected
DEBUG <11:15:56.569,T:10612> : VerifyDeviceInfo
ERROR <11:15:57.230,T:10612> : product: return:getvar:product FAILED (command write failed (Unknown error))
ERROR <11:15:57.873,T:10612> : soc-id: return:getvar:soc-id FAILED (command write failed (Unknown error))
ERROR <11:15:58.516,T:10612> : soc_id: return:getvar:soc_id FAILED (command write failed (Unknown error))
ERROR <11:15:59.215,T:10612> : board_version: return:getvar:board_version FAILED (command write failed (Unknown error))
ERROR <11:15:59.215,T:10612> : Can't identify device in fastboot mode.(num=0)
WARNING<11:15:59.215,T:10612> : cannot get product info again
ERROR <11:18:15.927,T:2000> : product: return:getvar:product FAILED (command write failed (Unknown error))
ERROR <11:18:16.589,T:2000> : soc-id: return:getvar:soc-id FAILED (command write failed (Unknown error))
ERROR <11:18:17.233,T:2000> : soc_id: return:getvar:soc_id FAILED (command write failed (Unknown error))
ERROR <11:18:17.935,T:2000> : board_version: return:getvar:board_version FAILED (command write failed (Unknown error))
ERROR <11:18:17.936,T:2000> : Can't identify device in fastboot mode.(num=0)
ERROR <11:18:19.035,T:2000> : product: return:getvar:product FAILED (command write failed (Unknown error))
ERROR <11:18:19.677,T:2000> : soc-id: return:getvar:soc-id FAILED (command write failed (Unknown error))
ERROR <11:18:20.319,T:2000> : soc_id: return:getvar:soc_id FAILED (command write failed (Unknown error))
ERROR <11:18:21.025,T:2000> : board_version: return:getvar:board_version FAILED (command write failed (Unknown error))
ERROR <11:18:21.025,T:2000> : Can't identify device in fastboot mode.(num=0)
I also cannot go back to a Global stable/dev rom, using the updater.
Any advises?

Bricked Xperia XZ Premium

Hello guys, just looking for some help. I recently bricked my Xperia and have been unable to restore the stock firmware using either flashtools or newflasher. The bricking occured after I screwed up the rooting process and was trying to revert it back to the factory firmware.
Flashtools gets to about flashing system.15 and it stops responding or working at all, with newflasher I get this error.
- Extracting sparse chunk flash_session/system.015
- Uploading sparse chunk flash_session/system.015
download:063ff070
ERROR: TIMEOUT: failed with error code 997 as follows:
Overlapped I/O operation is in progress.
- Error write! Need nBytes: 0x1ff070 but done: 0x0
nBytes[0x0]:
Error uploading chunk 50!
ERROR: TIMEOUT: failed with error code 997 as follows:
Overlapped I/O operation is in progress.
- Error write! Need nBytes: 0x11 but done: 0x0
nBytes[0x0]:
Error writing command 'go out of flashmode'!
ERROR: TIMEOUT: failed with error code 997 as follows:
Overlapped I/O operation is in progress.
- Error write! Need nBytes: 0x4 but done: 0x0
nBytes[0x0]:
- Error writing command Sync!
Press any key to continue . . .
Phone Model: Sony Xperia XZ Premium (G8141)
F/W: Original Sony Oreo 47.1.A.12.179
Rooted and Boot Loader Unlocked
Any help would be much appreciated.

Problems with QFIL on NX907J

Hello,
I own Nubia M2 play (NX907J).I recently kinda bricked it, but I have QFIL files for it. I have installed all the necessary drivers for Qualcomm, changed the port to QDloader 9008. After I press download I have a problem with Sahara. Here it is:
2020-03-22 12:38:35.981 12:38:35: ERROR: function: is_ack_successful:1121 SAHARA_NAK_MEMORY_DEBUG_NOT_SUPPORTED
2020-03-22 12:38:35.982
2020-03-22 12:38:35.983 12:38:35: ERROR: function: sahara_start:895 Exiting abruptly
2020-03-22 12:38:35.984
2020-03-22 12:38:35.985 12:38:35: ERROR: function: sahara_main:924 Sahara protocol error
2020-03-22 12:38:35.986
2020-03-22 12:38:35.986 12:38:35: ERROR: function: main:303 Uploading Image using Sahara protocol failed
2020-03-22 12:38:35.988
2020-03-22 12:38:35.989
2020-03-22 12:38:35.991 Download Fail:Sahara Fail:QSaharaServer Failrocess fail
2020-03-22 12:38:35.992 Finish Download
I have searched all over the internet for solutions but haven't found any. I have also tried switcing to DMSS ,but it didn't help ether. Is it a software problem or a hardware problem? I also added whole log to attachments.

Categories

Resources