Develop Bugs

[Q] flash kernel get black screen

My device is ARC lt15i
I try to flash the kernel ArcKnight RC3.3 in order to install Arconium-ICS-4.0
after use fastboot to flash kernel, and push power button
it only short vibrate and black screen ,can't enter recovery.
but it can enter recovery by " fastboot boot XXX.img "
and setup the rom
does anyone can help...

redownload the kernel and reflash it...try this and let us know

OK, i have re-download kernel (Arcknight) and reflash it.
but it only can boot by fastboot (fastboot boot XXX.img) and use as normal.
it still can not boot by power button

lalakuo said:
OK, i have re-download kernel (Arcknight) and reflash it.
but it only can boot by fastboot (fastboot boot XXX.img) and use as normal
Click to expand...
Click to collapse
The correct command is fastboot flash boot nameofboot.img

I have try fastboot flash boot nameofboot.img
but can't boot the device.
it only Successful fastboot boot nameofboot.img
{
"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"
}
Shuold I need to check something else ?

The bad block is the issue, so you need to take it to a Service Centre as arpith.fbi said.

So, it is hardware's problem ?
I've see another post that they has same problem of bad block
But they can flash kernel Susessfully.
If I sent it to service center, how do I tell them bad block problem?
I'm a beginner with it ,sorry ....

lalakuo said:
So, it is hardware's problem ?
I've see another post that they has same problem of bad block
But they can flash kernel Susessfully.
Click to expand...
Click to collapse
Then do whatever they've done.
lalakuo said:
If I sent it to service center, how do I tell them bad block problem?
Click to expand...
Click to collapse
By the power of speech. :silly:

do you have an unlockd bootloader?. if so i can help you.

link-in said:
do you have an unlockd bootloader?. if so i can help you.
Click to expand...
Click to collapse
Ummm.. He's flashing kernels, so his bootloader is unlocked! :|
Sent from my LT15i using xda app-developers app

link-in said:
do you have an unlockd bootloader?. if so i can help you.
Click to expand...
Click to collapse
yes, i've unlock bootloader.

Restoring Stock rom

Hello guys, this is what i have on my htc m9
{
"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"
}
Could I restore Stock rom on my htc m9 and how to do that?
And how I now which RUU to chose?

https://www.google.com/url?q=https:...134000&usg=AFQjCNGdzDwYjWYwYr-RSW3t2U9j47aOJw
Download this file. Copy it to your ext sdcard and rename it to 0PJAIMG.zip
Connect your phone to fastboot and type fastboot oem lock
Boot into download mode. Phone will prompt you to install. Press volup and wait.
Before u start backup ecerything

If you're already linking one of my files you could've linked my instructions, too, since what you wrote isn't completely correct. Re-locking the bootloader is unnecessary if you use the SD card method. In the worst case (e.g. if the RUU fails and OEM unlock isn't activated in the developer options) you could end up with a non-booting phone that can't be re-unlocked. The M9 has security checks that prevents it from booting if it isn't completely stock and the bootloader gets (re-)locked. And although I tested that RUU there can always be reasons why it fails to flash.

Could you be more specific please, I am new with htc and I dont know anything about it, What is fastboot? And if you have some time to tell me step buy step how to do that i would be greatiful. Sorry for bad english

Im sorry Flippy498 i just want to help him. You are a genious and i respect you. You are a life saver.

https://docs.google.com/spreadsheets/d/15K6xhb6wtosp9j8yu4xHBZ6n9v5OaFSW6ZVWxC4u_qc/pubhtml
My bad. I didn't notice that my signature isn't visible in this thread.
Edit: I don't know why the link gets broken as soon as I save this post. You'll need to copy'n'paste the link.

THX a lot, now I'm gonna to try to restore stock rome!

@Flippy498 I have just one question, I followed your instructions and it worked perfectly but I still have Software Status marked as Modified. Would I be able to receive software updates ?

Yes, you will. And you'll be able to install them, as well. (Receiving updates is not the problem, it's being able to install them if the system has been modified. However, a RUU reverts every modification you made.)
It's just strange that the flag still says that your system is modified. Normally the SD card method should reset it to original. But that shouldn't be a problem. OTAs don't check that flag. They compare whether the checksum of the system is the same as the reference value. Since a RUU overwrites the current system with the stock one you won't face any problems here.

Thanks a lot dude for your great work and quick reply !

Flashed stock rom via ODIN and now my phone thinks it is 32 GB

