Question Unsuccessful installation of GSI firmware (HELP) - Samsung Galaxy A12

It seems that I did everything right, I installed the custom rainbow kernel on the stock firmware, the kernel worked, there only at startup it gave out the message "SSHL Warning" like so.
When I decided to install GSI, a bootloup occurred. You can write the reason or guesses.
I have only one screenshot left from TWRP.
Thanks in advance!
{
"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"
}

what model do you have? If it is an A127F then use chondoe flasher, if it is an A125F, maybe try using a kernel if that doesn't work maybe chondoe flasher will work.
ChonDoe Flasher is below (For me ChonDoe always worked)

TheWorldYT said:
what model do you have? If it is an A127F then use chondoe flasher, if it is an A125F, maybe try using a kernel if that doesn't work maybe chondoe flasher will work.
ChonDoe Flasher is below (For me ChonDoe always worked)
Click to expand...
Click to collapse
i have A125F i used rainbow kernel

Test Superior

lil_kyrick said:
i have A125F i used rainbow kernel
Click to expand...
Click to collapse
Try to flash a new version of lineage (BgS) with ChonDoe Flasher (Like Lineage 19 or 20)
here are how you install the gsi with chondoe flasher:
Rename the .img file to system.img then copy the ChonDoe_Flasher.zip file at post #2 in the directory where the .img file is, then flash the ChonDoe_Flasher.zip as a zip file. Then, flash the kernel, and format data, then reboot your phone!
Here is a link to lineage 19 BgS: https://sourceforge.net/projects/an...2-UNOFFICIAL-arm64_bgN-secure.img.xz/download (Unzip to get the image)

Related

[SOLVED] Serious problem - can't install any rom

Hello,
Today I've been trying to root my HTC One S (S3) and install CM11 (cm-11-20140210-SNAPSHOT-M3-ville)
1. I made successfull S-OFF
{
"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"
}
2. Installed wrong recovery (r2-modaco-recovery-clockwork-touch-ville.img)
3. Then installed correct (working) recovery for s3
4. Flashed my boot - fastboot flash boot boot.img
5. Made backup
6. Factory reset (everything)
7. Tried to install cm *.zip but here it is (tried also another CM's):
What is more phone freezes during start, display non-stop the same:
Help me please, what can I do ?
marcinostry said:
Hello,
, what can I do ?
Click to expand...
Click to collapse
did you downloaded the rom fir your device ?
cause, as i look at your pictures, that rom isn't for your device, see picture number 2,
or there's something wrong at updater script, contact your rom developer about the updater script
edit : you can aslo try to replace your recovery with the others, maybe it's the problem too
http://download.cyanogenmod.org/?device=ville
Here is source of my roms. However there is no info if they are for s3 or s4 ..
Problem SOLVED
ROMS located on the cyanogenmod site are for ville (but not ville c2).
I used "Stable: cm-11-20140110-UNOFFICIAL" from http://forum.xda-developers.com/showthread.php?t=2527962 because it's especially for C2
Before flash I had to flash the kernel file from THIS NEW version
Then made factory reset in TWRP 2 Recovery (versions for c2 - http://techerrata.com/browse/twrp2/villec)
Finally, installed the rom from xda and everything works fine !

[GUIDE] Change baseband without flashin whole firmware through ODIN

Hi,
I see many people flashing whole firmware through ODIN just for changing their baseband (specially CM users). A simple way exist just for changing baseband.
What you'll need?
Rooted device
busybox installed
Terminal emulator
Baseband to flash
Click to expand...
Click to collapse
So what you need to do?
Extract firmware tar file & put modem.bin.md5 on your device as /sdcard/modem.bin.md5 (internal sdcard)
Fire up terminal emulator, get su rights by typing in terminal su
Now type
Code:
dd if=/sdcard/modem.bin.md5 of=/dev/block/mmcblk0p13
and hit enter.
Click to expand...
Click to collapse
Thats all...:good:
You can do this directly from CM based ROMs also...
As usual i'm not responsible for bricked devices...!
Newbie question. What is the help of flashing a new baseband ?
I have LQE (ROMANIA) baseband. Can I flash LQL (ITALY) baseband ?
Confirmation
Tested -> Working!
After flashing this, restarted my phone and a BIGGGG log file apeared in /data.
Look:
{
"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"
}
P.S. Sorry for new post! I had to edit the previous one....
BOOTMGR said:
Hi,
I see many people flashing whole firmware through ODIN just for changing their baseband (specially CM users). A simple way exist just for changing baseband.
Click to expand...
Click to collapse
There is also a flashable zip by t4n017.
So you can't make typos and brick your phone

FAILED (remote : variable not found) when flashing stock images

{
"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 get that error message when flashing the stock images on my unlocked google pixel 3. I now have no OS on my phone I don't believe as booting it up shows "unknown command".
Anyone know what to do?
https://imgur.com/0IjGoic if the image doesn't load
HueBearSong said:
I get that error message when flashing the stock images on my unlocked google pixel 3. I now have no OS on my phone I don't believe as booting it up shows "unknown command".
Anyone know what to do?
https://imgur.com/0IjGoic if the image doesn't load
Click to expand...
Click to collapse
Try flashing the system.img to both slots.
Sent from my [device_name] using XDA-Developers Legacy app
I had the same problem but managed to resolve it.
the way to do it is to do the followings:
1) Install the updated adb tool files from google official framework website here (Very very very important)
https://developer.android.com/studio/releases/platform-tools
2) download the factory image file and unzip it inside a folder. For example "A"
3) after unzipping the rom file, you will find another rom file, unzip it also to the same folder "A"
4) unzip the adb tool downloaded from step 1 and put them in the same folder "A"
5) Double click on "Flash all" to execute the command.
6) Enjoy

Lenovo K9 (L38043) cstom rom AOSP 9.0 v123

Hello guys today i will show you how to download Aosp rom (GSI) with android pie on Lenovo K9 (L30843)
Download TWRP first: https://mega.nz/#!tFcm1IYb!nN6H210DoyYqjL0WEnI-I9skClDPEO0gl82H5My-gq4
if you have not unlocked the bootloader: https://www.howtoapps.info/how-to-unlock-bootloader-lenovo-k9/
Aosp rom link: https://mega.nz/#!cAdFwSoI!RqVg18SU-adnmltKV1JuL_1NB_V9KCemYX8fZwUyzkA
First step: Go to the TWRP.If you have internal storage (0mb),Go to wipe/advanced wipe/mark data/repair or change file system/change flie system/EXT4 and you're done
I recommend you save your rom to sd card not have thousands of quarrels
Second step: Go to micro sd card/install image/your recorded aosp rom/mark system image/slipe to confirm flash
Third step: gapps link: https://mega.nz/#!9dFkWY5I!JKX80Udn2ZmTgRuGiwgcdRLQXEBssowK7xUOvL2wW4E
Install zip/mark open_gapps-arm64-9.0....../swipe to confirm flash/reboot system now
the rom leaves without a logo,shows its original logo of Lenovo,And after a while the inscriptions orange state are removed and the android logo appeared.
Mention below in the comments if there are bugs!
{
"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 can see only TWRP even after installing custom rom
irssharma said:
i can see only TWRP even after installing custom rom
Click to expand...
Click to collapse
you have to recover stock firmware and try again.
irssharma said:
i can see only TWRP even after installing custom rom
Click to expand...
Click to collapse
It also happens to me quite often.

How to return to stock and lock

I am using TWRP by brigudav 3.7.0_12-1-surya, with previous Lineage OS and did flash lattest surya_global_images_V13.0.1.0.SJGMIXM_20220725.0000.00_12.0_global with MiFlash version 2016.08.30.0 with the option flash_all_lock.bat . It did not finished from MiFlash (took more than 1000s) but the ROM and all partions seems flashed right, except recovery that remains TWRP and of course did not relocked.
How do i go back to full stock and relock ?
{
"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"
}
ushiyama said:
I am using TWRP by brigudav 3.7.0_12-1-surya, with previous Lineage OS and did flash lattest surya_global_images_V13.0.1.0.SJGMIXM_20220725.0000.00_12.0_global with MiFlash version 2016.08.30.0 with the option flash_all_lock.bat . It did not finished from MiFlash (took more than 1000s) but the ROM and all partions seems flashed right, except recovery that remains TWRP and of course did not relocked.
How do i go back to full stock and relock ?
Click to expand...
Click to collapse
Use TWRP to flash a recovery rom then Miflash.
The version of Miflash you are using is obsolete / the path / the rom name needs to be reviewed.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
NOSS8 said:
Use TWRP to flash a recovery rom then Miflash.
The version of Miflash you are using is obsolete / the path / the rom name needs to be reviewed.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Click to expand...
Click to collapse
TY
Your post https://forum.xda-developers.com/t/miflash-guide-use-xiaomi-flash-tool.4262425/post-87870641 on that thread actualy was what i did and what worked.

Categories

Resources