*Current behaviour of the device*
When trying to power it on, the device displays several text, it looks like it's debugging itself:
{
"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"
}
Now, while this device displays this texts, I push the following button to get to odin mode, "volume down+home+power button". It should have displayed a warning about entering odin mode, (to which pressing volume up continues going to odin mode and volume down cancels it), but it displays nothing-just blank. But even though it displays blank, I pressed volume up, to which I got then to odin mode.
Now, I have already downloaded the firmware for this device. I have attached BL_*tar.md5, AP_*tar.md5, CP_*tar.md5, CSC_*tar.md5 to the fields of odin, and unchecked "auto reboot", but then itt failed to flash, Odin failed writing the PBL.bin from BL_*tar.md5, but this failure did not gave me up!
AP_*tar.md5 consist of:
boot.img
NVM.img
recovery.img
system.img
I have extracted the files from AP_*tar.gz and tried flashing each of *img from it.
Extracting system.img from AP_*tar.md5, compressing it with `tar` and flashing it returned success from odin but it did not saved the device. No good news.
Extracting NVM.img from AP_*tar.md5, compressing it with `tar` to `NVM.tar.gz` and flashing it returned success from odin but it did not saved the device. No good news.
Other *img, (boot.img and recovery.img) failed to flash.
As a last resort, I would like to write a firmware that displays, "Hello world".
If you find ambiguities in this post, feel free to write.
On a side note: Is there a post about compiling boot.img, system.img, recovery.img?
Related
Hi, yesterday when i using my phone,it suddenly hang,then i perform a reset (hold power button) and it reboot to the OS, after receiving a call it hang again, then i using the same method to reboot and it stuck at the samsung logo...
Been searching inside the forum for the way to recover it,now i giving up and asking for help...
Before i get it rooted using exynos abuse but i unroot it due to gamevil games,situation for my phone now is:
Stock samsung firmware
CANNOT boot in recovery mode
CAN boot to download mode
HANG at samsung logo
below is the picture i take:
{
"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"
}
At recovery mode it just show the android fella blue heart keep spinning, few minutes later then it restart...
At download mode it shows:
ODIN MODE
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Since it shows the product name so i assumed that it not a SDS,methods i tried is:
ODIN FLASH N7100XXALJ1_N7100OXXALJ1_N7100XXALIH_HOME.tar.md5 - failed at modem.bin
ODIN FLASH N7100XXDMF2_N7100OLBDMD2_N7100DXDMF1_HOME.tar.md5 - failed at start
ODIN FLASH N7100XXALJ1_N7100OLBALJ1_N7100DXALIA_HOME.tar.md5 - SUCCESS
ODIN FLASH N7100XXALJ3_N7100OLBALJ3_N7100DXALJ1_HOME.tar.md5 - SUCCESS
ODIN FLASH other kernel such as philz touch,cwm6 recovery,even CFROOT - SUCCESS
ODIN FLASH with pit file (from DR.KETAN) - showing NO PIT PARTITION
Ok, i tried flash 2 ROM successfully, but still can't boot in the OS,any help would be appreciated.
Thanks.
As flashing frp.img: FAILED (remote: 'Requested download size is more than max allowed)
As flashing rooted-boot: FAILED (Write to device failed (Too many links)). It shows "press any key to shutdown" on my phone screen, even I enter the command at first, plug the phone then, or do both at the same time.
By the way the original fastboot shows the product name is g7ulm, but LG's official website says it's a sprint version according to my fastboot device-id.
Could you tell me what should I do if you knew the right way? I've been stucking here for a long time.
<hr />
{
"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"
}
Em_s'taht said:
As flashing frp.img: FAILED (remote: 'Requested download size is more than max allowed)
As flashing rooted-boot: FAILED (Write to device failed (Too many links)). It shows "press any key to shutdown" on my phone screen, even I enter the command at first, plug the phone then, or do both at the same time.
By the way the original fastboot shows the product name is g7ulm, but LG's official website says it's a sprint version according to my fastboot device-id.
Could you tell me what should I do if you knew the right way? I've been stucking here for a long time.
<hr />
View attachment 5232397
View attachment 5232403
Click to expand...
Click to collapse
Do you have the latest android platform tools (fastboot) installed?
For my phone, for root, you install magisk app.
Put stock boot.img on phone sdcard
In magisk, click "install magisk".
Choose patch file. Select your boot.img.
Patched image will be in download folder.
Put patched image on pc and boot to fastboot
fastboot flash boot magisk_patched***.img
I unlocked the bootloader of my Huawei y6 (atu-l21) 2 days ago. Now the problem is that I can't get working custom roms for twrp.
I had downloaded many .ZIP files but the zip file always contained only one image. When I wanted to download the ZIP file via twrp bottles, I always got a red message "invalid zip file format!
Does anyone have working custom ROMs for the Huawei y6 (atu-l21)
{
"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"
}
By you meaning by one file contains img file, you are trying to flash compressed gsi/treble image.
The installation procedure is different for treble devices. Instead do:
First you must uncompress it & do "adb reboot bootloader" & "fastboot flash system [UNCOMPRESSED_IMG_FILE]", wipe data by "fastboot -w", final reboot ur device "fastboot reboot"
do you think I should e.g. extract the customrom.zip to customrom.img and then the image with the commands Flash
Yes, Only if zip archive contains one *.img file like aonly, ab... etc
can I also flash the .IMG file via twrp. because when i try dan i don't know which partition to select.
System-Image
I just tried it and the message "Image is too large for the device" appears
You may read THIS POST about your device custom rom.
And if ab image doesn't work for you try aonly
Jannikoks06 said:
I just tried it and the message "Image is too large for the device" appears
Click to expand...
Click to collapse
Try with fastboot method
I'll do it later I'll report if it worked
Danielisko said:
Try with fastboot method
Click to expand...
Click to collapse
I did it but the phone doesn't boot, only the screen appears where it says that the bootloader on the phone has been unlocked
Hi everyone,
I need help to fix this problem: Stuck On Fastboot and SECURE BOOT -yes
I use LG G8 with firmware G820N20v Korean Open, the details how it ended up like this was:
1. I did unlock bootloader + magisk root after doin crossflash, it ended up well.
2. then i try to write my IMEI using this methods: https://www.hovatek.com/forum/thread-38608.html but didn't succes,the imei didnt change and my magisk been lost.
3. someone on my local group told me to try disable dm-verity first before write my IMEI. So i search for methods and found this one: https://www.hovatek.com/forum/thread-32719.html yes i flashed that empty vbmeta, and when i restart my phone it ended with white screen sayin that i need to insert pasword with 30x attemps (now still had about 10-15 attempts because it decrease everytime phone restart) because my phone is encrypted but i cannot touch any of my screen.
4. i can u enter EDL mode though, so i tried to restore everything that i backuped before like FTM, BOOT_A, BOOT_B, ABL_A, ABL_B and it ended Stuck On Fastboot with SECURE BOOT -yes. Heres the pic:
{
"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"
}
Its even cannot to power off, always goin back to fastboot automatically.
I appreciated any helps or methods here.
Anyone?
Thanks and regards.
my phone's working now following this step https://forum.xda-developers.com/t/tutorial-rescue-from-hard-brick.4351389/ thanks @netmsm
Im once again into this typical "I bricked my phone and spend endless hours searching for tutorials and hoping that something work" stuff. This time I broke my persist.img and noticed something strange:
There are dozen of tutorials which state that one should download a clean fastboot rom to extract the persist.img (".\images\persist.img") from the image folder and flash it either using recovery or fastboot edl in combination with a modified rom to only flash this partition.
Now I noticed that the persist.img partition is pretty empty for most Xiaomi stock roms:
{
"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"
}
In comparisation the persist partition I extracted from a friend who luckily got the same phone:
How is the above persist partition from the stockrom supposed to help someone when there are just empty files? Atleast for me it didnt bring back the sensors when I flashed it. On the contrary the persist partition from my friend fixed everything.
If the persist file of every stock rom is empty beside a few zero byte files the conclusion would be that the only way to get a working file is to get your hands on a unmodified one from someone else.
Or is there some magic that will enrich the partition with new files as soon as you boot the stockrom for the first time?
How come there are so many tutorials saying that one should flash this partition from stock?
are you sure you have downloaded a fastboot (TGZ) rom and open the TAR file?
Package Name: grus_eea_global_images_V12.5.1.0.RFBEUXM_20210526.0000.00_11.0_eea_0f94ab4db4.tgz