Hi, it's me again, well, now with all the quarentine i decided to unbrick my realme x, after lookin fot software, fiinally reach something that probably may help, but this software uses a "scatter File" instead of .ofp classic of oppo family devices, so, does anyone have the correct tool to convert the file?
searching i already saw different tools to do it, but none of them really have that option
Related
Hi, Need some help here....tired of the same whole mix-mash from htc (recycled phones) so going back to basics - htc s620 (wm6) + my just acquired used 4700. Intend to upgrade it to WM6.1, I've been using htc phones so I am used to rom flashing... or so i thought. I downloaded some of the wm6 and 6.1 roms only to find that dont come with an ruu built in. Not a problem I thought,just get a carrier and replace the nbf file. Unfortunately despite an extensive search on brighthand and here and yahoo searches galore i havent been able to find a suitable guide with the necessary utilities to carry out the flash. The "universal bootLoader" no longer seems to be around (404 errors) samething with other Ruu's (from ru websites etc) yet I can still see thru the long 220 - 251 pg threads that people are flashing with something. In the interest of new 4700 owners would it be possible to have a particular "How-to-flash" thread possibly as a sticky? If not at least can someone help me with a how-to guide and any link to the relevant ruu or bootLoader utility for the rom flash.
Thanx all appreciate it.
You can find all the neccessary information on this page; different ROM's, a bootloader, and instructions in PDF format..
Thanks a lot ridolfo. that has helped a great deal. Slight problem that you hopefully know a way around. After downloading the BootLoader.exe rar file, I tried to open it to proceed but it kept on coming up with an error... "windows cannot open the selected path file...you may not have the appropriate permissions to open them" I just cant get past that altough it has apparently opened and expanded showing a whole lot of other files but i cannot basically get past that stage to run the rom nbf file... Any ideas please?
Right sorted!
Very simple but unexpected solution especially since i hadn't seen the issue mentioned elsewhere.
Simply disconnected all connections to the internet especially wifi (for safety/protection etc) and then disabled zone alarm!
Everything went thru as normal,updated and now just waiting for boot-up.
thanx a lot Ridolfo!!!
Quote:
Originally Posted by kippsoft
Hi guys...
After alot, alot of work and problems...
I am happy to announce to you that I found solution to your Alcatel OT-918(All)..
Pre-requisites:
SP Flash tool(I have attached it)
One Touch Upgrade from Alcatel site
The 3 Alcatel ROM files(Attached)
Fully charged phone.
Steps
Download the appropriate ROM file for your phone and extract it to a folder.
Download Alcatel One Touch Upgrade for your phone ...Click here for Alcatel OT-918 Upgrade Tool...
Download the SP Flash tool(Attached)
Install appropriate USB drivers for your phone..
Using SP Flash tool push the 3 files(Download) to the smart phone...click here is an example of how to download...
Ensure it is successful..
Remove phone's battery,re-insert.
Open the upgrade tool and follow its help file on how to upgrade.
Thanks
NOW MY PART
-------------------------------------------------------------------------------------------------------------------------------
PLEASE NOTE THAT MY PHONE IS OT-918D
I didn't even know what was the imei of the phone was or the phone model but used SP-FLASH tool with many different versions of scatter files untill I came across the one that was used for installing recovery on ot-918 from a different website.
I even got to the point that the phone wouldn't come on after trying different models of the 918, but luckily usb worked.
WHAT YOU NEED
SP_Flash_Tool
One Touch Upgrade from Alcatel site
Scatter Files in the zip file below.
FILES TO USE ON THE SP-FLASH TOOL:
MT6573_Android_scatter_2_3_5_OT_918.txt
AND TICK THIS FILES :
dsp_bl
preloader
pro_info
NOTE: sometimes you have to press and hold the center button for the phone to be detected in order to accomplish the above procedure. Just make sure you remove the battery each time you try..
Then open the Alcatel Upgrade tool , this time it won't tell you that your phone is already up-todate. then proceed with the upgrade.
NB:MAKE SURE YOU USE A LOWER ANDROID VERSION E.G 2.3.5 SCATTER FILE OR ELSE ALCATE UPGRADE WILL SAY PHONE ALREADY UP TO DATE.
This applies to even a phone that won't come on(Mine was dead and couldnt come on only charging, and after fixing it, I discover that I had spoiled the display fiber since the phone was not displaying anything.)
Unfortunately I had to do the whole thing from a dead screen after pulling it apart prior to unbricking it.
You can find your serial number and phone model in the Alcatel upgrade file called otus_log.txt
Incase mine was in C:\ONE TOUCH Upgrade S 2.8.0\otus_log
I think that this method might work on all Alcatel MT65xx Phones.
But now that the phone works I have to get a new display.
918 Is dual sim !
After puling apart my phone which I have always assumed to be single sim(This apparently caused alot of confusion as to which Rom to use), I realize a second Sim card slot right beneath the top slot although it's hidden and not accessible if you replace the chasis , so you guys might want to try a possible second simcard for you 918 phones, that I suppose is the reason why some guys could install dual sim roms and fail to access fast speed since it's using the secondary sim card, I haven't tested it since I have not acquired the screen yet.
I'm grateful for any ideas at this point. The model no. is 4037R, the provider ID is: 4037R-2BVHCA1 (n.b. The Alcatel OneTouch Pop D3 is very similar if not same as the "Evolve 2" model).
Using SP Flash Tool I tried "Firmware Upgrade" as an option when I was having errors. But I had no preloader file to flash, note. Even though all options were checked, I only had the recovery.img file to flash. I think this bricking may have occurred because I flashed the wrong MT65xx MediaTek scatter file. The one that came with the files, MT6572, wouldn't work ending with a "BROM" error 1003. It said the chip was an MT6582. So I flashed a generic MT6582 scatter file. That finally gave me the "OK", but of course it wasn't OK. The phone is no longer recognized by adb, and just barely recognized by the PC.
Problem is, I'm not exactly sure what MediaTek chipset this phone has, and where to get the scatter file for it, and more importantly, where to get the firmware for it (which should contain the scatter file, if I'm not mistaken). Apparently, you can definitely unbrick these types of phones if you have the right scatter file! Needless to say, I did not make backups of anything!
I don't claim to be an expert but maybe I can be of assistance. Sounds like you might have flashed a wrong preloader or something. If the computer still reads it then you still have hopes of flashing the right one if you can get your hands on it. If you can provide a picture showing your model number/ provider ID, I might be able to assist you.
I'm grateful for any ideas at this point. The model no. is 4037R, the provider ID is: 4037R-2BVHCA1 (n.b. The Alcatel OneTouch Pop D3 is very similar if not same as the "Evolve 2" model).
Using SP Flash Tool I tried "Firmware Upgrade" as an option when I was having errors. But I had no preloader file to flash, note. Even though all options were checked, I only had the recovery.img file to flash. I think this bricking may have occurred because I flashed the wrong MT65xx MediaTek scatter file. The one that came with the files, MT6572, wouldn't work ending with a "BROM" error 1003. It said the chip was an MT6582. So I flashed a generic MT6582 scatter file. That finally gave me the "OK", but of course it wasn't OK. The phone is no longer recognized by adb, and just barely recognized by the PC.
Problem is, I'm not exactly sure what MediaTek chipset this phone has, and where to get the scatter file for it, and more importantly, where to get the firmware for it (which should contain the scatter file, if I'm not mistaken). Apparently, you can definitely unbrick these types of phones if you have the right scatter file! Needless to say, I did not make backups of anything!
You can unbrick it with the right file. Unfortunately i have them in OSP format which is probably useless to you since I don't have the password to unzip it. To find out the chip you can use MTK Droid Tools. Based on what you said, I can say with uttermost confidence that you have a preloader/boot issue seeing as you probably flash a blank partition over them. The right file will definitely fix it but i haven't found one yet. Will keep looking for you. Would be a breeze if you were in Saint Lucia. lol
Edit: Also something I feel the need to point out is that the 4037* phones have different chipsets and their roms are NOT interchangable. Even the same model (your for example) under different carriers (2BVHCA1 in your case) sometimes give mixed results which i learned the hard way (I had a 4037A working on recently)
That sounds very likely that I flashed a blank partition as you mention, since at one point I chose "firmware upgrade", to try to get past an error I was getting. This forces checkmarks on all ROM sections (including preloader), even though I only had a file for recovery. Unfortunately, MTK Droid Tools (and adb) is pretty useless to me now, as it won't recognize the phone. It looks like I can only flash things via SP Flash Tool.
Since I have no hope any longer of finding a stock ROM for a 4037R OneTouch Pop D3, much less a scatter file, I was really hoping that I could try to flash whatever ROM I can get my hands on that is the closest to it. ie. An "Evolve 2" (4037T)? But if what you say is so, that it has to be the exact ROM for this model, then I don't know how I''ll ever find that. Even a search on Alcatel's website for the 4037R turned up 0 results!
I wonder, if I had a 4037A ROM and flashed that.... could I at least use that to get the phone up and running, even if, say cell / wifi dont work??
As long as the computer reads in without a battery you should at least be able to pull a scatter .txt file which will tell you the chip version even if everything else may be useless. Also you can try the mobile upgrade tool and select 4037 as your phone model. I cannot try it myself but it might work.
http://www.alcatel-mobile.com/global-en/support/product?id=338&model=POP D3
Also if you can i suspect it might be easier to get a similar phone and get a rom dump because the internet isn't too happy about sharing that particular phone's firmware
I had already tried fixing it with Alcatel's Mobile Upgrade tool. I'm afraid it won't recognize the phone without a battery. Nor will MTK Droid Tool (battery in or out), so I can't use that to pull in a scatter file. The PC only seems to recognize the device when the battery is in. (In Mobile Upgrade, with the battery in, I get: "Read terminal information failed...unplug and remove battery". No battery also didn't work in SP Tools, when I specified "without battery" in the options). In fact, even though the PC recognizes a device when the battery is in, it goes bonkers (keeps restarting every 2 seconds). I am still able to flash using SP Tools, however.
I thought about getting another OneTouch Pop D3 to pull the necessary files off of that. But that's not possible, they don't sell it any longer since a long time. Is there maybe another ROM I can download you think might work? The 4037A perhaps? I realize it's risky, but what else can I do?!
I used my 4037R phone to generate a scatter file because I kept getting a BROM ERROR: S_CHIP_TYRE_NOT_MATCH(3168) with the scatter files that I would find online. But even with this generated scatter file I would still get a BROM ERROR: S_CHIP_TYRE_NOT_MATCH(3168) error.
The only scatter file that would work is the MT6582.
But now I can't find a recovery image that will flash properly. I keep getting a S_DL_GET_DRAM_SETTING_FAIL error with every image I try. Do you have a recovery image file that flashed with the 4037R ?
okay let start, my friend gave me his LG G4 with BOOT LOOP issue.
so i did like in the video
https://www.youtube.com/watch?v=TM9umec5aeo
the phone worked for 5 hours and back to boot loop issue. so in this time i made backup.
after it i follow this guide
https://forum.xda-developers.com/g4/development/ilapo-infinite-loop-auto-power-off-fix-t3404421
but the friend phone has marshmallow android and i need lollipop android so i have flashed wrong ktz by mistake and phone gone to Brick mode.
so i search a lot in the internet MBN file for G4 and i found so i want to share it with you
just download the files from next linkaccording to your model
http://bit.ly/2maK3uL
or
Code:
http://forum.gsmdevelopers.com/showthread.php?t=24303
the password for H815 is "Moyal Software H815",for other just PM to dev.
after i downgraded to android 5.5 i continue with
https://forum.xda-developers.com/g4/development/ilapo-infinite-loop-auto-power-off-fix-t3404421
and after it i reactive the reset cores with kernel adiutor.
right now the phone works well already 4 days.
Enjoy.
These are the exact same files as already given in another thread. They don't work for me.
Depending on QFIL version I have "Device not in firehose mode" or "too long to open COM port" error.
I have H815. Bricked the exact same way as yours.
Do you have any ideas what I can change/try?
Dear,
I have the same problem with a H818P.
Someone can help me!?
I`ve attached a screenshot with my problem!
https://ibb.co/hVthyv
I`m stuck in "COM Port number 5"
in device manager, is not possible to find "Qualcomm MMC Storage USB Device" under disk drivers.
thanks!
rfsaidel said:
Dear,
I have the same problem with a H818P.
Someone can help me!?
I`ve attached a screenshot with my problem!
https://ibb.co/hVthyv
I`m stuck in "COM Port number 5"
in device manager, is not possible to find "Qualcomm MMC Storage USB Device" under disk drivers.
thanks!
Click to expand...
Click to collapse
Hey, I have struggled long time with this but finally I got it to work
I used this guide:
http://gsmmarhaba.com/threads/unbrick-lg-g4-brick-hs-usb-qdloader-9008-without-box.612/
But instead files for H815 i used ones for LS991 and QPST 2.7.425. Files were flashed successfully and now I have download mode
So try with other versions of mbn files as well as with other versions of QPST/QFIL. Good luck.
washoq said:
Hey, I have struggled long time with this but finally I got it to work
I used this guide:
http://gsmmarhaba.com/threads/unbrick-lg-g4-brick-hs-usb-qdloader-9008-without-box.612/
But instead files for H815 i used ones for LS991 and QPST 2.7.425. Files were flashed successfully and now I have download mode
So try with other versions of mbn files as well as with other versions of QPST/QFIL. Good luck.
Click to expand...
Click to collapse
Thank you ! I'll try this and will send a message with final result.
I can Help
washoq said:
These are the exact same files as already given in another thread. They don't work for me.
Depending on QFIL version I have "Device not in firehose mode" or "too long to open COM port" error.
I have H815. Bricked the exact same way as yours.
Do you have any ideas what I can change/try?
Click to expand...
Click to collapse
I have a solution, BTW have you solved your issue
washoq said:
Hey, I have struggled long time with this but finally I got it to work
I used this guide:
http://gsmmarhaba.com/threads/unbrick-lg-g4-brick-hs-usb-qdloader-9008-without-box.612/
But instead files for H815 i used ones for LS991 and QPST 2.7.425. Files were flashed successfully and now I have download mode
So try with other versions of mbn files as well as with other versions of QPST/QFIL. Good luck.
Click to expand...
Click to collapse
Dear Washoq!
The mega.nz link (provided on the page you shared) is expired. Can you please upload the files yourself and share them here?
For fusing devices h815, to get download mode
https://mega.nz/#F!GJ9WlCYA!IT57novfFmId67gUt7_QPQ
Pleas bro all links are broken pleas update
Hey everybody. I am looking for mbn or firehose files so i can try to revive my hard bricked Nokia XL. I dont know the history of the device, because i have bought it online in hope of fixing it. My best guess is that somebody flashed V2 files on this device. The device shows as QDLoader 9008. I have read some tutorials and the problem is, dont have money, nor do i know where to buy a jtag box in order to flash boot files that way. QPST is my only hope but as you can guess from the title, i cannot find proper boot files for my device that will work on QPST. Thank you in advance for help