Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The device enters charging mode #99

Closed
ghost opened this issue Jul 15, 2024 · 1 comment
Closed

The device enters charging mode #99

ghost opened this issue Jul 15, 2024 · 1 comment

Comments

@ghost
Copy link

ghost commented Jul 15, 2024

I did the following steps:

• I ran unlock.bat

What happened: Saw that it was waiting for the device

• With the device turned off, I held VOLUME - and plugged in the USB Cable

What happened: the device connected to the PC as SPRD U2S Diag Mode, but it quickly disconnected and the device started charging

After that, unlock.bat shows "wrong mode or command detected, please reboot..." and no unlocking happens

(The same thing happens when I use the test points to enter Preloader mode)

PS: Using the "adb reboot autodloader" command to enter Preloader mode does not result in the same problem, the script starts to run, but in SPRD4/autoD mode, the unlock is not successful because After the first command, errors like "usb send failed (0/1)" start to appear

Device:
Motorola E13 using Alldocube Iplay 50 Mini (same board - Unisoc T606 ums9230) exploit

I know the exploit is device-based, but hey, In this xda post, they managed to unlock the Oukitel Wp23 (which doesn't have its exploit here) with the Alldocube Iplay 50 Mini exploit

https://xdaforums.com/t/oukitel-wp23-pro-unlocking-bootloader-rooting-gsi.4642483/

But well, if no Help is sent here or nothing improves for me as always is, I will simply remove all the screws from the back of the cell phone using the appropriate wrench and UNPLUG the battery from the board before running that unlock.bat, This is because SPRD Diag Mode works without battery and thus, the device does not start charging (This method has been used before in https://youtu.be/pSQ_aGYwdbQ?si=JNwyLTH0XAvttcbb)

After doing all that, I WILL PROVE (AGAIN) that

The exploit of another device works well on device with same board model (ums9230, for example)+flash memory type (ufs/emmc)

After proving this, I will go to Motorola E13 Group on Telegram and teach those dumb people that There's no point in trying exploits based on identifier tokens for an A13 and (mainly) Unisoc T606 device.

And finally, I will tell Motorola And Unisoc to go sh1t in the bushes!

Thanks everyone and salute to you, TomKing062.

May this post SERVE as an example and study for all those trying to unlock this device and may this be read in every classrooms across the planet. 🙏📿

@TomKing062
Copy link
Owner

TomKing062 commented Jul 15, 2024

3 type devices:
1 public key (alldocube/coolpad)
2 private key but not lock any register (ZTE, most tablet and some small OEM)
3 private key with different lock status (realme/hisense)

that register status in spl/fdl1 stage is dram init,in fdl2 it's pinmux

so yes type 1 and type 2 can use same files, but type 3 can't

another reason for spliting devices is the success rate is not 100%, the batch may overwrite(break) device's uboot/splloader backup in second run

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant