You can try by always this method. It worked for me a lot of times. WARNING! THIS METHOD IS ONLY WORKING FOR SIM UNLOCK!!
1- Download this HTC 2125 Offline Unlocker.zip to your PC
2- Unzip it! of course
3- Sync your device with activesync
4- MANUALLY COPY THE CERT.CAB TO YOUR 2125 AND INSTAL IT FROM YOUR DEVICE
5- Restart your device and sync with activesync
6- Run file named "Autounlock.bat" and just follow the instructions.
7- (ONLY FOR CID UNLOCK)Phone will reboot. then you have to hard reset. cuz some winmo files are gonna lost.
After its work is done, your device will reboot. Now you are ready for going in any services
I hope help you and to anyone!!!
thanks! May i just try
Crowleycator said:
You can try by always this method. It worked for me a lot of times. WARNING! THIS METHOD IS ONLY WORKING FOR SIM UNLOCK!!
1- Download this HTC 2125 Offline Unlocker.zip to your PC
2- Unzip it! of course
3- Sync your device with activesync
4- MANUALLY COPY THE CERT.CAB TO YOUR 2125 AND INSTAL IT FROM YOUR DEVICE
5- Restart your device and sync with activesync
6- Run file named "Autounlock.bat" and just follow the instructions.
7- (ONLY FOR CID UNLOCK)Phone will reboot. then you have to hard reset. cuz some winmo files are gonna lost.
After its work is done, your device will reboot. Now you are ready for going in any services
I hope help you and to anyone!!!
Click to expand...
Click to collapse
Did someyone try Wizard Service Tool?
http://forum.xda-developers.com/showthread.php?t=329170
IMEI changing works on HTC Tornado (checked). Maybe SIM & CID unlock works too. My Tornado is unlocked, so a can't try it...
Edit:
Unfortunetly WST doesn't work witch tornado SIM & CID unlock. Use lokiwiz please!!
How did you get the WST operate on the Tornado? For my devices it always gives me the error:
Warning!
A device was detected but one (or both) of RAPI
Communications and Applications Policy isn't
enabled.
Use first button for that purpose and try again
Doing so will not change anything. I checked the stuff that the Cabs are doing to the security policies and applied them manually - but no way is WST working. Also copying files from one cab to the device does not work either.
Any hints to get it running?
tobbbie said:
How did you get the WST operate on the Tornado? For my devices it always gives me the error:
Warning!
A device was detected but one (or both) of RAPI
Communications and Applications Policy isn't
enabled.
Use first button for that purpose and try again
Doing so will not change anything. I checked the stuff that the Cabs are doing to the security policies and applied them manually - but no way is WST working. Also copying files from one cab to the device does not work either.
Any hints to get it running?
Click to expand...
Click to collapse
I think it's ROM problem. I used ROM cooked in your kitchen, but had the same situation. After upgrade to wm6.5 ROM (link in my signature) it works
It must be the problem with full app unlock in your ROM...
I think SGregory has completely patched away the signature checks in the nk.exe - no need to care about security policies then. Will see if that does the trick.
Try and share experiences. Maybe we'll have a new tool for CID/SIM unlock our Tornado
Soon I will have the opportunity to try this on SimLocked SPV C600. Describe here the results of tests
Well, why another tool - lokiwiz works perfectly for CID unlock and SIM unlock on the Tornado (and all older using the G3 chip). From S620 onwards things have changed and there are no free permanent unlock solutions.
You can use a Wizard Serwice Tool ONLY for IMEI change, but only for repair. SIM & CID unlock doesn't work with HTC Tornado!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I used this to unlock the CID and the SIM. When I put the SIM card in the phone wont work and it says "data crashes. Please contact your service center"
Any ideas on how to resolve this issue?
You have corrupted the "encrypted block". This block holds the SIM-Lock, CID-Lock and IMEI (+ other forensically relevant data I was told). If you have a backup of the encrypted block (lokiwiz does this) try to upload it back to the phone. If not you have to pay 10 pounds to http://imei-check.co.uk/c600_unlock.php - they can recover the encrypted block and deliver tooling to do it. The device is unlocked (CID and SIM) after the procedure. It worked for one of my devices where the same problem occurred.
tobbbie said:
I think SGregory has completely patched away the signature checks in the nk.exe - no need to care about security policies then. Will see if that does the trick.
Click to expand...
Click to collapse
Well, it does not. Using the autopatcher (on my WM6 ROM) it does not succeed. Will not check further as the lokiwiz works perfectly and it creates a backup in case things go wrong.
garywlafreniere said:
I used this to unlock the CID and the SIM. When I put the SIM card in the phone wont work and it says "data crashes. Please contact your service center"
Any ideas on how to resolve this issue?
Click to expand...
Click to collapse
Wizard Service Tool creates backup copy of encrypted block (SuperCID-ing, default setings), so you can restore it by lokiwiz02b
Thanks gtek85!
@gutek85: did you check that the WST backup is also just a 64kB binary copy, just like Lokiwiz does it? Can you give advice on what to do in renaming and copying for those who are not aware of the details?
Can you further tell what happens if you "unlock" with WST and then try to repeat it? This may happen for another device or the same.
Problem could be that the old "original" backup is overwritten with the "corrupted" one that WST has put to the device and which taken as the new "original" - hence making it impossible to ever get back!
-> this happens with lokiwiz tooling if you don't care to save the first backup immediately.
Just binary compare the "backup" you have with a "fresh made" backup from the corrupted block. If they are identical all the restore will not help you!
If you set SuperCID, using WST, it creates backup copy in .bin file, so you can use it in lokiwiz (I found my old one for C600 and now it works) But renameing from WST_..._CID.fls to locked.bin works to (checked)
If you want to restore your old CID-block, you have to modify (right mouse click => Edit) lokiwiz02b code, otherwise it doesn't write your backup file, just modify file readen from the phone and write it back. You have to delate bold line of code and save it to lokiwiz1.bat file in the same directory. If you're sure that your old locked.bin file is coppied to lokiwiz directory, then run lokiwiz1.bat file and press L.
...
:ItemB
ECHO Locking mobile... DO NOT DISCONNECT UNTIL THE PHONE REBOOTS!
Utils\pdocread.exe -n 1 0x000000 0x10000 -b 0x4000 lock_backup.bin
Utils\wizardunlock.exe lock_backup.bin -lock -w locked.bin
Utils\pdocwrite.exe -n 1 -b 0x4000 locked.bin 0x000000 0x010000
Utils\preboot.exe
ECHO Your phone is now locked....
ECHO Store the generated 'lock_backup.bin' file in a safe place. It can help to restore your device if anything goes wrong.
GOTO End
...
WST asks where to save backup copy file and it's named with date and time of creating, so it's almost impossible to overwrite it
Great, this will help many, I think
The batch file normally tries to SIM-Lock again your device, hence the line with the wizardunlock -lock that you do not need here as you only want to write back the original block. You can either delete the line in the batch file or make it not execute by prefixing it with two colons ::
It is really a life-saver that WST puts a timestamp to the backup file! Would be great to add something similar to the lokiwiz batch file. This would give it an extra safety.
garywlafreniere said:
I used this to unlock the CID and the SIM. When I put the SIM card in the phone wont work and it says "data crashes. Please contact your service center"
Any ideas on how to resolve this issue?
Click to expand...
Click to collapse
i have the same problem, havent found solution yet...
There are 3 solutions to this problem:
restore your encryted block from the backup that either WST or Lokiwiz are doing with Lokiwiz, steps described by gutek85.
Mind that WST only "works" when you have the WM6.5 ROM from Gregory installed - but it will not correctly do the job and corrupt the encrypted block for the Tornado. Luckily the created backup of the encrypted block can be be copied back to the device using the Lokiwiz tooling, see a few posts earlier in this thread.
use the WM6.5 ROM from gregory - it seems patched to skip the check on the encrypted block. So if you used WST on this ROM and played around you may have ended up with a corrupted block but you would not notice until you go to another ROM.
pay imei-check.uk 10GBP to reconstruct the encrypted block for you
I think, should remove WST from list of programs for Tornado SIMlock and CIDlock remowing. This causes too many problems. lokiwiz is enough
Related
HTCMAG_ROM_WWE_O3
My first ROM for HTC Magician.
Release date: 14.04.2009 18:24 GMT+3
Alternate name: 3.03 WWE.
Features:
*128 and 64 ram support
*USB RNDIS support.
*SDHighCapacity support (up to 8GB)
*SDIO expansion no longer supported.
*Error Reporting turned off.
*RDP programm added
*WModem is obsolete. Excluded.
*Something else
*Of course all features from HTCMAG_ROM_WWE_O2 - read info about it also!
Installation:
*YOU MUST HAVE 1.12 RADIO! IF NOT, INSTALL IT FIRST!!!
*Download archive
*Extract files from it
*Enter bootloader mode on device (Press POWER + CAMERA + RESET, you will see Serial/USB at top and 1.0X at bottom)
*Connect via USB to PC
*Run Update.exe
*Follow instructions in Update program.
*At the end you should see at device screen: "100% Upgrade OS Image Complete".
*After flashing press reset.
*Don't touch device, wait while "welcome screen" appear.
*Press screen, do calibration and start using device.
NOTE: This is ONLY ONE right instruction how to flash your device with my rom.
otherwise your device can no longer boots, also you can get brick. be sure, before doing anything wrong!
Uninstallation
*Enter bootloader mode on device (Press POWER + CAMERA + RESET, you will see Serial/USB at top and 1.0X at bottom)
*Connect via USB to PC
*Install ORIGINAL 1.12 or 1.13 ROM. No big storage etc. Install original one!!
[YOU *MUST* REPLACE ROMUpgradeUt.exe TO MaUpgradeUt_noID.exe]
*Now you can flash any other old custom roms.
NOTE: This is ONLY ONE right instruction how to uninstall my rom, otherwise you can have problems with new rom.
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can read more and download rom from my website.
You are flashing your device at your own risk.
I've tried all my ROMs on my own device and didn't find any problem.
I take no responsibility for any harm or damage to yourself, your device, computer or anything else.
Something works, something doesn't. Something is not supposed to work.
Something is supposed to work, but doesn't. Something should't work, but works.
Something should work, but doesn't;
Something should work from your point of view, but not from mine.
Something is not supposed to work, that's why it doesn't work.
By downloading and using this files, you agree with this statements.
This is private project, don't ask any details about development, also don't ask about future releases, I won't answer. Sorry.
Please don't send me Private Messages about this project, write in this thread instead.
Best regards,
-Cotulla
Thanks you upper king of magician roms. Looks very good.
Do you ever sleep?
[reserved]
Thanks~~~downloading
Gee.. 3rd version in 2 month for wimo 6.1, what a great job, thank you sir, you are trully magician...
good job man!
Simply one word : Superb
Cotulla said:
HTCMAG_ROM_WWE_O3
My first ROM for HTC Magician.
Release date: 14.04.2009 18:24 GMT+3
Alternate name: 3.03 WWE.
Features:
...
*SDIO expansion no longer supported.
...
Click to expand...
Click to collapse
So.. we're not going to be able to use SD wifi / wlan cards anymore???
Big thanks to Cotulla, it is so cool.
But sorry of one demand,can make a ROM use CHS language of this release, please?
many chinese user are looking forward to......
Hi Cotulla,
One little problem... my storage card is now named as "Mounted Volume". Since I have used sprite backup and restore from your 02 rom to 03 without the need for reinstalling applications, but the path name is new, all my programs are not working...
Is there a fast fix to the matter? (renaming "Mounted Volume" back to "Storage Card").
Many thanks in advanced.
Philip
Thanx Cotulla Great Work
philiplam said:
Hi Cotulla,
One little problem... my storage card is now named as "Mounted Volume". Since I have used sprite backup and restore from your 02 rom to 03 without the need for reinstalling applications, but the path name is new, all my programs are not working...
Is there a fast fix to the matter? (renaming "Mounted Volume" back to "Storage Card").
Many thanks in advanced.
Philip
Click to expand...
Click to collapse
Dear Cotulla,
Sorry for bothering, but even more strange this is: Before my sprite restore, this is named "Storage Card"... the name gets changed only after the restore...
Help...
Philip
philiplam said:
Hi Cotulla,
One little problem... my storage card is now named as "Mounted Volume". Since I have used sprite backup and restore from your 02 rom to 03 without the need for reinstalling applications, but the path name is new, all my programs are not working...
Is there a fast fix to the matter? (renaming "Mounted Volume" back to "Storage Card").
Many thanks in advanced.
Philip
Click to expand...
Click to collapse
Comes me again,ha ha
Just have a look at here:
HKLM\System\StorageManager\Profiles\SDMMC
"Folder"="Storage Card"
And then reboot.
If Cotulla have changed the mount point of SDCard,you can click another subitem under "Profiles" and find which Folder's name is "Mounted Volume",change it to "Storage Card".
I have developed an optimization tool for Cotulla's WM6 and it works well,but it is a software in Simplified Chinese language,do you want to try?
If #7 is true, it would be a huuugee mess...
If by sdio you really talk about that kind of cards used to get the old magician wifi then...please explain why?!
It worked just fine....
xiaojin1985 said:
Comes me again,ha ha
Just have a look at here:
HKLM\System\StorageManager\Profiles\SDMMC
"Folder"="Storage Card"
And then reboot.
If Cotulla have changed the mount point of SDCard,you can click another subitem under "Profiles" and find which Folder's name is "Mounted Volume",change it to "Storage Card".
I have developed an optimization tool for Cotulla's WM6 and it works well,but it is a software in Simplified Chinese language,do you want to try?
Click to expand...
Click to collapse
Dear XiaoJin,
Thanks for your info. Worked like a charm.
Another question for you today: my o2 won't be able to recognize by Windows XP (Unknown USB Device) after my sprite restore, so I can't sync. Is there another key I need to delete from the device?
I would love to test drive my optimization software, and also if you need any translating work I could do that for you too. I have done that previously for the Chinese famous software "infinite today". Though I doubt if you need any as I think your English is as good (bad) as mine anyways.
Regards,
Philip
Dear Cotulla,
Sorry for bothering, but even more strange this is: Before my sprite restore, this is named "Storage Card"... the name gets changed only after the restore...
Click to expand...
Click to collapse
YOU MUST NOT RESTORE BACKUPS FROM OTHER ROMs!!!!
You can restore only PIM data(Contacts, Calendar, Messagess).
If you restore backup from old rom, you get a mixed sh#t - a half of old rom and a half of new rom, this can cause a lot of bugs and etc.
If people continue ignore this rule, I will include protection engine in future ROMs.
why would u remove sdio support?
how else can we get wifi on the magicin than through sdio wifi card?
pls confirm if this new rom doesnt support wifi cards.
thanks
does this version use less memory space?
Radio version
Hi everyone,
i'm using CHT Rom (OS 1.11.06 / ExtROM 1.11.902 / Radio 1.11 / traditional chinese) and the radio version is 1.11, while i have to have 1.12 version in order to install this WM6.1 ROM.
How can i upgrade my radio version to 1.12?
and for the uninstallation problem, the read me said that (Install ORIGINAL 1.12 or 1.13 ROM. No big storage etc. Install original one!!) but the CHT ROM is 1.11, so if i install this WM6.1 ROM, i won't be able to install other ROM? Thx
Dear Cotulla,
Will you release the CHT version of this ROM? Thx
Hi man
thanks for your great job and for your time keep on the good work
on testing....
Bluetooth in Setting\System folder
I just finished with 03 ROM installtion but I can't sync and it seem like the bluetooth icon in the setting\system (normally there, this is the place where you normally check the outgoing/incoming port 4 &5) is not there anymore or I missing something? Those are the 2 issues I have. Anybody having these problems?
My phone is S110 and I was able to run fine with 02 ROM.
Back to checking the new ROM...again many thanks Cotulla!!!
Updated: I got the (USB cable) sync problem fixed by uninstall and reinstall the activesync 4.5. But still can't get the bluetooth sync to work so I can't sync via bluetooth as an option so I can browse the web inside my house. My bluetooth headset works OK.. just the bluetooth icon normally in the setting\system folder is not there anymore :-( so I can't setup sync via bluetooth. BTW the SDHC work great on my 4GB Kingston SDHC
Mike8010
no SDIO Wlan cards? So we have a choice between sdhc and sdio am I wrong?
OK, after 3 hours investigation, I stopped trying.
My Phone is a Singapore HTC dream(SingTel), with version:
Model Number: HTC Dream
Firmware version: 1.1
Baseband version: 62.33.20.08U_1.22.14.11
Kernel version: 2.6.25-01845-g85d4f0d [email protected] #27
Build number: dream_stg-user 1.1 STG-RC8 128394 ota-relkeys,release-keys
I have tried:
- Format SD(the default 1GB Transcend micro sdcard) to Fat32, both on Mac OSX leopard and Windows XP;
- copy the RC7 DREAIMG.nbh on the sdcard. (also tried different case combination, like DREAMIMG.NBH, DREAIMG.NBH; and tried the similar step using RC29)
- restart using Camera + POWER(with the USB connected, and without the USB connected)
- I saw the rainbow screen, after 1~2 seconds, I saw message "loading", then "checking", then get 2 messages in red: "00028002", "Not Allow"
I've checked thru nearly all the related posts here, and Google. It seems that I am the only fool who face this problem...I hope this is stupid problem that could be easily fixed by a small typo...
Any one experience same issue and overcome successfully? I just want to upgrade to Cupcake 1.5 and get stopped at the very first step...
you cannot do so because that RC29 is for US G1s.. Read the thread on the Singapore user group for the specific step by step instruction for you to get root access for your Singtel Dream.
http://www.codeandroid.org/forum/?wpforumaction=viewtopic&t=9.2
u can check the latesr comment in this post. i followed this guide, and running on ADP1.5Hr3 now
http://www.codeandroid.org/forum/?wpforumaction=viewtopic&t=9.2
Thanks chuazy and sencorde. I am trying that solution now.
Read this thread: http://forum.xda-developers.com/showthread.php?t=485364
The Transcend 1GB microSD card that comes with the SingTel Dream is crappy. I couldn't write the goldcard.img onto the card without making it unreadable and requiring a format again. It seems that many SingTel Dream users seeking to root their phone faced this issue (see hazeline's post). Everything went without a hitch once I tried the procedures stated in the above thread with a new microSD card (Kingston 4GB Class 4, S$19.90).
ok, I stopped here...Will go to buy a Kingston microSD tmr...
My the other side question is, why is so crappy to downgrade a Singapore based HTC dream? it seems that (in this forum) the US/UK based phone can skip this 27 steps approach to make a downgrade and get rooted...
It is because there are no previous firmware versions of the Singtel build that you can recover to, and they are not rooted. Previous firmware of US and UK G1 are rooted (anything before UK RC8 and US RC30) so you can go into recovery mode and recover previous rooted firmware for that region (and then do whatever you want with it).
wonder if anyone in SG provide rooting service , me is a noob lol
dom't mind paying a norminal sum
kaninabu said:
Read this thread: http://forum.xda-developers.com/showthread.php?t=485364
The Transcend 1GB microSD card that comes with the SingTel Dream is crappy. I couldn't write the goldcard.img onto the card without making it unreadable and requiring a format again. It seems that many SingTel Dream users seeking to root their phone faced this issue (see hazeline's post). Everything went without a hitch once I tried the procedures stated in the above thread with a new microSD card (Kingston 4GB Class 4, S$19.90).
Click to expand...
Click to collapse
Hi I used the Transcend 1GB microSD card that comes with the SingTel Dream to root my phone, no issue at all.
mechiland said:
ok, I stopped here...Will go to buy a Kingston microSD tmr...
My the other side question is, why is so crappy to downgrade a Singapore based HTC dream? it seems that (in this forum) the US/UK based phone can skip this 27 steps approach to make a downgrade and get rooted...
Click to expand...
Click to collapse
Hi, when i first started to root my Singtel set, I had faced the same issue as yours. It took me 3 days to figure out whats wrong. AT first I suspected the sdcard but I was wrong. Make sure u following the "27 steps approach" from http://www.codeandroid.org/forum/?wpforumaction=viewtopic&t=9.2. The goldcard procedure etc... Its important.
An extra point to take note which is not stated is to copy the DREAMIMG-RC7.zip to your sdcard and extract the file from your sdcard to your sdcard.
Hopes the above helps. If not I will try my very best to help u again. Do let us know your results. GOOD Luck and have fun
mechiland, I'm facing the same issue. I'll try the 27 steps tonight when I get home, and post results.
OK, let's take a breath. a deep breath.
IT WORKS! IT WORKS! IT WORKS!
IT WORKS WITHOUT A NEW microSD CARD AND JUST USE THE OLD 1GB Trancent!
Thanks everyone give the warm-hearted help...we SingTel HTC users are not alone.
I exactly followed the 27 steps tutorial this morning for the last time before I went to e-market. And suddenly everything went so smoothly.
One tip I can share:
It's kind of tricky that to get the CID using the terminal, and manually write down the 32 characters is error prone. If you like me, have the latest Android SDK installed, you can use adb shell to get the CID:
Code:
// make sure that the devices is connected (Check USB Debug option on your HTC Dream)
$ adb devices
List of devices attached
HT92DKV01647 device
// go to shell
$adb shell
$cd /sys/class/mmc_host/mmc1
$ls
uevent
subsystem
device
power
mmc1:0002 // <-- you see
$cd mmc1:0002
$cat cid
1b534d303030303010b144ddde008cb8 // <-- it's your cid...
Just copy and paste the CID to QMAT(Thanks), and follow the steps from 4.
will appreciate you guys thank pk for his detailed instructions for the singtel dream on http://www.codeandroid.org/forum/?wpforumaction=viewtopic&t=9.3 =)
pls post any of your tips/advise there, as that is the thread which most Singtel users referred to.
Disco_Stu said:
mechiland, I'm facing the same issue. I'll try the 27 steps tonight when I get home, and post results.
Click to expand...
Click to collapse
Tried, and worked
Cheers!!
YAY! more singtel users joining the hacking party XDXD. However i did not did an extra step in using my another 1gb micro sd brand.
What i did was get my cid code from terminal emulator, then i reversed it using the qmat trail programme and used the hex editor, reading from a windows mobile device did not work for me. I got stuck when downgraded to RC7 because i did nt have a data plan but stupidly i went to activate my data plan in the middle of the night and waste money but thanks to xda community there is a method to skip over the registration.
step 3 i already got problem, might need to get need memory card to try again
No luck
ok, so I tried this process. Didn't get any errors, but still get the 'not allow' message when I try to reboot and downgrade to RC7. Any ideas what might be going wrong? I have an Aust Optus Dream with RC8.
After copy and pasting the info from goldcard.img, I have to reformat my card. Is this undoing the copy?
Thanks
Greg
gjlamb said:
ok, so I tried this process. Didn't get any errors, but still get the 'not allow' message when I try to reboot and downgrade to RC7. Any ideas what might be going wrong? I have an Aust Optus Dream with RC8.
After copy and pasting the info from goldcard.img, I have to reformat my card. Is this undoing the copy?
Thanks
Greg
Click to expand...
Click to collapse
Hi,
I didn't use the original 1GB card that came with the set, the gold card method doesn't seem to work on that, I bought a new 4GB and it works like a charm, running Ravenge R7 now. If after copying the goldcard.img on it, and you are asked to format the card, it means the card cannot be used to convert to a gold card or you had the steps in converting that card wrong (yes the numerous numbers and alphabets got me the first time too)...
gjlamb said:
ok, so I tried this process. Didn't get any errors, but still get the 'not allow' message when I try to reboot and downgrade to RC7. Any ideas what might be going wrong? I have an Aust Optus Dream with RC8.
After copy and pasting the info from goldcard.img, I have to reformat my card. Is this undoing the copy?
Thanks
Greg
Click to expand...
Click to collapse
Foramtting the card means it's wiping it and re-writing the filesystem, so it will delete everything on the card.
Unique problem on rogers HTC dream
Guys
here is the story,
-> i got rogers HTC dream
-> used DREAIMG.NBH to downgrade to RC29, it went smoothly
-> i did factory reset
-> it wont boots up, stucks at G1 screen
-> i pressed CAMERA+POWER button and i got
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but instead of DREA100 or 110 i got DREA210 (which is for rogers)
-> i formatted card to FAT32
-> loaded again DREAIMG.NBH
-> go to boot mode
-> it says "Not Allow 00028002 Error"
-> i asked big dad (google), n i found that itz carrier ID (CID) mismatch
-> as there is no LEAK of DREAIMG.NBH for canada (rogers), hw can i make my DREAM work??
-> i tried gold card method but same thing
-> i tried DREADIAG.NBH but same thing
-> how can i communicate with my HTC dream through USB cable?? i have original stock SPL of G1...
any ideas??
Thankssssssssss in advance..
Stock firmware
Rogers B05 Firmware
https://www.androidfilehost.com/?fid=1395089523397891291
Separate Firehose download
https://www.androidfilehost.com/?fid=1395089523397891292
ZTE Kernel source mirror (We are codenamed Helen)
https://www.androidfilehost.com/?fid=1395089523397891289
Here is a step by step guide on how to flash the stock rom with QFIL and by extension any image.
Download and install the Qualcomm drivers from here
Download the firmware from above
Extract the firmware to a folder that you can easily access them from like your desktop
Download and install QPST from here
Open the QFIL application (Find it in your start menu)
In the "Select Build Type" field select Flat Build
In the "Select Programmer" field navigate to the folder you extracted the firmware and support files to and select the prog_emmc_firehose_8909.mbn file
Select the "Load XML" button and navigate to the folder you extracted the firmware and support files to and select the rawprogram0.xml and then the patch0.xml when prompted.
Plug in your tablet
Run the following adb command "adb reboot edl" (Now the screen should be blank but the led light should be red)
If the text at the top of the QFIL application says "No Port Available" click the "Select Port..." option and pick your device. If your device isn't showing up there you didn't install the drivers properly.
Click the Download Button to begin flashing your device
So the above explains how to flash everything if you want to flash just boot or recovery use the tool in the 2nd post it is a lot easier
Warning
This is a dangerous tool. It can render your device permanently unusable. If you use it, your warranty will likely be void. You accept all responsibility for the consequences.
Acknowledgments
Special thanks to @tdm for taking the firehose I got and creating the k81tool with it!
Note Well
The first rule of intelligent tinkering is to save all the parts.
Always backup your partitions before writing new contents, so that you can get back to where you started.
Never write both boot and recovery in one session. Always make sure that you can boot into the other partition in case something fails.
Preparation
Download magisks patched boot.img from here.
Download k81tool from here.
Setup your computer.
Setup for Windows
Download zadig.
Boot your device in EDL mode (see below).
Windows will want to install the Qualcomm USB driver. We won't be using it so cancel.
Run zadig. Find device 05c6:9008 and install the WinUSB driver for it.
Reboot your device and rerun steps to go back to EDL mode
Booting in EDL mode
Code:
adb reboot edl
Usage
Code:
k81tool.exe <read|write> <boot|recovery> <filename>
Example:
Code:
k81tool.exe read boot stock-boot.img
Code:
k81tool.exe write boot patched_boot.img
Multiple Operations
This is a "one-shot" tool. After performing an operation, it will reset the device with a 5 second countdown. If you wish to perform multiple operations (eg. backup, flash), simply re-enter EDL mode.
Common Problems
Device was not found
First enter EDL mode, then run the tool.
Device is visible in device manager but cannot be found by the tool.
Connect directly to the PC, not through a hub.
Windows says bad file descriptor
The WinUSB driver is not installed.
Once you flash the patched_boot.img all you need to do is install the magisks manager and you will have root enjoy!
Proof of root:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Place Holder for TWRP
bad links??
Hi
First, thank-you, thank-you, thank-you x 100. I've been looking for a method to root this device from the day I got it as an add on to my cell plan. Not sure if I am missing something but when I click on the androidfilehost links I get taken to a home page but there is no file to download for all three links. Initially I thought I might have to register so I did that but the links still just take you to the Home advert page Could you update the links when you get a chance - thanks !!
edit - I have a couple of questions -As you have been the first to root the device there are obviously no custom firmware builds available so we stick with stock, correct? We will be able to remove the bloatware on stock because it's rooted though, correct? I also use tasker and the AutoApps suite for automation and I need root for some of my tasks so this is a huge step in the right direction. Lastly in order to root the device do we need to do follow all steps in the first post and then complete the steps in the second post? Or is the second post just a different way to do what was done in post 1? I'm excited to root this so thanks for fixing those links! Thanks again for all your work.
ryanoc75 said:
Hi
First, thank-you, thank-you, thank-you x 100. I've been looking for a method to root this device from the day I got it as an add on to my cell plan. Not sure if I am missing something but when I click on the androidfilehost links I get taken to a home page but there is no file to download for all three links. Initially I thought I might have to register so I did that but the links still just take you to the Home advert page Could you update the links when you get a chance - thanks !!
Click to expand...
Click to collapse
Sorry about that somehow the links broke, I have updated them so now they are proper.
Hey guys. Having a little trouble. I keep on running into "Failed: unknown error" when I try to flash the patched boot.img that was provided. I managed to read the stock boot image with no problems, but writing just runs into this error.
Thoughts?
I am using the Bell variant so I hope that isn't the source of it
Post Root questions
Hi
I'm about to try to root the device, assuming it goes according to plan, can we then install SuperSU? Do we need a TWRP for the device if we want to install another ROM and are there generic ROMS out there that would work on this tablet? Sorry if these are noob questions, I've been an apple jailbreaker for years and just bought and rooted and installed a custom ROM on a Samsung Galaxy S4. I installed a new android tablet NAV in my BMW and I needed a device to act as a hotspot, so I use Tasker and AutoApps with it to automate the process and it works really well. When I rooted the Galaxy S4 there are a ton of ROMS available for every variant so it was easy to follow the instructions. However, this is totally new territory for me. This device isn't nearly as popular so I wondered what options are available to us once we have it rooted?
same issue failed unknown error
Hi
I am using the Rogers K81 and I am encountering the same failed unknown error when I try to write the patched boot file. I also was able to read the firmware file without issue. I rebooted into edl mode and then tried to write the patched file -
NB - for those who have yet to try, move the k81tool.exe and the patched boot file to your c drive and make sure your at the root of c and then remove the B05 in the patch file name so that it can find the file if you are just cutting and pasting the command line instructions above, otherwise you'll get an error that it can't find the file. If the k81tool.exe isn't in the current directory you are in you will get an error saying k81tool.exe is not a known command ..etc.etc. This might seem obvious to some but for those with little command line experience, it will save you from having to post questions about your errors.
There is a product ZTE primetime K92 which is a successor of a ZTE K81.
Do you plan to support root for ZTE Primetime K92?
huaji2333 said:
There is a product ZTE primetime K92 which is a successor of a ZTE K81.
Do you plan to support root for ZTE Primetime K92?
Click to expand...
Click to collapse
A friend of mine has the k92, and currently it has a locked bootloader even with the firehose and all. So he is working to find an exploit to allow it to be unlocked. But no ETA at this time.
Sent from my iPhone using Tapatalk
Thank you for providing this. I have the Virgin Mobile device currently. Just a question before I try this. My past experience with a tablet from Rogers a few years ago was that whenever you put a different sim card in, it would force you to reset the entire device. To get around this, I was lucky that there were other generic firmware available for that device. Does the Rogers firmware that you provide force a reset if you change the sim? I'd ideally like to have the option to change sims when traveling. Thanks.
I own a Virgin Mobile Canada ZTE K81 tablet. As much as I like a rooted device, my goal, if possible, is to replace the Bell firmware with the Rogers firmware. The reason I would want to do this is because Bell has done some nasty things with this tablet. The SIM card is IMEI locked to this tablet, I cannot use the SIM card on anything else. So I decided this tablet could be used as a wifi hotspot. Unfortunately, Bell did something to the firmware to make wifi and bluetooth tethering impossible.
I guess the other question I have is will the IMEI lock still work on this Bell tablet after the Rogers firmware is installed?
wow i didn't think development for this device would've gotten this far already. we're gonna need our own device forum soon
---------- Post added at 12:20 PM ---------- Previous post was at 12:19 PM ----------
bridonca said:
I own a Virgin Mobile Canada ZTE K81 tablet. As much as I like a rooted device, my goal, if possible, is to replace the Bell firmware with the Rogers firmware. The reason I would want to do this is because Bell has done some nasty things with this tablet. The SIM card is IMEI locked to this tablet, I cannot use the SIM card on anything else. So I decided this tablet could be used as a wifi hotspot. Unfortunately, Bell did something to the firmware to make wifi and bluetooth tethering impossible.
I guess the other question I have is will the IMEI lock still work on this Bell tablet after the Rogers firmware is installed?
Click to expand...
Click to collapse
imei locks are independent of the device itself. you need to get the carrier to give you an unlock code
Online Gravy said:
wow i didn't think development for this device would've gotten this far already. we're gonna need our own device forum soon
---------- Post added at 12:20 PM ---------- Previous post was at 12:19 PM ----------
imei locks are independent of the device itself. you need to get the carrier to give you an unlock code
Click to expand...
Click to collapse
I got Bell to IMEI lock the SIM to another, better tablet, a LG G Pad IV 8.0 FHD (LGV533) from Fido. The SIM works perfectly, I can now wifi tether!
That makes it an easier choice to hack at the Bell K81, now that the IMEI lock is not tied to this K81 tablet anymore. If the Bell K81 works with the Rogers firmware, bonus. If it bricks, not the end of the world. My data plan will still work. I just need to find the time to do the hack!
bridonca said:
I got Bell to IMEI lock the SIM to another, better tablet, a LG G Pad IV 8.0 FHD (LGV533) from Fido. The SIM works perfectly, I can now wifi tether!
That makes it an easier choice to hack at the Bell K81, now that the IMEI lock is not tied to this K81 tablet anymore. If the Bell K81 works with the Rogers firmware, bonus. If it bricks, not the end of the world. My data plan will still work. I just need to find the time to do the hack!
Click to expand...
Click to collapse
I have flashed my Bell k81 with Rogers firmware and it works properly.
Sent from my iPhone using Tapatalk
any chance of getting Pie GO installed on this thing, mine lags to even tap and the stock settings leave only 400mb free of ram
I can't successfully flash the rogers firmware on the VM (Bell) device. When the flashing process gets to 'reading through the sparse file' for the userdata.img file, I get an error. The log reads:
{ERROR: sparse_open:1939 Didn't properly read the sparse_header!
If I delete this file as a test (not sure if that was a good idea), it continues on to reading the ddr.img file, but halts again and the error refers to this file being 0 bytes.
I may have missed a step. When is the kernel file used? Is the Rogers firmware file complete?
s_021 said:
I can't successfully flash the rogers firmware on the VM (Bell) device. When the flashing process gets to 'reading through the sparse file' for the userdata.img file, I get an error. The log reads:
{ERROR: sparse_open:1939 Didn't properly read the sparse_header!
If I delete this file as a test (not sure if that was a good idea), it continues on to reading the ddr.img file, but halts again and the error refers to this file being 0 bytes.
I may have missed a step. When is the kernel file used? Is the Rogers firmware file complete?
Click to expand...
Click to collapse
Delete DDR as well and any of the ones it complains about that are empty. When I have sometime I'll upload a new package with those removed.
Decided to try the k81tool to just root instead, but I'm getting the same Failed:unknown error as others have posted.
(Using VM stock firmware)
---------- Post added at 11:20 PM ---------- Previous post was at 11:14 PM ----------
If you put in a Rogers sim, does it attempt to do a hard reset or just the usual reboot?
thanks
deadman96385 said:
I have flashed my Bell k81 with Rogers firmware and it works properly.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
deadman96385 said:
Delete DDR as well and any of the ones it complains about that are empty. When I have sometime I'll upload a new package with those removed.
Click to expand...
Click to collapse
Deleting the files also fails. The error is {ERROR: handleProgram:8615 'ddr.img' not found. You could possibly try --notfiles=ddr.img,OtherFileToSkip.bin (note, exiting since you specified --noprompt)
Adding back ddr.img, the error is
{ERROR: handleProgram:8666 Filesize is 0 bytes. This is usually a mistake!! Please check 'C:\ZTE\rogers\ddr.img'
Here is a rooting method for the Plam Phone either the US variant or the Vodafone variant this has not been tested or confirmed working on any other device. This root method may break in the future because it is using a tool that isn't designed for the public i tried getting the firehose packaged with the tool to work in other edl flashing tools but was not able to get it working. So this is all we have for now. There is minimal risk in doing this it just has a lot of steps and it requires a pc running windows.
Note: This will wipe your device so anything stored on it will be lost please backup anything important like photos/contacts/etc
Download and install Sugar QCT from here (Be sure to install the usb drivers as well)
Included in the zip is the username and password that you will need to use to run the program please do not post it here.
Boot the device into recovery by turning the device off and then holding the power button until it restarts 3-4 times and boots to recovery
Select the option to go into emergency download mode
Now plug the device into your computer and open Sugar QCT
From the list select pepito/PVG100 (US) or pepito_vdf (Vodafone)
Now select Upgrade this will download the palms firmware package and flash it to the device
When it finishes do not close sugar
Unplug your device and hold the power button for a few minutes so it will restart out of EDL mode, use a rubber band or something to apply pressure to it so you don't have to hold it
Go to where Sugar QCT is installed (C:\Program Files (x86)\SUGAR QCT_SP_Gotu2\bin\)
In there you should see a folder called PVG100-xxxx (The x's are your serial number)
Copy that to your desktop or anywhere else that you like
In the folder, there should be some random looking mbn files these are actually the firmware files just names are randomized to make using them harder.
There should be a file called B1AMD0D0CV00.mbn if not look for a file that starts with a B it will be the boot.img
You will need to push that to an android device and patch it with magisk manager.
Once that is done replace the B1AMD0D0CV00.mbn in your copy of the firmware with the patched boot.img
Boot it back into emergency download mode as previously stated
Close and reopen sugar
Copy your firmware copy back into C:\Program Files (x86)\SUGAR QCT_SP_Gotu2\bin\ be sure it is the same folder structure
Now select your model again and then press the upgrade button in sugar this will now flash your modified firmware to the device.
Once it finishes hold the power button for a few minutes so it will restart out of EDL mode, use a rubber band or something to apply pressure to it so you don't have to hold it
When it restarts and powers up then go through setting the phone up and install magisk manager and you're rooted.
Thanks to @StormSeeker1 for telling me about holding the power button for a few minutes to get out of EDL previously you had to let the phone die to get out of it which is a pain.
Interesting, shall do it tomorrow.
Curious, this doesn't use the root exploit discussed in other threads? Where is (7) downloading from?
snoopy20 said:
Interesting, shall do it tomorrow.
Curious, this doesn't use the root exploit discussed in other threads? Where is (7) downloading from?
Click to expand...
Click to collapse
It doesn't use any root exploit, it's downloading the firmware directly from TCL servers, the tool used is designed for service centers.
If they are the same hardware, it should be possible to flash Vodaphone over the top?
snoopy20 said:
If they are the same hardware, it should be possible to flash Vodaphone over the top?
Click to expand...
Click to collapse
They are signed with different keys, so it will probably cause the device to boot loop and or not startup. I would not recommend trying it.
Is it possible to dump the radio files from an network unlocked device, and use these files to unlock Verizon network.
Any other ideas to unlock network?
Current findings:
1. Remove the Verizon sim warning.
Simply edit the /vendor/build.prop and modify line "ro.product.vzw=true" to false. However, it has a side effect, causing the contacts in dailer FC while browsering.
2. Enable diag, serial and QMI
One method is dialing "###2324#", another approach is launching "EngineerMode" through apps like quickshortcutmaker, then navigate to Connectivity - DiagProtector.
3. Boot animation path
/Vendor/JRD_custres/media/
4. Most garbage apps path
/Vendor /priv-app/
Every time I try to replace the MBN files after being patched the utility keeps redownloading the originals. Any advice?
xswxm said:
Is it possible to dump the radio files from an network unlocked device, and use these files to unlock Verizon network.
Any other ideas to unlock network?
Current findings:
1. Remove the Verizon sim warning.
Simply edit the /vendor/build.prop and modify line "ro.product.vzw=true" to false. However, it has a side effect, causing the contacts in dailer FC while browsering.
2. Enable diag, serial and QMI
One method is dialing "###2324#", another approach is launching "EngineerMode" through apps like quickshortcutmaker, then navigate to Connectivity - DiagProtector.
3. Boot animation path
/Vendor/JRD_custres/media/
4. Most garbage apps path
/Vendor /priv-app/
Click to expand...
Click to collapse
I put my t-mobile sim into mine and it worked fine no edits needed and mine is officially locked to verizon.
kotaKat said:
Every time I try to replace the MBN files after being patched the utility keeps redownloading the originals. Any advice?
Click to expand...
Click to collapse
Are you postive that the folder structure is the same?
deadman96385 said:
I put my t-mobile sim into mine and it worked fine no edits needed and mine is officially locked to verizon.
Are you postive that the folder structure is the same?
Click to expand...
Click to collapse
I am using another carrier, not USA ones, and it has problems with 4G network.
it works, thanks
Just began mind. So far it's stuck on 2%.
Regarding flashing Vodaphone over Verizon, if the ROM files are signed with different keys then modifying the boot.img will surely break the signage?
snoopy20 said:
Just began mind. So far it's stuck on 2%.
Regarding flashing Vodaphone over Verizon, if the ROM files are signed with different keys then modifying the boot.img will surely break the signage?
Click to expand...
Click to collapse
Are you still stuck at 2%? Of downloading, or of flashing?
deadman96385 said:
I put my t-mobile sim into mine and it worked fine no edits needed and mine is officially locked to verizon.
Are you postive that the folder structure is the same?
Click to expand...
Click to collapse
tapa_t said:
Are you still stuck at 2%? Of downloading, or of flashing?
Click to expand...
Click to collapse
Tried flash pvg100e over pvg100, it will stuck at the beginning and the program won't flash.
xswxm said:
Tried flash pvg100e over pvg100, it will stuck at the beginning and the program won't flash.
Click to expand...
Click to collapse
Doesn't that empirically prove that different versions have different signatures, or at least ROM's are different enough to prevent switching over? Maybe we are just so lucky that boot.img is not checked as rigorously.
Is pvg100e for Vodafone? Where did you get the ROM if your device is pvg100?
Does it finish flashing if you do pvg100 over pvg100?
tapa_t said:
Doesn't that empirically prove that different versions have different signatures, or at least ROM's are different enough to prevent switching over? Maybe we are just so lucky that boot.img is not checked as rigorously.
Is pvg100e for Vodafone? Where did you get the ROM if your device is pvg100?
Does it finish flashing if you do pvg100 over pvg100?
Click to expand...
Click to collapse
The tool deadman provided definitely works if u follow the instruction and choose the right version.
For the signature issue, maybe u can find the answer in another thread about temporary root.
As to the version problems, pvg100 is for Verizon.
To my knowledge, the pvg100e is for many other vendors, such as Vodafone, and the UK version maybe share the same model name. There is another version pvg100eu, for European. U can find more evidence in the temporary root thread.
So far the following:
Windows 10 64 - goes to 2% then after a few seconds a 5002 error.
Windows 7 64 inside Virtualbox - goes to 2% and then doesn't move.
I've tried the drivers and others on the web although the latest is around 2014/15.
xswxm said:
The tool deadman provided definitely works if u follow the instruction and choose the right version.
For the signature issue, maybe u can find the answer in another thread about temporary root.
As to the version problems, pvg100 is for Verizon.
To my knowledge, the pvg100e is for many other vendors, such as Vodafone, and the UK version maybe share the same model name. There is another version pvg100eu, for European. U can find more evidence in the temporary root thread.
Click to expand...
Click to collapse
Checked last night, mine, pvg100, is snapdragon 430, and the China mainland version is pvg100c with snapdragon 435.
deadman96385 said:
It doesn't use any root exploit, it's downloading the firmware directly from TCL servers, the tool used is designed for service centers.
Click to expand...
Click to collapse
I'm not looking to root right now, but if I'm understanding this correctly this should mean that I can use SugarQCT to pull the latest version (1AMD) firmware for my Palm that doesn't show any OTA's available and is still on the original 1AGL firmware. Is that correct?
Thanks for making this happen, deadman96385!
tapa_t said:
Doesn't that empirically prove that different versions have different signatures, or at least ROM's are different enough to prevent switching over? Maybe we are just so lucky that boot.img is not checked as rigorously.
Click to expand...
Click to collapse
No need for empirical proof, I did the analysis here.
The difference is: the early part of boot is Qualcomm code using Qualcomm security. These are the "pbl", "sbl/edl" and "aboot/fastboot" programs (and also "modem", "tz" and other bits). These were the parts that I was looking at in the link above.
When "aboot" completes, it hands over to the late part of boot, which is Android code using Google security. These are the "boot.img/Linux kernel" programs, "recovery", "system", "vendor", "data", etc. They use a different security model. That's what this root method targets. You are correct when you say "Maybe we are just so lucky that boot.img is not checked as rigorously".
It does imply that you can mix the PVG100 Qualcomm partitions for "early boot" with the PVG100E Android partitions for "late boot" and vice-versa. But someone with motivation needs to test this... (No, you can't unlock cellular bands this way; the "modem" partition is from Qualcomm and must match your hardware.)
A good diagram is below; Source (and explanation): https://blog.quarkslab.com/analysis-of-qualcomm-secure-boot-chains.html -- I recommend studying this article.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ssuds said:
I'm not looking to root right now, but if I'm understanding this correctly this should mean that I can use SugarQCT to pull the latest version (1AMD) firmware for my Palm that doesn't show any OTA's available and is still on the original 1AGL firmware. Is that correct?
Click to expand...
Click to collapse
This should work. Keep in mind that whilst 1AMD seems to be fine, future versions may (permanently) close the vulnerabilities that allow you to get root, modify system partitions or use the current version of SugarQCT. I don't think this will happen but we should all keep the possibility in mind.
Which Windows version are people using? I've tried W10 and also W7 through a virtualbox but with the above errors.
This guide is the only one made and tested personally by me, I am not responsible for malfunctions or any damage to the device, carefully read every single step and everything will be successful
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[ATTENTION]: Before proceeding, save all your data on your computer and REMOVE ANY KIND OF UNLOCKING (sequence, pin, fingerprint etc ..); remove the sim and the microSD; get a microSD, at least 3/4 giga, where you can upload the files necessary for the procedure.
[NECESSARY CONDITIONS]: Starting from emui 8; have the cell phone charged to 100%; bootloader unlocked and the only procedure I know and working is the one I propose in the guide, the code is obtained by paying 4 €/$, THERE ARE NO FREE ALTERNATIVES.
[PREREQUISITES]: Download -> HiSuite , Dc-Unlocker
At this point we create a folder on the desktop and we will call it ANDROID1O to have a reference point and we will extract the folder contained in the dc-unlocker archive. Once the folder has been extracted, install adb and fastboot in order. At this point we can also install HiSuite.
[PROCEDURE]
[DOWNGRADE] In
order for dc-unlocker to read the bootloader code it is necessary to go back to an older version of android, so let's proceed as follows:
(1) We connect the mobile phone to the computer and start HiSuite, in some cases it will start automatically, and we follow the procedure that will be shown to us to enable debugging. If you have followed everything correctly HiSuite will read your device without problems.
(2) Remaining on HiSuite, click on the UPDATE SYSTEM item, a window will appear, at this point we can press on PREVIOUS VERSION (now I don't remember the precise wording) and we can start the downgrade. It will take a while.
(3) At the end of the downgrade we can start the mobile phone by skipping and ignoring the various configurations by putting the language in Italian as a matter of practicality, let's move on to the next step
[GET BOOTLOADER CODE]
(1) We go to the system settings ---> information ----> we do many taps until the message "now you are a developer" appears ----> we go back ----> developer options and activate usb debugging.
(2) Let's go to HiSuite and in the settings located at the top right we remove the check mark under "Start when it connects to the device" and close it.
(3) We buy the credits to read the bootloader code from https://www.dc-unlocker.com/buy in this way:
- We select the payment method
- We leave "new user account"
- We enter a username that we like it
- We enter an e-mail address to which we can easily access, here we will be sent the credentials to be able to access dc-ulocker
- We enter 4 in the credits box and then type on confirm
- If everything went well, the screen will appear with the credentials and you will receive a copy on the email
(We now have the necessary credits to be able to read the unlock code)
(4) Let's go back to the folder created on the desktop and start dc-unlocker and clicking on the SERVER item we enter the credentials obtained on the site
(5) At this point in the drop-down at the top left we look for the item HUAWEI PHONES
(6) A guide will appear that in any case I will report here:
- In the call keypad type the following combination * # * # 2846579 # * # *
- Press on MANUFACTURE MODE
(7) We can connect the mobile phone and press on the magnifying glass we see on dc-unlocker and if we have done everything correctly the program it will detect our mobile phone
(8) When the phone has been recognized we go to the UNLOCKING section and press on READ BOOTLOADER CODE, if we have done everything correctly we will get a code that we will enter somewhere so as not to lose it, we will need it later
(I leave you the video dc-unlocker official guide on how to unlock bootloader if you have any doubts ---> Help
(9) We disconnect the mobile phone from the computer
(10) After writing down the bootloader code we can close dc-unlocker, connect the mobile phone to a wifi network and search for system updates to return to the latest version of android and therefore to emui8,
if no updates appear, we try to force them by going to settings, wifi, press and hold on the wifi to which we are connected, modify, check advanced options, press on proxy, manual,
in proxy hostname we write localhost and in the port we write 8080 , we press on connect and if we return to the updates item it should find the most recent version. At this point we can update the mobile phone to the most recent version.
[BOOTLOADER UNLOCK]
(1) After returning to the most recent version of android we turn on the mobile phone
(2) We go to the system settings ---> information ----> do many taps until the message "you are now a developer "----> go back ----> developer options and activate the usb debug and the active voice unlock manufacturer
(3) We connect the mobile phone to the computer, press on transfer files, go back to the developer settings and activate the debug , at this point the mobile will ask us to give permissions to our computer and we confirm
(4) Let's go back to the desktop and at the top right click on file, open windows powershell, open windows poweshell as administrator and click on yes
(5) We type the command "adb devices" (write it without quotes), we wait for the end of the 'execution of the command and type again the command "adb devices" (without quotes)
and so we will see a number that corresponds to our mobile phone
(6) We give the command "adb reboot bootloader" (without quotes) and we send
(7) The mobile phone will start in a white screen with an android, the important thing is that two written in red appear with the words PHONE Unlocked and FRP Unlock
(8) From the Widows poweshell screen opened previously we give the command "fastboot oem unlock CODICEBOOTLOADER" (without quotation marks) (CODICEBOOTLOADER refers to the code obtained with Dc-Unlocker) and press on
enter (9) On the cellualre a warning will appear, press once the volume up key and then the power key to confirm the unlocking of the bootloader
(10) When the procedure is finished, it will take very little time, we give the command "fastboot reboot" (without quotes) and when the mobile phone screen it will go black we unplug it
(11) The cellualre will restart a couple of times with a white and other yellow writing, let it go, it will be returned to the factory settings and we will just have to skip all the configuration procedures but set the language in Italian
Finally the bootloader is unlocked!
Here's a free way https://github.com/SkyEmie/huawei-honor-unlock-bootloader
JanoRasho13 said:
Here's a free way https://github.com/SkyEmie/huawei-honor-unlock-bootloader
Click to expand...
Click to collapse
You try this?
pitrazzu said:
You try this?
Click to expand...
Click to collapse
I didn't, but a friend of mine with p20 lite succeeded unlocking!
JanoRasho13 said:
I didn't, but a friend of mine with p20 lite succeeded unlocking!
Click to expand...
Click to collapse
Knowing this sooner I would do it with this tool. Anyway good to knoe but I don't think I would stay with Huawei brand due to their anti-community mods policy.
DunoCZ said:
Knowing this sooner I would do it with this tool. Anyway good to knoe but I don't think I would stay with Huawei brand due to their anti-community mods policy.
Click to expand...
Click to collapse
Yes, absolutelly. Why you prevent me to mod my phone if the phone is mine?
Here is a free alternative to DC-UNLOCKER
I've unlocked the bootloader and installed TWRP on my wife's phone (emui 8 up to date dec 2020)
Here is the program : Potato NV
Follow these instructions : PotatoNV - wiki
To find where the testpoint is located search for pralx1 STF testpoint on your favourite internet search engine.
PS : By the way, the understanding of how it works goes way beyond my technical skills...
Junkilito said:
Here is a free alternative to DC-UNLOCKER
I've unlocked the bootloader and installed TWRP on my wife's phone (emui 8 up to date dec 2020)
Here is the program : Potato NV
Follow these instructions : PotatoNV - wiki
To find where the testpoint is located search for pralx1 STF testpoint on your favourite internet search engine.
PS : By the way, the understanding of how it works goes way beyond my technical skills...
Click to expand...
Click to collapse
And that means I no longer need to downgrade?
gabefufezan said:
And that means I no longer need to downgrade?
Click to expand...
Click to collapse
I didn't need to downgrade. I've just downgraded after the unlock via dload in order to install Android 11 Rom.
JanoRasho13 said:
Here's a free way https://github.com/SkyEmie/huawei-honor-unlock-bootloader
Click to expand...
Click to collapse
I want to try this way. Did it work for you guys?
This is supossed to happen, right?
gabefufezan said:
View attachment 5273573This is supossed to happen, right?
Click to expand...
Click to collapse
It's almost impossible to find it randomly. There are too many combinations...
If you read the issue section of this git, you'll see it by yourself.
Junkilito said:
It's almost impossible to find it randomly. There are too many combinations...
If you read the issue section of this git, you'll see it by yourself.
Click to expand...
Click to collapse
So that means the tool is unefficient?
gabefufezan said:
So that means the tool is unefficient?
Click to expand...
Click to collapse
I think so.
gabefufezan said:
So that means the tool is unefficient?
Click to expand...
Click to collapse
I tried but It didn't work. Unfortunately I had an aplhanumeric code despite that my device was european, and this made impossible the task to find the code ( it would take millions of years to do a minimum percentage of combinations ).
I found it using PotatoNV, it adds the difficult part to disassemble the phone but it is very efficient.
gabefufezan said:
View attachment 5273573This is supossed to happen, right?
Click to expand...
Click to collapse
It is not supposed to happen this way. You have to see something like "fastboot error: wrong password", so you're probably missing some permissions.
Anyway unless you have a numeric code there is virtually zero chance to find it in that way.
In my case I ran the script and in ~4 hours it tried all the numeric codes supposed to fit with my imei, but with no success. Later I discovered that my code was alphanumeric.
Hi everyone, I've just obtained te bootloader code, but now I'm stuck on EMUI 5.0.3, there are no updates available.
I tried forcing it but nothing changes..
On my P8 Lite 2017, I've tried the PotatoNV method which is, in fact, very easy (the most difficult part was to open the back cover, but with an opening tool it's easier) and no need to downgrade. For me the SkyEmie method was just a waste of time.
pitrazzu said:
(10) After writing down the bootloader code we can close dc-unlocker, connect the mobile phone to a wifi network and search for system updates to return to the latest version of android and therefore to emui8,
if no updates appear, we try to force them by going to settings, wifi, press and hold on the wifi to which we are connected, modify, check advanced options, press on proxy, manual,
in proxy hostname we write localhost and in the port we write 8080 , we press on connect and if we return to the updates item it should find the most recent version. At this point we can update the mobile phone to the most recent version.
Click to expand...
Click to collapse
Hello, i'm stuck at this step, i'm back at EMUI 5.0.3 and when i check for update it tells me "no updates"
Worked for me (PRA-LX1) !!
So easy, except from potatoNV (didn't try back panel is broken, as a result I cannot open my phone) all other free solutions have not worked for me.