Related
I read the previous thread on this, but my situation is a bit different.
I successfully updated to TnT lite using the standard recovery option. I later installed CWM .8 via the Market. I then used CWM's GUI to perform a backup, wipe, and update to VEganLite.
It rebooted me, into CWM recovery screen. but it didn't perform any of the actions. So I manually did a backup, then did a factory data reset, and then choose to install the Vegan Lite.
I ended up with this on reboot:
Code:
Magic Value Mismatch: [ giberish chars ]
[ giberish chars ]
Critical failure: Unable to start kernel.
Unrecoverable bootloader error ( 0x00000002 )
Sometimes it just says "Magic Value Mismatch:", other times I get the more elaborate details above. Seems tied to what type of sleep state it's coming out of.
I can still get into CWM. I've tried to reparition, install vanilla, install tnt, re-install Vegan. All appear to install, and then on reboot I get the Magic Value Mismatch.
So what process should I use next? Low level nvflash? Is there some firmware I can apply via CWM .8?
Seems like I somehow screwed up the non-recovery firmware.
nvflash is a good option. As for root cause, a lot of the mods (and even stock) do not work with newer versions of clockworkmod - you get the mismatch error you are now experiencing. I still use the older .8 bekit version.
Weird, this is CWM 2.5.1.8, I grabbed it through the Market place and it detected me as a G-Tablet.
I'll try doing the bekit version. Can I flash over the current recovery from recovery, or should I go through the NVFlash process?
On my NVFlash files I downloaded, what's the difference between:
nvflash_gtablet_46_2010112600
and
nvflash_gtablet_2010110500
Which should I put on the tablet?
EDIT:
Ok, so I noticed the BEKIT version is:
ClockworkMod 2.5.1.1-bekit-0.8
vs mine 2.5.1.8. Unlucky sub-numbering....
The latest BEKIT appears to be:
2.5.1.3 per: bekit.net
I'm going to try and flash over my current CWM using this.
if it fails, I'll go down the NVFlash path...
Edit 2:
OK, so I tried to apply 2.5.1.3 BEKIT CWM, by copying it onto the internal SD card via USB, and using the CWM 2.5.1.8 to apply it. It applied, rebooted, and now the recovery image gives the bad Magic error.
So it's NVFLASH time....
You should try the older .8 bekit, like roebeet said.
For nvflash, the older one (nvflash_gtablet_2010110500) is generally the better choice, at least from my experience. I tried the newer one once on my newer tablet, and it didn't like it at all - the older one worked flawlessly, on the other hand.
same problem
Hi everybody
I have the same problem. I was running TnT lite and it was working fine. I decided to try the Vegan ROM, so I installed last version of CWM and last version of vegan rom.
I wiped my data, I did a back-up and tried to install the VEGAN ROM. Flashing was successful, but I could not boot. I tried to restore my previous ROM, but it did't work. I was able to boot in recovery mode by pressing Volume+ and ON buttons, but now I'm not able to boot anymore .
I see a black screen with the message: "Magic Value Mismatch:"
I don't know what to do....
OK, so on my G Tab, I had installed the TnT update to the stock rom. It was working great for about 2 weeks or so. One day we went to power up and it just stoped at the first screen with the 3 birds and gives me the Magic Value Mismatch. I tried to reboot holding the power and the vol+ button to get into the system and try to recover from there. No luck. If I let it set for an hour or more and then try to start with the power and vol+ buttons it says it's trying to load a recovery program. It processes for a little bit, takes me to a black screen that says ANDROID on the left mid section of the screen and then goes back to the Magic Value Mismatch error. Occasionally it gives me a couple lines of error info, what appears to be jibberish, but after a few retries it just goes to the Magic Value Mismatch. If I let it set for an hour or more, it's just a repeat. Also on that boot attempt after letting it set, when connected it pops up on my computer for the drive for about 5 seconds and then it goes away. If I try holding the power and the vol- button instead of the vol+ button when connected to my computer it flashes a screen on the tablet and then makes a connection with the computer and stays connected, not showing a drive until I try to restart the tablet. I'm no rocket scientist with this stuff. I'm new to trying to fool around with the roms. Have I bricked this thing or is their a way to make it boot into a recovery mode and reload? I've had the back open, tried the reset button, no luck, tried disconnecting the batteries and letting it sit for an hour and then restart. No luck their either.
AkRyder said:
OK, so on my G Tab, I had installed the TnT update to the stock rom. It was working great for about 2 weeks or so. One day we went to power up and it just stoped at the first screen with the 3 birds and gives me the Magic Value Mismatch. I tried to reboot holding the power and the vol+ button to get into the system and try to recover from there. No luck. If I let it set for an hour or more and then try to start with the power and vol+ buttons it says it's trying to load a recovery program. It processes for a little bit, takes me to a black screen that says ANDROID on the left mid section of the screen and then goes back to the Magic Value Mismatch error. Occasionally it gives me a couple lines of error info, what appears to be jibberish, but after a few retries it just goes to the Magic Value Mismatch. If I let it set for an hour or more, it's just a repeat. Also on that boot attempt after letting it set, when connected it pops up on my computer for the drive for about 5 seconds and then it goes away. If I try holding the power and the vol- button instead of the vol+ button when connected to my computer it flashes a screen on the tablet and then makes a connection with the computer and stays connected, not showing a drive until I try to restart the tablet. I'm no rocket scientist with this stuff. I'm new to trying to fool around with the roms. Have I bricked this thing or is their a way to make it boot into a recovery mode and reload? I've had the back open, tried the reset button, no luck, tried disconnecting the batteries and letting it sit for an hour and then restart. No luck their either.
Click to expand...
Click to collapse
Hi,
It sounds like you're connecting your gtab to a Windows of? If so, you're going to have to install the APX driver from the Nvidia website. I have info in the 1st post here:
http://forum.xda-developers.com/showthread.php?t=914039&highlight=long
You'll then need the files, including nvflash, from bekit's dropbox
http://forum.xda-developers.com/showthread.php?t=861950
Jim
Thanks for getting me started in the right direction. Yes I am using windows. I guess since I'm kind of new to this kind of stuff Im missing something. I'm having and issue on how to launch the NV Flash from the file to get it to push to the Tablet. I click on the NV Flash application and it brings up a small window, and then goes away about as fast as I noticed it. Any suggestions? I had the APX driver driver installed to windows and apparently had the power and vol- button figured out to get the tablet to where it needs to be to be flashed. I've swapped out the bootloader.bin file like you showed to do. Im just not getting the nv flash to launch.
AkRyder said:
Thanks for getting me started in the right direction. Yes I am using windows. I guess since I'm kind of new to this kind of stuff Im missing something. I'm having and issue on how to launch the NV Flash from the file to get it to push to the Tablet. I click on the NV Flash application and it brings up a small window, and then goes away about as fast as I noticed it. Any suggestions? I had the APX driver driver installed to windows and apparently had the power and vol- button figured out to get the tablet to where it needs to be to be flashed. I've swapped out the bootloader.bin file like you showed to do. Im just not getting the nv flash to launch.
Click to expand...
Click to collapse
Nvflash.exe is only a command line apparently, I.e., it doesn't have a GUI. So, you'll need to open a command prompt, cd to the dir, then type the nvflash command line.
I tried running nvflash though the command prompt window and it didn't seem to send anything to the tablet. This is what I got from the command prompt after hitting enter:
C:\Documents and Settings\Norm.AK-F46A8F8F3EDA>c:\nvidia\tegra_froyo_20101105\nv
flash
Nvflash started
nvflash action [options]
action (one or more) =
--help (or -h)
displays this page
--cmdhelp cmd(or -ch)
displays command help
--resume (or -r)
send the following commands to an already-running bootloader
--quiet (or -q)
surpress excessive console output
--wait (or -w)
waits for a device connection (currently a USB cable)
--create
full initialization of the target device using the config file
--download N filename
download partition filename to N
--setboot N
sets the boot partition to partition N
--format_partition N
formats contents of partition N
--read N filename
reads back partition N into filename
--getpartitiontable filename
reads back the partition table into filename
--getbit filename
reads back BIT into filename
--getbct
reads back the BCT from mass storage
--odm C Data
ODM custom 32bit command 'C' with associated 32bit data
--go
continues normal execution of the downloaded bootloader
options =
--configfile filename
indicates the configuration file used with the following commands:
--create, --format_all
--bct filename
indicates the file containing the BCT
--sbk 0x00000000 00000000 00000000 00000000
indicates the secure boot key for the target device
--bl filename
downloads and runs the bootloader specified by filename
--odmdata N
sets 32bit customer data into a field in the BCT, either hex or
decimal
--diskimgopt N
sets 32bit data required for disk image convertion tool
--format_all
formats all existing partitions on the target device using the config fil
e,
including partitions and the bct
--setbootdevtype S
sets the boot device type fuse value for the device name.
allowed device name string mentioned below:
emmc, nand_x8, nand_x16, nor, spi
--setbootdevconfig N
sets the boot device config fuse value either hex or decimal
--verifypart N
verifies data for partition id = N specified. N=-1
indicates all partitions
Intended to be used with --create command only.
--setbct
updates the chip specific settings of the BCT in mass storage to
the bct supplied,used with --create, should not be with --read,and
--format(delete)_all,format(delete)_partition,--download, and--read
--sync
issues force sync commad
--rawdeviceread S N filename
reads back N sectors starting from sector S into filename
--rawdevicewrite S N filename
writes back N sectors from filename to device starting from sector S
C:\Documents and Settings\Norm.AK-F46A8F8F3EDA>
It's like it starts the program and then closes. I'm sort of at a loss at this.
Nvfash is the utility that allows you to flash your tablet, you still need to specify what to flash and where to flash it using the command line parameters.
I don't suppose you can dumb that down for a 1 legged frog in a swimming contest? Since I'm not a programmer, it's all greek to me. I think I'm in over my head on this because to type in the command lines, I have no idea what I am to be typing in as a command line. At this point I think I have a brick. Too bad I'm in Alaska and there really isn't anyone local to say here, flash this and make it work.
Deleted bcuz double
AkRyder said:
I don't suppose you can dumb that down for a 1 legged frog in a swimming contest? Since I'm not a programmer, it's all greek to me. I think I'm in over my head on this because to type in the command lines, I have no idea what I am to be typing in as a command line. At this point I think I have a brick. Too bad I'm in Alaska and there really isn't anyone local to say here, flash this and make it work.
Click to expand...
Click to collapse
I'll try...
1) I'm assuming you have the APX driver installed, along w the Windows nvflash.exe, etc. Also you'll need the zip file from bekit's dropbox, the one w 1105 in the filename.
2) unzip that 1105 zip, extracting all the files into the same dir where nvflash.exe is.
3) so now you should have 1 dir w nvflash.exe, the nv*.DLL, etc., along w a bunch of partX.img files, plus others.
4) the same dir should have the right bootloader.bin, gtablet.bct, gtablet.cfg, and nvflash_gtablet.bat
5) start a command prompt and cd to that dir
6) hold vol- on gtab then press power on gtab
7) wait for white screen then black screen
8) on pc, type:
nvflash_gtablet.bat
9) that will do the flash of the entire Gtab
10) probably want to copy/paste the output, in case.
More references, for you:
http://forum.xda-developers.com/showthread.php?t=861950
I have a few Windows-APX-related links in there (I'm an Ubuntu user, so it's all third-party links).
Thanks I'm going to give this a try as soon as I get a chance. I got a hockey game to watch tonight that streams off the computer I'm doing this on and then fix my garage door that blew a spring (when it rains it pours). I'll let you know how I did. Thanks so much!!!
I had a moment to try this before the hockey game. When I ran nvflash., the black screen on the tablet flashes the following:
Entering nvflash recovery mode / nv3P Server
Then it disconnects it’s connection from the computer and the CMD window shows the following:
C:\Program Files\NVIDIA Corporation\tegra_froyo_20101105>"nvflash.exe" --bct fla
sh.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0x3C000011
--create --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 2
chip sku: 0x8
chip uid: 0x1700618341c08597
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0x3c000011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MSC
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
creating partition: USP
creating partition: UDA
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MSC please wait.. done!
Formatting partition 6 SOS please wait.. done!
Formatting partition 7 LNX please wait.. done!
Formatting partition 8 APP please wait.. done!
Formatting partition 9 CAC please wait.. done!
Formatting partition 10 USP please wait.. done!
Formatting partition 11 UDA please wait.. done!
failed executing command 14 NvError 0x30012
command failure: create failed
Press enter to continue:
Now when I press the power and Vol- button no white screen comes on. However I can hear the chime on the computer telling me it is connecting and disconnecting and can run the nvflash over and over with the same results.
Hmmmmmmmm……. It looks like it is trying to work but something is not working as it should…. Possibly a corrupted file in the downloaded files? I'm going to try to download and set up again a bit later. The adventure continues...
I uninstalled what I had installed from the computer, deleted the downloaded files, redownloaded the files, extracted and traded out / added in the files as you guys showed, plugged in the tablet, and watched it work and flash back the stock rom and complete all tasks. Then success, Viewsonic and G Tablet screens and back to original. It updated to the latest rom which won't work with the TnT enhancement rom I had used. But at least it's working again. I'll have to do some reading on the other roms available. Even with the latest update from Vewsonic in the past week it's laggy compared to what it was with the TnT enhancement. Also no app market without the software :-( This has been a learning experience for sure and I'm still not a Jedi yet on this stuff! I just wanted to say thanks for the help and thanks for posting to help a cross eyed, dyslexic rookie in trying to rescue our G Tablet!
AkRyder said:
I uninstalled what I had installed from the computer, deleted the downloaded files, redownloaded the files, extracted and traded out / added in the files as you guys showed, plugged in the tablet, and watched it work and flash back the stock rom and complete all tasks. Then success, Viewsonic and G Tablet screens and back to original. It updated to the latest rom which won't work with the TnT enhancement rom I had used. But at least it's working again. I'll have to do some reading on the other roms available. Even with the latest update from Vewsonic in the past week it's laggy compared to what it was with the TnT enhancement. Also no app market without the software :-( This has been a learning experience for sure and I'm still not a Jedi yet on this stuff! I just wanted to say thanks for the help and thanks for posting to help a cross eyed, dyslexic rookie in trying to rescue our G Tablet!
Click to expand...
Click to collapse
Glad you got it working! So do you think the earlier nvflash problem was bcuz of a bad download? And re-downloading and nvflashing worked?
Jim
Hi guys,
I'm afraid my emmc is fried. After occasional crashes/freezes/FC's in different apps/Android modules in CM7 over a few months, one day I opened this site in the browser, and the browser FC'ed and then kept FC'ing when opened. When rebooting, the phone gets stuck looping in the CM7 animated start-up logo. When I boot in Clockworkmod (v4.0.1.0) , I get this error:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
and I can't use Clockworkmod. Cannot mount/wipe cache, cannot install anything. I tried checking the eMMC with ADB and FASTBOOT, but they can't see the device, though Heimdall does see it as I was able to flash recovery.bin again in d/l mode (but without fixing the problem). Please help, I've run out of ideas and have no phone...
bollorr said:
Hi guys,
I'm afraid my emmc is fried. After occasional crashes/freezes/FC's in different apps/Android modules in CM7 over a few months, one day I opened this site in the browser, and the browser FC'ed and then kept FC'ing when opened. When rebooting, the phone gets stuck looping in the CM7 animated start-up logo. When I boot in Clockworkmod (v4.0.1.0) , I get this error:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
and I can't use Clockworkmod. Cannot mount/wipe cache, cannot install anything. I tried checking the eMMC with ADB and FASTBOOT, but they can't see the device, though Heimdall does see it as I was able to flash recovery.bin again in d/l mode (but without fixing the problem). Please help, I've run out of ideas and have no phone...
Click to expand...
Click to collapse
you need to get into recovery via the power menu...depending on what kernel version your running, three fingering into recovery will cause a bootloop. the same thing applies to all ICS roms. If you can no longer get the phone to boot up then simply odin cwm4 fixed for cm7, three finger into recovery, wipe data, then reflash the rom. Make sure everything is backed up first. More information can be found in section 3 here:
http://forum.xda-developers.com/showthread.php?t=1238070
Thanks for your reply. I explained that the phone doesn't boot up anymore (gets stuck in a loop), and while booting into ClockworkMod works (3 fingers), I get these errors, so even though the up/down/power buttons work (I can scroll through the recovery menus/options), certain things don't work, like wiping the cache (it cannot mount or open the cache) or re-flashing CM7 from SD-card... I get errors.
I've had problems with Odin before (it said it flashed stuff, but stuff didn't work), so I've been using Heimdall for a while instead. Like I said, I was able to successfully re-upload ClockworkMod to the phone (in d/l mode) with Heimdall, but it doesn't fix the problem. The problem seems to be that the cache partition is corrupted, and I can't do much from within ClockworkMod (though it worked without problems in the past).
I've found tips on here (http://forum.xda-developers.com/showthread.php?t=1284196) that the errors I get are sometimes (though not always) because of physical corruption of eMMC. Is it possible to flash CM7 or CM9 using Heimdall or (Heimdall-frontend), are there instructions on this, though I doubt it will work...I'm new to this lol. I want to at least have a working phone, until I can figure out how to fix the cache problem and make Clockworkmod work again. Thanks.
Is it possible to just fix the cache partition or re-partition using a program like Heimdall?
bollorr said:
Hi guys,
I'm afraid my emmc is fried. After occasional crashes/freezes/FC's in different apps/Android modules in CM7 over a few months, one day I opened this site in the browser, and the browser FC'ed and then kept FC'ing when opened. When rebooting, the phone gets stuck looping in the CM7 animated start-up logo. When I boot in Clockworkmod (v4.0.1.0) , I get this error:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
and I can't use Clockworkmod. Cannot mount/wipe cache, cannot install anything. I tried checking the eMMC with ADB and FASTBOOT, but they can't see the device, though Heimdall does see it as I was able to flash recovery.bin again in d/l mode (but without fixing the problem). Please help, I've run out of ideas and have no phone...
Click to expand...
Click to collapse
i have the exact same problem with my fascinate i would think that if i could get odin to flash a new rom to it it would boot but im not intirely sure
I've found others who have the same problem... in my opinion it's clear that the cache partition got corrupted for some reason, either software (fixable) or hardware (the internal memory/eMMC which then it would need replacement or a new phone lol).
bollorr said:
I've found others who have the same problem... in my opinion it's clear that the cache partition got corrupted for some reason, either software (fixable) or hardware (the internal memory/eMMC which then it would need replacement or a new phone lol).
Click to expand...
Click to collapse
you need to flash back to a stock rom via odin, heimdall, or adb...thats the only way to fix it at this point. if you can get odin to recognize the device try section 5 of my guide.
Thanks. I'll give it a try. Odin doesn't see my device, so I'm using Heimdall Frontend which is a little bit different. Do you have instructions for it? I load atlas.pit, but then in order to load the GB rom (which is .tar.md5), it asks for a BIN file, and I also have to add a partition and it's got a lot of options there. Why doesn't Odin see my device, but Heimdall does?
I got Odin to recognize my device (stupid USB ports), I followed the instructions, phone says downloading, do not turn off target, Odin says the same... it's been more than 5 minutes, the same...does it mean I have a bricked device now?
and I forgot, Odin says in top left corner, SET PARTITION...it's been 15 minutes now, maybe it cannot set the partition
Update...I rebooted the phone into Recovery after 20 mins or so of Odin not being able to flash (set partition)... of course Odin detected it and a big red FAIL appeared in the top left corner, and the bottom log said Re-partition operation failed, so, is there anything else I can try or the memory chip fried?
http://rootzwiki.com/topic/8867-romsch-i500-vzw-ed05-froyo-heimdall-linux-friendly/
Thanks, I tried what you said, and just like I thought, Heimdall (like Odin) gave this error:
Uploading PIT
ERROR: Failed to send file part packet!
PIT upload failed!
Ending session...
ERROR: Failed to send end session packet!
please help, I have no phone
Is Re-Partition checked in Odin? If it is, try unchecking it. If it isn't, try checking it. If it's unchecked, it won't fix the corrupted cache partition, but it should at least let you flash the OS
yes, I tried that in odin, doesn't work
Yikes. You seem to be stuck between a rock and a hard place. Honestly, it seems that the only possible option here is to get a new phone. It seems as though there must be physical damage to the chip, otherwise Odin/Heimdall would have worked.
bollorr said:
Thanks, I tried what you said, and just like I thought, Heimdall (like Odin) gave this error:
Uploading PIT
ERROR: Failed to send file part packet!
PIT upload failed!
Ending session...
ERROR: Failed to send end session packet!
please help, I have no phone
Click to expand...
Click to collapse
your last option is to try adb.
MultipleMonomials said:
Yikes. You seem to be stuck between a rock and a hard place. Honestly, it seems that the only possible option here is to get a new phone. It seems as though there must be physical damage to the chip, otherwise Odin/Heimdall would have worked.
Click to expand...
Click to collapse
that's usually the diagnostic (fried eMMC chip) for these error messages (though not always) and that's what I thought, and I was looking for ways to determine for sure whether the chip is fried or not, as to know what to do and not waste my time and the time of the people on this board...for some reason adb doesn't work, or I don't know how to use it (first time using it)...I type adb devices, I get error, no devices, adb shell, error again
droidstyle,
do you have instructions anywhere on how to use adb, it was one of the first things I tried, but it doesn't see the devices, I cannot start shell (adb shell)...thanks
I made an ADB for Noobs guide about a year ago. It never gained much traction but it should still be current. Anywhere it says CM7, the same goes for CM9.
Ok, so start I took my SGS2 i777 with Shostock3 and tried to enable encryption on it. Should've been a simple click of a box and a reboot, right? The battery was charged and I had it connected to a cable. I hit start, it rebooted a few times, I entered my password halfway through, and woke up to it asking for my password as if everything was complete. I entered the password, then it loaded to the initial start screen and asked me to input all my google account info (even though I'd done this months ago). As soon as I'd hit start it would reboot the phone and I'd be back at the screen asking for my encryption password.
So I deleted all user data to see if that would help and then it wouldn't accept any password. Then I tried reflashing through recovery and adb but I always got the error that it couldn't mount /sdcard and /emmc. This seems to be the root of the problem. No matter what guide I follow, I can't access these. I can't format them either using CWM.
I recently followed guide titled: "Prepare Your Phone to Return to the Store or for Warranty Replacement by following these steps:"
and I get the following error when I enter the heimdall flash command.
(heimdall flash --kernel zImage --factoryfs factoryfs.img --cache cache.img --hidden hidden.img --modem modem.bin?)
Popup window saying Unable to mount the MTP device (although it shows up in my computer on linux mint)
"ERROR: Partition "kernel" does not exist in the specified PIT.
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
"
After having previous issues, I tried flashing the PIT using the --pit command in heimdall, under the assumption that the encryption ruined the formatting.
Summary:
So right now I can get into recovery and download modes through CWM but nothing I do has any effect. I've put new .zip files on sd cards and it doesn't work, .zip files through adb won't work, and heimdall is giving me these issues.
Any other ideas? I know since I can get into download mode that it shouldn't be that hard to fix, but I can't find out what to do right now.
If you can, I would suggest you use a windows computer with Odin to flash back to stock.
I know very little about encryption except that it seems to be loaded into a partition that is not changed by flashing or wiping.
Hi there,
My moto e 2nd gen got stuck in bootloader and won't boot.
The monitor displays as below:
**********************************************
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
EROOR: Failed to pass validation, backup fastboot
Fastboot Reason: Fall-through from normal boot mode
BL:
Baseband: M8916_2020629.41.03.21.51R SURNIA_RECTA_CUS
Product/Variant: surnia XT1527 8GB P3
Serial Number:
CPU:
eMMC:
DRAM
Console [NULL]: null
Battery OK
Device is LOCKED. Status Code: 0
Software status: Official
Connect USB Data cable
**************************************************
In the Recovery Mode display, I see "qe 0/0" which I learned from the other thread that it means the device has never been rooted.
Below is how this happened;
I used the app called KingRoot.
But the app says failed to root the device.
My phone acted weird so I uninstalled KingRoot.
Then I tried to remove the .exe file of KingRoot but failed somehow.
Right after I just turned on some secure feature (which warns the user that the app may be harmful?) of the device, the device went black and displayed the bootloader screen.
Below is what I have done so far:
Wipe cache partition (successful), then Reboot the system (Failed)
Wipe data/factory reset (successful), then Reboot the system(Failed)
Apply update from ADB with the stock Rom I found in the [http://firmware.center/firmware/Moto...Stock/XT1527/] but received error as below,
***********************************************
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong.
E:signature verification failed.
Installation failed.
************************************************
Then, I flashed three image files (recovery, boot, bootloader) using fastboot command (without unlocking bootloader).
I did not use the bootloader unlocking command.
So I thought the flashing would failed but somehow succeeded only with recovery.imag.
I believe my device has never been rooted and the bootloader has never been unlocked.
Is it possible that KingRoot has modified some system files even when the device has never been rooted and the bootloader has never been unlocked?
And how can I fix my bricked moto e?
Could someone help me out on this please? :crying:
quicksand99999 said:
:
Click to expand...
Click to collapse
Are you following the steps as mentioned in this thread ?
Also you are getting signature failed error. In such cases, download the firmware again and check
Hi there,
Thank you for the reply. Sorry that it took so long to reply back.
I did what the above mentioned guideline tells for the first time.
And after I tried second time, finally my phone started working again!!
The first time with an older version stock firms, some file failed to be flashed.
So I used seemingly-newer-version-than-my-original-firmware the second time.
Even though "mfastboot flash system system.img_sparsechunk.5" was missing from the stock firmware, my phone was able to recover to the normal state.
THANK YOU SO MUCH!!!
I went to some shops that claim they can fix bricked phones but all of them said that motorola phones are difficult to fix. But I could fix it after second trial.
Developer Forum >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Shops
moto e xt1521 bootloader unlock?
**********************************************
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
EROOR: Failed to pass validation, backup fastboot
Fastboot Reason: Fall-through from normal boot mode
its displays when i flash
how to fix it?
Read drs22's post above ! He's mentioned the link you can follow to fix this, follow the steps to the 'T' and ensure you download a more recent version of the ROM.
Hello. I am new here and sorry if broke any rules.
I have note 5 n920L. Bought it used. Received update 7.0. After it, it worked for 2 days and than started working slowly. Restarted and after restart I saw blue screen - "installing system updates". The same screen was for 10 hours. It could not load into recovery mode for wiping. It could not install firmware from download mode. Cannot add here photos because do not have 10 posts.
When trying installing firmware, odin stops on system.img.
When trying recovery mode, it does not enters there.
I see recovery mode after hours trying installing system updates. When I click on wipe data or cache, I have errors:
no support single - sku
supported api: 3
dm-verify verification failed
e: failed to mount cache (invalid argument)
e: cannot mount cache recovery last install and many other similar errors
FRP IS LOCKED. STATUS IS CUSTOM (do not know how and why, if it was custom could not receive update..)
You're certain that you are using the same firmware build? What's the error message in Odin?
You can also try Smart Switch in emergency mode.
es0tericcha0s said:
You're certain that you are using the same firmware build? What's the error message in Odin?
You can also try Smart Switch in emergency mode.
Click to expand...
Click to collapse
Thank you for the reply. Odin does not have an error. Starts installing and than stops on system.img. Left for 20 hours and it was still there.
What do you mean in same firmware build? I downloaded firmware from samsung site. Downloaded it for 920L model. Tried android 7 and 6 too.
Cannot connect to the smart switch because it writes that my device is unsupported.
As I see, no one knows about this problem..
Could be the wrong firmware or Odin version. You might see if you can use Odin to install TWRP and boot into Recovery that way.