Phone broke, Help! - Samsung Galaxy Exhibit 4G

Hi, I recently tried to root my Galaxy Exhibit, but now it's broken, nothing will load, it all force closes. My home, menu and search buttons do not work, I tried to restore it by using factory reset, but that just messed it up more. I plunged it into Samsung Kies, but it won't recognize the device. How can I restore the phone back, unroot, to factory settings.
This is what I did, first I downloaded TWO custom kernel (or roms, idk the difference.) The first one worked like a charm it was the root stock 1.8 but it was too stock, I wanted ICS so, I restored and I put a different rom/kernel in and booted it up, and boom everything is messed up, my kernel version has not changed, I tried using cwm recovery, but it didn't do anything.
Thanks
Sent from my LG-E970 using xda app-developers app

Well easy fix, in cwm wipe system or ROM 3 times wipe cache/dalvic cache. Then you can flash ICS and gapps, be advised there is no further development for ICS so I would suggest any 4.1 ROMs or even the 4.2 ROMs. Make sure you flash gapps
Sent from my SGH-T679 using xda app-developers app

this is why people need to do research. if you dont know the difference between roms and kernels dont flash

Amen lol
Sent from my SGH-T679 using xda app-developers app

Related

Cm7 nightly question

I have cm7 on my phone, recently I've been trying to flash a nightly on my cappy and after the install "about phone" still shows the old mod. ROM manager also shows the old mod as my "current ROM"
I've tried reflashing, and even downloading onto my computer copying it to my card and trying to install through recovery and get stuck in bootloop. Ive deleted old mods from the download folder and Ive also tried different nightlies and have the same problem. Any help is appreciated
Sent from my SGH-I897 using XDA App
xcentrik05 said:
I have cm7 on my phone, recently I've been trying to flash a nightly on my cappy and after the install "about phone" still shows the old mod. ROM manager also shows the old mod as my "current ROM"
I've tried reflashing, and even downloading onto my computer copying it to my card and trying to install through recovery and get stuck in bootloop. Ive deleted old mods from the download folder and Ive also tried different nightlies and have the same problem. Any help is appreciated
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
..and you've done the basic clearing your caches, data and dalvik? You may want to try a fac reset. That fixes a lot of problems sometimes
.. for the future you should post in the cm7 q&a's. Even if it is a nightly
Yeah, Ive done the wipes and caches. I guess I'll try fac reset. Thank you for the help
Sent from my SGH-I897 using XDA App
Good luck!
Sent from my SGH-I897 using XDA Premium App
Ok, I did a fac reset, wipe cache, dalvik. Downloaded latest build through Rom manager, did cache, dalvik again, and still have the same results. Any ideas?
Sent from my SGH-I897 using XDA App
xcentrik05 said:
Ok, I did a fac reset, wipe cache, dalvik. Downloaded latest build through Rom manager, did cache, dalvik again, and still have the same results. Any ideas?
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
That is pretty bizarre .. honestly I don't know what's going on here.
Sent from my SGH-I897 using XDA Premium App
I know, my friends think I'm crazy. So I'm thinking I could flash back to stock and then start over? So, to do this I need to flash the stock Rom using Odin with repartitioning, correct? I'm assuming I can't use Odin jf6 one click because it doesn't repartition, or does it?
Sent from my SGH-I897 using XDA App
xcentrik05 said:
I know, my friends think I'm crazy. So I'm thinking I could flash back to stock and then start over? So, to do this I need to flash the stock Rom using Odin with repartitioning, correct? I'm assuming I can't use Odin jf6 one click because it doesn't repartition, or does it?
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
Yeah.. Odin one click JF6 does the repartition. I've flash back to stock a few times using that method and the last time being just a couple weeks ago. That is about your best bet. Odin back to stock.. get cwm and flash nightly. Its gotta stick then... you'd think
Sent from my SGH-I897 using XDA Premium App

Auto rebooting on CM9.1 (and CM9.0)

