Hello-
I bricked my phone, so I am trying to re-flash it.
I've obtained the ROM package, but it contains many more files than I'm used to seeing when flashing a ROM. I've had minimal luck so far, for example, I erased the recovery partition with Fastboot, and then I reflashed it with the recovery.img I found in the package, and it works great.
The main problem I'm running into is for some of the partitions, there are multiple image files. For example, although recovery.img was just one file, I see multiple system partition files, such as system.img (1kb), system_1.img (134mb), system_2.img (8.2kb), ... up to system_16.img.
userdata, cache, are similar.
There is no splatter file.
There also seem to be many meta files, such as partition.xml, patch.xml, rawprogram0.xml, definition_public.xml.
From research so far, some Qualcomm QPST app for Windows is the only way to re-flash this, but I'm on Linux, so I wanted to know if there is a Linux / Fastboot way to do it, and/or if this QPST app is the definitive solution to the problem.
Any feedback would be great, BLU says this is out of warranty and they offered me $10 for it towards a swap for another BLU phone, so I'm really hoping I can restore it.
Thanks,
Dutch
Related
Hello,
The home button of my device (Magic) does not work at all. So, I can not confirm to install the CyanogenMod in the recovery screen.
Am I able to install the ROM via fastboot? or does anybody has another suggestion?
Regards,
Omer
Yes, you can flash ROMs via fastboot, but you'll need a system and data img for the ROM, and I'm not aware of a method to package them up based on an update.zip.
I checked inside the archive and saw the images but there also some scripts need to run. That's why; I couldn't dare to flash.
Is there a method I can follow?
osaatcioglu said:
I checked inside the archive and saw the images but there also some scripts need to run. That's why; I couldn't dare to flash.
Is there a method I can follow?
Click to expand...
Click to collapse
You don't need any scripts, just a system and data to flash.
fastboot flash data.img
fastboot flash system.img
You wont find these images inside the update.zip, the sys/data-imgs need to be created from the sys/data folders. Best bet is to ask someone to perform a nandroid backup, backup the imgs, wipe, flash cyan, send you those imgs, restore their old imgs.
Thank you. But, the someone's device should be identical to magic, right? I have dream also. So, I can use the nandroid backups of it. However; I don't think this would be possible. what do you think?
osaatcioglu said:
Thank you. But, the someone's device should be identical to magic, right? I have dream also. So, I can use the nandroid backups of it. However; I don't think this would be possible. what do you think?
Click to expand...
Click to collapse
I'm really not sure, but I think the device would need to have the same size data and system partitions as the Magic, which the Dream doesn't.
Use mkyaffs2 to make the System and Data .img Files
What operating system do you have because if you have linux or a linux virtual machine you could extract the update zip and use the mkyaffs2 utility code.google.com/p/yaffs2utils/ to make the system and data images.
There is also a much easier program called yaffey http://forum.xda-developers.com/showthread.php?t=1645412 but it is windows only
So this thread is kind of old, but I stumbled upon it looking for stuff.
Im using a google galaxy nexus and have a strange issue where I cant connect it via usb when in a different state than fastboot mode. I replaced the usb port (flex cable) already, but it doesnt help (if you got any advice on that, please tell me)
What I actually want to say is that I can't install cyanogen from recovery because I can't connect my phone when in recovery, but I can flash firmware normally via bootloader, I tried that already, so how exactly do I get the images for cyanogen? Because I don't fully grasp it yet.
I wonder whether there is help for someone who thought he knew how to flash a kernel but apparently is deluded. I have the original nexus seven Wi-Fi tablet android version 4.3 build number JWR66V. The system still wants to update me to 4.3 because I ripped some files out of the cache directory to prevent OTA updates. I have both fastboot and adb. I have read the stickies about flashing.
The phone is rooted and the bootloader is unlocked. I use TWRP custom recovery, and it's a good thing, because I solidly bricked myself up just trying to get my lollipop. I know there are tools to root a nexus seven even with stock lollipop, so I thought I'd upgrade my phone to stock lollipop and then use one of those methods. I tried both the stock lollipop kernel and the one provided by chain fire, which I understand is rooted already. (I'm assuming upgrading to lollipop will lose me my root, unless I want to recover back to 4.3.)
I tried to do these things a couple of different ways. When I tried fast boot, I got the message "error: neither -p product specified nor ANDROID_PRODUCT_OUT set". There was a YouTube video suggesting how to deal with this error message. I'm pretty sure I followed the instructions but no go. (I was using the "flash all" command.) This was after I had put the file containing lollipop in the directory, both zipped and unzipped (so that I had an .img file instead of a zip file). I tried using both the zip file with all of the lollipop partitions and the system image file individually. No go. I also had a message that android-info.txt could not be found, even though it was in the same, working directory.
I could be wrong but I don't think you can install a complete updated kernel from a file on the device. I think that works only with update.zip.
I'm still thinking fastboot is my best bet, but there are dependencies apparently and I don't know what files to include in its directory. Then, am I wise to go to stock and then root, or should I simply flash the stock kernel already rooted? I assume that's what chainfire is providing, correct?
I notice the lollipop official ROM nor Chainfire’s supposedly-rooted image have any file named nakasi. I have only .img files, no .zip files.
I found a dozen sets of instructions on how to flash a kernel but something I need is missing from all of them. Does anyone know what it is or can anyone offer some helpful advice?
Thank you,
Leon M.
I found this guide on how to flash .mbn files on Qualcomm devices like X800,X900 etc... http://mytabletguru.com/how-to-flash-qualcomm-cpu/
The exact cause of hard bricking after flashing a chinese ROM is still unknown but i can assure you they're related to the one or more .mbn files included in those ROMs, unfortunately just taking them out won't make it possible to install the updates.
You'd still need to modify the kernel and boot.img in order to make it boot and still most things wouldn't work(current state of my cm13 rom), we would need to reverse engineer those incompatible files to get everything working or wait for the official update(which will never come). But i'll make a thread about reverse engineering .mbn files later.
Now, consider you have a bricked phone;
Basically here, you'd need an extracted image of the official update for X800 US(like the one included here) which include a lot of .mbn files and modem binaries.
Flash them all with the method above.
Then you should be able to boot into fastboot, after that you can flash recovery and either restore a backup or wipe data/cache to flash a new rom. This way you can keep your external storage(virtual sdcard) which wouldn't be the case with previous methods.
Theoretically it should work, if any of you have a bricked phone, wanna try it out but isn't sure how to do it, just post your question below and i'll try to help as soon as possible
Hi, first post here so please be kind - I really need your help.
SITUATION:
I unlocked the bootloader using the tool provided under the utilities section of ASUS support page. Then, I successfully rooted my phone using one of many exploits contained in KingoRoot. Root Checker app said that root was ok, and I rebooted my phone. Something in the process caused my phone to soft brick, probably KingoRoot messed up the partition table. My phone is now stuck at Asus logo when trying to turn it on.
I can access recovery and fastboot. I also flashed TWRP recovery 2.8.5.0 (no success flashing newer versions) that is capable to put my phone in ADB sideload. I wiped cache, dalvik, data multiple times. Factory reset. Tried to update system using almost every firmware zip that ASUS support page lists (WW) through recovery and through ADB sideload unsuccessfully. Stock recovery is unable to access my SD card (since after the fatal reboot - unable to mount E: ecc, I tried three different cards), while the custom one is able to but gives me error when trying to run zip files. There are a plenty of details that I could give, but my conclusion after 24 hours of forum headaches is that the partition table is messed up.
I came across an utility called Asus Flash Tool that may fix my problem, but it only accepts .raw firmware files and I am unable to find one for my A500KL. There's a folder for it in an old rapidgator link but it's empty now, no luck contacting the original uploader (many others have the same problem). I read through every related thread here on XDA and on many other forums (even in Chinese and Russian), this is my last resort. There's anyone willing to share such .raw image? I read that it can be built out of a functional phone, can someone help me?
Any help for my Nova plus ( MLA-L03) bricked,
Im with a bricked unit (nova plus MLA-L03) . i cant find on all web page firmware Any help for restore my phone pls .
I will detail here what happened to my own bricked Nova plus (MLA-L03) and how I got it working again, with the help of a lot of comments from this forum. First you should know that when asking such questions it is advisable to detail your problem and what led to it, so that others are willing to help without having to ask for additional details.
I got soft-bricked after installing twrp and formatting the /data partition (wrongly thinking it was only userdata and that nothing could go wrong) so I could then backup the partition for future use. Basically what unbricked was flashing these 3 partitions from a full firmware release: /recovery, /boot and /system and I believe this is the only thing required, so you may try that first. I am not an expert and I would also like to know if the other steps may have contributed to the unbricking.
-Through TWRP I restored the stock recovery and the /data files from Bluesmoothie's backup (look in the TWRP folder, also you might have to create a backup yourself to generate the correct file structure), but that didn't unbrick
https://forum.xda-developers.com/showpost.php?p=70197735&postcount=99
-Then I found files for my device (MLA-L03) from the Huawei Firmware finder available here:
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
-You can also find the firmware from this site but it is a hassle to search through everything:
http://hwmt.ru/oth/HWFF/info/view.php
-I downloaded the firmware called MLA-L03C6540B300CUSTC654D001 (the update.app file inside the .zip is actually 3.8GB and my understanding is it is a full OS, not merely an update)
IMPORTANT: using this firmware will install android 7 nougat and you may not be able to go back to android 6. Also as of this date you will not be able to use TWRP to backup you data partition and others, and I think that you cannot modify the system partition also (not sure, I would love to be wrong)
-(Not sure if it is worth mentioning but I tried to unzip the update.zip and put it in my sd card in a folder called /dload and boot by pressing all 3 buttons (boot to stock recovery) but the update got stuck, wouldn't go over 36%... I had also previously tried this with other zip packages for my device but none of them got over 12% or 30%)
-Then I used the Huawei Update Extractor (link right below to extract recovery.img, boot.img , and system.img from the update.app file extracted from update.zip.
https://forum.xda-developers.com/showthread.php?t=2433454
-Finally I flashed these 3 files with fastboot :
fastboot flash recovery "[filepath to recovery.img]" ( example: fastboot flash recovery "C:/my documents/recovery.img" )
fastboot flash boot "[filepath to boot.img]"
fastboot flash system "[filepath to system.img]"
-After I also did a factory reset, but I don't remember if I let the system boot completely before (I don't know either if it makes a difference... I hope someone here can answer)
Good luck!
Hi friends. I have the device MLA-AL10. i Want to change the region. Could you share your oeminfo file?
stas30 said:
Hi friends. I have the device MLA-AL10. i Want to change the region. Could you share your oeminfo file?
Click to expand...
Click to collapse
don't even try to change oeminfo, it will brick your phone network security
changing region on qualcomm devices is not easy, its complicated thing and involved paid tools
its better to see a professional to do this :good: