So... I was using this android app called BugJaer or something like that and it bricked my phone or at least I think.. it's stuck in fastboot mode and I tried flashing stuff to it and it hasn't work I'll include pictures and the name of it is like holi or something and yes the bootloader is unlocked .
Follow mg lineage guide, but replace the lineage ota with either the android 11 ota from scanman0's guide or the latest android 12 one from the Oxygen Updater app. Make sure its a full ota if you do the latter method.
Related
Hello, everyone. Im pretty new to all of this stuff so please bear with me. I was trying to root an old phone and as I learned more and more about rooting processes (wanting to use majisk) I realised the particular phone (SM-J737R4) is a crackhead and not a lot of stuff is available for it. Anyways I saw that someone with the same model was able to do it using this thread even though it's for a different model. But to use this guide I needed to have android 8.0 and when I got the phone it already had 9.0. I knew downgrading via Odin was possible on samsungs but when I tried googling the Stock firmware the baseband version for the 8.0 downloads were always different. Current Baseband: J737R4TYS8BTE1. And apparently trying to flash a stock firmware that doesnt exactly match your device bricks your phone, so I'm kinda confused on what to do next. And I may be confused on other things as well. Hopefully someone can help.
Tl;Dr: Trying to flash back to 8.0 from 9.0 on SM-J737R4 but stock firmware downloads dont match device.
Any Samsung device what comes with unlocked boot-loader - or whose boot-loader can get unlocked - can easily get rooted. Rooting a phone's Android doesn't depend on Android version.
jwoegerbauer said:
Any Samsung device what comes with unlocked boot-loader - or whose boot-loader can get unlocked - can easily get rooted. Rooting a phone's Android doesn't depend on Android version.
Click to expand...
Click to collapse
yeah but when I was trying to root with majisk the flash failed and when I looked up a TWRP one didnt exist for this model. The forum was a twrp for my model, but it was made for 8.0.
danalexcoro said:
yeah but when I was trying to root with majisk the flash failed and when I looked up a TWRP one didnt exist for this model. The forum was a twrp for my model, but it was made for 8.0.
Click to expand...
Click to collapse
TWRP is a Custom Recovery used to flash a Custom ROM. Installing TWRP prevents Android to receive OTA updates.
You don't need TWRP, but only the "Magisk Manager" app to root phone's Android.. And, of course phone's boot-loader must got unlocked before.
By means of "Magisk Manager" you create a patched boot.img what you then flash via "ODIN" what requires you have installed latest Samsung USB drivers on Windows computer.
Important: The "patched_boot.img" comes in .ZIP-file format. You have to convert it into .TAR-file format using Windows app "7ZIP" before you can use it with "ODIN".
Load .TAR-file into ODIN's AP-section, flash it.
Good afternoon everyone.
I got interested in putting a custom rom on my Galaxy Note 8 I have laying around (Current Daily driver has been upgraded to a Note 20 Ultra so I have no hurry to fix this issue.)
I followed the steps from one of the forum guides and installed TWRP, the first thing I noticed was that my Note 8 had 2 System directories while this is supossed to be a A only model. (Which struck me as odd.) After installing a android 11 Rom (A Only) I was stuck on the boot screen not loading any further. I found this logical as Android 11 is not really supported as of yet on this model.
I then decided to grab Havoc OS seeing as that was a stable version that should run properly i've seen people on Youtube install it on their S8's without a hitch. After installing this the way the guide told me I got stuck in a boot loop. (Also used an A only ROM) My final attempt will be downloading an A/B ROM and see if that works (Which i genuinly doubt.) but will update this post when that's finished.
On the post I also have added a screenshot of what I see when trying to install an Image. My question to you guys is, does this phone have a A/B configuration after all or am I doing something wrong?
Edit: AB was also not the solution.
After rummaging around a bit more with the phone I found out that i was using an extremely out of date version of the Pie Vendor. I looked at download by Version number instead of by date. Reinstalled Havoc, installed pie vendor.
Now the phone reboots into downloading mode. It's been this way around 10 minutes now will post an update in about an hour or so of leaving it in that state.
QuirkyTechGuy said:
After rummaging around a bit more with the phone I found out that i was using an extremely out of date version of the Pie Vendor. I looked at download by Version number instead of by date. Reinstalled Havoc, installed pie vendor.
Now the phone reboots into downloading mode. It's been this way around 10 minutes now will post an update in about an hour or so of leaving it in that state.
Click to expand...
Click to collapse
Odd. Truly. It could be due to the first install of GSI version. Here's what I suggest.
I hope u have a back up of your old rom, if so, flash it back. If not, check your twrp version. Update it to latest. Flash a non gsi rom. Boot the phone. If it boots and you have it running, then flash a gsi rom .
maxed4901 said:
Odd. Truly. It could be due to the first install of GSI version. Here's what I suggest.
I hope u have a back up of your old rom, if so, flash it back. If not, check your twrp version. Update it to latest. Flash a non gsi rom. Boot the phone. If it boots and you have it running, then flash a gsi rom .
Click to expand...
Click to collapse
I sadly forgot to make a back up of the rom which in hindsight is stupid of me. I did check and have the latest TWRP version, and managed to get LineAge OS 17.1 working without it being Treblized .
Should i now go on with the procedure of trying to flash a GSI rom with the Treble Convert?
QuirkyTechGuy said:
I sadly forgot to make a back up of the rom which in hindsight is stupid of me. I did check and have the latest TWRP version, and managed to get LineAge OS 17.1 working without it being Treblized .
Should i now go on with the procedure of trying to flash a GSI rom with the Treble Convert?
Click to expand...
Click to collapse
Let's take a back up first and then try. Which tutorial are u following.
Install Android 11 (R) On Any Treble Device ( Detailed Guide)
This way you can install Android 11 On any device without the need of waiting for your manufacturer to push the latest update.
xtremedroid.com
And try Google or aosp gsi from here https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Here's @corsicanu thread for instructions.
But it's for android 9? M not sure though
[AOSP][Treble][G95*F/FD] hadesTreble [03.09.2019]
Disclaimer I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it...
forum.xda-developers.com
Hi, do you know if there is any way to go back to android 10? Thank you
The best way would be to try finding custom ROM for your phone which is running Android 10.
But isn't there a way to flash the previous stock rom of Android 10? The previous version
Just use the MSM tool for your particular device. You can download tools to flash back to stock Android 10.
What do you not like about Android 11?
Omegapsy said:
Just use the MSM tool for your particular device. You can download tools to flash back to stock Android 10.
Click to expand...
Click to collapse
Do you know exactly what tools would be needed?
Thor_2 said:
Do you know exactly what tools would be needed?
Click to expand...
Click to collapse
You need to have previously unlocked bootloader
Put your phone in EDL Mode and use a brick recovery MSM Tool
AFAIK, you do not need an unlocked anything to use the MSM tool. It is pretty bad-ass. Of all the phones I have had, the OnePlus' are the most brick resistant, and that was before using this tool. Now its, like, bulletproof...
there is also a downgrade build here: https://www.thecustomdroid.com/oneplus-nord-android-11-downgrade-guide/ if you put that file in the root dir then go to system updates and choose local updates from the settings you are supposed to see the file and it will let you downgrade. not working for me though. it can see when i the official 10.5.11 build but tells me im not allowed to downgrade. when i switch and use the downgrade build it sees nothing.
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Link575 said:
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Click to expand...
Click to collapse
Lineage is using own kernel and boot.img on A11 so in the short run it is not going too make any difference, but when Lineage moves forward to A12 the OEM Firmware has newer drivers and is updated sooner, has more OEM features and bugfixes as well as no carrier bloatware.
It is possible that OP will neuter the Carrier firmware with an OTA update to prevent cross flashing device away from the Carrier rom in the next OTA update by preventing fastbootd from flashing the us oem from a carrier phone.
They have already removed fastboot boot command to boot a boot image without flashing it for test before you flash and to allow Magisk to make a backup of the original boot.img before adding Magisk.
I would convert NOW, before they decide to slam the door on this ability with a future OTA that will not allow you to downgrade and prevent this as they are under contract with the carriers to not allow this to be done.
Ok, thank you for the explanation. Guess I'll back everything up and convert it.
scanman0 said:
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Click to expand...
Click to collapse
This worked perfectly after following your convert guide and upgrading to 12. Downgraded back to 11 so I could install lineageOS. Thanks again!
This reddit post has a link to an English version of the downgrade apk which makes it a little easier.
keeps saying verification failed
weirdfate said:
keeps saying verification failed
Click to expand...
Click to collapse
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
I m trying as well .. but stuck with verification failed message just as scanman0 I m on stock android12 no root if anyone know how to fix it ... please assit
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
radekmazur said:
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
Click to expand...
Click to collapse
I did not have to remove root. I used the version posted that does not check for root but maybe there's a different reason.
Does the downgrade apk have to be sideloaded via ADB?
T3CHN0T33N said:
Does the downgrade apk have to be sideloaded via ADB?
Click to expand...
Click to collapse
Just place apk in phones working directory, same path where your downloads folder is. Then install from there like any other apk and run. I also kept the FW file in the same directory but I'm not sure if that was necessary.
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
T3CHN0T33N said:
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
Click to expand...
Click to collapse
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Link575 said:
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Click to expand...
Click to collapse
When you say "screwed things up" what do you mean? How did it effect the install?
T3CHN0T33N said:
When you say "screwed things up" what do you mean? How did it effect the install?
Click to expand...
Click to collapse
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Link575 said:
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Click to expand...
Click to collapse
Weird, for me it just closes the app and does nothing, both the official and emergency ones. I even tried adding it to magisk's deny-list.
But I just restored the boot image via magisk (didn't restart) and it works now...
scanman0 said:
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
Click to expand...
Click to collapse
Yes I factory restored the phone and tried again. Still fails every time
Has anybody had any luck figuring out the verification failed message? I too have tried both the official and emergency apps, of course I can't read the actual message in what I presume is Chinese, but it doesn't do anything and the other version says verification failed. Have not rooted. Kind of at a loss right now and all I want to do is install Lineage! I've already got my unlock token from OnePlus, but my understanding is that the phone still needs to be on A11 before installling Lineage.
There doesn't seem to be a thread for the G31 and this was the closest to it...
Is anyone able to guide me on a rollback from Android 12 to 11 on a Moto G31 or any other similar phones? I've read things like not being able to lock the bootloader again .. is it really not worth doing this?
I second this request. I've looked at some guides online, but it seems the rom files names don't match up with whatever commands I'm being told to flash using fastboot. For example the command is to "flash bootloader bootloader.img", but i only have boot.img and so on. Also I have a lot of more sparsechunk files than I'm being told to flash.
It would be great to get a correct guide on the fastboot flash process for the stock Android 11, as Android 12 on this device unfortunately is laggy, battery draining and slow to charge.
The rom I'm trying to flash is XT2173-3_COFUD_RETEU_11_RRWDS31.Q3-26-83-7_subsidy-DEFAULT_regulatory-DEFAULT_cid50_CFC.xml from https://mirrors.lolinet.com/firmware/motorola/cofud/official/RETEU/
As this seems to be the last 11 rom for he G31 before it switches to 12