Hello mates,
I flashed CM9.0 on my galaxy note and it all went well but in the latest days it was autorebooting himself, kinda out of the blue. Then I flashed the updated rom CM9.1, hoping to this bug disappear, but it still going on.
Anyone knows how to fix that? I was thinking that it might be a kernel problem, but i really don't remember wich kernel I flashed in the first place.
I was thinking to flash Paranoid Android Rom, but I just can't find a stable one, any one knows how to find it?
thanks
Try to go to any stock rom....then see if it is still exist
Sent from my GT-N7000 using xda app-developers app
Did you flash a custom kernel? You can also try clean note.
Sent from my GT-N7000 using xda app-developers app
I've just flashed another kernel and it is stupidly fast.
If I want to clean galaxy note, how can I do that?
Sent from my GT-N7000 using xda app-developers app
easy clean install first, dont restore data or apps, ever, and fix permissions solve 99% of the cases.
Just stick to procedures.
heres mine:
on safe kernel and safe kernel recovery(safe cwm)
wipe cache, dalvik and factory reset,
then format all(except efs and take out external card) in mounts
put external back in, reboot recovery, phone wont boot anymore but dont worry about that.
then install cm zip, gapps reboot, done! first boot takes time.
all at own risk,
you will lose data,
but the issues will not be caused by restoring of apps/data, or other crap lingering
edited.

Broken LockScreen (JB)

Hi XDA im new there i was looking for this issue everywhere but doesnt seems like its somewhere
when i installed Jelly bean i had fully working device but i pressed lock button and there it started when i want to unlock it i have screen like this
dl.dropbox.com/u/55724162/DSC_0885(.DOT)JPG
I used 3 versions of CM 10 JB
Still same issues and my Recovery is CWM 6.0.0.8
Thx in advance
Cant use link but i think its important to see it so please be nice
What specific tab do you have?
Edit and what rom
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I have P7310
Tested these jelly beans:
cm-10-20121111-UNOFFICIAL-p5wifi
cm-10-20121025-UNOFFICIAL-p5wifi
cm-10.1-20121222-UNOFFICIAL-p5wifi
and in everyone i got this issue right after first attempt to unlock from sleep mode (via lockscreen)
same AOSP_14-01-2013_Beta-14 P5wifi
Well your picture doesn't look good, can't do much on it can you? Does it only do it on the cm10 roms? I'm not sure what to tell you but I'd try fixing permissions in your recovery.
What recovery are you using and how did you flash it. Factory reset, wipes, etc
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Bassicaly i did all wipes then instaled rom then Gapps and then rebooted
Like i said my recovery is this Clockwork_Recovery_6.0.0.8_GT-P7310_alternate
And if you flash the stock rom it doesn't do it. You might try that to rule out hardware issues
Edit: found someone else who had a similar problem. There is an issue with the boot loader. If you odin the stock rom and then flash the cm rom. That fixed it. You'll of course, have to reinstall your recovery and root.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Just tried one stock rom and it says
Finding update
Opening
Installing
Inslalation aborted
// I got that its ok to moment when i push lock/unlock button . When i had it on Charger i saw the battery ok but after i pressed lock it goes scattered/distorded like i show u picture. I really dunno what this is but im going via backup back to my gingerbread *SADNESS*
Where did you get the stock rom? Go to sammobile.com for it. You have to register, but it's free you'll download a zip file. Use 7-zip to extract the .tar.md5 file from it. Use that in Odin, PDA.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

[How To] CWM Recovery

