Related
I just don't get it. I literally follow every instruction to a T and still get hosed every time. The Droid is so much easier to hack than these phones. It's unnerving.
Here's a 'quick' recap of what I've done so far.
My girlfriend has a vibrant, I installed one of sombionix's ROMs on it and she loved it. I think the latest one I installed was 1.7 I convinced her to try out a froyo ROM and she didn't like it, so I went into recovery and attempted to restore a nandroid backup I had made of the 2.1 ROM. Little did I know that apparently you have to install a 2.1 kernel on the Vibrant first if moving from a 2.2 ROM to a 2.1 ROM (Nandroid on the droid restores the kernel too, so I wasn't aware of this). So recovery got stuck at 'restoring data'.
I spent a week trying to get the damn phone into download mode, FINALLY got it there and restored back to stock JI6 (I think that's what it's called anyway). At this point I was on a stock 2.1 kernel and thought that restoring the original nandroid backup would work this time. Yet AGAIN the restore got stuck at 'restoring data'. Can someone please tell me what the hell I'm doing wrong? After waiting 45 minutes at 'restoring data' I rebooted the phone again. The odd thing is, the bionix lady started talking and saying she was initializing bionix. I know this normally takes 10 minutes or so, so I am waiting, but I have a hard time believing the phone will work without being fully restored. Is it possible I didn't wait long enough? (45 minutes on 'restoring data')
Any other suggestions for what I've done wrong? Will Vibrant hacking always be this frustrating? If so, I'm probably going to get her back to stock and leave her that way. The only problem is I *NEED* to get this nandroid backup to work to get some important text messages and other things she had saved. Please help.
So I just odin'd back to stock, and this time before attempting to restore the nandroid backup I went into CWM myself to delete data and cache before restoring. The phone hangs at 'formatting data'. It's as if anytime CWM tries to do anything with the data partition the phone freezes. Any suggestions?
Alright, I FINALLY got the restore process to finish. I then rebooted the phone and now I'm stuck at the Vibrant logo. What on earth am I doing wrong? I just don't understand this. It's like every single time I conquer one obstacle, there's another one waiting for me. What do I need to do now? The bionix lady says 'initiating bionix, hardware acceleration sequence enabled', etc. as if it's going to load up but it does nothing. What now?
ARGH. So after getting the restore process to work and getting stuck on the vibrant screen, I again odin'd back to stock JI6. Instead of Odin flashing me back to stock JI6, somehow my phone came on and is exactly the same as when I made the original nandroid backup I've been trying so hard to restore to, except that there is no root, it's the wrong kernel, and things aren't working right (apps do nothing when clicked, text messages won't open, etc). WHAT THE HELL IS GOING ON?!?! UGH.
I absolutely loathe this phone. Its performance is amazing, but this thing is a hacker's nightmare. I feel bad for those of you that own this piece of ****. I just spent the past hour redownloading a bionix 2.1 ROM, manually restoring all of her apps from titanium backup (free version, so had to do it one by one). I FINALLY got the phone to a point that was very similar to the nandroid backup I've been trying so hard to get back to and the damn thing rebooted, and now launcherpro is force closing repeatedly and not allowing me to do anything else at all. This phone is absolute crap as far as hacking goes. And I know, I know, I'm sure plenty of you will respond with wise ass remarks like 'if you knew what you were doing it wouldn't be', or 'I've never had a problem', but just the fact that this phone is only a few months old and its support forum is 5x more active than the most active Droid support forums shows how much harder this thing is to hack than my Droid. I am so frustrated with this thing I'm about to throw it out the damn window. You literally cannot do anything without encountering a new problem.
I guess I'll start the whole process over again. What a waste of good hardware.
It just never ends with this thing. Now after odin'ing back to stock the phone goes to a black screen and just sits there unresponsive. I ****ing hate my life. I really do. Will someone please help me? Please tell me what I did wrong in each of the 6 to 7 different problems I've had in this thread now?
Well it's all over now. After the most recent debacle I found a thread stating that if stuck on a black screen, flash the 'froyo that doesn't brick' through odin, then downgrade to stock JI6. I did that, and the phone boots now, but it wiped the SD card so it's all over now. All my nandroid backups, all files, everything is gone. Somehow the only thing it didn't wipe is an angry birds APK I bluetoothed to her phone the night it came out, since it wasn't showing up in her market yet. This phone may dominate my Droid in performance, but I have never had so many issues with a device in my entire life, not even when I first began hacking my Droid. I am going to leave her on stock and move on with my life. So many hours wasted on this piece of ****, my head is spinning. I do appreciate all the help on this forum but it's all been in vain. Thanks anyway everyone.
You keep posting to yourself. The reason, you are the issue. Some people forget to go to a2.1 kernel, but this thread is crazy. I've been flashing this phone since it came out with no issues at all. Don't bash the phone because YOU are having a problem.
I think he'd have been well advised to steer his girl to an HTC, not samsnot. Sorry you had such a ***** of a time man.
Sent from my PC36100 using XDA App
Oh boy, may I suggest RTFM before you screw with your girlfriend's phone any longer?
http://forum.xda-developers.com/showthread.php?t=732458
http://forum.xda-developers.com/showthread.php?t=771111
velocity92c said:
I absolutely loathe this phone. Its performance is amazing, but this thing is a hacker's nightmare. I feel bad for those of you that own this piece of ****. I just spent the past hour redownloading a bionix 2.1 ROM, manually restoring all of her apps from titanium backup (free version, so had to do it one by one). I FINALLY got the phone to a point that was very similar to the nandroid backup I've been trying so hard to get back to and the damn thing rebooted, and now launcherpro is force closing repeatedly and not allowing me to do anything else at all. This phone is absolute crap as far as hacking goes. And I know, I know, I'm sure plenty of you will respond with wise ass remarks like 'if you knew what you were doing it wouldn't be', or 'I've never had a problem', but just the fact that this phone is only a few months old and its support forum is 5x more active than the most active Droid support forums shows how much harder this thing is to hack than my Droid. I am so frustrated with this thing I'm about to throw it out the damn window. You literally cannot do anything without encountering a new problem.
I guess I'll start the whole process over again. What a waste of good hardware.
Click to expand...
Click to collapse
You say its a hackers nightmare, it is one of the few phones that is almost impossible to brick, do not consider yourself a hacker for using odin, you could not even figure out how to do that right and messed up, that is what happend you are the reason it wouldn't work the phone is great you just suck.
i was doing my first flash of a rom last night and i didnt notice a status bar letting you know what processes were going on or if it was even installing the rom. So... i left it sitting on the vibrant screen for like 20 minutes and i saw absolutely nothing going on and became concerned it bricked. so i whipped out the old trusty backup iphone and went to downloading android sdk and supporting programs so i could adb in and make it reboot. i got tired around 1am and called it a night. put the vibrant on the charger and noticed the battery charging display popped up and it was half full. left it to charge all night and left the laptop updating and downloading all the sdk tools and stuff. got up next morning and plugged the vibrant into the laptop and the vibrant screen popped up as usual when u plug it in to a computer. i paid no attn and brought up my cmd line and was fixing to adb reboot recover and low and behold i heard the tmo jingle and saw the galaxy s icon start going. so long story short would it be a big deal to put a status bar to let someone know its actually doing something other than just sitting there? just a thought... and what length of time does it usually take to flash a rom and reboot the system?
HaCkEdUpViB said:
i was doing my first flash of a rom last night and i didnt notice a status bar letting you know what processes were going on or if it was even installing the rom. So... i left it sitting on the vibrant screen for like 20 minutes and i saw absolutely nothing going on and became concerned it bricked. so i whipped out the old trusty backup iphone and went to downloading android sdk and supporting programs so i could adb in and make it reboot. i got tired around 1am and called it a night. put the vibrant on the charger and noticed the battery charging display popped up and it was half full. left it to charge all night and left the laptop updating and downloading all the sdk tools and stuff. got up next morning and plugged the vibrant into the laptop and the vibrant screen popped up as usual when u plug it in to a computer. i paid no attn and brought up my cmd line and was fixing to adb reboot recover and low and behold i heard the tmo jingle and saw the galaxy s icon start going. so long story short would it be a big deal to put a status bar to let someone know its actually doing something other than just sitting there? just a thought... and what length of time does it usually take to flash a rom and reboot the system?
Click to expand...
Click to collapse
regularly for me, the average is about 5-7 minutes, not including the time it takes to download the ROM itself on computer and transfer.
Probably because i have everything set up, i have a file called FIX BRICK and all the files i need in there to "fix" the "brick"
I'm used to it, and don't mind odin'ing so its all quite short.
but most of the time IS taken up by the phone reformatting everything, then rebooting, the first boot is ALWAYS the longest.
Were you installing a ROM with a Voodoo kernel baked in? If so it takes about 15 min to reformat the file system.
CrazyCharlie said:
Were you installing a ROM with a Voodoo kernel baked in? If so it takes about 15 min to reformat the file system.
Click to expand...
Click to collapse
does it?
I just flashed AXURA with voodoo in it, and it took me like 6 minutes.... o god, lemme confirm i have it enabled or something lol
i heard linda talking and telling me the confirm time, but.......
brb gonna check!
nvm its already enabled lol... guess my phone's awesome?
also i went to stock using odin then flashed so my previous voodoo has nothing to do with this
If it was already enabled when you flashed Auxura then it was probably because the rom you were having trouble with already reformated the file system. Voodoo can be tricky with some of the older rom's but with the ability to enable and disable through clockwork it's much easier to deal with. Remember when flashing new rom's to disable the lagfix first. If the new rom uses a non voodoo kernel you'll get a soft brick.
CrazyCharlie said:
If it was already enabled when you flashed Auxura then it was probably because the rom you were having trouble with already reformated the file system. Voodoo can be tricky with some of the older rom's but with the ability to enable and disable through clockwork it's much easier to deal with. Remember when flashing new rom's to disable the lagfix first. If the new rom uses a non voodoo kernel you'll get a soft brick.
Click to expand...
Click to collapse
na i did it on purpose.
When i want to use a rom for a long time, i odin back, so there are no ghosts what so ever left, and then flash the rom, so its fast just as good as new.
and i checked re-format on odin, so the ext4, was turned back to RFS or RTS what ever that is.
The longest it ever took for my phone was when I went from 2.1 to 2.2 for the first time. Wasn't more than 10 minutes but noticeably longer. Patience is key.
Whether you break your phone now or later, go ahead and get all things necessary to fix. Just sayin...
Agreed. Odin is you're friend.
[ROM] Vibrant AOSP ish JK2 1.1 Official FROYO (Working GPS, WiFi Calling) this is the rom i used. idk if it has a voodoo kernel. i wouldnt think so. it was asthetically pleasing to my eye when i saw the screen shots and i noticed all the bloatware was gone so thats y i chose it. i like it so far. kinda glitchy at the first restart/reboot ( moved all of my widgets back to where they were on first start up after i placed them where i wanted them, and i had to load my google acct twice and my FB contacts twice) but since then it seems like everything has settled down and i am very pleased. kudos to the rom maker. its 10 times better than eclair. thanks for the input guys
btw im really diggin the car section. does it pair via bluetooth?
Hey guys, this is my first post on XDA as I'm usually lurking or keeping up with updates. I've searched many forums for an answer to my problem but it does not seem that anyone has had the same issue.
Anyway, lately I've run into the problem of an unresponsive touchscreen. I can't even unlock my phone! Two nights ago I made three consecutive calls and about ten minutes later I couldn't unlock my phone.
In order to correct this problem, I first took off the screen protector to no avail. I was running CM7, flashed a sense ROM, flashed my backup of the stock ROM, went back to stock with S-ON, pulled the battery a bunch of times, completely wiped, removed the SD card, Soft & hard reset at a VZW store. Nothing.
Took it with me to school today, powered it on and before it completely loaded I was able to unlock it by chance, skipped the setup and it was working fine all day. I was hella overjoyed... until it did it again tonight. D: I so want it to be OS issues rather than hardware because I don't want to wait two days to get a 'reconditioned' TB from VZW.
HALP! Please? Thanks, guys for even looking!
MP
P.S. I do apologize if I did not follow proper procedure to post or posted in the wrong subforum. S:
I'm frustrated and sitting around with an unrooted TB, ohnoes. (Although the screen looks sexy as hell without a screen protector.)
moneecuh said:
Hey guys, this is my first post on XDA as I'm usually lurking or keeping up with updates. I've searched many forums for an answer to my problem but it does not seem that anyone has had the same issue.
Anyway, lately I've run into the problem of an unresponsive touchscreen. I can't even unlock my phone! Two nights ago I made three consecutive calls and about ten minutes later I couldn't unlock my phone.
In order to correct this problem, I first took off the screen protector to no avail. I was running CM7, flashed a sense ROM, flashed my backup of the stock ROM, went back to stock with S-ON, pulled the battery a bunch of times, completely wiped, removed the SD card, Soft & hard reset at a VZW store. Nothing.
Took it with me to school today, powered it on and before it completely loaded I was able to unlock it by chance, skipped the setup and it was working fine all day. I was hella overjoyed... until it did it again tonight. D: I so want it to be OS issues rather than hardware because I don't want to wait two days to get a 'reconditioned' TB from VZW.
HALP! Please? Thanks, guys for even looking!
MP
P.S. I do apologize if I did not follow proper procedure to post or posted in the wrong subforum. S:
I'm frustrated and sitting around with an unrooted TB, ohnoes. (Although the screen looks sexy as hell without a screen protector.)
Click to expand...
Click to collapse
sounds like it could be a digitizer(hardware related) issue. on the plus side, you can pickup a new digitizer pretty cheap... downside though is you'd have to open up the phone to replace it. it's not that hard to do and there's videos online showing you how to.. you'd just have to be comfortable i suppose.
i'd just fix it rather then going the refurbished route considering that god know's what was wrong with it before it became "refurbished" not to mention you have no idea how much use the phone had been put through and how much life it has left.
Hello all,
I've had the same touchscreen? issues with 2 different Evo3D's. The first phone I had replaced even though when I took the phone to a Sprint repair center, the Slate machine said theres nothing wrong with the phone.
What happens is quite simply is the phone starts acting crazy. It acts like Im pressing on the screen, making tons of selections, calling people etc...I can click on the power button to make it stop. But then it will act up again in a few minutes. The first phone I had the store flash back to stock, turned s-off etc... It didn't make a difference. No matter what ROM is on the phone it continues to do it. So I had that phone replaced.
The second phone does the exact samething. If I didn't have the first phone in front of me when I received the second one, I would have thought they sent me the same phone back to me. I rooted this one right away as the other one so I dont know if the phone had the same problem before the root process. I've stuck on a ton of different ROMS to various degrees of success. I'm running Eternity right now because it allows me to at least use the phone semi functionally. The touchscreen problems are limited to the upper 20% of the screen where its unresonsive most of the time. But the craziness clicking is down to a minimum comapred to other roms.
I fixed the problem once when I was flipping ROMS and kernels. I put on ViperROM2.1 then flashed the Tiamat kernel. I was like yesssssss, I found the right combo. But alot of the phones functions didnt work like voice reconition, 4g, etc... So I cleared storage to start again and all the problems of the touchscreen as before came back. I've tried flashing kernels like Tiamat, stock, dual cores, single cores. Always have the same result. Last bit of info is I tried to superwipe and that failed. So maybe theres something in the internal memory thats causing all these problems? any help would be appreciated.
Thanks
kdub2000 said:
Hello all,
I've had the same touchscreen? issues with 2 different Evo3D's. The first phone I had replaced even though when I took the phone to a Sprint repair center, the Slate machine said theres nothing wrong with the phone.
What happens is quite simply is the phone starts acting crazy. It acts like Im pressing on the screen, making tons of selections, calling people etc...I can click on the power button to make it stop. But then it will act up again in a few minutes. The first phone I had the store flash back to stock, turned s-off etc... It didn't make a difference. No matter what ROM is on the phone it continues to do it. So I had that phone replaced.
The second phone does the exact samething. If I didn't have the first phone in front of me when I received the second one, I would have thought they sent me the same phone back to me. I rooted this one right away as the other one so I dont know if the phone had the same problem before the root process. I've stuck on a ton of different ROMS to various degrees of success. I'm running Eternity right now because it allows me to at least use the phone semi functionally. The touchscreen problems are limited to the upper 20% of the screen where its unresonsive most of the time. But the craziness clicking is down to a minimum comapred to other roms.
I fixed the problem once when I was flipping ROMS and kernels. I put on ViperROM2.1 then flashed the Tiamat kernel. I was like yesssssss, I found the right combo. But alot of the phones functions didnt work like voice reconition, 4g, etc... So I cleared storage to start again and all the problems of the touchscreen as before came back. I've tried flashing kernels like Tiamat, stock, dual cores, single cores. Always have the same result. Last bit of info is I tried to superwipe and that failed. So maybe theres something in the internal memory thats causing all these problems? any help would be appreciated.
Thanks
Click to expand...
Click to collapse
My guess is that something is screwing up kernal wise or your flashing. If your phone was fine stock then something got dicked during the flash.
Is there anything I can do to a clean wipe and start fresh again? Or should I try to figure out why the Superwipe isnt working? Or do I have to flash all the stock back on and turn the s-on and get a new phone? I think the digitizer is causing these issues.
A while back I rooted my Samsung Galaxy S4 GT-i9506, I didn't modify it other than that, I just rooted so I could hack games, install snapchat addons, etc. No Custom Roms/Kernels, none of that. Then my phone smashed and the screen stopped working, it took me about 2 months to get it fixed so when I got it back it was being really slow, all it needed was time but then the Samsung Sync was not working, so I tried to update, it said that I couldn't because my device was modified, so I eventually after doing a couple things, got my device to Android 5.0.1 Lolipop by Flashing with Odin and TWRP. When I first got onto 5.0.1 my wifi didn't work, my data does but not the wifi, I have been looking for at least a week for a fix for this, but nothing seems to work. I'm not sure if i'm missing something but i'm tired of this, i've been using a very smashed s3 and I want to use my S4 quite badly, If anyone got point me in the right direction or even help me out on this one, I would appreciate it heaps! When I hit the wifi button it doesn't get stuck on that grey/green or anything, it just doesn't turn on, it goes straight back to grey. I assume this is the modem but I have tried getting a newer modem and it hasn't worked, i'll be checking this for a while until this problem is resolved, any help would be very appreciated!