I am on 2.3.4, and the phone randomly rebooted. But when it got the part after it vibrates, it rebooted back to where it said "droid" and started a never ending loop. I have tried sbfing to 2.3.4 again, but rsd lite sayss I have to manually reboot my phone. I can boot to where it says "fastboot" in white.
Edit: RSD lite now says that the phone has finished sbfing, but the bootloop still persists.
Sometimes you can get stuck in a bootloop after SBF'ing. Two things you could do would be to pull the battery and then just try restarting. Another thing you could do would be to boot into Android Recovery (same way you get into RSD) and just wipe the Data/cache.
Skelente said:
Sometimes you can get stuck in a bootloop after SBF'ing. Two things you could do would be to pull the battery and then just try restarting. Another thing you could do would be to boot into Android Recovery (same way you get into RSD) and just wipe the Data/cache.
Click to expand...
Click to collapse
What happens when I wipe data/cache?
Arbybear said:
What happens when I wipe data/cache?
Click to expand...
Click to collapse
Wiping cache just clears out files used to open/run apps quicker. These files are rebuilt the first time you use the app. This one is no big deal and I wipe mine periodically just to "clean house."
Wiping data doesn't clean house, it remodels it. It sets everything back to factory (like "out of box" after an sbf). You will lose your data, apps, personal settings, etc. It does not touch your sdcard, though.
only way to get out of bootloop after sbf is to go to Android recovery and wipe data
it will put your phone back to what it was when you bought it i.e."out of box condition"
data wipe deleted all user data
I have that problem occasionally as well. I usually go into recovery and wipe cache but not user data, that gets me into the phone, but it will reboot 30 seconds after you get in, so then use BSR to clear Dalvik. If you cannot clear Dalvik you will probably need to wipe the user data, which resets the phone to factory defaults.
Power it up like this:
Hold power and volume down until the phone says FASTBOOT
Once the phone says FASTBOOT, press volume down until you see ANDROID RECOVERY
Once you see ANDROID RECOVERY, press BOTH the volume up and the volume down buttons.
You will see the triangle with the exclamation point and the Android.
At this point press volume up and down simultaneously again and select the cache clearing option by using volume down, then pressing the power button to select. Don't wipe user data just yet. Try to reboot once it is complete (You will see it on the screen) and see if you can get back into your phone. If you can, I recommend wiping Dalvik as well to be safe.
You can wipe Dalvik with Titanium Backup Pro, but the easiest way is to install BSR (Boot Strap Recovery)
Info here and download links here: http://forum.xda-developers.com/showthread.php?t=1169677 (Be sure to use the Droid X2 links)
Nevermind....people read to.much.into ****
Goodbye
Thank you for proving you are superior Ash. I will try to avoid helping folks in the future. You are a winner.
As for the SBF, I posted to him how to use the stock recovery to clear his cache, hoping that it will get him back into his phone, where he can then root and install BSR. By the way, it tried, at least I posted instructions and links as well. Where are yours?
I fear he is going to need to clear user data, but I was trying to help him avoid that since it is tedious to re-install everything, unless you have a backup. By the way, there is no difference between pressing the volume up alone and pressing both. I have done both and posted what I think is most easy.
Since I did it SO wrong according to you however, I will refrain from advice in the future and leave it all up to you.
Nevermind....people read to.much into ****...goodbye
That's what I get for trying to help...
No, what you did was to confuse the issue and the thread with your need to show you are superior, without reading my entire post.
Since it works the same BOTH ways, either pressing volume up alone or pressing both, and since I specifically posted a method that might get him back into his phone without wiping all user data, from experience with the same issue, there was no need for your post other than to show you think you are superior in some way.
It's not a contest 'buddy', it's trying to help fellow users.
This is my last reply, back on topic.
Apparently YOU think I'm superior in some way
my.posts were not to show that at all
U need to relax
Didn't mean.to hurt your feelings/insult ya.
ill keep my clarification to myself from now.on....
y0himba said:
No, what you did was to confuse the issue and the thread with your need to show you are superior, without reading my entire post.
Since it works the same BOTH ways, either pressing volume up alone or pressing both, and since I specifically posted a method that might get him back into his phone without wiping all user data, from experience with the same issue, there was no need for your post other than to show you think you are superior in some way.
It's not a contest 'buddy', it's trying to help fellow users.
This is my last reply, back on topic.
Click to expand...
Click to collapse
Take a breath...then a chill pill. Its not a contest yes but anyone can post anything if they have two cents. No reason to be a **** when someone throws in two cents
Sent from my Cyanocrack using Xparent Blue Tapatalk
ashclepdia said:
Apparently YOU think I'm superior in some way
my.posts were not to show that at all
U need to relax
Didn't mean.to hurt your feelings/insult ya.
ill keep my clarification to myself from now.on....
Click to expand...
Click to collapse
Ash you have spit a lot of knowledge my way and have saved my butt many times. You have always been credible and I never second guess your comments. Don't stop helping so many for someone talking. We trust you ash. I just gave the same instructions to someone else about bootloop and SBF. I told him factory reset in android recovery. Works for me perfect every time! And I do not mind rooting and setting my phone back up.
Related
Yesterday I unplugged my phone and it wouldn't start. Had to take out battery and SD card to get it to eventually start, but it hung on the HTC white screen.
I can access the clockwork recovery screen, and have even been able to load previous backups and new roms to see if anything will work, but it won't let me get past that white HTC screen.
I feel like I'm close because I can still access the recovery menu, but something's up. So I have a few questions that if anyone can answer I will appreciate more than you know.
1) Is there a way to unroot my phone from the recovery menu/PC access so I can get it replaced by Verizon if it is a hardware problem? I know, I know, I did it to myself, but if there's a way out, I'll take it.
2) What are RUU files and would they somehow fix this? I am not against unrooting and going back to stock, especially after this scare.
3) As of now I have DasBampf 1.8.6 and MR2 radio on the phone. Will the RUU remove these and flash a whole new Radio/ROM? Again, I know I'm an idiot, but I need help. Help me Obi Wan!
4) I'll check back if anyone needs more info. BTW, the phone only boots into recovery *power+down volume* Won't turn on manually. I've tried another SD card, I've tried other ROMS. I have NOT tried any new radios yet, as I'm scared to accidentally brick it.
Thanks in advance.
go into bootloader (when it's off hold power button and volume down until white screen pops up) wait for it to check your sd card, then click wipe data. it should boot up after its done wiping the data, if not you might have to select reboot in recovery.
RUU update.
I flashed the 2.11.605.5 build of the new RUU. It started out fine, and then it failed at user data, system, and one other. Now it's still in the same hanging screen. What the hell!?
Please help me before I **** this thing up even more.
OTA updates are the DEVIL!!!!!! You people need to block them and stop installing the unrooted version while you are rooted with no reguard to your phones safety. If you are rooted install the rooted version of the OTA.
If I helped please use the thank you button and donate a free account to my dropbox http://db.tt/uDc7iw7x
I didn't read the op but if its hanging on htc screen with new ota try flashing the radio the new ota has or an older one. Had that issue with my EVO.
The wrong radio will cause your phone to never pass htc screen.
Sent from my Incredible 2 HD using XDA App
Haven't tried anything new yet, but besides one time this morning, I can't even get to the bootloader. Won't turn on, even with a spare charged working battery. Time to call Verizon and maybe eat the payment, methinks.
Update for anyone interested.
I got onto IRC and contacted Jcase, who had me flash a new RUU, which seemed to fix the problem.
HOWEVER, my phone is still FUBAR, as it shuts off periodically and will not allow me to call out. I managed to go through the entire unroot process and got my phone back to original status. I have a replacement coming from Verizon soon and although I think it's a hardware problem with my phone, I don't think I'll be rooting again anytime before my warranty expires. Thanks for all the help everyone.
need help
Hey guys, I was trying to unroot my thunderbolt but jacked things up. I had it wipe all date, now will not boot Its still rooted. When i go into the reboot mood its by Revolutionary. Info it displays where it gives me options of fastboot, recover, factory reset, simlock, hboot usb and image crc is
Revolutionary
MECHA XD SHIP S-OFF
HBOOT-6.O4.1002
MICROP-/
RADIO-1.49.00.0406v_1
eMMC-BOOT
Idk if that helps. It doesnt reboot or does a looping process. Just stays at the white htc screen and doesnt say anything, and is not the screen where it says htc quietly brilliant. When i go into recovery 4ext recovery touch is whats available, current rom:unknown. Im fairly new so i would greatly appreciate any help, I like this phone alot and would hate to use something else. I dont care if after everything is said and done its still rooted or not. I have my personal info still on my card and a backup on my computer so im safe on that and dont care if i lose everything on the phone. Also i did not try to do the ota update.
Because you wiped all your data to ahead and wipe cache and dalvik cache and system. Then flash another rom.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
Because you wiped all your data to ahead and wipe cache and dalvik cache and system. Then flash another rom.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
If you dont me asking, is there a step process you can suggest or point me to? Idk how to flash the rom and am new to this scene.
When flashing a rom. Wipe caches (cache and dalvik cache), wipe data (most of the time I recommend doing this), and system/boot partitions. Then after wiping all of those choose the option to flash a rom( I haven't used clockworkmod recovery in ages and I don't remember what they list that option as). When the installation is completed reboot and if all goes well you should be running a custom rom of your choosing. I would suggest you ditch cwm for 4ext recovery just as soon as you can. Cwm has some unusual bugs where the caches may not be properly wiped and your rom won't boot because of this.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
Cwm has some unusual bugs where the caches may not be properly wiped and your rom won't boot because of this.
Click to expand...
Click to collapse
I know back in the EVO days of no 4EXT Virus had a SuperWipe. It would wipe everything 3 times in CWM. If you are persistent to keep CWM you might want to try that... I think I have it somewhere I can make compatible for the Thunderbolt. But it is highly recommended to use 4EXT instead.
I had it at one point too but wiping 3x or 10x just to flash a rom is ridiculous.
Sent from my ADR6400L using Tapatalk 2
Hello, new here on XDA and hoping to be an established member here!
Im just startin out with roms and rooting. I trierd to install the liberty rom and its not working i dont think....
- i installed system recovery
- did a backup
- went through the rom toolbox and downloaded the liberty zip
- went through system recovery and installed liberty from the SD card.
- it went through successfully
now im stuck on a screen with the liberty bird spinning, the words liberty rom above it and it goes black every 3-5 seconds.
am i stuck? is it going through a process of some kind? it does this whether im plugged into the wall or not.
I just pulled the battery and i got the red M dual core logo, it went back to that liberty screen and is doing the same thing. I cant do anything!!!!
just some additional info for any help that may come my way....
i was on 2.3.4 before i flashed
I cant think of any other relevant info ppl might need. this is my only phone though, so im hurtin right now lol
Sounds like you are in a boot loop. Another important step you should have done before you rebooted out of recovery is to do the following:
1) Wipe the data
2) Wipe the cache
3) Wipe the dalvik cache
You can still salvage what you did. You need to pull the battery out. Then, put the battery in. After that, press and hold the power button AND the Volume Down button. Do this until you see words appear on the screen at the top.
Next, click the volume down button until you see Android Recovery.
Click the Volume Up button.
Wait a bit and you should then see the familiar Droid Icon with an exclamation point. When you get there, press both the Up and Down volume buttons at the same time to continue into recovery mode.
After that, you will be in the stock recovery. Click the volume down button to select the Wipe Data/Factory Reset and press the power button.
Once that's done, you can then select the Reboot System Now menu item and you should be good to go.
Remember, you should ALWAYS wipe the data, cache and Dalvik when flashing a new ROM to ensure left over files are lying around causing the dreaded boot loop you are experiencing.
I just tried it.
Im stuck on the liberty rom screen, but i read that it could take 10mins to boot up the first time. the screen isnt going black like it was before so I think im in the clear.
Im late for work now! hahaha
thank you so much though. This forum is a wonderful resource and the people seem really nice so far!
ill be sure to check for a thank you button after this post!
caseball20512 said:
I just tried it.
Im stuck on the liberty rom screen, but i read that it could take 10mins to boot up the first time. the screen isnt going black like it was before so I think im in the clear.
Im late for work now! hahaha
thank you so much though. This forum is a wonderful resource and the people seem really nice so far!
ill be sure to check for a thank you button after this post!
Click to expand...
Click to collapse
You may need to sbf if you cannot get back to the boot strap recovery screen.
Pull the battery and put the battery back in but do not power it on. Instead plug your phone into the charger if it goes into bootstrap recovery then wipe data, wipe chache then go to advanced and wipe dalvik cahce. reflash liberty and youll be good to go. If it doesn't youll have to sbf back to stock then try again. This time wipe data cache and dalvik and youll be ok. SBFing is easy and there is a tutorial the general section. If you have any questions on sbfing just put them here and myself or one of the other great community members will help you out.
Alright, I was running CM9 v13 until last night, but needed my camera for work(nothing portrays an accident scene better than a picture!), so I decided to reflash 198.7. Something terribly went wrong.
Read so many different threads and flashed so many different sbf's my head is spinning. I do know that when I power up and press up I get RSD, and if I power up and press down I can go through the menu. I even tried fastboot and attempted to follow some of these steps with fastboot. http://www.atrixforums.com/forum/rescue-squad/5358-alien-install-gone-bad-bricked-recovered-still-screwed-up-4.html
I am thinking that the bootloader isn't fried since I can get into the menu system, but even after flashing 198.7 if it doesn't fail it cycles through the never ending bootloop. When it does fail I get the following error on the device screen: SVF:106:1:2 sec_exception:b655, eddc, eb
Luckily I have seen Gman floating around here, so since he assisted big time with the atrix issue, I am hoping that he can assist me.
I don't have skype though...
I will have internet access tomorrow, but can't install anything to my work computer(toughbook, locked down like a fiend!)
Ideas? Not looking for a beatdown. Asking for help, from the community.
EDIT: Just saw this. http://forum.xda-developers.com/showthread.php?t=1394982For some odd reason I think this is what I did. Now it appears as though I am royally screwed!
Thank you,
Medic
You didn't have a nandroid backup of a blur rom you could have used? That would have been better than sbfing back to stock.
Sent from my MB855 using Tapatalk
When I got stuck in moto logo loop with no backup available I had to boot into recovery and factory reset then reboot. If you can use menu with power + down. On 154 sbf, then flashed 198.7 after booting again
Sent from my MB855 using XDA App
You need to factory reset or wipe before flashing a sbf. However all you need to do to get a camera is flash a blur rom like skinny or rocko, or even cm7. When you're done you can wipe and flash back. I do it all the time
Sent from my MB855 using XDA App
Grrr, I must have flashed the Electrify ROM. It boots into it, but has to make the phone call to activate. Can't bypass it. The Electrify has a locked bootloader?
Fastboot, RSD, and ASR work, or at least I can access them. Tried wiping date/factory reset, but it boots back into the Electrify ROM.
Not thinking my local rep will be able to help me out on this one!
Any other ideas?
Edit* Bypassed using the no bp option. Unable to root using Shabby's aio. Goes through the process, reboots, but when I attempt to launch system recovery it reminds me that I don't have root privs.
jokersax, why in your post for CM9 do you tell people that if they want to switch off of CM9 they have to sbf? I've nandroid'ed back without problems to stock, and it's a lot safer than flashing sbf's since everyone seems to temporarily brick.
it actually say just to wipe and flash a different rom. The sbf is to return to stock
mrinehart93 said:
jokersax, why in your post for CM9 do you tell people that if they want to switch off of CM9 they have to sbf? I've nandroid'ed back without problems to stock, and it's a lot safer than flashing sbf's since everyone seems to temporarily brick.
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Okay, now I am rooted and have bootstrap installed.
Looked in the about phone section, and duh, I am running 45.1.190 for the Electrify.
Any idea how to get this off of my phone?
medic233 said:
Okay, now I am rooted and have bootstrap installed.
Looked in the about phone section, and duh, I am running 45.1.190 for the Electrify.
Any idea how to get this off of my phone?
Click to expand...
Click to collapse
I had a similar issue. Unlocking the boot loader I used the Sbf for the Electrify by mistake and not the Pudding.sbf. Only it bricked my phone sticking it on the moto bootup and just giving me some errors and going nowhere from their. Now I'm just spit balling here, but I have a prediction on how you can fix, do some research to make sure this may work and not brick your phone:
1) Unlock your bootloader using Pudding.sbf
2) Use Bootstrap to Install CWM for Photon
3) goto the mounts and storage menu select format system
4) Once that finishes go back and select wipe data/factory reset and then wipe dalvik cache and cache partition
5) After wiped go to the advanced menu select reboot recovery
6) Once it goes back to recovery Power off
7) Go into RSD (hold power nd Volume up+)
8) Flash the stock sbf
9) boot up
10) I would recommend using Sdk tools Fastboot command -W to erase all user data and cache after everything if it boots up
I would assume this would do the trick, the only thing I'm uncertain of is if you'll be able to unlock. (If it goes through a long method then says failed right at the end then it probably worked) If it doesn't work you can continue the rest of the steps using bootstrap, but If it were me I would want to try to get as much Photon on the phone and Electrify off the phone as possible
FanBoy_Hunter said:
I had a similar issue. Unlocking the boot loader I used the Sbf for the Electrify by mistake and not the Pudding.sbf. Only it bricked my phone sticking it on the moto bootup and just giving me some errors and going nowhere from their. Now I'm just spit balling here, but I have a prediction on how you can fix, do some research to make sure this may work and not brick your phone:
1) Unlock your bootloader using Pudding.sbf
2) Use Bootstrap to Install CWM for Photon
3) goto the mounts and storage menu select format system
4) Once that finishes go back and select wipe data/factory reset and then wipe dalvik cache and cache partition
5) After wiped go to the advanced menu select reboot recovery
6) Once it goes back to recovery Power off
7) Go into RSD (hold power nd Volume up+)
8) Flash the stock sbf
9) boot up
10) I would recommend using Sdk tools Fastboot command -W to erase all user data and cache after everything if it boots up
I would assume this would do the trick, the only thing I'm uncertain of is if you'll be able to unlock. (If it goes through a long method then says failed right at the end then it probably worked) If it doesn't work you can continue the rest of the steps using bootstrap, but If it were me I would want to try to get as much Photon on the phone and Electrify off the phone as possible
Click to expand...
Click to collapse
Alright, completed 1-8. Phone won't reboot, stuck in the Dual Core screen.
I did notice a bunch of "Failed to Boot 2" messages, but last I had looked the battery was full.
Attempting fastboot stuff now.
moto-fastboot devices works, lists my device.
moto-fastboot erase recovery fails. remote: (00180001)
moto-fastboot flash recovery stock_recovery.smg works, sends and write recovery
moto-fastboot reboot works
medic233 said:
moto-fastboot reboot works
Click to expand...
Click to collapse
So where are you now?
It is just sitting there with the dual core screen. Still.
Tried turning it off so the battery could charge, won't turn off.
Menu is still accessible.
medic233 said:
It is just sitting there with the dual core screen. Still.
Tried turning it off so the battery could charge, won't turn off.
Menu is still accessible.
Click to expand...
Click to collapse
This is obvious, but I have to ask, did you do a battery pull and let it sit for a couple seconds and then try to reboot? also it's stuck on mogo, is it showing error 2,3 or 4? Or any error for that matter?
Did a few battery pulls.
No error, just the Moto Dual Core Screen.
I contacted one of my friends who is a rep, and he will strip the phone, and exchange it. Helps that his boss has a Mopho and he is getting one in a few days.
Thank you for the help FanBoy_Hunter. Greatly appreciated.
I pick up my new mopho tomorrow.
I am going to leave it stock(sigh).
Was not going to reactivate my crackberry.
Grrrr!
My X2 starting losing signal. Today I did a hard reboot and when the phone comes back on it makes it to the black screen with the Motorola logo and says Modem did not power up (2) starting RSD protocol support. Verizon is sending me a warranty replacement. I have already done a factory reset. Phone was rooted would the factory reset erase the root so that it's safe to send back.
Phone was rooted with Pete's root tool.
redfish10 said:
My X2 starting losing signal. Today I did a hard reboot and when the phone comes back on it makes it to the black screen with the Motorola logo and says Modem did not power up (2) starting RSD protocol support. Verizon is sending me a warranty replacement. I have already done a factory reset. Phone was rooted would the factory reset erase the root so that it's safe to send back.
Phone was rooted with Pete's root tool.
Click to expand...
Click to collapse
try dialing *228 option 2 This will reconfigure your signal from cell towers
http://support.verizonwireless.com/faqs/Wireless%20Service/faq_prl_preferred_roaming_list_update.html
I tried that. The phone will not make it past the black screen with the Motorola logo. And I get the modem message across the top.
Sounds like the radio is burned out. No fix for that unless you want to break out the soldering iron
That's what I figured. I have another phone on the way. I was able to do a factory reset. Would this remove the root. Phone was rooted with Pete's one click root tool.
Sending phone back so I have to make sure root is removed.
redfish10 said:
Sending phone back so I have to make sure root is removed.
Click to expand...
Click to collapse
I think there's an app for that
I know but my phone is useless right now. I can't see anything but the black boot screen.
Sbf and send it in. Problem solved
Sent from my GT-P3113 using xda premium
SBF = wipe everything. This is like doing a total factory reset; it clears and re-writes almost every partition. Root access would be wiped out from it.
****@Reddish****
Try resetting ur super user
Go to app manager and clear data I found that to be my problem in the past and then turn off ur x2, not reset your phone. Than repower.
Hope it works.
What are you running?
Sent from MB870 W/ Cm7.2 Rc1 MASHUP V2
SUCESS I THINK YES...
Dudes stuck @ red m. No way to reset superuser. Have to SBF.
Sent from my MB870 using Xparent Cyan Tapatalk 2
Omega360 said:
SBF = wipe everything. This is like doing a total factory reset; it clears and re-writes almost every partition. Root access would be wiped out from it.
Click to expand...
Click to collapse
Not ENTIRELY true.
While flashing a sbf file using RSDlite, you are setting all the system and proprietary things back to completely stock. It will remove root access, and all that junk, along with all, the things that came from mods/tweaks/hacks/roms
BUT flashing sbf BY ITSELF alone will NOT wipe away ANY user data. You MUST data wipe from stock recovery to do that. This is why sometimes you boot loop,after sbf flash , and you need to data wipe to cure those boot loop blues, cuz sometimes there are things left over that you tweaked that didn't get wiped out after flashing the sbf, but they get removed from a data wipe from stock Android recovery.
To sum up:
For a TRUE OUT OF BOX FACTORY CONDITION(i.e. You just bought and opened the box) MUST flash sbf file using RSDlite with a computer. AND THEN after that, you wipe data/cache from stock Android recovery.
I'm willing to bet that would have also fixed you issues with not being able to boot past Motorola screen as well. Cant hurt to get a new one, but if you can compare them to see which is in better working order, then it couldn't hurt to do.
Either way, if youre going to send it in, and want to erase traces of root and such, then you need to do more than just data wipe. You NEED to sbf AND data wipe.
From my nexus tappin the talk
<edit post successful>
That's why I said ALMOST every partition
Just do recovery...
Pull your battery/replace
And plug it in... to the wall that is
Screw an sbf
Sent from MB870 W/ Cm7.2 Rc1 MASHUP V2
SUCESS I THINK YES...
Modem Did Not Power Up (2)
ashclepdia said:
I'm willing to bet that would have also fixed you issues with not being able to boot past Motorola screen as well. Cant hurt to get a new one, but if you can compare them to see which is in better working order, then it couldn't hurt to do.
Either way, if youre going to send it in, and want to erase traces of root and such, then you need to do more than just data wipe. You NEED to sbf AND data wipe.
<edit post successful>
Click to expand...
Click to collapse
This is absolutely true. The error "Modem did not power up (2)" is something that I have been dealing with as well. I'd love to work with someone to figure out the problem, but it is probably not hardware. I encountered this error for the first time 2 weeks after installing Eclipse 2.2.1. I solved it by SBF to Stock. Once I had re-installed a stock ROM the error went away and the phone operated normally. I just had this error pop up again almost exactly 2 weeks after installing CM7 RC1. When I get home I'm going to SBF to stock and hopefully that will correct the issue (again). I tried clearing my cache and then clearing my data through stock recovery, but that won't correct the error - and unfortunately the error happens before BSR boots so I can't Nandroid back to a healthy setup and see where the problem is. Both times I lost signal on the phone, re-booted, and then got stuck at the Red M with the Modem error. :crying:
I'm going to try to load CM7 again, but it's pretty awful to have this happen at work and suddenly be without a functional phone. (Maybe I have to install RSD Lite on my work computer ...)
Any thoughts on this would be appreciated but I can tell you that ashclepdia is right, it is probably not a hardware problem. It seems to be a problem with rooting/flashing on certain handset builds.
guys i have a funny issue wonder if i can get some help. I flashed FlappJaxx Beta 3 and had a bad down load or something so anyway tons of reboots and nothing just the non stop vibrate.. well i i finally got it back to the down load screen after pulling the battery several times. and got it Odin back to unrooted and turn on followed the unroot instruction well i left it stock and have had same issue where i click something and it flashes and just vibrates over and over until i pull battery.. well is this phone dead is there a fix?
I odin back again and same thing im going to odin back to stock again then do a stock root and flash another room but its doing the stupid reboot over and over vibrate thing even with the non-rooted stock rom. i just can't seem to find any direction on how to fix this or is it just a lost cause. wanted it to hold on till Note 2 hit shelves but looks like a s3 in my futures.
OK didnt work still FC and boot looping this time i installed Kies and put in download mode and updated the firmware and im getting same thing. GOSH DOGGIT hahaha.. Yea i need some advise i tried everything ive read i must be missing something somewhere.
i guess no one has ever had this before? still no solution i have tried everything format the internal disc but want to know if i do that will i be able to flash odin back to stock any help there?
walkerkd said:
i guess no one has ever had this before? still no solution i have tried everything format the internal disc but want to know if i do that will i be able to flash odin back to stock any help there?
Click to expand...
Click to collapse
First of all, I'm no pro at this stuff but I feel your pain.
It sounds like you are getting stuck in a boot loop of sorts.
What I would do if I was you, after flashing a rom, go back into Recovery mode on the phone and clear out the cache partion, wipe Dalvik cache, and then wipe data/factory reset. After that, reboot your phone - it should start up normally. This is what I do to my phone to get it to function as it should.
Hope that helps
i went in to the advance tab and formatted everything hahah.. it juts wiped and odin back to stock again bout to wipe it and try to odin root see if i can get it done. worth a try ive tried to much stuff im bout to take phone out get my 338 tape to a zombie target and have some fun!
walkerkd said:
i went in to the advance tab and formatted everything hahah.. it juts wiped and odin back to stock again bout to wipe it and try to odin root see if i can get it done. worth a try ive tried to much stuff im bout to take phone out get my 338 tape to a zombie target and have some fun!
Click to expand...
Click to collapse
What language are you using here? I have no idea what you are saying.
kmacsouris said:
First of all, I'm no pro at this stuff but I feel your pain.
It sounds like you are getting stuck in a boot loop of sorts.
What I would do if I was you, after flashing a rom, go back into Recovery mode on the phone and clear out the cache partion, wipe Dalvik cache, and then wipe data/factory reset. After that, reboot your phone - it should start up normally. This is what I do to my phone to get it to function as it should.
Hope that helps
Click to expand...
Click to collapse
Agreed ...
When returning to stock via Odin ...you must reboot into your recovery and wipe data and factory reset the device prior to rebooting.
Even though you wiped prior to flashing the stock Odin .tar image.
These devices stay dirty even after wiping data on occasion ...g
gregsarg said:
Agreed ...
When returning to stock via Odin ...you must reboot into your recovery and wipe data and factory reset the device prior to rebooting.
Even though you wiped prior to flashing the stock Odin .tar image.
These devices stay dirty even after wiping data on occasion ...g
Click to expand...
Click to collapse
Yea i think thats what happen. it was not a clean wipe but i think i got it now i have gotten two fc & reboot i can live with that. thanks you guys for your help.
walkerkd said:
Yea i think thats what happen. it was not a clean wipe but i think i got it now i have gotten two fc & reboot i can live with that. thanks you guys for your help.
Click to expand...
Click to collapse
Boot into your recovery, and "fix permissions "...then reboot.
That should clear up the rest of the issues ...g
gregsarg said:
Boot into your recovery, and "fix permissions "...then reboot.
That should clear up the rest of the issues ...g
Click to expand...
Click to collapse
oh really? wow i didnt even think about that im wiping again and flashing odin to stock but this time after it boots i will wipe factory reset. then root factory reset and fix permissions. thank for the help!
Always welcome ....
Fixing permissions is overlooked a lot ...
And the wrong permissions will cause FC's all over the build ..
I always fix permissions after any flash or modification ....it's just a good habit to get into ...IMHO ...g