yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] Teblakuda4o4:
When i flash the Wiko MM with Blu's Secro and preloader, device is Soft Bricked and wont turn on. Are there any steps that are missed? Like do a manual format with spflashtools first before flashing the Wiko Firmware.
[Miscellaneous Android Development] Jorge_007:
Did you use "BLU_L0070UU_V12_M_GENERIC_RAW.rar?" If so, you bricked your device. That firmware seems to be a bad dump. I checked the kernel boot images from Marshmallow OTA and the RAR file posted here and they are not the same file size. It could be because of compression. What bricked your phone was the "BLU preloader found in the Marshmallow image. Go back to lollipop and do all the updates. Don't format all or you'll lose IMEI. I posted a link a few post back with lollipop firmware. If SP Flash tool does not detect your phone you'll have take the phone apart and pull the battery.

EDIT: I uploaded the preloader from the lollipop repair image. Replace the preloader in the firmware with the one in the zip and flash using SP Flash Tools if you want your phone to come back to life quickly. I recommend going back to lollipop and do all the updates though and make a TWRP backup of Marshmallow.
[Miscellaneous Android Development] Teblakuda4o4:
Thanks, so should i flash the LP preloader and secro with the Wiko MM firmware instead to avoid Brick and keep baseband? I have all the necessary files to recover from the brick, just letting it charge for a bit to have spflashtools read. I've bricked this blu more than 12 times already :D
[Miscellaneous Android Development] Jorge_007:
I haven't been able to get baseband working. Yes, Wiko MM should install with the LP preloader without bricking the device. I tried using mobile uncle, but the app says "not supported" when trying to backup IMEI on stock BLU MM. Good luck! If you get baseband you should let people here know.
[Miscellaneous Android Development] Teblakuda4o4:
Finally got oreo working with sims. Ill post wt i did soon

---------- Post added at 01:47 PM ---------- Previous post was at 01:13 PM ----------

To get Oreo working on Blu, do the following:

1. On Stock Blu MM backup IMEI using Mobile Uncle app. Put this backup on SDCARD so it does not get erased when you flash later.

2. SPFlashTools>Format> Do an "Auto Format" flashing all except bootloader.

3. SPFlashTools> "Format and Download" Wiko LP v11 Firmware but with BLU LP Preloader and Secro.

4. When phone Boots up, check that baseband is not saying "Unknown". Sim will not be working at this point.

***Next Upgrade to Marshmallow before Continuing*** (Somehow after flashing Wiko LP i was already on Wiko MM, so just to be safe, upgrade to MM before continuing)

5. Unlock Bootloader, flash twrp and flash magisk 16.0.

6. Install MobileUncle and restore IMEI.

7. Go to TWRP, install Oreo TWRP and reboot recovery. Found on facebook page https://www.facebook.com/notes/mad/rom-810-official-mados-wiko-fever-mt6753/1640799096003857/

8. (Optional) Backup NVRAM just in case.

9. Do a factory reset and finally flash madOS_8.1.0_fever_20180318.zip and open_gapps-arm64-8.1-pico-20180311.zip.

Bugs I've Noticed:

- Flashlight only works on Front Flash

- Camera only has FrontCam View and is upside-down.

- Double tap to wake screen not working
[Miscellaneous Android Development] mrmazak:
Now if you flash the blu modem do you get the US lte bands to work?
[Miscellaneous Android Development] Teblakuda4o4:
My bands are working without flashing any modem fix. So I don't think it is necessary but you could test it.
[Miscellaneous Android Development] mrmazak:
I have been haveing much trouble getting mobile uncle to connect to stock mm and make the backup.

The versions in the link i put up on page 6 (v3.3.3 and v2.9.9) did not work for me. I searched around net and found version 3.0.0 and that worked.
[Miscellaneous Android Development] Rikadoo:
Hi guys, I managed to root my device by following a guide on youtube, and it finally worked! Despite my problem (my device could not be connected to the PC to be switched on ...). I leave the link to the tutorial

https://www.youtube.com/watch?v=UJr1HRNDPd0

Tomorrow I will try to install the ROM ..

But i think I will start your procedure from second point, because I already installed twrp custom recovery.... I hope that when I will installed android Oreo, port usb will work.... With charging and with pc...
[Miscellaneous Android Development] Teblakuda4o4:
Yes, i also used Mobile Uncle v3.0.0 to backup and restore... and you need root access to use mobileuncle.

