yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] CXZa:
Don't open it yet! :laugh: I did a bit more searching. It's a MT6572. This "dazexy" fellow

most likely can help if you cannot get that factory firmware.

http://forum.gsmhosting.com/vbb/f29...nfinity-box-725574-post10962286/#post10962286

(gsmhosting is not working at the moment, so here is the page at google's cache:

http://webcache.googleusercontent.c...rum.gsmhosting.com/vbb/10962286-post1173.html )

At least he helped "kaller1" at the same forum.... see the second post here.

(if needed you can find kaller1's email by clicking his paypal donate button)

http://forum.gsmhosting.com/vbb/f82...nck-dongle-1314877/index147.html#post11354667

(gsmhosting is not working at the moment, so here is the page at google's cache:

http://webcache.googleusercontent.c...d-phones-via-nck-dongle-1314877/index147.html )

Some more helpful people having d402??

https://mobilarena.hu/tema/navon_mizu_d402/hsz_1-50.html

So no worry, I think your problem will be solved. :highfive: (Hopefully...)

(if it is that Navon Mizu D402, as I assumed because of this post

https://xdaforums.com/showthread.php?t=3501143 )

edit: gsmhosting works again. The second link (kaller1) updated to be more accurate.
[Android Q&A, Help & Troubleshooting] CXZa:
Here is another fellow who gives a damn. "donrico" is sharing the full rom here

http://forum.gsmkabelek.com/showthread.php?28404-navon-d402-rom&p=250246&viewfull=1#post250246

Because that 4shared site is a bit nasty, i copied it to mega, here

https://mega.nz/#!v4MgVIbJ!htsUcjHSrwwGIDuTeNRMAXKhxZOvVxJ8mnY3vMZoVks

Taking a full backup first might be a good idea.

SP_Flashtool should do the trick. You probably

can use the scatter file from that rom dump.

Or make your own: https://forum.hovatek.com/thread-21970.html

:D
[Android Q&A, Help & Troubleshooting] CXZa:
Sub forum changed... Okay, let us continue here if needed.

Though you should be able to fix that damn thing now...

:victory:
[Android Q&A, Help & Troubleshooting] Nikkka:
Thank you so much for making such a hard effort to help me! ?

I'll do my best and will keep you informed.
[Android Q&A, Help & Troubleshooting] CXZa:
Partitions "nvram" and in in my case also "pro_info" are important backups.

Nvram contains IMEI values etc... anyway it can be important to save it/them.

And pro_info might have some extra values defined in it. At least if the device

has some faked firmware showing wrong hardware values like in my case.

Then there might be some real values needed, defined there along with the faked ones...

I'm no MTK expert but managed to fix my tablet by restoring those partitions...
[Android Q&A, Help & Troubleshooting] Nikkka:
Ehh!

I've read all the info you linked. ????

OMG!

Well, I guess that I should download the rom.

After that do I have to do all the instructions?

How will my pc be able to see my phone?

I need no data backup.

I swear I got in touch with the store in which I bought the data cable and asked if it is really a data cable and not just a charging one.

I can do anything I just need to know the steps to be taken one by one.

There is no way to see the system files on my dead phone to be able to delete the rest files of SELinuxModeChanger?

Thanks for your kind reply in advance!
[Android Q&A, Help & Troubleshooting] CXZa:
1. I can relate your "shock". That Wwr route isn't the easiest one, I can imagine.

Haven't done it myself. Maybe that SP_FlashTool + scatter file is enough for

the backup. If you have those IMEI numbers saved you probably can skip

the backup, but as I said I'm no expert, so you might want to do some

Googling before deciding anything...

2. Install the MTK drivers (search). any tool will need them too.

3. IDK. Maybe someone else has an answer to this?

Checked. The stock recovery doesn't use test keys, so making update zip is not possible.
[Android Q&A, Help & Troubleshooting] CXZa:
Checked SELinuxModeChanger's info - and its source code too.

It shouldn't do any writing that factory reset wouldn't remove.

https://xdaforums.com/showthread.php?t=2524485

Easiest would be that the vendor would give you a

full

OTA/recovery update zip package.

(Not such that just patches the old one. ) That most likely would fix it.
[Android Q&A, Help & Troubleshooting] Nikkka:
Yep. Thanks.

Well, actually the antivirus Zemana asked if I wanted to make SELinuxModeChanger a part of the system/a system file. I agreed. I made the wrong decision. I used ES File Manager to delete SELinuxModeChanger. Well, I succeeded in half... but failed to delete it from all system maps and couldn't reinstall it again. Rebooted... The rest is history...

I guess phone thinks that it has a corrupted system and that's why it doesn't boot.

Navon... They never ever update. No system security patches ever.

Actually, 1 yr ago I had a problem nobody was able to help. I was advised to take my phone to Navon asking for refurbishing. I had no money and I wanted to fix the problem myself anyway. It took a year, but I found out how to fix it. ES File Manager was the key.
[Android Q&A, Help & Troubleshooting] CXZa:
Yes I have seen that post. For "fun" I added the fota values from your build.prop to

my tablet and installed the apks needed for the OTA update. The OTA server

http://adups.cn didn't respond. It seems that the programs needs to be

updated or they don't provide updates for the older models...

Something to read....

How to use SP Flash tool to backup Mediatek firmware

https://forum.hovatek.com/thread-526.html

How to Flash Stock Rom using Smart Phone Flash Tool

https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool

How to Flash IMEI

https://androidmtk.com/use-sn-write-tool

How to Backup and Restore IMEI/ NVRAM data on Mediatek Chipset Android Device

h t t p s://w w w . getdroidtips.com/backup-restore-imei-nvram-data-mediatek/

(Bad site, sorry. While the info in this article might be ok, all at this site is not.

So better to search if the info can be found elsewhere.)

+ lots of more similar articles + videos. Almost too much really... :eek:
[Android Q&A, Help & Troubleshooting] Nikkka:
Thank you so much for your trying to help me! :)

I guess I need some time to let it go for a while.

It came across my mind that 1 yr ago my phone was rooted also. Do you think that having my phone rooted makes Recovery Mode especially Factory Reset disabled?

Unfortunately twrp is not compatible with KitKat.

I guess it will be a hard effort to make my phone work again. I seem to give it up. Unfortunately, sending the phone to Navon for refurbishing... would cost too much and phone must be sent by post (!!!). It is a great phone, but customer service at Navon is...
[Android Q&A, Help & Troubleshooting] CXZa:
I don't think that rooting is causing it. How do you know that

Factory Reset doesn't work?

You have a twrp for it? Older one, or what do you mean?

Maybe not that hard if you're able to connect to PC... but.. :mad:

(it looks like that at the moment I cannot make a connection either, LOL

re-installing the drivers probably fixes it, IDK, have to check it some day... )

---

That OTA update needed (at least) one program more (to be run as a service).

Did that too. And I also disabled the firewall that was blocking the connection. :laugh:

It just says that my system is up to date. (Changing version numbers etc. doesn't help).

The server response hints to http://europedownhw.mayitek.com/ site

that seems to be dead...
[Android Q&A, Help & Troubleshooting] CXZa:
Navon...

https://forum.hovatek.com/thread-25956-post-155741.html#pid155741

Oh yeah? http://smartnavon.eu/smartphones/navon-t503 (not even an old model)

https://logout.hu/bejegyzes/cappa72/sp_flashtool_readback_kiolvaso_opcio_hasznalata_gy.html

https://itcafe.hu/tema/android_dual_sim_ket_sim_okostelefonok_topikja/hsz_16132-16132.html
[Android Q&A, Help & Troubleshooting] Nikkka:
[QUOTE
[Android Q&A, Help & Troubleshooting] CXZa:
While you're are letting go, you could read some stuff linked below. Good

instructions. What to do and what not to do. (Unlike at that "getdroidtips"

site I linked earlier. Some of the tips and articles there are total rubbish.

Mixed stuff copied somewhere else, I guess. Some might work, but not all.

Also they use wrong words in article names to get better Google rankings.)

SP Flash Tool + MediaTek MT65xx drivers download and installation guide including bricked devices

Download MTK Drivers (32 & 64 bit) XP Vista Win7 Win8

Windows 10 MTK VCOM USB Drivers for 32 & 64 bit + Drivers installation tutorial (Might be useful with win8 too.)

Download SP Flash Tool v3 & v5 – Latest versions ( Tip: read to the end)

Remove, Disable & Uninstall MTK USB Drivers and inactive COM Ports – USBDeview (if having driver problems)

(And I also sent you some info in Hungarian already in the previous post. Backup etc.)

;)
[Android Q&A, Help & Troubleshooting] CXZa:
Again. just for fun sake, I tried again if my MTK tablet/phone would be recognized by SP flash tool.

No luck. Previously it wasn't a problem. Still, the adb/fastboot works okay.

So, some problem with MTK drivers. I have used SP_Flashtool, BeTools,, even older ones

like WiseLinkTool. And maybe some that were between those two.

Well, I don't have any good reason to fix those driver problems at the moment,

everything works ok, but still it kind of sucks.

Anyway adb/fastboot works okay. And that is the problem mentioned originally in the title.

So, does the fastboot work?

With fastboot, if it works, you might be able to boot some modified recovery without flashing and then maybe do some backups etc.

My adb driver package, mentioned in my signature has some options to remove the

old adb installations and the old (maybe problematic) values from the registry...

USBDeview is better choice in some situations though...
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] vlad_tepesch:
Hi,

my S4 Mini died few days ago.

I tried to resurect it with a debrick.img but it fails reading and writing to the internal memory IC.

So for normal usage the phone is beyond repair (at least economical - if the devices age is considered)

But one idea came up:

Without the memory IC the Application Processor seems to wait for usb-uart connections to load some program/system.

And also the debrick image proves that it is possible to boot the system from SD-Card.

Are there any projects to run a linux system from the SD-Card to use the phone as some small kind of single board computer with display?

Maybe the debrick image can be used as a base for such a project
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Ibuprophen:
I don't have this device but, you may be able to obtain some member guidance within the following thread that's specific to your device.

https://xdaforums.com/showthread.php?t=2625628

Good Luck!

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] vlad_tepesch:
Hi,

This thread has not very much to do with my question. It just shows a way to create a debrick image from a running device.

My device is dead and the debrick image boots, but can not do its job, because the internal memory is dead.

But it boots and my question was, if somebody has tried to boot a running system from SD-Card. Of course the device is not very usable as a smart phone but may be it can fit some custom needs in some electronic projects - may be as some kind of smart display or so. or as an remote for smart home.

I would be totally happy if some small linux could be run and if the wifi would work - the mobile network stuff is not htat interesting for me.

It seems that there are a lot of dead phones out there and i guess that quite some will share the same reason of a dead memory chip. would be great if thei could become a quite cheap source of embedded computers with display units.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Ibuprophen:
Okay, my apologies...

I think that I understand you a bit better and I'm hoping that the following will work for you.

You can also create a Debrick image from the Stock Firmware Version for your specific device. I haven't performed this myself in a while, so I searched a bit for some helpful instructions in doing this.

The following thread post is actually located within a different device dedicated area on the forum but, the instructions itself for creating the Debrick image is correct.

https://xdaforums.com/showpost.php?p=66593246&postcount=2

Follow those instructions and, for the device portion, just use your device instead.

For example, Part 3 mentions downloading the stock firmware, (if you don't have it already) just obtain the one for your device.

Part 4, on the other hand, states that any good Debrick Image will do, so then you can use the link that was already provided. This just means that another good Debrick Image will be used as more of a template to modify with the file(s) and such that is specific to your device.

I do hope that it was helpful and I had explained it okay via text.

If everything was done right, and you were still unsuccessful, then it might just as well be (what you had just mentioned) the case of an EMMC Chip gone bad. I'm hoping that it's not.

I do wish you the best of luck!

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
[Galaxy S6 Q&A, Help & Troubleshooting] BlackOps556:
hi all,

so i got a screwed situation here, i have a SM-G925F 32GB (galaxy s6 edge) international

the problem is, it is softbricked, reactivation-lock is enabled and OEM Unlock is disabled :/ it has never been rooted or modified, its bone stock.

anyway i tried flashing the newest stock ROM, it gets stuck on boot.img or cache.img. i tried installing all the firmware components one by one. correct PIT file first, then sboot.bin, followed by boot.img. that goes flawless, i get the samsung galaxy s6 edge splash screen (prior to boot animation)

then i tried installing the modem, output:

<ID:0/003> Now Writing.. Please wait about 2 minutes

and eventualy return an error code, + the phone doesn't show the samsung splash screen anymore and goes back to that cyan screen which says something with smartswitch.

so i started again at square 1: PIT --> sboot.bin --> boot.img, that went flawless, got the thing on the samsung logo again.

but this time i went on and flashed system.img: output:

<ID:0/003> Added!!

<ID:0/003> Odin engine v(ID:3.1100)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> SingleDownload.

<ID:0/003> :ÿ&í

<ID:0/003> RQT_CLOSE !!

<ID:0/003> RES OK !!

<ID:0/003> Removed!!

<ID:0/003> Remain Port .... 0 <OSM> All threads completed. (succeed 1 / failed 0)

well, flashing system.img took aprox 1.5 secconds! thats impossible... what am i doing wrong here?

sidenote

, <ID:0/003> Initialzation.. takes 3/5 minutes, some rare occasions, 2 seconds. is that normal?

i tried different ODIN versions, and also the ones from SkipSoft. i tried several different USB cables, 2 different computers and a lot of different usb ports. i also cleaned the crap out of my usb port inside the phone.

reinstalled drivers, turned antivirus and firewall defender off, always ran odin as administrator, cleaned the pc with ccleaner etc.

errors i keep getting are:

<ID:0/003> Complete(Write) operation failed

<ID:0/003> NAND Write Start!! [eventually does nothing and throws errors]

details about the phone odin mode:

PRODUCT NAME: SM-G925F

CURRENT BINARY: Samsung Official

SYSTEM STATUS: Official

REACTIVATIONLOCK LOCK: ON

Secure Download : Enabled

KNOX WARRANTY VOID: 0 (0X0000)

RP SWREV: B:6 K:2 S:2

i'm trying to flash G925FXXU6ERF5_G925FPHN6ERF1.tar with ZEROLTE_EUR_OPEN_HIDDEN50M.pit

any suggestions?
[Honor View 10 Questions & Answers] Rob1hn:
Hi, i really need help, I don't know what to do ...

I tried to flash ma phone with lineageos 16.

But i had some problems with play store, so i tried re-flash lineageos with TWRP.

I must have done something wrong with full wipe but now, my phone can't launch anymore...

It don't launch system or recovery ...

I can turn into fastboot mode but that's all. I tried flash recovery ramdisk with erecovery stock (emui9) but it doesn't launch...

The first picture shows what's one screen when i boot into normal mode and the second one shows what's on screen when i boot into recovery mod.

But after these pictures, nothing happen.... really nothing.... The screen stay like this for long time. The phone comes very hot .... I had to let the battery down to reboot into fastboot mode.

Please anyone can help me ????
[Honor View 10 Questions & Answers] letschky:
Can you boot into eRecovery with Volume up?First Pic Number 2
[Honor View 10 Questions & Answers] Rob1hn:
No...

When I do, it's just the same... Screen block like first picture...

Envoyé de mon F5121 en utilisant Tapatalk
[Honor View 10 Questions & Answers] letschky:
Test a another way,

Power off the Phone.

Press and Hold Volume up and put the USB Cable from your Pc in the Phone and keep volume up until it's booted into the eRecovery

---------- Post added at 06:04 PM ---------- Previous post was at 05:53 PM ----------

that does not work,boot into Fastboot Mode and Flash System,Cust,Boot and Recovery img from Stockrom via Fastboot.

You should know what version you had before, before you flashed Lineage OS.

Download Emui Stockrom and extract the UPDATE.APP with Huawei Extractor and copy System,Cust,Boot and Recovery img in your ADB/Fastboot Folder

You can the Firmware found in Huawei Firmware Finder from Playstore.

Flash all the img files via Fastboot

Huawei Extractor

Did not make Twrp Backup before you flashed Lineageos that could help too.
[Honor View 10 Questions & Answers] Rob1hn:
From pictures attached

which img files i have to flash and which command line i have to use?

Thanks a lot
[Honor View 10 Questions & Answers] shashank1320:
Did you try booting to erecovery? Thats the best way to restore, i messed up my v10 the same way and restored via erecovery.

If not, you may try dload method to restore stock.

Or you may try flashing the system, cust and other img as mentioned in above comment.

Erecovery and dload is still your best bet.
[Honor View 10 Questions & Answers] Rob1hn:
I can't turn into erecovery....

The screen stay on the pictures I uploaded

Which img files exactly I have to flash and which command line I have to use?

Thanks

Envoyé de mon F5121 en utilisant Tapatalk
[Honor View 10 Questions & Answers] shashank1320:
Check one of the guide in my signature to return to stock with such issues.

Here

https://xdaforums.com/honor-view-10/development/return-to-stock-flashing-custom-roms-t3809905
[Honor View 10 Questions & Answers] GuestD0328:
I have the same issue and already tried that. Your guide seems to be for EMUI 8.x and with 9.x some files and partition names have changed so i get errors. Tried adapting it and even managed to flash the system but it does not boot or enter erecovery.

I can even flash twrp on the phone but it gets then stuck on the splashscreen of twrp and doesn*t load further. fastboot boot is not working either and i can't relock the bootloader. I am pretty much out of options.
[Honor View 10 Questions & Answers] elfabio:
I think the partition names have changed because I am in the same situation.

This is my story:

https://xdaforums.com/honor-view-10/help/9-0-0-official-pie-update-failed-boot-t3889378
[Honor View 10 Questions & Answers] Tripar:
I have figured it out. You have to flash ramdisk_recovery and kernel. Then you should get into erecovery with pluged usb in and holding power up and power off/on button. Worked for me. :)
[Honor View 10 Questions & Answers] GuestD0328:
Let's just assume i am a total idiot. Which file exactly did you flash to what partition?
[Honor View 10 Questions & Answers] Tripar:
I have downloaded BKL-L09C432E4R1P9B159 (9.0.0.159) file from this site. Then I downloaded HuaweiExtractor and extracted the update.app file that is located in rom zip. After that i extracted the kernel and recovery_ramdisk files and in fastboot mode write:

fastboot flash kernel KERLEL.IMG

fastboot flash recovery_ramdisk RECOVERY_RAMDIS.IMG (or something like that).

I am not sure if flashing system is needed here, but I did it too.

Hope this helps. :)

EDIT: Those files are for C435.
[Honor View 10 Questions & Answers] GuestD0328:
Sadly this didn't help me. Still stuck at "Your device is booting now..."
[Honor View 10 Questions & Answers] Tripar:
And did you tried to plug in usb and hold volume up and power off? It should boot into erecovery now.
[Honor View 10 Questions & Answers] GuestD0328:
Tried that, no erecovery. I have no idea what i could have done to damage it this badly.
[Honor View 10 Questions & Answers] elfabio:
I think i have already tried this.

1/ Can you say me which fastboot command did you use for flashing kernel and the recovery_ramdisk ?

2/ Can you say me which files (source link or whatever) did you use ?
[Honor View 10 Questions & Answers] Tripar:
I wrote it in the previous post. :)
[Honor View 10 Questions & Answers] ankan1993:
Bro, check my QnA. I explained how it got resolved for me. Or I just got lucky. Unsure! This is quite recoverable.
[Honor View 10 Questions & Answers] GuestD0328:
Where can I find that? Nothing i have tried has worked so far.
[Honor View 10 Questions & Answers] elfabio:
Solved for me too using https://xdaforums.com/showpost.php?p=78662167&postcount=13
[Honor View 10 Questions & Answers] Rob1hn:
hello to all here is what worked for me.