With the new boot loader unlock it comes time to use a recovery other than safe strap. The easiest way to flash a custom recovery, in this case, clockwordmod recovery, is to simply download ROM Manager and use it to flash the Motorola Photon Q version of CWM Recovery. I flashed it and booted into it and haven't experienced any problems as of yet so for those looking for a custom recovery straight out of the gate, this is for you.
Sent from my MB886 using xda premium
Nice i don't know if i should try it or wait for an official one for our device. In the mean time back to my nexus 4
Sent from my MB886 using xda premium
If you really want to give it a spin you can always flash the Photon Q version otherwise I'm sure there will be an official version ported soon
Sent from my MB886 using xda premium
Dumb question...... if I uninstall ss and install cwm will I lose the current ROM im using?
Sent from my MB886 using xda app-developers app
You'll have to reinstall yes.
Sent from my JokerMATRIX HD MAXX
Dumb question part 2..... uninstall ss first and then install cwm? Also erase all ROM slots before uninstalling? Thanks!
Sent from my MB886 using xda app-developers app
Yea make sure to erase the rom slots. I forgot to and uninstalled then was missing quite a bit of space lol.
Sent from my JokerMATRIX HD MAXX
I was thinking it might be a good idea lol. Thanks!
Sent from my MB886 using xda app-developers app
it actually works. lol
freshlycutlawn said:
With the new boot loader unlock it comes time to use a recovery other than safe strap. The easiest way to flash a custom recovery, in this case, clockwordmod recovery, is to simply download ROM Manager and use it to flash the Motorola Photon Q version of CWM Recovery. I flashed it and booted into it and haven't experienced any problems as of yet so for those looking for a custom recovery straight out of the gate, this is for you.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
Have you flashed anything with it?
I haven't actually tried yet flashing a ROM but since I'm on stock and don't want to flash white yet I haven't had the opportunity, as long as its flashing to the device it should work with no problems
Sent from my MB886 using xda premium
freshlycutlawn said:
I haven't actually tried yet flashing a ROM but since I'm on stock and don't want to flash white yet I haven't had the opportunity, as long as its flashing to the device it should work with no problems
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
So far, i have installed the cwm for the photon q like you, and made a back up through it. Im going to see if it will restore from it as well. ill keep everyone updated.:good:
:edit: I sucessfully backed up my stock JB rom, wiped everything, and restored everything back and everythings perfect... I dont know what else to try before attempting to flash using the photon CWM. any ideas?
I uses the photon q recovery to backup & restore, and haven't had any issues yet. No ROM flashing for the time being, just haven't tried it yet.
Sent from my MB886 using xda premium
I Flashes AOSPizza and was getting a bootloop, had to start the phone in DB Mode from the Fastboot menu to get it to start up, charging my battery and will be restoring original at&t firmware as soon as possible....Dont need a brick just bought this!
I'm on aosp pizza but I reverted to the stock jelly bean system. Mounted system installed the aosp ROM the Mexico firmware was giving me hell except with cm 10
Sent from my Nexus 4 using xda app-developers app
DaveNavy said:
I Flashes AOSPizza and was getting a bootloop, had to start the phone in DB Mode from the Fastboot menu to get it to start up, charging my battery and will be restoring original at&t firmware as soon as possible....Dont need a brick just bought this!
Click to expand...
Click to collapse
Did you try to go back into CWM and wipe everything again after the boot loops? That sometimes helps when it is boot looping after an install.
bconcio said:
Did you try to go back into CWM and wipe everything again after the boot loops? That sometimes helps when it is boot looping after an install.
Click to expand...
Click to collapse
I tried the same thing with cm10, i tried 3 times and got bootloops on each, in the end, at least we know the back up and restore function works well.:good:
jbatacan said:
I tried the same thing with cm10, i tried 3 times and got bootloops on each, in the end, at least we know the back up and restore function works well.:good:
Click to expand...
Click to collapse
I'm Stock Again, Restart always sent me to fastboot with a failed flash error, I could back out of it to the pizza ROM each time however I don't want to depend on my phone booting incorrectly so I used RSD and I'm stock again, I'm going to give it another try tonight.
UPDATE...Reflashed everything started over and everything works PERFECT Yippie!!! I'm very pleased!!!!
Running AOSPizza and Loving it!
DaveNavy said:
I'm Stock Again, Restart always sent me to fastboot with a failed flash error, I could back out of it to the pizza ROM each time however I don't want to depend on my phone booting incorrectly so I used RSD and I'm stock again, I'm going to give it another try tonight.
UPDATE...Reflashed everything started over and everything works PERFECT Yippie!!! I'm very pleased!!!!
Running AOSPizza and Loving it!
Click to expand...
Click to collapse
So what was your full procedure? I want to try this and try to install CM10 later.
From what I read, you installed the Photon Q CWM, installed Pizza through that, got boot loops, flashed back to stock, then installed Pizza again?
bconcio said:
So what was your full procedure? I want to try this and try to install CM10 later.
From what I read, you installed the Photon Q CWM, installed Pizza through that, got boot loops, flashed back to stock, then installed Pizza again?
Click to expand...
Click to collapse
Fastboot was kicking errors and was boot looping into fastboot with firmware flash fail, I found however I could start into AOSPizza in DB mode (Safe Mode) , so I did that, charged up the phone 100% then used RSDLite and Reflashed Stock current firmware, it however does not re-lock the bootloader as some have mentioned might be the case in other post's, from there I started up the phone,turned on usb debug, used "motochopper" to root it, then installed Rom Manager from the market, flashed clockwork to device with the Photo Q CWM , copied AOSPixxaV1.zip ( The ROM ) and GappizzaV1.zip to the Phones internal storage not on the external SD memory card, from there went to clockwork mod on my atrix opened up the program and selected to reboot into recovery, went to the mounts and storage then select Mount System then go back then install zip from sd card then choose zip from sd card, then scroll to your rom and select it and it will flash when its complete you will go back and go to reboot system now, it will ask you if you want to bypass stock recovery on boot select it and your phone will reboot into AOSPizza......Have Fun!