---------- Post added at 08:44 PM ---------- Previous post was at 08:31 PM ----------

How do i test Network bands to see the difference before and after i flash the Blu modem fix?
[Miscellaneous Android Development] mrmazak:
There are few aps on play that can be used.

Here is one

==>

==> signal check lite
[Miscellaneous Android Development] Teblakuda4o4:
Limited to HSPA+ (3G) it seems. I am creating a twrp backup now then i'll try the madOS_Oreo_8.1.0_BLU_modem_patch.zip fix. Hopefully this doesn't break the Rom :D

*****UPDATE***

Do not flash Modem Fix for Blu Oreo you will lose baseband.
[Miscellaneous Android Development] mrmazak:
So it's clear. What modem find did you use?

Was it one flashing files to vendor folder?

And only the modem files , not the whole firmware forlder.
[Miscellaneous Android Development] Teblakuda4o4:
Yes the one flashing to vendor folder, made for and labelled for fixing Blu modem on Oreo.
[Miscellaneous Android Development] Teblakuda4o4:
Mysteriously, after flashing the modem fix, breaking my baseband and restoring to the twrp backup I made beforehand, all my camera bugs are gone. Even he flash is working properly for Torchlight.

***Update

And just like that it's broken again.
[Miscellaneous Android Development] mrmazak:
can you compare the modem fix zip you have to the one I attach here.

I cannot find the one you mentioned anywhere.
[Miscellaneous Android Development] Teblakuda4o4:
No the one you have is different from what I used. I got it on the faceboom page. I would send u a screenshot of the files but I'm not at my computer rn.
[Miscellaneous Android Development] Teblakuda4o4:
These are the files the one I have contain. I also included a screenshot of the update script.
[Miscellaneous Android Development] mrmazak:
That looks similar to the way I first tried (i did not have working baseband at the time though, like you do now)..

posts #23,#24,& #25

https://xdaforums.com/android/development/rom-official-mados-wiko-fever-clones-t3762800/page3

There It was suggested to change the update to way I posted above.

When You have a chance, If you would, give it a try.
[Miscellaneous Android Development] Rikadoo:
_________________________________________________

Hello everyone,

I followed point 1.1 of your tutorial, and then following procedure,

https://www.youtube.com/watch?v=UJr1HRNDPd0

I installed the custom recovery: "team win recovey project" that you see in the attached image,

i ask, the procedure that I write below is right?

1) copy "twrp_wiko_fever_oreo.img" and "madOS_8.1.0_fever_2018xxyy.zip" into a folder on the phone, named "android oreo"

2) Start the custom recovery "team win recovey project", I go on installation (I put image option) I select the folder (open the folder) "android oreo", and drag the bar at the bottom, from left to right.

3) Once installed, I press back repeatedly and restart the system;

4) I follow point 3.0 of your tutorial;

5) Unfortunately, the points 3.1 3.2 3.3 and 3.4 can not run because my phone can no longer be connected to the PC. Are they indispensable? OR CAN I PASS DIRECTLY TO POINT 3.4 ??

Thank you for your understanding and your help.

Riccardo
[Miscellaneous Android Development] DerTeufel1980:
You said, you copied the files already to the phone. Then just install those
[Miscellaneous Android Development] Teblakuda4o4:
Just tried it. It did not break my baseband however I am unable to tell if it made a difference as the network I am on does not fully support LTE. They are still testing it and will probably implement it in the coming months. So all I can say is u can flash it as it is safe and won't break ur baseband.
[Miscellaneous Android Development] Rikadoo:
I managed to install the Oreo ROM. I installed Gapps Pico version, but it gives me problems, says that google service has stopped working, I'll try to install Gapps again, but the version a little 'bigger ....

Unfortunately, I found that my initial problem remained, and that is that the phone is only charged if it is turned off. Probably the problem must be at kernel level or hardware .... Many here in Italy after the update to MM have had this problem, they probably threw the device ... I tried to install another OS ....
[Miscellaneous Android Development] Harishwarrior:
Bro...you need to flash it when you flash the rom with full wipe...if you flash it after a boot it will cause this type of issues...
[Miscellaneous Android Development] superdragonpt:
Install ROM+gapps at the same time

Else, you'll get force closes

Cheers
[Miscellaneous Android Development] Rikadoo:
thank's

Hello guys,

I'm happy because now google apps work. As I was advised, I installed the ROM and Gapp pico version together.

