Hi, I haven't been lazy I have searched for ages, & Unless I missed it I haven't found information on the misc1-2.img file that has to be flashed, I'm curious as to what it is and what it actually does. I know during the rooting process it replaces the original misc file, some guides I have read tell you to backup the original misc file then reflash it back, other guides don't even mention backup and reflash.
I did backup my misc file but I didn't flash back the backup. My phone is rooted and doesn't seam to have any problems.
any Info would be great, thanks
I think this file allows HBOOT downgrade.
Related
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.
Hi,
I don't know if this is the correct section to get this question answered, but I'll try:
I have a new tablet, which is not really known at the moment. I managed to root it and next step would be to port Clockworkmod Recovery to it. Since I only found guides where I always have to repo sync the entire CyanogenMod github (which is 19GB+ as I heard), I searched for an alternative where I could save some traffic
I found a clockworkmod recovery from another tablet and wondered if it was just possible to unpack it, modify the recovery.fstab and repack it again.
Is this possible or do I have to modify more than the recovery.fstab? If yes, could you point me to the right direction?
Regards
dump your stock recovery
unpack the stock recovery and save the vold.fstab somewhere.
upload the stock recovery here
http://builder.clockworkmod.com/
get the output and flash`it
if the key`s are not working, unpack the new cwm, and the old recovery, and put the keys from the old recovery.
if you get some mount points erros, you will have to upload also the saved vold.fstab on the clockwork site when you cook the image.
if this does not offer you a good result, you will need to find a similar device (processor, resolution) that has allready a cwm, and try it
the recovery file is ramdisk/sbin/recovery
Hi,
thanks for showing me a way. Unfortunately builder.clockworkmod.com says it didn't find Android magic. This makes sense, as the image is a uImage with lzma compressed data inside. It seems koush's builder handles only "plain" recoveries...
Bad luck
I guess I'll try your second advice and search for a CWM for a similar device, unpack it, replace the fstab file and repack it again.
Thanks again!
hello I have made the porting on http://jenkins.cyanogenmod.com/job/recovery/lastBuild/console
I end up having a zip archive, how can I make my tablet to read that. I have installed cwm recovery and it is rooted. Let me know how can install it and replace my recovery with this.
BTW I have the original stock firmware of my tablet.
let me know thanks
I was trying to unlock my wifi tether by editing services.jar. I renamed both services.jar and services.odex by adding ".bak" I replaced services.jar with the recompiled one but didn't replace services.odex. now when my phone boots up I get "unfortunately verizon login has stopped" as well as a few others and I can't get in. What can I do to fix this? Its a verizon S5 with the march 31 kernel version.
Restore your backup. Or you could replace just the files you renamed with an ADB shell session and push the required files. Or "dirty' flash just the system files. Or write a full, stock firmware image with Odin.
Those would be some of the ways to recover. Lots of existing threads on this, with further elaboration if you need further guidance.
.
fffft said:
Restore your backup. Or you could replace just the files you renamed with an ADB shell session and push the required files. Or "dirty' flash just the system files. Or write a full, stock firmware image with Odin.
Those would be some of the ways to recover. Lots of existing threads on this, with further elaboration if you need further guidance.
.
Click to expand...
Click to collapse
I don't have a backup or custom recovery, I just used towelroot and thought it would be pretty safe to unlock the wifi tether. I think I forgot to turn on USB debuging so I think ADB is out of the question. Is there a way to "dirty flash" with Odin?
Edit: just did a reset with Odin, this fixed the problem. The phone was new so there wasn't much on it and I do keep my contacts and messages backed up so not much is lost except for the inconvenience of setting everything back up. I will definitely be more careful in the future.
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
I'm not exactly a newbie when it comes to flashing stuff, I know the usual backup through TWRP but I have seen in the forums that you need to backup IMEI, BT and MAC address. I've been searching through the forums but I'm seeing different tools and restore methods and I was wondering what exactly I should use should I ever want to go back to stock rom or incase installing a Custom ROM causes an issue stuff like IMEI or the addresses? Thanks in advance
I use this:
https://forum.xda-developers.com/mi-a1/how-to/tool-low-level-backup-restore-unbrick-t3790307
You need to backup EFS (contains IMEI) and persist (contains BT and Wifi MAC address), and you can do this if you use CosmicDan's TWRP.