Related
Hi
I accidentally deleted with TWPR the system of my OnePlus One and it seems I cannot install a new rom.
I downloaded gapps and the original Oneplus One rom (zip) file and also the android stock. None of them works. It seems I need a
different format/special rom do recover from this. To make things more complicated I have a Mac and most instructions I've found are for windows.
Is there any rom I can transfer after mounting and flash via TWPR? I don't know much about android development so I appreciate technical details in replies.
Thanks!
Exactly which zip files are you trying to flash? What are the filenames?
Transmitted via Bacon
use a toolbox and an option to flash to stock
gfusion said:
Hi
I accidentally deleted with TWPR the system of my OnePlus One and it seems I cannot install a new rom.
I downloaded gapps and the original Oneplus One rom (zip) file and also the android stock. None of them works. It seems I need a
different format/special rom do recover from this. To make things more complicated I have a Mac and most instructions I've found are for windows.
Is there any rom I can transfer after mounting and flash via TWPR? I don't know much about android development so I appreciate technical details in replies.
Thanks!
Click to expand...
Click to collapse
i assumed you fixed this since we have not heard back from you. Just an fyi - can you at least let people in your thread trying to help know you have been successful in doing what it is you were trying to do.
If not then simple download any rom transfer to your phone and flash it with TWRP and thats it. May I also suggest you dont use a toolkit since it will not give you the knowledge to fix your phone in the future
Indeed, i fixed it last night. Thank you very much.
It was too late for me to be able to do the captcha (actually, even now it's difficult).
I was using the Mac OnePlus One toolkit which is a real life safer. I already learned quite a bit but I was grateful to have the support of the toolkit. There are quite some hoops to jump through and I needed to use fastboot. Due to some reason I wasn't able to just flash a rom.
Cheers
Gfusion
playya said:
i assumed you fixed this since we have not heard back from you. Just an fyi - can you at least let people in your thread trying to help know you have been successful in doing what it is you were trying to do.
If not then simple download any rom transfer to your phone and flash it with TWRP and thats it. May I also suggest you dont use a toolkit since it will not give you the knowledge to fix your phone in the future
Click to expand...
Click to collapse
gfusion said:
Indeed, i fixed it last night. Thank you very much.
It was too late for me to be able to do the captcha (actually, even now it's difficult).
I was using the Mac OnePlus One toolkit which is a real life safer. I already learned quite a bit but I was grateful to have the support of the toolkit. There are quite some hoops to jump through and I needed to use fastboot. Due to some reason I wasn't able to just flash a rom.
Cheers
Gfusion
Click to expand...
Click to collapse
Here's a hint. Fastboot IS how you flash a new room for the first time had you not used the tool kit you would have seen this and done it that way lol
I'm kind of expert in the PC/laptop world, but a little rookie in Android and smartphones world. I don't get how a phone can get bricked.
As far as I know, an Android device has internal memory, and a portion of this internal memory is ROM (read-only memory), where the OS/firmware is installed. It's ROM because you don't want to mess around changing things of the OS, because you're not supposed to change things of the OS for the sake of a correct behavior of the phone.
The thing is that if you accidentally mess up something in the OS/firmware, you can, or should be always able to, re-install the OS again and start all over again. I mean, if I delete some Windows files in my PC and completely mess Windows up, I can always turn off the PC, turn it on, go to BIOS menu, boot from a Windows CD and re-install it. No problems at all.
1. So... where's the BIOS in Android? The recovery menu in Android is like the BIOS in Windows?
2. Bricking a phone is like damage the software of the hard disk drive (windows) or is it like mess up the BIOS?
3. Is there any difference between Operative System (android), firmware and ROM?
Well, ROM is memory, a physical drive/electronic device, completely different to a program/software/OS, but I'm referring to the conception you guys usually use (wrong I must say).
4. Why is it said that you flash a firmware, and not you install a firmware? Is it because it's done in a ROM, so it's called then flash?
Thanks!
rambomhtri said:
I'm kind of expert in the PC/laptop world, but a little rookie in Android and smartphones world. I don't get how a phone can get bricked.
As far as I know, an Android device has internal memory, and a portion of this internal memory is ROM (read-only memory), where the OS/firmware is installed. It's ROM because you don't want to mess around changing things of the OS, because you're not supposed to change things of the OS for the sake of a correct behavior of the phone.
The thing is that if you accidentally mess up something in the OS/firmware, you can, or should be always able to, re-install the OS again and start all over again. I mean, if I delete some Windows files in my PC and completely mess Windows up, I can always turn off the PC, turn it on, go to BIOS menu, boot from a Windows CD and re-install it. No problems at all.
Click to expand...
Click to collapse
I'm neither an expert in PCs or Android, so I might just be blowing hot air. I think the difference is that with a PC, it's designed to run Windows, thus Windows (obviously) will work on it (depending on version and processor compatibility). Linux runs because it's designed to run on that hardware. With Android however, everything is manufacturer-specific, and device-specific beyond that. If the firmware and kernel isn't written for that specific device, you'll brick your phone.
1. So... where's the BIOS in Android? The recovery menu in Android is like the BIOS in Windows?
Click to expand...
Click to collapse
Kinda? Maybe? I don't know.
2. Bricking a phone is like damage the software of the hard disk drive (windows) or is it like mess up the BIOS?
Click to expand...
Click to collapse
It could come from either. Flashing the wrong recovery (like TWRP for a Galaxy S3 Exynos instead of a Snapdragon model) would brick, and flashing the wrong ROM would brick as well.
3. Is there any difference between Operative System (android), firmware and ROM?
Well, ROM is memory, a physical drive/electronic device, completely different to a program/software/OS, but I'm referring to the conception you guys usually use (wrong I must say).
Click to expand...
Click to collapse
"ROM", in Android parlance, is indeed the OS. Sometimes also referred to as the firmware. Yes, both are misnomers. The use of "ROM" to refer to the OS I think comes from ROM image, when referring to gaming console emulation, but I could be mistake. "Firmware" typically refers to the programming in an electronic device that doesn't have a proper OS, per se. Like a basic mp3 player, VCR, cable modem, microwave oven, etc. It could be argued that Android is indeed a "firmware", by definition, even though "operating system" is more appropriate. Regardless, "ROM", and "firmware", in the Android world, both mean the OS.
4. Why is it said that you flash a firmware, and not you install a firmware? Is it because it's done in a ROM, so it's called then flash?
Click to expand...
Click to collapse
Flashing installs, but installing isn't necessarily flashing. "Flashing" is typically done at the recovery level (or through ADB), in the form of zips, tars, and other formats. It isn't incorrect to say that you installed a Gapps package through recovery, or you installed a newer version of TWRP, even though such actions are commonly known as "flashing". However, one wouldn't say that you flashed Clash of Clans through the Play Store, because that's not what you're doing. Flashing can refer to both firmware and software. For example, you can flash apps (like a Gapps package) TWRP batch back-ups, or even individual apps, and these are all software. You can flash nandroid backups or ROMs, and these are operating systems (and software/data). You can also flash proper firmware, such as radios/modems. You can flash kernels. Again, it's not wrong to say you "installed" it, but saying "flashed" is a more appropriate (in the Android community) and specific term.
rambomhtri said:
I'm kind of expert in the PC/laptop world, but a little rookie in Android and smartphones world. I don't get how a phone can get bricked.
As far as I know, an Android device has internal memory, and a portion of this internal memory is ROM (read-only memory), where the OS/firmware is installed. It's ROM because you don't want to mess around changing things of the OS, because you're not supposed to change things of the OS for the sake of a correct behavior of the phone.
The thing is that if you accidentally mess up something in the OS/firmware, you can, or should be always able to, re-install the OS again and start all over again. I mean, if I delete some Windows files in my PC and completely mess Windows up, I can always turn off the PC, turn it on, go to BIOS menu, boot from a Windows CD and re-install it. No problems at all.
1. So... where's the BIOS in Android? The recovery menu in Android is like the BIOS in Windows?
2. Bricking a phone is like damage the software of the hard disk drive (windows) or is it like mess up the BIOS?
3. Is there any difference between Operative System (android), firmware and ROM?
Well, ROM is memory, a physical drive/electronic device, completely different to a program/software/OS, but I'm referring to the conception you guys usually use (wrong I must say).
4. Why is it said that you flash a firmware, and not you install a firmware? Is it because it's done in a ROM, so it's called then flash?
Thanks!
Click to expand...
Click to collapse
A BRICKED phone is a phone that can't be fixed,no matter how hard you try.In other words,bricking your phone is altering the OS of your device in a way that causes it to become unusable/inoperable.
A BRICKED phone will not be able to Boot/Display any information/Boot into Recovery Mode.And thus your device turns into a very costly BRICK or Paperweight.
I have never seen any BRICKED device but heard about 2-3 cases here on XDA.I guess there are slight chances of getting your phone bricked until you do something HORRIBLY wrong or you do something,you don't have any idea about.
AFAIU,following factors can lead your device to BRICKING.
1.Overwriting the Firmware of the device or System softwares.
2.Interrupting Firmware update process (Half-written firmware ).E.g. Your device loses power during the process/data cable is pulled out during adb or rooting (That's the reason you get notifications or warnings as “Do not power the device off” when performing firmware updates and "Make sure your Battery is charged")
3.Flashing a ROM/MOD/Kernel that's not compatible to specific Device and Carrier.
Hope this helps!!
Regards
Do tell...
optimusodd said:
A BRICKED phone is a phone that can't be fixed,no matter how hard you try.In other words,bricking your phone is altering the OS of your device in a way that causes it to become unusable/inoperable.
A BRICKED phone will not be able to Boot/Display any information/Boot into Recovery Mode.And thus your device turns into a very costly BRICK or Paperweight.
I have never seen any BRICKED device but heard about 2-3 cases here on XDA.I guess there are slight chances of getting your phone bricked until you do something HORRIBLY wrong or you do something,you don't have any idea about.
AFAIU,following factors can lead your device to BRICKING.
1.Overwriting the Firmware of the device or System softwares.
2.Interrupting Firmware update process (Half-written firmware ).E.g. Your device loses power during the process/data cable is pulled out during adb or rooting (That's the reason you get notifications or warnings as “Do not power the device off” when performing firmware updates and "Make sure your Battery is charged")
3.Flashing a ROM/MOD/Kernel that's not compatible to specific Device and Carrier.
Hope this helps!!
Regards
Click to expand...
Click to collapse
That being said,
To my understanding so long as you flash your phones specific Kernel after flashing a carrier-incompatible ROM you will not BRICK. That is the only time I've bricked a device. It was an S3 and after 3 days of research I learned an SD card can be used to bring it back to life by basically flashing your .img onto it, albeit I could never boot the device without it again, though I could take it out afterward.
It was strange... but since using that device as a learning toy I believe that is something I learned from the experience, but correct me if I'm fatally wrong please before I get someone in trouble.
trinathaniel said:
That being said, To my understanding so long as you flash your phones specific Kernel after flashing a carrier-incompatible ROM you will not BRICK. That is the only time I've bricked a device. It was an S3 and after 3 days of research I learned an SD card can be used to bring it back to life by basically flashing your .img onto it, albeit I could never boot the device without it again, though I could take it out afterward. It was strange... but since using that device as a learning toy I believe that is something I learned from the experience, but correct me if I'm fatally wrong please before I get someone in trouble.
Click to expand...
Click to collapse
Short answer: If you can boot into Fastboot Or Recovery mode,you are not Hard bricked and there is still some hope
The scenerio you are talking about is Soft Brick.In this case your device don't boot but you can still get into Recovery.To fix it you boot into Recovery and restore the backup / flash the system image.You don't need to flash a kernel to make it working.
A hard bricked device won't show any sign of life,you won't be able to boot into Fastboot or Recovery to run Fastboot commands / ADB shell commands / Flash any image or zip.
Hope this helps!!
Plug out your Phone on flash Befor he finish boting
optimusodd said:
Short answer: If you can boot into Fastboot Or Recovery mode,you are not Hard bricked and there is still some hope
The scenerio you are talking about is Soft Brick.In this case your device don't boot but you can still get into Recovery.To fix it you boot into Recovery and restore the backup / flash the system image.You don't need to flash a kernel to make it working.
A hard bricked device won't show any sign of life,you won't be able to boot into Fastboot or Recovery to run Fastboot commands / ADB shell commands / Flash any image or zip.
Hope this helps!!
Click to expand...
Click to collapse
I totally understand what you're conveying and trust and believe when I say I've had my fair share of both types of Brick. What I mean is.... essentially the Kernel is going to be the defining difference between Hard Bricking vs Soft. For instance, I'm using a Note 5 Sprint (SM-N920P). If I were to flash BlahRom_N920T.zip then try and boot to system it'd definitely Hard Brick me, but if I were to flash an N920P Kernel immediately afterwards THEN boot to system out wouldn't. It might be kind of jacked up and buggy, but that's the determining factor as far as I understand.
Hi Everyone,
Living in Japan, we have no official channel to purchase a OnePlus handset here.
Really wanted to get a OnePlus 7 Pro as I felt it is the best model on the market as of today.
Knowing that, I got mine on Amazon Japan from a HK online shop which had very good reputation.
Now, the problem is these phones always come already opened as they say they need to confirm operation before sending it.
I have been reading news and article about this where we see more third party companies flash their roms with malware/ransomeware already built in...
In these situation, the best way to clean the phone is to do a full re-install of the OS.
I did review a bunch of article on XDA and it seems that now, due to the A/B partition setup, we can't just use official OnePlus image to load from the fastboot easily.
We have to rely on community provided too and stock rom to be able to do so....
When I raised the question to OnePlus and Oneplus forums, they mentioned to me that installed the updated like here (Page: support.oneplus.com/app/answers/detail/a_id/4312/~/oxygen-os-for-oneplus-7-pro)would do the trick using the local update function.
What I was directed to do is use the recovery boot to delete system settings/cache and everything data user and then, run the local update. Doing so, that would do it while not using community tools.
Here are my questions and which I would hope to get your experience:
1 Is the process I did really does use a brand new clean OS and do not rely/integrate part of the OS that came with the handset originally (that was the target).
2 Is there a way for me using OnePlus only provided tools and image to fully delete the phone and install the OS (maybe I am thinking this too much like a PC which I have more experience with...)
3 The OS looks fine and no strange apps shows up at all but how can I be sure nothing dodgy is running? Is there tools I could use to confirm this?
Sorry if I sound paranoid. Ideally, I understand the best thing to do was to buy directly from Oneplus and work a way to have it shipped to Japan but thought it would be interesting for me to learn more about android.
With previous Oneplus, it was easier as they were provided this type of official file for recovery but they stopped...
Thank you again for your time and hopping to learn more about how new android setup works.
Is the bootloader locked? Is Widevine (Netflix HD) certification still there? You can check these things to see if the phone has been tampered with.
brissoukun said:
Hi Everyone,
When I raised the question to OnePlus and Oneplus forums, they mentioned to me that installed the updated like here (Page: support.oneplus.com/app/answers/detail/a_id/4312/~/oxygen-os-for-oneplus-7-pro)would do the trick using the local update function.
What I was directed to do is use the recovery boot to delete system settings/cache and everything data user and then, run the local update. Doing so, that would do it while not using community tools.
Here are my questions and which I would hope to get your experience:
1 Is the process I did really does use a brand new clean OS and do not rely/integrate part of the OS that came with the handset originally (that was the target).
2 Is there a way for me using OnePlus only provided tools and image to fully delete the phone and install the OS (maybe I am thinking this too much like a PC which I have more experience with...)
3 The OS looks fine and no strange apps shows up at all but how can I be sure nothing dodgy is running? Is there tools I could use to confirm this?
Thank you again for your time and hopping to learn more about how new android setup works.
Click to expand...
Click to collapse
Good questions. Before you start, check the model number of your device through Settings > About. I'm assuming it's the international/global/unlocked version (GM1917).
With regard to question 1, a full build downloaded from the link you provided should contain every part of the OS, and flashing it through local update should overwrite anything that was there before. Before flashing, I would perform a full data wipe through recovery like you mentioned.
Q2: There is an MSM tool that will completely flash a system image for the OP7 Pro. I don't think they're generally intended for public use but they always get leaked anyways. They write an image (in the case of OnePlus, a .ops file) to the phone using a PC and USB connection. Here is a link to a thread which contains the MSM tool:
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
Download the tool for the model of your phone (probably the international, firmware GM21AA), and extract its contents into a directory. In order for the tool to work, you need the OnePlus USB drivers installed on your PC. Plug the phone into your PC with it on, and enable USB file transfer. Open File Explorer and you should see a drive labeled "OnePlus drivers" or similar. Open it and run the driver setup executable file. You'll also need ADB to make your phone reboot into a mode that will allow the tool to perform its tasks. Here is a guide to installing ADB:
https://www.xda-developers.com/what-is-adb/
Once you've set that up, make sure the phone is plugged into the PC and the MSM tool is open. Make the phone boot into edl mode by typing
Code:
adb reboot edl
and once it says Connected next to a COM port in the tool, press start. Don't interrupt the process until it completes the download and the status message turns green. The phone should automatically reboot. This method is arguably more risky than using the local upgrade option, so do it at your own risk.
Q3: Make sure that OEM unlocking is turned off in developer settings and that the bootloader is locked (if the bootloader is unlocked, you'll see a yellow warning message after you power on the device from a power off state). Without an unlocked bootloader it would be pretty difficult to make any deep modifications to the device.
Hi @Zocker1304 and @TManchu,
Please let me thank you very much first for your kind and detailed reply, this is really welcome.
@Zocker1304:
I checked using the ADB/Fastboot connection that indeed, the Bootloader is locked so, that looks good.
Also installed (using a separate Google account) DRM Info app to confirm that the Widevine is properly installed and at L1 level which indeed again, looks good.
@TManchu
Thank you again for your very detailed reply! This was exactly what I needed as information.
I did already exactly as mentioned for the #1 so, it looks I should be good now with a proper rom from OnePlus (and did a full wipe in the Recovery boot mode)
For #2, I think I will skip that since as you rightly said, with #1, it should be fine so, prefer to keep with the recommended step.
For #3, we are covering what Zocker1304 mentioned too and I could confirm it.
My only concern about #3 was that you can actually relock the bootloader but (and please correct me If I am wrong), you can only do so if you are using stock OnePlus images (to date...seems like dev teams are working to have this changed? Bootloader locked with custom firmware?) which then means the image is safe.
I suppose the last item was my only open query for your thoughts but so far, the handset looks fine.
Thanks to you and the community, I have learned about the A/B partition scheme, msm tool, Fastboot/Recovery mode and Bootloader and ADB tools.
It is always good to learn more about the tech we use (especially phones, we have so many sensitive information stored into them today).
Not being careful could potentially means quite a lot of troubles down the road with Ransomeware/data leak tools.
Of course again, I could have simply purchased a JP phone from a brick and mortar shop next to my place and be fine with it. :silly:
brissoukun said:
.
For #3, we are covering what Zocker1304 mentioned too and I could confirm it.
My only concern about #3 was that you can actually relock the bootloader but (and please correct me If I am wrong), you can only do so if you are using stock OnePlus images (to date...seems like dev teams are working to have this changed? Bootloader locked with custom firmware?) which then means the image is safe.
I suppose the last item was my only open query for your thoughts but so far, the handset looks fine.
Thanks to you and the community, I have learned about the A/B partition scheme, msm tool, Fastboot/Recovery mode and Bootloader and ADB tools.
It is always good to learn more about the tech we use (especially phones, we have so many sensitive information stored into them today).
Not being careful could potentially means quite a lot of troubles down the road with Ransomeware/data leak tools.
Of course again, I could have simply purchased a JP phone from a brick and mortar shop next to my place and be fine with it. :silly:
Click to expand...
Click to collapse
No problem! I’ve just done some reading and from what I understand, re-locking the bootloader on anything other than a completely stock ROM will result in a bricked phone. I believe this is due to the way Android handles data encryption. If what you’ve heard is true, being able to lock your bootloader on a custom ROM would be great for device security. However, should something go wrong with the ROM having a locked bootloader might make it more difficult to fix.
I know that there are ways to sign system and boot images so that you can lock the bootloader with them installed, but I think that would still show a warning though I'm not sure.
Anyways, if all the build dates and numbers in the system info are correct, the firmware should be stock and as long as the bootloader is locked too, I don't believe you can tamper with that.
Hi Gents,
Thank you very much for the answer to the thread and much appreciated.
Apologies for not getting back to you all earlier as yesterday was family day...haha!
Well, since things looked good on the OS and the build, I went ahead and started to use the phone properly setting up my accounts. It did give me some incentive to get all my sensitive accounts setup with 2FA so that in case I get hacked with my passwords in the future...they would still need the 2fa (using Google Authenticator).
I did check also all system apps/running process and didn't see anything shady.
Just for reference, here were the type of articles I was refering too for the OS being plagued with malware even out of the box:
Page_theverge.com/2019/6/6/18655755/google-android-malware-triada-ota-rom-ads-spam-oem (sorry gents, new account, cannot put links yet)
However here, it seems it is due to lax review from the maker to third party tools which were including malware...
To have the same level on the oneplus I bought from the HK shop, they would have needed access to OnePlus Dev team to inject the malware in official image (knowing anyway I have re-installed a new image from the local update).
Otherwise, I was reading on the web about the fact to relock the bootloader with a custom roam and there seems to have a lot of messages but not concrete steps. It seems it depends a lot on phone model and brand.
When you are checking
Page_gizmochina.com/2019/06/10/relock-bootloader-oneplus-7-pro/
This is where you can read at the end:
"The above method only works if OnePlus 7 Pro is running on stock recovery and stock firmware. The ability to relock devices running custom recovery is expected in the next few weeks. "
That was published last month so, not sure if they got this to work on the OnePlus 7 pro yet.
So that's it, I am now using my new device which looks to work great and hopefully, won't get any bugs down the road.
I appreciate you taking the time to get back to me and will continue to learn about android.:good:
flashed from graphene os and back to stock during stock flashing something failed and gives me a black screen and goesinto the screenshot provided
You can try to go through the applicable steps in this guide:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
Like installing the USB drivers, and SDK platform tools.
Then put the phone in fastboot mode and download an image from google and do a "flash-all.bat"
JohnC said:
You can try to go through the applicable steps in this guide:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
Like installing the USB drivers, and SDK platform tools.
Then put the phone in fastboot mode and download an image from google and do a "flash-all.bat"
Click to expand...
Click to collapse
it wont work , that is what caused the issue, there is no adb or fasboot commands as the phone has nothing to load or read, it was flashing the official latest stock firmware using the flash-all.bat, then after the first rebbot and waiting for devices it goes to a black screen and shows what i put in the screen shot,(i believe the battery died during flashing) there is two modes it goes into the qusb which is the qualcomm download mode and some other mode i cant tell neither can the pc device find drivers to read the phone, techinically this phone is not fixable using normal methods , but i believe there is a way to flash to firmware back on,i have looked into using edl and qspt flashing but it still doesnt read the phone, any help would be greatful i have device protection but they are sending me a refurbished phone i would rather try to fix this before i do get the replacement, as it was a new and working device
i have been able to find a working qualcomm driver is there anyway to edl or msm file for the pixel 4a to fix this, now that the phone is being read properly it should be able to take commands as it is reconized as a modem driver or port
Any Ideas Why Its Failing , says sahari protocal failed
files needed to repair phone, anyone able to extract or have files
RAM file (MPRGXXXX.mbn), e.g: MPRG8916.mbn
Boot file (XXXX_msimage.mbn), e.g: 8916_msimage.mbn
miko12312 said:
files needed to repair phone, anyone able to extract or have files
RAM file (MPRGXXXX.mbn), e.g: MPRG8916.mbn
Boot file (XXXX_msimage.mbn), e.g: 8916_msimage.mbn
Click to expand...
Click to collapse
I did the same thing as you trying to got back to stock. Still trying to find those files to unbrick myself.
vabeachboy0 said:
I did the same thing as you trying to got back to stock. Still trying to find those files to unbrick myself.
Click to expand...
Click to collapse
I believe Qualcomm is the ones that obtain these files not Google , only other way is to dump the files from download mode on a working device
I'd like to help by dumping the required files, I didn't know anything about EDL before doing research for this thread, but as I understand using EDL mode require a device-specific non-free "loader".
I'm trying to use B. Kerler's EDL tool (https://github.com/bkerler/edl) but fail because it doesn't have the proper loader file in its database.
If anyone come across the loader for the Pixel 4a (000e60e10066000a_3ef72a02fb931be1_fhprg.bin), I'd be happy to share boot and memory dump from my phone.
I encountered the same situation as you, did you solve it?
Older thread I know, but I've used EDL mode (on LG phones) to save partitions and write partitions.
But you have to have a 'programmer file' for the specific device for it to work. Aka a 'firehose' file for the specific device / chip.
Some mfg's make this available, some don't. Google does not. So, even having the file(s) you want to flash won't help, not if you don't have the firehose file.
sorry, cheers
Has anyone figured this out? Could really use some help. Thank you
Did anyone managed to unbrick phone? I bricked my phone. Now it's just black screen.
mizzunet said:
Did anyone managed to unbrick phone? I bricked my phone. Now it's just black screen.
Click to expand...
Click to collapse
Only suggestions are the go to software of choice,, pixel flasher or android flash tool, both need bootloader unlocked
@hammered58 Gladly, I was able to get it back. I was trying to relock bootloader with custom ROM. But failed.
Has anyone relocked bootloader with LineageOS/custom ROM?
I was following https://forum.xda-developers.com/t/signing-boot-images-for-android-verified-boot-avb-v8.3600606/ to sign boot and recovery images. Then flashed and relocked bootloader. But phone stuck at black screen. Has anyone managed to self...
forum.xda-developers.com
mizzunet said:
@hammered58 Gladly, I was able to get it back. I was trying to relock bootloader with custom ROM. But failed.
Has anyone relocked bootloader with LineageOS/custom ROM?
I was following https://forum.xda-developers.com/t/signing-boot-images-for-android-verified-boot-avb-v8.3600606/ to sign boot and recovery images. Then flashed and relocked bootloader. But phone stuck at black screen. Has anyone managed to self...
forum.xda-developers.com
Click to expand...
Click to collapse
Glad u got it going, the only time I relock is when I sell the phone, otherwise I have no need as all my apps work with unlocked
hammered58 said:
Glad u got it going, the only time I relock is when I sell the phone, otherwise I have no need as all my apps work with unlocked
Click to expand...
Click to collapse
Right. Every apps working even on unlocked state. But would be nice to get rid of the warning while booting.
mizzunet said:
Right. Every apps working even on unlocked state. But would be nice to get rid of the warning while booting.
Click to expand...
Click to collapse
I will second that, unfortunately I don't think it's possible, at least not that IAM aware of
I tried putting the beta of OOS13 on my Oneplus and now i get that error message and ive been trying for so long.
the serial number is fb7b98a9
Flash by edl if you can't do it then pm I'll fix it by tv
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Good luck
applyscience said:
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Click to expand...
Click to collapse
applyscience said:
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Good luck
Click to expand...
Click to collapse
The tool that you linked doesnt have o2 as he is saying in the guide.
Also yes, i tried flashing OOS13 and it just corrupted my device i've been endlessly working to fix it all day
SubColdSnow said:
The tool that you linked doesnt have o2 as he is saying in the guide.
Also yes, i tried flashing OOS13 and it just corrupted my device i've been endlessly working to fix it all day
Click to expand...
Click to collapse
1st of all flash with op9pro india msm with uncheck sah and check lite firehorse if u have hard bricked ur device then the next steps as mention above
rizzmughal said:
1st of all flash with op9pro india msm with uncheck sah and check lite firehorse if u have hard bricked ur device then the next steps as mention above
Click to expand...
Click to collapse
i tried and just get device does not match image
SubColdSnow said:
i tried and just get device does not match image
Click to expand...
Click to collapse
try it again. if anything, you will be attempting on the other slot. Many haves had issues and it just started working.
it could have been slot related, or possibly some minor detail that is finicky. (ex. you usually want to start the msmtoolkit and let it stay in the "waiting for device" phase and plug in your phone (which should be in EDL mode . youll know by the peeps of it habitually connecting/disconnecting on your PC)
assure you have india selected, assure you have the proper conditionals on/off per the guide's explication.
Assure you have the qualcom drivers installed, and they reflect the naming convention.
follow along the guide again and Just keep attempting it and don't get discouraged. Part of the reason people offer guides here is that they themselves failed many times until they got they figured it out and are trying to save people from it.
youll get it, dont worry.
I had this problem because I flashed a custom kernel on a custom rom today
SubColdSnow said:
i tried and just get device does not match image
Click to expand...
Click to collapse
try the modded msm tool. it worked for me.