Related
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
Ok so
Rooted
S-off
hboot 1.12.2222
was running Mean-rom 4.4
Then tried to install the new apk fix for ringtones
http://forum.xda-developers.com/showthread.php?t=1900629
Phone rebooted then then continues to be stuck in boot loop.
What I have tried:
Factory reset in bootloader
clear storage in bootloader
reinstall TWRP to get in recovery as if I choose recover in bootloader it just boot loops.
Tried to install the RUU but it can not connect during boot loops and errors out.
Any ideas?
Thanks in advance
Try fastboot wipe recovery then fastboot flash recovery recovery.img, if recovery loops back to bootloader then it's corrupt. Make sure you flash the latest twrp
om4 said:
Try fastboot wipe recovery then fastboot flash recovery recovery.img, if recovery loops back to bootloader then it's corrupt. Make sure you flash the latest twrp
Click to expand...
Click to collapse
All I see in fastboot option on bootloader is
bootloader
reboot
reboot bootloader
powerdown
am I missing something?
Those are fastboot commands, you use the terminal
fastboot wipe recovery
fastboot flash recovery recovery.img
You should be able to boot into recovery afterwards
What terminal? I'm a bit lost here
Do you have adb tools or Android SDK?
C:\android-sdk-windows
Open cmd prompt by opening SDK folder and then hold shift and right click, it will say open cmd prompt or something similar I don't recall if adb is in separate folder but I don't think so. From there you can plug in the phone in fastboot and type fastboot devices, it will tell you if you are connected or not. Download twrp and place it in the same folder. Then you can use the commands I listed earlier
om4 said:
Open cmd prompt by opening SDK folder and then hold shift and right click, it will say open cmd prompt or something similar I don't recall if adb is in separate folder but I don't think so. From there you can plug in the phone in fastboot and type fastboot devices, it will tell you if you are connected or not. Download twrp and place it in the same folder. Then you can use the commands I listed earlier
Click to expand...
Click to collapse
Get an error see attached
Now that I am in fasboot usb on the bootloader the RUU can connect to phone via USB.
If I just flashed that and started all over would that work and do I need to unroot and relock before doing the RUU?
Still not having any luck on terminal so far.
Sorry I was busy arguing with gf, it seems you aren't where you need to be if fastboot isn't recognized, I haven't had access to my own pc in quite a while so I'm having trouble remembering if there is another directory
om4 said:
Sorry I was busy arguing with gf, it seems you aren't where you need to be if fastboot isn't recognized, I haven't had access to my own pc in quite a while so I'm having trouble remembering if there is another directory
Click to expand...
Click to collapse
got fastboot working but get this with your first command
That's because I haven't used wipe in fastboot in quite a while, I'm sure I'm just confused on wipe and erase but you shouldn't need it, the first command should be fastboot erase recovery but like I said you shouldn't really have to, it's just like formatting before flashing the recovery, just fastboot flash recovery openrecovery.img or what ever the name is for the twrp file
Ran
C:\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (7356 KB)...
OKAY [ 1.112s]
writing 'recovery'...
OKAY [ 1.796s]
finished. total time: 2.912s
Hit recovery and we we still are in boot loop
Relock bootloader and run ruu fastboot oem lock
copc said:
All I see in fastboot option on bootloader is
bootloader
reboot
reboot bootloader
powerdown
am I missing something?
Click to expand...
Click to collapse
select bootloader the recovery as soon you have recovery up wipe and reflash the rom
HTC EVO LTE
luisrod03 said:
select bootloader the recovery as soon you have recovery up wipe and reflash the rom
HTC EVO LTE
Click to expand...
Click to collapse
Thanks recovery just loops, could never get in.
Ok this is where I am at (see OP)
We tried flashing TWRP and original recovery via ADB
We tried running RUU
I'm still stuck in a boot loop....
I am having a similar problem stuck in bootloader. I relocked to go to the new firmware and now am stuck in the bootloader. I can access adb but can't access recovery. I am now relocked. Can I unlock again with a fastboot command?
If you unlocked manually, HTC sends the unlock code code just use fastboot to flash, if you used regawmod, just run it again. I don't know if regawmod will recognize the phone in boot loader though
First of, I'm running Cyanogenmod 12.1 on my Z2.
On the install it vanished my TWRP Recovery, so I decided to reflash it using their app - this was unsucessfull. I thought I would flash it the next day using adb, so I didn't mind.
However in the next hours I needed to reboot the phone - resulting in the Sony logo and nothing more. So I bootet into the CM recovery and tried to reflash the CyanDelta zip - this failed and resulted in "footer is wrong - signature verification failed - Installation aborted". The next thing I tried was flashing a zip by adb recovery sideload - this failed as well and resulted in "protocol fault (no status)".
This was when I tried to boot into the bootloader using the recovery menu entry. The screen got black, the LED lighted up blue and nothing happened forever. The same thing occours when I try to boot into the bootloader by hardware keys (hold VolUp and insert MicroUSB cable).
So, in short:
I can't boot android
I can't install zips by CM recovery
I can't boot into the bootloader [EDIT: I can.]
I can't install nandroid backups since the CM recovery doesn't offer that
Any idea?
If the phone's LED lights up blue it means that you are in fastboot mode (AKA the bootloader) . It is normal for the screen to be black. I suggest that you download a stock FTF and flash it using the windows flashtool application. Your phone is fine. Good luck.
the_crevis said:
If the phone's LED lights up blue it means that you are in fastboot mode (AKA the bootloader) . It is normal for the screen to be black. I suggest that you download a stock FTF and flash it using the windows flashtool application. Your phone is fine. Good luck.
Click to expand...
Click to collapse
Ah, I feel dumb now. I might be damaged from the informational Nexus bootloader.
So, I tried to flash a new recovery - fastboot flash twrp-2.8.6.0-sirius.img - which succeded, but it still boots the CM Recovery. Buh.
Seems like something is overriding the recovery on boot. So lets erase everything:
Code:
fastboot erase system
fastboot erase userdata
fastboot erase recovery
fastboot flash twrp-2.8.6.0-sirius.img
Aaaand - still CM Recovery.
I also tried to flash a stock image as you suggested, however:
Code:
fastboot flash system system.sin
sending 'system' (1800183 KB)...
FAILED (remote: data too large)
finished. total time: 0.002s
No worries, I came from a nexus 4 and it confused me as well at first. Try exacting http://forum.xda-developers.com/xperia-z2/development/kernel-m5-kernel-t2858912 and flashing the boot image via fastboot. That should give you a working recovery.
As I said, flashing a recovery by fastboot results in the CM Recovery.
I just tried to wipe my device using the CM Recovery, it told me it was unable to mount /data - my guess? The filesystem is ****ed up.
EDIT: I got it. Seems like TWRP needs some custom stuff to work (which is provided by CM). Flashing philz worked fine and allowed me to sideload a proper ROM. Everything fine now
Hi all,
I appear to have done something wrong when flashing my device with boombox and flashing twrp. I seem not to be able to access recovery so I can update my boombox rom. I have tried button combinations, I have tried fastboot boot twrp.img in bootloader which just reboots my system, I have tried booting directly from home screen using adb which registers an error and I have tried re-flashing but unfortunately I cannot access recovery.
Any way I can get into recovery without erasing my data?
Jonnibravo said:
Hi all,
I appear to have done something wrong when flashing my device with boombox and flashing twrp. I seem not to be able to access recovery so I can update my boombox rom. I have tried button combinations, I have tried fastboot boot twrp.img in bootloader which just reboots my system, I have tried booting directly from home screen using adb which registers an error and I have tried re-flashing but unfortunately I cannot access recovery.
Any way I can get into recovery without erasing my data?
Click to expand...
Click to collapse
If you're rooted, give the reboot recovery app you installed after bootloader unlock root privileges.
If not then use the exact same PC ADB commands to boot to TWRP like during bootloader unlock.
I'm confused why you mention flashing TWRP after Boombox. Surely you didn't do that. You already had TWRP.
I am rooted, Recovery reboot just reboots the phone, I have tried to get into twrp by reinstalling but again does the same things just reboots the system after the corruption warning screen. I've also tried to install from the bootloader with the fastboot boot twrp.img command but it simply says waiting for device.
Sorry turns out I was flashing the wrong file from another tutorial, I was flashing 3.1.1 instead of 3.2.1
Jonnibravo said:
Sorry turns out I was flashing the wrong file from another tutorial, I was flashing 3.1.1 instead of 3.2.1
Click to expand...
Click to collapse
Then you didn't follow my bootloader unlock and root guide. I never mention that other TWRP, much less link to it.
You're going to have to load into Download mode and use fastboot commands, but you say you couldn't get past flashing TWRP.
Uninstall the LG Mobile Driver if you have them, then reinstall.
1st, reboot into OS, then open up Device Manager and change view to Show hidden devices. You should see a new category named 'ADB Interface' and underneath that 'Fastboot Interface (Google USB ID)'.
If not, you will also see 'ADB Device' for Other Devices category:
right click that to update driver software ---> Browse my computer for driver software ---> Let me pick from a list... ---> Show all Devices ---> Have Disk ---> Browse ---> C:\Program Files (x86)\LG Electronics\LG Mobile Driver ---> 'lgandbus' ---> 'LGE ADB Mobile Interface'
Download adb/fastboot software, download Joan TWRP 3.2.1 img file and place it in adb/fastboot folder, then send your phone into Download mode:
Open up cmd and type the following after changing directory to Adb/fastboot folder: fastboot devices (see if your device is there), fastboot flash recovery TWRP.img or (whatever file is named).img, then fastboot boot TWRP.img or (whatever file is named).img
Hi, I'm having some issues trying to install the newest update of A10.
I was on A9 with unlocked bootloader, root and twrp of recovery.
I first tried to install the .rar image via recovery but I couldn't find in the memory, but I already wiped system vendor and data.
So when I rebooted to try if the file was there or not, there was no recovery anymore.
Now I'm trying to flash the newest rom via fastboot but through the flash_all.bat it gives me fastboot tz_a error, so I'm trying to install a recovery through fastboot using this guide https://forum.xda-developers.com/mi-a3/how-to/basic-guide-to-flash-recovery-rom-via-t3989603 but of course it doesn't work and when I reboot it doesn't enter the recovery but always in fastboot (even tho I press the + button).
What should I do now? Is there anyway to erase everything and install a clean OS from 0 just from fastboot? (Without the flash_all or miflash because it doesn't work)
P.S. I don't care about the data, I've done a backup of all my important files before
Thanks for the help
Sapper Morton said:
First, you have to understand what you did. You wiped your system and vendor image, and didn't installed a newer one afterwards, you didn't wiped your recovery (it's inside boot partition).
Further, .rar files will not be flashed through TWRP, .zip must be used instead, with proper format, there must be a compatible flash script inside.
You can't access your recovery, just because you wiped system; inside your bootloader there's a component responsible to manage the slots, bootctl and by default if it detects a corrupted or invalid system partition, it will always boot onto bootloader mode.
As for the tz_a error, you must unlock critical partitions flashing, just because, tz is a critical partition, thus, run in Fastboot:
Code:
fastboot flashing unlock_critical
If you want to know your current state, use:
Code:
fastboot oem device-info
Your current slot is blocked by bootctl, but this doesn't mean your inactive is too, so, use:
Code:
fastboot set_active other
And reboot into TWRP again, that is, if you do have it installed in your inactive slot.
Fastboot/ADB and other tools, you will find it in here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
If you want to restore using recovery firmware, please do the favor, and read the post below:
https://forum.xda-developers.com/showpost.php?p=82595733&postcount=379
Click to expand...
Click to collapse
Thanks for the help but I managed to get into the recovery and install the rom via fastboot, the thing I was missing was a recovery working for Android10 (even though I remember recovery doesn't have nothing to do witg the installed OS), so I managed to install the recovery and root, and everything went fine after a few tries between various guides. Probably my partitions now are all messed up, but if I boot normally it goes into system (slot A), if I boot into recovery it goes into twrp and also works fastboot. Probably I also installed the OS on slot b, but I don't care as long the first partition works well