I left the battery completely discharged. Then I connected my phone with the USB cable on my computer.

As soon as the red charging logo appears, I simultaneously pressed the power button and low volume (fastboot mode).

I flashed everything I could flash (kernel, recovery_ramdis, system, etc ...) by extracting img files with huawei extractor.

I downloaded different version emui 9 for my model and tried several.

After flashing, I launched a reboot via fastboot (fastboot reboot).

Important: I have always left the phone connected to the computer, never unplugged it during the whole procedure.

I finally had access to Erecovery!

Only problem, I could not download and install the stock rom via the erecovery. If this is your case, I made a factory reset and a wipe cache then restart. Since I had flashed the system before, it worked!

I hope to help some people!
[Honor View 10 Questions & Answers] JJ2017:
Hi Rob1hn - thanks for post - I have exact same problem (borked installation of TWRP - unable to get back to eRecovery). I've used the extractor tool on the right firmware to get kernel, system and recovery_ramdisk. imgs. Have flashed in fastboot but to no avail!. Any tips on what to try next? Anything else to flash from the update? Let battery go completely flat? Please advise!!

Edit: I am wondering if I should re-lock bootloader from fastboot and then retry - good idea?
[Honor View 10 Questions & Answers] hansiohne:
I was running into the same problem today. I wiped userdata with fastboot (fastboot -w), randomly flashed kernel, system and recovery, then I was able to go to erecovery again (by holding vol + while rebooting, otherwise try to wait for the 1-2-3 screen if it appears and then press vol +) and wipe data (I messed up my data partition in TWRP while trying to wipe it - it won't work due to encryption). then you should be able to enter twrp again.
[Honor View 10 Questions & Answers] JJ2017:
Thanks for posting a reply - I've had this thing soft-bricked for a few days now and was getting desperate!

What cleared it for me was using: 'fastboot erase userdata' - I was a bit reluctant to try that but it did get me back to eRecovery - phew!

I notice on LoS thread you've been trying to install this ROM - any success? (like you I used MoS to unlock the bootloader but I am having big trouble getting Lineage on the device)

Edit: I have finally got Lineage to install on View 10 by rolling back EMUI to 9.0 (from 9.1) using HiSuite - once rolled back everything fairly straightforward :good: