I extract the kernel.sin file from c2004_brazil.ftf and i try to flash this in fast boot mode i am getting following error
{
"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"
}
how to flash this in fastboot mode need any conversion to get correct boot image ?
Okay, try this:
Retry doing it not in a removable disk this time. I've had this issue the last time.
If that didn't do the trick, make sure that the FTF is not corrupted. If so, redownload in SUS/PCC if necessary, then decrypt.
elmkzgirxp said:
Okay, try this:
Retry doing it not in a removable disk this time. I've had this issue the last time.
If that didn't do the trick, make sure that the FTF is not corrupted. If so, redownload in SUS/PCC if necessary, then decrypt.
Click to expand...
Click to collapse
i placed the ftf in internal drive only, ftf also correct one check with flashmode.
and also same error when i try to flash "kernel.elf" file extracted from "kernel.sin" of ftf
stalin.sk2 said:
I extract the kernel.sin file from c2004_brazil.ftf and i try to flash this in fast boot mode i am getting following error
how to flash this in fastboot mode need any conversion to get correct boot image ?
Click to expand...
Click to collapse
U can also flash kernel in flaah mode just select the firmware and untick wipe data and system and in exclude everything except kernel and flash it , it will work
Sent from my C1905 using XDA Premium 4 mobile app
Related
I have a problem. My tablet is turned on and shows only the label similar to a USB flash drive. rekaveri not go in. already tried all combinations of buttons.I am trying to solve the problem through flash tools, but nothing is impossible.
Really need your help. tablet a month is not working
I do not know. maybe the fact I am working through the flash tool? because when I try to do everything I have comes to 50% and then an error.
{
"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 have the exact same problem, and have been trying to use the Intel flash tools to fix it with not much success. I have found, though, that when using the phoneflashtoollitecli (flash tool command line utility that comes with phone flash tool lite) with the --clean-emmc option, the flash only succeeds when I hold down power and vol+ first, and then attempt the flash. All other times, it "Failed to start Dldr state machine, aborting...". Haven't been able to use this technique when flashing the os image though.
Hr.shokohi, where do you get your OS image and OS DnX files from?
download here
laoshu84 said:
laoshu84
Click to expand...
Click to collapse
https://yadi.sk/d/IdC9Pbxpj3HGC
in this file take (dnx_osr.bin) and put together os dnx, and click Show All Files at the bottom right and droidboot.img where os image
Thanks Hr.shokohi. I've had no luck using my method of flashing and your flash files, so far. I will be trying using the Linux version of the flasher to see if it makes a difference.
laoshu84 said:
Thanks Hr.shokohi.
Click to expand...
Click to collapse
If something happens write.
Do u solve the problem?
i will take n1 to factory. still cant solve the problem~ha
Nope no luck yet. I'll write back if I succeed
Please have a look at pictures. I have tried reseting the phone from "recovery mode" but still its same. I have also tried 'force stop' , 'clear cache' , 'delete data' from application manager.
I can install stock rom but the rom for this "rogers" phone is in TOT and I dont want to risk breaking the phone. Can I install KDZ Telus other than rogers?
Please advice. what should I do? OR can I fix it without re-installing ROM.
{
"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"
}
Thank you for reading
I would say get logcat from playstore, run it and check what's causing it to error out.
Play store is also giving same error, just checked. so what to do now?
can anyone help me, how to re-install stock firmware???? all I can find is a .TOT file, How can I install KDZ file?
Administr4tor said:
can anyone help me, how to re-install stock firmware???? all I can find is a .TOT file, How can I install KDZ file?
Click to expand...
Click to collapse
Download lg flash tool and flash your kdz. To enter download mode press volume up button and hold it...plug your usb then you will see download mode...then open flash tool flash your kdz....you will see error in flashtool just ignore it. But you have to find kdz file for your model first. In picture it showing you are on lolipop so you have to use lg flashtool.
Hey, I wanted to revert my One M9 to stock but I f#cked up along the way, I did lock the bootloader before installing the stock Rom. I dont know what to do, I've been searching google for hours now and tried everything. ANy tips?
Can't go into recovery, I can't flash STOCK recovery because it's not unlocked anymore, cant flash stock rom via fastboot.
PS: The phone was 100% functional before I relocked the bootloader, but now I can't boot to Android. goes straight to Bootloader.
I Hope somebody can help! Thanks!
{
"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"
}
flash a RUU. Youre on the european fw so there shouldnt be any issues. Check out flippys thread in the general section and youll be fine
Doesn't work, tried both Zip and Exe, none of them works. the exe starts flashing then quickly aborts. same with the zip.
Demyx11 said:
Doesn't work, tried both Zip and Exe, none of them works. the exe starts flashing then quickly aborts. same with the zip.
Click to expand...
Click to collapse
Then you are missing something. Read again.
Beamed in by telepathy.
Demyx11 said:
Doesn't work, tried both Zip and Exe, none of them works. the exe starts flashing then quickly aborts. same with the zip.
Click to expand...
Click to collapse
tell us what errors you got or we wont be able to help you
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
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