Related
Hi guys!
Just recently I bought the "HDC Galaxy Note 2" off of fastcardtech. I got it a few days ago, am fairly pleased with it except for the slight miscalibrated touch screen. There are some apps on various markets aiming to fix this by re-applying new calibrations. The problem is that you'll have to be rooted in order to run them.
The phone comes with a built-in calibration setting, called "Als_ps calibration", which you can utizile to correct the sensor. Alas, it only corrects the phone's recognition of obstacles placed above it, so that you accidentaly wouldn't press any undesired button during a call.
Phone: http://www.fastcardtech.com/Galaxy-Note-2-Mega
Here's what I've done so far!
Enabled USB-debugging and installed USB-drivers. [MT65xx_USB_Driver.zip]
Tried the bin4ry root method, normal mode. [Root_with_Restore_by_Bin4ry_v18.zip]
This method:
http://forum.xda-developers.com/showthread.php?t=1886460
Everything works just fine until the phone reboots. Bin4ry is then unable to mount or copy the last files needed to apply root permission, see attached picture.
I have attached my specs in a screenshot, nevermind the quality, t'was done by another crap-camera! Sorry ;]
Any kind soul who can help me root this thing?
Edit:
Rooting this device has been made possible by GT35pro. See posts below.
same problem
KristN91 said:
Hi guys!
Just recently I bought the "HDC Galaxy Note 2" off of fastcardtech. I got it a few days ago, am fairly pleased with it except for the slight miscalibrated touch screen. There are some apps on various markets aiming to fix this by re-applying new calibrations. The problem is that you'll have to be rooted in order to run them.
The phone comes with a built-in calibration setting, called "Als_ps calibration", which you can utizile to correct the sensor. Alas, it only corrects the phone's recognition of obstacles placed above it, so that you accidentaly wouldn't press any undesired button during a call.
Phone: http://www.fastcardtech.com/Galaxy-Note-2-Mega
Here's what I've done so far!
Enabled USB-debugging and installed USB-drivers. [MT65xx_USB_Driver.zip]
Tried the bin4ry root method, normal mode. [Root_with_Restore_by_Bin4ry_v18.zip]
This method:
http://forum.xda-developers.com/showthread.php?t=1886460
Everything works just fine until the phone reboots. Bin4ry is then unable to mount or copy the last files needed to apply root permission, see attached picture.
I have attached my specs in a screenshot, nevermind the quality, t'was done by another crap-camera! Sorry ;]
Any kind soul who can help me root this thing?
Click to expand...
Click to collapse
omg i have the exact same problem, did you get a solution? PLEASE i need to root it so bad
CWM installed and rooted the HDC galaxy note 2 MAGE / MEGA
rebmoe said:
omg i have the exact same problem, did you get a solution? PLEASE i need to root it so bad
Click to expand...
Click to collapse
I just created the cwm recovery and root. The link is on my blog. The zip file is password protected so be sure to get it from my blog page.
http://gt35pro-mobile-gadgets.blogspot.sg/2013/02/cmw-recovery-english-and-root-for-hdc.html
After you have clockwork mod recovery, use it to flash the root access into the phone.
Have fun!
KristN91 said:
Hi guys!
Just recently I bought the "HDC Galaxy Note 2" off of fastcardtech. I got it a few days ago, am fairly pleased with it except for the slight miscalibrated touch screen. There are some apps on various markets aiming to fix this by re-applying new calibrations. The problem is that you'll have to be rooted in order to run them.
The phone comes with a built-in calibration setting, called "Als_ps calibration", which you can utizile to correct the sensor. Alas, it only corrects the phone's recognition of obstacles placed above it, so that you accidentaly wouldn't press any undesired button during a call.
Phone: http://www.fastcardtech.com/Galaxy-Note-2-Mega
Here's what I've done so far!
Enabled USB-debugging and installed USB-drivers. [MT65xx_USB_Driver.zip]
Tried the bin4ry root method, normal mode. [Root_with_Restore_by_Bin4ry_v18.zip]
This method:
http://forum.xda-developers.com/showthread.php?t=1886460
Everything works just fine until the phone reboots. Bin4ry is then unable to mount or copy the last files needed to apply root permission, see attached picture.
I have attached my specs in a screenshot, nevermind the quality, t'was done by another crap-camera! Sorry ;]
Any kind soul who can help me root this thing?
Click to expand...
Click to collapse
Kristen, where you able to re-calibrate after rooting; I just ordered this phone last week so I want to be prepared if need be.
londonflu said:
Kristen, where you able to re-calibrate after rooting; I just ordered this phone last week so I want to be prepared if need be.
Click to expand...
Click to collapse
The one I got did not have that screen calibration problem. Everything works good. Anyway, root is available now.
Superb!
Thank you for sorting this out!
-KristN91
Extra Guide
Follow the link provided by GT35pro in his first post.
To everyone attempting this flash;
!! First of all, copy the Superuser.zip to the root of your internal phone memory or external SD Card.!!
* Use a high-quality mini-USB cable (The one that comes with your phone should work just fine)
* Connect your MEGA to your pc, without the battery inserted.
(This device will connect and disconnect, when it's visible, be sure to grab it and follow the next step)
* Make sure that you have the right drivers for MTK65xx preloader "mtk65xx Vcom driver" and install them through the Device Manager.
* Insert your battery again, with the cable still connected, and install the second MTK65xx preloader.
* Disconnect phone from pc and remove the battery
* Start up Smart flash Tool and select the scatter file included in the package.
* Now, select and tick the checkbox for Recovery only. Smart Flash Tool will complain about the flash, due to it not containing all the appropriate files needed for a "secure boot". Nevermind that pop-up and proceed with downloading.
* Start Download
* Insert the battery and connect your phone to your pc, with that, the flashing should start.
* Boot Phone into recovery mode (pwr button and vol - or vol +) and install superuser from ZIP-file.
* After reboot you should be rooted.
///////////////
Fun Fact!
I actually managed to install a pre-rooted HDC S7100 rom on my MEGA.
The port isn't 100% accurate
-Invalid IMEI, this was fixed by Talkingmobile's guide; " how to write imei number for MTK 65XX " -Just google it!
-Auto-rotation is unavailable, no fix yet.
-Als_pl calibration is unavailable (resulting in active screen during call)
Besides that, the rom is arguably better than the MEGA's original N7100 rom, in terms of visual presentation.
Smooth transitions, vivid and vibrant colors would be a good example of aspects that would come out as improved over the original rom.
Interested in the S7100 rom? Just PM me and I'll provide the link.
Cheers!
S_ft_need_download_all_fail (4050)
I'm trying for several days, but always get this error in the flash tool: S_FT_NEED_DOWNLOAD_ALL_FAIL (4050)
Tried on Windows 7 x64, Windows 7 x32 and Windows XP SP3 (x32). Only on the Windows XP computer I was able to make a backup with Flash Tool using the Read Back option.
When I try to flash the red bar goes to 100% then the error message shows...
Does anyone get this error aswell, and did someone manage to solve this?
Please help, I'm in desperate need for root because I need touch screen calibration.
Thnx!!
YES! SUCCES!! I managed to root my HDC Mage :laugh: Did use another method though, check http://forum.xda-developers.com/showthread.php?t=2160490 if you are interested.
Anyway, now back to calibrating the touchscreen. What tools are good do fix touchscreen issues? I already tried http://forum.xda-developers.com/showthread.php?t=934500, but I still am not satisfied.
Thnx :good:
Just curious, if anyone that owns an HDC, is actually located in the USA?
londonflu said:
Just curious, if anyone that owns an HDC, is actually located in the USA?
Click to expand...
Click to collapse
Nope, the Netherlands. Why do you ask?
Sent from my GT-I9000 using xda app-developers app
jg77 said:
Nope, the Netherlands. Why do you ask?
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Because I tried to order 5 different phones from China including Fastcardtech; they couldn't ship for some reason; even got an empty box from ZOPO mobile. I ended up buying the BLU here in the US, I'm kind of glad it happened, since now I have an N'vidia Tegra 4 CPU, that runs circles around the dual-core phones.
I did order one more phone on ebay from China, been waiting for 2 weeks now. MAKES ME WONDER IF THEY EVEN ACTUALLY SHIP TO THE US AT ALL?
Thank to Paypal I was able to get refunded everytime.
KristN91 said:
Follow the link provided by GT35pro in his first post.
To everyone attempting this flash;
!! First of all, copy the Superuser.zip to the root of your internal phone memory or external SD Card.!!
* Use a high-quality mini-USB cable (The one that comes with your phone should work just fine)
* Connect your MEGA to your pc, without the battery inserted.
(This device will connect and disconnect, when it's visible, be sure to grab it and follow the next step)
* Make sure that you have the right drivers for MTK65xx preloader "mtk65xx Vcom driver" and install them through the Device Manager.
* Insert your battery again, with the cable still connected, and install the second MTK65xx preloader.
* Disconnect phone from pc and remove the battery
* Start up Smart flash Tool and select the scatter file included in the package.
* Now, select and tick the checkbox for Recovery only. Smart Flash Tool will complain about the flash, due to it not containing all the appropriate files needed for a "secure boot". Nevermind that pop-up and proceed with downloading.
* Start Download
* Insert the battery and connect your phone to your pc, with that, the flashing should start.
* Boot Phone into recovery mode (pwr button and vol - or vol +) and install superuser from ZIP-file.
* After reboot you should be rooted.
///////////////
Fun Fact!
I actually managed to install a pre-rooted HDC S7100 rom on my MEGA.
The port isn't 100% accurate
-Invalid IMEI, this was fixed by Talkingmobile's guide; " how to write imei number for MTK 65XX " -Just google it!
-Auto-rotation is unavailable, no fix yet.
-Als_pl calibration is unavailable (resulting in active screen during call)
Besides that, the rom is arguably better than the MEGA's original N7100 rom, in terms of visual presentation.
Smooth transitions, vivid and vibrant colors would be a good example of aspects that would come out as improved over the original rom.
Interested in the S7100 rom? Just PM me and I'll provide the link.
Cheers!
Click to expand...
Click to collapse
I took out the battery then connect it to the pc and open device manager, it show mtk65xx preloader then the phone disconnect its self and connect back every two seconds is there a way to fix this pls
thank you
I took out the battery then connect it to the pc and open device manager, it show mtk65xx preloader then the phone disconnect its self and connect back every two seconds is there a way to fix this pls
farazafs said:
I took out the battery then connect it to the pc and open device manager, it show mtk65xx preloader then the phone disconnect its self and connect back every two seconds is there a way to fix this pls
Click to expand...
Click to collapse
Did you install all necessary drivers?
Sent from my GT-I9000 using xda app-developers app
---------- Post added at 08:21 AM ---------- Previous post was at 08:17 AM ----------
farazafs said:
I took out the battery then connect it to the pc and open device manager, it show mtk65xx preloader then the phone disconnect its self and connect back every two seconds is there a way to fix this pls
Click to expand...
Click to collapse
Did you install all necessary drivers? How does sp flash tool respond when you download the recovery?
Sent from my GT-I9000 using xda app-developers app
jg77 said:
Did you install all necessary drivers?
Sent from my GT-I9000 using xda app-developers app
---------- Post added at 08:21 AM ---------- Previous post was at 08:17 AM ----------
Did you install all necessary drivers? How does sp flash tool respond when you download the recovery?
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
I can Install all necessary drivers, when I Power OFF phone and connect it to my PC, in device manager it can show MT65xx Preloader (Com 9) connected n within 3 sec it can be disconnected.... in SP Flash Tool i can select recovery then press download button... then again i can connect phone, it's give me some 80xx error. it's mean that device not connect.
farazafs said:
I can Install all necessary drivers, when I Power OFF phone and connect it to my PC, in device manager it can show MT65xx Preloader (Com 9) connected n within 3 sec it can be disconnected.... in SP Flash Tool i can select recovery then press download button... then again i can connect phone, it's give me some 80xx error. it's mean that device not connect.
Click to expand...
Click to collapse
An 80Xx error does not always mean device not connected. It can also mean there is something not right in the scatterfile (error 8038). You should take a look at the sp flash tool logfiles. You can post them here so I can have a look.
jg77 said:
An 80Xx error does not always mean device not connected. It can also mean there is something not right in the scatterfile (error 8038). You should take a look at the sp flash tool logfiles. You can post them here so I can have a look.
Click to expand...
Click to collapse
Attached snapshot given below... always when I tried to flash Recovery from SP Flash Tool it's only give me this error.
farazafs said:
Attached snapshot given below... always when I tried to flash Recovery from SP Flash Tool it's only give me this error.
Click to expand...
Click to collapse
There is something wrong in the layout of the scatterfile. Can you post the logiles of sp flash tool? Just zip them all together.
I have had the exactly the same error with my HDC Mage. I just had to rename a small section of the scatterfile and then it was all good.
I have a problem with the screen rotation sensor. after a few hours the sensor stops working. When i restart the device the sensor works again for a few hours.
I set up my device right after the purchase with the lineageos, with the stock rom I have not yet tested, but with superior os (9.0), I have the same problem. Does anyone have an idea how I could solve the problem? Is it possibly a hardware problem?
I have also tested with the firmwares 10.0.3, 10.0.9, 10.0.12 and 10.0.13.
Not exactly a hardware problem. I had the same issue on LineageOS and told the developer to look into the issue but he has abandoned the ROM so we're not gonna get a fix for that. Some Pie ROMs break the sensors of the device. This is not limited to the rotation sensor but also including the proximity sensor and some camera issues. I suggest flashing Oreo in EDL mode and then using another ROM like MIUI (in which everything works the way they should), if you are trusting the developers of that ROM. Cheers.
Thanks for your help. Miui is not an option for me. I operate my mobile without Google services, so Gapps must not be pre-installed. POSP v3.1 would be my first alternative to Lineageos, but I hope someone will develop it further.
Can you still help me how exactly I flash in EDL mode?
counti said:
Thanks for your help. Miui is not an option for me. I operate my mobile without Google services, so Gapps must not be pre-installed. POSP v3.1 would be my first alternative to Lineageos, but I hope someone will develop it further.
Can you still help me how exactly I flash in EDL mode?
Click to expand...
Click to collapse
Download and install MiFlash 20170425, Qualcomm Drivers, ADB drivers and platform tools.
Download stock fastboot images. Extract them in root drive (suck as D:/). Fastboot / EDL do not want folder names with spaces.
Put your phone into fastboot mode (by long pressing Pwr + vol- until Fastboot Mode logo appears)
Type in Command Prompt or PowerShell: fastboot oem edl
Phone will turn black and have blinking LED.
Open MiFlash. Locate the extracted fastboot images folder.
Click refresh. Should display S/N of your phone and its status.
Select 'clean all'. Do NOT select Clean + Lock, as it will lock bootloader or make things worse.
Start flashing by clicking flash button, and wait patiently.
When it display 'success', long press power until you can see 'Device Unlock' warning screen or AndroidOne splash screen.
And you're basically done EDL'ing phone.
counti said:
Thanks for your help. Miui is not an option for me. I operate my mobile without Google services, so Gapps must not be pre-installed. POSP v3.1 would be my first alternative to Lineageos, but I hope someone will develop it further.
Can you still help me how exactly I flash in EDL mode?
Click to expand...
Click to collapse
There are a lot of ROMs you can try. Most of them are more up to date compared to LineageOS. Superior OS, ViperOS, Resurrection Remix are your options. Can you tell me how did you de-googled your phone? Don't you have problems with GPS or other stuff without Google Services on your phone ?
thanks for your help, i'll try to do that in the next weeks
RFD80M-75679 said:
Download and install MiFlash 20170425, Qualcomm Drivers, ADB drivers and platform tools.
Download stock fastboot images. Extract them in root drive (suck as D:/). Fastboot / EDL do not want folder names with spaces.
Put your phone into fastboot mode (by long pressing Pwr + vol- until Fastboot Mode logo appears)
Type in Command Prompt or PowerShell: fastboot oem edl
Phone will turn black and have blinking LED.
Open MiFlash. Locate the extracted fastboot images folder.
Click refresh. Should display S/N of your phone and its status.
Select 'clean all'. Do NOT select Clean + Lock, as it will lock bootloader or make things worse.
Start flashing by clicking flash button, and wait patiently.
When it display 'success', long press power until you can see 'Device Unlock' warning screen or AndroidOne splash screen.
And you're basically done EDL'ing phone.
Click to expand...
Click to collapse
All I have done is not to install gapps
GPS runs without problems without Google services (I use osmand for navigation), Whatsapp I don't use, I have Threema, you can set polling.
Because the Google camera is much better than Open Camera or the standard camera from Lineageos I installed MicroG, so the Google camera works.
marstonpear said:
There are a lot of ROMs you can try. Most of them are more up to date compared to LineageOS. Superior OS, ViperOS, Resurrection Remix are your options. Can you tell me how did you de-googled your phone? Don't you have problems with GPS or other stuff without Google Services on your phone ?
Click to expand...
Click to collapse
Hello, a while ago I had this same problem, but I was successful because my cell phone got wet on the top (where I imagine all the sensors are). From there accelerometer, gyroscope, compass, proximity and light stopped working.
Yesterday I was trying to install DerpFest ROM and I did not succeed, I tried it more or less 15 times and threw myself into bootloop, so I reinstalled stock ROM Pie 10.0.16 and the sensors from nowhere started working again, but after a while, When charging, the device rebooted only 2 times. After such reboot I deactivated the sensors again.
I have tried to fix it by reinstalling Stock ROM and cleaning the system files through the TWRP "Repair" option, but it does not work.
Did anyone find any solution for this?
The solution for this problem is the kernel. The installation of POSP Rom solved the problem, probably because of the included kernel. Actually i have the lineageos rom with the butterfly kernel and it works also, without this kernel i had also this problem with lineageos.
Earlier this year i bricked a RN8P brought in by a customer to convert to global rom. After applying and waiting to unlock bootloader for 168 hours, it was successful then installing the global rom the device disconnected went into a total black screen no recovery, no fastboot just a white led when connected. after so many researches this forum and google there was nothing to write home about. i was frustrated and sad the only solution was to get someone with and authorization account which was $30 and couldn't afford. Customer was on my neck and was already talking of paying for the device then lo and behold today i was reading through some post on unbrick and i bumped into a solution i thought wasnt worth it as i have tried it buh never paid attention too. its a post by @white_3n on https://forum.xda-developers.com/redmi-note-8-pro/how-to/guide-unbrick-stuck-da-mode-authorised-t4000433/page5. here is it in details:
1- open phone (this aint necessary)
2- disconnect the battery (this aint necessary)
3- wait 10 seconds (this aint necessary)
4- connect the battery (this aint necessary)
5- Press and hold power and volume-
6- Plug to PC
7- Wait for the second vibration (longer).
8- Download MiFlash2018-5-28-0 https://mva2.androidfilehost.com/dl/l-WKOxk-I6mBdYiEVPDMUQ/1598950844/8889791610682902064/MiFlash20181115.zip?
9- Download https://mifirm.net/download/3520
10- Extracted the firmware as it comes in a .TGZ format
11- then open MiFlash2018-5-28-0
12- Click on refresh to be sure its on fastboot mode
13- then select and locate file you have extracted in 10
14- then select clean at the bottom right side of the MiFlash2018-5-28-0
15- Flash
Viola RN8P is back to life
The phone must have the bootloader unlocked?
Goatzilla47 said:
The phone must have the bootloader unlocked?
Click to expand...
Click to collapse
yes bootloader already unlocked before brick
Hello Mdutsu,
Are you saying that removing the battery and putting it back gave you access back to fastboot (power + volume-) ?
I'm in your situation, without access to fastboot and only EDL falshing seems to be an option, but I have to pay someone with an authorized account...
I'd like to confirm that as you void warranty by removing the back cover.
hi this just happen to me i try you're method but screen stay black and when i connect to computer i just hear the connect/disconnect sound and mi tools don't find the phone what can i do ?
I had the same exact issue a few days ago. follow the instructions on this video and it should get you back up and running. Worked like a charm for me. ask me if have any questions.
There is a youtube video that will show you how to fix it but i cant paste the URL because it adds the entire video. search this in youtube
How To Unbrick Redmi Note 8 Pro || Flash Stock Rom using SP Flash Tool 100% Working without Mi Auth
MidNight0780 said:
I had the same exact issue a few days ago. follow the instructions on this video and it should get you back up and running. Worked like a charm for me. ask me if have any questions.
There is a youtube video that will show you how to fix it but i cant paste the URL because it adds the entire video. search this in youtube
How To Unbrick Redmi Note 8 Pro || Flash Stock Rom using SP Flash Tool 100% Working without Mi Auth
Click to expand...
Click to collapse
This video saved me too!
Bro I created a new account here just to thank you, my RN8PRO gave up and you saved me. THANK YOU SO MUCH
Mdutsu said:
Earlier this year i bricked a RN8P brought in by a customer to convert to global rom. After applying and waiting to unlock bootloader for 168 hours, it was successful then installing the global rom the device disconnected went into a total black screen no recovery, no fastboot just a white led when connected. after so many researches this forum and google there was nothing to write home about. i was frustrated and sad the only solution was to get someone with and authorization account which was $30 and couldn't afford. Customer was on my neck and was already talking of paying for the device then lo and behold today i was reading through some post on unbrick and i bumped into a solution i thought wasnt worth it as i have tried it buh never paid attention too. its a post by @white_3n on https://forum.xda-developers.com/re...brick-stuck-da-mode-authorised-t4000433/page5. here is it in details:
1- open phone (this aint necessary)
2- disconnect the battery (this aint necessary)
3- wait 10 seconds (this aint necessary)
4- connect the battery (this aint necessary)
5- Press and hold power and volume-
6- Plug to PC
7- Wait for the second vibration (longer).
8- Download MiFlash2018-5-28-0 https://mva2.androidfilehost.com/dl...0844/8889791610682902064/MiFlash20181115.zip?
9- Download https://mifirm.net/download/3520
10- Extracted the firmware as it comes in a .TGZ format
11- then open MiFlash2018-5-28-0
12- Click on refresh to be sure its on fastboot mode
13- then select and locate file you have extracted in 10
14- then select clean at the bottom right side of the MiFlash2018-5-28-0
15- Flash
Viola RN8P is back to life
Click to expand...
Click to collapse
Hello,
So the good news is - apparently we can unlock Kirin 970 now. I did the hardware testpoint mode with the HCU Client and it worked just fine! I was replacing the battery anyway so I already had access to the motherboard. The question now is - what happened to LineageOS ROMs? Looks like they just deleted all of them.
Is there anybody out there with one of them on their HDD willing to share? Google cached website is showing two of them:
lineage-16.0-20210211-nightly-charlotte-signed.zip 2/11/21
lineage-16.0-20210204-nightly-charlotte-signed.zip 2/4/21
I'm gonna try to build a custom LineageOS 18.1 (Android 11) soon as well.
Thanks.
RafBB said:
Hello,
So the good news is - apparently we can unlock Kirin 970 now. I did the hardware testpoint mode with the HCU Client and it worked just fine! I was replacing the battery anyway so I already had access to the motherboard. The question now is - what happened to LineageOS ROMs? Looks like they just deleted all of them.
Is there anybody out there with one of them on their HDD willing to share? Google cached website is showing two of them:
lineage-16.0-20210211-nightly-charlotte-signed.zip 2/11/21
lineage-16.0-20210204-nightly-charlotte-signed.zip 2/4/21
I'm gonna try to build a custom LineageOS 18.1 (Android 11) soon as well.
Thanks.
Click to expand...
Click to collapse
Here you are
lineage-16.0-20210211-nightly-charlotte-signed.zip
drive.google.com
RafBB said:
Hello,
So the good news is - apparently we can unlock Kirin 970 now. I did the hardware testpoint mode with the HCU Client and it worked just fine! I was replacing the battery anyway so I already had access to the motherboard. The question now is - what happened to LineageOS ROMs? Looks like they just deleted all of them.
Is there anybody out there with one of them on their HDD willing to share? Google cached website is showing two of them:
lineage-16.0-20210211-nightly-charlotte-signed.zip 2/11/21
lineage-16.0-20210204-nightly-charlotte-signed.zip 2/4/21
I'm gonna try to build a custom LineageOS 18.1 (Android 11) soon as well.
Thanks.
Click to expand...
Click to collapse
Are you use EMUI 9.1 to unlock Bootloader ?
RafBB said:
Hello,
So the good news is - apparently we can unlock Kirin 970 now. I did the hardware testpoint mode with the HCU Client and it worked just fine! I was replacing the battery anyway so I already had access to the motherboard. The question now is - what happened to LineageOS ROMs? Looks like they just deleted all of them.
Is there anybody out there with one of them on their HDD willing to share? Google cached website is showing two of them:
lineage-16.0-20210211-nightly-charlotte-signed.zip 2/11/21
lineage-16.0-20210204-nightly-charlotte-signed.zip 2/4/21
I'm gonna try to build a custom LineageOS 18.1 (Android 11) soon as well.
Thanks.
Click to expand...
Click to collapse
Here is my p20 pro , can I unlock the Bootloader ?
ArthurTsai said:
Here you are
lineage-16.0-20210211-nightly-charlotte-signed.zip
drive.google.com
Click to expand...
Click to collapse
Awesome! Thanks a lot. I've found an UNOFFICIAL rom yesterday and flashed it, but looks like I'll be doing it all over again today with this one.
ArthurTsai said:
Are you use EMUI 9.1 to unlock Bootloader ?
Click to expand...
Click to collapse
Ok so here was the process:
1) Backed up all my data from the device (CLT-L29)
2) Factory reset the device
3) I used Huawei Hisuite software to rollback as far (BACK) as I could. It actually let me downgrade to EMUI 8.
4) Installed HCU and DC Phoenix (timed 72 hour license for both was like 20 euro)
5) Installed NECESSARY drivers on my Windows 10 machine (HUAWEI USB COM 1.0) for the testpoint
6) I opened the phone (I wanted to replace the battery anyway). Unscrew a couple of screws and take a shield to get to the pad.
7) With the phone completely off, short the testpad to ground (I used tweezers) and plug in the USB cable while still shorting out that pad. (USB cable that is connected to your Windows machine that is). Your phone screen will stay completely OFF, but you should hear an USB "ding" sound in you windows machine. Go to the device manager and check for HUAWEI USB COM 1.0 (Your Port). If you don't see it it won't work.
8) Fire up HCU Client, check account, select "Fastboot/XLoader (Hisilicon only)" on phone connection mode.
9) Go to the "Fastboot/Xloader" tab and select CPU (for me Kirin970_T2_A8.1_V5) worked fine.
10) Click Read phone info button, you'll see a progress bar on the bottom, it should take like 2 minutes
11) If everything went fine you'll see a log on the right with your unlock code in it
12) You can unlock it from that software, select "Bootloader lock: unlock", and "Write bootloader code" I also selected "Erase Huawei ID" and click "Repair" button. It will be quick. And that's it!
Now, flashing a custom ROM was a pain. Apparently most of them REQUIRE EMUI 9.0.0.159 (159 is the KEY!). You must get the original firmware and flash it with DC Phoenix. After that the process went something like this...
1) Put the phone in fastboot/rescue mode (hold the volume down button wile inserting USB cable with the phone off)
2) Flash TWRP for charlotte with fastboot from your PC
3) Restart phone into RECOVERY (TWRP) mode
4) Sideload your rom.ZIP file (Lineage for example)
5) Sideload google apps
6) Sideload factory camera app (honestly its the best for that phone)
7) Restart the bootloader (you will be in the fastboot mode again)
8) Upload the ORIGINAL recovery image (it wont boot if you dont do it) you can revert to TWRP after the first boot
9) Go into Huawei recovery mode (power+volume up)
10) Wipe/factory reset
11) Restart and you are done! (now you can flash TWRP again if you want)
It took me an entire day of work to figure it out. All the info (steps) is available online including the location of the test pad and disassembly of the phone. Here's an awesome guide to flashing Lineage (https://depl0y.com/posts/P20-Pro-LineageOS-Guide/). One thing I've noticed if you try to use HiSuite AFTER you unlocked your bootloader it WILL lock it again. I had to do it twice while I was trying to get EMUI 9.0.0.159. The best way was to use DC Phoenix and ROM from androidhost.ru.
Anyway after all that I now have an unlocked P20 Pro with stock android. It's bloatware free and runs great. So far no major issues with the ROM.
RafBB said:
Ok so here was the process:
1) Backed up all my data from the device (CLT-L29)
2) Factory reset the device
3) I used Huawei Hisuite software to rollback as far (BACK) as I could. It actually let me downgrade to EMUI 8.
4) Installed HCU and DC Phoenix (timed 72 hour license for both was like 20 euro)
5) Installed NECESSARY drivers on my Windows 10 machine (HUAWEI USB COM 1.0) for the testpoint
6) I opened the phone (I wanted to replace the battery anyway). Unscrew a couple of screws and take a shield to get to the pad.
7) With the phone completely off, short the testpad to ground (I used tweezers) and plug in the USB cable while still shorting out that pad. (USB cable that is connected to your Windows machine that is). Your phone screen will stay completely OFF, but you should hear an USB "ding" sound in you windows machine. Go to the device manager and check for HUAWEI USB COM 1.0 (Your Port). If you don't see it it won't work.
8) Fire up HCU Client, check account, select "Fastboot/XLoader (Hisilicon only)" on phone connection mode.
9) Go to the "Fastboot/Xloader" tab and select CPU (for me Kirin970_T2_A8.1_V5) worked fine.
10) Click Read phone info button, you'll see a progress bar on the bottom, it should take like 2 minutes
11) If everything went fine you'll see a log on the right with your unlock code in it
12) You can unlock it from that software, select "Bootloader lock: unlock", and "Write bootloader code" I also selected "Erase Huawei ID" and click "Repair" button. It will be quick. And that's it!
Now, flashing a custom ROM was a pain. Apparently most of them REQUIRE EMUI 9.0.0.159 (159 is the KEY!). You must get the original firmware and flash it with DC Phoenix. After that the process went something like this...
1) Put the phone in fastboot/rescue mode (hold the volume down button wile inserting USB cable with the phone off)
2) Flash TWRP for charlotte with fastboot from your PC
3) Restart phone into RECOVERY (TWRP) mode
4) Sideload your rom.ZIP file (Lineage for example)
5) Sideload google apps
6) Sideload factory camera app (honestly its the best for that phone)
7) Restart the bootloader (you will be in the fastboot mode again)
8) Upload the ORIGINAL recovery image (it wont boot if you dont do it) you can revert to TWRP after the first boot
9) Go into Huawei recovery mode (power+volume up)
10) Wipe/factory reset
11) Restart and you are done! (now you can flash TWRP again if you want)
It took me an entire day of work to figure it out. All the info (steps) is available online including the location of the test pad and disassembly of the phone. Here's an awesome guide to flashing Lineage (https://depl0y.com/posts/P20-Pro-LineageOS-Guide/). One thing I've noticed if you try to use HiSuite AFTER you unlocked your bootloader it WILL lock it again. I had to do it twice while I was trying to get EMUI 9.0.0.159. The best way was to use DC Phoenix and ROM from androidhost.ru.
Anyway after all that I now have an unlocked P20 Pro with stock android. It's bloatware free and runs great. So far no major issues with the ROM.
Click to expand...
Click to collapse
Things are not that simple. The HiSuite on Mac have been updated.
I can't find the button that can roll back or check for update after this.
Maybe I should try HiSuite on Windows.
I suddenly remembered that I cannot use HiSuite Windows version to roll back to EMUI 8 , but I can roll back to EMUI 9. Maybe I can roll back to EMUI 8 from EMUI 9. Needing roll back twice ?
ArthurTsai said:
I suddenly remembered that I cannot use HiSuite Windows version to roll back to EMUI 8 , but I can roll back to EMUI 9. Maybe I can roll back to EMUI 8 from EMUI 9. Needing roll back twice ?
Click to expand...
Click to collapse
You *should be able to unlock it with EMUI 9. I rolled it back to 8, just to find out later on I need 9.0.0.159 anyway. So I used HiSuite to update it to 9 - but it wasn't the version I wanted and also doing this in HiSuite removed my bootloader code, so I ended up using HCU Client on EMUI 9 and it worked just fine. After that I used DC Phoenix to flash the 9.0.0.159 (bootloader stayed unlocked). It was a pain, but yeah you SHOULD be able to unlock it with EMUI9.
ArthurTsai said:
I suddenly remembered that I cannot use HiSuite Windows version to roll back to EMUI 8 , but I can roll back to EMUI 9. Maybe I can roll back to EMUI 8 from EMUI 9. Needing roll back twice ?
Click to expand...
Click to collapse
Here's a log from unlocking 9.0.0.168...
Just to let you know that official ROM (lineage-16.0-20210211-nightly-charlotte-signed.zip) is not working on my P20 Pro. It crashes on the first boot. I'm back with (lineage-16.0-20190217_125340-UNOFFICIAL-charlotte.zip) I believe it was made made by LuK1337. Works great. I use it with open gapps pico version.
guys, this is p20 non-pro forum.
why are you discussing this here?
When attempting to root, install a custom ROM, or even install the original firmware, you may encounter issues that are caused by a broken cord, a dead computer, or when the firmware you installed is corrupted or you have the incorrect version installed. However, covering all error messages in a single article is difficult. As a result, we're focusing solely on "An error occurred when updating the device software." Samsung Galaxy Smartphones exhibit this error. It happened to me on a Samsung Galaxy Note 10 Plus with One UI and Android 10, Android 11, and Android 12 firmware.
We have two options for fixing this: official and unofficial. The latter is suggested.
Unofficial Method
Using Frp HiJacker by Hagard
In this method, we will be using the unofficial application “Frp HiJacker by Hagard“.
1. First you need to download the application from this link.
2. Once downloaded please extract the zip archive and you will get a “.exe” file. Double click on it to install.
3. In the second installation window you will be asked to enter the password. Now enter “www.gsmhagard.com” as the password and complete the installation.
4. Once done connect your Samsung Galaxy Smartphone with your PC and open the “Frp HiJacker by Hagard” application.
Now if the box near “Port” is empty then please click the “Scan” button. Once done your phone will be detected by the application.
Else type your model number.
However, if the box is already filled automatically you are good to proceed.
5. Now select “Soft Brick Fixer” and click the “HIJACK IT!” button.
That’s it your Galaxy Smartphone will reboot and the error will be gone for good.
Official Method
This method uses the official Samsung “Smart Switch” PC application.
1. First please download and install the Smart Switch application on your Windows PC from this link and for MAC OS here.
2. Now open Smart Switch If your device is connected you will get the phone model on this screen. If your Galaxy Smartphone is already connected please press the 3 dots on the top right corner and you will get a dropdown.
3. Now tap on “Emergency Software Recovery “. If you are good to go your phone model will be listed in the window’s list.
If you can see your phone’s model there please select it and click “OK” and follow the onscreen steps to resolve the error.
However, if you are not able to see your phone model or not able to connect to Smart Switch In this case please click on the second option which is “Reinstall device driver “.
When you get the window please click “Confirm” to proceed with phone driver installation.
Continue from "Step-3" once the device driver installation is complete and you can connect your phone to the "Smart Switch."
If you are unable to connect your Galaxy Smartphone to Smart Switch or if your phone model is not listed under "Emergency Software Recovery," you should utilize the Unofficial approach.
This actually helped me. Say, I've noticed it also has "remove FRP". Can you please explain how to perform this operation, too?
AndroidDeveloperLB said:
This actually helped me. Say, I've noticed it also has "remove FRP". Can you please explain how to perform this operation, too?
Click to expand...
Click to collapse
Did you manage it to work?
Naksuhd said:
Did you manage it to work?
Click to expand...
Click to collapse
What do you mean?
It only solved the error. I still have FRP.
I have found this video though, and even though it looks quite dangerous (for the PC), I gave it a try.
I'm only half way there. I got to the point that I'm in the settings of the OS.
The video is here:
link
I had this exact same issue while trying to install twrp on my galaxy s7 edge, after a lot of searching I could'nt find any solutions. I ended up choosing an older version of twrp and uploaded that, which fixed the issue.
DanyBoi05 said:
I had this exact same issue while trying to install twrp on my galaxy s7 edge, after a lot of searching I could'nt find any solutions. I ended up choosing an older version of twrp and uploaded that, which fixed the issue.
Click to expand...
Click to collapse
Hey! Could you report which version of twrp you used? I ran into exactly the same problem with my galaxy s7 edge and would like to try your solution
Man! Thank you! Most readable guide. Tried others, but they are so convoluted, you wrote it so good, fixed soft brick on S10!