[Q] bootloops after flashing rom

I just got a nexus one for $35 that i plan on using mostly as an mp3 player. I rooted it using the one click method but it's still S-on. Part of my issue is that booting into recovery using CWM only works maybe 25% of the time. Not sure why that is. A couple times I've been able to flash a rom via recovery but after seeing the X screen, the phone bootloops on the next splash screen. This has happened on two GB roms - MIUI and CM 7.2.
Any guess on why this happens? One reason I want to flash a rom is that the camera doesn't work so I'm curious if it would work in a different rom.
nvillamob said:
I just got a nexus one for $35 that i plan on using mostly as an mp3 player. I rooted it using the one click method but it's still S-on. Part of my issue is that booting into recovery using CWM only works maybe 25% of the time. Not sure why that is. A couple times I've been able to flash a rom via recovery but after seeing the X screen, the phone bootloops on the next splash screen. This has happened on two GB roms - MIUI and CM 7.2.
Any guess on why this happens? One reason I want to flash a rom is that the camera doesn't work so I'm curious if it would work in a different rom.
Click to expand...
Click to collapse
Before flashing a ROM, clear cache/ dalvik-cache from recovery. If you don't do these, then you will see bootloops.
I had been doing that through rom manager but just did it through recovery. still bootlooping.
I wiped cache but did not factory reset
Sent from my Nexus 4 using xda app-developers app
nvillamob said:
I had been doing that through rom manager but just did it through recovery. still bootlooping.
I wiped cache but did not factory reset
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
If you are changing ROMs, its always advisable to do a factory reset in addition to clearing cache and dalvik. Try it
Sent from my Nexus One
Best advice is to skip ROM manager and always do everything manually in recovery, this has never been a problem for me
And just because, I would suggest using 4ext recovery as in my opinion it is by far the most superior recovery... Just saying
Sent from my Nexus 4 using xda premium
Unfortunately, I've tried flashing manually via recovery too...still bootloops
Check md5sum of ROM (maybe bad download)
Make sure you wipe fully (manually in recovery or with fastboot)
Make sure you meet requirements of ROM in op (as in you flashed gapps if needed or you have a large enough system partition etc)
Sent from my Nexus 4 using xda premium
yeah, i haven't checked the md5's but it's odd that it's happened with both official miui and cyanogenmod. i did wipe cache and dalvik. i think i'm just going to give up. i'd do a factory restore but don't want to do that because then i'd have to root my phone again. i rooted the phone using a Vista computer but now I'm back home and my computer runs windows 8. from what I can tell, installing the android SDK is kinda complicated on W8.
Factory reset is needed and will not mean you have to reroot your phone, this is something that would be done before each flash, in fact the cleaner the wipe the less chance of an issue.
Also there is no need for the SDK to root (but its easy to get for windows 8 anyway and tools such as fastboot and adb are very handy... Also there are other ways to get these tools without the SDK) but all that besides the point, these are your steps
Nandroid backup
Wipe everything as clean as possible
Flash ROM and anything else needed (gapps etc)
Reboot
This is the procedure you should follow for any ROM flash for any android and never a need to reroot in between
Best of luck
Sent from my Nexus 4 using xda premium
I really appreciate the help. the reason I mention the SDK is that my computer doesn't recognize my phone unless I install the SDK and the associated drivers. So I'd hate the wipe my phone so that I can flash a rom, but then be unable to flash a rom because I'm not rooted!
But you feel confident that if I factory reset, I won't loose root?
I factory reset daily! You'll be just fine, when you factory reset and wipe all partitions you are following the proper procedure to change roms. When you flash the new one you are sure to still have root access
Sent from my Nexus 4 using xda premium
well, did a factory reset last night but i'm still having the same problem. I'm at a loss.

Categories

Resources