So, here is the firmware flash guide for B15Q. It assumes either a Win7 x86 machine or a x64 with driver signature verification disabled (but Win8/8.1 in any variant or W7x64 is NOT RECOMMENDED). I assume no warranty for bricked devices, especially not if you manage to kill your PRELOADER or DSPBL. Double and triple check before downloading. 0) Driver and toolkit setup.
Get the driver set, scatter file and spFlashTool from this thread:. Remove back shell from phone, remove battery (!).
Attach phone via USB. Windows should now, approx. Once every 2-3s, make a sound similar as if you put in a USB stick and then pull it out again. Start=Run=devmgmt.msc, in the View menu choose 'Devices by connection'. Click yourself through the tree until you find an unknown device (MT65xx Preloader or similar). Rightclick on the device and press 'Install drivers'; you shall find the drivers in 'MTKUsbAll0.9.2 New inst.
Win 7&8x64' folder. Launch 'SP Flash Tool v5.1352.01 flashtool.exe'. In the tab 'Download', click on the 'Scatter loading' button and select the downloaded file 'MT6582Androidscatter.txt'. SpFlashTool usually remembers this across restarts. Unplug the phone at the computer side if you want to work with it later (the MicroUSB ports don't like too many inserts, they wear out physically). A) ReadBack for backup of existing firmware/userdata This will involve a.load of typing for the first readback.
Open the scatterfile using Notepad or any editor capable of handling UNIX line endings, NOT notepad. You will see a lot of blocks like. Code: - partitionindex: SYS0 partitionname: PRELOADER filename: preloader.bin isdownload: true type: SV5BLBIN linearstartaddr: 0x0 physicalstartaddr: 0x0 partitionsize: 0xC00000 region: EMMCBOOT1 storage: HWSTORAGEEMMC boundarycheck: true isreserved: false operationtype: BOOTLOADERS reserve: 0x00. In spFlashTool, select the 'Readback' tab. For all the blocks you see in the scatterfile (IDs 0-23), repeat the following:.
Click 'Add'. Double-click on the newly appeared row. Choose a filename (e.g. Preloader.bin for the first block; some blocks will have name = NONE, use the partitionname here for the filename) and click SAVE. A window 'Readback block start address' will appear.
Choose Type = 'hex'. Copy (Ctrl+C,Ctrl+V, and take care to exactly select the hex value! Do NOT type the hex values by hand!) the value from linearstartaddress (with the 0x) into the 'Start address' box and the partitionsize value in the 'Length' box, press OK. Unless you are at the SYS23 partition BMTPOOL, proceed to the next block, repeat from above. The SYS23 partition can not be backed up, because it has invalid lengths. Do not enter it into spFlashTool.
Cat B15 Phone
CHECK THE VALUES FOR START ADDRESS AND LENGTH IN THE TABLE. CHECK THEM ANOTHER TIME. Press 'Read back' button at the top.
Plug in the phone with the battery removed(!) and wait. This process will take time and consume approx. 3-4GB of disk space.
Archive the files you created somewhere safe. Do NOT distribute anything to other people except the BOOTIMG, RECOVERY and ANDROID partitions, because the other partitions contain data that is hardcoded to your board (e.g. IMEI/MAC addresses, sensor calibrations.) or your private data and app data (SYS22/USRDATA). If you want a full backup to disassemble by hand lateron (aka you trust in nothing going wrong and don't want to do the hard work except when you need it), just create one readback section with start=0x0 and length=0xE5720000 - this backups everything in one file. B) Download for flashing new firmware. In spFlashTool, select the 'Download' tab. In the dropdown box below the scatter file, keep it at 'Download only' or set it if this is not the case.
Uncheck all the boxes in the table. Double click on the 'Location' column of the BOOTIMG, RECOVERY, ANDROID or USRDATA rows which you want to flash, select the appropriate image file. Check that you selected the correct images for the correct partitions!. CHECK THAT ONLY THE ROWS WHICH YOU WANT TO FLASH ARE CHECKED. ESPECIALLY, NEVER EVER CHECK THE PRELOADER, MBR AND EBR PARTITIONS.
YOU HAVE BEEN WARNED. Press Download.
Plug in the phone with the battery removed and wait. SpFlashTool will tell you when it's done. Unplug phone from computer (!) and put in the battery. If you get an error 'PMT changed for the ROM; it must be downloaded', reboot your machine.
When you have a running ROM on it, you may also try to keep the battery in the phone during flashing; just press Download on the PC, then select Shutdown in the Android menu that appears after holding Power pressed. Once the phone has shut down, it will vibrate shortly and then be detected by spFlashTool.
I also recommend using a high-quality USB cable and not a worn out one because USB cables with worn out plugs may lead to issues during transmission. Excellent stuff you wrote here - thank you. Any hints on how to resurrect dead B15Q that has damaged/erased NAND or a Preloader? In this link http: // forum. Com/ showthread.php?t=1943442 a forum member claims that mt65xx have META mode even if they appear dead - like mine B15Q is right now - and could be revived with SPFT and proper W7 drivers. Does under those circumstances PRELOADER might be reflashed?
I read just afterwards that one should not do fully ticked Memory Test as it silently reformats NAND. I guess this is what happened in my case.
Also, a reason to do this test was that reflashing the phone with 1.010 BOOTIMG, ANDROID and RECOVERY, having it back for a brief moment and then upgrading it via OTA to 1.019 that had bricked it in a reboot loop. Any clue would be welcome. Quote: Originally Posted by uhuru-meditation Excellent stuff you wrote here - thank you.
Any hints on how to resurrect dead B15Q that has damaged/erased NAND or a Preloader? In this link http: // forum. Com/ showthread.php?t=1943442 a forum member claims that mt65xx have META mode even if they appear dead - like mine B15Q is right now - and could be revived with SPFT and proper W7 drivers. Does under those circumstances PRELOADER might be reflashed? I read just afterwards that one should not do fully ticked Memory Test as it silently reformats NAND.
I guess this is what happened in my case. Also, a reason to do this test was that reflashing the phone with 1.010 BOOTIMG, ANDROID and RECOVERY, having it back for a brief moment and then upgrading it via OTA to 1.019 that had bricked it in a reboot loop. Any clue would be welcome. It is all OK now and B15Q is alive and works well, as it did before the 'big brick' Christmas blackout.
The main thing is that thanks to MTK low-level USB communication on chipset as is in B15Q makes it 'unbrickable', really. The other thing is my bad clicking around and 'checking memory' while not really knowing what I am doing. As well as Windows x64 drivers, admin rights and all the other voodoo lurking in there. What troubles me more is how come that CAT ppl. Allowed 'bricking' device upon system update, while root or no root shouldn't really matter there? Software receiver tanaka hd. They sell it unlocked, so they should sell it, as well, with an easy option to root it.
As Nexus One from Google had this 'build-in' option. I still hope that future updates will not have the same behaviour and also that there will be an alternate option for some other flavour of Android. Quote: Originally Posted by uhuru-meditation It is all OK now and B15Q is alive and works well, as it did before the 'big brick' Christmas blackout.
The main thing is that thanks to MTK low-level USB communication on chipset as is in B15Q makes it 'unbrickable', really. The other thing is my bad clicking around and 'checking memory' while not really knowing what I am doing. As well as Windows x64 drivers, admin rights and all the other voodoo lurking in there. What troubles me more is how come that CAT ppl. Allowed 'bricking' device upon system update, while root or no root shouldn't really matter there?
They sell it unlocked, so they should sell it, as well, with an easy option to root it. As Nexus One from Google had this 'build-in' option. I still hope that future updates will not have the same behaviour and also that there will be an alternate option for some other flavour of Android.
Hello, I tried your workaround but haven't succeeded yet. And yes my phone also is bricked, unfortunately. My phone halts where you have to choose a language after a factory reset. At that moment I get some messages that some services had stopped. Like Google keyboard, Youtube and some more. I can click OK but this doesn't get me passed these messages and they reappear. I only can switch off the phone.
I tried your workaround on a x64 machine (and got the PMT message) because that's what I have. I am preparing a x86 machine which has XP on it but on launching SP Flash Tools I get the message the configuration of the computer is not correct. Will W7 32-bits do the trick? Also two more questions. The downloaded images are: boot.img, recovery.img, system.img and uboot.img. In your explanation you're mentioning: BOOTIMG, RECOVERY, ANDROID or USRDATA. I presume that in SP Flash Tool I have to use the system.img in the row ANDROID?
Or should it be in the row USRDATA? You don't use uboot.img. What's the reason for that? For what purpose is this image? Update 19 april 2015. I managed bringing back my phone to life. I did another attempt by rebooting my 64-bits computer (as you wrote in the beginning) because at that moment I didn't had a 32-bits machine.
It worked wonderwell. So, I'm using my phone again.
Like uhuru-meditation I give up rooting for the moment. Nevertheless Android 4.4.2 I still like this phone. Hope it won't let me down after this major reset. Keep fingers crossed. Harddiskwp many thanks for your hard working in making this workaround.
It sure has cost you more then an hour's work. I hope you read my questions and can or will answer them. Hi guys, i'm sorry i have to ask this in this forum but i've been asking for a couple of months now, and got no answer.
I have a CAT B15 (not the B15Q). It is single sim version (IMEI write on the back) and i managed to do plenty of things in it. I swapped memory and worked fine, and even i installed a Dual Sim android rom and i managed to use the secondary Sim bay in it (that was tapped with a plastic fake sim) and used the phone with 2 sims for like 2 weeks.
Then i started to play with deodex and build.prop and softbricked the phone, but it was piece of cake since it is easy to unbrick. The problem was that i wrongly flashed the phone with scatter file, and flashed all partitions in it, EBR1, MBR, UBOOT, etc, etc. The result was a non-working dual SIM phone. Everything works, but the SIMS, it does not detect any SIMs in it, in any of the SIM bays, and the IMEIs are wrong numbered. I did no buckup of the phone so i'm pretty screwed.
I've been asking for someone to upload the EMEASS or USSS ROM for the CAT B15, but nobody responded. I thaught maybe the CAT B15Q has a similar software/bands flashing partitions, but that i leave to you for answer. Anyway, if any of you has the possibility of taking the images of a single sim CAT B15 it would save me this awesome phone for me. I'm also willing to give a 20GB account of ownCloud server for 1-year free of charge if storage space is needed, no problem. This are the links i've been searching and asking.
All About CAT B15: Root for Catterpillar B15: Best regards. Good day I have the same questions as a previous user, but I cannot find any answer to it: 'Also two more questions.
The downloaded images are: boot.img, recovery.img, system.img and uboot.img. In your explanation you're mentioning: BOOTIMG, RECOVERY, ANDROID or USRDATA. I presume that in SP Flash Tool I have to use the system.img in the row ANDROID? Or should it be in the row USRDATA? You don't use uboot.img. What's the reason for that?
For what purpose is this image?' Could you please help with these? Should I use uboot.img as well? And does system.img go to the Android row? I added this 3d question later: is it safe to flash SS phone with the DS file?
Kind regards. Quote: Originally Posted by harddiskwp 0) Driver and toolkit setup. Get the driver set, scatter file and spFlashTool from this thread:. Remove back shell from phone, remove battery (!). Attach phone via USB.
Windows should now, approx. Once every 2-3s, make a sound similar as if you put in a USB stick and then pull it out again. Start=Run=devmgmt.msc, in the View menu choose 'Devices by connection'. Click yourself through the tree until you find an unknown device (MT65xx Preloader or similar).
Rightclick on the device and press 'Install drivers'; you shall find the drivers in 'MTKUsbAll0.9.2 New inst. Win 7&8x64' folder. Launch 'SP Flash Tool v5.1352.01 flashtool.exe'. If you get an error 'PMT changed for the ROM; it must be downloaded', reboot your machine.
Welcome to the GSM-Forum forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. Only registered members may post questions, contact other members or search our database of over 8 million posts. Registration is fast, simple and absolutely free so please -! If you have any problems with the registration process or your account login, please contact. Firmware for Caterpillar CAT B15?
User Name Remember Me?
ANDROID secret codes.#06# - IMEI number IMEI (International Mobile Equipment Identity). The IMEI or MEID number for CAT B15 mobile phone acts as a unique identifier for that device. No two devices will have the same IMEI or MEID, which makes it a very useful tool for tracking lost or stolen cell phones.#.#273282.255.663282.#.#. Immediate backup of all media files.#.#4636#.#.
This code can be used to get some interesting information about CAT B15 and battery. It shows following 4 menus on screen:. Phone information.
Battery information. Battery history. Usage statistics.#.#7780#.#. This code can be used for a factory data reset.
It'll remove following things:. Google account settings stored in your phone. System and application data and settings. Downloaded applications It'll NOT remove:.
Current system software and bundled applications. SD card files e.g. Photos, music files, etc. PS: Once you give this code, you get a prompt screen asking you to click on 'Reset phone' button.
So you get a chance to cancel your operation.2767.3855# - Think before you give this code. This code is used for factory format. It'll remove all files and settings including the internal memory storage. It'll also reinstall the phone firmware. PS: Once you give this code, there is no way to cancel the operation unless you remove the battery from the phone.
So think twice before giving this code.#.#34971539#.#. This code is used to get information about phone camera. It shows following 4 menus:. Update camera firmware in image (Don't try this option). Update camera firmware in SD card.
Get camera firmware version in CAT B15. Get firmware update count WARNING: Never use the first option otherwise your phone camera will stop working and you'll need to take CAT B15 to service center to reinstall camera firmware.#.#7594#.#. This one is favorite one. This code can be used to change the 'End Call / Power' button action in your phone. Be default, if you long press the button, it shows a screen asking you to select any option from Silent mode, Airplane mode and Power off.
You can change this action using this code. You can enable direct power off on this button so you don't need to waste your time in selecting the option.#.#225#.#.
Try to make a detail line based, with an array (instanced) thats overrided by the default lenght. Pat files for revit. Sadly, I couldn't find a ridig insulation pattern in there either probably because it is impossible to be made as a pattern. Any ideas how to work around that? I know that I can always do it as a detail component as a zig zag line, but would really like to have it as pattern as well since sometimes my insulation, at roofs for example, would be wedge cut. This user is offline Mon, Nov 7, 2011 at 3:28:29 PM| Pattern (.PAT) Files #4 active Joined: Tue, Jul 14, 2009 273 Posts Ah.
Shoppers. Events calendar.#.#426#.#. Debug information for Google Play service. Google Play Services is a proprietary background service and API package for Android devices. When first introduced in 2012, it provided simple access to the Google+ APIs and OAuth 2.0, but has since then expanded to cover a large variety of Google's services, allowing applications to easily communicate with the services through common means, being internally referred to as simply GMS.
As of January, 2014, it has been downloaded more then one billion times on Android devices.#.#759#.#. Access Google Partner setup (Rlz debug interface).#872564# - USB logging control.#9900# - System dump mode CAT B15.#.#97#.#. Language and Keyboard settings in CAT B15.#.#46.#.# - Reset Sim in CAT B15.#301279# - HSDPA HSDPA means “High Speed Downlink Packet Access” and is a technique used in the UMTS mobile communication system, the download speeds of currently 3.6 Mbit/s to 7.2 Mbit/s. HSUPA is developed commercially since 2007 in Germany.
High Speed Downlink Packet Access (HSDPA, 3.5G, 3G + or UMTS broadband) is a data transmission method of the cellular standards UMTS, which was defined by the 3rd Generation Partnership Project. The method enables DSL-like data rates in mobile networks. HSDPA is available in Germany, among others by the network operators Vodafone, E-Plus, O2, and telecom and in Switzerland by Swisscom, Sunrise and Orange. In Austria operate the A1, T-Mobile, Orange and Three HSDPA networks./HSUPA HSUPA means “High Speed Uplink Packet Access” and is a technique used in the UMTS mobile communication system, the upload speeds up to 5.8 Mbit/s. High Speed Uplink Packet Access (HSUPA) is a transmission method of the UMTS mobile radio standard that allows higher data rates in the uplink and reduces the round trip time (often referred to as ping). HSUPA Category 6 were up to 5.76 Mbit / s and category 9 (Release 9) up to 23 Mbit / s can be achieved. HSUPA is part of Release 9 of UMTS.