TLDR; Soft bricked phone trying to install TWRP, flashed stock rom on it, now phone says its 32 GB when its really 256 GB.
Hi all,
So I got a brand new Note 10+ a couple weeks ago and tried to flash TWRP onto it thinking it was easy like it used to be. Boy i was wrong. Stupid iphone user mistake.
So, I googled how to fix the soft brick. Downloaded the most recent firmware and flashed it via ODIN.
I flashed the following
BL
AP
CP
CSC (not HOME_CSC)
I setup my phone and personalised it like i had before and just now got a notification saying my phone is almost out of storage.
So i click the notification naturally being like what the hell already?
And long and behold my phone is now 32 GB instead of 256 GB.
I googled ways to fix this but all the ways say to flash the regular CSC which i already did!
Can anyone help me?
I've provided screenshots of the DF command and the storage settings.
Screenshots:
{
"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"
}

This could happen if you have flashed standalone AP file without CSC file same time.
Stock AP file must be flash with BL CP and Home_CSC at same time unless it may shrink your data.

Thank you for your response, however i flashed the AP file at the same time as everything else.
If i was to flash the AP file including everything else but change out the CSC file for the CSC_HOME will i keep my data on my phone because it was a pain to set it all back up.

No...

Is there a way to keep my data or no?

JosephShenton said:
Is there a way to keep my data or no?
Click to expand...
Click to collapse
If you use HOME_CSC_* it will not wipe data If you use CSC_* then it will wipe data. But looking to your device issue, probably you need to wipe it.

Question FASTBOOTD! Mode

I would like to know how to enter fastbootd! mode???

Enable the USB debug mode in the Developer options, install adb (it's the part of Android Studio, or as a separate tool for Linux available in the official repos) and execute "adb reboot bootloader".

This is FastBootd! mode ??
{
"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"
}

Yes it is. In this mode the phone responds only to the commands of the fastboot CLI tool.

uluruman said:
Yes it is. In this mode the phone responds only to the commands of the fastboot CLI tool.
Click to expand...
Click to collapse
so I can install GSI by the dynamic partitions

PaulinoBaslio said:
so I can install GSI by the dynamic partitions
Click to expand...
Click to collapse
Probably. May be. From my experience it simply doesn't work. It sorta flashes something but may be it just takes forever to complete or it's really just stuck but there's no response whatsoever. Fastboot mode is absolutely minimalistic, it does not report anything, no progress, nothing, and I guess it's intended to be like that, because it boots before anything else and theoretically allows you to flash even the very first bootloader. Anyway, I tried something like fastboot flash system lir-v316-220325-arm64-bvZ.img and the CLI tool reported Sending 'system' and then nothing else happened for the next 15 minutes or so, after which I just hit Ctrl+C, ran fastboot reboot and observed that nothing changed, the old system booted just like it was, so I guess nothing was really flashed, even partially. I don't know really, may be it's unpacked internally only when the image is fully uploaded and I didn't give it enough time, but for that time Odin would already flash the whole set of firmware. What else is to try, besides waiting more time, is converting the image to/from Android sparse format using the img2simg & simg2img tools, and try other partition names, such as "system_root" but I am sure this latter thing is absolutely wrong. The GSI system partition is called system, it just must be called that, system_root is something else (I guess it's the system root of the recovery mode).

Question System destroyed no fastboot no recovery

I get system destroyed and cant get into fastboot nor recovery i tried all youtube tuto and i can only see that edl flashing is the only solution can someone guide me how to fix it.
The only problem idk where are the edl point on motherboard and google dont have them

yenzenko said:
I get system destroyed and cant get into fastboot nor recovery i tried all youtube tuto and i can only see that edl flashing is the only solution can someone guide me how to fix it.
The only problem idk where are the edl point on motherboard and google dont have them
Click to expand...
Click to collapse
It seems to me that this is not necessary with a soc Mediatek.
https://forum.xda-developers.com/t/...no-auth-for-free.4229683/page-6#post-84813969
Search in this direction with https://spflashtool.com/

NOSS8 said:
It seems to me that this is not necessary with a soc Mediatek.
https://forum.xda-developers.com/t/...no-auth-for-free.4229683/page-6#post-84813969
Search in this direction with https://spflashtool.com/
Click to expand...
Click to collapse
I fixed it with another method thanks for reply

yenzenko said:
I fixed it with another method thanks for reply
Click to expand...
Click to collapse
how you fix it? i have same issue

Here is the way I fixed it
1. the main instruction is here. You need to download your firmware (in my case it's V13.0.2.0.SGDMIXM | 12.0 GLO), and flashtool.
2. Also you need tool to disable SLA authentication. The instruction has its own link to guide, however I decided to use different tool, MTK Auth Bypass Tool V44 from here. You click disable auth, then press volume up+down and connect phone to computer. You need to do it while phone screen is black
Spoiler: screen
{
"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"
}
3. then you are flashing with sp flashtool. Choose your scatter xml file, then press download (you need to do previous step every time you are trying to flash firmware). In my case I've got error about wrong value of combo_partsize_check, so I edited all "<combo_partsize_check>true</combo_partsize_check>" to "<combo_partsize_check>false</combo_partsize_check>", and after that it worked just fine. At least I could boot phone to fastboot mode and recovery, haven't decided what to do next