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
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 can't post in the development forums so I figured I would ask here:
I understand how to use adb and fastboot, etc.. What I am missing is with the new ICS ROM it states that I must "fastboot flash system system.img"; however none of the ICS zip file I have seen come with a system.img file (just the boot.img).
Am I missing something? Any help would be greatly appreciated..
I used the version available on Rootzwiki... not sure if thats the answer you wanted. I'm running 4.0.3 ICS on my wifi XOOM OC to 1.54. No FC's, reboots or anything of the sort. You'll need to be sure that you have su-install.zip, and other img files needed. As I said, you'll find them all on the rootzwiki website under xoom hope this helps, if not good luck.
You are talking about two different things here. I don't know where to start here you're all mixed up. There are several ways to flash a ROM, you can fastboot flash the .img files such as what you are referencing to. Or you can flash an update .zip file from recovery. The way you flash the ROM depends on the source, if its a bunch of *.img files you use fastboot, if it's a *.zip file you use recovery. Just follow the directions given for installation that are provided with the ROM you are downloading.
sboehler said:
I can't post in the development forums so I figured I would ask here:
I understand how to use adb and fastboot, etc.. What I am missing is with the new ICS ROM it states that I must "fastboot flash system system.img"; however none of the ICS zip file I have seen come with a system.img file (just the boot.img).
Am I missing something? Any help would be greatly appreciated..
Click to expand...
Click to collapse
Hello, and welcome to XDA! =] Anyways on with your question. There are two ways to flash a ROM to your xoom. One being fastboot/adb, where you use the command line on your computer to send commands to your device and make it do stuff. This is where you use system.img, boot.img, recovery.img.
The second, is CWM (ClockWorkMod recovery) This, as far as im aware, is the most common way. This is where the .zip's come in. Because you take the .zip you put it on your external SD card. boot into recovery (after flashing CWM of course) and flash the rom. CWM is nice because you can also make a 100% snapshot of your internal memory state via making a nanodroid back up. That way if anything messes up you have a 100% backup you can restore at anytime if you need it.
In a nutshell, You use *.img files with fastboot and .zip files with CWM.
Anyways. If you're new to rooting. Please check out these two threads, They'll help you get started. =]
Xoom Heaven: Root+Non Root Users Are Welcome!
[Guide] Setting up and using adb/fastboot-unlock, flash custom recovery & root
The second guide I did use to flash my own zoom so I can assure you it does work.
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.
Does anyone have or know where to get a stock recovery image for the BTV-W09?
When I flashed the US "003" update manually through the dload folder method, my TWRP was replaced by the stock recovery. I have left it there, and since flashed TWRP to recovery2. The update failed, but I ended up with stock recovery and the tablet no longer rooted. I would try that first. If that doesn't work for you and if you are on the US version "002" firmware let me know and I should be able to send you a backup of my recovery partition bit if you need the eRecovery from the recovery2 partition, I will be unable to help you.
I am on the US version “003”, I updated before flashing TWRP and rooting. TWRP was flashed recovery not recovery2. No worries though, Im sure someone will post a recovery as rooted people will be needing to flash OTA updates soon.
If you are on "003", try updating the unzipped "Update.Zip" from the dload file. I found a copy of the update.zip on my internal SD in directory called HwOUC. If you can't find it, I still have my file. The Update will most likely fail, but that should give you the standard recovery back. then I suggest you flash TWRP to Recovery2. TWRP actually is easier to access from Recovery2 becuase all you have to do is hold the volume up key down for a few seconds from the unlocked bootloader screen to boot into TWRP. Once you have TWRP re-installed you can then just flash the super user zip file to regain your root.
I am not sure if it is because I now have unlocked the bootloader, have recovery2 with TWRP or updated the file to enable the 5Ghz modem , but even with having the standard recovery partition back my system did not pass the altered system check and allow me to flash the OTA. I am not quite experienced enough to try and use Flashfire to force the update, since there is a warning about Huawei devices being easy to hard brick. Hopefully someone who has updated and then rooted will post an .img file of the updated system partition so it can be flashed with TWRP (at least I think that is what those of us who have already rooted will need to do).
I looked for the update.zip but it doesn’t exist anywhere. These updates are usually removed after the update completes successfully. Plus I’ve done a factory reset since updating, which may have deleted it. I wanted to see if enabling the 5GHz radio would stick after the reset (it did). The 5GHz radio hack was really my only reason to root. I didn’t alter my system partition with TWRP, so I may still be able to take an OTA update if I had the factory recovery. Ive stopped rooting all of my non Nexus devices. Since Google releases almost monthly security updates which usually unroots anyway it’s just too much hassle to keep root. If you want to post the update.zip somewhere I could give it a try, if not that’s cool. Im sure a factory image will be available at some point.
I have posted the Update.zip file to the following location:
http://www.mediafire.com/file/ug1pe2w38ddkxm9/update.zip
Let me know how things go.
Coming from a Nexus 7 I'm use to many of the img files you flash for restoring.
Using update extractor I now see many of those files (003 update) and some I have no idea about or how to flash them.
BOOT.img - OK
CRC.img - ?
CURVER.img - ?
EFI.img - I know what EFI is just never flashed it on an Android device.
FASTBOOT - OK
FW_HIFI.img - ?
FW_LPM3.img - ?
RECOVERY.img - OK
SENSORHUB.img - ?
SHA256RSA.img - No what it is normally but never flashed.
TEEOS.img - ?
TRUSTFIRMWARE.img - Interesting, but have no idea. - ?
VERLIST.img - ?
XLOADER.img - ?
Like many of us I'm in the same boat. Unlocked, Flashed recovery and rooted and cannot install update 003.
I've flashed the recovery.img from update 03. I've done a factory reset a few times. Odd enough it maintains 5Ghz wifi after doing a reset. I'm stumped and not sure of so many of the other .img files. Might one of them help me get the update to pass if I flash it. That or we wait for a full release and not an OTA to grab all the files we need. Really think I need system.img to make it work but the update doesn't include it.
Thanks johe for providing the 003 update.zip. I may try flashing the recovery.img this weekend. Ill let you know how it goes.
Jmjm003, I believe the issue with updating with the OTA is due to changes detected in the system partition after rooting/unlocking. Im not sure of a way around this other than flashing the full system partition, and we don’t have the factory ROM available yet. Im also new to Huawei devices and their partition structure so hopefully the development community will grow around this device and provide better solutions. I also can confirm the 5GHz stayed enabled after a factory reset, the question remains would it hold after an OTA update.
Attempting to root a ONN device that hasn't gotten a guide posted for it might be a bit of a pain if your a beginner.
Rooting might require you to make your own scatter file using wwrMTK and dump the files from your device yourself using SP Flash Tool which might be a bit hard for beginners to understand how to do so.
Flashing images (.img) from untrusted sources.
Other people's images or images from untrusted sites could contain malicious modifications to the image that could harm or brick your device so be careful and make you trust the site or person that uploaded the image file.
The risk of installing malicious software.
Most of the software like SP Flash Tool or wwrMTK mostly don't have a official source to get them so you risk installing tempered or malicious versions of the software which may harm your device or the device running the software.
TWRP or a custom rom might not be available.
Unofficial builds can take some time to make and build so they might not be available for your device model as of yet so if you just want to install TWRP or a custom rom onto your device it might not be available so check your device model and check if there's a build for it on this forum.
Rooting isn't as simple as getting the official firmware files.
If you want to use the Magisk method you have keep note that there is no site to download the firmware files officially also it's not on ONN's official website so the firmware can be modified so it's best to get your own firmware files straight from your device to patch with Magisk.