Related
Hello, I am completely new so I apologize if this is the wrong place.
I wanted to be able to lock my bootloader but still use cyanogenmod, specifically, only allow roms that I have compiled myself and signed with my cert to work on my phone. I unpacked the stock recovery.img, and made the necessary changes to the ramdisk to replace the stock OnePlus key with my own. I then was then able to confirm that only my signed zips could be sideloaded, both official CM and OxygenOS zips failed - just as I wanted.
The issue is then that this only worked with an unlocked bootloader. When I locked it, the OP3 entered a boot cycle, with a strange graphical glitch appearing then the screen going black, again and again. I could then no longer boot to either recovery or cyanogenmod, nor could I unlock fastboot. This amazing guide got my phone working again.
I now have three questions. What prevented my phone booting after I locked it, how does the unbrick tool work, and is there anything I can alter, like certifications or hashes, lower down in the boot sequence to allow only my signed images to work (using the previous tool. I am unsure what QLoader is, some form of serial interface to the 820 to write to the storage chip?).
Thanks for any advice you can offer!
Update: I have unpacked boot.img provided in the unbrick tool. I cannot find any keys to modify in /res but I have found a file called "verify_keys". Does anyone know what I need to change in boot.img to allow my self-signed recovery and os to boot? Thanks
UPDATE 2:
From reading some Android notes it appears that instead of replacing the OEM key, you can also just use fastboot to flash keystores for self-signed recovery and roms. This still allows OEM signed images to run, but is certainly a step in the right direction. I have run into an issue with building a correct keystore. I can use keytool and import my previous certs, but "fastboot flash keystore examplename.keystore" fails. I saw "fastboot flash ssd keystore.dat" used, and it works with my current dot keystore file, but then after locking it fails to boot. I'm going to see how I can convert my .keystore to a .dat.
I've been meaning to ask this same question for a while now also, so I'm eager to see the response. I suspect the official OnePlus forums might be a good place to ask as well, since they are visited by engineers from OnePlus. For anyone else who's curious as to what's being discussed and better the understand the risks of an unlocked bootloader (and how to mitigate them), there's a brief article here as well as a paper.
It is always suggested that never re-lock the bootloader until there is valid reason to do it
JumboMan said:
It is always suggested that never re-lock the bootloader until there is valid reason to do it
Click to expand...
Click to collapse
Have you read any of the attached links in my last post? There are valid reasons for doing so.
Just to pose an oversimplified hypothetical, imagine going through immigration/customs in Saudi Arabia (or maybe even the U.S.) with a Android device that has an unlocked bootloader. The officer examines your possesions, then takes your laptop and phone into a back room. Your phone is powered down and encrypted so it's not like they can do anything, right? Wrong. They plug it into a forensics device and flash a surreptitious malware app onto /system before returning it back to you. Then, the next time you turn on your phone your encryption keys and all your data, all your communications are secretly transmitted. You never have a clue... With a locked bootloader and appropriate precautions, that would never be possible.
Update 3:
I am now following the official Android guide for creating a keystore. They show how to create a "keystore.img" not .dat, bu the error I got when trying "fastboot flash keystore ..." said something along the lines of the keystore not being a valid image. Hopefully this will work. After I get this working, I will move on to removing or damaging the OEM key, hence not even allowing OnePlus images to be sideloaded.
JumboMan said:
It is always suggested that never re-lock the bootloader until there is valid reason to do it
Click to expand...
Click to collapse
I do have a valid reason - security. An unlocked bootloader means any code can be flashed to my device. Even with encryption it is vulnerable to cold boot attacks, it makes it easier to bruteforce, and pulling encryption keys from memory.
chocol4te said:
I do have a valid reason - security. An unlocked bootloader means any code can be flashed to my device. Even with encryption it is vulnerable to cold boot attacks, it makes it easier to bruteforce, and pulling encryption keys from memory.
Click to expand...
Click to collapse
sir prefer not rooting and staying on stock ROM with locked bootloader.
emptyragnarok said:
sir prefer not rooting and staying on stock ROM with locked bootloader.
Click to expand...
Click to collapse
Look, I'm sorry, I don't need any more useless comments saying the solution to my problem is to not do anything like on every other forum I've tried. I am perfectly aware of how to lock the bootloader with a stock rom, but I don't want to use the stock rom. I want to use custom roms. From what I have done so far it appears to be possible, so don't tell me it's not, at least without a good reason.
In addition, the stock method isn't even the most secure the phone can be. OnePlus can still sign any code and run it on my device and hence requires my trust in a third party that I am unwilling to give. I only want my own code to run.
Update 4:
Using the unbrick utility, I have updated the MD5 partition with the checksums of my modified boot and recovery partitions. Unfortunately, I am now getting a checksum failed error, with both the MD5 and recovery partitions highlighted in red. So I was wrong about the checksum being compared with hashes in the MD5 partition. Does anyone know where the lowest level checksums are stored? Hopefully if I can change that, then locking the bootloader will be no issue.
chocol4te said:
Update 4:
Using the unbrick utility, I have updated the MD5 partition with the checksums of my modified boot and recovery partitions. Unfortunately, I am now getting a checksum failed error, with both the MD5 and recovery partitions highlighted in red. So I was wrong about the checksum being compared with hashes in the MD5 partition. Does anyone know where the lowest level checksums are stored? Hopefully if I can change that, then locking the bootloader will be no issue.
Click to expand...
Click to collapse
Bro I am not a prolike you but I understand your vision now,... and I am with you in that.... Open Source stuff and ANdroid as an Open source impify that only... We should have our custom code for locking and unlocking our bootloader so we can have the full control over our device.... If not and the guy that said that you can lock the bootloader with the stock rom didn't get that .. even with stock rom and recovery anyone can have the access of the phone by just unlocking the boot loader and that is simple. SO I GOT YOUR VISION AND I AM WITH YOU I WILL TRY TO UNDERSTAND THE LOCKING SYSTEM OF THE BOOT-LOADER AND I WILL TRY TO FIND THE LOCATION OF LOWER LEVEL CHECKSLUMS... WE will try and try untill we succeed.... I AM WITH YOU BRO!!!!!
indroider said:
Bro I am not a prolike you but I understand your vision now,... and I am with you in that.... Open Source stuff and ANdroid as an Open source impify that only... We should have our custom code for locking and unlocking our bootloader so we can have the full control over our device.... If not and the guy that said that you can lock the bootloader with the stock rom didn't get that .. even with stock rom and recovery anyone can have the access of the phone by just unlocking the boot loader and that is simple. SO I GOT YOUR VISION AND I AM WITH YOU I WILL TRY TO UNDERSTAND THE LOCKING SYSTEM OF THE BOOT-LOADER AND I WILL TRY TO FIND THE LOCATION OF LOWER LEVEL CHECKSLUMS... WE will try and try untill we succeed.... I AM WITH YOU BRO!!!!!
Click to expand...
Click to collapse
Thanks! I'm glad to hear it!
chocol4te said:
Thanks! I'm glad to hear it!
Click to expand...
Click to collapse
You're most welcome bro.
Did I just witness a major bro-down?
Awsome thread, I'd also like to put my OP3 in a state where only ROMs I signed my self will run...
Any further development??
Sent from my Pixel XL using XDA-Developers mobile app
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
indieross said:
Did I just witness a major bro-down?
Click to expand...
Click to collapse
Whats a bro down?
Sent from my Pixel XL using XDA-Developers mobile app
indroider said:
Any further development??
Sent from my Pixel XL using XDA-Developers mobile app
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
Whats a bro down?
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
Sorry, other stuff came up. I am still very interested in getting this to work, but I am really stuck if I can't understand why the MD5 verification error occurs when I use Loader to flash the modified images. I looked at CopperheadOS, and in their documentation they show how to re-lock the bootloader with a custom ROM. Here is the shell script they use to upload the OS.
Code:
fastboot flash bootloader bootloader-bullhead-bhz11f.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-bullhead-m8994f-2.6.33.2.14.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-bullhead-nbd90z.zip
As you can see they flash two images, boot loader and radio, then update the main ROM. Then apparently it boots fine and the bootloader is OEM locked inside the OS. This was for the Nexus 5X, but I want to find out if a similar process is possible on the OP3.
I may also begin work on porting CopperheadOS to the OnePlus 3. I know it sounds unrealistic, but since OnePlus released the binaries and kernels it should make it slightly easier.
chocol4te said:
Sorry, other stuff came up. I am still very interested in getting this to work, but I am really stuck if I can't understand why the MD5 verification error occurs when I use Loader to flash the modified images. I looked at CopperheadOS, and in their documentation they show how to re-lock the bootloader with a custom ROM. Here is the shell script they use to upload the OS.
As you can see they flash two images, boot loader and radio, then update the main ROM. Then apparently it boots fine and the bootloader is OEM locked inside the OS. This was for the Nexus 5X, but I want to find out if a similar process is possible on the OP3.
I may also begin work on porting CopperheadOS to the OnePlus 3. I know it sounds unrealistic, but since OnePlus released the binaries and kernels it should make it slightly easier.
Click to expand...
Click to collapse
Ok.. Great to hear... Let me if you need any help.. I m here
chocol4te said:
Sorry, other stuff came up. I am still very interested in getting this to work ... ...
I may also begin work on porting CopperheadOS to the OnePlus 3. I know it sounds unrealistic, but since OnePlus released the binaries and kernels it should make it slightly easier.
Click to expand...
Click to collapse
This sounds exactly like what I was looking for. Have you been able to progress? Do you think that the bootloader and the radio are somehow linked in the boot verification sequence?
---------- Post added at 05:51 AM ---------- Previous post was at 05:43 AM ----------
chocol4te said:
UPDATE 2:
From reading some Android notes it appears that instead of replacing the OEM key, you can also just use fastboot to flash keystores for self-signed recovery and roms. This still allows OEM signed images to run, but is certainly a step in the right direction. I have run into an issue with building a correct keystore. I can use keytool and import my previous certs, but "fastboot flash keystore examplename.keystore" fails. I saw "fastboot flash ssd keystore.dat" used, and it works with my current dot keystore file, but then after locking it fails to boot. I'm going to see how I can convert my .keystore to a .dat.
Click to expand...
Click to collapse
Have you read this: https://mjg59.dreamwidth.org/31765.html
I have a MetroPCS LG K-10 lgms428. That phone comes with the OEM unlock under the development section in the menu. I know how to eat an unlock it and send a command through fastboot. This will unlock the bootloader after I do that would it be possible for me to flash a version of cdb cwm or TWRP for a recovery and then rooted with SuperSU? If anyone has any links or info on this I would really appreciate it thank you
GraphMatix said:
I have a MetroPCS LG K-10 lgms428. That phone comes with the OEM unlock under the development section in the menu. I know how to eat an unlock it and send a command through fastboot. This will unlock the bootloader after I do that would it be possible for me to flash a version of cdb cwm or TWRP for a recovery and then rooted with SuperSU? If anyone has any links or info on this I would really appreciate it thank you
Click to expand...
Click to collapse
Its a good idea, I found link's for twrp for ms420 devices (mtk) but I was wondering if a twrp can be ported to work on ms428 (lz4)
No sure, don't really know much about porting.
I'm also working off of the friends laptop still trying to install Android SDK I'm just too unlock the bootloader. The laptop Works horribly so probably won't even have the bootloader unlocked till tomorrow.
Once that's done though willing to try anything to get root. I've been going to the forum, many people want root.
GraphMatix said:
No sure, don't really know much about porting.
I'm also working off of the friends laptop still trying to install Android SDK I'm just too unlock the bootloader. The laptop Works horribly so probably won't even have the bootloader unlocked till tomorrow.
Once that's done though willing to try anything to get root. I've been going to the forum, many people want root.
Click to expand...
Click to collapse
How do you unlock the bootloader just by "fastboot oem unlock"? It doesn't work. There are root methods already present for the devices.
Root?!?
I found this link for "supported" root
mobile.twitter.com/srsroot/status/765566108992700416
Im going to give a try i hope dosen't brick my device
Wish me luck
I will post if it works
---------- Post added at 02:50 PM ---------- Previous post was at 02:15 PM ----------
Found a thread for twrp for lg ms428 it will arrive soon let's all wait with patience
Link for thread
Forum.xda-developers.com/lg-k10/development/recovery-twrp-3-0-2-t3479837
ItzTropic said:
I found this link for "supported" root
mobile.twitter.com/srsroot/status/765566108992700416
Im going to give a try i hope dosen't brick my device
Wish me luck
I will post if it works
---------- Post added at 02:50 PM ---------- Previous post was at 02:15 PM ----------
Found a thread for twrp for lg ms428 it will arrive soon let's all wait with patience
Link for thread
Forum.xda-developers.com/lg-k10/development/recovery-twrp-3-0-2-t3479837
Click to expand...
Click to collapse
Awesome! Tell us if the root works.
Root and Custom backup will be soon . I've already tried that Twitter link. No luck..
I finally got another laptop I've been looking on the web for Just 2 Android SDK with no luck. Anyone have a link
Sent from my LGMS428 using Tapatalk
srs root
seems that srsroot fail to gain root acces but they update there tool today i will give a second chance
no luck :/
No luck at all
Hey there I've had the LG K10 for about a month now it's ****ing blows kingroot doesn't work neither does any other new app that I found it's real nice if XDA Developers could developer root strategy until then I am stuck with a pretty much useless phone
No root at all I'm still frustrated
But I was wondering there's a system-less root by chainfire
There's a way to flash it via adb or fastboot?
Great news .... Theres a twrp for lg k10 ms428 first build thanks to pvineeth97 link for thread here
forum.xda-developers.com/lg-k10/development/recovery-twrp-3-0-2-t3479837
Sorry for the noob question...
How do we use the TWRP recovery file ? Do I flash it over with ADB or one of the LG programs? I have the phone working with ADB.
ItzTropic said:
Great news .... Theres a twrp for lg k10 ms428 first build thanks to pvineeth97 link for thread here
forum.xda-developers.com/lg-k10/development/recovery-twrp-3-0-2-t3479837
Click to expand...
Click to collapse
Would like to use systemless root also but no access to it
Hello i have a LGMS428 its october31st 2016 and i just recieved a android system update on my phone like at 1:58am. Does any one know what the update is about??? I dont want to install it if its not a good update
nobodyz bizznezz said:
Hello i have a LGMS428 its october31st 2016 and i just recieved a android system update on my phone like at 1:58am. Does any one know what the update is about??? I dont want to install it if its not a good update
Click to expand...
Click to collapse
I will install it later and i will tell you
I have to install it via pc because somehow my ota update dosent work in my phone
couldn't install it due slow internet connection I will inform it by tomorrow
I was wondering that some apps like force doze can modify system using adb interface by granting the shell command to the package and giving permission to use "android.permission.DUMP" and work like a charm on my lg k10 (ms428)
I had an idea if adding this command manually using the same method to the kingroot package will root my device properly without any risk off hardbrick?
nobodyz bizznezz said:
Hello i have a LGMS428 its october31st 2016 and i just recieved a android system update on my phone like at 1:58am. Does any one know what the update is about??? I dont want to install it if its not a good update
Click to expand...
Click to collapse
Just bug fixes for battery improvement, doze improvement and game optimization
You guys unlocked Bootloader? Without unlocking bootloader the TWRP wont work.
I have unlocked bootloader on metropcs k10, qualcomm variant. Used minimal adb and fastboot on a laptop with win 7. In windows, nothing worked until i used master admin privilege. Open command prompt, type " net user administrator /active:yes " and restart your computer. As soon as it booted up it found my device and installed drivers. Bootloader unlocked right away. Now i want to install twrp. Would flashing through adb and fastboot be the best way??
csdangerous said:
I have unlocked bootloader on metropcs k10, qualcomm variant. Used minimal adb and fastboot on a laptop with win 7. In windows, nothing worked until i used master admin privilege. Open command prompt, type " net user administrator /active:yes " and restart your computer. As soon as it booted up it found my device and installed drivers. Bootloader unlocked right away. Now i want to install twrp. Would flashing through adb and fastboot be the best way??
Click to expand...
Click to collapse
Can you elaborate ? How you unlocked bootloader?
---------- Post added at 08:52 AM ---------- Previous post was at 08:43 AM ----------
csdangerous said:
I have unlocked bootloader on metropcs k10, qualcomm variant. Used minimal adb and fastboot on a laptop with win 7. In windows, nothing worked until i used master admin privilege. Open command prompt, type " net user administrator /active:yes " and restart your computer. As soon as it booted up it found my device and installed drivers. Bootloader unlocked right away. Now i want to install twrp. Would flashing through adb and fastboot be the best way??
Click to expand...
Click to collapse
Use fastboot flash recovery *.img
hi I have a LG k10 2017 that has a problem, does not start in fastboot, and even in recovery and then go fastboot, how do I start in fastboot?
XRed_CubeX said:
hi I have a LG k10 2017 that has a problem, does not start in fastboot, and even in recovery and then go fastboot, how do I start in fastboot?
Click to expand...
Click to collapse
I have the same issue with the same phone, I tried everything, I can't root my phone. Looks like LG "blocked" fastboot in some models, unless someone knows a way to remove it, I guess we're stuck.
Klinsk said:
I have the same issue with the same phone, I tried everything, I can't root my phone. Looks like LG "blocked" fastboot in some models, unless someone knows a way to remove it, I guess we're stuck.
Click to expand...
Click to collapse
It is said that to activate the fastboot you must format the partition LAF, you would say: "impossible, there are no methods" but there is an explot called LGLAF, I do not know how to use it, format the partition LAF involves the loss of the Download mode and unlocking the fastboot, one method is to make a backup of the LAF partition, go into fastboot, unlock, do all the things you need to do and then restore the partition. As soon as I know how to use it, maybe I write it in this thread.
Thanks man.
Failed experiment.
XRed_CubeX said:
Failed experiment.
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-k10/help/nuked-laf-download-mode-fastboot-t3898626 For informations.
XRed_CubeX said:
hi I have a LG k10 2017 that has a problem, does not start in fastboot, and even in recovery and then go fastboot, how do I start in fastboot?
Click to expand...
Click to collapse
I also have the same problem friends and I am very sad.
---------- Post added at 12:20 AM ---------- Previous post was at 12:17 AM ----------
[/COLOR]
XRed_CubeX said:
https://forum.xda-developers.com/lg-k10/help/nuked-laf-download-mode-fastboot-t3898626 For informations.
Click to expand...
Click to collapse
What a sad hand, I sincerely hope that you can resolve this as soon as possible.
How to root realme 3?
Hey mate,
I recently published a detailed guide on rooting the RealMe 3 device. I have clearly explained everything from unlocking bootloader, Installing TWRP recovery till Rooting the device. This is a step-by-step complete guide. You can check this out: https://www.androidstrike.com/root-realme-3-without-pc/
If you found it useful. Please share it with your friends.
Thanks for the guide man. It helped a lot. But, Where to download the TWRP Recovery image for RealMe 3?
velaru said:
Thanks for the guide man. It helped a lot. But, Where to download the TWRP Recovery image for RealMe 3?
Click to expand...
Click to collapse
This is fake post. Realme 3 bootloader still locked
Is it working or not? Because in real me community they posted the same guide to unlock the bootloader that given in the link by @vijay-balasa
RealMe community post: c.realme.com/in/post-details/1110804709561597952
*Remove space after https: //*
Aftab_khatri said:
This is fake post. Realme 3 bootloader still locked
Click to expand...
Click to collapse
I guess unlock option is already provided, it's in developer mode - oem Unlock
---------- Post added at 11:00 PM ---------- Previous post was at 10:56 PM ----------
Just to contribute to this thread, I have got realme u1 scatter file, it has Mediatek p70 processor same as realme 3
If someone is able to fetch recovery etc from this phone in download mode, it will be great.
We can go in download mode by powering off the device and the pressing vol up + vol down and connect the usb cable.
Scatter File for realme u1 (Mediatek p70 device):
preloader 0x0
pgpt 0x0
boot_para 0x8000
recovery 0x108000
para 0x4108000
reserve1 0x4188000
reserve2 0x4388000
reserve3 0x5388000
reserve4 0x5588000
reserve_exp1 0x6588000
oppo_custom 0x6788000
expdb 0x6888000
frp 0x7c88000
nvcfg 0x7d88000
nvdata 0x9d88000
metadata 0xdd88000
protect1 0xfd88000
protect2 0x10588000
seccfg 0x11000000
persist 0x11800000
sec1 0x14800000
proinfo 0x14a00000
md1img 0x14d00000
spmfw 0x1b100000
scp1 0x1b200000
scp2 0x1b800000
sspm_1 0x1be00000
sspm_2 0x1bf00000
cam_vpu1 0x1c000000
cam_vpu2 0x1cf00000
cam_vpu3 0x1de00000
gz1 0x1ed00000
gz2 0x1fd00000
nvram 0x20d00000
lk 0x24d00000
lk2 0x25200000
boot 0x25700000
logo 0x27700000
odmdtbo 0x28700000
tee1 0x29700000
tee2 0x29c00000
odm 0x2a800000
vendor 0x3a800000
system 0xa1800000
cache 0x1ae800000
userdata 0x1c9800000
otp 0xFFFF01d8
flashinfo 0xFFFF0080
sgpt 0xFFFF0000
Aftab_khatri said:
This is fake post. Realme 3 bootloader still locked
Click to expand...
Click to collapse
Enable usb debugging and oem unlock from developers options. Please follow the below guide on how to unlock bootloader, you have to do additional steps to unlock bootloader.
Refer this guide:
https://c.realme.com/in/post-details/1110804709561597952
vijaygopalbalasa said:
Hey mate,
I recently published a detailed guide on rooting the RealMe 3 device. I have clearly explained everything from unlocking bootloader, Installing TWRP recovery till Rooting the device. This is a step-by-step complete guide. You can check this out: https://www.androidstrike.com/root-realme-3-without-pc/
If you found it useful. Please share it with your friends.
Click to expand...
Click to collapse
Hello
Thank you very much for your useful guide.
Only issue is that REALME agrement doesn't come after many trials and one day staying before being in "Start the in-depth test" at "application submited please wait"
Secondly TWRP link direct to TWRP official but no any version available yet for MTK version .
Any explanation?
Regards
---------- Post added at 06:41 AM ---------- Previous post was at 06:01 AM ----------
fawazahmed0 said:
Enable usb debugging and oem unlock from developers options. Please follow the below guide on how to unlock bootloader, you have to do additional steps to unlock bootloader.
Refer this guide:
https://c.realme.com/in/post-details/1110804709561597952
Click to expand...
Click to collapse
Hello,
I am a bit sorry but same comments (see my post above) apply to this guide you provided.
Something not explained is going wrong. I need TWRP to set my HOST file.
I come from Xiaomi phone and I am very surprised to see that because OPPO OP6 is bootloader unlock very simple way.
can you help us?
SOLVED
here is the solution and why the tool stay stuck.
So easy when advised!
https://forum.xda-developers.com/showpost.php?p=78688631&postcount=4
Garpituz said:
How to root realme 3?
Click to expand...
Click to collapse
Did you succeed unlocking and rooting it?
Solution in post above.
lolo9393 said:
Hello
Thank you very much for your useful guide.
Only issue is that REALME agrement doesn't come after many trials and one day staying before being in "Start the in-depth test" at "application submited please wait"
Secondly TWRP link direct to TWRP official but no any version available yet for MTK version .
Any explanation?
Regards
---------- Post added at 06:41 AM ---------- Previous post was at 06:01 AM ----------
Hello,
I am a bit sorry but same comments (see my post above) apply to this guide you provided.
Something not explained is going wrong. I need TWRP to set my HOST file.
I come from Xiaomi phone and I am very surprised to see that because OPPO OP6 is bootloader unlock very simple way.
can you help us?
SOLVED
here is the solution and why the tool stay stuck.
So easy when advised!
https://forum.xda-developers.com/showpost.php?p=78688631&postcount=4
Click to expand...
Click to collapse
Hi friend,
I didn't get you, do you mean you were unable to unlock the bootloader, can you provide me the screenshot of error which you are getting and also can you tell me your location, is it france?
fawazahmed0 said:
Hi friend,
I didn't get you, do you mean you were unable to unlock the bootloader, can you provide me the screenshot of error which you are getting and also can you tell me your location, is it france?
Click to expand...
Click to collapse
Hello,
Thanks for taking care.
Yes I was unable to unlock the realme3 bootloader thinking that the DeepTesting_Tool_ was supposed to send me back an agrement and I waited all night long for it. But digging around I found explanation (not written in any unlocking guide) how to get set.
this post;
https://forum.xda-developers.com/showpost.php?p=78688631&postcount=4
Issue solved, thanks everybody.
Now I have to find or wait for TWRP availability but unlock is done and phone has been cleared from the beginning.
Regards
PS: Coming from XIAOMI I can say that this PHONE is much greater than expected!
lolo9393 said:
Hello,
Thanks for taking care.
Yes I was unable to unlock the realme3 bootloader thinking that the DeepTesting_Tool_ was supposed to send me back an agrement and I waited all night long for it. But digging around I found explanation (not written in any unlocking guide) how to get set.
this post;
https://forum.xda-developers.com/showpost.php?p=78688631&postcount=4
Issue solved, thanks everybody.
Now I have to find or wait for TWRP availability but unlock is done and phone has been cleared from the beginning.
Regards
PS: Coming from XIAOMI I can say that this PHONE is much greater than expected!
Click to expand...
Click to collapse
Hi,
I have philz touch recovery from similar device realme u1, do you want to try flashing it, I will give you the procedure to flash.
fawazahmed0 said:
Hi,
I have philz touch recovery from similar device realme u1, do you want to try flashing it, I will give you the procedure to flash.
Click to expand...
Click to collapse
I am not in hurry, I just want access to system/etc in order to modify Hosts file.
Coming from Snapdragon stuff I would like to avoid mistaking as much before having learnt MTK tricks.
I've found one U1 TWRP in searching the web , it is a 15612KB file size (win10 explorer numbers). If you have a different one I'll be happy to test it because the first one didn't boot in fastboot. ( I just checked fastboot boot "twrp.img" instruction, because I feared to install it!)
Normally it should boot temporarily, expected something special is not to be done to open it?...
If you trust your version, I'll install it. Just confirm me the boot manipulation sequence.
Regards
lolo9393 said:
I am not in hurry, I just want access to system/etc in order to modify Hosts file.
Coming from Snapdragon stuff I would like to avoid mistaking as much before having learnt MTK tricks.
I've found one U1 TWRP in searching the web , it is a 15612KB file size (win10 explorer numbers). If you have a different one I'll be happy to test it because the first one didn't boot in fastboot. ( I just checked fastboot boot "twrp.img" instruction, because I feared to install it!)
Normally it should boot temporarily, expected something special is not to be done to open it?...
If you trust your version, I'll install it. Just confirm me the boot manipulation sequence.
Regards
Click to expand...
Click to collapse
After booting the recovery image temporarily, you should do this command,
fastboot oem reboot-recovery
Then it might work
---------- Post added at 09:58 AM ---------- Previous post was at 09:53 AM ----------
Here is the link: https://mega.nz/#F!SV8yhKiT!zY29yJFupGBK0REm40FSBQ
Procedure to boot temporarily:
adb reboot bootloader
fastboot boot philz.img
fastboot oem reboot-recovery
---------- Post added at 10:01 AM ---------- Previous post was at 09:58 AM ----------
Remember one thing, if the recovery work, then "DO NOT USE REBOOT TO RECOVERY OPTION" from philz recovery, it might brick the device
lolo9393 said:
I am not in hurry, I just want access to system/etc in order to modify Hosts file.
Coming from Snapdragon stuff I would like to avoid mistaking as much before having learnt MTK tricks.
I've found one U1 TWRP in searching the web , it is a 15612KB file size (win10 explorer numbers). If you have a different one I'll be happy to test it because the first one didn't boot in fastboot. ( I just checked fastboot boot "twrp.img" instruction, because I feared to install it!)
Normally it should boot temporarily, expected something special is not to be done to open it?...
If you trust your version, I'll install it. Just confirm me the boot manipulation sequence.
Regards
Click to expand...
Click to collapse
Did the philz worked?
fawazahmed0 said:
Did the philz worked?
Click to expand...
Click to collapse
Result trial!
Sorry, it doesn't boot , it stays at waiting for any devices after "fastboot oem reboot-recovery" instruction and reboot itself into system.
I've seen that a magisk boot is promoted at Realme 1 forum.
Do you feel it is a solution for having root?
lolo9393 said:
Result trial!
Sorry, it doesn't boot , it stays at waiting for any devices after "fastboot oem reboot-recovery" instruction and reboot itself into system.
I've seen that a magisk boot is promoted at Realme 1 forum.
Do you feel it is a solution for having root?
Click to expand...
Click to collapse
No don't try that, your device will get HARD BRICKED
I have tried magisk boot of realme U1, and my device got hard bricked, so never do that
fawazahmed0 said:
No don't try that, your device will get HARD BRICKED
I have tried magisk boot of realme U1, and my device got hard bricked, so never do that
Click to expand...
Click to collapse
Thanks for advising me!
I was only suggesting...
Without any prove of success, I CAN NOT trust a solution not well documented.
They are lot of "talks" on every forum.
We keep in touch.
lolo9393 said:
Thanks for advising me!
I was only suggesting...
Without any prove of success, I CAN NOT trust a solution not well documented.
They are lot of "talks" on every forum.
We keep in touch.
Click to expand...
Click to collapse
When I get my phone back, I will try building the twrp for our phone and yeah, we will keep in touch
Can someone enter this command in adb to get the file. It is needed to decrypt stock firmware which in turn is needed for building TWRP.
Code:
adb pull /vendor/lib64/libapplypatch_jni.so
PS. I don't have the device or I would have done it myself.
Hi guys, I'm stucked at this weird problem, basically when I type that command, fastboot reply with the list of options, like the command itself doesn't exist. Funny things is, to confirm it should work, I've tried to launch it with the device connected but not in fastboot, and it says "waiting for device" so the command actual exists.
I've tried so far: dl the last adb sdb from the official page
put the phone through fastboot using adb fastboot devices (it works)
launch the command: nothing works
This is hmm my 4th? Oneplus, so isn't like I'm new to unlock bootloaders but now I'm stucked, any ideas?
Of course OEM debug is on and also OEM unlock
ps.: I've also tried the old command but no resuts
here is the proper fastboot stuff you need. https://www.mediafire.com/file/xy5ifa0k1bz7tn4/fastboot.7z/file
with this one, fastboot flashing unlock
MrSteelX said:
here is the proper fastboot stuff you need. https://www.mediafire.com/file/xy5ifa0k1bz7tn4/fastboot.7z/file
with this one, fastboot flashing unlock
Click to expand...
Click to collapse
Ty, I've done it properly but sadly, I'm in the loop now, because following the guide to unlock:
because of the mismatch of the step 3 (which stated correctly I guess, "init_boot", and the pic, I've wrote boot instead of init_boot and flashed the patched magisk file to the boot.
Do you know/have where find the correct boot file to patch it back? My model is the CPH2449 A09 BA (europe) for what I remember...
Or, what guide can I follow withouth worst the situation... For now, I can still enter in the fastboot mode
If you flash init_boot to boot, it will hard brick your device. If you can't access fastboot now, then only way to recover is using MSM tool.
surajpai524 said:
If you flash init_boot to boot, it will hard brick your device. If you can't access fastboot now, then only way to recover is using MSM tool.
Click to expand...
Click to collapse
Yes I've noticed...someone helped me for 20 bucks from telegram so now its working...btw my mistake is due to the guide in the first post, as the pic there SHOWS to flash it to BOOT instead of INIT, please fix the guide and check it 200x times before post it wtf...
takui said:
Yes I've noticed...someone helped me for 20 bucks from telegram so now its working...btw my mistake is due to the guide in the first post, as the pic there SHOWS to flash it to BOOT instead of INIT, please fix the guide and check it 200x times before post it wtf...
Click to expand...
Click to collapse
I know.. That's why I used the other method to root. KernelSU method.
PROPER CPH2451 Root and Update instructions
This is for the CPH2451 Rom, but should also work for other roms. I have returned my device so I will not be updating this with future updates. I have validated these instructions work for CPH2451 NA version so it's your choice to follow it or...
forum.xda-developers.com
surajpai524 said:
I know.. That's why I used the other method to root. KernelSU method.
PROPER CPH2451 Root and Update instructions
This is for the CPH2451 Rom, but should also work for other roms. I have returned my device so I will not be updating this with future updates. I have validated these instructions work for CPH2451 NA version so it's your choice to follow it or...
forum.xda-developers.com
Click to expand...
Click to collapse
oh thanks for the link, ill check it after it finish to copy data from old one...this time it needs 1 hr (before 5 mins...lucky, without reason)... it worked for u then? Ok!
takui said:
oh thanks for the link, ill check it after it finish to copy data from old one...this time it needs 1 hr (before 5 mins...lucky, without reason)... it worked for u then? Ok!
Click to expand...
Click to collapse
Yes.. this method just needs booting and no hard flash. Also unlock bootloader and try setting passcode or patern before you copy data. If you can't set pattern, then relock and unlock bootloader till possible.
surajpai524 said:
Yes.. this method just needs booting and no hard flash. Also unlock bootloader and try setting passcode or patern before you copy data. If you can't set pattern, then relock and unlock bootloader till possible.
Click to expand...
Click to collapse
hey, did you perhaps found a way to fix fingerprint/passwords not working too? I guess that it is broken because I had one before unlocking it...so maybe locking it back, removing old one (if works) and unocking again, could work but...I'm still trying to figure out how to lock it back...maybe with enhanced tools... any ideas? Maybe I'm overthinking?
takui said:
hey, did you perhaps found a way to fix fingerprint/passwords not working too? I guess that it is broken because I had one before unlocking it...so maybe locking it back, removing old one (if works) and unocking again, could work but...I'm still trying to figure out how to lock it back...maybe with enhanced tools... any ideas? Maybe I'm overthinking?
Click to expand...
Click to collapse
Only is to fix phone lock issue is by relocking bootloader and unlocking it till it works. This must be done only if not rooted. No other method was found till now.
I've tried at least 5+ times, nothing. I've read first we need to flash stock then lock again, but idk how to flash stock frankly....now desperately I'm flashing it through enhanced fastboot tool, even if a guide said to avoid cuz some op10R got bricked... let's see....