I'm using [ROM]MIUI/CM7 Hybrid v3 multi-lang update 04/07/2012 and haven't had any issues whatsoever. Tonight I updated a bunch of Play Store apps that I've been putting off for a while and the only one that I could think of that could possibly have caused a problem is MiHome. Everything else was a pretty standard app/game.
Well my phone rebooted and now after it boots and shows the lock screen it goes blank a few seconds later. I tried unlocking it before it went blank and and I did see the home screen but it went blank again before the icons showed up. I can tell it's still on because there is a very slight glow from the screen if you look at it from an angle.
PLEASE HELP ME. I have no idea how to fix this and wouldn't even know where to begin!!
You've flashed a ROM before, you should know this already... Reboot into recovery, do a wipe data/cache (factory reset), reboot. If that doesn't work then wipe all and re-flash the ROM+gapps.
If you've been messing with system files, it's probably best to go straight to wipe all and re-flashing.
Re-install apps, re-configure the dozen or so apps you actually use on a normal day-to-day basis, and set a lovely wallpaper when you're done. 1 hour tops.
At the very least you'll be available for phone calls and text messages again within the next 10min.
Next time make sure to do a backup so you can restore a working copy of your data and cache whenever you need.
Unless you already know what the issue is, or how to fix it, sorry to say it, but the above steps are likely the quickest way to a resolution.
You're right I am very familiar with those steps but I can't reboot into recovery or any other method. My screen is blank and everything is unresponsive. The only way I can reboot is to pull the battery. I do remember there is a way to boot into recovery from a power off status but I can't remember how to do that.
BTW...thank you for your quick reply!
loanerdave said:
You're right I am very familiar with those steps but I can't reboot into recovery or any other method. My screen is blank and everything is unresponsive. The only way I can reboot is to pull the battery. I do remember there is a way to boot into recovery from a power off status but I can't remember how to do that.
BTW...thank you for your quick reply!
Click to expand...
Click to collapse
Hold down the volume-down key while booting up, when you see the Fastboot option appear, press the volume-down key repeatedly to cycle through the selections until you get to Android Recovery, then volume-up to select.
Try this:
- remove the battery
- press Volume Down and hold
- insert the battery (tricky part when holding Volume Down)
- wait till system menu appears
- release Volume Down
- press Volume Down again few times till "Recovery" shown.
- press Power
Thank you guys (or girls)! That's what I couldn't remember. Wiping now and will reinstall ROM.
Related
I had installed TNT Lite v 4.3.0 a couple of weeks ago and it was working pretty good. But today my tablet has gone into a bad state. Every app that I run results in FC. Even the ADW launcher EX that I had selected default is crashing. It then gives me the options: ADW Laucher, ADW Launcher EX, and the regular Launcher. The plain ADW Launcher also fails, but fortunately the regular Launcher still works so I can access the apps.
But unfortunately almost every app that I am trying fails. The only one that doesn't fail is the Web browser. The Settings starts and I can access Applications menu but once I choose say System Applications, after that if I try to choose some other option such as Installed Application, it crashes as well.
Last night however when I started the tablet the battery was probably down and while it was powering it up, it turned off and then restarted by itself and then turned off, without reaching the lock screen. I don't know if it has something to do with all this.
What do I do now? Any help will be appreciated.
Thanks.
A well known issue.
http://forum.xda-developers.com/showthread.php?t=896395
This is why I'm an advocate of people doing the partitioning right before they flash their first custom rom. This way, they won't have to wipe everything later on.
I could only wonder why people aren't mentioning this in every custom rom thread.
Thank you so much. Will try it out tonight.
Unfortunately it seems I have run into a worse issue (without even doing anything yet). Now when I power it on, it starts and shuts off within a few seconds, just shows the birds for like 5 secs and bang, black screen.
The tablet is fully charged (if I put it on charge the light turns green in no time). Looks like the battery is dead.
You might be dropping into APX mode. Do you know how to use nvflash?
Thanks for the reply. You are absolutely right. After multiple tries it did boot up and I was able to install clockworkmod and it all worked great. It wiped off everything but I could live with that. And I turned it off and back on and it was working fine.
But then it went back into the same mode - shutting off immediately after turning on. I decided to return this tablet thinking that it is bad. But before I would do that I thought to restore it or else Viewsonic won't honor the warranty. So I started reading the thread about restoring the tablet to stock using nvram flash. In that procedure it requires me to put the tablet in APX mode and that's when I thought that maybe it is going into APX without pressing the volume - button.
Anyway I was successfully able to flash nvram. Or so it said. I still have the output from the batch file. But now my tablet is totally bricked. It does not boot at all. No pretty birds for me.
I hope there is some way out of it. Please help.
Edit: After re-flashing and using a different file, it seems to have made it a little better. At least I am seeing the birds again. But the original problem of shutting off, or going into the APX mode without pressing Volume button, has returned. All I am getting is the birds for a few seconds and then black screen. I will continue to retry, and if I see it booting up successfully to the stock, this thing is going back to the factory.
1) What image did you use to nvflash?
2) What happened when the flash was finished? Did it boot normally at least once?
3) Does the screen just stay dark all the time now?
1) First time nvflash_gtablet_46_2010112600.zip and after that it did not boot at all. Only black screen. I flashed it couple of times, no avail. Later I flashed nvflash_gtablet_2010110500.zip. This at least recovered it enough that it shows the birds, but soon after the screen turns black. I have confirmed that it is going in APX mode. If I have USB cable connected to my PC, the PC reports discovering the NVIDEA APX device.
2) It hasn't booted normally since I flashed nvram.
3) No I get the birds, but after that it turns dark.
Ok. Using Bekit's 1105 image...
1) Replace part9.img with the recovery.img out of the clockworkmod installation zip.
2) Put the tablet into APX mode.
3) Type in the command to start nvflash but before you hit the enter key hold down the Volume Up key and continue to hold it down until the flash finishes.
4) The tablet should boot into clockworkmod recovery.
5) Repartition 2048 and 0
6) Clear everything (cache, data and dalvik)
7) You might need to re-nvflash at this point.
Thanks for your response. I tried it. Did not work. When you say Replace part9.img with the recovery.img, does it mean copy recovery.img into the NVFlash directory and rename it to part9.img or leave it as recevery.img. I renamed it to part9.img and backed up the original part9.img to part9.img.tmp. The size of recovery.img and the original part9.img are very different. I am confused. Please help.
K J Rad said:
Ok. Using Bekit's 1105 image...
1) Replace part9.img with the recovery.img out of the clockworkmod installation zip.
2) Put the tablet into APX mode.
3) Type in the command to start nvflash but before you hit the enter key hold down the Volume Up key and continue to hold it down until the flash finishes.
4) The tablet should boot into clockworkmod recovery.
5) Repartition 2048 and 0
6) Clear everything (cache, data and dalvik)
7) You might need to re-nvflash at this point.
Click to expand...
Click to collapse
Yes, that is exactly what I meant.
Are you sure you're holding the volume UP key? Birds and then black screen is APX mode which is normally entered by holding volume DOWN.
Well it goes into APX mode even if I don't press any Volume button at all. That is the problem I am trying to fix. When I press power button (without touching the volume button) the birds come and then black screen. And this is APX mode because if I am connected to the PC it brings up an NVIDIA APX device on the PC.
Now if I press the Volume UP button along with the power button, nothing happens, not even the birds come up.
So the fact that the recovery.img (3.7k) is much smaller than part9.img (16k) is ok? Or I am doing something wrong.
Any ideas?
I was thinking about formatting the gtablet. Please let me know if this is the right move, or there is something else I could try first.
shah123 said:
Well it goes into APX mode even if I don't press any Volume button at all. That is the problem I am trying to fix. When I press power button (without touching the volume button) the birds come and then black screen. And this is APX mode because if I am connected to the PC it brings up an NVIDIA APX device on the PC.
Now if I press the Volume UP button along with the power button, nothing happens, not even the birds come up.
So the fact that the recovery.img (3.7k) is much smaller than part9.img (16k) is ok? Or I am doing something wrong.
Click to expand...
Click to collapse
A little more than "It did not work" would be helpful.
What step failed? Please tell me what happened after each step.
Did you get into CWM and repartition?
Did you get everything cleared?
What happened when it rebooted?
What was the original filename of the image you tried to flash?
What version of clockworkmod do you have installed?
Have you ever used ROM Manager?
All of this is important and no one can help you if you don't provide enough information.
Oh, I am sorry. Here are the answers to the questions you asked:
What step failed? Please tell me what happened after each step.
Ans: Out of the 7 steps you provided, the steps 1, 2 and 3 worked fine. It is the step 4 that failed (and of course I can't proceed with the steps anymore). In other words I cannot go into clockworkmod recovery.
Did you get into CWM and repartition?
Ans: No I was not able to do so. If I press power and Volume Up key at the same time, nothing happens, screen remains black, not even birds come up.
Did you get everything cleared?
Ans: I believe you are referring to step 6. No, I could not get to that step.
What happened when it rebooted?
Ans: Nothing showed up. Because when Volume Up is pressed while it is powered on, nothing shows up on the screen.
What was the original filename of the image you tried to flash?
Ans: Actually first time nvflash_gtablet_46_2010112600.zip (and this is before you provided the 7-step recipe - see post #6, 7, 8 of this thread) and after that it did not boot at all. Only black screen. I flashed it couple of times, no avail. Maybe that was my mistake. I chose a wrong file. Later I flashed nvflash_gtablet_2010110500.zip. This recovered it enough that it shows the birds now, but soon after the screen turns black (goes into APX mode).
What version of clockworkmod do you have installed?
Ans: v08
Have you ever used ROM Manager?
Ans: No. What is it?
I really appreciate your help.
What happened at the end of step 3?
Did you start holding the volume UP before you pressed the return key for the nvflash? If not... go back and do it again.
Did you continue to hold it until the flash was happening? You must continue to hold it down for at least 5 - 10 seconds after the flash starts.
When the flash was done did it say "Recovery Key detected" on the screen? If it didn't say this that is an indication that you didn't hold the volume UP key long enough.
If all of the above was done correctly and did happen but you didn't get to clockworkmod then what did you get? Did it look like stock recovery?
It sounds to me like you did the nvflash then tried to reboot into recovery.
Its unbelievable. Tonight when I powered it on it started booting up normal instead of going into the APX mode. I was glad. The stock UI came up, but some of my apps like Quadrant, File Expert etc were still there. It also notified me of the Update 3588. So I downloaded it and started installing it. Pretty soon it rebooted itself (sooner than I thought - I don't know if the remaining installation was supposed to happen after the reboot).
But instead of booting up into 3588 it is unfortunately gone back to the same old issue - the birds followed by black screen - aka APX mode. It never booted up after that. No matter how many times I tried to reboot, it goes into APX mode just like before. I don't know what caused it to complete bootup. One thing I noticed was that the battery was totally drained when I started tonight. I don't know if the drained battery somehow took it out of the APX mode. But now it has a little bit of charge because of hooking up to power supply. I have disconnected the power supply and will leave it in APX mode over night and try it again tomorrow when the battery would be totally drained and see if it boots up fully.
To answer your questions though:
What happened at the end of step 3?
The screen went black and after that it stayed black. No CWM.
Did you start holding the volume UP before you pressed the return key for the nvflash? If not... go back and do it again.
Yes, I did.
Did you continue to hold it until the flash was happening? You must continue to hold it down for at least 5 - 10 secondsafter the flash starts.
Yes, I continued to hold it all the way until the flash completed and the screen went black and quite some time after that.
When the flash was done did it say "Recovery Key detected" on the screen?
I don't think it did.
If it didn't say this that is an indication that you didn't hold the volume UP key long enough.
So I guess I need to give it another try. Tomorrow I will try to reboot the tablet again and if it continued to go into APX I will do the nvflash one more time.
If all of the above was done correctly and did happen but you didn't get to clockworkmod then what did you get? Did it look like stock recovery?
A black dark screen. No CWM or stock recovery.
It sounds to me like you did the nvflash then tried to reboot into recovery.
No at the time of nvflash I held the Volume UP button and nothing happened. Since then I have been trying to bootup or put it in CWM Recovery but only thing the tablet wants to do is go into APX mode.
So I guess my theory of "drained battery takes it out of the APX mode" is correct. I tried to reboot the tablet several times but it just kept on going into the APX mode until the battery was completely drained. And then it started booting up normally but it went into some installation (probably the stock 3588 that I had downloaded in the previous successful bootup). And then the green android with the exclamation sign came and the exclamation sign was rotating for a second or two and then stopped. And it looked like it was hung. I waited for a minute or two but nothing happened, so I pressed one of the buttons, I don't know if it was Menu or Back button, and all of a sudden clockworkmod recovery screen came up.
I have attached the picture of the screen. It still shows the green android with the exclamation sign in the middle of the screen, along with the CWM Recovery.
One other thing I noticed and I am not sure if it is normal is that if I choose say Reboot System Now from CWM menu and it shows like 10 entries with many No's and only one Yes. I can only use the volume Up + button to go down, if I try to go up using volume Down - button it does not go up. Is that normal? Is the only way to go is go down using Voume Up button in CWM menus? I have a feeling that my Volume Down button has gone crazy and it is not functioning properly and that is what is causing it to go into APX mode at the startup as well.
Anyway I first attempted "Apply SDCARD:update.zip" hoping that it might continue with the stock 3588 installation, but that failed. You can see the messages in the picture. Then I tried the Factory Reset and it was successful. I then rebooted the tablet. But now again it keeps on going up into APX mode. I will have to wait until tomorrow for it to completely drain battery again and then try to reboot again.
Any ideas? I know it is overwhelming and the behavior is very weird. At this point I am trying to bring it back to the stock firmware so that I can get this tablet replaced under warranty.
There are quite a few things that are not acting normal from what I see here.
Did you try to repartition 2048 and 0? If not, I would start with that then I would format everything and re-nvflash a stock ROM onto it. That might clear things up. If not you could be looking at a hardware reset.
Recently i flashed the CM9 rom onto my Droid X2. Followed the instructions and everything installed correctly. Since it has been a couple of days and I have installed all my programs and got everything where i wanted it, i wanted to make a backup.
Soon i discovered that I didnt have System Recovery installed. SO i began looking into my SD card and i have two files,MOTODX2_Bootstrap_signed.apk. So i decided to install it, everything went fine but now my phone is stuck in a boot loop. It wont even boot into CM9.
Is there another BSR that i should be flashing instead of this one. Maybe the ReRecovery one? i know theres a [patched] BSR to install but i gave me the same problems.
Thanks EHB
Hi, for Cyanogenmod9 use the CM7 PATCHED BSR. It works just fine for me everyday. I'm kind of addicted to flashing ROMs for some reason and usually am on different ones multiple times a day. Always in BSR either restoring or backing up. The patched BSR for CM7 works just fine for me. For reference, in the app drawer it should say "CM7 System Recovery" not just System Recovery.
I'm not sure if it has been looked into by dev's yet or not, but the day CM9 was released I actually did flash the CM7 ReRecovery zip and I was able to boot to BSR from a powered off state just by plugging in. I wasn't sure if it was okay to use, so I installed a fresh CM9 without it. I don't know if this is 100% safe or if there would be any issues from using the ReRecovery zip. I would recommend just installing the patched CM7 apk and trying to use that.
Here's the link to the patched CM7 Recovery. Pulled straight from the CM7 thread
http://www.mediafire.com/?pzz4413k6wggcao
***^That BSR is an application. You download, install and run it on your phone. The ReRecovery is a flashable zip you can install once already inside of BSR allowing you to get into custom recovery say for example, if you're boot looping. ***
================================================
If you're still having bootloop issues, try this;
-Grab your ECOMOTO charger, plug into A/C power, pull battery, replace & plug into wall.
- Wait for the Motorola logo to disappear and the battery charging icon to appear (this can take several minutes)
-When you see the battery charging icon, unplug your phone and pull your battery.
-Reinstall the battery and hold the VOLUME DOWN key while powering on the device. Release the VOLUME DOWN button when it turns on.
You should now see "FASTBOOT" in white text above the Motorola logo.
-Press the volume down key several times until you see ANDROID RECOVERY.
-With ANDROID RECOVERY now showing where fasboot was, press the VOLUME UP button. It will tell you that it is starting android recovery mode.
This will take you to a screen that shows a picture of an android next to a triangle with an exclamation mark (!) inside of it.
-From that screen press both the VOLUME UP and VOLUME DOWN keys at the same time.
If you made it this far, you're now in the stock android recovery. Using the volume buttons, key down to Wipe Cache Partition then press the power button to select. You will be taken to a confirmation screen. Key down and select Yes. Wait for it to complete. After you wipe the cache try rebooting back into CM9. This will take slightly longer than usual as your cache has to rebuild itself. If you can boot back up successfully, click the link above. Download the patched CM7 Bootstrap Recovery and install it. If you don't know what to do from there, open the application "CM7 System Recovery" and click "Install Recovery" -- You will now be prompted to grant or deny it superuser permissions. Allow them. You will receive a message saying the install was a success! Click OK. Now plug your phone back into the wall outlet and hit "Recovery Mode" and your phone will boot into BSR! From there just go to backup and save it to your external SD card. You can find your backups later via the file explorer of your choice under /mnt/sdcard/clockworkmod/backup. Note: You can rename the file so you know which ROM is which, just don't add spaces to the file name or it will ruin your backup and you will not be able to restore it. NO SPACES!!!
FYI you will still see the Motorola logo immediately after it turns back on. It takes a minute or two to boot into custom recovery.
I've been through a lot of trial and error with the X2 and these steps have helped me plenty of times. Hopefully they do the same for you....Good luck.
Cyanogenmod all day
Thanks for the information.
I knew basically everything you said except for the "wipe cache partition". Why is this necessary? I know that it doesn't delete personal information but what does it wipe/delete?
Im going wait to do this tomorrow - my day off. Im just worried that its going do the same thing and ill have to reflash and start all over again.
Thanks again EHB
Wiping the cache partition clears any/all application data and common app components. It does not wipe apps themselves, rather the files that the app generates when used.
Wiping it is necessary because when core system components are changed, the resources used by the apps also (could) change. Having stale app data after a system change or tweak can cause problems, which is why it is best to clear it. It gets rebuilt as apps are used.
RoyJ said:
- Wait for the Motorola logo to disappear and the battery charging icon to appear (this can take several minutes)
Click to expand...
Click to collapse
I'm afraid I'm in the same boat and am going through these steps to hopefully get back on the right track. When you say the battery charging icon can take several minutes... are you suggesting 3-5 minutes, or up to 30 minutes? Because... I'm at about 35 minutes right now and am getting pretty nervous.
just skip to this part, if you can
remove charger and battery
-Reinstall the battery and hold the VOLUME DOWN key while powering on the device. Release the VOLUME DOWN button when it turns on.
You should now see "FASTBOOT" in white text above the Motorola logo.
-Press the volume down key several times until you see ANDROID RECOVERY.
-With ANDROID RECOVERY now showing where fasboot was, press the VOLUME UP button. It will tell you that it is starting android recovery mode.
Click to expand...
Click to collapse
Patched BSR, please help!!
RoyJ said:
Hi, for Cyanogenmod9 use the CM7 PATCHED BSR. It works just fine for me everyday. I'm kind of addicted to flashing ROMs for some reason and usually am on different ones multiple times a day. Always in BSR either restoring or backing up. The patched BSR for CM7 works just fine for me. For reference, in the app drawer it should say "CM7 System Recovery" not just System Recovery.
I'm not sure if it has been looked into by dev's yet or not, but the day CM9 was released I actually did flash the CM7 ReRecovery zip and I was able to boot to BSR from a powered off state just by plugging in. I wasn't sure if it was okay to use, so I installed a fresh CM9 without it. I don't know if this is 100% safe or if there would be any issues from using the ReRecovery zip. I would recommend just installing the patched CM7 apk and trying to use that.
***^That BSR is an application. You download, install and run it on your phone. The ReRecovery is a flashable zip you can install once already inside of BSR allowing you to get into custom recovery say for example, if you're boot looping. ***
================================================
If you're still having bootloop issues, try this;
-Grab your ECOMOTO charger, plug into A/C power, pull battery, replace & plug into wall.
- Wait for the Motorola logo to disappear and the battery charging icon to appear (this can take several minutes)
-When you see the battery charging icon, unplug your phone and pull your battery.
-Reinstall the battery and hold the VOLUME DOWN key while powering on the device. Release the VOLUME DOWN button when it turns on.
You should now see "FASTBOOT" in white text above the Motorola logo.
-Press the volume down key several times until you see ANDROID RECOVERY.
-With ANDROID RECOVERY now showing where fasboot was, press the VOLUME UP button. It will tell you that it is starting android recovery mode.
This will take you to a screen that shows a picture of an android next to a triangle with an exclamation mark (!) inside of it.
-From that screen press both the VOLUME UP and VOLUME DOWN keys at the same time.
If you made it this far, you're now in the stock android recovery. Using the volume buttons, key down to Wipe Cache Partition then press the power button to select. You will be taken to a confirmation screen. Key down and select Yes. Wait for it to complete. After you wipe the cache try rebooting back into CM9. This will take slightly longer than usual as your cache has to rebuild itself. If you can boot back up successfully, click the link above. Download the patched CM7 Bootstrap Recovery and install it. If you don't know what to do from there, open the application "CM7 System Recovery" and click "Install Recovery" -- You will now be prompted to grant or deny it superuser permissions. Allow them. You will receive a message saying the install was a success! Click OK. Now plug your phone back into the wall outlet and hit "Recovery Mode" and your phone will boot into BSR! From there just go to backup and save it to your external SD card. You can find your backups later via the file explorer of your choice under /mnt/sdcard/clockworkmod/backup. Note: You can rename the file so you know which ROM is which, just don't add spaces to the file name or it will ruin your backup and you will not be able to restore it. NO SPACES!!!
FYI you will still see the Motorola logo immediately after it turns back on. It takes a minute or two to boot into custom recovery.
I've been through a lot of trial and error with the X2 and these steps have helped me plenty of times. Hopefully they do the same for you....Good luck.
Cyanogenmod all day
Click to expand...
Click to collapse
I am having a similar but different problem with the patched BSR. I had it running fine while using CM9 on my Droid X2, but now I am running MIUI, and when I install and attempt to get into the custom recovery, it seems like it attempts to load it, but does not. What I get is a jumbled screen that has the colors of the custom recovery, so I can tell it is attempting to come up, but something is going wrong. It shows that jumbled screen for a few seconds, then goes black and eventually just shuts down. I have tried EVERYTHING I can think of to fix this. I have tried a fresh download of the patched BSR, and even did a fresh SBF and reinstall of MIUI, but nothing fixes it. Any advice you have would be greatly appreciated. Thanks!
I would re flash sbf
if you have been using ezSBF
use rsd lite, vise versa, or try a different sbf version like 2.3.3 and take ota update
or see if someone could upload a nandroid backup
Sent from my MB870 using xda premium
The odd thing is, if I restore to CM7 or CM9, then the patched BSR will work again. It seems it only goes bad with MIUI. Could the ROM somehow affect the BSR installation and/or function? I wouldn't think this is the case, as other are using the patched BSR with MIUI without trouble.
Sent from my MB870 using xda app-developers app
I have a T-679. it is only lightly modded. I still have stock UVLE1 with Clockworkmod recovery...v5.5 i think. All has been well until recently I have been trying out a lot of new apps. recently i got the adw launcher and camera sensor. now when i reboot i see one Samsung logo, then tmobile/android logo and jingle, then another Samsung logo and it hangs here. if i wait some time and start pushing buttons I see that the phone seems to be active. if i push the power button then the vol-up/down i hear the sound of the volume being adjusted. also very curiously i just found that if i hold down the home button and press the power button i hear a shutter sound!? In some instances, haven't figured out if its a particular button press of just random, i can get the lock screen to come up, which then allows me to unlock the phone and all works normally... until i reboot again.
any ideas suggestion how to proceed? Thanks.
edit: I just checked I have CWM recovery v5.5.04,b
I have a backup from a while back and i just made another backup
I also tryied wipe cache/dalvik which i thought it helped because i think it booted directly after that, but i just tryed again and
this time i see no benefit/effect
overload1 said:
I have a T-679. it is only lightly modded. I still have stock UVLE1 with Clockworkmod recovery...v5.5 i think. All has been well until recently I have been trying out a lot of new apps. recently i got the adw launcher and camera sensor. now when i reboot i see one Samsung logo, then tmobile/android logo and jingle, then another Samsung logo and it hangs here. if i wait some time and start pushing buttons I see that the phone seems to be active. if i push the power button then the vol-up/down i hear the sound of the volume being adjusted. also very curiously i just found that if i hold down the home button and press the power button i hear a shutter sound!? In some instances, haven't figured out if its a particular button press of just random, i can get the lock screen to come up, which then allows me to unlock the phone and all works normally... until i reboot again.
any ideas suggestion how to proceed? Thanks.
edit: I just checked I have CWM recovery v5.5.04,b
I have a backup from a while back and i just made another backup
I also tryied wipe cache/dalvik which i thought it helped because i think it booted directly after that, but i just tryed again and
this time i see no benefit/effect
Click to expand...
Click to collapse
After wiping everything such as data, cache, dalvik-cache, battery stats in CWM, try restoring the Nandroid backup which you've created. If still, it gives weird issues, fresh install another ROM.
Guys,
I'm rooted, with MDK base, and THOUGHT I had a working version of CWM (maybe 6.0.2.3?)
I was in the process of getting ready to try out a new ROM; going through the usual motions, formatting system, data, cache, and for good measure, I finished with a Wipe Data/Factory Reset (which I believe just does the same things again).
The phone suddenly rebooted and froze at the samsung custom screen. When I try to get back to recovery, I can't (hold down up-vol and power; blue message appears and disappears quickly in upper left, and back to Samsung custom lock screen.
I'm stuck. In the past, I always got into recovery by rebooting with ROM Manager, so I haven't really had to use the power-on/ vol up method (thus it may never have worked).
I can get into download mode. So I'm thinking - assuming - that the first thing I should try is to Odin CWM. But I'm admittedly confused, because all of the posts that relate to installing CWM seem to be in the context of the rooting process, and assume you have the ability to place certain files in rooted directories (like loki), which I obviously can't b/c I can't boot.
1) Is re-flashing CWM the right approach ? If so, is there a .TAR file somewhere with just CWM? I can't find an Odin-flashable .tar. EDIT: I found one, but it's designated for i9505. Same thing?
2) If that's not the right approach (or I'm just an idiot and don't know how to get into a working recovery), please advise
Thanks!
Turn the phone off.
Hold volume up and press the power button until it vibrates.
When it vibrates let go of the power and stay holding volume up until you see the recovery splash.
I've found that sometimes continuing to hold the power button will cancel the call for recovery boot. Not sure why.
You can always Odin if that doesn't work.
And I don't know of an Odin package for vzw recovery.
sent from my GE gs4
Dubbsy said:
Turn the phone off.
Hold volume up and press the power button until it vibrates.
When it vibrates let go of the power and stay holding volume up until you see the recovery splash.
Click to expand...
Click to collapse
O - M - G !? Unbelievable. Thanks a BILLION! You just saved me a ton of time.
EDIT: Cr*p. Not out of the woods yet. Now, when choosing 'Install from SD Card' I'm getting 'E: Can't mount /sdcard/'
I'll post this issue in a separate Q.
Got the phone with rebooting problem: it got the rebooting after updated. The device restarted during Android app optimization stage so I just unblock with the AT&T stock file (pda-odin-att-stock.tar) after that the phone can boot up fine the problem still. It works but continuing reboot every 2 minutes. I tried to clear the cache, test redbend fota... but nothing works
Anyone has idea?
abbuyacc said:
Got the phone with rebooting problem: it got the rebooting after updated. The device restarted during Android app optimization stage so I just unblock with the AT&T stock file (pda-odin-att-stock.tar) after that the phone can boot up fine the problem still. It works but continuing reboot every 2 minutes. I tried to clear the cache, test redbend fota... but nothing works
Anyone has idea?
Click to expand...
Click to collapse
your English is a little rough my friend
did you get the phone with reboot issue?
or
it started rebooting after an update?
what kind of update?
what rom are you trying to run?
and I don't understand "unblock with the ATT stock file " ?????
also what is "test redbend fota" ???
you need to be a little clearer with information please
captemo said:
your English is a little rough my friend
did you get the phone with reboot issue?
or
it started rebooting after an update?
what kind of update?
what rom are you trying to run?
and I don't understand "unblock with the ATT stock file " ?????
also what is "test redbend fota" ???
you need to be a little clearer with information please
Click to expand...
Click to collapse
First of all sorry about my English. I wish I can do better.
I got the phone with the rebooting and base on the owner of the phone he said it started rebooting after an update.
Not sure what was of update to but the phone I got always rebooting during Android app optimization stage ( when it updating about 90 files or so) but it got reboot when updating to the file of 57th (So it was not actually working)
I watched and followed the youtube (how to unblock/unbrick galaxy i717) which it used the pda-odin-att-stock.tar file with the ODIN3 V1.85 (I guess that original ROM of AT&T (android version 2.3)
After successful unblock/unbrick the phone the phone actual worked but the problem still. It works but only 2 minutes and the phone reboots.
2/ test redbend fota is one the options you can choose after hard booting the phone using both up - down keys and power key (other options are to clear the cache, or wipe the data..)
That actually happened to me while testing out Bean Stalk(which btw AWESOME ROM). It would do a Random Reboot and continuously do that every 2 minutes or so. The way I fixed it was by doing the following steps:
1) Power off your phone. If unable to power off, remove and reinsert the battery.
2 )Press and hold between both Volume keys and the Power key at the same time until the phone vibrates, then release ONLY the Power key.
3)Continue holding the Volume keys until Samsung appears on the screen. Then release both volume keys.
The recovery menu will display.
4) Press Volume down to move to option 3, Wipe data/factory reset, and then press the Home key to accept.
5) Use Volume Up and Volume Down buttons to navigate in the menu and select Yes- Delete all user data.
6)Navigate to highlight OK and press the Home key to select.
7) Select Reboot system now.
PLEASE UNDERSTAND THAT THIS WILL DELETE EVERYTHING INSIDE YOUR SD CARD AS WELL! SO DO A BACKUP BEFORE ERASING EVERYTHING!
hafridi said:
That actually happened to me while testing out Bean Stalk(which btw AWESOME ROM). It would do a Random Reboot and continuously do that every 2 minutes or so. The way I fixed it was by doing the following steps:
1) Power off your phone. If unable to power off, remove and reinsert the battery.
2 )Press and hold between both Volume keys and the Power key at the same time until the phone vibrates, then release ONLY the Power key.
3)Continue holding the Volume keys until Samsung appears on the screen. Then release both volume keys.
The recovery menu will display.
4) Press Volume down to move to option 3, Wipe data/factory reset, and then press the Home key to accept.
5) Use Volume Up and Volume Down buttons to navigate in the menu and select Yes- Delete all user data.
6)Navigate to highlight OK and press the Home key to select.
7) Select Reboot system now.
PLEASE UNDERSTAND THAT THIS WILL DELETE EVERYTHING INSIDE YOUR SD CARD AS WELL! SO DO A BACKUP BEFORE ERASING EVERYTHING!
Click to expand...
Click to collapse
I have done it already and it didn't works. I tried to clear the cache also and other options too but none of them worked.
abbuyacc said:
I have done it already and it didn't works. I tried to clear the cache also and other options too but none of them worked.
Click to expand...
Click to collapse
Could it be a battery issue? I mean if its not software, it might be hardware. Please check if the battery is fine? If you could elaborate the steps you took or the update process you followed, that would be great.
Don't worry we will definitely figure this out, i know how sad it can be when you are without your phone.
hafridi said:
Could it be a battery issue? I mean if its not software, it might be hardware. Please check if the battery is fine? If you could elaborate the steps you took or the update process you followed, that would be great.
Don't worry we will definitely figure this out, i know how sad it can be when you are without your phone.
Click to expand...
Click to collapse
No. Surely it is not about the battery. Battery is full and hold the charge pretty well. As I mentioned I was re-installed the original ROM of the phone and there was nothing much to say about this procedure. After reinstalled the original rom the phone works but the problems is still same (rebooting after 2 minutes), before the the phone didn't work and just was in the updating stage but I guess the time of the updating file was also about 2 minutes.
I believe this is about the software than the hardware issue. I am thinking that I may want to install the newest ROM to see it will work or not but I am in the middle of some works right now and have no time for it. So I am just wait to see if there is anyone had similar issue and follow their instruction. Thank you you all.
I am sure you either have hardware issue or in most circumstances it is a user issue.
Is there any possibility you have not read everything or something you are not understanding?
Those of us responding do so because our methods are tried and true. Nobody else is having this issue.
I just ask is it possible?
Have you confidently tried all suggestions with no shortcuts? Even the smallest deviation can lead to the biggest problems
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Here is a suggestion:
Please go to stock rom. After Odin restarts the phone...do not touch. Let the phone sit there for a little bit. Then if it restarts u might need to format your internal sd card after formatting system, data, cache and then install rom.
I had to flash it
hafridi said:
That actually happened to me while testing out Bean Stalk(which btw AWESOME ROM). It would do a Random Reboot and continuously do that every 2 minutes or so. The way I fixed it was by doing the following steps:
1) Power off your phone. If unable to power off, remove and reinsert the battery.
2 )Press and hold between both Volume keys and the Power key at the same time until the phone vibrates, then release ONLY the Power key.
3)Continue holding the Volume keys until Samsung appears on the screen. Then release both volume keys.
The recovery menu will display.
4) Press Volume down to move to option 3, Wipe data/factory reset, and then press the Home key to accept.
5) Use Volume Up and Volume Down buttons to navigate in the menu and select Yes- Delete all user data.
6)Navigate to highlight OK and press the Home key to select.
7) Select Reboot system now.
PLEASE UNDERSTAND THAT THIS WILL DELETE EVERYTHING INSIDE YOUR SD CARD AS WELL! SO DO A BACKUP BEFORE ERASING EVERYTHING!
Click to expand...
Click to collapse
factory reset did not help me with this...I ended up having to flash CM 10.1. Its the most stable custom I have used on this phone yet....