I had the "magic value mismatch" problem after using an incorrect ClockworkMod version (with ROM Manager). So I used nvflash, as described in the thread "nvflash FULL restore, using bekit's original image".
After that, first boot was OK, back to original firmware. So I put ClockworkMod v08 (cwmod_internal.zip) into internal memory and shut the tablet down.
I could never power it up again after that.
I tried power button and volume +, power button and volume -. No signs of life.
I opened the case and hold the reset button on the back. Nothing. I even tried disconnecting the battery cable.
I can't find a way to power it back up.
Any ideas?
PS.: If I connect it to the charger, the LED turns red (as expected), but I got the same results.
lbandrades said:
I had the "magic value mismatch" problem after using an incorrect ClockworkMod version (with ROM Manager). So I used nvflash, as described in the thread "nvflash FULL restore, using bekit's original image".
After that, first boot was OK, back to original firmware. So I put ClockworkMod v08 (cwmod_internal.zip) into internal memory and shut the tablet down.
I could never power it up again after that.
I tried power button and volume +, power button and volume -. No signs of life.
I opened the case and hold the reset button on the back. Nothing. I even tried disconnecting the battery cable.
I can't find a way to power it back up.
Any ideas?
PS.: If I connect it to the charger, the LED turns red (as expected), but I got the same results.
Click to expand...
Click to collapse
wait a few and see if the battery can drain then charge it back up... try nvflash mode again if possible. there were two images of nvflash. i had to first flash the non bekit one, THEN after flash ove the bekit one before it worked....
Related
Hi
After being on numerous custom Roms for the xoom I decided to return to stock and was succesful in return to the 3.01 stock image for the wifi MZ604 model
I was also successful in relocking the xoom.
I then began to receive the offical updates though everytime the were applied I had to go into recovery and wipe the device as otherwise it would bootloop on the dual core screen.
On the last update that it received and that was installed , on rebooting nothing happend and the screen just went blank
No combination of volume up + power would show any sign of doing anything.
After leaving the tablet to the side for awhile I noticed it came up with the following
model mz604 : Revision0 (0x8000) modem none
InitBl Info function failed with codes 299/3
failed to boot 0x0001
starting RSD mode 3
one wire : charger is not connected or battery is not being charged
battery charge level : 56%
I tried fastbooting and adb at this point but no devices are found. However when plugging in the xoom my laptop recognises something is attached.
After some searching I found out about RSd lite and SBF files.
When opening rsdlite v5.6 (running as admin) the tablet is recognised and I have now attempted to use two sbf files
HUBWF_W5.H.6.4-20_SIGNED_UCAHUBLWFRTCOREEU_P010_A010_M004_HWwifi_hubble_AP1FF.sb f
and
HUBWF_W5.H.6.2-24_SIGNED_UCAHUBLWFRTCOREEU_P006_A006_M003_HWwifi_hubble_Service1 FF.sbf
however both fail when it attempts re numeration.
I would greatly appreciate any help that anyone could give on this
Thanks
Try this.
My mom's Xoom had a similar problem. Reboot the tablet by pressing Volume Up and Power.
Then quickly turn on the xoom and press the down button as fast as possible, and continue pressing until you see "Recovery Mode" (or something similar) on the top left of the screen.
Once you see that, press the volume up button. Quickly, when you see the Android guy with the exclamation mark tap the power button and the up button.
This will take you to recovery mode. In there use the up and down volume keys to navigate and the power button to confirm things.
Go down to restore/delete data (may vary) and press power. use the volume down key to scroll to Yes.
This will restore your tablet back to factory settings. If you're trying to backup your data, don't try... No such luck and you won't be able to without the tablet booted.
thanks for the reply but this didnt work. Tried quite a few times. The screen just goes blank and again after a long while the error shown in the op appears. Should add there is no Motorola logo showing.
I have also tried forcing fastboot by the instructions found in other similar threads but again this does not work.
I think my best bet is the SBF files , but need to understand why this is failing on re-numeration
I have flashed the CWM from TF201 by accident. Now the tablet is stuck in that CWM mode. I can't connect to usb using adb mode. Power+volume down does not work anymore. Any way I can reflash the correct CWM?
THanks
If you can boot to OS - you can use fastboot to flash any recovery.. or flash TWRP from goomanager.
upd: sry..don't see about "stuck".
abe_cedar said:
I have flashed the CWM from TF201 by accident. Now the tablet is stuck in that CWM mode. I can't connect to usb using adb mode. Power+volume down does not work anymore. Any way I can reflash the correct CWM?
THanks
Click to expand...
Click to collapse
I have made the same mistake. Although I can get the device to fastboot USB mode. I have tried to use CWM with the restore I made before I put in Cyanogenmod 9, as well as putting on the Cyanogenmod experimental #2 for TF300. No error messages at all and it wipes data and cash without any problems.
But I get locked on the Asus boot screen and it does not continue ie I am stuck as well.
I have as well tried to use the TWRP 2.1.5. I get the Teamwin loggo screen, it wipes all the data and verifies all the filesystems and reboots. Still stuck.
Is the device bricked ?
upd:The TF300 can not be shutoff either. When you hold the power button the screen goes black, but after ~5 s the device is starting again and is still stuck on the Asus bootup screen.
if you reboot it holding vol down and power, can you get back into the boot menu, to reselect fastboot?
if holding the power button doesn't switch it off, what happens if you leave it to run out of batteries then do this?
then you can flash the correct recovery.img
cheedear said:
if you reboot it holding vol down and power, can you get back into the boot menu, to reselect fastboot?
if holding the power button doesn't switch it off, what happens if you leave it to run out of batteries then do this?
then you can flash the correct recovery.img
Click to expand...
Click to collapse
Yes, I can get access to the fastboot and I have already tried to flash with the recovery.img. I have as well let the battery run out and tried it once more with the same result.
Still stuck on the asus bootup screen.
power
Hare,
I have same problem.tab cannot power off. Just reboots into cwm.
I was thinking to drain bat. Thanks for sharing that info.
There are a lot of topics about people who broke their devices with TF201's recovery.
Afaik, no one recovered it. Send to Asus.
So the device is bricked then :'(.
Thanks for clearing it up.
Sent from my GT-I9100 using XDA
RMA..
Guillaume,
Thanks for clarification.
I have read that ASUS wants 700USD for replacing/reflashing the bootloader. That was for the tf201. Any way to nvflash it back to factory? I don't believe that they have to change the MB.
I have no warranty left, but I don't want to be gouged by them either.
Any thoughts, info?
Hi,
I've do the same mistake, but I can use adb.
Do youhave any news about our problem?
Thanks
Midyr
unable to power off
My issue is that I have the CWM for the tf201. I did the update from the CWM app in Android. Bad idea. So now the tab does not power off s.t. I can get into the power+vol down mode. Adb does not work since I cannot ( don't know how) to make it go into the usb debugging mode. I have tried several things none of which have worked. Still stuck.
I wanted some feedback for a RMA from ASUS, posted it here but sor far no answers.
Not sure if it would really work, but on my Evo, I don't have to completely power off the phone to do the recovery sequence. I can do it during a normal reboot. There is a point just before the device starts booting again where it is technically "off", and if I hold volume down (don't even have to hold power on my Evo; volume down seems to be the only necessary button) starting at this point, the phone will boot into the bootloader.
So, next time the device reboots, just start holding volume down (possibly power also, just in case) at the "off" point.
i have a Galaxy Tab 2 7.0 p3113.
i used heimdall to flash CWM into the tablet.
after what seemed like a succesful flash, my tablet rebooted. but for some reason, it would only go as far as showing the galaxy tab logo. it seems stuck there. i could not turn the unit off. i would hold the power button to force shutdown, but it always starts right back up. it seemed like i could only shut it down if it was connected to my mac while holding down the power button. i can however, boot into download mode.
after consulting google, it seems like the appropriate step was to restore the unit to stock. problem is, i can't seem to boot into recovery. i'm being told by the internet that to boot into recovery, i need to hold [power] and [volume down] until it turns on and then release [power] but keep on holding [volume down] and CWM will load. but nothing happens.
i know this is a total noob post, but i've been scouring the web for two days. i'm at my wits end. any help would be greatly appreciated.
I think recovery mode accessed via volume up+power if you could not so use download mode to flash stock or so to return to normal operation
Sent from my GT-I9100 using xda app-developers app
I press the power and UP ( button next to the power button) I normally hold BOTH buttons down at once and let the boot cycle process twice just to make sure i am going into recovery .....so i see the white samsung text twice i mean. It may take around 10 seconds to complete the process. Then release BOTH keys at once.
The battery needs a good charge for it to work.. Try charging over night before you try it via the mains supply.
Holding the power button and down will bring you into download mode and thats what you use for an odin/heimdall flash.
Hope that works for you
Let us know how you get on .....
Thanks. The battery of the gtab2 drained overnight, so i've got it charging back up now. Will definitely post my results when i have something.
Thank you guys. I'm able to boot into recovery now.
But unfortunately, i still need a little guidance on my original problem. And that problem being that my gtab2 will not startup. After rebooting, it gets stuck on the logo screen. It also plays a startup audio clip. But after that, it just displays the startup logo screen. It does not go into the animation screen and start.
I should also mention that when i plug my gtab2 into my computer, no drives show up.
My question now is, if i were to select [wipe data/factory reset] in CWM, would this restore my gtab2 to it's original factory state? Or would I need to flash a ROM for this? And if i need to flash a ROM, could i place a ROM on a microsd card and flash from there?
*********UPDATE*************
Everything is fine (so far).
I went poking around CWM and realized that I had put a cyanogenmod 9 update.zip in the root of the internal sd card before all this happened. So i went back to cyanogenmods wiki on how to install it on my gtab2 and followed the rest of the instructions on flashing it and VOILA!! I have my gtab2 back.
you should use ODIN instead CWM.
CWM is not designed specifically for Gtab2.
Ok. I bought this Galaxy Tab 2 7.0 from a friend for cheap because I thought I could fix it, but I'm running out of options. It's in a boot loop, but an abnormal boot loop. If it's unplugged, It will do the splash screen (Samsung) boot loop. If it's plugged in, either into the wall or into my computer via usb, it will do a battery (charging) boot loop. It's kinda weird. I used to have an Epic 4G and it happened damn near all the time, without the battery loop, but it would charge normally.
I haven't successfully gotten it to boot into Download mode.
If any of you have come across this issue, please feel free to help me out.
I also attached a picture of me attempting to put it in download mode. It reboots if I hit either VOL up or VOL down.
Thanks
extasy88 said:
Ok. I bought this Galaxy Tab 2 7.0 from a friend for cheap because I thought I could fix it, but I'm running out of options. It's in a boot loop, but an abnormal boot loop. If it's unplugged, It will do the splash screen (Samsung) boot loop. If it's plugged in, either into the wall or into my computer via usb, it will do a battery (charging) boot loop. It's kinda weird. I used to have an Epic 4G and it happened damn near all the time, without the battery loop, but it would charge normally.
I haven't successfully gotten it to boot into Download mode.
If any of you have come across this issue, please feel free to help me out.
I also attached a picture of me attempting to put it in download mode. It reboots if I hit either VOL up or VOL down.
Thanks
Click to expand...
Click to collapse
Can you get into recovery? Also, have you tried unplugging the charging cable and getting into download mode with the cable unplugged?
I'm not sure how to get into recovery. With it unplugged, all I have to do hold the VOL Down physical button and ti will take me to a "are you sure you want to put the device into download mode screen". I apologize. I'm not to familiar with this device.
Edit: After I get to the screen where it asks me if i want to go into download mode, it reboots within 5-10 seconds, no matter which button I press
extasy88 said:
I'm not sure how to get into recovery. With it unplugged, all I have to do hold the VOL Down physical button and ti will take me to a "are you sure you want to put the device into download mode screen". I apologize. I'm not to familiar with this device.
Click to expand...
Click to collapse
Hold power and Volume up (volume button closest to the power button) until the tab shuts off and reboots itself and then you can let go of both buttons. If it works, try doing a factory reset. Was this tablet rooted (or have a custom rom installed) in the past?
p3113owner said:
Hold power and Volkume up (volume button closest to the power button) until the tab shuts off and reboots itself and then you can let go of both buttons. If it works, try doing a factory reset. Was this tablet rooted (or have a custom rom installed) in the past?
Click to expand...
Click to collapse
As far as I know it's been on Stock. My GTab ignores me holding the Power and Volume up keys at the same time and keeps the boot loop going strong.
extasy88 said:
As far as I know it's been on Stock. My GTab ignores me holding the Power and Volume up keys at the same time and keeps the boot loop going strong.
Click to expand...
Click to collapse
Then I guess you can (and need) to send it in for warranty service (or replacement).
p3113owner said:
Then I guess you can (and need) to send it in for warranty service (or replacement).
Click to expand...
Click to collapse
No, his device is fine.
If your device bricked, but still showing Gtab2 logo on it, it's still fine. You need to flash to stock 4.03 rom via ODIN. (Not clockworkmod)
Warranty won't work if you have flashed custom ROM before.
Rotundjere said:
No, his device is fine.
If your device bricked, but still showing Gtab2 logo on it, it's still fine. You need to flash to stock 4.03 rom via ODIN. (Not clockworkmod)
Warranty won't work if you have flashed custom ROM before.
Click to expand...
Click to collapse
He needs to be able to get into Download Mode to use Odin. He stated that he can't. When he tried to continue into download mode by pressing volume up (vol. button closes to power button) the tablet reboots. It needs warranty service.
Experiments:
Power off the tab completely and charge completely and press power +volume up for 10 seconds then release, also try to power off and press power+ volume down for 10 seconds then release do you see any screens
If it says do you want to enter download mode or so press volume up and see if you could see (downloading) try also the same with volume down instead of up
Try to connect to computer do you see any messages indicating connections
Also try to connect to kies and try restore or recover firmware from options of kies
You said it reboots after 5 to 10 seconds so try to open odin and try to go to download mode and when you press volume up try as quickly as possible to connect tab to pc while odin is open
Sent from my GT-P5100 using xda app-developers app
p3113owner said:
He needs to be able to get into Download Mode to use Odin. He stated that he can't. When he tried to continue into download mode by pressing volume up (vol. button closes to power button) the tablet reboots. It needs warranty service.
Click to expand...
Click to collapse
There's other method by using OpenRecovery (OR), by putting OR on external SdCard,
but it seems the OR for Gtab2 is not developed yet -__-
So, been running CM10 for a long time on tab. Decided to go back to stock, and downloaded the JB stock rom. Flashed via ODIN. Everything seemed to go OK, except that after the flash the screen went black for ages, and didn't reboot. So I hard powered it off. Probably what did it, but it wasn't going anywhere for about 15 minutes, so figured it was the next step.
Now, I get the battery charging icon. The system goes through the Galaxy Tab 2 7.0 white logo, the swirling then glowing Samsung logo, and then loops through that forever.
It wouldn't be such a problem if I could back into ODIN and do another flash, but I can't get into download mode (normally I do it via adb but that isn't working since there is no USB connection at all). Tried all combinations, power/up, power/down etc. It just boot loops as above. I'm pretty sure I bricked it, but just wanted some confirmation.
Been doing this on and off for a long time, and it's the first time I've ever got stuck like this.
Thanks in advance.
Plug USB charger, your device will boot into charge mode. From charge mode you can boot into recovery by keep holding VOLUME UP button and than press POWER button. Clear data and cache in recovery, reboot.
ketut.kumajaya said:
Plug USB charger, your device will boot into charge mode. From charge mode you can boot into recovery by keep holding VOLUME UP button and than press POWER button. Clear data and cache in recovery, reboot.
Click to expand...
Click to collapse
Thanks, but I tried all combinations of Power/Volume UP and Power/Volume DOWN, it just goes through a normal boot cycle until it starts looping.
I guess it's possible I'm not using the right timing. I'm assuming that you hold Volume UP or DOWN and then press and hold Power until the screen goes black, and then release? I've done it like that many times, and also continued to hold everything down as the logo appears, and then system goes back to the battery charging icon as if it powers off again. I sound like such a noob when I type stuff like that!
I saw ODIN successfully write system.img, boot.img, and recovery.img, so I'm thinking any CWM recovery I had on there is toast.
sl0ttedpig said:
Thanks, but I tried all combinations of Power/Volume UP and Power/Volume DOWN, it just goes through a normal boot cycle until it starts looping.
I guess it's possible I'm not using the right timing. I'm assuming that you hold Volume UP or DOWN and then press and hold Power until the screen goes black, and then release? I've done it like that many times, and also continued to hold everything down as the logo appears, and then system goes back to the battery charging icon as if it powers off again. I sound like such a noob when I type stuff like that!
I saw ODIN successfully write system.img, boot.img, and recovery.img, so I'm thinking any CWM recovery I had on there is toast.
Click to expand...
Click to collapse
You must pull usb cable before start.
You can try to re-flash.
tuxafgmur said:
You must pull usb cable before start.
You can try to re-flash.
Click to expand...
Click to collapse
Well, don't I feel like the idiot!
How did I not think to disconnect the USB before trying this? tuxafgmur, your first "Thanks" has been registered, I've got it from here!
P.S. Welcome to the forum!
it sounds strange. never heard of such a strange boot problem. anyway it could be that while transferring boot.img it became damaged due to some error. i know you probably tryed but you may try and connect it to linux or mac os x in order to check if you could retrive more data about the tab. for example the mac could find if it is totally corrupted. normally when i plug my samsung devices it ask me to add the samsung-modem also if they are turned off. meybe if it happens the same to you you can try to adb fastboot it also if i doubt myself about it working, but give it a shot
i hope my bad english is not preventing you to understand what i'm saying!
give us new feedback!