I would be much happier if I could solve the problem of connection to the PC and the connection to the mains, when the device is on.

I will look to see if there is any thread that talks about this topic.

Thanks again

Riccardo

---------- Post added at 09:25 PM ---------- Previous post was at 09:09 PM ----------

Thanks Der teufen,

I think that my problem concerns only my phone, because after I switched from Lollipop to MM he gave me this problem. If it were a driver talk to be installed in the computer, the device would not load from off ..... be connected to the PC and the mains ....

:pianto:
[Miscellaneous Android Development] DerTeufel1980:
those of you with baseband gone...and if you are rooted.... could you please check in /nvdata, if there is any file with 'fstab' in its name

maybe you just need to update your windows drivers.
[Miscellaneous Android Development] Nourixe:
hello , yes there is it's fstab.mt6735 and no imei working can you help please , when i was in the 7.1.2 rom i had the same problem to fix it i just deleted the content of nvram folder then after a minute everything worked byitself but in this oreo it doesnt't work :/
[Miscellaneous Android Development] superdragonpt:
...or see the light and switch to Unix

Cheers
[Miscellaneous Android Development] DerTeufel1980:
I was expecting there to not have a fstab... This could have been a reason for the issue.

Maybe yours is another problem... But, what 7.1.2 rom are you referring to?

And what's your device?
[Miscellaneous Android Development] Nourixe:
i was on resurection remix 5.8.5 android 7.1.2 and i'm on wiko fever
[Miscellaneous Android Development] DerTeufel1980:
Then you probably 'just' have deleted your nvram, probably by using 'format all + download' anytime before.

You need to fix this on stock rom, by using 'sn writetool' or 'maui meta 3g'.

There are several tutorials in the net.
[Miscellaneous Android Development] FERRARI81:
In adding:

It's not a real bug, but SIM Application Toolkit is missing on this ROM.

My operator (it is an italian Full MVNO) doesn't work out of country without that application (it's needed to exchange some automatic message between operator and the smarthpone). I solved with Google Carrier Services, but I don't know if in other country it's strictrly needed.
[Miscellaneous Android Development] Rikadoo:
could you tell me the path of this "nvdata" folder?

I entered recovery mode, file manager, ... and then?

I remember, a few years ago, when you installed Windows 8.1 had the problem with the file "Rasppoe.sys" that had to be replaced.

In my opinion it should be a similar error, when there was the update of Android from LP to MM, some system files or drivers has not been programmed well .......
[Miscellaneous Android Development] NekuR:
Wiko Fever 4G HardBrick

Guys! I need some help with a HardBricked Wiko Fever 4G.

It don't turn on and I have not idea for flash it.

I tried to use SP Flash Tool but I can't do it.

I received:

ERROR: S_COM_PORT_OPEN_FAIL (1013)

[COM] Failed to open COM port.

ERROR: S_BROM_CMD_STARTCMD_FAIL(2005)

ERROR: S_FT_DA_NO_RESPONSE (4001)

DA didn't send responde data to FlashTool!

Help me, pls. I am so desperate...
[Miscellaneous Android Development] DerTeufel1980:
Try another pc, other usb port and/or check that you installed the drivers.

Also, how did you brick it at all?
[Miscellaneous Android Development] Nourixe:
bro where i found it wasnt on nvdata folder but in the root , are you having the same imei probelm too ?
[Miscellaneous Android Development] Rikadoo:
I have the problem that my device charge only when is switched off.... Also to computer and also to mains....

When I did check hardware, response was that usb hasn't worked, ..... (?) But when device is switched off usb work! Mystery......

In Italy with upgrade from LP to MM, many people had this problem.... Someone has fixed many people instead no....... (Like me)....
[Miscellaneous Android Development] Nourixe:
have you tried to go back to mm stock with pc ?
[Miscellaneous Android Development] Rikadoo:
No because I can't connect wiko fever and pc....

---------- Post added at 02:32 PM ---------- Previous post was at 02:30 PM ----------
[Miscellaneous Android Development] NekuR:
[YOUTUBE][/YOUTUBE]

My brother tried to format device with softreset. But he obtained BootLoop and he tried to format again with TWRP recovery. And the mobile didn't turn on, died.

But thanks! Works fine!
[Miscellaneous Android Development] DerTeufel1980:
i have to admit, that i don't understand some of the things you said...either by bad english (this can happen) or by quoting unrelated posts (maybe i just didn't understand the connection?)

