[a207F] Rooting? - Samsung Galaxy A20 Questions & Answers

After a few failed attempts and some net digging, i decided to downgrade my firmware to an early android 9 that i grabbed from samlabs.
i figured from this "workaround" that i can finally get magisk working with my device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but due to my limited knowledge, i don't exactly know what he mean't here, like... how do i flash something with a odin tarball???
and how do i even extract the files mentioned?
can anyone lay it to me straight?
Github Thread
PS: my bootloader is already unlocked, i tried the simple method that makes sense to me and just flashed a patched AP of the aforementioned Firmware but unfortunately hit
the usual dead end (Secure check fail, recovery.img).

Note that the bootloader with Android 10 and later on the Samsung Galaxy Tab A 8.0 (2019) [SM-T290] is suffering from this same issue.
Click to expand...
Click to collapse
It is about a different device, but may work.
Just replace the aboot.mbn.lz2 and vaultkeeper.mbn.lz2 in a tarball (.tar file) with aboot.mbn.lz2 and vaultkeeper.mbn.lz2 from last Android 9 tarball (.tar file)
I don't remember which one contains these files, so find one with them

Related

Flashing Bootloader & Modem via Odin Problem

Hi everyone, I'm having a couple of problems flashing the required Rom's Bootloader & Modem (XXU1COI3 & COI3) for my phone (N910G - 32Gb).
So the problem look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I had also try to extract the pit file from the phone using terminal emulator on Android. Used that pit file along with the flashing of Bootloader & Model. This is what it shows:
I have previous problem similar to this before. But it seems to work when I used the PDA tab while flashing both the Bootloader and Modem as a single tar.md5 (or tar file can't remember exactly).
I would be very appreciated if someone could merge the 2 file together (so I can give a try) or come to a solution for those problems.
Cheers!
untick autoreboot
Second this.... also unticking AR did not help.
Don't use Re-partition !
And don't forget to power off the phone (minimum 15 seconds) and start in download mode directly before flashing BL and CP

Keyboard Glitch/Broken after Rooting/Flashfyre

Hi guys,
I have a fresh S7 SM-G930V(Android 6.0.1). Which i logged in via google and it downloaded all my previous apps on my old phone(i assume it automatically does)
I was following https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039.
And now my keyboard is now starting to look weird
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I completed all the steps and rooted to the following image "Samsung_G930x_QC_Rooted_BOOT.TAR (any Samsung Galaxy S7) (MD5 hash 948A01ECCF280828DFD13AC366F6FE85)"
and used Odin3_v3.12_PrinceComsy.zip as opposed to the other odin.
Any ideas besides using another keyboard app?
EDIT: Just flashed back to G930VVRU4API3, which i thought was my stock rom but has a purpleish first time start up which i thought should be blueish?
Going to try and re-flash a root after work again.
UPDATE2: I Follow the rooting/xposed steps again and now i got my normal keyboard back. The difference is that the verizon startup is white/red while when i first ever used the phone it was a blueish/purple verizon start up. But i feel that it was definitely 6.0.1 with PI3.
Accessing the phone via cable seems extremely slow but thats for another thread...
I am now rooted with a working keyboard, now time to work on the other issues....

[HELP] [AOSP 10 BUILD] Update requires 'goldfish_arm64'.

Hello everyone,
since this awesome Tablet isn't getting Updates anymore I tried to build my own Android Version (10) with help of the AOSP Documentary.
Everything works smooth and fine, but when I try to flash this freshly created build, I get an error:
"Device product is 'baytrail'.
Update requires 'goldfish_arm64'."
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried resolving the problem by getting to know what exactly is goldfish in the first place. So I found, that the 'goldfish' is in the Android Kernel for 4.x versions. I simply just don't understand why the bootloader is attatched to a specific android version. Strange.
Additionally, Lenovo Support gives the whole Open Source .zip for both Lollipop and Kitkat versions, so I have full build .zips of the "old" versions.
Is maybe the boot.img file the problem? I extracted it from Lollipop.
Any help will be appreciated.
Same issue.
I think you need to edit the upadte-script.
Hello. Could you please share your previous build that worked? Will it work on the Tab 2 - 8 inches?

Flashing with ODIN problem.

Hi guys, i've bought note 20 ultra recently, i have to flash stock rom to my note fan edition phone but there is a problem.
I've tried several versions of odin in order to flash but no luck.
I had floydq v6.0 before, now phone doesnt even booting it says only "official released binaries are allowed"
Here is my steps:
- I downloaded binaries for N935F from sammobile,
- Tried to flash but no luck it stucks at SetupConnection or NAND Write Start or Set Partition part
- Then i came across with a thread that says i have to enable OEM Unlock but the thing is i couldnt see that switch in my developer settings page, i tried several things
- Now i am trying oem-unlock with fastboot but the thing is fastboot does not recognize my phone, but before the brick adb could see my phone idk what am i doing wrong
- I think i successfully installed the right drivers such as (Google Driver, Samsung OEM driver)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can anyone help me about that problem?
Using odin v3.13.1 solved my problem.

[SM-N9005] No commands, Goes back to stock recovery instead. After installing TWRP.

Tried to flash TWRP in SM-N9005, But odin says PASS.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried go to the recovery to see results, Goes back to the stock recovery.
Device is android 5.0 (Lolipop). Any help appreciated!!
Most likely your bootloader isn't unlocked. Try unlocking it again.
This only happens when ODIN tries to copy the image to the selected sector but the device is locked to use a certain image only in that mentioned sector.
XDHx86 said:
Most likely your bootloader isn't unlocked. Try unlocking it again.
This only happens when ODIN tries to copy the image to the selected sector but the device is locked to use a certain image only in that mentioned sector.
Click to expand...
Click to collapse
Nvm got it working, i have to make a proper file.
bulieme0 said:
Nvm got it working, i have to make a proper file.
Click to expand...
Click to collapse
Or the file may be corrupted, didn't think of this possibility. Happy to know it worked anyway mate!

Categories

Resources