Related
I am asking this because recently bought a BLU VIVO D910a phone from U.S., it has Android 4.0 firmware and its 3G Network is HSDPA 850 / 1900.
I made a big mistake, because the country where I currently live and work (Montenegro) uses 2100 3G network. I shoud have ordered the international version of BLU Vivo, the D910i which has HSDPA 850 / 2100. So, currently I cannot make use of the 3G data capability of my new phone
My question is: if I get the firmware (or just the modem.bin) of D910i and flash it to my phone will I change by this way the 3G frequency or it is hardware-dependent?
Thanks.
I think yes.
Sent using Tapatalk 2
Yes to what? Flashable or hardware-dependent?
ctibor said:
Yes to what? Flashable or hardware-dependent?
Click to expand...
Click to collapse
Flashable. :thumbup::thumbup:
Sent from my E15i using Tapatalk 2
ctibor said:
I am asking this because recently bought a BLU VIVO D910a phone from U.S., it has Android 4.0 firmware and its 3G Network is HSDPA 850 / 1900.
I made a big mistake, because the country where I currently live and work (Montenegro) uses 2100 3G network. I shoud have ordered the international version of BLU Vivo, the D910i which has HSDPA 850 / 2100. So, currently I cannot make use of the 3G data capability of my new phone
My question is: if I get the firmware (or just the modem.bin) of D910i and flash it to my phone will I change by this way the 3G frequency or it is hardware-dependent?
Thanks.
Click to expand...
Click to collapse
Hi!
Sorry for resurrecting this thread, have you solved your problem by flashing another modem.bin? If not, could you please send me a copy of your phone's modem.bin so I can try? I have a Newman N1 (mt6577 like yours) with 900/2100 bands and I need 850/1900 to enable 3G on my country.
Thanks!
Old Thread, new info
Figured I would post a belated follow-up on this thread so it's out there to help someone else. I have a D910a phone (yes the North American flavor). I've had it for a couple years now and only real complaints are the absolutely horrid GPS sensitivity and terrible low-light/white balance performance on the camera. That aside, my phone recently it experienced what I can only be describe as a sudden bout of crappiness. After hours and hours of digging through XDA forums I did locate the slightly older version (v3.1224.01) of the "Smart Phone Flash Tool" or simply SP_Flash_Tool (spft) Turns out the newer version, v3.1328.0, had issues as mentioned in at least one post I found. Also useful was the MtkDroidTools which I used to create the "scatter" file required by spft. I did locate sptf .img's for both CWM and TWRP recovery partitions but unfortunately the only spft rom image to be posted anywhere is the 910i version which I'll get to in a moment. The only 910a backup rom I could find was in CWM/ nandroid format so not all that useful considering I couldn't even boot and the CWM recovery I found doesn't seem to like that format. MTK VCOM drivers also had to get installed. To save someone some frustration, SPTF only connects to the phone with battery out and you plug in just the USB cable (just like the tutorial on XDA says)... the non-obvious catch is that SPTF has to be listening for the port to exist by initiating either a download or readback prior to plugging in the phone. The port is only present for a few seconds before the embedded MTK chipset loader turns it back off.
So here was the issue, plugged in the phone and set it on my night-stand on a Sunday evening. Monday morning, all I got when I tapped the power button was, well, nothing. Thought an app hung while in standby (not the first time) and killed the battery so I plugged it in. Got the phone-is-off battery charging screen (big animated charging battery), then held the power button on for a bit, got the pre-loader BLU logo but it never made it to the animated boot logo, it then rebooted to recovery mode after a while. So as I initially guessed, some partition table somewhere in the NAND flash got corrupted. In the end I determined that the "ANDROID"/system/OS partition was reporting as less than one third the size as it should be based on looking at scatter files included with various recovery ROM images.
Step 1 was to use spft and very manually readback the memory blocks which matched the various scatter files including the OS partition (MTKDroidTool calls it ANDROID when it generates a scatter file). Ignored the __NODL_ entries in the scatter files hoping it was one of these that contained the baseband information which tells the phone which region it thinks it's in. SPFT gets finicky if all of the blocks listed after loading a scatter file aren't linked to an image (happens automatically if they exist in the same folder as the loaded scatter file). Figured out I could just modify the scatter file and add __NODL_ to every item except the one I was trying to flash. (other variations worked). Flashed the TWRP recovery partition and then I had access to the adb debug interface which is not available in the stock recovery. Made TWRP backups for system, data, and cache then did adb pulls on /system and /data until I had everything I could back up. Then I started wiping cache and data partitions with TWRP. Phone still didn't boot. Finally flashed the wrong OS image from the d910i mentioned above. Still didn't boot. Then I flashed every partition active when loading that d910i scatter file. Phone booted to the OOBE (out of box experience)!!! Then I thought, I wonder if the OS block I read back from the phone before messing with it was any good, flashed that and it worked too. Tried to flash back all the pre-wipe NAND block reads I did on my phone and didn't work so I reverted back to the working state, ran the TWRP restore on the backups I'd made before wiping stuff, which left the OS non-bootable again, but then I sptf flashed (tool calls it "download") just the OS partition which I pulled from the phone manually (couldn't use the scatter file generated by MTKDroidTool... it was busted, based my start/stop on the scatter included in other valid rom/partition images), and poof, my phone was back to life, user data, wallpaper, everything.
You may be wondering why this is posted in this thread. Skipping over some details, now my phone about screen says the build is d910i, not d910a. No matter, the radios don't seem to care and it still connects to AT&T for voice and 3G data which gets back to the original question on this thread. Even if the OS version is reporting the wrong region, it may not matter. From experience with a Samsung GT-I5500, no amount of messing with the base band partitions will ever make the radios talk correctly in a different region, the hardware is different when they build the phone. I'm guessing that launching the d910i image modified something in one of the "hidden" partitions (which you don't want to touch if you can help it). I further speculate that if you did manage to flash over the partition containing the baseband info you would tank the phone's ability to work with any network but for now, it is just acceptably unsettling that mine just reports the wrong OS build but the phone works otherwise. It's likely that the d910i and d910a OS builds are identical and they key off of some other information to report the region variant.
In hind sight I wish I had just reflashed the OS partition I pulled from my phone because that's what seemed to fix the partition table. Probably could have saved a ton of trials and probably wouldn't have even had to restore any user data not to mention phone probably would have still thought it was a d910a.
Now the only question, is how long until it flakes out again? I suspect a critical section of the NAND is not what it used to be and will be more prone to failing again... after all, it is a low cost phone so the NAND was the stuff rejected by major brand suppliers (they cherry-pick flash chips but they pay for it). Fingers crossed it holds the partition table for a while... no idea where that info resides on this phone but did find the recovery logs which look like what MTKDroidTool looks at. Go ask an actual android developer I don't write code but have exceptional hardware debugging skills.
Hi, everyone! I'm new to this forum(so sorry if I post this in the wrong place), and I recently received an Cosmote Move(Alcatel OT-908 rebranded) from one of my friends. He said it belonged to his wife(she is a bit experienced in IT) but she bought herself a new phone so he gave me to find it a good use.
I turned the phone on, booted Android(after 5 minutes of showing me a blue, distorted and unrecognizable logo). The phone was slow, cluttered with tons of apps and almost unusable. I barely reached the settings, looked at the settings, and it had Android 2.2.3(the kernel & baseband info were empty). It was rooted and had custom recovery installed on it.
I wanted to install a new custom ROM on it, and as I am an CyanogenMod fan, looked for an unofficial CyanogenMod 7 ROM. After minutes of searching, I downloaded one from 4shared( big mistake, I know ), moved it to the SD card, and booted the recovery(CWM 5.0.2.8 - petite edition or something like that). I chose "Apply update from SD card" and selected the zip. It took 10 minutes to install, then something like this appeared: "CyanogenMod 7 LEWA", or something among those lines. I thought that was alright and I chose "Reboot system now". Then the phone was stuck in a boot loop, showing the distorted logo and rebooting again and again. The custom recovery combination(Power + Volume UP) didn't work anymore, so I couldn't do anything. I looked for some zips/images for fastbooting, but they didn't work or showed this: "Error: package has no android-info.txt or android-product.txt" so I gave up and searched the web for some tips, but none worked.
Has anyone here been into a similar situation and solved it? If yes, how?
Also, no BBCode, HTML or Markdown here on XDA?
I also forgot to tell you that the phone originally ran the stock Android 2.2 Froyo ROM and I tried to install CyanogenMod 7 (2.3 Gingerbread) on it, without installing the stock 2.3 first. That may be one of the reasons I can't do anything. I mean, it still turns on, but recovery is inaccessible and the ROM isn't working(distorted logo, then bootloop). Someone on AndroidForums told me to erase the kernel/boot partition and the recovery one and reflash them back. For the kernel I chose ChocolateKernel by cheqolada(Linux 2.6.32.9-pref for 2.2) and for the recovery I used an .img file that I found here on XDA. Unfortunately, it didn't work at all. But at least, instead of that distortion, now I get a white screen
Scatter files!?
New Update: I found an article deep here on XDA about a tool named SP FLASHTOOL by MediaTek(ARM arhitecture creator?) that can reflash the Alcatel OT-908, but it needs a scatter file. No idea what that is, but I'll do some research. In the meanwhile, if somebody has that file, please PM me or post it here.
Edit: I just looked up the term, and scatter files only work for MTK SoC phones, while the OT-908 has a Qualcomm one. Bad luck... :crying:
I am an idiot. On this phone, the recovery combination is Power+Home+Volume up, not Power+Vol up. I managed to flash a ROM from here and now everything is okay. I might make a tutorial on unbricking, ROMs and recovery once I can post links and stuff.
Hello, XDA forumites!
I've been lurking and reading a lot of threads in here for years, using all your knowledge to fix various phones. Today though is the day I first post and it is for good reason. I'm a guy who loves challenges but this one is making me go insane. I've spend the last two days looking for ways to fix this phone but NOTHING works.
So, the deal is that this phone turns on fine. It boots, it gets to the lockscreen and... it restarts itself. Again and again and again until the battery is removed. To fix it, I've tried the following:
- recovering/updating it through the Huawei official "firmware" supplied by the site: you put the file they supply on an SD card, inside a folder named "dload" and then hold vol up and down along with the power button to make the phone install the contents of that file, named UPDATE.APP. Needless to say it doesn't work. A menu appears with the options reboot system now, apply update from sdcard, apply update from cache, wipe/data factory reset, wipe cache partition and calibrate touch screen. Trying to apply update from sdcard only lets me browse the SD looking for the file but doesn't actually see the file itself, it just shows the dload folder empty (I've tried with 4 different versions of the file compatible with phones from Central America which is where I am ATM). Also, the factory reset does nothing (although it shows it wipes data), everything's there when I start the phone up.
- flashing it with SD Flash Tool: apparently partially works with the last version 3 of the tool (although nothing changes) while version 5 of SDFT doesn't even see the phone (drivers are correctly installed, adb detects it, more on this later). A problem that arises is that I can't flash the SEC_RO package on it (don't know why) nor the PRELOADER (not that one is supposed to normally, but I feel like it would fix my problem in this case).
- cleaning it in safe mode: booting it in safe mode made me notice that it was an app pretending to be Whatsapp causing the restarts (or, perhaps, the one that loads immediately after? The phone has several malware apps). In safe mode those apps didn't load so the phone stayed on. So I cleaned everything, activated USB debugging (for later use in adb mode) and restarted only to find everything as it was before I did the cleanup. I tried rooting it in safemode, cleaning again, still reverts to full "normality" after the restart. Same results when using the phone's proprietary SW HiSuite.
- installing CWM's recovery img through adb+fastboot: I installed all the possible - necessary or unnecessary - drivers (Google's, phone's official ones, PDANet ones) and the phone is correctly detected by the PC (visible in Device Manager) and is visible through the adb devices command. But as soon as I adb reboot bootloader it to fastload the CWM image, the phone stops being seen correctly and doesn't show up in fastboot devices, only showing "NEW: SAFE OLD:RISK" on a black background on its screen.
So, to recap: the phone restarts because of a malware at startup, reverts any and all changes made to it in safemode, doesn't wipe from the recovery menu, apparently has a corrupted bootloader and is impervious to normal flashing SW... Anyone got any more ideas on how to deal with it? The only option left that comes to mind is to fix it directly by flashing the internal memory using JTAG/RIFF but I don't have the equipment (nor do I intend to buy it).
Bump, hoping for some help...
One more bump, still stuck
First, don't get happy: I have no answer to your problem. Sorry. But I have a similar one. I was running a very efficient, rooted, stock ROM G730-U251, until I decided to switch from 'Ninjamorph Free' to 'Pro'. I've been made a lot of changes with Free version for a long time without any issues at all. Then, one day, when making a small, useless change with 'Pro', something went wrong; phone just rebooted and refused to get past bootanimation. With no custom recovery on hand, only solution for this is to flash ROM. Though I had no problem finding the official, stock UPDATE.APP, which flashed smoothly from the SD card to be fair. Mess came when, once flashed, I decided to install OTA update available, which I overlooked since phone was new. Big, BIG mistake. It just came with more restrictions than ever, letting me root, yes, but this time with 'Kingroot' only (as stock, I had no problem rooting with Framaroot) but soon discovered I wasn't able to use 'Super-Sume', 'Adaway' and 'Link2SD', because some system parts now CAN'T be mounted rw, even using ES File Explorer. To avoid any complication, decided to reflash UPDATE.APP just as I did before. No way I can do it this time. Don't know exactly why, but assuming it's not possible to update with a previous version of the 'same' ROM. So now I'm looking for a flashable stock ROM in order to try SP flash tool. Phone is in working state right now (not as yours), but I just don't feel comfortable with it as it is right now, because those apps are always the main reason why I actually root every single of my devices and simply because I like to have my stuff as my own way as possible. You know, truth is there's not much of an advanced support for this phone, not even here at XDA and I think that's because this is a Latin America version. We owners of G730-U251 devices are pretty much on our own, to say the least. Whatever, if the whole deal gets more complicated than it is, there's a strong possibility for me to end up getting rid of this phone. Sad. Really. It's actually a good phone. Though it WAS better...
Never flashed anything from Gitlab and IDK where I'm at with Flashing TWRP cause I have few tiny hard to read lines of text on the lower left of the unihertz boot logo.
It's detected in ADB and PowerShell Fastboot
https://unofficialtwrp.com/twrp-3-3-1-root-unihertz-titan/
https://www.androidweblog.com/unihertz-titan-root-install-twrp-recovery/
My question about this is do I merge the two folders together. (artifacts folder and unihertz titan master folder. )
https://gitlab.com/ubports/communit...-titan/unihertz-titan/-/blob/master/README.md
I've never even built anything so I'm just going to use it as is, but this type of flashing is new to me. Pulling files off a repo etc, I'm used to the old school download a zip from AFH and putting it on a sd card and flashing it in TWRP, prior to all this I rarely if not ever did very many ADB Cmd's let alone much flashing.
So I'm trying to see what else I need to do and where I went wrong with TWRP
Sidenote if I hold volume up on a fresh boot it just reboots to a black screen then powers back on again, sits at the black screen for 5 to 10 seconds.
I'm used to the old simple single click rooting and custom recovery then apply supersu.
The last device I flashed was a Note 4 Edge
So rooting via KitKat days vs Oreo days are different a few things have changed, not many single click autorooters, not much use of supersu anymore it's mostly all magisk
so I'm a little behind haha when I got the KeyOne and Key2 I became rusty.
TWRP only currently works on EMMC Titan. This is being worked on. There are instructions https://gitlab.com/HengYeDev/unihertz-titan here to get ubuntu touch on a ufs titan. However i have not been able to replicate the results, yet.
Good morning, everyone.
I have been frequenting this forum since the days when I had my trusty and beautiful HTC m8.
I find myself writing this post today looking for help: my uncle received from his friend a Doodgee x93 phone that was locked and whose unlock code he couldn't remember.
So I thought it would be simple, flash the ROM again so as to erase all the old data and reset the phone.
However, I found myself unable to do so.
After installing several versions of the drivers, in the various attempts, I used "SP_Flash_Tool_v5.1924_Win" with the only two firmwares available (any site always links to the exact same downloads) "Doogee_X93_MT6580_EEA_210902_10.zipper" and "DOOGEE-X93-Android10.0-20210902_user_20210902_R16.zipper".
The process stops at 2% without any error description.
In addition, the phone remains unusable, the screen does not turn on, and I cannot start recovery.
I then tried installing each file individually, and they all work except "super.img", which I assume are the android files given the weight of the 1.8Gb file.
Here I was able to turn it on, it did the boot android logo, then went to ">start fast boot.." but it never booted, surely because it couldn't find the rest of the files.
From the "MT6580_Android_scatter.txt" file, I tried editing the following.
"boundary_check: false" to true, but always to no avail.
I attach a screenshot and ask for your help, because I don't know how to proceed anymore, and all the online guides are the same copy/paste that don't work.
Thank you in advance
so you got a working phone and you bricked without doing research how to factory reset + reset FRP
Error: 3154 (S_DA_SDMMC_WRITE_FAILED) indicates flash storage wear-out.
you can however try another tool. do a full backup of all partitions first (especially partitions not included in stock ROM)
https://github.com/bkerler/mtkclient
I thank you for responding, I have downloaded and set up everything, as soon as I have a moment I will try to use the software you linked.
The phone worked, but it was locked as the owner, a friend of my uncle who gave it to him, had changed it long ago and could not remember the code to unlock it.
It was not a problem to reset it as he had already taken out his things before changing it.
However, I actually looked at several guides and followed every step, I didn't make anything up.
It had been several years since I had last done it, it seemed very similar to when using odin, and I went easy.
I can see in your screenshot you haven't unticked checkbox preloader. therefore I doubt you found the right tutorial. All it needs is formatting userdata and erase metadata + frp partitions.
https://www.hovatek.com/forum/thread-21638.html
some more information about Secure Boot Download Agents and why one must not flash in Format all + Download mode
https://www.hovatek.com/blog/so-whats-all-this-talk-about-meditek-secure-boot-and-da-files
similar thread
https://forum.xda-developers.com/t/frp-protection-on-doogee-s96-pro-who-has-tips.4418737
In the next few days I will have time to put in and try.
I have read the documentation, but I have a doubt: should I flash all *.img files, or just "super.img" which I failed with "SP Flash Tool"?
Or is there a command I haven't seen that automatically uses the "Android_scatter" file?
mtkclient don't use scatter file, it reads partition table on device. you can flash only super.img based on partition label.
Code:
python3 mtk w super super.img
Thanks for all the reply!
Im gonna watch all your link and in the next days let you know if it works! Meanwhile i wish you a good evening