Was having some troubles with my phone so I decided to do a factory reset, wiped everything and flashed Synergy 1.3 and Imo Leankernel. I got everything restored with TB and seemed to be going fine. Then I figured out the home button wasn't working. I turned off the screen and tried turning it on using the home button and it works fine, but once I get onto my home screen or in an app it absolutely won't work. I tried long pressing it to see if it will bring up the recent apps--it doesn't. I have no idea where to go from here. I'm new to flashing and I don't know what I could have done to make this happen. Any help would be greatly appreciated. I have the unlocked icon so I don't think I will be able to get Verizon to replace it. Thanks in advance.
Zool4nd3r said:
Was having some troubles with my phone so I decided to do a factory reset, wiped everything and flashed Synergy 1.3 and Imo Leankernel. I got everything restored with TB and seemed to be going fine. Then I figured out the home button wasn't working. I turned off the screen and tried turning it on using the home button and it works fine, but once I get onto my home screen or in an app it absolutely won't work. I tried long pressing it to see if it will bring up the recent apps--it doesn't. I have no idea where to go from here. I'm new to flashing and I don't know what I could have done to make this happen. Any help would be greatly appreciated. I have the unlocked icon so I don't think I will be able to get Verizon to replace it. Thanks in advance.
Click to expand...
Click to collapse
first step would be to download the stock odin image from samsung-updates.com and flash that. See if the button works. If it doesn't work, somehow you borked your phone in the wierdest way but hey who knows.
Also flashing this will take away the locked icon.
Other option would be to flash a different rom, like beanstown, or mine, and see what happens. If it doesn't do it there, I would reflash synergy, but after verifying the md5.
Also are you using any sort of launcher (apex, nova, go, etc.), I noticed my home button was a little finicky with them?
nosympathy said:
first step would be to download the stock odin image from samsung-updates.com and flash that. See if the button works. If it doesn't work, somehow you borked your phone in the wierdest way but hey who knows.
Also flashing this will take away the locked icon.
Other option would be to flash a different rom, like beanstown, or mine, and see what happens. If it doesn't do it there, I would reflash synergy, but after verifying the md5.
Click to expand...
Click to collapse
kabro91 said:
Also are you using any sort of launcher (apex, nova, go, etc.), I noticed my home button was a little finicky with them?
Click to expand...
Click to collapse
I was using Apex at the time, but I also tried Nova and TW to no avail. It was the weirdest thing...so I ended up flashing ParanoidAndroid Hybrid Jellybean ROM and it is working out great for me so far. No issues with the home button, and even if it does happen again, I have the on-screen keys to save me
Alright so I was running ParanoidAndroid for a little bit, but I saw that the new Synergy 1.4 was released. I figured with a clean wipe and install everything would be back to normal. Installed fine, restored everything fine, rebooted just so everything would be working properly and then the problem is back again. Is there any way it would be something that I am restoring onto my phone? I still just have no idea...I downloaded a temp virtual home button so it still functions, but I'm at a loss here. Same issue as last time. My home key will turn on the screen, but then is useless after that.
nosympathy said:
first step would be to download the stock odin image from samsung-updates.com and flash that. See if the button works. If it doesn't work, somehow you borked your phone in the wierdest way but hey who knows.
Also flashing this will take away the locked icon.
Other option would be to flash a different rom, like beanstown, or mine, and see what happens. If it doesn't do it there, I would reflash synergy, but after verifying the md5.
Click to expand...
Click to collapse
Oh, also I don't have a PC to run Odin on, so is there any way I could flash the stock image from my phone?
Related
I only installed the software cwm recovery (not nvflash), so I have no way out now. I haven't done anything serious except flash paul's patch and use titanium to uninstall some crapware like qik, that reader software, polaris office, etc.. nothing OS related, just apps. I also removed the GPS software, so I don't know what killed it exactly.
After removing those apps with TB, everything ran fine except I kept getting a force close from Qik... so I rebooted. Now it doesn't load and freezes on the LG screen with the loading bar not moving.
I don't know of any other options at this point...
Load up nvflash and get CWM on there so you can vol down + power into it. Then wipe data/cache and reboot.
You're not bricked even tho you think you are
GideonX said:
Load up nvflash and get CWM on there so you can vol down + power into it. Then wipe data/cache and reboot.
You're not bricked even tho you think you are
Click to expand...
Click to collapse
brick means HARDWARE LOCK or SOFTWARE LOCK
if your screen turns on at all... there is hope
fallow gideonx instructions... they have a nice tut set up for Nvflash
plus a one click type thing in the development section
I'm bricked for the time being until I can get home. I'm locked out of the device manager here at work, so I can't install the nvflash driver. Ignorant sons o'....
Sometimes I really hate the IT department.
Hopefully this is a warning to everyone else that if they want a custom recovery, they should bypass the rom manager option as it's too dangerious and just do the nvflash option.
For now nvflash is a better option instead of RM.
So I got home and used nvflash to put the latest cwm recovery on it. I wiped cache and rebooted... it shutdown the phone instead. So I manually turned it back on and it did the same thing.
So I did a full wipe and flashed a rom... and now it bootloops. I may very well have a bricked device after all.
Flashed which rom?
Here's a nandroid restore you can use:
http://forum.xda-developers.com/showthread.php?t=1048274
Eagles Blood since it was the fastest available.
The stock backup image is taking a long time thanks to the slow download. It's really irritating when all I can get on my 20mbps connection is 64KB/s.
antoniouslj said:
Eagles Blood since it was the fastest available.
The stock backup image is taking a long time thanks to the slow download. It's really irritating when all I can get on my 20mbps connection is 64KB/s.
Click to expand...
Click to collapse
I'd do the nandroid restore if I were you...
antoniouslj said:
Hopefully this is a warning to everyone else that if they want a custom recovery, they should bypass the rom manager option as it's too dangerious and just do the nvflash option.
Click to expand...
Click to collapse
noone will heed that warning lol.
Not a brick bro...just a minor bump in the road..you will get wiser from this..
G2X
fcisco13 said:
Not a brick bro...just a minor bump in the road..you will get wiser from this..
G2X
Click to expand...
Click to collapse
Actually it is completely gone now... seems like I have a defective device.
It won't boot into recovery or anything for that matter now, it just freezes at the first LG screen (the one without the progress bar). What's even weirder is I haven't really done anything to it... just installed and ran apps/games. I shut it down so I could install CM, but it won't boot into recovery or anything.
I tried redoing nvflash and it went fine, but it still won't boot into recovery.
This really sucks too... right on the eve of CM for this thing.
So I just updated to 3.1 thanks to BRD, I wiped like I was suppose to and everything seems to be working except the home button doesn't do anything anymore. The button highlights like I clicked on it but won't return me to home. Does anyone have a suggestion on how to fix this?
I came from tiamat 1.4.1 if that matters.
Thanks in advance and sorry if it's a n00b question, im usually good at finding an answer on my own (hence this being my first post)
Try a reboot.
Sent from my Xoom using Tapatalk
I've done that several times now, I also just tried reflashing the update and bootloader (this time without the factory wipe) and still a no go
Strange. I had my home button not work on a first boot of the official images for some reason but a reboot fixed it. Actually it may have been the back button.
Sent from my Xoom using Tapatalk
I would flash back to the official motor images. Pretty sure it will work then. I can't see how it could not. Then try the update again.
Sent from my Xoom using Tapatalk
Wow I feel like an idiot, i think i restored some things through titanium backup that I shouldn't have. A factory reset fixed it
My brother got tired of all the bloatware on his G2x with 2.3.3 OTA, so I proceeded to try to flash a custom ROM. Did the process of NVFlash, but with some unexpected results:
1) As I'm lead to believe, I should see an orange "ANDROID" show up when holding volume down and power. But instead I get a green "ANDROID" with a bunch of Android icons like messaging.
2) When it gets past the screen I mentioned, it does go into CWM Recovery but as soon as I let go of a button to navigate, the phone shuts off. Sometimes it stays on if, while still holding down volume and power, I press volume up, release down, then release power. Even then, it sometimes still shuts off.
3) When trying to flash a rooted ROM (CyanogenMod 7.1, after doing a data wipe/factory reset), I get an error message and the installation aborts.
Was able to restore the 2.3.3. OTA because I had backed up, but any ideas?
I am no expert but I would start over from scrach. Rinse and Repeat. it sounds like it did not install right.
Are you sure you flashed the CWM for the G2X? If you flashed the wrong recovery all kinds of problems, such as you described, could occur. Good thing you had the backup.
mojorisin7178 said:
I am no expert but I would start over from scrach. Rinse and Repeat. it sounds like it did not install right.
Click to expand...
Click to collapse
Would you recommend I reflash CWM straight up, or the stock recovery through NVFlash before trying again? I'd assume I should follow all the same steps as if I was trying to flash CWM, but instead of clicking on CWM, click stock recovery instead.
jboxer said:
Are you sure you flashed the CWM for the G2X? If you flashed the wrong recovery all kinds of problems, such as you described, could occur. Good thing you had the backup.
Click to expand...
Click to collapse
Positive. I downloaded the necessary files and followed all the steps from here:
http://forum.xda-developers.com/showthread.php?t=1056847
Again I am no expert but that sounds like a good idea i would say you it cant hurt. I think you will have to reflash cwm but you have to do that anyway so I would say it is the best way to start clean.
Got CWM Recovery to work. It still shows the green ANDROID with the icons, but I no longer have to struggle to keep it from shutting off. I was able to flash xboarder's tweaked Gingerbread ROM, but still unable to flash CyanogenMod 7.1. I did a factory/wipe data, wiped cache, and dalvik cache. Still get an error message upon trying to install.
when i first did the nvflash my phone was getting shut off when it got to the recovery and then i let go of the power button. Until i realized that you are supposed to let go of the power/volume button when the word android appears and all those icons u mentioned, yeah i get the same screen. i had no problems flashing 3 builds of cm7 and xboarder's rom 2 times.
Not sure what's going on with the CM 7.1RC but I was able to flash the latest EaglesBlood ROM this mornibg and he's really enjoying it so far. Thanks for all the help!
Sent from my HTC Glacier using XDA App
The green android with the icons is just a different splash screen in the newer version of cwm.
lcambriz said:
Not sure what's going on with the CM 7.1RC but I was able to flash the latest EaglesBlood ROM this mornibg and he's really enjoying it so far. Thanks for all the help!
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Could've been a bad download. Sometimes you just gotta download the file again and it'll flash no issues.
But I'd go for the latest CM7 nightly. They are leaps and bounds ahead of where they were with RC1.
I figured that might be the problem. Eaglesbood seems to be working really well for him, so I think he'll just stick with that. My bro is more of the "If it isn't broken, don't fix it" type, whereas I'm more inclined to try the latest. I'm tempted to try the nightlies myself on my Glacier, if they really are better than RC1.
Sent from my HTC Glacier using XDA Premium
***ONLY VERIZON GS3***
A lot of people have been having problems with flashing CM10.1 and the SlimBean 4.2.1 beta. This guide will tell you how to fix the data. At first it looks like you lost your IMEI, but you probably didn't. It is a simple fix.
What you will need:
Odin: http://samsung-updates.com/Odin307.zip
Stock Rom: https://www.dropbox.com/s/wjaifmod7d78lt0/stock.vzw_root66.tar
Instructions:
1. Go into Odin put the stock rom into the PDA part and make sure the check mark next to it is checked.
2. Boot into Download mode by hitting Volume Down + Power + Home
2. Make sure only "Auto Reboot" and "F. Reset Time" are checked under options (if not you can seriously mess up your phone).
3. Flash the stock rom using Odin.
4. Once it says pass in Odin take your phones battery out and boot into recovery by hitting Volume Up + Power + Home.
5. Hit wipe data/factory reset (your phone should restart)
6. Hit the bottom left then right then left then right then volume up to pass activation.
7 Then type *2767*3855# into the phone once you set it up (you shouldn't have to press call).
Now you phone should be fixed, and you should be able to root, unlock your boot loader and try again.
Tip:
When flashing SlimBean 4.2.1 beta 1 and CM10.1 use a dirty flash over a 4.1.1 or 4.1.2 rom.
- Dirty flash is when you don't clear your data before you flash.
thanks
Trying this now, I have been working all day to fix this.
I first ran into problems yesterday, cm10 ran out of room, removed a bunch of stuff( my back ups). Did some flashing and reverting and such. Now i seem to be stuck in roam mode.
Questions: What is the point of step 5?
It just says to load into recovery then next step is once the phone is loaded.
There is no step 6.
Haigot said:
Trying this now, I have been working all day to fix this.
I first ran into problems yesterday, cm10 ran out of room, removed a bunch of stuff( my back ups). Did some flashing and reverting and such. Now i seem to be stuck in roam mode.
Questions: What is the point of step 5?
It just says to load into recovery then next step is once the phone is loaded.
There is no step 6.
Click to expand...
Click to collapse
Sorry I'll fix that I was in a rush to get this finished before work.
This works!
But if you are still interested in CM10.1 you can still flash it with data working!
I decided to go out on a limb and tried going from ICS (VRALG1_odex) rooted/unlocked (after using provision code and getting data back) to CM10.1. To my surprise I found I flashed fine and had data!
I highly suggest using this ROM (http://www.sundergaming.com/downloads/sch-i535/tw/VRALG1_Odex.zip) as it uses its own UI when flashing it from recovery and will keep both ROOT and UNLOCKED BOOTLOADER when installing.
My guess is the problem seems to lie somewhere between a tw rom 4.1.1 JB and cm10.1
Luckly I don't have to deal with this and everything rolled over perfectly for cm10.1
Wow, I wished you had posted this before I returned my phone to the store for a warranty replacement!
Would have saved me a few days of agony, flashing and re-flashing that's for sure. Thanks for sharing though! It's good to know there is a fix for this.
You don't have to do this. This happened to me. Flash cm10.1 without any g apps. This will take u past the activation screen. Go into settings and change mobile network settings to SIM and automatic. Reboot phone. Make sure you have data, phone, and sms. Boot into recovery and flash away. U should have everything back on whatever Rom u choose.
Sent from my SCH-I535 using xda app-developers app
When you boot into recovery, just reboot?
and when i typed in the number, it didnt do anything....
P8ntballa57 said:
When you boot into recovery, just reboot?
and when i typed in the number, it didnt do anything....
Click to expand...
Click to collapse
Sorry I posted this in general and android development because I wasn't sure witch one it was, and when I fixed that I forgot to fix it here but I did now.
I can confirm this worked for me!
But, I couldn't get passed the activation screen in order for me to dial the code to reset phone so what I had to do was tap on the bottom of the screen as follows= Tap Left -Tap Right- Tap Left- Tap Right- then Volume up to get out of activation screen then was I able to dial the code to reset my phone. Thank you for this guide op!!!!
i wish i would have seen this yesterday. after trying to flash CM10.1 and getting stuck in roaming for a day in a half, i had to return mine to Costco and get a new one.
zaccat4 said:
Tip:
When flashing SlimBean 4.2.1 beta 1 and CM10.1 use a dirty flash over a 4.1.1 or 4.1.2 rom.
- Dirty flash is when you don't clear your data before you flash.
Click to expand...
Click to collapse
so just to make sure if im on CM 10.0 stable, if i flash the CM 10.1 without wiping or doing a factory reset, i wont go into roaming mode again? I apologize for possibly repeating you but ive had alot of trouble with this.
Ryan92019 said:
so just to make sure if im on CM 10.0 stable, if i flash the CM 10.1 without wiping or doing a factory reset, i wont go into roaming mode again? I apologize for possibly repeating you but ive had alot of trouble with this.
Click to expand...
Click to collapse
not necessarily. I did this and I was stuck in roaming but all I had to do was go into wireless settings/mobile network settings and make sure my preferred network was set to LTE/CDMA
you can do all this while your phone is trying to activate.
Anyone have an idea for a better file hosting site?
Will this work on a US Cellular phone?
This site has no section for US Cellular.
nmeseth said:
Will this work on a US Cellular phone?
This site has no section for US Cellular.
Click to expand...
Click to collapse
No you have to get a file for your phone or else you could hard brick it.
zaccat4 said:
No you have to get a file for your phone or else you could hard brick it.
Click to expand...
Click to collapse
I just got a stock ROM for USC, if I use that will these instructions work?
nmeseth said:
I just got a stock ROM for USC, if I use that will these instructions work?
Click to expand...
Click to collapse
Im not sure if the number will work either, it may just be a Verizon thing.
I tried flashing 4.2.1 ROM just to check it out before putting my phone back to stock for a replacement and it borked my network. I tried the method mentioned in the OP and it works great, thanks.
Thank you so much.....you saved my butt and now my phone is working again. Guess I should stop flashing a new rom every couple weeks.
Geez...I'm really tired of posting these newb questions...feel free to ignore.
After being on 7.2.0 for a while, I noticed that Bluetooth is not turning on...not a major issue since I use it so rarely...still, it's bugging me.
I've searched and tried the following:
1. Cleared dalvik, fix permissions, & reboot.
2. Holding down the "turn on Bluetooth" button and immediately rebooting.
3. Trying out all 3 padded modems suggested for this ROM
I have NOT tried reflashing the ROM or going back to stock and reflashing from there...I guess it's possible that a file or driver got left behind when I flashed from GB to CM7.2.0.
Other than the bluetooth issue, everything is working that's supposed to be working.
Any suggestions would be appreciated...as usual, thanks.
There are some bugs for CM7, that may be one of them. I REALLY doubt that a file got left back, but there no point in not trying to reflash.
airfluip1 said:
There are some bugs for CM7, that may be one of them. I REALLY doubt that a file got left back, but there no point in not trying to reflash.
Click to expand...
Click to collapse
Solved...I one-clicked back to stock, booted into recovery, did all the wipes, & reflashed. Bluetooth working fine and quickly paired with my device. I still have no idea what I did wrong the first time.
DickyG said:
Solved...I one-clicked back to stock, booted into recovery, did all the wipes, & reflashed. Bluetooth working fine and quickly paired with my device. I still have no idea what I did wrong the first time.
Click to expand...
Click to collapse
Sometimes things just go wonky. Like on a PC, drivers control the devices on the phone as well, as if you're had a driver go bad where your network quit working or any USB devices on a PC, the same thing is possible on a phone.