- for usb problems on android 6 and higher, you need to (re)install the mtp drivers in windows (check the device manager, the yellow '!'), or switch to linux, which just works fine

- for 'bricked' devices...unless you flashed a wrong preloader from another device, which is not wiko fever or a clone, you can't brick it! you maybe can format system, causing the phone not to boot, but it's not actually bricked. In any way, just flash your stock mm with flashtool (firmware upgrade mode) and you're back

- for nvdata. Everyone has this. this folder is in the root of the filesystem. this is where also is /system or /data. Because of a typo I made, it just can be possible, that there is no fstab.mt6735 in /nvdata. this fstab still is in the root of the filesystem. It could be possible, that copying the fstab from the root to /nvdata fixes the missing baseband (especially talking about blu)
[Miscellaneous Android Development] @adi5520:
Please fix the issue even for micromax canvas 5 and let us know about it?
[Miscellaneous Android Development] Rikadoo:
Thanks Derteufel1980,

I understand what you want to say about Android 6.0 and later versions need to install drivers for Windows 10.

But my problem is different.

Since I updated 2 months ago, Android stock MM (before there was 5.1 LP version), my smartphone has this problem: the battery is charged ONLY when the phone is switched off.

I put the video link where this problem is explained very clearly.

https://www.youtube.com/watch?v=EWPfgZ3t_kM

In Italy, as I think also in all the other countries where this device was sold, many people have encountered this problem, since there were also online articles that talked about this problem (see link).

http://www.optimaitalia.com/blog/20...ornamento-marshmallow-un-primo-rimedio/376115

I have felt that installing an operating system could solve this problem. Instead I found that the problem remained.

For NVdata, i havent this folder, I looked everywhere, i will try to search better to copy in right folder maybe to solve my problem? i understand well?

That's all.

Sorry for my bad english, but I use the google translator .....
[Miscellaneous Android Development] mrmazak:
One voice on this thread has shown the ==>way.

I have just been watching this for now. I have been messing with a different device , so I made no progress(not that I could )

Now that there is also chance a simpler solution may be here.

I will reflashed Oreo (straight from blu mm,

not

formating to wiko) and see if fstab is missing or not in nvram folder.
[Miscellaneous Android Development] mrmazak:
Fstab is present in the madOS.

compared the nvdata folder to copied version from on BLU LOX and looks like there is an extra folder.

/data/nvram/md/NVRAM/IMPORTNT

owner and group of files is nvram nvram

so still only known "working" method requires formatting device and flashing firmware upgrade in MM before upgrade to OREO.
[Miscellaneous Android Development] Rikadoo:
Sorry, but I just can not see this file fstab.mt6735. I enclose the image of the data folder, you can not see it anywhere ...

Is there a "search" in order to find this file?
[Miscellaneous Android Development] mrmazak:
Need to be rooted.
[Miscellaneous Android Development] DerTeufel1980:
The /nvdata as well as the fstab are not in /data.

The fstab.mt6735 is in the root of the filesystem '/' and it should also be in /nvdata. And /nvdata is also in the root of the filesystem.

Else I had written /data/nvdata. Or /data/fstab....I hope you get what I mean.

If you are in /data, navigate one level up to /

Then look for /nvdata
[Miscellaneous Android Development] mrmazak:
Oh, OK.

It is also there in the root /
[Miscellaneous Android Development] DerTeufel1980:
Too bad, this is not the issue/fix then...
[Miscellaneous Android Development] Teblakuda4o4:
I have working Baseband on BLU and i can confirm that there is an fstab.mt6735 file in the root/, nvram/ folder and also Data/Nvram/ folder. Just saying
[Miscellaneous Android Development] mrmazak:
I have not followed the same process, just because I can't understand the reason why it works that way but not when I flashed without formating.

Only difference I can see is the addition of partition, that I find no reference to in any of the init files of the rom.

Wiko has one extra partition. Compared to blu.

I am gonna poke around for little more before I cave in and do the format method.
[Miscellaneous Android Development] DerTeufel1980:
Great, I just found your edited guide for the update process, and have added it to the FAQ.
[Miscellaneous Android Development] mrmazak:
I tried the same process [MENTION=7263416]Teblakuda4o4[/MENTION] has laid out. But I went straight to wiko's MM version. And I could not restore IMEI or baseband.

Then restored previous version of BLU MM , still could not restore baseband and IMEI.

I needed to go back to BLU V12 LP rom , then sn writer was able to restore IMEI and baseband was valid and present.

