Dear Community,
I just searched the past 2 days for a solution but I've not been lucky
Therefore I'd like to ask for help in this forum and hope there is some additional hint or hack I could try...:
So here's the situation:
OnePlus 5T (8/128) with a non booting or not "useful" OS (see last point what I've tried)
No TWRP or CWM
Stock Recovery present
Bootloader Locked
Allow Bootloader to be unlocked = FALSE
What I've already tried yet:
Flashing TWRP --> Not possible Bootloader Locked
Flashing regarding any other kinds like "update" or "flash all" as provided with TOOL_ALL_IN_ONE
ADB Sideload any available ROMS (Original "full" OP5T / FreedomOS / Omni8) --> ADB stops at 47% in Stock Recovery regardless of size of the ZIP file
Tried different versions of ADB (32 & 64 Bit / older & new / also with the LargeAddressAware approach / and on multiple PC's) --> Always same error (47%)
Stumbled upon the possibility to EmergencyDownload a factory flash due to Qualcomm chipset using the MSM-Download-Tool --> Only OnePlus 5 ROM available (no "T")
Mentioned EDL procedure works and OS is booting BUT neither Touchscreen nor USB OTG (for external mouse support) is working --> So I can't navigate and allow Bootloader to be unlocked again
Unfortunately I'm now stuck and have no more idea how to unbrick my phone again
What would help:
Any source to MSM-Download-Tool packed with a correct ROM for the OnePlus 5T
A Workaround to just flash TWRP via MSM-Download-Tool or Qualcomm's QFIL application in EDL mode
Some "hack" to bypass the locked Bootloader situation
Every appreciated Input you might have that I'm currently not aware of...
So PLEASE let me know of any approach that I could try or if you might have found a link or something else to a solution that might help me out of this disaster...
Many thanks in advance!
Tryouts due to your feedback:
@dreinulldrei - "fastboot boot recovery.img" tried with the original 5T Recovery.img also with blu_spark TWRP --> no luck...
SOLVED SOLUTION:
As the EDL factory flash ROM is currently not (or will never officially be) available public getting in contact with the OnePlus support team is required.
They have such a recovery tool (MSM-Download-Tool) with an appropriate ROM and are able to flash the device during a remote support session conducted via chat.
So by starting a chat on the OnePlus Support page and describing your situation will lead to scheduled time slot where a Level-2 technician will do all required steps remotely.
(All files are password protected and the technician ensures they are deleted at the end of the session so I'm unfortunately not able to provide the sources for DIY purposes...)
Following. I would think there would be some way to flash some sort of signed image via fastboot...
U flashed a 5 os to it, using the msmtool try to extract those files from 5t os, I will do it when I get home and so u can try it, i can't guarantee anything though, would u like me to do that for u
Bradl79 said:
U flashed a 5 os to it, using the msmtool try to extract those files from 5t os, I will do it when I get home and so u can try it, i can't guarantee anything though, would u like me to do that for u
Click to expand...
Click to collapse
Thanks for your input - I'm really not aware of how to generate such *.ops ROM files as this is what the MSM Tool expects...
But if there is a way and you are able to extract and produce a MSM flashable file I would be very happy to try!
I would recommend trying to boot a OP5T recovery, you might have flashed some OP5 rom including OP5 recovery. Just go into fastboot (power on with volume up pressed down), then via cmd:
fastboot boot recovery.img
Since OP does not offer the recovery to be downloaded, it will need to be downloaded from a working device. Lacking the cable right where I am, but I am sure someone else can help out.
crakerjac said:
Following. I would think there would be some way to flash some sort of signed image via fastboot...
Click to expand...
Click to collapse
Thanks for the input - I forgot to mention I also tried the 2 original available OP5T "full" ZIP ROM's (think they should be signed...)
Will add this to the initial Post but I assume also no chance here...
dreinulldrei said:
I would recommend trying to boot a OP5T recovery, you might have flashed some OP5 rom including OP5 recovery. Just go into fastboot (power on with volume up pressed down), then via cmd:
fastboot boot recovery.img
Since OP does not offer the recovery to be downloaded, it will need to be downloaded from a working device. Lacking the cable right where I am, but I am sure someone else can help out.
Click to expand...
Click to collapse
Ohhh good point - I also think there is the "wrong" recovery (from 5) currently on my phone (because also there the touchscreen behaves unexpectedly...)
But unfortunately with your command I get the "Your device is corrupted. It can't be trusted and will not boot" message.
Tried this with the original 5T Recovery.img I managed to obtain and also with the blu_spark TWRP - no luck...
Edit: Ignore, misread previous post.
U may have to make a call to oneplus so they can restore for u
Submit a ticket to One Plus
You are going to have to submit a ticket, they will arrange a time to help you by unbricking the phone remotely.
I just had to do this myself this week, and it got done today.
I do have the 5t unbricking files but I cannot access the archive because it's password protected.
One important this you didn't mention is how this happened.
OnePlus may be able to help with this one, but all root guides explicitly include the phrase "at your own risk."
blackknightavalon said:
OnePlus may be able to help with this one, but all root guides explicitly include the phrase "at your own risk."
Click to expand...
Click to collapse
Bradl79 said:
U may have to make a call to oneplus so they can restore for u
Click to expand...
Click to collapse
WMerkens said:
You are going to have to submit a ticket, they will arrange a time to help you by unbricking the phone remotely.
I just had to do this myself this week, and it got done today.
I do have the 5t unbricking files but I cannot access the archive because it's password protected.
Click to expand...
Click to collapse
Thanks for all your advice - so I will arrange a support chat/ticket as soon as possible and inform about the result in this thread.
Didn't thought that OnePlus Support Team would even care about such bricks (no warranty / own risk / "playing" with root / etc...)
But as indeed they seem to help like @WMerkens experienced I would be very happy to have a working device again
CodeXter said:
Thanks for all your advice - so I will arrange a support chat/ticket as soon as possible and inform about the result in this thread.
Didn't thought that OnePlus Support Team would even care about such bricks (no warranty / own risk / "playing" with root / etc...)
But as indeed they seem to help like @WMerkens experienced I would be very happy to have a working device again
Click to expand...
Click to collapse
don't know why you would think that OP wouldn't help...they have said from day one that unlocking/rooting does not void your warranty. Heck they encourage it. I assume you are the same person on the OP forum w/ this problem. Hopefully after you get this resolved you will have learned to NEVER EVER RELOCK your phone unless you do the whole factory image qualcomm recovery tool bit. and experienced OP folks on this forum know any claims of a "hardbricked" OP phone is ALWAYS not true.
Yeah oneplus used to be good about and does a remote session to restore, this was back in the one plus one days though, but I think they still do it
---------- Post added at 03:25 AM ---------- Previous post was at 02:54 AM ----------
WMerkens said:
You are going to have to submit a ticket, they will arrange a time to help you by unbricking the phone remotely.
I just had to do this myself this week, and it got done today.
I do have the 5t unbricking files but I cannot access the archive because it's password protected.
Click to expand...
Click to collapse
Awwww I wish we could get them, do they use the msmtool too?
How I bricked a 5t
I got the phone and I had installed twrp, that went fine. I was looking at magick systemless rooter when the phone then kicked in with a OTA update, I chose to ignore it the first time. It occurred again a few minutes and in my haste I let it do it's job but it did not complete correctly. I rebooted and the phone complained about corruption to the OS, I got in again but made the dumb mistake of re enabling the OEM lock and because I thought that might be causing the problem. I rebooted again but now I could not boot any more into the OS, it complained I was corrupted and go to google to see what to do.
So I was left with a bricked phone.
I could do bootloader but not recovery and I could not unlock the bootloader.
I could not get in via adb usb debug, So after much research I download the OnePlus 5 unbricking pack and learned a whole lot about qualicom and EDL mode, plus I learned a lot about the QFIL tools and restoring a phone. I did the 5 unbrick but my screen ended up upside down but the touch was right side up, which resulted in a very hard to use phone.
I tried the QFIL method but I was missing a mdb file to be able to talk to the phone.
So I gave up submitted a ticket and after much bad co-ordination on their part got a level 2 tech to debrick the phone remotely.
They do a reverse VPN and connect to your computer, they tell you to have 2 files archive ready in a folder on your desktop (they supply the links). They install the EDL driver and unpack the debrick archive. The archives are password protected, they run the tool and restore the phone
back to factory.
They erase the unpacked archives after they are done.
jerrywmilton said:
don't know why you would think that OP wouldn't help...they have said from day one that unlocking/rooting does not void your warranty. Heck they encourage it. I assume you are the same person on the OP forum w/ this problem. Hopefully after you get this resolved you will have learned to NEVER EVER RELOCK your phone unless you do the whole factory image qualcomm recovery tool bit. and experienced OP folks on this forum know any claims of a "hardbricked" OP phone is ALWAYS not true.
Click to expand...
Click to collapse
Oh yes I've learned my lesson on this :angel: --> Never ever set OEM to be unlocked to NO again
Obviously I do not exactly know what wrong procedure made me stuck in this situation but I just wanted to revert every single step back one by one to see which element brings me back to a valid SafetyNet situation...
I've been with the OnePlus "family" since the OP1 but never needed any direct support from the vendor - so every time there's a first time and so for me now...
Thus I really didn't know OP staff is actively doing remote support for their devices - but thumbs up for that! :good:
(BTW: I'm not the guy from the OP forum)
Bradl79 said:
Yeah oneplus used to be good about and does a remote session to restore, this was back in the one plus one days though, but I think they still do it
---------- Post added at 03:25 AM ---------- Previous post was at 02:54 AM ----------
Awwww I wish we could get them, do they use the msmtool too?
Click to expand...
Click to collapse
Yes basically it's the same archive as the 5 unbrick pack but it's for 5t, OnePlus 5T OxygenOS 4.7.2-171116.zip is the archive and you can look in it and you see the ops file is for dumpling not cheesburger, which is the code name for 5t. I saw the MsmDownloadTool is 4.0.8
Bradl79 said:
Yeah oneplus used to be good about and does a remote session to restore, this was back in the one plus one days though, but I think they still do it
---------- Post added at 03:25 AM ---------- Previous post was at 02:54 AM ----------
Awwww I wish we could get them, do they use the msmtool too?
Click to expand...
Click to collapse
I just had a chat with them before and got mailed a link to the MSMTool incl. ROM for the OP5T (dumpling)
But unfortunatley support files from OnePlus are password protected Nevertheless here the original vendor link:
https://onepluscn-my.sharepoint.com/personal/sheva_liu_oneplus_net/_layouts/15/guestaccess.aspx?docid=0fde9596c72744b4fb9c073ca5d87edbe&authkey=AQPXKRi7pdIzZX-5WH_pwWg&e=1030aa0046da4d1aa9189020027d9c93
So I have to wait for my remote support schedule on Saturday to have the L2 technician entering the password and do the rest.
Would be able to do this myself but OnePlus obviously wants to protect their sources what I have to accept, respect and be patient for...
So, never turn off the OEM Unlocking?
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
hi,
A70 is now widely sold, i try to buy one soonest but just waiting for root and twrp. it is still empty here on xda...
i found a link show how to root and install
https://myphoneupdate.com/samsung-galaxy-a70-twrp-recovery/
can i ask if some one already tried as above? looks like a copy method for all kind of phones ...
tks.
Most likely fake, the article was published a month ago. A70 only got released on 26th March.
I would definitely wait until someone posts a technique here; I tend to trust the experts here, but not so much everywhere else on the internet. I would prefer to wait a few weeks and put with an unrooted device, rather than possibly end up with a bricked (or hijacked) device.
Andre
ok i will wait...
it was like this, waited for s10+, came twrp but didnot like camera hole and waiting for A70, then waiting for twrp, then oneplus7pro release, then wait a bit for its twrp, till then note 10 pro comes soon, then wait for twrp of it....
and after 2+ year still using note8 LOL
amk said:
hi,
A70 is now widely sold, i try to buy one soonest but just waiting for root and twrp. it is still empty here on xda...
i found a link show how to root and install
https://myphoneupdate.com/samsung-galaxy-a70-twrp-recovery/
can i ask if some one already tried as above? looks like a copy method for all kind of phones ...
tks.
Click to expand...
Click to collapse
First thing I tried ofcourse, rooting the A70, but... follow the steps in the manual yourself, and you'll see that you get stuck on step 3:
3.) After That Download TWRP Recovery https://twrp.me File On Your PC And Renamed The Downloaded Recovery File Name To twrp.img.
But there is no TWRP Recovery available for the A70
I also tried the A50 manual, but that also fails (stuck on OEM lock). I can install CROM Service, but it crashes.
Captain Beretta said:
First thing I tried ofcourse, rooting the A70, but... follow the steps in the manual yourself, and you'll see that you get stuck on step 3:
3.) After That Download TWRP Recovery https://twrp.me File On Your PC And Renamed The Downloaded Recovery File Name To twrp.img.
But there is no TWRP Recovery available for the A70
I also tried the A50 manual, but that also fails (stuck on OEM lock). I can install CROM Service, but it crashes.
Click to expand...
Click to collapse
don't follow some clickbait website's...
wait for a proper and trusted dev to release twrp. the phones has barely hit the market it will take a few weeks (if not months) at least till someone builds an twrp. one think you could provide us with would be some information. is the bootloader unlockable?
In devsettings is a possible to unlock oem. Try this before flashing twrp. If twrp flashed ok, I think need to wipe all data, include internal storage, then flash DM-VERITY, FORCE ENCRYPTION, AND DISC QUOTA DISABLER
zackptg5.com/android.php
I don't try it by myself. But you can try it, if you just buy the phone, and have not important data on it
What about this guide is it worth trying or not really possible? https://topjohnwu.github.io/Magisk/install.html
Avicohen21 said:
What about this guide is it worth trying or not really possible? https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
Need to try
hello everyone I find a good deal on galaxy a70 is anyone succeed in rooting?
celoxocis said:
... is the bootloader unlockable?
Click to expand...
Click to collapse
i have opened 2 sealed box of A70 and there was no OEM unlock option in developer mode. then got another with tick to choose. baterry is so good but look like i have touch panel issue. waiting for update and then root, twrp...
amk said:
i have opened 2 sealed box of A70 and there was no OEM unlock option in developer mode.
Click to expand...
Click to collapse
Mine (bought direct from Samsung UK) has the OEM Unlock option in the Developer Options menu. Not tried it yet, not really much point until there is a reliable and tested root out there.
Andre
Hey guys manegd to root with this guide https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
Seems to work good I'll notify if I'll notice any bugs. If you have twrp porting guide send me and I'll try to Port. If you want I can open a new thread with more details and upload the AP file I used. BTW I have the Israeli version SM-705FN
Avicohen21 said:
Hey guys manegd to root with this guide https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
Seems to work good I'll notify if I'll notice any bugs. If you have twrp porting guide send me and I'll try to Port. If you want I can open a new thread with more details and upload the AP file I used. BTW I have the Israeli version SM-705FN
Click to expand...
Click to collapse
make a topic please
sanakess said:
make a topic please
Click to expand...
Click to collapse
Ok when I get home I'll open a thread with detailed explanation of what I did
Samsung account
Hello. My dumbass bought used A70 with samsung account. I can't make a factory reset, because it needs password from old owner account which i don't know. But I have my Google account on that phone and Google find my device enabled. Will I need to enter samsung account information when I make a reset via Google find my device? So when reset is made, phone will be locked only by FRP? And then when I login in my old Google account can i create a new Samsung account or do I need to login in existing that was on that phone first? Sorry for offtopic.
Any news about TWRP? SuperSu or Magisk?
Hello All, still can't find TWRP for sm-a705fn
Can I flash TWRP for another Exynos phone, like Galaxy 9, to my A70 ?
Also, can I still use SuperSu with Pie/A70 ? I failed to root my previous Galaxy Tab8 with custom Pie using SuperSU, had to root with Magisk instead,
it worked just fine, but the link to topjohnwu mentioned in previous posts, tells scary things about Samsung/Pie/Magisk -
like, I have to switch between two recoveries... Is that really the case?
I haven't noticed any issue with Tab8/Pie/Magisk, but SuperSu would be still more familiar to me.
used2brick said:
Hello All, still can't find TWRP for sm-a705fn
Can I flash TWRP for another Exynos phone, like Galaxy 9, to my A70 ?
Also, can I still use SuperSu with Pie/A70 ? I failed to root my previous Galaxy Tab8 with custom Pie using SuperSU, had to root with Magisk instead,
it worked just fine, but the link to topjohnwu mentioned in previous posts, tells scary things about Samsung/Pie/Magisk -
like, I have to switch between two recoveries... Is that really the case?
I haven't noticed any issue with Tab8/Pie/Magisk, but SuperSu would be still more familiar to me.
Click to expand...
Click to collapse
No, you can't use twrp for a different device, and don't use SuperSU neither. It was sold by chainfire to a Chinese company years ago and have been basically abandoned since 2017. I'm pretty sure Magisk is the better choice on any device running android 5 - 9.
Sent from my motorola one vision
Hello,
The problem with the post you mentioned is that there is no valid twrp attached. And I noticed that only Odin detects the fastboot mode of this device. If you enable USB debugging let's say, the command "adb devices" will detect the device and list it; whereas, if you reboot it to bootloader mode(fastboot), the command fastboot devices doesn't detect the phone. So in fastboot mode, only Odin will detect the device. Meaning, that the post of fake and not tested.
Regards,
Wael
amk said:
i have opened 2 sealed box of A70 and there was no OEM unlock option in developer mode. then got another with tick to choose. baterry is so good but look like i have touch panel issue. waiting for update and then root, twrp...
Click to expand...
Click to collapse
That's weird. I do have the Bootloader unlock option in the developer settings and can do/undo it just fine. Looks like Samsung is using different Firmware versions on the A70?
Hello there !
I got the RN8Pro, last week and i unlocked it today. I naturally started to look how to root/install TWRP. I found numerous threads with instructions on how to do it but i also found a lot of warnings that it may brick the device, and that if that happens i need a special account to be able to unbrick it. It seems that some methods will work for the Chinese version while bricking others and vice versa. I have the Global ROM version 11.0.3.0(PGGEUXM) and the model of my phone is M1906G7G. Do you think it's safe for me to try flashing TWRP or at least root through ADB ?
I have also searched for custom ROMs and did not find any. The phone is relatively new so i wouldn't mind if i had to wait a bit, but i have also read that people just don't want to develop for it because of the Mediatek chip. Everyone says that development is not possible because there is no source code the the Mediatek chip. But here it says that the sources have been released partially here and the rest here. Is there something that's missing from these repos that makes development impossible ?
I also would like to become more than just a user and learn how to make custom roms. I found this thread that compiles some guides but a lot of them seem a bit outdated and I'm lost. Is that a good starting point or i should i go elsewhere ?
Thanks ^^
TheBolshe said:
Hello there !
I got the RN8Pro, last week and i unlocked it today. I naturally started to look how to root/install TWRP. I found numerous threads with instructions on how to do it but i also found a lot of warnings that it may brick the device, and that if that happens i need a special account to be able to unbrick it. It seems that some methods will work for the Chinese version while bricking others and vice versa. I have the Global ROM version 11.0.3.0(PGGEUXM) and the model of my phone is M1906G7G. Do you think it's safe for me to try flashing TWRP or at least root through ADB ?
I have also searched for custom ROMs and did not find any. The phone is relatively new so i wouldn't mind if i had to wait a bit, but i have also read that people just don't want to develop for it because of the Mediatek chip. Everyone says that development is not possible because there is no source code the the Mediatek chip. But here it says that the sources have been released partially here and the rest here. Is there something that's missing from these repos that makes development impossible ?
I also would like to become more than just a user and learn how to make custom roms. I found this thread that compiles some guides but a lot of them seem a bit outdated and I'm lost. Is that a good starting point or i should i go elsewhere ?
Thanks ^^
Click to expand...
Click to collapse
Can't you look at guides section we need Testers for POSP :crying:
girishjangir7 said:
Can't you look at guides section we need Testers for POSP :crying:
Click to expand...
Click to collapse
I did, but what is said there doesn't apply to me. I don't live near a center and I bought it on AliExpress, so I don't tink that I have a guarantee that I could use.
TheBolshe said:
I did, but what is said there doesn't apply to me. I don't live near a center and I bought it on AliExpress, so I don't tink that I have a guarantee that I could use.
Click to expand...
Click to collapse
No problem then wait for someone to test:laugh:
TheBolshe said:
I did, but what is said there doesn't apply to me. I don't live near a center and I bought it on AliExpress, so I don't tink that I have a guarantee that I could use.
Click to expand...
Click to collapse
I would love to help though. But your post is quite cryptic. More details could be nice like what are the risks, what is need to be done, what to do in case of a problem. Plus, it's my only phone ATM and I am poor ^^
It Is Safe As Well As Not Safe.
I Had Bricked My Redmi Note 8 Pro(8GB) And I Had To Visit Mi Service Centre As I Required Xiaomi Authorised Account Which I Don't Have.
Some Peoples Bricked Their Phone After Flashing TWRP And Some After Flashing Wrong Boot.img
I Flashed TWRP Successfully But When I Rooted My Phone, I Faced Bootloop Problem Then To Solve That Problem I Accidently Flashed Wrong Boot.img File( 10.0.4 Boot File Into 11.0.3) Which Resulted Into Bootloop
But If You Follow All The Steps Carefully Then It Is Absolutely Safe.
Hemant Singh Rajput said:
I Had Bricked My Redmi Note 8 Pro(8GB) And I Had To Visit Mi Service Centre As I Required Xiaomi Authorised Account Which I Don't Have.
Some Peoples Bricked Their Phone After Flashing TWRP And Some After Flashing Wrong Boot.img
I Flashed TWRP Successfully But When I Rooted My Phone, I Faced Bootloop Problem Then To Solve That Problem I Accidently Flashed Wrong Boot.img File( 10.0.4 Boot File Into 11.0.3) Which Resulted Into Bootloop
But If You Follow All The Steps Carefully Then It Is Absolutely Safe.
Click to expand...
Click to collapse
Mine has 6gb ram. Which TWRP img did you use?
When it's in bootloop, all I need to do is hold power up to get to fastboot so I can flash boot.img right?
TheBolshe said:
Mine has 6gb ram. Which TWRP img did you use?
When it's in bootloop, all I need to do is hold power up to get to fastboot so I can flash boot.img right?
Click to expand...
Click to collapse
I Flashed This TWRP Through CMD
https://forum.xda-developers.com/re...overy-unofficial-twrp-recovery-redmi-t4002397
You Need To Press&Hold Power+Vol Down Button To Enter Into Fastboot Mode.
When TWRP Flashed Successfully Through CMD You Have To Immediately Disconnect Your Phone From PC Otherwise Your Phone Will Load Stock Recovery.
---------- Post added at 12:45 PM ---------- Previous post was at 12:42 PM ----------
TheBolshe said:
Mine has 6gb ram. Which TWRP img did you use?
When it's in bootloop, all I need to do is hold power up to get to fastboot so I can flash boot.img right?
Click to expand...
Click to collapse
I Think You Shouldn't Take Risk As Your Phone Has No Warranty
I tried unsuccessfully to install TWRP on a Xiaomi Redmi Note 8 Pro.
These are the steps I took:
Unlock the bootloader with MiUnlock.
Downloaded Fastboot.
Copied this CFW TWRP inside the Fastboot folder.
Downloaded these two files and copied inside the Fastboot folder.
fastboot flash preloader preloader_begonia.bin
fastboot flash lk lk.img
fastboot flash recovery twrp-3.3.1-0-begonia_UNOFFICIAL.img
fastboot reboot
And the result is that it no longer turns on. It also fails neither to enter the Fastboot screen, nor in that of recovery.
Windows no longer sees the device, so I can't interact in any way even with the folders inside the phone memory. Finally it is not even seen by Xiaomi Flash Tool (wanting to try to reinstall the official ROM).
The phone, immediately after unlocking it with the Xiaomi tool, had MIUI 12. I don't know which Android mounted (my fault), but I proceeded the same, without doing a downgrade, since in a discussion here on the forum it seemed that it could work same, even without downgrading to Android 9.
Is there any way to fix?
Maybe using Linux, you might be able to interact with the phone memory even if it is turned off / bricked?
Solution
Without hoping in the least, I solved it by following this video step-by-step.
I thank the author of this video a million times.
For anyone who was reading and needed it, there is no need to open the phone, remove the battery, connect various wires... You can do everything from software with a couple of clicks, even if the phone does not seem to want to connect absolutely to the PC.
Follow the linked video, it's very simple and you will save a lot of money!
Only if you have flashed it with a CFW
Angry Unlocker said:
Without hoping in the least, I solved it by following this video step-by-step.
I thank the author of this video a million times.
For anyone who was reading and needed it, there is no need to open the phone, remove the battery, connect various wires... You can do everything from software with a couple of clicks, even if the phone does not seem to want to connect absolutely to the PC.
Follow the linked video, it's very simple and you will save a lot of money!
Click to expand...
Click to collapse
Good for CFW, but if you are on a official MIUI and you've hardbricked it then you have to through an authorised Xiaomi account, in other words, it is a "payable flash" that you have to perform.
I had the same problem
Months ago I tried to install a stock ROM prior to the latest version installed, I got a brick exactly like the one you have, I didn't know who to go with until days ago, in a group on Telegram.
There is a group where a boy from Spain helped me with his authorized account for € 30, if you want to contact him I will leave you the link of the group.
https: //t.me /edlauth
(I put spaces for it to allow me to post the answer)
Thanks for your answers!
kingsemperor said:
Good for CFW, but if you are on a official MIUI and you've hardbricked it then you have to through an authorised Xiaomi account, in other words, it is a "payable flash" that you have to perform.
Click to expand...
Click to collapse
I am not quite clear what you mean exactly, but I, before proceeding with trying to flash a custom ROM, I had connected my original Xiaomi account to the device in question and also had requested the unlocking of the bootloader through the appropriate Xiaomi software (and I finally waited the time indicated by them, before proceeding). So on my Note 8 Pro there was actually the original / official MIUI updated to the latest version and I didn't need to proceed with a payment of any kind following that tutorial.
chumpokemon said:
Months ago I tried to install a stock ROM prior to the latest version installed, I got a brick exactly like the one you have, I didn't know who to go with until days ago, in a group on Telegram.
There is a group where a boy from Spain helped me with his authorized account for € 30, if you want to contact him I will leave you the link of the group.
https: //t.me /edlauth
(I put spaces for it to allow me to post the answer)
Click to expand...
Click to collapse
Thanks for your suggestion, but I have already solved it by following precisely that video.
How could I unlock the bootloader with the device bricked?
I has been trying a to unlock bootloader with MiUnlock but doesn't work. Is there any other way to unlock the bootloader with the bricked device?
Perike said:
How could I unlock the bootloader with the device bricked?
I has been trying a to unlock bootloader with MiUnlock but doesn't work. Is there any other way to unlock the bootloader with the bricked device?
Click to expand...
Click to collapse
You need to unbrick your device, follow the video tutorial
https :// youtu.be /wm0UFvjSvVg
chumpokemon said:
You need to unbrick your device, follow the video tutorial
https :// youtu.be /wm0UFvjSvVg
Click to expand...
Click to collapse
Flashed successfully, but the result is a reboot and This Miui version cant be installed on this device...
Angry Unlocker said:
Solution
Without hoping in the least, I solved it by following this video step-by-step.
I thank the author of this video a million times.
For anyone who was reading and needed it, there is no need to open the phone, remove the battery, connect various wires... You can do everything from software with a couple of clicks, even if the phone does not seem to want to connect absolutely to the PC.
Follow the linked video, it's very simple and you will save a lot of money!
Click to expand...
Click to collapse
Why does it say "this video is private" ?
Follow and complain here.
Let ASUS know their bootloader implementation is VERY NOT FRIENDLY to us. I've been modding my Android devices since the Android 2 era and this is the first time I encountered an UNOFFICIALLY UNRECOVERABLE state which is a HORRIBLE experience.
Me? Have played with
Samsung(S5 to S9 and Tab/Odin is a good thing)
XiaomiRedmiPoco(Main device for me today, very modder friendly and robust)
Huawei(Remember when they allow applying for BL unlock?)
Apple(LOL jailbreak from A4 SoC until iPhone X(meantime Samsung S8 looks gorgeous) lost my interest)
And various small brands or exited market big brands(honorable mention Lenovo LePhone C101. My first smart device/Android and received big community support at the good old time)
ASUS. Fix your buggy BL. Fix your policy. Release everything we need to fix OUR DEVICES of OURSELVES. Just ONE step closer to perfect.
Just imagine how stupid is this:
Everytime you want to update you operating system, your UEFI/BIOS firmware might break.
And worse, that you don't have free official resources to fix it?
And can it be worse? Yes! Your Warranty is maybe void because you may unlocked bootloader, now supposedly only ASUS service center have the file to fix it.
Ha now it's interesting. That's the era of ANTITRUST. Even Apple won't do it(Worst case DFU, easily fixable using OFFICIAL iTunes).
WT*?
yeah dude i'm bricked up rn
Paid here, paid there.
Yeah sure.
Exploit people.
Perhaps instead of ranting about asus, you could tell us what you have done exactly to brick your device, and someone might be able to help you ? can you get into fastboot at all?
EDIT: quoted content removed.
Never use this firmware, because it has not been modified, 100% of fingerprints and IMEI will be lost after use. You need to modify the firmware before you can flash it.
mahdibassam said:
Perhaps instead of ranting about asus, you could tell us what you have done exactly to brick your device, and someone might be able to help you ? can you get into fastboot at all?
Click to expand...
Click to collapse
Trying to flash img unpacked from update zip. Which you should NOT do. Because Android 12 dynamic partition.
iMoc said:
Trying to flash img unpacked from update zip. Which you should NOT do. Because Android 12 dynamic partition.
Click to expand...
Click to collapse
Ok, yes you definitely should not do that
So just wondering, you went and grabbed some img files and made the decision to flash them, why is this any fault of asus?
mahdibassam said:
Ok, yes you definitely should not do that
So just wondering, you went and grabbed some img files and made the decision to flash them, why is this any fault of asus?
Click to expand...
Click to collapse
1\ The fastboot code in their bootloader have bugs, any CORRECT command you type can easily break bootloader then stuck you in 9008.
2\ The normal update method failed because THEIR UPDATER did do things wrong.
3\ They refuse to provide official ROM to let yourself fix it. SEND IT TO ME TO FIX IT, AND I MIGHT CHARGE YOU SOME.
....\
N\ You go talk to Apple about it because they are experts about saying YOU USED IT WRONG.
Anyone asked for help gets it for free so far.
All devs on my chat group agree at least fastboot flashable should be available on the official download page.
MOD EDIT: off topic content removed
Did you manage to unbrick your phone?
I managed to semi hard brick my phone. Can get into fastboot but unable to start recovery mode from fast boot and phone doesn't show up from adb devices.
I guess I'll start a new thread but any tips?
insideoft said:
Did you manage to unbrick your phone?
I managed to semi hard brick my phone. Can get into fastboot but unable to start recovery mode from fast boot and phone doesn't show up from adb devices.
I guess I'll start a new thread but any tips?
Click to expand...
Click to collapse
If you can boot into fastboot you can just flash the RAW ROM file available a few days ago. It's not bricked in this case.
Moderator Information
Hello everyone,
I have cleaned the thread from off topic contents and posts. Please focus on problem solving related discussion, not finger pointing or flaming each other. We all come here to solve the issues and learn some new stuffs.
Thanks.
iMoc said:
If you can boot into fastboot you can just flash the RAW ROM file available a few days ago. It's not bricked in this case.
Click to expand...
Click to collapse
Sorry long time ago since I was into this stuff previosly.
That fixed it, thanks for the help!
same here