Database Info

(Q) Odin 3 flashing kernel issue

What would start causing this to happen?
{
"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 am very familiar with the process. Rooted, sideloading for apps is all done. I have flashed my device with JM2, JH2, and the 1.2 OC. Now when I try to flash it doesn't work. I tried last night with no luck. I decided to master clear the device since I was having issues and wanted to start back with a fresh device. Now after trying to flash the JH3 from JF6 with Unleash the beast it wont work.
I also tried flashing with one click root, and superrooter from a fresh Odin one click. Usb debugging is enabled, Odin opened and then get into download mode. So my process from when it would work is now not working haha? So beyond my confusion of what I might be forgetting can anyone think of something that might help? I didn't want to put this in the dev section since there is nothing specifically made up for odin 3, only odin one click restore.

Your drivers are messed up... grab the ones from the odin thread and reinstall with the phone plugged in and in download mode.

designgears said:
Your drivers are messed up... grab the ones from the odin thread and reinstall with the phone plugged in and in download mode.
Click to expand...
Click to collapse
Reloaded the drivers and still get the message. Any other suggestions would be helpful.

Try un-selecting the other options? (auto reboot/time)
I had a similar error message when the "repartition" was selected. Just an idea...

Gave that a shot but no luck
I am almost resigned to the fact I might be stuck with JF6 until Froyo gets pushed out OTA (if/when that happens). I just can't believe it has me this stumped.
Can busybox, the older superuser, anything like that cause this issue? When I wiped back to stock I loaded Unleash the beast because I prefer the older superuser (ninja guy). When I first got my phone I did the adb code for sideloading after doing one click root. That process isn't different from what the guys that made the UTB and Superrooter update.zip files is it?
Well tried running Odin as an administrator and that didn't work haha. Worth a shot.

I dont really know if that could be the cause or not. Im actually having trouble wiping all the data from my phone (I have my own thread, but it could be related). I used Odin 1 click, I used the regular Odin and did everything manually, tried master reset, and also did a factory data reset. Tons of data still on my phone, though. I was contributing it to titanium backup, but it may be things installed from super rooter

Anyone else have an idea that I might try?
Now even Odin one click comes up with this message??? I am really baffled with this situation.
Update: Got Odin one click to work again, I wiped my user data through clockwork. After this reloads I am going to try and do sideloading via the adb codes rather then using UTB or superrooter to see if that makes a difference for me. Still could use any suggestion on what else people have tried in this situation, if you have been in this before.
Sweet life

Still stumped by this issue if anyone has any help for me. Also could this be moved to the new Q&A section. Thanks.

flashman2002 said:
Still stumped by this issue if anyone has any help for me. Also could this be moved to the new Q&A section. Thanks.
Click to expand...
Click to collapse
Do you use the Kies program and if so has it ran an update lately, I had it on my Win7 laptop and when it ran the software update it totally hosed up my drivers and I could not connect to my phone anymore... I had to uninstall Kies and remove all my drivers and then reboot my laptop then I only reinstalled the Samsung drivers and now I can connect again. I won't be using Kies anymore..Anyways I thought I would share my experience in case it might help you..

jhernand1102 said:
Do you use the Kies program and if so has it ran an update lately, I had it on my Win7 laptop and when it ran the software update it totally hosed up my drivers and I could not connect to my phone anymore... I had to uninstall Kies and remove all my drivers and then reboot my laptop then I only reinstalled the Samsung drivers and now I can connect again. I won't be using Kies anymore..Anyways I thought I would share my experience in case it might help you..
Click to expand...
Click to collapse
I haven't used kies since I first got the phone to put contacts in. But I just tried again to give it a whirl and got it to load the kernel. Hell if I know why it worked today compared to before hahaha.

[Q] My atrix 2 is on the edge of dying. please help.

I'm really sorry if this doesn't belong here.
My atrix 2 (MB865 from Singapore) updated by OTA to ICS then rooted successfully and I installed custom roms (scv7 and swifty etc) and even mods (xLoud and Beats) but in CWM (Bootstrap + cwm-on-boot script) it would usually say ''installation aborted'' whenever I tried to flash a custom rom, which is pretty weird since I was using the correct roms for my device.
One day I decided to go back to stock ICS by flashing a ics fzw in RSD Lite 6.0 (I tried flashing 6.7.2_EDEM-18-SEARET_cfc.xml and 6.7.2_EDEM-18-ASIAOPS_cfc.xml) but every time it would stop at step 14/20 ''writing system.img'' but the progress arrows would still keep moving. So after an hour of waiting, I disconnected the phone from the usb cable and I got the black screen with Flashmode (Flash Failure) with ''cannot program'' and ''battery low''. Now the battery died and it won't even charge when I connect it to the wall adapter, it would only boot into the flashmode (flash failure) screen and when I turn it off and try to to it on again it won't. I don't think it's hardbricked because when the battery was still on, I could turn it off and boot back up into fastboot with options like normal boot or go to the stock android recovery.
What do I do now?

Hey, so you have 2 issues here. 1 is that your battery is dead, and you need to charge it.
you can try to find the diy method posted here a while ago, but be careful as you could fry your phone if your not careful. or you can find another phone to charge the battery in (another a2). if neither of those work, you can buy an external charger online to do it.
2 is the issue of why it is not flashing. make sure you are using the exact right fxz for your phone version, there are many available.

lkrasner said:
Hey, so you have 2 issues here. 1 is that your battery is dead, and you need to charge it.
you can try to find the diy method posted here a while ago, but be careful as you could fry your phone if your not careful. or you can find another phone to charge the battery in (another a2). if neither of those work, you can buy an external charger online to do it.
2 is the issue of why it is not flashing. make sure you are using the exact right fxz for your phone version, there are many available.
Click to expand...
Click to collapse
Thanks alot man, i've stopped stressing, I'll find a way to get the battery charged. But then the problem is in how to escape this damned AP Fastboot Flash Mode "Flash Failure" screen. I mean the fxz I mentioned should work (they match the phone's specifications) but whenever I use FDS Lite 6.0 it always gets stuck at step 14/20 "system.img" for like an hour, is it maybe a drivers problem? Should I try another computer? Should I claim warranty for it even though it's rooted? Thanks in advance

aligex said:
Thanks alot man, i've stopped stressing, I'll find a way to get the battery charged. But then the problem is in how to escape this damned AP Fastboot Flash Mode "Flash Failure" screen. I mean the fxz I mentioned should work (they match the phone's specifications) but whenever I use FDS Lite 6.0 it always gets stuck at step 14/20 "system.img" for like an hour, is it maybe a drivers problem? Should I try another computer? Should I claim warranty for it even though it's rooted? Thanks in advance
Click to expand...
Click to collapse
I am going to be totally honest here. You are using the wrong fxz file for your phone. I see you are trying to flash the SEARET fxz, that is for south east asia phones ONLY, and would not work on say an AT&T phone that was purchased someplace else and just being used there.
First off what region/country are you in?
Second does the phone have the AT&T logo at the bottom front of the phone?
Did you get the phone through proper channels in your part of the world, or did you buy it on ebay or something?
Yes all of these things matter. You will need to do the McGyver method to charge your battery (lkrasner mentioned it as the diy method). It is in this forum, just Search for it.
After you get us the information I asked for above we will be able to better help you.
Also one last thing to check is to see if the MD5sum matches. If not you prolly have a corrupt download and that is why it may not be working as well.

With respect to our developers this will allow you to flash without a battery. It does nothing else useful but does get around the low battery issue
http://forum.xda-developers.com/showthread.php?t=1910027
There are other forms however being in Singapore may limit your options. Remember Google is your friend.

jimbridgman said:
I am going to be totally honest here. You are using the wrong fxz file for your phone. I see you are trying to flash the SEARET fxz, that is for south east asia phones ONLY, and would not work on say an AT&T phone that was purchased someplace else and just being used there.
First off what region/country are you in?
Second does the phone have the AT&T logo at the bottom front of the phone?
Did you get the phone through proper channels in your part of the world, or did you buy it on ebay or something?
Click to expand...
Click to collapse
To follow up on that, there is a simple way to check if your Atrix 2 is from Singapore. Open the back cover, remove the battery, and look for
{
"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"
}
If you see that, your phone is indeed a Singapore version, and the SEARET fxz is the correct one to flash.

matthew5025 said:
To follow up on that, there is a simple way to check if your Atrix 2 is from Singapore. Open the back cover, remove the battery, and look for
If you see that, your phone is indeed a Singapore version, and the SEARET fxz is the correct one to flash.
Click to expand...
Click to collapse
That is great information! Thanks!

[Q] Samsung gt-s7560m [I killed it]

Hi, I have a koodo branded Samsung galaxy ace 2 x, the model is gt-s7560m
Anyways I'll give my storry on how i broke my phone, it's kind of stupid.... and totally my fault. If i can fix it then i don't have to send it out... but i guess i might have to.
Anyways. I rooted my phone so I could delete the useless Samsung all shair and other stupid services like that from my phone, then i started to delete other stuff off my phone, it eventuly broke notifications, and i was no longer alertaed about texts.
The next day i desided to do a factory wipe from the phones menu its self.....NOT SMART. because i had changed out my launcher and deleted the orginal one it came with, so after it was done the factory restore i could only go in the settings... kind of useless. and when i looked at the apps i had installed, there were alot of apps at 0b,
now, I had!!! clock work recovery mod... but i never made a backup or anything.like a smart person should anyways I did a factory restore from there, and now my phone no longer has clock work recovery mod, and it informs me it must be conected to samsung kies now, and that failes to work. my computer sees it but cant conect properly, I've tried with a few diffrent usb wires and another computer, so thats not a problem,
now the phone still shows up in odion, and i can put it in download mode still, so where do i go from here?
I amuse my phone is totally empty
I feel rather stupid and well if theres a way to even get a custom rom on there that'd be cool.
Yeah.... im sorry if this is a hard task for someone,

HelmetDoe said:
now the phone still shows up in odion, and i can put it in download mode still, so where do i go from here?
,
Click to expand...
Click to collapse
Chose the correct firmware from here for your region and network , and flash using Odin3, makes sure you have fully charged battery First, remove sim card and ext SD card also
Check this out! You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, click on their Thanks button
{
"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"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.​

HelmetDoe said:
Hi, I have a koodo branded Samsung galaxy ace 2 x, the model is gt-s7560m
Anyways I'll give my storry on how i broke my phone, it's kind of stupid.... and totally my fault. If i can fix it then i don't have to send it out... but i guess i might have to.
Anyways. I rooted my phone so I could delete the useless Samsung all shair and other stupid services like that from my phone, then i started to delete other stuff off my phone, it eventuly broke notifications, and i was no longer alertaed about texts.
The next day i desided to do a factory wipe from the phones menu its self.....NOT SMART. because i had changed out my launcher and deleted the orginal one it came with, so after it was done the factory restore i could only go in the settings... kind of useless. and when i looked at the apps i had installed, there were alot of apps at 0b,
now, I had!!! clock work recovery mod... but i never made a backup or anything.like a smart person should anyways I did a factory restore from there, and now my phone no longer has clock work recovery mod, and it informs me it must be conected to samsung kies now, and that failes to work. my computer sees it but cant conect properly, I've tried with a few diffrent usb wires and another computer, so thats not a problem,
now the phone still shows up in odion, and i can put it in download mode still, so where do i go from here?
I amuse my phone is totally empty
I feel rather stupid and well if theres a way to even get a custom rom on there that'd be cool.
Yeah.... im sorry if this is a hard task for someone,
Click to expand...
Click to collapse
Ok first of all..always remember search button is your friend..you wouldn't need to post also if you search once.
ok now second, dont worry your phone is not dead and its very much possible to revive it. Ok start from here http://samsung-updates.com/device/?id=GT-S7560M.
I wont tell you how to flash from Odin as you can easily search here and there are several tutorials here on that.
http://forum.xda-developers.com/showthread.php?t=2189539
Important thing to keep in mind is this. Don't cross flash a rom not meant for your phone. and even if u do make sure you dont overwrite the bootloader or preloader of your phone. As long as your phone will get detected by usb,your phone can be revived.
happy flashing

Wow, well i wasent shure what that samsung site was about but figured it out on my own with out the guide. odin aint hard to understand besides where to put what...
There was no koodo file so i took telus, (telus and koodo are the same) it seemed to work fine
any ways, its almost all done installing, I hope it works, its been like 4-5 days now,
Yeah I'm no good with search....
.... Anyways, It flashed properly and my phone actualy booted woah..... Awsome!!!
well atleast i have my phone back... .
anyways is there a custom for this phone? thats another think i have a problem finding, ... and the ones i find, they have dead links,

GT-S7560GSMH dead - please help!
Friend gave me GT-S7560GSMH to change rom in his telephone. I changed to CM11 4.4.1 but it was problem with camera it was taking pictures 90 degrees angle. Then I decided to try to flash other rom. But I try first change the recovery since there was some problems with recovery. So change to other version of CWM or TWRP or something else. I flash through CWM some recovery zip file and after that the telephone became completely dead. No any signs of life at all. Trying buttons for download mode and recovery mode, removing and put battery back, nothing at all, no signs of any life. Please tell me there is any way to resurrect the phone? To bring back to life? It is not my phone. I wish I could give back living phone not a dead phone. Hope to hear any help from you. Thank you,

Really confusing softbrick (small reward offered for fix)

TLDR: LGUP will just straight up not recognize my G5 no matter what. I'll give you five bucks on Paypal for a solution, if that means anything.
{
"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"
}
Hi guys, I try to avoid posting, but I've searched high and low for an answer and I really can't find it.
I've got a T-Mobile LG G5 H830, that I have recently rooted and installed TWRP on it. Last night, I decided to try changing a value in build.prop, stupidly without making a backup first and after I changed the value and rebooted, stuck at T-Mobile bootscreen, go figure. All I did was change a value from false to true for adoptable storage..
Anyway-- I tried factory resetting, I tried flashing that FLUENCE rom I found somewhere here on XDA, I've tried just about every thing I could, before I gave up and decided it would be easier to just revert back to stock and unroot. I wasn't really utilizing root for more than Titanium Backup anyway.
To the point; I've got the LG UP program installed, I've got the DLL for it installed and inserted, and the appropriate .tot file to flash it back to factory default. No matter what I do, no matter how many different COM ports I try, different drivers I've tried etc, I cannot get it to read my phone in download mode. ADB mode works in TWRP still, but this is driving me insane. The only other phone I have is a busted up BlackBerry Priv, and I want this phone working again asap.
If someone can shed some light on whatever the hell I'm doing wrong, it would mean the world to me.
Please.
P.S: yes I've tried just about every USB port on my computer, and I've tried restarting Windows many times.

you have tried jiggling it?

You know what? Hell, if someone finds me a working solution to my problem, I will personally paypal them five dollars. I just want this fixed. I've had LG G3s brick on me obnoxiously and then never come back from it, I don't know what it is about LG phones.. Samsung phones, Nexus phones, and basically any other Android phones I've worked on aren't nearly this hard to restore and repair.

speedanderson said:
You know what? Hell, if someone finds me a working solution to my problem, I will personally paypal them five dollars. I just want this fixed. I've had LG G3s brick on me obnoxiously and then never come back from it, I don't know what it is about LG phones.. Samsung phones, Nexus phones, and basically any other Android phones I've worked on aren't nearly this hard to restore and repair.
Click to expand...
Click to collapse
Use the twrp restore file in the development thread it will revert your build prop back, and from there your phone will work again. Editing build prop is not advised on the H830 has been discussed on numerous threads even before root was established. At least it's only a soft brick .

Have you tried jiggling it perhaps?

so did @wolfu11 get the 5 bucks? his solution should have fixed it.

autoprime said:
so did @wolfu11 get the 5 bucks? his solution should have fixed it.
Click to expand...
Click to collapse
I don't know if he's been back on since his initial post.

wolfu11 said:
I don't know if he's been back on since his initial post.
Click to expand...
Click to collapse
Last Activity: Today 12:52 AM
good luck :fingers-crossed:

autoprime said:
Last Activity: Today 12:52 AM
good luck :fingers-crossed:
Click to expand...
Click to collapse
Not holding my breath lol. That's why I declined any of the root bounty.

Try manually pointing to either the lg drivers, or adb drivers had that same problem when trying to root H830.
Sent from my LG-H830 using XDA-Developers mobile app

IDK if u fixed it or not, but i have a simular issue where LGUP does not recognize my phone. i'm guessing it could be the buildprop could have broken it. i have factory reset my phone, but upon turning on wifi, the phone crashes and i need to factory reset. i am rooted and retain root. My guess is that changing the buildprop causes the phone to be unrecognized. I did backup my buildprop but its stuck in an encrypted backup. Thanks alot gooogle...

Same problem here
I am having the same problem but I never touched my build prop. I rooted and decided to install cm14. When i flashed, none of my partitions are mounting and phone would not boot. I put stock back on and flashed tot and tried mounting partitions and nothing. Now computer doesn't recognize it as well as it will not boot into recovery or android.

I have seen this and I think I fixed it by disabling one of the two, in device manager. 1st listed, iirc.

Barsky said:
I have seen this and I think I fixed it by disabling one of the two, in device manager. 1st listed, iirc.
Click to expand...
Click to collapse
ill give it a shot, thanks

Bricked MT6577 SoSoon/Senq X8 Elite 3, NO USB Debug/ADB, Stock Recovry No Roms to D/L

I've had an MT6577 phone sitting around for a few years now that's been stuck in a boot loop. My phone karked it today and this is the only device lying around, hoping it can be revived some how to save a few dollars.
It all happened one time when I tried to use an app to install a new font just to see what it looks like.
Seems to be the most obscure thing ever made as it has many names and models all with 0 firmware available. Typically SoSoon X8 Elite 3 shows up as the most common make but I recall the original box having Senq X8 Elite on it.
The bad?:
USB Debugging is almost certainly off because ADB can't find a device no matter if I just plug it in off, in bootloop (shows 2 drives on my PC that are not ready to be used in this stage), fastboot mode, recovery (install update from ADB)
Questionable root, one of those generic one click apps.
No stock or custom roms available any where that I have found from searches here and there over the last few years
I tried to follow a tutorial to port an MT6577 rom but I would need the kernel off the phone, which can't be done to my limited knowledge.
No custom recoveries available, running Android System Recovery 3e. Can't use TWRP MTK 1 click install on my PC because the device needs to be fully booted to work.
The good?:
Fastboot seems to work as it does show the device in the command prompt "fastboot devices"
I think the bootloader was unlocked at some point, no idea on the relevance of that.
Any information on if/how to sort it out is greatly appreciated.
Last ditch effort to try revive it because it was decently usable for what it is, hoping that someone on here has one lying around somewhere.
Will add more information as I remember and reply to any responses asap
Thanks for your time

Hello have you tried a hard reset so far ?

-Hope- said:
Hello have you tried a hard reset so far ?
Click to expand...
Click to collapse
I have, through the recovery "Wipe cache partition" and "Wipe data/factory reset" have been done a few times as I've tried different ways to try and fix it

can you get the model it would be easier to look up for the rom
try fastboot oem device-info that will input some useful informations

-Hope- said:
can you get the model it would be easier to look up for the rom
try fastboot oem device-info that will input some useful informations
Click to expand...
Click to collapse
Good news: Tired it
Bad news: Nothing happened
{
"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"
}
Also tried "getvar all" which according to a post on a xiaomi forum, is an MTK specific command, returned nothing anyway.
Just showed the "..." until I pulled the USB cable out.
Thanks for the suggestion, guess that's a pretty significant strike against any kind of fix for it.

the battery is removable ? maybe you can find the model in the box if you have it , dont lose hope

-Hope- said:
the battery is removable ? maybe you can find the model in the box if you have it , dont lose hope
Click to expand...
Click to collapse
The battery is soldered in but the back panel pops off easily, no information at all besides "X8" written on the battery.
I've found what I'm sure is the exact same model phone on GearBest and I've asked the seller if there's a chance of them providing the stock firmware.
This is the only form of model number I've found, but it's generic and shows up more Sony Xperia posts than anything else through google.

weavernater said:
The battery is soldered in but the back panel pops off easily, no information at all besides "X8" written on the battery.
I've found what I'm sure is the exact same model phone on GearBest and I've asked the seller if there's a chance of them providing the stock firmware.
This is the only form of model number I've found, but it's generic and shows up more Sony Xperia posts than anything else through google.
Click to expand...
Click to collapse
https://url.gem-flash.com/gtKxY
Here this flash is not for your device exactly by might work, check if the spcs match too

weavernater said:
The battery is soldered in but the back panel pops off easily, no information at all besides "X8" written on the battery.
I've found what I'm sure is the exact same model phone on GearBest and I've asked the seller if there's a chance of them providing the stock firmware.
This is the only form of model number I've found, but it's generic and shows up more Sony Xperia posts than anything else through google.
Click to expand...
Click to collapse
You don't need a whole firmware, all you need is a good copy of system.img from a device like yours or from a similar device that uses the same kernel, trying to find a whole firmware that will flash without issues will be kinda difficult because there are things in a whole firmware that might not work on your device, a system.img on the other hand doesnt have all the extras in a firmware that could cause issues. Use fastboot to flash the .img with this command.
fasboot flash system system.img
From what you described causing the issue, technically, all you "need" is a copy of the stock font to replace the font that you tried and screwed it up with, but getting just the font back on without doing anything else isn't as easy as flashing the whole system.img unless you have TWRP or can sideload apps in the recovery that you have.
Sent from my SM-S903VL using Tapatalk

-Hope- said:
https://url.gem-flash.com/gtKxY
Here this flash is not for your device exactly by might work, check if the spcs match too
Click to expand...
Click to collapse
Thank you for finding this, much closer than anything I've ever found. From what I can see on it, it's really close spec wise. I'll download it and have a look through the files before trying it.
Droidriven said:
You don't need a whole firmware, all you need is a good copy of system.img from a device like yours or from a similar device that uses the same kernel, trying to find a whole firmware that will flash without issues will be kinda difficult because there are things in a whole firmware that might not work on your device, a system.img on the other hand doesnt have all the extras in a firmware that could cause issues. Use fastboot to flash the .img with this command.
fasboot flash system system.img
From what you described causing the issue, technically, all you "need" is a copy of the stock font to replace the font that you tried and screwed it up with, but getting just the font back on without doing anything else isn't as easy as flashing the while system.img.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I did try that. I have all kinds of zips that could supposedly be flashed with the stock roboto font as well as the file itself ofcourse but I could never get fast boot to so anything with it. Based solely off the assumption that all android devices use it as the default, and assuming that the app was just renaming custom fonts to Roboto or something along those lines.