[ROOT][TWRP][MODS][ROMS] WIKO U Feel Prime

[glococo]

Second tool succeed :highfive:
Now I have to restore BT and Wifi macs. Going to try the first tool again.

UPDATE: No luck. Uniscope app still fail with "read sn fail"!

Are you sure you selected the good COM PORT ? (look my picture in attach files of this message)

You can also try this second tool.
https://drive.google.com/open?id=10gfFrkkFOqGaYp-1_ligsur63mWw1Utj

 

[foxyone0809]

Thanks for your fast reply,
See attach. Now I'm going to try your second tool.
Will give you feedback soon.
Thank you so much

something is wrong with your adb driver

 

[foxyone0809]

Second tool succeed :highfive:
Now I have to restore BT and Wifi macs. Going to try the first tool again.

UPDATE: No luck. Uniscope app still fail with "read sn fail"!

no need to restore Bluetooth and wifi Mac Adress.
wifi and Bluetooth will work without restore.

 

[glococo]

Thanks a lot foxyone !

Everything is working + Android 9

no need to restore Bluetooth and wifi Mac Adress.
wifi and Bluetooth will work without restore.

 

[Xpl0it_U]

Qfil gives sahara protocol error when trying to flash this, any solution? (Reffer to the post where you shared the fw, can't quote it)
@foxyone0809

 

[glococo]

I had the same errors. but later after tried many things, I end up using the 1.0.0.3 version which worked fine.

https://androidmtk.com/download-qualcomm-flash-image-loader-qfil

Qfil gives sahara protocol error when trying to flash this, any solution? (Reffer to the post where you shared the fw, can't quote it)
@foxyone0809

 

[Xpl0it_U]

I had the same errors. but later after tried many things, I end up using the 1.0.0.3 version which worked fine.

It doesnt work for me, sahara protocol error, the header is 0kb

---------- Post added at 07:52 PM ---------- Previous post was at 07:25 PM ----------

It doesnt work for me, sahara protocol error, the header is 0kb

nvm, just installed qpst tools and moved the fw to pgfilesx86, Qualcomm, qpst, bin. and it worked

 

[glococo]

Hi Foxyone,
I end up with mine in diagnostic 900e.
I tried deep cable but it didnt change to EDL.

Have you learned anything new about hard debrick?
Btw; in deepCable mode, red led blink at 1hz.

Cheers

 

[karambolage2k3]

no need to restore Bluetooth and wifi Mac Adress.
wifi and Bluetooth will work without restore.

yes but they have changed after switching to yu yureka firmware, so if you want the original one back you have to flash that too.

The whole procedure worked fine for me ... so thanks for the solution! First flashing the yureka FW with the Wiko Firmware tool, then flashing imei. Now I am on AICP Rom (Android 9) and very happy with it

 

[foxyone0809]

Hi Foxyone,
I end up with mine in diagnostic 900e.
I tried deep cable but it didnt change to EDL.

Have you learned anything new about hard debrick?
Btw; in deepCable mode, red led blink at 1hz.

Cheers

do you brick your phone?
I don't understand, because you success install android 9!

 

[glococo]

do you brick your phone?
I don't understand, because you success install android 9!

Yes, after trying to workaround the fingerprint issue with Yureka firmwares, flashed some img, and end up in brick state.
It start in diagnostic 900e. I tried deep cable but it didn't show up in EDL.

It responded to deep flash cable in some way. It start to flash red led once per second, but it still get discovered as 900e in my win7

 

[foxyone0809]

Yes, after trying to workaround the fingerprint issue with Yureka firmwares, flashed some img, and end up in brick state.
It start in diagnostic 900e. I tried deep cable but it didn't show up in EDL.

It responded to deep flash cable in some way. It start to flash red led once per second, but it still get discovered as 900e in my win7

but the fingerprint is ok with yureka black firmware.
I use resurection remix 7 (android pie) for device garlic (yureka Black name code) and all is ok

did you tried to use qfil for flash yureka firmware and repair?

 

[A Trash Can]

apologies on necroposting, but i have took back my own wiko ufeel prime and found a turnaround to the device being "unmoddable" by using another android device.
Check my guide for more

Looks like the whole problem will be called solved