I cant unlock my bootloader,i am trying to unlock bootloader with Test Point (S1 TOOL) and it says this:
DETACH USB CABLE FROM PHONE
REMOVE BATTERY FROM PHONE
ATTACH TESTPOINT
PRESS "READY", THEN ATTACH USB CABLE TO PHONE
PROCESSING ...
REMOVE TESTPOINT NOW, THEN PRESS "READY"
qcReceivePacket: can't get packet start.
Elapsed:56 secs.
PHONE INFO
__________________
RUNNING S1_EROM VER "R9B031"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0098/00B3"
LOADER VERSION: "R4A069"
MODEL (from GDFS): SK17i
SOFTWARE VERSION: 1244-7088_4.1.B.0.431
CUSTOM VERSION: 1249-7380_R1I
FILESYSTEM VERSION: WORLD-i_4.1.B.0.431
SERIAL NO: BX902WVUJR
SEMC SIMLOCK CERTIFICATE
Elapsed:20 secs.
__________________________
Bootloader unlock allowed:yes
Phone date 12w13, so it doesnt have new security ,right?
Please help me guys.
pulja9 said:
I cant unlock my bootloader,i am trying to unlock bootloader with Test Point (S1 TOOL) and it says this:
DETACH USB CABLE FROM PHONE
REMOVE BATTERY FROM PHONE
ATTACH TESTPOINT
PRESS "READY", THEN ATTACH USB CABLE TO PHONE
PROCESSING ...
REMOVE TESTPOINT NOW, THEN PRESS "READY"
qcReceivePacket: can't get packet start.
Elapsed:56 secs.
PHONE INFO
__________________
RUNNING S1_EROM VER "R9B031"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0098/00B3"
LOADER VERSION: "R4A069"
MODEL (from GDFS): SK17i
SOFTWARE VERSION: 1244-7088_4.1.B.0.431
CUSTOM VERSION: 1249-7380_R1I
FILESYSTEM VERSION: WORLD-i_4.1.B.0.431
SERIAL NO: BX902WVUJR
SEMC SIMLOCK CERTIFICATE
Elapsed:20 secs.
__________________________
Bootloader unlock allowed:yes
Phone date 12w13, so it doesnt have new security ,right?
Please help me guys.
Click to expand...
Click to collapse
It does, it is still unlockable.
Try the official Sony way, Mikhan pointed link in his unlocking tutorial: http://forum.xda-developers.com/showthread.php?p=31376248#post31376248
Related
I tried to update my phone by going to Cyanogenmod's Mirror network and updating to the newest version (crespo full 118 zip) but once I had "successfully" installed it, it got stuck on the google logo lock screen, so I took the battery out, and tried again with no luck.
On Fastboot mode, I tried all options, but cannot get past this logo/lock screen. I am using a Mac and am having a really hard time finding any information on step by step (got lost in a unzip/zip file explanation video) and really need help turning it back on and making sure I don't mess it up permanently!
Anyone? I would really appreciate it!
ANYbody? Please I'm starting to get desperate and I have continued trying to find a solution for the past 4 hours with no luck whatsoever! I don't understand, and would really be super grateful if someone could help me out!
QUICK UPDATE: I'm using a Mac and my computer doesn't seem to pick up any sign of the phone when I connect it with the USB cable.
When I get to the Fastboot mode page this is what I see:
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOODLOADER VERSION - I9020XXJK1
BOOTLADER BUILD - NOV 4 2010
BASEBAND VERSION - I9020XXJK8
SERIAL NUMBER - (my serial number)
LOCK STATE - UNLOCKED
.......please please please help!
selenag said:
QUICK UPDATE: I'm using a Mac and my computer doesn't seem to pick up any sign of the phone when I connect it with the USB cable.
When I get to the Fastboot mode page this is what I see:
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOODLOADER VERSION - I9020XXJK1
BOOTLADER BUILD - NOV 4 2010
BASEBAND VERSION - I9020XXJK8
SERIAL NUMBER - (my serial number)
LOCK STATE - UNLOCKED
.......please please please help!
Click to expand...
Click to collapse
Ok, don't panic
So, you're unlocked - that's good.
Verify that fastboot sees your device when connected in the boot loader (fastboot devices should list a serial)
If it does then reflash the appropriate recovery for your device
NS:http://mirror.sea.tdrevolution.net/cm/recoveries/recovery-clockwork-3.0.2.4-crespo.img
NS4G: http://mirror.sea.tdrevolution.net/cm/recoveries/recovery-clockwork-3.1.0.1-crespo4g.img
Download the image, put it in the same folder as fastboot (unless you've added it to your $PATH) and then run
Code:
fastboot flash recovery recovery-image-name-here.img
This is going to reflash the recovery image. At this point you should be able to reboot into recovery.
Once you are in recovery go ahead and reflash the CM7 build if you'd like or flash any other package (a full stock rom for example).
Thanks!! Got it
I flashed my stock. 2.1 Milestone (rooted) preparing it for froyo. Apparently the .sbf was corrupt or wrong;
GOT_TELUS_2_2_1FULL.sbf
I am told the correct sbf is;
BL_9078_GOOD_sholes_HS_Consumer_replacer.sbf\BL_90 78_umts_sholes_HS_Consumer_replacer.sbf.
- Now It’s stuck in bootloader mode
-RSD Lite seems to recognize phone but the “Start” button remains disabled, grey, it can’t be pushed (with either .sbf file.)
-I’ve loaded a fresh copy of RSD Lite v5.0 (previously had v4.7). Both behave the same; the start button is disabled.
I want to save this phone. I'm looking for alternative tools or methods to ultimately flash the proper .SBF…Help please!!!
BOOTLOADER SCREEN BELOW
PHP:
Bootloader
90.74
Err:A5,69,35,00,27
Battery OK
OK to Program
Transfer Mode:
USB
RSD LITE SCREEN BELOW
PHP:
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x009074
DRM Version: N / A
AP Die ID: 06a0010c60720304000000000400
BP Die ID: 0000000000000000000000000000
AP Public ID: 4bd4854c5cb58e173025f2751e09441b44fa681f
BP Public ID: 0000000000000000000000000000000000000000
-----------------------------------------------------------------------
Model Port No Port Type IMEI/ESN/MEID Status
S Flash OMAP3430 1 USB N/A connected
(I’ve successfully flashed my other Millstone an many other phones)
Any help is greatly appreciated,
PK
I cant unlock my bootloader,i am trying to unlock bootloader with Test Point (S1 TOOL) and it says this:
DETACH USB CABLE FROM PHONE
REMOVE BATTERY FROM PHONE
ATTACH TESTPOINT
PRESS "READY", THEN ATTACH USB CABLE TO PHONE
PROCESSING ...
REMOVE TESTPOINT NOW, THEN PRESS "READY"
qcReceivePacket: can't get packet start.
Elapsed:56 secs.
PHONE INFO
__________________
RUNNING S1_EROM VER "R9B031"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0098/00B3"
LOADER VERSION: "R4A069"
MODEL (from GDFS): SK17i
SOFTWARE VERSION: 1244-7088_4.1.B.0.431
CUSTOM VERSION: 1249-7380_R1I
FILESYSTEM VERSION: WORLD-i_4.1.B.0.431
SERIAL NO: BX902WVUJR
SEMC SIMLOCK CERTIFICATE
Elapsed:20 secs.
__________________________
Bootloader unlock allowed:yes
Phone date 12w13, so it doesnt have new security ,right?
Please help me guys.
Hello, as shared with the specific page https://forum.xda-developers.com/z2...d-xt1789-06-cheap-t4036047/page3#post83118467
my story is COMPLEX and now i have
-no usb debug mode (no adb)
-oem blocked blootloader
-cannot open unlock oem bootloader (because no usb debug mode)
-i have the LATEST ROM available (latest android 9)
-when i flash OFFICIAL LATEST ROM it takes it as "rollback" and refuse it (locked bootloader)
-i cannot flash NOTHING
- i only have bootloader
The motorola official tool cannot "match" / "recognize the type or whatnot and it wont help.
Motorola support refuse to help they told me its my fault ! (I did not do nothing to get to bootloop/bootloader).
Now i think i can solve it : by flashing any rom and opening bootloader without USB debug mode on.
How ? I want to BRICK IT !!! and in qualcomm mode 9008 i will flash the BLANKFLASH file (available).
Then OEM is unblocked, i will have ADB and flash WHATEVER rom i want in my xt1789-06 RETAIL (z2 force France).
My question here for this forum (general Q&A) : how do we BRICK a locked bootloader only access android smartphone? is there a magic command or process?
I tried unpluging in a middle of a flash rom but since flashing even latest official rom is blocked by bootloader => i cannot brick it.
Please tell me HOW to brick it, i take the risk ... i love this smartphone.
Thx.
you need an mtk tool like
https://droidbull.com/Android-multi-tools/
good luck
also
https://www.99mediasector.com/enable-usb-debugging-locked-phone-without-access-setting/
Hi guys, so I recently discovered you can use test point mode on my phone through DC Phoenix to then use HCU to unlock your bootloader and root and flash custom roms etc.
So after unlocking the bootloader which gave a success message. My phone proceeded to reboot into erecovery as there was some red text etc warning me about the system not being verified or trusted or something.
Now i started to download latest software to install through recovery but decided to stop it as i had already downloaded a firmware file 8.1 in full to flash. So i started that. And after flashing the erecovery files it rebooted me into upgrade mode (as it should) but it failed then after a few seconds and then the phone went black screen. I've now only got access to fastboot mode and nothing else. PC picks up the device in FB mode but cant issue any commands. They fail saying remote: failed. So I cannot flash any more files albeit system.img etc.
I have heard of the dload method but i cant seem to get it to work phone just doesnt boot up and start installing or anything.
Worth mentioning I have logs of everything i can post here.
The log from the "Successful" bootloader unlock via HCU: (it relocked after reboot) FRP too I think.
I have also replaced the endings of the imei listings etc with XXXX just as habit. I dont wanan post my IMEI etc online. Call it paranoia lol
25/01/2021 22:49:23
HCU Client v1.0.0.0372
Account: shortyzsly
Before operation turn phone to TestPoint mode:
Turn off phone, then short TestPoint on phone pcb
and plug USB cable
Wait for device "HUAWEI USB COM 1.0" in Ports
Read phone info
2021-01-25 22:49:23.140 Selected Cpu/Bootloader - Kirin970_T1_A8.1_V6
2021-01-25 22:49:23.142 Connecting to server...
2021-01-25 22:49:23.358 Connected!
2021-01-25 22:49:23.939 Find device COM3, handle 9956
BOOTLOADER selected to update:Kirin970_T1_A8.1_V6
2021-01-25 22:49:24.247 Downloading bootloader...
FILE TO download: Kirin970_T1_A8.1_V6_3.dtwork
downloading file Kirin970_T1_A8.1_V6_3.dtwork...
2021-01-25 22:49:26.501 Success
FILE TO download: Kirin970_T1_A8.1_V6_4.dtwork
downloading file Kirin970_T1_A8.1_V6_4.dtwork...
2021-01-25 22:49:27.671 Success
FILE TO download: Kirin970_T1_A8.1_V6_5.dtwork
downloading file Kirin970_T1_A8.1_V6_5.dtwork...
2021-01-25 22:50:22.279 Success
2021-01-25 22:50:22.286 Bootloader write success!
2021-01-25 22:50:22.288 Waiting for device REMOVAL/INSERTION...
2021-01-25 22:50:28.903 Device ready!
2021-01-25 22:50:28.983 Found device in fastboot mode!
2021-01-25 22:50:28.987 Reading info...
2021-01-25 22:50:33.024 Done!
Fastboot provided info:
CPU: kirin970
Model: CLT-L09
Firmware: CLT-L09 9.1.0.372(C782E12R1P11)
Vendor: hw
Country: eu
SN: LCL021XXXXXXXXX
PCB SN: 025DGTXXXXXX
WIFI MAC: 8811XXXXXX
BT MAC: 8811XXXXXXX
Theme color: black
Device color: black
FBLOCK: 1
Bootloader FB lock: unlocked
Bootloader User lock: locked
Found signed IMEI:
IMEI1: 867259XXXXXXXX
IMEI2: 867259XXXXXXXX
SIM NW_LOCK status: UNLOCKED
Found NV data:
Modems: 3
IMEI1: 86725XXXXXXXXX
IMEI2: 86725XXXXXXXXX
IMEI3: 000000000000000
PESN: 8022XXXX
MEID: A0000093XXXXX
Found OEM data:
Model: CLT-L09
Firmware: CLT-L09 9.0.0.168(C782E3R1P9)
Rescue: rescue:Chipset-boston 8.1.0.001(01FL)
Vendor: hw
Country: eu
Version limitation: ON
SIMCARDMODE: single
Bootloader User lock: locked
Click to expand...
Click to collapse
25/01/2021 22:52:35
HCU Client v1.0.0.0372
Account: shortyzsly
Before operation turn phone to TestPoint mode:
Turn off phone, then short TestPoint on phone pcb
and plug USB cable
Wait for device "HUAWEI USB COM 1.0" in Ports
Repair
New FB User Lock : UNLOCKED
New downgrade/customization limitations : UNLOCKED
Selected Cpu/Bootloader - Kirin970_T1_A8.1_V6
2021-01-25 22:52:36.442 Connecting to server...
2021-01-25 22:52:36.708 Connected!
2021-01-25 22:52:37.330 HUAWEI device in Test Point mode Not found!
2021-01-25 22:52:37.402 Reading info...
2021-01-25 22:52:41.275 Done!
Fastboot provided info:
CPU: kirin970
Model: CLT-L09
Firmware: CLT-L09 9.1.0.372(C782E12R1P11)
Vendor: hw
Country: eu
SN: LCL0218717XXXX
PCB SN: 025DGT187D00XXX
WIFI MAC: 88119XXXX
BT MAC: 8811966XXXX
Theme color: black
Device color: black
FBLOCK: 1
Bootloader FB lock: unlocked
Bootloader User lock: locked
Found signed IMEI:
IMEI1: 8672590XXXXX
IMEI2: 8672590XXXXX
SIM NW_LOCK status: UNLOCKED
Found NV data:
Modems: 3
IMEI1: 86725903XXXXXX
IMEI2: 867259035XXXXX
IMEI3: 000000000000000
PESN: 80221B5B
MEID: A00000934BCC82
Found OEM data:
Model: CLT-L09
Firmware: CLT-L09 9.0.0.168(C782E3R1P9)
Rescue: rescue:Chipset-boston 8.1.0.001(01FL)
Vendor: hw
Country: eu
Version limitation: ON
SIMCARDMODE: single
Bootloader User lock: locked
Phone ID: 80A0E6XXXXXXXX
2021-01-25 22:52:45.590 Repairing...
2021-01-25 22:52:45.598 Write FB User lock not supported for this model, skipped!
2021-01-25 22:52:45.611 Write partition oeminfo...
2021-01-25 22:52:47.468 Write partition oeminfo success!
2021-01-25 22:52:47.494 Unlocking restrictions...
2021-01-25 22:52:47.511 Unlock restrictions success!
2021-01-25 22:52:47.514 Done!
Click to expand...
Click to collapse
Basically what I wanna know is, is she dead and gone or can she be saved?
As it turns out, I think it may be an issue with the loader I may have tried to flash 8.1 and it was on 9.1. Any help when you get a chance anyone who's has the same issue. I searched the forums can't find my exact issue.