Did you get the message: Magic Value Mismatch:-.-.-.-.-.-?!
After flashing a new recovery it happens sometimes.
GREEN ZONE
Are you able to go to the recocery menu(power + vol up)? If not, go to BLUE ZONE. If yes, follow these steps
1. check whether you have copied your rom as "update.zip" to your SD card's root directory
2. Go to recovery menu and install update.zip
BLUE ZONE
You may did something wrong while flashing a new recovery. Here is the right method:
1. go back to fastboot mode(power+power+power+vol up) and type these commands on your PC
2. fastboot erase userdata
3. fastboot erase system
4. fastboot erase cache
5. fastboot erase linux
6. fastboot erase recovery
7. fastboot flash recovery recovery.img (change path, if recovery.img is not in the same directory as fastboot.exe)
8. fastboot reboot
Are you able now to go to the recovery menu? If yes, go to GREEN ZONE and follow steps. If not, go to ORANGE ZONE.
ORANGE ZONE
Are able to unpack the update.zip and find the system.img and boot.img files? If not, then go to RED ZONE. If yes, copy these 2 files to the directory where the fastboot.exe is, run these commands:
1. fastboot erase recovery
2. fastboot flash recovery recovery.img
3. fastboot -w
4. fastboot erase linux
5. fastboot erase system
6. fastboot flash system system.img
7. fastboot flash linux boot.img
8. fastboot reboot
ROM is installed. Enjoy it!
RED ZONE
Make sure, that you copied the same recovery.img to fastboot folder, that you had flashed before to your tablet.
Type this command in recovery mode:
1. fastboot boot recovery.img
This command will run the recovery from your PC. After the recovery menu is booted, go to GREEN ZONE and enjoy your ROM!
If this was helpful to you, please do not hesitate to click on Thanks!
Lol, nice to see my post copy/pasted without any links indicated. Anyway, I hope It's helpful for ppl.
Tried following these steps, however, I'm still getting this error... followed this thread
http://forum.xda-developers.com/showthread.php?t=1470823
installed recovery successfully (via fastboot), and update seems to install fine, until I reboot and get the "Magic Value Mismatch" again..
Any ideas?
yellowumbrella said:
Tried following these steps, however, I'm still getting this error... followed this thread
http://forum.xda-developers.com/showthread.php?t=1470823
installed recovery successfully (via fastboot), and update seems to install fine, until I reboot and get the "Magic Value Mismatch" again..
Any ideas?
Click to expand...
Click to collapse
So you installed the recovery via fastboot. Did you manage to boot into recovery mode?
I had that issue, that I couldn't boot into recovery mod from my Folio, by pressing power+Up button. Thats why I added the RED ZONE method. Its like booting recovery from your PC. (fastboot boot recovery.img). All the times I wanna upgrade my current ROM, I have to do this step, because the power+up does not work, and the Folio skips booting in recovery and wanna do normal booting. However there is no Rom installed on machine, so I get the magic value mismatch message.
So try to boot recovery from your PC, but be sure you have copied to your fastboot folder the same recovery, that you flashed onto the tablet.
I hope it was helpful. If something is not clear, feel free to ask.
Hi there, thanks for the answer.
I am able to install recovery images via fastboot.
Device is showing up as a question mark with >fastboot devices
but recovery installs fine. CWM gives a series of e: can't opne/mount /cache errors.
Foliomod 1.4 installs no problem, thanks to the method here
http://forum.xda-developers.com/showthread.php?t=1458876
yellowumbrella said:
Hi there, thanks for the answer.
I am able to install recovery images via fastboot.
Device is showing up as a question mark with >fastboot devices
but recovery installs fine. CWM gives a series of e: can't opne/mount /cache errors.
Foliomod 1.4 installs no problem, thanks to the method here
http://forum.xda-developers.com/showthread.php?t=1458876
Click to expand...
Click to collapse
Are you able to wipe cache from recovery? And what else errors are listed?
One more thing, try to flash your boot.img and system.img via fastboot as written above.
If I follow this
http://forum.xda-developers.com/showthread.php?t=1458876
and let it install cwm v 3, I get the cache error and cannot wipe or mount via recovery.
If I follow the ICS thread, and flash the new cwm v5 via fastboot, I don't get the cache error, but the rom simply won't start. If I open the package, there is a boot.img, but not a system.img, just a system folder...
I could try flashing boot.img, but I don't see how that could help
yellowumbrella said:
If I follow this
http://forum.xda-developers.com/showthread.php?t=1458876
and let it install cwm v 3, I get the cache error and cannot wipe or mount via recovery.
If I follow the ICS thread, and flash the new cwm v5 via fastboot, I don't get the cache error, but the rom simply won't start. If I open the package, there is a boot.img, but not a system.img, just a system folder...
I could try flashing boot.img, but I don't see how that could help
Click to expand...
Click to collapse
Well just to see it clear. So you are able to install Foliomod 1.4, so your Internal storage is not broken.
When I get home, I will check the system folder of ICS rom. There are some method to create system.img from an unpacked folder...
So, in CWM 5.5.0.4 you manage to install Zip from SD card, ROM and GAPPS as well, but the Rom does not boot?!
yup, that's exactly it.
Haven't tried installing Gapps since I can't even get the rom to boot.
I have a perfectly working tablet with foliomod 1.4, and I did get honeycomb to run but some apps crashed so I reverted back to foliomod.
with CWM CWM 5.5.0.4 everything seems to work great, except at reboot, nothing happens (somehow, I no longer even get the magic value mismatch)
------------------
PS. not sure if this is at all relevant, but I cannot fastboot from win7, I'm fastbooting in either ubuntu or xp via VirtualBox, and the device, when calling >fastboot devices shows up as ?????????? (ubuntu) and ? (xp)... :\
yellowumbrella said:
yup, that's exactly it.
Haven't tried installing Gapps since I can't even get the rom to boot.
I have a perfectly working tablet with foliomod 1.4, and I did get honeycomb to run but some apps crashed so I reverted back to foliomod.
with CWM CWM 5.5.0.4 everything seems to work great, except at reboot, nothing happens (somehow, I no longer even get the magic value mismatch)
------------------
PS. not sure if this is at all relevant, but I cannot fastboot from win7, I'm fastbooting in either ubuntu or xp via VirtualBox, and the device, when calling >fastboot devices shows up as ?????????? (ubuntu) and ? (xp)... :\
Click to expand...
Click to collapse
Try to install gapps as well. Maybe it helps...
nope, no luck even with gapps installed..
just a blank screen..
sigh
yellowumbrella said:
nope, no luck even with gapps installed..
just a blank screen..
sigh
Click to expand...
Click to collapse
Have you tried all the roms? ICS Alpha 1,2,3 and 4?
Tried 3 and 4, didn't bother trying earlier ones, as it seems the latest ones work for most users
yellowumbrella said:
nope, no luck even with gapps installed..
just a blank screen..
sigh
Click to expand...
Click to collapse
Hmmm strange. I ask it for you on developers forum. What you can still do, is to check the steps, that you did them correctly. In most of the cases users forget something, or do some steps incorrectly.
Try to erase userdata, cache, system, linux and recovery in fastboot. You mentioned you had problem with fastboot under Win7. Problem may occur, in case of not proper erasing.
Thanks, I'll give it another try tonight.
Fastboot in win7 is simply not seeing the device. It shows up in XP and Ubuntu, but as "??????" - not sure if that could be a symptom.
I'll post a reply as soon as I've tried, and let you know how it went.
yellowumbrella said:
Thanks, I'll give it another try tonight.
Fastboot in win7 is simply not seeing the device. It shows up in XP and Ubuntu, but as "??????" - not sure if that could be a symptom.
I'll post a reply as soon as I've tried, and let you know how it went.
Click to expand...
Click to collapse
For me it works perfectly on Win7. After Installing SDK and JDK the in the devicemanager it is shown as an Unknown device. Simply add the driver manually to it.
Download driver from attachment.
Copy it to SDK\USB_driver folder
That works for me. After its done, the Folio is shown as "Fastboot" in device manager. But connect the tablet in fastboot mode to your PC before you add driver manually to it.
Thanks for that.
Tried it, still not working in win7. It shows up correctly in device manager, but fastboot itself just doesn't want to see it...
I've attached a screenshot for you
EDIT: screenshot gets resized, but it shows device manager listing
NVIDIA Android Fastboot Device
and a terminal with fastboot not seeing the device
yellowumbrella said:
Thanks for that.
Tried it, still not working in win7. It shows up correctly in device manager, but fastboot itself just doesn't want to see it...
I've attached a screenshot for you
EDIT: screenshot gets resized, but it shows device manager listing
NVIDIA Android Fastboot Device
and a terminal with fastboot not seeing the device
Click to expand...
Click to collapse
When You have win7, You have run the console as admin!
Or copy the complete Fastboot folder to another Destination like c:\temp...
Thanks stefannsv, tried it, still not showing...
But I can access fastboot on another platform, so I assume it's not an issue, I can just switch over to another OS to flash
no go, followed both this original post (tried all steps except orange, cause the rom I'm trying to install has a system folder, not a system.img)
Last method I tried was:
1) boot into fastboot
2) boot cwm-recovery-5.5.0.4.img directly from PC
3) wipe data/factory reset
4) wipe cache partition
5) install zip from SD card and chose the alpha 4 release
installing update...
then back to recovery, reboot and voilà... magic value mismatch again (it had disappeared for a while... )
Also, when booting into CWM 3.0.0.5, I get a series of "E: Can't mount/cache/recovery" type errors.. could this be related?
booting directly into recovery from PC doesn't alllow me to install any ROMS, not even foliomod 1.4 which works if using puppet13th's method
I did a System wipe instead of a Factory Reset, and I had no ROM on the internal SD card. Is there anything I can do to get this running again? I can get into twrp v2.1.3.
shadow3352 said:
I did a System wipe instead of a Factory Reset, and I had no ROM on the internal SD card. Is there anything I can do to get this running again? I can get into twrp v2.1.3.
Click to expand...
Click to collapse
The easiest route to go may be to ADB push a ROM to internal then flash it from TWRP. There's plenty of guides on how to ADB push files to the internal memory, so do a search around. Another option is to flash TWRP 2.2.1.4 via fastboot (you'll need to install the AndroidRoot.mobi custom bootloader first) and install a ROM from the external memory. Instructions to install TWRP 2.2.1.4, with a link to the custom bootloader can be found at the following link:
http://www.teamw.in/project/twrp2/93
Good luck!
~Azrael's Kiss~
AzraelsKiss said:
The easiest route to go may be to ADB push a ROM to internal then flash it from TWRP. There's plenty of guides on how to ADB push files to the internal memory, so do a search around. Another option is to flash TWRP 2.2.1.4 via fastboot (you'll need to install the AndroidRoot.mobi customer bootloader first) and install a ROM from the external memory. Instructions to install 2.2.1.4, with a link to the custom bootloader can be found at the following link:
http://www.teamw.in/project/twrp2/93
Good luck!
~Azrael's Kiss~
Click to expand...
Click to collapse
I couldn't find a way to install 2.2.1.4 via fastboot. And as far as ADB goes, I have no idea how to use it. I installed the drivers and everything, but when I do adb devices, nothing shows up under devices attached, but I do see it under device manager.
shadow3352 said:
I couldn't find a way to install 2.2.1.4 via fastboot. And as far as ADB goes, I have no idea how to use it. I installed the drivers and everything, but when I do adb devices, nothing shows up under devices attached, but I do see it under device manager.
Click to expand...
Click to collapse
The link I provided has the instructions for installing TWRP 2.2.1.4. Look again. The GooManager option is out because you don't have an OS, but if you have the custom bootloader (which is recommended) you can flash the img file in the second set of instructions, or it also provides a blob file to flash in the third set of instructions, and finally, if you could get ADB to work, the fourth set of instructions are for ADB installation.
~Azrael's Kiss~
AzraelsKiss said:
The link I provided has the instructions for installing TWRP 2.2.1.4. Look again. The GooManager option is out because you don't have an OS, but if you have the custom bootloader (which is recommended) you can flash the img file in the second set of instructions, or it also provides a blob file to flash in the third set of instructions, and finally, if you could get ADB to work, the fourth set of instructions are for ADB installation.
~Azrael's Kiss~
Click to expand...
Click to collapse
I really appreciate your help. Do you know where I would but the twrp file I would flash? When I do "fastboot -i 0x0b05 flash recovery twrp.blob" or "fastboot -i 0x0b05 flash recovery twrp.img" it just says error: cannot load
shadow3352 said:
I really appreciate your help. Do you know where I would but the twrp file I would flash? When I do "fastboot -i 0x0b05 flash recovery twrp.blob" or "fastboot -i 0x0b05 flash recovery twrp.img" it just says error: cannot load
Click to expand...
Click to collapse
The img or blob file has to be in the same directory as your fastboot binary on your PC.
~Azrael's Kiss~
AzraelsKiss said:
The img or blob file has to be in the same directory as your fastboot binary on your PC.
~Azrael's Kiss~
Click to expand...
Click to collapse
Okay, I got that. It said finished in cmd prompt and now there's a full loading bar on the screen. Should I wait or restart?
AzraelsKiss said:
The img or blob file has to be in the same directory as your fastboot binary on your PC.
~Azrael's Kiss~
Click to expand...
Click to collapse
I got it to work through ADB pushing CM10 on to the internal SD. I really want to thank you for your help.
ok guys this is not my first rodeo. I have hacked all my prior phones but I need some assistance here...
I have unlocked my bootloader, rooted and installed CWM. Now I am trying to install a system writable Kernel and modules so I can install a Rom. I am having a problem getting ADB to see my phone. When I do adb devices it comes up blank and will not push the modules to my phone. I have re-installed the HTC manager driver files and restarted my PC. Windows 7 64 bit.
Can someone give me some ideas on how to get adb to see my phone?
Also can someone give me some specific instructions with adb commands to install the kernel and modules and what exactly I need to have in my adb folder??
Any help is appreciated...
Memnoch73 said:
ok guys this is not my first rodeo. I have hacked all my prior phones but I need some assistance here...
I have unlocked my bootloader, rooted and installed CWM. Now I am trying to install a system writable Kernel and modules so I can install a Rom. I am having a problem getting ADB to see my phone. When I do adb devices it comes up blank and will not push the modules to my phone. I have re-installed the HTC manager driver files and restarted my PC. Windows 7 64 bit.
Can someone give me some ideas on how to get adb to see my phone?
Also can someone give me some specific instructions with adb commands to install the kernel and modules and what exactly I need to have in my adb folder??
Any help is appreciated...
Click to expand...
Click to collapse
As far as getting your phone to be recognized, try installing HTC Sync and then immediately uninstalling it, I have seen this fix many people's driver issues.
This is how I usually flash my kernels: Assuming you have fastboot in the same folder as adb, put the boot.img and the modules.zip in that same folder. Boot into recovery. In recovery do:
adb push modules.zip /sdcard/whatever (whatever folder you keep your flashables in)
Then hit install in recovery, find the file you just pushed and flash it. Then do:
adb reboot bootloader
Then while you are in bootloader (Should say "fastboot usb" in red) do this:
fastboot flash boot boot.img (replace boot.img if your file is named differently)
You should see it flash the file, and finally do:
fastboot reboot
Thanks man. I think I have it now. When I did fastboot devices it showed my phone. Also I was confused about the modules after more reading I just put them on my sd card and flashed them in recovery.
I have the stock system writable kernel installed and modules flashed. All looks good. Booted up and its says dsb's kernel in my about phone.
I think I'm off to flash a rom now.
Thanks
my device is stuck in bootloop with no backup and is not showing up in adb for me to push rom to phone? suggestions????
What Version of adb do you have and which recovery are you using
Sent from my HTC One X+ using xda premium
Reboot into recovery, find the adb sideload option, activate it. Run adb sideload romname.zip on your computer where romname.zip is the ROM you want to flash. Sometimes it will take a number of minutes for your computer to recognize your device once it is in sideload mode. Just keep trying. I've had more luck doing this with TWRP than with CWM. We really should sticky some sort of sideload instructions...
NasaGeek said:
Reboot into recovery, find the adb sideload option, activate it. Run adb sideload romname.zip on your computer where romname.zip is the ROM you want to flash. Sometimes it will take a number of minutes for your computer to recognize your device once it is in sideload mode. Just keep trying. I've had more luck doing this with TWRP than with CWM. We really should sticky some sort of sideload instructions...
Click to expand...
Click to collapse
got error device not found using twrp recovery and * failed to write data 'protocol fault (no status)' * with cwm don't know what's wrong, Not rooted phone since my nexus one when i used to always root but with that could just whip the sd card out...
jizang said:
What Version of adb do you have and which recovery are you using
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
1.0.31 and tried both twrp and cwm
have you waited a few minutes and tried executing the adb sideload command on your computer multiple times when trying to sideload with TWRP?
NasaGeek said:
have you waited a few minutes and tried executing the adb sideload command on your computer multiple times when trying to sideload with TWRP?
Click to expand...
Click to collapse
yea ridiculous amount times
I had the same problem i could not adb sideload a Rom,in the end i had to flash stock ruu to save my phone
Sent from my HTC One X+ using xda premium
indie12 said:
got error device not found using twrp recovery and * failed to write data 'protocol fault (no status)' * with cwm don't know what's wrong, Not rooted phone since my nexus one when i used to always root but with that could just whip the sd card out...
Click to expand...
Click to collapse
Install TWRP instead of CWM! AFAIK adb sideload does not work on CWM recovery, had the same problem when i needed to use this command for the first time.
reaper90 said:
Install TWRP instead of CWM! AFAIK adb sideload does not work on CWM recovery, had the same problem when i needed to use this command for the first time.
Click to expand...
Click to collapse
doesn't work with twrp either,
also forgot to mention is odd that adb doesn't find device since i can flash new recovery / kernal via fastboot?
adb discovering my device in sideload now but not allowing the sideload? how can i push the rom to sdcard via adb?
indie12 said:
doesn't work with twrp either
Click to expand...
Click to collapse
It has to work, believe me. Are you on latest TWRP 2.5.0.0? If not, you should probably update. Erasing cache in fastboot ("fastboot erase cache") may help sometimes. Did you wait long enough for adb to recognize your phone in sideload mode (may take some minutes)?
If not:
1. Boot your phone in recovery, connect it to your computer and start sideload mode in recovery.
2. Open command line, navigate to the folder where your adb/fastboot files are (you must also copy the desired rom.zip file into this folder)
3. Type "adb start-server" and now wait some minutes.
4. Type "adb devices", your device should now be listed there in sideload mode. If not, wait some more time and try again
(10 min should be enough, if not, there's probably something wrong with the driver or adb files on your computer)
5. Now you can type "adb sideload name_of_your_rom.zip"
It should work now. when it's finished, the rom.zip file is saved on your phones internal memory as "sideload.zip"
If not, there must be something wrong with your driver and/or adb/fastboot files. Try reinstalling them then.
reaper90 said:
It has to work, believe me. Are you on latest TWRP 2.5.0.0? If not, you should probably update. Erasing cache in fastboot ("fastboot erase cache") may help sometimes. Did you wait long enough for adb to recognize your phone in sideload mode (may take some minutes)?
If not:
1. Boot your phone in recovery, connect it to your computer and start sideload mode in recovery.
2. Open command line, navigate to the folder where your adb/fastboot files are (you must also copy the desired rom.zip file into this folder)
3. Type "adb start-server" and now wait some minutes.
4. Type "adb devices", your device should now be listed there in sideload mode. If not, wait some more time and try again
(10 min should be enough, if not, there's probably something wrong with the driver or adb files on your computer)
5. Now you can type "adb sideload name_of_your_rom.zip"
It should work now. when it's finished, the rom.zip file is saved on your phones internal memory as "sideload.zip"
If not, there must be something wrong with your driver and/or adb/fastboot files. Try reinstalling them then.
Click to expand...
Click to collapse
its just worked, transfering the rom now, no idea what caused it to work this time but it is so thanks
Hello
i managed to unlock my bootloader, flashed twrp recovery, flashed super user.
Tried to install dirty unicorn and got status 7 error.
And now i dont have a rom/os installed.
I tried to move over .zip files through twrp but cant mount drives.
Any help?!?
I TRIED TO PUSH ZIP WITH SIDELOAD AND NO LUCK
BUMP!
i really need to get this fixed please help
xr1charxx said:
BUMP!
i really need to get this fixed please help
Click to expand...
Click to collapse
I did the same thing yesterday, as it was my first time using TWRP (always been a CWM guy), All you have to do to fix it is go into advanced and go into adb sideload, put your rom in you adb folder and run this command
adb sideload nameofzip.zip
Then the zip will be placed in internal storage named sideload.zip and you can flash it.
dsf767 said:
I did the same thing yesterday, as it was my first time using TWRP (always been a CWM guy), All you have to do to fix it is go into advanced and go into adb sideload, put your rom in you adb folder and run this command
adb sideload nameofzip.zip
Then the zip will be placed in internal storage named sideload.zip and you can flash it.
Click to expand...
Click to collapse
Already tried this. when i run adb devices my device does not show up. and when i try to sideload any files i get error:closed
xr1charxx said:
Already tried this. when i run adb devices my device does not show up. and when i try to sideload any files i get error:closed
Click to expand...
Click to collapse
I would try to plug in the USB after your already in recovery.
If you cant get that to work you can always buy this:
https://shopmeenova.appspot.com/st/order.html
its a microusb to microsd its a good worst case and will get you up and running.
do you still have the rom that errored out on you on your internal storage? if so you can always try a fresh wipe and try to install again.