SO It appears as the process MUST be as laid out. Flash wiko LP rom , restore IMEI, then update to MM, Finnally up to MADOS Oreo

I still have not finished the process. Too busy takeing notes I guess. And I keep going back to original state to start over from fresh.
[Miscellaneous Android Development] Teblakuda4o4:
Sn writer works in Blu v12 LP?! Hmm never knew. Yeah I suspect it works on LP and not mm because we are using LP preloaders and secro. Blu mm preloader and secro are stupid and don't work when used with wiko mm firmware. Still not sure why but the initial manual format is vital to getting baseband to show up.

Maybe during this week I could go thru the process again and see if there are any steps that can be skipped.
[Miscellaneous Android Development] mrmazak:
A side note to add is. Even though sn writer could not write IMEI when MM installed, it could connect to device. It would fail to "get version" But when I tried to load a DB file it returned with an error message stating the file I was trying to load did not match then version reported as being loaded on device. It displayed the loaded baseband that was loaded at that point.

Does This suggests it is a permission issue that makes baseband show as unknown , not that it is missing.?
[Miscellaneous Android Development] alex moymoy:
Hi DerTeufel ? I want to thank you for this work. I have this running on my wiko almost a week and I don't have nothing wrong to say. Working sweet. No issues on day use. Seriously I'm very happy with it. I had issues with another ROMs but not with this one. Thanks allot ? great work ??
[Miscellaneous Android Development] DerTeufel1980:
Oh, I never digged deeper into maui meta or other tools. No idea what this actually means
[Miscellaneous Android Development] Rikadoo:
sorry, I saw that in the changelog of March 19, post # 3, the problem of recharging was solved only when switched off. If I download the rom now and install it, does everything work? I installed the downloaded file with the name "madOS_8.1.0_fever_20180318".

Thank you:bene:

to reinstall I have to do some wipe? Or it is enough to flash.
[Miscellaneous Android Development] DerTeufel1980:
I just had uploaded it later, than I had built it. That's the latest file you got
[Miscellaneous Android Development] Betamonster:
IMEI

1. On Stock Blu MM backup IMEI using Mobile Uncle app. Put this backup on SDCARD so it does not get erased when you flash later.

2. SPFlashTools>Format> Do an "Auto Format" flashing all except bootloader.

3. SPFlashTools> "Format and Download" Wiko LP v11 Firmware but with BLU LP Preloader and Secro.

4. When phone Boots up, check that baseband is not saying "Unknown". Sim will not be working at this point.

Can you please help me find and understand what to do in step 2 and 3? Thanks.
[Miscellaneous Android Development] mrmazak:
2. On the format tab of sp flash tool , select auot and all except bootloader

3. on download tab select the drop down menu , select format and download.

and in the firmware folder for the V11 wiko rom paste the preloader file and secro file from the blu v12 repair rom.
[Miscellaneous Android Development] Rikadoo:
This file is for note3 and not for wiko fever ...

I think you were wrong to upload the file, I tried to install it but it crashes and says that the file is for note3 ...
[Miscellaneous Android Development] DerTeufel1980:
Maybe you downloaded the wrong file. The link you posted points to the wiko fb post. And the link to download the rom points to a file with wiko in its name. The name is auto generated during build, depending what I build for.

This can't be anything else

Sent from my K6000 Plus running madOS O-8.1.0
[Miscellaneous Android Development] zaxscd01:
I appreciate the detailed screenshots. However, in the last screenshot, can you please clarify why you have "to wiko v11" written in red but the circled archive name shows FEVER Marshmallow_V34? Does that means we should be able to paste the two files from the blu V12 LP repair rom directly to wiko MM V34 and not bother with wiko LP V11? I notice that the guide written by Teblakuda4o4 states that the device was still in MM despite flashing wiko LP v11, so that would make sense.

Thanks in advance for your help!
[Miscellaneous Android Development] mrmazak:
When I tried I used wiko v34. I could not restore imei, I still had unknown baseband. Teblakuda4o4 had success with v11 so I wrote v11 over my screen shot. I do not have v11 downloaded so I can't take photo of that.
[Miscellaneous Android Development] DerTeufel1980:
You didn't update to this rom at all yet? Or did you find another way to get baseband working?
[Miscellaneous Android Development] mrmazak:
on the rom without baseband at the moment

I have been busy with mods to my honor 7x lately, not done anything with the LOX in weeks